From 0aa953b2fd0fe08e3a683e93eda2ad4a3d834be4 Mon Sep 17 00:00:00 2001
From: PedroAntunesCosta <PedroAntunesCosta@users.noreply.github.com>
Date: Thu, 1 Aug 2024 19:28:35 +0000
Subject: [PATCH 01/13] update documentation files using contentful

---
 ...s-pagespeed-insights-in-your-vtex-admin.md |    2 +-
 .../en/admin-disponivel-em-japones.md         |    2 +-
 ...ion-will-now-be-restricted-by-user-role.md |    2 +-
 ...mazon-integration-amazon-offer-matching.md |   35 +
 .../en/amazon-new-category-mapping-model.md   |   36 +
 ...to-simplify-product-customization-teste.md |    2 +-
 ...w-app-to-simplify-product-customization.md |    2 +-
 ...metrics-now-available-in-search-reports.md |    2 +-
 ...automatic-archiving-inactive-promotions.md |   41 +
 ...eek-vtex-dashboards-analysis-strategies.md |   22 +
 ...lment-operation-with-vtex-pick-and-pack.md |    2 +-
 ...back-url-signature-authentication-token.md |   32 +
 ...option-when-configuring-target-audience.md |    2 +-
 .../en/catalogs-new-visual-and-navigation.md  |    8 +-
 ...ed-actions-available-to-the-master-user.md |    2 +-
 .../changes-in-vtex-support-service-policy.md |   18 +
 .../checkout-api-now-supports-recaptcha-v3.md |   38 +
 ...ing-up-the-cardholder-document-id-field.md |    2 +-
 ...s-into-sales-with-whatsapp-ai-campaigns.md |   29 +
 .../en/coupon-experience-improvements.md      |    4 +-
 ...-selection-of-sellers-for-b2b-purchases.md |   32 +
 ...ntinuation-of-legacy-payment-connectors.md |   88 ++
 ...-bulk-data-import-for-organizations-and.md |   30 +
 ...displaying-pickup-points-on-google-maps.md |    2 +-
 ...before-activating-it-to-ensure-security.md |    2 +-
 ...efore-activating-it-to-ensure-security1.md |    2 +-
 ...rs-with-the-new-reviews-and-ratings-app.md |    2 +-
 ...trol-on-your-order-authorization-screen.md |    2 +-
 ...xpand-your-operation-through-vtex-admin.md |   12 +-
 ...t-your-conversion-with-the-new-checkout.md |   70 +
 ...ort-with-new-solutions-for-vtex-clients.md |   35 +
 ...ty-with-the-updated-price-table-feature.md |    2 +-
 ...anaging-your-orders-events-with-feed-v3.md |    7 +-
 .../get-to-know-the-new-vtex-status-page.md   |   36 +
 ...ck-friday-with-our-best-practices-guide.md |    2 +-
 ...ason-with-our-best-practices-guide-2022.md |    2 +-
 .../en/google-catalog-migration.md            |   42 +
 ...ay-new-payment-method-available-on-vtex.md |   36 +
 ...le-shopping-new-option-to-submit-prices.md |   40 +
 ...dless-cms-create-non-duplicatable-pages.md |    2 +-
 ...r-insights-into-page-publication-status.md |   35 +
 .../headless-cms-events-available-in-audit.md |   47 +
 ...dless-cms-new-authorization-requirement.md |   57 +
 ...t-creation-and-management-with-projects.md |   40 +
 ...y-informed-on-your-publication-progress.md |   45 +
 .../headless-cms-updated-user-permissions.md  |   33 +
 ...curity-for-the-customers-first-purchase.md |    8 +-
 ...nt-of-discount-price-viewing-experience.md |    8 +-
 ...nts-in-exporting-prices-via-spreadsheet.md |    2 +-
 ...nts-to-unified-search-in-vtex-sales-app.md |   43 +
 ...s-with-a-new-order-authorization-screen.md |    2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |    2 +-
 .../en/introducing-vtex-ad-network-beta.md    |   48 +
 ...-emails-containing-access-code-requests.md |    2 +-
 ...-configuring-shipping-time-at-sku-level.md |   50 +
 ...connectors-will-be-discontinued-in-2024.md |  123 ++
 ...g-the-vtex-app-to-broadcast-live-events.md |    2 +-
 ...-for-credit-and-debit-cards-at-checkout.md |   40 +
 ...rketplace-improvements-on-received-skus.md |    2 +-
 .../marketplace-network-has-been-improved.md  |    2 +-
 .../marketplace-new-offer-quality-filters.md  |    2 +-
 ...e-new-sidebar-with-received-sku-details.md |    2 +-
 ...-and-integrations-are-now-a-single-page.md |    2 +-
 .../en/marketplaces-received-skus-beta.md     |    6 +-
 ...er-data-v1-dynamic-settings-deprecation.md |   53 +
 ...tion-new-promotion-management-interface.md |    2 +-
 ...tenacao-reduz-erros-no-envio-de-e-mails.md |    6 +-
 .../en/multi-currency-gift-card.md            |   48 +
 .../en/multilanguage-checkout-launch.md       |   26 +
 ...my-authentication-section-in-my-account.md |   16 +-
 ...-data-in-store-overview-beta-admin-page.md |   44 +
 ...kout-settings-for-bot-attack-protection.md |   52 +
 ...e-the-technical-aspects-of-the-platform.md |   40 +
 ...ture-product-feedback-in-the-vtex-admin.md |   25 +
 ...custom-displays-by-store-and-collection.md |   26 +
 ...hoo-requirements-for-bulk-email-senders.md |   74 +
 .../en/new-indexation-history-screen.md       |    2 +-
 .../new-orders-module-interface-official.md   |    6 +-
 ...nts-for-an-improved-shopping-experience.md |    4 +-
 ...der-and-anti-fraud-management-interface.md |   36 +
 ...manage-redirects-in-store-framework-cms.md |   34 +
 .../en/new-process-for-security-testing.md    |   34 +
 ...manage-your-promotions-more-efficiently.md |    2 +-
 docs/announcements/en/new-roles-page.md       |   35 +
 .../new-rules-for-activating-vtex-support.md  |   33 +
 .../en/new-sales-app-performance-monitor.md   |   33 +
 .../en/new-sales-performance-dashboard.md     |    2 +-
 .../en/new-sku-bindings-interface.md          |    2 +-
 .../en/new-subscriptions-module.md            |   16 +-
 ...or-the-admins-user-management-dashboard.md |    2 +-
 ...vo-layout-no-e-mail-de-codigo-de-acesso.md |    2 +-
 ...ices-to-products-sold-in-vtex-sales-app.md |   28 +
 ...r-pickup-points-for-subscription-orders.md |    2 +-
 ...for-integrations-with-vtex-marketplaces.md |   30 +
 ...ores-my-account-page-will-change-review.md |    2 +-
 ...ing-guide-your-complete-journey-at-vtex.md |   79 +
 docs/announcements/en/performance-monitor.md  |   18 +
 ...s-new-payment-method-on-your-e-commerce.md |   18 +-
 .../price-filters-more-search-flexibility.md  |    2 +-
 ...ontinued-update-your-store-by-september.md |    2 +-
 ...tand-the-promotions-applied-to-the-cart.md |   55 +
 .../en/rate-vtexs-service-in-your-admin.md    |    2 +-
 ...rderform-configuration-for-all-requests.md |   87 ++
 .../en/redesigned-products-and-skus-page.md   |    2 +-
 ...agination-will-change-in-the-search-api.md |    8 +-
 .../en/sales-performance-dashboard-updates.md |    2 +-
 ...yments-thanks-to-the-new-digital-wallet.md |   16 +-
 ...stored-information-for-future-purchases.md |    2 +-
 ...le-content-publication-with-site-editor.md |    2 +-
 ...earch-filters-in-instores-endless-aisle.md |    2 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |   50 +
 ...grates-your-business-to-google-shopping.md |    2 +-
 ...with-more-control-over-affected-sellers.md |    4 +-
 ...eady-with-our-best-practices-guide-2023.md |   30 +
 ...and-media-new-authorization-requirement.md |   35 +
 .../site-editor-fixed-content-loss-issue.md   |   28 +
 ...ling-share-instore-carts-using-qr-codes.md |    2 +-
 .../social-selling-share-your-instore-cart.md |    4 +-
 ...insights-dashboard-will-be-discontinued.md |   39 +
 ...t-page-will-change-review-your-settings.md |    2 +-
 ...-management-module-will-be-discontinued.md |   35 +
 ...laced-by-the-term-role-in-your-admin-ui.md |    2 +-
 ...-and-security-with-the-new-audit-module.md |    2 +-
 ...s-your-new-vtex-self-service-experience.md |   53 +
 .../update-grants-in-the-promotions-module.md |    2 +-
 .../update-of-the-external-privacy-notice.md  |   39 +
 ...pgrade-your-store-to-google-analytics-4.md |   12 +-
 ...ustomers-abandoning-their-shopping-cart.md |    2 +-
 ...rovements-at-checkout-for-expired-cards.md |    2 +-
 .../en/vtex-insurance-discontinuity.md        |   31 +
 ...w-visual-editor-for-merchandising-rules.md |   37 +
 .../vtex-io-documentation-has-a-new-home.md   |    4 +-
 ...ow-available-in-dutch-french-and-korean.md |    2 +-
 ...e-new-version-of-instore-vtex-sales-app.md |    6 +-
 .../en/vtex-marketplace-launches-in-2022.md   |    6 +-
 ...will-no-longer-be-available-for-windows.md |   37 +
 .../en/web-page-performance-deprecation.md    |   24 +
 ...elcome-to-the-redesigned-vtex-admin-new.md |    2 +-
 ...r-new-cross-selling-and-up-selling-apis.md |    6 +-
 ...ist-discover-the-new-vtex-app-store-app.md |    2 +-
 ...ss-to-the-settings-screen-on-the-orders.md |    4 +-
 ...s-pagespeed-insights-in-your-vtex-admin.md |    2 +-
 .../es/admin-disponivel-em-japones.md         |    2 +-
 ...ion-will-now-be-restricted-by-user-role.md |    2 +-
 ...mazon-integration-amazon-offer-matching.md |   35 +
 .../es/amazon-new-category-mapping-model.md   |   35 +
 ...to-simplify-product-customization-teste.md |    2 +-
 ...w-app-to-simplify-product-customization.md |    2 +-
 ...metrics-now-available-in-search-reports.md |    2 +-
 ...automatic-archiving-inactive-promotions.md |   41 +
 ...eek-vtex-dashboards-analysis-strategies.md |   22 +
 ...lment-operation-with-vtex-pick-and-pack.md |    2 +-
 ...back-url-signature-authentication-token.md |   32 +
 ...option-when-configuring-target-audience.md |    2 +-
 .../es/catalogs-new-visual-and-navigation.md  |    8 +-
 ...ed-actions-available-to-the-master-user.md |    2 +-
 .../changes-in-vtex-support-service-policy.md |   18 +
 .../checkout-api-now-supports-recaptcha-v3.md |   39 +
 ...ing-up-the-cardholder-document-id-field.md |    2 +-
 ...s-into-sales-with-whatsapp-ai-campaigns.md |   29 +
 .../es/coupon-experience-improvements.md      |    4 +-
 ...-selection-of-sellers-for-b2b-purchases.md |   31 +
 ...s-with-the-new-card-level-functionality.md |    2 +-
 ...ntinuation-of-legacy-payment-connectors.md |   89 ++
 ...-bulk-data-import-for-organizations-and.md |   30 +
 ...displaying-pickup-points-on-google-maps.md |    2 +-
 ...before-activating-it-to-ensure-security.md |    2 +-
 ...efore-activating-it-to-ensure-security1.md |    2 +-
 ...rs-with-the-new-reviews-and-ratings-app.md |    2 +-
 ...trol-on-your-order-authorization-screen.md |    2 +-
 ...xpand-your-operation-through-vtex-admin.md |   10 +-
 ...t-your-conversion-with-the-new-checkout.md |   70 +
 ...ort-with-new-solutions-for-vtex-clients.md |   34 +
 ...ty-with-the-updated-price-table-feature.md |    2 +-
 ...anaging-your-orders-events-with-feed-v3.md |    6 +-
 .../get-to-know-the-new-vtex-status-page.md   |   36 +
 ...ck-friday-with-our-best-practices-guide.md |    2 +-
 ...ason-with-our-best-practices-guide-2022.md |    2 +-
 .../es/google-catalog-migration.md            |   40 +
 ...ay-new-payment-method-available-on-vtex.md |   36 +
 ...le-shopping-new-option-to-submit-prices.md |   40 +
 ...dless-cms-create-non-duplicatable-pages.md |    2 +-
 ...r-insights-into-page-publication-status.md |   33 +
 .../headless-cms-events-available-in-audit.md |   47 +
 ...dless-cms-new-authorization-requirement.md |   58 +
 ...t-creation-and-management-with-projects.md |   42 +
 ...y-informed-on-your-publication-progress.md |   45 +
 .../headless-cms-updated-user-permissions.md  |   18 +
 ...curity-for-the-customers-first-purchase.md |    8 +-
 ...nt-of-discount-price-viewing-experience.md |    8 +-
 ...nts-in-exporting-prices-via-spreadsheet.md |    2 +-
 ...nts-to-unified-search-in-vtex-sales-app.md |   44 +
 ...s-with-a-new-order-authorization-screen.md |    2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |    2 +-
 .../es/introducing-vtex-ad-network-beta.md    |   49 +
 ...-emails-containing-access-code-requests.md |    2 +-
 ...-configuring-shipping-time-at-sku-level.md |   50 +
 ...connectors-will-be-discontinued-in-2024.md |  123 ++
 ...g-the-vtex-app-to-broadcast-live-events.md |    4 +-
 ...-for-credit-and-debit-cards-at-checkout.md |   40 +
 ...rketplace-improvements-on-received-skus.md |    2 +-
 .../marketplace-network-has-been-improved.md  |    2 +-
 .../marketplace-new-offer-quality-filters.md  |    2 +-
 ...e-new-sidebar-with-received-sku-details.md |    2 +-
 ...-and-integrations-are-now-a-single-page.md |    2 +-
 .../es/marketplaces-received-skus-beta.md     |    6 +-
 ...er-data-v1-dynamic-settings-deprecation.md |   53 +
 ...tion-new-promotion-management-interface.md |    2 +-
 ...tenacao-reduz-erros-no-envio-de-e-mails.md |    6 +-
 .../es/multi-currency-gift-card.md            |   48 +
 .../es/multilanguage-checkout-launch.md       |   27 +
 ...my-authentication-section-in-my-account.md |   16 +-
 ...-data-in-store-overview-beta-admin-page.md |   44 +
 ...kout-settings-for-bot-attack-protection.md |   50 +
 ...e-the-technical-aspects-of-the-platform.md |   40 +
 ...ture-product-feedback-in-the-vtex-admin.md |   25 +
 ...custom-displays-by-store-and-collection.md |   26 +
 ...hoo-requirements-for-bulk-email-senders.md |   74 +
 .../es/new-indexation-history-screen.md       |    2 +-
 .../new-orders-module-interface-official.md   |    6 +-
 ...nts-for-an-improved-shopping-experience.md |    4 +-
 ...der-and-anti-fraud-management-interface.md |   36 +
 ...manage-redirects-in-store-framework-cms.md |   34 +
 .../es/new-process-for-security-testing.md    |   34 +
 ...manage-your-promotions-more-efficiently.md |    2 +-
 docs/announcements/es/new-roles-page.md       |   35 +
 .../new-rules-for-activating-vtex-support.md  |   32 +
 .../es/new-sales-app-performance-monitor.md   |   32 +
 .../es/new-sales-performance-dashboard.md     |    2 +-
 .../es/new-sku-bindings-interface.md          |    2 +-
 .../es/new-subscriptions-module.md            |   16 +-
 ...or-the-admins-user-management-dashboard.md |    2 +-
 ...vo-layout-no-e-mail-de-codigo-de-acesso.md |    2 +-
 ...ices-to-products-sold-in-vtex-sales-app.md |   28 +
 ...r-pickup-points-for-subscription-orders.md |    2 +-
 ...for-integrations-with-vtex-marketplaces.md |   31 +
 ...ores-my-account-page-will-change-review.md |    2 +-
 ...ing-guide-your-complete-journey-at-vtex.md |   79 +
 docs/announcements/es/performance-monitor.md  |   18 +
 ...s-new-payment-method-on-your-e-commerce.md |   18 +-
 .../price-filters-more-search-flexibility.md  |    2 +-
 ...ontinued-update-your-store-by-september.md |    2 +-
 ...tand-the-promotions-applied-to-the-cart.md |   54 +
 .../es/rate-vtexs-service-in-your-admin.md    |    2 +-
 ...rderform-configuration-for-all-requests.md |   88 ++
 .../es/redesigned-products-and-skus-page.md   |    2 +-
 ...agination-will-change-in-the-search-api.md |    8 +-
 .../es/reusing-images-in-site-editor.md       |    2 +-
 .../es/sales-performance-dashboard-updates.md |    2 +-
 ...yments-thanks-to-the-new-digital-wallet.md |   10 +-
 ...stored-information-for-future-purchases.md |    2 +-
 ...le-content-publication-with-site-editor.md |    2 +-
 ...earch-filters-in-instores-endless-aisle.md |    2 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |   50 +
 ...grates-your-business-to-google-shopping.md |    2 +-
 ...with-more-control-over-affected-sellers.md |    4 +-
 ...eady-with-our-best-practices-guide-2023.md |   30 +
 ...and-media-new-authorization-requirement.md |   35 +
 .../site-editor-fixed-content-loss-issue.md   |   29 +
 ...ling-share-instore-carts-using-qr-codes.md |    2 +-
 .../social-selling-share-your-instore-cart.md |    4 +-
 ...insights-dashboard-will-be-discontinued.md |   39 +
 ...t-page-will-change-review-your-settings.md |    2 +-
 ...-management-module-will-be-discontinued.md |   34 +
 ...-and-security-with-the-new-audit-module.md |    2 +-
 ...s-your-new-vtex-self-service-experience.md |   53 +
 .../update-grants-in-the-promotions-module.md |    2 +-
 .../update-of-the-external-privacy-notice.md  |   39 +
 ...pgrade-your-store-to-google-analytics-4.md |   12 +-
 ...ustomers-abandoning-their-shopping-cart.md |    2 +-
 ...rovements-at-checkout-for-expired-cards.md |    2 +-
 .../es/vtex-insurance-discontinuity.md        |   29 +
 ...w-visual-editor-for-merchandising-rules.md |   37 +
 .../vtex-io-documentation-has-a-new-home.md   |    4 +-
 ...ow-available-in-dutch-french-and-korean.md |    2 +-
 ...e-new-version-of-instore-vtex-sales-app.md |    6 +-
 .../es/vtex-marketplace-launches-in-2022.md   |    6 +-
 ...will-no-longer-be-available-for-windows.md |   36 +
 .../es/web-page-performance-deprecation.md    |   25 +
 ...elcome-to-the-redesigned-vtex-admin-new.md |    2 +-
 ...r-new-cross-selling-and-up-selling-apis.md |    6 +-
 ...ist-discover-the-new-vtex-app-store-app.md |    2 +-
 ...ss-to-the-settings-screen-on-the-orders.md |    4 +-
 ...s-pagespeed-insights-in-your-vtex-admin.md |    2 +-
 .../pt/admin-disponivel-em-japones.md         |    2 +-
 ...ion-will-now-be-restricted-by-user-role.md |    2 +-
 ...mazon-integration-amazon-offer-matching.md |   35 +
 .../pt/amazon-new-category-mapping-model.md   |   36 +
 ...to-simplify-product-customization-teste.md |    2 +-
 ...w-app-to-simplify-product-customization.md |    2 +-
 ...metrics-now-available-in-search-reports.md |    2 +-
 ...automatic-archiving-inactive-promotions.md |   41 +
 ...ome-an-expert-in-vtex-with-training-day.md |    2 +-
 ...eek-vtex-dashboards-analysis-strategies.md |   22 +
 ...lment-operation-with-vtex-pick-and-pack.md |    2 +-
 ...back-url-signature-authentication-token.md |   32 +
 ...option-when-configuring-target-audience.md |    2 +-
 .../pt/catalogs-new-visual-and-navigation.md  |    8 +-
 ...ed-actions-available-to-the-master-user.md |    2 +-
 .../changes-in-vtex-support-service-policy.md |   39 +
 .../checkout-api-now-supports-recaptcha-v3.md |   39 +
 ...ing-up-the-cardholder-document-id-field.md |    2 +-
 ...s-into-sales-with-whatsapp-ai-campaigns.md |   29 +
 .../pt/coupon-experience-improvements.md      |    4 +-
 ...-selection-of-sellers-for-b2b-purchases.md |   32 +
 ...s-with-the-new-card-level-functionality.md |    2 +-
 ...ntinuation-of-legacy-payment-connectors.md |   89 ++
 ...-bulk-data-import-for-organizations-and.md |   30 +
 ...displaying-pickup-points-on-google-maps.md |    2 +-
 ...rs-with-the-new-reviews-and-ratings-app.md |    2 +-
 ...trol-on-your-order-authorization-screen.md |    2 +-
 ...xpand-your-operation-through-vtex-admin.md |   10 +-
 ...t-your-conversion-with-the-new-checkout.md |   70 +
 ...ort-with-new-solutions-for-vtex-clients.md |   35 +
 ...ty-with-the-updated-price-table-feature.md |    2 +-
 ...anaging-your-orders-events-with-feed-v3.md |    8 +-
 .../get-to-know-the-new-vtex-status-page.md   |   36 +
 ...ck-friday-with-our-best-practices-guide.md |    2 +-
 ...ason-with-our-best-practices-guide-2022.md |    2 +-
 .../pt/google-catalog-migration.md            |   40 +
 ...ay-new-payment-method-available-on-vtex.md |   37 +
 ...le-shopping-new-option-to-submit-prices.md |   39 +
 ...dless-cms-create-non-duplicatable-pages.md |    2 +-
 ...r-insights-into-page-publication-status.md |   35 +
 .../headless-cms-events-available-in-audit.md |   47 +
 ...dless-cms-new-authorization-requirement.md |   58 +
 ...t-creation-and-management-with-projects.md |   39 +
 ...y-informed-on-your-publication-progress.md |   44 +
 .../headless-cms-updated-user-permissions.md  |   18 +
 ...curity-for-the-customers-first-purchase.md |    8 +-
 ...nt-of-discount-price-viewing-experience.md |    8 +-
 ...nts-in-exporting-prices-via-spreadsheet.md |    2 +-
 ...nts-to-unified-search-in-vtex-sales-app.md |   43 +
 ...s-with-a-new-order-authorization-screen.md |    2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |    2 +-
 .../pt/introducing-vtex-ad-network-beta.md    |   51 +
 ...-emails-containing-access-code-requests.md |    2 +-
 ...-configuring-shipping-time-at-sku-level.md |   50 +
 ...connectors-will-be-discontinued-in-2024.md |  123 ++
 ...-for-credit-and-debit-cards-at-checkout.md |   40 +
 ...rketplace-improvements-on-received-skus.md |    2 +-
 .../marketplace-network-has-been-improved.md  |    2 +-
 .../marketplace-new-offer-quality-filters.md  |    2 +-
 ...e-new-sidebar-with-received-sku-details.md |    2 +-
 ...-and-integrations-are-now-a-single-page.md |    2 +-
 .../pt/marketplaces-received-skus-beta.md     |    6 +-
 ...er-data-v1-dynamic-settings-deprecation.md |   53 +
 ...tion-new-promotion-management-interface.md |    2 +-
 ...tenacao-reduz-erros-no-envio-de-e-mails.md |    6 +-
 .../pt/multi-currency-gift-card.md            |   49 +
 .../pt/multilanguage-checkout-launch.md       |   26 +
 ...my-authentication-section-in-my-account.md |   16 +-
 ...-data-in-store-overview-beta-admin-page.md |   44 +
 ...kout-settings-for-bot-attack-protection.md |   52 +
 ...e-the-technical-aspects-of-the-platform.md |   40 +
 ...ture-product-feedback-in-the-vtex-admin.md |   25 +
 ...custom-displays-by-store-and-collection.md |   26 +
 ...hoo-requirements-for-bulk-email-senders.md |   74 +
 .../pt/new-indexation-history-screen.md       |    2 +-
 .../new-orders-module-interface-official.md   |    6 +-
 ...nts-for-an-improved-shopping-experience.md |    6 +-
 ...der-and-anti-fraud-management-interface.md |   36 +
 ...manage-redirects-in-store-framework-cms.md |   34 +
 .../pt/new-process-for-security-testing.md    |   34 +
 ...manage-your-promotions-more-efficiently.md |    2 +-
 docs/announcements/pt/new-roles-page.md       |   35 +
 .../new-rules-for-activating-vtex-support.md  |   30 +
 .../pt/new-sales-app-performance-monitor.md   |   32 +
 .../pt/new-sales-performance-dashboard.md     |    2 +-
 .../pt/new-sku-bindings-interface.md          |    2 +-
 .../pt/new-subscriptions-module.md            |   16 +-
 ...or-the-admins-user-management-dashboard.md |    2 +-
 ...vo-layout-no-e-mail-de-codigo-de-acesso.md |    2 +-
 ...ices-to-products-sold-in-vtex-sales-app.md |   29 +
 ...r-pickup-points-for-subscription-orders.md |    2 +-
 ...for-integrations-with-vtex-marketplaces.md |   31 +
 ...ores-my-account-page-will-change-review.md |    2 +-
 ...ing-guide-your-complete-journey-at-vtex.md |   78 +
 docs/announcements/pt/performance-monitor.md  |   23 +
 ...s-new-payment-method-on-your-e-commerce.md |   17 +-
 .../price-filters-more-search-flexibility.md  |    2 +-
 ...ontinued-update-your-store-by-september.md |    2 +-
 ...tand-the-promotions-applied-to-the-cart.md |   55 +
 .../pt/rate-vtexs-service-in-your-admin.md    |    2 +-
 ...rderform-configuration-for-all-requests.md |   87 ++
 .../pt/redesigned-products-and-skus-page.md   |    2 +-
 ...agination-will-change-in-the-search-api.md |    8 +-
 .../pt/reusing-images-in-site-editor.md       |    2 +-
 .../pt/sales-performance-dashboard-updates.md |    2 +-
 ...yments-thanks-to-the-new-digital-wallet.md |    6 +-
 ...stored-information-for-future-purchases.md |    2 +-
 ...le-content-publication-with-site-editor.md |    2 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |   50 +
 ...grates-your-business-to-google-shopping.md |    2 +-
 ...with-more-control-over-affected-sellers.md |    4 +-
 ...eady-with-our-best-practices-guide-2023.md |   30 +
 ...and-media-new-authorization-requirement.md |   34 +
 .../site-editor-fixed-content-loss-issue.md   |   29 +
 ...ling-share-instore-carts-using-qr-codes.md |    2 +-
 ...insights-dashboard-will-be-discontinued.md |   39 +
 ...t-page-will-change-review-your-settings.md |    2 +-
 ...-management-module-will-be-discontinued.md |   34 +
 ...-and-security-with-the-new-audit-module.md |    2 +-
 ...s-your-new-vtex-self-service-experience.md |   53 +
 .../untitled-entry-2021-01-19-at-17-22-53.md  |    2 +-
 .../update-grants-in-the-promotions-module.md |    2 +-
 .../update-of-the-external-privacy-notice.md  |   39 +
 ...pgrade-your-store-to-google-analytics-4.md |   12 +-
 ...ustomers-abandoning-their-shopping-cart.md |    2 +-
 ...rovements-at-checkout-for-expired-cards.md |    2 +-
 .../pt/vtex-insurance-discontinuity.md        |   30 +
 ...w-visual-editor-for-merchandising-rules.md |   37 +
 .../vtex-io-documentation-has-a-new-home.md   |    4 +-
 ...ow-available-in-dutch-french-and-korean.md |    2 +-
 ...e-new-version-of-instore-vtex-sales-app.md |    6 +-
 .../pt/vtex-marketplace-launches-in-2022.md   |    8 +-
 ...will-no-longer-be-available-for-windows.md |   37 +
 .../pt/web-page-performance-deprecation.md    |   24 +
 ...elcome-to-the-redesigned-vtex-admin-new.md |    2 +-
 ...r-new-cross-selling-and-up-selling-apis.md |    6 +-
 ...ist-discover-the-new-vtex-app-store-app.md |    2 +-
 ...ss-to-the-settings-screen-on-the-orders.md |    4 +-
 ...ations-to-troubleshoot-front-end-issues.md |   12 +-
 ...iliations-that-support-native-split-faq.md |    2 +-
 .../faq/en/fix-redirect-error-in-pagseguro.md |   22 +-
 .../en/how-do-i-find-the-order-nsu-and-tid.md |    2 +-
 docs/faq/en/how-does-vtex-support-work.md     |   19 +-
 ...ciate-two-promotions-to-the-same-coupon.md |    4 +-
 ...nt-edit-a-required-field-on-master-data.md |    6 +-
 ...ecognize-the-reservation-id-of-an-order.md |    6 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |    2 +-
 ...ook-is-not-displayed-in-the-shop-window.md |    2 +-
 .../en/my-admin-is-blocked-what-do-i-do.md    |   13 +-
 ...-in-ready-for-handling-what-should-i-do.md |   30 +
 ...iliations-are-highlighted-in-yellow-why.md |    2 +-
 ...understanding-vtex-email-capture-system.md |    2 +-
 docs/faq/en/vtex-support-brazil.md            |    4 +-
 docs/faq/en/vtex-support-emea.md              |  227 +++
 .../en/website-with-error-how-to-fix-it.md    |    4 +-
 ...while-selecting-paypal-plus-at-checkout.md |    6 +-
 ...exported-report-does-not-reach-my-email.md |    4 +-
 ...rror-message-during-shipping-simulation.md |    8 +-
 ...n-the-notify-me-option-is-not-displayed.md |    2 +-
 ...ders-not-integrating-with-mercado-livre.md |    2 +-
 ...-images-being-displayed-in-poor-quality.md |   27 +
 ...hy-can-t-i-change-the-fields-in-a-group.md |    8 +-
 .../why-cant-i-see-my-carrier-on-checkout.md  |    8 +-
 ...for-a-weight-lower-than-the-minimum-set.md |    6 +-
 ...nt-my-benefit-work-for-a-client-cluster.md |    2 +-
 ...-benefit-work-for-all-types-of-delivery.md |    2 +-
 docs/faq/en/why-is-let-me-know-not-showing.md |    2 +-
 docs/faq/en/why-is-my-freight-value-wrong.md  |    4 +-
 docs/faq/en/why-is-my-stock-negative.md       |    4 +-
 .../en/why-is-my-stores-zoom-not-working.md   |    2 +-
 ...fferent-on-vtex-and-on-google-analytics.md |    6 +-
 ...-the-product-not-visible-on-the-website.md |   32 +-
 .../why-is-the-thumb-image-of-poor-quality.md |    2 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |    2 +-
 .../why-was-the-item-splitted-in-the-cart.md  |   18 +-
 ...heckout-when-the-purchase-was-concluded.md |    2 +-
 ...he-promotion-applied-to-the-marketplace.md |    2 +-
 ...ations-to-troubleshoot-front-end-issues.md |   12 +-
 ...iliations-that-support-native-split-faq.md |    2 +-
 .../faq/es/fix-redirect-error-in-pagseguro.md |   22 +-
 .../es/how-do-i-find-the-order-nsu-and-tid.md |    2 +-
 docs/faq/es/how-does-vtex-support-work.md     |   20 +-
 ...ciate-two-promotions-to-the-same-coupon.md |    4 +-
 ...nt-edit-a-required-field-on-master-data.md |    6 +-
 ...ecognize-the-reservation-id-of-an-order.md |    6 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |    2 +-
 ...ook-is-not-displayed-in-the-shop-window.md |    2 +-
 .../es/my-admin-is-blocked-what-do-i-do.md    |   13 +-
 ...-in-ready-for-handling-what-should-i-do.md |   30 +
 ...iliations-are-highlighted-in-yellow-why.md |    2 +-
 ...understanding-vtex-email-capture-system.md |    2 +-
 docs/faq/es/vtex-support-brazil.md            |    4 +-
 docs/faq/es/vtex-support-emea.md              |   17 +
 .../es/website-with-error-how-to-fix-it.md    |    4 +-
 ...while-selecting-paypal-plus-at-checkout.md |    6 +-
 ...exported-report-does-not-reach-my-email.md |    4 +-
 ...rror-message-during-shipping-simulation.md |   10 +-
 ...n-the-notify-me-option-is-not-displayed.md |    2 +-
 ...ders-not-integrating-with-mercado-livre.md |    2 +-
 ...-images-being-displayed-in-poor-quality.md |   27 +
 ...hy-can-t-i-change-the-fields-in-a-group.md |    6 +-
 .../why-cant-i-see-my-carrier-on-checkout.md  |    8 +-
 ...for-a-weight-lower-than-the-minimum-set.md |    6 +-
 ...nt-my-benefit-work-for-a-client-cluster.md |    2 +-
 ...-benefit-work-for-all-types-of-delivery.md |    2 +-
 docs/faq/es/why-is-let-me-know-not-showing.md |    2 +-
 docs/faq/es/why-is-my-freight-value-wrong.md  |    4 +-
 docs/faq/es/why-is-my-stock-negative.md       |    4 +-
 .../es/why-is-my-stores-zoom-not-working.md   |    2 +-
 ...fferent-on-vtex-and-on-google-analytics.md |    6 +-
 ...-the-product-not-visible-on-the-website.md |   32 +-
 .../why-is-the-thumb-image-of-poor-quality.md |    2 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |    2 +-
 .../why-was-the-item-splitted-in-the-cart.md  |   16 +-
 ...heckout-when-the-purchase-was-concluded.md |    2 +-
 ...he-promotion-applied-to-the-marketplace.md |    2 +-
 ...ations-to-troubleshoot-front-end-issues.md |    8 +-
 ...iliations-that-support-native-split-faq.md |    2 +-
 .../faq/pt/fix-redirect-error-in-pagseguro.md |   26 +-
 .../pt/how-do-i-find-the-order-nsu-and-tid.md |    2 +-
 docs/faq/pt/how-does-vtex-support-work.md     |   21 +-
 ...ciate-two-promotions-to-the-same-coupon.md |    4 +-
 docs/faq/pt/how-to-edit-a-whatsapp-link.md    |    2 +-
 docs/faq/pt/how-to-find-facebook-pixel.md     |    6 +-
 .../pt/how-to-find-google-analytics-pixel.md  |    6 +-
 .../how-to-find-google-tag-manager-pixel.md   |    4 +-
 ...nt-edit-a-required-field-on-master-data.md |    6 +-
 ...ecognize-the-reservation-id-of-an-order.md |    7 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |    2 +-
 ...ook-is-not-displayed-in-the-shop-window.md |    2 +-
 docs/faq/pt/locate-the-google-ads-pixel.md    |   10 +-
 .../pt/my-admin-is-blocked-what-do-i-do.md    |   14 +-
 ...-in-ready-for-handling-what-should-i-do.md |   30 +
 ...iliations-are-highlighted-in-yellow-why.md |    2 +-
 ...r-when-trying-to-process-sku-suggestion.md |    4 +-
 ...understanding-vtex-email-capture-system.md |    2 +-
 docs/faq/pt/utms.md                           |    4 +-
 docs/faq/pt/vtex-support-brazil.md            |    6 +-
 docs/faq/pt/vtex-support-emea.md              |   17 +
 .../pt/website-with-error-how-to-fix-it.md    |    4 +-
 ...while-selecting-paypal-plus-at-checkout.md |    6 +-
 ...exported-report-does-not-reach-my-email.md |    4 +-
 ...rror-message-during-shipping-simulation.md |    8 +-
 ...n-the-notify-me-option-is-not-displayed.md |    2 +-
 ...ders-not-integrating-with-mercado-livre.md |    2 +-
 ...-images-being-displayed-in-poor-quality.md |   27 +
 ...hy-can-t-i-change-the-fields-in-a-group.md |    8 +-
 .../why-cant-i-see-my-carrier-on-checkout.md  |    8 +-
 ...for-a-weight-lower-than-the-minimum-set.md |    6 +-
 ...nt-my-benefit-work-for-a-client-cluster.md |    2 +-
 ...-benefit-work-for-all-types-of-delivery.md |    2 +-
 docs/faq/pt/why-is-let-me-know-not-showing.md |    2 +-
 docs/faq/pt/why-is-my-freight-value-wrong.md  |    4 +-
 docs/faq/pt/why-is-my-stock-negative.md       |    6 +-
 .../pt/why-is-my-stores-zoom-not-working.md   |    2 +-
 ...fferent-on-vtex-and-on-google-analytics.md |    6 +-
 ...-the-product-not-visible-on-the-website.md |   32 +-
 .../why-is-the-thumb-image-of-poor-quality.md |    2 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |    2 +-
 .../why-was-the-item-splitted-in-the-cart.md  |   18 +-
 ...heckout-when-the-purchase-was-concluded.md |    2 +-
 ...he-promotion-applied-to-the-marketplace.md |    2 +-
 docs/known-issues/en/.md                      |    7 +-
 ...3-error-for-all-urls-containing-develop.md |   47 +
 ...the-activate-if-possible-flag-unchecked.md |   45 +
 ...-be-returned-blank-in-the-catalog-admin.md |   46 +
 ...information-for-sessions-and-conversion.md |   45 +
 ...skuvincularvalorservicoaspx-not-working.md |   29 +-
 ...-not-available-when-creating-dictionary.md |    2 +-
 ...nvoice-address-returns-null-api-results.md |    6 +-
 ...he-shopper-opts-to-insert-a-new-address.md |   52 +
 ...-removing-essential-address-information.md |    6 +-
 ...n-buyer-has-can-add-shipping-permission.md |   48 +
 ...n-impersonated-using-vtex-telemarketing.md |   45 +
 ...auses-invalid-address-for-an-item-error.md |   55 +
 ...rder-has-more-than-one-product-centauro.md |    6 +-
 .../en/admin-collection-brand-list-timeout.md |    6 +-
 ...rch-doesnt-recognize-profile-menu-items.md |   49 +
 ...n-how-to-improve-section-of-the-catalog.md |    4 +-
 ...nsion-as-jpg-even-when-the-image-is-png.md |    6 +-
 ...-engine-redirects-them-to-the-wrong-url.md |   53 +
 .../en/admin-review-global-search.md          |   46 +
 docs/known-issues/en/admin-timeout.md         |   50 +
 ...ut-country-disrupting-orderform-changes.md |    6 +-
 ...-generates-payment-authorization-denial.md |   52 +
 ...ethodtype-for-amex-when-using-apple-pay.md |   45 +
 ...ed-delivery-selection-appears-only-once.md |    6 +-
 ...-showing-in-vtexcmcproductimage-zoomon-.md |    4 +-
 .../en/amazon-category-implementation.md      |    6 +-
 ...e-sending-product-to-amazon-marketplace.md |   49 +
 ...sku-is-not-being-logged-into-the-bridge.md |   50 +
 .../en/amazon-global-category-not-working.md  |    6 +-
 ...n-integration-attribute-number-of-itens.md |    6 +-
 ...integration-stock-reservations-for-kits.md |    6 +-
 .../amazoncasacaso-erros-de-rastreamento.md   |   12 +-
 ...mate-returns-wrong-info-when-sc-is-null.md |    6 +-
 ...ts-does-not-return-additionalinfo-field.md |    6 +-
 ...-are-not-erased-when-you-delete-the-app.md |   60 +
 ...most-expensive-items-ui-not-saving-data.md |   51 +
 ...oved-skus-spreadsheet-not-showing-price.md |    6 +-
 ...t-allow-null-domainvalues-and-it-should.md |   67 +
 ...ation-on-field-domainvalues-not-working.md |    6 +-
 ...g-an-item-from-a-seller-with-attachment.md |   61 +
 ...are-not-updated-when-its-added-to-items.md |   45 +
 ...e-not-being-updated-in-meli-integration.md |   48 +
 ...pricing-logs-showing-unknow-information.md |   46 +
 ...payments-when-the-first-one-is-canceled.md |   43 +
 .../en/auto-approve-api-accepts-any-values.md |    6 +-
 ...ng-suggestion-products-shown-with-delay.md |    6 +-
 ...tocomplete-not-answering-to-cold-starts.md |   11 +-
 ...i-removes-the-dot-from-the-product-name.md |   50 +
 ...culate-during-the-first-hour-of-the-day.md |    2 +-
 ...ic-payment-settlement-incorrectly-setup.md |   57 +
 ...not-occurring-due-to-special-characters.md |   47 +
 ...date-of-deliveries-tracking-by-correios.md |    8 +-
 ...mulation-for-no-stock-or-price-products.md |   49 +
 ...-missing-data-for-newly-created-address.md |   66 +
 ...r-of-routes-created-to-deliver-the-item.md |   43 +
 ...d-data-is-not-removed-after-logging-out.md |   47 +
 ...story-doesnt-work-in-the-website-domain.md |   43 +
 ...ng-geolocation-when-registering-address.md |   45 +
 ...-detail-ui-only-shows-100-first-sellers.md |   53 +
 ...e-doesnt-register-information-in-orders.md |   47 +
 ...count-at-checkout-in-the-website-domain.md |   44 +
 ...e-geocoordinates-to-calculate-region-id.md |   46 +
 ...rect-order-fob-integrating-with-carrier.md |    6 +-
 .../en/b2w-freight-value-in-oms-vtex.md       |    6 +-
 ...n-searching-terms-with-directly-via-url.md |    6 +-
 ...arching-terms-with-through-autocomplete.md |   43 +
 ...-with-a-huge-quantity-of-reserved-items.md |   53 +
 ...ific-scenarios-with-merchandising-rules.md |   46 +
 ...en-the-promotion-is-a-buy-together-type.md |   45 +
 ...form-application-does-not-work-properly.md |   54 +
 ...rties-not-being-validated-on-legacy-cms.md |    6 +-
 ...s-are-not-searchable-on-the-brand-admin.md |   40 +
 ...hanges-to-the-intelligent-search-module.md |    4 +-
 ...cep-not-working-in-create-giftlist-form.md |    6 +-
 ...-mycards-page-not-translated-to-spanish.md |    6 +-
 ...k-on-the-first-try-in-fullcleanup-admin.md |   46 +
 ...oducts-not-to-load-on-the-front-timeout.md |   47 +
 ...figuration-in-organizationscost-centers.md |   45 +
 .../calculation-issue-in-comissionamount.md   |   42 +
 ...s-to-cart-from-store-framework-frontend.md |   47 +
 ...to-retry-payment-which-may-also-deny-it.md |   42 +
 ...rent-from-to-equal-to-with-a-collection.md |   54 +
 ...ormaspx-save-button-requires-two-clicks.md |    6 +-
 ...re-not-applied-after-3rd-category-level.md |   46 +
 ...nt-edit-the-name-of-the-styles-template.md |   43 +
 ...rd-brands-incorrectly-processed-as-visa.md |   42 +
 ...card-facebook-doesnt-save-some-settings.md |    6 +-
 ...order-doesnt-bring-the-assembly-options.md |   47 +
 ...-old-order-doesnt-bring-the-attachments.md |    6 +-
 ...ing-placed-as-expected-in-the-orderform.md |   54 +
 ...sing-sent-by-checkout-in-additionaldata.md |   43 +
 ...re-kept-in-orders-with-total-value-zero.md |   45 +
 ...if-store-cant-ship-to-all-the-countries.md |   45 +
 ...ent-do-not-receive-promotions-correctly.md |   47 +
 ...-not-consider-items-removed-from-orders.md |   51 +
 ...gunit-with-query-parameter-refid-return.md |    6 +-
 ...properly-to-space-at-the-end-of-strings.md |   47 +
 ...export-cannot-handle-t-and-s-characters.md |   47 +
 ...xport-for-attachment-cuts-50-characters.md |   51 +
 .../en/catalog-filters-timeout.md             |   45 +
 ...ql-categoryinputtranslation-not-working.md |   45 +
 ...enerating-invalid-translation-documents.md |   44 +
 ...-report-total-section-calculation-error.md |    6 +-
 ...ion-xml-fiscal-code-field-not-rendering.md |   48 +
 ...alog-search-api-limited-to-2500-results.md |   47 +
 ...rn-information-for-products-unavailable.md |    6 +-
 ...slations-not-reflecting-on-the-frontend.md |   54 +
 .../en/catalogv2-user-roles-not-applying.md   |    6 +-
 ...update-with-values-from-review-skus-tab.md |   49 +
 ...category-score-field-is-not-being-saved.md |    6 +-
 .../centauro-to-implement-centauro-envios.md  |    6 +-
 ...-to-myaccount-instead-of-the-order-page.md |   55 +
 ...-calculation-of-promotions-take-3-pay-2.md |    6 +-
 ...er-using-api-without-email-orderchanged.md |    6 +-
 ...tyles-admin-page-are-not-saved-properly.md |   46 +
 ...ccessories-is-not-triggering-indexation.md |   48 +
 ...-could-make-the-page-not-work-correctly.md |    6 +-
 ...without-shipping-address-on-the-ui-only.md |    6 +-
 ...-add-2-different-addresses-for-delivery.md |   46 +
 ...pty-shippingdata-when-using-geolocation.md |   45 +
 ...as-free-shipping-and-scheduled-delivery.md |    6 +-
 ...at-first-instant-for-specific-condition.md |   19 +-
 ...support-encoding-assembly-options-names.md |   44 +
 ...tly-sending-item-details-to-transaction.md |    6 +-
 ...ct-seller-when-merging-cart-information.md |   44 +
 ...tax-field-for-shipping-percentage-taxes.md |   44 +
 ...e-same-sku-receives-a-logistics-timeout.md |   48 +
 ...ress-for-shoppers-with-complete-profile.md |   47 +
 ...r-items-with-no-common-shipping-methods.md |   49 +
 ...orrect-sla-values-from-logistics-system.md |    8 +-
 ...-hyphen-in-the-postal-code-to-orderform.md |   47 +
 ...-the-user-switches-the-delivery-options.md |   44 +
 ...-there-is-only-pickup-address-available.md |    7 +-
 ...oesnt-handle-multiple-filters-correctly.md |   39 +
 ...ly-sometimes-in-global-checkout-setting.md |   50 +
 ...t-add-client-profile-is-performed-twice.md |   44 +
 ...with-the-same-names-as-the-default-ones.md |    6 +-
 ...is-not-accessible-through-the-new-admin.md |    2 +-
 .../en/cms-legacy-collections-timeout.md      |   26 +-
 ...oving-value-from-the-unit-of-mass-field.md |    6 +-
 ...s-settings-role-not-working-as-expected.md |   54 +
 ...ble-menu-issues-rendering-all-the-items.md |    6 +-
 ...ot-allow-more-than-1000-skus-per-upload.md |    4 +-
 ...ustom-search-results-pages-in-b2b-suite.md |   47 +
 .../collections-dont-open-on-subaccounts.md   |   44 +
 ...-only-shows-1st-sku-of-inactive-product.md |   46 +
 ...-equal-to-on-the-campaign-audience-form.md |    6 +-
 ...h-special-characters-cannot-be-exported.md |   45 +
 ...ation-details-shows-only-20-collections.md |   52 +
 ...ng-as-expected-on-progressive-discounts.md |   48 +
 ...eation-due-to-failure-in-gatewaycallbak.md |   17 +-
 ...n-implemented-in-productsummary-for-ios.md |    4 +-
 ...nconsistency-in-deliveryshipping-prices.md |    6 +-
 ...components-in-a-kit-with-the-same-price.md |   46 +
 .../confirmed-order-email-not-being-sent.md   |    4 +-
 ...the-same-name-at-the-intelligent-search.md |   50 +
 ...violates-the-following-content-security.md |   51 +
 .../en/cookie-broken-the-apisessions.md       |    4 +-
 ...-only-25-options-in-b2b-admin-customers.md |   46 +
 .../country-field-as-null-in-invoicedata.md   |   44 +
 ...ys-restricted-to-the-delivery-countries.md |    6 +-
 ...oupons-created-as-archived-temporarrily.md |   47 +
 ...oesnt-send-nulls-as-release-date-values.md |   45 +
 ...-does-not-update-the-items-stockbalance.md |   47 +
 ...-of-redirects-breaks-the-redirects-page.md |   48 +
 ...-of-the-csv-through-the-cli-doesnt-work.md |   47 +
 ...not-returned-on-the-explained-search-ui.md |   43 +
 .../crm-error-when-searching-with-spaces.md   |    4 +-
 ...y-symbol-does-not-follow-admin-language.md |   47 +
 .../custom-attribute-mapper-mercado-livre.md  |   44 +
 ...cms-not-working-with-more-than-one-html.md |   46 +
 ...mage-is-not-displayed-on-mobile-version.md |    6 +-
 ...tatus-at-mycredits-page-are-not-correct.md |    6 +-
 ...s-some-order-with-profileerroronloading.md |   43 +
 ...tion-is-not-saved-in-the-profile-system.md |    6 +-
 ...ipping-promotion-default-saleschannel-1.md |    6 +-
 ...v-without-validation-of-characters-type.md |    6 +-
 ...ed-payment-system-rendering-at-checkout.md |   42 +
 ...eadlocked-error-when-using-catalog-apis.md |   47 +
 ...-an-error-in-the-transactionstate-field.md |   25 +-
 ...-checkout-if-not-deactivated-previously.md |   42 +
 ...e-is-space-in-the-id-of-shipping-policy.md |   46 +
 ...with-lean-shipping-offering-invalid-sla.md |   49 +
 ...ing-on-seller-management-commissions-ui.md |   47 +
 .../diacritics-are-removed-on-catalogapi.md   |    6 +-
 ...rices-between-pdp-plp-and-checkout-cart.md |   47 +
 ...-specification-value-on-apis-and-portal.md |   50 +
 ...perly-when-prop-animated-is-set-as-true.md |    6 +-
 ...oupon-usage-count-on-oms-and-coupons-ui.md |   44 +
 ...al-order-value-and-total-products-value.md |    2 +-
 ...-settings-on-new-accounts-or-workspaces.md |   47 +
 ...transaction-list-and-on-the-transaction.md |   11 +-
 ...domly-getting-last-digit-deleted-on-ios.md |   46 +
 ...sspecification-values-on-the-same-level.md |    6 +-
 ...n-modal-to-switch-between-organizations.md |   46 +
 ...-ignored-when-approved-on-received-skus.md |   46 +
 ...th-automatic-capture-on-authorizedotnet.md |   56 +
 ...derest-are-not-respecting-early-capture.md |    6 +-
 ...filling-for-new-buyers-after-logging-in.md |   46 +
 ...autofilling-for-new-users-on-checkoutui.md |   60 +
 ...ate-using-the-b2b-organizations-feature.md |   44 +
 .../en/encoding-error-in-apple-mail-app.md    |    2 +-
 ...ters-leads-to-unexpected-product-search.md |   47 +
 ...re-specific-global-category-persistente.md |    6 +-
 ...e-rejected-or-reviewed-by-offer-quality.md |   52 +
 ...ror-cancelling-customer-credit-invoices.md |   44 +
 ...a-promotion-excluding-more-than-1-brand.md |    6 +-
 .../error-closing-customer-credit-account.md  |   44 +
 ...xporting-entity-with-too-many-documents.md |   47 +
 ...ror-exporting-large-amount-of-giftcards.md |   19 +-
 .../error-exporting-prices-with-metadata.md   |   48 +
 .../en/error-in-checkout-error-message.md     |    6 +-
 .../en/error-in-custom-payments-creation.md   |   43 +
 ...ients-is-different-than-operation-value.md |   46 +
 ...lue-cannot-be-null-parameter-name-value.md |   46 +
 ...-cancelation-when-the-returncode-is-359.md |   46 +
 ...ui-after-requesting-the-invoice-via-app.md |   58 +
 ...trying-to-access-catalog-pages-on-admin.md |   47 +
 ...-sku-is-binded-on-vtexvtex-integrations.md |    6 +-
 ...-search-using-the-all-field-in-vtex-crm.md |   46 +
 .../en/error-on-duplicate-payment-method.md   |   50 +
 ...-sellers-to-marketplaces-and-vice-versa.md |    2 +-
 ...gain-when-adding-images-via-site-editor.md |   47 +
 .../en/error-sww-on-product-pdp.md            |   16 +-
 ...al-connector-for-pending-payment-status.md |    6 +-
 ...ng-an-index-if-the-fields-are-identical.md |   43 +
 ...delivery-type-when-seller-has-recursion.md |    6 +-
 ...-publishing-dynamic-storage-data-entity.md |   58 +
 ...en-running-vtex-link-for-the-first-time.md |    2 +-
 ...-transaction-with-2-cards-mercadopagov1.md |    6 +-
 ...r-when-trying-to-publish-or-link-an-app.md |   46 +
 docs/known-issues/en/event-inconsistency.md   |   20 +-
 ...be-returned-once-the-order-has-a-change.md |    6 +-
 ...de-products-from-collection-not-working.md |   48 +
 ...edirects-not-pointing-back-to-old-route.md |   47 +
 ...xts-between-different-areas-or-products.md |   42 +
 ...sometimes-the-request-can-not-completed.md |   38 +
 ...xport-redirects-not-working-as-intended.md |   26 +-
 ...the-csv-in-the-sales-performance-module.md |    8 +-
 ...his-character-cut-in-the-image-url-rows.md |   48 +
 ...pdate-the-price-in-the-facebook-catalog.md |   50 +
 ...rumbs-page-title-and-additional-filters.md |   48 +
 ...ancellation-ppp-when-cancellationidnull.md |    6 +-
 ...s-the-go-to-payment-button-to-disappear.md |   45 +
 ...ststore-cart-merges-assembly-line-items.md |   43 +
 ...ng-not-removing-facets-set-to-ne-hidden.md |   48 +
 ...pi-considering-fuzzy-as-auto-as-default.md |   43 +
 ...return-seo-information-on-graphql-query.md |   46 +
 ...page-status-and-crashing-the-pagination.md |    6 +-
 ...n-trade-policy-not-reflecting-on-pdpplp.md |    6 +-
 ...ting-on-seller-management-ui-after-save.md |   18 +-
 ...any-change-in-order-management-settings.md |   10 +-
 ...not-update-all-the-files-only-the-first.md |    8 +-
 ...-performance-is-not-accepting-uppercase.md |    6 +-
 ...names-while-applying-additional-filters.md |   44 +
 ...t-considering-regionalized-availability.md |   49 +
 ...den-from-intelligent-search-admin-pages.md |   38 +
 ...to-old-component-version-on-site-editor.md |   45 +
 ...ll-the-profileshipping-data-at-checkout.md |   45 +
 ...orporatedocument-if-starts-with-letters.md |   44 +
 .../en/first-subscription-cycle-is-skipped.md |   49 +
 ...rade-policy-1-when-saving-bundle-prices.md |    6 +-
 ...ace-integrate-an-order-erro-code-fmt010.md |    6 +-
 ...it-orders-outside-promotion-restriction.md |    6 +-
 ...-has-seller-groups-on-seller-management.md |   48 +
 ...egory-tree-on-itemcategory-in-datalayer.md |   44 +
 ...a-cant-be-informed-for-some-cultureinfo.md |    6 +-
 ...-for-pickup-points-loading-indefinitely.md |    2 +-
 ...eep-same-sku-order-when-changing-limits.md |    6 +-
 ...ist-multiple-orders-for-the-same-coupon.md |   46 +
 ...ed-offers-list-api-not-working-properly.md |    6 +-
 ...-by-refid-returning-null-when-not-found.md |    6 +-
 ...sku-by-ean-api-returns-only-active-skus.md |    6 +-
 ...from-component-sku-and-not-from-kit-sku.md |    6 +-
 .../en/gift-card-creation-error-via-admin.md  |   47 +
 ...ith-the-date-chosen-when-it-was-created.md |    6 +-
 ...ty-id-in-response-to-create-transaction.md |   43 +
 ...-extra-backslash-when-calling-providers.md |    6 +-
 ...relationname-when-we-make-a-get-request.md |   43 +
 ...-a-generic-exception-if-it-has-no-price.md |    6 +-
 ...n-acting-alongside-other-gift-promotion.md |    6 +-
 ...add-credit-to-the-gift-card-through-api.md |    6 +-
 ...a-na-ui-nao-e-a-mesma-que-reflete-no-bd.md |    6 +-
 ...-in-catalog-outdated-compared-to-google.md |    6 +-
 ...onent-iframe-has-inconsistent-rendering.md |   46 +
 ...les-performance-not-working-as-expected.md |    6 +-
 ...s-cms-ignores-array-validation-settings.md |   48 +
 ...ng-do-not-work-on-seller-portal-catalog.md |   47 +
 ...ignored-after-one-purchase-is-completed.md |   48 +
 ...idget-not-shown-if-showmodal-is-enabled.md |   44 +
 ...oducts-if-import-is-made-based-on-skuid.md |   49 +
 ...-items-to-invoice-field-in-the-order-ui.md |   45 +
 ...e-tax-values-in-the-ui-appear-the-total.md |    6 +-
 ...partial-cancellation-with-mercadopagov1.md |    6 +-
 ...paypal-credentials-for-the-same-account.md |   17 +-
 ...tions-appearing-with-brazilian-currency.md |   45 +
 ...items-with-assembly-options-in-the-cart.md |    2 +-
 ...-organization-and-b2b-checkout-settings.md |   45 +
 ...ku-has-unit-multiplier-different-than-1.md |   23 +-
 .../en/incorrect-currency-on-payment-form.md  |    6 +-
 ...iscount-to-all-the-same-items-in-a-cart.md |   50 +
 ...ients-is-different-than-operation-value.md |   52 +
 ...rect-shippingestimatedate-for-order-fob.md |    6 +-
 ...e-registered-on-the-fulfillmentendpoint.md |   48 +
 .../en/incorrectly-updated-inventory.md       |    6 +-
 ...the-highest-instead-of-the-lowest-price.md |    6 +-
 ...s-do-not-work-on-seller-portal-accounts.md |    6 +-
 ...are-same-skuid-in-different-array-items.md |   50 +
 .../en/infocard-mobile-images-wont-apply.md   |   47 +
 ...s-from-servers-that-require-user-agents.md |   50 +
 ...ns-not-updating-automatically-on-pdpplp.md |   46 +
 ...e-via-image-url-does-not-work-correctly.md |    8 +-
 ...s-not-in-sync-with-store-configurations.md |   64 +
 ...ot-capturing-sales-events-for-faststore.md |   42 +
 ...t-settings-search-bar-is-case-sensitive.md |   41 +
 ...-normalizing-gender-in-portuguese-words.md |   47 +
 ...tate-changes-the-address-insertion-mode.md |   46 +
 ...ng-state-sends-the-wrong-payment-option.md |   45 +
 .../intermitent-site-editor-content-loss.md   |   49 +
 .../internalsearcherror-timeouts-on-portal.md |   45 +
 ...ilable-addresses-with-different-country.md |   47 +
 ...ory-notifications-to-indexer-are-cached.md |   52 +
 .../en/inventory-reserved-items-error.md      |   18 +-
 ...egory-names-cause-page-not-found-errors.md |   46 +
 ...-not-work-as-expected-on-the-search-api.md |    6 +-
 ...d-search-for-searches-with-accent-marks.md |    6 +-
 ...e-on-translating-titles-for-some-facets.md |   12 +-
 ...operties-beginning-with-the-same-prefix.md |   43 +
 ...values-in-loyalty-gift-card-at-checkout.md |   44 +
 ...ss-leading-to-transaction-cancellations.md |   48 +
 .../en/issues-with-my-account-links.md        |   45 +
 ...his-item-without-attachment-in-the-cart.md |   51 +
 ...create-a-path-using-content-type-via-ui.md |   47 +
 ...shown-in-seller-whitelabel-change-order.md |   46 +
 ...r-location-is-not-defined-with-no-stock.md |   47 +
 ...f-add-to-cart-event-in-google-analytics.md |   46 +
 ...-promotions-with-collections-associated.md |   52 +
 ...api-is-not-calculating-component-prices.md |   10 +-
 ...ight-can-be-overritten-by-apiwebservice.md |    6 +-
 ...a-request-when-the-accountid-is-missing.md |   19 +-
 ...eadsheet-error-on-new-collections-admin.md |   21 +-
 ...same-slas-but-in-a-different-ordination.md |   19 +-
 ...went-wrong-after-changing-pickup-points.md |   49 +
 ...activate-after-removing-items-from-cart.md |   46 +
 ...catalog-ui-delete-button-not-functional.md |   49 +
 ...-cmss-banner-custom-element-not-working.md |   54 +
 ...ting-products-wrongly-to-the-collection.md |    6 +-
 ...ntrols-do-not-consider-unit-multipliers.md |   48 +
 ...ntroller-texts-are-not-being-translated.md |    6 +-
 ...eadsheet-only-returning-active-services.md |   48 +
 ...y-setup-only-works-opening-in-a-new-tab.md |    6 +-
 ...r-when-translating-with-catalog-graphql.md |   89 ++
 ...tcher-doesnt-work-in-myvtex-environment.md |    4 +-
 ...with-password-cannot-be-undone-in-admin.md |   54 +
 ...es-not-work-when-productprice-as-0-zero.md |    6 +-
 ...yment-condition-requires-authentication.md |    4 +-
 ...specifications-from-another-marketplace.md |    6 +-
 ...marketplace-didnt-update-status-on-vtex.md |   47 +
 ...ine-luiza-some-skus-do-not-update-price.md |   53 +
 ...-deve-ser-igual-ou-menor-a-data-de-hoje.md |   50 +
 .../mandatory-service-working-as-optional.md  |   46 +
 ...using-multiple-coupons-feature-and-utms.md |   45 +
 ...value-when-campaign-audience-is-matched.md |   45 +
 ...lues-due-to-certain-purchase-conditions.md |   49 +
 ...snt-consider-manual-price-for-discounts.md |   45 +
 ...est-doesnt-consider-some-discount-types.md |   44 +
 ...ransactions-are-being-processed-as-visa.md |   43 +
 ...erdata-export-download-link-unavailable.md |    6 +-
 ...ved-skus-api-returning-invalid-sellerid.md |   52 +
 ...ng-height-width-weight-and-length-to-01.md |   48 +
 ...uctsku-name-contains-special-characters.md |   46 +
 ...hipping-discount-not-updating-pricetags.md |   47 +
 ...rrect-discount-when-using-the-same-item.md |   67 +
 ...cannot-be-changed-by-franchise-accounts.md |   45 +
 ...t-passing-a-symbol-or-special-character.md |   44 +
 ...o-meli-without-being-mapped-from-seller.md |   50 +
 ...ntegration-with-a-non-expected-behavior.md |    6 +-
 ...tomatic-messages-mercado-livre-messages.md |    8 +-
 ...enu-not-showing-the-orderid-information.md |   45 +
 ...aused-when-the-marketplace-ad-is-paused.md |   45 +
 ...-error-while-sending-the-order-tracking.md |    6 +-
 ...quotation-for-multiple-officialstoreids.md |   44 +
 ...ull-orders-not-creating-invoice-in-vtex.md |   45 +
 ...ct-value-when-client-has-coupon-on-meli.md |   46 +
 ...-errors-from-meli-429-too-many-requests.md |   51 +
 ...-for-peru-venezuela-equador-and-uruguai.md |   45 +
 ...ntegration-zipcodes-11111-meli-limaperu.md |    6 +-
 ...ding-product-specification-as-variation.md |   44 +
 ...tex-oms-for-multiples-accounts-scenario.md |   46 +
 ...hart-not-working-for-sizes-with-letters.md |   50 +
 ...eli-sizechart-issue-attribute-not-valid.md |   45 +
 .../en/meli-update-stockprice-issue.md        |   45 +
 ...ybox-doesnt-update-shippingmode-for-me2.md |   55 +
 ...bridge-isnt-logging-some-error-messages.md |   50 +
 ...-not-showing-the-shippingid-information.md |   47 +
 .../en/mercado-livre-mapper-attribute-size.md |   14 +-
 ...ve-underreview-validation-in-update-sku.md |   43 +
 ...bridge-isnt-logging-some-error-messages.md |   44 +
 ...working-for-the-facet-productclusterids.md |   50 +
 ...for-some-clients-in-customer-credit-api.md |   51 +
 ...ing-too-long-to-return-the-informations.md |   40 +
 ...n-field-cannot-be-deleted-through-admin.md |   47 +
 ...messages-only-appear-after-a-second-try.md |   49 +
 ...does-not-show-sku-specs-in-b2b-scenario.md |    6 +-
 ...sending-options-for-already-added-items.md |    6 +-
 ...-app-breaks-other-apps-of-the-same-type.md |    4 +-
 ...causes-antifraud-to-cancel-transactions.md |    6 +-
 ...price-facetfilter-at-intelligent-search.md |   44 +
 ...en-this-type-of-modal-are-configured-ok.md |    6 +-
 ...cated-divergences-setup-shipping-policy.md |    6 +-
 .../multiple-sku-promotion-api-not-working.md |    6 +-
 ...shivering-when-trying-to-add-a-new-card.md |   46 +
 ...field-filled-in-the-address-information.md |    6 +-
 ...tion-is-associated-with-a-pick-up-point.md |    4 +-
 ...-the-address-line-2-this-appear-as-null.md |    6 +-
 ...-spinner-button-is-not-working-properly.md |    4 +-
 ...hen-accessing-from-an-dependent-account.md |    6 +-
 ...eased-filter-is-not-working-for-exports.md |    2 -
 ...e-customers-id-document-for-example-cpf.md |    6 +-
 ...the-invoiced-value-on-return-items-page.md |    6 +-
 ...acters-and-causes-problem-in-order-flow.md |    2 +-
 ...e-and-lastdeliveryday-for-high-timecost.md |   71 +
 ...as-expected-with-subtraction-operations.md |   51 +
 ...distributed-among-all-items-in-the-cart.md |   22 +-
 ...plit-for-second-item-incorrect-discount.md |   63 +
 ...proper-detached-sku-on-pdp-in-a-new-tab.md |   46 +
 ...when-entity-has-more-than-10k-documents.md |    6 +-
 ...upted-file-when-there-are-no-skus-found.md |   46 +
 ...r-does-not-correspond-to-correct-number.md |    6 +-
 ...t-first-informs-an-address-for-delivery.md |   49 +
 ...pears-even-after-filled-until-save-data.md |   43 +
 ...er-only-captures-the-information-of-the.md |    6 +-
 ...bypricedesc-could-bring-the-wrong-order.md |   53 +
 ...dal-hook-affects-all-modals-on-the-page.md |   46 +
 ...orrectly-due-to-null-documenttype-field.md |   47 +
 ...ain-from-b2b-orders-history-doesnt-work.md |    6 +-
 ...ization-lessthan-100-goes-with-the-flow.md |   50 +
 ...r-card-info-causing-confusing-on-status.md |    6 +-
 ...o-price-divergence-on-fulfillment-layer.md |    6 +-
 ...erly-due-double-space-on-promotion-name.md |   21 +-
 ...uotes-in-the-promotion-name-or-sku-name.md |   55 +
 ...carrier-leaves-label-barcode-incomplete.md |   43 +
 ...-triggered-the-transaction-total-refund.md |    6 +-
 ...-and-original-order-have-the-same-value.md |   45 +
 ...nses-field-from-get-payment-details-api.md |   51 +
 ...ler-status-cancellationrequestdeniedffm.md |   54 +
 ...o-missing-payment-approved-notification.md |   48 +
 ...-the-items-and-refund-the-total-payment.md |   49 +
 ...-conectors-like-payment-app-or-redirect.md |    6 +-
 ...eled-but-the-payment-remains-authorized.md |   12 +-
 ...r-the-same-item-under-different-sellers.md |    6 +-
 ...id-scheduled-delivery-that-cant-be-used.md |   31 +-
 ...rs-data-even-for-authorized-credentials.md |    6 +-
 ...form-not-updating-after-order-is-placed.md |   49 +
 ...of-delivery-times-scheduled-at-checkout.md |    2 +-
 ...ps-from-the-root-category-does-not-work.md |    6 +-
 ...hat-dont-update-the-invoice-at-netshoes.md |    6 +-
 ...oice-value-in-output-invoice-validation.md |   51 +
 ...th-asterisks-in-the-address-and-profile.md |   51 +
 ...aceitems-is-not-opening-on-new-ui-admin.md |   20 +-
 ...nvoiceaddress-created-through-native-ui.md |   11 +-
 ...hen-uploading-a-new-version-not-working.md |    6 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   48 +
 ...n-performing-2-product-changes-in-a-row.md |   49 +
 ...-is-causing-us-to-misidentify-some-bins.md |    9 +-
 .../outdated-url-on-the-update-binding-ui.md  |   50 +
 ...iggered-twice-when-accessing-my-account.md |   44 +
 ...being-duplicated-in-custom-search-pages.md |   59 +
 ...h-results-not-working-on-giftlist-pages.md |    6 +-
 ...esnt-reset-when-changing-search-context.md |   50 +
 ...-cart-sometimes-returns-null-api-result.md |   19 +-
 ...cessing-transactions-as-prepaid-in-full.md |   46 +
 ...-with-swl-when-using-identical-typesids.md |    6 +-
 ...t-differ-from-active-payment-conditions.md |    4 +-
 ...ot-applied-in-the-b2b-checkout-settings.md |   63 +
 ...-assigned-after-approving-organizations.md |   48 +
 ...rice-comes-exclusively-from-manualprice.md |   46 +
 ...er-for-multilevel-omnichannel-inventory.md |    6 +-
 ...-respect-the-minimum-installment-amount.md |    6 +-
 ...kup-point-disregarded-based-on-priority.md |    8 +-
 ...eocoordinates-without-a-google-maps-key.md |   49 +
 ...ble-for-selection-in-shipping-policy-ui.md |    4 +-
 ...d-in-the-shipping-policy-after-deletion.md |   43 +
 ...d-after-searching-addresses-in-map-mode.md |    6 +-
 ...ickup-points-not-indexed-in-master-data.md |   47 +
 ...-same-id-pattern-show-product-available.md |   46 +
 ...the-same-cart-are-not-working-correctly.md |   47 +
 ...address-options-for-recurring-customers.md |   56 +
 ...-cookies-when-client-logout-at-checkout.md |   12 +-
 ...ging-out-when-using-callcenter-operator.md |    4 +-
 ...ssing-the-url-with-pagination-parameter.md |    6 +-
 ...-notification-in-the-ui-api-and-gateway.md |   43 +
 ...he-legacy-cms-collection-is-not-working.md |   49 +
 ...-of-spot-price-instead-of-regular-price.md |   52 +
 ...doesnt-correspond-to-the-search-results.md |   43 +
 .../en/price-range-disregards-sales-policy.md |   26 +-
 ...-minimum-value-after-selecting-a-filter.md |   50 +
 ...-twice-and-one-is-from-assembly-options.md |   49 +
 ...-updates-with-cache-on-end-applications.md |   49 +
 ...-to-int32-max-value-on-change-price-api.md |   42 +
 ...ducts-keyword-not-considering-stopwords.md |   44 +
 ...-value-field-when-buying-with-two-cards.md |    6 +-
 ...with-phone-validation-on-mobile-devices.md |   46 +
 ...ayed-when-using-multiple-sales-channels.md |   69 +
 ...ed-in-the-pickups-in-cart-display-modal.md |    6 +-
 ...product-comissioning-inconsistent-cache.md |   60 +
 ...on-admin-changes-with-more-than-70-skus.md |   49 +
 ...date-api-allows-n-in-the-textlink-field.md |    6 +-
 ...m-doesnt-work-on-catalogs-redesigned-ui.md |   46 +
 ...ku-name-when-the-product-has-only-1-sku.md |    6 +-
 .../en/product-page-sessions-not-working.md   |   43 +
 ...e-not-considering-default-seller-in-pdp.md |    6 +-
 ...r-not-working-on-seller-portal-accounts.md |    6 +-
 ...specification-export-index-out-of-range.md |   13 +-
 ...ection-module-assuming-incorrect-values.md |   46 +
 ...tion-module-does-not-list-root-category.md |   45 +
 ...oes-not-trigger-the-products-indexation.md |   46 +
 ...chresolver-is-incorrect-due-to-rounding.md |    6 +-
 ...d-when-the-productname-contains-numbers.md |    6 +-
 ...flag-and-discount-after-promotion-ended.md |   42 +
 ...wn-as-unavailable-at-intelligent-search.md |   42 +
 ...ted-with-duplicated-skus-on-the-catalog.md |   48 +
 ...ed-as-with-promotion-for-search-filters.md |   45 +
 ...sellers-are-appearing-in-the-end-of-plp.md |    6 +-
 ...form-allows-utf16-format-uploaddownload.md |    6 +-
 ...productsskus-import-does-not-support-lb.md |    6 +-
 ...complete-profile-with-ignoreprofiledata.md |   47 +
 ...ed-after-adding-client-preferences-data.md |   46 +
 ...equency-not-working-on-recurring-cycles.md |   44 +
 ...t-performance-or-lead-to-timeout-errors.md |   52 +
 ...hod-doesnt-works-for-whitelabel-sellers.md |   44 +
 ...thods-do-not-appear-on-the-product-page.md |    6 +-
 .../en/promotions-microrounding-divergence.md |   95 ++
 ...-sorting-filtering-by-price-or-discount.md |   39 +
 ...s-ui-loading-wrong-currency-information.md |   13 +-
 ...ty-blockclass-from-infocard-not-working.md |    6 +-
 ...t-split-items-and-free-shipping-applied.md |   44 +
 ...-is-shown-in-the-license-manager-module.md |    6 +-
 ...ly-when-2-categories-have-the-same-name.md |    6 +-
 ...nd-is-stuck-on-freight-type-has-changed.md |   45 +
 .../put-price-overwrites-kit-price-logic.md   |   27 +-
 ...he-limit-value-when-user-quickly-clicks.md |    6 +-
 ...-wont-let-me-change-the-value-by-typing.md |   48 +
 ...h-after-reaching-max-available-qunatity.md |    6 +-
 ...-to-the-searched-zip-codes-availability.md |    2 +-
 ...n-the-sku-is-sold-by-more-than-1-seller.md |    6 +-
 ...ter-do-not-work-with-special-characters.md |   49 +
 ...ceived-skus-review-tab-missing-products.md |   51 +
 ...irects-are-being-counted-multiple-times.md |   48 +
 ...inks-when-using-in-the-final-of-the-url.md |   44 +
 ...avior-not-consistent-between-api-and-ui.md |   47 +
 ...es-us-to-misidentify-mastercard-as-visa.md |   49 +
 ...on-api-returns-seller-list-due-to-cache.md |   45 +
 ...-while-requesting-nonwhitelabel-sellers.md |    6 +-
 ...delivery-to-pickup-on-the-checkout-page.md |   47 +
 ...is-not-inactivating-skus-without-refids.md |    6 +-
 .../render-component-issues-on-site-editor.md |   19 +-
 ...ing-orders-with-different-sales-channel.md |   45 +
 .../en/replicated-pending-payment-emails.md   |    6 +-
 ...g-is-inconsistent-when-running-ab-tests.md |   38 +
 .../en/reserved-stock-in-invoiced-orders.md   |    6 +-
 ...queid-arrays-it-is-not-visible-properly.md |   43 +
 ...ve-a-different-value-added-to-gift-card.md |   12 +-
 .../rewriter-is-not-receiving-url-updates.md  |   59 +
 ...-items-with-unitmultiplier-other-than-1.md |   54 +
 ...terms-of-quantity-of-packages-and-items.md |   44 +
 ...-assigned-after-approving-organizations.md |   51 +
 ...ailing-for-custom-types-in-headless-cms.md |   49 +
 ...e-when-zooming-after-search-page-render.md |   47 +
 ...en-theres-a-slider-layout-on-background.md |   48 +
 .../en/search-analytics-duplicated-events.md  |   60 +
 ...een-versions-withwithout-funnel-metrics.md |   46 +
 ...-skus-for-fqspecificationfilter-queries.md |    6 +-
 ...login-in-using-the-call-center-operator.md |    6 +-
 ...rl-after-navigating-through-suggestions.md |   42 +
 ...the-operator-and-for-trigger-conditions.md |   52 +
 ...rch-by-ean-not-working-on-received-skus.md |   18 +-
 ...account-management-when-using-b2b-suite.md |   54 +
 ...-price-range-yielding-incorrect-results.md |    6 +-
 ...lations-over-already-translated-content.md |   50 +
 ...t-when-the-value-contains-a-plus-symbol.md |   62 +
 ...-updated-only-after-refreshing-the-page.md |    4 +-
 ...sion-updates-does-not-index-binded-skus.md |   53 +
 ...-creation-does-not-add-selected-sellers.md |   51 +
 ...price-condition-not-working-as-expected.md |   47 +
 ...-specifications-dropdown-malfunctioning.md |    6 +-
 ...s-to-reindex-when-inactivating-a-seller.md |   45 +
 ...ced-with-problem-in-the-payment-capture.md |   62 +
 ...ype-name-field-wrongly-returned-via-api.md |   45 +
 ...ces-are-not-updated-when-added-to-items.md |    4 +-
 ...hen-they-are-not-in-the-same-path-level.md |   46 +
 ...esnt-update-expiration-period-of-quotes.md |   53 +
 ...-frozen-when-trying-to-select-an-option.md |   46 +
 ...layed-as-active-in-the-new-logistics-ui.md |   46 +
 ...deliver-on-weekends-is-being-considered.md |    6 +-
 ...es-not-show-message-error-on-simulation.md |    6 +-
 ...does-not-use-sla-name-for-display-in-ui.md |    6 +-
 ...s-package-split-for-pickup-and-shipping.md |   45 +
 ...ng-the-date-when-its-scheduled-delivery.md |    6 +-
 ...g-the-price-when-its-scheduled-delivery.md |    6 +-
 ...s-postal-code-input-field-is-not-hidden.md |    6 +-
 ...rent-slas-causing-divergence-in-tax-hub.md |   44 +
 ...for-some-countries-united-arab-emirates.md |   56 +
 ...pee-failed-to-create-product-variations.md |    6 +-
 ...oducts-ui-brokes-with-too-many-products.md |   49 +
 ...-catalog-v2-on-shipping-simulation-page.md |    6 +-
 ...nt-condition-does-not-appear-at-chekout.md |   48 +
 ...low-changes-on-the-conditional-template.md |   46 +
 ...rsion-when-accessing-via-ipad-on-safari.md |    6 +-
 .../en/sitemap-isnt-being-generatedupdated.md |   75 +
 ...eference-code-longer-than-50-characters.md |   49 +
 ...after-throttling-on-marketplace-catalog.md |   44 +
 ...e-update-does-not-update-v-version-tags.md |   49 +
 ...s-not-responding-with-the-text-property.md |   47 +
 ...c-is-not-being-disable-in-amazon-portal.md |    6 +-
 ...splay-mode-select-not-working-in-shelfs.md |    6 +-
 ...ving-similar-variations-with-substrings.md |   52 +
 .../en/sku-selector-with-multilpe-contexts.md |   49 +
 ...s-only-available-in-a-whitelabel-seller.md |    6 +-
 ...-accounts-with-autoapprove-flag-enabled.md |    6 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   54 +
 ...-value-tables-at-first-for-a-value-type.md |    6 +-
 ...o-cache-in-estimated-date-of-30-seconds.md |   48 +
 ...using-prop-infinite-as-always-on-mobile.md |   46 +
 ...talog-facets-api-have-different-formats.md |   54 +
 ...ail-template-redirects-user-to-404-page.md |   46 +
 ...-are-not-able-to-be-saved-on-my-account.md |    9 +-
 ...cted-when-viewed-through-safari-browser.md |   45 +
 ...king-properly-on-seller-portal-accounts.md |   50 +
 ...ipped-from-product-searches-or-indexing.md |   52 +
 .../some-unexpected-behavior-in-masterdata.md |   48 +
 ...error-is-displayed-in-the-catalog-admin.md |   49 +
 ...cessing-a-and-p-routes-in-portal-stores.md |   48 +
 ...incomplete-address-and-tried-to-edit-it.md |   47 +
 ...rent-on-stores-integrated-before-a-date.md |    6 +-
 ...fects-address-field-display-at-checkout.md |   45 +
 ...ses-internal-logistics-requests-to-fail.md |    6 +-
 ...t-be-used-for-cnpj-search-on-masterdata.md |    4 +-
 ...enumber-cause-postpurchase-flow-to-fail.md |   49 +
 ...or-radio-box-category-type-of-selection.md |    6 +-
 .../specifications-multiplied-on-catalog.md   |   52 +
 ...rect-for-products-with-multiple-sellers.md |    6 +-
 ...sactions-list-doesnt-match-actual-state.md |   43 +
 ...ompleted-even-after-receiving-error-500.md |    8 +-
 ...ows-invalid-commercial-condition-values.md |    6 +-
 ...ingunitbyean-returns-404-for-eans-with-.md |    4 +-
 ...-method-allows-to-insert-existent-refid.md |    6 +-
 ...ssions-considers-inactive-organizations.md |   45 +
 .../stucked-not-found-routes-on-platform.md   |    4 +-
 ...not-show-active-subscriptions-correctly.md |    6 +-
 ...subscription-event-history-out-of-order.md |   48 +
 ...-dashboard-with-conflicting-information.md |    6 +-
 ...ing-failure-or-masterdata-query-failure.md |   45 +
 ...ckuppointid-contains-special-characters.md |   45 +
 ...th-less-than-3-characters-does-not-work.md |    6 +-
 ...via-update-selected-address-information.md |   47 +
 ...-revert-the-zoom-causing-display-issues.md |   45 +
 ...senting-success-even-for-failed-actions.md |   42 +
 ...onyms-not-shown-in-the-explained-search.md |   42 +
 ...idering-seller-1-for-rule-sellers-limit.md |    6 +-
 ...ometimes-appear-on-list-format-plp-view.md |   46 +
 ...s-not-displayng-marketing-tags-dropdown.md |   48 +
 ...-discounts-when-manual-price-is-applied.md |   44 +
 ...re-than-once-when-using-assembly-option.md |   45 +
 ...otions-with-promotion-that-splits-items.md |   46 +
 ...-nominal-promotions-when-placing-orders.md |   45 +
 ...en-when-a-cart-has-two-selected-address.md |   44 +
 ...document-data-instead-of-customer-email.md |    6 +-
 ...nt-accept-special-characters-aside-from.md |   50 +
 ...-not-being-translated-using-site-editor.md |   50 +
 ...-not-being-translated-using-site-editor.md |   52 +
 ...-not-being-translated-using-site-editor.md |   53 +
 ...-marketplace-upon-approvals-reoccurence.md |   15 +-
 ...n-address-editing-on-romania-my-account.md |   12 +-
 ...-list-after-using-the-api-to-create-put.md |    6 +-
 ...lace-is-always-done-with-saleschannel-1.md |    6 +-
 ...-asynchronously-denying-payment-capture.md |   43 +
 ...s-not-work-with-save-card-functionality.md |   51 +
 ...data-containing-more-than-40-characters.md |   50 +
 ...mation-button-does-not-display-the-data.md |    4 +-
 ...redit-of-payment-method-customer-credit.md |    6 +-
 ...work-for-asynchronous-payment-providers.md |    8 +-
 ...-documents-typically-exceeding-millions.md |   46 +
 ...low-multiple-cancellation-with-giftcard.md |   11 +-
 ...ent-affiliation-for-debit-online-method.md |    6 +-
 ...eestoque-does-not-support-multilanguage.md |    6 +-
 ...-directly-from-the-mysubscriptions-area.md |    6 +-
 .../en/time-out-import-and-export-admin.md    |    6 +-
 ...gory-keywords-change-with-many-products.md |    6 +-
 ...ut-generating-internal-application-keys.md |   46 +
 ...s-preventing-to-check-the-inventory-log.md |   44 +
 ...tem-with-negative-value-in-inventory-ui.md |   67 +
 ...ion-error-with-unreachable-code-message.md |   44 +
 ...us-prior-to-the-state-that-it-should-be.md |   42 +
 ...anceling-when-one-of-the-card-is-denied.md |    8 +-
 ...n-status-approved-with-payment-canceled.md |   48 +
 ...t-consider-items-removed-from-the-order.md |    4 +-
 ...g-longer-than-expected-to-update-status.md |   43 +
 ...enied-by-error-card-not-enrolled-in-3ds.md |    6 +-
 ...count-to-implement-multilanguage-stores.md |   47 +
 ...ng-saved-in-vbase-and-not-into-rewriter.md |   70 +
 ...does-not-update-best-sla-choice-in-cart.md |    6 +-
 ...en-items-for-pickup-from-another-seller.md |   48 +
 ...en-selecting-to-add-a-new-address-first.md |    6 +-
 ...urs-in-the-place-order-internal-process.md |   42 +
 ...-with-subscriptions-but-it-wasnt-in-api.md |   46 +
 ...or-delivery-is-between-items-for-pickup.md |   48 +
 ...ed-when-using-order-replacement-feature.md |   45 +
 ...ests-for-each-keyfield-of-an-attachment.md |   51 +
 ...ons-that-had-payout-split-config-change.md |    6 +-
 ...to-log-in-through-the-google-app-on-ios.md |   45 +
 ...sing-protocol-encryption-protocol-ssl13.md |   51 +
 ...e-products-pdp-are-still-being-returned.md |   43 +
 ...ritization-by-diacritics-for-portuguese.md |   43 +
 ...-requests-and-components-being-reloaded.md |    6 +-
 ...ning-when-registeringupdating-a-product.md |   48 +
 ...-error-when-changing-edition-of-account.md |   53 +
 ...exportacaoimportacaoespecificacaov2aspx.md |    6 +-
 ...t-search-api-return-wrong-or-empty-data.md |   50 +
 ...default-value-after-changing-it-via-api.md |    6 +-
 ...s-does-not-trigger-automatic-indexation.md |   53 +
 .../update-users-name-in-the-login-section.md |    6 +-
 ...ue-to-lacking-property-on-get-resp-json.md |    6 +-
 ...-working-on-adminportalsitesdefaultcode.md |   49 +
 ...res-even-without-the-correct-permission.md |   53 +
 ...estricted-is-not-able-to-list-the-users.md |   53 +
 ...ant-access-gift-card-admin-looping-page.md |   42 +
 ...n-not-see-the-orders-on-my-account-page.md |   48 +
 ...-when-adding-the-first-item-to-the-cart.md |   45 +
 ...-list-affects-the-results-in-the-report.md |   16 +-
 ...nstep-to-1-causes-last-dots-to-be-empty.md |   48 +
 ...c-not-being-kept-on-the-url-after-login.md |    6 +-
 ...cartmutation-failing-when-large-payload.md |   46 +
 ...-mycards-are-not-automatically-canceled.md |    6 +-
 ...ote-not-found-on-vtex-id-on-the-profile.md |   60 +
 ...ion-not-sending-the-description-in-card.md |    6 +-
 ...t-being-sent-from-seller-to-marketplace.md |    6 +-
 ...ent-doesnt-work-properly-on-ios-devices.md |    6 +-
 ...eived-on-the-datalayer-every-other-time.md |   45 +
 ...-we-change-product-quantity-in-minicart.md |   46 +
 ...-product-feature-does-not-work-properly.md |    6 +-
 ...when-multiple-search-terms-are-provided.md |   51 +
 ...experience-some-trouble-on-firefox-89-0.md |    2 +-
 ...-does-not-work-before-acessing-checkout.md |   49 +
 ...clientid-field-of-the-giftcard-on-admin.md |    6 +-
 ...shows-success-even-when-it-isnt-working.md |    6 +-
 ...-not-fully-integrated-with-headless-cms.md |   42 +
 ...e-kit-is-shown-as-sold-out-on-searching.md |   30 +-
 ...ctname-without-the-sku-name-information.md |   44 +
 ...yed-in-the-order-and-email-notification.md |    6 +-
 ...er-its-not-possible-to-use-a-custom-one.md |    4 +-
 ...n-the-initial-message-is-not-translated.md |    6 +-
 ...ly-our-gateway-performs-a-double-refund.md |    6 +-
 ...ryslainminutes-calculation-returns-null.md |    6 +-
 ...-filters-options-doesnt-colapse-anymore.md |   46 +
 ...eater-than-1-in-intelligent-search-apis.md |   46 +
 ...nt-fields-under-the-same-original-value.md |   52 +
 ...hain-order-for-a-multilevel-marketplace.md |   43 +
 .../xml-currency-symbol-in-the-installment.md |    9 +-
 ...mation-defined-on-category-global-level.md |   41 +
 ...xml-installment-currency-does-not-apply.md |   47 +
 ...not-load-contents-for-unavailable-items.md |   49 +
 ...-product-name-flag-not-working-properly.md |   47 +
 .../en/xmls-returning-500-error.md            |   12 +-
 docs/known-issues/es/.md                      |    2 +-
 ...3-error-for-all-urls-containing-develop.md |   50 +
 ...the-activate-if-possible-flag-unchecked.md |   47 +
 ...-be-returned-blank-in-the-catalog-admin.md |   48 +
 ...information-for-sessions-and-conversion.md |   48 +
 ...skuvincularvalorservicoaspx-not-working.md |   32 +-
 ...-not-available-when-creating-dictionary.md |    2 +-
 ...nvoice-address-returns-null-api-results.md |    6 +-
 ...he-shopper-opts-to-insert-a-new-address.md |   56 +
 ...-removing-essential-address-information.md |    6 +-
 ...n-buyer-has-can-add-shipping-permission.md |   51 +
 ...n-impersonated-using-vtex-telemarketing.md |   48 +
 ...auses-invalid-address-for-an-item-error.md |   59 +
 ...rder-has-more-than-one-product-centauro.md |    6 +-
 .../es/admin-collection-brand-list-timeout.md |    6 +-
 ...rch-doesnt-recognize-profile-menu-items.md |   52 +
 ...n-how-to-improve-section-of-the-catalog.md |    4 +-
 ...nsion-as-jpg-even-when-the-image-is-png.md |    6 +-
 ...-engine-redirects-them-to-the-wrong-url.md |   57 +
 .../es/admin-review-global-search.md          |   50 +
 docs/known-issues/es/admin-timeout.md         |   53 +
 ...ut-country-disrupting-orderform-changes.md |    6 +-
 ...-generates-payment-authorization-denial.md |   55 +
 ...ethodtype-for-amex-when-using-apple-pay.md |   48 +
 ...ed-delivery-selection-appears-only-once.md |    6 +-
 ...-showing-in-vtexcmcproductimage-zoomon-.md |    4 +-
 .../es/amazon-category-implementation.md      |    6 +-
 ...e-sending-product-to-amazon-marketplace.md |   52 +
 ...sku-is-not-being-logged-into-the-bridge.md |   54 +
 .../es/amazon-global-category-not-working.md  |    6 +-
 ...n-integration-attribute-number-of-itens.md |    6 +-
 ...integration-stock-reservations-for-kits.md |    6 +-
 .../amazoncasacaso-erros-de-rastreamento.md   |   17 +-
 ...mate-returns-wrong-info-when-sc-is-null.md |    6 +-
 ...ts-does-not-return-additionalinfo-field.md |    6 +-
 ...-are-not-erased-when-you-delete-the-app.md |   59 +
 ...most-expensive-items-ui-not-saving-data.md |   54 +
 ...oved-skus-spreadsheet-not-showing-price.md |    6 +-
 ...t-allow-null-domainvalues-and-it-should.md |   70 +
 ...ation-on-field-domainvalues-not-working.md |    6 +-
 ...g-an-item-from-a-seller-with-attachment.md |   65 +
 ...are-not-updated-when-its-added-to-items.md |   49 +
 ...e-not-being-updated-in-meli-integration.md |   51 +
 ...pricing-logs-showing-unknow-information.md |   49 +
 ...payments-when-the-first-one-is-canceled.md |   46 +
 .../es/auto-approve-api-accepts-any-values.md |    6 +-
 ...ng-suggestion-products-shown-with-delay.md |    6 +-
 ...tocomplete-not-answering-to-cold-starts.md |   18 +-
 ...i-removes-the-dot-from-the-product-name.md |   53 +
 ...culate-during-the-first-hour-of-the-day.md |    2 +-
 ...ic-payment-settlement-incorrectly-setup.md |   60 +
 ...not-occurring-due-to-special-characters.md |   46 +
 ...date-of-deliveries-tracking-by-correios.md |    8 +-
 ...mulation-for-no-stock-or-price-products.md |   53 +
 ...-missing-data-for-newly-created-address.md |   69 +
 ...r-of-routes-created-to-deliver-the-item.md |   46 +
 ...d-data-is-not-removed-after-logging-out.md |   49 +
 ...story-doesnt-work-in-the-website-domain.md |   46 +
 ...ng-geolocation-when-registering-address.md |   48 +
 ...-detail-ui-only-shows-100-first-sellers.md |   56 +
 ...e-doesnt-register-information-in-orders.md |   44 +
 ...count-at-checkout-in-the-website-domain.md |   48 +
 ...e-geocoordinates-to-calculate-region-id.md |   49 +
 ...rect-order-fob-integrating-with-carrier.md |    6 +-
 .../es/b2w-freight-value-in-oms-vtex.md       |    6 +-
 ...n-searching-terms-with-directly-via-url.md |    8 +-
 ...arching-terms-with-through-autocomplete.md |   46 +
 ...-with-a-huge-quantity-of-reserved-items.md |   45 +
 ...ific-scenarios-with-merchandising-rules.md |   51 +
 ...en-the-promotion-is-a-buy-together-type.md |   49 +
 ...form-application-does-not-work-properly.md |   58 +
 ...rties-not-being-validated-on-legacy-cms.md |    6 +-
 ...s-are-not-searchable-on-the-brand-admin.md |   43 +
 ...hanges-to-the-intelligent-search-module.md |    4 +-
 ...cep-not-working-in-create-giftlist-form.md |    6 +-
 ...-mycards-page-not-translated-to-spanish.md |    6 +-
 ...k-on-the-first-try-in-fullcleanup-admin.md |   49 +
 ...oducts-not-to-load-on-the-front-timeout.md |   51 +
 ...figuration-in-organizationscost-centers.md |   47 +
 .../calculation-issue-in-comissionamount.md   |   44 +
 ...s-to-cart-from-store-framework-frontend.md |   50 +
 ...to-retry-payment-which-may-also-deny-it.md |   45 +
 ...rent-from-to-equal-to-with-a-collection.md |   56 +
 ...ormaspx-save-button-requires-two-clicks.md |    6 +-
 ...re-not-applied-after-3rd-category-level.md |   49 +
 ...nt-edit-the-name-of-the-styles-template.md |   46 +
 ...rd-brands-incorrectly-processed-as-visa.md |   45 +
 ...card-facebook-doesnt-save-some-settings.md |    6 +-
 ...order-doesnt-bring-the-assembly-options.md |   46 +
 ...-old-order-doesnt-bring-the-attachments.md |    6 +-
 ...ing-placed-as-expected-in-the-orderform.md |   57 +
 ...sing-sent-by-checkout-in-additionaldata.md |   46 +
 ...re-kept-in-orders-with-total-value-zero.md |   44 +
 ...if-store-cant-ship-to-all-the-countries.md |   47 +
 ...ent-do-not-receive-promotions-correctly.md |   46 +
 ...-not-consider-items-removed-from-orders.md |   48 +
 ...gunit-with-query-parameter-refid-return.md |    6 +-
 ...properly-to-space-at-the-end-of-strings.md |   50 +
 ...export-cannot-handle-t-and-s-characters.md |   50 +
 ...xport-for-attachment-cuts-50-characters.md |   54 +
 .../es/catalog-filters-timeout.md             |   47 +
 ...ql-categoryinputtranslation-not-working.md |   49 +
 ...enerating-invalid-translation-documents.md |   47 +
 ...-report-total-section-calculation-error.md |    6 +-
 ...ion-xml-fiscal-code-field-not-rendering.md |   47 +
 ...alog-search-api-limited-to-2500-results.md |   50 +
 ...rn-information-for-products-unavailable.md |    6 +-
 ...slations-not-reflecting-on-the-frontend.md |   57 +
 .../es/catalogv2-user-roles-not-applying.md   |    6 +-
 ...update-with-values-from-review-skus-tab.md |   51 +
 ...category-score-field-is-not-being-saved.md |    6 +-
 .../centauro-to-implement-centauro-envios.md  |    6 +-
 ...-to-myaccount-instead-of-the-order-page.md |   58 +
 ...-calculation-of-promotions-take-3-pay-2.md |    6 +-
 ...er-using-api-without-email-orderchanged.md |    6 +-
 ...tyles-admin-page-are-not-saved-properly.md |   49 +
 ...ccessories-is-not-triggering-indexation.md |   50 +
 ...-could-make-the-page-not-work-correctly.md |    6 +-
 ...without-shipping-address-on-the-ui-only.md |    6 +-
 ...-add-2-different-addresses-for-delivery.md |   49 +
 ...pty-shippingdata-when-using-geolocation.md |   44 +
 ...as-free-shipping-and-scheduled-delivery.md |    6 +-
 ...at-first-instant-for-specific-condition.md |   29 +-
 ...support-encoding-assembly-options-names.md |   47 +
 ...tly-sending-item-details-to-transaction.md |    6 +-
 ...ct-seller-when-merging-cart-information.md |   46 +
 ...tax-field-for-shipping-percentage-taxes.md |   47 +
 ...e-same-sku-receives-a-logistics-timeout.md |   51 +
 ...ress-for-shoppers-with-complete-profile.md |   50 +
 ...r-items-with-no-common-shipping-methods.md |   53 +
 ...orrect-sla-values-from-logistics-system.md |    8 +-
 ...-hyphen-in-the-postal-code-to-orderform.md |   50 +
 ...-the-user-switches-the-delivery-options.md |   47 +
 ...-there-is-only-pickup-address-available.md |    7 +-
 ...oesnt-handle-multiple-filters-correctly.md |   42 +
 ...ly-sometimes-in-global-checkout-setting.md |   53 +
 ...t-add-client-profile-is-performed-twice.md |   47 +
 ...with-the-same-names-as-the-default-ones.md |    6 +-
 ...is-not-accessible-through-the-new-admin.md |    2 +-
 .../es/cms-legacy-collections-timeout.md      |   28 +-
 ...oving-value-from-the-unit-of-mass-field.md |    6 +-
 ...s-settings-role-not-working-as-expected.md |   57 +
 ...ble-menu-issues-rendering-all-the-items.md |    6 +-
 ...ot-allow-more-than-1000-skus-per-upload.md |    4 +-
 ...ustom-search-results-pages-in-b2b-suite.md |   49 +
 .../collections-dont-open-on-subaccounts.md   |   47 +
 ...-only-shows-1st-sku-of-inactive-product.md |   49 +
 ...-equal-to-on-the-campaign-audience-form.md |    6 +-
 ...h-special-characters-cannot-be-exported.md |   48 +
 ...ation-details-shows-only-20-collections.md |   55 +
 ...ng-as-expected-on-progressive-discounts.md |   50 +
 ...eation-due-to-failure-in-gatewaycallbak.md |   24 +-
 ...n-implemented-in-productsummary-for-ios.md |    4 +-
 ...nconsistency-in-deliveryshipping-prices.md |    6 +-
 ...components-in-a-kit-with-the-same-price.md |   50 +
 .../confirmed-order-email-not-being-sent.md   |    4 +-
 ...the-same-name-at-the-intelligent-search.md |   53 +
 ...violates-the-following-content-security.md |   54 +
 .../es/cookie-broken-the-apisessions.md       |    4 +-
 ...-only-25-options-in-b2b-admin-customers.md |   49 +
 .../country-field-as-null-in-invoicedata.md   |   48 +
 ...ys-restricted-to-the-delivery-countries.md |    6 +-
 ...oupons-created-as-archived-temporarrily.md |   49 +
 ...oesnt-send-nulls-as-release-date-values.md |   48 +
 ...-does-not-update-the-items-stockbalance.md |   50 +
 ...-of-redirects-breaks-the-redirects-page.md |   51 +
 ...-of-the-csv-through-the-cli-doesnt-work.md |   51 +
 ...not-returned-on-the-explained-search-ui.md |   46 +
 .../crm-error-when-searching-with-spaces.md   |    4 +-
 ...y-symbol-does-not-follow-admin-language.md |   50 +
 .../custom-attribute-mapper-mercado-livre.md  |   47 +
 ...cms-not-working-with-more-than-one-html.md |   49 +
 ...mage-is-not-displayed-on-mobile-version.md |    6 +-
 ...tatus-at-mycredits-page-are-not-correct.md |    6 +-
 ...s-some-order-with-profileerroronloading.md |   46 +
 ...tion-is-not-saved-in-the-profile-system.md |    6 +-
 ...ipping-promotion-default-saleschannel-1.md |    6 +-
 ...v-without-validation-of-characters-type.md |    6 +-
 ...ed-payment-system-rendering-at-checkout.md |   45 +
 ...eadlocked-error-when-using-catalog-apis.md |   44 +
 ...-an-error-in-the-transactionstate-field.md |   28 +-
 ...-checkout-if-not-deactivated-previously.md |   41 +
 ...e-is-space-in-the-id-of-shipping-policy.md |   49 +
 ...with-lean-shipping-offering-invalid-sla.md |   51 +
 ...ing-on-seller-management-commissions-ui.md |   50 +
 .../diacritics-are-removed-on-catalogapi.md   |    6 +-
 ...rices-between-pdp-plp-and-checkout-cart.md |   49 +
 ...-specification-value-on-apis-and-portal.md |   41 +
 ...perly-when-prop-animated-is-set-as-true.md |    6 +-
 ...oupon-usage-count-on-oms-and-coupons-ui.md |   47 +
 ...al-order-value-and-total-products-value.md |    2 +-
 ...-settings-on-new-accounts-or-workspaces.md |   50 +
 ...transaction-list-and-on-the-transaction.md |   14 +-
 ...domly-getting-last-digit-deleted-on-ios.md |   38 +
 ...sspecification-values-on-the-same-level.md |    6 +-
 ...n-modal-to-switch-between-organizations.md |   49 +
 ...-ignored-when-approved-on-received-skus.md |   49 +
 ...th-automatic-capture-on-authorizedotnet.md |   59 +
 ...derest-are-not-respecting-early-capture.md |    6 +-
 ...filling-for-new-buyers-after-logging-in.md |   48 +
 ...autofilling-for-new-users-on-checkoutui.md |   62 +
 ...ate-using-the-b2b-organizations-feature.md |   47 +
 .../es/encoding-error-in-apple-mail-app.md    |    2 +-
 ...ters-leads-to-unexpected-product-search.md |   44 +
 ...re-specific-global-category-persistente.md |    6 +-
 ...e-rejected-or-reviewed-by-offer-quality.md |   55 +
 ...ror-cancelling-customer-credit-invoices.md |   47 +
 ...a-promotion-excluding-more-than-1-brand.md |    6 +-
 .../error-closing-customer-credit-account.md  |   47 +
 ...xporting-entity-with-too-many-documents.md |   50 +
 ...ror-exporting-large-amount-of-giftcards.md |   15 +-
 .../error-exporting-prices-with-metadata.md   |   51 +
 .../es/error-in-checkout-error-message.md     |    6 +-
 .../es/error-in-custom-payments-creation.md   |   46 +
 ...ients-is-different-than-operation-value.md |   49 +
 ...lue-cannot-be-null-parameter-name-value.md |   49 +
 ...-cancelation-when-the-returncode-is-359.md |   49 +
 ...ui-after-requesting-the-invoice-via-app.md |   62 +
 ...trying-to-access-catalog-pages-on-admin.md |   50 +
 ...-sku-is-binded-on-vtexvtex-integrations.md |    6 +-
 ...-search-using-the-all-field-in-vtex-crm.md |   49 +
 .../es/error-on-duplicate-payment-method.md   |   53 +
 ...-sellers-to-marketplaces-and-vice-versa.md |    2 +-
 ...gain-when-adding-images-via-site-editor.md |   50 +
 .../es/error-sww-on-product-pdp.md            |   19 +-
 ...al-connector-for-pending-payment-status.md |    6 +-
 ...ng-an-index-if-the-fields-are-identical.md |   46 +
 ...delivery-type-when-seller-has-recursion.md |    6 +-
 ...-publishing-dynamic-storage-data-entity.md |   60 +
 ...en-running-vtex-link-for-the-first-time.md |    2 +-
 ...-transaction-with-2-cards-mercadopagov1.md |    6 +-
 ...r-when-trying-to-publish-or-link-an-app.md |   50 +
 docs/known-issues/es/event-inconsistency.md   |   49 +-
 ...be-returned-once-the-order-has-a-change.md |    6 +-
 ...de-products-from-collection-not-working.md |   52 +
 ...edirects-not-pointing-back-to-old-route.md |   50 +
 ...xts-between-different-areas-or-products.md |   45 +
 ...sometimes-the-request-can-not-completed.md |   41 +
 ...xport-redirects-not-working-as-intended.md |   29 +-
 ...the-csv-in-the-sales-performance-module.md |    8 +-
 ...his-character-cut-in-the-image-url-rows.md |   50 +
 ...pdate-the-price-in-the-facebook-catalog.md |   54 +
 ...rumbs-page-title-and-additional-filters.md |   51 +
 ...ancellation-ppp-when-cancellationidnull.md |    6 +-
 ...s-the-go-to-payment-button-to-disappear.md |   48 +
 ...ststore-cart-merges-assembly-line-items.md |   46 +
 ...ng-not-removing-facets-set-to-ne-hidden.md |   50 +
 ...pi-considering-fuzzy-as-auto-as-default.md |   46 +
 ...return-seo-information-on-graphql-query.md |   49 +
 ...page-status-and-crashing-the-pagination.md |    6 +-
 ...n-trade-policy-not-reflecting-on-pdpplp.md |    6 +-
 ...ting-on-seller-management-ui-after-save.md |   29 +-
 ...any-change-in-order-management-settings.md |   12 +-
 ...not-update-all-the-files-only-the-first.md |   21 +-
 ...-performance-is-not-accepting-uppercase.md |    6 +-
 ...names-while-applying-additional-filters.md |   47 +
 ...t-considering-regionalized-availability.md |   53 +
 ...den-from-intelligent-search-admin-pages.md |   42 +
 ...to-old-component-version-on-site-editor.md |   48 +
 ...ll-the-profileshipping-data-at-checkout.md |   48 +
 ...orporatedocument-if-starts-with-letters.md |   47 +
 .../es/first-subscription-cycle-is-skipped.md |   54 +
 ...rade-policy-1-when-saving-bundle-prices.md |    6 +-
 ...ace-integrate-an-order-erro-code-fmt010.md |    6 +-
 ...it-orders-outside-promotion-restriction.md |    6 +-
 ...-has-seller-groups-on-seller-management.md |   51 +
 ...egory-tree-on-itemcategory-in-datalayer.md |   47 +
 ...a-cant-be-informed-for-some-cultureinfo.md |    6 +-
 ...eep-same-sku-order-when-changing-limits.md |   20 +-
 ...ist-multiple-orders-for-the-same-coupon.md |   50 +
 ...ed-offers-list-api-not-working-properly.md |    6 +-
 ...-by-refid-returning-null-when-not-found.md |    6 +-
 ...sku-by-ean-api-returns-only-active-skus.md |    6 +-
 ...from-component-sku-and-not-from-kit-sku.md |    6 +-
 .../es/gift-card-creation-error-via-admin.md  |   50 +
 ...ith-the-date-chosen-when-it-was-created.md |    6 +-
 ...ty-id-in-response-to-create-transaction.md |   45 +
 ...-extra-backslash-when-calling-providers.md |    6 +-
 ...relationname-when-we-make-a-get-request.md |   46 +
 ...-a-generic-exception-if-it-has-no-price.md |    6 +-
 ...n-acting-alongside-other-gift-promotion.md |    6 +-
 ...add-credit-to-the-gift-card-through-api.md |    6 +-
 ...a-na-ui-nao-e-a-mesma-que-reflete-no-bd.md |    6 +-
 ...-in-catalog-outdated-compared-to-google.md |    6 +-
 ...onent-iframe-has-inconsistent-rendering.md |   49 +
 ...les-performance-not-working-as-expected.md |    6 +-
 ...s-cms-ignores-array-validation-settings.md |   51 +
 ...ng-do-not-work-on-seller-portal-catalog.md |   50 +
 ...ignored-after-one-purchase-is-completed.md |   51 +
 ...idget-not-shown-if-showmodal-is-enabled.md |   47 +
 ...oducts-if-import-is-made-based-on-skuid.md |   52 +
 ...-items-to-invoice-field-in-the-order-ui.md |   48 +
 ...e-tax-values-in-the-ui-appear-the-total.md |    6 +-
 ...partial-cancellation-with-mercadopagov1.md |    6 +-
 ...paypal-credentials-for-the-same-account.md |   18 +-
 ...tions-appearing-with-brazilian-currency.md |   47 +
 ...items-with-assembly-options-in-the-cart.md |    2 +-
 ...-organization-and-b2b-checkout-settings.md |   47 +
 ...ku-has-unit-multiplier-different-than-1.md |   27 +-
 .../es/incorrect-currency-on-payment-form.md  |    6 +-
 ...iscount-to-all-the-same-items-in-a-cart.md |   53 +
 ...ients-is-different-than-operation-value.md |   55 +
 ...rect-shippingestimatedate-for-order-fob.md |    6 +-
 ...e-registered-on-the-fulfillmentendpoint.md |   50 +
 .../es/incorrectly-updated-inventory.md       |    6 +-
 ...the-highest-instead-of-the-lowest-price.md |    6 +-
 ...s-do-not-work-on-seller-portal-accounts.md |    6 +-
 ...are-same-skuid-in-different-array-items.md |   52 +
 .../es/infocard-mobile-images-wont-apply.md   |   50 +
 ...s-from-servers-that-require-user-agents.md |   52 +
 ...ns-not-updating-automatically-on-pdpplp.md |   38 +
 ...e-via-image-url-does-not-work-correctly.md |    8 +-
 ...s-not-in-sync-with-store-configurations.md |   67 +
 ...ot-capturing-sales-events-for-faststore.md |   45 +
 ...t-settings-search-bar-is-case-sensitive.md |   44 +
 ...-normalizing-gender-in-portuguese-words.md |   50 +
 ...tate-changes-the-address-insertion-mode.md |   49 +
 ...ng-state-sends-the-wrong-payment-option.md |   48 +
 .../intermitent-site-editor-content-loss.md   |   52 +
 .../internalsearcherror-timeouts-on-portal.md |   48 +
 ...ilable-addresses-with-different-country.md |   50 +
 ...ory-notifications-to-indexer-are-cached.md |   55 +
 .../es/inventory-reserved-items-error.md      |   33 +-
 ...egory-names-cause-page-not-found-errors.md |   49 +
 ...-not-work-as-expected-on-the-search-api.md |    6 +-
 ...d-search-for-searches-with-accent-marks.md |    6 +-
 ...e-on-translating-titles-for-some-facets.md |   12 +-
 ...operties-beginning-with-the-same-prefix.md |   46 +
 ...values-in-loyalty-gift-card-at-checkout.md |   46 +
 ...ss-leading-to-transaction-cancellations.md |   51 +
 .../es/issues-with-my-account-links.md        |   48 +
 ...his-item-without-attachment-in-the-cart.md |   54 +
 ...create-a-path-using-content-type-via-ui.md |   50 +
 ...shown-in-seller-whitelabel-change-order.md |   49 +
 ...r-location-is-not-defined-with-no-stock.md |   50 +
 ...f-add-to-cart-event-in-google-analytics.md |   49 +
 ...-promotions-with-collections-associated.md |   55 +
 ...api-is-not-calculating-component-prices.md |   12 +-
 ...ight-can-be-overritten-by-apiwebservice.md |    6 +-
 ...a-request-when-the-accountid-is-missing.md |   17 +-
 ...eadsheet-error-on-new-collections-admin.md |   23 +-
 ...same-slas-but-in-a-different-ordination.md |   23 +-
 ...went-wrong-after-changing-pickup-points.md |   52 +
 ...activate-after-removing-items-from-cart.md |   49 +
 ...catalog-ui-delete-button-not-functional.md |   52 +
 ...-cmss-banner-custom-element-not-working.md |   57 +
 ...ting-products-wrongly-to-the-collection.md |    6 +-
 ...ntrols-do-not-consider-unit-multipliers.md |   51 +
 ...ntroller-texts-are-not-being-translated.md |    6 +-
 ...eadsheet-only-returning-active-services.md |   51 +
 ...y-setup-only-works-opening-in-a-new-tab.md |    6 +-
 ...r-when-translating-with-catalog-graphql.md |   93 ++
 ...tcher-doesnt-work-in-myvtex-environment.md |    4 +-
 ...with-password-cannot-be-undone-in-admin.md |   57 +
 ...es-not-work-when-productprice-as-0-zero.md |    6 +-
 ...yment-condition-requires-authentication.md |    4 +-
 ...specifications-from-another-marketplace.md |    6 +-
 ...marketplace-didnt-update-status-on-vtex.md |   50 +
 ...ine-luiza-some-skus-do-not-update-price.md |   56 +
 ...-deve-ser-igual-ou-menor-a-data-de-hoje.md |   53 +
 .../mandatory-service-working-as-optional.md  |   49 +
 ...using-multiple-coupons-feature-and-utms.md |   47 +
 ...value-when-campaign-audience-is-matched.md |   49 +
 ...lues-due-to-certain-purchase-conditions.md |   52 +
 ...snt-consider-manual-price-for-discounts.md |   48 +
 ...est-doesnt-consider-some-discount-types.md |   48 +
 ...ransactions-are-being-processed-as-visa.md |   45 +
 ...erdata-export-download-link-unavailable.md |   12 +-
 ...ved-skus-api-returning-invalid-sellerid.md |   55 +
 ...ng-height-width-weight-and-length-to-01.md |   52 +
 ...uctsku-name-contains-special-characters.md |   49 +
 ...hipping-discount-not-updating-pricetags.md |   50 +
 ...rrect-discount-when-using-the-same-item.md |   70 +
 ...cannot-be-changed-by-franchise-accounts.md |   48 +
 ...t-passing-a-symbol-or-special-character.md |   34 +
 ...o-meli-without-being-mapped-from-seller.md |   52 +
 ...ntegration-with-a-non-expected-behavior.md |    6 +-
 ...tomatic-messages-mercado-livre-messages.md |    8 +-
 ...enu-not-showing-the-orderid-information.md |   48 +
 ...aused-when-the-marketplace-ad-is-paused.md |   48 +
 ...-error-while-sending-the-order-tracking.md |   18 +-
 ...quotation-for-multiple-officialstoreids.md |   47 +
 ...ull-orders-not-creating-invoice-in-vtex.md |   47 +
 ...ct-value-when-client-has-coupon-on-meli.md |   49 +
 ...-errors-from-meli-429-too-many-requests.md |   54 +
 ...-for-peru-venezuela-equador-and-uruguai.md |   48 +
 ...ntegration-zipcodes-11111-meli-limaperu.md |    6 +-
 ...ding-product-specification-as-variation.md |   46 +
 ...tex-oms-for-multiples-accounts-scenario.md |   49 +
 ...hart-not-working-for-sizes-with-letters.md |   54 +
 ...eli-sizechart-issue-attribute-not-valid.md |   47 +
 .../es/meli-update-stockprice-issue.md        |   48 +
 ...ybox-doesnt-update-shippingmode-for-me2.md |   59 +
 ...bridge-isnt-logging-some-error-messages.md |   53 +
 ...-not-showing-the-shippingid-information.md |   50 +
 .../es/mercado-livre-mapper-attribute-size.md |   19 +-
 ...ve-underreview-validation-in-update-sku.md |   42 +
 ...bridge-isnt-logging-some-error-messages.md |   48 +
 ...working-for-the-facet-productclusterids.md |   52 +
 ...for-some-clients-in-customer-credit-api.md |   54 +
 ...ing-too-long-to-return-the-informations.md |   43 +
 ...n-field-cannot-be-deleted-through-admin.md |   46 +
 ...messages-only-appear-after-a-second-try.md |   52 +
 ...does-not-show-sku-specs-in-b2b-scenario.md |    6 +-
 ...sending-options-for-already-added-items.md |    6 +-
 ...-app-breaks-other-apps-of-the-same-type.md |    4 +-
 ...causes-antifraud-to-cancel-transactions.md |    6 +-
 ...price-facetfilter-at-intelligent-search.md |   47 +
 ...en-this-type-of-modal-are-configured-ok.md |    6 +-
 ...cated-divergences-setup-shipping-policy.md |    6 +-
 .../multiple-sku-promotion-api-not-working.md |    6 +-
 ...shivering-when-trying-to-add-a-new-card.md |   49 +
 ...field-filled-in-the-address-information.md |    6 +-
 ...tion-is-associated-with-a-pick-up-point.md |    4 +-
 ...-the-address-line-2-this-appear-as-null.md |    6 +-
 ...-spinner-button-is-not-working-properly.md |    4 +-
 ...hen-accessing-from-an-dependent-account.md |    6 +-
 ...eased-filter-is-not-working-for-exports.md |   36 -
 ...e-customers-id-document-for-example-cpf.md |    6 +-
 ...the-invoiced-value-on-return-items-page.md |    6 +-
 ...acters-and-causes-problem-in-order-flow.md |    2 +-
 ...e-and-lastdeliveryday-for-high-timecost.md |   75 +
 ...as-expected-with-subtraction-operations.md |   55 +
 ...distributed-among-all-items-in-the-cart.md |   19 +-
 ...plit-for-second-item-incorrect-discount.md |   67 +
 ...proper-detached-sku-on-pdp-in-a-new-tab.md |   49 +
 ...when-entity-has-more-than-10k-documents.md |    6 +-
 ...upted-file-when-there-are-no-skus-found.md |   49 +
 ...r-does-not-correspond-to-correct-number.md |    6 +-
 ...t-first-informs-an-address-for-delivery.md |   51 +
 ...pears-even-after-filled-until-save-data.md |   46 +
 ...er-only-captures-the-information-of-the.md |    6 +-
 ...bypricedesc-could-bring-the-wrong-order.md |   55 +
 ...dal-hook-affects-all-modals-on-the-page.md |   49 +
 ...orrectly-due-to-null-documenttype-field.md |   41 +
 ...ain-from-b2b-orders-history-doesnt-work.md |    6 +-
 ...ization-lessthan-100-goes-with-the-flow.md |   53 +
 ...r-card-info-causing-confusing-on-status.md |    6 +-
 ...o-price-divergence-on-fulfillment-layer.md |    6 +-
 ...erly-due-double-space-on-promotion-name.md |   21 +-
 ...uotes-in-the-promotion-name-or-sku-name.md |   58 +
 ...carrier-leaves-label-barcode-incomplete.md |   46 +
 ...-triggered-the-transaction-total-refund.md |    6 +-
 ...-and-original-order-have-the-same-value.md |   48 +
 ...nses-field-from-get-payment-details-api.md |   54 +
 ...ler-status-cancellationrequestdeniedffm.md |   58 +
 ...o-missing-payment-approved-notification.md |   51 +
 ...-the-items-and-refund-the-total-payment.md |   53 +
 ...-conectors-like-payment-app-or-redirect.md |    6 +-
 ...eled-but-the-payment-remains-authorized.md |   19 +-
 ...r-the-same-item-under-different-sellers.md |   10 +-
 ...id-scheduled-delivery-that-cant-be-used.md |   42 +-
 ...rs-data-even-for-authorized-credentials.md |    6 +-
 ...form-not-updating-after-order-is-placed.md |   53 +
 ...of-delivery-times-scheduled-at-checkout.md |    2 +-
 ...ps-from-the-root-category-does-not-work.md |    6 +-
 ...hat-dont-update-the-invoice-at-netshoes.md |    6 +-
 ...oice-value-in-output-invoice-validation.md |   54 +
 ...th-asterisks-in-the-address-and-profile.md |   55 +
 ...aceitems-is-not-opening-on-new-ui-admin.md |   27 +-
 ...nvoiceaddress-created-through-native-ui.md |   30 +-
 ...hen-uploading-a-new-version-not-working.md |    6 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   50 +
 ...n-performing-2-product-changes-in-a-row.md |   52 +
 ...-is-causing-us-to-misidentify-some-bins.md |   21 +-
 .../outdated-url-on-the-update-binding-ui.md  |   53 +
 ...iggered-twice-when-accessing-my-account.md |   47 +
 ...being-duplicated-in-custom-search-pages.md |   63 +
 ...h-results-not-working-on-giftlist-pages.md |    6 +-
 ...esnt-reset-when-changing-search-context.md |   53 +
 ...-cart-sometimes-returns-null-api-result.md |   18 +-
 ...cessing-transactions-as-prepaid-in-full.md |   49 +
 ...-with-swl-when-using-identical-typesids.md |    6 +-
 ...t-differ-from-active-payment-conditions.md |   10 +-
 ...ot-applied-in-the-b2b-checkout-settings.md |   66 +
 ...-assigned-after-approving-organizations.md |   51 +
 ...rice-comes-exclusively-from-manualprice.md |   49 +
 ...er-for-multilevel-omnichannel-inventory.md |    6 +-
 ...-respect-the-minimum-installment-amount.md |    6 +-
 ...kup-point-disregarded-based-on-priority.md |    8 +-
 ...eocoordinates-without-a-google-maps-key.md |   51 +
 ...ble-for-selection-in-shipping-policy-ui.md |    4 +-
 ...d-in-the-shipping-policy-after-deletion.md |   46 +
 ...d-after-searching-addresses-in-map-mode.md |    6 +-
 ...ickup-points-not-indexed-in-master-data.md |   50 +
 ...-same-id-pattern-show-product-available.md |   49 +
 ...the-same-cart-are-not-working-correctly.md |   49 +
 ...address-options-for-recurring-customers.md |   60 +
 ...-cookies-when-client-logout-at-checkout.md |   21 +-
 ...ging-out-when-using-callcenter-operator.md |    4 +-
 ...ssing-the-url-with-pagination-parameter.md |    6 +-
 ...-notification-in-the-ui-api-and-gateway.md |   46 +
 ...he-legacy-cms-collection-is-not-working.md |   52 +
 ...-of-spot-price-instead-of-regular-price.md |   55 +
 ...doesnt-correspond-to-the-search-results.md |   47 +
 .../es/price-range-disregards-sales-policy.md |   37 +-
 ...-minimum-value-after-selecting-a-filter.md |   54 +
 ...-twice-and-one-is-from-assembly-options.md |   52 +
 ...-updates-with-cache-on-end-applications.md |   45 +
 ...-to-int32-max-value-on-change-price-api.md |   45 +
 ...ducts-keyword-not-considering-stopwords.md |   48 +
 ...-value-field-when-buying-with-two-cards.md |    6 +-
 ...with-phone-validation-on-mobile-devices.md |   49 +
 ...ayed-when-using-multiple-sales-channels.md |   73 +
 ...ed-in-the-pickups-in-cart-display-modal.md |    6 +-
 ...product-comissioning-inconsistent-cache.md |   64 +
 ...on-admin-changes-with-more-than-70-skus.md |   52 +
 ...date-api-allows-n-in-the-textlink-field.md |    6 +-
 ...m-doesnt-work-on-catalogs-redesigned-ui.md |   49 +
 ...ku-name-when-the-product-has-only-1-sku.md |    6 +-
 .../es/product-page-sessions-not-working.md   |   45 +
 ...e-not-considering-default-seller-in-pdp.md |    6 +-
 ...r-not-working-on-seller-portal-accounts.md |    6 +-
 ...specification-export-index-out-of-range.md |   20 +-
 ...ection-module-assuming-incorrect-values.md |   49 +
 ...tion-module-does-not-list-root-category.md |   48 +
 ...oes-not-trigger-the-products-indexation.md |   49 +
 ...chresolver-is-incorrect-due-to-rounding.md |    6 +-
 ...d-when-the-productname-contains-numbers.md |   16 +-
 ...flag-and-discount-after-promotion-ended.md |   45 +
 ...wn-as-unavailable-at-intelligent-search.md |   45 +
 ...ted-with-duplicated-skus-on-the-catalog.md |   50 +
 ...ed-as-with-promotion-for-search-filters.md |   48 +
 ...sellers-are-appearing-in-the-end-of-plp.md |    6 +-
 ...form-allows-utf16-format-uploaddownload.md |    6 +-
 ...productsskus-import-does-not-support-lb.md |    6 +-
 ...complete-profile-with-ignoreprofiledata.md |   50 +
 ...ed-after-adding-client-preferences-data.md |   43 +
 ...equency-not-working-on-recurring-cycles.md |   46 +
 ...t-performance-or-lead-to-timeout-errors.md |   55 +
 ...hod-doesnt-works-for-whitelabel-sellers.md |   47 +
 ...thods-do-not-appear-on-the-product-page.md |    6 +-
 .../es/promotions-microrounding-divergence.md |   99 ++
 ...-sorting-filtering-by-price-or-discount.md |   42 +
 ...s-ui-loading-wrong-currency-information.md |   18 +-
 ...ty-blockclass-from-infocard-not-working.md |    6 +-
 ...t-split-items-and-free-shipping-applied.md |   41 +
 ...-is-shown-in-the-license-manager-module.md |    6 +-
 ...ly-when-2-categories-have-the-same-name.md |    6 +-
 ...nd-is-stuck-on-freight-type-has-changed.md |   48 +
 .../put-price-overwrites-kit-price-logic.md   |   29 +-
 ...he-limit-value-when-user-quickly-clicks.md |    6 +-
 ...-wont-let-me-change-the-value-by-typing.md |   51 +
 ...h-after-reaching-max-available-qunatity.md |    6 +-
 ...-to-the-searched-zip-codes-availability.md |    2 +-
 ...n-the-sku-is-sold-by-more-than-1-seller.md |    6 +-
 ...ter-do-not-work-with-special-characters.md |   52 +
 ...ceived-skus-review-tab-missing-products.md |   54 +
 ...irects-are-being-counted-multiple-times.md |   51 +
 ...inks-when-using-in-the-final-of-the-url.md |   47 +
 ...avior-not-consistent-between-api-and-ui.md |   50 +
 ...es-us-to-misidentify-mastercard-as-visa.md |   52 +
 ...on-api-returns-seller-list-due-to-cache.md |   48 +
 ...-while-requesting-nonwhitelabel-sellers.md |    6 +-
 ...delivery-to-pickup-on-the-checkout-page.md |   50 +
 ...is-not-inactivating-skus-without-refids.md |    6 +-
 .../render-component-issues-on-site-editor.md |   19 +-
 ...ing-orders-with-different-sales-channel.md |   48 +
 .../es/replicated-pending-payment-emails.md   |    6 +-
 ...g-is-inconsistent-when-running-ab-tests.md |   42 +
 .../es/reserved-stock-in-invoiced-orders.md   |    6 +-
 ...queid-arrays-it-is-not-visible-properly.md |   45 +
 ...ve-a-different-value-added-to-gift-card.md |   14 +-
 .../rewriter-is-not-receiving-url-updates.md  |   62 +
 ...-items-with-unitmultiplier-other-than-1.md |   57 +
 ...terms-of-quantity-of-packages-and-items.md |   46 +
 ...-assigned-after-approving-organizations.md |   54 +
 ...ailing-for-custom-types-in-headless-cms.md |   53 +
 ...e-when-zooming-after-search-page-render.md |   50 +
 ...en-theres-a-slider-layout-on-background.md |   51 +
 .../es/search-analytics-duplicated-events.md  |   63 +
 ...een-versions-withwithout-funnel-metrics.md |   49 +
 ...-skus-for-fqspecificationfilter-queries.md |    6 +-
 ...login-in-using-the-call-center-operator.md |    6 +-
 ...rl-after-navigating-through-suggestions.md |   46 +
 ...the-operator-and-for-trigger-conditions.md |   54 +
 ...rch-by-ean-not-working-on-received-skus.md |   46 +-
 ...account-management-when-using-b2b-suite.md |   58 +
 ...-price-range-yielding-incorrect-results.md |    6 +-
 ...lations-over-already-translated-content.md |   53 +
 ...t-when-the-value-contains-a-plus-symbol.md |   66 +
 ...-updated-only-after-refreshing-the-page.md |    6 +-
 ...sion-updates-does-not-index-binded-skus.md |   56 +
 ...-creation-does-not-add-selected-sellers.md |   54 +
 ...price-condition-not-working-as-expected.md |   50 +
 ...-specifications-dropdown-malfunctioning.md |    6 +-
 ...s-to-reindex-when-inactivating-a-seller.md |   48 +
 ...ced-with-problem-in-the-payment-capture.md |   66 +
 ...ype-name-field-wrongly-returned-via-api.md |   48 +
 ...ces-are-not-updated-when-added-to-items.md |    6 +-
 ...hen-they-are-not-in-the-same-path-level.md |   49 +
 ...esnt-update-expiration-period-of-quotes.md |   56 +
 ...-frozen-when-trying-to-select-an-option.md |   49 +
 ...layed-as-active-in-the-new-logistics-ui.md |   49 +
 ...deliver-on-weekends-is-being-considered.md |    6 +-
 ...es-not-show-message-error-on-simulation.md |    6 +-
 ...does-not-use-sla-name-for-display-in-ui.md |    6 +-
 ...s-package-split-for-pickup-and-shipping.md |   47 +
 ...ng-the-date-when-its-scheduled-delivery.md |    6 +-
 ...g-the-price-when-its-scheduled-delivery.md |   10 +-
 ...s-postal-code-input-field-is-not-hidden.md |    6 +-
 ...rent-slas-causing-divergence-in-tax-hub.md |   48 +
 ...for-some-countries-united-arab-emirates.md |   34 +
 ...pee-failed-to-create-product-variations.md |    6 +-
 ...oducts-ui-brokes-with-too-many-products.md |   52 +
 ...-catalog-v2-on-shipping-simulation-page.md |    6 +-
 ...nt-condition-does-not-appear-at-chekout.md |   51 +
 ...low-changes-on-the-conditional-template.md |   49 +
 ...rsion-when-accessing-via-ipad-on-safari.md |    6 +-
 .../es/sitemap-isnt-being-generatedupdated.md |   79 +
 ...eference-code-longer-than-50-characters.md |   52 +
 ...after-throttling-on-marketplace-catalog.md |   47 +
 ...e-update-does-not-update-v-version-tags.md |   52 +
 ...s-not-responding-with-the-text-property.md |   50 +
 ...c-is-not-being-disable-in-amazon-portal.md |    6 +-
 ...splay-mode-select-not-working-in-shelfs.md |    6 +-
 ...ving-similar-variations-with-substrings.md |   56 +
 .../es/sku-selector-with-multilpe-contexts.md |   52 +
 ...s-only-available-in-a-whitelabel-seller.md |    6 +-
 ...-accounts-with-autoapprove-flag-enabled.md |    6 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   57 +
 ...-value-tables-at-first-for-a-value-type.md |    6 +-
 ...o-cache-in-estimated-date-of-30-seconds.md |   51 +
 ...using-prop-infinite-as-always-on-mobile.md |   49 +
 ...talog-facets-api-have-different-formats.md |   58 +
 ...ail-template-redirects-user-to-404-page.md |   38 +
 ...-are-not-able-to-be-saved-on-my-account.md |    9 +-
 ...cted-when-viewed-through-safari-browser.md |   48 +
 ...king-properly-on-seller-portal-accounts.md |   53 +
 ...ipped-from-product-searches-or-indexing.md |   55 +
 .../some-unexpected-behavior-in-masterdata.md |   51 +
 ...error-is-displayed-in-the-catalog-admin.md |   52 +
 ...cessing-a-and-p-routes-in-portal-stores.md |   51 +
 ...incomplete-address-and-tried-to-edit-it.md |   50 +
 ...rent-on-stores-integrated-before-a-date.md |    6 +-
 ...fects-address-field-display-at-checkout.md |   48 +
 ...ses-internal-logistics-requests-to-fail.md |    6 +-
 ...t-be-used-for-cnpj-search-on-masterdata.md |    4 +-
 ...enumber-cause-postpurchase-flow-to-fail.md |   53 +
 ...or-radio-box-category-type-of-selection.md |    6 +-
 .../specifications-multiplied-on-catalog.md   |   54 +
 ...rect-for-products-with-multiple-sellers.md |    6 +-
 ...sactions-list-doesnt-match-actual-state.md |   46 +
 ...ompleted-even-after-receiving-error-500.md |   11 +-
 ...ows-invalid-commercial-condition-values.md |    6 +-
 ...ingunitbyean-returns-404-for-eans-with-.md |    4 +-
 ...-method-allows-to-insert-existent-refid.md |    6 +-
 ...ssions-considers-inactive-organizations.md |   48 +
 .../stucked-not-found-routes-on-platform.md   |   22 +-
 ...not-show-active-subscriptions-correctly.md |    6 +-
 ...subscription-event-history-out-of-order.md |   51 +
 ...-dashboard-with-conflicting-information.md |    6 +-
 ...ing-failure-or-masterdata-query-failure.md |   47 +
 ...ckuppointid-contains-special-characters.md |   48 +
 ...th-less-than-3-characters-does-not-work.md |    6 +-
 ...via-update-selected-address-information.md |   50 +
 ...-revert-the-zoom-causing-display-issues.md |   48 +
 ...senting-success-even-for-failed-actions.md |   45 +
 ...onyms-not-shown-in-the-explained-search.md |   38 +
 ...idering-seller-1-for-rule-sellers-limit.md |    6 +-
 ...ometimes-appear-on-list-format-plp-view.md |   49 +
 ...s-not-displayng-marketing-tags-dropdown.md |   51 +
 ...-discounts-when-manual-price-is-applied.md |   47 +
 ...re-than-once-when-using-assembly-option.md |   49 +
 ...otions-with-promotion-that-splits-items.md |   49 +
 ...-nominal-promotions-when-placing-orders.md |   48 +
 ...en-when-a-cart-has-two-selected-address.md |   47 +
 ...document-data-instead-of-customer-email.md |    6 +-
 ...nt-accept-special-characters-aside-from.md |   53 +
 ...-not-being-translated-using-site-editor.md |   53 +
 ...-not-being-translated-using-site-editor.md |   55 +
 ...-not-being-translated-using-site-editor.md |   56 +
 ...-marketplace-upon-approvals-reoccurence.md |   15 +-
 ...n-address-editing-on-romania-my-account.md |   22 +-
 ...-list-after-using-the-api-to-create-put.md |    6 +-
 ...lace-is-always-done-with-saleschannel-1.md |    6 +-
 ...-asynchronously-denying-payment-capture.md |   42 +
 ...s-not-work-with-save-card-functionality.md |   53 +
 ...data-containing-more-than-40-characters.md |   54 +
 ...redit-of-payment-method-customer-credit.md |    6 +-
 ...work-for-asynchronous-payment-providers.md |   23 +-
 ...-documents-typically-exceeding-millions.md |   48 +
 ...low-multiple-cancellation-with-giftcard.md |   21 +-
 ...ent-affiliation-for-debit-online-method.md |    6 +-
 ...eestoque-does-not-support-multilanguage.md |    6 +-
 ...-directly-from-the-mysubscriptions-area.md |    6 +-
 .../es/time-out-import-and-export-admin.md    |   15 +-
 ...gory-keywords-change-with-many-products.md |    6 +-
 ...ut-generating-internal-application-keys.md |   49 +
 ...s-preventing-to-check-the-inventory-log.md |   47 +
 ...tem-with-negative-value-in-inventory-ui.md |   71 +
 ...ion-error-with-unreachable-code-message.md |   41 +
 ...us-prior-to-the-state-that-it-should-be.md |   38 +
 ...anceling-when-one-of-the-card-is-denied.md |    8 +-
 ...n-status-approved-with-payment-canceled.md |   51 +
 ...t-consider-items-removed-from-the-order.md |    4 +-
 ...g-longer-than-expected-to-update-status.md |   42 +
 ...enied-by-error-card-not-enrolled-in-3ds.md |    6 +-
 ...count-to-implement-multilanguage-stores.md |   50 +
 ...ng-saved-in-vbase-and-not-into-rewriter.md |   74 +
 ...does-not-update-best-sla-choice-in-cart.md |    6 +-
 ...en-items-for-pickup-from-another-seller.md |   51 +
 ...en-selecting-to-add-a-new-address-first.md |    8 +-
 ...urs-in-the-place-order-internal-process.md |   45 +
 ...-with-subscriptions-but-it-wasnt-in-api.md |   48 +
 ...or-delivery-is-between-items-for-pickup.md |   51 +
 ...ed-when-using-order-replacement-feature.md |   48 +
 ...ests-for-each-keyfield-of-an-attachment.md |   54 +
 ...ons-that-had-payout-split-config-change.md |    6 +-
 ...to-log-in-through-the-google-app-on-ios.md |   34 +
 ...sing-protocol-encryption-protocol-ssl13.md |   54 +
 ...e-products-pdp-are-still-being-returned.md |   46 +
 ...ritization-by-diacritics-for-portuguese.md |   46 +
 ...-requests-and-components-being-reloaded.md |    6 +-
 ...ning-when-registeringupdating-a-product.md |   51 +
 ...-error-when-changing-edition-of-account.md |   56 +
 ...exportacaoimportacaoespecificacaov2aspx.md |    6 +-
 ...t-search-api-return-wrong-or-empty-data.md |   53 +
 ...default-value-after-changing-it-via-api.md |    6 +-
 ...s-does-not-trigger-automatic-indexation.md |   56 +
 .../update-users-name-in-the-login-section.md |    6 +-
 ...ue-to-lacking-property-on-get-resp-json.md |    6 +-
 ...-working-on-adminportalsitesdefaultcode.md |   53 +
 ...res-even-without-the-correct-permission.md |   56 +
 ...estricted-is-not-able-to-list-the-users.md |   56 +
 ...ant-access-gift-card-admin-looping-page.md |   45 +
 ...n-not-see-the-orders-on-my-account-page.md |   51 +
 ...-when-adding-the-first-item-to-the-cart.md |   48 +
 ...-list-affects-the-results-in-the-report.md |   25 +-
 ...nstep-to-1-causes-last-dots-to-be-empty.md |   51 +
 ...c-not-being-kept-on-the-url-after-login.md |    6 +-
 ...cartmutation-failing-when-large-payload.md |   49 +
 ...-mycards-are-not-automatically-canceled.md |    6 +-
 ...ote-not-found-on-vtex-id-on-the-profile.md |   63 +
 ...ion-not-sending-the-description-in-card.md |    6 +-
 ...t-being-sent-from-seller-to-marketplace.md |    6 +-
 ...ent-doesnt-work-properly-on-ios-devices.md |    6 +-
 ...eived-on-the-datalayer-every-other-time.md |   48 +
 ...-we-change-product-quantity-in-minicart.md |   49 +
 ...-product-feature-does-not-work-properly.md |    6 +-
 ...when-multiple-search-terms-are-provided.md |   54 +
 ...experience-some-trouble-on-firefox-89-0.md |    2 +-
 ...-does-not-work-before-acessing-checkout.md |   46 +
 ...clientid-field-of-the-giftcard-on-admin.md |    6 +-
 ...shows-success-even-when-it-isnt-working.md |    6 +-
 ...-not-fully-integrated-with-headless-cms.md |   41 +
 ...e-kit-is-shown-as-sold-out-on-searching.md |   42 +-
 ...ctname-without-the-sku-name-information.md |   47 +
 ...yed-in-the-order-and-email-notification.md |    6 +-
 ...er-its-not-possible-to-use-a-custom-one.md |    4 +-
 ...n-the-initial-message-is-not-translated.md |    6 +-
 ...ly-our-gateway-performs-a-double-refund.md |    6 +-
 ...ryslainminutes-calculation-returns-null.md |    6 +-
 ...-filters-options-doesnt-colapse-anymore.md |   49 +
 ...eater-than-1-in-intelligent-search-apis.md |   41 +
 ...nt-fields-under-the-same-original-value.md |   55 +
 ...hain-order-for-a-multilevel-marketplace.md |   46 +
 .../xml-currency-symbol-in-the-installment.md |    9 +-
 ...mation-defined-on-category-global-level.md |   44 +
 ...xml-installment-currency-does-not-apply.md |   49 +
 ...not-load-contents-for-unavailable-items.md |   52 +
 ...-product-name-flag-not-working-properly.md |   49 +
 .../es/xmls-returning-500-error.md            |   19 +-
 docs/known-issues/pt/.md                      |   22 +-
 ...3-error-for-all-urls-containing-develop.md |   47 +
 ...the-activate-if-possible-flag-unchecked.md |   45 +
 ...-be-returned-blank-in-the-catalog-admin.md |   46 +
 ...information-for-sessions-and-conversion.md |   43 +
 ...skuvincularvalorservicoaspx-not-working.md |   27 +-
 ...-not-available-when-creating-dictionary.md |    2 +-
 ...nvoice-address-returns-null-api-results.md |    6 +-
 ...he-shopper-opts-to-insert-a-new-address.md |   50 +
 ...-removing-essential-address-information.md |    6 +-
 ...n-buyer-has-can-add-shipping-permission.md |   46 +
 ...n-impersonated-using-vtex-telemarketing.md |   43 +
 ...auses-invalid-address-for-an-item-error.md |   54 +
 ...rder-has-more-than-one-product-centauro.md |    6 +-
 .../pt/admin-collection-brand-list-timeout.md |    6 +-
 ...rch-doesnt-recognize-profile-menu-items.md |   47 +
 ...n-how-to-improve-section-of-the-catalog.md |    4 +-
 ...nsion-as-jpg-even-when-the-image-is-png.md |    6 +-
 ...-engine-redirects-them-to-the-wrong-url.md |   51 +
 .../pt/admin-review-global-search.md          |   44 +
 docs/known-issues/pt/admin-timeout.md         |   48 +
 ...ut-country-disrupting-orderform-changes.md |    6 +-
 ...-generates-payment-authorization-denial.md |   52 +
 ...ethodtype-for-amex-when-using-apple-pay.md |   45 +
 ...ed-delivery-selection-appears-only-once.md |    6 +-
 ...-showing-in-vtexcmcproductimage-zoomon-.md |    4 +-
 .../pt/amazon-category-implementation.md      |    6 +-
 ...e-sending-product-to-amazon-marketplace.md |   49 +
 ...sku-is-not-being-logged-into-the-bridge.md |   48 +
 .../pt/amazon-global-category-not-working.md  |    6 +-
 ...n-integration-attribute-number-of-itens.md |    6 +-
 ...integration-stock-reservations-for-kits.md |    6 +-
 .../amazoncasacaso-erros-de-rastreamento.md   |   16 +-
 ...mate-returns-wrong-info-when-sc-is-null.md |    6 +-
 ...ts-does-not-return-additionalinfo-field.md |    6 +-
 ...-are-not-erased-when-you-delete-the-app.md |   59 +
 ...most-expensive-items-ui-not-saving-data.md |   49 +
 ...oved-skus-spreadsheet-not-showing-price.md |    6 +-
 ...t-allow-null-domainvalues-and-it-should.md |   65 +
 ...ation-on-field-domainvalues-not-working.md |    6 +-
 ...g-an-item-from-a-seller-with-attachment.md |   60 +
 ...are-not-updated-when-its-added-to-items.md |   43 +
 ...e-not-being-updated-in-meli-integration.md |   45 +
 ...pricing-logs-showing-unknow-information.md |   46 +
 ...payments-when-the-first-one-is-canceled.md |   43 +
 .../pt/auto-approve-api-accepts-any-values.md |    6 +-
 ...ng-suggestion-products-shown-with-delay.md |    6 +-
 ...tocomplete-not-answering-to-cold-starts.md |   19 +-
 ...i-removes-the-dot-from-the-product-name.md |   48 +
 ...culate-during-the-first-hour-of-the-day.md |    2 +-
 ...ic-payment-settlement-incorrectly-setup.md |   54 +
 ...not-occurring-due-to-special-characters.md |   45 +
 ...date-of-deliveries-tracking-by-correios.md |    9 +-
 ...mulation-for-no-stock-or-price-products.md |   47 +
 ...-missing-data-for-newly-created-address.md |   67 +
 ...r-of-routes-created-to-deliver-the-item.md |   41 +
 ...d-data-is-not-removed-after-logging-out.md |   47 +
 ...story-doesnt-work-in-the-website-domain.md |   41 +
 ...ng-geolocation-when-registering-address.md |   43 +
 ...-detail-ui-only-shows-100-first-sellers.md |   51 +
 ...e-doesnt-register-information-in-orders.md |   45 +
 ...count-at-checkout-in-the-website-domain.md |   42 +
 ...e-geocoordinates-to-calculate-region-id.md |   44 +
 ...rect-order-fob-integrating-with-carrier.md |    6 +-
 .../pt/b2w-freight-value-in-oms-vtex.md       |    6 +-
 ...n-searching-terms-with-directly-via-url.md |   20 +-
 ...arching-terms-with-through-autocomplete.md |   43 +
 ...-with-a-huge-quantity-of-reserved-items.md |   42 +
 ...ific-scenarios-with-merchandising-rules.md |   45 +
 ...en-the-promotion-is-a-buy-together-type.md |   35 +
 ...form-application-does-not-work-properly.md |   51 +
 ...rties-not-being-validated-on-legacy-cms.md |    6 +-
 ...s-are-not-searchable-on-the-brand-admin.md |   40 +
 ...hanges-to-the-intelligent-search-module.md |    4 +-
 ...cep-not-working-in-create-giftlist-form.md |    6 +-
 ...-mycards-page-not-translated-to-spanish.md |    6 +-
 ...k-on-the-first-try-in-fullcleanup-admin.md |   35 +
 ...oducts-not-to-load-on-the-front-timeout.md |   46 +
 ...figuration-in-organizationscost-centers.md |   43 +
 .../calculation-issue-in-comissionamount.md   |   40 +
 ...s-to-cart-from-store-framework-frontend.md |   45 +
 ...to-retry-payment-which-may-also-deny-it.md |   42 +
 ...rent-from-to-equal-to-with-a-collection.md |   36 +
 ...ormaspx-save-button-requires-two-clicks.md |    6 +-
 ...re-not-applied-after-3rd-category-level.md |   46 +
 ...nt-edit-the-name-of-the-styles-template.md |   43 +
 ...rd-brands-incorrectly-processed-as-visa.md |   42 +
 ...card-facebook-doesnt-save-some-settings.md |    6 +-
 ...order-doesnt-bring-the-assembly-options.md |   47 +
 ...-old-order-doesnt-bring-the-attachments.md |    6 +-
 ...ing-placed-as-expected-in-the-orderform.md |   52 +
 ...sing-sent-by-checkout-in-additionaldata.md |   41 +
 ...re-kept-in-orders-with-total-value-zero.md |   45 +
 ...if-store-cant-ship-to-all-the-countries.md |   43 +
 ...ent-do-not-receive-promotions-correctly.md |   45 +
 ...-not-consider-items-removed-from-orders.md |   51 +
 ...gunit-with-query-parameter-refid-return.md |    6 +-
 ...properly-to-space-at-the-end-of-strings.md |   45 +
 ...export-cannot-handle-t-and-s-characters.md |   45 +
 ...xport-for-attachment-cuts-50-characters.md |   51 +
 .../pt/catalog-filters-timeout.md             |   45 +
 ...ql-categoryinputtranslation-not-working.md |   43 +
 ...enerating-invalid-translation-documents.md |   44 +
 ...-report-total-section-calculation-error.md |    6 +-
 ...ion-xml-fiscal-code-field-not-rendering.md |   46 +
 ...alog-search-api-limited-to-2500-results.md |   45 +
 ...rn-information-for-products-unavailable.md |    6 +-
 ...slations-not-reflecting-on-the-frontend.md |   52 +
 .../pt/catalogv2-user-roles-not-applying.md   |    6 +-
 ...update-with-values-from-review-skus-tab.md |   47 +
 ...category-score-field-is-not-being-saved.md |    6 +-
 .../centauro-to-implement-centauro-envios.md  |    6 +-
 ...-to-myaccount-instead-of-the-order-page.md |   53 +
 ...-calculation-of-promotions-take-3-pay-2.md |    6 +-
 ...er-using-api-without-email-orderchanged.md |    6 +-
 ...tyles-admin-page-are-not-saved-properly.md |   46 +
 ...ccessories-is-not-triggering-indexation.md |   37 +
 ...-could-make-the-page-not-work-correctly.md |    6 +-
 ...without-shipping-address-on-the-ui-only.md |    6 +-
 ...-add-2-different-addresses-for-delivery.md |   46 +
 ...pty-shippingdata-when-using-geolocation.md |   43 +
 ...as-free-shipping-and-scheduled-delivery.md |    6 +-
 ...at-first-instant-for-specific-condition.md |   32 +-
 ...support-encoding-assembly-options-names.md |   42 +
 ...tly-sending-item-details-to-transaction.md |    6 +-
 ...ct-seller-when-merging-cart-information.md |   44 +
 ...tax-field-for-shipping-percentage-taxes.md |   42 +
 ...e-same-sku-receives-a-logistics-timeout.md |   46 +
 ...ress-for-shoppers-with-complete-profile.md |   45 +
 ...r-items-with-no-common-shipping-methods.md |   47 +
 ...orrect-sla-values-from-logistics-system.md |    8 +-
 ...-hyphen-in-the-postal-code-to-orderform.md |   45 +
 ...-the-user-switches-the-delivery-options.md |   44 +
 ...-there-is-only-pickup-address-available.md |    7 +-
 ...oesnt-handle-multiple-filters-correctly.md |   39 +
 ...ly-sometimes-in-global-checkout-setting.md |   48 +
 ...t-add-client-profile-is-performed-twice.md |   42 +
 ...with-the-same-names-as-the-default-ones.md |    6 +-
 ...is-not-accessible-through-the-new-admin.md |    2 +-
 .../pt/cms-legacy-collections-timeout.md      |   24 +-
 ...oving-value-from-the-unit-of-mass-field.md |    6 +-
 ...s-settings-role-not-working-as-expected.md |   52 +
 ...ble-menu-issues-rendering-all-the-items.md |    6 +-
 ...ot-allow-more-than-1000-skus-per-upload.md |    4 +-
 ...ustom-search-results-pages-in-b2b-suite.md |   45 +
 .../collections-dont-open-on-subaccounts.md   |   42 +
 ...-only-shows-1st-sku-of-inactive-product.md |   44 +
 ...-equal-to-on-the-campaign-audience-form.md |    6 +-
 ...h-special-characters-cannot-be-exported.md |   45 +
 ...ation-details-shows-only-20-collections.md |   50 +
 ...ng-as-expected-on-progressive-discounts.md |   46 +
 ...eation-due-to-failure-in-gatewaycallbak.md |   18 +-
 ...n-implemented-in-productsummary-for-ios.md |    4 +-
 ...nconsistency-in-deliveryshipping-prices.md |    6 +-
 ...components-in-a-kit-with-the-same-price.md |   44 +
 .../confirmed-order-email-not-being-sent.md   |    4 +-
 ...the-same-name-at-the-intelligent-search.md |   48 +
 ...violates-the-following-content-security.md |   51 +
 .../pt/cookie-broken-the-apisessions.md       |   16 +-
 ...-only-25-options-in-b2b-admin-customers.md |   44 +
 .../country-field-as-null-in-invoicedata.md   |   42 +
 ...ys-restricted-to-the-delivery-countries.md |    6 +-
 ...oupons-created-as-archived-temporarrily.md |   47 +
 ...oesnt-send-nulls-as-release-date-values.md |   43 +
 ...-does-not-update-the-items-stockbalance.md |   45 +
 ...-of-redirects-breaks-the-redirects-page.md |   46 +
 ...-of-the-csv-through-the-cli-doesnt-work.md |   45 +
 ...not-returned-on-the-explained-search-ui.md |   43 +
 .../crm-error-when-searching-with-spaces.md   |    4 +-
 ...y-symbol-does-not-follow-admin-language.md |   45 +
 .../custom-attribute-mapper-mercado-livre.md  |   44 +
 ...cms-not-working-with-more-than-one-html.md |   44 +
 ...mage-is-not-displayed-on-mobile-version.md |    6 +-
 ...tatus-at-mycredits-page-are-not-correct.md |    6 +-
 ...s-some-order-with-profileerroronloading.md |   43 +
 ...tion-is-not-saved-in-the-profile-system.md |   20 +-
 ...ipping-promotion-default-saleschannel-1.md |    6 +-
 ...v-without-validation-of-characters-type.md |    6 +-
 ...ed-payment-system-rendering-at-checkout.md |   40 +
 ...eadlocked-error-when-using-catalog-apis.md |   45 +
 ...-an-error-in-the-transactionstate-field.md |   23 +-
 ...-checkout-if-not-deactivated-previously.md |   42 +
 ...e-is-space-in-the-id-of-shipping-policy.md |   44 +
 ...with-lean-shipping-offering-invalid-sla.md |   47 +
 ...ing-on-seller-management-commissions-ui.md |   45 +
 .../diacritics-are-removed-on-catalogapi.md   |    6 +-
 ...rices-between-pdp-plp-and-checkout-cart.md |   45 +
 ...-specification-value-on-apis-and-portal.md |   50 +
 ...perly-when-prop-animated-is-set-as-true.md |    6 +-
 ...oupon-usage-count-on-oms-and-coupons-ui.md |   42 +
 ...al-order-value-and-total-products-value.md |    2 +-
 ...-settings-on-new-accounts-or-workspaces.md |   45 +
 ...transaction-list-and-on-the-transaction.md |   19 +-
 ...domly-getting-last-digit-deleted-on-ios.md |   44 +
 ...sspecification-values-on-the-same-level.md |    6 +-
 ...n-modal-to-switch-between-organizations.md |   44 +
 ...-ignored-when-approved-on-received-skus.md |   45 +
 ...th-automatic-capture-on-authorizedotnet.md |   54 +
 ...derest-are-not-respecting-early-capture.md |    6 +-
 ...filling-for-new-buyers-after-logging-in.md |   44 +
 ...autofilling-for-new-users-on-checkoutui.md |   61 +
 ...ate-using-the-b2b-organizations-feature.md |   42 +
 .../pt/encoding-error-in-apple-mail-app.md    |    2 +-
 ...ters-leads-to-unexpected-product-search.md |   45 +
 ...re-specific-global-category-persistente.md |    6 +-
 ...e-rejected-or-reviewed-by-offer-quality.md |   50 +
 ...ror-cancelling-customer-credit-invoices.md |   44 +
 ...a-promotion-excluding-more-than-1-brand.md |    6 +-
 .../error-closing-customer-credit-account.md  |   42 +
 ...xporting-entity-with-too-many-documents.md |   47 +
 ...ror-exporting-large-amount-of-giftcards.md |   18 +-
 .../error-exporting-prices-with-metadata.md   |   46 +
 .../pt/error-in-checkout-error-message.md     |    6 +-
 .../pt/error-in-custom-payments-creation.md   |   43 +
 ...ients-is-different-than-operation-value.md |   46 +
 ...lue-cannot-be-null-parameter-name-value.md |   46 +
 ...-cancelation-when-the-returncode-is-359.md |   46 +
 ...ui-after-requesting-the-invoice-via-app.md |   57 +
 ...trying-to-access-catalog-pages-on-admin.md |   47 +
 ...-sku-is-binded-on-vtexvtex-integrations.md |    6 +-
 ...-search-using-the-all-field-in-vtex-crm.md |   44 +
 .../pt/error-on-duplicate-payment-method.md   |   50 +
 ...gain-when-adding-images-via-site-editor.md |   45 +
 .../pt/error-sww-on-product-pdp.md            |   20 +-
 ...al-connector-for-pending-payment-status.md |    6 +-
 ...ng-an-index-if-the-fields-are-identical.md |   41 +
 ...delivery-type-when-seller-has-recursion.md |    6 +-
 ...-publishing-dynamic-storage-data-entity.md |   58 +
 ...en-running-vtex-link-for-the-first-time.md |    2 +-
 ...-transaction-with-2-cards-mercadopagov1.md |    6 +-
 ...r-when-trying-to-publish-or-link-an-app.md |   44 +
 docs/known-issues/pt/event-inconsistency.md   |   46 +-
 ...be-returned-once-the-order-has-a-change.md |    6 +-
 ...de-products-from-collection-not-working.md |   46 +
 ...edirects-not-pointing-back-to-old-route.md |   36 +
 ...xts-between-different-areas-or-products.md |   42 +
 ...sometimes-the-request-can-not-completed.md |   38 +
 ...xport-redirects-not-working-as-intended.md |   26 +-
 ...the-csv-in-the-sales-performance-module.md |    8 +-
 ...his-character-cut-in-the-image-url-rows.md |   46 +
 ...pdate-the-price-in-the-facebook-catalog.md |   47 +
 ...rumbs-page-title-and-additional-filters.md |   46 +
 ...ancellation-ppp-when-cancellationidnull.md |    6 +-
 ...s-the-go-to-payment-button-to-disappear.md |   43 +
 ...ststore-cart-merges-assembly-line-items.md |   43 +
 ...ng-not-removing-facets-set-to-ne-hidden.md |   46 +
 ...pi-considering-fuzzy-as-auto-as-default.md |   35 +
 ...return-seo-information-on-graphql-query.md |   44 +
 ...page-status-and-crashing-the-pagination.md |    6 +-
 ...n-trade-policy-not-reflecting-on-pdpplp.md |    6 +-
 ...ting-on-seller-management-ui-after-save.md |   31 +-
 ...any-change-in-order-management-settings.md |   28 +-
 ...y-in-master-data-lead-to-checkout-error.md |    6 +-
 ...not-update-all-the-files-only-the-first.md |   28 +-
 ...-performance-is-not-accepting-uppercase.md |    6 +-
 ...names-while-applying-additional-filters.md |   44 +
 ...t-considering-regionalized-availability.md |   47 +
 ...den-from-intelligent-search-admin-pages.md |   35 +
 ...to-old-component-version-on-site-editor.md |   35 +
 ...ll-the-profileshipping-data-at-checkout.md |   43 +
 ...orporatedocument-if-starts-with-letters.md |   42 +
 .../pt/first-subscription-cycle-is-skipped.md |   47 +
 ...rade-policy-1-when-saving-bundle-prices.md |    6 +-
 ...ace-integrate-an-order-erro-code-fmt010.md |    6 +-
 ...it-orders-outside-promotion-restriction.md |    6 +-
 ...-has-seller-groups-on-seller-management.md |   46 +
 ...egory-tree-on-itemcategory-in-datalayer.md |   42 +
 ...a-cant-be-informed-for-some-cultureinfo.md |    6 +-
 ...-for-pickup-points-loading-indefinitely.md |    2 +-
 ...eep-same-sku-order-when-changing-limits.md |   34 +-
 ...ist-multiple-orders-for-the-same-coupon.md |   40 +
 ...ed-offers-list-api-not-working-properly.md |    6 +-
 ...-by-refid-returning-null-when-not-found.md |    6 +-
 ...sku-by-ean-api-returns-only-active-skus.md |    6 +-
 ...from-component-sku-and-not-from-kit-sku.md |    6 +-
 .../pt/gift-card-creation-error-via-admin.md  |   39 +
 ...ith-the-date-chosen-when-it-was-created.md |    6 +-
 ...ty-id-in-response-to-create-transaction.md |   43 +
 ...-extra-backslash-when-calling-providers.md |    6 +-
 ...relationname-when-we-make-a-get-request.md |   43 +
 ...-a-generic-exception-if-it-has-no-price.md |    6 +-
 ...n-acting-alongside-other-gift-promotion.md |    6 +-
 ...add-credit-to-the-gift-card-through-api.md |    6 +-
 ...a-na-ui-nao-e-a-mesma-que-reflete-no-bd.md |    6 +-
 ...-in-catalog-outdated-compared-to-google.md |    6 +-
 ...onent-iframe-has-inconsistent-rendering.md |   44 +
 ...les-performance-not-working-as-expected.md |    6 +-
 ...s-cms-ignores-array-validation-settings.md |   48 +
 ...ng-do-not-work-on-seller-portal-catalog.md |   47 +
 ...ignored-after-one-purchase-is-completed.md |   46 +
 ...idget-not-shown-if-showmodal-is-enabled.md |   42 +
 ...oducts-if-import-is-made-based-on-skuid.md |   47 +
 ...-items-to-invoice-field-in-the-order-ui.md |   43 +
 ...e-tax-values-in-the-ui-appear-the-total.md |    6 +-
 ...partial-cancellation-with-mercadopagov1.md |    6 +-
 ...paypal-credentials-for-the-same-account.md |   19 +-
 ...tions-appearing-with-brazilian-currency.md |   43 +
 ...-organization-and-b2b-checkout-settings.md |   43 +
 ...ku-has-unit-multiplier-different-than-1.md |   25 +-
 .../pt/inconsistent-shipping-calculator.md    |    2 +-
 .../pt/incorrect-currency-on-payment-form.md  |    6 +-
 ...iscount-to-all-the-same-items-in-a-cart.md |   39 +
 ...ients-is-different-than-operation-value.md |   50 +
 ...rect-shippingestimatedate-for-order-fob.md |    6 +-
 ...e-registered-on-the-fulfillmentendpoint.md |   46 +
 .../pt/incorrectly-updated-inventory.md       |    6 +-
 ...the-highest-instead-of-the-lowest-price.md |    6 +-
 ...s-do-not-work-on-seller-portal-accounts.md |    6 +-
 ...are-same-skuid-in-different-array-items.md |   50 +
 .../pt/infocard-mobile-images-wont-apply.md   |   47 +
 ...s-from-servers-that-require-user-agents.md |   47 +
 ...ns-not-updating-automatically-on-pdpplp.md |   46 +
 ...e-via-image-url-does-not-work-correctly.md |   28 +-
 ...s-not-in-sync-with-store-configurations.md |   62 +
 ...ot-capturing-sales-events-for-faststore.md |   42 +
 ...t-settings-search-bar-is-case-sensitive.md |   39 +
 ...-normalizing-gender-in-portuguese-words.md |   45 +
 ...tate-changes-the-address-insertion-mode.md |   44 +
 ...ng-state-sends-the-wrong-payment-option.md |   43 +
 .../intermitent-site-editor-content-loss.md   |   49 +
 .../internalsearcherror-timeouts-on-portal.md |   45 +
 ...ilable-addresses-with-different-country.md |   47 +
 ...ory-notifications-to-indexer-are-cached.md |   50 +
 .../pt/inventory-reserved-items-error.md      |   34 +-
 ...egory-names-cause-page-not-found-errors.md |   44 +
 ...-not-work-as-expected-on-the-search-api.md |    6 +-
 ...d-search-for-searches-with-accent-marks.md |    6 +-
 ...e-on-translating-titles-for-some-facets.md |   26 +-
 ...operties-beginning-with-the-same-prefix.md |   43 +
 ...values-in-loyalty-gift-card-at-checkout.md |   42 +
 ...ss-leading-to-transaction-cancellations.md |   48 +
 .../pt/issues-with-my-account-links.md        |   45 +
 ...his-item-without-attachment-in-the-cart.md |   51 +
 ...create-a-path-using-content-type-via-ui.md |   47 +
 ...shown-in-seller-whitelabel-change-order.md |   44 +
 ...r-location-is-not-defined-with-no-stock.md |   45 +
 ...f-add-to-cart-event-in-google-analytics.md |   35 +
 ...-promotions-with-collections-associated.md |   50 +
 ...api-is-not-calculating-component-prices.md |   23 +-
 ...ight-can-be-overritten-by-apiwebservice.md |    6 +-
 ...a-request-when-the-accountid-is-missing.md |   23 +-
 ...eadsheet-error-on-new-collections-admin.md |   33 +-
 ...same-slas-but-in-a-different-ordination.md |   17 +-
 ...went-wrong-after-changing-pickup-points.md |   47 +
 ...activate-after-removing-items-from-cart.md |   44 +
 ...catalog-ui-delete-button-not-functional.md |   39 +
 ...-cmss-banner-custom-element-not-working.md |   54 +
 ...ting-products-wrongly-to-the-collection.md |    6 +-
 ...ntrols-do-not-consider-unit-multipliers.md |   46 +
 ...ntroller-texts-are-not-being-translated.md |    6 +-
 ...eadsheet-only-returning-active-services.md |   46 +
 ...y-setup-only-works-opening-in-a-new-tab.md |    6 +-
 ...r-when-translating-with-catalog-graphql.md |   90 ++
 ...tcher-doesnt-work-in-myvtex-environment.md |    4 +-
 ...with-password-cannot-be-undone-in-admin.md |   53 +
 ...es-not-work-when-productprice-as-0-zero.md |    6 +-
 ...yment-condition-requires-authentication.md |    4 +-
 ...specifications-from-another-marketplace.md |    6 +-
 ...marketplace-didnt-update-status-on-vtex.md |   47 +
 ...ine-luiza-some-skus-do-not-update-price.md |   51 +
 ...-deve-ser-igual-ou-menor-a-data-de-hoje.md |   48 +
 .../mandatory-service-working-as-optional.md  |   44 +
 ...using-multiple-coupons-feature-and-utms.md |   43 +
 ...value-when-campaign-audience-is-matched.md |   43 +
 ...lues-due-to-certain-purchase-conditions.md |   47 +
 ...snt-consider-manual-price-for-discounts.md |   43 +
 ...est-doesnt-consider-some-discount-types.md |   42 +
 ...ransactions-are-being-processed-as-visa.md |   43 +
 ...erdata-export-download-link-unavailable.md |   24 +-
 ...ved-skus-api-returning-invalid-sellerid.md |   49 +
 ...ng-height-width-weight-and-length-to-01.md |   46 +
 ...uctsku-name-contains-special-characters.md |   46 +
 ...hipping-discount-not-updating-pricetags.md |   47 +
 ...rrect-discount-when-using-the-same-item.md |   66 +
 ...cannot-be-changed-by-franchise-accounts.md |   43 +
 ...t-passing-a-symbol-or-special-character.md |   42 +
 ...o-meli-without-being-mapped-from-seller.md |   50 +
 ...ntegration-with-a-non-expected-behavior.md |    6 +-
 ...tomatic-messages-mercado-livre-messages.md |    8 +-
 ...enu-not-showing-the-orderid-information.md |   43 +
 ...aused-when-the-marketplace-ad-is-paused.md |   45 +
 ...-error-while-sending-the-order-tracking.md |   28 +-
 ...quotation-for-multiple-officialstoreids.md |   42 +
 ...ull-orders-not-creating-invoice-in-vtex.md |   43 +
 ...ct-value-when-client-has-coupon-on-meli.md |   44 +
 ...-errors-from-meli-429-too-many-requests.md |   51 +
 ...-for-peru-venezuela-equador-and-uruguai.md |   36 +
 ...ntegration-zipcodes-11111-meli-limaperu.md |    6 +-
 ...ding-product-specification-as-variation.md |   42 +
 ...tex-oms-for-multiples-accounts-scenario.md |   44 +
 ...hart-not-working-for-sizes-with-letters.md |   48 +
 ...eli-sizechart-issue-attribute-not-valid.md |   43 +
 .../pt/meli-update-stockprice-issue.md        |   43 +
 ...ybox-doesnt-update-shippingmode-for-me2.md |   56 +
 ...bridge-isnt-logging-some-error-messages.md |   48 +
 ...-not-showing-the-shippingid-information.md |   45 +
 .../pt/mercado-livre-mapper-attribute-size.md |   20 +-
 ...ve-underreview-validation-in-update-sku.md |   41 +
 ...bridge-isnt-logging-some-error-messages.md |   44 +
 ...working-for-the-facet-productclusterids.md |   48 +
 ...for-some-clients-in-customer-credit-api.md |   51 +
 ...ing-too-long-to-return-the-informations.md |   40 +
 ...n-field-cannot-be-deleted-through-admin.md |   45 +
 ...messages-only-appear-after-a-second-try.md |   49 +
 ...does-not-show-sku-specs-in-b2b-scenario.md |    6 +-
 ...sending-options-for-already-added-items.md |    6 +-
 ...-app-breaks-other-apps-of-the-same-type.md |    4 +-
 ...causes-antifraud-to-cancel-transactions.md |    6 +-
 ...price-facetfilter-at-intelligent-search.md |   44 +
 ...en-this-type-of-modal-are-configured-ok.md |    6 +-
 ...cated-divergences-setup-shipping-policy.md |    6 +-
 .../multiple-sku-promotion-api-not-working.md |    6 +-
 ...shivering-when-trying-to-add-a-new-card.md |   44 +
 ...field-filled-in-the-address-information.md |    6 +-
 ...tion-is-associated-with-a-pick-up-point.md |   24 +-
 ...-the-address-line-2-this-appear-as-null.md |    6 +-
 ...-spinner-button-is-not-working-properly.md |    4 +-
 ...hen-accessing-from-an-dependent-account.md |    6 +-
 ...eased-filter-is-not-working-for-exports.md |   36 -
 ...e-customers-id-document-for-example-cpf.md |    6 +-
 ...the-invoiced-value-on-return-items-page.md |    6 +-
 ...acters-and-causes-problem-in-order-flow.md |    2 +-
 ...e-and-lastdeliveryday-for-high-timecost.md |   72 +
 ...as-expected-with-subtraction-operations.md |   48 +
 ...distributed-among-all-items-in-the-cart.md |   26 +-
 ...plit-for-second-item-incorrect-discount.md |   62 +
 ...proper-detached-sku-on-pdp-in-a-new-tab.md |   44 +
 ...when-entity-has-more-than-10k-documents.md |    6 +-
 ...upted-file-when-there-are-no-skus-found.md |   44 +
 ...r-does-not-correspond-to-correct-number.md |    6 +-
 ...t-first-informs-an-address-for-delivery.md |   49 +
 ...pears-even-after-filled-until-save-data.md |   41 +
 ...er-only-captures-the-information-of-the.md |    6 +-
 ...bypricedesc-could-bring-the-wrong-order.md |   37 +
 ...dal-hook-affects-all-modals-on-the-page.md |   35 +
 ...orrectly-due-to-null-documenttype-field.md |   47 +
 ...ain-from-b2b-orders-history-doesnt-work.md |    6 +-
 ...ization-lessthan-100-goes-with-the-flow.md |   48 +
 ...r-card-info-causing-confusing-on-status.md |    6 +-
 ...o-price-divergence-on-fulfillment-layer.md |    6 +-
 ...erly-due-double-space-on-promotion-name.md |   25 +-
 ...uotes-in-the-promotion-name-or-sku-name.md |   55 +
 ...carrier-leaves-label-barcode-incomplete.md |   43 +
 ...-triggered-the-transaction-total-refund.md |    6 +-
 ...-and-original-order-have-the-same-value.md |   43 +
 ...nses-field-from-get-payment-details-api.md |   49 +
 ...ler-status-cancellationrequestdeniedffm.md |   55 +
 ...o-missing-payment-approved-notification.md |   48 +
 ...-the-items-and-refund-the-total-payment.md |   34 +
 ...-conectors-like-payment-app-or-redirect.md |    6 +-
 ...eled-but-the-payment-remains-authorized.md |   18 +-
 ...r-the-same-item-under-different-sellers.md |   22 +-
 ...id-scheduled-delivery-that-cant-be-used.md |   39 +-
 ...rs-data-even-for-authorized-credentials.md |   32 +-
 ...form-not-updating-after-order-is-placed.md |   43 +
 ...of-delivery-times-scheduled-at-checkout.md |    2 +-
 ...ps-from-the-root-category-does-not-work.md |    6 +-
 ...hat-dont-update-the-invoice-at-netshoes.md |    6 +-
 ...oice-value-in-output-invoice-validation.md |   51 +
 ...th-asterisks-in-the-address-and-profile.md |   49 +
 ...aceitems-is-not-opening-on-new-ui-admin.md |   32 +-
 ...nvoiceaddress-created-through-native-ui.md |   44 +-
 ...hen-uploading-a-new-version-not-working.md |    6 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   46 +
 ...n-performing-2-product-changes-in-a-row.md |   47 +
 ...-is-causing-us-to-misidentify-some-bins.md |   27 +-
 .../outdated-url-on-the-update-binding-ui.md  |   48 +
 ...iggered-twice-when-accessing-my-account.md |   42 +
 ...being-duplicated-in-custom-search-pages.md |   59 +
 ...h-results-not-working-on-giftlist-pages.md |    6 +-
 ...esnt-reset-when-changing-search-context.md |   50 +
 ...-cart-sometimes-returns-null-api-result.md |   21 +-
 ...cessing-transactions-as-prepaid-in-full.md |   44 +
 ...-with-swl-when-using-identical-typesids.md |    6 +-
 ...t-differ-from-active-payment-conditions.md |   18 +-
 ...ot-applied-in-the-b2b-checkout-settings.md |   62 +
 ...-assigned-after-approving-organizations.md |   46 +
 ...rice-comes-exclusively-from-manualprice.md |   46 +
 ...er-for-multilevel-omnichannel-inventory.md |    6 +-
 ...-respect-the-minimum-installment-amount.md |    6 +-
 ...kup-point-disregarded-based-on-priority.md |    6 +-
 ...eocoordinates-without-a-google-maps-key.md |   46 +
 ...ble-for-selection-in-shipping-policy-ui.md |    4 +-
 ...d-in-the-shipping-policy-after-deletion.md |   43 +
 ...d-after-searching-addresses-in-map-mode.md |    6 +-
 ...ickup-points-not-indexed-in-master-data.md |   47 +
 ...-same-id-pattern-show-product-available.md |   44 +
 ...the-same-cart-are-not-working-correctly.md |   47 +
 ...address-options-for-recurring-customers.md |   55 +
 ...-cookies-when-client-logout-at-checkout.md |   28 +-
 ...ging-out-when-using-callcenter-operator.md |    4 +-
 ...ssing-the-url-with-pagination-parameter.md |    6 +-
 ...-notification-in-the-ui-api-and-gateway.md |   43 +
 ...he-legacy-cms-collection-is-not-working.md |   49 +
 ...-of-spot-price-instead-of-regular-price.md |   49 +
 ...doesnt-correspond-to-the-search-results.md |   41 +
 .../pt/price-range-disregards-sales-policy.md |   39 +-
 ...-minimum-value-after-selecting-a-filter.md |   50 +
 ...-twice-and-one-is-from-assembly-options.md |   47 +
 ...-updates-with-cache-on-end-applications.md |   47 +
 ...-to-int32-max-value-on-change-price-api.md |   40 +
 ...ducts-keyword-not-considering-stopwords.md |   42 +
 ...-value-field-when-buying-with-two-cards.md |    6 +-
 ...with-phone-validation-on-mobile-devices.md |   35 +
 ...ayed-when-using-multiple-sales-channels.md |   68 +
 ...ed-in-the-pickups-in-cart-display-modal.md |    6 +-
 ...product-comissioning-inconsistent-cache.md |   65 +
 ...on-admin-changes-with-more-than-70-skus.md |   47 +
 ...date-api-allows-n-in-the-textlink-field.md |    6 +-
 ...m-doesnt-work-on-catalogs-redesigned-ui.md |   44 +
 ...ku-name-when-the-product-has-only-1-sku.md |    6 +-
 .../pt/product-page-sessions-not-working.md   |   43 +
 ...e-not-considering-default-seller-in-pdp.md |    6 +-
 ...r-not-working-on-seller-portal-accounts.md |    6 +-
 ...specification-export-index-out-of-range.md |   26 +-
 ...ection-module-assuming-incorrect-values.md |   35 +
 ...tion-module-does-not-list-root-category.md |   35 +
 ...oes-not-trigger-the-products-indexation.md |   44 +
 ...chresolver-is-incorrect-due-to-rounding.md |    6 +-
 ...d-when-the-productname-contains-numbers.md |   26 +-
 ...flag-and-discount-after-promotion-ended.md |   42 +
 ...wn-as-unavailable-at-intelligent-search.md |   42 +
 ...ted-with-duplicated-skus-on-the-catalog.md |   48 +
 ...ed-as-with-promotion-for-search-filters.md |   43 +
 ...sellers-are-appearing-in-the-end-of-plp.md |    6 +-
 ...form-allows-utf16-format-uploaddownload.md |    6 +-
 ...productsskus-import-does-not-support-lb.md |    6 +-
 ...complete-profile-with-ignoreprofiledata.md |   45 +
 ...ed-after-adding-client-preferences-data.md |   44 +
 ...equency-not-working-on-recurring-cycles.md |   42 +
 ...t-performance-or-lead-to-timeout-errors.md |   52 +
 ...hod-doesnt-works-for-whitelabel-sellers.md |   44 +
 ...thods-do-not-appear-on-the-product-page.md |    6 +-
 .../pt/promotions-microrounding-divergence.md |   93 ++
 ...-sorting-filtering-by-price-or-discount.md |   42 +
 ...s-ui-loading-wrong-currency-information.md |   29 +-
 ...ty-blockclass-from-infocard-not-working.md |    6 +-
 ...t-split-items-and-free-shipping-applied.md |   44 +
 ...-is-shown-in-the-license-manager-module.md |    6 +-
 ...ly-when-2-categories-have-the-same-name.md |    6 +-
 ...nd-is-stuck-on-freight-type-has-changed.md |   43 +
 .../put-price-overwrites-kit-price-logic.md   |   25 +-
 ...he-limit-value-when-user-quickly-clicks.md |    6 +-
 ...-wont-let-me-change-the-value-by-typing.md |   46 +
 ...h-after-reaching-max-available-qunatity.md |    6 +-
 ...-to-the-searched-zip-codes-availability.md |    2 +-
 ...n-the-sku-is-sold-by-more-than-1-seller.md |    6 +-
 ...ter-do-not-work-with-special-characters.md |   49 +
 ...ceived-skus-review-tab-missing-products.md |   51 +
 ...irects-are-being-counted-multiple-times.md |   46 +
 ...inks-when-using-in-the-final-of-the-url.md |   44 +
 ...avior-not-consistent-between-api-and-ui.md |   45 +
 ...es-us-to-misidentify-mastercard-as-visa.md |   49 +
 ...on-api-returns-seller-list-due-to-cache.md |   43 +
 ...-while-requesting-nonwhitelabel-sellers.md |    6 +-
 ...delivery-to-pickup-on-the-checkout-page.md |   45 +
 ...is-not-inactivating-skus-without-refids.md |    6 +-
 .../render-component-issues-on-site-editor.md |   25 +-
 ...ing-orders-with-different-sales-channel.md |   43 +
 .../pt/replicated-pending-payment-emails.md   |    6 +-
 ...g-is-inconsistent-when-running-ab-tests.md |   41 +
 .../pt/reserved-stock-in-invoiced-orders.md   |    6 +-
 ...queid-arrays-it-is-not-visible-properly.md |   42 +
 ...ve-a-different-value-added-to-gift-card.md |   12 +-
 .../rewriter-is-not-receiving-url-updates.md  |   57 +
 ...-items-with-unitmultiplier-other-than-1.md |   52 +
 ...terms-of-quantity-of-packages-and-items.md |   42 +
 ...-assigned-after-approving-organizations.md |   49 +
 ...ailing-for-custom-types-in-headless-cms.md |   46 +
 ...e-when-zooming-after-search-page-render.md |   45 +
 ...en-theres-a-slider-layout-on-background.md |   48 +
 .../pt/search-analytics-duplicated-events.md  |   60 +
 ...een-versions-withwithout-funnel-metrics.md |   46 +
 ...-skus-for-fqspecificationfilter-queries.md |    6 +-
 ...login-in-using-the-call-center-operator.md |    6 +-
 ...rl-after-navigating-through-suggestions.md |   40 +
 ...the-operator-and-for-trigger-conditions.md |   50 +
 ...rch-by-ean-not-working-on-received-skus.md |   41 +-
 ...account-management-when-using-b2b-suite.md |   53 +
 ...-price-range-yielding-incorrect-results.md |    6 +-
 ...lations-over-already-translated-content.md |   48 +
 ...t-when-the-value-contains-a-plus-symbol.md |   63 +
 ...-updated-only-after-refreshing-the-page.md |   28 +-
 ...sion-updates-does-not-index-binded-skus.md |   51 +
 ...-creation-does-not-add-selected-sellers.md |   51 +
 ...price-condition-not-working-as-expected.md |   47 +
 ...-specifications-dropdown-malfunctioning.md |    6 +-
 ...s-to-reindex-when-inactivating-a-seller.md |   43 +
 ...ced-with-problem-in-the-payment-capture.md |   60 +
 ...ype-name-field-wrongly-returned-via-api.md |   45 +
 ...ces-are-not-updated-when-added-to-items.md |    4 +-
 ...hen-they-are-not-in-the-same-path-level.md |   44 +
 ...esnt-update-expiration-period-of-quotes.md |   51 +
 ...-frozen-when-trying-to-select-an-option.md |   44 +
 ...layed-as-active-in-the-new-logistics-ui.md |   46 +
 ...deliver-on-weekends-is-being-considered.md |    6 +-
 ...es-not-show-message-error-on-simulation.md |    6 +-
 ...does-not-use-sla-name-for-display-in-ui.md |    6 +-
 ...s-package-split-for-pickup-and-shipping.md |   43 +
 ...ng-the-date-when-its-scheduled-delivery.md |    6 +-
 ...g-the-price-when-its-scheduled-delivery.md |   18 +-
 ...s-postal-code-input-field-is-not-hidden.md |    6 +-
 ...rent-slas-causing-divergence-in-tax-hub.md |   42 +
 ...for-some-countries-united-arab-emirates.md |   34 +
 ...pee-failed-to-create-product-variations.md |    6 +-
 ...oducts-ui-brokes-with-too-many-products.md |   49 +
 ...-catalog-v2-on-shipping-simulation-page.md |    6 +-
 ...nt-condition-does-not-appear-at-chekout.md |   46 +
 ...low-changes-on-the-conditional-template.md |   46 +
 ...rsion-when-accessing-via-ipad-on-safari.md |    6 +-
 .../pt/sitemap-isnt-being-generatedupdated.md |   76 +
 ...eference-code-longer-than-50-characters.md |   35 +
 ...after-throttling-on-marketplace-catalog.md |   44 +
 ...e-update-does-not-update-v-version-tags.md |   46 +
 ...s-not-responding-with-the-text-property.md |   45 +
 ...c-is-not-being-disable-in-amazon-portal.md |    6 +-
 ...splay-mode-select-not-working-in-shelfs.md |    6 +-
 ...ving-similar-variations-with-substrings.md |   35 +
 .../pt/sku-selector-with-multilpe-contexts.md |   47 +
 ...s-only-available-in-a-whitelabel-seller.md |    6 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   32 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   52 +
 ...-value-tables-at-first-for-a-value-type.md |    6 +-
 ...o-cache-in-estimated-date-of-30-seconds.md |   48 +
 ...using-prop-infinite-as-always-on-mobile.md |   35 +
 ...talog-facets-api-have-different-formats.md |   52 +
 ...ail-template-redirects-user-to-404-page.md |   44 +
 ...-are-not-able-to-be-saved-on-my-account.md |   28 +-
 ...cted-when-viewed-through-safari-browser.md |   35 +
 ...king-properly-on-seller-portal-accounts.md |   48 +
 ...ipped-from-product-searches-or-indexing.md |   50 +
 .../some-unexpected-behavior-in-masterdata.md |   41 +
 ...error-is-displayed-in-the-catalog-admin.md |   47 +
 ...cessing-a-and-p-routes-in-portal-stores.md |   46 +
 ...incomplete-address-and-tried-to-edit-it.md |   45 +
 ...rent-on-stores-integrated-before-a-date.md |    6 +-
 ...fects-address-field-display-at-checkout.md |   43 +
 ...ses-internal-logistics-requests-to-fail.md |    6 +-
 ...t-be-used-for-cnpj-search-on-masterdata.md |    4 +-
 ...enumber-cause-postpurchase-flow-to-fail.md |   48 +
 ...or-radio-box-category-type-of-selection.md |    6 +-
 .../specifications-multiplied-on-catalog.md   |   41 +
 ...rect-for-products-with-multiple-sellers.md |    6 +-
 ...sactions-list-doesnt-match-actual-state.md |   43 +
 ...ompleted-even-after-receiving-error-500.md |   18 +-
 ...ows-invalid-commercial-condition-values.md |    6 +-
 ...ingunitbyean-returns-404-for-eans-with-.md |    4 +-
 ...-method-allows-to-insert-existent-refid.md |    6 +-
 ...ssions-considers-inactive-organizations.md |   43 +
 .../stucked-not-found-routes-on-platform.md   |   31 +-
 ...not-show-active-subscriptions-correctly.md |    6 +-
 ...subscription-event-history-out-of-order.md |   46 +
 ...-dashboard-with-conflicting-information.md |    6 +-
 ...ing-failure-or-masterdata-query-failure.md |   43 +
 ...ckuppointid-contains-special-characters.md |   43 +
 ...th-less-than-3-characters-does-not-work.md |    6 +-
 ...via-update-selected-address-information.md |   45 +
 ...-revert-the-zoom-causing-display-issues.md |   45 +
 ...senting-success-even-for-failed-actions.md |   42 +
 ...onyms-not-shown-in-the-explained-search.md |   42 +
 ...idering-seller-1-for-rule-sellers-limit.md |    6 +-
 ...ometimes-appear-on-list-format-plp-view.md |   46 +
 ...s-not-displayng-marketing-tags-dropdown.md |   46 +
 ...-discounts-when-manual-price-is-applied.md |   41 +
 ...re-than-once-when-using-assembly-option.md |   43 +
 ...otions-with-promotion-that-splits-items.md |   44 +
 ...-nominal-promotions-when-placing-orders.md |   43 +
 ...en-when-a-cart-has-two-selected-address.md |   42 +
 ...document-data-instead-of-customer-email.md |    6 +-
 ...nt-accept-special-characters-aside-from.md |   48 +
 ...-not-being-translated-using-site-editor.md |   50 +
 ...-not-being-translated-using-site-editor.md |   52 +
 ...-not-being-translated-using-site-editor.md |   53 +
 ...-marketplace-upon-approvals-reoccurence.md |   16 +-
 ...n-address-editing-on-romania-my-account.md |   26 +-
 ...-list-after-using-the-api-to-create-put.md |    6 +-
 ...lace-is-always-done-with-saleschannel-1.md |    6 +-
 ...-asynchronously-denying-payment-capture.md |   43 +
 ...s-not-work-with-save-card-functionality.md |   51 +
 ...data-containing-more-than-40-characters.md |   48 +
 ...redit-of-payment-method-customer-credit.md |    6 +-
 ...work-for-asynchronous-payment-providers.md |   36 +-
 ...-documents-typically-exceeding-millions.md |   44 +
 ...low-multiple-cancellation-with-giftcard.md |   17 +-
 ...ent-affiliation-for-debit-online-method.md |    6 +-
 ...eestoque-does-not-support-multilanguage.md |    6 +-
 ...-directly-from-the-mysubscriptions-area.md |    6 +-
 .../pt/time-out-import-and-export-admin.md    |   12 +-
 ...gory-keywords-change-with-many-products.md |    6 +-
 ...ut-generating-internal-application-keys.md |   44 +
 ...s-preventing-to-check-the-inventory-log.md |   44 +
 ...tem-with-negative-value-in-inventory-ui.md |   48 +
 ...ion-error-with-unreachable-code-message.md |   44 +
 ...us-prior-to-the-state-that-it-should-be.md |   35 +
 ...anceling-when-one-of-the-card-is-denied.md |    8 +-
 ...n-status-approved-with-payment-canceled.md |   48 +
 ...t-consider-items-removed-from-the-order.md |    4 +-
 ...g-longer-than-expected-to-update-status.md |   43 +
 ...enied-by-error-card-not-enrolled-in-3ds.md |    6 +-
 ...count-to-implement-multilanguage-stores.md |   45 +
 ...ng-saved-in-vbase-and-not-into-rewriter.md |   68 +
 ...does-not-update-best-sla-choice-in-cart.md |    6 +-
 ...en-items-for-pickup-from-another-seller.md |   46 +
 ...en-selecting-to-add-a-new-address-first.md |   22 +-
 ...urs-in-the-place-order-internal-process.md |   42 +
 ...-with-subscriptions-but-it-wasnt-in-api.md |   44 +
 ...or-delivery-is-between-items-for-pickup.md |   46 +
 ...ed-when-using-order-replacement-feature.md |   43 +
 ...ests-for-each-keyfield-of-an-attachment.md |   49 +
 ...ons-that-had-payout-split-config-change.md |    6 +-
 ...to-log-in-through-the-google-app-on-ios.md |   45 +
 ...sing-protocol-encryption-protocol-ssl13.md |   49 +
 ...e-products-pdp-are-still-being-returned.md |   43 +
 ...ritization-by-diacritics-for-portuguese.md |   41 +
 ...-requests-and-components-being-reloaded.md |    6 +-
 ...ning-when-registeringupdating-a-product.md |   46 +
 ...-error-when-changing-edition-of-account.md |   53 +
 ...exportacaoimportacaoespecificacaov2aspx.md |    6 +-
 ...t-search-api-return-wrong-or-empty-data.md |   48 +
 ...default-value-after-changing-it-via-api.md |    6 +-
 ...s-does-not-trigger-automatic-indexation.md |   51 +
 .../update-users-name-in-the-login-section.md |    6 +-
 ...ue-to-lacking-property-on-get-resp-json.md |    6 +-
 ...-working-on-adminportalsitesdefaultcode.md |   47 +
 ...res-even-without-the-correct-permission.md |   53 +
 ...estricted-is-not-able-to-list-the-users.md |   51 +
 ...ant-access-gift-card-admin-looping-page.md |   40 +
 ...n-not-see-the-orders-on-my-account-page.md |   48 +
 ...-when-adding-the-first-item-to-the-cart.md |   43 +
 ...-list-affects-the-results-in-the-report.md |   33 +-
 ...nstep-to-1-causes-last-dots-to-be-empty.md |   46 +
 ...c-not-being-kept-on-the-url-after-login.md |    6 +-
 ...cartmutation-failing-when-large-payload.md |   46 +
 ...-mycards-are-not-automatically-canceled.md |    6 +-
 ...ote-not-found-on-vtex-id-on-the-profile.md |   57 +
 ...ion-not-sending-the-description-in-card.md |    6 +-
 ...t-being-sent-from-seller-to-marketplace.md |    6 +-
 ...ent-doesnt-work-properly-on-ios-devices.md |    6 +-
 ...eived-on-the-datalayer-every-other-time.md |   43 +
 ...-we-change-product-quantity-in-minicart.md |   44 +
 ...-product-feature-does-not-work-properly.md |    6 +-
 ...when-multiple-search-terms-are-provided.md |   49 +
 ...experience-some-trouble-on-firefox-89-0.md |    2 +-
 ...-does-not-work-before-acessing-checkout.md |   44 +
 ...clientid-field-of-the-giftcard-on-admin.md |    6 +-
 ...shows-success-even-when-it-isnt-working.md |    6 +-
 ...-not-fully-integrated-with-headless-cms.md |   42 +
 ...e-kit-is-shown-as-sold-out-on-searching.md |   42 +-
 ...ctname-without-the-sku-name-information.md |   42 +
 ...yed-in-the-order-and-email-notification.md |    6 +-
 ...er-its-not-possible-to-use-a-custom-one.md |   20 +-
 ...n-the-initial-message-is-not-translated.md |    6 +-
 ...ly-our-gateway-performs-a-double-refund.md |    6 +-
 ...ryslainminutes-calculation-returns-null.md |    6 +-
 ...-filters-options-doesnt-colapse-anymore.md |   44 +
 ...eater-than-1-in-intelligent-search-apis.md |   44 +
 ...nt-fields-under-the-same-original-value.md |   50 +
 ...hain-order-for-a-multilevel-marketplace.md |   41 +
 .../xml-currency-symbol-in-the-installment.md |    9 +-
 ...mation-defined-on-category-global-level.md |   41 +
 ...xml-installment-currency-does-not-apply.md |   45 +
 ...not-load-contents-for-unavailable-items.md |   49 +
 ...-product-name-flag-not-working-properly.md |   47 +
 .../pt/xmls-returning-500-error.md            |   20 +-
 docs/tracks/en/.md                            |    7 +-
 .../en/access-to-the-customers-last-cart.md   |    2 +-
 docs/tracks/en/accounts-and-architecture.md   |  125 ++
 docs/tracks/en/add-on-products.md             |  134 ++
 docs/tracks/en/add-pickup-points.md           |    2 +-
 docs/tracks/en/add-sku-specifications.md      |    8 +-
 docs/tracks/en/adding-a-fixed-price.md        |    8 +-
 docs/tracks/en/adding-a-loading-dock.md       |    2 +-
 docs/tracks/en/adding-a-price-rule.md         |    6 +-
 .../adding-extra-text-to-the-order-print.md   |    4 +-
 .../tracks/en/adding-new-stores-to-instore.md |    8 +-
 .../en/adding-product-specifications.md       |    8 +-
 docs/tracks/en/adding-products.md             |    2 +-
 docs/tracks/en/adding-skus.md                 |    6 +-
 docs/tracks/en/adding-vendors.md              |    4 +-
 docs/tracks/en/adding-warehouses.md           |    2 +-
 docs/tracks/en/allowing-order-replacement.md  |    8 +-
 docs/tracks/en/amazon-account-settings.md     |    4 +-
 docs/tracks/en/amazon.md                      |    2 +-
 docs/tracks/en/apple-pay.md                   |   53 +
 .../associating-a-template-with-a-layout.md   |    2 +-
 docs/tracks/en/autocomplete-search.md         |    8 +-
 docs/tracks/en/availability.md                |    6 +-
 docs/tracks/en/b2b-form.md                    |    6 +-
 docs/tracks/en/backend-integrations.md        |  408 +++++
 docs/tracks/en/banners-en.md                  |    2 +-
 docs/tracks/en/barcode-reading.md             |    2 +-
 .../en/basic-vtex-io-developer-setup.md       |    6 +-
 .../en/best-practices-for-testing-instore.md  |    2 +-
 docs/tracks/en/billing-support.md             |   51 +
 docs/tracks/en/canceling-an-order.md          |   12 +-
 docs/tracks/en/cart-transfer-and-capture.md   |    6 +-
 docs/tracks/en/cart-transfer.md               |    6 +-
 docs/tracks/en/catalog-architecture.md        |    2 +-
 docs/tracks/en/catalog-concept-definition.md  |    2 +-
 docs/tracks/en/centauro-marketplace.md        |    4 +-
 .../en/changing-the-instore-language.md       |    2 +-
 docs/tracks/en/cms-vtex-io.md                 |   10 +-
 docs/tracks/en/commercial-support.md          |   35 +
 ...uracao-da-estrutura-para-suporte-humano.md |    6 +-
 .../en/configure-customer-identification.md   |   10 +-
 ...configure-integration-of-pick-up-points.md |    8 +-
 docs/tracks/en/configure-integration.md       |    7 +-
 .../en/configure-warranty-in-via-varejo.md    |    6 +-
 .../en/configuring-a-payment-condition.md     |   47 +-
 docs/tracks/en/configuring-banners.md         |    9 +-
 ...nfiguring-cash-payments-through-instore.md |    2 +-
 .../tracks/en/configuring-dafiti-connector.md |    4 +-
 ...onfiguring-livelo-price-divergence-rule.md |   18 +
 .../en/configuring-login-with-facebook.md     |    2 +-
 .../en/configuring-login-with-google.md       |    2 +-
 .../en/configuring-merchandising-rules.md     |   10 +-
 .../en/configuring-payment-connectors.md      |   42 +-
 ...guring-physical-stores-as-pickup-points.md |    4 +-
 ...onfiguring-price-divergence-rule-dafiti.md |    4 +-
 ...ing-price-divergence-rule-mercado-libre.md |    4 +-
 .../configuring-price-divergence-rule-via.md  |    4 +-
 ...configuring-rappi-price-divergence-rule.md |   18 +
 docs/tracks/en/configuring-redirect.md        |    9 +-
 docs/tracks/en/configuring-ship-from-store.md |    8 +-
 docs/tracks/en/configuring-synonyms.md        |   45 +-
 .../en/configuring-the-amazon-integration.md  |    4 +-
 .../en/configuring-the-connector-b2w.md       |    4 +-
 docs/tracks/en/configuring-the-connector.md   |   14 +-
 .../en/configuring-the-integration-rappi.md   |   18 +
 ...-integration-with-fbe-in-the-vtex-admin.md |    6 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |    2 +-
 docs/tracks/en/configuring-the-integration.md |   18 +
 .../en/configuring-the-relevance-feature.md   |    6 +-
 docs/tracks/en/contract-termination.md        |   22 +
 docs/tracks/en/corporate-digital-account.md   |    6 +-
 docs/tracks/en/create-brands.md               |    2 +-
 docs/tracks/en/create-product-feed.md         |    6 +-
 docs/tracks/en/creating-accounts.md           |  127 +-
 docs/tracks/en/creating-and-editing-users.md  |    6 +-
 ...ating-merchandising-rules-visual-editor.md |   98 ++
 .../en/creating-or-editing-a-page-template.md |    4 +-
 docs/tracks/en/creating-regular-promotions.md |  227 +--
 docs/tracks/en/credit-card-payment-flow.md    |    9 +-
 docs/tracks/en/customer-identification.md     |    2 +-
 docs/tracks/en/customizing-instore.md         |   14 +-
 docs/tracks/en/customizing-styles.md          |    4 +-
 docs/tracks/en/customizing-templates.md       |    2 +-
 docs/tracks/en/dafiti-marketplace.md          |    4 +-
 docs/tracks/en/dashboard.md                   |    8 +-
 docs/tracks/en/data-protection-roles.md       |   85 ++
 ...ne-payment-methods-displayed-on-instore.md |    6 +-
 .../en/defining-centauro-trade-policy.md      |    4 +-
 .../tracks/en/defining-dafiti-trade-policy.md |    4 +-
 .../en/defining-netshoes-trade-policy.md      |    4 +-
 ...fining-the-google-shopping-trade-policy.md |   41 +-
 .../en/defining-the-shipping-strategy-via.md  |    4 +-
 docs/tracks/en/delivery.md                    |    8 +-
 .../en/detaching-skus-by-specification.md     |    2 +-
 docs/tracks/en/digital-wallet-e-wallet.md     |   23 +
 .../enabling-2-factor-authentication-login.md |   16 +-
 docs/tracks/en/enabling-a-sales-rep-code.md   |    4 +-
 .../enabling-cart-transfer-between-devices.md |    6 +-
 .../en/enabling-product-recommendations.md    |    2 +-
 docs/tracks/en/endless-aisle.md               |   14 +-
 docs/tracks/en/explained-search.md            |    2 +-
 docs/tracks/en/extensions-hub-1.md            |    2 +-
 docs/tracks/en/extensions-hub-app-store.md    |    6 +-
 docs/tracks/en/extensions-hub-partners.md     |   19 +
 docs/tracks/en/filter-orders-by-vendor.md     |    4 +-
 docs/tracks/en/filters.md                     |   17 +-
 docs/tracks/en/frontend-implementation.md     |  322 ++++
 docs/tracks/en/frontend.md                    |    2 +-
 .../en/getting-started-with-logistics.md      |    2 +-
 docs/tracks/en/go-live-process.md             |   12 +-
 docs/tracks/en/google-pay.md                  |  111 ++
 docs/tracks/en/google-shopping-marketplace.md |    6 +-
 ...hide-product-suggestions-recommendation.md |    2 +-
 .../how-a-split-payment-transaction-works.md  |    2 +-
 .../how-does-vtex-intelligent-search-work.md  |  145 +-
 .../en/how-the-payments-module-works.md       |   32 +-
 ...ustom-text-in-the-printout-of-the-order.md |    4 +-
 ...change-the-sales-policy-used-by-instore.md |    4 +-
 .../en/how-to-configure-a-custom-payment.md   |    8 +-
 ...nfigure-a-device-for-printout-the-order.md |    4 +-
 ...-and-edit-transactional-email-templates.md |    8 +-
 docs/tracks/en/how-vtex-support-works.md      |   43 +
 docs/tracks/en/import-orders-from-lengow.md   |    2 +-
 ...uding-order-variables-in-email-template.md |    4 +-
 docs/tracks/en/indexing-history.md            |   66 +
 .../en/initializing-your-store-theme.md       |    6 +-
 .../inserting-and-configuring-placeholders.md |    6 +-
 docs/tracks/en/installation-and-setup.md      |    8 +-
 docs/tracks/en/installing-customer-credit.md  |   26 +-
 docs/tracks/en/instore-basic-settings.md      |    4 +-
 docs/tracks/en/instore-customizations.md      |    6 +-
 docs/tracks/en/instore-login.md               |    2 +-
 docs/tracks/en/instore.md                     |   30 +-
 ...ating-instore-to-a-new-payment-acquirer.md |    2 +-
 docs/tracks/en/integration-settings.md        |   20 +-
 docs/tracks/en/intelligent-synonyms.md        |   67 +
 docs/tracks/en/intro-to-vtex-io-builders.md   |    2 +-
 docs/tracks/en/introduction-to-vtex-io.md     |    2 +-
 docs/tracks/en/introduction-to-vtex.md        |   45 +
 .../inventory-and-shipping-module-overview.md |    2 +-
 docs/tracks/en/legacy-cms-portal.md           |    4 +-
 docs/tracks/en/live-support.md                |   16 +-
 docs/tracks/en/livelo-integration-overview.md |   18 +
 .../en/livelo-integration-registration.md     |   18 +
 docs/tracks/en/magazine-luiza-marketplace.md  |    4 +-
 docs/tracks/en/managing-accounts.md           |  117 +-
 .../en/managing-customer-credit-invoices.md   |   73 +
 .../managing-sales-associates-in-instore.md   |   50 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |    2 +-
 docs/tracks/en/mapping-colors-and-sizes.md    |    2 +-
 ...egories-and-attributes-to-mercado-libre.md |    4 +-
 ...pping-product-categories-and-attributes.md |   18 +
 ...rappi-product-categories-and-attributes.md |   18 +
 docs/tracks/en/mercado-libre-marketplace.md   |    6 +-
 docs/tracks/en/merchandising-rules.md         |   39 +-
 docs/tracks/en/next-steps.md                  |   28 +
 docs/tracks/en/opening-tickets.md             |   35 +
 docs/tracks/en/order-delivery.md              |    2 +-
 docs/tracks/en/order-flow.md                  |   14 +-
 docs/tracks/en/other-vtex-module-settings.md  |  105 ++
 docs/tracks/en/overview-intelligent-search.md |   15 +-
 docs/tracks/en/partial-invoices.md            |    7 +-
 docs/tracks/en/payment.md                     |   16 +-
 docs/tracks/en/personal-data.md               |   47 +
 docs/tracks/en/planning-the-go-live.md        |  195 +++
 .../en/preco-base-definicao-de-conceito.md    |    2 +-
 .../en/preco-fixo-definicao-de-conceito.md    |    4 +-
 .../en/prerequisites-for-using-instore.md     |   25 +-
 docs/tracks/en/prices-module-overview.md      |    4 +-
 docs/tracks/en/pricing-system-architecture.md |   18 +-
 docs/tracks/en/printing-an-order-summary.md   |   10 +-
 docs/tracks/en/product-details.md             |    2 +-
 .../product-integration-errors-with-amazon.md |  156 ++
 .../en/promotions-for-specific-scenarios.md   |   27 +-
 docs/tracks/en/rappi-integration-overview.md  |   18 +
 .../en/rappi-integration-registration.md      |   18 +
 docs/tracks/en/receivables-management.md      |    6 +-
 .../en/register-mercado-livre-integration.md  |    4 +-
 .../registering-the-carrefour-integration.md  |    4 +-
 .../registering-the-centauro-integration.md   |    4 +-
 docs/tracks/en/registering-the-integration.md |    6 +-
 .../registering-the-netshoes-integration.md   |    4 +-
 docs/tracks/en/relevance.md                   |  103 +-
 .../en/reports-vtex-intelligent-search.md     |    4 +-
 docs/tracks/en/sale-confirmed.md              |    2 +-
 docs/tracks/en/sales-channel-mapping.md       |    4 +-
 ...eduled-deliveries-and-delivery-capacity.md |    8 +-
 docs/tracks/en/search-settings.md             |   41 +-
 docs/tracks/en/seeing-order-details.md        |   15 +-
 .../en/sending-product-data-to-dafiti.md      |    4 +-
 docs/tracks/en/sending-products-to-amazon.md  |  105 +-
 .../tracks/en/sending-products-to-facebook.md |   12 +-
 docs/tracks/en/sending-products-to-via.md     |    6 +-
 ...etting-instore-up-in-a-store-easy-setup.md |   12 +-
 ...setting-up-a-marketplace-trade-policy-2.md |    4 +-
 ...p-a-marketplace-trade-policy-skyhub-b2w.md |    4 +-
 ...up-a-marketplace-trade-policy-viavarejo.md |    4 +-
 .../setting-up-a-marketplace-trade-policy.md  |    4 +-
 ...app-linking-for-payments-app-in-instore.md |    2 +-
 .../en/setting-up-credit-direct-sale.md       |    8 +-
 .../setting-up-payment-methods-for-instore.md |    8 +-
 docs/tracks/en/setting-up-the-app.md          |  122 +-
 ...ting-up-the-logistics-for-mercado-livre.md |    4 +-
 .../setting-up-the-order-summary-printing.md  |    8 +-
 docs/tracks/en/settings-on-via-marketplace.md |    6 +-
 ...pping-cart-using-instore-social-selling.md |    8 +-
 docs/tracks/en/shipping-strategies.md         |    2 +-
 docs/tracks/en/specifications-mapping.md      |    4 +-
 docs/tracks/en/store-development.md           |    2 +-
 docs/tracks/en/subject-rights.md              |   31 +
 .../technical-and-administrative-measures.md  |   56 +
 docs/tracks/en/technical-support.md           |   33 +
 docs/tracks/en/teste-1.md                     |   64 +-
 docs/tracks/en/the-reservation.md             |    2 +-
 docs/tracks/en/unified-commerce-101.md        |   22 +-
 docs/tracks/en/unified-commerce.md            |   56 +
 docs/tracks/en/unified-search.md              |   50 +-
 .../en/update-and-import-product-feed.md      |    2 +-
 docs/tracks/en/using-custom-controls.md       |    2 +-
 docs/tracks/en/via-varejo-marketplace.md      |    6 +-
 .../viewing-the-email-history-of-an-order.md  |    8 +-
 docs/tracks/en/vtex-modules-i.md              |  355 +++++
 docs/tracks/en/vtex-modules-ii.md             |  299 ++++
 docs/tracks/en/vtex-support.md                |   33 +
 .../what-are-clustered-payment-conditions.md  |    7 +-
 docs/tracks/en/what-is-a-logistics-route.md   |    2 +-
 .../what-is-conversational-commerce-vtex.md   |    6 +-
 docs/tracks/en/what-is-instore.md             |   15 +-
 docs/tracks/en/what-is-lengow.md              |    2 +-
 docs/tracks/en/what-is-the-cms.md             |    2 +-
 docs/tracks/en/what-is-the-master-user.md     |    2 +-
 docs/tracks/en/what-is-vtex-payment.md        |    6 +-
 ...figure-in-wish-prior-to-the-integration.md |    4 +-
 docs/tracks/en/whatsapp-integration.md        |   14 +-
 .../es/access-to-the-customers-last-cart.md   |    2 +-
 docs/tracks/es/accounts-and-architecture.md   |  126 ++
 .../tracks/es/ad-types-classic-and-premium.md |    4 +-
 docs/tracks/es/add-on-products.md             |  136 ++
 docs/tracks/es/add-pickup-points.md           |    2 +-
 docs/tracks/es/add-sku-specifications.md      |    8 +-
 docs/tracks/es/adding-a-fixed-price.md        |    8 +-
 docs/tracks/es/adding-a-loading-dock.md       |    2 +-
 docs/tracks/es/adding-a-price-rule.md         |    6 +-
 .../adding-extra-text-to-the-order-print.md   |    4 +-
 .../tracks/es/adding-new-stores-to-instore.md |   10 +-
 .../es/adding-product-specifications.md       |    8 +-
 docs/tracks/es/adding-products.md             |    2 +-
 docs/tracks/es/adding-skus.md                 |    6 +-
 docs/tracks/es/adding-vendors.md              |    4 +-
 docs/tracks/es/adding-warehouses.md           |    2 +-
 docs/tracks/es/allowing-order-replacement.md  |    8 +-
 docs/tracks/es/amazon-account-settings.md     |    4 +-
 docs/tracks/es/amazon.md                      |    2 +-
 docs/tracks/es/apple-pay.md                   |   53 +
 .../associating-a-template-with-a-layout.md   |    2 +-
 docs/tracks/es/autocomplete-search.md         |    8 +-
 docs/tracks/es/availability.md                |    6 +-
 docs/tracks/es/b2b-form.md                    |    6 +-
 docs/tracks/es/backend-integrations.md        |  406 +++++
 docs/tracks/es/banners-en.md                  |    2 +-
 docs/tracks/es/barcode-reading.md             |    2 +-
 .../es/basic-vtex-io-developer-setup.md       |    6 +-
 .../es/best-practices-for-testing-instore.md  |    2 +-
 docs/tracks/es/billing-support.md             |   53 +
 docs/tracks/es/canceling-an-order.md          |    8 +-
 docs/tracks/es/cart-transfer-and-capture.md   |    6 +-
 docs/tracks/es/cart-transfer.md               |    6 +-
 docs/tracks/es/catalog-architecture.md        |    2 +-
 docs/tracks/es/catalog-concept-definition.md  |    2 +-
 docs/tracks/es/centauro-marketplace.md        |    4 +-
 .../es/changing-the-instore-language.md       |    2 +-
 docs/tracks/es/cms-folder-structure.md        |    2 +-
 docs/tracks/es/cms-vtex-io.md                 |   10 +-
 docs/tracks/es/commercial-support.md          |   35 +
 ...uracao-da-estrutura-para-suporte-humano.md |    6 +-
 .../es/configure-customer-identification.md   |   10 +-
 ...configure-integration-of-pick-up-points.md |   10 +-
 docs/tracks/es/configure-integration.md       |    6 +-
 .../es/configure-warranty-in-via-varejo.md    |    6 +-
 .../es/configuring-a-payment-condition.md     |   45 +-
 docs/tracks/es/configuring-banners.md         |    9 +-
 ...nfiguring-cash-payments-through-instore.md |    2 +-
 .../tracks/es/configuring-dafiti-connector.md |   27 +-
 ...onfiguring-livelo-price-divergence-rule.md |   18 +
 .../es/configuring-login-with-facebook.md     |    2 +-
 .../es/configuring-login-with-google.md       |    2 +-
 .../es/configuring-merchandising-rules.md     |   10 +-
 .../es/configuring-payment-connectors.md      |   41 +-
 ...guring-physical-stores-as-pickup-points.md |    4 +-
 ...onfiguring-price-divergence-rule-dafiti.md |    4 +-
 ...ing-price-divergence-rule-mercado-libre.md |    8 +-
 .../configuring-price-divergence-rule-via.md  |    4 +-
 ...configuring-rappi-price-divergence-rule.md |   18 +
 docs/tracks/es/configuring-redirect.md        |    7 +-
 docs/tracks/es/configuring-ship-from-store.md |    8 +-
 docs/tracks/es/configuring-synonyms.md        |   45 +-
 .../es/configuring-the-amazon-integration.md  |    4 +-
 .../es/configuring-the-connector-b2w.md       |    4 +-
 docs/tracks/es/configuring-the-connector.md   |   14 +-
 .../es/configuring-the-integration-rappi.md   |   18 +
 ...-integration-with-fbe-in-the-vtex-admin.md |    6 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |    2 +-
 docs/tracks/es/configuring-the-integration.md |   18 +
 .../es/configuring-the-relevance-feature.md   |    6 +-
 docs/tracks/es/contract-termination.md        |   22 +
 docs/tracks/es/corporate-digital-account.md   |    6 +-
 docs/tracks/es/create-brands.md               |    2 +-
 docs/tracks/es/creating-accounts.md           |  132 +-
 docs/tracks/es/creating-and-editing-users.md  |    6 +-
 ...ating-merchandising-rules-visual-editor.md |   99 ++
 .../es/creating-or-editing-a-page-template.md |    4 +-
 docs/tracks/es/creating-regular-promotions.md |  220 +--
 docs/tracks/es/credit-card-payment-flow.md    |   10 +-
 docs/tracks/es/customer-identification.md     |    2 +-
 docs/tracks/es/customizing-instore.md         |   14 +-
 docs/tracks/es/customizing-styles.md          |    4 +-
 docs/tracks/es/customizing-templates.md       |    2 +-
 docs/tracks/es/dafiti-marketplace.md          |    4 +-
 docs/tracks/es/dashboard.md                   |    8 +-
 docs/tracks/es/data-protection-roles.md       |   86 ++
 ...ne-payment-methods-displayed-on-instore.md |    6 +-
 .../es/defining-centauro-trade-policy.md      |    4 +-
 .../tracks/es/defining-dafiti-trade-policy.md |    4 +-
 .../es/defining-netshoes-trade-policy.md      |    4 +-
 ...fining-the-google-shopping-trade-policy.md |   36 +-
 .../es/defining-the-shipping-strategy-via.md  |    4 +-
 docs/tracks/es/delivery.md                    |    8 +-
 .../es/detaching-skus-by-specification.md     |    2 +-
 docs/tracks/es/digital-wallet-e-wallet.md     |   23 +
 .../enabling-2-factor-authentication-login.md |   16 +-
 docs/tracks/es/enabling-a-sales-rep-code.md   |    4 +-
 .../enabling-cart-transfer-between-devices.md |    6 +-
 .../es/enabling-product-recommendations.md    |    2 +-
 docs/tracks/es/endless-aisle.md               |    4 +-
 docs/tracks/es/explained-search.md            |    2 +-
 docs/tracks/es/extensions-hub-1.md            |    2 +-
 docs/tracks/es/extensions-hub-app-store.md    |    6 +-
 docs/tracks/es/extensions-hub-partners.md     |   19 +
 docs/tracks/es/filter-orders-by-vendor.md     |    4 +-
 docs/tracks/es/filters.md                     |   16 +-
 docs/tracks/es/frontend-implementation.md     |  320 ++++
 docs/tracks/es/frontend.md                    |    2 +-
 .../es/getting-started-with-logistics.md      |    2 +-
 docs/tracks/es/go-live-process.md             |   10 +-
 docs/tracks/es/google-pay.md                  |  111 ++
 docs/tracks/es/google-shopping-marketplace.md |    6 +-
 ...hide-product-suggestions-recommendation.md |    2 +-
 .../how-a-split-payment-transaction-works.md  |    2 +-
 .../es/how-clustered-conditions-work.md       |    2 +-
 .../how-does-vtex-intelligent-search-work.md  |  148 +-
 docs/tracks/es/how-message-center-works.md    |    6 +-
 .../es/how-the-payments-module-works.md       |   34 +-
 ...change-the-sales-policy-used-by-instore.md |    4 +-
 .../es/how-to-configure-a-custom-payment.md   |    6 +-
 ...nfigure-a-device-for-printout-the-order.md |    8 +-
 ...-and-edit-transactional-email-templates.md |    8 +-
 docs/tracks/es/how-vtex-support-works.md      |   42 +
 ...uding-order-variables-in-email-template.md |    4 +-
 docs/tracks/es/indexing-history.md            |   66 +
 .../es/initializing-your-store-theme.md       |    6 +-
 .../inserting-and-configuring-placeholders.md |    6 +-
 docs/tracks/es/installing-customer-credit.md  |   28 +-
 docs/tracks/es/instore-basic-settings.md      |   10 +-
 docs/tracks/es/instore-customizations.md      |    6 +-
 docs/tracks/es/instore-login.md               |    2 +-
 docs/tracks/es/instore.md                     |   30 +-
 ...ating-instore-to-a-new-payment-acquirer.md |    2 +-
 docs/tracks/es/integration-configurations.md  |    2 +-
 docs/tracks/es/integration-settings.md        |   19 +-
 docs/tracks/es/intelligent-synonyms.md        |   67 +
 docs/tracks/es/intro-to-vtex-io-builders.md   |    2 +-
 docs/tracks/es/introduction-to-vtex-io.md     |    2 +-
 docs/tracks/es/introduction-to-vtex.md        |   45 +
 .../inventory-and-shipping-module-overview.md |    2 +-
 docs/tracks/es/legacy-cms-portal.md           |    6 +-
 docs/tracks/es/live-support.md                |   16 +-
 docs/tracks/es/livelo-integration-overview.md |   18 +
 .../es/livelo-integration-registration.md     |   18 +
 docs/tracks/es/magazine-luiza-marketplace.md  |    4 +-
 docs/tracks/es/managing-accounts.md           |  124 +-
 .../es/managing-customer-credit-invoices.md   |   73 +
 .../managing-sales-associates-in-instore.md   |   58 +-
 docs/tracks/es/managing-shipping-rates.md     |    2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |    2 +-
 docs/tracks/es/mapping-colors-and-sizes.md    |    2 +-
 ...egories-and-attributes-to-mercado-libre.md |  102 +-
 ...pping-product-categories-and-attributes.md |   18 +
 ...rappi-product-categories-and-attributes.md |   18 +
 docs/tracks/es/mercado-libre-marketplace.md   |    8 +-
 docs/tracks/es/merchandising-rules.md         |   43 +-
 docs/tracks/es/next-steps.md                  |   28 +
 docs/tracks/es/opening-tickets.md             |   35 +
 docs/tracks/es/order-delivery.md              |    2 +-
 docs/tracks/es/order-flow.md                  |   14 +-
 docs/tracks/es/other-vtex-module-settings.md  |  106 ++
 docs/tracks/es/overview-intelligent-search.md |   16 +-
 docs/tracks/es/partial-invoices.md            |    7 +-
 docs/tracks/es/payment.md                     |   16 +-
 docs/tracks/es/personal-data.md               |   48 +
 docs/tracks/es/planning-the-go-live.md        |  195 +++
 .../es/preco-base-definicao-de-conceito.md    |    2 +-
 .../es/preco-fixo-definicao-de-conceito.md    |    4 +-
 .../es/prerequisites-for-using-instore.md     |   24 +-
 docs/tracks/es/prices-module-overview.md      |    6 +-
 docs/tracks/es/pricing-system-architecture.md |   18 +-
 docs/tracks/es/printing-an-order-summary.md   |   14 +-
 docs/tracks/es/product-details.md             |    2 +-
 .../product-integration-errors-with-amazon.md |  148 ++
 .../es/promotions-for-specific-scenarios.md   |   24 +-
 docs/tracks/es/rappi-integration-overview.md  |   20 +
 .../es/rappi-integration-registration.md      |   18 +
 docs/tracks/es/receivables-management.md      |    6 +-
 .../es/register-mercado-livre-integration.md  |   15 +-
 .../registering-the-carrefour-integration.md  |    4 +-
 .../registering-the-centauro-integration.md   |    4 +-
 docs/tracks/es/registering-the-integration.md |    6 +-
 .../registering-the-netshoes-integration.md   |    4 +-
 docs/tracks/es/relevance.md                   |  111 +-
 .../es/reports-vtex-intelligent-search.md     |    4 +-
 docs/tracks/es/sale-confirmed.md              |    2 +-
 ...eduled-deliveries-and-delivery-capacity.md |   10 +-
 docs/tracks/es/search-settings.md             |   42 +-
 docs/tracks/es/seeing-order-details.md        |   13 +-
 .../es/sending-product-data-to-dafiti.md      |    8 +-
 docs/tracks/es/sending-products-to-amazon.md  |   96 +-
 .../tracks/es/sending-products-to-facebook.md |   12 +-
 docs/tracks/es/sending-products-to-via.md     |    6 +-
 ...etting-instore-up-in-a-store-easy-setup.md |   12 +-
 ...setting-up-a-marketplace-trade-policy-2.md |    2 +-
 ...p-a-marketplace-trade-policy-skyhub-b2w.md |    4 +-
 ...up-a-marketplace-trade-policy-viavarejo.md |    4 +-
 .../setting-up-a-marketplace-trade-policy.md  |    6 +-
 ...app-linking-for-payments-app-in-instore.md |    2 +-
 .../es/setting-up-credit-direct-sale.md       |    4 +-
 .../setting-up-payment-methods-for-instore.md |    6 +-
 docs/tracks/es/setting-up-the-app.md          |  125 +-
 ...ting-up-the-logistics-for-mercado-livre.md |   35 +-
 .../setting-up-the-order-summary-printing.md  |    8 +-
 docs/tracks/es/settings-on-via-marketplace.md |    6 +-
 ...pping-cart-using-instore-social-selling.md |    8 +-
 docs/tracks/es/shipping-strategies.md         |    2 +-
 docs/tracks/es/size-chart.md                  |    6 +-
 docs/tracks/es/store-development.md           |    2 +-
 docs/tracks/es/subject-rights.md              |   32 +
 .../technical-and-administrative-measures.md  |   56 +
 docs/tracks/es/technical-support.md           |   34 +
 docs/tracks/es/teste-1.md                     |   65 +-
 docs/tracks/es/the-reservation.md             |    2 +-
 docs/tracks/es/unified-commerce-101.md        |   12 +-
 docs/tracks/es/unified-commerce.md            |   57 +
 docs/tracks/es/unified-search.md              |   50 +-
 docs/tracks/es/using-custom-controls.md       |    2 +-
 docs/tracks/es/via-varejo-marketplace.md      |    6 +-
 .../viewing-the-email-history-of-an-order.md  |    7 +-
 docs/tracks/es/vtex-modules-i.md              |  355 +++++
 docs/tracks/es/vtex-modules-ii.md             |  300 ++++
 docs/tracks/es/vtex-support.md                |   33 +
 .../what-are-clustered-payment-conditions.md  |    6 +-
 docs/tracks/es/what-is-a-logistics-route.md   |    2 +-
 .../what-is-conversational-commerce-vtex.md   |    6 +-
 docs/tracks/es/what-is-instore.md             |   15 +-
 docs/tracks/es/what-is-the-master-user.md     |    2 +-
 docs/tracks/es/what-is-vtex-payment.md        |    6 +-
 ...figure-in-wish-prior-to-the-integration.md |    4 +-
 docs/tracks/es/whatsapp-integration.md        |   14 +-
 .../pt/access-to-the-customers-last-cart.md   |    2 +-
 docs/tracks/pt/accounts-and-architecture.md   |  122 ++
 .../tracks/pt/ad-types-classic-and-premium.md |    4 +-
 docs/tracks/pt/add-on-products.md             |  128 ++
 docs/tracks/pt/add-pickup-points.md           |    2 +-
 docs/tracks/pt/add-sku-specifications.md      |    8 +-
 docs/tracks/pt/adding-a-fixed-price.md        |    8 +-
 docs/tracks/pt/adding-a-loading-dock.md       |    2 +-
 docs/tracks/pt/adding-a-price-rule.md         |    6 +-
 .../adding-extra-text-to-the-order-print.md   |    4 +-
 .../tracks/pt/adding-new-stores-to-instore.md |    8 +-
 .../pt/adding-product-specifications.md       |    8 +-
 docs/tracks/pt/adding-products.md             |    2 +-
 docs/tracks/pt/adding-skus.md                 |    6 +-
 docs/tracks/pt/adding-vendors.md              |    4 +-
 docs/tracks/pt/adding-warehouses.md           |    2 +-
 docs/tracks/pt/allowing-order-replacement.md  |    8 +-
 docs/tracks/pt/amazon-account-settings.md     |    4 +-
 docs/tracks/pt/apple-pay.md                   |   53 +
 .../associating-a-template-with-a-layout.md   |    2 +-
 docs/tracks/pt/autocomplete-search.md         |    8 +-
 docs/tracks/pt/availability.md                |    7 +-
 docs/tracks/pt/b2b-form.md                    |    6 +-
 docs/tracks/pt/backend-integrations.md        |  406 +++++
 docs/tracks/pt/banners-en.md                  |    2 +-
 docs/tracks/pt/barcode-reading.md             |    2 +-
 .../pt/basic-vtex-io-developer-setup.md       |    6 +-
 .../pt/best-practices-for-testing-instore.md  |    2 +-
 docs/tracks/pt/billing-support.md             |   52 +
 docs/tracks/pt/canceling-an-order.md          |    8 +-
 ...tes-de-iniciar-uma-conversa-no-whatsapp.md |   10 +-
 docs/tracks/pt/carrefour-marketplace.md       |    2 +-
 docs/tracks/pt/cart-transfer-and-capture.md   |    6 +-
 docs/tracks/pt/cart-transfer.md               |    6 +-
 docs/tracks/pt/catalog-architecture.md        |    2 +-
 docs/tracks/pt/centauro-marketplace.md        |    8 +-
 .../pt/changing-the-instore-language.md       |    2 +-
 docs/tracks/pt/cms-folder-structure.md        |    2 +-
 docs/tracks/pt/cms-vtex-io.md                 |   10 +-
 docs/tracks/pt/commercial-support.md          |   34 +
 ...ento-no-whatsapp-para-mais-de-um-numero.md |    4 +-
 .../pt/como-funciona-o-adaptador-vtex.md      |    2 +-
 ...uracao-da-estrutura-para-suporte-humano.md |    6 +-
 docs/tracks/pt/configurar-erps.md             |    2 +-
 .../pt/configure-customer-identification.md   |   10 +-
 ...configure-integration-of-pick-up-points.md |   10 +-
 docs/tracks/pt/configure-integration.md       |  104 +-
 .../pt/configure-warranty-in-via-varejo.md    |   14 +-
 .../pt/configuring-a-payment-condition.md     |   43 +-
 docs/tracks/pt/configuring-banners.md         |    9 +-
 .../tracks/pt/configuring-dafiti-connector.md |   44 +-
 ...onfiguring-livelo-price-divergence-rule.md |   33 +
 .../pt/configuring-login-with-facebook.md     |    2 +-
 .../pt/configuring-login-with-google.md       |    2 +-
 .../pt/configuring-merchandising-rules.md     |    8 +-
 .../pt/configuring-payment-connectors.md      |   41 +-
 ...guring-physical-stores-as-pickup-points.md |    8 +-
 ...onfiguring-price-divergence-rule-dafiti.md |   13 +-
 ...ing-price-divergence-rule-mercado-libre.md |    8 +-
 .../configuring-price-divergence-rule-via.md  |   10 +-
 ...configuring-rappi-price-divergence-rule.md |   29 +
 docs/tracks/pt/configuring-redirect.md        |    7 +-
 docs/tracks/pt/configuring-ship-from-store.md |    6 +-
 docs/tracks/pt/configuring-synonyms.md        |   48 +-
 .../pt/configuring-the-amazon-integration.md  |    9 +-
 .../pt/configuring-the-connector-b2w.md       |   31 +-
 docs/tracks/pt/configuring-the-connector.md   |   18 +-
 .../pt/configuring-the-integration-rappi.md   |   41 +
 ...-integration-with-fbe-in-the-vtex-admin.md |    6 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |    2 +-
 docs/tracks/pt/configuring-the-integration.md |   47 +
 .../pt/configuring-the-relevance-feature.md   |    6 +-
 docs/tracks/pt/contract-termination.md        |   22 +
 docs/tracks/pt/corporate-digital-account.md   |    6 +-
 docs/tracks/pt/create-brands.md               |    2 +-
 docs/tracks/pt/creating-accounts.md           |  127 +-
 docs/tracks/pt/creating-and-editing-users.md  |    6 +-
 ...ating-merchandising-rules-visual-editor.md |   98 ++
 .../pt/creating-or-editing-a-page-template.md |    4 +-
 docs/tracks/pt/creating-regular-promotions.md |  193 ++-
 docs/tracks/pt/credit-card-payment-flow.md    |   10 +-
 docs/tracks/pt/customer-identification.md     |    2 +-
 docs/tracks/pt/customizing-instore.md         |   14 +-
 docs/tracks/pt/customizing-styles.md          |    4 +-
 docs/tracks/pt/customizing-templates.md       |    2 +-
 docs/tracks/pt/dafiti-marketplace.md          |    8 +-
 docs/tracks/pt/dashboard.md                   |    8 +-
 docs/tracks/pt/data-protection-roles.md       |   85 ++
 ...ne-payment-methods-displayed-on-instore.md |    6 +-
 .../pt/defining-centauro-trade-policy.md      |    4 +-
 .../tracks/pt/defining-dafiti-trade-policy.md |    6 +-
 .../pt/defining-netshoes-trade-policy.md      |    4 +-
 ...fining-the-google-shopping-trade-policy.md |   42 +-
 .../pt/defining-the-shipping-strategy-via.md  |   10 +-
 docs/tracks/pt/delivery.md                    |   10 +-
 .../pt/detaching-skus-by-specification.md     |    2 +-
 docs/tracks/pt/digital-wallet-e-wallet.md     |   24 +
 .../enabling-2-factor-authentication-login.md |   16 +-
 docs/tracks/pt/enabling-a-sales-rep-code.md   |    4 +-
 .../enabling-cart-transfer-between-devices.md |    6 +-
 .../enabling-order-filter-by-salesperson.md   |    4 +-
 .../pt/enabling-product-recommendations.md    |    4 +-
 docs/tracks/pt/endless-aisle.md               |    4 +-
 ...o-os-clientes-chegam-ate-o-seu-whatsapp.md |   16 +-
 docs/tracks/pt/explained-search.md            |    2 +-
 docs/tracks/pt/extensions-hub-1.md            |    2 +-
 docs/tracks/pt/extensions-hub-app-store.md    |    6 +-
 docs/tracks/pt/extensions-hub-partners.md     |   19 +
 docs/tracks/pt/filter-orders-by-vendor.md     |    4 +-
 docs/tracks/pt/filters.md                     |   16 +-
 docs/tracks/pt/frontend-implementation.md     |  321 ++++
 docs/tracks/pt/frontend.md                    |    2 +-
 ...website-and-social-networks-to-whatsapp.md |    2 +-
 .../pt/getting-started-with-logistics.md      |    2 +-
 docs/tracks/pt/go-live-process.md             |   12 +-
 docs/tracks/pt/google-pay.md                  |  111 ++
 docs/tracks/pt/google-shopping-marketplace.md |    6 +-
 ...hide-product-suggestions-recommendation.md |    2 +-
 .../how-a-split-payment-transaction-works.md  |    2 +-
 .../pt/how-clustered-conditions-work.md       |    8 +-
 .../how-does-vtex-intelligent-search-work.md  |  129 +-
 docs/tracks/pt/how-message-center-works.md    |    6 +-
 .../pt/how-the-payments-module-works.md       |   29 +-
 ...ustom-text-in-the-printout-of-the-order.md |    4 +-
 ...change-the-sales-policy-used-by-instore.md |    4 +-
 .../pt/how-to-configure-a-custom-payment.md   |    6 +-
 ...nfigure-a-device-for-printout-the-order.md |    8 +-
 ...-and-edit-transactional-email-templates.md |    8 +-
 docs/tracks/pt/how-to-get-started.md          |    6 +-
 docs/tracks/pt/how-vtex-support-works.md      |   43 +
 docs/tracks/pt/indexing-history.md            |   67 +
 .../pt/initializing-your-store-theme.md       |    6 +-
 .../inserting-and-configuring-placeholders.md |    6 +-
 docs/tracks/pt/installing-customer-credit.md  |   28 +-
 docs/tracks/pt/instore-basic-settings.md      |    6 +-
 docs/tracks/pt/instore-customizations.md      |    6 +-
 docs/tracks/pt/instore-login.md               |    2 +-
 docs/tracks/pt/instore.md                     |   32 +-
 ...ating-instore-to-a-new-payment-acquirer.md |    2 +-
 docs/tracks/pt/integration-configurations.md  |    2 +-
 docs/tracks/pt/integration-settings.md        |   19 +-
 docs/tracks/pt/intelligent-synonyms.md        |   68 +
 docs/tracks/pt/intro-to-vtex-io-builders.md   |    2 +-
 docs/tracks/pt/introduction-to-vtex-io.md     |    2 +-
 docs/tracks/pt/introduction-to-vtex.md        |   45 +
 .../inventory-and-shipping-module-overview.md |    2 +-
 docs/tracks/pt/legacy-cms-portal.md           |    6 +-
 ...var-os-contatos-do-whatsapp-para-um-crm.md |   10 +-
 docs/tracks/pt/live-support.md                |   18 +-
 docs/tracks/pt/livelo-integration-overview.md |   32 +
 .../pt/livelo-integration-registration.md     |   37 +
 docs/tracks/pt/login-e-senha.md               |    2 +-
 docs/tracks/pt/magazine-luiza-marketplace.md  |    6 +-
 docs/tracks/pt/managing-accounts.md           |  122 +-
 .../pt/managing-customer-credit-invoices.md   |   73 +
 .../managing-sales-associates-in-instore.md   |   40 +-
 docs/tracks/pt/managing-shipping-rates.md     |    2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |    2 +-
 docs/tracks/pt/mapping-colors-and-sizes.md    |    2 +-
 ...egories-and-attributes-to-mercado-libre.md |  104 +-
 ...pping-product-categories-and-attributes.md |   32 +
 ...rappi-product-categories-and-attributes.md |   32 +
 docs/tracks/pt/mercado-libre-marketplace.md   |    8 +-
 docs/tracks/pt/merchandising-rules.md         |   39 +-
 docs/tracks/pt/netshoes-marketplace.md        |    4 +-
 docs/tracks/pt/next-steps.md                  |   28 +
 docs/tracks/pt/opening-tickets.md             |   35 +
 docs/tracks/pt/order-delivery.md              |    2 +-
 docs/tracks/pt/order-flow.md                  |   14 +-
 docs/tracks/pt/other-vtex-module-settings.md  |  102 ++
 docs/tracks/pt/overview-intelligent-search.md |   16 +-
 docs/tracks/pt/partial-invoices.md            |    9 +-
 docs/tracks/pt/payment.md                     |   16 +-
 docs/tracks/pt/personal-data.md               |   47 +
 docs/tracks/pt/planning-the-go-live.md        |  195 +++
 .../pt/preco-base-definicao-de-conceito.md    |    2 +-
 .../pt/preco-fixo-definicao-de-conceito.md    |    4 +-
 .../pt/prerequisites-for-using-instore.md     |   25 +-
 docs/tracks/pt/prices-module-overview.md      |    6 +-
 docs/tracks/pt/pricing-system-architecture.md |   18 +-
 docs/tracks/pt/printing-an-order-summary.md   |   10 +-
 docs/tracks/pt/product-details.md             |    2 +-
 .../product-group-registration-in-netshoes.md |   18 +-
 .../product-integration-errors-with-amazon.md |  155 ++
 .../pt/promotions-for-specific-scenarios.md   |   25 +-
 docs/tracks/pt/rappi-integration-overview.md  |   35 +
 .../pt/rappi-integration-registration.md      |   35 +
 docs/tracks/pt/receivables-management.md      |    6 +-
 .../pt/register-mercado-livre-integration.md  |   17 +-
 .../registering-the-carrefour-integration.md  |   29 +-
 .../registering-the-centauro-integration.md   |   31 +-
 docs/tracks/pt/registering-the-integration.md |   57 +-
 .../registering-the-netshoes-integration.md   |   30 +-
 docs/tracks/pt/relevance.md                   |  142 +-
 .../pt/reports-vtex-intelligent-search.md     |    4 +-
 docs/tracks/pt/sale-confirmed.md              |    2 +-
 ...eduled-deliveries-and-delivery-capacity.md |   10 +-
 docs/tracks/pt/search-settings.md             |   41 +-
 docs/tracks/pt/seeing-order-details.md        |   13 +-
 .../pt/sending-product-data-to-dafiti.md      |   12 +-
 docs/tracks/pt/sending-products-to-amazon.md  |   95 +-
 .../tracks/pt/sending-products-to-facebook.md |   18 +-
 docs/tracks/pt/sending-products-to-via.md     |   62 +-
 ...etting-instore-up-in-a-store-easy-setup.md |   12 +-
 ...setting-up-a-marketplace-trade-policy-2.md |    4 +-
 ...p-a-marketplace-trade-policy-skyhub-b2w.md |    4 +-
 ...up-a-marketplace-trade-policy-viavarejo.md |   14 +-
 ...app-linking-for-payments-app-in-instore.md |    2 +-
 .../pt/setting-up-credit-direct-sale.md       |    4 +-
 .../setting-up-payment-methods-for-instore.md |    6 +-
 docs/tracks/pt/setting-up-the-app.md          |  119 +-
 ...ting-up-the-logistics-for-mercado-livre.md |   34 +-
 .../setting-up-the-order-summary-printing.md  |    8 +-
 docs/tracks/pt/settings-on-via-marketplace.md |   38 +-
 ...pping-cart-using-instore-social-selling.md |   13 +-
 docs/tracks/pt/shipping-strategies.md         |    2 +-
 docs/tracks/pt/size-chart.md                  |   14 +-
 docs/tracks/pt/store-development.md           |    2 +-
 docs/tracks/pt/subject-rights.md              |   31 +
 .../technical-and-administrative-measures.md  |   56 +
 docs/tracks/pt/technical-support.md           |   33 +
 docs/tracks/pt/teste-1.md                     |  102 +-
 docs/tracks/pt/the-reservation.md             |    2 +-
 docs/tracks/pt/unified-commerce-101.md        |   14 +-
 docs/tracks/pt/unified-commerce.md            |   51 +
 docs/tracks/pt/unified-search.md              |   47 +-
 docs/tracks/pt/using-custom-controls.md       |    2 +-
 docs/tracks/pt/via-varejo-marketplace.md      |   14 +-
 .../viewing-the-email-history-of-an-order.md  |    8 +-
 docs/tracks/pt/vtex-modules-i.md              |  354 +++++
 docs/tracks/pt/vtex-modules-ii.md             |  299 ++++
 docs/tracks/pt/vtex-support.md                |   33 +
 .../what-are-clustered-payment-conditions.md  |    6 +-
 docs/tracks/pt/what-is-a-logistics-route.md   |    2 +-
 .../what-is-conversational-commerce-vtex.md   |    8 +-
 docs/tracks/pt/what-is-instore.md             |   15 +-
 docs/tracks/pt/what-is-the-cms.md             |    2 +-
 docs/tracks/pt/what-is-the-master-user.md     |    2 +-
 docs/tracks/pt/what-is-vtex-payment.md        |    6 +-
 ...figure-in-wish-prior-to-the-integration.md |   10 +-
 docs/tracks/pt/whatsapp-integration.md        |   14 +-
 .../en/ab-testing-how-where-when-and-why.md   |   73 +-
 docs/tutorials/en/access-control.md           |   61 +
 .../en/accessing-a-client-abandoned-cart.md   |   12 +-
 .../en/accessing-the-beta-environment.md      |   52 +-
 docs/tutorials/en/account-management.md       |   78 +-
 .../tutorials/en/account-settings-overview.md |    2 +-
 docs/tutorials/en/accounts-payable-brazil.md  |    6 +-
 docs/tutorials/en/activating-new-vtex-cdn.md  |    6 +-
 ...complete-list-link-on-the-category-menu.md |    4 +-
 ...-your-integration-for-change-order-beta.md |  305 ++++
 ...s-support-to-the-integration-with-adyen.md |    8 +-
 ...-a-url-mapping-through-worksheet-import.md |    2 +-
 ...a-client-secret-to-log-in-with-facebook.md |  126 +-
 ...d-a-client-secret-to-log-in-with-google.md |   24 +-
 .../adding-a-record-on-a-master-data-form.md  |   56 +
 docs/tutorials/en/adding-an-attachment.md     |    8 +-
 docs/tutorials/en/adding-bin-information.md   |   42 +
 docs/tutorials/en/adding-collections-cms.md   |   20 +-
 .../en/adding-sku-specifications-or-fields.md |   18 +-
 ...adding-specifications-or-product-fields.md |   10 +-
 .../tutorials/en/additional-shipping-costs.md |    8 +-
 ...dmin-redirect-search-returns-no-results.md |  111 ++
 docs/tutorials/en/admin-v4-getting-started.md |   10 +-
 docs/tutorials/en/ads-from-vtex-sales-app.md  |  134 +-
 .../advertising-with-vtex-ad-network-beta.md  |  163 ++
 docs/tutorials/en/affiliates-program-app.md   |   10 +-
 docs/tutorials/en/all-orders.md               |   19 +-
 docs/tutorials/en/amaro-integration.md        |   19 +
 docs/tutorials/en/amazon-offer-matching.md    |   32 +-
 docs/tutorials/en/analytics.md                |   87 ++
 docs/tutorials/en/antifraud-provider.md       |   14 +-
 docs/tutorials/en/application-keys.md         |  181 ++-
 ...roving-payment-of-the-bank-payment-slip.md |    8 +-
 docs/tutorials/en/apps-overview.md            |    2 +-
 docs/tutorials/en/assembly-options-app.md     |    2 +-
 .../en/assembly-options-in-vtex-sales-app.md  |   60 +
 docs/tutorials/en/assembly-options.md         |    8 +-
 .../en/associate-a-sku-to-a-trade-policy.md   |   10 +-
 .../associating-a-template-with-a-layout.md   |    2 +-
 docs/tutorials/en/audit.md                    |  136 ++
 docs/tutorials/en/authentication.md           |   86 ++
 docs/tutorials/en/autocomplete.md             |   77 +
 docs/tutorials/en/availability.md             |   32 +
 docs/tutorials/en/b2b-checkout-settings.md    |   71 +
 .../en/b2b-cost-center-management.md          |  101 ++
 .../en/b2b-organization-general-settings.md   |   34 +
 docs/tutorials/en/b2b-overview.md             |    6 +-
 docs/tutorials/en/b2b-store-settings.md       |   42 +
 docs/tutorials/en/b2b-suite-overview.md       |   93 ++
 .../en/b2b-trade-policies-overview.md         |   32 +
 docs/tutorials/en/bank-reconciliations.md     |    6 +-
 docs/tutorials/en/banners.md                  |   69 +
 .../best-practices-against-virtual-attacks.md |   34 +-
 .../en/best-practices-application-keys.md     |    5 +-
 ...ces-for-accessing-the-store-without-www.md |   74 +
 ...ices-for-the-success-of-your-vtex-store.md |  171 +++
 ...actices-for-using-images-in-the-catalog.md |    4 +-
 docs/tutorials/en/best-practices-on-spf.md    |   12 +-
 ...ces-to-avoid-scams-using-the-vtex-brand.md |   53 +
 docs/tutorials/en/beta-price-configuration.md |    6 +-
 docs/tutorials/en/billing-module-overview.md  |    2 +-
 docs/tutorials/en/brands.md                   |    2 +-
 ...inging-app-content-into-the-admin-panel.md |    8 +-
 docs/tutorials/en/buy-one-get-one.md          |  133 +-
 ...e-articulos-del-mismo-sku-en-el-carrito.md |    2 +-
 docs/tutorials/en/campaign-audiences-list.md  |    4 +-
 docs/tutorials/en/campaign-audiences.md       |    2 +-
 docs/tutorials/en/campaign-promotion.md       |    4 +-
 docs/tutorials/en/canceling-orders.md         |   27 +-
 .../carrefour-inventory-integration-errors.md |    4 +-
 docs/tutorials/en/carrier-working-hours.md    |   41 +-
 ...rking-hours-and-scheduled-delivery-beta.md |    6 +-
 docs/tutorials/en/carries-on-vtex.md          |    4 +-
 docs/tutorials/en/catalog-overview-2.md       |    8 +-
 docs/tutorials/en/catalog-overview.md         |   39 +-
 docs/tutorials/en/categories.md               |    4 +-
 .../en/category-registration-fields.md        |   12 +-
 .../en/change-a-placeholder-title.md          |    4 +-
 docs/tutorials/en/change-seller.md            |    4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |    2 +-
 ...ult-system-texts-displayed-in-the-store.md |    4 +-
 .../changing-items-from-a-complete-order.md   |    7 +-
 .../changing-the-total-cost-of-the-order.md   |    4 +-
 docs/tutorials/en/changing-tracking-data.md   |    2 +-
 .../en/check-order-delivery-details.md        |    2 +-
 ...-order-delivery-deadline-was-calculated.md |   12 +-
 docs/tutorials/en/checkout-vtex-overview.md   |    2 +-
 ...chitecture-or-an-additional-environment.md |   38 +-
 ...ount-franchise-account-or-seller-portal.md |    8 +-
 docs/tutorials/en/cms-overview.md             |    8 +-
 docs/tutorials/en/cms-store-overview.md       |    2 +-
 .../en/collection-highlight-control.md        |    6 +-
 .../en/conditions-builder-usage-examples.md   |    6 +-
 docs/tutorials/en/conecta-la-integration.md   |    6 +-
 docs/tutorials/en/configure-cartman.md        |   37 +-
 ...e-direct-consumer-credit-cdc-by-losango.md |    4 +-
 ...yee-benefits-using-master-data-clusters.md |    4 +-
 .../configure-payment-with-pix-at-nubank.md   |    4 +-
 .../en/configure-payment-with-shopfacil.md    |   18 +
 .../en/configure-seller-regionalization.md    |    6 +-
 ...figure-template-in-smartcheckout-update.md |   30 +-
 ...configure-template-in-the-smartcheckout.md |   24 +-
 ...g-a-discount-for-orders-prepaid-in-full.md |    2 +-
 .../configuring-a-marketplace-trade-policy.md |   28 +-
 ...uring-a-pricing-rule-for-a-sales-policy.md |    6 +-
 .../en/configuring-a-registered-boleto.md     |   23 +-
 ...nfiguring-a-santander-registered-boleto.md |    6 +-
 docs/tutorials/en/configuring-affiliates.md   |    8 +-
 docs/tutorials/en/configuring-banners.md      |   70 +
 ...port-for-organizations-and-cost-centers.md |   67 +
 .../en/configuring-cargo-splitting.md         |   13 +-
 .../en/configuring-cielo-acquirer.md          |    6 +-
 ...ng-clearsale-global-anti-fraud-solution.md |    2 +-
 .../en/configuring-clearsale-v3-antifraud.md  |   47 +-
 ...ders-prepaid-in-full-on-google-shopping.md |   11 +-
 ...nctions-in-the-message-center-templates.md |    2 +-
 .../en/configuring-kushki-gateway.md          |   28 +-
 ...figuring-login-with-facebook-and-google.md |   46 +-
 ...automatic-payment-settlement-time-frame.md |    2 +-
 ...guring-mercado-pagos-device-fingerprint.md |    4 +-
 ...ring-my-account-conversational-commerce.md |    8 +-
 .../en/configuring-openpay-payment-gateway.md |   33 +-
 .../configuring-payment-conditions-for-b2b.md |   43 +
 ...-payment-with-adyenv3-in-vtex-sales-app.md |   51 +-
 .../en/configuring-payment-with-adyenv3.md    |   68 +-
 .../en/configuring-price-divergence-rule.md   |   25 +-
 .../en/configuring-product-visited.md         |   10 +-
 ...configuring-promotions-for-marketplaces.md |   55 +-
 ...iguring-promotions-with-a-highlightflag.md |   10 +-
 ...uring-pwa-in-your-store-framework-store.md |   73 +
 docs/tutorials/en/configuring-redirects.md    |   81 +
 ...iguring-samsung-pay-as-a-payment-method.md |   36 +-
 ...guring-seller-allocation-for-buying-xky.md |   51 +
 .../en/configuring-seo-in-your-store.md       |   63 +
 .../en/configuring-shipping-promotions.md     |   14 +-
 .../configuring-sign-in-with-apple-id-beta.md |   88 ++
 .../configuring-stripe-gateway-affiliation.md |   87 +-
 .../en/configuring-the-scheduled-delivery.md  |    4 +-
 .../en/configuring-the-store-domain.md        |  104 ++
 .../configuring-tuna-gateway-affiliation.md   |   12 +-
 .../en/configuring-vtex-marketplace.md        |    8 +-
 ...g-a-layout-from-one-web-site-to-another.md |    2 +-
 docs/tutorials/en/coupons-list-beta.md        |   12 +-
 .../en/creating-a-campaign-audience.md        |    9 +-
 ...o-guarantee-it-as-an-option-at-checkout.md |   26 +-
 docs/tutorials/en/creating-a-coupon-beta.md   |    8 +-
 .../en/creating-a-more-for-less-promotion.md  |  104 +-
 .../en/creating-a-product-collection.md       |   16 +-
 .../en/creating-a-shipping-policy.md          |   73 +
 .../en/creating-a-subscription-plan.md        |    2 +-
 .../en/creating-a-subscription-promotion.md   |    2 +-
 docs/tutorials/en/creating-a-trade-policy.md  |   41 +-
 docs/tutorials/en/creating-a-type-of-list.md  |    4 +-
 .../creating-an-application-in-master-data.md |   49 +-
 .../en/creating-an-oauth2-authentication.md   |    2 +-
 ...h-promotional-price-using-a-price-table.md |    4 +-
 .../tutorials/en/creating-collections-beta.md |   26 +-
 ...eating-custom-queries-in-master-data-v1.md |   60 +
 ...ustomer-and-address-forms-in-new-stores.md |   19 +-
 .../en/creating-form-in-master-data.md        |   58 +-
 .../en/creating-landing-pages-per-binding.md  |    2 +-
 docs/tutorials/en/creating-landing-pages.md   |   11 +-
 ...ating-merchandising-rules-manual-editor.md |   92 ++
 ...-merchandising-rules-visual-editor-beta.md |  101 +-
 ...ating-merchandising-rules-visual-editor.md |   99 ++
 docs/tutorials/en/creating-price-tables.md    |   18 +-
 ...eating-promotion-for-a-customer-cluster.md |    8 +-
 docs/tutorials/en/creating-promotions.md      |    2 +-
 ...etween-master-data-entities-using-admin.md |   44 +-
 docs/tutorials/en/creating-roles.md           |   95 ++
 .../en/creating-service-for-a-sku.md          |   15 +-
 ...ing-subaccount-multi-store-multi-domain.md |   65 +
 docs/tutorials/en/creating-surchargestaxes.md |   37 +-
 docs/tutorials/en/creating-synonyms.md        |   96 ++
 .../en/creating-trigger-in-master-data.md     |  195 +--
 .../en/credit-card-basic-payment-flow.md      |    2 +-
 docs/tutorials/en/criar-um-produto-beta.md    |  194 +++
 ...stom-fields-when-adding-an-organization.md |   46 +
 ...ustom-payment-information-for-argentina.md |    6 +-
 docs/tutorials/en/custom-product-fields.md    |   20 +
 docs/tutorials/en/customer-approval.md        |   24 +-
 docs/tutorials/en/customer-credit-overview.md |   97 +-
 .../en/customizing-your-stores-typography.md  |    4 +-
 docs/tutorials/en/dashboards-overview.md      |    5 +-
 ...data-dictionary-vtex-data-pipeline-beta.md |   54 +
 docs/tutorials/en/data-entity.md              |  109 ++
 docs/tutorials/en/data-subject-rights.md      |   10 +-
 .../en/database-maintenance-full-cleanup.md   |    8 +-
 .../en/declining-order-cancelation.md         |   89 ++
 ...andatory-fields-in-master-data-v1-forms.md |   30 +
 docs/tutorials/en/defining-window-displays.md |   12 +-
 docs/tutorials/en/deleting-a-category.md      |    2 +-
 ...liveries-progress-vtex-shipping-network.md |    4 +-
 .../en/detaching-skus-by-specification.md     |   34 +
 ...e-the-minimum-number-of-items-in-a-cart.md |   21 +-
 .../en/direct-migration-magazine-luiza.md     |   20 +
 docs/tutorials/en/disable-cloudflare-proxy.md |    2 +-
 ...isplaying-the-store-in-another-language.md |    2 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |   85 ++
 ...ty-in-the-online-tokenized-payment-flow.md |   41 +
 ...ic-relevance-in-intelligent-search-beta.md |   76 +
 ...-field-on-profile-system-of-master-data.md |   25 +-
 docs/tutorials/en/enable-checkout-v6.md       |    4 +-
 .../enabling-2-factor-authentication-login.md |   23 +-
 ...enabling-3ds2-for-redsys-v2-integration.md |   10 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |    6 +-
 ...ng-pwa-push-notifications-in-your-store.md |    2 +-
 .../en/entering-tax-receipts-in-the-order.md  |    2 +-
 docs/tutorials/en/erasing-customer-data.md    |   65 +
 ...-skus-via-spreadsheet-in-the-vtex-admin.md |   44 +
 .../tutorials/en/events-available-in-audit.md |  841 +++--------
 docs/tutorials/en/explained-search.md         |   31 +
 ...mporting-product-and-sku-specifications.md |   18 +-
 docs/tutorials/en/exporting-data.md           |   26 +-
 docs/tutorials/en/facebook-faq.md             |    6 +-
 .../en/facilitating-b2b-store-operation.md    |    8 +-
 docs/tutorials/en/faq-security-2.md           |    2 +-
 .../en/faq-security-restricted-content.md     |  187 +++
 ...-import-spreadsheets-fixed-price-fields.md |    2 +-
 docs/tutorials/en/filtering-all-orders.md     |   25 +-
 .../en/filtering-data-on-master-data.md       |   76 +-
 .../filtering-transactions-on-pci-gateway.md  |    6 +-
 docs/tutorials/en/filters.md                  |   50 +
 ...tplaces-and-sellers-in-the-vtex-network.md |   10 +-
 docs/tutorials/en/find-sellers.md             |   57 +
 ...d-questions-new-orders-module-interface.md |   12 +-
 .../en/fulfillment-logistics-vtex.md          |    2 +-
 docs/tutorials/en/fulfillment-magalu.md       |   18 +
 .../en/general-configurations-on-the-oms.md   |    8 +-
 docs/tutorials/en/geolocation-at-checkout.md  |    4 +-
 docs/tutorials/en/gift-card.md                |   20 +-
 docs/tutorials/en/google-analytics-faq.md     |   36 +-
 .../en/google-integration-warnings.md         |   20 +
 docs/tutorials/en/google-pay-beta.md          |    8 +-
 .../google-search-console-tracking-sitemap.md |    4 +-
 docs/tutorials/en/headless-cms-overview.md    |   54 +
 .../how-and-when-do-i-receive-my-invoice.md   |   15 +-
 ...how-can-i-change-the-domain-of-my-store.md |    2 +-
 ...how-can-i-create-a-field-in-master-data.md |    4 +-
 .../en/how-can-i-create-callcenter-user.md    |    2 +-
 .../how-can-i-create-cluster-of-customers.md  |    8 +-
 ...-can-i-direct-a-financial-doubt-to-vtex.md |    6 +-
 ...e-newsletter-database-using-master-data.md |   17 +-
 .../how-can-my-customer-login-to-my-store.md  |   18 +-
 .../en/how-change-order-works-beta.md         |   77 +
 .../en/how-dns-configuration-works-on-vtex.md |   36 +
 ...ow-do-i-terminate-my-contract-with-vtex.md |   10 +-
 ...e-the-https-protocol-on-my-stores-pages.md |    8 +-
 ...reversals-work-when-an-item-is-returned.md |    6 +-
 .../en/how-does-promotion-proration-work.md   |    2 +-
 .../tutorials/en/how-does-reservation-work.md |    6 +-
 ...th-multiple-items-work-in-mercado-livre.md |    2 +-
 .../en/how-does-the-delivery-flow-work.md     |    2 +-
 .../en/how-does-the-score-field-work.md       |   46 +-
 .../en/how-does-the-type-of-delivery-work.md  |    6 +-
 .../tutorials/en/how-does-vtex-search-work.md |    2 +-
 .../en/how-is-pro-rata-calculated-in-vtex.md  |    2 +-
 ...-the-order-delivery-deadline-calculated.md |   33 +-
 ...-the-platforms-operation-sla-determined.md |   32 +-
 ...o-cancel-an-order-with-an-unpaid-boleto.md |    4 +-
 docs/tutorials/en/how-my-account-works.md     |   33 +-
 .../en/how-order-authorization-works.md       |    6 +-
 .../en/how-order-authorization-workss.md      |    2 +-
 .../en/how-promotion-competition-works.md     |  215 +++
 .../en/how-recursive-marketplace-works.md     |    2 +-
 .../en/how-shipping-calculation-works.md      |    5 +-
 ...hen-delivery-is-done-by-the-marketplace.md |   15 +-
 docs/tutorials/en/how-subscriptions-work.md   |   24 +-
 .../en/how-the-carrefour-integration-works.md |    4 +-
 .../en/how-the-order-replacement-works.md     |    2 +-
 .../en/how-the-seller-portal-catalog-works.md |    2 +-
 .../how-to-activate-the-shareable-cart-app.md |    4 +-
 docs/tutorials/en/how-to-alter-a-banner.md    |    6 +-
 .../tutorials/en/how-to-archive-ratestaxes.md |    2 +-
 .../en/how-to-capture-the-ip-of-an-order.md   |    4 +-
 .../tutorials/en/how-to-change-orders-beta.md |  217 +++
 ...he-order-of-payment-methods-at-checkout.md |    4 +-
 .../tutorials/en/how-to-check-your-balance.md |    2 +-
 .../en/how-to-configure-a-bank-slip.md        |   53 +-
 .../en/how-to-configure-a-custom-payment.md   |   14 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |    4 +-
 .../en/how-to-configure-payment-conditions.md |   12 +-
 ...to-configure-rating-and-review-controls.md |    4 +-
 .../en/how-to-configure-subscriptions.md      |   16 +-
 .../en/how-to-configure-the-anti-fraud.md     |   34 +-
 ...uro-without-redirect-option-transparent.md |   33 +-
 ...pment-environment-with-a-mobile-version.md |    2 +-
 ...ow-to-create-a-financial-access-profile.md |    6 +-
 .../en/how-to-create-a-page-template.md       |    8 +-
 docs/tutorials/en/how-to-create-a-product.md  |    6 +-
 ...eate-a-promotion-with-limitation-of-use.md |    2 +-
 .../en/how-to-create-a-store-name.md          |    2 +-
 ...how-to-create-a-subscription-attachment.md |    4 +-
 .../en/how-to-create-conditional-prices.md    |    2 +-
 ...ize-the-checkout-ui-custom-in-the-admin.md |   86 ++
 ...ow-to-define-the-url-for-a-product-page.md |    2 +-
 ...w-to-deprecate-and-undeprecate-your-app.md |    2 +-
 .../how-to-disable-a-transactional-email.md   |    2 +-
 .../en/how-to-download-the-vtex-invoices.md   |    6 +-
 .../en/how-to-identify-a-page-template.md     |    6 +-
 ...ayout-errors-caused-by-javascript-files.md |    2 +-
 ...identify-promotions-applied-to-the-cart.md |    6 +-
 ...import-pickup-points-using-spreadsheets.md |    4 +-
 ...llection-of-products-in-the-shop-window.md |   18 +-
 ...ata-when-exporting-a-prices-spreadsheet.md |    4 +-
 ...reverse-proxy-in-front-of-vtex-services.md |   25 +-
 .../en/how-to-install-a-service-worker.md     |   26 +-
 ...n-external-gift-card-provider-with-vtex.md |   20 +-
 .../en/how-to-manage-subscriptions.md         |   14 +-
 .../en/how-to-manage-the-kit-stock.md         |   12 +-
 .../en/how-to-manually-invoice-an-order.md    |   11 +-
 ...o-modify-details-of-customers-addresses.md |   14 +-
 ...optimize-searches-with-substitute-words.md |   17 +-
 ...how-to-request-receivables-anticipation.md |    2 +-
 .../en/how-to-retrieve-the-access-password.md |   10 +-
 .../tutorials/en/how-to-return-order-items.md |   12 +-
 .../how-to-see-orders-closed-with-benefits.md |    2 +-
 ...fine-a-default-sla-for-recurrent-orders.md |    4 +-
 .../en/how-to-set-up-fingerprint-for-payu.md  |    2 +-
 ...set-up-recurrence-in-payment-conditions.md |    8 +-
 ...r-to-accept-payments-with-adyen-at-vtex.md |   18 +-
 ...t-up-the-device-fingerprint-for-braspag.md |    2 +-
 ...set-up-the-indeva-scheduled-appointment.md |   10 +-
 ...e-for-pick-up-field-in-smartcheckout-v6.md |    8 +-
 docs/tutorials/en/how-to-set-up-the-zoom.md   |    6 +-
 docs/tutorials/en/how-to-set-up-visa-debit.md |    6 +-
 ...w-to-set-up-your-store-on-seller-portal.md |   21 +-
 ...to-setup-google-analytics-in-vtex-store.md |    6 +-
 ...how-to-turn-my-store-website-into-a-pwa.md |   10 +-
 .../en/how-to-use-conditions-builder-app.md   |    6 +-
 .../en/how-to-use-the-index-report.md         |    8 +-
 .../en/how-to-use-the-meta-tags-control.md    |    6 +-
 .../how-to-use-the-search-result-control.md   |   10 +-
 .../en/how-to-use-the-shareable-cart-app.md   |   28 +-
 ...how-to-view-taxes-information-in-taxhub.md |    2 +-
 ...how-to-view-transactions-on-pci-gateway.md |    2 +-
 ...ith-different-layouts-for-the-same-page.md |    2 +-
 docs/tutorials/en/how-trade-policies-work.md  |    9 +-
 .../en/i-cant-import-the-price-table.md       |   67 +
 .../en/i-cant-receive-emails-from-vtex.md     |   98 ++
 ...-cant-update-the-ean-of-my-skus-via-api.md |   50 +
 ...-view-the-product-in-the-search-results.md |  241 +++
 docs/tutorials/en/image-compression.md        |   63 +
 docs/tutorials/en/image-widget.md             |   12 +-
 .../en/import-customer-data-brazil.md         |   56 +-
 ...-and-exporting-an-inventory-spreadsheet.md |    6 +-
 .../en/importing-data-into-master-data.md     |   10 +-
 .../en/importing-images-from-a-spreadsheet.md |   10 +-
 ...roving-the-seo-of-product-listing-pages.md |    4 +-
 docs/tutorials/en/indexes-in-master-data.md   |   88 ++
 docs/tutorials/en/indexing-history-beta.md    |   18 +-
 docs/tutorials/en/indexing-history.md         |   67 +
 docs/tutorials/en/indexing.md                 |   28 +
 ...information-about-chile-custom-payments.md |    6 +-
 ...ormation-about-colombia-custom-payments.md |    6 +-
 ...formation-about-uruguay-custom-payments.md |    6 +-
 ...inserting-images-into-let-me-know-email.md |    2 +-
 ...g-my-orders-through-the-extension-store.md |    6 +-
 docs/tutorials/en/integrating-with-enjoei.md  |    4 +-
 .../en/integrating-with-madeiramadeira.md     |    4 +-
 .../integrating-with-renner-and-camicado.md   |    6 +-
 ...integration-guide-for-erps-full-catalog.md |    2 +-
 ...-guide-for-marketplaces-seller-non-vtex.md |    6 +-
 .../en/integration-with-google-tag-manager.md |   10 +-
 ...lligent-search-synonym-suggestions-beta.md |   41 +-
 docs/tutorials/en/intelligent-synonyms.md     |   68 +
 ...racting-with-masterdata-through-graphql.md |   10 +-
 docs/tutorials/en/interaction-details.md      |   26 +-
 ...erpreting-the-data-of-the-oms-order-bar.md |    2 +-
 .../tutorials/en/introduction-to-vtex-apis.md |    2 +-
 .../en/inventory-data-pipeline-beta.md        |   97 ++
 docs/tutorials/en/inventory-update-history.md |   15 +-
 docs/tutorials/en/kit-registration.md         |   20 +-
 docs/tutorials/en/kr1-test.md                 |   18 +
 .../lead-time-shipping-time-at-sku-level.md   |  104 ++
 .../tutorials/en/license-manager-resources.md |   18 +-
 ...-the-store-by-means-of-the-trade-policy.md |   66 +
 ...g-urls-to-banners-using-the-site-editor.md |    4 +-
 .../list-of-payment-providers-by-country.md   |    6 +-
 docs/tutorials/en/loading-dock.md             |    2 +-
 .../en/locations-details-page-beta.md         |    6 +-
 .../tutorials/en/logistics-module-overview.md |   12 +-
 .../en/making-a-master-data-field-editable.md |   31 +
 .../en/manage-the-sales-comissions-report.md  |    2 +-
 .../en/managing-b2b-organizations.md          |  100 ++
 .../managing-credit-with-customer-credit.md   |    4 +-
 .../en/managing-delivery-capacity.md          |   22 +-
 docs/tutorials/en/managing-http-headers.md    |   65 +
 .../en/managing-page-and-template-content.md  |    6 +-
 docs/tutorials/en/managing-pages.md           |   42 +-
 docs/tutorials/en/managing-placeholders.md    |    6 +-
 docs/tutorials/en/managing-projects.md        |  129 ++
 .../en/managing-redirects-per-binding.md      |   16 +-
 .../en/managing-shipping-policies.md          |  114 ++
 .../en/managing-singleton-content-types.md    |   31 +-
 docs/tutorials/en/managing-stock-items.md     |   37 +-
 docs/tutorials/en/managing-url-redirects.md   |   19 +-
 .../en/managing-users-in-b2b-organizations.md |   67 +
 docs/tutorials/en/managing-users.md           |   81 +-
 .../en/marketplace-invited-sellers.md         |    2 +-
 docs/tutorials/en/marketplace-overview.md     |    6 +-
 .../en/marketplace-strategies-at-vtex.md      |  243 +--
 .../en/marketplaces-and-integrations.md       |    8 +-
 docs/tutorials/en/master-data.md              |  324 ++--
 .../en/match-offers-mercado-livre.md          |   20 +
 docs/tutorials/en/media-overview.md           |   89 +-
 docs/tutorials/en/mercado-libre-size-chart.md |   20 +
 .../en/merchandising-rule-conditions.md       |   32 +
 docs/tutorials/en/merchandising-rules-list.md |   71 +
 ...re-not-displayed-in-the-order-dashboard.md |   43 +
 .../minimum-stock-control-for-integrations.md |    2 +-
 docs/tutorials/en/mode-off-faq.md             |   11 +-
 ...moving-order-to-start-handling-shipping.md |    8 +-
 .../en/multilevel-omnichannel-inventory.md    |   70 +-
 ...my-ad-is-not-displayed-on-mercado-livre.md |   19 +
 docs/tutorials/en/my-inventory-is-negative.md |   34 +
 .../my-orders-in-mercado-libre-have-errors.md |   20 +
 .../en/my-store-order-was-not-created.md      |   64 +
 .../en/names-of-vtex-branches-worldwide.md    |    2 +-
 docs/tutorials/en/navigation.md               |  208 +++
 .../new-integration-with-erede-erederest.md   |   10 +-
 ...n-vtex-cmc-newsletteroptin-greater-than.md |    6 +-
 docs/tutorials/en/offer-details.md            |   24 +-
 ...moderation-and-quality-of-mercado-libre.md |    4 +-
 docs/tutorials/en/offer-management.md         |   18 +-
 docs/tutorials/en/offer-quality-filters.md    |   12 +-
 docs/tutorials/en/offer-status.md             |  241 +++
 ...-the-same-vtex-sellers-and-marketplaces.md |    2 +-
 docs/tutorials/en/oms-page-structure.md       |   16 +-
 ...pening-tickets-to-vtex-support-finacial.md |   15 +-
 .../en/opening-tickets-to-vtex-support.md     |    8 +-
 .../tutorials/en/operational-capacity-beta.md |  198 +++
 ...ization-of-shipping-options-at-checkout.md |    2 +-
 .../en/order-allocation-algorithm-beta.md     |    6 +-
 ...-cancellation-requested-by-the-customer.md |    8 +-
 docs/tutorials/en/order-details-page.md       |   35 +-
 ...errors-in-the-mercado-livre-integration.md |    4 +-
 docs/tutorials/en/order-flow-and-status.md    |   18 +-
 docs/tutorials/en/order-replacement.md        |    6 +-
 docs/tutorials/en/order-report.md             |    8 +-
 .../en/order-split-and-delivery-split.md      |    7 +-
 .../en/order-transactional-email-templates.md |   32 +-
 docs/tutorials/en/orderform-settings.md       |   40 +
 ...-window-display-and-on-the-product-page.md |    2 +-
 docs/tutorials/en/orders-list.md              |    6 +-
 docs/tutorials/en/orders-overview.md          |   15 +-
 docs/tutorials/en/orders.md                   |  372 +++++
 .../en/overview-of-b2b-orders-history.md      |   30 +
 docs/tutorials/en/overview-pricing-module.md  |    8 +-
 .../tutorials/en/payment-provider-protocol.md |  148 +-
 docs/tutorials/en/payments.md                 |   99 ++
 .../en/payu-romania-refund-details.md         |    2 +-
 docs/tutorials/en/pci-gateway-overview.md     |    2 +-
 ...ration-testing-and-vulnerability-notice.md |  158 +-
 .../en/permissions-management-in-b2b-suite.md |   68 +
 .../en/physical-store-instore-beta.md         |    4 +-
 .../pickup-points-for-subscription-orders.md  |   54 +
 docs/tutorials/en/pickup-points.md            |   10 +-
 docs/tutorials/en/plan-your-project.md        |    6 +-
 .../en/planner-calendar-page-beta.md          |    6 +-
 .../en/planner-releases-page-beta.md          |    2 +-
 docs/tutorials/en/predefined-roles.md         | 1339 +++-------------
 ...ier-from-meeting-certain-zip-code-range.md |    9 +-
 docs/tutorials/en/price-divergence-rule.md    |    6 +-
 .../en/price-divergence-rules-beta.md         |    2 +-
 ...e-table-management-in-b2b-organizations.md |   48 +
 docs/tutorials/en/price-waterfall.md          |    2 +-
 .../tutorials/en/prices-data-pipeline-beta.md |   92 ++
 docs/tutorials/en/prices-settings.md          |    6 +-
 docs/tutorials/en/prices.md                   |    6 +-
 docs/tutorials/en/product-list.md             |    8 +-
 docs/tutorials/en/products-and-skus-beta.md   |   22 +-
 docs/tutorials/en/promotion-alerts-beta.md    |    2 +-
 docs/tutorials/en/promotion-list-beta.md      |   10 +-
 docs/tutorials/en/promotion-summary.md        |    6 +-
 docs/tutorials/en/promotions-beta.md          |    8 +-
 docs/tutorials/en/promotions-overview.md      |    6 +-
 .../tutorials/en/promotions-simulator-beta.md |  116 +-
 docs/tutorials/en/promotions-simulator.md     |    6 +-
 docs/tutorials/en/promotions.md               |  108 ++
 .../protection-against-transaction-attacks.md |   14 +-
 docs/tutorials/en/ready-to-dispatch.md        |    4 +-
 docs/tutorials/en/received-skus-beta.md       |  224 +++
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |  116 ++
 .../en/redirect-from-other-addresses.md       |   81 +
 docs/tutorials/en/redirects.md                |   41 +
 docs/tutorials/en/registered-ticket-flow.md   |    4 +-
 docs/tutorials/en/registering-a-category.md   |    6 +-
 docs/tutorials/en/registering-brands.md       |    2 +-
 .../en/registering-gateway-affiliations.md    |   83 +-
 docs/tutorials/en/registering-geolocation.md  |    8 +-
 ...ing-the-skus-barcode-for-vtex-sales-app.md |    4 +-
 ...-with-nominal-discount-based-on-formula.md |    8 +-
 .../en/regular-promotion-with-reward-value.md |   16 +-
 docs/tutorials/en/regular-promotion.md        |   14 +-
 docs/tutorials/en/releases-module-beta.md     |    4 +-
 .../en/releasing-the-store-for-production.md  |    2 +-
 docs/tutorials/en/relevance-rules.md          |  108 ++
 ...request-headers-must-only-contain-ascii.md |   90 ++
 .../en/requesting-a-new-organization.md       |   97 ++
 .../requesting-an-additional-trade-policy.md  |   17 +-
 ...factor-authentication-app-configuration.md |   31 +-
 .../responsibilities-in-the-vtex-ecosystem.md |  201 +++
 .../en/responsive-vs-mobile-version.md        |    2 +-
 ...ict-public-access-to-master-data-fields.md |   57 +
 docs/tutorials/en/risk-assessment.md          |  465 ++++++
 docs/tutorials/en/roles.md                    |  103 +-
 docs/tutorials/en/rounding-rules.md           |    8 +-
 .../en/sales-app-sales-performance.md         |    4 +-
 .../sales-associate-code-field-at-checkout.md |   96 ++
 .../en/sales-associates-instore-beta.md       |    4 +-
 docs/tutorials/en/sales-performance.md        |   10 +-
 docs/tutorials/en/scheduled-delivery.md       |    8 +-
 .../scheduling-features-for-special-events.md |    2 +-
 docs/tutorials/en/search-behavior.md          |  135 ++
 docs/tutorials/en/search-configuration.md     |   52 +
 docs/tutorials/en/search-navigator-control.md |    4 +-
 docs/tutorials/en/searching-for-old-orders.md |    2 +-
 .../searching-for-transactions-on-payments.md |    4 +-
 docs/tutorials/en/security-certificate-ssl.md |   26 +
 .../en/security-education-and-awareness.md    |    4 +-
 docs/tutorials/en/security-monitor.md         |  130 ++
 docs/tutorials/en/seller-management.md        |    4 +-
 docs/tutorials/en/seller-monitoring.md        |   60 +
 .../en/seller-portal-creating-a-promotion.md  |  102 ++
 ...tal-getting-started-for-the-marketplace.md |    2 +-
 .../en/seller-portal-product-details.md       |    2 +-
 docs/tutorials/en/seller-portal-promotions.md |   97 ++
 .../en/seller-portal-shared-products.md       |   11 +-
 ...nd-item-price-with-tax-shown-separately.md |   22 +-
 .../en/sending-sku-attributes-to-amazon.md    |    4 +-
 docs/tutorials/en/sent-offers-beta.md         |    2 +-
 .../en/sent-offers-buybox-opportunities.md    |   18 +-
 docs/tutorials/en/set-up-mundi-gateway.md     |   12 +-
 ...r-authentication-for-recurring-payments.md |    2 +-
 ...ct-suggestions-accessories-and-generics.md |    8 +-
 .../en/setting-up-abandoned-carts.md          |   22 +-
 .../tutorials/en/setting-up-amazonpay-beta.md |    2 +-
 ...app-linking-for-payments-app-in-instore.md |    2 +-
 .../setting-up-bradesco-registered-ticket.md  |    2 +-
 .../en/setting-up-braspag-gateway.md          |    6 +-
 .../en/setting-up-conductor-gateway.md        |   15 +-
 .../en/setting-up-cybersource-antifraud.md    |   32 +-
 .../en/setting-up-cybersource-gateway.md      |  224 ++-
 .../en/setting-up-firstdata-acquirer.md       |   54 +-
 ...-getnet-acquirer-with-egetnet-connector.md |   30 +-
 ...ent-search-integration-with-the-catalog.md |   31 +
 ...-itau-registered-ticket-itau-registrado.md |   42 +-
 .../en/setting-up-itau-registered-ticket.md   |    4 +-
 ...eto-in-installments-as-a-payment-method.md |    6 +-
 .../setting-up-mercadopagov1-sub-acquirer.md  |   18 +-
 .../setting-up-mercadopagov2-sub-acquirer.md  |   72 +-
 .../en/setting-up-merchant-id-in-apple-pay.md |   40 +-
 ...g-up-mundipagg-fraud-prevention-gateway.md |   15 +-
 .../en/setting-up-mundipagg-gateway.md        |   15 +-
 docs/tutorials/en/setting-up-my-account.md    |    8 +-
 .../en/setting-up-nexxpago-gateway.md         |   24 +-
 docs/tutorials/en/setting-up-nps-gateway.md   |    8 +-
 .../en/setting-up-pagar-me-gateway.md         |   11 +-
 .../en/setting-up-pagarmev2-gateway.md        |   20 +-
 .../en/setting-up-pagbrasil-gateway.md        |   15 +-
 .../en/setting-up-paghiper-gateway.md         |   15 +-
 docs/tutorials/en/setting-up-pagseguro-v3.md  |   40 +-
 .../en/setting-up-payment-with-paypal.md      |    8 +-
 .../en/setting-up-paymentez-gateway.md        |   26 +-
 .../en/setting-up-payments-with-55pay.md      |    4 +-
 .../en/setting-up-payments-with-99pay.md      |   14 +-
 .../en/setting-up-payments-with-aarin.md      |    4 +-
 .../en/setting-up-payments-with-addi.md       |   14 +-
 .../en/setting-up-payments-with-alignet.md    |   24 +-
 .../en/setting-up-payments-with-alignetv2.md  |   39 +
 .../setting-up-payments-with-ame-digital.md   |   14 +-
 .../en/setting-up-payments-with-apple-pay.md  |   42 +-
 .../en/setting-up-payments-with-appmax.md     |   33 +
 .../en/setting-up-payments-with-argonpay.md   |   50 +
 .../en/setting-up-payments-with-astropay.md   |   20 +-
 .../en/setting-up-payments-with-bamboo.md     |   10 +-
 ...tting-up-payments-with-bancolombia-bnpl.md |   16 +-
 .../en/setting-up-payments-with-banqi.md      |   14 +-
 .../en/setting-up-payments-with-bitfy.md      |   14 +-
 .../en/setting-up-payments-with-bluepay.md    |   14 +-
 .../en/setting-up-payments-with-boletoflex.md |   11 +-
 ...etting-up-payments-with-bom-pra-credito.md |    4 +-
 .../en/setting-up-payments-with-braintree.md  |   49 +
 .../en/setting-up-payments-with-braspagv2.md  |    6 +-
 ...-up-payments-with-brinks-cash-ecommerce.md |   16 +-
 ...setting-up-payments-with-cieloecommerce.md |   66 +
 .../en/setting-up-payments-with-cielov4.md    |    6 +-
 .../en/setting-up-payments-with-conekta.md    |   22 +-
 .../en/setting-up-payments-with-crecoscorp.md |   10 +-
 .../setting-up-payments-with-credimarcas.md   |   60 +
 .../en/setting-up-payments-with-credit-key.md |   20 +-
 .../en/setting-up-payments-with-culqi.md      |   58 +
 .../en/setting-up-payments-with-dapp.md       |   39 +
 .../en/setting-up-payments-with-deuna.md      |   48 +
 ...tting-up-payments-with-digital-river-v2.md |   14 +-
 ...etting-up-payments-with-dlocal-payments.md |   14 +-
 .../en/setting-up-payments-with-dock.md       |    4 +-
 .../en/setting-up-payments-with-e-sitef.md    |   48 +
 ...ng-up-payments-with-easypay-marketplace.md |   18 +
 ...setting-up-payments-with-easypay-seller.md |   51 +
 .../en/setting-up-payments-with-easypay.md    |  210 +++
 .../setting-up-payments-with-ebanx-local.md   |   14 +-
 .../en/setting-up-payments-with-ebanx.md      |   14 +-
 .../en/setting-up-payments-with-egetnetv2.md  |   30 +-
 .../en/setting-up-payments-with-etpay.md      |   18 +-
 .../setting-up-payments-with-evopayments.md   |   46 +
 ...payments-with-fcamara-payment-initiator.md |   14 +-
 .../en/setting-up-payments-with-fintoc.md     |   39 +
 .../en/setting-up-payments-with-flywire.md    |   28 +-
 .../en/setting-up-payments-with-fpay.md       |   20 +-
 .../en/setting-up-payments-with-geru.md       |   40 +
 .../en/setting-up-payments-with-gocuotas.md   |   39 +
 .../en/setting-up-payments-with-guatapay.md   |   39 +
 .../en/setting-up-payments-with-inswitch.md   |   49 +
 .../en/setting-up-payments-with-itau-rede.md  |   91 ++
 .../en/setting-up-payments-with-iugu.md       |   73 +-
 .../en/setting-up-payments-with-k8bank.md     |   44 +
 .../en/setting-up-payments-with-kaiowa.md     |   14 +-
 .../en/setting-up-payments-with-khipu.md      |   22 +-
 .../setting-up-payments-with-koin-payments.md |   22 +-
 .../en/setting-up-payments-with-koin.md       |    8 +-
 .../en/setting-up-payments-with-kueski-pay.md |   12 +-
 ...etting-up-payments-with-liquido-payment.md |   32 +
 .../en/setting-up-payments-with-mach.md       |   16 +-
 .../en/setting-up-payments-with-meliuz.md     |    4 +-
 .../setting-up-payments-with-mercado-pago.md  |   13 +-
 .../en/setting-up-payments-with-mobbex.md     |   34 +
 .../setting-up-payments-with-msc-payment.md   |   51 +
 ...ayments-with-netpay-and-netpay-checkout.md |   24 +-
 .../setting-up-payments-with-notes-payable.md |   56 +
 .../en/setting-up-payments-with-nupay.md      |    4 +-
 .../en/setting-up-payments-with-nuvei.md      |   69 +
 .../en/setting-up-payments-with-pagaleve.md   |    4 +-
 .../en/setting-up-payments-with-pagarmev3.md  |   28 +-
 .../setting-up-payments-with-pagbrasilv2.md   |   40 +
 .../en/setting-up-payments-with-paghiperv2.md |   36 +
 .../en/setting-up-payments-with-paghiperv3.md |   38 +
 .../setting-up-payments-with-pagoefectivo.md  |    6 +-
 ...setting-up-payments-with-pagoefectivov2.md |   55 +
 .../setting-up-payments-with-pagoexpress.md   |   40 +
 .../en/setting-up-payments-with-pagosweb.md   |    8 +-
 .../en/setting-up-payments-with-parcelex.md   |    4 +-
 .../en/setting-up-payments-with-pay4fun.md    |   40 +
 .../en/setting-up-payments-with-paycash.md    |   14 +-
 .../en/setting-up-payments-with-payclub.md    |    8 +-
 .../setting-up-payments-with-paymentezv2.md   |   34 +
 .../en/setting-up-payments-with-paypalv2.md   |   43 +
 .../en/setting-up-payments-with-payu-india.md |   20 +-
 .../en/setting-up-payments-with-payuv2.md     |   48 +
 .../en/setting-up-payments-with-payway.md     |   37 +
 .../en/setting-up-payments-with-picpay.md     |   16 +-
 .../en/setting-up-payments-with-pine-labs.md  |   18 +-
 .../en/setting-up-payments-with-poolpay.md    |   33 +
 .../en/setting-up-payments-with-powerpay.md   |   50 +
 ...etting-up-payments-with-puntos-colombia.md |   16 +-
 .../en/setting-up-payments-with-qhantuy.md    |   16 +-
 .../en/setting-up-payments-with-retrypay.md   |   30 +-
 .../setting-up-payments-with-safetypayv2.md   |   33 +
 .../en/setting-up-payments-with-scalapay.md   |   18 +-
 .../en/setting-up-payments-with-shipay.md     |   14 +-
 .../en/setting-up-payments-with-sibs.md       |   16 +-
 .../en/setting-up-payments-with-stark-bank.md |   34 +
 .../en/setting-up-payments-with-stelo.md      |    8 +-
 .../en/setting-up-payments-with-stelom1v2.md  |   33 +
 ...g-up-payments-with-store-card-cobranded.md |   20 +-
 ...payments-with-transfero-crypto-checkout.md |   49 +
 .../setting-up-payments-with-tyendacrypto.md  |   14 +-
 .../en/setting-up-payments-with-unlimit.md    |   44 +
 .../en/setting-up-payments-with-ventipay.md   |   16 +-
 .../en/setting-up-payments-with-virtuspay.md  |    6 +-
 .../setting-up-payments-with-virtuspayv2.md   |   14 +-
 ...setting-up-payments-with-webpayoneclick.md |   39 +
 .../en/setting-up-payments-with-wepay4u.md    |   52 +
 .../en/setting-up-payments-with-wompi.md      |   10 +-
 .../en/setting-up-payments-with-wompicov2.md  |   10 +-
 .../en/setting-up-payments-with-woovi.md      |   40 +
 .../en/setting-up-payments-with-yuno.md       |   14 +-
 .../en/setting-up-payments-with-zenki.md      |   20 +-
 .../en/setting-up-payments-with-zoop.md       |   24 +-
 docs/tutorials/en/setting-up-paypal-plus.md   |   64 +-
 docs/tutorials/en/setting-up-payu-gateway.md  |   15 +-
 .../tutorials/en/setting-up-payzen-gateway.md |    8 +-
 ...ng-up-personal-data-on-the-users-screen.md |   12 +-
 .../en/setting-up-place2pay-gateway.md        |    8 +-
 ...ting-up-price-tables-for-specific-users.md |    6 +-
 ...setting-up-rede-acquirer-with-erederest.md |    8 +-
 ...up-seller-white-label-as-a-pickup-point.md |   10 +-
 docs/tutorials/en/setting-up-shipment.md      |    2 +-
 .../setting-up-sitef-gateway-with-pre-auth.md |    8 +-
 docs/tutorials/en/setting-up-sitef-gateway.md |   18 +-
 .../en/setting-up-sms-password-recovery.md    |   12 +-
 .../en/setting-up-sub-acquirer-stelo.md       |    8 +-
 .../setting-up-the-notes-payable-conector.md  |   31 +
 .../en/setting-up-the-notify-me-option.md     |    2 +-
 .../en/setting-up-the-paymee-gateway.md       |   33 +-
 .../en/setting-up-the-price-range-filter.md   |    2 +-
 ...up-the-sales-funnel-on-google-analytics.md |   10 +-
 .../en/setting-up-the-tnspay-gateway.md       |    8 +-
 .../setting-up-the-type-of-interest-rate.md   |    2 +-
 .../en/setting-up-the-voucher-list.md         |    4 +-
 .../en/setting-up-the-worldpay-acquirer.md    |   41 +-
 .../setting-up-the-yamisplitmoipv1-gateway.md |   26 +-
 .../tutorials/en/setting-up-vcmais-gateway.md |    6 +-
 docs/tutorials/en/setting-up-vindi-gateway.md |   30 +-
 .../en/setting-up-webpay2p-gateway.md         |    4 +-
 docs/tutorials/en/setup-safetypay.md          |   18 +-
 ...ween-a-marketplace-and-a-seller-on-vtex.md |   12 +-
 docs/tutorials/en/shipping-options-beta.md    |   10 +-
 docs/tutorials/en/shipping-policy.md          |   86 +-
 docs/tutorials/en/shipping-rate-template.md   |   10 +-
 docs/tutorials/en/shipping-rates.md           |    2 +-
 docs/tutorials/en/shipping-simulation.md      |    8 +-
 docs/tutorials/en/shipping-strategy.md        |   28 +-
 docs/tutorials/en/shopee-integration.md       |    4 +-
 docs/tutorials/en/site-editor-overview.md     |    2 +-
 docs/tutorials/en/sku-bindings.md             |    8 +-
 docs/tutorials/en/sku-price-change.md         |   40 +-
 docs/tutorials/en/sku-registration-fields.md  |    6 +-
 docs/tutorials/en/skus.md                     |  128 ++
 ...martcheckout-v5-general-characteristics.md |   69 +
 docs/tutorials/en/special-conditions.md       |   18 +-
 docs/tutorials/en/split-payment.md            |   44 +-
 docs/tutorials/en/store-access-permission.md  |    2 +-
 docs/tutorials/en/store-overview-beta.md      |  160 ++
 docs/tutorials/en/store-overview.md           |   18 +-
 docs/tutorials/en/store-profile.md            |   85 ++
 docs/tutorials/en/store-settings-overview.md  |    8 +-
 docs/tutorials/en/styles-overview.md          |    2 +-
 docs/tutorials/en/subscription-plans.md       |    2 +-
 docs/tutorials/en/synonym-list.md             |  112 ++
 docs/tutorials/en/table-of-base-prices.md     |    2 +-
 docs/tutorials/en/telesales-features.md       |    8 +-
 docs/tutorials/en/telesales-toolbar.md        |   17 +-
 docs/tutorials/en/test-kr1.md                 |   18 +
 ...-into-packages-with-separate-deliveries.md |   46 +
 ...sult-is-different-from-the-product-page.md |    6 +-
 ...help-the-performance-of-your-e-commerce.md |    6 +-
 docs/tutorials/en/total-shipping-cost.md      |    2 +-
 .../en/tracking-your-sales-analytics.md       |   16 +-
 ...actional-emails-for-subscription-orders.md |    8 +-
 docs/tutorials/en/transactions-events.md      |    2 +-
 .../en/transferring-store-ownership.md        |    4 +-
 ...eshooting-errors-in-subscription-orders.md |   14 +-
 docs/tutorials/en/understanding-b2b-orders.md |    2 +-
 .../en/understanding-how-indexation-works.md  |   14 +-
 .../en/understanding-how-the-cache-works.md   |    6 +-
 ...standing-storebuilder-and-stylesbuilder.md |   18 +-
 ...erstanding-the-additional-shipping-cost.md |    6 +-
 .../understanding-the-cubic-weight-factor.md  |   36 +-
 .../en/understanding-the-message-center.md    |    2 +-
 .../en/understanding-the-price-change-rule.md |    2 +-
 .../en/understanding-the-security-report.md   |    2 +-
 docs/tutorials/en/understanding-the-topbar.md |    8 +-
 .../understanding-the-updating-of-the-xml.md  |    6 +-
 ...nderstanding-vtexs-email-capture-system.md |    8 +-
 .../untitled-entry-2024-03-13-at-16-25-15.md  |   18 +
 .../untitled-entry-2024-07-25-at-21-25-31.md  |   18 +
 ...ting-the-quantity-of-items-in-inventory.md |    2 +-
 .../en/using-recaptcha-at-checkout.md         |   51 +-
 ...-track-browsing-sessions-in-vtex-stores.md |    2 +-
 .../en/using-the-project-task-timeline.md     |    6 +-
 ...r-store-and-uploading-it-for-production.md |    6 +-
 .../en/via-inventory-integration-errors.md    |    4 +-
 .../visao-geral-configuracoes-de-usuario.md   |    2 +-
 docs/tutorials/en/vtex-ad-network-beta.md     |  123 ++
 docs/tutorials/en/vtex-admin-start-here.md    |   63 +-
 docs/tutorials/en/vtex-admin-start-here1.md   |   10 +-
 docs/tutorials/en/vtex-agreement.md           |   34 +
 ...vtex-dashboard-guide-for-black-week-faq.md |  201 +++
 docs/tutorials/en/vtex-do-interface.md        |   10 +-
 docs/tutorials/en/vtex-insurance.md           |  117 +-
 ...gent-search-multilanguage-settings-beta.md |   18 +-
 docs/tutorials/en/vtex-invoice-notifier.md    |   12 +-
 ...x-operation-service-level-agreement-sla.md |   26 +
 .../en/vtex-pick-and-pack-fulfillment.md      |    8 +-
 .../en/vtex-pick-and-pack-insights.md         |   65 +
 .../en/vtex-pick-and-pack-last-mile.md        |    8 +-
 .../tutorials/en/vtex-pick-and-pack-mobile.md |  224 +++
 .../tutorials/en/vtex-pick-and-pack-orders.md |   94 ++
 .../en/vtex-pick-and-pack-settings.md         |  267 ++++
 .../en/vtex-pick-and-pack-worksheets.md       |   79 +
 docs/tutorials/en/vtex-pick-and-pack.md       |    8 +-
 docs/tutorials/en/vtex-shield.md              |   63 +
 ...ex-shipping-network-correios-activation.md |   20 +
 .../en/vtex-shipping-network-correios-faq.md  |    4 +-
 .../en/vtex-shipping-network-dashboard.md     |   16 +-
 docs/tutorials/en/vtex-status-page.md         |  169 +++
 docs/tutorials/en/vtex-support-apac.md        |  182 +++
 docs/tutorials/en/warehouse.md                |    2 +-
 .../en/web-application-firewall-waf.md        |   58 +
 docs/tutorials/en/web-page-performance.md     |    4 +-
 ...urce-and-orders-with-fulfillment-source.md |    2 +-
 docs/tutorials/en/what-are-templates.md       |    2 +-
 ...payments-are-available-in-latin-america.md |    6 +-
 ...tivate-a-gift-multiplier-on-a-promotion.md |    2 +-
 ...r-as-revenue-in-the-billing-calculation.md |    2 +-
 .../en/what-is-a-franchise-account.md         |   25 +-
 docs/tutorials/en/what-is-a-service.md        |    6 +-
 docs/tutorials/en/what-is-a-transaction.md    |   10 +-
 docs/tutorials/en/what-is-an-affiliate.md     |    4 +-
 docs/tutorials/en/what-is-an-e-wallet.md      |    8 +-
 docs/tutorials/en/what-is-deposit-slip.md     |   15 +-
 ...rand-gateway-and-sub-acquirer-in-brazil.md |   22 +-
 ...ce-between-inventory-and-warehouse-dock.md |    2 +-
 ...-the-difference-between-product-and-sku.md |    8 +-
 ...what-is-the-maximum-limit-of-promotions.md |   14 +-
 docs/tutorials/en/what-is-the-pci-ssc.md      |    6 +-
 ...s-the-purpose-of-the-customized-control.md |    2 +-
 .../en/what-is-transparent-checkout.md        |    8 +-
 ...nditions-are-available-in-latin-america.md |    6 +-
 ...-when-my-report-does-not-reach-my-inbox.md |   15 +-
 ...app-ai-campaigns-management-and-details.md |   96 ++
 ...re-do-i-see-clients-that-use-recurrence.md |    2 +-
 ...y-certificates-may-be-added-to-my-store.md |    6 +-
 docs/tutorials/en/white-label-seller.md       |    5 +-
 .../en/white-label-sellers-selection.md       |   10 +-
 ...ketplace-orders-integrate-with-my-store.md |   43 +
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |    8 +-
 ...ing-an-effective-ticket-to-vtex-support.md |   67 +-
 .../es/ab-testing-how-where-when-and-why.md   |   73 +-
 docs/tutorials/es/access-control.md           |   61 +
 .../es/accessing-a-client-abandoned-cart.md   |   12 +-
 .../es/accessing-the-beta-environment.md      |   48 +-
 docs/tutorials/es/account-management.md       |   82 +-
 .../tutorials/es/account-settings-overview.md |    2 +-
 docs/tutorials/es/accounts-payable-brazil.md  |    7 +-
 docs/tutorials/es/activating-new-vtex-cdn.md  |    6 +-
 ...complete-list-link-on-the-category-menu.md |    4 +-
 ...-your-integration-for-change-order-beta.md |  305 ++++
 ...s-support-to-the-integration-with-adyen.md |    8 +-
 ...-a-url-mapping-through-worksheet-import.md |    2 +-
 ...a-client-secret-to-log-in-with-facebook.md |  125 +-
 ...d-a-client-secret-to-log-in-with-google.md |   24 +-
 .../adding-a-record-on-a-master-data-form.md  |   57 +
 docs/tutorials/es/adding-an-attachment.md     |    6 +-
 docs/tutorials/es/adding-bin-information.md   |   42 +
 docs/tutorials/es/adding-collections-cms.md   |   20 +-
 .../es/adding-sku-specifications-or-fields.md |   18 +-
 ...adding-specifications-or-product-fields.md |   10 +-
 .../tutorials/es/additional-shipping-costs.md |    8 +-
 ...dmin-redirect-search-returns-no-results.md |  110 ++
 docs/tutorials/es/admin-v4-getting-started.md |   10 +-
 docs/tutorials/es/ads-from-vtex-sales-app.md  |   52 +-
 .../advertising-with-vtex-ad-network-beta.md  |  161 ++
 docs/tutorials/es/affiliates-program-app.md   |   10 +-
 docs/tutorials/es/all-orders.md               |   19 +-
 docs/tutorials/es/amaro-integration.md        |   19 +
 ...mazon-multi-channel-fulfillment-mcf-app.md |    2 +-
 docs/tutorials/es/amazon-offer-matching.md    |   36 +-
 docs/tutorials/es/analytics.md                |   87 ++
 docs/tutorials/es/antifraud-provider.md       |   14 +-
 docs/tutorials/es/application-keys.md         |  184 ++-
 ...roving-payment-of-the-bank-payment-slip.md |    8 +-
 docs/tutorials/es/apps-overview.md            |    2 +-
 docs/tutorials/es/assembly-options-app.md     |    2 +-
 .../es/assembly-options-in-vtex-sales-app.md  |   55 +
 docs/tutorials/es/assembly-options.md         |    8 +-
 .../es/associate-a-sku-to-a-trade-policy.md   |   10 +-
 .../associating-a-template-with-a-layout.md   |    2 +-
 docs/tutorials/es/audit.md                    |  139 ++
 docs/tutorials/es/authentication.md           |   86 ++
 docs/tutorials/es/autocomplete.md             |   75 +
 docs/tutorials/es/availability.md             |   32 +
 docs/tutorials/es/b2b-checkout-settings.md    |   72 +
 .../es/b2b-cost-center-management.md          |  101 ++
 .../es/b2b-organization-general-settings.md   |   34 +
 docs/tutorials/es/b2b-overview.md             |    6 +-
 docs/tutorials/es/b2b-store-settings.md       |   42 +
 docs/tutorials/es/b2b-suite-overview.md       |   93 ++
 .../es/b2b-trade-policies-overview.md         |   33 +
 docs/tutorials/es/bank-reconciliations.md     |    6 +-
 docs/tutorials/es/banners.md                  |   68 +
 .../best-practices-against-virtual-attacks.md |   49 +-
 .../es/best-practices-application-keys.md     |    5 +-
 ...ces-for-accessing-the-store-without-www.md |   73 +
 ...ices-for-the-success-of-your-vtex-store.md |  171 +++
 ...actices-for-using-images-in-the-catalog.md |    4 +-
 docs/tutorials/es/best-practices-on-spf.md    |   12 +-
 ...ces-to-avoid-scams-using-the-vtex-brand.md |   53 +
 docs/tutorials/es/beta-price-configuration.md |    6 +-
 docs/tutorials/es/billing-module-overview.md  |    2 +-
 docs/tutorials/es/brands.md                   |    2 +-
 ...inging-app-content-into-the-admin-panel.md |    8 +-
 docs/tutorials/es/buy-one-get-one.md          |  133 +-
 ...e-articulos-del-mismo-sku-en-el-carrito.md |    2 +-
 docs/tutorials/es/campaign-audiences-list.md  |    4 +-
 docs/tutorials/es/campaign-audiences.md       |    2 +-
 docs/tutorials/es/campaign-promotion.md       |    4 +-
 docs/tutorials/es/canceling-orders.md         |   17 +-
 .../carrefour-inventory-integration-errors.md |    4 +-
 docs/tutorials/es/carrier-working-hours.md    |   51 +-
 ...rking-hours-and-scheduled-delivery-beta.md |    6 +-
 docs/tutorials/es/carries-on-vtex.md          |    4 +-
 docs/tutorials/es/catalog-overview-2.md       |    8 +-
 docs/tutorials/es/catalog-overview.md         |   35 +-
 docs/tutorials/es/categories.md               |    4 +-
 .../es/category-registration-fields.md        |   10 +-
 .../es/change-a-placeholder-title.md          |    4 +-
 docs/tutorials/es/change-seller.md            |    4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |    2 +-
 ...ult-system-texts-displayed-in-the-store.md |    4 +-
 .../changing-items-from-a-complete-order.md   |    7 +-
 .../changing-the-total-cost-of-the-order.md   |    4 +-
 docs/tutorials/es/changing-tracking-data.md   |    2 +-
 .../es/check-order-delivery-details.md        |    2 +-
 ...-order-delivery-deadline-was-calculated.md |   12 +-
 docs/tutorials/es/checkout-vtex-overview.md   |    2 +-
 ...chitecture-or-an-additional-environment.md |   38 +-
 ...ount-franchise-account-or-seller-portal.md |    8 +-
 docs/tutorials/es/cms-overview.md             |    8 +-
 docs/tutorials/es/cms-store-overview.md       |    2 +-
 .../es/collection-highlight-control.md        |    6 +-
 ...ipacao-dos-recebiveis-pelo-vtex-payment.md |    2 +-
 .../es/conditions-builder-usage-examples.md   |    6 +-
 docs/tutorials/es/conecta-la-integration.md   |    6 +-
 docs/tutorials/es/configure-cartman.md        |   37 +-
 ...e-direct-consumer-credit-cdc-by-losango.md |    4 +-
 ...yee-benefits-using-master-data-clusters.md |    4 +-
 .../configure-payment-with-pix-at-nubank.md   |    4 +-
 .../es/configure-payment-with-shopfacil.md    |   18 +
 .../es/configure-seller-regionalization.md    |    6 +-
 ...figure-template-in-smartcheckout-update.md |   30 +-
 ...configure-template-in-the-smartcheckout.md |   24 +-
 ...g-a-discount-for-orders-prepaid-in-full.md |    2 +-
 .../configuring-a-marketplace-trade-policy.md |   28 +-
 ...uring-a-pricing-rule-for-a-sales-policy.md |    6 +-
 .../es/configuring-a-registered-boleto.md     |   24 +-
 ...nfiguring-a-santander-registered-boleto.md |    6 +-
 docs/tutorials/es/configuring-affiliates.md   |    8 +-
 docs/tutorials/es/configuring-banners.md      |   70 +
 ...port-for-organizations-and-cost-centers.md |   68 +
 .../es/configuring-cargo-splitting.md         |   13 +-
 .../es/configuring-cielo-acquirer.md          |    6 +-
 ...ng-clearsale-global-anti-fraud-solution.md |    2 +-
 .../es/configuring-clearsale-v3-antifraud.md  |   46 +-
 ...ders-prepaid-in-full-on-google-shopping.md |   11 +-
 ...nctions-in-the-message-center-templates.md |    2 +-
 .../es/configuring-kushki-gateway.md          |   28 +-
 ...figuring-login-with-facebook-and-google.md |   49 +-
 ...automatic-payment-settlement-time-frame.md |    2 +-
 ...guring-mercado-pagos-device-fingerprint.md |    4 +-
 ...ring-my-account-conversational-commerce.md |    8 +-
 .../es/configuring-openpay-payment-gateway.md |   29 +-
 .../configuring-payment-conditions-for-b2b.md |   43 +
 ...-payment-with-adyenv3-in-vtex-sales-app.md |   51 +-
 .../es/configuring-payment-with-adyenv3.md    |   76 +-
 .../es/configuring-price-divergence-rule.md   |   65 +-
 .../es/configuring-product-visited.md         |   10 +-
 ...configuring-promotions-for-marketplaces.md |   97 +-
 ...iguring-promotions-with-a-highlightflag.md |   10 +-
 ...uring-pwa-in-your-store-framework-store.md |   73 +
 docs/tutorials/es/configuring-redirects.md    |   81 +
 ...iguring-samsung-pay-as-a-payment-method.md |   34 +-
 ...guring-seller-allocation-for-buying-xky.md |   51 +
 .../es/configuring-seo-in-your-store.md       |   62 +
 .../es/configuring-shipping-promotions.md     |   12 +-
 .../configuring-sign-in-with-apple-id-beta.md |   88 ++
 .../configuring-stripe-gateway-affiliation.md |   87 +-
 .../es/configuring-the-scheduled-delivery.md  |    4 +-
 .../es/configuring-the-store-domain.md        |  103 ++
 .../configuring-tuna-gateway-affiliation.md   |   12 +-
 .../es/configuring-vtex-marketplace.md        |    8 +-
 ...g-a-layout-from-one-web-site-to-another.md |    2 +-
 docs/tutorials/es/coupons-list-beta.md        |   12 +-
 .../es/creating-a-campaign-audience.md        |    9 +-
 ...o-guarantee-it-as-an-option-at-checkout.md |   30 +-
 docs/tutorials/es/creating-a-coupon-beta.md   |    8 +-
 .../es/creating-a-more-for-less-promotion.md  |  149 +-
 .../es/creating-a-product-collection.md       |   16 +-
 .../es/creating-a-shipping-policy.md          |   71 +
 .../es/creating-a-subscription-plan.md        |    2 +-
 .../es/creating-a-subscription-promotion.md   |    2 +-
 docs/tutorials/es/creating-a-trade-policy.md  |   39 +-
 docs/tutorials/es/creating-a-type-of-list.md  |    4 +-
 .../creating-an-application-in-master-data.md |   49 +-
 .../es/creating-an-oauth2-authentication.md   |    2 +-
 ...h-promotional-price-using-a-price-table.md |    4 +-
 .../tutorials/es/creating-collections-beta.md |   27 +-
 ...eating-custom-queries-in-master-data-v1.md |   62 +
 ...ustomer-and-address-forms-in-new-stores.md |   19 +-
 .../es/creating-form-in-master-data.md        |   58 +-
 .../es/creating-landing-pages-per-binding.md  |    2 +-
 docs/tutorials/es/creating-landing-pages.md   |   11 +-
 ...ating-merchandising-rules-manual-editor.md |   98 ++
 ...-merchandising-rules-visual-editor-beta.md |  110 +-
 ...ating-merchandising-rules-visual-editor.md |  100 ++
 docs/tutorials/es/creating-price-tables.md    |   23 +-
 ...eating-promotion-for-a-customer-cluster.md |    8 +-
 docs/tutorials/es/creating-promotions.md      |    2 +-
 ...etween-master-data-entities-using-admin.md |   44 +-
 docs/tutorials/es/creating-roles.md           |   98 ++
 .../es/creating-service-for-a-sku.md          |   15 +-
 ...ing-subaccount-multi-store-multi-domain.md |   65 +
 docs/tutorials/es/creating-surchargestaxes.md |   37 +-
 docs/tutorials/es/creating-synonyms.md        |   96 ++
 .../es/creating-trigger-in-master-data.md     |  197 +--
 .../es/credit-card-basic-payment-flow.md      |    2 +-
 docs/tutorials/es/criar-um-produto-beta.md    |  174 +++
 ...stom-fields-when-adding-an-organization.md |   48 +
 ...ustom-payment-information-for-argentina.md |    6 +-
 docs/tutorials/es/custom-product-fields.md    |   90 ++
 docs/tutorials/es/customer-approval.md        |   24 +-
 docs/tutorials/es/customer-credit-overview.md |   94 +-
 .../es/customizing-your-stores-typography.md  |    4 +-
 docs/tutorials/es/dashboards-overview.md      |    5 +-
 ...data-dictionary-vtex-data-pipeline-beta.md |   53 +
 docs/tutorials/es/data-entity.md              |  109 ++
 docs/tutorials/es/data-subject-rights.md      |    6 +-
 .../es/database-maintenance-full-cleanup.md   |    8 +-
 .../es/declining-order-cancelation.md         |   89 ++
 ...andatory-fields-in-master-data-v1-forms.md |   30 +
 docs/tutorials/es/defining-window-displays.md |   12 +-
 docs/tutorials/es/deleting-a-category.md      |    2 +-
 ...liveries-progress-vtex-shipping-network.md |    4 +-
 .../es/detaching-skus-by-specification.md     |   35 +
 ...e-the-minimum-number-of-items-in-a-cart.md |   21 +-
 .../es/direct-migration-magazine-luiza.md     |   20 +
 docs/tutorials/es/disable-cloudflare-proxy.md |    2 +-
 ...isplaying-the-store-in-another-language.md |    2 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |   84 ++
 ...ty-in-the-online-tokenized-payment-flow.md |   40 +
 ...ic-relevance-in-intelligent-search-beta.md |   78 +
 ...-field-on-profile-system-of-master-data.md |   30 +-
 docs/tutorials/es/enable-checkout-v6.md       |    4 +-
 .../enabling-2-factor-authentication-login.md |   22 +-
 ...enabling-3ds2-for-redsys-v2-integration.md |   10 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |    6 +-
 ...ng-pwa-push-notifications-in-your-store.md |    2 +-
 .../es/entering-tax-receipts-in-the-order.md  |    2 +-
 docs/tutorials/es/erasing-customer-data.md    |   66 +
 ...-skus-via-spreadsheet-in-the-vtex-admin.md |   40 +
 .../tutorials/es/events-available-in-audit.md |  845 +++--------
 docs/tutorials/es/explained-search.md         |   31 +
 ...mporting-product-and-sku-specifications.md |   14 +-
 docs/tutorials/es/exporting-data.md           |   26 +-
 docs/tutorials/es/facebook-faq.md             |    6 +-
 .../es/facilitating-b2b-store-operation.md    |    8 +-
 docs/tutorials/es/faq-security-2.md           |    2 +-
 .../es/faq-security-restricted-content.md     |  187 +++
 ...-import-spreadsheets-fixed-price-fields.md |    2 +-
 docs/tutorials/es/filtering-all-orders.md     |   25 +-
 .../es/filtering-data-on-master-data.md       |   91 +-
 .../filtering-transactions-on-pci-gateway.md  |    4 +-
 docs/tutorials/es/filters.md                  |   51 +
 ...tplaces-and-sellers-in-the-vtex-network.md |   10 +-
 docs/tutorials/es/find-sellers.md             |   57 +
 ...d-questions-new-orders-module-interface.md |   12 +-
 .../es/fulfillment-logistics-vtex.md          |    2 +-
 docs/tutorials/es/fulfillment-magalu.md       |   18 +
 .../es/general-configurations-on-the-oms.md   |    8 +-
 docs/tutorials/es/geolocation-at-checkout.md  |    4 +-
 docs/tutorials/es/gift-card.md                |   16 +-
 docs/tutorials/es/google-analytics-faq.md     |   37 +-
 .../es/google-integration-warnings.md         |   20 +
 docs/tutorials/es/google-pay-beta.md          |    8 +-
 docs/tutorials/es/headless-cms-overview.md    |   53 +
 .../how-and-when-do-i-receive-my-invoice.md   |   14 +-
 ...how-can-i-change-the-domain-of-my-store.md |    2 +-
 ...how-can-i-create-a-field-in-master-data.md |    4 +-
 .../es/how-can-i-create-callcenter-user.md    |    2 +-
 .../how-can-i-create-cluster-of-customers.md  |    6 +-
 ...-can-i-direct-a-financial-doubt-to-vtex.md |    6 +-
 ...e-newsletter-database-using-master-data.md |   17 +-
 .../how-can-my-customer-login-to-my-store.md  |   18 +-
 .../es/how-change-order-works-beta.md         |   77 +
 .../es/how-dns-configuration-works-on-vtex.md |   36 +
 ...ow-do-i-terminate-my-contract-with-vtex.md |   10 +-
 ...e-the-https-protocol-on-my-stores-pages.md |    8 +-
 ...reversals-work-when-an-item-is-returned.md |    4 +-
 .../es/how-does-promotion-proration-work.md   |    2 +-
 .../tutorials/es/how-does-reservation-work.md |    4 +-
 ...th-multiple-items-work-in-mercado-livre.md |    2 +-
 .../es/how-does-the-delivery-flow-work.md     |    2 +-
 .../es/how-does-the-score-field-work.md       |   51 +-
 .../es/how-does-the-type-of-delivery-work.md  |    6 +-
 .../es/how-is-pro-rata-calculated-in-vtex.md  |    2 +-
 ...-the-order-delivery-deadline-calculated.md |   34 +-
 ...-the-platforms-operation-sla-determined.md |   33 +-
 ...o-cancel-an-order-with-an-unpaid-boleto.md |    4 +-
 docs/tutorials/es/how-my-account-works.md     |   33 +-
 .../es/how-order-authorization-works.md       |    7 +-
 .../es/how-order-authorization-workss.md      |    2 +-
 .../es/how-promotion-competition-works.md     |  213 +++
 .../es/how-recursive-marketplace-works.md     |    2 +-
 .../es/how-shipping-calculation-works.md      |    5 +-
 ...hen-delivery-is-done-by-the-marketplace.md |   15 +-
 docs/tutorials/es/how-subscriptions-work.md   |   22 +-
 .../es/how-the-carrefour-integration-works.md |    4 +-
 .../es/how-the-order-replacement-works.md     |    2 +-
 .../es/how-the-seller-portal-catalog-works.md |    2 +-
 .../how-to-activate-the-shareable-cart-app.md |    4 +-
 docs/tutorials/es/how-to-alter-a-banner.md    |    6 +-
 .../tutorials/es/how-to-archive-ratestaxes.md |    2 +-
 .../es/how-to-capture-the-ip-of-an-order.md   |    4 +-
 .../tutorials/es/how-to-change-orders-beta.md |  217 +++
 ...he-order-of-payment-methods-at-checkout.md |    8 +-
 .../tutorials/es/how-to-check-your-balance.md |    2 +-
 .../es/how-to-configure-a-bank-slip.md        |   38 +-
 .../es/how-to-configure-a-custom-payment.md   |   12 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |    4 +-
 .../es/how-to-configure-payment-conditions.md |   16 +-
 ...to-configure-rating-and-review-controls.md |    4 +-
 .../es/how-to-configure-subscriptions.md      |   18 +-
 .../es/how-to-configure-the-anti-fraud.md     |   34 +-
 ...uro-without-redirect-option-transparent.md |   29 +-
 ...pment-environment-with-a-mobile-version.md |    2 +-
 ...ow-to-create-a-financial-access-profile.md |    6 +-
 .../es/how-to-create-a-page-template.md       |    8 +-
 docs/tutorials/es/how-to-create-a-product.md  |    6 +-
 ...eate-a-promotion-with-limitation-of-use.md |    2 +-
 .../es/how-to-create-a-store-name.md          |    2 +-
 ...how-to-create-a-subscription-attachment.md |    4 +-
 .../es/how-to-create-conditional-prices.md    |    2 +-
 ...ize-the-checkout-ui-custom-in-the-admin.md |   87 ++
 ...ow-to-define-the-url-for-a-product-page.md |    2 +-
 ...w-to-deprecate-and-undeprecate-your-app.md |    2 +-
 .../how-to-disable-a-transactional-email.md   |    2 +-
 .../es/how-to-download-the-vtex-invoices.md   |    6 +-
 .../es/how-to-identify-a-page-template.md     |    8 +-
 ...ayout-errors-caused-by-javascript-files.md |    2 +-
 ...identify-promotions-applied-to-the-cart.md |    6 +-
 ...import-pickup-points-using-spreadsheets.md |    4 +-
 ...llection-of-products-in-the-shop-window.md |   18 +-
 ...ata-when-exporting-a-prices-spreadsheet.md |    4 +-
 ...reverse-proxy-in-front-of-vtex-services.md |   25 +-
 .../es/how-to-install-a-service-worker.md     |   28 +-
 ...n-external-gift-card-provider-with-vtex.md |   17 +-
 .../es/how-to-manage-subscriptions.md         |   14 +-
 .../es/how-to-manage-the-kit-stock.md         |   18 +-
 .../es/how-to-manually-invoice-an-order.md    |   10 +-
 ...o-modify-details-of-customers-addresses.md |   12 +-
 ...optimize-searches-with-substitute-words.md |   14 +-
 ...how-to-request-receivables-anticipation.md |    2 +-
 .../tutorials/es/how-to-return-order-items.md |   14 +-
 .../how-to-see-orders-closed-with-benefits.md |    2 +-
 ...fine-a-default-sla-for-recurrent-orders.md |    4 +-
 ...set-up-recurrence-in-payment-conditions.md |    8 +-
 ...r-to-accept-payments-with-adyen-at-vtex.md |   18 +-
 ...t-up-the-device-fingerprint-for-braspag.md |    2 +-
 ...set-up-the-indeva-scheduled-appointment.md |   10 +-
 ...e-for-pick-up-field-in-smartcheckout-v6.md |    8 +-
 docs/tutorials/es/how-to-set-up-the-zoom.md   |    6 +-
 docs/tutorials/es/how-to-set-up-visa-debit.md |    6 +-
 ...w-to-set-up-your-store-on-seller-portal.md |   19 +-
 ...to-setup-google-analytics-in-vtex-store.md |    6 +-
 ...how-to-turn-my-store-website-into-a-pwa.md |   10 +-
 .../es/how-to-use-conditions-builder-app.md   |    6 +-
 .../es/how-to-use-the-index-report.md         |    8 +-
 .../es/how-to-use-the-meta-tags-control.md    |    6 +-
 .../how-to-use-the-search-result-control.md   |   10 +-
 .../es/how-to-use-the-shareable-cart-app.md   |   28 +-
 ...how-to-view-taxes-information-in-taxhub.md |    2 +-
 ...how-to-view-transactions-on-pci-gateway.md |    2 +-
 ...ith-different-layouts-for-the-same-page.md |    2 +-
 docs/tutorials/es/how-trade-policies-work.md  |    8 +-
 .../es/i-cant-import-the-price-table.md       |   67 +
 .../es/i-cant-receive-emails-from-vtex.md     |   98 ++
 ...-cant-update-the-ean-of-my-skus-via-api.md |   50 +
 ...-view-the-product-in-the-search-results.md |  240 +++
 docs/tutorials/es/image-compression.md        |   63 +
 docs/tutorials/es/image-widget.md             |   10 +-
 .../es/import-customer-data-brazil.md         |   46 +-
 ...-and-exporting-an-inventory-spreadsheet.md |    4 +-
 .../es/importing-data-into-master-data.md     |   10 +-
 .../es/importing-images-from-a-spreadsheet.md |   38 +-
 ...roving-the-seo-of-product-listing-pages.md |    4 +-
 docs/tutorials/es/indexes-in-master-data.md   |   87 ++
 docs/tutorials/es/indexing-history-beta.md    |   18 +-
 docs/tutorials/es/indexing-history.md         |   67 +
 docs/tutorials/es/indexing.md                 |   26 +
 ...information-about-chile-custom-payments.md |    6 +-
 ...ormation-about-colombia-custom-payments.md |    6 +-
 ...formation-about-uruguay-custom-payments.md |    6 +-
 ...inserting-images-into-let-me-know-email.md |    2 +-
 ...g-my-orders-through-the-extension-store.md |    6 +-
 docs/tutorials/es/integrating-with-enjoei.md  |    4 +-
 .../es/integrating-with-madeiramadeira.md     |    4 +-
 .../integrating-with-renner-and-camicado.md   |    6 +-
 ...-guide-for-marketplaces-seller-non-vtex.md |    6 +-
 docs/tutorials/es/integration-interfaces.md   |    2 +-
 .../es/integration-with-google-tag-manager.md |   10 +-
 ...lligent-search-synonym-suggestions-beta.md |   39 +-
 docs/tutorials/es/intelligent-synonyms.md     |   68 +
 ...racting-with-masterdata-through-graphql.md |   10 +-
 docs/tutorials/es/interaction-details.md      |   27 +-
 ...erpreting-the-data-of-the-oms-order-bar.md |    2 +-
 .../tutorials/es/introduction-to-vtex-apis.md |    2 +-
 .../es/inventory-data-pipeline-beta.md        |   95 ++
 docs/tutorials/es/inventory-update-history.md |   12 +-
 docs/tutorials/es/kit-registration.md         |   30 +-
 docs/tutorials/es/kr1-test.md                 |   18 +
 .../lead-time-shipping-time-at-sku-level.md   |  103 ++
 .../tutorials/es/license-manager-resources.md |   18 +-
 ...-the-store-by-means-of-the-trade-policy.md |   66 +
 ...g-urls-to-banners-using-the-site-editor.md |    4 +-
 .../list-of-payment-providers-by-country.md   |    6 +-
 docs/tutorials/es/loading-dock.md             |    2 +-
 .../es/locations-details-page-beta.md         |    6 +-
 .../tutorials/es/logistics-module-overview.md |   12 +-
 .../es/making-a-master-data-field-editable.md |   31 +
 .../es/manage-the-sales-comissions-report.md  |    2 +-
 .../es/managing-b2b-organizations.md          |  100 ++
 .../tutorials/es/managing-content-versions.md |    2 +-
 .../managing-credit-with-customer-credit.md   |    4 +-
 .../es/managing-delivery-capacity.md          |   19 +-
 docs/tutorials/es/managing-http-headers.md    |   65 +
 .../es/managing-page-and-template-content.md  |    6 +-
 docs/tutorials/es/managing-pages.md           |   38 +-
 docs/tutorials/es/managing-placeholders.md    |    6 +-
 docs/tutorials/es/managing-projects.md        |  129 ++
 .../es/managing-redirects-per-binding.md      |   16 +-
 .../es/managing-shipping-policies.md          |  114 ++
 .../es/managing-singleton-content-types.md    |   31 +-
 docs/tutorials/es/managing-stock-items.md     |   37 +-
 docs/tutorials/es/managing-url-redirects.md   |   18 +-
 .../es/managing-users-in-b2b-organizations.md |   68 +
 docs/tutorials/es/managing-users.md           |   71 +-
 ...re-categories-variations-and-attributes.md |    2 +-
 .../es/marketplace-invited-sellers.md         |    2 +-
 docs/tutorials/es/marketplace-overview.md     |    6 +-
 .../es/marketplace-strategies-at-vtex.md      |  240 +--
 .../es/marketplaces-and-integrations.md       |    6 +-
 docs/tutorials/es/master-data.md              |  313 ++--
 .../es/match-offers-mercado-livre.md          |  131 ++
 docs/tutorials/es/media-overview.md           |  103 +-
 docs/tutorials/es/mercado-libre-promotions.md |    2 +-
 docs/tutorials/es/mercado-libre-size-chart.md |  132 ++
 ...ercado-livre-automobilist-compatibility.md |    4 +-
 docs/tutorials/es/mercado-livre-faq.md        |   10 +-
 .../es/merchandising-rule-conditions.md       |   66 +
 docs/tutorials/es/merchandising-rules-list.md |   70 +
 ...re-not-displayed-in-the-order-dashboard.md |   43 +
 .../minimum-stock-control-for-integrations.md |    2 +-
 docs/tutorials/es/mode-off-faq.md             |   11 +-
 ...moving-order-to-start-handling-shipping.md |    8 +-
 .../es/multilevel-omnichannel-inventory.md    |  112 +-
 ...my-ad-is-not-displayed-on-mercado-livre.md |   60 +
 docs/tutorials/es/my-inventory-is-negative.md |   34 +
 .../my-orders-in-mercado-libre-have-errors.md |   61 +
 .../es/my-store-order-was-not-created.md      |   64 +
 docs/tutorials/es/navigation.md               |  210 +++
 .../new-integration-with-erede-erederest.md   |   10 +-
 ...n-vtex-cmc-newsletteroptin-greater-than.md |    6 +-
 docs/tutorials/es/offer-details.md            |   25 +-
 ...moderation-and-quality-of-mercado-libre.md |    4 +-
 docs/tutorials/es/offer-management.md         |   19 +-
 docs/tutorials/es/offer-quality-filters.md    |   12 +-
 docs/tutorials/es/offer-status.md             |  247 +++
 ...-the-same-vtex-sellers-and-marketplaces.md |    2 +-
 docs/tutorials/es/oms-page-structure.md       |   16 +-
 ...pening-tickets-to-vtex-support-finacial.md |   15 +-
 .../es/opening-tickets-to-vtex-support.md     |    8 +-
 .../tutorials/es/operational-capacity-beta.md |  198 +++
 ...ization-of-shipping-options-at-checkout.md |    2 +-
 .../es/order-allocation-algorithm-beta.md     |    6 +-
 ...-cancellation-requested-by-the-customer.md |    8 +-
 docs/tutorials/es/order-details-page.md       |   35 +-
 ...errors-in-the-mercado-livre-integration.md |    4 +-
 docs/tutorials/es/order-flow-and-status.md    |   18 +-
 docs/tutorials/es/order-replacement.md        |    6 +-
 docs/tutorials/es/order-report.md             |    8 +-
 .../es/order-split-and-delivery-split.md      |    6 +-
 .../es/order-transactional-email-templates.md |   30 +-
 docs/tutorials/es/orderform-settings.md       |   40 +
 ...-window-display-and-on-the-product-page.md |    2 +-
 docs/tutorials/es/orders-list.md              |    6 +-
 docs/tutorials/es/orders-overview.md          |   15 +-
 docs/tutorials/es/orders.md                   |  380 +++++
 .../es/overview-of-b2b-orders-history.md      |   31 +
 docs/tutorials/es/overview-pricing-module.md  |    8 +-
 docs/tutorials/es/pages-overview.md           |    2 +-
 .../tutorials/es/payment-provider-protocol.md |  157 +-
 docs/tutorials/es/payments.md                 |   99 ++
 .../es/payu-romania-refund-details.md         |    2 +-
 docs/tutorials/es/pci-gateway-overview.md     |    2 +-
 ...ration-testing-and-vulnerability-notice.md |  163 +-
 .../es/permissions-management-in-b2b-suite.md |   66 +
 .../es/physical-store-instore-beta.md         |    4 +-
 .../pickup-points-for-subscription-orders.md  |   54 +
 docs/tutorials/es/pickup-points.md            |   10 +-
 docs/tutorials/es/plan-your-project.md        |    6 +-
 .../es/planner-calendar-page-beta.md          |    6 +-
 .../es/planner-releases-page-beta.md          |    2 +-
 docs/tutorials/es/predefined-roles.md         | 1341 +++--------------
 ...ier-from-meeting-certain-zip-code-range.md |    8 +-
 docs/tutorials/es/price-divergence-rule.md    |    6 +-
 .../es/price-divergence-rules-beta.md         |    2 +-
 ...e-table-management-in-b2b-organizations.md |   47 +
 docs/tutorials/es/price-waterfall.md          |    2 +-
 .../tutorials/es/prices-data-pipeline-beta.md |   92 ++
 docs/tutorials/es/prices-settings.md          |    6 +-
 docs/tutorials/es/prices.md                   |    6 +-
 docs/tutorials/es/product-list.md             |    8 +-
 docs/tutorials/es/products-and-skus-beta.md   |   22 +-
 docs/tutorials/es/promotion-alerts-beta.md    |    2 +-
 docs/tutorials/es/promotion-list-beta.md      |   10 +-
 docs/tutorials/es/promotion-summary.md        |    6 +-
 docs/tutorials/es/promotions-beta.md          |    8 +-
 docs/tutorials/es/promotions-overview.md      |    6 +-
 .../tutorials/es/promotions-simulator-beta.md |  114 +-
 docs/tutorials/es/promotions-simulator.md     |    6 +-
 docs/tutorials/es/promotions.md               |  112 ++
 .../protection-against-transaction-attacks.md |   14 +-
 docs/tutorials/es/ready-to-dispatch.md        |    4 +-
 docs/tutorials/es/received-skus-beta.md       |  222 +++
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |  117 ++
 .../es/redirect-from-other-addresses.md       |   81 +
 docs/tutorials/es/redirects.md                |   42 +
 docs/tutorials/es/registering-a-category.md   |    6 +-
 docs/tutorials/es/registering-brands.md       |    2 +-
 .../es/registering-gateway-affiliations.md    |   84 +-
 docs/tutorials/es/registering-geolocation.md  |    8 +-
 ...ing-the-skus-barcode-for-vtex-sales-app.md |    4 +-
 ...-with-nominal-discount-based-on-formula.md |    8 +-
 .../es/regular-promotion-with-reward-value.md |   16 +-
 docs/tutorials/es/regular-promotion.md        |   14 +-
 docs/tutorials/es/releases-module-beta.md     |    4 +-
 .../es/releasing-the-store-for-production.md  |    2 +-
 docs/tutorials/es/relevance-rules.md          |  114 ++
 ...request-headers-must-only-contain-ascii.md |   91 ++
 .../es/requesting-a-new-organization.md       |  104 ++
 .../requesting-an-additional-trade-policy.md  |   15 +-
 ...factor-authentication-app-configuration.md |   31 +-
 .../responsibilities-in-the-vtex-ecosystem.md |  202 +++
 .../es/responsive-vs-mobile-version.md        |    2 +-
 ...ict-public-access-to-master-data-fields.md |   57 +
 docs/tutorials/es/risk-assessment.md          |  382 +++++
 docs/tutorials/es/roles.md                    |  105 +-
 docs/tutorials/es/rounding-rules.md           |    8 +-
 .../es/sales-app-sales-performance.md         |    4 +-
 .../sales-associate-code-field-at-checkout.md |   96 ++
 .../es/sales-associates-instore-beta.md       |    4 +-
 docs/tutorials/es/sales-performance.md        |   10 +-
 docs/tutorials/es/scheduled-delivery.md       |    9 +-
 .../scheduling-features-for-special-events.md |    2 +-
 docs/tutorials/es/search-behavior.md          |  134 ++
 docs/tutorials/es/search-configuration.md     |   52 +
 docs/tutorials/es/search-navigator-control.md |    4 +-
 docs/tutorials/es/searching-for-old-orders.md |    2 +-
 .../searching-for-transactions-on-payments.md |    4 +-
 docs/tutorials/es/security-certificate-ssl.md |   26 +
 .../es/security-education-and-awareness.md    |    4 +-
 docs/tutorials/es/security-monitor.md         |  131 ++
 ...ng-stock-for-orders-mercado-envios-full.md |    4 +-
 docs/tutorials/es/seller-management.md        |    4 +-
 docs/tutorials/es/seller-monitoring.md        |   60 +
 .../es/seller-portal-creating-a-promotion.md  |  102 ++
 ...tal-getting-started-for-the-marketplace.md |    2 +-
 .../es/seller-portal-product-details.md       |    2 +-
 docs/tutorials/es/seller-portal-promotions.md |   96 ++
 .../es/seller-portal-shared-products.md       |   11 +-
 ...nd-item-price-with-tax-shown-separately.md |   22 +-
 .../es/sending-sku-attributes-to-amazon.md    |    4 +-
 docs/tutorials/es/sent-offers-beta.md         |    2 +-
 .../es/sent-offers-buybox-opportunities.md    |   53 +-
 docs/tutorials/es/set-up-mundi-gateway.md     |   10 +-
 ...r-authentication-for-recurring-payments.md |    2 +-
 ...ct-suggestions-accessories-and-generics.md |    8 +-
 .../es/setting-up-abandoned-carts.md          |   22 +-
 ...app-linking-for-payments-app-in-instore.md |    2 +-
 .../setting-up-bradesco-registered-ticket.md  |    2 +-
 .../es/setting-up-braspag-gateway.md          |    6 +-
 .../es/setting-up-conductor-gateway.md        |   15 +-
 .../es/setting-up-cybersource-antifraud.md    |   32 +-
 .../es/setting-up-cybersource-gateway.md      |  226 ++-
 .../es/setting-up-firstdata-acquirer.md       |   83 +-
 ...-getnet-acquirer-with-egetnet-connector.md |   30 +-
 ...ent-search-integration-with-the-catalog.md |   30 +
 ...-itau-registered-ticket-itau-registrado.md |   42 +-
 .../es/setting-up-itau-registered-ticket.md   |    4 +-
 ...eto-in-installments-as-a-payment-method.md |    6 +-
 .../setting-up-mercadopagov1-sub-acquirer.md  |   18 +-
 .../setting-up-mercadopagov2-sub-acquirer.md  |   68 +-
 .../es/setting-up-merchant-id-in-apple-pay.md |   40 +-
 ...g-up-mundipagg-fraud-prevention-gateway.md |   15 +-
 .../es/setting-up-mundipagg-gateway.md        |   15 +-
 docs/tutorials/es/setting-up-my-account.md    |    8 +-
 .../es/setting-up-nexxpago-gateway.md         |   24 +-
 docs/tutorials/es/setting-up-nps-gateway.md   |    8 +-
 .../es/setting-up-pagar-me-gateway.md         |   11 +-
 .../es/setting-up-pagarmev2-gateway.md        |   21 +-
 .../es/setting-up-pagbrasil-gateway.md        |   15 +-
 .../es/setting-up-paghiper-gateway.md         |   15 +-
 docs/tutorials/es/setting-up-pagseguro-v3.md  |   40 +-
 .../es/setting-up-payment-with-paypal.md      |    8 +-
 .../es/setting-up-paymentez-gateway.md        |   24 +-
 .../es/setting-up-payments-with-55pay.md      |    4 +-
 .../es/setting-up-payments-with-99pay.md      |   14 +-
 .../es/setting-up-payments-with-aarin.md      |    4 +-
 .../es/setting-up-payments-with-addi.md       |   14 +-
 .../es/setting-up-payments-with-alignet.md    |   24 +-
 .../es/setting-up-payments-with-alignetv2.md  |   39 +
 .../setting-up-payments-with-ame-digital.md   |   14 +-
 .../es/setting-up-payments-with-apple-pay.md  |   42 +-
 .../es/setting-up-payments-with-appmax.md     |   33 +
 .../es/setting-up-payments-with-argonpay.md   |   50 +
 .../es/setting-up-payments-with-astropay.md   |    8 +-
 .../es/setting-up-payments-with-bamboo.md     |    8 +-
 ...tting-up-payments-with-bancolombia-bnpl.md |   14 +-
 .../es/setting-up-payments-with-banqi.md      |   15 +-
 .../es/setting-up-payments-with-bitfy.md      |   14 +-
 .../es/setting-up-payments-with-bluepay.md    |   16 +-
 .../es/setting-up-payments-with-boletoflex.md |   11 +-
 ...etting-up-payments-with-bom-pra-credito.md |    4 +-
 .../es/setting-up-payments-with-braintree.md  |   49 +
 .../es/setting-up-payments-with-braspagv2.md  |    6 +-
 ...-up-payments-with-brinks-cash-ecommerce.md |   14 +-
 ...setting-up-payments-with-cieloecommerce.md |   67 +
 .../es/setting-up-payments-with-cielov4.md    |    6 +-
 .../es/setting-up-payments-with-conekta.md    |   18 +-
 .../es/setting-up-payments-with-crecoscorp.md |    8 +-
 .../setting-up-payments-with-credimarcas.md   |   60 +
 .../es/setting-up-payments-with-credit-key.md |   12 +-
 .../es/setting-up-payments-with-culqi.md      |   58 +
 .../es/setting-up-payments-with-dapp.md       |   39 +
 .../es/setting-up-payments-with-deuna.md      |   48 +
 ...tting-up-payments-with-digital-river-v2.md |   14 +-
 ...etting-up-payments-with-dlocal-payments.md |   14 +-
 .../es/setting-up-payments-with-dock.md       |    4 +-
 .../es/setting-up-payments-with-e-sitef.md    |   48 +
 ...ng-up-payments-with-easypay-marketplace.md |   18 +
 ...setting-up-payments-with-easypay-seller.md |   51 +
 .../es/setting-up-payments-with-easypay.md    |  210 +++
 .../setting-up-payments-with-ebanx-local.md   |   14 +-
 .../es/setting-up-payments-with-ebanx.md      |   16 +-
 .../es/setting-up-payments-with-egetnetv2.md  |   26 +-
 .../es/setting-up-payments-with-etpay.md      |   14 +-
 .../setting-up-payments-with-evopayments.md   |   46 +
 ...payments-with-fcamara-payment-initiator.md |   15 +-
 .../es/setting-up-payments-with-fintoc.md     |   38 +
 .../es/setting-up-payments-with-flywire.md    |   14 +-
 .../es/setting-up-payments-with-fpay.md       |   14 +-
 .../es/setting-up-payments-with-geru.md       |   40 +
 .../es/setting-up-payments-with-gocuotas.md   |   39 +
 .../es/setting-up-payments-with-guatapay.md   |   38 +
 .../es/setting-up-payments-with-inswitch.md   |   49 +
 .../es/setting-up-payments-with-itau-rede.md  |   91 ++
 .../es/setting-up-payments-with-iugu.md       |   73 +-
 .../es/setting-up-payments-with-k8bank.md     |   44 +
 .../es/setting-up-payments-with-kaiowa.md     |   14 +-
 .../es/setting-up-payments-with-khipu.md      |   14 +-
 .../setting-up-payments-with-koin-payments.md |   20 +-
 .../es/setting-up-payments-with-koin.md       |    8 +-
 .../es/setting-up-payments-with-kueski-pay.md |   10 +-
 ...etting-up-payments-with-liquido-payment.md |   32 +
 .../es/setting-up-payments-with-mach.md       |   14 +-
 .../es/setting-up-payments-with-meliuz.md     |    4 +-
 .../setting-up-payments-with-mercado-pago.md  |   13 +-
 .../es/setting-up-payments-with-mobbex.md     |   34 +
 .../setting-up-payments-with-msc-payment.md   |   51 +
 ...ayments-with-netpay-and-netpay-checkout.md |   22 +-
 .../setting-up-payments-with-notes-payable.md |   58 +
 .../es/setting-up-payments-with-nupay.md      |    4 +-
 .../es/setting-up-payments-with-nuvei.md      |   72 +
 .../es/setting-up-payments-with-pagaleve.md   |    4 +-
 .../es/setting-up-payments-with-pagarmev3.md  |   26 +-
 .../setting-up-payments-with-pagbrasilv2.md   |   40 +
 .../es/setting-up-payments-with-paghiperv2.md |   36 +
 .../es/setting-up-payments-with-paghiperv3.md |   38 +
 .../setting-up-payments-with-pagoefectivo.md  |    8 +-
 ...setting-up-payments-with-pagoefectivov2.md |   55 +
 .../setting-up-payments-with-pagoexpress.md   |   40 +
 .../es/setting-up-payments-with-pagosweb.md   |    8 +-
 .../es/setting-up-payments-with-parcelex.md   |    4 +-
 .../es/setting-up-payments-with-pay4fun.md    |   40 +
 .../es/setting-up-payments-with-paycash.md    |   14 +-
 .../es/setting-up-payments-with-payclub.md    |    8 +-
 .../setting-up-payments-with-paymentezv2.md   |   34 +
 .../es/setting-up-payments-with-paypalv2.md   |   43 +
 .../es/setting-up-payments-with-payu-india.md |   18 +-
 .../es/setting-up-payments-with-payuv2.md     |   48 +
 .../es/setting-up-payments-with-payway.md     |   37 +
 .../es/setting-up-payments-with-picpay.md     |   16 +-
 .../es/setting-up-payments-with-pine-labs.md  |   14 +-
 .../es/setting-up-payments-with-poolpay.md    |   33 +
 .../es/setting-up-payments-with-powerpay.md   |   50 +
 ...etting-up-payments-with-puntos-colombia.md |   14 +-
 .../es/setting-up-payments-with-qhantuy.md    |   14 +-
 .../es/setting-up-payments-with-retrypay.md   |   16 +-
 .../setting-up-payments-with-safetypayv2.md   |   33 +
 .../es/setting-up-payments-with-scalapay.md   |   16 +-
 .../es/setting-up-payments-with-shipay.md     |   14 +-
 .../es/setting-up-payments-with-sibs.md       |   14 +-
 .../es/setting-up-payments-with-stark-bank.md |   34 +
 .../es/setting-up-payments-with-stelo.md      |    8 +-
 .../es/setting-up-payments-with-stelom1v2.md  |   33 +
 ...g-up-payments-with-store-card-cobranded.md |   21 +-
 ...payments-with-transfero-crypto-checkout.md |   49 +
 .../setting-up-payments-with-tyendacrypto.md  |   14 +-
 .../es/setting-up-payments-with-unlimit.md    |   43 +
 .../es/setting-up-payments-with-ventipay.md   |   12 +-
 .../es/setting-up-payments-with-virtuspay.md  |    6 +-
 .../setting-up-payments-with-virtuspayv2.md   |   15 +-
 ...setting-up-payments-with-webpayoneclick.md |   39 +
 .../es/setting-up-payments-with-wepay4u.md    |   52 +
 .../es/setting-up-payments-with-wompi.md      |   10 +-
 .../es/setting-up-payments-with-wompicov2.md  |    8 +-
 .../es/setting-up-payments-with-woovi.md      |   39 +
 .../es/setting-up-payments-with-yuno.md       |   14 +-
 .../es/setting-up-payments-with-zenki.md      |   15 +-
 .../es/setting-up-payments-with-zoop.md       |   24 +-
 docs/tutorials/es/setting-up-paypal-plus.md   |   64 +-
 docs/tutorials/es/setting-up-payu-gateway.md  |   15 +-
 .../tutorials/es/setting-up-payzen-gateway.md |    8 +-
 ...ng-up-personal-data-on-the-users-screen.md |   12 +-
 .../es/setting-up-place2pay-gateway.md        |    8 +-
 ...ting-up-price-tables-for-specific-users.md |    2 +-
 ...setting-up-rede-acquirer-with-erederest.md |    8 +-
 ...up-seller-white-label-as-a-pickup-point.md |   11 +-
 docs/tutorials/es/setting-up-shipment.md      |    2 +-
 .../setting-up-sitef-gateway-with-pre-auth.md |    8 +-
 docs/tutorials/es/setting-up-sitef-gateway.md |   18 +-
 .../es/setting-up-sms-password-recovery.md    |   12 +-
 .../es/setting-up-sub-acquirer-stelo.md       |    8 +-
 .../es/setting-up-the-critical-stock-alert.md |    2 +-
 .../setting-up-the-notes-payable-conector.md  |   31 +
 .../es/setting-up-the-notify-me-option.md     |    2 +-
 .../es/setting-up-the-paymee-gateway.md       |   33 +-
 .../es/setting-up-the-price-range-filter.md   |    2 +-
 ...up-the-sales-funnel-on-google-analytics.md |   10 +-
 .../es/setting-up-the-tnspay-gateway.md       |    8 +-
 .../es/setting-up-the-voucher-list.md         |    4 +-
 .../es/setting-up-the-worldpay-acquirer.md    |   41 +-
 .../setting-up-the-yamisplitmoipv1-gateway.md |   26 +-
 .../tutorials/es/setting-up-vcmais-gateway.md |    4 +-
 docs/tutorials/es/setting-up-vindi-gateway.md |   30 +-
 .../es/setting-up-webpay2p-gateway.md         |   14 +-
 docs/tutorials/es/setup-safetypay.md          |   18 +-
 ...ween-a-marketplace-and-a-seller-on-vtex.md |   12 +-
 docs/tutorials/es/shipping-options-beta.md    |   10 +-
 docs/tutorials/es/shipping-policy.md          |   89 +-
 docs/tutorials/es/shipping-rate-template.md   |   14 +-
 docs/tutorials/es/shipping-rates.md           |    2 +-
 docs/tutorials/es/shipping-simulation.md      |    8 +-
 docs/tutorials/es/shipping-strategy.md        |   28 +-
 docs/tutorials/es/shopee-integration.md       |    4 +-
 docs/tutorials/es/site-editor-overview.md     |    2 +-
 docs/tutorials/es/sku-bindings.md             |    8 +-
 docs/tutorials/es/sku-price-change.md         |   41 +-
 docs/tutorials/es/sku-registration-fields.md  |    6 +-
 docs/tutorials/es/skus.md                     |  130 ++
 ...martcheckout-v5-general-characteristics.md |   69 +
 docs/tutorials/es/special-conditions.md       |   18 +-
 docs/tutorials/es/split-payment.md            |   87 +-
 docs/tutorials/es/store-access-permission.md  |    2 +-
 docs/tutorials/es/store-overview-beta.md      |  161 ++
 docs/tutorials/es/store-overview.md           |   18 +-
 docs/tutorials/es/store-profile.md            |   88 ++
 docs/tutorials/es/store-settings-overview.md  |    8 +-
 docs/tutorials/es/storefront-overview.md      |    2 +-
 docs/tutorials/es/styles-overview.md          |    2 +-
 docs/tutorials/es/subscription-plans.md       |    2 +-
 docs/tutorials/es/synonym-list.md             |  112 ++
 docs/tutorials/es/table-of-base-prices.md     |    2 +-
 docs/tutorials/es/telesales-features.md       |    6 +-
 docs/tutorials/es/telesales-toolbar.md        |    9 +-
 docs/tutorials/es/test-kr1.md                 |   18 +
 ...-into-packages-with-separate-deliveries.md |   46 +
 ...sult-is-different-from-the-product-page.md |    6 +-
 ...help-the-performance-of-your-e-commerce.md |    6 +-
 docs/tutorials/es/total-shipping-cost.md      |    2 +-
 .../es/tracking-your-sales-analytics.md       |   16 +-
 ...actional-emails-for-subscription-orders.md |   10 +-
 docs/tutorials/es/transactions-events.md      |    2 +-
 .../es/transferring-store-ownership.md        |    4 +-
 ...eshooting-errors-in-subscription-orders.md |   12 +-
 docs/tutorials/es/understanding-b2b-orders.md |    2 +-
 .../es/understanding-how-indexation-works.md  |   13 +-
 .../es/understanding-how-the-cache-works.md   |    6 +-
 ...standing-storebuilder-and-stylesbuilder.md |   18 +-
 ...erstanding-the-additional-shipping-cost.md |    6 +-
 .../understanding-the-cubic-weight-factor.md  |   46 +-
 .../es/understanding-the-message-center.md    |    2 +-
 .../es/understanding-the-price-change-rule.md |    2 +-
 .../es/understanding-the-security-report.md   |    2 +-
 docs/tutorials/es/understanding-the-topbar.md |    8 +-
 .../understanding-the-updating-of-the-xml.md  |    4 +-
 ...nderstanding-vtexs-email-capture-system.md |    8 +-
 .../untitled-entry-2024-03-13-at-16-25-15.md  |   18 +
 .../untitled-entry-2024-07-25-at-21-25-31.md  |   18 +
 ...ting-the-quantity-of-items-in-inventory.md |    2 +-
 .../es/using-recaptcha-at-checkout.md         |   49 +-
 ...-track-browsing-sessions-in-vtex-stores.md |    2 +-
 .../es/using-the-project-task-timeline.md     |    6 +-
 ...r-store-and-uploading-it-for-production.md |    6 +-
 .../es/via-inventory-integration-errors.md    |    4 +-
 .../visao-geral-configuracoes-de-usuario.md   |    2 +-
 docs/tutorials/es/vtex-ad-network-beta.md     |  124 ++
 docs/tutorials/es/vtex-admin-start-here.md    |   59 +-
 docs/tutorials/es/vtex-admin-start-here1.md   |   10 +-
 docs/tutorials/es/vtex-agreement.md           |   35 +
 ...vtex-dashboard-guide-for-black-week-faq.md |  200 +++
 docs/tutorials/es/vtex-do-interface.md        |   10 +-
 docs/tutorials/es/vtex-insurance.md           |  110 +-
 ...gent-search-multilanguage-settings-beta.md |   18 +-
 docs/tutorials/es/vtex-invoice-notifier.md    |    4 +-
 ...x-operation-service-level-agreement-sla.md |   26 +
 .../es/vtex-pick-and-pack-fulfillment.md      |  745 ++++-----
 .../es/vtex-pick-and-pack-insights.md         |   66 +
 .../es/vtex-pick-and-pack-last-mile.md        |    9 +-
 .../tutorials/es/vtex-pick-and-pack-mobile.md |  224 +++
 .../tutorials/es/vtex-pick-and-pack-orders.md |   95 ++
 .../es/vtex-pick-and-pack-settings.md         |  269 ++++
 .../es/vtex-pick-and-pack-worksheets.md       |   79 +
 docs/tutorials/es/vtex-pick-and-pack.md       |    8 +-
 docs/tutorials/es/vtex-shield.md              |   63 +
 ...ex-shipping-network-correios-activation.md |   20 +
 .../es/vtex-shipping-network-correios-faq.md  |    4 +-
 .../es/vtex-shipping-network-dashboard.md     |   17 +-
 docs/tutorials/es/vtex-status-page.md         |  169 +++
 docs/tutorials/es/vtex-support-apac.md        |   18 +
 docs/tutorials/es/warehouse.md                |    2 +-
 .../es/web-application-firewall-waf.md        |   58 +
 docs/tutorials/es/web-page-performance.md     |    4 +-
 ...urce-and-orders-with-fulfillment-source.md |    2 +-
 docs/tutorials/es/what-are-templates.md       |    2 +-
 ...payments-are-available-in-latin-america.md |    6 +-
 ...tivate-a-gift-multiplier-on-a-promotion.md |    2 +-
 ...r-as-revenue-in-the-billing-calculation.md |    2 +-
 .../es/what-is-a-franchise-account.md         |   15 +-
 docs/tutorials/es/what-is-a-service.md        |    6 +-
 docs/tutorials/es/what-is-a-transaction.md    |   10 +-
 docs/tutorials/es/what-is-an-affiliate.md     |    4 +-
 docs/tutorials/es/what-is-an-e-wallet.md      |    8 +-
 docs/tutorials/es/what-is-deposit-slip.md     |   14 +-
 ...rand-gateway-and-sub-acquirer-in-brazil.md |   28 +-
 ...ce-between-inventory-and-warehouse-dock.md |    2 +-
 ...-the-difference-between-product-and-sku.md |    8 +-
 ...what-is-the-maximum-limit-of-promotions.md |   10 +-
 docs/tutorials/es/what-is-the-pci-ssc.md      |    6 +-
 ...s-the-purpose-of-the-customized-control.md |    2 +-
 .../es/what-is-transparent-checkout.md        |    6 +-
 ...nditions-are-available-in-latin-america.md |    6 +-
 ...-when-my-report-does-not-reach-my-inbox.md |   15 +-
 ...app-ai-campaigns-management-and-details.md |   96 ++
 ...re-do-i-see-clients-that-use-recurrence.md |    2 +-
 ...y-certificates-may-be-added-to-my-store.md |    6 +-
 docs/tutorials/es/white-label-seller.md       |    5 +-
 .../es/white-label-sellers-selection.md       |   10 +-
 ...ketplace-orders-integrate-with-my-store.md |   44 +
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |    8 +-
 ...ing-an-effective-ticket-to-vtex-support.md |   64 +-
 .../pt/ab-testing-how-where-when-and-why.md   |   75 +-
 docs/tutorials/pt/access-control.md           |   62 +
 .../pt/accessing-a-client-abandoned-cart.md   |   12 +-
 .../pt/accessing-the-beta-environment.md      |   46 +-
 docs/tutorials/pt/account-management.md       |   76 +-
 .../tutorials/pt/account-settings-overview.md |    2 +-
 docs/tutorials/pt/account-summary.md          |   14 +-
 docs/tutorials/pt/accounts-payable-brazil.md  |    4 +-
 docs/tutorials/pt/activating-new-vtex-cdn.md  |    6 +-
 ...complete-list-link-on-the-category-menu.md |    4 +-
 .../pt/active-campaign-suiteshare.md          |   10 +-
 ...-your-integration-for-change-order-beta.md |  304 ++++
 ...s-support-to-the-integration-with-adyen.md |    8 +-
 ...-a-url-mapping-through-worksheet-import.md |    2 +-
 ...a-client-secret-to-log-in-with-facebook.md |  126 +-
 ...d-a-client-secret-to-log-in-with-google.md |   24 +-
 .../adding-a-record-on-a-master-data-form.md  |   48 +
 docs/tutorials/pt/adding-an-attachment.md     |    6 +-
 docs/tutorials/pt/adding-bin-information.md   |   43 +
 docs/tutorials/pt/adding-collections-cms.md   |   20 +-
 .../pt/adding-sku-specifications-or-fields.md |   18 +-
 ...adding-specifications-or-product-fields.md |   10 +-
 .../tutorials/pt/additional-shipping-costs.md |    2 +-
 ...dmin-redirect-search-returns-no-results.md |  111 ++
 docs/tutorials/pt/admin-v4-getting-started.md |   10 +-
 docs/tutorials/pt/ads-from-vtex-sales-app.md  |   51 +-
 .../advertising-with-vtex-ad-network-beta.md  |  165 ++
 docs/tutorials/pt/affiliates-program-app.md   |   10 +-
 docs/tutorials/pt/all-orders.md               |   19 +-
 docs/tutorials/pt/amaro-integration.md        |  107 ++
 ...mazon-multi-channel-fulfillment-mcf-app.md |    2 +-
 docs/tutorials/pt/amazon-offer-matching.md    |   36 +-
 docs/tutorials/pt/analytics.md                |   87 ++
 docs/tutorials/pt/analyze-suiteshare.md       |   18 +-
 docs/tutorials/pt/anapro-suiteshare.md        |   10 +-
 docs/tutorials/pt/antifraud-provider.md       |   14 +-
 docs/tutorials/pt/application-keys.md         |  153 +-
 ...roving-payment-of-the-bank-payment-slip.md |    8 +-
 docs/tutorials/pt/apps-overview.md            |    2 +-
 docs/tutorials/pt/assembly-options-app.md     |    2 +-
 .../pt/assembly-options-in-vtex-sales-app.md  |   62 +
 docs/tutorials/pt/assembly-options.md         |    8 +-
 .../pt/associate-a-sku-to-a-trade-policy.md   |   10 +-
 .../associating-a-template-with-a-layout.md   |    2 +-
 docs/tutorials/pt/audit.md                    |  136 ++
 docs/tutorials/pt/authentication.md           |   87 ++
 docs/tutorials/pt/autocomplete.md             |   74 +
 docs/tutorials/pt/availability.md             |   32 +
 docs/tutorials/pt/b2b-checkout-settings.md    |   71 +
 .../pt/b2b-cost-center-management.md          |  101 ++
 .../pt/b2b-organization-general-settings.md   |   33 +
 docs/tutorials/pt/b2b-overview.md             |    6 +-
 docs/tutorials/pt/b2b-store-settings.md       |   43 +
 docs/tutorials/pt/b2b-suite-overview.md       |   89 ++
 .../pt/b2b-trade-policies-overview.md         |   32 +
 docs/tutorials/pt/bank-reconciliations.md     |    6 +-
 docs/tutorials/pt/banners.md                  |   69 +
 .../best-practices-against-virtual-attacks.md |   39 +-
 .../pt/best-practices-application-keys.md     |    5 +-
 ...ces-for-accessing-the-store-without-www.md |   73 +
 ...ices-for-the-success-of-your-vtex-store.md |  171 +++
 ...actices-for-using-images-in-the-catalog.md |    8 +-
 docs/tutorials/pt/best-practices-on-spf.md    |   13 +-
 ...ces-to-avoid-scams-using-the-vtex-brand.md |   54 +
 docs/tutorials/pt/beta-price-configuration.md |    6 +-
 docs/tutorials/pt/billing-module-overview.md  |    2 +-
 docs/tutorials/pt/bitrix24.md                 |   16 +-
 docs/tutorials/pt/black-week.md               |    8 +-
 docs/tutorials/pt/brands.md                   |    2 +-
 ...inging-app-content-into-the-admin-panel.md |    8 +-
 docs/tutorials/pt/buy-one-get-one.md          |  133 +-
 .../tutorials/pt/call-to-action-suiteshare.md |   26 +-
 ...e-articulos-del-mismo-sku-en-el-carrito.md |    2 +-
 docs/tutorials/pt/campaign-audiences-list.md  |    4 +-
 docs/tutorials/pt/campaign-audiences.md       |    2 +-
 docs/tutorials/pt/campaign-promotion.md       |    4 +-
 docs/tutorials/pt/canceling-orders.md         |   19 +-
 docs/tutorials/pt/capture-form-suiteshare.md  |   22 +-
 .../carrefour-inventory-integration-errors.md |    8 +-
 docs/tutorials/pt/carrier-working-hours.md    |   49 +-
 ...rking-hours-and-scheduled-delivery-beta.md |    6 +-
 docs/tutorials/pt/carries-on-vtex.md          |    4 +-
 docs/tutorials/pt/catalog-overview-2.md       |    8 +-
 docs/tutorials/pt/catalog-overview.md         |   50 +-
 docs/tutorials/pt/categories.md               |    2 +-
 .../pt/category-registration-fields.md        |   10 +-
 .../pt/change-a-placeholder-title.md          |    6 +-
 ...-seller-of-an-vtex-sales-app-order-beta.md |    8 +-
 docs/tutorials/pt/change-seller.md            |    4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |    2 +-
 ...ult-system-texts-displayed-in-the-store.md |    4 +-
 .../changing-items-from-a-complete-order.md   |    5 +-
 .../changing-the-total-cost-of-the-order.md   |    4 +-
 docs/tutorials/pt/changing-tracking-data.md   |    2 +-
 docs/tutorials/pt/chat.md                     |   20 +-
 .../pt/check-order-delivery-details.md        |    2 +-
 ...-order-delivery-deadline-was-calculated.md |   12 +-
 docs/tutorials/pt/checkout-vtex-overview.md   |    2 +-
 ...chitecture-or-an-additional-environment.md |   40 +-
 ...ount-franchise-account-or-seller-portal.md |    8 +-
 docs/tutorials/pt/cms-overview.md             |    8 +-
 docs/tutorials/pt/cms-store-overview.md       |    2 +-
 .../pt/collection-highlight-control.md        |    6 +-
 ...ipacao-dos-recebiveis-pelo-vtex-payment.md |    2 +-
 .../pt/conditions-builder-usage-examples.md   |   14 +-
 docs/tutorials/pt/conecta-la-integration.md   |    6 +-
 docs/tutorials/pt/configuracao-de-precos.md   |    6 +-
 docs/tutorials/pt/configurar-o-cartman.md     |    6 +-
 docs/tutorials/pt/configure-cartman.md        |   23 +-
 ...e-direct-consumer-credit-cdc-by-losango.md |   27 +-
 ...yee-benefits-using-master-data-clusters.md |    4 +-
 .../configure-payment-with-pix-at-nubank.md   |   12 +-
 .../pt/configure-payment-with-shopfacil.md    |   41 +
 .../pt/configure-seller-regionalization.md    |    6 +-
 ...figure-template-in-smartcheckout-update.md |   30 +-
 ...configure-template-in-the-smartcheckout.md |   26 +-
 ...g-a-discount-for-orders-prepaid-in-full.md |    2 +-
 .../configuring-a-marketplace-trade-policy.md |   29 +-
 ...uring-a-pricing-rule-for-a-sales-policy.md |    6 +-
 .../pt/configuring-a-registered-boleto.md     |   21 +-
 ...nfiguring-a-santander-registered-boleto.md |   23 +-
 docs/tutorials/pt/configuring-affiliates.md   |    8 +-
 docs/tutorials/pt/configuring-banners.md      |   70 +
 ...port-for-organizations-and-cost-centers.md |   68 +
 .../pt/configuring-cargo-splitting.md         |    8 +-
 .../pt/configuring-cielo-acquirer.md          |    6 +-
 .../pt/configuring-clearsale-v3-antifraud.md  |   44 +-
 ...ders-prepaid-in-full-on-google-shopping.md |   11 +-
 ...nctions-in-the-message-center-templates.md |    2 +-
 .../pt/configuring-kushki-gateway.md          |   28 +-
 ...figuring-login-with-facebook-and-google.md |   44 +-
 ...automatic-payment-settlement-time-frame.md |    2 +-
 ...ring-my-account-conversational-commerce.md |    8 +-
 .../pt/configuring-openpay-payment-gateway.md |   29 +-
 .../configuring-payment-conditions-for-b2b.md |   43 +
 ...-payment-with-adyenv3-in-vtex-sales-app.md |   51 +-
 .../pt/configuring-payment-with-adyenv3.md    |   76 +-
 ...ng-physical-stores-integration-with-b2w.md |    8 +-
 .../pt/configuring-price-divergence-rule.md   |   27 +-
 .../pt/configuring-product-visited.md         |   14 +-
 ...configuring-promotions-for-marketplaces.md |   57 +-
 ...iguring-promotions-with-a-highlightflag.md |   10 +-
 ...uring-pwa-in-your-store-framework-store.md |   73 +
 docs/tutorials/pt/configuring-redirects.md    |   81 +
 ...iguring-samsung-pay-as-a-payment-method.md |   36 +-
 ...guring-seller-allocation-for-buying-xky.md |   52 +
 .../pt/configuring-seo-in-your-store.md       |   62 +
 .../pt/configuring-shipping-promotions.md     |   14 +-
 .../configuring-sign-in-with-apple-id-beta.md |   88 ++
 .../configuring-stripe-gateway-affiliation.md |   87 +-
 .../pt/configuring-the-additional-freight.md  |    2 +-
 .../pt/configuring-the-scheduled-delivery.md  |    2 +-
 .../pt/configuring-the-store-domain.md        |  104 ++
 .../configuring-tuna-gateway-affiliation.md   |   12 +-
 .../pt/configuring-vtex-marketplace.md        |    8 +-
 ...g-a-layout-from-one-web-site-to-another.md |    2 +-
 docs/tutorials/pt/coupons-list-beta.md        |   12 +-
 .../pt/creating-a-campaign-audience.md        |    9 +-
 ...o-guarantee-it-as-an-option-at-checkout.md |   27 +-
 docs/tutorials/pt/creating-a-coupon-beta.md   |    8 +-
 .../pt/creating-a-more-for-less-promotion.md  |  110 +-
 .../pt/creating-a-product-collection.md       |   16 +-
 .../pt/creating-a-shipping-policy.md          |   73 +
 .../pt/creating-a-subscription-plan.md        |    2 +-
 .../pt/creating-a-subscription-promotion.md   |    2 +-
 docs/tutorials/pt/creating-a-trade-policy.md  |   42 +-
 docs/tutorials/pt/creating-a-type-of-list.md  |    4 +-
 .../creating-an-application-in-master-data.md |   52 +-
 ...h-promotional-price-using-a-price-table.md |    4 +-
 .../tutorials/pt/creating-collections-beta.md |   30 +-
 ...eating-custom-queries-in-master-data-v1.md |   62 +
 ...ustomer-and-address-forms-in-new-stores.md |   19 +-
 .../pt/creating-form-in-master-data.md        |   60 +-
 .../pt/creating-landing-pages-per-binding.md  |    2 +-
 docs/tutorials/pt/creating-landing-pages.md   |   11 +-
 ...ating-merchandising-rules-manual-editor.md |   97 ++
 ...-merchandising-rules-visual-editor-beta.md |   99 +-
 ...ating-merchandising-rules-visual-editor.md |   99 ++
 docs/tutorials/pt/creating-price-tables.md    |   24 +-
 ...eating-promotion-for-a-customer-cluster.md |    8 +-
 ...etween-master-data-entities-using-admin.md |  135 +-
 docs/tutorials/pt/creating-roles.md           |  101 ++
 .../pt/creating-service-for-a-sku.md          |   15 +-
 ...ing-subaccount-multi-store-multi-domain.md |   66 +
 docs/tutorials/pt/creating-surchargestaxes.md |   42 +-
 docs/tutorials/pt/creating-synonyms.md        |   95 ++
 .../pt/creating-trigger-in-master-data.md     |  194 +--
 docs/tutorials/pt/criar-um-produto-beta.md    |  172 +++
 docs/tutorials/pt/crm-zen-suiteshare.md       |   10 +-
 ...stom-fields-when-adding-an-organization.md |   46 +
 ...ustom-payment-information-for-argentina.md |    6 +-
 docs/tutorials/pt/custom-product-fields.md    |   90 ++
 docs/tutorials/pt/customer-approval.md        |   28 +-
 docs/tutorials/pt/customer-credit-overview.md |   91 +-
 docs/tutorials/pt/customize-suiteshare.md     |   14 +-
 .../pt/customizing-your-stores-typography.md  |    4 +-
 docs/tutorials/pt/dashboards-overview.md      |    5 +-
 ...data-dictionary-vtex-data-pipeline-beta.md |   53 +
 docs/tutorials/pt/data-entity.md              |  109 ++
 docs/tutorials/pt/data-subject-rights.md      |    6 +-
 .../pt/database-maintenance-full-cleanup.md   |    8 +-
 .../pt/declining-order-cancelation.md         |   88 ++
 ...andatory-fields-in-master-data-v1-forms.md |   30 +
 docs/tutorials/pt/defining-window-displays.md |   12 +-
 docs/tutorials/pt/deleting-a-category.md      |    2 +-
 ...liveries-progress-vtex-shipping-network.md |   16 +-
 .../pt/detaching-skus-by-specification.md     |   35 +
 ...e-the-minimum-number-of-items-in-a-cart.md |   21 +-
 .../pt/direct-migration-magazine-luiza.md     |   87 ++
 ...isplaying-the-store-in-another-language.md |    2 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |   85 ++
 ...ty-in-the-online-tokenized-payment-flow.md |   40 +
 ...ic-relevance-in-intelligent-search-beta.md |   78 +
 ...-field-on-profile-system-of-master-data.md |   26 +-
 .../pt/editing-my-data-suiteshare.md          |    8 +-
 docs/tutorials/pt/enable-checkout-v6.md       |    4 +-
 .../enabling-2-factor-authentication-login.md |   22 +-
 ...enabling-3ds2-for-redsys-v2-integration.md |   10 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |    8 +-
 .../pt/entering-tax-receipts-in-the-order.md  |    2 +-
 docs/tutorials/pt/erasing-customer-data.md    |   64 +
 ...-skus-via-spreadsheet-in-the-vtex-admin.md |   43 +
 .../tutorials/pt/events-available-in-audit.md |  851 +++--------
 docs/tutorials/pt/exact-sales-suiteshare.md   |    6 +-
 docs/tutorials/pt/explained-search.md         |   31 +
 ...mporting-product-and-sku-specifications.md |   16 +-
 docs/tutorials/pt/exporting-data.md           |   24 +-
 docs/tutorials/pt/facebook-faq.md             |    6 +-
 ...acebook-liberacao-de-dominio-suiteshare.md |    2 +-
 .../pt/facilitating-b2b-store-operation.md    |    8 +-
 docs/tutorials/pt/faq-security-2.md           |    2 +-
 .../pt/faq-security-restricted-content.md     |  187 +++
 ...-import-spreadsheets-fixed-price-fields.md |    2 +-
 docs/tutorials/pt/filtering-all-orders.md     |   25 +-
 .../pt/filtering-data-on-master-data.md       |   84 +-
 .../filtering-transactions-on-pci-gateway.md  |    4 +-
 docs/tutorials/pt/filters.md                  |   51 +
 ...tplaces-and-sellers-in-the-vtex-network.md |   10 +-
 docs/tutorials/pt/find-sellers.md             |   56 +
 ...d-questions-new-orders-module-interface.md |   12 +-
 .../pt/fulfillment-logistics-vtex.md          |    2 +-
 docs/tutorials/pt/fulfillment-magalu.md       |  126 ++
 .../pt/general-configurations-on-the-oms.md   |    6 +-
 docs/tutorials/pt/geolocalizado-suiteshare.md |   10 +-
 docs/tutorials/pt/geolocation-at-checkout.md  |    4 +-
 docs/tutorials/pt/gift-card.md                |   44 +-
 docs/tutorials/pt/google-analytics-faq.md     |   40 +-
 .../pt/google-integration-warnings.md         |   92 ++
 docs/tutorials/pt/google-pay-beta.md          |    8 +-
 docs/tutorials/pt/headless-cms-overview.md    |   53 +
 .../how-and-when-do-i-receive-my-invoice.md   |   17 +-
 ...how-can-i-change-the-domain-of-my-store.md |    2 +-
 ...how-can-i-create-a-field-in-master-data.md |    4 +-
 .../pt/how-can-i-create-callcenter-user.md    |    2 +-
 .../how-can-i-create-cluster-of-customers.md  |    8 +-
 ...-can-i-direct-a-financial-doubt-to-vtex.md |    6 +-
 ...e-newsletter-database-using-master-data.md |   21 +-
 ...w-can-i-track-the-status-of-my-disputes.md |    2 +-
 .../how-can-my-customer-login-to-my-store.md  |   18 +-
 .../pt/how-change-order-works-beta.md         |   77 +
 .../pt/how-dns-configuration-works-on-vtex.md |   37 +
 ...ow-do-i-terminate-my-contract-with-vtex.md |   10 +-
 ...e-the-https-protocol-on-my-stores-pages.md |    8 +-
 ...reversals-work-when-an-item-is-returned.md |    4 +-
 .../tutorials/pt/how-does-reservation-work.md |    4 +-
 ...th-multiple-items-work-in-mercado-livre.md |    2 +-
 .../pt/how-does-the-score-field-work.md       |   44 +-
 .../pt/how-does-the-type-of-delivery-work.md  |   22 +-
 .../pt/how-is-pro-rata-calculated-in-vtex.md  |    2 +-
 ...-the-order-delivery-deadline-calculated.md |   33 +-
 ...-the-platforms-operation-sla-determined.md |   33 +-
 ...o-cancel-an-order-with-an-unpaid-boleto.md |   57 +-
 docs/tutorials/pt/how-my-account-works.md     |   25 +-
 .../pt/how-order-authorization-works.md       |    6 +-
 .../pt/how-order-authorization-workss.md      |    8 +-
 .../pt/how-promotion-competition-works.md     |  215 +++
 .../pt/how-recursive-marketplace-works.md     |    2 +-
 .../pt/how-shipping-calculation-works.md      |    7 +-
 ...hen-delivery-is-done-by-the-marketplace.md |   17 +-
 docs/tutorials/pt/how-subscriptions-work.md   |   21 +-
 .../pt/how-the-carrefour-integration-works.md |    6 +-
 .../pt/how-the-order-replacement-works.md     |    2 +-
 .../pt/how-the-seller-portal-catalog-works.md |    2 +-
 .../how-to-activate-the-shareable-cart-app.md |    4 +-
 docs/tutorials/pt/how-to-alter-a-banner.md    |    6 +-
 .../tutorials/pt/how-to-archive-ratestaxes.md |    2 +-
 .../pt/how-to-capture-the-ip-of-an-order.md   |    4 +-
 .../tutorials/pt/how-to-change-orders-beta.md |  217 +++
 ...he-order-of-payment-methods-at-checkout.md |    4 +-
 .../tutorials/pt/how-to-check-your-balance.md |    2 +-
 .../pt/how-to-configure-a-bank-slip.md        |   55 +-
 .../pt/how-to-configure-a-custom-payment.md   |   12 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |    4 +-
 .../pt/how-to-configure-payment-conditions.md |   16 +-
 ...to-configure-rating-and-review-controls.md |    4 +-
 .../pt/how-to-configure-subscriptions.md      |   16 +-
 .../pt/how-to-configure-the-anti-fraud.md     |   34 +-
 ...uro-without-redirect-option-transparent.md |   29 +-
 ...pment-environment-with-a-mobile-version.md |    2 +-
 ...ow-to-create-a-financial-access-profile.md |    6 +-
 .../pt/how-to-create-a-page-template.md       |    6 +-
 docs/tutorials/pt/how-to-create-a-product.md  |    2 +-
 .../pt/how-to-create-a-store-name.md          |    2 +-
 ...how-to-create-a-subscription-attachment.md |    4 +-
 .../pt/how-to-create-conditional-prices.md    |    2 +-
 ...ize-the-checkout-ui-custom-in-the-admin.md |   86 ++
 ...ow-to-define-the-url-for-a-product-page.md |    2 +-
 ...w-to-deprecate-and-undeprecate-your-app.md |    2 +-
 .../how-to-disable-a-transactional-email.md   |    2 +-
 .../pt/how-to-download-the-vtex-invoices.md   |    6 +-
 .../pt/how-to-identify-a-page-template.md     |    2 +-
 ...ayout-errors-caused-by-javascript-files.md |    2 +-
 ...identify-promotions-applied-to-the-cart.md |    6 +-
 ...ore-and-salesperson-in-an-instore-order.md |   12 +-
 ...import-pickup-points-using-spreadsheets.md |    4 +-
 ...llection-of-products-in-the-shop-window.md |   18 +-
 ...ata-when-exporting-a-prices-spreadsheet.md |    4 +-
 ...reverse-proxy-in-front-of-vtex-services.md |   24 +-
 .../pt/how-to-install-a-service-worker.md     |   31 +-
 ...he-vtex-tracking-app-on-your-vtex-admin.md |    2 +-
 ...n-external-gift-card-provider-with-vtex.md |   22 +-
 .../pt/how-to-manage-subscriptions.md         |   14 +-
 .../pt/how-to-manage-the-kit-stock.md         |   10 +-
 .../pt/how-to-manually-invoice-an-order.md    |   11 +-
 ...o-modify-details-of-customers-addresses.md |   12 +-
 ...optimize-searches-with-substitute-words.md |   14 +-
 ...how-to-request-receivables-anticipation.md |    2 +-
 .../tutorials/pt/how-to-return-order-items.md |   12 +-
 .../how-to-see-orders-closed-with-benefits.md |    2 +-
 ...fine-a-default-sla-for-recurrent-orders.md |    4 +-
 .../pt/how-to-set-up-fingerprint-for-payu.md  |    2 +-
 ...set-up-recurrence-in-payment-conditions.md |    6 +-
 ...r-to-accept-payments-with-adyen-at-vtex.md |   21 +-
 ...t-up-the-device-fingerprint-for-braspag.md |    2 +-
 ...set-up-the-indeva-scheduled-appointment.md |   10 +-
 ...e-for-pick-up-field-in-smartcheckout-v6.md |    8 +-
 docs/tutorials/pt/how-to-set-up-the-zoom.md   |    6 +-
 docs/tutorials/pt/how-to-set-up-visa-debit.md |    4 +-
 ...w-to-set-up-your-store-on-seller-portal.md |   20 +-
 ...to-setup-google-analytics-in-vtex-store.md |    6 +-
 ...how-to-turn-my-store-website-into-a-pwa.md |   13 +-
 .../pt/how-to-use-conditions-builder-app.md   |    6 +-
 .../pt/how-to-use-the-index-report.md         |    6 +-
 .../pt/how-to-use-the-meta-tags-control.md    |    6 +-
 .../how-to-use-the-search-result-control.md   |   10 +-
 .../pt/how-to-use-the-shareable-cart-app.md   |   28 +-
 ...how-to-view-taxes-information-in-taxhub.md |    2 +-
 ...how-to-view-transactions-on-pci-gateway.md |    2 +-
 ...ith-different-layouts-for-the-same-page.md |    2 +-
 docs/tutorials/pt/how-trade-policies-work.md  |   19 +-
 docs/tutorials/pt/hubspot-suiteshare.md       |    4 +-
 .../pt/i-cant-import-the-price-table.md       |   67 +
 .../pt/i-cant-receive-emails-from-vtex.md     |   98 ++
 ...-cant-update-the-ean-of-my-skus-via-api.md |   50 +
 ...-view-the-product-in-the-search-results.md |  240 +++
 .../pt/i-forgot-my-password-suiteshare.md     |    6 +-
 docs/tutorials/pt/image-compression.md        |   62 +
 docs/tutorials/pt/image-widget.md             |   19 +-
 .../pt/import-customer-data-brazil.md         |   56 +-
 ...-and-exporting-an-inventory-spreadsheet.md |    4 +-
 .../pt/importing-data-into-master-data.md     |   10 +-
 .../pt/importing-images-from-a-spreadsheet.md |   10 +-
 docs/tutorials/pt/indexes-in-master-data.md   |   86 ++
 docs/tutorials/pt/indexing-history-beta.md    |   18 +-
 docs/tutorials/pt/indexing-history.md         |   68 +
 docs/tutorials/pt/indexing.md                 |   28 +
 ...information-about-chile-custom-payments.md |    6 +-
 ...ormation-about-colombia-custom-payments.md |    6 +-
 ...formation-about-uruguay-custom-payments.md |    6 +-
 ...inserting-images-into-let-me-know-email.md |    2 +-
 ...g-my-orders-through-the-extension-store.md |    6 +-
 ...stalling-the-widget-with-gtm-suiteshare.md |   20 +-
 docs/tutorials/pt/integrating-with-enjoei.md  |    4 +-
 .../pt/integrating-with-madeiramadeira.md     |    4 +-
 .../integrating-with-renner-and-camicado.md   |   34 +-
 ...-guide-for-marketplaces-seller-non-vtex.md |    6 +-
 .../pt/integration-with-google-tag-manager.md |   10 +-
 ...lligent-search-synonym-suggestions-beta.md |   42 +-
 docs/tutorials/pt/intelligent-synonyms.md     |   69 +
 ...racting-with-masterdata-through-graphql.md |   10 +-
 docs/tutorials/pt/interaction-details.md      |   27 +-
 ...erpreting-the-data-of-the-oms-order-bar.md |    2 +-
 .../tutorials/pt/introduction-to-vtex-apis.md |    2 +-
 .../pt/inventory-data-pipeline-beta.md        |   95 ++
 docs/tutorials/pt/inventory-update-history.md |   17 +-
 docs/tutorials/pt/kit-registration.md         |   28 +-
 docs/tutorials/pt/kr1-test.md                 |   30 +
 .../lead-time-shipping-time-at-sku-level.md   |  104 ++
 .../tutorials/pt/license-manager-resources.md |   18 +-
 ...-the-store-by-means-of-the-trade-policy.md |   66 +
 docs/tutorials/pt/links-suiteshare.md         |   18 +-
 .../list-of-payment-providers-by-country.md   |    6 +-
 docs/tutorials/pt/lista-da-vez.md             |    8 +-
 .../pt/locations-details-page-beta.md         |   16 +-
 .../tutorials/pt/logistics-module-overview.md |   12 +-
 docs/tutorials/pt/magento-suiteshare.md       |    2 +-
 .../pt/making-a-master-data-field-editable.md |   31 +
 .../pt/manage-the-sales-comissions-report.md  |    2 +-
 .../pt/managing-b2b-organizations.md          |  101 ++
 .../managing-credit-with-customer-credit.md   |    4 +-
 .../pt/managing-delivery-capacity.md          |   20 +-
 docs/tutorials/pt/managing-http-headers.md    |   65 +
 .../pt/managing-page-and-template-content.md  |    6 +-
 docs/tutorials/pt/managing-pages.md           |   42 +-
 docs/tutorials/pt/managing-placeholders.md    |    6 +-
 docs/tutorials/pt/managing-projects.md        |  134 ++
 .../pt/managing-redirects-per-binding.md      |   18 +-
 .../pt/managing-shipping-policies.md          |  116 ++
 .../pt/managing-singleton-content-types.md    |   33 +-
 docs/tutorials/pt/managing-stock-items.md     |   39 +-
 docs/tutorials/pt/managing-url-redirects.md   |   17 +-
 .../pt/managing-users-in-b2b-organizations.md |   66 +
 docs/tutorials/pt/managing-users.md           |   82 +-
 ...ies-and-brands-for-the-marketplace-beta.md |   12 +-
 ...re-categories-variations-and-attributes.md |    2 +-
 .../pt/marketplace-invited-sellers.md         |    2 +-
 docs/tutorials/pt/marketplace-overview.md     |    6 +-
 .../pt/marketplace-strategies-at-vtex.md      |  228 +--
 .../pt/marketplaces-and-integrations.md       |    7 +-
 docs/tutorials/pt/master-data.md              |  310 ++--
 .../pt/match-offers-mercado-livre.md          |  134 ++
 docs/tutorials/pt/media-overview.md           |  109 +-
 docs/tutorials/pt/mercado-libre-promotions.md |    2 +-
 docs/tutorials/pt/mercado-libre-size-chart.md |  137 ++
 ...ercado-livre-automobilist-compatibility.md |    4 +-
 docs/tutorials/pt/mercado-livre-faq.md        |   10 +-
 .../pt/merchandising-rule-conditions.md       |   32 +
 docs/tutorials/pt/merchandising-rules-list.md |   69 +
 docs/tutorials/pt/meta-tags-suiteshare.md     |   10 +-
 ...re-not-displayed-in-the-order-dashboard.md |   43 +
 .../minimum-stock-control-for-integrations.md |    2 +-
 docs/tutorials/pt/mode-off-faq.md             |   11 +-
 docs/tutorials/pt/moskit-suiteshare.md        |   12 +-
 ...moving-order-to-start-handling-shipping.md |   10 +-
 .../pt/multilevel-omnichannel-inventory.md    |   80 +-
 ...my-ad-is-not-displayed-on-mercado-livre.md |   61 +
 docs/tutorials/pt/my-inventory-is-negative.md |   34 +
 .../my-orders-in-mercado-libre-have-errors.md |   63 +
 .../pt/my-store-order-was-not-created.md      |   64 +
 .../pt/names-of-vtex-branches-worldwide.md    |    2 +-
 docs/tutorials/pt/navigation.md               |  208 +++
 .../new-integration-with-erede-erederest.md   |   10 +-
 docs/tutorials/pt/new-route.md                |    2 +-
 ...n-vtex-cmc-newsletteroptin-greater-than.md |    6 +-
 docs/tutorials/pt/offer-details.md            |   25 +-
 ...moderation-and-quality-of-mercado-libre.md |    4 +-
 docs/tutorials/pt/offer-management.md         |   19 +-
 docs/tutorials/pt/offer-quality-filters.md    |   12 +-
 docs/tutorials/pt/offer-status.md             |  239 +++
 ...-the-same-vtex-sellers-and-marketplaces.md |    2 +-
 docs/tutorials/pt/oms-page-structure.md       |   16 +-
 docs/tutorials/pt/opening-hours-suiteshare.md |   10 +-
 ...pening-tickets-to-vtex-support-finacial.md |   15 +-
 .../pt/opening-tickets-to-vtex-support.md     |   14 +-
 .../tutorials/pt/operational-capacity-beta.md |  198 +++
 ...ization-of-shipping-options-at-checkout.md |    2 +-
 .../pt/order-allocation-algorithm-beta.md     |    6 +-
 ...-cancellation-requested-by-the-customer.md |    8 +-
 docs/tutorials/pt/order-details-page.md       |   19 +-
 ...errors-in-the-mercado-livre-integration.md |    4 +-
 docs/tutorials/pt/order-flow-and-status.md    |   18 +-
 docs/tutorials/pt/order-replacement.md        |    8 +-
 docs/tutorials/pt/order-report.md             |   10 +-
 .../pt/order-split-and-delivery-split.md      |    7 +-
 docs/tutorials/pt/order-to-delivery.md        |   20 +-
 .../pt/order-transactional-email-templates.md |   30 +-
 docs/tutorials/pt/orderform-settings.md       |   40 +
 ...-window-display-and-on-the-product-page.md |    2 +-
 docs/tutorials/pt/orders-list.md              |    2 +-
 docs/tutorials/pt/orders-overview.md          |   15 +-
 docs/tutorials/pt/orders.md                   |  370 +++++
 .../pt/overview-of-b2b-orders-history.md      |   31 +
 docs/tutorials/pt/overview-pricing-module.md  |    8 +-
 .../tutorials/pt/payment-provider-protocol.md |  141 +-
 docs/tutorials/pt/payments.md                 |   97 ++
 .../pt/payu-romania-refund-details.md         |    2 +-
 docs/tutorials/pt/pci-gateway-overview.md     |    2 +-
 ...ration-testing-and-vulnerability-notice.md |  157 +-
 .../pt/permissions-management-in-b2b-suite.md |   67 +
 .../pt/physical-store-instore-beta.md         |    4 +-
 .../pickup-points-for-subscription-orders.md  |   54 +
 docs/tutorials/pt/pickup-points.md            |   10 +-
 docs/tutorials/pt/pipedrive-suiteshare.md     |   16 +-
 docs/tutorials/pt/piperun-suiteshare.md       |   30 +-
 docs/tutorials/pt/pix-faq.md                  |    4 +-
 docs/tutorials/pt/plan-your-project.md        |    6 +-
 .../pt/planner-calendar-page-beta.md          |    6 +-
 .../pt/planner-releases-page-beta.md          |    2 +-
 docs/tutorials/pt/predefined-roles.md         | 1340 +++-------------
 ...ier-from-meeting-certain-zip-code-range.md |    8 +-
 docs/tutorials/pt/price-divergence-rule.md    |    6 +-
 .../pt/price-divergence-rules-beta.md         |    2 +-
 ...e-table-management-in-b2b-organizations.md |   46 +
 docs/tutorials/pt/price-waterfall.md          |    2 +-
 .../tutorials/pt/prices-data-pipeline-beta.md |   91 ++
 docs/tutorials/pt/prices-settings.md          |    6 +-
 docs/tutorials/pt/prices.md                   |    8 +-
 docs/tutorials/pt/product-list.md             |    8 +-
 docs/tutorials/pt/products-and-skus-beta.md   |   22 +-
 ...oducts-errors-in-the-amazon-integration.md |    2 +-
 docs/tutorials/pt/promotion-alerts-beta.md    |    2 +-
 docs/tutorials/pt/promotion-list-beta.md      |   12 +-
 docs/tutorials/pt/promotion-summary.md        |    2 +-
 docs/tutorials/pt/promotions-beta.md          |    8 +-
 docs/tutorials/pt/promotions-overview.md      |    6 +-
 .../tutorials/pt/promotions-simulator-beta.md |  110 +-
 docs/tutorials/pt/promotions-simulator.md     |    6 +-
 docs/tutorials/pt/promotions.md               |  108 ++
 .../protection-against-transaction-attacks.md |   17 +-
 docs/tutorials/pt/qr-code-suiteshare.md       |   10 +-
 docs/tutorials/pt/rdstation-crm-suiteshare.md |   10 +-
 docs/tutorials/pt/rdstation-suiteshare.md     |   12 +-
 docs/tutorials/pt/ready-to-dispatch.md        |   20 +-
 docs/tutorials/pt/received-skus-beta.md       |  223 +++
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |  106 ++
 .../pt/redirect-from-other-addresses.md       |   81 +
 docs/tutorials/pt/redirects.md                |   41 +
 docs/tutorials/pt/registering-a-category.md   |    6 +-
 docs/tutorials/pt/registering-brands.md       |    2 +-
 .../pt/registering-gateway-affiliations.md    |   78 +-
 docs/tutorials/pt/registering-geolocation.md  |    8 +-
 ...ing-the-skus-barcode-for-vtex-sales-app.md |   10 +-
 ...-with-nominal-discount-based-on-formula.md |    8 +-
 .../pt/regular-promotion-with-reward-value.md |   16 +-
 docs/tutorials/pt/regular-promotion.md        |   14 +-
 docs/tutorials/pt/releases-module-beta.md     |    4 +-
 .../pt/releasing-the-store-for-production.md  |    2 +-
 docs/tutorials/pt/relevance-rules.md          |  114 ++
 docs/tutorials/pt/remarketing.md              |   10 +-
 ...request-headers-must-only-contain-ascii.md |   91 ++
 docs/tutorials/pt/reports.md                  |    2 +-
 .../pt/requesting-a-new-organization.md       |   98 ++
 .../requesting-an-additional-trade-policy.md  |   18 +-
 ...factor-authentication-app-configuration.md |   36 +-
 .../responsibilities-in-the-vtex-ecosystem.md |  219 +++
 ...ict-public-access-to-master-data-fields.md |   59 +
 docs/tutorials/pt/risk-assessment.md          |  467 ++++++
 docs/tutorials/pt/roles.md                    |  105 +-
 docs/tutorials/pt/rounding-rules.md           |    8 +-
 docs/tutorials/pt/routing-monitoring.md       |    2 +-
 .../pt/sales-app-sales-performance.md         |    4 +-
 .../sales-associate-code-field-at-checkout.md |   96 ++
 .../pt/sales-associates-instore-beta.md       |    4 +-
 docs/tutorials/pt/sales-funnel-suiteshare.md  |    8 +-
 docs/tutorials/pt/sales-performance.md        |   12 +-
 docs/tutorials/pt/scheduled-delivery.md       |   12 +-
 .../scheduling-features-for-special-events.md |    2 +-
 docs/tutorials/pt/search-behavior.md          |  134 ++
 docs/tutorials/pt/search-configuration.md     |   53 +
 docs/tutorials/pt/searching-for-old-orders.md |    2 +-
 .../searching-for-transactions-on-payments.md |    4 +-
 docs/tutorials/pt/security-certificate-ssl.md |   26 +
 .../pt/security-education-and-awareness.md    |    4 +-
 docs/tutorials/pt/security-monitor.md         |  131 ++
 ...ng-stock-for-orders-mercado-envios-full.md |    4 +-
 docs/tutorials/pt/seletivo.md                 |   14 +-
 docs/tutorials/pt/seller-management.md        |    4 +-
 docs/tutorials/pt/seller-monitoring.md        |   64 +
 .../pt/seller-portal-creating-a-promotion.md  |  102 ++
 ...tal-getting-started-for-the-marketplace.md |    2 +-
 .../pt/seller-portal-product-details.md       |    2 +-
 docs/tutorials/pt/seller-portal-promotions.md |   96 ++
 .../pt/seller-portal-shared-products.md       |   11 +-
 ...nd-item-price-with-tax-shown-separately.md |    8 +-
 .../pt/sending-sku-attributes-to-amazon.md    |    4 +-
 docs/tutorials/pt/sent-offers-beta.md         |    2 +-
 .../pt/sent-offers-buybox-opportunities.md    |   55 +-
 docs/tutorials/pt/sequencial-suiteshare.md    |    8 +-
 docs/tutorials/pt/services-import.md          |    2 +-
 docs/tutorials/pt/services-scheduling.md      |    4 +-
 docs/tutorials/pt/set-up-mundi-gateway.md     |   12 +-
 ...r-authentication-for-recurring-payments.md |    2 +-
 ...ct-suggestions-accessories-and-generics.md |    8 +-
 .../pt/setting-up-abandoned-carts.md          |  179 +--
 ...app-linking-for-payments-app-in-instore.md |    2 +-
 .../setting-up-bradesco-registered-ticket.md  |   44 +-
 .../pt/setting-up-braspag-gateway.md          |    6 +-
 .../pt/setting-up-conductor-gateway.md        |   15 +-
 .../pt/setting-up-cybersource-antifraud.md    |   45 +-
 .../pt/setting-up-cybersource-gateway.md      |  227 ++-
 .../pt/setting-up-firstdata-acquirer.md       |   84 +-
 ...-getnet-acquirer-with-egetnet-connector.md |   30 +-
 ...ent-search-integration-with-the-catalog.md |   30 +
 ...-itau-registered-ticket-itau-registrado.md |   42 +-
 .../pt/setting-up-itau-registered-ticket.md   |    6 +-
 ...eto-in-installments-as-a-payment-method.md |   25 +-
 .../setting-up-mercadopagov1-sub-acquirer.md  |   18 +-
 .../setting-up-mercadopagov2-sub-acquirer.md  |   72 +-
 .../pt/setting-up-merchant-id-in-apple-pay.md |   40 +-
 ...g-up-mundipagg-fraud-prevention-gateway.md |   15 +-
 .../pt/setting-up-mundipagg-gateway.md        |   15 +-
 docs/tutorials/pt/setting-up-my-account.md    |    8 +-
 .../pt/setting-up-nexxpago-gateway.md         |   24 +-
 docs/tutorials/pt/setting-up-nps-gateway.md   |    8 +-
 .../pt/setting-up-pagar-me-gateway.md         |   11 +-
 .../pt/setting-up-pagarmev2-gateway.md        |   20 +-
 .../pt/setting-up-pagbrasil-gateway.md        |   15 +-
 .../pt/setting-up-paghiper-gateway.md         |   15 +-
 docs/tutorials/pt/setting-up-pagseguro-v3.md  |   40 +-
 .../pt/setting-up-payment-with-paypal.md      |    8 +-
 .../pt/setting-up-paymentez-gateway.md        |   26 +-
 .../pt/setting-up-payments-with-55pay.md      |   14 +-
 .../pt/setting-up-payments-with-99pay.md      |   14 +-
 .../pt/setting-up-payments-with-aarin.md      |   14 +-
 .../pt/setting-up-payments-with-addi.md       |   15 +-
 .../pt/setting-up-payments-with-alignet.md    |   25 +-
 .../pt/setting-up-payments-with-alignetv2.md  |   39 +
 .../setting-up-payments-with-ame-digital.md   |   20 +-
 .../pt/setting-up-payments-with-apple-pay.md  |   44 +-
 .../pt/setting-up-payments-with-appmax.md     |   33 +
 .../pt/setting-up-payments-with-argonpay.md   |   50 +
 .../pt/setting-up-payments-with-astropay.md   |   16 +-
 .../pt/setting-up-payments-with-bamboo.md     |   10 +-
 ...tting-up-payments-with-bancolombia-bnpl.md |   16 +-
 .../pt/setting-up-payments-with-banqi.md      |   14 +-
 .../pt/setting-up-payments-with-bitfy.md      |   14 +-
 .../pt/setting-up-payments-with-bluepay.md    |   14 +-
 .../pt/setting-up-payments-with-boletoflex.md |   11 +-
 ...etting-up-payments-with-bom-pra-credito.md |   14 +-
 .../pt/setting-up-payments-with-braintree.md  |   50 +
 .../pt/setting-up-payments-with-braspagv2.md  |    6 +-
 ...-up-payments-with-brinks-cash-ecommerce.md |   16 +-
 ...setting-up-payments-with-cieloecommerce.md |   66 +
 .../pt/setting-up-payments-with-cielov4.md    |    6 +-
 .../pt/setting-up-payments-with-conekta.md    |   20 +-
 .../pt/setting-up-payments-with-crecoscorp.md |   10 +-
 .../setting-up-payments-with-credimarcas.md   |   61 +
 .../pt/setting-up-payments-with-credit-key.md |   16 +-
 .../pt/setting-up-payments-with-culqi.md      |   58 +
 .../pt/setting-up-payments-with-dapp.md       |   39 +
 .../pt/setting-up-payments-with-deuna.md      |   49 +
 ...tting-up-payments-with-digital-river-v2.md |   14 +-
 ...etting-up-payments-with-dlocal-payments.md |   14 +-
 .../pt/setting-up-payments-with-dock.md       |   14 +-
 .../pt/setting-up-payments-with-e-sitef.md    |   48 +
 ...ng-up-payments-with-easypay-marketplace.md |  232 +++
 ...setting-up-payments-with-easypay-seller.md |   51 +
 .../pt/setting-up-payments-with-easypay.md    |  210 +++
 .../setting-up-payments-with-ebanx-local.md   |   14 +-
 .../pt/setting-up-payments-with-ebanx.md      |   14 +-
 .../pt/setting-up-payments-with-egetnetv2.md  |   28 +-
 .../pt/setting-up-payments-with-etpay.md      |   16 +-
 .../setting-up-payments-with-evopayments.md   |   46 +
 ...payments-with-fcamara-payment-initiator.md |   14 +-
 .../pt/setting-up-payments-with-fintoc.md     |   39 +
 .../pt/setting-up-payments-with-flywire.md    |   16 +-
 .../pt/setting-up-payments-with-fpay.md       |   14 +-
 .../pt/setting-up-payments-with-geru.md       |   40 +
 .../pt/setting-up-payments-with-gocuotas.md   |   39 +
 .../pt/setting-up-payments-with-guatapay.md   |   39 +
 .../pt/setting-up-payments-with-inswitch.md   |   49 +
 .../pt/setting-up-payments-with-itau-rede.md  |   91 ++
 .../pt/setting-up-payments-with-iugu.md       |   73 +-
 .../pt/setting-up-payments-with-k8bank.md     |   44 +
 .../pt/setting-up-payments-with-kaiowa.md     |   14 +-
 .../pt/setting-up-payments-with-khipu.md      |   16 +-
 .../setting-up-payments-with-koin-payments.md |   24 +-
 .../pt/setting-up-payments-with-koin.md       |    8 +-
 .../pt/setting-up-payments-with-kueski-pay.md |   10 +-
 ...etting-up-payments-with-liquido-payment.md |   32 +
 .../pt/setting-up-payments-with-mach.md       |   16 +-
 .../pt/setting-up-payments-with-meliuz.md     |   14 +-
 .../setting-up-payments-with-mercado-pago.md  |   13 +-
 .../pt/setting-up-payments-with-mobbex.md     |   34 +
 .../setting-up-payments-with-msc-payment.md   |   51 +
 ...ayments-with-netpay-and-netpay-checkout.md |   24 +-
 .../setting-up-payments-with-notes-payable.md |   57 +
 .../pt/setting-up-payments-with-nupay.md      |   14 +-
 .../pt/setting-up-payments-with-nuvei.md      |   69 +
 .../pt/setting-up-payments-with-pagaleve.md   |   14 +-
 .../pt/setting-up-payments-with-pagarmev3.md  |   28 +-
 .../setting-up-payments-with-pagbrasilv2.md   |   40 +
 .../pt/setting-up-payments-with-paghiperv2.md |   36 +
 .../pt/setting-up-payments-with-paghiperv3.md |   38 +
 .../setting-up-payments-with-pagoefectivo.md  |    6 +-
 ...setting-up-payments-with-pagoefectivov2.md |   55 +
 .../setting-up-payments-with-pagoexpress.md   |   40 +
 .../pt/setting-up-payments-with-pagosweb.md   |    8 +-
 .../pt/setting-up-payments-with-parcelex.md   |   26 +-
 .../pt/setting-up-payments-with-pay4fun.md    |   40 +
 .../pt/setting-up-payments-with-paycash.md    |   14 +-
 .../pt/setting-up-payments-with-payclub.md    |    8 +-
 .../setting-up-payments-with-paymentezv2.md   |   34 +
 .../pt/setting-up-payments-with-paypalv2.md   |   43 +
 .../pt/setting-up-payments-with-payu-india.md |   20 +-
 .../pt/setting-up-payments-with-payuv2.md     |   48 +
 .../pt/setting-up-payments-with-payway.md     |   37 +
 .../pt/setting-up-payments-with-picpay.md     |   16 +-
 .../pt/setting-up-payments-with-pine-labs.md  |   16 +-
 .../pt/setting-up-payments-with-poolpay.md    |   33 +
 .../pt/setting-up-payments-with-powerpay.md   |   50 +
 ...etting-up-payments-with-puntos-colombia.md |   16 +-
 .../pt/setting-up-payments-with-qhantuy.md    |   14 +-
 .../pt/setting-up-payments-with-retrypay.md   |   18 +-
 .../setting-up-payments-with-safetypayv2.md   |   33 +
 .../pt/setting-up-payments-with-scalapay.md   |   18 +-
 .../pt/setting-up-payments-with-shipay.md     |   14 +-
 .../pt/setting-up-payments-with-sibs.md       |   16 +-
 .../pt/setting-up-payments-with-stark-bank.md |   34 +
 .../pt/setting-up-payments-with-stelo.md      |    8 +-
 .../pt/setting-up-payments-with-stelom1v2.md  |   33 +
 ...g-up-payments-with-store-card-cobranded.md |   19 +-
 ...payments-with-transfero-crypto-checkout.md |   49 +
 .../setting-up-payments-with-tyendacrypto.md  |   14 +-
 .../pt/setting-up-payments-with-unlimit.md    |   43 +
 .../pt/setting-up-payments-with-ventipay.md   |   16 +-
 .../pt/setting-up-payments-with-virtuspay.md  |   16 +-
 .../setting-up-payments-with-virtuspayv2.md   |   14 +-
 ...setting-up-payments-with-webpayoneclick.md |   39 +
 .../pt/setting-up-payments-with-wepay4u.md    |   52 +
 .../pt/setting-up-payments-with-wompi.md      |   10 +-
 .../pt/setting-up-payments-with-wompicov2.md  |    8 +-
 .../pt/setting-up-payments-with-woovi.md      |   40 +
 .../pt/setting-up-payments-with-yuno.md       |   14 +-
 .../pt/setting-up-payments-with-zenki.md      |   16 +-
 .../pt/setting-up-payments-with-zoop.md       |   24 +-
 docs/tutorials/pt/setting-up-paypal-plus.md   |   64 +-
 docs/tutorials/pt/setting-up-payu-gateway.md  |   15 +-
 .../tutorials/pt/setting-up-payzen-gateway.md |    8 +-
 ...ng-up-personal-data-on-the-users-screen.md |   12 +-
 .../pt/setting-up-place2pay-gateway.md        |    8 +-
 ...ting-up-price-tables-for-specific-users.md |    6 +-
 ...setting-up-rede-acquirer-with-erederest.md |    8 +-
 ...up-seller-white-label-as-a-pickup-point.md |   12 +-
 docs/tutorials/pt/setting-up-shipment.md      |    2 +-
 .../setting-up-sitef-gateway-with-pre-auth.md |    8 +-
 docs/tutorials/pt/setting-up-sitef-gateway.md |   18 +-
 .../pt/setting-up-sms-password-recovery.md    |   12 +-
 .../pt/setting-up-sub-acquirer-stelo.md       |    8 +-
 .../pt/setting-up-the-critical-stock-alert.md |    2 +-
 .../setting-up-the-notes-payable-conector.md  |   31 +
 .../pt/setting-up-the-notify-me-option.md     |    2 +-
 .../pt/setting-up-the-paymee-gateway.md       |   33 +-
 .../pt/setting-up-the-price-range-filter.md   |    2 +-
 ...up-the-sales-funnel-on-google-analytics.md |   10 +-
 .../pt/setting-up-the-tnspay-gateway.md       |    8 +-
 .../setting-up-the-type-of-interest-rate.md   |    2 +-
 .../pt/setting-up-the-voucher-list.md         |    4 +-
 .../pt/setting-up-the-worldpay-acquirer.md    |   39 +-
 .../setting-up-the-yamisplitmoipv1-gateway.md |   26 +-
 .../tutorials/pt/setting-up-vcmais-gateway.md |    4 +-
 docs/tutorials/pt/setting-up-vindi-gateway.md |   30 +-
 .../pt/setting-up-webpay2p-gateway.md         |    4 +-
 docs/tutorials/pt/setup-safetypay.md          |   18 +-
 ...ween-a-marketplace-and-a-seller-on-vtex.md |   12 +-
 docs/tutorials/pt/sharpspring-suiteshare.md   |   14 +-
 docs/tutorials/pt/shipping-options-beta.md    |   10 +-
 docs/tutorials/pt/shipping-policy.md          |   91 +-
 docs/tutorials/pt/shipping-rate-template.md   |   12 +-
 docs/tutorials/pt/shipping-rates.md           |    2 +-
 docs/tutorials/pt/shipping-simulation.md      |    8 +-
 docs/tutorials/pt/shipping-strategy.md        |   29 +-
 docs/tutorials/pt/shopee-integration.md       |   85 +-
 docs/tutorials/pt/shopify-suiteshare.md       |    2 +-
 docs/tutorials/pt/site-editor-overview.md     |    2 +-
 docs/tutorials/pt/sku-bindings.md             |    8 +-
 docs/tutorials/pt/sku-price-change.md         |   55 +-
 docs/tutorials/pt/sku-registration-fields.md  |    6 +-
 docs/tutorials/pt/skus.md                     |  128 ++
 ...martcheckout-v5-general-characteristics.md |   70 +
 docs/tutorials/pt/special-conditions.md       |   18 +-
 docs/tutorials/pt/split-payment.md            |   45 +-
 docs/tutorials/pt/store-access-permission.md  |    2 +-
 docs/tutorials/pt/store-overview-beta.md      |  162 ++
 docs/tutorials/pt/store-overview.md           |   18 +-
 docs/tutorials/pt/store-profile.md            |   86 ++
 docs/tutorials/pt/store-settings-overview.md  |   10 +-
 docs/tutorials/pt/styles-overview.md          |    2 +-
 docs/tutorials/pt/subscription-plans.md       |    2 +-
 docs/tutorials/pt/synonym-list.md             |  112 ++
 docs/tutorials/pt/table-of-base-prices.md     |    2 +-
 docs/tutorials/pt/telesales-features.md       |    6 +-
 docs/tutorials/pt/telesales-toolbar.md        |   17 +-
 docs/tutorials/pt/test-kr1.md                 |   18 +
 docs/tutorials/pt/teste.md                    |    2 +-
 ...-into-packages-with-separate-deliveries.md |   46 +
 ...sult-is-different-from-the-product-page.md |    6 +-
 ...help-the-performance-of-your-e-commerce.md |    6 +-
 .../pt/tracking-your-sales-analytics.md       |   16 +-
 ...actional-emails-for-subscription-orders.md |   10 +-
 docs/tutorials/pt/transactions-events.md      |    2 +-
 .../pt/transferring-store-ownership.md        |    2 +-
 ...eshooting-errors-in-subscription-orders.md |   14 +-
 .../pt/tutorial-vtex-tracking-mobile-app.md   |   32 +-
 docs/tutorials/pt/understand-your-balance.md  |    2 +-
 docs/tutorials/pt/understanding-b2b-orders.md |    2 +-
 .../pt/understanding-how-indexation-works.md  |    9 +-
 .../pt/understanding-how-the-cache-works.md   |    6 +-
 ...standing-storebuilder-and-stylesbuilder.md |   18 +-
 ...erstanding-the-additional-shipping-cost.md |    6 +-
 .../understanding-the-cubic-weight-factor.md  |   34 +-
 .../pt/understanding-the-message-center.md    |    2 +-
 .../pt/understanding-the-price-change-rule.md |    2 +-
 .../pt/understanding-the-security-report.md   |    2 +-
 docs/tutorials/pt/understanding-the-topbar.md |    8 +-
 .../understanding-the-updating-of-the-xml.md  |    4 +-
 ...nderstanding-vtexs-email-capture-system.md |    8 +-
 .../untitled-entry-2024-03-13-at-16-25-15.md  |   18 +
 .../untitled-entry-2024-07-25-at-21-25-31.md  |   18 +
 ...ting-the-quantity-of-items-in-inventory.md |    2 +-
 .../pt/using-recaptcha-at-checkout.md         |   43 +-
 ...-track-browsing-sessions-in-vtex-stores.md |    2 +-
 .../pt/using-the-project-task-timeline.md     |    6 +-
 ...r-store-and-uploading-it-for-production.md |    6 +-
 .../pt/via-inventory-integration-errors.md    |   18 +-
 .../visao-geral-configuracoes-de-usuario.md   |    2 +-
 docs/tutorials/pt/vtex-ad-network-beta.md     |  124 ++
 docs/tutorials/pt/vtex-admin-start-here.md    |   59 +-
 docs/tutorials/pt/vtex-admin-start-here1.md   |   10 +-
 docs/tutorials/pt/vtex-agreement.md           |   35 +
 ...vtex-dashboard-guide-for-black-week-faq.md |  199 +++
 docs/tutorials/pt/vtex-do-interface.md        |   10 +-
 docs/tutorials/pt/vtex-insurance.md           |   43 +-
 ...gent-search-multilanguage-settings-beta.md |   18 +-
 docs/tutorials/pt/vtex-invoice-notifier.md    |   12 +-
 ...x-operation-service-level-agreement-sla.md |   27 +
 .../pt/vtex-pick-and-pack-fulfillment.md      |    8 +-
 .../pt/vtex-pick-and-pack-insights.md         |   65 +
 .../pt/vtex-pick-and-pack-last-mile.md        |    9 +-
 .../tutorials/pt/vtex-pick-and-pack-mobile.md |  225 +++
 .../tutorials/pt/vtex-pick-and-pack-orders.md |   95 ++
 .../pt/vtex-pick-and-pack-settings.md         |  269 ++++
 .../pt/vtex-pick-and-pack-worksheets.md       |   79 +
 docs/tutorials/pt/vtex-pick-and-pack.md       |    8 +-
 docs/tutorials/pt/vtex-shield.md              |   63 +
 ...ex-shipping-network-correios-activation.md |   78 +
 .../pt/vtex-shipping-network-correios-faq.md  |    6 +-
 .../pt/vtex-shipping-network-dashboard.md     |   20 +-
 docs/tutorials/pt/vtex-status-page.md         |  169 +++
 docs/tutorials/pt/vtex-suiteshare.md          |   12 +-
 docs/tutorials/pt/vtex-support-apac.md        |   18 +
 docs/tutorials/pt/vtex-tracking-agencies.md   |    4 +-
 docs/tutorials/pt/warehouse.md                |    2 +-
 .../pt/web-application-firewall-waf.md        |   58 +
 docs/tutorials/pt/web-page-performance.md     |    4 +-
 ...urce-and-orders-with-fulfillment-source.md |    2 +-
 docs/tutorials/pt/what-are-templates.md       |    2 +-
 ...payments-are-available-in-latin-america.md |    6 +-
 ...tivate-a-gift-multiplier-on-a-promotion.md |    2 +-
 ...r-as-revenue-in-the-billing-calculation.md |    2 +-
 .../pt/what-is-a-franchise-account.md         |   11 +-
 docs/tutorials/pt/what-is-a-service.md        |    6 +-
 docs/tutorials/pt/what-is-a-transaction.md    |   10 +-
 docs/tutorials/pt/what-is-an-affiliate.md     |    6 +-
 docs/tutorials/pt/what-is-an-e-wallet.md      |    8 +-
 docs/tutorials/pt/what-is-deposit-slip.md     |   15 +-
 ...rand-gateway-and-sub-acquirer-in-brazil.md |   15 +-
 ...ce-between-inventory-and-warehouse-dock.md |    2 +-
 ...-the-difference-between-product-and-sku.md |    8 +-
 ...what-is-the-maximum-limit-of-promotions.md |   13 +-
 docs/tutorials/pt/what-is-the-pci-ssc.md      |    6 +-
 ...s-the-purpose-of-the-customized-control.md |    2 +-
 .../pt/what-is-transparent-checkout.md        |    6 +-
 ...nditions-are-available-in-latin-america.md |    6 +-
 ...-when-my-report-does-not-reach-my-inbox.md |   15 +-
 ...app-ai-campaigns-management-and-details.md |   96 ++
 ...re-do-i-see-clients-that-use-recurrence.md |    2 +-
 ...y-certificates-may-be-added-to-my-store.md |    6 +-
 docs/tutorials/pt/white-label-seller.md       |    5 +-
 .../pt/white-label-sellers-selection.md       |   10 +-
 ...ketplace-orders-integrate-with-my-store.md |   42 +
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |    8 +-
 docs/tutorials/pt/widget.md                   |   18 +-
 docs/tutorials/pt/wix-suiteshare.md           |    6 +-
 docs/tutorials/pt/wordpress-suiteshare.md     |    6 +-
 ...ing-an-effective-ticket-to-vtex-support.md |   70 +-
 docs/tutorials/pt/zapier-suiteshare.md        |   14 +-
 6054 files changed, 161156 insertions(+), 28739 deletions(-)
 create mode 100644 docs/announcements/en/amazon-integration-amazon-offer-matching.md
 create mode 100644 docs/announcements/en/amazon-new-category-mapping-model.md
 create mode 100644 docs/announcements/en/automatic-archiving-inactive-promotions.md
 create mode 100644 docs/announcements/en/black-week-vtex-dashboards-analysis-strategies.md
 create mode 100644 docs/announcements/en/callback-url-signature-authentication-token.md
 create mode 100644 docs/announcements/en/changes-in-vtex-support-service-policy.md
 create mode 100644 docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md
 create mode 100644 docs/announcements/en/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
 create mode 100644 docs/announcements/en/custom-selection-of-sellers-for-b2b-purchases.md
 create mode 100644 docs/announcements/en/discontinuation-of-legacy-payment-connectors.md
 create mode 100644 docs/announcements/en/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
 create mode 100644 docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
 create mode 100644 docs/announcements/en/faster-customer-support-with-new-solutions-for-vtex-clients.md
 create mode 100644 docs/announcements/en/get-to-know-the-new-vtex-status-page.md
 create mode 100644 docs/announcements/en/google-catalog-migration.md
 create mode 100644 docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md
 create mode 100644 docs/announcements/en/google-shopping-new-option-to-submit-prices.md
 create mode 100644 docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md
 create mode 100644 docs/announcements/en/headless-cms-events-available-in-audit.md
 create mode 100644 docs/announcements/en/headless-cms-new-authorization-requirement.md
 create mode 100644 docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md
 create mode 100644 docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md
 create mode 100644 docs/announcements/en/headless-cms-updated-user-permissions.md
 create mode 100644 docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md
 create mode 100644 docs/announcements/en/introducing-vtex-ad-network-beta.md
 create mode 100644 docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
 create mode 100644 docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md
 create mode 100644 docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
 create mode 100644 docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md
 create mode 100644 docs/announcements/en/multi-currency-gift-card.md
 create mode 100644 docs/announcements/en/multilanguage-checkout-launch.md
 create mode 100644 docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
 create mode 100644 docs/announcements/en/new-checkout-settings-for-bot-attack-protection.md
 create mode 100644 docs/announcements/en/new-documentation-explore-the-technical-aspects-of-the-platform.md
 create mode 100644 docs/announcements/en/new-feature-product-feedback-in-the-vtex-admin.md
 create mode 100644 docs/announcements/en/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
 create mode 100644 docs/announcements/en/new-google-and-yahoo-requirements-for-bulk-email-senders.md
 create mode 100644 docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
 create mode 100644 docs/announcements/en/new-permission-required-to-manage-redirects-in-store-framework-cms.md
 create mode 100644 docs/announcements/en/new-process-for-security-testing.md
 create mode 100644 docs/announcements/en/new-roles-page.md
 create mode 100644 docs/announcements/en/new-rules-for-activating-vtex-support.md
 create mode 100644 docs/announcements/en/new-sales-app-performance-monitor.md
 create mode 100644 docs/announcements/en/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
 create mode 100644 docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md
 create mode 100644 docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md
 create mode 100644 docs/announcements/en/performance-monitor.md
 create mode 100644 docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
 create mode 100644 docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
 create mode 100644 docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
 create mode 100644 docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
 create mode 100644 docs/announcements/en/site-editor-and-media-new-authorization-requirement.md
 create mode 100644 docs/announcements/en/site-editor-fixed-content-loss-issue.md
 create mode 100644 docs/announcements/en/the-insights-dashboard-will-be-discontinued.md
 create mode 100644 docs/announcements/en/the-offer-management-module-will-be-discontinued.md
 create mode 100644 docs/announcements/en/troubleshooting-guides-your-new-vtex-self-service-experience.md
 create mode 100644 docs/announcements/en/update-of-the-external-privacy-notice.md
 create mode 100644 docs/announcements/en/vtex-insurance-discontinuity.md
 create mode 100644 docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
 create mode 100644 docs/announcements/en/vtex-sales-app-will-no-longer-be-available-for-windows.md
 create mode 100644 docs/announcements/en/web-page-performance-deprecation.md
 create mode 100644 docs/announcements/es/amazon-integration-amazon-offer-matching.md
 create mode 100644 docs/announcements/es/amazon-new-category-mapping-model.md
 create mode 100644 docs/announcements/es/automatic-archiving-inactive-promotions.md
 create mode 100644 docs/announcements/es/black-week-vtex-dashboards-analysis-strategies.md
 create mode 100644 docs/announcements/es/callback-url-signature-authentication-token.md
 create mode 100644 docs/announcements/es/changes-in-vtex-support-service-policy.md
 create mode 100644 docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md
 create mode 100644 docs/announcements/es/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
 create mode 100644 docs/announcements/es/custom-selection-of-sellers-for-b2b-purchases.md
 create mode 100644 docs/announcements/es/discontinuation-of-legacy-payment-connectors.md
 create mode 100644 docs/announcements/es/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
 create mode 100644 docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
 create mode 100644 docs/announcements/es/faster-customer-support-with-new-solutions-for-vtex-clients.md
 create mode 100644 docs/announcements/es/get-to-know-the-new-vtex-status-page.md
 create mode 100644 docs/announcements/es/google-catalog-migration.md
 create mode 100644 docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md
 create mode 100644 docs/announcements/es/google-shopping-new-option-to-submit-prices.md
 create mode 100644 docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md
 create mode 100644 docs/announcements/es/headless-cms-events-available-in-audit.md
 create mode 100644 docs/announcements/es/headless-cms-new-authorization-requirement.md
 create mode 100644 docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md
 create mode 100644 docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md
 create mode 100644 docs/announcements/es/headless-cms-updated-user-permissions.md
 create mode 100644 docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md
 create mode 100644 docs/announcements/es/introducing-vtex-ad-network-beta.md
 create mode 100644 docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
 create mode 100644 docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md
 create mode 100644 docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
 create mode 100644 docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md
 create mode 100644 docs/announcements/es/multi-currency-gift-card.md
 create mode 100644 docs/announcements/es/multilanguage-checkout-launch.md
 create mode 100644 docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
 create mode 100644 docs/announcements/es/new-checkout-settings-for-bot-attack-protection.md
 create mode 100644 docs/announcements/es/new-documentation-explore-the-technical-aspects-of-the-platform.md
 create mode 100644 docs/announcements/es/new-feature-product-feedback-in-the-vtex-admin.md
 create mode 100644 docs/announcements/es/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
 create mode 100644 docs/announcements/es/new-google-and-yahoo-requirements-for-bulk-email-senders.md
 create mode 100644 docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
 create mode 100644 docs/announcements/es/new-permission-required-to-manage-redirects-in-store-framework-cms.md
 create mode 100644 docs/announcements/es/new-process-for-security-testing.md
 create mode 100644 docs/announcements/es/new-roles-page.md
 create mode 100644 docs/announcements/es/new-rules-for-activating-vtex-support.md
 create mode 100644 docs/announcements/es/new-sales-app-performance-monitor.md
 create mode 100644 docs/announcements/es/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
 create mode 100644 docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md
 create mode 100644 docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md
 create mode 100644 docs/announcements/es/performance-monitor.md
 create mode 100644 docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
 create mode 100644 docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
 create mode 100644 docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
 create mode 100644 docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
 create mode 100644 docs/announcements/es/site-editor-and-media-new-authorization-requirement.md
 create mode 100644 docs/announcements/es/site-editor-fixed-content-loss-issue.md
 create mode 100644 docs/announcements/es/the-insights-dashboard-will-be-discontinued.md
 create mode 100644 docs/announcements/es/the-offer-management-module-will-be-discontinued.md
 create mode 100644 docs/announcements/es/troubleshooting-guides-your-new-vtex-self-service-experience.md
 create mode 100644 docs/announcements/es/update-of-the-external-privacy-notice.md
 create mode 100644 docs/announcements/es/vtex-insurance-discontinuity.md
 create mode 100644 docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
 create mode 100644 docs/announcements/es/vtex-sales-app-will-no-longer-be-available-for-windows.md
 create mode 100644 docs/announcements/es/web-page-performance-deprecation.md
 create mode 100644 docs/announcements/pt/amazon-integration-amazon-offer-matching.md
 create mode 100644 docs/announcements/pt/amazon-new-category-mapping-model.md
 create mode 100644 docs/announcements/pt/automatic-archiving-inactive-promotions.md
 create mode 100644 docs/announcements/pt/black-week-vtex-dashboards-analysis-strategies.md
 create mode 100644 docs/announcements/pt/callback-url-signature-authentication-token.md
 create mode 100644 docs/announcements/pt/changes-in-vtex-support-service-policy.md
 create mode 100644 docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md
 create mode 100644 docs/announcements/pt/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
 create mode 100644 docs/announcements/pt/custom-selection-of-sellers-for-b2b-purchases.md
 create mode 100644 docs/announcements/pt/discontinuation-of-legacy-payment-connectors.md
 create mode 100644 docs/announcements/pt/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
 create mode 100644 docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
 create mode 100644 docs/announcements/pt/faster-customer-support-with-new-solutions-for-vtex-clients.md
 create mode 100644 docs/announcements/pt/get-to-know-the-new-vtex-status-page.md
 create mode 100644 docs/announcements/pt/google-catalog-migration.md
 create mode 100644 docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md
 create mode 100644 docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
 create mode 100644 docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md
 create mode 100644 docs/announcements/pt/headless-cms-events-available-in-audit.md
 create mode 100644 docs/announcements/pt/headless-cms-new-authorization-requirement.md
 create mode 100644 docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md
 create mode 100644 docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md
 create mode 100644 docs/announcements/pt/headless-cms-updated-user-permissions.md
 create mode 100644 docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md
 create mode 100644 docs/announcements/pt/introducing-vtex-ad-network-beta.md
 create mode 100644 docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
 create mode 100644 docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md
 create mode 100644 docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
 create mode 100644 docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md
 create mode 100644 docs/announcements/pt/multi-currency-gift-card.md
 create mode 100644 docs/announcements/pt/multilanguage-checkout-launch.md
 create mode 100644 docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
 create mode 100644 docs/announcements/pt/new-checkout-settings-for-bot-attack-protection.md
 create mode 100644 docs/announcements/pt/new-documentation-explore-the-technical-aspects-of-the-platform.md
 create mode 100644 docs/announcements/pt/new-feature-product-feedback-in-the-vtex-admin.md
 create mode 100644 docs/announcements/pt/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
 create mode 100644 docs/announcements/pt/new-google-and-yahoo-requirements-for-bulk-email-senders.md
 create mode 100644 docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
 create mode 100644 docs/announcements/pt/new-permission-required-to-manage-redirects-in-store-framework-cms.md
 create mode 100644 docs/announcements/pt/new-process-for-security-testing.md
 create mode 100644 docs/announcements/pt/new-roles-page.md
 create mode 100644 docs/announcements/pt/new-rules-for-activating-vtex-support.md
 create mode 100644 docs/announcements/pt/new-sales-app-performance-monitor.md
 create mode 100644 docs/announcements/pt/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
 create mode 100644 docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md
 create mode 100644 docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md
 create mode 100644 docs/announcements/pt/performance-monitor.md
 create mode 100644 docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
 create mode 100644 docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
 create mode 100644 docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
 create mode 100644 docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
 create mode 100644 docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md
 create mode 100644 docs/announcements/pt/site-editor-fixed-content-loss-issue.md
 create mode 100644 docs/announcements/pt/the-insights-dashboard-will-be-discontinued.md
 create mode 100644 docs/announcements/pt/the-offer-management-module-will-be-discontinued.md
 create mode 100644 docs/announcements/pt/troubleshooting-guides-your-new-vtex-self-service-experience.md
 create mode 100644 docs/announcements/pt/update-of-the-external-privacy-notice.md
 create mode 100644 docs/announcements/pt/vtex-insurance-discontinuity.md
 create mode 100644 docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
 create mode 100644 docs/announcements/pt/vtex-sales-app-will-no-longer-be-available-for-windows.md
 create mode 100644 docs/announcements/pt/web-page-performance-deprecation.md
 create mode 100644 docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
 create mode 100644 docs/faq/en/vtex-support-emea.md
 create mode 100644 docs/faq/en/why-are-my-store-images-being-displayed-in-poor-quality.md
 create mode 100644 docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
 create mode 100644 docs/faq/es/vtex-support-emea.md
 create mode 100644 docs/faq/es/why-are-my-store-images-being-displayed-in-poor-quality.md
 create mode 100644 docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
 create mode 100644 docs/faq/pt/vtex-support-emea.md
 create mode 100644 docs/faq/pt/why-are-my-store-images-being-displayed-in-poor-quality.md
 create mode 100644 docs/known-issues/en/403-error-for-all-urls-containing-develop.md
 create mode 100644 docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
 create mode 100644 docs/known-issues/en/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
 create mode 100644 docs/known-issues/en/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
 create mode 100644 docs/known-issues/en/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
 create mode 100644 docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
 create mode 100644 docs/known-issues/en/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
 create mode 100644 docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md
 create mode 100644 docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
 create mode 100644 docs/known-issues/en/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
 create mode 100644 docs/known-issues/en/admin-review-global-search.md
 create mode 100644 docs/known-issues/en/admin-timeout.md
 create mode 100644 docs/known-issues/en/adyen-3ds2-double-request-generates-payment-authorization-denial.md
 create mode 100644 docs/known-issues/en/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
 create mode 100644 docs/known-issues/en/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
 create mode 100644 docs/known-issues/en/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
 create mode 100644 docs/known-issues/en/app-settings-are-not-erased-when-you-delete-the-app.md
 create mode 100644 docs/known-issues/en/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
 create mode 100644 docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
 create mode 100644 docs/known-issues/en/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
 create mode 100644 docs/known-issues/en/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
 create mode 100644 docs/known-issues/en/attribute-melishippingmode-not-being-updated-in-meli-integration.md
 create mode 100644 docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md
 create mode 100644 docs/known-issues/en/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
 create mode 100644 docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
 create mode 100644 docs/known-issues/en/automatic-payment-settlement-incorrectly-setup.md
 create mode 100644 docs/known-issues/en/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
 create mode 100644 docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
 create mode 100644 docs/known-issues/en/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
 create mode 100644 docs/known-issues/en/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
 create mode 100644 docs/known-issues/en/b2b-impersonated-data-is-not-removed-after-logging-out.md
 create mode 100644 docs/known-issues/en/b2b-orders-history-doesnt-work-in-the-website-domain.md
 create mode 100644 docs/known-issues/en/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
 create mode 100644 docs/known-issues/en/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
 create mode 100644 docs/known-issues/en/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
 create mode 100644 docs/known-issues/en/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
 create mode 100644 docs/known-issues/en/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
 create mode 100644 docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md
 create mode 100644 docs/known-issues/en/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
 create mode 100644 docs/known-issues/en/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
 create mode 100644 docs/known-issues/en/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
 create mode 100644 docs/known-issues/en/boolean-filter-on-form-application-does-not-work-properly.md
 create mode 100644 docs/known-issues/en/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
 create mode 100644 docs/known-issues/en/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
 create mode 100644 docs/known-issues/en/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
 create mode 100644 docs/known-issues/en/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
 create mode 100644 docs/known-issues/en/calculation-issue-in-comissionamount.md
 create mode 100644 docs/known-issues/en/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
 create mode 100644 docs/known-issues/en/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
 create mode 100644 docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
 create mode 100644 docs/known-issues/en/canonical-tags-are-not-applied-after-3rd-category-level.md
 create mode 100644 docs/known-issues/en/cant-edit-the-name-of-the-styles-template.md
 create mode 100644 docs/known-issues/en/card-brands-incorrectly-processed-as-visa.md
 create mode 100644 docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
 create mode 100644 docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
 create mode 100644 docs/known-issues/en/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
 create mode 100644 docs/known-issues/en/cart-itens-are-kept-in-orders-with-total-value-zero.md
 create mode 100644 docs/known-issues/en/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
 create mode 100644 docs/known-issues/en/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
 create mode 100644 docs/known-issues/en/cashback-promotions-do-not-consider-items-removed-from-orders.md
 create mode 100644 docs/known-issues/en/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
 create mode 100644 docs/known-issues/en/catalog-export-cannot-handle-t-and-s-characters.md
 create mode 100644 docs/known-issues/en/catalog-export-for-attachment-cuts-50-characters.md
 create mode 100644 docs/known-issues/en/catalog-filters-timeout.md
 create mode 100644 docs/known-issues/en/catalog-graphql-categoryinputtranslation-not-working.md
 create mode 100644 docs/known-issues/en/catalog-indexer-generating-invalid-translation-documents.md
 create mode 100644 docs/known-issues/en/catalog-integration-xml-fiscal-code-field-not-rendering.md
 create mode 100644 docs/known-issues/en/catalog-search-api-limited-to-2500-results.md
 create mode 100644 docs/known-issues/en/catalog-translations-not-reflecting-on-the-frontend.md
 create mode 100644 docs/known-issues/en/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
 create mode 100644 docs/known-issues/en/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
 create mode 100644 docs/known-issues/en/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
 create mode 100644 docs/known-issues/en/changing-accessories-is-not-triggering-indexation.md
 create mode 100644 docs/known-issues/en/checkout-allows-to-add-2-different-addresses-for-delivery.md
 create mode 100644 docs/known-issues/en/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
 create mode 100644 docs/known-issues/en/checkout-does-not-support-encoding-assembly-options-names.md
 create mode 100644 docs/known-issues/en/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
 create mode 100644 docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
 create mode 100644 docs/known-issues/en/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
 create mode 100644 docs/known-issues/en/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
 create mode 100644 docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
 create mode 100644 docs/known-issues/en/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
 create mode 100644 docs/known-issues/en/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
 create mode 100644 docs/known-issues/en/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
 create mode 100644 docs/known-issues/en/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
 create mode 100644 docs/known-issues/en/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
 create mode 100644 docs/known-issues/en/cms-settings-role-not-working-as-expected.md
 create mode 100644 docs/known-issues/en/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
 create mode 100644 docs/known-issues/en/collections-dont-open-on-subaccounts.md
 create mode 100644 docs/known-issues/en/collections-export-only-shows-1st-sku-of-inactive-product.md
 create mode 100644 docs/known-issues/en/collections-named-with-special-characters-cannot-be-exported.md
 create mode 100644 docs/known-issues/en/collections-page-in-organization-details-shows-only-20-collections.md
 create mode 100644 docs/known-issues/en/collections-trigger-not-working-as-expected-on-progressive-discounts.md
 create mode 100644 docs/known-issues/en/components-in-a-kit-with-the-same-price.md
 create mode 100644 docs/known-issues/en/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
 create mode 100644 docs/known-issues/en/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
 create mode 100644 docs/known-issues/en/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
 create mode 100644 docs/known-issues/en/country-field-as-null-in-invoicedata.md
 create mode 100644 docs/known-issues/en/coupons-created-as-archived-temporarrily.md
 create mode 100644 docs/known-issues/en/create-product-api-doesnt-send-nulls-as-release-date-values.md
 create mode 100644 docs/known-issues/en/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
 create mode 100644 docs/known-issues/en/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
 create mode 100644 docs/known-issues/en/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
 create mode 100644 docs/known-issues/en/criteria-composition-is-not-returned-on-the-explained-search-ui.md
 create mode 100644 docs/known-issues/en/currency-symbol-does-not-follow-admin-language.md
 create mode 100644 docs/known-issues/en/custom-attribute-mapper-mercado-livre.md
 create mode 100644 docs/known-issues/en/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
 create mode 100644 docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
 create mode 100644 docs/known-issues/en/deactivated-payment-system-rendering-at-checkout.md
 create mode 100644 docs/known-issues/en/deadlocked-error-when-using-catalog-apis.md
 create mode 100644 docs/known-issues/en/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
 create mode 100644 docs/known-issues/en/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
 create mode 100644 docs/known-issues/en/delivery-split-with-lean-shipping-offering-invalid-sla.md
 create mode 100644 docs/known-issues/en/departments-name-not-loading-on-seller-management-commissions-ui.md
 create mode 100644 docs/known-issues/en/difference-in-prices-between-pdp-plp-and-checkout-cart.md
 create mode 100644 docs/known-issues/en/differences-between-specification-value-on-apis-and-portal.md
 create mode 100644 docs/known-issues/en/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
 create mode 100644 docs/known-issues/en/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
 create mode 100644 docs/known-issues/en/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
 create mode 100644 docs/known-issues/en/duplicated-organizations-in-modal-to-switch-between-organizations.md
 create mode 100644 docs/known-issues/en/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
 create mode 100644 docs/known-issues/en/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
 create mode 100644 docs/known-issues/en/email-not-autofilling-for-new-buyers-after-logging-in.md
 create mode 100644 docs/known-issues/en/email-not-autofilling-for-new-users-on-checkoutui.md
 create mode 100644 docs/known-issues/en/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
 create mode 100644 docs/known-issues/en/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
 create mode 100644 docs/known-issues/en/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
 create mode 100644 docs/known-issues/en/error-cancelling-customer-credit-invoices.md
 create mode 100644 docs/known-issues/en/error-closing-customer-credit-account.md
 create mode 100644 docs/known-issues/en/error-exporting-entity-with-too-many-documents.md
 create mode 100644 docs/known-issues/en/error-exporting-prices-with-metadata.md
 create mode 100644 docs/known-issues/en/error-in-custom-payments-creation.md
 create mode 100644 docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
 create mode 100644 docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md
 create mode 100644 docs/known-issues/en/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
 create mode 100644 docs/known-issues/en/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
 create mode 100644 docs/known-issues/en/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
 create mode 100644 docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
 create mode 100644 docs/known-issues/en/error-on-duplicate-payment-method.md
 create mode 100644 docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
 create mode 100644 docs/known-issues/en/error-when-changing-an-index-if-the-fields-are-identical.md
 create mode 100644 docs/known-issues/en/error-when-publishing-dynamic-storage-data-entity.md
 create mode 100644 docs/known-issues/en/error-when-trying-to-publish-or-link-an-app.md
 create mode 100644 docs/known-issues/en/exclude-products-from-collection-not-working.md
 create mode 100644 docs/known-issues/en/expired-temporary-redirects-not-pointing-back-to-old-route.md
 create mode 100644 docs/known-issues/en/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
 create mode 100644 docs/known-issues/en/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
 create mode 100644 docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
 create mode 100644 docs/known-issues/en/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
 create mode 100644 docs/known-issues/en/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
 create mode 100644 docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
 create mode 100644 docs/known-issues/en/faststore-cart-merges-assembly-line-items.md
 create mode 100644 docs/known-issues/en/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
 create mode 100644 docs/known-issues/en/faststore-search-api-considering-fuzzy-as-auto-as-default.md
 create mode 100644 docs/known-issues/en/faststore-v1-dont-return-seo-information-on-graphql-query.md
 create mode 100644 docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
 create mode 100644 docs/known-issues/en/filters-by-sku-specifications-not-considering-regionalized-availability.md
 create mode 100644 docs/known-issues/en/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
 create mode 100644 docs/known-issues/en/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
 create mode 100644 docs/known-issues/en/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
 create mode 100644 docs/known-issues/en/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
 create mode 100644 docs/known-issues/en/first-subscription-cycle-is-skipped.md
 create mode 100644 docs/known-issues/en/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
 create mode 100644 docs/known-issues/en/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
 create mode 100644 docs/known-issues/en/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
 create mode 100644 docs/known-issues/en/gift-card-creation-error-via-admin.md
 create mode 100644 docs/known-issues/en/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
 create mode 100644 docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
 create mode 100644 docs/known-issues/en/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
 create mode 100644 docs/known-issues/en/headless-cms-ignores-array-validation-settings.md
 create mode 100644 docs/known-issues/en/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
 create mode 100644 docs/known-issues/en/impersonation-is-ignored-after-one-purchase-is-completed.md
 create mode 100644 docs/known-issues/en/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
 create mode 100644 docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
 create mode 100644 docs/known-issues/en/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
 create mode 100644 docs/known-issues/en/incomplete-transactions-appearing-with-brazilian-currency.md
 create mode 100644 docs/known-issues/en/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
 create mode 100644 docs/known-issues/en/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
 create mode 100644 docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
 create mode 100644 docs/known-issues/en/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
 create mode 100644 docs/known-issues/en/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
 create mode 100644 docs/known-issues/en/infocard-mobile-images-wont-apply.md
 create mode 100644 docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
 create mode 100644 docs/known-issues/en/installment-options-not-updating-automatically-on-pdpplp.md
 create mode 100644 docs/known-issues/en/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
 create mode 100644 docs/known-issues/en/intelligent-search-not-capturing-sales-events-for-faststore.md
 create mode 100644 docs/known-issues/en/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
 create mode 100644 docs/known-issues/en/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
 create mode 100644 docs/known-issues/en/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
 create mode 100644 docs/known-issues/en/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
 create mode 100644 docs/known-issues/en/intermitent-site-editor-content-loss.md
 create mode 100644 docs/known-issues/en/internalsearcherror-timeouts-on-portal.md
 create mode 100644 docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
 create mode 100644 docs/known-issues/en/inventory-notifications-to-indexer-are-cached.md
 create mode 100644 docs/known-issues/en/invisible-characters-in-category-names-cause-page-not-found-errors.md
 create mode 100644 docs/known-issues/en/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
 create mode 100644 docs/known-issues/en/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
 create mode 100644 docs/known-issues/en/issues-with-billingaddress-leading-to-transaction-cancellations.md
 create mode 100644 docs/known-issues/en/issues-with-my-account-links.md
 create mode 100644 docs/known-issues/en/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
 create mode 100644 docs/known-issues/en/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
 create mode 100644 docs/known-issues/en/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
 create mode 100644 docs/known-issues/en/item-available-when-customer-location-is-not-defined-with-no-stock.md
 create mode 100644 docs/known-issues/en/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
 create mode 100644 docs/known-issues/en/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
 create mode 100644 docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
 create mode 100644 docs/known-issues/en/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
 create mode 100644 docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md
 create mode 100644 docs/known-issues/en/legacy-cmss-banner-custom-element-not-working.md
 create mode 100644 docs/known-issues/en/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
 create mode 100644 docs/known-issues/en/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
 create mode 100644 docs/known-issues/en/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
 create mode 100644 docs/known-issues/en/login-preference-with-password-cannot-be-undone-in-admin.md
 create mode 100644 docs/known-issues/en/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
 create mode 100644 docs/known-issues/en/magazine-luiza-some-skus-do-not-update-price.md
 create mode 100644 docs/known-issues/en/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
 create mode 100644 docs/known-issues/en/mandatory-service-working-as-optional.md
 create mode 100644 docs/known-issues/en/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
 create mode 100644 docs/known-issues/en/marketingtags-with-null-value-when-campaign-audience-is-matched.md
 create mode 100644 docs/known-issues/en/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
 create mode 100644 docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
 create mode 100644 docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
 create mode 100644 docs/known-issues/en/mastercard-credit-card-transactions-are-being-processed-as-visa.md
 create mode 100644 docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md
 create mode 100644 docs/known-issues/en/matcher-converting-height-width-weight-and-length-to-01.md
 create mode 100644 docs/known-issues/en/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
 create mode 100644 docs/known-issues/en/max-shipping-discount-not-updating-pricetags.md
 create mode 100644 docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
 create mode 100644 docs/known-issues/en/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
 create mode 100644 docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
 create mode 100644 docs/known-issues/en/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
 create mode 100644 docs/known-issues/en/meli-bridge-orders-menu-not-showing-the-orderid-information.md
 create mode 100644 docs/known-issues/en/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
 create mode 100644 docs/known-issues/en/meli-freight-quotation-for-multiple-officialstoreids.md
 create mode 100644 docs/known-issues/en/meli-full-orders-not-creating-invoice-in-vtex.md
 create mode 100644 docs/known-issues/en/meli-incorrect-value-when-client-has-coupon-on-meli.md
 create mode 100644 docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
 create mode 100644 docs/known-issues/en/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
 create mode 100644 docs/known-issues/en/meli-mapper-incorrectly-sending-product-specification-as-variation.md
 create mode 100644 docs/known-issues/en/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
 create mode 100644 docs/known-issues/en/meli-size-chart-not-working-for-sizes-with-letters.md
 create mode 100644 docs/known-issues/en/meli-sizechart-issue-attribute-not-valid.md
 create mode 100644 docs/known-issues/en/meli-update-stockprice-issue.md
 create mode 100644 docs/known-issues/en/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
 create mode 100644 docs/known-issues/en/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
 create mode 100644 docs/known-issues/en/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
 create mode 100644 docs/known-issues/en/mercado-livre-remove-underreview-validation-in-update-sku.md
 create mode 100644 docs/known-issues/en/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
 create mode 100644 docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md
 create mode 100644 docs/known-issues/en/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
 create mode 100644 docs/known-issues/en/messages-app-taking-too-long-to-return-the-informations.md
 create mode 100644 docs/known-issues/en/metatagdescription-field-cannot-be-deleted-through-admin.md
 create mode 100644 docs/known-issues/en/minicart-coupon-error-messages-only-appear-after-a-second-try.md
 create mode 100644 docs/known-issues/en/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
 create mode 100644 docs/known-issues/en/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
 create mode 100644 docs/known-issues/en/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
 create mode 100644 docs/known-issues/en/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
 create mode 100644 docs/known-issues/en/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
 create mode 100644 docs/known-issues/en/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
 create mode 100644 docs/known-issues/en/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
 create mode 100644 docs/known-issues/en/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
 create mode 100644 docs/known-issues/en/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
 create mode 100644 docs/known-issues/en/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
 create mode 100644 docs/known-issues/en/openclose-modal-hook-affects-all-modals-on-the-page.md
 create mode 100644 docs/known-issues/en/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
 create mode 100644 docs/known-issues/en/order-authorization-lessthan-100-goes-with-the-flow.md
 create mode 100644 docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
 create mode 100644 docs/known-issues/en/order-not-notified-carrier-leaves-label-barcode-incomplete.md
 create mode 100644 docs/known-issues/en/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
 create mode 100644 docs/known-issues/en/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
 create mode 100644 docs/known-issues/en/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
 create mode 100644 docs/known-issues/en/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
 create mode 100644 docs/known-issues/en/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
 create mode 100644 docs/known-issues/en/orderform-not-updating-after-order-is-placed.md
 create mode 100644 docs/known-issues/en/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
 create mode 100644 docs/known-issues/en/orders-with-asterisks-in-the-address-and-profile.md
 create mode 100644 docs/known-issues/en/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
 create mode 100644 docs/known-issues/en/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
 create mode 100644 docs/known-issues/en/outdated-url-on-the-update-binding-ui.md
 create mode 100644 docs/known-issues/en/pageview-is-triggered-twice-when-accessing-my-account.md
 create mode 100644 docs/known-issues/en/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
 create mode 100644 docs/known-issues/en/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
 create mode 100644 docs/known-issues/en/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
 create mode 100644 docs/known-issues/en/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
 create mode 100644 docs/known-issues/en/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
 create mode 100644 docs/known-issues/en/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
 create mode 100644 docs/known-issues/en/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
 create mode 100644 docs/known-issues/en/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
 create mode 100644 docs/known-issues/en/pickup-points-not-indexed-in-master-data.md
 create mode 100644 docs/known-issues/en/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
 create mode 100644 docs/known-issues/en/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
 create mode 100644 docs/known-issues/en/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
 create mode 100644 docs/known-issues/en/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
 create mode 100644 docs/known-issues/en/presales-of-the-legacy-cms-collection-is-not-working.md
 create mode 100644 docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
 create mode 100644 docs/known-issues/en/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
 create mode 100644 docs/known-issues/en/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
 create mode 100644 docs/known-issues/en/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
 create mode 100644 docs/known-issues/en/price-updates-with-cache-on-end-applications.md
 create mode 100644 docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md
 create mode 100644 docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
 create mode 100644 docs/known-issues/en/problem-with-phone-validation-on-mobile-devices.md
 create mode 100644 docs/known-issues/en/product-availability-display-delayed-when-using-multiple-sales-channels.md
 create mode 100644 docs/known-issues/en/product-comissioning-inconsistent-cache.md
 create mode 100644 docs/known-issues/en/product-image-on-admin-changes-with-more-than-70-skus.md
 create mode 100644 docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
 create mode 100644 docs/known-issues/en/product-page-sessions-not-working.md
 create mode 100644 docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md
 create mode 100644 docs/known-issues/en/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
 create mode 100644 docs/known-issues/en/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
 create mode 100644 docs/known-issues/en/products-showing-flag-and-discount-after-promotion-ended.md
 create mode 100644 docs/known-issues/en/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
 create mode 100644 docs/known-issues/en/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
 create mode 100644 docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
 create mode 100644 docs/known-issues/en/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
 create mode 100644 docs/known-issues/en/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
 create mode 100644 docs/known-issues/en/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
 create mode 100644 docs/known-issues/en/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
 create mode 100644 docs/known-issues/en/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
 create mode 100644 docs/known-issues/en/promotions-microrounding-divergence.md
 create mode 100644 docs/known-issues/en/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
 create mode 100644 docs/known-issues/en/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
 create mode 100644 docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
 create mode 100644 docs/known-issues/en/quantity-selector-wont-let-me-change-the-value-by-typing.md
 create mode 100644 docs/known-issues/en/received-skus-filter-do-not-work-with-special-characters.md
 create mode 100644 docs/known-issues/en/received-skus-review-tab-missing-products.md
 create mode 100644 docs/known-issues/en/redirects-are-being-counted-multiple-times.md
 create mode 100644 docs/known-issues/en/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
 create mode 100644 docs/known-issues/en/refid-behavior-not-consistent-between-api-and-ui.md
 create mode 100644 docs/known-issues/en/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
 create mode 100644 docs/known-issues/en/region-api-returns-seller-list-due-to-cache.md
 create mode 100644 docs/known-issues/en/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
 create mode 100644 docs/known-issues/en/replacing-orders-with-different-sales-channel.md
 create mode 100644 docs/known-issues/en/request-routing-is-inconsistent-when-running-ab-tests.md
 create mode 100644 docs/known-issues/en/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
 create mode 100644 docs/known-issues/en/rewriter-is-not-receiving-url-updates.md
 create mode 100644 docs/known-issues/en/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
 create mode 100644 docs/known-issues/en/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
 create mode 100644 docs/known-issues/en/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
 create mode 100644 docs/known-issues/en/schema-validation-failing-for-custom-types-in-headless-cms.md
 create mode 100644 docs/known-issues/en/scroll-issue-when-zooming-after-search-page-render.md
 create mode 100644 docs/known-issues/en/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
 create mode 100644 docs/known-issues/en/search-analytics-duplicated-events.md
 create mode 100644 docs/known-issues/en/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
 create mode 100644 docs/known-issues/en/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
 create mode 100644 docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md
 create mode 100644 docs/known-issues/en/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
 create mode 100644 docs/known-issues/en/search-resolver-applying-messages-translations-over-already-translated-content.md
 create mode 100644 docs/known-issues/en/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
 create mode 100644 docs/known-issues/en/seller-commission-updates-does-not-index-binded-skus.md
 create mode 100644 docs/known-issues/en/seller-group-creation-does-not-add-selected-sellers.md
 create mode 100644 docs/known-issues/en/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
 create mode 100644 docs/known-issues/en/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
 create mode 100644 docs/known-issues/en/sellers-order-invoiced-with-problem-in-the-payment-capture.md
 create mode 100644 docs/known-issues/en/service-type-name-field-wrongly-returned-via-api.md
 create mode 100644 docs/known-issues/en/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
 create mode 100644 docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
 create mode 100644 docs/known-issues/en/shipping-options-gets-frozen-when-trying-to-select-an-option.md
 create mode 100644 docs/known-issues/en/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
 create mode 100644 docs/known-issues/en/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
 create mode 100644 docs/known-issues/en/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
 create mode 100644 docs/known-issues/en/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
 create mode 100644 docs/known-issues/en/similar-products-ui-brokes-with-too-many-products.md
 create mode 100644 docs/known-issues/en/single-installment-payment-condition-does-not-appear-at-chekout.md
 create mode 100644 docs/known-issues/en/site-editor-doesnt-allow-changes-on-the-conditional-template.md
 create mode 100644 docs/known-issues/en/sitemap-isnt-being-generatedupdated.md
 create mode 100644 docs/known-issues/en/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
 create mode 100644 docs/known-issues/en/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
 create mode 100644 docs/known-issues/en/sku-file-update-does-not-update-v-version-tags.md
 create mode 100644 docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md
 create mode 100644 docs/known-issues/en/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
 create mode 100644 docs/known-issues/en/sku-selector-with-multilpe-contexts.md
 create mode 100644 docs/known-issues/en/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
 create mode 100644 docs/known-issues/en/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
 create mode 100644 docs/known-issues/en/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
 create mode 100644 docs/known-issues/en/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
 create mode 100644 docs/known-issues/en/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
 create mode 100644 docs/known-issues/en/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
 create mode 100644 docs/known-issues/en/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
 create mode 100644 docs/known-issues/en/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
 create mode 100644 docs/known-issues/en/some-unexpected-behavior-in-masterdata.md
 create mode 100644 docs/known-issues/en/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
 create mode 100644 docs/known-issues/en/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
 create mode 100644 docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
 create mode 100644 docs/known-issues/en/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
 create mode 100644 docs/known-issues/en/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
 create mode 100644 docs/known-issues/en/specifications-multiplied-on-catalog.md
 create mode 100644 docs/known-issues/en/status-on-transactions-list-doesnt-match-actual-state.md
 create mode 100644 docs/known-issues/en/storefront-permissions-considers-inactive-organizations.md
 create mode 100644 docs/known-issues/en/subscription-event-history-out-of-order.md
 create mode 100644 docs/known-issues/en/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
 create mode 100644 docs/known-issues/en/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
 create mode 100644 docs/known-issues/en/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
 create mode 100644 docs/known-issues/en/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
 create mode 100644 docs/known-issues/en/synonyms-import-presenting-success-even-for-failed-actions.md
 create mode 100644 docs/known-issues/en/synonyms-not-shown-in-the-explained-search.md
 create mode 100644 docs/known-issues/en/tags-wont-sometimes-appear-on-list-format-plp-view.md
 create mode 100644 docs/known-issues/en/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
 create mode 100644 docs/known-issues/en/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
 create mode 100644 docs/known-issues/en/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
 create mode 100644 docs/known-issues/en/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
 create mode 100644 docs/known-issues/en/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
 create mode 100644 docs/known-issues/en/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
 create mode 100644 docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
 create mode 100644 docs/known-issues/en/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/en/text-in-infocard-is-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/en/text-in-store-login-are-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/en/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
 create mode 100644 docs/known-issues/en/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
 create mode 100644 docs/known-issues/en/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
 create mode 100644 docs/known-issues/en/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
 create mode 100644 docs/known-issues/en/timeout-generating-internal-application-keys.md
 create mode 100644 docs/known-issues/en/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
 create mode 100644 docs/known-issues/en/total-reservation-item-with-negative-value-in-inventory-ui.md
 create mode 100644 docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md
 create mode 100644 docs/known-issues/en/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
 create mode 100644 docs/known-issues/en/transaction-stuck-in-status-approved-with-payment-canceled.md
 create mode 100644 docs/known-issues/en/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
 create mode 100644 docs/known-issues/en/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
 create mode 100644 docs/known-issues/en/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
 create mode 100644 docs/known-issues/en/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
 create mode 100644 docs/known-issues/en/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
 create mode 100644 docs/known-issues/en/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
 create mode 100644 docs/known-issues/en/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
 create mode 100644 docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md
 create mode 100644 docs/known-issues/en/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
 create mode 100644 docs/known-issues/en/unable-to-log-in-through-the-google-app-on-ios.md
 create mode 100644 docs/known-issues/en/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
 create mode 100644 docs/known-issues/en/unavailable-products-pdp-are-still-being-returned.md
 create mode 100644 docs/known-issues/en/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
 create mode 100644 docs/known-issues/en/unexpected-reload-happening-when-registeringupdating-a-product.md
 create mode 100644 docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md
 create mode 100644 docs/known-issues/en/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
 create mode 100644 docs/known-issues/en/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
 create mode 100644 docs/known-issues/en/upload-file-not-working-on-adminportalsitesdefaultcode.md
 create mode 100644 docs/known-issues/en/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
 create mode 100644 docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
 create mode 100644 docs/known-issues/en/users-cant-access-gift-card-admin-looping-page.md
 create mode 100644 docs/known-issues/en/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
 create mode 100644 docs/known-issues/en/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
 create mode 100644 docs/known-issues/en/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
 create mode 100644 docs/known-issues/en/validatecartmutation-failing-when-large-payload.md
 create mode 100644 docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md
 create mode 100644 docs/known-issues/en/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
 create mode 100644 docs/known-issues/en/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
 create mode 100644 docs/known-issues/en/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
 create mode 100644 docs/known-issues/en/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
 create mode 100644 docs/known-issues/en/webops-app-is-not-fully-integrated-with-headless-cms.md
 create mode 100644 docs/known-issues/en/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
 create mode 100644 docs/known-issues/en/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
 create mode 100644 docs/known-issues/en/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
 create mode 100644 docs/known-issues/en/wrong-translation-for-different-fields-under-the-same-original-value.md
 create mode 100644 docs/known-issues/en/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
 create mode 100644 docs/known-issues/en/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
 create mode 100644 docs/known-issues/en/xml-installment-currency-does-not-apply.md
 create mode 100644 docs/known-issues/en/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
 create mode 100644 docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
 create mode 100644 docs/known-issues/es/403-error-for-all-urls-containing-develop.md
 create mode 100644 docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
 create mode 100644 docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
 create mode 100644 docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
 create mode 100644 docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
 create mode 100644 docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
 create mode 100644 docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
 create mode 100644 docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
 create mode 100644 docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
 create mode 100644 docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
 create mode 100644 docs/known-issues/es/admin-review-global-search.md
 create mode 100644 docs/known-issues/es/admin-timeout.md
 create mode 100644 docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md
 create mode 100644 docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
 create mode 100644 docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
 create mode 100644 docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
 create mode 100644 docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md
 create mode 100644 docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
 create mode 100644 docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
 create mode 100644 docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
 create mode 100644 docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
 create mode 100644 docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md
 create mode 100644 docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
 create mode 100644 docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
 create mode 100644 docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
 create mode 100644 docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md
 create mode 100644 docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
 create mode 100644 docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
 create mode 100644 docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
 create mode 100644 docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
 create mode 100644 docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md
 create mode 100644 docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md
 create mode 100644 docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
 create mode 100644 docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
 create mode 100644 docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
 create mode 100644 docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
 create mode 100644 docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
 create mode 100644 docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
 create mode 100644 docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
 create mode 100644 docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
 create mode 100644 docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
 create mode 100644 docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md
 create mode 100644 docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
 create mode 100644 docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
 create mode 100644 docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
 create mode 100644 docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
 create mode 100644 docs/known-issues/es/calculation-issue-in-comissionamount.md
 create mode 100644 docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
 create mode 100644 docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
 create mode 100644 docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
 create mode 100644 docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md
 create mode 100644 docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md
 create mode 100644 docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md
 create mode 100644 docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
 create mode 100644 docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
 create mode 100644 docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
 create mode 100644 docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md
 create mode 100644 docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
 create mode 100644 docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
 create mode 100644 docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md
 create mode 100644 docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
 create mode 100644 docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md
 create mode 100644 docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md
 create mode 100644 docs/known-issues/es/catalog-filters-timeout.md
 create mode 100644 docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md
 create mode 100644 docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md
 create mode 100644 docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md
 create mode 100644 docs/known-issues/es/catalog-search-api-limited-to-2500-results.md
 create mode 100644 docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md
 create mode 100644 docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
 create mode 100644 docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
 create mode 100644 docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
 create mode 100644 docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md
 create mode 100644 docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md
 create mode 100644 docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
 create mode 100644 docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md
 create mode 100644 docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
 create mode 100644 docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
 create mode 100644 docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
 create mode 100644 docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
 create mode 100644 docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
 create mode 100644 docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
 create mode 100644 docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
 create mode 100644 docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
 create mode 100644 docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
 create mode 100644 docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
 create mode 100644 docs/known-issues/es/cms-settings-role-not-working-as-expected.md
 create mode 100644 docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
 create mode 100644 docs/known-issues/es/collections-dont-open-on-subaccounts.md
 create mode 100644 docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md
 create mode 100644 docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md
 create mode 100644 docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md
 create mode 100644 docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md
 create mode 100644 docs/known-issues/es/components-in-a-kit-with-the-same-price.md
 create mode 100644 docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
 create mode 100644 docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
 create mode 100644 docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
 create mode 100644 docs/known-issues/es/country-field-as-null-in-invoicedata.md
 create mode 100644 docs/known-issues/es/coupons-created-as-archived-temporarrily.md
 create mode 100644 docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md
 create mode 100644 docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
 create mode 100644 docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
 create mode 100644 docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
 create mode 100644 docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md
 create mode 100644 docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md
 create mode 100644 docs/known-issues/es/custom-attribute-mapper-mercado-livre.md
 create mode 100644 docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
 create mode 100644 docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
 create mode 100644 docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md
 create mode 100644 docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md
 create mode 100644 docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
 create mode 100644 docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
 create mode 100644 docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md
 create mode 100644 docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md
 create mode 100644 docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md
 create mode 100644 docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md
 create mode 100644 docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
 create mode 100644 docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
 create mode 100644 docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
 create mode 100644 docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md
 create mode 100644 docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
 create mode 100644 docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
 create mode 100644 docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md
 create mode 100644 docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md
 create mode 100644 docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
 create mode 100644 docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
 create mode 100644 docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
 create mode 100644 docs/known-issues/es/error-cancelling-customer-credit-invoices.md
 create mode 100644 docs/known-issues/es/error-closing-customer-credit-account.md
 create mode 100644 docs/known-issues/es/error-exporting-entity-with-too-many-documents.md
 create mode 100644 docs/known-issues/es/error-exporting-prices-with-metadata.md
 create mode 100644 docs/known-issues/es/error-in-custom-payments-creation.md
 create mode 100644 docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
 create mode 100644 docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
 create mode 100644 docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
 create mode 100644 docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
 create mode 100644 docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
 create mode 100644 docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
 create mode 100644 docs/known-issues/es/error-on-duplicate-payment-method.md
 create mode 100644 docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
 create mode 100644 docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md
 create mode 100644 docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md
 create mode 100644 docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md
 create mode 100644 docs/known-issues/es/exclude-products-from-collection-not-working.md
 create mode 100644 docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md
 create mode 100644 docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
 create mode 100644 docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
 create mode 100644 docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
 create mode 100644 docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
 create mode 100644 docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
 create mode 100644 docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
 create mode 100644 docs/known-issues/es/faststore-cart-merges-assembly-line-items.md
 create mode 100644 docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
 create mode 100644 docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md
 create mode 100644 docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md
 create mode 100644 docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
 create mode 100644 docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md
 create mode 100644 docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
 create mode 100644 docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
 create mode 100644 docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
 create mode 100644 docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
 create mode 100644 docs/known-issues/es/first-subscription-cycle-is-skipped.md
 create mode 100644 docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
 create mode 100644 docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
 create mode 100644 docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
 create mode 100644 docs/known-issues/es/gift-card-creation-error-via-admin.md
 create mode 100644 docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
 create mode 100644 docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
 create mode 100644 docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
 create mode 100644 docs/known-issues/es/headless-cms-ignores-array-validation-settings.md
 create mode 100644 docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
 create mode 100644 docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md
 create mode 100644 docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
 create mode 100644 docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
 create mode 100644 docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
 create mode 100644 docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md
 create mode 100644 docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
 create mode 100644 docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
 create mode 100644 docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
 create mode 100644 docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
 create mode 100644 docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
 create mode 100644 docs/known-issues/es/infocard-mobile-images-wont-apply.md
 create mode 100644 docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
 create mode 100644 docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md
 create mode 100644 docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
 create mode 100644 docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md
 create mode 100644 docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
 create mode 100644 docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
 create mode 100644 docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
 create mode 100644 docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
 create mode 100644 docs/known-issues/es/intermitent-site-editor-content-loss.md
 create mode 100644 docs/known-issues/es/internalsearcherror-timeouts-on-portal.md
 create mode 100644 docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
 create mode 100644 docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md
 create mode 100644 docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
 create mode 100644 docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
 create mode 100644 docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
 create mode 100644 docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md
 create mode 100644 docs/known-issues/es/issues-with-my-account-links.md
 create mode 100644 docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
 create mode 100644 docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
 create mode 100644 docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
 create mode 100644 docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md
 create mode 100644 docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
 create mode 100644 docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
 create mode 100644 docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
 create mode 100644 docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
 create mode 100644 docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
 create mode 100644 docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md
 create mode 100644 docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
 create mode 100644 docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
 create mode 100644 docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
 create mode 100644 docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md
 create mode 100644 docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
 create mode 100644 docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md
 create mode 100644 docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
 create mode 100644 docs/known-issues/es/mandatory-service-working-as-optional.md
 create mode 100644 docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
 create mode 100644 docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md
 create mode 100644 docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
 create mode 100644 docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
 create mode 100644 docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
 create mode 100644 docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md
 create mode 100644 docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
 create mode 100644 docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md
 create mode 100644 docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
 create mode 100644 docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md
 create mode 100644 docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
 create mode 100644 docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
 create mode 100644 docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
 create mode 100644 docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
 create mode 100644 docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md
 create mode 100644 docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
 create mode 100644 docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md
 create mode 100644 docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md
 create mode 100644 docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md
 create mode 100644 docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
 create mode 100644 docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
 create mode 100644 docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md
 create mode 100644 docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
 create mode 100644 docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md
 create mode 100644 docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md
 create mode 100644 docs/known-issues/es/meli-update-stockprice-issue.md
 create mode 100644 docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
 create mode 100644 docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
 create mode 100644 docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
 create mode 100644 docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md
 create mode 100644 docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
 create mode 100644 docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
 create mode 100644 docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
 create mode 100644 docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md
 create mode 100644 docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md
 create mode 100644 docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md
 create mode 100644 docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
 create mode 100644 docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
 create mode 100644 docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
 create mode 100644 docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
 create mode 100644 docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
 create mode 100644 docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
 create mode 100644 docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
 create mode 100644 docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
 create mode 100644 docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
 create mode 100644 docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
 create mode 100644 docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md
 create mode 100644 docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
 create mode 100644 docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md
 create mode 100644 docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
 create mode 100644 docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md
 create mode 100644 docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
 create mode 100644 docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
 create mode 100644 docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
 create mode 100644 docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
 create mode 100644 docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
 create mode 100644 docs/known-issues/es/orderform-not-updating-after-order-is-placed.md
 create mode 100644 docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
 create mode 100644 docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md
 create mode 100644 docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
 create mode 100644 docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
 create mode 100644 docs/known-issues/es/outdated-url-on-the-update-binding-ui.md
 create mode 100644 docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md
 create mode 100644 docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
 create mode 100644 docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
 create mode 100644 docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
 create mode 100644 docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
 create mode 100644 docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
 create mode 100644 docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
 create mode 100644 docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
 create mode 100644 docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
 create mode 100644 docs/known-issues/es/pickup-points-not-indexed-in-master-data.md
 create mode 100644 docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
 create mode 100644 docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
 create mode 100644 docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
 create mode 100644 docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
 create mode 100644 docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md
 create mode 100644 docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
 create mode 100644 docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
 create mode 100644 docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
 create mode 100644 docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
 create mode 100644 docs/known-issues/es/price-updates-with-cache-on-end-applications.md
 create mode 100644 docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
 create mode 100644 docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
 create mode 100644 docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md
 create mode 100644 docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md
 create mode 100644 docs/known-issues/es/product-comissioning-inconsistent-cache.md
 create mode 100644 docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md
 create mode 100644 docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
 create mode 100644 docs/known-issues/es/product-page-sessions-not-working.md
 create mode 100644 docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
 create mode 100644 docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
 create mode 100644 docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
 create mode 100644 docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md
 create mode 100644 docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
 create mode 100644 docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
 create mode 100644 docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
 create mode 100644 docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
 create mode 100644 docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
 create mode 100644 docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
 create mode 100644 docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
 create mode 100644 docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
 create mode 100644 docs/known-issues/es/promotions-microrounding-divergence.md
 create mode 100644 docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
 create mode 100644 docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
 create mode 100644 docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
 create mode 100644 docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md
 create mode 100644 docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md
 create mode 100644 docs/known-issues/es/received-skus-review-tab-missing-products.md
 create mode 100644 docs/known-issues/es/redirects-are-being-counted-multiple-times.md
 create mode 100644 docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
 create mode 100644 docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md
 create mode 100644 docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
 create mode 100644 docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md
 create mode 100644 docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
 create mode 100644 docs/known-issues/es/replacing-orders-with-different-sales-channel.md
 create mode 100644 docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md
 create mode 100644 docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
 create mode 100644 docs/known-issues/es/rewriter-is-not-receiving-url-updates.md
 create mode 100644 docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
 create mode 100644 docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
 create mode 100644 docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
 create mode 100644 docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md
 create mode 100644 docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md
 create mode 100644 docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
 create mode 100644 docs/known-issues/es/search-analytics-duplicated-events.md
 create mode 100644 docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
 create mode 100644 docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
 create mode 100644 docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
 create mode 100644 docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
 create mode 100644 docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md
 create mode 100644 docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
 create mode 100644 docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md
 create mode 100644 docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md
 create mode 100644 docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
 create mode 100644 docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
 create mode 100644 docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md
 create mode 100644 docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md
 create mode 100644 docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
 create mode 100644 docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
 create mode 100644 docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md
 create mode 100644 docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
 create mode 100644 docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
 create mode 100644 docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
 create mode 100644 docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
 create mode 100644 docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md
 create mode 100644 docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md
 create mode 100644 docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md
 create mode 100644 docs/known-issues/es/sitemap-isnt-being-generatedupdated.md
 create mode 100644 docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
 create mode 100644 docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
 create mode 100644 docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md
 create mode 100644 docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
 create mode 100644 docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
 create mode 100644 docs/known-issues/es/sku-selector-with-multilpe-contexts.md
 create mode 100644 docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
 create mode 100644 docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
 create mode 100644 docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
 create mode 100644 docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
 create mode 100644 docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
 create mode 100644 docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
 create mode 100644 docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
 create mode 100644 docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
 create mode 100644 docs/known-issues/es/some-unexpected-behavior-in-masterdata.md
 create mode 100644 docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
 create mode 100644 docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
 create mode 100644 docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
 create mode 100644 docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
 create mode 100644 docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
 create mode 100644 docs/known-issues/es/specifications-multiplied-on-catalog.md
 create mode 100644 docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md
 create mode 100644 docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md
 create mode 100644 docs/known-issues/es/subscription-event-history-out-of-order.md
 create mode 100644 docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
 create mode 100644 docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
 create mode 100644 docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
 create mode 100644 docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
 create mode 100644 docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md
 create mode 100644 docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md
 create mode 100644 docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md
 create mode 100644 docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
 create mode 100644 docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
 create mode 100644 docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
 create mode 100644 docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
 create mode 100644 docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
 create mode 100644 docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
 create mode 100644 docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
 create mode 100644 docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
 create mode 100644 docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
 create mode 100644 docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
 create mode 100644 docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
 create mode 100644 docs/known-issues/es/timeout-generating-internal-application-keys.md
 create mode 100644 docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
 create mode 100644 docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md
 create mode 100644 docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
 create mode 100644 docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
 create mode 100644 docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md
 create mode 100644 docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
 create mode 100644 docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
 create mode 100644 docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
 create mode 100644 docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
 create mode 100644 docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
 create mode 100644 docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
 create mode 100644 docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
 create mode 100644 docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
 create mode 100644 docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
 create mode 100644 docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md
 create mode 100644 docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
 create mode 100644 docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md
 create mode 100644 docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
 create mode 100644 docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md
 create mode 100644 docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
 create mode 100644 docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
 create mode 100644 docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
 create mode 100644 docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md
 create mode 100644 docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
 create mode 100644 docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
 create mode 100644 docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md
 create mode 100644 docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
 create mode 100644 docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
 create mode 100644 docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
 create mode 100644 docs/known-issues/es/validatecartmutation-failing-when-large-payload.md
 create mode 100644 docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
 create mode 100644 docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
 create mode 100644 docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
 create mode 100644 docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
 create mode 100644 docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
 create mode 100644 docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md
 create mode 100644 docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
 create mode 100644 docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
 create mode 100644 docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
 create mode 100644 docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md
 create mode 100644 docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
 create mode 100644 docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
 create mode 100644 docs/known-issues/es/xml-installment-currency-does-not-apply.md
 create mode 100644 docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
 create mode 100644 docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
 create mode 100644 docs/known-issues/pt/403-error-for-all-urls-containing-develop.md
 create mode 100644 docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
 create mode 100644 docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
 create mode 100644 docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
 create mode 100644 docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
 create mode 100644 docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
 create mode 100644 docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
 create mode 100644 docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
 create mode 100644 docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
 create mode 100644 docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
 create mode 100644 docs/known-issues/pt/admin-review-global-search.md
 create mode 100644 docs/known-issues/pt/admin-timeout.md
 create mode 100644 docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md
 create mode 100644 docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
 create mode 100644 docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
 create mode 100644 docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
 create mode 100644 docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md
 create mode 100644 docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
 create mode 100644 docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
 create mode 100644 docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
 create mode 100644 docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
 create mode 100644 docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md
 create mode 100644 docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
 create mode 100644 docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
 create mode 100644 docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
 create mode 100644 docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md
 create mode 100644 docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
 create mode 100644 docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
 create mode 100644 docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
 create mode 100644 docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
 create mode 100644 docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md
 create mode 100644 docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md
 create mode 100644 docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
 create mode 100644 docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
 create mode 100644 docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
 create mode 100644 docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
 create mode 100644 docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
 create mode 100644 docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
 create mode 100644 docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
 create mode 100644 docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
 create mode 100644 docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
 create mode 100644 docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md
 create mode 100644 docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
 create mode 100644 docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
 create mode 100644 docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
 create mode 100644 docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
 create mode 100644 docs/known-issues/pt/calculation-issue-in-comissionamount.md
 create mode 100644 docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
 create mode 100644 docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
 create mode 100644 docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
 create mode 100644 docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md
 create mode 100644 docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md
 create mode 100644 docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md
 create mode 100644 docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
 create mode 100644 docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
 create mode 100644 docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
 create mode 100644 docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md
 create mode 100644 docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
 create mode 100644 docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
 create mode 100644 docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md
 create mode 100644 docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
 create mode 100644 docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md
 create mode 100644 docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md
 create mode 100644 docs/known-issues/pt/catalog-filters-timeout.md
 create mode 100644 docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md
 create mode 100644 docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md
 create mode 100644 docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md
 create mode 100644 docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md
 create mode 100644 docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md
 create mode 100644 docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
 create mode 100644 docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
 create mode 100644 docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
 create mode 100644 docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md
 create mode 100644 docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md
 create mode 100644 docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
 create mode 100644 docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md
 create mode 100644 docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
 create mode 100644 docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
 create mode 100644 docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
 create mode 100644 docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
 create mode 100644 docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
 create mode 100644 docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
 create mode 100644 docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
 create mode 100644 docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
 create mode 100644 docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
 create mode 100644 docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
 create mode 100644 docs/known-issues/pt/cms-settings-role-not-working-as-expected.md
 create mode 100644 docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
 create mode 100644 docs/known-issues/pt/collections-dont-open-on-subaccounts.md
 create mode 100644 docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md
 create mode 100644 docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md
 create mode 100644 docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md
 create mode 100644 docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md
 create mode 100644 docs/known-issues/pt/components-in-a-kit-with-the-same-price.md
 create mode 100644 docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
 create mode 100644 docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
 create mode 100644 docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
 create mode 100644 docs/known-issues/pt/country-field-as-null-in-invoicedata.md
 create mode 100644 docs/known-issues/pt/coupons-created-as-archived-temporarrily.md
 create mode 100644 docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md
 create mode 100644 docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
 create mode 100644 docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
 create mode 100644 docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
 create mode 100644 docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md
 create mode 100644 docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md
 create mode 100644 docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md
 create mode 100644 docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
 create mode 100644 docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
 create mode 100644 docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md
 create mode 100644 docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md
 create mode 100644 docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
 create mode 100644 docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
 create mode 100644 docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md
 create mode 100644 docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md
 create mode 100644 docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md
 create mode 100644 docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md
 create mode 100644 docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
 create mode 100644 docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
 create mode 100644 docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
 create mode 100644 docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md
 create mode 100644 docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
 create mode 100644 docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
 create mode 100644 docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md
 create mode 100644 docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md
 create mode 100644 docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
 create mode 100644 docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
 create mode 100644 docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
 create mode 100644 docs/known-issues/pt/error-cancelling-customer-credit-invoices.md
 create mode 100644 docs/known-issues/pt/error-closing-customer-credit-account.md
 create mode 100644 docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md
 create mode 100644 docs/known-issues/pt/error-exporting-prices-with-metadata.md
 create mode 100644 docs/known-issues/pt/error-in-custom-payments-creation.md
 create mode 100644 docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
 create mode 100644 docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
 create mode 100644 docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
 create mode 100644 docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
 create mode 100644 docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
 create mode 100644 docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
 create mode 100644 docs/known-issues/pt/error-on-duplicate-payment-method.md
 create mode 100644 docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
 create mode 100644 docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md
 create mode 100644 docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md
 create mode 100644 docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md
 create mode 100644 docs/known-issues/pt/exclude-products-from-collection-not-working.md
 create mode 100644 docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md
 create mode 100644 docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
 create mode 100644 docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
 create mode 100644 docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
 create mode 100644 docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
 create mode 100644 docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
 create mode 100644 docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
 create mode 100644 docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md
 create mode 100644 docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
 create mode 100644 docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md
 create mode 100644 docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md
 create mode 100644 docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
 create mode 100644 docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md
 create mode 100644 docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
 create mode 100644 docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
 create mode 100644 docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
 create mode 100644 docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
 create mode 100644 docs/known-issues/pt/first-subscription-cycle-is-skipped.md
 create mode 100644 docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
 create mode 100644 docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
 create mode 100644 docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
 create mode 100644 docs/known-issues/pt/gift-card-creation-error-via-admin.md
 create mode 100644 docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
 create mode 100644 docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
 create mode 100644 docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
 create mode 100644 docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md
 create mode 100644 docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
 create mode 100644 docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md
 create mode 100644 docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
 create mode 100644 docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
 create mode 100644 docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
 create mode 100644 docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md
 create mode 100644 docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
 create mode 100644 docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
 create mode 100644 docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
 create mode 100644 docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
 create mode 100644 docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
 create mode 100644 docs/known-issues/pt/infocard-mobile-images-wont-apply.md
 create mode 100644 docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
 create mode 100644 docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md
 create mode 100644 docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
 create mode 100644 docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md
 create mode 100644 docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
 create mode 100644 docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
 create mode 100644 docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
 create mode 100644 docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
 create mode 100644 docs/known-issues/pt/intermitent-site-editor-content-loss.md
 create mode 100644 docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md
 create mode 100644 docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
 create mode 100644 docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md
 create mode 100644 docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
 create mode 100644 docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
 create mode 100644 docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
 create mode 100644 docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md
 create mode 100644 docs/known-issues/pt/issues-with-my-account-links.md
 create mode 100644 docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
 create mode 100644 docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
 create mode 100644 docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
 create mode 100644 docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md
 create mode 100644 docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
 create mode 100644 docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
 create mode 100644 docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
 create mode 100644 docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
 create mode 100644 docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
 create mode 100644 docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md
 create mode 100644 docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
 create mode 100644 docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
 create mode 100644 docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
 create mode 100644 docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md
 create mode 100644 docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
 create mode 100644 docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md
 create mode 100644 docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
 create mode 100644 docs/known-issues/pt/mandatory-service-working-as-optional.md
 create mode 100644 docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
 create mode 100644 docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md
 create mode 100644 docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
 create mode 100644 docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
 create mode 100644 docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
 create mode 100644 docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md
 create mode 100644 docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
 create mode 100644 docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md
 create mode 100644 docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
 create mode 100644 docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md
 create mode 100644 docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
 create mode 100644 docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
 create mode 100644 docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
 create mode 100644 docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
 create mode 100644 docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md
 create mode 100644 docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
 create mode 100644 docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md
 create mode 100644 docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md
 create mode 100644 docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md
 create mode 100644 docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
 create mode 100644 docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
 create mode 100644 docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md
 create mode 100644 docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
 create mode 100644 docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md
 create mode 100644 docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md
 create mode 100644 docs/known-issues/pt/meli-update-stockprice-issue.md
 create mode 100644 docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
 create mode 100644 docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
 create mode 100644 docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
 create mode 100644 docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md
 create mode 100644 docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
 create mode 100644 docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
 create mode 100644 docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
 create mode 100644 docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md
 create mode 100644 docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
 create mode 100644 docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md
 create mode 100644 docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
 create mode 100644 docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
 create mode 100644 docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
 create mode 100644 docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
 create mode 100644 docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
 create mode 100644 docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
 create mode 100644 docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
 create mode 100644 docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
 create mode 100644 docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
 create mode 100644 docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
 create mode 100644 docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md
 create mode 100644 docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
 create mode 100644 docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md
 create mode 100644 docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
 create mode 100644 docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md
 create mode 100644 docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
 create mode 100644 docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
 create mode 100644 docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
 create mode 100644 docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
 create mode 100644 docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
 create mode 100644 docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md
 create mode 100644 docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
 create mode 100644 docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md
 create mode 100644 docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
 create mode 100644 docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
 create mode 100644 docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md
 create mode 100644 docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md
 create mode 100644 docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
 create mode 100644 docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
 create mode 100644 docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
 create mode 100644 docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
 create mode 100644 docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
 create mode 100644 docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
 create mode 100644 docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
 create mode 100644 docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
 create mode 100644 docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md
 create mode 100644 docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
 create mode 100644 docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
 create mode 100644 docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
 create mode 100644 docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
 create mode 100644 docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md
 create mode 100644 docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
 create mode 100644 docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
 create mode 100644 docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
 create mode 100644 docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
 create mode 100644 docs/known-issues/pt/price-updates-with-cache-on-end-applications.md
 create mode 100644 docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
 create mode 100644 docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
 create mode 100644 docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md
 create mode 100644 docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md
 create mode 100644 docs/known-issues/pt/product-comissioning-inconsistent-cache.md
 create mode 100644 docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md
 create mode 100644 docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
 create mode 100644 docs/known-issues/pt/product-page-sessions-not-working.md
 create mode 100644 docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
 create mode 100644 docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
 create mode 100644 docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
 create mode 100644 docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md
 create mode 100644 docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
 create mode 100644 docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
 create mode 100644 docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
 create mode 100644 docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
 create mode 100644 docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
 create mode 100644 docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
 create mode 100644 docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
 create mode 100644 docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
 create mode 100644 docs/known-issues/pt/promotions-microrounding-divergence.md
 create mode 100644 docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
 create mode 100644 docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
 create mode 100644 docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
 create mode 100644 docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md
 create mode 100644 docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md
 create mode 100644 docs/known-issues/pt/received-skus-review-tab-missing-products.md
 create mode 100644 docs/known-issues/pt/redirects-are-being-counted-multiple-times.md
 create mode 100644 docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
 create mode 100644 docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md
 create mode 100644 docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
 create mode 100644 docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md
 create mode 100644 docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
 create mode 100644 docs/known-issues/pt/replacing-orders-with-different-sales-channel.md
 create mode 100644 docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md
 create mode 100644 docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
 create mode 100644 docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md
 create mode 100644 docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
 create mode 100644 docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
 create mode 100644 docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
 create mode 100644 docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md
 create mode 100644 docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md
 create mode 100644 docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
 create mode 100644 docs/known-issues/pt/search-analytics-duplicated-events.md
 create mode 100644 docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
 create mode 100644 docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
 create mode 100644 docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
 create mode 100644 docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
 create mode 100644 docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md
 create mode 100644 docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
 create mode 100644 docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md
 create mode 100644 docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md
 create mode 100644 docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
 create mode 100644 docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
 create mode 100644 docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md
 create mode 100644 docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md
 create mode 100644 docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
 create mode 100644 docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
 create mode 100644 docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md
 create mode 100644 docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
 create mode 100644 docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
 create mode 100644 docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
 create mode 100644 docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
 create mode 100644 docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md
 create mode 100644 docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md
 create mode 100644 docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md
 create mode 100644 docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md
 create mode 100644 docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
 create mode 100644 docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
 create mode 100644 docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md
 create mode 100644 docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
 create mode 100644 docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
 create mode 100644 docs/known-issues/pt/sku-selector-with-multilpe-contexts.md
 create mode 100644 docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
 create mode 100644 docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
 create mode 100644 docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
 create mode 100644 docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
 create mode 100644 docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
 create mode 100644 docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
 create mode 100644 docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
 create mode 100644 docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
 create mode 100644 docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md
 create mode 100644 docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
 create mode 100644 docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
 create mode 100644 docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
 create mode 100644 docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
 create mode 100644 docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
 create mode 100644 docs/known-issues/pt/specifications-multiplied-on-catalog.md
 create mode 100644 docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md
 create mode 100644 docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md
 create mode 100644 docs/known-issues/pt/subscription-event-history-out-of-order.md
 create mode 100644 docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
 create mode 100644 docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
 create mode 100644 docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
 create mode 100644 docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
 create mode 100644 docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md
 create mode 100644 docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md
 create mode 100644 docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md
 create mode 100644 docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
 create mode 100644 docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
 create mode 100644 docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
 create mode 100644 docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
 create mode 100644 docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
 create mode 100644 docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
 create mode 100644 docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
 create mode 100644 docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md
 create mode 100644 docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
 create mode 100644 docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
 create mode 100644 docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
 create mode 100644 docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
 create mode 100644 docs/known-issues/pt/timeout-generating-internal-application-keys.md
 create mode 100644 docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
 create mode 100644 docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md
 create mode 100644 docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
 create mode 100644 docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
 create mode 100644 docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md
 create mode 100644 docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
 create mode 100644 docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
 create mode 100644 docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
 create mode 100644 docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
 create mode 100644 docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
 create mode 100644 docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
 create mode 100644 docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
 create mode 100644 docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
 create mode 100644 docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
 create mode 100644 docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md
 create mode 100644 docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
 create mode 100644 docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md
 create mode 100644 docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
 create mode 100644 docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md
 create mode 100644 docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
 create mode 100644 docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
 create mode 100644 docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
 create mode 100644 docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md
 create mode 100644 docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
 create mode 100644 docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
 create mode 100644 docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md
 create mode 100644 docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
 create mode 100644 docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
 create mode 100644 docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
 create mode 100644 docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md
 create mode 100644 docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
 create mode 100644 docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
 create mode 100644 docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
 create mode 100644 docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
 create mode 100644 docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
 create mode 100644 docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md
 create mode 100644 docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
 create mode 100644 docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
 create mode 100644 docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
 create mode 100644 docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md
 create mode 100644 docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
 create mode 100644 docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
 create mode 100644 docs/known-issues/pt/xml-installment-currency-does-not-apply.md
 create mode 100644 docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
 create mode 100644 docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
 create mode 100644 docs/tracks/en/accounts-and-architecture.md
 create mode 100644 docs/tracks/en/add-on-products.md
 create mode 100644 docs/tracks/en/apple-pay.md
 create mode 100644 docs/tracks/en/backend-integrations.md
 create mode 100644 docs/tracks/en/billing-support.md
 create mode 100644 docs/tracks/en/commercial-support.md
 create mode 100644 docs/tracks/en/configuring-livelo-price-divergence-rule.md
 create mode 100644 docs/tracks/en/configuring-rappi-price-divergence-rule.md
 create mode 100644 docs/tracks/en/configuring-the-integration-rappi.md
 create mode 100644 docs/tracks/en/configuring-the-integration.md
 create mode 100644 docs/tracks/en/contract-termination.md
 create mode 100644 docs/tracks/en/creating-merchandising-rules-visual-editor.md
 create mode 100644 docs/tracks/en/data-protection-roles.md
 create mode 100644 docs/tracks/en/digital-wallet-e-wallet.md
 create mode 100644 docs/tracks/en/extensions-hub-partners.md
 create mode 100644 docs/tracks/en/frontend-implementation.md
 create mode 100644 docs/tracks/en/google-pay.md
 create mode 100644 docs/tracks/en/how-vtex-support-works.md
 create mode 100644 docs/tracks/en/indexing-history.md
 create mode 100644 docs/tracks/en/intelligent-synonyms.md
 create mode 100644 docs/tracks/en/introduction-to-vtex.md
 create mode 100644 docs/tracks/en/livelo-integration-overview.md
 create mode 100644 docs/tracks/en/livelo-integration-registration.md
 create mode 100644 docs/tracks/en/managing-customer-credit-invoices.md
 create mode 100644 docs/tracks/en/mapping-product-categories-and-attributes.md
 create mode 100644 docs/tracks/en/mapping-rappi-product-categories-and-attributes.md
 create mode 100644 docs/tracks/en/next-steps.md
 create mode 100644 docs/tracks/en/opening-tickets.md
 create mode 100644 docs/tracks/en/other-vtex-module-settings.md
 create mode 100644 docs/tracks/en/personal-data.md
 create mode 100644 docs/tracks/en/planning-the-go-live.md
 create mode 100644 docs/tracks/en/product-integration-errors-with-amazon.md
 create mode 100644 docs/tracks/en/rappi-integration-overview.md
 create mode 100644 docs/tracks/en/rappi-integration-registration.md
 create mode 100644 docs/tracks/en/subject-rights.md
 create mode 100644 docs/tracks/en/technical-and-administrative-measures.md
 create mode 100644 docs/tracks/en/technical-support.md
 create mode 100644 docs/tracks/en/unified-commerce.md
 create mode 100644 docs/tracks/en/vtex-modules-i.md
 create mode 100644 docs/tracks/en/vtex-modules-ii.md
 create mode 100644 docs/tracks/en/vtex-support.md
 create mode 100644 docs/tracks/es/accounts-and-architecture.md
 create mode 100644 docs/tracks/es/add-on-products.md
 create mode 100644 docs/tracks/es/apple-pay.md
 create mode 100644 docs/tracks/es/backend-integrations.md
 create mode 100644 docs/tracks/es/billing-support.md
 create mode 100644 docs/tracks/es/commercial-support.md
 create mode 100644 docs/tracks/es/configuring-livelo-price-divergence-rule.md
 create mode 100644 docs/tracks/es/configuring-rappi-price-divergence-rule.md
 create mode 100644 docs/tracks/es/configuring-the-integration-rappi.md
 create mode 100644 docs/tracks/es/configuring-the-integration.md
 create mode 100644 docs/tracks/es/contract-termination.md
 create mode 100644 docs/tracks/es/creating-merchandising-rules-visual-editor.md
 create mode 100644 docs/tracks/es/data-protection-roles.md
 create mode 100644 docs/tracks/es/digital-wallet-e-wallet.md
 create mode 100644 docs/tracks/es/extensions-hub-partners.md
 create mode 100644 docs/tracks/es/frontend-implementation.md
 create mode 100644 docs/tracks/es/google-pay.md
 create mode 100644 docs/tracks/es/how-vtex-support-works.md
 create mode 100644 docs/tracks/es/indexing-history.md
 create mode 100644 docs/tracks/es/intelligent-synonyms.md
 create mode 100644 docs/tracks/es/introduction-to-vtex.md
 create mode 100644 docs/tracks/es/livelo-integration-overview.md
 create mode 100644 docs/tracks/es/livelo-integration-registration.md
 create mode 100644 docs/tracks/es/managing-customer-credit-invoices.md
 create mode 100644 docs/tracks/es/mapping-product-categories-and-attributes.md
 create mode 100644 docs/tracks/es/mapping-rappi-product-categories-and-attributes.md
 create mode 100644 docs/tracks/es/next-steps.md
 create mode 100644 docs/tracks/es/opening-tickets.md
 create mode 100644 docs/tracks/es/other-vtex-module-settings.md
 create mode 100644 docs/tracks/es/personal-data.md
 create mode 100644 docs/tracks/es/planning-the-go-live.md
 create mode 100644 docs/tracks/es/product-integration-errors-with-amazon.md
 create mode 100644 docs/tracks/es/rappi-integration-overview.md
 create mode 100644 docs/tracks/es/rappi-integration-registration.md
 create mode 100644 docs/tracks/es/subject-rights.md
 create mode 100644 docs/tracks/es/technical-and-administrative-measures.md
 create mode 100644 docs/tracks/es/technical-support.md
 create mode 100644 docs/tracks/es/unified-commerce.md
 create mode 100644 docs/tracks/es/vtex-modules-i.md
 create mode 100644 docs/tracks/es/vtex-modules-ii.md
 create mode 100644 docs/tracks/es/vtex-support.md
 create mode 100644 docs/tracks/pt/accounts-and-architecture.md
 create mode 100644 docs/tracks/pt/add-on-products.md
 create mode 100644 docs/tracks/pt/apple-pay.md
 create mode 100644 docs/tracks/pt/backend-integrations.md
 create mode 100644 docs/tracks/pt/billing-support.md
 create mode 100644 docs/tracks/pt/commercial-support.md
 create mode 100644 docs/tracks/pt/configuring-livelo-price-divergence-rule.md
 create mode 100644 docs/tracks/pt/configuring-rappi-price-divergence-rule.md
 create mode 100644 docs/tracks/pt/configuring-the-integration-rappi.md
 create mode 100644 docs/tracks/pt/configuring-the-integration.md
 create mode 100644 docs/tracks/pt/contract-termination.md
 create mode 100644 docs/tracks/pt/creating-merchandising-rules-visual-editor.md
 create mode 100644 docs/tracks/pt/data-protection-roles.md
 create mode 100644 docs/tracks/pt/digital-wallet-e-wallet.md
 create mode 100644 docs/tracks/pt/extensions-hub-partners.md
 create mode 100644 docs/tracks/pt/frontend-implementation.md
 create mode 100644 docs/tracks/pt/google-pay.md
 create mode 100644 docs/tracks/pt/how-vtex-support-works.md
 create mode 100644 docs/tracks/pt/indexing-history.md
 create mode 100644 docs/tracks/pt/intelligent-synonyms.md
 create mode 100644 docs/tracks/pt/introduction-to-vtex.md
 create mode 100644 docs/tracks/pt/livelo-integration-overview.md
 create mode 100644 docs/tracks/pt/livelo-integration-registration.md
 create mode 100644 docs/tracks/pt/managing-customer-credit-invoices.md
 create mode 100644 docs/tracks/pt/mapping-product-categories-and-attributes.md
 create mode 100644 docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md
 create mode 100644 docs/tracks/pt/next-steps.md
 create mode 100644 docs/tracks/pt/opening-tickets.md
 create mode 100644 docs/tracks/pt/other-vtex-module-settings.md
 create mode 100644 docs/tracks/pt/personal-data.md
 create mode 100644 docs/tracks/pt/planning-the-go-live.md
 create mode 100644 docs/tracks/pt/product-integration-errors-with-amazon.md
 create mode 100644 docs/tracks/pt/rappi-integration-overview.md
 create mode 100644 docs/tracks/pt/rappi-integration-registration.md
 create mode 100644 docs/tracks/pt/subject-rights.md
 create mode 100644 docs/tracks/pt/technical-and-administrative-measures.md
 create mode 100644 docs/tracks/pt/technical-support.md
 create mode 100644 docs/tracks/pt/unified-commerce.md
 create mode 100644 docs/tracks/pt/vtex-modules-i.md
 create mode 100644 docs/tracks/pt/vtex-modules-ii.md
 create mode 100644 docs/tracks/pt/vtex-support.md
 create mode 100644 docs/tutorials/en/access-control.md
 create mode 100644 docs/tutorials/en/adapting-your-integration-for-change-order-beta.md
 create mode 100644 docs/tutorials/en/adding-a-record-on-a-master-data-form.md
 create mode 100644 docs/tutorials/en/adding-bin-information.md
 create mode 100644 docs/tutorials/en/admin-redirect-search-returns-no-results.md
 create mode 100644 docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
 create mode 100644 docs/tutorials/en/amaro-integration.md
 create mode 100644 docs/tutorials/en/analytics.md
 create mode 100644 docs/tutorials/en/assembly-options-in-vtex-sales-app.md
 create mode 100644 docs/tutorials/en/audit.md
 create mode 100644 docs/tutorials/en/authentication.md
 create mode 100644 docs/tutorials/en/autocomplete.md
 create mode 100644 docs/tutorials/en/availability.md
 create mode 100644 docs/tutorials/en/b2b-checkout-settings.md
 create mode 100644 docs/tutorials/en/b2b-cost-center-management.md
 create mode 100644 docs/tutorials/en/b2b-organization-general-settings.md
 create mode 100644 docs/tutorials/en/b2b-store-settings.md
 create mode 100644 docs/tutorials/en/b2b-suite-overview.md
 create mode 100644 docs/tutorials/en/b2b-trade-policies-overview.md
 create mode 100644 docs/tutorials/en/banners.md
 create mode 100644 docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md
 create mode 100644 docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md
 create mode 100644 docs/tutorials/en/best-practices-to-avoid-scams-using-the-vtex-brand.md
 create mode 100644 docs/tutorials/en/configure-payment-with-shopfacil.md
 create mode 100644 docs/tutorials/en/configuring-banners.md
 create mode 100644 docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
 create mode 100644 docs/tutorials/en/configuring-payment-conditions-for-b2b.md
 create mode 100644 docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md
 create mode 100644 docs/tutorials/en/configuring-redirects.md
 create mode 100644 docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
 create mode 100644 docs/tutorials/en/configuring-seo-in-your-store.md
 create mode 100644 docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
 create mode 100644 docs/tutorials/en/configuring-the-store-domain.md
 create mode 100644 docs/tutorials/en/creating-a-shipping-policy.md
 create mode 100644 docs/tutorials/en/creating-custom-queries-in-master-data-v1.md
 create mode 100644 docs/tutorials/en/creating-merchandising-rules-manual-editor.md
 create mode 100644 docs/tutorials/en/creating-merchandising-rules-visual-editor.md
 create mode 100644 docs/tutorials/en/creating-roles.md
 create mode 100644 docs/tutorials/en/creating-subaccount-multi-store-multi-domain.md
 create mode 100644 docs/tutorials/en/creating-synonyms.md
 create mode 100644 docs/tutorials/en/criar-um-produto-beta.md
 create mode 100644 docs/tutorials/en/custom-fields-when-adding-an-organization.md
 create mode 100644 docs/tutorials/en/custom-product-fields.md
 create mode 100644 docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md
 create mode 100644 docs/tutorials/en/data-entity.md
 create mode 100644 docs/tutorials/en/declining-order-cancelation.md
 create mode 100644 docs/tutorials/en/defining-mandatory-fields-in-master-data-v1-forms.md
 create mode 100644 docs/tutorials/en/detaching-skus-by-specification.md
 create mode 100644 docs/tutorials/en/direct-migration-magazine-luiza.md
 create mode 100644 docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
 create mode 100644 docs/tutorials/en/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
 create mode 100644 docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
 create mode 100644 docs/tutorials/en/erasing-customer-data.md
 create mode 100644 docs/tutorials/en/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
 create mode 100644 docs/tutorials/en/explained-search.md
 create mode 100644 docs/tutorials/en/faq-security-restricted-content.md
 create mode 100644 docs/tutorials/en/filters.md
 create mode 100644 docs/tutorials/en/find-sellers.md
 create mode 100644 docs/tutorials/en/fulfillment-magalu.md
 create mode 100644 docs/tutorials/en/google-integration-warnings.md
 create mode 100644 docs/tutorials/en/headless-cms-overview.md
 create mode 100644 docs/tutorials/en/how-change-order-works-beta.md
 create mode 100644 docs/tutorials/en/how-dns-configuration-works-on-vtex.md
 create mode 100644 docs/tutorials/en/how-promotion-competition-works.md
 create mode 100644 docs/tutorials/en/how-to-change-orders-beta.md
 create mode 100644 docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md
 create mode 100644 docs/tutorials/en/i-cant-import-the-price-table.md
 create mode 100644 docs/tutorials/en/i-cant-receive-emails-from-vtex.md
 create mode 100644 docs/tutorials/en/i-cant-update-the-ean-of-my-skus-via-api.md
 create mode 100644 docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
 create mode 100644 docs/tutorials/en/image-compression.md
 create mode 100644 docs/tutorials/en/indexes-in-master-data.md
 create mode 100644 docs/tutorials/en/indexing-history.md
 create mode 100644 docs/tutorials/en/indexing.md
 create mode 100644 docs/tutorials/en/intelligent-synonyms.md
 create mode 100644 docs/tutorials/en/inventory-data-pipeline-beta.md
 create mode 100644 docs/tutorials/en/kr1-test.md
 create mode 100644 docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
 create mode 100644 docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
 create mode 100644 docs/tutorials/en/making-a-master-data-field-editable.md
 create mode 100644 docs/tutorials/en/managing-b2b-organizations.md
 create mode 100644 docs/tutorials/en/managing-http-headers.md
 create mode 100644 docs/tutorials/en/managing-projects.md
 create mode 100644 docs/tutorials/en/managing-shipping-policies.md
 create mode 100644 docs/tutorials/en/managing-users-in-b2b-organizations.md
 create mode 100644 docs/tutorials/en/match-offers-mercado-livre.md
 create mode 100644 docs/tutorials/en/mercado-libre-size-chart.md
 create mode 100644 docs/tutorials/en/merchandising-rule-conditions.md
 create mode 100644 docs/tutorials/en/merchandising-rules-list.md
 create mode 100644 docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md
 create mode 100644 docs/tutorials/en/my-ad-is-not-displayed-on-mercado-livre.md
 create mode 100644 docs/tutorials/en/my-inventory-is-negative.md
 create mode 100644 docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md
 create mode 100644 docs/tutorials/en/my-store-order-was-not-created.md
 create mode 100644 docs/tutorials/en/navigation.md
 create mode 100644 docs/tutorials/en/offer-status.md
 create mode 100644 docs/tutorials/en/operational-capacity-beta.md
 create mode 100644 docs/tutorials/en/orderform-settings.md
 create mode 100644 docs/tutorials/en/orders.md
 create mode 100644 docs/tutorials/en/overview-of-b2b-orders-history.md
 create mode 100644 docs/tutorials/en/payments.md
 create mode 100644 docs/tutorials/en/permissions-management-in-b2b-suite.md
 create mode 100644 docs/tutorials/en/pickup-points-for-subscription-orders.md
 create mode 100644 docs/tutorials/en/price-table-management-in-b2b-organizations.md
 create mode 100644 docs/tutorials/en/prices-data-pipeline-beta.md
 create mode 100644 docs/tutorials/en/promotions.md
 create mode 100644 docs/tutorials/en/received-skus-beta.md
 create mode 100644 docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
 create mode 100644 docs/tutorials/en/redirect-from-other-addresses.md
 create mode 100644 docs/tutorials/en/redirects.md
 create mode 100644 docs/tutorials/en/relevance-rules.md
 create mode 100644 docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
 create mode 100644 docs/tutorials/en/requesting-a-new-organization.md
 create mode 100644 docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
 create mode 100644 docs/tutorials/en/restrict-public-access-to-master-data-fields.md
 create mode 100644 docs/tutorials/en/risk-assessment.md
 create mode 100644 docs/tutorials/en/sales-associate-code-field-at-checkout.md
 create mode 100644 docs/tutorials/en/search-behavior.md
 create mode 100644 docs/tutorials/en/search-configuration.md
 create mode 100644 docs/tutorials/en/security-certificate-ssl.md
 create mode 100644 docs/tutorials/en/security-monitor.md
 create mode 100644 docs/tutorials/en/seller-monitoring.md
 create mode 100644 docs/tutorials/en/seller-portal-creating-a-promotion.md
 create mode 100644 docs/tutorials/en/seller-portal-promotions.md
 create mode 100644 docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-alignetv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-appmax.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-argonpay.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-braintree.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-cieloecommerce.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-credimarcas.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-culqi.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-dapp.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-deuna.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-e-sitef.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-easypay-marketplace.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-easypay-seller.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-easypay.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-evopayments.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-fintoc.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-geru.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-gocuotas.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-guatapay.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-inswitch.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-itau-rede.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-k8bank.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-liquido-payment.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-mobbex.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-msc-payment.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-notes-payable.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-nuvei.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-pagbrasilv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-paghiperv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-paghiperv3.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-pagoefectivov2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-pagoexpress.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-pay4fun.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-paymentezv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-paypalv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-payuv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-payway.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-poolpay.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-powerpay.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-safetypayv2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-stark-bank.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-stelom1v2.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-transfero-crypto-checkout.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-unlimit.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-webpayoneclick.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-wepay4u.md
 create mode 100644 docs/tutorials/en/setting-up-payments-with-woovi.md
 create mode 100644 docs/tutorials/en/setting-up-the-notes-payable-conector.md
 create mode 100644 docs/tutorials/en/skus.md
 create mode 100644 docs/tutorials/en/smartcheckout-v5-general-characteristics.md
 create mode 100644 docs/tutorials/en/store-overview-beta.md
 create mode 100644 docs/tutorials/en/store-profile.md
 create mode 100644 docs/tutorials/en/synonym-list.md
 create mode 100644 docs/tutorials/en/test-kr1.md
 create mode 100644 docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md
 create mode 100644 docs/tutorials/en/untitled-entry-2024-03-13-at-16-25-15.md
 create mode 100644 docs/tutorials/en/untitled-entry-2024-07-25-at-21-25-31.md
 create mode 100644 docs/tutorials/en/vtex-ad-network-beta.md
 create mode 100644 docs/tutorials/en/vtex-agreement.md
 create mode 100644 docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
 create mode 100644 docs/tutorials/en/vtex-operation-service-level-agreement-sla.md
 create mode 100644 docs/tutorials/en/vtex-pick-and-pack-insights.md
 create mode 100644 docs/tutorials/en/vtex-pick-and-pack-mobile.md
 create mode 100644 docs/tutorials/en/vtex-pick-and-pack-orders.md
 create mode 100644 docs/tutorials/en/vtex-pick-and-pack-settings.md
 create mode 100644 docs/tutorials/en/vtex-pick-and-pack-worksheets.md
 create mode 100644 docs/tutorials/en/vtex-shield.md
 create mode 100644 docs/tutorials/en/vtex-shipping-network-correios-activation.md
 create mode 100644 docs/tutorials/en/vtex-status-page.md
 create mode 100644 docs/tutorials/en/vtex-support-apac.md
 create mode 100644 docs/tutorials/en/web-application-firewall-waf.md
 create mode 100644 docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md
 create mode 100644 docs/tutorials/en/why-dont-marketplace-orders-integrate-with-my-store.md
 create mode 100644 docs/tutorials/es/access-control.md
 create mode 100644 docs/tutorials/es/adapting-your-integration-for-change-order-beta.md
 create mode 100644 docs/tutorials/es/adding-a-record-on-a-master-data-form.md
 create mode 100644 docs/tutorials/es/adding-bin-information.md
 create mode 100644 docs/tutorials/es/admin-redirect-search-returns-no-results.md
 create mode 100644 docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
 create mode 100644 docs/tutorials/es/amaro-integration.md
 create mode 100644 docs/tutorials/es/analytics.md
 create mode 100644 docs/tutorials/es/assembly-options-in-vtex-sales-app.md
 create mode 100644 docs/tutorials/es/audit.md
 create mode 100644 docs/tutorials/es/authentication.md
 create mode 100644 docs/tutorials/es/autocomplete.md
 create mode 100644 docs/tutorials/es/availability.md
 create mode 100644 docs/tutorials/es/b2b-checkout-settings.md
 create mode 100644 docs/tutorials/es/b2b-cost-center-management.md
 create mode 100644 docs/tutorials/es/b2b-organization-general-settings.md
 create mode 100644 docs/tutorials/es/b2b-store-settings.md
 create mode 100644 docs/tutorials/es/b2b-suite-overview.md
 create mode 100644 docs/tutorials/es/b2b-trade-policies-overview.md
 create mode 100644 docs/tutorials/es/banners.md
 create mode 100644 docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md
 create mode 100644 docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md
 create mode 100644 docs/tutorials/es/best-practices-to-avoid-scams-using-the-vtex-brand.md
 create mode 100644 docs/tutorials/es/configure-payment-with-shopfacil.md
 create mode 100644 docs/tutorials/es/configuring-banners.md
 create mode 100644 docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
 create mode 100644 docs/tutorials/es/configuring-payment-conditions-for-b2b.md
 create mode 100644 docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md
 create mode 100644 docs/tutorials/es/configuring-redirects.md
 create mode 100644 docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
 create mode 100644 docs/tutorials/es/configuring-seo-in-your-store.md
 create mode 100644 docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
 create mode 100644 docs/tutorials/es/configuring-the-store-domain.md
 create mode 100644 docs/tutorials/es/creating-a-shipping-policy.md
 create mode 100644 docs/tutorials/es/creating-custom-queries-in-master-data-v1.md
 create mode 100644 docs/tutorials/es/creating-merchandising-rules-manual-editor.md
 create mode 100644 docs/tutorials/es/creating-merchandising-rules-visual-editor.md
 create mode 100644 docs/tutorials/es/creating-roles.md
 create mode 100644 docs/tutorials/es/creating-subaccount-multi-store-multi-domain.md
 create mode 100644 docs/tutorials/es/creating-synonyms.md
 create mode 100644 docs/tutorials/es/criar-um-produto-beta.md
 create mode 100644 docs/tutorials/es/custom-fields-when-adding-an-organization.md
 create mode 100644 docs/tutorials/es/custom-product-fields.md
 create mode 100644 docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md
 create mode 100644 docs/tutorials/es/data-entity.md
 create mode 100644 docs/tutorials/es/declining-order-cancelation.md
 create mode 100644 docs/tutorials/es/defining-mandatory-fields-in-master-data-v1-forms.md
 create mode 100644 docs/tutorials/es/detaching-skus-by-specification.md
 create mode 100644 docs/tutorials/es/direct-migration-magazine-luiza.md
 create mode 100644 docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
 create mode 100644 docs/tutorials/es/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
 create mode 100644 docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
 create mode 100644 docs/tutorials/es/erasing-customer-data.md
 create mode 100644 docs/tutorials/es/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
 create mode 100644 docs/tutorials/es/explained-search.md
 create mode 100644 docs/tutorials/es/faq-security-restricted-content.md
 create mode 100644 docs/tutorials/es/filters.md
 create mode 100644 docs/tutorials/es/find-sellers.md
 create mode 100644 docs/tutorials/es/fulfillment-magalu.md
 create mode 100644 docs/tutorials/es/google-integration-warnings.md
 create mode 100644 docs/tutorials/es/headless-cms-overview.md
 create mode 100644 docs/tutorials/es/how-change-order-works-beta.md
 create mode 100644 docs/tutorials/es/how-dns-configuration-works-on-vtex.md
 create mode 100644 docs/tutorials/es/how-promotion-competition-works.md
 create mode 100644 docs/tutorials/es/how-to-change-orders-beta.md
 create mode 100644 docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md
 create mode 100644 docs/tutorials/es/i-cant-import-the-price-table.md
 create mode 100644 docs/tutorials/es/i-cant-receive-emails-from-vtex.md
 create mode 100644 docs/tutorials/es/i-cant-update-the-ean-of-my-skus-via-api.md
 create mode 100644 docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
 create mode 100644 docs/tutorials/es/image-compression.md
 create mode 100644 docs/tutorials/es/indexes-in-master-data.md
 create mode 100644 docs/tutorials/es/indexing-history.md
 create mode 100644 docs/tutorials/es/indexing.md
 create mode 100644 docs/tutorials/es/intelligent-synonyms.md
 create mode 100644 docs/tutorials/es/inventory-data-pipeline-beta.md
 create mode 100644 docs/tutorials/es/kr1-test.md
 create mode 100644 docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
 create mode 100644 docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
 create mode 100644 docs/tutorials/es/making-a-master-data-field-editable.md
 create mode 100644 docs/tutorials/es/managing-b2b-organizations.md
 create mode 100644 docs/tutorials/es/managing-http-headers.md
 create mode 100644 docs/tutorials/es/managing-projects.md
 create mode 100644 docs/tutorials/es/managing-shipping-policies.md
 create mode 100644 docs/tutorials/es/managing-users-in-b2b-organizations.md
 create mode 100644 docs/tutorials/es/match-offers-mercado-livre.md
 create mode 100644 docs/tutorials/es/mercado-libre-size-chart.md
 create mode 100644 docs/tutorials/es/merchandising-rule-conditions.md
 create mode 100644 docs/tutorials/es/merchandising-rules-list.md
 create mode 100644 docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md
 create mode 100644 docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md
 create mode 100644 docs/tutorials/es/my-inventory-is-negative.md
 create mode 100644 docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md
 create mode 100644 docs/tutorials/es/my-store-order-was-not-created.md
 create mode 100644 docs/tutorials/es/navigation.md
 create mode 100644 docs/tutorials/es/offer-status.md
 create mode 100644 docs/tutorials/es/operational-capacity-beta.md
 create mode 100644 docs/tutorials/es/orderform-settings.md
 create mode 100644 docs/tutorials/es/orders.md
 create mode 100644 docs/tutorials/es/overview-of-b2b-orders-history.md
 create mode 100644 docs/tutorials/es/payments.md
 create mode 100644 docs/tutorials/es/permissions-management-in-b2b-suite.md
 create mode 100644 docs/tutorials/es/pickup-points-for-subscription-orders.md
 create mode 100644 docs/tutorials/es/price-table-management-in-b2b-organizations.md
 create mode 100644 docs/tutorials/es/prices-data-pipeline-beta.md
 create mode 100644 docs/tutorials/es/promotions.md
 create mode 100644 docs/tutorials/es/received-skus-beta.md
 create mode 100644 docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
 create mode 100644 docs/tutorials/es/redirect-from-other-addresses.md
 create mode 100644 docs/tutorials/es/redirects.md
 create mode 100644 docs/tutorials/es/relevance-rules.md
 create mode 100644 docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
 create mode 100644 docs/tutorials/es/requesting-a-new-organization.md
 create mode 100644 docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
 create mode 100644 docs/tutorials/es/restrict-public-access-to-master-data-fields.md
 create mode 100644 docs/tutorials/es/risk-assessment.md
 create mode 100644 docs/tutorials/es/sales-associate-code-field-at-checkout.md
 create mode 100644 docs/tutorials/es/search-behavior.md
 create mode 100644 docs/tutorials/es/search-configuration.md
 create mode 100644 docs/tutorials/es/security-certificate-ssl.md
 create mode 100644 docs/tutorials/es/security-monitor.md
 create mode 100644 docs/tutorials/es/seller-monitoring.md
 create mode 100644 docs/tutorials/es/seller-portal-creating-a-promotion.md
 create mode 100644 docs/tutorials/es/seller-portal-promotions.md
 create mode 100644 docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-alignetv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-appmax.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-argonpay.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-braintree.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-cieloecommerce.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-credimarcas.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-culqi.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-dapp.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-deuna.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-e-sitef.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-easypay-marketplace.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-easypay-seller.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-easypay.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-evopayments.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-fintoc.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-geru.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-gocuotas.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-guatapay.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-inswitch.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-itau-rede.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-k8bank.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-liquido-payment.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-mobbex.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-msc-payment.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-notes-payable.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-nuvei.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-pagbrasilv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-paghiperv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-paghiperv3.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-pagoefectivov2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-pagoexpress.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-pay4fun.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-paymentezv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-paypalv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-payuv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-payway.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-poolpay.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-powerpay.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-safetypayv2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-stark-bank.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-stelom1v2.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-transfero-crypto-checkout.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-unlimit.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-webpayoneclick.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-wepay4u.md
 create mode 100644 docs/tutorials/es/setting-up-payments-with-woovi.md
 create mode 100644 docs/tutorials/es/setting-up-the-notes-payable-conector.md
 create mode 100644 docs/tutorials/es/skus.md
 create mode 100644 docs/tutorials/es/smartcheckout-v5-general-characteristics.md
 create mode 100644 docs/tutorials/es/store-overview-beta.md
 create mode 100644 docs/tutorials/es/store-profile.md
 create mode 100644 docs/tutorials/es/synonym-list.md
 create mode 100644 docs/tutorials/es/test-kr1.md
 create mode 100644 docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md
 create mode 100644 docs/tutorials/es/untitled-entry-2024-03-13-at-16-25-15.md
 create mode 100644 docs/tutorials/es/untitled-entry-2024-07-25-at-21-25-31.md
 create mode 100644 docs/tutorials/es/vtex-ad-network-beta.md
 create mode 100644 docs/tutorials/es/vtex-agreement.md
 create mode 100644 docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
 create mode 100644 docs/tutorials/es/vtex-operation-service-level-agreement-sla.md
 create mode 100644 docs/tutorials/es/vtex-pick-and-pack-insights.md
 create mode 100644 docs/tutorials/es/vtex-pick-and-pack-mobile.md
 create mode 100644 docs/tutorials/es/vtex-pick-and-pack-orders.md
 create mode 100644 docs/tutorials/es/vtex-pick-and-pack-settings.md
 create mode 100644 docs/tutorials/es/vtex-pick-and-pack-worksheets.md
 create mode 100644 docs/tutorials/es/vtex-shield.md
 create mode 100644 docs/tutorials/es/vtex-shipping-network-correios-activation.md
 create mode 100644 docs/tutorials/es/vtex-status-page.md
 create mode 100644 docs/tutorials/es/vtex-support-apac.md
 create mode 100644 docs/tutorials/es/web-application-firewall-waf.md
 create mode 100644 docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md
 create mode 100644 docs/tutorials/es/why-dont-marketplace-orders-integrate-with-my-store.md
 create mode 100644 docs/tutorials/pt/access-control.md
 create mode 100644 docs/tutorials/pt/adapting-your-integration-for-change-order-beta.md
 create mode 100644 docs/tutorials/pt/adding-a-record-on-a-master-data-form.md
 create mode 100644 docs/tutorials/pt/adding-bin-information.md
 create mode 100644 docs/tutorials/pt/admin-redirect-search-returns-no-results.md
 create mode 100644 docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
 create mode 100644 docs/tutorials/pt/amaro-integration.md
 create mode 100644 docs/tutorials/pt/analytics.md
 create mode 100644 docs/tutorials/pt/assembly-options-in-vtex-sales-app.md
 create mode 100644 docs/tutorials/pt/audit.md
 create mode 100644 docs/tutorials/pt/authentication.md
 create mode 100644 docs/tutorials/pt/autocomplete.md
 create mode 100644 docs/tutorials/pt/availability.md
 create mode 100644 docs/tutorials/pt/b2b-checkout-settings.md
 create mode 100644 docs/tutorials/pt/b2b-cost-center-management.md
 create mode 100644 docs/tutorials/pt/b2b-organization-general-settings.md
 create mode 100644 docs/tutorials/pt/b2b-store-settings.md
 create mode 100644 docs/tutorials/pt/b2b-suite-overview.md
 create mode 100644 docs/tutorials/pt/b2b-trade-policies-overview.md
 create mode 100644 docs/tutorials/pt/banners.md
 create mode 100644 docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md
 create mode 100644 docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md
 create mode 100644 docs/tutorials/pt/best-practices-to-avoid-scams-using-the-vtex-brand.md
 create mode 100644 docs/tutorials/pt/configure-payment-with-shopfacil.md
 create mode 100644 docs/tutorials/pt/configuring-banners.md
 create mode 100644 docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
 create mode 100644 docs/tutorials/pt/configuring-payment-conditions-for-b2b.md
 create mode 100644 docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md
 create mode 100644 docs/tutorials/pt/configuring-redirects.md
 create mode 100644 docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
 create mode 100644 docs/tutorials/pt/configuring-seo-in-your-store.md
 create mode 100644 docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
 create mode 100644 docs/tutorials/pt/configuring-the-store-domain.md
 create mode 100644 docs/tutorials/pt/creating-a-shipping-policy.md
 create mode 100644 docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md
 create mode 100644 docs/tutorials/pt/creating-merchandising-rules-manual-editor.md
 create mode 100644 docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
 create mode 100644 docs/tutorials/pt/creating-roles.md
 create mode 100644 docs/tutorials/pt/creating-subaccount-multi-store-multi-domain.md
 create mode 100644 docs/tutorials/pt/creating-synonyms.md
 create mode 100644 docs/tutorials/pt/criar-um-produto-beta.md
 create mode 100644 docs/tutorials/pt/custom-fields-when-adding-an-organization.md
 create mode 100644 docs/tutorials/pt/custom-product-fields.md
 create mode 100644 docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md
 create mode 100644 docs/tutorials/pt/data-entity.md
 create mode 100644 docs/tutorials/pt/declining-order-cancelation.md
 create mode 100644 docs/tutorials/pt/defining-mandatory-fields-in-master-data-v1-forms.md
 create mode 100644 docs/tutorials/pt/detaching-skus-by-specification.md
 create mode 100644 docs/tutorials/pt/direct-migration-magazine-luiza.md
 create mode 100644 docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
 create mode 100644 docs/tutorials/pt/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
 create mode 100644 docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
 create mode 100644 docs/tutorials/pt/erasing-customer-data.md
 create mode 100644 docs/tutorials/pt/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
 create mode 100644 docs/tutorials/pt/explained-search.md
 create mode 100644 docs/tutorials/pt/faq-security-restricted-content.md
 create mode 100644 docs/tutorials/pt/filters.md
 create mode 100644 docs/tutorials/pt/find-sellers.md
 create mode 100644 docs/tutorials/pt/fulfillment-magalu.md
 create mode 100644 docs/tutorials/pt/google-integration-warnings.md
 create mode 100644 docs/tutorials/pt/headless-cms-overview.md
 create mode 100644 docs/tutorials/pt/how-change-order-works-beta.md
 create mode 100644 docs/tutorials/pt/how-dns-configuration-works-on-vtex.md
 create mode 100644 docs/tutorials/pt/how-promotion-competition-works.md
 create mode 100644 docs/tutorials/pt/how-to-change-orders-beta.md
 create mode 100644 docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md
 create mode 100644 docs/tutorials/pt/i-cant-import-the-price-table.md
 create mode 100644 docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
 create mode 100644 docs/tutorials/pt/i-cant-update-the-ean-of-my-skus-via-api.md
 create mode 100644 docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
 create mode 100644 docs/tutorials/pt/image-compression.md
 create mode 100644 docs/tutorials/pt/indexes-in-master-data.md
 create mode 100644 docs/tutorials/pt/indexing-history.md
 create mode 100644 docs/tutorials/pt/indexing.md
 create mode 100644 docs/tutorials/pt/intelligent-synonyms.md
 create mode 100644 docs/tutorials/pt/inventory-data-pipeline-beta.md
 create mode 100644 docs/tutorials/pt/kr1-test.md
 create mode 100644 docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
 create mode 100644 docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
 create mode 100644 docs/tutorials/pt/making-a-master-data-field-editable.md
 create mode 100644 docs/tutorials/pt/managing-b2b-organizations.md
 create mode 100644 docs/tutorials/pt/managing-http-headers.md
 create mode 100644 docs/tutorials/pt/managing-projects.md
 create mode 100644 docs/tutorials/pt/managing-shipping-policies.md
 create mode 100644 docs/tutorials/pt/managing-users-in-b2b-organizations.md
 create mode 100644 docs/tutorials/pt/match-offers-mercado-livre.md
 create mode 100644 docs/tutorials/pt/mercado-libre-size-chart.md
 create mode 100644 docs/tutorials/pt/merchandising-rule-conditions.md
 create mode 100644 docs/tutorials/pt/merchandising-rules-list.md
 create mode 100644 docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md
 create mode 100644 docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md
 create mode 100644 docs/tutorials/pt/my-inventory-is-negative.md
 create mode 100644 docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md
 create mode 100644 docs/tutorials/pt/my-store-order-was-not-created.md
 create mode 100644 docs/tutorials/pt/navigation.md
 create mode 100644 docs/tutorials/pt/offer-status.md
 create mode 100644 docs/tutorials/pt/operational-capacity-beta.md
 create mode 100644 docs/tutorials/pt/orderform-settings.md
 create mode 100644 docs/tutorials/pt/orders.md
 create mode 100644 docs/tutorials/pt/overview-of-b2b-orders-history.md
 create mode 100644 docs/tutorials/pt/payments.md
 create mode 100644 docs/tutorials/pt/permissions-management-in-b2b-suite.md
 create mode 100644 docs/tutorials/pt/pickup-points-for-subscription-orders.md
 create mode 100644 docs/tutorials/pt/price-table-management-in-b2b-organizations.md
 create mode 100644 docs/tutorials/pt/prices-data-pipeline-beta.md
 create mode 100644 docs/tutorials/pt/promotions.md
 create mode 100644 docs/tutorials/pt/received-skus-beta.md
 create mode 100644 docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
 create mode 100644 docs/tutorials/pt/redirect-from-other-addresses.md
 create mode 100644 docs/tutorials/pt/redirects.md
 create mode 100644 docs/tutorials/pt/relevance-rules.md
 create mode 100644 docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
 create mode 100644 docs/tutorials/pt/requesting-a-new-organization.md
 create mode 100644 docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
 create mode 100644 docs/tutorials/pt/restrict-public-access-to-master-data-fields.md
 create mode 100644 docs/tutorials/pt/risk-assessment.md
 create mode 100644 docs/tutorials/pt/sales-associate-code-field-at-checkout.md
 create mode 100644 docs/tutorials/pt/search-behavior.md
 create mode 100644 docs/tutorials/pt/search-configuration.md
 create mode 100644 docs/tutorials/pt/security-certificate-ssl.md
 create mode 100644 docs/tutorials/pt/security-monitor.md
 create mode 100644 docs/tutorials/pt/seller-monitoring.md
 create mode 100644 docs/tutorials/pt/seller-portal-creating-a-promotion.md
 create mode 100644 docs/tutorials/pt/seller-portal-promotions.md
 create mode 100644 docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-alignetv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-appmax.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-argonpay.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-braintree.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-credimarcas.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-culqi.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-dapp.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-deuna.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-e-sitef.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-easypay-seller.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-easypay.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-evopayments.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-fintoc.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-geru.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-gocuotas.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-guatapay.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-inswitch.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-itau-rede.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-k8bank.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-liquido-payment.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-mobbex.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-msc-payment.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-notes-payable.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-nuvei.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-pagbrasilv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-paghiperv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-paghiperv3.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-pagoefectivov2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-pagoexpress.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-pay4fun.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-paymentezv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-paypalv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-payuv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-payway.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-poolpay.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-powerpay.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-safetypayv2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-stark-bank.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-stelom1v2.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-transfero-crypto-checkout.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-unlimit.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-webpayoneclick.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-wepay4u.md
 create mode 100644 docs/tutorials/pt/setting-up-payments-with-woovi.md
 create mode 100644 docs/tutorials/pt/setting-up-the-notes-payable-conector.md
 create mode 100644 docs/tutorials/pt/skus.md
 create mode 100644 docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
 create mode 100644 docs/tutorials/pt/store-overview-beta.md
 create mode 100644 docs/tutorials/pt/store-profile.md
 create mode 100644 docs/tutorials/pt/synonym-list.md
 create mode 100644 docs/tutorials/pt/test-kr1.md
 create mode 100644 docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md
 create mode 100644 docs/tutorials/pt/untitled-entry-2024-03-13-at-16-25-15.md
 create mode 100644 docs/tutorials/pt/untitled-entry-2024-07-25-at-21-25-31.md
 create mode 100644 docs/tutorials/pt/vtex-ad-network-beta.md
 create mode 100644 docs/tutorials/pt/vtex-agreement.md
 create mode 100644 docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
 create mode 100644 docs/tutorials/pt/vtex-operation-service-level-agreement-sla.md
 create mode 100644 docs/tutorials/pt/vtex-pick-and-pack-insights.md
 create mode 100644 docs/tutorials/pt/vtex-pick-and-pack-mobile.md
 create mode 100644 docs/tutorials/pt/vtex-pick-and-pack-orders.md
 create mode 100644 docs/tutorials/pt/vtex-pick-and-pack-settings.md
 create mode 100644 docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
 create mode 100644 docs/tutorials/pt/vtex-shield.md
 create mode 100644 docs/tutorials/pt/vtex-shipping-network-correios-activation.md
 create mode 100644 docs/tutorials/pt/vtex-status-page.md
 create mode 100644 docs/tutorials/pt/vtex-support-apac.md
 create mode 100644 docs/tutorials/pt/web-application-firewall-waf.md
 create mode 100644 docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md
 create mode 100644 docs/tutorials/pt/why-dont-marketplace-orders-integrate-with-my-store.md

diff --git a/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md b/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md
index becbe6b0b..8d5f2fe1e 100644
--- a/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md
+++ b/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md
@@ -21,7 +21,7 @@ This is why we created the new [Web Page Performance](https://help.vtex.com/en/v
 
 PageSpeed Insights and Lighthouse are tools developed by Google to report on the user experience of a page on both mobile and desktop devices, providing suggestions on how that page may be improved. They use [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals) as metrics to assess online user experience. 
 
-![Web page performance Dash EN](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
+![Web page performance Dash EN](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/admin-disponivel-em-japones.md b/docs/announcements/en/admin-disponivel-em-japones.md
index 58d1ad916..cff46147d 100644
--- a/docs/announcements/en/admin-disponivel-em-japones.md
+++ b/docs/announcements/en/admin-disponivel-em-japones.md
@@ -26,4 +26,4 @@ The Admin’s translation into Japanese was driven by the [opening of our new of
 
 ## What do you need to do
 To view the Admin in Japanese, select JP in the language dropdown menu in the upper right corner of the screen. 
-![Select JP](https://images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/962f59494964fb2dddfb42f557949e28/japones.png)
+![Select JP](//images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/962f59494964fb2dddfb42f557949e28/japones.png)
diff --git a/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
index e148719d3..9cbaf3a0e 100644
--- a/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -29,7 +29,7 @@ Now, users will only see the sidebar menu items they are allowed to access, acco
 
 The image below illustrates how the sidebar might change as a result of these housekeeping procedures to improve your store's security and user experience.
 
-![EN Sidebar permissions announcement screenshot](https://images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/8ffedd77b8566929fd3c39b73cad6590/EN_Sidebar_permissions_announcement_screenshot.png)
+![EN Sidebar permissions announcement screenshot](//images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/8ffedd77b8566929fd3c39b73cad6590/EN_Sidebar_permissions_announcement_screenshot.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/amazon-integration-amazon-offer-matching.md b/docs/announcements/en/amazon-integration-amazon-offer-matching.md
new file mode 100644
index 000000000..a8af10572
--- /dev/null
+++ b/docs/announcements/en/amazon-integration-amazon-offer-matching.md
@@ -0,0 +1,35 @@
+---
+title: 'Amazon integration: Amazon Offer Matching'
+id: 6cWiUoUTzVtOAVpF4XhOzm
+status: PUBLISHED
+createdAt: 2023-07-04T20:11:24.168Z
+updatedAt: 2023-07-04T21:44:36.582Z
+publishedAt: 2023-07-04T21:44:36.582Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: amazon-integration-amazon-offer-matching
+locale: en
+legacySlug: amazon-offer-matching
+announcementImageID: ''
+announcementSynopsisEN: 'Amazon offer matching is now manual. Learn more about the new page.'
+---
+
+The [integration](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon) between VTEX stores and Amazon allows sellers to send their product catalog to the marketplace, which expands their sales channels. To increase the quality of offers shown on Amazon, we created a new page for VTEX sellers to do the product matching.
+
+## What has changed?
+
+Before, when a seller sent a product to the Amazon integration, it would go through an automatic matching process to link the seller SKU to the product ASIN (Amazon Standard Identification Number) on Amazon. However, this process occasionally resulted in compatibility errors between the sent product and the published offer on Amazon.
+
+With the new matching flow, the sellers approve the matches between their products and Amazon offers. Despite matching now being a manual process, sellers can approve SKUs in bulk.
+
+## Why did we make this change?
+
+The process will now be completely manual. This change aims to reduce compatibility errors, so sellers show reliable and quality offers on the marketplace, giving sellers control over how the sent products and the published offers are matched.
+
+## What needs to be done?
+
+You can find the Amazon Offer Matching page in Marketplace > __Amazon Offer Matching__ or through the search bar. The page will be available for all VTEX accounts as of July 03, 2023. No action is required to activate it.
+
+For more information about how the page works, check the [documentation Amazon Offer Matching](https://help.vtex.com/en/tutorial/match-de-anuncios-amazon--7fRfoP69kYgg8znImMhyQ0).
+
diff --git a/docs/announcements/en/amazon-new-category-mapping-model.md b/docs/announcements/en/amazon-new-category-mapping-model.md
new file mode 100644
index 000000000..d2688bd14
--- /dev/null
+++ b/docs/announcements/en/amazon-new-category-mapping-model.md
@@ -0,0 +1,36 @@
+---
+title: 'Amazon: New category mapping model'
+id: 584nPLYkI8tnOGz1s4X5LE
+status: PUBLISHED
+createdAt: 2023-11-27T23:08:37.697Z
+updatedAt: 2023-12-18T15:49:17.763Z
+publishedAt: 2023-12-18T15:49:17.763Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: amazon-new-category-mapping-model
+locale: en
+legacySlug: amazon-new-category-mapping-model
+announcementImageID: ''
+announcementSynopsisEN: 'Check out the new category and attribute mapping model for the VTEX and Amazon integration.'
+---
+
+An important step in the [integration](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5sYA9MlRo92jJIxKF1MTXb) between VTEX stores and Amazon is mapping categories and attributes, which consists of matching the products in your catalog with the offers available on Amazon.
+
+To make the mapping process easier and more intuitive, we have developed the **[category and attribute mapping via VTEX Admin](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD?&utm_source=autocomplete#mapeamento-via-admin-vtex-beta),** which is available for VTEX stores in Brazil, Mexico, and the United States. To access the new mapping model, go to **Marketplace > Marketplaces and Integrations > Amazon > Perform Mapping.** The instructions are available in the [Mapping and sending product categories to Amazon](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) tutorial.  
+
+## What has changed?
+
+Previously, the mapping process could only be carried out [via spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD?&utm_source=autocomplete#mapeamento-via-planilha). Now, with the new mapping model, you can choose which type of mapping best meets your needs.  
+
+Here are some of the advantages of mapping categories and attributes using the VTEX Admin:  
+
+- Monitor the mapping status of each category.  
+- Search for the category on Amazon to match it with your catalog.  
+- Autofill the attributes that are already in your catalog.  
+- Customize the shipping rate template by SKU.  
+
+## What needs to be done?
+
+The feature will be available to all [VTEX accounts that act as sellers](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) from **December 18, 2023.** To use it, you need to have your VTEX account [integrated](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5sYA9MlRo92jJIxKF1MTXb) with Amazon and send the products by following the [Mapping and sending product categories to Amazon](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) tutorial.
+
diff --git a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md
index f6710a36c..37f4903d3 100644
--- a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md
+++ b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md
@@ -21,7 +21,7 @@ For example, restaurants that accept online orders usually allow customers to ch
 
 To simplify this feature, we developed the Assembly Options app, which provides an interface for configuring and managing custom options. The app is only available for stores using [VTEX IO](https://vtex.com/us-en/store-framework/).
 
-![assembly-options-app-en](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
+![assembly-options-app-en](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md
index 57ff44efe..12184a066 100644
--- a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md
+++ b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md
@@ -21,7 +21,7 @@ For example, restaurants that accept online orders usually allow customers to ch
 
 To simplify this feature, we developed the Assembly Options app, which provides an interface for configuring and managing custom options. The app is only available for stores using [VTEX IO](https://vtex.com/us-en/store-framework/).
 
-![assembly-options-app-en](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
+![assembly-options-app-en](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/autocomplete-metrics-now-available-in-search-reports.md b/docs/announcements/en/autocomplete-metrics-now-available-in-search-reports.md
index f5f8348ca..d5197ec5e 100644
--- a/docs/announcements/en/autocomplete-metrics-now-available-in-search-reports.md
+++ b/docs/announcements/en/autocomplete-metrics-now-available-in-search-reports.md
@@ -24,7 +24,7 @@ Previously it was only possible to see, and export reports on search results and
 <table width = "100%">
   <tr>
     <td>
-      <img src = "https:https://images.ctfassets.net/alneenqid6w5/34n3YHcet5J5gHNNLwLw3r/092ec32f2cc0c2f4fb8254b3327006fd/relatorios-filtros-EN.png" style = "display:block; margin-left: auto; margin-right: auto;" alt = "Opções de filtros do relatório" title = "Opções de filtros do relatório">
+      <img src = "https://images.ctfassets.net/alneenqid6w5/34n3YHcet5J5gHNNLwLw3r/092ec32f2cc0c2f4fb8254b3327006fd/relatorios-filtros-EN.png" style = "display:block; margin-left: auto; margin-right: auto;" alt = "Opções de filtros do relatório" title = "Opções de filtros do relatório">
     </td>
   </tr>
   <tr>
diff --git a/docs/announcements/en/automatic-archiving-inactive-promotions.md b/docs/announcements/en/automatic-archiving-inactive-promotions.md
new file mode 100644
index 000000000..d5a84d3ef
--- /dev/null
+++ b/docs/announcements/en/automatic-archiving-inactive-promotions.md
@@ -0,0 +1,41 @@
+---
+title: 'Automatic archiving inactive promotions'
+id: 4LDQbli98aRSNJDus7mgqi
+status: PUBLISHED
+createdAt: 2024-05-13T11:40:27.337Z
+updatedAt: 2024-05-20T12:14:24.232Z
+publishedAt: 2024-05-20T12:14:24.232Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: automatic-archiving-inactive-promotions
+locale: en
+legacySlug: automatic-archiving-inactive-promotions
+announcementImageID: ''
+announcementSynopsisEN: 'The new auto-archive feature for inactive promotions helps you manage promotions in your store.'
+---
+
+To enhance the promotion management experience, VTEX is introducing an automatic archiving feature for inactive promotions. This feature helps you organize and monitor the promotions available in your store.
+
+## What has changed?
+
+We have implemented the following improvements to the promotion management experience:
+
+**Promotion auto-archiving rules:**
+
+1. **Promotions with an end date (not activated):** These will be automatically archived 7 days after the last change, counting from the promotion end date.
+
+2. **Promotions without an end date (not activated):** These will be automatically archived 30 days after the last change.
+
+3. **Promotions with an end date (active):** These will be automatically archived 7 days after their end date.
+
+**Feature optimization:** We've improved the loading time and performance of the promotions list.
+
+<div class = "alert alert-info">
+To view the promotions that have been automatically archived, go to VTEX Admin <b>Promotions > Promotions</b>, or type <b>Promotions</b> in the search bar at the top of the page. In the top right corner, click <i class="fas fa-ellipsis-v" aria-hidden="true"></i>, and then click Applied Promotions.
+</div>
+
+## What needs to be done?
+
+No action is required. The feature to automatically archive inactive promotions is now available in all VTEX stores.
+
diff --git a/docs/announcements/en/black-week-vtex-dashboards-analysis-strategies.md b/docs/announcements/en/black-week-vtex-dashboards-analysis-strategies.md
new file mode 100644
index 000000000..b45d5de05
--- /dev/null
+++ b/docs/announcements/en/black-week-vtex-dashboards-analysis-strategies.md
@@ -0,0 +1,22 @@
+---
+title: 'Black Week: VTEX Dashboards Analysis Strategies'
+id: 1MrvvWj1ziiqLWhM021PX7
+status: PUBLISHED
+createdAt: 2023-11-20T20:29:11.550Z
+updatedAt: 2023-11-20T20:39:16.159Z
+publishedAt: 2023-11-20T20:39:16.159Z
+contentType: updates
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: black-week-vtex-dashboards-analysis-strategies
+locale: en
+legacySlug: black-week-vtex-dashboards-analysis-strategies
+announcementImageID: ''
+announcementSynopsisEN: 'Learn the best strategies for analyzing your sales metrics during Black Week with the VTEX Dashboards guide'
+---
+
+We have officially arrived at __Black Week,__ which takes place from __11/20/2023__ to __11/27/2023.__ The stores already have their campaigns online and their operations ready to attend shoppers.  
+
+Aiming to maximize opportunities for improving __Black Friday__ actions during this period, we have created a special guide focused on clarifying the most frequently asked questions related to the use of our dashboards in Admin VTEX during the most important event of the year.  
+
+See the [VTEX dashboard guide for Black Week: FAQ](https://help.vtex.com/en/tutorial/guia-de-los-dashboards-vtex-para-la-black-week-faq--6O3CiGiZctVIgIrpIcko9h) and you will find answers to the most frequently asked questions about how to use Dashboards during Black Week.  
diff --git a/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 3c39e4e17..545b1fec5 100644
--- a/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -25,7 +25,7 @@ In addition, **VTEX Pick and Pack** [collects data and analytics](https://help.v
 * [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): Control of last-mile delivery.
 * **Mobile Applications:** Applications for pickers and couriers.
 
-![pick_pack_gif_EN](https://images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/a6b1137ac375e1a046cc2a76a56e3958/pick_pack_gif_EN.gif)
+![pick_pack_gif_EN](//images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/a6b1137ac375e1a046cc2a76a56e3958/pick_pack_gif_EN.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/callback-url-signature-authentication-token.md b/docs/announcements/en/callback-url-signature-authentication-token.md
new file mode 100644
index 000000000..6c8dd7d54
--- /dev/null
+++ b/docs/announcements/en/callback-url-signature-authentication-token.md
@@ -0,0 +1,32 @@
+---
+title: 'Callback URL signature: Blocking asynchronous payment authorizations without an authentication token'
+id: 3at5YtI2L6QqBym6Af56tV
+status: PUBLISHED
+createdAt: 2024-05-03T18:12:04.996Z
+updatedAt: 2024-05-03T18:33:19.277Z
+publishedAt: 2024-05-03T18:33:19.277Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: callback-url-signature-authentication-token
+locale: en
+legacySlug: callback-url-signature-authentication-token
+announcementImageID: ''
+announcementSynopsisEN: 'Authentication token for asynchronous payment authorizations'
+---
+
+To enhance payment operations on the platform, VTEX is implementing the `X-VTEX-signature` authentication token. Payment providers and partners must use this token to report the status of asynchronous payment transactions via a [callback URL](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#callback-url).  
+
+As of May 27, 2024,  the VTEX gateway will automatically include the callback URL information and the respective authentication token with each payment transaction.
+
+Example of a callback URL containing the authentication token:
+
+`https://gatewayqa.vtexpayments.com.br/api/pvt/payment-provider/transactions/8FB0F111111122222333344449984ACB/payments/A2A9A25B11111111222222333327883C/callback?accountName=teampaymentsintegrations&X-VTEX-signature=R123456789aBcDeFGHij1234567890tk`
+
+## What needs to be done?
+
+Starting June 26, 2024, all payment providers and partners must report the status of asynchronous payment transactions exclusively via the callback URL and authentication token.
+
+After this date, any transaction status updates sent only via callback URL (without the authentication token) will be blocked, and the respective payment transactions will be canceled.
+
+For more information about the callback URL, see [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#callback-url) and [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
diff --git a/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md b/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md
index 63245e49b..923a5d91d 100644
--- a/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md
+++ b/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md
@@ -23,7 +23,7 @@ We have improved the campaign audience settings so that you can add up target au
 
 In the VTEX Admin, **Products > Promotions and Taxes > Campaign Audience > New Campaign Audience**, in the settings related to the **Target Audience**, we added the "and" option, where there was previously only the "or" option. This means that now you can apply a criteria adding logic ("and") besides the pre-existent alternative logic ("or"). Please see the image below:
 
-![publico-alvo-e-ou-en](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
+![publico-alvo-e-ou-en](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
 
 Using the new option, you can create campaign promotions flexibly combining different criteria.
 
diff --git a/docs/announcements/en/catalogs-new-visual-and-navigation.md b/docs/announcements/en/catalogs-new-visual-and-navigation.md
index 93f0b443f..a2684f479 100644
--- a/docs/announcements/en/catalogs-new-visual-and-navigation.md
+++ b/docs/announcements/en/catalogs-new-visual-and-navigation.md
@@ -23,16 +23,16 @@ The main difference to the old version is on how you navigate through it. We've
 ## What has changed
 
 Most items of the old Catalog can now be found on the _Catalog_ option, on the sidebar's _PRODUCTS_ section.
-![EN-Catálogo1](https://images.ctfassets.net/alneenqid6w5/6PWNLidc6AYwsIw4W8GcEQ/e5fb1c8e3aaf79fa05d895a920dd78c7/EN-Cat__logo1.png)
+![EN-Catálogo1](//images.ctfassets.net/alneenqid6w5/6PWNLidc6AYwsIw4W8GcEQ/e5fb1c8e3aaf79fa05d895a920dd78c7/EN-Cat__logo1.png)
 
 
 The _Gift card_ subitem (formerly known as _Vouchers_ and previously located under the _Campaign Control_ tab) is now one of the _Payments_ drop-down options, on the sidebar's _TRANSACTIONS_ section. 
-![EN-Catálogo2](https://images.ctfassets.net/alneenqid6w5/mYzfITNdIWSQ00qaewAsQ/0a9fd430c40271c4f4d6ed9574bf13fd/EN-Cat__logo2.png)
+![EN-Catálogo2](//images.ctfassets.net/alneenqid6w5/mYzfITNdIWSQ00qaewAsQ/0a9fd430c40271c4f4d6ed9574bf13fd/EN-Cat__logo2.png)
 
 
 The _Settings_ item (formerly a tab of its own) is now one of the _CMS_ drop-down options, on the sidebar's _STORE SETUP_ section. 
-![EN-Catálogo3](https://images.ctfassets.net/alneenqid6w5/5mVP1uxDzi2e28ym2o0IEO/3c72b956fb706517dacd2bc3d473550f/EN-Cat__logo3.png)
+![EN-Catálogo3](//images.ctfassets.net/alneenqid6w5/5mVP1uxDzi2e28ym2o0IEO/3c72b956fb706517dacd2bc3d473550f/EN-Cat__logo3.png)
 
 
 The former _Marketplace_ tab continues independent (even the name remains the same), with a section of its own on the sidebar.
-![EN-Catálogo4](https://images.ctfassets.net/alneenqid6w5/2BjYZAd5PKACmiiOum64O4/a9379e8f4bb1cb762b744db5a2cae42a/EN-Cat__logo4.png)
+![EN-Catálogo4](//images.ctfassets.net/alneenqid6w5/2BjYZAd5PKACmiiOum64O4/a9379e8f4bb1cb762b744db5a2cae42a/EN-Cat__logo4.png)
diff --git a/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md b/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
index 85a42b068..995df8e74 100644
--- a/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
+++ b/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
@@ -27,7 +27,7 @@ Rest assured, we made no mistake. After careful consideration, our team decided
 
 But that's not all. We also completely revamped the process to change the Sponsor user for an account, transforming it into an invitation-based transfer flow that is fully auditable. 
 
-![Sponsor management gif](https://images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/93870cb4eae7fd2591b388279faa2db9/Announcement_EN.gif)
+![Sponsor management gif](//images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/93870cb4eae7fd2591b388279faa2db9/Announcement_EN.gif)
 
 Check out [Transferring store ownership](https://help.vtex.com/en/tutorial/transferring-store-ownership) for more details on this new process.
 
diff --git a/docs/announcements/en/changes-in-vtex-support-service-policy.md b/docs/announcements/en/changes-in-vtex-support-service-policy.md
new file mode 100644
index 000000000..c20713eed
--- /dev/null
+++ b/docs/announcements/en/changes-in-vtex-support-service-policy.md
@@ -0,0 +1,18 @@
+---
+title: 'Changes in VTEX Support Service Policy'
+id: 7f5YRWJQ7q0VUGCTDKVDon
+status: PUBLISHED
+createdAt: 2024-02-16T18:37:29.587Z
+updatedAt: 2024-02-22T21:12:09.365Z
+publishedAt: 2024-02-22T21:12:09.365Z
+contentType: updates
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: changes-in-vtex-support-service-policy
+locale: en
+legacySlug: changes-in-vtex-support-service-policy
+announcementImageID: ''
+announcementSynopsisEN: 'Now, the main channel to open a ticket is the VTEX Community.'
+---
+
+<div class="alert alert-info">This content is being translated.</div>
diff --git a/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md b/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md
new file mode 100644
index 000000000..fc61fbc2a
--- /dev/null
+++ b/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md
@@ -0,0 +1,38 @@
+---
+title: 'Checkout API now supports reCAPTCHA v3'
+id: 1buRTScMhlis0LESr7g8Rt
+status: PUBLISHED
+createdAt: 2023-06-28T19:52:18.268Z
+updatedAt: 2023-08-25T23:36:39.909Z
+publishedAt: 2023-08-25T23:36:39.909Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: checkout-api-now-supports-recaptcha-v3
+locale: en
+legacySlug: checkout-api-now-supports-recaptcha-v3
+announcementImageID: ''
+announcementSynopsisEN: 'This user validation solution to prevent fake users can be used in native mobile apps and other similar integrations'
+---
+
+[reCAPTCHA](https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP) is a user validation solution that VTEX provides for all stores. It foresees scenarios where malware is used for fraud and prevents access by fake users.
+
+Besides the native storefront functionality of the VTEX platform, stores implementing their own storefronts can [integrate reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) via the Checkout API to improve security.
+
+## What has changed?
+
+Now, the Checkout API also supports score-based reCAPTCHA reCAPTCHA validation (equivalent to v3), which is suitable for native mobile apps.
+
+<div class = "alert alert-info">
+VTEX is integrated with reCAPTCHA enterprise, which offers two validation approaches: checkbox (equivalent to reCAPTCHA v2) and score-based (equivalent to reCATPCHA v3). See this article on <a href="https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-versions">reCAPTCHA at VTEX Checkout</a> to learn what version you should use depending on your storefront characteristics. You can also learn more each method: <a href="https://developers.google.com/recaptcha/docs/display">reCAPTCHA v2</a> or <a href="https://developers.google.com/recaptcha/docs/v3">reCAPTCHA v3</a> with the documentation provided by Google.
+</div>
+
+However, the reCAPTCHA checkbox (equivalent to v2) integration option is still available and is the recommended option if you want to implement a [reCAPTCHA integration](https://developers.vtex.com/docs/guides/recaptcha) other than in a native mobile app.
+
+Currently, score-based validation is not available for native VTEX storefronts - it is expected to be in the coming months. This solution is only available for integrations based on the Checkout API.
+
+## What needs to be done?
+
+If you use a native VTEX storefront solution or integrate with reCAPTCHA checkbox via the Checkout API, no action is required. reCAPTCHA will continue working as configured.
+
+If you want to implement reCAPTCHA in a native mobile app storefront, you should use score-based validation. Contact your development team and see the [reCAPTCHA integration guide](https://developers.vtex.com/docs/guides/recaptcha).
diff --git a/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
index c5edb4390..5ff9b8954 100644
--- a/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
@@ -45,7 +45,7 @@ To check if the anti-fraud solutions configured in your store allow changing the
 2. In the **Payments** module, click on **Settings > Gateway affiliations**. 
 3. After selecting the desired anti-fraud solution, check if the **Cardholder document field** option is available on the configuration screen.
 
-![cardholder document field](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/350f0aaab8c88555c89a9ca3f2304f6c/cardholder_document_field.png)
+![cardholder document field](//images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/350f0aaab8c88555c89a9ca3f2304f6c/cardholder_document_field.png)
 
 <div class = "alert alert-warning">
   If the <b>Cardholder document field</b> option is not available on the configuration screen of your anti-fraud solution provider, the <b>Cardholder document</b> field will still be displayed at Checkout in your store, and the customer will be required to fill it out.
diff --git a/docs/announcements/en/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md b/docs/announcements/en/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
new file mode 100644
index 000000000..c71f9ab4b
--- /dev/null
+++ b/docs/announcements/en/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
@@ -0,0 +1,29 @@
+---
+title: 'Convert abandoned checkouts into sales with WhatsApp AI Campaigns'
+id: 4pzBvWuadV753AdCqPhoVS
+status: PUBLISHED
+createdAt: 2024-06-26T11:08:16.663Z
+updatedAt: 2024-06-26T11:27:29.365Z
+publishedAt: 2024-06-26T11:27:29.365Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns
+locale: en
+legacySlug: convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns
+announcementImageID: ''
+announcementSynopsisEN: 'WhatsApp AI Campaigns boost sales by recovering abandoned checkouts.'
+---
+
+We have developed a new feature: WhatsApp AI Campaigns. This new feature allows merchants to automatically send personalized reminders via WhatsApp to users who have not completed their orders.
+
+These reminders are designed to motivate users to return to the payment page and complete their transactions, thus improving the shopping experience and boosting sales.
+
+The new WhatsApp AI Campaigns feature offers improvements such as:
+- **Custom messages:** Sends custom messages to users who haven't completed their orders.
+- **Real-time monitoring:** Allows you to monitor campaign performance in real time via the VTEX dashboard.
+- **Quick configuration:** Enables the feature without any coding.
+- **Redirection after expiration:** Allows the user to be redirected to checkout even after their session has expired.
+
+## What needs to be done?
+The feature is now available for all stores using [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) that don't have Checkout customizations.  To implement it in your store, go to [Recovering abandoned checkouts with WhatsApp AI Campaigns](https://help.vtex.com/en/tutorial/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns--20i0zLQHt72LKzVEmk1CRZ?&utm_source=autocomplete).
diff --git a/docs/announcements/en/coupon-experience-improvements.md b/docs/announcements/en/coupon-experience-improvements.md
index 1d736b70b..91f36f140 100644
--- a/docs/announcements/en/coupon-experience-improvements.md
+++ b/docs/announcements/en/coupon-experience-improvements.md
@@ -27,7 +27,7 @@ The new [Coupons](https://help.vtex.com/en/tutorial/cupons-beta--1aAEN3ADpz19ss5
 
 The new [coupon list](https://help.vtex.com/en/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ) shows all the existing coupons in your store. This allows you to manage coupon data and analyze in which orders they were used.
 
-![listacupons en](https://images.ctfassets.net/alneenqid6w5/3EL3TmEa9iBuABSPWAkT0B/1cfe126f85df72b7c9e30f8e4cb85606/listacupons_en.gif)
+![listacupons en](//images.ctfassets.net/alneenqid6w5/3EL3TmEa9iBuABSPWAkT0B/1cfe126f85df72b7c9e30f8e4cb85606/listacupons_en.gif)
 
 ### Easier access to coupon codes
 
@@ -44,7 +44,7 @@ The new filters allow you to view coupons that meet specific criteria. The avail
 - Last modified
 - Coupon type
 
-![filtroscupons en](https://images.ctfassets.net/alneenqid6w5/5ImK8Og5MsOnruVxkwblJ6/b2abce2b73d9facd5edcf6f589dad039/filtroscupons_en.gif)
+![filtroscupons en](//images.ctfassets.net/alneenqid6w5/5ImK8Og5MsOnruVxkwblJ6/b2abce2b73d9facd5edcf6f589dad039/filtroscupons_en.gif)
 
 ### Coupon groups for agile management
 
diff --git a/docs/announcements/en/custom-selection-of-sellers-for-b2b-purchases.md b/docs/announcements/en/custom-selection-of-sellers-for-b2b-purchases.md
new file mode 100644
index 000000000..82cd314a7
--- /dev/null
+++ b/docs/announcements/en/custom-selection-of-sellers-for-b2b-purchases.md
@@ -0,0 +1,32 @@
+---
+title: 'Custom selection of sellers for B2B purchases'
+id: 2AezDuup65tH3MyBBWDasG
+status: PUBLISHED
+createdAt: 2023-12-21T13:29:04.048Z
+updatedAt: 2023-12-21T18:13:37.674Z
+publishedAt: 2023-12-21T18:13:37.674Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: custom-selection-of-sellers-for-b2b-purchases
+locale: en
+legacySlug: custom-selection-of-sellers-for-b2b-purchases
+announcementImageID: ''
+announcementSynopsisEN: 'The seller allocation feature allows buying organizations to have their purchase orders fulfilled by specific sellers.'
+---
+
+ VTEX is launching a new feature that allows buying organizations (B2B) to select an exclusive group of sellers to fulfill their purchase orders.
+
+## What has changed?
+
+Now, each buying organization will be able to determine which sellers can display products to their customers during the purchasing process.
+
+## Why did we make this change?
+
+To enable a more streamlined, centralized buying experience that gives buyers direct access to the products of selected sellers.
+
+## What needs to be done?
+
+No action is required. The feature is available for all stores.
+For more information on how to create a new seller allocation, read the [Configuring seller allocation for buying organizations (B2B)](https://help.vtex.com/pt/tutorial/configurando-atribuicao-de-sellers-a-organizacoes-compradoras-b2b-xky--3VJtKNbLpVAl71uVdaOqpE) article.
+
diff --git a/docs/announcements/en/discontinuation-of-legacy-payment-connectors.md b/docs/announcements/en/discontinuation-of-legacy-payment-connectors.md
new file mode 100644
index 000000000..066a94882
--- /dev/null
+++ b/docs/announcements/en/discontinuation-of-legacy-payment-connectors.md
@@ -0,0 +1,88 @@
+---
+title: 'Discontinuation of legacy payment connectors'
+id: 11SHyRwcAr4fs46K7PccOr
+status: PUBLISHED
+createdAt: 2024-03-15T10:19:40.450Z
+updatedAt: 2024-04-08T19:55:00.286Z
+publishedAt: 2024-04-08T19:55:00.286Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: discontinuation-of-legacy-payment-connectors
+locale: en
+legacySlug: discontinuation-of-legacy-payment-connectors
+announcementImageID: ''
+announcementSynopsisEN: 'Legacy payment connectors will be removed from the VTEX platform'
+---
+
+As another step in the process of [discontinuing legacy payment connectors](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14), the table below lists the legacy connectors that will be removed from the VTEX platform and the new connectors (integrated via Payment Provider Protocol) that are available to replace them:
+
+| **Legacy connector** | **New version (PPP connector)** |
+| :---: | :---: |
+| Adyen | AdyenV3 |
+| Alignet | AlignetV2 |
+| Amex | - |
+| AuthorizeNet/AuthorizeDotNet | - |
+| BanamexInvoice | - |
+| BankInvoiceItau/BankIssuedInvoiceItau | MaxiPagoV4 |
+| BankInvoiceSantander/BankIssuedInvoiceSantander | Egetnet |
+| Bcash | - |
+| BoldCron | - |
+| Bradesco/RegisteredBankInvoiceBradesco | - |
+| Braspag/BraspagV2 | CieloEcommerce |
+| Cielo/CieloV3 | CieloEcommerce |
+| Conductor | - |
+| Credomatic | - |
+| CyberSource | Cybersource IO |
+| Decidir/DecidirV1 | Payway |
+| ERede/E-Rede V2/ERedeRest | Itaú Rede |
+| Evolucard | - |
+| Firstdata | - |
+| IPay88 | - |
+| ItauShopline | MaxiPagoV4 |
+| Koin | Koin-Payments |
+| MaxiPago | MaxiPagoV4 |
+| MeoWallet | - |
+| MercadoPagoV1 | MercadoPagoV2 |
+| MobilPay | - |
+| Moip | YamiSplitMoipV1 |
+| MOLPay | - |
+| Mundipagg/MundipaggFraudPrevention | PagarmeV3 |
+| Nexxpago | - |
+| NPS | - |
+| PagamentoDigital | - |
+| PagBrasil | PagBrasilV2 |
+| PagHiper | PagHiperV2 or PagHiperV3 |
+| PagoEfectivo | PagoEfectivoV2  |
+| PagosNet | - |
+| PagosWeb | - |
+| PagSeguro/PagSeguroDirect | - |
+| PayClub | - |
+| Payme | PayMee |
+| Paymentez | PaymentezV2 |
+| PaymentHub | - |
+| PaymentsOS | PayUv2 |
+| PayPal/PayPalPlus | PayPalV2 |
+| PayU/PayUGlobal | PayUv2 |
+| Payzen | - |
+| Place2Pay/PlaceToPay | PlaceToPayLatam |
+| Rede Pay/RedePay | Itaú Rede |
+| Redecard | Itaú Rede |
+| Redsys/RedsysV2 | - |
+| SafetyPay | SafetyPayV2 |
+| SalesMachine | - |
+| Scopus | - |
+| Sitef/SitefDirectSale/SitefPreauth | ESITEF |
+| Stelo | SteloM1V2 |
+| TNSPay | EvoPayments |
+| TodoPago | - |
+| WebPay/WebPay2P | - |
+| WorldPay | Worldpay-Payments-Via-WPG |
+
+## What needs to be done?
+
+If your store uses any of the legacy connectors listed above, complete the specific actions that apply to each connector:
+
+- __Legacy connector does not yet have a corresponding PPP connector available__: Open a ticket with [VTEX Support](https://help.vtex.com/en/support) so that the CX team assigned to your account can assist you in checking which available PPP connectors are best suited to your type of operation and can be configured in your store.
+
+- __PPP connector available to replace legacy connector__: Contact your payment provider for more information about the migration process and setting up the new connector in your store.
diff --git a/docs/announcements/en/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md b/docs/announcements/en/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
new file mode 100644
index 000000000..97f97a64a
--- /dev/null
+++ b/docs/announcements/en/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
@@ -0,0 +1,30 @@
+---
+title: 'Discover the new feature that allows bulk data import for organizations and cost centers'
+id: 6XwSfF6YYjIiIDoxR3NoDN
+status: PUBLISHED
+createdAt: 2024-04-29T17:36:01.588Z
+updatedAt: 2024-05-21T14:07:17.423Z
+publishedAt: 2024-05-21T14:07:17.423Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and
+locale: en
+legacySlug: discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and
+announcementImageID: ''
+announcementSynopsisEN: 'Make organization management easier: Bulk Import streamlines data updates and maintenance'
+---
+
+VTEX now offers a new feature for bulk data import, designed to streamline the process of updating and maintaining information for buyer organizations, their users (members), and cost centers.
+
+## What has changed?
+
+From now on, stores using the [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite) can import buyer organizations, cost centers, and members using a **XLSX file** or the [Bulk Import API](https://developers.vtex.com/docs/api-reference/buyer-organizations?endpoint=overview). 
+
+## Why did we make this change?
+
+Our aim is to make data management in buyer organizations more efficient.
+
+## What needs to be done?
+
+No action is required. The feature will be available to all stores with the B2B Suite app installed.
diff --git a/docs/announcements/en/displaying-pickup-points-on-google-maps.md b/docs/announcements/en/displaying-pickup-points-on-google-maps.md
index 2c7dad755..5962c0512 100644
--- a/docs/announcements/en/displaying-pickup-points-on-google-maps.md
+++ b/docs/announcements/en/displaying-pickup-points-on-google-maps.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'An application that lists pickup locations and displays
 
 One of the most common features of websites and online stores is a map showing the location of physical stores. The new[ Store Locator](https://apps.vtex.com/vtex-store-locator/p#overview) app allows stores developed with VTEX IO to list their pickup points on Google Maps and show them as markers on a map.
 
-![Maps](https://images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
+![Maps](//images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
 
 ## What changed?
 
diff --git a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md
index bed3eb7ce..3985e2bfc 100644
--- a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md
+++ b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Promotion summary allows you to review information abou
 
 Mistakes can happen when configuring a new promotion and filling in information. To avoid activating promotions with incorrect information, we created the promotion summary. The new feature allows you to confirm the promotion settings before activating it.
 
-![resumo-promo-EN](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
+![resumo-promo-EN](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
 
 ## What has changed?
 Previously, a promotion was automatically activated when saved with **Active** status. With the new feature, you can view a summary of the settings configured before activating a new promotion. This allows you to make sure that all data in the promotion is correct, avoiding implementation errors.
diff --git a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
index f1f18d0af..297af14e5 100644
--- a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
+++ b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Promotion summary allows you to review information abou
 
 Mistakes can happen when configuring a new promotion and filling in information. To avoid activating promotions with incorrect information, we created the promotion summary. The new feature allows you to confirm the promotion settings before activating it.
 
-![resumo-promo-EN](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
+![resumo-promo-EN](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
 
 ## What has changed?
 Previously, a promotion was automatically activated when saved with **Active** status. With the new feature, you can view a summary of the settings configured before activating a new promotion. This allows you to make sure that all data in the promotion is correct, avoiding implementation errors.
diff --git a/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 9689ce484..3683313d2 100644
--- a/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -25,7 +25,7 @@ The application is available in the [VTEX App Store](https://apps.vtex.com "VTEX
 - Allows you to moderate reviews: approve product reviews before they are published on the product page;
 - Allows you to configure your store to enable anonymous reviews.
 
-![Reviews and Ratings - Printscreen](https://images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
+![Reviews and Ratings - Printscreen](//images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
 
 ## What are the advantages?
 - Allows your customer to be more confident and assertive when shopping, based on ratings from other users;
diff --git a/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 3ced52386..ce9c241f8 100644
--- a/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -38,6 +38,6 @@ In order to do this, you need to add a product called `Order Authorization` to t
 6. Choose the type of permission you wish to grant: either `Save Configuration` if you want to allow the user to edit and save changes, or `View Configuration` if you want the user to only view the Order Authorization page.
 7. Finally, click on **Save**.
 
-![GIT-OrderAutho.en](https://images.ctfassets.net/alneenqid6w5/1K34RexhGDYnU2ogYWsH6L/5214f0861ae9a92073005c074ab5c128/GIT-OrderAutho.en.gif)
+![GIT-OrderAutho.en](//images.ctfassets.net/alneenqid6w5/1K34RexhGDYnU2ogYWsH6L/5214f0861ae9a92073005c074ab5c128/GIT-OrderAutho.en.gif)
 
 Upon adding this new product to a profile, ensure that the desired users are in fact linked to this profile.
diff --git a/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
index 36a51bb50..8fd6229b8 100644
--- a/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -3,8 +3,8 @@ title: 'Extensions Hub: Expand your operation through the VTEX Admin'
 id: 4FYJCHTttMa0znV1mdHW9w
 status: PUBLISHED
 createdAt: 2023-05-31T22:15:06.695Z
-updatedAt: 2023-06-04T22:02:53.542Z
-publishedAt: 2023-06-04T22:02:53.542Z
+updatedAt: 2023-08-02T14:37:08.083Z
+publishedAt: 2023-08-02T14:37:08.083Z
 contentType: updates
 productTeam: Apps
 author: 4ubliktPJIsvyl1hq91RdK
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'The new VTEX Admin section to find partners, add featur
 
 Extensions Hub is a new section of VTEX Admin that gathers partner developers and merchants who want to expand their operation capabilities. Through Extensions Hub, partners can publish extensions, and merchants can view, purchase, install, and manage them. Extensions Hub will be available globally in all VTEX stores during the third quarter (Q3) of 2023. If you want to enable Extensions Hub in your store immediately, you can request it by [opening a ticket to our support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM).
 
-![Extensions Hub GIF](https://images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e48b0ef19071288b6ed0cf7f6880dc16/Extensions_Hub.gif)
+![Extensions Hub GIF](//images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e48b0ef19071288b6ed0cf7f6880dc16/Extensions_Hub.gif)
 
 ## What has changed?
 
@@ -49,7 +49,7 @@ The [Partner Portal website](https://partnerportal.vtex.com/) will remain unchan
 
 Extensions Hub will be available for all stores in the third quarter (Q3) of 2023. If you want to enable Extensions Hub in your store immediately, you can request it by [opening a ticket to our support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM). Then, to start using the Extensions Hub, access it in your Admin. On the VTEX Admin left side menu, click the **Extensions** icon, and the Extensions Hub will be visible at the top of the menu.
 
-![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
+![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
 
 ## Why did we make this change?
 
@@ -59,4 +59,6 @@ Additionally, we have redesigned the app shopping experience in the **App Store*
 
 Finally, our goal is to strengthen the relationship between merchants and VTEX partners. Thus, merchants who want to implement unique store solutions can now directly find and contact partners and developers through the **Partners** page in the VTEX Admin.
 
-Learn more in our [Extensions Hub documentation](https://help.vtex.com/es/tracks/extensions-hub--AW7klkYMh557y5IUOgzco).
+Learn more in our [Extensions Hub documentation](https://help.vtex.com/en/tracks/extensions-hub--AW7klkYMh557y5IUOgzco).
+
+_\*Updated on August 2, 2023: The **Partners** page will be available later. There is no expected date when this page will be available._
diff --git a/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
new file mode 100644
index 000000000..5ca356c1b
--- /dev/null
+++ b/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -0,0 +1,70 @@
+---
+title: 'FastCheckout: Boost your conversion with the new checkout'
+id: 1sOAAmRehyJ1YkzbG4BkE2
+status: PUBLISHED
+createdAt: 2024-04-03T18:54:06.111Z
+updatedAt: 2024-04-23T10:00:03.018Z
+publishedAt: 2024-04-23T10:00:03.018Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: fastcheckout-boost-your-conversion-with-the-new-checkout
+locale: en
+legacySlug: fastcheckout-boost-your-conversion-with-the-new-checkout
+announcementImageID: ''
+announcementSynopsisEN: 'Introducing FastCheckout: Checkout innovation for custom, high-converting experiences.'
+---
+
+Committed to continuously innovating and delivering excellence to our clients, VTEX introduces **FastCheckout**, the latest evolution of our checkout. This new solution allows us to create custom checkout experiences with high conversion rates and is constantly updated with new features.
+
+![fastcheckout](//images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/15f7c568ca3e481a52d3c93ecc9865bf/image.png)
+
+## What has changed?
+
+Previously, VTEX Checkout provided an outdated experience for clients and did not follow market innovation standards. Besides, all customization required CSS and Javascript code.
+
+Now, to provide a more dynamic client experience, we have significantly improved the following aspects of VTEX Checkout:
+
+- Experience optimized for conversion, based on research on the best user experiences according to the[ Baymard Institute](https://baymard.com/).
+- Support for high-end omnichannel options.
+- High performance, even in carts with multiple items.
+- Customizable layout and features.
+- Optimization for mobile and desktop devices.
+- Continuous updates to offer the best experience by examining new features.
+- Option to place an order without registering.
+- Option to accept multiple coupons by default.
+
+### Easy customization
+
+FastCheckout allows you to create a customizable checkout experience, adapting to the contexts and needs of your store. In FastCheckout, you can customize the following features via Admin, without any coding:
+
+- Add the store logo to the checkout.
+- Customize the checkout button and menu colors.
+- Set limits for order quantities and cart total amount.
+- Hide or add the **promo code**, **estimated shipping**, and **SKU price display** elements.
+- Configure Adobe Analytics and Google Maps API.
+- Add a text description you want to display to the customer.
+- Deactivate and activate tax information within the **order summary**.
+
+We allow you to add fully custom elements, without having to be familiar with JavaScript or CSS.
+
+<div class="alert alert-warning">
+  <p>The first version released of FastCheckout allows limited customization. Soon, you will be able to fully customize the content using the FastStore Platform extensions.</p>
+</div>
+
+### New purchase flow
+
+The new purchase flow in FastCheckout is designed to be dynamic and intuitive, providing your customers with a more fluid and streamlined buying experience. We've made the checkout process more efficient with clear steps and intuitive navigation.
+
+![GIFCheckout](//images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/0f6cf76a12a01a77905195ba835d5028/GIFCheckout.gif)
+
+## Why did we make this change?
+
+The redesigned checkout aims to boost store conversions and simplify the customization of the checkout experience. FastCheckout offers fluid and intuitive navigation, ensuring a smoother buying experience.
+
+We have made customization significantly easier, adapting the user experience to the specific needs of the Admin.
+
+## What needs to be done?
+
+To join the FastCheckout early access program, please contact [our support](https://support.vtex.com/hc/en/requests). The VTEX team will contact you and assess whether the features available in this first release meet your needs. If so, you will be invited to join our beta program, and all users in your store account will be upgraded to the new experience. No additional configuration is required.
+
diff --git a/docs/announcements/en/faster-customer-support-with-new-solutions-for-vtex-clients.md b/docs/announcements/en/faster-customer-support-with-new-solutions-for-vtex-clients.md
new file mode 100644
index 000000000..1a762eb81
--- /dev/null
+++ b/docs/announcements/en/faster-customer-support-with-new-solutions-for-vtex-clients.md
@@ -0,0 +1,35 @@
+---
+title: 'Faster Customer Support with New Solutions for VTEX Clients'
+id: 2ofvmblxC8uksroSiWmna0
+status: PUBLISHED
+createdAt: 2023-06-29T13:08:03.574Z
+updatedAt: 2023-06-29T13:23:21.815Z
+publishedAt: 2023-06-29T13:23:21.815Z
+contentType: updates
+productTeam: Billing
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: faster-customer-support-with-new-solutions-for-vtex-clients
+locale: en
+legacySlug: faster-customer-support-with-new-solutions-for-vtex-clients
+announcementImageID: ''
+announcementSynopsisEN: "Now, you'll have access to a service bot powered by extensive platform knowledge."
+---
+
+We are excited to introduce the latest customer service solution from VTEX. Now, you'll have access to a service bot powered by extensive platform knowledge. With Artificial Intelligence, you will enjoy **prompt and wait-free assistance**, with **tailored conversational capabilities **to meet your demands.
+
+### What has changed?
+
+When opening a [support ticket](https://help.vtex.com/en/support) of type 'Technical', you will have access to a new real-time conversation screen with the VTEX bot where you can clarify any doubt about the platform. The bot supports **multiple languages** and has been trained with **all the VTEX available knowledge base**.
+
+Even with this new support option, you can choose at any moment to **continue the assistance with our Support team of experts**, following the SLAs defined in your [region's service policy](https://help.vtex.com/en/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe).
+
+### Limited availability in beta version
+
+This is a beta version of the service. Initially, the bot will only be available in selected regions.
+
+Important points to consider:
+
+- Conversations may be shared with third-party software to improve our service.
+- Do not share information that could identify your account, company, customers, employees, or your company's confidential information via chat.
+- We are committed to continually improving bot responses. However, it may occasionally provide inconsistent information. You can continue to count on our Help Center, Developer Portal and calls for our support.
+
diff --git a/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md b/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md
index bd11a29f0..0c41c9558 100644
--- a/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md
+++ b/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md
@@ -20,7 +20,7 @@ It is now possible to create Price Tables in a more intuitive, practical and fas
 ## What changes
 Before, to create a Price Table, it was necessary to acess the Prices module filter and enter the name of the table to be created. Now, we've added a new __Price Table__ button that allows you to create and select the price table you want to view.
 
-![Annoucement Price Table EN](https://images.ctfassets.net/alneenqid6w5/2TtSjOmyXMNNA523PqsQxB/3d2711e543c6bef5aa0c5cadf231d0a7/Annoucement_Price_Table_EN.png)
+![Annoucement Price Table EN](//images.ctfassets.net/alneenqid6w5/2TtSjOmyXMNNA523PqsQxB/3d2711e543c6bef5aa0c5cadf231d0a7/Annoucement_Price_Table_EN.png)
 
 ## Advantages
 
diff --git a/docs/announcements/en/get-more-agility-managing-your-orders-events-with-feed-v3.md b/docs/announcements/en/get-more-agility-managing-your-orders-events-with-feed-v3.md
index 2aeb5354f..6a4cbf8f5 100644
--- a/docs/announcements/en/get-more-agility-managing-your-orders-events-with-feed-v3.md
+++ b/docs/announcements/en/get-more-agility-managing-your-orders-events-with-feed-v3.md
@@ -3,8 +3,8 @@ title: 'Get more agility managing your orders events with Feed v3'
 id: 49FssyfGcJfvGfrb3JQjVr
 status: PUBLISHED
 createdAt: 2019-02-18T19:55:07.210Z
-updatedAt: 2019-12-31T15:13:12.603Z
-publishedAt: 2019-12-31T15:13:12.603Z
+updatedAt: 2024-01-03T18:00:45.130Z
+publishedAt: 2024-01-03T18:00:45.130Z
 contentType: updates
 productTeam: Post-purchase
 author: 6AcGyun1hSWewU8YcaQiO
@@ -31,6 +31,5 @@ Once they are independent solutions, a migration is not needed and you can enabl
 
 ## What do you need to do
 
-Find the step-by-step for the Feed v3 setup in our [Order Management Feed v3](https://help.vtex.com/en/tutorial/orders-management-feed-v3)
-
+Find the setuo step-by-step in [Feed v3](https://developers.vtex.com/docs/guides/orders-feed).
 
diff --git a/docs/announcements/en/get-to-know-the-new-vtex-status-page.md b/docs/announcements/en/get-to-know-the-new-vtex-status-page.md
new file mode 100644
index 000000000..2a54d89b7
--- /dev/null
+++ b/docs/announcements/en/get-to-know-the-new-vtex-status-page.md
@@ -0,0 +1,36 @@
+---
+title: 'Get to know the new VTEX Status page'
+id: 7n6kl6CftvChNUU1BJFmqw
+status: PUBLISHED
+createdAt: 2023-12-22T13:42:40.056Z
+updatedAt: 2023-12-22T13:57:46.734Z
+publishedAt: 2023-12-22T13:57:46.734Z
+contentType: updates
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: get-to-know-the-new-vtex-status-page
+locale: en
+legacySlug: get-to-know-the-new-vtex-status-page
+announcementImageID: ''
+announcementSynopsisEN: 'Rediseñamos la página VTEX Status, optimizando la transparencia y la comunicación eficaz de incidentes y mantenimiento.'
+---
+
+Working on incidents is crucial to the tenant experience, which is why we've made the process as transparent and informative as possible. We've redesigned the platform's status page ([status.vtex.com](https://status.vtex.com/)) to improve how we communicate maintenance events and incidents.
+
+## What has changed?
+
+Previously, we faced challenges by categorizing incidents into four components: Checkout, WebStore, Administrative Environment, and Internal Modules. In some situations, the broad categorization did not accurately reflect the real impact of the incident. For example, an issue with a payment connector could be tagged as a problem in the Checkout component, leading to miscommunication about the extent of the issue.
+
+Now, we have introduced 18 more specific components, grouped into four categories: Storefront, Checkout, Admin, and Developer Tools. This approach focuses not only on our internal architecture but mainly on where merchants can see the symptoms. The following image shows all the components displayed on the new page:
+
+![status-page-vtex](//images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/c79f37753e6a20025ad5b529a7c43e99/status-page-vtex.png)
+
+Check out the [VTEX Status page](https://help.vtex.com/en/tutorial/vtex-status-page--gPhqDn9IQ3c67wbJEX3JJ) article for more information on each component.
+
+## Why did we make this change?
+
+We have updated the platform's status page to provide a more transparent and contextualized communication experience during and after incidents and scheduled maintenance, allowing merchants to better understand the real impact on their operations.
+
+## What needs to be done?
+
+Access the new page at [status.vtex.com](https://status.vtex.com/) and read the [VTEX Status page](https://help.vtex.com/en/tutorial/vtex-status-page--gPhqDn9IQ3c67wbJEX3JJ) guide for more details.
diff --git a/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md b/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
index 7c3522bd4..20ba839f1 100644
--- a/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
+++ b/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
@@ -21,4 +21,4 @@ As in previous years, we came up with a guide with recommendations and exclusive
 
 The guide is available to all our clients and partners and may be accessed through the homepage of your Admin or directly through the URL `https://{AccountName}.myvtex.com/admin/blackfriday`. Just replace `{AccountName}` with your store's Account Name.
 
-![Announcement Cartilha BF - EN](https://images.ctfassets.net/alneenqid6w5/1qu1Wg1MFyc0aCCeA6AimE/7f7644728fe95b415ea45bf1203a17f3/Announcement_Cartilha_BF_-_EN.png)
+![Announcement Cartilha BF - EN](//images.ctfassets.net/alneenqid6w5/1qu1Wg1MFyc0aCCeA6AimE/7f7644728fe95b415ea45bf1203a17f3/Announcement_Cartilha_BF_-_EN.png)
diff --git a/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md b/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
index f0e731833..e4260f363 100644
--- a/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
+++ b/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
@@ -27,4 +27,4 @@ https://{AccountName}.myvtex.com/admin/shopping-season
 
 Simply replace `{AccountName}` with your store's Account Name, as in the image below.
 
-![Shopping Season Guidelines - 2022 - EN](https://images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/4e64d85173498b710da6706438fb100a/Screen_Shot_2022-10-19_at_18.14.44.png)
+![Shopping Season Guidelines - 2022 - EN](//images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/4e64d85173498b710da6706438fb100a/Screen_Shot_2022-10-19_at_18.14.44.png)
diff --git a/docs/announcements/en/google-catalog-migration.md b/docs/announcements/en/google-catalog-migration.md
new file mode 100644
index 000000000..d962b2d29
--- /dev/null
+++ b/docs/announcements/en/google-catalog-migration.md
@@ -0,0 +1,42 @@
+---
+title: 'Google catalog migration'
+id: 5dwWSG8NVTSXpylGZC67FU
+status: PUBLISHED
+createdAt: 2024-05-22T19:50:50.806Z
+updatedAt: 2024-05-22T20:16:57.592Z
+publishedAt: 2024-05-22T20:16:57.592Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: google-catalog-migration
+locale: en
+legacySlug: google-catalog-migration
+announcementImageID: ''
+announcementSynopsisEN: 'Integrate with Google Shopping without losing the relevance of your ads.'
+---
+
+We have developed the **Google catalog migration** feature to map and match sellers' products in the VTEX catalog with their ads on Google Shopping.
+
+This feature is designed for sellers who previously integrated their store's products with Google via an external platform and are now using the [Google Shopping connector](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw) on VTEX.
+
+## Why did we develop this feature?
+
+This feature enables sellers to maintain the relevance of their Google Shopping ads. By migrating your integration to the VTEX connector, you preserve the relevance history of your ads.
+
+<div class="alert alert-info">
+Catalog migration maps and matches products in the VTEX catalog with the existing ads in the Google Merchant Center.
+</div>
+
+Catalog migration maps and matches products in the VTEX catalog with the existing ads in the Google Merchant Center.
+
+## What needs to be done?
+
+To proceed with the migration, contact [VTEX Support](https://help.vtex.com/pt/support). However, you must first complete the following two requirements:
+
+1. Create a new trade policy without any associated products.
+2. Set up the integration with Google Shopping using the trade policy created in the previous step.
+
+After these steps, contact VTEX Support to request the migration. We will respond within four working days.
+
+Once the migration is complete, you can add the SKUs you wish to advertise on Google Shopping to the integration’s trade policy.
+
diff --git a/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md b/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md
new file mode 100644
index 000000000..95ed6673c
--- /dev/null
+++ b/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md
@@ -0,0 +1,36 @@
+---
+title: 'Google Pay: New payment method available on VTEX'
+id: 4HWD5UwH4FsjUyOqDcOFiX
+status: PUBLISHED
+createdAt: 2023-06-20T18:18:22.678Z
+updatedAt: 2023-06-28T13:00:03.123Z
+publishedAt: 2023-06-28T13:00:03.123Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: google-pay-new-payment-method-available-on-vtex
+locale: en
+legacySlug: google-pay-new-payment-method-available-on-vtex
+announcementImageID: ''
+announcementSynopsisEN: 'Google Pay integration on VTEX: Fast and secure checkout with a single click.'
+---
+
+Google Pay payment is now available for VTEX stores. This new native integration allows merchants to provide customers with a faster and more secure checkout experience.
+
+Google Pay uses Tokens instead of actual card numbers linked to the user's device. This increases approval rates and significantly reduces fraud. 
+
+Additionally, it has millions of registered cards stored securely in the Google Wallet, making them available for one-click payments on any website or app that offers the "Pay with Google Pay" button.
+
+## What has changed?
+
+Google Pay is a digital wallet platform and online payment system developed by Google to enable in-app and tap-to-pay purchases on mobile devices, allowing users to pay via Android phones, tablets, or watches.
+
+Now, you can add Google Pay as a payment method to your store, giving customers a faster and more convenient checkout process.
+
+![google-pay-checkout-en](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b0a0e3b391668b1fcf2df8d3dc33a3f7/image.png)
+
+## What needs to be done?
+
+First, read the [Google Pay and Wallet APIs Acceptable Use Policy](https://payments.developers.google.com/terms/aup) to check the types of products and services that cannot be used with Google Pay.
+
+To enable Google Pay as a payment method in your store, follow our [Google Pay](https://help.vtex.com/en/tracks/carteira-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/61JMBvM5Vanqj6RaJsP8CT) article.
diff --git a/docs/announcements/en/google-shopping-new-option-to-submit-prices.md b/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
new file mode 100644
index 000000000..b1ccfd02f
--- /dev/null
+++ b/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
@@ -0,0 +1,40 @@
+---
+title: 'Google Shopping: New option to submit prices'
+id: 4qtyADXxyaUCbOD498K14l
+status: PUBLISHED
+createdAt: 2023-12-13T23:27:59.782Z
+updatedAt: 2023-12-14T13:10:09.812Z
+publishedAt: 2023-12-14T13:10:09.812Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: google-shopping-new-option-to-submit-prices
+locale: en
+legacySlug: google-shopping-new-option-to-submit-prices
+announcementImageID: ''
+announcementSynopsisEN: 'Update your integration: New ways to apply discounts on Google Shopping.'
+---
+
+We have updated the way you can submit product prices via the [Google Shopping integration](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG), enabling merchants to offer more attractive offers and discounts using [payment methods](https://help.vtex.com/en/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) that best meet their customer needs.
+
+## What has changed?
+
+Previously, merchants could see the **Consider discount for boleto payment in the submitted price** option when setting up [Google Shopping integration](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG), which has been replaced by the __Apply discount to submitted price__ option. With the update, VTEX stores can use one of the two options below to configure the price sent to Google Shopping:
+- __Submit base price (for discount prices):__ Only displays products with a [list price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#list-price).
+- __Apply discount to submitted price:__ Google Shopping will display the VTEX store's products with the associated discount and payment method.
+
+<div class = "alert alert-warning">
+  The <b>Apply discount to submitted price</b> setting is only available for VTEX stores in Brazil.
+</div>
+
+![envio-de-precos-google-en](//images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/419f9830910ef18e14deec1eef56f5aa/envio-de-precos-google-en.png)  
+
+## What needs to be done?
+
+As of December 14, 2023, the update will be available to all [VTEX accounts acting as sellers](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller).
+Accounts not using the Google Shopping integration but wanting to activate the __Submit base price (for discount prices)__ and __Apply discount to submitted price__ settings should follow [this article track](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4z) to start using the new settings. Accounts that are integrated with Google Shopping and have the __Consider discount for boleto payment in the submitted price__ setting active will automatically have the __Apply discount to submitted price__ option active after the update, as shown in the image below:
+
+![fluxo-update-news-google-en](//images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/8feca453a73f6c2a09f311f9b482d8da/fluxo-update-news-google-en.png)
+
+Check out the documentation and learn how to [configure a discount linked to a payment method](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/3AqbcsWrge8zLt0BC5CtGd#desconto-vinculado-ao-metodo-de-pagamento) and [how to configure a discount in the connector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
+
diff --git a/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md b/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md
index c8fe439c0..ac953448e 100644
--- a/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md
+++ b/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md
@@ -16,7 +16,7 @@ announcementSynopsisEN: 'Introducing the Singleton: a Headless CMS content type
 ---
 
 The Singleton is a new type of content type that allows merchants to create and manage a single page of a content type in the Headless CMS. Unlike other content types, the Singleton cannot be duplicated, ensuring that only one page exists and the content is consistent across the store's pages.
-![singleton-en](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
+![singleton-en](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 The Singleton content type is only available for stores using the <a href="https://help.vtex.com/en/tutorial/managing-pages-beta--3DO6rBhZ1p3zndnFu5BgRt">VTEX Headless CMS</a> (Currently in Beta phase).
diff --git a/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md b/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md
new file mode 100644
index 000000000..2802d51b5
--- /dev/null
+++ b/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md
@@ -0,0 +1,35 @@
+---
+title: 'Headless CMS: Deeper insights into page publication status'
+id: 9G9ILO21L5sGtEVIHFhLr
+status: PUBLISHED
+createdAt: 2023-10-18T12:31:52.699Z
+updatedAt: 2023-10-18T20:56:21.584Z
+publishedAt: 2023-10-18T20:56:21.584Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-deeper-insights-into-page-publication-status
+locale: en
+legacySlug: headless-cms-deeper-insights-into-page-publication-status
+announcementImageID: ''
+announcementSynopsisEN: 'Publishing status on Headless CMS Pages will be discontinued in favor of Build Status for detailed deployment tracking.'
+---
+
+Starting November 1st, 2023, the **Publishing** status on Pages in the Headless CMS will be discontinued. Instead, you can track the deployment status of pages through the **Build Status** tool, as [previously announced](https://help.vtex.com/en/announcements/headless-cms-stay-informed-on-your-publication-progress--3ajb4FgE6nmqjblpSEg3SP). This tool offers a more detailed view of the deployment process of your pages.
+
+When a new page is created, it is initially set to **Draft**, indicating that the page has not yet been deployed. Once the page is successfully deployed, its status is updated to **Published**, meaning that the build process is ready to commence. Upon completion of the build, the page becomes accessible to end users.
+
+![Build Status - EN](//images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/81374cc9a9e94e04975cca5946de4ece/publishing-status-en.gif)
+
+## What has changed?
+
+The **Publishing** status was previously used to describe the deployment process of a CMS page to FastStore. However, it did not provide further details on the process.
+
+Now, by integrating the Build Status tool with other systems like [Releases](https://help.vtex.com/en/tutorial/planner-releases-page-beta--2p7IiVD6K8i1iRiwHph5sw), WebOps, and [FastStore](https://www.faststore.dev/), the Headless CMS provides more comprehensive insights into the status of these systems.
+
+## Why are we making this change?
+The introduction of the Build Status tool aims to improve clarity and transparency in the deployment workflow.
+
+## What needs to be done?
+This feature will be implemented into the Headless CMS by November 1st, 2023, and no action is required on your side.
+
diff --git a/docs/announcements/en/headless-cms-events-available-in-audit.md b/docs/announcements/en/headless-cms-events-available-in-audit.md
new file mode 100644
index 000000000..25a98f823
--- /dev/null
+++ b/docs/announcements/en/headless-cms-events-available-in-audit.md
@@ -0,0 +1,47 @@
+---
+title: 'Headless CMS events available in Audit'
+id: 2WQz4dwteRahTD71hIHNNc
+status: PUBLISHED
+createdAt: 2023-12-08T14:36:53.841Z
+updatedAt: 2023-12-08T14:57:21.295Z
+publishedAt: 2023-12-08T14:57:21.295Z
+contentType: updates
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: headless-cms-events-available-in-audit
+locale: en
+legacySlug: headless-cms-events-available-in-audit
+announcementImageID: ''
+announcementSynopsisEN: 'We added Headless CMS events to Audit logs.'
+---
+
+[Audit](https://help.vtex.com/en/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA), a VTEX Admin module that records events in your store for future auditing, now processes [Headless CMS](https://help.vtex.com/en/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt) events. Headless CMS is the VTEX solution that allows managing web content with the autonomy to create, edit, and publish content via the VTEX Admin.
+
+## What has changed?
+
+We added the Headless CMS events listed below to the Audit logs:
+
+| Action | Event description | Event details |
+|---|---|---|
+| TRY_PUBLISHING | Attempt to publish a page. | Event ID. |
+| TRY_PUBLISH_IN_RELEASE | Attempt to publish a release. | Event ID. |
+| TRY_UNPUBLISHING | Attempt to unpublish a page. | Event ID. |
+| RESTORE_CONTENT | Content restore. | Event ID. |
+| TRY_UPDATING_DRAFT | Attempt to update a draft. | Event ID. |
+| TRY_UNPUBLISHING_AND_OVERWRITING | Attempt to unpublish and overwrite a page. | Event ID. |
+| done.invoke.deleteContent | Delete content. | Event ID. |
+| done.invoke.deleteContentVariant | Delete content version. | Event ID. |
+
+In the **Action** column, all Headless CMS events also display the following information:
+
+* **CONTENT_ID:** unique identifier of the content.
+* **VARIANT_ID:** unique identifier of the content version.
+* **WORKSPACE**: workspace where the action occurred.
+
+<div class="alert alert-info">
+  <p>Check the complete <a href="https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">list of events available in Audit</a>.</p>
+</div>
+
+## What needs to be done?
+No action is required. The change in Audit is already active for all accounts, recording the [list of events](#what-has-changed) mentioned above.
+
diff --git a/docs/announcements/en/headless-cms-new-authorization-requirement.md b/docs/announcements/en/headless-cms-new-authorization-requirement.md
new file mode 100644
index 000000000..7fd871bd9
--- /dev/null
+++ b/docs/announcements/en/headless-cms-new-authorization-requirement.md
@@ -0,0 +1,57 @@
+---
+title: 'Headless CMS: new authorization requirement '
+id: 7G056zzZmGFBztkRqhpUgj
+status: PUBLISHED
+createdAt: 2024-02-02T12:34:37.766Z
+updatedAt: 2024-02-02T14:14:58.237Z
+publishedAt: 2024-02-02T14:14:58.237Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-new-authorization-requirement
+locale: en
+legacySlug: headless-cms-new-authorization-requirement
+announcementImageID: ''
+announcementSynopsisEN: 'Users now require CMS GraphQL API resource for content management. Update user roles accordingly.'
+---
+
+As of February 15, all [users](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) and [application keys](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) that need access to Headless CMS will be required to have the `See CMS menu on the top-bar` and `Settings` License Manager [resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) added to their [user roles](https://help.vtex.com/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). For content management in the Headless CMS, they must also have the `CMS GraphQL API` [resource](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3). This requirement applies to Headless CMS API and VTEX Admin.
+
+## What has changed?
+Previously, users and application keys could manage store content on Headless CMS
+ without having a specific License Manager resource associated with their role.
+
+Now, any request via Headless CMS API or VTEX Admin will authenticate the user and verify if they have the required resources associated with their role.  
+The `See CMS menu on the top-bar` and `Settings` resources grant access to Headless CMS. For content management, users also need to have the `CMS GraphQL API` resource. Without this resource, users are restricted from content management within the Headless CMS.
+
+## Why did we make this change?
+This change aims to enhance security and simplify user access to the Headless CMS. This means users have a more controlled and secure environment when managing store content. 
+
+## What needs to be done?
+Ensure that Headless CMS users are associated with the `CMS GraphQL API`, `See CMS menu on the top-bar` and `Settings` resources within their user roles by either [creating a new role](#creating-a-new-role) or [editing an existing one](#editing-a-role).
+
+<div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 35px">
+  <p>To manage users and their roles, you need the <code>Save access profile</code> resource from the <b>License Manager</b> product associated with your user role. For example, the <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> is a predefined role that has the <code>Save access profile</code> resource associated with it.</p>
+
+</div>
+
+### Creating a new role
+
+If you have not created a specific role for Headless CMS users yet or wish to create one, refer to the [Creating a role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) guide. Ensure that you associate the role with the `CMS GraphQL API`, `See CMS menu on the top-bar` and `Settings` resources in the **Products and Resources** section.
+
+### Editing a role
+
+If you need to edit an existing role for Headless CMS users, follow these instructions:
+
+1. Access the VTEX Admin.
+2. Click on your profile avatar on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings > User roles**.
+3. Click on the **Role name** that the Headless CMS users have assigned to them.
+
+<div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; margin-bottom: 10px; padding: 15px">
+  <p>Given the option to create custom roles, they may differ based on the store's configuration, and each store can define its specific role for Headless CMS users.</p>
+</div>
+
+4. On the **Edit Role** page, navigate to the **Products and Resources** section.
+5. Locate the **CMS** product and click on it.
+6. Select the `CMS GraphQL API`, `See CMS menu on the top-bar` and `Settings` resources.
+7. Click `Save`.
diff --git a/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md b/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md
new file mode 100644
index 000000000..2ccb7de54
--- /dev/null
+++ b/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md
@@ -0,0 +1,40 @@
+---
+title: 'Headless CMS: Simplify content creation and management with Projects'
+id: 6pl14hf2E6sNgR9ykCJkj8
+status: PUBLISHED
+createdAt: 2023-11-01T16:39:47.055Z
+updatedAt: 2023-11-16T14:17:47.228Z
+publishedAt: 2023-11-16T14:17:47.228Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-simplify-content-creation-and-management-with-projects
+locale: en
+legacySlug: headless-cms-simplify-content-creation-and-management-with-projects
+announcementImageID: ''
+announcementSynopsisEN: 'Headless CMS - Centralize and customize your projects in one place.'
+---
+
+**Projects** is the new feature in the Headless CMS that streamlines the management of multiple digital experiences, such as mobile apps, websites, and email marketing, from one control panel. 
+
+![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c7ccee21dc6cae85a41886c49d9a3d8f/projects-two-en.png)
+
+With Projects, you can customize each project's settings, content, and branding to specific audiences or purposes.
+
+## What has changed
+Before, to handle different projects with distinct target audiences or solutions, you had to access the VTEX Admin, go to **Apps** > **Extensions Hub** > **App Management**, and then search for the **CMS (alpha)** app. Within the **CMS (alpha)** app, each project required individual creation and settings.
+
+Now, the **Projects** interface allows you to manage all your projects from a single dashboard, providing a centralized control panel where you can manage all projects. You can now easily switch between projects, adjusting settings, content, and identity in one place. This improvement makes you more adaptable, catering to different audiences and objectives.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
+
+## Why are we making this change?
+The **Projects** interface brings the following improvements:
+
+- To simplify the process of managing content across multiple projects.
+- To centralize projects in one place.
+- To effectively cater to specific audiences or objectives by having separate projects.
+
+## What needs to be done?
+The feature is already available for all accounts with Headless CMS installed. Refer to the [Managing Projects](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) guide for more information on using the feature.
+
diff --git a/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md b/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md
new file mode 100644
index 000000000..81890d313
--- /dev/null
+++ b/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md
@@ -0,0 +1,45 @@
+---
+title: 'Headless CMS: Stay informed on your publication progress'
+id: 3ajb4FgE6nmqjblpSEg3SP
+status: CHANGED
+createdAt: 2023-08-21T12:33:36.149Z
+updatedAt: 2023-10-04T13:35:38.902Z
+publishedAt: 2023-08-21T15:36:01.683Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-stay-informed-on-your-publication-progress
+locale: en
+legacySlug: headless-cms-stay-informed-on-your-publication-progress
+announcementImageID: ''
+announcementSynopsisEN: 'Stay informed about Headless CMS publication stages and quickly identify publication errors.'
+---
+
+The Headless CMS now offers a notification feature that keeps you informed throughout each stage of the publication process. The new notification cards provide updates on each stage of a publication in the VTEX Headless CMS, keeping users informed about the publication on Releases, VTEX Headless CMS, and FastStore build stages. 
+
+![Headless CMS - Notification](//images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/7ab62cbd7fbb27b46894c0f366e7d25c/headless-cms-publish-en.gif)
+
+This feature also helps you identify and report errors during deployment by indicating the exact error stage. It also provides the option to retry deployments if needed.
+
+## What has changed?
+Previously, when a publication did not occur, it was difficult to determine the source of the problem, leading to challenges in debugging and reporting the issue, and delays in launching campaigns.
+
+With the notification feature, you can now stay informed about the status of each deployment stage:
+
+| Status                 | Description                                      |
+| ---------------------- | ------------------------------------------------ |
+| **Publishing started** | Starts the publishing of release by Headless CMS. |
+| **Build**              | Takes release changes to production.             |
+| **Update document status**       | Updates all pages, including the new changes.       |
+| **Close release**      | Updates the release status.       |
+
+If an error occurs during deployment, the notification card will indicate the stage at which the error occurred. You can click `Try again` to redeploy.
+
+![Headless CMS - Redeploy](//images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/2e950f93b204d1ce40d67b0f8516b327/headless-cms-redeploy-en.gif)
+
+## Why are we making this change?
+The notification feature gives you more autonomy to understand and address issues related to store publications. It enables you to precisely identify and report issues and retry the publication process.
+
+## What needs to be done?
+This feature is already implemented in the Headless CMS, and no action is required on your side.
+
diff --git a/docs/announcements/en/headless-cms-updated-user-permissions.md b/docs/announcements/en/headless-cms-updated-user-permissions.md
new file mode 100644
index 000000000..6e7d8cc9a
--- /dev/null
+++ b/docs/announcements/en/headless-cms-updated-user-permissions.md
@@ -0,0 +1,33 @@
+---
+title: 'Headless CMS: updated user permissions'
+id: 6EvqWHQ2akp2dpdjChGJcy
+status: DRAFT
+createdAt: 2024-01-11T18:15:47.624Z
+updatedAt: 2024-01-11T18:21:20.966Z
+publishedAt: 
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-updated-user-permissions
+locale: en
+legacySlug: headless-cms-updated-user-permissions
+announcementImageID: ''
+announcementSynopsisEN: ''
+---
+
+To effectively manage store content in the Headless CMS, users must now have the `CMS GraphQL API` resource associated with their [user roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+## What has changed
+Previously, users with Headless CMS access could manage store content without specific resource associations.
+
+Now, any request sent to the Headless CMS API will authenticate the user and verify their permissions via the associated `CMS GraphQL API` resource. Without this resource, users won’t be able to manage content within the Headless CMS.
+## Why did we make this change
+
+## What needs to be done
+Ensure Headless CMS users have the `CMS GraphQL API` resource connected to their user roles. If not, take the following steps:
+
+Associating `CMS GraphQL API` resource to a role:
+
+Creating a new role
+{Link to the official doc}
+
diff --git a/docs/announcements/en/improved-security-for-the-customers-first-purchase.md b/docs/announcements/en/improved-security-for-the-customers-first-purchase.md
index 2fde029cf..c8913477f 100644
--- a/docs/announcements/en/improved-security-for-the-customers-first-purchase.md
+++ b/docs/announcements/en/improved-security-for-the-customers-first-purchase.md
@@ -1,9 +1,9 @@
 ---
 title: "Improved security for the customer's first purchase"
-id: DKlfRaMNHxgQhUT5VqRrK
+id: 3RBko0KXi8eOm4nKARgReD
 status: DRAFT
-createdAt: 2023-04-28T12:35:44.503Z
-updatedAt: 2023-06-09T15:37:43.651Z
+createdAt: 2023-07-03T11:34:49.078Z
+updatedAt: 2023-10-09T14:12:03.607Z
 publishedAt: 
 contentType: updates
 productTeam: Shopping
@@ -21,7 +21,7 @@ In order to improve the security of your store information, VTEX has made improv
 
 During a customer's first purchase, their personal information is displayed unmasked next to the cart since they do not have a profile in the store yet.
 
-Now, when a new cart is created, a new cookie called `CheckoutOrderFormOwnership` is forwarded along with the existing `checkout.vtex.com` cookie that contains the orderFormId. This will ensure that only the customer who created the cart has unrestricted access to their personal information.
+Now, when a new cart is created, a new cookie called `CheckoutOrderFormOwnership` is forwarded along with the existing `checkout.vtex.com` cookie that contains the `orderFormId`. This will ensure that only the customer who created the cart has unrestricted access to their personal information.
 
 In case there is an external attempt to access the cart data, the customer's personal information cannot be viewed, as the data will appear masked.
 
diff --git a/docs/announcements/en/improvement-of-discount-price-viewing-experience.md b/docs/announcements/en/improvement-of-discount-price-viewing-experience.md
index 1fc9a744f..6518bee28 100644
--- a/docs/announcements/en/improvement-of-discount-price-viewing-experience.md
+++ b/docs/announcements/en/improvement-of-discount-price-viewing-experience.md
@@ -24,16 +24,16 @@ Before this change, customers could experience issues in the order summary if th
 Consider, for instance, a customer that wants to buy a product that costs US$ 600 and is eligible for a 10% discount for prepayment in full. The customer proceeds to checkout and lands on the order summary page, where they must select a payment option. Here are the three main error scenarios that could occur:
 
 - The customer has not selected a payment option yet, and the price is displayed without the discount in all options, even the one that is eligible for it.
-![O usuário ainda não selecionou um número de parcelas](https://images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
+![O usuário ainda não selecionou um número de parcelas](//images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
 
 - The customer has selected a payment option that is not eligible for the discount, and the price is displayed without the discount in all options, even the one that is eligible for it (prepayment in full).
-![O usuário selecionou um número de parcelas não elegível para desconto](https://images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
+![O usuário selecionou um número de parcelas não elegível para desconto](//images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
 
 - The customer has selected a payment option that is eligible for the discount (prepayment in full), and the discount is applied to all options, even the ones that are not eligible for it.
-![O usuário selecionou um número de parcelas elegível para desconto (à vista)](https://images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
+![O usuário selecionou um número de parcelas elegível para desconto (à vista)](//images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
 
 With this change, discounts will be displayed correctly in the payment options that are eligible for them.
-![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](https://images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
+![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](//images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md b/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md
index 520a2b9d4..b633d2745 100644
--- a/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md
+++ b/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md
@@ -25,7 +25,7 @@ On VTEX, you can change the price many times a day according to your store's str
 
 You can add prices via spreadsheet in two steps, exporting and importing. The price export had its experience improved with new features to give the user more visibility about the status of each price export spreadsheet.
 
-![exportacao en](https://images.ctfassets.net/alneenqid6w5/5mPN6MnLBwQOvlRAccbT58/c5c7b58769f5355ac63eb89c96200b6a/exportacao_en.gif)
+![exportacao en](//images.ctfassets.net/alneenqid6w5/5mPN6MnLBwQOvlRAccbT58/c5c7b58769f5355ac63eb89c96200b6a/exportacao_en.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md b/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md
new file mode 100644
index 000000000..ee8c5db7e
--- /dev/null
+++ b/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md
@@ -0,0 +1,43 @@
+---
+title: 'Improvements to unified search in VTEX Sales App'
+id: 4ZfzuvJjgtfjNR3UXrggYN
+status: PUBLISHED
+createdAt: 2024-05-03T12:45:14.073Z
+updatedAt: 2024-05-06T13:37:06.301Z
+publishedAt: 2024-05-06T13:37:06.301Z
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: improvements-to-unified-search-in-vtex-sales-app
+locale: en
+legacySlug: improvements-to-unified-search-in-vtex-sales-app
+announcementImageID: ''
+announcementSynopsisEN: "We've improved the VTEX Sales App's unified search to enhance user experience when browsing and searching for products."
+---
+
+We have enhanced the unified search in VTEX Sales App to improve user experience when browsing and searching for products.
+
+This improvement allows sales associates to find products beyond the store's inventory and add them to the cart. Click the magnifying glass icon <i class="fas fa-search"></i>  and enter the product name, reference code, SKU ID, or EAN in the search bar on the store's homepage.
+
+## What has changed?
+
+- **Intuitive search list:** You'll have access to an intuitive and informative search list, which offers a simplified view of your previous searches.
+
+- **Detailed view of products:** Spaces have been optimized, allowing you to see more items with larger, higher-quality images. Adding products to the cart, especially those with a single SKU, is now more straightforward and simplified.
+
+- **Search refinement with filters:** You can apply filters by clicking the predefined filters, without having to submit the form with the `Apply Filters` button. In addition, applied filters will be displayed at the top of the page, making it easier to know which filters are in use and easily remove any of them.
+
+- **Quick view of unavailable products:** Before, the system displayed all products as unavailable and, after some time, loaded their availability correctly. Now, product availability is immediately displayed when the product loads.
+
+- **Optimization for slow connections:** By leveraging browser caching, the search will return new information only when necessary, guaranteeing a fast response even in scenarios with slow internet connections.
+
+![Mobile - EN](//images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/13a9e307f44564906b210cc72a38c436/mobile__1_.gif)
+
+## Why did we make this change?
+
+This change is meant to improve the browsing and product search experience of sales associates. This will make their search journey more intuitive and informative.
+
+## What needs to be done?
+
+No action is required. The feature will be automatically applied to all VTEX stores using VTEX Sales App. For more information, see the article [Unified search in VTEX Sales App](https://help.vtex.com/en/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/9sXeVwoD60qYYgRJ11r5F). 
+
diff --git a/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md b/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md
index 02e102fbb..ef7292a36 100644
--- a/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md
+++ b/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md
@@ -22,7 +22,7 @@ This tool allows to control order approvals with changes in their values. The ch
 ## What changes? 
 Now, instead of opening a ticket directly with the support, you can manage the authorization rules by admin. To do this, go to the path: Menu - Order Management - Order Authorization.
 
-![ENAutorizacaoPedidos.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/5DZywamKgUPvEGpYkTfZZ5/02ce2c609e45a7eccfacf103b5351f29/ENAutorizacaoPedidos.PNG_h_250)
+![ENAutorizacaoPedidos.PNG?h=250](//images.ctfassets.net/alneenqid6w5/5DZywamKgUPvEGpYkTfZZ5/02ce2c609e45a7eccfacf103b5351f29/ENAutorizacaoPedidos.PNG_h_250)
 
 ## What you need to do
 It is important to mention that the store will not lose the previous rules, which were done by opening a ticket to the support team. They will automatically update on the new screen.
diff --git a/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
index 3f9e39a9b..e3b3a2e86 100644
--- a/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
@@ -19,7 +19,7 @@ Starting from May 31st, we are launching for all VTEX stores the beta version of
 
 The **Shipping Strategy** pages have been updated according to the new VTEX design system, as shown below:
 
-![nova_estrategia_envio_announcement_boards_EN](https://images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/9a19eb3111c11ccc7b8f085255449b1e/nova_estrategia_envio_announcement_boards_EN.png)
+![nova_estrategia_envio_announcement_boards_EN](//images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/9a19eb3111c11ccc7b8f085255449b1e/nova_estrategia_envio_announcement_boards_EN.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/introducing-vtex-ad-network-beta.md b/docs/announcements/en/introducing-vtex-ad-network-beta.md
new file mode 100644
index 000000000..dfb9dc3df
--- /dev/null
+++ b/docs/announcements/en/introducing-vtex-ad-network-beta.md
@@ -0,0 +1,48 @@
+---
+title: 'Introducing VTEX Ad Network (Beta)'
+id: 5Xk8ekbP2Vb5QoI8GXRsQ6
+status: DRAFT
+createdAt: 2024-04-30T16:15:57.595Z
+updatedAt: 2024-04-30T17:41:55.796Z
+publishedAt: 
+contentType: updates
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: introducing-vtex-ad-network-beta
+locale: en
+legacySlug: introducing-vtex-ad-network-beta
+announcementImageID: ''
+announcementSynopsisEN: ' VTEX is launching an ad platform, designed to connect advertisers with merchants to promote products.'
+---
+
+VTEX is launching [VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur). This product aims to connect advertisers with merchants interested in promoting their products, allowing both to boost their business.
+
+## Advertisers
+
+Advertisers can [create ad campaigns](https://help.vtex.com/en/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse) to promote products in stores selling those products. This allows them to boost sales and view data to improve decision-making.
+
+When you create campaigns for your product, your ad can be highlighted in multiple VTEX stores with that product in their catalog.
+
+## Merchants
+
+Merchants can offer ad space in their stores for advertisers to promote products. In return, these merchants will receive a fee for each click on an ad in their stores.
+
+VTEX will select ads for your store, featuring products already in your catalog to ensure a smooth and seamless buying journey. This selection is based on your customer behavior.
+
+IMAGE
+
+## What needs to be done?
+
+See below how you can join **VTEX Ad Network** as a merchant or an advertiser.
+
+### Merchants
+
+To make ad space available in your store, install the [VTEX Ad Network for stores]() app in your VTEX account. Learn more in the [Displaying VTEX Ad Network ads in your store (Beta)](https://help.vtex.com/en/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA) article.
+
+<div class="alert alert-danger">
+Currently, only stores developed with <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> can offer ad space.
+</div>
+
+### Advertisers
+
+Any brand interested in promoting products already sold in VTEX stores can advertise using **VTEX Ad Network**. Learn more in [VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) and [Advertising with VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse).
diff --git a/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md b/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
index adf426f16..82828a2ec 100644
--- a/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
+++ b/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
@@ -28,4 +28,4 @@ When trying to access a store's Admin using an email address, you have the optio
 
 Security is a major focus here at VTEX, which takes center stage even more as major events like Black Friday comes into play. This new feature can help identify the source of an unauthorized access attempt.
 
-![IP Geolocation email - EN](https://images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/97307ceb15b0b247e4ae14c3f29bd607/IP_Geolocation_email_-_EN.png)
+![IP Geolocation email - EN](//images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/97307ceb15b0b247e4ae14c3f29bd607/IP_Geolocation_email_-_EN.png)
diff --git a/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
new file mode 100644
index 000000000..700415bce
--- /dev/null
+++ b/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
@@ -0,0 +1,50 @@
+---
+title: 'Lead time: Configuring shipping time at SKU level'
+id: 39Q8TeXaDCbmTXFtwpNXlf
+status: PUBLISHED
+createdAt: 2023-09-22T14:07:20.464Z
+updatedAt: 2023-09-28T17:47:25.398Z
+publishedAt: 2023-09-28T17:47:25.398Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: lead-time-configuring-shipping-time-at-sku-level
+locale: en
+legacySlug: lead-time-configuring-shipping-time-at-sku-level
+announcementImageID: ''
+announcementSynopsisEN: 'Global launch of lead time, an optional SKU-level shipping time setting.'
+---
+
+VTEX has made [lead time](https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B), a shipping time setting for inventory SKUs, available to all stores. In other words, you can set an additional shipping time at SKU level when calculating the shipping promises displayed to customers at checkout.
+
+![lead_time_image_total_time_EN](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
+
+The store's shipping will remain unchanged when not configured, as lead time is optional. Note that the checkout consolidation rules are maintained, calculating the total shipping time of the order based on the longest shipping time among the items.
+
+## What has changed?
+
+Previously, the order [shipping calculation](https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) considered the periods configured in your shipping strategy at different levels:
+
+- [Inventory](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+- [Loading dock](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+- [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+
+Now, you can also configure the shipping time at SKU level with the new lead time column on the [Inventory Management](https://help.vtex.com/en/tutorial/gerenciar-inventario--tutorials_139) page, which can be found in your VTEX Admin under **Catalog > Inventory > Inventory Management**, as shown in the image below:
+
+![lead_time_inventory_management_EN](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png) 
+
+<div class="alert alert-warning">
+In the VTEX Admin, the lead time is configured in days, with a 365-day limit. By default, the days are calculated in business days, but you can configure your shipping policy to <a href="https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configuring-lead-time-calculation-in-calendar-days-optional">calculate them in calendar days</a>. You need to use the <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a> endpoint to configure periods in hours, minutes, and seconds.
+</div>
+
+## Why did we make this change?
+
+These are the main advantages:
+
+- **More flexibility in inventory management**; especially useful for businesses with on-demand products and _dropshipping_ scenarios, in which the provider sends the product directly to the customer.
+- **More accurate shipping time configuration**, making it easier for you to manage your inventory.
+- **More accurate shipping promise calculations** for customers, leading to better shopping experiences.
+
+## What needs to be done?
+
+The [Inventory Management](https://help.vtex.com/en/tutorial/gerenciar-inventario--tutorials_139) page of the VTEX Admin was updated with the lead time column in all stores, and no action is required from you. Using the new field is optional, so if you don't configure it, the shipping time for your orders will remain unchanged.
diff --git a/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md b/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md
new file mode 100644
index 000000000..df291872b
--- /dev/null
+++ b/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md
@@ -0,0 +1,123 @@
+---
+title: 'Legacy payment connectors will be discontinued in 2024'
+id: 4R5YIjUu1IWkiOHzXtQU14
+status: PUBLISHED
+createdAt: 2023-10-13T12:52:48.753Z
+updatedAt: 2023-10-17T20:57:39.669Z
+publishedAt: 2023-10-17T20:57:39.669Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: legacy-payment-connectors-will-be-discontinued-in-2024
+locale: en
+legacySlug: legacy-payment-connectors-will-be-discontinued-in-2024
+announcementImageID: ''
+announcementSynopsisEN: 'In 2024, VTEX will discontinue legacy payment connectors, that do not use the Payment Provider Protocol.'
+---
+
+To integrate payment methods to the VTEX platform, payment providers can create payment connectors using the [Payment Provider Protocol](https://help.vtex.com/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) (PPP). However, several legacy connectors are using older versions of our payment integration architecture, which are less stable and less performant.
+
+## What has changed?
+
+<div class="alert alert-danger">
+These changes will not affect Black Friday 2023. They will only be implemented in the first quarter of 2024.
+</div>
+
+VTEX is initiating the discontinuation of these legacy connectors, which will happen gradually:
+
+- **January 31, 2024** - Blocking the creation of new gateway affiliations using legacy payment connectors. As of this date, VTEX stores will no longer be able to set up connections using the connectors that will be discontinued. All payment rules already configured will continue to operate as usual without affecting transactions.
+- **February 10, 2024** - Suggested deadline for submitting new connectors for approval. If partner companies want to develop new connectors using the [PPP](https://help.vtex.com/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) to replace legacy connectors, we suggest submitting them for approval by this date. By doing so, VTEX stores will have a few weeks to reconfigure their payment connections before discontinuation. This date is also intended to guarantee the SLA of the [payment connector approval process on the VTEX platform](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+- **March 31, 2024** - Permanent discontinuation of connectors that do not use the [PPP](https://help.vtex.com/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). From this date, VTEX will block all transactions from legacy payment connectors.
+
+### List of legacy payment connectors
+
+See the list of all the connectors that will be discontinued:
+
+- Adyen
+- Alignet
+- Amex
+- AuthorizeNet/AuthorizeDotNet
+- BanamexInvoice
+- BankInvoiceItau/BankIssuedInvoiceItau
+- BankInvoiceSantander/BankIssuedInvoiceSantander
+- Bcash
+- BoldCron
+- Bradesco/RegisteredBankInvoiceBradesco
+- BrasPag/Braspag
+- Cielo/CieloV3
+- Conductor
+- Credomatic
+- CyberSource
+- Decidir/DecidirV1
+- ERede/E-Rede V2/ERedeRest
+- Evolucard
+- Firstdata
+- IPay88
+- ItauShopline
+- Koin
+- MaxiPago
+- MeoWallet
+- MercadoPagoV1
+- MobilPay
+- Moip
+- MOLPay
+- Mundipagg/MundipaggFraudPrevention
+- Nexxpago
+- NPS
+- PagamentoDigital
+- PagBrasil
+- PagHiper
+- PagoEfectivo
+- PagosNet
+- PagosWeb
+- PagSeguro/PagSeguroDirect
+- PayClub
+- Payme
+- Paymentez
+- PaymentHub
+- PaymentsOS
+- PayPal/PayPalPlus
+- PayU/PayUGlobal
+- Payzen
+- Place2Pay/PlaceToPay
+- Rede Pay/RedePay
+- Redecard
+- Redsys/RedsysV2
+- SafetyPay
+- SalesMachine
+- Scopus
+- Sitef/SitefDirectSale/SitefPreauth
+- Stelo
+- TNSPay
+- TodoPago
+- WebPay/WebPay2P
+- WorldPay
+
+## Why we are making this change?
+
+Connectors using the [PPP](https://help.vtex.com/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) have higher authorization rates than legacy connectors. Therefore, migrating to new connectors tends to boost VTEX stores' sales.
+
+Furthermore, many legacy connectors are outdated in terms of technology. Migrating to connectors using the [PPP](https://help.vtex.com/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) ensures that VTEX stores will be using more modern and stable technologies offered by VTEX.
+
+## What needs to be done?
+
+The actions required from this change depend on your context in the VTEX ecosystem. See below to find out the option that best applies to your business.
+
+### Legacy payment connector providers
+
+If you are a payment provider managing one or more [connectors being discontinued](#list-of-legacy-payment-connectors), you must develop a new connector using the [Payment Provider Protocol](https://help.vtex.com/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Otherwise, you will not be able to process transactions as of the discontinuation date mentioned above.
+
+In this case, we recommend that you submit your new connector for approval by February 10, 2024, so that stores have time to reconfigure their payment connections before discontinuation. Learn more about the [approval process for new payment connectors](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+
+<div class="alert alert-danger">
+VTEX cannot guarantee that your new payment connector will be available to VTEX merchants before the official discontinuation if you submit it for approval after this date.
+</div>
+
+If you have any questions about this process or would like to align joint communication with merchants, please contact your VTEX Partner Manager.
+
+### Stores using legacy payment connectors
+
+If your store uses one of the [connectors that will be discontinued](#list-of-legacy-payment-connectors), you must configure it with the new connector corresponding to that payment provider before March 31, 2024. Otherwise, you will not be able to complete purchases in your store using the payment method in question.
+
+Throughout the discontinuation and migration process, you can contact your payment providers to monitor the progress and get more information on the development of the new connectors.
+
diff --git a/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md b/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md
index b7f5be78c..50fd7a3d6 100644
--- a/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md
+++ b/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md
@@ -42,7 +42,7 @@ Behind the scenes on the Admin, it allows you to:
 - Set a list of forbidden words that will be blocked in the realtime chat;
 - Propose polls and quizzes to your users.
 
-![live-shopping-event-details-en](https://images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/e1929b824a37a1e0c1b21a0e3bf38ab8/image4.png)
+![live-shopping-event-details-en](//images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/e1929b824a37a1e0c1b21a0e3bf38ab8/image4.png)
 
 ## What are the advantages?
 
diff --git a/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
new file mode 100644
index 000000000..252f4f518
--- /dev/null
+++ b/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -0,0 +1,40 @@
+---
+title: 'Luhn algorithm for credit and debit cards at checkout'
+id: 22hAb6KVWUitIG9OzFzgi2
+status: PUBLISHED
+createdAt: 2023-09-19T15:43:01.350Z
+updatedAt: 2023-09-19T16:47:51.216Z
+publishedAt: 2023-09-19T16:47:51.216Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: luhn-algorithm-for-credit-and-debit-cards-at-checkout
+locale: en
+legacySlug: luhn-algorithm-for-credit-and-debit-cards-at-checkout
+announcementImageID: ''
+announcementSynopsisEN: 'Reduce the percentage of declined transactions due to invalid card number'
+---
+
+VTEX now allows validating credit and debit card numbers with the Luhn algorithm at checkout.
+
+## What has changed?
+
+Previously, when a customer entered the card number at checkout, it was not possible to identify whether it was a valid card. When there were typing errors, the transaction was created but then canceled during authorization.
+
+Now, the Luhn algorithm will ensure that only a valid card number can be used for payment, which will reduce the percentage of declined transactions due to invalid card numbers.
+
+If a customer enters an incorrect number, an error message is displayed at checkout. In such cases, the customer must check and correct the number to complete the purchase.
+
+![algoritmo_luhn_en](//images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/ccd302d3086caaeca01c5725bdbd8b2d/algoritmo_luhn_en.PNG)
+
+## Why did we make this change?
+
+Having a payment transaction declined due to an invalid card number could lead customers to give up on buying again, as they would have to enter the card number again. So, this improvement in the shopping experience aims to increase your store conversion rate.
+
+## What needs to be done?
+
+No action is required. The Luhn algorithm is already active in all VTEX stores.
+
+<div class="alert alert-warning">
+The Luhn algorithm does not prevent fraud through card testing attacks. Its purpose is to detect typing errors in card numbers.
+</div>
diff --git a/docs/announcements/en/marketplace-improvements-on-received-skus.md b/docs/announcements/en/marketplace-improvements-on-received-skus.md
index b1705fdd1..7531f8981 100644
--- a/docs/announcements/en/marketplace-improvements-on-received-skus.md
+++ b/docs/announcements/en/marketplace-improvements-on-received-skus.md
@@ -29,7 +29,7 @@ No configuration is needed to activate this functionality - it will be installed
 
 It is worth noting that this action can be undone. It is possible to approve a blocked SKU through REST API if the marketplace wishes to receive it again as a suggestion from the seller. To learn more about SKU approval, access our API documentation on the Developer Portal.
 
-![EN SKUs Recebidos Announcement](https://images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/fab32d8d2bbf1b59bace4e2fb0d85ac5/EN_SKUs_Recebidos_Announcement.jpg)
+![EN SKUs Recebidos Announcement](//images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/fab32d8d2bbf1b59bace4e2fb0d85ac5/EN_SKUs_Recebidos_Announcement.jpg)
 
 ## Configuring automatic SKU approval
 
diff --git a/docs/announcements/en/marketplace-network-has-been-improved.md b/docs/announcements/en/marketplace-network-has-been-improved.md
index 8eeb19d1a..2de558b0c 100644
--- a/docs/announcements/en/marketplace-network-has-been-improved.md
+++ b/docs/announcements/en/marketplace-network-has-been-improved.md
@@ -19,7 +19,7 @@ A big challenge for marketplaces and sellers in our ecosystem is connecting with
 
 The Marketplace Network has been revamped to improve your experience. In addition, it is no longer necessary to download the app from our App Store, as the feature has been automatically added to all stores that act as sellers or marketplaces.
 
-![Marketplace network tour EN](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
+![Marketplace network tour EN](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
 
 ## What has changed?
 The Marketplace Network pages have undergone some changes:
diff --git a/docs/announcements/en/marketplace-new-offer-quality-filters.md b/docs/announcements/en/marketplace-new-offer-quality-filters.md
index 2a68d138a..92ae7077d 100644
--- a/docs/announcements/en/marketplace-new-offer-quality-filters.md
+++ b/docs/announcements/en/marketplace-new-offer-quality-filters.md
@@ -21,7 +21,7 @@ To give marketplaces more control over the approval criteria for an offer, we cr
 
 Thus, the SKUs that are sent to the marketplace meet the requirements relevant to catalog curation. 
 
- ![Offer Quality gif](https://images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/ecf196465a00c5b0e12eca29f1c9e3f4/Offer_Quality_01.gif)
+ ![Offer Quality gif](//images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/ecf196465a00c5b0e12eca29f1c9e3f4/Offer_Quality_01.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md b/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md
index e8e0b2049..d4959c722 100644
--- a/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md
+++ b/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md
@@ -24,7 +24,7 @@ Previously, to check a received SKU's information, you had to leave the main lis
 
 The sidebar contains the SKU's images, price, inventory levels, and product attributes such as a description, specifications, codes and IDs. It also includes the matching percentage that the SKU received from the [matcher](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) set up in your store. You can still access the SKU’s full details by clicking on the button *View details page*.
 
-![EN Sidebar received](https://images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/e77bda0e72c12f4190a3fe61249a7e65/EN_Sidebar_received.gif)
+![EN Sidebar received](//images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/e77bda0e72c12f4190a3fe61249a7e65/EN_Sidebar_received.gif)
 
 ## Why did we make this change?
 We developed the sidebar to provide more agility to your operation and facilitate the cataloging of received SKUs, by allowing you to:  
diff --git a/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md b/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md
index 955d45b25..1b7490875 100644
--- a/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md
+++ b/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'We have unified the Marketplace Network and the Integra
 
 To unify the opportunities to connect to VTEX and external marketplaces, we have merged the Integrations and Marketplace Network pages, now called __Marketplaces and Integrations__. The update will be available in all VTEX accounts as of May 03, 2023.  
 
-![Marketplaces and Integrations](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
+![Marketplaces and Integrations](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
 
 ## What has changed?  
 
diff --git a/docs/announcements/en/marketplaces-received-skus-beta.md b/docs/announcements/en/marketplaces-received-skus-beta.md
index 7fd269e02..17e2c1f5b 100644
--- a/docs/announcements/en/marketplaces-received-skus-beta.md
+++ b/docs/announcements/en/marketplaces-received-skus-beta.md
@@ -25,7 +25,7 @@ This open beta is the first in a series of product updates and improvements to c
 
 One of the first and principal improvements is the new way to select SKUs en masse — so you can approve or reject them in bulk. Aligned with our [Styleguide](https://styleguide.vtex.com/ "Styleguide"), the bulk selection will make your work faster and better.
 
-![received-skus-bulk](https://images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
+![received-skus-bulk](//images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
 
 
 
@@ -33,13 +33,13 @@ One of the first and principal improvements is the new way to select SKUs en mas
 One of the challenges in managing items from multiple sellers is prioritizing your never-ending items list. To help you with that we've built a brand new __ordering__ feature, where you can reorder all submissions according to price and – one of the main improvements – by inventory availability. See how many items are available at a glance, so you can approve the SKUs that will perform better.
 
 
-![received-skus-ordering](https://images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
+![received-skus-ordering](//images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
 
 
 This extends to the new __filtering__ tool. See and filter SKUs by category, brand, and seller in a simple and intuitive way.
 
 
-![received-skus-filtering](https://images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
+![received-skus-filtering](//images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
 
 
 
diff --git a/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md b/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md
new file mode 100644
index 000000000..b4e41e535
--- /dev/null
+++ b/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md
@@ -0,0 +1,53 @@
+---
+title: 'Master Data v1: Dynamic settings deprecation'
+id: 4a1FZX8wGeHLcOyMg0egg8
+status: PUBLISHED
+createdAt: 2024-04-17T12:34:11.024Z
+updatedAt: 2024-04-17T12:48:51.570Z
+publishedAt: 2024-04-17T12:48:51.570Z
+contentType: updates
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: master-data-v1-dynamic-settings-deprecation
+locale: en
+legacySlug: master-data-v1-dynamic-settings-deprecation
+announcementImageID: ''
+announcementSynopsisEN: 'The Calculated field and the "Change field value" trigger will be discontinued in Master Data v1.'
+---
+
+On June 17, 2024, we will disable the following settings in Master Data v1: **Calculated field** and **Change field value** trigger.
+
+These options allowed you to dynamically change document values in[ Master Data](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) by running code from a trigger or updating/creating a document.
+
+We recommend [creating an app to communicate with Master Data](https://developers.vtex.com/docs/guides/create-master-data-crud-app) to replace these settings if you need to update field values dynamically.
+
+## What has changed?
+
+Both dynamic settings will be disabled in Master Data v1.
+
+Note that **Calculated fields** and existing triggers using the **Change field value** function will stop working on the same date. See the [What needs to be done?](#what-needs-to-be-done) section for more information on how to adapt to these changes.
+
+### Calculated field
+
+The **Calculated field** was a setting within the [data entity](https://help.vtex.com/en/tutorial/data-entity--tutorials_1265) fields that allowed running C# code to recalculate the field's value whenever a new document was added or updated. 
+
+This field type and the calculated fields created will no longer be available from June 17, 2024, as illustrated below. 
+
+![image5](//images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/f0f168a3da476c6dfce2d74060569f98/image5.png)
+
+### Change field value
+
+When configuring triggers, the **Change field value** option allows you to add C# code to change the value of selected fields for each trigger execution.
+
+The **Change field value** option, illustrated below, will no longer be available when configuring trigger actions from June 17, 2024. Triggers previously created with this option will continue to work until that date.
+
+![image2](//images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/cb208350954b305141787aa0b4c65407/image2.png)
+
+## What needs to be done?
+
+If you need to update Master Data field values based on a trigger, we recommend contacting your development team and following the instructions below:
+
+- Develop an app on VTEX IO that communicates with Master Data, following the instructions in the developer's guide on [Creating a Master Data CRUD app](https://developers.vtex.com/docs/guides/create-master-data-crud-app).
+-	Configure a trigger that sends an HTTP request to the app, following the instructions in [How to create a trigger in Master Data v1](https://help.vtex.com/en/tutorial/creating-trigger-in-master-data--tutorials_1270#sending-an-http-request).
+
+If you use the **Calculated field** or a trigger with the **Change field value**, follow the steps above before June 17, 2024 to dynamically update the values even after these settings have been deprecated in Master Data v1.
diff --git a/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md b/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md
index faaa1b4e5..ed2e3e58f 100644
--- a/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md
+++ b/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md
@@ -19,7 +19,7 @@ Continuing with the improvements implemented for the [Mercado Libre certificatio
 
 On the new Mercado Libre **Promotions** page, you can manage a list of different promotional campaigns on the platform available for your store.
 
-![Promotions](https://images.ctfassets.net/alneenqid6w5/1uv8mQZR9ey8oQsnhDbvCo/eae937e7894481e7f1e555f5a9993c61/Promotions.gif)
+![Promotions](//images.ctfassets.net/alneenqid6w5/1uv8mQZR9ey8oQsnhDbvCo/eae937e7894481e7f1e555f5a9993c61/Promotions.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md b/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
index f5d448920..f4d53aa9c 100644
--- a/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
+++ b/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
@@ -19,14 +19,14 @@ From now on, your store can use a semicolon (`;`) to concatenate e-mail addresse
 
 This feature works for both the copy field (`Cc`) and the hidden copy field (`Bcc`), just as the comma already worked. The two concatenation options are now valid.
 
-![Message Center bug fix - EN](https://images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
+![Message Center bug fix - EN](//images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
 
 This simple change in the module responsible for sending transactional emails dramatically reduced the error rate on customer communications.
 
 The chart below shows the error rate of a store before we implemented the support for semicolon concatenation. More than 90% of e-mails failed every day.
 
-![Message Center bug fix 2](https://images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
+![Message Center bug fix 2](//images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
 
 After the improvement was implemented, the errors in sending transactional emails from the same store were completely eliminated, as this other chart shows:
 
-![Message Center bug fix 3](https://images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
+![Message Center bug fix 3](//images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
diff --git a/docs/announcements/en/multi-currency-gift-card.md b/docs/announcements/en/multi-currency-gift-card.md
new file mode 100644
index 000000000..3fca00f09
--- /dev/null
+++ b/docs/announcements/en/multi-currency-gift-card.md
@@ -0,0 +1,48 @@
+---
+title: 'Multi-currency gift card'
+id: 4FUXWCaQrFHcgjir698onc
+status: PUBLISHED
+createdAt: 2023-07-27T15:01:02.025Z
+updatedAt: 2023-07-27T16:13:02.651Z
+publishedAt: 2023-07-27T16:13:02.651Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: multi-currency-gift-card
+locale: en
+legacySlug: multi-currency-gift-card
+announcementImageID: ''
+announcementSynopsisEN: 'Configure your store gift cards in multiple currencies'
+---
+
+VTEX provides a new feature to configure gift cards based on your store local currencies.
+
+## What has changed?
+
+Previously, all gift cards were created without a specific currency associated with their value. When purchasing, the customer would add a gift card as one of the payment methods at Checkout. The amount would then be deducted based on the currency configured in the products in the cart.
+
+Now, the merchant can select the currency in which the gift card will be generated and make it available only for purchases made with that same type of currency.
+
+## Why did we make this change?
+
+In some regions, such as Europe and the United States, some stores sell products to more than one country and operate with price lists using multiple currencies. As there is no currency exchange operation when using a gift card, the discount could be higher or lower depending on the currency applied to the cart at checkout.
+
+## What needs to be done?
+
+Defining a specific currency for each gift card is optional. If you do not want to indicate in which currency it should be created, the behavior will remain the same as in a single-currency store, where discounts are applied without currency conversion.
+
+To create a gift card using a specific currency, follow the steps below:
+
+1. In the VTEX Admin, go to **Promotions > Gift Cards**, or type **Gift Cards** in the search bar at the top of the page.
+2. Click `New Gift Card` or `New Gift Card Batch` (to create a batch of gift cards).
+3. In the **Currency code** field, select the desired currency.
+4. Complete the other fields for creating the gift card.
+5. Click `Save`.
+
+![Multi-currency gift card](//images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/9c698709e61906ad413c76cfbbbb4c46/GiftCard_Multicurrency_EN_1.PNG)
+
+The currencies available will be the same as those in the [trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) of each store.
+
+<div class="alert alert-warning">
+You must choose the currency when creating each gift card or a batch of gift cards since you cannot change the gift card currency after it has been created.
+</div>
diff --git a/docs/announcements/en/multilanguage-checkout-launch.md b/docs/announcements/en/multilanguage-checkout-launch.md
new file mode 100644
index 000000000..a23148226
--- /dev/null
+++ b/docs/announcements/en/multilanguage-checkout-launch.md
@@ -0,0 +1,26 @@
+---
+title: 'Multilanguage Checkout: Internationalize your store'
+id: 6qvNJhChyccFS8mWoESMue
+status: PUBLISHED
+createdAt: 2024-04-22T16:22:22.210Z
+updatedAt: 2024-04-26T15:32:14.356Z
+publishedAt: 2024-04-26T15:32:14.356Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: multilanguage-checkout-launch
+locale: en
+legacySlug: multilanguage-checkout-launch
+announcementImageID: ''
+announcementSynopsisEN: 'Explore the new Multilanguage Checkout and expand your store globally by offering a localized shopping experience.'
+---
+
+We are introducing **Multilanguage Checkout**, a new feature designed to enhance your store's shopping experience, regardless of the country. As of 04/29/2024, your customers can enjoy an internationalized buying journey, from catalog browsing to the checkout process.
+
+## What has changed?
+
+With **Multilanguage Checkout**, we have implemented a complete solution that translates your product catalog into different languages previously added by merchants. This feature allows your customers to explore and buy products regardless of their language, providing a more fluid and customized shopping experience. The product and its information will be displayed in the same language on the storefront during browsing and at checkout.
+
+## What needs to be done?
+
+No action is required, as the update will be applied automatically to all VTEX stores as of 04/29/2024. If you want to add translations to the catalog, follow the instructions in the guide [Translating Catalog content](https://developers.vtex.com/docs/guides/catalog-internationalization) to add them to your catalog.
diff --git a/docs/announcements/en/my-authentication-section-in-my-account.md b/docs/announcements/en/my-authentication-section-in-my-account.md
index a4018efc3..1b79bb500 100644
--- a/docs/announcements/en/my-authentication-section-in-my-account.md
+++ b/docs/announcements/en/my-authentication-section-in-my-account.md
@@ -25,15 +25,15 @@ This change will affect all VTEX stores. Because this change interferes with som
 
 In this section, all users can manage their password and login sessions, allowing them to sign out other sessions remotely. For more details on using My Authentication, see the [Authentication section on the article Setting up My account](https://help.vtex.com/en/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh).
 
-![My Authentication app EN](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
+![My Authentication app EN](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
 
-![My Authentication Session Management EN](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
+![My Authentication Session Management EN](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
 
 On September 29, the component for managing passwords will also be removed from the user profile page to prevent duplication issues. The images below show examples of a user profile page with and without the password management component.
 
-![My Account with password EN](https://images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/0ae8b228f91e42d0baef43d66e99c43f/My_Account_with_password_EN.png)
+![My Account with password EN](//images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/0ae8b228f91e42d0baef43d66e99c43f/My_Account_with_password_EN.png)
 
-![My Account no password EN](https://images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/08d27ed752e8e08a1019272cc832a182/My_Account_no_password_EN.png)
+![My Account no password EN](//images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/08d27ed752e8e08a1019272cc832a182/My_Account_no_password_EN.png)
 
 ## Why did we make this change?
 
@@ -66,12 +66,12 @@ To make the My authentication section visible for your customers, follow the ste
 1. On the left side menu in the Admin, go to **ACCOUNT SETTINGS**.
 2. Click on **Apps**.
 3. Click on **My apps**.  
-![My apps menu EN](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
+![My apps menu EN](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
 4. Go to the **My Account** app and click on `Settings`.  
-![My apps installed EN](https://images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/eec5a07fc1a77033113a4767b4672fc7/My_apps_installed_EN.png)
+![My apps installed EN](//images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/eec5a07fc1a77033113a4767b4672fc7/My_apps_installed_EN.png)
 5. In the **AUTHENTICATION** field, check the `Visible` box.
 6. Click on `Save`.  
-![My Authentication visible setting EN](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
+![My Authentication visible setting EN](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
 
 You can also directly access the My Account app settings via URL.
 
@@ -80,4 +80,4 @@ You can also directly access the My Account app settings via URL.
 
 After enabling the **Authentication** section, it will be displayed for your customers in their user profiles in your store, and they can access it using the left side menu on the My Account page.
 
-![My Authentication visible setting EN](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
+![My Authentication visible setting EN](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
diff --git a/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md b/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
new file mode 100644
index 000000000..93590e70f
--- /dev/null
+++ b/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
@@ -0,0 +1,44 @@
+---
+title: 'New charts and real-time data in Store Overview (Beta) Admin page'
+id: 6yzy7BYw5rPbaH0WdrAHyI
+status: PUBLISHED
+createdAt: 2023-07-12T13:28:42.856Z
+updatedAt: 2023-08-07T15:31:50.283Z
+publishedAt: 2023-08-07T15:31:50.283Z
+contentType: updates
+productTeam: Management
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: new-charts-and-real-time-data-in-store-overview-beta-admin-page
+locale: en
+legacySlug: new-charts-and-real-time-data-in-store-overview-beta-admin-page
+announcementImageID: ''
+announcementSynopsisEN: "We've redesigned the Admin home page, which now features new graphs with real-time data."
+---
+
+The [Overview (beta)](https://help.vtex.com/en/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) page in your VTEX Admin has been redesigned and now offers new charts, metrics, and views. These new features allow you to monitor your operation in real time, providing insights on metrics for you and your team to get quick feedback on the actions taken in the store and act promptly on improvements.
+
+![EN visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/88b40023b0c9d38dae93d2ccb563e378/EN_visa__o_geral_beta.png)
+
+## What has changed?
+
+We have improved the interface and data updates to optimize your analysis. The changes include:
+
+- **Real-time data:** The charts in the Monitoring section update automatically within three minutes, depending on the view. Other page sections are updated every 15 minutes.  
+- **Improved charts:** Now the _Revenue captured_, _Orders captured_, and _New sessions_ charts are highlighted, displaying both growth or decrease percentages, in addition to the absolute value. These new charts have replaced the old _Order trend analysis_ and _Highest grossing categories_ charts. The _Sales funnel_ is now within the _Conversion rate_ metric, and you can access it by clicking the arrow icon <i class='fa fa-chevron-down'></i>.  
+- **Metric changes:** We have removed the _Popular products without stock_ and _Orders with payment in authorization_ metrics to focus on revenue and order metrics. Besides, we have included the new _Orders canceled_ metric, which can be viewed in the _Orders captured_ chart, as we believe this metric better indicates the health of an operation.  
+- **New views:** Toggle between the `Accumulated` and `Last 2 hours` views to tailor the view to your needs. The _Accumulated_ option is ideal for tracking the overall performance of actions in the store, while the _Last 2 hours_ option allows you to identify any unexpected behavior.    
+
+## Why did we make this change?
+
+We have made changes to the Overview (Beta) page to provide more clarity to your operation, ensuring that the store is performing as expected.
+
+Real-time data supports your team in analyzing campaign results and identifying potential negative impacts from configuration changes or deploys. The highlighted metrics indicate whether there has been an impact on the number of orders, sessions, or customer conversion, affecting the health and performance of your business.  
+
+## What needs to be done?
+
+The updated version of the [Store Overview (Beta)](https://help.vtex.com/en/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) page will be available in the VTEX Admin as of August 17th. To access the page, in the VTEX Admin, go to **Dashboards > Overview (Beta)**, or type _Overview (Beta)_ in the search bar at the top of the page.
+
+The page will be available for free during its beta phase or as determined by VTEX, but note that extra fees may apply in the future.
+
+The current Overview page in the VTEX Admin will remain available for use and can be accessed from the[ Dashboards](https://help.vtex.com/en/tutorial/dashboards-overview--1yn2nZUoXtDO3teTEJsCNl) menu in your Admin.
+
diff --git a/docs/announcements/en/new-checkout-settings-for-bot-attack-protection.md b/docs/announcements/en/new-checkout-settings-for-bot-attack-protection.md
new file mode 100644
index 000000000..bff5069ef
--- /dev/null
+++ b/docs/announcements/en/new-checkout-settings-for-bot-attack-protection.md
@@ -0,0 +1,52 @@
+---
+title: 'New Checkout settings for bot attack protection'
+id: 3kA92hues6c2XgRe1uf2Or
+status: DRAFT
+createdAt: 2023-09-11T17:23:20.383Z
+updatedAt: 2024-06-28T18:38:49.327Z
+publishedAt: 
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: new-checkout-settings-for-bot-attack-protection
+locale: en
+legacySlug: new-checkout-settings-for-bot-attack-protection
+announcementImageID: ''
+announcementSynopsisEN: 'New Checkout settings improve security by preventing fraud and unauthorized orders.'
+---
+
+
+To improve the security of your store information, VTEX implemented new Checkout settings, boosting protection against possible attacks by software simulating human behavior (bots).
+
+## What has changed?
+
+The following settings are now available:
+
+- [Require login when completing a purchase](#require-login-when-completing-a-purchase).
+- [Minimum time between orders](#minimum-time-between-orders)
+- [Minimum time a cart remains open to allow the use of a new credit card](#minimum-time-a-cart-remains-open-to-allow-the-use-of-a-new-credit-card)
+
+### Require login when completing a purchase
+
+The `requiresLoginToPlaceOrder` field allows only authenticated customers to proceed with a purchase.
+The customer must be logged in using the same email provided when adding products to the cart.
+ When you enable this field, the checkout without login option, known as [SmartCheckout](https://help.vtex.com/en/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB) remains disabled for all store customers.
+
+### Minimum time between orders
+
+The `minimumPurchaseDowntimeSeconds` field allows you to set the minimum time a customer must wait before placing another order.
+This configuration reduces the risk of several accounts being created in a row to complete a purchase.
+
+### Minimum time a cart remains open to allow the use of a new credit card
+
+The `cartAgeToUseNewCardSeconds` field allows you to set a minimum time frame for a cart to remain active before a new credit card is authorized to be used for it.
+This setting reduces the risk of creating multiple carts and adding new credit cards.
+Activating this field does not affect orders placed with cards previously saved in the customer account.
+
+## Why did we make this change?
+
+We created these new settings to improve security against fraud attempts and unauthorized orders, boosting merchant security and customer account protection.
+
+## What needs to be done?
+
+The new settings are available in the [Update an account's orderForm configuration](https://developers.vtex.com/docs/guides/update-an-account-orderform-configuration) endpoint. For more information on activating the fields in each setting, go to [New Checkout Settings for Bot Attack Protection](https://developers.vtex.com/updates/release-notes/2023-09-12-new-checkout-settings-for-bot-attack-protection).
diff --git a/docs/announcements/en/new-documentation-explore-the-technical-aspects-of-the-platform.md b/docs/announcements/en/new-documentation-explore-the-technical-aspects-of-the-platform.md
new file mode 100644
index 000000000..6fd0d1d71
--- /dev/null
+++ b/docs/announcements/en/new-documentation-explore-the-technical-aspects-of-the-platform.md
@@ -0,0 +1,40 @@
+---
+title: 'New documentation: Explore the technical aspects of the platform'
+id: 6cMtwOjX7hawCKAE1XZeWt
+status: PUBLISHED
+createdAt: 2024-06-03T18:05:03.937Z
+updatedAt: 2024-06-05T17:29:34.519Z
+publishedAt: 2024-06-05T17:29:34.519Z
+contentType: updates
+productTeam: VTEX IO
+author: YRJ73j8mt38D5TUleocQB
+slug: new-documentation-explore-the-technical-aspects-of-the-platform
+locale: en
+legacySlug: new-documentation-explore-the-technical-aspects-of-the-platform
+announcementImageID: ''
+announcementSynopsisEN: 'Understand how our engineering decisions can leverage your business with the VTEX Platform Overview documentation.'
+---
+
+Thinking of facilitating access to technical information about our platform, we have made available the VTEX Platform Overview, a new documentation that presents the main features of VTEX in a single place, in a clear and objective way.
+
+## What is the VTEX Platform Overview?
+
+The [**VTEX Platform Overview**](https://developers.vtex.com/docs/guides/vtex-platform-overview) is a new set of articles that provides a comprehensive overview of our platform, emphasizing the technical aspects essential to empowering your team and maximizing the potential of your business. The content is available in English on the Developer Portal.
+
+Here's an introduction of what you will find in each article:
+
+- [**Cloud infrastructure**](https://developers.vtex.com/docs/guides/cloud-infrastructure): Understand how our multi-tenant infrastructure and cloud-based architecture guarantee the scalability, reliability, and performance of your business.
+
+- [**Security**](https://developers.vtex.com/docs/guides/security): Learn how VTEX manages authentication, access controls, attack protection, incident response, and other measures and best practices to protect your store.
+
+- [**Data privacy**](https://developers.vtex.com/docs/guides/data-privacy): Understand how we ensure compliance with data privacy regulations and how our platform's features can help merchants and developers protect shoppers' personal data.
+
+- [**Composability**](https://developers.vtex.com/docs/guides/composability): Learn how our platform's composable commerce model allows you to create customized solutions for your business needs, maximizing efficiency and scalability.
+
+- [**Store Architecture**](https://developers.vtex.com/docs/guides/store-architecture): Explore the architecture models of VTEX stores, which are adapted to suit different business models.
+
+- [**Developer experience**](https://developers.vtex.com/docs/guides/developer-experience): Learn about the main tools we offer to improve the developer experience, applicable both to building and deploying apps with [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) and to our solutions for [storefront](https://developers.vtex.com/docs/guides/getting-started-with-storefront-solutions).
+
+## Why did we create this content?
+
+To provide easy access to the platform's technical information, fostering confidence, autonomy, and efficiency in processes related to these topics.
diff --git a/docs/announcements/en/new-feature-product-feedback-in-the-vtex-admin.md b/docs/announcements/en/new-feature-product-feedback-in-the-vtex-admin.md
new file mode 100644
index 000000000..f781e2e2e
--- /dev/null
+++ b/docs/announcements/en/new-feature-product-feedback-in-the-vtex-admin.md
@@ -0,0 +1,25 @@
+---
+title: 'New feature: Product Feedback in the VTEX Admin'
+id: 4uZsA31friMnSs4kkVMC0w
+status: PUBLISHED
+createdAt: 2024-07-01T11:15:19.350Z
+updatedAt: 2024-07-01T16:01:07.956Z
+publishedAt: 2024-07-01T16:01:07.956Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: new-feature-product-feedback-in-the-vtex-admin
+locale: en
+legacySlug: new-feature-product-feedback-in-the-vtex-admin
+announcementImageID: ''
+announcementSynopsisEN: 'The new "Product Feedback" feature in the VTEX Admin allows you to share your feedback with our team.'
+---
+
+We are launching a new feature in the VTEX Admin: the Give Feedback button.
+You can share your experience on our platform through this button, which can be found in the top bar of the page after clicking the Information Center icon.
+
+## Why did we make this change?
+The Give Feedback button allows the VTEX development team to receive feedback more efficiently, improving communication with our users and allowing us to improve our products and services to meet client needs.
+
+## What needs to be done?
+No action is required. The feature is available automatically in all stores. For more information, go to [Admin VTEX: Start Here](https://help.vtex.com/en/tutorial/admin-vtex-comece-aqui--531cHtUCUi3puRXNDmKziw).
diff --git a/docs/announcements/en/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md b/docs/announcements/en/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
new file mode 100644
index 000000000..f7d8d0361
--- /dev/null
+++ b/docs/announcements/en/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
@@ -0,0 +1,26 @@
+---
+title: 'New features for VTEX Sales App: Custom displays by store and collection'
+id: 2J9rtMQDyY6OdWDdyYWJ3X
+status: PUBLISHED
+createdAt: 2024-06-27T12:29:38.823Z
+updatedAt: 2024-06-28T12:58:10.676Z
+publishedAt: 2024-06-28T12:58:10.676Z
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: new-features-for-vtex-sales-app-custom-displays-by-store-and-collection
+locale: en
+legacySlug: new-features-for-vtex-sales-app-custom-displays-by-store-and-collection
+announcementImageID: ''
+announcementSynopsisEN: 'New VTEX features: Enhancing product visibility with window displays by store and collection.'
+---
+
+We have made available two new features for VTEX Sales App: custom displays by store and collection. These features have been developed to enhance product display and improve the customer shopping experience:
+- **Custom display by store:** Merchants can now highlight a product page by specifying the store ID to which the product will be linked in [Master Data](https://developers.vtex.com/docs/guides/master-data-introduction), allowing them to create customized custom displays tailored to each store.
+- **Collection custom display:** Enables you to manage a section of the custom display using a specific [collection from the catalog](https://help.vtex.com/en/tutorial/criando-colecao-de-produtos--tutorials_244). Merchants can set the custom display name and collection identifier, making it easier to organize products and highlight collections to customers.
+
+## Why did we make this change?
+We developed these features to help merchants efficiently create customized offers and organize their custom displays around product collections.
+
+## What needs to be done?
+No action is required, as the feature will be automatically applied to all stores using VTEX Sales App. For more information, please see the [VTEX Sales App announcements](https://help.vtex.com/en/tutorial/anuncios-do-vtex-sales-app--3UtOFwbwD4muz3p72RBPmC). 
diff --git a/docs/announcements/en/new-google-and-yahoo-requirements-for-bulk-email-senders.md b/docs/announcements/en/new-google-and-yahoo-requirements-for-bulk-email-senders.md
new file mode 100644
index 000000000..986ed86f3
--- /dev/null
+++ b/docs/announcements/en/new-google-and-yahoo-requirements-for-bulk-email-senders.md
@@ -0,0 +1,74 @@
+---
+title: 'New Google and Yahoo requirements for bulk email senders'
+id: 4Tb5eIYJVnKHAK2hPHY1uZ
+status: PUBLISHED
+createdAt: 2024-01-25T21:37:28.950Z
+updatedAt: 2024-01-26T00:23:10.235Z
+publishedAt: 2024-01-26T00:23:10.235Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: new-google-and-yahoo-requirements-for-bulk-email-senders
+locale: en
+legacySlug: new-google-and-yahoo-requirements-for-bulk-email-senders
+announcementImageID: ''
+announcementSynopsisEN: 'Google and Yahoo new requirements for bulk email senders.'
+---
+
+Google and Yahoo are implementing new requirements for bulk email senders. They aim to ensure greater security for recipients, reduce the number of spam messages, and provide a better user experience.
+
+As of February 2024, based on its [Email sender guidelines](https://support.google.com/mail/answer/81126?hl=pt-BR&sjid=15077216349840152409-SA), Google will demand new requirements for senders who send 5,000 or more messages a day to Gmail accounts. Similarly, Yahoo has also defined new [practices for bulk email deliverability](https://senders.yahooinc.com/best-practices/). The requirements stipulated by the companies are:
+
+* Authentication of the sender's email.
+* Making it easy to unsubscribe.
+* Limiting the rate of emails marked as spam.
+
+If senders do not comply with these guidelines, their emails may be rejected or delivered to the recipient's spam box.
+
+## What has changed?
+
+As of February 2024, Google and Yahoo will require bulk email senders to meet the following requirements:
+
+| **Requirements** | **Description** |
+| :---: | :--- |
+| Sender email authentication | <p>Senders must authenticate their emails using the following protocols:</p><p><ul><li><a href="https://support.google.com/a/answer/33786?sjid=4150033421619503412-SA">SPF</a> (Sender Policy Framework)</li><li><a href="https://support.google.com/a/answer/174124?sjid=4150033421619503412-SA">DKIM</a> (DomainKeys Identified Mail)</li><li><a href="https://support.google.com/a/answer/2466580?sjid=4150033421619503412-SA">DMARC</a> (Domain-based Message Authentication, Reporting & Conformance)</li></ul></p><p>By implementing these settings, you protect yourself against spoofing (fake messages sent on behalf of your domain) and prevent your outgoing messages from being marked as spam.</p><p>Learn more in the <a href="https://support.google.com/a/answer/10583557">Prevent spam, spoofing & phishing with Gmail authentication</a> article.</p> |
+| Make it easy to unsubscribe | <p>Recipients must be able to unsubscribe from an email with a single click, and the unsubscribe request must be processed within two days.</p><p>Learn more about <a href="https://support.google.com/mail/answer/81126#subscriptions">Subscriptions</a> (Google) and <a href="https://blog.postmaster.yahooinc.com/post/182917670818/dont-want-to-be-marked-as-spam-support-one-click">Support one click unsubscribe</a> (Yahoo).</p> |
+| Spam rate limit | <p>Recipients must consider the emails as desirable, so the rate of emails marked as spam must be less than 0.1%, and the sender must prevent it from reaching 0.3% or more. This rate refers to the number of emails marked as spam by recipients divided by the total number of emails received.</p><p>You can use <a href="https://support.google.com/mail/answer/14289100">Postmaster Tools</a> to track data on large numbers of Gmail emails and <a href="https://senders.yahooinc.com/complaint-feedback-loop/">Complaint Feedback Loop</a> for Yahoo.</p> |
+
+The aforementioned requirements are considered fundamental in maintaining email deliverability. For more detailed information on email deliverability best practices, see [Email sender guidelines](https://support.google.com/mail/answer/81126) for Google-related practices, and for Yahoo, see [Email deliverability best practices](https://senders.yahooinc.com/best-practices/).
+
+## What needs to be done?
+
+To be a bulk email sender compliant with Google and Yahoo's requirements, you must:
+
+* [Configure sender email authentication](#configuring-sender-email-authentication)
+* [Allow recipients to easily unsubscribe](#allowing-recipients-to-easily-unsubscribe)
+* [Control the spam rate limit](#controling-the-spam-rate-limit)
+
+If you don't follow these guidelines, your emails may be rejected or delivered to the recipient's spam box. You can check whether you comply with Google's requirements through [Postmaster Tools](https://support.google.com/mail/answer/14289100).
+
+### Configuring sender email authentication
+
+* Configure [SPF authentication](https://support.google.com/a/answer/33786?sjid=4150033421619503412-SA) for your sending domain.
+* Configure [DKIM authentication](https://support.google.com/a/answer/174124?sjid=4150033421619503412-SA) for your sending domain.
+* Configure [DMARC authentication](https://support.google.com/a/topic/2759254?hl=pt-BR&ref_topic=9061731&sjid=8809025610711525699-SA) for your sending domain (you can check if you have a [valid DMARC record](https://dmarcian.com/dmarc-inspector/)).
+* Define a DMARC policy for your domain (check out Google's [recommended rollout](https://support.google.com/a/answer/10032473?hl=pt-BR&ref_topic=2759254&sjid=8809025610711525699-SA)).
+
+### Allowing recipients to easily unsubscribe
+
+* Give recipients the option to unsubscribe from emails with [a single click](https://blog.postmaster.yahooinc.com/post/182917670818/dont-want-to-be-marked-as-spam-support-one-click).
+* Include a visible unsubscribe link in the message body.
+* Process the unsubscribe request within 2 days.
+
+### Controling the spam rate limit
+
+* Ideally, keep reported spam rates below 0.1%.
+* Avoid reaching a spam rate of 0.3% or more.
+* Monitor spam rates reported in Gmail using [Postmaster Tools](https://gmail.com/postmaster) and in Yahoo using the [Complaint Feedback Loop](https://senders.yahooinc.com/complaint-feedback-loop/).
+
+## Related articles
+
+| **VTEX** | **Google** | **Yahoo** |
+| :--- | :--- | :--- |
+| <p><ul><li><a href="https://help.vtex.com/pt/tutorial/best-practices-on-spf--42t0lkl2VyC6Yewc4wA6wI">Best Practices on Sender Policy Framework (SPF)</a></li><li><a href="https://developers.vtex.com/docs/guides/setting-up-the-spf">Setting up the SPF</a></li><li><a href="https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails">Setting up DKIM for transactional emails</a></li></ul></p> | <p><ul><li><a href="https://developers.vtex.com/docs/api-reference/message-center-api#post-/api/mail-service/pvt/providers/-EmailProvider-/dkim">Generate DKIM keys</a></li><li><a href="https://support.google.com/mail/answer/81126?hl=pt-BR&sjid=15077216349840152409-SA">Email sender guidelines</a></li><li><a href="https://support.google.com/a/answer/14229414?hl=pt-BR&ref_topic=7279058&sjid=15077216349840152409-SA#zippy=%2Co-que-acontece-quando-os-remetentes-n%C3%A3o-atendem-aos-requisitos-nas-diretrizes%2Co-que-acontece-quando-a-taxa-de-spam-do-remetente-excede-o-m%C3%A1ximo-permitido-pelas-diretrizes">Email sender guidelines FAQ</a></li><li><a href="https://support.google.com/a/answer/10583557?hl=pt-BR&sjid=8809025610711525699-SA">Prevent spam, spoofing & phishing with Gmail authentication</a></li></ul></p> | <p><ul><li><a href="https://blog.google/products/gmail/gmail-security-authentication-spam-protection/">Google's announcement</a></li><li><a href="https://senders.yahooinc.com/best-practices/">Best practices - Deliverability</a></li><li><a href="https://senders.yahooinc.com/faqs/">FAQs - Deliverability</a></li><li><a href="https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-less-spam">Yahoo's announcement</a></li></ul></p> |
+
diff --git a/docs/announcements/en/new-indexation-history-screen.md b/docs/announcements/en/new-indexation-history-screen.md
index f68e13404..2412a2f0e 100644
--- a/docs/announcements/en/new-indexation-history-screen.md
+++ b/docs/announcements/en/new-indexation-history-screen.md
@@ -19,7 +19,7 @@ In every ecommerce operation, it is necessary to add or edit product information
 
 To improve the catalog indexing monitoring experience, we redesigned the **Indexing History** page in the VTEX Admin. The new interface allows you to track the indexing time of products and the indexing status of your store.
 
-![Histórico da Indexação 1 - EN](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/new-orders-module-interface-official.md b/docs/announcements/en/new-orders-module-interface-official.md
index 1fa947490..ffe3ecfd6 100644
--- a/docs/announcements/en/new-orders-module-interface-official.md
+++ b/docs/announcements/en/new-orders-module-interface-official.md
@@ -27,15 +27,15 @@ The new interface, which will be official as of February 1st, has two main new f
 
 * **No-date limit order search:** You can search for orders without setting a date limit, which returns all orders related to the criteria used, regardless of the order creation date. This search cannot be combined with other filters. However, you can select a custom search period of up to 6 months and then combine it with the filters. Learn more in the article [Filter orders on All orders](https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192).
 
-  ![busca_sem_limite_data_all_en](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
+  ![busca_sem_limite_data_all_en](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
 
 * **Order diagram:** In the _Order status_ section of the new interface, by default, a timeline with the events of the order is displayed. Now you can also see the _Order diagram_. When you click `View diagram`, a modal opens and displays the following image:
 
-  ![diagrama_pedido_en](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
+  ![diagrama_pedido_en](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
 
 For those not using the beta version yet, the image below maps the  fields between the old and new versions of the **Order Details** page:
 
-![board_comparativo_interface_pedido_v2_en](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
+![board_comparativo_interface_pedido_v2_en](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/new-payment-features-enhancements-for-an-improved-shopping-experience.md b/docs/announcements/en/new-payment-features-enhancements-for-an-improved-shopping-experience.md
index c8753c77a..f3d0bd1da 100644
--- a/docs/announcements/en/new-payment-features-enhancements-for-an-improved-shopping-experience.md
+++ b/docs/announcements/en/new-payment-features-enhancements-for-an-improved-shopping-experience.md
@@ -3,8 +3,8 @@ title: 'New Payment Features: enhancements for an Improved Shopping Experience'
 id: 3b5C6DabaGrWsS9Jahs75D
 status: PUBLISHED
 createdAt: 2023-05-29T14:05:55.900Z
-updatedAt: 2023-05-29T14:10:59.814Z
-publishedAt: 2023-05-29T14:10:59.814Z
+updatedAt: 2024-04-04T19:35:42.974Z
+publishedAt: 2024-04-04T19:35:42.974Z
 contentType: updates
 productTeam: Shopping
 author: 2o8pvz6z9hvxvhSoKAiZzg
diff --git a/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
new file mode 100644
index 000000000..adc379ef8
--- /dev/null
+++ b/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
@@ -0,0 +1,36 @@
+---
+title: 'New payment provider and anti-fraud management interface'
+id: Qx6SkUJqM8DwoZajvAP0k
+status: PUBLISHED
+createdAt: 2023-12-22T09:09:05.292Z
+updatedAt: 2024-01-22T20:43:27.828Z
+publishedAt: 2024-01-22T20:43:27.828Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: new-payment-provider-and-anti-fraud-management-interface
+locale: en
+legacySlug: new-payment-provider-and-anti-fraud-management-interface
+announcementImageID: ''
+announcementSynopsisEN: 'View information on payment and anti-fraud providers more quickly'
+---
+
+VTEX is launching a new interface on its payment and anti-fraud provider page in the VTEX Admin, which offers a more intuitive and efficient experience for your operation.
+
+## What has changed?
+
+From now on, you can view the information of providers in your store more quickly. The new layout allows filtering payment and anti-fraud providers by name, type, and operation environment (test or production).
+
+The screen for adding a new provider, editing settings, and searching for providers was also improved for better navigation.
+
+![new_admin_providers_interface](//images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/af1aed9f59ac711ba1f07d5d84b54eb5/Announcement_interface_provedor_EN.JPG)
+
+## What needs to be done?
+
+The new payment and anti-fraud provider management page is now automatically available for all VTEX accounts. To leverage the new experience in the VTEX Admin, go to __Store Settings > Payment > Providers__.
+
+Learn more about the new interface features in [Register payment and anti-fraud providers](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
+
+<div class = "alert alert-warning">
+  The previous version of the affiliations management interface, available at <b>Store Settings > Payment > Settings > Gateway Affiliations</b>, will still be accessible until January 14, 2024.
+</div>
diff --git a/docs/announcements/en/new-permission-required-to-manage-redirects-in-store-framework-cms.md b/docs/announcements/en/new-permission-required-to-manage-redirects-in-store-framework-cms.md
new file mode 100644
index 000000000..7d7916494
--- /dev/null
+++ b/docs/announcements/en/new-permission-required-to-manage-redirects-in-store-framework-cms.md
@@ -0,0 +1,34 @@
+---
+title: 'Store Framework CMS: New permission required to manage redirects'
+id: 1GcT48ML2w6TZQxQyGbD6W
+status: PUBLISHED
+createdAt: 2023-08-31T18:10:04.246Z
+updatedAt: 2023-09-05T16:32:32.516Z
+publishedAt: 2023-09-05T16:32:32.516Z
+contentType: updates
+productTeam: VTEX IO
+author: 4ubliktPJIsvyl1hq91RdK
+slug: new-permission-required-to-manage-redirects-in-store-framework-cms
+locale: en
+legacySlug: store-framework-cms-new-permission-required-to-manage-redirects
+announcementImageID: ''
+announcementSynopsisEN: 'Creating redirects in the Store Framework CMS requires a role with the "CMS Settings" resource.'
+---
+
+**Redirects** is a Store Framework CMS feature that automatically redirects a store user to an internal or external page when they visit a specific page. For security purposes, we now require Admin users to have specific permission to create redirects.
+
+## What has changed?
+
+To allow Admin users to create, edit, and remove redirects in the CMS, they must have a role with the [License Manager](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) **CMS Settings** resource.
+
+## Why did we make this change?
+
+We added this required permission for security purposes. Thus, only Admin users who have been explicitly authorized will have access to the **Redirects** feature, preventing unauthorized users from creating, editing, and removing redirects.
+
+## What needs to be done?
+
+For an existing Admin user to be able to manage redirects in the Store Framework CMS, they need to be assigned a user role that includes the **CMS Settings** resource. Check the instructions for editing a user's role in the [How to manage users article](https://help.vtex.com/en/tutorial/managing-users--tutorials_512#editing-users).
+
+If you want to use a customized role, you can create a new role or edit an existing one to include the **CMS Settings** resource. Check the instructions for creating and editing roles in the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role) article.
+
+Learn more about redirects in the [Managing URL redirects](https://help.vtex.com/en/tutorial/managing-url-redirects--3UJuFrU8imSVWg134mkvJV) article.
diff --git a/docs/announcements/en/new-process-for-security-testing.md b/docs/announcements/en/new-process-for-security-testing.md
new file mode 100644
index 000000000..a064a656f
--- /dev/null
+++ b/docs/announcements/en/new-process-for-security-testing.md
@@ -0,0 +1,34 @@
+---
+title: 'New process for security testing'
+id: 7z6kjzqf2yZyRuwIXOfY3o
+status: PUBLISHED
+createdAt: 2023-09-05T13:50:09.793Z
+updatedAt: 2023-09-05T13:57:39.737Z
+publishedAt: 2023-09-05T13:57:39.737Z
+contentType: updates
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: new-process-for-security-testing
+locale: en
+legacySlug: new-process-for-security-testing
+announcementImageID: ''
+announcementSynopsisEN: 'We have updated our penetration test procedure to make it even more secure.'
+---
+
+VTEX periodically performs vulnerability checks through recurring scanning and penetration tests (_pen tests_). These procedures allow us to evaluate the level of security maturity of our platform.
+
+If necessary, you can run a penetration test on your own — provided you are authorized by VTEX — and report any vulnerabilities found. To assist with this, the VTEX Security team has updated the procedure merchants should follow to perform a penetration test in their store environment.
+
+## What has changed?
+
+In summary, the new process for running penetration tests consists of:
+
+1. Submit a request to schedule a test through [VTEX Support](https://help.vtex.com/en/support).
+2. Review and sign the [confidentiality agreement](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip) before running any tests.
+3. Once the test is complete, share the results with the VTEX Security team.
+
+For more detailed information on this procedure, see the [Penetration tests and vulnerability notifications](https://help.vtex.com/en/tutorial/penetration-testing-and-vulnerability-notice--6jodF6s1I50Fg84ZwutOCb) guide.
+
+## Why did we make this change?
+
+We have updated the penetration testing procedure to ensure the platform is secure and checks are run securely, preventing [unauthorized procedures](https://help.vtex.com/en/tutorial/penetration-testing-and-vulnerability-notice--6jodF6s1I50Fg84ZwutOCb#unauthorized-procedures) and actions that could harm our customers.
diff --git a/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md b/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md
index ec3526b13..af9c2f77c 100644
--- a/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md
+++ b/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md
@@ -30,7 +30,7 @@ We developed a new interface for the Promotion List, which includes:
 * Exporting your active promotions list.
 * Duplicating active or archived promotions for a faster creation process.
 
-![lista-promocoes-en](https://images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/f08b0d232c4b386e29cc75c436f91471/promotions-list-en.PNG)
+![lista-promocoes-en](//images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/f08b0d232c4b386e29cc75c436f91471/promotions-list-en.PNG)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/new-roles-page.md b/docs/announcements/en/new-roles-page.md
new file mode 100644
index 000000000..c8d31e1c7
--- /dev/null
+++ b/docs/announcements/en/new-roles-page.md
@@ -0,0 +1,35 @@
+---
+title: 'New Roles page'
+id: 6kAbgyB0Ah8WK4ZAj7aSSL
+status: DRAFT
+createdAt: 2023-11-30T16:11:56.563Z
+updatedAt: 2023-11-30T16:25:18.794Z
+publishedAt: 
+contentType: updates
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: new-roles-page
+locale: en
+legacySlug: new-roles-page
+announcementImageID: ''
+announcementSynopsisEN: 'We redesigned the roles page to display more detailed and structured information.'
+---
+
+Many employees access the Admin environment from each account. Therefore, it is essential to limit access to critical actions to ensure that users can only access what is necessary for their role.
+
+In this context, the roles feature is used to assign a set of [resources](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) to admin users, granting them the necessary permissions for store activities.
+
+We have redesigned the **Roles** page to optimize the management of user permissions. To view this page, at the top bar of the VTEX Admin, click your profile avatar — indicated by the first letter of your email — and then click **Account settings** > **User roles**.
+
+## What has changed?
+
+Besides all features from the previous version, the new **Roles** page allows you to:
+
+*	Access the complete list of roles added to your store with a more intuitive and elegant design, updated for the [New VTEX Admin](https://help.vtex.com/en/tutorial/admin-vtex-start-here--531cHtUCUi3puRXNDmKziw).
+*	View useful information for managing roles directly in the list, such as the number of users associated with each profile, the type of profile (predefined or customized), and the date the profile was created.
+
+![roles-en](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/d0c8e68b433a987fb1d0c9f031726d6f/roles-en.png)
+
+## What needs to be done?
+
+This update will be automatically applied to all stores. Learn more on how to use the enhanced page in the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) article.
diff --git a/docs/announcements/en/new-rules-for-activating-vtex-support.md b/docs/announcements/en/new-rules-for-activating-vtex-support.md
new file mode 100644
index 000000000..36e10d2b9
--- /dev/null
+++ b/docs/announcements/en/new-rules-for-activating-vtex-support.md
@@ -0,0 +1,33 @@
+---
+title: 'New rules for activating VTEX Support in Brazil'
+id: 18xfVJM9tbzpyqAUzIsBC1
+status: PUBLISHED
+createdAt: 2023-12-01T17:11:24.955Z
+updatedAt: 2023-12-13T14:03:46.024Z
+publishedAt: 2023-12-13T14:03:46.024Z
+contentType: updates
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: new-rules-for-activating-vtex-support
+locale: en
+legacySlug: new-rules-for-activating-vtex-support
+announcementImageID: ''
+announcementSynopsisEN: "For accounts in Brazil, it's now required the Open Support Ticket feature in the access profile to use VTEX support."
+---
+
+Now, for Brazil accounts to contact VTEX Support, the  **Open Support Ticket** resource of the **VTEX - Support** product must be enabled in their role. A user with the *User Administrator - Restricted* role must configure this permission in [License Manager](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
+
+<div class="alert alert-info">Admin users with the <strong> Owner (Admin Super) </strong> role are automatically associated with the <em> Open Support Ticket</em> resource.</div> 
+
+## What has changed?
+
+The configuration is only valid for Brazil accounts and restricts the ability to open support tickets to users with permission. To open a request to the support team, the user must have the **Open Support Ticket** resource of the **VTEX - Support** product in their [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+## Why did we make this change?
+
+In terms of best security practices, this step aims to enhance the protection of the store's sensitive information.
+
+## What needs to be done?
+
+A user with the *User Administrator - Restricted* role needs to assign the **Open Support Ticket** resource of the **VTEX - Support** product in [License Manager](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) to the [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) of the users that should have permission to open support tickets.
+
diff --git a/docs/announcements/en/new-sales-app-performance-monitor.md b/docs/announcements/en/new-sales-app-performance-monitor.md
new file mode 100644
index 000000000..3bfe90b64
--- /dev/null
+++ b/docs/announcements/en/new-sales-app-performance-monitor.md
@@ -0,0 +1,33 @@
+---
+title: 'New Sales App Performance Monitor'
+id: 1xi0UVrKl5SwQbwts907bh
+status: PUBLISHED
+createdAt: 2023-09-05T19:37:19.176Z
+updatedAt: 2023-09-06T13:06:33.383Z
+publishedAt: 2023-09-06T13:06:33.383Z
+contentType: updates
+productTeam: Shopping
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: new-sales-app-performance-monitor
+locale: en
+legacySlug: new-sales-app-performance-monitor
+announcementImageID: ''
+announcementSynopsisEN: 'Performance Monitor allows your sales associates to know how much they have sold through the solution.'
+---
+
+[Performance Monitor](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/5pqtuvi97FFZiGf7MlSe8q) is the new VTEX Sales App feature. It allows your sales associates to know exactly how much they have sold through the solution and view key retail indicators, such as average ticket, average number of items per sale, and average amount per item.
+It also shows your sales associates how their performance compares to your store average.
+
+These data are also available to managers accessing the VTEX Admin to closely monitor the performance of their sales associates and stores.
+# What has changed?
+The Sales App's side menu now features the Sales Performance option, where sales associates can view their own sales performance and that of other employees.
+
+# What needs to be done?
+The feature is enabled by default for all accounts using the app. The only exception is for brands that already use the Indeva by VTEX solution, which requires contacting support to activate the feature.
+
+For more information about Sales App, see the following documentation:
+- [Sales App - First steps and setting up](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf)
+- [Sales App - Payments](https://help.vtex.com/en/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/2liigRors32hzqBNs2M1Oa)
+- [Sales App - Using the app](https://help.vtex.com/en/tracks/instore-using-the-app--4BYzQIwyOHvnmnCYQgLzdr/6cq4E1JCmA6vCvBCCtAgIM)
+- [Unified commerce strategies](https://help.vtex.com/en/tracks/unified-commerce-strategies--3WGDRRhc3vf1MJb9zGncnv/2LGAiUnHES1enjHsfi8fI3)
+
diff --git a/docs/announcements/en/new-sales-performance-dashboard.md b/docs/announcements/en/new-sales-performance-dashboard.md
index 53112a837..44a3f6a6a 100644
--- a/docs/announcements/en/new-sales-performance-dashboard.md
+++ b/docs/announcements/en/new-sales-performance-dashboard.md
@@ -19,7 +19,7 @@ With an ever-increasing volume of data available for ecommerce operations to eva
 
 The dashboard allows users to analyze data from all sales channels of the store and its sellers, including metrics on revenue, orders, average ticket, and more. It also includes charts and tables so you can compare results from different periods, and introduces eleven filter options to provide unified insights into your entire operation.
 
-![Sales Perf Dash EN](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
+![Sales Perf Dash EN](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
 
 ## What has changed?
 Previously, your VTEX Admin only had the Insights page to generate business intelligence from your operations data. We have now included the Sales Performance page, where you can have a more detailed view of the results of the different sales channels of your store. The Insights page will remain in your VTEX Admin.
diff --git a/docs/announcements/en/new-sku-bindings-interface.md b/docs/announcements/en/new-sku-bindings-interface.md
index 0e991ecf2..7abaad92d 100644
--- a/docs/announcements/en/new-sku-bindings-interface.md
+++ b/docs/announcements/en/new-sku-bindings-interface.md
@@ -19,7 +19,7 @@ VTEX allows your store to act both as a [seller](https://help.vtex.com/en/tutori
 
 To improve this experience, we redesigned the **SKU Bindings** page in the VTEX Admin. The new interface allows you to track and manage the binding relationship between seller and marketplace SKUs in a simpler and more agile way.
 
-![sku_binding_page_EN_final](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/495c45bef9699a32fbfb55842890a91f/sku_binding_page_EN_final.png)
+![sku_binding_page_EN_final](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/495c45bef9699a32fbfb55842890a91f/sku_binding_page_EN_final.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/new-subscriptions-module.md b/docs/announcements/en/new-subscriptions-module.md
index 66a0491a4..69e262c44 100644
--- a/docs/announcements/en/new-subscriptions-module.md
+++ b/docs/announcements/en/new-subscriptions-module.md
@@ -39,37 +39,37 @@ The improvements to the Subscription system include new features for your end cu
 #### Subscription details 
 Our subscription details page has been redesigned to improve customer experience by reducing the time to find information and perform tasks. In addition, a new feature allows you to add items to an existing subscription.
 
-![img1 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/01b71fce5ac6f65621c37a917a798050/img1_subscriptions_EN.png)
+![img1 subscriptions EN](//images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/01b71fce5ac6f65621c37a917a798050/img1_subscriptions_EN.png)
 
 #### Notification box
 Now you can use a notification box to improve your communication with users about actions they need to perform or to communicate important events about your subscriptions.
 
-![img2 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/b925e16f3a4eefc38b2b2edc6af2333a/img2_subscriptions_EN.png)
+![img2 subscriptions EN](//images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/b925e16f3a4eefc38b2b2edc6af2333a/img2_subscriptions_EN.png)
 
 #### Adding products to your subscription
 You can also add new items to your subscription by searching for products available in the store.
 
-![img3 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/adbd8d1d4cc519b9f687e27f4fea3a5a/img3_subscriptions_EN.png)
+![img3 subscriptions EN](//images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/adbd8d1d4cc519b9f687e27f4fea3a5a/img3_subscriptions_EN.png)
 
 #### Creating a new subscription
 A long-awaited feature is now available: a screen for creating subscriptions. You can now configure a new subscription without the need to go through the checkout and place an order. To do that, click on the __New subscription__ button on the subscriptions list.
 
-![img4 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/784b7439f54cedde4fc381f3a275f556/img4_subscriptions_EN.png)
+![img4 subscriptions EN](//images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/784b7439f54cedde4fc381f3a275f556/img4_subscriptions_EN.png)
 
 ### New subscription concept in the VTEX system
 Previously, in the VTEX system, a subscription consisted of an SKU linked to a purchase configuration. It allowed the customer to subscribe to SKUs with different shipping addresses and different payment methods—which represented an evolution compared to the first version of the system.
 
 #### Before:
-![img5 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/107288b39d263aad20e153aa3c0a045a/img5_subscriptions_EN.png)
+![img5 subscriptions EN](//images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/107288b39d263aad20e153aa3c0a045a/img5_subscriptions_EN.png)
 
-![img6 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/18bbe8fa02f3361873d6e2ceba450d01/img6_subscriptions_EN.png)
+![img6 subscriptions EN](//images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/18bbe8fa02f3361873d6e2ceba450d01/img6_subscriptions_EN.png)
 
-![img7 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/6e0250e84776f69dad0d8f1c17ee1eff/img7_subscriptions_EN.png)
+![img7 subscriptions EN](//images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/6e0250e84776f69dad0d8f1c17ee1eff/img7_subscriptions_EN.png)
 
 The subscription now consists of an SKU list and a particular purchase configuration. This means that we have removed the concept of Subscription Groups from our system. For more information, read our article [How subscription works](https://help.vtex.com/en/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453). The diagram below shows our new subscription concept:
 
 #### Now:
-![img8 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/33a97511d0c48f954b9de33bcad8fa40/img8_subscriptions_EN.png)
+![img8 subscriptions EN](//images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/33a97511d0c48f954b9de33bcad8fa40/img8_subscriptions_EN.png)
 
 ### Subscription order cycle date
 
diff --git a/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md b/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md
index fa095e887..46d34cb30 100644
--- a/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md
+++ b/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md
@@ -22,7 +22,7 @@ The user management dashboard design has been refreshed with the same interface
 - The MFA (multi-factor authentication) configuration is now displayed for each user in the user list.
 - A button to export the user list data to a csv file that includes id, email and name.
 
-![Lista Usuários User Management EN](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
+![Lista Usuários User Management EN](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
 
 In addition, the dashboard has undergone some changes:
 
diff --git a/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md b/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md
index 64df6554a..cf11b2fc3 100644
--- a/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md
+++ b/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: "We've updated the layout for the email you receive when
 
 We've updated the layout for the email you receive when requesting an access code for your admin. From now on, every time access to login or change password is requested, you'll receive an email as the one shown below:
 
-![announcement-novo-layout-email-codigo-acesso EN](https://images.ctfassets.net/alneenqid6w5/5jLkyQ1zg1ZhtORCCLq4OR/3f69be2db4b8edfd6685e74216093b8a/announcement-novo-layout-email-codigo-acesso_EN.png)
+![announcement-novo-layout-email-codigo-acesso EN](//images.ctfassets.net/alneenqid6w5/5jLkyQ1zg1ZhtORCCLq4OR/3f69be2db4b8edfd6685e74216093b8a/announcement-novo-layout-email-codigo-acesso_EN.png)
 
 ## What changes
 The new version makes the layout more seamless and usable, in addition to making it more coherent with VTEX's visual identity.
diff --git a/docs/announcements/en/offer-add-on-services-to-products-sold-in-vtex-sales-app.md b/docs/announcements/en/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
new file mode 100644
index 000000000..c650456ba
--- /dev/null
+++ b/docs/announcements/en/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
@@ -0,0 +1,28 @@
+---
+title: 'Offer add-on services to products sold in VTEX Sales App'
+id: 2kF3T4fCxoNKEKslXezTHL
+status: PUBLISHED
+createdAt: 2024-04-30T13:52:00.217Z
+updatedAt: 2024-04-30T17:15:44.935Z
+publishedAt: 2024-04-30T17:15:44.935Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: offer-add-on-services-to-products-sold-in-vtex-sales-app
+locale: en
+legacySlug: offer-add-on-services-to-products-sold-in-vtex-sales-app
+announcementImageID: ''
+announcementSynopsisEN: 'Assembly Options in VTEX Sales App: Add-on services and item assembly with different SKUs.'
+---
+
+We have developed a new feature for [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p). It allows integration between online and physical sales channels, through which sales associates from physical stores can provide customized services to customers.
+
+## What has changed?
+With the Assembly Options feature, sellers can offer add-on services for their products, such as extended warranties and protection plans. It also makes it possible to assemble sets of multiple SKUs, such as Christmas or breakfast baskets, makeup sets, etc.
+
+## Why did we make this change?
+We developed this feature to allow sellers to offer product customization options through VTEX Sales App.
+
+## What needs to be done?
+No action is required. The feature is already available in VTEX Sales App.
+For more information on how to use this feature, see the article [Assembly Options in VTEX Sales App](https://help.vtex.com/en/tutorial/assembly-options-no-vtex-sales-app--4fTfqOMcXyhAhWXkl935lr).
diff --git a/docs/announcements/en/offer-pickup-points-for-subscription-orders.md b/docs/announcements/en/offer-pickup-points-for-subscription-orders.md
index a0f3bb586..d7eb03bde 100644
--- a/docs/announcements/en/offer-pickup-points-for-subscription-orders.md
+++ b/docs/announcements/en/offer-pickup-points-for-subscription-orders.md
@@ -24,7 +24,7 @@ The pickup points feature for subscriptions is available in beta only for accoun
 
 Previously, pickup was not a delivery option available for subscriptions. With this feature, end customers can choose pickup points for items in a subscription order at checkout, as illustrated in the image below.
 
-![subscriptionspickup EN](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
+![subscriptionspickup EN](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
 
 You can also assign pickup points to new and existing subscriptions via the[ Subscriptions API](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1).
 
diff --git a/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md b/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md
new file mode 100644
index 000000000..b35993fcc
--- /dev/null
+++ b/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md
@@ -0,0 +1,30 @@
+---
+title: 'Offer Status module for integrations with VTEX marketplaces'
+id: 1EeGgit1Brq3mmm8qhv2m3
+status: PUBLISHED
+createdAt: 2024-02-07T20:18:50.779Z
+updatedAt: 2024-03-04T19:21:14.936Z
+publishedAt: 2024-03-04T19:21:14.936Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: offer-status-module-for-integrations-with-vtex-marketplaces
+locale: en
+legacySlug: offer-status-module-for-integrations-with-vtex-marketplaces
+announcementImageID: ''
+announcementSynopsisEN: 'Monitor your offers with the new Offer Status module'
+---
+
+__Offer Status__ is the new VTEX Admin module that allows sellers to monitor offers being sent and synced from integrations with VTEX marketplaces worldwide. To access the module, in the VTEX Admin, go to __Marketplace > Connections > Offer Status,__ or type __Offer Status__ in the search bar.
+
+![Offer Status Screen](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/2de2b349e1c114b7b50db65533eee1df/-EN-_Offer_Status_-_GIF.gif)
+
+## Why did we develop this feature?
+
+We developed the __Offer Status__ module to provide an overview of the process of sending and syncing offers with VTEX marketplaces and allow you to monitor your offers on a single page. Now, you can use different tabs to view the __Published__ offers, identify the __Issues__ that prevented an offer from being published, and monitor the offers __Awaiting completion__ by each marketplace the seller is connected to.
+
+Learn about each module tab and how to use them by reading the [Offer Status](https://help.vtex.com/pt/tutorial/status-de-anuncios-beta--2OE87wU26F7lApl99OdwvJ) tutorial.
+
+## What needs to be done?
+
+No adjustment is required to use the __Offer Status__ module, which will be available for all integrations with VTEX marketplaces as of **February 28, 2024.**
diff --git a/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md b/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
index 05e3f1d3d..6ce198087 100644
--- a/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
+++ b/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
@@ -34,7 +34,7 @@ This change's review and subsequent adjustment should be implemented following t
 
 Required steps for review and adjustment:
 
-1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Customization__: if the "/account/orders" page is affected by any front-end customization, it should be migrated and adapted to the new URL: "/account#/orders". Review and perform all necessary tests to ensure that all custom resources are functioning properly.  
 3. __Site links__: Review and update all of the site's custom links, in addition to the ones pertaining to transactional emails that would previously direct users to "/account/orders". These links should now direct users to "/account#/orders".
 
diff --git a/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md b/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md
new file mode 100644
index 000000000..1ac95286d
--- /dev/null
+++ b/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md
@@ -0,0 +1,79 @@
+---
+title: 'Onboarding guide: your complete journey at VTEX'
+id: 510SdtVmDcuIQAGoAl0sgf
+status: PUBLISHED
+createdAt: 2024-02-22T20:28:44.286Z
+updatedAt: 2024-02-23T14:44:33.307Z
+publishedAt: 2024-02-23T14:44:33.307Z
+contentType: updates
+productTeam: Others
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: onboarding-guide-your-complete-journey-at-vtex
+locale: en
+legacySlug: onboarding-guide-your-complete-journey-at-vtex
+announcementImageID: ''
+announcementSynopsisEN: 'Onboarding guide release: content about the store up to go-live, evolving the operation, and VTEX support.'
+---
+
+With client success in mind, VTEX offers complete solutions for different business models. This puts the flexibility of composable commerce at the service of innovation and growth in your operation.
+
+To help you easily adopt new resources, manage your business autonomously, and gain scalability, we have published the new **Onboarding guide** — content covering the complete journey for operating a VTEX store. This documentation will be available in the [Start here](https://help.vtex.com/en/tracks) section of the Help Center.
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/359WPOFfC5pE91DpoECZJe/ead8add75ce24d17af10d12a439959f0/announcement_complete_guide_EN.png" alt="Onboarding guide">
+</div>
+
+## What is the Onboarding guide?
+
+The **Onboarding guide** is a collection of three documentation tracks, which include planning the store architecture, go-live configurations, products to help evolve your business, and guidelines about our support. The guide describes and contextualizes the platform settings and resources within the VTEX store journey.
+
+The **Onboarding guide** has three tracks:
+
+- [VTEX store overview](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9)
+- [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS)
+- [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy)
+
+<div class="alert alert-info">
+The tracks include content that complement one another, but they are intended to be standalone. This means you can explore the content freely, without following any specific order.
+</div>
+
+Our aim is to allow clients, partners, and the VTEX ecosystem to take advantage of the **Onboarding guide**. We took into account a comprehensive journey to make sure the content stayed relevant for different businesses.
+
+You can find an [overview](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9) of the guide content below.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/1N4nX2r9WxhdSCqr8zOEla/08f6af21193f72196786c3675d950a0e/announcement_headings_track_1_EN.png" height="90" alt="VTEX store track">
+</div>
+
+The **VTEX store track** describes the initial context of the operation, starting by defining the [account type and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) that best suit the business needs. From there, you can complete the [initial setup](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) and configure the platform [modules](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), focusing on getting the operation going. Once the [backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) are completed and the [frontend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) technology has been implemented in order to build the storefront, it's time for the [go-live](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) and launching the new store.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6yRmvP19rt7z1mNE7vdWQz/0e09fd47f72f6177da8f318ea78d0d9f/announcement_headings_track_2_EN.png" height="90" alt="Next steps after go live">
+</div>
+
+The **Next steps after go-live** track describes how [unified commerce](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/5Qvw31yH2FPDBl14K5xXHA) is achieved with the platform resources, including [module settings](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) not mentioned before. The aim here is to focus on evolving the operation. This track also describes VTEX's [add-on products](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm), which are products that can be requested separately for implementing new strategies and diversifying the business.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6N7adQ7RxTfTyuIrCDqstZ/500c3acec9c5f6c7ddc8895df69916ac/announcement_headings_track_3_EN.png" height="90" alt="VTEX Support">
+</div>
+
+The **VTEX Support** track describes the [support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) offered by VTEX to clients, which is not restricted to a specific part of the journey. Other tracks also mention [how support works](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3), since [opening a ticket](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE) is the designated channel for certain requests. The organization of this track aims to help our clients have the best experiences with our services, providing all the necessary information for opening tickets, whether for [technical](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [billing](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl), or [commercial](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) support.
+
+## Why did we create this content?
+
+We organized the **Onboarding guide** to provide autonomy for our clients. Here are some highlights about the guide:
+
+- **Complete journey:** This is the first documentation that covers the complete operational journey of a VTEX store. The content is designed to make go-live faster and reduce the _time to revenue_ of the business.
+- **Brand-new content:** In addition to the new approach of the journey, there is brand-new content, with the following highlights in the _VTEX store track_ ([Accounts and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl), [Backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), [Frontend implementation](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)), in the _Next steps after the go-live track_ ([Add-on products](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm)), and the _VTEX Support track_ as a whole.
+- **General relevance:** The value of this guide is not restricted to new clients or stores in the phases before go-live. We envisioned a comprehensive journey to make it relevant for different business models.
+
+We hope this content contributes to the success of your business and your satisfaction with VTEX.
+
+|  | **Onboarding guide** |  |
+| :---: | :---: | :---: |
+| Part I | Part II | Part III |
+| [VTEX store overview](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9) | [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS) | [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy) |
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/4CgTVLjK3cazg4dDyVlB8m/924575a75836acd4e7b5e4a4c199b516/announcement_under_table_image_EN.png" alt="Ecommerce image">
+</div>
diff --git a/docs/announcements/en/performance-monitor.md b/docs/announcements/en/performance-monitor.md
new file mode 100644
index 000000000..8213406ae
--- /dev/null
+++ b/docs/announcements/en/performance-monitor.md
@@ -0,0 +1,18 @@
+---
+title: 'Performance Monitor'
+id: 5xIaEr9iAiefNiVbDHJPuK
+status: DRAFT
+createdAt: 2023-08-30T18:48:05.528Z
+updatedAt: 2023-08-30T18:50:40.345Z
+publishedAt: 
+contentType: updates
+productTeam: 
+author: 
+slug: performance-monitor
+locale: en
+legacySlug: performance-monitor
+announcementImageID: ''
+announcementSynopsisEN: ''
+---
+
+
diff --git a/docs/announcements/en/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md b/docs/announcements/en/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
index ad7b4d3ed..1d9345afb 100644
--- a/docs/announcements/en/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
+++ b/docs/announcements/en/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
@@ -3,8 +3,8 @@ title: 'Pix: get ready to offer this new payment method on your e-commerce'
 id: 1v5clxhNiDST404Orzwrv6
 status: PUBLISHED
 createdAt: 2020-10-28T11:13:00.457Z
-updatedAt: 2021-03-16T14:18:44.362Z
-publishedAt: 2021-03-16T14:18:44.362Z
+updatedAt: 2024-05-03T14:59:47.895Z
+publishedAt: 2024-05-03T14:59:47.895Z
 contentType: updates
 productTeam: Financial
 author: 5kCzbURAoPwM0YJGmMCLyD
@@ -20,14 +20,14 @@ Pix transactions - the new payment method offered by Banco Central (Bacen) - a B
 ## What is Pix?
 Pix is the new instant payment method offered by Banco Central (Bacen) - available 24 hours a day, seven days a week - that will realize banking transactions in less than 10 seconds.
 
-To know the benefits and the advantages to accept Pix as a payment method in your e-commerce, [click here](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/ "click here").
+To know the benefits and the advantages to accept Pix as a payment method in your e-commerce, [click here](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/).
 
 ## How partners can integrate with VTEX?
-__From October 19th 2020__, partners will be able to start its integrations using the [Payment Provider Protocol](https://developers.vtex.com/vtex-developer-docs/reference/payment-provider-protocol-api-overview "Payment Provider Protocol") to offer Pix as a payment method to your clients.
+__From October 19th 2020__, partners will be able to start its integrations using the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) to offer Pix as a payment method to your clients.
 
 __Payment institutions that already have a partnership with VTEX__ can get in touch with their Partner Manager. You can also do this solicitation through a [Support ticket](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM "Support ticket").  
 
-__Payment institutions that not VTEX partners__ should fill out our [registration form](https://vtex.com/br-pt/partner/ "registration form") to start the partnership.
+__Payment institutions that not VTEX partners__ should fill out our [registration form](https://vtex.com/us-en/partners) to start the partnership.
 
 ## How VTEX clients can get prepared to offer Pix in your ecommerce?
 
@@ -35,7 +35,7 @@ There are two options:
 
 - Get in touch with the company in charge of managing the payments in your e-commerce. Then, request an integration between VTEX and this company.
 
-- Choose a payment partner that is already in touch with VTEX about Pix then proceed with the contract negotiation and tech configuration. Currently, the available partners are: [PayMee](https://www.paymee.com.br/ "PayMee"), [Spin Pay](https://spinpay.com.br/ "Spin Pay") and [IUGU](https://iugu.com/ "IUGU").
+- Choose a payment partner that is already in touch with VTEX about Pix then proceed with the contract negotiation and tech configuration. Currently, the available partners are: [PayMee](https://www.paymee.com.br/), [Spin Pay](https://spinpay.com.br/ "Spin Pay"), [IUGU](https://iugu.com/ "IUGU"), [Pagar.me](https://help.vtex.com/en/tutorial/setting-up-pagarmev2-gateway--5TugxXNMOs0Ocyg4uqussM) and [Aarin](https://aarin.com.br/).
 
 ## Get in touch with the available partners
 
@@ -45,6 +45,8 @@ Write it down:
 
 - __Spin Pay__:  comercial@spinpay.com.br 
 - __IUGU__: pixvtex@iugu.com 
-- __Paymee__:  www.paymee.com.br or comercial@paymee.com.br 
+- __Paymee__:  www.paymee.com.br or comercial@paymee.com.br
+- __Mercado Pago__: www.mercadopago.com.br
+- __Aarin__: https://aarin.com.br
 
-You can check all our [Payment Provider Protocol documentation](https://developers.vtex.com/vtex-developer-docs/reference/payment-flow#paymentmethods "Payment Provider Protocol documentation") on our Developer Portal and also a [guide of how to use this tool](https://developers.vtex.com/vtex-developer-docs/docs/pix-instant-payments-in-brazil "guide of how to use this tool") on the same web site. 
+You can check all our [Payment Provider Protocol documentation](https://developers.vtex.com/docs/api-reference/payment-provider-protocol) on our Developer Portal and also a [guide of how to use this tool](https://developers.vtex.com/docs/guides/payments-integration-pix-instant-payments-in-brazil) on the same web site. 
diff --git a/docs/announcements/en/price-filters-more-search-flexibility.md b/docs/announcements/en/price-filters-more-search-flexibility.md
index 0add1d5b9..68b088ae1 100644
--- a/docs/announcements/en/price-filters-more-search-flexibility.md
+++ b/docs/announcements/en/price-filters-more-search-flexibility.md
@@ -23,7 +23,7 @@ Now you can filter prices by combining multiple Categories and Brands, as well a
 
 This update enables you to export more specific prices from filter selection.
 
-![filtro preco-EN](https://images.ctfassets.net/alneenqid6w5/6zuHx35ldRSPGIGMCw61VH/f16a50faf4cfba4d806f8d6aa7430735/filtro_preco-EN.png)
+![filtro preco-EN](//images.ctfassets.net/alneenqid6w5/6zuHx35ldRSPGIGMCw61VH/f16a50faf4cfba4d806f8d6aa7430735/filtro_preco-EN.png)
 
 ## What do I need to do?
 To use this new configuration, follow the steps below:
diff --git a/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md b/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
index d92b415e3..c4c519977 100644
--- a/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
+++ b/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
@@ -31,7 +31,7 @@ To find out if your account is still using Pricing V1, follow the steps below:
 
 If you see a screen similar to the one below, it means that your account needs to migrate.
 
-![Tela pricing antiga - EN](https://images.ctfassets.net/alneenqid6w5/7wk5rGZNxCldv1KHUEUIFz/e3c41c74ab30125e804250a432eb95c0/Tela_pricing_antiga_-_EN.png)
+![Tela pricing antiga - EN](//images.ctfassets.net/alneenqid6w5/7wk5rGZNxCldv1KHUEUIFz/e3c41c74ab30125e804250a432eb95c0/Tela_pricing_antiga_-_EN.png)
 
 If your VTEX account still uses previous versions of the VTEX Admin (such as "vtexcommercestable"), it will also need to migrate. To do so, please follow the steps below:
 
diff --git a/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md b/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
new file mode 100644
index 000000000..b3e428098
--- /dev/null
+++ b/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
@@ -0,0 +1,55 @@
+---
+title: 'Promotion Simulator: Understand the promotions applied to the cart'
+id: 2PPhczsmI0MXb5MyAlQx4R
+status: PUBLISHED
+createdAt: 2024-03-13T14:31:21.027Z
+updatedAt: 2024-03-13T19:02:02.287Z
+publishedAt: 2024-03-13T19:02:02.287Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: promotion-simulator-understand-the-promotions-applied-to-the-cart
+locale: en
+legacySlug: promotion-simulator-understand-the-promotions-applied-to-the-cart
+announcementImageID: ''
+announcementSynopsisEN: 'View and manage the promotions applied to the cart with the Promotion Simulator.'
+---
+
+
+We have launched the **Promotion Simulator** for all VTEX stores globally. It is a new tool that allows you to see the promotions applied to the cart in your store, along with their activation conditions. 
+
+Given the multiple options for configuring [promotions](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N), this feature provides a clear view of competing and accumulated promotions and conditions to activate them.
+
+We created the **Promotion Simulator** to give merchants more autonomy to manage and run promotions based on their business strategies. With the new tool, you can explore and streamline the performance of your promotions while ensuring a more efficient operation and an enhanced shopping experience for your customers.
+
+## What's new?
+
+From now on, the **Promotion Simulator** will be available for all VTEX stores via [Cartman](https://help.vtex.com/en/tutorial/configure-cartman--1ACMTStZYkMqB0lTgwg451), an auxiliary tool for merchants at checkout. The simulator allows you to:
+
+* **View the promotions** applicable or applied to each item in the cart and the condition to activate them.
+* **Manage existing promotions** through the cart.
+* **Test removing promotions** applied to the cart.
+* **Test applying** other promotions to the cart before activating them, including scheduled or inactive promotions.
+* **Understand the reasons** a promotion was not applied to the cart.
+
+![promotions simulator - en-gif 3](//downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/c54434442ee4cd19b211505896daa841/promotions_simulator_gi-3.gif)
+
+## What needs to be done?
+
+No action is required, as the **Promotion Simulator** is now available in all VTEX stores via [Cartman](https://help.vtex.com/en/tutorial/configure-cartman--1ACMTStZYkMqB0lTgwg451).
+
+Users must have a [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) authorized to access the **Promotions** module in the VTEX Admin to access the **Promotion Simulator**. 
+
+To start using the simulator, follow these instructions:
+
+1. In the top bar of the VTEX Admin, click the` Preview` button to open your store's restricted access page. 
+
+    Alternatively, you can access it directly via the URL `https://{accountname}.myvtex.com`, replacing `{accountname}` with your VTEX account name.
+
+2. Add products to the cart and proceed to checkout at `https://{accountname}.myvtex.com/checkout/#/cart`.
+3. Click the blue button <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> in the bottom right corner of the page to launch Cartman.
+4. Click **Promotion Simulator**.
+
+   In the new window, you will see the details of promotions applied and not applied to the cart.
+
+Check out the [Promotion Simulator](https://help.vtex.com/en/tutorial/promotion-simulator-beta--4zc8SNqjqeIJ0ZRMhjlnvy) guide for more details on how to use the new tool.
diff --git a/docs/announcements/en/rate-vtexs-service-in-your-admin.md b/docs/announcements/en/rate-vtexs-service-in-your-admin.md
index d892c92a8..b8c8aa60c 100644
--- a/docs/announcements/en/rate-vtexs-service-in-your-admin.md
+++ b/docs/announcements/en/rate-vtexs-service-in-your-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'We have launched a satisfaction survey page in the VTEX
 
 We have launched the new *Satisfaction Survey* page in the VTEX Admin. Now, you can rate our support service without leaving the VTEX environment.
 
-![Pesquisa de satisfação EN](https://images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/eaadd736c6ce0d1b06e9f7cf2543f643/image__17_.png)
+![Pesquisa de satisfação EN](//images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/eaadd736c6ce0d1b06e9f7cf2543f643/image__17_.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
new file mode 100644
index 000000000..ff3751aad
--- /dev/null
+++ b/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -0,0 +1,87 @@
+---
+title: 'reCAPTCHA validation will now follow orderForm configuration for all requests'
+id: 3SLXk0n8neXgWxaLaIgAC7
+status: PUBLISHED
+createdAt: 2023-07-04T21:20:42.330Z
+updatedAt: 2023-07-05T18:40:32.146Z
+publishedAt: 2023-07-05T18:40:32.146Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests
+locale: en
+legacySlug: recaptcha-validation-will-now-follow-orderform-configuration-for-all
+announcementImageID: ''
+announcementSynopsisEN: 'Merchants that use the Checkout API to place orders from mobile apps/headless storefronts must review their integrations'
+---
+
+[reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) is a security service used to determine if a given action is performed by a real user or malicious automation, protecting websites from fraud and abuse. By activating [reCAPTCHA at checkout](https://help.vtex.com/en/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP), you are following best practices against virtual attacks and reducing the risk that your store can be exploited for fraudulent purposes.
+
+To further protect our customers, VTEX will now enforce the reCAPTCHA orderForm configuration set in each account for all Checkout API requests, regardless of the roles associated with the user or application key.
+
+Merchants that use the Checkout API to place orders from mobile apps, headless storefronts and similar applications must [review](#review-your-integrations) and [adjust](#adjust-your-integrations) their integrations before __September 1, 2023__.
+
+## What is changing?
+
+Before, reCAPTCHA verification was not required for orders placed by users and application keys with the `Shopping Cart Full Access` [resource in License Manager](https://help.vtex.com/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3). This includes [predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy) such as `Owner (Admin Super)` and `User Admin - RESTRICTED`, as well as the [Sponsor user](https://help.vtex.com/en/tutorial/what-is-the-sponsor-user--3oPr7YuIkEYqUGmEqIMSEy).
+
+Now, reCAPTCHA verification will follow orderForm configuration set in each account for all Checkout API requests, regardless of the roles associated with the user or application key.
+
+## Why are we making this change?
+
+This action was necessary to reduce the chances of fraud and abuse, such as card testing, in our stores. While the best practices for using application keys indicate that stores should create individual keys for each integration and apply restrictive roles to them, some merchants were exposing themselves to risk by using application keys with administrative roles. 
+
+Because we understand that there may be a legitimate reason for some integrations to have access to more resources and information, our decision was to require merchants to implement reCAPTCHA in those integrations. If that is not possible, they have the alternative of disabling the reCAPTCHA validation in their account (`recaptchaValidation="never"`) and implementing alternative protective measures against automated attacks on their own.
+
+We know that these changes will have an impact on our customers’ operations, but adopting security best practices is always necessary and beneficial for our entire ecosystem.
+
+## What needs to be done?
+
+### Review your integrations
+
+Ask your development team to review your integrations that use the Checkout API to place orders to your VTEX store, using the following endpoints:
+
+- [Place order from an existing cart](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pub/orderForm/-orderFormId-/transaction)
+- [Place order](https://developers.vtex.com/docs/api-reference/checkout-api#put-/api/checkout/pub/orders)
+
+They should be able to follow the diagram below to assess whether an integration needs to be adjusted, according to your store's [reCAPTCHA orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) and how requests made to these endpoints are [authenticated](https://developers.vtex.com/docs/guides/authentication-overview):
+
+![reCAPTCHA diagram](//images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/077e3f3122263a78aaa5a4cf47bd9eb2/recaptcha-config-EN.png)
+
+- __Case 1__: *No changes are required in the integration, but your store might be at risk.*
+
+  Your store does not use reCAPTCHA at Checkout and is therefore vulnerable to automated attacks, unless other protective measures are implemented in your integration.
+
+- __Case 2__: *You need to adjust your integration, otherwise it might stop working.*
+
+  Your store uses reCAPTCHA at Checkout, but is not ready to display it correctly in the user interface. Your development team should [adjust your integrations](#adjust-your-integrations).
+
+- __Case 3__: *No changes are required in the integration.*
+
+  Your store uses reCAPTCHA at Checkout and is ready to display it correctly in the user interface. Congratulations for following best practices in security!
+
+### Adjust your integrations
+
+If your development team identified that your integration requires attention, they must follow the instructions provided in the developer guide [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations).
+
+<div class="alert alert-warning">
+If you are implementing reCAPTCHA on a native mobile app, use reCAPTCHA v3. Otherwise, reCAPTCHA use v2.
+</div>
+
+Using the reCAPTCHA key returned by the Checkout, the reCAPTCHA widget should be rendered in the user interface of your mobile app/headless storefront (or similar) as described in the [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) or [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3) documentation provided by Google.
+
+After the shopper has completed the reCAPTCHA challenge, their response (`recaptchaToken`) should be sent to the Checkout API to complete the purchase, as described in the *Final validation* section of [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#final-validation). Checkout API will then [verify the user's response](https://developers.google.com/recaptcha/docs/verify) using the provided token.
+
+<div class="alert alert-danger">
+All integrations using Checkout API to place orders must be reviewed and adjusted before September 1, 2023. Applications that fail to render the reCAPTCHA widget and verify the user's response will not be able to place orders after this date.
+</div>
+
+## Learn more
+
+Check out the following documentation to learn more about reCAPTCHA and best practices to ensure your store is protected:
+
+- [Using reCAPTCHA at Checkout](https://help.vtex.com/en/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP)
+- [Best practices against virtual attacks](https://help.vtex.com/en/tutorial/best-practices-against-virtual-attacks--191rpbF7UgrKapVCi1PCDE)
+- [Best practices for using application keys](https://help.vtex.com/en/tutorial/best-practices-application-keys--7b6nD1VMHa49aI5brlOvJm)
+- [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3)
+
diff --git a/docs/announcements/en/redesigned-products-and-skus-page.md b/docs/announcements/en/redesigned-products-and-skus-page.md
index a7314264a..7536b158d 100644
--- a/docs/announcements/en/redesigned-products-and-skus-page.md
+++ b/docs/announcements/en/redesigned-products-and-skus-page.md
@@ -28,7 +28,7 @@ The new **Products & SKUs** interface allows you to:
 * Track product and SKU status in a more straightforward and visual way, with icons and SKU status in the list.
 * Easily identify products and SKUs with pending information waiting to be available for sale through the new **Pending** status.
 
-![catalog-products-skus-en](https://images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/8efc01107b80405151eb83c94061f2cb/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_23_24_1.png)
+![catalog-products-skus-en](//images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/8efc01107b80405151eb83c94061f2cb/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_23_24_1.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
index 387009c69..a1e87e3e1 100644
--- a/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
@@ -1,10 +1,10 @@
 ---
 title: 'Requests with pagination will change in the search API'
 id: 3UZR4qoAisiqE6kmuuYEAc
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-01-24T14:11:26.225Z
-updatedAt: 2020-11-27T19:40:17.179Z
-publishedAt: 2020-05-11T18:53:36.826Z
+updatedAt: 2023-12-15T13:03:53.872Z
+publishedAt: 2023-12-15T13:03:53.872Z
 contentType: updates
 productTeam: Identity
 author: authors_24
@@ -32,4 +32,4 @@ This change has already been implemented in the API, but until the due date, bot
 - There's also a limit of 2500 items for any given search. Because of that, it's not possible to have a value over 2500 at the <b>_to</b> parameter.<br>
 </div>
 
-To know more about how pagination requests work in the search API, take a look at this [document](https://developers.vtex.com/reference/search-api-overview).
+To know more about how pagination requests work in the search API, take a look at this [document](https://developers.vtex.com/docs/api-reference/search-api).
diff --git a/docs/announcements/en/sales-performance-dashboard-updates.md b/docs/announcements/en/sales-performance-dashboard-updates.md
index 0175b4098..dae05ee98 100644
--- a/docs/announcements/en/sales-performance-dashboard-updates.md
+++ b/docs/announcements/en/sales-performance-dashboard-updates.md
@@ -19,7 +19,7 @@ The Sales Performance dashboard allows store operators to analyze data from all
 
 We have improved the experience on this page based on your suggestions, adding new features for applying filters, customizing views, and exploring data. 
 
-![Sales perf update EN](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
+![Sales perf update EN](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
 
 ## What has changed?
 We have enhanced existing features, such as Filters and Data, and added the Views menu. The new filter experience allows you to try different filter combinations with fewer clicks. The new Views feature has been designed to save the filters and metrics applied on the page, allowing you to access the same view combination quickly. 
diff --git a/docs/announcements/en/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md b/docs/announcements/en/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
index 402411ae0..935008147 100644
--- a/docs/announcements/en/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
+++ b/docs/announcements/en/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
@@ -3,8 +3,8 @@ title: 'Samsung Pay: more flexible payments thanks to the new digital wallet'
 id: 2hPbwpiBjuUDh5exB2t5I9
 status: PUBLISHED
 createdAt: 2020-08-26T13:58:55.512Z
-updatedAt: 2020-08-26T16:42:36.874Z
-publishedAt: 2020-08-26T16:42:36.874Z
+updatedAt: 2023-09-26T15:25:06.834Z
+publishedAt: 2023-09-26T15:25:06.834Z
 contentType: updates
 productTeam: Financial
 author: 7qy2DBsUp8U5P9lqV0JHfR
@@ -15,18 +15,18 @@ announcementImageID: ''
 announcementSynopsisEN: "As of August, VTEX offers Samsung Pay, Samsung's digital wallet, as a payment method within SmartCheckout."
 ---
 
-VTEX always aims to provide the best shopping experience for your customers and now provides you with [Samsung Pay](https://www.samsung.com/us/samsung-pay/ "Samsung Pay") - the Samsung [e-wallet](https://help.vtex.com/en/tutorial/o-que-e-uma-carteira-digital-e-wallet?locale=es "e-wallet") - as a payment method in your e-commerce.
- 
+VTEX always aims to provide the best shopping experience for your customers and now provides you with [Samsung Pay](https://www.samsung.com/us/samsung-pay/ "Samsung Pay") - the Samsung [ewallet](https://help.vtex.com/en/tutorial/o-que-e-uma-carteira-digital-e-wallet?locale=es "e-wallet") - as a payment method in your e-commerce.
+
 ## Advantages
 Offering digital wallets as a payment method within SmartCheckout expands the range of means of payment for your e-commerce.
- 
+
 This strategy allows your store to cover different buyer profiles. The more payment options, the bigger the chances that your customers will choose one and complete the purchase.
- 
+
 In addition, including Samsung Pay as a payment option empowers a niche of customers who only pay online using digital wallets.
- 
+
 ## How it works
 Only Samsung Pay users will be able to make purchases using this payment method, meaning end users who have already installed and configured Samsung Pay on their mobile device.
- 
+
 By accessing SmartCheckout and selecting Samsung Pay as payment method, customers simply need to authorize the purchase via biometric identification or app password.
 
 For more details, check out the article on [how to configure Samsung Pay as a payment method in your store](https://help.vtex.com/en/tutorial/configurar-samsung-pay-como-meio-de-pagamento--5Yj9rgzOCVYuGmAumQlfpP "how to configure Samsung Pay as a payment method in your store").
diff --git a/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md b/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md
index 4c3628568..57fae259a 100644
--- a/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md
+++ b/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md
@@ -23,7 +23,7 @@ Previously, after customers entered their information at checkout or after their
 
 From now on, two checkboxes will be available on the Checkout screen, allowing users to indicate if they want their personal and payment information to be stored and used for future purchases. This will reduce your customers' shopping time. 
 
-![ Save user data opt-in EN](https://images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/465f60548b25abfde675c3e81cbbcebe/Save_user_data_-_EN.PNG)
+![ Save user data opt-in EN](//images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/465f60548b25abfde675c3e81cbbcebe/Save_user_data_-_EN.PNG)
 
 Learn more in [SmartCheckout - Customer information automatic fill-in](https://help.vtex.com/en/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan#).
 
diff --git a/docs/announcements/en/schedule-content-publication-with-site-editor.md b/docs/announcements/en/schedule-content-publication-with-site-editor.md
index bd7a431bd..aa03ae83c 100644
--- a/docs/announcements/en/schedule-content-publication-with-site-editor.md
+++ b/docs/announcements/en/schedule-content-publication-with-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Create and schedule predefined block versions in Site E
 
 The Site Editor feature **Configurations** was updated. It is now called **Versions** and allows you to create deactivated versions of your store’s content and activate them whenever you want.
 
-![activating-versions-en](https://images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/d3402adb77ed7eaada1fb51b8ac736ab/activating-versions-en.gif)
+![activating-versions-en](//images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/d3402adb77ed7eaada1fb51b8ac736ab/activating-versions-en.gif)
 
 ## What has changed?
 Previously, the **Versions** feature was called **Configurations**, and it only allowed users to create a new activated version, such as a Carousel with promotional products or schedule to activate it. After inactivating a version, it was also not possible to activate it again.
diff --git a/docs/announcements/en/search-filters-in-instores-endless-aisle.md b/docs/announcements/en/search-filters-in-instores-endless-aisle.md
index 72c27ce22..ce5e58d3d 100644
--- a/docs/announcements/en/search-filters-in-instores-endless-aisle.md
+++ b/docs/announcements/en/search-filters-in-instores-endless-aisle.md
@@ -26,7 +26,7 @@ Previously, VTEX Intelligent Search filters were not available in inStore, only
 
 With the new feature, when searching for a term, sales associates can filter results by price range, department, and brand, for example, among other configurable filters in VTEX Intelligent Search. This allows them to quickly find the desired product.
 
-![instore-filtros-en](https://images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b253d8baf245473167c7ad606283b315/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_05_18.png)
+![instore-filtros-en](//images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b253d8baf245473167c7ad606283b315/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_05_18.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
new file mode 100644
index 000000000..814545388
--- /dev/null
+++ b/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -0,0 +1,50 @@
+---
+title: 'Now you can search for orders in the VTEX Admin global search bar'
+id: 4ycVQJ5hRkxVy8r2iQamCb
+status: PUBLISHED
+createdAt: 2023-10-17T12:05:18.467Z
+updatedAt: 2023-10-17T21:04:22.374Z
+publishedAt: 2023-10-17T21:04:22.374Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: search-for-orders-in-the-vtex-admin-global-search-bar
+locale: en
+legacySlug: la-barra-de-busqueda-global-del-admin-vtex-ahora-permite-buscar-pedidos
+announcementImageID: ''
+announcementSynopsisEN: 'The global search bar in the VTEX Admin now allows you to search for store orders.'
+---
+
+We've improved the global search bar at the top of the VTEX Admin pages. Now, not only you can search the Admin pages but also store orders.
+
+Starting today, October 17, this improvement will be available globally for all VTEX stores through an automatic update.
+
+## What has changed?
+
+Previously, the global search bar allowed you to search only the VTEX Admin pages. Now, you can also search your store orders by using any of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
+
+To do this, click the search bar, select the `Orders` option, and search for what you want. Each search can return up to 10 results, as shown in the image below:
+
+![order_global_search_EN](//images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/cbf95c626a1dcc5a75382fc8db06a863/order_global_search_EN.gif)
+
+By clicking a result, you will be redirected to the [Order Details page](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). The last 10 orders you searched for will be recorded in your recent search history, making access more convenient. The search record is stored at the [user](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) level and not shared among users.
+
+<div class = "alert alert-info">
+To access orders via the VTEX Admin global search, the user <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> must be associated with the <b>View Order</b> resource (OMSViewer key) of the Order Management System (OMS).
+</div>
+
+## Why did we make this change?
+
+Using the global search bar to access orders makes it easier to manage order-related operations, increasing efficiency.
+
+Now, regardless of the VTEX Admin page you are on, you can access the global search bar and find orders without going to the **Orders** module.
+
+## What needs to be done?
+
+Starting today, October 17, all VTEX stores will be automatically updated with the improvement. No action is required from you.
+
diff --git a/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md b/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
index b9c2ee357..72b1ade5d 100644
--- a/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
+++ b/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
@@ -19,7 +19,7 @@ __Black Friday__ is coming. And with it comes the need to use this unique opport
 
 To help you with this task, VTEX is launching an __exclusive app in partnership with Google__, which will be available in our [App Store](https://apps.vtex.com/vtex-google-shopping/p).
 
-![Google Shopping App](https://images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
+![Google Shopping App](//images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
 
 It integrates your business with Google Ads and allows you to advertise your products on Google Shopping, using the new Smart Shopping Campaigns, and track the results easily and quickly.
 
diff --git a/docs/announcements/en/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md b/docs/announcements/en/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
index 65fa7b854..06328ca23 100644
--- a/docs/announcements/en/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
+++ b/docs/announcements/en/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
@@ -25,7 +25,7 @@ Configuration before the update:
   <tr>
     <td>
       <img
-           src="https:https://images.ctfassets.net/alneenqid6w5/2vhukfvaRA6F6aoa1zA0jj/fbffb2976972972a7c86b259f8a7d033/seller-promo-EN.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
+           src="https://images.ctfassets.net/alneenqid6w5/2vhukfvaRA6F6aoa1zA0jj/fbffb2976972972a7c86b259f8a7d033/seller-promo-EN.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
     </td>
   </tr>
   <tr>
@@ -43,7 +43,7 @@ Configuration after the update:
   <tr>
     <td>
       <img
-           src="https:https://images.ctfassets.net/alneenqid6w5/233U9aja4gDKtrBge4c0tl/d114d8774fa855551fd16b7d32c5be21/seller-promo-EN2.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
+           src="https://images.ctfassets.net/alneenqid6w5/233U9aja4gDKtrBge4c0tl/d114d8774fa855551fd16b7d32c5be21/seller-promo-EN2.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
     </td>
   </tr>
   <tr>
diff --git a/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md b/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
new file mode 100644
index 000000000..b47f40f37
--- /dev/null
+++ b/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
@@ -0,0 +1,30 @@
+---
+title: 'Shopping Season: Get your store ready with our Best Practices Guide'
+id: 4c0wnRmblHPKfCKkkiOkhX
+status: PUBLISHED
+createdAt: 2023-10-03T13:08:30.221Z
+updatedAt: 2023-11-17T19:45:14.488Z
+publishedAt: 2023-11-17T19:45:14.488Z
+contentType: updates
+productTeam: Others
+author: 1u80f14cWqneWquMc8tUq1
+slug: shopping-season-get-your-store-ready-with-our-best-practices-guide-2023
+locale: en
+legacySlug: 
+announcementImageID: ''
+announcementSynopsisEN: "Follow our recommendations and exclusive tips to make the most out of this year's Black Friday."
+---
+
+__Black Friday__ is coming. Despite its official date (__November 24__), many stores will start their campaigns a lot earlier. To make sure you'll make the most out of one of the main events on the retail calendar, start prepping soon.
+
+As in previous years, we came up with a guide with recommendations and exclusive tips that will help you ensure your store's health and sales. 
+
+The guide is available to all our clients and partners and may be accessed through the homepage of your Admin or directly through the URL 
+
+```
+https://{accountName}.myvtex.com/admin/shopping-season
+```
+
+Simply replace `{accountName}` with your store's Account Name, as in the image below.
+
+![Shopping Season Guidelines - 2023 - EN](//images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/0dbbce1dd40337f020fbcd57833af2fc/Shopping_Season_Guidelines_-_2023_-_EN.png)
diff --git a/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md b/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md
new file mode 100644
index 000000000..089b225ba
--- /dev/null
+++ b/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md
@@ -0,0 +1,35 @@
+---
+title: 'Site Editor and Media: new authorization requirement'
+id: 7tO32uRxIUK8lOp8AvWs2L
+status: PUBLISHED
+createdAt: 2024-02-26T12:35:10.352Z
+updatedAt: 2024-02-26T18:06:13.754Z
+publishedAt: 2024-02-26T18:06:13.754Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: site-editor-and-media-new-authorization-requirement
+locale: en
+legacySlug: site-editor-and-media-new-authorization-requirement
+announcementImageID: ''
+announcementSynopsisEN: 'Users now require CMS GraphQL API resource for content management. Update user roles accordingly.'
+---
+
+As of Monday, March 18th, 2024, all [users](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) and [application keys](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) that need access to [Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) and [Media](https://help.vtex.com/en/tutorial/media-overview--31fhjHTt4TBoo50AmGQ9b2) will be required to have the `CMS GraphQL API` License Manager [resource](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) added to their [user roles](https://help.vtex.com/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) for content management. 
+
+## What has changed?
+
+As [previously announced for Headless CMS users](https://help.vtex.com/announcements/headless-cms-new-authorization-requirement--7G056zzZmGFBztkRqhpUgj), users and application keys must have the `CMS GraphQL API` resource associated with their role to manage content.  
+
+Now, we are extending this requirement to Site Editor and Media, which means the `CMS GraphQL API` resource is necessary to manage content using these tools.
+
+## Why did we make this change?
+This change aims to enhance security and simplify user access to the Site Editor and Media. This means users have a more controlled and secure environment when managing store content. 
+
+## What needs to be done?
+Ensure that users are associated with the `CMS GraphQL API` resource within their user roles by either [creating a new role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) or editing an existing one.
+
+<div class="alert alert-warning">
+  <p>To manage users and their roles, you need the <code>Save access profile</code> resource from the <bold>License Manager</bold> product associated with your user role. For example, the <a href=”https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted”> User Administrator - RESTRICTED</a> is a predefined role that has the <code>Save access profile</code> resource associated with it.</p>
+</div>
+
diff --git a/docs/announcements/en/site-editor-fixed-content-loss-issue.md b/docs/announcements/en/site-editor-fixed-content-loss-issue.md
new file mode 100644
index 000000000..4ad1445cc
--- /dev/null
+++ b/docs/announcements/en/site-editor-fixed-content-loss-issue.md
@@ -0,0 +1,28 @@
+---
+title: 'Site Editor: Fixed content loss issue'
+id: 1mnrlSMyMmU1iAUyEquVYB
+status: PUBLISHED
+createdAt: 2024-06-13T12:25:13.359Z
+updatedAt: 2024-06-13T13:29:05.308Z
+publishedAt: 2024-06-13T13:29:05.308Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: site-editor-fixed-content-loss-issue
+locale: en
+legacySlug: site-editor-fixed-content-loss-issue
+announcementImageID: ''
+announcementSynopsisEN: 'Site Editor content storage received an upgrade for better performance and reliability.'
+---
+
+On June 12, [Site Editor](https://help.vtex.com/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) content storage was updated for all accounts that use it in order to address a known issue: [Intermittent Site Editor content loss](https://help.vtex.com/en/known-issues/intermitent-site-editor-content-loss--3a5MlAoD2Z7Gu6HDS8wihD). This upgrade improves storage performance, reliability, and reduces the size of your stored content.
+## What has changed?
+Previously, frequent content changes in Site Editor could cause the `content.json` file to become excessively large, leading to content loss when [promoting a production workspace to master](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspaces-best-practices#deployment-and-workspace-promotion) or installing a new theme version in a test workspace.
+
+We have now improved the storage architecture and file partitioning solution for Site Editor. The improvement solution stores content in smaller, template-specific files, instead of a single large file. This change reduces file size by approximately 90%, reducing storage needs per page, and enhancing overall performance and content delivery.
+
+## What needs to be done?
+No action is needed. The upgrade was automatically implemented in all VTEX stores using Site Editor.
+
+If you continue to experience content loss after June 12, open a ticket with [VTEX Support](https://help.vtex.com/support).
+
diff --git a/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md b/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md
index 204ac6d8f..59cd9337d 100644
--- a/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md
+++ b/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md
@@ -27,7 +27,7 @@ Previously, the Social Selling feature in inStore consisted of generating a link
 
 With the change, inStore now also generates a QR code that can be scanned by customers' devices, in addition to the shareable link.
 
-![instore-social-selling-qr-code-share-en](https://images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/f3ec6fdf7a587799dcf51ebdf30cf6f7/image2.png)
+![instore-social-selling-qr-code-share-en](//images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/f3ec6fdf7a587799dcf51ebdf30cf6f7/image2.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/social-selling-share-your-instore-cart.md b/docs/announcements/en/social-selling-share-your-instore-cart.md
index 5a57bd1e7..6037a2ff2 100644
--- a/docs/announcements/en/social-selling-share-your-instore-cart.md
+++ b/docs/announcements/en/social-selling-share-your-instore-cart.md
@@ -27,7 +27,7 @@ Previously, cart sharing wasn’t possible on inStore, [only through ecommerce](
 
 With inStore Social Selling, your physical store sales reps can select products and generate a link to share the **Cart Suggestion** with one or more customers via WhatsApp, as shown below. It is also possible to copy the link and share it on other social media.
 
-![socialselling-EN2](https://images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/e1fd62dd05b2468ba4cb198572a5bce8/socialselling-EN2.gif)
+![socialselling-EN2](//images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/e1fd62dd05b2468ba4cb198572a5bce8/socialselling-EN2.gif)
 
 The sales rep can share the same link with several customers, as many times as they want. Every time someone opens this link, a new shopping cart is generated, exactly like the one created on inStore. Each cart accessed is also linked to the sales rep account and their code, if any.
 
@@ -35,7 +35,7 @@ The customers can access the cart, make the payment, and complete the purchase o
 
 The sales rep can also fill in the customer's delivery information, choose the payment method, and then share a **Payment Link**. That way, the shared cart link will have all the personal information already filled in, so the customer will only need to fill in the payment information to complete the purchase on their own device.  Check out how it works.
 
-![paymentlink EN](https://images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/b20493f0a9350f2ae8574441fc6bbc9f/paymentlink_EN.gif)
+![paymentlink EN](//images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/b20493f0a9350f2ae8574441fc6bbc9f/paymentlink_EN.gif)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/the-insights-dashboard-will-be-discontinued.md b/docs/announcements/en/the-insights-dashboard-will-be-discontinued.md
new file mode 100644
index 000000000..6972741dd
--- /dev/null
+++ b/docs/announcements/en/the-insights-dashboard-will-be-discontinued.md
@@ -0,0 +1,39 @@
+---
+title: 'The Insights dashboard will be discontinued'
+id: 4yJtAquGwufjHFTcGwnTwr
+status: PUBLISHED
+createdAt: 2023-10-03T23:02:27.048Z
+updatedAt: 2023-10-04T15:06:15.480Z
+publishedAt: 2023-10-04T15:06:15.480Z
+contentType: updates
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: the-insights-dashboard-will-be-discontinued
+locale: en
+legacySlug: the-insights-dashboard-will-be-discontinued
+announcementImageID: ''
+announcementSynopsisEN: 'As of October 15, 2023, it will no longer be possible to access the Insights dashboard, which will be discontinued.'
+---
+
+**Insights** is a dashboard that allows you to monitor your sales with a detailed view of the conversion funnel and the main metrics that impact your store's revenue.
+
+Currently, the [Insights dashboard](https://help.vtex.com/en/tutorial/acompanhando-a-evolucao-das-suas-vendas--5QtyTR0jFy9gDnr4EYCjdq) is only available at:
+```
+https://{accountname}.myvtex.com/admin/insights
+```
+
+As of October 15, 2023, it will no longer be possible to access the [Insights dashboard](https://help.vtex.com/en/tutorial/acompanhando-a-evolucao-das-suas-vendas--5QtyTR0jFy9gDnr4EYCjdq), which will be discontinued.
+
+## Why we are making this change?
+
+The information available in the **Insights** dashboard can also be found in other dashboards, such as:
+- [Store Overview](https://help.vtex.com/en/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ)
+- [Store Overview (beta)](https://help.vtex.com/en/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46)
+
+Therefore, this discontinuation aims to reduce redundancy on the platform so that, in the future, we can focus on maintaining and improving a single experience. Currently, the **Store Overview** dashboards already display the same information as the **Insights** dashboard but with more accurate data and improved visualization.
+
+## What needs to be done?
+
+As of October 15, 2023, this change will be automatically applied to all VTEX stores, and no action is required from you.
+
+If you want to monitor your store sales metrics, please go to the [Store Overview](https://help.vtex.com/en/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ) or [Store Overview](https://help.vtex.com/en/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) (beta) dashboards, which have the same information as the **Insights** dashboard but with more accurate data and improved visualization.
diff --git a/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md b/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md
index d061a8f15..8ace5107c 100644
--- a/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md
+++ b/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md
@@ -34,7 +34,7 @@ This change's review and subsequent adjustment should be implemented following t
 
 Required steps for review and adjustment:
 
-1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Customization__: if the "/account/orders" page is affected by any front-end customization, it should be migrated and adapted to the new URL: "/account#/orders". Review and perform all necessary tests to ensure that all custom resources are functioning properly.  
 3. __Site links__: Review and update all of the site's custom links, in addition to the ones pertaining to transactional emails that would previously direct users to "/account/orders". These links should now direct users to "/account#/orders".
 
diff --git a/docs/announcements/en/the-offer-management-module-will-be-discontinued.md b/docs/announcements/en/the-offer-management-module-will-be-discontinued.md
new file mode 100644
index 000000000..635b3bfc2
--- /dev/null
+++ b/docs/announcements/en/the-offer-management-module-will-be-discontinued.md
@@ -0,0 +1,35 @@
+---
+title: 'The Offer Management module will be discontinued'
+id: 1kQw84J88i1ziNlXX5XA5S
+status: PUBLISHED
+createdAt: 2023-10-05T12:50:25.536Z
+updatedAt: 2023-10-05T13:51:31.119Z
+publishedAt: 2023-10-05T13:51:31.119Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: the-offer-management-module-will-be-discontinued
+locale: en
+legacySlug: the-offer-management-module-will-be-discontinued
+announcementImageID: ''
+announcementSynopsisEN: 'The Offer management module will be available only for integration with Mercado Livre.'
+---
+
+Aiming to offer the best experience to our clients, we announce the deprecation of the VTEX Admin Offer Management module.
+ 
+The offers sent to the marketplaces will not be affected, and you can still view the status of each one in the VTEX Admin under **Marketplace > Connections > Products.**
+ 
+## What has changed?
+
+We have removed the option of monitoring the status and synchronization of offers sent to a marketplace from the Offers Management module.  
+The [Moderation](https://help.vtex.com/pt/tutorial/gerenciamento-de-anuncios-moderacao-e-qualidade-dos-anuncios-do-mercado--xSbPzA41jiWPAorlBCEA4?&utm_source=autocomplete#moderacao), [Offer Quality](https://help.vtex.com/pt/tutorial/gerenciamento-de-anuncios-moderacao-e-qualidade-dos-anuncios-do-mercado--xSbPzA41jiWPAorlBCEA4?&utm_source=autocomplete#qualidade), and [MeLi Catalog Opportunities](https://help.vtex.com/pt/tutorial/anuncios-enviados-oportunidades-de-buybox--1hO9eI1th47EGxQoTzGewC) features will remain available until December 15, 2023, only for offers linked to the [Mercado Libre integration](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/51oWBHvVxSs8eAwLQhSbSd) through **Marketplace > Mercado Libre > Offer Management.**  
+ 
+## What needs to be done?
+
+This update is automatic, so no action is required from you. As of the date indicated above, the module will be completely discontinued from the VTEX Admin.  
+
+<div class="alert alert-info">
+We will soon have a replacement module for Offer Management. Follow the updates through the <a href="https://developers.vtex.com/updates/release-notes">Release Notes page on the Developer Portal</a> and the <a href="https://help.vtex.com/en/announcements">News page in the VTEX Help Center</a>.
+</div>
+
+
diff --git a/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md b/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
index 2c25c5918..2e8c1db59 100644
--- a/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
+++ b/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
@@ -19,7 +19,7 @@ announcementSynopsisEN: 'The term "Access Profile" has been replaced by "Role" t
 
 What was called “Access Profile” in the Account Management module will now be called “Role”. This change applies only to the English interface. The Admin and all documentation have been updated with the new term. No functionality has been affected. Here’s an example of how the term appears on the Roles dashboard in the Admin:
 
-![Roles Panel](https://images.ctfassets.net/alneenqid6w5/3onlQoxSxoBtgwPGtGUUdH/bd0130c89de14555d1bf9dd465c420be/Roles_Panel.png)
+![Roles Panel](//images.ctfassets.net/alneenqid6w5/3onlQoxSxoBtgwPGtGUUdH/bd0130c89de14555d1bf9dd465c420be/Roles_Panel.png)
 
 All documents that mentioned this concept, both on our Developer Portal and Help Center, have been changed to include the new term.
 
diff --git a/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md b/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md
index 593a62f64..51a67155a 100644
--- a/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md
+++ b/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md
@@ -18,7 +18,7 @@ announcementSynopsisEN: 'Launch of the new auditing tool'
 
 Ensuring your store is always in compliance with security and transparency best practices, VTEX has launched a new audit feature, **Audit**. 
 
-![Screenshot for Audit UI for announcement](https://images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/1cae72785358e9622b3bbf0c481bd998/Audit_EN.png)
+![Screenshot for Audit UI for announcement](//images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/1cae72785358e9622b3bbf0c481bd998/Audit_EN.png)
 
 From now on, users with the admin role can check operations performed in their store in a simple and fast way. You can create multiple search filters to make it easier to search for events and increase the speed of auditing processes.
 
diff --git a/docs/announcements/en/troubleshooting-guides-your-new-vtex-self-service-experience.md b/docs/announcements/en/troubleshooting-guides-your-new-vtex-self-service-experience.md
new file mode 100644
index 000000000..6797167c6
--- /dev/null
+++ b/docs/announcements/en/troubleshooting-guides-your-new-vtex-self-service-experience.md
@@ -0,0 +1,53 @@
+---
+title: 'Troubleshooting guides: Your new VTEX self-service experience'
+id: 5oDp5raqBpRta660NERceY
+status: PUBLISHED
+createdAt: 2024-07-08T15:04:53.687Z
+updatedAt: 2024-07-08T21:47:04.455Z
+publishedAt: 2024-07-08T21:47:04.455Z
+contentType: updates
+productTeam: Others
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: troubleshooting-guides-your-new-vtex-self-service-experience
+locale: en
+legacySlug: troubleshooting-guides-your-new-vtex-self-service-experience
+announcementImageID: ''
+announcementSynopsisEN: 'Solve problems faster and autonomously with our redesigned troubleshooting guides.'
+---
+
+VTEX is constantly evolving to enhance the customer support experience and empower our clients to solve problems more efficiently and autonomously.
+To facilitate access to support, now you can use the Troubleshooting guides available in the [Help Center](https://help.vtex.com/subcategory/store-operations--2Q0IQjRcOqSgJTh6wRHVMB) and [Developer Portal](https://developers.vtex.com/docs/troubleshooting). These guides detail potential error scenarios in store operations and during store or app development, as well as provide instructions on how to proceed to restore expected performance for your store.
+
+<div class="alert alert-info" role="alert"> 
+  Would you like to contribute to this initiative? Complete this <a href="https://forms.gle/PdVNZmMDMjiDfJaf8">Feedback form</a>.
+</div>
+
+## How are the Troubleshooting guides organized?
+The Troubleshooting guides are available in the [Help Center](https://help.vtex.com/subcategory/store-operations--2Q0IQjRcOqSgJTh6wRHVMB) and [Developer Portal](https://developers.vtex.com/docs/troubleshooting), organized into categories as follows:
+
+- [Help Center](https://help.vtex.com/category/troubleshooting--39pDkp8qxSll6mGj0tWViz):
+  - [Store operations](https://help.vtex.com/subcategory/store-operations--2Q0IQjRcOqSgJTh6wRHVMB): This section focuses on solving the difficulties with platform and ecommerce operations.
+
+- [Developer Portal](https://developers.vtex.com/docs/troubleshooting)
+  - **Development**: This section is designed to address errors related to storefront and app development.
+  - **Store performance**: This section includes procedures for debugging errors and restoring the store to operational condition if it is down or malfunctioning.
+
+<div class="alert alert-info" role="alert"> 
+  At the time of this announcement's publication, 15 guides are available for consultation, with more in production.
+</div>
+
+## Why did we create this initiative?
+Our goal is to simplify and streamline the VTEX support experience. With the new Troubleshooting guides, you can:
+
+- **Identify problems more quickly:** The descriptions of store operation and development scenarios will help you identify the problems you may be experiencing.
+- **Find solutions for each case presented:** The guides contain procedures that explain the necessary steps to resolve errors.
+- **Gain greater autonomy in fault management:** You will be able to resolve errors internally, at any time, without the need to contact technical support.
+
+## How can you help us?
+We are committed to continually expanding and improving this initiative, analyzing new problem scenarios and regularly publishing more Troubleshooting guides. Your feedback is crucial to ensuring we are on the right track!
+
+Here’s how you can contribute:
+
+- **Share your feedback:** Complete our [Feedback form](https://forms.gle/PdVNZmMDMjiDfJaf8) with your suggestions or criticisms about the new Troubleshooting guides.
+- **Let's talk:** If you’d like to discuss your experience with our documentation in more detail or suggest specific improvements to the Help Center and Developer Portal, please complete the [Feedback form](https://forms.gle/PdVNZmMDMjiDfJaf8). We will contact you within 5 working days to schedule a chat with our Education team.
+
diff --git a/docs/announcements/en/update-grants-in-the-promotions-module.md b/docs/announcements/en/update-grants-in-the-promotions-module.md
index 734ea12bb..eb6a2618c 100644
--- a/docs/announcements/en/update-grants-in-the-promotions-module.md
+++ b/docs/announcements/en/update-grants-in-the-promotions-module.md
@@ -37,4 +37,4 @@ This update gives you more power over your promotions' behavior. The new buttons
 6. Tick the box next to **Use recurrence settings**
 7. Set the desired days and schedule for that promotion 
 
-![CRON 2 EN](https://images.ctfassets.net/alneenqid6w5/48EFCYtz5TvqhZVXmBasyW/d37188c1a6a742e3a086fe6984eded31/CRON_2_EN.png)
+![CRON 2 EN](//images.ctfassets.net/alneenqid6w5/48EFCYtz5TvqhZVXmBasyW/d37188c1a6a742e3a086fe6984eded31/CRON_2_EN.png)
diff --git a/docs/announcements/en/update-of-the-external-privacy-notice.md b/docs/announcements/en/update-of-the-external-privacy-notice.md
new file mode 100644
index 000000000..2aae27abf
--- /dev/null
+++ b/docs/announcements/en/update-of-the-external-privacy-notice.md
@@ -0,0 +1,39 @@
+---
+title: 'Update of the External Privacy Notice'
+id: fpUnEC85ixK1vNzXQSrTY
+status: PUBLISHED
+createdAt: 2024-07-02T23:52:09.837Z
+updatedAt: 2024-07-03T14:07:13.062Z
+publishedAt: 2024-07-03T14:07:13.062Z
+contentType: updates
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: update-of-the-external-privacy-notice
+locale: en
+legacySlug: update-of-the-external-privacy-notice
+announcementImageID: ''
+announcementSynopsisEN: "We have updated the Privacy Notice regarding the processing of Shoppers' personal data on VTEX."
+---
+
+We have revised the [Privacy Notice](https://vtex.com/us-en/privacy-and-agreements/external-notice/) that explains how VTEX processes the personal data of _Shoppers_, i.e., individuals who access ecommerce environments controlled by merchants who are direct clients of VTEX.
+
+The document includes information about the following aspects:
+
+* Personal data processed by VTEX and its purpose
+* Data retention period
+* Data subject rights
+* VTEX's personal data protection practices
+* Storage of personal data in the cloud
+* Data sharing with partners
+
+## What has changed?
+
+The new version of the Notice includes VTEX's latest privacy practices for personal data processing on the VTEX Platform, presented in a clearer, summarized way and directed at _Shoppers_.
+
+## Why did we make this change?
+
+We updated the Privacy Notice to align with legislation and our global privacy certifications, which recommend periodic updates. In addition, we have separated the privacy policies for job applicants, employees, and events into specific documents.
+
+## What needs to be done?
+
+No action is required. The document is now available in all languages on the VTEX website. For more information, you can access the new [External Privacy Notice](https://vtex.com/us-en/privacy-and-agreements/external-notice/) and the getting started guide [Data and privacy](https://help.vtex.com/en/tracks/data-and-privacy--4Lc0i0an0DgnEtB0AUwlcq).
diff --git a/docs/announcements/en/upgrade-your-store-to-google-analytics-4.md b/docs/announcements/en/upgrade-your-store-to-google-analytics-4.md
index 99ae7d9ad..152d50706 100644
--- a/docs/announcements/en/upgrade-your-store-to-google-analytics-4.md
+++ b/docs/announcements/en/upgrade-your-store-to-google-analytics-4.md
@@ -3,8 +3,8 @@ title: 'Upgrade your store to Google Analytics 4'
 id: 01mmrSck8nvXAKsypecT9V
 status: PUBLISHED
 createdAt: 2023-04-28T14:42:52.792Z
-updatedAt: 2023-05-03T17:47:48.884Z
-publishedAt: 2023-05-03T17:47:48.884Z
+updatedAt: 2023-07-17T13:38:03.472Z
+publishedAt: 2023-07-17T13:38:03.472Z
 contentType: updates
 productTeam: Shopping
 author: 1malnhMX0vPThsaJaZMYm2
@@ -17,21 +17,21 @@ announcementSynopsisEN: 'upgrade-your-store-to-google-analytics-4'
 
 As of July 1, 2023, [Google Analytics 4](https://support.google.com/analytics/answer/10089681) (GA4) will replace Universal Analytics, the previous version of Google's data analytics tool. See details about the change in [this Google article](https://support.google.com/analytics/answer/11583528). 
 
-For stores using [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) or [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), to continue tracking browsing data in your VTEX store, you will need to create a GA4 property and adjust some settings in your store.
+For stores using [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) or [VTEX IO - Store Framework](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), to continue tracking browsing data in your VTEX store, you will need to create a GA4 property and adjust some settings in your store.
 
 ## What has changed?
 Universal Analytics will stop processing events on July 1, 2023. Therefore, the only functional version of the tool will be Google Analytics 4.
 
 To ensure VTEX stores are compatible with the new version of Google Analytics, you need to create a Google Analytics 4 property and adjust your Google Tag Manager account settings, as described in [Configuring Google Analytics 4 in VTEX stores](https://help.vtex.com/en/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG).
 
-Stores using VTEX IO also need to configure [the Google Tag Manager app](https://developers.vtex.com/docs/guides/google-tag-manager) to integrate with Google Analytics 4.
+Stores using VTEX IO - Store Framework also need to configure [the Google Tag Manager app](https://developers.vtex.com/docs/guides/google-tag-manager) to integrate with Google Analytics 4.
 
 ## Why make this change?
 
-This change is necessary to ensure that VTEX stores using [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) or [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) remain compatible with Google Analytics 4, enabling them to gather relevant browsing data through the latest version of Google's analytics tool.
+This change is necessary to ensure that VTEX stores using [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) or [VTEX IO - Store Framework](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) remain compatible with Google Analytics 4, enabling them to gather relevant browsing data through the latest version of Google's analytics tool.
 
 ## What needs to be done?
 
 To make your store compatible with the new version of Google's data analytics tool, please follow the instructions in the [Configuring Google Analytics 4 in VTEX stores](https://help.vtex.com/en/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG) guide.
 
-If your store uses [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), you must enable the `Send events in GA4 format` setting in the VTEX Admin and configure the app to receive all Google Analytics 4 updates. For more information, see the [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager) guide.
+If your store uses [VTEX IO - Store Framework](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), you must enable the `Send events in GA4 format` setting in the VTEX Admin and configure the app to receive all Google Analytics 4 updates. For more information, see the [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager) guide.
diff --git a/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md b/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
index 05fcd0dd2..55184bee1 100644
--- a/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
+++ b/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
@@ -32,5 +32,5 @@ The functionality can be used whenever retailers want to opt for a fixed product
 - Under "What kind and amount of tax?", choose the Nominal tax option
 - Fill in the required fields and click on save
 
-![Nominal tax EN](https://images.ctfassets.net/alneenqid6w5/5ntJCk8NaGwYD4W4ZzTx9b/6217dcf2fd3ba137d84f78a7d3e8d129/Nominal_tax_EN.png)
+![Nominal tax EN](//images.ctfassets.net/alneenqid6w5/5ntJCk8NaGwYD4W4ZzTx9b/6217dcf2fd3ba137d84f78a7d3e8d129/Nominal_tax_EN.png)
 
diff --git a/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md b/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md
index bc5b0be5d..5986df865 100644
--- a/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md
+++ b/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md
@@ -23,7 +23,7 @@ To continue enhancing this experience, we have included additional validation in
 
 Previously, customers could select an expired card, proceed with a purchase, and then the payment would be declined. We now flag expired cards and prevent them from being chosen at checkout, in order to offer a smoother shopping experience.
 
-![EN - Expired Cards](https://images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/857a5d45b665bbde2d646f06a32d8fe2/EN_-_Expired_Cards.png)
+![EN - Expired Cards](//images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/857a5d45b665bbde2d646f06a32d8fe2/EN_-_Expired_Cards.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/vtex-insurance-discontinuity.md b/docs/announcements/en/vtex-insurance-discontinuity.md
new file mode 100644
index 000000000..bec16f24d
--- /dev/null
+++ b/docs/announcements/en/vtex-insurance-discontinuity.md
@@ -0,0 +1,31 @@
+---
+title: 'VTEX Insurance Discontinuity'
+id: 413Jet3S6F49mmlQzZ7Bev
+status: PUBLISHED
+createdAt: 2024-01-19T19:54:48.085Z
+updatedAt: 2024-01-29T21:49:24.406Z
+publishedAt: 2024-01-29T21:49:24.406Z
+contentType: updates
+productTeam: Others
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: vtex-insurance-discontinuity
+locale: en
+legacySlug: vtex-insurance-discontinuity
+announcementImageID: ''
+announcementSynopsisEN: 'VTEX Insurance has been discontinued as a VTEX product, but will continue to exist as Assurant Digital.'
+---
+
+As of December 11, 2023, VTEX Insurance was deprecated as a VTEX product, but its features will be migrated to Assurant Digital.
+
+**VTEX Insurance** was an app that allowed merchants to associate their store products with warranty offers from the partner warranty company [Assurant](https://www.assurant.com.br/). This feature allowed your store to offer custom warranties to customers, providing financial protection against faulty or defective products or services.
+
+# What has changed?
+
+There will be no contractual or commercial changes since the contract was between the customers and Assurant. The main change concerns support services, which were previously provided by both companies and will now be exclusively provided by Assurant.
+
+# What needs to be done?
+
+No action is required, as the update will be applied automatically to all VTEX stores. Any technical questions or issues related to the product should be addressed directly with [Assurant](https://www.assurant.com.br/).
+
+<div class = "alert alert-warning">VTEX will not provide technical support to customers.</div>
+
diff --git a/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md b/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
new file mode 100644
index 000000000..6a205a764
--- /dev/null
+++ b/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
@@ -0,0 +1,37 @@
+---
+title: 'VTEX Intelligent Search: New visual editor for Merchandising Rules'
+id: 63xoRkTEoqllK6KKadys51
+status: PUBLISHED
+createdAt: 2024-01-30T13:15:08.893Z
+updatedAt: 2024-01-31T17:00:02.465Z
+publishedAt: 2024-01-31T17:00:02.465Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-intelligent-search-new-visual-editor-for-merchandising-rules
+locale: en
+legacySlug: vtex-intelligent-search-new-visual-editor-for-merchandising-rules
+announcementImageID: ''
+announcementSynopsisEN: 'Explore the visual editor for Merchandising Rules in VTEX Intelligent Search.'
+---
+
+[Merchandising Rules](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) is a feature that handles search results in stores using [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). This feature allows you to display products that are more relevant to the customer and to add or hide pre-selected products from the search results.
+
+To provide a more visual, complete, and intuitive experience, we have launched a new editor option for creating merchandising rules.
+
+## What has changed?
+
+Previously, stores using [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) relied exclusively on the [manual editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) for Merchandising Rules. Now, you can also choose the [new visual editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr), which allows you to:
+
+* Preview the search results customers will see while navigating the store.
+* Reorder search results.
+* Pin a product to the top positions in the search results.
+* Review the main product information.
+
+![visual-merch-rules-EN-announcement](//images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/058e0548f09749d0db291a9a222e369f/visual-merch-rules-EN-announcement.png)
+
+When creating a merchandising rule in the VTEX Admin under **Storefront > Intelligent Search > Merchandising Rules > New**, you can choose the type of editor you want to use. Read the [Merchandising Rules](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#types-of-editing) guide for more information on the differences between the manual and the visual editor.
+
+## What needs to be done?
+
+No action is required. The new editor is available for all stores using[ VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Read the [Creating merchandising rules - Visual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr) guide for more information.
diff --git a/docs/announcements/en/vtex-io-documentation-has-a-new-home.md b/docs/announcements/en/vtex-io-documentation-has-a-new-home.md
index 208a2bb94..f54d527d5 100644
--- a/docs/announcements/en/vtex-io-documentation-has-a-new-home.md
+++ b/docs/announcements/en/vtex-io-documentation-has-a-new-home.md
@@ -19,7 +19,7 @@ Since March 13th, 2020, VTEX IO and VTEX IO Store Framework documentation is no
 
 The documentation can be accessed in [**VTEX IO Docs**](https://vtex.io/docs), our documentation platform where all content related to both solutions is available. 
 
-![vtex-io-docs](https://images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/a78b3e5600bc5b7c1dcefcaa5da40fb6/vtex-io-docs.png)
+![vtex-io-docs](//images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/a78b3e5600bc5b7c1dcefcaa5da40fb6/vtex-io-docs.png)
 
 ## Why the change?
 
@@ -33,7 +33,7 @@ The decision to remove VTEX IO and VTEX IO Store Framework documentation from He
 
 Home to our [API documentation](https://developers.vtex.com/reference), [guides](https://developers.vtex.com/docs) aimed at developers working with integrations and customization, and the [Release Notes](https://developers.vtex.com/changelog), which are synced with all the latest updates about our product, the [**Developer Portal**](https://developers.vtex.com) - formerly known as Help Center Developer Docs - offers all the necessary resources for VTEX's most advanced users in a single place. 
 
-![developer-portal](https://images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/4c1aa7fcb8d7275e1287d5e03bbe1e80/developer-portal.png)
+![developer-portal](//images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/4c1aa7fcb8d7275e1287d5e03bbe1e80/developer-portal.png)
 
 Aiming to improve VTEX development experience, the Developer Portal will soon incorporate the VTEX IO and VTEX IO Store Framework documentation - which is available today on VTEX IO Docs.
 
diff --git a/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md b/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md
index e2df97019..20c078037 100644
--- a/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md
+++ b/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'VTEX Admin has three new language options.'
 
 The VTEX admin currently supports different language options to serve our clients all over the world. We localize our product to enhance its overall experience, not only through translations but also on a cultural level, taking into account the particularities of each country.
 
-![EN new locales](https://images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/aa4557f81746ab4e3735b07aaf4085a0/EN_new_locales.jpg)
+![EN new locales](//images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/aa4557f81746ab4e3735b07aaf4085a0/EN_new_locales.jpg)
 
 ## What has changed?
 In addition to Portuguese, English, Spanish, Italian, Romanian and Japanese, starting May 2021, VTEX users will find three new language options in our Admin: Dutch, French and Korean. 
diff --git a/docs/announcements/en/vtex-launches-the-new-version-of-instore-vtex-sales-app.md b/docs/announcements/en/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
index b0e69c654..b73f8deb2 100644
--- a/docs/announcements/en/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
+++ b/docs/announcements/en/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
@@ -29,7 +29,7 @@ The new menu provides significant advantages, which are highlighted below:
 - **Intuitive navigation:** Improved layout to quickly find what you need.
 - **Visual consistency:** Consistent look and feel aligned with other recent platform updates.
 
-<img src="https://images.ctfassets.net/alneenqid6w5/pcXNfExZYZML7AHP57tzz/42794337b88dd86f325eb5e034d44f1f/image.png" alt= “menu-sales-app-en” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/pcXNfExZYZML7AHP57tzz/42794337b88dd86f325eb5e034d44f1f/image.png" alt= “menu-sales-app-en” width="35%" height="35%">
 
 ### Offers section
 
@@ -37,13 +37,13 @@ The Offers section allows merchants to display specific products or search resul
 
 One of the key features of this update is that merchants can set the Offers section as their home page. This provides a more customized user experience, as customers are immediately greeted with selected content and product recommendations. Learn more in the [Enabling Local stock sale in VTEX Sales App](https://help.vtex.com/en/tutorial/enabling-local-stock-sale-in-vtex-sales-app--54eQN4rOH5yBYPGG2w8v9q) article.
 
-<img src="https://images.ctfassets.net/alneenqid6w5/XXJQykcV9p6yNN6Q5mB5u/fcdfa190f4766760449d9bf4d7eff4b5/image.png" alt= “anuncio-sale-app-en” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/XXJQykcV9p6yNN6Q5mB5u/fcdfa190f4766760449d9bf4d7eff4b5/image.png" alt= “anuncio-sale-app-en” width="35%" height="35%">
 
 ### Sales Performance
 
 The Sales Performance page allows merchants to view their sales metrics and compare performance across sales dates and staff performance. Learn more in the [VTEX Sales App: Sales Performance](https://help.vtex.com/en/tutorial/sales-app-sales-performance--7i4Elt835tatBM6iqZoc56) article.
 
-<img src="https://images.ctfassets.net/alneenqid6w5/3UWhX6QODOG8pQ6Xi0QXKV/0f05e6e637790f140f22bb5b9bf877e5/image.png" alt= “vendas-da-loja-sales-app-en” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/3UWhX6QODOG8pQ6Xi0QXKV/0f05e6e637790f140f22bb5b9bf877e5/image.png" alt= “vendas-da-loja-sales-app-en” width="35%" height="35%">
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/vtex-marketplace-launches-in-2022.md b/docs/announcements/en/vtex-marketplace-launches-in-2022.md
index ba5ad79b6..ca074df55 100644
--- a/docs/announcements/en/vtex-marketplace-launches-in-2022.md
+++ b/docs/announcements/en/vtex-marketplace-launches-in-2022.md
@@ -29,7 +29,7 @@ The new features allow marketplaces to:
 
 Go beyond traditional ecommerce with the [VTEX 2022 Marketplace Release](https://content.vtex.com/en/2022-marketplace-release/?utm_source=announcement&utm_medium=organic&utm_campaign=2022_marketplace_release).
 
-![capa de blog marketplace 2022](https://images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/9c691ba396bbd1c6fdd0c8d6b53f1b58/capa_de_blog.png)
+![capa de blog marketplace 2022](//images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/9c691ba396bbd1c6fdd0c8d6b53f1b58/capa_de_blog.png)
 
 ## What are the launches? 
 
@@ -78,7 +78,7 @@ Learn more about each one below.
 
 ### Seller Portal 
 
-![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 The Seller Portal is a VTEX platform edition for [sellers](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402) to connect and sell their products on VTEX marketplaces. The portal allows sellers to access all the key features necessary to operate ecommerce on big storefronts, increasing visibility and sales conversion. 
 
@@ -126,7 +126,7 @@ To facilitate new sellers joining the Seller Portal, we have also launched the [
 
 ### Seller management
 
-![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 We launched the redesigned experience of the [Seller Management](https://help.vtex.com/en/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv) page, where marketplace operators can [add sellers](https://help.vtex.com/en/tutorial/adicionar-seller-beta--6q4G4RNqVENr5YMJyindwL) and their respective information and manage their status. 
 
diff --git a/docs/announcements/en/vtex-sales-app-will-no-longer-be-available-for-windows.md b/docs/announcements/en/vtex-sales-app-will-no-longer-be-available-for-windows.md
new file mode 100644
index 000000000..b098f24f0
--- /dev/null
+++ b/docs/announcements/en/vtex-sales-app-will-no-longer-be-available-for-windows.md
@@ -0,0 +1,37 @@
+---
+title: 'VTEX Sales App will no longer be available as an application on Windows'
+id: 1wcqeNs1AyppGdu20FjAJ8
+status: PUBLISHED
+createdAt: 2023-08-02T15:12:02.978Z
+updatedAt: 2023-08-03T16:00:53.203Z
+publishedAt: 2023-08-03T16:00:53.203Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-sales-app-will-no-longer-be-available-for-windows
+locale: en
+legacySlug: vtex-sales-app-will-no-longer-be-available-for-windows
+announcementImageID: ''
+announcementSynopsisEN: 'The VTEX Sales App will no longer be supported as a native app on Windows, available only on the web interface.'
+---
+
+As part of our ongoing efforts to improve the user experience, we are deprecating VTEX Sales App for Windows.
+
+## What has changed?
+
+As of October 31, 2023, VTEX Sales App will no longer be available for Windows.
+
+## What needs to be done?
+
+The update will be automatically applied to all VTEX stores using VTEX Sales App. To access it from Windows, or any operating system, you will need to access the web version of VTEX Sales App through the following URL:
+
+```
+https://{accountname}.myvtex.com/assisted-sales/sales-app
+```
+
+To learn more about VTEX Sales App, see our documentation:
+
+* [VTEX Sales App - Getting started and setting up](https://help.vtex.com/en/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc#)
+* [VTEX Sales App - Payments](https://help.vtex.com/en/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy#)
+* [VTEX Sales App - Using the app](https://help.vtex.com/en/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr#)
+* [Unified Commerce Strategies](https://help.vtex.com/en/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv)
diff --git a/docs/announcements/en/web-page-performance-deprecation.md b/docs/announcements/en/web-page-performance-deprecation.md
new file mode 100644
index 000000000..57cf925f5
--- /dev/null
+++ b/docs/announcements/en/web-page-performance-deprecation.md
@@ -0,0 +1,24 @@
+---
+title: 'Web Page Performance module discontinuation'
+id: 4zrnpCSC8R8OFpahiaf2sE
+status: PUBLISHED
+createdAt: 2024-05-29T17:50:25.024Z
+updatedAt: 2024-05-29T19:04:53.248Z
+publishedAt: 2024-05-29T19:04:53.248Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: web-page-performance-deprecation
+locale: en
+legacySlug: web-page-performance-module-discontinuation
+announcementImageID: ''
+announcementSynopsisEN: 'The Web Page Performance module will be deprecated.'
+---
+
+On **June 04, 2024,** we will disable the VTEX Admin **Web Page Performance module.** The module allowed merchants to monitor the performance metrics of their ecommerce URLs presented by [PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about) directly on the VTEX platform.
+
+From now on, merchants will be able to [monitor and optimize these metrics](https://developers.google.com/speed?hl=es-419) through the [PageSpeed Insights](https://pagespeed.web.dev/) website.
+
+## What needs to be done?
+
+In this discontinuation, the merchants do not need to take any action. In the VTEX Admin, the [Store Overview](https://help.vtex.com/en/tutorial/vista-general-de-la-tienda--P8ahguoRs0U3PzmXg2wuQ) and [Sales Performance](https://help.vtex.com/en/tutorial/desempeno-de-ventas--3DMube0sEsK9vPcRYGas72) modules will continue to be available.
diff --git a/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md
index 215defd36..b2f028220 100644
--- a/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md
@@ -19,7 +19,7 @@ Digital businesses are increasingly looking for tools that can help them grow, w
 
 Welcome to the [redesigned Admin experience](https://content.vtex.com/join-new-admin-beta-program-en/?utm_source=announcement&utm_medium=organic&utm_campaign=new_admin_beta).
 
-![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/weve-released-our-new-cross-selling-and-up-selling-apis.md b/docs/announcements/en/weve-released-our-new-cross-selling-and-up-selling-apis.md
index 14aa31aad..8fa0cab66 100644
--- a/docs/announcements/en/weve-released-our-new-cross-selling-and-up-selling-apis.md
+++ b/docs/announcements/en/weve-released-our-new-cross-selling-and-up-selling-apis.md
@@ -3,8 +3,8 @@ title: "We've released our new Cross-selling and Up-selling APIs"
 id: 37Lc6sI2owMCiUamocgAcc
 status: PUBLISHED
 createdAt: 2017-12-04T18:54:28.850Z
-updatedAt: 2020-05-11T19:43:09.938Z
-publishedAt: 2020-05-11T19:43:09.938Z
+updatedAt: 2024-01-04T15:05:24.804Z
+publishedAt: 2024-01-04T15:05:24.804Z
 contentType: updates
 productTeam: Marketing & Merchandising
 author: 245tA425AIeioKAk2eaiwS
@@ -73,6 +73,6 @@ This API will return the products that were registered as Up-selling __suggestio
 
 ## Go further
 
-For more details on the requests, please visit our [API documentation](https://developers.vtex.com/reference/crossselling#productsearchwhosawalsosaw).
+For more details on the requests, please visit our [API documentation](https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/products/crossselling/whosawalsosaw/-productId-?endpoint=get-/api/catalog_system/pub/products/crossselling/whosawalsosaw/-productId-).
 
 For more information on the Cross-selling and Up-Selling techniques described above, access the [VTEX Help article](/en/tutorial/setting-up-a-similar-product-suggestions-accessories-and-generics)
diff --git a/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md b/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md
index cf5be8e54..62ee37cc0 100644
--- a/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md
+++ b/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md
@@ -24,7 +24,7 @@ The application is available in the [VTEX App Store](https://apps.vtex.com/ "VTE
 - Adding a heart icon next to each product in the product lists and product detail pages;
 - Creating a Wishlist page, where customers can see their favorite items and easily purchase them.
 
-![Wishlist Printscreen](https://images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
+![Wishlist Printscreen](//images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
 
 ## What are the advantages?
 - Makes your store’s shopping experience more complete;
diff --git a/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 354383732..bae1d05c4 100644
--- a/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -21,7 +21,7 @@ From June 25 <sup>th</sup>, 2019, users without access to <code>Checkout</code>
 
 Seeking to ensure greater safety, we created the possibility to limit user access to the **Settings** screen on the Orders Management module, allowing information to be edited by selected users only. 
 
-![2019-06-07 17 24 10-Settings.en](https://images.ctfassets.net/alneenqid6w5/6YfxLgI43YD5FwrXu92j2A/aca4f546516816fabd42f25a39450a6d/2019-06-07_17_24_10-Settings.en.png)
+![2019-06-07 17 24 10-Settings.en](//images.ctfassets.net/alneenqid6w5/6YfxLgI43YD5FwrXu92j2A/aca4f546516816fabd42f25a39450a6d/2019-06-07_17_24_10-Settings.en.png)
 
 ## Main Advantages 
 
@@ -41,7 +41,7 @@ In order to do this, you need to add a product called `Checkout` to the desired
 6. Choose the type of permission you wish to grant: either `Save Order Configuration` if you want to allow the user to edit the **Orders** secction, or `Save OrderForm Configuration` if you want the user to edit the **Cart** section.
 7. Finally, click on **Save**.
 
-![GIT-Checkout.en](https://images.ctfassets.net/alneenqid6w5/1stGxj4wiW6Ijfl4f5QFry/481f3c628d303dc72a40db8bbb81a89e/GIT-Checkout.en.gif)
+![GIT-Checkout.en](//images.ctfassets.net/alneenqid6w5/1stGxj4wiW6Ijfl4f5QFry/481f3c628d303dc72a40db8bbb81a89e/GIT-Checkout.en.gif)
 
 Upon adding this new product to a profile, ensure that the desired users are in fact linked to this profile.
 
diff --git a/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md b/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md
index 029683f8f..743884554 100644
--- a/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md
+++ b/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md
@@ -21,7 +21,7 @@ Con este fin, hemos creado la nueva pantalla [Rendimiento de las páginas web](h
 
 PageSpeed Insights y Lighthouse son herramientas desarrolladas por Google para proporcionar información sobre la experiencia de usuario de una página tanto en dispositivos móviles como de escritorio, ofreciendo sugerencias sobre cómo se puede mejorar esa página. Utilizan las [Métricas web principales de Google](https://web.dev/vitals/#core-web-vitals) para evaluar la experiencia del usuario _online_.
 
-![Web page performance Dash ES](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
+![Web page performance Dash ES](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/admin-disponivel-em-japones.md b/docs/announcements/es/admin-disponivel-em-japones.md
index 705a4b574..b12a28ea1 100644
--- a/docs/announcements/es/admin-disponivel-em-japones.md
+++ b/docs/announcements/es/admin-disponivel-em-japones.md
@@ -25,4 +25,4 @@ La [apertura de una oficina en Singapur](https://vtex.com/us-en/press/vtex-opens
 
 ## ¿Qué se necesita hacer?
 Para visualizar el Admin en japonés, basta con seleccionar el código __JP__ en el menú desplegable de idioma situado en la esquina superior derecha de la pantalla. 
-![Seleccionar el código JP ](https://images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/7ab7644ee7b02343b7eccaa5dc2e4596/japones.png)
+![Seleccionar el código JP ](//images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/7ab7644ee7b02343b7eccaa5dc2e4596/japones.png)
diff --git a/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
index f38564df5..2ee705f62 100644
--- a/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -29,7 +29,7 @@ Ahora, los usuarios sólo verán los ítems del menú de la barra lateral a los
 
 La imagen a continuación ilustra cómo la barra lateral cambiaría al aplicar esta modificación de mantenimiento para mejorar la seguridad y la experiencia de usuario de su tienda.
 
-![ES Sidebar permissions announcement screenshot](https://images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/e099126ea9483ee64e156948b6bd1695/ES_Sidebar_permissions_announcement_screenshot__1_.png)
+![ES Sidebar permissions announcement screenshot](//images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/e099126ea9483ee64e156948b6bd1695/ES_Sidebar_permissions_announcement_screenshot__1_.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/amazon-integration-amazon-offer-matching.md b/docs/announcements/es/amazon-integration-amazon-offer-matching.md
new file mode 100644
index 000000000..74394acbb
--- /dev/null
+++ b/docs/announcements/es/amazon-integration-amazon-offer-matching.md
@@ -0,0 +1,35 @@
+---
+title: 'Integración con Amazon: Match de anuncios Amazon'
+id: 6cWiUoUTzVtOAVpF4XhOzm
+status: PUBLISHED
+createdAt: 2023-07-04T20:11:24.168Z
+updatedAt: 2023-07-04T21:44:36.582Z
+publishedAt: 2023-07-04T21:44:36.582Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: integracion-con-amazon-match-de-anuncios-amazon
+locale: es
+legacySlug: match-de-anuncios-amazon
+announcementImageID: ''
+announcementSynopsisES: 'El proceso de matching de anuncios Amazon es ahora manual. Conoce la nueva página.'
+---
+
+La [integración](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon)  entre las tiendas VTEX y Amazon permite a los sellers enviar su catálogo de productos al marketplace, lo que amplía sus canales de venta. Con el objetivo de ofrecer mayor calidad a los anuncios que se muestran en Amazon, hemos desarrollado una nueva página para que los sellers de VTEX hagan el proceso de matching de productos.
+
+## ¿Qué cambió?
+
+Antes, cuando un seller enviaba un producto a la integración de Amazon, se realizaba un proceso de matching automático para vincular el SKU del seller con el ASIN (Número de Identificación Estándar de Amazon) del producto en Amazon. Sin embargo, a veces el proceso provocaba errores de compatibilidad entre el producto enviado y el anuncio mostrado en Amazon. 
+
+Con el nuevo flujo de matching, los sellers son los responsables de aprobar las coincidencias entre sus productos y los anuncios de Amazon. Aunque el matching es ahora un proceso manual, los sellers pueden aprobar varios SKU a la vez.
+
+## ¿Por qué realizamos este cambio?
+
+El proceso será ahora completamente manual. Este cambio tiene como objetivo reducir los errores de compatibilidad, para que los sellers ofrezcan anuncios fiables y de calidad en el marketplace, dando a los sellers el control sobre la correspondencia entre los productos enviados y los anuncios publicados.
+
+## ¿Qué se necesita hacer?
+
+Puedes encontrar la página __Match de anuncios Amazon__ en *Marketplace* > __Match de anuncios Amazon__ o a través de la barra de búsqueda. La página estará disponible para todas las cuentas VTEX a partir del 03 de Julio de 2023. No se requiere ninguna acción para activarla.
+
+Para más información sobre el funcionamiento de la página, consulta la [documentación Match de anuncios Amazon](https://help.vtex.com/en/tutorial/match-de-anuncios-amazon--7fRfoP69kYgg8znImMhyQ0).
+
diff --git a/docs/announcements/es/amazon-new-category-mapping-model.md b/docs/announcements/es/amazon-new-category-mapping-model.md
new file mode 100644
index 000000000..df2c8b919
--- /dev/null
+++ b/docs/announcements/es/amazon-new-category-mapping-model.md
@@ -0,0 +1,35 @@
+---
+title: 'Amazon: nuevo modelo de mapeo de categorías'
+id: 584nPLYkI8tnOGz1s4X5LE
+status: PUBLISHED
+createdAt: 2023-11-27T23:08:37.697Z
+updatedAt: 2023-12-18T15:49:17.763Z
+publishedAt: 2023-12-18T15:49:17.763Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: amazon-nuevo-modelo-de-mapeo-de-categorias
+locale: es
+legacySlug: amazon-nuevo-modelo-de-mapeo-de-categorias
+announcementImageID: ''
+announcementSynopsisES: 'Conoce el nuevo modelo de mapeo de categorías y atributos en la integración de VTEX y Amazon.'
+---
+
+Un paso importante en la [integración](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5sYA9MlRo92jJIxKF1MTXb) entre las tiendas VTEX y Amazon es el proceso de mapeo de categorías y atributos, que consiste en realizar un match entre los productos de tu catálogo y los anuncios disponibles en Amazon.  
+
+Para que el proceso de mapeo sea más fácil e intuitivo, hemos desarrollado el **[Mapeo de categorías y atributos a través del Admin VTEX](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD?&utm_source=autocomplete#mapeamento-via-admin-vtex-beta),** que está disponible para tiendas VTEX de Brasil, México y Estados Unidos. Para acceder al nuevo modelo de mapeo, dirígete a **Marketplace > Marketplaces e integraciones > Amazon > Realizar mapeo.** El paso a paso está disponible en el tutorial [Envío y mapeo de categorías de productos a Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).  
+
+## ¿Qué cambió?
+
+Antes, el proceso de mapeo solo podía realizarse [a través de la plantilla](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD?&utm_source=autocomplete#mapeamento-via-planilha). Ahora, con el nuevo modelo de mapeo, puedes elegir la forma de mapeo que más se ajuste a los requisitos de tu operación.  
+
+Estos son algunos de los beneficios del mapeo de categorías y atributos a través del Admin VTEX:  
+
+- Dar seguimiento al status de mapeo de cada categoría.  
+- Buscar la categoría en Amazon para realizar la coincidencia (match) con tu catálogo.  
+- Relleno automático de atributos ya presentes en tu catálogo.  
+- Personalización de la tabla de tarifas de envío por SKU.  
+
+## ¿Qué se necesita hacer?
+
+La funcionalidad estará disponible para todas las cuentas [VTEX que actúan como seller](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) a partir del **18 de diciembre de 2023.** Para utilizarla, necesitas tener tu cuenta VTEX [integrada](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5sYA9MlRo92jJIxKF1MTXb) con Amazon y enviar los productos utilizando el tutorial [Envío y mapeo de categorías de productos a Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).  
diff --git a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md
index 6b4ca8322..ae9387bc5 100644
--- a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md
+++ b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md
@@ -22,7 +22,7 @@ Una situación común en los restaurantes que aceptan pedidos online, por ejempl
 
 Para simplificar el uso de esta funcionalidad, hemos desarrollado la aplicación **Assembly Options**, que presenta una interfaz para configurar y gestionar las opciones de personalización. La aplicación solo está disponible para las tiendas que utilizan [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app-es](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
+![assembly-options-app-es](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md
index 3d3e8ec2c..e35f023bf 100644
--- a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md
+++ b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md
@@ -22,7 +22,7 @@ Una situación común en los restaurantes que aceptan pedidos online, por ejempl
 
 Para simplificar el uso de esta funcionalidad, hemos desarrollado la aplicación **Assembly Options**, que presenta una interfaz para configurar y gestionar las opciones de personalización. La aplicación solo está disponible para las tiendas que utilizan [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app-es](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
+![assembly-options-app-es](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/autocomplete-metrics-now-available-in-search-reports.md b/docs/announcements/es/autocomplete-metrics-now-available-in-search-reports.md
index f1d88a642..e2d7156a7 100644
--- a/docs/announcements/es/autocomplete-metrics-now-available-in-search-reports.md
+++ b/docs/announcements/es/autocomplete-metrics-now-available-in-search-reports.md
@@ -23,7 +23,7 @@ Antes solo se podía ver y exportar informes sobre los resultados de búsqueda y
 <table width = "100%">
   <tr>
     <td>
-      <img src = "https:https://images.ctfassets.net/alneenqid6w5/7xQxfEBJDIY7aOBzPqkRox/9a2594c86f5fe7aa30e75f78a10241e9/relatorios-filtros-ES.png" style = "display:block; margin-left: auto; margin-right: auto;" alt = "Opções de filtros do relatório" title = "Opções de filtros do relatório">
+      <img src = "https://images.ctfassets.net/alneenqid6w5/7xQxfEBJDIY7aOBzPqkRox/9a2594c86f5fe7aa30e75f78a10241e9/relatorios-filtros-ES.png" style = "display:block; margin-left: auto; margin-right: auto;" alt = "Opções de filtros do relatório" title = "Opções de filtros do relatório">
     </td>
   </tr>
   <tr>
diff --git a/docs/announcements/es/automatic-archiving-inactive-promotions.md b/docs/announcements/es/automatic-archiving-inactive-promotions.md
new file mode 100644
index 000000000..f27b3f189
--- /dev/null
+++ b/docs/announcements/es/automatic-archiving-inactive-promotions.md
@@ -0,0 +1,41 @@
+---
+title: 'Archivado automático  de promociones inactivas'
+id: 4LDQbli98aRSNJDus7mgqi
+status: PUBLISHED
+createdAt: 2024-05-13T11:40:27.337Z
+updatedAt: 2024-05-20T12:14:24.232Z
+publishedAt: 2024-05-20T12:14:24.232Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: archivado-automatico-de-promociones-inactivas
+locale: es
+legacySlug: archivado-automatico-de-promociones-inactivas
+announcementImageID: ''
+announcementSynopsisES: 'La nueva función de archivado automático de promociones inactivas mejora la gestión de promociones en tu tienda.'
+---
+
+Con el objetivo de optimizar la experiencia de gestión de promociones, VTEX está implementando el archivado automático de promociones inactivas. Esta funcionalidad facilita la organización y el monitoreo de las promociones disponibles en tu tienda. 
+
+## ¿Qué cambió?
+
+Aplicamos las siguientes optimizaciones en la experiencia de gestión de promociones.
+
+**Autoarchivado de promociones:
+
+1. **Promociones con fecha de fin (inactivas):** se archivarán automáticamente 7 días después de la última modificación, contados a partir de la fecha de término de la promoción.
+
+2. **Promociones sin fecha de finalización (inactivas):** se archivarán automáticamente 30 días después de la última modificación.
+
+3. **Promociones con fecha de fin (activas):** se archivarán automáticamente 7 días después de la fecha de término de la promoción.
+
+**Optimización de recursos:** hemos optimizado el tiempo de carga y el desempeño de la lista de promociones.
+
+<div class = "alert alert-info">
+Para ver a las promociones que se archivaron automáticamente, accede al Admin VTEX <b>Promociones > Promociones</b>, o <b>ingresa Promociones</b> en la barra de búsqueda de la parte superior de la página. En la esquina superior derecha haz clic en <i class="fas fa-ellipsis-v" aria-hidden="true"></i>, y después en Promociones aplicadas.
+</div>
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción. La funcionalidad de archivado automático de promociones inactivas ya está disponible en todas las tiendas VTEX.
+
diff --git a/docs/announcements/es/black-week-vtex-dashboards-analysis-strategies.md b/docs/announcements/es/black-week-vtex-dashboards-analysis-strategies.md
new file mode 100644
index 000000000..b158187cc
--- /dev/null
+++ b/docs/announcements/es/black-week-vtex-dashboards-analysis-strategies.md
@@ -0,0 +1,22 @@
+---
+title: 'Black Week: Estrategias de Análisis de Dashboards VTEX'
+id: 1MrvvWj1ziiqLWhM021PX7
+status: PUBLISHED
+createdAt: 2023-11-20T20:29:11.550Z
+updatedAt: 2023-11-20T20:39:16.159Z
+publishedAt: 2023-11-20T20:39:16.159Z
+contentType: updates
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: black-week-estrategias-de-analisis-de-dashboards-vtex
+locale: es
+legacySlug: black-week-estrategias-de-analisis-de-dashboards-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Conozca las mejores estrategias para analizar sus métricas de ventas durante la Black Week con la guía VTEX Dashboards'
+---
+
+Hemos llegado oficialmente a la __Black Week,__ que se extiende del __20/11/2023__ al __27/11/2023.__ Las tiendas ya tienen sus campañas online y sus operaciones listas para atender a los compradores.
+
+Con el objetivo de maximizar las oportunidades de mejora de las acciones del __Black Friday__ durante este período, creamos el __Guía de los dashboards VTEX para la Black Week: FAQ,__ enfocado en aclarar las preguntas más frecuentes relacionadas con el uso de los dashboards en el VTEX Admin durante el evento más importante del año.
+
+Lea el [Guía de los dashboards VTEX para la Black Week: FAQ](https://help.vtex.com/es/tutorial/guia-de-los-dashboards-vtex-para-la-black-week-faq--6O3CiGiZctVIgIrpIcko9h) donde encontrará respuestas a las preguntas más frecuentes sobre cómo utilizar los Dashboards durante la Black Week.
diff --git a/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 33bacada6..6099ce0b0 100644
--- a/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -25,7 +25,7 @@ La solución combina dos funcionalidades y aplicaciones móviles:
 - [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): control de la entrega last-mile.
 - **Aplicaciones móviles:** aplicaciones para entregadores y conductores.
 
-![pick_pack_gif_ES](https://images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/c662e643c1ab451f005898166b65b0f7/pick_pack_gif_ES.gif)
+![pick_pack_gif_ES](//images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/c662e643c1ab451f005898166b65b0f7/pick_pack_gif_ES.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/callback-url-signature-authentication-token.md b/docs/announcements/es/callback-url-signature-authentication-token.md
new file mode 100644
index 000000000..a0eece91d
--- /dev/null
+++ b/docs/announcements/es/callback-url-signature-authentication-token.md
@@ -0,0 +1,32 @@
+---
+title: 'Callback URL signature: bloqueo de autorizaciones de pago asíncrono que no utilicen token de autenticación'
+id: 3at5YtI2L6QqBym6Af56tV
+status: PUBLISHED
+createdAt: 2024-05-03T18:12:04.996Z
+updatedAt: 2024-05-03T18:33:19.277Z
+publishedAt: 2024-05-03T18:33:19.277Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: callback-url-signature-token-de-autenticacion
+locale: es
+legacySlug: callback-url-signature-token-de-autenticacion
+announcementImageID: ''
+announcementSynopsisES: 'Token de autenticación para autorizaciones de pago asíncrono'
+---
+
+Con el objetivo de optimizar las operaciones de pago realizadas en la plataforma, VTEX está implementando el uso del token de autenticación `X-VTEX-signature`. Este token deben utilizarlo partners y proveedores de servicios de pago al retornar el status de una transacción de pago asíncrona a través de [callback URL](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#callback-url).
+
+A partir del 27 de mayo de 2024, el gateway de VTEX enviará en cada transacción de pago la información de callback URL y el respectivo token de autenticación.
+
+Ejemplo de callback URL que contiene el token de autenticación:
+
+`https://gatewayqa.vtexpaids.com.br/api/pvt/paid-provider/transactions/8FB0F111111122222333344449984ACB/paids/A2A9A25B11111111222222333327883C/callback?accountName=teampaidsintegrations&X-VTEX-signa ture=R123456789aBcDeFGHij1234567890tk`
+
+## ¿Qué se necesita hacer?
+
+A partir del 26 de junio de 2024, todos los partners y proveedores de servicios de pago deben informar el status de una transacción de pago asíncrona únicamente a través de callback URL y token de autenticación.
+
+Después de esta fecha, cualquier información que se envíe únicamente a callback URL (sin el token de autenticación) será bloqueada y se cancelarán las respectivas transacciones de pago.
+
+Para más información sobre callback URL, consulta [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#callback-url) y [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
diff --git a/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md b/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md
index d144d9240..7f1fa6e49 100644
--- a/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md
+++ b/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md
@@ -23,7 +23,7 @@ Mejoramos la configuración de Audiencia de campañas para permitirte sumar púb
 
 En el Admin VTEX, en **Productos > Promociones y Tasas > Audiencia de campañas > Nueva audiencia de campaña**, en las configuraciones referidas al **Público objetivo**, agregamos la opción «y», donde antes solo estaba la opción «o».  Esto significa que ahora puedes aplicar una lógica de adición de criterios («y»), además de la lógica de alternativa («o») que ya existía. Observa la imagen a continuación:
 
-![publico-alvo-e-ou-es](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
+![publico-alvo-e-ou-es](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
 
 Con la nueva opción, puedes crear promociones de campaña a partir de una combinación de criterios de una manera más flexible.
 
diff --git a/docs/announcements/es/catalogs-new-visual-and-navigation.md b/docs/announcements/es/catalogs-new-visual-and-navigation.md
index 77fe0cfad..5a6d5bbd5 100644
--- a/docs/announcements/es/catalogs-new-visual-and-navigation.md
+++ b/docs/announcements/es/catalogs-new-visual-and-navigation.md
@@ -23,16 +23,16 @@ La principal diferencia para la versión antigua está en la navegación. Cambie
 ## Que ha cambiado
 
 La mayoría de los elementos del Catálogo se pueden encontrar en _Catálogo_, que se encuentra en la sección _PRODUCTOS_ del menú lateral.
-![ES-Catálogo1](https://images.ctfassets.net/alneenqid6w5/34XVA7oE408IGWg0ksG4qQ/7ac747eed47cc684526edd8a8e860ace/ES-Cat__logo1.png)
+![ES-Catálogo1](//images.ctfassets.net/alneenqid6w5/34XVA7oE408IGWg0ksG4qQ/7ac747eed47cc684526edd8a8e860ace/ES-Cat__logo1.png)
 
 
 El ítem _Tarjeta de regallo_ (que antes se llamaba _Vales_ y se encontraba en _Controles de campañas_) ahora está en _Pagos_, dentro de la sección _TRANSACCIONES_ del menú lateral.
-![ES-Catálogo2](https://images.ctfassets.net/alneenqid6w5/1QZmRnr4Y8M80sSQGywG8i/6b66051ad5a8fe23a79d779faa2dfea4/ES-Cat__logo2.png)
+![ES-Catálogo2](//images.ctfassets.net/alneenqid6w5/1QZmRnr4Y8M80sSQGywG8i/6b66051ad5a8fe23a79d779faa2dfea4/ES-Cat__logo2.png)
 
 
 El elemento _Configuraciones_ se convirtió en un ítem de _CMS_, que se encuentra en la sección _CONFIGURACIÓN DE LA TIENDA_ del menú lateral.
-![ES-Catálogo3](https://images.ctfassets.net/alneenqid6w5/2KMa8ImOCsakEyaGa8yci0/c7f86a05fcb34f14b31771f558b3efe0/ES-Cat__logo3.png)
+![ES-Catálogo3](//images.ctfassets.net/alneenqid6w5/2KMa8ImOCsakEyaGa8yci0/c7f86a05fcb34f14b31771f558b3efe0/ES-Cat__logo3.png)
 
 
 La pestaña _Marketplace_ ganó una sección propia del mismo nombre en el menú lateral.
-![ES-Catálogo4](https://images.ctfassets.net/alneenqid6w5/6bTv54WR4QwaiOKOoiwSIG/f124f5a1bd87d0ce854108658cd52467/ES-Cat__logo4.png)
+![ES-Catálogo4](//images.ctfassets.net/alneenqid6w5/6bTv54WR4QwaiOKOoiwSIG/f124f5a1bd87d0ce854108658cd52467/ES-Cat__logo4.png)
diff --git a/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md b/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
index 0d6fbbe3f..542b9be6d 100644
--- a/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
+++ b/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
@@ -27,7 +27,7 @@ Tenga la seguridad de que no nos equivocamos. Tras un cuidadoso análisis, nuest
 
 Pero eso no es todo. También renovamos por completo el proceso para cambiar el usuario titular de una cuenta, transformándolo en un flujo de transferencia basado en invitaciones que es totalmente auditable. 
 
-![Gestion titular gif](https://images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/0faedf49cfdee92ffdaabbdb3a624b04/Announcement_ES.gif)
+![Gestion titular gif](//images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/0faedf49cfdee92ffdaabbdb3a624b04/Announcement_ES.gif)
 
 Consulte [Transferir la propiedad de la tienda](https://help.vtex.com/es/tutorial/transferir-la-propiedad-de-la-tienda) para conocer más detalles sobre este nuevo proceso. 
 
diff --git a/docs/announcements/es/changes-in-vtex-support-service-policy.md b/docs/announcements/es/changes-in-vtex-support-service-policy.md
new file mode 100644
index 000000000..3b851bba7
--- /dev/null
+++ b/docs/announcements/es/changes-in-vtex-support-service-policy.md
@@ -0,0 +1,18 @@
+---
+title: 'Cambios en la política de atención al cliente de Soporte VTEX'
+id: 7f5YRWJQ7q0VUGCTDKVDon
+status: PUBLISHED
+createdAt: 2024-02-16T18:37:29.587Z
+updatedAt: 2024-02-22T21:12:09.365Z
+publishedAt: 2024-02-22T21:12:09.365Z
+contentType: updates
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: cambios-en-la-politica-de-atencion-al-cliente-de-soporte-vtex
+locale: es
+legacySlug: cambios-en-la-politica-de-atencion-al-cliente-de-soporte-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Ahora, el canal principal para abrir un ticket es la Comunidad VTEX.'
+---
+
+<div class="alert alert-info">Este contenido está siendo traducido.</div>
diff --git a/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md b/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md
new file mode 100644
index 000000000..1e7c08848
--- /dev/null
+++ b/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md
@@ -0,0 +1,39 @@
+---
+title: 'La API de Checkout ahora es compatible con reCAPTCHA v3'
+id: 1buRTScMhlis0LESr7g8Rt
+status: PUBLISHED
+createdAt: 2023-06-28T19:52:18.268Z
+updatedAt: 2023-08-25T23:36:39.909Z
+publishedAt: 2023-08-25T23:36:39.909Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: la-api-de-checkout-ahora-es-compatible-con-recaptcha-v3
+locale: es
+legacySlug: la-api-de-checkout-ahora-es-compatible-con-recaptcha-v3
+announcementImageID: ''
+announcementSynopsisES: 'Esta solución para evitar usuarios falsos puede utilizarse en aplicaciones móviles y otras integraciones similares.'
+---
+
+[reCAPTCHA](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP) es una solución utilizada para la validación de usuarios reales que VTEX dispone para todas las tiendas. Prevé situaciones en que se utilizan programas maliciosos para cometer fraude, impidiendo así el acceso de falsos usuarios.
+
+Además de la funcionalidad disponible para los storefronts nativos de la plataforma VTEX, las tiendas que implementan storefronts propios también pueden [integrar reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) a través de la API de Checkout con el fin de aumentar la seguridad de su tienda.
+
+## ¿Qué cambió?
+
+La API de Checkout ahora también admite validación reCAPTCHA basada en puntuación (equivalente a v3), adecuado para aplicaciones móviles nativas.
+
+<div class="alert alert-info">
+VTEX está integrado con reCAPTCHA enterprise, que ofrece dos enfoques de validación: checkbox (equivalente a reCAPTCHA v2) y basada en puntuación (equivalente a reCAPTCHA v3). Consulta este artículo sobre <a href="https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#versiones-de-recaptcha">reCAPTCHA en el Checkout de VTEX</a> para aprender qué versión debes usar según las características de tu tienda. También puedes obtener más información sobre cada método: <a href="https://developers.google.com/recaptcha/docs/display">reCAPTCHA v2</a> o <a href="https://developers.google.com/recaptcha/docs/v3">reCAPTCHA v3</a> con la documentación proporcionada por Google.
+</div>
+
+Sin embargo, la opción de integración con validación de reCAPTCHA checkbox (equivalente a v2) sigue disponible y es la opción recomendada si deseas implementar una [integración de reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) que no sea en una aplicación móvil nativa.
+
+Actualmente, validación basada en puntuación no está disponible para los storefronts nativos de VTEX - se espera que lo esté en los próximos meses. Esta solución sólo está disponible para las integraciones basadas en la API de Checkout.
+
+## ¿Qué se necesita hacer?
+
+Si utilizas una solución de storefront nativo de VTEX o la integración con reCAPTCHA checkbox a través de la API de Checkout, no es necesario realizar ninguna acción. reCAPTCHA seguirá funcionando de acuerdo con tu configuración.
+
+Si deseas implementar reCAPTCHA en un storefront de aplicación móvil nativa, debes utilizar validación basada en puntuación. Ponte en contacto con tu equipo de desarrolladores y consulta la [guía de integración de reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha).
+
diff --git a/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
index 8f133a2a7..532fe509d 100644
--- a/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
@@ -45,7 +45,7 @@ Para comprobar si los proveedores antifraude configurados en tu tienda permiten
 2. En **Pagos**, haz clic en **Configuración > Afiliaciones de gateway**. 
 3. Al seleccionar el proveedor antifraude escogido, comprueba si la opción **Campo de documento del titular de la tarjeta** está disponible en la pantalla de configuración.
 
-![campo de documento del titular de la tarjeta](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/d826f02dac101b0385119f52685fb846/campo_de_documento_del_titular_de_la_tarjeta.png)
+![campo de documento del titular de la tarjeta](//images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/d826f02dac101b0385119f52685fb846/campo_de_documento_del_titular_de_la_tarjeta.png)
 
 <div class = "alert alert-warning">
   Si la opción <b>Campo de documento del titular de la tarjeta</b> no está disponible en la pantalla de configuración de tu proveedor antifraude, el campo <b>Identificación del titular de la tarjeta</b> seguirá apareciendo en la pantalla del Checkout de la tienda y será obligatorio que el cliente lo rellene.
diff --git a/docs/announcements/es/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md b/docs/announcements/es/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
new file mode 100644
index 000000000..d2f16135f
--- /dev/null
+++ b/docs/announcements/es/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
@@ -0,0 +1,29 @@
+---
+title: 'Transforma en ventas los checkouts abandonados con WhatsApp AI Campaigns'
+id: 4pzBvWuadV753AdCqPhoVS
+status: PUBLISHED
+createdAt: 2024-06-26T11:08:16.663Z
+updatedAt: 2024-06-26T11:27:29.365Z
+publishedAt: 2024-06-26T11:27:29.365Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: transforma-en-ventas-los-checkouts-abandonados-con-whatsapp-ai-campaigns
+locale: es
+legacySlug: transforma-en-ventas-los-checkouts-abandonados-con-whatsapp-ai-campaigns
+announcementImageID: ''
+announcementSynopsisES: 'WhatsApp AI Campaigns impulsa las ventas al recuperar checkouts abandonados.'
+---
+
+Hemos desarrollado una nueva funcionalidad, WhatsApp AI Campaigns, que permite a los retailers enviar automáticamente recordatorios personalizados de WhatsApp a los usuarios que no hayan finalizado sus compras.
+
+Estos recordatorios están diseñados para motivar a los usuarios a volver a la página de checkout y completar sus transacciones, mejorando así la experiencia de compra e impulsando las ventas.
+
+La nueva funcionalidad WhatsApp AI Campaigns ofrece las siguientes mejoras:
+- **Personalización de mensajes:** envío de mensajes personalizados a usuarios que no finalizaron sus compras.
+- **Seguimiento en tiempo real:** permite supervisar el desempeño de la campaña en tiempo real a través del dashboard de VTEX.
+- **Configuración rápida:** activa la funcionalidad sin necesidad de codificación.
+- **Redirección tras expiración:** permite redirigir al usuario al checkout incluso después de que la sesión haya expirado.
+
+## ¿Qué se necesita hacer?
+La funcionalidad ya está disponible para tiendas que utilizan Store Framework y no tienen personalizaciones en Checkout.  Para implementarla en tu tienda, ve a [Recuperar checkouts abandonados con WhatsApp AI Campaigns](https://help.vtex.com/es/tutorial/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns--20i0zLQHt72LKzVEmk1CRZ?&utm_source=autocomplete).
diff --git a/docs/announcements/es/coupon-experience-improvements.md b/docs/announcements/es/coupon-experience-improvements.md
index a1c13cf87..e4b3fcddb 100644
--- a/docs/announcements/es/coupon-experience-improvements.md
+++ b/docs/announcements/es/coupon-experience-improvements.md
@@ -27,7 +27,7 @@ La nueva experiencia de [Cupones](https://help.vtex.com/es/tutorial/cupons-beta-
 
 La nueva [lista de Cupones](https://help.vtex.com/es/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ) muestra todos los cupones registrados en tu tienda, permitiendo gestionar los datos y analizar en qué pedidos se han utilizado.
 
-![listacupons es](https://images.ctfassets.net/alneenqid6w5/2BeCmFJ9bya2SOvx7wQHxC/7e1236597924f6ffd9c2f288884631b6/listacupons_es.gif)
+![listacupons es](//images.ctfassets.net/alneenqid6w5/2BeCmFJ9bya2SOvx7wQHxC/7e1236597924f6ffd9c2f288884631b6/listacupons_es.gif)
 
 ### Acceso más fácil a los códigos de los cupones
 
@@ -44,7 +44,7 @@ Los nuevos filtros permiten la visualización de aquellos cupones que cumplen cr
 - Última modificación
 - Tipo de cupón
 
-![filtroscupons es](https://images.ctfassets.net/alneenqid6w5/5wiejFZZWnKU6ASUP3yk74/6474e893083a2db3a9cfb525b463162d/filtroscupons_es.gif)
+![filtroscupons es](//images.ctfassets.net/alneenqid6w5/5wiejFZZWnKU6ASUP3yk74/6474e893083a2db3a9cfb525b463162d/filtroscupons_es.gif)
 
 ### Grupos de cupones para una gestión ágil
 
diff --git a/docs/announcements/es/custom-selection-of-sellers-for-b2b-purchases.md b/docs/announcements/es/custom-selection-of-sellers-for-b2b-purchases.md
new file mode 100644
index 000000000..d2bf3e711
--- /dev/null
+++ b/docs/announcements/es/custom-selection-of-sellers-for-b2b-purchases.md
@@ -0,0 +1,31 @@
+---
+title: 'Selección personalizada de sellers para compras B2B'
+id: 2AezDuup65tH3MyBBWDasG
+status: PUBLISHED
+createdAt: 2023-12-21T13:29:04.048Z
+updatedAt: 2023-12-21T18:13:37.674Z
+publishedAt: 2023-12-21T18:13:37.674Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: seleccion-personalizada-de-sellers-para-compras-b2b
+locale: es
+legacySlug: seleccion-personalizada-de-sellers-para-compras-b2b
+announcementImageID: ''
+announcementSynopsisES: 'Asignación de sellers a las organizaciones permite que estas tengan sus pedidos atendidos por sellers seleccionados.'
+---
+
+VTEX está lanzando una nueva funcionalidad que permite a las organizaciones compradoras (B2B) elegir y seleccionar a un grupo exclusivo de sellers para atender sus pedidos de compra.
+
+## ¿Qué cambió?
+
+A partir de ahora, cada organización compradora podrá determinar los sellers que están autorizados a mostrar sus productos durante el proceso de compra.
+
+## ¿Por qué realizamos este cambio?
+
+Para que el proceso de compra sea más ágil, centralizado y que simplifique el acceso directo de los compradores a los productos de sellers seleccionados.
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción, la funcionalidad ya está disponible para todas las tiendas.
+Para obtener más información sobre cómo crear una nueva asignación de sellers, accede a [Configurar la asignación de sellers a organizaciones compradoras (B2B)](https://help.vtex.com/es/tutorial/configurando-atribuicao-de-sellers-a-organizacoes-compradoras-b2b-xky--3VJtKNbLpVAl71uVdaOqpE).
diff --git a/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md b/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md
index 4be7de4ee..f372691d3 100644
--- a/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md
+++ b/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md
@@ -38,6 +38,6 @@ La configuración es similar al de las demás condiciones especiales de pago.
 
 La principal diferencia es que, después de seleccionar el país y el banco emisor, el administrador de la tienda puede elegir entre las opciones de Card Level que ofrece  la institución financiera elegida.
 
-![comousarcardlevelES.gif?h=250](https://images.ctfassets.net/alneenqid6w5/7GeRvL3w0PW2czAGdnQWRw/e7ed1290e19aea854cb4dda72f501b26/comousarcardlevelES.gif_h_250)
+![comousarcardlevelES.gif?h=250](//images.ctfassets.net/alneenqid6w5/7GeRvL3w0PW2czAGdnQWRw/e7ed1290e19aea854cb4dda72f501b26/comousarcardlevelES.gif_h_250)
 
 Para saber en detalle cómo configurar esta funcionalidad, vea nuestro [artículo sobre Configuración de Condiciones Especiales de Pago](https://help.vtex.com/tutorial/condiciones-especiales--tutorials_456).
diff --git a/docs/announcements/es/discontinuation-of-legacy-payment-connectors.md b/docs/announcements/es/discontinuation-of-legacy-payment-connectors.md
new file mode 100644
index 000000000..a1655d8d8
--- /dev/null
+++ b/docs/announcements/es/discontinuation-of-legacy-payment-connectors.md
@@ -0,0 +1,89 @@
+---
+title: 'Descontinuación de conectores de pago legados'
+id: 11SHyRwcAr4fs46K7PccOr
+status: PUBLISHED
+createdAt: 2024-03-15T10:19:40.450Z
+updatedAt: 2024-04-08T19:55:00.286Z
+publishedAt: 2024-04-08T19:55:00.286Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: descontinuacion-de-conectores-de-pago-legados
+locale: es
+legacySlug: descontinuacion-de-conectores-de-pago-legados
+announcementImageID: ''
+announcementSynopsisES: 'Los conectores de pago legados serán eliminados de la plataforma VTEX'
+---
+
+Como parte del proceso en curso para descontinuar [conectores de pago legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14), la siguiente tabla presenta los conectores legados que serán eliminados de la plataforma VTEX y los nuevos conectores (integrados vía Payment Provider Protocol) ya disponibles para reemplazarlos:
+
+| **Conector legado** | **Nueva versión (Conector PPP)** |
+| :---: | :---: |
+| Adyen | AdyenV3 |
+| Alignet | AlignetV2 |
+| Amex | - |
+| AuthorizeNet/AuthorizeDotNet | - |
+| BanamexInvoice | - |
+| BankInvoiceItau/BankIssuedInvoiceItau | MaxiPagoV4 |
+| BankInvoiceSantander/BankIssuedInvoiceSantander | Egetnet |
+| Bcash | - |
+| BoldCron | - |
+| Bradesco/RegisteredBankInvoiceBradesco | - |
+| Braspag/BraspagV2 | CieloEcommerce |
+| Cielo/CieloV3 | CieloEcommerce |
+| Conductor | - |
+| Credomatic | - |
+| CyberSource | Cybersource IO |
+| Decidir/DecidirV1 | Payway |
+| ERede/E-Rede V2/ERedeRest | Itaú Rede |
+| Evolucard | - |
+| Firstdata | - |
+| IPay88 | - |
+| ItauShopline | MaxiPagoV4 |
+| Koin | Koin-Payments |
+| MaxiPago | MaxiPagoV4 |
+| MeoWallet | - |
+| MercadoPagoV1 | MercadoPagoV2 |
+| MobilPay | - |
+| Moip | YamiSplitMoipV1 |
+| MOLPay | - |
+| Mundipagg/MundipaggFraudPrevention | PagarmeV3 |
+| Nexxpago | - |
+| NPS | - |
+| PagamentoDigital | - |
+| PagBrasil | PagBrasilV2 |
+| PagHiper | PagHiperV2 o PagHiperV3 |
+| PagoEfectivo | PagoEfectivoV2  |
+| PagosNet | - |
+| PagosWeb | - |
+| PagSeguro/PagSeguroDirect | - |
+| PayClub | - |
+| Payme | PayMee |
+| Paymentez | PaymentezV2 |
+| PaymentHub | - |
+| PaymentsOS | PayUv2 |
+| PayPal/PayPalPlus | PayPalV2 |
+| PayU/PayUGlobal | PayUv2 |
+| Payzen | - |
+| Place2Pay/PlaceToPay | PlaceToPayLatam |
+| Rede Pay/RedePay | Itaú Rede |
+| Redecard | Itaú Rede |
+| Redsys/RedsysV2 | - |
+| SafetyPay | SafetyPayV2 |
+| SalesMachine | - |
+| Scopus | - |
+| Sitef/SitefDirectSale/SitefPreauth | ESITEF |
+| Stelo | SteloM1V2 |
+| TNSPay | EvoPayments |
+| TodoPago | - |
+| WebPay/WebPay2P | - |
+| WorldPay | Worldpay-Payments-Via-WPG |
+
+## ¿Qué se necesita hacer?
+
+Si tu tienda utiliza alguno de los conectores legados indicados anteriormente, realiza las acciones específicas relacionadas con cada conector:
+
+- __El conector legado aún no tiene un conector PPP correspondiente disponible__: abre un ticket con el [soporte de VTEX](https://help.vtex.com/es/support) para que el equipo CX responsable de tu cuenta te ayude a verificar qué conectores PPP disponibles se adaptan mejor a tu tipo de operación y se pueden configurar en tu tienda.
+
+- __Conector PPP disponible para reemplazar el conector legado__: ponte en contacto con tu proveedor de pago para obtener más información sobre el proceso de migración y configuración del nuevo conector en tu tienda.
+
diff --git a/docs/announcements/es/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md b/docs/announcements/es/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
new file mode 100644
index 000000000..6bf7d32b4
--- /dev/null
+++ b/docs/announcements/es/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
@@ -0,0 +1,30 @@
+---
+title: 'Nueva funcionalidad permite importar en masa los datos de organizaciones y centros de costo '
+id: 6XwSfF6YYjIiIDoxR3NoDN
+status: PUBLISHED
+createdAt: 2024-04-29T17:36:01.588Z
+updatedAt: 2024-05-21T14:07:17.423Z
+publishedAt: 2024-05-21T14:07:17.423Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: nueva-funcionalidad-permite-importar-en-masa-los-datos-de-organizaciones-y
+locale: es
+legacySlug: nueva-funcionalidad-permite-importar-en-masa-los-datos-de-organizaciones-y
+announcementImageID: ''
+announcementSynopsisES: 'Gestión de organizaciones: importar en masa simplifica la actualización y mantenimiento de los datos'
+---
+
+VTEX ofrece una nueva funcionalidad de importar en masa que simplifica el proceso de actualización y mantenimiento de los datos de las organizaciones compradoras, sus usuarios (miembros) y los centros de costo.
+
+## ¿Qué cambió?
+
+Ahora, las tiendas que utilizan [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite) pueden importar en masa las organizaciones compradoras, centros de costo y miembros utilizando un **archivo XLSX** o mediante la [API de Bulk Import](https://developers.vtex.com/docs/api-reference/buyer-organizations?endpoint=overview). 
+
+## ¿Por qué realizamos este cambio?
+
+Para optimizar la gestión de datos de organizaciones compradoras.
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción. La funcionalidad estará disponible para todas las tiendas que tengan la aplicación B2B Suite instalada.
diff --git a/docs/announcements/es/displaying-pickup-points-on-google-maps.md b/docs/announcements/es/displaying-pickup-points-on-google-maps.md
index 884d668a0..bb2a24557 100644
--- a/docs/announcements/es/displaying-pickup-points-on-google-maps.md
+++ b/docs/announcements/es/displaying-pickup-points-on-google-maps.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Aplicación que lista los Puntos de Recogida y los mues
 
 Una de las funcionalidades más comunes de los sitios web y de las tiendas en línea es poner a disposición mapas que señalan la ubicación de las tiendas físicas. Con la nueva aplicación [Store Locator](https://apps.vtex.com/vtex-store-locator/p#overview), las tiendas desarrolladas con VTEX IO pueden utilizar Google Maps para listar los puntos de recogida registrados en la tienda y mostrarlos como marcadores en un mapa.
 
-![Maps](https://images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
+![Maps](//images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
 
 ## ¿Qué cambió?
 Las tiendas desarrolladas con VTEX IO ahora pueden instalar la aplicación Store Locator y mostrar los puntos de recogida como marcadores en Google Maps.
diff --git a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md
index 2a051f85d..2472589cb 100644
--- a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md
+++ b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'El resumen de la promoción permite revisar su informac
 
 Es posible que se cometan errores al rellenar la información en el momento de configurar una nueva promoción. Para evitar que se activen promociones con información incorrecta, hemos creado el resumen de la promoción. Esta nueva funcionalidad te permite confirmar la configuración de la promoción antes de activarla.
 
-![resumo-promo-ES](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
+![resumo-promo-ES](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
 
 ## ¿Qué cambió?
 Anteriormente, una promoción se activaba automáticamente cuando se guardaba con el status **Activa**. Con el nuevo recurso, puedes ver un resumen de las configuraciones definidas antes de activar una nueva promoción. De este modo, es posible revisar si todos los datos de la promoción son correctos, evitando errores de implementación.
diff --git a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
index eef88f042..e5afe405f 100644
--- a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
+++ b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'El resumen de la promoción permite revisar su informac
 
 Es posible que se cometan errores al rellenar la información en el momento de configurar una nueva promoción. Para evitar que se activen promociones con información incorrecta, hemos creado el resumen de la promoción. Esta nueva funcionalidad te permite confirmar la configuración de la promoción antes de activarla.
 
-![resumo-promo-ES](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
+![resumo-promo-ES](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
 
 ## ¿Qué cambió?
 Anteriormente, una promoción se activaba automáticamente cuando se guardaba con el status **Activa**. Con el nuevo recurso, puedes ver un resumen de las configuraciones definidas antes de activar una nueva promoción. De este modo, es posible revisar si todos los datos de la promoción son correctos, evitando errores de implementación.
diff --git a/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index c232b4bb4..1d5cda1d9 100644
--- a/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -25,7 +25,7 @@ La aplicación está disponible en [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Permite moderar las calificaciones: apruebe las calificaciones de los productos antes de que estén disponibles en la página de producto.
 - Permite que usted configure su tienda para habilitar las calificaciones anónimas.
 
-![Reviews and Ratings - Printscreen](https://images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
+![Reviews and Ratings - Printscreen](//images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
 
 ## ¿Cuáles son los beneficios?
 - Permite que su consumidor compre con más confianza y asertividad basándose en las calificaciones de otros usuarios.
diff --git a/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 1673e18a9..0e6858b92 100644
--- a/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -38,6 +38,6 @@ Para hacer esto es necesario añadir un producto llamado `Order Authorization` a
  6. Elija el tipo de permiso que desea: `Save Configuration`, para permitir al usuario editar y guardar modificaciones, o `View Configuration`, para permitirle la visualización de la página de Autorización de Pedidos.
  7. Haga clic en **Guardar**.
 
-![GIT-OrderAutho.es](https://images.ctfassets.net/alneenqid6w5/405FxMK69Z6aRClIKAqcqb/6879d0b48f435ed7dcc212cd239c62fe/GIT-OrderAutho.es.gif)
+![GIT-OrderAutho.es](//images.ctfassets.net/alneenqid6w5/405FxMK69Z6aRClIKAqcqb/6879d0b48f435ed7dcc212cd239c62fe/GIT-OrderAutho.es.gif)
 
 Después de añadir este nuevo producto a un perfil, asegúrese de que los usuarios deseados están asociados a este perfil de acceso.
diff --git a/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
index 370732d89..32fe90f5d 100644
--- a/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -3,8 +3,8 @@ title: 'Hub de extensiones: amplía tu operación a través del Admin VTEX'
 id: 4FYJCHTttMa0znV1mdHW9w
 status: PUBLISHED
 createdAt: 2023-05-31T22:15:06.695Z
-updatedAt: 2023-06-04T22:02:53.542Z
-publishedAt: 2023-06-04T22:02:53.542Z
+updatedAt: 2023-08-02T14:37:08.083Z
+publishedAt: 2023-08-02T14:37:08.083Z
 contentType: updates
 productTeam: Apps
 author: 4ubliktPJIsvyl1hq91RdK
@@ -17,7 +17,7 @@ announcementSynopsisES: 'La nueva sección del Admin VTEX para encontrar partner
 
 El Hub de extensiones es la nueva sección del Admin VTEX que reúne a desarrolladores, partners y administradores de las tiendas que desean ampliar las funcionalidades de su operación. A través del Hub de extensiones los partners pueden publicar sus extensiones y los administradores de las tiendas pueden verlas, comprarlas, instalarlas y gestionarlas. El Hub de extensiones estará disponible globalmente en todas las tiendas VTEX durante el tercer trimestre de 2023. Si deseas habilitar el Hub de extensiones en tu tienda de forma inmediata, puedes hacer la solicitud [abriendo un ticket con soporte](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-![Extensions Hub GIF](https://images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/ebae6d6f5ef33a29f0037730c2a64cea/Extensions_Hub.gif)
+![Extensions Hub GIF](//images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/ebae6d6f5ef33a29f0037730c2a64cea/Extensions_Hub.gif)
 
 ## ¿Qué cambió?
 
@@ -49,7 +49,7 @@ El [sitio web Partner portal](https://partnerportal.vtex.com/) continuará exist
 
 El Hub de extensiones estará disponible para todas las tiendas a partir del tercer trimestre de 2023. Si deseas habilitar el Hub de extensiones en tu tienda de forma inmediata, puedes realizar la solicitud [abriendo un ticket a nuestro equipo de soporte](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM). A continuación, para empezar a utilizar el Hub de extensiones, solo tendrás que acceder a través del Admin de tu tienda. En el panel lateral izquierdo del Admin VTEX, haz clic en el ícono **Extensiones** y el Hub de extensiones estará visible en la parte superior del menú.
 
-![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
+![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
 
 ## ¿Por qué realizamos este cambio?
 
@@ -60,3 +60,5 @@ Además, renovamos la experiencia de compra de aplicaciones en la **App Store**.
 Por último, nuestro objetivo es reforzar la relación entre los administradores de las tiendas y los partners de VTEX. Así, los administradores de las tiendas que deseen implementar soluciones únicas en sus negocios, pueden ahora encontrar y contactar directamente con partners y desarrolladores a través de la nueva sección, **Partners**, en el Admin VTEX.
 
 Para obtener más información, consulta nuestra [documentación sobre el Hub de extensiones](https://help.vtex.com/es/tracks/hub-de-extensiones--AW7klkYMh557y5IUOgzco).
+
+_\*Información actualizada el 2 de agosto de 2023: la página **Partners** estará disponible en el futuro. Sin embargo, todavía no hay una fecha prevista para su lanzamiento._
diff --git a/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
new file mode 100644
index 000000000..a426afc88
--- /dev/null
+++ b/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -0,0 +1,70 @@
+---
+title: 'FastCheckout: aumenta tu conversión con el nuevo checkout'
+id: 1sOAAmRehyJ1YkzbG4BkE2
+status: PUBLISHED
+createdAt: 2024-04-03T18:54:06.111Z
+updatedAt: 2024-04-23T10:00:03.018Z
+publishedAt: 2024-04-23T10:00:03.018Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: fastcheckout-aumenta-tu-conversion-con-el-nuevo-checkout
+locale: es
+legacySlug: fastcheckout-aumenta-tu-conversion-con-el-nuevo-checkout
+announcementImageID: ''
+announcementSynopsisES: 'FastCheckout: innovación en el checkout para experiencias personalizadas y de alta conversión.'
+---
+
+Con el compromiso continuo de innovar y ofrecer calidad de excelencia a nuestros clientes, VTEX presenta **FastCheckout**, la evolución más reciente de nuestro checkout. La nueva solución permite crear experiencias de checkout personalizadas de alta conversión, que siempre están actualizadas con nuevas funcionalidades.
+
+![fastcheckout](//images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/14df7a3c5d09bdf75b288dd352763515/image.png)
+
+## ¿Qué cambió?
+
+La experiencia anterior de VTEX Checkout estaba desactualizada y no se ajustaba a los estándares de innovación del mercado. Además, toda la personalización dependía de códigos CSS y JavaScript.
+
+Para ofrecer una experiencia más dinámica a nuestros clientes, implementamos importantes mejoras en los siguientes aspectos de VTEX Checkout:
+
+- Experiencia optimizada para conversión basada en investigaciones sobre las mejores experiencias de usuario por [Baymard Institute](https://baymard.com/).
+- Compatibilidad con opciones de omnichannel sofisticadas.
+- Alto desempeño, incluso en carritos con muchos ítems.
+- Diseño y funcionalidades personalizables.
+- Optimización para dispositivos móviles y de escritorio.
+- Actualizaciones constantes para ofrecer una óptima experiencia.
+- Opción de finalizar la compra sin tener que registrarse.
+- Opción de aceptar múltiples cupones de forma predeterminada.
+
+### Personalización sin complicaciones
+
+FastCheckout permite personalizar la experiencia de checkout para adaptarse al contexto y necesidades de los retailers. También se pueden personalizar los siguientes elementos a través del Admin sin necesidad de código:
+
+- Incluir el logotipo de la tienda en el checkout.
+- Personalizar los colores de los botones y menús del checkout.
+- Definir límites de valores para la compra y el carrito.
+- Ocultar o agregar los elementos de **Código promocional**, **Previsión de envío** y **Mostrar   precio de SKU**.
+- Configurar Adobe Analytics y la API de Google Maps.
+- Agregar descripción de texto para mostrar al cliente.
+- Desactivar y activar información de impuestos dentro del **Resumen del pedido**.
+
+También es posible incluir elementos completamente personalizados sin necesidad de conocimientos previos de JavaScript o CSS.
+
+<div class="alert alert-warning">
+  <p>La versión inicial de FastCheckout permite personalizaciones limitadas. Pronto será posible personalizar todo el contenido utilizando los puntos de extensión de la plataforma FastStore.</p>
+</div>
+
+### Nuevo flujo de compra
+
+El nuevo flujo de compra de FastCheckout está diseñado para ser dinámico e intuitivo y ofrecer a tus clientes una experiencia de compra más ágil y simplificada. Los pasos claramente definidos y la navegación intuitiva hacen que el proceso de checkout sea más eficaz.
+
+![GIFCheckout](//images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/4196b4d4a12b04c1561ebe01b4db5323/GIFCheckout.gif)
+
+## ¿Por qué realizamos este cambio?
+
+El nuevo checkout se diseñó con el objetivo de aumentar las conversiones de la tienda y facilitar la personalización de la experiencia de checkout. FastCheckout ofrece una navegación flexible e intuitiva, garantizando una jornada de compra más sencilla.
+
+Facilitamos considerablemente las personalizaciones, que ahora se pueden adaptar a la experiencia del usuario de acuerdo con sus necesidades específicas a través del Admin.
+
+## ¿Qué se necesita hacer?
+
+Para participar del programa early access de FastCheckout, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support). El equipo de VTEX se pondrá en contacto contigo y evaluará si las funcionalidades disponibles en esta primera versión satisfacen tus necesidades. De ser así, se te invitará a unirte a nuestro programa beta y se actualizarán todos los usuarios en la cuenta de tu tienda con la nueva experiencia. No se requiere ninguna configuración adicional.
+
diff --git a/docs/announcements/es/faster-customer-support-with-new-solutions-for-vtex-clients.md b/docs/announcements/es/faster-customer-support-with-new-solutions-for-vtex-clients.md
new file mode 100644
index 000000000..fb59c838a
--- /dev/null
+++ b/docs/announcements/es/faster-customer-support-with-new-solutions-for-vtex-clients.md
@@ -0,0 +1,34 @@
+---
+title: 'Soporte más rápida con nuevas soluciones para soporte de clientes VTEX'
+id: 2ofvmblxC8uksroSiWmna0
+status: PUBLISHED
+createdAt: 2023-06-29T13:08:03.574Z
+updatedAt: 2023-06-29T13:23:21.815Z
+publishedAt: 2023-06-29T13:23:21.815Z
+contentType: updates
+productTeam: Billing
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: soporte-mas-rapida-con-nuevas-soluciones-para-soporte-de-clientes-vtex
+locale: es
+legacySlug: soporte-mas-rapida-con-nuevas-soluciones-para-soporte-de-clientes-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Ahora, tendrás acceso a un chatbot de atención alimentado con un amplio conocimiento de la plataforma.'
+---
+
+Estamos emocionados de presentar la más reciente solución de atención al cliente de VTEX. Ahora, tendrás acceso a un chatbot de atención alimentado con un amplio conocimiento de la plataforma. Con la aplicación de Inteligencia Artificial, disfrutarás de una **atención ágil y sin esperas**, con capacidades conversacionales** adaptadas a tus necesidades**.
+
+### ¿Qué ha cambiado?
+
+Al abrir un [ticket de soporte](https://help.vtex.com/es/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe) de tipo Técnico, tendrás acceso a una nueva pantalla de conversación en tiempo real con el chatbot VTEX, donde podrás resolver todas tus dudas sobre la plataforma. El chatbot ofrece** soporte para varios idiomas **y ha sido **entrenado con toda la base de conocimientos** disponible por VTEX.
+
+A pesar de esta novedad, siempre podrás optar por **continuar el soporte con nuestro equipo de especialistas de Soporte**, siguiendo los Acuerdos de Nivel de Servicio (SLAs) definidos en la [política de atención de tu región](https://help.vtex.com/es/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe).
+
+### Disponibilidad limitada en versión beta
+
+Queremos destacar que esta es una versión beta del servicio, por lo tanto, inicialmente, el chatbot estará disponible solo en regiones seleccionadas.
+
+Puntos importantes a considerar:
+
+- Las conversaciones pueden compartirse con software de terceros para mejorar nuestro servicio.
+- No comparta información que pueda identificar su cuenta, empresa, clientes, empleados o información confidencial de su empresa a través del chat.
+- Estamos comprometidos a mejorar continuamente las respuestas de los bots. Sin embargo, ocasionalmente puede proporcionar información inconsistente. En caso de duda, puedes seguir contando con nuestro Help Center, Developer Portal y llamadas para nuestro soporte.
diff --git a/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md b/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md
index 096cd55b4..12307eab0 100644
--- a/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md
+++ b/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md
@@ -21,7 +21,7 @@ Ahora es posible crear Tablas de Precios de una manera más intuitiva, práctica
 
 Antes, para crear una tabla de precios era necesario ir hasta el filtro y digitar el nombre de la tabla que se crearía. Ahora, hemos añadido un nuevo campo Tablas de Precios que permite crear y seleccionar la tabla que desea visualizar y trabajar con los precios.
 
-![Annoucement Price Table ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6ORyt5Phgwt65ORLPJbGtU/40e250956718b901dcea414b9e759294/Annoucement_Price_Table_ES.png_h_250)
+![Annoucement Price Table ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6ORyt5Phgwt65ORLPJbGtU/40e250956718b901dcea414b9e759294/Annoucement_Price_Table_ES.png_h_250)
 
 ## Ventajas
 
diff --git a/docs/announcements/es/get-more-agility-managing-your-orders-events-with-feed-v3.md b/docs/announcements/es/get-more-agility-managing-your-orders-events-with-feed-v3.md
index 584145c0f..cb3cdd901 100644
--- a/docs/announcements/es/get-more-agility-managing-your-orders-events-with-feed-v3.md
+++ b/docs/announcements/es/get-more-agility-managing-your-orders-events-with-feed-v3.md
@@ -3,8 +3,8 @@ title: 'Gane más agilidad en la gestión de los eventos de sus pedidos con el F
 id: 49FssyfGcJfvGfrb3JQjVr
 status: PUBLISHED
 createdAt: 2019-02-18T19:55:07.210Z
-updatedAt: 2019-12-31T15:13:12.603Z
-publishedAt: 2019-12-31T15:13:12.603Z
+updatedAt: 2024-01-03T18:00:45.130Z
+publishedAt: 2024-01-03T18:00:45.130Z
 contentType: updates
 productTeam: Post-purchase
 author: 6AcGyun1hSWewU8YcaQiO
@@ -31,4 +31,4 @@ Por seren soluciones independientes y no tratarse de una migración, es posible
 
 ## Que usted necesita hacer
 
-Leya el paso a paso de la configuración del Feed v3 en nuestro tutorial [Feed v3 de Gestión de pedidos](https://help.vtex.com/es/tutorial/feed-v3-de-gestion-de-pedidos)
+Leya el paso a paso de la configuración en [Feed v3](https://developers.vtex.com/docs/guides/orders-feed).
diff --git a/docs/announcements/es/get-to-know-the-new-vtex-status-page.md b/docs/announcements/es/get-to-know-the-new-vtex-status-page.md
new file mode 100644
index 000000000..1d1508b97
--- /dev/null
+++ b/docs/announcements/es/get-to-know-the-new-vtex-status-page.md
@@ -0,0 +1,36 @@
+---
+title: 'Nueva página VTEX Status'
+id: 7n6kl6CftvChNUU1BJFmqw
+status: PUBLISHED
+createdAt: 2023-12-22T13:42:40.056Z
+updatedAt: 2023-12-22T13:57:46.734Z
+publishedAt: 2023-12-22T13:57:46.734Z
+contentType: updates
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: nueva-pagina-vtex-status
+locale: es
+legacySlug: nueva-pagina-vtex-status
+announcementImageID: ''
+announcementSynopsisES: 'We redesigned the VTEX Status page, with more transparency and effective communication about incidents and maintenance.'
+---
+
+Gestionar incidentes es una parte fundamental de la experiencia de los retailers y es importante que ese proceso sea lo más transparente e informativo posible. Con esa necesidad en mente, rediseñamos la página de status de la plataforma ([status.vtex.com](https://status.vtex.com/)) para mejorar la forma en que comunicamos eventos de mantenimiento e incidentes.
+
+## ¿Qué cambió?
+
+Antes, enfrentábamos dificultades a la hora de categorizar los incidentes en solo cuatro componentes: Checkout, WebStore, Administrative Environment e Internal Modules. En algunas situaciones, la categorización general no reflejaba con exactitud el impacto real del incidente. Por ejemplo, un problema con un proveedor de pago podía ser marcado como un incidente en el componente Checkout, lo que resultaba en comunicación inadecuada sobre la verdadera magnitud del problema.
+
+Ahora, tenemos 18 componentes más específicos agrupados en cuatro categorías: Storefront, Checkout, Admin y Developer Tools, enfocados no solo en nuestra arquitectura interna, sino también los puntos donde los retailers pueden observar los síntomas. La siguiente imagen muestra todos los componentes que se incluyen en la nueva página:
+
+![status-page-vtex](//images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/83a6e336c064817e69ed39e85fb83a96/status-page-vtex.png)
+
+Consulta el artículo [Página VTEX Status](https://help.vtex.com/es/tutorial/pagina-vtex-status--gPhqDn9IQ3c67wbJEX3JJ), para más información sobre cada componente.
+
+## ¿Por qué realizamos este cambio?
+
+Actualizamos la página de status de la plataforma para ofrecer una experiencia de comunicación más clara y contextualizada durante y después de incidentes y mantenimientos programados, con el fin de que los retailers entiendan mejor el impacto real a su operación.
+
+## ¿Qué se necesita hacer?
+
+Accede a la nueva página en [status.vtex.com](https://status.vtex.com/) y consulta la guía [Página VTEX Status](https://help.vtex.com/es/tutorial/pagina-vtex-status--gPhqDn9IQ3c67wbJEX3JJ) para más información.
diff --git a/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md b/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
index a14342aac..a7beffbda 100644
--- a/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
+++ b/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
@@ -21,4 +21,4 @@ Como hacemos todos los años, hemos creado una guía con recomendaciones y conse
 
 Disponible para clientes y socios VTEX, usted puede acceder a la guía por la homepage del Admin o directamente por la URL `https://{AccountName}.myvtex.com/admin/blackfriday`. Sólo hay que sustituir `{AccountName}` por el Account Name de su tienda.
 
-![Announcement Cartilha BF - ES](https://images.ctfassets.net/alneenqid6w5/1RSlbXUdcYiAUQSi6S226w/325d5511f9fea08746aa5362ec65a814/Announcement_Cartilha_BF_-_ES.png)
+![Announcement Cartilha BF - ES](//images.ctfassets.net/alneenqid6w5/1RSlbXUdcYiAUQSi6S226w/325d5511f9fea08746aa5362ec65a814/Announcement_Cartilha_BF_-_ES.png)
diff --git a/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md b/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
index 5398d27e1..16982c8d7 100644
--- a/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
+++ b/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
@@ -27,4 +27,4 @@ https://{AccountName}.myvtex.com/admin/shopping-season
 
 Sólo hay que sustituir `{AccountName}` por el Account Name de su tienda, como en la imagen de abajo.
 
-![Shopping Season Guidelines - 2022 - ES](https://images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/f364db4afdea7487e01325f9c455cdcf/Screen_Shot_2022-10-19_at_18.15.02.png)
+![Shopping Season Guidelines - 2022 - ES](//images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/f364db4afdea7487e01325f9c455cdcf/Screen_Shot_2022-10-19_at_18.15.02.png)
diff --git a/docs/announcements/es/google-catalog-migration.md b/docs/announcements/es/google-catalog-migration.md
new file mode 100644
index 000000000..6f5546ea3
--- /dev/null
+++ b/docs/announcements/es/google-catalog-migration.md
@@ -0,0 +1,40 @@
+---
+title: 'Migración del catálogo Google'
+id: 5dwWSG8NVTSXpylGZC67FU
+status: PUBLISHED
+createdAt: 2024-05-22T19:50:50.806Z
+updatedAt: 2024-05-22T20:16:57.592Z
+publishedAt: 2024-05-22T20:16:57.592Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: migracion-del-catalogo-google
+locale: es
+legacySlug: migracion-del-catalogo-google
+announcementImageID: ''
+announcementSynopsisES: 'Realiza la integración con Google Shopping sin perder la relevancia de tus anuncios.'
+---
+
+Desarrollamos la funcionalidad **Migración del catálogo Google** para mapear y realizar match entre los productos del seller en el catálogo de VTEX y los anuncios del seller en Google Shopping.
+
+La funcionalidad está dirigida a sellers que anteriormente integraban los productos de su tienda con Google a través de una plataforma externa a VTEX y ahora realizan la integración a través del [conector Google Shopping](https://help.vtex.com/es/tracks/configurar-integracao-com -o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw) en VTEX.
+
+## ¿Por qué desarrollamos la funcionalidad?
+
+El objetivo de esta funcionalidad es permitir al seller la migración de la relevancia de sus anuncios en Google Shopping. Al llevar a cabo la migración con el conector de VTEX, el seller no pierde el historial de relevancia de sus anuncios.
+
+<div class="alert alert-info">
+La migración del catálogo solo mapea y realiza match entre productos del catálogo VTEX con anuncios existentes en Merchant Center de Google Shopping.
+</div>
+
+## ¿Qué se necesita hacer?
+
+Para realizar la migración es necesario enviar una solicitud al [soporte VTEX](https://help.vtex.com/es/support), pero antes deben cumplirse los dos requisitos siguientes:
+
+1. Crear una nueva política comercial, que no debe contener productos vinculados.
+2. Configurar la integración con Google Shopping, utilizando la nueva política comercial creada en el paso anterior.
+
+Luego, entra en contacto con el soporte de VTEX solicitando la migración. Para recibir respuesta a esta solicitud, considera un plazo de hasta cuatro días laborables.
+
+Una vez completada la migración, debes incluir los SKU que deseas anunciar en Google Shopping en la política comercial registrada en la integración.
+
diff --git a/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md b/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md
new file mode 100644
index 000000000..3969102a8
--- /dev/null
+++ b/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md
@@ -0,0 +1,36 @@
+---
+title: 'Google Pay: nuevo medio de pago en la plataforma VTEX'
+id: 4HWD5UwH4FsjUyOqDcOFiX
+status: PUBLISHED
+createdAt: 2023-06-20T18:18:22.678Z
+updatedAt: 2023-06-28T13:00:03.123Z
+publishedAt: 2023-06-28T13:00:03.123Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: google-pay-nuevo-medio-de-pago-en-la-plataforma-vtex
+locale: es
+legacySlug: google-pay-nuevo-medio-de-pago-en-la-plataforma-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Integración Google Pay en VTEX: checkout rápido y seguro con un solo toque.'
+---
+
+Ahora Google Pay está disponible como medio de pago en las tiendas VTEX. Esta nueva integración nativa permite que los administradores de la tienda proporcionen una experiencia de checkout más rápida y segura a sus clientes.
+
+Google Pay utiliza Tokens en lugar de los números reales de las tarjetas, vinculados al dispositivo del usuario. Esto aumenta las tasas de aprobación y reduce significativamente el fraude. 
+
+Además, cuenta con millones de tarjetas registradas almacenadas de forma segura en Google Wallet, lo que permite realizar pagos con un solo clic en cualquier sitio web o aplicación que ofrezca el botón "Pagar con Google Pay".
+
+## ¿Qué cambió?
+
+Google Pay es una plataforma de cartera digital y un sistema de pagos online desarrollado por Google para permitir las compras en la aplicación y compras con un solo toque para pagar en dispositivos móviles, lo que les permite a los usuarios pagar usando su teléfono, tablet o relojes Android.
+
+Ahora, puedes agregar Google Pay como medio de pago en tu tienda para proporcionar a tus clientes un proceso de checkout más ágil y conveniente.
+
+![google-pay-checkout-es](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/35be7ad3c5e155d0af64fdf42611cc9d/image.png)
+
+## ¿Qué se necesita hacer?
+
+En primer lugar, lea [Google Pay and Wallet APIs Acceptable Use Policy](https://payments.developers.google.com/terms/aup) para comprobar los tipos de productos y servicios que no se pueden utilizar con Google Pay.
+
+Para activar Google Pay como medio de pago en tu tienda, consulta nuestra documentación sobre [Google Pay](https://help.vtex.com/es/tracks/carteira-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/61JMBvM5Vanqj6RaJsP8CT).
diff --git a/docs/announcements/es/google-shopping-new-option-to-submit-prices.md b/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
new file mode 100644
index 000000000..1f9c1600b
--- /dev/null
+++ b/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
@@ -0,0 +1,40 @@
+---
+title: 'Google Shopping: nueva opción de envío de precios'
+id: 4qtyADXxyaUCbOD498K14l
+status: PUBLISHED
+createdAt: 2023-12-13T23:27:59.782Z
+updatedAt: 2023-12-14T13:10:09.812Z
+publishedAt: 2023-12-14T13:10:09.812Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: google-shopping-nueva-opcion-de-envio-de-precios
+locale: es
+legacySlug: google-shopping-nueva-opcion-de-envio-de-precios
+announcementImageID: ''
+announcementSynopsisES: 'Actualiza tu integración: nuevas formas de aplicar descuentos en Google Shopping.'
+---
+
+Hemos actualizado las formas de envío de precios de productos en la [integración con Google Shopping](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) para que los retailers puedan ofrecer anuncios con mayor calidad y descuentos con el [medio de pago](https://help.vtex.com/es/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) que mejor se adapte a las demandas del público de la tienda.
+
+## ¿Qué cambió?
+
+Antes, el registro de la [integración con Google Shopping](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) incluía la opción __Considerar descuento para el pago con boleto al precio enviado__ que ahora ha sido sustituida por __Aplicar descuento al precio enviado.__ La actualización permite que las tiendas VTEX puedan utilizar una de las siguientes dos opciones para configurar el precio enviado a Google Shopping:  
+- __Enviar precio base (para precios con descuento):__ solo muestra los productos registrados con [precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista).  
+- __Aplicar descuento al precio enviado:__ muestra los productos de la tienda VTEX en Google Shopping con el descuento y medio de pago registrados.  
+
+<div class = "alert alert-warning">
+  La configuración <b>Aplicar descuento al precio enviado</b> solo está disponible para tiendas VTEX en Brasil.
+</div>
+
+![envio-de-precos-google-es](//images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/afc4f30ca92f564cb47326e9956b21df/envio-de-precos-google-es.png)
+
+## ¿Qué se necesita hacer?
+
+La actualización estará disponible para todas las [cuentas VTEX que operan como seller](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) a partir del 14 de diciembre de 2023.
+Las cuentas que aún no utilizan la integración con Google Shopping y desean activar la configuración __Enviar precio base (para precios con descuento)__ y __Aplicar descuento al precio enviado__, deben seguir [esta serie de tutoriales](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) para comenzar a utilizar los nuevos ajustes. Las cuentas que ya estén integradas con Google Shopping y tienen la configurada la opción __Considerar descuento para pago con boleto en el precio enviado__ activa, tendrán la opción __Aplicar descuento al precio enviado__ activa después de que se realice la actualización según se muestra en la imagen a continuación:
+
+ ![fluxo-update-news-google-es](//images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/4c8dc610fc35a1ab2dc5d2c820f7fea4/fluxo-update-news-google-es.png)
+
+Consulta la documentación para más información sobre cómo configurar [un descuento vinculado al medio de pago](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/3AqbcsWrge8zLt0BC5CtGd#desconto-vinculado-ao-metodo-de-pagamento) y [un descuento en el conector](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
+
diff --git a/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md b/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md
index 36f60ed18..b69fcbc7e 100644
--- a/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md
+++ b/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md
@@ -16,7 +16,7 @@ announcementSynopsisES: 'Singleton: el tipo de content type en Headless CMS que
 ---
 
 Singleton es un nuevo tipo de content type que permite que el comerciante (administrador de la tienda) pueda crear y gestionar una única página de un content type en el Headless CMS. Los content types de Singleton no pueden duplicarse, lo que garantiza que solo haya una página de ese tipo de contenido y que sea coherente en toda la tienda.
-![singleton-es](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
+![singleton-es](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 El content type Singleton solo está disponible para tiendas que utilicen <a href="https://help.vtex.com/es/tutorial/managing-pages-beta--3DO6rBhZ1p3zndnFu5BgRt">VTEX Headless CMS</a> (Actualmente se encuentra en fase beta).
diff --git a/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md b/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md
new file mode 100644
index 000000000..da063b13c
--- /dev/null
+++ b/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md
@@ -0,0 +1,33 @@
+---
+title: 'Headless CMS: información sobre el status de publicación de la página'
+id: 9G9ILO21L5sGtEVIHFhLr
+status: PUBLISHED
+createdAt: 2023-10-18T12:31:52.699Z
+updatedAt: 2023-10-18T20:56:21.584Z
+publishedAt: 2023-10-18T20:56:21.584Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-informacion-sobre-el-status-de-publicacion-de-la-pagina
+locale: es
+legacySlug: headless-cms-informacion-sobre-el-status-de-publicacion-de-la-pagina
+announcementImageID: ''
+announcementSynopsisES: 'Estado de publicación en Headless CMS se descontinuará a favor del Build Status para seguimiento detallado del deploy.'
+---
+
+A partir del 1 de noviembre de 2023, se descontinuará el estado **Publicando** en las páginas de Headless CMS. En su lugar, puedes realizar un seguimiento del status del deploy de las páginas a través de la herramienta **Build Status**, como [ya habíamos anunciado](https://help.vtex.com/es/announcements/headless-cms-stay-informed-on-your-publication-progress--3ajb4FgE6nmqjblpSEg3SP). Esta herramienta ofrece una vista más detallada del proceso de deploy de tus páginas, manteniendo a los usuarios informados acerca de las fases de compilación (build).
+
+Cuando se crea una nueva página, inicialmente se muestra como **Borrador** en la columna Versiones, lo que indica que aún no se hizo deploy de la página. Una vez que el deploy se ha realizado, el status se actualiza a **Publicado**, lo que significa que el proceso de compilación está listo para comenzar. Una vez completado este proceso, la página pasa a estar disponible para los usuarios finales.
+
+![Build Status - ES](//images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/bab768f8fd499965a4836002ae1bdd6b/publishing-status-es.gif)
+
+## ## ¿Qué cambió?
+El status *Publicando* se utilizaba anteriormente para describir el proceso de deploy de una página CMS en FastStore. Sin embargo, no proporcionaba más detalles sobre el proceso.
+
+Ahora, al integrar la herramienta Build Status con otros sistemas como [Releases](https://help.vtex.com/es/tutorial/planner-releases-page-beta--2p7IiVD6K8i1iRiwHph5sw), WebOps y [FastStore](https ://www.faststore.dev/), Headless CMS proporciona información más completa sobre el status de estos sistemas.
+
+## ¿Por qué realizamos este cambio?
+La implementación de la herramienta Build Status tiene como objetivo mejorar la claridad y la transparencia durante el proceso de deploy.
+
+## ¿Qué se necesita hacer?
+Esta funcionalidad se implementará en Headless CMS a partir del 1 de noviembre de 2023, y no requiere ninguna acción por tu parte.
diff --git a/docs/announcements/es/headless-cms-events-available-in-audit.md b/docs/announcements/es/headless-cms-events-available-in-audit.md
new file mode 100644
index 000000000..0d700c31f
--- /dev/null
+++ b/docs/announcements/es/headless-cms-events-available-in-audit.md
@@ -0,0 +1,47 @@
+---
+title: 'Eventos de Headless CMS disponibles en Audit'
+id: 2WQz4dwteRahTD71hIHNNc
+status: PUBLISHED
+createdAt: 2023-12-08T14:36:53.841Z
+updatedAt: 2023-12-08T14:57:21.295Z
+publishedAt: 2023-12-08T14:57:21.295Z
+contentType: updates
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: eventos-de-headless-cms-disponibles-en-audit
+locale: es
+legacySlug: eventos-de-headless-cms-disponibles-en-audit
+announcementImageID: ''
+announcementSynopsisES: 'Agregamos los eventos de Headless CMS a los logs de Audit.'
+---
+
+[Audit](https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA), el módulo que registra los eventos que ocurren en tu tienda para auditorías futuras, ahora procesa eventos de [Headless CMS](https://help.vtex.com/es/tutorial/gestion-de-paginas--3DO6rBhZ1p3zndnFu5BgRt): la solución VTEX para gestionar contenido web y que ofrece autonomía para crear, editar y publicar contenido a través del Admin VTEX.
+
+## ¿Qué cambió?
+
+Agregamos los eventos de Headless CMS que figuran en la siguiente tabla a los logs de Audit:
+
+| Acción | Descripción | Detalles del evento |
+|---|---|---|
+| TRY_PUBLISHING | Intento de publicar una página. | ID del evento. |
+| TRY_PUBLISH_IN_RELEASE | Intento de publicar un release. | ID del evento. |
+| TRY_UNPUBLISHING | Intento de despublicar una página. | ID del evento. |
+| RESTORE_CONTENT | Restauración de contenido. | ID del evento. |
+| TRY_UPDATING_DRAFT | Intento de actualizar un borrador. | ID del evento. |
+| TRY_UNPUBLISHING_AND_OVERWRITING | Intento de despublicar y sobrescribir una página. | ID del evento. |
+| done.invoke.deleteContent | Eliminación de contenido. | ID del evento. |
+| done.invoke.deleteContentVariant | Eliminación de una versión del contenido. | ID del evento. |
+
+En la columna **Acción**, todos los eventos de Headless CMS también muestran la siguiente información:
+
+* **CONTENT_ID:** código identificador único de contenido.
+* **VARIANT_ID:** código identificador único de la versión del contenido.
+* **WORKSPACE**: workspace en el que se realizó el cambio.
+
+<div class="alert alert-info">
+  <p>Consulta la<a href="https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ"> lista completa de eventos disponibles en Audit</a>.</p>
+</div>
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción. El cambio en Audit ya está activo para todas las cuentas y ya registran la [lista de eventos](#que-cambio) antes mencionados.
diff --git a/docs/announcements/es/headless-cms-new-authorization-requirement.md b/docs/announcements/es/headless-cms-new-authorization-requirement.md
new file mode 100644
index 000000000..8acde1c6a
--- /dev/null
+++ b/docs/announcements/es/headless-cms-new-authorization-requirement.md
@@ -0,0 +1,58 @@
+---
+title: 'Headless CMS: nueva solicitud de autorización'
+id: 7G056zzZmGFBztkRqhpUgj
+status: PUBLISHED
+createdAt: 2024-02-02T12:34:37.766Z
+updatedAt: 2024-02-02T14:14:58.237Z
+publishedAt: 2024-02-02T14:14:58.237Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-nueva-solicitud-de-autorizacion
+locale: es
+legacySlug: headless-cms-nueva-solicitud-de-autorizacion
+announcementImageID: ''
+announcementSynopsisES: 'CMS GraphQL API es obligatorio para la gestión de contenido. Actualiza los roles según corresponda.'
+---
+
+A partir del 15 de febrero, será obligatorio que todos los [usuarios](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) y [claves de aplicación](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) que necesiten acceder a Headless CMS tengan los [recursos](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) de License Manager `See CMS menu on the top-bar` y `Settings` agregados a sus [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Para la gestión de contenido en el Headless CMS, también es necesario contar con el [recurso](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `CMS GraphQL API`. Este requisito se aplica a la API de Headless CMS y al Admin VTEX.
+
+## ¿Qué cambió?
+Anteriormente, los usuarios y las claves de aplicación podían gestionar el contenido de la tienda en Headless CMS
+ sin tener un recurso específico de License Manager asociado a su rol.
+
+Ahora, cualquier request vía API de Headless CMS o Admin VTEX autenticará al usuario y verificará si tiene los recursos obligatorios asociados a su rol.  
+Los recursos `See CMS menu on the top-bar` y `Settings` dan acceso a Headless CMS. Para la gestión de contenido, los usuarios también necesitan disponer del recurso `CMS GraphQL API`. Sin este recurso, los usuarios no podrán gestionar contenido en Headless CMS.
+
+## ¿Por qué realizamos este cambio?
+Este cambio tiene como objetivo mejorar la seguridad y simplificar el acceso del usuario a Headless CMS, brindando un entorno más controlado y seguro para gestionar el contenido de la tienda. 
+
+## ¿Qué se necesita hacer?
+Asegúrate de que los usuarios de Headless CMS tienen sus roles asociados a los recursos `CMS GraphQL API`, `See CMS menu on the top-bar` y `Settings`, ya sea [creando un nuevo rol](#crear-un-nuevo-rol) o [editando uno existente](#editar-rol).
+
+<div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 35px">
+  <p>Para gestionar usuarios y roles, tu rol de usuario debe estar asociado al recurso <code>Save access profile</code> del producto <b>License Manager</b> Por ejemplo, <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> es un rol predefinido que tiene asociado el recurso <code>Save access profile</code>.</p>
+
+</div>
+
+### Crear un rol
+
+Si aún no has creado un rol específico para los usuarios de Headless CMS y deseas hacerlo, consulta la guía [Crear un rol] (https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role). Asegúrate de asociar el rol a los recursos `CMS GraphQL API`, `See CMS menu on the top-bar` y `Settings` en la sección **Productos y recursos**.
+
+### Editar rol
+
+Para editar un rol existente para usuarios de Headless CMS, sigue las instrucciones a continuación:
+
+1. Accede al Admin VTEX.
+2. En la barra superior, haz clic en el avatar de tu perfil (marcado por la inicial de tu email) y después en **Configuración de la cuenta > Roles de usuario**.
+3. Haz clic en el **nombre del rol** que los usuarios de Headless CMS tienen asignado.
+
+<div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; margin-bottom: 10px; padding: 15px">
+  <p>Ya que los roles se pueden personalizar, los nombres pueden diferir en función de la configuración de la tienda, y cada tienda puede definir un rol específico para los usuarios de Headless CMS.</p>
+</div>
+
+4. En la página **Editar rol**, ve a la sección **Productos y recursos**.
+5. Selecciona el producto **CMS**.
+6. Después, selecciona los recursos `CMS GraphQL API`, `See CMS menu on the top-bar` y `Settings`.
+7. Haz clic en `Guardar`.
+
diff --git a/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md b/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md
new file mode 100644
index 000000000..e76feb1a0
--- /dev/null
+++ b/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md
@@ -0,0 +1,42 @@
+---
+title: 'Headless CMS: simplifica la creación y gestión de contenidos con Proyectos'
+id: 6pl14hf2E6sNgR9ykCJkj8
+status: PUBLISHED
+createdAt: 2023-11-01T16:39:47.055Z
+updatedAt: 2023-11-16T14:17:47.228Z
+publishedAt: 2023-11-16T14:17:47.228Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-simplifica-la-creacion-y-gestion-de-contenidos-con-proyectos
+locale: es
+legacySlug: headless-cms-simplifica-la-creacion-y-gestion-de-contenidos-con-proyectos
+announcementImageID: ''
+announcementSynopsisES: 'Headless CMS - Administre sus proyectos de manera centralizada y personalizada.'
+---
+
+**Proyectos** es una nueva funcionalidad en Headless CMS que agiliza la gestión de múltiples experiencias digitales, tales como aplicaciones móviles, sitios web y email marketing desde un solo dashboard.
+
+![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/fa66fd00d9a29e3eeb835369c70277d7/projects-two-es-outro.png)
+
+Proyectos te permite personalizar la configuración, contenido y marca de cada proyecto para ajustarlo a públicos u objetivos específicos.
+
+## Qué cambió
+
+Antes, para gestionar diferentes proyectos con distintos públicos o soluciones, en el Admin VTEX había que acceder a **Hub de extensiones** > **Gestión de aplicaciones**** y buscar la aplicación **CMS (alpha)**. Dentro de la aplicación **CMS (alpha)**, había que crear y configurar cada proyecto individualmente.
+
+Ahora, la interfaz **Proyectos** te permite gestionar todos tus proyectos desde un único dashboard centralizado, desde donde puedes cambiar fácilmente de un proyecto a otro para ajustar la configuración, contenido e identidad desde un solo lugar. Esta mejora le aporta adaptabilidad a tu operación y te brinda la oportunidad de atender públicos y objetivos distintos.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
+
+## ¿Por qué realizamos este cambio?
+
+La interfaz **Proyectos** implementa las siguientes mejoras:
+
+- Proceso de gestión de contenidos entre múltiples proyectos simplificado.
+- Centralización de proyectos.
+- Atención efectiva a públicos u objetivos específicos mediante proyectos separados.
+
+## ¿Qué se necesita hacer?
+Esta funcionalidad ya está disponible para todas las cuentas que tienen la aplicación Headless CMS instalada. Consulta la guía [Gestionar proyectos](https://help.vtex.com/es/tutorial/gestionar-proyectos--42IpDFqTVTESH8DCypJMPM) para más información sobre cómo utilizar la funcionalidad.
+
diff --git a/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md b/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md
new file mode 100644
index 000000000..571b10345
--- /dev/null
+++ b/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md
@@ -0,0 +1,45 @@
+---
+title: 'Headless CMS: mantente informado sobre el progreso de tus publicaciones'
+id: 3ajb4FgE6nmqjblpSEg3SP
+status: CHANGED
+createdAt: 2023-08-21T12:33:36.149Z
+updatedAt: 2023-10-04T13:35:38.902Z
+publishedAt: 2023-08-21T15:36:01.683Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-mantente-informado-sobre-el-progreso-de-tus-publicaciones
+locale: es
+legacySlug: headless-cms-mantente-informado-sobre-el-progreso-de-tus-publicaciones
+announcementImageID: ''
+announcementSynopsisES: 'Mantente informado sobre las etapas de publicación de Headless CMS e identifica rápidamente errores de publicación.'
+---
+
+Headless CMS ofrece ahora una funcionalidad de notificaciones que te mantiene informado durante cada etapa del proceso de publicación. Las nuevas notificaciones proporcionan actualizaciones sobre cada etapa de las publicaciones en el VTEX Headless CMS, manteniendo a los usuarios informados acerca de las fases de compilación (build) de las publicaciones en Releases, VTEX Headless CMS y FastStore. 
+
+![Headless CMS - Notificaciones](//images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/1da7e60b1ebb7b74b67140a0832581a4/headless-cms-publish-es.gif)
+
+Esta funcionalidad también te ayuda a identificar y notificar errores durante el deploy, indicando la etapa exacta en la que se produjo el error. También ofrece la opción de reintentar los deploys si es necesario.
+
+## ¿Qué cambió?
+Antes, cuando una publicación no se producía, era difícil determinar el origen del problema, lo que dificultaba hacer debug y notificarlo, además de retrasar el lanzamiento de las campañas.
+
+Con la funcionalidad de notificaciones, ahora puedes mantenerte informado sobre el status de cada fase del deploy:
+
+| Status                                  | Descripción                                           |
+| --------------------------------------- | ----------------------------------------------------- |
+| **Publicación iniciada**                | El CMS comenzó a publicar el release.                 |
+| **Compilar**                            | El proceso de implementar los cambios del release en producción. |
+| **Actualizar status de los documentos** | Actualiza todas las páginas incluidas en el release. |
+| **Cerrar release**      | Actualiza el status del release.   |
+
+Si se produce un error durante el deploy, el mensaje de la notificación indicará en qué etapa ocurrió. Puedes hacer clic en `Reintentar` para repetir el deploy.
+
+![Headless CMS - Novo deploy](//images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/5f9ba3184bd15234a1a4a0d4a09a78c3/headless-cms-redeploy-es.gif)
+
+## ¿Por qué realizamos este cambio?
+La funcionalidad de notificaciones te da más autonomía para comprender y abordar los problemas relacionados con las publicaciones de tu tienda, permitiendo identificar e informar con precisión los problemas y reintentar el proceso de publicación.
+
+## ¿Qué se necesita hacer?
+Esta funcionalidad ya se encuentra implementada en Headless CMS, y no se requiere ninguna acción por tu parte.
+
diff --git a/docs/announcements/es/headless-cms-updated-user-permissions.md b/docs/announcements/es/headless-cms-updated-user-permissions.md
new file mode 100644
index 000000000..25d28a367
--- /dev/null
+++ b/docs/announcements/es/headless-cms-updated-user-permissions.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 6EvqWHQ2akp2dpdjChGJcy
+status: DRAFT
+createdAt: 2024-01-11T18:15:47.624Z
+updatedAt: 2024-01-11T18:21:20.966Z
+publishedAt: 
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: untitled-entry-2024-01-11-at-18-15-47
+locale: es
+legacySlug: untitled-entry-2024-01-11-at-18-15-47
+announcementImageID: ''
+announcementSynopsisES: ''
+---
+
+
diff --git a/docs/announcements/es/improved-security-for-the-customers-first-purchase.md b/docs/announcements/es/improved-security-for-the-customers-first-purchase.md
index 088d6abaf..e78e22309 100644
--- a/docs/announcements/es/improved-security-for-the-customers-first-purchase.md
+++ b/docs/announcements/es/improved-security-for-the-customers-first-purchase.md
@@ -1,9 +1,9 @@
 ---
 title: 'Mejora de seguridad en la primera compra del cliente'
-id: DKlfRaMNHxgQhUT5VqRrK
+id: 3RBko0KXi8eOm4nKARgReD
 status: DRAFT
-createdAt: 2023-04-28T12:35:44.503Z
-updatedAt: 2023-06-09T15:37:43.651Z
+createdAt: 2023-07-03T11:34:49.078Z
+updatedAt: 2023-10-09T14:12:03.607Z
 publishedAt: 
 contentType: updates
 productTeam: Shopping
@@ -21,7 +21,7 @@ Con el fin de aumentar la seguridad de la información de tu tienda, VTEX ha int
 
 Antes, durante la primera compra, la información personal del cliente se mostraba en el carrito sin enmascaramiento de datos, ya que aún no tiene un perfil creado en la tienda.
 
-Ahora, durante la creación de un nuevo carrito, además de la cookie `checkout.vtex.com` que contiene el orderFormId, se enviará una nueva cookie (`CheckoutOrderFormOwnership`). Esto permitirá que solo el cliente que creó el carrito tenga acceso ilimitado a su información.
+Ahora, durante la creación de un nuevo carrito, además de la cookie `checkout.vtex.com` que contiene el `orderFormId`, se enviará una nueva cookie (`CheckoutOrderFormOwnership`). Esto permitirá que solo el cliente que creó el carrito tenga acceso ilimitado a su información.
 
 Si se produce un intento externo de acceder a los datos del carrito, no se podrá ver la información personal del cliente, ya que sus datos aparecerán enmascarados.
 
diff --git a/docs/announcements/es/improvement-of-discount-price-viewing-experience.md b/docs/announcements/es/improvement-of-discount-price-viewing-experience.md
index 1655007d7..8629806e4 100644
--- a/docs/announcements/es/improvement-of-discount-price-viewing-experience.md
+++ b/docs/announcements/es/improvement-of-discount-price-viewing-experience.md
@@ -24,16 +24,16 @@ Antes de este cambio, podían producirse errores de visualización en el resumen
 Considere, por ejemplo, un usuario que ve un producto que cuesta  US$ 600, con un descuento del 10% pagando al contado. La persona continúa para el checkout y llega a la página de resumen del pedido, donde debe seleccionar las opciones de pago. Estos son los tres principales errores que pueden producirse:
 
 - El usuario aún no ha seleccionado un número de cuotas y el precio se muestra sin descuentos, incluso en la opción elegible.
-![O usuário ainda não selecionou um número de parcelas](https://images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
+![O usuário ainda não selecionou um número de parcelas](//images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
 
 - El cliente ha seleccionado un número de cuotas no elegibles para el descuento, y el precio se muestra solo sin descuentos, incluso en la opción elegible para el descuento.
-![O usuário selecionou um número de parcelas não elegível para desconto](https://images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
+![O usuário selecionou um número de parcelas não elegível para desconto](//images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
 
 - El usuario seleccionó un número de cuotas válido para aplicar el descuento y el descuento se muestra incluso en las opciones no elegibles.
-![O usuário selecionou um número de parcelas elegível para desconto (à vista)](https://images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
+![O usuário selecionou um número de parcelas elegível para desconto (à vista)](//images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
 
 Con este cambio, el descuento se mostrará siempre solo en las opciones de pago en cuotas  elegibles.
-![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](https://images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
+![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](//images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
 
 ## ¿Por qué realizamos este cambio?  
 
diff --git a/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md b/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md
index b5f2a2685..b7bbab219 100644
--- a/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md
+++ b/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md
@@ -25,7 +25,7 @@ En VTEX, puedes cambiar el precio varias veces al día según la estrategia de t
 
 El registro con una plantilla se realiza en dos etapas: exportación e importación. Se ha mejorado la experiencia de exportación de precios con nuevas funcionalidades para dar más visibilidad al usuario del status de cada plantilla de exportación de precios.
 
-![exportacao es](https://images.ctfassets.net/alneenqid6w5/2w6DG43n73r48D3pM6OmXa/0f70f35ceb6f562f16f40346e4e046cb/exportacao_es.gif)
+![exportacao es](//images.ctfassets.net/alneenqid6w5/2w6DG43n73r48D3pM6OmXa/0f70f35ceb6f562f16f40346e4e046cb/exportacao_es.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md b/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md
new file mode 100644
index 000000000..56a1d90cf
--- /dev/null
+++ b/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md
@@ -0,0 +1,44 @@
+---
+title: 'Optimización de la búsqueda unificada de VTEX Sales App'
+id: 4ZfzuvJjgtfjNR3UXrggYN
+status: PUBLISHED
+createdAt: 2024-05-03T12:45:14.073Z
+updatedAt: 2024-05-06T13:37:06.301Z
+publishedAt: 2024-05-06T13:37:06.301Z
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: optimizacion-de-la-busqueda-unificada-de-vtex-sales-app
+locale: es
+legacySlug: optimizacion-de-la-busqueda-unificada-de-vtex-sales-app
+announcementImageID: ''
+announcementSynopsisES: 'Optimización de la búsqueda unificada en VTEX Sales App mejora la experiencia del usuario al navegar y buscar productos.'
+---
+
+Hemos mejorado la búsqueda unificada de VTEX Sales App con el fin de optimizar la experiencia del usuario al navegar y buscar productos.
+
+Esta mejora permite a los vendedores buscar productos más allá del stock de la tienda y agregarlos al carrito. Solo tienen que hacer clic en el ícono de lupa <i class="fas fa-search"></i> e ingresar el nombre de producto, código de referencia, ID de SKU o EAN en la barra de búsqueda de la página de inicio de la tienda.
+
+## ¿Qué cambió?
+
+Los cambios optimizan la experiencia de búsqueda y compra:
+
+- **Lista de búsqueda intuitiva:** acceso a una lista de búsqueda intuitiva e informativa que proporciona una vista simplificada de las búsquedas pasadas.
+
+- **Vista detallada de los productos:** espacio optimizado para que se puedan ver más ítems con imágenes más grandes y de mejor calidad. Al agregar productos al carrito, especialmente aquellos que tengan un SKU único, el proceso es más directo y simplificado.
+
+- **Ajuste de la búsqueda con filtros:** se pueden aplicar filtros al hacer clic en los filtros predefinidos sin tener que enviar el formulario con el botón `Aplicar filtros`. Además, los filtros aplicados se mostrarán en la parte superior de la página para que sea más fácil saber los filtros que están en uso y removerlos fácilmente.
+
+- **Vista rápida de productos no disponibles:** antes, el sistema mostraba todos los productos como no disponibles y, después de algunos minutos, cargaba la disponibilidad de forma correcta. Ahora, la disponibilidad del producto se muestra inmediatamente al cargarse.
+
+- **Optimización para conexiones lentas:** gracias al uso de la caché del navegador, la búsqueda solo devolverá nueva información cuando sea necesario, garantizando una respuesta rápida aun cuando la conexión de internet esté lenta.
+
+![Mobile - ES](//images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/095d38f345e181216351f7560a65d914/mobile__1_.gif)
+
+## ¿Por qué realizamos este cambio?
+
+Hemos desarrollado esta mejora principalmente para los vendedores de tiendas físicas con el objetivo de optimizar su experiencia al navegar y buscar productos. proporcionando una jornada de búsqueda más intuitiva e informativa.
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción; la funcionalidad se aplicará automáticamente en todas las tiendas VTEX que utilizan VTEX Sales App. Para más información, accede al artículo [Búsqueda unificada en VTEX Sales App](https://help.vtex.com/es/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/9sXeVwoD60qYYgRJ11r5F). 
diff --git a/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md b/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md
index f44814875..eda387408 100644
--- a/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md
+++ b/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md
@@ -22,7 +22,7 @@ Esta herramienta permite el control de las aprobaciones de pedidos con cambios e
 ## Lo que cambia
 Ahora, en lugar de abrir un ticket directamente con el soporte, es posible configurar las reglas de autorización por el administrador. Para ello, acceda al camino: Menú - Gestión de Pedidos - Autorización de Pedidos.
 
-![ESAutorizacaoPedidosPrint.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/445WPSN6h0ELYf07ZlPg0M/e0fd3a929af7ed9b1c23f03826e43271/ESAutorizacaoPedidosPrint.PNG_h_250)
+![ESAutorizacaoPedidosPrint.PNG?h=250](//images.ctfassets.net/alneenqid6w5/445WPSN6h0ELYf07ZlPg0M/e0fd3a929af7ed9b1c23f03826e43271/ESAutorizacaoPedidosPrint.PNG_h_250)
 
 ## Qué necesitas hacer
 Es importante mencionar que la tienda no perderá las reglas anteriores, que se hicieron abriendo un ticket al equipo de soporte. Se actualizarán automáticamente en la nueva pantalla.
diff --git a/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
index 465183b69..590b937ac 100644
--- a/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
@@ -19,7 +19,7 @@ A partir del 31 de mayo, estamos lanzando para todas las tiendas VTEX la versió
 
 Las páginas de la **Estrategia de envío** fueran actualizadas al nuevo _VTEX design system_, como se puede ver a continuación:
 
-![nova_estrategia_envio_announcement_boards_ES](https://images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/6ec635cd52cd33a2845fed3d1b444ba6/nova_estrategia_envio_announcement_boards_ES.png)
+![nova_estrategia_envio_announcement_boards_ES](//images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/6ec635cd52cd33a2845fed3d1b444ba6/nova_estrategia_envio_announcement_boards_ES.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/introducing-vtex-ad-network-beta.md b/docs/announcements/es/introducing-vtex-ad-network-beta.md
new file mode 100644
index 000000000..a0238d6c1
--- /dev/null
+++ b/docs/announcements/es/introducing-vtex-ad-network-beta.md
@@ -0,0 +1,49 @@
+---
+title: 'Presentamos VTEX Ad Network (Beta)'
+id: 5Xk8ekbP2Vb5QoI8GXRsQ6
+status: DRAFT
+createdAt: 2024-04-30T16:15:57.595Z
+updatedAt: 2024-04-30T17:41:55.796Z
+publishedAt: 
+contentType: updates
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: presentamos-vtex-ad-network-beta
+locale: es
+legacySlug: presentamos-vtex-ad-network-beta
+announcementImageID: ''
+announcementSynopsisES: 'VTEX lanza una plataforma de anuncios con el propósito de conectar anunciantes y retailers para promocionar productos.'
+---
+
+VTEX está lanzando [VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur). Se trata de un producto que conecta retailers interesados en promocionar sus productos con anunciantes. Con esta conexión, anunciantes y retailers pueden impulsar su negocio.
+
+## Anunciantes
+
+Los anunciantes pueden [crear campañas](https://help.vtex.com/es/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse) de anuncios para promocionar productos en los storefronts de los retailers que los venden. De este modo, pueden impulsar ventas y visualizar datos para mejorar la toma de decisiones.
+
+Cuando creas campañas para el producto que promocionas, tu anuncio puede destacarse en múltiples tiendas VTEX que tengan ese producto en su catálogo.
+
+## Retailers
+
+Los retailers pueden ofrecer espacios en sus storefronts para que los anunciantes promocionen sus productos. Estos retailers recibirán un valor por cada clic recibido en anuncios de su tienda.
+
+VTEX seleccionará para tu tienda anuncios de productos que ya estén en tu catálogo, garantizando una jornada de compra fluida y sin interrupciones. Esta selección se realiza basándose en el comportamiento de tus clientes al navegar por tu tienda.
+
+IMAGEM
+
+## ¿Qué se necesita hacer?
+
+Consulta a continuación cómo puedes formar parte de **VTEX Ad Network**, como retailer o como anunciante.
+
+### Retailers
+
+Para disponibilizar espacios para anuncios en tu tienda, instala la aplicación [VTEX Ad Network para retailers]() en tu cuenta VTEX. Para saber más, consulta el artículo [Mostrar anuncios con VTEX Ad Network en tu tienda (Beta)](https://help.vtex.com/es/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA).
+
+<div class="alert alert-danger">
+Por el momento, solamente tiendas desarrolladas con <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> pueden ofrecer espacios para anuncios.
+</div>
+
+### Anunciantes
+
+Cualquier anunciante interesado en promocionar productos que ya se venden en las tiendas VTEX puede anunciarse utilizando **VTEX Ad Network**. Aprende más consultando los artículos [VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) y [Anunciar con VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse).
+
diff --git a/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md b/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
index c6f0b7231..54578577e 100644
--- a/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
+++ b/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
@@ -28,4 +28,4 @@ Al intentar acceder al Admin de una tienda utilizando una dirección de correo e
 
 La seguridad es una de las principales preocupaciones de VTEX, y esto se vuelve aún más importante cuando estamos cerca de grandes eventos como el Black Friday. Esta nueva función ayudará a identificar de donde provienen posibles intentos de acceso no deseados.
 
-![IP Geolocation email - ES](https://images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/7d95bdb689d5af09718c80c7ba077b95/IP_Geolocation_email_-_ES.png)
+![IP Geolocation email - ES](//images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/7d95bdb689d5af09718c80c7ba077b95/IP_Geolocation_email_-_ES.png)
diff --git a/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
new file mode 100644
index 000000000..abdaca421
--- /dev/null
+++ b/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
@@ -0,0 +1,50 @@
+---
+title: 'Lead time: configuración del tiempo de envío a nivel de SKU'
+id: 39Q8TeXaDCbmTXFtwpNXlf
+status: PUBLISHED
+createdAt: 2023-09-22T14:07:20.464Z
+updatedAt: 2023-09-28T17:47:25.398Z
+publishedAt: 2023-09-28T17:47:25.398Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: lead-time-configuracion-del-tiempo-de-envio-a-nivel-de-sku
+locale: es
+legacySlug: lead-time-configuracion-del-tiempo-de-envio-a-nivel-de-sku
+announcementImageID: ''
+announcementSynopsisES: 'Lanzamiento global del lead time, una configuración opcional del tiempo de envío a nivel de SKU.'
+---
+
+VTEX ha puesto a disposición de todas las tiendas el [lead time](https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B), una configuración del tiempo de envío de un SKU en un determinado stock. En otras palabras, puedes definir a nivel de SKU un tiempo de envío adicional en el cálculo de las promesas de envío que se muestran a los clientes en el checkout.
+
+![lead_time_image_total_time_ES](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
+
+El uso del lead time es opcional y, cuando no se configura, el envío de pedidos de la tienda permanece sin cambios. Cabe señalar que las reglas de consolidación del checkout, que calculan el plazo de envío total del pedido tomando en consideración el tiempo más largo de uno de los ítems, se mantienen.
+
+## ¿Qué cambió?
+
+Antes, el [cálculo del envío de pedidos](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) consideraba los periodos configurados en tu estrategia de envío a nivel de:
+
+* [Almacenes](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+* [Muelles](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+* [Políticas de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140)
+
+Ahora, también existe la opción de configurar el tiempo de envío a nivel de SKU, con la nueva columna de lead time en la página [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-inventario--tutorials_139), a la que puedes acceder a través del Admin VTEX > **Catálogo > Stock > Gestión del stock**, como se muestra en la imagen a continuación:
+
+![lead_time_inventory_management_ES](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
+
+<div class="alert alert-warning">
+En el Admin VTEX, el lead time se configura en días, hasta un límite de 365. De manera predeterminada, el contaje se realiza en días laborables, pero puedes configurar tu política de envío para se <a href="https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional">realice en días naturales</a>. Para configurar periodos en horas, minutos y segundos debes utilizar el endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## ¿Por qué realizamos este cambio?
+
+Los principales beneficios de la nueva configuración del lead time son:
+
+* **Mayor flexibilidad en la gestión de stocks**, especialmente útil para negocios con productos personalizables y escenarios de _dropshipping_ (el proveedor envía el producto directamente al cliente).
+* **Ajustes más precisos de los plazos de envío**, lo que facilita la gestión del stock.
+* **Cálculos de promesas de envío más precisos** para los clientes, lo que contribuye a una mejor experiencia de compra.
+
+## ¿Qué se necesita hacer?
+
+La página [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-inventario--tutorials_139) del Admin VTEX se ha actualizado agregando una columna de lead time en todas las tiendas, y no se requiere ninguna acción por tu parte. El uso del nuevo campo es opcional; si no lo configuras, el tiempo de envío de tus pedidos permanecerá sin cambios.
diff --git a/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md b/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md
new file mode 100644
index 000000000..90a944294
--- /dev/null
+++ b/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md
@@ -0,0 +1,123 @@
+---
+title: 'Descontinuación de conectores de pago legados en 2024'
+id: 4R5YIjUu1IWkiOHzXtQU14
+status: PUBLISHED
+createdAt: 2023-10-13T12:52:48.753Z
+updatedAt: 2023-10-17T20:57:39.669Z
+publishedAt: 2023-10-17T20:57:39.669Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: descontinuacion-de-conectores-de-pago-legados-en-2024
+locale: es
+legacySlug: descontinuacion-de-conectores-de-pago-legados-en-2024
+announcementImageID: ''
+announcementSynopsisES: 'En 2024, VTEX discontinuará los conectores de pagos heredados, que no utilizan el Payment Provider Protocol.'
+---
+
+Para integrar los medios de pago en la plataforma VTEX, los proveedores de pago pueden crear conectores de pago utilizando el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) (PPP). Sin embargo, hay varios conectores legados que utilizan versiones anteriores de nuestra arquitectura de integración de pagos, que son menos estables y menos eficaces.
+
+## ¿Qué va a cambiar?
+
+<div class="alert alert-danger">
+Los cambios descritos en este documento no tendrán ninguna repercusión en el Black Friday 2023,  ya que no se aplicarán hasta el primer trimestre de 2024.
+</div>
+
+VTEX está iniciando la descontinuación de estos conectores legados, lo que ocurrirá por etapas:
+
+- **31 de enero de 2024 ** - Bloqueo de la creación de nuevas afiliaciones de gateway utilizando conectores de pago legados. A partir de esta fecha, las tiendas VTEX ya no podrán configurar conexiones con los conectores que serán descontinuados. Todas las reglas de pago ya configuradas seguirán funcionando con normalidad, sin afectar las transacciones.
+- **10 de febrero de 2024** - Fecha límite sugerida para presentar nuevos conectores para su homologación. Si las empresas partners desean desarrollar nuevos conectores utilizando el [PPP](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) para sustituir los conectores legados, sugerimos que los presenten para su homologación antes de esta fecha. De este modo, las tiendas VTEX dispondrán de varias semanas para reconfigurar sus conexiones de pago antes de la descontinuación. Al establecer esta fecha, nuestro objetivo es garantizar el cumplimiento del SLA del [proceso de homologación de conectores de pago en la plataforma VTEX](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+- **31 de marzo de 2024** - Descontinuación definitiva de los conectores que no utilizan [PPP](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). A partir de esta fecha, VTEX bloqueará todas las transacciones de los conectores de pago legados.
+
+### Lista de los conectores de pago legados
+
+Consulta la lista de todos los conectores que serán descontinuados:
+
+- Adyen
+- Alignet
+- Amex
+- AuthorizeNet/AuthorizeDotNet
+- BanamexInvoice
+- BankInvoiceItau/BankIssuedInvoiceItau
+- BankInvoiceSantander/BankIssuedInvoiceSantander
+- Bcash
+- BoldCron
+- Bradesco/RegisteredBankInvoiceBradesco
+- BrasPag/Braspag
+- Cielo/CieloV3
+- Conductor
+- Credomatic
+- CyberSource
+- Decidir/DecidirV1
+- ERede/E-Rede V2/ERedeRest
+- Evolucard
+- Firstdata
+- IPay88
+- ItauShopline
+- Koin
+- MaxiPago
+- MeoWallet
+- MercadoPagoV1
+- MobilPay
+- Moip
+- MOLPay
+- Mundipagg/MundipaggFraudPrevention
+- Nexxpago
+- NPS
+- PagamentoDigital
+- PagBrasil
+- PagHiper
+- PagoEfectivo
+- PagosNet
+- PagosWeb
+- PagSeguro/PagSeguroDirect
+- PayClub
+- Payme
+- Paymentez
+- PaymentHub
+- PaymentsOS
+- PayPal/PayPalPlus
+- PayU/PayUGlobal
+- Payzen
+- Place2Pay/PlaceToPay
+- Rede Pay/RedePay
+- Redecard
+- Redsys/RedsysV2
+- SafetyPay
+- SalesMachine
+- Scopus
+- Sitef/SitefDirectSale/SitefPreauth
+- Stelo
+- TNSPay
+- TodoPago
+- WebPay/WebPay2P
+- WorldPay
+
+## ¿Por qué estamos realizando este cambio?
+
+Los conectores que utilizan el [PPP](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) tienen tasas de autorización más altas que los conectores legados. Por lo tanto, la migración a nuevos conectores tiende a aumentar las ventas de las tiendas VTEX.
+
+Además, muchos conectores legados están desactualizados en términos de tecnología,  por lo que migrar a conectores que usen el [PPP](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) garantiza que las tiendas VTEX utilizarán tecnologías más modernas y estables ofrecidas por VTEX.
+
+## ¿Qué se necesita hacer?
+
+Las acciones necesarias como resultado de este cambio dependen de tu contexto en el ecosistema VTEX. Consulta a continuación qué opción se adapta mejor a tu negocio.
+
+### Responsable de los conectores de pago legados
+
+Si actúas como proveedor de pago responsable de uno o más [conectores que serán descontinuados](#lista-de-los-conectores-de-pago-legados), deberás desarrollar un nuevo conector utilizando el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). De lo contrario, no podrás procesar transacciones a partir de la fecha de descontinuación mencionada anteriormente.
+
+En este caso, te recomendamos que presentes un nuevo conector para homologación antes del 10 de febrero de 2024 para que las tiendas tengan tiempo de reconfigurar sus conexiones de pago antes de la descontinuación. Aquí puedes consultar más información sobre el [proceso de homologación de nuevos conectores de pago](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+
+<div class="alert alert-danger">
+VTEX no puede garantizar que tu nuevo conector de pago esté disponible para administradores de tiendas VTEX antes de la descontinuación oficial si lo presentas para homologación después de esta fecha.
+</div>
+
+Si tienes alguna pregunta sobre este proceso o deseas alinear la información con los administradores de tiendas, ponte en contacto con tu Partner Manager VTEX.
+
+### Tiendas que utilizan conectores de pago legados
+
+Si tu tienda utiliza uno de los [conectores que serán descontinuados](#lista-de-los-conectores-de-pago-legados), deberás configurarlo con el nuevo conector correspondiente a aquel proveedor de pago antes del 31 de marzo de 2024. De lo contrario, no será posible realizar compras en tu tienda utilizando el medio de pago en cuestión.
+
+A lo largo del proceso de descontinuación y migración, puedes ponerte en contacto con tus proveedores de pago para hacer un seguimiento de la evolución y obtener más información sobre el desarrollo de los nuevos conectores.
+
diff --git a/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md b/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md
index 79e85f00d..e3ad15707 100644
--- a/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md
+++ b/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'La aplicación permite a las tiendas transmitir en vivo
 
 La aplicación Live Shopping es responsable por revolucionar su relación con los consumidores: utilícela para realizar transmisiones en vivo en el sitio web de su tienda para promover colecciones de productos, aumentar los índices de venta y mejorar la experiencia de los usuarios de forma simultánea y en tiempo real.
 
-![live-shopping-overviewes](https://images.ctfassets.net/alneenqid6w5/6QNneCank2FRHN1M5pZVF1/db72cb142151c3a0745d07c8025ced0c/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
+![live-shopping-overviewes](//images.ctfassets.net/alneenqid6w5/6QNneCank2FRHN1M5pZVF1/db72cb142151c3a0745d07c8025ced0c/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
 
 La aplicación está disponible en la [VTEX App Store](https://apps.vtex.com/) y todas las tiendas que utilicen VTEX IO y Legado la pueden descargar por un precio de suscripción razonable.
 
@@ -42,7 +42,7 @@ Los controles en el Admin le permiten:
 - establecer una lista de palabras prohibidas que serán bloqueadas en el chat en tiempo real;
 - proponer encuestas y pruebas a sus usuarios.
 
-![live-shopping-event-details-es](https://images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/d6c04ae630f2d812789410ad5e2fe2a7/image4.png)
+![live-shopping-event-details-es](//images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/d6c04ae630f2d812789410ad5e2fe2a7/image4.png)
 
 ## ¿Cuáles son las ventajas?
 
diff --git a/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
new file mode 100644
index 000000000..776d5af38
--- /dev/null
+++ b/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -0,0 +1,40 @@
+---
+title: 'Algoritmo de Luhn para tarjetas de crédito y débito en el checkout'
+id: 22hAb6KVWUitIG9OzFzgi2
+status: PUBLISHED
+createdAt: 2023-09-19T15:43:01.350Z
+updatedAt: 2023-09-19T16:47:51.216Z
+publishedAt: 2023-09-19T16:47:51.216Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: algoritmo-de-luhn-para-tarjetas-de-credito-y-debito-en-el-checkout
+locale: es
+legacySlug: algoritmo-de-luhn-para-tarjetas-de-credito-y-debito-en-el-checkout
+announcementImageID: ''
+announcementSynopsisES: 'Reduce el porcentaje de transacciones rechazadas debido a número de tarjeta inválido'
+---
+
+Ahora VTEX ofrece la validación de números de tarjetas de crédito y débito en el checkout mediante el algoritmo de Luhn.
+
+## ¿Qué cambió?
+
+Antes, cuando un cliente ingresaba el número de tarjeta en el checkout, no era posible saber si el número correspondía a una tarjeta válida. Cuando se producían errores tipográficos o de valor ingresado, la transacción se creaba para luego ser cancelada en la etapa de autorización.
+
+De ahora en adelante, se aplicará el algoritmo de Luhn para garantizar que solo se pueda ingresar un número de tarjeta válido para realizar una compra. Así, se reducirá el porcentaje de transacciones rechazadas debido a la inserción de números de tarjeta inválidos.
+
+Si el cliente ingresa un número incorrecto, se mostrará un mensaje de error en el checkout. En ese caso, el cliente deberá comprobar el número ingresado y corregirlo para continuar con la finalización de la compra.
+
+![algoritmo_luhn_es](//images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/b061baadc25eb3b451af06004a05a9d9/algoritmo_luhn_es.PNG)
+
+## ¿Por qué realizamos este cambio?
+
+El rechazo de una transacción de pago debido a un número de tarjeta inválido puede hacer que el cliente desista de realizar una nueva compra, ya que tendría que corregir el número de la tarjeta. Por lo tanto, el objetivo de esta mejora en la experiencia de compra es aumentar la tasa de conversión de tu tienda.
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción. El algoritmo de Luhn ya está activo en todas las tiendas VTEX.
+
+<div class="alert alert-warning">
+El algoritmo de Luhn no restringe el fraude por ataques con tarjeta. El objetivo específico es comprobar si hay errores tipográficos o del valor ingresado en los números de las tarjetas.
+</div>
diff --git a/docs/announcements/es/marketplace-improvements-on-received-skus.md b/docs/announcements/es/marketplace-improvements-on-received-skus.md
index ce267c7b2..32563e7f6 100644
--- a/docs/announcements/es/marketplace-improvements-on-received-skus.md
+++ b/docs/announcements/es/marketplace-improvements-on-received-skus.md
@@ -29,7 +29,7 @@ No se requiere ninguna configuración para activar esta funcionalidad, se instal
 
 Cabe señalar que esta acción puede ser deshecha. Es posible aprobar un SKU por API REST, si el marketplace quiere recibirlo de nuevo como una sugerencia del seller. Para obtener más información sobre la aprobación de SKUs, acceda a nuestra documentación de API en el Portal del Desarrollador.
 
-![ES SKUs Recebidos Announcement](https://images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/d4b04317dc8e786079db0c7fe8127a4a/ES_SKUs_Recebidos_Announcement.jpg)
+![ES SKUs Recebidos Announcement](//images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/d4b04317dc8e786079db0c7fe8127a4a/ES_SKUs_Recebidos_Announcement.jpg)
 
 ## Configuración de aprobación automática de SKUs
 
diff --git a/docs/announcements/es/marketplace-network-has-been-improved.md b/docs/announcements/es/marketplace-network-has-been-improved.md
index 4301d7340..eb372458c 100644
--- a/docs/announcements/es/marketplace-network-has-been-improved.md
+++ b/docs/announcements/es/marketplace-network-has-been-improved.md
@@ -19,7 +19,7 @@ Uno de los desafíos de los *marketplaces* y *sellers* de nuestro ecosistema es
 
 Hemos rediseñado Marketplace Network para mejorar la experiencia. Además, ya no es necesario descargar la aplicación desde nuestra App Store, se añadió la funcionalidad a todas las tiendas que operan como *sellers* o *marketplaces* de forma automática.
 
-![Marketplace network tour ES](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/27c4fdcd812b730a445b022c7232a5f2/Marketplace_network_tour_ES.gif)
+![Marketplace network tour ES](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/27c4fdcd812b730a445b022c7232a5f2/Marketplace_network_tour_ES.gif)
 
 ## ¿Qué cambió?
 Se hicieron algunos cambios a las páginas de Marketplace Network:
diff --git a/docs/announcements/es/marketplace-new-offer-quality-filters.md b/docs/announcements/es/marketplace-new-offer-quality-filters.md
index adb8a627a..9498dddbc 100644
--- a/docs/announcements/es/marketplace-new-offer-quality-filters.md
+++ b/docs/announcements/es/marketplace-new-offer-quality-filters.md
@@ -21,7 +21,7 @@ Para que los _marketplaces_ tengan más control sobre los criterios de aprobaci
 
 De esta forma, los SKU que se envían al _marketplace_ cumplen los requisitos relevantes para la curación de catálogos. 
 
-![Offer Quality gif](https://images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/5525f637d51f9d9fc5fe29395f58d07f/Offer_Quality_01.gif)
+![Offer Quality gif](//images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/5525f637d51f9d9fc5fe29395f58d07f/Offer_Quality_01.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md b/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md
index e0b69d2c6..d12e070d6 100644
--- a/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md
+++ b/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md
@@ -24,7 +24,7 @@ Antes, para comprobar la información de un SKU recibido, era necesario acceder
 
 La barra contiene imágenes del SKU, precio, nivel de stock y otros atributos del producto, como descripción, especificaciones, códigos e ID. También incluye el porcentaje de equivalencia que el SKU recibió por el [matcher](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) instalado en su tienda. Aún es posible acceder a la página completa de detalles del SKU, haciendo clic en el botón *«Ver página de detalles»*.
 
-![ES Sidebar received](https://images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/fd3306cf276f1f52281fa583a448661a/ES_Sidebar_received.gif)
+![ES Sidebar received](//images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/fd3306cf276f1f52281fa583a448661a/ES_Sidebar_received.gif)
 ## ¿Por qué realizamos este cambio?
 Desarrollamos la barra lateral para brindar más agilidad a su operación y facilitar la catalogación de SKU recibidos, permitiendo:    
 - Acceder a la información necesaria para un SKU sin salir de la lista principal.  
diff --git a/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md b/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md
index 9408140da..471db3684 100644
--- a/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md
+++ b/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Unificamos Marketplace Network y el módulo de Integrac
 
 Para centralizar las oportunidades de conexión entre marketplaces VTEX y marketplaces externos, unificamos las páginas de Integraciones y Marketplace Network, y ahora se denominan __Marketplaces e integraciones__. La actualización estará disponible en todas las cuentas VTEX a partir del 03 de mayo de 2023.   
 
-![Marketplaces e integraciones](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
+![Marketplaces e integraciones](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
 
 ## ¿Qué cambió?  
 
diff --git a/docs/announcements/es/marketplaces-received-skus-beta.md b/docs/announcements/es/marketplaces-received-skus-beta.md
index 5dce4480f..75ceb0644 100644
--- a/docs/announcements/es/marketplaces-received-skus-beta.md
+++ b/docs/announcements/es/marketplaces-received-skus-beta.md
@@ -25,7 +25,7 @@ Esta beta abierta es la primera de una serie de mejoras y actualizaciones de pro
 
 Una de las primeras y principales mejoras es la nueva forma de seleccionar los SKUs en masa - para que pueda aprobarlos o rechazarlos en masa. Alineado con nuestra [Styleguide](https://styleguide.vtex.com/ "Styleguide"), la selección masiva hará que su trabajo sea más rápido y mejor.
 
-![received-skus-bulk](https://images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
+![received-skus-bulk](//images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
 
 
 
@@ -33,13 +33,13 @@ Una de las primeras y principales mejoras es la nueva forma de seleccionar los S
 Uno de los desafíos en la gestión de ítems de múltiples sellers es priorizar su lista de ítems interminable. Para ayudarlo con eso, hemos creado una nueva característica de ordenamiento, donde puede reordenar todos los envíos de acuerdo con el precio y – una de las principales mejoras–  por disponibilidad de inventario. Vea cuántos ítems están disponibles a simple vista, para que pueda aprobar los SKUs que mejor se desempeñarán.
 
 
-![received-skus-ordering](https://images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
+![received-skus-ordering](//images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
 
 
 Esto se extiende a la nueva herramienta de filtrado. Vea y filtre las SKUs por categoría, marca y seller de una manera simple e intuitiva.
 
 
-![received-skus-filtering](https://images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
+![received-skus-filtering](//images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
 
 
 
diff --git a/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md b/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md
new file mode 100644
index 000000000..f25c2a949
--- /dev/null
+++ b/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md
@@ -0,0 +1,53 @@
+---
+title: 'Master Data v1: descontinuación de configuraciones dinámicas'
+id: 4a1FZX8wGeHLcOyMg0egg8
+status: PUBLISHED
+createdAt: 2024-04-17T12:34:11.024Z
+updatedAt: 2024-04-17T12:48:51.570Z
+publishedAt: 2024-04-17T12:48:51.570Z
+contentType: updates
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: master-data-v1-descontinuacion-de-configuraciones-dinamicas
+locale: es
+legacySlug: master-data-v1-descontinuacion-de-configuraciones-dinamicas
+announcementImageID: ''
+announcementSynopsisES: 'El "Campo calculado" y la acción de trigger "Editar el valor del campo” serán descontinuados en Master Data v1.'
+---
+
+El día 17 de junio de 2024 desactivaremos las siguientes configuraciones en Master Data v1: **Campo calculado** y acción de trigger **Editar el valor del campo**.
+
+Estas opciones permitían cambiar los valores de documentos en [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) de forma dinámica, ejecutando código desde un trigger o desde la actualización/creación de un documento.
+
+Para sustituir estas configuraciones, si necesitas actualizar los valores de los campos de forma dinámica, te recomendamos [crear una aplicación que se comunique con Master Data](https://developers.vtex.com/docs/guides/create-master-data-crud-app).
+
+## ¿Qué cambió?
+
+Ambas configuraciones dinámicas se desactivarán en Master Data v1.
+
+Ten en cuenta que tanto los **Campos calculados** como los triggers existentes que utilizan la función **Editar el valor del campo** dejarán de funcionar en la misma fecha. Consulta la sección [¿Qué se necesita hacer?](#que-se-necesita-hacer) para más información sobre cómo ajustarse a estos cambios.
+
+### Campo calculado
+
+El **Campo calculado** era una configuración dentro de los campos de [entidad de datos](https://help.vtex.com/es/tutorial/entidade-de-datos--tutorials_1265) que permitía ejecutar código C# para recalcular el valor del campo cada vez que se insertaba o actualizaba un nuevo documento.
+
+Este tipo de campo, ilustrado a continuación, ya no estará disponible a partir del 17 de junio de 2024. Los campos calculados creados anteriormente dejarán de funcionar en la misma fecha.
+
+![image6](//images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/981d72dc1c1cc713a12f2be8bb4e1658/image6.png)
+
+### Editar el valor del campo
+
+Al configurar acciones de triggers, existía la opción de **Editar el valor del campo**, que permitía agregar código C# para modificar el valor de campos seleccionados en cada ejecución del trigger.
+
+La opción **Editar el valor del campo**, ilustrada a continuación, ya no estará disponible al configurar acciones de triggers a partir del 17 de junio de 2024. Los triggers configurados con esta acción continuarán operativos solo hasta esa fecha.
+
+![image1](//images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/05a36119e4539dec726d1bdea30622d6/image1.png)
+
+## ¿Qué se necesita hacer?
+
+Si necesitas actualizar los valores de campo de Master Data con base en un trigger, recomendamos que te pongas en contacto con tu equipo de desarrolladores para seguir las directrices que se indican a continuación:
+
+* Desarrollar una aplicación en VTEX IO que se comunique con Master Data, siguiendo las directrices de la guía para desarrolladores [Creating a Master Data CRUD app](https://developers.vtex.com/docs/guides/create-master-data-crud-app).
+* Configura un trigger que envíe una solicitud HTTP a la aplicación, siguiendo las instrucciones disponibles en [Crear trigger en Master Data v1](https://help.vtex.com/es/tutorial/criando-trigger-no-master-data--tutorials_1270#enviar-request-http).
+
+Si utilizas el **Campo calculado** o un trigger con la acción **Editar el valor del campo**, sigue el procedimiento anterior antes del 17 de junio de 2024 para que los valores continúen actualizándose dinámicamente incluso después de que estos ajustes se hayan descontinuado en Master Data v1.
diff --git a/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md b/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md
index 4021f0774..5c698e7a0 100644
--- a/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md
+++ b/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md
@@ -19,7 +19,7 @@ Continuando con las mejoras realizadas para la [certificación de Mercado Libre]
 
 En la nueva página **Promociones** de Mercado Libre, puedes gestionar una lista con las diferentes campañas promocionales en la plataforma disponibles para tu tienda.
 
-![Promociones](https://images.ctfassets.net/alneenqid6w5/2drMTXsElqn1iLe0WnVuTa/81ac8a2fea28f3db675cc33ef164ab8c/Promociones.gif)
+![Promociones](//images.ctfassets.net/alneenqid6w5/2drMTXsElqn1iLe0WnVuTa/81ac8a2fea28f3db675cc33ef164ab8c/Promociones.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md b/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
index 8fa857f90..1974e21f2 100644
--- a/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
+++ b/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
@@ -19,14 +19,14 @@ A partir de ahora, su tiendna puede utilizar punto y coma (`;`) para concatenar
 
 Esta feature funciona en los campos de copia (`CC`) y copia oculta (`CCO`), así como la coma ya funcionaba anteriormente. Ahora las dos opciones de concatenación son válidas.
 
-![Message Center bug fix - EN](https://images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
+![Message Center bug fix - EN](//images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
 
 Este cambio simple en el módulo responsable del envío de e-mails transaccionales redujo drásticamente la tasa de errores en comunicaciones con clientes.
 
 El gráfico siguiente muestra la tasa de errores de una tienda antes de implementado el soporte de concatenación con punto y coma. Más del 90% de los correos electrónicos fallaban todos los días.
 
-![Message Center bug fix 2](https://images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
+![Message Center bug fix 2](//images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
 
 Después de implementada la mejora, los errores en el envío de e-mails transaccionales de la misma tienda fueron completamente eliminados, como muestra este otro gráfico:
 
-![Message Center bug fix 3](https://images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
+![Message Center bug fix 3](//images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
diff --git a/docs/announcements/es/multi-currency-gift-card.md b/docs/announcements/es/multi-currency-gift-card.md
new file mode 100644
index 000000000..411a68bb9
--- /dev/null
+++ b/docs/announcements/es/multi-currency-gift-card.md
@@ -0,0 +1,48 @@
+---
+title: 'Tarjeta de regalo multimoneda'
+id: 4FUXWCaQrFHcgjir698onc
+status: PUBLISHED
+createdAt: 2023-07-27T15:01:02.025Z
+updatedAt: 2023-07-27T16:13:02.651Z
+publishedAt: 2023-07-27T16:13:02.651Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: tarjeta-de-regalo-multimoneda
+locale: es
+legacySlug: tarjeta-de-regalo-multimoneda
+announcementImageID: ''
+announcementSynopsisES: 'Configura las tarjetas de regalo de tu tienda en múltiples monedas'
+---
+
+VTEX presenta una nueva funcionalidad de configuración de las tarjetas de regalo que considera las monedas locales utilizadas en tu tienda.
+
+## ¿Qué cambió?
+
+Antes, todas las tarjetas de regalo se creaban sin una moneda específica asignada a su valor. Antes de finalizar la compra, el cliente aplicaba la tarjeta de regalo como uno de los medios de pago en el checkout y el valor se descontaba según la moneda configurada en los productos del carrito.
+
+A partir de ahora, el administrador de la tienda podrá seleccionar en qué moneda se generará la tarjeta de regalo y hacer que solo esté disponible para compras realizadas en esa misma moneda. 
+
+## ¿Por qué realizamos este cambio?
+
+En algunas regiones, como Europa o Estados Unidos, hay tiendas que venden sus productos a más de un país y operan con tablas de precios que utilizan monedas diferentes. Como no tiene lugar ninguna operación de cambio de divisa al utilizar la tarjeta de regalo, el importe del descuento podría ser mayor o menor dependiendo de la moneda aplicada en el carrito en el momento de la compra.
+
+## ¿Qué se necesita hacer?
+
+La asignación de una moneda específica a cada tarjeta de regalo es una funcionalidad opcional. Si no deseas seleccionar en qué moneda debe crearse, la acción será la misma que para las tiendas que utilizan un solo tipo de moneda, donde los descuentos de un determinado valor se aplican sin conversión de moneda.
+
+Para crear una tarjeta de regalo en una moneda concreta, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, accede a **Promociones > Tarjetas de regalo** o escribe **Tarjetas de regalo** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en `Nuevo vale` o `Nuevos vales en masa` (para crear un lote de tarjetas de regalo).
+3. En el campo **Código de moneda**, selecciona la moneda deseada.
+4. Rellena los demás campos para crear la tarjeta de regalo.
+5. Haz clic en `Guardar`.
+
+![Tarjeta de regalo multimoneda](//images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/8908f1e2a6d350ebdbc3ae648aad5eec/GiftCard_Multicurrency_ES_1.PNG)
+
+Las monedas disponibles serán las mismas que las registradas en las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) de cada tienda.
+
+<div class="alert alert-warning">
+La elección de la moneda debe hacerse durante la creación de cada tarjeta de regalo o de un lote de tarjetas de regalo. No es posible cambiar la moneda asignada a una tarjeta de regalo una vez creada.
+</div>
diff --git a/docs/announcements/es/multilanguage-checkout-launch.md b/docs/announcements/es/multilanguage-checkout-launch.md
new file mode 100644
index 000000000..ea12bc449
--- /dev/null
+++ b/docs/announcements/es/multilanguage-checkout-launch.md
@@ -0,0 +1,27 @@
+---
+title: 'Checkout Multilingue: internacionaliza tu tienda'
+id: 6qvNJhChyccFS8mWoESMue
+status: PUBLISHED
+createdAt: 2024-04-22T16:22:22.210Z
+updatedAt: 2024-04-26T15:32:14.356Z
+publishedAt: 2024-04-26T15:32:14.356Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: lanzamiento-checkout-multilingue
+locale: es
+legacySlug: lanzamiento-checkout-multilingue
+announcementImageID: ''
+announcementSynopsisES: 'Explora el nuevo Checkout Multilingue y expande tu tienda globalmente ofreciendo una experiencia de compra localizada.'
+---
+
+Presentamos **Checkout Multilingue**, una nueva funcionalidad diseñada para mejorar la experiencia de compra en tu tienda, independientemente del país. A partir del 29/04/2024, tus clientes podrán disfrutar de una jornada de compra internacionalizada, desde la navegación por el catálogo hasta el proceso de finalización de compra.
+
+## ¿Qué cambió?
+
+Con **Checkout Multilingue**, implementamos una solución completa que traduce automáticamente tu catálogo de productos a los distintos idiomas registrados previamente en la tienda. De esta forma, tus clientes pueden explorar y comprar productos sin barreras linguísticas, garantizando una experiencia de compra más fluida y personalizada. La información del producto se mostrará en el storefront en el mismo idioma durante la navegación y el proceso de checkout. 
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción. La actualización se aplicará automáticamente a todas las tiendas VTEX a partir del 29/04/2024. Si deseas agregar traducciones al catálogo, sigue los pasos especificados en guía [Translating Catalog content](https://developers.vtex.com/docs/guides/catalog-internationalization) para incluirlas en tu catálogo. 
+
diff --git a/docs/announcements/es/my-authentication-section-in-my-account.md b/docs/announcements/es/my-authentication-section-in-my-account.md
index 14b0aa73c..ffe592b5f 100644
--- a/docs/announcements/es/my-authentication-section-in-my-account.md
+++ b/docs/announcements/es/my-authentication-section-in-my-account.md
@@ -25,15 +25,15 @@ Este cambio afectará a todas las tiendas VTEX. Debido a que el cambio interfier
 
 En esta pestaña los usuarios podrán gestionar su contraseña. También es posible gestionar las sesiones de inicio de sesión, lo que permite al usuario cancelar otras sesiones de forma remota. Encontrará más detalles sobre el uso de la pestaña en la sección [Autenticación del artículo Configurar My Account](https://help.vtex.com/es/tutorial/como-funciona-mi-cuenta--2BQ3GiqhqGJTXsWVuio3Xh).
 
-![My Authentication app ES](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
+![My Authentication app ES](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
 
-![My Authentication Session Management ES](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
+![My Authentication Session Management ES](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
 
 El 29 de septiembre también se eliminará el componente de gestión de contraseña del perfil de usuario para evitar duplicidades. Las siguientes imágenes muestran ejemplos de una página de perfil de usuario con y sin el componente de gestión de contraseña.
 
-![My Account with password ES](https://images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/35a836d86b2c5ace5ae163209ef847dc/My_Account_with_password_ES.png)
+![My Account with password ES](//images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/35a836d86b2c5ace5ae163209ef847dc/My_Account_with_password_ES.png)
 
-![My Account no password ES](https://images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/d60f96ecdedda8f48b23be754f3fbfae/My_Account_no_password_ES.png)
+![My Account no password ES](//images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/d60f96ecdedda8f48b23be754f3fbfae/My_Account_no_password_ES.png)
 
 ## ¿Por qué hicimos este cambio?
 
@@ -66,12 +66,12 @@ Para que la pestaña My Authentication sea visible públicamente en su tienda:
 1. En el panel lateral izquierdo del Admin, vaya a la sección **CONFIGURACIÓN DE LA CUENTA**.
 2. Haga clic en **Apps**.
 3. Haga clic en **Mis aplicaciones**.  
-![My apps menu ES](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/0beb96ff4fd9af269359146a2df949be/My_apps_menu_ES.png)
+![My apps menu ES](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/0beb96ff4fd9af269359146a2df949be/My_apps_menu_ES.png)
 4. Vaya a la app **My Account** y haga clic en `Configuración`.  
-![My apps installed ES](https://images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/919435a4bf6e8222afc6a4d91c136ff5/My_apps_installed_ES.png)
+![My apps installed ES](//images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/919435a4bf6e8222afc6a4d91c136ff5/My_apps_installed_ES.png)
 5. En la sección **AUTHENTICATION** de la configuración de la app, marque la casilla `Visible`.
 6. Haga clic en `Guardar`.
-![My Authentication visible setting ES](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/7669ac9d7f583253b032a48b0471fbd7/My_Authentication_visible_setting_ES.png)
+![My Authentication visible setting ES](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/7669ac9d7f583253b032a48b0471fbd7/My_Authentication_visible_setting_ES.png)
 
 También puede acceder directamente a la configuración de la aplicación My Account en el Admin a través de una URL.
 
@@ -80,4 +80,4 @@ También puede acceder directamente a la configuración de la aplicación My Acc
 
 Tras habilitar la visibilidad de la pestaña **Autenticación**, esta aparecerá en el perfil de usuario de la tienda. Cualquier usuario puede acceder a ella desde el panel lateral izquierdo.
 
-![My Authentication app ES](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
+![My Authentication app ES](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
diff --git a/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md b/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
new file mode 100644
index 000000000..5c64eee73
--- /dev/null
+++ b/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
@@ -0,0 +1,44 @@
+---
+title: 'Nuevos gráficos y datos en tiempo real en la página de Vista general (Beta) '
+id: 6yzy7BYw5rPbaH0WdrAHyI
+status: PUBLISHED
+createdAt: 2023-07-12T13:28:42.856Z
+updatedAt: 2023-08-07T15:31:50.283Z
+publishedAt: 2023-08-07T15:31:50.283Z
+contentType: updates
+productTeam: Management
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: nuevos-graficos-y-datos-en-tiempo-real-en-la-pagina-de-vista-general-beta
+locale: es
+legacySlug: nuevos-graficos-y-datos-en-tiempo-real-en-la-pagina-de-vista-general-beta
+announcementImageID: ''
+announcementSynopsisES: 'La página Vista General de tu Admin VTEX ha sido rediseñada y ahora ofrece nuevos gráficos, en tiempo real.'
+---
+
+La página de [Vista general (Beta)](https://help.vtex.com/es/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) de tu Admin VTEX ha sido rediseñada y ahora ofrece nuevos gráficos, métricas y vistas. Estas nuevas funcionalidades proporcionan un seguimiento en tiempo real de tu operación, ofreciendo visibilidad con relación a los indicadores para que tu equipo y tú tengan un rápido feedback sobre las acciones realizadas en la tienda y puedan actuar con prontitud para implementar mejoras. 
+
+![ES Visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/5b97a2cf1346f1c95fc32512c95da972/ES_Visa__o_geral_beta.png)
+
+## ¿Qué cambió?
+
+Hemos actualizado la interfaz y optimizado la actualización de los datos para mejorar los análisis. Los cambios incluyen: 
+
+* **Datos en tiempo real:** los gráficos de la sección Monitoreo se actualizan automáticamente en hasta tres minutos, según la vista. Otras secciones de la página se actualizan cada 15 minutos.  
+* **Gráficos mejorados:** ahora, los gráficos _Ingresos capturados_, _Pedidos capturados_ y _Nuevas sesiones_ se presentan como elementos destacados, con porcentajes de crecimiento o disminución, además del valor absoluto, que sustituyen a los anteriores gráficos de _Análisis de tendencias de pedidos_ y _Categorías con mayores ingresos_. El _Embudo de ventas_ ahora se encuentra dentro de la métrica de _Tasa de conversión_, y para acceder, solo tienes que hacer clic en el ícono de la flecha <i class='fa fa-chevron-down'></i>.   
+* **Cambios en las métricas:** eliminamos las métricas _Productos populares sin stock_ y _Pedidos con pago en autorización_ para destacar las métricas de ingresos y pedidos. Además, hemos incluido la nueva métrica de _Pedidos cancelados_, que se puede ver en el gráfico de _Pedidos capturados_, ya que creemos que esta métrica es un mejor indicador del estado de una operación.   
+* **Nuevas vistas:** alterna entre las vistas `Acumulado` y `Últimas 2 horas` para ajustar la visualización a tus necesidades específicas. La opción _Acumulado_ es ideal para realizar un seguimiento del desempeño general de las acciones implementadas en la tienda, mientras que la opción _Últimas 2 horas_ permite identificar comportamientos inesperados.
+
+## ¿Por qué realizamos este cambio?
+
+Los cambios introducidos en la página Visión general (Beta) tienen como finalidad aportar, a través de los datos, más control a tu operación, garantizando que la tienda funciona según lo esperado. 
+
+Los datos en tiempo real ayudan a tu equipo a analizar los resultados de las campañas y a verificar los posibles impactos negativos en cambios de configuración o en las implementaciones realizadas (*deploys*).  Las métricas destacadas indican si hubo impactos en el número de pedidos, sesiones o conversión de clientes, lo que afecta tanto al estado como al desempeño de tu negocio.   
+
+## ¿Qué se necesita hacer?
+
+La versión actualizada de la página [Vista general (Beta)](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) ya está disponible en el Admin VTEX desde el día 17 de agosto. Para acceder a la página, en el Admin VTEX, haz clic en **Dashboard > Vista general (Beta)**, o escribe _Vista general (Beta)_ en la barra de búsqueda de la parte superior de la página.
+
+El acceso a la página será gratuito durante su periodo en beta, o hasta que VTEX lo decida; sin embargo, es importante tener en cuenta que en el futuro podrían aplicarse tarifas adicionales. 
+
+La página Vista general, actualmente presente en el Admin seguirá estando disponible para su uso y se podrá acceder a ella desde el menú [Dashboards](https://help.vtex.com/es/tutorial/dashboards-overview--1yn2nZUoXtDO3teTEJsCNl) de tu Admin. 
+
diff --git a/docs/announcements/es/new-checkout-settings-for-bot-attack-protection.md b/docs/announcements/es/new-checkout-settings-for-bot-attack-protection.md
new file mode 100644
index 000000000..0a509daaf
--- /dev/null
+++ b/docs/announcements/es/new-checkout-settings-for-bot-attack-protection.md
@@ -0,0 +1,50 @@
+---
+title: 'Nuevas opciones de configuración en el Checkout para protección contra ataques de bots'
+id: 3kA92hues6c2XgRe1uf2Or
+status: DRAFT
+createdAt: 2023-09-11T17:23:20.383Z
+updatedAt: 2024-06-28T18:38:49.327Z
+publishedAt: 
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: nuevas-opciones-de-configuracion-en-el-checkout-para-proteccion-contra
+locale: es
+legacySlug: nuevas-opciones-de-configuracion-en-el-checkout-para-proteccion-contra
+announcementImageID: ''
+announcementSynopsisES: 'Creamos nuevas configuraciones en el Checkout para evitar fraudes y pedidos no autorizados, reforzando la seguridad.'
+---
+
+
+Con el fin de mejorar la seguridad de la información de tu tienda, VTEX ha implementado una nueva configuración en el Checkout, optimizando las defensas contra posibles ataques de software que simulan el comportamiento humano (bots).
+
+## ¿Qué cambió?
+
+Las siguientes opciones de configuración ya se encuentran disponibles:
+
+- [Exigir inicio de sesión al completar una compra](#exigir-inicio-de-sesión-al-completar-una-compra)
+- [Tiempo mínimo entre pedidos](#tiempo-mínimo-entre-pedidos)
+- [Tiempo mínimo de existencia de un carrito para permitir el uso de una nueva tarjeta de crédito](#tiempo-mínimo-de-existencia-de-un-carrito-para-permitir-el-uso-de-una-nueva-tarjeta-de-crédito)
+
+### Exigir inicio de sesión al completar una compra
+
+A través del campo `requiresLoginToPlaceOrder`, permitimos que solamente aquellos clientes que hayan pasado por el proceso de autenticación puedan realizar compras.
+Se exige la autenticación del usuario con el email que proporcionó cuando agregó los productos al carrito.
+Cuando activas este campo, la opción de pagar sin iniciar sesión, denominada [SmartCheckout](https://help.vtex.com/es/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB) permanece desactivada para todos los clientes de la tienda.
+
+### Tiempo mínimo entre pedidos
+
+Utilizando el campo `minimumPurchaseDowntimeSeconds`, puedes establecer el tiempo mínimo que debe esperar un comprador antes de realizar otra compra.
+Esta configuración reduce la probabilidad de que se creen otras cuentas para realizar una compra.
+
+### Tiempo mínimo de existencia de un carrito para permitir el uso de una nueva tarjeta de crédito
+
+A través del campo `cartAgeToUseNewCardSeconds`, se establece un intervalo de tiempo mínimo en el que un carrito de compra debe permanecer activo antes de que se pueda autorizar el uso de una nueva tarjeta de crédito en el mismo.
+Esta configuración reduce la probabilidad de creación de varios carritos simultáneamente y evita que se agreguen nuevas tarjetas de crédito.
+La activación de este campo no afecta a las compras realizadas con tarjetas ya guardadas en la cuenta del cliente.
+
+## ¿Por qué realizamos este cambio?
+Hemos creado las configuraciones con el objetivo de mejorar el nivel de seguridad y evitar tentativas de fraude y pedidos no autorizados, reforzando la seguridad de los administradores de tiendas y aumentando la protección de las cuentas de los clientes.
+
+## ¿Qué se necesita hacer?
+Las nuevas opciones de configuración están disponibles en el endpoint [Update an account's orderForm configuration](https://developers.vtex.com/docs/guides/update-an-account-orderform-configuration). Para obtener más información sobre cómo activar los campos de cada configuración, accede a [New checkout settings for bot attack protection](https://developers.vtex.com/updates/release-notes/2023-09-12-new-checkout-settings-for-bot-attack-protection).
diff --git a/docs/announcements/es/new-documentation-explore-the-technical-aspects-of-the-platform.md b/docs/announcements/es/new-documentation-explore-the-technical-aspects-of-the-platform.md
new file mode 100644
index 000000000..eb2be6b35
--- /dev/null
+++ b/docs/announcements/es/new-documentation-explore-the-technical-aspects-of-the-platform.md
@@ -0,0 +1,40 @@
+---
+title: 'Nueva documentación: explora los aspectos técnicos de la plataforma'
+id: 6cMtwOjX7hawCKAE1XZeWt
+status: PUBLISHED
+createdAt: 2024-06-03T18:05:03.937Z
+updatedAt: 2024-06-05T17:29:34.519Z
+publishedAt: 2024-06-05T17:29:34.519Z
+contentType: updates
+productTeam: VTEX IO
+author: YRJ73j8mt38D5TUleocQB
+slug: nueva-documentacion-explora-los-aspectos-tecnicos-de-la-plataforma
+locale: es
+legacySlug: nueva-documentacion-explora-los-aspectos-tecnicos-de-la-plataforma
+announcementImageID: ''
+announcementSynopsisES: 'Descubre cómo nuestras decisiones de ingeniería pueden impulsar tu negocio en la documentación VTEX Platform Overview.'
+---
+
+Para facilitar el acceso a la información técnica sobre nuestra plataforma, publicamos VTEX Platform Overview, una nueva documentación que describe las principales características de VTEX en un solo lugar de forma clara y objetiva.
+
+## ¿Qué es VTEX Platform Overview?
+
+[**VTEX Platform Overview**](https://developers.vtex.com/docs/guides/vtex-platform-overview) es un nuevo conjunto de artículos que presenta una visión global de nuestra plataforma con enfoque en los aspectos técnicos esenciales para capacitar a tu equipo y maximizar el potencial de tu negocio. El contenido está en inglés en el Developer Portal.
+
+Consulta a continuación un resumen del contenido de cada artículo:
+
+- [**Cloud infrastructure** ](https://developers.vtex.com/docs/guides/cloud-infrastructure): descubre cómo nuestra infraestructura multiinquilino y arquitectura de nube garantizan la escalabilidad, confiabilidad y desempeño de tu negocio.
+
+- [**Security**](https://developers.vtex.com/docs/guides/security): aprende sobre cómo VTEX gestiona la autenticación, controles de acceso, protección contra ataques, respuesta ante incidentes, entre otras medidas y buenas prácticas para proteger tu tienda.
+
+- [**Data privacy**](https://developers.vtex.com/docs/guides/data-privacy): descubre cómo garantizamos el cumplimiento de las normas de privacidad de datos y cómo los recursos de nuestra plataforma pueden ayudar a los retailers y desarrolladores a proteger los datos personales de los compradores.
+
+- [**Composability**](https://developers.vtex.com/docs/guides/composability): conoce cómo el modelo de composable commerce de nuestra plataforma te permite crear soluciones personalizadas que se adaptan a las necesidades de tu negocio y maximizan su eficiencia y escalabilidad.
+
+- [**Store Architecture**](https://developers.vtex.com/docs/guides/store-architecture): explora los modelos de arquitectura de las tiendas VTEX que se adaptan a diferentes modelos de negocio.
+
+- [**Developer experience**](https://developers.vtex.com/docs/guides/developer-experience): aprende sobre las principales herramientas que ofrecemos para impulsar la experiencia de los desarrolladores, que pueden utilizarse tanto en la construcción e implementación de aplicaciones con [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io), como en nuestras soluciones de [storefront](https://developers.vtex.com/docs/guides/getting-started-with-storefront-solutions).
+
+¿Por qué creamos este material?
+
+Creamos este material para facilitar el acceso a la información técnica de la plataforma y promover la confianza, autonomía y agilidad en los procesos relacionados con estos temas.
diff --git a/docs/announcements/es/new-feature-product-feedback-in-the-vtex-admin.md b/docs/announcements/es/new-feature-product-feedback-in-the-vtex-admin.md
new file mode 100644
index 000000000..d0149f436
--- /dev/null
+++ b/docs/announcements/es/new-feature-product-feedback-in-the-vtex-admin.md
@@ -0,0 +1,25 @@
+---
+title: 'Nueva funcionalidad: Feedback de producto en el Admin VTEX'
+id: 4uZsA31friMnSs4kkVMC0w
+status: PUBLISHED
+createdAt: 2024-07-01T11:15:19.350Z
+updatedAt: 2024-07-01T16:01:07.956Z
+publishedAt: 2024-07-01T16:01:07.956Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: nueva-funcionalidad-feedback-de-producto-en-el-admin-vtex
+locale: es
+legacySlug: nueva-funcionalidad-feedback-de-producto-en-el-admin-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Nueva funcionalidad "Feedback de producto" del Admin VTEX permite compartir opinión directamente con nuestro equipo.'
+---
+
+Estamos lanzando una nueva funcionalidad en el Admin VTEX: el botón Dar feedback. 
+Accede al botón Dar feedback para compartir tu experiencia en nuestra plataforma haciendo clic en el Centro de información (ícono de interrogación en la esquina superior derecha de la página).
+
+## ¿Por qué realizamos este cambio?
+El botón Dar feedback permite al equipo de desarrollo de VTEX recibir información de manera eficiente, mejorando la comunicación con nuestros usuarios y permitiéndonos optimizar continuamente nuestros productos y servicios para satisfacer las necesidades de nuestros clientes.
+
+## ¿Qué se necesita hacer?
+No se requiere ninguna acción; la funcionalidad ya está disponible en todas las tiendas. Para más información, consulta el artículo [Admin VTEX: comienza aquí](https://help.vtex.com/es/tutorial/admin-vtex-comece-aqui--531cHtUCUi3puRXNDmKziw).
diff --git a/docs/announcements/es/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md b/docs/announcements/es/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
new file mode 100644
index 000000000..ae32c4074
--- /dev/null
+++ b/docs/announcements/es/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
@@ -0,0 +1,26 @@
+---
+title: 'Nuevas funcionalidades de VTEX Sales App: vitrina por tienda y vitrina de colección'
+id: 2J9rtMQDyY6OdWDdyYWJ3X
+status: PUBLISHED
+createdAt: 2024-06-27T12:29:38.823Z
+updatedAt: 2024-06-28T12:58:10.676Z
+publishedAt: 2024-06-28T12:58:10.676Z
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: nuevas-funcionalidades-de-vtex-sales-app-vitrina-por-tienda-y-vitrina-de
+locale: es
+legacySlug: nuevas-funcionalidades-de-vtex-sales-app-vitrina-por-tienda-y-vitrina-de
+announcementImageID: ''
+announcementSynopsisES: 'Nuevas funcionalidades VTEX: vitrina por tienda y vitrina de colección para optimizar los productos mostrados.'
+---
+
+Hemos agregado dos nuevas funcionalidades en VTEX Sales App: vitrinas por tienda y vitrinas de colección. Estas funcionalidades optimizan los productos mostrados y la experiencia de compra de los clientes de las siguientes maneras:
+- **Vitrina por tienda:** los retailers pueden agregar una página de productos resaltados especificando el ID de la tienda al que se asociará el anuncio en [Master Data](https://developers.vtex.com/docs/guides/master-data-introduction), lo que permite crear vitrinas personalizadas para cada tienda.
+- **Vitrina de colección:** permite controlar una sección de la vitrina mediante una [colección de catálogo](https://help.vtex.com/es/tutorial/criando-colecao-de-produtos--tutorials_244). El retailer puede definir el nombre de la vitrina y el identificador de la colección para facilitar la organización de los productos y resaltar las colecciones ante los clientes.
+
+## ¿Por qué realizamos este cambio?
+Desarrollamos estas funcionalidades para que los retailers puedan crear anuncios y organizar vitrinas con colecciones de productos de forma eficiente.
+
+## ¿Qué se necesita hacer?
+No se requiere ninguna acción. La funcionalidad se aplicará automáticamente en todas las tiendas que utilizan VTEX Sales App. Para más información, accede a [Anuncios de VTEX Sales App](https://help.vtex.com/es/tutorial/anuncios-do-vtex-sales-app--3UtOFwbwD4muz3p72RBPmC#create-an-ad-page).
diff --git a/docs/announcements/es/new-google-and-yahoo-requirements-for-bulk-email-senders.md b/docs/announcements/es/new-google-and-yahoo-requirements-for-bulk-email-senders.md
new file mode 100644
index 000000000..80f282d32
--- /dev/null
+++ b/docs/announcements/es/new-google-and-yahoo-requirements-for-bulk-email-senders.md
@@ -0,0 +1,74 @@
+---
+title: 'Nuevos requisitos de Google y Yahoo para los remitentes de emails en masa'
+id: 4Tb5eIYJVnKHAK2hPHY1uZ
+status: PUBLISHED
+createdAt: 2024-01-25T21:37:28.950Z
+updatedAt: 2024-01-26T00:23:10.235Z
+publishedAt: 2024-01-26T00:23:10.235Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: nuevos-requisitos-de-google-y-yahoo-para-los-remitentes-de-emails-en-masa
+locale: es
+legacySlug: nuevos-requisitos-de-google-y-yahoo-para-los-remitentes-de-emails-en-masa
+announcementImageID: ''
+announcementSynopsisES: 'Nuevos requisitos de Google y Yahoo para remitentes de emails en masa.'
+---
+
+Google y Yahoo están aplicando nuevos requisitos a los remitentes de emails en masa. El objetivo es garantizar una mayor seguridad a los destinatarios, reducir el volumen de spam y ofrecer una mejor experiencia a los usuarios.
+
+A partir de febrero de 2024, según sus [directrices para remitentes de correos](https://support.google.com/a/answer/81126?hl=es&visit_id=638412075303779567-3830782619&rd=1), Google exigirá nuevos requisitos a los remitentes que envíen 5000 o más mensajes al día a cuentas de Gmail. Del mismo modo, Yahoo también ha definido nuevas [prácticas en materia de entregabilidad masiva de emails](https://senders.yahooinc.com/best-practices/). Estas empresas han especificado que deben cumplirse los siguientes requisitos:
+
+* Autenticación de email del remitente.
+* Facilitar la opción de anular la suscripción.
+* Límite para la tasa de emails marcados como spam.
+
+Si los remitentes no siguen estas directrices, existe la posibilidad de que los emails enviados sean rechazados o dirigidos a la carpeta de spam del destinatario.
+
+## ¿Qué cambió?
+
+A partir de febrero de 2024, Google y Yahoo exigirán los siguientes requisitos a los remitentes de emails en masa:
+
+| **Requisitos** | **Descripción** |
+| :--- | :--- |
+| Autenticación de email del remitente | <p>Los remitentes deben autenticar el origen de su email utilizando los siguientes protocolos:</p><p><ul><li><a href="https://support.google.com/a/answer/33786?sjid=4150033421619503412-SA">SPF</a> (Sender Policy Framework)</li><li><a href="https://support.google.com/a/answer/174124?sjid=4150033421619503412-SA">DKIM</a> (DomainKeys Identified Mail)</li><li><a href="https://support.google.com/a/answer/2466580?sjid=4150033421619503412-SA">DMARC</a> (Domain-based Message Authentication, Reporting & Conformance)</li></ul></p><p>Al realizar estos ajustes, te proteges contra el spoofing (emails falsos enviados en nombre de tu dominio) y evitas que tus emails enviados se marquen como spam.</p><p>Más información en <a href="https://support.google.com/a/answer/10583557?hl=es#:~:text=La%20autenticaci%C3%B3n%20tambi%C3%A9n%20ayuda%20a,mensajes%20pueden%20marcarlos%20como%20spam.">Evitar el spam, el spoofing y el phishing con la autenticación de Gmail</a>.</p> |
+| Facilitar la opción de anular la suscripción | <p>Los destinatarios deben tener la opción de darse de baja de tus mensajes con un solo clic, y el procesamiento de dicha baja debe completarse en un plazo de dos días.</p><p>Más información en <a href="https://support.google.com/mail/answer/81126#subscriptions">Suscripciones</a> (Google) y <a href="https://blog.postmaster.yahooinc.com/post/182917670818/dont-want-to-be-marked-as-spam-support-one-click">Support one click unsubscribe</a> (Yahoo).</p> |
+| Límite para tasa de emails marcados como spam | Los destinatarios deben considerar tus emails como deseables, por lo que la tasa de emails marcados como spam debe ser inferior al 0.1% y el remitente debe evitar que alcance o supere el 0.3 %. Esta tasa se refiere al número de emails marcados como spam por los destinatarios, dividido por el número total de emails recibidos.<p>Puedes utilizar <a href="https://support.google.com/mail/answer/14289100">Postmaster Tools</a> para monitorear datos sobre grandes volúmenes de emails de Gmail, y <a href="https://senders.yahooinc.com/complaint-feedback-loop/">Complaint Feedback Loop</a> para el mismo servicio de Yahoo.</p> |
+
+Los requisitos mencionados se consideran básicos en lo que respecta a la gestión de envío de emails. Para más información sobre las prácticas recomendadas de entregabilidad de emails en Google, consulta [Directrices para remitentes de correos](https://support.google.com/a/answer/81126?hl=es&visit_id=638412075303779567-3830782619&rd=1); para consultar contenido en Yahoo, accede a [Email deliverability best practices](https://senders.yahooinc.com/best-practices/).
+
+## ¿Qué se necesita hacer?
+
+Para ser un remitente de emails en masa y cumplir los requisitos de Google y Yahoo, debes:
+
+* [Configurar la autenticación del email del remitente](#configurar-la-autenticacion-del-email-del-remitente)
+* [Facilitar la opción de anular la suscripción a los destinatarios](#facilitar-la-opcion-de-anular-la-suscripcion)
+* [Controlar el límite de la tasa de spam](#controlar-el-limite-de-la-tasa-de-spam)
+
+Si no se siguen estas directrices, existe la posibilidad de que los emails enviados sean rechazados o dirigidos a la carpeta de spam del destinatario. Puedes verificar si cumples con los requisitos de Google utilizando [Postmaster Tools](https://support.google.com/mail/answer/14289100).
+
+### Configurar la autenticación del email del remitente
+
+* Configura la [autenticación SPF](https://support.google.com/a/answer/33786?sjid=4150033421619503412-SA) para tu dominio de envío.
+* Configura la autenticación [DKIM](https://support.google.com/a/answer/174124?sjid=4150033421619503412-SA) para tu dominio de envío.
+* Configura la [autenticación DMARC](https://support.google.com/a/answer/2466580?hl=es#dmarc-setup) para tu dominio de envío (puedes comprobar si tienes un [registro DMARC válido](https://dmarcian.com/dmarc-inspector/)).
+* Define una política DMARC para tu dominio (consulta la [implementación recomendada por Google](https://support.google.com/a/answer/10032473?hl=es)).
+
+### Facilitar la opción de anular la suscripción
+
+* Ofrece a los destinatarios la opción de anular la suscripción de los emails con [un solo clic](https://blog.postmaster.yahooinc.com/post/182917670818/dont-want-to-be-marked-as-spam-support-one-click).
+* Incluye un link visible para cancelar la suscripción en el cuerpo del mensaje.
+* Procesa la solicitud de cancelación en hasta 2 días.
+
+### Controlar el límite de la tasa de spam
+
+* Mantén las tasas de spam por debajo del 0.1 %.
+* Evita alcanzar una tasa de spam igual o superior al 0.3 %.
+* Monitorea las tasas de spam informadas. En Gmail, utiliza [Postmaster Tools](https://gmail.com/postmaster); en Yahoo, [Complaint Feedback Loop](https://senders.yahooinc.com/complaint-feedback-loop/).
+
+## Artículos relacionados
+
+| **VTEX** | **Google** | **Yahoo** |
+| :--- | :--- | :--- |
+| <p><ul><li><a href="https://help.vtex.com/es/tutorial/best-practices-on-spf--42t0lkl2VyC6Yewc4wA6wI">Buenas prácticas de SPF (Sender Policy Framework)</a></li><li><a href="https://developers.vtex.com/docs/guides/setting-up-the-spf">Setting up the SPF</a></li><li><a href="https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails">Setting up DKIM for transactional emails</a></li><li><a href="https://developers.vtex.com/docs/api-reference/message-center-api#post-/api/mail-service/pvt/providers/-EmailProvider-/dkim">Generate DKIM keys</a></li></ul></p> | <p><ul><li><a href="https://support.google.com/a/answer/81126?hl=es&visit_id=638412075303779567-3830782619&rd=1">Directrices para remitentes de correos</a></li><li><a href="https://support.google.com/a/answer/14229414?hl=es-bo">Preguntas frecuentes sobre las directrices para remitentes de correos</a></li><li><a href="https://support.google.com/a/answer/10583557?hl=es#:~:text=La%20autenticaci%C3%B3n%20tambi%C3%A9n%20ayuda%20a,mensajes%20pueden%20marcarlos%20como%20spam">Evitar el spam, el spoofing y el phishing con la autenticación de Gmail</a></li><li><a href="https://blog.google/products/gmail/gmail-security-authentication-spam-protection/">Comunicado de Google</a></li></ul></p> | <p><ul><li><a href="https://senders.yahooinc.com/best-practices/">Best practices - Deliverability</a></li><li><a href="https://senders.yahooinc.com/faqs/">FAQs - Deliverability</a></li><li><a href="https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-less-spam">Comunicado de Yahoo</a></li></ul></p> |
+
diff --git a/docs/announcements/es/new-indexation-history-screen.md b/docs/announcements/es/new-indexation-history-screen.md
index 284984fa7..d965989d3 100644
--- a/docs/announcements/es/new-indexation-history-screen.md
+++ b/docs/announcements/es/new-indexation-history-screen.md
@@ -19,7 +19,7 @@ En toda operación de ecommerce, es necesario registrar o cambiar información d
 
 Para mejorar la experiencia de monitoreo de la indexación del catálogo, rediseñamos la página **Historial de indexación** en el Admin VTEX. La nueva interfaz permite dar seguimiento al tiempo de indexación de los productos y al status de indexación de la tienda.
 
-![Histórico da Indexação 1 - ES](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/new-orders-module-interface-official.md b/docs/announcements/es/new-orders-module-interface-official.md
index 0085564fe..fa9d67c67 100644
--- a/docs/announcements/es/new-orders-module-interface-official.md
+++ b/docs/announcements/es/new-orders-module-interface-official.md
@@ -27,15 +27,15 @@ En comparación con la versión beta, la interfaz que será oficial a partir del
 
 * **Búsqueda de pedidos sin límite de fecha:** se puede buscar pedidos sin límite de fecha y ver todos los pedidos relacionados con el criterio utilizado, independientemente de la fecha de creación del pedido. Esta búsqueda no puede ser asociada a otros filtros. Sin embargo, puedes seleccionar un periodo de búsqueda personalizado de hasta seis meses y combinarlo con los filtros. Aprende más en el artículo [Filtrar pedidos en Todos los pedidos](https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192).
 
-  ![busca_sem_limite_data_all_es](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
+  ![busca_sem_limite_data_all_es](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
 
 * **Diagrama del pedido:** en la sección _Status del pedido_ de la nueva interfaz, de forma predeterminada, se muestra una línea de tiempo con los eventos del pedido. Ahora también puedes ver el _Diagrama del pedido_. Al hacer clic en `Ver diagrama`, se abrirá una ventana modal que muestra una imagen similar a la siguiente:
 
-  ![diagrama_pedido_es](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
+  ![diagrama_pedido_es](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
 
 Si todavía no has utilizado la versión beta, la imagen a continuación muestra la correspondencia de campos entre la versión antigua de la página **Detalles del pedido** y la versión oficial:
 
-![board_comparativo_interface_pedido_v2_es](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
+![board_comparativo_interface_pedido_v2_es](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/new-payment-features-enhancements-for-an-improved-shopping-experience.md b/docs/announcements/es/new-payment-features-enhancements-for-an-improved-shopping-experience.md
index c98546dcf..1c83dc863 100644
--- a/docs/announcements/es/new-payment-features-enhancements-for-an-improved-shopping-experience.md
+++ b/docs/announcements/es/new-payment-features-enhancements-for-an-improved-shopping-experience.md
@@ -3,8 +3,8 @@ title: 'Nuevas funcionalidades de Pagos: mejoras para una experiencia de compra
 id: 3b5C6DabaGrWsS9Jahs75D
 status: PUBLISHED
 createdAt: 2023-05-29T14:05:55.900Z
-updatedAt: 2023-05-29T14:10:59.814Z
-publishedAt: 2023-05-29T14:10:59.814Z
+updatedAt: 2024-04-04T19:35:42.974Z
+publishedAt: 2024-04-04T19:35:42.974Z
 contentType: updates
 productTeam: Shopping
 author: 2o8pvz6z9hvxvhSoKAiZzg
diff --git a/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
new file mode 100644
index 000000000..503d58fa8
--- /dev/null
+++ b/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
@@ -0,0 +1,36 @@
+---
+title: 'Nueva interfaz de gestión de proveedores de pago y antifraude'
+id: Qx6SkUJqM8DwoZajvAP0k
+status: PUBLISHED
+createdAt: 2023-12-22T09:09:05.292Z
+updatedAt: 2024-01-22T20:43:27.828Z
+publishedAt: 2024-01-22T20:43:27.828Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: nueva-interfaz-de-gestion-de-proveedores-de-pago-y-antifraude
+locale: es
+legacySlug: nueva-interfaz-de-gestion-de-proveedores-de-pago-y-antifraude
+announcementImageID: ''
+announcementSynopsisES: 'Accede a la información de proveedores de pago y antifraude más rápidamente'
+---
+
+VTEX está lanzando una nueva interfaz en la página de proveedores de pago y antifraude en el Admin VTEX que ofrece una experiencia más intuitiva y eficiente para tu operación.
+
+## ¿Qué cambió?
+
+Ahora puedes acceder a la información de los proveedores registrados en tu tienda más rápidamente. El nuevo layout ofrece la opción de filtrar los proveedores de pago y antifraude por nombre, tipo y entorno operativo (prueba o producción).
+
+También hemos mejorado la experiencia de navegación de la pantalla que permite agregar, editar y buscar proveedores.
+
+![nueva_interfaz_de_proveedores_de_administración](//images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/48c5d451e15c9ce565047821cb074b03/nueva_interfaz_de_proveedores_de_administraci_n.JPG)
+
+## ¿Qué se necesita hacer?
+
+La nueva página de gestión de proveedores de pago y antifraude ya está disponible automáticamente para todas las cuentas VTEX. Para utilizar la nueva experiencia, en el Admin VTEX accede a __Configuración de la tienda > Pago > Proveedores__.
+
+Para más información sobre las funcionalidades de la nueva interfaz, accede a [Registrar proveedores de pagos y antifraude](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
+
+<div class = "alert alert-warning">
+  La versión anterior de la interfaz de administración de afiliaciones, disponible en <b>Configuración de la tienda > Pago > Configuración > Afiliaciones de Gateway</b>, seguirá siendo accesible hasta el 14 de enero de 2024.
+</div>
diff --git a/docs/announcements/es/new-permission-required-to-manage-redirects-in-store-framework-cms.md b/docs/announcements/es/new-permission-required-to-manage-redirects-in-store-framework-cms.md
new file mode 100644
index 000000000..88aa04fc8
--- /dev/null
+++ b/docs/announcements/es/new-permission-required-to-manage-redirects-in-store-framework-cms.md
@@ -0,0 +1,34 @@
+---
+title: 'Store Framework CMS: nuevo permiso necesario para gestionar redirecciones'
+id: 1GcT48ML2w6TZQxQyGbD6W
+status: PUBLISHED
+createdAt: 2023-08-31T18:10:04.246Z
+updatedAt: 2023-09-05T16:32:32.516Z
+publishedAt: 2023-09-05T16:32:32.516Z
+contentType: updates
+productTeam: VTEX IO
+author: 4ubliktPJIsvyl1hq91RdK
+slug: store-framework-cms-nuevo-permiso-para-gestionar-redirecciones
+locale: es
+legacySlug: store-framework-cms-nuevo-permiso-necesario-para-gestionar-redirecciones
+announcementImageID: ''
+announcementSynopsisES: 'Para realizar redirecciones en Store Framework CMS es necesario tener un rol con el recurso "CMS Settings".'
+---
+
+**Redirecciones** es una funcionalidad de Store Framework CMS que hace que un usuario de la tienda, al entrar en una página específica, sea redirigido automáticamente a otra página, ya sea interna o externa a la tienda. Por razones de seguridad, estamos exigiendo que los usuarios del Admin tengan un permiso específico para realizar redirecciones.
+
+## ¿Qué cambió?
+
+Para que los usuarios del Admin puedan crear, editar y eliminar redirecciones en el CMS, ahora es necesario que tengan un rol de acceso con el [recurso del License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) **CMS Settings**.
+
+## ¿Por qué realizamos este cambio?
+
+Agregamos este requisito de permiso por motivos de seguridad. Así, solo los usuarios del Admin que hayan sido explícitamente autorizados tendrán acceso a la funcionalidad **Redirecciones**, impidiendo, de esta forma, que usuarios no autorizados puedan crear, editar y eliminar redirecciones.
+
+## ¿Qué se necesita hacer?
+
+Para que un usuario del Admin pueda gestionar redirecciones en Store Framework CMS, se le debe asignar un rol de acceso específico que incluya el recurso **CMS Settings**. Consulta las instrucciones para editar los roles de acceso de un usuario en el artículo [Gestionar usuarios](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512#editando-usuarios).
+
+Si deseas utilizar un rol de acceso personalizado, puedes crear un nuevo rol de acceso o editar uno existente para incluir el recurso **CMS Settings**. Consulta las instrucciones para crear y editar roles de acceso en el artículo [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol).
+
+Para más información sobre redirecciones, consulta el artículo [Gestión de redirecciones de URL](https://help.vtex.com/es/tutorial/gestion-de-redirecciones-de-url--3UJuFrU8imSVWg134mkvJV).
diff --git a/docs/announcements/es/new-process-for-security-testing.md b/docs/announcements/es/new-process-for-security-testing.md
new file mode 100644
index 000000000..7a1fdfed4
--- /dev/null
+++ b/docs/announcements/es/new-process-for-security-testing.md
@@ -0,0 +1,34 @@
+---
+title: 'Nuevo proceso para pruebas de seguridad'
+id: 7z6kjzqf2yZyRuwIXOfY3o
+status: PUBLISHED
+createdAt: 2023-09-05T13:50:09.793Z
+updatedAt: 2023-09-05T13:57:39.737Z
+publishedAt: 2023-09-05T13:57:39.737Z
+contentType: updates
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: nuevo-proceso-para-pruebas-de-seguridad
+locale: es
+legacySlug: nuevo-proceso-para-pruebas-de-seguridad
+announcementImageID: ''
+announcementSynopsisES: 'Hemos actualizado el procedimiento de realización de pruebas de penetración para que sea aún más seguro.'
+---
+
+VTEX realiza comprobaciones periódicas de vulnerabilidades mediante escaneos recurrentes y pruebas de penetración (_pen tests_). Estas prácticas nos permiten evaluar el nivel de madurez de la seguridad de nuestra plataforma.
+
+En caso necesario, puedes realizar una prueba de penetración independiente (con autorización de VTEX) e informar de cualquier vulnerabilidad encontrada. Para ello, el equipo de seguridad de VTEX ha actualizado el procedimiento que debe seguir el administrador de la tienda que desee realizar una prueba de penetración en su entorno.
+
+## ¿Qué cambió?
+
+De manera resumida, el nuevo proceso para realizar pruebas de penetración consiste en:
+
+1. Solicitar la programación de una prueba abriendo un ticket para el [equipo de soporte](https://help.vtex.com/support?/cultureInfo=es-419) de VTEX.
+2. Revisar y firmar el [acuerdo de confidencialidad](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip) antes de ejecutar cualquier prueba.
+3. Compartir los resultados con el equipo de seguridad de VTEX una vez finalizada la prueba.
+
+Para más información sobre este procedimiento, consulta la guía [Pruebas de penetración y avisos de vulnerabilidad](https://help.vtex.com/es/tutorial/pruebas-de-penetracion-y-advertencia-de-vulnerabilidad--6jodF6s1I50Fg84ZwutOCb).
+
+## ¿Por qué realizamos este cambio?
+
+Hemos actualizado el procedimiento de pruebas de penetración para garantizar la seguridad de la plataforma y que las evaluaciones se realicen de forma segura, impidiendo [procedimientos no permitidos](https://help.vtex.com/es/tutorial/pruebas-de-penetracion-y-advertencia-de-vulnerabilidad--6jodF6s1I50Fg84ZwutOCb#procedimientos-no-permitidos) y acciones que puedan perjudicar a nuestros clientes.
diff --git a/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md b/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md
index 6fc48eece..470799496 100644
--- a/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md
+++ b/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md
@@ -30,7 +30,7 @@ Para la Lista de promociones, desarrollamos una nueva interfaz que te permite:
 * Exportar tu lista de promociones activas.
 * Duplicar las promociones activas o archivadas para que el proceso de creación sea más rápido.
 
-![lista-promocoes-es](https://images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/4549ea65d574f5481ccbea5cde7e549c/lista-promociones-es.PNG)
+![lista-promocoes-es](//images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/4549ea65d574f5481ccbea5cde7e549c/lista-promociones-es.PNG)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/new-roles-page.md b/docs/announcements/es/new-roles-page.md
new file mode 100644
index 000000000..e84c9e785
--- /dev/null
+++ b/docs/announcements/es/new-roles-page.md
@@ -0,0 +1,35 @@
+---
+title: 'Nueva página Roles'
+id: 6kAbgyB0Ah8WK4ZAj7aSSL
+status: DRAFT
+createdAt: 2023-11-30T16:11:56.563Z
+updatedAt: 2023-11-30T16:25:18.794Z
+publishedAt: 
+contentType: updates
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: nueva-pagina-roles
+locale: es
+legacySlug: nueva-pagina-roles
+announcementImageID: ''
+announcementSynopsisES: 'Hemos rediseñado la página de roles para mostrar una información más completa y organizada.'
+---
+
+Diversos empleados ingresan al entorno administrativo de cada cuenta, por lo tanto, resulta fundamental restringir el acceso a acciones críticas con el fin de asegurar que cada usuario tenga acceso solamente a las acciones necesarias para el desempeño de sus funciones.
+
+En este contexto, la funcionalidad de los roles sirve para asignar un conjunto de [recursos](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) a usuarios administrativos, otorgando los permisos necesarios para el desarrollo de sus actividades en la tienda.
+
+Hemos rediseñado la página **Roles** con el objetivo de optimizar la gestión de los permisos de los usuarios. Accede desde la barra superior del Admin VTEX, haciendo clic en el avatar de tu perfil, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Roles de usuario**.
+
+## ¿Qué cambió?
+
+Además de todas las funcionalidades de la versión anterior, la nueva página **Roles** permite:
+
+* Acceder a la lista completa de los roles registrados en tu tienda con un diseño más moderno e intuitivo, actualizado de acuerdo con el [nuevo Admin VTEX](https://help.vtex.com/es/tutorial/admin-vtex-comience-aqui--531cHtUCUi3puRXNDmKziw).
+* Consultar información útil para gestionar los roles directamente desde la lista, así como el número de usuarios asociados a cada uno; también el tipo de rol (predefinido o personalizado) y la fecha de creación del mismo.
+
+![roles-es](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/61435c94a6654fd066e3b0f5f8cd2fd0/roles-es.png)
+
+## ¿Qué se necesita hacer?
+
+La actualización se aplicará automáticamente a todas las tiendas. Consulta más información sobre cómo utilizar la página optimizada en el artículo [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/announcements/es/new-rules-for-activating-vtex-support.md b/docs/announcements/es/new-rules-for-activating-vtex-support.md
new file mode 100644
index 000000000..1b601aabc
--- /dev/null
+++ b/docs/announcements/es/new-rules-for-activating-vtex-support.md
@@ -0,0 +1,32 @@
+---
+title: 'Nuevas reglas para activar el Soporte VTEX en Brasil'
+id: 18xfVJM9tbzpyqAUzIsBC1
+status: PUBLISHED
+createdAt: 2023-12-01T17:11:24.955Z
+updatedAt: 2023-12-13T14:03:46.024Z
+publishedAt: 2023-12-13T14:03:46.024Z
+contentType: updates
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: nuevas-reglas-para-activar-el-soporte-vtex
+locale: es
+legacySlug: nuevas-reglas-para-activar-el-soporte-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Para cuentas en Brasil, ahora es esencial tener Open Support Ticket en el perfil de acceso para usar el soporte de VTEX.'
+---
+
+Las cuentas de Brasil ahora requieren que los roles de los usuarios tengan asignado el recurso **Open Support Ticket** del producto **VTEX - Support** para poder solicitar asistencia del equipo de soporte VTEX. Un usuario con el rol *User Administrator - Restricted* debe asignar el permiso en [License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete).
+
+<div class="alert alert-info"> Los usuarios administrativos asociados al rol <strong> Owner (Admin Super)</strong> tienen el recurso <em> Open Support Ticket </em> asignado automáticamente.</div> 
+
+## ¿Qué cambió?
+
+Esta configuración solo es válida para las cuentas de Brasil y restringe la apertura de tickets de soporte a los usuarios autorizados. Para abrir un ticket con el equipo de soporte, el usuario debe tener el recurso **Open Support Ticket** del producto **VTEX - Support** asignado a su [rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+## ¿Por qué realizamos este cambio?
+
+El objetivo de este requisito es proteger la privacidad de los datos sensibles almacenados en la tienda, según las buenas prácticas de seguridad.
+
+## ¿Qué se necesita hacer?
+
+Un usuario con el rol *User Administrator - Restricted* debe asignar el recurso **Open Support Ticket** del producto **VTEX Support** en [License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete) a los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) de los usuarios que necesitan permiso para abrir tickets de soporte.
diff --git a/docs/announcements/es/new-sales-app-performance-monitor.md b/docs/announcements/es/new-sales-app-performance-monitor.md
new file mode 100644
index 000000000..496f43005
--- /dev/null
+++ b/docs/announcements/es/new-sales-app-performance-monitor.md
@@ -0,0 +1,32 @@
+---
+title: 'Nueva funcionalidad Performance Monitor de Sales App'
+id: 1xi0UVrKl5SwQbwts907bh
+status: PUBLISHED
+createdAt: 2023-09-05T19:37:19.176Z
+updatedAt: 2023-09-06T13:06:33.383Z
+publishedAt: 2023-09-06T13:06:33.383Z
+contentType: updates
+productTeam: Shopping
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: nuevo-performance-monitor-de-sales-app
+locale: es
+legacySlug: nuevo-performance-monitor-de-sales-app
+announcementImageID: ''
+announcementSynopsisES: 'Performance Monitor, la funcionalidad de Sales App con la cual tus vendedores saben cuánto vendieron usando la solución.'
+---
+
+[Performance Monitor](https://help.vtex.com/es/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/5pqtuvi97FFZiGf7MlSe8q) es la nueva funcionalidad de VTEX Sales App con la cual los vendedores saben exactamente cuánto vendieron usando la solución y ven los principales indicadores de ventas: ticket promedio, unidades por cliente y precio promedio por ítem vendido. Además, los vendedores también ven su posición con relación al promedio de la tienda.
+
+Los administradores que acceden al Admin VTEX también pueden ver estos datos, lo que les permite monitorear de cerca el desempeño de sus vendedores y tiendas.
+
+# Qué cambió?
+El menú lateral de VTEX Sales App ahora tiene la opción Desempeño de ventas. En esta sección, el vendedor puede ver su desempeño de ventas y el de otros colaboradores.
+
+# ¿Qué se necesita hacer?
+La funcionalidad está activada de forma predeterminada en todas las cuentas que utilizan la aplicación. La única excepción son las marcas que utilizan la solución Indeva by VTEX, en cuyo caso te debes poner en contacto con el equipo de soporte para activar la funcionalidad.
+
+- [Sales App - Primeros pasos y configuración](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc#)
+- [Sales App - Pagos](https://help.vtex.com/es/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy#)
+- [Sales App - Usando el App](https://help.vtex.com/es/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr#)
+- [Estrategias de comercio unificado](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv)
+
diff --git a/docs/announcements/es/new-sales-performance-dashboard.md b/docs/announcements/es/new-sales-performance-dashboard.md
index 916b9b2b4..2d421b01e 100644
--- a/docs/announcements/es/new-sales-performance-dashboard.md
+++ b/docs/announcements/es/new-sales-performance-dashboard.md
@@ -20,7 +20,7 @@ Con un volumen cada vez mayor de datos disponibles para que las operaciones de e
 
 El dashboard permite a los usuarios analizar los datos de todos los canales de venta de la tienda y de sus sellers, incluyendo métricas sobre los ingresos, los pedidos, el ticket promedio y mucho más. También incluye gráficos y tablas para que puedas comparar los resultados de diferentes periodos, e introduce once opciones de filtro para proporcionar insights unificados de toda la operación.
 
-![Sales Perf Dash ES](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
+![Sales Perf Dash ES](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
 
 ## ¿Qué cambió?
 Anteriormente, tu Admin VTEX solo contaba con la página Insights para generar inteligencia empresarial a partir de los datos de tus operaciones. Ahora hemos incluido una nueva página, Desempeño de Ventas, para ofrecerte una visión más detallada de los resultados de los diferentes canales de venta de tu tienda. La página Insights permanecerá en tu Admin VTEX.
diff --git a/docs/announcements/es/new-sku-bindings-interface.md b/docs/announcements/es/new-sku-bindings-interface.md
index e03530e7b..26c835333 100644
--- a/docs/announcements/es/new-sku-bindings-interface.md
+++ b/docs/announcements/es/new-sku-bindings-interface.md
@@ -19,7 +19,7 @@ VTEX permite que tu tienda actúe a la vez como [seller](https://help.vtex.com/e
 
 Para mejorar esta experiencia, hemos rediseñado la página **Vínculos de SKU** en el Admin VTEX. La nueva interfaz te permite seguir y gestionar la relación de vínculo entre los SKU del seller y del marketplace de una forma más sencilla y ágil.
 
-![sku_binding_page_ES_final](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/c5f9ed73561edd82c340eef6f28ef12a/sku_binding_page_ES_final.png)
+![sku_binding_page_ES_final](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/c5f9ed73561edd82c340eef6f28ef12a/sku_binding_page_ES_final.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/new-subscriptions-module.md b/docs/announcements/es/new-subscriptions-module.md
index 3d81c3458..c3166182c 100644
--- a/docs/announcements/es/new-subscriptions-module.md
+++ b/docs/announcements/es/new-subscriptions-module.md
@@ -39,36 +39,36 @@ La mejora del sistema de suscripciones también trajo nuevas funcionalidades par
 #### Nueva página de detalles de suscripción 
 Nuestra página de detalles de suscripción fue rediseñada con el fin de mejorar la experiencia del consumidor al reducir el tiempo para encontrar información y realizar tareas.  Además, contamos con una nueva funcionalidad de agregar ítems a una suscripción existente. 
 
-![img1 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/4af981552e541469c5e6e64cce65c0fe/img1_subscriptions_ES.png)
+![img1 subscriptions ES](//images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/4af981552e541469c5e6e64cce65c0fe/img1_subscriptions_ES.png)
 
 #### Barra de acciones
 Añadimos una barra de acciones para mejorar la comunicación con el usuario sobre lo que se necesita realizar o comunicar eventos importantes sobre su suscripción. 
 
-![img2 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/3e81d1e12117816f16aed0868751f9fa/img2_subscriptions_ES.png)
+![img2 subscriptions ES](//images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/3e81d1e12117816f16aed0868751f9fa/img2_subscriptions_ES.png)
 
 #### Agregar productos a su suscripción 
 Ahora se puede agregar nuevos ítems a su suscripción a través de la búsqueda de los productos disponibles en su tienda.
-![img3 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/a6418dd71b17f26b8052bae335b51514/img3_subscriptions_ES.png)
+![img3 subscriptions ES](//images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/a6418dd71b17f26b8052bae335b51514/img3_subscriptions_ES.png)
 
 #### Crear una nueva suscripción
 Añadimos una funcionalidad muy esperada: la pantalla de creación de suscripciones. La misma permite configurar una nueva suscripción sin tener que pasar por el checkout y ejecutar un pedido en ese momento. Para realizar esta acción, basta hacer clic en el botón __Nueva suscripción__, en la lista de suscripciones. 
 
-![img4 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/f6798de027a9761f8844f8a989ab45ea/img4_subscriptions_ES.png)
+![img4 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/f6798de027a9761f8844f8a989ab45ea/img4_subscriptions_ES.png)
 
 ### Nuevo concepto de suscripción para el sistema 
 Antes, para el sistema de VTEX, una suscripción estaba compuesta por un SKU asociado a una configuración de compra. Eso permitía que el consumidor de la tienda suscriba SKUs con direcciones de entrega e, incluso, con formas de pago diferentes —una evolución en comparación con la primera versión del sistema.
 
 #### Antes:
-![img5 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/0746b7539b10864ce48ed94972ac7f73/img5_subscriptions_ES_2.png)
+![img5 subscriptions ES](//images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/0746b7539b10864ce48ed94972ac7f73/img5_subscriptions_ES_2.png)
 
-![img6 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/be74eff4e0f355e2f2f54025d67e6b31/img6_subscriptions_ES.png)
+![img6 subscriptions ES](//images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/be74eff4e0f355e2f2f54025d67e6b31/img6_subscriptions_ES.png)
 
-![img7 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/8de4a03901a548be9c3ca65eaf9b68a4/img7_subscriptions_ES.png)
+![img7 subscriptions ES](//images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/8de4a03901a548be9c3ca65eaf9b68a4/img7_subscriptions_ES.png)
 
 La suscripción ahora consiste en una lista de SKUs y una configuración de compra determinada. Esto significa que eliminamos el concepto de «Grupos de suscripción» de nuestro sistema. Vea más información en nuestro artículo [Cómo funciona la suscripción](https://help.vtex.com/es/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453). El siguiente diagrama muestra el nuevo concepto de suscripción:  
 
 #### Ahora:
-![img8 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/0d226ff2f1bbcf31e803c7b9d297e35a/img8_subscriptions_ES_2.png)
+![img8 subscriptions ES](//images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/0d226ff2f1bbcf31e803c7b9d297e35a/img8_subscriptions_ES_2.png)
 
 ### Fecha de ciclo de la suscripción
 El cálculo de la próxima fecha del pedido por suscripción cambió. Esta alteración permite que el usuario modifique la fecha de su pedido con mayor facilidad. Para acompañar el cambio, desarrollamos una [API](https://developers.vtex.com/vtex-developer-docs/reference/cycles) que permite elegir con exactitud la próxima fecha, sin tener que modificar la frecuencia de la suscripción para que se adecue a la fecha deseada.
diff --git a/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md b/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md
index f9c874bdb..d26f57d1f 100644
--- a/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md
+++ b/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md
@@ -22,7 +22,7 @@ El diseño del panel de gestión de usuarios se actualizó con los mismos están
 - Exhibición de la configuración de MFA (autenticación de múltiples factores) de cada usuario en la lista de usuarios.
 - Botón para exportar los datos de la lista de usuarios en un archivo CSV que incluye ID, email y nombre.
 
-![Lista Usuários User Management ES](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
+![Lista Usuários User Management ES](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
 
 Además, el panel tiene algunos cambios:
 
diff --git a/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md b/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md
index 7dc0941a9..5c1126f0e 100644
--- a/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md
+++ b/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Actualizamos el layout del e-mail recibido al solicitar
 
 Actualizamos el layout del e-mail recibido al solicitar el código de acceso para su admin. Ahora, cada vez que se solicite el código de acceso para iniciar sesión o cambiar la contraseña, recibirá un e-mail como este a continuación:
 
-![announcement-novo-layout-email-codigo-acesso ES](https://images.ctfassets.net/alneenqid6w5/6LquxoOPXIDPxed7Zj46xY/f97c0ba49ec2942bfd37033f3e4ea521/announcement-novo-layout-email-codigo-acesso_ES.png)
+![announcement-novo-layout-email-codigo-acesso ES](//images.ctfassets.net/alneenqid6w5/6LquxoOPXIDPxed7Zj46xY/f97c0ba49ec2942bfd37033f3e4ea521/announcement-novo-layout-email-codigo-acesso_ES.png)
 
 ## ¿Qué cambia?
 
diff --git a/docs/announcements/es/offer-add-on-services-to-products-sold-in-vtex-sales-app.md b/docs/announcements/es/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
new file mode 100644
index 000000000..e15bc71b4
--- /dev/null
+++ b/docs/announcements/es/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
@@ -0,0 +1,28 @@
+---
+title: 'Ofrece servicios adicionales en productos vendidos en VTEX Sales App'
+id: 2kF3T4fCxoNKEKslXezTHL
+status: PUBLISHED
+createdAt: 2024-04-30T13:52:00.217Z
+updatedAt: 2024-04-30T17:15:44.935Z
+publishedAt: 2024-04-30T17:15:44.935Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: ofrece-servicios-adicionales-en-productos-vendidos-en-vtex-sales-app
+locale: es
+legacySlug: ofrece-servicios-adicionales-en-productos-vendidos-en-vtex-sales-app
+announcementImageID: ''
+announcementSynopsisES: 'Assembly Options en VTEX Sales App: servicios adicionales en productos vendidos y ensamblaje de ítems con diferentes SKU'
+---
+
+Desarrollamos una nueva funcionalidad para [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) que permite la integración entre los canales de venta online y físicos. Mediante esta herramienta, los vendedores de las tiendas físicas pueden ofrecer a los clientes atención personalizada.
+
+## ¿Qué cambió?
+Ahora, con la funcionalidad Assembly Options, los vendedores pueden ofrecer servicios adicionales en los productos vendidos, como garantías extendidas y seguros. Además, la funcionalidad permite la creación de conjuntos compuestos por distintos SKU, como cestas de Navidad o de desayuno, kits de maquillaje, entre otros.
+
+## ¿Por qué realizamos este cambio?
+Hemos desarrollado esta funcionalidad para posibilitar que los vendedores ofrezcan opciones de personalización de productos a través de la aplicación VTEX Sales App.
+
+## ¿Qué se necesita hacer?
+No se requiere ninguna acción; la funcionalidad ya está disponible en VTEX Sales App.
+Para más detalles sobre el uso de esta funcionalidad, consulta el artículo [Assembly Options en VTEX Sales App](https://help.vtex.com/es/tutorial/assembly-options-no-vtex-sales-app--4fTfqOMcXyhAhWXkl935lr).
diff --git a/docs/announcements/es/offer-pickup-points-for-subscription-orders.md b/docs/announcements/es/offer-pickup-points-for-subscription-orders.md
index acfb900f3..5b76d2d48 100644
--- a/docs/announcements/es/offer-pickup-points-for-subscription-orders.md
+++ b/docs/announcements/es/offer-pickup-points-for-subscription-orders.md
@@ -23,7 +23,7 @@ La funcionalidad de puntos de recogida del módulo Suscripciones solo está disp
 
 Anteriormente, las suscripciones no tenían puntos de recogida como una de las opciones de entrega. Con la nueva funcionalidad, el cliente final puede elegir los puntos de recogida de los ítems de un pedido de suscripción cuando realiza el _checkout_, como se ilustra en la siguiente imagen.
 
-![subscriptionspickup ES](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
+![subscriptionspickup ES](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
 
 Además, puede asignar puntos de recogida para las suscripciones nuevas y las suscripciones existentes a través de la [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1).
 
diff --git a/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md b/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md
new file mode 100644
index 000000000..5db168042
--- /dev/null
+++ b/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md
@@ -0,0 +1,31 @@
+---
+title: 'Módulo Status de los anuncios para integraciones con marketplaces VTEX'
+id: 1EeGgit1Brq3mmm8qhv2m3
+status: PUBLISHED
+createdAt: 2024-02-07T20:18:50.779Z
+updatedAt: 2024-03-04T19:21:14.936Z
+publishedAt: 2024-03-04T19:21:14.936Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: modulo-status-de-los-anuncios-para-integraciones-con-marketplaces-vtex
+locale: es
+legacySlug: modulo-status-de-los-anuncios-para-integraciones-con-marketplaces-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Monitorea tus anuncios con el nuevo módulo Status de los anuncios'
+---
+
+__Status de los anuncios__ es el nuevo módulo en el Admin VTEX que les permite a los sellers monitorear el envío y la sincronización de los anuncios de integraciones con marketplaces VTEX globalmente. Puedes acceder al módulo en el Admin VTEX a través de __Marketplace > Conexiones > Status de los anuncios__ o ingresando Status de los anuncios en la barra de búsqueda.  
+
+![Pantalla de estado de la oferta](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/91b3ae83719e933617324f74223d736b/-ES-_Offer_Status_-_GIF.gif)
+
+## ¿Por qué desarrollamos esta funcionalidad?
+
+Desarrollamos el módulo __Status de los anuncios__ para proporcionar una manera de visualizar todo el proceso de envío y sincronización de anuncios con marketplaces VTEX, así como su seguimiento desde una sola página. Ahora las pestañas separadas muestran los anuncios que están __Publicados,__ los que tienen __Problemas__ que impidieron su publicación y monitorear los que están __A la espera de finalización__ por parte del marketplace.
+
+Para ver información más detallada de cada pestaña del módulo y cómo utilizarlas, consulta el tutorial [Status de los anuncios](https://help.vtex.com/es/tutorial/status-de-anuncios-beta--2OE87wU26F7lApl99OdwvJ).
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción para utilizar el módulo __Status de los anuncios.__ Estará disponible en todas las integraciones con marketplaces VTEX a partir del **28 de febrero de 2024.**
+
diff --git a/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md b/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
index df793921b..e061b78f5 100644
--- a/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
+++ b/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
@@ -33,7 +33,7 @@ La revisión y la eventual adaptación de este cambio deben aplicarse a través
 
 Pasos necesarios para la revisión y adaptación:
 
-1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Personalización__: Si la página "/account/orders" tiene alguna personalización de front-end, debe migrarse y adaptarse a la nueva URL "/account#/orders". Revise y realice todas las pruebas necesarias garantizando el funcionamiento de todos los recursos personalizados.  
 3. __Enlaces del sitio__: Revise y actualice todos los enlaces personalizados del sitio y de los correos electrónicos transaccionales que antes dirigían al usuario a la URL "/account/orders". Estos enlaces ahora deben direccionar al usuario a "/account#/orders".
 
diff --git a/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md b/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md
new file mode 100644
index 000000000..71166d43f
--- /dev/null
+++ b/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md
@@ -0,0 +1,79 @@
+---
+title: 'Guía de onboarding: tu jornada completa en VTEX'
+id: 510SdtVmDcuIQAGoAl0sgf
+status: PUBLISHED
+createdAt: 2024-02-22T20:28:44.286Z
+updatedAt: 2024-02-23T14:44:33.307Z
+publishedAt: 2024-02-23T14:44:33.307Z
+contentType: updates
+productTeam: Others
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: guia-de-onboarding-tu-jornada-completa-en-vtex
+locale: es
+legacySlug: guia-de-onboarding-tu-jornada-completa-en-vtex
+announcementImageID: ''
+announcementSynopsisES: 'Lanzamiento de la Guía de onboarding: contenido hasta el go live, evolución de la operación y soporte en VTEX.'
+---
+
+Enfocados en el éxito de nuestros clientes, en VTEX brindamos soluciones completas para diversos modelos de negocio. La versatilidad del comercio composable se pone al servicio de la innovación y el crecimiento de tu operación.
+
+Y para facilitar la adopción de nuevos recursos, la gestión autónoma de tu negocio y la mejora en la escalabilidad, hemos lanzado la nueva **Guía de onboarding**, un contenido que abarca íntegramente la jornada de operar una tienda VTEX. Accede desde la sección [Comienza aquí](https://help.vtex.com/es/tracks) del Help Center.
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/359WPOFfC5pE91DpoECZJe/7fadfccaa642f496b82cdd09d93a5647/announcement_complete_guide_ES.png" alt="Guia de onboarding">
+</div>
+
+## ¿Qué es la Guía de onboarding?
+
+La **Guía de onboarding** está compuesta por una serie de artículos que incluyen la planificación de la arquitectura de la tienda, configuración del go live, productos para evolucionar el negocio y orientaciones sobre nuestro soporte. La guía presenta ajustes y recursos de la plataforma contextualizados en la jornada de operación de una tienda VTEX.
+
+La **Guía de onboarding** se compone de 3 series:
+
+* [Serie de la tienda VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU)
+* [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS)
+* [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy)
+
+<div class="alert alert-info"> 
+Las series presentan contenidos complementarios, pero son independientes entre sí, lo que significa que se puede explorar el contenido libremente y sin necesidad de seguir una secuencia.
+</div>
+
+Nuestra meta es asegurarnos de que tanto clientes como partners, así como todo el ecosistema de VTEX, puedan sacarle el máximo partido a la **Guía de onboarding**. Con este objetivo de garantizar la pertinencia del material para una amplia gama de negocios, hemos cubierto una jornada completa y abarcadora. 
+
+A continuación, te presentamos una [introducción](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) a lo que encontrarás en la guía.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/1N4nX2r9WxhdSCqr8zOEla/0c63bf21015b75c89c8dc1e75b283662/announcement_headings_track_1_ES.png" height="90" alt="Serie de la tienda VTEX">
+</div>
+
+La **Serie de la tienda VTEX** presenta el contexto inaugural de la operación, comenzando por la definición del [tipo de cuenta y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) que mejor se adaptan a las necesidades de tu negocio. A partir de ese punto, puedes llevar a cabo la [configuración inicial](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) y la configuración de los [módulos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) de la plataforma, enfocándote en acelerar la inauguración de la tienda. Una vez finalizadas las [integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) y la implementación de la [tecnología de frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para la construcción del storefront, es el momento del [go live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) y de la inauguración de la nueva tienda.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6yRmvP19rt7z1mNE7vdWQz/24410786064e27a396dd068b5c37418a/announcement_headings_track_2_ES.png" height="90" alt="Proximos pasos tras el go live">
+</div>
+
+La serie **Próximos pasos tras el go live** presenta la manera en que se realiza el [comercio unificado](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/5Qvw31yH2FPDBl14K5xXHA) con los recursos de la plataforma, abordando [configuración de módulos](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) no mencionada anteriormente, ya que en este punto el enfoque está en la evolución de la operación. Esta serie también presenta los [productos add-on](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) de VTEX, una variedad de productos que pueden adquirirse por separado para posibilitar nuevas estrategias y la diversificación del negocio.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6N7adQ7RxTfTyuIrCDqstZ/e7a5437f1d39e69bfe53047c68c22821/announcement_headings_track_3_ES.png" height="90" alt="VTEX Support">
+</div>
+
+**Soporte en VTEX** presenta el [soporte](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) que proporcionamos a los clientes, que no se limita a una parte específica de la jornada. El [funcionamiento del soporte](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) se aborda también en otras series, ya que la [apertura de tickets](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE) es la vía para determinadas contrataciones y solicitudes. Esta serie ha sido diseñada para que nuestros clientes tengan la mejor experiencia con nuestros servicios y dispongan de la información necesaria para abrir tickets, ya sea en el ámbito del soporte [técnico](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [financiero](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) o [comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
+
+## ¿Por qué creamos este material?
+
+Con el propósito de promover la autonomía de nuestros clientes, hemos estructurado la **Guía de onboarding** enfocándonos en los siguientes aspectos clave:
+
+* **Jornada completa:** se trata de la primera documentación de la jornada completa de la operación de una tienda VTEX, y el contenido está diseñado para acelerar el go live y reducir el time-to-revenue del negocio.
+* **Contenido inédito:** además del novedoso planteamiento de la jornada, hay contenido inédito, donde podemos destacar: _Serie de la tienda VTEX_ ([Cuentas y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl), [Integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), [Implementación de frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)), _Acciones después del go live_, ([Productos add-on](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm)) y Soporte VTEX como un todo.
+* **Relevancia general:** el valor de esta guía no se limita a nuevos clientes o a tiendas que se encuentran en las fases previas al go live, ya que consideramos una jornada lo suficientemente abarcadora como para ser relevante para una gran variedad de modelos de negocio.
+
+Esperamos que este material contribuya al éxito de tu negocio y a tu satisfacción con VTEX.
+
+|  | **Guía de onboarding** |  |
+| :---: | :---: | :---: |
+| Parte I | Parte II | Parte III |
+| [Serie de la tienda VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS) | [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy) |
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/4CgTVLjK3cazg4dDyVlB8m/eaf5ae6c543344566898cd810a9753a1/announcement_under_table_image_ES.png" alt="Imagen ecommerce">
+</div>
diff --git a/docs/announcements/es/performance-monitor.md b/docs/announcements/es/performance-monitor.md
new file mode 100644
index 000000000..a62b61ae8
--- /dev/null
+++ b/docs/announcements/es/performance-monitor.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 5xIaEr9iAiefNiVbDHJPuK
+status: DRAFT
+createdAt: 2023-08-30T18:48:05.528Z
+updatedAt: 2023-08-30T18:50:40.345Z
+publishedAt: 
+contentType: updates
+productTeam: 
+author: 
+slug: untitled-entry-2023-08-30-at-18-48-05
+locale: es
+legacySlug: untitled-entry-2023-08-30-at-18-48-05
+announcementImageID: ''
+announcementSynopsisES: ''
+---
+
+
diff --git a/docs/announcements/es/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md b/docs/announcements/es/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
index c22f3f2e5..97a217ed1 100644
--- a/docs/announcements/es/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
+++ b/docs/announcements/es/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
@@ -3,8 +3,8 @@ title: ' Pix: prepárate para el nuevo medio de pago para tu e-commerce'
 id: 1v5clxhNiDST404Orzwrv6
 status: PUBLISHED
 createdAt: 2020-10-28T11:13:00.457Z
-updatedAt: 2021-03-16T14:18:44.362Z
-publishedAt: 2021-03-16T14:18:44.362Z
+updatedAt: 2024-05-03T14:59:47.895Z
+publishedAt: 2024-05-03T14:59:47.895Z
 contentType: updates
 productTeam: Financial
 author: 5kCzbURAoPwM0YJGmMCLyD
@@ -21,14 +21,14 @@ Transaciones hechas con el Pix - nuevo medio de pago de Banco Central - empiezar
 
 El Pix és el nuevo médio de pago instantaneo de Banco Central (Bacen) - disponible 24 horas, siete dias por la semana - que hará transacciones bancarias en menos de 10 segundos. 
 
-Para conocer las ventajas y los beneficios de aceptar el Pix como medio de pago en su e-commerce, [haga clic aquí](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/ "haga clic aquí").
+Para conocer las ventajas y los beneficios de aceptar el Pix como medio de pago en su e-commerce, [haga clic aquí](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/).
 
 ## ¿Cómo parceros pueden integrarse a VTEX?
-__A partir del dia 19 de octubre de 2020__, parceros pueron empiezar sus integraciones con el [Payment Provider Protocol](https://developers.vtex.com/vtex-developer-docs/reference/payment-provider-protocol-api-overview "Payment Provider Protocol") para ofrecer el Pix como medio de pago para sus clientes.
+__A partir del dia 19 de octubre de 2020__, parceros pueron empiezar sus integraciones con el [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) para ofrecer el Pix como medio de pago para sus clientes.
 
 __Entidades de pago socias de VTEX __poden ponerse en contacto con la área de Asociaciónes y solicitar la integración hablando directamente con su Partner Manager. Además, tambien és possible hacer la integración abriendo un ticket para el time de [Soporte VTEX](https://help.vtex.com/es/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM?locale=en "Soporte VTEX").
 
-__Entidades de pago que aún no son socias de VTEX__ deben [rellenar un formulario de registro](https://vtex.com/br-pt/partner/ "rellenar un formulario de registro") para empiezar la asociación.
+__Entidades de pago que aún no son socias de VTEX__ deben [rellenar un formulario de registro](https://vtex.com/es-es/partner) para empiezar la asociación.
 
 ## Cómo clientes VTEX pueden prepararse para acceptar Pix en su ecommerce?
 
@@ -36,7 +36,7 @@ Existem dos opciones:
 
 - Ponerse en contacto con la empresa responsable por gestionar los pagos de su ecommerce y solicitar que esa empresa haga la integración con VTEX.
 
-- Elejir un socio y hacer las negociaciones contractuales y técnicos. Hoy los socios disponibles son: [PayMee](https://www.paymee.com.br/ "PayMee"), [Spin Pay](https://spinpay.com.br/ "Spin Pay") y [IUGU](https://iugu.com/ "IUGU").
+- Elejir un socio y hacer las negociaciones contractuales y técnicos. Hoy los socios disponibles son: [PayMee](https://www.paymee.com.br/ "PayMee"), [Spin Pay](https://spinpay.com.br/ "Spin Pay"), [IUGU](https://iugu.com/ "IUGU"), [Pagar.me](https://help.vtex.com/es/tutorial/configurar-gateway-pagarmev2--5TugxXNMOs0Ocyg4uqussM) y [Aarin](https://aarin.com.br/).
 
 ## Contáctese con los socios disponibles
 
@@ -46,6 +46,8 @@ Para descubrir más acerca los trámites para ofrecer el Pix como medio de pago,
 
 - __Spin Pay__:  comercial@spinpay.com.br 
 - __IUGU__: pixvtex@iugu.com 
-- __Paymee__:  www.paymee.com.br o comercial@paymee.com.br 
+- __Paymee__:  www.paymee.com.br o comercial@paymee.com.br
+- __Mercado Pago__: www.mercadopago.com.br
+- __Aarin__: https://aarin.com.br
 
-Usted puede leer toda na documentación de [Payment Provider Protocol](https://developers.vtex.com/vtex-developer-docs/reference/payment-flow#paymentmethods "Payment Provider Protocol") y también un [guía de cómo hacer la integración](https://developers.vtex.com/vtex-developer-docs/docs/pix-instant-payments-in-brazil "guía de cómo hacer la integración") utilizando la herramienta.
+Usted puede leer toda na documentación de [Payment Provider Protocol](https://developers.vtex.com/docs/api-reference/payment-provider-protocol) y también un [guía de cómo hacer la integración](https://developers.vtex.com/docs/guides/payments-integration-pix-instant-payments-in-brazil) utilizando la herramienta.
diff --git a/docs/announcements/es/price-filters-more-search-flexibility.md b/docs/announcements/es/price-filters-more-search-flexibility.md
index 46201ef07..ebf8f69c6 100644
--- a/docs/announcements/es/price-filters-more-search-flexibility.md
+++ b/docs/announcements/es/price-filters-more-search-flexibility.md
@@ -23,7 +23,7 @@ Ahora usted puede filtrar los precios combinando las múltiples Categorías y Ma
 
 Esta actualización de la funcionalidad permite la exportación de precios más específicos, a partir de la selección de los filtros.
 
-![filtro preco-ES](https://images.ctfassets.net/alneenqid6w5/7rJSF8qFUuoagVZaeVw2mp/4f00df74073f97f6da58c621b0b4a313/filtro_preco-ES.png)
+![filtro preco-ES](//images.ctfassets.net/alneenqid6w5/7rJSF8qFUuoagVZaeVw2mp/4f00df74073f97f6da58c621b0b4a313/filtro_preco-ES.png)
 
 ## ¿Qué necesito hacer?
 Para utilizar esta nueva configuración, realice los siguientes pasos:
diff --git a/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md b/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
index 72e4a848c..c274ce86c 100644
--- a/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
+++ b/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
@@ -31,7 +31,7 @@ Para saber si su cuenta aún está utilizando Pricing V1, realice los siguientes
 
 Si ve una pantalla similar a la que aparece a continuación, significa que necesita realizar la migración de su cuenta. 
 
-![Tela pricing antiga - ES](https://images.ctfassets.net/alneenqid6w5/54yIQLSCHg9VfDUumByo2r/20ba1b2f56b1e1b90fa6ecc4f386cbc5/Tela_pricing_antiga_-_ES.png)
+![Tela pricing antiga - ES](//images.ctfassets.net/alneenqid6w5/54yIQLSCHg9VfDUumByo2r/20ba1b2f56b1e1b90fa6ecc4f386cbc5/Tela_pricing_antiga_-_ES.png)
 
 Si su cuenta VTEX sigue utilizando versiones anteriores del Admin de VTEX (como "vtexcommercestable"), usted necesitará realizar la migración de la misma. Para eso, siga los pasos a continuación: 
 
diff --git a/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md b/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
new file mode 100644
index 000000000..64c88cd23
--- /dev/null
+++ b/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
@@ -0,0 +1,54 @@
+---
+title: 'Simulador de promociones: comprende las promociones aplicadas en el carrito'
+id: 2PPhczsmI0MXb5MyAlQx4R
+status: PUBLISHED
+createdAt: 2024-03-13T14:31:21.027Z
+updatedAt: 2024-03-13T19:02:02.287Z
+publishedAt: 2024-03-13T19:02:02.287Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: simulador-de-promociones-comprende-las-promociones-aplicadas-en-el-carrito
+locale: es
+legacySlug: simulador-de-promociones-comprende-las-promociones-aplicadas-en-el-carrito
+announcementImageID: ''
+announcementSynopsisES: 'Visualiza y gestiona las promociones aplicadas al carrito con el Simulador de promociones.'
+---
+
+Hemos lanzado globalmente y para todas las tiendas VTEX el **Simulador de promociones**: una nueva herramienta que permite visualizar las promociones aplicadas en el carrito de compras en tu tienda, junto con sus condiciones de activación. 
+
+Dadas las diversas opciones de configuración de [promociones](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N), este recurso es importante para tener una visión clara de la competencia, la acumulación de descuentos durante la compra y las causas de activación de dichas promociones.
+
+Hemos creado el **Simulador de promociones** con el objetivo de proporcionar a los administradores de tiendas más autonomía para gestionar y dirigir las promociones de acuerdo con sus estrategias de negocio. Con la nueva herramienta, podrás explorar y optimizar el desempeño de tus promociones, garantizando una mayor eficiencia en tu operación y una experiencia de compra mejorada para tus clientes.
+
+## ¿Qué hay de nuevo?
+
+A partir de ahora, el **Simulador de promociones** estará accesible para todas las tiendas VTEX a través de [Cartman](https://help.vtex.com/es/tutorial/configurar-cartman--1ACMTStZYkMqB0lTgwg451), una herramienta auxiliar a disposición de los administradores de tiendas en la etapa del checkout. Con el simulador podrás:
+
+* **Ver las** promociones aplicables o aplicadas a cada ítem del carrito y las condiciones para activarlas.
+* **Gestionar las promociones** existentes desde el carrito de compras.
+* **Probar la eliminación** de promociones aplicadas al carrito.
+* **Probar la aplicación** de otras promociones en el carrito antes de activarlas, incluidas las promociones programadas o inactivas.
+* **Comprender los motivos** por los que no se ha aplicado una promoción al carrito.
+
+![promotions simulator - es-gif 3](//downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/57780b2b9e038420e502eda2c41f4357/promotions_simulator_gi-3.gif)
+
+## ¿Qué se necesita hacer?
+
+No es necesario realizar ninguna acción, ya que el **Simulador de promociones** ya está disponible en todas las tiendas VTEX a través de [Cartman](https://help.vtex.com/es/tutorial/configurar-cartman--1ACMTStZYkMqB0lTgwg451).
+
+Los usuarios deben tener un [rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) con permisos para ver el módulo **Promociones** en el Admin VTEX y poder acceder al **Simulador de promociones**.
+
+Para empezar a utilizar el Simulador, sigue los pasos a continuación:
+
+1. En la barra superior del Admin VTEX, haz clic en el botón `Vista previa` para acceder a la página de acceso restringido de tu tienda.
+
+    También puedes acceder directamente a través de la URL `https://{accountname}.myvtex.com`,` `sustituyendo `{accountname}` por el nombre de tu cuenta VTEX.
+
+2. Agrega productos al carrito y accede al checkout en `https://{accountname}.myvtex.com/checkout/#/cart`.
+3. Haz clic en el botón azul <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> de la parte inferior derecha de la página para iniciar Cartman.
+4. Haz clic en **Simulador de promociones**.
+
+    En la nueva ventana, verás los detalles de las promociones aplicadas y no aplicadas al carrito.
+
+Consulta el artículo [Simulador de promociones](https://help.vtex.com/es/tutorial/simulador-de-promociones-beta--4zc8SNqjqeIJ0ZRMhjlnvy) para obtener más detalles sobre cómo utilizar la nueva herramienta.
diff --git a/docs/announcements/es/rate-vtexs-service-in-your-admin.md b/docs/announcements/es/rate-vtexs-service-in-your-admin.md
index 3701c1d76..1593031f8 100644
--- a/docs/announcements/es/rate-vtexs-service-in-your-admin.md
+++ b/docs/announcements/es/rate-vtexs-service-in-your-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Hemos lanzado una página de encuesta de satisfacción
 
 Hemos lanzado la nueva página *Encuesta de Satisfacción* en el Admin VTEX. Ahora, puedes evaluar nuestro servicio de soporte sin salir de la plataforma VTEX.
 
-![Pesquisa de satisfação ES](https://images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/075a8169826dbd7f0a98354b9825d467/image__18_.png)
+![Pesquisa de satisfação ES](//images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/075a8169826dbd7f0a98354b9825d467/image__18_.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
new file mode 100644
index 000000000..36ad5a829
--- /dev/null
+++ b/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -0,0 +1,88 @@
+---
+title: 'La validación con reCAPTCHA ahora seguirá la configuración del orderForm en todos los requests'
+id: 3SLXk0n8neXgWxaLaIgAC7
+status: PUBLISHED
+createdAt: 2023-07-04T21:20:42.330Z
+updatedAt: 2023-07-05T18:40:32.146Z
+publishedAt: 2023-07-05T18:40:32.146Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: validacion-con-recaptcha-seguira-la-configuracion-del-orderform-en-todos-los-requests
+locale: es
+legacySlug: la-validacion-con-recaptcha-ahora-seguira-la-configuracion-del-orderform-en
+announcementImageID: ''
+announcementSynopsisES: 'Tiendas que utilicen la API de Checkout para realizar pedidos deben revisar sus integraciones'
+---
+
+[reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) es un servicio de seguridad utilizado para determinar si una acción la realiza un usuario real o una automatización maliciosa, protegiendo los sitios web contra fraudes y abusos. Al activar [reCAPTCHA en el checkout](https://help.vtex.com/es/tutorial/recaptcha-en-el-checkout--18Te3oDd7f4qcjKu9jhNzP), además de seguir las mejores prácticas contra ataques virtuales, reduces el riesgo de que tu tienda sea vulnerada con fines fraudulentos.
+
+A partir de ahora, y para proteger aún más a nuestros clientes, VTEX aplicará la configuración del orderForm reCAPTCHA de cada cuenta a todos los requests provenientes de la API de Checkout, independientemente de los roles asociados al usuario o clave de la aplicación.
+
+Los administradores de tienda que utilizan la API de Checkout para realizar pedidos desde aplicaciones móviles, entornos de tienda headless y otras aplicaciones similares deben
+ [revisar](#revisa-tus-integraciones) y [ajustar](#ajusta-tus-integraciones) sus integraciones antes del __1 de septiembre de 2023__.
+
+## ¿Qué cambia?
+
+Antes, la verificación con reCAPTCHA no era necesaria para los pedidos realizados por usuarios y claves de aplicación con el recurso [recurso](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) `Shopping Cart Full Access` en License Manager. Esto incluye [roles predefinidos](https://help.vtex.com/es/tutorial/roles-de-usuario-predefinidos--jGDurZKJHvHJS13LnO7Dy) como el rol `Owner (Admin Super)` y `User Admin - RESTRICTED`, así como el [usuario Titular](https://help.vtex.com/es/tutorial/que-es-el-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy).
+
+Ahora, la verificación con reCAPTCHA seguirá la configuración del orderForm establecida en cada cuenta en todos los requests de la API de Checkout, independientemente de los roles asociados al usuario o la clave de aplicación.
+
+## ¿Por qué realizamos este cambio?
+
+Esta acción era necesaria para reducir las posibilidades de fraude y abuso en nuestras tiendas, como por ejemplo la prueba de tarjetas (card testing). Aunque las mejores prácticas para el uso de claves de aplicación indican que las tiendas deben crear claves individuales para cada integración y otorgarles roles restrictivos, algunos administradores de tiendas se ponían en riesgo al utilizar claves de aplicación con roles de administrador. 
+
+Entendemos que puede haber una razón legítima para que en algunas integraciones se amplíen los permisos dando acceso a más recursos e información, por lo que tomamos la decisión de solicitar a los administradores de tiendas que implementen reCAPTCHA en dichas integraciones. Si esto no fuera posible, tienen la opción de deshabilitar la validación reCAPTCHA en sus cuentas (`recaptchaValidation="never"`) e implementar medidas de protección alternativas contra ataques automatizados.
+
+Sabemos que estos cambios tendrán un impacto en las operaciones de nuestros clientes, pero adoptar las mejores prácticas de seguridad siempre es necesario y beneficioso para todo nuestro ecosistema.
+
+## ¿Qué se necesita hacer?
+
+### Revisa tus integraciones
+
+Pide a tu equipo de desarrolladores que revisen tus integraciones que utilizan la API de Checkout para realizar pedidos en tu tienda VTEX, usando los siguientes endpoints:
+
+- [Place order from an existing cart](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pub/orderForm/-orderFormId-/transaction)
+- [Place order](https://developers.vtex.com/docs/api-reference/checkout-api#put-/api/checkout/pub/orders)
+
+Tu equipo podrá guiarse por el siguiente diagrama para evaluar si es necesario ajustar una integración, según la [configuración del reCAPTCHA en el orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) de tu tienda y cómo se [autentican](https://developers.vtex.com/docs/guides/authentication-overview) los requests realizados a estos endpoints:
+
+![reCAPTCHA diagram](//images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/ec9c6f6a9dfdc69fbcd412bde938d4f2/recaptcha-config-ES.png)
+
+- __Caso 1__: *no se requieren cambios en la integración, pero tu tienda podría estar en riesgo.*
+
+Tu tienda no utiliza reCAPTCHA en el Checkout y, por lo tanto, es vulnerable a ataques automatizados, a menos que implementes otras medidas de protección en tu integración.
+
+- __Caso 2__: *necesitas ajustar tu integración, de lo contrario podría dejar de funcionar.*
+
+Tu tienda utiliza reCAPTCHA en el Checkout, pero no está preparada para mostrarlo correctamente en la interfaz de usuario. Tu equipo de desarrolladores debe [ajustar sus integraciones](#ajusta-tus-integraciones).
+
+- __Caso 3__: *no se requieren cambios en la integración.*
+
+Tu tienda utiliza reCAPTCHA en el Checkout y está preparada para exhibirlo correctamente en la interfaz de usuario. ¡Enhorabuena por seguir las mejores prácticas en materia de seguridad!
+
+### Ajusta tus integraciones
+
+Si tu equipo de desarrolladores identifica que tu integración requiere algún tipo de atención, deben seguir las instrucciones proporcionadas en el artículo [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations).
+
+<div class="alert alert-warning">
+Si está implementando reCAPTCHA en una aplicación móvil nativa, use reCAPTCHA v3. De lo contrario, use reCAPTCHA v2.
+</div>
+
+Al utilizar el `recaptchaKey` que devolvió el Checkout, el widget reCAPTCHA debe ser renderizado en la interfaz de usuario de tu aplicación móvil/entorno de tienda headless (o similar) como se describe en el artículo de [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display?hl=es-419) o [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3?hl=es-419) proporcionado por Google.
+
+Después de que el comprador resuelva el reCAPTCHA, su respuesta (`recaptchaToken`) se debe enviar a la API de Checkout para completar la compra, tal y como se describe en la sección *Final validation* del artículo [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#final-validation). En este momento, la API de Checkout [verificará la respuesta del usuario](https://developers.google.com/recaptcha/docs/verify?hl=es-419) utilizando el token proporcionado.
+
+<div class="alert alert-danger">
+Todas las integraciones que utilicen la API de Checkout para realizar pedidos deben revisarse y ajustarse antes del 1 de septiembre de 2023. Las aplicaciones que no tengan la capacidad de mostrar el widget reCAPTCHA y verificar la respuesta del usuario no podrán realizar pedidos a partir de esta fecha.
+</div>
+
+## Más información
+
+Consulta los siguientes artículos sobre reCAPTCHA y las mejores prácticas para garantizar la protección de tu tienda:
+
+- [reCAPTCHA en el Checkout](https://help.vtex.com/es/tutorial/recaptcha-en-el-checkout--18Te3oDd7f4qcjKu9jhNzP)
+- [Prácticas recomendadas para evitar ataques virtuales](https://help.vtex.com/es/tutorial/practicas-recomendadas-para-evitar-ataques-virtuales--191rpbF7UgrKapVCi1PCDE)
+- [Prácticas recomendadas para evitar ataques virtuales](https://help.vtex.com/es/tutorial/buenas-practicas-claves-de-aplicacion--7b6nD1VMHa49aI5brlOvJm)
+- [Recursos del License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3)
+
diff --git a/docs/announcements/es/redesigned-products-and-skus-page.md b/docs/announcements/es/redesigned-products-and-skus-page.md
index 06a4036e6..2b815ae61 100644
--- a/docs/announcements/es/redesigned-products-and-skus-page.md
+++ b/docs/announcements/es/redesigned-products-and-skus-page.md
@@ -28,7 +28,7 @@ La nueva interfaz de **Productos y SKUs** permite:
 - Monitorear el status de los productos y SKU de forma más directa y visual con iconos y status de SKU directamente en la lista.
 - Identificar más fácilmente los productos y SKU que tengan información pendiente para estar disponibles para la venta mediante el nuevo status **Pendiente**.
 
-![catalog-products-skus-es](https://images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/2978ab303cb7eba7b77ad22caa620a49/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_29_13_1.png)
+![catalog-products-skus-es](//images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/2978ab303cb7eba7b77ad22caa620a49/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_29_13_1.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
index 6abdbff27..40037d7fd 100644
--- a/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
@@ -1,10 +1,10 @@
 ---
 title: 'Requests con paginación en la API de búsqueda van a cambiar'
 id: 3UZR4qoAisiqE6kmuuYEAc
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-01-24T14:11:26.225Z
-updatedAt: 2020-11-27T19:40:17.179Z
-publishedAt: 2020-05-11T18:53:36.826Z
+updatedAt: 2023-12-15T13:03:53.872Z
+publishedAt: 2023-12-15T13:03:53.872Z
 contentType: updates
 productTeam: Identity
 author: authors_24
@@ -31,4 +31,4 @@ Este cambio ya se ha implementado en la API, pero hasta la fecha límite, todav
 - También hay un límite de 2500 elementos para una búsqueda. Por lo tanto, usted no puede utilizar un valor mayor que 2500 al parámetro <b>_to</b>.
 </div>
 
-Para saber todos los detalles del funcionamiento de los requests de paginación en la API de búsqueda, acceda a este [documento](https://developers.vtex.com/reference/search-api-overview).
+Para saber todos los detalles del funcionamiento de los requests de paginación en la API de búsqueda, acceda a este [documento](https://developers.vtex.com/docs/api-reference/search-api).
diff --git a/docs/announcements/es/reusing-images-in-site-editor.md b/docs/announcements/es/reusing-images-in-site-editor.md
index e7511f01a..5d91e86b2 100644
--- a/docs/announcements/es/reusing-images-in-site-editor.md
+++ b/docs/announcements/es/reusing-images-in-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Hemos mejorado los bloques con la opción nativa de sub
 
 Hemos mejorado la forma de gestionar sus imágenes en [Site Editor](https://help.vtex.com/es/subcategory/site-editor--9Arh3cJIOYlfSD1MUC2h3) mediante un Image Widget, que es un repositorio de imágenes centralizado para que pueda subir y reutilizar las imágenes de la tienda. 
 
-![gif-image-widget-es](https://images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/d92ceb37b53da2c63b9802a6c082db77/Yhin0k3Vio.gif)
+![gif-image-widget-es](//images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/d92ceb37b53da2c63b9802a6c082db77/Yhin0k3Vio.gif)
 
 <div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 16px">
   Image Widget está disponible en Open Beta para los usuarios de VTEX IO.
diff --git a/docs/announcements/es/sales-performance-dashboard-updates.md b/docs/announcements/es/sales-performance-dashboard-updates.md
index 4d7b3187a..a00eb375b 100644
--- a/docs/announcements/es/sales-performance-dashboard-updates.md
+++ b/docs/announcements/es/sales-performance-dashboard-updates.md
@@ -19,7 +19,7 @@ La página «Desempeño de ventas» es un dashboard que permite a los operadores
 
 Actualizamos la experiencia en la página basándonos en tus sugerencias y agregamos nuevas posibilidades para aplicar filtros, vistas y exploración de datos. 
 
-![Sales perf update ES](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
+![Sales perf update ES](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
 
 ## ¿Qué cambió?
 Mejoramos algunas funcionalidades existentes, como Filtros y Datos y expandimos el menú de Vistas. La nueva experiencia de filtros de la página permite más combinaciones de filtros con menos clics. Por su parte, la nueva funcionalidad de menú Vista está diseñada para guardar los filtros y métricas aplicados en la página, lo que permite volver rápidamente al mismo contexto. 
diff --git a/docs/announcements/es/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md b/docs/announcements/es/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
index c9101b746..7b6529014 100644
--- a/docs/announcements/es/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
+++ b/docs/announcements/es/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
@@ -1,10 +1,10 @@
 ---
-title: 'Samsung Pay: flexibilice pagos con la nueva cartera digital.'
+title: 'Samsung Pay: flexibilice pagos con la nueva cartera digital'
 id: 2hPbwpiBjuUDh5exB2t5I9
 status: PUBLISHED
 createdAt: 2020-08-26T13:58:55.512Z
-updatedAt: 2020-08-26T16:42:36.874Z
-publishedAt: 2020-08-26T16:42:36.874Z
+updatedAt: 2023-09-26T15:25:06.834Z
+publishedAt: 2023-09-26T15:25:06.834Z
 contentType: updates
 productTeam: Financial
 author: 7qy2DBsUp8U5P9lqV0JHfR
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'A partir de agosto, VTEX cuenta con Samsung Pay —cartera digital de Samsung— como medio de pago en el SmartCheckout.'
 ---
 
-VTEX siempre busca proporcionar la mejor experiencia de compra para sus clientes. Por esta razón, ahora usted puede utilizar [Samsung Pay](https://www.samsung.com/es/samsung-pay/ "Samsung Pay") —la [cartera digital](https://help.vtex.com/es/tutorial/o-que-e-uma-carteira-digital-e-wallet?locale=es "cartera digital") (e-wallet) de Samsung— como medio de pago en su comercio electrónico.
+VTEX siempre busca proporcionar la mejor experiencia de compra para sus clientes. Por esta razón, ahora usted puede utilizar [Samsung Pay](https://www.samsung.com/es/samsung-pay/ "Samsung Pay") —la [cartera digital](https://help.vtex.com/es/tutorial/o-que-e-uma-carteira-digital-e-wallet?locale=es "cartera digital") (ewallet) de Samsung— como medio de pago en su comercio electrónico.
 
 ## Ventajas
 Ofrecer carteras digitales como forma de pago en SmartCheckout expande la gama de medios de pago de su comercio electrónico.
@@ -23,7 +23,7 @@ Ofrecer carteras digitales como forma de pago en SmartCheckout expande la gama d
 Esta estrategia permite que el administrador de la tienda contemple diferentes perfiles de compra. Cuanto más diversas sean sus opciones de pago, mayores serán las posibilidades de que su consumidor se incline por una de ellas y finalice la compra.   
 
 Además, la inclusión de Samsung Pay en sus opciones de pago incluye un nicho de consumidores que solo compran en línea a través de carteras digitales.
- 
+
 ## Cómo funciona 
 Solamente los usuarios de Samsung Pay podrán efectuar compras con este método de pago. Es decir, los consumidores finales que ya poseen Samsung Pay instalado en su dispositivo móvil.
 
diff --git a/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md b/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md
index 0ba947a2d..0febd274e 100644
--- a/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md
+++ b/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md
@@ -23,7 +23,7 @@ Anteriormente, tras el registro en la tienda o la primera compra, los datos del
 
 A partir de ahora, dos casillas de verificación en la pantalla de pago permitirán al usuario indicar si quiere que su información personal y de pago se almacene y se reutilice para futuras compras. De este modo, se reducirá el tiempo que tarda el cliente en realizar la compra. 
 
-![ Save user data opt-in ES](https://images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/503e29a5bdf5749d0d44bd525b96117e/Save_user_data_-_ES.PNG)
+![ Save user data opt-in ES](//images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/503e29a5bdf5749d0d44bd525b96117e/Save_user_data_-_ES.PNG)
 
 Más información en [SmartCheckout - Rellenado automático de los datos del cliente](https://help.vtex.com/es/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan#).
 
diff --git a/docs/announcements/es/schedule-content-publication-with-site-editor.md b/docs/announcements/es/schedule-content-publication-with-site-editor.md
index c9cbd7c26..05e87cef7 100644
--- a/docs/announcements/es/schedule-content-publication-with-site-editor.md
+++ b/docs/announcements/es/schedule-content-publication-with-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Crea y programa versiones de bloques predefinidas en el
 
 El recurso **Configuraciones** del Site Editor se actualizó. Ahora, además de llamarse **Versiones**, puedes crear versiones del contenido de tu tienda que se han desactivado, y activarlas cuando así lo desees.
 
-![activating-versions-es](https://images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/fe0961feb8749a97ba1879d2245e2a04/activating-versions-es.gif)
+![activating-versions-es](//images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/fe0961feb8749a97ba1879d2245e2a04/activating-versions-es.gif)
 
 ## ¿Qué cambió?
 Anteriormente, la funcionalidad **Versiones** se llamaba **Configuraciones**, y solo era posible crear una nueva versión activada, por ejemplo un carrusel con productos en promoción, o programar su activación. Después de deshabilitar una versión, no podía volver a activarla.
diff --git a/docs/announcements/es/search-filters-in-instores-endless-aisle.md b/docs/announcements/es/search-filters-in-instores-endless-aisle.md
index 5f33f491c..0ffff6aca 100644
--- a/docs/announcements/es/search-filters-in-instores-endless-aisle.md
+++ b/docs/announcements/es/search-filters-in-instores-endless-aisle.md
@@ -25,7 +25,7 @@ Anteriormente, los filtros de búsqueda de VTEX Intelligent Search no estaban di
 
 Con la nueva funcionalidad, al buscar un término, los vendedores pueden filtrar los resultados por rango de precios, departamento y marca, por ejemplo, entre otros filtros configurables en VTEX Intelligent Search. Esto permite encontrar rápidamente el producto deseado.
 
-![instore-filtros-es](https://images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b4bbbc744c5efe25cbc100d53113ca6b/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_09_28.png)
+![instore-filtros-es](//images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b4bbbc744c5efe25cbc100d53113ca6b/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_09_28.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
new file mode 100644
index 000000000..34df1727c
--- /dev/null
+++ b/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -0,0 +1,50 @@
+---
+title: 'La barra de búsqueda global del Admin VTEX ahora permite buscar pedidos'
+id: 4ycVQJ5hRkxVy8r2iQamCb
+status: PUBLISHED
+createdAt: 2023-10-17T12:05:18.467Z
+updatedAt: 2023-10-17T21:04:22.374Z
+publishedAt: 2023-10-17T21:04:22.374Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: barra-de-busqueda-global-del-admin-vtex-ahora-permite-buscar-pedidos
+locale: es
+legacySlug: now-you-can-search-for-orders-in-the-vtex-admin-global-search-bar
+announcementImageID: ''
+announcementSynopsisES: 'La barra de búsqueda global del Admin VTEX ahora te permite buscar pedidos de la tienda.'
+---
+
+Hemos mejorado la barra de búsqueda global, situada en la parte superior de las páginas del Admin VTEX, para que además de buscar las páginas del Admin también puedas buscar los pedidos de tu tienda.
+
+Esta mejora estará disponible globalmente en todas las tiendas VTEX a partir de de hoy, 17 de octubre, mediante una actualización automática.
+
+## ¿Qué cambió?
+
+Antes, la barra de búsqueda solo permitía buscar las páginas del Admin VTEX. Ahora, también puedes buscar los pedidos de tu tienda utilizando cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
+Para buscar, haz clic en la barra de búsqueda, selecciona la opción `Pedidos` y ejecuta la búsqueda deseada. Cada búsqueda puede devolver hasta 10 resultados, como se muestra en la siguiente imagen:
+
+![order_global_search_ES](//images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/a109785412d490a21a2f9f984ad47114/order_global_search_ES.gif)
+
+Al hacer clic en un resultado, se te redirigirá a la [página de detalles](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) del pedido. Además, los últimos 10 pedidos buscados se registran como historial de búsquedas recientes para mayor facilidad de acceso. El registro de búsqueda se almacena a nivel de [usuario](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) y no se comparte entre diferentes usuarios.
+
+<div class = "alert alert-info">
+Para acceder a los pedidos a través de la búsqueda global del Admin VTEX, el <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol</a> del usuario debe estar asociado al recurso <b>View order</b> (clave OMSViewier) del <i>Order Management System</i> (OMS).
+</div>
+
+## ¿Por qué realizamos este cambio?
+
+El acceso a los pedidos desde la barra de búsqueda global facilita las operaciones relacionadas con los pedidos y aumenta la eficiencia.
+
+Ahora, independientemente de la página del Admin VTEX en la que te encuentres, la barra de búsqueda global está visible y puedes acceder a los pedidos sin tener que navegar al módulo **Pedidos**.
+
+## ¿Qué se necesita hacer? 
+
+A partir del hoy, 17 de octubre, todas las tiendas VTEX se actualizarán automáticamente con la mejora. No se requiere ninguna acción de tu parte.
+
diff --git a/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md b/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
index 4d3cd31f8..90ba46050 100644
--- a/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
+++ b/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
@@ -19,7 +19,7 @@ La __Black Friday__ será pronto. Y, con ella, viene el deseo de aprovechar esta
 
 Para ayudarle en esta tarea, VTEX está lanzando una __app exclusiva en asociación con Google__, que estará disponible en nuestra [App Store](https://apps.vtex.com/vtex-google-shopping/p).
 
-![Google Shopping App](https://images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
+![Google Shopping App](//images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
 
 Ella integra su negocio a Google Ads y le permite divulgar sus productos en Google Shopping, utilizando las nuevas Smart Shopping Campaigns, y acompañar los resultados con facilidad y rapidez.
 
diff --git a/docs/announcements/es/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md b/docs/announcements/es/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
index 359b79f07..5f77245ae 100644
--- a/docs/announcements/es/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
+++ b/docs/announcements/es/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
@@ -25,7 +25,7 @@ Configuración antes de la actualización:
   <tr>
     <td>
       <img
-           src="https:https://images.ctfassets.net/alneenqid6w5/3X2DYFqS9osYocOAfE2fHO/1bbfd3da21bf313a3ac44e5a22319a70/seller-promo-ES.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuración de sellers en la promoción">
+           src="https://images.ctfassets.net/alneenqid6w5/3X2DYFqS9osYocOAfE2fHO/1bbfd3da21bf313a3ac44e5a22319a70/seller-promo-ES.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuración de sellers en la promoción">
     </td>
   </tr>
   <tr>
@@ -43,7 +43,7 @@ Configuración después de la actualización:
   <tr>
     <td>
       <img
-           src="https://https://images.ctfassets.net/alneenqid6w5/4vwUzssj4VtevZv3oLSgVL/48ab618d37104731244e7a5bc3c5766c/seller-promo-ES2.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuración de sellers en la promoción">
+           src="https:////images.ctfassets.net/alneenqid6w5/4vwUzssj4VtevZv3oLSgVL/48ab618d37104731244e7a5bc3c5766c/seller-promo-ES2.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuración de sellers en la promoción">
     </td>
   </tr>
   <tr>
diff --git a/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md b/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
new file mode 100644
index 000000000..86d98a486
--- /dev/null
+++ b/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
@@ -0,0 +1,30 @@
+---
+title: 'Temporada de Compras: Prepare su tienda con nuestra Guía de Buenas Prácticas'
+id: 4c0wnRmblHPKfCKkkiOkhX
+status: PUBLISHED
+createdAt: 2023-10-03T13:08:30.221Z
+updatedAt: 2023-11-17T19:45:14.488Z
+publishedAt: 2023-11-17T19:45:14.488Z
+contentType: updates
+productTeam: Others
+author: 1u80f14cWqneWquMc8tUq1
+slug: temporada-de-compras-prepare-su-tienda-con-nuestra-guia-de-buenas-practicas-2023
+locale: es
+legacySlug: temporada-de-compras-prepare-su-tienda-con-nuestra-guia-de-buenas-practicas-2023
+announcementImageID: ''
+announcementSynopsisES: 'Siga nuestras recomendaciones y consejos para aprovechar todas las oportunidades de venta del Black Friday.'
+---
+
+El __Black Friday__ ya está llegando. La fecha oficial este año es __24 de noviembre__, pero muchas tiendas comenzarán a hacer campañas de promoción dentro de poco tiempo. Por eso, para aprovechar al máximo todas las oportunidades de una de las principales fechas del comercio on-line, es bueno empezar pronto a prepararse.
+
+Como hacemos todos los años, hemos creado una guía con recomendaciones y consejos exclusivos para garantizar la salud de su tienda y el éxito de sus ventas. 
+
+Disponible para clientes y socios VTEX, usted puede acceder a la guía por la homepage del Admin o directamente por la URL 
+
+```
+https://{accountName}.myvtex.com/admin/shopping-season
+```
+
+Sólo hay que sustituir `{accountName}` por el Account Name de su tienda, como en la imagen de abajo.
+
+![Shopping Season Guidelines - 2023 - ES](//images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/6fec5cf6a7f649fef7c71a4c0f3d7e00/Shopping_Season_Guidelines_-_2023_-_ES.png)
diff --git a/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md b/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md
new file mode 100644
index 000000000..6b323a14f
--- /dev/null
+++ b/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md
@@ -0,0 +1,35 @@
+---
+title: 'Site Editor y Multimedia: nuevo requisito de autorización'
+id: 7tO32uRxIUK8lOp8AvWs2L
+status: PUBLISHED
+createdAt: 2024-02-26T12:35:10.352Z
+updatedAt: 2024-02-26T18:06:13.754Z
+publishedAt: 2024-02-26T18:06:13.754Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: site-editor-y-multimedia-nuevo-requisito-de-autorizacion
+locale: es
+legacySlug: site-editor-y-multimedia-nuevo-requisito-de-autorizacion
+announcementImageID: ''
+announcementSynopsisES: 'CMS GraphQL API es obligatorio para la gestión de contenido. Actualiza los roles según corresponda.'
+---
+
+A partir del lunes 18 de marzo de 2024, será obligatorio que todos los [usuarios](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) y [claves de aplicación](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) que necesiten acceder a [Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) y [Multimedia](https://help.vtex.com/es/tutorial/media-overview--31fhjHTt4TBoo50AmGQ9b2) tengan el [recurso](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) de License Manager `CMS GraphQL API` agregado a sus [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+## ¿Qué cambió?
+
+Como se [anunció anteriormente para los usuarios de Headless CMS](https://help.vtex.com/es/announcements/headless-cms-new-authorization-requirement--7G056zzZmGFBztkRqhpUgj), es necesario que tanto los usuarios como las claves de aplicación tengan el recurso `CMS GraphQL API` asociado con su rol para gestionar el contenido.
+
+Ahora, estamos extendiendo este requisito al Site Editor y Multimedia, lo que significa que el recurso 'CMS GraphQL API' es necesario para gestionar el contenido utilizando estas herramientas.
+
+## ¿Por qué realizamos este cambio?
+Este cambio tiene como objetivo mejorar la seguridad y simplificar el acceso del usuario a Site Editor y Multimedia, brindando un entorno más controlado y seguro para gestionar el contenido de la tienda. 
+
+## ¿Qué se necesita hacer?
+Asegúrate de que los usuarios de Site Editor y Multimedia tienen sus roles asociados al recurso `CMS GraphQL API`, ya sea [creando un nuevo rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) o editando uno existente.
+
+<div class="alert alert-warning">
+  <p>Para gestionar usuarios y roles, tu rol de usuario debe estar asociado al recurso <code>Save access profile</code> del producto <bold>License Manager</bold>. Por ejemplo, <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> es un rol predefinido que tiene asociado el recurso <code>Save access profile</code>.</p>
+</div>
+
diff --git a/docs/announcements/es/site-editor-fixed-content-loss-issue.md b/docs/announcements/es/site-editor-fixed-content-loss-issue.md
new file mode 100644
index 000000000..601b83c36
--- /dev/null
+++ b/docs/announcements/es/site-editor-fixed-content-loss-issue.md
@@ -0,0 +1,29 @@
+---
+title: 'Site Editor: solución para el problema de pérdida de contenido'
+id: 1mnrlSMyMmU1iAUyEquVYB
+status: PUBLISHED
+createdAt: 2024-06-13T12:25:13.359Z
+updatedAt: 2024-06-13T13:29:05.308Z
+publishedAt: 2024-06-13T13:29:05.308Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: site-editor-solucion-para-el-problema-de-perdida-de-contenido
+locale: es
+legacySlug: site-editor-solucion-para-el-problema-de-perdida-de-contenido
+announcementImageID: ''
+announcementSynopsisES: 'Site Editor: actualización de almacenamiento para mejor desempeño y confiabilidad.'
+---
+
+El 12 de junio, se actualizó el almacenamiento de contenido del [Site Editor](https://help.vtex.com/es/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) para todas las cuentas que lo utilizan para solucionar el problema de la [pérdida intermitente de contenido de Site Editor](https://help.vtex.com/es/known-issues/intermitent-site-editor-content-loss--3a5MlAoD2Z7Gu6HDS8wihD). Esta actualización optimiza el desempeño y la confiabilidad del almacenamiento, además de reducir el espacio que ocupa el contenido almacenado.
+
+## ¿Qué cambió?
+Anteriormente, los frecuentes cambios en el contenido de Site Editor podían resultar en que el archivo `content.json` se volviera excesivamente grande, lo que causaba la pérdida de contenido [al promover un workspace de producción a master](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspaces-best-practices#deployment-and-workspace-promotion) o al instalar una nueva versión en un workspace de prueba.
+
+Por este motivo, mejoramos la arquitectura de almacenamiento y la solución de partición de archivos en Site Editor. La solución optimizada almacena el contenido en archivos más pequeños y específicos, diseñados para ese tipo de contenido, en lugar de en un solo archivo grande. Este cambio reduce el tamaño de los archivos en aproximadamente un 90 %, lo que disminuye el espacio de almacenamiento necesario por página y mejora el desempeño general y la entrega de contenido.
+
+## ¿Qué se necesita hacer?
+No es necesaria ninguna acción. La actualización se implementó automáticamente en todas las tiendas VTEX que utilicen Site Editor.
+
+Si después del 12 de junio la pérdida de contenido continúa, abre un ticket para el equipo de [soporte VTEX](https://help.vtex.com/es/support).
+
diff --git a/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md b/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md
index c1db4a78d..1b7ae878b 100644
--- a/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md
+++ b/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md
@@ -27,7 +27,7 @@ Anteriormente, la funcionalidad Social Selling en inStore consistía en generar
 
 Con el cambio, inStore ahora también genera un código QR que puede ser leído por los dispositivos de los clientes, además del enlace compartible.
 
-![instore-social-selling-qr-code-share-es](https://images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/1d1c94682042d029f24d527ef8290e94/image3.png)
+![instore-social-selling-qr-code-share-es](//images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/1d1c94682042d029f24d527ef8290e94/image3.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/social-selling-share-your-instore-cart.md b/docs/announcements/es/social-selling-share-your-instore-cart.md
index 6441ae1d6..ee65bfad7 100644
--- a/docs/announcements/es/social-selling-share-your-instore-cart.md
+++ b/docs/announcements/es/social-selling-share-your-instore-cart.md
@@ -27,7 +27,7 @@ Anteriormente no era posible compartir el carrito en inStore, [solo en el ecomme
 
 Con inStore Social Selling, los vendedores de su tienda física pueden seleccionar productos y generar un enlace para compartir la **Sugerencia de carrito** con uno o más clientes a través de WhatsApp, como se muestra a continuación. También es posible copiar el enlace y compartirlo en otras redes sociales.
 
-![socialselling-ES](https://images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/7eb64840bde5bb1648e313d6277e872f/socialselling-ES.gif)
+![socialselling-ES](//images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/7eb64840bde5bb1648e313d6277e872f/socialselling-ES.gif)
 
 El vendedor puede enviar el mismo enlace a varios clientes, tantas veces como lo desee. Cada vez que una persona acceda a este enlace, se generará un nuevo carrito de compra, exactamente igual al creado en inStore. Cada carrito también estará asociado a la cuenta del vendedor y, si lo hay, al código del vendedor.
 
@@ -35,7 +35,7 @@ Sus clientes pueden acceder al carrito, realizar el pago y concluir la compra en
 
 Otra posibilidad es que el vendedor rellene los datos de entrega del cliente, elija el método de pago y luego comparta un **Enlace de pago.** De este modo, el enlace del carrito compartido ya contendrá toda la información personal. El cliente solo tiene que completar los datos de pago para finalizar la compra. Vea cómo funciona a continuación.
 
-![paymentlink ES](https://images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/1136d3cb3448664865ce0615392076d7/paymentlink_ES.gif)
+![paymentlink ES](//images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/1136d3cb3448664865ce0615392076d7/paymentlink_ES.gif)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/the-insights-dashboard-will-be-discontinued.md b/docs/announcements/es/the-insights-dashboard-will-be-discontinued.md
new file mode 100644
index 000000000..38319177e
--- /dev/null
+++ b/docs/announcements/es/the-insights-dashboard-will-be-discontinued.md
@@ -0,0 +1,39 @@
+---
+title: 'El dashboard Insights será descontinuado'
+id: 4yJtAquGwufjHFTcGwnTwr
+status: PUBLISHED
+createdAt: 2023-10-03T23:02:27.048Z
+updatedAt: 2023-10-04T15:06:15.480Z
+publishedAt: 2023-10-04T15:06:15.480Z
+contentType: updates
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: el-dashboard-insights-sera-descontinuado
+locale: es
+legacySlug: el-dashboard-insights-sera-descontinuado
+announcementImageID: ''
+announcementSynopsisES: 'A partir del 15 de octubre de 2023, no se podrá acceder al dashboard Insights debido a su descontinuación.'
+---
+
+**Insights** es un dashboard que permite dar seguimiento a la evolución de las ventas mediante una vista detallada del embudo de conversión y de las principales métricas que impactan los ingresos de tu tienda.
+
+Actualmente, solo se puede acceder al [dashboard Insights](https://help.vtex.com/es/tutorial/acompanhando-a-evolucao-das-suas-vendas--5QtyTR0jFy9gDnr4EYCjdq) a través de la dirección:
+```
+https://{nombreDeLaCuenta}.myvtex.com/admin/insights
+```
+
+A partir del 15 de octubre de 2023, no se podrá acceder al [dashboard Insights](https://help.vtex.com/es/tutorial/acompanhando-a-evolucao-das-suas-vendas--5QtyTR0jFy9gDnr4EYCjdq) debido a su descontinuación.
+
+## ¿Por qué realizamos este cambio?
+
+La información de **Insights** también se muestra en otros dashboards:
+- [Vista general de la tienda](https://help.vtex.com/es/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ)
+- [Vista general de la tienda (beta)](https://help.vtex.com/es/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46)
+
+Por lo tanto, la descontinuación de este dashboard reducirá la redundancia de la plataforma y nos permitirá enfocarnos en mantener y mejorar una experiencia unificada. Los dashboards **Vista general** de la tienda proporcionan la misma información que **Insights** y contienen datos más precisos.
+
+## ¿Qué se necesita hacer?
+
+A partir del 15 de octubre, el cambio se implementará automáticamente en todas las tiendas VTEX y no se requerirá ninguna acción de tu parte.
+
+Si deseas dar seguimiento a las métricas de ventas de tu tienda, consulta el dashboard [Vista general de la tienda](https://help.vtex.com/es/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ) o la [nueva versión de Vista general](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) (beta), que contiene la misma información que **Insights** con datos más precisos y mejor visualización.
diff --git a/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md b/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md
index 7a660224c..539d653ca 100644
--- a/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md
+++ b/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md
@@ -33,7 +33,7 @@ La revisión y la eventual adaptación de este cambio deben aplicarse a través
 
 Pasos necesarios para la revisión y adaptación:
 
-1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Personalización__: Si la página "/account/orders" tiene alguna personalización de front-end, debe migrarse y adaptarse a la nueva URL "/account#/orders". Revise y realice todas las pruebas necesarias garantizando el funcionamiento de todos los recursos personalizados.  
 3. __Enlaces del sitio__: Revise y actualice todos los enlaces personalizados del sitio y de los correos electrónicos transaccionales que antes dirigían al usuario a la URL "/account/orders". Estos enlaces ahora deben direccionar al usuario a "/account#/orders".
 
diff --git a/docs/announcements/es/the-offer-management-module-will-be-discontinued.md b/docs/announcements/es/the-offer-management-module-will-be-discontinued.md
new file mode 100644
index 000000000..3af612e5a
--- /dev/null
+++ b/docs/announcements/es/the-offer-management-module-will-be-discontinued.md
@@ -0,0 +1,34 @@
+---
+title: 'El módulo Gestión de anuncios será descontinuado'
+id: 1kQw84J88i1ziNlXX5XA5S
+status: PUBLISHED
+createdAt: 2023-10-05T12:50:25.536Z
+updatedAt: 2023-10-05T13:51:31.119Z
+publishedAt: 2023-10-05T13:51:31.119Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: el-modulo-gestion-de-anuncios-sera-descontinuado
+locale: es
+legacySlug: el-modulo-gestion-de-anuncios-sera-descontinuado
+announcementImageID: ''
+announcementSynopsisES: 'El módulo Gestión de anuncios solo estará disponible para integración con Mercado Libre.'
+---
+
+Con el objetivo de ofrecer la mejor experiencia a nuestros clientes, anunciamos la descontinuación del módulo Gestión de anuncios del Admin VTEX.
+
+Los anuncios enviados a los marketplaces no se verán afectados y todavía puedes consultar el status de cada uno accediendo a **Marketplace > Conexiones > Productos en el Admin VTEX.**
+
+## ¿Qué cambió?  
+
+Removimos del módulo Gestión de anuncios la posibilidad de hacer un seguimiento del status y la sincronización de los anuncios enviados a un marketplace.  
+Las funcionalidades de [Moderación](https://help.vtex.com/es/tutorial/gerenciamento-de-anuncios-moderacao-e-qualidade-dos-anuncios-do-mercado--xSbPzA41jiWPAorlBCEA4?&utm_source=autocomplete#moderacao), [Calidad](https://help.vtex.com/es/tutorial/gerenciamento-de-anuncios-moderacao-e-qualidade-dos-anuncios-do-mercado--xSbPzA41jiWPAorlBCEA4?&utm_source=autocomplete#qualidade) y [Oportunidades activas](https://help.vtex.com/es/tutorial/anuncios-enviados-oportunidades-de-buybox--1hO9eI1th47EGxQoTzGewC) estarán disponibles hasta el 15 de diciembre de 2023, únicamente para anuncios vinculados a la integración [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/51oWBHvVxSs8eAwLQhSbSd), accediendo a **Marketplace > Mercado Libre > Gestión de anuncios.**
+
+## ¿Qué se necesita hacer?
+
+Esta actualización es automática y no se requiere ninguna acción por tu parte. El módulo dejará de estar disponible para todos los Admin VTEX a partir de la fecha anteriormente indicada.
+
+<div class="alert alert-info">
+Pronto pondremos a disposición un reemplazo del módulo Gestión de anuncios; accede a las novedades en la página <a href="https://developers.vtex.com/updates/release-notes">Release notes, dentro del Developer portal</a> y <a href="https://help.vtex.com/es/announcements">en la pestaña Noticias de nuestro Help Center</a>.
+</div>
+
diff --git a/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md b/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md
index 9105f2461..fc189e4f2 100644
--- a/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md
+++ b/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md
@@ -18,7 +18,7 @@ announcementSynopsisES: 'Lanzamiento de una nueva herramienta de auditoría'
 
 Siempre en línea con las mejores prácticas de seguridad y transparencia para tu tienda, VTEX ha lanzado un nuevo recurso de auditoría: **Audit**. 
 
-![Screenshot for Audit UI for announcement](https://images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/e5e64ab35e499176c8815260dd703e00/Audit_ES.png)
+![Screenshot for Audit UI for announcement](//images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/e5e64ab35e499176c8815260dd703e00/Audit_ES.png)
 
 A partir de ahora, los administradores pueden verificar las distintas operaciones que se han realizado en su tienda de forma sencilla y rápida. Es posible crear varios filtros para facilitar la búsqueda de eventos y aumentar la velocidad de los procesos de auditoría.
 
diff --git a/docs/announcements/es/troubleshooting-guides-your-new-vtex-self-service-experience.md b/docs/announcements/es/troubleshooting-guides-your-new-vtex-self-service-experience.md
new file mode 100644
index 000000000..c8a3ca550
--- /dev/null
+++ b/docs/announcements/es/troubleshooting-guides-your-new-vtex-self-service-experience.md
@@ -0,0 +1,53 @@
+---
+title: 'Guías de resolución de problemas: tu nueva experiencia de autoservicio de soporte técnico en VTEX'
+id: 5oDp5raqBpRta660NERceY
+status: PUBLISHED
+createdAt: 2024-07-08T15:04:53.687Z
+updatedAt: 2024-07-08T21:47:04.455Z
+publishedAt: 2024-07-08T21:47:04.455Z
+contentType: updates
+productTeam: Others
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: guias-de-resolucion-de-problemas-tu-nueva-experiencia-de-autoservicio-de
+locale: es
+legacySlug: guias-de-resolucion-de-problemas-tu-nueva-experiencia-de-autoservicio-de
+announcementImageID: ''
+announcementSynopsisES: 'Resuelve problemas con mayor rapidez y autonomía con nuestras guías de resolución de problemas reformuladas.'
+---
+
+VTEX está en constante evolución para mejorar la experiencia de soporte al cliente, capacitándolo para resolver problemas de manera más eficaz y autónoma. 
+Con el objetivo de facilitar el proceso de soporte, ahora tienes acceso a las Guías de resolución de problemas disponibles en el [Help Center](https://help.vtex.com/es/category/troubleshooting--39pDkp8qxSll6mGj0tWViz) y [Developer Portal](https://developers.vtex.com/docs/troubleshooting). Estas guías explican los posibles escenarios de error tanto en las operaciones como en el desarrollo de la tienda o aplicaciones, proporcionando orientación sobre cómo restaurar el desempeño esperado de tu tienda.
+
+<div class="alert alert-info" role="alert"> 
+  ¿Deseas contribuir a esta iniciativa? Rellena este <a href="https://forms.gle/PdVNZmMDMjiDfJaf8">Formulario de feedback</a>.
+</div>
+
+## ¿Cómo están organizadas las guías de resolución de problemas?
+Las guías de resolución de problemas están disponibles en el [Help Center](https://help.vtex.com/es/category/troubleshooting--39pDkp8qxSll6mGj0tWViz) e [Developer Portal](https://developers.vtex.com/docs/troubleshooting), y se dividen en las siguientes categorías:
+
+- [Help Center](https://help.vtex.com/es/category/troubleshooting--39pDkp8qxSll6mGj0tWViz):
+  - [Operaciones de la tienda](https://help.vtex.com/es/subcategory/operaciones-de-la-tienda--2Q0IQjRcOqSgJTh6wRHVMB): sección destinada a resolver las dificultades encontradas en las operaciones de la plataforma y tiendas de ecommerce.
+
+- [Developer Portal](https://developers.vtex.com/docs/troubleshooting)
+  - **Development**: sección destinada a tratar errores relacionados con el desarrollo de storefronts y aplicaciones.
+  - **Store performance**: sección con procedimientos para depurar errores y restaurar el funcionamiento de la tienda en caso de que esté inoperativa o fuera de línea. 
+
+<div class="alert alert-info" role="alert"> 
+En el momento de la publicación de este anuncio, ya están disponibles 15 guías para consulta y se están elaborando más.
+</div>
+
+## ¿Por qué creamos esta iniciativa?
+Nuestro objetivo es hacer que la experiencia de soporte de VTEX sea más sencilla y eficiente. Con las nuevas guías de resolución de problemas podrás:
+
+- **Identificar problemas más rápidamente:** las descripciones detalladas de escenarios de operación de la tienda y desarrollo ayudan en la identificación de problemas que puedas estar experimentando.
+- **Encontrar soluciones para cada caso presentado:** procedimientos precisos sobre los pasos necesarios para solucionar los errores identificados.
+- **Tener mayor autonomía en la gestión de fallas:** posibilidad de resolver errores internamente, en cualquier momento y sin necesidad de abrir tickets con el soporte técnico.
+
+## ¿Cómo puedes ayudar?
+Nos comprometemos a ampliar y mejorar de forma continua esta iniciativa, explorando nuevos escenarios de problemas y publicando regularmente más guías de resolución de problemas. Valoramos enormemente tus comentarios para asegurarnos de que avanzamos en la dirección correcta.
+
+¿Deseas contribuir?
+
+- **Comparte tu opinión:** rellena nuestro [Formulario de feedback](https://forms.gle/PdVNZmMDMjiDfJaf8) con tus sugerencias o críticas sobre las nuevas guías de resolución de problemas.
+- **¿Hablamos?:** si deseas compartir tu experiencia con nuestra documentación en más detalle o sugerir mejoras específicas sobre el Help Center y Developer Portal, rellena el [Formulario de feedback](https://forms.gle/PdVNZmMDMjiDfJaf8) y nos pondremos en contacto contigo en hasta 5 días laborables para programar una cita con nuestro equipo de Education.
+
diff --git a/docs/announcements/es/update-grants-in-the-promotions-module.md b/docs/announcements/es/update-grants-in-the-promotions-module.md
index e0d2e0bf9..9f5e5e4ea 100644
--- a/docs/announcements/es/update-grants-in-the-promotions-module.md
+++ b/docs/announcements/es/update-grants-in-the-promotions-module.md
@@ -37,6 +37,6 @@ Con esta actualización, usted tiene más poder sobre el comportamiento de sus p
  6. Haga clic en **Utilizar configuraciones de recurrencia**
  7. Establezca la configuración deseable de días y horarios para la promoción
 
-![CRON 2 ES](https://images.ctfassets.net/alneenqid6w5/7b6Kfpi1jxXcrr1qrPSycM/f08e20b7f69d579ff8b9d6f79bf19b01/CRON_2_ES.png)
+![CRON 2 ES](//images.ctfassets.net/alneenqid6w5/7b6Kfpi1jxXcrr1qrPSycM/f08e20b7f69d579ff8b9d6f79bf19b01/CRON_2_ES.png)
 
  
diff --git a/docs/announcements/es/update-of-the-external-privacy-notice.md b/docs/announcements/es/update-of-the-external-privacy-notice.md
new file mode 100644
index 000000000..805031489
--- /dev/null
+++ b/docs/announcements/es/update-of-the-external-privacy-notice.md
@@ -0,0 +1,39 @@
+---
+title: 'Actualización del Aviso de Privacidad Externo'
+id: fpUnEC85ixK1vNzXQSrTY
+status: PUBLISHED
+createdAt: 2024-07-02T23:52:09.837Z
+updatedAt: 2024-07-03T14:07:13.062Z
+publishedAt: 2024-07-03T14:07:13.062Z
+contentType: updates
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: actualizacion-del-aviso-de-privacidad-externo
+locale: es
+legacySlug: actualizacion-del-aviso-de-privacidad-externo
+announcementImageID: ''
+announcementSynopsisES: 'Actualizamos el Aviso de Privacidad sobre el tratamiento de datos personales de Shoppers en VTEX.'
+---
+
+Hemos revisado el [Aviso de Privacidad](https://vtex.com/mx-es/privacy-and-agreements/external-notice/) que detalla la manera en que VTEX trata los datos personales de los Shoppers, es decir, quienes acceden a los entornos de tiendas online controladas por los retailers, que son clientes directos de VTEX.
+
+El documento contiene información sobre los siguientes aspectos:
+
+* Datos personales tratados por VTEX y su finalidad
+* Periodo de retención de los datos
+* Derechos de los titulares de datos
+* Prácticas de protección de datos personales adoptadas por VTEX
+* Almacenamiento de datos personales en la nube
+* Compartir datos con partners
+
+## ¿Qué cambió?
+
+La nueva versión del Aviso incorpora las prácticas de privacidad más recientes de VTEX para el tratamiento de datos personales en la Plataforma VTEX, presentadas de manera clara, concisa y dirigida a los Shoppers.
+
+## ¿Por qué realizamos este cambio?
+
+Hemos actualizado nuestro Aviso de Privacidad de acuerdo con la legislación vigente y nuestras certificaciones globales de privacidad, que recomiendan actualizaciones periódicas. Además, hemos creado políticas de privacidad separadas para procesos de reclutamiento, empleados y eventos, cada una en documentos específicos.
+
+## ¿Qué se necesita hacer?
+
+No es necesaria ninguna acción. El documento ya está disponible en todos los idiomas en el sitio web de VTEX. Para más información, accede al nuevo [Aviso de Privacidad Externo](https://vtex.com/mx-es/privacy-and-agreements/external-notice/) y a la guía de onboarding de [Datos y privacidad](https://help.vtex.com/es/tracks/datos-y-privacidad--4Lc0i0an0DgnEtB0AUwlcq).
diff --git a/docs/announcements/es/upgrade-your-store-to-google-analytics-4.md b/docs/announcements/es/upgrade-your-store-to-google-analytics-4.md
index 7c18f83a0..859d024c5 100644
--- a/docs/announcements/es/upgrade-your-store-to-google-analytics-4.md
+++ b/docs/announcements/es/upgrade-your-store-to-google-analytics-4.md
@@ -3,8 +3,8 @@ title: 'Actualiza tu tienda a Google Analytics 4'
 id: 01mmrSck8nvXAKsypecT9V
 status: PUBLISHED
 createdAt: 2023-04-28T14:42:52.792Z
-updatedAt: 2023-05-03T17:47:48.884Z
-publishedAt: 2023-05-03T17:47:48.884Z
+updatedAt: 2023-07-17T13:38:03.472Z
+publishedAt: 2023-07-17T13:38:03.472Z
 contentType: updates
 productTeam: Shopping
 author: 1malnhMX0vPThsaJaZMYm2
@@ -17,7 +17,7 @@ announcementSynopsisES: 'actualiza-tu-tienda-a-google-analytics-4'
 
 A partir del 1 de julio de 2023, [Google Analytics 4](https://support.google.com/analytics/answer/10089681) (GA4) sustituirá a Universal Analytics, la versión anterior de la herramienta de análisis de datos de Google. Consulta los detalles sobre los cambios implementados [en este comunicado de Google](https://support.google.com/analytics/answer/11583528).
 
-Para seguir monitoreando los datos de navegación en tu tienda VTEX, deberás crear una propiedad GA4 y adaptar algunas configuraciones, si utilizas el [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) o [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
+Para seguir monitoreando los datos de navegación en tu tienda VTEX, deberás crear una propiedad GA4 y adaptar algunas configuraciones, si utilizas el [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) o [VTEX IO - Store Framework](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
 
 ## ¿Qué cambió?
 
@@ -25,15 +25,15 @@ Universal Analytics dejará de procesar eventos el 1 de julio de 2023. Por lo ta
 
 Para garantizar la compatibilidad de las tiendas VTEX debes crear un registro en Google Analytics 4 y ajustar las configuraciones de tu cuenta en Google Tag Manager como se especifica en el artículo [Configurar Google Analytics 4 en tiendas VTEX](https://help.vtex.com/es/tutorial/como-configurar-el-google-analytics-en-tienda-vtex--G2P0rmSrEiqCcmUMyUUwG).
 
-Las tiendas que utilizan VTEX IO también necesitan configurar [la aplicación Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager) para realizar la integración con Google Analytics 4. 
+Las tiendas que utilizan VTEX IO - Store Framework también necesitan configurar [la aplicación Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager) para realizar la integración con Google Analytics 4. 
 
 ## ¿Por qué realizamos este cambio?
 
-Implementamos el cambio para permitir que las tiendas VTEX que utilizan el [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) o [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) continúen siendo compatibles con Google Analytics 4. De este modo, seguirá siendo posible obtener datos de navegación relevantes a través de la versión más actual de la herramienta de Google.
+Implementamos el cambio para permitir que las tiendas VTEX que utilizan el [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) o [VTEX IO - Store Framework](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) continúen siendo compatibles con Google Analytics 4. De este modo, seguirá siendo posible obtener datos de navegación relevantes a través de la versión más actual de la herramienta de Google.
 
 ## ¿Qué se necesita hacer?
 
 Para que tu tienda sea compatible con la nueva herramienta de análisis de datos de Google, sigue las instrucciones de la guía [Configurar Google Analytics 4 en tiendas VTEX](https://help.vtex.com/es/tutorial/como-configurar-el-google-analytics-en-tienda-vtex--G2P0rmSrEiqCcmUMyUUwG).
 
-Si tu tienda utiliza [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), será necesário activar una configuración en el Admin VTEX, `Send events in GA4 format`, y configurar la aplicación para recibir actualizaciones de Google Analytics 4. Para más información, accede a [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+Si tu tienda utiliza [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), será necesário activar una configuración en el Admin VTEX, `Send events in GA4 format`, y configurar la aplicación para recibir actualizaciones de Google Analytics 4. Para más información, accede a [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
diff --git a/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md b/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
index 721315711..7dcdf4a85 100644
--- a/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
+++ b/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
@@ -33,5 +33,5 @@ La funcionalidad puede ser utilizada siempre que el administrador de la tienda d
 - En  “¿Cuál es el tipo y el valor de la tasa?”, escoja la opción Tasa Nominal
 - Complete los ítems necesarios y haga clic en guardar
 
-![Nominal tax ES](https://images.ctfassets.net/alneenqid6w5/2qg2CsNALcvSojlXkcJkvI/3bdf5a1e180bc33a30efa9b99a802aaf/Nominal_tax_ES.png)
+![Nominal tax ES](//images.ctfassets.net/alneenqid6w5/2qg2CsNALcvSojlXkcJkvI/3bdf5a1e180bc33a30efa9b99a802aaf/Nominal_tax_ES.png)
 
diff --git a/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md b/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md
index 55758f6fc..20441c382 100644
--- a/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md
+++ b/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md
@@ -23,7 +23,7 @@ Con el objetivo de continuar perfeccionando esa experiencia, incluimos una valid
 
 Antes, un consumidor podía seleccionar una tarjeta vencida y realizar una compra, cuyo pago luego sería rechazado. Ahora, señalamos las tarjetas caducadas y evitamos que sean seleccionadas en el checkout, para una experiencia de compra más fluida.
 
-![ES - Expired Cards](https://images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/276fcf10f19f3c8ec703547d75e2aa5d/ES_-_Expired_Cards.png)
+![ES - Expired Cards](//images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/276fcf10f19f3c8ec703547d75e2aa5d/ES_-_Expired_Cards.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/vtex-insurance-discontinuity.md b/docs/announcements/es/vtex-insurance-discontinuity.md
new file mode 100644
index 000000000..07e03d2eb
--- /dev/null
+++ b/docs/announcements/es/vtex-insurance-discontinuity.md
@@ -0,0 +1,29 @@
+---
+title: 'Descontinuación de VTEX Insurance'
+id: 413Jet3S6F49mmlQzZ7Bev
+status: PUBLISHED
+createdAt: 2024-01-19T19:54:48.085Z
+updatedAt: 2024-01-29T21:49:24.406Z
+publishedAt: 2024-01-29T21:49:24.406Z
+contentType: updates
+productTeam: Others
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: descontinuidad-del-seguro-vtex
+locale: es
+legacySlug: descontinuidad-del-seguro-vtex
+announcementImageID: ''
+announcementSynopsisES: 'VTEX Insurance dejará de ser un producto VTEX, pero continuará existiendo como Assurant Digital.'
+---
+
+Desde el 11 de diciembre de 2023, se descontinuó VTEX Insurance de VTEX y se migraron sus funcionalidades a Assurant Digital.
+
+**VTEX Insurance** era una aplicación que permitía al retailer vincular los productos vendidos con ofertas de seguros de la aseguradora partner [Assurant](https://www.assurant.com.br/). Esta funcionalidad permitía que la tienda ofreciera seguros personalizados a los clientes para brindar protección financiera en caso de fallos o defectos en el producto o servicio adquirido.
+
+# ¿Qué cambió?
+No habrá cambios contractuales o comerciales, ya que el contrato era entre los clientes y Assurant. El principal cambio reside en la asistencia al cliente, que antes la realizaban los equipos de ambas empresas y ahora estará exclusivamente a cargo de Assurant.
+
+# ¿Qué se necesita hacer?
+No se requiere ninguna acción. La actualización se aplicará automáticamente a todas las tiendas VTEX. Cualquier duda técnica u otros problemas relacionados al producto se deben dirigir directamente a [Assurant](https://www.assurant.com.br/).
+
+<div class = "alert alert-warning"> VTEX no prestará soporte técnico a los clientes.</div>
+
diff --git a/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md b/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
new file mode 100644
index 000000000..0249545d7
--- /dev/null
+++ b/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
@@ -0,0 +1,37 @@
+---
+title: 'VTEX Intelligent Search: nuevo Editor visual de Reglas de merchandising'
+id: 63xoRkTEoqllK6KKadys51
+status: PUBLISHED
+createdAt: 2024-01-30T13:15:08.893Z
+updatedAt: 2024-01-31T17:00:02.465Z
+publishedAt: 2024-01-31T17:00:02.465Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-intelligent-search-nuevo-editor-visual-de-reglas-de-merchandising
+locale: es
+legacySlug: vtex-intelligent-search-nuevo-editor-visual-de-reglas-de-merchandising
+announcementImageID: ''
+announcementSynopsisES: 'Descubre el Editor visual de Reglas de merchandising en VTEX Intelligent Search.'
+---
+
+[Reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) es la funcionalidad que maneja los resultados dentro de la búsqueda en tiendas que utilizan [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Este recurso permite ofrecer productos más relevantes para el cliente y agregar u ocultar los productos preseleccionados por la búsqueda.
+
+Con el fin de ofrecer una experiencia más visual, completa e intuitiva, lanzamos una nueva opción de editor para crear reglas de merchandising.
+
+## ¿Qué cambió?
+
+Antes, las tiendas que utilizaban [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) solo contaban con el [Editor manual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) de Reglas de merchandising. Ahora, la nueva opción del [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr) está disponible y permite:
+
+* Generar una vista previa que muestra los resultados de búsqueda tal como los verán los clientes al navegar por la tienda.
+* Reordenar los resultados de búsqueda.
+* Fijar un producto en las primeras posiciones de los resultados de búsqueda.
+* Analizar la información principal del producto.
+
+![visual-merch-rules-ES-announcement](//images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/5230eea36b9eb3014e45d1f988d6057d/visual-merch-rules-ES-announcement.png)
+
+Al crear una regla de merchandising en el Admin VTEX en **Storefront > Intelligent Search > Reglas de merchandising > Agregar** puedes escoger el tipo de editor que deseas utilizar. Consulta la guía [Reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicion) para más información sobre las diferencias entre el Editor manual y el Editor visual.
+
+## ¿Qué se necesita hacer?
+
+No se requiere ninguna acción; el nuevo editor está disponible para todos las tiendas que utilizan [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Consulta la guía [Crear regla de merchandising - Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr) para más información.
diff --git a/docs/announcements/es/vtex-io-documentation-has-a-new-home.md b/docs/announcements/es/vtex-io-documentation-has-a-new-home.md
index 1ede9649b..e10c57a0d 100644
--- a/docs/announcements/es/vtex-io-documentation-has-a-new-home.md
+++ b/docs/announcements/es/vtex-io-documentation-has-a-new-home.md
@@ -19,7 +19,7 @@ Desde el 13 de marzo de 2020, la documentación de VTEX IO y VTEX IO Store Frame
 
 Se puede acceder a esta documentación a través de [**VTEX IO Docs**](https://vtex.io/docs), una plataforma de documentación que reúne todos los contenidos disponibles en ambas soluciones. 
 
-![vtex-io-docs](https://images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/d22c3ecd05c9fecccdba405a83e61d30/vtex-io-docs.png)
+![vtex-io-docs](//images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/d22c3ecd05c9fecccdba405a83e61d30/vtex-io-docs.png)
 
 ## ¿Por qué estamos haciendo este cambio?
 
@@ -33,7 +33,7 @@ La decisión de eliminar la documentación de VTEX IO y VTEX IO Store Framework
 
 Con nuestra [documentación de la API](https://developers.vtex.com/reference), [guías](https://developers.vtex.com/docs) dirigidas a los desarrolladores que trabajan con integraciones, personalizaciones y  [Release Notes](https://developers.vtex.com/changelog)  sincronizadas con todo lo nuevo de nuestro producto, el [**Developer Portal**](https://developers.vtex.com) - antiguo Developer Docs del Help Center - ofrece en un solo lugar todos los recursos necesarios para los usuarios más técnicos de VTEX. 
 
-![developer-portal](https://images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/7785b5da696fe5e428e742a93abb654f/developer-portal.png)
+![developer-portal](//images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/7785b5da696fe5e428e742a93abb654f/developer-portal.png)
 
 Con el fin de mejorar la experiencia de desarrollo en VTEX, el Developer Portal pronto contará también con la documentación de VTEX IO y VTEX IO Store Framework - disponible hoy en VTEX IO Docs. 
 
diff --git a/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md b/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md
index 6cc15566c..84daea5c9 100644
--- a/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md
+++ b/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'El VTEX Admin tiene tres nuevas opciones de idioma.'
 
 El panel de VTEX ahora admite diferentes opciones de idiomas para atender a nuestros clientes en todo el mundo. Localizamos nuestro producto para mejorar su experiencia en general, no solo mediante traducciones, sino también a nivel cultural al tomar en cuenta las particularidades de cada país.  
 
-![ES new locales](https://images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/bb1e1ac7fefbeccdc3d9d6d05883cc6a/ES_new_locales.jpg)
+![ES new locales](//images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/bb1e1ac7fefbeccdc3d9d6d05883cc6a/ES_new_locales.jpg)
 
 ## ¿Qué cambió?
 Además de portugués, inglés, español, italiano, rumano y japonés, a partir de mayo de 2021, los usuarios VTEX encontrarán tres nuevas opciones de idioma en nuestro panel del admin: neerlandés, francés y coreano. 
diff --git a/docs/announcements/es/vtex-launches-the-new-version-of-instore-vtex-sales-app.md b/docs/announcements/es/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
index a0069c779..b49ec39d5 100644
--- a/docs/announcements/es/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
+++ b/docs/announcements/es/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
@@ -29,7 +29,7 @@ El nuevo menú aporta beneficios significativos, que destacamos a continuación:
 * **Navegación intuitiva:** organización mejorada para encontrar rápidamente lo que se está buscando.
 * **Coherencia visual:** apariencia alineada con otras actualizaciones recientes de nuestra plataforma.
 
-<img src="https://images.ctfassets.net/alneenqid6w5/pcXNfExZYZML7AHP57tzz/34a7a68e115b780bcdb60bbf516f389d/image.png" alt= “menu-sales-app-es” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/pcXNfExZYZML7AHP57tzz/34a7a68e115b780bcdb60bbf516f389d/image.png" alt= “menu-sales-app-es” width="35%" height="35%">
 
 ### Área de anuncios
 
@@ -37,13 +37,13 @@ El área de anuncios permite que los administradores de las tiendas muestren pro
 
 Uno de los principales recursos de esta actualización es la opción de que los administradores de las tiendas establezcan la nueva área de anuncios como página de inicio. Esto permite una experiencia de usuario más personalizada, ya que los clientes, en cuanto acceden, se encuentran inmediatamente con contenido seleccionado y recomendaciones de productos. Más información en el artículo [Habilitar Venta de inventario local en VTEX Sales App](https://help.vtex.com/es/tutorial/habilitar-venta-de-inventario-local-en-vtex-sales-app--54eQN4rOH5yBYPGG2w8v9q).
 
-<img src="https://images.ctfassets.net/alneenqid6w5/XXJQykcV9p6yNN6Q5mB5u/7a3b82fcbf53f2502aab0e236f6f6585/image.png" alt= “anuncio-sale-app-es” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/XXJQykcV9p6yNN6Q5mB5u/7a3b82fcbf53f2502aab0e236f6f6585/image.png" alt= “anuncio-sale-app-es” width="35%" height="35%">
 
 ### Desempeño de ventas
 
 La sección Desempeño de ventas permite al administrador de la tienda acceder a las métricas de ventas de su tienda, mostrando la comparación de desempeño entre periodos de ventas y también de los empleados. Más información en el artículo [VTEX Sales App: Rendimiento de Ventas](https://help.vtex.com/es/tutorial/sales-app-rendimiento-de-ventas--7i4Elt835tatBM6iqZoc56).
 
-<img src="https://images.ctfassets.net/alneenqid6w5/3UWhX6QODOG8pQ6Xi0QXKV/c787fdddf2e386e56342ab50a7d154fa/image.png" alt= “vendas-da-loja-sales-app-es” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/3UWhX6QODOG8pQ6Xi0QXKV/c787fdddf2e386e56342ab50a7d154fa/image.png" alt= “vendas-da-loja-sales-app-es” width="35%" height="35%">
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/vtex-marketplace-launches-in-2022.md b/docs/announcements/es/vtex-marketplace-launches-in-2022.md
index addca80c4..02d696746 100644
--- a/docs/announcements/es/vtex-marketplace-launches-in-2022.md
+++ b/docs/announcements/es/vtex-marketplace-launches-in-2022.md
@@ -29,7 +29,7 @@ Nuestras nuevas funcionalidades permiten a los _marketplaces_:
 
 Ve más allá del ecommerce tradicional con las [novedades de Marketplace de VTEX](https://content.vtex.com/es/2022-marketplace-release/?utm_source=announcement&utm_medium=organic&utm_campaign=2022_marketplace_release).
 
-![capa de blog marketplace 2022](https://images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/20f7d7d151a3dbd76d0d69e5858510d0/capa_de_blog.png)
+![capa de blog marketplace 2022](//images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/20f7d7d151a3dbd76d0d69e5858510d0/capa_de_blog.png)
 
 ## ¿Qué estamos lanzando?
 
@@ -78,7 +78,7 @@ Obtén más información sobre cada característica a continuación.
 
 ### Seller Portal
 
-![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
 
 Seller Portal es una edición de la plataforma VTEX destinada a que los [sellers](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#vender-em-marketplace) se conecten y vendan sus productos en los _marketplaces_ hospedados en VTEX. Con el portal, los _sellers_ acceden a todas las funcionalidades esenciales para la operación del ecommerce en grandes vitrinas, aportando visibilidad y conversión de ventas.
 
@@ -126,7 +126,7 @@ Para facilitar que los nuevos _sellers_ se unan al Seller Portal, también hemos
 
 ### Gestión de sellers
 
-![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 Hemos lanzado la experiencia renovada de la página [Gestión de sellers](https://help.vtex.com/es/tutorial/gerenciamento-de-sellers-beta--6eEiOISwxuAWJ8w6MtK7iv), donde los operadores de los _marketplaces_ [agregan sellers](https://help.vtex.com/es/tutorial/adicionar-seller-beta--6q4G4RNqVENr5YMJyindwL), registran su información respectiva y gestionan el status de cada _seller_.
 
diff --git a/docs/announcements/es/vtex-sales-app-will-no-longer-be-available-for-windows.md b/docs/announcements/es/vtex-sales-app-will-no-longer-be-available-for-windows.md
new file mode 100644
index 000000000..e922f2376
--- /dev/null
+++ b/docs/announcements/es/vtex-sales-app-will-no-longer-be-available-for-windows.md
@@ -0,0 +1,36 @@
+---
+title: 'VTEX Sales App ya no estará disponible como una aplicación en Windows'
+id: 1wcqeNs1AyppGdu20FjAJ8
+status: PUBLISHED
+createdAt: 2023-08-02T15:12:02.978Z
+updatedAt: 2023-08-03T16:00:53.203Z
+publishedAt: 2023-08-03T16:00:53.203Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-sales-app-ya-no-estara-disponible-en-windows
+locale: es
+legacySlug: vtex-sales-app-ya-no-estara-disponible-en-windows
+announcementImageID: ''
+announcementSynopsisES: 'VTEX Sales App ya no tendrá más soporte como aplicación nativa en Windows. Solo estará disponible en la interfaz web.'
+---
+
+Como parte de nuestros esfuerzos para mejorar la experiencia del usuario, anunciamos la descontinuación de VTEX Sales App en Windows.
+
+## ¿Qué cambió?
+
+A partir del 31/10/23, VTEX Sales App no estará disponible para Windows.
+
+## ¿Qué se necesita hacer?
+
+La actualización se va a ejecutar automáticamente en todas las tiendas VTEX que utilizan VTEX Sales App. Para entrar desde una computadora con Windows, o cualquier sistema operativo, será necesario acceder a la versión web de VTEX Sales App, utilizando la siguiente URL:
+
+```
+https://{nombre de la cuenta}.myvtex.com/assisted-sales/sales-app
+```
+Para más información sobre VTEX Sales App, consulta los siguientes artículos:
+
+* [VTEX Sales App - Primeros pasos y configuración](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc#)
+* [VTEX Sales App - Pagos](https://help.vtex.com/es/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy#)
+* [VTEX Sales App - Uso de la aplicación](https://help.vtex.com/es/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr#)
+* [Estrategias de comercio unificado](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv#)
diff --git a/docs/announcements/es/web-page-performance-deprecation.md b/docs/announcements/es/web-page-performance-deprecation.md
new file mode 100644
index 000000000..dde2a1d92
--- /dev/null
+++ b/docs/announcements/es/web-page-performance-deprecation.md
@@ -0,0 +1,25 @@
+---
+title: 'Discontinuación del módulo Rendimiento de Páginas Web'
+id: 4zrnpCSC8R8OFpahiaf2sE
+status: PUBLISHED
+createdAt: 2024-05-29T17:50:25.024Z
+updatedAt: 2024-05-29T19:04:53.248Z
+publishedAt: 2024-05-29T19:04:53.248Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: discontinuacion-rendimiento-de-paginas-web
+locale: es
+legacySlug: discontinuacion-del-modulo-rendimiento-de-paginas-web
+announcementImageID: ''
+announcementSynopsisES: 'El módulo Rendimiento de Página Web quedará obsoleto.'
+---
+
+El **04 de junio de 2024** deshabilitaremos el **módulo Rendimiento de Página Web** del VTEX Admin. El módulo permitió a los retailer monitorear las métricas de desempeño de las URL de sus ecommerce presentadas por [PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about) directamente en la plataforma VTEX.  
+
+A partir de ahora, los retailers podrán [monitorear y optimizar](https://developers.google.com/speed?hl=es-419) estas métricas a través de la página [PageSpeed Insights](https://pagespeed.web.dev/).  
+
+## ¿Qué se necesita hacer?
+
+En esta discontinuación, el retailer no necesita realizar ninguna acción. Los módulos [Vista General de la Tienda](https://help.vtex.com/es/tutorial/vista-general-de-la-tienda--P8ahguoRs0U3PzmXg2wuQ) y [Desempeño de Ventas](https://help.vtex.com/es/tutorial/desempeno-de-ventas--3DMube0sEsK9vPcRYGas72) seguirán disponibles en el VTEX Admin.
+
diff --git a/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md
index c544ba47c..af55cf104 100644
--- a/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md
@@ -19,7 +19,7 @@ Las empresas digitales buscan cada vez más contar con herramientas que les perm
 
 Bienvenido a la [experiencia del nuevo Admin VTEX](https://content.vtex.com/join-new-admin-beta-program-es/?utm_source=announcement&utm_medium=organic&utm_campaign=new_admin_beta).
 
-![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/weve-released-our-new-cross-selling-and-up-selling-apis.md b/docs/announcements/es/weve-released-our-new-cross-selling-and-up-selling-apis.md
index 8b2c7013b..adadda60a 100644
--- a/docs/announcements/es/weve-released-our-new-cross-selling-and-up-selling-apis.md
+++ b/docs/announcements/es/weve-released-our-new-cross-selling-and-up-selling-apis.md
@@ -3,8 +3,8 @@ title: 'Lanzamos nuestras nuevas API de Cross-selling y Up-selling'
 id: 37Lc6sI2owMCiUamocgAcc
 status: PUBLISHED
 createdAt: 2017-12-04T18:54:28.850Z
-updatedAt: 2020-05-11T19:43:09.938Z
-publishedAt: 2020-05-11T19:43:09.938Z
+updatedAt: 2024-01-04T15:05:24.804Z
+publishedAt: 2024-01-04T15:05:24.804Z
 contentType: updates
 productTeam: Marketing & Merchandising
 author: 245tA425AIeioKAk2eaiwS
@@ -73,6 +73,6 @@ Esta API devolverá los productos que también se han registrado como __sugerenc
 
 ## Saber más
 
-Para obtener más información sobre las llamadas, acceda a nuestra [documentación de APIs](https://developers.vtex.com/reference/crossselling#productsearchwhosawalsosaw).
+Para obtener más información sobre las llamadas, acceda a nuestra [documentación de APIs](https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/products/crossselling/whosawalsosaw/-productId-?endpoint=get-/api/catalog_system/pub/products/crossselling/whosawalsosaw/-productId-).
 
 Para más informaciones sobre las modalidades de Cross-selling y Up-Selling descritas arriba, acceda al [artículo del VTEX Help](/es/tutorial/configurando-produto-similar-sugestoes-acessorios-e-genericos)
diff --git a/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md b/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md
index 2cd87eb11..851198379 100644
--- a/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md
+++ b/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md
@@ -24,7 +24,7 @@ La aplicación está disponible en [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Inclusión de un ícono de corazón al lado de cada producto en las listas de productos y en las páginas de detalle de los productos.
 - Creación de una página para la Lista de Deseos, donde el consumidor pueda ver todos los artículos y comprarlos fácilmente.
 
-![Wishlist Printscreen](https://images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
+![Wishlist Printscreen](//images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
 
 ## ¿Cuáles son los beneficios?
 - Hace que la experiencia de compra de su tienda sea más completa.
diff --git a/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 55303f276..d977ae0c4 100644
--- a/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -21,7 +21,7 @@ A partir del 25 de junio de 2019, el usuario que no tenga acceso vinculado al pe
 
 Con el fin de garantizar una mayor seguridad, creamos la posibilidad de limitar perfiles de acceso en la pantalla **Configuración**, permitiendo que solo algunos usuarios editen las informaciones.
 
-![2019-06-07 17 24 38-Configuración.es](https://images.ctfassets.net/alneenqid6w5/1SrUApvjjUxaUZRJfJnqwB/b597be4eb4343dbf03e74feee5cb5cdc/2019-06-07_17_24_38-Configuraci__n.es.png)
+![2019-06-07 17 24 38-Configuración.es](//images.ctfassets.net/alneenqid6w5/1SrUApvjjUxaUZRJfJnqwB/b597be4eb4343dbf03e74feee5cb5cdc/2019-06-07_17_24_38-Configuraci__n.es.png)
 
 ## Principales ventajas
 
@@ -41,6 +41,6 @@ Para hacer esto es necesario añadir un producto llamado `Checkout` al perfil de
  6. Elija el tipo de permiso deseado: `Save Order Configuration`, para permitir al usuario editar la sección **Pedidos**, o `Save OrderForm Configuration`, para permitir al usuario editar la sección **Carrito**.
  7. Haga clic en **Guardar**
 
-![GIT-Checkout.es](https://images.ctfassets.net/alneenqid6w5/245LTWQExeQEmDWb7HrAyZ/9acea81b01288dd051acffec409a2984/GIT-Checkout.es.gif)
+![GIT-Checkout.es](//images.ctfassets.net/alneenqid6w5/245LTWQExeQEmDWb7HrAyZ/9acea81b01288dd051acffec409a2984/GIT-Checkout.es.gif)
 
 Después de añadir este nuevo producto a un perfil, asegúrese de que los usuarios deseados están asociados a este perfil de acceso.
diff --git a/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md b/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md
index b7d8e6896..5d3e405fc 100644
--- a/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md
+++ b/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md
@@ -21,7 +21,7 @@ Com esse objetivo, nós criamos a nova tela [Performance das páginas web](https
 
 O PageSpeed Insights e o Lighthouse são ferramentas desenvolvidas pelo Google para gerar relatórios sobre a experiência do usuário de uma página tanto em dispositivos móveis quanto em computadores, fornecendo sugestões sobre como essa página pode ser aprimorada. Eles usam as [principais métricas da web do Google](https://web.dev/vitals/#core-web-vitals) para avaliar a experiência do usuário online. 
 
-![Web page performance Dash PT](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
+![Web page performance Dash PT](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/admin-disponivel-em-japones.md b/docs/announcements/pt/admin-disponivel-em-japones.md
index dfe4e3ac0..6eb3ec3b7 100644
--- a/docs/announcements/pt/admin-disponivel-em-japones.md
+++ b/docs/announcements/pt/admin-disponivel-em-japones.md
@@ -25,4 +25,4 @@ A tradução do Admin para o japonês foi incentivada pela [abertura do nosso no
 
 ## O que precisa ser feito?
 Para visualizar o Admin em japonês, basta selecionar o código __JP__ no menu de seleção de idiomas no canto superior direito da tela. 
-![ Selecionar o código JP](https://images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/900a9b6d702feaa51ea2d582354165a4/japones.png)
+![ Selecionar o código JP](//images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/900a9b6d702feaa51ea2d582354165a4/japones.png)
diff --git a/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
index b6ba0b616..1d7eecd2a 100644
--- a/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -28,7 +28,7 @@ Agora, os usuários irão visualizar apenas os itens do menu lateral que eles t
 
 A imagem abaixo ilustra uma das possibilidades de visualização da barra lateral de acordo com a nova organização para melhorar a segurança e a experiência do usuário da sua loja.
 
-![PT Sidebar permissions announcement screenshot](https://images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/0404c44da45173707c4fb3af5eb2de74/PT_Sidebar_permissions_announcement_screenshot.png)
+![PT Sidebar permissions announcement screenshot](//images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/0404c44da45173707c4fb3af5eb2de74/PT_Sidebar_permissions_announcement_screenshot.png)
 
 ## Por que fizemos essa mudança?
 O objetivo dessa mudança é limitar a visualização de módulos importantes dentro de uma conta, protegendo a integridade da sua loja. Dessa forma, o risco de possíveis interrupções na operação da loja é minimizado e você garante que cada usuário irá visualizar apenas o que é permitido ao seu perfil de acesso.
diff --git a/docs/announcements/pt/amazon-integration-amazon-offer-matching.md b/docs/announcements/pt/amazon-integration-amazon-offer-matching.md
new file mode 100644
index 000000000..fb1a7c583
--- /dev/null
+++ b/docs/announcements/pt/amazon-integration-amazon-offer-matching.md
@@ -0,0 +1,35 @@
+---
+title: 'Integração Amazon: Match de anúncios Amazon'
+id: 6cWiUoUTzVtOAVpF4XhOzm
+status: PUBLISHED
+createdAt: 2023-07-04T20:11:24.168Z
+updatedAt: 2023-07-04T21:44:36.582Z
+publishedAt: 2023-07-04T21:44:36.582Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: integracao-amazon-match-de-anuncios-amazon
+locale: pt
+legacySlug: match-de-anuncios-amazon
+announcementImageID: ''
+announcementSynopsisPT: 'O Match de anúncios Amazon agora é manual, conheça a nova página.'
+---
+
+A [integração](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon) entre lojas VTEX e a Amazon permite que sellers enviem seu catálogo de produtos para o marketplace, ampliando os canais de venda e para oferecer maior qualidade aos anúncios disponibilizados na Amazon, desenvolvemos uma nova página para a realização do *matching* de produtos de sellers VTEX.
+
+## O que mudou?
+
+Anteriormente, quando o seller enviava um produto para a integração da Amazon, um processo de matching automático era realizado para relacionar o SKU do seller com o ASIN (*Amazon Standard Identification Number*, ou, Número de Identificação Padrão da Amazon) do produto na Amazon. No entanto, em alguns casos, o processo gerava erros de compatibilidade entre o produto enviado e o anúncio disponibilizado na Amazon. 
+
+Agora com o novo fluxo de *matching*, os sellers são responsáveis por aprovar as correspondências entre seus produtos e anúncios da Amazon. Apesar de o match ser manual, os sellers têm a possibilidade de aprovar vários SKUs de uma só vez.
+
+## Por que fizemos essa mudança?
+
+O processo passa a ser realizado 100% manualmente, com o objetivo de reduzir os erros de compatibilidade para que sellers ofereçam anúncios confiáveis e de qualidade no marketplace, trazendo ao seller o controle sobre a correspondência entre o produto enviado e o anúncio disponibilizado.
+
+## O que precisa ser feito?
+
+A página __Match de anúncios Amazon__ poderá ser encontrada em Marketplace > __Match de anúncios Amazon__, ou na barra de busca, e estará disponível para todas as contas VTEX a partir do dia 03 de julho de 2023, sem a necessidade de qualquer ação para ativá-la.
+
+Para mais informações sobre o funcionamento, consulte nossa [documentação Match de anúncios Amazon](https://help.vtex.com/pt/tutorial/match-de-anuncios-amazon--7fRfoP69kYgg8znImMhyQ0).
+
diff --git a/docs/announcements/pt/amazon-new-category-mapping-model.md b/docs/announcements/pt/amazon-new-category-mapping-model.md
new file mode 100644
index 000000000..9c4b98d59
--- /dev/null
+++ b/docs/announcements/pt/amazon-new-category-mapping-model.md
@@ -0,0 +1,36 @@
+---
+title: 'Amazon: novo modelo de mapeamento de categorias'
+id: 584nPLYkI8tnOGz1s4X5LE
+status: PUBLISHED
+createdAt: 2023-11-27T23:08:37.697Z
+updatedAt: 2023-12-18T15:49:17.763Z
+publishedAt: 2023-12-18T15:49:17.763Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: amazon-novo-modelo-de-mapeamento-de-categorias
+locale: pt
+legacySlug: amazon-novo-modelo-de-mapeamento-de-categorias
+announcementImageID: ''
+announcementSynopsisPT: 'Conheça o novo modelo de mapeamento de categorias e atributos na integração VTEX e Amazon.'
+---
+
+Um passo importante na [integração](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5sYA9MlRo92jJIxKF1MTXb) entre as lojas VTEX e a Amazon é o processo de  mapeamento de categorias e atributos, que consiste em fazer uma correspondência entre os produtos do seu catálogo e os anúncios disponíveis na Amazon.  
+
+Visando facilitar o processo de mapeamento e torná-lo intuitivo, desenvolvemos o **[Mapeamento de categorias e atributos via Admin VTEX](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD?&utm_source=autocomplete#mapeamento-via-admin-vtex-beta),** que está disponível para lojas VTEX do Brasil, México e Estados Unidos. Para acessar o novo modelo de mapeamento, vá em **Marketplace > Marketplaces e Integrações > Amazon > Realizar Mapeamento,** o passo a passo está disponível no tutorial de [Envio e mapeamento de categorias dos produtos para a Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).  
+
+## O que mudou?  
+
+Anteriormente, o processo de mapeamento podia ser realizado somente [via planilha](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD?&utm_source=autocomplete#mapeamento-via-planilha). Agora, com o novo modelo de mapeamento, é possível escolher qual forma de mapeamento melhor atende as necessidades da sua operação.  
+
+Veja alguns benefícios do mapeamento de categorias e atributos via Admin VTEX:  
+
+- Acompanhar o status de mapeamento de cada categoria.  
+- Buscar a categoria na Amazon para fazer a correspondência com o seu catálogo.  
+- Preenchimento automático de atributos já presentes no seu catálogo.  
+- Personalização de tabela de frete por SKU.  
+
+## O que precisa ser feito?  
+
+A funcionalidade estará disponível para todas as [contas VTEX que atuam como seller](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) a partir de **18 de dezembro de 2023.** Para utilizá-la, você precisa ter a sua conta VTEX [integrada](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5sYA9MlRo92jJIxKF1MTXb) à Amazon e fazer o envio dos produtos utilizando o tutorial de [Envio e mapeamento de categorias dos produtos para a Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).  
+
diff --git a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md
index 9905578ee..5a8e7d015 100644
--- a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md
+++ b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md
@@ -21,7 +21,7 @@ Uma situação comum em restaurantes que aceitam pedidos online, por exemplo, é
 
 Para simplificar o uso dessa funcionalidade, desenvolvemos o aplicativo **Assembly Options**, que apresenta uma interface para configuração e gerenciamento das opções de customização. O aplicativo está disponível somente para lojas que utilizam [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
+![assembly-options-app](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md
index 32b4af495..4244c98d1 100644
--- a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md
+++ b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md
@@ -21,7 +21,7 @@ Uma situação comum em restaurantes que aceitam pedidos online, por exemplo, é
 
 Para simplificar o uso dessa funcionalidade, desenvolvemos o aplicativo **Assembly Options**, que apresenta uma interface para configuração e gerenciamento das opções de customização. O aplicativo está disponível somente para lojas que utilizam [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
+![assembly-options-app](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/autocomplete-metrics-now-available-in-search-reports.md b/docs/announcements/pt/autocomplete-metrics-now-available-in-search-reports.md
index 218292d1d..fd1f19732 100644
--- a/docs/announcements/pt/autocomplete-metrics-now-available-in-search-reports.md
+++ b/docs/announcements/pt/autocomplete-metrics-now-available-in-search-reports.md
@@ -23,7 +23,7 @@ Antes só era possível visualizar e exportar relatórios sobre os resultados de
 <table width = "100%">
   <tr>
     <td>
-      <img src = "https:https://images.ctfassets.net/alneenqid6w5/2QF4oxUnywaQz8RZjm85SJ/a3fa0d57d6e5fa330b042b106c1f7a2a/relatorios-filtros-PT.png" style = "display:block; margin-left: auto; margin-right: auto;" alt = "Opções de filtros do relatório" title = "Opções de filtros do relatório">
+      <img src = "https://images.ctfassets.net/alneenqid6w5/2QF4oxUnywaQz8RZjm85SJ/a3fa0d57d6e5fa330b042b106c1f7a2a/relatorios-filtros-PT.png" style = "display:block; margin-left: auto; margin-right: auto;" alt = "Opções de filtros do relatório" title = "Opções de filtros do relatório">
     </td>
   </tr>
   <tr>
diff --git a/docs/announcements/pt/automatic-archiving-inactive-promotions.md b/docs/announcements/pt/automatic-archiving-inactive-promotions.md
new file mode 100644
index 000000000..a61d106f7
--- /dev/null
+++ b/docs/announcements/pt/automatic-archiving-inactive-promotions.md
@@ -0,0 +1,41 @@
+---
+title: 'Arquivamento automático de promoções inativas'
+id: 4LDQbli98aRSNJDus7mgqi
+status: PUBLISHED
+createdAt: 2024-05-13T11:40:27.337Z
+updatedAt: 2024-05-20T12:14:24.232Z
+publishedAt: 2024-05-20T12:14:24.232Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: arquivamento-automatico-de-promocoes-inativas
+locale: pt
+legacySlug: arquivamento-automatico-de-promocoes-inativas
+announcementImageID: ''
+announcementSynopsisPT: 'A nova funcionalidade de arquivamento automático para promoções inativas auxilia o gerenciamento de promoções na loja.'
+---
+
+Visando melhorar a experiência de gerenciamento de promoções, a VTEX está implementando o arquivamento automático de promoções inativas. Esta funcionalidade permite que você tenha uma melhor organização e controle das promoções disponíveis em sua loja.
+
+## O que mudou?
+
+Aplicamos as seguintes melhorias na experiência de gerenciamento de promoções.
+
+**Autoarquivamento de promoções:** as regras para o arquivamento automático de promoções são as seguintes:
+
+1. **Promoções com data de término e não ativadas:** serão arquivadas automaticamente 7 dias após a última modificação, contados a partir da data de fim da promoção.
+
+2. **Promoções sem data de término e não ativadas:** serão arquivadas automaticamente 30 dias após a última modificação.
+
+3. **Promoções com data de término e ativas:** serão arquivadas automaticamente 7 dias após a data de fim da promoção.
+
+**Otimização de recursos:** melhoria no carregamento e performance da lista de promoções.
+
+<div class = "alert alert-info">
+Para visualizar as promoções que foram arquivadas automaticamente, você pode acessar no Admin VTEX <b>Promoções > Promoções</b>, ou digite <b>Promoções</b> na barra de busca no topo da página, e no canto superior direito clique nos <i class="fas fa-ellipsis-v" aria-hidden="true"></i> e em Promoções aplicadas.
+</div>
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. A funcionalidade de arquivamento automático de promoções inativas já está disponível em todas as lojas VTEX.
+
diff --git a/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md b/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
index 3b7a3baec..6533636c8 100644
--- a/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
+++ b/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Participe de um dia de treinamento intensivo em VTEX com os maiores especialistas no assunto.'
 ---
 
-![cover fb 01](https://images.ctfassets.net/alneenqid6w5/fj8PzFYRP2yaeAaIiKCW2/e06c967d7129640c493c545ecfc48db8/cover_fb_01.png)
+![cover fb 01](//images.ctfassets.net/alneenqid6w5/fj8PzFYRP2yaeAaIiKCW2/e06c967d7129640c493c545ecfc48db8/cover_fb_01.png)
 
 <div class="alert alert-info">
 Um dia inteiro de treinamento em VTEX com os maiores especialistas no assunto.
diff --git a/docs/announcements/pt/black-week-vtex-dashboards-analysis-strategies.md b/docs/announcements/pt/black-week-vtex-dashboards-analysis-strategies.md
new file mode 100644
index 000000000..443b2baab
--- /dev/null
+++ b/docs/announcements/pt/black-week-vtex-dashboards-analysis-strategies.md
@@ -0,0 +1,22 @@
+---
+title: 'Black Week: Estratégias de análise dos Dashboards VTEX'
+id: 1MrvvWj1ziiqLWhM021PX7
+status: PUBLISHED
+createdAt: 2023-11-20T20:29:11.550Z
+updatedAt: 2023-11-20T20:39:16.159Z
+publishedAt: 2023-11-20T20:39:16.159Z
+contentType: updates
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: black-week-estrategias-de-analise-dos-dashboards-vtex
+locale: pt
+legacySlug: black-week-estrategias-de-analise-dos-dashboards-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Aprenda as melhores estratégias para analisar suas métricas de vendas na Black Week com o guia de Dashboards da VTEX'
+---
+
+Chegamos oficialmente à **Black Week,** que acontece de **20/11/2023** a **27/11/2023.** As lojas já estão com suas campanhas online e com suas operações prontas para atender aos compradores.  
+
+Visando maximizar as oportunidades de melhoria das ações de **Black Friday** durante esse período, elaboramos um guia especial destinado a esclarecer as dúvidas mais frequentes relacionadas ao uso dos nossos dashboards no Admin VTEX durante o evento mais importante do ano.  
+
+Veja o [Guia de uso dos Dashboards da VTEX: FAQ](https://help.vtex.com/pt/tutorial/guia-de-los-dashboards-vtex-para-la-black-week-faq--6O3CiGiZctVIgIrpIcko9h) nele você encontrará respostas às perguntas mais frequentes sobre como utilizar os Dashboards durante a Black Week.
diff --git a/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 92df48457..8241515f6 100644
--- a/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -25,7 +25,7 @@ A solução combina duas funcionalidades e aplicativos móveis:
 * [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): controle da entrega last mile.
 * **Aplicativos móveis:** aplicativos móveis para separadores e entregadores.
 
-![pick_pack_gif_PT](https://images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/f35996b674b6ded591dcb0d8b46ee0f1/pick_pack_gif_PT.gif)
+![pick_pack_gif_PT](//images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/f35996b674b6ded591dcb0d8b46ee0f1/pick_pack_gif_PT.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/callback-url-signature-authentication-token.md b/docs/announcements/pt/callback-url-signature-authentication-token.md
new file mode 100644
index 000000000..f31fd71da
--- /dev/null
+++ b/docs/announcements/pt/callback-url-signature-authentication-token.md
@@ -0,0 +1,32 @@
+---
+title: 'Callback URL signature: bloqueio em autorizações de pagamento assíncrono sem o uso de token de autenticação'
+id: 3at5YtI2L6QqBym6Af56tV
+status: PUBLISHED
+createdAt: 2024-05-03T18:12:04.996Z
+updatedAt: 2024-05-03T18:33:19.277Z
+publishedAt: 2024-05-03T18:33:19.277Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: callback-url-signature-token-de-autenticacao
+locale: pt
+legacySlug: callback-url-signature-token-de-autenticacao
+announcementImageID: ''
+announcementSynopsisPT: 'Token de autenticação para autorizações de pagamento assíncrono'
+---
+
+Visando aprimorar as operações de pagamento realizadas na plataforma, a VTEX está implementando a utilização do token de autenticação `X-VTEX-signature`.  Este token deve ser utilizado por provedores e parceiros de pagamento no momento de retornar o status de uma transação de pagamento assíncrona via [callback URL](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#callback-url).  
+
+A partir do dia 27 de maio de 2024, o gateway da VTEX encaminhará em cada transação de pagamento a informação da callback URL e o respectivo token de autenticação.
+
+Exemplo de callback URL contendo o token de autenticação:
+
+`https://gatewayqa.vtexpayments.com.br/api/pvt/payment-provider/transactions/8FB0F111111122222333344449984ACB/payments/A2A9A25B11111111222222333327883C/callback?accountName=teampaymentsintegrations&X-VTEX-signature=R123456789aBcDeFGHij1234567890tk`
+
+## O que precisa ser feito?
+
+A partir do dia 26 de junho de 2024, todos os provedores e parceiros de pagamento deverão informar o status de uma transação de pagamento assíncrona somente via callback URL e token de autenticação.
+
+Após esta data, informações encaminhadas apenas para a callback URL (sem o token de autenticação), serão bloqueadas e as respectivas transações de pagamento, canceladas.
+
+Para mais informações sobre a callback URL, acesse [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#callback-url) e [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
diff --git a/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md b/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md
index b09f59846..905550602 100644
--- a/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md
+++ b/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md
@@ -23,7 +23,7 @@ Aprimoramos a configuração de audiência de campanha para permitir que você s
 
 No Admin VTEX, em **Produtos > Promoções e Taxas > Audiências de campanhas > Nova audiência de campanha**, nas configurações referentes ao **Público-alvo**, acrescentamos a opção “e”, onde antes havia apenas a opção “ou”.  Isso significa que agora você pode aplicar uma lógica de adição de critérios (“e”), além da lógica de alternativa (“ou”) que já existia antes. Veja a imagem a seguir:
 
-![publico-alvo-e-ou-pt](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
+![publico-alvo-e-ou-pt](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
 
 Com a nova opção, é possível criar promoções de campanha a partir da combinação de critérios de forma mais flexível.
 
diff --git a/docs/announcements/pt/catalogs-new-visual-and-navigation.md b/docs/announcements/pt/catalogs-new-visual-and-navigation.md
index c87e2f320..8af62cc16 100644
--- a/docs/announcements/pt/catalogs-new-visual-and-navigation.md
+++ b/docs/announcements/pt/catalogs-new-visual-and-navigation.md
@@ -23,16 +23,16 @@ A principal diferença para a versão antiga está na navegação. Rearranjamos
 ## O que mudou
 
 A maior parte dos itens do Catálogo podem ser encontrados em _Catálogo_, que fica na seção _PRODUTOS_ do menu lateral.
-![Catálogo1](https://images.ctfassets.net/alneenqid6w5/6zg0sXt3qwc8KGUuwEwsSI/0f3f2fafcc1a4addaabe3e5deb100296/Cat__logo1.png)
+![Catálogo1](//images.ctfassets.net/alneenqid6w5/6zg0sXt3qwc8KGUuwEwsSI/0f3f2fafcc1a4addaabe3e5deb100296/Cat__logo1.png)
 
 
 O subitem _Vale-compra_ (que antes se chamava _Vales_ e ficava em _Controle de Campanhas_) está no item _Pagamentos_, dentro da seção _TRANSAÇÕES_ do menu lateral.
-![Catálogo2](https://images.ctfassets.net/alneenqid6w5/2giEGOSr8EGWWqS4goeOU8/c655d3c669fcfb54ea7a44b97d490d4e/Cat__logo2.png)
+![Catálogo2](//images.ctfassets.net/alneenqid6w5/2giEGOSr8EGWWqS4goeOU8/c655d3c669fcfb54ea7a44b97d490d4e/Cat__logo2.png)
 
 
 O item _Configurações_ virou um subitem de _CMS_, que fica na seção _CONFIGURAÇÕES DE LOJA_ do menu lateral.
-![Catálogo3](https://images.ctfassets.net/alneenqid6w5/6ybb0PjANUOC6kgugu4WCW/d599404279f39970b047aa9aac532d3d/Cat__logo3.png)
+![Catálogo3](//images.ctfassets.net/alneenqid6w5/6ybb0PjANUOC6kgugu4WCW/d599404279f39970b047aa9aac532d3d/Cat__logo3.png)
 
 
 A aba _Marketplace_ ganhou uma seção própria de mesmo nome no menu lateral.
-![Catálogo4](https://images.ctfassets.net/alneenqid6w5/5oQsBoQHOoMqYK688g8c6a/d708824d3496d3d66b06dcd27dd5aa1b/Cat__logo4.png)
+![Catálogo4](//images.ctfassets.net/alneenqid6w5/5oQsBoQHOoMqYK688g8c6a/d708824d3496d3d66b06dcd27dd5aa1b/Cat__logo4.png)
diff --git a/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md b/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
index c518d28e6..6b06048d8 100644
--- a/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
+++ b/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
@@ -27,7 +27,7 @@ Fique tranquilo, nós não nos enganamos. Após uma análise criteriosa, nossa e
 
 Mas isso não é tudo. Também modificamos o processo para mudar o usuário Titular de uma conta, transformando-o em um fluxo de transferência controlado por convite que é totalmente auditável.  
 
-![Gerenciamento titular gif](https://images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/a3f49ef6a2cc6208afa52859da36b7fe/Announcement_PT.gif)
+![Gerenciamento titular gif](//images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/a3f49ef6a2cc6208afa52859da36b7fe/Announcement_PT.gif)
 
 Confira o artigo [Transferência de propriedade da loja](https://help.vtex.com/pt/tutorial/transferencia-de-propriedade-da-loja) para mais detalhes sobre este novo processo.
 
diff --git a/docs/announcements/pt/changes-in-vtex-support-service-policy.md b/docs/announcements/pt/changes-in-vtex-support-service-policy.md
new file mode 100644
index 000000000..090d71065
--- /dev/null
+++ b/docs/announcements/pt/changes-in-vtex-support-service-policy.md
@@ -0,0 +1,39 @@
+---
+title: 'Mudanças na política de atendimento do Suporte VTEX'
+id: 7f5YRWJQ7q0VUGCTDKVDon
+status: PUBLISHED
+createdAt: 2024-02-16T18:37:29.587Z
+updatedAt: 2024-02-22T21:12:09.365Z
+publishedAt: 2024-02-22T21:12:09.365Z
+contentType: updates
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: mudancas-na-politica-de-atendimento-do-suporte-vtex
+locale: pt
+legacySlug: mudancas-na-politica-de-atendimento-do-suporte-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Agora, o canal principal para abrir um chamado é a VTEX Community.'
+---
+
+A dinâmica do Suporte VTEX passou por transformações com a transição do canal de atendimento. Agora, a [VTEX Community](https://community.vtex.com/) passa a ser o canal principal de suporte na maioria dos casos.
+
+<div class="alert alert-info">Esta mudança é válida apenas para contas no Brasil.</div>
+
+# O que mudou?
+Anteriormente, para obter auxílio do time do suporte VTEX, era necessário abrir um chamado no Suporte. A partir de hoje, a [VTEX Community](https://community.vtex.com/) se torna o canal primário de Suporte.
+
+# Por que fizemos essa mudança?
+Essas mudanças visam proporcionar uma experiência de suporte mais escalável e eficiente, garantindo que as necessidades dos usuários sejam atendidas de forma rápida e satisfatória.
+
+A VTEX Community conta com moderadores dedicados para acompanhar as publicações e garantir que todas as perguntas sejam respondidas.
+
+# O que precisa ser feito?
+
+Ao precisar de suporte, acesse [VTEX Community](https://community.vtex.com/), realize o login no portal e  obtenha a resposta da nossa equipe de especialistas do ecossistema VTEX.
+
+A maioria dos casos será tratada através da VTEX Community, porém, ainda existirão situações em que o suporte será realizado via ticket. Se o seu caso demandar um tratamento de [urgência](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9?&utm_source=autocomplete), é indicada a abertura de um ticket no [Suporte](https://help.vtex.com/pt/support).
+
+Sugerimos também que, antes de publicar uma pergunta, os usuários realizem uma pesquisa na comunidade para verificar se a resposta já está disponível. Caso não encontrem a solução desejada, podem criar um novo tópico para receber ajuda da comunidade.
+
+<div class="alert alert-warning"> VTEX Community é um fórum público e, portanto, não devem ser compartilhadas informações sensíveis, como chaves de aplicação, senhas ou quaisquer outros dados confidenciais. </div>
+
diff --git a/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md b/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md
new file mode 100644
index 000000000..0080f819c
--- /dev/null
+++ b/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md
@@ -0,0 +1,39 @@
+---
+title: 'A API do Checkout agora suporta reCAPTCHA v3'
+id: 1buRTScMhlis0LESr7g8Rt
+status: PUBLISHED
+createdAt: 2023-06-28T19:52:18.268Z
+updatedAt: 2023-08-25T23:36:39.909Z
+publishedAt: 2023-08-25T23:36:39.909Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: a-api-do-checkout-agora-suporta-recaptcha-v3
+locale: pt
+legacySlug: a-api-do-checkout-agora-suporta-recaptcha-v3
+announcementImageID: ''
+announcementSynopsisPT: 'Esta solução utilizada para prevenção de usuários falsos pode ser usada para apps mobile nativos e outras integrações'
+---
+
+O [reCAPTCHA](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP) é uma solução utilizada para validação de usuário real disponibilizada pela VTEX para todas as lojas. Ele prevê cenários em que programas maliciosos são utilizados para fraudes, evitando acesso de falsos usuários.
+
+Além da funcionalidade nas frentes de loja nativas da plataforma VTEX, lojas implementando frentes de loja proprietárias, podem [integrar o reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) pela API do Checkout, afim de aumentar a segurança da sua loja.
+
+## O que mudou?
+
+Agora, a API do Checkout suporta também reCATPCHA com validação baseada em pontuação (equivalente à v3), adequada para apps mobile nativos.
+
+<div class="alert alert-info">
+A VTEX está integrada com o reCAPTCHA enterprise, que oferece duas abordagens de validação: checkbox (equivalente ao reCAPTCHA v2) e baseada em pontuação (equivalente ao reCAPTCHA v3). Confira este artigo sobre o <a href="https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#versoes-do-recaptcha">reCAPTCHA no Checkout da VTEX</a> para aprender qual versão você deve usar dependendo das características da sua loja. Você também pode aprender mais sobre cada método: <a href="https://developers.google.com/recaptcha/docs/display">reCAPTCHA v2</a> ou <a href="https://developers.google.com/recaptcha/docs/v3">reCAPTCHA v3</a> com a documentação fornecida pelo Google.
+</div>
+
+Entretanto, a opção de integração com reCAPTCHA checkbox (equivalente à v2) continua disponível, sendo a opção recomendada caso deseje implementar uma [integração de reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) que não seja em um app mobile nativo.
+
+Atualmente, a validação baseada em pontuação não está disponível para frentes de loja nativas da VTEX – a previsão é que esteja nos próximos meses. Essa solução está disponível apenas para integrações baseadas na Checkout API.
+
+## O que precisa ser feito?
+
+Se você usa uma solução de frente de loja nativa da VTEX ou se usa integração com o reCAPTCHA checkbox pela API do Checkout, nenhuma ação é necessária. O reCAPTCHA continuará funcionando de acordo com a sua configuração.
+
+Caso deseje implementar o reCAPTCHA em uma frente de loja de app mobile nativo, você deve usar o reCAPTCHA baseado em pontuação. Entre em contato com seu time de desenvolvimento e confira o [guia de integração com reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha).
+
diff --git a/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
index 9fa08e9c1..4a38867fb 100644
--- a/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
@@ -45,7 +45,7 @@ Para verificar se os provedores de antifraude configurados em sua loja permitem
 2. Em **Pagamentos**, clique em **Configurações > Afiliações de Gateway**. 
 3. Ao selecionar o provedor de antifraude escolhido, verifique se a opção **Campo de documento do titular do cartão **está disponível na tela de configuração.
 
-![campo de documento do titular do cartão](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/5bbfb8cbfce605b09d61e10a8ff06e3b/campo_de_documento_do_titular_do_cart__o.png)
+![campo de documento do titular do cartão](//images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/5bbfb8cbfce605b09d61e10a8ff06e3b/campo_de_documento_do_titular_do_cart__o.png)
 
 <div class = "alert alert-warning">
   Caso a opção <b>Campo de documento do titular do cartão</b> não esteja disponível na tela de configuração do seu provedor de antifraude, o campo <b>Identificação do titular do cartão</b> continuará sendo exibido na tela do Checkout da loja e deverá ser obrigatoriamente preenchido pelo cliente.
diff --git a/docs/announcements/pt/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md b/docs/announcements/pt/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
new file mode 100644
index 000000000..4ba76450d
--- /dev/null
+++ b/docs/announcements/pt/convert-abandoned-checkouts-into-sales-with-whatsapp-ai-campaigns.md
@@ -0,0 +1,29 @@
+---
+title: 'Transforme checkouts abandonados em vendas com WhatsApp AI Campaigns'
+id: 4pzBvWuadV753AdCqPhoVS
+status: PUBLISHED
+createdAt: 2024-06-26T11:08:16.663Z
+updatedAt: 2024-06-26T11:27:29.365Z
+publishedAt: 2024-06-26T11:27:29.365Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: transforme-checkouts-abandonados-em-vendas-com-whatsapp-ai-campaigns
+locale: pt
+legacySlug: transforme-checkouts-abandonados-em-vendas-com-whatsapp-ai-campaigns
+announcementImageID: ''
+announcementSynopsisPT: 'WhatsApp AI Campaigns impulsiona vendas ao recuperar checkouts abandonados.'
+---
+
+Desenvolvemos uma nova funcionalidade, o WhatsApp AI Campaigns. Essa nova funcionalidade permite que lojistas enviem automaticamente lembretes personalizados por WhatsApp aos usuários que não finalizaram suas compras.
+
+Esses lembretes são projetados para motivar os usuários a retornarem à página de pagamento e completarem suas transações, melhorando assim a experiência de compra e impulsionando as vendas.
+
+A nova funcionalidade do WhatsApp AI Campaigns oferece melhorias, tais como:
+- **Personalização de mensagens:** direciona mensagens personalizadas para os usuários que não finalizaram suas compras.
+- **Acompanhamento em tempo real:** permite acompanhar o desempenho das campanhas em tempo real por meio do painel da VTEX.
+- **Configuração rápida:** ativa a funcionalidade sem a necessidade de codificação.
+- **Redirecionamento após expiração:** permite redirecionar o usuário para o checkout mesmo após a expiração da sessão.
+
+## O que precisa ser feito?
+A funcionalidade já está disponível para todas as lojas que utilizam [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) que não tenham customizações no checkout.  Para implementar esta funcionalidade na sua loja, acesse [Recupere checkouts abandonados com WhatsApp AI Campaigns](https://help.vtex.com/pt/tutorial/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns--20i0zLQHt72LKzVEmk1CRZ?&utm_source=autocomplete)
diff --git a/docs/announcements/pt/coupon-experience-improvements.md b/docs/announcements/pt/coupon-experience-improvements.md
index be067095c..668a6cb9d 100644
--- a/docs/announcements/pt/coupon-experience-improvements.md
+++ b/docs/announcements/pt/coupon-experience-improvements.md
@@ -27,7 +27,7 @@ A nova experiência de Cupons oferece os seguintes recursos:
 
 A nova [Lista de cupons](https://help.vtex.com/pt/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ) exibe todos os cupons cadastrados na sua loja, possibilitando gerenciar seus dados e analisar em quais pedidos foram utilizados.
 
-![listacupons pt](https://images.ctfassets.net/alneenqid6w5/2uuixGwgV7WgvGhpwZnQiM/a883b91403037b62476bb53c0b905ad3/listacupons_pt.gif)
+![listacupons pt](//images.ctfassets.net/alneenqid6w5/2uuixGwgV7WgvGhpwZnQiM/a883b91403037b62476bb53c0b905ad3/listacupons_pt.gif)
 
 ### Acesso mais fácil aos códigos de cupom
 
@@ -44,7 +44,7 @@ Os novos filtros possibilitam a visualização apenas dos cupons que atendem a c
 - Última edição
 - Tipo de cupom 
 
-![filtroscupons pt](https://images.ctfassets.net/alneenqid6w5/4ycZkMAbrCVdN5sryskEcE/0d0fe4fe0dc88f7fdadc0bc21999a946/filtroscupons_pt.gif)
+![filtroscupons pt](//images.ctfassets.net/alneenqid6w5/4ycZkMAbrCVdN5sryskEcE/0d0fe4fe0dc88f7fdadc0bc21999a946/filtroscupons_pt.gif)
 
 ### Grupos de cupons para gerenciamento ágil
 
diff --git a/docs/announcements/pt/custom-selection-of-sellers-for-b2b-purchases.md b/docs/announcements/pt/custom-selection-of-sellers-for-b2b-purchases.md
new file mode 100644
index 000000000..47c2948e0
--- /dev/null
+++ b/docs/announcements/pt/custom-selection-of-sellers-for-b2b-purchases.md
@@ -0,0 +1,32 @@
+---
+title: 'Seleção personalizada de sellers para compras B2B'
+id: 2AezDuup65tH3MyBBWDasG
+status: PUBLISHED
+createdAt: 2023-12-21T13:29:04.048Z
+updatedAt: 2023-12-21T18:13:37.674Z
+publishedAt: 2023-12-21T18:13:37.674Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: selecao-personalizada-de-sellers-para-compras-b2b
+locale: pt
+legacySlug: selecao-personalizada-de-sellers-para-compras-b2b
+announcementImageID: ''
+announcementSynopsisPT: 'Atribuir sellers às organizações compradoras permite que estas tenham seus pedidos atendidos por sellers selecionados.'
+---
+
+A VTEX disponibiliza uma nova funcionalidade que permite às organizações compradoras (B2B) escolher e selecionar um grupo exclusivo de sellers destinados a atender os seus pedidos de compra.
+
+## O que mudou?
+
+A partir de agora, cada organização compradora poderá determinar quais sellers estão habilitados a exibir produtos durante um processo de compra realizado por seus compradores.
+
+## Por que fizemos essa mudança?
+
+Para permitir um processo de compra mais ágil, centralizado e que simplifique o acesso direto dos compradores aos produtos de sellers selecionados.
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. A funcionalidade já está disponível para todas as lojas.
+Para mais informações sobre como criar uma nova atribuição de seller, acesse [Configurando atribuição de sellers a organizações compradoras (B2B)](https://help.vtex.com/pt/tutorial/configurando-atribuicao-de-sellers-a-organizacoes-compradoras-b2b-xky--3VJtKNbLpVAl71uVdaOqpE).
+
diff --git a/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md b/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md
index e544c38b7..47d4cfa98 100644
--- a/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md
+++ b/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md
@@ -35,6 +35,6 @@ A configuração é similar à das demais condições especiais de pagamento.
 
 A principal diferença é que, depois de selecionar o país e o banco emissor, o lojista pode escolher entre as opções de Card Level disponibilizadas pela instituição financeira escolhida.
 
-![comousarcardlevel](https://images.ctfassets.net/alneenqid6w5/29GOP06jAv6PhE408fiaD8/947436f46b295ce09ab7928a9bb7ce95/comousarcardlevel.gif)
+![comousarcardlevel](//images.ctfassets.net/alneenqid6w5/29GOP06jAv6PhE408fiaD8/947436f46b295ce09ab7928a9bb7ce95/comousarcardlevel.gif)
 
 Para saber em detalhes como configurar essa feature, veja nosso [artigo sobre Configuração de Condições Especiais de Pagamento](https://help.vtex.com/tutorial/special-conditions--tutorials_456).
diff --git a/docs/announcements/pt/discontinuation-of-legacy-payment-connectors.md b/docs/announcements/pt/discontinuation-of-legacy-payment-connectors.md
new file mode 100644
index 000000000..961839207
--- /dev/null
+++ b/docs/announcements/pt/discontinuation-of-legacy-payment-connectors.md
@@ -0,0 +1,89 @@
+---
+title: 'Descontinuidade de conectores legados de pagamento'
+id: 11SHyRwcAr4fs46K7PccOr
+status: PUBLISHED
+createdAt: 2024-03-15T10:19:40.450Z
+updatedAt: 2024-04-08T19:55:00.286Z
+publishedAt: 2024-04-08T19:55:00.286Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: descontinuidade-de-conectores-legados-de-pagamento
+locale: pt
+legacySlug: descontinuidade-de-conectores-legados-de-pagamento
+announcementImageID: ''
+announcementSynopsisPT: 'Conectores de pagamento legados serão removidos da plataforma VTEX'
+---
+
+Em prosseguimento ao processo de [descontinuidade dos conectores legados de pagamento](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14), a tabela abaixo apresenta os conectores legados a serem removidos da plataforma VTEX e os novos conectores (integrados via Payment Provider Protocol) já disponíveis para substituí-los:
+
+| **Conector legado** | **Nova versão (Conector PPP)** |
+| :---: | :---: |
+| Adyen | AdyenV3 |
+| Alignet | AlignetV2 |
+| Amex | - |
+| AuthorizeNet/AuthorizeDotNet | - |
+| BanamexInvoice | - |
+| BankInvoiceItau/BankIssuedInvoiceItau | MaxiPagoV4 |
+| BankInvoiceSantander/BankIssuedInvoiceSantander | Egetnet |
+| Bcash | - |
+| BoldCron | - |
+| Bradesco/RegisteredBankInvoiceBradesco | - |
+| Braspag/BraspagV2 | CieloEcommerce |
+| Cielo/CieloV3 | CieloEcommerce |
+| Conductor | - |
+| Credomatic | - |
+| CyberSource | Cybersource IO |
+| Decidir/DecidirV1 | Payway |
+| ERede/E-Rede V2/ERedeRest | Itaú Rede |
+| Evolucard | - |
+| Firstdata | - |
+| IPay88 | - |
+| ItauShopline | MaxiPagoV4 |
+| Koin | Koin-Payments |
+| MaxiPago | MaxiPagoV4 |
+| MeoWallet | - |
+| MercadoPagoV1 | MercadoPagoV2 |
+| MobilPay | - |
+| Moip | YamiSplitMoipV1 |
+| MOLPay | - |
+| Mundipagg/MundipaggFraudPrevention | PagarmeV3 |
+| Nexxpago | - |
+| NPS | - |
+| PagamentoDigital | - |
+| PagBrasil | PagBrasilV2 |
+| PagHiper | PagHiperV2 ou PagHiperV3 |
+| PagoEfectivo | PagoEfectivoV2  |
+| PagosNet | - |
+| PagosWeb | - |
+| PagSeguro/PagSeguroDirect | - |
+| PayClub | - |
+| Payme | PayMee |
+| Paymentez | PaymentezV2 |
+| PaymentHub | - |
+| PaymentsOS | PayUv2 |
+| PayPal/PayPalPlus | PayPalV2 |
+| PayU/PayUGlobal | PayUv2 |
+| Payzen | - |
+| Place2Pay/PlaceToPay | PlaceToPayLatam |
+| Rede Pay/RedePay | Itaú Rede |
+| Redecard | Itaú Rede |
+| Redsys/RedsysV2 | - |
+| SafetyPay | SafetyPayV2 |
+| SalesMachine | - |
+| Scopus | - |
+| Sitef/SitefDirectSale/SitefPreauth | ESITEF |
+| Stelo | SteloM1V2 |
+| TNSPay | EvoPayments |
+| TodoPago | - |
+| WebPay/WebPay2P | - |
+| WorldPay | Worldpay-Payments-Via-WPG |
+
+## O que precisa ser feito?
+
+Caso a sua loja utilize algum dos conectores legados listados acima, realize as ações específicas de acordo com a situação de cada conector:
+
+- __Conector legado não possui ainda conector PPP correspondente disponível__: abra um ticket no [Suporte VTEX](https://help.vtex.com/pt/support) para que o time de CX responsável pela sua conta possa auxiliá-lo na verificação de quais conectores PPP disponíveis são mais adequados ao seu tipo de operação e podem ser configurados em sua loja.
+
+- __Conector PPP disponível para substituir conector legado__: entre em contato com o seu provedor de pagamento para obter mais informações sobre o processo de migração e configuração do novo conector em sua loja.
+
diff --git a/docs/announcements/pt/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md b/docs/announcements/pt/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
new file mode 100644
index 000000000..4b162e369
--- /dev/null
+++ b/docs/announcements/pt/discover-the-new-feature-that-allows-bulk-data-import-for-organizations-and.md
@@ -0,0 +1,30 @@
+---
+title: 'Conheça a nova funcionalidade que permite a importação em massa de dados sobre organizações e centros de custos '
+id: 6XwSfF6YYjIiIDoxR3NoDN
+status: PUBLISHED
+createdAt: 2024-04-29T17:36:01.588Z
+updatedAt: 2024-05-21T14:07:17.423Z
+publishedAt: 2024-05-21T14:07:17.423Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: conheca-a-nova-funcionalidade-que-permite-a-importacao-em-massa-de-dados
+locale: pt
+legacySlug: conheca-a-nova-funcionalidade-que-permite-a-importacao-em-massa-de-dados
+announcementImageID: ''
+announcementSynopsisPT: 'Facilite a gestão de organizações: Bulk Import simplifica atualizações e manutenção de dados'
+---
+
+A VTEX disponibiliza uma nova funcionalidade de importação em massa, permitindo a simplificação do processo de atualização e manutenção de informações para organizações compradoras, seus usuários (membros) e centros de custo.
+
+## O que mudou?
+
+A partir de agora, as lojas que utilizam [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite) podem realizar a importação de organizações compradoras, centros de custo e membros por meio de um arquivo em formato **XLSX** ou da [API de Bulk import](https://developers.vtex.com/docs/api-reference/buyer-organizations?endpoint=overview). 
+
+## Por que fizemos essa mudança?
+
+Para melhorar a eficiência na gestão de informações em organizações compradoras.
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. A funcionalidade estará disponível para todas as lojas que tenham o aplicativo B2B Suite instalado. 
diff --git a/docs/announcements/pt/displaying-pickup-points-on-google-maps.md b/docs/announcements/pt/displaying-pickup-points-on-google-maps.md
index 25452b35f..5b5a12650 100644
--- a/docs/announcements/pt/displaying-pickup-points-on-google-maps.md
+++ b/docs/announcements/pt/displaying-pickup-points-on-google-maps.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Aplicativo que lista Pontos de Retirada e os exibe como
 
 Uma das funcionalidades mais comuns de websites e lojas online é a disponibilização de mapas que sinalizam a localização de lojas físicas. Com o novo app [Store Locator](https://apps.vtex.com/vtex-store-locator/p#overview), as lojas desenvolvidas com VTEX IO podem utilizar o Google Maps para listar os Pontos de Retirada registrados na loja e exibi-los como marcadores em um mapa.
 
-![Maps](https://images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
+![Maps](//images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
 
 ## O que mudou? 
 As lojas desenvolvidas com VTEX IO agora podem instalar o aplicativo Store Locator e apresentar os pontos de retirada no Google Maps através de marcadores.
diff --git a/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 01cbafc1f..158752503 100644
--- a/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -25,7 +25,7 @@ O aplicativo está disponível na [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Possibilita moderar as avaliações: aprovar as avaliações de produtos antes de serem disponibilizadas na página do produto;
 - Permite que você configure a sua loja para habilitar avaliações anônimas.
 
-![Reviews and Ratings - Printscreen](https://images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
+![Reviews and Ratings - Printscreen](//images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
 
 ## Quais os benefícios?
 - Permite que o seu consumidor faça compras com mais confiança e assertividade baseando-se em avaliações de outros usuários;
diff --git a/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 41397822a..8737ffbce 100644
--- a/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -39,7 +39,7 @@ Para fazer isso é necessário adicionar um produto chamado `Order Authorization
  6. Escolha o tipo de permissão desejada: `Save Configuration`, para permitir que o usuário edite e salve modificações, ou `View Configuration`, para permitir a visualização da página de Autorização de Pedidos.
  7. Clique em **Salvar**
 
-![GIT-OrderAutho](https://images.ctfassets.net/alneenqid6w5/4jnwsJuKbMW7YMt6g3Jhfp/19219d84c921d287462551b1b5ddbd00/GIT-OrderAutho.gif)
+![GIT-OrderAutho](//images.ctfassets.net/alneenqid6w5/4jnwsJuKbMW7YMt6g3Jhfp/19219d84c921d287462551b1b5ddbd00/GIT-OrderAutho.gif)
 
 Após adicionar este novo produto a um perfil, certifique-se de que os usuários desejados estão associados a este perfil de acesso.
   
diff --git a/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
index 021400b83..d224d66d6 100644
--- a/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -3,8 +3,8 @@ title: 'Hub de Extensões: Estenda a sua operação pelo Admin VTEX'
 id: 4FYJCHTttMa0znV1mdHW9w
 status: PUBLISHED
 createdAt: 2023-05-31T22:15:06.695Z
-updatedAt: 2023-06-04T22:02:53.542Z
-publishedAt: 2023-06-04T22:02:53.542Z
+updatedAt: 2023-08-02T14:37:08.083Z
+publishedAt: 2023-08-02T14:37:08.083Z
 contentType: updates
 productTeam: Apps
 author: 4ubliktPJIsvyl1hq91RdK
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'A nova seção do Admin VTEX para encontrar parceiros,
 
 Hub de Extensões é a nova seção do Admin VTEX que reúne desenvolvedores parceiros e merchants que querem estender as funcionalidades da sua operação. Pelo Hub de Extensões, parceiros podem publicar suas extensões e merchants podem visualizar, comprar, instalar e gerenciar extensões. O Hub de Extensões estará disponível globalmente em todas as lojas VTEX durante o terceiro trimestre (Q3) de 2023. Caso você queira habilitar o Hub de Extensões na sua loja imediatamente, você pode fazer o pedido [abrindo um ticket para o nosso suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-![Extensions Hub GIF](https://images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e5d1491570f8676841390e1899c54250/Extensions_Hub.gif)
+![Extensions Hub GIF](//images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e5d1491570f8676841390e1899c54250/Extensions_Hub.gif)
 
 ## O que mudou?
 
@@ -49,7 +49,7 @@ O [site Portal de Parceiros](https://partnerportal.vtex.com/) continuará existi
 
 O Hub de Extensões estará disponível para todas as lojas a partir do terceiro trimestre (Q3) de 2023. Caso você queira habilitar o Hub de Extensões na sua loja imediatamente, você pode fazer o pedido [abrindo um ticket para o nosso suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). Em seguida, para começar a utilizar o Hub de Extensões, basta acessá-lo no Admin da sua loja. No painel lateral esquerdo do Admin VTEX, clique no ícone **Extensões** e o Hub de Extensões estará visível na parte superior do menu.
 
-![Extensions Hub painel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
+![Extensions Hub painel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
 
 ## Por que fizemos essa mudança?
 
@@ -60,3 +60,5 @@ Além disso, renovamos a experiência de compra de apps na **App Store**. Com po
 Por fim, nosso objetivo é estreitar o relacionamento entre os lojistas e parceiros VTEX. Assim, lojistas que desejam implementar soluções únicas para suas lojas, agora podem encontrar e contatar diretamente parceiros e desenvolvedores pelo **Parceiros** no Admin VTEX.
 
 Para mais informações, veja a nossa [documentação do Extensions Hub](https://help.vtex.com/pt/tracks/hub-de-extensoes--AW7klkYMh557y5IUOgzco).
+
+_\*Edição em 02/08/2023: A página **Parceiros** será disponibilizada futuramente. Ainda não há uma previsão de quando esta página estará disponível._
diff --git a/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
new file mode 100644
index 000000000..bee0fba4a
--- /dev/null
+++ b/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -0,0 +1,70 @@
+---
+title: 'FastCheckout: aumente sua conversão com o novo checkout'
+id: 1sOAAmRehyJ1YkzbG4BkE2
+status: PUBLISHED
+createdAt: 2024-04-03T18:54:06.111Z
+updatedAt: 2024-04-23T10:00:03.018Z
+publishedAt: 2024-04-23T10:00:03.018Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: fastcheckout-aumente-sua-conversao-com-o-novo-checkout
+locale: pt
+legacySlug: fastcheckout-aumente-sua-conversao-com-o-novo-checkout
+announcementImageID: ''
+announcementSynopsisPT: 'Apresentamos o FastCheckout: inovação em checkout para experiências personalizadas e de alta conversão.'
+---
+
+
+Com o compromisso contínuo de inovar e a entregar excelência aos nossos clientes, a VTEX apresenta o **FastCheckout**, a mais recente evolução em nosso checkout. A nova solução permite criar experiências de checkout personalizadas com alta conversão, sempre atualizadas com novas funcionalidades.
+
+![fastcheckout](//images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/4e751e1a0b31e6e68d6f9053f0451ecd/image.png)
+
+## O que mudou?
+
+Anteriormente, o Checkout VTEX apresentava uma experiência ultrapassada para os clientes, não seguindo os padrões de inovações do mercado. Além disso, toda a customização era dependente de códigos CSS e Javascript.
+
+Agora, para oferecer uma experiência mais dinâmica aos clientes, realizamos melhorias significativas nos seguintes aspectos do Checkout VTEX:
+
+* Experiência otimizada para a conversão, baseada em pesquisas das melhores experiências de usuário segundo a [Baymard Institute](https://baymard.com/).
+* Suporte para opções omnichannel sofisticadas.
+* Alta performance, mesmo em carrinhos com muitos itens.
+* Aparência e funcionalidades customizáveis.
+* Otimização para dispositivos móveis e desktop.
+* Atualizações constantes para oferecer a melhor experiência, por meio de estudo de novas funcionalidades.
+* Possibilidade de fechar a compra sem necessidade de cadastro.
+* Possibilidade de aceitar múltiplos cupons por padrão.
+
+### Customização descomplicada
+
+O FastCheckout permite uma experiência de checkout customizável, adaptando-se aos contextos e necessidades dos lojistas. No FastCheckout, é possível personalizar os elementos a seguir via Admin, sem necessidade de código:
+
+* Incluir o logotipo da loja no checkout.
+* Customizar cores dos botões e menus do checkout.
+* Definir limites de valores da compra e do carrinho. 
+* Ocultar ou adicionar os elementos de **Código promocional**, de **Previsão de envio** e de **Exibição de preço de SKU**.
+* Configurar o Adobe Analytics e o Google Maps API. 
+* Adicionar descrição em texto que deseje exibir para o cliente.
+* Desabilitar e habilitar a informação de impostos dentro do **Resumo do Pedido**.
+
+Proporcionamos a liberdade de incluir elementos completamente customizados, sem a necessidade de conhecimento em JavaScript ou CSS.
+
+<div class="alert alert-warning">
+  <p>A primeira versão lançada do FastCheckout permite customizações limitadas. Em breve, será possível personalizar completamente o conteúdo utilizando os pontos de extensão da FastStore Platform.</p>
+</div>
+
+### Novo fluxo de compra
+
+O novo fluxo de compra no FastCheckout é projetado para ser dinâmico e intuitivo, para oferecer aos seus clientes uma experiência de compra mais fluida e simplificada. Com etapas claramente definidas e uma navegação intuitiva, tornamos o processo de checkout mais eficiente.
+
+![GIFCheckout](//images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/27979c72da22a010d210379d502dab88/GIFCheckout.gif)
+
+## Por que fizemos essa mudança?
+
+O novo checkout foi concebido com o objetivo de aumentar a conversão das lojas e facilitar a customização da experiência de checkout. O FastCheckout oferece uma navegação fluida e intuitiva, garantindo uma jornada de compra mais simples.
+
+Facilitamos significativamente a customização, adaptável a experiência do usuário de acordo com as necessidades específicas feitas pelo Admin.
+
+## O que precisa ser feito?
+
+Para participar do programa early access do FastCheckout, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests). A equipe da VTEX entrará em contato e avaliará se as funcionalidades disponíveis neste primeiro lançamento atendem às suas necessidades. Caso positivo, você será chamado para aderir ao nosso programa Beta e todos os usuários na conta da sua loja serão atualizados para a nova experiência. Nenhuma configuração adicional é necessária.
diff --git a/docs/announcements/pt/faster-customer-support-with-new-solutions-for-vtex-clients.md b/docs/announcements/pt/faster-customer-support-with-new-solutions-for-vtex-clients.md
new file mode 100644
index 000000000..95ff19ae3
--- /dev/null
+++ b/docs/announcements/pt/faster-customer-support-with-new-solutions-for-vtex-clients.md
@@ -0,0 +1,35 @@
+---
+title: 'Atendimento mais rápido com nova solução para suporte de clientes VTEX'
+id: 2ofvmblxC8uksroSiWmna0
+status: PUBLISHED
+createdAt: 2023-06-29T13:08:03.574Z
+updatedAt: 2023-06-29T13:23:21.815Z
+publishedAt: 2023-06-29T13:23:21.815Z
+contentType: updates
+productTeam: Billing
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: atendimento-mais-rapido-com-nova-solucao-para-suporte-de-clientes-vtex
+locale: pt
+legacySlug: atendimento-mais-rapido-com-nova-solucao-para-suporte-de-clientes-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Nosso suporte a clientes VTEX agora inclui um bot que utiliza inteligência artificial para tirar suas dúvidas.'
+---
+
+Nosso suporte a clientes VTEX agora inclui um bot que utiliza inteligência artificial para tirar suas dúvidas sobre nossa plataforma. O bot foi alimentado com o conteúdo das nossas bases de conhecimento para que você desfrute de um atendimento **ágil e sem espera**, com capacidade conversacional feita **sob medida para sua demanda**.
+
+### O que mudou?
+
+Ao abrir um [chamado de atendimento](https://help.vtex.com/pt/support) do tipo Técnico, você terá acesso a uma nova tela de conversação em tempo real com o bot VTEX, onde poderá tirar as suas dúvidas sobre a plataforma. O bot oferece **suporte para múltiplos idiomas**, e foi treinado com a base de conhecimento disponível pela VTEX, como nosso [Help Center](https://help.vtex.com/).
+
+Mesmo com essa novidade, ainda é possível **continuar o atendimento com nosso time de especialistas do Suporte**, seguindo os SLAs definidos na [política de atendimento de sua região](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe#planos-de-suporte).
+
+### Disponibilidade limitada em versão beta
+
+Gostaríamos de destacar que essa é uma versão beta do serviço, portanto, inicialmente, o bot estará disponível apenas em regiões selecionadas.
+
+ Pontos importantes a serem considerados:
+
+* As conversas podem ser compartilhadas com softwares de terceiros para aprimorar nosso serviço.  
+* Não compartilhe informações que podem identificar sua conta, empresa, clientes, funcionários, ou informações confidenciais da sua empresa por meio do chat.  
+* Estamos empenhados em aprimorar continuamente as respostas do bot. No entanto, ele poderá ocasionalmente fornecer informações inconsistentes. Em caso de dúvidas, você pode continuar contando com nosso Help Center, Developer Portal e chamados para nosso suporte.  
+
diff --git a/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md b/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md
index 700fed0bc..9208a85e0 100644
--- a/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md
+++ b/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md
@@ -21,7 +21,7 @@ Agora é possível criar Tabelas de Preços de forma mais intuitiva, prática e
 
 Antes, para criar uma tabela de preços, era necessário ir até o filtro do módulo de Preços e digitar o nome da tabela a ser criada. Agora, adicionamos um novo botão __Tabelas de Preços__ que permite criar e selecionar as tabelas de preço que você deseja visualizar.
 
-![Annoucement Price table PT](https://images.ctfassets.net/alneenqid6w5/22qst5crxgQq0Mdih3XgnK/93c3034eabe8c139143bcb2fc92ec35f/Annoucement_Price_table_PT.png)
+![Annoucement Price table PT](//images.ctfassets.net/alneenqid6w5/22qst5crxgQq0Mdih3XgnK/93c3034eabe8c139143bcb2fc92ec35f/Annoucement_Price_table_PT.png)
 
 ## Vantagens
 
diff --git a/docs/announcements/pt/get-more-agility-managing-your-orders-events-with-feed-v3.md b/docs/announcements/pt/get-more-agility-managing-your-orders-events-with-feed-v3.md
index 60c080ec1..606cf39d5 100644
--- a/docs/announcements/pt/get-more-agility-managing-your-orders-events-with-feed-v3.md
+++ b/docs/announcements/pt/get-more-agility-managing-your-orders-events-with-feed-v3.md
@@ -3,8 +3,8 @@ title: 'Ganhe mais agilidade na gestão dos eventos dos seus pedidos com o Feed
 id: 49FssyfGcJfvGfrb3JQjVr
 status: PUBLISHED
 createdAt: 2019-02-18T19:55:07.210Z
-updatedAt: 2019-12-31T15:13:12.603Z
-publishedAt: 2019-12-31T15:13:12.603Z
+updatedAt: 2024-01-03T18:00:45.130Z
+publishedAt: 2024-01-03T18:00:45.130Z
 contentType: updates
 productTeam: Post-purchase
 author: 6AcGyun1hSWewU8YcaQiO
@@ -31,7 +31,5 @@ Por serem soluções independentes e não se tratar de uma migração, é possí
 
 ## O que você precisa fazer
 
-Encontre o passo a passo da configuração do feed v3 no nosso tutorial [Feed v3 de Gerenciamento de pedidos](https://help.vtex.com/pt/tutorial/feed-v3-de-gerenciamento-de-pedidos) 
-
-
+Encontre o passo a passo da configuração em [Feed v3](https://developers.vtex.com/docs/guides/orders-feed).
 
diff --git a/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md b/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md
new file mode 100644
index 000000000..3350ffdbc
--- /dev/null
+++ b/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md
@@ -0,0 +1,36 @@
+---
+title: 'Conheça a nova página de Status da VTEX'
+id: 7n6kl6CftvChNUU1BJFmqw
+status: PUBLISHED
+createdAt: 2023-12-22T13:42:40.056Z
+updatedAt: 2023-12-22T13:57:46.734Z
+publishedAt: 2023-12-22T13:57:46.734Z
+contentType: updates
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: conheca-a-nova-pagina-de-status-da-vtex
+locale: pt
+legacySlug: conheca-a-nova-pagina-de-status-da-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Reformulamos a página de Status VTEX, com foco na transparência e na comunicação eficaz sobre incidentes e manutenções.'
+---
+
+Lidar com incidentes é uma parte crucial da experiência dos lojistas, por isso é fundamental tornar esse processo o mais transparente e informativo possível. A partir dessa necessidade, reformulamos a página de status da plataforma ([status.vtex.com](https://status.vtex.com/)), para aprimorar como comunicamos eventos de manutenção e incidentes.
+
+## O que mudou?
+
+Anteriormente, enfrentamos desafios ao categorizar incidentes em apenas quatro componentes: Checkout, WebStore, Administrative Environment e Internal Modules. Em algumas situações, a categorização ampla não refletia com precisão o impacto real do incidente. Por exemplo, um problema com um conector de pagamento poderia ser marcado como um problema no componente Checkout, levando a uma comunicação inadequada sobre a extensão do problema.
+
+Agora, apresentamos 18 componentes mais específicos agrupados em quatro categorias – Storefront, Checkout, Admin e Developer Tools – com foco não apenas em nossa arquitetura interna, mas principalmente em onde os sintomas podem ser observados por lojistas. A imagem a seguir apresenta todos os componentes exibidos na nova página:
+
+![status-page-vtex](//images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/08f9ab11d14629a3f6e534268be71b06/status-page-vtex.png)
+
+Confira o artigo [Página de status da VTEX](https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ) para mais informações sobre cada componente.
+
+## Por que fizemos essa mudança?
+
+Atualizamos a página de status da plataforma para proporcionar uma experiência de comunicação mais clara e contextualizada durante e após incidentes e manutenções agendadas, permitindo que lojistas compreendam melhor o impacto real em suas operações.
+
+## O que precisa ser feito?
+
+Acesse a nova página em [status.vtex.com](https://status.vtex.com/) e leia o guia [Página de status da VTEX](https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ) para mais detalhes.
diff --git a/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md b/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
index 09c211d4c..0d7524d20 100644
--- a/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
+++ b/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
@@ -21,4 +21,4 @@ Como fazemos todos os anos, criamos uma cartilha com recomendações e dicas exc
 
 Disponível para clientes e parceiros VTEX, o guia pode ser acessado pela homepage do seu Admin ou diretamente pela URL `https://{AccountName}.myvtex.com/admin/blackfriday`. Basta substituir `{AccountName}` pelo Account Name da sua loja.
 
-![Announcement Cartilha BF](https://images.ctfassets.net/alneenqid6w5/etqQlJKljisiesmY8kUYS/c45814633c167f8af372df7ec75749ab/Announcement_Cartilha_BF.png)
+![Announcement Cartilha BF](//images.ctfassets.net/alneenqid6w5/etqQlJKljisiesmY8kUYS/c45814633c167f8af372df7ec75749ab/Announcement_Cartilha_BF.png)
diff --git a/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md b/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
index d718adc30..4c9e321aa 100644
--- a/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
+++ b/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
@@ -27,4 +27,4 @@ https://{AccountName}.myvtex.com/admin/shopping-season
 
 Basta substituir `{AccountName}` pelo Account Name da sua loja, como na imagem abaixo.
 
-![Shopping Season Guidelines - 2022 - PT](https://images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/55de9dc55b06266326e99aa3d0b89836/Screen_Shot_2022-10-19_at_18.15.20.png)
+![Shopping Season Guidelines - 2022 - PT](//images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/55de9dc55b06266326e99aa3d0b89836/Screen_Shot_2022-10-19_at_18.15.20.png)
diff --git a/docs/announcements/pt/google-catalog-migration.md b/docs/announcements/pt/google-catalog-migration.md
new file mode 100644
index 000000000..4f98b50db
--- /dev/null
+++ b/docs/announcements/pt/google-catalog-migration.md
@@ -0,0 +1,40 @@
+---
+title: 'Migração do catálogo Google'
+id: 5dwWSG8NVTSXpylGZC67FU
+status: PUBLISHED
+createdAt: 2024-05-22T19:50:50.806Z
+updatedAt: 2024-05-22T20:16:57.592Z
+publishedAt: 2024-05-22T20:16:57.592Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: migracao-do-catalogo-google
+locale: pt
+legacySlug: migracao-do-catalogo-google
+announcementImageID: ''
+announcementSynopsisPT: 'Realize a integração com o Google Shopping sem perder a relevância dos seus anúncios.'
+---
+
+Desenvolvemos a funcionalidade de **Migração do catálogo Google** para mapear e realizar match entre os produtos do seller no catálogo VTEX e os anúncios do seller no Google shopping.
+
+A funcionalidade é destinada a sellers que antes integravam os produtos de sua loja com o Google por meio de uma plataforma externa a VTEX e agora passam a integrar através do [conector Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw) na VTEX.
+
+## Por que desenvolvemos a funcionalidade?
+
+O objetivo dessa funcionalidade é possibilitar ao seller a migração da relevância de seus anúncios no Google Shopping. Ao migrar sua integração para o conector da VTEX, você não perde o histórico de relevância dos seus anúncios. 
+
+<div class="alert alert-info">
+A migração de catálogo apenas mapeia e realiza match entre produtos do catálogo VTEX com anúncios já existentes no Merchant Center do Google Shopping.
+</div>
+
+## O que precisa ser feito?
+
+Para realizar a migração, você deve entrar em solicitar para o suporte da VTEX. Mas antes é necessário seguir os dois requisitos abaixo:
+
+1. Criar uma nova política comercial que não deve ter produtos vinculados.
+2. Configurar a integração com o Google Shopping, utilizando a nova política comercial criada no passo anterior.
+
+Então, entre em contato com o suporte da VTEX solicitando a migração. Para o retorno dessa solicitação, considere o prazo de até quatro dias úteis.
+
+Com a migração finalizada, você deve incluir os SKUs que deseja anunciar no Google shopping à política comercial que está cadastrada na integração.
+
diff --git a/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md b/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md
new file mode 100644
index 000000000..3518de750
--- /dev/null
+++ b/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md
@@ -0,0 +1,37 @@
+---
+title: 'Google Pay: novo meio de pagamento na plataforma VTEX'
+id: 4HWD5UwH4FsjUyOqDcOFiX
+status: PUBLISHED
+createdAt: 2023-06-20T18:18:22.678Z
+updatedAt: 2023-06-28T13:00:03.123Z
+publishedAt: 2023-06-28T13:00:03.123Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: google-pay-novo-meio-de-pagamento-na-plataforma-vtex
+locale: pt
+legacySlug: google-pay-novo-meio-de-pagamento-na-plataforma-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Integração Google Pay na VTEX: checkout rápido e seguro com apenas um toque.'
+---
+
+O pagamento pelo Google Pay está disponível para as lojas VTEX. Essa nova integração nativa permite que os lojistas ofereçam uma experiência de checkout mais rápida e segura para seus clientes.
+
+O Google Pay usa Tokens, em vez dos números reais dos cartões, vinculados ao dispositivo do usuário. Com isso as taxas de aprovação são maiores e o número de fraudes é significativamente reduzido.
+
+Além disso, ele possui milhões de cartões já registrados. Ainda armazena os dados dos cartões adicionados à Carteira do Google ou diretamente no serviço. Disponibilizando todos esses cartões em qualquer site ou aplicativo que tenha o botão "Pagar com Google Pay" com apenas um clique.
+
+## O que mudou?
+
+O Google Pay é uma plataforma de carteira digital e um sistema de pagamento online desenvolvido pelo Google para viabilizar compras no aplicativo e compras com toque para pagar em dispositivos móveis, permitindo que os usuários façam pagamentos com telefones, tablets ou relógios Android.
+
+A partir de agora, você pode adicionar o Google Pay como meio de pagamento na sua loja, proporcionando aos seus clientes um processo de checkout mais ágil e conveniente.
+
+![google-pay-checkout-pt](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/1e5184005b2c0a2098589a1abffb9e72/image.png)
+
+## O que precisa ser feito?
+
+Primeiro, leia [Google Pay and Wallet APIs Acceptable Use Policy](https://payments.developers.google.com/terms/aup) para conferir os tipos de produtos e serviços que não podem ser usados com Google Pay.
+
+Para habilitar o Google Pay como meio de pagamento da sua loja, siga nossa track [Google Pay](https://help.vtex.com/pt/tracks/carteira-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/61JMBvM5Vanqj6RaJsP8CT).
+
diff --git a/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md b/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
new file mode 100644
index 000000000..34cc1fb19
--- /dev/null
+++ b/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
@@ -0,0 +1,39 @@
+---
+title: 'Google Shopping: nova opção de envio de preço'
+id: 4qtyADXxyaUCbOD498K14l
+status: PUBLISHED
+createdAt: 2023-12-13T23:27:59.782Z
+updatedAt: 2023-12-14T13:10:09.812Z
+publishedAt: 2023-12-14T13:10:09.812Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: google-shopping-nova-opcao-de-envio-de-preco
+locale: pt
+legacySlug: google-shopping-nova-opcao-de-envio-de-preco
+announcementImageID: ''
+announcementSynopsisPT: 'Atualize sua integração: novas formas de aplicar desconto no Google Shopping.'
+---
+
+Atualizamos as modalidades de envio de preços de produtos na [integração com o Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) para que os lojistas possam oferecer anúncios com mais qualidade e descontos com o [meio de pagamento](https://help.vtex.com/pt/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) que melhor atender à demanda do público da loja.
+
+## O que mudou?
+
+Anteriormente, no cadastro da [integração com o Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG), era encontrada a opção **Considerar desconto para pagamento com boleto no preço enviado.** Agora, ela foi substituída por **Aplicar desconto no preço enviado.** Com a atualização, as lojas VTEX podem utilizar uma das duas opções abaixo para configurar o preço enviado ao Google Shopping:
+- **Enviar preço-base (para preços com desconto):** apresentará somente os produtos cadastrados com [preço lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista).  
+- **Aplicar desconto no preço enviado:** apresentará no Google Shopping os produtos da loja VTEX com o desconto e o meio de pagamento cadastrados.  
+
+<div class = "alert alert-warning">
+  A configuração <b>Aplicar desconto no preço enviado</b> está disponível somente para lojas VTEX Brasil.
+</div>
+
+![envio-de-precos-google-pt](//images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/309246aab10954d984d851b58442a4ef/envio-de-precos-google-pt.png)
+
+## O que precisa ser feito?
+
+A atualização estará disponível para todas as [contas VTEX que atuam como seller](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) a partir de 14 de dezembro de 2023. 
+Para contas que ainda não utilizam a integração com o Google Shopping e desejam ativar as configurações **Enviar preço base (para preços com desconto)** e **Aplicar desconto no preço enviado**, siga [esta trilha](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) para começar a utilizar as novas configurações. Para contas já integradas com o Google Shopping e com a configuração **Considerar desconto para pagamento com boleto no preço enviado** ativa, após a atualização a configuração correspondente **Aplicar desconto no preço enviado** já estará ativa conforme imagem abaixo:  
+
+![fluxo-update-news-google](//images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/9f4ee800552c105e69dae21676a58b31/fluxo-update-news-google.png)  
+
+Confira a documentação e saiba como [Configurar desconto vinculado ao meio de pagamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/3AqbcsWrge8zLt0BC5CtGd#desconto-vinculado-ao-metodo-de-pagamento) e como [Configurar o desconto no conector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
diff --git a/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md b/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md
index 0648cb342..39f8cce0a 100644
--- a/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md
+++ b/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Conheça o Singleton: tipo de content type no Headless
 
 O Singleton é um novo tipo de content type que permite comerciantes criar e gerenciar uma única página de um content type no Headless CMS. Content types do tipoSingleton não podem ser duplicados. Isto garanteque haja apenas uma página daquele content type e que o conteúdo seja consistente em toda a loja.
 
-![singleton-br](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
+![singleton-br](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 O content type Singleton está disponível apenas para lojas usando o <a href="https://help.vtex.com/pt/tutorial/managing-pages-beta--3DO6rBhZ1p3zndnFu5BgRt">VTEX Headless CMS</a> (Atualmente está em fase Beta).
diff --git a/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md b/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md
new file mode 100644
index 000000000..f43d6322a
--- /dev/null
+++ b/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md
@@ -0,0 +1,35 @@
+---
+title: 'Headless CMS: mais informações sobre o status de publicação de páginas'
+id: 9G9ILO21L5sGtEVIHFhLr
+status: PUBLISHED
+createdAt: 2023-10-18T12:31:52.699Z
+updatedAt: 2023-10-18T20:56:21.584Z
+publishedAt: 2023-10-18T20:56:21.584Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-mais-informacoes-sobre-o-status-de-publicacao-de-paginas
+locale: pt
+legacySlug: headless-cms-mais-informacoes-sobre-o-status-de-publicacao-de-paginas
+announcementImageID: ''
+announcementSynopsisPT: 'Status de publicação no Headless CMS será descontinuado em favor do Build Status para rastreamento detalhado do deploy.'
+---
+
+A partir de 01 de novembro de 2023, o status **Publicando** em Páginas no Headless CMS será descontinuado. Agora, você poderá acompanhar o status do deploy das páginas por meio da ferramenta **Build Status**, como [anunciado anteriormente](https://help.vtex.com/pt/announcements/headless-cms-mantenha-se-informado-sobre-o-progresso-das-suas-publicacoes--3ajb4FgE6nmqjblpSEg3SP). Essa ferramenta oferece uma visão mais detalhada do processo de deploy das suas páginas.
+
+Quando uma nova página é criada, ela recebe o status de **Rascunho**, indicando que ainda não foi feito o deploy. Após o deploy da página, o status é atualizado para **Publicado**, o que significa que o processo de compilação (build) poderá ser iniciado. Após a conclusão da compilação, a página ficará disponível para os usuários finais.
+
+![Build Status - PT](//images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/3b495e096d368969817a01eaea027f08/publishing-status-pt.gif)
+
+## O que mudou?
+
+O status **Publicando** era usado anteriormente para descrever o processo de deploy de uma página CMS no FastStore. No entanto, ele não dava muitos detalhes do processo.
+
+Agora, ao integrar a ferramenta Build Status a outros sistemas, como [Lançamentos](https://help.vtex.com/pt/tutorial/planner-pagina-calendario-beta--46wSZ7Z5xoXQPP0xHfIx9C), WebOps e [FastStore](https://www.faststore.dev/), o Headless CMS fornece informações mais completas sobre o status desses sistemas.
+
+## Por que fizemos essa mudança?
+A ferramenta Build Status foi implementada para melhorar a clareza e garantir a transparência do processo de deploy.
+
+## O que precisa ser feito?
+Essa funcionalidade será implementada no Headless CMS em 01 de novembro de 2023 e nenhuma ação é necessária.
+
diff --git a/docs/announcements/pt/headless-cms-events-available-in-audit.md b/docs/announcements/pt/headless-cms-events-available-in-audit.md
new file mode 100644
index 000000000..cb0ce0a16
--- /dev/null
+++ b/docs/announcements/pt/headless-cms-events-available-in-audit.md
@@ -0,0 +1,47 @@
+---
+title: 'Eventos do Headless CMS disponíveis no Audit'
+id: 2WQz4dwteRahTD71hIHNNc
+status: PUBLISHED
+createdAt: 2023-12-08T14:36:53.841Z
+updatedAt: 2023-12-08T14:57:21.295Z
+publishedAt: 2023-12-08T14:57:21.295Z
+contentType: updates
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: eventos-do-headless-cms-disponiveis-no-audit
+locale: pt
+legacySlug: eventos-do-headless-cms-disponiveis-no-audit
+announcementImageID: ''
+announcementSynopsisPT: 'Adicionamos eventos do Headless CMS aos registros do Audit.'
+---
+
+O [Audit](https://help.vtex.com/pt/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA), módulo que registra eventos que acontecem na sua loja para auditoria futura, agora processa eventos do [Headless CMS](https://help.vtex.com/pt/tutorial/gerenciando-paginas--3DO6rBhZ1p3zndnFu5BgRt) – a solução da VTEX que permite gerenciar conteúdo na web com autonomia para criar, editar e publicar conteúdo por meio do VTEX Admin.
+
+## O que mudou?
+
+Adicionamos os eventos do Headless CMS listados a seguir aos registros do Audit:
+
+| Ação | Descrição | Detalhes do evento |
+|---|---|---|
+| TRY_PUBLISHING | Tentativa de publicar uma página. | ID do evento. |
+| TRY_PUBLISH_IN_RELEASE | Tentativa de publicar um lançamento. | ID do evento. |
+| TRY_UNPUBLISHING | Tentativa de despublicar uma página. | ID do evento. |
+| RESTORE_CONTENT | Restauração de conteúdo. | ID do evento. |
+| TRY_UPDATING_DRAFT | Tentativa de atualizar um rascunho. | ID do evento. |
+| TRY_UNPUBLISHING_AND_OVERWRITING | Tentativa de despublicar e sobrescrever uma página. | ID do evento. |
+| done.invoke.deleteContent | Exclusão de conteúdo. | ID do evento. |
+| done.invoke.deleteContentVariant | Exclusão de uma versão do conteúdo. | ID do evento. |
+
+Na coluna **Ação**, todos os eventos do Headless CMS também apresentam as seguintes informações:
+
+* **CONTENT_ID:** código identificador único do conteúdo.
+* **VARIANT_ID:** código identificador único da versão do conteúdo.
+* **WORKSPACE:** workspace em que a alteração foi realizada.
+
+<div class="alert alert-info">
+  <p>Confira a <a href="https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista completa de eventos disponíveis no Audit</a>.</p>
+</div>
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. A mudança no Audit já está ativa para todas as contas, registrando a [lista de eventos](#o-que-mudou) citada acima.
diff --git a/docs/announcements/pt/headless-cms-new-authorization-requirement.md b/docs/announcements/pt/headless-cms-new-authorization-requirement.md
new file mode 100644
index 000000000..433243eb7
--- /dev/null
+++ b/docs/announcements/pt/headless-cms-new-authorization-requirement.md
@@ -0,0 +1,58 @@
+---
+title: 'Headless CMS: nova solicitação de autorização'
+id: 7G056zzZmGFBztkRqhpUgj
+status: PUBLISHED
+createdAt: 2024-02-02T12:34:37.766Z
+updatedAt: 2024-02-02T14:14:58.237Z
+publishedAt: 2024-02-02T14:14:58.237Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-nova-solicitacao-de-autorizacao
+locale: pt
+legacySlug: headless-cms-nova-solicitacao-de-autorizacao
+announcementImageID: ''
+announcementSynopsisPT: 'Usuários agora precisam do recurso CMS GraphQL API para gerenciar conteúdo. Atualize os perfis de acesso de acordo.'
+---
+
+A partir de 15 de Fevereiro, todos os [usuários](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) e [chaves de aplicação](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) que precisarem acessar o Headless CMS deverão ter os [recursos](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar` e `Settings` do License Manager adicionados aos seus [perfis de acesso](https://help.vtex.com/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Para o gerenciamento de conteúdo no Headless CMS, também é necessário ter o [recurso](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `CMS GraphQL API`. Esse requisito se aplica à API do Headless CMS e ao Admin VTEX.
+
+## O que mudou?
+Antes, o gerenciamento de conteúdo da loja no Headless CMS podia ser feito por usuários e chaves de aplicação
+sem ter um recurso específico do License Manager associado ao seu perfil de acesso.
+
+Agora, qualquer solicitação via API do Headless CMS ou Admin VTEX autenticará o usuário e verificará se ele tem os recursos necessários associados ao seu perfil de acesso.
+Os recursos `See CMS menu on the top-bar` e `Settings` concedem acesso ao Headless CMS. Para o gerenciamento de conteúdo, os usuários também precisam do recurso `CMS GraphQL API`. Sem este recurso, não será possível gerenciar o conteúdo no Headless CMS.
+
+## Por que fizemos esta mudança?
+Essa alteração visa aumentar a segurança e simplificar o acesso do usuário ao Headless CMS, proporcionando aos usuários um ambiente mais controlado e seguro para gerenciar o conteúdo da loja.
+
+## O que precisa ser feito?
+Certifique-se de que os usuários do Headless CMS estejam associados aos recursos `CMS GraphQL API`, `See CMS menu on the top-bar` e `Settings` em seus perfis de acesso, seja [criando um novo perfil de acesso](#criar-um-novo-perfil-de-acesso) ou [editando um existente](#editar-um-perfil-de-acesso).
+
+<div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 35px">
+  <p>Para gerenciar usuários e perfis de acesso, é necessário ter o recurso <code>Save access profile</code> do produto <b>License Manager</b> associado ao perfil de acesso do usuário. Por exemplo, o <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> é um perfil de acesso predefinido que tem o recurso <code>Save access profile</code> associado a ele.</p>
+
+</div>
+
+### Criar um novo perfil de acesso
+
+Se você ainda não criou um perfil de acesso específico para os usuários do Headless CMS e deseja criar um, acesse o guia [Criando um perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role). Não deixe de associar o perfil de acesso aos recursos `CMS GraphQL API`, `See CMS menu on the top-bar` e `Settings` na seção **Produtos e recursos**.
+
+### Editar um perfil de acesso
+
+Para editar um perfil de acesso já existente para usuários do Headless CMS, siga os passos abaixo:
+
+1. Acesse o Admin VTEX.
+2. Clique no avatar do seu perfil na barra superior do VTEX Admin, representado pela inicial do seu email, e clique em **Configurações da conta > Perfis de acesso**.
+3. Clique no **nome do perfil** atribuído aos usuários do Headless CMS.
+
+<div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; margin-bottom: 10px; padding: 15px">
+  <p>A opção de criar perfis de acesso personalizados pode variar de acordo com a configuração da loja, e cada loja pode definir um perfil específico para os usuários do Headless CMS.</p>
+</div>
+
+4. Na página **Editar perfil de acesso**, vá até a seção **Produtos e recursos**.
+5. Procure pelo produto **CMS** e clique nele.
+6. Selecione os recursos `CMS GraphQL API`, `See CMS menu on the top-bar` e `Settings`.
+7. Clique em `Salvar`.
+
diff --git a/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md b/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md
new file mode 100644
index 000000000..43f5443e8
--- /dev/null
+++ b/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md
@@ -0,0 +1,39 @@
+---
+title: 'Headless CMS: simplifique a criação e o gerenciamento de conteúdo com Projetos'
+id: 6pl14hf2E6sNgR9ykCJkj8
+status: PUBLISHED
+createdAt: 2023-11-01T16:39:47.055Z
+updatedAt: 2023-11-16T14:17:47.228Z
+publishedAt: 2023-11-16T14:17:47.228Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-simplifique-a-criacao-e-o-gerenciamento-de-conteudo-com
+locale: pt
+legacySlug: headless-cms-simplifique-a-criacao-e-o-gerenciamento-de-conteudo-com
+announcementImageID: ''
+announcementSynopsisPT: 'Headless CMS - Gerencie seus projetos de forma centralizada e personalizada.'
+---
+
+**Projetos** é a nova funcionalidade do Headless CMS que simplifica o gerenciamento de diversas experiências digitais, como aplicativos móveis, sites e email marketing em uma única tela.
+
+![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c5a1f1ba3077c11504d9f78c1712c59e/projects-two-pt.png)
+
+Com ele, você pode personalizar as configurações, o conteúdo e a marca de cada projeto para públicos ou objetivos específicos.
+
+## O que mudou?
+Antes, para lidar com diferentes projetos com diferentes públicos-alvo ou soluções, era necessário acessar o VTEX Admin, ir para **Aplicativos** > **Hub de Extensões** > **Gerenciamento de Aplicativos** e, em seguida, procurar o aplicativo **CMS (alpha)**. No aplicativo **CMS (alpha)**, cada projeto precisava ser criado e configurado individualmente.
+
+Agora, a interface de **Projetos** permite que você gerencie todos os seus projetos a partir de uma experiência centralizada, além de permitir que você navegue entre os projetos facilmente, edite as configurações, o conteúdo e a identidade em um só lugar. Essa melhoria aumenta sua capacidade de se adaptar, atendendo diferentes públicos e objetivos.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
+
+## Por que fizemos essa mudança?
+Com a interface de **Projetos**, você poderá:
+
+- Simplificar o processo de gerenciamento de conteúdo em diferentes projetos.
+- Centralizar os projetos em um único local
+- Atender de forma eficaz públicos ou objetivos específicos por meio de diferentes projetos.
+
+## O que precisa ser feito?
+A funcionalidade já está disponível em todas as contas que tenham o Headless CMS instalado. Acesse o guia [Gerenciando projetos](https://help.vtex.com/pt/tutorial/gerenciando-projetos--42IpDFqTVTESH8DCypJMPM) para saber mais sobre como usá-lo.
diff --git a/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md b/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md
new file mode 100644
index 000000000..9d660dd04
--- /dev/null
+++ b/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md
@@ -0,0 +1,44 @@
+---
+title: 'Headless CMS: mantenha-se informado sobre o progresso das suas publicações'
+id: 3ajb4FgE6nmqjblpSEg3SP
+status: CHANGED
+createdAt: 2023-08-21T12:33:36.149Z
+updatedAt: 2023-10-04T13:35:38.902Z
+publishedAt: 2023-08-21T15:36:01.683Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-mantenha-se-informado-sobre-o-progresso-das-suas-publicacoes
+locale: pt
+legacySlug: headless-cms-mantenha-se-informado-sobre-o-progresso-das-suas-publicacoes
+announcementImageID: ''
+announcementSynopsisPT: ' Mantenha-se informado sobre as etapas de publicação do Headless CMS e identifique rapidamente erros de publicação.'
+---
+
+O Headless CMS agora conta com uma funcionalidade de notificação que mantém você informado durante cada etapa do processo de publicação. As novas notificações fornecem atualizações sobre cada estágio de uma publicação no VTEX Headless CMS, mantendo os usuários informados sobre os estágios de compilação (build) da publicação em Lançamentos, VTEX Headless CMS e FastStore. 
+
+![Headless CMS - Notificações](//images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/faec3fe558ef0b94048f83cefd6a5106/headless-cms-publish-pt.gif)
+
+Essa funcionalidade também permite identificar e relatar erros durante o deploy, indicando o estágio exato do erro. Além de oferecer a opção de refazer os deploys, se necessário.
+
+## O que mudou?
+Anteriormente, quando uma publicação não acontecia, era difícil determinar a origem do problema, o que dificultava o debugging e a notificação do problema, além de gerar atrasos no lançamento de campanhas.
+
+Com esta funcionalidade, agora você pode acompanhar o status de cada estágio do deploy:
+
+| Status                                	| Descrição 
+| ------------------------------------- | ---------------------------------------------------------------------------- |
+|  **Publicação iniciada**       	| CMS inicia a publicação do lançamento.             	|
+|  **Build**                             	| Processo de colocar em produção as alterações do lançamento.        	                        |
+|  **Atualizar o status dos documentos**  | Atualiza todos os documentos, incluindo as novas alterações. |
+|  **Concluir lançamento**              	| Atualiza o status do lançamento.                                         	        |
+
+Caso ocorra um erro durante a implementação, a notificação indicará o estágio em que se deu o erro. Você pode clicar em `Tentar novamente` para refazer o deploy.
+
+![Headless CMS - Novo deploy](//images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/b9ce5d741d88aa05661c2e592b9cf550/headless-cms-redeploy-pt.gif)
+
+## Por que fizemos essa mudança?
+A funcionalidade de notificação permite que você tenha maior autonomia para entender e resolver os problemas relacionados às publicações da loja, possibilitando identificá-los e relatá-los com precisão, além de repetir o processo de publicação.
+
+## O que precisa ser feito?
+Nenhuma ação é necessária, já que essa funcionalidade já foi implementada no Headless CMS.
diff --git a/docs/announcements/pt/headless-cms-updated-user-permissions.md b/docs/announcements/pt/headless-cms-updated-user-permissions.md
new file mode 100644
index 000000000..1c3a39e5f
--- /dev/null
+++ b/docs/announcements/pt/headless-cms-updated-user-permissions.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 6EvqWHQ2akp2dpdjChGJcy
+status: DRAFT
+createdAt: 2024-01-11T18:15:47.624Z
+updatedAt: 2024-01-11T18:21:20.966Z
+publishedAt: 
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: untitled-entry-2024-01-11-at-18-15-47
+locale: pt
+legacySlug: untitled-entry-2024-01-11-at-18-15-47
+announcementImageID: ''
+announcementSynopsisPT: ''
+---
+
+
diff --git a/docs/announcements/pt/improved-security-for-the-customers-first-purchase.md b/docs/announcements/pt/improved-security-for-the-customers-first-purchase.md
index d506c3480..c9eac3b2e 100644
--- a/docs/announcements/pt/improved-security-for-the-customers-first-purchase.md
+++ b/docs/announcements/pt/improved-security-for-the-customers-first-purchase.md
@@ -1,9 +1,9 @@
 ---
 title: 'Melhoria de segurança na primeira compra do cliente'
-id: DKlfRaMNHxgQhUT5VqRrK
+id: 3RBko0KXi8eOm4nKARgReD
 status: DRAFT
-createdAt: 2023-04-28T12:35:44.503Z
-updatedAt: 2023-06-09T15:37:43.651Z
+createdAt: 2023-07-03T11:34:49.078Z
+updatedAt: 2023-10-09T14:12:03.607Z
 publishedAt: 
 contentType: updates
 productTeam: Shopping
@@ -21,7 +21,7 @@ Visando aprimorar a segurança das informações da sua loja, a VTEX realizou me
 
 Durante a primeira compra, as informações pessoais do cliente são exibidas sem mascaramento junto ao carrinho, já que ele ainda não possui um perfil criado na loja.
 
-Agora, durante a criação de um novo carrinho, além do cookie `checkout.vtex.com` que contém o orderFormId, um novo cookie (`CheckoutOrderFormOwnership`) será encaminhado. Isso permitirá que apenas o cliente que criou o carrinho tenha acesso irrestrito às suas informações.
+Agora, durante a criação de um novo carrinho, além do cookie `checkout.vtex.com` que contém o `orderFormId`, um novo cookie (`CheckoutOrderFormOwnership`) será encaminhado. Isso permitirá que apenas o cliente que criou o carrinho tenha acesso irrestrito às suas informações.
 
 Caso haja uma tentativa externa de acesso aos dados do carrinho, as informações pessoais do cliente original não poderão ser visualizadas, pois os dados aparecerão mascarados.
 
diff --git a/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md b/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md
index cfcc9b4a7..96574029b 100644
--- a/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md
+++ b/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md
@@ -24,16 +24,16 @@ Antes desta mudança, era possível ocorrer erros de visualização no resumo do
 Considere, por exemplo, um usuário que vê um produto que custa R$ 600,00, elegível para um desconto de 10% em caso de pagamento à vista. A pessoa procede para o checkout e chega à página do resumo do pedido, na qual deverá selecionar as opções de pagamento. Estes são os três erros principais que poderiam ocorrer:
 
 - O usuário ainda não selecionou um número de parcelas e o preço é exibido sem descontos, mesmo na opção elegível.
-![O usuário ainda não selecionou um número de parcelas](https://images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
+![O usuário ainda não selecionou um número de parcelas](//images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
 
 - O usuário selecionou um número de parcelas não elegível para desconto e o preço é exibido sem descontos, mesmo na opção elegível (à vista).
-![O usuário selecionou um número de parcelas não elegível para desconto](https://images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
+![O usuário selecionou um número de parcelas não elegível para desconto](//images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
 
 - O usuário selecionou um número de parcelas elegível (à vista) para desconto e o desconto é exibido mesmo em opções não elegíveis.
-![O usuário selecionou um número de parcelas elegível para desconto (à vista)](https://images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
+![O usuário selecionou um número de parcelas elegível para desconto (à vista)](//images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
 
 Com essa mudança, o desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.
-![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](https://images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
+![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](//images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
 
 ## Por que realizamos essa mudança?
 
diff --git a/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md b/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md
index 24cbf885b..ff54522d5 100644
--- a/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md
+++ b/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md
@@ -25,7 +25,7 @@ Na VTEX, é possível alterar o preço várias vezes ao dia de acordo com a estr
 
 O cadastro via planilha se dá por duas etapas, a exportação e importação. A exportação dos preços teve sua experiência aprimorada com novas features, buscando dar mais visibilidade ao usuário do status de cada planilha de exportação de preços.
 
-![exportacao pt](https://images.ctfassets.net/alneenqid6w5/3yLQbrPd39kTWYnNrsbJgC/fbf24da5553dee1c5bc0ba5a51e2f070/exportacao_pt.gif)
+![exportacao pt](//images.ctfassets.net/alneenqid6w5/3yLQbrPd39kTWYnNrsbJgC/fbf24da5553dee1c5bc0ba5a51e2f070/exportacao_pt.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md b/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md
new file mode 100644
index 000000000..60a9b011e
--- /dev/null
+++ b/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md
@@ -0,0 +1,43 @@
+---
+title: 'Melhorias na busca unificada do VTEX Sales App'
+id: 4ZfzuvJjgtfjNR3UXrggYN
+status: PUBLISHED
+createdAt: 2024-05-03T12:45:14.073Z
+updatedAt: 2024-05-06T13:37:06.301Z
+publishedAt: 2024-05-06T13:37:06.301Z
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: melhorias-na-busca-unificada-do-vtex-sales-app
+locale: pt
+legacySlug: melhorias-na-busca-unificada-do-vtex-sales-app
+announcementImageID: ''
+announcementSynopsisPT: 'Melhoramos a busca unificada do VTEX Sales App para aprimorar a experiência dos usuários ao navegar e buscar produtos.'
+---
+
+Aprimoramos a busca unificada do VTEX Sales App, visando melhorar a experiência dos usuários durante a navegação e busca de produtos no VTEX Sales App.
+
+Com essa melhoria, os vendedores podem encontrar produtos além do estoque da loja e adicioná-los ao carrinho. Basta clicar no ícone de lupa <i class="fas fa-search"></i> e digitar o nome do produto, código referência, SKU ID ou EAN na barra de busca da página inicial da loja.
+
+## O que mudou?
+Com a nova melhoria, você encontrará mudanças que visam melhorar sua experiência de busca e compra:
+
+- **Lista de busca intuitiva:** você terá acesso a uma lista de busca intuitiva e informativa, que oferece uma visão simplificada das suas buscas anteriores.
+
+- **Visualização detalhada dos produtos:** os espaços foram otimizados, permitindo que você veja mais itens com imagens maiores e de maior qualidade. Ao adicionar produtos ao carrinho, principalmente aqueles com SKU único, o processo de adição agora é mais direto e simplificado.
+
+- **Refinamento de busca com filtros:** é possível aplicar filtros clicando sobre os filtros pré-definidos, sem a necessidade de enviar o formulário com o botão `Aplicar filtros`. Além disso, os filtros aplicados serão exibidos no topo da página, tornando mais fácil saber quais filtros estão em uso e remover qualquer um de forma simples.
+
+- **Visualização rápida de produtos indisponíveis:** antes, o sistema exibia todos os produtos como indisponíveis e, após alguns segundos, carregava a informação da disponibilidade. Agora, a disponibilidade do produto é exibida imediatamente quando o produto é exibido.
+
+- **Otimização para conexões lentas:** com o uso de caches do navegador, a busca retornará novas informações apenas quando necessário, garantindo uma resposta rápida mesmo em cenários de conexão lenta.
+
+![Mobile - PT](//images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/9d6c3d38f68b7ddbca623b0cf4b2067a/mobile__1_.gif)
+
+## Por que fizemos essa mudança?
+
+Desenvolvemos esta melhoria principalmente para os vendedores de lojas físicas, para melhorar a sua experiência ao navegar e pesquisar por produtos. Assim, proporcionamos que a sua jornada de busca seja mais intuitiva e informativa.
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. A funcionalidade será aplicada automaticamente em todas as lojas VTEX que utilizam o VTEX Sales App. Para mais informações, acesse o artigo [Busca unificada no VTEX Sales App](https://help.vtex.com/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/9sXeVwoD60qYYgRJ11r5F). 
diff --git a/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md b/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md
index 4579b561d..98bb3b6ee 100644
--- a/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md
+++ b/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md
@@ -22,7 +22,7 @@ Esta ferramenta permite o controle das aprovações de pedidos com mudanças em
 ## O que muda
 Agora, ao invés de abrir um chamado diretamente com o suporte, é possível configurar as regras de autorização pelo admin. Para isso, acesse o caminho: Menu - Gerenciamento de Pedidos - Autorização de Pedidos.
 
-![Print Tela Principal OrderAuthorization (2)](https://images.ctfassets.net/alneenqid6w5/3hRybooCq6ynxWhOBN2J6C/58182a66426ecd5d480c9a79a5f8a9e7/Print_Tela_Principal_OrderAuthorization__2_.jpg)
+![Print Tela Principal OrderAuthorization (2)](//images.ctfassets.net/alneenqid6w5/3hRybooCq6ynxWhOBN2J6C/58182a66426ecd5d480c9a79a5f8a9e7/Print_Tela_Principal_OrderAuthorization__2_.jpg)
 
 ## O que você precisa fazer
 Importante mencionar que a loja não perde as regras configuradas através do fluxo antigo, que era feito abrindo chamado para a equipe de suporte. Elas serão atualizadas automaticamente na nova tela.
diff --git a/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
index 11133d20b..7f2951423 100644
--- a/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
@@ -19,7 +19,7 @@ A partir de 31 de maio, estamos lançando para todas as lojas VTEX a versão bet
 
 As páginas da **Estratégia de envio** foram atualizadas para o novo design system da VTEX, como pode ser visto a seguir:
 
-![nova_estrategia_envio_announcement_boards_PT](https://images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/b93bbe35c2870827dd761f244cb447dc/nova_estrategia_envio_announcement_boards_PT.png)
+![nova_estrategia_envio_announcement_boards_PT](//images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/b93bbe35c2870827dd761f244cb447dc/nova_estrategia_envio_announcement_boards_PT.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/introducing-vtex-ad-network-beta.md b/docs/announcements/pt/introducing-vtex-ad-network-beta.md
new file mode 100644
index 000000000..d913ffe63
--- /dev/null
+++ b/docs/announcements/pt/introducing-vtex-ad-network-beta.md
@@ -0,0 +1,51 @@
+---
+title: 'Apresentando: VTEX Ad Network (Beta)'
+id: 5Xk8ekbP2Vb5QoI8GXRsQ6
+status: DRAFT
+createdAt: 2024-04-30T16:15:57.595Z
+updatedAt: 2024-04-30T17:41:55.796Z
+publishedAt: 
+contentType: updates
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: apresentando-vtex-ad-network-beta
+locale: pt
+legacySlug: apresentando-vtex-ad-network-beta
+announcementImageID: ''
+announcementSynopsisPT: 'A VTEX está lançando uma plataforma de anúncios, uma forma de conectar anunciantes a lojas para promover produtos.'
+---
+
+A VTEX está lançando [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur). Este é um produto que conecta lojas a marcas interessadas em promover seus produtos. Com esta conexão, anunciantes e lojas podem potencializar seu negócio.
+
+## Anunciantes
+
+Anunciantes podem [criar campanhas](https://help.vtex.com/pt/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse) de anúncios para promover seus produtos nas frentes de lojas que vendem aqueles produtos. Desta forma, podem impulsionar vendas e visualizar dados para melhorar a tomada de decisão.
+
+Ao criar campanhas para um produto da sua marca, seu anúncio poderá aparecer em espaços de destaque em diversas lojas VTEX que já possuem aquele produto em seu catálogo.
+
+![vtex_ad_network_admin_PT](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/c479a1adcfce1ab838edfa17aeb6aca7/vtex_ad_network_admin.png)
+
+## Lojas
+
+Podem disponibilizar espaço publicitário para que anunciantes promovam seus produtos na sua frente de loja. Estas lojas receberão um valor por cada clique recebido em anúncios na sua loja.
+
+A VTEX selecionará para a sua loja anúncios de produtos que já compõem o seu catálogo, garantindo uma jornada de compra fluida e sem quebras. Esta seleção é feita com base no contexto de navegação dos clientes da sua loja.
+
+![vtex_ad_network_sponsored_PT](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
+
+## O que precisa ser feito?
+
+Veja abaixo como você pode fazer parte da **VTEX Ad Network**, seja como loja ou anunciante.
+
+### Lojas
+
+Para disponibilizar espaço publicitário na sua loja, basta instalar o app [VTEX Ad Network para lojas]() na sua conta VTEX. Saiba mais com o artigo [Exibindo anúncios do VTEX Ad Network na sua loja (Beta)](https://help.vtex.com/pt/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA).
+
+<div class="alert alert-danger">
+Por hora, podem disponibilizar espaço de anúncios apenas lojas desenvolvidas com <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
+</div>
+
+### Anunciantes
+
+Qualquer marca que deseja promover seus produtos que já são vendidos em lojas VTEX pode anunciar com **VTEX Ad Network**. Saiba mais com os artigos [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) e [Anunciando com VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse).
+
diff --git a/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md b/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
index 40a3f179a..8fa08abd8 100644
--- a/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
+++ b/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
@@ -28,4 +28,4 @@ Ao tentar acessar o Admin de uma loja usando um endereço de email, você tem a
 
 Segurança é uma das principais preocupações na VTEX, e isso se torna ainda mais importante quando estamos próximos de grandes eventos como a Black Friday. Esse novo recurso pode ajudar a identificar a fonte de uma tentativa de acesso indesejado.
 
-![IP Geolocation email - PT](https://images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/0f65303dae22ac38b6f66e1942830224/IP_Geolocation_email_-_PT.png)
+![IP Geolocation email - PT](//images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/0f65303dae22ac38b6f66e1942830224/IP_Geolocation_email_-_PT.png)
diff --git a/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
new file mode 100644
index 000000000..0e8f94c4e
--- /dev/null
+++ b/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
@@ -0,0 +1,50 @@
+---
+title: 'Lead time: configure tempo de envio a nível de SKU'
+id: 39Q8TeXaDCbmTXFtwpNXlf
+status: PUBLISHED
+createdAt: 2023-09-22T14:07:20.464Z
+updatedAt: 2023-09-28T17:47:25.398Z
+publishedAt: 2023-09-28T17:47:25.398Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: lead-time-configure-tempo-de-envio-a-nivel-de-sku
+locale: pt
+legacySlug: lead-time-configure-tempo-de-envio-a-nivel-de-sku
+announcementImageID: ''
+announcementSynopsisPT: 'Lançamento global do lead time, uma configuração opcional do tempo de envio a nível de SKU.'
+---
+
+A VTEX disponibilizou para todas as lojas o [lead time](https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B), uma configuração do tempo de envio do SKU de um estoque. Ou seja, você pode definir a nível de SKU um tempo de envio adicional no cálculo das promessas de envio apresentadas para os clientes no checkout.
+
+![lead_time_image_total_time_PT](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
+
+O uso do lead time é opcional e, quando não configurado, o envio de pedidos da loja segue inalterado. Vale ressaltar que as regras de consolidação do checkout se mantêm, calculando o prazo de envio total do pedido pelo maior tempo de um dos itens.
+
+## O que mudou?
+
+Antes, o [cálculo de envio](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) de pedidos considerava os períodos configurados na sua estratégia de envio a nível de:
+
+* [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+* [Doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+* [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
+
+Agora, existe também a opção de configurar o tempo de envio a nível de SKU, com a nova coluna do lead time na página [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-inventario--tutorials_139), que se encontra no seu Admin VTEX, em **Catálogo > Estoque > Gerenciamento de inventário**, como na imagem abaixo:
+
+![lead_time_inventory_management_PT](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
+
+<div class="alert alert-warning">
+Pelo Admin VTEX, o lead time é configurado em dias, até o limite de 365 dias. Por padrão, os dias são contados em dias úteis, mas você pode configurar sua política de envio para que a <a href="https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional">contagem seja feita em dias corridos</a>. Para configurar períodos em horas, minutos e segundos, é necessário utilizar o endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## Por que fizemos essa mudança?
+
+Os principais benefícios com a nova configuração lead time são:
+
+* **Maior flexibilidade no gerenciamento de inventário**, especialmente útil para negócios com produtos criados sob demanda e cenários _dropshipping_ (o fornecedor envia o produto direto para o cliente).
+* **Configurações mais precisas de prazos de envio**, o que facilita a sua gestão de estoque.
+* **Estimativas de promessas de envio mais acuradas** para os clientes, o que contribui para melhor experiências de compra.
+
+## O que precisa ser feito?
+
+A página [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-inventario--tutorials_139) do Admin VTEX de todas as lojas foi atualizada com uma coluna do lead time, e não é necessária qualquer ação da sua parte. A utilização do novo campo é opcional, caso você não realize nenhuma configuração, o prazo de envio dos seus pedidos seguirá inalterado.
diff --git a/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md b/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md
new file mode 100644
index 000000000..697814ba7
--- /dev/null
+++ b/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md
@@ -0,0 +1,123 @@
+---
+title: 'Conectores legados de pagamentos serão descontinuados em 2024'
+id: 4R5YIjUu1IWkiOHzXtQU14
+status: PUBLISHED
+createdAt: 2023-10-13T12:52:48.753Z
+updatedAt: 2023-10-17T20:57:39.669Z
+publishedAt: 2023-10-17T20:57:39.669Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: conectores-legados-de-pagamentos-serao-descontinuados-em-2024
+locale: pt
+legacySlug: conectores-legados-de-pagamentos-serao-descontinuados-em-2024
+announcementImageID: ''
+announcementSynopsisPT: 'Em 2024, a VTEX descontinuará os conectores legados de pagamentos, que não utilizam o Payment Provider Protocol.'
+---
+
+Para integrar meios de pagamentos à plataforma VTEX, provedores de pagamentos podem criar conectores de pagamentos utilizando o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) (PPP). Entretanto, há diversos conectores legados utilizando versões anteriores da nossa arquitetura de integração de pagamentos, que são menos estáveis e menos performáticas.
+
+## O que está mudando?
+
+<div class="alert alert-danger">
+As mudanças descritas neste documento não terão impacto na Black Friday 2023. Serão realizadas apenas no primeiro trimestre de 2024.
+</div>
+
+A VTEX está iniciando a descontinuação destes conectores legados, que acontecerá em etapas:
+
+- **31 de janeiro de 2024** - Bloqueio da criação de novas afiliações de gateway usando conectores legados de pagamento. A partir desta data, lojas VTEX não poderão mais configurar conexões com os conectores que serão descontinuados. Todas as regras de pagamento já configuradas continuarão funcionando normalmente, sem impacto nas transações.
+- **10 de fevereiro de 2024** - Data limite sugerida para submeter novos conectores para homologação. Caso empresas parceiras desejem desenvolver novos conectores usando o [PPP](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m), para substituir os conectores legados, é necessário que submetam para homologação até esta data. Caso contrário, a VTEX não garante a homologação de novos conectores em tempo hábil para que as lojas façam a configuração com o novo conector. Saiba mais sobre o [processo de homologação de novos conectores de pagamento](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+- **31 de março de 2024** - Descontinuação definitiva de conectores que não usam o [PPP](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). A partir desta data a VTEX bloqueará todas as transações de conectores legados de pagamentos.
+
+### Lista dos conectores legados de pagamentos
+
+Confira a lista de todos os conectores que serão descontinuados:
+
+- Adyen
+- Alignet
+- Amex
+- AuthorizeNet/AuthorizeDotNet
+- BanamexInvoice
+- BankInvoiceItau/BankIssuedInvoiceItau
+- BankInvoiceSantander/BankIssuedInvoiceSantander
+- Bcash
+- BoldCron
+- Bradesco/RegisteredBankInvoiceBradesco
+- BrasPag/Braspag
+- Cielo/CieloV3
+- Conductor
+- Credomatic
+- CyberSource
+- Decidir/DecidirV1
+- ERede/E-Rede V2/ERedeRest
+- Evolucard
+- Firstdata
+- IPay88
+- ItauShopline
+- Koin
+- MaxiPago
+- MeoWallet
+- MercadoPagoV1
+- MobilPay
+- Moip
+- MOLPay
+- Mundipagg/MundipaggFraudPrevention
+- Nexxpago
+- NPS
+- PagamentoDigital
+- PagBrasil
+- PagHiper
+- PagoEfectivo
+- PagosNet
+- PagosWeb
+- PagSeguro/PagSeguroDirect
+- PayClub
+- Payme
+- Paymentez
+- PaymentHub
+- PaymentsOS
+- PayPal/PayPalPlus
+- PayU/PayUGlobal
+- Payzen
+- Place2Pay/PlaceToPay
+- Rede Pay/RedePay
+- Redecard
+- Redsys/RedsysV2
+- SafetyPay
+- SalesMachine
+- Scopus
+- Sitef/SitefDirectSale/SitefPreauth
+- Stelo
+- TNSPay
+- TodoPago
+- WebPay/WebPay2P
+- WorldPay
+
+## Por que estamos fazendo essa mudança?
+
+Os conectores que utilizam o [PPP](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) possuem taxas de autorização maiores do que os conectores legados. Portanto, migrar para novos conectores tende a aumentar as vendas das lojas VTEX.
+
+Além disso, muitos conectores legados estão desatualizados em termos de tecnologia. A migração para conectores que utilizam o [PPP](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) garante que as lojas VTEX utilizarão tecnologias mais modernas e estáveis oferecidas pela VTEX.
+
+## O que precisa ser feito?
+
+As ações necessárias a partir desta mudança dependem do seu contexto no ecossistema VTEX. Confira abaixo qual opção melhor se aplica ao seu negócio.
+
+### Responsáveis por conectores legados de pagamentos
+
+Se você é um provedor de pagamentos responsável por um ou mais [conectores que serão descontinuados](#lista-dos-conectores-legados-de-pagamentos), você deve desenvolver um novo conector utilizando o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Caso contrário, não poderá processar transações a partir da data de descontinuação mencionada acima.
+
+Neste caso, recomendamos que submeta seu novo conector para homologação até 10 de fevereiro de 2024, para que as lojas tenham tempo hábil para reconfigurar suas conexões de pagamentos antes da descontinuação. Saiba mais sobre o [processo de homologação de novos conectores de pagamento](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+
+<div class="alert alert-danger">
+A VTEX não pode garantir que seu novo conector de pagamentos estará disponível para lojistas VTEX antes da descontinuação oficial caso você o submeta para homologação após esta data.
+</div>
+
+Caso tenha dúvidas sobre este processo ou queira alinhar a comunicação conjunta com lojistas, entre em contato com seu Partner Manager VTEX.
+
+### Lojas que utilizam de conectores legados de pagamentos
+
+Se a sua loja utiliza um dos [conectores que serão descontinuados](#lista-dos-conectores-legados-de-pagamentos), você deve realizar configuração com o novo conector correspondente àquele provedor de pagamento antes de 31 de março de 2024. Caso contrário, não será possível realizar compras na sua loja utilizando o meio de pagamento em questão.
+
+Ao longo do processo de descontinuação e migração, você pode entrar em contato com seus provedores de pagamentos para acompanhar a evolução e obter mais informações sobre o desenvolvimento dos novos conectores.
+
diff --git a/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
new file mode 100644
index 000000000..85ebca27a
--- /dev/null
+++ b/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -0,0 +1,40 @@
+---
+title: 'Algoritmo de Luhn para cartões de crédito e débito no Checkout'
+id: 22hAb6KVWUitIG9OzFzgi2
+status: PUBLISHED
+createdAt: 2023-09-19T15:43:01.350Z
+updatedAt: 2023-09-19T16:47:51.216Z
+publishedAt: 2023-09-19T16:47:51.216Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: algoritmo-de-luhn-para-cartoes-de-credito-e-debito-no-checkout
+locale: pt
+legacySlug: algoritmo-de-luhn-para-cartoes-de-credito-e-debito-no-checkout
+announcementImageID: ''
+announcementSynopsisPT: 'Reduza o percentual de transações rejeitadas por motivo de número de cartão inválido'
+---
+
+A VTEX disponibiliza a partir de agora no Checkout, a validação dos números de cartão de crédito e débito por meio do algoritmo de Luhn.
+
+## O que mudou?
+
+Anteriormente, no momento em que um cliente inseria um número de cartão no Checkout, não era possível identificar se o número correspondia a um cartão válido. Quando ocorriam erros de digitação ou preenchimento, a transação de pagamento era criada e posteriormente cancelada durante a fase de autorização.
+
+A partir de agora, o algoritmo de Luhn será aplicado para assegurar que somente um número de cartão válido possa ser utilizado na compra. Desta forma, o percentual de transações rejeitadas pelo uso de um número de cartão inválido será reduzido.
+
+Caso um cliente digite um número incorreto, uma mensagem de erro será exibida no Checkout. Nesta situação, o cliente deverá verificar o número inserido e corrigí-lo para prosseguir com a finalização da compra.
+
+![algoritmo_luhn_pt](//images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/2ab586ebecb172fa058c7daffdb5833d/algoritmo_luhn_pt.PNG)
+
+## Por que fizemos essa mudança?
+
+A rejeição de uma transação de pagamento por motivo de número de cartão inválido, poderia contribuir para a desistência do cliente em realizar uma nova compra, já que seria necessário corrigir o número do cartão. Portanto, esta melhoria na experiência de compra visa aumentar a taxa de conversão da sua loja.
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. O algoritmo de Luhn já está ativo em todas as lojas VTEX.
+
+<div class="alert alert-warning">
+O algoritmo de Luhn não tem a função restringir fraudes por ataques de cartões. Seu objetivo específico é a verificação de erros de digitação ou preenchimento dos números dos cartões.
+</div>
diff --git a/docs/announcements/pt/marketplace-improvements-on-received-skus.md b/docs/announcements/pt/marketplace-improvements-on-received-skus.md
index 42483522b..2ab2c0a94 100644
--- a/docs/announcements/pt/marketplace-improvements-on-received-skus.md
+++ b/docs/announcements/pt/marketplace-improvements-on-received-skus.md
@@ -29,7 +29,7 @@ Vale notar que essa ação pode ser desfeita. É possível aprovar um SKU bloque
 
 Não é preciso realizar nenhuma configuração para ativar essa funcionalidade, ela será instalada de forma automática na plataforma VTEX. Para saber mais sobre o bloqueio de SKUs, no painel do módulo SKUs recebidos, confira nosso artigo sobre [Catalogação manual de SKUs](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus--tutorials_396).
 
-![PT SKUs Recebidos Announcement](https://images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/b6d7724cfd093568a02012b5fdd14afe/PT_SKUs_Recebidos_Announcement.jpg)
+![PT SKUs Recebidos Announcement](//images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/b6d7724cfd093568a02012b5fdd14afe/PT_SKUs_Recebidos_Announcement.jpg)
 
 ## Configurações de aprovação automática de SKUs
 
diff --git a/docs/announcements/pt/marketplace-network-has-been-improved.md b/docs/announcements/pt/marketplace-network-has-been-improved.md
index 8668ee33e..8137a45d6 100644
--- a/docs/announcements/pt/marketplace-network-has-been-improved.md
+++ b/docs/announcements/pt/marketplace-network-has-been-improved.md
@@ -19,7 +19,7 @@ Para marketplaces e sellers do nosso ecossistema, um dos maiores desafios é con
 
 O Marketplace Network foi redesenhado para melhorar sua experiência. Além disso, não é mais preciso baixar a app em nossa App Store, a funcionalidade foi inserida em todas as lojas que atuam como sellers ou marketplaces automaticamente.
 
-![Marketplace network tour](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
+![Marketplace network tour](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
 
 ## O que mudou?
 As páginas do Marketplace Network passaram por algumas mudanças:
diff --git a/docs/announcements/pt/marketplace-new-offer-quality-filters.md b/docs/announcements/pt/marketplace-new-offer-quality-filters.md
index c42668c02..9b93f7349 100644
--- a/docs/announcements/pt/marketplace-new-offer-quality-filters.md
+++ b/docs/announcements/pt/marketplace-new-offer-quality-filters.md
@@ -21,7 +21,7 @@ Para que marketplaces tenham mais controle sobre os critérios de aprovação de
 
 Dessa forma, os SKUs que chegam até o marketplace já estão de acordo com os requisitos que importam na curadoria de seu catálogo. 
 
-![Offer Quality gif](https://images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/4311d5d111ba8d0f8f92a586dd833eef/Offer_Quality_01.gif)
+![Offer Quality gif](//images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/4311d5d111ba8d0f8f92a586dd833eef/Offer_Quality_01.gif)
 
 ## O que mudou? 
 
diff --git a/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md b/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md
index d2eed2141..e774e5706 100644
--- a/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md
+++ b/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md
@@ -24,7 +24,7 @@ Até então, para conferir as informações de um SKU recebido era preciso acess
 
 A barra contém  imagens do SKU, preço, nível de estoque, além de outros atributos do produto, como descrição, especificações, códigos e IDs. Também inclui a porcentagem de equivalência que o SKU recebeu pelo [matcher](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) instalado em sua loja. Ainda é possível acessar a página completa de detalhes do SKU, clicando no botão *Ver página de detalhes*. 
 
-![Sidebar received](https://images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/6ea0f2c2f6403f60b7ca96418da7f04e/Sidebar_received.gif)
+![Sidebar received](//images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/6ea0f2c2f6403f60b7ca96418da7f04e/Sidebar_received.gif)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md b/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md
index f3f02e18e..d1b706a79 100644
--- a/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md
+++ b/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Unificamos o Marketplace Network e o módulo de Integra
 
 Para centralizar as oportunidades de conexão com marketplaces VTEX e marketplaces externos, unificamos as páginas de Integrações e Marketplace Network, chamando-se agora __Marketplaces e Integrações__. A atualização estará disponível em todas as contas VTEX a partir do dia 03 de maio de 2023. 
 
-![Marketplace e integrações](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png)
+![Marketplace e integrações](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png)
 
 ## O que mudou?  
 
diff --git a/docs/announcements/pt/marketplaces-received-skus-beta.md b/docs/announcements/pt/marketplaces-received-skus-beta.md
index 310b7453d..46f9015ca 100644
--- a/docs/announcements/pt/marketplaces-received-skus-beta.md
+++ b/docs/announcements/pt/marketplaces-received-skus-beta.md
@@ -25,7 +25,7 @@ A versão beta está aberta para todos que quiserem testar e é só a primeira d
 
 Uma das principais melhorias é a nova forma de selecionar SKUs em massa. Assim, você pode aprovar ou rejeitar todos eles de uma só vez. Alinhado com nosso [Styleguide](https://styleguide.vtex.com/ "Styleguide"), a seleção em massa vai trazer ainda mais agilidade e eficiência para o seu trabalho.
 
-![received-skus-bulk](https://images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
+![received-skus-bulk](//images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
 
 
 
@@ -33,13 +33,13 @@ Uma das principais melhorias é a nova forma de selecionar SKUs em massa. Assim,
 Um dos desafios de gerenciar itens de múltiplos sellers é priorizar uma lista que nunca acaba. Para ajudar, construímos uma nova funcionalidade de ordenação, para você reordenar tudo o que foi enviado por preço e - uma das principais melhorias - por disponibilidade de estoque. Visualize com facilidade quantos itens estão disponíveis e aprove os SKUs que vão performar melhor.
 
 
-![received-skus-ordering](https://images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
+![received-skus-ordering](//images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
 
 
 Tudo isso é potencializado com os novos filtros. Veja e filtre SKUs por categoria, marca e seller de forma simples e intuitiva.
 
 
-![received-skus-filtering](https://images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
+![received-skus-filtering](//images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
 
 
 
diff --git a/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md b/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md
new file mode 100644
index 000000000..6629b6e0a
--- /dev/null
+++ b/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md
@@ -0,0 +1,53 @@
+---
+title: 'Master Data v1: deprecação de configurações dinâmicas'
+id: 4a1FZX8wGeHLcOyMg0egg8
+status: PUBLISHED
+createdAt: 2024-04-17T12:34:11.024Z
+updatedAt: 2024-04-17T12:48:51.570Z
+publishedAt: 2024-04-17T12:48:51.570Z
+contentType: updates
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: master-data-v1-deprecacao-de-configuracoes-dinamicas
+locale: pt
+legacySlug: master-data-v1-deprecacao-de-configuracoes-dinamicas
+announcementImageID: ''
+announcementSynopsisPT: 'O Campo calculado e a ação de trigger “Alterar valor do campo” serão descontinuados do Master Data v1.'
+---
+
+No dia 17 de junho de 2024, vamos desabilitar as seguintes configurações no Master Data v1: **Campo calculado** e ação de ativação (trigger) **Alterar valor do campo**.
+
+Essas opções permitiam alterar valores de documentos no [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) de forma dinâmica, executando código a partir de um trigger ou da atualização/criação de um documento.
+
+Para substituir essas configurações, caso seja necessário atualizar valores de campos de forma dinâmica, recomendamos [criar um app para se comunicar com o Master Data](https://developers.vtex.com/docs/guides/create-master-data-crud-app).
+
+## O que mudou?
+
+Ambas as configurações dinâmicas serão desativadas no Master Data v1.
+
+Note que **Campos calculados** e triggers já existentes que utilizam a função **Alterar valor do campo** deixarão de funcionar na mesma data. Veja a seção [O que precisa ser feito?](#o-que-precisa-ser-feito) para mais informações sobre como se adequar a essas mudanças.
+
+### Campo calculado
+
+O **Campo calculado** era uma configuração dentro dos campos de [entidade de dados](https://help.vtex.com/pt/tutorial/entidade-de-dados--tutorials_1265) que permitia a execução de código C# para recalcular o valor do campo sempre que um novo documento fosse inserido ou atualizado.
+
+Esse tipo de campo, ilustrado abaixo, não estará mais disponível a partir de 17 de junho de 2024. Os campos calculados criados previamente deixarão de funcionar na mesma data.
+
+![md-deprecation-calculated-field-pt](//images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/e25fa67f6207592c2893b3f86132c057/md-deprecation-calculated-field-pt.png)
+
+### Alterar valor do campo
+
+Ao configurar ações de triggers na aba **Ativação**, havia a opção de **Alterar valor do campo**, que permitia adicionar código C# para modificar o valor de campos selecionados a cada execução do trigger.
+
+A opção **Alterar valor do campo**, ilustrada abaixo, não estará mais disponível ao configurar ações de triggers a partir de 17 de junho de 2024. Os triggers criados anteriormente com essa ação continuarão funcionando somente até essa data.
+
+![md-deprecation-trigger-pt](//images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/267ad58ad21c7ba83b7182d3bc4c581b/md-deprecation-trigger-pt.png)
+
+## O que precisa ser feito?
+
+Se você precisar atualizar os valores de campo do Master Data com base em um trigger, recomendamos que contate o seu time de desenvolvimento para seguir as orientações abaixo:
+
+* Desenvolva um app no VTEX IO que se comunique com o Master Data, seguindo as orientações do guia para desenvolvedores [Creating a Master Data CRUD app](https://developers.vtex.com/docs/guides/create-master-data-crud-app).
+* Configure um trigger que envie uma requisição HTTP para o app, seguindo as instruções disponíveis em [Criar trigger no Master Data v1](https://help.vtex.com/pt/tutorial/criando-trigger-no-master-data--tutorials_1270#envie-requisicao-http).
+
+Se você utiliza o **Campo calculado** ou um trigger com a ação **Alterar valor do campo**, siga o procedimento acima antes de 17 de junho de 2024 para que os valores continuem sendo atualizados de forma dinâmica mesmo após a deprecação dessas configurações no Master Data v1.
diff --git a/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md b/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md
index 380ca0b66..38bef89a1 100644
--- a/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md
+++ b/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md
@@ -19,7 +19,7 @@ Dando continuidade às melhorias feitas para a [certificação do Mercado Livre]
 
 Na nova página de **Promoções** do Mercado Livre, é possível gerenciar uma lista com diferentes campanhas promocionais na plataforma disponíveis para a sua loja.
 
-![Promoções](https://images.ctfassets.net/alneenqid6w5/7qDxLkDgrBDJWovD2dhG9I/08759bd0132772b8c5cb51078f9e80bd/Promo____es.gif)
+![Promoções](//images.ctfassets.net/alneenqid6w5/7qDxLkDgrBDJWovD2dhG9I/08759bd0132772b8c5cb51078f9e80bd/Promo____es.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md b/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
index 9e3be17c3..c0bbcfbd8 100644
--- a/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
+++ b/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
@@ -19,14 +19,14 @@ A partir de agora, sua loja pode usar ponto e vírgula (`;`) para concatenar end
 
 Esse recurso funciona nos campos de cópia (`Destinatário (CC)`) e cópia oculta (`Destinatário (CCO)`), assim como a vírgula já funcionava anteriormente. Agora as duas opções de concatenação são válidas.
 
-![Message Center bug fix](https://images.ctfassets.net/alneenqid6w5/1DCmh5JlI4cGyIEgwuQQUk/068e65871809d2810df7ec0427773b56/Message_Center_bug_fix.png)
+![Message Center bug fix](//images.ctfassets.net/alneenqid6w5/1DCmh5JlI4cGyIEgwuQQUk/068e65871809d2810df7ec0427773b56/Message_Center_bug_fix.png)
 
 Essa mudança simples no módulo responsável pelo envio de e-mails transacionais reduziu drasticamente a taxa de erros em comunicações com clientes.
 
 O gráfico abaixo mostra a taxa de erros de uma loja antes de implementarmos o suporte à concatenação com ponto e vírgula. Mais de 90% dos e-mails falhavam todos os dias.
 
-![Message Center bug fix 2](https://images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
+![Message Center bug fix 2](//images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
 
 Depois de implementada a melhoria, os erros no envio de e-mails transacionais da mesma loja foram completamente eliminados, como mostra este outro gráfico:
 
-![Message Center bug fix 3](https://images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
+![Message Center bug fix 3](//images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
diff --git a/docs/announcements/pt/multi-currency-gift-card.md b/docs/announcements/pt/multi-currency-gift-card.md
new file mode 100644
index 000000000..d62ef0204
--- /dev/null
+++ b/docs/announcements/pt/multi-currency-gift-card.md
@@ -0,0 +1,49 @@
+---
+title: 'Vales-presente multimoedas'
+id: 4FUXWCaQrFHcgjir698onc
+status: PUBLISHED
+createdAt: 2023-07-27T15:01:02.025Z
+updatedAt: 2023-07-27T16:13:02.651Z
+publishedAt: 2023-07-27T16:13:02.651Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: vales-presente-multimoedas
+locale: pt
+legacySlug: vales-presente-multimoedas
+announcementImageID: ''
+announcementSynopsisPT: 'Configure os vales-presente de sua loja em múltiplas moedas'
+---
+
+A VTEX disponibiliza a nova funcionalidade de configuração de vales-presente de acordo com as moedas locais utilizadas em sua loja.
+
+## O que mudou?
+
+Anteriormente, todos os vales-presente eram criados sem uma moeda específica atribuída ao seu valor. No momento da compra, o cliente aplicava o vale-presente como um dos meios de pagamento no Checkout e o valor era debitado conforme a moeda configurada nos produtos do carrinho.
+
+A partir de agora, o lojista poderá selecionar em qual moeda o vale-presente será gerado e disponibilizá-lo somente para compras efetuadas com esse mesmo tipo de moeda. 
+
+## Por que fizemos essa mudança?
+
+Em algumas regiões, como Europa e Estados Unidos, existem lojas atuando na venda de produtos para mais de um país e operando com tabelas de preços que utilizam moedas diferentes. Como não há operação de câmbio monetário na utilização do vale-presente, o valor de desconto poderia ser maior ou menor de acordo com a moeda aplicada no carrinho no momento da compra.
+
+## O que precisa ser feito?
+
+A atribuição de uma moeda específica para cada vale-presente é uma funcionalidade opcional. Caso não deseje indicar em qual moeda ele deve ser criado, o comportamento permanece o mesmo de uma loja que utiliza apenas um tipo de moeda, no qual os descontos no valor são aplicados sem conversão monetária.
+
+Para criar um vale-presente em uma moeda específica, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Promoções > Vales-presente**, ou digite **Vales-presente** na barra de busca no topo da página.
+2. Clique em `Criar vale` ou `Criar vales em massa` (para criar um lote de vales-presente).
+3. No campo **Código da moeda**, selecione a moeda desejada.
+4. Preencha os demais campos de criação do vale-presente.
+5. Clique em `Salvar`.
+
+![Vales-presente multimoedas](//images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/d27b2d03cf01d9626f267a315e2a0c88/GiftCard_Multicurrency_PT_1.PNG)
+
+As moedas disponíveis serão as mesmas cadastradas nas [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) de cada loja.
+
+<div class="alert alert-warning">
+A escolha da moeda deve ser realizada durante a criação de cada vale-presente ou de um lote de vales-presente. Não é possível modificar a moeda atribuída a um vale-presente após a sua criação. 
+</div>
+
diff --git a/docs/announcements/pt/multilanguage-checkout-launch.md b/docs/announcements/pt/multilanguage-checkout-launch.md
new file mode 100644
index 000000000..0d219c16b
--- /dev/null
+++ b/docs/announcements/pt/multilanguage-checkout-launch.md
@@ -0,0 +1,26 @@
+---
+title: 'Checkout Multilíngue: internacionalize sua loja'
+id: 6qvNJhChyccFS8mWoESMue
+status: PUBLISHED
+createdAt: 2024-04-22T16:22:22.210Z
+updatedAt: 2024-04-26T15:32:14.356Z
+publishedAt: 2024-04-26T15:32:14.356Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: lancamento-checkout-multilingue
+locale: pt
+legacySlug: lancamento-checkout-multilingue
+announcementImageID: ''
+announcementSynopsisPT: 'Explore o novo Checkout Multilíngue e expanda sua loja globalmente, oferecendo uma experiência de compra localizada.'
+---
+
+Apresentamos o **Checkout Multilíngue**, uma nova funcionalidade desenvolvida para elevar a experiência de compra em sua loja, independentemente do país. A partir do dia 29/04/2024, seus clientes podem desfrutar de uma jornada de compra internacionalizada, desde a navegação pelo catálogo até o processo de finalização da compra.
+
+## O que mudou?
+
+Com o **Checkout Multilíngue**, implementamos uma solução completa que traduz o catálogo de produtos para diferentes idiomas cadastrados previamente pelos lojistas. Isso significa que seus clientes podem explorar e comprar produtos sem barreiras linguísticas, tendo uma experiência de compra mais fluida e personalizada. O produto e suas informações serão mostrados na frente de loja no mesmo idioma na navegação e no processo de checkout. 
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária, já que as atualizações serão aplicadas automaticamente em todas as lojas VTEX a partir do dia 29/04/2024. Caso deseje adicionar alguma tradução do catálogo, siga o guia [Translating Catalog content](https://developers.vtex.com/docs/guides/catalog-internationalization) para cadastrá-las em seu catálogo.
diff --git a/docs/announcements/pt/my-authentication-section-in-my-account.md b/docs/announcements/pt/my-authentication-section-in-my-account.md
index ed316e547..58b791443 100644
--- a/docs/announcements/pt/my-authentication-section-in-my-account.md
+++ b/docs/announcements/pt/my-authentication-section-in-my-account.md
@@ -25,15 +25,15 @@ Esta mudança afetará todas as lojas da VTEX. Como a mudança interfere em algu
 
 Esta aba é um local onde os usuários serão capazes de gerenciar a sua senha. Na aba também é possível gerenciar as sessões de login, permitindo ao usuário encerrar outras sessões remotamente. Mais detalhes sobre o uso da aba podem ser encontrados na seção [Autenticação do artigo Configurar o My Account](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh).
 
-![My Authentication app PT](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
+![My Authentication app PT](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
 
-![My Authentication Session Management PT](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
+![My Authentication Session Management PT](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
 
 No dia 29/09 o componente de gerenciamento de senha também será removido do perfil do usuário para evitar a sua duplicidade. As imagens abaixo mostram exemplos de página de perfil do usuário com e sem o componente de gerenciamento de senha.
 
-![My Account with password PT](https://images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/2a78bae58eb46f9ec94c7bb70ccbe11c/My_Account_with_password_PT.png)
+![My Account with password PT](//images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/2a78bae58eb46f9ec94c7bb70ccbe11c/My_Account_with_password_PT.png)
 
-![My Account no password PT](https://images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/65082d69145a716441e2d2b555798c72/My_Account_no_password_PT.png)
+![My Account no password PT](//images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/65082d69145a716441e2d2b555798c72/My_Account_no_password_PT.png)
 
 ## Por que realizamos essa mudança?
 
@@ -66,12 +66,12 @@ Para tornar a aba My Authentication visível publicamente na sua loja:
 1. No painel lateral esquerdo do Admin, vá até a seção **CONFIGURAÇÕES DA CONTA**.
 2. Clique em **Aplicativos**.
 3. Clique em **Meus aplicativos**.  
-![My apps menu PT](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/600c792e5f1d3854175315a1854c85bc/My_apps_menu_PT.png)
+![My apps menu PT](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/600c792e5f1d3854175315a1854c85bc/My_apps_menu_PT.png)
 4. Vá até o app **My Account** e clique em `Configurações`.  
-![My apps installed PT](https://images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/20d89a53135279f89f0484c0bfef5685/My_apps_installed_PT.png)
+![My apps installed PT](//images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/20d89a53135279f89f0484c0bfef5685/My_apps_installed_PT.png)
 5. Na seção **AUTHENTICATION** das configurações do app, marque a caixa `Visible`.
 6. Clique em `Salvar`.  
-![My Authentication visible setting PT](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/537169239dc172ce1fe772aa91d75b92/My_Authentication_visible_setting_PT.png)
+![My Authentication visible setting PT](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/537169239dc172ce1fe772aa91d75b92/My_Authentication_visible_setting_PT.png)
 
 Também é possível acessar diretamente as configurações do app My Account no Admin por uma URL.
 - Caso a sua loja seja VTEX IO, utilize o endereço `https://{account}.myvtex.com/admin/apps/vtex.my-account@1.x/setup`, substituindo `{account}` pelo nome da conta.
@@ -79,4 +79,4 @@ Também é possível acessar diretamente as configurações do app My Account no
 
 Após habilitar a visibilidade da aba **Autenticação**, ela aparecerá no perfil de usuário da loja. Ela pode ser acessada por qualquer usuário pelo painel lateral esquerdo.
 
-![My Authentication app PT](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
+![My Authentication app PT](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
diff --git a/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md b/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
new file mode 100644
index 000000000..cf5c9d8af
--- /dev/null
+++ b/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
@@ -0,0 +1,44 @@
+---
+title: 'Novos gráficos e dados em tempo real na página Visão Geral (Beta)'
+id: 6yzy7BYw5rPbaH0WdrAHyI
+status: PUBLISHED
+createdAt: 2023-07-12T13:28:42.856Z
+updatedAt: 2023-08-07T15:31:50.283Z
+publishedAt: 2023-08-07T15:31:50.283Z
+contentType: updates
+productTeam: Management
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: novos-graficos-e-dados-em-tempo-real-na-pagina-visao-geral-beta
+locale: pt
+legacySlug: novos-graficos-e-dados-em-tempo-real-na-pagina-visao-geral-beta
+announcementImageID: ''
+announcementSynopsisPT: 'Redesenhamos a página inicial do seu Admin, agora com novos gráficos e dados em tempo real.'
+---
+
+A página [Visão Geral (Beta)](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) em seu Admin VTEX foi redesenhada e agora oferece novos gráficos, métricas e visualizações. Estas novas funcionalidades permitem o acompanhamento em tempo real da sua operação, fornecendo visibilidade sobre indicadores para que você e sua equipe tenham um feedback rápido das ações realizadas na loja e possam atuar prontamente em melhorias. 
+
+![PT Visão geral Beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/62aceefab415f246a39fcd604a89f080/PT_Visa__o_geral_Beta.png)
+
+## O que mudou?
+
+Atualizamos a interface e otimizamos a atualização dos dados para aprimorar suas análises. As mudanças incluem: 
+
+* **Dados em tempo real:** os gráficos na seção de Monitoramento são atualizados automaticamente em até três minutos, dependendo da visualização. Outras seções da página são atualizadas a cada 15 minutos. 
+* **Gráficos aprimorados:** agora você conta com os gráficos _Receita captada_, _Pedidos captados_ e _Novas sessões_ em destaque, com porcentagens de crescimento ou decrescimento, além do valor absoluto. Eles substituem os gráficos anteriores de _Análise de tendências de pedidos_ e _Categorias com maior receita_. O _Funil de vendas_ agora está aninhado dentro da métrica de _Taxa de Conversão_, podendo ser acessado ao clicar no ícone de seta <i class='fa fa-chevron-down'></i>.  
+* **Mudanças nas métricas:** removemos as métricas _Produtos populares sem estoque_ e _Pedidos com pagamento em autorização_ para dar destaque aos indicadores de receita e pedidos. Além disso, incluímos a nova métrica de _Pedidos cancelados_, que pode ser vista no gráfico de _Pedidos captados_, pois acreditamos que essa métrica é um melhor indicador da saúde de uma operação.  
+* **Novas visualizações:** alterne entre as visualizações `Acumulado` e `Últimas 2 horas` para ajustar a visualização de acordo com suas necessidades específicas. A opção _Acumulado_ é ideal para acompanhar o desempenho geral das ações na loja, enquanto a opção _Últimas 2 horas_ permite identificar comportamentos inesperados.
+
+## Por que fizemos essa mudança?
+
+Introduzimos as mudanças à página Visão Geral (Beta) para trazer mais paz de espírito para a sua operação, garantindo que a loja está operando como o esperado. 
+
+Os dados em tempo real apoiam sua equipe a analisar resultados de campanhas e verificar possíveis impactos negativos em mudanças de configurações ou implementações realizadas (deploys). As métricas destacadas indicam se houve impacto no número de pedidos, sessões ou conversão de clientes, afetando a saúde e desempenho do seu negócio.   
+
+## O que precisa ser feito?
+
+A versão atualizada da página [Visão Geral (Beta)](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) já está disponível no Admin VTEX a partir do dia 17 de agosto. Para acessar a página, no Admin VTEX, vá para **Dashboards > Visão Geral (Beta)**, ou digite _Visão Geral (Beta)_ na barra de busca no topo da página.
+
+O acesso à página será gratuito durante seu período em Beta, ou até decidido pela VTEX, porém é importante observar que podem ser aplicadas taxas extras no futuro. 
+
+A página Visão Geral atualmente presente no Admin VTEX continuará disponível para uso. Ambas as páginas poderão ser acessadas pelo menu [Dashboards](https://help.vtex.com/pt/tutorial/dashboards-overview--1yn2nZUoXtDO3teTEJsCNl) do seu Admin. 
+
diff --git a/docs/announcements/pt/new-checkout-settings-for-bot-attack-protection.md b/docs/announcements/pt/new-checkout-settings-for-bot-attack-protection.md
new file mode 100644
index 000000000..4cf82b3a9
--- /dev/null
+++ b/docs/announcements/pt/new-checkout-settings-for-bot-attack-protection.md
@@ -0,0 +1,52 @@
+---
+title: 'Novas configurações do Checkout para proteção contra ataques de bots'
+id: 3kA92hues6c2XgRe1uf2Or
+status: DRAFT
+createdAt: 2023-09-11T17:23:20.383Z
+updatedAt: 2024-06-28T18:38:49.327Z
+publishedAt: 
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: novas-configuracoes-do-checkout-para-protecao-contra-ataques-de-bots
+locale: pt
+legacySlug: novas-configuracoes-do-checkout-para-protecao-contra-ataques-de-bots
+announcementImageID: ''
+announcementSynopsisPT: 'Criamos novas configurações no Checkout, para evitar fraudes e pedidos não autorizados, fortalecendo a segurança.'
+---
+
+
+Visando aprimorar a segurança das informações da sua loja, a VTEX implementou novas configurações no Checkout, melhorando as defesas contra possíveis ataques de softwares que simulam o comportamento humano (bots).
+
+## O que mudou?
+
+Agora, as seguintes configurações estão disponíveis:
+
+- [Exigir login ao fechar uma compra](#exigir-login-ao-fechar-uma-compra)
+- [Tempo mínimo entre pedidos](#tempo-mínimo-entre-pedidos)
+- [Tempo mínimo de existência de um carrinho para permitir uso de um novo cartão de crédito](#tempo-mínimo-de-existência-de-um-carrinho-para-permitir-uso-de-um-novo-cartão-de-crédito)
+
+### Exigir login ao fechar uma compra
+
+Por meio do campo `requiresLoginToPlaceOrder`, possibilitamos que compras sejam efetuadas apenas por clientes que tenham passado pelo processo de autenticação.
+É exigido que o cliente esteja logado, usando o mesmo endereço de email fornecido no momento em que os produtos foram adicionados ao carrinho de compras.
+Quando você optar por ativar este campo, a opção de finalização de compra sem login, conhecida como [SmartCheckout](https://help.vtex.com/pt/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB) permanece desabilitada para todos os clientes da loja.
+
+### Tempo mínimo entre pedidos
+
+Por meio do campo `minimumPurchaseDowntimeSeconds`, é possível definir um tempo mínimo para que um comprador deva aguardar antes de efetuar outra compra.
+Essa configuração diminui a probabilidade da criação de várias contas em sequência para realizar uma compra.
+
+### Tempo mínimo de existência de um carrinho para permitir uso de um novo cartão de crédito
+
+Por meio do campo `cartAgeToUseNewCardSeconds`, é estabelecido um intervalo de tempo mínimo no qual um carrinho de compras deve permanecer ativo antes que um novo cartão de crédito possa ser autorizado para uso nele.
+Essa configuração diminui a probabilidade da criação de múltiplos carrinhos e a adição de novos cartões de crédito.
+A ativação deste campo não influencia compras realizadas com cartões já previamente salvos na conta do cliente.
+
+## Por que fizemos essa mudança?
+
+Criamos as novas configurações para melhorar o nível de segurança contra tentativas de fraudes e pedidos não autorizados, fortalecendo a segurança dos lojistas e aumentando a proteção das contas dos clientes.
+
+## O que precisa ser feito?
+
+As novas configurações estão disponíveis no endpoint [Update an account's orderForm configuration](https://developers.vtex.com/docs/guides/update-an-account-orderform-configuration). Para mais informações sobre como ativar os campos de cada configuração, acesse [New Checkout Settings for Bot Attack Protection](https://developers.vtex.com/updates/release-notes/2023-09-12-new-checkout-settings-for-bot-attack-protection).
diff --git a/docs/announcements/pt/new-documentation-explore-the-technical-aspects-of-the-platform.md b/docs/announcements/pt/new-documentation-explore-the-technical-aspects-of-the-platform.md
new file mode 100644
index 000000000..a5af6a945
--- /dev/null
+++ b/docs/announcements/pt/new-documentation-explore-the-technical-aspects-of-the-platform.md
@@ -0,0 +1,40 @@
+---
+title: 'Nova documentação: explore os aspectos técnicos da plataforma'
+id: 6cMtwOjX7hawCKAE1XZeWt
+status: PUBLISHED
+createdAt: 2024-06-03T18:05:03.937Z
+updatedAt: 2024-06-05T17:29:34.519Z
+publishedAt: 2024-06-05T17:29:34.519Z
+contentType: updates
+productTeam: VTEX IO
+author: YRJ73j8mt38D5TUleocQB
+slug: nova-documentacao-explore-os-aspectos-tecnicos-da-plataforma
+locale: pt
+legacySlug: nova-documentacao-explore-os-aspectos-tecnicos-da-plataforma
+announcementImageID: ''
+announcementSynopsisPT: 'Entenda como nossas decisões de engenharia podem alavancar seu negócio com a documentação VTEX Platform Overview.'
+---
+
+Pensando em facilitar o acesso às informações técnicas sobre a nossa plataforma, disponibilizamos o VTEX Platform Overview, uma nova documentação que apresenta as principais características da VTEX em um único lugar, de forma clara e objetiva.
+
+## O que é o VTEX Platform Overview?
+
+O [**VTEX Platform Overview**](https://developers.vtex.com/docs/guides/vtex-platform-overview) é um novo conjunto de artigos que oferece uma visão abrangente da nossa plataforma, enfatizando os aspectos técnicos essenciais para capacitar sua equipe e maximizar o potencial do seu negócio. O conteúdo está disponível em inglês, no Developer Portal.
+
+Confira a seguir uma introdução do que você encontrará em cada artigo:
+
+- [**Cloud infrastructure** ](https://developers.vtex.com/docs/guides/cloud-infrastructure): entenda como a nossa infraestrutura multi-tenant e arquitetura baseada em nuvem garante a escalabilidade, confiabilidade e performance do seu negócio.
+
+- [**Security**](https://developers.vtex.com/docs/guides/security): aprenda como a VTEX gerencia autenticação, controles de acesso, proteção contra ataques, resposta a incidentes, entre outras medidas e boas práticas para proteger sua loja.
+
+- [**Data privacy**](https://developers.vtex.com/docs/guides/data-privacy): entenda como garantimos a conformidade com as regulamentações de privacidade de dados e como os recursos da nossa plataforma podem ajudar lojistas e desenvolvedores a proteger os dados pessoais dos compradores.
+
+- [**Composability**](https://developers.vtex.com/docs/guides/composability): conheça como o modelo *composable commerce* da nossa plataforma permite que você crie soluções personalizadas para as necessidades do seu negócio, maximizando eficiência e escalabilidade. 
+
+- [**Store Architecture**](https://developers.vtex.com/docs/guides/store-architecture): explore os modelos de arquitetura das lojas VTEX, que são adaptados para atender diversos modelos de negócios.
+
+- [**Developer experience**](https://developers.vtex.com/docs/guides/developer-experience): conheça as principais ferramentas que oferecemos para aprimorar a experiência dos desenvolvedores, aplicáveis tanto na construção e implementação de apps com o [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io), quanto nas nossas soluções para [storefront](https://developers.vtex.com/docs/guides/getting-started-with-storefront-solutions).
+
+## Por que criamos este material?
+
+Este material foi desenvolvido para facilitar o acesso às informações técnicas da plataforma, promovendo confiança, autonomia e agilidade nos processos que envolvem esses temas.
diff --git a/docs/announcements/pt/new-feature-product-feedback-in-the-vtex-admin.md b/docs/announcements/pt/new-feature-product-feedback-in-the-vtex-admin.md
new file mode 100644
index 000000000..446fe1224
--- /dev/null
+++ b/docs/announcements/pt/new-feature-product-feedback-in-the-vtex-admin.md
@@ -0,0 +1,25 @@
+---
+title: 'Nova funcionalidade: feedback do produto no Admin VTEX'
+id: 4uZsA31friMnSs4kkVMC0w
+status: PUBLISHED
+createdAt: 2024-07-01T11:15:19.350Z
+updatedAt: 2024-07-01T16:01:07.956Z
+publishedAt: 2024-07-01T16:01:07.956Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: nova-funcionalidade-feedback-do-produto-no-admin-vtex
+locale: pt
+legacySlug: nova-funcionalidade-feedback-do-produto-no-admin-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Nova funcionalidade "Feedback do Produto" no Admin VTEX permite que você compartilhe seu feedback com nossa equipe.'
+---
+
+Estamos lançando uma nova funcionalidade no Admin VTEX: o botão Feedback do Produto. 
+Por meio deste botão que pode ser acessado na barra superior da página, após clicar no botão Central de Informações, é possível compartilhar a sua experiência em nossa plataforma.
+
+## Por que fizemos essa mudança?
+O botão Enviar feedback permite que a equipe de desenvolvimento da VTEX receba as informações de modo mais eficiente, melhorando a comunicação com os nossos usuários, e permitindo que nossos produtos e serviços sejam aprimorados para atender as necessidades dos nossos clientes.
+
+## O que precisa ser feito?
+Nenhuma ação é necessária. A funcionalidade já está disponível automaticamente em todas as lojas. Para mais informações acesse [Admin VTEX: Comece Aqui](https://help.vtex.com/pt/tutorial/admin-vtex-comece-aqui--531cHtUCUi3puRXNDmKziw).
diff --git a/docs/announcements/pt/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md b/docs/announcements/pt/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
new file mode 100644
index 000000000..a69adfc35
--- /dev/null
+++ b/docs/announcements/pt/new-features-for-vtex-sales-app-custom-displays-by-store-and-collection.md
@@ -0,0 +1,26 @@
+---
+title: 'Novas funcionalidades do VTEX Sales App: vitrine por loja e coleção'
+id: 2J9rtMQDyY6OdWDdyYWJ3X
+status: PUBLISHED
+createdAt: 2024-06-27T12:29:38.823Z
+updatedAt: 2024-06-28T12:58:10.676Z
+publishedAt: 2024-06-28T12:58:10.676Z
+contentType: updates
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: novas-funcionalidades-do-vtex-sales-app-vitrine-por-loja-e-colecao
+locale: pt
+legacySlug: novas-funcionalidades-do-vtex-sales-app-vitrine-por-loja-e-colecao
+announcementImageID: ''
+announcementSynopsisPT: 'Novas funcionalidades VTEX: vitrine por loja e vitrine de coleção para melhorar a exibição de produtos.'
+---
+
+Estamos disponibilizando duas novas funcionalidades para o VTEX Sales App: vitrines por loja e coleções. Essas funcionalidades foram desenvolvidas para melhorar a exibição de produtos e a experiência de compra dos clientes da seguinte forma:
+- **Vitrine por loja:** os lojistas podem adicionar uma página de produtos em destaque especificando o ID da loja no [Master Data](https://developers.vtex.com/docs/guides/master-data-introduction) ao qual o anúncio será vinculado, o que permite criar vitrines personalizadas para cada loja.
+- **Vitrine de coleção:** permite controlar uma seção da vitrine por meio de uma [coleção do catálogo](https://help.vtex.com/pt/tutorial/criando-colecao-de-produtos--tutorials_244). O lojista pode definir o nome da vitrine e o identificador da coleção, facilitando a organização dos produtos e destacando as coleções para os clientes.
+
+## Por que fizemos essa mudança?
+Desenvolvemos essas funcionalidades para que os lojistas possam criar anúncios e organizar vitrines com coleções de produtos de forma eficiente.
+
+## O que precisa ser feito?
+Nenhuma ação é necessária, a funcionalidade será aplicada automaticamente em todas as lojas que utilizam o VTEX Sales App. Para mais informações, acesse [Anúncios do VTEX Sales App](https://help.vtex.com/pt/tutorial/anuncios-do-vtex-sales-app--3UtOFwbwD4muz3p72RBPmC#create-an-ad-page). 
diff --git a/docs/announcements/pt/new-google-and-yahoo-requirements-for-bulk-email-senders.md b/docs/announcements/pt/new-google-and-yahoo-requirements-for-bulk-email-senders.md
new file mode 100644
index 000000000..c52500bd0
--- /dev/null
+++ b/docs/announcements/pt/new-google-and-yahoo-requirements-for-bulk-email-senders.md
@@ -0,0 +1,74 @@
+---
+title: 'Novos requisitos do Google e Yahoo para remetentes de emails em massa'
+id: 4Tb5eIYJVnKHAK2hPHY1uZ
+status: PUBLISHED
+createdAt: 2024-01-25T21:37:28.950Z
+updatedAt: 2024-01-26T00:23:10.235Z
+publishedAt: 2024-01-26T00:23:10.235Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: novos-requisitos-do-google-e-yahoo-para-remetentes-de-emails-em-massa
+locale: pt
+legacySlug: novos-requisitos-do-google-e-yahoo-para-remetentes-de-emails-em-massa
+announcementImageID: ''
+announcementSynopsisPT: 'Novas exigências do Google e do Yahoo para os remetentes de emails em massa.'
+---
+
+O Google e o Yahoo estão implementando novas exigências para os remetentes de emails em massa. O objetivo é garantir mais segurança aos destinatários, diminuir o volume de spam e oferecer melhor experiência para os usuários.
+
+A partir de fevereiro de 2024, conforme suas [diretrizes para remetentes de emails](https://support.google.com/mail/answer/81126?hl=pt-BR&sjid=15077216349840152409-SA), o Google vai exigir novos requisitos para os remetentes que enviam 5 mil ou mais mensagens por dia para as contas do Gmail. De forma similar, o Yahoo também definiu novas [práticas na entregabilidade massiva de emails](https://senders.yahooinc.com/best-practices/). Os requisitos exigidos pelas empresas são:
+
+* Autenticação do email do remetente.
+* Fácil cancelamento de inscrição pelos destinatários.
+* Limite para a taxa de emails marcados como spam.
+
+Caso essas diretrizes não sejam seguidas pelos remetentes, os emails enviados poderão ser rejeitados ou entregues na caixa de spam dos destinatários.
+
+## O que mudou?
+
+A partir de fevereiro de 2024, o Google e o Yahoo vão exigir dos remetentes de emails massivos os seguintes requisitos:
+
+| **Requisitos** | **Descrição** |
+| :---: | :--- |
+| Autenticação de email do remetente | <p>Os remetentes devem autenticar a origem do seu email usando os seguintes protocolos:</p><p><ul><li><a href="https://support.google.com/a/answer/33786?sjid=4150033421619503412-SA">SPF</a> (<i>Sender Policy Framework</i>)</li><li><a href="https://support.google.com/a/answer/174124?sjid=4150033421619503412-SA">DKIM</a> (<i>DomainKeys Identified Mail</i>)</li><li><a href="https://support.google.com/a/answer/2466580?sjid=4150033421619503412-SA">DMARC</a> (<i>Domain-based Message Authentication, Reporting & Conformance</i>)</li></ul></p><p>Ao realizar essas configurações, você se protege contra <i>spoofing</i> (mensagens falsas enviadas em nome do seu domínio) e evita que as suas mensagens enviadas sejam marcadas como spam.</p><p>Saiba mais em <a href="https://support.google.com/a/answer/10583557">Evitar spam, spoofing e phishing com a autenticação do Gmail</a>.</p> |
+| Fácil cancelamento de inscrição | Os destinatários devem ser capazes de cancelar a inscrição de um email com um único clique, e o processamento da solicitação de cancelamento deve ocorrer em até dois dias.<p>Saiba mais em <a href="https://support.google.com/mail/answer/81126#subscriptions">Inscrições</a> (Google) e <a href="https://blog.postmaster.yahooinc.com/post/182917670818/dont-want-to-be-marked-as-spam-support-one-click">Support one click unsubscribe</a> (Yahoo).</p> |
+| Limite para taxa de spam | Os destinatários devem considerar os emails como desejáveis, portanto a taxa de emails marcados como spam deve ser menor que 0,1% e o remetente deve evitar que ela chegue a 0,3% ou mais. Essa taxa é referente ao número de emails marcados como spam pelos destinatários, dividido pelo número total de emails recebidos.<p>É possível usar o <a href="https://support.google.com/mail/answer/14289100">Postmaster Tools</a> para rastrear dados sobre grandes volumes de emails do Gmail, e o <a href="https://senders.yahooinc.com/complaint-feedback-loop/">Complaint Feedback Loop</a> para o mesmo serviço do Yahoo.</p> |
+
+Os requisitos acima mencionados são considerados básicos na manutenção de envio de emails. Para obter mais informações sobre boas práticas na entregabilidade de emails no Google, acesse [Diretrizes para remetentes de emails](https://support.google.com/mail/answer/81126), e para conteúdo sobre o Yahoo, veja [Email deliverability best practices](https://senders.yahooinc.com/best-practices/).
+
+## O que precisa ser feito?
+
+Para ser um remetente de emails em massa que está em conformidade com as exigências do Google e Yahoo, você deve:
+
+* [Configurar a autenticação de email do remetente](#configure-a-autenticacao-de-email-do-remetente)
+* [Permitir o fácil cancelamento da inscrição](#permita-o-facil-cancelamento-da-inscricao)
+* [Controlar o limite da taxa de spam](#controle-o-limite-da-taxa-de-spam)
+
+Caso essas diretrizes não sejam seguidas, os emails enviados poderão ser rejeitados ou entregues na caixa de spam dos destinatários. É possível confirmar se você está em conformidade com os requisitos do Google, por meio do [Postmaster Tools](https://support.google.com/mail/answer/14289100).
+
+### Configure a autenticação de email do remetente
+
+* Configure a [autenticação SPF](https://support.google.com/a/answer/33786?sjid=4150033421619503412-SA) para seu domínio de envio.
+* Configure a [autenticação DKIM](https://support.google.com/a/answer/174124?sjid=4150033421619503412-SA) para seu domínio de envio.
+* Configure a [autenticação DMARC](https://support.google.com/a/topic/2759254?hl=pt-BR&ref_topic=9061731&sjid=8809025610711525699-SA) para seu domínio de envio (você pode conferir se tem um [registro válido de DMARC](https://dmarcian.com/dmarc-inspector/)).
+* Defina uma política de DMARC para o seu domínio (confira a [implementação recomendada](https://support.google.com/a/answer/10032473?hl=pt-BR&ref_topic=2759254&sjid=8809025610711525699-SA) pelo Google).
+
+### Permita o fácil cancelamento da inscrição
+
+* Garanta aos destinatários a opção de cancelar a inscrição de emails com [um único clique](https://blog.postmaster.yahooinc.com/post/182917670818/dont-want-to-be-marked-as-spam-support-one-click).
+* Inclua um link visível para o cancelamento no corpo da mensagem.
+* Processe a solicitação de cancelamento em até 2 dias.
+
+### Controle o limite da taxa de spam
+
+* Idealmente, mantenha as taxas de spam informadas abaixo de 0,1%.
+* Evite atingir uma taxa de spam de 0,3% ou mais.
+* Monitore as taxas de spam informadas no Gmail pelo [Postmaster Tools](https://gmail.com/postmaster) e no Yahoo pelo [Complaint Feedback Loop](https://senders.yahooinc.com/complaint-feedback-loop/).
+
+## Artigos relacionados
+
+| **VTEX** | **Google** | **Yahoo** |
+| :--- | :--- | :--- |
+| <p><ul><li><a href="https://help.vtex.com/pt/tutorial/best-practices-on-spf--42t0lkl2VyC6Yewc4wA6wI">Boas práticas de SPF (Sender Policy Framework)</a></li><li><a href="https://developers.vtex.com/docs/guides/setting-up-the-spf">Setting up the SPF</a></li><li><a href="https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails">Setting up DKIM for transactional emails</a></li><li><a href="https://developers.vtex.com/docs/api-reference/message-center-api#post-/api/mail-service/pvt/providers/-EmailProvider-/dkim">Generate DKIM keys</a></li></ul></p> | <p><ul><li><a href="https://support.google.com/mail/answer/81126?hl=pt-BR&sjid=15077216349840152409-SA">Diretrizes para remetentes de e-mails</a></li><li><a href="https://support.google.com/a/answer/14229414?hl=pt-BR&ref_topic=7279058&sjid=15077216349840152409-SA#zippy=%2Co-que-acontece-quando-os-remetentes-n%C3%A3o-atendem-aos-requisitos-nas-diretrizes%2Co-que-acontece-quando-a-taxa-de-spam-do-remetente-excede-o-m%C3%A1ximo-permitido-pelas-diretrizes">Perguntas frequentes sobre as diretrizes para remetentes de e-mails</a></li><li><a href="https://support.google.com/a/answer/10583557?hl=pt-BR&sjid=8809025610711525699-SA">Evitar spam, spoofing e phishing com a autenticação do Gmail</a></li><li><a href="https://support.google.com/a/answer/10583557?hl=pt-BR&sjid=8809025610711525699-SA">Anúncio do Google</a></li></ul></p> | <p><ul><li><a href="https://senders.yahooinc.com/best-practices/">Best practices- Deliverability</a></li><li><a href="https://senders.yahooinc.com/faqs/">FAQs - Deliverability</a></li><li><a href="https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-less-spam">Anúncio do Yahoo</a></li></ul></p> |
+
diff --git a/docs/announcements/pt/new-indexation-history-screen.md b/docs/announcements/pt/new-indexation-history-screen.md
index 3a6c4453b..c0620e6bd 100644
--- a/docs/announcements/pt/new-indexation-history-screen.md
+++ b/docs/announcements/pt/new-indexation-history-screen.md
@@ -19,7 +19,7 @@ Em toda operação de ecommerce, é necessário cadastrar ou alterar informaçõ
 
 Para aprimorar a experiência de monitoramento da indexação do seu Catálogo, redesenhamos a página de **Histórico da Indexação** no Admin VTEX. A nova interface permite acompanhar o tempo de indexação dos seus produtos e o status de indexação da sua loja.
 
-![Histórico da Indexação 1 - PT](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/new-orders-module-interface-official.md b/docs/announcements/pt/new-orders-module-interface-official.md
index b9478018e..f27957414 100644
--- a/docs/announcements/pt/new-orders-module-interface-official.md
+++ b/docs/announcements/pt/new-orders-module-interface-official.md
@@ -27,15 +27,15 @@ Em relação à versão beta, a interface que será oficial a partir de 1 de fev
 
 * **Busca de pedidos sem limite de data:** possibilidade de buscar pedidos sem definir um limite de data, o que retorna todos os pedidos relacionados ao critério utilizado, independente da data de criação do pedido. Essa busca não pode ser associada a outros filtros. No entanto, você pode selecionar um período de busca personalizado de até seis meses e então combiná-lo com os filtros. Saiba mais no artigo [Filtrar pedidos em Todos os pedidos](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192).
 
-  ![busca_sem_limite_data_all_pt](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
+  ![busca_sem_limite_data_all_pt](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
 
 * **Diagrama do pedido:** na seção _Status do pedido_ da nova interface, por padrão, o que é exibido é uma linha tempo com os eventos do pedido. Agora você pode também ver o _Diagrama do pedido_. Ao clicar em `Ver diagrama`, um modal é aberto e apresenta uma imagem como a seguinte:
 
-  ![diagrama_pedido_pt](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
+  ![diagrama_pedido_pt](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
 
 Para quem ainda não usava a versão beta, a imagem abaixo é um mapeamento da correspondência de campos entre a versão antiga da página **Detalhes do pedido** e a versão oficial:
 
-![board_comparativo_interface_pedido_v2_pt](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
+![board_comparativo_interface_pedido_v2_pt](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/new-payment-features-enhancements-for-an-improved-shopping-experience.md b/docs/announcements/pt/new-payment-features-enhancements-for-an-improved-shopping-experience.md
index 471ac1cd5..837e7056c 100644
--- a/docs/announcements/pt/new-payment-features-enhancements-for-an-improved-shopping-experience.md
+++ b/docs/announcements/pt/new-payment-features-enhancements-for-an-improved-shopping-experience.md
@@ -3,8 +3,8 @@ title: 'Novas funcionalidades de Pagamentos: melhorias para uma experiência de
 id: 3b5C6DabaGrWsS9Jahs75D
 status: PUBLISHED
 createdAt: 2023-05-29T14:05:55.900Z
-updatedAt: 2023-05-29T14:10:59.814Z
-publishedAt: 2023-05-29T14:10:59.814Z
+updatedAt: 2024-04-04T19:35:42.974Z
+publishedAt: 2024-04-04T19:35:42.974Z
 contentType: updates
 productTeam: Shopping
 author: 2o8pvz6z9hvxvhSoKAiZzg
@@ -26,5 +26,5 @@ Com o objetivo de aprimorar a experiência de compra dos clientes, apresentamos
 
 ## O que precisa ser feito?
 
-Nenhuma ação é necessária para, já que as atualizações serão aplicadas automaticamente em todas as lojas VTEX. 
+Nenhuma ação é necessária, já que as atualizações serão aplicadas automaticamente em todas as lojas VTEX. 
 
diff --git a/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
new file mode 100644
index 000000000..d25716190
--- /dev/null
+++ b/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
@@ -0,0 +1,36 @@
+---
+title: 'Nova interface de gerenciamento de provedores de pagamento e antifraude'
+id: Qx6SkUJqM8DwoZajvAP0k
+status: PUBLISHED
+createdAt: 2023-12-22T09:09:05.292Z
+updatedAt: 2024-01-22T20:43:27.828Z
+publishedAt: 2024-01-22T20:43:27.828Z
+contentType: updates
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: nova-interface-de-gerenciamento-de-provedores-de-pagamento-e-antifraude
+locale: pt
+legacySlug: nova-interface-de-gerenciamento-de-provedores-de-pagamento-e-antifraude
+announcementImageID: ''
+announcementSynopsisPT: 'Acesse informações sobre provedores de pagamento e antifraude de forma mais ágil'
+---
+
+A VTEX está disponibilizando uma nova interface na página de provedores de pagamento e antifraude no Admin VTEX, que oferece uma experiência mais intuitiva e eficiente para a sua operação.
+
+## O que mudou?
+
+A partir de agora você poderá acessar de forma mais rápida as informações de provedores cadastrados em sua loja. O novo layout oferece a opção de filtrar provedores de pagamento e antifraude por nome, tipo de provedor e ambiente de operação (teste ou produção).
+
+A tela que permite adicionar um novo provedor, editar configurações e realizar busca de provedores, também foi aprimorada para permitir uma melhor experiência de navegação.
+
+![nova_interface_provedores_admin](//images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/339b129737e2bbf0167d892a50de7f8e/nova_interface_provedores_admin.JPG)
+
+## O que precisa ser feito?
+
+A nova página de gerenciamento de provedores de pagamento e antifraude já está disponível de forma automática para todas as contas VTEX. Para utilizar a nova experiência no Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__.
+
+Para mais detalhes sobre as funcionalidades da nova interface, acesse [Cadastrar provedores de pagamento e antifraude](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
+
+<div class = "alert alert-warning">
+  A versão anterior da interface de gerenciamento de afiliações, disponível em <b>Configurações da loja > Pagamentos > Configurações > Afiliações de gateways</b>, ainda poderá ser acessada até 14 de janeiro de 2024.
+</div>
diff --git a/docs/announcements/pt/new-permission-required-to-manage-redirects-in-store-framework-cms.md b/docs/announcements/pt/new-permission-required-to-manage-redirects-in-store-framework-cms.md
new file mode 100644
index 000000000..e867cd2e8
--- /dev/null
+++ b/docs/announcements/pt/new-permission-required-to-manage-redirects-in-store-framework-cms.md
@@ -0,0 +1,34 @@
+---
+title: 'Store Framework CMS: Nova permissão necessária para gerenciar redirecionamentos'
+id: 1GcT48ML2w6TZQxQyGbD6W
+status: PUBLISHED
+createdAt: 2023-08-31T18:10:04.246Z
+updatedAt: 2023-09-05T16:32:32.516Z
+publishedAt: 2023-09-05T16:32:32.516Z
+contentType: updates
+productTeam: VTEX IO
+author: 4ubliktPJIsvyl1hq91RdK
+slug: store-framework-cms-nova-permissao-para-gerenciar-redirecionamentos
+locale: pt
+legacySlug: store-framework-cms-nova-permissao-para-gerenciar-redirecionamentos
+announcementImageID: ''
+announcementSynopsisPT: 'Fazer redirecionamentos no Store Framework CMS exige acesso ao recurso “CMS Settings”.'
+---
+
+**Redirecionamentos** é uma funcionalidade do Store Framework CMS que faz com que um usuário da loja, ao entrar em uma página específica, seja redirecionado a outra página automaticamente, seja ela interna ou externa à loja. Por motivos de segurança, estamos exigindo que usuários do Admin possuam uma permissão específica para fazer redirecionamentos.
+
+## O que mudou?
+
+Para que usuários do Admin possam criar, editar e apagar redirecionamentos no CMS, agora é necessário possuir um perfil de acesso com o [recurso do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) **CMS Settings**.
+
+## Por que fizemos essa mudança?
+
+Adicionamos esse requisito de permissão por motivos de segurança. Dessa forma, apenas usuários do Admin que foram explicitamente autorizados terão acesso à funcionalidade **Redirecionamentos**. Isso impede que usuários não autorizados possam criar, editar e apagar redirecionamentos de forma indesejada.
+
+## O que precisa ser feito?
+
+Para que um usuário existente do Admin possa gerenciar redirecionamentos no Store Framework CMS, é necessário atribuir ao usuário um perfil de acesso que inclua o recurso **CMS Settings**. Verifique as instruções para editar os perfis de acesso de um usuário no artigo [Gerenciando Usuários](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512#editar-usuarios).
+
+Caso você queira utilizar um perfil de acesso personalizado, você pode criar um novo perfil de acesso ou editar um já existente para incluir o recurso **CMS Settings**. Verifique as instruções para criar e editar perfis de acesso no artigo [Perfis de Acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso).
+
+Mais informações sobre redirecionamentos podem ser vistas no artigo [Gerenciando redirecionamentos de URL](https://help.vtex.com/pt/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV).
diff --git a/docs/announcements/pt/new-process-for-security-testing.md b/docs/announcements/pt/new-process-for-security-testing.md
new file mode 100644
index 000000000..b95f3ed6c
--- /dev/null
+++ b/docs/announcements/pt/new-process-for-security-testing.md
@@ -0,0 +1,34 @@
+---
+title: 'Novo processo para testes de segurança'
+id: 7z6kjzqf2yZyRuwIXOfY3o
+status: PUBLISHED
+createdAt: 2023-09-05T13:50:09.793Z
+updatedAt: 2023-09-05T13:57:39.737Z
+publishedAt: 2023-09-05T13:57:39.737Z
+contentType: updates
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: novo-processo-para-testes-de-seguranca
+locale: pt
+legacySlug: novo-processo-para-testes-de-seguranca
+announcementImageID: ''
+announcementSynopsisPT: 'Atualizamos o procedimento para realizar testes de penetração com o objetivo de torná-lo ainda mais seguro.'
+---
+
+A VTEX realiza verificações periódicas de vulnerabilidade por meio de varreduras recorrentes e testes de penetração (_pen tests_). Essas práticas nos permitem avaliar o nível de maturidade de segurança da nossa plataforma.
+
+Se necessário, você pode realizar um teste de penetração por conta própria – desde que autorizado pela VTEX – e reportar alguma vulnerabilidade encontrada. Para isso, a equipe de Segurança da VTEX atualizou o procedimento a ser seguido por lojistas que desejam realizar um teste de penetração em seu ambiente.
+
+## O que mudou?
+
+De maneira resumida, o novo processo para realizar testes de penetração consiste em:
+
+1. Solicitar o agendamento de um teste pelo [Suporte](https://help.vtex.com/pt/support) da VTEX.
+2. Revisar e assinar o [acordo de confidencialidade](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip) antes de executar qualquer teste.
+3. Após a conclusão do teste, compartilhar os resultados com a equipe de segurança da VTEX.
+
+Confira informações detalhadas sobre esse procedimento no guia [Testes de penetração e avisos de vulnerabilidade](https://help.vtex.com/pt/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb).
+
+## Por que fizemos essa mudança?
+
+Atualizamos o procedimento de testes de penetração para garantir a segurança da plataforma e a realização de verificações de forma segura, impedindo [procedimentos não permitidos](https://help.vtex.com/pt/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb#procedimentos-nao-permitidos) e ações que possam prejudicar nossos clientes.
diff --git a/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md b/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md
index a88022e79..44d014e7c 100644
--- a/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md
+++ b/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md
@@ -30,7 +30,7 @@ Desenvolvemos uma nova interface para a Lista de Promoções, que permite:
 * Exportar sua lista de promoções ativas.
 * Duplicar promoções ativas ou arquivadas para um processo de criação mais rápido.
 
-![geral-promo-PT](https://images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/76708dc950cfef626516c9a08b6fe13d/image3.png)
+![geral-promo-PT](//images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/76708dc950cfef626516c9a08b6fe13d/image3.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/new-roles-page.md b/docs/announcements/pt/new-roles-page.md
new file mode 100644
index 000000000..a0931c686
--- /dev/null
+++ b/docs/announcements/pt/new-roles-page.md
@@ -0,0 +1,35 @@
+---
+title: 'Nova página de Perfis de acesso'
+id: 6kAbgyB0Ah8WK4ZAj7aSSL
+status: DRAFT
+createdAt: 2023-11-30T16:11:56.563Z
+updatedAt: 2023-11-30T16:25:18.794Z
+publishedAt: 
+contentType: updates
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: nova-pagina-de-perfis-de-acesso
+locale: pt
+legacySlug: nova-pagina-de-perfis-de-acesso
+announcementImageID: ''
+announcementSynopsisPT: 'Redesenhamos a página de perfis de acesso para exibir informações mais completas e organizadas.'
+---
+
+Diversos colaboradores acessam o ambiente administrativo de cada conta. Logo, é essencial limitar o acesso a ações críticas para garantir que cada usuário tenha acesso apenas às ações necessárias para o seu papel.
+
+Nesse contexto, a funcionalidade de perfis de acesso serve para atribuir um conjunto de [recursos](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) a  usuários administrativos, concedendo as permissões necessárias para as atividades na loja.
+
+Reformulamos a página de **Perfis de acesso** com o objetivo de otimizar o gerenciamento de permissões de usuários. Para acessá-la, na barra superior do Admin VTEX, clique no avatar do seu perfil, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Perfis de acesso**.
+
+## O que mudou?
+
+Além de todas as funcionalidades da versão anterior, a nova página de **Perfis de acesso** permite:
+
+* Acessar a listagem completa dos perfis de acesso cadastrados na sua loja com um design mais moderno e intuitivo, atualizado para o [Novo Admin VTEX](https://help.vtex.com/pt/tutorial/admin-vtex-comece-aqui--531cHtUCUi3puRXNDmKziw).
+* Visualizar informações úteis para o gerenciamento de perfis de acesso diretamente na listagem, como a quantidade de usuários associados a cada perfil, o tipo de perfil (predefinido ou personalizado) e a data de criação do perfil.
+
+![roles-pt](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/943f5df380f3fb685bb369014b435454/roles-pt.png)
+
+## O que precisa ser feito?
+
+A atualização será aplicada de forma automática em todas as lojas. Confira mais detalhes sobre como utilizar a página otimizada no artigo [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/announcements/pt/new-rules-for-activating-vtex-support.md b/docs/announcements/pt/new-rules-for-activating-vtex-support.md
new file mode 100644
index 000000000..14c1d5b9b
--- /dev/null
+++ b/docs/announcements/pt/new-rules-for-activating-vtex-support.md
@@ -0,0 +1,30 @@
+---
+title: 'Novas regras para acionar o Suporte VTEX'
+id: 18xfVJM9tbzpyqAUzIsBC1
+status: PUBLISHED
+createdAt: 2023-12-01T17:11:24.955Z
+updatedAt: 2023-12-13T14:03:46.024Z
+publishedAt: 2023-12-13T14:03:46.024Z
+contentType: updates
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: novas-regras-para-acionar-o-suporte-vtex
+locale: pt
+legacySlug: novas-regras-para-acionar-o-suporte-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Para contas no Brasil, agora é essencial ter o recurso Open Support Ticket no perfil de acesso para usar o suporte VTEX.'
+---
+
+Para contas no Brasil, agora é obrigatório ter o recurso **Open Support Ticket** do produto **VTEX - Support** autorizado em seu perfil de acesso para acionar o suporte VTEX. Um usuário com perfil de acesso *User Administrator - Restricted* precisará configurar essa autorização no [License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete).
+
+<div class="alert alert-info"> Usuários administrativos vinculados ao perfil de acesso <strong>Owner (Admin Super)</strong>  possuem o recurso <em>Open Support Ticket</em>  vinculado automaticamente.</div>
+
+## O que mudou?
+A configuração é válida somente para contas no Brasil e restringe a abertura de tickets de suporte a usuários autorizados. Para realizar a abertura de solicitação ao time de suporte, o usuário precisará ter o recurso *Open Support Ticket* do produto **VTEX - Support** autorizado em seu [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc). 
+
+## Por que fizemos essa mudança?
+No contexto das boas práticas de segurança, esta etapa visa fortalecer a proteção da privacidade das informações sensíveis armazenadas na loja.
+
+## O que precisa ser feito?
+Um usuário com o perfil de acesso *User Administrator - Restricted* precisa vincular o recurso **Open Support Ticket** do produto **VTEX - Support** no [License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) aos [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) correspondentes aos usuários que devem ter esse acesso à abertura de tickets de suporte. 
+
diff --git a/docs/announcements/pt/new-sales-app-performance-monitor.md b/docs/announcements/pt/new-sales-app-performance-monitor.md
new file mode 100644
index 000000000..ddaa23888
--- /dev/null
+++ b/docs/announcements/pt/new-sales-app-performance-monitor.md
@@ -0,0 +1,32 @@
+---
+title: 'Novo Performance Monitor do Sales App'
+id: 1xi0UVrKl5SwQbwts907bh
+status: PUBLISHED
+createdAt: 2023-09-05T19:37:19.176Z
+updatedAt: 2023-09-06T13:06:33.383Z
+publishedAt: 2023-09-06T13:06:33.383Z
+contentType: updates
+productTeam: Shopping
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: novo-performance-monitor-do-sales-app
+locale: pt
+legacySlug: novo-performance-monitor-do-sales-app
+announcementImageID: ''
+announcementSynopsisPT: 'Performance Monitor é a funcionalidade que permite que os vendedores tenham acesso ao quanto venderam usando a solução.'
+---
+
+O [Performance Monitor](https://help.vtex.com/pt/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/5pqtuvi97FFZiGf7MlSe8q) é a nova funcionalidade do Sales App. Com ela seus vendedores sabem exatamente o quanto venderam com a solução e como estão seus principais indicadores de varejo como: Ticket Médio, Peças por Atendimento e Preço Médio por item vendido. Além disso, também é exibido para os vendedores como estão em relação a média da sua loja.
+
+Esses dados também estão disponíveis para os gestores que acessam o Portal Admin da VTEX, permitindo acompanhar de perto o desempenho de seus vendedores e lojas. 
+# O que mudou?
+Agora no menu lateral do Sales App existe a opção "Desempenho de Vendas". Nela, o vendedor pode visualizar o seu próprio desempenho de vendas e ode outros colaboradores.
+# O que precisa ser feito?
+A funcionalidade está ativada por padrão para todas as contas que utilizem o app. A única exceção são para marcas que já utilizam a solução Indeva by VTEX, neste caso será necessário acionar o suporte para ativar a funcionalidade.
+
+Para mais informações sobre o Sales App, consulte a nossa documentação:
+
+- [Sales App - Primeiros passos e configurações](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc#)
+- [Sales App - Pagamentos](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy#)
+- [Sales App - Usando o app](https://help.vtex.com/pt/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr#)
+- [Estratégias de Comércio Unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv#)
+
diff --git a/docs/announcements/pt/new-sales-performance-dashboard.md b/docs/announcements/pt/new-sales-performance-dashboard.md
index cf30a6b48..0f57f6135 100644
--- a/docs/announcements/pt/new-sales-performance-dashboard.md
+++ b/docs/announcements/pt/new-sales-performance-dashboard.md
@@ -19,7 +19,7 @@ Com um volume cada vez maior de dados disponíveis para operações de ecommerce
 
 O dashboard permite que os usuários analisem dados de todos os canais de venda da loja, e de seus sellers, incluindo métricas sobre receita, pedidos, ticket médio e muito mais. Inclui também gráficos e tabelas para que você compare resultados de períodos diferentes, introduzindo onze opções de filtros para que obtenham insights unificados de toda a operação.
 
-![Sales Perf Dash PT](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
+![Sales Perf Dash PT](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
 
 ## O que mudou?
 Antes, o seu Admin VTEX incluía somente a página Insights para gerar inteligência de negócios a partir dos dados da sua operação. Agora incluímos uma nova página, a Performance de Vendas, para que você tenha uma visão mais detalhada dos resultados dos diferentes canais de venda da sua loja. A página de Insights ainda permanecerá em seu Admin VTEX.
diff --git a/docs/announcements/pt/new-sku-bindings-interface.md b/docs/announcements/pt/new-sku-bindings-interface.md
index de022f859..248c4b4f1 100644
--- a/docs/announcements/pt/new-sku-bindings-interface.md
+++ b/docs/announcements/pt/new-sku-bindings-interface.md
@@ -19,7 +19,7 @@ A VTEX possibilita que a sua loja atue tanto como [seller](https://help.vtex.com
 
 Para aprimorar essa experiência, redesenhamos a página de **Vínculos de SKU** no Admin VTEX. A nova interface permite acompanhar e gerenciar a relação de vínculo entre os SKUs do seller e do marketplace de forma mais simples e ágil.
 
-![sku_binding_page_PT_final](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/5b8897408601d49051d35dd5364c2a8e/sku_binding_page_PT_final.png)
+![sku_binding_page_PT_final](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/5b8897408601d49051d35dd5364c2a8e/sku_binding_page_PT_final.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/new-subscriptions-module.md b/docs/announcements/pt/new-subscriptions-module.md
index 7da275344..fe0f7196f 100644
--- a/docs/announcements/pt/new-subscriptions-module.md
+++ b/docs/announcements/pt/new-subscriptions-module.md
@@ -39,35 +39,35 @@ A melhoria do sistema de assinaturas também trouxe novas funcionalidades para o
 #### Novo detalhamento de assinaturas 
 A nossa página de detalhamento de assinatura foi remodelada pensando em melhorar a experiência do consumidor ao reduzir o tempo para localizar informações e realizar tarefas. Além disso, contamos com a nova funcionalidade de adicionar itens a uma assinatura existente.
 
-![img1 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/0578726c45d942f7960c7e3999649627/img1_subscriptions_PT.png)
+![img1 subscriptions PT](//images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/0578726c45d942f7960c7e3999649627/img1_subscriptions_PT.png)
 
 #### Barra de ações
 Adicionamos uma barra de ações para melhorar a comunicação com o usuário sobre o que precisa ser feito ou comunicar eventos importantes sobre a sua assinatura.
 
-![img2 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/77b61a6259cf558bfa78db8c5ada1f80/img2_subscriptions_PT.png)
+![img2 subscriptions PT](//images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/77b61a6259cf558bfa78db8c5ada1f80/img2_subscriptions_PT.png)
 
 #### Adicionar produto à sua assinatura
 Agora é possível adicionar um novo item à sua assinatura através da busca dos produtos disponíveis na loja. 
 
-![img3 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/64249fe1d011fc477d8760f27a783506/img3_subscriptions_PT.png)
+![img3 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/64249fe1d011fc477d8760f27a783506/img3_subscriptions_PT.png)
 
 #### Criar uma nova assinatura
 Adicionamos uma funcionalidade muito aguardada que é a tela de criação de assinaturas. Ela permite configurar uma nova assinatura sem ter que passar pelo checkout e realizar um pedido na hora. Para realizar essa ação, basta clicar no botão __Nova assinatura__, na listagem de assinaturas.
 
-![img4 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/8659bfceec1f88773e5871092be90771/img4_subscriptions_PT.png)
+![img4 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/8659bfceec1f88773e5871092be90771/img4_subscriptions_PT.png)
 
 ### Novo conceito de assinaturas para o sistema
 Até então, para o sistema da VTEX, uma assinatura era composta por um SKU, atrelado a uma configuração de compra. Isso permitia que o consumidor da loja assinasse SKUs com endereços de entrega e até mesmo formas de pagamento diferentes – uma evolução em comparação à primeira versão do sistema. 
 
 #### Antes:
-![img5 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/4d469f2404f59d76b5ebe67b89e36365/img5_subscriptions_PT.png)
-![img6 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/eb2c0c259c6ffba5c7bd4e7ac0cda841/img6_subscriptions_PT.png)
-![img7 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/cab5768ff5bad6dab10ca2cd5e931c8f/img7_subscriptions_PT.png)
+![img5 subscriptions PT](//images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/4d469f2404f59d76b5ebe67b89e36365/img5_subscriptions_PT.png)
+![img6 subscriptions PT](//images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/eb2c0c259c6ffba5c7bd4e7ac0cda841/img6_subscriptions_PT.png)
+![img7 subscriptions PT](//images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/cab5768ff5bad6dab10ca2cd5e931c8f/img7_subscriptions_PT.png)
 
 A assinatura para nós agora consiste em uma lista de SKUs e uma determinada configuração de compra. Isso significa que nós retiramos o conceito de Grupos de Assinatura do nosso sistema. Saiba mais no artigo [Como funciona a assinatura](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453). O diagrama abaixo demonstra o novo conceito de assinatura:
 
 #### Agora:
-![img8 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/474f3170b2f10977be30172465ffd630/img8_subscriptions_PT.png)
+![img8 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/474f3170b2f10977be30172465ffd630/img8_subscriptions_PT.png)
 
 ### Data do ciclo da assinatura
 
diff --git a/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md b/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md
index 87747e3a3..da30caf57 100644
--- a/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md
+++ b/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md
@@ -22,7 +22,7 @@ O painel de gerenciamento de usuários teve seu design atualizado com os mesmos
 - Apresentação da configuração de MFA (autenticação de múltiplos fatores) para cada usuário na lista de usuários.
 - Botão para exportar os dados da lista de usuários para um arquivo csv que inclui id, email e nome.
 
-![Lista Usuários User Management PT](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
+![Lista Usuários User Management PT](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
 
 Além disso, o painel sofreu algumas alterações:
 
diff --git a/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md b/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md
index 4352721cf..56d062234 100644
--- a/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md
+++ b/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md
@@ -18,7 +18,7 @@ announcementSynopsisPT: 'Atualizamos o layout do e-mail recebido ao solicitar o
 Atualizamos o layout do e-mail recebido ao solicitar o código de acesso para seu admin. 
 Agora, todas as vezes que o código de acesso for requisitado para logar ou alterar a senha, você receberá um e-mail como este abaixo:  
 
-![announcement-novo-layout-email-codigo-acesso PT](https://images.ctfassets.net/alneenqid6w5/cQVFNnznSclT585LRuACz/06a49b0a9837c3d5a64503f982a354d1/announcement-novo-layout-email-codigo-acesso.png)
+![announcement-novo-layout-email-codigo-acesso PT](//images.ctfassets.net/alneenqid6w5/cQVFNnznSclT585LRuACz/06a49b0a9837c3d5a64503f982a354d1/announcement-novo-layout-email-codigo-acesso.png)
 
 ## O que muda  
 A nova versão proporciona mais usabilidade e fluidez ao layout e está mais coerente com a identidade visual da VTEX. Além disso, o código recebeu mais destaque no corpo do e-mail, privilegiando a informação. Outro ponto favorável são as versões disponíveis para cada idioma.  
diff --git a/docs/announcements/pt/offer-add-on-services-to-products-sold-in-vtex-sales-app.md b/docs/announcements/pt/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
new file mode 100644
index 000000000..bfa4a4fd7
--- /dev/null
+++ b/docs/announcements/pt/offer-add-on-services-to-products-sold-in-vtex-sales-app.md
@@ -0,0 +1,29 @@
+---
+title: 'Ofereça serviços adicionais aos produtos vendidos no VTEX Sales App'
+id: 2kF3T4fCxoNKEKslXezTHL
+status: PUBLISHED
+createdAt: 2024-04-30T13:52:00.217Z
+updatedAt: 2024-04-30T17:15:44.935Z
+publishedAt: 2024-04-30T17:15:44.935Z
+contentType: updates
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: ofereca-servicos-adicionais-aos-produtos-vendidos-no-vtex-sales-app
+locale: pt
+legacySlug: ofereca-servicos-adicionais-aos-produtos-vendidos-no-vtex-sales-app
+announcementImageID: ''
+announcementSynopsisPT: 'Assembly Options no VTEX Sales App: serviços adicionais a produtos vendidos e montagem de itens com SKUs diversos.'
+---
+
+Desenvolvemos uma nova funcionalidade para o [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p), que permite a integração entre os canais de vendas online e físicos, por meio dele os vendedores das lojas físicas podem oferecer atendimento personalizado aos clientes.
+
+## O que mudou?
+Agora, com a funcionalidade Assembly Options, os vendedores têm a possibilidade de oferecer serviços adicionais aos produtos vendidos, como garantia estendida e seguro. Além disso, a funcionalidade permite a montagem de itens compostos por diversos SKUs, por exemplo, uma cesta de natal ou café da manhã, kits de maquiagem, entre outros.
+
+## Por que fizemos essa mudança?
+Desenvolvemos essa funcionalidade para permitir que os vendedores ofereçam opções de customizações de produtos por meio do VTEX Sales App.
+
+## O que precisa ser feito?
+Nenhuma ação é necessária. A funcionalidade já está disponível no VTEX Sales App.
+Para mais detalhes sobre o uso dessa funcionalidade, acesse o artigo [Assembly Options no VTEX Sales App](https://help.vtex.com/pt/tutorial/assembly-options-no-vtex-sales-app--4fTfqOMcXyhAhWXkl935lr).
+
diff --git a/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md b/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md
index 6804e0d0e..20da4f1f5 100644
--- a/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md
+++ b/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md
@@ -23,7 +23,7 @@ A funcionalidade de pontos de retirada para assinaturas está disponível em ver
 
 Antes, as assinaturas não tinham pontos de retirada como uma das opções de entrega. Com a nova funcionalidade, o cliente final pode escolher pontos de retirada para itens de um pedido de assinatura no momento do checkout, conforme ilustrado na imagem abaixo.
 
-![subscriptionspickup PT](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
+![subscriptionspickup PT](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
 
 Além disso, você também pode atribuir pontos de retirada a novas assinaturas e a assinaturas já existentes por meio da [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1).
 
diff --git a/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md b/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md
new file mode 100644
index 000000000..3cf5428fd
--- /dev/null
+++ b/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md
@@ -0,0 +1,31 @@
+---
+title: 'Módulo Status dos anúncios para integrações com marketplaces VTEX'
+id: 1EeGgit1Brq3mmm8qhv2m3
+status: PUBLISHED
+createdAt: 2024-02-07T20:18:50.779Z
+updatedAt: 2024-03-04T19:21:14.936Z
+publishedAt: 2024-03-04T19:21:14.936Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: modulo-status-dos-anuncios-para-integracoes-com-marketplaces-vtex
+locale: pt
+legacySlug: modulo-status-dos-anuncios-para-integracoes-com-marketplaces-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Acompanhe seus anúncios com o novo módulo Status dos anúncios'
+---
+
+__Status dos anúncios__ é o novo módulo no Admin VTEX que permite ao seller acompanhar o envio e a sincronização dos anúncios de integrações com marketplaces VTEX de todas as regiões do mundo. Para acessar o módulo, vá em __Marketplace > Conexões > Status de anúncios,__ ou digite __Status de anúncios__ na barra de busca.
+
+![Tela Offer Status](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/e383485bcec5739e5594fb942ab529a2/-PT-_Offer_Status_-_GIF.gif)
+
+## Por que desenvolvemos essa funcionalidade?
+
+Desenvolvemos o módulo __Status dos anúncios__ visando proporcionar a visão do processo completo de envio e sincronização dos anúncios com marketplaces VTEX. Agora, é possível visualizar em abas separadas os anúncios que estão __Publicados,__ saber os __Problemas__ que impediram um anúncio de ser publicado e acompanhar os anúncios que estão __Aguardando conclusão__ por parte de cada marketplace que o seller está conectado. 
+
+Para conhecer detalhadamente cada aba do módulo e saber como utilizá-las, leia o tutorial [Status dos anúncios](https://help.vtex.com/pt/tutorial/status-de-anuncios-beta--2OE87wU26F7lApl99OdwvJ).
+
+## O que precisa ser feito?
+
+Nenhuma alteração é necessária para a utilização do módulo __Status dos anúncios,__ ele estará disponível para todas as integrações com marketplaces VTEX a partir do dia __28 de fevereiro de 2024__.
+
diff --git a/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md b/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
index e0deeeb9e..8496a445a 100644
--- a/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
+++ b/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
@@ -35,7 +35,7 @@ A revisão e o eventual ajuste desta mudança devem ser aplicados através dos t
 
 Passos necessários para a revisão e adaptação:
 
-1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
+1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
 2. __Customização__: se a página "/account/orders" possuir alguma customização de front-end, esta deve ser migrada e adaptada para a nova URL "/account#/orders". Revise e realize todos os testes necessários garantindo funcionamento de todas as recursos personalizados;  
 3. __Links do site__: Revise e atualize todos os links customizados do site e dos e-mails transacionais que antes direcionavam o usuário para a URL "/account/orders". Estes links agora devem direcionar o usuário para "/account#/orders".
 
diff --git a/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md b/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md
new file mode 100644
index 000000000..50072af2f
--- /dev/null
+++ b/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md
@@ -0,0 +1,78 @@
+---
+title: 'Guia de onboarding: sua jornada completa na VTEX'
+id: 510SdtVmDcuIQAGoAl0sgf
+status: PUBLISHED
+createdAt: 2024-02-22T20:28:44.286Z
+updatedAt: 2024-02-23T14:44:33.307Z
+publishedAt: 2024-02-23T14:44:33.307Z
+contentType: updates
+productTeam: Others
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: guia-de-onboarding-sua-jornada-completa-na-vtex
+locale: pt
+legacySlug: guia-de-onboarding-sua-jornada-completa-na-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Lançamento do Guia de onboarding: conteúdo da loja até o go-live, evolução da operação e suporte na VTEX.'
+---
+
+Com foco no sucesso dos nossos clientes, a VTEX oferece soluções completas para diversos modelos de negócio. É a versatilidade do composable commerce a serviço da inovação e do crescimento da sua operação.
+
+E para que você adote facilmente novos recursos, gerencie seu negócio com autonomia e ganhe em escalabilidade, disponibilizamos o novo Guia de onboarding, um conteúdo da jornada completa de operar uma loja VTEX. O material está disponível na seção [Comece aqui](https://help.vtex.com/pt/tracks) do Help Center.
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/359WPOFfC5pE91DpoECZJe/4ec1ed1efbb3b2bc052974136a8759ce/announcement_complete_guide_PT.png" alt="Guia de onboarding">
+</div>
+
+## O que é o Guia de onboarding?
+
+O **Guia de onboarding** é um conjunto de trilhas de documentação que incluem o planejamento de arquitetura da loja, as configurações para o go-live, os produtos para evoluir o negócio e as orientações sobre o nosso suporte. O guia apresenta configurações e recursos da plataforma contextualizados na jornada de operação da loja VTEX.
+
+O **Guia de onboarding** é composto por três trilhas, são elas:
+
+- [Trilha da loja VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9)
+- [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS)
+- [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy)
+
+<div class="alert alert-info">
+As trilhas tem conteúdos complementares, mas são independentes entre si. Isso significa que você pode explorar o conteúdo com liberdade, sem precisar seguir uma sequência.
+</div>
+
+Nosso objetivo é que clientes, parceiros e todo o ecossistema VTEX se beneficiem do **Guia de onboarding**. E para manter a relevância do material para diferentes negócios, consideramos uma jornada bastante abrangente. 
+Veja a seguir uma [introdução](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) do que você encontrará no guia.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/1N4nX2r9WxhdSCqr8zOEla/dc8a923eb652753491a1501284d17e00/announcement_headings_track_1_PT.png" height="90" alt="Trilha da loja VTEX">
+</div>
+
+A **Trilha da loja VTEX** apresenta o contexto inaugural da operação, começando pela definição de qual [tipo de conta e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) são adequados às necessidades do negócio. A partir disso, é possível realizar as [configurações iniciais](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) e as configurações dos [módulos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) da plataforma, focando em acelerar a inauguração da loja. Uma vez que as [integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) estejam concluídas e a implementação da tecnologia de [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para a construção da frente de loja tenha sido finalizada, é chegado o momento do [go-live](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) e da inauguração da nova loja.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6yRmvP19rt7z1mNE7vdWQz/4f45499ead8fd1b91442d51e9e3c50a6/announcement_headings_track_2_PT.png" height="90" alt="Proximos passos apos o go live">
+</div>
+
+A trilha **Próximos passos após o go-live** apresenta como o [comércio unificado](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/5Qvw31yH2FPDBl14K5xXHA) é realizado com os recursos da plataforma, incluindo [configurações de módulos](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) não mencionadas anteriormente, pois aqui o foco é na evolução da operação. Esta trilha apresenta também os [produtos Add on](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) da VTEX, uma série de produtos que podem ser adquiridos à parte para permitir novas estratégias e diversificação do negócio.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6N7adQ7RxTfTyuIrCDqstZ/ee6aea639c26136d7f9ff6b9e560c9cb/announcement_headings_track_3_PT.png" height="90" alt="Suporte na VTEX">
+</div>
+
+O **Suporte na VTEX** apresenta o [suporte](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) que prestamos aos clientes, o que não se restringe a uma parte específica da jornada. O [funcionamento do suporte](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) é inclusive referenciado nas outras trilhas, pois a [abertura de chamados](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE) é a via para determinadas contratações e solicitações. Esta trilha foi organizada para que os nossos clientes tenham a melhor experiência com nossos serviços e que disponham das informações necessárias à abertura de chamados, seja no contexto de suporte [técnico](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [financeiro](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) ou [comercial](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
+
+## Por que criamos este material?
+
+Pensando em promover a autonomia dos nossos clientes, organizamos o **Guia de onboarding** e vale ressaltar os seguintes aspectos:
+
+* **Jornada completa:** esta é a primeira documentação da jornada completa da operação de uma loja VTEX, sendo que o conteúdo foi planejado para acelerar o go-live e diminuir o _time-to-revenue_ do negócio.
+* **Conteúdo inédito:** além da novidade da abordagem da jornada, existem conteúdos inéditos, com destaques na _Trilha da loja VTEX_ ([Contas e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl), [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), [Implementação de frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)), na _Próximos passos após o go-live_ ([Produtos Add-on](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm)) e na _Suporte na VTEX_ como um todo.
+* **Relevância geral:** o valor deste guia não se restringe a novos clientes ou lojas em fases anteriores ao go-live, pois consideramos uma jornada suficientemente abrangente para ser relevante a diversos modelos de negócio.
+
+Desejamos que este material contribua para o sucesso do seu negócio e sua satisfação com a VTEX.
+
+|  | **Guia de onboarding** |  |
+| :---: | :---: | :---: |
+| Parte I | Parte II | Parte III |
+| [Trilha da loja VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/7bORBaAr4rIG3JgRi68jIK) | [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) |
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/4CgTVLjK3cazg4dDyVlB8m/92967dbc04e132e4901ba7080d76f2e5/announcement_under_table_image_PT.png" alt="Imagem de ecommerce">
+</div>
diff --git a/docs/announcements/pt/performance-monitor.md b/docs/announcements/pt/performance-monitor.md
new file mode 100644
index 000000000..53dccc3d4
--- /dev/null
+++ b/docs/announcements/pt/performance-monitor.md
@@ -0,0 +1,23 @@
+---
+title: 'Monitor de Performance'
+id: 5xIaEr9iAiefNiVbDHJPuK
+status: DRAFT
+createdAt: 2023-08-30T18:48:05.528Z
+updatedAt: 2023-08-30T18:50:40.345Z
+publishedAt: 
+contentType: updates
+productTeam: 
+author: 
+slug: monitor-de-performance
+locale: pt
+legacySlug: monitor-de-performance
+announcementImageID: ''
+announcementSynopsisPT: ''
+---
+
+O [Performance Monitor](https://help.vtex.com/pt/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/5pqtuvi97FFZiGf7MlSe8q) é a nova funcionalidade do Sales App. Com ela seus vendedores sabem exatamente o quanto venderam com a solução e como estão seus principais indicadores de varejo como: Ticket Médio, Peças por Atendimento e Preço Médio por item vendido. Além disso, também é exibido para os vendedores como estão em relação a média da sua loja.
+
+Esses dados também estão disponíveis para os gestores que acessam o Portal Admin da VTEX, permitindo acompanhar de perto o desempenho de seus vendedores e lojas. 
+O que mudou?
+Agora no menu lateral do Sales App existe a opção "Desempenho de Vendas". Nela, o vendedor pode visualizar o seu próprio desempenho de vendas e ode outros colaboradores.
+
diff --git a/docs/announcements/pt/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md b/docs/announcements/pt/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
index a1a3cafe1..91f29f052 100644
--- a/docs/announcements/pt/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
+++ b/docs/announcements/pt/pix-get-ready-to-offer-this-new-payment-method-on-your-e-commerce.md
@@ -3,8 +3,8 @@ title: ' Pix: prepare-se para esse novo meio de pagamento no seu e-commerce'
 id: 1v5clxhNiDST404Orzwrv6
 status: PUBLISHED
 createdAt: 2020-10-28T11:13:00.457Z
-updatedAt: 2021-03-16T14:18:44.362Z
-publishedAt: 2021-03-16T14:18:44.362Z
+updatedAt: 2024-05-03T14:59:47.895Z
+publishedAt: 2024-05-03T14:59:47.895Z
 contentType: updates
 productTeam: Financial
 author: 5kCzbURAoPwM0YJGmMCLyD
@@ -21,15 +21,15 @@ As transações com o Pix –  novo método de pagamento do Banco Central – co
 
 O Pix é o novo método de pagamento instantâneo do Banco Central (Bacen), disponível 24 horas por dia, sete dias por semana, que possibilitará a realização de transações bancárias em menos de 10 segundos. 
 
-Para conhecer as vantagens e os benefícios de aceitar o Pix como meio de pagamento no seu e-commerce, [clique aqui](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/ "clique aqui"). 
+Para conhecer as vantagens e os benefícios de aceitar o Pix como meio de pagamento no seu e-commerce, [clique aqui](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/). 
 
 ## Como parceiros podem integrar-se com a VTEX?
 
-__A partir de 19 de outubro de 2020__, parceiros poderão iniciar suas integrações via [Payment Provider Protocol](https://developers.vtex.com/vtex-developer-docs/reference/payment-provider-protocol-api-overview "Payment Provider Protocol") para oferecer o Pix como meio de pagamento para seus clientes. 
+__A partir de 19 de outubro de 2020__, parceiros poderão iniciar suas integrações via [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) para oferecer o Pix como meio de pagamento para seus clientes. 
 
 __Instituições de pagamento que já são parceiras__ VTEX podem entrar em contato com a área de Parcerias e solicitar a integração via contato direto com seu Partner Manager. Também é possível fazer esse pedido via [Suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM "Suporte").  
 
-__Instituições de pagamento que ainda não são parceiras__ VTEX devem entrar em contato via [formulário](https://vtex.com/br-pt/partner/ "registro") para iniciar a parceria.
+__Instituições de pagamento que ainda não são parceiras__ VTEX devem entrar em contato via [formulário](https://vtex.com/br-pt/partner) para iniciar a parceria.
 
 ## Como clientes VTEX podem se preparar para aceitar o Pix no seu e-commerce?
 
@@ -37,7 +37,7 @@ Existem duas opções:
 
 - Entrar em contato com a empresa que realiza o intermédio de seus pagamentos no e-commerce e solicitar que a instituição integre-se com a VTEX. 
 
-- Escolher um parceiro que já está em contato com a VTEX e realizar a negociação contratual e de configuração técnica com ele. Atualmente, os parceiros disponíveis são: [PayMee](https://www.paymee.com.br/ "PayMee"), [Spin Pay](https://spinpay.com.br/ "Spin Pay"), [IUGU](https://iugu.com/ "IUGU"), [Mercado Pago](https://www.mercadopago.com.br/), [Pagar.me](https://help.vtex.com/pt/tutorial/configurar-gateway-pagarmev2--5TugxXNMOs0Ocyg4uqussM?&utm_source=autocomplete) e Aarin.
+- Escolher um parceiro que já está em contato com a VTEX e realizar a negociação contratual e de configuração técnica com ele. Atualmente, os parceiros disponíveis são: [PayMee](https://www.paymee.com.br/), [Spin Pay](https://spinpay.com.br/ "Spin Pay"), [IUGU](https://iugu.com/ "IUGU"), [Mercado Pago](https://www.mercadopago.com.br/), [Pagar.me](https://help.vtex.com/pt/tutorial/configurar-gateway-pagarmev2--5TugxXNMOs0Ocyg4uqussM) e [Aarin](https://aarin.com.br/).
 
 ## Contate os parceiros disponíveis
 
@@ -48,6 +48,7 @@ Confira:
 - __Spin Pay__:  comercial@spinpay.com.br 
 - __IUGU__: pixvtex@iugu.com 
 - __Paymee__:  www.paymee.com.br ou comercial@paymee.com.br
-- __Mercado Pago__: www.mercadopago.com.br 
+- __Mercado Pago__: www.mercadopago.com.br
+- __Aarin__: https://aarin.com.br
 
-Acesse toda a [documentação técnica do protocolo](https://developers.vtex.com/vtex-developer-docs/reference/payment-flow#paymentmethods "documentação técnica do protocolo") e também [um guia de como realizar a integração](https://developers.vtex.com/vtex-developer-docs/docs/pix-instant-payments-in-brazil "um guia de como realizar a integração"). 
+Acesse toda a [documentação técnica do protocolo](https://developers.vtex.com/docs/api-reference/payment-provider-protocol) e também [um guia de como realizar a integração](https://developers.vtex.com/docs/guides/payments-integration-pix-instant-payments-in-brazil). 
diff --git a/docs/announcements/pt/price-filters-more-search-flexibility.md b/docs/announcements/pt/price-filters-more-search-flexibility.md
index aca2bb5fb..547b8fab6 100644
--- a/docs/announcements/pt/price-filters-more-search-flexibility.md
+++ b/docs/announcements/pt/price-filters-more-search-flexibility.md
@@ -23,7 +23,7 @@ Agora, você pode filtrar os preços combinando as múltiplas Categorias e Marca
 
 Essa atualização da funcionalidade viabiliza a exportação de preços mais específicos, a partir da seleção dos filtros.
 
-![filtro preco-PT](https://images.ctfassets.net/alneenqid6w5/NzavsKoHY8DQUX2FZeoG6/f8152dfe5944412d46bea030585a20f0/filtro_preco-PT.png)
+![filtro preco-PT](//images.ctfassets.net/alneenqid6w5/NzavsKoHY8DQUX2FZeoG6/f8152dfe5944412d46bea030585a20f0/filtro_preco-PT.png)
 
 ## O que preciso fazer?
 Para utilizar essa nova configuração, siga os passos  abaixo:
diff --git a/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md b/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
index 636fa23c5..5ab1274a7 100644
--- a/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
+++ b/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
@@ -31,7 +31,7 @@ Para saber se a sua conta ainda está utilizando o Pricing V1, siga os passos ab
 
 Caso você visualize uma tela semelhante à tela abaixo, significa que sua conta precisa realizar a migração. 
 
-![Tela pricing antiga - PT](https://images.ctfassets.net/alneenqid6w5/7JRnTJEIa0Fh3noWBUEiUF/1c961c41028c24c19969c521ba1df552/Tela_pricing_antiga_-_PT.png)
+![Tela pricing antiga - PT](//images.ctfassets.net/alneenqid6w5/7JRnTJEIa0Fh3noWBUEiUF/1c961c41028c24c19969c521ba1df552/Tela_pricing_antiga_-_PT.png)
 
 Caso a sua conta VTEX ainda utiliza versões anteriores do Admin VTEX (como "vtexcommercestable", por exemplo), ela também precisará realizar a migração. Para isso, siga os passos a seguir:
 
diff --git a/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md b/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
new file mode 100644
index 000000000..f588515d7
--- /dev/null
+++ b/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
@@ -0,0 +1,55 @@
+---
+title: 'Simulador de promoções: entenda as promoções aplicadas ao carrinho'
+id: 2PPhczsmI0MXb5MyAlQx4R
+status: PUBLISHED
+createdAt: 2024-03-13T14:31:21.027Z
+updatedAt: 2024-03-13T19:02:02.287Z
+publishedAt: 2024-03-13T19:02:02.287Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: simulador-de-promocoes-entenda-as-promocoes-aplicadas-ao-carrinho
+locale: pt
+legacySlug: simulador-de-promocoes-entenda-as-promocoes-aplicadas-ao-carrinho
+announcementImageID: ''
+announcementSynopsisPT: 'Visualize e gerencie as promoções aplicadas no carrinho com o Simulador de promoções.'
+---
+
+
+Lançamos globalmente para todas as lojas VTEX o **Simulador de promoções**, nova ferramenta que permite visualizar as promoções aplicadas ao carrinho de compras na sua loja, juntamente com os motivos para sua ativação. 
+
+Diante das várias opções de configuração de [promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N), esse recurso é importante para ter uma visão clara das promoções concorrentes, do acúmulo de descontos durante a compra e das razões para a ativação dessas promoções.
+
+Criamos o **Simulador de promoções** para fornecer aos lojistas mais autonomia para gerenciar e conduzir as promoções de acordo com suas estratégias de negócios. Com a nova ferramenta, você poderá explorar e otimizar o desempenho das suas promoções, garantindo mais eficiência na sua operação e uma experiência de compra aprimorada para seus clientes.
+
+## O que há de novo?
+
+A partir de agora, o **Simulador de promoções** está disponível para todas as lojas VTEX pelo [Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451), ferramenta auxiliar para lojistas na etapa do checkout. Com o simulador, você pode:
+
+* **Visualizar as promoções** aplicáveis ou aplicadas a cada item no carrinho e a condição para ativá-las.
+* **Gerenciar as promoções** existentes a partir do carrinho de compras.
+* **Testar a remoção** de promoções aplicadas ao carrinho.
+* **Testar a aplicação** de outras promoções ao carrinho antes de ativá-las, incluindo promoções agendadas e inativas.
+* **Entender os motivos** de uma promoção não ter sido aplicada ao carrinho.
+
+![promotions simulator - pt-gif 3](//downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/54f7514e928050ff2ae19ce3fc3a93d4/promotions_simulator_announcement.gif)
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária, pois o **Simulador de promoções** já está disponível em todas as lojas VTEX pelo [Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451).
+
+Os usuários devem possuir um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) com autorização para acessar o módulo **Promoções** no Admin VTEX para conseguir utilizar o **Simulador de promoções**.
+
+Para começar a utilizar o simulador, siga os passos abaixo:
+
+1. Na barra superior do Admin VTEX, clique no botão `Pré-visualizar` para abrir a página de acesso restrito da sua loja.
+
+    Se preferir, você pode acessá-la diretamente pela URL `https://{nomedaconta}.myvtex.com/`, substituindo `{nomedaconta}` pelo nome da sua conta VTEX.
+
+2. Adicione produtos no carrinho e acesse o checkout em `https://{nomedaconta}.myvtex.com/checkout/#/cart`.
+3. Clique no botão azul <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> no canto inferior direito da página para iniciar o Cartman.
+4. Clique em **Simulador de promoções**.
+
+   Na nova janela, você verá os detalhes das promoções aplicadas e não aplicadas ao carrinho.
+
+Confira o guia [Simulador de promoções](https://help.vtex.com/pt/tutorial/simulador-de-promocoes-beta--4zc8SNqjqeIJ0ZRMhjlnvy) para mais detalhes sobre como usar a nova ferramenta.
diff --git a/docs/announcements/pt/rate-vtexs-service-in-your-admin.md b/docs/announcements/pt/rate-vtexs-service-in-your-admin.md
index b34222774..2699c6cbb 100644
--- a/docs/announcements/pt/rate-vtexs-service-in-your-admin.md
+++ b/docs/announcements/pt/rate-vtexs-service-in-your-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Lançamos uma página de pesquisa de satisfação no Ad
 
 Lançamos a nova página *Pesquisa de Satisfação* no seu Admin VTEX. Agora, você pode avaliar o atendimento do nosso suporte sem sair do ambiente VTEX.
 
-![Pesquisa de satisfação PT](https://images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/b213884709ae4bd96dc820d6b60b99b2/image__19_.png)
+![Pesquisa de satisfação PT](//images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/b213884709ae4bd96dc820d6b60b99b2/image__19_.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
new file mode 100644
index 000000000..7559784d4
--- /dev/null
+++ b/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -0,0 +1,87 @@
+---
+title: 'A validação do reCAPTCHA agora seguirá a configuração do orderForm para todas as solicitações'
+id: 3SLXk0n8neXgWxaLaIgAC7
+status: PUBLISHED
+createdAt: 2023-07-04T21:20:42.330Z
+updatedAt: 2023-07-05T18:40:32.146Z
+publishedAt: 2023-07-05T18:40:32.146Z
+contentType: updates
+productTeam: Shopping
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: validacao-recaptcha-agora-seguira-a-configuracao-do-orderform-para-todas-as-solicitacoes
+locale: pt
+legacySlug: a-validacao-do-recaptcha-agora-seguira-a-configuracao-do-orderform-para
+announcementImageID: ''
+announcementSynopsisPT: 'Lojas que usam a API de Checkout para fazer pedidos precisam revisar suas integrações'
+---
+
+O [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) é um serviço de segurança usado para verificar se uma determinada ação é realizada por um usuário real ou por uma automação mal-intencionada, protegendo os sites contra fraudes e abusos. Ao ativar o [reCAPTCHA no checkout](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP), além de seguir as melhores práticas contra ataques virtuais, você reduz o risco de sua loja ser explorada para fins fraudulentos.
+
+Para proteger ainda mais nossos clientes, a VTEX agora aplicará a configuração de reCAPTCHA do orderForm definida em cada conta a todas as solicitações da API de Checkout, independentemente dos perfis de acesso associados ao usuário ou à chave de aplicação.
+
+Os lojistas que usam a API de Checkout para fazer pedidos de aplicativos móveis, ambientes de loja headless e aplicativos semelhantes devem [revisar](#revise-suas-integracoes) e [ajustar](#ajuste-suas-integracoes) suas integrações antes de __1 de setembro de 2023__.
+
+## O que muda?
+
+Antes, a verificação reCAPTCHA não era necessária para pedidos feitos por usuários e chaves de aplicação com o [recurso](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) `Shopping Cart Full Access` no License Manager. Isso inclui [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy) como `Owner (Admin Super)` e `User Admin - RESTRICTED`, bem como o [usuário Titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy).
+
+Agora, a verificação do reCAPTCHA seguirá a configuração do orderForm definida em cada conta para todas as solicitações da API de Checkout, independentemente dos perfis de acesso associados ao usuário ou à chave de aplicação.
+
+## Por que estamos realizando esta mudança?
+
+Esta ação foi necessária para reduzir os riscos de fraude e abuso, como testes de cartões, em nossas lojas. Apesar de as boas práticas para o uso de chaves de aplicação recomendarem que as lojas criem chaves individuais para cada integração e apliquem perfis de acesso restritivos a elas, alguns lojistas estavam se expondo a riscos ao usar chaves de aplicação com perfis de acesso administrativos. 
+
+Como entendemos que pode haver um motivo legítimo para que algumas integrações tenham acesso a mais recursos e informações, nossa decisão foi exigir que os lojistas implementem o reCAPTCHA nessas integrações. Se isso não for possível, existe a alternativa de desativar a validação do reCAPTCHA em sua conta (`recaptchaValidation="never"`) e implementar medidas de proteção alternativas contra ataques automatizados por conta própria.
+
+Sabemos que essas mudanças terão um impacto nas operações de nossos clientes, mas aderir às melhores práticas de segurança é sempre necessário e benéfico para todo o nosso ecossistema.
+
+## O que precisa ser feito?
+
+### Revise suas integrações
+
+Peça à sua equipe de desenvolvimento para revisar as integrações que usam a API de Checkout para fazer pedidos em sua loja VTEX, usando os seguintes endpoints:
+
+- [Place order from an existing cart](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pub/orderForm/-orderFormId-/transaction)
+- [Place order](https://developers.vtex.com/docs/api-reference/checkout-api#put-/api/checkout/pub/orders)
+
+Ela poderá seguir o diagrama abaixo para avaliar se uma integração precisa ser ajustada, de acordo com a [configuração de reCAPTCHA do orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) da sua loja e como as solicitações feitas a esses endpoints são [autenticadas](https://developers.vtex.com/docs/guides/authentication-overview):
+
+![reCAPTCHA diagram](//images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/bfd89311bfff3e2597bb5fbf2862d6da/recaptcha-config-PT.png)
+
+- __Caso 1__: *não são necessárias alterações na integração, mas sua loja pode estar em risco.*
+
+  Sua loja não usa o reCAPTCHA no Checkout e, portanto, está vulnerável a ataques automatizados, a menos que outras medidas de proteção sejam implementadas na sua integração.
+
+- __Caso 2__: *sua integração precisa ser ajustada, caso contrário, ela poderá parar de funcionar.*
+
+  Sua loja usa o reCAPTCHA no Checkout, mas não está pronta para exibi-lo corretamente na interface do usuário. Sua equipe de desenvolvimento deve [ajustar suas integrações](#ajuste-suas-integracoes).
+
+- __Caso 3__: *não são necessárias alterações na integração.*
+
+  Sua loja usa o reCAPTCHA no Checkout e está pronta para exibi-lo corretamente na interface do usuário. Parabéns por seguir as melhores práticas de segurança!
+
+### Ajuste suas integrações
+
+Se sua equipe de desenvolvimento identificou que sua integração requer atenção, ela deve seguir as instruções fornecidas no guia para desenvolvedores [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations) (em inglês).
+
+<div class="alert alert-warning">
+Para implementar o reCAPTCHA em um aplicativo mobile nativo, use reCAPTCHA v3. Para outros casos de integração, use reCAPTCHA v2.
+</div>
+
+Ao usar a chave do reCAPTCHA (`recaptchaKey`) retornada pelo Checkout, o widget reCAPTCHA deve ser renderizado na interface do usuário do seu aplicativo móvel/storefront headless (ou similar), conforme descrito na documentação do [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display?hl=pt-br) ou [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3?hl=pt-br) fornecida pelo Google.
+
+Depois que o comprador tiver concluído o desafio do reCAPTCHA, sua resposta (`recaptchaToken`) deverá ser enviada para a API de Checkout para finalizar a compra, conforme descrito na seção *Final validation* do guia [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#final-validation) (em inglês). Em seguida, a API de Checkout [verificará a resposta do usuário](https://developers.google.com/recaptcha/docs/verify?hl=pt-br) usando o token fornecido.
+
+<div class="alert alert-danger">
+Todas as integrações que usam a API de Checkout para fazer pedidos devem ser revisadas e ajustadas antes de 1 de setembro de 2023. Os aplicativos que não conseguirem renderizar o widget reCAPTCHA e verificar a resposta do usuário não poderão fazer pedidos após essa data.
+</div>
+
+## Saiba mais
+
+Consulte a documentação a seguir para saber mais sobre o reCAPTCHA e as melhores práticas para garantir que sua loja esteja protegida:
+
+- [reCAPTCHA no Checkout](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP)
+- [Boas práticas contra ataques virtuais](https://help.vtex.com/pt/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE)
+- [Boas práticas na utilização de chaves de aplicação](https://help.vtex.com/pt/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm)
+- [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3)
+
diff --git a/docs/announcements/pt/redesigned-products-and-skus-page.md b/docs/announcements/pt/redesigned-products-and-skus-page.md
index 3a4c65f78..377aefd48 100644
--- a/docs/announcements/pt/redesigned-products-and-skus-page.md
+++ b/docs/announcements/pt/redesigned-products-and-skus-page.md
@@ -28,7 +28,7 @@ A nova interface de **Produtos & SKUs** possibilita:
 * Acompanhar status de produtos e SKUs de forma mais direta e visual, com ícones e status de SKUs diretamente na listagem.
 * Identificar com mais facilidade produtos e SKUs com informações pendentes para ficarem disponíveis para venda, a partir do novo status **Pendente**.
 
-![catalog-products-skus-pt](https://images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/269a128e08a453ce564041ceb39bea9e/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_25_56_1.png)
+![catalog-products-skus-pt](//images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/269a128e08a453ce564041ceb39bea9e/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_25_56_1.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
index 2a71ac39e..0bca9e35b 100644
--- a/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
@@ -1,10 +1,10 @@
 ---
 title: 'Requisições com paginação na API de busca vão mudar'
 id: 3UZR4qoAisiqE6kmuuYEAc
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-01-24T14:11:26.225Z
-updatedAt: 2020-11-27T19:40:17.179Z
-publishedAt: 2020-05-11T18:53:36.826Z
+updatedAt: 2023-12-15T13:03:53.872Z
+publishedAt: 2023-12-15T13:03:53.872Z
 contentType: updates
 productTeam: Identity
 author: authors_24
@@ -32,5 +32,5 @@ Essa mudança já foi implementada na API, mas até a data limite, ainda será p
 - Também há um limite de 2500 itens para uma busca. Por isso, não é possível adicionar um valor maior que 2500 ao parâmetro <b>_to</b>.<br>
 </div>
 
-Para saber todos os detalhes do funcionamento das requisições de paginação na API de busca, acesse este [documento](https://developers.vtex.com/reference/search-api-overview).
+Para saber todos os detalhes do funcionamento das requisições de paginação na API de busca, acesse este [documento](https://developers.vtex.com/docs/api-reference/search-api).
 
diff --git a/docs/announcements/pt/reusing-images-in-site-editor.md b/docs/announcements/pt/reusing-images-in-site-editor.md
index a130592cd..611569e84 100644
--- a/docs/announcements/pt/reusing-images-in-site-editor.md
+++ b/docs/announcements/pt/reusing-images-in-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Aprimoramos blocos com a opção nativa de envio de ima
 
 Aprimoramos a maneira como você gerencia suas imagens no [Site Editor](https://help.vtex.com/pt/subcategory/site-editor--9Arh3cJIOYlfSD1MUC2h3) por meio do Image Widget, um repositório de imagens centralizado para que você possa enviar e reutilizar imagens da loja. 
 
-![gif-image-widget-pt](https://images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/04a48b195d89b88cf44fde97989c3770/Irec5JDGdy.gif)
+![gif-image-widget-pt](//images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/04a48b195d89b88cf44fde97989c3770/Irec5JDGdy.gif)
 
 <div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 16px">
   Image Widget está disponível em Open Beta para usuários VTEX IO.
diff --git a/docs/announcements/pt/sales-performance-dashboard-updates.md b/docs/announcements/pt/sales-performance-dashboard-updates.md
index bb428c492..985b95e27 100644
--- a/docs/announcements/pt/sales-performance-dashboard-updates.md
+++ b/docs/announcements/pt/sales-performance-dashboard-updates.md
@@ -19,7 +19,7 @@ A página Performance de Vendas é um dashboard que permite que operadores de lo
 
 Atualizamos a sua experiência na página a partir das sugestões dadas por vocês, adicionando novas possibilidades para aplicação de filtros, visualizações e exploração de dados. 
 
-![Sales perf update PT](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
+![Sales perf update PT](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
 
 ## O que mudou?
 Aprimoramos algumas funcionalidades existentes, como Filtros e Dados, e acrescentamos o menu Visualização. A nova experiência de filtros da página possibilita mais combinações de filtros, com menos cliques. Já a nova funcionalidade de menu Visualização foi feita para gravar os filtros e métricas aplicados na página, permitindo voltar rapidamente para o mesmo contexto. 
diff --git a/docs/announcements/pt/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md b/docs/announcements/pt/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
index 9cfdb82a4..0e497b638 100644
--- a/docs/announcements/pt/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
+++ b/docs/announcements/pt/samsung-pay-more-flexible-payments-thanks-to-the-new-digital-wallet.md
@@ -3,8 +3,8 @@ title: 'Samsung Pay: flexibilize pagamentos com a nova carteira digital'
 id: 2hPbwpiBjuUDh5exB2t5I9
 status: PUBLISHED
 createdAt: 2020-08-26T13:58:55.512Z
-updatedAt: 2020-08-26T16:42:36.874Z
-publishedAt: 2020-08-26T16:42:36.874Z
+updatedAt: 2023-09-26T15:25:06.834Z
+publishedAt: 2023-09-26T15:25:06.834Z
 contentType: updates
 productTeam: Financial
 author: 7qy2DBsUp8U5P9lqV0JHfR
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'A partir de Agosto, a VTEX conta com Samsung Pay, carteira digital da Samsung, como meio de pagamento no SmartCheckout.'
 ---
 
-A VTEX procura sempre entregar a melhor experiência de compra para os seus clientes. Por isso, agora você pode utilizar o [Samsung Pay](https://www.samsung.com.br/samsungpay/ "Samsung Pay") - a [carteira digital](https://help.vtex.com/pt/tutorial/o-que-e-uma-carteira-digital-e-wallet?locale=pt "carteira digital") (e-wallet) da Samsung - como meio de pagamento no seu e-commerce.
+A VTEX procura sempre entregar a melhor experiência de compra para os seus clientes. Por isso, agora você pode utilizar o [Samsung Pay](https://www.samsung.com.br/samsungpay/ "Samsung Pay") - a [carteira digital](https://help.vtex.com/pt/tutorial/o-que-e-uma-carteira-digital-e-wallet?locale=pt "carteira digital") (ewallet) da Samsung - como meio de pagamento no seu e-commerce.
 
 ## Vantagens 
 Oferecer carteiras digitais como forma de pagamento no SmartCheckout expande a gama de meios de pagamento do seu e-commerce.
diff --git a/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md b/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md
index 8986a4a4e..be765a6c0 100644
--- a/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md
+++ b/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md
@@ -23,7 +23,7 @@ Anteriormente, após o cadastro na loja ou primeira compra, os dados do cliente
 
 A partir de agora, duas caixas de seleção estarão disponíveis na tela do Checkout, permitindo que o usuário indique se deseja que suas informações pessoais e de pagamento sejam armazenadas e reutilizadas para futuras compras. Dessa maneira, será  reduzido o tempo de compra realizado pelo cliente. 
 
-![ Save user data opt-in PT](https://images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/5324e710aa8787fc411b63e1f67609e2/Save_user_data_-_PT.PNG)
+![ Save user data opt-in PT](//images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/5324e710aa8787fc411b63e1f67609e2/Save_user_data_-_PT.PNG)
 
 Saiba mais em [SmartCheckout - Preenchimento automático de dados do cliente](https://help.vtex.com/pt/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan#).
 
diff --git a/docs/announcements/pt/schedule-content-publication-with-site-editor.md b/docs/announcements/pt/schedule-content-publication-with-site-editor.md
index f48e215c6..47a08580f 100644
--- a/docs/announcements/pt/schedule-content-publication-with-site-editor.md
+++ b/docs/announcements/pt/schedule-content-publication-with-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Crie e programe versões de bloco predefinidas no Site
 
 O recurso **Configurações** do Site Editor foi atualizado. Agora, além de se chamar **Versões**, você pode criar as  versões do conteúdo de sua loja desativadas e ativá-las quando desejar.
 
-![activating-versions-pt](https://images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/01ea74a9392015c3eb54ae8b0546908a/activating-versions-pt.gif)
+![activating-versions-pt](//images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/01ea74a9392015c3eb54ae8b0546908a/activating-versions-pt.gif)
 
 ## O que mudou?
 Antes, o recurso **Versões** se chamava **Configurações**, e era apenas possível criar uma nova versão ativada, por exemplo, de um Carrossel com produtos em promoção, ou agendar a sua ativação. Após uma versão sair do ar, também não era possível ativá-la novamente.
diff --git a/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
new file mode 100644
index 000000000..19dbfa9ac
--- /dev/null
+++ b/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -0,0 +1,50 @@
+---
+title: 'A barra de busca global do Admin VTEX agora permite buscar pedidos'
+id: 4ycVQJ5hRkxVy8r2iQamCb
+status: PUBLISHED
+createdAt: 2023-10-17T12:05:18.467Z
+updatedAt: 2023-10-17T21:04:22.374Z
+publishedAt: 2023-10-17T21:04:22.374Z
+contentType: updates
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: a-barra-de-busca-global-do-admin-vtex-agora-permite-buscar-pedidos
+locale: pt
+legacySlug: a-barra-de-busca-global-do-admin-vtex-agora-permite-buscar-pedidos
+announcementImageID: ''
+announcementSynopsisPT: 'A barra de busca global do Admin VTEX agora permite buscar nos pedidos da loja.'
+---
+
+Melhoramos a barra de busca global, localizada no topo das páginas do Admin VTEX, para que você possa pesquisar não apenas nas páginas do Admin, mas também nos pedidos da sua loja.
+
+Esta melhoria será disponibilizada globalmente para todas as lojas VTEX a partir de hoje, 17 de outubro, por meio de uma atualização automática.
+
+## O que mudou?
+
+Antes, a barra de busca global permitia buscar somente nas páginas do Admin VTEX. Agora, você também pode buscar nos pedidos da sua loja, utilizando qualquer um dos seguintes critérios:
+
+* ID do pedido
+* Nome do cliente
+* Email do cliente
+* Documento do cliente
+
+Para isso, clique na barra de busca, selecione a opção `Pedidos`, e realize a pesquisa desejada. Cada busca pode apresentar até 10 resultados, como na imagem abaixo:
+
+![order_global_search_PT](//images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/1d0f182535930b7157f9ed03aa363af6/order_global_search_PT.gif)
+
+Ao clicar em um resultado, você é redirecionado para a [página de detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) do pedido. Além disso, os últimos 10 pedidos buscados ficam registrados como um histórico de buscas recentes, aumentando a praticidade de acesso. O registro de busca é armazenado a nível de [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) e não é compartilhado entre usuários diferentes.
+
+<div class = "alert alert-info">
+Para acessar pedidos pela busca global do Admin VTEX, é necessário que o <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> do usuário esteja associado ao recurso <b>View order</b> (chave OMSViewer) do <i>Order Management System</i> (OMS).
+</div>
+
+## Por que fizemos essa mudança?
+
+Acessar pedidos a partir da barra de busca global facilita a realização de operações que envolvem pedidos, o que resulta em um aumento da eficiência. 
+
+Agora, independente da página do Admin em que você se encontre, você tem acesso à barra de busca global e pode acessar pedidos sem a necessidade de acessar o módulo **Pedidos**.
+
+## O que precisa ser feito?
+
+A partir de hoje, 17 de outubro, todas as lojas VTEX serão automaticamente atualizadas com a melhoria, não sendo necessário qualquer ação da sua parte.
+
diff --git a/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md b/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
index 007d80cea..50ef42a8f 100644
--- a/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
+++ b/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
@@ -19,7 +19,7 @@ A __Black Friday__ está chegando. E, com ela, vem o desejo de aproveitar essa o
 
 Para te ajudar nessa tarefa, a VTEX está lançando uma __app exclusiva em parceria com o Google__, que ficará disponível em nossa [App Store](https://apps.vtex.com/vtex-google-shopping/p).
 
-![Google Shopping App](https://images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
+![Google Shopping App](//images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
 
 Ela integra seu negócio ao Google Ads, permitindo que você divulgue seus produtos no Google Shopping, usando as novas Smart Shopping Campaigns, e acompanhe os resultados com facilidade e rapidez.
 
diff --git a/docs/announcements/pt/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md b/docs/announcements/pt/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
index fd409f598..9f90f7da0 100644
--- a/docs/announcements/pt/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
+++ b/docs/announcements/pt/seller-restriction-create-promotions-with-more-control-over-affected-sellers.md
@@ -25,7 +25,7 @@ Configuração antes da atualização:
   <tr>
     <td>
       <img
-           src="https:https://images.ctfassets.net/alneenqid6w5/6qb2C2KjQgKayaqiM2USGL/ed89629aff64aa8256b0e7c77fa8ed76/seller-promo-PT.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
+           src="https://images.ctfassets.net/alneenqid6w5/6qb2C2KjQgKayaqiM2USGL/ed89629aff64aa8256b0e7c77fa8ed76/seller-promo-PT.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
     </td>
   </tr>
   <tr>
@@ -43,7 +43,7 @@ Configuração após a atualização:
   <tr>
     <td>
       <img
-           src="https:https://images.ctfassets.net/alneenqid6w5/5hJ6CCeGeJdJtDUrsVcc8h/c8025981576d0941aed65edc10975e4e/seller-promo-PT2.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
+           src="https://images.ctfassets.net/alneenqid6w5/5hJ6CCeGeJdJtDUrsVcc8h/c8025981576d0941aed65edc10975e4e/seller-promo-PT2.png" style= "display: block; margin-left: auto; margin-right: auto;" alt = "Configuração de sellers na promoção">
     </td>
   </tr>
   <tr>
diff --git a/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md b/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
new file mode 100644
index 000000000..47526a27a
--- /dev/null
+++ b/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
@@ -0,0 +1,30 @@
+---
+title: 'Black Friday: Prepare sua loja com a nossa Cartilha de Boas Práticas'
+id: 4c0wnRmblHPKfCKkkiOkhX
+status: PUBLISHED
+createdAt: 2023-10-03T13:08:30.221Z
+updatedAt: 2023-11-17T19:45:14.488Z
+publishedAt: 2023-11-17T19:45:14.488Z
+contentType: updates
+productTeam: Others
+author: 1u80f14cWqneWquMc8tUq1
+slug: black-friday-prepare-sua-loja-com-a-nossa-cartilha-de-boas-praticas-2023
+locale: pt
+legacySlug: 
+announcementImageID: ''
+announcementSynopsisPT: 'Siga nossas recomendações e dicas exclusivas para aproveitar todas as oportunidades de venda da Black Friday.'
+---
+
+A __Black Friday__ já está chegando. A data oficial este ano é __24 de novembro__, mas muitas lojas vão começar a fazer campanhas promocionais com bastante antecedência. Por isso, para aproveitar ao máximo todas as oportunidades de uma das principais datas do varejo, é bom começar logo a se preparar.
+
+Como fazemos todos os anos, criamos uma cartilha com recomendações e dicas exclusivas para você garantir a saúde da sua loja e o sucesso das suas vendas. 
+
+Disponível para clientes e parceiros VTEX, o guia pode ser acessado diretamente pela URL:
+
+```
+https://{accountName}.myvtex.com/admin/shopping-season
+```
+
+Basta substituir `{accountName}` pelo Account Name da sua loja, como na imagem abaixo.
+
+![Shopping Season Guidelines - 2023 - PT](//images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/241e179f90c255d883968098fc781826/Shopping_Season_Guidelines_-_2023_-_PT.png)
diff --git a/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md b/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md
new file mode 100644
index 000000000..c99879cb1
--- /dev/null
+++ b/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md
@@ -0,0 +1,34 @@
+---
+title: 'Site Editor e Mídia: nova solicitação de autorização'
+id: 7tO32uRxIUK8lOp8AvWs2L
+status: PUBLISHED
+createdAt: 2024-02-26T12:35:10.352Z
+updatedAt: 2024-02-26T18:06:13.754Z
+publishedAt: 2024-02-26T18:06:13.754Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: site-editor-e-midia-nova-solicitacao-de-autorizacao
+locale: pt
+legacySlug: site-editor-e-midia-nova-solicitacao-de-autorizacao
+announcementImageID: ''
+announcementSynopsisPT: 'Usuários agora precisam do recurso CMS GraphQL API para gerenciar conteúdo. Atualize os perfis de acesso de acordo.'
+---
+
+A partir de segunda-feira, 18 de março de 2024, todos os[ usuários](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) e [chaves de aplicação](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) que precisarem acessar o [Site Editor](https://help.vtex.com/pt/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) e o [Mídia](https://help.vtex.com/pt/tutorial/media-overview--31fhjHTt4TBoo50AmGQ9b2) deverão ter o[ recurso](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `CMS GraphQL API` do License Manager adicionados aos seus[ perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) para o gerenciamento de conteúdo.
+
+## O que mudou?
+Como [anunciado anteriormente para os usuários do Headless CMS](https://help.vtex.com/pt/announcements/headless-cms-new-authorization-requirement--7G056zzZmGFBztkRqhpUgj), os usuários e as chaves de aplicação devem ter o recurso `CMS GraphQL API` associado aos seus perfis de acesso para gerenciar conteúdo.
+
+Agora, estamos estendendo esse requisito para o Site Editor e o Mídia, o que significa que o recurso `CMS GraphQL API` é necessário para gerenciar conteúdo usando essas ferramentas.
+
+## Por que fizemos esta mudança?
+Essa alteração visa aumentar a segurança e simplificar o acesso do usuário ao Site Editor e ao Mídia, proporcionando aos usuários um ambiente mais controlado e seguro para gerenciar o conteúdo da loja.
+
+## O que precisa ser feito?
+Certifique-se de que os usuários do Site Editor e do Mídia estejam associados ao recurso `CMS GraphQL API` em seus perfis de acesso, seja [criando um novo perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) ou editando um existente.
+
+<div class="alert alert-warning">
+  <p> Para gerenciar usuários e perfis de acesso, é necessário ter o recurso <code>Save access profile</code> do produto <bold>License Manager</bold> associado ao perfil de acesso do usuário. Por exemplo, o <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> é um perfil de acesso predefinido que tem o recurso <code>Save access profile</code> associado a ele.</p>
+</div>
+
diff --git a/docs/announcements/pt/site-editor-fixed-content-loss-issue.md b/docs/announcements/pt/site-editor-fixed-content-loss-issue.md
new file mode 100644
index 000000000..3d31fd1c3
--- /dev/null
+++ b/docs/announcements/pt/site-editor-fixed-content-loss-issue.md
@@ -0,0 +1,29 @@
+---
+title: 'Site Editor: problema de perda de conteúdo corrigido'
+id: 1mnrlSMyMmU1iAUyEquVYB
+status: PUBLISHED
+createdAt: 2024-06-13T12:25:13.359Z
+updatedAt: 2024-06-13T13:29:05.308Z
+publishedAt: 2024-06-13T13:29:05.308Z
+contentType: updates
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: site-editor-problema-de-perda-de-conteudo-corrigido
+locale: pt
+legacySlug: site-editor-problema-de-perda-de-conteudo-corrigido
+announcementImageID: ''
+announcementSynopsisPT: 'O armazenamento de conteúdo do Site Editor foi atualizado para melhorar seu desempenho e confiabilidade.'
+---
+
+No dia 12 de junho, o armazenamento de conteúdo do [Site Editor](https://help.vtex.com/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) foi atualizado todas as contas para todas as contas que o utilizam a fim de solucionar um problema conhecido: a perda [intermitente de conteúdo do Site Editor](https://help.vtex.com/en/known-issues/intermitent-site-editor-content-loss--3a5MlAoD2Z7Gu6HDS8wihD). Essa atualização melhora o desempenho e a confiabilidade do armazenamento, além de reduzir o espaço ocupado pelo seu conteúdo.
+
+## O que mudou?
+Antes, as constantes alterações de conteúdo no Site Editor podiam fazer com que o arquivo `content.json` se tornasse excessivamente grande, levando à perda de conteúdo ao [criar um workspace de produção para a master](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspaces-best-practices#deployment-and-workspace-promotion) ou ao instalar uma nova versão de tema em um workspace de teste.
+
+Também aprimoramos a arquitetura de armazenamento e a solução de segmentação de arquivos do Site Editor. Agora o conteúdo é armazenado em arquivos menores e específicos do modelo, em vez de em um único arquivo grande. Essa alteração reduz o tamanho do arquivo em aproximadamente 90%, reduzindo o espaço de armazenamento necessário por página e melhorando o desempenho geral e a entrega de conteúdo.
+
+## O que precisa ser feito?
+Nenhuma ação é necessária. A atualização foi implementada automaticamente em todas as lojas VTEX que usam o Site Editor.
+
+Se a perda de conteúdo persistir após 12 de junho, abra um ticket para o [Suporte da VTEX](https://help.vtex.com/support).
+
diff --git a/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md b/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md
index bc2ca5c9e..af0681483 100644
--- a/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md
+++ b/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md
@@ -27,7 +27,7 @@ Antes, a funcionalidade de Social Selling no inStore consistia em gerar um link
 
 Com a mudança, agora o inStore também gera um QR code que pode ser lido pelos dispositivos dos clientes, além do link compartilhável.
 
-![instore-social-selling-qr-code-share-pt](https://images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/21874f9cc593ea5f8dda4f985deb6fe2/image1.png)
+![instore-social-selling-qr-code-share-pt](//images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/21874f9cc593ea5f8dda4f985deb6fe2/image1.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/the-insights-dashboard-will-be-discontinued.md b/docs/announcements/pt/the-insights-dashboard-will-be-discontinued.md
new file mode 100644
index 000000000..44302ba87
--- /dev/null
+++ b/docs/announcements/pt/the-insights-dashboard-will-be-discontinued.md
@@ -0,0 +1,39 @@
+---
+title: 'O painel Insights será descontinuado'
+id: 4yJtAquGwufjHFTcGwnTwr
+status: PUBLISHED
+createdAt: 2023-10-03T23:02:27.048Z
+updatedAt: 2023-10-04T15:06:15.480Z
+publishedAt: 2023-10-04T15:06:15.480Z
+contentType: updates
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: o-painel-insights-sera-descontinuado
+locale: pt
+legacySlug: o-painel-insights-sera-descontinuado
+announcementImageID: ''
+announcementSynopsisPT: 'A partir de 15 de outubro de 2023, não será mais possível acessar o painel Insights, que será descontinuado.'
+---
+
+O **Insights** é um painel que permite que você acompanhe a evolução das suas vendas, com uma visão detalhada do funil de conversão e das principais métricas que impactam a receita da sua loja.
+
+Atualmente, o [painel Insights](https://help.vtex.com/pt/tutorial/acompanhando-a-evolucao-das-suas-vendas--5QtyTR0jFy9gDnr4EYCjdq) é acessível somente pelo endereço:
+```
+https://{nomeDeConta}.myvtex.com/admin/insights
+```
+
+A partir de 15 de outubro de 2023, não será mais possível acessar o [painel Insights](https://help.vtex.com/pt/tutorial/acompanhando-a-evolucao-das-suas-vendas--5QtyTR0jFy9gDnr4EYCjdq), que será descontinuado.
+
+## Por que estamos fazendo esta mudança?
+
+As informações disponibilizadas no painel **Insights** também estão disponíveis em outros painéis:
+- [Visão geral da loja](https://help.vtex.com/pt/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ)
+- [Visão geral da loja (Beta)](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46)
+
+Portanto, esta descontinuação visa diminuir a redundância na plataforma e que, futuramente, possamos focar em manter e aprimorar uma única experiência. Atualmente, os painéis **Visão geral da loja** já contam as mesmas informações que o painel **Insights**, mas com dados mais precisos e melhor visualização.
+
+## O que precisa ser feito?
+
+A partir de 15 de outubro de 2023, a mudança acontecerá de forma automática para todas as lojas VTEX sem nenhuma ação necessária da sua parte.
+
+Caso deseje acompanhar as métricas de vendas da sua loja, confira a [visão geral da loja](https://help.vtex.com/pt/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ) ou a [nova versão da visão geral](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) (Beta), que contam com as mesmas informações do painel **Insights**, mas com dados mais precisos e melhor visualização.
diff --git a/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md b/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md
index d911d6b35..632464912 100644
--- a/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md
+++ b/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md
@@ -35,7 +35,7 @@ A revisão e o eventual ajuste desta mudança devem ser aplicados através dos t
 
 Passos necessários para a revisão e adaptação:
 
-1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
+1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
 2. __Customização__: se a página "/account/orders" possuir alguma customização de front-end, esta deve ser migrada e adaptada para a nova URL "/account#/orders". Revise e realize todos os testes necessários garantindo funcionamento de todas as recursos personalizados;  
 3. __Links do site__: Revise e atualize todos os links customizados do site e dos e-mails transacionais que antes direcionavam o usuário para a URL "/account/orders". Estes links agora devem direcionar o usuário para "/account#/orders".
 
diff --git a/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md b/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md
new file mode 100644
index 000000000..843e49eb1
--- /dev/null
+++ b/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md
@@ -0,0 +1,34 @@
+---
+title: 'Módulo Gerenciamento de anúncio será descontinuado'
+id: 1kQw84J88i1ziNlXX5XA5S
+status: PUBLISHED
+createdAt: 2023-10-05T12:50:25.536Z
+updatedAt: 2023-10-05T13:51:31.119Z
+publishedAt: 2023-10-05T13:51:31.119Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: modulo-gerenciamento-de-anuncio-sera-descontinuado
+locale: pt
+legacySlug: modulo-gerenciamento-de-anuncio-sera-descontinuado
+announcementImageID: ''
+announcementSynopsisPT: 'O módulo de Gerenciamento de anúncios estará disponível apenas para integração com o Mercado Livre.'
+---
+
+Visando proporcionar a melhor experiência aos nossos clientes, anunciamos a deprecação do módulo de Gerenciamento de anúncios do Admin VTEX.
+
+Os anúncios enviados aos marketplaces não serão afetados e ainda é possível visualizar o status de cada um acessando **Marketplace > Conexões > Produtos no Admin VTEX.**
+
+## O que mudou?
+
+Removemos do módulo de Gerenciamento de anúncios a possibilidade de acompanhar o status e a sincronização dos anúncios enviados a um marketplace.
+Permanece disponível as funcionalidades de [Moderação](https://help.vtex.com/pt/tutorial/gerenciamento-de-anuncios-moderacao-e-qualidade-dos-anuncios-do-mercado--xSbPzA41jiWPAorlBCEA4?&utm_source=autocomplete#moderacao), [Qualidade de anúncios](https://help.vtex.com/pt/tutorial/gerenciamento-de-anuncios-moderacao-e-qualidade-dos-anuncios-do-mercado--xSbPzA41jiWPAorlBCEA4?&utm_source=autocomplete#qualidade) e [Oportunidades de Catálogo MeLi](https://help.vtex.com/pt/tutorial/anuncios-enviados-oportunidades-de-buybox--1hO9eI1th47EGxQoTzGewC) até a data de 15 de dezembro de 2023, apenas para anúncios vinculados à [integração do Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/51oWBHvVxSs8eAwLQhSbSd), acessando **Marketplace > Mercado Livre > Gerenciamento de anúncios.**
+
+## O que precisa ser feito?
+
+Essa atualização é automática, não é necessário realizar nenhuma ação. A partir da data indicada acima o módulo será completamente descontinuado de todos os Admin VTEX.
+
+<div class="alert alert-info">
+Em breve teremos um módulo substituto para o Gerenciador de anúncios, acompanhe as novidades no <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
+</div>
+
diff --git a/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md b/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md
index fb98c04f6..baf1060ae 100644
--- a/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md
+++ b/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Lançamento de nova ferramenta de auditoria'
 
 Sempre em conformidade com as melhores práticas de segurança e transparência para sua loja, a VTEX lançou mais um novo recurso de auditoria, o **Audit**. 
 
-![Screenshot for Audit UI for announcement](https://images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/a7e351d449a8ff53422f9a9b914dbdc2/Audit_PT.png)
+![Screenshot for Audit UI for announcement](//images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/a7e351d449a8ff53422f9a9b914dbdc2/Audit_PT.png)
 
 A partir de agora, os administradores podem verificar diversas operações que foram feitas em sua loja de uma maneira simples e rápida. É possível criar vários filtros de busca para facilitar a procura de eventos e aumentar a rapidez dos processos de auditoria.
 
diff --git a/docs/announcements/pt/troubleshooting-guides-your-new-vtex-self-service-experience.md b/docs/announcements/pt/troubleshooting-guides-your-new-vtex-self-service-experience.md
new file mode 100644
index 000000000..1e9a4446b
--- /dev/null
+++ b/docs/announcements/pt/troubleshooting-guides-your-new-vtex-self-service-experience.md
@@ -0,0 +1,53 @@
+---
+title: 'Guias de troubleshooting: sua nova experiência de autoatendimento na VTEX'
+id: 5oDp5raqBpRta660NERceY
+status: PUBLISHED
+createdAt: 2024-07-08T15:04:53.687Z
+updatedAt: 2024-07-08T21:47:04.455Z
+publishedAt: 2024-07-08T21:47:04.455Z
+contentType: updates
+productTeam: Others
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: guias-de-troubleshooting-sua-nova-experiencia-de-autoatendimento-na-vtex
+locale: pt
+legacySlug: guias-de-troubleshooting-sua-nova-experiencia-de-autoatendimento-na-vtex
+announcementImageID: ''
+announcementSynopsisPT: 'Resolva problemas com mais rapidez e autonomia com nossos guias de troubleshooting reformulados.'
+---
+
+A VTEX está em constante evolução para melhorar a experiência de suporte ao cliente e capacitá-lo a resolver problemas com mais eficiência e autonomia. 
+Com o objetivo de facilitar o seu suporte, agora você tem acesso aos Guias de Troubleshooting disponíveis no [Help Center](https://help.vtex.com/pt/category/troubleshooting--39pDkp8qxSll6mGj0tWViz) e [Developer Portal](https://developers.vtex.com/docs/troubleshooting). Esses guias explicam os possíveis cenários de erros em operações da loja e durante o desenvolvimento da loja ou apps, e orientam como atuar para restaurar o desempenho esperado para a sua loja.
+
+<div class="alert alert-info" role="alert"> 
+  Quer contribuir com esta iniciativa? Preencha este <a href="https://forms.gle/PdVNZmMDMjiDfJaf8">Formulário de feedback</a>.
+</div>
+
+## Como estão organizados os Guias de Troubleshooting?
+Os Guias de Troubleshooting estão disponíveis no [Help Center](https://help.vtex.com/category/troubleshooting--39pDkp8qxSll6mGj0tWViz) e [Developer Portal](https://developers.vtex.com/docs/troubleshooting), e estão divididos em categorias da seguinte forma:
+
+- [Help Center](https://help.vtex.com/category/troubleshooting--39pDkp8qxSll6mGj0tWViz):
+  - [Operações da loja](https://help.vtex.com/subcategory/store-operations--2Q0IQjRcOqSgJTh6wRHVMB): Seção para solucionar as dificuldades encontradas com operações de plataforma e ecommerce.
+
+- [Developer Portal](https://developers.vtex.com/docs/troubleshooting):
+  - **Development**: Seção destinada a abordar erros relacionados ao desenvolvimento de frente de loja e aplicativos.
+  - **Store performance**: Seção com procedimentos para depurar erros e restaurar o funcionamento da loja caso esteja inoperante ou fora do ar. 
+
+<div class="alert alert-info" role="alert"> 
+  Até o momento da publicação deste Announcement, 15 guias já estão disponíveis para consulta e outros mais estão sendo produzidos.
+</div>
+
+## Por que criamos esta iniciativa?
+Nosso objetivo é tornar a experiência de suporte VTEX mais simples e eficiente. Com os novos guias de Troubleshooting você poderá:
+
+- **Identificar problemas com mais rapidez:** Descrições de cenários de operação de loja e desenvolvimento que ajudarão você a identificar o problema que está enfrentando.
+- **Encontrar soluções para cada caso apresentado:** Procedimentos que explicam os passos necessários para resolver os erros.
+- **Ter maior autonomia no gerenciamento de falhas:** Possibilidade de resolver erros internamente, no momento em que desejar e sem a necessidade de acionamento do Suporte Técnico.
+
+## Como você pode nos ajudar?
+Estamos comprometidos em expandir e melhorar continuamente esta iniciativa, analisando novos cenários de problemas e publicando mais Guias de Troubleshooting regularmente. Para garantir que estamos no caminho certo, o seu feedback é crucial!
+
+Veja como contribuir conosco:
+
+- **Compartilhe seu feedback:** Preencha nosso [Formulário de Feedback](https://forms.gle/PdVNZmMDMjiDfJaf8) com suas sugestões ou críticas sobre os novos Guias de Troubleshooting.
+- **Vamos conversar?** Caso deseje compartilhar de forma mais detalhada a sua experiência com a nossa documentação ou sugerir melhorias específicas a respeito do Help Center e Developer Portal, preencha o [Formulário de Feedback](https://forms.gle/PdVNZmMDMjiDfJaf8) e entraremos em contato com você em até 5 dias úteis para agendarmos um bate-papo com o nosso time de Education.
+
diff --git a/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md b/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md
index db0cd8576..0cacbc950 100644
--- a/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md
+++ b/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md
@@ -17,6 +17,6 @@ announcementSynopsisPT: ''
 
 kjevfuevd
 
-![PT Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![PT Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 jsvdcusv
diff --git a/docs/announcements/pt/update-grants-in-the-promotions-module.md b/docs/announcements/pt/update-grants-in-the-promotions-module.md
index 9343a92e9..0adb6172d 100644
--- a/docs/announcements/pt/update-grants-in-the-promotions-module.md
+++ b/docs/announcements/pt/update-grants-in-the-promotions-module.md
@@ -37,5 +37,5 @@ Com esta atualização, você tem mais poder sobre  o comportamento das suas pro
  6. Clique em  **Usar configurações de recorrência**
  7. Faça a configuração desejável de dias e horários para a promoção
 
-![CRON 2 PT](https://images.ctfassets.net/alneenqid6w5/7sn8XLs4lRqMFeWaR77Jqa/ab7e5605b834f8054b84191448cc6240/CRON_2_PT.png)
+![CRON 2 PT](//images.ctfassets.net/alneenqid6w5/7sn8XLs4lRqMFeWaR77Jqa/ab7e5605b834f8054b84191448cc6240/CRON_2_PT.png)
 
diff --git a/docs/announcements/pt/update-of-the-external-privacy-notice.md b/docs/announcements/pt/update-of-the-external-privacy-notice.md
new file mode 100644
index 000000000..acf2cd722
--- /dev/null
+++ b/docs/announcements/pt/update-of-the-external-privacy-notice.md
@@ -0,0 +1,39 @@
+---
+title: 'Atualização do Aviso de Privacidade Externo'
+id: fpUnEC85ixK1vNzXQSrTY
+status: PUBLISHED
+createdAt: 2024-07-02T23:52:09.837Z
+updatedAt: 2024-07-03T14:07:13.062Z
+publishedAt: 2024-07-03T14:07:13.062Z
+contentType: updates
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: atualizacao-do-aviso-de-privacidade-externo
+locale: pt
+legacySlug: atualizacao-do-aviso-de-privacidade-externo
+announcementImageID: ''
+announcementSynopsisPT: 'Atualizamos o Aviso de Privacidade sobre o tratamento de dados pessoais de Shoppers na VTEX.'
+---
+
+Revisamos o [Aviso de Privacidade](https://vtex.com/br-pt/privacy-and-agreements/external-notice/) que explica como a VTEX trata dados pessoais de _Shoppers_, ou seja, indivíduos que acessam os ambientes de ecommerce controlados por lojistas que são os clientes diretos da VTEX.
+
+O documento contém informações sobre os seguintes aspectos:
+
+* Dados pessoais tratados pela VTEX e sua finalidade
+* Período de retenção dos dados
+* Direitos dos titulares dos dados
+* Práticas de proteção dos dados pessoais praticadas pela VTEX
+* Armazenamento de dados pessoais em nuvem
+* Compartilhamento de dados com parceiros
+
+## O que mudou?
+
+A nova versão do Aviso inclui as práticas de privacidade mais recentes da VTEX, voltadas para o tratamento de dados pessoais na Plataforma VTEX, de forma mais clara, resumida e direcionada aos _Shoppers_.
+
+## Por que fizemos essa mudança?
+
+Atualizamos o Aviso de Privacidade em alinhamento com legislações e com nossas certificações globais de privacidade, que recomendam atualizações periódicas. Além disso, separamos em documentos específicos as políticas de privacidade direcionadas a candidatos a vagas de emprego, funcionários e eventos.
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. O documento já está disponível em todos os idiomas no site da VTEX. Para mais informações, você pode acessar o novo aviso em [Aviso de Privacidade Externo](https://vtex.com/br-pt/privacy-and-agreements/external-notice/) e o guia de primeiros passos [Dados e privacidade](https://help.vtex.com/pt/tracks/dados-e-privacidade--4Lc0i0an0DgnEtB0AUwlcq).
diff --git a/docs/announcements/pt/upgrade-your-store-to-google-analytics-4.md b/docs/announcements/pt/upgrade-your-store-to-google-analytics-4.md
index 442399945..873deac69 100644
--- a/docs/announcements/pt/upgrade-your-store-to-google-analytics-4.md
+++ b/docs/announcements/pt/upgrade-your-store-to-google-analytics-4.md
@@ -3,8 +3,8 @@ title: 'Atualize a sua loja para o Google Analytics 4'
 id: 01mmrSck8nvXAKsypecT9V
 status: PUBLISHED
 createdAt: 2023-04-28T14:42:52.792Z
-updatedAt: 2023-05-03T17:47:48.884Z
-publishedAt: 2023-05-03T17:47:48.884Z
+updatedAt: 2023-07-17T13:38:03.472Z
+publishedAt: 2023-07-17T13:38:03.472Z
 contentType: updates
 productTeam: Shopping
 author: 1malnhMX0vPThsaJaZMYm2
@@ -17,21 +17,21 @@ announcementSynopsisPT: 'atualize-a-sua-loja-para-o-google-analytics-4'
 
 A partir de 1º de julho de 2023, o [Google Analytics 4](https://support.google.com/analytics/answer/10089681) (GA4) vai substituir o Universal Analytics, versão anterior da ferramenta de análise de dados do Google. Confira detalhes sobre a mudança [neste comunicado do Google](https://support.google.com/analytics/answer/11583528).
 
-Para continuar rastreando dados sobre a navegação em sua loja VTEX, será necessário criar um registro no GA4 e adaptar algumas configurações na sua loja, se você utilizar o [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) ou o [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
+Para continuar rastreando dados sobre a navegação em sua loja VTEX, será necessário criar um registro no GA4 e adaptar algumas configurações na sua loja, se você utilizar o [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) ou o [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
 
 ## O que mudou?
 O Universal Analytics não irá mais processar eventos a partir do dia 1º de julho de 2023. Portanto, a única versão funcional da ferramenta será o Google Analytics 4.
 
 Para garantir a compatibilidade de lojas VTEX com a nova versão do Google Analytics, você precisa criar um registro no Google Analytics 4 e ajustar as configurações da sua conta no Google Tag Manager, conforme descrito no guia [Configurar Google Analytics 4 em loja VTEX](https://help.vtex.com/pt/tutorial/como-configurar-google-analytics-em-loja-vtex--G2P0rmSrEiqCcmUMyUUwG).
 
-Lojas que utilizam VTEX IO também precisam configurar [o app Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager) para ter a integração com o Google Analytics 4. 
+Lojas que utilizam VTEX IO - Store Framework também precisam configurar [o app Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager) para ter a integração com o Google Analytics 4. 
 
 ## Por que fazer essa mudança?
 
-Essa mudança é necessária para possibilitar que sua loja VTEX que utiliza o [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) ou o [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) continue compatível com o Google Analytics 4. Dessa forma, ainda será possível obter dados relevantes sobre navegação através da versão mais atual da ferramenta do Google.
+Essa mudança é necessária para possibilitar que sua loja VTEX que utiliza o [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) ou o [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) continue compatível com o Google Analytics 4. Dessa forma, ainda será possível obter dados relevantes sobre navegação através da versão mais atual da ferramenta do Google.
 
 ## O que precisa ser feito?
 
 Para tornar a sua loja compatível com a nova versão da ferramenta de análise de dados do Google, siga as instruções do guia [Configurar Google Analytics 4 em loja VTEX](https://help.vtex.com/pt/tutorial/como-configurar-google-analytics-em-loja-vtex--G2P0rmSrEiqCcmUMyUUwG).
 
-Se a sua loja utiliza [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), será necessário ativar uma configuração no VTEX Admin, `Send events in GA4 format`, e configurar o app para receber atualizações do Google Analytics 4. Para mais informações, acesse o guia [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+Se a sua loja utiliza [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), será necessário ativar uma configuração no VTEX Admin, `Send events in GA4 format`, e configurar o app para receber atualizações do Google Analytics 4. Para mais informações, acesse o guia [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
diff --git a/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md b/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
index 0e1d574e3..39039a17b 100644
--- a/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
+++ b/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
@@ -33,5 +33,5 @@ A funcionalidade  pode ser utilizada sempre que o lojista desejar que a taxa no
 - Em "Qual o tipo e valor da Taxa?", escolha a opção Taxa Nominal
 - Preencha os itens necessários e clique em salvar
 
-![Nominal tax PT](https://images.ctfassets.net/alneenqid6w5/2TKpj3XiV3ZOULJnsDrZoO/02331539e2325d6b26f9547f48ca8575/Nominal_tax_PT.png)
+![Nominal tax PT](//images.ctfassets.net/alneenqid6w5/2TKpj3XiV3ZOULJnsDrZoO/02331539e2325d6b26f9547f48ca8575/Nominal_tax_PT.png)
 
diff --git a/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md b/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md
index f0d3aa016..2536eeb92 100644
--- a/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md
+++ b/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md
@@ -23,7 +23,7 @@ Para continuarmos refinando essa experiência, incluímos uma validação adicio
 
 Antes era possível que um comprador selecionasse um cartão vencido e realizasse uma compra, que teria seu pagamento negado em seguida. Agora sinalizamos cartões vencidos e impedimos que eles sejam selecionados checkout, para uma experiência de compra mais fluida.
 
-![PT - Expired Cards](https://images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/d9be78a77ef1849dd23b5bb86bd58fc7/PT_-_Expired_Cards.png)
+![PT - Expired Cards](//images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/d9be78a77ef1849dd23b5bb86bd58fc7/PT_-_Expired_Cards.png)
 
 ## Por que realizamos esta mudança?
 
diff --git a/docs/announcements/pt/vtex-insurance-discontinuity.md b/docs/announcements/pt/vtex-insurance-discontinuity.md
new file mode 100644
index 000000000..3dc35bffc
--- /dev/null
+++ b/docs/announcements/pt/vtex-insurance-discontinuity.md
@@ -0,0 +1,30 @@
+---
+title: 'Descontinuidade do VTEX Insurance'
+id: 413Jet3S6F49mmlQzZ7Bev
+status: PUBLISHED
+createdAt: 2024-01-19T19:54:48.085Z
+updatedAt: 2024-01-29T21:49:24.406Z
+publishedAt: 2024-01-29T21:49:24.406Z
+contentType: updates
+productTeam: Others
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: descontinuidade-do-vtex-insurance
+locale: pt
+legacySlug: descontinuidade-do-vtex-insurance
+announcementImageID: ''
+announcementSynopsisPT: 'O VTEX Insurance foi descontinuado como um produto VTEX, mas continuará existindo como Assurant Digital.'
+---
+
+A partir do dia 11/12/2023, o VTEX Insurance foi descontinuado como um produto VTEX, mas suas funcionalidades serão migradas para o Assurant Digital.
+
+O **VTEX Insurance** era um aplicativo que possibilitava o lojista vincular os produtos da loja com ofertas de seguro fornecidas pela seguradora parceira [Assurant](https://www.assurant.com.br/). Essa funcionalidade permitia que sua loja oferecesse seguros personalizados ao seu cliente, oferecendo proteção financeira em caso de falhas ou defeitos do produto ou serviço adquirido. 
+
+# O que mudou?
+
+Não haverá nenhuma alteração contratual ou comercial, já que o contrato era entre os clientes e a Assurant. A principal mudança está relacionada ao suporte que antes era realizado entre os times das duas empresas e agora passa a ser realizado exclusivamente pela Assurant.
+# O que precisa ser feito?
+
+Nenhuma ação é necessária, já que a atualização será aplicada automaticamente em todas as lojas VTEX. Eventuais dúvidas técnicas e problemas relacionados ao produto deverão ser tratadas diretamente com a [Assurant](https://www.assurant.com.br/). 
+
+<div class = "alert alert-warning"> A VTEX não prestará suporte técnico aos clientes.</div>
+
diff --git a/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md b/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
new file mode 100644
index 000000000..bc054cf27
--- /dev/null
+++ b/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
@@ -0,0 +1,37 @@
+---
+title: 'VTEX Intelligent Search: Novo editor visual de Regras de merchandising'
+id: 63xoRkTEoqllK6KKadys51
+status: PUBLISHED
+createdAt: 2024-01-30T13:15:08.893Z
+updatedAt: 2024-01-31T17:00:02.465Z
+publishedAt: 2024-01-31T17:00:02.465Z
+contentType: updates
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-intelligent-search-novo-editor-visual-de-regras-de-merchandising
+locale: pt
+legacySlug: vtex-intelligent-search-novo-editor-visual-de-regras-de-merchandising
+announcementImageID: ''
+announcementSynopsisPT: 'Conheça o editor visual de Regras de merchandising no VTEX Intelligent Search.'
+---
+
+[Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) é a funcionalidade que manipula resultados dentro da busca em lojas que utilizam o [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Esse recurso possibilita oferecer produtos mais relevantes para o cliente e adicionar ou ocultar produtos pré-selecionados pela busca.
+
+Para oferecer uma experiência mais visual, completa e intuitiva, lançamos uma nova opção de editor para criar regras de merchandising.
+
+## O que mudou?
+
+Anteriormente, lojas com [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) contavam exclusivamente com o [editor manual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) de Regras de merchandising. Agora, também é possível optar pelo [novo editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr), que possibilita:
+
+* Visualizar uma prévia de como os resultados de busca aparecerão para os clientes durante a navegação na loja.
+* Reordenar resultados de busca.
+* Fixar um produto nas primeiras posições dos resultados de busca.
+* Analisar as principais informações do produto.
+
+![visual-merch-rules-PT-announcement (1)](//images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/618748bfb039c6a3e757b1655774a8e0/visual-merch-rules-PT-announcement__1_.png)
+
+Ao criar uma regra de merchandising no Admin VTEX em **Storefront > Intelligent Search > Regras de merchandising > Adicionar**, é possível escolher o tipo de editor a ser utilizado. Acesse o guia [Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao) para obter mais informações sobre as diferenças entre o editor manual e o editor visual.
+
+## O que precisa ser feito?
+
+Nenhuma ação é necessária. O novo editor está disponível para todas as lojas que utilizam o [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Consulte o guia [Criar Regra de merchandising - Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr) para mais informações.
diff --git a/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md b/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md
index 50f454f61..a6ce60005 100644
--- a/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md
+++ b/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md
@@ -19,7 +19,7 @@ Desde 13 de março de 2020, as documentações do  VTEX IO e VTEX IO Store Frame
 
 Agora, elas devem ser acessadas através do [**VTEX IO Docs**](https://vtex.io/docs), plataforma de documentação que reúne todos os conteúdos disponíveis sobre ambas soluções. 
 
-![vtex-io-docs](https://images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/3b50ae0f6b3b3252901ad7597f128c2a/vtex-io-docs.png)
+![vtex-io-docs](//images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/3b50ae0f6b3b3252901ad7597f128c2a/vtex-io-docs.png)
 
 ## Por que estamos realizando esta mudança?
 
@@ -33,7 +33,7 @@ A decisão de remover do Help Center as documentações do VTEX IO e VTEX IO Sto
 
 Abrigando nossa [documentação de API](https://developers.vtex.com/reference), [guias](https://developers.vtex.com/docs) voltados para desenvolvedores que trabalham com integrações e customizações e [Release Notes](https://developers.vtex.com/changelog) sincronizados com tudo de novo que acontece no nosso produto, o [**Developer Portal**](https://developers.vtex.com) - antigo Developer Docs do Help Center - oferece em um só lugar todos os recursos necessários para os usuários mais técnicos da VTEX. 
 
-![developer-portal](https://images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/e5bcdea0033bf9dd9ac8b8d2ff120f72/developer-portal.png)
+![developer-portal](//images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/e5bcdea0033bf9dd9ac8b8d2ff120f72/developer-portal.png)
 
 Com o objetivo de melhorar a experiência de desenvolvimento na VTEX, o Developer Portal em breve também contará com as documentações do VTEX IO e VTEX IO Store Framework - hoje disponibilizadas no VTEX IO Docs. 
 
diff --git a/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md b/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md
index 1e644c1db..4fd05bc93 100644
--- a/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md
+++ b/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Existem três novas opções de idioma no Admin da VTEX
 
 O admin da VTEX suporta atualmente diferentes opções de idiomas para atender nossos clientes em todo o mundo. Localizamos o nosso produto para melhorar a sua experiência, não apenas por meio de traduções, mas também a nível cultural, levando em conta as particularidades de cada país.  
 
-![PT new locales](https://images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/c4201ae259f80a1aa0359441ca1c8dff/PT_new_locales.jpg)
+![PT new locales](//images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/c4201ae259f80a1aa0359441ca1c8dff/PT_new_locales.jpg)
 
 ## O que mudou?
 Além do português, inglês, espanhol, italiano, romeno e japonês, a partir de maio de 2021, os usuários da VTEX encontrarão três novas opções de idiomas em nosso Admin: holandês, francês e coreano.   
diff --git a/docs/announcements/pt/vtex-launches-the-new-version-of-instore-vtex-sales-app.md b/docs/announcements/pt/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
index 71142a84f..5e6d63b4a 100644
--- a/docs/announcements/pt/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
+++ b/docs/announcements/pt/vtex-launches-the-new-version-of-instore-vtex-sales-app.md
@@ -29,7 +29,7 @@ O novo menu traz vários benefícios significativos, que destacamos abaixo:
 * **Navegação intuitiva:** organização aprimorada para encontrar rapidamente o que precisa.
 * **Consistência visual:** aparência harmonizada com outras atualizações recentes em nossa plataforma.
 
-<img src="https://images.ctfassets.net/alneenqid6w5/pcXNfExZYZML7AHP57tzz/36a4fd0238f6c0844a533ffdc5750ed7/image.png" alt= “menu-sales-app-pt” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/pcXNfExZYZML7AHP57tzz/36a4fd0238f6c0844a533ffdc5750ed7/image.png" alt= “menu-sales-app-pt” width="35%" height="35%">
 
 ### Área de anúncios
 
@@ -37,13 +37,13 @@ A área de anúncios permite que os lojistas exibam produtos ou resultados de pe
 
 Um dos principais recursos dessa atualização é a opção de os lojistas definirem a área do anúncio como sua página inicial. Isso permite uma experiência de usuário mais personalizada, pois os clientes são imediatamente recebidos com conteúdo selecionado e recomendações de produtos. Saiba mais no artigo [Anúncios do VTEX Sales App](https://help.vtex.com/pt/tutorial/anuncios-do-vtex-sales-app--3UtOFwbwD4muz3p72RBPmC).
 
-<img src="https://images.ctfassets.net/alneenqid6w5/XXJQykcV9p6yNN6Q5mB5u/ad226528000d3cd143de46bd47a7cd12/image.png" alt= “anuncio-sale-app-pt” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/XXJQykcV9p6yNN6Q5mB5u/ad226528000d3cd143de46bd47a7cd12/image.png" alt= “anuncio-sale-app-pt” width="35%" height="35%">
 
 ### Performance de vendas
 
 Performance de vendas permite que o lojista tenha acesso às métricas de vendas de sua loja, tornando possível a comparação de performance entre períodos de venda e desempenho de funcionários. Saiba mais no artigo [VTEX Sales App: Performance de vendas](https://help.vtex.com/pt/tutorial/sales-app-performance-de-vendas--7i4Elt835tatBM6iqZoc56).
 
-<img src="https://images.ctfassets.net/alneenqid6w5/3UWhX6QODOG8pQ6Xi0QXKV/705391db8cbbe18c8c139a1640bc6ba4/image.png" alt= “vendas-da-loja-sales-app-pt” width="35%" height="35%">
+<img src="//images.ctfassets.net/alneenqid6w5/3UWhX6QODOG8pQ6Xi0QXKV/705391db8cbbe18c8c139a1640bc6ba4/image.png" alt= “vendas-da-loja-sales-app-pt” width="35%" height="35%">
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/vtex-marketplace-launches-in-2022.md b/docs/announcements/pt/vtex-marketplace-launches-in-2022.md
index 25a8b51fc..08f0946b7 100644
--- a/docs/announcements/pt/vtex-marketplace-launches-in-2022.md
+++ b/docs/announcements/pt/vtex-marketplace-launches-in-2022.md
@@ -29,7 +29,7 @@ Com nossas novas funcionalidades, marketplaces podem:
 
 Vá além do ecommerce tradicional com as [novidades de Marketplace da VTEX](https://content.vtex.com/pt-br/2022-marketplace-release/?utm_source=announcement&utm_medium=organic&utm_campaign=2022_marketplace_release). 
 
-![capa de blog marketplace 2022](https://images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/a84a5eb1e72967e9365c6334d33ab1c1/capa_de_blog.png)
+![capa de blog marketplace 2022](//images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/a84a5eb1e72967e9365c6334d33ab1c1/capa_de_blog.png)
 
 ## O que estamos lançando?
 
@@ -78,7 +78,7 @@ Saiba mais sobre cada funcionalidade a seguir.
 
 ### Seller Portal 
 
-![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 O Seller Portal é uma edição da plataforma VTEX voltada para [sellers](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#vender-em-marketplace) se conectarem e venderem seus produtos em marketplaces hospedados na VTEX. Com o portal, sellers acessam todas as funcionalidades essenciais para a operação de ecommerce em grandes vitrines, trazendo visibilidade e conversão de vendas.
 
@@ -126,7 +126,7 @@ Para facilitar a entrada de novos sellers no Seller Portal, lançamos também a
 
 ### Gestão de sellers
 
-![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 Lançamos a experiência renovada da página [Gestão de Sellers](https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers-beta--6eEiOISwxuAWJ8w6MtK7iv), onde operadores de marketplace [adicionam sellers](https://help.vtex.com/pt/tutorial/adicionar-seller-beta--6q4G4RNqVENr5YMJyindwL), registram suas respectivas informações e administram o status de cada seller. 
 
@@ -141,7 +141,7 @@ _Esta página segue o novo Design System da VTEX, com um visual mais limpo, mode
 
 ### Gerenciamento de anúncios
 
-![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 A eficiência e atuação estratégica de um seller depende da sua visibilidade sobre o envio dos anúncios ao marketplace, além da identificação e correção de erros durante o envio. Para facilitar esse processo, lançamos a funcionalidade [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/gestao-de-anuncios--7MRb9S78aBdZjFGpbuffpE).
 
diff --git a/docs/announcements/pt/vtex-sales-app-will-no-longer-be-available-for-windows.md b/docs/announcements/pt/vtex-sales-app-will-no-longer-be-available-for-windows.md
new file mode 100644
index 000000000..c5d6098e8
--- /dev/null
+++ b/docs/announcements/pt/vtex-sales-app-will-no-longer-be-available-for-windows.md
@@ -0,0 +1,37 @@
+---
+title: 'VTEX Sales App não estará mais disponível como uma aplicação no Windows'
+id: 1wcqeNs1AyppGdu20FjAJ8
+status: PUBLISHED
+createdAt: 2023-08-02T15:12:02.978Z
+updatedAt: 2023-08-03T16:00:53.203Z
+publishedAt: 2023-08-03T16:00:53.203Z
+contentType: updates
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-sales-app-nao-estara-mais-disponivel-no-windows
+locale: pt
+legacySlug: vtex-sales-app-nao-estara-mais-disponivel-no-windows
+announcementImageID: ''
+announcementSynopsisPT: 'O VTEX Sales App não terá mais suporte como app nativo no Windows. Estará disponível apenas na interface web.'
+---
+
+Como parte contínua de nossos esforços para melhorar a experiência do usuário, estamos anunciando a deprecação da aplicação VTEX Sales App no Windows.
+
+## O que mudou?
+
+A partir do dia 31/10/23 o aplicativo do VTEX Sales App não estará disponível para o Windows. 
+
+## O que precisa ser feito?
+
+A atualização será aplicada automaticamente em todas as lojas VTEX que utilizam o VTEX Sales App. Para acessá-lo de um computador Windows, ou qualquer sistema operacional, será preciso acessar a versão web do VTEX Sales App, utilizando a seguinte URL:
+
+```
+https://{nome da conta}.myvtex.com/assisted-sales/sales-app
+```
+
+Para mais informações sobre o VTEX Sales App, consulte a nossa documentação:
+
+* [VTEX Sales App - Primeiros passos e configurações](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc#)
+* [VTEX Sales App - Pagamentos](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy#)
+* [VTEX Sales App - Usando o app](https://help.vtex.com/pt/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr#)
+* [Estratégias de Comércio Unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv#)
diff --git a/docs/announcements/pt/web-page-performance-deprecation.md b/docs/announcements/pt/web-page-performance-deprecation.md
new file mode 100644
index 000000000..6dc18d767
--- /dev/null
+++ b/docs/announcements/pt/web-page-performance-deprecation.md
@@ -0,0 +1,24 @@
+---
+title: 'Descontinuação do módulo Performance de Páginas Web'
+id: 4zrnpCSC8R8OFpahiaf2sE
+status: PUBLISHED
+createdAt: 2024-05-29T17:50:25.024Z
+updatedAt: 2024-05-29T19:04:53.248Z
+publishedAt: 2024-05-29T19:04:53.248Z
+contentType: updates
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: descontinuacao-performance-de-paginas-web
+locale: pt
+legacySlug: descontinuacao-do-modulo-performance-de-paginas-web
+announcementImageID: ''
+announcementSynopsisPT: 'O módulo Performance de Páginas Web será descontinuada.'
+---
+
+No dia **04 de junho de 2024,** desabilitaremos o __módulo Performance de Páginas Web__ do Admin VTEX. O módulo permitia ao lojista monitorar as métricas de desempenho das URLs de seu ecommerce apresentadas pelo [PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about) diretamente na plataforma VTEX.
+
+A partir de agora o lojista poderá fazer o [monitoramento e otimização](https://developers.google.com/speed?hl=pt-br) dessas métricas pelo site [PageSpeed Insights](https://pagespeed.web.dev/).
+
+## O que precisa ser feito?
+
+Nesta descontinuação, o lojista não precisa executar nenhuma ação. No Admin VTEX continuará disponível os módulos [Visão geral da loja](https://help.vtex.com/pt/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ) e o [Performance de vendas](https://help.vtex.com/pt/tutorial/performance-de-vendas--3DMube0sEsK9vPcRYGas72).
diff --git a/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
index ec7e449d5..5947c678b 100644
--- a/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
@@ -19,7 +19,7 @@ As empresas digitais têm buscado cada vez mais ferramentas que permitam que ela
 
 Dê as boas-vindas à [experiência do novo Admin](https://content.vtex.com/join-new-admin-beta-program-pt/?utm_source=announcement&utm_medium=organic&utm_campaign=new_admin_beta).
 
-![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/weve-released-our-new-cross-selling-and-up-selling-apis.md b/docs/announcements/pt/weve-released-our-new-cross-selling-and-up-selling-apis.md
index c968c3d9a..9f4234791 100644
--- a/docs/announcements/pt/weve-released-our-new-cross-selling-and-up-selling-apis.md
+++ b/docs/announcements/pt/weve-released-our-new-cross-selling-and-up-selling-apis.md
@@ -3,8 +3,8 @@ title: 'Lançamos nossas novas APIs de Cross-selling e Up-selling'
 id: 37Lc6sI2owMCiUamocgAcc
 status: PUBLISHED
 createdAt: 2017-12-04T18:54:28.850Z
-updatedAt: 2020-05-11T19:43:09.938Z
-publishedAt: 2020-05-11T19:43:09.938Z
+updatedAt: 2024-01-04T15:05:24.804Z
+publishedAt: 2024-01-04T15:05:24.804Z
 contentType: updates
 productTeam: Marketing & Merchandising
 author: 245tA425AIeioKAk2eaiwS
@@ -73,6 +73,6 @@ Esta API vai retornar os produtos que também foram cadastrados como __sugestõe
 
 ## Saiba mais
 
-Para saber mais detalhes sobre as chamadas, acesse nossa [documentação de APIs](https://developers.vtex.com/reference/crossselling#productsearchwhosawalsosaw).
+Para saber mais detalhes sobre as chamadas, acesse nossa [documentação de APIs](https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/products/crossselling/whosawalsosaw/-productId-?endpoint=get-/api/catalog_system/pub/products/crossselling/whosawalsosaw/-productId-).
 
 Para mais informações sobre as modalidades de Cross-selling e Up-Selling descritas acima, acesse o [artigo do VTEX Help](/pt/tutorial/configurando-produto-similar-sugestoes-acessorios-e-genericos)
diff --git a/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md b/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md
index c6fd3a2f6..5ce29a06c 100644
--- a/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md
+++ b/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md
@@ -24,7 +24,7 @@ O aplicativo está disponível na [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Inclusão de um ícone de coração ao lado de cada produto nas listas de produtos e nas páginas de detalhamento do produto;
 - Criação de uma página para a Lista de Desejos, onde o comprador consegue ver todos os itens e facilmente comprá-los.
 
-![Wishlist Printscreen](https://images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
+![Wishlist Printscreen](//images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
 
 ## Quais os benefícios?
 - Torna a experiência de compra da sua loja mais completa;
diff --git a/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 60df2c039..11586ee1a 100644
--- a/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -21,7 +21,7 @@ A partir do dia 25 de junho de 2019, o usuário que não tiver acesso vinculado
 
 Buscando garantir maior segurança, criamos a possibilidade de limitar perfis de acesso a tela de **Configurações** do módulo Gerenciamento de Pedidos, permitindo que somente alguns usuários editem as informações.
 
-![2019-06-07 17 23 36-Configurações.pt](https://images.ctfassets.net/alneenqid6w5/45magq14vJ6nY1opKENj62/f7f22017b6c4fb359d5d0a0211669401/2019-06-07_17_23_36-Configura____es.pt.png)
+![2019-06-07 17 23 36-Configurações.pt](//images.ctfassets.net/alneenqid6w5/45magq14vJ6nY1opKENj62/f7f22017b6c4fb359d5d0a0211669401/2019-06-07_17_23_36-Configura____es.pt.png)
 
 ## Principais Vantagens
 
@@ -41,7 +41,7 @@ Para fazer isso é necessário adicionar um produto chamado `Checkout` ao perfil
  6. Escolha o tipo de permissão desejada: `Save Order Configuration`, para permitir que o usuário edite e salve modificações na seção de **Pedidos**, ou `Save OrderForm Configuration`, para permitir a edição na seção de **Carrinho**.
  7. Clique em **Salvar**
 
-![GIT-Checkout.pt](https://images.ctfassets.net/alneenqid6w5/4nqdHOVWcKnMNdMjLqJhtF/9d285f0e1d5c4f6f3277cbce6f73cfb3/GIT-Checkout.pt.gif)
+![GIT-Checkout.pt](//images.ctfassets.net/alneenqid6w5/4nqdHOVWcKnMNdMjLqJhtF/9d285f0e1d5c4f6f3277cbce6f73cfb3/GIT-Checkout.pt.gif)
 
 Após adicionar este novo produto a um perfil, certifique-se de que os usuários desejados estão associados a este perfil de acesso.
   
diff --git a/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
index e3ba3e98a..f14e8a3fd 100644
--- a/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -26,15 +26,15 @@ To do that, we will show you how to remove the customizations using a Chrome nat
 
 1. To open DevTools, open Chrome and click **F12** or **right-click** anywhere on the page and select **Inspect**.
 
-![Customizations1](https://images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
+![Customizations1](//images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
 
 2. Search for the **Request Blocking** function to block all customizations made via CSS, JavaScript, and Google Tag Manager. Click on the three vertical dots on the top right of the page, as indicated in the image below. Select **More Tools** and then **Request Blocking**.
 
-![Customizations2](https://images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
+![Customizations2](//images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
 
 3. A box will be displayed, as in the image below:
 
-![Customizations3](https://images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
+![Customizations3](//images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
 
 4. Click on the **Request Blocking** tab.
 
@@ -49,7 +49,7 @@ Now you will determine the features you want to block. This configuration must b
 
 The box will finally be displayed as in the image below:
 
-![Customizations4](https://images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
+![Customizations4](//images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
 
 Please remember that this configuration must be done only __once__.
 
@@ -59,11 +59,11 @@ Please remember that this configuration must be done only __once__.
 
 2. This configuration will be set by default, with all options for blocking enabled.
 
-![Customizations5](https://images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
+![Customizations5](//images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
 
 3. Now refresh the page by clicking on **F5**. The page will be displayed without custom components.
 
-![Customizations6](https://images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
+![Customizations6](//images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
 
 4. To view customizations again, deselect the checkbox **Enable request blocking** and refresh the page.
 
diff --git a/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
index 5c1249dd1..00820554c 100644
--- a/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -30,7 +30,7 @@ For this reason, to access the change seller feature, you must configure the aff
 - __Use Payment Processor Recommended Behavior__.
 - __Disabled: Do Not Auto Settle__.
 
-![AutoSettlement](https://images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/a085c82de3cd5dfac48f16deeb7c4cdd/AutoSettlement.png)
+![AutoSettlement](//images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/a085c82de3cd5dfac48f16deeb7c4cdd/AutoSettlement.png)
 
 ### If I opted for a non-automatic settlement behavior, when will the payment be settled?
 
diff --git a/docs/faq/en/fix-redirect-error-in-pagseguro.md b/docs/faq/en/fix-redirect-error-in-pagseguro.md
index 1d1731bf8..2df023ffd 100644
--- a/docs/faq/en/fix-redirect-error-in-pagseguro.md
+++ b/docs/faq/en/fix-redirect-error-in-pagseguro.md
@@ -3,8 +3,8 @@ title: 'Fix redirect error in PagSeguro'
 id: 5b1lVDQ9HUKQs4Wy24uWq2
 status: PUBLISHED
 createdAt: 2018-02-15T16:07:47.669Z
-updatedAt: 2019-12-31T14:23:59.281Z
-publishedAt: 2019-12-31T14:23:59.281Z
+updatedAt: 2024-02-16T12:41:04.461Z
+publishedAt: 2024-02-16T12:41:04.461Z
 firstPublishedAt: 2018-02-15T17:26:16.189Z
 contentType: frequentlyAskedQuestion
 productTeam: Financial
@@ -14,6 +14,8 @@ locale: en
 legacySlug: fix-redirect-error-in-pagseguro
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 If you are having "redirect problems" using PagSeguro, it's likely that PagSeguro's *redirect* is configured incorrectly.
 
 To fix the problem, there are two options: Set the PagSeguro *with redirect* in the correct way or configure the PagSeguro *without redirect*.
@@ -22,16 +24,12 @@ To fix the problem, there are two options: Set the PagSeguro *with redirect* in
 
 ### Configuring Gateway Affiliation PagSeguro
 
-1. Access the __Payments__ section.
-2. Click the __Settings__ button.
-3. Click on the tab __Gateway Affiliations__.
-4. Click the __+__ button in the upper right corner of the screen.
-5. Click the __PagSeguro__ affiliation.
-6. Fill in the __email__ and __token__ fields with the information provided by PagSeguro.
-
-In your PagSeguro account, you must activate "Redirect with transaction code" (My Account > Integrations > Redirection Page). The requested parameter name must be `psTransactionId`.
-
-After that, click __Save__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagSeguro__ in the search bar and click on the name of the provider.
+4. Fill in the __email__ and __token__ fields with the information provided by PagSeguro.
+5. Follow the  __Configuração do redirecionamento__ guidance outlined in the configuration panel.
+6. Click `Save`.
 
 ### Setting up PagSeguro Payment Condition
 
diff --git a/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md b/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md
index 186544234..576e7eef2 100644
--- a/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md
+++ b/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md
@@ -23,5 +23,5 @@ NSU and TID are payment data that remain stored in the __Payment__ module, in th
 
 This information is notified to VTEX during the transactions and organized for a simple view in **+ Information** in the [details of the order](/en/tutorial/how-to-view-the-orders-details), as illustrated below:
 
-![mais-informações-detalhes-pedido en](https://images.ctfassets.net/alneenqid6w5/3ncJnNqpXeGWmlhalll0Ck/507f1008c7121f7722f3d694faddc94b/mais-informa____es-detalhes-pedido_en.png)
+![mais-informações-detalhes-pedido en](//images.ctfassets.net/alneenqid6w5/3ncJnNqpXeGWmlhalll0Ck/507f1008c7121f7722f3d694faddc94b/mais-informa____es-detalhes-pedido_en.png)
 
diff --git a/docs/faq/en/how-does-vtex-support-work.md b/docs/faq/en/how-does-vtex-support-work.md
index a8bf7aed1..efadfeb91 100644
--- a/docs/faq/en/how-does-vtex-support-work.md
+++ b/docs/faq/en/how-does-vtex-support-work.md
@@ -3,8 +3,8 @@ title: 'How does VTEX support work?'
 id: 3kACEfni4m8Yxa1vnf2ebe
 status: PUBLISHED
 createdAt: 2019-03-10T19:06:12.818Z
-updatedAt: 2022-12-23T15:50:55.141Z
-publishedAt: 2022-12-23T15:50:55.141Z
+updatedAt: 2024-01-08T19:15:40.782Z
+publishedAt: 2024-01-08T19:15:40.782Z
 firstPublishedAt: 2019-03-10T19:08:36.723Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -35,7 +35,7 @@ To better serve global customers in different countries, our Customer Excellence
 - Asia-Pacific (APAC)
 - [Brazil](/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)
 - [United States (USA)](/en/faq/vtex-support-united-states--Bm45YFp68QRe1Z5r2oa07)
-- Europe, Middle East and Africa (EMEA)
+- [Europe, Middle East and Africa (EMEA)](https://help.vtex.com/en/faq/vtex-support-emea--5ePu2qkCfmE0IEKDFKg53F?&utm_source=autocomplete)
 - Latin America (LATAM, ex. Brasil)
 
 ### Satisfaction Survey
@@ -48,15 +48,11 @@ To access it, go to **Account settings** and click on **Satisfaction survey**.
 
 ### Real-time Monitoring
 
-We value transparency regarding the integrity of our systems. Thus, whenever there is a critical problem that can affect store sales or the functioning of the platform, we will establish a proactive communication with clients and partners through the following three channels:  
-
-- The [Healthcheck](http://healthcheck.vtex.com/) dashboard shows modules responsible for monitoring each VTEX service in real time. We display a functioning indicator for each module and the time it was last updated, warning when a resource is unavailable or not functioning properly. 
+We value transparency regarding the integrity of our systems. Thus, whenever there is a critical problem that can affect store sales or the functioning of the platform, we will establish a proactive communication with clients and partners through the following channels:  
 
 - The [Status](https://status.vtex.com/) page displays a timeline with the recent system incidents history. Detailed information on each incident is available, such as what happened, which modules were affected, the sequence of actions taken towards solving the problem, and in the end, a summary of the issue. 
 
-- The [Releases](https://releases.vtex.com/) page displays a timeline, detailed per module and version, with all updates made in stable and beta environments. 
-
-We will take all necessary measures to solve any issue as soon as possible and fulfill our [SLA](https://help.vtex.com/en/tutorial/o-que-e-o-sla-de-operacao-da-plataforma--2cIFrsY5S8usk84OU4QOKm?locale=pt) under contract.
+We will take all necessary measures to solve any issue as soon as possible and fulfill our [SLA](https://help.vtex.com/en/tutorial/o-que-e-o-sla-de-operacao-da-plataforma--2cIFrsY5S8usk84OU4QOKm) under contract.
 
 ### Help Center
 
@@ -70,10 +66,7 @@ The [developer portal](https://developers.vtex.com) contains all the documentati
 
 Our admin panel contains a product update communications channel, which highlights our latest functionalities and releases, in addition to any necessary action to avoid downtime. These announcements are also available in the Help Center [News](https://help.vtex.com/en/announcements) section. 
 
-Technical updates focused on developers and partners, including APIs updates, new development guides and VTEX IO announcements, are published in the Developer Portal [Release Notes](https://developers.vtex.com/changelog) section.  
+Technical updates focused on developers and partners, including APIs updates, new development guides and VTEX IO announcements, are published in the Developer Portal [Release Notes](https://developers.vtex.com/updates/release-notes) section.  
 
 Releases that are highly relevant to the market, such as new products, impactful new resources for existing products and company updates, are published on the [Blog](https://vtex.com/pt-br/category/produto/) and in the product's monthly newsletter.  
 
-## Additional services on demand
-
-For situations in which our clients need greater support for more complex projects, we offer project consulting services. If you are interested, your Customer Success Manager can guide you through all the available options and forward this request internally to the responsible teams.
diff --git a/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md b/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md
index 421498545..9e6454088 100644
--- a/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md
+++ b/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md
@@ -31,7 +31,7 @@ Check below how to perform this process:
 4. Proceed to the __What are the conditions for the benefit to be valid?__ section.
 5. Enter the coupon code in __utm_source__.
 
-  ![Sincronizar promoções no mesmo cupom - 1 - EN](https://images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/8393ce300e19c709d554f7794ce06a43/7yJhwPnclx3tCiJdgpcYyv_-_EN.png)
+  ![Sincronizar promoções no mesmo cupom - 1 - EN](//images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/8393ce300e19c709d554f7794ce06a43/7yJhwPnclx3tCiJdgpcYyv_-_EN.png)
 
 6. Click 'Create coupon from UTMs above'.
 7. Click 'Save'.
@@ -39,6 +39,6 @@ Check below how to perform this process:
 9. Repeat the process with the second regular promotion.
 10. In the end, both promotions must present the same UTM.
 
-  ![Sincronizar promoções no mesmo cupom - 2 - EN](https://images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/491e1a1df904baa955571eed701be5f5/5nhdQy1Y4YWs4pHHokSA44_-_EN.png)
+  ![Sincronizar promoções no mesmo cupom - 2 - EN](//images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/491e1a1df904baa955571eed701be5f5/5nhdQy1Y4YWs4pHHokSA44_-_EN.png)
 
 With this, the customer can get a full discount of both values before closing the purchase.
diff --git a/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md b/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md
index cbba8a074..bfe907e92 100644
--- a/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md
+++ b/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md
@@ -19,11 +19,11 @@ Editing the fields that appear as mandatory in __Profile System__ in __Master Da
 1. In the admin menu, select the __Master Data__ module.
 2. Make sure that you're in the __Applications__ tab, in __Quick Links__.
 3. Click on settings in __Profile System__.
-![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
+![MasterDataTutorial 1 UM](//images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
 4. Click on the __pencil__ next to the item you wish to configure.
-![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
+![MasterDataTutorial2](//images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
 5. Click on __Layout Outlines__.
 6. In __Section 1__, choose the item of the field you wish to configure.
-7. In __Advanced field settings, select __Mandatory Field__ on the form. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
+7. In __Advanced field settings, select __Mandatory Field__ on the form. ![MasterDataTutorial3](//images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
 The option may be changed whenever it may be necessary. 
 
diff --git a/docs/faq/en/i-dont-recognize-the-reservation-id-of-an-order.md b/docs/faq/en/i-dont-recognize-the-reservation-id-of-an-order.md
index c55ed7e86..55bf21421 100644
--- a/docs/faq/en/i-dont-recognize-the-reservation-id-of-an-order.md
+++ b/docs/faq/en/i-dont-recognize-the-reservation-id-of-an-order.md
@@ -3,8 +3,8 @@ title: "I don't recognize the reservation ID of an order. What's happened?"
 id: tja793G4XAWI2K8uIC4uW
 status: PUBLISHED
 createdAt: 2018-03-05T21:07:36.301Z
-updatedAt: 2023-03-22T20:28:58.311Z
-publishedAt: 2023-03-22T20:28:58.311Z
+updatedAt: 2024-02-05T18:01:17.750Z
+publishedAt: 2024-02-05T18:01:17.750Z
 firstPublishedAt: 2018-03-05T22:28:55.349Z
 contentType: frequentlyAskedQuestion
 productTeam: Channels
@@ -18,4 +18,4 @@ This might be happening because the orders you are viewing have not yet entered
 
 When this happens, you may contact the marketplace or wait a bit longer to verify if the order information was updated. If it did not entered the in Integrations tool, it might have been canceled or failed to be created.
 
-If you prefer, check your order reservation information via [API](https://developers.vtex.com/reference/reservations#createreservation).
+If you prefer, check your order reservation information via Logistics API, using the [List reservation by ID](https://developers.vtex.com/docs/api-reference/logistics-api?endpoint=get-/api/logistics/pvt/inventory/reservations/-reservationId-) endpoint.
diff --git a/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 2d1c55776..3e26f8b5b 100644
--- a/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -31,6 +31,6 @@ For manual inclusion of specific SKUs, follow these step-by-step instructions:
 5. Name your Collection (the other fields are not to be filled).
 6. Insert the SKUs in the field and __separate them with commas__.
 
-![recurrence-specific-skus](https://images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
+![recurrence-specific-skus](//images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
 
 Finally, give a name to the __Group__ of your Collection and click __Save Group__.
diff --git a/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md b/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md
index b8a4dfae4..11d2eec37 100644
--- a/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md
+++ b/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md
@@ -32,7 +32,7 @@ __Fill in the Label field__
 4. Go to the __Images__ tab;
 5. Enter a term to populate the __Label__;
 
-  ![Kit Look - Label - EN](https://images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/2789e7a69d5258c78d192a47ecc2aff5/7FR879Lzl3eEDmAHiBV0TV_en.jpg)
+  ![Kit Look - Label - EN](//images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/2789e7a69d5258c78d192a47ecc2aff5/7FR879Lzl3eEDmAHiBV0TV_en.jpg)
 
 6. Click __Save__.
 
diff --git a/docs/faq/en/my-admin-is-blocked-what-do-i-do.md b/docs/faq/en/my-admin-is-blocked-what-do-i-do.md
index 3eddb57c4..162d7b42f 100644
--- a/docs/faq/en/my-admin-is-blocked-what-do-i-do.md
+++ b/docs/faq/en/my-admin-is-blocked-what-do-i-do.md
@@ -3,8 +3,8 @@ title: 'My Admin is blocked. What do I do?'
 id: 4IkFRmDVx6quIIcwoOGY6K
 status: PUBLISHED
 createdAt: 2017-10-11T13:36:13.665Z
-updatedAt: 2021-03-22T20:31:43.767Z
-publishedAt: 2021-03-22T20:31:43.767Z
+updatedAt: 2023-07-24T15:11:04.222Z
+publishedAt: 2023-07-24T15:11:04.222Z
 firstPublishedAt: 2017-10-11T13:39:18.676Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -22,9 +22,8 @@ While waiting for the Finance team to contact you, you can temporarily unlock th
 
 Follow the steps below in order to unlock your Admin for this period of time. You must have the permissions of Admin Super or [Financial Role](https://help.vtex.com/en/tutorial/como-criar-um-perfil-de-acesso-financeiro--717qPtxW3Cy9n5KrReHeVv?locale=en) to perform the following actions:
 
-- Access the Invoices module.
-- Click **Check how to temporarily unlock**.
-- Enter the ticket number you previously opened to unlock.
-- Click the **Unlock for 48 hours** button.
+1. Access the Invoices module.
+2. Click **Check how to temporarily unlock**.
+3. Enter the ticket number you previously opened to unlock.
+4. Click the **Unlock for 48 hours** button.
 
-![Home](https://images.ctfassets.net/alneenqid6w5/47nqpufLpGtuGZKFS9hUj2/45133349a94313f29910f94f40c7f860/Home.gif)
diff --git a/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
new file mode 100644
index 000000000..defdddbda
--- /dev/null
+++ b/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -0,0 +1,30 @@
+---
+title: 'Order is locked in "Ready for Handling", what should I do?'
+id: frequentlyAskedQuestions_771
+status: PUBLISHED
+createdAt: 2017-04-27T22:27:37.057Z
+updatedAt: 2023-06-15T13:20:25.568Z
+publishedAt: 2023-06-15T13:20:25.568Z
+firstPublishedAt: 2017-04-27T23:02:34.947Z
+contentType: frequentlyAskedQuestion
+productTeam: Post-purchase
+author: authors_84
+slug: order-is-locked-in-ready-for-handling-what-should-i-do
+locale: en
+legacySlug: order-is-locked-in-pronto-para-manuseio-what-do-i-do
+---
+
+When a store has an order locked in the status **Ready for Handling**, it means that the ERP has to advise that it has consulted the order and has begun handling it.
+
+This happens because within the flow of orders there is a status in which the orders have to be queried by the ERP - this is the **Ready for Handling** status.
+
+When the ERP queries and enters this order in your base, it has to inform VTEX that the order can continue its flow. This can be done in two ways:
+
+- [ERP advises using API](https://developers.vtex.com/vtex-rest-api/reference/starthandling): this is the most common way of updating.
+- **Storeowner advances manually**: the store has no ERP and has to advance the order manually in VTEX Admin, in the [Order details page](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). The complete steps are described in [Moving order to Handling Shipping](https://help.vtex.com/en/tutorial/passar-pedido-para-o-status-preparando-entrega--tutorials_198).
+
+> You must have a [OMS - Full access role](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") to be able to perform this action.
+
+<div class="alert alert-warning">
+<p>If the order is moved manually from the <b>Start handling</b> status, it will not be possible to move the order down to the ERP afterwards.</p>
+</div>
diff --git a/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md b/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md
index 731a64b8d..a29c22c50 100644
--- a/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md
+++ b/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md
@@ -18,7 +18,7 @@ In __Gateway Affiliation__, you can view the list of all settings made. However,
 
 This means that these affiliations are not enabled, but being tested. You may confirm this information by clicking on the affiliation highlighted. 
 
-![afiliação-gateway-teste en](https://images.ctfassets.net/alneenqid6w5/4o2BXZ5q9iyQqyO064sSwm/b0f8f391add763acdad6a91686bcd730/gateway_teste_en.png)
+![afiliação-gateway-teste en](//images.ctfassets.net/alneenqid6w5/4o2BXZ5q9iyQqyO064sSwm/b0f8f391add763acdad6a91686bcd730/gateway_teste_en.png)
 
 
 That is, the settings that have not yet been enabled are highlighted in a different color.
diff --git a/docs/faq/en/understanding-vtex-email-capture-system.md b/docs/faq/en/understanding-vtex-email-capture-system.md
index 17f72c5ed..d092ebb92 100644
--- a/docs/faq/en/understanding-vtex-email-capture-system.md
+++ b/docs/faq/en/understanding-vtex-email-capture-system.md
@@ -50,5 +50,5 @@ So that the <a href="https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandon
 Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
 </div>
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/faq/en/vtex-support-brazil.md b/docs/faq/en/vtex-support-brazil.md
index 55cc374d6..21bc7853d 100644
--- a/docs/faq/en/vtex-support-brazil.md
+++ b/docs/faq/en/vtex-support-brazil.md
@@ -3,8 +3,8 @@ title: 'VTEX Support - Brazil'
 id: 5q861sTw1n7H2BENOu7ls9
 status: PUBLISHED
 createdAt: 2021-03-02T00:59:46.352Z
-updatedAt: 2022-12-23T15:47:00.476Z
-publishedAt: 2022-12-23T15:47:00.476Z
+updatedAt: 2024-05-23T16:25:31.311Z
+publishedAt: 2024-05-23T16:25:31.311Z
 firstPublishedAt: 2021-03-02T01:09:50.358Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
diff --git a/docs/faq/en/vtex-support-emea.md b/docs/faq/en/vtex-support-emea.md
new file mode 100644
index 000000000..140086d00
--- /dev/null
+++ b/docs/faq/en/vtex-support-emea.md
@@ -0,0 +1,227 @@
+---
+title: 'VTEX Support - EMEA'
+id: 5ePu2qkCfmE0IEKDFKg53F
+status: PUBLISHED
+createdAt: 2023-11-09T16:29:55.255Z
+updatedAt: 2024-05-28T02:20:01.805Z
+publishedAt: 2024-05-28T02:20:01.805Z
+firstPublishedAt: 2023-11-09T16:51:03.796Z
+contentType: frequentlyAskedQuestion
+productTeam: Billing
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: vtex-support-emea
+locale: en
+legacySlug: vtex-support-emea
+---
+
+This article presents the availability, SLA, and additional support resources available to customers served by our offices in **Europe, the Middle East, and Africa (EMEA).** For a broader perspective of our global support resources, see: [How does VTEX support work?](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe)
+
+<div class="alert alert-info">If the Support team identifies that a ticket was opened incorrectly, they will recommend the most appropriate resource to use, and this assessment can be made at any time during the resolution process.</div>
+
+## Availability
+
+<div class="overflow-x-auto">
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Priority</th>
+     <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Average first response time</th>
+          <th class=> Average next response time</th>
+           <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Urgent</td>
+      <td class="t-body pa5" style="min-width: 15rem;">1 hour</td>
+      <td class="t-body pa5" style="min-width: 20rem;">2 hours</td>
+      <td class="t-body pa5" style="min-width: 20rem;">
+        <p>Your VTEX store in production is unavailable or completely unusable, with allcustomers or all regions affected.</p>
+        <p><em>Example: VTEX returning error 502.</em></p>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">High</td>
+      <td class="t-body pa5" style="min-width: 15rem;">2 hours</td>
+      <td class="t-body pa5" style="min-width: 20rem;">8 hours</td>
+        <p>Important features of your VTEX store are unavailable or extremely slow, with no viable alternative to overcome the problem.</p>
+        <p><em>Example: A promotion is not being applied or products are not being sent from a
+Seller to a Marketplace.
+</em></p>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Normal</td>
+      <td class="t-body pa5" style="min-width: 15rem;">2 hours</td>
+      <td class="t-body pa5" style="min-width: 20rem;">8 hours</td>
+      <td class="t-body pa5" style="min-width: 20rem;">
+        <p>Important features of your VTEX store are unavailable or slow, but there is a
+viable alternative to overcome the problem.</p>
+        <p><em>Example:  A known issue impacts your use of VTEX, but a workaround is being used as a temporary solution.</em></p>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Low</td>
+      <td class="t-body pa5" style="min-width: 15rem;"> 2 hours</td>
+      <td class="t-body pa5" style="min-width: 20rem;">8 hours</td>
+      <td class="t-body pa5" style="min-width: 20rem;">
+        <p>Calls to the finance team, tasks or questions about features or documentation.</p>
+        <p><em>Example: "Is it possible to configure local holidays on the platform?"</em></p>
+      </td>
+    </tr>
+  </tbody>
+</table>
+</div>
+
+Keep in mind that our first response time calculation is based on working hours. The criteria for ticket urgency are defined in the section below.  
+
+<div class="alert alert-warning">
+Emergency support will be available <b>exclusively</b> for Urgent requests and provided via <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Zendesk tickets</a>. Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in <a href="#ticket-urgency">Ticket Urgency</a>.
+</div>
+
+## Ticket urgency
+
+Urgent tickets report critical problems that have a direct impact on sales. The table below lists the scenarios we consider when classifying ticket urgency.
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <thead>
+        <tr class="bb b--muted-3">
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Scenario</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">VTEX Platform Unavailable</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Storefront or Admin completely down</li>
+                <li>Open incident in our <a href="https://status.vtex.com" target="_blank">status page</a></li>
+              </ul>
+            </td>
+        </tr>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">Checkout Unavailable</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Shipping calculations preventing orders from being placed</li>
+                <li>Taxes not being calculated preventing orders from being placed</li>
+                <li>Shopping cart or checkout pages not loading (completely down)</li>
+              </ul>
+            </td>
+        </tr>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">Unable to Fulfill Order</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Orders status isn’t being updated</li>
+                <li>Order feed or hook isn’t working</li>
+              </ul>
+            </td>
+        </tr>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">Store Usability Unavailable</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Unable to add to cart</li>
+                <li>Unable to register on the site</li>
+                <li>Onsite search not responding</li>
+              </ul>
+            </td>
+        </tr>
+    </tbody>
+</table>
+
+## Ticket Priorities
+
+The following table lists the scenarios we consider when ranking ticket priority based on how the ticket forms were filled out.  
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <thead>
+        <tr class="bb b--muted-3">
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Source</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Type</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Users impacted</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Impact</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Priority</th>
+        </tr>
+    </thead>
+    <tr class="bb b--muted-3">
+        <td>Financial
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td rowspan="8" >Technical
+        </td>
+        <td>Question
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>Task
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td rowspan="6" >Incident
+        </td>
+        <td rowspan="3" >Internal
+        </td>
+        <td>Low
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>Moderate
+        </td>
+        <td>Normal
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>High
+        </td>
+        <td>High
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td rowspan="3" >External / All
+        </td>
+        <td>Low
+        </td>
+        <td>Normal
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>Moderate
+        </td>
+        <td>High
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>High
+        </td>
+        <td>Urgent
+        </td>
+    </tr>
+</table>
+
+The priority of a ticket may change over time, based on VTEX's analysis of the impact of the request. You can check the priority of your open requests through the [support panel](https://support.vtex.com/hc/en/requests).
diff --git a/docs/faq/en/website-with-error-how-to-fix-it.md b/docs/faq/en/website-with-error-how-to-fix-it.md
index 6ff2ae979..a90263cce 100644
--- a/docs/faq/en/website-with-error-how-to-fix-it.md
+++ b/docs/faq/en/website-with-error-how-to-fix-it.md
@@ -23,7 +23,7 @@ However, if it's yellow, it means there is an error.
 Below are the steps to adjust it:
 
 1. Click on the website.
-2. Select the Binding on the screen (line highlighted in the image below), and click on __Update__.![Binding 1](https://images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
+2. Select the Binding on the screen (line highlighted in the image below), and click on __Update__.![Binding 1](//images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
 3. On the screen displayed, the __Store name from License Manager__ field will be blank; click on the arrow that appears in this field and select the name of your store.
-4. Click on __Save Binding__.![Binding 2](https://images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
+4. Click on __Save Binding__.![Binding 2](//images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
 5. Click on __Websites__ again to update the page, and that’s it! The little globe will appear in blue, which means that now this is right.
diff --git a/docs/faq/en/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md b/docs/faq/en/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
index 596bdb4d4..022c5d5b9 100644
--- a/docs/faq/en/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
+++ b/docs/faq/en/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'What to do when an unexpected error message appears while selecting PayPal Plus at checkout'
 id: 2eyMuEf6wsWuOgrjo7tzQH
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-03-18T14:01:50.694Z
-updatedAt: 2019-12-31T14:24:40.864Z
-publishedAt: 2019-12-31T14:24:40.864Z
+updatedAt: 2024-02-19T17:41:00.925Z
+publishedAt: 
 firstPublishedAt: 2019-03-18T14:10:08.064Z
 contentType: frequentlyAskedQuestion
 productTeam: Shopping
diff --git a/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md b/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md
index cdde5d03b..ec7614f6e 100644
--- a/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md
+++ b/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md
@@ -23,8 +23,8 @@ However, there is a way to extract this report manually by accessing Master Data
 Let's see how in the following step-by-step:
 
 1. Enter the __Master Data__;
-2. Click __"Exportations"__;![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
-3. Make sure that the tab currently open is __"Applications"__;![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
+2. Click __"Exportations"__;![3WNNUZ8EgDZ4iYv8e0OyQG](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
+3. Make sure that the tab currently open is __"Applications"__;![7ecXBGaCeC3hTaO0lODPq1](//images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
 4. Under __"Export Status"__, click the report you want to download.
 
 With this, you'll be able access the content even if the original email has not arrived.
diff --git a/docs/faq/en/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md b/docs/faq/en/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
index 7b13822e4..9c055995f 100644
--- a/docs/faq/en/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
+++ b/docs/faq/en/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
@@ -3,8 +3,8 @@ title: 'What to do when receiving an error message during shipping simulation'
 id: 3bkJwe0Yj6qEkuYKUWwKwK
 status: PUBLISHED
 createdAt: 2017-05-09T14:03:03.097Z
-updatedAt: 2021-03-22T20:46:27.291Z
-publishedAt: 2021-03-22T20:46:27.291Z
+updatedAt: 2023-10-10T16:20:54.988Z
+publishedAt: 2023-10-10T16:20:54.988Z
 firstPublishedAt: 2017-05-09T14:06:10.341Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -18,7 +18,7 @@ What to do when a shipping simulation does not show the expected result?
 
 Here, we will provide a step-by-step description about how to check the Logistics settings.
 
-Before we start, please remember that the [Shipping Simulation](/en/tutorial/freight-simulation/) will return the result of the [Shipping Calculation](https://developers.vtex.com/reference/logistics-api-overview) API. We recommend always using APIs. If you don’t have access, ask your store administrator and check the role associated with your user.
+Before we start, please remember that the [Shipping Simulation](/en/tutorial/freight-simulation/) will return the result of the [Shipping Calculation](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping/calculate) API. We recommend always using APIs. If you don’t have access, ask your store administrator and check the role associated with your user.
 
 To illustrate this article, let’s consider a scenario where the __X-Box__ product is not being delivered to Postal Code 22451-451 for sales policy 1. The error message is as follows: "_It was not possible to generate the cart. See details below_".
 
@@ -26,7 +26,7 @@ Some factors may influence a simulation; so, we recommend that you always start
 
 Then, we must check Logistics as a whole, that is, which X-Box inventory and which carrier are associated with Sales Policy 1. This information is contained in the Warehouse Dock.
 
-This would also be very simple if you use the API. Through the query [Shipping Calculation](https://developers.vtex.com/reference/logistics-api-overview) it is easy to identify the carrier’s ID and, thus, to go backwards. 
+This would also be very simple if you use the API. Through the query [Shipping Calculation](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping/calculate) it is easy to identify the carrier’s ID and, thus, to go backwards. 
 
 But how can you correct that?
 
diff --git a/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
index 78694cc04..adb7f6a8c 100644
--- a/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -16,7 +16,7 @@ legacySlug: what-to-do-when-the-avise-me-doesnt-show
 
 There is a situation in which, despite having [set up the “Notify me” option](/en/tutorial/set-up-the-avise-me) correctly, it does not appear. This happens **when the category display type is marked as “List of SKUs”.**
 
-![categoria-lista-de-skus EN](https://images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
+![categoria-lista-de-skus EN](//images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
 
 In this case, in addition to the default settings, the use of the `vtex.cmc:SkuSelection` control is required, even if there is only one SKU per page.
 
diff --git a/docs/faq/en/why-are-my-orders-not-integrating-with-mercado-livre.md b/docs/faq/en/why-are-my-orders-not-integrating-with-mercado-livre.md
index 3e02df06e..d876f47d8 100644
--- a/docs/faq/en/why-are-my-orders-not-integrating-with-mercado-livre.md
+++ b/docs/faq/en/why-are-my-orders-not-integrating-with-mercado-livre.md
@@ -21,7 +21,7 @@ In order to do this, the first step is accessing the integration registration:
 1. Access the __Marketplace__ module
 2. Click on __Integration__
 3. Look for the Mercado Livre __panel__
-4. Click on the __gears__ icon <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
+4. Click on the __gears__ icon <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
 5. Click on __Edit config_
 
 From there onwards, you'll need to redo the integration process.
diff --git a/docs/faq/en/why-are-my-store-images-being-displayed-in-poor-quality.md b/docs/faq/en/why-are-my-store-images-being-displayed-in-poor-quality.md
new file mode 100644
index 000000000..a825b25d5
--- /dev/null
+++ b/docs/faq/en/why-are-my-store-images-being-displayed-in-poor-quality.md
@@ -0,0 +1,27 @@
+---
+title: 'Why are my store images being displayed in poor quality?'
+id: 5LxgbF8S2cIUOCaCO00GcK
+status: PUBLISHED
+createdAt: 2018-02-22T19:10:35.567Z
+updatedAt: 2024-04-15T15:07:36.249Z
+publishedAt: 2024-04-15T15:07:36.249Z
+firstPublishedAt: 2018-02-22T22:03:18.347Z
+contentType: frequentlyAskedQuestion
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: why-are-my-store-images-being-displayed-in-poor-quality
+locale: en
+legacySlug: images-with-poor-quality
+---
+
+The reduction in image quality can occur during the automatic [image compression process](https://help.vtex.com/en/tutorial/image-compression--4klbgpsPksq44KcwqKeye8).
+
+If you're using JPG or JPEG photos on your website, it's common for them to lose some quality due to conversion to lossy [WebP](https://developers.google.com/speed/webp/) format. However, this loss shouldn't be too noticeable. To address this, try to upload the files again in a slightly higher resolution.
+
+For your store to display images with solid colors, detailed graphics, and high contrast in your store, we recommend opting for PNG format. PNG is either optimized in the same format or converted to lossless WebP, which should preserve the quality of the original file.
+
+Another option is to use pre-optimized images using conversion tools for progressive JPEG photos or 8-bit PNGs for illustrations. By compressing the file beforehand, there’s a chance the format can be maintained without further recompression.
+
+## Learn more
+
+* [Image compression](https://help.vtex.com/en/tutorial/image-compression--4klbgpsPksq44KcwqKeye8)
diff --git a/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md b/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md
index ad10f0d59..c7c657e27 100644
--- a/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md
+++ b/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md
@@ -26,14 +26,14 @@ Once that field has been located, follow the instructions below:
 
 1. Access the __Catalog__ module
 2. Click on __Categories__
-![ENgrupo1](https://images.ctfassets.net/alneenqid6w5/1FV4cfZ09pHFMm5PQQjh7I/67df4c591f88db3ae47f057ad81b5d49/ENgrupo1.PNG)
+![ENgrupo1](//images.ctfassets.net/alneenqid6w5/1FV4cfZ09pHFMm5PQQjh7I/67df4c591f88db3ae47f057ad81b5d49/ENgrupo1.PNG)
 3. Click on __Actions__
 4. Select __Product Fields__
-![ENSgrupo2](https://images.ctfassets.net/alneenqid6w5/3F6DH1j52N2e1oUBMKoSNf/8d5b1a3644ae4700f1eb99fc065d2464/ENSgrupo2.png)
+![ENSgrupo2](//images.ctfassets.net/alneenqid6w5/3F6DH1j52N2e1oUBMKoSNf/8d5b1a3644ae4700f1eb99fc065d2464/ENSgrupo2.png)
 5. Find the __group__ you wish to make changes to
 6. Click on __Edit__
-![ENgrupo3](https://images.ctfassets.net/alneenqid6w5/4GBCyFv6QYipoaBROwGxbN/0d5050a3e8bd6021e8a6cca3ca8606ad/ENgrupo3.png)
+![ENgrupo3](//images.ctfassets.net/alneenqid6w5/4GBCyFv6QYipoaBROwGxbN/0d5050a3e8bd6021e8a6cca3ca8606ad/ENgrupo3.png)
 7. After performing the required changes, click on __Save__ 
-![ENgrupo4](https://images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
+![ENgrupo4](//images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
 
 Done, fields have been changed! Don't forget to save the settings for the changes to be displayed on your store's front end.
diff --git a/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md b/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md
index f152bb1d9..d1c1084bf 100644
--- a/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md
+++ b/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md
@@ -3,8 +3,8 @@ title: "Why can't I see my carrier on checkout?"
 id: frequentlyAskedQuestions_165
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:09.470Z
-updatedAt: 2023-03-20T20:32:20.572Z
-publishedAt: 2023-03-20T20:32:20.572Z
+updatedAt: 2023-08-25T15:13:42.026Z
+publishedAt: 2023-08-25T15:13:42.026Z
 firstPublishedAt: 2017-04-27T23:01:43.444Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -26,6 +26,10 @@ Carriers should be grouped into categories upon registration, including the [typ
 
 Checkout will always highlight the cheapest/fastest carrier from the options of the same type of delivery. Thus, a carrier will not appear at checkout when another of the same type has a better cost/delivery option registered. 
 
+<div class="alert alert-warning">
+When there is a tie between carriers, the tiebreaker criterion is to have the lowest shipping cost.
+</div>
+
 ### Solution
 
 If you want all carriers to be displayed, you should register these in the **Store Settings > Shipping > Settings** as carriers of _different delivery types_.
diff --git a/docs/faq/en/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md b/docs/faq/en/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
index e8ab22ee7..63c9ae635 100644
--- a/docs/faq/en/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
+++ b/docs/faq/en/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
@@ -3,8 +3,8 @@ title: 'Why did the carrier calculate freight for a weight lower than the minimu
 id: frequentlyAskedQuestions_164
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:17.904Z
-updatedAt: 2019-12-31T14:25:25.374Z
-publishedAt: 2019-12-31T14:25:25.374Z
+updatedAt: 2023-12-19T16:53:24.136Z
+publishedAt: 2023-12-19T16:53:24.136Z
 firstPublishedAt: 2017-04-27T23:01:43.295Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -14,7 +14,7 @@ locale: en
 legacySlug: why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set
 ---
 
-Freight calculation always considers two parameters: product weight and volume. The priority in calculation is always given to the real or cubed weight &#8211; the one with highest value. However, if the weight of a product is lower than the minimum registered for a carrier, volume will be considered.
+Freight calculation always considers two parameters: product weight and volume. The priority in calculation is always given to the minimum weight or cubed weight &#8211; the one with highest value. However, if the weight of a product is lower than the minimum registered for a carrier, volume will be considered.
 
 ## Examples
 
diff --git a/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md b/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md
index a88b7fc35..4d5a932dd 100644
--- a/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md
+++ b/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md
@@ -34,7 +34,7 @@ Make sure the value has been entered by following these steps:
 4. Go to the session __"What are the conditions for the benefit to be valid?"__;!
 5. Check which clusters are registered in __"Customers Cluster"__;
 
-![EN - 7GcSb6BuF6JKnmGAggO3uA](https://images.ctfassets.net/alneenqid6w5/5dIEGqj1MTmtqOvWdIJFh5/0a0656ee4a3c8f7ac084d438c7cdf82d/Cluster-promo-EN.png)
+![EN - 7GcSb6BuF6JKnmGAggO3uA](//images.ctfassets.net/alneenqid6w5/5dIEGqj1MTmtqOvWdIJFh5/0a0656ee4a3c8f7ac084d438c7cdf82d/Cluster-promo-EN.png)
 
 6. Enter the "new data";
 7. Click __Save__;
diff --git a/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md b/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
index 462770d9e..966c0fc39 100644
--- a/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
+++ b/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
@@ -22,7 +22,7 @@ To specify the type of delivery to which you want to apply the benefit, you must
 2. Click on the card of the benefit to which you want to apply the free shipping.
 3. In item 3, activate the __Shipping Method__ flag and specify which ones should receive the free shipping.
 
-![promoções-campo-tipo-frete en](https://images.ctfassets.net/alneenqid6w5/cEe5QqUczQ4MikWAEGkwS/054310fa7cf2bef0d7b02f058f4ddc49/promo____es-campo-tipo-frete_en.png)
+![promoções-campo-tipo-frete en](//images.ctfassets.net/alneenqid6w5/cEe5QqUczQ4MikWAEGkwS/054310fa7cf2bef0d7b02f058f4ddc49/promo____es-campo-tipo-frete_en.png)
 
 Once this has been done, the specified shipping types will enter the promotion and will appear to the customer with free shipping available.
 
diff --git a/docs/faq/en/why-is-let-me-know-not-showing.md b/docs/faq/en/why-is-let-me-know-not-showing.md
index 75a10870d..b260d08e3 100644
--- a/docs/faq/en/why-is-let-me-know-not-showing.md
+++ b/docs/faq/en/why-is-let-me-know-not-showing.md
@@ -21,7 +21,7 @@ The basic settings for displaying **Let me know** when the product is not availa
 
 However, there is a situation in which despite having set up the items above, “Let me know” does not appear. This happens **when the Category display type is marked as “List of SKUs”.**
 
-![categoria-lista-de-skus EN](https://images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
+![categoria-lista-de-skus EN](//images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
 
 In this case, in addition to the default settings, the use of the `vtex.cmc:SkuSelection` control is required, even if there is only one SKU per page.
 
diff --git a/docs/faq/en/why-is-my-freight-value-wrong.md b/docs/faq/en/why-is-my-freight-value-wrong.md
index d0aff7dd0..860ddaaed 100644
--- a/docs/faq/en/why-is-my-freight-value-wrong.md
+++ b/docs/faq/en/why-is-my-freight-value-wrong.md
@@ -23,7 +23,7 @@ Freight calculation is based on several factors: freight table, additional freig
 3. Here, you can see the value registered on the spreadsheet, as well as all [additionals](/en/tutorial/understanding-the-additional-freight) added to this value.
 4. If the value is not consistent with the one displayed at the store, follow the steps below to check if there isn't a sale altering the value of the freight.
 
-![por-que-meu-valor-de-frete-esta-errado en](https://images.ctfassets.net/alneenqid6w5/440sXQOHl6ME0SsyuoEaAA/8ea9d8cd9e2c9bb70509664c7f82eb86/por-que-meu-valor-de-frete-esta-errado_en.jpg)
+![por-que-meu-valor-de-frete-esta-errado en](//images.ctfassets.net/alneenqid6w5/440sXQOHl6ME0SsyuoEaAA/8ea9d8cd9e2c9bb70509664c7f82eb86/por-que-meu-valor-de-frete-esta-errado_en.jpg)
 
 ## Sale
 
@@ -32,4 +32,4 @@ Freight calculation is based on several factors: freight table, additional freig
 3. Observe the box **Total Value** box.
 4. Check if, among sales, there is one offering a freight discount. To check that, simply access the sale and verify the type of discount offered.
 
-![valortotal en](https://images.ctfassets.net/alneenqid6w5/5MBxhrcMi4wMgKCIOWckWg/b767465dc888b24295de98b036e2eefe/valortotal_en.jpg)
+![valortotal en](//images.ctfassets.net/alneenqid6w5/5MBxhrcMi4wMgKCIOWckWg/b767465dc888b24295de98b036e2eefe/valortotal_en.jpg)
diff --git a/docs/faq/en/why-is-my-stock-negative.md b/docs/faq/en/why-is-my-stock-negative.md
index decebe2a1..33cf9e7c9 100644
--- a/docs/faq/en/why-is-my-stock-negative.md
+++ b/docs/faq/en/why-is-my-stock-negative.md
@@ -3,8 +3,8 @@ title: 'Why is my inventory negative?'
 id: frequentlyAskedQuestions_159
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:51.880Z
-updatedAt: 2023-03-22T20:34:48.834Z
-publishedAt: 2023-03-22T20:34:48.834Z
+updatedAt: 2024-04-18T14:18:13.634Z
+publishedAt: 2024-04-18T14:18:13.634Z
 firstPublishedAt: 2017-04-27T23:01:42.612Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
diff --git a/docs/faq/en/why-is-my-stores-zoom-not-working.md b/docs/faq/en/why-is-my-stores-zoom-not-working.md
index c44f71ded..34c2a9545 100644
--- a/docs/faq/en/why-is-my-stores-zoom-not-working.md
+++ b/docs/faq/en/why-is-my-stores-zoom-not-working.md
@@ -25,7 +25,7 @@ This image size can be set up through the following steps:
 2. Enter Settings.
 3. Click __File Types__ tab.
 
-![Tipos de Arquivo EN](https://images.ctfassets.net/alneenqid6w5/3vFG4pv5Wgkcu6GaIEgOAa/17ee2d04db1d1dce4237de9bfaf6cc9e/Tipos_de_Arquivo_EN.png)
+![Tipos de Arquivo EN](//images.ctfassets.net/alneenqid6w5/3vFG4pv5Wgkcu6GaIEgOAa/17ee2d04db1d1dce4237de9bfaf6cc9e/Tipos_de_Arquivo_EN.png)
 
 The 1000x1000 size means that the resulting zoom will display the image in that size. Thus, this is the minimum size for the zoom to work.
 
diff --git a/docs/faq/en/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md b/docs/faq/en/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
index a8f6eecb9..2a4af473f 100644
--- a/docs/faq/en/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
+++ b/docs/faq/en/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
@@ -1,10 +1,10 @@
 ---
 title: 'Why is the origin of the orders different on VTEX and on Google Analytics?'
 id: frequentlyAskedQuestions_5030
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T22:22:57.838Z
-updatedAt: 2019-12-31T14:24:58.529Z
-publishedAt: 2019-12-31T14:24:58.529Z
+updatedAt: 2023-06-21T22:44:36.086Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:02:44.531Z
 contentType: frequentlyAskedQuestion
 productTeam: Identity
diff --git a/docs/faq/en/why-is-the-product-not-visible-on-the-website.md b/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
index a9710a7c2..67e1e804e 100644
--- a/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
@@ -42,7 +42,7 @@ We recommend beginning the investigation with **Catalog**. To check the **Catalo
 1. Access the VTEX Admin and go to **Products > Catalog > Products and SKUs** to check the products listed in your store.
 2. Find the product you want to display in the list, as illustrated below.
 
-    ![01-produto-en](https://images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/8b6bbeb3f736a6e16c77b4b9889c6026/01-produto-en.PNG)
+    ![01-produto-en](//images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/8b6bbeb3f736a6e16c77b4b9889c6026/01-produto-en.PNG)
 
 3. Follow the instructions described in the next sections to check this information:
     * [Product](#product)
@@ -71,9 +71,9 @@ To check the product settings, you must follow the steps below.
     * If the product contains specifications, check the **Specifications** tab to see if they are filled in.
 3. After each change, click `Save`.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/nGAGYNdVtTFdAPjW1mi5f/080a8fbd5815fe8059b449a23c01b944/02-campos-produto-en.png" alt="02-campos-produto-en" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Fields you must check on the product information page.</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/nGAGYNdVtTFdAPjW1mi5f/080a8fbd5815fe8059b449a23c01b944/02-campos-produto-en.png" alt="02-campos-produto-en" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Fields you must check on the product information page.</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/6UXDapFf9bvtnCSoHQBwZC/4870d3860fc73faed98f2237aa85cca9/03-aba-especificacoes-en.png" alt="03-aba-especificacoes-en" style="margin-bottom: 20px;"> <figcaption align = "center"><em><strong>Specifications</strong> tab</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/6UXDapFf9bvtnCSoHQBwZC/4870d3860fc73faed98f2237aa85cca9/03-aba-especificacoes-en.png" alt="03-aba-especificacoes-en" style="margin-bottom: 20px;"> <figcaption align = "center"><em><strong>Specifications</strong> tab</em></figcaption></figure>
 
 ### SKUs
 
@@ -85,16 +85,16 @@ On the SKUs page, in **Products > Catalog > Products and SKUs**, follow the inst
 
     |Button | Description |
     |-|-|
-    | ![04-botao-precos](https://images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Allows you to access the __Price list__ to check if the desired trade policy has a valid price associated with the product SKUs. For more information, check the [Prices](#prices) section. |
-    | ![05-botao-logistica](https://images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Allows you to access the __Inventory management__ page to check if the SKU is available in stock.  For more information, check the [Logistics](#logistics) section. |
-    | ![06-botao-indexed-info](https://images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Allows you to view each **Seller ** selling the SKU, the trade policy (**Policy**), the price (**Value**) and the SKU quantity in inventory (**Quantity**). |
+    | ![04-botao-precos](//images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Allows you to access the __Price list__ to check if the desired trade policy has a valid price associated with the product SKUs. For more information, check the [Prices](#prices) section. |
+    | ![05-botao-logistica](//images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Allows you to access the __Inventory management__ page to check if the SKU is available in stock.  For more information, check the [Logistics](#logistics) section. |
+    | ![06-botao-indexed-info](//images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Allows you to view each **Seller ** selling the SKU, the trade policy (**Policy**), the price (**Value**) and the SKU quantity in inventory (**Quantity**). |
 
 2. On the row displaying the product with the SKU you want to verify, click the down arrow <i class="fas fa-caret-down"></i>, next to the `Update` button.
 3. Click the **SKU** option to access the SKUs detailed list.
 4. In the **Status** column, check if the indicated situation is `Active`. If the SKUs are active, go to step 7.
 5. If a SKU appears as `Inactive`, click `Update` to view the SKU detailed information.
 
-    ![07-catalogo-skus-en](https://images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/038a679284d7261a44ace5814e67ee34/07-catalogo-skus-en.png)
+    ![07-catalogo-skus-en](//images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/038a679284d7261a44ace5814e67ee34/07-catalogo-skus-en.png)
 
 6. On the SKU information page, continue checking the items listed below.
     * **Activate SKU if possible:** Check if this option is selected. Otherwise, the SKU will not be displayed. When you activate this option, you determine that the SKU will be activated if it meets the necessary requirements:
@@ -107,9 +107,9 @@ On the SKUs page, in **Products > Catalog > Products and SKUs**, follow the inst
 8. Check if the SKU contains at least one image. If it does not, the SKU will not be activated — follow the next step to correct this problem.
 9. Click `Insert` to upload a new image. If you prefer, click `Associate existing images`  to include an image already used for another SKU.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/ebc572e69e7dc83a5de491a83c4233ac/08-aba-imagens-en.png" alt="08-aba-imagens-es" style="margin-bottom: 20px;"> <figcaption align = "center"><em><strong>Images</strong> tab</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/ebc572e69e7dc83a5de491a83c4233ac/08-aba-imagens-en.png" alt="08-aba-imagens-es" style="margin-bottom: 20px;"> <figcaption align = "center"><em><strong>Images</strong> tab</em></figcaption></figure>
 
-![09-sku-imagens-en](https://images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/f58814d66052faf18d3bc44e68eb83cc/09-sku-imagens-en.PNG)
+![09-sku-imagens-en](//images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/f58814d66052faf18d3bc44e68eb83cc/09-sku-imagens-en.PNG)
 
 ### Indexed Info
 
@@ -123,13 +123,13 @@ The indexing list displays each product SKU status. If any issue is detected, th
 
 In the example below, you can conclude that the SKU is unavailable because there are no items in stock:
 
-![10-indexed-info-code](https://images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/f1e1650c980fd7042649f6bd8ae3e9a4/Group_1__7_.png)
+![10-indexed-info-code](//images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/f1e1650c980fd7042649f6bd8ae3e9a4/Group_1__7_.png)
 
 Based on this information, you can take action to correct the issue. In this example, you should adjust the item quantity in stock in the [Logistics](#logistics) system.
 
 An active SKU without errors will appear in the index, similar to the one illustrated below:
 
-![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/9e9c99cc4c9408c6dfbaddd4feaaaa84/11-indexed-info-code-active.png)
+![11-indexed-info-code-active](//images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/9e9c99cc4c9408c6dfbaddd4feaaaa84/11-indexed-info-code-active.png)
 
 <div class="alert alert-info">
 <p>If no reason is given for the product’s unavailability and if you do not find any issues in the product/SKUs, reindexing the product may solve the problem.</p>
@@ -147,7 +147,7 @@ In the **Prices** module, it's important to verify if your product SKU contains
 
 In the example illustrated below, there are two SKUs without a base price. This is why there is no calculated price in the trade policy column — only the information _No price yet_ is displayed.
 
-![12-precos-en](https://images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/fe4b6781deb81831cd88cef790af7aee/12-precos-en.PNG)
+![12-precos-en](//images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/fe4b6781deb81831cd88cef790af7aee/12-precos-en.PNG)
 
 ### Creating a base price
 
@@ -175,7 +175,7 @@ The **Shipping simulator** allows you to check if the item exists in the invento
 2. Fill in the necessary information, as described in [Shipping simulator](https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144).
 3. Click `Shipping simulation`.
 
-![13-simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/0fbc4b15077d4ea265c82c0a70f5f064/13-simular-frete-en.PNG)
+![13-simular-frete-pt](//images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/0fbc4b15077d4ea265c82c0a70f5f064/13-simular-frete-en.PNG)
 
 <div class="alert alert-info">
 <p>To investigate a specific item, you must perform the simulation using a <strong>zip code</strong> included in all the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140">trade policies</a>. If you find out the item is not available for that zip code, it means it will not be available for any other one.</p>
@@ -183,7 +183,7 @@ The **Shipping simulator** allows you to check if the item exists in the invento
 
 The simulation result shows whether the product is available for delivery at the provided address and which are the best shipping options. For example, if there are not enough available items in stock, the simulator will display the following message:
 
-![14-simulador-motivos-en](https://images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/68f0e61b7646bb685b5f28278856512b/14-simulador-motivos-en.PNG)
+![14-simulador-motivos-en](//images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/68f0e61b7646bb685b5f28278856512b/14-simulador-motivos-en.PNG)
 
 For more information on using the simulator, please read the article [Shipping simulator](https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144).
 
@@ -204,7 +204,7 @@ If a product is not available on the website because it is out of stock, you mus
 3. To update the stock count, go to the desired SKU row and write the current quantity in the **Update count** column, as illustrated below.
 4. Click `Save`.
 
-![15-gerenciar-inventario-en](https://images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/1ef88e4a10e7cac64efaca80a3fe37fa/15-gerenciar-inventario-en.gif)
+![15-gerenciar-inventario-en](//images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/1ef88e4a10e7cac64efaca80a3fe37fa/15-gerenciar-inventario-en.gif)
 
 For more information, please read the [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) tutorial.
 
@@ -249,7 +249,7 @@ Follow the steps below to check the template your page is using.
 
     In the example below, the default template is `vtex.curbside-pickup@0.x:store.curbside-pickup` and there is no conditional template.
 
-    ![16-templates-cms-en](https://images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/13b66c83e437aa4e2a3bd0d9f722553b/16-templates-cms-en.PNG)
+    ![16-templates-cms-en](//images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/13b66c83e437aa4e2a3bd0d9f722553b/16-templates-cms-en.PNG)
 
 4. Next, you must check the blocks declared in the used template, as described in [Templates](#templates).
 
diff --git a/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
index 7010bfc30..d9f568e31 100644
--- a/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
@@ -24,7 +24,7 @@ To perform this configuration:
 3. Click **Edit** on the `Produto - Thumb` row.
 4. In the display, you can choose the maximum file size  for the thumbnails in the **Maximum size in Kb** field.
 
-![File type settings in CMS](https://images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/388b019bc9fa6b0331b56209353f9165/EN.PNG)
+![File type settings in CMS](//images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/388b019bc9fa6b0331b56209353f9165/EN.PNG)
 
 To learn how to improve the quality of any image from your store without compromising the page load performance, we also recommend reading the article [Improving the performance of product images](https://help.vtex.com/pt/tutorial/improving-the-performance-of-product-images/).
 
diff --git a/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 477d09975..04cdeea35 100644
--- a/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -21,7 +21,7 @@ Follow the steps below to validate the information:
 1. Go to your store Admin: `https://{AccountName}.myvtex.com/admin`.
 2. On the side menu, click __Master Data__.
 3. In the __Profile System__ box, click __Customers__.
-4. Select the option __Email__ and search the client's email.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+4. Select the option __Email__ and search the client's email.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 5. Click the customer record to access the profile details.
 
 In the __Contact__ section, you will see that the `Is Company?` option is filled with the value `No`. At the same time, in the section __Company Data__, you will see that the `Document Type` field is filled with the value `cnpj`.
diff --git a/docs/faq/en/why-was-the-item-splitted-in-the-cart.md b/docs/faq/en/why-was-the-item-splitted-in-the-cart.md
index 509388327..1a6609223 100644
--- a/docs/faq/en/why-was-the-item-splitted-in-the-cart.md
+++ b/docs/faq/en/why-was-the-item-splitted-in-the-cart.md
@@ -3,8 +3,8 @@ title: 'Why was the item splitted in the cart?'
 id: frequentlyAskedQuestions_350
 status: PUBLISHED
 createdAt: 2017-04-27T22:37:20.610Z
-updatedAt: 2019-12-31T14:24:24.843Z
-publishedAt: 2019-12-31T14:24:24.843Z
+updatedAt: 2023-07-12T18:31:38.375Z
+publishedAt: 2023-07-12T18:31:38.375Z
 firstPublishedAt: 2017-04-27T23:01:45.290Z
 contentType: frequentlyAskedQuestion
 productTeam: Shopping
@@ -14,15 +14,15 @@ locale: en
 legacySlug: why-was-the-item-splitted-in-the-cart
 ---
 
-This scenario is presented when more than one item from the same SKU is splitted into more than one line in the cart.
+This scenario is presented when more than one item from the same SKU is splitted into more than one line in the cart. This occurs due to an action called apportionment - that is the division of a value among some items.
 
-This occurs due to an action called apportionment - that is the division of a value among some items. However, there are scenarios in which the discount amount is indivisible by the number of items, particularly in cases where the SKU has a multiplier unit. So, you need to give different discounts to items of the same SKU for the discount amount be correct. This ends up assigning different prices, and splitting each unit in a line.
+ However, there are scenarios in which the discount amount is indivisible by the number of items, particularly in cases where the SKU has a multiplier unit. So, you need to give different discounts to items of the same SKU for the discount amount be correct. This ends up assigning different prices, and splitting each unit in a line.
 
 The example below helps to understand this concept :
 
-![](//images.contentful.com/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/65984bd4a878563818fa92d1f58a0db9/Por_que_o_item_do_carrinho_foi_separado.jpg)
+![Por que o item do carrinho foi separado](//images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/f3753a72da2cdfa13dc4cc797b2d9883/Por_que_o_item_do_carrinho_foi_separado.jpg)
 
-1. Multiplier unit
-2. Product price after discount
-3. Product price with the difference due to the apportionment
-4. Discount applied
+1. Multiplier unit.
+2. Product price after discount.
+3. Product price with the difference due to the apportionment.
+4. Discount applied.
diff --git a/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 1f5abc26e..705feaecc 100644
--- a/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -18,7 +18,7 @@ A security rule exists at checkout, regarding SmartCheckout purchase facility.
 
 Since with SmartCheckout purchases can be closed just with the email and with the CVV of the card, where the customer has already completed the purchase before, we restrict the number of unsuccessful attempts to conclude the purchase to 3 before asking the customer for their user ID.
 
-![LoginEN](https://images.ctfassets.net/alneenqid6w5/FeavXteriS8e4sUYiccgG/fdc93275e4e4145405e95b9e57ab6e4a/LoginEN.png)
+![LoginEN](//images.ctfassets.net/alneenqid6w5/FeavXteriS8e4sUYiccgG/fdc93275e4e4145405e95b9e57ab6e4a/LoginEN.png)
 
 In other words, if the customer concludes the purchase using only the email and the CVV of the credit card, and if the operator’s approval does not occur after 3 consecutive attempts, a user ID screen is displayed so that the customer can continue trying to purchase. This countdown starts again when the customer logs in and successfully completes their purchase.
 
diff --git a/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md b/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md
index b0cc87599..a283b6443 100644
--- a/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md
+++ b/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md
@@ -16,7 +16,7 @@ legacySlug: why-wasnt-the-promotion-applied-to-the-marketplace
 
 To create a promotion for marketplaces, the scenario is almost the same as that for usual promotions. However, you must select, in the **política comercial** field, the value **Loja(s) de terceiro(s)** and select the trade policy applied by the marketplace, or fill out the **afiliado **field with the Id of the marketplace.
 
-![marketplace.es](https://images.ctfassets.net/alneenqid6w5/1eBfrn5ZxkarVv9eS793vG/cd52d2a90c555f8bb3829c626afc159a/marketplace.es.png)
+![marketplace.es](//images.ctfassets.net/alneenqid6w5/1eBfrn5ZxkarVv9eS793vG/cd52d2a90c555f8bb3829c626afc159a/marketplace.es.png)
 
 For more details on how to do so, check [our article on how to create a promotion for the marketplace](https://help.vtex.com/en/tutorial/configurando-promocao-para-marketplace/).
 
diff --git a/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
index 19e4d623f..26a78ebbc 100644
--- a/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -26,15 +26,15 @@ Hay varias aplicaciones y extensiones de Chrome que retiran las personalizacione
 
 1. Para abrir DevTools, ingrese a Chrome y oprima **F12** o haga clic en el **botón derecho del mouse > Inspeccionar**.
 
-![Customizations1](https://images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
+![Customizations1](//images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
 
 2. Vamos a buscar la función **Request Blocking** para bloquear todas las personalizaciones realizadas con CSS, JavaScript y Google Tag Manager. Haga clic en los tres puntos de la derecha, como se indica en la imagen, después en **More Tools** y, por último, en **Request Blocking**.
 
-![Customizations2](https://images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
+![Customizations2](//images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
 
 3. Se abrirá un recuadro como se muestra aquí:
 
-![Customizations3](https://images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
+![Customizations3](//images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
 
 4. Haga clic en la pestaña **Request Blocking**.
 
@@ -50,7 +50,7 @@ Ahora defina los recursos que se deben bloquear. Solo tiene que hacer la configu
 
 El recuadro se verá así:
 
-![Customizations4](https://images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
+![Customizations4](//images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
 
 Recuerde: solo tiene que hacer la configuración __una__ vez.
 
@@ -60,11 +60,11 @@ Recuerde: solo tiene que hacer la configuración __una__ vez.
 
 2. Esta será la configuración que quedará definida como estándar, con las cinco opciones habilitadas para el bloqueo.
 
-![Customizations5](https://images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
+![Customizations5](//images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
 
 3. Ahora, actualice la página oprimiendo **F5**. La página se mostrará sin los componentes de personalización.
 
-![Customizations6](https://images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
+![Customizations6](//images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
 
 4. Para volver a visualizar las personalizaciones, solo tiene que desactivar la casilla **Enable request blocking** y actualizar la página otra vez.
 
diff --git a/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
index bec68f16b..18f62ea88 100644
--- a/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -31,7 +31,7 @@ Por eso, para tener acceso al cambio de seller, la afiliación con split se debe
 - __Utilizar el comportamiento recomendado del procesador de pagos__.
 - __Desactivado: No se captura automáticamente__.
 
-![Captura de Pago Automática](https://images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/0c82ee9775c65757ccfd014d8dd910eb/Captura_De_Pago.png)
+![Captura de Pago Automática](//images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/0c82ee9775c65757ccfd014d8dd910eb/Captura_De_Pago.png)
 
 ### ¿Al seleccionar el comportamiento de liquidación que no es automático, cuándo se liquidará el pago?
 
diff --git a/docs/faq/es/fix-redirect-error-in-pagseguro.md b/docs/faq/es/fix-redirect-error-in-pagseguro.md
index 4dab57845..779b2645e 100644
--- a/docs/faq/es/fix-redirect-error-in-pagseguro.md
+++ b/docs/faq/es/fix-redirect-error-in-pagseguro.md
@@ -3,8 +3,8 @@ title: 'Corregir error de redireccionamiento en PagSeguro'
 id: 5b1lVDQ9HUKQs4Wy24uWq2
 status: PUBLISHED
 createdAt: 2018-02-15T16:07:47.669Z
-updatedAt: 2019-12-31T14:23:59.281Z
-publishedAt: 2019-12-31T14:23:59.281Z
+updatedAt: 2024-02-16T12:41:04.461Z
+publishedAt: 2024-02-16T12:41:04.461Z
 firstPublishedAt: 2018-02-15T17:26:16.189Z
 contentType: frequentlyAskedQuestion
 productTeam: Financial
@@ -14,6 +14,8 @@ locale: es
 legacySlug: corregir-error-de-redirecionamento-en-pagseguro
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Si usted está encontrando __problemas de redireccionamiento__ utilizando Pagseguro, es probable que el *redirect* de PagSeguro esté configurado de forma incorrecta.
 
 Para corregir el problema, hay dos opciones: Configurar el PagSeguro *con redirect* de la forma correcta o configurar PagSeguro *sin redirect*.
@@ -22,16 +24,12 @@ Para corregir el problema, hay dos opciones: Configurar el PagSeguro *con redire
 
 ### Configurar Afiliación de Gateway PagSeguro
 
-1. Acceda la sección de __Pagos__.
-2. Haga clic en el botón __Configuración__.
-3. Haga clic en la pestaña __Afiliaciones__.
-4. Haga clic en el botón __+__ en la esquina superior derecha de la pantalla.
-5. Haga clic en la afiliación __PagSeguro__.
-6. Rellene los campos __email__ y __token__ con la información proporcionada por PagSeguro.
-
-En su cuenta de PagSeguro, debe activar "Redirigir con código de transacción" (Mi cuenta > Integraciones > Página de redireccionamiento). El nombre del parámetro solicitado debe ser `psTransactionId`.
-
-Después, haga clic en __Guardar__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagSeguro__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos __email__ y __token__ con la información proporcionada por PagSeguro.
+5. Siga la guía __Configuração do redirecionamento__ descrita en el panel de configuración.
+6. Haga clic en `Guardar`.
 
 ### Configurar Condición de Pago PagSeguro
 
diff --git a/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md b/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md
index 5e11232e5..b755109c1 100644
--- a/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md
+++ b/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md
@@ -23,4 +23,4 @@ NSU y TID son datos de pago que quedan guardados en __Pagos__, en la sección de
 
 Esas informaciones son facilitadas a VTEX durante las transacciones y son organizadas para una simple visualización en **+ Informaciones**, en el [detalle del pedido](/es/tutorial/como-visualizar-detalle-del-pedido), conforme imagen abajo:
 
-![mais-informações-detalhes-pedido es](https://images.ctfassets.net/alneenqid6w5/3Ht2Oe6PAYLQCEtwxULNZA/f54b2b67f42713cb300977e387b12a5b/mais-informa____es-detalhes-pedido_es.png)
+![mais-informações-detalhes-pedido es](//images.ctfassets.net/alneenqid6w5/3Ht2Oe6PAYLQCEtwxULNZA/f54b2b67f42713cb300977e387b12a5b/mais-informa____es-detalhes-pedido_es.png)
diff --git a/docs/faq/es/how-does-vtex-support-work.md b/docs/faq/es/how-does-vtex-support-work.md
index 2c05ecce1..615d601cc 100644
--- a/docs/faq/es/how-does-vtex-support-work.md
+++ b/docs/faq/es/how-does-vtex-support-work.md
@@ -3,8 +3,8 @@ title: '¿Cómo funciona el soporte de VTEX?'
 id: 3kACEfni4m8Yxa1vnf2ebe
 status: PUBLISHED
 createdAt: 2019-03-10T19:06:12.818Z
-updatedAt: 2022-12-23T15:50:55.141Z
-publishedAt: 2022-12-23T15:50:55.141Z
+updatedAt: 2024-01-08T19:15:40.782Z
+publishedAt: 2024-01-08T19:15:40.782Z
 firstPublishedAt: 2019-03-10T19:08:36.723Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -18,7 +18,7 @@ En VTEX, compartimos la responsabilidad por el éxito de nuestros clientes. Nues
 
 ## Soporte	
 
-Todos los clientes tienen acceso al servicio de atención ofrecido por nuestro equipo de especialistas del Soporte. Estos especialistas están preparados para brindar la mejor experiencia posible en la atención de las solicitudes. Para contactarlos, [es necesario abrir un ticket para el soporte VTEX](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt).
+Todos los clientes tienen acceso al servicio de atención ofrecido por nuestro equipo de especialistas del Soporte. Estos especialistas están preparados para brindar la mejor experiencia posible en la atención de las solicitudes. Para contactarlos, [es necesario abrir un ticket para el soporte VTEX](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
 ### Sistema de Tickets
 
@@ -42,20 +42,16 @@ Para servir mejor a los clientes globales en diferentes países, nuestro equipo
 - Asia-Pacífico (APAC)
 - [Brasil](/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)
 - [Estados Unidos (EE. UU.)](/en/faq/vtex-support-united-states--Bm45YFp68QRe1Z5r2oa07)
-- Europa, Oriente Medio y África (EMEA)
+- [Europa, Oriente Medio y África (EMEA)](https://help.vtex.com/es/faq/vtex-soporte-emea--5ePu2qkCfmE0IEKDFKg53F?&utm_source=autocomplete)
 
 ## Servicios disponibles para todos los planes
 
 ### Monitoreo en tiempo real  
 
-Dirigimos nuestros esfuerzos a la transparencia relacionada con la integridad de nuestros sistemas. Por eso, siempre que se presente un problema crítico que afecte las ventas de las tiendas o el funcionamiento de la plataforma, nos comunicaremos de manera proactiva con los clientes y partners por medio de tres canales:
-
-- El panel [Healthcheck](http://healthcheck.vtex.com/) muestra los módulos responsables por el monitoreo de cada servicio de VTEX en tiempo real. Exhibimos un indicador del funcionamiento de cada módulo y el horario de la última actualización, emitiendo alertas cuando algún recurso no esté disponible o su funcionamiento esté degradado. 
+Dirigimos nuestros esfuerzos a la transparencia relacionada con la integridad de nuestros sistemas. Por eso, siempre que se presente un problema crítico que afecte las ventas de las tiendas o el funcionamiento de la plataforma, nos comunicaremos de manera proactiva con los clientes y partners por medio de los canales siguientes:
 
 - La página de [Status](https://status.vtex.com/) exhibe una línea de tiempo con el historial reciente de incidentes del sistema. En ese historial, detallamos la información de cada incidente: lo que sucedió, los módulos que fueron afectados, la secuencia de acciones hasta su resolución y un resumen final de lo que ocurrió. 
 
-- La página de [Releases](https://releases.vtex.com/) muestra una línea de tiempo, detallada por módulo y versión, de todas las actualizaciones hechas en los ambientes stable y beta.  
-
 Tomaremos todas las medidas pertinentes para resolver la situación lo antes posible y para garantizar el cumplimiento de nuestro [SLA](https://help.vtex.com/es/tutorial/o-que-e-o-sla-de-operacao-da-plataforma--2cIFrsY5S8usk84OU4QOKm?locale=pt) previsto en contrato.
 
 ### Help Center
@@ -70,11 +66,7 @@ En este [portal para desarrolladores](https://developers.vtex.com), usted encuen
 
 En el panel administrativo tenemos nuestro canal de comunicación de actualizaciones del producto, en el cual publicamos comunicados siempre que alguna funcionalidad nueva se lanza o cuando alguna acción es necesaria para evitar una interrupción del servicio. Estos comunicados también están disponibles en la sección de [Noticias](https://help.vtex.com/es/announcements) del Help Center.
 
-Las actualizaciones técnicas, dirigidas a desarrolladores y partners, son publicadas en la sección [Release Notes](https://developers.vtex.com/changelog) del portal del desarrollador. Eso incluye actualizaciones en las APIs, nuevas guías de desarrollo y comunicados sobre VTEX IO.
+Las actualizaciones técnicas, dirigidas a desarrolladores y partners, son publicadas en la sección [Release Notes](https://developers.vtex.com/updates/release-notes) del portal del desarrollador. Eso incluye actualizaciones en las APIs, nuevas guías de desarrollo y comunicados sobre VTEX IO.
 
 Los lanzamientos que tienen una mayor relevancia para el mercado, como nuevos productos, nuevos recursos de gran impacto sobre los productos existentes y  actualizaciones de la empresa son divulgados en el [Blog](https://vtex.com/pt-br/category/produto/) y en el boletín informativo mensual del producto.
 
-## Servicios adicionales bajo demanda
-
-En las situaciones en que nuestros clientes necesitan mayor ayuda para proyectos complejos, ofrecemos servicios de consultoría de proyectos. En caso de que tenga interés, su Customer Success Manager podrá orientarlo sobre las alternativas disponibles y direccionará la demanda a los equipos responsables.
-
diff --git a/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md b/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md
index 411fe9548..756430832 100644
--- a/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md
+++ b/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md
@@ -31,7 +31,7 @@ En este caso,
 4. Acceda a __¿Cuáles son las condiciones para que la promoción sea válida?__.
 5. Introduzca el código del cupón en __utm_source__.
 
-  ![Sincronizar promoções no mesmo cupom - 1 - ES](https://images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/c049994bcf92c903a7d4792330ad4306/7yJhwPnclx3tCiJdgpcYyv_-_ES.png)
+  ![Sincronizar promoções no mesmo cupom - 1 - ES](//images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/c049994bcf92c903a7d4792330ad4306/7yJhwPnclx3tCiJdgpcYyv_-_ES.png)
 
 6. Haga clic en 'Crear cupón a partir de las UTMs arriba'.
 7. Haga clic en 'Guardar'.
@@ -39,6 +39,6 @@ En este caso,
 9. Repita el proceso con la segunda promoción regular.
 10. Al final, ambas promociones deben presentar la misma UTM.
 
-  ![Sincronizar promoções no mesmo cupom - 2 - ES](https://images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/b1d28f6435312f320902fb62c12dc6b6/5nhdQy1Y4YWs4pHHokSA44_-_ES.png)
+  ![Sincronizar promoções no mesmo cupom - 2 - ES](//images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/b1d28f6435312f320902fb62c12dc6b6/5nhdQy1Y4YWs4pHHokSA44_-_ES.png)
 
 De este modo, el cliente puede quitar los dos valores antes de finalizar la compra.
diff --git a/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md b/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md
index ae75a9efd..5d8424486 100644
--- a/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md
+++ b/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md
@@ -18,11 +18,11 @@ Puede editar los campos que aparecen como obligatorios en el __Profile System__
 
 1. En el menú de admin, seleccione el módulo __Master Data__. 
 2. Asegúrese de que se encuentra en la pestaña Aplicaciones, dentro de __ Links Rápidos__.
-3. Haga clic en el __engranaje__ en __Profile System__. ![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
-4. Haga clic en el __lápiz__ al lado del ítem que desea configurar. ![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
+3. Haga clic en el __engranaje__ en __Profile System__. ![MasterDataTutorial 1 UM](//images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
+4. Haga clic en el __lápiz__ al lado del ítem que desea configurar. ![MasterDataTutorial2](//images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
 5. Haga clic en __Schemas de Layout__.
 6. En la __Sección 1__, escoja el ítem del campo que desea configurar.
-7. En __Configuraciones avanzadas del campo__, seleccione __Campo obligatorio__ en el formulario. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
+7. En __Configuraciones avanzadas del campo__, seleccione __Campo obligatorio__ en el formulario. ![MasterDataTutorial3](//images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
 
 La opción también puede modificarse siempre que lo desee. 
 
diff --git a/docs/faq/es/i-dont-recognize-the-reservation-id-of-an-order.md b/docs/faq/es/i-dont-recognize-the-reservation-id-of-an-order.md
index c965bd2a4..90389e0c5 100644
--- a/docs/faq/es/i-dont-recognize-the-reservation-id-of-an-order.md
+++ b/docs/faq/es/i-dont-recognize-the-reservation-id-of-an-order.md
@@ -3,8 +3,8 @@ title: 'No reconozco el ID de reserva de un pedido. ¿Qué puede haber ocurrido?
 id: tja793G4XAWI2K8uIC4uW
 status: PUBLISHED
 createdAt: 2018-03-05T21:07:36.301Z
-updatedAt: 2023-03-22T20:28:58.311Z
-publishedAt: 2023-03-22T20:28:58.311Z
+updatedAt: 2024-02-05T18:01:17.750Z
+publishedAt: 2024-02-05T18:01:17.750Z
 firstPublishedAt: 2018-03-05T22:28:55.349Z
 contentType: frequentlyAskedQuestion
 productTeam: Channels
@@ -18,4 +18,4 @@ Esto debe estar sucediendo porque los pedidos que usted está viendo todavía no
 
 En este caso, puede ponerse en contacto con su marketplace o esperar un poco más para comprobar si la información del pedido se actualiza, ya que para no haber entrado en la herramienta de Integraciones, puede haber sido cancelado o incluso no se ha creado.
 
-Si lo prefiere, usted puede comprobar la información relativa a la reserva de su pedido a través de [API](https://developers.vtex.com/reference/reservations#createreservation).
+Si lo prefiere, usted puede comprobar la información relativa a la reserva de su pedido a través de Logistics API, a traves del endpoint [List reservation by ID](https://developers.vtex.com/docs/api-reference/logistics-api?endpoint=get-/api/logistics/pvt/inventory/reservations/-reservationId-).
diff --git a/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 4d0cdf6f2..4925902a9 100644
--- a/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -31,6 +31,6 @@ __Para hacer la inclusión manual de SKUs específicos, siga el paso a paso abaj
 5. Dé un nombre a su colección (los demás campos no se deben llenar).
 6. Introduzca los SKUs en el campo informado y __los separe con comas__.
 
-![recurrence-specific-skus](https://images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
+![recurrence-specific-skus](//images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
 
 Por fin, dé un nombre al __Grupo__ de su Colección y haga clic en __Save Group__.
diff --git a/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md b/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md
index bae23d77e..61445833c 100644
--- a/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md
+++ b/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md
@@ -32,7 +32,7 @@ __Llene el campo Label__
 4. Vaya a la pestaña __Imágenes__;
 5. Introduzca un término para llenar la __Label__;
 
-  ![Kit Look - Label - ES](https://images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/63dcfae1b88d48e1a8582c43cfa9af81/7FR879Lzl3eEDmAHiBV0TV_es.jpg)
+  ![Kit Look - Label - ES](//images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/63dcfae1b88d48e1a8582c43cfa9af81/7FR879Lzl3eEDmAHiBV0TV_es.jpg)
 
 6. Haga clic en __Guardar__.
 
diff --git a/docs/faq/es/my-admin-is-blocked-what-do-i-do.md b/docs/faq/es/my-admin-is-blocked-what-do-i-do.md
index bb704b9d4..a31c8692a 100644
--- a/docs/faq/es/my-admin-is-blocked-what-do-i-do.md
+++ b/docs/faq/es/my-admin-is-blocked-what-do-i-do.md
@@ -3,8 +3,8 @@ title: 'Mi Admin está bloqueado. ¿Que hacer?'
 id: 4IkFRmDVx6quIIcwoOGY6K
 status: PUBLISHED
 createdAt: 2017-10-11T13:36:13.665Z
-updatedAt: 2021-03-22T20:31:43.767Z
-publishedAt: 2021-03-22T20:31:43.767Z
+updatedAt: 2023-07-24T15:11:04.222Z
+publishedAt: 2023-07-24T15:11:04.222Z
 firstPublishedAt: 2017-10-11T13:39:18.676Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -22,9 +22,8 @@ Mientras espera a que el equipo de Finanzas lo contacte, es posible desbloquear
 
 Siga los pasos a continuación para desbloquear su Admin durante este período. Debe tener los permisos de Admin Super o un [Perfil de Acceso Financiero](https://help.vtex.com/es/tutorial/como-criar-um-perfil-de-acesso-financeiro--717qPtxW3Cy9n5KrReHeVv?locale=pt) para realizar las siguientes acciones:
 
-- Acceda al módulo Facturas.
-- Haga clic en el botón **Cómo desbloquear temporalmente**.
-- Introduzca el número del ticket que abrió previamente para el desbloqueo.
-- Haga clic en el botón **Desbloquear por 48 horas**.
+1. Acceda al módulo Facturas.
+2. Haga clic en el botón **Cómo desbloquear temporalmente**.
+3. Introduzca el número del ticket que abrió previamente para el desbloqueo.
+4. Haga clic en el botón **Desbloquear por 48 horas**.
 
-![Home 1](https://images.ctfassets.net/alneenqid6w5/6GCOTVMqGicNCz1TdzzrzJ/6dadcd5d6923b9eaa0612a62b006180f/Home__1_.gif)
diff --git a/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
new file mode 100644
index 000000000..a8bdbe222
--- /dev/null
+++ b/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -0,0 +1,30 @@
+---
+title: 'Pedido está trabado en "Listo para preparación", ¿qué se hace?'
+id: frequentlyAskedQuestions_771
+status: PUBLISHED
+createdAt: 2017-04-27T22:27:37.057Z
+updatedAt: 2023-06-15T13:20:25.568Z
+publishedAt: 2023-06-15T13:20:25.568Z
+firstPublishedAt: 2017-04-27T23:02:34.947Z
+contentType: frequentlyAskedQuestion
+productTeam: Post-purchase
+author: authors_84
+slug: pedido-esta-trabado-en-listo-para-preparacion-que-se-hace
+locale: es
+legacySlug: pedido-está-trabado-en-pronto-para-manuseio-que-se-hace
+---
+
+Cuando una tienda tiene algún pedido trabado en el status **Listo para preparación** quiere decir que es necesario que el ERP informe que ha consultado el pedido y empezó su manoseo.
+
+Esto ocurre porque, en el flujo de pedidos, existe el status en el que los pedidos deben ser consultados por el ERP, llamado **Listo para preparación**.
+
+Cuando el ERP consulta e inserta este pedido en su base, es necesario que él le informe a VTEX que el pedido puede seguir con su flujo. Ese aviso puede hacerse por dos maneras:
+
+- [ERP informa por API](https://developers.vtex.com/vtex-rest-api/reference/starthandling): el modo más común de actualización.
+- **Lojista informa manualmente**: la tienda no posee un ERP y para que el pedido siga su flujo es necesario informar manualmente en el Admin VTEX, en la [página de detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). Para ver el paso a paso completo, consulte el artículo [Enviar pedido al status a Preparar la Entrega](https://help.vtex.com/es/tutorial/passar-pedido-para-o-status-preparando-entrega--tutorials_198).
+
+> Es necesario tener un [perfil de acceso con permiso OMS - Full access](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para llevar a cabo esta acción.
+
+<div class="alert alert-warning">
+<p>Si el pedido pasa del status <b>Iniciar preparación</b> manualmente, no será posible bajar el pedido para el ERP posteriormente.</p>
+</div>
diff --git a/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md b/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md
index 41de5cee5..76ec2d0df 100644
--- a/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md
+++ b/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md
@@ -18,6 +18,6 @@ Cuando entre en __Afiliaciones__, es posible ver la lista de todas las configura
 
 Eso significa que esta afiliación no está activa, y sí que está en teste. Es posible confirmar esa información haciendo clic en la Afiliación.
 
-![afiliação-gateway-teste es](https://images.ctfassets.net/alneenqid6w5/6CYa8SyybuMGwYqOqkoa8U/b1b1d471edd3d98336719c8e07f22605/gateway_teste_es.png)
+![afiliação-gateway-teste es](//images.ctfassets.net/alneenqid6w5/6CYa8SyybuMGwYqOqkoa8U/b1b1d471edd3d98336719c8e07f22605/gateway_teste_es.png)
 
 O sea, el color destaca aquellas configuraciones que todavía no están activas.
diff --git a/docs/faq/es/understanding-vtex-email-capture-system.md b/docs/faq/es/understanding-vtex-email-capture-system.md
index c365d2000..ec18282e3 100644
--- a/docs/faq/es/understanding-vtex-email-capture-system.md
+++ b/docs/faq/es/understanding-vtex-email-capture-system.md
@@ -50,5 +50,5 @@ Para que se pueda utilizar la función <a href="https://help.vtex.com/es/tutoria
 Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
 </div>
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/faq/es/vtex-support-brazil.md b/docs/faq/es/vtex-support-brazil.md
index 3f022562b..21282a267 100644
--- a/docs/faq/es/vtex-support-brazil.md
+++ b/docs/faq/es/vtex-support-brazil.md
@@ -3,8 +3,8 @@ title: 'Soporte VTEX - Brasil'
 id: 5q861sTw1n7H2BENOu7ls9
 status: PUBLISHED
 createdAt: 2021-03-02T00:59:46.352Z
-updatedAt: 2022-12-23T15:47:00.476Z
-publishedAt: 2022-12-23T15:47:00.476Z
+updatedAt: 2024-05-23T16:25:31.311Z
+publishedAt: 2024-05-23T16:25:31.311Z
 firstPublishedAt: 2021-03-02T01:09:50.358Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
diff --git a/docs/faq/es/vtex-support-emea.md b/docs/faq/es/vtex-support-emea.md
new file mode 100644
index 000000000..fbe6439b6
--- /dev/null
+++ b/docs/faq/es/vtex-support-emea.md
@@ -0,0 +1,17 @@
+---
+title: 'Soporte VTEX - EMEA'
+id: 5ePu2qkCfmE0IEKDFKg53F
+status: PUBLISHED
+createdAt: 2023-11-09T16:29:55.255Z
+updatedAt: 2024-05-28T02:20:01.805Z
+publishedAt: 2024-05-28T02:20:01.805Z
+firstPublishedAt: 2023-11-09T16:51:03.796Z
+contentType: frequentlyAskedQuestion
+productTeam: Billing
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: soporte-vtex-emea
+locale: es
+legacySlug: soporte-vtex-emea
+---
+
+Este contenido está disponible solo en inglés. [Haga clic aquí](https://help.vtex.com/faq/suporte-vtex-emea--5ePu2qkCfmE0IEKDFKg53F) para acceder.
diff --git a/docs/faq/es/website-with-error-how-to-fix-it.md b/docs/faq/es/website-with-error-how-to-fix-it.md
index bc52a56d8..df9aafcd8 100644
--- a/docs/faq/es/website-with-error-how-to-fix-it.md
+++ b/docs/faq/es/website-with-error-how-to-fix-it.md
@@ -22,7 +22,7 @@ Pero, si está Amarillo, está con error.
 Sigue el paso a paso de cómo ajustarlo:
 
 1. Haga clic en el website.
-2. Seleccione el Binding (línea seleccionada en la imagen abajo) y haga clic en __Update__:![Binding 1](https://images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
+2. Seleccione el Binding (línea seleccionada en la imagen abajo) y haga clic en __Update__:![Binding 1](//images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
 3. En la pantalla que será mostrada, el campo __Store name from License Manager__ estará en blanco. Con eso, haga clic en la flecha que aparece en ese campo y seleccione el nombre de su tienda.
-4. Haga clic en __Save Binding__.![Binding 2](https://images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
+4. Haga clic en __Save Binding__.![Binding 2](//images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
 5. Haga clic en __Websites__ de nuevo para actualizar la página y listo. El globito estará azul. ¡Lo que es una indicación de que ahora esta correcto!
diff --git a/docs/faq/es/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md b/docs/faq/es/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
index faab3a6c8..82c88af06 100644
--- a/docs/faq/es/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
+++ b/docs/faq/es/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'Qué hacer cuando aparece un mensaje de error inesperado al seleccionar PayPal Plus en el checkout'
 id: 2eyMuEf6wsWuOgrjo7tzQH
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-03-18T14:01:50.694Z
-updatedAt: 2019-12-31T14:24:40.864Z
-publishedAt: 2019-12-31T14:24:40.864Z
+updatedAt: 2024-02-19T17:41:00.925Z
+publishedAt: 
 firstPublishedAt: 2019-03-18T14:10:08.064Z
 contentType: frequentlyAskedQuestion
 productTeam: Shopping
diff --git a/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md b/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md
index 91411e478..7dd4376a5 100644
--- a/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md
+++ b/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md
@@ -24,9 +24,9 @@ A continuación, entienda el paso a paso para hacerlo:
 
 1. Acceda al __Master Data__;
 2. Haga clic en __Exportations__;
-![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
+![3WNNUZ8EgDZ4iYv8e0OyQG](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
 3. Asegúrese de que la pestaña abierta es la de __"Applications"__;
-![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
+![7ecXBGaCeC3hTaO0lODPq1](//images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
 4. En __"Status de exportaciones"__, haga clic en el informe que desea descargar.
 
 De esta forma, es posible acceder a este material aunque el email original no haya llegado al solicitante.
diff --git a/docs/faq/es/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md b/docs/faq/es/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
index 40ad0322a..6c2c7926c 100644
--- a/docs/faq/es/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
+++ b/docs/faq/es/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
@@ -3,8 +3,8 @@ title: 'Qué hacer al recibir error en la simulación de flete'
 id: 3bkJwe0Yj6qEkuYKUWwKwK
 status: PUBLISHED
 createdAt: 2017-05-09T14:03:03.097Z
-updatedAt: 2021-03-22T20:46:27.291Z
-publishedAt: 2021-03-22T20:46:27.291Z
+updatedAt: 2023-10-10T16:20:54.988Z
+publishedAt: 2023-10-10T16:20:54.988Z
 firstPublishedAt: 2017-05-09T14:06:10.341Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -18,15 +18,15 @@ legacySlug: que-hacer-al-recibir-error-en-la-simulacion-de-flete
 
 Vamos a diseñar aquí el paso a paso para comprobar la configuración de Logística.
 
-Antes de empezar, vale la pena recordar que la [Simulación de Flete](/es/tutorial/simulacion-de-flete/) retorna o resultado da API de [Cálculo de Flete](https://developers.vtex.com/reference/logistics-api-overview). Recomendamos siempre el uso de las API´s. Si no tiene acceso, consulte el Administrador de su tienda y verifique qué perfil de acceso está asociado a su usuario.
+Antes de empezar, vale la pena recordar que la [Simulación de Flete](/es/tutorial/simulacion-de-flete/) retorna o resultado da API de [Cálculo de SLA](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping/calculate). Recomendamos siempre el uso de las API´s. Si no tiene acceso, consulte el Administrador de su tienda y verifique qué perfil de acceso está asociado a su usuario.
 
 Para ilustrar ese artigo crearemos un escenario en el que el producto __X-Box__ no está siendo entregado en el Código Postal 22451-451 para la política comercial 1. El mensaje de error es este: "_No fue posible generar el carrito. Vea los detalles abajo_".
 
 Hay algunos factores que pueden influir en una simulación, por lo que recomendamos siempre comenzar desde lo más básico, verificar si el __X-Box__ es un producto activo y si está con las configuraciones correctas. El camino más rápido para ello es en el [Indexed-Info](https://help.vtex.com/es/faq/por-que-o-produto-nao-aparece-no-site#indexed-info).
 
 Una vez hecho lo anterior, tenemos que chequear la Logística como una totalidad, o sea, cuál es el stock de X-Box y qué transportadora está asociada Política Comercial 1. Esa información está contenida en el Muelle.
-	
-Vía API sería también bien sencillo. Haciendo la llamada [Cálculo de Flete](https://developers.vtex.com/reference/logistics-api-overview) es fácil identificar el ID de la transportadora y así hacer el camino inverso.
+
+Vía API sería también bien sencillo. Haciendo la llamada [Cálculo de SLA](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping/calculate) es fácil identificar el ID de la transportadora y así hacer el camino inverso.
 
 Pero, ¿qué hacer para corregirlo?
 
diff --git a/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md
index a6727de1f..5d152b705 100644
--- a/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -16,7 +16,7 @@ legacySlug: que-hacer-cuando-el-aviseme-no-es-exhibido
 
 Existe un caso en que, aun con la [configuración del Avíseme](/es/tutorial/configurar-el-aviseme) hecha, el Avíseme no aparece. Es **cuando el tipo de exhibición de la categoría está seleccionado como Lista de SKUs**.
 
-![categoria-lista-de-skus ES](https://images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
+![categoria-lista-de-skus ES](//images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
 
 En este caso, además de las configuraciones estándar, es necesario usar el control `vtex.cmc:SkuSelection`, aunque no exista más de un SKU por página.
 
diff --git a/docs/faq/es/why-are-my-orders-not-integrating-with-mercado-livre.md b/docs/faq/es/why-are-my-orders-not-integrating-with-mercado-livre.md
index 1ab7ca72b..d2e0cff12 100644
--- a/docs/faq/es/why-are-my-orders-not-integrating-with-mercado-livre.md
+++ b/docs/faq/es/why-are-my-orders-not-integrating-with-mercado-livre.md
@@ -21,7 +21,7 @@ Dicho esto, el primer paso es acceder al registro de esta integración:
 1. Acceda al módulo __Marketplace__
 2. Haga clic en __Integraciones__ 
 3. Busque el __panel__ de Mercado Libre
-4. Haga clic en el __engranaje__ <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
+4. Haga clic en el __engranaje__ <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
 5. Haga clic en __Editar configuración__
 
 A partir de ahí, tenemos que rehacer el proceso de integración.
diff --git a/docs/faq/es/why-are-my-store-images-being-displayed-in-poor-quality.md b/docs/faq/es/why-are-my-store-images-being-displayed-in-poor-quality.md
new file mode 100644
index 000000000..766f1be49
--- /dev/null
+++ b/docs/faq/es/why-are-my-store-images-being-displayed-in-poor-quality.md
@@ -0,0 +1,27 @@
+---
+title: '¿Por qué las imágenes de mi tienda se muestran con baja calidad?'
+id: 5LxgbF8S2cIUOCaCO00GcK
+status: PUBLISHED
+createdAt: 2018-02-22T19:10:35.567Z
+updatedAt: 2024-04-15T15:07:36.249Z
+publishedAt: 2024-04-15T15:07:36.249Z
+firstPublishedAt: 2018-02-22T22:03:18.347Z
+contentType: frequentlyAskedQuestion
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: por-que-las-imagenes-de-mi-tienda-se-muestran-con-baja-calidad
+locale: es
+legacySlug: imagenes-con-baja-calidad
+---
+
+La disminución de la calidad de imágenes puede ocurrir durante el proceso automático de [compresión de imágenes](https://help.vtex.com/es/tutorial/compresion-de-imagenes--4klbgpsPksq44KcwqKeye8).
+
+Si utilizas fotos en formato JPG o JPEG en tu sitio web, es normal que su calidad disminuya durante la conversión a [WebP](https://developers.google.com/speed/webp?hl=es) con pérdida (lossy). Sin embargo, esta diferencia no debería ser muy notoria. Para solucionar este problema, lo mejor es volver a cargar los archivos con una resolución ligeramente mayor.
+
+Para que tu tienda muestre imágenes con colores sólidos, gráficos detallados o alto contraste, te recomendamos utilizar el formato PNG, que tiene una optimización en el mismo formato. Alternativamente, puedes utilizar la conversión a WebP sin pérdida (lossless), lo que aumenta la probabilidad de mantener la calidad del archivo original.
+
+Otra opción es utilizar imágenes preoptimizadas con herramientas de conversión a JPEG progresivo para fotos o PNG de 8 bits para ilustraciones. Así, puedes comprimir el archivo con antelación y es probable que el formato se transfiera sin que se le aplique el proceso automático de compresión.
+
+## Más información
+
+* [Compresión de imágenes](https://help.vtex.com/es/tutorial/compresion-de-imagenes--4klbgpsPksq44KcwqKeye8)
diff --git a/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md b/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md
index fc974c119..178657379 100644
--- a/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md
+++ b/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md
@@ -26,13 +26,13 @@ Una vez localizado el campo, continúe con las instrucciones:
 
 1. Acceda al módulo __Catálogo__
 2. Haga clic en __Categorías__
-![campos1](https://images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
+![campos1](//images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
 3. Haga clic en __Acciones__
 4. Seleccione __Campos (Producto)__
-![campos2](https://images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
+![campos2](//images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
 5. Encuentre el __grupo__ al que desea hacerle modificaciones. 
 6. Haga clic en __Alterar__
-![campos3](https://images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
+![campos3](//images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
 7. Después de realizar los cambios requeridos, haga clic en __Guardar__
 
 ¡Listo, campos alterados! No se olvide de guardar las configuraciones para que las alteraciones sean exhibidas en el front de la tienda.
diff --git a/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md b/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md
index 8da292bed..eb49b8a8f 100644
--- a/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md
+++ b/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md
@@ -3,8 +3,8 @@ title: '¿Por qué mi transportista no aparece en el checkout?'
 id: frequentlyAskedQuestions_165
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:09.470Z
-updatedAt: 2023-03-20T20:32:20.572Z
-publishedAt: 2023-03-20T20:32:20.572Z
+updatedAt: 2023-08-25T15:13:42.026Z
+publishedAt: 2023-08-25T15:13:42.026Z
 firstPublishedAt: 2017-04-27T23:01:43.444Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -26,6 +26,10 @@ Al momento de registrar una transportadora, es necesario incluir el [tipo de ent
 
 El checkout exhibe siempre la transportadora más rápida/barata entre las opciones de un mismo tipo de entrega. Así, una transportadora no aparece en el checkout cuando otra del mismo tipo tiene menor plazo/costo registrado.  
 
+<div class="alert alert-warning">
+Cuando hay empate entre dos transportadoras, el criterio de desempate es tener el menor costo de envío.
+</div>
+
 ### Solución
 
 Si desea que se muestren todas las transportadoras, estas deben ser registradas en el módulo de Inventario y envío como transportadoras con tipos de entrega diferentes.
diff --git a/docs/faq/es/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md b/docs/faq/es/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
index 53f5630e8..f580522da 100644
--- a/docs/faq/es/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
+++ b/docs/faq/es/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
@@ -3,8 +3,8 @@ title: '¿Por qué mi transportadora calculó flete,  para un peso menor que el
 id: frequentlyAskedQuestions_164
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:17.904Z
-updatedAt: 2019-12-31T14:25:25.374Z
-publishedAt: 2019-12-31T14:25:25.374Z
+updatedAt: 2023-12-19T16:53:24.136Z
+publishedAt: 2023-12-19T16:53:24.136Z
 firstPublishedAt: 2017-04-27T23:01:43.295Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -14,7 +14,7 @@ locale: es
 legacySlug: por-que-mi-transportadora-calculo-flete-para-un-peso-menor-que-el-minimo-configurado
 ---
 
-El cálculo del flete considera siempre dos parámetros, el peso y el volumen del producto. La prioridad de cálculo es siempre para el peso real o cúbico, vale el mayor. Sin embargo, caso el peso del producto sea menor que el mínimo catastrado para el transportista, será considerado el volumen.
+El cálculo del flete considera siempre dos parámetros, el peso y el volumen del producto. La prioridad de cálculo es siempre para el peso mínimo o cúbico, vale el mayor. Sin embargo, caso el peso del producto sea menor que el mínimo catastrado para el transportista, será considerado el volumen.
 
 ## Ejemplos
 
diff --git a/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md b/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md
index 0851e92d4..c3feea836 100644
--- a/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md
+++ b/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md
@@ -34,7 +34,7 @@ Asegúrese de que el valor se ha insertado siguiendo los pasos abajo:
 4. Acceda a la sesión __"¿Cuáles son las condiciones para la promoción sea válida?"__;
 5. Compruebe qué clústeres están registrados en __"Clúster de clientes"__;
 
-![ES - 7GcSb6BuF6JKnmGAggO3uA](https://images.ctfassets.net/alneenqid6w5/5mX30OM2efHdMldl5xHS6A/9a8352287ca7193f213098189a182abe/Cluster-promo-ES.png)
+![ES - 7GcSb6BuF6JKnmGAggO3uA](//images.ctfassets.net/alneenqid6w5/5mX30OM2efHdMldl5xHS6A/9a8352287ca7193f213098189a182abe/Cluster-promo-ES.png)
 
 6. Introduzca los __nuevos datos__;
 7. Haga clic en __Guardar__.!
diff --git a/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md b/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
index 4d29db0d3..7ad4b8c6f 100644
--- a/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
+++ b/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
@@ -22,7 +22,7 @@ Para especificar en qué tipo de entrega desea aplicar la promoción, es necesar
 2. Haga clic en el card de la promoción a que desea aplicar el envío gratis.
 3. En el ítem 3, active la flag __Tipo de carga__ y especifique cuales deben recibir el flete gratis.
 
-![promoções-campo-tipo-frete es](https://images.ctfassets.net/alneenqid6w5/4wTOYyINOgy4oGceMGmQKM/46c06b029b0e1a8fcf3f3ab48eaddf3a/promo____es-campo-tipo-frete_es.png)
+![promoções-campo-tipo-frete es](//images.ctfassets.net/alneenqid6w5/4wTOYyINOgy4oGceMGmQKM/46c06b029b0e1a8fcf3f3ab48eaddf3a/promo____es-campo-tipo-frete_es.png)
 
 Hecho esto, los tipos de flete especificados entrarán en la promoción y aparecerán para el cliente con el flete gratis disponible.
 
diff --git a/docs/faq/es/why-is-let-me-know-not-showing.md b/docs/faq/es/why-is-let-me-know-not-showing.md
index c217f112e..866615e1a 100644
--- a/docs/faq/es/why-is-let-me-know-not-showing.md
+++ b/docs/faq/es/why-is-let-me-know-not-showing.md
@@ -21,7 +21,7 @@ Las configuraciones básicas para exhibir **avíseme** cuando el producto está
 
 Pero existe un caso en que, aun con los ítems arriba configurados, el avíseme no aparece, que es **cuando el tipo de exhibición de la Categoría está seleccionado como Lista de SKUs**.
 
-![categoria-lista-de-skus ES](https://images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
+![categoria-lista-de-skus ES](//images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
 
 En este caso, además de las configuraciones estándar, es necesario usar el control `vtex.cmc:SkuSelection`, aunque no exista más de un SKU por página.
 Luego, cuando la Categoría del producto deseado esté flechada para Lista de SKUs, como en la imagen arriba, es necesario que sea insertado el control `vtex.cmc:SkuSelection` en el template de página para que el avíseme sea exhibido.
diff --git a/docs/faq/es/why-is-my-freight-value-wrong.md b/docs/faq/es/why-is-my-freight-value-wrong.md
index bc87f1480..a59de9a73 100644
--- a/docs/faq/es/why-is-my-freight-value-wrong.md
+++ b/docs/faq/es/why-is-my-freight-value-wrong.md
@@ -23,7 +23,7 @@ Se calcula el valor de flete en base a varios factores: tabla de flete, adiciona
 3. Aquí, usted verificará el valor catastrado en la plantilla más todos los [adicionales](/es/tutorial/como-se-maneja-el-adicional-de-carga) sumados a ese valor.
 4. Caso el valor todavía no este condecente con el exhibido en la tienda, siga los pasos abajo para verificar si no hay ninguna promoción alterando el valor del flete.
 
-![por-que-meu-valor-de-frete-esta-errado sp](https://images.ctfassets.net/alneenqid6w5/6Olcu5Bw88Q0Q644gQ06qQ/803b38526bb74d1fcafa2400355b8f1e/por-que-meu-valor-de-frete-esta-errado_sp.jpg)
+![por-que-meu-valor-de-frete-esta-errado sp](//images.ctfassets.net/alneenqid6w5/6Olcu5Bw88Q0Q644gQ06qQ/803b38526bb74d1fcafa2400355b8f1e/por-que-meu-valor-de-frete-esta-errado_sp.jpg)
 
 ## Promoción
 
@@ -32,4 +32,4 @@ Se calcula el valor de flete en base a varios factores: tabla de flete, adiciona
 3. Verifique el box __Valor Total__.
 4. Verifique si, entre las promociones, existe alguna con descuento en flete. Para verificar, basta que aceda la promoción del pedido y verifique el tipo de descuento.
 
-![valortotal es](https://images.ctfassets.net/alneenqid6w5/4vNJocmHWEqoqWGQgyU6Ck/d0a87594351705001565612159df9312/valortotal_es.jpg)
+![valortotal es](//images.ctfassets.net/alneenqid6w5/4vNJocmHWEqoqWGQgyU6Ck/d0a87594351705001565612159df9312/valortotal_es.jpg)
diff --git a/docs/faq/es/why-is-my-stock-negative.md b/docs/faq/es/why-is-my-stock-negative.md
index 462e90164..b236579ed 100644
--- a/docs/faq/es/why-is-my-stock-negative.md
+++ b/docs/faq/es/why-is-my-stock-negative.md
@@ -3,8 +3,8 @@ title: '¿Por qué mi inventario está negativo?'
 id: frequentlyAskedQuestions_159
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:51.880Z
-updatedAt: 2023-03-22T20:34:48.834Z
-publishedAt: 2023-03-22T20:34:48.834Z
+updatedAt: 2024-04-18T14:18:13.634Z
+publishedAt: 2024-04-18T14:18:13.634Z
 firstPublishedAt: 2017-04-27T23:01:42.612Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
diff --git a/docs/faq/es/why-is-my-stores-zoom-not-working.md b/docs/faq/es/why-is-my-stores-zoom-not-working.md
index 24e5a3a69..85650fd6a 100644
--- a/docs/faq/es/why-is-my-stores-zoom-not-working.md
+++ b/docs/faq/es/why-is-my-stores-zoom-not-working.md
@@ -25,7 +25,7 @@ Este tamaño de imagen puede configurarse por el camino abajo:
 2. Haga clic en __Configuraciones__.
 3. Acceda a la pestaña __Tipos de Archivos__.
 
-![Tipos de Arquivo ES](https://images.ctfassets.net/alneenqid6w5/4j5jxDs3lSgOmgEOgyI2KS/2321dffd3c570bba5bd73b0efba87c4e/Tipos_de_Arquivo_ES.png)
+![Tipos de Arquivo ES](//images.ctfassets.net/alneenqid6w5/4j5jxDs3lSgOmgEOgyI2KS/2321dffd3c570bba5bd73b0efba87c4e/Tipos_de_Arquivo_ES.png)
 
 El tamaño 1000x1000 significa que el zoom resultante mostrará la imagen en ese tamaño. Por tanto, éste es el tamaño mínimo para que funcione el zoom.
 
diff --git a/docs/faq/es/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md b/docs/faq/es/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
index 495f45b1b..e3f7ccef5 100644
--- a/docs/faq/es/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
+++ b/docs/faq/es/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Por qué el origen de los pedidos está diferente en VTEX y en Google Analytics?'
 id: frequentlyAskedQuestions_5030
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T22:22:57.838Z
-updatedAt: 2019-12-31T14:24:58.529Z
-publishedAt: 2019-12-31T14:24:58.529Z
+updatedAt: 2023-06-21T22:44:36.086Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:02:44.531Z
 contentType: frequentlyAskedQuestion
 productTeam: Identity
diff --git a/docs/faq/es/why-is-the-product-not-visible-on-the-website.md b/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
index 60a3dacb9..7b8fef230 100644
--- a/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
@@ -42,7 +42,7 @@ Te recomendamos que empieces tu búsqueda de errores por el **Catálogo**. Para
 1. Accede al Admin VTEX y navega hasta **Productos > Catálogo > Gestión de productos y SKU** para verificar los productos registrados en tu tienda.
 2. Busca el producto que deseas mostrar en la lista, tal como se ilustra en la imagen a continuación.
 
-    ![01-produto-es](https://images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/b7bf043742b03bd0ea130f8541a8fbad/01-produto-es.PNG)
+    ![01-produto-es](//images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/b7bf043742b03bd0ea130f8541a8fbad/01-produto-es.PNG)
 
 3. Sigue las instrucciones descriptas en las próximas secciones para verificar la información a continuación:
     * [Producto](#producto)
@@ -71,9 +71,9 @@ Para verificar la configuración del producto, es importante que sigas los pasos
     * En caso de que el producto tenga especificaciones, navega hasta la pestaña **Especificaciones** y verifica que se hayan rellenado los campos correspondientes.
 3. Luego de cualquier modificación, haz clic en `Guardar`.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/nGAGYNdVtTFdAPjW1mi5f/ad8fd616f6245872af18ad98d1c9f4a6/02-campos-produto-es.png" alt="02-campos-produto-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Campos que se deben verificar en la página de información del producto</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/nGAGYNdVtTFdAPjW1mi5f/ad8fd616f6245872af18ad98d1c9f4a6/02-campos-produto-es.png" alt="02-campos-produto-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Campos que se deben verificar en la página de información del producto</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/6UXDapFf9bvtnCSoHQBwZC/1933479b0f82ec9229bdf1687859a714/03-aba-especificacoes-es.png" alt="03-aba-especificacoes-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Pestaña <strong>Especificaciones</strong></em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/6UXDapFf9bvtnCSoHQBwZC/1933479b0f82ec9229bdf1687859a714/03-aba-especificacoes-es.png" alt="03-aba-especificacoes-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Pestaña <strong>Especificaciones</strong></em></figcaption></figure>
 
 ### SKU
 
@@ -85,16 +85,16 @@ En la página de SKU, en **Productos > Catálogo > Gestión de productos y SKU**
 
     | Botón | Descripción |
     |-|-|
-    | ![04-botao-precos](https://images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acceder a la __Lista de precios__ para verificar si existe un precio válido para la política comercial deseada que esté asociado a los SKU del producto. Consulta la sección de [Precios](#precios) para más información. |
-    | ![05-botao-logistica](https://images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acceder a la página __Gestión del stock__ para verificar si el SKU tiene stock disponible. Consulta la sección de [Logística](#logistica) para más información. |
-    | ![06-botao-indexed-info](https://images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite ver a cada **_seller_** que comercializa el SKU, la política comercial (**Policy**), el precio (**Value**) y la cantidad de SKU en stock (**Quantity**). |
+    | ![04-botao-precos](//images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acceder a la __Lista de precios__ para verificar si existe un precio válido para la política comercial deseada que esté asociado a los SKU del producto. Consulta la sección de [Precios](#precios) para más información. |
+    | ![05-botao-logistica](//images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acceder a la página __Gestión del stock__ para verificar si el SKU tiene stock disponible. Consulta la sección de [Logística](#logistica) para más información. |
+    | ![06-botao-indexed-info](//images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite ver a cada **_seller_** que comercializa el SKU, la política comercial (**Policy**), el precio (**Value**) y la cantidad de SKU en stock (**Quantity**). |
 
 2. En la línea del producto correspondiente al SKU que se verificará, haz clic en la flecha hacia abajo <i class="fas fa-caret-down"></i>, al lado del botón `Modificar`.
 3. Haz clic en la opción** SKU** para acceder a la lista detallada de los SKU.
 4. En la columna **Status**, verifica que el status indicado sea `Activo`. Si los SKU están activos, continúa con el paso 7.
 5. Si algún SKU está con el status `Inactivo`, haz clic en `Modificar` para ver la información detallada del SKU.
 
-    ![07-catalogo-skus-es](https://images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/720d48a725fe4740f78466149846d29a/07-catalogo-skus-es.png)
+    ![07-catalogo-skus-es](//images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/720d48a725fe4740f78466149846d29a/07-catalogo-skus-es.png)
 
 6. En la página de información del SKU, el próximo paso es verificar los ítems que se enumeran a continuación.
     * **Activar SKU si es posible:** verifica si esta opción está seleccionada. De lo contrario, el SKU no se mostrará. Activar esta opción significa determinar que el SKU se activará si cumple con los requisitos necesarios:
@@ -107,9 +107,9 @@ En la página de SKU, en **Productos > Catálogo > Gestión de productos y SKU**
 8. Verifica si el SKU incluye al menos una imagen. Si no la tiene, el SKU no se activará. Realiza el paso a continuación para corregir este problema.
 9. Haz clic en `Insertar` para subir una imagen nueva. Si lo prefieres, haz clic en `Asociar a las imágenes existentes` para incluir una imagen que ya se utilice en otro SKU.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/1be699da86b880750f7884f9aabaa8a3/08-aba-imagens-es.png" alt="08-aba-imagens-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Pestaña  <strong>Imágenes</strong></em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/1be699da86b880750f7884f9aabaa8a3/08-aba-imagens-es.png" alt="08-aba-imagens-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Pestaña  <strong>Imágenes</strong></em></figcaption></figure>
 
-![09-sku-imagens-es](https://images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/06bad0f8081c24488cee7ec6d0853853/09-sku-imagens-es.PNG)
+![09-sku-imagens-es](//images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/06bad0f8081c24488cee7ec6d0853853/09-sku-imagens-es.PNG)
 
 ### Información indexada
 
@@ -123,13 +123,13 @@ El registro de indexación muestra el status de cada SKU del producto. Si hay al
 
 En el ejemplo a continuación, podemos llegar a la conclusión de que el SKU no está disponible por falta de ítems en el stock:
 
-![10-indexed-info-code](https://images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/eade8a30097193dabb38a1085d28defa/Group_1__7_.png)
+![10-indexed-info-code](//images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/eade8a30097193dabb38a1085d28defa/Group_1__7_.png)
 
 A partir de esto, es posible tomar medidas para corregir el problema. En el caso del ejemplo, sería necesario ajustar el número de ítems en el stock del sistema de [Logística](#logistica).
 
 Un SKU activo y sin errores tendrá el registro en el indexador parecido al que se muestra a continuación:
 
-![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/059ed660c68d5e05fbe5f2ac0c571326/11-indexed-info-code-active.png)
+![11-indexed-info-code-active](//images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/059ed660c68d5e05fbe5f2ac0c571326/11-indexed-info-code-active.png)
 
 <div class="alert alert-info">
 <p>Si la información de la indexación no muestra ningún motivo para la falta de disponibilidad de los productos, y si no encontraste ningún error en el registro de los productos y SKU, probablemente lo que resuelva el problema sea volver a indexar el producto.</p>
@@ -147,7 +147,7 @@ En el módulo de **Precios**, es importante verificar que los SKU del producto t
 
 En el ejemplo a continuación, hay dos SKU sin precio base registrado. Es por esto que no hay un precio ingresado en la columna de la política comercial. Solo aparece la información _Precio no registrado_.
 
-![12-precos-es](https://images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/35266b55e248d148f419219696f5b661/12-precos-es.PNG)
+![12-precos-es](//images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/35266b55e248d148f419219696f5b661/12-precos-es.PNG)
 
 ### Crear precio base
 
@@ -175,7 +175,7 @@ El **Simulador de envío** sirve para verificar si el ítem está en stock y si
 2. Completa la información necesaria que se describe en el [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144).
 3. Haz clic en `Simulación de envío`.
 
-![13-simular-frete-es](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/9d99f84da1c2fa38d8457f1668eb4a5f/13-simular-frete-es.PNG)
+![13-simular-frete-es](//images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/9d99f84da1c2fa38d8457f1668eb4a5f/13-simular-frete-es.PNG)
 
 <div class="alert alert-info">
 <p>Para revisar un ítem específico, debes realizar la simulación con un <strong>código postal</strong> que cubra todas las <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">políticas de envío</a> registradas. Así sabrás que si un ítem no está disponible para ese CP, tampoco lo estará para algún otro.</p>
@@ -183,7 +183,7 @@ El **Simulador de envío** sirve para verificar si el ítem está en stock y si
 
 El resultado obtenido indica si el producto está disponible o no para ser entregado en la dirección informada y cuáles son las mejores opciones de envío. Ejemplo: si no hay ítems suficientes disponibles en stock, el simulador mostrará el siguiente mensaje:
 
-![14-simulador-motivos-es](https://images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/2edfa46661ba21558a2d9ee2c5507a67/14-simulador-motivos-es.PNG)
+![14-simulador-motivos-es](//images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/2edfa46661ba21558a2d9ee2c5507a67/14-simulador-motivos-es.PNG)
 
 Para más información sobre cómo usar el simulador, consulta el tutorial [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144).
 
@@ -204,7 +204,7 @@ Si un producto no está disponible en el sitio web por falta de _ítems_ en el _
 3. Para actualizar el recuento de stock, escribe la cantidad actual en la columna **Actualizar recuento** en la línea del SKU deseado, según la imagen a continuación.
 4. Haz clic en `Guardar`.
 
-![15-gerenciar-inventario-es](https://images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/f8fcc9989836959c1c300c332bffb91e/15-gerenciar-inventario-es.gif)
+![15-gerenciar-inventario-es](//images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/f8fcc9989836959c1c300c332bffb91e/15-gerenciar-inventario-es.gif)
 
 Para más información, consulta el tutorial [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139).
 
@@ -249,7 +249,7 @@ Sigue los pasos a continuación para verificar la plantilla que está usando tu
 
     En el ejemplo a continuación, la plantilla estándar que se usó es `vtex.curbside-pickup@0.x:store.curbside-pickup` y no hay una plantilla condicional.
 
-    ![16-templates-cms-es](https://images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/c23d4524c1339d0f952613f13c4c3cac/16-templates-cms-es.PNG)
+    ![16-templates-cms-es](//images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/c23d4524c1339d0f952613f13c4c3cac/16-templates-cms-es.PNG)
 
 4. Luego, debes configurar los bloques incluidos en la plantilla utilizada, tal como se indica en [Templates](#templates).
 
diff --git a/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
index 2617eca32..2454feb0d 100644
--- a/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
@@ -25,6 +25,6 @@ Para activar esta configuración:
 3. Haz clic en **Editar** en la línea `Producto - Thumb`.
 4. En el panel que aparece, se puede elegir el tamaño máximo del archivo para las imágenes en miniaturas en el campo **Tamaño máximo en KB**.
 
-![Configuración de tipo de archivo en CMS](https://images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/3eb78e622efb3066eee570dc342c1a20/ES.PNG)
+![Configuración de tipo de archivo en CMS](//images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/3eb78e622efb3066eee570dc342c1a20/ES.PNG)
 
 También te recomendamos que leas el artículo [Mejorar la performance de imágenes de productos](https://help.vtex.com/pt/tutorial/improving-the-performance-of-product-images/) para aprender cómo mejorar la calidad de cualquier imagen de la tienda reduciendo al máximo cualquier alteración en la performance de la carga de la página.
diff --git a/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index ad15c1c30..88c87fcac 100644
--- a/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -21,7 +21,7 @@ Siga estos pasos para validar la información:
 1. Acceda al Admin de su tienda: `https://{AccountName}.myvtex.com/admin`.
 2. En el menú lateral del Admin, haga clic en __Master Data__.
 3. En el cuadro __Profile System__, haga clic en __Clientes__.
-4. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+4. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 5. Haga clic en el registro del cliente para acceder a los detalles del perfil.
 
 En la sección __Contato__, usted verá que la opción `Es Empresa?` Se llena con el valor `No`. Al mismo tiempo, en la sección __Datos de la empresa__, usted verá que el campo `Tipo documento` tiene el valor `cnpj`.
diff --git a/docs/faq/es/why-was-the-item-splitted-in-the-cart.md b/docs/faq/es/why-was-the-item-splitted-in-the-cart.md
index d2eced698..2d4a0cc72 100644
--- a/docs/faq/es/why-was-the-item-splitted-in-the-cart.md
+++ b/docs/faq/es/why-was-the-item-splitted-in-the-cart.md
@@ -3,8 +3,8 @@ title: 'Por qué se separó el producto en el carrito?'
 id: frequentlyAskedQuestions_350
 status: PUBLISHED
 createdAt: 2017-04-27T22:37:20.610Z
-updatedAt: 2019-12-31T14:24:24.843Z
-publishedAt: 2019-12-31T14:24:24.843Z
+updatedAt: 2023-07-12T18:31:38.375Z
+publishedAt: 2023-07-12T18:31:38.375Z
 firstPublishedAt: 2017-04-27T23:01:45.290Z
 contentType: frequentlyAskedQuestion
 productTeam: Shopping
@@ -14,13 +14,13 @@ locale: es
 legacySlug: por-que-se-separo-el-producto-del-carrito
 ---
 
-Este escenario sucede cuando más de un artículo del mismo SKU se separa en más de una línea en el carrito.
+Este escenario sucede cuando más de un artículo del mismo SKU se separa en más de una línea en el carrito. Esto ocurre por una acción llamada "prorrateo" - es la división de un valor entre artículos.
 
-Esto ocurre por una acción llamada "prorrateo" - es la división de un valor entre artículos. Pero hay escenarios en que el importe de descuento es indivisible por el número de artículos, especialmente en los casos en que el SKU tiene una unidad de multiplicación, por lo que necesitamos dar diferentes descuentos para los artículos del mismo SKU, de manera que el importe de descuento sea correcto. Lo que termina dejando los precios diferentes y separando cada unidad en una fila. Vea mejor esta explicación con el siguiente ejemplo.
+Pero hay escenarios en que el importe de descuento es indivisible por el número de artículos, especialmente en los casos en que el SKU tiene una unidad de multiplicación, por lo que necesitamos dar diferentes descuentos para los artículos del mismo SKU, de manera que el importe de descuento sea correcto. Lo que termina dejando los precios diferentes y separando cada unidad en una fila. Vea mejor esta explicación con el siguiente ejemplo.
 
-![](//images.contentful.com/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/65984bd4a878563818fa92d1f58a0db9/Por_que_o_item_do_carrinho_foi_separado.jpg)
+![Por que o item do carrinho foi separado](//images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/4e46b5b17ed4c3eeb1cfba4e3440d845/Por_que_o_item_do_carrinho_foi_separado.jpg)
 
-1. Unidad de multiplicación;
-2. Precio del producto después del descuento;
-3. Precio del producto con la diferencia debido al prorrateo;
+1. Unidad de multiplicación.
+2. Precio del producto después del descuento.
+3. Precio del producto con la diferencia debido al prorrateo.
 4. Descuento aplicado.
diff --git a/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 8da2b358c..f75615794 100644
--- a/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -18,7 +18,7 @@ Existe una regla de seguridad en el Checkout que está relacionada con la facili
 
 Como el SmartCheckout permite cerrar una compra sólo con el email y con el CVV de la tarjeta, si el cliente ya ha finalizado la compra anteriormente, limitamos la cantidad de finalización de compra sin éxito a 3. Depois de eses 3 intentos, solicitamos el login del cliente.
 
-![LoginES](https://images.ctfassets.net/alneenqid6w5/3iJKRBnU00IAwu24SMey0y/50a69e45f7f1a8380e0299490fb58603/LoginES.png)
+![LoginES](//images.ctfassets.net/alneenqid6w5/3iJKRBnU00IAwu24SMey0y/50a69e45f7f1a8380e0299490fb58603/LoginES.png)
 
 O sea, en el caso de que el cliente finalice la compra tan sólo con el email y el CVV de la tarjeta de crédito y la autorización de la operadora no ocurra en hasta 3 veces seguidas, es mostrada la pantalla de login para que el cliente siga intentando comprar. Ese conteo vuelve al inicio cuando el cliente inicia sesión y completa con éxito su compra.
 
diff --git a/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md b/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md
index 145a777ee..b77c277a9 100644
--- a/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md
+++ b/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md
@@ -16,7 +16,7 @@ legacySlug: por-que-la-promocion-no-fue-aplicada-em-el-marketplace
 
 Para crear una promoción para marketplaces, el escenario es casi el mismo de una promoción común. Sin embargo, se debe seleccionar en el campo **política comercial** el valor **Tienda(s) de tercero(s)** y seleccionar la **política comercial** usada por el marketplace o llenar el campo **afiliado** con el ID del marketplace.
 
-![marketplace.ess](https://images.ctfassets.net/alneenqid6w5/1eKWkGJX4m9jrQC971dxJH/50bec937a116cdd40cdcd26fc6c337ce/marketplace.ess.png)
+![marketplace.ess](//images.ctfassets.net/alneenqid6w5/1eKWkGJX4m9jrQC971dxJH/50bec937a116cdd40cdcd26fc6c337ce/marketplace.ess.png)
 
 Para obtener más información sobre cómo hacerlo, lea nuestro [artículo sobre cómo crear promoción para el marketplace](/es/tutorial/promocion-para-marketplace).
 
diff --git a/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
index 56fa2bdbd..1929b0e69 100644
--- a/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -29,11 +29,11 @@ Para configurar o [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
 1. Abra o [Google Chrome](https://www.google.com/intl/pt-BR/chrome/) no seu computador.
 2. Clique no botão `F12` do seu teclado ou com o botão direito do mouse em qualquer lugar da tela e selecione **Inspecionar**.
 3. Clique nos três pontos verticais na parte superior direita da página, conforme indicado na imagem abaixo.
-![Customizations1 - PT](https://images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/cb8f01010eb287fcc5b63f2b9956a2ad/Captura_de_Tela_2022-09-20_a__s_14.51.15.png)
+![Customizations1 - PT](//images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/cb8f01010eb287fcc5b63f2b9956a2ad/Captura_de_Tela_2022-09-20_a__s_14.51.15.png)
 4. Selecione **Mais ferramentas** e, em seguida, **Bloqueios de solicitação de rede** para bloquear todas as customizações feitas via CSS, JavaScript e Google Tag Manager. 
-![Customizations2 - PT](https://images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/cee054457174fb6309d84826753d7411/Captura_de_Tela_2022-09-20_a__s_14.59.20.png)
+![Customizations2 - PT](//images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/cee054457174fb6309d84826753d7411/Captura_de_Tela_2022-09-20_a__s_14.59.20.png)
 5. A aba **Bloqueios de solicitação de rede** abrirá em seguida como mostra a imagem abaixo:
-![Customizations3 - PT](https://images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/8eaa7683eaccc0f4af13088a328c022b/Captura_de_Tela_2022-09-20_a__s_15.00.47.png)
+![Customizations3 - PT](//images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/8eaa7683eaccc0f4af13088a328c022b/Captura_de_Tela_2022-09-20_a__s_15.00.47.png)
 6. Clique em `Adicionar padrão` para definir o primeiro recursos será bloqueado. Para adicionar mais recursos, clique em `+` e, depois de defini-lo, clique em `Adicionar`. Essa configuração precisa ser feita apenas uma vez no seu navegador. Inclua os itens abaixo:
 
  * `*/arquivos/*.js`
@@ -42,7 +42,7 @@ Para configurar o [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
  * `*/files/*.css`
  * `*gtm.js*`
 
-![Customizations4 - PT](https://images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/021f16c927cedf17ec8c8410b447c026/Captura_de_Tela_2022-09-20_a__s_15.14.39.png)
+![Customizations4 - PT](//images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/021f16c927cedf17ec8c8410b447c026/Captura_de_Tela_2022-09-20_a__s_15.14.39.png)
 <ol start ="7">
 <li>Marque a opção <b>Ativar bloqueio de solicitação de rede</b> e habilite todos os checkboxes abaixo. Essa será a configuração que ficará definida por padrão, com todas as opções habilitadas para bloqueio.</li>
 <li>Agora atualize a página. Ela será exibida sem os componentes customizados.</li>
diff --git a/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
index 60d0ee256..36fb365b2 100644
--- a/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -31,7 +31,7 @@ Por isso, para ter acesso ao change seller, a afiliação com split deve ser con
 - __Use O Comportamento Recomendado Pelo Processador de Pagamentos__.
 - __Desativado: Não Capturado Automaticamente__.
 
-![Captura automática de pagamento](https://images.ctfassets.net/alneenqid6w5/6oARqXfu6KSJ6g8ZH4069P/cf5b21c4ecb29930d9e52d7df430d60c/Captura_Autom__tica.png)
+![Captura automática de pagamento](//images.ctfassets.net/alneenqid6w5/6oARqXfu6KSJ6g8ZH4069P/cf5b21c4ecb29930d9e52d7df430d60c/Captura_Autom__tica.png)
 
 ### Selecionando o comportamento de liquidação não automática, quando o pagamento será liquidado?
 
diff --git a/docs/faq/pt/fix-redirect-error-in-pagseguro.md b/docs/faq/pt/fix-redirect-error-in-pagseguro.md
index 276623fb1..580f53633 100644
--- a/docs/faq/pt/fix-redirect-error-in-pagseguro.md
+++ b/docs/faq/pt/fix-redirect-error-in-pagseguro.md
@@ -3,8 +3,8 @@ title: 'Corrigir erro de redirecionamento no PagSeguro'
 id: 5b1lVDQ9HUKQs4Wy24uWq2
 status: PUBLISHED
 createdAt: 2018-02-15T16:07:47.669Z
-updatedAt: 2019-12-31T14:23:59.281Z
-publishedAt: 2019-12-31T14:23:59.281Z
+updatedAt: 2024-02-16T12:41:04.461Z
+publishedAt: 2024-02-16T12:41:04.461Z
 firstPublishedAt: 2018-02-15T17:26:16.189Z
 contentType: frequentlyAskedQuestion
 productTeam: Financial
@@ -14,24 +14,24 @@ locale: pt
 legacySlug: corrigir-erro-de-redirecionamento-no-pagseguro
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Caso você esteja encontrando __problemas de redirecionamento__ utilizando o Pagseguro, é provável que o *redirect* do PagSeguro esteja configurado de forma errada.
 
 Para corrigir o problema, há duas opções: Configurar o PagSeguro *com redirect* da forma correta ou configurar o PagSeguro *sem redirect*. 
 
 ## Configurar o PagSeguro *com redirect*
 
-### Configurar Afiliação de Gateway PagSeguro
+### Configurar Gateway PagSeguro
 
-1. Acesse a seção de __Pagamentos__.
-2. Clique no botão __Configurações__.
-3. Clique na aba __Afiliações de Gateways__.
-4. Clique no botão __+__ no canto superior direito da tela.
-5. Clique na afiliação __PagSeguro__.
-6. Preencha os campos __email__ e __token__ com as informações fornecidas pelo PagSeguro.
-7. Siga a orientação __Configuração do redirecionamento__ descrita no painel de configuração.
-8. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagSeguro__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __email__ e __token__ com as informações fornecidas pelo PagSeguro.
+5. Siga a orientação __Configuração do redirecionamento__ descrita no painel de configuração.
+6. Clique em `Salvar`.
 
-### Configurar Condição de Pagamento PagSeguro
+### Configurar condição de pagamento PagSeguro
 
 1. Depois de configurar corretamente a Afiliação de Gateway no passo anterior, clique na aba __Condições de Pagamento__.
 2. Clique no botão __+__ no canto superior direito da tela.
@@ -43,7 +43,7 @@ Para corrigir o problema, há duas opções: Configurar o PagSeguro *com redirec
 
 ## Configurar o PagSeguro *sem redirect*
 
-### Configurar afiliação de gateway PagSeguro sem redirect
+### Configurar gateway PagSeguro sem redirect
 
 1. Acesse a seção de __Pagamentos__.
 2. Clique no botão __Configurações__.
diff --git a/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md b/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md
index 2bb662dbf..7bcd9be55 100644
--- a/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md
+++ b/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md
@@ -24,4 +24,4 @@ NSU e TID são dados de pagamento que ficam registrados em __Pagamentos__, na se
 
 Essas informações são informadas à VTEX durante as transações e são organizadas para uma simples visualização em **+ Informações**, no [detalhe do pedido](/pt/tutorial/como-visualizar-detalhes-do-pedido "detalhe do pedido"), conforme imagem abaixo:
 
-![mais-informações-detalhes-pedido pt](https://images.ctfassets.net/alneenqid6w5/5SaZEE8HcJHaXfdahYfueX/aae0b71aea18bd58876bdf3b5af7ca4e/mais-informa____es-detalhes-pedido_pt.png)
+![mais-informações-detalhes-pedido pt](//images.ctfassets.net/alneenqid6w5/5SaZEE8HcJHaXfdahYfueX/aae0b71aea18bd58876bdf3b5af7ca4e/mais-informa____es-detalhes-pedido_pt.png)
diff --git a/docs/faq/pt/how-does-vtex-support-work.md b/docs/faq/pt/how-does-vtex-support-work.md
index 1faf652d7..9e5037a3e 100644
--- a/docs/faq/pt/how-does-vtex-support-work.md
+++ b/docs/faq/pt/how-does-vtex-support-work.md
@@ -3,8 +3,8 @@ title: 'Como funciona o suporte da VTEX?'
 id: 3kACEfni4m8Yxa1vnf2ebe
 status: PUBLISHED
 createdAt: 2019-03-10T19:06:12.818Z
-updatedAt: 2022-12-23T15:50:55.141Z
-publishedAt: 2022-12-23T15:50:55.141Z
+updatedAt: 2024-01-08T19:15:40.782Z
+publishedAt: 2024-01-08T19:15:40.782Z
 firstPublishedAt: 2019-03-10T19:08:36.723Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -16,6 +16,8 @@ legacySlug: planos-de-suporte
 
 Na VTEX, compartilhamos a responsabilidade pelo sucesso dos nossos clientes. Nossos planos de suporte permitem que você receba o nível adequado de atenção e expertise para fazer o melhor uso da plataforma e desenvolver o seu negócio. Com isso, você pode mitigar os riscos da sua operação digital e manter seus custos operacionais sob controle. 
 
+<div class="alert alert-info">É necessário <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">habilitar a autorização de suporte</a> no <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">License Manager</a> para que o usuário tenha acesso ao Suporte da VTEX. Esta configuração é válida apenas para contas no Brasil.</div>
+
 ## Suporte	
 
 Todos os clientes têm acesso a atendimento fornecido por nosso time de especialistas do time de Suporte. Estes especialistas estão preparados para proporcionar a melhor experiência possível para a solução dos chamados. Para contatá-los, é necessário [abrir um chamado por meio do sistema de tickets](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt).
@@ -32,11 +34,11 @@ Enquanto seu ticket não é solucionado, você pode acompanhar o status dele pel
 
 Para melhor atender clientes globais em diferentes países, nosso time de Customer Excellence funciona de forma independente por região. Cada região tem autonomia para definir a organização e disponibilidade do seu time, o nível de serviço (SLA de atendimento) e os recursos adicionais de suporte:
 
-- América Latina (LATAM, ex. Brasil)
+- América Latina (LATAM)
 - Ásia-Pacífico (APAC)
 - [Brasil](/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)
 - [Estados Unidos (EUA)](/en/faq/vtex-support-united-states--Bm45YFp68QRe1Z5r2oa07)
-- Europa, Oriente Médio e África (EMEA)
+- [Europa, Oriente Médio e África (EMEA)](https://help.vtex.com/faq/suporte-vtex-emea--5ePu2qkCfmE0IEKDFKg53F)
 
 ### Pesquisa de Satisfação
 
@@ -48,14 +50,10 @@ Para acessá-la, vá até o menu __Configurações da Conta__ e clique em __Pesq
 
 ### Monitoramento em tempo real
 
-Prezamos pela transparência quanto à integridade dos nossos sistemas. Por isso, sempre que houver um problema crítico que afete vendas das lojas ou impacte o funcionamento da plataforma, faremos a comunicação proativa com clientes e parceiros por meio de três canais:
-
-- O painel [Healthcheck](http://healthcheck.vtex.com/) apresenta módulos responsáveis pelo monitoramento de cada serviço da VTEX em tempo real. Exibimos um indicador do funcionamento de cada módulo e o horário da última atualização, alertando quando algum recurso estiver indisponível ou com funcionamento degradado. 
+Prezamos pela transparência quanto à integridade dos nossos sistemas. Por isso, sempre que houver um problema crítico que afete vendas das lojas ou impacte o funcionamento da plataforma, faremos a comunicação proativa com clientes e parceiros por meio dos canais a seguir:
 
 - A página de [Status](https://status.vtex.com/) exibe uma linha do tempo com o histórico recente de incidentes do sistema. Nesse histórico, detalhamos as informações de cada incidente: o que aconteceu, quais módulos foram afetados, a sequência de ações até sua resolução e um resumo do ocorrido ao final.
 
-- A página de [Releases](https://releases.vtex.com/) exibe uma linha do tempo, detalhada por módulo e versão, de todas atualizações feitas nos ambientes stable e beta.
-
 Tomaremos todas as providências cabíveis para resolver a situação o quanto antes e garantir o cumprimento do nosso [SLA](https://help.vtex.com/pt/tutorial/o-que-e-o-sla-de-operacao-da-plataforma--2cIFrsY5S8usk84OU4QOKm?locale=pt) previsto em contrato.
 
 ### Help Center
@@ -70,10 +68,7 @@ Neste [portal para desenvolvedores](https://developers.vtex.com), você encontra
 
 No painel administrativo temos nosso canal de comunicação de atualizações no produto, em que publicamos comunicados sempre que alguma funcionalidade nova é lançada ou alguma ação é necessária para evitar uma interrupção de serviço. Estes comunicados também estão disponíveis na seção de [Novidades](https://help.vtex.com/pt/announcements) do Help Center.
 
-Atualizações técnicas, voltadas para desenvolvedores e parceiros, são publicadas na seção de [Release Notes](https://developers.vtex.com/changelog) do Developer Portal. Isso inclui atualizações nas APIs, novos guias de desenvolvimento e comunicados sobre o VTEX IO.
+Atualizações técnicas, voltadas para desenvolvedores e parceiros, são publicadas na seção de [Release Notes](https://developers.vtex.com/updates/release-notes) do Developer Portal. Isso inclui atualizações nas APIs, novos guias de desenvolvimento e comunicados sobre o VTEX IO.
 
 Lançamentos que tenham uma relevância maior para o mercado, como novos produtos, novos recursos de grande impacto para produtos existentes e atualizações da empresa são divulgados no [Blog](https://vtex.com/pt-br/category/produto/) e na newsletter mensal do produto.
 
-## Serviços adicionais sob demanda
-
-Para as situações em que nossos clientes precisam de um auxílio maior para projetos mais complexos, oferecemos serviços de consultoria de projetos. Caso haja interesse, seu Customer Success Manager poderá orientá-lo sobre as alternativas disponíveis e fazer o direcionamento interno da demanda para os times responsáveis.
diff --git a/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md b/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md
index 006608653..67153d3bd 100644
--- a/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md
+++ b/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md
@@ -31,7 +31,7 @@ Confira abaixo como realizar esse processo:
 4. Vá para a seção __Quais as condições para a promoção ser válida?__.
 5. Insira o código do cupom em __utm_source__.
 
-  ![Sincronizar promoções no mesmo cupom - 1 - PT](https://images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/070d7f66702c0c4c71fa1431b3d896fc/7yJhwPnclx3tCiJdgpcYyv_-_PT.png)
+  ![Sincronizar promoções no mesmo cupom - 1 - PT](//images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/070d7f66702c0c4c71fa1431b3d896fc/7yJhwPnclx3tCiJdgpcYyv_-_PT.png)
 
 6. Clique em `Criar cupom a partir das UTMs acima`.
 7. Clique em `Salvar`.
@@ -39,6 +39,6 @@ Confira abaixo como realizar esse processo:
 9. Repita o processo com a segunda promoção regular.
 10. Ao final, ambas as promoções devem apresentar a mesma UTM.
 
-  ![Sincronizar promoções no mesmo cupom - 2 - PT](https://images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/4aebcc54458e4661a94360cf6d9f566a/5nhdQy1Y4YWs4pHHokSA44_-_PT.png)
+  ![Sincronizar promoções no mesmo cupom - 2 - PT](//images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/4aebcc54458e4661a94360cf6d9f566a/5nhdQy1Y4YWs4pHHokSA44_-_PT.png)
 
 Desse modo, o cliente pode abater os dois valores antes de finalizar a compra. 
diff --git a/docs/faq/pt/how-to-edit-a-whatsapp-link.md b/docs/faq/pt/how-to-edit-a-whatsapp-link.md
index 1b8461129..5c671cfd2 100644
--- a/docs/faq/pt/how-to-edit-a-whatsapp-link.md
+++ b/docs/faq/pt/how-to-edit-a-whatsapp-link.md
@@ -18,7 +18,7 @@ No painel da **VTEX Assisted Sales (SuiteShare)**, acesse a opção _**Atrair >
 
 Na nova página, localize o link que você deseja editar, clique na seta localizada no lado direito e clique na opção **Editar**. 
 
-![LinkWhatsapp](https://images.ctfassets.net/alneenqid6w5/4o2p2Hz94PIONgv9fK3Wzs/ac8052b0a1343b7437699b3ce1318d22/LinkWhatsapp.png)
+![LinkWhatsapp](//images.ctfassets.net/alneenqid6w5/4o2p2Hz94PIONgv9fK3Wzs/ac8052b0a1343b7437699b3ce1318d22/LinkWhatsapp.png)
 
 Pronto, basta editar a opção desejada. 
 
diff --git a/docs/faq/pt/how-to-find-facebook-pixel.md b/docs/faq/pt/how-to-find-facebook-pixel.md
index f9f0f9f4a..0ac44adbc 100644
--- a/docs/faq/pt/how-to-find-facebook-pixel.md
+++ b/docs/faq/pt/how-to-find-facebook-pixel.md
@@ -16,16 +16,16 @@ legacySlug: como-encontrar-pixel-do-facebook
 
 Para começar a capturar dados do público por meio do Link Manager, você precisa configurar os pixels para cada uma das suas plataformas de publicidade. Para encontrar seu ID de pixel no Facebook, siga as instruções abaixo. Não tem um pixel do Facebook configurado? [Siga as instruções aqui para começar](https://www.facebook.com/business/help/952192354843755).
 
-![Pixel Facebook](https://images.ctfassets.net/alneenqid6w5/SyRmwIJcSHT6hub7cHL0i/57094d247c03c7768144dce07fc4f88c/Facebook1.png)
+![Pixel Facebook](//images.ctfassets.net/alneenqid6w5/SyRmwIJcSHT6hub7cHL0i/57094d247c03c7768144dce07fc4f88c/Facebook1.png)
 
 Faça o login no Facebook e vá para sua conta do Gerenciador de Anúncios.
 
 Abra a barra de navegação e selecione Gerenciador de eventos.
 
-![Gerenciador de Negócios Facebook](https://images.ctfassets.net/alneenqid6w5/2zRxhjDHyVTj1VqTOKjnP3/ff5aa015c1ca8809ce3cf43b2c2e4644/Facebook2.png)
+![Gerenciador de Negócios Facebook](//images.ctfassets.net/alneenqid6w5/2zRxhjDHyVTj1VqTOKjnP3/ff5aa015c1ca8809ce3cf43b2c2e4644/Facebook2.png)
 
 Copie o Pixel ID do pixel que você deseja usar.
 
-![Pixel ID](https://images.ctfassets.net/alneenqid6w5/1ViWYddvpIbNYruMIjG9Xx/aa38ac1dc6d812a86e7a962752d59369/Facebook3.png)
+![Pixel ID](//images.ctfassets.net/alneenqid6w5/1ViWYddvpIbNYruMIjG9Xx/aa38ac1dc6d812a86e7a962752d59369/Facebook3.png)
 
 Pronto! Agora você poderá adicionar o seu Pixel do Facebook na opção de _**Atrair > Remarketing**_ da **VTEX Assisted Sales (SuiteShare)**.
diff --git a/docs/faq/pt/how-to-find-google-analytics-pixel.md b/docs/faq/pt/how-to-find-google-analytics-pixel.md
index 6422975fa..aa10ace25 100644
--- a/docs/faq/pt/how-to-find-google-analytics-pixel.md
+++ b/docs/faq/pt/how-to-find-google-analytics-pixel.md
@@ -16,11 +16,11 @@ legacySlug: como-encontrar-o-pixel-do-google-analytics
 
 Para encontrar o ID de acompanhamento faça login na sua conta do [Analytics](https://analytics.google.com/analytics/web/#/).
 
-![GoogleAnalyticsLogo](https://images.ctfassets.net/alneenqid6w5/1ahGCXWIcYa4uTIo9RCtLO/bc57ebf9e9eed16c22431dc6b06939d0/GoogleAnalyticsLogo.png)
+![GoogleAnalyticsLogo](//images.ctfassets.net/alneenqid6w5/1ahGCXWIcYa4uTIo9RCtLO/bc57ebf9e9eed16c22431dc6b06939d0/GoogleAnalyticsLogo.png)
 
 Clique em **Administrador**. 
 
-![GoogleAnalytics_menu](https://images.ctfassets.net/alneenqid6w5/7weyAzsvGxyeYyU4EHA9JG/7b761daaf7806248de5d6f259da52a3d/GoogleAnalytics_menu.png)
+![GoogleAnalytics_menu](//images.ctfassets.net/alneenqid6w5/7weyAzsvGxyeYyU4EHA9JG/7b761daaf7806248de5d6f259da52a3d/GoogleAnalytics_menu.png)
 
 Selecione uma conta no menu na coluna conta.
 
@@ -28,6 +28,6 @@ Selecione uma propriedade no menu na coluna propriedade.
 
 Em propriedade, clique em Informações de rastreamento e depois em Código de acompanhamento. Seu ID de rastreamento é exibido na parte superior da página.
 
-![GoogleAnalytics_informações de acompanhamento](https://images.ctfassets.net/alneenqid6w5/7Dz2GrDyXgbGmS49YMcZ7S/627ff46b8b3e2656d270b6ea11ace913/GoogleAnalytics_informa____es_de_acompanhamento.png)
+![GoogleAnalytics_informações de acompanhamento](//images.ctfassets.net/alneenqid6w5/7Dz2GrDyXgbGmS49YMcZ7S/627ff46b8b3e2656d270b6ea11ace913/GoogleAnalytics_informa____es_de_acompanhamento.png)
 
 Pronto! Agora você poderá adicionar o seu Pixel do Google Analytics na opção de _**Atrair > Remarketing**_ da **VTEX Assisted Sales (SuiteShare)**.
diff --git a/docs/faq/pt/how-to-find-google-tag-manager-pixel.md b/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
index 7efa61583..5397ee41e 100644
--- a/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
+++ b/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
@@ -16,7 +16,7 @@ legacySlug: como-encontrar-o-pixel-do-google-tag-manager
 
 Faça login no Gerenciador de [tags do Google](https://www.google.com/intl/pt-BR/tagmanager/).
 
-![Gerenciador de Tags Google](https://images.ctfassets.net/alneenqid6w5/6LoAdO0EywCYPEraFxwKb5/4e29b0762d74cc540d81c9fb6b64ef2a/Gerenciador_de_Tags_Google.png)
+![Gerenciador de Tags Google](//images.ctfassets.net/alneenqid6w5/6LoAdO0EywCYPEraFxwKb5/4e29b0762d74cc540d81c9fb6b64ef2a/Gerenciador_de_Tags_Google.png)
 
 Na opção **Contâiner ID**, você encontrará o código. Copie-o.
 
@@ -24,6 +24,6 @@ Na opção **Contâiner ID**, você encontrará o código. Copie-o.
   <p><b>Atenção</b>: Seu ID deve conter o prefixo do GTM.</p>
 </div>
 
-![Gerenciador de tags Goggle 2](https://images.ctfassets.net/alneenqid6w5/4UqVluoy3i3PraHgP3upQ3/5f45d8f38635a803a00b417667102433/Gerenciador_de_Tags_Google_2.png)
+![Gerenciador de tags Goggle 2](//images.ctfassets.net/alneenqid6w5/4UqVluoy3i3PraHgP3upQ3/5f45d8f38635a803a00b417667102433/Gerenciador_de_Tags_Google_2.png)
 
 Pronto! Agora você poderá adicionar o seu Pixel do Google Tag Manager na opção de _**Atrair > Remarketing**_ da **VTEX Assisted Sales (SuiteShare)**.
diff --git a/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md b/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md
index 03ce3f390..b8eccd3ea 100644
--- a/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md
+++ b/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md
@@ -19,11 +19,11 @@ legacySlug: nao-consigo-editar-um-campo-obrigatorio-do-master-data
 1. No menu do admin, selecione o módulo __Master Data__. 
 2. Certifique-se que está na aba __Aplicações__, dentro de __Links Rápidos__.
 3. Clique na engrenagem em __Profile System__.
-![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
+![MasterDataTutorial 1 UM](//images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
 4. Clique no __lápis__ ao lado do item que deseja configurar.
-![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
+![MasterDataTutorial2](//images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
 5. Clique em __Schemas de Layout__.
 6.  Na __Seção 1__, escolha o item do campo que deseja configurar.
 7. Em __Configurações avançadas do campo__, selecione__ Campo obrigatório no formulário__.
-![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
+![MasterDataTutorial3](//images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
 A opção também pode ser alterada sempre que desejado.
diff --git a/docs/faq/pt/i-dont-recognize-the-reservation-id-of-an-order.md b/docs/faq/pt/i-dont-recognize-the-reservation-id-of-an-order.md
index f19bb1442..11fd5cd9c 100644
--- a/docs/faq/pt/i-dont-recognize-the-reservation-id-of-an-order.md
+++ b/docs/faq/pt/i-dont-recognize-the-reservation-id-of-an-order.md
@@ -3,8 +3,8 @@ title: 'Não reconheço o ID de reserva de um pedido. O que pode ter acontecido?
 id: tja793G4XAWI2K8uIC4uW
 status: PUBLISHED
 createdAt: 2018-03-05T21:07:36.301Z
-updatedAt: 2023-03-22T20:28:58.311Z
-publishedAt: 2023-03-22T20:28:58.311Z
+updatedAt: 2024-02-05T18:01:17.750Z
+publishedAt: 2024-02-05T18:01:17.750Z
 firstPublishedAt: 2018-03-05T22:28:55.349Z
 contentType: frequentlyAskedQuestion
 productTeam: Channels
@@ -18,5 +18,4 @@ Isso pode estar acontecendo porque o pedido que você está visualizando ainda n
 
 Neste caso, você pode entrar em contato com seu marketplace ou esperar mais um pouco para verificar se as informações do pedido são atualizadas. Pois para não ter entrado na ferramenta de Integrações, o pedido pode ter sido cancelado ou até mesmo não ter sido criado.
 
-Se preferir, você pode verificar as informações referentes à reserva do seu pedido via [API](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/inventory/reservations).
-
+Se preferir, você pode verificar as informações referentes à reserva do seu pedido via Logistics API, usando o endpoint [List reservation by ID](https://developers.vtex.com/docs/api-reference/logistics-api?endpoint=get-/api/logistics/pvt/inventory/reservations/-reservationId-).
diff --git a/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 26596aa42..d8ff57db6 100644
--- a/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -31,6 +31,6 @@ _Para fazer a inclusão manual de SKUs específicos, siga o passo a passo abaixo
 5. Dê um nome à sua Coleção (os demais campos não devem ser preenchidos).
 6. Insira os SKUs no campo informado e __separe-os com vírgulas__.
 
-![recurrence-specific-skus](https://images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
+![recurrence-specific-skus](//images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
 
 Por fim, dê um nome ao __Grupo__ da sua Coleção e clique em __Save Group__.
diff --git a/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md b/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md
index 94390c9eb..edfcc7d8c 100644
--- a/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md
+++ b/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md
@@ -32,7 +32,7 @@ __Preencha o campo da Label__
 4. Vá para a aba __Imagens__
 5. Insira um termo para preencher a __Label__
 
-  ![Kit Look - Label - PT](https://images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/ba398076f25a3f1bc85df073e0e571c4/7FR879Lzl3eEDmAHiBV0TV_pt.png)
+  ![Kit Look - Label - PT](//images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/ba398076f25a3f1bc85df073e0e571c4/7FR879Lzl3eEDmAHiBV0TV_pt.png)
 
 6. Clique em __Salvar__
 
diff --git a/docs/faq/pt/locate-the-google-ads-pixel.md b/docs/faq/pt/locate-the-google-ads-pixel.md
index b6d3f4371..838767411 100644
--- a/docs/faq/pt/locate-the-google-ads-pixel.md
+++ b/docs/faq/pt/locate-the-google-ads-pixel.md
@@ -16,23 +16,23 @@ legacySlug: localize-o-pixel-do-google-ads
 
 Para localizar o ID do pixel de remarketing é necessário realizar o login dentro do Google ads.
 
-![Google_Ads](https://images.ctfassets.net/alneenqid6w5/3WHxCxHMQ7glNyc32wFa8G/3de7c855fa9574725c9df93eaf555ff9/Google_Ads.png)
+![Google_Ads](//images.ctfassets.net/alneenqid6w5/3WHxCxHMQ7glNyc32wFa8G/3de7c855fa9574725c9df93eaf555ff9/Google_Ads.png)
 
 O próximo passo, é acessar o menu **Ferramentas e Definições** e em **Biblioteca Partilhada**, acesse **Gestor de públicos-alvo**, conforme a imagem abaixo:
 
-![Google_Ads_Menu](https://images.ctfassets.net/alneenqid6w5/38QwaYvtbHLw3o52tKJjG1/417e13fdbf1bea474d9cb6e180808f9f/Google_Ads_Menu.png)
+![Google_Ads_Menu](//images.ctfassets.net/alneenqid6w5/38QwaYvtbHLw3o52tKJjG1/417e13fdbf1bea474d9cb6e180808f9f/Google_Ads_Menu.png)
 
 Agora, em gestor de público alvo, selecione a opção **Origens de públicos-alvo**.
 
-![Google_Ads_Menu_2](https://images.ctfassets.net/alneenqid6w5/29cE5O5pA3VrxJVmBrA52Y/9c5ae98d7886f80430928be4049dd7f8/Google_Ads_Menu_2.png)
+![Google_Ads_Menu_2](//images.ctfassets.net/alneenqid6w5/29cE5O5pA3VrxJVmBrA52Y/9c5ae98d7886f80430928be4049dd7f8/Google_Ads_Menu_2.png)
 
 Dentro do menu Origens de públicos-alvo, algumas opções estarão disponíveis (Analytics, Youtube, etc), selecione a tag do Google ADS. Acesse **Detalhes** ou em **Editar origem**. Agora, o próximo passo é selecionar o tipo de dados recolhidos por esta origem:
 
-![Google_Ads_Menu_3](https://images.ctfassets.net/alneenqid6w5/17FFDoGSDe74oPlheNvL1a/3a05b360a1375aed52e4e29a5f32ea45/Google_Ads_Menu_3.png)
+![Google_Ads_Menu_3](//images.ctfassets.net/alneenqid6w5/17FFDoGSDe74oPlheNvL1a/3a05b360a1375aed52e4e29a5f32ea45/Google_Ads_Menu_3.png)
 
 A seguir, selecione o tipo de tag:
 
-![Google_Ads_Menu_4](https://images.ctfassets.net/alneenqid6w5/5F1q4U7ZLrgvbJF0rBtEOu/5a41e7c9e34be8e340d7a633ebb983b0/Google_Ads_Menu_4.png)
+![Google_Ads_Menu_4](//images.ctfassets.net/alneenqid6w5/5F1q4U7ZLrgvbJF0rBtEOu/5a41e7c9e34be8e340d7a633ebb983b0/Google_Ads_Menu_4.png)
 
 Uma vez que o tipo de tag seja selecionada, aparecerão as instruções, bem como o código da tag que você deverá copiar.
 
diff --git a/docs/faq/pt/my-admin-is-blocked-what-do-i-do.md b/docs/faq/pt/my-admin-is-blocked-what-do-i-do.md
index 9fc2e8120..7d568b91e 100644
--- a/docs/faq/pt/my-admin-is-blocked-what-do-i-do.md
+++ b/docs/faq/pt/my-admin-is-blocked-what-do-i-do.md
@@ -3,8 +3,8 @@ title: 'Meu Admin está bloqueado. O que fazer?'
 id: 4IkFRmDVx6quIIcwoOGY6K
 status: PUBLISHED
 createdAt: 2017-10-11T13:36:13.665Z
-updatedAt: 2021-03-22T20:31:43.767Z
-publishedAt: 2021-03-22T20:31:43.767Z
+updatedAt: 2023-07-24T15:11:04.222Z
+publishedAt: 2023-07-24T15:11:04.222Z
 firstPublishedAt: 2017-10-11T13:39:18.676Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -22,12 +22,10 @@ Enquanto aguarda o contato do Financeiro, é possível desbloquear temporariamen
 
 Siga os passos abaixo para desbloquear seu Admin por esse período. Você deve possuir as permissões de Admin Super ou [Perfil de Acesso Financeiro](https://help.vtex.com/pt/tutorial/como-criar-um-perfil-de-acesso-financeiro--717qPtxW3Cy9n5KrReHeVv?locale=pt) para realizar as ações a seguir:
 
-- Acesse o módulo Faturas.
-- Clique no botão **Veja como desbloquear temporariamente**.
-- Insira o número do ticket que você abriu anteriormente para desbloqueio.
-- Clique no botão **Desbloquear por 48 horas**.
+1. Acesse o módulo Faturas.
+2. Clique no botão **Veja como desbloquear temporariamente**.
+3. Insira o número do ticket que você abriu anteriormente para desbloqueio.
+4. Clique no botão **Desbloquear por 48 horas**.
 
 Feito esse procedimento, seu perfil ficará desbloqueado por 48 horas de dias úteis. Aproveite para colocar suas faturas em dia até o contato do time Financeiro.
 
-![Início](https://images.ctfassets.net/alneenqid6w5/6bYCHufFuKJ2TKivBJl8Pr/bc552ab6bbfad7ef49c1a9a59e2d5724/In__cio.gif)
-
diff --git a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
new file mode 100644
index 000000000..24b1f392e
--- /dev/null
+++ b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -0,0 +1,30 @@
+---
+title: 'Pedido está travado em "Pronto para manuseio", o que fazer?'
+id: frequentlyAskedQuestions_771
+status: PUBLISHED
+createdAt: 2017-04-27T22:27:37.057Z
+updatedAt: 2023-06-15T13:20:25.568Z
+publishedAt: 2023-06-15T13:20:25.568Z
+firstPublishedAt: 2017-04-27T23:02:34.947Z
+contentType: frequentlyAskedQuestion
+productTeam: Post-purchase
+author: authors_84
+slug: pedido-esta-travado-em-pronto-para-manuseio-o-que-fazer
+locale: pt
+legacySlug: meus-pedidos-estao-travados-em-pronto-para-manuseio
+---
+
+Quando uma loja tem algum pedido travado no status **Pronto para manuseio**, isto significa que é necessário que o ERP informe que consultou o pedido e iniciou seu manuseio.
+
+Isso acontece porque, dentro do fluxo de pedidos, o status **Pronto para manuseio** é o status em que os pedidos devem ser consultados pelo ERP.
+
+Quando o ERP consulta e insere este pedido em sua base, é preciso que ele informe à VTEX que o pedido pode seguir com seu fluxo. Esse aviso pode ser feito de duas maneiras:
+
+- [ERP informa por API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling): modo mais comum de atualização.
+- **Lojista informa manualmente**: a loja não possui um ERP e o lojista informa que o pedido deve seguir o fluxo pelo Admin VTEX, na [página de detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). Para saber o passo a passo completo, confira o artigo [Passar pedido para o status Preparando Entrega](https://help.vtex.com/pt/tutorial/passar-pedido-para-o-status-preparando-entrega--tutorials_198).
+
+> É necessário ter um [perfil de acesso com permissão OMS - Full access](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para realizar esta ação.
+
+<div class="alert alert-warning">
+<p>Se o pedido passar do status <b>Iniciar manuseio</b> manualmente, não será possível enviar o pedido para o ERP posteriormente.</p>
+</div>
diff --git a/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md b/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md
index 00298f2f5..68f672231 100644
--- a/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md
+++ b/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md
@@ -18,6 +18,6 @@ Ao entrar em **Afiliações de Gateways**, é possível ver a listagem de todas
 
 Isso significa que esta afiliação não está ativa, e sim, está em teste. É possível confirmar essa informação entrando na afiliação destacada. 
 
-![afiliação-gateway-teste pt](https://images.ctfassets.net/alneenqid6w5/5fCrLnTamsyKIwY4WaEI4e/1d5e0ef719b52b6b46257032a3d5d521/gateway_teste_pt.png)
+![afiliação-gateway-teste pt](//images.ctfassets.net/alneenqid6w5/5fCrLnTamsyKIwY4WaEI4e/1d5e0ef719b52b6b46257032a3d5d521/gateway_teste_pt.png)
 
 Ou seja, a cor destaca aquelas configurações que ainda não estão ativas.
diff --git a/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md b/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
index b224062f6..d9353ad82 100644
--- a/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
+++ b/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
@@ -22,10 +22,10 @@ Isto acontece quando há algum erro no cadastro do SKU no seller.
 
 Para identificar qual é o erro, siga os passos abaixo:
 1. Entre no módulo __Sugestões__.  
-2. Clique no SKU que o marketplace não aceitou.!![suggestions1](https://images.ctfassets.net/alneenqid6w5/4cgijfXaTmcy00Q8G8eISS/fb35d1ecb947bd68b76674902ea30ac8/suggestions1.png)  
+2. Clique no SKU que o marketplace não aceitou.!![suggestions1](//images.ctfassets.net/alneenqid6w5/4cgijfXaTmcy00Q8G8eISS/fb35d1ecb947bd68b76674902ea30ac8/suggestions1.png)  
 3. Entre no __developer tools__ do browser (para isso, se estiver usando o Google Chrome, aperte `F12` no Windows ou `Command+Option+I` no Mac).   
 4. No developer tools, clique na aba __Network__.  
-5. Ainda no developer tools, clique na opção __All__.!![f12pt](https://images.ctfassets.net/alneenqid6w5/29nyZivZywIyM8m4aE6Omu/f595c009eb3e8f7559bee5ebc3444c16/f12pt.png)  
+5. Ainda no developer tools, clique na opção __All__.!![f12pt](//images.ctfassets.net/alneenqid6w5/29nyZivZywIyM8m4aE6Omu/f595c009eb3e8f7559bee5ebc3444c16/f12pt.png)  
 6. Clique no botão __Aceitar__ do módulo Sugestões.  
 7. Você verá uma lista das chamadas ativadas pelo botão Aceitar.  
 8. Se uma delas estiver em vermelho e com status `400`, como na imagem abaixo, clique nessa chamada.![erroSuggestion3](//images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)  
diff --git a/docs/faq/pt/understanding-vtex-email-capture-system.md b/docs/faq/pt/understanding-vtex-email-capture-system.md
index b70f6d7d9..f9382fa90 100644
--- a/docs/faq/pt/understanding-vtex-email-capture-system.md
+++ b/docs/faq/pt/understanding-vtex-email-capture-system.md
@@ -50,4 +50,4 @@ Para que a função do <a href="https://help.vtex.com/pt/tutorial/acesse-o-carri
 Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
 </div>
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
diff --git a/docs/faq/pt/utms.md b/docs/faq/pt/utms.md
index 82e4212bd..8a41152fa 100644
--- a/docs/faq/pt/utms.md
+++ b/docs/faq/pt/utms.md
@@ -24,12 +24,12 @@ Para que as **UTMS** configuradas funcionem corretamente, é necessário que **
 2 - utm\_medium.  
 3 - utm\_campaign.
 
-![UTMs1](https://images.ctfassets.net/alneenqid6w5/3rxDnnXLJN8HFAeoDaD7Dz/5ef0ebc8475ef92c049fd998ff0e6f96/UTMs1.png)
+![UTMs1](//images.ctfassets.net/alneenqid6w5/3rxDnnXLJN8HFAeoDaD7Dz/5ef0ebc8475ef92c049fd998ff0e6f96/UTMs1.png)
 
 Abaixo um exemplo de como o link deve ficar e como aparecerá no **RD Station**: 
 
 **[https://whts.co/marcelows](\"https://whts.co/marcelows\")**utm\_source=**facebook**&utm\_medium=cpc&utm\_campaign=nomecampanhaexemplo&utm\_term=palavrachaveYou
 
-![UTMs2](https://images.ctfassets.net/alneenqid6w5/49FZ9GtBTiNiXhNYMla6Hd/b14036e3cbe534ea449dd9b9e7011752/UTMs2.png)
+![UTMs2](//images.ctfassets.net/alneenqid6w5/49FZ9GtBTiNiXhNYMla6Hd/b14036e3cbe534ea449dd9b9e7011752/UTMs2.png)
 
 Após estar com o link configurado, as origens de leads convertidos nesse link respeitarão as configurações inseridas por você.
diff --git a/docs/faq/pt/vtex-support-brazil.md b/docs/faq/pt/vtex-support-brazil.md
index 63371f977..bee1adc1d 100644
--- a/docs/faq/pt/vtex-support-brazil.md
+++ b/docs/faq/pt/vtex-support-brazil.md
@@ -3,8 +3,8 @@ title: 'Suporte VTEX - Brasil'
 id: 5q861sTw1n7H2BENOu7ls9
 status: PUBLISHED
 createdAt: 2021-03-02T00:59:46.352Z
-updatedAt: 2022-12-23T15:47:00.476Z
-publishedAt: 2022-12-23T15:47:00.476Z
+updatedAt: 2024-05-23T16:25:31.311Z
+publishedAt: 2024-05-23T16:25:31.311Z
 firstPublishedAt: 2021-03-02T01:09:50.358Z
 contentType: frequentlyAskedQuestion
 productTeam: Others
@@ -16,6 +16,8 @@ legacySlug: suporte-vtex-brasil
 
 Este artigo apresenta a disponibilidade, SLA e recursos de suporte adicionais disponíveis para clientes atendidos por nossos escritórios no **Brasil**. Para uma perspectiva mais ampla de nossos recursos de suporte global, consulte: [Como funciona o suporte VTEX?](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe)
 
+<div class="alert alert-info">Se a equipe de Suporte identificar que um chamado foi aberto incorretamente, será recomendado o recurso mais apropriado a ser utilizado, e essa avaliação poderá ser feita em qualquer momento durante o processo de resolução.</div>
+
 ## Disponibilidade e SLA de atendimento
 
 As respostas aos [chamados abertos para o suporte VTEX](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) ocorrerão dentro do horário comercial, de 09:00 até 18:00 BRT, com exceção de feriados e fins de semana. 
diff --git a/docs/faq/pt/vtex-support-emea.md b/docs/faq/pt/vtex-support-emea.md
new file mode 100644
index 000000000..3f0988fdb
--- /dev/null
+++ b/docs/faq/pt/vtex-support-emea.md
@@ -0,0 +1,17 @@
+---
+title: 'Suporte VTEX - EMEA'
+id: 5ePu2qkCfmE0IEKDFKg53F
+status: PUBLISHED
+createdAt: 2023-11-09T16:29:55.255Z
+updatedAt: 2024-05-28T02:20:01.805Z
+publishedAt: 2024-05-28T02:20:01.805Z
+firstPublishedAt: 2023-11-09T16:51:03.796Z
+contentType: frequentlyAskedQuestion
+productTeam: Billing
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: suporte-vtex-emea
+locale: pt
+legacySlug: suporte-vtex-emea
+---
+
+Este conteúdo está disponível apenas em inglês. [Clique aqui](https://help.vtex.com/pt/faq/vtex-support-brazil--5q861sTw1n7H2BENOu7ls9?&utm_source=autocomplete) para acessar.
diff --git a/docs/faq/pt/website-with-error-how-to-fix-it.md b/docs/faq/pt/website-with-error-how-to-fix-it.md
index 8a109a0e6..e53fb1764 100644
--- a/docs/faq/pt/website-with-error-how-to-fix-it.md
+++ b/docs/faq/pt/website-with-error-how-to-fix-it.md
@@ -23,7 +23,7 @@ No entanto, se estiver amarelo, há um erro.
 Veja abaixo o passo a passo para corrigi-lo:
 
 1. Clique no website desejado.
-2. Selecione o Binding (linha selecionada na imagem abaixo), e clique em __Update__.![Binding 1](https://images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
+2. Selecione o Binding (linha selecionada na imagem abaixo), e clique em __Update__.![Binding 1](//images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
 3. Na tela que aparecerá em seguida, o campo __Store name from License Manager__ estará em branco. Clique na seta que aparece nesse campo e selecione o nome da sua loja.
-4. Clique em **Save Binding**.![Binding 2](https://images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
+4. Clique em **Save Binding**.![Binding 2](//images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
 5. Clique em **Websites** novamente para atualizar a página. Pronto! O globo estará azul, o que indica que agora está tudo certo com a associação ao Binding.
diff --git a/docs/faq/pt/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md b/docs/faq/pt/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
index 1baf045c6..faec0ffad 100644
--- a/docs/faq/pt/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
+++ b/docs/faq/pt/what-to-do-when-an-unexpected-error-message-appears-while-selecting-paypal-plus-at-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'O que fazer quando uma mensagem de erro inesperado aparece ao selecionar PayPal Plus no checkout'
 id: 2eyMuEf6wsWuOgrjo7tzQH
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-03-18T14:01:50.694Z
-updatedAt: 2019-12-31T14:24:40.864Z
-publishedAt: 2019-12-31T14:24:40.864Z
+updatedAt: 2024-02-19T17:41:00.925Z
+publishedAt: 
 firstPublishedAt: 2019-03-18T14:10:08.064Z
 contentType: frequentlyAskedQuestion
 productTeam: Shopping
diff --git a/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md b/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md
index b1fee4695..7f90b493e 100644
--- a/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md
+++ b/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md
@@ -24,9 +24,9 @@ A seguir, entenda o passo a passo:
 
 1. Acesse o __Master Data__
 2. Clique em __“Exportations”__
-![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
+![3WNNUZ8EgDZ4iYv8e0OyQG](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
 3. Certifique-se que aba aberta é a de __“Aplicações”__
-![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
+![7ecXBGaCeC3hTaO0lODPq1](//images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
 4. Em __“Status de exportações”__, clique no relatório que deseja baixar.
 
 Dessa forma, é possível acessar esse material mesmo que o email original não tenha chegado para o solicitante.
diff --git a/docs/faq/pt/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md b/docs/faq/pt/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
index 06c71dc40..868985f26 100644
--- a/docs/faq/pt/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
+++ b/docs/faq/pt/what-to-do-when-receiving-an-error-message-during-shipping-simulation.md
@@ -3,8 +3,8 @@ title: 'O que fazer ao receber erro na simulação de frete'
 id: 3bkJwe0Yj6qEkuYKUWwKwK
 status: PUBLISHED
 createdAt: 2017-05-09T14:03:03.097Z
-updatedAt: 2021-03-22T20:46:27.291Z
-publishedAt: 2021-03-22T20:46:27.291Z
+updatedAt: 2023-10-10T16:20:54.988Z
+publishedAt: 2023-10-10T16:20:54.988Z
 firstPublishedAt: 2017-05-09T14:06:10.341Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -18,7 +18,7 @@ Como proceder ao fazer uma simulação de frete e não encontrar o resultado esp
 
 Vamos desenhar aqui o passo-a-passo para conferir a configuração de Logística.
 
-Antes de começar vale a pena lembrar que a [Simulação de Frete](/pt/tutorial/simulacao-de-frete/) retorna o resultado da API de [Cálculo de Frete](https://developers.vtex.com/reference/logistics-api-overview). Recomendamos sempre o uso das API´s. Caso não tenha acesso, consulte o administrador da sua loja e confira qual perfil de acesso está associado ao seu usuário.
+Antes de começar vale a pena lembrar que a [Simulação de Frete](/pt/tutorial/simulacao-de-frete/) retorna o resultado da API de [Cálculo de SLA](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping/calculate). Recomendamos sempre o uso das API´s. Caso não tenha acesso, consulte o administrador da sua loja e confira qual perfil de acesso está associado ao seu usuário.
 
 Para ilustrar esse artigo vamos criar um cenário em que o produto __X-Box__ não está sendo entregue no Cep 22451-451 para a política comercial 1. A mensagem de erro é esta: "_Não foi possível gerar o carrinho. Veja os detalhes abaixo_".
 
@@ -26,7 +26,7 @@ Há alguns fatores que podem influenciar uma simulação, então recomendamos se
 
 Feito isso, temos que conferir a Logística como um todo, ou seja, conferir qual estoque do X-box e qual transportadora que estão associada Política Comercial 1. Essa útima informação está contida na Doca.
 
-Via API seria bem simples também. Fazendo a chamada [Cálculo de Frete](https://developers.vtex.com/reference/logistics-api-overview) é facil identificar o ID da transportadora e assim fazer o caminho inverso.
+Via API seria bem simples também. Fazendo a chamada [Cálculo de SLA](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping/calculate) é facil identificar o ID da transportadora e assim fazer o caminho inverso.
 
 Mas o que fazer para corrigir isso?
 
diff --git a/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
index 622936471..1029df20a 100644
--- a/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -16,7 +16,7 @@ legacySlug:
 
 Existe um caso em que, mesmo com o Avise-me [corretamente configurado](/pt/tutorial/configurar-o-avise-me), ele não aparece. É **quando o tipo de exibição da categoria está selecionado como Lista de SKUs**.
 
-![categoria-lista-de-skus PT](https://images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
+![categoria-lista-de-skus PT](//images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
 
 Neste caso, além das configurações padrão, é necessário o uso do controle `vtex.cmc:SkuSelection`, mesmo que não exista mais de um SKU por página.
 
diff --git a/docs/faq/pt/why-are-my-orders-not-integrating-with-mercado-livre.md b/docs/faq/pt/why-are-my-orders-not-integrating-with-mercado-livre.md
index 5a9052a07..a7e456eb9 100644
--- a/docs/faq/pt/why-are-my-orders-not-integrating-with-mercado-livre.md
+++ b/docs/faq/pt/why-are-my-orders-not-integrating-with-mercado-livre.md
@@ -21,7 +21,7 @@ Dito isso, o primeiro passo é acessar o cadastro dessa integração:
 1. Acesse o módulo __Marketplace__
 2. Clique em __Integrações__
 3. Procure o __painel__ do Mercado Livre
-4. Clique na __engrenagem__ <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
+4. Clique na __engrenagem__ <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
 5. Clique em __Editar configuração__
 
 A partir daí, é preciso refazer o processo de integração.
diff --git a/docs/faq/pt/why-are-my-store-images-being-displayed-in-poor-quality.md b/docs/faq/pt/why-are-my-store-images-being-displayed-in-poor-quality.md
new file mode 100644
index 000000000..d35eaecec
--- /dev/null
+++ b/docs/faq/pt/why-are-my-store-images-being-displayed-in-poor-quality.md
@@ -0,0 +1,27 @@
+---
+title: 'Por que as imagens da minha loja estão sendo exibidas com baixa qualidade?'
+id: 5LxgbF8S2cIUOCaCO00GcK
+status: PUBLISHED
+createdAt: 2018-02-22T19:10:35.567Z
+updatedAt: 2024-04-15T15:07:36.249Z
+publishedAt: 2024-04-15T15:07:36.249Z
+firstPublishedAt: 2018-02-22T22:03:18.347Z
+contentType: frequentlyAskedQuestion
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: por-que-as-imagens-da-minha-loja-estao-sendo-exibidas-com-baixa-qualidade
+locale: pt
+legacySlug: por-que-as-imagens-da-minha-loja-estao-sendo-exibidas-com-baixa-qualidade
+---
+
+A redução na qualidade das imagens pode acontecer durante o processo automático de [compactação ou compressão de imagens](https://help.vtex.com/pt/tutorial/compactacao-de-imagens--4klbgpsPksq44KcwqKeye8).
+
+Se você utiliza fotos no formato JPG ou JPEG no seu website, é normal que elas passem por alguma perda de qualidade, devido à conversão para [WebP](https://developers.google.com/speed/webp?hl=pt-br) com perdas (lossy). No entanto, essa diferença não deveria ser muito sensível. Para corrigir isso, o melhor é fazer upload novamente dos arquivos, mas com uma resolução um pouco maior.
+
+Para sua loja exibir imagens com cores sólidas, gráficos detalhados e alto contraste, recomendamos que você use o formato PNG, que conta com otimização no mesmo formato ou conversão para WebP sem perdas (lossless), com mais probabilidade de manter a qualidade do arquivo original.
+
+Outra opção é utilizar imagens pré-otimizadas com ferramentas de conversão para JPEG progressivo para fotos ou PNG 8-bit para ilustrações. Dessa forma, é possível compactar o arquivo previamente e existe uma chance do formato ser distribuído sem passar por recompressão.
+
+## Saiba mais
+
+* [Compactação de imagens](https://help.vtex.com/pt/tutorial/compactacao-de-imagens--4klbgpsPksq44KcwqKeye8)
diff --git a/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md b/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md
index 61e7c7c5f..a307649b8 100644
--- a/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md
+++ b/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md
@@ -28,14 +28,14 @@ Uma vez localizado o campo, prossiga com as instruções a seguir:
 
 1. Acesse o módulo __Catálogo__
 2. Do lado esquerdo da tela, clique em __Categorias__
-![campos1](https://images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
+![campos1](//images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
 3. Vá até o lado direito da página e clique no botão azul __Ações__
 4. Selecione a opção __Campos (Produto)__
-![campos2](https://images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
+![campos2](//images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
 5. Encontre o __grupo__ em que deseja fazer as modificações
 6. Clique em __Alterar__
-![campos3](https://images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
+![campos3](//images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
 7. Após fazer as mudanças necessárias, clique em __Salvar__
-![PTgrupo4](https://images.ctfassets.net/alneenqid6w5/TwYOgTmuhvs1buHQoWEf4/4b75359b1604b842446960bb64d8f6da/PTgrupo4.png)![ENgrupo4](https://images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
+![PTgrupo4](//images.ctfassets.net/alneenqid6w5/TwYOgTmuhvs1buHQoWEf4/4b75359b1604b842446960bb64d8f6da/PTgrupo4.png)![ENgrupo4](//images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
 
 Pronto, campos alterados! Não se esqueça de salvar as configurações para que as alterações sejam exibidas no front da loja.
diff --git a/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md b/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md
index 404fef429..f0f17662b 100644
--- a/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md
+++ b/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md
@@ -3,8 +3,8 @@ title: 'Por que minha transportadora não aparece no checkout?'
 id: frequentlyAskedQuestions_165
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:09.470Z
-updatedAt: 2023-03-20T20:32:20.572Z
-publishedAt: 2023-03-20T20:32:20.572Z
+updatedAt: 2023-08-25T15:13:42.026Z
+publishedAt: 2023-08-25T15:13:42.026Z
 firstPublishedAt: 2017-04-27T23:01:43.444Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -26,6 +26,10 @@ No momento de cadastro de uma transportadora, é preciso incluir o [método de e
 
 O checkout exibe sempre a transportadora mais rápida/barata entre as opções de um mesmo métodos de envio. Assim, uma transportadora não aparece no checkout quando outra do mesmo tipo tem menor prazo/custo cadastrado.
 
+<div class="alert alert-warning">
+O critério de desempate na concorrência entre transportadoras é a priorização do menor custo de envio.
+</div>
+
 ### Solução
 
 Caso você deseje que todas as transportadoras sejam exibidas, você deve cadastrá-las no módulo **Configurações da loja > Envio > Configurações** como transportadoras com métodos de envio diferentes.
diff --git a/docs/faq/pt/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md b/docs/faq/pt/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
index 04eedc817..c30774ffc 100644
--- a/docs/faq/pt/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
+++ b/docs/faq/pt/why-did-the-carrier-calculate-freight-for-a-weight-lower-than-the-minimum-set.md
@@ -3,8 +3,8 @@ title: 'Por que a transportadora calculou frete para um peso menor do que o mín
 id: frequentlyAskedQuestions_164
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:17.904Z
-updatedAt: 2019-12-31T14:25:25.374Z
-publishedAt: 2019-12-31T14:25:25.374Z
+updatedAt: 2023-12-19T16:53:24.136Z
+publishedAt: 2023-12-19T16:53:24.136Z
 firstPublishedAt: 2017-04-27T23:01:43.295Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -14,7 +14,7 @@ locale: pt
 legacySlug: por-que-minha-transportadora-calculou-frete-para-um-peso-menor-do-que-o-minimo-configurado
 ---
 
-O cálculo do frete sempre considera dois parâmetros, o peso e o volume do produto. A prioridade de cálculo é sempre para o peso real ou cubado &#8211; o maior entre eles. Porém, caso peso do produto seja menor do que o mínimo cadastrado para a transportadora, será considerado o volume.
+O cálculo do frete sempre considera dois parâmetros, o peso e o volume do produto. A prioridade de cálculo é sempre para o peso mínimo ou cubado &#8211; o maior entre eles. Porém, caso peso do produto seja menor do que o mínimo cadastrado para a transportadora, será considerado o volume.
 
 ## Exemplos
 
diff --git a/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md b/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md
index 037120b7a..f0a3bc716 100644
--- a/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md
+++ b/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md
@@ -34,7 +34,7 @@ Certifique-se o valor foi inserido seguindo os seguintes passos:
 4. Vá para a sessão __“Quais as condições para a promoção ser válida?”__
 5. Confira quais Clusters estão cadastradas em __“Cluster de clientes”__
 
-![PT - 7GcSb6BuF6JKnmGAggO3uA ](https://images.ctfassets.net/alneenqid6w5/wltgxrSqvTKY5QmcZpK6A/6588a08d631b0bee3b52aa885ca34dda/Cluster-promo-PT.png)
+![PT - 7GcSb6BuF6JKnmGAggO3uA ](//images.ctfassets.net/alneenqid6w5/wltgxrSqvTKY5QmcZpK6A/6588a08d631b0bee3b52aa885ca34dda/Cluster-promo-PT.png)
 
 6. Insira os __novos dados__
 7. Clique em __Salvar__
diff --git a/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md b/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
index 564b29b4a..e2be433c0 100644
--- a/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
+++ b/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
@@ -22,7 +22,7 @@ Para especificar em que tipo de entrega você deseja aplicar a promoção, é pr
 2. Clique no card da promoção à qual você deseja aplicar o frete grátis.
 3. No item 3, ative a flag __Tipo de frete__ e especifique quais devem receber o frete grátis.
 
-![promoções-campo-tipo-frete pt](https://images.ctfassets.net/alneenqid6w5/5FX7WnVH3OOaoUGmUAumMO/a3f7f8fec3b78167565da7717e04b137/promo____es-campo-tipo-frete_pt.png)
+![promoções-campo-tipo-frete pt](//images.ctfassets.net/alneenqid6w5/5FX7WnVH3OOaoUGmUAumMO/a3f7f8fec3b78167565da7717e04b137/promo____es-campo-tipo-frete_pt.png)
 
 Feito isso, os tipos de frete epecificados entrarão na promoção e aparecerão para o cliente com o frete grátis disponível.
 
diff --git a/docs/faq/pt/why-is-let-me-know-not-showing.md b/docs/faq/pt/why-is-let-me-know-not-showing.md
index 94941a6fe..922260209 100644
--- a/docs/faq/pt/why-is-let-me-know-not-showing.md
+++ b/docs/faq/pt/why-is-let-me-know-not-showing.md
@@ -21,7 +21,7 @@ As configurações básicas para a exibição do **Avise-me** quando o produto e
 
 Porém, existe um caso em que, mesmo com os itens acima configurados, o Avise-me não aparece, que é **quando o tipo de exibição da Categoria está selecionado como Lista de SKUs**.
 
-![categoria-lista-de-skus PT](https://images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
+![categoria-lista-de-skus PT](//images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
 
 Neste caso, além das configurações padrão, é necessário o uso do controle `vtex.cmc:SkuSelection`, mesmo que não exista mais de um SKU por página.
 Logo, quando a Categoria do produto desejado estiver setada para Lista de SKUs, como na imagem acima, é necessário que seja inserido o controle `vtex.cmc:SkuSelection` no template de página para que o avise-me seja exibido.
diff --git a/docs/faq/pt/why-is-my-freight-value-wrong.md b/docs/faq/pt/why-is-my-freight-value-wrong.md
index 60c15e7ea..0a79d7509 100644
--- a/docs/faq/pt/why-is-my-freight-value-wrong.md
+++ b/docs/faq/pt/why-is-my-freight-value-wrong.md
@@ -23,7 +23,7 @@ O valor de frete é calculado com base em vários fatores: tabela de frete, adic
 3. Aqui, você verificará o valor cadastrado na planilha mais todos os [adicionais](/pt/tutorial/como-funciona-o-adicional-de-frete/) somados a esse valor.
 4. Caso o valor ainda não esteja condizente com o exibido na loja, siga os passos abaixo para verificar se não há nenhuma promoção alterando o valor do frete.
 
-![por-que-meu-valor-de-frete-esta-errado pt](https://images.ctfassets.net/alneenqid6w5/4voY55RWlOO8m0wOmciwkk/2663f2b117d2ce1cfffcbc513602937b/por-que-meu-valor-de-frete-esta-errado_pt.jpg)
+![por-que-meu-valor-de-frete-esta-errado pt](//images.ctfassets.net/alneenqid6w5/4voY55RWlOO8m0wOmciwkk/2663f2b117d2ce1cfffcbc513602937b/por-que-meu-valor-de-frete-esta-errado_pt.jpg)
 
 ### Promoção
 
@@ -32,4 +32,4 @@ O valor de frete é calculado com base em vários fatores: tabela de frete, adic
 3. Observe a box **Valor Total**.
 4. Verifique se, entre as promoções, existe alguma com desconto em frete. Para verificar, basta você acessar a promoção do pedido e verificar o tipo de desconto.
 
-![valortotal pt](https://images.ctfassets.net/alneenqid6w5/HTsaBSleouCOQKO0g0AEO/eac925ecef4c78b1fc41c22c8127dce1/valortotal_pt.jpg)
+![valortotal pt](//images.ctfassets.net/alneenqid6w5/HTsaBSleouCOQKO0g0AEO/eac925ecef4c78b1fc41c22c8127dce1/valortotal_pt.jpg)
diff --git a/docs/faq/pt/why-is-my-stock-negative.md b/docs/faq/pt/why-is-my-stock-negative.md
index a2d656001..4ead41073 100644
--- a/docs/faq/pt/why-is-my-stock-negative.md
+++ b/docs/faq/pt/why-is-my-stock-negative.md
@@ -3,8 +3,8 @@ title: 'Por que meu estoque está negativo?'
 id: frequentlyAskedQuestions_159
 status: PUBLISHED
 createdAt: 2017-04-27T22:39:51.880Z
-updatedAt: 2023-03-22T20:34:48.834Z
-publishedAt: 2023-03-22T20:34:48.834Z
+updatedAt: 2024-04-18T14:18:13.634Z
+publishedAt: 2024-04-18T14:18:13.634Z
 firstPublishedAt: 2017-04-27T23:01:42.612Z
 contentType: frequentlyAskedQuestion
 productTeam: Post-purchase
@@ -30,7 +30,7 @@ O fluxo correto prevê que a baixa no estoque só ocorra após o status __Prepar
 
 Para ajustar este cenário, o estoque do item deve ser atualizado com a quantidade de itens físicos no estoque. Dessa maneira, o valor dos itens em estoque deve ser a soma dos itens disponíveis mais os itens que estão reservados e que ainda não estão no status de __Preparando Entrega__. A correção pode ser feita seguindo os passos abaixo:
 
-1. No Admin VTEX, acesse __Catálogo > Estoque__, ou digite **Estoque** na barra de busca no topo da página.
+1. No Admin VTEX, acesse __Catálogo > Inventário__, ou digite **Inventário** na barra de busca no topo da página.
 2. Clique em __Gerenciamento de inventário__.
 3. Busque pelo SKU desejado e clique no resultado da busca.
 4. Na coluna __Atualizar contagem__, preencha com o valor indicado na descrição acima.
diff --git a/docs/faq/pt/why-is-my-stores-zoom-not-working.md b/docs/faq/pt/why-is-my-stores-zoom-not-working.md
index 0cb260c38..43b42c859 100644
--- a/docs/faq/pt/why-is-my-stores-zoom-not-working.md
+++ b/docs/faq/pt/why-is-my-stores-zoom-not-working.md
@@ -25,7 +25,7 @@ Para configurar este tamanho de imagem, siga estes passos:
 2. Clique em __Configurações__.
 3. Acesse a aba __Tipos de Arquivo__.
 
-![Tipos de Arquivo PT](https://images.ctfassets.net/alneenqid6w5/6Bc1z4n3tSqwYIa40YwKC2/ae8cac2252ac614d548bf2fbb1831401/Tipos_de_Arquivo_PT.png)
+![Tipos de Arquivo PT](//images.ctfassets.net/alneenqid6w5/6Bc1z4n3tSqwYIa40YwKC2/ae8cac2252ac614d548bf2fbb1831401/Tipos_de_Arquivo_PT.png)
 
 O tamanho 1000x1000 significa que o zoom resultante mostrará a imagem nesse tamanho. Logo, este é o tamanho mínimo para o zoom funcionar.
 
diff --git a/docs/faq/pt/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md b/docs/faq/pt/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
index a5d740ca1..8163bd4fd 100644
--- a/docs/faq/pt/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
+++ b/docs/faq/pt/why-is-the-origin-of-the-orders-different-on-vtex-and-on-google-analytics.md
@@ -1,10 +1,10 @@
 ---
 title: 'Por que a origem dos pedidos está diferente na VTEX e no Google Analytics?'
 id: frequentlyAskedQuestions_5030
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T22:22:57.838Z
-updatedAt: 2019-12-31T14:24:58.529Z
-publishedAt: 2019-12-31T14:24:58.529Z
+updatedAt: 2023-06-21T22:44:36.086Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:02:44.531Z
 contentType: frequentlyAskedQuestion
 productTeam: Identity
diff --git a/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md b/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
index 181be245c..09a323bda 100644
--- a/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
@@ -42,7 +42,7 @@ Recomendamos iniciar a investigação pelo **Catálogo**. Para verificar as conf
 1. Acesse o Admin VTEX e navegue até **Produtos > Catálogo > Produtos e SKUs** para verificar os produtos cadastrados na sua loja.
 2. Encontre na listagem o produto que você pretende exibir, conforme ilustrado a seguir.
 
-    ![01-produto-pt](https://images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/89bf951c58bd80765de8bfb480fd73df/01-produto-pt.png)
+    ![01-produto-pt](//images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/89bf951c58bd80765de8bfb480fd73df/01-produto-pt.png)
 
 3. Siga as instruções descritas nas próximas seções para verificar as seguintes informações:
    - [Produto](#produto)
@@ -71,9 +71,9 @@ Para verificar as configurações do produto, é importante seguir os passos aba
    * Caso o produto contenha especificações, navegue até a aba **Especificações** e verifique se elas estão preenchidas.
 3. Após qualquer alteração, clique em `Salvar`.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/nGAGYNdVtTFdAPjW1mi5f/0651c6f05455a3318423364b9129b8b4/02-campos-produto-pt.png" alt="02-campos-produto-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Campos que devem ser verificados na página de informações do produto</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/nGAGYNdVtTFdAPjW1mi5f/0651c6f05455a3318423364b9129b8b4/02-campos-produto-pt.png" alt="02-campos-produto-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Campos que devem ser verificados na página de informações do produto</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/6UXDapFf9bvtnCSoHQBwZC/d8a3043e74dfea536e1f47c02a634359/03-aba-especificacoes-pt.png" alt="03-aba-especificacoes-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Aba <strong>Especificações</strong></em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/6UXDapFf9bvtnCSoHQBwZC/d8a3043e74dfea536e1f47c02a634359/03-aba-especificacoes-pt.png" alt="03-aba-especificacoes-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Aba <strong>Especificações</strong></em></figcaption></figure>
 
 ### SKUs
 
@@ -85,16 +85,16 @@ Na página de SKUs, em **Produtos > Catálogo > Produtos e SKUs**, siga as instr
 
     |Botão | Descrição |
     |-|-|
-    | ![04-botao-precos](https://images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acessar a **Lista de preços** para verificar se existe um preço válido para a política comercial desejada associado aos SKUs do produto. Confira a seção de [Preços](#precos) para mais informações.|
-    | ![05-botao-logistica](https://images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acessar a página **Gerenciar inventário** para verificar se o SKU está disponível em estoque. Confira a seção de [Logística](#logistica) para mais informações. |
-    | ![06-botao-indexed-info](https://images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite visualizar cada **Seller **que comercializa o SKU, a política comercial (**Policy**), o preço (**Value**) e a quantidade do SKU em estoque (**Quantity**). |
+    | ![04-botao-precos](//images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acessar a **Lista de preços** para verificar se existe um preço válido para a política comercial desejada associado aos SKUs do produto. Confira a seção de [Preços](#precos) para mais informações.|
+    | ![05-botao-logistica](//images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acessar a página **Gerenciar inventário** para verificar se o SKU está disponível em estoque. Confira a seção de [Logística](#logistica) para mais informações. |
+    | ![06-botao-indexed-info](//images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite visualizar cada **Seller **que comercializa o SKU, a política comercial (**Policy**), o preço (**Value**) e a quantidade do SKU em estoque (**Quantity**). |
 
 2. Na linha do produto que corresponde ao SKU a ser verificado, clique na seta para baixo <i class="fas fa-caret-down"></i>, ao lado do botão `Alterar`.
 3. Clique na opção **Sku** para acessar a lista detalhada de SKUs.
 4. Na coluna **Status**, verifique se a situação indicada é `Ativa`. Se os SKUs estiverem ativos, prossiga para o passo 7.
 5. Caso algum SKU esteja com situação `Inativa`, clique em `Alterar` para visualizar as informações detalhadas do SKU.
 
-    ![07-catalogo-skus-pt](https://images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/a1f33a9ce222d960b565f61d47dc1230/07-catalogo-skus-pt.png)
+    ![07-catalogo-skus-pt](//images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/a1f33a9ce222d960b565f61d47dc1230/07-catalogo-skus-pt.png)
 
 6. Na página de informações do SKU, prossiga para a verificação dos itens listados a seguir:
     * **Ativar o SKU se possível:** verifique se esta opção está marcada. Caso contrário, o SKU não será exibido. Ativar esta opção significa determinar que o SKU será ativado se cumprir os requisitos necessários:
@@ -107,9 +107,9 @@ Na página de SKUs, em **Produtos > Catálogo > Produtos e SKUs**, siga as instr
 8. Verifique se o SKU contém pelo menos uma imagem. Se não tiver, o SKU não será ativado – siga o próximo passo para corrigir esse problema.
 9. Clique em `Inserir` para fazer upload de uma nova imagem. Se preferir, clique em `Associar a imagens existentes` para incluir uma imagem já utilizada em outro SKU.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/71839095433fdf925be4cbe97710fb7c/08-aba-imagens-pt.png" alt="08-aba-imagens-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Aba <strong>Imagens</strong></em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/71839095433fdf925be4cbe97710fb7c/08-aba-imagens-pt.png" alt="08-aba-imagens-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Aba <strong>Imagens</strong></em></figcaption></figure>
 
-![09-sku-imagens-pt](https://images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/ef6a125c561d518d683a942b15b3bf58/09-sku-imagens-pt.png)
+![09-sku-imagens-pt](//images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/ef6a125c561d518d683a942b15b3bf58/09-sku-imagens-pt.png)
 
 ### Indexed Info
 
@@ -123,13 +123,13 @@ O registro de indexação apresenta o status de cada SKU do produto. Caso exista
 
 No exemplo abaixo, é possível concluir que o SKU está indisponível por causa da ausência de itens em estoque:
 
-![10-indexed-info-code](https://images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/6c4b52fbcf0abaf0f53e3b49ca224e15/Group_1__7_.png)
+![10-indexed-info-code](//images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/6c4b52fbcf0abaf0f53e3b49ca224e15/Group_1__7_.png)
 
 A partir disso, é possível tomar ações para corrigir o problema. No caso do exemplo, seria necessário ajustar a quantidade de itens em estoque no sistema de [Logística](#logistica).
 
 Um SKU ativo e sem erros terá o registro no indexador similar ao ilustrado a seguir:
 
-![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/a5c498ba9733244ba7d9c85cd02d801c/11-indexed-info-code-active.png)
+![11-indexed-info-code-active](//images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/a5c498ba9733244ba7d9c85cd02d801c/11-indexed-info-code-active.png)
 
 <div class="alert alert-info">
 <p>Se as informações de indexação não apontarem nenhum motivo para a indisponibilidade dos produtos e se você não tiver encontrado nenhum erro no cadastro dos produtos e dos SKUs, é possível que reindexar o produto resolva o problema.</p>
@@ -147,7 +147,7 @@ No módulo de **Preços**, é importante verificar se os SKUs do seu produto con
 
 No exemplo ilustrado a seguir, há três SKUs sem preço base cadastrado. Por isso, não há preço computado na coluna da política comercial – aparece apenas a informação _Preço não cadastrado_.
 
-![12-precos-pt](https://images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/13794723132a95851a9810320575adcf/12-precos-pt.png)
+![12-precos-pt](//images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/13794723132a95851a9810320575adcf/12-precos-pt.png)
 
 ### Criar preço base
 
@@ -175,7 +175,7 @@ O **Simulador de envio** serve para verificar se o item existe em estoque e se s
 2. Preencha as informações necessárias, descritas em [Simulador de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete).
 3. Clique em `Simular frete`.
 
-![13-simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/4acf4052c5e41e259ef8374afae39472/13-simular-frete-pt.png)
+![13-simular-frete-pt](//images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/4acf4052c5e41e259ef8374afae39472/13-simular-frete-pt.png)
 
 <div class="alert alert-info">
 <p>Para investigar um item específico, você deve realizar essa simulação com um <strong>Código postal</strong> atendido por todas as <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Políticas de envio</a> cadastradas, pois saberá que, se o item não estiver disponível para esse CEP, não estará disponível para nenhum outro.</p>
@@ -183,7 +183,7 @@ O **Simulador de envio** serve para verificar se o item existe em estoque e se s
 
 O resultado obtido indica se o produto está disponível ou não para entrega no endereço informado e quais são as melhores opções de frete. Exemplo: caso não existam itens suficientes disponíveis em estoque, o simulador apresenta a seguinte mensagem:
 
-![14-simulador-motivos-pt](https://images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/36096b0e89ac6a6aa7236200be70fb59/14-simulador-motivos-pt.png)
+![14-simulador-motivos-pt](//images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/36096b0e89ac6a6aa7236200be70fb59/14-simulador-motivos-pt.png)
 
 Para mais informações sobre como utilizar o simulador, leia o tutorial [Simulador de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete).
 
@@ -204,7 +204,7 @@ Caso um produto não esteja disponível no site por falta de itens em estoque, v
 3. Para atualizar a contagem de estoque, escreva a quantidade atual na coluna **Atualizar contagem** na linha do SKU desejado, conforme ilustrado a seguir.
 4. Clique em `Salvar`.
 
-![15-gerenciar-inventario-pt](https://images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/3f5d9cfcb6029899be80ba3b2a1d3c7e/15-gerenciar-inventario-pt.gif)
+![15-gerenciar-inventario-pt](//images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/3f5d9cfcb6029899be80ba3b2a1d3c7e/15-gerenciar-inventario-pt.gif)
 
 Para mais informações, leia o tutorial [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
@@ -249,7 +249,7 @@ Siga os passos abaixo para verificar o template que a sua página está utilizan
 
     No exemplo abaixo, o template padrão utilizado é `vtex.curbside-pickup@0.x:store.curbside-pickup` e não há template condicional.
 
-    ![16-templates-cms-pt](https://images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/eb5a2372a8a1dd70d98b8d32676fd710/16-templates-cms-pt.png)
+    ![16-templates-cms-pt](//images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/eb5a2372a8a1dd70d98b8d32676fd710/16-templates-cms-pt.png)
 
 4. Em seguida, é necessário conferir os blocos declarados no template utilizado, conforme descrito em [Templates](#templates).
 
diff --git a/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
index 19868a985..d55632506 100644
--- a/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
@@ -24,7 +24,7 @@ Para realizar esta configuração:
 3. Clique em **Alterar** na linha `Produto - Thumb`.
 4. No painel exibido é possível escolher o tamanho máximo de arquivo para as miniaturas no campo **Tamanho Máximo em KB**.
 
-![Configuração de tipo de arquivo no CMS](https://images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/b7aed6fe9d4892aba36b6695c22fbfb5/PT.PNG)
+![Configuração de tipo de arquivo no CMS](//images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/b7aed6fe9d4892aba36b6695c22fbfb5/PT.PNG)
 
 Recomendamos também a leitura do artigo [Melhorar a performance de imagens de produtos](https://help.vtex.com/pt/tutorial/improving-the-performance-of-product-images/) para aprender como melhorar a qualidade de qualquer imagem da loja evitando ao máximo o prejuízo de performance de carregamento da página.
 
diff --git a/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 2b80665ee..1ecef55c3 100644
--- a/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -21,7 +21,7 @@ Siga os passos abaixo para validar as informações:
 1. Acesse o admin da sua loja: `https://{AccountName}.myvtex.com/admin`.
 2. No menu lateral do admin, clique em __Master Data__.
 3. Na caixa __Profile System__, clique em __Clientes__.
-4. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+4. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 5. Clique no registro do cliente para acessar os detalhes do perfil.
 
 Na seção __Contato__, você verá que a opção `É Empresa?` está preenchida com o valor `Não`. Ao mesmo tempo, na seção __Dados da empresa__, você verá que o campo `Tipo documento` está preenchido com o valor `cnpj`. 
diff --git a/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md b/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md
index cc861a0ff..0cf9e6b59 100644
--- a/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md
+++ b/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md
@@ -3,8 +3,8 @@ title: 'Por que o item do carrinho foi separado?'
 id: frequentlyAskedQuestions_350
 status: PUBLISHED
 createdAt: 2017-04-27T22:37:20.610Z
-updatedAt: 2019-12-31T14:24:24.843Z
-publishedAt: 2019-12-31T14:24:24.843Z
+updatedAt: 2023-07-12T18:31:38.375Z
+publishedAt: 2023-07-12T18:31:38.375Z
 firstPublishedAt: 2017-04-27T23:01:45.290Z
 contentType: frequentlyAskedQuestion
 productTeam: Shopping
@@ -14,13 +14,13 @@ locale: pt
 legacySlug: por-que-o-item-do-carrinho-foi-separado
 ---
 
-Esse cenário acontece quando mais de um item do mesmo SKU é separado em mais de uma linha no carrinho.
+Esse cenário acontece quando mais de um item do mesmo SKU é separado em mais de uma linha no carrinho. Isso ocorre por uma ação denominada rateio - é a divisão de um valor entre os itens.
 
-Isso ocorre por uma ação denominada rateio - é a divisão de um valor entre os itens. Porém, existem cenários em que o valor do desconto é indivisível pelo número de itens, principalmente em casos em que o SKU possui uma unidade multiplicadora e, por isso, é preciso dar descontos diferentes para itens de um mesmo SKU para que o valor do desconto fique correto. O que acaba por deixar os preços diferentes e separando cada unidade em uma linha. Visualize melhor essa explicação com exemplo abaixo:
+Porém, existem cenários em que o valor do desconto é indivisível pelo número de itens, principalmente em casos em que o SKU possui uma unidade multiplicadora e, por isso, é preciso dar descontos diferentes para itens de um mesmo SKU para que o valor do desconto fique correto. O que acaba por deixar os preços diferentes e separando cada unidade em uma linha. Visualize melhor essa explicação com exemplo abaixo:
 
-![](//images.contentful.com/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/65984bd4a878563818fa92d1f58a0db9/Por_que_o_item_do_carrinho_foi_separado.jpg)
+![Por_que_o_item_do_carrinho_foi_separado](//images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/9f522427584df5bf97156641a1ac2bb3/Por_que_o_item_do_carrinho_foi_separado.jpg)
 
-1. Unidade multiplicadora
-2. Preço do produto após o desconto
-3. Preço do produto com a diferença, devido ao rateio
-4. Desconto aplicado
+1. Unidade multiplicadora.
+2. Preço do produto após o desconto.
+3. Preço do produto com a diferença, devido ao rateio.
+4. Desconto aplicado.
diff --git a/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 261a1e246..3750338ad 100644
--- a/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -18,7 +18,7 @@ Existe uma regra de segurança no Checkout que está relacionada à facilidade d
 
 Como o SmartCheckout permite fechar uma compra apenas com o e-mail e com o CVV do cartão, caso o cliente já tenha finalizado compra anteriormente, limitamos a quantidade de tentativas de finalização de compra sem sucesso a 3. Depois dessas 3 tentativas, pedimos o login do cliente.
 
-![LoginPT](https://images.ctfassets.net/alneenqid6w5/6M66QYzmnYoaAieMEkgeQU/ad36bed2e62bedaa2fb6ca5e9efe67c0/LoginPT.png)
+![LoginPT](//images.ctfassets.net/alneenqid6w5/6M66QYzmnYoaAieMEkgeQU/ad36bed2e62bedaa2fb6ca5e9efe67c0/LoginPT.png)
 
 Ou seja, caso o cliente finalize a compra apenas com o e-mail e o CVV do cartão de crédito e a autorização da operadora não ocorra em até 3 vezes seguidas, é mostrada a tela de login para que o cliente continue tentando comprar. Essa contagem volta ao início quando o cliente fizer o login e finalizar sua compra com sucesso.
 
diff --git a/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md b/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md
index c2f4c5d4c..4f8da5a4b 100644
--- a/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md
+++ b/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md
@@ -16,7 +16,7 @@ legacySlug: por-que-a-promocao-nao-foi-aplicada-no-marketplace
 
 Para criar uma promoção para marketplaces, o cenário é quase o mesmo de uma promoção comum, porém, deve-se selecionar no campo **política comercial** o valor **Loja(s) de terceiro(s)** e selecionar a **política comercial** usada pelo marketplace ou preencher o campo **afiliado** com o ID do marketplace.
 
-![marketplace.pt](https://images.ctfassets.net/alneenqid6w5/2WLaENr8b1szg1iBnTS3e9/6f7a2d4e07cc7b0da7173519212e19e4/marketplace.pt.png)
+![marketplace.pt](//images.ctfassets.net/alneenqid6w5/2WLaENr8b1szg1iBnTS3e9/6f7a2d4e07cc7b0da7173519212e19e4/marketplace.pt.png)
 
 Para saber mais detalhes de como fazê-lo, verifique nosso [artigo sobre como criar promoção para marketplace](/pt/tutorial/configurando-promocao-para-marketplace/).
 
diff --git a/docs/known-issues/en/.md b/docs/known-issues/en/.md
index 7f290904e..9d73addb1 100644
--- a/docs/known-issues/en/.md
+++ b/docs/known-issues/en/.md
@@ -28,13 +28,16 @@ internalReference:
 
 
 
- Simulation
+rkaround
+
+
 
 
 
-## Workaround
 
 
+## Workaround
+
 
 
 orkaround
diff --git a/docs/known-issues/en/403-error-for-all-urls-containing-develop.md b/docs/known-issues/en/403-error-for-all-urls-containing-develop.md
new file mode 100644
index 000000000..a374d9eff
--- /dev/null
+++ b/docs/known-issues/en/403-error-for-all-urls-containing-develop.md
@@ -0,0 +1,47 @@
+---
+title: '403 error for all URLs containing develop-'
+id: X6JDmLhD0StgHPGXJd9cZ
+status: PUBLISHED
+createdAt: 2024-02-01T13:46:53.024Z
+updatedAt: 2024-02-01T13:46:54.008Z
+publishedAt: 2024-02-01T13:46:54.008Z
+firstPublishedAt: 2024-02-01T13:46:54.008Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: 403-error-for-all-urls-containing-develop
+locale: en
+kiStatus: Backlog
+internalReference: 975182
+---
+
+## Summary
+
+
+It is expected that a URL can contain any word without generating an error, but the word "**develop"** followed by the "**-**" character generates an automatic 403 error.
+For exemple, a product with the text link  `how-to-develot-a-culture-of-custumer-centricity` will display a 403 erro, since its contain the string "develop-".
+
+
+##
+
+## Simulation
+
+
+
+1. Put the string "develop-" in a text link
+2. Load the product
+3. See the 403 error
+
+
+##
+
+## Workaround
+
+
+Not use the string "develop-"
+
+
+
+
+
diff --git a/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
new file mode 100644
index 000000000..79fd27b81
--- /dev/null
+++ b/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -0,0 +1,45 @@
+---
+title: 'A SKU can be active and have the "activate if possible" flag unchecked'
+id: 5uXQ65flkoEbYeLkNSw4ig
+status: PUBLISHED
+createdAt: 2023-11-07T11:01:20.612Z
+updatedAt: 2023-11-07T11:01:21.419Z
+publishedAt: 2023-11-07T11:01:21.419Z
+firstPublishedAt: 2023-11-07T11:01:21.419Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked
+locale: en
+kiStatus: Backlog
+internalReference: 931324
+---
+
+## Summary
+
+
+It is expected that an active SKU has the "activate if possible" flag checked, however, this is not always the case.
+A SKU can be active and have the "activate if possible" flag unchecked.
+
+
+##
+
+## Simulation
+
+
+Open the SKU admin
+See in the form that the SKU is active and the "activate if possible" flag is unchecked
+
+
+##
+
+## Workaround
+
+
+Save the SKU directly through the admin
+
+
+
+
+
diff --git a/docs/known-issues/en/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md b/docs/known-issues/en/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
new file mode 100644
index 000000000..e4ae07059
--- /dev/null
+++ b/docs/known-issues/en/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
@@ -0,0 +1,46 @@
+---
+title: 'A valid product specification value can be returned blank in the catalog admin'
+id: 46IZtoT2nSKE71g2Tj0m8y
+status: PUBLISHED
+createdAt: 2024-01-16T00:28:14.900Z
+updatedAt: 2024-01-16T00:28:15.482Z
+publishedAt: 2024-01-16T00:28:15.482Z
+firstPublishedAt: 2024-01-16T00:28:15.482Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin
+locale: en
+kiStatus: Backlog
+internalReference: 966499
+---
+
+## Summary
+
+
+It is expected that the product specifications admin will always render the correct values for the specifications of a product. However, this may not always be the case.
+The specification value can be returned blank in the admin as if it had no associated value.
+In addition to the visualization problem, if the user saves the product using product admin, the blank specification value will overwrite the original value
+
+
+##
+
+## Simulation
+
+
+Open a product specification form and compare the value shown in the admin with the value returned by the API.
+
+
+
+##
+
+## Workaround
+
+
+Manage product specifications via API
+
+
+
+
+
diff --git a/docs/known-issues/en/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md b/docs/known-issues/en/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
new file mode 100644
index 000000000..8c2740020
--- /dev/null
+++ b/docs/known-issues/en/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
@@ -0,0 +1,45 @@
+---
+title: 'AB Tester app shows miscalculated information for sessions and conversion'
+id: 2Sgvlldl0kyDcWBVi4KMzg
+status: PUBLISHED
+createdAt: 2023-07-20T12:42:25.435Z
+updatedAt: 2024-07-01T18:49:08.433Z
+publishedAt: 2024-07-01T18:49:08.433Z
+firstPublishedAt: 2023-07-20T12:42:26.335Z
+contentType: knownIssue
+productTeam: Cloud Services
+author: 2mXZkbi0oi061KicTExNjo
+tag: Cloud Services
+slug: ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion
+locale: en
+kiStatus: No Fix
+internalReference: 865727
+---
+
+## Summary
+
+
+AB Tester app shows miscalculated information for sessions and conversion when running tests, causing undesired results interpretation. The workspace split functionality still works as expected.
+
+
+##
+
+## Simulation
+
+
+
+- Create a A/B Test;
+- Let the test run for some time;
+- Check the values for sessions and conversions; it will show miscalculated information.
+
+
+##
+
+## Workaround
+
+
+Use an external analytics tool to analyze the data.
+
+
+
+
diff --git a/docs/known-issues/en/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md b/docs/known-issues/en/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
index 1b0c56f51..6bdbdc759 100644
--- a/docs/known-issues/en/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
+++ b/docs/known-issues/en/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
@@ -3,8 +3,8 @@ title: 'Activate Service on Import (SkuVincularValorServico.aspx) not Working'
 id: 1gM3bYz0IX4ozLrIkWIicb
 status: PUBLISHED
 createdAt: 2022-02-25T14:56:50.052Z
-updatedAt: 2022-11-25T21:44:43.603Z
-publishedAt: 2022-11-25T21:44:43.603Z
+updatedAt: 2024-05-10T14:24:13.156Z
+publishedAt: 2024-05-10T14:24:13.156Z
 firstPublishedAt: 2022-02-25T14:56:50.569Z
 contentType: knownIssue
 productTeam: Catalog
@@ -19,12 +19,37 @@ internalReference: 339894
 ## Summary
 
 
+Currently, in the SkuVincularValorServico.aspx import usability, when trying to change previously exiting services from inactive from active, the values are not changed. The UI prompts that values were changed but nothing actually really happens.
+
+(The opposite is not true, changing from active to inactive works).
+
+
+##
 
 ## Simulation
 
 
+1) Go to the UI https://account.myvtex.com/admin/Site/SkuVincularValorServico.aspx interchanging the rows in the attached sheet from 0 to 1 and vice versa:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ladK39V5My6gjGixeHuNTaV2b/?name=inline-1801216200.png)
+
+2) Check the final effects on the SKU you've changed values of:
+ ![](https://vtexhelp.zendesk.com/attachments/token/znYEzQhMevPcRVYKlBQYa73fF/?name=inline1216426643.png)
+
+You will be able to set them as inactive, but not as active. The import UI prompts that changes were made:
+ ![](https://vtexhelp.zendesk.com/attachments/token/6iKARGtVqTbKaL0vY9s7XPvt6/?name=inline2110004305.png)
+
+No values are actually changed on the given account's database.
+
+
+##
 
 ## Workaround
 
 
+Using the UI to make changes of inactive -->> active and/or our service APIs:
+https://developers.vtex.com/vtex-developer-docs/reference/catalog-api-sku-service
+
+
+
 
diff --git a/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
index 6f37ddca1..daa2bfda7 100644
--- a/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
@@ -31,5 +31,5 @@ Create a new dictionary in the CMS Module that has no previously registered Host
 
 In the CMS module, click on the magnifying glass and then on the "Clear" button to unlock the "Add" new host button.
 
-![PT - Criar dicionário não disponibiliza opção de "Add"](https://images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
+![PT - Criar dicionário não disponibiliza opção de "Add"](//images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
 
diff --git a/docs/known-issues/en/adding-a-new-address-on-invoice-address-returns-null-api-results.md b/docs/known-issues/en/adding-a-new-address-on-invoice-address-returns-null-api-results.md
index 0f501cbf9..dabf06851 100644
--- a/docs/known-issues/en/adding-a-new-address-on-invoice-address-returns-null-api-results.md
+++ b/docs/known-issues/en/adding-a-new-address-on-invoice-address-returns-null-api-results.md
@@ -3,8 +3,8 @@ title: 'Adding a new address on Invoice Address returns null API results'
 id: 43eiz4YORQv1u4yDahZdvC
 status: PUBLISHED
 createdAt: 2023-02-07T13:15:36.832Z
-updatedAt: 2023-02-07T13:15:52.825Z
-publishedAt: 2023-02-07T13:15:52.825Z
+updatedAt: 2024-07-01T18:48:46.296Z
+publishedAt: 2024-07-01T18:48:46.296Z
 firstPublishedAt: 2023-02-07T13:15:37.293Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: adding-a-new-address-on-invoice-address-returns-null-api-results
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 748668
 ---
 
diff --git a/docs/known-issues/en/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md b/docs/known-issues/en/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
new file mode 100644
index 000000000..4c6e8b79a
--- /dev/null
+++ b/docs/known-issues/en/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
@@ -0,0 +1,52 @@
+---
+title: 'Address Form is not shown when the shopper opts to insert a new address'
+id: 4HOP82OvC4smfjPFT8aXJA
+status: PUBLISHED
+createdAt: 2024-07-05T21:16:00.552Z
+updatedAt: 2024-07-05T21:16:01.340Z
+publishedAt: 2024-07-05T21:16:01.340Z
+firstPublishedAt: 2024-07-05T21:16:01.340Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address
+locale: en
+kiStatus: Backlog
+internalReference: 1061637
+---
+
+## Summary
+
+
+Sometimes, when an identified shopper tries to add a new address in checkout's shipping step a message requiring authentication is requested but the address form is not shown and can't be filled.
+
+
+##
+
+## Simulation
+
+
+
+- Go to checkout, identify as a shopper with a complete profile and proceed to the shipping step;
+- Choose the option to deliver to a new address;
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/TFgWp6jleflU5LlPZ3rd4KcTQ/?name=image.png)
+
+
+- Enter the postal code and a message requiring authentication will appear.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/iTNky5H9cDijZ00prjAwQv24h/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/address-review-flow-is-removing-essential-address-information.md b/docs/known-issues/en/address-review-flow-is-removing-essential-address-information.md
index 9e8086dbc..36ebe1b71 100644
--- a/docs/known-issues/en/address-review-flow-is-removing-essential-address-information.md
+++ b/docs/known-issues/en/address-review-flow-is-removing-essential-address-information.md
@@ -3,8 +3,8 @@ title: 'Address review flow is removing essential address information'
 id: 416pFRk6KsWIfgPr8pzWii
 status: PUBLISHED
 createdAt: 2022-08-11T18:33:49.548Z
-updatedAt: 2022-11-25T21:50:56.733Z
-publishedAt: 2022-11-25T21:50:56.733Z
+updatedAt: 2024-02-16T20:23:20.195Z
+publishedAt: 2024-02-16T20:23:20.195Z
 firstPublishedAt: 2022-08-11T18:33:50.049Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: address-review-flow-is-removing-essential-address-information
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 618756
 ---
 
diff --git a/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
new file mode 100644
index 000000000..a054ba53a
--- /dev/null
+++ b/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -0,0 +1,48 @@
+---
+title: 'Addresses are shown in the Checkout when buyer has "Can add shipping" permission'
+id: 2ssiTryGJ6kGoZWxWkGnFF
+status: PUBLISHED
+createdAt: 2024-05-21T22:03:55.172Z
+updatedAt: 2024-05-21T22:03:56.435Z
+publishedAt: 2024-05-21T22:03:56.435Z
+firstPublishedAt: 2024-05-21T22:03:56.435Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission
+locale: en
+kiStatus: Backlog
+internalReference: 1037067
+---
+
+## Summary
+
+
+When a role has the permission "Can add shipping" in the B2B Checkout Settings and a buyer has addresses registered in the Profile System, clicking on "Deliver to another address" in the shipping step and clicking on "Back to address list" shows the addresses from the Profile System.
+
+
+##
+
+## Simulation
+
+
+
+- Add the permission "Can add shipping" in the B2B Checkout Settings via admin to a role;
+- Add the role to a buyer;
+- Log in to the store and assemble a cart;
+- After accessing the checkout, click on "Change shipping options"
+- Click on "Deliver to another address" in the shipping step and click on "Back to address list",
+- Different addresses from the cost center are in the cart.
+
+
+##
+
+## Workaround
+
+
+Enable the Save user data opt-in so no addresses are added to the Profile System.
+
+
+
+
diff --git a/docs/known-issues/en/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md b/docs/known-issues/en/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
new file mode 100644
index 000000000..66be19c03
--- /dev/null
+++ b/docs/known-issues/en/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
@@ -0,0 +1,45 @@
+---
+title: 'Addresses from the profile system is shown when impersonated using VTEX Telemarketing'
+id: 5fFacgD8grxKqJoOO2fwU7
+status: PUBLISHED
+createdAt: 2023-07-12T13:19:48.090Z
+updatedAt: 2023-08-31T19:38:04.369Z
+publishedAt: 2023-08-31T19:38:04.369Z
+firstPublishedAt: 2023-07-12T13:19:48.807Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing
+locale: en
+kiStatus: No Fix
+internalReference: 860375
+---
+
+## Summary
+
+
+When the shopper has addresses registered in the Profile System, and it's impersonated using VTEX Telemarketing, the addresses from Profile System and Organizations are shown
+
+
+##
+
+## Simulation
+
+
+
+- Impersonate a shopper who has addresses registered in the Profile System;
+- Assemble a cart and go to Shipping;
+- Select an address; the component will update and show all addresses from Profile System and Organizations.
+
+
+##
+
+## Workaround
+
+
+
+- Use the B2B Organizations impersonating function.
+
+
+
diff --git a/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md
new file mode 100644
index 000000000..72af9f4e1
--- /dev/null
+++ b/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -0,0 +1,55 @@
+---
+title: 'AddressId mismatch causes "invalid address for an item" error'
+id: 5bSac85eHb9NmrOhcTjHNw
+status: PUBLISHED
+createdAt: 2024-03-01T19:28:52.074Z
+updatedAt: 2024-03-01T19:28:52.875Z
+publishedAt: 2024-03-01T19:28:52.875Z
+firstPublishedAt: 2024-03-01T19:28:52.875Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: addressid-mismatch-causes-invalid-address-for-an-item-error
+locale: en
+kiStatus: Backlog
+internalReference: 992503
+---
+
+## Summary
+
+
+The `shippingData` cart attachment supports the `addressId` field within a few different objects: `logisticsInfo`, `address`, and `selectedAddresses`.
+The `addressId` field is also persisted in the user's saved addresses, kept within Master Data's AD entity.
+
+When placing an order, the Checkout API compares the selected shipping address in the orderForm with the ones available within the user's profile.
+If a match occurs, the `addressId` within `address` and `selectedAddresses` from the orderForm is replaced with the existing value from their profile.
+
+However, at a later point in the API's validations, it will also compare this `addressId` with the one in the `logisticsInfo` object.
+As the one in `logisticsInfo` is not replaced by the aforementioned process, they may not match, and this later validation will fail.
+This triggers an "**invalid address for an item**" / "endereço inválido para um item", preventing the purchase from being completed.
+
+
+
+##
+
+## Simulation
+
+
+
+- Save two different addresses within a user's profile, and take note of their `addressId` values.
+- Assemble a Place Order request. Use one of your addresses created in the previous step, but use the `addressId` of the other one.
+- Send the request. The response will contain the error message "invalid address for an item".
+
+
+##
+
+## Workaround
+
+
+When sending the Place Order request with a previously saved address, ensure the value used for `addressId` matches the actual address data.
+Alternatively, you may also omit the `addressId` from the request.
+
+
+
+
diff --git a/docs/known-issues/en/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md b/docs/known-issues/en/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
index a14f4eb2b..d36ed1b37 100644
--- a/docs/known-issues/en/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
+++ b/docs/known-issues/en/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
@@ -3,8 +3,8 @@ title: 'Adjust shipping query when the order has more than one product - Centaur
 id: 5VsGJar6FBHbGi4OZpxvbk
 status: PUBLISHED
 createdAt: 2022-06-15T19:08:37.828Z
-updatedAt: 2022-11-25T21:56:35.720Z
-publishedAt: 2022-11-25T21:56:35.720Z
+updatedAt: 2024-02-16T20:25:35.893Z
+publishedAt: 2024-02-16T20:25:35.893Z
 firstPublishedAt: 2022-06-15T19:08:38.488Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: adjust-shipping-query-when-the-order-has-more-than-one-product-centauro
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 599380
 ---
 
diff --git a/docs/known-issues/en/admin-collection-brand-list-timeout.md b/docs/known-issues/en/admin-collection-brand-list-timeout.md
index b663d289c..b06aced08 100644
--- a/docs/known-issues/en/admin-collection-brand-list-timeout.md
+++ b/docs/known-issues/en/admin-collection-brand-list-timeout.md
@@ -3,8 +3,8 @@ title: 'Admin Collection Brand List Timeout'
 id: 4de4lqAIhr9mU77EPAbvq1
 status: PUBLISHED
 createdAt: 2022-08-17T15:58:26.950Z
-updatedAt: 2022-11-25T21:43:44.331Z
-publishedAt: 2022-11-25T21:43:44.331Z
+updatedAt: 2024-07-01T18:48:37.335Z
+publishedAt: 2024-07-01T18:48:37.335Z
 firstPublishedAt: 2022-08-17T15:58:27.573Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: admin-collection-brand-list-timeout
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639905
 ---
 
diff --git a/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
new file mode 100644
index 000000000..da9f9980a
--- /dev/null
+++ b/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -0,0 +1,49 @@
+---
+title: "[Admin] Global Search doesn't recognize "Profile Menu items""
+id: 4AZiu9NXouL6b8z5EHJIWK
+status: PUBLISHED
+createdAt: 2024-01-22T17:09:55.423Z
+updatedAt: 2024-01-22T17:09:55.944Z
+publishedAt: 2024-01-22T17:09:55.944Z
+firstPublishedAt: 2024-01-22T17:09:55.944Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-global-search-doesnt-recognize-profile-menu-items
+locale: en
+kiStatus: Backlog
+internalReference: 969645
+---
+
+## Summary
+
+
+Global Search doesn't recognize "Profile Menu items"
+
+
+##
+
+## Simulation
+
+
+In some cases, the search returns no results.
+For example: "Users" "Authentication"
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/QwUkKwavO6WM00STA32BVwyvn/?name=image.png)
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/weT1QdMEqTne83NxeJRN1ilFm/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+Use side menu to access these modules
+
+
+
+
+
diff --git a/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index a2cb2e61c..52dda1b74 100644
--- a/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -30,7 +30,7 @@ This was because the number `1` had been set as the default, even when there was
 
 Log in to your **VTEX Admin > Home > How to improve > Catalog**. If the section indicates that `1` issue was found, by clicking on `Popular products without stock` you will be redirected to the Catalog page.
 
-![Como melhorar EN](https://images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/956eb8af39b7edff3928a4acb13ba700/Como_melhorar_EN.png)
+![Como melhorar EN](//images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/956eb8af39b7edff3928a4acb13ba700/Como_melhorar_EN.png)
 
 
 ## Workaround
@@ -39,5 +39,5 @@ No action is required from the user as we have already fixed the issue. When no
 
 `We didn't find any issues in your catalog`
 
-![Como melhorar fixed EN](https://images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/4251750222051f48f073536c305e0f10/Como_melhorar_fixed_EN.png)
+![Como melhorar fixed EN](//images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/4251750222051f48f073536c305e0f10/Como_melhorar_fixed_EN.png)
 
diff --git a/docs/known-issues/en/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md b/docs/known-issues/en/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
index 5f4aaa062..a204f55aa 100644
--- a/docs/known-issues/en/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
+++ b/docs/known-issues/en/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
@@ -3,8 +3,8 @@ title: 'Admin is showing image extension as .jpg even when the image is .png'
 id: 1nVCuVnNjT7e1E9Cy0Veer
 status: PUBLISHED
 createdAt: 2022-02-02T18:48:49.607Z
-updatedAt: 2022-11-25T21:48:51.993Z
-publishedAt: 2022-11-25T21:48:51.993Z
+updatedAt: 2024-02-16T20:26:18.176Z
+publishedAt: 2024-02-16T20:26:18.176Z
 firstPublishedAt: 2022-02-02T18:48:49.929Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 516269
 ---
 
diff --git a/docs/known-issues/en/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md b/docs/known-issues/en/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
new file mode 100644
index 000000000..a5763e106
--- /dev/null
+++ b/docs/known-issues/en/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
@@ -0,0 +1,53 @@
+---
+title: '[Admin] Master Data module, the admin search engine redirects them to the wrong URL.'
+id: NPUIMi5uS5ngHZBeemIMe
+status: PUBLISHED
+createdAt: 2023-08-28T18:39:23.578Z
+updatedAt: 2023-09-06T15:03:32.872Z
+publishedAt: 2023-09-06T15:03:32.872Z
+firstPublishedAt: 2023-08-28T18:39:24.558Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url
+locale: en
+kiStatus: Fixed
+internalReference: 889045
+---
+
+## Summary
+
+
+The Master Data module, the admin search engine redirects them to the wrong URL.
+
+
+##
+
+## Simulation
+
+
+
+Steps:
+Admin > Search > Master Data >
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/DhvSEUDDmPjgGdIlWV4PJvh0A/?name=image.png)
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/9nUmLbZLPdCzBgvNziUi1WCvw/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+
+it's possible accessed normally using the side menu:
+Admin > Store front > Master Data
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/59KwJCdK91ol1f4edT4hjNBHQ/?name=image.png)
+
+
+
+
+
diff --git a/docs/known-issues/en/admin-review-global-search.md b/docs/known-issues/en/admin-review-global-search.md
new file mode 100644
index 000000000..04f682b06
--- /dev/null
+++ b/docs/known-issues/en/admin-review-global-search.md
@@ -0,0 +1,46 @@
+---
+title: '[admin] review global search'
+id: 1r83M4ug7WVoF1gb22NMh0
+status: PUBLISHED
+createdAt: 2023-08-29T20:01:07.327Z
+updatedAt: 2023-08-29T20:01:08.251Z
+publishedAt: 2023-08-29T20:01:08.251Z
+firstPublishedAt: 2023-08-29T20:01:08.251Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-review-global-search
+locale: en
+kiStatus: Backlog
+internalReference: 889993
+---
+
+## Summary
+
+
+global search isn't finding information about "users"
+
+
+##
+
+## Simulation
+
+
+Steps:
+Admin > global search > Master Data > User
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/bT7SSj1ApVwcvNCxCwtOB8yJj/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+it's possible to access directly through the URL .com/admin/users
+
+
+
+
+
diff --git a/docs/known-issues/en/admin-timeout.md b/docs/known-issues/en/admin-timeout.md
new file mode 100644
index 000000000..464f5a2e7
--- /dev/null
+++ b/docs/known-issues/en/admin-timeout.md
@@ -0,0 +1,50 @@
+---
+title: 'Admin timeout'
+id: 6Kp2viMZSnmGucJnciDNKx
+status: PUBLISHED
+createdAt: 2024-06-17T18:07:48.342Z
+updatedAt: 2024-06-17T18:07:49.170Z
+publishedAt: 2024-06-17T18:07:49.170Z
+firstPublishedAt: 2024-06-17T18:07:49.170Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: admin-timeout
+locale: en
+kiStatus: Backlog
+internalReference: 1051070
+---
+
+## Summary
+
+
+The messages app is receiving a timeout error randomly and some admin pages may need a refresh to work properly.
+
+This may be related to GraphQL queries. Normally you'll see errors in the `/meta` route or a messages app timeout related to the `translateWithDeps` query.
+
+
+##
+
+## Simulation
+
+
+Try accessing some pages on the admin of an account and randomly this page can receive the error below:
+ ![](https://vtexhelp.zendesk.com/attachments/token/zNzGxtaY5SszSHGFiKRMiCXda/?name=image.png)
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/KqbIgf2qqZIAdpYgXJcaiu5FJ/?name=image.png)
+
+When you refresh the page everything should be back to normal
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/adress-without-country-disrupting-orderform-changes.md b/docs/known-issues/en/adress-without-country-disrupting-orderform-changes.md
index ff9b61aaa..4581150e1 100644
--- a/docs/known-issues/en/adress-without-country-disrupting-orderform-changes.md
+++ b/docs/known-issues/en/adress-without-country-disrupting-orderform-changes.md
@@ -3,8 +3,8 @@ title: 'Adress without country disrupting orderForm changes'
 id: 3LfFmUaetyqZij8MCBJtcY
 status: PUBLISHED
 createdAt: 2022-05-16T19:58:42.987Z
-updatedAt: 2022-11-25T21:52:11.051Z
-publishedAt: 2022-11-25T21:52:11.051Z
+updatedAt: 2024-02-16T20:23:23.949Z
+publishedAt: 2024-02-16T20:23:23.949Z
 firstPublishedAt: 2022-05-16T19:58:43.429Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: adress-without-country-disrupting-orderform-changes
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 579814
 ---
 
diff --git a/docs/known-issues/en/adyen-3ds2-double-request-generates-payment-authorization-denial.md b/docs/known-issues/en/adyen-3ds2-double-request-generates-payment-authorization-denial.md
new file mode 100644
index 000000000..5045a420e
--- /dev/null
+++ b/docs/known-issues/en/adyen-3ds2-double-request-generates-payment-authorization-denial.md
@@ -0,0 +1,52 @@
+---
+title: 'Adyen 3DS2 double request generates payment authorization denial'
+id: 3yR8LzaUjclJ22PkAymvoe
+status: PUBLISHED
+createdAt: 2023-09-20T13:09:29.771Z
+updatedAt: 2023-09-20T13:09:30.507Z
+publishedAt: 2023-09-20T13:09:30.507Z
+firstPublishedAt: 2023-09-20T13:09:30.507Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: adyen-3ds2-double-request-generates-payment-authorization-denial
+locale: en
+kiStatus: Backlog
+internalReference: 884154
+---
+
+## Summary
+
+
+When Adyen's 3DS2 request is sent twice it retrieves an error in the response and the payment is automatically denied.
+
+Authorization response:
+
+`{"status":409,"errorCode":"704","message":"request already processed or in progress","errorType":"validation"}`
+
+Following the message:
+
+`Not expected Response [].`
+
+This is an issue when the payment is actually authorized on Adyen's end but since there is no settlement on our side we can't send a refund request.
+
+
+##
+
+## Simulation
+
+
+We were not able to reproduce this scenario or find a pattern so far.
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/en/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md b/docs/known-issues/en/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
new file mode 100644
index 000000000..f4e82fb77
--- /dev/null
+++ b/docs/known-issues/en/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
@@ -0,0 +1,45 @@
+---
+title: 'AdyenV1 does not correctly send the paymentMethod.type for Amex when using Apple Pay.'
+id: UCCG0Lwe3U6dO7MHwFebO
+status: PUBLISHED
+createdAt: 2023-10-17T14:58:27.621Z
+updatedAt: 2023-10-17T14:58:28.348Z
+publishedAt: 2023-10-17T14:58:28.348Z
+firstPublishedAt: 2023-10-17T14:58:28.348Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay
+locale: en
+kiStatus: Backlog
+internalReference: 920563
+---
+
+## Summary
+
+
+Although Apple Pay allows the user to place an order using an Amex card, our AdyenV1 legacy connector does not support this brand.
+
+In the interaction logs, it is noticed that the` paymentMethod.type` field is filled with "scheme," which results in an error from Adyen.
+
+
+##
+
+## Simulation
+
+
+Attempt to place an order using Apple Pay with an Amex card. The transaction will be denied
+
+
+##
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/en/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md b/docs/known-issues/en/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
index 55aa6ffb8..e47bfedbd 100644
--- a/docs/known-issues/en/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
+++ b/docs/known-issues/en/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
@@ -3,8 +3,8 @@ title: 'Alert for fill the scheduled delivery selection appears only once'
 id: f668KUV24RqlpUvDvoIEm
 status: PUBLISHED
 createdAt: 2022-04-25T14:49:29.983Z
-updatedAt: 2022-11-25T21:51:08.681Z
-publishedAt: 2022-11-25T21:51:08.681Z
+updatedAt: 2024-02-16T20:26:02.010Z
+publishedAt: 2024-02-16T20:26:02.010Z
 firstPublishedAt: 2022-04-25T14:49:30.465Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: alert-for-fill-the-scheduled-delivery-selection-appears-only-once
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 565982
 ---
 
diff --git a/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index d1d6fa985..a1567c30a 100644
--- a/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -3,7 +3,7 @@ title: 'ALT attribute not showing in <vtex.cmc:ProductImage zoom="on" />'
 id: 4P1Eys9Q2WFddrMLQVDvM9
 status: DRAFT
 createdAt: 2022-02-17T13:08:53.295Z
-updatedAt: 2022-03-18T15:38:31.951Z
+updatedAt: 2024-02-16T20:26:26.971Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 526563
 ---
 
diff --git a/docs/known-issues/en/amazon-category-implementation.md b/docs/known-issues/en/amazon-category-implementation.md
index fa160d5cc..af40e4fdb 100644
--- a/docs/known-issues/en/amazon-category-implementation.md
+++ b/docs/known-issues/en/amazon-category-implementation.md
@@ -3,8 +3,8 @@ title: 'Amazon category implementation'
 id: 5drX2V0avfk1X2llMyTlK1
 status: PUBLISHED
 createdAt: 2022-03-25T11:33:04.920Z
-updatedAt: 2022-12-02T18:00:24.056Z
-publishedAt: 2022-12-02T18:00:24.056Z
+updatedAt: 2024-02-16T20:24:37.027Z
+publishedAt: 2024-02-16T20:24:37.027Z
 firstPublishedAt: 2022-03-25T11:33:15.226Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazon-category-implementation
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 549924
 ---
 
diff --git a/docs/known-issues/en/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md b/docs/known-issues/en/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
new file mode 100644
index 000000000..51a929b61
--- /dev/null
+++ b/docs/known-issues/en/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
@@ -0,0 +1,49 @@
+---
+title: '[Amazon] Error Code 13013 while sending product to Amazon marketplace'
+id: 5bmPQ4Jzi8HvoDoTaDFv9b
+status: PUBLISHED
+createdAt: 2023-10-27T11:24:52.357Z
+updatedAt: 2023-12-18T17:35:20.302Z
+publishedAt: 2023-12-18T17:35:20.302Z
+firstPublishedAt: 2023-10-27T11:24:53.258Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: amazon-error-code-13013-while-sending-product-to-amazon-marketplace
+locale: en
+kiStatus: Fixed
+internalReference: 926656
+---
+
+## Summary
+
+
+
+Currently we have an issue while trying to export products for Amazon marketplace, there are some cases Amazon itself returns an error 13013. but the error is sometimes not logged in Bridge menu, and some products remains with sucess status, but when they actually have the error below
+
+
+    "code": "13013", "message": "Não há registro do código SKU correspondente a esta atualização em sua conta. Isso geralmente ocorre quando há outros problemas com o código SKU.", "severity": "ERROR",
+
+
+
+##
+
+## Simulation
+
+
+
+Inside the bridge products menu, you may see an error, showing the error code 13013, or any other message, but when checking the Amazon Portal que SKU might not be exported to Amazon.
+
+
+##
+
+## Workaround
+
+
+Is there a workaround for this bug? If yes, describe it here. If not, write "N/A" or "There is no workaround available.". Do not remove this section if there is no workaround, please.
+
+
+
+
+
diff --git a/docs/known-issues/en/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md b/docs/known-issues/en/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
new file mode 100644
index 000000000..51087f947
--- /dev/null
+++ b/docs/known-issues/en/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
@@ -0,0 +1,50 @@
+---
+title: '[Amazon] Error in the update flow sku is not being logged into the bridge'
+id: 1oBkaT6GWZfhB4t2Qpn6c0
+status: PUBLISHED
+createdAt: 2024-02-27T19:40:49.825Z
+updatedAt: 2024-02-27T19:40:50.483Z
+publishedAt: 2024-02-27T19:40:50.483Z
+firstPublishedAt: 2024-02-27T19:40:50.483Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge
+locale: en
+kiStatus: Backlog
+internalReference: 990197
+---
+
+## Summary
+
+
+Error in the update flow sku isn't being logged into the bridge
+
+**Marketplace:** Amazon
+**Root Cause:** Product
+
+
+1. doesn't happen with all skus;
+
+
+##
+
+## Simulation
+
+
+Admin > Marketplace > Products > Amazon
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/l7i4mRjrhA0eo5BWd92YCS46m/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+Reprocess SKU
+
+
+
+
diff --git a/docs/known-issues/en/amazon-global-category-not-working.md b/docs/known-issues/en/amazon-global-category-not-working.md
index fd1d9cb8f..8add1d8e7 100644
--- a/docs/known-issues/en/amazon-global-category-not-working.md
+++ b/docs/known-issues/en/amazon-global-category-not-working.md
@@ -3,8 +3,8 @@ title: 'Amazon global category not working'
 id: 4xG37vNjH3XWVdb57w6zzV
 status: PUBLISHED
 createdAt: 2022-08-12T11:49:47.214Z
-updatedAt: 2022-12-02T18:32:25.769Z
-publishedAt: 2022-12-02T18:32:25.769Z
+updatedAt: 2024-02-16T20:25:10.435Z
+publishedAt: 2024-02-16T20:25:10.435Z
 firstPublishedAt: 2022-08-12T11:49:47.743Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazon-global-category-not-working
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 634199
 ---
 
diff --git a/docs/known-issues/en/amazon-integration-attribute-number-of-itens.md b/docs/known-issues/en/amazon-integration-attribute-number-of-itens.md
index 9e72cb08f..f5538f996 100644
--- a/docs/known-issues/en/amazon-integration-attribute-number-of-itens.md
+++ b/docs/known-issues/en/amazon-integration-attribute-number-of-itens.md
@@ -3,8 +3,8 @@ title: 'Amazon integration attribute Number of itens'
 id: 75Afw210mMY9h6dbk3AV8V
 status: PUBLISHED
 createdAt: 2022-04-07T12:18:04.361Z
-updatedAt: 2022-11-25T21:56:13.168Z
-publishedAt: 2022-11-25T21:56:13.168Z
+updatedAt: 2024-02-16T20:25:56.485Z
+publishedAt: 2024-02-16T20:25:56.485Z
 firstPublishedAt: 2022-04-07T12:18:05.650Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazon-integration-attribute-number-of-itens
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 557788
 ---
 
diff --git a/docs/known-issues/en/amazon-integration-stock-reservations-for-kits.md b/docs/known-issues/en/amazon-integration-stock-reservations-for-kits.md
index f3dadc0f9..cd4559f55 100644
--- a/docs/known-issues/en/amazon-integration-stock-reservations-for-kits.md
+++ b/docs/known-issues/en/amazon-integration-stock-reservations-for-kits.md
@@ -3,8 +3,8 @@ title: 'Amazon integration stock reservations for KITS'
 id: 6ZEvHuGCOEcuQTya1oDOyu
 status: PUBLISHED
 createdAt: 2023-05-22T14:28:54.846Z
-updatedAt: 2023-05-22T14:28:55.337Z
-publishedAt: 2023-05-22T14:28:55.337Z
+updatedAt: 2023-09-27T14:37:26.343Z
+publishedAt: 2023-09-27T14:37:26.343Z
 firstPublishedAt: 2023-05-22T14:28:55.337Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazon-integration-stock-reservations-for-kits
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 829583
 ---
 
diff --git a/docs/known-issues/en/amazoncasacaso-erros-de-rastreamento.md b/docs/known-issues/en/amazoncasacaso-erros-de-rastreamento.md
index 734905227..c16d008a0 100644
--- a/docs/known-issues/en/amazoncasacaso-erros-de-rastreamento.md
+++ b/docs/known-issues/en/amazoncasacaso-erros-de-rastreamento.md
@@ -3,8 +3,8 @@ title: '[Amazon][casacaso] - Erros de rastreamento'
 id: 6a8QqrvjiQBBI2EM22581P
 status: PUBLISHED
 createdAt: 2022-03-10T17:59:48.309Z
-updatedAt: 2022-11-25T21:57:04.066Z
-publishedAt: 2022-11-25T21:57:04.066Z
+updatedAt: 2023-08-16T12:26:16.960Z
+publishedAt: 2023-08-16T12:26:16.960Z
 firstPublishedAt: 2022-03-10T17:59:48.640Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazoncasacaso-erros-de-rastreamento
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 360564
 ---
 
@@ -22,6 +22,7 @@ internalReference: 360564
 We are having issue in some cases where the tracking workflow for Amazon is not working.
 
 
+##
 
 ## Simulation
 
@@ -32,9 +33,14 @@ The below message is shown in bridge UI for tracking Menu:
 As quantidades fornecidas para a ID do pedido (XXXXXXXXXXXX) eram maiores do que as quantidades que podiam ser atendidas. Revise a quantidade a partir do relatório de pedido e leve em conta quaisquer produtos que foram cancelados ou já foram encerrados
 
 
+##
 
 ## Workaround
 
 
 N/A
 
+
+
+
+
diff --git a/docs/known-issues/en/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md b/docs/known-issues/en/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
index 790dbc23e..88182c8fb 100644
--- a/docs/known-issues/en/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
+++ b/docs/known-issues/en/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
@@ -3,8 +3,8 @@ title: 'API Shipping Estimate returns wrong info when SC is null'
 id: 6bxlw1nQ27JGbiOmNbgyn2
 status: PUBLISHED
 createdAt: 2022-04-01T23:33:47.015Z
-updatedAt: 2022-11-25T21:59:23.170Z
-publishedAt: 2022-11-25T21:59:23.170Z
+updatedAt: 2024-07-01T18:48:14.728Z
+publishedAt: 2024-07-01T18:48:14.728Z
 firstPublishedAt: 2022-05-18T18:27:53.441Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: api-shipping-estimate-returns-wrong-info-when-sc-is-null
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 554948
 ---
 
diff --git a/docs/known-issues/en/api-to-list-pickup-points-does-not-return-additionalinfo-field.md b/docs/known-issues/en/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
index e4580f852..e8eb0b745 100644
--- a/docs/known-issues/en/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
+++ b/docs/known-issues/en/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
@@ -3,8 +3,8 @@ title: 'API to list pickup points does not return additionalInfo field'
 id: 5YY5srSA2ZRiOSZiMY9UF9
 status: PUBLISHED
 createdAt: 2022-09-02T12:09:09.980Z
-updatedAt: 2022-11-25T21:50:17.504Z
-publishedAt: 2022-11-25T21:50:17.504Z
+updatedAt: 2024-02-16T20:24:50.684Z
+publishedAt: 2024-02-16T20:24:50.684Z
 firstPublishedAt: 2022-09-02T12:09:10.777Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: api-to-list-pickup-points-does-not-return-additionalinfo-field
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 650714
 ---
 
diff --git a/docs/known-issues/en/app-settings-are-not-erased-when-you-delete-the-app.md b/docs/known-issues/en/app-settings-are-not-erased-when-you-delete-the-app.md
new file mode 100644
index 000000000..6098ac9ce
--- /dev/null
+++ b/docs/known-issues/en/app-settings-are-not-erased-when-you-delete-the-app.md
@@ -0,0 +1,60 @@
+---
+title: 'App settings are not erased when you delete the app'
+id: 7KXfKLgbc3UDeDSsCgT0Sk
+status: PUBLISHED
+createdAt: 2024-07-15T22:29:24.058Z
+updatedAt: 2024-07-15T22:29:24.867Z
+publishedAt: 2024-07-15T22:29:24.867Z
+firstPublishedAt: 2024-07-15T22:29:24.867Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: app-settings-are-not-erased-when-you-delete-the-app
+locale: en
+kiStatus: Backlog
+internalReference: 1065954
+---
+
+## Summary
+
+
+When you install an app from the App Store and access its settings/setup, you have the "**Uninstall**" option, which deletes the app from the workspace but keeps its settings, and the "**Delete**" option, which deletes both the app and its settings.
+However, when you select the "**Delete**" option and install the app again, you notice that the configuration has not been deleted.
+
+
+##
+
+## Simulation
+
+
+
+- Go to the "App Store";
+- Select the app;
+- Click on "Get app";
+- Click on "Install app";
+- Follow the instructions to install the app;
+- Fill in the settings (if applicable) and "Save";
+- Click on "Delete". The following message will be shown:
+ ![](https://vtexhelp.zendesk.com/attachments/token/kM5EhsfVaHLlISckht8rRYumU/?name=image.png)
+
+> _**Do you want to remove the app X?**_
+>
+> _Are you sure you want to delete this app? All of its saved configurations in all workspaces will be lost, and the app will be removed from your app list._
+
+- Click on "Delete" again to confirm. The app will be deleted;
+- Go to the first steps and install the same app;
+- Check its settings, and see that the information has not been delete as expected (the information previously filled in will appear there).
+
+
+##
+
+## Workaround
+
+
+There is no workaround available. But you can put fictitious information.
+
+
+
+
+
diff --git a/docs/known-issues/en/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md b/docs/known-issues/en/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
new file mode 100644
index 000000000..539b49a59
--- /dev/null
+++ b/docs/known-issues/en/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
@@ -0,0 +1,51 @@
+---
+title: 'Apply the discount to the most expensive items - UI not saving data.'
+id: 6VQuVOAtzbA6OyjDEi2bHh
+status: PUBLISHED
+createdAt: 2024-04-03T17:29:36.171Z
+updatedAt: 2024-04-03T17:29:37.024Z
+publishedAt: 2024-04-03T17:29:37.024Z
+firstPublishedAt: 2024-04-03T17:29:37.024Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: apply-the-discount-to-the-most-expensive-items-ui-not-saving-data
+locale: en
+kiStatus: Backlog
+internalReference: 1011071
+---
+
+## Summary
+
+
+When using the promotions UI, manually attempting to save the "Apply to the most expensive items" option will not work and the selector will remain at the cheapest type option.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ofDGJuHHbNRwvbYDMOSSCznvB/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+1 - Go to the promotions User Interface: https://account_name.myvtex.com/admin/promotions
+
+2 - In the promotions UI, select the option to "Apply the discount to the most expensive items"
+
+3 - Save the promotion
+
+4 - Access it once again, the box to apply for the cheapest option will be selected instead.
+
+
+##
+
+## Workaround
+
+
+Use the promotions save API instead https://developers.vtex.com/docs/api-reference/promotions-and-taxes-api#post-/api/rnb/pvt/calculatorconfiguration
+
+
+
+
+
diff --git a/docs/known-issues/en/approved-skus-spreadsheet-not-showing-price.md b/docs/known-issues/en/approved-skus-spreadsheet-not-showing-price.md
index 163c1ce6a..03e6e5f48 100644
--- a/docs/known-issues/en/approved-skus-spreadsheet-not-showing-price.md
+++ b/docs/known-issues/en/approved-skus-spreadsheet-not-showing-price.md
@@ -3,8 +3,8 @@ title: 'Approved Skus Spreadsheet not showing price'
 id: 3nWwzGYX1Ys0rKkoSZZpdz
 status: PUBLISHED
 createdAt: 2022-03-29T19:22:12.977Z
-updatedAt: 2022-11-25T22:00:49.862Z
-publishedAt: 2022-11-25T22:00:49.862Z
+updatedAt: 2024-02-16T20:23:36.636Z
+publishedAt: 2024-02-16T20:23:36.636Z
 firstPublishedAt: 2022-03-29T19:22:13.346Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: approved-skus-spreadsheet-not-showing-price
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 552155
 ---
 
diff --git a/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
new file mode 100644
index 000000000..966bd6706
--- /dev/null
+++ b/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -0,0 +1,67 @@
+---
+title: "Attachents API doesn't allow null "domainValues" (and it should)"
+id: 7KMb6nh0ulcWdEfz7USbPg
+status: PUBLISHED
+createdAt: 2023-09-11T19:02:51.514Z
+updatedAt: 2023-09-11T19:02:52.164Z
+publishedAt: 2023-09-11T19:02:52.164Z
+firstPublishedAt: 2023-09-11T19:02:52.164Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: attachents-api-doesnt-allow-null-domainvalues-and-it-should
+locale: en
+kiStatus: Backlog
+internalReference: 897480
+---
+
+## Summary
+
+
+The update requests for the /api/catalog/pvt/attachment/ API isn't allowing updates for the domain Value field as a null value.
+
+This field is nullable, so this API response is incorrectly responding with:
+
+`{`
+`  "Message": "DomainValues in Domain at position 1 can not be null or empty value"`
+`}`
+
+
+##
+
+## Simulation
+
+
+1 - Create an attachment via UI or API: https://help.vtex.com/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU
+
+2 - try updating it sending the domainValue field as a null, for example:
+
+`{`
+`  "Id": 123,`
+`  "Name": "payload with null domain",`
+`  "IsRequired": true,`
+`  "IsActive": true,`
+`  "Domains": [`
+`      {`
+`          "FieldName": "Basic test",`
+`          "MaxCaracters": "354534",`
+`          "DomainValues": ""`
+`      }`
+`  ]`
+`}`
+
+3 - a "Bad request" response type will be shown to you, when it actually should accept null values for this field.
+
+
+##
+
+## Workaround
+
+
+Update the permitted values manually, via UI or create them already null (the POST method is working, the PUT isn't).
+
+
+
+
+
diff --git a/docs/known-issues/en/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md b/docs/known-issues/en/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
index c6182cf02..6f6603441 100644
--- a/docs/known-issues/en/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
+++ b/docs/known-issues/en/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
@@ -3,8 +3,8 @@ title: 'Attachment Update and Create API validation on field DomainValues not wo
 id: 1NAwwi7C65xM2G61uaTLrB
 status: PUBLISHED
 createdAt: 2023-02-09T16:10:03.814Z
-updatedAt: 2023-02-09T16:10:04.449Z
-publishedAt: 2023-02-09T16:10:04.449Z
+updatedAt: 2024-07-01T18:48:48.654Z
+publishedAt: 2024-07-01T18:48:48.654Z
 firstPublishedAt: 2023-02-09T16:10:04.449Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: attachment-update-and-create-api-validation-on-field-domainvalues-not-working
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 751091
 ---
 
diff --git a/docs/known-issues/en/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md b/docs/known-issues/en/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
new file mode 100644
index 000000000..cf1fc816a
--- /dev/null
+++ b/docs/known-issues/en/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
@@ -0,0 +1,61 @@
+---
+title: 'Attachment validation only in the marketplace when adding an item from a seller with attachment'
+id: 638N4urP08NY7v8jdH7U5N
+status: PUBLISHED
+createdAt: 2023-12-22T18:18:59.194Z
+updatedAt: 2023-12-22T18:18:59.909Z
+publishedAt: 2023-12-22T18:18:59.909Z
+firstPublishedAt: 2023-12-22T18:18:59.909Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment
+locale: en
+kiStatus: Backlog
+internalReference: 957343
+---
+
+## Summary
+
+
+Adding an item from a seller with an attachment in the same API request, the attachment validation happens only in the marketplace.
+
+**Scenario 1:**
+If the marketplace has the same attachment name and the keys differ from the seller's, the error message "Item attachment has an invalid value for key" will be shown, and the item won't be added to the cart.
+
+**Scenario 2:**
+If the marketplace doesn't have the same attachment, the error message "The name of attachment is invalid" will be shown, and the item won't be added to the cart.
+
+This behavior happens in both APIs to add items: Add cart items and Handle cart items.
+
+
+##
+
+## Simulation
+
+
+
+- Configure the same attachment in the marketplace and seller with different field keys;
+- Associate with an item;
+- Add the item via Add cart items or Handle cart items, with attachments.
+
+
+- Configure an attachment in the seller and associate it with an item;
+- Add the item via Add cart items or Handle cart items, with attachments.
+
+
+##
+
+## Workaround
+
+
+
+- Add the item first and the attachment later in different requests. To send the attachment, you can:
+  - send the attachments via Handle cart items;
+  - send the attachments via Add an attachment to an item, for example:
+
+    curl --location 'https://{accountName}.{environment}.com.br/api/checkout/pub/orderForm/{orderFormId}/items/{itemIndex}/attachments/{attachmentName}' \--header 'Content-Type: application/json' \--data '{  "content": {      "key": "value"  },  "noSplitItem": true}'
+
+
+
diff --git a/docs/known-issues/en/attachments-permitted-values-are-not-updated-when-its-added-to-items.md b/docs/known-issues/en/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
new file mode 100644
index 000000000..e5695ae7e
--- /dev/null
+++ b/docs/known-issues/en/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
@@ -0,0 +1,45 @@
+---
+title: "Attachment's permitted values are not updated when it's added to items"
+id: 1JjFJJGsUaLWvthJ7kxSBw
+status: PUBLISHED
+createdAt: 2023-10-17T20:16:40.973Z
+updatedAt: 2023-10-17T20:16:41.571Z
+publishedAt: 2023-10-17T20:16:41.571Z
+firstPublishedAt: 2023-10-17T20:16:41.571Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: attachments-permitted-values-are-not-updated-when-its-added-to-items
+locale: en
+kiStatus: Backlog
+internalReference: 920970
+---
+
+## Summary
+
+
+Attachment's permitted values are not updated if it was added to an item before changing their values in the admin. This will cause an error in the cart with the message "Unable to communicate with seller".
+
+
+##
+
+## Simulation
+
+
+
+- Create an attachment with permitted values;
+- Add an item with the attachment;
+- Change the attachment's permitted values;
+- Refresh the cart.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/attribute-melishippingmode-not-being-updated-in-meli-integration.md b/docs/known-issues/en/attribute-melishippingmode-not-being-updated-in-meli-integration.md
new file mode 100644
index 000000000..0453d15f1
--- /dev/null
+++ b/docs/known-issues/en/attribute-melishippingmode-not-being-updated-in-meli-integration.md
@@ -0,0 +1,48 @@
+---
+title: 'Attribute meli_shipping_mode not being updated in MELI integration'
+id: 7DMsCqv2AsOEsL3LGLhxWq
+status: PUBLISHED
+createdAt: 2023-08-03T10:19:05.524Z
+updatedAt: 2024-06-10T13:38:07.225Z
+publishedAt: 2024-06-10T13:38:07.225Z
+firstPublishedAt: 2023-08-03T10:19:06.574Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: attribute-melishippingmode-not-being-updated-in-meli-integration
+locale: en
+kiStatus: Fixed
+internalReference: 873993
+---
+
+## Summary
+
+
+
+We currently have an issue with the product attribute named "meli_shipping_mode" which is not being updated in MELI integration
+
+
+##
+
+## Simulation
+
+
+
+Inside the product specification the seller can use the attribute "meli_shipping_mode" and set ME1 or ME2 to define the shipping strategy in MELI.
+
+But currently we can only sending this value while creating the SKU in MELI, and we are not updating with the correct value.
+
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md
new file mode 100644
index 000000000..83cd33bc3
--- /dev/null
+++ b/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md
@@ -0,0 +1,46 @@
+---
+title: 'Audit pricing logs showing "unknow" information'
+id: 7b8UDsiBo7VOHCN3pgcfd0
+status: PUBLISHED
+createdAt: 2023-07-05T18:51:22.120Z
+updatedAt: 2023-07-05T18:51:22.566Z
+publishedAt: 2023-07-05T18:51:22.566Z
+firstPublishedAt: 2023-07-05T18:51:22.566Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: audit-pricing-logs-showing-unknow-information
+locale: en
+kiStatus: Backlog
+internalReference: 856420
+---
+
+## Summary
+
+
+A few user actions regarding price modifications are being logged on the audit module as "unknow".
+
+
+##
+
+## Simulation
+
+
+
+1. Merchant makes a few modifications on the pricing module.
+2. Some actions will be correctly logged on the audit.
+3. Verify that some actions will be logged with the fields "Action" and "Event Details" set as "unknow".
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md b/docs/known-issues/en/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
new file mode 100644
index 000000000..d9b36dbd3
--- /dev/null
+++ b/docs/known-issues/en/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
@@ -0,0 +1,43 @@
+---
+title: 'Authorization status is stuck for asynchronous transactions with 2 or more payments when the first one is canceled.'
+id: 7kEU8P6lkSQYZWzgaC16nY
+status: PUBLISHED
+createdAt: 2023-11-02T15:49:18.723Z
+updatedAt: 2023-11-02T19:37:18.326Z
+publishedAt: 2023-11-02T19:37:18.326Z
+firstPublishedAt: 2023-11-02T15:49:19.524Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled
+locale: en
+kiStatus: Backlog
+internalReference: 929517
+---
+
+## Summary
+
+
+When a transaction has multiple payments and becomes asynchronous due to Sherlock or Defense mode, and if the first payment authorization attempt fails, it can result in the other payments being stuck in an "Authorized" status. This is because the entire transaction is canceled, but our worker does not recognize this and proceeds with an authorization attempt for the second payment. Consequently, the second payment cannot be canceled, as the transaction has already been canceled, and it does not allow a cancellation request.
+
+
+##
+
+## Simulation
+
+
+Create a transaction with two payments, in which Defense Mode or any other feature that makes the transaction asynchronous is activated. Then, use a custom provider connector to decline the first payment authorization attempt while approving the other one.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/auto-approve-api-accepts-any-values.md b/docs/known-issues/en/auto-approve-api-accepts-any-values.md
index 0c7ccd3fe..ed708519a 100644
--- a/docs/known-issues/en/auto-approve-api-accepts-any-values.md
+++ b/docs/known-issues/en/auto-approve-api-accepts-any-values.md
@@ -3,8 +3,8 @@ title: 'Auto approve API accepts any values'
 id: kLl4mtwKPPqW6jk5hZMWs
 status: PUBLISHED
 createdAt: 2022-12-12T14:18:51.059Z
-updatedAt: 2022-12-12T14:18:51.733Z
-publishedAt: 2022-12-12T14:18:51.733Z
+updatedAt: 2024-02-16T20:27:19.981Z
+publishedAt: 2024-02-16T20:27:19.981Z
 firstPublishedAt: 2022-12-12T14:18:51.733Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: auto-approve-api-accepts-any-values
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 713704
 ---
 
diff --git a/docs/known-issues/en/autocomplete-bringing-suggestion-products-shown-with-delay.md b/docs/known-issues/en/autocomplete-bringing-suggestion-products-shown-with-delay.md
index 36d6486b5..50cbc559a 100644
--- a/docs/known-issues/en/autocomplete-bringing-suggestion-products-shown-with-delay.md
+++ b/docs/known-issues/en/autocomplete-bringing-suggestion-products-shown-with-delay.md
@@ -3,8 +3,8 @@ title: 'Autocomplete bringing suggestion products shown with delay'
 id: 26ydVkjgikjeBq8Jxuh0Vr
 status: PUBLISHED
 createdAt: 2022-07-12T12:21:25.537Z
-updatedAt: 2023-02-08T13:50:52.209Z
-publishedAt: 2023-02-08T13:50:52.209Z
+updatedAt: 2024-07-01T18:48:28.298Z
+publishedAt: 2024-07-01T18:48:28.298Z
 firstPublishedAt: 2022-07-12T12:21:26.029Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: autocomplete-bringing-suggestion-products-shown-with-delay
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 615616
 ---
 
diff --git a/docs/known-issues/en/autocomplete-not-answering-to-cold-starts.md b/docs/known-issues/en/autocomplete-not-answering-to-cold-starts.md
index 81361e9f9..a03ce31f3 100644
--- a/docs/known-issues/en/autocomplete-not-answering-to-cold-starts.md
+++ b/docs/known-issues/en/autocomplete-not-answering-to-cold-starts.md
@@ -3,8 +3,8 @@ title: 'Autocomplete not answering to cold starts'
 id: 2lgYjT8lmFIvLV3vKOXKmt
 status: PUBLISHED
 createdAt: 2022-02-23T22:01:05.141Z
-updatedAt: 2022-11-25T21:58:01.186Z
-publishedAt: 2022-11-25T21:58:01.186Z
+updatedAt: 2024-03-14T18:48:50.406Z
+publishedAt: 2024-03-14T18:48:50.406Z
 firstPublishedAt: 2022-02-23T22:01:05.666Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: autocomplete-not-answering-to-cold-starts
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 418573
 ---
 
@@ -23,6 +23,7 @@ Intelligent Search feature known as **autocomplete** is not working for some new
 
 
 
+##
 
 ## Simulation
 
@@ -30,9 +31,13 @@ Intelligent Search feature known as **autocomplete** is not working for some new
 N/A.
 
 
+##
 
 ## Workaround
 
 
 Currently there's no workaround for this Known Issue, but autocomplete itself is working properly and will keep learning based on user experience, which means that a while after go-live it will work just fine for new accounts.
 
+
+
+
diff --git a/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
new file mode 100644
index 000000000..99a7640d1
--- /dev/null
+++ b/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -0,0 +1,50 @@
+---
+title: 'Autocomplete Suggestion API removes the dot "." from the product name'
+id: 55185IvERIwGQ3kH6H510O
+status: PUBLISHED
+createdAt: 2024-04-10T13:58:51.138Z
+updatedAt: 2024-04-10T13:58:52.084Z
+publishedAt: 2024-04-10T13:58:52.084Z
+firstPublishedAt: 2024-04-10T13:58:52.084Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: autocomplete-suggestion-api-removes-the-dot-from-the-product-name
+locale: en
+kiStatus: Backlog
+internalReference: 1014701
+---
+
+## Summary
+
+
+This issue occurs when searching for a term, and the autocomplete suggestion returns the product name without the dot character ".", even if it exists in the product name, resulting in incorrect search results.
+
+
+##
+
+## Simulation
+
+
+
+1. GET` https://..com.br/api/io/_v/api/intelligent-search/autocomplete_suggestions?query=`.
+2. Observe the autocomplete suggestions provided by the system.
+3. Note that the dot character is missing from the selected product name.
+
+For example, if the term "headphone" is searched in the autocomplete suggestion API, the suggestion results, if containing a dot in the name, will be displayed as "Headphone Bluetooth 5 0" instead of having the dot in the number "5.0". The correct format should be "Headphone Bluetooth 5.0".
+
+When using this suggestion in the product_search API, will not return results.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index d8a71f481..e7c172260 100644
--- a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Summary
 
-The automatic field works correctly when set to recalculate itself when there is a new entry.  It stops working however, when set to one of the "first hour" options. ![inline1511102536](https://images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
+The automatic field works correctly when set to recalculate itself when there is a new entry.  It stops working however, when set to one of the "first hour" options. ![inline1511102536](//images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/automatic-payment-settlement-incorrectly-setup.md b/docs/known-issues/en/automatic-payment-settlement-incorrectly-setup.md
new file mode 100644
index 000000000..98652ae4b
--- /dev/null
+++ b/docs/known-issues/en/automatic-payment-settlement-incorrectly-setup.md
@@ -0,0 +1,57 @@
+---
+title: 'Automatic payment settlement incorrectly setup'
+id: 6KOQwBKNgOPNL7TM80Bqjf
+status: PUBLISHED
+createdAt: 2024-06-19T22:12:10.705Z
+updatedAt: 2024-06-19T22:12:11.484Z
+publishedAt: 2024-06-19T22:12:11.484Z
+firstPublishedAt: 2024-06-19T22:12:11.484Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: automatic-payment-settlement-incorrectly-setup
+locale: en
+kiStatus: Backlog
+internalReference: 1053010
+---
+
+## Summary
+
+
+The issue is that the gateway ignored the `delayToAutoSettleAfterAntifraud` value.
+
+These fields are required in the authorization response, but the gateway accepts their absence. Our documentation related to this.
+
+        "delayToAutoSettle": 1200, "delayToAutoSettleAfterAntifraud": 1200
+
+In the perfect scenario, the gateway shouldn't accept the response without them.
+
+When the `delayToAutoSettleAfterAntifraud` field is not in the payload of the authorization response. The gateway cannot define the correct value, so the default value of the automatic payment settlement will be 4 days (default).
+
+
+##
+
+## Simulation
+
+
+
+1. Create a payment.
+2. Configure the connector to respond without this required the field delayToAutoSettle, but sending the delayToAutoSettleAfterAntifraud
+3. Check the Authorization response, and it will have only the value that the connector responded to
+4. Please check the purple card to see which value it has set up. The automatic payment settlement will be scheduled for four days after the payment approval.
+
+
+
+##
+
+## Workaround
+
+
+
+Set the **delayAutoSettle** as the same value as **delayAutoSettleAfterAntifraud.**
+
+
+
+
+
diff --git a/docs/known-issues/en/automatic-translation-of-urls-not-occurring-due-to-special-characters.md b/docs/known-issues/en/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
new file mode 100644
index 000000000..4583393ed
--- /dev/null
+++ b/docs/known-issues/en/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
@@ -0,0 +1,47 @@
+---
+title: 'Automatic translation of URLs not occurring due to special characters'
+id: 7G0WKfFFZxZ7mMEoasePld
+status: PUBLISHED
+createdAt: 2024-07-09T19:45:44.410Z
+updatedAt: 2024-07-10T12:45:50.061Z
+publishedAt: 2024-07-10T12:45:50.061Z
+firstPublishedAt: 2024-07-09T19:45:45.704Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: automatic-translation-of-urls-not-occurring-due-to-special-characters
+locale: en
+kiStatus: Backlog
+internalReference: 1062858
+---
+
+## Summary
+
+
+When using the app `admin-catalog-translations` to translate catalog content automatically the linkId may have problems to be translated when it has special characters such as `ç`. The `admin-catalog-translations` uses the `messages app` to do the translations and some words may not be correctly translated due to those characters.
+
+
+##
+
+## Simulation
+
+
+Try to translate the link of a product that has a word with special characters such as `calça`. If you want to translate this word on a URL this will probably be `calca`, which doesn't exist in the Portuguese language so the `message app` will not be able to translate it automatically.
+
+
+##
+
+## Workaround
+
+
+** **
+You must change the URL of the product manually by running the following mutation:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "/yourTranslatedLinkdId/p", "declarer": "vtex.store@2.x", "type": "product", "id": "productId", "resolveAs": "/yourOrinalLinkdId/p", "binding": "bindingId" }}
+
+
+
+
+
+
diff --git a/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
index 485512d71..5faedfba8 100644
--- a/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
@@ -3,8 +3,8 @@ title: 'Automatic update of deliveries tracking by Correios'
 id: 7hKUU5Qp4AyCW2QaMQC0S6
 status: PUBLISHED
 createdAt: 2017-08-16T22:07:06.254Z
-updatedAt: 2022-12-22T14:52:07.213Z
-publishedAt: 2022-12-22T14:52:07.213Z
+updatedAt: 2024-02-29T18:16:47.090Z
+publishedAt: 2024-02-29T18:16:47.090Z
 firstPublishedAt: 2017-08-16T23:00:56.342Z
 contentType: knownIssue
 productTeam: Post-purchase
@@ -34,5 +34,9 @@ It's possible to send tracking updates via API, with emails continuing to be sen
 
 Delivery confirmation via OMS is also passed on to the marketplaces.
 
+<div class = "alert alert-info">
+Now, we offer the <a href="https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib">VTEX Shipping Network</a>, a logistics solution to integrate your operation with Correios and/or carriers with partnerships with VTEX. All of your store's orders linked to this solution will have the tracking automatically updated. (Valid only for Brazil)
+</div>
+
 Another option is to use solutions developed by partners to track deliveries by Correios, such as [XP Agência's tracking system](https://rastreio.xpagencia.com.br/).
 
diff --git a/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
new file mode 100644
index 000000000..ec830756b
--- /dev/null
+++ b/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -0,0 +1,49 @@
+---
+title: '"availability" field is incorrect in Fulfillment Simulation for no stock or price products'
+id: 1k2zcLEN5vG6mnksLwEXxp
+status: PUBLISHED
+createdAt: 2023-10-04T14:22:53.519Z
+updatedAt: 2023-10-04T14:22:54.219Z
+publishedAt: 2023-10-04T14:22:54.219Z
+firstPublishedAt: 2023-10-04T14:22:54.219Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products
+locale: en
+kiStatus: Backlog
+internalReference: 773537
+---
+
+## Summary
+
+
+When a product is out of stock or has no price, the fulfillment simulation incorrectly reports the `availability` field as `available`.
+This behavior also applies to the context of gift selection, where the `selectableGifts` field is likewise affected by this issue.
+
+
+1. If the item has a price, but no stock, the fulfillment simulation will return `"availability": "nullPrice"` when there is no address;
+2. If the item has a price, but no stock, the fulfillment simulation will return `"availability": "available"` when there is an address.
+
+
+##
+
+## Simulation
+
+
+
+- Have a product with no stock or price in a seller
+- Do a Fulfillment Simulation
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md b/docs/known-issues/en/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
new file mode 100644
index 000000000..2425f1bf1
--- /dev/null
+++ b/docs/known-issues/en/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
@@ -0,0 +1,66 @@
+---
+title: 'Available addresses list on Checkout UI missing data for newly created address'
+id: 1BEDcoXLVAs5L039eKXsXv
+status: PUBLISHED
+createdAt: 2024-07-05T21:08:40.994Z
+updatedAt: 2024-07-11T15:56:34.357Z
+publishedAt: 2024-07-11T15:56:34.357Z
+firstPublishedAt: 2024-07-05T21:08:42.246Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address
+locale: en
+kiStatus: Backlog
+internalReference: 1061630
+---
+
+## Summary
+
+
+When a user adds a new address during the Checkout's shipping step, advances to the payment step, and then returns to the shipping step's list of available addresses, this newly created address may be missing from the list or display incomplete information on the UI.
+
+
+##
+
+## Simulation
+
+
+
+Case 1, for authenticated users:
+
+1. Log in to the store with a user who has at least one address saved and create a cart.
+2. Proceed to Checkout and reach the Payment screen.
+3. Click "Change shipping options".
+4. Click "Deliver to another address".
+5. Fill in a new address and click "Go to payment".
+6. Click "Change shipping options" again.
+7. Click "Deliver to another address" again.
+8. Click "Back to address list".
+9. The newly created address may be missing from the list.
+
+Case 2,  for identified but unauthenticated users:
+
+1. Create a cart and identify yourself with the email of a user who has at least one address saved.
+2. Proceed to Checkout and reach the Payment screen.
+3. Click "Change shipping options".
+4. Click "Deliver to another address".
+5. Fill in a new address and click "Go to payment".
+6. Click "Change shipping options" again.
+7. Click "Deliver to another address" again.
+8. Click "Back to address list".
+9. For some countries, the newly added address may show incomplete information, such as showing only the postal code and the country's name.
+
+
+##
+
+## Workaround
+
+
+Refresh the page.
+
+
+
+
+
diff --git a/docs/known-issues/en/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md b/docs/known-issues/en/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
new file mode 100644
index 000000000..a8cae1359
--- /dev/null
+++ b/docs/known-issues/en/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
@@ -0,0 +1,43 @@
+---
+title: 'AvailableQuantity value inconsistent due to the large number of routes created to deliver the item'
+id: 4kKVjSNsIEU8ZVGcpwvzQw
+status: PUBLISHED
+createdAt: 2024-05-16T12:14:20.776Z
+updatedAt: 2024-05-16T12:15:36.200Z
+publishedAt: 2024-05-16T12:15:36.200Z
+firstPublishedAt: 2024-05-16T12:14:21.778Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item
+locale: en
+kiStatus: Backlog
+internalReference: 1034211
+---
+
+## Summary
+
+
+During the indexing pipeline of an item, a simulation is carried out without the use of a postal code to validate availability, this simulation, when it reaches the logistics system, carries out a validation combining all the docks, warehouses and shipping policies available for a sales channel, the response to this calculation determines the availability of the item, however this response has a read limit of 10,000 routes, so when a calculation results in more than 10,000, the remaining routes are disregarded, which can cause the system to return an inconsistent response.
+
+
+##
+
+## Simulation
+
+
+There is no simple way to simulate such a scenario, as you need to have numerous logistics configurations in place.
+
+
+##
+
+## Workaround
+
+
+Remove unused configurations from the sales channel (Docks, Warehouses and Shipping policies), thus reducing the number of routes created by the system during calculation, bringing the number of routes below the limit recommended by the system (10,000).
+
+
+
+
+
diff --git a/docs/known-issues/en/b2b-impersonated-data-is-not-removed-after-logging-out.md b/docs/known-issues/en/b2b-impersonated-data-is-not-removed-after-logging-out.md
new file mode 100644
index 000000000..6a1e9b627
--- /dev/null
+++ b/docs/known-issues/en/b2b-impersonated-data-is-not-removed-after-logging-out.md
@@ -0,0 +1,47 @@
+---
+title: 'B2B impersonated data is not removed after logging out'
+id: bHYLV4reDQl4epmPbYwmJ
+status: PUBLISHED
+createdAt: 2024-07-18T21:56:41.780Z
+updatedAt: 2024-07-18T21:56:42.802Z
+publishedAt: 2024-07-18T21:56:42.802Z
+firstPublishedAt: 2024-07-18T21:56:42.802Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-impersonated-data-is-not-removed-after-logging-out
+locale: en
+kiStatus: Backlog
+internalReference: 1067969
+---
+
+## Summary
+
+
+Logging out after impersonating a user in B2B Suite doesn't remove the storefront-permissions from the session.
+
+This allows the user to navigate the website and even place orders if the impersonated user has access to checkout.
+
+
+##
+
+## Simulation
+
+
+
+- Login with a user with impersonating roles;
+- Impersonate another user;
+- Logout.
+
+
+##
+
+## Workaround
+
+
+Click "Stop Impersonation" to remove the impersonated data from the session.
+
+
+
+
diff --git a/docs/known-issues/en/b2b-orders-history-doesnt-work-in-the-website-domain.md b/docs/known-issues/en/b2b-orders-history-doesnt-work-in-the-website-domain.md
new file mode 100644
index 000000000..178fae395
--- /dev/null
+++ b/docs/known-issues/en/b2b-orders-history-doesnt-work-in-the-website-domain.md
@@ -0,0 +1,43 @@
+---
+title: "B2B Orders History doesn't work in the website domain"
+id: 4Y7lpxWvMBZFaAA4wuvbGP
+status: PUBLISHED
+createdAt: 2023-06-22T21:53:45.542Z
+updatedAt: 2023-08-02T19:09:35.905Z
+publishedAt: 2023-08-02T19:09:35.905Z
+firstPublishedAt: 2023-06-22T21:53:46.030Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-orders-history-doesnt-work-in-the-website-domain
+locale: en
+kiStatus: Fixed
+internalReference: 849394
+---
+
+## Summary
+
+
+B2B Orders History doesn't work in the website domain, showing the message "You don't have permission to access this.".
+
+
+##
+
+## Simulation
+
+
+
+- Access My Account - Orders in the website domain;
+- The message "You don't have permission to access this." will be shown.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md b/docs/known-issues/en/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
new file mode 100644
index 000000000..052d6e374
--- /dev/null
+++ b/docs/known-issues/en/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
@@ -0,0 +1,45 @@
+---
+title: "B2B Organization don't consider accounts using geolocation when registering address"
+id: 2o6k71zZQWGVNDVSTwMZSx
+status: PUBLISHED
+createdAt: 2023-09-21T16:10:29.092Z
+updatedAt: 2023-09-21T16:10:59.672Z
+publishedAt: 2023-09-21T16:10:59.672Z
+firstPublishedAt: 2023-09-21T16:10:29.723Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address
+locale: en
+kiStatus: Backlog
+internalReference: 904907
+---
+
+## Summary
+
+
+B2B Organization don't have anything to configure an address when accounts use geolocation, causing the items to be unavailable.
+
+
+##
+
+## Simulation
+
+
+
+- Configure an account to use geolocation at checkout;
+- Make sure it's an account from countries using predefined options, for example, Argentina, Chile, Colombia, etc;
+- Create an organization;
+- Try to buy any product, it will always be unavailable.
+
+
+##
+
+## Workaround
+
+
+Change the configuration to use only postal code.
+
+
+
diff --git a/docs/known-issues/en/b2b-organizations-detail-ui-only-shows-100-first-sellers.md b/docs/known-issues/en/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
new file mode 100644
index 000000000..7c439dc7a
--- /dev/null
+++ b/docs/known-issues/en/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
@@ -0,0 +1,53 @@
+---
+title: 'B2B Organizations Detail UI only shows 100 first sellers'
+id: 6gZm70bIF0p92u6WtDZqdO
+status: PUBLISHED
+createdAt: 2024-01-15T21:29:19.105Z
+updatedAt: 2024-01-15T21:29:45.018Z
+publishedAt: 2024-01-15T21:29:45.018Z
+firstPublishedAt: 2024-01-15T21:29:19.660Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-organizations-detail-ui-only-shows-100-first-sellers
+locale: en
+kiStatus: Backlog
+internalReference: 966450
+---
+
+## Summary
+
+
+B2B Organizations Detail UI only shows 100 first sellers; the UI doesn't have pagination, making it impossible to select a seller if not in the first page
+
+
+##
+
+## Simulation
+
+
+
+- Make sure the account has more than 100 sellers registered;
+- Access the seller tab in B2B Organizations Detail UI;
+- Only the 100 first sellers will be shown.
+
+
+##
+
+## Workaround
+
+
+
+- Perform a getOrganizationById via graphQL using the app:
+
+    { getOrganizationById(id:""){ id name tradeName status collections { id } paymentTerms { id } priceTables customFields { name type value useOnRegistration } salesChannel sellers { id name }}}
+
+- Perform a mutation using the data from the previous graphQL:
+
+    mutation { updateOrganization ( id: "", name: "" tradeName: "" status: "active" collections: [] paymentTerms: [] priceTables: [] customFields: [] salesChannel: null sellers: [{ id: "", name: "" }] ) { id }}
+
+
+
+
+
diff --git a/docs/known-issues/en/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md b/docs/known-issues/en/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
new file mode 100644
index 000000000..f2de1e0fa
--- /dev/null
+++ b/docs/known-issues/en/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
@@ -0,0 +1,47 @@
+---
+title: "B2B Organizations' impersonate feature doesn't register information in orders"
+id: 48IPJWvzeN0uPjGVyOd3Ff
+status: PUBLISHED
+createdAt: 2024-06-27T13:04:27.839Z
+updatedAt: 2024-06-27T13:04:28.879Z
+publishedAt: 2024-06-27T13:04:28.879Z
+firstPublishedAt: 2024-06-27T13:04:28.879Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-organizations-impersonate-feature-doesnt-register-information-in-orders
+locale: en
+kiStatus: Backlog
+internalReference: 1056736
+---
+
+## Summary
+
+
+B2B Organizations have a native feature to impersonate other members of the organization or cost center.
+
+When an email has the proper permissions and impersonates another member, no impersonation information about who finished the purchase is registered in the order.
+
+
+##
+
+## Simulation
+
+
+
+- Impersonate a member;
+- Assemble a cart;
+- Place an order and check that no information about the impersonation is saved.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md b/docs/known-issues/en/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
new file mode 100644
index 000000000..5f65681fc
--- /dev/null
+++ b/docs/known-issues/en/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
@@ -0,0 +1,44 @@
+---
+title: "B2B Quotes doesn't apply discount at checkout in the website domain"
+id: 2VWm5NVqW1LRSZINAAjM7B
+status: PUBLISHED
+createdAt: 2023-06-22T17:17:04.039Z
+updatedAt: 2024-01-31T21:13:13.614Z
+publishedAt: 2024-01-31T21:13:13.614Z
+firstPublishedAt: 2023-06-22T17:17:04.726Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain
+locale: en
+kiStatus: Fixed
+internalReference: 849080
+---
+
+## Summary
+
+
+When a quote has a discount applied by a salesperson, the B2B Quotes won't apply the discount at checkout in the website domain.
+
+
+##
+
+## Simulation
+
+
+
+- Create a quote;
+- In the website domain, click on "Use Quote";
+- In the cart, there is no change in the item's price.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md b/docs/known-issues/en/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
new file mode 100644
index 000000000..8b85a2fdd
--- /dev/null
+++ b/docs/known-issues/en/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
@@ -0,0 +1,46 @@
+---
+title: "B2B Suite don't use geocoordinates to calculate region Id"
+id: 7ITcf4hiOD1k6XBIhaCclj
+status: PUBLISHED
+createdAt: 2024-06-24T21:48:19.921Z
+updatedAt: 2024-06-27T20:58:12.541Z
+publishedAt: 2024-06-27T20:58:12.541Z
+firstPublishedAt: 2024-06-24T21:48:20.731Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-suite-dont-use-geocoordinates-to-calculate-region-id
+locale: en
+kiStatus: Backlog
+internalReference: 1055033
+---
+
+## Summary
+
+
+It's possible to use shipping rates using postal codes or geocoordinates, but B2B Organizations use only postal codes to calculate region IDs. If an account has geolocation (polygons) registered in its shipping rates, products will be shown as unavailable on the storefront.
+
+
+##
+
+## Simulation
+
+
+
+- Register shipping rates with polygons;
+- Create an organization;
+- Log in in the store;
+- No product is shown.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 4157e0a92..1f0b70450 100644
--- a/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -3,8 +3,8 @@ title: '[B2W] "B2W direct" order (FOB) integrating with carrier'
 id: 20nA7vm1RFMhv7yhaJ43GG
 status: PUBLISHED
 createdAt: 2022-12-12T18:14:19.975Z
-updatedAt: 2022-12-12T18:14:20.451Z
-publishedAt: 2022-12-12T18:14:20.451Z
+updatedAt: 2024-02-16T20:27:21.732Z
+publishedAt: 2024-02-16T20:27:21.732Z
 firstPublishedAt: 2022-12-12T18:14:20.451Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: b2w-b2w-direct-order-fob-integrating-with-carrier
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 714879
 ---
 
diff --git a/docs/known-issues/en/b2w-freight-value-in-oms-vtex.md b/docs/known-issues/en/b2w-freight-value-in-oms-vtex.md
index c97f532f0..d6533cb31 100644
--- a/docs/known-issues/en/b2w-freight-value-in-oms-vtex.md
+++ b/docs/known-issues/en/b2w-freight-value-in-oms-vtex.md
@@ -3,8 +3,8 @@ title: '[B2W] Freight Value in OMS VTEX'
 id: 7kVoMojCNmOHatg2L1ykBP
 status: PUBLISHED
 createdAt: 2022-10-04T19:43:17.116Z
-updatedAt: 2022-11-25T21:55:17.709Z
-publishedAt: 2022-11-25T21:55:17.709Z
+updatedAt: 2024-02-16T20:23:26.779Z
+publishedAt: 2024-02-16T20:23:26.779Z
 firstPublishedAt: 2022-10-04T19:43:20.129Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: b2w-freight-value-in-oms-vtex
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 671748
 ---
 
diff --git a/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md
index 8f307cee7..d56d8c179 100644
--- a/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md
@@ -3,8 +3,8 @@ title: 'Bad Request when searching terms with "%" directly via URL'
 id: 3gdZ8egQRa4zcNRe2f5CbT
 status: PUBLISHED
 createdAt: 2023-03-21T22:51:46.273Z
-updatedAt: 2023-03-21T22:51:46.888Z
-publishedAt: 2023-03-21T22:51:46.888Z
+updatedAt: 2024-02-16T17:45:27.298Z
+publishedAt: 2024-02-16T17:45:27.298Z
 firstPublishedAt: 2023-03-21T22:51:46.888Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -37,7 +37,7 @@ When searching for a term with "%" directly via URL, the page returns a 400 Bad
 ## Workaround
 
 
-Search without the "%"
+N/A
 
 
 
diff --git a/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md
new file mode 100644
index 000000000..18400ec50
--- /dev/null
+++ b/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -0,0 +1,43 @@
+---
+title: 'Bad Request when searching terms with "#" through autocomplete'
+id: 18pMsxubB9eSPGlULAN35p
+status: PUBLISHED
+createdAt: 2024-02-06T20:07:52.739Z
+updatedAt: 2024-02-06T20:07:53.531Z
+publishedAt: 2024-02-06T20:07:53.531Z
+firstPublishedAt: 2024-02-06T20:07:53.531Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: bad-request-when-searching-terms-with-through-autocomplete
+locale: en
+kiStatus: Backlog
+internalReference: 978136
+---
+
+## Summary
+
+
+When searching for a term with "#" directly via autocomplete, the page never loads
+
+
+##
+
+## Simulation
+
+
+
+- Search for any term with "#" in it, for example, "Shirt#" in autocomplete;
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md b/docs/known-issues/en/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
new file mode 100644
index 000000000..8ee6c8006
--- /dev/null
+++ b/docs/known-issues/en/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
@@ -0,0 +1,53 @@
+---
+title: 'Bad request when trying to access an inventory with a huge quantity of reserved items'
+id: 4DujUMKeYTlx2MXAjnHlS5
+status: PUBLISHED
+createdAt: 2024-07-03T20:18:55.508Z
+updatedAt: 2024-07-03T20:23:50.434Z
+publishedAt: 2024-07-03T20:23:50.434Z
+firstPublishedAt: 2024-07-03T20:18:56.626Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items
+locale: en
+kiStatus: Fixed
+internalReference: 296066
+---
+
+## Summary
+
+
+
+When we try to see the details of reservations for an SKU in the logistics module, in the list of product inventory (**Inventory & Shipping** > **Inventory management**), we may have a problem when there are too many active reservations.
+
+It is not possible to access or update an SKU inventory with a huge amount of reserved items, like, 100000 active reservations.
+
+The user may see in the UI the error: **"Error while trying to fetch reservation"**
+
+Or in the API response details the error: **"Too many active reservations"**
+
+
+##
+
+## Simulation
+
+
+
+
+1. In the **Inventory & Shipping** > **Inventory management,** try to find an SKU that has a huge amount of active reservation
+2. Is possible that you get an error trying to view the details
+3. Or try to update the quantity of the SKU
+4. Maybe you will get the error described in the summary
+
+##
+
+##
+
+## Workaround
+
+
+
+The idea is that inventory management avoids the excessive accumulation of active reserves, which implies making inventory updates more frequently, either directly in the UI or via API.
+
diff --git a/docs/known-issues/en/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md b/docs/known-issues/en/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
new file mode 100644
index 000000000..0476d063a
--- /dev/null
+++ b/docs/known-issues/en/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
@@ -0,0 +1,46 @@
+---
+title: 'Badly formatted text for search titles and breadcrumbs in specific scenarios with merchandising rules'
+id: 3dQskVnI1sbF6jgsopjUUt
+status: PUBLISHED
+createdAt: 2024-03-13T20:52:33.781Z
+updatedAt: 2024-03-13T20:52:34.698Z
+publishedAt: 2024-03-13T20:52:34.698Z
+firstPublishedAt: 2024-03-13T20:52:34.698Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules
+locale: en
+kiStatus: Backlog
+internalReference: 999476
+---
+
+## Summary
+
+
+Some search result pages hide the applied filters – as they are already part of the page itself, so they are set as "initialAttributes" – to focus on the additional filters that can be applied. In these scenarios, values for the page title and breadcrumbs are basically defined by the first product from the page.
+
+Merchandising rules that put products from different contexts in the first positions of a page affect this string. When the "initialAttributes" from the page don't match any of the attributes from the first product, as a fallback, these texts are defined by the slug – a simplified text without capitalization, diacritics, or any other special characters.
+
+Be mindful that this type of merchandising rule can be a bad practice.
+
+
+##
+
+## Simulation
+
+
+
+- Consider a category with the tree as "Food > Fruits > Apples and Pears", which translates to "Maçãs e Peras" in Portuguese (so we have diacritics/accents for a better example);
+- Add a product from a different category tree through a Merchandising Rule, as a slicer from the category "Kitchen > Accessories > Slicers" to the category "Food > Fruits";
+- As the first product in the "Apples and Pears" category will be this slicer, the page title and breadcrumbs will be presented as "Macas E Peras".
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md b/docs/known-issues/en/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
new file mode 100644
index 000000000..682a817bc
--- /dev/null
+++ b/docs/known-issues/en/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
@@ -0,0 +1,45 @@
+---
+title: 'Benefits.items array inside of ProductContextProvider shuffle items when the promotion is a Buy Together type'
+id: 1VeBqJAKwpVR5YHqtEJ7Xz
+status: PUBLISHED
+createdAt: 2023-10-05T19:57:59.828Z
+updatedAt: 2023-10-05T19:58:00.724Z
+publishedAt: 2023-10-05T19:58:00.724Z
+firstPublishedAt: 2023-10-05T19:58:00.724Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type
+locale: en
+kiStatus: Backlog
+internalReference: 915213
+---
+
+## Summary
+
+
+When looking at the benefits array inside of the ProductContextProvider on the PDP of a product we can see that not all the products are returned and the ones returned are shuffled. Both lists of products within the promotion are together on the same array. It only happens when the promotion is a Buy Together type.
+
+
+##
+
+## Simulation
+
+
+Go to the PDP of a product that has a Buy Together promotion
+Try to look at the benefits array inside the ProductContextProvider
+Not all the products will be returned on the items array, and there will be no differentiation between the lists of products within the promotion
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/boolean-filter-on-form-application-does-not-work-properly.md b/docs/known-issues/en/boolean-filter-on-form-application-does-not-work-properly.md
new file mode 100644
index 000000000..93a39e479
--- /dev/null
+++ b/docs/known-issues/en/boolean-filter-on-form-application-does-not-work-properly.md
@@ -0,0 +1,54 @@
+---
+title: 'Boolean filter on Form Application does not work properly'
+id: 4x77xCLrvU4gDWZ4s1faHw
+status: PUBLISHED
+createdAt: 2023-10-11T21:15:13.342Z
+updatedAt: 2023-10-11T21:31:06.894Z
+publishedAt: 2023-10-11T21:31:06.894Z
+firstPublishedAt: 2023-10-11T21:15:13.935Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: boolean-filter-on-form-application-does-not-work-properly
+locale: en
+kiStatus: Backlog
+internalReference: 918537
+---
+
+## Summary
+
+
+When a boolean filter is selected, the following message is returned:
+`An unexpected error has occurred. Please try again. If the problem persists, contact support.`
+ ![](https://vtexhelp.zendesk.com/attachments/token/HAwA6Uf51x49bxGLiziKpdQnj/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+
+- Access Master Data CRM (for example https://my-account-here.vtexcrm.com.br);
+- Access a Form Application with boolean filter option:
+ ![](https://vtexhelp.zendesk.com/attachments/token/tyRYoZP61rVzhVBx3A1rHbGgf/?name=image.png)
+
+- Select 0 or 1 option;
+- Click on "_Filter_" button;
+- A popup message will open with the error "`An unexpected error has occurred. Please try again. If the problem persists, contact support.`":
+ ![](https://vtexhelp.zendesk.com/attachments/token/HAwA6Uf51x49bxGLiziKpdQnj/?name=image.png)
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md b/docs/known-issues/en/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
index 6e17da8cd..a4791dd4a 100644
--- a/docs/known-issues/en/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
+++ b/docs/known-issues/en/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
@@ -3,8 +3,8 @@ title: 'Boolean Video/Audio HTML Properties not being validated on Legacy CMS'
 id: 2WjsLZ7vw0KO023rGQd77L
 status: PUBLISHED
 createdAt: 2022-03-16T19:27:06.599Z
-updatedAt: 2022-11-25T22:10:23.568Z
-publishedAt: 2022-11-25T22:10:23.568Z
+updatedAt: 2024-02-16T20:28:59.288Z
+publishedAt: 2024-02-16T20:28:59.288Z
 firstPublishedAt: 2022-03-16T19:27:07.097Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 491898
 ---
 
diff --git a/docs/known-issues/en/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md b/docs/known-issues/en/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
new file mode 100644
index 000000000..e39636aac
--- /dev/null
+++ b/docs/known-issues/en/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
@@ -0,0 +1,40 @@
+---
+title: 'Brands with some special characters are not searchable on the brand admin'
+id: 296otMWGge4c2LJMvVhKEr
+status: PUBLISHED
+createdAt: 2024-01-04T13:57:15.861Z
+updatedAt: 2024-02-16T20:26:37.632Z
+publishedAt: 2024-02-16T20:26:37.632Z
+firstPublishedAt: 2024-01-04T13:57:16.584Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: brands-with-some-special-characters-are-not-searchable-on-the-brand-admin
+locale: en
+kiStatus: No Fix
+internalReference: 503496
+---
+
+## Summary
+
+
+The brand UI, `.myvtex.com/admin/Site/Marca.aspx`, doesn't allow users to search for brands with some special characters in the name, such as apostrophes `'`. Additionally, letters from non-Latin alphabets are also not searchable, for example from the Polish alphabet such as `Ż`.
+
+
+##
+
+## Simulation
+
+
+- Search for any brand with apostrophes on the brand UI;
+- The Search will not find brands with apostrophes.
+
+
+##
+
+## Workaround
+
+
+There is no workaround.
+
diff --git a/docs/known-issues/en/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md b/docs/known-issues/en/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
index 08f8702e4..ac7030a33 100644
--- a/docs/known-issues/en/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
+++ b/docs/known-issues/en/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
@@ -3,8 +3,8 @@ title: 'Broadcaster not notifying all the stock changes to the Intelligent Searc
 id: XLozPnuonjPImtZa8bWAz
 status: PUBLISHED
 createdAt: 2022-10-24T12:26:59.536Z
-updatedAt: 2023-03-29T13:40:37.657Z
-publishedAt: 2023-03-29T13:40:37.657Z
+updatedAt: 2023-07-05T17:37:16.708Z
+publishedAt: 2023-07-05T17:37:16.708Z
 firstPublishedAt: 2022-10-24T12:27:00.490Z
 contentType: knownIssue
 productTeam: Intelligent Search
diff --git a/docs/known-issues/en/buscacep-not-working-in-create-giftlist-form.md b/docs/known-issues/en/buscacep-not-working-in-create-giftlist-form.md
index d46111dc0..8fbf27191 100644
--- a/docs/known-issues/en/buscacep-not-working-in-create-giftlist-form.md
+++ b/docs/known-issues/en/buscacep-not-working-in-create-giftlist-form.md
@@ -3,8 +3,8 @@ title: 'Buscacep not working in create GiftList form.'
 id: 3VRPSO1wYFX5XWrpTSD78X
 status: PUBLISHED
 createdAt: 2022-11-02T13:00:43.442Z
-updatedAt: 2022-11-25T21:42:09.907Z
-publishedAt: 2022-11-25T21:42:09.907Z
+updatedAt: 2024-02-16T20:29:33.235Z
+publishedAt: 2024-02-16T20:29:33.235Z
 firstPublishedAt: 2022-11-02T13:00:44.422Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: buscacep-not-working-in-create-giftlist-form
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 342418
 ---
 
diff --git a/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index df96a6b40..5fa2c85c9 100644
--- a/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -3,8 +3,8 @@ title: 'Button "Cancel" inside the MyCards page not translated to Spanish'
 id: 5wIEEoF7gTLYlWnANxDZ7h
 status: PUBLISHED
 createdAt: 2022-02-24T13:18:00.062Z
-updatedAt: 2022-11-25T22:07:29.627Z
-publishedAt: 2022-11-25T22:07:29.627Z
+updatedAt: 2024-02-16T20:25:05.684Z
+publishedAt: 2024-02-16T20:25:05.684Z
 firstPublishedAt: 2022-02-24T13:18:00.593Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: button-cancel-inside-the-mycards-page-not-translated-to-spanish
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 431200
 ---
 
diff --git a/docs/known-issues/en/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md b/docs/known-issues/en/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
new file mode 100644
index 000000000..941516e6a
--- /dev/null
+++ b/docs/known-issues/en/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
@@ -0,0 +1,46 @@
+---
+title: 'Buttons may not work on the first try in fullcleanup admin'
+id: 4spOMbnKZPCcnQghKTP6Zb
+status: PUBLISHED
+createdAt: 2023-04-14T17:39:56.758Z
+updatedAt: 2024-06-17T13:39:35.332Z
+publishedAt: 2024-06-17T13:39:35.332Z
+firstPublishedAt: 2023-04-14T17:39:57.290Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: buttons-may-not-work-on-the-first-try-in-fullcleanup-admin
+locale: en
+kiStatus: Backlog
+internalReference: 790828
+---
+
+## Summary
+
+
+In the Fullcleanup admin, buttons are expected to act on the first attempt. However, to perform the action, it may be necessary to click the button several times.
+
+
+##
+
+## Simulation
+
+
+
+1. Open Fullcleanup admin - `/Admin/Site/FullCleanUp.aspx  `
+2. Click the button **Reindex Database**
+3. Nothing may occur
+
+
+##
+
+## Workaround
+
+
+Try to click on the bottom more times
+
+
+
+
+
diff --git a/docs/known-issues/en/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md b/docs/known-issues/en/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
new file mode 100644
index 000000000..77a64e0ac
--- /dev/null
+++ b/docs/known-issues/en/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
@@ -0,0 +1,47 @@
+---
+title: 'Buy Together Promotion with lots of SKUs may let the eligible products not to load on the front (timeout)'
+id: e1OJuUhZhYidnoRaDoDRc
+status: PUBLISHED
+createdAt: 2022-01-21T17:36:41.181Z
+updatedAt: 2024-02-16T20:29:59.287Z
+publishedAt: 2024-02-16T20:29:59.287Z
+firstPublishedAt: 2024-01-23T15:09:22.474Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout
+locale: en
+kiStatus: No Fix
+internalReference: 301463
+---
+
+## Summary
+
+
+Buy Together Promotion with lots of SKUs may let the eligible products not load on the front due to timeout. The product pages use the product control `<vtex.cmc:BuyTogether/>`. This control is responsible to bring information of all the eligible SKUs set on the promotion to the product page.
+
+The problem is if the customer sets lots of SKUs on this promotion, the Portal will have to bring this information (price, stock, etc) of all the products from these SKUs to the product page. And Portal does this by simulating its products with the checkout. If we have a promotion that was set with for example with 50 SKUs, and these SKUs are from products that have at least 5 SKUs per product) and they are available for example 3 Sales Channels, Portal will have to simulate with the checkout every SKU for every SC of every product eligible on this promo just to show this specific product page. In this example, Portal will have to make 750 simulations with the checkout ( 50 SKUs set on the promo, assuming that these SKus are from products that have 5 SKUs, it is 250 SKUs, and everyone should be simulated for every SC, what gives to us 750 simulations).
+
+ps: we do not have a correct number to set on the SKU List, as it will depend on every client. If the client has products with few SKUs and only an SC available, they will be able to use more SKUs on this kind of Promo.
+
+
+##
+
+## Simulation
+
+
+- Create a Buy Together Promotion
+- Put on the SKU List 1 or on the SKU list 2 a lot of SKUs, like more than 50.
+- Try to load the Product page that uses the control `<vtex.cmc:BuyTogether/>`, the page should not load due to a time-out.
+
+
+##
+
+## Workaround
+
+
+They have two ways to "solve" this problem:
+- Remove the template control <vtex.cmc:BuyTogether/>, this will make the product page not to load the information about this product available on this promotion;
+- Use fewer SKUs on the list of the Buy Together promotion. One more time, unfortunately, we do not have a specific number that works. I advise the client to try with something like 10 and start increasing and testing.
+
diff --git a/docs/known-issues/en/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md b/docs/known-issues/en/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
new file mode 100644
index 000000000..8cb73c714
--- /dev/null
+++ b/docs/known-issues/en/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
@@ -0,0 +1,45 @@
+---
+title: "Buyers can't login if there is misconfiguration in organizations/cost centers"
+id: r5p7K15FkbZUDSOUQ6hGz
+status: PUBLISHED
+createdAt: 2023-11-30T22:21:39.852Z
+updatedAt: 2023-12-01T20:19:35.375Z
+publishedAt: 2023-12-01T20:19:35.375Z
+firstPublishedAt: 2023-11-30T22:21:40.638Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers
+locale: en
+kiStatus: Backlog
+internalReference: 945609
+---
+
+## Summary
+
+
+When a user has the first organization assigned to them is invalid with the wrong cost center id login fails with no message.
+
+There will be the message `"App storefront-permissions failed, resulting in an error building the session"` in the session response.
+
+
+##
+
+## Simulation
+
+
+
+- Create an organization with the wrong cost center id;
+- Login in the site.
+
+
+##
+
+## Workaround
+
+
+Fix the cost center id associated with the organization or delete the organization.
+
+
+
diff --git a/docs/known-issues/en/calculation-issue-in-comissionamount.md b/docs/known-issues/en/calculation-issue-in-comissionamount.md
new file mode 100644
index 000000000..27560128b
--- /dev/null
+++ b/docs/known-issues/en/calculation-issue-in-comissionamount.md
@@ -0,0 +1,42 @@
+---
+title: 'Calculation issue in comissionAmount'
+id: 1E8DRneWHVncTu5bZ9hNtF
+status: PUBLISHED
+createdAt: 2024-03-15T21:13:28.729Z
+updatedAt: 2024-03-15T21:13:29.705Z
+publishedAt: 2024-03-15T21:13:29.705Z
+firstPublishedAt: 2024-03-15T21:13:29.705Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: calculation-issue-in-comissionamount
+locale: en
+kiStatus: Backlog
+internalReference: 1001005
+---
+
+## Summary
+
+
+This happens in a specific scenario of payout split with multiple payments and sellers (where both are accountable for payment processing charges and chargebacks). The sum of sellers `comissionAmount` is not equal to marketplace `amount` (rounding issue), this difference can cause a settlement denial by acquirer.
+
+
+##
+
+## Simulation
+
+
+We were not able to simulate this as it involves several conditions.
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/en/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md b/docs/known-issues/en/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
new file mode 100644
index 000000000..c43476880
--- /dev/null
+++ b/docs/known-issues/en/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
@@ -0,0 +1,47 @@
+---
+title: "Call center operator's email is sent to orderForm when adding items to cart from Store Framework front-end"
+id: 3KwP4q7VZsu6e3c1DwWY5t
+status: PUBLISHED
+createdAt: 2024-07-16T20:06:11.748Z
+updatedAt: 2024-07-16T20:06:12.844Z
+publishedAt: 2024-07-16T20:06:12.844Z
+firstPublishedAt: 2024-07-16T20:06:12.844Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend
+locale: en
+kiStatus: Backlog
+internalReference: 1066571
+---
+
+## Summary
+
+
+When using Store Framework components to add items to a cart while logged in as a call center operator and not impersonating any customer, the operator's email is filled in the orderForm's clientProfileData attachment.
+
+
+##
+
+## Simulation
+
+
+
+1. Access a store built on Store Framework.
+2. Authenticate as a call center operator.
+3. Without impersonating any customers, add an item to the cart with a component such as add-to-cart-button.
+4. Verify that the cart now contains the call center operator's email address.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md b/docs/known-issues/en/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
new file mode 100644
index 000000000..a9a5ba931
--- /dev/null
+++ b/docs/known-issues/en/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
@@ -0,0 +1,42 @@
+---
+title: 'Callbacks after approval may trigger PaymentAuthorizationWorker to retry payment which may also deny it.'
+id: 1dbTbMRMvJQaxzXjWwQplD
+status: PUBLISHED
+createdAt: 2023-09-15T18:22:54.533Z
+updatedAt: 2023-09-15T18:22:55.496Z
+publishedAt: 2023-09-15T18:22:55.496Z
+firstPublishedAt: 2023-09-15T18:22:55.496Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it
+locale: en
+kiStatus: Backlog
+internalReference: 740499
+---
+
+## Summary
+
+
+When the provider sends a callback right after authorization, it may trigger a new authorization attempt. Hence, in some cases when the transaction has more than 1 payment and one of them is a gift card, a new authorization retry may cancel the transaction when it has no funds.
+
+
+##
+
+## Simulation
+
+
+It can't be simulated as it depends on the provider's callback.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
new file mode 100644
index 000000000..61e439361
--- /dev/null
+++ b/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -0,0 +1,54 @@
+---
+title: 'Campaign audience UI changing "Different from" to "Equal to" with a collection'
+id: 6IkWioZ9WRgg1DFEMdnthB
+status: PUBLISHED
+createdAt: 2023-08-15T15:12:54.580Z
+updatedAt: 2023-08-15T15:18:11.108Z
+publishedAt: 2023-08-15T15:18:11.108Z
+firstPublishedAt: 2023-08-15T15:12:55.461Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection
+locale: en
+kiStatus: Backlog
+internalReference: 881131
+---
+
+## Summary
+
+
+
+When creating a target audience and setting Collections **Different from** this option is saved in the UI, after returning to the target audience it will display as Equal to in the UI, but it keeps your first choice on the API.
+
+
+##
+
+## Simulation
+
+
+
+** **
+Crete a Campaign audience with a target audience, in Collections, select Different From and save.
+Return to the target audience and check that the option Different From changed to Equal to
+
+Before saving:
+ ![](https://vtexhelp.zendesk.com/attachments/token/kHN5aLHsNDPz5pblzihtgsw28/?name=Captura+de+Tela+2023-08-15+a%CC%80s+12.09.12.png)
+
+After saving:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/hLAnRYl94mE99yyyRWVo461j5/?name=Captura+de+Tela+2023-08-15+a%CC%80s+12.09.24.png)
+
+
+##
+
+## Workaround
+
+
+Since this is a visual bug, there's no workaround available. Just check on the API if your option was saved correctly and the target will apply accordingly.
+
+
+
+
+
diff --git a/docs/known-issues/en/campovalorformaspx-save-button-requires-two-clicks.md b/docs/known-issues/en/campovalorformaspx-save-button-requires-two-clicks.md
index ac11652a5..844df061e 100644
--- a/docs/known-issues/en/campovalorformaspx-save-button-requires-two-clicks.md
+++ b/docs/known-issues/en/campovalorformaspx-save-button-requires-two-clicks.md
@@ -3,8 +3,8 @@ title: 'CampoValorForm.aspx Save button requires two clicks'
 id: G0YtmOpdB4nNdw8w87ZNz
 status: PUBLISHED
 createdAt: 2022-02-16T13:28:52.922Z
-updatedAt: 2022-11-25T21:45:10.712Z
-publishedAt: 2022-11-25T21:45:10.712Z
+updatedAt: 2024-02-16T20:26:25.672Z
+publishedAt: 2024-02-16T20:26:25.672Z
 firstPublishedAt: 2022-02-16T13:28:53.505Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: campovalorformaspx-save-button-requires-two-clicks
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 525616
 ---
 
diff --git a/docs/known-issues/en/canonical-tags-are-not-applied-after-3rd-category-level.md b/docs/known-issues/en/canonical-tags-are-not-applied-after-3rd-category-level.md
new file mode 100644
index 000000000..05b372ab5
--- /dev/null
+++ b/docs/known-issues/en/canonical-tags-are-not-applied-after-3rd-category-level.md
@@ -0,0 +1,46 @@
+---
+title: 'Canonical tags are not applied after 3rd category level'
+id: 6HU8WLT5yVRBqeBmGgYRsi
+status: PUBLISHED
+createdAt: 2023-11-08T13:31:23.182Z
+updatedAt: 2024-02-19T19:24:10.757Z
+publishedAt: 2024-02-19T19:24:10.757Z
+firstPublishedAt: 2023-11-08T13:31:24.275Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: canonical-tags-are-not-applied-after-3rd-category-level
+locale: en
+kiStatus: Backlog
+internalReference: 932349
+---
+
+## Summary
+
+
+Canonical tags are not applied after 3rd category level when having a category tree with more than 3 levels (department, category and subcategory), the other above levels aren't displayed in canonical
+
+
+##
+
+## Simulation
+
+
+
+1. Create any 4th level subcategory
+2. Access the page created
+3. Check the Canonical for it on the console, it will not show anything after the 3rd level. Only 3rd and bellow.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/cant-edit-the-name-of-the-styles-template.md b/docs/known-issues/en/cant-edit-the-name-of-the-styles-template.md
new file mode 100644
index 000000000..482307f5b
--- /dev/null
+++ b/docs/known-issues/en/cant-edit-the-name-of-the-styles-template.md
@@ -0,0 +1,43 @@
+---
+title: "Can't edit the name of the Styles template"
+id: 5czxRVaMCZFgvOadfYKl1h
+status: PUBLISHED
+createdAt: 2023-08-16T17:41:40.059Z
+updatedAt: 2023-08-16T17:41:41.113Z
+publishedAt: 2023-08-16T17:41:41.113Z
+firstPublishedAt: 2023-08-16T17:41:41.113Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: cant-edit-the-name-of-the-styles-template
+locale: en
+kiStatus: Backlog
+internalReference: 882147
+---
+
+## Summary
+
+
+Once you create a new style on the Styles module it is not possible to edit its name.
+
+
+##
+
+## Simulation
+
+
+Create your style template on the Styles module and save it. Try to edit its name, you'll see that there is no option for it.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/card-brands-incorrectly-processed-as-visa.md b/docs/known-issues/en/card-brands-incorrectly-processed-as-visa.md
new file mode 100644
index 000000000..c20a062a5
--- /dev/null
+++ b/docs/known-issues/en/card-brands-incorrectly-processed-as-visa.md
@@ -0,0 +1,42 @@
+---
+title: 'Card brands incorrectly processed as Visa'
+id: 7xXie4JWGLWe0ImmHAHzSy
+status: PUBLISHED
+createdAt: 2024-04-30T13:28:23.035Z
+updatedAt: 2024-04-30T20:35:47.075Z
+publishedAt: 2024-04-30T20:35:47.075Z
+firstPublishedAt: 2024-04-30T13:28:24.008Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: card-brands-incorrectly-processed-as-visa
+locale: en
+kiStatus: Backlog
+internalReference: 1024823
+---
+
+## Summary
+
+
+Some credit cards may be processed as Visa when they are actually another brand.
+
+
+##
+
+## Simulation
+
+
+We were not able to replicate this issue, this seems to happen in mobile devices and saved cards.
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/en/card-facebook-doesnt-save-some-settings.md b/docs/known-issues/en/card-facebook-doesnt-save-some-settings.md
index 7637ec285..fd9fec5ee 100644
--- a/docs/known-issues/en/card-facebook-doesnt-save-some-settings.md
+++ b/docs/known-issues/en/card-facebook-doesnt-save-some-settings.md
@@ -3,8 +3,8 @@ title: "Card facebook doesn't save some settings"
 id: 4MTMozT5bmub7Y96TXCl09
 status: PUBLISHED
 createdAt: 2022-03-23T18:52:58.216Z
-updatedAt: 2022-12-02T18:05:07.099Z
-publishedAt: 2022-12-02T18:05:07.099Z
+updatedAt: 2024-02-16T20:26:09.791Z
+publishedAt: 2024-02-16T20:26:09.791Z
 firstPublishedAt: 2022-03-23T18:52:58.849Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: card-facebook-doesnt-save-some-settings
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 548763
 ---
 
diff --git a/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md b/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
new file mode 100644
index 000000000..ce8de38a5
--- /dev/null
+++ b/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
@@ -0,0 +1,47 @@
+---
+title: "Cart created from an old order doesn't bring the assembly options"
+id: 530zUKzAm8oafA8BKl7G8F
+status: PUBLISHED
+createdAt: 2024-04-19T20:21:41.131Z
+updatedAt: 2024-04-19T20:21:42.184Z
+publishedAt: 2024-04-19T20:21:42.184Z
+firstPublishedAt: 2024-04-19T20:21:42.184Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: cart-created-from-an-old-order-doesnt-bring-the-assembly-options
+locale: en
+kiStatus: Backlog
+internalReference: 1020278
+---
+
+## Summary
+
+
+When creating a cart from an old order ("Order again" button on "My orders" screen), the assembly options from the original order will not be retained.
+
+
+##
+
+## Simulation
+
+
+
+1. Order a product with assembly options;
+2. Access the "My orders" screen;
+3. Click on "Order again";
+4. Note that the cart that was then generated only brought the SKUs from the previous order, without their assemblies.
+
+
+##
+
+## Workaround
+
+
+Currently, there is no workaround for this scenario.
+
+
+
+
+
diff --git a/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-attachments.md b/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
index 00f121351..5af7195c2 100644
--- a/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
+++ b/docs/known-issues/en/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
@@ -3,8 +3,8 @@ title: "Cart created from an old order doesn't bring the attachments"
 id: 2TGthMyZOUQWkc2Wo6wgIg
 status: PUBLISHED
 createdAt: 2019-01-08T16:58:19.057Z
-updatedAt: 2023-05-08T18:33:57.918Z
-publishedAt: 2023-05-08T18:33:57.918Z
+updatedAt: 2024-07-01T18:49:01.443Z
+publishedAt: 2024-07-01T18:49:01.443Z
 firstPublishedAt: 2019-01-08T18:21:16.502Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: cart-created-from-an-old-order-doesnt-bring-the-attachments
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 802464
 ---
 
diff --git a/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
new file mode 100644
index 000000000..54823ba3e
--- /dev/null
+++ b/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -0,0 +1,54 @@
+---
+title: "Cart created from an "order again" option in My Orders, the customer's email is not being placed as expected in the orderForm"
+id: 6dDhkaIhquOqaDuNkVZuln
+status: PUBLISHED
+createdAt: 2023-12-04T22:41:21.385Z
+updatedAt: 2023-12-04T22:41:22.139Z
+publishedAt: 2023-12-04T22:41:22.139Z
+firstPublishedAt: 2023-12-04T22:41:22.139Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform
+locale: en
+kiStatus: Backlog
+internalReference: 947563
+---
+
+## Summary
+
+
+
+In the **My Orders** section within **My Account**, there is the option to set up a cart based on an order the customer previously placed.
+
+In this case, the problem is that in a **telesales flow**, when **impersonating the customer and trying to assemble a cart based on a previous order**, when clicking on the **My Orders (List)** at the "**Order again**" option, the email of the telesales agent is placed in the order form client profile data and not the client one as expected.
+
+It is worth mentioning that this behavior only happens when clicking on the "order again" button in the My Orders order list.
+
+
+##
+
+## Simulation
+
+
+
+1. Login with a telesales user
+2. Impersonate a client
+3. Go to the My Orders section within My Account
+4. In the list of orders, click on "order again" on any of them.
+5. Validate the client information in the orderForm (clientProfileData.email)
+
+
+##
+
+## Workaround
+
+
+
+To place orders based on an old one, it is recommended to enter the order details first, and then click on the "order again" option.
+
+
+
+
+
diff --git a/docs/known-issues/en/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md b/docs/known-issues/en/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
new file mode 100644
index 000000000..d621b0c85
--- /dev/null
+++ b/docs/known-issues/en/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
@@ -0,0 +1,43 @@
+---
+title: 'cart item.deliveryType is missing sent by checkout in AdditionalData'
+id: lV8VxXUPOzO9cSMgNV4fj
+status: PUBLISHED
+createdAt: 2024-03-19T12:59:17.599Z
+updatedAt: 2024-03-19T12:59:18.450Z
+publishedAt: 2024-03-19T12:59:18.450Z
+firstPublishedAt: 2024-03-19T12:59:18.450Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata
+locale: en
+kiStatus: Backlog
+internalReference: 1002115
+---
+
+## Summary
+
+
+When there's a quantity split in the `priceDefinition` due to rounding for the unit multiplier, the gateway can receive no value for `deliveryType` in the cart object. So, this might cause the payment provider to deny the payment if they use this field..
+
+
+##
+
+## Simulation
+
+
+
+- Place an order with a cart with a quantity split in the `priceDefinition` field in the orderForm;
+- Check the "miniCart.Items", it may not have have ``deliveryType`.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/cart-itens-are-kept-in-orders-with-total-value-zero.md b/docs/known-issues/en/cart-itens-are-kept-in-orders-with-total-value-zero.md
new file mode 100644
index 000000000..6f947edf7
--- /dev/null
+++ b/docs/known-issues/en/cart-itens-are-kept-in-orders-with-total-value-zero.md
@@ -0,0 +1,45 @@
+---
+title: 'Cart Itens are kept in orders with total value zero'
+id: 66D6RuacgCeCMQDmLPrlNP
+status: PUBLISHED
+createdAt: 2024-06-24T20:59:07.721Z
+updatedAt: 2024-06-24T20:59:08.668Z
+publishedAt: 2024-06-24T20:59:08.668Z
+firstPublishedAt: 2024-06-24T20:59:08.668Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: cart-itens-are-kept-in-orders-with-total-value-zero
+locale: en
+kiStatus: Backlog
+internalReference: 1054999
+---
+
+## Summary
+
+
+Whenever a cart has a total value of `0` no transaction is created upon finishing an order.  When completing an order through checkout's UI no process order request happens, so the cart items and data are kept, and the shopper can create an order with the same cart again.
+
+
+##
+
+## Simulation
+
+
+
+- Create a cart with total value `0`;
+- Finish the purchase;
+- Reaccess the cart after some time; there will be no change in the cart content.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
diff --git a/docs/known-issues/en/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md b/docs/known-issues/en/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
new file mode 100644
index 000000000..561751add
--- /dev/null
+++ b/docs/known-issues/en/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
@@ -0,0 +1,45 @@
+---
+title: "Cart with multiple country addresses lose the pickup address if store can't ship to all the countries"
+id: 5yDJ05btQxQq8BuZzfopqv
+status: PUBLISHED
+createdAt: 2024-07-19T15:02:39.647Z
+updatedAt: 2024-07-19T15:02:41.579Z
+publishedAt: 2024-07-19T15:02:41.579Z
+firstPublishedAt: 2024-07-19T15:02:41.579Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries
+locale: en
+kiStatus: Backlog
+internalReference: 1068197
+---
+
+## Summary
+
+
+If a shopper has several addresses in their profile from different countries, and the store doesn't deliver to any of those addresses, when selecting pickup to a valid address and moving to the payment step, the Checkout UI redirects the shopper back to the shipping step.
+
+
+##
+
+## Simulation
+
+
+
+- Register addresses from a country that the store doesn't offer delivery to;
+- Go to checkout and select a valid address with the country that the store delivers;
+- Click on "Go to payment".
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md b/docs/known-issues/en/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
new file mode 100644
index 000000000..90c0ac9fd
--- /dev/null
+++ b/docs/known-issues/en/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
@@ -0,0 +1,47 @@
+---
+title: 'Carts created from order replacement do not receive promotions correctly'
+id: 2ODIE9RNP7Q5LCglXsztzf
+status: PUBLISHED
+createdAt: 2023-10-20T17:47:40.494Z
+updatedAt: 2023-10-20T17:47:41.099Z
+publishedAt: 2023-10-20T17:47:41.099Z
+firstPublishedAt: 2023-10-20T17:47:41.099Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: carts-created-from-order-replacement-do-not-receive-promotions-correctly
+locale: en
+kiStatus: Backlog
+internalReference: 473424
+---
+
+## Summary
+
+
+Carts created from existing orders through the "replace orders" functionality presented on the "my orders" page are restricted to the original promotion, but without considering that the same promotion can apply to different contexts, such as different payment methods or shipping options.
+
+
+##
+
+## Simulation
+
+
+
+- Have a promotion for multiple payment methods
+- Close the order by paying with "A", which must have a discount
+- On my orders screen, choose to change the order payment method
+- Back to the cart, choose to pay with "B"
+- The discount will not be shown
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/cashback-promotions-do-not-consider-items-removed-from-orders.md b/docs/known-issues/en/cashback-promotions-do-not-consider-items-removed-from-orders.md
new file mode 100644
index 000000000..99a48bb2f
--- /dev/null
+++ b/docs/known-issues/en/cashback-promotions-do-not-consider-items-removed-from-orders.md
@@ -0,0 +1,51 @@
+---
+title: 'Cashback promotions do not consider items removed from orders'
+id: lm9v37jvUSCeh9FVFHjsr
+status: PUBLISHED
+createdAt: 2024-04-19T13:50:10.264Z
+updatedAt: 2024-04-19T13:50:11.130Z
+publishedAt: 2024-04-19T13:50:11.130Z
+firstPublishedAt: 2024-04-19T13:50:11.130Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: cashback-promotions-do-not-consider-items-removed-from-orders
+locale: en
+kiStatus: Backlog
+internalReference: 1019864
+---
+
+## Summary
+
+
+Currently, when using cashback promotions, the calculations are entirely performed in the moment the items are inserted in the cart.
+
+Hence, any changes to the orders done after that are not considered. Consequently, orders that had removed items and only consider the application of cashback after an invoice, the main case for this issue, will still take into account the removed item's cashback even though it was removed.
+
+
+##
+
+## Simulation
+
+
+1 - Create a 10% cashback promotion, restricted to only yourself (to avoid incorrect applications) and with the invoiced condition to apply the credits.
+
+2 - Close a $100 order composed of 2 items: one that costs $80 and the other $20.
+
+3 - The applied credits should be $10. Remove the $8 item from the order and invoice it.
+
+4 - You will still be credited $10 as a cashback, despite the expected value now being $2, which happens because the promotion calculations are done during the checkout simulation, before the order is closed.
+
+
+##
+
+## Workaround
+
+
+There is no workaround.
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md b/docs/known-issues/en/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
index eae9c263e..75dcd3bb7 100644
--- a/docs/known-issues/en/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
+++ b/docs/known-issues/en/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
@@ -3,8 +3,8 @@ title: 'Catalog API /catalog/pvt/stockkeepingunit with query parameter refId ret
 id: 71Y9CFaM10xaVyQkcgKydQ
 status: PUBLISHED
 createdAt: 2022-01-21T15:28:34.187Z
-updatedAt: 2022-12-22T15:16:11.363Z
-publishedAt: 2022-12-22T15:16:11.363Z
+updatedAt: 2024-02-16T20:24:19.402Z
+publishedAt: 2024-02-16T20:24:19.402Z
 firstPublishedAt: 2022-12-22T15:16:11.363Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 388869
 ---
 
diff --git a/docs/known-issues/en/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md b/docs/known-issues/en/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
new file mode 100644
index 000000000..442ae7163
--- /dev/null
+++ b/docs/known-issues/en/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
@@ -0,0 +1,47 @@
+---
+title: "Catalog API doesn't respond properly to space at the end of strings"
+id: 37TmHtc19126iarlQ4IL2p
+status: PUBLISHED
+createdAt: 2024-02-05T16:49:35.136Z
+updatedAt: 2024-07-01T18:49:25.845Z
+publishedAt: 2024-07-01T18:49:25.845Z
+firstPublishedAt: 2024-02-05T16:49:36.178Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings
+locale: en
+kiStatus: No Fix
+internalReference: 977033
+---
+
+## Summary
+
+
+When using the catalog API collection, if a string JSON field is sent ending with spaces (for instance productName: "myProductName    ") the catalog APIs will respond with an improper 400 response and empty response body, leaving the user clueless about what was sent improperly.
+
+The correct response should still be a 400 (bad request) but with an error handling informing which field is incorrect and why.
+
+
+##
+
+## Simulation
+
+
+For any catalog API (https://developers.vtex.com/docs/api-reference/catalog-api) insert 1+ empty spaces at the end of a string field, such as exemplified above.
+
+
+##
+
+## Workaround
+
+
+n/a
+
+This type of string should not be accepted, but the error handling must be adjusted.
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-export-cannot-handle-t-and-s-characters.md b/docs/known-issues/en/catalog-export-cannot-handle-t-and-s-characters.md
new file mode 100644
index 000000000..02546418f
--- /dev/null
+++ b/docs/known-issues/en/catalog-export-cannot-handle-t-and-s-characters.md
@@ -0,0 +1,47 @@
+---
+title: 'Catalog export cannot handle ț and ș characters.'
+id: 1c28limdEHowD4LKDeHAB1
+status: PUBLISHED
+createdAt: 2023-12-11T17:40:16.688Z
+updatedAt: 2023-12-11T17:40:17.536Z
+publishedAt: 2023-12-11T17:40:17.536Z
+firstPublishedAt: 2023-12-11T17:40:17.536Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-export-cannot-handle-t-and-s-characters
+locale: en
+kiStatus: Backlog
+internalReference: 950933
+---
+
+## Summary
+
+
+Currently, the catalog import/export cuts our the special characters ț and ș when exporting data.
+
+
+##
+
+## Simulation
+
+
+1 - Create a product that has ș in its name.
+
+2 - in the export tab of the catalog module, try exporting a spreadsheet.
+
+3 - this character will not be shown in the exported spreadsheet.
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-export-for-attachment-cuts-50-characters.md b/docs/known-issues/en/catalog-export-for-attachment-cuts-50-characters.md
new file mode 100644
index 000000000..f143ff981
--- /dev/null
+++ b/docs/known-issues/en/catalog-export-for-attachment-cuts-50-characters.md
@@ -0,0 +1,51 @@
+---
+title: 'Catalog export for attachment cuts > 50 characters'
+id: 7hX23y19wmMNPTUgbhh2WX
+status: PUBLISHED
+createdAt: 2023-12-14T16:46:58.819Z
+updatedAt: 2023-12-14T16:46:59.522Z
+publishedAt: 2023-12-14T16:46:59.522Z
+firstPublishedAt: 2023-12-14T16:46:59.522Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-export-for-attachment-cuts-50-characters
+locale: en
+kiStatus: Backlog
+internalReference: 953161
+---
+
+## Summary
+
+
+When importing data for attachments in the catalog module, if the said attachment is over 50 characters long, the string is cut, leading to no updates for this data.
+
+
+##
+
+## Simulation
+
+
+1 - create an attachment with a name over 50 characters long, for instance, "This is a very long attachment name that is created to test an issue".
+
+2 - associate it to a product
+
+3 - export this data using the UI /admin/Site/Relatorio_Skus.aspx
+
+4 - Check the column related to this and it will be displayed as "`This is a very long attachment name that is create`" (exactly at 50 characters).
+
+5 - you will need to manually adjust this information if you want to properly import it
+
+
+##
+
+## Workaround
+
+
+Update attachments via API, UI, or manually change their incorrect string in the sheet.
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-filters-timeout.md b/docs/known-issues/en/catalog-filters-timeout.md
new file mode 100644
index 000000000..11077df5c
--- /dev/null
+++ b/docs/known-issues/en/catalog-filters-timeout.md
@@ -0,0 +1,45 @@
+---
+title: 'Catalog Filters Timeout'
+id: 5KtT2SvTSO6xMdJOSYz5VZ
+status: PUBLISHED
+createdAt: 2023-10-19T17:11:37.486Z
+updatedAt: 2023-10-19T17:11:38.181Z
+publishedAt: 2023-10-19T17:11:38.181Z
+firstPublishedAt: 2023-10-19T17:11:38.181Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-filters-timeout
+locale: en
+kiStatus: Backlog
+internalReference: 922350
+---
+
+## Summary
+
+
+For stores with a large quantity of skus (1 million or more), often, when filtering using the catalog UI's filters, either for the main menu or for the reports section, if the filter query returns a very large result, the UI times out (504 gateway timeout)
+
+
+##
+
+## Simulation
+
+
+There is no reliable way to simulate it consistently - only specific large queries for few accounts end up in the error.
+
+
+##
+
+## Workaround
+
+
+Request a "user filter cleanup" to the product team.
+
+Also, if the same query is often generating a timeout (i.e. you filter for a specific department and it times out), consider performing filters that select a subset of what you want (in the same example, a category within the given department)
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-graphql-categoryinputtranslation-not-working.md b/docs/known-issues/en/catalog-graphql-categoryinputtranslation-not-working.md
new file mode 100644
index 000000000..a70a8a864
--- /dev/null
+++ b/docs/known-issues/en/catalog-graphql-categoryinputtranslation-not-working.md
@@ -0,0 +1,45 @@
+---
+title: 'Catalog GraphQL CategoryInputTranslation not working'
+id: 1Zue7Roia2sYa4xNP9hF2y
+status: PUBLISHED
+createdAt: 2024-04-29T14:30:53.743Z
+updatedAt: 2024-04-29T14:30:54.577Z
+publishedAt: 2024-04-29T14:30:54.577Z
+firstPublishedAt: 2024-04-29T14:30:54.577Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-graphql-categoryinputtranslation-not-working
+locale: en
+kiStatus: Backlog
+internalReference: 1024172
+---
+
+## Summary
+
+
+Currently, the method CategoryInputTranslation, for the catalog graphQL is not generating an update in the translated data for accounts.
+
+
+##
+
+## Simulation
+
+
+1 - Acess VTEX's graphQL IDE and select the application vtex.catalog-graphql@1.103.1
+2 - Create a mutation for the method CategoryInputTranslation
+3 - Check if such update has reflected in the translated data in the website
+
+
+##
+
+## Workaround
+
+
+Directly use the VTEX messages app for translating data instead (vtex.messages)
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-indexer-generating-invalid-translation-documents.md b/docs/known-issues/en/catalog-indexer-generating-invalid-translation-documents.md
new file mode 100644
index 000000000..9b8dbf48a
--- /dev/null
+++ b/docs/known-issues/en/catalog-indexer-generating-invalid-translation-documents.md
@@ -0,0 +1,44 @@
+---
+title: 'Catalog indexer generating invalid translation documents'
+id: 3pbXOA3DQILdu05tAwjlVM
+status: PUBLISHED
+createdAt: 2024-02-29T18:02:38.600Z
+updatedAt: 2024-07-01T18:49:27.852Z
+publishedAt: 2024-07-01T18:49:27.852Z
+firstPublishedAt: 2024-02-29T18:02:39.430Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-indexer-generating-invalid-translation-documents
+locale: en
+kiStatus: No Fix
+internalReference: 991494
+---
+
+## Summary
+
+
+When indexing a product with translated information the app messages is requested. These requests are supposed to be under 3s and when they take more than that the indexation fails and generates an invalide translation document.
+
+
+
+##
+
+## Simulation
+
+
+There is no easy way to reproduce this scenario, but accounts with a lot of languages or a lot of fields to translate are more susceptible to this scenario.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md
index aef1ff535..9088420ed 100644
--- a/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md
@@ -3,8 +3,8 @@ title: 'Catalog Indexing Report "Total" Section Calculation Error'
 id: 6TJXux104P2c0mruo5vlEn
 status: PUBLISHED
 createdAt: 2022-02-25T11:39:42.098Z
-updatedAt: 2022-11-25T21:45:40.741Z
-publishedAt: 2022-11-25T21:45:40.741Z
+updatedAt: 2024-02-16T20:26:35.750Z
+publishedAt: 2024-02-16T20:26:35.750Z
 firstPublishedAt: 2022-02-25T11:39:42.485Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalog-indexing-report-total-section-calculation-error
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 499450
 ---
 
diff --git a/docs/known-issues/en/catalog-integration-xml-fiscal-code-field-not-rendering.md b/docs/known-issues/en/catalog-integration-xml-fiscal-code-field-not-rendering.md
new file mode 100644
index 000000000..d67814bb5
--- /dev/null
+++ b/docs/known-issues/en/catalog-integration-xml-fiscal-code-field-not-rendering.md
@@ -0,0 +1,48 @@
+---
+title: 'Catalog Integration XML fiscal code field not rendering'
+id: 19Ubw33gsHcyIeMUQA3LGh
+status: PUBLISHED
+createdAt: 2024-05-10T14:28:22.117Z
+updatedAt: 2024-05-10T14:28:23.190Z
+publishedAt: 2024-05-10T14:28:23.190Z
+firstPublishedAt: 2024-05-10T14:28:23.190Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-integration-xml-fiscal-code-field-not-rendering
+locale: en
+kiStatus: Backlog
+internalReference: 1031109
+---
+
+## Summary
+
+
+Currently, the catalog XML configuration for the fiscal code field is not rendering the expected results, it always returns a <![CDATA[]]>
+
+
+##
+
+## Simulation
+
+
+1 - Register a fiscal code in a product of your store.
+2 - In your account's XML configuration https://myaccountname.myvtex.com/admin/Site/Xml.aspx, set up the XML fiscal code field
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/LHjBFETlon2zWcRX7pXYF0xjP/?name=image.png)
+
+3 - Load the generated XML and, despite the product having valid data in it, the fiscal code XML tags will not load valid content.
+
+
+##
+
+## Workaround
+
+
+Use other means of catalog integration if a fiscal code is absolutely necessary in your store's operations.
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-search-api-limited-to-2500-results.md b/docs/known-issues/en/catalog-search-api-limited-to-2500-results.md
new file mode 100644
index 000000000..f0a7651e3
--- /dev/null
+++ b/docs/known-issues/en/catalog-search-api-limited-to-2500-results.md
@@ -0,0 +1,47 @@
+---
+title: 'Catalog Search API limited to 2500 results'
+id: 33kKjUGKN5tlxvksnbnw7n
+status: PUBLISHED
+createdAt: 2023-08-31T14:59:31.132Z
+updatedAt: 2023-08-31T14:59:31.766Z
+publishedAt: 2023-08-31T14:59:31.766Z
+firstPublishedAt: 2023-08-31T14:59:31.766Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-search-api-limited-to-2500-results
+locale: en
+kiStatus: Backlog
+internalReference: 891184
+---
+
+## Summary
+
+
+When using Catalog Search API the maximum results obtained is 2500, even if there are more products.
+The pagination is up to 50 products and it works correctly until the parameter _from reaches the number of 2500. When they set `_from` above 2500 they get `"Parameter _from can't be greater than 2500."`
+
+
+##
+
+## Simulation
+
+
+This situation can happen when requesting the API using postman or using the shared catalog on seller portal accounts (it uses the same API on the UI).
+
+When using API: - make the request using the paramenter `_from` above 2500
+When using Shared Catalog: - skip the pagination on available products tab until you reach 2500. The next pages won't update and will show the same results as the page before 2500.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md b/docs/known-issues/en/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
index d52913de4..296d18e70 100644
--- a/docs/known-issues/en/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
+++ b/docs/known-issues/en/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
@@ -3,8 +3,8 @@ title: 'Catalog Search Facets API does not return information for products unava
 id: 1JrbscqI4BQgFqfVuRZIl8
 status: PUBLISHED
 createdAt: 2022-05-23T13:58:53.501Z
-updatedAt: 2022-11-25T21:45:53.573Z
-publishedAt: 2022-11-25T21:45:53.573Z
+updatedAt: 2024-02-16T20:25:52.080Z
+publishedAt: 2024-02-16T20:25:52.080Z
 firstPublishedAt: 2022-05-23T13:58:53.924Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalog-search-facets-api-does-not-return-information-for-products-unavailable
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 583623
 ---
 
diff --git a/docs/known-issues/en/catalog-translations-not-reflecting-on-the-frontend.md b/docs/known-issues/en/catalog-translations-not-reflecting-on-the-frontend.md
new file mode 100644
index 000000000..cb7ec67e1
--- /dev/null
+++ b/docs/known-issues/en/catalog-translations-not-reflecting-on-the-frontend.md
@@ -0,0 +1,54 @@
+---
+title: 'Catalog translations not reflecting on the frontend'
+id: 4c6Qzdn6NQfHhEN5U76WOi
+status: PUBLISHED
+createdAt: 2023-07-13T19:43:10.669Z
+updatedAt: 2023-07-13T19:43:11.858Z
+publishedAt: 2023-07-13T19:43:11.858Z
+firstPublishedAt: 2023-07-13T19:43:11.858Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-translations-not-reflecting-on-the-frontend
+locale: en
+kiStatus: Backlog
+internalReference: 861892
+---
+
+## Summary
+
+
+When the merchant performs an action on the Messages app in order to have some product data translated on the frontend, this action is not being actually reflected.
+
+
+##
+
+## Simulation
+
+
+
+1. Make a change on the messages app;
+2. Check on the indexInfo if the field GenerateAndSaveTranslationsDocument is set as 'false'
+3. Do not reindex the product;
+4. Check that the change did not reflected on the translated website.
+
+
+##
+
+## Workaround
+
+
+In order to force the translations to appear is necessary to reindex the product. One of the following actions should do the trick:
+
+- Change the name;
+- Change the keywords;
+- Change the Text;
+- Change the category;
+- Change the brand;
+- Change the Active flag.
+
+
+
+
+
diff --git a/docs/known-issues/en/catalogv2-user-roles-not-applying.md b/docs/known-issues/en/catalogv2-user-roles-not-applying.md
index 22c8738ac..dfcdc7105 100644
--- a/docs/known-issues/en/catalogv2-user-roles-not-applying.md
+++ b/docs/known-issues/en/catalogv2-user-roles-not-applying.md
@@ -3,8 +3,8 @@ title: 'CatalogV2 User Roles not Applying'
 id: 3cDaOuqpAJyCL5JOMzD5nL
 status: PUBLISHED
 createdAt: 2022-02-25T12:18:17.776Z
-updatedAt: 2022-11-25T21:55:04.311Z
-publishedAt: 2022-11-25T21:55:04.311Z
+updatedAt: 2024-02-16T20:26:53.078Z
+publishedAt: 2024-02-16T20:26:53.078Z
 firstPublishedAt: 2022-02-25T12:18:18.632Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalogv2-user-roles-not-applying
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 489297
 ---
 
diff --git a/docs/known-issues/en/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md b/docs/known-issues/en/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
new file mode 100644
index 000000000..51d76c932
--- /dev/null
+++ b/docs/known-issues/en/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
@@ -0,0 +1,49 @@
+---
+title: 'Categories and Brands spreadsheet mapping do not update with values from Review Skus Tab'
+id: 50p9fJ63Loml6pWqcKxm9Y
+status: PUBLISHED
+createdAt: 2024-05-03T13:51:01.537Z
+updatedAt: 2024-05-03T13:51:02.491Z
+publishedAt: 2024-05-03T13:51:02.491Z
+firstPublishedAt: 2024-05-03T13:51:02.491Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab
+locale: en
+kiStatus: Backlog
+internalReference: 1026699
+---
+
+## Summary
+
+
+When a seller sends to the marketplace a sku with a category or brand that is not yet mapped on the spreadsheet, the spreadsheet is updated with this new value on the 3rd column in order to be mapped.
+
+If the sku is sent to the Review tab, this update is not happening.
+
+
+##
+
+## Simulation
+
+
+
+1. Seller sends a sku with a not mapped brand/category to the marketplace;
+2. Sku fails some optional rule on the offer quality;
+3. Sku goes to the review tab;
+4. Check that the mapping spreadsheet is not updated.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/category-score-field-is-not-being-saved.md b/docs/known-issues/en/category-score-field-is-not-being-saved.md
index d1d7a892d..320cb2d20 100644
--- a/docs/known-issues/en/category-score-field-is-not-being-saved.md
+++ b/docs/known-issues/en/category-score-field-is-not-being-saved.md
@@ -3,8 +3,8 @@ title: 'Category Score field is not being saved'
 id: 3YxhdI31I4SY62w6oY806s
 status: PUBLISHED
 createdAt: 2018-06-01T17:24:40.180Z
-updatedAt: 2022-12-22T20:48:43.605Z
-publishedAt: 2022-12-22T20:48:43.605Z
+updatedAt: 2024-03-05T15:28:44.072Z
+publishedAt: 2024-03-05T15:28:44.072Z
 firstPublishedAt: 2018-06-01T17:39:02.287Z
 contentType: knownIssue
 productTeam: Marketing & Merchandising
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: category-score-field-is-not-being-saved
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 
 ---
 
diff --git a/docs/known-issues/en/centauro-to-implement-centauro-envios.md b/docs/known-issues/en/centauro-to-implement-centauro-envios.md
index 0e3b8fd2b..8cd7c280c 100644
--- a/docs/known-issues/en/centauro-to-implement-centauro-envios.md
+++ b/docs/known-issues/en/centauro-to-implement-centauro-envios.md
@@ -3,8 +3,8 @@ title: '[Centauro] To implement "Centauro Envios"'
 id: 1xkjyfVfT8Fs2as9mbNjj3
 status: PUBLISHED
 createdAt: 2022-11-25T21:23:23.849Z
-updatedAt: 2022-11-25T21:23:24.283Z
-publishedAt: 2022-11-25T21:23:24.283Z
+updatedAt: 2024-02-16T20:24:05.883Z
+publishedAt: 2024-02-16T20:24:05.883Z
 firstPublishedAt: 2022-11-25T21:23:24.283Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: centauro-to-implement-centauro-envios
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 618941
 ---
 
diff --git a/docs/known-issues/en/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md b/docs/known-issues/en/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
new file mode 100644
index 000000000..99bf574ae
--- /dev/null
+++ b/docs/known-issues/en/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
@@ -0,0 +1,55 @@
+---
+title: 'Change order link on checkout/orderPlaced is leading to myAccount instead of the order page'
+id: 6bP44VBdFIujX072rY6wCA
+status: PUBLISHED
+createdAt: 2023-06-15T16:13:03.752Z
+updatedAt: 2023-06-15T16:13:04.279Z
+publishedAt: 2023-06-15T16:13:04.279Z
+firstPublishedAt: 2023-06-15T16:13:04.279Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page
+locale: en
+kiStatus: Backlog
+internalReference: 844893
+---
+
+## Summary
+
+
+When the account has setup the possibility of the shopper changing the order by themselves the change order link will appear on the checkout/orderPlaced template.
+
+However, this link is not redirecting the customer to the edit page, but to the myAccount, which appears empty.
+
+
+
+##
+
+## Simulation
+
+
+Setup the Allow customers to make changes to orders flag on Admin -> settings -> order settings
+ ![](https://vtexhelp.zendesk.com/attachments/token/GqrSJ7cBhZc844LR3kXH7WMlX/?name=image.png)
+
+The shopper fulfills an order and goes to the checkout/orderPlaced
+
+Check that the link will not redirect them to the order edit area.
+
+
+##
+
+## Workaround
+
+
+
+1. The shopper has to click on My Orders in the myAccount section;
+2. Choose again the order they want to change;
+3. Click on change order.
+
+
+
+
+
+
diff --git a/docs/known-issues/en/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md b/docs/known-issues/en/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
index a29c29ba8..2312bceed 100644
--- a/docs/known-issues/en/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
+++ b/docs/known-issues/en/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
@@ -3,8 +3,8 @@ title: 'Change Order through the UI does not take into account the calculation o
 id: 3rvsDyCggYirvH7WT9rBVZ
 status: PUBLISHED
 createdAt: 2022-03-15T20:25:17.217Z
-updatedAt: 2022-11-25T22:03:48.329Z
-publishedAt: 2022-11-25T22:03:48.329Z
+updatedAt: 2024-02-16T20:23:38.705Z
+publishedAt: 2024-02-16T20:23:38.705Z
 firstPublishedAt: 2022-03-15T20:25:17.513Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 472882
 ---
 
diff --git a/docs/known-issues/en/change-order-using-api-without-email-orderchanged.md b/docs/known-issues/en/change-order-using-api-without-email-orderchanged.md
index b1b97f3f7..0e3bf5d44 100644
--- a/docs/known-issues/en/change-order-using-api-without-email-orderchanged.md
+++ b/docs/known-issues/en/change-order-using-api-without-email-orderchanged.md
@@ -3,8 +3,8 @@ title: 'Change Order using API Without e-mail order-changed'
 id: 1KMglga4xM1s7EvNO1mmua
 status: PUBLISHED
 createdAt: 2022-05-18T18:40:48.935Z
-updatedAt: 2022-11-25T22:02:43.384Z
-publishedAt: 2022-11-25T22:02:43.384Z
+updatedAt: 2024-02-16T20:27:31.478Z
+publishedAt: 2024-02-16T20:27:31.478Z
 firstPublishedAt: 2022-05-18T18:40:49.234Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: change-order-using-api-without-email-orderchanged
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 380509
 ---
 
diff --git a/docs/known-issues/en/changes-made-in-the-styles-admin-page-are-not-saved-properly.md b/docs/known-issues/en/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
new file mode 100644
index 000000000..b7ee8dab4
--- /dev/null
+++ b/docs/known-issues/en/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
@@ -0,0 +1,46 @@
+---
+title: 'Changes made in the Styles admin page are not saved properly'
+id: 4XmBeVMf0yZJElH85mSxC3
+status: PUBLISHED
+createdAt: 2024-01-25T19:13:16.165Z
+updatedAt: 2024-01-25T19:13:16.858Z
+publishedAt: 2024-01-25T19:13:16.858Z
+firstPublishedAt: 2024-01-25T19:13:16.858Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: changes-made-in-the-styles-admin-page-are-not-saved-properly
+locale: en
+kiStatus: No Fix
+internalReference: 971948
+---
+
+## Summary
+
+
+Changes that are made using the styles page of the admin UI are not currently saving properly and not always will be applied to the website.
+
+
+##
+
+## Simulation
+
+
+Try to make changes to the stylying of the website through the styles page.
+Save the changes.
+Changes won't reflect and won't be saved.
+There are no errors logged in the console and the message of "Saved sucesfully" is displayed.
+
+
+##
+
+## Workaround
+
+
+No workaround.
+
+
+
+
+
diff --git a/docs/known-issues/en/changing-accessories-is-not-triggering-indexation.md b/docs/known-issues/en/changing-accessories-is-not-triggering-indexation.md
new file mode 100644
index 000000000..d096b8644
--- /dev/null
+++ b/docs/known-issues/en/changing-accessories-is-not-triggering-indexation.md
@@ -0,0 +1,48 @@
+---
+title: 'Changing Accessories is not triggering indexation'
+id: 5asLRh4ChyuSEg1mRwWbgT
+status: PUBLISHED
+createdAt: 2024-05-22T18:30:14.578Z
+updatedAt: 2024-05-22T18:30:15.412Z
+publishedAt: 2024-05-22T18:30:15.412Z
+firstPublishedAt: 2024-05-22T18:30:15.412Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: changing-accessories-is-not-triggering-indexation
+locale: en
+kiStatus: Backlog
+internalReference: 1037800
+---
+
+## Summary
+
+
+When the merchant makes changes or adds new accessories to the sku, the indexer is not being triggered automatically.
+
+This makes the changes not reflect at the UI until another action triggers the indexer.
+
+
+##
+
+## Simulation
+
+
+Make a change or add a accessories to a sku.
+Check (after cache time) that the PDP does not update automatically.
+Make another change on the sku.
+Check (after cache time) that the PDP will reflect both changes.
+
+
+##
+
+## Workaround
+
+
+Force the indexer by making another action on the sku.
+
+
+
+
+
diff --git a/docs/known-issues/en/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md b/docs/known-issues/en/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
index d2aff9da7..5e158ad04 100644
--- a/docs/known-issues/en/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
+++ b/docs/known-issues/en/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
@@ -3,8 +3,8 @@ title: 'Changing the order of a SKU specification on the Admin could make the pa
 id: 5MuozhOKaYLGShytNH5k8Z
 status: PUBLISHED
 createdAt: 2022-08-10T13:57:53.322Z
-updatedAt: 2022-11-25T21:43:51.741Z
-publishedAt: 2022-11-25T21:43:51.741Z
+updatedAt: 2024-02-16T20:26:58.129Z
+publishedAt: 2024-02-16T20:26:58.129Z
 firstPublishedAt: 2022-08-10T13:57:53.867Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 460329
 ---
 
diff --git a/docs/known-issues/en/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md b/docs/known-issues/en/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
index a0c402929..d73c59e3a 100644
--- a/docs/known-issues/en/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
+++ b/docs/known-issues/en/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
@@ -3,8 +3,8 @@ title: 'Checkout allows proceeding to payment form without shipping address on t
 id: 3k9zxMq6Pl9WBnIz5Hy6Xf
 status: PUBLISHED
 createdAt: 2022-11-18T18:42:08.326Z
-updatedAt: 2022-11-25T23:17:39.653Z
-publishedAt: 2022-11-25T23:17:39.653Z
+updatedAt: 2024-02-16T20:27:39.990Z
+publishedAt: 2024-02-16T20:27:39.990Z
 firstPublishedAt: 2022-11-18T18:42:08.914Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 699317
 ---
 
diff --git a/docs/known-issues/en/checkout-allows-to-add-2-different-addresses-for-delivery.md b/docs/known-issues/en/checkout-allows-to-add-2-different-addresses-for-delivery.md
new file mode 100644
index 000000000..b295141c0
--- /dev/null
+++ b/docs/known-issues/en/checkout-allows-to-add-2-different-addresses-for-delivery.md
@@ -0,0 +1,46 @@
+---
+title: 'Checkout allows to add 2 different addresses for delivery'
+id: 2z7iq68qdHXAfY8RLDHXDg
+status: PUBLISHED
+createdAt: 2023-11-06T22:03:24.983Z
+updatedAt: 2023-11-07T21:28:43.164Z
+publishedAt: 2023-11-07T21:28:43.164Z
+firstPublishedAt: 2023-11-06T22:03:25.472Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-allows-to-add-2-different-addresses-for-delivery
+locale: en
+kiStatus: Backlog
+internalReference: 931225
+---
+
+## Summary
+
+
+Checkout allows adding two different addresses for delivery in the orderForm, for example, a "commercial" and a "residential" (defined by the 'addressType' field), when one of them is disposable.
+
+When both addresses are selected, there will be a message error "Unable to communicate with seller", and the shopper can't proceed to the next steps.
+
+
+##
+
+## Simulation
+
+
+
+- Send a new address via API Add shipping address and select delivery option;
+- Add a client who already has a complete profile via API Add client profile.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md b/docs/known-issues/en/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
new file mode 100644
index 000000000..0c029d43c
--- /dev/null
+++ b/docs/known-issues/en/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
@@ -0,0 +1,45 @@
+---
+title: "Checkout allows users to jump to payment step with an empty 'shippingData' when using geolocation"
+id: 7uv85LIrjoPaHxVgCAoy7I
+status: PUBLISHED
+createdAt: 2023-10-23T17:48:05.377Z
+updatedAt: 2023-10-23T17:58:49.908Z
+publishedAt: 2023-10-23T17:58:49.908Z
+firstPublishedAt: 2023-10-23T17:48:06.206Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation
+locale: en
+kiStatus: Backlog
+internalReference: 343056
+---
+
+## Summary
+
+
+When using geolocation at checkout, users are allowed to jump to the payment step with the `shippingData` incomplete.
+
+
+##
+
+## Simulation
+
+
+
+- Send the address via API with incomplete data;
+- Add any products to the cart;
+- Go to the cart and then go to checkout;
+- Add the profile information.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md b/docs/known-issues/en/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
index 4bbe092e1..181f52a26 100644
--- a/docs/known-issues/en/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
+++ b/docs/known-issues/en/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'Checkout does not correctly calculate shipping value for single item tha
 id: 4jX7JT0Wxt9S4xBe9FSwO
 status: PUBLISHED
 createdAt: 2022-02-21T19:48:04.202Z
-updatedAt: 2022-11-25T21:53:42.846Z
-publishedAt: 2022-11-25T21:53:42.846Z
+updatedAt: 2024-02-16T20:26:29.918Z
+publishedAt: 2024-02-16T20:26:29.918Z
 firstPublishedAt: 2022-02-21T19:48:04.748Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 529043
 ---
 
diff --git a/docs/known-issues/en/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md b/docs/known-issues/en/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
index 0387334ed..c787b7029 100644
--- a/docs/known-issues/en/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
+++ b/docs/known-issues/en/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
@@ -3,8 +3,8 @@ title: 'Checkout does not display shipping promotion at first instant for specif
 id: 14rQaM53csQQeA1wu5lRj8
 status: PUBLISHED
 createdAt: 2022-05-20T17:46:10.644Z
-updatedAt: 2022-11-25T21:53:02.607Z
-publishedAt: 2022-11-25T21:53:02.607Z
+updatedAt: 2024-01-15T14:35:39.473Z
+publishedAt: 2024-01-15T14:35:39.473Z
 firstPublishedAt: 2022-05-20T17:46:11.046Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 280144
 ---
 
@@ -30,12 +30,25 @@ This only occurs at the first moment, as the checkout does not recalculate promo
 In addition to this fact, the cart shipping simulation (shipping-preview) makes additional requests to the API, not only using the orderForm context. This causes him to receive the promotion, while cart totals are restricted to the context of the orderForm, which does not yet have the promotion, resulting in diverging values.
 
 
+##
 
 ## Simulation
 
 
+- have a free shipping promotion restricted to an option "A", and with the additional option above enabled
+- have a cart and zip code with two or more types of shipping, where "A" is the cheapest shipping (example, A = R$10; B = R$20)
+- enter the zip code and note that "A" (the cheapest) will be selected automatically, but will still appear as R$10
+- select "B" shipping (BRL 20) and return to "A" shipping (BRL 10)
+- at this time the value of "A" will be recalculated and will be displayed as free
+
+
+##
 
 ## Workaround
 
 
+It is not recommended to use this restriction in shipping promotions.
+
+
+
 
diff --git a/docs/known-issues/en/checkout-does-not-support-encoding-assembly-options-names.md b/docs/known-issues/en/checkout-does-not-support-encoding-assembly-options-names.md
new file mode 100644
index 000000000..b8183fc78
--- /dev/null
+++ b/docs/known-issues/en/checkout-does-not-support-encoding-assembly-options-names.md
@@ -0,0 +1,44 @@
+---
+title: 'Checkout does not support encoding Assembly Options names'
+id: 29YnOA15HDzJSRwiOLLNfR
+status: PUBLISHED
+createdAt: 2024-05-06T19:01:35.962Z
+updatedAt: 2024-05-06T19:01:36.828Z
+publishedAt: 2024-05-06T19:01:36.828Z
+firstPublishedAt: 2024-05-06T19:01:36.828Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-does-not-support-encoding-assembly-options-names
+locale: en
+kiStatus: Backlog
+internalReference: 378842
+---
+
+## Summary
+
+
+The name of assembly options are used in the API route. Thus, it is necessary to support the encoding of these names so as not to create problems in the URL with special characters, such as "/". When adding an assembly option with "/" in the cart, it simply doesn't get added and also doesn't notify the user.
+
+
+##
+
+## Simulation
+
+
+
+- Add a "/" into the assembly option name;
+- Try adding a product with the assembly option;
+- The item will be added to the cart without the assembly option.
+
+
+##
+
+## Workaround
+
+
+Remove "/" from the assembly option name.
+
+
+
diff --git a/docs/known-issues/en/checkout-incorrectly-sending-item-details-to-transaction.md b/docs/known-issues/en/checkout-incorrectly-sending-item-details-to-transaction.md
index c562ec23f..1e773c18b 100644
--- a/docs/known-issues/en/checkout-incorrectly-sending-item-details-to-transaction.md
+++ b/docs/known-issues/en/checkout-incorrectly-sending-item-details-to-transaction.md
@@ -3,8 +3,8 @@ title: 'Checkout incorrectly sending item details to transaction'
 id: YxjZNKuIxkKQioS7lkmu8
 status: PUBLISHED
 createdAt: 2022-03-04T15:08:55.326Z
-updatedAt: 2022-11-25T21:52:34.380Z
-publishedAt: 2022-11-25T21:52:34.380Z
+updatedAt: 2024-02-16T20:28:39.301Z
+publishedAt: 2024-02-16T20:28:39.301Z
 firstPublishedAt: 2022-03-04T15:08:55.710Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-incorrectly-sending-item-details-to-transaction
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 535859
 ---
 
diff --git a/docs/known-issues/en/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md b/docs/known-issues/en/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
new file mode 100644
index 000000000..cd6236f10
--- /dev/null
+++ b/docs/known-issues/en/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
@@ -0,0 +1,44 @@
+---
+title: "Checkout pipeline doesn't update taxes considering the correct seller when merging cart information"
+id: 4HDGps2Ez5kWKuW1UNX1JQ
+status: PUBLISHED
+createdAt: 2024-07-03T20:21:23.533Z
+updatedAt: 2024-07-03T20:21:24.413Z
+publishedAt: 2024-07-03T20:21:24.413Z
+firstPublishedAt: 2024-07-03T20:21:24.413Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information
+locale: en
+kiStatus: Backlog
+internalReference: 759842
+---
+
+## Summary
+
+
+When there are 2 sellers in the "SellerElection" method, one of them is selected as having the cheapest price for delivery, and the other one the cheapest price for pickup-in-point, the cart information merge doesn't update taxes when selecting pickup-in-point, causing an error to finish the purchase
+
+
+##
+
+## Simulation
+
+
+
+- Have two sellers configured: 1 is the cheapest when delivery and the other one when pickup-in-point
+- Configure taxes _only_ for the seller that will fulfill pickup-in-point or different taxes between them
+- Perform a Checkout Simulation and you will see there will be no taxes in "priceTags" and it won't finish the purchase
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
new file mode 100644
index 000000000..b277f0e5e
--- /dev/null
+++ b/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -0,0 +1,44 @@
+---
+title: 'Checkout Simulation returns value 0 in "slas.tax" field for Shipping Percentage taxes'
+id: 54Mtsj8EKuo0SaQCoWyYzj
+status: PUBLISHED
+createdAt: 2024-04-05T18:55:32.183Z
+updatedAt: 2024-04-05T18:55:33.336Z
+publishedAt: 2024-04-05T18:55:33.336Z
+firstPublishedAt: 2024-04-05T18:55:33.336Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes
+locale: en
+kiStatus: Backlog
+internalReference: 1012724
+---
+
+## Summary
+
+
+Shipping Percentage taxes are not returned in the `logisticsInfo.slas.tax` field when performing a checkout simulation even though individual taxes information are available in the `items.priceTags` field.
+
+
+##
+
+## Simulation
+
+
+
+- Configure a Shipping Percentage Tax
+- Make a cart simulation request with selected SLA
+- The `tax` field returns value `0`
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md b/docs/known-issues/en/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
new file mode 100644
index 000000000..a8abadf18
--- /dev/null
+++ b/docs/known-issues/en/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
@@ -0,0 +1,48 @@
+---
+title: 'Checkout simulation with a great quantity of the same sku receives a Logistics timeout'
+id: 753MDZbcyN9BTHAaSTpOlY
+status: PUBLISHED
+createdAt: 2024-06-18T12:42:44.404Z
+updatedAt: 2024-06-18T12:42:45.419Z
+publishedAt: 2024-06-18T12:42:45.419Z
+firstPublishedAt: 2024-06-18T12:42:45.419Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout
+locale: en
+kiStatus: No Fix
+internalReference: 330775
+---
+
+## Summary
+
+
+We have an error in the Logistics service when trying to simulate a purchase with thousands of units of the same SKU. That error happens because the request to split the package takes too long.
+
+The error detail in the API is: "The operation was canceled."
+
+
+##
+
+## Simulation
+
+
+
+1. Try to make a **Checkout Simulation** or a simulation in the **Shopping Cart** with thousands of units of the same SKU (like 50k)
+2. Review the details in the response of the API, and you probably see an error when processing that request (**timeout**)
+
+
+##
+
+## Workaround
+
+
+We recommend increasing the carrier's package limits to accommodate the units in a single package. It would provide a faster request and would not return a timeout.
+
+
+
+
+
+
diff --git a/docs/known-issues/en/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md b/docs/known-issues/en/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
new file mode 100644
index 000000000..8804118bf
--- /dev/null
+++ b/docs/known-issues/en/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
@@ -0,0 +1,47 @@
+---
+title: 'Checkout UI goes to Payment with an incomplete invoice address for shoppers with complete profile'
+id: NmN6oNKp1isyxssTE5jPR
+status: PUBLISHED
+createdAt: 2023-11-27T17:40:11.335Z
+updatedAt: 2023-12-12T15:46:39.789Z
+publishedAt: 2023-12-12T15:46:39.789Z
+firstPublishedAt: 2023-11-27T17:40:12.008Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile
+locale: en
+kiStatus: Fixed
+internalReference: 937615
+---
+
+## Summary
+
+
+When a shopper has a complete profile and the store is configured to use an invoice address for pick-up, UI will move forward to Payment with an incomplete invoice address.
+
+
+##
+
+## Simulation
+
+
+
+- Configure the invoice address for pick-up;
+ ![](https://vtexhelp.zendesk.com/attachments/token/1zJ19Lq9oJ5CHdkaHUfw4SAka/?name=image.png)
+
+- After adding products to the cart, use an email with a complete profile;
+- UI will move forward to Payment even with an incomplete invoice address in the Profile System.
+
+
+##
+
+## Workaround
+
+
+Update the invoice address via Master Data.
+
+
+
+
diff --git a/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
new file mode 100644
index 000000000..06a54b9d8
--- /dev/null
+++ b/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -0,0 +1,49 @@
+---
+title: 'Checkout UI is not automatically using "lean shipping" for items with no common shipping methods'
+id: 2LXp8VCAay7Ic9MBfbtirT
+status: PUBLISHED
+createdAt: 2024-04-02T15:27:23.003Z
+updatedAt: 2024-04-02T15:27:24.004Z
+publishedAt: 2024-04-02T15:27:24.004Z
+firstPublishedAt: 2024-04-02T15:27:24.004Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods
+locale: en
+kiStatus: Backlog
+internalReference: 329846
+---
+
+## Summary
+
+
+The Checkout UI settings allow you to disable lean shipping (delivery mode optimizations), but this is only possible if all items in the cart have the same delivery methods in common. Otherwise, lean shipping must appear forcefully in the cart even with the option turned off.
+However, in some scenarios, the behavior reported above does not happen, and all available delivery methods are presented individually to the buyer.
+
+As a result, as there is no way to select a different delivery method for each item, no delivery displayed corresponds to a single delivery option for the entire cart, with nonsense options and packages being presented.
+
+
+##
+
+## Simulation
+
+
+
+- Deactivate the **Optimized Shipping Options****;**
+- Assemble a cart where not all items have the same delivery method;
+- It is also necessary that the store has "allowMultipleDeliveries" enabled;
+- The reported scenario will show the options openly instead of lean shipping.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md b/docs/known-issues/en/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
index 5973ba5fa..07a9925a0 100644
--- a/docs/known-issues/en/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
+++ b/docs/known-issues/en/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
@@ -1,10 +1,10 @@
 ---
 title: 'Checkout UI loops when not receiving correct SLA values from logistics system'
 id: 4tACwwmorLZ7NAt3zWldWL
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-04T19:28:24.852Z
-updatedAt: 2022-06-27T12:27:43.525Z
-publishedAt: 2022-06-26T16:28:26.833Z
+updatedAt: 2024-02-16T20:28:53.645Z
+publishedAt: 2024-02-16T20:28:53.645Z
 firstPublishedAt: 2022-05-04T19:28:25.322Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 485016
 ---
 
diff --git a/docs/known-issues/en/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md b/docs/known-issues/en/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
new file mode 100644
index 000000000..0a76de615
--- /dev/null
+++ b/docs/known-issues/en/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
@@ -0,0 +1,47 @@
+---
+title: 'Checkout UI sends hyphen in the postal code to orderForm'
+id: 3cqrBqq5x8nixjAFt8BxCx
+status: PUBLISHED
+createdAt: 2024-01-16T12:37:56.497Z
+updatedAt: 2024-01-16T12:37:57.041Z
+publishedAt: 2024-01-16T12:37:57.041Z
+firstPublishedAt: 2024-01-16T12:37:57.041Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-ui-sends-hyphen-in-the-postal-code-to-orderform
+locale: en
+kiStatus: Backlog
+internalReference: 937692
+---
+
+## Summary
+
+
+Checkout UI sends a hyphen for the postal code to orderForm, causing issues calculating SLAs when a country has 7 digits + the hyphen. This happens because the Logistics module considers the hyphen as a digit and depending on how the shipping rates were registered in the shipping policy.
+
+Portugal and Japan are the only ones in this scenario.
+
+
+##
+
+## Simulation
+
+
+
+- Have an account for Portugal or Japan;
+- After adding products to the cart, type the postal code;
+- The product may be shown as unavailable.
+
+
+##
+
+## Workaround
+
+
+
+- Review the shipping rates to include a broader range.
+
+
+
diff --git a/docs/known-issues/en/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md b/docs/known-issues/en/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
new file mode 100644
index 000000000..7a6c56c6d
--- /dev/null
+++ b/docs/known-issues/en/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
@@ -0,0 +1,44 @@
+---
+title: 'Checkout UI shows free shipping when the user switches the delivery options'
+id: 5ibXQuVSU5vLfihL8uImyX
+status: PUBLISHED
+createdAt: 2023-09-27T20:40:02.973Z
+updatedAt: 2023-10-02T19:35:11.231Z
+publishedAt: 2023-10-02T19:35:11.231Z
+firstPublishedAt: 2023-09-27T20:40:03.494Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options
+locale: en
+kiStatus: Backlog
+internalReference: 897109
+---
+
+## Summary
+
+
+The checkout UI shows free delivery when the user switches the delivery method from normal dispatch to scheduled delivery. The problem only occurs in the delivery box and when the account has the LeanShipping feature configured. although the UI shows free shipping, the purchase total values are correctly displayed and charged.
+
+
+##
+
+## Simulation
+
+
+
+1. Go to the checkout page by purchasing a random item
+2. in the shipping section, select schedule delivery and then select normal dispatch again and the free delivery price will appear on the delivery section
+
+
+##
+
+## Workaround
+
+
+There's no workaround.
+
+
+
+
diff --git a/docs/known-issues/en/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md b/docs/known-issues/en/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
index 7367270bd..669f47799 100644
--- a/docs/known-issues/en/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
+++ b/docs/known-issues/en/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
@@ -3,8 +3,8 @@ title: 'City and state are not sent to PayPalPlus when there is only pickup addr
 id: 5ScWTMLqT9oBMUYFc6WGo2
 status: PUBLISHED
 createdAt: 2023-06-01T13:47:08.477Z
-updatedAt: 2023-06-01T13:47:09.590Z
-publishedAt: 2023-06-01T13:47:09.590Z
+updatedAt: 2023-09-12T13:10:53.169Z
+publishedAt: 2023-09-12T13:10:53.169Z
 firstPublishedAt: 2023-06-01T13:47:09.590Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 836025
 ---
 
@@ -43,3 +43,4 @@ Select "Delivery", add the postal code, and the change to "Pick up in store".
 
 
 
+
diff --git a/docs/known-issues/en/clear-filter-button-doesnt-handle-multiple-filters-correctly.md b/docs/known-issues/en/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
new file mode 100644
index 000000000..7e96bc9a3
--- /dev/null
+++ b/docs/known-issues/en/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
@@ -0,0 +1,39 @@
+---
+title: "Clear filter button doesn't handle multiple filters correctly"
+id: TVLYkkJXq5bxmFvHZyRS6
+status: PUBLISHED
+createdAt: 2024-01-03T22:35:40.705Z
+updatedAt: 2024-01-03T22:35:41.328Z
+publishedAt: 2024-01-03T22:35:41.328Z
+firstPublishedAt: 2024-01-03T22:35:41.328Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: clear-filter-button-doesnt-handle-multiple-filters-correctly
+locale: en
+kiStatus: Backlog
+internalReference: 960905
+---
+
+## Summary
+
+
+In some scenarios, like landing pages and collection pages, additional filters aren't correctly cleared after clicking the "clear filter" button. The URL may go to invalid or wrong filters and the product listing may get empty or with unexpected products.
+
+
+##
+
+## Simulation
+
+
+In a store theme with the "clear filters" button enabled, try it on a landing page or collection page after applying additional filters.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md b/docs/known-issues/en/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
new file mode 100644
index 000000000..c813b23bb
--- /dev/null
+++ b/docs/known-issues/en/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
@@ -0,0 +1,50 @@
+---
+title: 'Client document value will not update correctly sometimes in Global Checkout setting'
+id: 3846jcrfuMvULJt5dZkJxf
+status: PUBLISHED
+createdAt: 2023-07-17T20:50:26.133Z
+updatedAt: 2023-07-17T20:50:27.048Z
+publishedAt: 2023-07-17T20:50:27.048Z
+firstPublishedAt: 2023-07-17T20:50:27.048Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting
+locale: en
+kiStatus: Backlog
+internalReference: 863726
+---
+
+## Summary
+
+
+When using Global Checkout, and changing from using the default document and an self-identified document and value informed for the document number field will not "take it" correctly.
+
+Attached is a video showing the behavior.
+
+
+
+
+##
+
+## Simulation
+
+
+Apply the customizations to enable the global checkout.
+Proceed to add a foreign document and save the profile changes.
+Edit the profile, change to regular document input and introduce a different value, then save the changes
+Open the profile again, sometimes the value shown was replaced with the foreign value
+
+
+##
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/en/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md b/docs/known-issues/en/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
new file mode 100644
index 000000000..9f8eedad1
--- /dev/null
+++ b/docs/known-issues/en/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
@@ -0,0 +1,44 @@
+---
+title: 'clientProfileData gets empty if request Add client profile is performed twice'
+id: 1TG7cnnMyWHNKrCjoouKoC
+status: PUBLISHED
+createdAt: 2023-10-02T15:51:35.989Z
+updatedAt: 2023-10-02T15:51:36.771Z
+publishedAt: 2023-10-02T15:51:36.771Z
+firstPublishedAt: 2023-10-02T15:51:36.771Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice
+locale: en
+kiStatus: Backlog
+internalReference: 911203
+---
+
+## Summary
+
+
+When sending the request Add client profile twice and the email has a complete profile, "clientProfileData" gets empty, showing only the email.
+
+
+##
+
+## Simulation
+
+
+
+- Add client profile via API;
+- Resend the same request authenticated, the "clientProfileData" will have only the email.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md b/docs/known-issues/en/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
index 8e5433a4f..2377ff434 100644
--- a/docs/known-issues/en/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
+++ b/docs/known-issues/en/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
@@ -3,8 +3,8 @@ title: 'CMS allows the creation but not the editing of folders with the same nam
 id: q2Fvxfwv5MjAcqxb81avH
 status: PUBLISHED
 createdAt: 2022-04-26T14:09:30.508Z
-updatedAt: 2022-11-25T22:10:43.268Z
-publishedAt: 2022-11-25T22:10:43.268Z
+updatedAt: 2024-02-16T20:26:06.081Z
+publishedAt: 2024-02-16T20:26:06.081Z
 firstPublishedAt: 2022-04-26T14:09:31.061Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 566791
 ---
 
diff --git a/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md b/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md
index 38c7024e5..54395bbae 100644
--- a/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md
+++ b/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md
@@ -20,7 +20,7 @@ internalReference:
 
 When accessing the CMS through the new administrative environment (My VTEX - `{AccountName}.myvtex.com/admin`), an error page is displayed, and the CMS can not be accessed.
 
-![4JSc1cw](https://images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
+![4JSc1cw](//images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/cms-legacy-collections-timeout.md b/docs/known-issues/en/cms-legacy-collections-timeout.md
index e556bfe42..07184c0be 100644
--- a/docs/known-issues/en/cms-legacy-collections-timeout.md
+++ b/docs/known-issues/en/cms-legacy-collections-timeout.md
@@ -3,8 +3,8 @@ title: 'CMS Legacy Collections Timeout'
 id: 3TgWP83kn8G8NClnUHmaoS
 status: PUBLISHED
 createdAt: 2022-02-25T12:33:00.051Z
-updatedAt: 2023-05-19T18:23:32.371Z
-publishedAt: 2023-05-19T18:23:32.371Z
+updatedAt: 2023-06-20T13:24:40.031Z
+publishedAt: 2023-06-20T13:24:40.031Z
 firstPublishedAt: 2022-02-25T12:33:00.399Z
 contentType: knownIssue
 productTeam: Catalog
@@ -18,34 +18,24 @@ internalReference: 434026
 
 ## Summary
 
-
 Often, when attempting to save data for a collection group using the legacy collections application, under the path /admin/a and attempting to Save Group, the user will, in cases of large catalogs (large amount of categories, brands, products), face a timeout error message and won't be able to save their changes.
 
 `{account}.myvtex.com/admin/a/`
 
  ![](https://vtexhelp.zendesk.com/attachments/token/pBcpo1sWfBMio0mpL5iMc4Iek/?name=inline-1265713773.png)
 
-
-##
-
 ## Simulation
 
 
-1) Go to the CMS UI application using a store that has a large catalog base, for instance, >10000 products.
-2) Go to "Product Clusters (Collections) and select "_new group_"
-3)  Create a group and then select a few checkboxes in the form
-4) Attempt to save these changes
-5) If the request takes longer than 50 seconds to save, which is often the case in accounts with a large amount of data, the request will be stopped by and the data will not be saved.
-
-
-##
+1. Go to the CMS UI application using a store that has a large catalog base, for instance, >10000 products.
+2. Go to "Product Clusters (Collections) and select "_new group_"
+3. Create a group and then select a few checkboxes in the form
+4. Attempt to save these changes
+5. If the request takes longer than 50 seconds to save, which is often the case in accounts with a large amount of data, the request will be stopped by and the data will not be saved.
 
 ## Workaround
 
 
-Either using the new collections admin OR Using our collections API endpoints: https://developers.vtex.com/vtex-rest-api/reference/collection-cms
-
-
-
+Either using the new collections Admin OR using our [Collections API endpoints](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection).
 
 
diff --git a/docs/known-issues/en/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md b/docs/known-issues/en/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
index d309af635..007a0aa7d 100644
--- a/docs/known-issues/en/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
+++ b/docs/known-issues/en/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
@@ -3,8 +3,8 @@ title: 'CMS Settings does not allow removing value from the Unit of Mass field'
 id: QVmSN1VuGQUiklZDkarEI
 status: PUBLISHED
 createdAt: 2022-03-11T13:49:28.490Z
-updatedAt: 2022-11-25T22:11:28.148Z
-publishedAt: 2022-11-25T22:11:28.148Z
+updatedAt: 2024-02-16T20:28:41.042Z
+publishedAt: 2024-02-16T20:28:41.042Z
 firstPublishedAt: 2022-03-11T13:49:28.850Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 540756
 ---
 
diff --git a/docs/known-issues/en/cms-settings-role-not-working-as-expected.md b/docs/known-issues/en/cms-settings-role-not-working-as-expected.md
new file mode 100644
index 000000000..eab2240ca
--- /dev/null
+++ b/docs/known-issues/en/cms-settings-role-not-working-as-expected.md
@@ -0,0 +1,54 @@
+---
+title: 'CMS Settings Role not working as expected'
+id: 1xAUvtkD2gbvc3yaoYXT2d
+status: PUBLISHED
+createdAt: 2023-06-19T12:31:33.137Z
+updatedAt: 2023-06-19T12:31:33.699Z
+publishedAt: 2023-06-19T12:31:33.699Z
+firstPublishedAt: 2023-06-19T12:31:33.699Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: cms-settings-role-not-working-as-expected
+locale: en
+kiStatus: Backlog
+internalReference: 538706
+---
+
+## Summary
+
+
+CMS Settings Role not working as expected. Sometimes the user can't access the CMS even after is added to the role.
+Another unexpected behavior is that other modules continue to be available for the CMS role even without the necessary permissions.
+
+
+##
+
+## Simulation
+
+
+
+- Create a role at the License Manager Roles application giving only access to:
+  - CMS menu on the top-bar;
+  - CMS Settings.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/fbpObVoVdnEYGeYjd3GDh9Qqf/?name=image.png)
+
+
+- Associate this role to a user;
+- Log in with this user and try to access the CMS settings menu, you will not be able.
+- Check that other modules continue to be available.
+
+
+##
+
+## Workaround
+
+
+To access the CMS Menu, the user should be an Admin Super.
+
+
+
+
+
diff --git a/docs/known-issues/en/collapsible-menu-issues-rendering-all-the-items.md b/docs/known-issues/en/collapsible-menu-issues-rendering-all-the-items.md
index 473b40ba4..0fbe56347 100644
--- a/docs/known-issues/en/collapsible-menu-issues-rendering-all-the-items.md
+++ b/docs/known-issues/en/collapsible-menu-issues-rendering-all-the-items.md
@@ -3,8 +3,8 @@ title: 'Collapsible Menu issues rendering all the items'
 id: 1iOlmwj8DvaxCQCmvyHQww
 status: PUBLISHED
 createdAt: 2022-05-23T19:39:49.204Z
-updatedAt: 2022-11-25T22:13:59.079Z
-publishedAt: 2022-11-25T22:13:59.079Z
+updatedAt: 2024-02-16T20:24:35.010Z
+publishedAt: 2024-02-16T20:24:35.010Z
 firstPublishedAt: 2022-05-23T19:39:49.609Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: collapsible-menu-issues-rendering-all-the-items
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 542091
 ---
 
diff --git a/docs/known-issues/en/collections-does-not-allow-more-than-1000-skus-per-upload.md b/docs/known-issues/en/collections-does-not-allow-more-than-1000-skus-per-upload.md
index 68529d71c..c497befcd 100644
--- a/docs/known-issues/en/collections-does-not-allow-more-than-1000-skus-per-upload.md
+++ b/docs/known-issues/en/collections-does-not-allow-more-than-1000-skus-per-upload.md
@@ -3,8 +3,8 @@ title: 'Collections does not Allow more than 1000 SKUs per Upload'
 id: 4XC2ZLCsBkQhexRB4YrNMn
 status: PUBLISHED
 createdAt: 2023-04-19T13:53:02.339Z
-updatedAt: 2023-04-19T13:53:02.926Z
-publishedAt: 2023-04-19T13:53:02.926Z
+updatedAt: 2023-10-10T13:31:27.610Z
+publishedAt: 2023-10-10T13:31:27.610Z
 firstPublishedAt: 2023-04-19T13:53:02.926Z
 contentType: knownIssue
 productTeam: Catalog
diff --git a/docs/known-issues/en/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md b/docs/known-issues/en/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
new file mode 100644
index 000000000..43500b739
--- /dev/null
+++ b/docs/known-issues/en/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
@@ -0,0 +1,47 @@
+---
+title: "Collections doesn't work in custom search results pages in B2B Suite"
+id: 2O2UmKrMJHimDunDRbLBe
+status: PUBLISHED
+createdAt: 2024-06-03T22:13:10.775Z
+updatedAt: 2024-06-21T14:57:27.454Z
+publishedAt: 2024-06-21T14:57:27.454Z
+firstPublishedAt: 2024-06-03T22:13:11.591Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite
+locale: en
+kiStatus: Backlog
+internalReference: 1043470
+---
+
+## Summary
+
+
+Custom search results pages set up with collection id don't work when a different product Collections are assigned to an organization.
+
+The expected behavior when using Collections is to define the assortment of products the organization users will see in the storefront, but since B2B Organizations also use `productClusterId` in the search, when accessing custom search results pages set up with a different `productClusterId`, the search results show products from both collections.
+
+
+##
+
+## Simulation
+
+
+
+- Set up a product Collections to an organization;
+- Create a custom search results page with a different collection;
+- Log in and access the custom search result page; products from both collections are shown.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/collections-dont-open-on-subaccounts.md b/docs/known-issues/en/collections-dont-open-on-subaccounts.md
new file mode 100644
index 000000000..bda8333d5
--- /dev/null
+++ b/docs/known-issues/en/collections-dont-open-on-subaccounts.md
@@ -0,0 +1,44 @@
+---
+title: "Collections don't open on subaccounts"
+id: Ly7eHGXdzg0aJLYF2c4eZ
+status: PUBLISHED
+createdAt: 2024-07-31T18:50:48.046Z
+updatedAt: 2024-07-31T18:50:49.007Z
+publishedAt: 2024-07-31T18:50:49.007Z
+firstPublishedAt: 2024-07-31T18:50:49.007Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: collections-dont-open-on-subaccounts
+locale: en
+kiStatus: Backlog
+internalReference: 649948
+---
+
+## Summary
+
+
+When trying to open a collection on the new collections module of a subaccount an error "Sorry, an unknown error occurred." is returned.
+
+
+##
+
+## Simulation
+
+
+
+1. Enter a subaccount;
+2. Go to the new collections module;
+3. Try to open any collection;
+4. Check that an error has ocurred.
+
+
+##
+
+## Workaround
+
+
+
+Since the catalog is shared between accounts, open the collection on the main account OR use the old collections module on the CMS.
+
diff --git a/docs/known-issues/en/collections-export-only-shows-1st-sku-of-inactive-product.md b/docs/known-issues/en/collections-export-only-shows-1st-sku-of-inactive-product.md
new file mode 100644
index 000000000..8cfd84111
--- /dev/null
+++ b/docs/known-issues/en/collections-export-only-shows-1st-sku-of-inactive-product.md
@@ -0,0 +1,46 @@
+---
+title: 'Collections Export only shows 1st SKU of inactive product'
+id: 7FegROKSwxpadN5NYVFR8M
+status: PUBLISHED
+createdAt: 2024-05-28T19:56:23.549Z
+updatedAt: 2024-05-28T19:56:24.303Z
+publishedAt: 2024-05-28T19:56:24.303Z
+firstPublishedAt: 2024-05-28T19:56:24.303Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: collections-export-only-shows-1st-sku-of-inactive-product
+locale: en
+kiStatus: Backlog
+internalReference: 1040753
+---
+
+## Summary
+
+
+When using the collections module and attempting to export registers, if the listed product in a given collection has all of its skus set as inactive, the exported sheet will only list 1 of the product's skus, instead of all.
+
+
+##
+
+## Simulation
+
+
+1 - Get a product that has multiple skus and set all of them to inactive.
+2 - Insert them into a catalog collection /admin/collections
+3 - use the export feature
+4 - only the uppermost SKU of the product will be listed in the sheet, instead of all
+
+
+##
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index f5d13a1c8..62ad4114a 100644
--- a/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -3,8 +3,8 @@ title: 'Collections Field always appearing as "Equal To" on the Campaign Audienc
 id: 2NPEh7LZkrpO0gf802I7HZ
 status: PUBLISHED
 createdAt: 2022-11-11T21:18:53.386Z
-updatedAt: 2022-11-25T22:11:31.863Z
-publishedAt: 2022-11-25T22:11:31.863Z
+updatedAt: 2024-02-16T20:27:37.566Z
+publishedAt: 2024-02-16T20:27:37.566Z
 firstPublishedAt: 2022-11-11T21:18:54.385Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 697168
 ---
 
diff --git a/docs/known-issues/en/collections-named-with-special-characters-cannot-be-exported.md b/docs/known-issues/en/collections-named-with-special-characters-cannot-be-exported.md
new file mode 100644
index 000000000..6f5e346ca
--- /dev/null
+++ b/docs/known-issues/en/collections-named-with-special-characters-cannot-be-exported.md
@@ -0,0 +1,45 @@
+---
+title: 'Collections named with special characters cannot be exported'
+id: 516zuwek2Gfwd0U99si2XU
+status: PUBLISHED
+createdAt: 2023-08-22T12:46:46.230Z
+updatedAt: 2023-12-12T14:21:31.164Z
+publishedAt: 2023-12-12T14:21:31.164Z
+firstPublishedAt: 2023-08-22T12:46:46.895Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: collections-named-with-special-characters-cannot-be-exported
+locale: en
+kiStatus: Backlog
+internalReference: 683343
+---
+
+## Summary
+
+
+It is expected that a collection can be exported on the admin. However, collections with names that contain symbols such as `$` , `+`  or `,` cannot be exported.
+
+
+##
+
+## Simulation
+
+
+
+- Create a collection with `$` , `+`  or `,`  on the name
+- Try to export the collection
+- An error will be displayed on the admin
+
+
+##
+
+## Workaround
+
+
+Remove the character
+
+
+
+
diff --git a/docs/known-issues/en/collections-page-in-organization-details-shows-only-20-collections.md b/docs/known-issues/en/collections-page-in-organization-details-shows-only-20-collections.md
new file mode 100644
index 000000000..a52f05599
--- /dev/null
+++ b/docs/known-issues/en/collections-page-in-organization-details-shows-only-20-collections.md
@@ -0,0 +1,52 @@
+---
+title: 'Collections page in Organization Details shows only 20 collections'
+id: 1NL46GlhANQoa6IzGSSwdS
+status: PUBLISHED
+createdAt: 2023-08-31T20:02:37.675Z
+updatedAt: 2024-04-23T21:35:34.440Z
+publishedAt: 2024-04-23T21:35:34.440Z
+firstPublishedAt: 2023-08-31T20:02:38.351Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: collections-page-in-organization-details-shows-only-20-collections
+locale: en
+kiStatus: Fixed
+internalReference: 891511
+---
+
+## Summary
+
+
+The Collections page in Organization Details shows only 20 collections even after changing the row quantity in the bottom of the page.
+
+
+##
+
+## Simulation
+
+
+
+- Make sure you have more than 20 active collections;
+- In the admin, go to the B2B Organizations page, select an organization;
+- Go to the Collections tab; you will see only 20 collections available.
+
+
+##
+
+## Workaround
+
+
+If the desired collection does not appear in the Collections tab, assign it using GraphQL IDE:
+
+- Access GraphQL IDE;
+- Select the app `vtex.b2b-organizations-graphql`;
+- Use the mutation below and add the values for `id`, `name`, `collections.id` and `collections.name`
+
+    mutation { updateOrganization ( id: "" name: "" status: "active" collections: [{ id: "" name: "" }] ){ status message }}
+
+
+
+
+
diff --git a/docs/known-issues/en/collections-trigger-not-working-as-expected-on-progressive-discounts.md b/docs/known-issues/en/collections-trigger-not-working-as-expected-on-progressive-discounts.md
new file mode 100644
index 000000000..724943ac3
--- /dev/null
+++ b/docs/known-issues/en/collections-trigger-not-working-as-expected-on-progressive-discounts.md
@@ -0,0 +1,48 @@
+---
+title: 'Collections trigger not working as expected on Progressive Discounts'
+id: 78b9yQnTm1bxgOM2cfMlql
+status: PUBLISHED
+createdAt: 2023-11-06T16:42:53.081Z
+updatedAt: 2023-11-06T16:42:53.722Z
+publishedAt: 2023-11-06T16:42:53.722Z
+firstPublishedAt: 2023-11-06T16:42:53.722Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: collections-trigger-not-working-as-expected-on-progressive-discounts
+locale: en
+kiStatus: Backlog
+internalReference: 930849
+---
+
+## Summary
+
+
+When creating a progressive discount promotion the client can set the trigger by collection, by a SKU list or by both.
+
+However, when both are setup on the promotion, the condition that should be either the collection or either the sku list triggers the promotion is actually behaving like only the SKU list is the trigger.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a progressive discount promotion;
+2. On the promo triggers, select a collection and a SKU list with a sku that doesn't belong to the collection;
+3. Check on the cart that the promotion is only active when the sku that belongs to the sku list is present.
+
+
+##
+
+## Workaround
+
+
+To enable both triggers at the same time there is no workaround.
+
+
+
+
+
diff --git a/docs/known-issues/en/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md b/docs/known-issues/en/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
index 7e289902b..614f47298 100644
--- a/docs/known-issues/en/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
+++ b/docs/known-issues/en/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
@@ -3,8 +3,8 @@ title: 'Complete orders with error in creation due to failure in gatewaycallbak'
 id: 2qVa686QBsvkgXY8wwmc8Y
 status: PUBLISHED
 createdAt: 2022-05-04T19:28:00.775Z
-updatedAt: 2022-11-25T21:52:28.991Z
-publishedAt: 2022-11-25T21:52:28.991Z
+updatedAt: 2024-04-04T16:46:47.602Z
+publishedAt: 2024-04-04T16:46:47.602Z
 firstPublishedAt: 2022-05-04T19:28:01.142Z
 contentType: knownIssue
 productTeam: Checkout
@@ -24,16 +24,27 @@ We received some inquiries about orders that were stuck in payment approved stat
 Based on the analysis of the cases, we understand that a possible occurrence of this occurrence was;
 
 The marketplace order was created incomplete, the marketplace order receives the gatewaycallback call and, at this time, a failure occurs, and this causes an order cancellation process to start, but the marketppace order receives a second call from gatewaycallback that causes the order to be authorized and complete, thus preventing the transaction from being canceled, and this scenario generates a complete order (marketplace / checkout), but with a creation error and the fullfiment order canceled, which could be avoided implementing a validation in gatewaycallback to not proceed with incomplete requests.
+In some cases, the Seller order may not be cancelled.
 
 
+##
 
+## Simulation
 
 
-## Simulation
+
+We cannot simulate due to the complexity of the flow, the analysis must be done considering the data reported here.
+
 
 
+##
 
 ## Workaround
 
 
+In cases where the Seller's order is not canceled, you must cancel the order manually, or wait for the 30-day time limit.
+
+
+
+
 
diff --git a/docs/known-issues/en/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md b/docs/known-issues/en/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
index 1b124c206..c8a5fe13a 100644
--- a/docs/known-issues/en/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
+++ b/docs/known-issues/en/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
@@ -3,8 +3,8 @@ title: "Component drawer doesn't work when implemented in product-summary for iO
 id: 75145kfQE8swAef57Yr4Aj
 status: PUBLISHED
 createdAt: 2023-05-29T13:22:57.856Z
-updatedAt: 2023-05-29T13:22:58.422Z
-publishedAt: 2023-05-29T13:22:58.422Z
+updatedAt: 2024-02-19T18:51:53.024Z
+publishedAt: 2024-02-19T18:51:53.024Z
 firstPublishedAt: 2023-05-29T13:22:58.422Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/en/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md b/docs/known-issues/en/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
index e82ff14fd..7b5957c77 100644
--- a/docs/known-issues/en/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
+++ b/docs/known-issues/en/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
@@ -3,8 +3,8 @@ title: 'Component Seller Selector may present inconsistency in delivery/shipping
 id: 2agLvjXgT76ngdu3YsA6uh
 status: PUBLISHED
 createdAt: 2022-09-14T22:26:22.177Z
-updatedAt: 2022-11-25T22:13:07.124Z
-publishedAt: 2022-11-25T22:13:07.124Z
+updatedAt: 2024-02-16T20:28:08.976Z
+publishedAt: 2024-02-16T20:28:08.976Z
 firstPublishedAt: 2022-09-14T22:26:22.762Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 658452
 ---
 
diff --git a/docs/known-issues/en/components-in-a-kit-with-the-same-price.md b/docs/known-issues/en/components-in-a-kit-with-the-same-price.md
new file mode 100644
index 000000000..72624c263
--- /dev/null
+++ b/docs/known-issues/en/components-in-a-kit-with-the-same-price.md
@@ -0,0 +1,46 @@
+---
+title: 'Components in a kit with the same price'
+id: 6TIDKJ6nEGUu3E5bzAea65
+status: PUBLISHED
+createdAt: 2024-02-26T19:53:43.754Z
+updatedAt: 2024-02-26T19:53:45.011Z
+publishedAt: 2024-02-26T19:53:45.011Z
+firstPublishedAt: 2024-02-26T19:53:45.011Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: components-in-a-kit-with-the-same-price
+locale: en
+kiStatus: Backlog
+internalReference: 989371
+---
+
+## Summary
+
+
+Components in a kit have the same price when a gift promotion is configured, and a regular seller fulfills it.
+
+
+##
+
+## Simulation
+
+
+
+- Register a kit;
+- Set a gift promotion;
+- Add an item to the cart using a regular seller;
+- Place the order; the components' price will be the same.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/confirmed-order-email-not-being-sent.md b/docs/known-issues/en/confirmed-order-email-not-being-sent.md
index 1a7e54861..d277d87aa 100644
--- a/docs/known-issues/en/confirmed-order-email-not-being-sent.md
+++ b/docs/known-issues/en/confirmed-order-email-not-being-sent.md
@@ -3,8 +3,8 @@ title: 'Confirmed order email not being sent'
 id: 4RelMFApLldLtf0GxhYzdt
 status: PUBLISHED
 createdAt: 2023-03-10T22:07:59.908Z
-updatedAt: 2023-05-29T20:07:11.271Z
-publishedAt: 2023-05-29T20:07:11.271Z
+updatedAt: 2023-08-28T14:53:51.322Z
+publishedAt: 2023-08-28T14:53:51.322Z
 firstPublishedAt: 2023-03-10T22:08:01.026Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/en/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md b/docs/known-issues/en/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
new file mode 100644
index 000000000..68fd59a77
--- /dev/null
+++ b/docs/known-issues/en/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
@@ -0,0 +1,50 @@
+---
+title: 'Conflict between specifications with the same name at the Intelligent Search'
+id: 1TcMLTNMMGqjgbGArywSeh
+status: PUBLISHED
+createdAt: 2023-11-10T00:13:18.275Z
+updatedAt: 2024-06-24T13:48:09.391Z
+publishedAt: 2024-06-24T13:48:09.391Z
+firstPublishedAt: 2023-11-10T00:13:18.980Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: conflict-between-specifications-with-the-same-name-at-the-intelligent-search
+locale: en
+kiStatus: Fixed
+internalReference: 933958
+---
+
+## Summary
+
+
+Multiple specifications with the same name are grouped into the same _"facet"_ by the Intelligent Search, which can be a problem if they have different settings.
+
+Some attributes that may be affected are the filter, hidden and indexed/searchable toggles, field type, and value position. There's no difference between being a product or SKU specification.
+
+It is not possible to know which property will take precedence on top of the other.
+
+
+##
+
+## Simulation
+
+
+For a store with:
+- specification named "foo" (ID 1) set as a filter (to appear in the storefront) and with the value "bar" for a product;
+- another specification named "foo" (but ID 2), which is not a filter, and with value "baz" for the same or another product.
+
+The storefront may render a search filter for the facet/specification "foo" with both values "bar" and "baz" or even hide the whole filter.
+
+
+##
+
+## Workaround
+
+
+Although the Catalog module does not block repeated specification names, this usage should be considered wrong.
+
+
+
+
diff --git a/docs/known-issues/en/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md b/docs/known-issues/en/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
new file mode 100644
index 000000000..7908b6d9c
--- /dev/null
+++ b/docs/known-issues/en/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
@@ -0,0 +1,51 @@
+---
+title: 'Console error [Report Only] - Refused to apply inline style because it violates the following Content Security'
+id: mix75F8F7a7D4iTWyHLyM
+status: PUBLISHED
+createdAt: 2024-04-16T10:30:41.610Z
+updatedAt: 2024-04-16T10:30:42.934Z
+publishedAt: 2024-04-16T10:30:42.934Z
+firstPublishedAt: 2024-04-16T10:30:42.934Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security
+locale: en
+kiStatus: Backlog
+internalReference: 1017370
+---
+
+## Summary
+
+
+We have some logs in the console reporting script blocks due to restrictions via the CSP header.
+The inline style calls to the host io2.vtex.com have this blocking log because it is not released in the CSP of the previous host, thus generating error messages in the console.
+
+
+    [Report Only] Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' https://io.vtex.com.br https://*.vtex.com.br https://*.vtexpayments.com.br https://*.myvtex.com https://*.vtexcommercestable.com.br https://*.vtexcommercebeta.com.br https://*.vteximg.com.br https://*.vtexassets.com 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-AdqydPwVZwz4OteEhuvEEzsFBDTM/J6q0/ZlIWf9Wr4='), or a nonce ('nonce-...') is required to enable inline execution.
+
+
+
+
+##
+
+## Simulation
+
+
+
+1. Go to store checkout;
+2. Open the console and check the report messages;
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/cookie-broken-the-apisessions.md b/docs/known-issues/en/cookie-broken-the-apisessions.md
index 9286fa35a..cfc7655e1 100644
--- a/docs/known-issues/en/cookie-broken-the-apisessions.md
+++ b/docs/known-issues/en/cookie-broken-the-apisessions.md
@@ -3,8 +3,8 @@ title: 'Cookie broken the API/Sessions'
 id: 5knDMVZabZRYaEtITjkDbE
 status: PUBLISHED
 createdAt: 2023-03-27T19:54:42.696Z
-updatedAt: 2023-03-27T19:54:43.232Z
-publishedAt: 2023-03-27T19:54:43.232Z
+updatedAt: 2024-03-20T20:34:36.743Z
+publishedAt: 2024-03-20T20:34:36.743Z
 firstPublishedAt: 2023-03-27T19:54:43.232Z
 contentType: knownIssue
 productTeam: Identity
diff --git a/docs/known-issues/en/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md b/docs/known-issues/en/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
new file mode 100644
index 000000000..70907c7fb
--- /dev/null
+++ b/docs/known-issues/en/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
@@ -0,0 +1,46 @@
+---
+title: 'Cost center dropdown shows only 25 options in B2B Admin Customers'
+id: 1ynkpOppe8iqbwB3CF0euV
+status: PUBLISHED
+createdAt: 2023-10-17T23:11:29.713Z
+updatedAt: 2023-10-17T23:11:30.187Z
+publishedAt: 2023-10-17T23:11:30.187Z
+firstPublishedAt: 2023-10-17T23:11:30.187Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers
+locale: en
+kiStatus: Backlog
+internalReference: 921115
+---
+
+## Summary
+
+
+When registering a new customer using the B2B Admin Customers, the cost center dropdown shows only 25 options.
+
+
+##
+
+## Simulation
+
+
+
+- Register more than 25 cost centers for an organization;
+- Access B2B Customers via admin;
+- Click on "New" and "Add New" at the bottom of the pop-up;
+- When selecting the cost center, the dropdown shows only 25 options.
+
+
+##
+
+## Workaround
+
+
+Use the B2B Organizations to add new users for organization with more than 25 cost centers.
+
+
+
+
diff --git a/docs/known-issues/en/country-field-as-null-in-invoicedata.md b/docs/known-issues/en/country-field-as-null-in-invoicedata.md
new file mode 100644
index 000000000..7d6f94d6f
--- /dev/null
+++ b/docs/known-issues/en/country-field-as-null-in-invoicedata.md
@@ -0,0 +1,44 @@
+---
+title: 'Country field as null in invoiceData'
+id: 6TbzOvnKw5Uhcr1C5Jrneb
+status: PUBLISHED
+createdAt: 2023-12-13T15:53:26.073Z
+updatedAt: 2023-12-19T21:22:09.038Z
+publishedAt: 2023-12-19T21:22:09.038Z
+firstPublishedAt: 2023-12-13T15:53:26.800Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: country-field-as-null-in-invoicedata
+locale: en
+kiStatus: Fixed
+internalReference: 382175
+---
+
+## Summary
+
+
+Country field in invoiceData can be null if sent via API or there is an invoice address in the Profile System with the country as null, so orders will be created with incomplete data in invoiceData.
+
+
+##
+
+## Simulation
+
+
+
+- Assemble a cart with items;
+- Sends the invoiceData without the country field filled via API;
+- Finish the purchase.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md b/docs/known-issues/en/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
index f99686425..809347e8d 100644
--- a/docs/known-issues/en/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
+++ b/docs/known-issues/en/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
@@ -3,8 +3,8 @@ title: 'Country selector for billing address while in international mode stays r
 id: 5lHG60ATBiCdPBQnE1CEuP
 status: PUBLISHED
 createdAt: 2022-05-24T13:38:13.922Z
-updatedAt: 2022-11-25T21:51:33.189Z
-publishedAt: 2022-11-25T21:51:33.189Z
+updatedAt: 2024-02-16T20:29:40.951Z
+publishedAt: 2024-02-16T20:29:40.951Z
 firstPublishedAt: 2022-05-24T13:38:14.583Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 335581
 ---
 
diff --git a/docs/known-issues/en/coupons-created-as-archived-temporarrily.md b/docs/known-issues/en/coupons-created-as-archived-temporarrily.md
new file mode 100644
index 000000000..b4b018c54
--- /dev/null
+++ b/docs/known-issues/en/coupons-created-as-archived-temporarrily.md
@@ -0,0 +1,47 @@
+---
+title: 'Coupons created as archived temporarrily'
+id: 783FJICQzATVkJ2uPgk9Mq
+status: PUBLISHED
+createdAt: 2023-09-01T13:34:21.842Z
+updatedAt: 2023-09-01T13:34:22.607Z
+publishedAt: 2023-09-01T13:34:22.607Z
+firstPublishedAt: 2023-09-01T13:34:22.607Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: coupons-created-as-archived-temporarrily
+locale: en
+kiStatus: Backlog
+internalReference: 892041
+---
+
+## Summary
+
+
+Currently, when a coupon is created, the UI/API shows it is archived for a few minutes (~2) when it actually (on the pricing database), the coupon is active.
+
+After a few minutes, the coupons displays its correct data.
+
+It is important to note that this doesnt affect the "real" coupon info, even when it is incorrectly shown as "archived" on the UI due to this issue, it'll be useable on the checkout.
+
+
+##
+
+## Simulation
+
+
+Simply creating a coupon and checking its daata already shows it as archived.
+
+
+##
+
+## Workaround
+
+
+There is no workaround other than waiting for a short time.
+
+
+
+
+
diff --git a/docs/known-issues/en/create-product-api-doesnt-send-nulls-as-release-date-values.md b/docs/known-issues/en/create-product-api-doesnt-send-nulls-as-release-date-values.md
new file mode 100644
index 000000000..cb6e8500d
--- /dev/null
+++ b/docs/known-issues/en/create-product-api-doesnt-send-nulls-as-release-date-values.md
@@ -0,0 +1,45 @@
+---
+title: "Create product API doesn't send nulls as Release Date values."
+id: 6IjwYVm9SdNEtW9aNYkSrj
+status: PUBLISHED
+createdAt: 2024-04-29T15:10:44.454Z
+updatedAt: 2024-04-29T15:10:45.337Z
+publishedAt: 2024-04-29T15:10:45.337Z
+firstPublishedAt: 2024-04-29T15:10:45.337Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: create-product-api-doesnt-send-nulls-as-release-date-values
+locale: en
+kiStatus: Backlog
+internalReference: 1024207
+---
+
+## Summary
+
+
+When using the create or update product APIs in the catalog application: https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product and sending the field releaseDate as null, in its value, it is created with the current date instead.
+
+
+##
+
+## Simulation
+
+
+1 - Create or update a new product, in your store, via the mentioned API, passing, in its request body, the releaseDate field as a null.
+2 - Access the catalog admin UI or use a GET in the same API path to fetch the sent data
+3 - The releaseDate field will be displaying the sent date's value instead of a null.
+
+
+##
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/en/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md b/docs/known-issues/en/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
new file mode 100644
index 000000000..8b9a631b9
--- /dev/null
+++ b/docs/known-issues/en/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
@@ -0,0 +1,47 @@
+---
+title: "Creating a regionalized sales channel with an already used binding does not update the item's stockbalance"
+id: 7CqZPslfGY8mTmBLuWe5SQ
+status: PUBLISHED
+createdAt: 2024-03-22T19:39:26.469Z
+updatedAt: 2024-07-01T18:49:34.061Z
+publishedAt: 2024-07-01T18:49:34.061Z
+firstPublishedAt: 2024-03-22T19:39:27.432Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance
+locale: en
+kiStatus: No Fix
+internalReference: 1005112
+---
+
+## Summary
+
+
+For regionalized accounts the index system filters by the regionalized sales channels the stockbalance that should appear, in order not to show sales bindings that are not regionalized.
+
+If a new channel needs to be regionalized on a binding that is already in production, the indexation won't be triggered. Causing some inconsistence on the availability of the products.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a regionalized sales channel on a production binding;
+2. Check if the stocks and availability are consistent with all products.
+
+
+##
+
+## Workaround
+
+
+Force a reindex with stockSimulation. Update stock for example.
+
+
+
+
+
diff --git a/docs/known-issues/en/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md b/docs/known-issues/en/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
new file mode 100644
index 000000000..72b98770b
--- /dev/null
+++ b/docs/known-issues/en/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
@@ -0,0 +1,48 @@
+---
+title: 'Creating and deleting a large number of redirects breaks the redirects page'
+id: 5uFuid4a5f7uiRVW9LdT5Q
+status: PUBLISHED
+createdAt: 2024-04-02T19:45:07.540Z
+updatedAt: 2024-04-02T19:45:08.762Z
+publishedAt: 2024-04-02T19:45:08.762Z
+firstPublishedAt: 2024-04-02T19:45:08.762Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page
+locale: en
+kiStatus: Backlog
+internalReference: 1010392
+---
+
+## Summary
+
+
+Dealing with a massive amount of redirects can breaks the UI's page. If you have a lot of redirects or need to delete this huge amount this could lead to a bug where the UI's page is loading forever and never return the redirects information. We think that this may happen because when we delete a huge amount of redirects the first pages from the `listRedirects` query are blank and the UI will look for this first pages to load the first redirects and will never found this.
+
+This can also impact the CLI import/export.
+
+
+##
+
+## Simulation
+
+
+
+- Create a huge amount of redirects
+- Try deleting them (through the UI or using the rewriter)
+- When returning to the UI page the redirects will not load
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md b/docs/known-issues/en/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
new file mode 100644
index 000000000..11dc6accf
--- /dev/null
+++ b/docs/known-issues/en/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
@@ -0,0 +1,47 @@
+---
+title: "Creating wrong redirects containing characters/queries that shouldn't be uploaded the upload/download of the csv through the CLI doesn't work"
+id: 6ShJSvo6g8ZJFaejSo0gx3
+status: PUBLISHED
+createdAt: 2024-01-25T19:00:17.586Z
+updatedAt: 2024-01-25T19:00:18.204Z
+publishedAt: 2024-01-25T19:00:18.204Z
+firstPublishedAt: 2024-01-25T19:00:18.204Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work
+locale: en
+kiStatus: No Fix
+internalReference: 971936
+---
+
+## Summary
+
+
+After creating wrong redirects containing characters that should not be uploaded: ie.: #, queries, or redirects that should be created on the server level, the mass upload/download of the csv through the CLI doesn't work anymore.
+
+
+##
+
+## Simulation
+
+
+Create a redirect for a query for example: /?binding=XXXXX
+Delete the redirect by the graphql IDE (you won't be able to delete otherwise)
+Try to download or upload the CSV of the redirects through the CLI and you want be able to do it.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/etn94WlrSAYOFFj0rZfVwoowE/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+There is currently no workaround for this and the CLI mass download will be unusable.
+
+
+
+
+
diff --git a/docs/known-issues/en/criteria-composition-is-not-returned-on-the-explained-search-ui.md b/docs/known-issues/en/criteria-composition-is-not-returned-on-the-explained-search-ui.md
new file mode 100644
index 000000000..12bcc2633
--- /dev/null
+++ b/docs/known-issues/en/criteria-composition-is-not-returned-on-the-explained-search-ui.md
@@ -0,0 +1,43 @@
+---
+title: 'Criteria composition is not returned on the explained search UI'
+id: 5IyEZe5GBlt732g0rbU5T4
+status: PUBLISHED
+createdAt: 2023-06-29T15:05:18.815Z
+updatedAt: 2023-06-29T15:05:19.578Z
+publishedAt: 2023-06-29T15:05:19.578Z
+firstPublishedAt: 2023-06-29T15:05:19.578Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: criteria-composition-is-not-returned-on-the-explained-search-ui
+locale: en
+kiStatus: Backlog
+internalReference: 852898
+---
+
+## Summary
+
+
+When you search for a term in which the response is only one product, that product will not have the criteria composition appearing on the screen of the explained search.
+
+
+##
+
+## Simulation
+
+
+Try to open the explained search and search for a term in which the response is only one product, that product will not have its criteria composition on the screen.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/crm-error-when-searching-with-spaces.md b/docs/known-issues/en/crm-error-when-searching-with-spaces.md
index 54c5c30fe..dcee68f4d 100644
--- a/docs/known-issues/en/crm-error-when-searching-with-spaces.md
+++ b/docs/known-issues/en/crm-error-when-searching-with-spaces.md
@@ -20,7 +20,7 @@ internalReference:
 
 User receives a generic error message when using the CRM's search bar to filter documents containing attributes with spaces. Example:Searching for a city called "Rio de Janeiro" will yield an error message
 
-[Screen Shot 2018-12-26 at 14.38.55](https://images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
+[Screen Shot 2018-12-26 at 14.38.55](//images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
 
 ## Simulation
 
@@ -31,6 +31,6 @@ User receives a generic error message when using the CRM's search bar to filter
 
 ## Workaround
 
-![Screen Shot 2018-12-26 at 14.40.03](https://images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
+![Screen Shot 2018-12-26 at 14.40.03](//images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
 Fortunately there is a simple workaround that does not require the use of an API.  By clicking on the "Todos"("All") dropdown next to the search bar, the same search can be made successfully without an error message.
 
diff --git a/docs/known-issues/en/currency-symbol-does-not-follow-admin-language.md b/docs/known-issues/en/currency-symbol-does-not-follow-admin-language.md
new file mode 100644
index 000000000..c44dd3630
--- /dev/null
+++ b/docs/known-issues/en/currency-symbol-does-not-follow-admin-language.md
@@ -0,0 +1,47 @@
+---
+title: 'Currency symbol does not follow admin language'
+id: 7gEGdkDSbRCtk2Q1u2nW6k
+status: PUBLISHED
+createdAt: 2024-03-15T19:37:45.395Z
+updatedAt: 2024-03-15T19:40:56.682Z
+publishedAt: 2024-03-15T19:40:56.682Z
+firstPublishedAt: 2024-03-15T19:37:46.387Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: currency-symbol-does-not-follow-admin-language
+locale: en
+kiStatus: Backlog
+internalReference: 1000915
+---
+
+## Summary
+
+
+When a user accesses the cart configuration screen in the orders area (`https://{accountname}}.myvtex.com/admin/checkout/#/configurations )` the currency symbol follows the conventions of the locale indicated by the admin, the exchange of this symbol is done whenever the admin indicates a different locale, however according to our analysis this exchange is failing at certain times, causing the currency symbol indicated to be the default of the page which in this case is R$.
+
+
+##
+
+## Simulation
+
+
+
+
+- Log in to admin
+- Go to https://.myvtex.com/admin/checkout/#/configurations
+- Change the locale to PT and back to EN;
+- Refresh the page, and you will see that currency symbol is still R$;
+
+
+##
+
+## Workaround
+
+
+We currently don't have a Workaround for this scenario, but it doesn't impact the store's operation, as the Currency Symbol in this area is only visual with no operational impact on the store.
+
+
+
+
diff --git a/docs/known-issues/en/custom-attribute-mapper-mercado-livre.md b/docs/known-issues/en/custom-attribute-mapper-mercado-livre.md
new file mode 100644
index 000000000..04260e279
--- /dev/null
+++ b/docs/known-issues/en/custom-attribute-mapper-mercado-livre.md
@@ -0,0 +1,44 @@
+---
+title: 'Custom Attribute Mapper Mercado Livre'
+id: 4A7inX7nFte4jRhZRLkPRO
+status: PUBLISHED
+createdAt: 2023-12-12T09:59:40.945Z
+updatedAt: 2024-02-16T20:26:22.091Z
+publishedAt: 2024-02-16T20:26:22.091Z
+firstPublishedAt: 2023-12-12T09:59:41.722Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: custom-attribute-mapper-mercado-livre
+locale: en
+kiStatus: No Fix
+internalReference: 521197
+---
+
+## Summary
+
+
+
+In the new mapper screen, we do not have the option to create a custom attribute in MELI.
+
+
+##
+
+## Simulation
+
+
+
+Inside Mapper screen, the custom attribute is missing from what we had in the spreadsheet.
+
+
+##
+
+## Workaround
+
+
+currently no workaround is available, Its only allowed to create a custom valeu inside the attribute, but not a custom attribute.
+
+
+
+
diff --git a/docs/known-issues/en/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md b/docs/known-issues/en/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
new file mode 100644
index 000000000..d3764c4da
--- /dev/null
+++ b/docs/known-issues/en/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
@@ -0,0 +1,46 @@
+---
+title: 'Custom elements on legacy cms not working with more than one HTML'
+id: 6hGraRq2ffsw5c3jJ8nwh0
+status: PUBLISHED
+createdAt: 2023-07-31T16:35:04.392Z
+updatedAt: 2023-07-31T16:35:05.018Z
+publishedAt: 2023-07-31T16:35:05.018Z
+firstPublishedAt: 2023-07-31T16:35:05.018Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: custom-elements-on-legacy-cms-not-working-with-more-than-one-html
+locale: en
+kiStatus: Backlog
+internalReference: 871480
+---
+
+## Summary
+
+
+When creating a custom element with more than one HTML element, only the first one is loaded on the template.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a custom element with HTML type;
+2. Create a least 2 html codes on this custom element;
+3. Check that the template that has this custom element only loads the first HTML.
+
+
+##
+
+## Workaround
+
+
+Gather all htmls on only one element on the custom element.
+
+
+
+
+
diff --git a/docs/known-issues/en/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md b/docs/known-issues/en/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
index 4a0551f2e..10ffbd339 100644
--- a/docs/known-issues/en/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
+++ b/docs/known-issues/en/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
@@ -3,8 +3,8 @@ title: 'Custom video thumbnail image is not displayed on mobile version'
 id: 5d71mBz4kXdwX7AhspYhit
 status: PUBLISHED
 createdAt: 2022-03-21T17:51:55.027Z
-updatedAt: 2022-11-25T21:54:30.917Z
-publishedAt: 2022-11-25T21:54:30.917Z
+updatedAt: 2024-07-01T18:48:03.005Z
+publishedAt: 2024-07-01T18:48:03.005Z
 firstPublishedAt: 2022-03-21T17:51:55.483Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: custom-video-thumbnail-image-is-not-displayed-on-mobile-version
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 412632
 ---
 
diff --git a/docs/known-issues/en/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md b/docs/known-issues/en/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
index b27061ea5..0be7881fa 100644
--- a/docs/known-issues/en/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
+++ b/docs/known-issues/en/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
@@ -3,8 +3,8 @@ title: 'Customer Credit invoices status at MyCredits page are not correct'
 id: 413knN4Gtk9GuZV5zFlw7k
 status: PUBLISHED
 createdAt: 2022-03-27T17:49:32.464Z
-updatedAt: 2022-11-25T22:06:46.582Z
-publishedAt: 2022-11-25T22:06:46.582Z
+updatedAt: 2024-02-16T20:25:28.872Z
+publishedAt: 2024-02-16T20:25:28.872Z
 firstPublishedAt: 2022-03-27T17:49:33.246Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: customer-credit-invoices-status-at-mycredits-page-are-not-correct
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 369457
 ---
 
diff --git a/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
new file mode 100644
index 000000000..ceda43ea0
--- /dev/null
+++ b/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -0,0 +1,43 @@
+---
+title: 'Customer information being lost when it has some order with "profileErrorOnLoading"'
+id: 7B0eutLBOCKOun4iwALVpq
+status: PUBLISHED
+createdAt: 2023-06-27T12:51:33.790Z
+updatedAt: 2023-06-27T12:51:34.237Z
+publishedAt: 2023-06-27T12:51:34.237Z
+firstPublishedAt: 2023-06-27T12:51:34.237Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: customer-information-being-lost-when-it-has-some-order-with-profileerroronloading
+locale: en
+kiStatus: Backlog
+internalReference: 340036
+---
+
+## Summary
+
+
+When the order has "profileErrorOnLoading=true", the expected behavior is that the customer profile, address, and credit card won't be saved/updated on the Profile System.
+
+The problem is that the checkout is still making some requests to register the buyer's e-mail, naturally, without sending other fields like name and phone. So, if the customer is already registered in the store, these fields are cleared, and the customer data is lost.
+
+
+##
+
+## Simulation
+
+
+We can't simulate the behavior since the "profileErrorOnLoading" is just for unexpected exceptions.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/customer-information-is-not-saved-in-the-profile-system.md b/docs/known-issues/en/customer-information-is-not-saved-in-the-profile-system.md
index 76d39fad3..3da81abe9 100644
--- a/docs/known-issues/en/customer-information-is-not-saved-in-the-profile-system.md
+++ b/docs/known-issues/en/customer-information-is-not-saved-in-the-profile-system.md
@@ -3,8 +3,8 @@ title: 'Customer information is not saved in the Profile System'
 id: 1MCiEAJ3ZueJVM04T7x9z2
 status: PUBLISHED
 createdAt: 2023-04-04T22:47:43.035Z
-updatedAt: 2023-04-06T17:51:29.025Z
-publishedAt: 2023-04-06T17:51:29.025Z
+updatedAt: 2023-11-01T12:37:24.071Z
+publishedAt: 2023-11-01T12:37:24.071Z
 firstPublishedAt: 2023-04-04T22:47:43.593Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: customer-information-is-not-saved-in-the-profile-system
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 784763
 ---
 
diff --git a/docs/known-issues/en/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md b/docs/known-issues/en/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
index 86fa6d978..744a4a819 100644
--- a/docs/known-issues/en/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
+++ b/docs/known-issues/en/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
@@ -3,8 +3,8 @@ title: 'Customized cluster expression not working on free shipping promotion + D
 id: 27QJfNVhuPNiRxqQiXPRt2
 status: PUBLISHED
 createdAt: 2022-03-16T19:36:36.102Z
-updatedAt: 2022-11-25T22:12:51.339Z
-publishedAt: 2022-11-25T22:12:51.339Z
+updatedAt: 2024-02-16T20:29:37.996Z
+publishedAt: 2024-02-16T20:29:37.996Z
 firstPublishedAt: 2022-03-16T19:36:36.504Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 334027
 ---
 
diff --git a/docs/known-issues/en/cvv-without-validation-of-characters-type.md b/docs/known-issues/en/cvv-without-validation-of-characters-type.md
index 1367b6a78..d48b99291 100644
--- a/docs/known-issues/en/cvv-without-validation-of-characters-type.md
+++ b/docs/known-issues/en/cvv-without-validation-of-characters-type.md
@@ -3,8 +3,8 @@ title: 'CVV without validation of characters type'
 id: 63MJ3ODCvr3ayfgJiuN1ja
 status: PUBLISHED
 createdAt: 2022-03-27T20:25:43.400Z
-updatedAt: 2022-11-25T22:07:55.541Z
-publishedAt: 2022-11-25T22:07:55.541Z
+updatedAt: 2024-02-16T20:29:04.636Z
+publishedAt: 2024-02-16T20:29:04.636Z
 firstPublishedAt: 2022-03-27T20:25:43.819Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: cvv-without-validation-of-characters-type
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 425204
 ---
 
diff --git a/docs/known-issues/en/deactivated-payment-system-rendering-at-checkout.md b/docs/known-issues/en/deactivated-payment-system-rendering-at-checkout.md
new file mode 100644
index 000000000..734ed8063
--- /dev/null
+++ b/docs/known-issues/en/deactivated-payment-system-rendering-at-checkout.md
@@ -0,0 +1,42 @@
+---
+title: 'Deactivated payment system rendering at checkout'
+id: 2LQYOKtkURQoWUU1InCRUo
+status: PUBLISHED
+createdAt: 2024-06-13T19:37:58.649Z
+updatedAt: 2024-06-13T19:37:59.481Z
+publishedAt: 2024-06-13T19:37:59.481Z
+firstPublishedAt: 2024-06-13T19:37:59.481Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: deactivated-payment-system-rendering-at-checkout
+locale: en
+kiStatus: Backlog
+internalReference: 1049543
+---
+
+## Summary
+
+
+The issue seems to happen only in sub accounts, even deactivated (also deleted) the payment method renders at checkout
+
+
+##
+
+## Simulation
+
+
+We were not able to simulate.
+
+
+##
+
+## Workaround
+
+
+A manual correction can be performed, the support team must be reached for this.
+
+
+
+
diff --git a/docs/known-issues/en/deadlocked-error-when-using-catalog-apis.md b/docs/known-issues/en/deadlocked-error-when-using-catalog-apis.md
new file mode 100644
index 000000000..9a45943d1
--- /dev/null
+++ b/docs/known-issues/en/deadlocked-error-when-using-catalog-apis.md
@@ -0,0 +1,47 @@
+---
+title: 'deadlocked error when using Catalog APIs'
+id: 6A4jBKBKIzn87mxNQJ4YQN
+status: PUBLISHED
+createdAt: 2023-07-14T18:29:11.937Z
+updatedAt: 2023-07-19T14:16:39.062Z
+publishedAt: 2023-07-19T14:16:39.062Z
+firstPublishedAt: 2023-07-14T18:29:13.088Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: deadlocked-error-when-using-catalog-apis
+locale: en
+kiStatus: Backlog
+internalReference: 862626
+---
+
+## Summary
+
+
+The constant use of some catalog APIs like "Add SKU to Subcollection" or trying to link products through the suggestions module can cause deadlocked errors for the merchant.
+
+Deadlocked erros can happen when there is a concurrence in saving the data on the database. So when requesting too much the API in a short period of time, this errors are more evident.
+
+
+##
+
+## Simulation
+
+
+
+1. Use, for instance, the Add SKU to Subcollection API (https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/subcollection/-subCollectionId-/stockkeepingunit) to add lots of skus into a collection in a short period of time;
+2. Check that errors might happen, such is deadlocked.
+
+
+##
+
+## Workaround
+
+
+Try to make less requests per minute.
+
+
+
+
+
diff --git a/docs/known-issues/en/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md b/docs/known-issues/en/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
index bacc09d1c..bf4c76bb4 100644
--- a/docs/known-issues/en/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
+++ b/docs/known-issues/en/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
@@ -3,8 +3,8 @@ title: 'Debit payments using Firstdata connector cannot be settled due to an err
 id: 6imTj4PTpJGGFqyhSLTPu9
 status: PUBLISHED
 createdAt: 2022-03-03T21:59:55.119Z
-updatedAt: 2022-11-25T22:05:01.885Z
-publishedAt: 2022-11-25T22:05:01.885Z
+updatedAt: 2024-02-16T20:24:59.932Z
+publishedAt: 2024-02-16T20:24:59.932Z
 firstPublishedAt: 2022-03-03T21:59:55.506Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,33 +12,36 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 461095
 ---
 
 ## Summary
 
 
-When using Firstdata connector to process debit payments, our code expects the field `TransactionState`as "CAPTURED". However, the provider is sending "CAPTURED" as well as "SETTLED" which triggers an error:
+When utilizing the Firstdata connector for processing debit payments, our code is designed to expect the field TransactionState to be set as "CAPTURED." However, we have encountered an issue where the provider is sending both "CAPTURED" and "SETTLED" values, which is causing an error to occur:
 
-Message: Unknown Error on AutoSettleThere is an error in XML document (1, 745).
-&
-Error executing Settlement operation. Please, see the inner exception. Connector = Firstdata. Message = Input string was not in a correct format.
 
-I couldn't find in the firstdata documentation what is the correct one, but there are examples for both of them.
+    Error Message: Unknown Error on AutoSettle. There is an error in the XML document (1, 745). & Error executing the Settlement operation. Please refer to the inner exception. Connector: Firstdata. Message: Input string was not in the correct format.
 
 
 
-## Simulation
+##
 
+## Simulation
 
 
-Sometimes when a transaction is canceled using this connector is possible to observe this behavior.
+It is not possible to simulate since it is an intermittent behavior that depends on the payment provider's response.
 
 
+##
 
 ## Workaround
 
 
-No workaround is available.
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/en/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md b/docs/known-issues/en/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
new file mode 100644
index 000000000..f33bf82c1
--- /dev/null
+++ b/docs/known-issues/en/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
@@ -0,0 +1,42 @@
+---
+title: 'Deleted Customer Credit rules will appear at checkout if not deactivated previously'
+id: 7culNJ04UcZfzgHFREyNEs
+status: PUBLISHED
+createdAt: 2024-03-04T23:12:22.826Z
+updatedAt: 2024-03-04T23:12:23.859Z
+publishedAt: 2024-03-04T23:12:23.859Z
+firstPublishedAt: 2024-03-04T23:12:23.859Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously
+locale: en
+kiStatus: Backlog
+internalReference: 994066
+---
+
+## Summary
+
+
+If you have `vtex.custom-payments` app installed and delete a Customer Credit payment rule without deactivating it first it will be rendered at checkout.
+
+
+##
+
+## Simulation
+
+
+With `vtex.custom-payments` installed in the account create several Customer Credit installment rules and delete one without deactivating, you will see it at checkout.
+
+
+##
+
+## Workaround
+
+
+It's possible to manually fix this with the help of support team.
+
+
+
+
diff --git a/docs/known-issues/en/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md b/docs/known-issues/en/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
new file mode 100644
index 000000000..4d71eb626
--- /dev/null
+++ b/docs/known-issues/en/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
@@ -0,0 +1,46 @@
+---
+title: 'Delivery capacity is not respected if there is space in the Id of Shipping Policy'
+id: 1OyY54G05o15EI2zAmW4Vq
+status: PUBLISHED
+createdAt: 2023-07-14T21:25:50.522Z
+updatedAt: 2024-03-19T19:26:55.344Z
+publishedAt: 2024-03-19T19:26:55.344Z
+firstPublishedAt: 2023-07-14T21:25:51.117Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy
+locale: en
+kiStatus: Backlog
+internalReference: 862830
+---
+
+## Summary
+
+
+If the delivery scheduling feature is in use and delivery capacity is enabled, there are two known scenarios that can make the window available even after it has reached its maximum configured capacity limit.
+The scenarios are: Shipping policy id with a space or too many characters making up the string, `AccountName+ShippingPolicyId` cannot exceed 60 characters.
+
+
+##
+
+## Simulation
+
+
+Create a shipping policy and, in its Id, insert a space, or `AccountName+ShippingPolicyId` resulting in more than 60 characters, configure scheduled delivery and delivery capacity.
+Place orders by selecting the registered window, check that it will be possible to create more orders than the maximum configured in the delivery capacity.
+At checkout, when the configured limit is reached, the window should not become unavailable, but will remain visible and can be selected.
+
+
+##
+
+## Workaround
+
+
+Do not register any Id with a space in the shipping policy or with more than 60 characters adding together the characters in the `AccountName+ShippingPolicyId`.
+
+
+
+
+
diff --git a/docs/known-issues/en/delivery-split-with-lean-shipping-offering-invalid-sla.md b/docs/known-issues/en/delivery-split-with-lean-shipping-offering-invalid-sla.md
new file mode 100644
index 000000000..8a750457e
--- /dev/null
+++ b/docs/known-issues/en/delivery-split-with-lean-shipping-offering-invalid-sla.md
@@ -0,0 +1,49 @@
+---
+title: 'Delivery split with Lean Shipping offering invalid SLA'
+id: 61Yq1WhmCclFtcum3YMtXn
+status: PUBLISHED
+createdAt: 2024-02-27T19:21:21.615Z
+updatedAt: 2024-02-27T19:26:27.513Z
+publishedAt: 2024-02-27T19:26:27.513Z
+firstPublishedAt: 2024-02-27T19:21:22.667Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: delivery-split-with-lean-shipping-offering-invalid-sla
+locale: en
+kiStatus: Backlog
+internalReference: 990155
+---
+
+## Summary
+
+
+When a shopping cart includes products from different sellers, with different delivery channels, and SLA IDs among them, Checkout UI activates Lean Shipping, summarizing the available SLAs to display only the "fastest" and "cheapest" options for each item.
+
+However, if there is a scheduled delivery option but it is not the fastest or cheapest one, the scheduling toggle will still appear in the UI, even though Lean Shipping will not select it as a viable option.
+
+
+##
+
+## Simulation
+
+
+
+- Assemble a cart with at least 2 different sellers, where one item has 3 SLAs, where the scheduled one is neither the fastest nor cheapest option (and thus will not be offered through Lean Shipping).
+- Select pickup-in-store.
+- Use the UI's scheduling interface for the other item's delivery.
+- Notice that it still applies the fastest/cheapest (non-scheduled) SLA, rather than the scheduled one, effectively ignoring your delivery window selection from the previous step.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/departments-name-not-loading-on-seller-management-commissions-ui.md b/docs/known-issues/en/departments-name-not-loading-on-seller-management-commissions-ui.md
new file mode 100644
index 000000000..794beb93f
--- /dev/null
+++ b/docs/known-issues/en/departments-name-not-loading-on-seller-management-commissions-ui.md
@@ -0,0 +1,47 @@
+---
+title: "Department's name not loading on seller management commissions UI"
+id: 5TkKtfYi5oFxNOk0mTTeiQ
+status: PUBLISHED
+createdAt: 2024-03-25T17:20:22.888Z
+updatedAt: 2024-03-25T17:20:23.761Z
+publishedAt: 2024-03-25T17:20:23.761Z
+firstPublishedAt: 2024-03-25T17:20:23.761Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: departments-name-not-loading-on-seller-management-commissions-ui
+locale: en
+kiStatus: Backlog
+internalReference: 1005799
+---
+
+## Summary
+
+
+When selecting a department to set a specific commission on the seller management the table is not loading the department's name. The behavior does not happen for child categories.
+ ![](https://vtexhelp.zendesk.com/attachments/token/irbcBV8R7kNO4F5XsLHtaxUMO/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+
+1. Enable the toggle "Add commissions by category"
+2. Select a department to map the commissions and save the seller
+3. Check that the UI is not loading the department name.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/diacritics-are-removed-on-catalogapi.md b/docs/known-issues/en/diacritics-are-removed-on-catalogapi.md
index b740f0192..5edb89914 100644
--- a/docs/known-issues/en/diacritics-are-removed-on-catalogapi.md
+++ b/docs/known-issues/en/diacritics-are-removed-on-catalogapi.md
@@ -3,8 +3,8 @@ title: 'Diacritics are removed on CatalogAPI'
 id: 2iVyAQ8TSaT3jFYzcQGjSs
 status: PUBLISHED
 createdAt: 2022-07-22T18:18:04.236Z
-updatedAt: 2022-11-25T21:44:21.525Z
-publishedAt: 2022-11-25T21:44:21.525Z
+updatedAt: 2024-02-16T20:28:19.994Z
+publishedAt: 2024-02-16T20:28:19.994Z
 firstPublishedAt: 2022-07-22T18:18:05.160Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: diacritics-are-removed-on-catalogapi
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 623345
 ---
 
diff --git a/docs/known-issues/en/difference-in-prices-between-pdp-plp-and-checkout-cart.md b/docs/known-issues/en/difference-in-prices-between-pdp-plp-and-checkout-cart.md
new file mode 100644
index 000000000..dfa970f1e
--- /dev/null
+++ b/docs/known-issues/en/difference-in-prices-between-pdp-plp-and-checkout-cart.md
@@ -0,0 +1,47 @@
+---
+title: 'Difference in prices between PDP, PLP and Checkout Cart'
+id: 3Oo5ccYOG7hcEXYaROxXMV
+status: PUBLISHED
+createdAt: 2023-06-29T20:02:13.485Z
+updatedAt: 2023-06-29T20:02:14.572Z
+publishedAt: 2023-06-29T20:02:14.572Z
+firstPublishedAt: 2023-06-29T20:02:14.572Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: difference-in-prices-between-pdp-plp-and-checkout-cart
+locale: en
+kiStatus: Backlog
+internalReference: 853175
+---
+
+## Summary
+
+
+
+Portal is delivering the same content on the PDPs and PLPs even after some updates like promotions.
+
+
+##
+
+## Simulation
+
+
+
+With an expired cache, the CND asks the portal system if the page was changed. If so, the portal delivers the new page to be rendered, otherwise, the CDN redraws the page it already has.
+
+In this case, we saw that although the page had submitted some changes, the inclusion of a promotion, the portal returned to the CDN that there was no change compared to the cached page and therefore the edge layer was rendering the page without promotion.
+
+
+##
+
+## Workaround
+
+
+
+One way around it was **to change the template of the product page (like include a comment**), so the portal informes that there was a change in the structure, and the CDN gets the new page to be cached.
+
+
+
+
diff --git a/docs/known-issues/en/differences-between-specification-value-on-apis-and-portal.md b/docs/known-issues/en/differences-between-specification-value-on-apis-and-portal.md
new file mode 100644
index 000000000..911d20eae
--- /dev/null
+++ b/docs/known-issues/en/differences-between-specification-value-on-apis-and-portal.md
@@ -0,0 +1,50 @@
+---
+title: 'Differences between Specification Value on APIs and Portal'
+id: 29Utcf4B7PBZitEHxrZwbE
+status: PUBLISHED
+createdAt: 2023-06-29T20:11:49.484Z
+updatedAt: 2023-07-06T13:41:29.683Z
+publishedAt: 2023-07-06T13:41:29.683Z
+firstPublishedAt: 2023-06-29T20:11:50.157Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: differences-between-specification-value-on-apis-and-portal
+locale: en
+kiStatus: Backlog
+internalReference: 853184
+---
+
+## Summary
+
+
+
+Currently these two APIs ("api/catalog" and "api/catalog_system" GET Specification Value) are consulting different tables on the catalog database. The values are supposed to be the same on both tables, however scenarios with special characters may diverge.
+
+This also reflects on the Portal and PDPs, since the information is being generated based on the wrong table. The special characters appear as "????" on the frontend.
+
+
+##
+
+## Simulation
+
+
+
+1. Have a specification value with a special characters;
+2. Check the results on the "api/catalog" and "api/catalog_system" APIs;
+3. Check the PDP information;
+4. Verify if they were equal.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md b/docs/known-issues/en/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
index d6ac8f1b3..2c2fe4ef7 100644
--- a/docs/known-issues/en/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
+++ b/docs/known-issues/en/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
@@ -3,8 +3,8 @@ title: "Disclosure Layout can't be used properly when prop animated is set as tr
 id: 14QweVpzLO8TsyI68H79ZG
 status: PUBLISHED
 createdAt: 2022-04-19T19:53:22.409Z
-updatedAt: 2022-11-25T22:13:15.022Z
-publishedAt: 2022-11-25T22:13:15.022Z
+updatedAt: 2024-07-01T18:48:05.329Z
+publishedAt: 2024-07-01T18:48:05.329Z
 firstPublishedAt: 2022-04-19T19:53:23.090Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 417947
 ---
 
diff --git a/docs/known-issues/en/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md b/docs/known-issues/en/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
new file mode 100644
index 000000000..4d361f567
--- /dev/null
+++ b/docs/known-issues/en/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
@@ -0,0 +1,44 @@
+---
+title: 'Discrepancy on coupon usage count on OMS and coupons UI'
+id: 5PyOeirr1XqXREmQJpSHs1
+status: PUBLISHED
+createdAt: 2023-12-18T21:53:26.360Z
+updatedAt: 2023-12-18T21:53:27.039Z
+publishedAt: 2023-12-18T21:53:27.039Z
+firstPublishedAt: 2023-12-18T21:53:27.039Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui
+locale: en
+kiStatus: Backlog
+internalReference: 954959
+---
+
+## Summary
+
+
+Some orders are not being retrieved in the usage of the coupons, we identified that a few orders weren't being counted by the coupons admin.
+
+
+##
+
+## Simulation
+
+
+Check if between 10/09 and 13/09 there's any discrepancy between coupon usages
+
+
+##
+
+## Workaround
+
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md b/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md
index dfe08aff1..96c43c14f 100644
--- a/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md
+++ b/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md
@@ -26,7 +26,7 @@ The order is closed and normally transacted at VTEX. But, depending on the exter
 
 Example of occurrence:
 
-![image](https://images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
 
 In this case, the total value of the order charged to the customer was `R$ 7.98`. However, when adding the sales figures recorded in each product, the total would be `R$ 7.95`.
 
diff --git a/docs/known-issues/en/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md b/docs/known-issues/en/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
new file mode 100644
index 000000000..2879a322f
--- /dev/null
+++ b/docs/known-issues/en/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
@@ -0,0 +1,47 @@
+---
+title: 'Divergence on the Advanced Store Settings on new accounts or workspaces'
+id: 1Jt8McqXjYAxfJNkBZHt4j
+status: PUBLISHED
+createdAt: 2024-07-11T18:16:01.106Z
+updatedAt: 2024-07-11T18:16:02.006Z
+publishedAt: 2024-07-11T18:16:02.006Z
+firstPublishedAt: 2024-07-11T18:16:02.006Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces
+locale: en
+kiStatus: Backlog
+internalReference: 1064235
+---
+
+## Summary
+
+
+On new workspaces or accounts that never changed the advanced configurations of the Store Settings can verify an inconsistency between the information on the UI and the flag applied to the account.
+
+
+##
+
+## Simulation
+
+
+
+- Create a new workspace
+- Go to the Store Settings in the Advanced tab
+- See that some flags are set on the UI
+- Verify the configurations using the settings plugin with the following command `vtex settings get vtex.store`.
+- See that the flags are not applied.
+
+
+##
+
+## Workaround
+
+
+Click on the "Save" button on the UI
+
+
+
+
diff --git a/docs/known-issues/en/divergent-status-on-the-transaction-list-and-on-the-transaction.md b/docs/known-issues/en/divergent-status-on-the-transaction-list-and-on-the-transaction.md
index 652f440bb..816b7ce2a 100644
--- a/docs/known-issues/en/divergent-status-on-the-transaction-list-and-on-the-transaction.md
+++ b/docs/known-issues/en/divergent-status-on-the-transaction-list-and-on-the-transaction.md
@@ -3,8 +3,8 @@ title: 'Divergent status on the transaction list and on the transaction'
 id: 1LD32IQJFbvlOJzD12KL64
 status: PUBLISHED
 createdAt: 2022-03-03T18:41:10.292Z
-updatedAt: 2022-11-25T22:09:15.186Z
-publishedAt: 2022-11-25T22:09:15.186Z
+updatedAt: 2023-12-12T22:12:02.916Z
+publishedAt: 2023-12-12T22:12:02.916Z
 firstPublishedAt: 2022-03-03T18:41:10.764Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: divergent-status-on-the-transaction-list-and-on-the-transaction
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 308919
 ---
 
@@ -22,6 +22,7 @@ internalReference: 308919
 The status of the transactions is different once you open them compared to what is shown in the transaction's list.
 
 
+##
 
 ## Simulation
 
@@ -30,9 +31,13 @@ Since it does not happen in all transactions, the way to simulate it is to enter
 Once you enter into the transaction, in fact, the status is different
 
 
+##
 
 ## Workaround
 
 
 There isn't a workaround.
 
+
+
+
diff --git a/docs/known-issues/en/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md b/docs/known-issues/en/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
new file mode 100644
index 000000000..702ec3e87
--- /dev/null
+++ b/docs/known-issues/en/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
@@ -0,0 +1,46 @@
+---
+title: 'Document number field (RUT) randomly getting last digit deleted on iOS'
+id: 6KcbAWPN3AylZEm6IkSw3I
+status: PUBLISHED
+createdAt: 2023-10-18T22:53:27.101Z
+updatedAt: 2023-10-19T13:02:18.095Z
+publishedAt: 2023-10-19T13:02:18.095Z
+firstPublishedAt: 2023-10-18T22:53:27.624Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: document-number-field-rut-randomly-getting-last-digit-deleted-on-ios
+locale: en
+kiStatus: Backlog
+internalReference: 921944
+---
+
+## Summary
+
+
+Only on Safari/iOS, when filling in the document number and moving through the customer data fields, the document number field (RUT) will have the last digit deleted.
+
+
+##
+
+## Simulation
+
+
+
+- Input a valid document number in the RUT field;
+- Go to the following field (phone);
+- Go back to the document field, delete, and type the same number;
+- Change input again, and the last digit of the RUT field will be deleted.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md b/docs/known-issues/en/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
index 9fb4e418f..9fd4b8b9c 100644
--- a/docs/known-issues/en/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
+++ b/docs/known-issues/en/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
@@ -3,8 +3,8 @@ title: 'Duplicated entries for categories/specification values on the same level
 id: IoWI8yx1cabm4bWhSU4Ek
 status: PUBLISHED
 createdAt: 2022-04-18T18:53:37.507Z
-updatedAt: 2022-11-25T21:58:08.677Z
-publishedAt: 2022-11-25T21:58:08.677Z
+updatedAt: 2024-02-16T20:26:00.077Z
+publishedAt: 2024-02-16T20:26:00.077Z
 firstPublishedAt: 2022-04-18T18:53:38.097Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: duplicated-entries-for-categoriesspecification-values-on-the-same-level
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 562588
 ---
 
diff --git a/docs/known-issues/en/duplicated-organizations-in-modal-to-switch-between-organizations.md b/docs/known-issues/en/duplicated-organizations-in-modal-to-switch-between-organizations.md
new file mode 100644
index 000000000..ec784bf4a
--- /dev/null
+++ b/docs/known-issues/en/duplicated-organizations-in-modal-to-switch-between-organizations.md
@@ -0,0 +1,46 @@
+---
+title: 'Duplicated organizations in modal to switch between organizations'
+id: 7pOIj0RzcmA5mZy60OpfRk
+status: PUBLISHED
+createdAt: 2024-02-22T16:51:15.327Z
+updatedAt: 2024-02-22T16:51:16.213Z
+publishedAt: 2024-02-22T16:51:16.213Z
+firstPublishedAt: 2024-02-22T16:51:16.213Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: duplicated-organizations-in-modal-to-switch-between-organizations
+locale: en
+kiStatus: Backlog
+internalReference: 986868
+---
+
+## Summary
+
+
+When a user has many organizations registered and uses the modal to switch between organizations, some organizations will be shown duplicated in the list.
+
+
+##
+
+## Simulation
+
+
+
+- Configure many organizations for the same email;
+- Log in and open the modal to switch the organization;
+- Some organizations will be duplicated in the list.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/ean-field-as-string-being-ignored-when-approved-on-received-skus.md b/docs/known-issues/en/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
new file mode 100644
index 000000000..40c656417
--- /dev/null
+++ b/docs/known-issues/en/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
@@ -0,0 +1,46 @@
+---
+title: 'Ean field as string being ignored when approved on Received Skus'
+id: 3ubVdtlt8ElWzQGFM9OTTq
+status: PUBLISHED
+createdAt: 2023-09-11T16:37:06.258Z
+updatedAt: 2023-11-28T16:54:04.790Z
+publishedAt: 2023-11-28T16:54:04.790Z
+firstPublishedAt: 2023-09-11T16:37:07.098Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: ean-field-as-string-being-ignored-when-approved-on-received-skus
+locale: en
+kiStatus: Backlog
+internalReference: 897301
+---
+
+## Summary
+
+
+The seller sends the sku with all fields declared on this article (https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-) for the marketplace to approve on the Received Skus module.
+
+The ean field is declared as string type on the above article. However, despite appearing on the Received Skus UI, is being ignored by the matcher backend system and also by the catalog module, meaning the sku is being created with this field empty.
+
+
+##
+
+## Simulation
+
+
+1. Send a sku to the marketplace with the ean field set as string: `"ean": "123456"`
+2. Approve the sku as a new product on the marketplace's Received Skus module;
+3. Check that on the catalog this field is set as empty.
+
+##
+
+## Workaround
+
+
+**Before this issue is fixed and the system is working according to our docs**, the format that is currently working is sending the ean field as an array:
+`"ean": ["123456"]`
+
+Another way is to set this field manually on the catalog side once the sku is approved.
+
+
diff --git a/docs/known-issues/en/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md b/docs/known-issues/en/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
new file mode 100644
index 000000000..2f34b71ad
--- /dev/null
+++ b/docs/known-issues/en/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
@@ -0,0 +1,56 @@
+---
+title: 'Early Capture wrongfully competing with Automatic Capture on AuthorizeDotNet'
+id: 2IDoJIBiGzhkVZGHurLsnj
+status: PUBLISHED
+createdAt: 2023-07-20T18:08:30.934Z
+updatedAt: 2023-07-20T18:08:31.479Z
+publishedAt: 2023-07-20T18:08:31.479Z
+firstPublishedAt: 2023-07-20T18:08:31.479Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet
+locale: en
+kiStatus: Backlog
+internalReference: 866068
+---
+
+## Summary
+
+
+In order for us to understand this behavior, first we need to comprehend the difference between automatic capture and early capture:
+
+**Automatic Capture:** It will call the settlement request automatically once the date is reached, no matter if the transaction is or isn't approved by the acquirer and the antifraud.
+
+**Early Capture:** It will call the settlement request after the antifraud approves the transaction, once the amount of days configured is reached.
+
+In this connector, the automatic capture is hard coded to happen after 4 days, while the early capture can be configured to a maximum of 10 days after antifraud approval. They end up competing with each other, and if the early capture is configured to a value bigger than 4 days the automatic capture will always occur sooner, so it will always be called first.
+
+This makes the values allowed in the early capture to be useless if they are bigger than 4 days.
+
+
+##
+
+## Simulation
+
+
+
+
+1. Configure the AuthorizeDotNet connector in your store;
+2. Set the field "Early Capture" to an amount higher than 4 days;
+3. Make a test transaction;
+4. Go to the Transaction UI and see as the schedule value for the automatic capture is called first.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md b/docs/known-issues/en/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
index 673f30e1b..c23ac811f 100644
--- a/docs/known-issues/en/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
+++ b/docs/known-issues/en/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
@@ -3,8 +3,8 @@ title: "Elo's card brand transactions with ERedeRest are not respecting early ca
 id: 2OSpQyzDkiGioqcEmhuXpk
 status: PUBLISHED
 createdAt: 2023-05-08T20:29:59.412Z
-updatedAt: 2023-05-08T20:36:20.200Z
-publishedAt: 2023-05-08T20:36:20.200Z
+updatedAt: 2024-02-16T20:27:48.477Z
+publishedAt: 2024-02-16T20:27:48.477Z
 firstPublishedAt: 2023-05-08T20:29:59.878Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 350814
 ---
 
diff --git a/docs/known-issues/en/email-not-autofilling-for-new-buyers-after-logging-in.md b/docs/known-issues/en/email-not-autofilling-for-new-buyers-after-logging-in.md
new file mode 100644
index 000000000..137326599
--- /dev/null
+++ b/docs/known-issues/en/email-not-autofilling-for-new-buyers-after-logging-in.md
@@ -0,0 +1,46 @@
+---
+title: 'Email not auto-filling for new buyers after logging in'
+id: 2H6REXZGS6utlWmYKoPmGq
+status: PUBLISHED
+createdAt: 2023-10-17T16:22:21.667Z
+updatedAt: 2023-11-03T17:17:12.530Z
+publishedAt: 2023-11-03T17:17:12.530Z
+firstPublishedAt: 2023-10-17T16:22:22.650Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: email-not-autofilling-for-new-buyers-after-logging-in
+locale: en
+kiStatus: Fixed
+internalReference: 920634
+---
+
+## Summary
+
+
+When a new buyer logs in and proceeds to checkout, the email isn't automatically filled in requiring the customer to re-enter their email. This also happens using APIs and sending in headers with the buyer's cookies.
+
+
+##
+
+## Simulation
+
+
+
+- Log in with an email never used before in the store;
+- Add products to the cart;
+- Go to checkout;
+- The email won't be filled, and it should be typed again.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/email-not-autofilling-for-new-users-on-checkoutui.md b/docs/known-issues/en/email-not-autofilling-for-new-users-on-checkoutui.md
new file mode 100644
index 000000000..d714deec9
--- /dev/null
+++ b/docs/known-issues/en/email-not-autofilling-for-new-users-on-checkoutui.md
@@ -0,0 +1,60 @@
+---
+title: 'Email not auto-filling for new users on checkout-ui'
+id: 6XBghXwc93RBF53dCHr35y
+status: DRAFT
+createdAt: 2023-08-25T15:29:58.242Z
+updatedAt: 2023-08-25T16:47:25.505Z
+publishedAt: 
+firstPublishedAt: 
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: email-not-autofilling-for-new-users-on-checkoutui
+locale: en
+kiStatus: Backlog
+internalReference: 887949
+---
+
+## Summary
+
+
+When a new user enters a new email at the email step and proceeds to the next page, in the customer data component, the email isn't automatically filled in.
+This is because there's no registered user with that email. As a result, the loaded `orderForm` also contains an empty email field, causing it to remain blank and requiring the customer to re-enter their email.
+
+
+##
+
+## Simulation
+
+
+
+1. Navigate to the checkout page where customers enter their email.
+2. Put an email never used before in the store.
+3. Go to the client profile component.
+4. The email box will be empty, and then you have to type it again.
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
+ave to type it again.
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md b/docs/known-issues/en/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
new file mode 100644
index 000000000..70b9acc97
--- /dev/null
+++ b/docs/known-issues/en/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
@@ -0,0 +1,44 @@
+---
+title: 'Emails with sales roles are not allowed to impersonate using the B2B Organizations feature'
+id: 4HKDawkaTmzWcTZyrIhhuj
+status: PUBLISHED
+createdAt: 2023-09-29T18:15:08.398Z
+updatedAt: 2023-10-09T14:21:48.982Z
+publishedAt: 2023-10-09T14:21:48.982Z
+firstPublishedAt: 2023-09-29T18:15:09.110Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature
+locale: en
+kiStatus: Fixed
+internalReference: 910328
+---
+
+## Summary
+
+
+If emails have any associated sales roles, they are not allowed to impersonate using the B2B Organizations feature.
+
+
+##
+
+## Simulation
+
+
+
+- Create a user for an Organization and assign any sales role;
+- Access the website and try to impersonate any other user.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/encoding-error-in-apple-mail-app.md b/docs/known-issues/en/encoding-error-in-apple-mail-app.md
index 3dfba0339..dabc78a7e 100644
--- a/docs/known-issues/en/encoding-error-in-apple-mail-app.md
+++ b/docs/known-issues/en/encoding-error-in-apple-mail-app.md
@@ -29,7 +29,7 @@ Mount an email sending trigger that has a special character in the "Subject" of
 
 Result:
 
-![png](https://images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
+![png](//images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md b/docs/known-issues/en/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
new file mode 100644
index 000000000..7badcaca3
--- /dev/null
+++ b/docs/known-issues/en/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
@@ -0,0 +1,47 @@
+---
+title: 'Encoding issues for specific characters leads to unexpected product search'
+id: O0dM1H8ofJU0ahJRa6217
+status: PUBLISHED
+createdAt: 2024-04-24T22:09:33.395Z
+updatedAt: 2024-04-24T22:09:34.217Z
+publishedAt: 2024-04-24T22:09:34.217Z
+firstPublishedAt: 2024-04-24T22:09:34.217Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: encoding-issues-for-specific-characters-leads-to-unexpected-product-search
+locale: en
+kiStatus: Backlog
+internalReference: 1022550
+---
+
+## Summary
+
+
+An encoding issue may affect searches with special characters when they are indicated through the "query" parameter, leading to wrong search results.
+
+Searches without any filters may use the first path of the URL to indicate the search term, but searches with filters depend on the "query" parameter from the URL.
+
+
+##
+
+## Simulation
+
+
+This issue happens especially with the symbol "+".
+
+The search term "A+" works correctly while indicated via the URL path, but it'll behave as "A " while indicated through the "query" parameter.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index b36e9cb3e..c29a2c2da 100644
--- a/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -3,8 +3,8 @@ title: "Erro "Category XXX not found in browse node mapping for SKU's department
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
-updatedAt: 2022-11-25T21:56:57.092Z
-publishedAt: 2022-11-25T21:56:57.092Z
+updatedAt: 2024-02-16T20:29:13.856Z
+publishedAt: 2024-02-16T20:29:13.856Z
 firstPublishedAt: 2022-03-10T17:58:43.266Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 417639
 ---
 
diff --git a/docs/known-issues/en/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md b/docs/known-issues/en/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
new file mode 100644
index 000000000..f9a58aa2a
--- /dev/null
+++ b/docs/known-issues/en/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
@@ -0,0 +1,52 @@
+---
+title: 'Error approving skus that were rejected or reviewed by Offer Quality'
+id: 7fRMTxq7CFRkyZeK08AGIg
+status: PUBLISHED
+createdAt: 2023-11-23T13:46:30.453Z
+updatedAt: 2024-03-25T12:22:46.687Z
+publishedAt: 2024-03-25T12:22:46.687Z
+firstPublishedAt: 2023-11-23T13:46:31.370Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality
+locale: en
+kiStatus: Fixed
+internalReference: 940998
+---
+
+## Summary
+
+
+When a sku fails the Offer Quality rules created by the Marketplace, it goes directly to the "Review Tab" or "Rejected Tab" of Received Skus.
+
+However, when trying to approve the sku, an error message is returned: "Sorry, something went wrong in the Catalog. Please try again or contact VTEX if the problem persists."
+
+This happens because the Matcher module was not able to fill the product and sku information after sending the sku to these Tabs (you can check this using the APIs):
+ ![](https://vtexhelp.zendesk.com/attachments/token/0Dti3ak7twOpuVzvzntmPCGit/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+
+1. Create an optional or mandatory rule on Offer Quality;
+2. Wait for a sku to fail the rule and go to the Review/Rejected Tab;
+3. Try to approve the sku and get an error message;
+4. Check via API if the matches object is filled like the image above.
+
+
+##
+
+## Workaround
+
+
+Approve the sku via API passing the correct product and sku information manually.
+
+
+
+
+
diff --git a/docs/known-issues/en/error-cancelling-customer-credit-invoices.md b/docs/known-issues/en/error-cancelling-customer-credit-invoices.md
new file mode 100644
index 000000000..9afd24b52
--- /dev/null
+++ b/docs/known-issues/en/error-cancelling-customer-credit-invoices.md
@@ -0,0 +1,44 @@
+---
+title: 'Error cancelling Customer Credit invoices'
+id: 75nZNOHGYGBlAoTOjG6gs
+status: PUBLISHED
+createdAt: 2023-10-26T21:09:54.255Z
+updatedAt: 2024-05-29T17:25:32.948Z
+publishedAt: 2024-05-29T17:25:32.948Z
+firstPublishedAt: 2023-10-26T21:09:54.992Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-cancelling-customer-credit-invoices
+locale: en
+kiStatus: Backlog
+internalReference: 926563
+---
+
+## Summary
+
+
+In some cases invoices can't be cancelled, when running the DELETE API we get an error 500 with the below response:
+
+`"message": "An error has occurred."`
+
+
+##
+
+## Simulation
+
+
+We were not able to replicate this bug.
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index 9eaa1f42d..af19a06f6 100644
--- a/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -3,8 +3,8 @@ title: "Error "can't create search criteria! error: filter already exists:"brand
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
-updatedAt: 2022-11-25T22:11:53.363Z
-publishedAt: 2022-11-25T22:11:53.363Z
+updatedAt: 2024-02-16T20:23:47.779Z
+publishedAt: 2024-02-16T20:23:47.779Z
 firstPublishedAt: 2022-09-22T15:53:16.277Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 663698
 ---
 
diff --git a/docs/known-issues/en/error-closing-customer-credit-account.md b/docs/known-issues/en/error-closing-customer-credit-account.md
new file mode 100644
index 000000000..35410e092
--- /dev/null
+++ b/docs/known-issues/en/error-closing-customer-credit-account.md
@@ -0,0 +1,44 @@
+---
+title: 'Error closing Customer Credit account'
+id: zp8Bd8sIijJVNHws4nrkh
+status: PUBLISHED
+createdAt: 2023-09-20T21:38:28.253Z
+updatedAt: 2023-09-20T21:38:28.888Z
+publishedAt: 2023-09-20T21:38:28.888Z
+firstPublishedAt: 2023-09-20T21:38:28.888Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-closing-customer-credit-account
+locale: en
+kiStatus: Backlog
+internalReference: 904432
+---
+
+## Summary
+
+
+When main and sub accounts have the Customer Credit app installed the creation of a creditAccount happens in all of them. In this scenario there are cases where closing the creditAccount doesn't work, the folowing error appears:
+
+`Error while closing account.`
+
+
+##
+
+## Simulation
+
+
+We were not able to replicate or identify what causes this, in some accounts this issue does not occur.
+
+
+##
+
+## Workaround
+
+
+NA, what can be done is change the credit limit to zero so the payment method won't work for the registered email.
+
+
+
+
diff --git a/docs/known-issues/en/error-exporting-entity-with-too-many-documents.md b/docs/known-issues/en/error-exporting-entity-with-too-many-documents.md
new file mode 100644
index 000000000..670d04313
--- /dev/null
+++ b/docs/known-issues/en/error-exporting-entity-with-too-many-documents.md
@@ -0,0 +1,47 @@
+---
+title: 'Error exporting entity with too many documents'
+id: 1uLEk6e9z3011GaoJ4DNU0
+status: PUBLISHED
+createdAt: 2023-07-07T15:59:46.214Z
+updatedAt: 2023-07-07T15:59:46.899Z
+publishedAt: 2023-07-07T15:59:46.899Z
+firstPublishedAt: 2023-07-07T15:59:46.899Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-exporting-entity-with-too-many-documents
+locale: en
+kiStatus: Backlog
+internalReference: 857894
+---
+
+## Summary
+
+
+Exporting a large number of documents from an entity results in excessive processing, causing errors in the process queue and preventing the export of the document list.
+
+
+##
+
+## Simulation
+
+
+
+1. Access the Master Data CRM platform and navigate to the desired entity's form.
+2. Locate the "Export XLS" button within the interface and click on it.
+3. Locate and click on the "Export XLS" button.
+4. Initiate the export process by confirming the selection and starting the export.
+5. To monitor the progress of the export, navigate to the Applications tab within the platform.
+6. Look for the "Exports" button and click on it to view the list ongoing.
+7. Observe the export status, and check for any errors or issues encountered during the export process.
+
+
+
+##
+
+## Workaround
+
+
+A workaround for this issue is to utilize the scroll API.
+
diff --git a/docs/known-issues/en/error-exporting-large-amount-of-giftcards.md b/docs/known-issues/en/error-exporting-large-amount-of-giftcards.md
index 1e5bbfb55..51aa05147 100644
--- a/docs/known-issues/en/error-exporting-large-amount-of-giftcards.md
+++ b/docs/known-issues/en/error-exporting-large-amount-of-giftcards.md
@@ -1,10 +1,10 @@
 ---
 title: 'Error exporting large amount of Giftcards'
 id: 2EZ9XmZwYmcWdRxKbTNEBJ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-03-27T12:37:51.512Z
-updatedAt: 2022-11-25T22:09:09.150Z
-publishedAt: 2022-11-25T22:09:09.150Z
+updatedAt: 2023-07-03T17:14:32.962Z
+publishedAt: 
 firstPublishedAt: 2022-03-27T12:37:52.279Z
 contentType: knownIssue
 productTeam: Payments
@@ -35,3 +35,16 @@ N/A
 
 N/A
 
+imulation
+
+
+Try to make the export process with more than 50000 giftcards.
+
+
+##
+
+## Workaround
+
+
+Export in smaller amounts or smaller periods of time.
+
diff --git a/docs/known-issues/en/error-exporting-prices-with-metadata.md b/docs/known-issues/en/error-exporting-prices-with-metadata.md
new file mode 100644
index 000000000..f3ecc351c
--- /dev/null
+++ b/docs/known-issues/en/error-exporting-prices-with-metadata.md
@@ -0,0 +1,48 @@
+---
+title: 'Error exporting prices with metadata'
+id: 7nYPmatUXq57ZUsKHvfYJo
+status: PUBLISHED
+createdAt: 2023-07-12T11:49:06.370Z
+updatedAt: 2023-07-12T11:49:07.185Z
+publishedAt: 2023-07-12T11:49:07.185Z
+firstPublishedAt: 2023-07-12T11:49:07.185Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: error-exporting-prices-with-metadata
+locale: en
+kiStatus: Backlog
+internalReference: 860290
+---
+
+## Summary
+
+
+Sometimes when trying to export the prices with the metadata option enabled and without using filters, an error can occur. Checking the message on devTools something similar to "Polly broken circuit on service..." will appear.
+
+This error happens due to throttling on the catalog module when trying to retrieve the metadata for a lot of skus.
+
+
+##
+
+## Simulation
+
+
+
+1. Export the prices with metadata without using any filters;
+2. Sometimes an error message will appear;
+3. Check on inspect devtools if the message is similar to the one above.
+
+
+##
+
+## Workaround
+
+
+Use the filters to reduce the amount of skus on the spreadsheet and the catalog module return the data without problems.
+
+
+
+
+
diff --git a/docs/known-issues/en/error-in-checkout-error-message.md b/docs/known-issues/en/error-in-checkout-error-message.md
index 40e3d78c9..3cd9e4d1a 100644
--- a/docs/known-issues/en/error-in-checkout-error-message.md
+++ b/docs/known-issues/en/error-in-checkout-error-message.md
@@ -3,8 +3,8 @@ title: 'Error in checkout error message'
 id: 7jCEQoDRPvNwYCJmAt78im
 status: PUBLISHED
 createdAt: 2022-03-25T14:46:49.548Z
-updatedAt: 2022-11-25T22:07:18.470Z
-publishedAt: 2022-11-25T22:07:18.470Z
+updatedAt: 2024-02-16T20:27:24.748Z
+publishedAt: 2024-02-16T20:27:24.748Z
 firstPublishedAt: 2022-03-25T15:30:16.292Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: error-in-checkout-error-message
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 409895
 ---
 
diff --git a/docs/known-issues/en/error-in-custom-payments-creation.md b/docs/known-issues/en/error-in-custom-payments-creation.md
new file mode 100644
index 000000000..8baa12f50
--- /dev/null
+++ b/docs/known-issues/en/error-in-custom-payments-creation.md
@@ -0,0 +1,43 @@
+---
+title: 'Error in Custom Payments creation'
+id: 28jwG2jyT5FkSTbb85KlLX
+status: PUBLISHED
+createdAt: 2024-03-06T14:19:49.398Z
+updatedAt: 2024-07-01T18:49:29.959Z
+publishedAt: 2024-07-01T18:49:29.959Z
+firstPublishedAt: 2024-03-06T14:19:50.201Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-in-custom-payments-creation
+locale: en
+kiStatus: No Fix
+internalReference: 995110
+---
+
+## Summary
+
+
+Merchants can experience a bug when creating a Custom Payment, after filling everything and hit save the message `Custom payment was configured successfully!` appears but the creation actually failed (it doesn't appear in UI).
+
+
+##
+
+## Simulation
+
+
+Go to Custom Payments tab and configure any payment rule, you may experience the issue above.
+
+
+##
+
+## Workaround
+
+
+The only workaround would be retrying the creation until it appears in UI.
+
+
+
+
+
diff --git a/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
new file mode 100644
index 000000000..674396588
--- /dev/null
+++ b/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -0,0 +1,46 @@
+---
+title: 'Error in refund and capture operations with Payout Split - "Value in recipients * is different than operation value *."'
+id: 3Wo9ltN7Ju0ZqVLAQZcd7m
+status: PUBLISHED
+createdAt: 2023-08-23T13:57:20.424Z
+updatedAt: 2024-02-02T20:52:54.054Z
+publishedAt: 2024-02-02T20:52:54.054Z
+firstPublishedAt: 2023-08-23T13:57:21.389Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value
+locale: en
+kiStatus: Backlog
+internalReference: 698005
+---
+
+## Summary
+
+
+Due to rounding problems when recalculating the recipients of a transaction with Payout Split, either in the capture or in the refund, we receive the following exception from the gateway, since the sum of the recipient's value differs from the transaction value.
+
+
+    Vtex.Practices.ExceptionHandling.ValidationException: Value in recipients (xx.989999999999999999999999988) is different than operation value (xx.99). at Vtex.PaymentGateway.PaymentSplit.RecipientsBuilder.ValidateRecipientsValue(List`1 recipients, Decimal value)...
+
+
+
+##
+
+## Simulation
+
+
+Cannot simulate
+
+
+##
+
+## Workaround
+
+
+There is no workaround
+
+
+
+
diff --git a/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md
new file mode 100644
index 000000000..1339aa6da
--- /dev/null
+++ b/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -0,0 +1,46 @@
+---
+title: 'Error in refund - "Value cannot be null. Parameter name: value"'
+id: 6TZFYB9zb02oMoN5IJMxR3
+status: PUBLISHED
+createdAt: 2024-06-13T18:49:16.797Z
+updatedAt: 2024-06-13T18:49:17.823Z
+publishedAt: 2024-06-13T18:49:17.823Z
+firstPublishedAt: 2024-06-13T18:49:17.823Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-in-refund-value-cannot-be-null-parameter-name-value
+locale: en
+kiStatus: Backlog
+internalReference: 1049494
+---
+
+## Summary
+
+
+When trying to refund a transaction an error 500 can happen with the message:
+
+`Value cannot be null. Parameter name: value`
+
+ In this scenario the refund attempts are visible in the transaction logs with no response.
+
+
+##
+
+## Simulation
+
+
+We were not able to replicate.
+
+
+##
+
+## Workaround
+
+
+NA, merchant will need to request the refund directly with acquirer.
+
+
+
+
diff --git a/docs/known-issues/en/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md b/docs/known-issues/en/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
new file mode 100644
index 000000000..7cbec7f83
--- /dev/null
+++ b/docs/known-issues/en/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
@@ -0,0 +1,46 @@
+---
+title: 'Error in the cancellation process. ERedeRest and E-Rede V2 only allows cancelation when the returnCode is 359'
+id: 5lNLTmKp1xRfewx9OyhcNk
+status: PUBLISHED
+createdAt: 2023-01-26T18:29:35.310Z
+updatedAt: 2023-12-01T16:41:01.605Z
+publishedAt: 2023-12-01T16:41:01.605Z
+firstPublishedAt: 2023-01-26T18:29:36.467Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359
+locale: en
+kiStatus: Backlog
+internalReference: 740084
+---
+
+## Summary
+
+
+The legacy connectors, ERedeRest and E-Rede V2, initiate cancellations by sending a request to the provider and expect a "returnCode":"359" indicating a successful cancellation. Any other code is interpreted by our gateway as an undefined status, causing the transaction to get stuck in a cancelling state. Even though in some cases, the refund/cancellation request is successful. This led to repeated cancellation attempts, even when the cancellation had already been processed by the provider.
+
+
+##
+
+## Simulation
+
+
+It cannot be simulated as we depend on the provider's response.
+
+
+##
+
+## Workaround
+
+
+If the payment on the provider side is already canceled
+
+    {"returnCode":"355","returnMessage":"Transaction already cancelled."}
+
+The product support team has the option to utilize an internal API, '`force-cancel-status`', to update the payment and transaction status to 'canceled.'
+
+
+
+
diff --git a/docs/known-issues/en/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md b/docs/known-issues/en/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
new file mode 100644
index 000000000..26e43ec84
--- /dev/null
+++ b/docs/known-issues/en/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
@@ -0,0 +1,58 @@
+---
+title: 'Error in viewing the orders UI after requesting the invoice via App'
+id: 1yrb25L1Skj3sRRWyiFDSA
+status: PUBLISHED
+createdAt: 2024-07-24T14:24:29.799Z
+updatedAt: 2024-07-24T14:24:30.583Z
+publishedAt: 2024-07-24T14:24:30.583Z
+firstPublishedAt: 2024-07-24T14:24:30.583Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app
+locale: en
+kiStatus: Backlog
+internalReference: 1070299
+---
+
+## Summary
+
+
+When we execute a `change V2` by removing or adding an item to an order, we create a change in the list of items in the order, which can increase or decrease the number of indexes in the list of items in the json. This change, in turn, may not be consumed by all the apps or databases involved in handling the order, such as the invoice notifier app;
+
+As a result, by requesting the invoice via the invoice notifier app before having carried out an action to remove or add an item, the user ends up causing a breakage scenario in the UI, as the `invoice notifier app` starts to return an error due to having more or fewer items than expected by the UI, resulting in a “null reference” error which prevents the order from being displayed in the UI;
+
+
+##
+
+## Simulation
+
+
+
+**NOTE**: To simulate this scenario, you must have configured the `invoice notifier app` and also be using the `Change V2` flow;
+
+
+- In an order with more than one item, go to the handling status;
+
+
+- From the UI, click on the “Request invoice” option (Notify your ERP).
+
+
+- Before the invoice is returned by the ERP, make a change to the order by removing or adding any item to the order;
+
+
+- Wait until the ERP sends the invoice to the Orders system, then access the order again from the Orders UI, at which point the UI will return an error message and the order cannot be displayed;
+
+
+##
+
+## Workaround
+
+
+Make the invoice request via invoice-notifier only after performing the change of order items.
+
+
+
+
+
diff --git a/docs/known-issues/en/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md b/docs/known-issues/en/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
new file mode 100644
index 000000000..9d3ed3e65
--- /dev/null
+++ b/docs/known-issues/en/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
@@ -0,0 +1,47 @@
+---
+title: 'Error (LeituraDeDadosDoAdministrador) when trying to access catalog pages on admin'
+id: 40EruMGkO9DVEwb7RZ5nxF
+status: PUBLISHED
+createdAt: 2024-06-25T18:30:24.815Z
+updatedAt: 2024-06-25T18:30:25.929Z
+publishedAt: 2024-06-25T18:30:25.929Z
+firstPublishedAt: 2024-06-25T18:30:25.929Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin
+locale: en
+kiStatus: Backlog
+internalReference: 1055578
+---
+
+## Summary
+
+
+Some users even with the right role receive an error "The user xx does not have access to the requested page (LeituraDeDadosDoAdministrador)" when accessing catalog pages on admin.
+
+This usually happens with new users created in PII accounts.
+
+
+##
+
+## Simulation
+
+
+
+1. Using a PII account create a new user and give them the correct access to catalog modules.
+2. Check if the user can actually access these pages.
+
+
+##
+
+## Workaround
+
+
+Create a ticket to VTEX.
+
+
+
+
+
diff --git a/docs/known-issues/en/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md b/docs/known-issues/en/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
index cd6fc6f79..398dcac06 100644
--- a/docs/known-issues/en/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
+++ b/docs/known-issues/en/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
@@ -3,8 +3,8 @@ title: 'Error message on offers management does not update after sku is binded o
 id: 5tMKDMsFTZlXQrkVM4WeJD
 status: PUBLISHED
 createdAt: 2022-12-08T14:02:22.948Z
-updatedAt: 2022-12-08T14:03:27.764Z
-publishedAt: 2022-12-08T14:03:27.764Z
+updatedAt: 2024-02-16T20:24:16.785Z
+publishedAt: 2024-02-16T20:24:16.785Z
 firstPublishedAt: 2022-12-08T14:02:23.384Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 712956
 ---
 
diff --git a/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
new file mode 100644
index 000000000..6c7a1cd6c
--- /dev/null
+++ b/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -0,0 +1,46 @@
+---
+title: 'Error occurs when attempting to perform a search using the "All" field in VTEX CRM'
+id: 1OKMTJuUZx6mnDmYW3MBjP
+status: PUBLISHED
+createdAt: 2023-10-25T18:46:48.120Z
+updatedAt: 2023-10-25T18:46:48.731Z
+publishedAt: 2023-10-25T18:46:48.731Z
+firstPublishedAt: 2023-10-25T18:46:48.731Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm
+locale: en
+kiStatus: Backlog
+internalReference: 925679
+---
+
+## Summary
+
+
+This case happens with entities containing a large number of fields and millions of records in an entity. The problem arises due to the search engine using the “All” field, which sends individual requests for each searchable field of the entity and multiplies the request load for each document.
+
+
+##
+
+## Simulation
+
+
+
+1. Access `https://.vtexcrm.com.br/`.
+2. Navigate to a view that represents an entity with millions of records.
+3. Initiate a search using the "All" field.
+ ![](https://vtexhelp.zendesk.com/attachments/token/NGWvp5vsTzd31GA07N6vp0Wev/?name=Captura+de+Tela+2023-10-25+a%CC%80s+15.42.35.png)
+4. Observe the system's response and check if it returns an error or experiences significant performance issues.
+ ![](https://vtexhelp.zendesk.com/attachments/token/aFWGBmUtDtl9ppgmMNOkDX8Fu/?name=Captura+de+Tela+2023-10-25+a%CC%80s+15.40.50.png)
+5. Repeat the search with a specific searchable field to confirm if the issue is related to the "All" field's search mechanism.
+
+
+##
+
+## Workaround
+
+
+Search with a specific searchable field.
+
diff --git a/docs/known-issues/en/error-on-duplicate-payment-method.md b/docs/known-issues/en/error-on-duplicate-payment-method.md
new file mode 100644
index 000000000..f4a680161
--- /dev/null
+++ b/docs/known-issues/en/error-on-duplicate-payment-method.md
@@ -0,0 +1,50 @@
+---
+title: 'Error on duplicate payment method'
+id: 1wdiEae6sehlnTDnanWT7n
+status: PUBLISHED
+createdAt: 2023-11-02T12:23:14.027Z
+updatedAt: 2023-11-02T12:23:15.109Z
+publishedAt: 2023-11-02T12:23:15.109Z
+firstPublishedAt: 2023-11-02T12:23:15.109Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-on-duplicate-payment-method
+locale: en
+kiStatus: Backlog
+internalReference: 929428
+---
+
+## Summary
+
+
+When duplicating a payment method that does not have installments, the operator receives the following message on the screen, "The current payment system does not allow installment options". This happens because when the body of the creation request in the new rule is created, some fields are inserted by default, including installmentOptions, but this field does not exist for cash payments such as debit and boleto(Brazil).
+
+
+##
+
+## Simulation
+
+
+
+1. Go to the payment terms screen
+2. Select a payment method that does not have installments.
+3. Click the button to duplicate the rule.
+4. The following error message will be displayed on your screen: "The current payment system does not allow installment options"
+
+
+##
+
+## Workaround
+
+
+We have two ways to get around this problem:
+
+1. Create another one with the same settings as the one you want to duplicate;
+2. Create the rule via API, `https://.myvtex.com/api/payments/pvt/rules/`, removing the installmentOptions field from the body.
+
+
+
+
+
diff --git a/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md b/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
index abc34ab47..3db5a8a4b 100644
--- a/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
+++ b/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
@@ -22,7 +22,7 @@ VTEX stores can become each other's [sellers](https://help.vtex.com/en/tutorial/
 
 This is because products that are sold by both the marketplace and its sellers are not recognized by the system when they are sent. It is only possible to send products that are sold by only one of the stores.
 
-![arquitetura circular](https://images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/9e024cb7fedda9e1c4fda6566c598be2/arquitetura_circular.JPG)
+![arquitetura circular](//images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/9e024cb7fedda9e1c4fda6566c598be2/arquitetura_circular.JPG)
 
 
 ## Simulation
diff --git a/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
new file mode 100644
index 000000000..305b1c166
--- /dev/null
+++ b/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -0,0 +1,47 @@
+---
+title: 'Error "Something went wrong. Please try again." when adding images via Site Editor'
+id: r3QVP1kp8HApP83bOi6t9
+status: PUBLISHED
+createdAt: 2023-11-07T22:33:02.296Z
+updatedAt: 2023-11-07T22:34:52.005Z
+publishedAt: 2023-11-07T22:34:52.005Z
+firstPublishedAt: 2023-11-07T22:33:03.046Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: error-something-went-wrong-please-try-again-when-adding-images-via-site-editor
+locale: en
+kiStatus: Backlog
+internalReference: 932126
+---
+
+## Summary
+
+
+When adding images via Site Editor, the message "`Something went wrong. Please try again.`" can occasionally occur.
+This is due to the number of images per block. At the moment, we don't have an exact number of images that causes this issue, but we have noticed this behavior above 20 images in the same block.
+
+
+##
+
+## Simulation
+
+
+
+- Access the CMS Site Editor (for example https://my-account-here.myvtex.com/admin/cms/site-editor);
+- Select the block with the new images to be added;
+- When the addition is saved, the message "`Something went wrong. Please try again.`" will appear in the bottom right-hand corner:
+ ![](https://vtexhelp.zendesk.com/attachments/token/97C4wewa6iz3f7bsmHtdnXu1H/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+You can add the images directly to the theme, or break them into blocks with flex layout (ref https://developers.vtex.com/docs/apps/vtex.flex-layout).
+
+
+
+
diff --git a/docs/known-issues/en/error-sww-on-product-pdp.md b/docs/known-issues/en/error-sww-on-product-pdp.md
index 93d86f8f9..1d1bd9dbc 100644
--- a/docs/known-issues/en/error-sww-on-product-pdp.md
+++ b/docs/known-issues/en/error-sww-on-product-pdp.md
@@ -3,8 +3,8 @@ title: 'Error SWW on product PDP'
 id: 3DhuWocQwqiWxuAffdwYkg
 status: PUBLISHED
 createdAt: 2023-01-23T12:38:30.711Z
-updatedAt: 2023-01-23T12:38:31.382Z
-publishedAt: 2023-01-23T12:38:31.382Z
+updatedAt: 2023-09-19T19:15:13.868Z
+publishedAt: 2023-09-19T19:15:13.868Z
 firstPublishedAt: 2023-01-23T12:38:31.382Z
 contentType: knownIssue
 productTeam: Catalog
@@ -19,7 +19,8 @@ internalReference: 738108
 ## Summary
 
 
-In some occasions, when opening the product PDP through the admin page (or the final domain) an error Something Went Wrong appears on the screen.
+On some occasions, when opening the product PDP through the admin page (or the final domain) an error Something Went Wrong appears on the screen.
+This behavior can happen due to previous category movements on the category tree causing a wrong validation of the product/sku specifications on the catalog system.
 
 
 ##
@@ -27,9 +28,8 @@ In some occasions, when opening the product PDP through the admin page (or the f
 ## Simulation
 
 
-This behavior can happen due to previous category movements on the category tree causing a wrong validation of the product/sku specifications on the catalog system.
-
-The real error message behind the SWW error (that can be checked via internal logs) is "Nome da variação do produto não encontrado."
+Open the product PDP link
+Get a Something Went Wrong on the front
 
 
 ##
@@ -38,6 +38,10 @@ The real error message behind the SWW error (that can be checked via internal lo
 
 
 In order to correct this behavior, the specification causing the error must not have a value on the product.
+OR
+Any SKU specification must be filled in because it may be erroneously considered mandatory
+(check if there is an SKU that has an unfilled specification, but the other SKUs of the product are filled)
+
 
 
 
diff --git a/docs/known-issues/en/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md b/docs/known-issues/en/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
index 8054793b8..d304e35fe 100644
--- a/docs/known-issues/en/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
+++ b/docs/known-issues/en/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
@@ -3,8 +3,8 @@ title: 'Error triggered by overridden TOKEN in legacy PayPal connector for pendi
 id: 5GrnhD8fwte7qu50Az8r3Y
 status: PUBLISHED
 createdAt: 2023-06-13T22:35:16.397Z
-updatedAt: 2023-06-13T22:38:27.909Z
-publishedAt: 2023-06-13T22:38:27.909Z
+updatedAt: 2024-07-01T18:47:54.680Z
+publishedAt: 2024-07-01T18:47:54.680Z
 firstPublishedAt: 2023-06-13T22:35:16.955Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 308214
 ---
 
diff --git a/docs/known-issues/en/error-when-changing-an-index-if-the-fields-are-identical.md b/docs/known-issues/en/error-when-changing-an-index-if-the-fields-are-identical.md
new file mode 100644
index 000000000..0d218a79d
--- /dev/null
+++ b/docs/known-issues/en/error-when-changing-an-index-if-the-fields-are-identical.md
@@ -0,0 +1,43 @@
+---
+title: 'Error when changing an index if the fields are identical.'
+id: Ckic7QH3kKyW3IA92A3Cm
+status: PUBLISHED
+createdAt: 2023-07-03T18:48:49.070Z
+updatedAt: 2023-07-03T18:48:49.971Z
+publishedAt: 2023-07-03T18:48:49.971Z
+firstPublishedAt: 2023-07-03T18:48:49.971Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-when-changing-an-index-if-the-fields-are-identical
+locale: en
+kiStatus: Backlog
+internalReference: 854634
+---
+
+## Summary
+
+
+An update of a schema index can result in a 500 Internal Server error when there are no changes to be made, this means that the field values are identical to the current ones.
+Performing a GET request on the API to check the indices reveals that no update is required, as the index is identical to the body provided in the PUT request.
+
+
+##
+
+## Simulation
+
+
+
+1. Send a PUT request to update a schema index through the API, providing the necessary payload in the request body.
+2. Verify the response from the API and observe if it returns a **500 Internal Server Error**.
+3. Perform a subsequent GET request on the API to retrieve the schema indices and compare them to the body provided in the PUT request.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/error-when-changing-delivery-type-when-seller-has-recursion.md b/docs/known-issues/en/error-when-changing-delivery-type-when-seller-has-recursion.md
index 9446afb3d..93788e9e6 100644
--- a/docs/known-issues/en/error-when-changing-delivery-type-when-seller-has-recursion.md
+++ b/docs/known-issues/en/error-when-changing-delivery-type-when-seller-has-recursion.md
@@ -3,8 +3,8 @@ title: 'Error when changing delivery type when seller has recursion'
 id: 7JLnqVWHz94sQZKMOGUkKC
 status: PUBLISHED
 createdAt: 2022-06-14T14:07:38.881Z
-updatedAt: 2022-11-25T21:52:59.031Z
-publishedAt: 2022-11-25T21:52:59.031Z
+updatedAt: 2024-02-16T20:24:13.311Z
+publishedAt: 2024-02-16T20:24:13.311Z
 firstPublishedAt: 2022-06-14T14:07:39.358Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: error-when-changing-delivery-type-when-seller-has-recursion
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 597915
 ---
 
diff --git a/docs/known-issues/en/error-when-publishing-dynamic-storage-data-entity.md b/docs/known-issues/en/error-when-publishing-dynamic-storage-data-entity.md
new file mode 100644
index 000000000..344482ae3
--- /dev/null
+++ b/docs/known-issues/en/error-when-publishing-dynamic-storage-data-entity.md
@@ -0,0 +1,58 @@
+---
+title: 'Error when publishing dynamic storage data entity'
+id: 1yNh5CV41vrrrU5F7Vj2tG
+status: PUBLISHED
+createdAt: 2023-10-04T16:33:03.051Z
+updatedAt: 2023-10-04T16:37:00.614Z
+publishedAt: 2023-10-04T16:37:00.614Z
+firstPublishedAt: 2023-10-04T16:33:03.847Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-when-publishing-dynamic-storage-data-entity
+locale: en
+kiStatus: Backlog
+internalReference: 666357
+---
+
+## Summary
+
+
+When the store creates or updates a Data Entity and then tries to publish it, the following error may occurs:
+
+
+    Unexpected error. Please try again or contact customer support.
+
+
+
+##
+
+## Simulation
+
+
+
+- Access the Dynamic Storage system / Data Structure application (https://my-account-here.ds.vtexcrm.com.br);
+- Access the Data Entities tab:
+ ![](https://vtexhelp.zendesk.com/attachments/token/65UPKYKl3vuaeweF46K91bpI5/?name=image.png)
+
+- Click on the disk icon to publish the Data Entity that was created or updated:
+ ![](https://vtexhelp.zendesk.com/attachments/token/C1nUZnpG8lmDWOL8wrXRBiGj0/?name=image.png)
+
+- Then the following message will be shown:
+ ![](https://vtexhelp.zendesk.com/attachments/token/DFKVanOk3noBMaN8aBd6CQssp/?name=image.png)
+
+    Unexpected error. Please try again or contact customer support.
+
+
+
+##
+
+## Workaround
+
+
+For these scenarios, a workaround is to open a ticket for VTEX, so that we can validate a possible update of this account's cluster.
+
+
+
+
diff --git a/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
index 565eabfaa..9c960e92e 100644
--- a/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
@@ -29,7 +29,7 @@ The error authorization message can change from `node`to `react` according to th
 1.  Install the VTEX CLI (Toolbelt)
 2.  Navigate towards the app's directory
 3.  Execute the "vtex-link" command through the terminal.
-4.  ![image (8)](https://images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
+4.  ![image (8)](//images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/error-when-settling-transaction-with-2-cards-mercadopagov1.md b/docs/known-issues/en/error-when-settling-transaction-with-2-cards-mercadopagov1.md
index 8e9235433..39abba534 100644
--- a/docs/known-issues/en/error-when-settling-transaction-with-2-cards-mercadopagov1.md
+++ b/docs/known-issues/en/error-when-settling-transaction-with-2-cards-mercadopagov1.md
@@ -3,8 +3,8 @@ title: 'Error when settling transaction with 2 cards - MercadoPagoV1'
 id: 1WFFLHywLePfl5v5IMhili
 status: PUBLISHED
 createdAt: 2022-03-03T21:30:42.237Z
-updatedAt: 2022-11-25T22:05:14.074Z
-publishedAt: 2022-11-25T22:05:14.074Z
+updatedAt: 2024-02-16T20:27:28.600Z
+publishedAt: 2024-02-16T20:27:28.600Z
 firstPublishedAt: 2022-03-03T21:30:42.610Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: error-when-settling-transaction-with-2-cards-mercadopagov1
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 395943
 ---
 
diff --git a/docs/known-issues/en/error-when-trying-to-publish-or-link-an-app.md b/docs/known-issues/en/error-when-trying-to-publish-or-link-an-app.md
new file mode 100644
index 000000000..9eda4231a
--- /dev/null
+++ b/docs/known-issues/en/error-when-trying-to-publish-or-link-an-app.md
@@ -0,0 +1,46 @@
+---
+title: 'Error when trying to publish or link an app'
+id: 2WPukfSHWzzIUjIzMJaAEK
+status: PUBLISHED
+createdAt: 2024-06-27T15:39:00.583Z
+updatedAt: 2024-06-27T19:46:21.021Z
+publishedAt: 2024-06-27T19:46:21.021Z
+firstPublishedAt: 2024-06-27T15:39:01.543Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: error-when-trying-to-publish-or-link-an-app
+locale: en
+kiStatus: Backlog
+internalReference: 1056882
+---
+
+## Summary
+
+
+Our team investigated that this is normally associated with a huge app size being developed. This happens because the builder hub bursts its memory due to many files on the app. Delays in linking the app may also be associated with this issue
+
+
+##
+
+## Simulation
+
+
+Try using `vtex link` on an app with a huge size or a lot of files. You may receive the following errors:
+
+    11:51:13.298 - error: Workerpool Worker terminated Unexpectedly exitCode: `null` signalCode: `SIGABRT` workerpool.script: `/usr/local/data/service/src/node/utils/workers/worker.js` spawnArgs: `/usr/local/bin/node,/usr/local/data/service/src/node/utils/workers/worker.js` spawnfile: `/usr/local/bin/node` stdout: `null` stderr: `null` vtex.builder-hub@0.299.0 11:51:13.299 - error: App build failed with message: Workerpool Worker terminated Unexpectedly exitCode: `null` signalCode: `SIGABRT` workerpool.script: `/usr/local/data/service/src/node/utils/workers/worker.js` spawnArgs: `/usr/local/bin/node,/usr/local/data/service/src/node/utils/workers/worker.js` spawnfile: `/usr/local/bin/node` stdout: `null` stderr: `null`
+
+    13:30:05.456 - error: App ended with exit code 15. Will restart in 10s. service-node@6.38.3
+
+
+
+##
+
+## Workaround
+
+
+Analyze the size of the app and its files, if it is necessary try to divide the app into smaller apps so the size will be reduced.
+
+
+
diff --git a/docs/known-issues/en/event-inconsistency.md b/docs/known-issues/en/event-inconsistency.md
index d985c5a30..363049a54 100644
--- a/docs/known-issues/en/event-inconsistency.md
+++ b/docs/known-issues/en/event-inconsistency.md
@@ -1,10 +1,10 @@
 ---
 title: 'Event Inconsistency'
 id: 2YnhehJXuJcsy3f3Rezn6X
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-06-20T23:00:31.430Z
-updatedAt: 2022-06-27T12:52:29.346Z
-publishedAt: 2022-06-27T12:52:28.556Z
+updatedAt: 2024-05-23T12:45:46.343Z
+publishedAt: 2024-05-23T12:45:46.343Z
 firstPublishedAt: 2022-06-20T23:00:31.899Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: event-inconsistency
 locale: en
-kiStatus: Scheduled
+kiStatus: Fixed
 internalReference: 267299
 ---
 
@@ -20,9 +20,7 @@ internalReference: 267299
 
 
 
-
-
-When the user places an order in checkout, a new order flow is started. From this moment on, the VTEX gateway is consulted when the following order statuses are identified: "Payment pending" and "Verifying invoice". In the "Payment Pending" status, a payment notification is expected to be sent to the Orders module. During this period, some problems with event processing may occur.Although there is not only one root cause directly related to the processing event issue, any other internal or external issue linked to the notification system can cause the order flow to be blocked in "pending payment" status.
+When the user places an order in checkout, a new order flow is started. From this moment on, the VTEX gateway is consulted when the following order statuses are identified: "Payment pending" and "Verifying invoice". In the "Payment Pending" status, a payment notification is expected to be sent to the Orders module. During this period, some problems with event processing may occur. Although there is not only one root cause directly related to the processing event issue, any other internal or external issue linked to the notification system can cause the order flow to be blocked in "pending payment" status.
 
 The message queue provides an asynchronous communication protocol, in which events are placed in a queue to be consumed at a predetermined time in the future. Thus, we've already mapped some scenarios where there is an inconsistency in this flow to categorize them and solve them one by one.
 
@@ -31,25 +29,25 @@ The message queue provides an asynchronous communication protocol, in which even
 - Event stuck and not processed;
 - Processing errors that may cause database inconsistencies.
 
-This KI refers explicitly to the scenarios mentioned above and is not intended to exhaust all possibilities of event processing problems that may occur. New root causes or related issues, such as bad responses from the provider (which happens regularly), can lead to situations where the order is stuck.Each case needs to be investigated individually in order to determine the root cause of the problem.
+This KI refers explicitly to the scenarios mentioned above and is not intended to exhaust all possibilities of event processing problems that may occur. New root causes or related issues, such as bad responses from the provider (which happens regularly), can lead to situations where the order is stuck. Each case needs to be investigated individually to determine the root cause of the problem.
 
 
+##
 
 ## Simulation
 
 
 
-
-
 There's no way to simulate this behavior.
 
 
+##
 
 ## Workaround
 
 
+Please contact our support team to manually reprocess the event.
 
 
 
-Please contact our support team to manually reprocess the event.
 
diff --git a/docs/known-issues/en/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md b/docs/known-issues/en/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
index 2c42772dd..19e913417 100644
--- a/docs/known-issues/en/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
+++ b/docs/known-issues/en/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
@@ -1,10 +1,10 @@
 ---
-title: 'ew UI does not suggest the correct Item to be returned once the order has a change'
+title: 'New UI does not suggest the correct Item to be returned once the order has a change'
 id: 7hjZaUZ1GNiGjMnSKe0pZu
 status: PUBLISHED
 createdAt: 2023-01-18T17:05:53.889Z
-updatedAt: 2023-01-18T17:05:54.590Z
-publishedAt: 2023-01-18T17:05:54.590Z
+updatedAt: 2024-05-28T18:33:17.977Z
+publishedAt: 2024-05-28T18:33:17.977Z
 firstPublishedAt: 2023-01-18T17:05:54.590Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/en/exclude-products-from-collection-not-working.md b/docs/known-issues/en/exclude-products-from-collection-not-working.md
new file mode 100644
index 000000000..9d214c5bb
--- /dev/null
+++ b/docs/known-issues/en/exclude-products-from-collection-not-working.md
@@ -0,0 +1,48 @@
+---
+title: 'Exclude products from collection not working.'
+id: 102Z3QRDo07OM6IPJCDlsY
+status: PUBLISHED
+createdAt: 2023-10-20T16:30:13.646Z
+updatedAt: 2023-10-20T16:30:14.840Z
+publishedAt: 2023-10-20T16:30:14.840Z
+firstPublishedAt: 2023-10-20T16:30:14.840Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: exclude-products-from-collection-not-working
+locale: en
+kiStatus: Backlog
+internalReference: 923016
+---
+
+## Summary
+
+
+The account can create collections using the legacy version and add entire collections and brands.
+
+However, when trying to exclude some products of these collection or brands using the "exclusao" subcollection nothing happens. Despite no error messages appear, the skus continue to be on the collection.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a collection and add a category on the "Inclusão" subcollection group.
+2. Create a "exclusão" subcollection group with at leat one product (all skus) on the add skus part.
+3. Check that the sku continues to be on the collection;
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/expired-temporary-redirects-not-pointing-back-to-old-route.md b/docs/known-issues/en/expired-temporary-redirects-not-pointing-back-to-old-route.md
new file mode 100644
index 000000000..8c1c6a621
--- /dev/null
+++ b/docs/known-issues/en/expired-temporary-redirects-not-pointing-back-to-old-route.md
@@ -0,0 +1,47 @@
+---
+title: 'Expired temporary redirects not pointing back to old route'
+id: 1kI87EueEtHIyfZ4KmUJSF
+status: PUBLISHED
+createdAt: 2023-09-12T14:41:09.843Z
+updatedAt: 2023-09-12T14:41:11.758Z
+publishedAt: 2023-09-12T14:41:11.758Z
+firstPublishedAt: 2023-09-12T14:41:11.758Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: expired-temporary-redirects-not-pointing-back-to-old-route
+locale: en
+kiStatus: Backlog
+internalReference: 898062
+---
+
+## Summary
+
+
+
+When a redirect route is created, the internal route is removed, but, when the redirect expires the route doesn't come back
+
+
+##
+
+## Simulation
+
+
+
+
+- Create a temporary redirect
+- Check and this will redirect properly
+- After the expiration date, check it again
+- The original path/route will not load properly
+
+
+##
+
+## Workaround
+
+
+The route will only work again if you create it once again in the rewriter
+
+
+
diff --git a/docs/known-issues/en/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md b/docs/known-issues/en/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
new file mode 100644
index 000000000..a863722ca
--- /dev/null
+++ b/docs/known-issues/en/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
@@ -0,0 +1,42 @@
+---
+title: 'Explained search interface overlapping long texts between different areas or products'
+id: 5BMYpoif30DAOjPOVHMDfS
+status: PUBLISHED
+createdAt: 2023-09-21T00:25:00.402Z
+updatedAt: 2023-09-21T00:25:00.874Z
+publishedAt: 2023-09-21T00:25:00.874Z
+firstPublishedAt: 2023-09-21T00:25:00.874Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: explained-search-interface-overlapping-long-texts-between-different-areas-or-products
+locale: en
+kiStatus: Backlog
+internalReference: 904482
+---
+
+## Summary
+
+
+The explained search admin page has problems with the merchandising rules and searchable field areas when a search or a product has too much information there, overlapping texts between different sections/products.
+
+
+##
+
+## Simulation
+
+
+Register a good number of words in a field that is searchable.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md b/docs/known-issues/en/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
new file mode 100644
index 000000000..0ef893258
--- /dev/null
+++ b/docs/known-issues/en/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
@@ -0,0 +1,38 @@
+---
+title: 'Export lots of products/SKUs takes long time and sometimes the request can not completed'
+id: 4MBgn0t3jm698ZkkcF1o5G
+status: PUBLISHED
+createdAt: 2022-01-21T14:33:34.881Z
+updatedAt: 2024-02-16T20:25:42.392Z
+publishedAt: 2024-02-16T20:25:42.392Z
+firstPublishedAt: 2024-01-23T15:58:51.944Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed
+locale: en
+kiStatus: No Fix
+internalReference: 284386
+---
+
+## Summary
+
+
+Export lots of products/SKUs takes long time and sometimes the request can not completed. This problem also affects other catalog exports.
+
+
+##
+
+## Simulation
+
+
+Try to export more than 100k products.
+
+##
+
+## Workaround
+
+
+Use the filter to filter the products in groups of less than 10000 products.
+
diff --git a/docs/known-issues/en/export-redirects-not-working-as-intended.md b/docs/known-issues/en/export-redirects-not-working-as-intended.md
index dacd3c00f..a92cf654b 100644
--- a/docs/known-issues/en/export-redirects-not-working-as-intended.md
+++ b/docs/known-issues/en/export-redirects-not-working-as-intended.md
@@ -3,13 +3,13 @@ title: 'Export Redirects not working as intended'
 id: 5WoiJDQCSMDCwCn1auNwC4
 status: PUBLISHED
 createdAt: 2022-04-05T12:53:18.824Z
-updatedAt: 2022-11-25T21:54:34.008Z
-publishedAt: 2022-11-25T21:54:34.008Z
+updatedAt: 2024-01-29T18:40:08.833Z
+publishedAt: 2024-01-29T18:40:08.833Z
 firstPublishedAt: 2022-04-05T12:53:19.875Z
 contentType: knownIssue
-productTeam: CMS
+productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
-tag: CMS
+tag: Store Framework
 slug: export-redirects-not-working-as-intended
 locale: en
 kiStatus: Backlog
@@ -20,15 +20,31 @@ internalReference: 537962
 
 
 
-When you try to export the redirect, either though the terminal or through the page on the CMS it brings different sizes of file, with possible different results inside, this isn't the expected behavior since there's no changes done on the redirects that could explain the differences.
+When you try to export the redirect, either through the terminal or through the page on the CMS it brings different sizes of files, with possible different results inside, this isn't the expected behavior since there are no changes done on the redirects that could explain the differences.
 
 
 
+##
+
 ## Simulation
 
 
 
+(Terminal) Follow the steps on the documentation: https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-managing-url-redirects
+
+Check the files returned and you can see in some cases the difference between the two files extracted.
+
+(Admin UI) Go the the admin > CMS > Redirects change between the pages on the pagination and click on export you will see the differences in the files that are returned.
+
+
+##
+
 ## Workaround
 
 
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/en/export-the-csv-in-the-sales-performance-module.md b/docs/known-issues/en/export-the-csv-in-the-sales-performance-module.md
index b34249c6d..2a50cefb9 100644
--- a/docs/known-issues/en/export-the-csv-in-the-sales-performance-module.md
+++ b/docs/known-issues/en/export-the-csv-in-the-sales-performance-module.md
@@ -3,13 +3,13 @@ title: 'Export the CSV in the sales performance module'
 id: 7qnlFfnImq7N6Nrz0xIT8L
 status: PUBLISHED
 createdAt: 2023-05-11T13:42:36.411Z
-updatedAt: 2023-05-11T13:42:37.027Z
-publishedAt: 2023-05-11T13:42:37.027Z
+updatedAt: 2023-09-13T20:08:40.788Z
+publishedAt: 2023-09-13T20:08:40.788Z
 firstPublishedAt: 2023-05-11T13:42:37.027Z
 contentType: knownIssue
-productTeam: Admin
+productTeam: Analytics
 author: 2mXZkbi0oi061KicTExNjo
-tag: Admin
+tag: Analytics
 slug: export-the-csv-in-the-sales-performance-module
 locale: en
 kiStatus: Backlog
diff --git a/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
new file mode 100644
index 000000000..cc2cc1ff1
--- /dev/null
+++ b/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -0,0 +1,48 @@
+---
+title: "Exporting SKU images for accounts starting with 'h','t' or 'p' get this character cut in the "Image URL" rows."
+id: 1IZdnE8IGwkBlbcFhjLrzn
+status: PUBLISHED
+createdAt: 2023-10-13T15:20:49.703Z
+updatedAt: 2023-10-13T15:20:50.483Z
+publishedAt: 2023-10-13T15:20:50.483Z
+firstPublishedAt: 2023-10-13T15:20:50.483Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows
+locale: en
+kiStatus: Backlog
+internalReference: 919199
+---
+
+## Summary
+
+
+The SKU image report, /admin/Site/ProdutoImagemExportacao.aspx, for accountnames that start with "h", "t" or "p", such as "testaccount", wil lshow a missing character in the export sheeto for the imageURL row.
+
+
+##
+
+## Simulation
+
+
+1 - for an account that starts with the mentioned initial characters, go to /admin/Site/ProdutoImagemExportacao.aspx and export a sheet for any sku that has at least 1 image.
+2 - open the exported sheet and check the column "UrlImagem": it'll be without the initial character
+
+For instance, if the account is named "testaccount":
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/3VxPtxFSDjU1obEtgqkS16BXM/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+Create a subaccount starting with another character (for instance, "mytestaccount") and access the export UI using this subaccount. The export then  will show the whole URL string without any incorrect trims.
+
+
+
+
+
diff --git a/docs/known-issues/en/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md b/docs/known-issues/en/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
new file mode 100644
index 000000000..15eb3d5f8
--- /dev/null
+++ b/docs/known-issues/en/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
@@ -0,0 +1,50 @@
+---
+title: '[Facebook] Today Facebook looks at sellingPrice and listPrice to update the price in the Facebook catalog'
+id: 4CDh12JM3y9AqBnuGDHgnT
+status: PUBLISHED
+createdAt: 2024-04-03T12:41:15.144Z
+updatedAt: 2024-04-03T12:41:16.005Z
+publishedAt: 2024-04-03T12:41:16.005Z
+firstPublishedAt: 2024-04-03T12:41:16.005Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog
+locale: en
+kiStatus: Backlog
+internalReference: 924411
+---
+
+## Summary
+
+
+Today Facebook looks at sellingPrice and listPrice to update the price in the Facebook catalog.
+
+
+##
+
+## Simulation
+
+
+Seller is using unitMultiplier = 0.5
+
+Checkout makes the following calculation when the item has a multiplier unit, so sellingPrice = price * unitMultiplier = 3999 * 0.5 = 1999.5. Checkout rounding will ignore the decimal and consider 1999
+
+What is the problem with this calculation?
+When the seller uses 0.5, for example, on Facebook we are updating it as the settlement price on Facebook.
+2. When the seller uses a multiplier greater than 1.39, it falls within the promotional price even though it is higher than the listPrice
+
+
+
+##
+
+## Workaround
+
+
+seller use unitMultiplier = 10000
+
+
+
+
+
diff --git a/docs/known-issues/en/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md b/docs/known-issues/en/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
new file mode 100644
index 000000000..81a6aaad3
--- /dev/null
+++ b/docs/known-issues/en/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
@@ -0,0 +1,48 @@
+---
+title: 'Facets from the Segment affecting breadcrumbs, page title, and additional filters'
+id: 3lBgcsjxiZxoDvnPhbMXgo
+status: PUBLISHED
+createdAt: 2024-06-27T22:57:42.875Z
+updatedAt: 2024-06-27T22:57:43.965Z
+publishedAt: 2024-06-27T22:57:43.965Z
+firstPublishedAt: 2024-06-27T22:57:43.965Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters
+locale: en
+kiStatus: Backlog
+internalReference: 1057254
+---
+
+## Summary
+
+
+The "facets" property stored at the Segment/Session for a navigation context works to limit search results to predefined filters. For example, it is used by "B2B Organizations" to restrict what a user can see in the store.
+
+These facets may affect the behavior for page titles and breadcrumbs by generating unexpected values that are not part of the filters applied on the page. All filters are considered while generating these values, not only the explicit filters from the page, which should ignore the facets from Segment.
+
+It can also affect the page URL as you apply additional filters, which will be merged with the facets from Segment.
+
+
+##
+
+## Simulation
+
+
+
+- Attach a user to a B2B Organization that is limited to some product collections (A);
+- Create a landing page which shows a different collection (B);
+- The breadcrumbs and page title may show the name of collection A instead of collection B
+- Select additional search filters in the landing page, as a category or brand;
+- Notice that the URL (and also breadcrumbs and page title) will also show collection A instead of staying limited to collection B.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/failure-on-the-cancellation-ppp-when-cancellationidnull.md b/docs/known-issues/en/failure-on-the-cancellation-ppp-when-cancellationidnull.md
index 52e7735a9..236f02d2a 100644
--- a/docs/known-issues/en/failure-on-the-cancellation-ppp-when-cancellationidnull.md
+++ b/docs/known-issues/en/failure-on-the-cancellation-ppp-when-cancellationidnull.md
@@ -3,8 +3,8 @@ title: 'Failure on the cancellation (PPP) when cancellationId=null'
 id: 4yNCRQ1xhA8lEp5AGRs5eu
 status: PUBLISHED
 createdAt: 2022-06-21T21:37:04.567Z
-updatedAt: 2022-11-25T22:07:04.838Z
-publishedAt: 2022-11-25T22:07:04.838Z
+updatedAt: 2023-08-11T19:16:35.985Z
+publishedAt: 2023-08-11T19:16:35.985Z
 firstPublishedAt: 2022-06-21T21:37:05.374Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: failure-on-the-cancellation-ppp-when-cancellationidnull
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 333897
 ---
 
diff --git a/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
new file mode 100644
index 000000000..f49c46968
--- /dev/null
+++ b/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -0,0 +1,45 @@
+---
+title: 'Failure to add data in the "deliver to another address" step causes the "go to payment" button to disappear'
+id: cdZO8gGXDB1JZSj42AnVh
+status: PUBLISHED
+createdAt: 2022-01-24T21:42:52.750Z
+updatedAt: 2023-10-13T15:29:14.854Z
+publishedAt: 2023-10-13T15:29:14.854Z
+firstPublishedAt: 2023-10-13T15:29:14.854Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear
+locale: en
+kiStatus: Backlog
+internalReference: 467419
+---
+
+## Summary
+
+
+During the checkout stage, in the step of filling in the shipping data, by clicking on the option "Deliver to another address", if no address is added and the shopper comes back to the address list (using the button "back to address book") the button "Go to payment" disappears.
+
+
+##
+
+## Simulation
+
+
+
+- During the Checkout stage, when filling in the shipping data, if there is a list of addresses, click on "Deliver to another address";
+- Do not add any address and return to the shipping data by clicking on the "Back to address list" button;
+- The "Go to payment" button disappears.
+
+
+##
+
+## Workaround
+
+
+For the button to be displayed again, just click on one of the addresses in the address book. However, there is no workaround to prevent this behavior.
+
+
+
+
diff --git a/docs/known-issues/en/faststore-cart-merges-assembly-line-items.md b/docs/known-issues/en/faststore-cart-merges-assembly-line-items.md
new file mode 100644
index 000000000..6c0353007
--- /dev/null
+++ b/docs/known-issues/en/faststore-cart-merges-assembly-line-items.md
@@ -0,0 +1,43 @@
+---
+title: 'FastStore cart merges assembly line items'
+id: 4NBNaTZpr6PnRxPfrtGj77
+status: PUBLISHED
+createdAt: 2024-06-14T17:25:47.764Z
+updatedAt: 2024-06-14T17:25:48.655Z
+publishedAt: 2024-06-14T17:25:48.655Z
+firstPublishedAt: 2024-06-14T17:25:48.655Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-cart-merges-assembly-line-items
+locale: en
+kiStatus: Backlog
+internalReference: 1050068
+---
+
+## Summary
+
+
+If the same assembly option is added to different products FastStore will merge them into a single line item.
+
+
+##
+
+## Simulation
+
+
+Try to add two or more products that have the same assembly item to the cart, the products will be added on the same line
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md b/docs/known-issues/en/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
new file mode 100644
index 000000000..98d5c300e
--- /dev/null
+++ b/docs/known-issues/en/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
@@ -0,0 +1,48 @@
+---
+title: 'Faststore facets considering not removing facets set to ne hidden'
+id: 4EElvOEvMzcu52fhNOVJGM
+status: PUBLISHED
+createdAt: 2024-05-08T18:35:17.015Z
+updatedAt: 2024-05-08T18:36:15.922Z
+publishedAt: 2024-05-08T18:36:15.922Z
+firstPublishedAt: 2024-05-08T18:35:18.742Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-facets-considering-not-removing-facets-set-to-ne-hidden
+locale: en
+kiStatus: Backlog
+internalReference: 1029837
+---
+
+## Summary
+
+
+
+The expected behavior in IS facets API is to not bring facets with hidden true, but, there are some exceptions for that, for example when the facet is selected in the query, the API brings the facet in the results with the hidden prop as true, and we are not considering this information
+
+
+##
+
+## Simulation
+
+
+
+Filter for a query with the hidden facet, like for example:
+
+https://storeframework.vtex.app/new-collection?productclusternames=new-collection&fuzzy=0&operator=and&facets=productclusternames%2Cfuzzy%2Coperator&sort=score_desc&page=0
+
+In this case, productClusterNames is set as hidden but, since it's being filtered, it displays in the filter navigator
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/faststore-search-api-considering-fuzzy-as-auto-as-default.md b/docs/known-issues/en/faststore-search-api-considering-fuzzy-as-auto-as-default.md
new file mode 100644
index 000000000..1410bcb53
--- /dev/null
+++ b/docs/known-issues/en/faststore-search-api-considering-fuzzy-as-auto-as-default.md
@@ -0,0 +1,43 @@
+---
+title: 'Faststore search api considering fuzzy as auto as default'
+id: 2zedXBMhlD8pu4gZMXsrSp
+status: PUBLISHED
+createdAt: 2023-08-28T23:35:04.009Z
+updatedAt: 2024-03-27T14:10:53.090Z
+publishedAt: 2024-03-27T14:10:53.090Z
+firstPublishedAt: 2023-08-28T23:35:04.608Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-search-api-considering-fuzzy-as-auto-as-default
+locale: en
+kiStatus: Fixed
+internalReference: 889321
+---
+
+## Summary
+
+
+In package @fatstore/api, for the Intelligent Search resolver, we are considering fuzzy as auto by default when it should be 0, this is causing the behavior of fuzzy to be applied causing a "fake missmatch" in search results when we really have an exact match with the searched term, but, we display more results regardless that
+
+
+##
+
+## Simulation
+
+
+This is easy to be replicable when you search for any product, sku, or ref ID, the expected result is to display only products that matches with the ID, but, it will display more than one
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/faststore-v1-dont-return-seo-information-on-graphql-query.md b/docs/known-issues/en/faststore-v1-dont-return-seo-information-on-graphql-query.md
new file mode 100644
index 000000000..75b75a676
--- /dev/null
+++ b/docs/known-issues/en/faststore-v1-dont-return-seo-information-on-graphql-query.md
@@ -0,0 +1,46 @@
+---
+title: "Faststore V1 don't return SEO information on Graphql query"
+id: 4nZnX8sj9J90xtkNpYIgZ4
+status: PUBLISHED
+createdAt: 2023-11-01T17:08:35.090Z
+updatedAt: 2023-11-01T17:13:13.061Z
+publishedAt: 2023-11-01T17:13:13.061Z
+firstPublishedAt: 2023-11-01T17:08:35.767Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-v1-dont-return-seo-information-on-graphql-query
+locale: en
+kiStatus: No Fix
+internalReference: 929029
+---
+
+## Summary
+
+
+When accessing the Graphql playground to run queries on Faststore V1 we have a product query. The documentation states that the SEO field of that query should return the SEO information, but this is not happening.
+
+
+##
+
+## Simulation
+
+
+
+- access your store using the Graphql playground
+- run the product query with the SEO fields
+- compare with the SEO product information on the catalog
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md b/docs/known-issues/en/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
index 01d841092..b1ba7e4c3 100644
--- a/docs/known-issues/en/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
+++ b/docs/known-issues/en/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
@@ -3,8 +3,8 @@ title: 'FetchMore keeping the nextPage status and crashing the pagination'
 id: 3hyeUjVRNKE8A2UYIQiw2x
 status: PUBLISHED
 createdAt: 2022-04-11T20:53:26.480Z
-updatedAt: 2022-11-25T21:58:27.486Z
-publishedAt: 2022-11-25T21:58:27.486Z
+updatedAt: 2024-07-01T18:48:17.176Z
+publishedAt: 2024-07-01T18:48:17.176Z
 firstPublishedAt: 2022-04-11T20:53:26.870Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 560014
 ---
 
diff --git a/docs/known-issues/en/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md b/docs/known-issues/en/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
index 0b93f1f38..78c7a7030 100644
--- a/docs/known-issues/en/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
+++ b/docs/known-issues/en/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
@@ -3,8 +3,8 @@ title: 'Field Currency decimal places in Trade Policy not reflecting on PDP/PLP'
 id: 1QxxwRvFDUVnGHh5icIPpo
 status: PUBLISHED
 createdAt: 2022-11-09T17:40:35.832Z
-updatedAt: 2022-11-25T21:41:45.862Z
-publishedAt: 2022-11-25T21:41:45.862Z
+updatedAt: 2024-02-16T20:24:30.832Z
+publishedAt: 2024-02-16T20:24:30.832Z
 firstPublishedAt: 2022-11-09T17:40:36.610Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 695044
 ---
 
diff --git a/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index 3722ddde8..f344e694a 100644
--- a/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -3,8 +3,8 @@ title: 'Field "Exchanges and returns" is not updating on seller management UI af
 id: 1z8LrsbGk5B2ejZ1PV9vaB
 status: PUBLISHED
 createdAt: 2022-11-01T17:47:30.359Z
-updatedAt: 2022-11-25T22:00:22.743Z
-publishedAt: 2022-11-25T22:00:22.743Z
+updatedAt: 2023-10-30T19:28:26.143Z
+publishedAt: 2023-10-30T19:28:26.143Z
 firstPublishedAt: 2022-11-01T17:47:31.132Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,26 +12,21 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 689886
 ---
 
 ## Summary
 
 
-
 After saving the field "Exchanges and returns" on the UI the information is first updated but if we try to leave the management area or refresh the page the information is lost.
 
-
-
 The info showed on the UI is the same as the field "Shipping Policy".
 
-
-
 However, this seems to be happening only on the UI, via API the information is correct.
 
 
-
+##
 
 ## Simulation
 
@@ -42,9 +37,14 @@ However, this seems to be happening only on the UI, via API the information is c
 3. Enter again the same seller and check that the information is not correct.
 
 
+##
 
 ## Workaround
 
 
 There is no need to workaround, the information is correct on the system's backend.
 
+
+
+
+
diff --git a/docs/known-issues/en/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md b/docs/known-issues/en/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
index 3c5c6d674..6f2931a09 100644
--- a/docs/known-issues/en/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
+++ b/docs/known-issues/en/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
@@ -3,16 +3,16 @@ title: 'Fields in the orderForm Configuration are updated to null when there is
 id: jKGnwUGdfmCXtKjGPe6hj
 status: PUBLISHED
 createdAt: 2023-02-06T21:00:09.224Z
-updatedAt: 2023-04-03T14:22:00.794Z
-publishedAt: 2023-04-03T14:22:00.794Z
+updatedAt: 2024-05-09T12:44:51.823Z
+publishedAt: 2024-05-09T12:44:51.823Z
 firstPublishedAt: 2023-02-06T21:00:09.753Z
 contentType: knownIssue
-productTeam: Checkout
+productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
-tag: Checkout
+tag: Order Management
 slug: fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 748404
 ---
 
diff --git a/docs/known-issues/en/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md b/docs/known-issues/en/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
index 7c1cbd27b..9397c36b3 100644
--- a/docs/known-issues/en/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
+++ b/docs/known-issues/en/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
@@ -3,8 +3,8 @@ title: 'File Manager upload with two one more existent files does not update all
 id: 2LHdzsFFe83E1Tf0Z4j66y
 status: PUBLISHED
 createdAt: 2022-03-17T00:20:51.454Z
-updatedAt: 2022-11-25T22:10:54.509Z
-publishedAt: 2022-11-25T22:10:54.509Z
+updatedAt: 2024-02-16T20:23:18.080Z
+publishedAt: 2024-02-16T20:23:18.080Z
 firstPublishedAt: 2022-03-17T00:20:52.317Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 418253
 ---
 
@@ -22,6 +22,7 @@ internalReference: 418253
 File Manager upload with two one more existent files does not update all the files, only the first
 
 
+##
 
 ## Simulation
 
@@ -35,6 +36,7 @@ This warning is telling us only about one file, the second one is not being vali
 - Both files upload, but only one will replace the older one.
 
 
+##
 
 ## Workaround
 
diff --git a/docs/known-issues/en/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md b/docs/known-issues/en/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
index 63418c8b8..6fb8a987f 100644
--- a/docs/known-issues/en/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
+++ b/docs/known-issues/en/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
@@ -3,8 +3,8 @@ title: ' Filter by SkuName on Sales Performance is not accepting uppercase.'
 id: 3FCDeEn8xmEvOXKgBxqyL5
 status: PUBLISHED
 createdAt: 2022-08-16T18:06:02.919Z
-updatedAt: 2022-11-30T19:08:14.148Z
-publishedAt: 2022-11-30T19:08:14.148Z
+updatedAt: 2024-02-16T20:24:21.760Z
+publishedAt: 2024-02-16T20:24:21.760Z
 firstPublishedAt: 2022-08-16T18:06:03.474Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: filter-by-skuname-on-sales-performance-is-not-accepting-uppercase
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639219
 ---
 
diff --git a/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
new file mode 100644
index 000000000..63b83138b
--- /dev/null
+++ b/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -0,0 +1,44 @@
+---
+title: 'Filter "productClusterIds" is overwritten by "productClusterNames" while applying additional filters'
+id: 3d4BIZQBZgeK3eKwT8B1PZ
+status: PUBLISHED
+createdAt: 2023-09-13T22:42:57.138Z
+updatedAt: 2023-09-21T18:04:57.946Z
+publishedAt: 2023-09-21T18:04:57.946Z
+firstPublishedAt: 2023-09-13T22:42:57.682Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters
+locale: en
+kiStatus: Backlog
+internalReference: 899508
+---
+
+## Summary
+
+
+When a search is started from the filter "productClusterIds", applying any additional filter will convert it to "productClusterNames", losing the characteristic of presenting the items with the sorting manually defined at the product collection.
+
+
+##
+
+## Simulation
+
+
+The scenario can be seen on any page, like `"store.com/111?map=productClusterIds"`, and applying any additional filter, like a category, specification, etc.
+
+The user will be directed to `"store.com/clothing/special-sale?initialMap=productClusterIds&initialQuery=111&map=category,productclusternames"`.
+
+
+##
+
+## Workaround
+
+
+There's no workaround for the specific issue if you need the special sorting, but be sure to use "productClusterIds" only in required scenarios. Otherwise, use the filter as "productClusterNames".
+
+
+
+
diff --git a/docs/known-issues/en/filters-by-sku-specifications-not-considering-regionalized-availability.md b/docs/known-issues/en/filters-by-sku-specifications-not-considering-regionalized-availability.md
new file mode 100644
index 000000000..bbbf12665
--- /dev/null
+++ b/docs/known-issues/en/filters-by-sku-specifications-not-considering-regionalized-availability.md
@@ -0,0 +1,49 @@
+---
+title: 'Filters by SKU specifications not considering regionalized availability'
+id: 3CeTfHaNBfhrC5qIi3nTLh
+status: PUBLISHED
+createdAt: 2024-06-05T20:52:53.211Z
+updatedAt: 2024-06-05T20:52:54.055Z
+publishedAt: 2024-06-05T20:52:54.055Z
+firstPublishedAt: 2024-06-05T20:52:54.055Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: filters-by-sku-specifications-not-considering-regionalized-availability
+locale: en
+kiStatus: Backlog
+internalReference: 1045111
+---
+
+## Summary
+
+
+Filtering the search by an SKU specification will also apply a filter by SKU availability, removing products where the selected variation is stockout, but it doesn't apply to regionalized stores.
+
+Regionalized navigations may return products where the filtered variation is unavailable because the indexed availability for an SKU specification is based on all regular and whitelabel sellers.
+
+
+##
+
+## Simulation
+
+
+Considering a store with two sellers and the following availability matrix for a specific product:
+
+- size: small; seller A: available; seller B: unavailable
+- size: large; seller A: unavailable; seller B: unavailable
+
+In a navigation with "regionId: seller B", filtering by "size: small" will return the product (as it were available) and "size: large" will hide the product (because it's unavailable everywhere).
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md b/docs/known-issues/en/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
new file mode 100644
index 000000000..0251d92ae
--- /dev/null
+++ b/docs/known-issues/en/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
@@ -0,0 +1,38 @@
+---
+title: 'Filters hidden from the store are also hidden from Intelligent Search admin pages'
+id: 3TvpIUFzdXWesADHDhjyLQ
+status: PUBLISHED
+createdAt: 2022-02-23T21:59:22.607Z
+updatedAt: 2023-10-19T16:24:57.801Z
+publishedAt: 2023-10-19T16:24:57.801Z
+firstPublishedAt: 2022-02-23T21:59:22.977Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages
+locale: en
+kiStatus: Backlog
+internalReference: 416638
+---
+
+## Summary
+
+
+Some specifications have internal usage or scenarios that need to be hidden, but the store needs that specification for purposes of the search, like using it for Merch Rules.
+
+
+##
+
+## Simulation
+
+
+On some accounts, the SKU specification "color" does not appear as an option under "Use SKU specifications to display individual products in search results". We see that "color" is one of the specifications under "Hide facets".
+
+
+
+## Workaround
+
+
+Remove the attribute from the "hide facets" configuration, create the merchandising rule or do the expected configuration, and hide the attribute again.
+
diff --git a/docs/known-issues/en/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md b/docs/known-issues/en/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
new file mode 100644
index 000000000..987ea29ca
--- /dev/null
+++ b/docs/known-issues/en/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
@@ -0,0 +1,45 @@
+---
+title: 'Final domain different from myvtex due to old component version on Site Editor'
+id: 7bf2mMbpcxUd6Q32DYP6vz
+status: PUBLISHED
+createdAt: 2023-12-05T18:07:50.089Z
+updatedAt: 2024-01-26T17:52:03.169Z
+publishedAt: 2024-01-26T17:52:03.169Z
+firstPublishedAt: 2023-12-05T18:07:50.675Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor
+locale: en
+kiStatus: Backlog
+internalReference: 948071
+---
+
+## Summary
+
+
+Sometimes you can make changes on Site Editor and those changes are reflected on the myvtex environment, but when you try to update the final domain, those changes are not being reflected. This normally happens when the component you're trying to change has more than one version. The front keeps using the inactive version of the component while the myvtex is using the active version. The only way to solve this is by deleting the inactive version of the component.
+
+
+##
+
+## Simulation
+
+
+
+- Try to change something on the site editor on a new version of a component
+- Check if your changes are being reflected on the final domain and in the myvtex environment
+
+
+##
+
+## Workaround
+
+
+Delete the old version, this will make the final domain use the right version of the component
+
+
+
+
+
diff --git a/docs/known-issues/en/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md b/docs/known-issues/en/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
new file mode 100644
index 000000000..b173a00da
--- /dev/null
+++ b/docs/known-issues/en/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
@@ -0,0 +1,45 @@
+---
+title: 'First address in the address list incomplete does not fill the profile/shipping data at checkout'
+id: 2AqDZb1AGBjmeMOBU0JkLQ
+status: PUBLISHED
+createdAt: 2024-01-03T20:44:07.692Z
+updatedAt: 2024-01-03T20:49:41.249Z
+publishedAt: 2024-01-03T20:49:41.249Z
+firstPublishedAt: 2024-01-03T20:44:11.604Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout
+locale: en
+kiStatus: Backlog
+internalReference: 366975
+---
+
+## Summary
+
+
+When a user has more than one address in their profile and the first address in the address list is incomplete, regardless of whether the others are valid, the checkout does not automatically populate their profile/shipping data after adding their email.
+
+
+##
+
+## Simulation
+
+
+
+- Add 2 addresses to a profile, where the 1st one is incomplete;
+- Assemble a cart, and add the email;
+- No profile/address data is filled.
+
+
+##
+
+## Workaround
+
+
+Remove the incomplete address from the profile via Master Data
+
+
+
+
diff --git a/docs/known-issues/en/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md b/docs/known-issues/en/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
new file mode 100644
index 000000000..8fe53524b
--- /dev/null
+++ b/docs/known-issues/en/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
@@ -0,0 +1,44 @@
+---
+title: 'First digit is removed from corporateDocument if starts with letters'
+id: sfKdoiEwBRR73CbhvSHJF
+status: PUBLISHED
+createdAt: 2023-10-17T17:26:20.683Z
+updatedAt: 2024-03-14T22:02:01.236Z
+publishedAt: 2024-03-14T22:02:01.236Z
+firstPublishedAt: 2023-10-17T17:26:21.490Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: first-digit-is-removed-from-corporatedocument-if-starts-with-letters
+locale: en
+kiStatus: Fixed
+internalReference: 920703
+---
+
+## Summary
+
+
+When an organization's corporate document starts with letters, the first digit is removed after accessing checkout.
+
+
+##
+
+## Simulation
+
+
+
+- Register an organization with corporate document starts with letters;
+- Add items to the cart;
+- Go to checkout and check the orderForm, the first digit from corporateDocument field will be removed.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/first-subscription-cycle-is-skipped.md b/docs/known-issues/en/first-subscription-cycle-is-skipped.md
new file mode 100644
index 000000000..f8afa1184
--- /dev/null
+++ b/docs/known-issues/en/first-subscription-cycle-is-skipped.md
@@ -0,0 +1,49 @@
+---
+title: 'First subscription cycle is skipped'
+id: 2VX6uoop56wK6jecAly40G
+status: PUBLISHED
+createdAt: 2024-02-05T14:10:40.701Z
+updatedAt: 2024-02-05T14:10:41.599Z
+publishedAt: 2024-02-05T14:10:41.599Z
+firstPublishedAt: 2024-02-05T14:10:41.599Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: first-subscription-cycle-is-skipped
+locale: en
+kiStatus: Backlog
+internalReference: 528556
+---
+
+## Summary
+
+
+The subscription system uses information such as the purchase frequency and the subscription cycle date to generate a subscription order. However, depending on the consumer's time zone and the time the order is placed, the first cycle is skipped, and only generated in the second month.
+Suppose that on May 9, 11 p.m., a customer created a monthly subscription and set the subscription cycle date for the 9th day of each month, expecting that the first order would be placed on June 9.
+The orders management system operates in the time zone previously set in the store. In this case, we will consider GMT-5, Chicago time. However, the subscription system operates in the GMT 0 time zone. This means that although the subscription was created at 11 p.m., the subscription system considers that it was created 5 hours later, therefore on May 10.
+In this case, the system takes into consideration the subscription creation date, May 10, to calculate the next subscription cycle. As the subscription cycle date on June 9 would not meet the 30-day period condition, totaling 29 days, the system sets the next purchase date for July. Therefore, the customer ends up receiving the product after the expected date.
+
+
+##
+
+## Simulation
+
+
+Have a SKU set up for subscription, with monthly frequency and purchase day;
+Place an order after 11 p.m., for example
+Check that the first cycle, which should be generated in the following month, will be skipped, being generated only in the second month.
+
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md b/docs/known-issues/en/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
index f1fa00cb0..f01728393 100644
--- a/docs/known-issues/en/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
+++ b/docs/known-issues/en/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
@@ -3,8 +3,8 @@ title: 'Fixed Price being created on trade Policy 1 when saving bundle prices.'
 id: 3Xbh5GVn0jm2yhaOiRg3Le
 status: PUBLISHED
 createdAt: 2022-11-28T12:41:07.808Z
-updatedAt: 2022-11-28T12:41:08.426Z
-publishedAt: 2022-11-28T12:41:08.426Z
+updatedAt: 2024-02-16T20:24:01.848Z
+publishedAt: 2024-02-16T20:24:01.848Z
 firstPublishedAt: 2022-11-28T12:41:08.426Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 705869
 ---
 
diff --git a/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index 0c8e1d085..ee9c5f37c 100644
--- a/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -3,8 +3,8 @@ title: 'FOB External Marketplace integrate an order (Erro code: "FMT010")'
 id: 3qzV4zJRkPIwQnAZuK5dWu
 status: PUBLISHED
 createdAt: 2022-02-25T16:33:49.641Z
-updatedAt: 2022-11-25T22:00:10.646Z
-publishedAt: 2022-11-25T22:00:10.646Z
+updatedAt: 2024-02-16T20:26:31.795Z
+publishedAt: 2024-02-16T20:26:31.795Z
 firstPublishedAt: 2022-02-25T16:33:50.398Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: fob-external-marketplace-integrate-an-order-erro-code-fmt010
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 532377
 ---
 
diff --git a/docs/known-issues/en/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md b/docs/known-issues/en/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
index 89740597b..6746c92ed 100644
--- a/docs/known-issues/en/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
+++ b/docs/known-issues/en/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
@@ -3,8 +3,8 @@ title: 'Free shipping promotion being applied on split orders outside promotion
 id: APAIGZx8tdtIjGsQJmvgu
 status: PUBLISHED
 createdAt: 2023-01-12T16:19:47.878Z
-updatedAt: 2023-01-12T16:19:48.479Z
-publishedAt: 2023-01-12T16:19:48.479Z
+updatedAt: 2024-02-16T20:23:58.107Z
+publishedAt: 2024-02-16T20:23:58.107Z
 firstPublishedAt: 2023-01-12T16:19:48.479Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 732302
 ---
 
diff --git a/docs/known-issues/en/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md b/docs/known-issues/en/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
new file mode 100644
index 000000000..b2fe21bb4
--- /dev/null
+++ b/docs/known-issues/en/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
@@ -0,0 +1,48 @@
+---
+title: 'Fullcleanup on sellers does not work if the account has seller groups on Seller Management'
+id: 3U9tS11FQU0JLUxEDSt5rL
+status: PUBLISHED
+createdAt: 2023-10-19T19:54:36.389Z
+updatedAt: 2024-07-01T18:49:14.530Z
+publishedAt: 2024-07-01T18:49:14.530Z
+firstPublishedAt: 2023-10-19T19:54:37.266Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management
+locale: en
+kiStatus: No Fix
+internalReference: 922541
+---
+
+## Summary
+
+
+On the Seller Management area the marketplace can group their sellers as they wish and manage them on the group management tab.
+
+However, if they wish to delete all seller data on the fullcleanup area, the process will fail if there are groups created.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a seller group on Seller Management;
+2. Perform a seller fullcleanup;
+3. Check that an error appears.
+
+
+##
+
+## Workaround
+
+
+First, delete the seller groups manually on the seller management and then try to perform the seller fullcleanup again.
+
+
+
+
+
diff --git a/docs/known-issues/en/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md b/docs/known-issues/en/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
new file mode 100644
index 000000000..dbc962c4f
--- /dev/null
+++ b/docs/known-issues/en/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
@@ -0,0 +1,44 @@
+---
+title: "GA4 purchase event doesn't have the category tree on item_category in dataLayer"
+id: 6GCrgcG8PJHaZp80hi4Gb1
+status: PUBLISHED
+createdAt: 2023-07-12T16:42:17.087Z
+updatedAt: 2023-07-12T16:43:37.976Z
+publishedAt: 2023-07-12T16:43:37.976Z
+firstPublishedAt: 2023-07-12T16:42:17.674Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer
+locale: en
+kiStatus: Backlog
+internalReference: 860655
+---
+
+## Summary
+
+
+GA4 purchase event doesn't have the category tree on item_category in dataLayer, so the only category available is the last level category from the product.
+
+
+##
+
+## Simulation
+
+
+
+- Configure the app Google Tag Manager and activate "Send Google Analytics 4 Events";
+- Finish a purchase;
+- On the console, check the events in dataLayer; there will be only the last level category on item_category.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md b/docs/known-issues/en/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
index 560ca2b71..b8fa4c960 100644
--- a/docs/known-issues/en/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
+++ b/docs/known-issues/en/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
@@ -3,8 +3,8 @@ title: "GeoCoordinates data can't be informed for some cultureInfo"
 id: 4MjLbyrniWsPKpFBHgn8sG
 status: PUBLISHED
 createdAt: 2022-05-19T16:19:45.245Z
-updatedAt: 2022-11-25T21:52:55.550Z
-publishedAt: 2022-11-25T21:52:55.550Z
+updatedAt: 2024-07-01T18:48:21.888Z
+publishedAt: 2024-07-01T18:48:21.888Z
 firstPublishedAt: 2022-05-19T16:19:45.749Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: geocoordinates-data-cant-be-informed-for-some-cultureinfo
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 582065
 ---
 
diff --git a/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md b/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md
index 9a2a08dec..aa51dc1f9 100644
--- a/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md
+++ b/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md
@@ -34,7 +34,7 @@ After making sure your browser meets the said condition, follow the steps below:
 5. At checkout, select the **pickup point** delivery option. 
 6. Note that the page is stuck on loading, displaying the message "Awaiting permission to get your current location".
 
-![erro EN](https://images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/22bc5539ee83ef63668f4ad01c7e0933/erro_EN.png)
+![erro EN](//images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/22bc5539ee83ef63668f4ad01c7e0933/erro_EN.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 23cd379df..e93f7ec17 100644
--- a/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -3,8 +3,8 @@ title: ""Get all SKU suggestions" API doesn't keep same sku order when changing
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
-updatedAt: 2022-12-05T14:50:25.991Z
-publishedAt: 2022-12-05T14:50:25.991Z
+updatedAt: 2024-03-01T21:06:12.857Z
+publishedAt: 2024-03-01T21:06:12.857Z
 firstPublishedAt: 2022-12-05T14:49:47.309Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 367187
 ---
 
diff --git a/docs/known-issues/en/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md b/docs/known-issues/en/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
new file mode 100644
index 000000000..43dc88ef4
--- /dev/null
+++ b/docs/known-issues/en/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
@@ -0,0 +1,46 @@
+---
+title: "GET Coupon Usage API doesn't list multiple orders for the same coupon"
+id: 7B9Qlcx2XMGxWj9OB5Xl8n
+status: PUBLISHED
+createdAt: 2023-09-08T17:54:13.642Z
+updatedAt: 2023-09-08T17:54:14.220Z
+publishedAt: 2023-09-08T17:54:14.220Z
+firstPublishedAt: 2023-09-08T17:54:14.220Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon
+locale: en
+kiStatus: Backlog
+internalReference: 326662
+---
+
+## Summary
+
+
+
+The GET Coupon Usage API https://developers.vtex.com/vtex-rest-api/reference/catalog-api-overview is currently not listing all the order closed in which this coupon was used on, is listing total-1
+
+
+
+##
+
+## Simulation
+
+
+1) Close two distinct orders with the same coupon.
+
+2) GET the data from this coupon's usage https://developers.vtex.com/vtex-rest-api/reference/coupons#getusage
+
+3) It will be listed the total minus one order.
+
+
+
+##
+
+## Workaround
+
+
+n/a
+
diff --git a/docs/known-issues/en/get-matched-offers-list-api-not-working-properly.md b/docs/known-issues/en/get-matched-offers-list-api-not-working-properly.md
index 6c0bc06db..a75e984bd 100644
--- a/docs/known-issues/en/get-matched-offers-list-api-not-working-properly.md
+++ b/docs/known-issues/en/get-matched-offers-list-api-not-working-properly.md
@@ -3,8 +3,8 @@ title: 'Get Matched Offers List API not working properly'
 id: 7mxrjTDYB8yLeKmQkB5D9h
 status: PUBLISHED
 createdAt: 2022-03-31T13:49:41.374Z
-updatedAt: 2022-11-25T22:00:46.842Z
-publishedAt: 2022-11-25T22:00:46.842Z
+updatedAt: 2024-07-01T18:48:12.526Z
+publishedAt: 2024-07-01T18:48:12.526Z
 firstPublishedAt: 2022-03-31T13:49:42.277Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: get-matched-offers-list-api-not-working-properly
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 553456
 ---
 
diff --git a/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md
index 1de707cd4..85760ba7f 100644
--- a/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md
@@ -3,8 +3,8 @@ title: 'GET Product by Refid Returning "Null" when not Found'
 id: 6yiM9gJT5DB77pZSBNfGZ3
 status: PUBLISHED
 createdAt: 2023-05-16T19:35:46.743Z
-updatedAt: 2023-05-16T19:35:47.468Z
-publishedAt: 2023-05-16T19:35:47.468Z
+updatedAt: 2024-07-01T18:49:03.498Z
+publishedAt: 2024-07-01T18:49:03.498Z
 firstPublishedAt: 2023-05-16T19:35:47.468Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: get-product-by-refid-returning-null-when-not-found
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 826702
 ---
 
diff --git a/docs/known-issues/en/get-sku-by-ean-api-returns-only-active-skus.md b/docs/known-issues/en/get-sku-by-ean-api-returns-only-active-skus.md
index 0e0659e95..0711d9168 100644
--- a/docs/known-issues/en/get-sku-by-ean-api-returns-only-active-skus.md
+++ b/docs/known-issues/en/get-sku-by-ean-api-returns-only-active-skus.md
@@ -3,8 +3,8 @@ title: 'GET SKU by EAN API returns only active SKUs'
 id: 5NiuB1Lgf3CM5kXSSVdfuu
 status: PUBLISHED
 createdAt: 2020-03-23T15:10:23.842Z
-updatedAt: 2022-11-25T22:00:19.153Z
-publishedAt: 2022-11-25T22:00:19.153Z
+updatedAt: 2023-10-24T17:25:02.496Z
+publishedAt: 2023-10-24T17:25:02.496Z
 firstPublishedAt: 2020-03-27T19:32:53.914Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: get-sku-by-ean-api-returns-only-active-skus
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 699007
 ---
 
diff --git a/docs/known-issues/en/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md b/docs/known-issues/en/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
index 1e1237d7b..73f63a4ab 100644
--- a/docs/known-issues/en/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
+++ b/docs/known-issues/en/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
@@ -3,8 +3,8 @@ title: 'getCurrentProductWithVariations function from VTEX.js brings data from C
 id: 1m1bMbNXZVpQo9bQG1iSjn
 status: PUBLISHED
 createdAt: 2022-03-16T16:35:51.214Z
-updatedAt: 2022-11-25T22:10:09.849Z
-publishedAt: 2022-11-25T22:10:09.849Z
+updatedAt: 2024-02-16T20:24:03.691Z
+publishedAt: 2024-02-16T20:24:03.691Z
 firstPublishedAt: 2022-03-16T16:35:51.652Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 324416
 ---
 
diff --git a/docs/known-issues/en/gift-card-creation-error-via-admin.md b/docs/known-issues/en/gift-card-creation-error-via-admin.md
new file mode 100644
index 000000000..a630e1f38
--- /dev/null
+++ b/docs/known-issues/en/gift-card-creation-error-via-admin.md
@@ -0,0 +1,47 @@
+---
+title: 'Gift Card creation error via admin'
+id: 6GUhpZbxYr0wTIuqN3S95A
+status: PUBLISHED
+createdAt: 2024-02-21T22:45:26.869Z
+updatedAt: 2024-02-21T22:45:27.647Z
+publishedAt: 2024-02-21T22:45:27.647Z
+firstPublishedAt: 2024-02-21T22:45:27.647Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: gift-card-creation-error-via-admin
+locale: en
+kiStatus: Backlog
+internalReference: 986327
+---
+
+## Summary
+
+
+Some accounts won't be able to create a Gift Card for the first time via admin, the message below will appear in the screen:
+
+`Something went wrong`
+`Error connecting to the backend server.`
+`Please, return to our store in an few moments.`
+
+
+##
+
+## Simulation
+
+
+This is only replicable in stores facing this issue, after filling all Gift Card information and pressing the `Save` button users will see the error message mentioned above.
+
+
+##
+
+## Workaround
+
+
+If the first Gift Card is created via API the error will stop ocurring, merchants will be able to create Gift Cards via admin normally after that.
+
+
+
+
+
diff --git a/docs/known-issues/en/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md b/docs/known-issues/en/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
index 3157246c2..eabe2fdd9 100644
--- a/docs/known-issues/en/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
+++ b/docs/known-issues/en/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
@@ -3,8 +3,8 @@ title: 'Gift card expiration date does not match with the date chosen when it wa
 id: 57GeuSubkdDkQNwzL3nmup
 status: PUBLISHED
 createdAt: 2022-03-27T14:08:35.577Z
-updatedAt: 2022-11-25T22:07:21.976Z
-publishedAt: 2022-11-25T22:07:21.976Z
+updatedAt: 2024-07-01T18:48:00.399Z
+publishedAt: 2024-07-01T18:48:00.399Z
 firstPublishedAt: 2022-03-27T14:08:36.056Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 378436
 ---
 
diff --git a/docs/known-issues/en/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md b/docs/known-issues/en/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
new file mode 100644
index 000000000..23e0d121b
--- /dev/null
+++ b/docs/known-issues/en/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
@@ -0,0 +1,43 @@
+---
+title: 'Gift Card HUB accepts Invalid/Empty ID in response to create transaction'
+id: 3ODSXijmpvkk55FUqMcGvQ
+status: PUBLISHED
+createdAt: 2023-07-05T12:50:36.661Z
+updatedAt: 2023-07-05T12:51:07.938Z
+publishedAt: 2023-07-05T12:51:07.938Z
+firstPublishedAt: 2023-07-05T12:50:37.274Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction
+locale: en
+kiStatus: Backlog
+internalReference: 855864
+---
+
+## Summary
+
+
+Our gift card provider protocol documentation specifies that the create transaction API must include a valid ID in the response. However, the current protocol implementation allows providers to respond to this request with either an empty or invalid ID. As a result, when attempting to settle the payment, the transaction becomes stuck because the required ID is missing. This leads to an error being thrown and the transaction remaining stuck in the process.
+
+
+##
+
+## Simulation
+
+
+Respond to the create transaction call with an invalid ID and try to finish a transaction.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index 4f56337ca..49e444760 100644
--- a/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -3,8 +3,8 @@ title: 'Gift Card hub is adding an extra backslash ("/") when calling providers.
 id: 2ZstMKKGUbrdXGuhS2Rr1f
 status: PUBLISHED
 createdAt: 2022-09-30T21:07:47.856Z
-updatedAt: 2022-11-25T22:04:08.181Z
-publishedAt: 2022-11-25T22:04:08.181Z
+updatedAt: 2024-02-16T20:24:58.109Z
+publishedAt: 2024-02-16T20:24:58.109Z
 firstPublishedAt: 2022-09-30T21:07:48.985Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: gift-card-hub-is-adding-an-extra-backslash-when-calling-providers
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 669575
 ---
 
diff --git a/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
new file mode 100644
index 000000000..c66fa629f
--- /dev/null
+++ b/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -0,0 +1,43 @@
+---
+title: 'Gift card - It does not return Fields "caption" and "relationName" when we make a get request.'
+id: 2nh2Cc3Hc2Zm0b1INtwDep
+status: PUBLISHED
+createdAt: 2023-06-23T19:33:35.774Z
+updatedAt: 2024-02-16T20:25:03.806Z
+publishedAt: 2024-02-16T20:25:03.806Z
+firstPublishedAt: 2023-06-23T19:33:36.777Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request
+locale: en
+kiStatus: No Fix
+internalReference: 428725
+---
+
+## Summary
+
+
+When the GET method is executed for an existing Gift card, it does not return the "caption" field or the "relationName" field even though these parameters have value.
+
+
+##
+
+## Simulation
+
+
+Make a get request on the API:  https://developers.vtex.com/vtex-rest-api/reference/gift-card#getgiftcardbyid
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/gift-items-throws-a-generic-exception-if-it-has-no-price.md b/docs/known-issues/en/gift-items-throws-a-generic-exception-if-it-has-no-price.md
index 5a7c6d995..75e454446 100644
--- a/docs/known-issues/en/gift-items-throws-a-generic-exception-if-it-has-no-price.md
+++ b/docs/known-issues/en/gift-items-throws-a-generic-exception-if-it-has-no-price.md
@@ -3,8 +3,8 @@ title: 'Gift items throws a generic exception if it has no price'
 id: 7Jw1Nihqp3Sg2ecg7R9IEt
 status: PUBLISHED
 createdAt: 2022-05-12T14:52:18.546Z
-updatedAt: 2022-11-25T21:51:44.617Z
-publishedAt: 2022-11-25T21:51:44.617Z
+updatedAt: 2024-02-16T20:27:57.698Z
+publishedAt: 2024-02-16T20:27:57.698Z
 firstPublishedAt: 2022-05-12T14:52:18.968Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: gift-items-throws-a-generic-exception-if-it-has-no-price
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 510490
 ---
 
diff --git a/docs/known-issues/en/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md b/docs/known-issues/en/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
index 4e10e3ec2..d1210bf27 100644
--- a/docs/known-issues/en/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
+++ b/docs/known-issues/en/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
@@ -3,8 +3,8 @@ title: 'Gift promotions not working as expected when acting alongside other gift
 id: 7p037qcaXYMYKC3kJPztc3
 status: PUBLISHED
 createdAt: 2023-01-09T21:08:49.800Z
-updatedAt: 2023-01-09T21:08:50.899Z
-publishedAt: 2023-01-09T21:08:50.899Z
+updatedAt: 2024-02-16T20:23:54.228Z
+publishedAt: 2024-02-16T20:23:54.228Z
 firstPublishedAt: 2023-01-09T21:08:50.899Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 729980
 ---
 
diff --git a/docs/known-issues/en/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md b/docs/known-issues/en/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
index 2250c9d80..4aa6bc717 100644
--- a/docs/known-issues/en/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
+++ b/docs/known-issues/en/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
@@ -3,8 +3,8 @@ title: 'Giftcard Rechargeable configuration does not work when trying to add cre
 id: 3MXPd85Km51KpO4FNPqlDf
 status: PUBLISHED
 createdAt: 2022-05-23T14:21:10.608Z
-updatedAt: 2022-11-25T22:05:59.003Z
-publishedAt: 2022-11-25T22:05:59.003Z
+updatedAt: 2024-02-16T20:25:54.496Z
+publishedAt: 2024-02-16T20:25:54.496Z
 firstPublishedAt: 2022-05-23T14:21:11.126Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 583669
 ---
 
diff --git a/docs/known-issues/en/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md b/docs/known-issues/en/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
index ec064a18b..3b0106b18 100644
--- a/docs/known-issues/en/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
+++ b/docs/known-issues/en/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
@@ -3,8 +3,8 @@ title: '[Giftlist] Data de evento salva na UI não é a mesma que reflete no bd'
 id: 6PUBzRdtno8ypsPMg97B6K
 status: PUBLISHED
 createdAt: 2022-07-25T17:45:12.568Z
-updatedAt: 2022-11-25T21:42:07.374Z
-publishedAt: 2022-11-25T21:42:07.374Z
+updatedAt: 2024-02-16T20:28:47.100Z
+publishedAt: 2024-02-16T20:28:47.100Z
 firstPublishedAt: 2022-07-25T17:45:13.009Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 402134
 ---
 
diff --git a/docs/known-issues/en/global-categories-in-catalog-outdated-compared-to-google.md b/docs/known-issues/en/global-categories-in-catalog-outdated-compared-to-google.md
index 45e77019f..20fdb8059 100644
--- a/docs/known-issues/en/global-categories-in-catalog-outdated-compared-to-google.md
+++ b/docs/known-issues/en/global-categories-in-catalog-outdated-compared-to-google.md
@@ -3,8 +3,8 @@ title: 'Global categories in catalog outdated compared to Google'
 id: 4vH5NRdMsuZmOohdHFn16H
 status: PUBLISHED
 createdAt: 2023-02-14T19:42:08.121Z
-updatedAt: 2023-02-14T19:42:08.712Z
-publishedAt: 2023-02-14T19:42:08.712Z
+updatedAt: 2024-07-01T18:48:52.824Z
+publishedAt: 2024-07-01T18:48:52.824Z
 firstPublishedAt: 2023-02-14T19:42:08.712Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: global-categories-in-catalog-outdated-compared-to-google
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 754062
 ---
 
diff --git a/docs/known-issues/en/google-customer-reviews-component-iframe-has-inconsistent-rendering.md b/docs/known-issues/en/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
new file mode 100644
index 000000000..3e9819c89
--- /dev/null
+++ b/docs/known-issues/en/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
@@ -0,0 +1,46 @@
+---
+title: 'Google Customer Reviews component iframe has inconsistent rendering'
+id: 7BDB9yYv3ZHbhE4ExCXgZK
+status: PUBLISHED
+createdAt: 2023-12-22T17:55:39.082Z
+updatedAt: 2024-02-16T20:25:48.248Z
+publishedAt: 2024-02-16T20:25:48.248Z
+firstPublishedAt: 2023-12-22T17:55:39.764Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: google-customer-reviews-component-iframe-has-inconsistent-rendering
+locale: en
+kiStatus: No Fix
+internalReference: 578443
+---
+
+## Summary
+
+
+The iframe, responsible for the Google Customer Review badge, has inconsistent rendering inside the Google Customer Reviews component div element.
+
+Google Customer Reviews:
+https://developers.vtex.com/vtex-developer-docs/docs/vtex-google-customer-reviews
+
+
+##
+
+## Simulation
+
+
+In an account that uses the Google Customer Reviews component, opening the Element tab in the browser inspector, you can see always the Google Customer Review div, but, sometimes, the element is empty, without the Google iframe.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/group-by-delivery-method-on-sales-performance-not-working-as-expected.md b/docs/known-issues/en/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
index 8c8adc6bf..616ec54de 100644
--- a/docs/known-issues/en/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
+++ b/docs/known-issues/en/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
@@ -3,8 +3,8 @@ title: ' Group by Delivery Method on Sales Performance not working as expected'
 id: 8zHND5pzrt0mrIrb061Zq
 status: PUBLISHED
 createdAt: 2022-11-30T19:02:13.548Z
-updatedAt: 2022-12-01T22:14:52.118Z
-publishedAt: 2022-12-01T22:14:52.118Z
+updatedAt: 2024-02-16T20:25:12.853Z
+publishedAt: 2024-02-16T20:25:12.853Z
 firstPublishedAt: 2022-11-30T19:02:13.994Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: group-by-delivery-method-on-sales-performance-not-working-as-expected
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639294
 ---
 
diff --git a/docs/known-issues/en/headless-cms-ignores-array-validation-settings.md b/docs/known-issues/en/headless-cms-ignores-array-validation-settings.md
new file mode 100644
index 000000000..f223a44a5
--- /dev/null
+++ b/docs/known-issues/en/headless-cms-ignores-array-validation-settings.md
@@ -0,0 +1,48 @@
+---
+title: 'Headless CMS ignores array validation settings'
+id: 1szfagZFJHmevSWDTyd45e
+status: PUBLISHED
+createdAt: 2024-06-07T14:22:41.366Z
+updatedAt: 2024-06-07T14:22:41.992Z
+publishedAt: 2024-06-07T14:22:41.992Z
+firstPublishedAt: 2024-06-07T14:22:41.992Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: headless-cms-ignores-array-validation-settings
+locale: en
+kiStatus: Backlog
+internalReference: 1046372
+---
+
+## Summary
+
+
+When trying to configure array validation rules in the Headless CMS, such as minimum and maximum array items, the validation errors are not shown to the user and it is possible to save the schema without passing validation.
+
+The expected scenario would be to block the screen and show a message like:
+
+    "keyword": "minItems", "message": "must NOT have fewer than 3 items",
+
+
+
+##
+
+## Simulation
+
+
+Try adding a section that has a validation rule. If you don't respect the validation the hCMS will let you publish the content normally.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md b/docs/known-issues/en/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
new file mode 100644
index 000000000..80858af42
--- /dev/null
+++ b/docs/known-issues/en/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
@@ -0,0 +1,47 @@
+---
+title: 'Image format as JPG or PNG do not work on seller portal catalog'
+id: 19s9bGcpNsOkIkA0iGkWRi
+status: PUBLISHED
+createdAt: 2024-04-22T12:41:43.272Z
+updatedAt: 2024-04-22T12:41:44.252Z
+publishedAt: 2024-04-22T12:41:44.252Z
+firstPublishedAt: 2024-04-22T12:41:44.252Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog
+locale: en
+kiStatus: Backlog
+internalReference: 1020505
+---
+
+## Summary
+
+
+When trying to create a product with a image format set as JPG or PNG, the product is created with a broken image. This behavior does not happen if the format is set like jpg or png (no capslock).
+
+
+##
+
+## Simulation
+
+
+
+1. Create a product on a seller portal account
+2. Import a image with format JPG or PNG
+3. Save the product
+4. Check that the image is broken on the UI if you open the created product.
+
+
+##
+
+## Workaround
+
+
+Import images with format jpg or png (lowercase).
+
+
+
+
+
diff --git a/docs/known-issues/en/impersonation-is-ignored-after-one-purchase-is-completed.md b/docs/known-issues/en/impersonation-is-ignored-after-one-purchase-is-completed.md
new file mode 100644
index 000000000..2aef80ce5
--- /dev/null
+++ b/docs/known-issues/en/impersonation-is-ignored-after-one-purchase-is-completed.md
@@ -0,0 +1,48 @@
+---
+title: 'Impersonation is ignored after one purchase is completed'
+id: 4mHKOlwaLwfIEf8HFh4y4Y
+status: PUBLISHED
+createdAt: 2024-03-20T20:10:26.200Z
+updatedAt: 2024-03-20T20:10:27.029Z
+publishedAt: 2024-03-20T20:10:27.029Z
+firstPublishedAt: 2024-03-20T20:10:27.029Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: impersonation-is-ignored-after-one-purchase-is-completed
+locale: en
+kiStatus: Backlog
+internalReference: 1003545
+---
+
+## Summary
+
+
+When a call center operator impersonates a shopper, completes a purchase and is sent to the orderPlaced page, a new orderForm will be generated.
+
+This new orderForm will have its clientProfileData attachment with the call center operator's email instead of the impersonated shopper, even though the impersonation data is persisted normally within the Session.
+
+
+##
+
+## Simulation
+
+
+
+1. Log into the myvtex environment as a call center operator.
+2. Impersonate a shopper and complete a purchase.
+3. Afterwards, while still impersonating the user, begin a new purchase, and note how the cart data will contain your call center operator's email within clientProfileData.
+
+
+##
+
+## Workaround
+
+
+If you need to create more than one order for the same shopper, make sure to redo the impersonation process in-between orders.
+
+
+
+
+
diff --git a/docs/known-issues/en/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md b/docs/known-issues/en/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
new file mode 100644
index 000000000..bb0a671f3
--- /dev/null
+++ b/docs/known-issues/en/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
@@ -0,0 +1,44 @@
+---
+title: 'Impersonation User Widget not shown if showModal is enabled'
+id: 19IHgjxPOEFC6HsAc5FD96
+status: PUBLISHED
+createdAt: 2024-06-03T15:55:49.797Z
+updatedAt: 2024-06-03T15:55:50.539Z
+publishedAt: 2024-06-03T15:55:50.539Z
+firstPublishedAt: 2024-06-03T15:55:50.539Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: impersonation-user-widget-not-shown-if-showmodal-is-enabled
+locale: en
+kiStatus: Backlog
+internalReference: 1043039
+---
+
+## Summary
+
+
+After impersonating another email, it's expected to show a "Stop Impersonation" button, but when the `showModal` is enabled, it doesn't show.
+
+
+##
+
+## Simulation
+
+
+
+- Enable "Use modal to switch company" in B2B Organizations settings;
+- Log in and impersonate another email.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
new file mode 100644
index 000000000..93cd1d1c5
--- /dev/null
+++ b/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -0,0 +1,49 @@
+---
+title: 'Import collection only accepts the order of products if import is made based on "skuId"'
+id: 7vXi2bDVyGHSMLluQi2ZWZ
+status: PUBLISHED
+createdAt: 2023-12-15T16:35:11.545Z
+updatedAt: 2023-12-21T18:55:17.090Z
+publishedAt: 2023-12-21T18:55:17.090Z
+firstPublishedAt: 2023-12-15T16:35:12.450Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid
+locale: en
+kiStatus: Fixed
+internalReference: 953862
+---
+
+## Summary
+
+
+When importing a spreadsheet of products into a collection, the user can choose to select the products either by "skuId", "productId", "skuRefId" or "productRefId".
+
+However, the order of the products in the collection is only being respected when the spreadsheet is using "skuId".
+
+
+##
+
+## Simulation
+
+
+
+1. Create a new collection;
+2. Use import spreadsheet to add products;
+3. Choose a field different from "skuId" to fill out the spreadsheet;
+4. Check that the order of products on the collections is different than the order on the spreadsheet.
+
+
+##
+
+## Workaround
+
+
+Use the column "skuId" to fill out the spreadsheet.
+
+
+
+
+
diff --git a/docs/known-issues/en/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md b/docs/known-issues/en/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
new file mode 100644
index 000000000..37e23dd75
--- /dev/null
+++ b/docs/known-issues/en/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
@@ -0,0 +1,45 @@
+---
+title: 'In some cases where there is a discount on the order, we have a discrepancy in the total value of the Items to invoice field in the order UI.'
+id: 20xiOKxpvdCODmDJDKunST
+status: PUBLISHED
+createdAt: 2024-05-06T20:17:01.162Z
+updatedAt: 2024-05-06T20:17:01.968Z
+publishedAt: 2024-05-06T20:17:01.968Z
+firstPublishedAt: 2024-05-06T20:17:01.968Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui
+locale: en
+kiStatus: Backlog
+internalReference: 1028210
+---
+
+## Summary
+
+
+It was identified that in some orders where there is a discount associated with one or more items, we may have a discrepancy in the total value of the "items to invoice" field in the order UI, as the calculation for this field takes into account the "sellingPrice" parameter, instead of the "priceDefinitions" parameter. Therefore, it is possible to notice differences of 0.01 or a little more from the total order value.
+
+We emphasize that this field is illustrative, as the main field is the total value (amount) of the order and there is NO discrepancy in this field.
+
+
+##
+
+## Simulation
+
+
+It is not possible to simulate this scenario.
+
+
+##
+
+## Workaround
+
+
+It wouldn't be a workaround, just a tip to invoice the order with the full amount, informed in the "amount" field, or in the case of partial invoices, inform the value of the item(s).
+
+
+
+
+
diff --git a/docs/known-issues/en/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md b/docs/known-issues/en/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
index 30394ad23..be5ce106a 100644
--- a/docs/known-issues/en/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
+++ b/docs/known-issues/en/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
@@ -3,8 +3,8 @@ title: 'In the partial return, the Tax values in the UI appear the total'
 id: 2I5a9hwrUo6s1htxOg8H1U
 status: PUBLISHED
 createdAt: 2022-04-11T13:15:06.455Z
-updatedAt: 2022-11-25T22:03:40.667Z
-publishedAt: 2022-11-25T22:03:40.667Z
+updatedAt: 2024-02-16T20:28:35.114Z
+publishedAt: 2024-02-16T20:28:35.114Z
 firstPublishedAt: 2022-04-11T13:15:07.028Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: in-the-partial-return-the-tax-values-in-the-ui-appear-the-total
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 559458
 ---
 
diff --git a/docs/known-issues/en/inability-to-make-partial-cancellation-with-mercadopagov1.md b/docs/known-issues/en/inability-to-make-partial-cancellation-with-mercadopagov1.md
index 047c3c6ca..1c32bb055 100644
--- a/docs/known-issues/en/inability-to-make-partial-cancellation-with-mercadopagov1.md
+++ b/docs/known-issues/en/inability-to-make-partial-cancellation-with-mercadopagov1.md
@@ -3,8 +3,8 @@ title: 'Inability to make partial cancellation with MercadoPagoV1'
 id: 59aimeqhjGVOVkP9f6A9ls
 status: PUBLISHED
 createdAt: 2022-06-28T16:44:19.059Z
-updatedAt: 2022-11-25T22:06:36.432Z
-publishedAt: 2022-11-25T22:06:36.432Z
+updatedAt: 2024-02-16T20:30:01.307Z
+publishedAt: 2024-02-16T20:30:01.307Z
 firstPublishedAt: 2022-06-28T16:44:19.331Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: inability-to-make-partial-cancellation-with-mercadopagov1
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 286738
 ---
 
diff --git a/docs/known-issues/en/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md b/docs/known-issues/en/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
index f703946b4..92ec9bbd5 100644
--- a/docs/known-issues/en/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
+++ b/docs/known-issues/en/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
@@ -3,8 +3,8 @@ title: 'Inability to use two or more different PayPal credentials for the same a
 id: 3cVh2SbvToH8yGOOYcWgDB
 status: PUBLISHED
 createdAt: 2022-03-03T18:39:24.442Z
-updatedAt: 2022-11-25T22:05:45.390Z
-publishedAt: 2022-11-25T22:05:45.390Z
+updatedAt: 2024-02-16T20:25:01.876Z
+publishedAt: 2024-02-16T20:25:01.876Z
 firstPublishedAt: 2022-03-03T18:39:25.004Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,17 +12,17 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 459704
 ---
 
 ## Summary
 
 
-When the customer registers two different affiliations in the same account using PayPalPlus, the platform does not update the cache for when there is a change in a payment rule, that is, it is possible to use only one credential per account.
-
+When the user registers two different affiliations in the same account using PayPalPlus, the platform does not update the cache for when there is a change in a payment rule, that is, it is possible to use only one credential per account.
 
 
+##
 
 ## Simulation
 
@@ -31,9 +31,14 @@ Register two different affiliations with different credentials and create rules
 Close two purchases, each with one of the rules, and in the transaction payload you can see that despite entering the correct rules, the merchant_id (identification of the account in which the money will fall) is the same.
 
 
+##
 
 ## Workaround
 
 
-There is no workaround
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/en/incomplete-transactions-appearing-with-brazilian-currency.md b/docs/known-issues/en/incomplete-transactions-appearing-with-brazilian-currency.md
new file mode 100644
index 000000000..965716999
--- /dev/null
+++ b/docs/known-issues/en/incomplete-transactions-appearing-with-brazilian-currency.md
@@ -0,0 +1,45 @@
+---
+title: 'Incomplete transactions appearing with Brazilian currency'
+id: 7g0j3FGa5E8kNi9PM3kBOf
+status: PUBLISHED
+createdAt: 2024-04-01T13:37:35.197Z
+updatedAt: 2024-04-01T13:37:36.114Z
+publishedAt: 2024-04-01T13:37:36.114Z
+firstPublishedAt: 2024-04-01T13:37:36.114Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: incomplete-transactions-appearing-with-brazilian-currency
+locale: en
+kiStatus: Backlog
+internalReference: 1007953
+---
+
+## Summary
+
+
+Incomplete transactions ("No name" customer) can appear in Transactions section with R$ currency, those are result of creation error (payment data was not sent) but the orders are created correctly in local currency.
+
+As these transactions are already lost there is no operational impact (visual bug).
+
+
+##
+
+## Simulation
+
+
+When finishing a payment at checkout you can reload the page to "break" the process and check in UI if the complete transaction creation failed (looking for the "No name" one).
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
+
diff --git a/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md b/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
index 0d04cb697..af63f0f64 100644
--- a/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
+++ b/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
@@ -28,7 +28,7 @@ In products with assembly options customization, a parent item has components, w
 3. Select the child item of the product, in the same quantity;
 4. Check the items in the cart.
 
-![KI assembly](https://images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/2296bfc12736ff882e99f2bf70645470/KI_assembly.png)
+![KI assembly](//images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/2296bfc12736ff882e99f2bf70645470/KI_assembly.png)
 
 Notice that the cart contains one more unit of the child item relative to the parent item.
 
diff --git a/docs/known-issues/en/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md b/docs/known-issues/en/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
new file mode 100644
index 000000000..13a80ea61
--- /dev/null
+++ b/docs/known-issues/en/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
@@ -0,0 +1,45 @@
+---
+title: 'Inconsistency payment terms information between Cost Center Details in My Organization and B2B Checkout Settings'
+id: VB70gSEsPOdTHVi3SPMaB
+status: PUBLISHED
+createdAt: 2023-06-20T18:29:30.859Z
+updatedAt: 2023-07-17T14:34:00.520Z
+publishedAt: 2023-07-17T14:34:00.520Z
+firstPublishedAt: 2023-06-20T18:29:31.475Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings
+locale: en
+kiStatus: Fixed
+internalReference: 847340
+---
+
+## Summary
+
+
+Inconsistency information between Cost Center Details in My Organization and B2B Checkout Settings where the My Organization shows a payment term deactivated, but the payment term is still shown when accessing checkout.
+
+
+##
+
+## Simulation
+
+
+
+- Access the My Organization in My Account with an "Organization Admin" role;
+- Click on the Cost Center;
+- In the "Payment Terms" section, deactivate a payment term;
+- Access the checkout and go to Payment; the deactivated option is still available.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md b/docs/known-issues/en/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
index 2e92625c2..0dd685071 100644
--- a/docs/known-issues/en/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
+++ b/docs/known-issues/en/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
@@ -3,8 +3,8 @@ title: 'Inconsistent price when the SKU has unit multiplier different than 1'
 id: NVtFiuWgptqa2gBEVmpOC
 status: PUBLISHED
 createdAt: 2022-09-05T13:05:50.789Z
-updatedAt: 2023-02-27T14:22:04.935Z
-publishedAt: 2023-02-27T14:22:04.935Z
+updatedAt: 2024-02-02T16:50:00.987Z
+publishedAt: 2024-02-02T16:50:00.987Z
 firstPublishedAt: 2022-09-05T13:05:51.613Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -19,22 +19,31 @@ internalReference: 651102
 ## Summary
 
 
-When some SKU contains a unit multiplier different than 1, in some situations, the price returned in store-graphql may have inconsistencies based on the division of the price returned from the simulation API:
+When some SKU contains a unit multiplier different than 1 (it can be int as 10 or 100, or float as 0.8, for example), in some situations, the price returned in store-graphql may have inconsistencies based on the division of the price returned from the simulation API:
 
 calculatedSellingPrice / (unitMultiplier * 100)
 
-It also applies to values in installments that do not consider unit multiplier value and the simulation call sends the value with the unit multiplier being considered
-
-Based on:
-https://vtexhelp.zendesk.com/agent/tickets/578022
+It can apply to all price values that use the unit multiplier such as in installments (that do not consider unit multiplier value and the simulation call sends the value with the unit multiplier being considered), PDP price, PLP price, or cart.
 
 
+##
 
 ## Simulation
 
 
+Check the simulation called for a product with a unit multiplier
+Check the Price of the product on a search page or using a product search query from search-graphql
+The prices can be divergent by cents
+
+
+##
 
 ## Workaround
 
 
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/en/incorrect-currency-on-payment-form.md b/docs/known-issues/en/incorrect-currency-on-payment-form.md
index f6a0a9b17..a1c3458e4 100644
--- a/docs/known-issues/en/incorrect-currency-on-payment-form.md
+++ b/docs/known-issues/en/incorrect-currency-on-payment-form.md
@@ -3,8 +3,8 @@ title: 'Incorrect currency on payment form'
 id: 636reFJs0MeHQJO0NlQV7Z
 status: PUBLISHED
 createdAt: 2022-03-13T21:29:33.920Z
-updatedAt: 2022-11-25T22:05:48.750Z
-publishedAt: 2022-11-25T22:05:48.750Z
+updatedAt: 2024-02-16T20:27:07.481Z
+publishedAt: 2024-02-16T20:27:07.481Z
 firstPublishedAt: 2022-03-13T21:29:34.493Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: incorrect-currency-on-payment-form
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 449286
 ---
 
diff --git a/docs/known-issues/en/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md b/docs/known-issues/en/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
new file mode 100644
index 000000000..378f533d7
--- /dev/null
+++ b/docs/known-issues/en/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
@@ -0,0 +1,50 @@
+---
+title: "Incorrect price update when a promotion doesn't apply the discount to all the same items in a cart"
+id: 1nXGR7pKjyc0Rmo0UzMOns
+status: PUBLISHED
+createdAt: 2024-05-01T20:07:04.369Z
+updatedAt: 2024-05-01T20:07:16.339Z
+publishedAt: 2024-05-01T20:07:16.339Z
+firstPublishedAt: 2024-05-01T20:07:05.363Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart
+locale: en
+kiStatus: Backlog
+internalReference: 1025539
+---
+
+## Summary
+
+
+When a promotion applies a discount to only one item of the same SKU (e.g. a More for Less promotion), if there is a second promotion for that same SKU, the discount calculation will be applied to the amount already discounted by the first promotion - resulting in a smaller discount than would be given if the second promotion were applied to the initial price of the SKU.
+
+The problem occurs in the price update when a promotion doesn't apply the discount to all the same items in a cart and this causes a "split" (two same items with different prices). When the second promotion is applied, it is applied to the wrong price.
+
+The bug is not given because of a specific promotion.
+
+
+##
+
+## Simulation
+
+
+
+- Create a More for Less promotion, giving the discount to only one item from the same SKU
+- Create a regular percentage promotion for the same SKU
+- At checkout, see that the discount given by the second promotion is based on the lower value of the SKU, which had already been discounted by the first promotion
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
new file mode 100644
index 000000000..2f5d3157f
--- /dev/null
+++ b/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -0,0 +1,52 @@
+---
+title: 'Incorrect refund calculation in Payout Split - "Value in recipients * is different than operation value *."'
+id: 7Fxtwnntpmi0DrUD5a603W
+status: PUBLISHED
+createdAt: 2024-07-29T15:07:07.716Z
+updatedAt: 2024-07-29T15:07:12.565Z
+publishedAt: 2024-07-29T15:07:12.565Z
+firstPublishedAt: 2024-07-29T15:07:12.565Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value
+locale: en
+kiStatus: Backlog
+internalReference: 1072285
+---
+
+## Summary
+
+
+When calling a refund (in transactions with payout split) the error below can happen with divergent amounts:
+
+(Example)
+
+    Vtex.Practices.ExceptionHandling.ValidationException: Value in recipients (45.00) is different than operation value (299.99). at Vtex.PaymentGateway.PaymentSplit.RecipientsBuilder.ValidateRecipientsValue(List`1 recipients, Decimal value)...
+
+
+Note that this KI is different from the below (calculation issue related to rounding - the values difference is small):
+
+https://help.vtex.com/en/known-issues/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value--3Wo9ltN7Ju0ZqVLAQZcd7m
+
+
+##
+
+## Simulation
+
+
+This seems to happen when the cart doesn't have marketplace products but we were not able to simulate this error.
+
+
+##
+
+## Workaround
+
+
+NA, merchants need to request manual refund directly with acquirer.
+
+
+
+
+
diff --git a/docs/known-issues/en/incorrect-shippingestimatedate-for-order-fob.md b/docs/known-issues/en/incorrect-shippingestimatedate-for-order-fob.md
index 874791913..bba34104b 100644
--- a/docs/known-issues/en/incorrect-shippingestimatedate-for-order-fob.md
+++ b/docs/known-issues/en/incorrect-shippingestimatedate-for-order-fob.md
@@ -3,8 +3,8 @@ title: 'Incorrect ShippingEstimateDate for order FOB'
 id: 3WLcrdw0tEdOvlMCYx9uyd
 status: PUBLISHED
 createdAt: 2023-01-05T20:26:07.074Z
-updatedAt: 2023-01-05T20:26:07.500Z
-publishedAt: 2023-01-05T20:26:07.500Z
+updatedAt: 2024-02-16T20:23:32.848Z
+publishedAt: 2024-02-16T20:23:32.848Z
 firstPublishedAt: 2023-01-05T20:26:07.500Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: incorrect-shippingestimatedate-for-order-fob
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 269104
 ---
 
diff --git a/docs/known-issues/en/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md b/docs/known-issues/en/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
new file mode 100644
index 000000000..8cdef98f1
--- /dev/null
+++ b/docs/known-issues/en/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
@@ -0,0 +1,48 @@
+---
+title: 'Incorrect/Lacking indexings for accounts where the accountname is different from the one registered on the fulfillmentEndpoint'
+id: 3TPRChOVHGpOYVeVo4zGOK
+status: PUBLISHED
+createdAt: 2024-06-14T16:45:39.257Z
+updatedAt: 2024-07-09T16:49:07.942Z
+publishedAt: 2024-07-09T16:49:07.942Z
+firstPublishedAt: 2024-06-14T16:45:40.852Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint
+locale: en
+kiStatus: Backlog
+internalReference: 1050023
+---
+
+## Summary
+
+
+Currently, a franchise account can have its fulFillmentEndpoint register differing from its "official" accountname, which is a common practice for specific seller<>marketplace architectures that need multiple prices and/or stock for distinct sales channels using the franchise feature with multiple sellers for the same franchise.
+
+Although this feature works in terms of displaying the needed content for shoppers, when sales-relevant data, such is price/stock is updated for the main seller of a given franchise, the other associated accounts are not correctly indexed alongside it, generating inconsistent availability and pricing displays among selling channels for a store.
+
+
+##
+
+## Simulation
+
+
+
+-  For a store that has multiple sellers and 1+ franchise accounts, configure 2+ sellers pointing, in the fulfillmentendpoint, towards the same franchise account in its seller settings.
+- Attempt to update price/stock data for any item of the franchise account.
+- Check the updated data on the other associated sellers that use the franchise account in their FFM endpoints, it will be outdated.
+
+
+##
+
+## Workaround
+
+
+Use the salesChannelMapping feature instead to implement this architecture instead
+
+
+
+
+
diff --git a/docs/known-issues/en/incorrectly-updated-inventory.md b/docs/known-issues/en/incorrectly-updated-inventory.md
index 8caec6bd8..33b47df01 100644
--- a/docs/known-issues/en/incorrectly-updated-inventory.md
+++ b/docs/known-issues/en/incorrectly-updated-inventory.md
@@ -3,8 +3,8 @@ title: 'Incorrectly updated inventory'
 id: 2M8DqNY1pGQWZnF9ZXNycq
 status: PUBLISHED
 createdAt: 2022-05-03T12:32:14.192Z
-updatedAt: 2022-11-25T21:56:29.965Z
-publishedAt: 2022-11-25T21:56:29.965Z
+updatedAt: 2024-02-16T20:24:24.243Z
+publishedAt: 2024-02-16T20:24:24.243Z
 firstPublishedAt: 2022-05-03T12:32:14.713Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: incorrectly-updated-inventory
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 556514
 ---
 
diff --git a/docs/known-issues/en/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md b/docs/known-issues/en/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
index a13fa2027..de79c58bd 100644
--- a/docs/known-issues/en/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
+++ b/docs/known-issues/en/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
@@ -3,8 +3,8 @@ title: 'Indexed price for a product considering the SKU with the highest instead
 id: 333mavl9dvgO4Jrgv8ECE6
 status: PUBLISHED
 createdAt: 2023-05-09T14:39:56.338Z
-updatedAt: 2023-05-09T14:39:56.771Z
-publishedAt: 2023-05-09T14:39:56.771Z
+updatedAt: 2023-08-18T17:24:09.314Z
+publishedAt: 2023-08-18T17:24:09.314Z
 firstPublishedAt: 2023-05-09T14:39:56.771Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price
 locale: en
-kiStatus: Scheduled
+kiStatus: Fixed
 internalReference: 822120
 ---
 
diff --git a/docs/known-issues/en/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md b/docs/known-issues/en/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
index 0255df8b7..4a603cc8b 100644
--- a/docs/known-issues/en/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
+++ b/docs/known-issues/en/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
@@ -3,8 +3,8 @@ title: 'Individual warehouse (inventory) exports do not work on seller portal ac
 id: 7GoxwXFUWnebmCqF1sm7rm
 status: PUBLISHED
 createdAt: 2022-10-24T19:21:06.182Z
-updatedAt: 2022-11-25T21:43:01.961Z
-publishedAt: 2022-11-25T21:43:01.961Z
+updatedAt: 2024-07-01T18:48:39.414Z
+publishedAt: 2024-07-01T18:48:39.414Z
 firstPublishedAt: 2022-10-24T19:21:06.574Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 684464
 ---
 
diff --git a/docs/known-issues/en/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md b/docs/known-issues/en/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
new file mode 100644
index 000000000..6ef6f7721
--- /dev/null
+++ b/docs/known-issues/en/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
@@ -0,0 +1,50 @@
+---
+title: 'Inference Invoice System is not working properly when there are same SKUid in different array items'
+id: 3fSQGwIPj0ekewMuaxPPEe
+status: PUBLISHED
+createdAt: 2024-03-28T19:00:12.852Z
+updatedAt: 2024-04-04T13:33:04.775Z
+publishedAt: 2024-04-04T13:33:04.775Z
+firstPublishedAt: 2024-03-28T19:00:14.053Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items
+locale: en
+kiStatus: Backlog
+internalReference: 1008459
+---
+
+## Summary
+
+
+Some orders has same SKUid in separated array of items it happens at the purchase moment on checkout for different reasons as discount to be apllied for example.
+This not a problem but a condition for a purchase calculation.
+
+The problem is at the phase of invoice for that items. Sometimes the inference system can not match the itens to be insert correctly at the refrence items on packageAttachment, because of the same SKUid and selling prices.
+Even the customer sends the quantity of itens correctly on the inference it will be wrong.
+
+Is possible to see the difference on SNO system versus the packageAttachment items on order.
+
+
+##
+
+## Simulation
+
+
+Create a order with a more than one quantity items and apply some discount, creating an order with more than one array of itens with different selling price. After that try to invoice all items of order.
+
+
+
+##
+
+## Workaround
+
+
+There is no workarround for that.
+
+
+
+
+
diff --git a/docs/known-issues/en/infocard-mobile-images-wont-apply.md b/docs/known-issues/en/infocard-mobile-images-wont-apply.md
new file mode 100644
index 000000000..c922f40b7
--- /dev/null
+++ b/docs/known-issues/en/infocard-mobile-images-wont-apply.md
@@ -0,0 +1,47 @@
+---
+title: "Infocard mobile images won't apply"
+id: 1vx5fwa5nL3SO27HpihLFd
+status: PUBLISHED
+createdAt: 2024-02-19T19:12:18.516Z
+updatedAt: 2024-02-19T19:12:19.362Z
+publishedAt: 2024-02-19T19:12:19.362Z
+firstPublishedAt: 2024-02-19T19:12:19.362Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: infocard-mobile-images-wont-apply
+locale: en
+kiStatus: Backlog
+internalReference: 909647
+---
+
+## Summary
+
+
+When you change the image on an infocard to be displayed on the mobile version, it won't be shown. Instead, the main image stays being shown.
+
+
+##
+
+## Simulation
+
+
+
+- Open an infocard on site-editor for editing.
+- Change the main image of the infocard and apply.
+- Change the image for the mobile version of the infocard and apply.
+- Observe the results, the image will still be the main image instead of the one set for mobile when in mobile mode.
+
+
+##
+
+## Workaround
+
+
+Instead, try to use a flex layout with a store image + other apps to create the desired banner.
+
+
+
+
+
diff --git a/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
new file mode 100644
index 000000000..b1b63a22c
--- /dev/null
+++ b/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -0,0 +1,50 @@
+---
+title: 'Insert SKU File API doesnt accept URLs from servers that require "User Agents"'
+id: 5Z1PmRXyW78mohsKTMQfzj
+status: PUBLISHED
+createdAt: 2024-07-22T19:49:14.140Z
+updatedAt: 2024-07-22T19:49:15.319Z
+publishedAt: 2024-07-22T19:49:15.319Z
+firstPublishedAt: 2024-07-22T19:49:15.319Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents
+locale: en
+kiStatus: Backlog
+internalReference: 1069222
+---
+
+## Summary
+
+
+A **user-agent** is a string of text that a web browser or other client sends to a web server in an HTTP request header to identify itself. This string contains information about the browser type, operating system, and sometimes additional details like the browser version and the rendering engine used.
+
+This is often requested as a security measure by servers, such as ones that host images, that can be passed via URL in the request body of the insert SKU file API.
+
+This kind of authentication, however, is not currently supported by the VTEX APIs.
+
+
+##
+
+## Simulation
+
+
+1 - Using either the Create or Update (write methods) SKU file API passing down an URL that has server-side user agent requirement to fetch data https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file
+
+2 - A 40x type response will be shown, either a generic 400 or a more specific 403 depending on the type of response implemented.
+
+
+
+##
+
+## Workaround
+
+
+Either opt for the file upload va spreadsheet, form-data (using the APIs) or disable the user-agent requirements on the server-side.
+
+
+
+
+
diff --git a/docs/known-issues/en/installment-options-not-updating-automatically-on-pdpplp.md b/docs/known-issues/en/installment-options-not-updating-automatically-on-pdpplp.md
new file mode 100644
index 000000000..1854b3339
--- /dev/null
+++ b/docs/known-issues/en/installment-options-not-updating-automatically-on-pdpplp.md
@@ -0,0 +1,46 @@
+---
+title: 'Installment options not updating automatically on PDP/PLP'
+id: 1PSjCEZyKatCZ9Q1W1zQOc
+status: PUBLISHED
+createdAt: 2024-02-23T12:31:32.446Z
+updatedAt: 2024-02-23T12:31:33.262Z
+publishedAt: 2024-02-23T12:31:33.262Z
+firstPublishedAt: 2024-02-23T12:31:33.262Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: installment-options-not-updating-automatically-on-pdpplp
+locale: en
+kiStatus: Backlog
+internalReference: 987467
+---
+
+## Summary
+
+
+When a account changes the installment options of a product, despite the product being correctly indexed, the installment options do not update on the PLP or the PDP (sometimes both).
+
+
+##
+
+## Simulation
+
+
+
+1. Create an installment option and check that it reflects correctly on PDP/PLP
+2. Update this same installment
+3. Check that not all PDPs and PLPs updated to the new correct information.
+
+
+##
+
+## Workaround
+
+
+Reindex the affected products again.
+
+
+
+
+
diff --git a/docs/known-issues/en/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md b/docs/known-issues/en/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
index 1a81776c1..ceedfa6c1 100644
--- a/docs/known-issues/en/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
+++ b/docs/known-issues/en/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
@@ -3,8 +3,8 @@ title: 'Intelligent Search Banner update via Image URL does not work correctly'
 id: bMFrVUmfbjvTWs4Ag6U57
 status: PUBLISHED
 createdAt: 2023-01-17T14:34:02.195Z
-updatedAt: 2023-01-17T14:34:10.348Z
-publishedAt: 2023-01-17T14:34:10.348Z
+updatedAt: 2023-09-06T22:35:01.155Z
+publishedAt: 2023-09-06T22:35:01.155Z
 firstPublishedAt: 2023-01-17T14:34:02.912Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -19,7 +19,7 @@ internalReference: 734833
 ## Summary
 
 
-In Admin V4, in the Banners module, the user has the possibility to create or update already created banners. When selecting a banner for updating, he can choose between using an HTML field or inserting a direct image link with an external URL. When selecting to insert the banner via a direct image link, the GraphQL query `setBanner` is triggered, which is currently not working correctly, returning `syntaxError`, consequently, error 500.
+In Admin V4, in the Banners module, the user has the possibility to create or update already created banners. When selecting a banner for updating, he can choose between using an HTML field or inserting a direct image link with an external URL. When selecting to insert the banner via a direct image link, the GraphQL query is triggered, which is currently not working correctly, returning `syntaxError`, consequently, error 500.
 
 
 ##
@@ -39,7 +39,7 @@ When clicking Save, the screen will show a GraphQL error;
 ## Workaround
 
 
-Create a new banner with the same specifications (the banner creation query is `createBanner` and is working correctly);
+N/A
 
 
 
diff --git a/docs/known-issues/en/intelligent-search-language-settings-not-in-sync-with-store-configurations.md b/docs/known-issues/en/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
new file mode 100644
index 000000000..de802aa52
--- /dev/null
+++ b/docs/known-issues/en/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
@@ -0,0 +1,64 @@
+---
+title: 'Intelligent Search language settings not in sync with store configurations'
+id: 1GqoAyUSbTxwHvzoMoAYfD
+status: PUBLISHED
+createdAt: 2024-02-27T21:30:40.309Z
+updatedAt: 2024-03-06T15:38:20.358Z
+publishedAt: 2024-03-06T15:38:20.358Z
+firstPublishedAt: 2024-02-27T21:30:41.209Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: intelligent-search-language-settings-not-in-sync-with-store-configurations
+locale: en
+kiStatus: Backlog
+internalReference: 990343
+---
+
+## Summary
+
+
+The primary language for Intelligent Search is not automatically updated according to the trade policy and binding settings, making it out of sync.
+
+For single-language stores, Intelligent Search contents, such as synonyms, merchandising rules, search banners, and search redirects, are created on top of the locales registered at the binding. The storefront is rendered based also on the trade policy, which may override the binding and won't match the registered content.
+
+For multi-language stores, potentially, it also affects the provided translations at the storefront and APIs.
+
+
+##
+
+## Simulation
+
+
+
+- Create a store in "pt-BR";
+- Enable/configure the Intelligent Search module;
+- Change the trade policy from "pt-BR" to "en-US";
+- Single-language:
+  - Keep the binding as "pt-BR";
+  - Create Intelligent Search content;
+  - Access the storefront page that should present the registered content;
+  - The content/behavior won't be visible.
+- Multi-language:
+  - Register the products in English;
+  - Add Portuguese as a second/alternate language at the bindings
+  - Register catalog translations for Portuguese;
+  - In this scenario, navigation between both languages may present problems.
+
+
+
+##
+
+## Workaround
+
+
+Ensure that bindings and trade policies match otherwise, the search content will be invalid.
+
+Previously registered content won't follow the new primary language if it changes; it will remain attached to their creation language. It's necessary to register at least two locales at the bindings configuration (the old/unexpected language and the new/expected language) to see the language selector in the content editor so you can fix them manually to use the expected language. Another method is recreating the content.
+
+In some scenarios, such as multi-language and catalog translations, you may also need to contact our support to review internal language settings for Intelligent Search.
+
+
+
+
diff --git a/docs/known-issues/en/intelligent-search-not-capturing-sales-events-for-faststore.md b/docs/known-issues/en/intelligent-search-not-capturing-sales-events-for-faststore.md
new file mode 100644
index 000000000..82290d80d
--- /dev/null
+++ b/docs/known-issues/en/intelligent-search-not-capturing-sales-events-for-faststore.md
@@ -0,0 +1,42 @@
+---
+title: 'Intelligent Search not capturing sales events for FastStore'
+id: 4sT3tm37DP6E6jWzYNHJQe
+status: PUBLISHED
+createdAt: 2024-06-05T22:21:23.343Z
+updatedAt: 2024-06-05T22:21:24.206Z
+publishedAt: 2024-06-05T22:21:24.206Z
+firstPublishedAt: 2024-06-05T22:21:24.206Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: intelligent-search-not-capturing-sales-events-for-faststore
+locale: en
+kiStatus: Scheduled
+internalReference: 1045163
+---
+
+## Summary
+
+
+Intelligent Search is not capturing finished order events for stores using FastStore. These events compose the relevance criteria and product sorting by sales.
+
+
+##
+
+## Simulation
+
+
+The scenario can be reproduced in any store using FastStore. The easiest way to see the problem is by noticing that the search analytics report won't compute sales.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md b/docs/known-issues/en/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
new file mode 100644
index 000000000..f9398d636
--- /dev/null
+++ b/docs/known-issues/en/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
@@ -0,0 +1,41 @@
+---
+title: 'Intelligent Search Redirect settings search bar is case sensitive'
+id: 5QEkcyhCQWyw093UkDCeOq
+status: PUBLISHED
+createdAt: 2023-09-26T23:50:50.661Z
+updatedAt: 2023-09-26T23:50:51.661Z
+publishedAt: 2023-09-26T23:50:51.661Z
+firstPublishedAt: 2023-09-26T23:50:51.661Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: intelligent-search-redirect-settings-search-bar-is-case-sensitive
+locale: en
+kiStatus: Backlog
+internalReference: 361894
+---
+
+## Summary
+
+
+The Intelligent Search Redirect settings page has a search bar to help find specific redirect settings, but it is case sensitive and will only find terms if they match exactly.
+
+
+##
+
+## Simulation
+
+
+Access `/admin/search/redirects`.
+
+Search for a setting name, but changing one letter to uppercase. The search won't fetch any result.
+
+
+##
+
+## Workaround
+
+
+Generate route names with a consistent pattern, only lower case, only uppercase or camel case.
+
diff --git a/docs/known-issues/en/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md b/docs/known-issues/en/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
new file mode 100644
index 000000000..260ac0cea
--- /dev/null
+++ b/docs/known-issues/en/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
@@ -0,0 +1,47 @@
+---
+title: 'Intelligent Search word analyzer not normalizing gender in Portuguese words'
+id: 2oVUQnXZK6FNXg7co88C1B
+status: PUBLISHED
+createdAt: 2024-07-26T22:55:32.746Z
+updatedAt: 2024-07-26T22:55:46.558Z
+publishedAt: 2024-07-26T22:55:46.558Z
+firstPublishedAt: 2024-07-26T22:55:33.875Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words
+locale: en
+kiStatus: Backlog
+internalReference: 1072003
+---
+
+## Summary
+
+
+It's expected that searched terms are normalized between their different forms (plural/singular, gender, and other possibilities), a process formally called stemming. The analyzer is different for each language to match their needs.
+
+The analyzer for Portuguese is not normalizing the gender of words.
+
+
+##
+
+## Simulation
+
+
+Consider a word registered in different products with different genders, such as "camiseta listrada" and "vestido listrado".
+
+Although "listrada" and "listrado" are the same word but in different gender forms, searching "listrada" won't return the "vestidos" – and vice-versa.
+
+
+##
+
+## Workaround
+
+
+Register bidirectional synonyms for words with relevant gender form variations.
+
+
+
+
+
diff --git a/docs/known-issues/en/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md b/docs/known-issues/en/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
new file mode 100644
index 000000000..6e4f0d726
--- /dev/null
+++ b/docs/known-issues/en/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
@@ -0,0 +1,46 @@
+---
+title: 'Interacting with the address component while some data on the UI is still in a loading state changes the address insertion mode'
+id: 7t3jzIpIppmZDAc9R2BgpS
+status: PUBLISHED
+createdAt: 2023-09-13T20:39:43.294Z
+updatedAt: 2023-09-13T20:39:44.079Z
+publishedAt: 2023-09-13T20:39:44.079Z
+firstPublishedAt: 2023-09-13T20:39:44.079Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode
+locale: en
+kiStatus: Backlog
+internalReference: 423811
+---
+
+## Summary
+
+
+When the user chooses to change their address while some respective data is still loading on the page, the address component changes from geolocation to the component with a dropdown. The data can be, for example, selecting a store to pick up. While the data loads in the interface, the user clicks on "change address", with that, the return address is in another component, not in the geolocation component.
+
+
+##
+
+## Simulation
+
+
+
+- Configure an account to use geocoordinates at checkout;
+- Search for an address in the shipping step;
+- Click on Change while the page is loading;
+- The address component will change and ask you to fill out the address information
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md b/docs/known-issues/en/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
new file mode 100644
index 000000000..b564278d7
--- /dev/null
+++ b/docs/known-issues/en/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
@@ -0,0 +1,45 @@
+---
+title: 'Interacting with the payment component while is still in a loading state sends the wrong payment option'
+id: 4kSvM6fti8YfgcUyl4qFJs
+status: PUBLISHED
+createdAt: 2023-12-12T22:07:58.762Z
+updatedAt: 2023-12-12T22:07:59.474Z
+publishedAt: 2023-12-12T22:07:59.474Z
+firstPublishedAt: 2023-12-12T22:07:59.474Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option
+locale: en
+kiStatus: Backlog
+internalReference: 952086
+---
+
+## Summary
+
+
+When the shopper changes the payment method while the payment component is still loading on the page, if the payment method has options, the payment sent to the orderForm is wrong. When this behavior happen, the order is not created and a message to review the payment information is shown.
+
+
+##
+
+## Simulation
+
+
+
+- Add items to the cart and move until payment data;
+- Click on a different payment method while the page is loading and select another option inside the component;
+- The payment sent to the orderForm is wrong, being the first option.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/intermitent-site-editor-content-loss.md b/docs/known-issues/en/intermitent-site-editor-content-loss.md
new file mode 100644
index 000000000..84738d079
--- /dev/null
+++ b/docs/known-issues/en/intermitent-site-editor-content-loss.md
@@ -0,0 +1,49 @@
+---
+title: 'Intermitent Site Editor content loss'
+id: 3a5MlAoD2Z7Gu6HDS8wihD
+status: PUBLISHED
+createdAt: 2022-07-05T17:07:24.733Z
+updatedAt: 2024-03-21T20:37:27.369Z
+publishedAt: 2024-03-21T20:37:27.369Z
+firstPublishedAt: 2022-07-05T17:07:25.091Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: intermitent-site-editor-content-loss
+locale: en
+kiStatus: Scheduled
+internalReference: 610533
+---
+
+## Summary
+
+
+Every content change in Site Editor inserts changes to the content.json file, which is stored in a bucket on AWS S3. Some customers have reported a loss of Site Editor content after some common procedures of theme updates.
+
+
+##
+
+## Simulation
+
+
+The scenario is intermittent, however, it has been reported in two different scenarios:
+
+**1. When promoting a production workspace to master:**
+Customers reported that when promoting a production workspace, containing changes in components, to the master environment, there was a loss of content in other workspaces.
+
+**2. When installing a new version in a test workspace:**
+Customers reported that when installing a new theme version in a test workspace, the content of the category pages was deleted.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/internalsearcherror-timeouts-on-portal.md b/docs/known-issues/en/internalsearcherror-timeouts-on-portal.md
new file mode 100644
index 000000000..c85350e8b
--- /dev/null
+++ b/docs/known-issues/en/internalsearcherror-timeouts-on-portal.md
@@ -0,0 +1,45 @@
+---
+title: 'InternalSearchError timeouts on Portal'
+id: 6D6mdJ3zQypy1lcuht7WuU
+status: PUBLISHED
+createdAt: 2024-06-03T15:25:56.353Z
+updatedAt: 2024-07-30T13:55:06.518Z
+publishedAt: 2024-07-30T13:55:06.518Z
+firstPublishedAt: 2024-06-03T15:25:57.378Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: internalsearcherror-timeouts-on-portal
+locale: en
+kiStatus: Backlog
+internalReference: 1043003
+---
+
+## Summary
+
+
+Currently, stores using the legacy Portal search can face, when using multiple filters on their store, such as collection filters on templates, can face random, intermittent timeouts that are often displayed as a "Something Went Wrong" error for customers.
+
+This issue is, internally, a timeout, that is being analysed by the tech teams to have its time increased.
+
+
+##
+
+## Simulation
+
+
+This error is highly intermittent and hard to consistently replicate. It's often more frequent in accounts using several collection filters in their templates, but there's no reliable way to replicate it.
+
+
+##
+
+## Workaround
+
+
+While the timeouts are not further investigated and increased, reducing the amount of filters being used in searches and menus is recommended, yet not guaranteed to completely eliminate such timeouts, but significantly reduce them.
+
+
+
+
+
diff --git a/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
new file mode 100644
index 000000000..70b572c14
--- /dev/null
+++ b/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -0,0 +1,47 @@
+---
+title: '"Invalid postal code" message in Checkout UI when address is in available addresses with different country'
+id: 4VggIx4xWPNW6OBIrQ0js4
+status: PUBLISHED
+createdAt: 2024-06-21T17:08:59.860Z
+updatedAt: 2024-06-21T17:09:00.771Z
+publishedAt: 2024-06-21T17:09:00.771Z
+firstPublishedAt: 2024-06-21T17:09:00.771Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country
+locale: en
+kiStatus: Backlog
+internalReference: 1053959
+---
+
+## Summary
+
+
+Checkout UI uses the country registered in its state to validate the postal code input.
+
+When addresses are registered in available addresses, but the orderForm is changed to another sales channel, and this sales channel has a different country to ship, the message "Invalid postal code" is shown right below the postal code input, not being able to move forward with the purchase.
+
+
+##
+
+## Simulation
+
+
+
+- Assemble a cart and add an address;
+- Change the sales channel, where it ships to a different country;
+- Try to add the new postal code; the "Invalid postal code" is shown.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/inventory-notifications-to-indexer-are-cached.md b/docs/known-issues/en/inventory-notifications-to-indexer-are-cached.md
new file mode 100644
index 000000000..9b01810e9
--- /dev/null
+++ b/docs/known-issues/en/inventory-notifications-to-indexer-are-cached.md
@@ -0,0 +1,52 @@
+---
+title: 'Inventory notifications to indexer are cached'
+id: 2eFmUbO1PR7ahxAGiMkqZd
+status: PUBLISHED
+createdAt: 2023-10-05T12:48:05.930Z
+updatedAt: 2024-05-14T11:26:36.897Z
+publishedAt: 2024-05-14T11:26:36.897Z
+firstPublishedAt: 2023-10-05T12:48:06.727Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: inventory-notifications-to-indexer-are-cached
+locale: en
+kiStatus: Fixed
+internalReference: 914545
+---
+
+## Summary
+
+
+When a franchise account or seller notifies the main account (or marketplace) about inventory changes, the account sends the product to indexer in order to have the most updated information.
+
+The system responsible to receive the notifications and pass them to indexer is Broadcaster.
+
+The problem is that the workflow Availability -> Broadcaster -> Indexer is working on a very fast rhythm and in some cases the information is still cached. That way the Indexer remains with the old information until a new indexation.
+
+
+##
+
+## Simulation
+
+
+There is not an easy way to simulate this scenario, since it doesn't happen in every occasion.
+The process should be:
+
+1. Franchise account updates an inventory;
+2. Broadcaster sends the product to Indexer;
+3. Indexer updates the main account sku with the old info.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/inventory-reserved-items-error.md b/docs/known-issues/en/inventory-reserved-items-error.md
index ac15d34de..572d4c268 100644
--- a/docs/known-issues/en/inventory-reserved-items-error.md
+++ b/docs/known-issues/en/inventory-reserved-items-error.md
@@ -1,10 +1,10 @@
 ---
 title: 'Inventory Reserved Items Error'
 id: 37cO3T4D0exvOMhStKYds9
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-18T15:13:46.087Z
-updatedAt: 2022-06-27T12:33:44.492Z
-publishedAt: 2022-06-20T12:39:37.793Z
+updatedAt: 2024-07-03T20:14:35.313Z
+publishedAt: 2024-07-03T20:14:35.313Z
 firstPublishedAt: 2022-05-18T15:13:46.568Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,27 +12,33 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: inventory-reserved-items-error
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 347924
 ---
 
 ## Summary
 
 
-Checking the items of reserved status on Inventory Management there is an error to show the orders related.
-It is not possible to see the orders clicking on the number of reserved itens, shows the message error "There was an error loading reservations. Please try again."
 
+Checking the items of reserved status on **Inventory Management**, there is an error to show the orders related.
 
+It is not possible to see the orders clicking on the number of reserved items, shows the message error "There was an error loading reservations. Please try again."
+
+
+##
 
 ## Simulation
 
 
+
 The simulation is not possible.
 
 
+##
 
 ## Workaround
 
 
+
 There is no workaround available.
 
diff --git a/docs/known-issues/en/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/en/invisible-characters-in-category-names-cause-page-not-found-errors.md
new file mode 100644
index 000000000..27503b7c8
--- /dev/null
+++ b/docs/known-issues/en/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -0,0 +1,46 @@
+---
+title: "Invisible Characters in Category Names Cause 'Page Not Found' Errors"
+id: 4np2BZUF1EmlLmV0KTpnrf
+status: PUBLISHED
+createdAt: 2024-07-05T13:11:13.031Z
+updatedAt: 2024-07-05T13:11:14.090Z
+publishedAt: 2024-07-05T13:11:14.090Z
+firstPublishedAt: 2024-07-05T13:11:14.090Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: invisible-characters-in-category-names-cause-page-not-found-errors
+locale: en
+kiStatus: Backlog
+internalReference: 1061149
+---
+
+## Summary
+
+
+When creating categories via API or the admin panel, the category name is not properly validated, allowing invisible characters to be included. Since the category name is used to generate the category URL, these invisible characters are also included in the URL. This results in the category page not functioning correctly and returning a "Page Not Found" error.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a category with an invisible character in its name using the API or admin panel.
+2. Access the API URL for this category.
+3. Observe the "Page Not Found" error.
+
+
+##
+
+## Workaround
+
+
+
+The workaround is to remove the invisible character from the category name, which will also update the URL of the page, resolving the issue.
+
+
+
+
diff --git a/docs/known-issues/en/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md b/docs/known-issues/en/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
index 341cccdb5..54eb478a3 100644
--- a/docs/known-issues/en/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
+++ b/docs/known-issues/en/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
@@ -3,8 +3,8 @@ title: 'isAvailablePerSalesChannel parameter does not work as expected on the Se
 id: 6vexCZQTib8fFI6sCSTdWL
 status: PUBLISHED
 createdAt: 2022-09-12T16:03:25.215Z
-updatedAt: 2022-11-25T21:43:40.015Z
-publishedAt: 2022-11-25T21:43:40.015Z
+updatedAt: 2024-02-16T20:24:54.890Z
+publishedAt: 2024-02-16T20:24:54.890Z
 firstPublishedAt: 2022-09-12T16:03:25.837Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 656284
 ---
 
diff --git a/docs/known-issues/en/issue-on-the-explained-search-for-searches-with-accent-marks.md b/docs/known-issues/en/issue-on-the-explained-search-for-searches-with-accent-marks.md
index 5c036bc6d..0b35ac379 100644
--- a/docs/known-issues/en/issue-on-the-explained-search-for-searches-with-accent-marks.md
+++ b/docs/known-issues/en/issue-on-the-explained-search-for-searches-with-accent-marks.md
@@ -3,8 +3,8 @@ title: 'Issue on the Explained Search for searches with accent marks'
 id: 5rh2FSzIeSjnO7bUlEkJ9S
 status: PUBLISHED
 createdAt: 2022-02-23T21:59:57.268Z
-updatedAt: 2022-11-25T21:58:45.841Z
-publishedAt: 2022-11-25T21:58:45.841Z
+updatedAt: 2024-02-16T20:28:06.748Z
+publishedAt: 2024-02-16T20:28:06.748Z
 firstPublishedAt: 2022-02-23T21:59:57.508Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: issue-on-the-explained-search-for-searches-with-accent-marks
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 434752
 ---
 
diff --git a/docs/known-issues/en/issue-on-translating-titles-for-some-facets.md b/docs/known-issues/en/issue-on-translating-titles-for-some-facets.md
index 1e26995f0..d819074da 100644
--- a/docs/known-issues/en/issue-on-translating-titles-for-some-facets.md
+++ b/docs/known-issues/en/issue-on-translating-titles-for-some-facets.md
@@ -3,8 +3,8 @@ title: 'Issue on translating titles for some facets'
 id: iG3Kb1AfH7QIqYn1ewnuw
 status: PUBLISHED
 createdAt: 2023-03-22T19:26:31.477Z
-updatedAt: 2023-03-22T19:26:31.933Z
-publishedAt: 2023-03-22T19:26:31.933Z
+updatedAt: 2023-10-27T00:51:10.361Z
+publishedAt: 2023-10-27T00:51:10.361Z
 firstPublishedAt: 2023-03-22T19:26:31.933Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: issue-on-translating-titles-for-some-facets
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 776353
 ---
 
@@ -35,9 +35,5 @@ Check the path that is being mounted also check if the store is multilanguage, a
 ## Workaround
 
 
-There's none
-
-
-
-
+N/A
 
diff --git a/docs/known-issues/en/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md b/docs/known-issues/en/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
new file mode 100644
index 000000000..3d2655ab2
--- /dev/null
+++ b/docs/known-issues/en/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
@@ -0,0 +1,43 @@
+---
+title: 'Issue with session APIs using public properties beginning with the same prefix'
+id: RAoSKg2hwwiC6L7wFPyNv
+status: PUBLISHED
+createdAt: 2023-08-21T20:00:45.403Z
+updatedAt: 2023-08-21T20:11:44.751Z
+publishedAt: 2023-08-21T20:11:44.751Z
+firstPublishedAt: 2023-08-21T20:00:46.132Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix
+locale: en
+kiStatus: Backlog
+internalReference: 885011
+---
+
+## Summary
+
+
+The session API is generating some inconsistencies. The engineering team has identified the bug, the bug is related with properties beginning with the same word.
+
+
+##
+
+## Simulation
+
+
+If you make a POST sending 2 public values with the same prefix, the API only receives one. If you try again, making the same POST sending the same 2 values, the API receives both.
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/issues-inserting-values-in-loyalty-gift-card-at-checkout.md b/docs/known-issues/en/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
new file mode 100644
index 000000000..f5e61e720
--- /dev/null
+++ b/docs/known-issues/en/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
@@ -0,0 +1,44 @@
+---
+title: 'Issues inserting values in loyalty gift card at checkout'
+id: 74bFvs0PmQzRGzkOdnwiLw
+status: PUBLISHED
+createdAt: 2023-11-28T17:16:34.758Z
+updatedAt: 2023-11-28T17:16:35.407Z
+publishedAt: 2023-11-28T17:16:35.407Z
+firstPublishedAt: 2023-11-28T17:16:35.407Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: issues-inserting-values-in-loyalty-gift-card-at-checkout
+locale: en
+kiStatus: Backlog
+internalReference: 943629
+---
+
+## Summary
+
+
+When using loyalty gift card users can face bad experience when selecting the option "Use only part of the value", there's no "Add" button after filling "Value to use" (the input is automatically accepted) so if a value is not filled fast enough it will be updated with the first digits only making the user to repeat the procedure. This experience is worse via mobile website.
+
+
+##
+
+## Simulation
+
+
+After creating a loyalty gift card to an email it will appear at checkout and you can proceed with the above described scenario.
+
+https://support.vtex.com/hc/en-us/articles/12897485276443
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/en/issues-with-billingaddress-leading-to-transaction-cancellations.md b/docs/known-issues/en/issues-with-billingaddress-leading-to-transaction-cancellations.md
new file mode 100644
index 000000000..f21099dbd
--- /dev/null
+++ b/docs/known-issues/en/issues-with-billingaddress-leading-to-transaction-cancellations.md
@@ -0,0 +1,48 @@
+---
+title: 'Issues with BillingAddress Leading to Transaction Cancellations'
+id: 14RT6S4Hm7H30L0FBzdDRY
+status: PUBLISHED
+createdAt: 2024-05-06T16:34:12.989Z
+updatedAt: 2024-05-06T16:34:14.299Z
+publishedAt: 2024-05-06T16:34:14.299Z
+firstPublishedAt: 2024-05-06T16:34:14.299Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: issues-with-billingaddress-leading-to-transaction-cancellations
+locale: en
+kiStatus: Backlog
+internalReference: 1027901
+---
+
+## Summary
+
+
+
+Transactions are being canceled during the antifraud analysis due to missing essential information in the `billingAddress`.
+
+The `billingAddress` is sent during the payment process and can either be a copy of the `shippingAddress` if the user chooses not to differentiate them (by marking `isBillingAddressDifferent` as `false`) during checkout. Alternatively, it can be a new address provided by the user if the `isBillingAddressDifferent` option is marked as `true`. This address is used in the antifraud authorization request, and the absence of mandatory information can lead to transaction cancellations.
+
+We have observed that this behavior occurs with payments made using new cards, which have not been previously saved in the store, and when the user chooses not to differentiate the addresses (`isBillingAddressDifferent`: `false`). Importantly, the `shippingAaddress` contains all the required fields correctly filled out, while the `billingAddress`, which should be a copy of the `shippingAddress`, remains incomplete.
+
+
+##
+
+## Simulation
+
+
+We were not able to replicate this issue
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/issues-with-my-account-links.md b/docs/known-issues/en/issues-with-my-account-links.md
new file mode 100644
index 000000000..d2f527062
--- /dev/null
+++ b/docs/known-issues/en/issues-with-my-account-links.md
@@ -0,0 +1,45 @@
+---
+title: 'Issues with My Account links'
+id: 1p23CCNhJwnEXm501P9Nxh
+status: PUBLISHED
+createdAt: 2023-07-03T17:26:59.597Z
+updatedAt: 2023-07-03T17:27:00.108Z
+publishedAt: 2023-07-03T17:27:00.108Z
+firstPublishedAt: 2023-07-03T17:27:00.108Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: issues-with-my-account-links
+locale: en
+kiStatus: Backlog
+internalReference: 522514
+---
+
+## Summary
+
+
+Links in My Account (header menu) do not work if the user is already in the My Account section
+
+
+##
+
+## Simulation
+
+
+Accessing the My account page
+Click on the link from the header menu (like Orders option, for example)
+Verify the url get modified, but the page does not load
+
+
+##
+
+## Workaround
+
+
+There is no workaround.
+
+
+
+
+
diff --git a/docs/known-issues/en/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md b/docs/known-issues/en/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
new file mode 100644
index 000000000..506904b14
--- /dev/null
+++ b/docs/known-issues/en/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
@@ -0,0 +1,51 @@
+---
+title: 'It is not possible to add an item with attachment to the cart if there is already another unit of this item without attachment in the cart'
+id: 3l41VmdtPCxUjYChuO7o9O
+status: PUBLISHED
+createdAt: 2021-09-15T15:24:52.309Z
+updatedAt: 2024-02-02T15:01:32.297Z
+publishedAt: 2024-02-02T15:01:32.297Z
+firstPublishedAt: 2021-09-15T15:30:26.487Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart
+locale: en
+kiStatus: No Fix
+internalReference: 412041
+---
+
+## Summary
+
+
+During the purchase process, if the customer adds an item that has already been included in the cart previously and the new inclusion has assembly options, the second item is not added to the cart.
+
+For example, if during the purchase process, the customer adds an SKU to the cart and then another unit of the same SKU but with an extended warranty (via assemblyOptions), the last item added (the item with an extended warranty) will not be available in the cart.
+
+
+##
+
+## Simulation
+
+
+To run the simulation, please make sure there are items with assembly options in your store.
+
+
+1. Access the store;
+2. Add a product to the cart;
+3. Add the product once again and include an assembly option to the item (a customization or an extended warranty, for example);
+4. Check the cart and verify that the item with the assembly option has not been added.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md b/docs/known-issues/en/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
new file mode 100644
index 000000000..c1d625e93
--- /dev/null
+++ b/docs/known-issues/en/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
@@ -0,0 +1,47 @@
+---
+title: 'It is not possible to create a path using content type via UI'
+id: 3jVjkZYCATrnDNhR0IKSEA
+status: PUBLISHED
+createdAt: 2023-10-23T13:19:09.970Z
+updatedAt: 2024-07-01T18:49:16.580Z
+publishedAt: 2024-07-01T18:49:16.580Z
+firstPublishedAt: 2023-10-23T13:19:10.738Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: it-is-not-possible-to-create-a-path-using-content-type-via-ui
+locale: en
+kiStatus: No Fix
+internalReference: 923619
+---
+
+## Summary
+
+
+If we try to create a path using content types through the UI the page will not work. It only works if we create it through the theme.
+
+
+##
+
+## Simulation
+
+
+
+- Create a path using a content type on the Pages module, for example, `storeTest/:test_id`
+- Save it
+- Try to access it on the front
+- It will not work
+
+
+##
+
+## Workaround
+
+
+If we add the path using the content type through the theme, the page will appear on the UI and it will work
+
+
+
+
+
diff --git a/docs/known-issues/en/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md b/docs/known-issues/en/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
new file mode 100644
index 000000000..ce76def0c
--- /dev/null
+++ b/docs/known-issues/en/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
@@ -0,0 +1,46 @@
+---
+title: 'Item auto-complete not shown in seller whitelabel (change order)'
+id: 1jvkXj20gVHNtpp3KNL5GW
+status: PUBLISHED
+createdAt: 2024-03-05T21:55:53.411Z
+updatedAt: 2024-03-11T20:00:01.928Z
+publishedAt: 2024-03-11T20:00:01.928Z
+firstPublishedAt: 2024-03-05T21:55:54.222Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: item-autocomplete-not-shown-in-seller-whitelabel-change-order
+locale: en
+kiStatus: Backlog
+internalReference: 348841
+---
+
+## Summary
+
+
+When changing an item (change order) from a WhiteLabel seller account, the auto-complete does not show the item as expected.
+
+
+
+##
+
+## Simulation
+
+
+- Access an order from a whitelabel seller account, and request the item change option:
+- When filling in the SKU name in the search, it is not shown by auto-complete:
+- The same applies to whitelabel seller with the new admin-orders version:
+
+
+##
+
+## Workaround
+
+
+You can make the item change through the Register Change on Order API.
+
+
+
+
+
diff --git a/docs/known-issues/en/item-available-when-customer-location-is-not-defined-with-no-stock.md b/docs/known-issues/en/item-available-when-customer-location-is-not-defined-with-no-stock.md
new file mode 100644
index 000000000..57ed121cc
--- /dev/null
+++ b/docs/known-issues/en/item-available-when-customer-location-is-not-defined-with-no-stock.md
@@ -0,0 +1,47 @@
+---
+title: 'Item available when customer location is not defined with no stock'
+id: 7vDywP0WtfpJ4bCiNkXNfw
+status: PUBLISHED
+createdAt: 2024-07-30T22:51:30.425Z
+updatedAt: 2024-07-30T22:54:29.056Z
+publishedAt: 2024-07-30T22:54:29.056Z
+firstPublishedAt: 2024-07-30T22:51:31.764Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: item-available-when-customer-location-is-not-defined-with-no-stock
+locale: en
+kiStatus: Backlog
+internalReference: 1073363
+---
+
+## Summary
+
+
+When customer location is not defined, items appear available even when no stock is available and no seller white label is comprehensive. This happens only if the SKU has stock in the white label seller in a warehouse associated with a different sales channel than the one registered in the seller's fulfillment endpoint.
+
+
+##
+
+## Simulation
+
+
+
+- No stock for seller 1;
+- No comprehensive seller configured;
+- Stock in a white label seller in a different sales channel than fulfillment endpoint, for example:
+Fulfillment endpoint with sc=1;
+Stock in the seller for sc=2.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md b/docs/known-issues/en/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
new file mode 100644
index 000000000..e2063fed6
--- /dev/null
+++ b/docs/known-issues/en/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
@@ -0,0 +1,46 @@
+---
+title: 'item_name of purchase event is different from item_name of add to cart event in Google Analytics'
+id: 3FV2cJIV7uOIoH0lpl0iMP
+status: PUBLISHED
+createdAt: 2023-08-10T12:59:26.495Z
+updatedAt: 2023-08-10T12:59:27.432Z
+publishedAt: 2023-08-10T12:59:27.432Z
+firstPublishedAt: 2023-08-10T12:59:27.432Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics
+locale: en
+kiStatus: Backlog
+internalReference: 878629
+---
+
+## Summary
+
+
+When the SKU has the same name as the product the item_name from the purchase ever is different from the item_name of the add-to-cart event.
+
+
+##
+
+## Simulation
+
+
+
+- Add a product to the cart which its name is similar to its SKU name. For example, "Socks" is the product name and the SKU name is "Socks - G"
+- Look for its item_name on the add-to-cart event
+- Finish the purchase and look for the item_name on the purchase event
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/items-in-benefits-not-generated-in-promotions-with-collections-associated.md b/docs/known-issues/en/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
new file mode 100644
index 000000000..8cf232548
--- /dev/null
+++ b/docs/known-issues/en/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
@@ -0,0 +1,52 @@
+---
+title: 'Items in benefits not generated in promotions with collections associated'
+id: 9HrnxMcq7VWFQOPhg9ywd
+status: PUBLISHED
+createdAt: 2024-02-21T15:09:01.111Z
+updatedAt: 2024-02-21T15:09:01.913Z
+publishedAt: 2024-02-21T15:09:01.913Z
+firstPublishedAt: 2024-02-21T15:09:01.913Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: items-in-benefits-not-generated-in-promotions-with-collections-associated
+locale: en
+kiStatus: Backlog
+internalReference: 985850
+---
+
+## Summary
+
+
+
+When having a promotion with products/skus associated through a collection, the productContext isn't prepared to create the items array inside benefits associated with the products of the collection
+
+
+##
+
+## Simulation
+
+
+
+
+- Create a promotion
+- Associate the products for this promotion through a collection
+- Open one of the products that should have a promotion
+- Open your browser's console
+- Check on your React Dev Tools extension for productContextProvider
+- Open benefits.items, it will be empty or with the sku with the same id of the collection
+
+
+##
+
+## Workaround
+
+
+
+The only possible way to have benefits.items filled is filling all skus associated with the promotion instead of a cluster/collection
+
+
+
+
+
diff --git a/docs/known-issues/en/kit-creation-api-is-not-calculating-component-prices.md b/docs/known-issues/en/kit-creation-api-is-not-calculating-component-prices.md
index 536978155..5c6c4ee4c 100644
--- a/docs/known-issues/en/kit-creation-api-is-not-calculating-component-prices.md
+++ b/docs/known-issues/en/kit-creation-api-is-not-calculating-component-prices.md
@@ -3,8 +3,8 @@ title: 'Kit Creation API is not Calculating Component Prices'
 id: 3yyIEv6o3CjIbUg4KoLOWT
 status: PUBLISHED
 createdAt: 2023-03-28T16:34:55.491Z
-updatedAt: 2023-03-28T16:34:55.990Z
-publishedAt: 2023-03-28T16:34:55.990Z
+updatedAt: 2024-04-02T18:36:44.624Z
+publishedAt: 2024-04-02T18:36:44.624Z
 firstPublishedAt: 2023-03-28T16:34:55.990Z
 contentType: knownIssue
 productTeam: Catalog
@@ -32,9 +32,7 @@ The kit Price should be: 10*2 + 25 === 45.
 
 This is what happens on the KIT UI SkuKit.aspx.
 
-However, the API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit is not accounting for multiple components on the sum, so the price only considers each component once when calculation (then, our example above would, incorrectly, be 10 + 25 = 35).
-
-
+However, the API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit is not making such price updates for components other than the 1st one added.
 
 
 
@@ -54,5 +52,5 @@ Create a kit using the following API with a component with a quantity of 2 or mo
 ## Workaround
 
 
-Upon creating a kit, go to the UI and save the components once again to run the logic of calculating the mentioned ponderated sum.
+Insert the final price of the kit directly via pricing API.
 
diff --git a/docs/known-issues/en/kit-weight-can-be-overritten-by-apiwebservice.md b/docs/known-issues/en/kit-weight-can-be-overritten-by-apiwebservice.md
index fe1676a34..eb324fea9 100644
--- a/docs/known-issues/en/kit-weight-can-be-overritten-by-apiwebservice.md
+++ b/docs/known-issues/en/kit-weight-can-be-overritten-by-apiwebservice.md
@@ -3,8 +3,8 @@ title: 'Kit Weight can be Overritten by API/Webservice'
 id: Dlrs4qgHsnwIHxqqV0Rmg
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:40.711Z
-updatedAt: 2022-11-25T21:43:12.999Z
-publishedAt: 2022-11-25T21:43:12.999Z
+updatedAt: 2024-02-16T20:29:08.522Z
+publishedAt: 2024-02-16T20:29:08.522Z
 firstPublishedAt: 2022-06-28T16:55:40.971Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: kit-weight-can-be-overritten-by-apiwebservice
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429993
 ---
 
diff --git a/docs/known-issues/en/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md b/docs/known-issues/en/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
index c9e6f0015..9c287cb7c 100644
--- a/docs/known-issues/en/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
+++ b/docs/known-issues/en/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
@@ -3,8 +3,8 @@ title: 'Konduto AF cannot complete a request when the accountId is missing.'
 id: CGHZoCfr01ATsbtiLU9ym
 status: PUBLISHED
 createdAt: 2022-03-03T22:09:57.638Z
-updatedAt: 2022-11-25T22:05:52.845Z
-publishedAt: 2022-11-25T22:05:52.845Z
+updatedAt: 2023-06-20T17:54:26.840Z
+publishedAt: 2023-06-20T17:54:26.840Z
 firstPublishedAt: 2022-03-03T22:09:58.094Z
 contentType: knownIssue
 productTeam: Payments
@@ -19,22 +19,29 @@ internalReference: 496298
 ## Summary
 
 
-
-Some transactions cannot be finished because Konduto anti-fraud doesn't make the proper request because the accountId used to get payment information from the account database table is missing. This can be validated by looking at the /payment route where the node "usedAccountId" is false in this case.
+There's an issue to approve some transactions that is related to the Konduto anti-fraud system. This issue arises when the system fails to make the necessary request due to the absence of the accountId, which is required to retrieve payment information from the account database. You can verify this by examining the "/payment" route, where you will find the node "usedAccountId" with a value of "False" in such cases.
 
 **{**"name": "usedAccountId","value": "False"**}**
 
+Furthermore, this problem is commonly observed when a user removes their own card from the MyAccount page immediately after placing an order.
+
 
+##
 
 ## Simulation
 
 
-This error cannot be reproduced at this time, it occurs intermittently.
+Follow the aforementioned step, which involves deleting a card immediately after placing an order utilizing Konduto Antifraud.
 
 
+##
 
 ## Workaround
 
 
-No workaround is available.
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/en/large-importexport-spreadsheet-error-on-new-collections-admin.md b/docs/known-issues/en/large-importexport-spreadsheet-error-on-new-collections-admin.md
index 351a6e44d..a34e48ae4 100644
--- a/docs/known-issues/en/large-importexport-spreadsheet-error-on-new-collections-admin.md
+++ b/docs/known-issues/en/large-importexport-spreadsheet-error-on-new-collections-admin.md
@@ -3,8 +3,8 @@ title: 'Large Import/Export Spreadsheet Error on New Collections Admin'
 id: 6xbBVR2Z7CCpIC0iCAKHgN
 status: PUBLISHED
 createdAt: 2023-02-16T19:04:08.298Z
-updatedAt: 2023-02-16T19:04:08.784Z
-publishedAt: 2023-02-16T19:04:08.784Z
+updatedAt: 2023-12-12T21:08:23.871Z
+publishedAt: 2023-12-12T21:08:23.871Z
 firstPublishedAt: 2023-02-16T19:04:08.784Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,15 +12,14 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: large-importexport-spreadsheet-error-on-new-collections-admin
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 362017
 ---
 
 ## Summary
 
 
-Currently, the new collection's admin, in the import feature for an SKU inclusion, using the SKU row, often returns an unspecific error response when attempting to import a file with too many registries.
-
+Currently, uploading items to the new collections module with a list with over 1000 SKUs is impossible, since the process will timeout. It returns an unspecific error response:
 "`Your file was not imported. Please try importing this file again.`"
 
 
@@ -29,9 +28,11 @@ Currently, the new collection's admin, in the import feature for an SKU inclusio
 ## Simulation
 
 
-1) In a store in which the catalog is very large, 50K+ products access the new collections admin /admin/collections
 
-2) In a collection, try importing new registries with over 100 SKUs in a single import.
+1. Go to the new collections module
+2. Select the tab "Import"
+3. Use a sheet that has over 1000 SKUs (i.e. 300 products with 50 SKUs, each)
+4. The import will generate a timeout.
 
 
 ##
@@ -39,11 +40,7 @@ Currently, the new collection's admin, in the import feature for an SKU inclusio
 ## Workaround
 
 
-1) Use the legacy collections for massively importing SKUs.
-
-2) Split the imports into smaller sheets and do the process gradually.
-
-3) Use the UI's massive actions to reach the desired effect.
+Upload gradually using smaller sheets, the legacy CMS collections and/or the insert SKU to subcollection API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/subcollection/-subCollectionId-/stockkeepingunit
 
 
 
diff --git a/docs/known-issues/en/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md b/docs/known-issues/en/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
index dfe022e51..dbee6f200 100644
--- a/docs/known-issues/en/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
+++ b/docs/known-issues/en/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
@@ -3,8 +3,8 @@ title: 'Lean Shipping being forced even when the items have the same SLAs, but i
 id: 2YTqsVWPm73msQZVQX9x80
 status: PUBLISHED
 createdAt: 2022-05-13T17:26:15.513Z
-updatedAt: 2022-11-25T21:52:30.793Z
-publishedAt: 2022-11-25T21:52:30.793Z
+updatedAt: 2023-09-11T21:38:39.068Z
+publishedAt: 2023-09-11T21:38:39.068Z
 firstPublishedAt: 2022-05-13T17:26:16.378Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,19 +12,32 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 455218
 ---
 
 ## Summary
 
 
+In some scenarios it is possible that even if the LeanShipping feature is turned off in the settings, the system may still consider it necessary to group the shipping options, and with that it will not disable leanShipping, this is because the rule used by the system to define the use or no leanshipping other than the setting is on or off and there is the same or different SLAs available for cart items;
+However, there are scenarios where just the order of how the SLAs are delivered makes the system understand that they are a different SLA's and activate leanShipping at checkout and start displaying the fastest and cheapest labels for the shipping method.
+
+
+##
 
 ## Simulation
 
 
+There is no linear way to replicate the scenario, however it can occur whenever we have a cart with two or more items whose slas are similar between the items, and are being presented in different orders within the object sla of each item;
+
+
+##
 
 ## Workaround
 
 
+N/A
+
+
+
 
diff --git a/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
new file mode 100644
index 000000000..e530908aa
--- /dev/null
+++ b/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -0,0 +1,49 @@
+---
+title: 'Lean shipping causes "Something went wrong" after changing pick-up points'
+id: 45jQODtjZ4vLXniNJIlQZc
+status: PUBLISHED
+createdAt: 2024-06-20T21:11:53.067Z
+updatedAt: 2024-06-20T21:15:28.608Z
+publishedAt: 2024-06-20T21:15:28.608Z
+firstPublishedAt: 2024-06-20T21:11:53.899Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: lean-shipping-causes-something-went-wrong-after-changing-pickup-points
+locale: en
+kiStatus: Backlog
+internalReference: 1053609
+---
+
+## Summary
+
+
+A shopper can search for different pick-up points in different postal codes. When using lean shipping, after adding a postal code with pick-up points available and changing to a postal code without pick-up points, the shipping step is blocked with the message "Something went wrong".
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/i0jCDFlz5EGPnKyk5Nfw0Etl0/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+
+- Assemble a cart and select pick up in point in the cart;
+- Add a postal code with pick-up;
+- Select one of the pickups
+- Change to a postal code without pick-up points;
+- Go to checkout and the message "Something went wrong" is shown in the shipping step.
+
+
+##
+
+## Workaround
+
+
+Refresh the page or deactivate the lean shipping.
+
+
+
+
diff --git a/docs/known-issues/en/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md b/docs/known-issues/en/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
new file mode 100644
index 000000000..7089b60ee
--- /dev/null
+++ b/docs/known-issues/en/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
@@ -0,0 +1,46 @@
+---
+title: "Lean Shipping doesn't deactivate after removing items from cart"
+id: 4dZZz28csz9BLhJNvQGHQV
+status: PUBLISHED
+createdAt: 2023-10-09T14:20:03.767Z
+updatedAt: 2023-10-09T14:20:04.692Z
+publishedAt: 2023-10-09T14:20:04.692Z
+firstPublishedAt: 2023-10-09T14:20:04.692Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: lean-shipping-doesnt-deactivate-after-removing-items-from-cart
+locale: en
+kiStatus: Backlog
+internalReference: 916461
+---
+
+## Summary
+
+
+Lean Shipping doesn't deactivate automatically after removing items from the cart, keeping only one where it should show all options.
+
+
+##
+
+## Simulation
+
+
+
+- Add 2 or more items from different sellers that have different SLAs;
+- Lean shipping will be active;
+- Remove all items, keeping only 1;
+- Lean shipping will be still active.
+
+
+##
+
+## Workaround
+
+
+Refresh the page
+
+
+
+
diff --git a/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md
new file mode 100644
index 000000000..38a01ccb8
--- /dev/null
+++ b/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md
@@ -0,0 +1,49 @@
+---
+title: 'Legacy Catalog UI "delete" button not functional'
+id: 2soNSJfiQMZcxlpW6jT2FR
+status: PUBLISHED
+createdAt: 2022-01-23T02:51:17.884Z
+updatedAt: 2024-05-21T16:03:51.417Z
+publishedAt: 2024-05-21T16:03:51.417Z
+firstPublishedAt: 2024-05-21T16:03:51.417Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: legacy-catalog-ui-delete-button-not-functional
+locale: en
+kiStatus: Backlog
+internalReference: 326408
+---
+
+## Summary
+
+
+The button to delete products on the catalog is not working, it simply doesn't recognize any user clicks
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ZR7ogOzhfLN3yC61V9RzTMRlZ/?name=inline-652081372.png)
+
+This action might work if the product was just created and no skus, images or any other kind of data is associated with it.
+
+
+##
+
+## Simulation
+
+
+- Go to the catalog main page;
+- Try to delete a product: no action will be triggered
+
+
+
+
+##
+
+## Workaround
+
+
+There is no way to delete only a single product, only the entire base. To achieve the same result as a deletion, try replacing this product with data you'd already use for a new product anyway.
+
+
+
+
diff --git a/docs/known-issues/en/legacy-cmss-banner-custom-element-not-working.md b/docs/known-issues/en/legacy-cmss-banner-custom-element-not-working.md
new file mode 100644
index 000000000..6772d3a34
--- /dev/null
+++ b/docs/known-issues/en/legacy-cmss-banner-custom-element-not-working.md
@@ -0,0 +1,54 @@
+---
+title: "Legacy CMS's banner custom element not working"
+id: 3ezW1BTc2nSvHpp0mAYhwh
+status: PUBLISHED
+createdAt: 2024-02-07T13:44:20.722Z
+updatedAt: 2024-02-07T13:44:21.554Z
+publishedAt: 2024-02-07T13:44:21.554Z
+firstPublishedAt: 2024-02-07T13:44:21.554Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: legacy-cmss-banner-custom-element-not-working
+locale: en
+kiStatus: Backlog
+internalReference: 978466
+---
+
+## Summary
+
+
+Currently, the "custom elements" tab of the legacy CMS configurations is not working properly.
+
+Setting up a custom element of this type will not yield effects in most cases and directly setting it up in the layout's HTML is recommended.
+
+This only happens for legacy template stores.
+
+
+##
+
+## Simulation
+
+
+1 - go to the legacy CMS and select the custom elements tab
+2 - upload a custom element of the "banner" type
+3 - reference this banner in your html
+4 - the configured banner will not render properly
+
+
+##
+
+## Workaround
+
+
+set up the banners by using the type HTML layout and/or subtemplates associated to it.
+
+OR
+
+migrate to the VTEX store framework
+
+
+
+
+
diff --git a/docs/known-issues/en/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md b/docs/known-issues/en/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
index dcf795e68..a142150d6 100644
--- a/docs/known-issues/en/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
+++ b/docs/known-issues/en/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
@@ -3,8 +3,8 @@ title: 'Legacy collection UI category filter selecting products wrongly to the c
 id: 1IlioZpOSQf5t4TWqZreiS
 status: PUBLISHED
 createdAt: 2022-10-31T20:42:26.100Z
-updatedAt: 2022-12-20T16:37:12.340Z
-publishedAt: 2022-12-20T16:37:12.340Z
+updatedAt: 2024-02-16T20:28:22.357Z
+publishedAt: 2024-02-16T20:28:22.357Z
 firstPublishedAt: 2022-10-31T20:42:26.591Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 590934
 ---
 
diff --git a/docs/known-issues/en/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md b/docs/known-issues/en/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
new file mode 100644
index 000000000..c9cdbd81c
--- /dev/null
+++ b/docs/known-issues/en/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
@@ -0,0 +1,48 @@
+---
+title: 'Legacy installment template and shelf controls do not consider unit multipliers'
+id: 1E0Co7ssCUAKAgxCzlJoVn
+status: PUBLISHED
+createdAt: 2024-02-08T13:39:40.663Z
+updatedAt: 2024-02-08T13:48:30.740Z
+publishedAt: 2024-02-08T13:48:30.740Z
+firstPublishedAt: 2024-02-08T13:39:41.744Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers
+locale: en
+kiStatus: Backlog
+internalReference: 979205
+---
+
+## Summary
+
+
+Currently, for store using the legacy CMS, legacy template and shelf controls are not adjusted if the SKU has a unit multiplier.
+
+For instance, if you have an item with an unit multiplier of 2 and a installment controller, the data displayed on shelves will only show the installment options of a single unit, instead of adjusting for this configuration.
+
+
+##
+
+## Simulation
+
+
+1 - create a sku with an unit multiplier
+2 - set up installment options for it
+3 - set up a installment related controller, such as $product.InstallmentValue
+4 - the displayed data will be relative to a single unit, only.
+
+
+##
+
+## Workaround
+
+
+implement a front-end customization to overwrite the original data being shown.
+
+
+
+
+
diff --git a/docs/known-issues/en/let-me-know-controller-texts-are-not-being-translated.md b/docs/known-issues/en/let-me-know-controller-texts-are-not-being-translated.md
index a32f768e4..68b10735f 100644
--- a/docs/known-issues/en/let-me-know-controller-texts-are-not-being-translated.md
+++ b/docs/known-issues/en/let-me-know-controller-texts-are-not-being-translated.md
@@ -3,8 +3,8 @@ title: 'Let Me Know controller texts are not being translated'
 id: 4UXWf34IXNVAEKgH4hQLTx
 status: PUBLISHED
 createdAt: 2022-02-03T17:18:23.078Z
-updatedAt: 2022-12-02T18:35:11.786Z
-publishedAt: 2022-12-02T18:35:11.786Z
+updatedAt: 2024-02-16T20:26:19.991Z
+publishedAt: 2024-02-16T20:26:19.991Z
 firstPublishedAt: 2022-02-03T17:18:23.416Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: let-me-know-controller-texts-are-not-being-translated
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 517165
 ---
 
diff --git a/docs/known-issues/en/link-service-values-to-skus-spreadsheet-only-returning-active-services.md b/docs/known-issues/en/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
new file mode 100644
index 000000000..baf40a0b3
--- /dev/null
+++ b/docs/known-issues/en/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
@@ -0,0 +1,48 @@
+---
+title: 'LINK SERVICE VALUES TO SKUS spreadsheet only returning active services'
+id: 1FqAokiJLWwWnsPodyTMKY
+status: PUBLISHED
+createdAt: 2023-08-23T17:51:58.839Z
+updatedAt: 2023-08-23T17:51:59.677Z
+publishedAt: 2023-08-23T17:51:59.677Z
+firstPublishedAt: 2023-08-23T17:51:59.677Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: link-service-values-to-skus-spreadsheet-only-returning-active-services
+locale: en
+kiStatus: Backlog
+internalReference: 886486
+---
+
+## Summary
+
+
+When exporting service values from a specific category on the admin the result is only bringing the active services. Not enabling the merchant to activate previously inactive services by spreadsheet.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a service and associate to an sku;
+2. Inactivate the service on the sku;
+3. Export the LINK SERVICE VALUES TO SKUS spreadsheet;
+4. Check that the previously service is not returned.
+
+
+##
+
+## Workaround
+
+
+Use API or go directly on the sku - services admin in order to update the service:
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/skuservice/-skuServiceId-
+
+
+
+
+
diff --git a/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index 8d38a16a2..f202bba67 100644
--- a/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -3,8 +3,8 @@ title: 'Link "Why fill VTEX Global Category?" on category setup only works openi
 id: 3u7aq2otUovQbO98lzjbus
 status: PUBLISHED
 createdAt: 2022-03-16T17:59:14.355Z
-updatedAt: 2022-12-20T16:36:51.563Z
-publishedAt: 2022-12-20T16:36:51.563Z
+updatedAt: 2024-02-16T20:23:34.672Z
+publishedAt: 2024-02-16T20:23:34.672Z
 firstPublishedAt: 2022-03-16T17:59:14.784Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 544034
 ---
 
diff --git a/docs/known-issues/en/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/en/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
new file mode 100644
index 000000000..a7524381c
--- /dev/null
+++ b/docs/known-issues/en/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -0,0 +1,89 @@
+---
+title: 'linkId is not being registered on rewriter when translating with catalog graphql'
+id: 7b7KOHlxyIO4zKy2xrMuSD
+status: PUBLISHED
+createdAt: 2022-09-08T21:27:03.855Z
+updatedAt: 2024-07-10T12:47:32.306Z
+publishedAt: 2024-07-10T12:47:32.306Z
+firstPublishedAt: 2022-09-08T21:27:04.567Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql
+locale: en
+kiStatus: Backlog
+internalReference: 654951
+---
+
+## Summary
+
+
+When using the catalog graphQL and translating the URL using the linkId the rewriter should store the linkId, but it's not happening: https://developers.vtex.com/docs/guides/catalog-internationalization
+
+
+##
+
+## Simulation
+
+
+
+- Follow the documentation guide for translating the catalog content: https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization#mutation
+- **For Category links:**
+  - Check the linkId that you created at admin/graphql-ide and choose the rewriter app:
+
+    { internal{ get(path: "yourLinkdIdHere"){ id } }}
+
+
+
+- This will return null;
+- Check again with the name of your translated category but, slugified:
+
+    { internal{ get(path: "yourTranslatedCategoryNameSlugified"){ id } }}
+
+
+
+- This will return results.
+
+
+
+- **For product links:**
+  - Access the product page using the translated link created using the catalog graphQL;
+  - It will show a 404 Not Found.
+
+
+##
+
+## Workaround
+
+
+
+- **For Category links:**
+  - Run the following query on rewriter:
+
+    { internal{ get(path: "yourTranslatedLinkdId"){ id from declarer type query binding  origin resolveAs } }}
+
+
+
+- Save the returned values, you will need to use them in the next step;
+- Run the following mutation just changing the from parameter, the others must be the same as above:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "yourLinkId", "declarer": "yourSavedDeclarer", "type": "yourSavedType", "binding": "yourSavedBinding", "id": "yourSavedId", "origin": "yourSavedOrigin", "resolveAs": "yourSavedResolveAs" }}
+
+> For more information regarding those params, you can consult: https://developers.vtex.com/vtex-developer-docs/docs/rewriter
+
+
+
+- Now, we are going to delete the old route (the one saved with the name)
+
+    mutation saveInternal($route: InternalInput!) { internal { delete(path: "yourTranslatedLinkdId") { id } }}
+
+
+
+- **For product links:**
+  - Run the following mutation just changing the from parameter, the others must be the same as above:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "/yourTranslatedLinkdId/p", "declarer": "vtex.store@2.x", "type": "product", "id": "productId", "resolveAs": "/yourOrinalLinkdId/p", "binding": "bindingId" }}
+
+
+
diff --git a/docs/known-issues/en/locale-switcher-doesnt-work-in-myvtex-environment.md b/docs/known-issues/en/locale-switcher-doesnt-work-in-myvtex-environment.md
index 37a65694c..2fed28468 100644
--- a/docs/known-issues/en/locale-switcher-doesnt-work-in-myvtex-environment.md
+++ b/docs/known-issues/en/locale-switcher-doesnt-work-in-myvtex-environment.md
@@ -3,8 +3,8 @@ title: "Locale Switcher doesn't work in myvtex environment"
 id: 1ZB56egPjPbTaUUnws5juK
 status: PUBLISHED
 createdAt: 2023-03-27T12:26:31.974Z
-updatedAt: 2023-03-27T14:55:12.486Z
-publishedAt: 2023-03-27T14:55:12.486Z
+updatedAt: 2024-02-02T21:03:39.535Z
+publishedAt: 2024-02-02T21:03:39.535Z
 firstPublishedAt: 2023-03-27T12:26:32.649Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/en/login-preference-with-password-cannot-be-undone-in-admin.md b/docs/known-issues/en/login-preference-with-password-cannot-be-undone-in-admin.md
new file mode 100644
index 000000000..6202b56c5
--- /dev/null
+++ b/docs/known-issues/en/login-preference-with-password-cannot-be-undone-in-admin.md
@@ -0,0 +1,54 @@
+---
+title: 'Login preference with password cannot be undone in Admin'
+id: 5OPVJusw14TQzKdAVS71wx
+status: PUBLISHED
+createdAt: 2024-04-22T13:30:15.401Z
+updatedAt: 2024-05-06T20:40:26.631Z
+publishedAt: 2024-05-06T20:40:26.631Z
+firstPublishedAt: 2024-04-22T13:30:16.436Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: login-preference-with-password-cannot-be-undone-in-admin
+locale: en
+kiStatus: Backlog
+internalReference: 1020548
+---
+
+## Summary
+
+
+When a user logs on to the VTEX platform for the first time (Admin), they are asked to choose their login preference for the next time they log on. They can then choose between entering their e-mail address and password, or entering a code that will be sent to their e-mail address;
+
+However, when the user chooses to enter their e-mail address and password, they are unable to undo this choice, as it is an irrevocable choice at UI level, and a systemic action is required to undo this choice.
+
+
+##
+
+## Simulation
+
+
+**NOTE**: To simulate this scenario, you must be logging in for the first time;
+
+Log in to admin
+
+Enter your e-mail address and create a password;
+
+At this point you will be asked if you want to continue receiving the access code or if you want the system to always ask for your e-mail address and password.
+
+Request that you always log in using your e-mail address and password.
+
+The next time you log in, you won't be able to undo your login choice and you will always be asked for your e-mail address and password.
+
+
+##
+
+## Workaround
+
+
+In order for the user to be able to make a new choice, it is necessary to ask the engineering team to revoke the preference saved in the user's profile, so that on their next login they will be asked again about their login preference and can make a new choice
+
+
+
+
diff --git a/docs/known-issues/en/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md b/docs/known-issues/en/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
index 79e6cba88..34a01b2ce 100644
--- a/docs/known-issues/en/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
+++ b/docs/known-issues/en/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
@@ -3,8 +3,8 @@ title: 'Logistics Simulation with Minimum and Maximum price in Shipping Policy d
 id: 5gsBLbPMIZjZvkl5QHudVY
 status: PUBLISHED
 createdAt: 2022-03-30T20:10:30.205Z
-updatedAt: 2022-11-25T21:59:57.297Z
-publishedAt: 2022-11-25T21:59:57.297Z
+updatedAt: 2024-02-16T20:26:15.370Z
+publishedAt: 2024-02-16T20:26:15.370Z
 firstPublishedAt: 2022-05-17T14:23:38.006Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 553080
 ---
 
diff --git a/docs/known-issues/en/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md b/docs/known-issues/en/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
index 46e011279..8bf76a922 100644
--- a/docs/known-issues/en/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
+++ b/docs/known-issues/en/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
@@ -3,8 +3,8 @@ title: 'Loop in the authentication pop-up when the first payment condition requi
 id: 7fU6wnrTjS0aJqRmertSFg
 status: PUBLISHED
 createdAt: 2023-06-14T17:54:36.973Z
-updatedAt: 2023-06-14T17:55:47.281Z
-publishedAt: 2023-06-14T17:55:47.281Z
+updatedAt: 2023-12-21T15:50:16.992Z
+publishedAt: 2023-12-21T15:50:16.992Z
 firstPublishedAt: 2023-06-14T17:54:37.537Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/en/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md b/docs/known-issues/en/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
index 54e8bfebc..3f70bc3cf 100644
--- a/docs/known-issues/en/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
+++ b/docs/known-issues/en/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
@@ -3,8 +3,8 @@ title: '[Magalu] Sku being integrated with specifications from another marketpla
 id: 4AYsfMTB2HVmp2PnOG2plY
 status: PUBLISHED
 createdAt: 2022-10-31T19:29:16.911Z
-updatedAt: 2022-12-02T18:30:12.315Z
-publishedAt: 2022-12-02T18:30:12.315Z
+updatedAt: 2024-03-19T20:33:58.929Z
+publishedAt: 2024-03-19T20:33:58.929Z
 firstPublishedAt: 2022-10-31T19:29:18.080Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: magalu-sku-being-integrated-with-specifications-from-another-marketplace
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 689151
 ---
 
diff --git a/docs/known-issues/en/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md b/docs/known-issues/en/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
new file mode 100644
index 000000000..64f0a045a
--- /dev/null
+++ b/docs/known-issues/en/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
@@ -0,0 +1,47 @@
+---
+title: "[Magazine Luiza] Order canceled on marketplace didn't update status on VTEX"
+id: 4C1G20Iwj6x1mvqzsSDU0P
+status: PUBLISHED
+createdAt: 2023-07-20T15:33:25.631Z
+updatedAt: 2023-07-20T15:33:26.222Z
+publishedAt: 2023-07-20T15:33:26.222Z
+firstPublishedAt: 2023-07-20T15:33:26.222Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex
+locale: en
+kiStatus: Backlog
+internalReference: 865926
+---
+
+## Summary
+
+
+Order canceled on marketplace didn't update status on VTEX
+
+**Marketplace:** Magazine Luiza
+**Root Cause:** Order Integration
+**Type:** Status not updated on marketplace
+**Impact:** Few orders
+
+
+##
+
+## Simulation
+
+
+No errors were found in the logs, but the order In OMS/VTEX is `Invoiced `but in marktplace the order is as `canceled`
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/magazine-luiza-some-skus-do-not-update-price.md b/docs/known-issues/en/magazine-luiza-some-skus-do-not-update-price.md
new file mode 100644
index 000000000..bb351cfe1
--- /dev/null
+++ b/docs/known-issues/en/magazine-luiza-some-skus-do-not-update-price.md
@@ -0,0 +1,53 @@
+---
+title: '[Magazine Luiza] Some skus do not update price'
+id: NXb7Bb4BTJepPphcK9z0V
+status: PUBLISHED
+createdAt: 2023-08-17T14:14:36.434Z
+updatedAt: 2023-08-17T14:14:37.098Z
+publishedAt: 2023-08-17T14:14:37.098Z
+firstPublishedAt: 2023-08-17T14:14:37.098Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: magazine-luiza-some-skus-do-not-update-price
+locale: en
+kiStatus: Backlog
+internalReference: 882919
+---
+
+## Summary
+
+
+We need to understand why some skus don't update the price in the marketplace.
+Important: doesn't happen with all skus
+
+
+##
+
+## Simulation
+
+
+Flow: Price updated in the VTEX catalog
+
+broadcaster
+received notification for price change
+
+Integration
+received notification for price change
+
+marketplace
+Price has not been updated and no errors found in the log
+
+
+##
+
+## Workaround
+
+
+Reindex sku in VTEX catalog
+
+
+
+
+
diff --git a/docs/known-issues/en/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md b/docs/known-issues/en/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
new file mode 100644
index 000000000..fc703c6c7
--- /dev/null
+++ b/docs/known-issues/en/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
@@ -0,0 +1,50 @@
+---
+title: "[Magazine Luiza] [tracking] Erro: Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"
+id: 7ublDwKHM4JJxsCtcbLqq8
+status: PUBLISHED
+createdAt: 2023-07-06T14:06:45.020Z
+updatedAt: 2023-07-06T14:06:45.783Z
+publishedAt: 2023-07-06T14:06:45.783Z
+firstPublishedAt: 2023-07-06T14:06:45.783Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje
+locale: en
+kiStatus: Backlog
+internalReference: 856984
+---
+
+## Summary
+
+
+In the tracking step some orders are returning the following error `"Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"`
+
+**Marketplace:** Magazine Luiza
+**Status:** tracking
+**Impact:** Some Orders
+
+
+##
+
+## Simulation
+
+
+1. Integrations
+2. Bridge
+3. Tracking
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/mlpzu59MIDWuvUP6n8zJc8GI6/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+Usually manually reprocessing the request from the bridge fixes the error.
+
+
+
+
diff --git a/docs/known-issues/en/mandatory-service-working-as-optional.md b/docs/known-issues/en/mandatory-service-working-as-optional.md
new file mode 100644
index 000000000..f192cc028
--- /dev/null
+++ b/docs/known-issues/en/mandatory-service-working-as-optional.md
@@ -0,0 +1,46 @@
+---
+title: 'Mandatory Service working as optional'
+id: 6bcdioCSYL7ZGoOy0nEtJC
+status: PUBLISHED
+createdAt: 2023-08-01T15:15:29.008Z
+updatedAt: 2023-08-01T15:15:30.099Z
+publishedAt: 2023-08-01T15:15:30.099Z
+firstPublishedAt: 2023-08-01T15:15:30.099Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: mandatory-service-working-as-optional
+locale: en
+kiStatus: Backlog
+internalReference: 872411
+---
+
+## Summary
+
+
+When creating a service the merchant can choose if is going to be a mandatory field at the checkout or not.
+However, currently this functionality is not working as expected. Even when the mandatory field is flagged as true, the product can be purchased without adding it on the checkout.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a service as mandatory;
+2. Associate to an sku;
+3. Check that at the checkout the service can be added or removed without problems.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md b/docs/known-issues/en/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
new file mode 100644
index 000000000..f292047c3
--- /dev/null
+++ b/docs/known-issues/en/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
@@ -0,0 +1,45 @@
+---
+title: 'marketingData is not saved in orders when using multiple coupons feature and utms'
+id: OUMc8x9sEcdp8ZbLIka4b
+status: PUBLISHED
+createdAt: 2023-11-22T21:53:36.924Z
+updatedAt: 2024-04-09T13:33:02.091Z
+publishedAt: 2024-04-09T13:33:02.091Z
+firstPublishedAt: 2023-11-22T21:53:37.493Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms
+locale: en
+kiStatus: Fixed
+internalReference: 936458
+---
+
+## Summary
+
+
+When using the multiple coupons feature and there are coupons and utms, or 'marketingTags', in the 'orderForm', no 'marketingData' is saved into the order.
+
+
+##
+
+## Simulation
+
+
+
+- Have an account using multiple coupons feature;
+- Use a coupon and set any utm or 'marketingTags', both must be in the orderForm;
+- Finish the purchase; there won't be any 'marketingData' in the order.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/marketingtags-with-null-value-when-campaign-audience-is-matched.md b/docs/known-issues/en/marketingtags-with-null-value-when-campaign-audience-is-matched.md
new file mode 100644
index 000000000..f0df2f9bd
--- /dev/null
+++ b/docs/known-issues/en/marketingtags-with-null-value-when-campaign-audience-is-matched.md
@@ -0,0 +1,45 @@
+---
+title: 'marketingTags with null value when campaign audience is matched'
+id: 17pTWB1gLNJgFy7KEZd8pk
+status: PUBLISHED
+createdAt: 2024-06-19T20:08:49.413Z
+updatedAt: 2024-06-19T20:08:50.452Z
+publishedAt: 2024-06-19T20:08:50.452Z
+firstPublishedAt: 2024-06-19T20:08:50.452Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketingtags-with-null-value-when-campaign-audience-is-matched
+locale: en
+kiStatus: Backlog
+internalReference: 1052895
+---
+
+## Summary
+
+
+When an account has a campaign audience and a logged-in user is matched, checkout uses the information registered in the session, which only has the campaign's id. In `marketingTags`, it should have the campaign's name, but it's `null` as there is no information available in the session.
+
+
+##
+
+## Simulation
+
+
+
+- Create a campaign audience;
+- Log in with a user that the campaign is matched;
+- Check the field `marketingData.marketingTags` in the orderForm, it will have a null value and the campaign's name.
+ ![](https://vtexhelp.zendesk.com/attachments/token/1i6d9cIyg1Hx2fs9QsVZ6BFCY/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md b/docs/known-issues/en/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
new file mode 100644
index 000000000..5f7b6b7cd
--- /dev/null
+++ b/docs/known-issues/en/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
@@ -0,0 +1,49 @@
+---
+title: 'Marketplace and Fulfillment can expect different order values due to certain purchase conditions'
+id: 5LoC3DwesBWH5kr2b5u6WD
+status: PUBLISHED
+createdAt: 2024-05-13T20:04:19.094Z
+updatedAt: 2024-05-13T20:34:01.432Z
+publishedAt: 2024-05-13T20:34:01.432Z
+firstPublishedAt: 2024-05-13T20:04:20.144Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions
+locale: en
+kiStatus: Backlog
+internalReference: 1032473
+---
+
+## Summary
+
+
+Marketplace and Fulfillment layers may expect different values for the order, preventing purchase completion.
+In such cases, the Marketplace's `sellingPrice` for the item does not match its Fulfillment `price`.
+
+
+##
+
+## Simulation
+
+
+The issue is not necessarily restricted to this exact step-by-step, but is easiest to reproduce as follows:
+
+1. Set the Marketplace and seller's decimal places to zero.
+2. At the seller's account, set an item's price to 49950.00, and a Fulfillment promotion that applies a 15% discount to it.
+3. At a Marketplace, add 3 units of the seller's item to your cart.
+4. Try to complete the purchase. The error message "The requested order could not be created. Please try again." will be displayed.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md b/docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
new file mode 100644
index 000000000..63850d6d6
--- /dev/null
+++ b/docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
@@ -0,0 +1,45 @@
+---
+title: "Marketplace tax hub request doesn't consider manual price for discounts"
+id: 2pGgbPB7Qm4dXtQauohvx7
+status: PUBLISHED
+createdAt: 2023-11-08T17:59:41.102Z
+updatedAt: 2023-12-06T19:27:50.006Z
+publishedAt: 2023-12-06T19:27:50.006Z
+firstPublishedAt: 2023-11-08T17:59:41.695Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts
+locale: en
+kiStatus: Fixed
+internalReference: 932657
+---
+
+## Summary
+
+
+When the account has isMarketplaceResponsibleForTaxes configured, the tax hub request doesn't consider manual prices for item discounts.
+
+
+##
+
+## Simulation
+
+
+
+- Configure taxConfiguration.isMarketplaceResponsibleForTaxes in the orderForm configuration;
+- Set manual price for an item;
+- The tax hub request won't apply the difference as a discount.
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md b/docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
new file mode 100644
index 000000000..dd5ea4bc1
--- /dev/null
+++ b/docs/known-issues/en/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
@@ -0,0 +1,44 @@
+---
+title: "Marketplace tax hub request doesn't consider some discount types"
+id: 630nSPu8y5G6CSFtiH3MOL
+status: PUBLISHED
+createdAt: 2023-11-30T21:14:13.709Z
+updatedAt: 2023-12-06T19:27:05.930Z
+publishedAt: 2023-12-06T19:27:05.930Z
+firstPublishedAt: 2023-11-30T21:14:14.259Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketplace-tax-hub-request-doesnt-consider-some-discount-types
+locale: en
+kiStatus: Fixed
+internalReference: 945580
+---
+
+## Summary
+
+
+When the account has isMarketplaceResponsibleForTaxes configured, the tax hub request doesn't consider some discount types: Nominal, Percentage, and Maximum price per item. This impacts the tax calculation, and the final price is higher than expected.
+
+
+##
+
+## Simulation
+
+
+
+- Configure taxConfiguration.isMarketplaceResponsibleForTaxes in the orderForm configuration;
+- Configure one of the discount types Nominal, Percentage, or Maximum price per item from regular promotion;
+- The tax hub request won't apply the discount.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/mastercard-credit-card-transactions-are-being-processed-as-visa.md b/docs/known-issues/en/mastercard-credit-card-transactions-are-being-processed-as-visa.md
new file mode 100644
index 000000000..18ad5c60e
--- /dev/null
+++ b/docs/known-issues/en/mastercard-credit-card-transactions-are-being-processed-as-visa.md
@@ -0,0 +1,43 @@
+---
+title: 'Mastercard credit card transactions are being processed as Visa'
+id: 4B547KIrO7xBUWdCUhPkjs
+status: PUBLISHED
+createdAt: 2024-05-02T19:12:19.672Z
+updatedAt: 2024-05-02T19:12:20.545Z
+publishedAt: 2024-05-02T19:12:20.545Z
+firstPublishedAt: 2024-05-02T19:12:20.545Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: mastercard-credit-card-transactions-are-being-processed-as-visa
+locale: en
+kiStatus: Backlog
+internalReference: 1026263
+---
+
+## Summary
+
+
+Some transactions are being mistakenly registered under the Visa brand, when in fact the cards are Mastercard. This issue occurs specifically with new cards, although we can verify that the card's BIN correctly matches the validator regex for the correct brand.
+
+
+##
+
+## Simulation
+
+
+We were not able to replicate this issue.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/masterdata-export-download-link-unavailable.md b/docs/known-issues/en/masterdata-export-download-link-unavailable.md
index 83071529a..6c952de8c 100644
--- a/docs/known-issues/en/masterdata-export-download-link-unavailable.md
+++ b/docs/known-issues/en/masterdata-export-download-link-unavailable.md
@@ -3,8 +3,8 @@ title: 'Masterdata Export Download Link Unavailable'
 id: 2oi0ABhQQxfPsKETeNUyvE
 status: PUBLISHED
 createdAt: 2022-07-08T13:50:43.220Z
-updatedAt: 2023-01-19T14:19:49.870Z
-publishedAt: 2023-01-19T14:19:49.870Z
+updatedAt: 2023-07-28T17:14:13.207Z
+publishedAt: 2023-07-28T17:14:13.207Z
 firstPublishedAt: 2022-07-08T13:50:43.638Z
 contentType: knownIssue
 productTeam: Storage
@@ -40,5 +40,5 @@ Currently, for data entities with several fields, when there's an attempt to exp
 ## Workaround
 
 
-fetch data via API https://developers.vtex.com/docs/api-reference/masterdata-api#get-/api/dataentities/-acronym-/search and/or download data into several, smaller spreadsheets
+**Right-click on the Download link and copy the link, then paste the link in another tab and the download will start or** fetch data via API https://developers.vtex.com/docs/api-reference/masterdata-api#get-/api/dataentities/-acronym-/search and/or download data into several, smaller spreadsheets
 
diff --git a/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md
new file mode 100644
index 000000000..bea3c6bcf
--- /dev/null
+++ b/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -0,0 +1,52 @@
+---
+title: 'Match Multiple Received SKUs API returning "Invalid sellerId"'
+id: 60aL2Chds0Jo3m6XMkxmnG
+status: PUBLISHED
+createdAt: 2023-10-17T16:26:27.980Z
+updatedAt: 2023-10-17T16:26:40.592Z
+publishedAt: 2023-10-17T16:26:40.592Z
+firstPublishedAt: 2023-10-17T16:26:28.466Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: match-multiple-received-skus-api-returning-invalid-sellerid
+locale: en
+kiStatus: Fixed
+internalReference: 506660
+---
+
+## Summary
+
+
+The Match Multiple Received SKUs API (doc: https://developers.vtex.com/vtex-rest-api/reference/match-received-skus#matchmultiple) is returning the error message "Invalid sellerId" for any attempt of approving new products, even if the seller is correctly active on the marketplace.
+
+
+##
+
+## Simulation
+
+
+1. Copy the curl of the previous documentation;
+2. Paste it on your API tool (postman, insomnia...);
+3. Replace the object values with the data from the sku you're trying to approve;
+4. Check if the sellerId is active and valid on the marketplace's seller management;
+5. The API response should not be:
+
+    "errorResponse": { "Code": 33, "Message": "Invalid sellerId"        }
+
+
+
+
+##
+
+## Workaround
+
+
+The Match Received SKUs individually API is working correctly and can replace the previous API to approve new products one by one.
+
+
+
+
+
+
diff --git a/docs/known-issues/en/matcher-converting-height-width-weight-and-length-to-01.md b/docs/known-issues/en/matcher-converting-height-width-weight-and-length-to-01.md
new file mode 100644
index 000000000..0ab3ac91b
--- /dev/null
+++ b/docs/known-issues/en/matcher-converting-height-width-weight-and-length-to-01.md
@@ -0,0 +1,48 @@
+---
+title: 'Matcher converting Height, Width, Weight and Length to 0.1'
+id: j3rz875eWVHFMLYxcYsDL
+status: PUBLISHED
+createdAt: 2023-08-23T13:38:55.976Z
+updatedAt: 2023-08-23T20:01:37.842Z
+publishedAt: 2023-08-23T20:01:37.842Z
+firstPublishedAt: 2023-08-23T13:38:58.327Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: matcher-converting-height-width-weight-and-length-to-01
+locale: en
+kiStatus: Fixed
+internalReference: 886168
+---
+
+## Summary
+
+
+When the Matcher process the skus on the suggestions module of the marketplace the infos of Height, Width, Weight and Length are being set to 0.1 instead of respecting the values sent by the seller.
+
+
+##
+
+## Simulation
+
+
+
+1. Seller sends the sku to marketplace with Height, Width, Weight and Length with normal values;
+2. Sku gets to the marketplace and is processed by the matcher;
+3. Check on the following API if the Matcher object has the fields Height, Width, Weight and Length set as 0.1
+https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/-sellerId-/-sellerSkuId-
+ ![](https://vtexhelp.zendesk.com/attachments/token/vCdMBFKEJ0243C9Ew7PPFDgp3/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md b/docs/known-issues/en/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
new file mode 100644
index 000000000..646969aa8
--- /dev/null
+++ b/docs/known-issues/en/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
@@ -0,0 +1,46 @@
+---
+title: 'Matcher does not work as expected when the Product/SKU name contains special characters'
+id: 1kRjFExdSRMAJMgFgC7Bbj
+status: PUBLISHED
+createdAt: 2023-10-19T15:37:17.652Z
+updatedAt: 2023-10-19T15:37:18.601Z
+publishedAt: 2023-10-19T15:37:18.601Z
+firstPublishedAt: 2023-10-19T15:37:18.601Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters
+locale: en
+kiStatus: Fixed
+internalReference: 736164
+---
+
+## Summary
+
+
+When integrating products that have special characters in the name, such as `. - + # /` , Matcher gives a score of 50% and makes products stay in Pending. With this, the products depend on manual approval or via API.
+
+
+
+##
+
+## Simulation
+
+
+
+1. Through a VTEX seller, send an SKU that contains special characters in the name
+2. On the SKU Received page, see that the SKU in question will have a score of 50%, in the Pending tab
+
+
+##
+
+## Workaround
+
+
+To resolve the scenario it is indicated that the seller changes the SKU/product name, removing the special characters. If this is not possible, the marketplace can use the API https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/api.vtex.com/-accountName-/suggestions/matches/action/-actionName- to match the products
+
+
+
+
+
diff --git a/docs/known-issues/en/max-shipping-discount-not-updating-pricetags.md b/docs/known-issues/en/max-shipping-discount-not-updating-pricetags.md
new file mode 100644
index 000000000..720e5d1ee
--- /dev/null
+++ b/docs/known-issues/en/max-shipping-discount-not-updating-pricetags.md
@@ -0,0 +1,47 @@
+---
+title: 'Max Shipping Discount not updating priceTags'
+id: uA0KFnyIOHq3ikcaZmYGr
+status: PUBLISHED
+createdAt: 2023-09-20T17:54:59.620Z
+updatedAt: 2023-10-02T18:20:48.375Z
+publishedAt: 2023-10-02T18:20:48.375Z
+firstPublishedAt: 2023-09-20T17:55:00.609Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: max-shipping-discount-not-updating-pricetags
+locale: en
+kiStatus: Backlog
+internalReference: 904190
+---
+
+## Summary
+
+
+
+##
+Maximum shipping discount not returning price tags, when the seller tries to calculate the tax, the chk doesn't have the value to consider and consider the discount in the tax final value.
+
+
+
+##
+
+## Simulation
+
+
+Create a maximum shipping discount and a tax
+simulate a cart with both, you'll see that the price tag is not populated.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
new file mode 100644
index 000000000..309344198
--- /dev/null
+++ b/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -0,0 +1,67 @@
+---
+title: '"maximum number of eligible items for each cart" + more for less applies incorrect discount when using the same item.'
+id: gWIMhi9RCv9BE1RvV6GiM
+status: PUBLISHED
+createdAt: 2024-07-30T17:14:36.972Z
+updatedAt: 2024-07-30T17:14:37.931Z
+publishedAt: 2024-07-30T17:14:37.931Z
+firstPublishedAt: 2024-07-30T17:14:37.931Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item
+locale: en
+kiStatus: Backlog
+internalReference: 1073080
+---
+
+## Summary
+
+
+When using a more for less discount along with another promotion that uses the "maximum items per cart" for the same item, both of them accumulating, in incorrect discount is given, exceeding the initially configured setup.
+
+This happens due to the way that the checkout splits the items.
+
+For instance, let's say you have a more for less promotion (A) set to give a "100% discount for 1 item out of every 8 inserted in the cart".
+
+Along that, you have another promotion (B) that, for this same SKU, gives a 50% discount, limited to a maximum of 2 items.
+
+**What is expected**:
+
+If 80 items are inserted on the checkout, a total of 11 items should be given for free.  10 coming from (A), 1 coming from (B).
+
+**What actually happens**:
+
+The items are split into 3 different quantities in the checkout
+
+(1) those that only got the discount (A)
+(2) those that only got the discount (B)
+(3) those that got both discount (AB)
+
+However, line (2), which should have only 2 items with a 50% discount, actually replicates the 100% off from line (1), essentially giving 2 extra items off, in a total of 13 items, instead of 11.
+
+
+
+
+##
+
+## Simulation
+
+
+Create a promotion scenario as described above or similar to it, using the "maximum number of eligible items for each cart" and a more for less promotion, both set to accumulate.
+
+It is important to note that this issue only happens when **all of the promotions are configured for the same SKU**.
+
+
+##
+
+## Workaround
+
+
+n/a (avoid using these 2 specific setting together when operating with discounts for the same SKU).
+
+
+
+
+
diff --git a/docs/known-issues/en/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md b/docs/known-issues/en/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
new file mode 100644
index 000000000..3462805a7
--- /dev/null
+++ b/docs/known-issues/en/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
@@ -0,0 +1,45 @@
+---
+title: 'Maximum quantity setting of the same item in the cart cannot be changed by franchise accounts'
+id: 5NqcSpcmPXEJE4KIkp6eZE
+status: PUBLISHED
+createdAt: 2022-05-12T14:52:33.074Z
+updatedAt: 2023-10-18T14:34:56.570Z
+publishedAt: 2023-10-18T14:34:56.570Z
+firstPublishedAt: 2022-05-12T14:52:33.334Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts
+locale: en
+kiStatus: Backlog
+internalReference: 325273
+---
+
+## Summary
+
+
+The configuration of the maximum quantity of the same item in the cart cannot be changed by franchise accounts (seller whitelabel), as it takes place in a legacy catalog screen (/admin/Site/ConfigForm.aspx) – module that is removed from franchise accounts, as they inherit the products of the parent account.
+
+
+##
+
+## Simulation
+
+
+
+- Enter a franchise or whitelabel seller account environment
+- Access the screen "CMS > Settings > General tab" from the admin, or go directly to the page /admin/Site/ConfigForm.aspx
+- Note that it is not possible to access the content of this area
+
+
+##
+
+## Workaround
+
+
+Request the configuration via ticket to VTEX.
+
+
+
+
diff --git a/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
new file mode 100644
index 000000000..7eb1dc839
--- /dev/null
+++ b/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -0,0 +1,44 @@
+---
+title: 'MDv2 returns error "504 Gateway Timeout" when we try to update a document passing a symbol or special character.'
+id: 6GP5QBWyIAir2oKe08giT2
+status: PUBLISHED
+createdAt: 2023-08-09T13:04:34.819Z
+updatedAt: 2023-08-09T13:04:35.446Z
+publishedAt: 2023-08-09T13:04:35.446Z
+firstPublishedAt: 2023-08-09T13:04:35.446Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character
+locale: en
+kiStatus: Backlog
+internalReference: 852966
+---
+
+## Summary
+
+
+The behavior of the API when trying to update a document that contains a symbol in a field of type string such as `"name": "Product1 14€"`, will return the error 504 Gateway timeout and will not update the document.
+
+
+##
+
+## Simulation
+
+
+
+1. Make a PUT request to update a document through the API, in the body include the special character in a field of type string.
+
+    { "name": "Product1 14€", ...}
+
+2.  Look at the API response and verify that it returns the error 504 Gateway timeout.
+
+
+##
+
+## Workaround
+
+
+Delete the special character and enter the name of the symbol. For example: "`14 euros`"
+
diff --git a/docs/known-issues/en/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md b/docs/known-issues/en/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
new file mode 100644
index 000000000..aba74c5d1
--- /dev/null
+++ b/docs/known-issues/en/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
@@ -0,0 +1,50 @@
+---
+title: '[MELI] Attribute is being sent to MELI without being mapped from seller'
+id: CILYWlvEAlXkcvEYuZ99m
+status: PUBLISHED
+createdAt: 2023-10-30T10:09:31.578Z
+updatedAt: 2023-11-30T11:05:05.907Z
+publishedAt: 2023-11-30T11:05:05.907Z
+firstPublishedAt: 2023-10-30T10:09:32.150Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller
+locale: en
+kiStatus: Fixed
+internalReference: 791380
+---
+
+## Summary
+
+
+
+We currently have an issue which still needs more investigation and details, But there are some categories mapped inside the Mapper feature, and for some attributes which were not mapped but they are currently being sent to MELI.
+
+This will result in some SKUs being exported and some won't as the first SKU includes and undesired attribute, and second SKU won't be exported as MELI have rules that requires all variantion inside the same product must have same attribute combinations.
+
+
+##
+
+## Simulation
+
+
+
+Inside bridge product menu, you will see an error for some SKUs as seen below:
+**Variations with different attribute combinations are not allowed.**
+
+This is due to first SKU exported with undesired attribute, and the rest of SKUs are not being sent to that attribute.
+
+
+##
+
+## Workaround
+
+
+Is there a workaround for this bug? If yes, describe it here. If not, write "N/A" or "There is no workaround available.". Do not remove this section if there is no workaround, please.
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md b/docs/known-issues/en/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
index 40844f9b6..eda1535c2 100644
--- a/docs/known-issues/en/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
+++ b/docs/known-issues/en/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
@@ -3,8 +3,8 @@ title: '[Meli] Attributes Negro_#000000 integration with a non expected behavior
 id: 1GPrObE1SQPP4ScyNHyjDt
 status: PUBLISHED
 createdAt: 2022-09-19T14:04:56.594Z
-updatedAt: 2022-11-25T21:55:27.032Z
-publishedAt: 2022-11-25T21:55:27.032Z
+updatedAt: 2024-02-16T20:28:12.568Z
+publishedAt: 2024-02-16T20:28:12.568Z
 firstPublishedAt: 2022-09-19T14:04:57.386Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: meli-attributes-negro000000-integration-with-a-non-expected-behavior
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 660703
 ---
 
diff --git a/docs/known-issues/en/meli-automatic-messages-mercado-livre-messages.md b/docs/known-issues/en/meli-automatic-messages-mercado-livre-messages.md
index 353140a56..020aa29c8 100644
--- a/docs/known-issues/en/meli-automatic-messages-mercado-livre-messages.md
+++ b/docs/known-issues/en/meli-automatic-messages-mercado-livre-messages.md
@@ -3,8 +3,8 @@ title: 'MELI automatic messages Mercado Livre - Messages'
 id: 6WZy5RNesYJtJOaBAFnbkW
 status: PUBLISHED
 createdAt: 2023-05-04T11:22:21.762Z
-updatedAt: 2023-05-08T18:33:14.421Z
-publishedAt: 2023-05-08T18:33:14.421Z
+updatedAt: 2024-01-30T10:48:09.504Z
+publishedAt: 2024-01-30T10:48:09.504Z
 firstPublishedAt: 2023-05-04T11:22:22.366Z
 contentType: knownIssue
 productTeam: Connections
@@ -20,7 +20,7 @@ internalReference: 615164
 
 
 
-Currently our MELI APP to send automatic messages to MELI is having some issues with ME2 logistic mode.
+Currently our MELI APP to send automatic messages to MELI is having some issues while using the template messages.
 
 
 ##
@@ -29,7 +29,7 @@ Currently our MELI APP to send automatic messages to MELI is having some issues
 
 
 
-The automatic messages in VTEX admin for ME2 logistic mode, will not be sent to seller.
+The automatic messages in VTEX admin sometimes are not being sent to MELI..
 
 
 ##
diff --git a/docs/known-issues/en/meli-bridge-orders-menu-not-showing-the-orderid-information.md b/docs/known-issues/en/meli-bridge-orders-menu-not-showing-the-orderid-information.md
new file mode 100644
index 000000000..26499fbc1
--- /dev/null
+++ b/docs/known-issues/en/meli-bridge-orders-menu-not-showing-the-orderid-information.md
@@ -0,0 +1,45 @@
+---
+title: 'MELI Bridge Orders menu, not showing the orderID information'
+id: ZBc9ny043rVpYFqkZIQ1K
+status: PUBLISHED
+createdAt: 2023-08-16T10:46:52.015Z
+updatedAt: 2023-10-05T18:51:13.700Z
+publishedAt: 2023-10-05T18:51:13.700Z
+firstPublishedAt: 2023-08-16T10:46:53.089Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-bridge-orders-menu-not-showing-the-orderid-information
+locale: en
+kiStatus: Fixed
+internalReference: 881733
+---
+
+## Summary
+
+
+
+Currently we have an issue that only affects the visibility of some MELI Orders, what happens is that we are currently logging the ShipmentID in order bridge menu, but some error messages are missing the OrderID, and it's necessary for some cases as the orderID is the information the sellers have in MELI Portal
+
+
+##
+
+## Simulation
+
+
+
+Inside the bridge orders menu, some error messages are not logging the orderID, which gives the impressions some orders are not in VTEX brige, but the sellers can find the orders by searching for the shipmentID.
+
+
+##
+
+## Workaround
+
+
+Search for the shipmentID instead of the orderID
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md b/docs/known-issues/en/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
new file mode 100644
index 000000000..33223711b
--- /dev/null
+++ b/docs/known-issues/en/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
@@ -0,0 +1,45 @@
+---
+title: 'MELI Buybox ADs are not being paused when the marketplace AD is paused'
+id: 5OFALDi7lY93D7KkZ4scvg
+status: PUBLISHED
+createdAt: 2023-09-29T19:12:14.424Z
+updatedAt: 2023-10-09T20:52:25.672Z
+publishedAt: 2023-10-09T20:52:25.672Z
+firstPublishedAt: 2023-09-29T19:12:15.051Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused
+locale: en
+kiStatus: Fixed
+internalReference: 910371
+---
+
+## Summary
+
+
+
+Currently we have an issue with Buybox MELI flow, which is when removing the SKU from SC for example, the marketplace AD is being paused in MELi, but the Buybox AD remains active.
+
+
+##
+
+## Simulation
+
+
+
+When the marketplace AD is paused in MELI, by the reason of being removed from VTEX SC for example, the Buybox AD would need to be paused as well.
+
+
+##
+
+## Workaround
+
+
+Is there a workaround for this bug? If yes, describe it here. If not, write "N/A" or "There is no workaround available.". Do not remove this section if there is no workaround, please.
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-error-while-sending-the-order-tracking.md b/docs/known-issues/en/meli-error-while-sending-the-order-tracking.md
index 2ad7b92b4..dad9e4ce5 100644
--- a/docs/known-issues/en/meli-error-while-sending-the-order-tracking.md
+++ b/docs/known-issues/en/meli-error-while-sending-the-order-tracking.md
@@ -3,8 +3,8 @@ title: 'MELI error while sending the order tracking'
 id: 4wdzb5xjelAkFnbuRCFXAt
 status: PUBLISHED
 createdAt: 2023-03-06T10:06:58.255Z
-updatedAt: 2023-03-06T10:06:59.162Z
-publishedAt: 2023-03-06T10:06:59.162Z
+updatedAt: 2023-10-20T17:28:38.314Z
+publishedAt: 2023-10-20T17:28:38.314Z
 firstPublishedAt: 2023-03-06T10:06:59.162Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: meli-error-while-sending-the-order-tracking
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 764885
 ---
 
diff --git a/docs/known-issues/en/meli-freight-quotation-for-multiple-officialstoreids.md b/docs/known-issues/en/meli-freight-quotation-for-multiple-officialstoreids.md
new file mode 100644
index 000000000..cdb225466
--- /dev/null
+++ b/docs/known-issues/en/meli-freight-quotation-for-multiple-officialstoreids.md
@@ -0,0 +1,44 @@
+---
+title: 'MELI Freight quotation for multiple officialStoreIDs'
+id: 4KdPYtRbDdsBrn2k0dz7oc
+status: PUBLISHED
+createdAt: 2024-02-07T11:19:11.169Z
+updatedAt: 2024-06-19T11:43:56.663Z
+publishedAt: 2024-06-19T11:43:56.663Z
+firstPublishedAt: 2024-02-07T11:19:12.139Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-freight-quotation-for-multiple-officialstoreids
+locale: en
+kiStatus: Fixed
+internalReference: 978358
+---
+
+## Summary
+
+
+Currently we have an issue with MELI integration regarding the Freight quotation API from MELI, this is applied only for sellers using multiple officialStoreIDs in MELI, but using only one account in VTEX using the same sellerID in MELI
+
+
+##
+
+## Simulation
+
+
+
+If this scenario is applied the freight quotation from MELI will return error, and MELI will redirect the seller to freight spreadsheet instead of using the freight API.
+
+
+##
+
+## Workaround
+
+
+keep the freight spreadsheet updated to avoid inconsistencies beteween VTEX and MELI
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-full-orders-not-creating-invoice-in-vtex.md b/docs/known-issues/en/meli-full-orders-not-creating-invoice-in-vtex.md
new file mode 100644
index 000000000..7ca6d29eb
--- /dev/null
+++ b/docs/known-issues/en/meli-full-orders-not-creating-invoice-in-vtex.md
@@ -0,0 +1,45 @@
+---
+title: 'MELI FULL orders not creating Invoice in VTEX'
+id: 6SNkDcqCWeDDPm01RrM0FQ
+status: PUBLISHED
+createdAt: 2024-02-05T11:14:30.020Z
+updatedAt: 2024-02-05T11:14:31.187Z
+publishedAt: 2024-02-05T11:14:31.187Z
+firstPublishedAt: 2024-02-05T11:14:31.187Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-full-orders-not-creating-invoice-in-vtex
+locale: en
+kiStatus: Backlog
+internalReference: 976614
+---
+
+## Summary
+
+
+
+Currently we have an issue with MELI FULL orders, if the order presented any error during the creating in VTEX, such as SLA error, out of stock, etc. the process to create the invoice in VTEX is not executed. Basically the XML inside embeddedInvocie of OMS is not being created in these cases.
+
+
+##
+
+## Simulation
+
+
+
+If the order presented any error during it's creation, the XML will not placed inside VTEX OMS.
+
+
+##
+
+## Workaround
+
+
+to avoid this error the orders should not be stucked in VTEX Bridge, for that always configure the necessary SLAs to avoid this error
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-incorrect-value-when-client-has-coupon-on-meli.md b/docs/known-issues/en/meli-incorrect-value-when-client-has-coupon-on-meli.md
new file mode 100644
index 000000000..fd8d30774
--- /dev/null
+++ b/docs/known-issues/en/meli-incorrect-value-when-client-has-coupon-on-meli.md
@@ -0,0 +1,46 @@
+---
+title: 'MELI incorrect value when client has Coupon on MELI'
+id: 3PvNKqG2BMZDBLLVuriIHy
+status: PUBLISHED
+createdAt: 2024-01-22T11:58:00.747Z
+updatedAt: 2024-01-22T11:58:01.431Z
+publishedAt: 2024-01-22T11:58:01.431Z
+firstPublishedAt: 2024-01-22T11:58:01.431Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-incorrect-value-when-client-has-coupon-on-meli
+locale: en
+kiStatus: Backlog
+internalReference: 969297
+---
+
+## Summary
+
+
+
+Currently the client used a coupon in MELI, there is a variety of coupon types in MELI. And some of them are not included in VTEX OMS calculations.
+
+
+##
+
+## Simulation
+
+
+
+In VTEX OMS, the value of the order can be different from what MELI sold to the client, due to some coupon type are not being considering while creating the order in VTEX.
+
+
+##
+
+## Workaround
+
+
+
+For ME1 orders, if the seller needs to have the correct value of the order, in order to send the invoice value to MELI, they can use the field in VTEX OMS called "total_paid_amount", this field is currently considering all coupon values.
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
new file mode 100644
index 000000000..249703cb2
--- /dev/null
+++ b/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -0,0 +1,51 @@
+---
+title: 'MELI integration is receiving errors from MELI "429 too many requests"'
+id: 1e4g9nzZFyanywmLbSHq4D
+status: PUBLISHED
+createdAt: 2023-08-03T10:47:41.602Z
+updatedAt: 2023-08-14T14:08:12.646Z
+publishedAt: 2023-08-14T14:08:12.646Z
+firstPublishedAt: 2023-08-03T10:47:43.214Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-integration-is-receiving-errors-from-meli-429-too-many-requests
+locale: en
+kiStatus: Fixed
+internalReference: 873998
+---
+
+## Summary
+
+
+
+We currently have an issue with some accounts in MELi which are getting an error while trying to update products, stock or price in MELI.
+
+This is not affecting all accounts and not all SKUs, but only part of them, and this is caused due to sending more requests then MELI is currently prepared to receive.
+
+
+##
+
+## Simulation
+
+
+
+Inside integration stock/price/product menu some account may see an error:
+
+**Sorry, we couldn't process this request. Please, wait a few minutes and reprocess it**
+
+We are working on how to better handle the requests to avoid getting this error from MELI.
+
+
+##
+
+## Workaround
+
+
+The only workaround available for now is to reprocess the request directly in bridge menu.
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md b/docs/known-issues/en/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
new file mode 100644
index 000000000..a1347284a
--- /dev/null
+++ b/docs/known-issues/en/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
@@ -0,0 +1,45 @@
+---
+title: 'MELI integration listing types for Peru, Venezuela, Equador and Uruguai'
+id: 77DQc7iQ4KgiWZGRAGdTgT
+status: PUBLISHED
+createdAt: 2023-10-25T11:48:14.580Z
+updatedAt: 2023-10-25T11:48:15.479Z
+publishedAt: 2023-10-25T11:48:15.479Z
+firstPublishedAt: 2023-10-25T11:48:15.479Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai
+locale: en
+kiStatus: Backlog
+internalReference: 925139
+---
+
+## Summary
+
+
+
+Currently our MELI application is not sending the correct listing type for countries **Peru, Venezuela, Equador and Uruguai**
+
+
+##
+
+## Simulation
+
+
+
+Whenever the sellers enables MELI Classic in VTEX for countries **Peru, Venezuela, Equador and Uruguai** the ADs will be created as Premium.
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md
index 9befa9717..a9150b021 100644
--- a/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -3,8 +3,8 @@ title: 'MELI integration ZIPCodes "11111" Meli - Lima/Perú'
 id: 7ICcek0NOUczgtA65CaZk5
 status: PUBLISHED
 createdAt: 2023-05-16T17:50:38.417Z
-updatedAt: 2023-05-16T17:50:39.140Z
-publishedAt: 2023-05-16T17:50:39.140Z
+updatedAt: 2023-08-16T12:43:27.706Z
+publishedAt: 2023-08-16T12:43:27.706Z
 firstPublishedAt: 2023-05-16T17:50:39.140Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: meli-integration-zipcodes-11111-meli-limaperu
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 826566
 ---
 
diff --git a/docs/known-issues/en/meli-mapper-incorrectly-sending-product-specification-as-variation.md b/docs/known-issues/en/meli-mapper-incorrectly-sending-product-specification-as-variation.md
new file mode 100644
index 000000000..b79cab602
--- /dev/null
+++ b/docs/known-issues/en/meli-mapper-incorrectly-sending-product-specification-as-variation.md
@@ -0,0 +1,44 @@
+---
+title: 'MELI Mapper incorrectly sending product specification as variation'
+id: 6b49pUUxL3B3RtUWofLjL8
+status: PUBLISHED
+createdAt: 2023-06-27T11:20:49.475Z
+updatedAt: 2023-06-27T11:20:50.484Z
+publishedAt: 2023-06-27T11:20:50.484Z
+firstPublishedAt: 2023-06-27T11:20:50.484Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-mapper-incorrectly-sending-product-specification-as-variation
+locale: en
+kiStatus: Backlog
+internalReference: 851021
+---
+
+## Summary
+
+
+
+We currently have an issue in MELI Mapper feature, which we decide to send a SKU as variation based on MELI's category attributes, and not based on what seller has mapped in VTEX, which means a product specification mapped in VTEX can be sent as variation to MELI.
+
+
+##
+
+## Simulation
+
+
+
+Inside the mapper feature whenever the seller mapped an attribute that accepts variation in MELI it will be sent as variation, even if the seller mapped inside the product specification.
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
diff --git a/docs/known-issues/en/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md b/docs/known-issues/en/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
new file mode 100644
index 000000000..9d81393ba
--- /dev/null
+++ b/docs/known-issues/en/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
@@ -0,0 +1,46 @@
+---
+title: 'MELI Orders not being cancelled in VTEX OMS for multiples accounts scenario'
+id: 4u9ue93sHNWcfVm3sRL2qx
+status: PUBLISHED
+createdAt: 2024-02-06T11:04:52.918Z
+updatedAt: 2024-02-06T11:04:54.082Z
+publishedAt: 2024-02-06T11:04:54.082Z
+firstPublishedAt: 2024-02-06T11:04:54.082Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario
+locale: en
+kiStatus: Backlog
+internalReference: 977453
+---
+
+## Summary
+
+
+
+Currently our MELI integration has an issue related to the process of cancelling orders. When MELI cancel an order and the seller has more than 4 accounts in VTEX there is a chance of not trying to cancel the order in the fifth account
+
+
+##
+
+## Simulation
+
+
+
+If the cancellation of the order cannot be completed the seller may see the order not cancelled in VTEX but cancelled in MELI, for this case a manual cancellation is required directly in OMS.
+This is only applied for cases that the seller has more than 4 accounts in VTEX, using the same MELI UserID.
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-size-chart-not-working-for-sizes-with-letters.md b/docs/known-issues/en/meli-size-chart-not-working-for-sizes-with-letters.md
new file mode 100644
index 000000000..bd15e4ceb
--- /dev/null
+++ b/docs/known-issues/en/meli-size-chart-not-working-for-sizes-with-letters.md
@@ -0,0 +1,50 @@
+---
+title: 'MELI Size Chart not working for sizes with Letters'
+id: 7vAViV3MmC7zOSTF0cFTYy
+status: PUBLISHED
+createdAt: 2023-07-24T12:04:19.589Z
+updatedAt: 2023-09-12T15:04:46.716Z
+publishedAt: 2023-09-12T15:04:46.716Z
+firstPublishedAt: 2023-07-24T12:04:20.171Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-size-chart-not-working-for-sizes-with-letters
+locale: en
+kiStatus: Fixed
+internalReference: 867262
+---
+
+## Summary
+
+
+
+Currently our MELI Size Chart feature is not working for sizes with letters example:
+
+Size = "P", "M", "G".
+
+
+##
+
+## Simulation
+
+
+
+Inside the mapper screen, we can the Size chart feature available for MELI Integration, So if the sellers maps a size with it's values as letters it won't work and a error message will be shown at bridge product like below:
+
+"O valor do atributo SIZE é invalido: P. Este valor deve ser igual ao da tabela de medidas."
+
+
+##
+
+## Workaround
+
+
+
+The sizes are currently working with numbers, so sellers can use the numbers instead of letters.
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-sizechart-issue-attribute-not-valid.md b/docs/known-issues/en/meli-sizechart-issue-attribute-not-valid.md
new file mode 100644
index 000000000..e71a581c3
--- /dev/null
+++ b/docs/known-issues/en/meli-sizechart-issue-attribute-not-valid.md
@@ -0,0 +1,45 @@
+---
+title: 'MELI SizeChart issue attribute not valid'
+id: 3t6zqW9aE6pvW9b3Zvj0MB
+status: PUBLISHED
+createdAt: 2024-03-08T13:59:23.756Z
+updatedAt: 2024-03-11T20:00:06.480Z
+publishedAt: 2024-03-11T20:00:06.480Z
+firstPublishedAt: 2024-03-08T13:59:24.514Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-sizechart-issue-attribute-not-valid
+locale: en
+kiStatus: Fixed
+internalReference: 996639
+---
+
+## Summary
+
+
+
+Mercado Livre has recently included new mandatory attributes in the size chart integration feature, so we now should fix our integration with this new attributes in order for the sellers to be able to correctly export size charts to MELI.
+
+
+##
+
+## Simulation
+
+
+
+While uploading the size chart in the UI, you may see an error "Attribute XXX is not valid", this maybe related to this error
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/meli-update-stockprice-issue.md b/docs/known-issues/en/meli-update-stockprice-issue.md
new file mode 100644
index 000000000..1ad3d69cb
--- /dev/null
+++ b/docs/known-issues/en/meli-update-stockprice-issue.md
@@ -0,0 +1,45 @@
+---
+title: 'MELI Update Stock/Price issue'
+id: 7LQ81vG5nsbBn4Wj7Z9VJe
+status: PUBLISHED
+createdAt: 2023-12-12T10:22:28.961Z
+updatedAt: 2024-01-10T17:51:59.853Z
+publishedAt: 2024-01-10T17:51:59.853Z
+firstPublishedAt: 2023-12-12T10:22:29.656Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-update-stockprice-issue
+locale: en
+kiStatus: Fixed
+internalReference: 939329
+---
+
+## Summary
+
+
+
+We currently have a very specific scenario affecting few cases of SKUs not being able to update the stock on MELI.
+
+
+##
+
+## Simulation
+
+
+
+What happens is that some cases the seller_custom_field which should be filled with the VTEX SKU, is actually blank, and so the integration is not able to update the MELI stock in this cases.
+
+
+##
+
+## Workaround
+
+
+Fill the migration spreadsheet with this cases and send to product team to set our SKU inside seller_custom_field.
+
+
+
+
+
diff --git a/docs/known-issues/en/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md b/docs/known-issues/en/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
new file mode 100644
index 000000000..75e231842
--- /dev/null
+++ b/docs/known-issues/en/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
@@ -0,0 +1,55 @@
+---
+title: "[Mercado Livre] AD BuyBox doesn't update shipping_mode for ME2"
+id: 5XmZsbZz1171a04dWPs2MY
+status: PUBLISHED
+createdAt: 2024-06-03T11:38:34.337Z
+updatedAt: 2024-06-03T11:38:35.242Z
+publishedAt: 2024-06-03T11:38:35.242Z
+firstPublishedAt: 2024-06-03T11:38:35.242Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2
+locale: en
+kiStatus: Backlog
+internalReference: 1042779
+---
+
+## Summary
+
+
+AD BuyBox doesn't update shipping_mode for ME2
+
+
+##
+
+## Simulation
+
+
+
+Q: Why is the ad in under_review when I try to update ME2?
+A: Today the status of this ad on MELI is under_review, this happens because it is a BuyBox type ad and in this case we cannot update it to ME2 because MELI doesn't allow it, and for this reason when we try to update MELI it returns the following moderation:
+
+
+    Não é possível processar uma solicitação de um anúncio moderado pelo Mercado Livre.<br><br>Resumo da moderação: <br><br>Razão: Cancelamos o anúncio porque você só pode vender este produto com seu anúncio de catálogo. <br>Remédio: Cancelamos o anúncio porque você só pode vender este produto com seu anúncio de catálogo.
+
+
+Q: So will this happen for all buybox ads?
+A: No, this scenario will only happen when the case is for "Restrict catalog" where there can only be a BuyBox advertisement, not because it's BuyBox but because it's this specific Restrict type.
+
+**SOLUTION**
+As we don't have this ME2 update flow for buybox ads, we are opening this KI
+
+
+##
+
+## Workaround
+
+
+Open a ticket to the connections team requesting an update for ME2, always informing the buybox ad ex: MLB36470123456
+
+
+
+
+
diff --git a/docs/known-issues/en/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/en/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
new file mode 100644
index 000000000..d2fb5bd2f
--- /dev/null
+++ b/docs/known-issues/en/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
@@ -0,0 +1,50 @@
+---
+title: "[Mercado Livre] [Bridge] Bridge isn't logging some error messages"
+id: 3KmdcY6hlLQx5h1FgKHAbS
+status: PUBLISHED
+createdAt: 2024-06-21T12:38:31.025Z
+updatedAt: 2024-06-26T11:07:40.994Z
+publishedAt: 2024-06-26T11:07:40.994Z
+firstPublishedAt: 2024-06-21T12:38:31.845Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-bridge-bridge-isnt-logging-some-error-messages
+locale: en
+kiStatus: Backlog
+internalReference: 1053742
+---
+
+## Summary
+
+
+Error in the update flow sku isn't being logged into the bridge
+
+**Marketplace:** Mercado Livre
+**Root Cause:** Admin > Bridge > Product
+
+**Important:** doesn't happen with all skus;
+
+
+##
+
+## Simulation
+
+
+Admin > Marketplace > Products > Amazon
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/3MxTLEnmPv9lgG7UE8iUEd1Ft/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+In some cases, reprocessing the sku on the bridge resolve the problem.
+
+
+
+
+
diff --git a/docs/known-issues/en/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md b/docs/known-issues/en/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
new file mode 100644
index 000000000..005d38822
--- /dev/null
+++ b/docs/known-issues/en/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
@@ -0,0 +1,47 @@
+---
+title: '[Mercado Livre] Bridge Orders menu, not showing the shippingID information'
+id: 2fXDbejpPJ04NDfPCCcr0j
+status: PUBLISHED
+createdAt: 2024-03-18T20:56:17.859Z
+updatedAt: 2024-03-18T20:56:18.697Z
+publishedAt: 2024-03-18T20:56:18.697Z
+firstPublishedAt: 2024-03-18T20:56:18.697Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information
+locale: en
+kiStatus: Backlog
+internalReference: 1001903
+---
+
+## Summary
+
+
+Currently we have an issue that only affects the visibility of some MELI Orders, what happens is that we are currently logging the ShipmentID in order bridge menu, but some error messages are missing the OrderID, and it's necessary for some cases as the orderID is the information the sellers have in MELI Portal
+
+Mercado Livre  > Bridge  > OrderId
+
+
+##
+
+## Simulation
+
+
+Inside the bridge orders menu, some error messages are not logging the orderID, which gives the impressions some orders are not in VTEX brige, but the sellers can find the orders by searching for the shipmentID.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/OZk1c79PgvKBKq6wGldvIbHM6/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+GET the OrderID, and get the ShipmentID and look for it in the bridge
+
+
+
+
+
diff --git a/docs/known-issues/en/mercado-livre-mapper-attribute-size.md b/docs/known-issues/en/mercado-livre-mapper-attribute-size.md
index 820810252..00dd3aa95 100644
--- a/docs/known-issues/en/mercado-livre-mapper-attribute-size.md
+++ b/docs/known-issues/en/mercado-livre-mapper-attribute-size.md
@@ -3,8 +3,8 @@ title: 'Mercado Livre Mapper attribute Size'
 id: 3dLrm6SVsPB4tU46SC3Xdi
 status: PUBLISHED
 createdAt: 2022-07-26T19:53:34.899Z
-updatedAt: 2022-11-25T21:55:42.119Z
-publishedAt: 2022-11-25T21:55:42.119Z
+updatedAt: 2024-02-16T20:28:24.174Z
+publishedAt: 2024-02-16T20:28:24.174Z
 firstPublishedAt: 2022-07-26T19:53:35.449Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: mercado-livre-mapper-attribute-size
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 592577
 ---
 
@@ -23,6 +23,7 @@ internalReference: 592577
 Even mapping correctly the attribute "Size" in mapper, for some MELI categories it's not working properly.
 
 
+##
 
 ## Simulation
 
@@ -31,9 +32,14 @@ Even mapping correctly the attribute "Size" in mapper, for some MELI categories
 Inside bridge products menu, you will see an error about the attribute Size in MELI.
 
 
+##
 
 ## Workaround
 
 
-n/a
+Is there a workaround for this bug? If yes, describe it here. If not, write "N/A" or "There is no workaround available.". Do not remove this section if there is no workaround, please.
+
+
+
+
 
diff --git a/docs/known-issues/en/mercado-livre-remove-underreview-validation-in-update-sku.md b/docs/known-issues/en/mercado-livre-remove-underreview-validation-in-update-sku.md
new file mode 100644
index 000000000..1088d9cff
--- /dev/null
+++ b/docs/known-issues/en/mercado-livre-remove-underreview-validation-in-update-sku.md
@@ -0,0 +1,43 @@
+---
+title: '[Mercado Livre] Remove under_review validation in Update SKU'
+id: 1yeZeigiok3zaltkI7RTMW
+status: PUBLISHED
+createdAt: 2023-08-30T18:15:25.269Z
+updatedAt: 2023-08-30T18:15:25.924Z
+publishedAt: 2023-08-30T18:15:25.924Z
+firstPublishedAt: 2023-08-30T18:15:25.924Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-remove-underreview-validation-in-update-sku
+locale: en
+kiStatus: Backlog
+internalReference: 890658
+---
+
+## Summary
+
+
+Remove under_review validation in Update SKU flow because when the seller applies the actions to fix the moderation cases and these are related with the catalog we are not sending those changes to MELI and finally the MELI ads continue being moderated.
+
+
+##
+
+## Simulation
+
+
+SKU was moderated for being in the wrong category, the correction has already been made and now it has the correct mapping in mapepr, but it is still not being exported according to the mapper category.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/en/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
new file mode 100644
index 000000000..2247d4f3b
--- /dev/null
+++ b/docs/known-issues/en/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
@@ -0,0 +1,44 @@
+---
+title: "[Mercado Livre] [Sku] Bridge isn't logging some error messages"
+id: 2GcnFE9TKcivoPekYuCNF9
+status: PUBLISHED
+createdAt: 2024-07-23T16:00:26.447Z
+updatedAt: 2024-07-23T16:08:16.661Z
+publishedAt: 2024-07-23T16:08:16.661Z
+firstPublishedAt: 2024-07-23T16:00:27.366Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-sku-bridge-isnt-logging-some-error-messages
+locale: en
+kiStatus: Backlog
+internalReference: 1069692
+---
+
+## Summary
+
+
+Correct context: In some cases, seller is unable to integrate the SKU, as the error message with the reason why the item was moderated does not appear correctly in Bridge.
+
+
+
+##
+
+## Simulation
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/8b6ggO2OjPCsPZlU5NanwK645/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md
new file mode 100644
index 000000000..6201a1727
--- /dev/null
+++ b/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -0,0 +1,50 @@
+---
+title: 'Merchandising rules not working for the facet "productClusterIds"'
+id: 6sLODMgjuoyJD52uc0DBW1
+status: PUBLISHED
+createdAt: 2024-07-09T00:02:40.930Z
+updatedAt: 2024-07-09T00:02:41.798Z
+publishedAt: 2024-07-09T00:02:41.798Z
+firstPublishedAt: 2024-07-09T00:02:41.798Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: merchandising-rules-not-working-for-the-facet-productclusterids
+locale: en
+kiStatus: Backlog
+internalReference: 1062457
+---
+
+## Summary
+
+
+Merchandising rules are not applied to the facet "productClusterIds". This happens because this facet has the special behavior of sorting the products by the collection order instead of relevance and merch rules.
+
+This facet should not be considered valid for a merch rule.
+
+
+##
+
+## Simulation
+
+
+
+- create a collection with some products in a specific order
+- create a merch rule explicitly filtered by "productClusterIds" or "productClusterSearchableIds"
+- set this rule to sort the products in a different order
+- check in the store that the products will keep the collection sorting
+
+
+##
+
+## Workaround
+
+
+The expected way to manage and sort products in a collection is to do it directly on the collection by adding/removing products or changing their position.
+
+It's also possible to apply the merch rule to the facet "productClusterNames" instead. This facet follows the relevance rules instead of the collection order and works with merchandising rules.
+
+
+
+
diff --git a/docs/known-issues/en/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md b/docs/known-issues/en/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
new file mode 100644
index 000000000..19a4e9cf2
--- /dev/null
+++ b/docs/known-issues/en/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
@@ -0,0 +1,51 @@
+---
+title: 'Merchant not being able to open account for some clients in Customer Credit API'
+id: 4NGCingtQxzFV1gMbxFzT1
+status: PUBLISHED
+createdAt: 2023-09-25T13:22:58.063Z
+updatedAt: 2023-09-25T13:22:58.651Z
+publishedAt: 2023-09-25T13:22:58.651Z
+firstPublishedAt: 2023-09-25T13:22:58.651Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api
+locale: en
+kiStatus: Backlog
+internalReference: 906509
+---
+
+## Summary
+
+
+For some reason, when trying to open a new account for specific clients through the API, it returns the following error:
+
+{
+"code": 1099,
+"message": "The Credit Account is already open."
+}
+
+
+In this scenario, the data of the client (Name, document, etc.) has never been used before on any other account.
+
+
+##
+
+## Simulation
+
+
+This happens inconsistently, so it will only happen every other attempt.
+
+
+##
+
+## Workaround
+
+
+Create the account via Admin UI.
+
+
+
+
+
diff --git a/docs/known-issues/en/messages-app-taking-too-long-to-return-the-informations.md b/docs/known-issues/en/messages-app-taking-too-long-to-return-the-informations.md
new file mode 100644
index 000000000..3c3176ea3
--- /dev/null
+++ b/docs/known-issues/en/messages-app-taking-too-long-to-return-the-informations.md
@@ -0,0 +1,40 @@
+---
+title: 'Messages app taking too long to return the informations'
+id: 5GnHyQaPlqCW0KNar1tlMC
+status: PUBLISHED
+createdAt: 2024-01-30T14:16:58.627Z
+updatedAt: 2024-01-30T14:16:59.326Z
+publishedAt: 2024-01-30T14:16:59.326Z
+firstPublishedAt: 2024-01-30T14:16:59.326Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: messages-app-taking-too-long-to-return-the-informations
+locale: en
+kiStatus: Backlog
+internalReference: 567305
+---
+
+## Summary
+
+
+In the indexation process, we call the messages app to save translated information on the products, the main issue is that the requests are taking too long to return and with that, some stores that have lots of languages either do not index fully or have their indexations stuck.
+
+
+##
+
+## Simulation
+
+
+Check any store that has a great amount of languages, more than 10 and it will start to slow the response of the messages.
+It can reflect other systems that depend on the messages to translate information.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/metatagdescription-field-cannot-be-deleted-through-admin.md b/docs/known-issues/en/metatagdescription-field-cannot-be-deleted-through-admin.md
new file mode 100644
index 000000000..be51ec873
--- /dev/null
+++ b/docs/known-issues/en/metatagdescription-field-cannot-be-deleted-through-admin.md
@@ -0,0 +1,47 @@
+---
+title: "'MetaTagDescription' field cannot be deleted through Admin"
+id: 7h0HlpuQnE8nWylgSWJ1lR
+status: PUBLISHED
+createdAt: 2024-02-08T20:21:00.735Z
+updatedAt: 2024-02-08T20:21:01.739Z
+publishedAt: 2024-02-08T20:21:01.739Z
+firstPublishedAt: 2024-02-08T20:21:01.739Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: metatagdescription-field-cannot-be-deleted-through-admin
+locale: en
+kiStatus: Backlog
+internalReference: 979691
+---
+
+## Summary
+
+
+There is an inconsistent behavior in the `MetaTagDescription` field within the product registration, which cannot be deleted through the Admin but is possible to delete through API. In the Admin, when clicking "save" with this field empty, the value from the field `Description` is copied. This scenario doesn't happen when using the API, the value is correctly deleted.
+
+
+##
+
+## Simulation
+
+
+
+- Click on the product to edit
+- Delete the value from the field `MetaTagDescription`
+- Click "save" and return to the product
+- Check that the original value is not there anymore, but the value from the `description` was duplicated
+
+
+##
+
+## Workaround
+
+
+Use the API to delete the undesired value after updating the product in the Admin
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/product/-productId-?endpoint=put-/api/catalog/pvt/product/-productId-
+
+
+
+
diff --git a/docs/known-issues/en/minicart-coupon-error-messages-only-appear-after-a-second-try.md b/docs/known-issues/en/minicart-coupon-error-messages-only-appear-after-a-second-try.md
new file mode 100644
index 000000000..0226fe1a4
--- /dev/null
+++ b/docs/known-issues/en/minicart-coupon-error-messages-only-appear-after-a-second-try.md
@@ -0,0 +1,49 @@
+---
+title: 'Minicart Coupon error messages only appear after a second try'
+id: 6ZdpXaHJFudXXwUDC00lcr
+status: PUBLISHED
+createdAt: 2023-12-18T16:22:10.537Z
+updatedAt: 2023-12-18T16:22:11.359Z
+publishedAt: 2023-12-18T16:22:11.359Z
+firstPublishedAt: 2023-12-18T16:22:11.359Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: minicart-coupon-error-messages-only-appear-after-a-second-try
+locale: en
+kiStatus: No Fix
+internalReference: 938379
+---
+
+## Summary
+
+
+Coupon error in Minicart messages wont appear the first time you try a coupon, even if it doesnt exist.
+
+
+##
+
+## Simulation
+
+
+
+1. Add the product to the cart.
+2. Open the minicart.
+3. Input a random coupon inside the minicart.
+4. The error message won't appear.
+5. Input another fake coupon.
+6. The error will appear.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available. However, inputing the code any time after the first try will show the error message properly.
+
+
+
+
+
diff --git a/docs/known-issues/en/minicart-does-not-show-sku-specs-in-b2b-scenario.md b/docs/known-issues/en/minicart-does-not-show-sku-specs-in-b2b-scenario.md
index 69f24c40b..6407d1795 100644
--- a/docs/known-issues/en/minicart-does-not-show-sku-specs-in-b2b-scenario.md
+++ b/docs/known-issues/en/minicart-does-not-show-sku-specs-in-b2b-scenario.md
@@ -3,8 +3,8 @@ title: 'Minicart does not show SKU specs in B2B scenario'
 id: 4eOpxrLEkyHyobCDuWzsMK
 status: PUBLISHED
 createdAt: 2022-10-27T19:11:58.877Z
-updatedAt: 2022-11-25T22:13:10.845Z
-publishedAt: 2022-11-25T22:13:10.845Z
+updatedAt: 2024-02-16T20:28:02.341Z
+publishedAt: 2024-02-16T20:28:02.341Z
 firstPublishedAt: 2022-10-27T19:11:59.318Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: minicart-does-not-show-sku-specs-in-b2b-scenario
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 687308
 ---
 
diff --git a/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index e34a8e294..165dd8ce0 100644
--- a/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -3,8 +3,8 @@ title: 'Misbehaviors for addToCart mutation from checkout-graphql while sending
 id: 1lMWbgmBsOis9gAKcMm8ob
 status: PUBLISHED
 createdAt: 2022-05-03T20:42:18.655Z
-updatedAt: 2022-11-25T22:44:04.555Z
-publishedAt: 2022-11-25T22:44:04.555Z
+updatedAt: 2023-11-16T16:46:29.538Z
+publishedAt: 2023-11-16T16:46:29.538Z
 firstPublishedAt: 2022-05-03T20:42:18.940Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 452053
 ---
 
diff --git a/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md b/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
index 1576e1f63..9e590d7d5 100644
--- a/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
+++ b/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
@@ -29,9 +29,9 @@ Main causes of a badly configured app:
 
 In the case of a non-existent JSON Schema, insert the correct JSON Schema's name in the `model` field.
 
-For example: ![Screen Shot 2019-01-03 at 19.31.53](https://images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
+For example: ![Screen Shot 2019-01-03 at 19.31.53](//images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
 
-Notice how the app's border turns red and the error message on the console indicates "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](https://images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
+Notice how the app's border turns red and the error message on the console indicates "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](//images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md b/docs/known-issues/en/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
index 022f763ba..b5c38e993 100644
--- a/docs/known-issues/en/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
+++ b/docs/known-issues/en/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
@@ -3,8 +3,8 @@ title: 'missing minicart.buyer.id field causes anti-fraud to cancel transactions
 id: 6dvOH9b96qGAHXIzW3wBe1
 status: PUBLISHED
 createdAt: 2023-05-23T17:10:17.329Z
-updatedAt: 2023-05-23T17:10:17.964Z
-publishedAt: 2023-05-23T17:10:17.964Z
+updatedAt: 2024-02-16T20:26:42.045Z
+publishedAt: 2024-02-16T20:26:42.045Z
 firstPublishedAt: 2023-05-23T17:10:17.964Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 514335
 ---
 
diff --git a/docs/known-issues/en/missing-translation-for-the-price-facetfilter-at-intelligent-search.md b/docs/known-issues/en/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
new file mode 100644
index 000000000..17b469d1f
--- /dev/null
+++ b/docs/known-issues/en/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
@@ -0,0 +1,44 @@
+---
+title: 'Missing translation for the price facet/filter at Intelligent Search'
+id: 6c6GnC1dKGViJ2h0ZoY5pm
+status: PUBLISHED
+createdAt: 2024-01-31T21:33:04.796Z
+updatedAt: 2024-01-31T21:33:05.556Z
+publishedAt: 2024-01-31T21:33:05.556Z
+firstPublishedAt: 2024-01-31T21:33:05.556Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: missing-translation-for-the-price-facetfilter-at-intelligent-search
+locale: en
+kiStatus: Backlog
+internalReference: 974840
+---
+
+## Summary
+
+
+The Intelligent Search does not apply the translation to the filter/facet name "price" for additional languages when queried via REST API.
+
+The primary language still returns the expected string as its internal configuration, but any other language will return this with "Price" as a fixed value.
+
+
+##
+
+## Simulation
+
+
+In a store with multiple languages, set the translations for Intelligent Search context via the messages service to the secondary languages and query it using the facets API. Values for "Price" won't be considered, while it works for any other label, like the categories and brand.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md b/docs/known-issues/en/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
index 97e35fc13..39cd04b04 100644
--- a/docs/known-issues/en/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
+++ b/docs/known-issues/en/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
@@ -3,8 +3,8 @@ title: 'Modal as Generic Reason even this type of Modal are configured OK'
 id: 2ftzXjtPZcPypFpsnZMcIK
 status: PUBLISHED
 createdAt: 2022-05-18T18:23:53.248Z
-updatedAt: 2022-11-25T21:59:39.823Z
-publishedAt: 2022-11-25T21:59:39.823Z
+updatedAt: 2024-02-16T20:25:38.358Z
+publishedAt: 2024-02-16T20:25:38.358Z
 firstPublishedAt: 2022-05-18T18:23:53.787Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: modal-as-generic-reason-even-this-type-of-modal-are-configured-ok
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 488339
 ---
 
diff --git a/docs/known-issues/en/modals-deprecated-divergences-setup-shipping-policy.md b/docs/known-issues/en/modals-deprecated-divergences-setup-shipping-policy.md
index b63799705..96fcf73c4 100644
--- a/docs/known-issues/en/modals-deprecated-divergences-setup-shipping-policy.md
+++ b/docs/known-issues/en/modals-deprecated-divergences-setup-shipping-policy.md
@@ -3,8 +3,8 @@ title: 'Modals Deprecated Divergences setup - Shipping Policy'
 id: TYWgIv5xOTUBWdC63FbK5
 status: PUBLISHED
 createdAt: 2022-05-18T18:20:55.870Z
-updatedAt: 2022-11-25T21:59:19.021Z
-publishedAt: 2022-11-25T21:59:19.021Z
+updatedAt: 2024-02-16T20:27:05.367Z
+publishedAt: 2024-02-16T20:27:05.367Z
 firstPublishedAt: 2022-05-18T18:20:56.247Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: modals-deprecated-divergences-setup-shipping-policy
 locale: en
-kiStatus: Scheduled
+kiStatus: No Fix
 internalReference: 445866
 ---
 
diff --git a/docs/known-issues/en/multiple-sku-promotion-api-not-working.md b/docs/known-issues/en/multiple-sku-promotion-api-not-working.md
index 844a27580..bf6f4209f 100644
--- a/docs/known-issues/en/multiple-sku-promotion-api-not-working.md
+++ b/docs/known-issues/en/multiple-sku-promotion-api-not-working.md
@@ -3,8 +3,8 @@ title: 'Multiple Sku Promotion API not working'
 id: 38CLe2oIWHGNgjL4L0uIxz
 status: PUBLISHED
 createdAt: 2023-01-09T21:18:05.077Z
-updatedAt: 2023-01-09T21:18:05.807Z
-publishedAt: 2023-01-09T21:18:05.807Z
+updatedAt: 2024-02-16T20:23:56.065Z
+publishedAt: 2024-02-16T20:23:56.065Z
 firstPublishedAt: 2023-01-09T21:18:05.807Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: multiple-sku-promotion-api-not-working
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 729990
 ---
 
diff --git a/docs/known-issues/en/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md b/docs/known-issues/en/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
new file mode 100644
index 000000000..b0e6d35f5
--- /dev/null
+++ b/docs/known-issues/en/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
@@ -0,0 +1,46 @@
+---
+title: 'My Cards footer is shivering when trying to add a new card'
+id: 5JRsJqm0PmVkdCh7td3DIr
+status: PUBLISHED
+createdAt: 2024-04-05T16:09:59.991Z
+updatedAt: 2024-04-05T16:11:11.933Z
+publishedAt: 2024-04-05T16:11:11.933Z
+firstPublishedAt: 2024-04-05T16:10:01.510Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: my-cards-footer-is-shivering-when-trying-to-add-a-new-card
+locale: en
+kiStatus: Backlog
+internalReference: 1012542
+---
+
+## Summary
+
+
+The footer in 'My Cards' shiver on the screen when attempting to add a new card.
+
+
+##
+
+## Simulation
+
+
+
+1. Go to a random account
+2. Make login
+3. Access My Account> My Cards
+4. Try to save a new fake card and when the process fails, click to save again, and then the screen will shiver until the process finish
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md b/docs/known-issues/en/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
index dc3482638..c6cf10292 100644
--- a/docs/known-issues/en/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
+++ b/docs/known-issues/en/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
@@ -3,8 +3,8 @@ title: 'My Cards UI allow customers to save credit cards without number field fi
 id: 7Ab61xaPRXqxA7VYEnFu8J
 status: PUBLISHED
 createdAt: 2022-02-10T12:34:15.351Z
-updatedAt: 2022-11-25T22:07:26.657Z
-publishedAt: 2022-11-25T22:07:26.657Z
+updatedAt: 2024-02-16T20:26:23.845Z
+publishedAt: 2024-02-16T20:26:23.845Z
 firstPublishedAt: 2022-02-10T12:34:15.869Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 521542
 ---
 
diff --git a/docs/known-issues/en/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md b/docs/known-issues/en/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
index 09588f941..858fcc78e 100644
--- a/docs/known-issues/en/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
+++ b/docs/known-issues/en/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
@@ -3,8 +3,8 @@ title: 'My subscription showing error message when subscription is associated wi
 id: 4p9jzcVzB6E5b6PTm2Ng5E
 status: PUBLISHED
 createdAt: 2022-12-15T19:08:41.210Z
-updatedAt: 2022-12-15T19:08:42.066Z
-publishedAt: 2022-12-15T19:08:42.066Z
+updatedAt: 2024-03-11T19:58:56.132Z
+publishedAt: 2024-03-11T19:58:56.132Z
 firstPublishedAt: 2022-12-15T19:08:42.066Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/en/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md b/docs/known-issues/en/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
index 2799dcf76..7d357b43d 100644
--- a/docs/known-issues/en/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
+++ b/docs/known-issues/en/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
@@ -3,8 +3,8 @@ title: 'My Subscriptions When entering the address Line 2 this appear as null'
 id: 1VbFyW5rQcfUSEJgKphrqb
 status: PUBLISHED
 createdAt: 2022-05-30T13:50:13.717Z
-updatedAt: 2022-11-25T22:02:34.424Z
-publishedAt: 2022-11-25T22:02:34.424Z
+updatedAt: 2024-02-16T20:28:33.052Z
+publishedAt: 2024-02-16T20:28:33.052Z
 firstPublishedAt: 2022-05-30T13:50:14.433Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: my-subscriptions-when-entering-the-address-line-2-this-appear-as-null
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 588046
 ---
 
diff --git a/docs/known-issues/en/mycards-spinner-button-is-not-working-properly.md b/docs/known-issues/en/mycards-spinner-button-is-not-working-properly.md
index 95a116732..c0783f8d6 100644
--- a/docs/known-issues/en/mycards-spinner-button-is-not-working-properly.md
+++ b/docs/known-issues/en/mycards-spinner-button-is-not-working-properly.md
@@ -3,8 +3,8 @@ title: 'MyCards spinner button is not working properly'
 id: 2Y1IHSesmqAKYsep1JzIND
 status: PUBLISHED
 createdAt: 2023-03-29T19:18:47.318Z
-updatedAt: 2023-03-29T19:18:47.732Z
-publishedAt: 2023-03-29T19:18:47.732Z
+updatedAt: 2023-11-06T13:02:14.964Z
+publishedAt: 2023-11-06T13:02:14.964Z
 firstPublishedAt: 2023-03-29T19:18:47.732Z
 contentType: knownIssue
 productTeam: Payments
diff --git a/docs/known-issues/en/mycredits-has-an-error-when-accessing-from-an-dependent-account.md b/docs/known-issues/en/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
index b5f5ea9fa..24b6a596a 100644
--- a/docs/known-issues/en/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
+++ b/docs/known-issues/en/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
@@ -3,8 +3,8 @@ title: 'MyCredits has an error when accessing from an dependent account'
 id: 6QJWAD7Q2PSEMsmZYXqMag
 status: PUBLISHED
 createdAt: 2022-03-27T16:19:47.411Z
-updatedAt: 2022-11-25T22:08:20.276Z
-publishedAt: 2022-11-25T22:08:20.276Z
+updatedAt: 2024-02-16T20:29:22.908Z
+publishedAt: 2024-02-16T20:29:22.908Z
 firstPublishedAt: 2022-03-27T16:19:47.994Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: mycredits-has-an-error-when-accessing-from-an-dependent-account
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 367276
 ---
 
diff --git a/docs/known-issues/en/new-collections-newly-released-filter-is-not-working-for-exports.md b/docs/known-issues/en/new-collections-newly-released-filter-is-not-working-for-exports.md
index 14aa25e9d..4cd006e8e 100644
--- a/docs/known-issues/en/new-collections-newly-released-filter-is-not-working-for-exports.md
+++ b/docs/known-issues/en/new-collections-newly-released-filter-is-not-working-for-exports.md
@@ -55,5 +55,3 @@ However, when combining this functionality with the sheet export, this filter is
 
 Use alternative filters for your export.
 
-rnative filters for your export.
-
diff --git a/docs/known-issues/en/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md b/docs/known-issues/en/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
index 1368136d0..7c064b830 100644
--- a/docs/known-issues/en/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
+++ b/docs/known-issues/en/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
@@ -3,8 +3,8 @@ title: 'New UI does not show the customers ID document for example CPF'
 id: 7y7Npcr6krhsnnEy54vQFa
 status: PUBLISHED
 createdAt: 2022-12-08T22:21:07.966Z
-updatedAt: 2022-12-08T22:21:08.507Z
-publishedAt: 2022-12-08T22:21:08.507Z
+updatedAt: 2024-02-16T20:27:18.190Z
+publishedAt: 2024-02-16T20:27:18.190Z
 firstPublishedAt: 2022-12-08T22:21:08.507Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: new-ui-does-not-show-the-customers-id-document-for-example-cpf
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 713480
 ---
 
diff --git a/docs/known-issues/en/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md b/docs/known-issues/en/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
index 07f5532cd..4f6e7820b 100644
--- a/docs/known-issues/en/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
+++ b/docs/known-issues/en/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
@@ -3,8 +3,8 @@ title: 'New UI does not show the invoiced value on Return items page'
 id: 3DBFXzWoz7jxSdgSLICV8i
 status: PUBLISHED
 createdAt: 2022-09-27T19:34:46.895Z
-updatedAt: 2022-11-25T22:01:19.774Z
-publishedAt: 2022-11-25T22:01:19.774Z
+updatedAt: 2024-02-16T20:28:14.405Z
+publishedAt: 2024-02-16T20:28:14.405Z
 firstPublishedAt: 2022-09-27T19:34:47.384Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: new-ui-does-not-show-the-invoiced-value-on-return-items-page
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 664838
 ---
 
diff --git a/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md b/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
index 10cc1b775..4ac97b1c7 100644
--- a/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
+++ b/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
@@ -20,7 +20,7 @@ internalReference:
 
 The NIF field (document) in the checkout for Portugal (UI) is allowing special characters to be entered as value. However, orders that are closed with special characters get stuck with error in the OMS.
 
-![OMS](https://images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
+![OMS](//images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md b/docs/known-issues/en/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
new file mode 100644
index 000000000..891f20106
--- /dev/null
+++ b/docs/known-issues/en/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
@@ -0,0 +1,71 @@
+---
+title: 'No delivery window can be created due to inconsistence in estimateDate and lastDeliveryDay for high timecost'
+id: 3E5ZPyrjSOPD68vH4SXunM
+status: PUBLISHED
+createdAt: 2024-03-06T19:38:26.954Z
+updatedAt: 2024-03-06T19:38:27.765Z
+publishedAt: 2024-03-06T19:38:27.765Z
+firstPublishedAt: 2024-03-06T19:38:27.765Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost
+locale: en
+kiStatus: Backlog
+internalReference: 995491
+---
+
+## Summary
+
+
+
+The `estimateDate` takes into account the total delivery time but only considering the days that the carrier delivers, so in the case of this example it does not consider weekends.
+But the `lastDeliveryDay` is calculated as calendar days (consecutive days), which is `today date + delivery time + maximum number of days` configured for scheduled delivery, as it count consecutive days, it will consider the weekends.
+
+For the system to assemble the available delivery window, it will compare if:
+
+    lastDeliveryDay > estimateDate : TRUE
+
+
+And only if meets this condition it will create the delivery window.
+
+But with a total transit `timecost` excessive high, there is an inconsistence with the variable `estimateDate` and `lastDeliveryDay`, the condition will return `false`, and therefore no delivery window will be created.
+
+
+
+##
+
+## Simulation
+
+
+
+Change the shipping configuration to the following:
+
+- Processing days and hours of warehouse with 100 days;
+- Timecost in the spreadsheet rate file with 1 day;
+- Remove weekends and holidays for the shipping policy configuration;
+- Schedule delivery for Monday to Friday from 0h to 23:59h;
+- Maximum delivery time in Schedule delivery configuration for 5 days;
+
+For this configuration will lead to `lastDeliveryDay=10/05/2024` and the `estimateDate=14/06/2024`;
+And thus the condition will be false:
+
+    10/05/2024 > 14/06/2024 : FALSE
+
+
+and no delivery window will be created;
+
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md b/docs/known-issues/en/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
new file mode 100644
index 000000000..e5c0fa66c
--- /dev/null
+++ b/docs/known-issues/en/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
@@ -0,0 +1,51 @@
+---
+title: 'Nominal discount based on formula not working as expected with subtraction operations'
+id: 50YsRuiICJNdH2e1QqYnn0
+status: DRAFT
+createdAt: 2023-08-24T13:30:36.935Z
+updatedAt: 2023-08-28T20:44:40.744Z
+publishedAt: 
+firstPublishedAt: 2023-08-24T13:30:37.863Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations
+locale: en
+kiStatus: Backlog
+internalReference: 886980
+---
+
+## Summary
+
+
+When creating a promotion using Nominal discount based on formula, the merchant can use the follow operations according to this documentation: https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV
+ ![](https://vtexhelp.zendesk.com/attachments/token/1EhryrRZDsiXZ31kaSV2VcegW/?name=image.png)
+
+However, when using subtraction operation, the discount value is replaced by the total value of the order.
+
+
+##
+
+## Simulation
+
+
+Create a promotion using the nominal discount based on formula and use a subtraction operation, like this:
+ ![](https://vtexhelp.zendesk.com/attachments/token/3wIEiPGtF9oX2daeQ3F3AZqCk/?name=image.png)
+
+Check on checkout that the discount is replaced by what should be the total value of the order:
+ ![](https://vtexhelp.zendesk.com/attachments/token/r2bWktL4reNcVnnhSqr4hT0FC/?name=image.png)
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md b/docs/known-issues/en/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
index c7a7a8a30..f35ef5b22 100644
--- a/docs/known-issues/en/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
+++ b/docs/known-issues/en/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
@@ -3,8 +3,8 @@ title: 'Nominal discount is not being distributed among all items in the cart'
 id: gt1qMqN71YkaHuZgk9Ibs
 status: PUBLISHED
 createdAt: 2023-01-25T17:33:59.274Z
-updatedAt: 2023-01-25T17:33:59.996Z
-publishedAt: 2023-01-25T17:33:59.996Z
+updatedAt: 2024-07-20T02:22:10.021Z
+publishedAt: 2024-07-20T02:22:10.021Z
 firstPublishedAt: 2023-01-25T17:33:59.996Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -20,11 +20,11 @@ internalReference: 334130
 
 
 
-Nominal discount is not being distributed among all items in the cart.
+The Nominal Discount from promotions is not being distributed among all items in the cart.
 
-This scenario is only happening in a few accounts.
+This scenario is happening only in a few accounts.
 
-The store has a nominal promotion and the discount is only being applied on the one item in the cart, not proportionally distributing the discount to all the items like is supposed to.
+The store has a nominal promotion and the discount is only being applied to one item in the cart, not proportionally distributing the discount to all the items like it is supposed to.
 
 
 ##
@@ -35,10 +35,10 @@ The store has a nominal promotion and the discount is only being applied on the
 
 
 1. Create a regular promotion with a nominal discount;
-2. Create a cartlink where the promotion is applicable;
-3. Check that the discount is being entirely applied on just one item instead of be distributed among all items.
+2. Create a cart link where the promotion is applicable;
+3. Check that the discount is being entirely applied to just one item instead of being distributed among all items.
 
-PS: This doesn't happen everytime and with every account.
+PS: This doesn't happen every time and with every account.
 
 
 ##
@@ -46,5 +46,9 @@ PS: This doesn't happen everytime and with every account.
 ## Workaround
 
 
-No workaround.
+To mitigate this issue, you can use the API Create or Update Coupon API to increase the `maxItemsPerClient` field. This allows the coupon to be applied to as many SKUs as permitted in this field.
+
+
+
+
 
diff --git a/docs/known-issues/en/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md b/docs/known-issues/en/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
new file mode 100644
index 000000000..4024a15c1
--- /dev/null
+++ b/docs/known-issues/en/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
@@ -0,0 +1,63 @@
+---
+title: 'Nominal discount + More for Less + Split for second item --> incorrect discount'
+id: 4hxRWUY6P8aDR9T1KHd3Yf
+status: PUBLISHED
+createdAt: 2024-07-25T16:48:26.511Z
+updatedAt: 2024-07-25T16:48:27.336Z
+publishedAt: 2024-07-25T16:48:27.336Z
+firstPublishedAt: 2024-07-25T16:48:27.336Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: nominal-discount-more-for-less-split-for-second-item-incorrect-discount
+locale: en
+kiStatus: Backlog
+internalReference: 1071119
+---
+
+## Summary
+
+
+When setting up a nominal discount promotion accumulating with more for less promotion, when there's a discount in the more for less only for 1 out of 2 items, leads to an incorrect discount on the 2nd order item due to the checkout split.
+
+For instance, let's say there is a 50% discount only for 1 out of 2 items in a buy and win and then a -$300 off, with both promotions accumulating.
+
+Let's say the item costs $200 and 2 are inserted.
+
+The **expected** discounts would be:
+
+Item (1) ---> -$100 + -$100 --> the 2nd items is only $100 because there is no additional "room" to be reduced from its price.
+Item (2) --> -$200 ---> the rest of the discount to compose the full -$300
+
+However, the scenario that **currently happens** is:
+
+Item (1) ---> -$100 + -$100 --> the 2nd items is only $100 because there is no additional "room" to be reduced from its price.
+Item (2) --> **-$100 ---> the price of the 1st item, from the split is replicated**
+
+This only happens if the discounted items are 2+ units of the same SKU and the "combo" of promotions specified above.
+
+
+##
+
+## Simulation
+
+
+1 - create a percentual promotion
+2 - create a buy and win promotion that gives discount for only the 2nd item
+3 - insert 2 units of said item in the cart
+
+OBS: the combination of prices and discounts must be in a way that the "amount to be discounted" from the price of the 1st item is not enough to compose 50%+ of the nominal discount value
+
+
+##
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/en/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md b/docs/known-issues/en/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
new file mode 100644
index 000000000..1a2c7f297
--- /dev/null
+++ b/docs/known-issues/en/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
@@ -0,0 +1,46 @@
+---
+title: 'Not able to open proper detached SKU on PDP in a new tab'
+id: 26kt6vcKm02TMXDFQPA3ES
+status: PUBLISHED
+createdAt: 2023-07-31T21:20:31.271Z
+updatedAt: 2023-07-31T21:20:31.900Z
+publishedAt: 2023-07-31T21:20:31.900Z
+firstPublishedAt: 2023-07-31T21:20:31.900Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab
+locale: en
+kiStatus: Backlog
+internalReference: 871848
+---
+
+## Summary
+
+
+When using detach feature to split products by some SKU specification and trying to open a new tab from PLP to PDP, it doesn't recognize the property parameter being passed to the URL to select the correct SKU, it just displays the proper SKU when opening in the same tab.
+
+
+##
+
+## Simulation
+
+
+For that, you will need to have a store using detach feature from the intelligent Search modulehttps://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE
+
+- Go to any PLP page
+- For the visual effect, you must select any detached SKU that is not the default SKU from PDP and open it in a new tab
+- You will notice that the SKU that you selected is not the same SKU being displayed
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md b/docs/known-issues/en/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
index 26dc2a234..16c606dde 100644
--- a/docs/known-issues/en/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
+++ b/docs/known-issues/en/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
@@ -3,8 +3,8 @@ title: 'Not possible to upload new media/document in a development workspace whe
 id: zhDX1xoXAifH9tYroXCFn
 status: PUBLISHED
 createdAt: 2023-04-24T20:01:04.211Z
-updatedAt: 2023-05-08T18:00:19.246Z
-publishedAt: 2023-05-08T18:00:19.246Z
+updatedAt: 2024-06-28T16:07:27.058Z
+publishedAt: 2024-06-28T16:07:27.058Z
 firstPublishedAt: 2023-04-24T20:01:04.779Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 795940
 ---
 
diff --git a/docs/known-issues/en/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md b/docs/known-issues/en/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
new file mode 100644
index 000000000..63aecda9f
--- /dev/null
+++ b/docs/known-issues/en/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
@@ -0,0 +1,46 @@
+---
+title: 'Notify-me report generates a corrupted file when there are no SKUs found'
+id: 4UXSRdwdh7TTqGvQ3HrBX4
+status: PUBLISHED
+createdAt: 2023-12-20T20:13:33.873Z
+updatedAt: 2023-12-20T20:13:34.707Z
+publishedAt: 2023-12-20T20:13:34.707Z
+firstPublishedAt: 2023-12-20T20:13:34.707Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found
+locale: en
+kiStatus: Backlog
+internalReference: 956264
+---
+
+## Summary
+
+
+When the 'Notify Me' report has no SKUs, attempting to export it will generate a corrupted file to Excel
+
+
+##
+
+## Simulation
+
+
+
+- Check if the 'Notify Me' report is empty
+- If yes, click on "Export to Excel"
+- Download the file and check if it is possible to open it
+
+
+##
+
+## Workaround
+
+
+Open the file in another software or populate the report to be able to export
+
+
+
+
+
diff --git a/docs/known-issues/en/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md b/docs/known-issues/en/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
index c7c5dad42..6443d844e 100644
--- a/docs/known-issues/en/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
+++ b/docs/known-issues/en/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
@@ -3,8 +3,8 @@ title: 'Number of itens on Pricing filter does not correspond to correct number'
 id: 1FyjpY1K6JfAQ0gRIuXyuO
 status: PUBLISHED
 createdAt: 2022-03-16T19:37:02.943Z
-updatedAt: 2022-11-25T22:12:33.361Z
-publishedAt: 2022-11-25T22:12:33.361Z
+updatedAt: 2024-02-16T20:24:00.118Z
+publishedAt: 2024-02-16T20:24:00.118Z
 firstPublishedAt: 2022-03-16T19:37:03.370Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 371405
 ---
 
diff --git a/docs/known-issues/en/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md b/docs/known-issues/en/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
new file mode 100644
index 000000000..e3beb1bbf
--- /dev/null
+++ b/docs/known-issues/en/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
@@ -0,0 +1,49 @@
+---
+title: 'Omnishipping component will not fill the PickupReceiver field when the client first informs an address for delivery'
+id: 0vYgYP5NTflaVEBiAchhL
+status: DRAFT
+createdAt: 2023-12-01T14:11:00.160Z
+updatedAt: 2023-12-04T13:28:38.612Z
+publishedAt: 
+firstPublishedAt: 2023-12-01T14:11:00.848Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery
+locale: en
+kiStatus: Backlog
+internalReference: 945896
+---
+
+## Summary
+
+
+
+When using the **Omnishipping** component on checkout, the **PickupReceiver** field will show blank when it should have the name the client input in the Identification step. This only happens if the client first informs an address for delivery and then clicks on the Pickup tab to select a pick-up point.
+
+
+##
+
+## Simulation
+
+
+
+1. Install the Omnishipping component in a store without any customizations on checkout
+2. Start a checkout process and fill the identification information
+3. Select an address for delivery but then click in the Pickup Option
+4. The PickupReceiver field will show blank
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md b/docs/known-issues/en/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
new file mode 100644
index 000000000..80de90f34
--- /dev/null
+++ b/docs/known-issues/en/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
@@ -0,0 +1,43 @@
+---
+title: 'On My Account the address edition with Red Information of Required Field appears even after filled until save data'
+id: 1QWktgA1c4iyONb8sFCaIh
+status: PUBLISHED
+createdAt: 2023-07-28T20:52:37.170Z
+updatedAt: 2023-07-28T20:52:38.569Z
+publishedAt: 2023-07-28T20:52:38.569Z
+firstPublishedAt: 2023-07-28T20:52:38.569Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data
+locale: en
+kiStatus: Backlog
+internalReference: 870891
+---
+
+## Summary
+
+
+On My Address edition page of My account, even the address is filled the red info of "Obrigatory Field" appears until the data is saved.
+
+
+##
+
+## Simulation
+
+
+Goes to my address page choose the edition option and after fill the address the info message still appears until save the data.
+
+
+##
+
+## Workaround
+
+
+There is no workaround.
+
+
+
+
+
diff --git a/docs/known-issues/en/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md b/docs/known-issues/en/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
index a98784e92..73357bdce 100644
--- a/docs/known-issues/en/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
+++ b/docs/known-issues/en/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
@@ -3,8 +3,8 @@ title: 'On the Order Placed page, the DataLayer only captures the information of
 id: 5cTy3dCZ6x7FNMKvBbc9s8
 status: PUBLISHED
 createdAt: 2023-01-04T21:06:17.111Z
-updatedAt: 2023-01-10T19:08:17.450Z
-publishedAt: 2023-01-10T19:08:17.450Z
+updatedAt: 2024-02-16T20:23:30.519Z
+publishedAt: 2024-02-16T20:23:30.519Z
 firstPublishedAt: 2023-01-04T21:14:00.744Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: authors_84
 tag: Order Management
 slug: on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the
 locale: en
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 727339
 ---
 
diff --git a/docs/known-issues/en/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md b/docs/known-issues/en/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
new file mode 100644
index 000000000..60b370c2c
--- /dev/null
+++ b/docs/known-issues/en/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
@@ -0,0 +1,53 @@
+---
+title: 'O=OrderByPriceASC (or OrderByPriceDESC) could bring the wrong order'
+id: 2XCplZQutilKeD2bNnjYDx
+status: PUBLISHED
+createdAt: 2022-05-20T15:48:15.215Z
+updatedAt: 2024-06-21T11:29:11.233Z
+publishedAt: 2024-06-21T11:29:11.233Z
+firstPublishedAt: 2022-05-20T15:48:16.089Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order
+locale: en
+kiStatus: Backlog
+internalReference: 582861
+---
+
+## Summary
+
+
+**O=OrderByPriceASC** (or **OrderByPriceDESC**) can use the wrong policy to order prices. Also, since the indexed price only has one decimal place, the second decimal place of the price will not be considered.
+
+Additionally, the prices of non-comprehensive sellers are not considered in the sorting. As a result, regionalized stores on the Portal are unable to use the **orderByPrice** parameter.
+
+
+##
+
+## Simulation
+
+
+
+- Enter more than one price on the product. Ex: two different list prices on different sellers
+- Put page sorting by price (ex: O=OrderByPriceASC)
+- See that the sorting is not in the order of the prices being displayed
+or
+
+- Search for two products with decimal prices. Ex: price 1 = 14.04 and price 2 = 14.01
+- Put page sorting by price (ex: O=OrderByPriceASC)
+- See that the sorting is not in the order of the prices being displayed
+
+
+##
+
+## Workaround
+
+
+None on the Portal. However, the account can switch to Inteligente Search.
+
+
+
+
+
diff --git a/docs/known-issues/en/openclose-modal-hook-affects-all-modals-on-the-page.md b/docs/known-issues/en/openclose-modal-hook-affects-all-modals-on-the-page.md
new file mode 100644
index 000000000..f4b329f98
--- /dev/null
+++ b/docs/known-issues/en/openclose-modal-hook-affects-all-modals-on-the-page.md
@@ -0,0 +1,46 @@
+---
+title: 'Open/close modal hook affects all modals on the page'
+id: l1G3HN5Y3LxYVzuMnhjkL
+status: PUBLISHED
+createdAt: 2024-05-31T19:16:13.601Z
+updatedAt: 2024-06-04T12:14:19.271Z
+publishedAt: 2024-06-04T12:14:19.271Z
+firstPublishedAt: 2024-05-31T19:16:14.596Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: openclose-modal-hook-affects-all-modals-on-the-page
+locale: en
+kiStatus: Backlog
+internalReference: 1042165
+---
+
+## Summary
+
+
+On opening/closing a modal the action affects all the modals of the page
+
+
+##
+
+## Simulation
+
+
+Try opening a modal on a page with more than one
+Look for the other modals, you'll see the behavior will be the same
+
+
+##
+
+## Workaround
+
+
+You can use a customized state instead of the native one. Here is an example:
+
+     import { useState } from "react";import { Modal, ModalHeader, ModalBody, LinkButton, Icon } from "@faststore/ui";import ModalContent from "./ModalContent";import section from "./styles.module.scss";const ModalSelector = () => {const [showModal, setShowModal] = useState(false);const ToggleModal = () => {setShowModal((showModal) => !showModal);};return (} > Delivery {showModal && ( <> )});};export default ModalSelector;
+
+
+
+
+
diff --git a/docs/known-issues/en/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md b/docs/known-issues/en/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
new file mode 100644
index 000000000..16201307a
--- /dev/null
+++ b/docs/known-issues/en/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
@@ -0,0 +1,47 @@
+---
+title: 'Operations cannot be performed correctly due to null documentType field.'
+id: 5cZWkKc0ZXnMZCw4bvXJjA
+status: PUBLISHED
+createdAt: 2023-05-11T17:33:04.077Z
+updatedAt: 2023-12-06T15:21:16.013Z
+publishedAt: 2023-12-06T15:21:16.013Z
+firstPublishedAt: 2023-05-11T17:33:04.511Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: operations-cannot-be-performed-correctly-due-to-null-documenttype-field
+locale: en
+kiStatus: Backlog
+internalReference: 697107
+---
+
+## Summary
+
+
+Some providers necessarily need `documentType` to be different from `null`, that is, to be correctly filled in to carry out some payment operations.
+
+So far we have two known scenarios:
+
+1. The absence of this field does not allow the payment to be correctly analyzed by anti-fraud, which causes the transaction to be at risk.
+2. The absence of the field prevents the payment from being authorized and consequently leads to the transaction being canceled.
+
+
+##
+
+## Simulation
+
+
+This issue occurs when a client uses information from a company to complete an order.
+If the company name is used to complete the transaction, the `documentType` field is left unfilled, causing problems with the approval for the payment.
+
+
+##
+
+## Workaround
+
+
+
+For the first scenario, it is possible to use an internal API to skip the anti-fraud analysis step.
+Despite being strongly discouraged, it is a possible operation.
+
diff --git a/docs/known-issues/en/order-again-from-b2b-orders-history-doesnt-work.md b/docs/known-issues/en/order-again-from-b2b-orders-history-doesnt-work.md
index ef2e2854b..6d38fd19d 100644
--- a/docs/known-issues/en/order-again-from-b2b-orders-history-doesnt-work.md
+++ b/docs/known-issues/en/order-again-from-b2b-orders-history-doesnt-work.md
@@ -3,8 +3,8 @@ title: "Order Again from B2B Orders History doesn't work"
 id: 2kT6UJsivYRgEaYpeRpEWa
 status: PUBLISHED
 createdAt: 2023-05-05T13:16:44.403Z
-updatedAt: 2023-05-08T18:34:38.873Z
-publishedAt: 2023-05-08T18:34:38.873Z
+updatedAt: 2023-09-19T21:46:58.308Z
+publishedAt: 2023-09-19T21:46:58.308Z
 firstPublishedAt: 2023-05-05T13:16:45.530Z
 contentType: knownIssue
 productTeam: B2B
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: B2B
 slug: order-again-from-b2b-orders-history-doesnt-work
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 819920
 ---
 
diff --git a/docs/known-issues/en/order-authorization-lessthan-100-goes-with-the-flow.md b/docs/known-issues/en/order-authorization-lessthan-100-goes-with-the-flow.md
new file mode 100644
index 000000000..7a1adfed9
--- /dev/null
+++ b/docs/known-issues/en/order-authorization-lessthan-100-goes-with-the-flow.md
@@ -0,0 +1,50 @@
+---
+title: 'Order Authorization lessThan 100 goes with the flow'
+id: 51vxznnbek6mtVtQgKEW9d
+status: PUBLISHED
+createdAt: 2024-02-16T13:44:05.199Z
+updatedAt: 2024-02-16T13:44:05.932Z
+publishedAt: 2024-02-16T13:44:05.932Z
+firstPublishedAt: 2024-02-16T13:44:05.932Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: order-authorization-lessthan-100-goes-with-the-flow
+locale: en
+kiStatus: Backlog
+internalReference: 983031
+---
+
+## Summary
+
+
+We identified that when the order Authorization (OrderAuth) system is configured with the value "lessThan: 100", in the "Rules-list.CreateDoEffect" , it cannot understand that it is less than or equal to 100%, only that it is less than 100% and When the order has a 100% discount, the system authorizes the order to follow the normal flow.
+
+
+##
+
+## Simulation
+
+
+To simulate it is necessary to configure orderAuth:
+Access: https://.myvtex.com/admin/order-auth
+Configure price divergence > insert the following values into the rule:
+Rules-list.denyEffect :0 to 60%
+
+Rules-list.CreateDoEffect: 61 to 100%
+
+When configuring the "Rules-list.CreateDoEffect" rule to 100%, it cannot understand that it is less than or equal, only that it is less and therefore authorizes the request to follow the normal flow when it is equal to 100%.
+
+
+##
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/en/order-card-info-causing-confusing-on-status.md b/docs/known-issues/en/order-card-info-causing-confusing-on-status.md
index b7e0eff78..eac6620ae 100644
--- a/docs/known-issues/en/order-card-info-causing-confusing-on-status.md
+++ b/docs/known-issues/en/order-card-info-causing-confusing-on-status.md
@@ -3,8 +3,8 @@ title: 'Order card info causing confusing on Status'
 id: 2f0nEqccswuyWEcwdqiRZS
 status: PUBLISHED
 createdAt: 2022-08-18T19:04:12.824Z
-updatedAt: 2022-11-25T22:01:43.687Z
-publishedAt: 2022-11-25T22:01:43.687Z
+updatedAt: 2024-02-16T20:24:07.700Z
+publishedAt: 2024-02-16T20:24:07.700Z
 firstPublishedAt: 2022-08-18T19:04:13.465Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: order-card-info-causing-confusing-on-status
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 619778
 ---
 
diff --git a/docs/known-issues/en/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md b/docs/known-issues/en/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
index 91b487493..18599b4e4 100644
--- a/docs/known-issues/en/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
+++ b/docs/known-issues/en/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
@@ -3,8 +3,8 @@ title: 'Order creation failed due to price divergence on fulfillment layer'
 id: 31fiMPNRULuOH73AhlzU5K
 status: PUBLISHED
 createdAt: 2022-02-03T15:24:07.791Z
-updatedAt: 2022-11-25T21:52:40.751Z
-publishedAt: 2022-11-25T21:52:40.751Z
+updatedAt: 2024-02-16T20:26:40.128Z
+publishedAt: 2024-02-16T20:26:40.128Z
 firstPublishedAt: 2022-02-03T15:24:08.353Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: order-creation-failed-due-to-price-divergence-on-fulfillment-layer
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 512393
 ---
 
diff --git a/docs/known-issues/en/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md b/docs/known-issues/en/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
index b1b6a3bd5..546258dc5 100644
--- a/docs/known-issues/en/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
+++ b/docs/known-issues/en/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
@@ -3,8 +3,8 @@ title: 'Order Export Report is not working properly due double space on Promotio
 id: 3dVPZEs544WyPDBNzTesWx
 status: PUBLISHED
 createdAt: 2023-04-06T20:22:47.489Z
-updatedAt: 2023-04-06T20:22:48.141Z
-publishedAt: 2023-04-06T20:22:48.141Z
+updatedAt: 2024-06-28T17:44:15.662Z
+publishedAt: 2024-06-28T17:44:15.662Z
 firstPublishedAt: 2023-04-06T20:22:48.141Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,15 +12,14 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: order-export-report-is-not-working-properly-due-double-space-on-promotion-name
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 786216
 ---
 
 ## Summary
 
 
-For orders promotion, is not correct use doble space or special character on names, this can breake the filter or missing some order on order export report.
-Name on "ratesAndBenefitsData" array.
+The orders report system currently cannot build a file from promotion filters that contain double spaces in their names, when trying to build the report the system generates an error and the export is not performed, resulting in the message "_Export completed. 0 orders were sent to your email"_.
 
 
 ##
@@ -28,9 +27,12 @@ Name on "ratesAndBenefitsData" array.
 ## Simulation
 
 
-Create order using some promotion with incorrect name, for example with doble space on name.
-After that goes to order management all orders and execute a filter with this promotion as condition.
-That moment you can see the order on order list filtered, but choosing the export report that export will not get the order with promotion with double space.
+
+Create order using some promotion whose name contains double spaces;
+
+After that, go into order management and run a filter with this promotion as condition.
+
+At this point, the OMS UI will normally display a list of orders with the chosen condition, but when selecting export orders the UI will return the following message "_Export completed. 0 orders have been sent to your email_".
 
 
 ##
@@ -38,8 +40,7 @@ That moment you can see the order on order list filtered, but choosing the expor
 ## Workaround
 
 
-There is no workaround available.
-
+Filter the orders in the UI by another parameter e.g. date, payment method etc., then export the orders and filter them by promotion directly in the Excel file generated by the system.
 
 
 
diff --git a/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
new file mode 100644
index 000000000..404f7d44b
--- /dev/null
+++ b/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -0,0 +1,55 @@
+---
+title: "Order Filter doesn't work properly due to double quotes (") in the Promotion name or SKU name"
+id: 4Qm0akQTQXR8sSbkTDiBL7
+status: PUBLISHED
+createdAt: 2024-06-06T15:42:19.747Z
+updatedAt: 2024-06-06T15:42:20.627Z
+publishedAt: 2024-06-06T15:42:20.627Z
+firstPublishedAt: 2024-06-06T15:42:20.627Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name
+locale: en
+kiStatus: Backlog
+internalReference: 1045623
+---
+
+## Summary
+
+
+The orders filter system currently doesn't return the order with promotions that contain double quotes `"` in their names, this also applies to SKU name.
+
+
+##
+
+## Simulation
+
+
+To reproduce this scenario, follow the steps below.
+
+1. Create a promotion/sku with double quotes `"` in the name;
+Example: Promotion name as `10% off usando o cupom "DIAGEO" (8)`
+2. Create a test order:
+
+  1. In the store environment (storefront), select an item and add it to the cart;
+  2. Make sure promotion is applied;
+  3. Go to the checkout and place the order.
+3. Go to **Orders > Order management**;
+4. Click on `All orders`;
+5. Use the **filter** to select the promotion you've added;
+6. Note that no orders are found with the selected filter, and returned message in the UI is: `Nenhum pedido encontrado. Limpe seus filtros e tente uma pesquisa diferente.`
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/order-not-notified-carrier-leaves-label-barcode-incomplete.md b/docs/known-issues/en/order-not-notified-carrier-leaves-label-barcode-incomplete.md
new file mode 100644
index 000000000..99a2df828
--- /dev/null
+++ b/docs/known-issues/en/order-not-notified-carrier-leaves-label-barcode-incomplete.md
@@ -0,0 +1,43 @@
+---
+title: 'Order not notified carrier leaves label barcode incomplete'
+id: 2QjxFv2Ul2wKCdnYtrlF0T
+status: PUBLISHED
+createdAt: 2023-08-01T16:55:39.774Z
+updatedAt: 2023-09-18T22:52:54.573Z
+publishedAt: 2023-09-18T22:52:54.573Z
+firstPublishedAt: 2023-08-01T16:55:40.545Z
+contentType: knownIssue
+productTeam: VTEX Shipping Network (VTEX Log)
+author: 2mXZkbi0oi061KicTExNjo
+tag: VTEX Shipping Network (VTEX Log)
+slug: order-not-notified-carrier-leaves-label-barcode-incomplete
+locale: en
+kiStatus: Backlog
+internalReference: 872530
+---
+
+## Summary
+
+
+Customers who use Shipping Network partner carriers, when requesting the label issue in Ready to Ship, may get the file with the incomplete barcode, which may prevent the package from being posted.
+
+
+##
+
+## Simulation
+
+
+It was not possible to reproduce, only to verify by checking the labels sent by customers with the incomplete barcode and confirming via API that the package was not notified.
+
+
+##
+
+## Workaround
+
+
+Notifying the order manually again, makes sure that the carrier is notified and the barcode is complete and the label can be used.
+
+
+
+
+
diff --git a/docs/known-issues/en/order-partial-return-triggered-the-transaction-total-refund.md b/docs/known-issues/en/order-partial-return-triggered-the-transaction-total-refund.md
index c46e9cad9..4beebe4c2 100644
--- a/docs/known-issues/en/order-partial-return-triggered-the-transaction-total-refund.md
+++ b/docs/known-issues/en/order-partial-return-triggered-the-transaction-total-refund.md
@@ -1,10 +1,10 @@
 ---
 title: 'Order partial return triggered the transaction total refund'
 id: 5cPpyvV4t6swxDPrEmuzrn
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-04-04T21:20:39.334Z
-updatedAt: 2022-11-25T22:03:29.435Z
-publishedAt: 2022-11-25T22:03:29.435Z
+updatedAt: 2024-05-28T19:09:23.158Z
+publishedAt: 
 firstPublishedAt: 2022-04-04T21:20:40.180Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/en/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md b/docs/known-issues/en/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
new file mode 100644
index 000000000..9899ee764
--- /dev/null
+++ b/docs/known-issues/en/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
@@ -0,0 +1,45 @@
+---
+title: "Order replacement feature doesn't work when the replaced cart and original order have the same value"
+id: 7eHiC34Pgsr1XcfIVHl7Sc
+status: PUBLISHED
+createdAt: 2023-07-21T14:49:31.057Z
+updatedAt: 2023-12-18T20:17:32.757Z
+publishedAt: 2023-12-18T20:17:32.757Z
+firstPublishedAt: 2023-07-21T14:49:31.682Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value
+locale: en
+kiStatus: Fixed
+internalReference: 866622
+---
+
+## Summary
+
+
+The Order replacement feature doesn't work when the replaced cart has the same value as the original order, and the payment system is "Reuse Payment".
+
+
+##
+
+## Simulation
+
+
+
+- Activate the Order replacement feature;
+- Complete an order and change something, for example, from size small to large;
+- Make sure the replaced cart has the same value as the original order;
+- In the payment step, select "Reuse Payment".
+
+
+##
+
+## Workaround
+
+
+Select a payment method different from "Reuse Payment". The previous transaction will be canceled and refunded; a new one will be created.
+
+
+
diff --git a/docs/known-issues/en/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md b/docs/known-issues/en/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
new file mode 100644
index 000000000..0e6affa1b
--- /dev/null
+++ b/docs/known-issues/en/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
@@ -0,0 +1,51 @@
+---
+title: 'Order report inconsistency when tid field is duplicated in the connectorResponses field from GET payment details API.'
+id: 4xXSp2RMyHMeHpEUXgmpAZ
+status: PUBLISHED
+createdAt: 2023-09-06T21:18:05.941Z
+updatedAt: 2023-09-06T21:18:06.733Z
+publishedAt: 2023-09-06T21:18:06.733Z
+firstPublishedAt: 2023-09-06T21:18:06.733Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api
+locale: en
+kiStatus: Backlog
+internalReference: 895664
+---
+
+## Summary
+
+
+Connectors from that list need to save more fields for the connector that works with “Venda direta” - Sales app. Specifically, for the connectors listed below, and only for them, all content from the payload should be directed to the "`connectorResponses`" field. This results in a duplication of the "`tid`" field, which already exists in the "`connectorResponses`." While this duplication does not pose a problem in terms of the transaction life cycle, it does create an inconsistency when generating reports from the order page.
+
+
+- PagarMeV3
+- PagarMeV3Stg
+- Adyen V3
+
+
+##
+
+## Simulation
+
+
+
+1. Access the admin order page.
+2. Generate the order report.
+3. Look for the `tId` column where the orders were placed using one of these connectors
+
+
+##
+
+## Workaround
+
+
+Use the /payment route or the GET order API to retrieve this data
+
+
+
+
+
diff --git a/docs/known-issues/en/order-stuck-at-seller-status-cancellationrequestdeniedffm.md b/docs/known-issues/en/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
new file mode 100644
index 000000000..2a5ff92b6
--- /dev/null
+++ b/docs/known-issues/en/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
@@ -0,0 +1,54 @@
+---
+title: 'Order stuck at seller status cancellation-request-denied-ffm'
+id: 5hBeTQMKmo5C63QRAOSvT2
+status: PUBLISHED
+createdAt: 2024-03-22T17:50:37.946Z
+updatedAt: 2024-03-22T17:50:38.822Z
+publishedAt: 2024-03-22T17:50:38.822Z
+firstPublishedAt: 2024-03-22T17:50:38.822Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: order-stuck-at-seller-status-cancellationrequestdeniedffm
+locale: en
+kiStatus: Backlog
+internalReference: 1004978
+---
+
+## Summary
+
+
+We identified that some sellers, in the VTEX seller and marketplace structure, when requesting cancellation, then refuse this cancellation via the UI, or call the API "cancellation-request-denied-ffm", this is as if they were denying the request itself of cancellation, for some reason, the request to deny the cancellation overlaps with the request to cancel.
+As a result, the order is stuck at the seller, in the "cancellation-request-denied-ffm" status.
+And in some cases, the marketplace itself tries to request cancellation, as a result, the marketplace is also stuck in the "request cancellation" status.
+On the other hand, we have the case where the marketplace does not receive this cancellation notification and continues with your order until the Invoiced status!
+In all cases, we are unable to change the status of these orders.
+
+
+##
+
+## Simulation
+
+
+1- Create an order, with seller whiteLabel;
+2- In the seller's order, advance the status to "handling";
+3- Still at the seller, request the cancellation of the order;
+4- On the seller's request, we will have the message, "accept or refuse cancellation", click on the refuse option on the seller or use the API, you will see that the seller's request will go to the status "cancellation-request-denied-ffm".
+5- In the Marketplace order, click cancel;
+6- The Marketplace request will be stuck at "Request-Cancel";
+
+It may happen that the Marketplace order continues with the order and goes to invoice, when it sends the invoice.
+
+
+##
+
+## Workaround
+
+
+This is not a workaround, but guidance to accounts, once the seller requests cancellation, do not refuse the request itself.
+
+
+
+
+
diff --git a/docs/known-issues/en/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md b/docs/known-issues/en/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
new file mode 100644
index 000000000..d4e6063d2
--- /dev/null
+++ b/docs/known-issues/en/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
@@ -0,0 +1,48 @@
+---
+title: 'Order stuck in Payment Pending status due to missing payment approved notification'
+id: 1yM3alrrYhrpdZhBPLslZC
+status: PUBLISHED
+createdAt: 2024-05-24T15:04:47.795Z
+updatedAt: 2024-05-24T15:04:48.820Z
+publishedAt: 2024-05-24T15:04:48.820Z
+firstPublishedAt: 2024-05-24T15:04:48.820Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification
+locale: en
+kiStatus: Backlog
+internalReference: 1031035
+---
+
+## Summary
+
+
+
+In the "Payment Pending" status, a payment notification is expected to be sent to the Orders module. During this period, some problems with event processing may occur.
+The message queue provides an asynchronous communication protocol, in which events are placed in a queue to be consumed at a predetermined time in the future.
+This KI refers explicitly to the scenarios with PPP connectors and is not intended to exhaust all possibilities of event processing problems that may occur.
+
+
+##
+
+## Simulation
+
+
+
+There's no way to simulate this behavior.
+
+
+##
+
+## Workaround
+
+
+
+Please contact our support team to manually reprocess the event.
+
+
+
+
+
diff --git a/docs/known-issues/en/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md b/docs/known-issues/en/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
new file mode 100644
index 000000000..fc7efe061
--- /dev/null
+++ b/docs/known-issues/en/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
@@ -0,0 +1,49 @@
+---
+title: 'Order with interest has problems when trying to return all the items and refund the total payment'
+id: 2J5XD9jjQfZWMVg0yYMzUa
+status: PUBLISHED
+createdAt: 2023-09-18T20:53:08.156Z
+updatedAt: 2023-09-18T20:53:08.813Z
+publishedAt: 2023-09-18T20:53:08.813Z
+firstPublishedAt: 2023-09-18T20:53:08.813Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment
+locale: en
+kiStatus: Backlog
+internalReference: 376077
+---
+
+## Summary
+
+
+The platform prevents the chargeback of amounts greater than the total amount of the order. This becomes an issue for the chargeback of orders in which the payment method involves interest.
+In addition to the **total amount**, orders have an **invoiced amount**, which, for legal reasons, may not include the interest applied based on a payment method.
+Consequently, the platform returns an error with status 400 when an attempt is made to issue a chargeback invoice with an amount greater than the one previously invoiced.
+
+###
+
+###
+
+## Simulation
+
+
+
+1. In your store, create an order with interest applied to the payment;
+2. Try performing a chargeback on the total amount paid via API with the invoice submission request;
+3. Notice that the API returns an error with status 400, indicating that it is not possible to issue an invoice of type INPUT with an amount greater than the total amount of the order.
+
+###
+
+###
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md b/docs/known-issues/en/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
index 157d2a338..dcd85958c 100644
--- a/docs/known-issues/en/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
+++ b/docs/known-issues/en/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
@@ -3,8 +3,8 @@ title: 'Order with no subscription Created and no email of New Orders on Cases r
 id: 747TGL3sy1mmM1LnVkEjuO
 status: PUBLISHED
 createdAt: 2022-02-21T20:54:35.174Z
-updatedAt: 2022-11-25T22:03:15.831Z
-publishedAt: 2022-11-25T22:03:15.831Z
+updatedAt: 2024-02-16T20:23:42.061Z
+publishedAt: 2024-02-16T20:23:42.061Z
 firstPublishedAt: 2022-05-18T18:43:19.767Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 529143
 ---
 
diff --git a/docs/known-issues/en/order-with-status-of-canceled-but-the-payment-remains-authorized.md b/docs/known-issues/en/order-with-status-of-canceled-but-the-payment-remains-authorized.md
index 02f6a7500..bd4fef20c 100644
--- a/docs/known-issues/en/order-with-status-of-canceled-but-the-payment-remains-authorized.md
+++ b/docs/known-issues/en/order-with-status-of-canceled-but-the-payment-remains-authorized.md
@@ -3,16 +3,16 @@ title: 'Order with status of canceled but the payment remains authorized'
 id: 19WmIjIbAQmJ19AOC4q56N
 status: PUBLISHED
 createdAt: 2022-05-11T12:49:23.081Z
-updatedAt: 2022-11-25T21:51:23.997Z
-publishedAt: 2022-11-25T21:51:23.997Z
+updatedAt: 2024-06-28T17:45:57.362Z
+publishedAt: 2024-06-28T17:45:57.362Z
 firstPublishedAt: 2022-05-11T12:49:23.599Z
 contentType: knownIssue
-productTeam: Checkout
+productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
-tag: Checkout
+tag: Order Management
 slug: order-with-status-of-canceled-but-the-payment-remains-authorized
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 420019
 ---
 
@@ -22,6 +22,7 @@ internalReference: 420019
 In some cases where the order is incomplete or canceled when there is any communication failure with the Gateway, the payment remains authorized and/or approved, not entering the cancellation flow and the amount paid is not automatically refunded. Also, transactional emails can be accidentally sent, which also allows payment of bank slips, as the URL will go with it.
 
 
+##
 
 ## Simulation
 
@@ -29,6 +30,7 @@ In some cases where the order is incomplete or canceled when there is any commun
 There's no way to simulate. But we have some cases that this happened before.
 
 
+##
 
 ## Workaround
 
diff --git a/docs/known-issues/en/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md b/docs/known-issues/en/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
index d845513eb..4780b78c4 100644
--- a/docs/known-issues/en/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
+++ b/docs/known-issues/en/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
@@ -3,8 +3,8 @@ title: 'OrderForm API preventing the shipping method selection for the same item
 id: 4dEfq7lNqTLF7SFIOaRsc2
 status: PUBLISHED
 createdAt: 2023-01-27T21:56:04.190Z
-updatedAt: 2023-01-27T22:03:21.165Z
-publishedAt: 2023-01-27T22:03:21.165Z
+updatedAt: 2023-07-05T14:33:51.370Z
+publishedAt: 2023-07-05T14:33:51.370Z
 firstPublishedAt: 2023-01-27T21:56:04.914Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 742139
 ---
 
diff --git a/docs/known-issues/en/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md b/docs/known-issues/en/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
index b73c77189..4da165619 100644
--- a/docs/known-issues/en/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
+++ b/docs/known-issues/en/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
@@ -3,13 +3,13 @@ title: "orderForm (Chk API) suggesting invalid scheduled delivery that can't be
 id: 7e2bSJSJa938QCrOHkRibZ
 status: PUBLISHED
 createdAt: 2022-01-24T20:20:11.732Z
-updatedAt: 2023-03-21T19:26:09.280Z
-publishedAt: 2023-03-21T19:26:09.280Z
+updatedAt: 2023-12-01T14:08:09.892Z
+publishedAt: 2023-12-01T14:08:09.892Z
 firstPublishedAt: 2023-03-21T19:26:09.280Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
-tag: 
+tag: Checkout
 slug: orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used
 locale: en
 kiStatus: Backlog
@@ -18,27 +18,34 @@ internalReference: 298665
 
 ## Summary
 
-When a cart/orderForm has multiple items with scheduled delivery, the scheduled options that have the same ID (so, considered the same shipping method) needs to have the same delivery windows between it. If there's no intersection, the shipping method will be discarded for some items.
 
-The issue is that, in some flows, like the "GET orderForm" API, this filtering behavior isn't being applied, offering an invalid scheduled delivery (without intersection). In other flows, like in the "orderForm simulation" or while in fact selecting the shipping method, the offered option will be correctly filtered/removed.
+When a cart/orderForm has multiple items with scheduled delivery from the same seller, the scheduled options with the same ID (considered the same shipping method) need to have the same delivery windows between them. If there's no intersection, the shipping method will be discarded for some items.
 
-Side-effect: the Chk UI will try to use/simulate the invalid option and can stay locked in a **requests loop**, because the shipping method is available in the first moment, but can't be used in a second moment, and the UI application try again the first step while reviewing the options available in the orderForm.
+The issue is that, in some flows, like the "GET orderForm" API, this filtering behavior isn't being applied, offering an invalid scheduled delivery (without intersection). In other flows, like in the "orderForm simulation" or while selecting the shipping method, the offered option will be correctly filtered/removed.
 
+Side-effect: the Chk UI will try to use/simulate the invalid option and can stay locked in a **requests loop** because the shipping method is available in the first moment but can't be used in a second moment, and the UI tries the first step again while reviewing the options available in the orderForm.
+
+
+##
 
 ## Simulation
 
 
-- to have two different shipping policies (carriers) with the same "freight type" (that defines the "slaId")
-- both of them scheduled, but with a different delivery window between them
-- to have one item for each shipping policy
-- include both items in the cart and simulate the shipping
 
-At this moment, the UI can stay locked in a loop due to the divergence between the "GET orderForm" and the "orderForm simulation".
+- From the same seller, configure two different shipping policies (carriers) with the same "freight type" (that defines the "slaId");
+- Both of them are scheduled delivery, but with a different delivery window between them;
+- Add 2 items to the cart, one item from each shipping policy.
+
+The UI can stay locked in a loop due to the divergence between the "GET orderForm" and the "orderForm simulation".
 
 
+##
 
 ## Workaround
 
 
-It's required to fix the delivery window between the shipping methods that have the same ID (to have the same delivery windows), or treat them as different shipping methods, so using different IDs.
+It's required to fix the delivery window between the shipping methods with the same ID (to have the same delivery windows), or treat them as different shipping methods, so using different IDs.
+
+
+
 
diff --git a/docs/known-issues/en/orderform-not-returning-customers-data-even-for-authorized-credentials.md b/docs/known-issues/en/orderform-not-returning-customers-data-even-for-authorized-credentials.md
index 987b53972..37ae62909 100644
--- a/docs/known-issues/en/orderform-not-returning-customers-data-even-for-authorized-credentials.md
+++ b/docs/known-issues/en/orderform-not-returning-customers-data-even-for-authorized-credentials.md
@@ -3,8 +3,8 @@ title: "OrderForm not returning customer's data even for authorized credentials"
 id: JcjDusU8YP0kerWXC6LXK
 status: PUBLISHED
 createdAt: 2022-05-19T16:25:28.039Z
-updatedAt: 2023-02-01T21:29:33.875Z
-publishedAt: 2023-02-01T21:29:33.875Z
+updatedAt: 2023-09-27T20:39:27.746Z
+publishedAt: 2023-09-27T20:39:27.746Z
 firstPublishedAt: 2022-05-19T16:25:28.427Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: orderform-not-returning-customers-data-even-for-authorized-credentials
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 582070
 ---
 
diff --git a/docs/known-issues/en/orderform-not-updating-after-order-is-placed.md b/docs/known-issues/en/orderform-not-updating-after-order-is-placed.md
new file mode 100644
index 000000000..5e3512d10
--- /dev/null
+++ b/docs/known-issues/en/orderform-not-updating-after-order-is-placed.md
@@ -0,0 +1,49 @@
+---
+title: 'OrderForm not updating after order is placed'
+id: 4Xkk9LA95PRXbKxFYy189f
+status: PUBLISHED
+createdAt: 2024-06-27T15:22:19.922Z
+updatedAt: 2024-06-28T11:47:47.958Z
+publishedAt: 2024-06-28T11:47:47.958Z
+firstPublishedAt: 2024-06-27T15:22:20.951Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: orderform-not-updating-after-order-is-placed
+locale: en
+kiStatus: Backlog
+internalReference: 1056870
+---
+
+## Summary
+
+
+After an order is placed, the orderFormId is not updated, causing items to remain visible in the cart. This issue affects FastStore accounts
+This issue may be related to the delay in updating the orderFormId due to changes related to the checkout cookie.
+
+After the gatewayCallback response, the expected scenario would be a new orderFormId cookie for the user. This scenario is broken because the domain of the new cookie does not match the domain of the user's previous cookie (because of the secure domain).
+
+
+##
+
+## Simulation
+
+
+
+- Complete an order on a Faststore account
+- Return to the home page
+- The items that you just bought will remain in your cart
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md b/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md
index b58e29bec..54dc306d3 100644
--- a/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md
+++ b/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md
@@ -20,7 +20,7 @@ internalReference:
 
 Currently the delivery times for a scheduled delivery are out of order, or in descending order. For better readability, this information is expected to be organized in ascending order.
 
-![image](https://images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/ordering-of-specification-groups-from-the-root-category-does-not-work.md b/docs/known-issues/en/ordering-of-specification-groups-from-the-root-category-does-not-work.md
index b977fec9c..7fcdeabd2 100644
--- a/docs/known-issues/en/ordering-of-specification-groups-from-the-root-category-does-not-work.md
+++ b/docs/known-issues/en/ordering-of-specification-groups-from-the-root-category-does-not-work.md
@@ -3,8 +3,8 @@ title: 'Ordering of specification groups from the root category does not work'
 id: 5iuLxVdAuK70VMYGts7CzJ
 status: PUBLISHED
 createdAt: 2022-08-09T00:46:23.102Z
-updatedAt: 2022-11-25T21:43:59.468Z
-publishedAt: 2022-11-25T21:43:59.468Z
+updatedAt: 2024-02-16T20:25:08.305Z
+publishedAt: 2024-02-16T20:25:08.305Z
 firstPublishedAt: 2022-08-09T00:46:23.684Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: ordering-of-specification-groups-from-the-root-category-does-not-work
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 634129
 ---
 
diff --git a/docs/known-issues/en/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md b/docs/known-issues/en/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
index 12f44f75f..e09ade91a 100644
--- a/docs/known-issues/en/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
+++ b/docs/known-issues/en/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
@@ -3,8 +3,8 @@ title: "Orders invoiced at VTEX but that don't update the invoice at Netshoes"
 id: 1SrJBQj0iTYh4AdvmJQqIg
 status: PUBLISHED
 createdAt: 2022-05-11T19:45:30.831Z
-updatedAt: 2022-11-25T21:56:22.896Z
-publishedAt: 2022-11-25T21:56:22.896Z
+updatedAt: 2024-02-16T20:25:46.426Z
+publishedAt: 2024-02-16T20:25:46.426Z
 firstPublishedAt: 2022-05-11T19:45:31.187Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 577219
 ---
 
diff --git a/docs/known-issues/en/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md b/docs/known-issues/en/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
new file mode 100644
index 000000000..52fed478c
--- /dev/null
+++ b/docs/known-issues/en/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
@@ -0,0 +1,51 @@
+---
+title: 'Orders invoicing calculation using input invoice value in output invoice validation'
+id: kEjeBKkJMpUDR0JdX6fZv
+status: PUBLISHED
+createdAt: 2023-11-06T11:39:27.169Z
+updatedAt: 2023-11-09T20:47:52.250Z
+publishedAt: 2023-11-09T20:47:52.250Z
+firstPublishedAt: 2023-11-06T11:39:28.035Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation
+locale: en
+kiStatus: Fixed
+internalReference: 930491
+---
+
+## Summary
+
+
+During the process of sending invoices, it is possible for the user to send output and input invoices, but if two partial invoices are made in an order, one for output and one for input, the system adds up these values to validate whether the order can receive a new invoice, making it impossible for orders whose item was invoiced and then returned not to have their total value invoiced.
+
+This is because the Orders API currently performs a value validation to determine whether it should allow a new output invoice to be made for the order, but the calculation is considering the sum of all invoices regardless of their type (input or output), making the system understand that there is no more value to be invoiced.
+
+
+##
+
+## Simulation
+
+
+
+1- Create an order with two units of the same SKU
+2- Invoice only one of these units
+3- Now make a new input invoice for the unit invoiced in the previous step.
+4- Now try to invoice the remaining unit of the order.
+5- At this point you will receive a generic message in the UI indicating that it is not possible to invoice the item.
+
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/orders-with-asterisks-in-the-address-and-profile.md b/docs/known-issues/en/orders-with-asterisks-in-the-address-and-profile.md
new file mode 100644
index 000000000..08128b451
--- /dev/null
+++ b/docs/known-issues/en/orders-with-asterisks-in-the-address-and-profile.md
@@ -0,0 +1,51 @@
+---
+title: 'Orders with asterisks in the address and profile'
+id: 6AaZ4p042LZwvfeKIqavjw
+status: PUBLISHED
+createdAt: 2023-08-25T17:03:49.755Z
+updatedAt: 2024-06-06T20:16:16.607Z
+publishedAt: 2024-06-06T20:16:16.607Z
+firstPublishedAt: 2023-08-25T17:03:50.594Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: orders-with-asterisks-in-the-address-and-profile
+locale: en
+kiStatus: Backlog
+internalReference: 360783
+---
+
+## Summary
+
+
+There are orders where the `invoiceAddress`, `shippingAddress` or `clientProfileData` are being sent as 'masked' instead of the actual address. This behavior occurs when a user completes the purchase with an order form containing masked data that is 'stringified'. Since these are string fields, the order data is filled with the '***' mask.
+
+So, the bug lies in the fact that our API to place orders allows objects with special characters in these fields.
+
+
+##
+
+## Simulation
+
+
+
+1. Add some products to your cart;
+2. During the checkout process, enter a valid billing address and log into your account;
+3. Abandon the cart or leave the website without completing the purchase;
+4. Use our API to insert an attachment and put an address with "***" in some fields, such as the neighborhood one;
+5. Place an order using this same cart;
+6. Note that the order will have the shipping data with these special characters.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md b/docs/known-issues/en/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
index 5e1303c8d..ed13fc47e 100644
--- a/docs/known-issues/en/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
+++ b/docs/known-issues/en/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
@@ -3,8 +3,8 @@ title: 'Orders with items on array MarketplaceItems is not opening on New UI Adm
 id: 3tj9AKklBHm4tCKYgrfDi5
 status: PUBLISHED
 createdAt: 2022-09-13T03:06:57.141Z
-updatedAt: 2022-11-25T22:01:26.839Z
-publishedAt: 2022-11-25T22:01:26.839Z
+updatedAt: 2023-09-28T15:01:19.205Z
+publishedAt: 2023-09-28T15:01:19.205Z
 firstPublishedAt: 2022-09-13T03:06:57.675Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,39 +12,41 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 656821
 ---
 
 ## Summary
 
 
+
 Some orders has the array "marketplace Items" filled with more items then the array "items" of json order. This setup is normal and is regarding for example "wedding gift list".
 But the New UI is not prepared to handle these kind of orders with items on "marketplace Items" and broke the page with an error message:
 
 
-
-
-
 "Sorry, something went wrong on our side.
-
 Please try again or refresh the page.
-
 Back to the list"
 
 
 
+##
 
 ## Simulation
 
 
-Create an order with catalog using array "marketplace Items", after that you can try see the order on UI admin. The UI will broke and show a message error.
 
+Create an order with catalog using array "marketplace Items", after that you can try see the order on UI admin. The UI will broke and show a message error.
 
 
+##
 
 ## Workaround
 
 
 Use the old UI to open that order.
 
+
+
+
+
diff --git a/docs/known-issues/en/orders-without-invoiceaddress-created-through-native-ui.md b/docs/known-issues/en/orders-without-invoiceaddress-created-through-native-ui.md
index 0e4bd27e2..e35f79eb3 100644
--- a/docs/known-issues/en/orders-without-invoiceaddress-created-through-native-ui.md
+++ b/docs/known-issues/en/orders-without-invoiceaddress-created-through-native-ui.md
@@ -3,8 +3,8 @@ title: 'Orders without invoiceAddress created through native UI'
 id: 1XjNZhcTJ5rZJP4w3kJtcW
 status: PUBLISHED
 createdAt: 2022-01-24T20:21:07.893Z
-updatedAt: 2022-11-25T21:52:06.721Z
-publishedAt: 2022-11-25T21:52:06.721Z
+updatedAt: 2023-12-19T21:34:15.743Z
+publishedAt: 2023-12-19T21:34:15.743Z
 firstPublishedAt: 2022-06-27T19:49:05.878Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: orders-without-invoiceaddress-created-through-native-ui
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 306140
 ---
 
@@ -23,6 +23,7 @@ In some cases it is still possible to create orders without `invoiceAddress` via
 The invoice address must be mandatory in the UI of all stores that have the functionality enabled.
 
 
+##
 
 ## Simulation
 
@@ -44,9 +45,13 @@ In addition to the above, the behavior can be observed when the user is in the s
 Another scenario that induces the behavior is to switch between the list of previously registered addresses and a new address, which allows the user to proceed to payment without filling in the zip code (of a new address).
 
 
+##
 
 ## Workaround
 
 
 There is no known workaround to avoid the root scenario.
 
+
+
+
diff --git a/docs/known-issues/en/ordination-of-images-when-uploading-a-new-version-not-working.md b/docs/known-issues/en/ordination-of-images-when-uploading-a-new-version-not-working.md
index 3eb176ac3..8a4d2ffcd 100644
--- a/docs/known-issues/en/ordination-of-images-when-uploading-a-new-version-not-working.md
+++ b/docs/known-issues/en/ordination-of-images-when-uploading-a-new-version-not-working.md
@@ -3,8 +3,8 @@ title: 'Ordination of images when uploading a new version not working'
 id: 2Oq65YHU6uIQpQ5g8ZpjTE
 status: PUBLISHED
 createdAt: 2023-01-25T15:08:43.356Z
-updatedAt: 2023-01-25T15:08:43.873Z
-publishedAt: 2023-01-25T15:08:43.873Z
+updatedAt: 2024-02-16T20:26:48.206Z
+publishedAt: 2024-02-16T20:26:48.206Z
 firstPublishedAt: 2023-01-25T15:08:43.873Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: ordination-of-images-when-uploading-a-new-version-not-working
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 739814
 ---
 
diff --git a/docs/known-issues/en/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/en/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
new file mode 100644
index 000000000..07db0a6e0
--- /dev/null
+++ b/docs/known-issues/en/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
@@ -0,0 +1,48 @@
+---
+title: 'Outdated Elo regex is causing us to misidentify some BINs'
+id: 45vx88VCQ0yZynkVxGqSq8
+status: PUBLISHED
+createdAt: 2024-04-10T17:25:57.376Z
+updatedAt: 2024-04-10T17:25:58.309Z
+publishedAt: 2024-04-10T17:25:58.309Z
+firstPublishedAt: 2024-04-10T17:25:58.309Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: outdated-elo-regex-is-causing-us-to-misidentify-some-bins
+locale: en
+kiStatus: Backlog
+internalReference: 1015043
+---
+
+## Summary
+
+
+Some BINs are not being correctly identified at checkout. The card brand is determined by a regex that could become outdated, leading to unidentified or misidentified card brands.
+
+
+##
+
+## Simulation
+
+
+
+1. Configure two Payment Conditions one for Elo
+2. Add a random item to your cart in the store and choose to pay for it by Credit Card
+3. Fill in the card number with the Elo BIN 65057000 and complete it with random numbers
+4. Fill the rest of the card information with fake data
+5. As the card could not be identified, the checkout will ask to confirm the card number and the card brand can be already selected as another card brand
+
+
+##
+
+## Workaround
+
+
+
+The user should change the selected card brand at checkout by clicking on the right brand.
+
+
+
+
diff --git a/docs/known-issues/en/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md b/docs/known-issues/en/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
new file mode 100644
index 000000000..8d519642e
--- /dev/null
+++ b/docs/known-issues/en/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
@@ -0,0 +1,49 @@
+---
+title: 'Outdated indexed information when performing 2 product changes in a row.'
+id: 66aX8MktRogeUD9bbTo0vF
+status: PUBLISHED
+createdAt: 2023-09-26T14:44:57.146Z
+updatedAt: 2023-09-26T14:44:57.895Z
+publishedAt: 2023-09-26T14:44:57.895Z
+firstPublishedAt: 2023-09-26T14:44:57.895Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: outdated-indexed-information-when-performing-2-product-changes-in-a-row
+locale: en
+kiStatus: No Fix
+internalReference: 907428
+---
+
+## Summary
+
+
+For stores using the legacy search engine, if two changes of a product's data are done in a quick succession (i.e. you've inactivated a product and then reactivated it right after that), and the latter change returns the product's information to what it was right before, the state of said item can be stuck in the first change, as the latter is not properly recognized.
+
+This issue doesn't happen in stores using the intelligent search application.
+
+
+##
+
+## Simulation
+
+
+1 - get an active item in your store and inactivate it
+2 - Right after that (< 5min), reactivate it.
+3 - After a few minutes, check your product: it'll be not showing in the store, despite it being set to do so. (in other words, it got "stuck" in that middle state).
+
+
+##
+
+## Workaround
+
+
+1 - Reindex said products after 5+ min of experiencing the issue.
+2 - Use the Intelligent search engine, which doesn't face this issue at all.
+3 - Avoid performing 2+ changes for a product in a row in which the latter change just reverts the former.
+
+
+
+
+
diff --git a/docs/known-issues/en/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/en/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
index d8b774139..c3053701f 100644
--- a/docs/known-issues/en/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/en/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
@@ -3,8 +3,8 @@ title: 'Outdated Mastercard Debit regex is causing us to misidentify some BINs'
 id: 5gx4dSY2P5gGE0JI661hGL
 status: PUBLISHED
 createdAt: 2022-08-20T00:03:11.640Z
-updatedAt: 2022-11-25T22:04:24.418Z
-publishedAt: 2022-11-25T22:04:24.418Z
+updatedAt: 2024-04-02T19:13:02.839Z
+publishedAt: 2024-04-02T19:13:02.839Z
 firstPublishedAt: 2022-08-20T00:03:12.490Z
 contentType: knownIssue
 productTeam: Payments
@@ -22,6 +22,7 @@ internalReference: 642136
 Some BINs are not being identified correctly at checkout. The card brand is determined by a regex that may eventually be out of date, causing the card brand to be unidentified or misidentified.
 
 
+##
 
 ## Simulation
 
@@ -34,9 +35,13 @@ Some BINs are not being identified correctly at checkout. The card brand is dete
 5. As the card could not be identified, the checkout will ask to confirm the card number and the card brand can be already selected as another card brand
 
 
+##
 
 ## Workaround
 
 
 There's no workaround.
 
+
+
+
diff --git a/docs/known-issues/en/outdated-url-on-the-update-binding-ui.md b/docs/known-issues/en/outdated-url-on-the-update-binding-ui.md
new file mode 100644
index 000000000..07907d5b7
--- /dev/null
+++ b/docs/known-issues/en/outdated-url-on-the-update-binding-ui.md
@@ -0,0 +1,50 @@
+---
+title: 'Outdated URL on the Update binding UI'
+id: 7bgh2LIJTFovgoz0TaBr5B
+status: PUBLISHED
+createdAt: 2023-08-30T20:04:23.301Z
+updatedAt: 2023-08-30T20:04:23.905Z
+publishedAt: 2023-08-30T20:04:23.905Z
+firstPublishedAt: 2023-08-30T20:04:23.905Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: outdated-url-on-the-update-binding-ui
+locale: en
+kiStatus: Backlog
+internalReference: 890791
+---
+
+## Summary
+
+
+When the merchant is updating a biding the UI is like it follows:
+ ![](https://vtexhelp.zendesk.com/attachments/token/UfffIyuM7K7isQMiPnAqRvSiW/?name=image.png)
+
+When trying to go to the license manager link, they are redirected to a SWW page.
+
+
+##
+
+## Simulation
+
+
+
+1. go to CMS setup (.../admin/a)
+2. Select a website and click on update binding
+3. Click on the License Manager link
+4. Check that an error SWW appears.
+
+
+##
+
+## Workaround
+
+
+Use the url directly: (.../admin/account/stores/)
+
+
+
+
+
diff --git a/docs/known-issues/en/pageview-is-triggered-twice-when-accessing-my-account.md b/docs/known-issues/en/pageview-is-triggered-twice-when-accessing-my-account.md
new file mode 100644
index 000000000..d733f6726
--- /dev/null
+++ b/docs/known-issues/en/pageview-is-triggered-twice-when-accessing-my-account.md
@@ -0,0 +1,44 @@
+---
+title: 'pageView is triggered twice when accessing My Account'
+id: 2jV0cIVxNUhb170tBgBQo6
+status: PUBLISHED
+createdAt: 2023-07-03T16:33:09.076Z
+updatedAt: 2023-07-03T16:33:09.652Z
+publishedAt: 2023-07-03T16:33:09.652Z
+firstPublishedAt: 2023-07-03T16:33:09.652Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: pageview-is-triggered-twice-when-accessing-my-account
+locale: en
+kiStatus: Backlog
+internalReference: 854480
+---
+
+## Summary
+
+
+When accessing the My Account, the pageView event is triggered twice, duplicating the data on Analytics.
+
+
+##
+
+## Simulation
+
+
+
+- Configure the app Google Tag Manager,
+- Access the My Account;
+- Open the browser's Developer Tools and type "dataLayer" on Console; there will be two pageView events.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md b/docs/known-issues/en/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
new file mode 100644
index 000000000..1364b80bf
--- /dev/null
+++ b/docs/known-issues/en/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
@@ -0,0 +1,59 @@
+---
+title: 'Pageview triggers on G4A are being duplicated in custom search pages'
+id: 4hIwZ2v9bbyyZXrxoDglyx
+status: PUBLISHED
+createdAt: 2023-11-08T13:35:27.802Z
+updatedAt: 2024-02-19T18:43:16.271Z
+publishedAt: 2024-02-19T18:43:16.271Z
+firstPublishedAt: 2023-11-08T13:35:28.390Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages
+locale: en
+kiStatus: Backlog
+internalReference: 888042
+---
+
+## Summary
+
+
+The pageView event is showing duplicated in dataLayer when on custom search pages
+
+
+##
+
+## Simulation
+
+
+
+- Go to any custom search page
+- Open your browser's console
+- Type dataLayer and check the pageView event
+
+The expected behavior is the duplicated event
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+## **Internal Notes**
+
+Also found something curious on department page with pageView and page_view
+
+https://storetheme.vtex.com/apparel---accessories/
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/dXFuDY5Q9XhZ7hgIvA8m8ugJ3/?name=image.png)
+
+But, this specific issue is replicable at
+
+https://www.dzarm.com.br/outlet
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/EVakZYSBKtcrCQoNXBe92uAzQ/?name=image.png)
+
diff --git a/docs/known-issues/en/pagination-links-on-search-results-not-working-on-giftlist-pages.md b/docs/known-issues/en/pagination-links-on-search-results-not-working-on-giftlist-pages.md
index 521ffb3c9..9b190097c 100644
--- a/docs/known-issues/en/pagination-links-on-search-results-not-working-on-giftlist-pages.md
+++ b/docs/known-issues/en/pagination-links-on-search-results-not-working-on-giftlist-pages.md
@@ -3,8 +3,8 @@ title: 'Pagination links on Search Results not working on Giftlist Pages'
 id: 1w6h5MwZthKMM8rvqXZtQi
 status: PUBLISHED
 createdAt: 2022-11-02T14:01:35.650Z
-updatedAt: 2022-11-25T21:41:59.731Z
-publishedAt: 2022-11-25T21:41:59.731Z
+updatedAt: 2024-02-16T20:26:50.585Z
+publishedAt: 2024-02-16T20:26:50.585Z
 firstPublishedAt: 2022-11-02T14:01:36.502Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: pagination-links-on-search-results-not-working-on-giftlist-pages
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 481330
 ---
 
diff --git a/docs/known-issues/en/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md b/docs/known-issues/en/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
new file mode 100644
index 000000000..1640af05c
--- /dev/null
+++ b/docs/known-issues/en/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
@@ -0,0 +1,50 @@
+---
+title: "Pagination on searchpage doesn't reset when changing search context"
+id: 2lNL95NDZvO8NqxhJDrA6G
+status: PUBLISHED
+createdAt: 2023-07-06T19:54:29.289Z
+updatedAt: 2023-07-06T19:58:59.059Z
+publishedAt: 2023-07-06T19:58:59.059Z
+firstPublishedAt: 2023-07-06T19:54:29.968Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: pagination-on-searchpage-doesnt-reset-when-changing-search-context
+locale: en
+kiStatus: Scheduled
+internalReference: 857392
+---
+
+## Summary
+
+
+While navigating on a given page of a PLP, fetching to show more results, and changing the context to navigate in a different department, the pagination param will be kept and the search result will start on the new category in the same page that we were previously
+
+
+##
+
+## Simulation
+
+
+
+Following the steps:
+
+
+- Go to: https://starter.vtex.app/computer---software
+- Click on Load more products (the page parameter in your URL is going to change)
+- Click on a different department (for example Technology)
+- Check that the page technology will start with the pagination that you were previously
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md b/docs/known-issues/en/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
index e0b63259c..7d15518b0 100644
--- a/docs/known-issues/en/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
+++ b/docs/known-issues/en/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
@@ -3,8 +3,8 @@ title: 'Pasting postal code in shipping preview cart sometimes returns null API
 id: 5Lq32htqC7M9xiqajfn7y7
 status: PUBLISHED
 createdAt: 2022-06-01T15:30:08.776Z
-updatedAt: 2022-11-25T21:53:05.306Z
-publishedAt: 2022-11-25T21:53:05.306Z
+updatedAt: 2024-05-21T13:03:32.812Z
+publishedAt: 2024-05-21T13:03:32.812Z
 firstPublishedAt: 2022-06-01T15:30:09.241Z
 contentType: knownIssue
 productTeam: Checkout
@@ -19,16 +19,29 @@ internalReference: 481878
 ## Summary
 
 
-After entering the postal code once in shipping preview and choosing to paste the postal code again, it sometimes occurs to make a null request to the zip code API.
+After entering the postal code once in the shipping preview and choosing to paste it again, it sometimes occurs to make a null request to the zip code API.
 
+The request is `/api/checkout/pub/postal-code/null/postalcodenumber` and returns a 500 error.
 
 
+##
 
 ## Simulation
 
 
 
+- Go to the cart and add a postal code;
+- Click to change it and paste another postal code (or even the same);
+- Go to the shipping step, and the address may be incomplete.
+
+
+##
+
 ## Workaround
 
 
+The user will need to click the "Calculate" button or hit the enter key, in some cases typing the postal code without inserting it.
+
+
+
 
diff --git a/docs/known-issues/en/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md b/docs/known-issues/en/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
new file mode 100644
index 000000000..ece76a68a
--- /dev/null
+++ b/docs/known-issues/en/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
@@ -0,0 +1,46 @@
+---
+title: 'Payment Conditions set to process transactions in installments other than 1x are processing transactions as prepaid in full'
+id: 2z9cDiCAovzKVFZO7RSqOD
+status: PUBLISHED
+createdAt: 2024-05-09T18:47:33.319Z
+updatedAt: 2024-05-09T18:47:34.221Z
+publishedAt: 2024-05-09T18:47:34.221Z
+firstPublishedAt: 2024-05-09T18:47:34.221Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full
+locale: en
+kiStatus: Backlog
+internalReference: 1030652
+---
+
+## Summary
+
+
+Payment conditions configured to process transactions in a number of installments other than 1x are being able to process payments in 1x. The issue only occurs for payments where the user has chosen to pay as prepaid in full.
+
+
+##
+
+## Simulation
+
+
+
+1. Set up 3 Payment Conditions for credit cards of any brand: Payment Condition A - with installment in 1x, Payment Condition B - with installment in 2x, and Payment Condition C - with installment in 3x.
+2. Go to the Checkout page by adding any item to the cart and proceed to the payment screen. Choose to pay with a credit card in 1x and complete the purchase.
+3. Go to the admin and open the newly created transaction, click the "+ Information" button, and observe that the `AvailableRules` field will contain a list with all the IDs of Payment Conditions, Payment Condition A, Payment Condition B, and Payment Condition C, as being able to process the transaction in question.
+
+
+##
+
+## Workaround
+
+
+t is possible to set the Payment Condition 1x as default, so when there is a tie between all Payment Conditions, the gateway will prioritize the default rule.
+
+
+
+
+
diff --git a/docs/known-issues/en/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md b/docs/known-issues/en/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
index 89305d24f..075993c39 100644
--- a/docs/known-issues/en/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
+++ b/docs/known-issues/en/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
@@ -3,8 +3,8 @@ title: 'Payment Method from Marketplace matches with SWL when using identical ty
 id: 4AHyl5z7ySagx6Myx0KqM7
 status: PUBLISHED
 createdAt: 2022-03-15T22:06:35.540Z
-updatedAt: 2022-11-25T22:12:10.257Z
-publishedAt: 2022-11-25T22:12:10.257Z
+updatedAt: 2024-02-16T20:29:19.824Z
+publishedAt: 2024-02-16T20:29:19.824Z
 firstPublishedAt: 2022-03-15T22:06:36.030Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 402140
 ---
 
diff --git a/docs/known-issues/en/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md b/docs/known-issues/en/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
index 0883a4cdb..58fe4e8df 100644
--- a/docs/known-issues/en/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
+++ b/docs/known-issues/en/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'Payment methods displayed at checkout differ from active payment conditi
 id: 1cpVNspn5G6je4EZKzvCF9
 status: PUBLISHED
 createdAt: 2022-09-27T16:32:55.806Z
-updatedAt: 2023-04-10T15:14:18.718Z
-publishedAt: 2023-04-10T15:14:18.718Z
+updatedAt: 2024-06-07T21:23:28.431Z
+publishedAt: 2024-06-07T21:23:28.431Z
 firstPublishedAt: 2023-04-10T15:11:01.389Z
 contentType: knownIssue
 productTeam: Payments
diff --git a/docs/known-issues/en/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md b/docs/known-issues/en/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
new file mode 100644
index 000000000..56c7569bb
--- /dev/null
+++ b/docs/known-issues/en/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
@@ -0,0 +1,63 @@
+---
+title: 'Payment Terms changes not applied in the B2B Checkout Settings'
+id: 12PfZx6O0MIUSIFdpQdUdI
+status: PUBLISHED
+createdAt: 2024-04-18T19:07:22.743Z
+updatedAt: 2024-07-25T21:47:29.442Z
+publishedAt: 2024-07-25T21:47:29.442Z
+firstPublishedAt: 2024-04-18T19:07:23.644Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: payment-terms-changes-not-applied-in-the-b2b-checkout-settings
+locale: en
+kiStatus: Fixed
+internalReference: 1019548
+---
+
+## Summary
+
+
+Updating the Payment Terms in Organization Details UI for an organization doesn't apply to B2B Checkout Settings.
+
+This behavior occurs because the update occurs only for the organization, but the B2B Checkout Settings uses information from the cost center, which is not updated by the Organization Details UI.
+
+
+##
+
+## Simulation
+
+
+
+- Create an organization;
+- In the Organization Details UI, update the Payment Terms;
+- Access the website, assemble a cart, and access checkout; the Payment Terms will remain the same.
+
+
+##
+
+## Workaround
+
+
+
+- Access GraphQL IDE and select vtex.b2b-organizations-graphql;
+- Use the query below to get the cost center details:
+
+    { getCostCenterById (id:"insert here the cost center id"){ name addresses{ addressId addressType addressQuery postalCode country receiverName city state street number complement neighborhood geoCoordinates reference } phoneNumber businessDocument customFields{ name type value dropdownValues{ value label } useOnRegistration } stateRegistration paymentTerms{ id name } }}
+
+- Use the query below to get the payment terms from the organization:
+
+    { getOrganizationById(id:"insert here the organization id"){ paymentTerms{ id name } }}
+
+
+
+- Send a mutation to update the cost center, adding the payment terms from the organization to the response from the cost center:
+
+    mutation updateCostCenter($id: ID!, $input: CostCenterInput!) { updateCostCenter( id: $id input: $input ){ id status }}{ "id": "", "input": { "name": "", "addresses": [{ "addressId": "", "addressType": "", "addressQuery": "", "postalCode": "", "country": "", "receiverName": "", "city": "", "state": "", "street": "", "number": "", "complement": null, "neighborhood": "", "geoCoordinates": [], "reference": null } ], "phoneNumber": "", "businessDocument": "", "customFields": [], "stateRegistration": "", "paymentTerms": [{ "id": "", "name": "" }, { "id": "", "name": "" }] }}
+
+
+
+
+
+
diff --git a/docs/known-issues/en/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/en/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
new file mode 100644
index 000000000..0b74b8eba
--- /dev/null
+++ b/docs/known-issues/en/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -0,0 +1,48 @@
+---
+title: 'Payment Terms configured in B2B Settings is not assigned after approving Organizations'
+id: 7pUMnYPWPHlhPzlWwTtWsL
+status: PUBLISHED
+createdAt: 2024-02-26T22:29:03.516Z
+updatedAt: 2024-02-26T22:29:04.387Z
+publishedAt: 2024-02-26T22:29:04.387Z
+firstPublishedAt: 2024-02-26T22:29:04.387Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations
+locale: en
+kiStatus: Backlog
+internalReference: 989507
+---
+
+## Summary
+
+
+The payment terms configured in B2B Organizations Settings is not saved in the Organization Details.
+
+
+##
+
+## Simulation
+
+
+
+- Configure a default payment terms in B2B Organizations Settings;
+- Create an Organization Request;
+- Approve the Organization Request;
+- Check the Organization details; it won't have any payment terms assigned.
+
+
+##
+
+## Workaround
+
+
+
+- Assign the payment terms to the organization via admin;
+- Create a trigger for the organizations entity's schema.
+
+
+
+
diff --git a/docs/known-issues/en/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md b/docs/known-issues/en/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
new file mode 100644
index 000000000..502532272
--- /dev/null
+++ b/docs/known-issues/en/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
@@ -0,0 +1,46 @@
+---
+title: 'PaymentSystems are not returned in orderForm when a cart price comes exclusively from manualPrice'
+id: 3KPNFtPgEwshbv6WiGrqOF
+status: PUBLISHED
+createdAt: 2024-04-30T20:06:52.774Z
+updatedAt: 2024-04-30T20:06:53.756Z
+publishedAt: 2024-04-30T20:06:53.756Z
+firstPublishedAt: 2024-04-30T20:06:53.756Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice
+locale: en
+kiStatus: Backlog
+internalReference: 1025321
+---
+
+## Summary
+
+
+When a cart's total value comes exclusively from a manual price, items `price` and delivery `price` are `0`, no payment systems other than Gift Card (if active) are offered.
+
+
+##
+
+## Simulation
+
+
+
+- Add an item with price `0` and select a delivery option with price `0`
+- Add a `manualPrice` amount to the item
+- Proceed to the payment step in checkout and no payment methods are returned as available
+
+
+##
+
+## Workaround
+
+
+There is no known workaround other thank adding some ammount to the item's price.
+
+
+
+
+
diff --git a/docs/known-issues/en/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md b/docs/known-issues/en/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
index 3fe39f876..338b0616d 100644
--- a/docs/known-issues/en/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
+++ b/docs/known-issues/en/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
@@ -3,8 +3,8 @@ title: "Payout and Transaction split don't work in the same order for Multilevel
 id: 3rFyqzEnSwx2czwdlgDovU
 status: PUBLISHED
 createdAt: 2023-03-23T19:03:22.498Z
-updatedAt: 2023-03-27T12:27:57.714Z
-publishedAt: 2023-03-27T12:27:57.714Z
+updatedAt: 2024-02-16T20:25:26.525Z
+publishedAt: 2024-02-16T20:25:26.525Z
 firstPublishedAt: 2023-03-23T19:03:23.526Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 777201
 ---
 
diff --git a/docs/known-issues/en/paypalplus-does-not-respect-the-minimum-installment-amount.md b/docs/known-issues/en/paypalplus-does-not-respect-the-minimum-installment-amount.md
index ac97723ac..103f40972 100644
--- a/docs/known-issues/en/paypalplus-does-not-respect-the-minimum-installment-amount.md
+++ b/docs/known-issues/en/paypalplus-does-not-respect-the-minimum-installment-amount.md
@@ -3,8 +3,8 @@ title: 'PayPalPlus does not respect the minimum installment amount'
 id: 1IGzNPtXaaUsPkaq0qRgfK
 status: PUBLISHED
 createdAt: 2022-03-26T23:00:59.044Z
-updatedAt: 2022-11-25T22:06:43.067Z
-publishedAt: 2022-11-25T22:06:43.067Z
+updatedAt: 2024-02-16T20:25:30.693Z
+publishedAt: 2024-02-16T20:25:30.693Z
 firstPublishedAt: 2022-03-26T23:00:59.445Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: paypalplus-does-not-respect-the-minimum-installment-amount
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 370271
 ---
 
diff --git a/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md b/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md
index be1dc5a6d..885c5aaa5 100644
--- a/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md
+++ b/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md
@@ -3,8 +3,8 @@ title: 'Pickup point disregarded based on priority'
 id: 3bbsm8TELPBa0DpFtnlAGz
 status: PUBLISHED
 createdAt: 2021-09-29T14:38:08.930Z
-updatedAt: 2022-12-22T20:41:01.800Z
-publishedAt: 2022-12-22T20:41:01.800Z
+updatedAt: 2024-06-14T16:56:59.120Z
+publishedAt: 2024-06-14T16:56:59.120Z
 firstPublishedAt: 2021-09-29T14:49:34.443Z
 contentType: knownIssue
 productTeam: Post-purchase
@@ -13,7 +13,7 @@ tag: Logistics
 slug: pickup-point-disregarded-based-on-priority
 locale: en
 kiStatus: Backlog
-internalReference: 
+internalReference: 380545
 ---
 
 ## Summary
@@ -36,7 +36,7 @@ To simulate the described scenario, at least two shipping policies serving the s
 4. See which pickup point has been selected;
 5. Check which pickup points were disregarded and note the message displayed.
 
-![KIpontoderetirada EN](https://images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/097a4d4b13f79150adf8f2eda2e7a888/KIpontoderetirada_EN.png)
+![KIpontoderetirada EN](//images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/097a4d4b13f79150adf8f2eda2e7a888/KIpontoderetirada_EN.png)
 
 The pickup point was disregarded because there was another shipping method already named as **SCS Mall**.
 
diff --git a/docs/known-issues/en/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md b/docs/known-issues/en/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
new file mode 100644
index 000000000..5aed81072
--- /dev/null
+++ b/docs/known-issues/en/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
@@ -0,0 +1,49 @@
+---
+title: "Pickup point modal doesn't utilize geoCoordinates without a Google Maps key"
+id: 5aPNjLlsVVeyGe0Vywt0H9
+status: PUBLISHED
+createdAt: 2024-05-29T20:31:46.863Z
+updatedAt: 2024-07-03T15:56:30.595Z
+publishedAt: 2024-07-03T15:56:30.595Z
+firstPublishedAt: 2024-05-29T20:31:47.737Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key
+locale: en
+kiStatus: Backlog
+internalReference: 1041462
+---
+
+## Summary
+
+
+Inserting a postal code into the pickup point selector modal triggers a request to obtain available SLAs for that location. If the account doesn't have a Google Maps API key defined in its Checkout settings, this request will not include geoCoordinates information. This may result in pickup points within a valid range not being shown, such as ones whose freight tables are based on polygons.
+
+
+##
+
+## Simulation
+
+
+
+1. Use a store that doesn't have a Google Maps API key defined.
+2. Set up a pickup point, and bind it to a carrier whose freight table is based on polygons.
+3. Add a product to your cart.
+4. In the shipping preview, select the pickup option, and input a postal code that has availability for the pickup point you've created.
+5. Inspect the shippingData request generated by this action. It will not contain geoCoordinates.
+
+
+
+##
+
+## Workaround
+
+
+Set a Google Maps API key on the store's Checkout settings.
+
+
+
+
+
diff --git a/docs/known-issues/en/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md b/docs/known-issues/en/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
index 7a679e15e..abd79ed30 100644
--- a/docs/known-issues/en/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
+++ b/docs/known-issues/en/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
@@ -3,7 +3,7 @@ title: 'Pickup point not visible for selection in shipping policy (UI)'
 id: 84BhCZGoAxxuu1eljw0Uh
 status: DRAFT
 createdAt: 2021-12-28T14:52:46.105Z
-updatedAt: 2022-01-05T21:09:34.658Z
+updatedAt: 2024-02-16T20:27:08.666Z
 publishedAt: 
 firstPublishedAt: 2021-12-28T22:18:57.306Z
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: 
 slug: pickup-point-not-visible-for-selection-in-shipping-policy-ui
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 449813
 ---
 
diff --git a/docs/known-issues/en/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md b/docs/known-issues/en/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
new file mode 100644
index 000000000..717e35743
--- /dev/null
+++ b/docs/known-issues/en/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
@@ -0,0 +1,43 @@
+---
+title: 'Pickup point tags continue to be displayed in the shipping policy after deletion.'
+id: 2ZcIGeYUud4bQJrAd5MMLb
+status: PUBLISHED
+createdAt: 2024-04-10T18:52:17.457Z
+updatedAt: 2024-04-10T18:52:18.169Z
+publishedAt: 2024-04-10T18:52:18.169Z
+firstPublishedAt: 2024-04-10T18:52:18.169Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion
+locale: en
+kiStatus: Backlog
+internalReference: 1015158
+---
+
+## Summary
+
+
+The tags registered at the pickup point are available in a dropdown in the shipping policies to link the PUP to the Shipping Policy, however when any of these tags are deleted in the PUP, they remain available in the dropdown within the shipping policy.
+
+
+##
+
+## Simulation
+
+
+Register a tag in a PUP, check that it will be available in the shipping policy to link it to the PUP, then in the PUP itself delete the tag and check again in the shipping policy, the tag will still be there.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available
+
+
+
+
+
diff --git a/docs/known-issues/en/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md b/docs/known-issues/en/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
index e16ce3039..c26325a0c 100644
--- a/docs/known-issues/en/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
+++ b/docs/known-issues/en/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
@@ -3,8 +3,8 @@ title: "Pickup points list can't be scrolled after searching addresses in map mo
 id: 3e0JgNoWSQ0GAw8kurGrIR
 status: PUBLISHED
 createdAt: 2022-08-11T18:35:48.300Z
-updatedAt: 2022-11-25T21:50:52.987Z
-publishedAt: 2022-11-25T21:50:52.987Z
+updatedAt: 2024-07-01T18:48:32.968Z
+publishedAt: 2024-07-01T18:48:32.968Z
 firstPublishedAt: 2022-08-11T18:35:48.775Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 624646
 ---
 
diff --git a/docs/known-issues/en/pickup-points-not-indexed-in-master-data.md b/docs/known-issues/en/pickup-points-not-indexed-in-master-data.md
new file mode 100644
index 000000000..46c53d52c
--- /dev/null
+++ b/docs/known-issues/en/pickup-points-not-indexed-in-master-data.md
@@ -0,0 +1,47 @@
+---
+title: 'Pickup Points not indexed in Master Data'
+id: 6OHjbM6GXBEvgepaod3AyT
+status: PUBLISHED
+createdAt: 2023-12-14T22:29:26.240Z
+updatedAt: 2024-04-30T12:56:14.390Z
+publishedAt: 2024-04-30T12:56:14.390Z
+firstPublishedAt: 2023-12-14T22:29:26.972Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: pickup-points-not-indexed-in-master-data
+locale: en
+kiStatus: Fixed
+internalReference: 530824
+---
+
+## Summary
+
+
+Currently, the logistics system uses MasterData to store Pickup Points information. As a result, we may have problems indexing this internal entity when using the search route. This can lead to outdated information, such as:
+
+- Delete made in Logistics that is not reflected in the list;
+- Pickup Point being activated/inactivated in Logistics but still returning with the previous status;
+- Coordinate changes not being reflected;
+- And others.
+
+
+##
+
+## Simulation
+
+
+There is no reliable way to reproduce this issue.
+
+
+##
+
+## Workaround
+
+
+The VTEX team must check the data and eventually re-index it, so that the data will be updated.
+
+
+
+
diff --git a/docs/known-issues/en/pickup-points-starting-with-the-same-id-pattern-show-product-available.md b/docs/known-issues/en/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
new file mode 100644
index 000000000..2bf24a3dd
--- /dev/null
+++ b/docs/known-issues/en/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
@@ -0,0 +1,46 @@
+---
+title: 'Pick-up points starting with the same ID pattern show product available'
+id: 1iCnOFHyKNTLvY20VS58HP
+status: PUBLISHED
+createdAt: 2024-01-10T16:01:39.766Z
+updatedAt: 2024-01-10T16:01:40.403Z
+publishedAt: 2024-01-10T16:01:40.403Z
+firstPublishedAt: 2024-01-10T16:01:40.403Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: pickup-points-starting-with-the-same-id-pattern-show-product-available
+locale: en
+kiStatus: Backlog
+internalReference: 964036
+---
+
+## Summary
+
+
+When the two pick-up points with IDs start with the same pattern, the checkout UI validates them as the same store, showing a product available.
+
+
+##
+
+## Simulation
+
+
+
+- Register two pick-up points: one with ID 8 and another one with ID 835;
+- Associate them with different shipping strategies, where only one pick-up should have a product available;
+- Assemble a cart and select the pick-up where the product shouldn't be available;
+- The product will show as available.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md b/docs/known-issues/en/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
new file mode 100644
index 000000000..3fc4f813e
--- /dev/null
+++ b/docs/known-issues/en/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
@@ -0,0 +1,47 @@
+---
+title: 'Pick-up-point and schedule delivery in the same cart are not working correctly'
+id: 6ZCy8a4K6655BANe2yvz6e
+status: PUBLISHED
+createdAt: 2023-06-16T21:14:13.927Z
+updatedAt: 2023-06-16T21:14:14.834Z
+publishedAt: 2023-06-16T21:14:14.834Z
+firstPublishedAt: 2023-06-16T21:14:14.834Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly
+locale: en
+kiStatus: Backlog
+internalReference: 482256
+---
+
+## Summary
+
+
+The UI does not work correctly in a cart with more than one item with a delivery split in which one of the items is available for pick up and the others only for scheduled delivery.
+
+The date for choosing pick-up items is set without problems. But the dates for the scheduled delivery do not behave as expected.
+
+
+##
+
+## Simulation
+
+
+
+- Assemble a cart with at least two items where one of the items is available for pick up and the others only for scheduled delivery;
+- In the shipping step, select Pick up in store and select a delivery window ;
+- Try to select a delivery window for the schedule delivery.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md b/docs/known-issues/en/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
new file mode 100644
index 000000000..5543d2085
--- /dev/null
+++ b/docs/known-issues/en/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
@@ -0,0 +1,56 @@
+---
+title: 'Placing postal code in the Shipping Preview of the cart is duplicating address options for recurring customers'
+id: 4J8TMlhGmMtnHKXGES4qie
+status: PUBLISHED
+createdAt: 2023-12-20T21:36:52.612Z
+updatedAt: 2023-12-20T21:36:53.238Z
+publishedAt: 2023-12-20T21:36:53.238Z
+firstPublishedAt: 2023-12-20T21:36:53.238Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers
+locale: en
+kiStatus: Backlog
+internalReference: 956338
+---
+
+## Summary
+
+
+We have some problems when it comes to placing postal codes in the **Shipping Preview** module in the cart, some of them are described in these KIs:
+
+
+- Ref. 1: [KI]  Pasting postal code in shipping preview cart sometimes returns null API result
+- Ref. 2: [KI] Shipping preview's postal code input field is not hidden
+
+In this case, what happens is that for customers who already have addresses registered in their profile (recurring buyers), when placing a postal code in the Shipping Preview already used in a past purchase, in the API An additional delivery address option is being placed (`shippingData.availableAddresses`), when advancing through the Checkout steps and reaching the address selection (`/checkout/#/shipping`), it turns out that instead of selecting the address corresponding to said postal code, it opens a new incomplete selection option, and in some cases hidden, forcing the client to select one in the list or complement the "new one" to get to the next step.
+
+
+##
+
+## Simulation
+
+
+
+1. Use a user that already made some purchases and whose profile has some address for delivery.
+2. Add some items to the cart, then go to the checkout.
+3. In the cart use the Shipping Preview to place a postal code of one in your profile.
+  1. Try to review the `orderForm`, and search for the `shippingData.availableAddresses`
+  2. The address in your profile will be listed with a key detail, the address has already the number of the street (`shippingData.availableAddresses.[].number`)
+  3. The new option in the array that generates the problem doesn’t have the `number`, which converts it into an incomplete address option.
+4. Try to go to the shipping step of the checkout (`/checkout/#/shipping`) and you will see that you cannot pass to the payment step if you do not complete de address selected, or select another one of the options.
+
+
+##
+
+## Workaround
+
+
+In the shipping step of the checkout, try to select the desired listed address (force select one of the previous ones of the client).
+
+
+
+
+
diff --git a/docs/known-issues/en/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md b/docs/known-issues/en/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
index 0923e16ac..26939bd0a 100644
--- a/docs/known-issues/en/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
+++ b/docs/known-issues/en/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
@@ -3,8 +3,8 @@ title: "Portal doesn't delete cookies when client logout at checkout"
 id: 5GPBW2TBOUzJkw5u47KC5z
 status: PUBLISHED
 createdAt: 2022-03-16T16:13:44.658Z
-updatedAt: 2022-11-25T22:10:31.240Z
-publishedAt: 2022-11-25T22:10:31.240Z
+updatedAt: 2024-04-26T18:05:09.421Z
+publishedAt: 2024-04-26T18:05:09.421Z
 firstPublishedAt: 2022-03-16T16:13:45.038Z
 contentType: knownIssue
 productTeam: Portal
@@ -24,6 +24,7 @@ At a store's checkout, we have an option to log out.
 Unfortunately, the request made to the portal application, is not deleting the cookies of the user, remaining on the OrderForm with the email ID from this client, so the client cannot log out using this option
 
 
+##
 
 ## Simulation
 
@@ -39,9 +40,14 @@ Checkout performs the request normally, making the request along with the `order
 However, Portal Application is not deleting this user's cookie and thus returning the same user, with this the email is kept in the orderForm and consequently, it is not logged out.
 
 
+##
 
 ## Workaround
 
 
-Log out using the Home page.
+Use a JS custom to force the logout
+
+
+
+
 
diff --git a/docs/known-issues/en/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md b/docs/known-issues/en/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
index 36b290004..68ac64139 100644
--- a/docs/known-issues/en/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
+++ b/docs/known-issues/en/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
@@ -3,8 +3,8 @@ title: "Portal keeps UTM's after logging out when using Callcenter Operator."
 id: 4dogeU7iMoTXBWwv5DyR8u
 status: PUBLISHED
 createdAt: 2022-03-18T19:04:54.519Z
-updatedAt: 2022-11-25T22:10:46.942Z
-publishedAt: 2022-11-25T22:10:46.942Z
+updatedAt: 2024-02-16T20:27:34.500Z
+publishedAt: 2024-02-16T20:27:34.500Z
 firstPublishedAt: 2022-03-18T19:04:55.239Z
 contentType: knownIssue
 productTeam: Portal
diff --git a/docs/known-issues/en/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md b/docs/known-issues/en/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
index f5f15f64c..8acf4d09f 100644
--- a/docs/known-issues/en/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
+++ b/docs/known-issues/en/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
@@ -3,8 +3,8 @@ title: 'Portal reloads all search results when accessing the URL with pagination
 id: 18Y8yYKByGTzMxyYhk1pdl
 status: PUBLISHED
 createdAt: 2022-01-23T02:35:50.182Z
-updatedAt: 2022-11-25T22:11:17.525Z
-publishedAt: 2022-11-25T22:11:17.525Z
+updatedAt: 2024-02-16T20:29:31.154Z
+publishedAt: 2024-02-16T20:29:31.154Z
 firstPublishedAt: 2022-03-16T16:22:55.043Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 342378
 ---
 
diff --git a/docs/known-issues/en/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md b/docs/known-issues/en/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
new file mode 100644
index 000000000..62003453d
--- /dev/null
+++ b/docs/known-issues/en/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
@@ -0,0 +1,43 @@
+---
+title: 'Possible errors in Change Orders notification in the UI, API and Gateway.'
+id: 1UeG6MyFYIUVCnH8kPwNIJ
+status: PUBLISHED
+createdAt: 2023-12-19T19:37:47.313Z
+updatedAt: 2023-12-19T19:37:47.950Z
+publishedAt: 2023-12-19T19:37:47.950Z
+firstPublishedAt: 2023-12-19T19:37:47.950Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway
+locale: en
+kiStatus: Backlog
+internalReference: 955489
+---
+
+## Summary
+
+
+Some problems were identified in the Change Orders V1 architecture, where some cases were not notified in the order interaction in the UI, were not notified in the Get Orders API, however, there was a discount or increase in the value. We have also seen scenarios where the notification occurs in the UI and API, however, the discount or increase is not made at the gateway.
+
+
+##
+
+## Simulation
+
+
+It is not possible to carry out a simulation, as the scenarios are sporadic and generally occur due to a timeout error, which we have already increased the timer for.
+
+
+##
+
+## Workaround
+
+
+Initially we do not have a workaround, however, it is worth mentioning that some scenarios we will be able to adjust manually, such as if the registration of change orders occurs in the gateway and does not occur in the Marketplace or fulfillment order interaction and in the API as well.
+
+
+
+
+
diff --git a/docs/known-issues/en/presales-of-the-legacy-cms-collection-is-not-working.md b/docs/known-issues/en/presales-of-the-legacy-cms-collection-is-not-working.md
new file mode 100644
index 000000000..5c13e8060
--- /dev/null
+++ b/docs/known-issues/en/presales-of-the-legacy-cms-collection-is-not-working.md
@@ -0,0 +1,49 @@
+---
+title: 'Pre-sales of the legacy CMS collection is not working'
+id: 1bRqhWCmtckyCbYf1SQa5N
+status: PUBLISHED
+createdAt: 2023-08-22T18:51:34.059Z
+updatedAt: 2023-08-22T18:51:34.595Z
+publishedAt: 2023-08-22T18:51:34.595Z
+firstPublishedAt: 2023-08-22T18:51:34.595Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: presales-of-the-legacy-cms-collection-is-not-working
+locale: en
+kiStatus: Backlog
+internalReference: 885693
+---
+
+## Summary
+
+
+It was expected that, by selecting the pre-order checkbox, the collection would be populated with products whose release date had been filled in for a future date.
+However, this is not happening, as the collection is not populated, but always remains empty.
+
+
+##
+
+## Simulation
+
+
+
+- Set a release date on some products for a future date
+- Create a collection
+- Go to the collection admin in the legacy CMS
+- Configure the collection for pre-sale products
+- See that the collection is never populated
+
+
+##
+
+## Workaround
+
+
+Manually manage the products in the collection
+
+
+
+
+
diff --git a/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
new file mode 100644
index 000000000..f8aeb5f6a
--- /dev/null
+++ b/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -0,0 +1,52 @@
+---
+title: 'Price filter applied on top of "spot price" instead of regular price'
+id: 2EEgRV1NxYuns4eF7F0ZqD
+status: PUBLISHED
+createdAt: 2024-02-15T19:39:53.576Z
+updatedAt: 2024-02-15T19:39:54.436Z
+publishedAt: 2024-02-15T19:39:54.436Z
+firstPublishedAt: 2024-02-15T19:39:54.436Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: price-filter-applied-on-top-of-spot-price-instead-of-regular-price
+locale: en
+kiStatus: Backlog
+internalReference: 982664
+---
+
+## Summary
+
+
+Price filters are applied on top of the "spotPrice" value, which is the price for special payment conditions, instead of the item's regular price.
+
+This may affect expectations while diverging from most places, which focus on the regular price, as the shelves and cart usually do, or properties like "priceRange" from the API.
+
+
+##
+
+## Simulation
+
+
+Consider a product priced at $430 with 10% off in a specific payment method, generating a "spot price" of $387.
+
+Filtering by items with a price between $300 to $400 will return this product, which usually will be shown on the shelf as $430 (its regular price), generating the perception of divergence.
+
+In the same way, the "priceRange" property from the API will answer with the following values (considering this product as the single result for this search query), feeding the sense of divergence:
+
+    "priceRange": { "sellingPrice": { "highPrice": 430, "lowPrice": 430 }, "listPrice": { "highPrice": 430, "lowPrice": 430 }}
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md b/docs/known-issues/en/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
new file mode 100644
index 000000000..1e20f821e
--- /dev/null
+++ b/docs/known-issues/en/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
@@ -0,0 +1,43 @@
+---
+title: "Price range at the facets API doesn't correspond to the search results"
+id: 2X9Z21u9kJh55uWu6o6sP3
+status: PUBLISHED
+createdAt: 2024-03-08T22:36:43.149Z
+updatedAt: 2024-03-08T22:36:44.086Z
+publishedAt: 2024-03-08T22:36:44.086Z
+firstPublishedAt: 2024-03-08T22:36:44.086Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: price-range-at-the-facets-api-doesnt-correspond-to-the-search-results
+locale: en
+kiStatus: Backlog
+internalReference: 997121
+---
+
+## Summary
+
+
+The price ranges from the facets API ("Get list of the possible facets for a given query") may vary between returning buckets of "from" and "to" values with rounded prices and the minimum and maximum prices between the search results.
+
+While the rounded prices generate a better UX to present a list of price ranges to the shopper, it's not desired to use as a price "slider".
+
+Moreover, since the minimum and maximum prices are applied at a second moment, the price ranges as "buckets" in a search that already applies a price filter get out of bounds of bounds in relation to the specified prices.
+
+
+##
+
+## Simulation
+
+
+Using the  API, make a request with and without a price filter like "/price/100:500" and observe the returned price ranges (from/to) in the "values" object for the facet with type "PRICERANGE".
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/price-range-disregards-sales-policy.md b/docs/known-issues/en/price-range-disregards-sales-policy.md
index dd62fcb3b..fd074ea95 100644
--- a/docs/known-issues/en/price-range-disregards-sales-policy.md
+++ b/docs/known-issues/en/price-range-disregards-sales-policy.md
@@ -1,41 +1,33 @@
 ---
 title: 'Price range disregards sales policy'
-id: 4isnfk4T2UB3CId8bXcvFT
-status: DRAFT
-createdAt: 2022-03-16T16:35:57.963Z
-updatedAt: 2022-06-08T14:01:22.874Z
-publishedAt: 
-firstPublishedAt: 
+id: 3OsmwHOZyM0AQWA8CuK0aC
+status: PUBLISHED
+createdAt: 2017-10-17T17:50:40.970Z
+updatedAt: 2022-12-22T20:46:23.778Z
+publishedAt: 2022-12-22T20:46:23.778Z
+firstPublishedAt: 2017-10-17T18:03:23.731Z
 contentType: knownIssue
-productTeam: Portal
+productTeam: Marketing & Merchandising
 author: 2mXZkbi0oi061KicTExNjo
-tag: Portal
+tag: Portal (CMS)
 slug: price-range-disregards-sales-policy
 locale: en
 kiStatus: Backlog
-internalReference: 322764
+internalReference: 
 ---
 
 ## Summary
 
-
 The price range filter, which is configured from the options category, considers the price that is registered in all of the store's sales policies, which means that it will always display the lowest registered value from any sales policy, possibly displaying a product that is not in the price range of the that particular sales policy.
 
-
-
 ## Simulation
 
-
-
 1. Register different prices in different sales policies for the same SKU;
 2. Create price ranges in the category in which the registered prices have different ranges;
 3. In the sales policy of the SKU with the highest price, filter by price range
 4. Notice that the considered SKU value belongs to another sales policy, because the filter only looks at the lowest value of any policy.
 
-
-
 ## Workaround
 
-
 There is no available workaround for this scenario.
 
diff --git a/docs/known-issues/en/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md b/docs/known-issues/en/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
new file mode 100644
index 000000000..8e1f6517f
--- /dev/null
+++ b/docs/known-issues/en/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
@@ -0,0 +1,50 @@
+---
+title: 'Price Range Slider defaults to minimum value after selecting a filter'
+id: 15ABXMTT9cqieizxYWqC2V
+status: PUBLISHED
+createdAt: 2023-11-08T13:34:50.960Z
+updatedAt: 2023-11-08T13:34:51.373Z
+publishedAt: 2023-11-08T13:34:51.373Z
+firstPublishedAt: 2023-11-08T13:34:51.373Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: price-range-slider-defaults-to-minimum-value-after-selecting-a-filter
+locale: en
+kiStatus: Backlog
+internalReference: 843442
+---
+
+## Summary
+
+
+This is a price range, it is a slider and has two selectors(markers), one for min and one for max so it knows where to position itself on the slider.
+When applying a brand filter to it the selector will not move its min value to the brand min values, it will keep the default min value and the marker will appear out of the range.
+
+
+##
+
+## Simulation
+
+
+1 - Access a Category page and notice the price range filter and its min e max values.
+2- Select a filter by checking it on the left (category2/3/4)
+3- With the filter applied, notice that the price range slider will keep the min value as before and will be out of the slider range.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/RuhwOHLwbPslKpeZ4VUq4Y995/?name=image.png)
+
+Filter with the behavior as described for the min value.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md b/docs/known-issues/en/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
new file mode 100644
index 000000000..007476216
--- /dev/null
+++ b/docs/known-issues/en/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
@@ -0,0 +1,49 @@
+---
+title: 'Price swapped if the same item is in the cart twice and one is from Assembly Options'
+id: 6ASEyEYPt9wjj4eSzMqdc0
+status: PUBLISHED
+createdAt: 2024-07-24T14:51:12.922Z
+updatedAt: 2024-07-24T14:51:13.713Z
+publishedAt: 2024-07-24T14:51:13.713Z
+firstPublishedAt: 2024-07-24T14:51:13.713Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options
+locale: en
+kiStatus: Backlog
+internalReference: 1070336
+---
+
+## Summary
+
+
+If an item is added to the cart as an option (also known as child) from Assembly Options, and the same item is added to the cart as a regular item; the prices are mixed up, and each is applied to the incorrect one.
+
+For example:
+
+- Item as an option with a price of 0;
+- Item as regular with a price of 100.
+In the order, the item as the option will have the price of 100 and the regular one with the price of 0.
+
+
+##
+
+## Simulation
+
+
+
+- Add an item with an assembly option to the cart, and make sure one of the options has a different price list in the configuration;
+- Add the same item as the option.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/price-updates-with-cache-on-end-applications.md b/docs/known-issues/en/price-updates-with-cache-on-end-applications.md
new file mode 100644
index 000000000..1a0f609b6
--- /dev/null
+++ b/docs/known-issues/en/price-updates-with-cache-on-end-applications.md
@@ -0,0 +1,49 @@
+---
+title: 'Price updates with cache on end applications'
+id: 1ZDl8C3DDoACmxRqRlYDJo
+status: PUBLISHED
+createdAt: 2023-09-08T16:08:24.445Z
+updatedAt: 2023-09-08T16:08:25.900Z
+publishedAt: 2023-09-08T16:08:25.900Z
+firstPublishedAt: 2023-09-08T16:08:25.900Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: price-updates-with-cache-on-end-applications
+locale: en
+kiStatus: Backlog
+internalReference: 896520
+---
+
+## Summary
+
+
+The price modifications made on the account update almost real time on price APIs. However, checkout simulations take about 5min have the most updated price on the product due to cache. This is expected.
+
+However, on end applications such as external affiliates or marketplace integrations like google shopping the prices can, **sometimes**, be delivered wrong.
+
+This happens because the price module notifies all internal systems that the price was updated as soon as the action happens, not giving enough time for the end applications that consults checkout simulations to get the price without cache.
+
+
+##
+
+## Simulation
+
+
+
+1. Update the price on a sku;
+2. Check on the bridge logs if the price sent to marketplace integrations was the must updated one or the old value.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md
new file mode 100644
index 000000000..53fca52ef
--- /dev/null
+++ b/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -0,0 +1,42 @@
+---
+title: 'Prices restricted to "Int32" max value on Change Price API'
+id: 5mzOjCUYs7vXUkttbsK0za
+status: PUBLISHED
+createdAt: 2022-04-25T17:28:05.159Z
+updatedAt: 2024-02-16T20:26:04.281Z
+publishedAt: 2024-02-16T20:26:04.281Z
+firstPublishedAt: 2022-04-25T17:28:05.773Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: prices-restricted-to-int32-max-value-on-change-price-api
+locale: en
+kiStatus: No Fix
+internalReference: 566142
+---
+
+## Summary
+
+
+Checkout REST API Change price doesn't support prices higher than an "Int32" value. So, applying a "manual price" will be restricted up to the number "2,147,483,647" (number in decimals).
+
+
+##
+
+## Simulation
+
+
+While using the "Change price" API (https://developers.vtex.com/vtex-rest-api/reference/pricechange), sending a payload like "{"price":2500000000}" (which represents $25.000.000,00) will return a 500 error with the message "Value was either too large or too small for an Int32.".
+
+
+##
+
+## Workaround
+
+
+Use the Handle cart items API to update the price.
+
+
+
+
diff --git a/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
new file mode 100644
index 000000000..803cbd9ba
--- /dev/null
+++ b/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -0,0 +1,44 @@
+---
+title: "Prioritization by product's "keyword" not considering stopwords"
+id: 55S7nFg61dAyCeGQCIw6aK
+status: PUBLISHED
+createdAt: 2024-05-30T22:05:25.328Z
+updatedAt: 2024-05-30T22:05:26.335Z
+publishedAt: 2024-05-30T22:05:26.335Z
+firstPublishedAt: 2024-05-30T22:05:26.335Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: prioritization-by-products-keyword-not-considering-stopwords
+locale: en
+kiStatus: Backlog
+internalReference: 1041743
+---
+
+## Summary
+
+
+Products may be prioritized in the search results by their "keyword", a word from the product's name set as relevant by an algorithm. Stopwords are search terms filtered out from the original terms because it's not significant for the search.
+
+In a scenario where the keyword for a product is a stopword, this product may lose priority in the search results.
+
+
+##
+
+## Simulation
+
+
+
+- A product with the name "La vida en el oceano" will have "la" as keyword.
+- Considering a Spanish store, a search for this product name will be effectively made as "vida el oceano" after removing the stopwords.
+- Products with "vida" as a keyword will be prioritized over the searched product.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/problem-while-validating-value-field-when-buying-with-two-cards.md b/docs/known-issues/en/problem-while-validating-value-field-when-buying-with-two-cards.md
index 3252364e2..374ff99b1 100644
--- a/docs/known-issues/en/problem-while-validating-value-field-when-buying-with-two-cards.md
+++ b/docs/known-issues/en/problem-while-validating-value-field-when-buying-with-two-cards.md
@@ -3,8 +3,8 @@ title: 'Problem while validating value field when buying with two cards'
 id: 6dr0p9WQPSHLkFaSbjI9J7
 status: PUBLISHED
 createdAt: 2022-03-28T01:05:19.734Z
-updatedAt: 2022-11-25T22:06:10.550Z
-publishedAt: 2022-11-25T22:06:10.550Z
+updatedAt: 2024-07-01T18:48:07.379Z
+publishedAt: 2024-07-01T18:48:07.379Z
 firstPublishedAt: 2022-03-28T01:05:20.361Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: problem-while-validating-value-field-when-buying-with-two-cards
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 460683
 ---
 
diff --git a/docs/known-issues/en/problem-with-phone-validation-on-mobile-devices.md b/docs/known-issues/en/problem-with-phone-validation-on-mobile-devices.md
new file mode 100644
index 000000000..b1b7bbdcb
--- /dev/null
+++ b/docs/known-issues/en/problem-with-phone-validation-on-mobile-devices.md
@@ -0,0 +1,46 @@
+---
+title: 'Problem with phone validation on mobile devices'
+id: 2KpjpNZEbAZ7PFFPvMvwNA
+status: PUBLISHED
+createdAt: 2024-01-12T14:24:34.604Z
+updatedAt: 2024-01-12T14:24:56.084Z
+publishedAt: 2024-01-12T14:24:56.084Z
+firstPublishedAt: 2024-01-12T14:24:35.388Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: problem-with-phone-validation-on-mobile-devices
+locale: en
+kiStatus: Backlog
+internalReference: 964802
+---
+
+## Summary
+
+
+The phone field validation on mobile devices is not behaving as intended. When the expected number of characters is reached, the validation correctly marks the field with a check. However, when additional characters are added and then removed one by one, the validation fails to recognize that the character count is still higher than expected, incorrectly marking the entry as valid. The validation also marks inputs with fewer characters than expected as valid.
+
+
+##
+
+## Simulation
+
+
+
+1. Navigate to the checkout page by purchasing any random item.
+2. During the profile step, input a phone number until the field is validated and marked with a check.
+3. Experiment by adding more characters to the phone number and then removing them one by one, observing how the field retains the checkmark even with a reduced number of characters compared to the initial validation.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/product-availability-display-delayed-when-using-multiple-sales-channels.md b/docs/known-issues/en/product-availability-display-delayed-when-using-multiple-sales-channels.md
new file mode 100644
index 000000000..f9dc917fd
--- /dev/null
+++ b/docs/known-issues/en/product-availability-display-delayed-when-using-multiple-sales-channels.md
@@ -0,0 +1,69 @@
+---
+title: 'Product availability display delayed when using multiple sales channels'
+id: 7JluVogO4pom0l57UobYIP
+status: PUBLISHED
+createdAt: 2023-12-07T16:18:59.300Z
+updatedAt: 2023-12-07T16:19:00.098Z
+publishedAt: 2023-12-07T16:19:00.098Z
+firstPublishedAt: 2023-12-07T16:19:00.098Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-availability-display-delayed-when-using-multiple-sales-channels
+locale: en
+kiStatus: Backlog
+internalReference: 949411
+---
+
+## Summary
+
+
+The display, for legacy portal stores, of products in PLPs is based on the store's sales channel and its basic availability data.
+
+If a product has stock, price and its basic data to be properly sold in a store + it belongs to a said sales channel, this product is and should be listed in the store.
+
+However, when this said product has the option "show if unavailable" tag set a false, it should be removed from the store pages when it can't be sold.
+
+This process mostly happens efficiently, but in cases where said product is not available for a given sales channel but is for others, it can still be shown in the unintended channels.
+
+
+**Example**:
+
+1 -  Product 1 is available in the sales channels 1, 2 and 3.
+
+2 - It went out of stock in sales channel 2. It's supposed to not be shown in it anylonger.
+
+3 - Since it is still available in the channels 1 and 3, it might get "stuck" and still show for an extended time in the channel 2, despite its unavailability.
+
+*this issue only occurs when a product with the said flag = false and it goes from available to unavailable in a single sales channel whilst it is still showing on the others. Such inconsistency does not happen the other way around (going from unavailable to available).
+
+
+
+##
+
+## Simulation
+
+
+For a store with multiple sales channels and that uses different domains for each, get a product that is available in both and showing under a specific search result.
+
+This test product must have the "show even if unavailable" option set as false in it.
+
+Then, set it to out of stock in one of the sales channels.
+
+It will still be shown, even after a long time, in both domains search result, despite the unavailability in one of the channels.
+
+
+##
+
+## Workaround
+
+
+**Option A**) Perform an indexer deletion and a reindex database if your store has under 10000 products and has several items under this scenario.
+
+**Option B**) For a small set of products, remove its availability from the store altogether (make it unavailable in all sales channels) and then immediately revert these changes.
+
+
+
+
+
diff --git a/docs/known-issues/en/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md b/docs/known-issues/en/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
index 2dd9ba1e1..994e14ac5 100644
--- a/docs/known-issues/en/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
+++ b/docs/known-issues/en/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
@@ -3,8 +3,8 @@ title: 'Product availability is incorrectly showed in the pickups in cart displa
 id: 6aoRWAMSGDwcuUPvGd8bI9
 status: PUBLISHED
 createdAt: 2022-03-30T17:24:21.013Z
-updatedAt: 2022-11-25T21:53:23.560Z
-publishedAt: 2022-11-25T21:53:23.560Z
+updatedAt: 2024-02-16T20:28:45.041Z
+publishedAt: 2024-02-16T20:28:45.041Z
 firstPublishedAt: 2022-03-30T17:24:21.669Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 552875
 ---
 
diff --git a/docs/known-issues/en/product-comissioning-inconsistent-cache.md b/docs/known-issues/en/product-comissioning-inconsistent-cache.md
new file mode 100644
index 000000000..3c1d06e41
--- /dev/null
+++ b/docs/known-issues/en/product-comissioning-inconsistent-cache.md
@@ -0,0 +1,60 @@
+---
+title: 'Product Comissioning Inconsistent Cache'
+id: 7queBSJcAG9yIlKbvWOVgY
+status: PUBLISHED
+createdAt: 2023-08-01T17:48:39.144Z
+updatedAt: 2023-08-01T17:56:01.673Z
+publishedAt: 2023-08-01T17:56:01.673Z
+firstPublishedAt: 2023-08-01T17:54:19.969Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-comissioning-inconsistent-cache
+locale: en
+kiStatus: Backlog
+internalReference: 872364
+---
+
+## Summary
+
+
+There are, as of 2023, two distinct API sets to update a seller information on a marketplace, they are:
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
+https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/seller-register/pvt/sellers/-sellerId-/commissions/categories
+
+These should be consistent among themselves (and msotly, they are) but, when updating comissioning data for all categories on the latter, it takes very long to update the information on the response of the catalog_system API.
+
+This happens when the comission is set for the root category (for instance, the payload below)
+
+```
+[
+ {
+      ""categoryId"": ""default"",
+      ""categoryName"": null,
+      ""categoryFullPath"": [],
+      ""productCommissionPercentage"": 50.0,
+      ""freightCommissionPercentage"": 0.0
+  }
+]
+```
+
+The main consequence of this delay is that the checkout and marktplaces mostly use the catalog_system response, which can lead to incorrect comissions on orders.
+
+
+## Simulation
+
+1. On a marketplace, try using a GET request using the catalog API for a given seller https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/seller/-sellerId-
+2. Update its product comissioning data via a PUT to the same path https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
+3. Perform another GET and you'll see that the information was correctly updated.
+4. Now, try doing the same using the seller register API https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-/commissions
+5. Send a payload for the root category (which means for the entire store, aside from other categories with specific comissions) setting up any productComissionPercentage https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/seller-register/pvt/sellers/-sellerId-/commissions/categories
+6. If you fetch data via the GET for this same collection, you'll see the updated information: https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-/commissions
+7. However, when attempting to get this very same data vi the catalog_system API, it'll take days to update it there if you don't perform any other update.
+
+## Workaround
+
+- Setting up other data on the seller register api, which forces a cache miss.
+- Updating via the catalog_system api directly
+- Using the UI to perform updates
+
diff --git a/docs/known-issues/en/product-image-on-admin-changes-with-more-than-70-skus.md b/docs/known-issues/en/product-image-on-admin-changes-with-more-than-70-skus.md
new file mode 100644
index 000000000..9bbdafe5b
--- /dev/null
+++ b/docs/known-issues/en/product-image-on-admin-changes-with-more-than-70-skus.md
@@ -0,0 +1,49 @@
+---
+title: 'Product Image on admin changes with more than 70 skus.'
+id: 6EtUyiWzpm5moEN6hkY4B0
+status: PUBLISHED
+createdAt: 2024-03-21T15:18:20.218Z
+updatedAt: 2024-03-21T15:18:21.405Z
+publishedAt: 2024-03-21T15:18:21.405Z
+firstPublishedAt: 2024-03-21T15:18:21.405Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-image-on-admin-changes-with-more-than-70-skus
+locale: en
+kiStatus: Backlog
+internalReference: 1003966
+---
+
+## Summary
+
+
+When a product has more than 70 skus variations it's image on admin (and on admin only) changes to a information image:
+ ![](https://vtexhelp.zendesk.com/attachments/token/3oAwbW4sgou7su2F6Ls5CGqoR/?name=image.png)
+
+with the text: "ATENÇÃO: não foi possível excluir este produto porque ele tem mais SKUs do que o permitido pelo sistema."
+
+
+##
+
+## Simulation
+
+
+
+- Add more than 70 skus on a product
+- Check that the image on admin changes to the one presented before
+- Check that the product remains the same on PDP.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 656e7bbdb..972a6c506 100644
--- a/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -3,8 +3,8 @@ title: 'Product Insert/Update API allows "\n" in the textLink field.'
 id: 5TfUw5tTxBEu9HkL3ypBKw
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.325Z
-updatedAt: 2022-11-25T21:44:48.430Z
-publishedAt: 2022-11-25T21:44:48.430Z
+updatedAt: 2024-02-16T20:28:55.474Z
+publishedAt: 2024-02-16T20:28:55.474Z
 firstPublishedAt: 2022-06-28T16:55:54.138Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: product-insertupdate-api-allows-n-in-the-textlink-field
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 486459
 ---
 
diff --git a/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
new file mode 100644
index 000000000..e1e5c754f
--- /dev/null
+++ b/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -0,0 +1,46 @@
+---
+title: ""Product name contains" search with more than one term doesn't work on catalog's redesigned UI"
+id: 2kI6ab0kdpLG6m63ETGGqf
+status: PUBLISHED
+createdAt: 2024-06-05T13:38:38.836Z
+updatedAt: 2024-06-05T13:38:39.630Z
+publishedAt: 2024-06-05T13:38:39.630Z
+firstPublishedAt: 2024-06-05T13:38:39.630Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui
+locale: en
+kiStatus: Backlog
+internalReference: 1044571
+---
+
+## Summary
+
+
+On the redesigned product list in the catalog, one of the search fields is "Product name contains". Currently, when searching for a product name with more than one term, two situations can happen:
+
+- it returns any product that has any of the terms
+- it doesn't return the product with the exact name searched
+
+
+##
+
+## Simulation
+
+
+Search for a product name with two or more terms on a redesigned catalog and note that it can be returned products that contain only one of the terms
+
+
+##
+
+## Workaround
+
+
+Use the "SKU name" search or the other search options available
+
+
+
+
+
diff --git a/docs/known-issues/en/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md b/docs/known-issues/en/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
index 0b8fbaaec..954517d00 100644
--- a/docs/known-issues/en/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
+++ b/docs/known-issues/en/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
@@ -3,8 +3,8 @@ title: 'Product Name Field on XML returns Product Name + Sku Name when the produ
 id: 7sNNzBe5pLn7oigDgoCKjv
 status: PUBLISHED
 createdAt: 2022-09-19T19:06:55.572Z
-updatedAt: 2022-11-25T21:43:35.947Z
-publishedAt: 2022-11-25T21:43:35.947Z
+updatedAt: 2024-02-16T20:23:45.927Z
+publishedAt: 2024-02-16T20:23:45.927Z
 firstPublishedAt: 2022-09-19T19:06:56.137Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 661089
 ---
 
diff --git a/docs/known-issues/en/product-page-sessions-not-working.md b/docs/known-issues/en/product-page-sessions-not-working.md
new file mode 100644
index 000000000..4dadd8fb7
--- /dev/null
+++ b/docs/known-issues/en/product-page-sessions-not-working.md
@@ -0,0 +1,43 @@
+---
+title: 'Product page sessions not working'
+id: 6Hgk9lBPmrZ9byc6eeRiki
+status: PUBLISHED
+createdAt: 2024-01-04T21:34:51.613Z
+updatedAt: 2024-01-04T21:36:00.900Z
+publishedAt: 2024-01-04T21:36:00.900Z
+firstPublishedAt: 2024-01-04T21:34:52.264Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: product-page-sessions-not-working
+locale: en
+kiStatus: Backlog
+internalReference: 961591
+---
+
+## Summary
+
+
+The admin overview has some analytics information. The one about product page sessions should return the values of this event but sometimes it is returning zero
+
+
+##
+
+## Simulation
+
+
+Access the admin of the store and try to look for the product page sessions. Check if it is returning as zero
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/product-price-not-considering-default-seller-in-pdp.md b/docs/known-issues/en/product-price-not-considering-default-seller-in-pdp.md
index 25152ab56..ad09724e4 100644
--- a/docs/known-issues/en/product-price-not-considering-default-seller-in-pdp.md
+++ b/docs/known-issues/en/product-price-not-considering-default-seller-in-pdp.md
@@ -3,8 +3,8 @@ title: 'Product Price not considering default seller in PDP'
 id: 4VOIW6kCTfFZ3S9u3xtdDF
 status: PUBLISHED
 createdAt: 2022-02-23T21:52:42.520Z
-updatedAt: 2022-11-25T22:13:37.983Z
-publishedAt: 2022-11-25T22:13:37.983Z
+updatedAt: 2024-02-16T20:27:12.071Z
+publishedAt: 2024-02-16T20:27:12.071Z
 firstPublishedAt: 2022-03-07T22:34:44.879Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: product-price-not-considering-default-seller-in-pdp
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429888
 ---
 
diff --git a/docs/known-issues/en/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md b/docs/known-issues/en/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
index 4296404b5..d4e9d0e4c 100644
--- a/docs/known-issues/en/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
+++ b/docs/known-issues/en/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
@@ -3,8 +3,8 @@ title: 'Product replacement on OMS order not working on seller portal accounts'
 id: 1wQTfSR6OB6CL0sRpCYARp
 status: PUBLISHED
 createdAt: 2023-02-14T12:25:00.911Z
-updatedAt: 2023-02-14T12:25:01.506Z
-publishedAt: 2023-02-14T12:25:01.506Z
+updatedAt: 2024-07-01T18:48:50.766Z
+publishedAt: 2024-07-01T18:48:50.766Z
 firstPublishedAt: 2023-02-14T12:25:01.506Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: product-replacement-on-oms-order-not-working-on-seller-portal-accounts
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 753484
 ---
 
diff --git a/docs/known-issues/en/product-specification-export-index-out-of-range.md b/docs/known-issues/en/product-specification-export-index-out-of-range.md
index c5a9c4dbf..84840f93b 100644
--- a/docs/known-issues/en/product-specification-export-index-out-of-range.md
+++ b/docs/known-issues/en/product-specification-export-index-out-of-range.md
@@ -3,8 +3,8 @@ title: 'Product Specification Export Index Out of Range'
 id: 2Qu9QCZvfcjmNfAh3uvPkf
 status: PUBLISHED
 createdAt: 2022-02-25T12:22:04.014Z
-updatedAt: 2022-11-25T21:45:45.357Z
-publishedAt: 2022-11-25T21:45:45.357Z
+updatedAt: 2024-01-10T20:25:32.586Z
+publishedAt: 2024-01-10T20:25:32.586Z
 firstPublishedAt: 2022-02-25T12:22:04.405Z
 contentType: knownIssue
 productTeam: Catalog
@@ -19,18 +19,18 @@ internalReference: 481095
 ## Summary
 
 
-When attempting to export, using the UI: , data from product specifications, if they do not have any valid fields directly registered in the category to be exported, the process will fail with an "Index out of Range" message.
-
+When attempting to export Product Specifications from the "Import and Export" UI, if there is any null value or null relation on the category to be exported, the process will fail with an "Index out of Range" message. In other words, the category must have registered directly at its level a product field, products, and products with values associated.
 
 
 
+##
 
 ## Simulation
 
 
-1) Go to the Product SPecification export UI: ProdutoExportacaoImportacaoEspecificacaoV2.aspx
+1) Go to the Product Specification export UI: ProdutoExportacaoImportacaoEspecificacaoV2.aspx
 
-2) Right click a category in which there's no product specification field registered
+2) Right-click a category in which there's no product specification field registered
 
 3) An error message of "Index out of bonds" will be prompted.
 
@@ -38,6 +38,7 @@ When attempting to export, using the UI: , data from product specifications, if
 
 
 
+##
 
 ## Workaround
 
diff --git a/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md
new file mode 100644
index 000000000..9f5cf1481
--- /dev/null
+++ b/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -0,0 +1,46 @@
+---
+title: '"Product Specification" filter on Collection Module assuming incorrect values'
+id: 2vg3t5kp7j4Ttla53pVjck
+status: PUBLISHED
+createdAt: 2023-10-26T22:22:44.895Z
+updatedAt: 2023-10-26T22:22:45.413Z
+publishedAt: 2023-10-26T22:22:45.413Z
+firstPublishedAt: 2023-10-26T22:22:45.413Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-specification-filter-on-collection-module-assuming-incorrect-values
+locale: en
+kiStatus: Backlog
+internalReference: 926593
+---
+
+## Summary
+
+
+On the Collection Module, the Product Specifications filter is not working properly when the specification has the type "Text" and "Large Text". When this kind of specification is selected, a text box is opened to insert the possible values separated by a comma, tab, or enter. However, when typing only one character, the system assumes it as a value even without separating the terms.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a Product Specification with the type "Text"
+2. Go to Collection Module, click on the "More" filter, select "Product Specification"
+3. Localize the specification you've created and type anything, see that even one character will become a term of search
+
+
+##
+
+## Workaround
+
+
+Continue to type until the term is completed and then delete the incorrect terms
+
+
+
+
+
diff --git a/docs/known-issues/en/product-specification-filter-on-the-collection-module-does-not-list-root-category.md b/docs/known-issues/en/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
new file mode 100644
index 000000000..1f002cf70
--- /dev/null
+++ b/docs/known-issues/en/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
@@ -0,0 +1,45 @@
+---
+title: 'Product specification filter on the Collection Module does not list root category'
+id: 6ZDaMBc9G5TtuwMJ5b0nuK
+status: PUBLISHED
+createdAt: 2023-10-12T14:29:57.985Z
+updatedAt: 2023-10-12T14:29:58.698Z
+publishedAt: 2023-10-12T14:29:58.698Z
+firstPublishedAt: 2023-10-12T14:29:58.698Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-specification-filter-on-the-collection-module-does-not-list-root-category
+locale: en
+kiStatus: Backlog
+internalReference: 918687
+---
+
+## Summary
+
+
+On the collection module, when using the filters to add products, the Product Specification filter does not list the fields registered on the root category
+
+
+##
+
+## Simulation
+
+
+
+- In a collection, on the "More" option, select the Product Specification filter
+- A new field will open "Type a category"
+- Try to find the root category
+
+
+##
+
+## Workaround
+
+
+Use the other filters on the module, import the products through a spreadsheet, or add products individually on the UI
+
+
+
+
diff --git a/docs/known-issues/en/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/en/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
new file mode 100644
index 000000000..afad0b8f9
--- /dev/null
+++ b/docs/known-issues/en/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -0,0 +1,46 @@
+---
+title: "Product specification import with type 'text' does not trigger the product's indexation"
+id: 5eQB7LCCyDbVNQBQvWti33
+status: PUBLISHED
+createdAt: 2024-03-12T19:36:58.647Z
+updatedAt: 2024-03-12T19:36:59.477Z
+publishedAt: 2024-03-12T19:36:59.477Z
+firstPublishedAt: 2024-03-12T19:36:59.477Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: product-specification-import-with-type-text-does-not-trigger-the-products-indexation
+locale: en
+kiStatus: Backlog
+internalReference: 998658
+---
+
+## Summary
+
+
+When importing product specifications, the types with pre-registered values (such as Checkbox or Radio) trigger the product's indexation, but when the type is "Text" the same does not occur.
+
+
+##
+
+## Simulation
+
+
+
+- Register a field with the type text within the category
+- Import a file filled with a new value
+- Note that the value will be updated in the Admin, but the product won't be reindexed
+
+
+##
+
+## Workaround
+
+
+Configure this type of field through Admin or API
+
+
+
+
+
diff --git a/docs/known-issues/en/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md b/docs/known-issues/en/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
index c7e873192..8ebed6462 100644
--- a/docs/known-issues/en/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
+++ b/docs/known-issues/en/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
@@ -3,8 +3,8 @@ title: 'Product taxPercentage value saved by search-resolver is incorrect due to
 id: 5zalMbGTuKaxpepVEdW3Dt
 status: PUBLISHED
 createdAt: 2022-03-21T17:38:14.386Z
-updatedAt: 2022-11-25T22:12:35.742Z
-publishedAt: 2022-11-25T22:12:35.742Z
+updatedAt: 2024-02-16T20:27:03.136Z
+publishedAt: 2024-02-16T20:27:03.136Z
 firstPublishedAt: 2022-03-21T17:38:14.760Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 470143
 ---
 
diff --git a/docs/known-issues/en/products-not-being-correctly-matched-when-the-productname-contains-numbers.md b/docs/known-issues/en/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
index 5611d38d5..ffc48ad61 100644
--- a/docs/known-issues/en/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
+++ b/docs/known-issues/en/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
@@ -3,8 +3,8 @@ title: 'Products not being correctly matched when the productName contains numbe
 id: 7Kr0VtRScH54j04Rh2uuOj
 status: PUBLISHED
 createdAt: 2023-03-01T18:55:20.183Z
-updatedAt: 2023-03-01T18:55:20.910Z
-publishedAt: 2023-03-01T18:55:20.910Z
+updatedAt: 2023-10-19T12:08:30.076Z
+publishedAt: 2023-10-19T12:08:30.076Z
 firstPublishedAt: 2023-03-01T18:55:20.910Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: products-not-being-correctly-matched-when-the-productname-contains-numbers
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 762525
 ---
 
diff --git a/docs/known-issues/en/products-showing-flag-and-discount-after-promotion-ended.md b/docs/known-issues/en/products-showing-flag-and-discount-after-promotion-ended.md
new file mode 100644
index 000000000..504a8ddbf
--- /dev/null
+++ b/docs/known-issues/en/products-showing-flag-and-discount-after-promotion-ended.md
@@ -0,0 +1,42 @@
+---
+title: 'Products showing flag and discount after promotion ended'
+id: 21qXD9XIfaxsxCH4jMGLJX
+status: PUBLISHED
+createdAt: 2024-06-07T19:50:09.302Z
+updatedAt: 2024-06-07T19:50:10.154Z
+publishedAt: 2024-06-07T19:50:10.154Z
+firstPublishedAt: 2024-06-07T19:50:10.154Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: products-showing-flag-and-discount-after-promotion-ended
+locale: en
+kiStatus: Backlog
+internalReference: 383911
+---
+
+## Summary
+
+
+Sometimes promotion flags and discounts are displayed on PLP and PLP after the promotion's expiration date. This happens because the promotion doesn't trigger the product indexation, resulting in the wrong exhibition of the discount.
+
+
+##
+
+## Simulation
+
+
+1- Create a promotion with a flag
+2- Set an expiration date
+3- Check that the promotion continues to be active on PLP and PDP
+
+
+
+##
+
+## Workaround
+
+
+Reindex the products included in the promotion
+
diff --git a/docs/known-issues/en/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md b/docs/known-issues/en/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
new file mode 100644
index 000000000..0486827e9
--- /dev/null
+++ b/docs/known-issues/en/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
@@ -0,0 +1,42 @@
+---
+title: 'Products with price zero shown as unavailable at Intelligent Search'
+id: 4oh4ROvCp7JrfWeSAc0dE0
+status: PUBLISHED
+createdAt: 2024-06-05T23:34:05.987Z
+updatedAt: 2024-06-05T23:34:07.147Z
+publishedAt: 2024-06-05T23:34:07.147Z
+firstPublishedAt: 2024-06-05T23:34:07.147Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: products-with-price-zero-shown-as-unavailable-at-intelligent-search
+locale: en
+kiStatus: Backlog
+internalReference: 1045184
+---
+
+## Summary
+
+
+Products with price zero are shown as unavailable by the Intelligent Search. Different from a product with no registered price, the price set as zero defines a free product.
+
+
+##
+
+## Simulation
+
+
+It's possible to simulate the scenario just by changing its price to "$ 0,00". It'll affect the frontend for search results and the APIs.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md b/docs/known-issues/en/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
new file mode 100644
index 000000000..45c20b64d
--- /dev/null
+++ b/docs/known-issues/en/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
@@ -0,0 +1,48 @@
+---
+title: 'Products with sku variations approved on Received Skus are being created with duplicated skus on the Catalog.'
+id: 2RqrBOeHDBZmfmqe6Rowl2
+status: PUBLISHED
+createdAt: 2023-08-29T15:50:44.042Z
+updatedAt: 2023-08-29T15:50:44.976Z
+publishedAt: 2023-08-29T15:50:44.976Z
+firstPublishedAt: 2023-08-29T15:50:44.976Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog
+locale: en
+kiStatus: Backlog
+internalReference: 889676
+---
+
+## Summary
+
+
+The seller can send a product with multiple sku variations.
+On the marketplace's Received Skus module these skus will appear separately to be approved.
+The merchant can manually approve these skus.
+
+The scenario happening is that some of the skus are being created duplicated on the marketplace's catalog due to a fail on the catalog communication.
+
+
+##
+
+## Simulation
+
+
+Approve skus on the Received Skus pending area from the same product in short interval of time.
+Check in the catalog if some sku was created duplicated
+
+
+##
+
+## Workaround
+
+
+Approve slowly the skus from the same product to avoid errors on the catalog side.
+
+
+
+
+
diff --git a/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
new file mode 100644
index 000000000..4be51a718
--- /dev/null
+++ b/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -0,0 +1,45 @@
+---
+title: 'Products with "unitMultiplier" wrongly flagged as "with promotion" for search filters'
+id: 2rCi8K01DHsNuYsefE7oR2
+status: PUBLISHED
+createdAt: 2024-02-15T22:52:17.434Z
+updatedAt: 2024-02-15T22:52:18.189Z
+publishedAt: 2024-02-15T22:52:18.189Z
+firstPublishedAt: 2024-02-15T22:52:18.189Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters
+locale: en
+kiStatus: Backlog
+internalReference: 982830
+---
+
+## Summary
+
+
+A product whose selling price is lower than its list price will be flagged as being part of a promotion for search filtering purposes. Products with some unit multiplier may result in a wrong calculation that can affect this comparison, resulting in them wrongly receiving this flag.
+
+
+##
+
+## Simulation
+
+
+The simulation depends on the occurrence of specific rounding issues, but an example of that is a product with a list price and regular price of $264.20 and a unit multiplier of 3.07.
+
+Although the list price and regular price are the same, this item will be returned in the search filter "promotion=yes".
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md b/docs/known-issues/en/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
index 037453d30..c92d9c68f 100644
--- a/docs/known-issues/en/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
+++ b/docs/known-issues/en/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
@@ -3,8 +3,8 @@ title: 'Products without stock on whitelabel sellers are appearing in the end of
 id: 5WCKWky2gKGTZyp9ydnFnL
 status: PUBLISHED
 createdAt: 2022-04-20T15:52:50.807Z
-updatedAt: 2022-11-25T21:57:51.904Z
-publishedAt: 2022-11-25T21:57:51.904Z
+updatedAt: 2024-07-01T18:48:10.012Z
+publishedAt: 2024-07-01T18:48:10.012Z
 firstPublishedAt: 2022-04-20T15:52:51.421Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 495741
 ---
 
diff --git a/docs/known-issues/en/productsku-upload-form-allows-utf16-format-uploaddownload.md b/docs/known-issues/en/productsku-upload-form-allows-utf16-format-uploaddownload.md
index c86635453..861eddd45 100644
--- a/docs/known-issues/en/productsku-upload-form-allows-utf16-format-uploaddownload.md
+++ b/docs/known-issues/en/productsku-upload-form-allows-utf16-format-uploaddownload.md
@@ -3,8 +3,8 @@ title: 'Product/SKU upload form allows UTF-16 format upload/download'
 id: 3NSxmGXvgFKHd2C4v2EwWV
 status: PUBLISHED
 createdAt: 2022-06-08T20:04:18.508Z
-updatedAt: 2022-11-25T22:12:28.497Z
-publishedAt: 2022-11-25T22:12:28.497Z
+updatedAt: 2024-02-16T20:26:55.864Z
+publishedAt: 2024-02-16T20:26:55.864Z
 firstPublishedAt: 2022-06-08T20:04:19.062Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: productsku-upload-form-allows-utf16-format-uploaddownload
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 493402
 ---
 
diff --git a/docs/known-issues/en/productsskus-import-does-not-support-lb.md b/docs/known-issues/en/productsskus-import-does-not-support-lb.md
index f09f8ddad..9f4cea0dc 100644
--- a/docs/known-issues/en/productsskus-import-does-not-support-lb.md
+++ b/docs/known-issues/en/productsskus-import-does-not-support-lb.md
@@ -3,8 +3,8 @@ title: "Products&SKUs Import does not support 'lb'"
 id: 1OjtnFf9MpY1IFzQa8Ua2t
 status: PUBLISHED
 createdAt: 2022-06-17T19:38:17.726Z
-updatedAt: 2023-01-05T20:03:49.367Z
-publishedAt: 2023-01-05T20:03:49.367Z
+updatedAt: 2024-02-16T20:29:45.337Z
+publishedAt: 2024-02-16T20:29:45.337Z
 firstPublishedAt: 2022-06-17T19:38:18.052Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: productsskus-import-does-not-support-lb
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 337860
 ---
 
diff --git a/docs/known-issues/en/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md b/docs/known-issues/en/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
new file mode 100644
index 000000000..3293a636a
--- /dev/null
+++ b/docs/known-issues/en/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
@@ -0,0 +1,47 @@
+---
+title: "Profile data loaded empty in the UI for complete profile with 'ignoreProfileData'"
+id: 10B1QKgN42sjapDEALmKOp
+status: PUBLISHED
+createdAt: 2024-04-15T11:41:06.841Z
+updatedAt: 2024-04-15T11:41:07.691Z
+publishedAt: 2024-04-15T11:41:07.691Z
+firstPublishedAt: 2024-04-15T11:41:07.691Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata
+locale: en
+kiStatus: Backlog
+internalReference: 1016582
+---
+
+## Summary
+
+
+When setting 'ignoreProfileData' via API Ignore profile data on checkout, if the shopper has a complete profile but is not logged in, the data will be loaded empty in the UI.
+
+
+##
+
+## Simulation
+
+
+
+- Send the ignoreProfileData via API Ignore profile data on checkout;
+- Add an item to the cart;
+- Add an email with a complete profile; no data will be loaded and it'll require login.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/jVk0tmcR7R4BmaEkDcCedJgBP/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md b/docs/known-issues/en/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
new file mode 100644
index 000000000..dada6b651
--- /dev/null
+++ b/docs/known-issues/en/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
@@ -0,0 +1,46 @@
+---
+title: 'Promotion item will not show splitted after adding client preferences data'
+id: 3bme5oDKxbRyQzozUP6XNp
+status: PUBLISHED
+createdAt: 2023-06-12T20:09:11.042Z
+updatedAt: 2024-01-31T15:20:39.646Z
+publishedAt: 2024-01-31T15:20:39.646Z
+firstPublishedAt: 2023-06-12T20:09:11.600Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: promotion-item-will-not-show-splitted-after-adding-client-preferences-data
+locale: en
+kiStatus: Backlog
+internalReference: 842575
+---
+
+## Summary
+
+
+When applying a More for Less promotion, the expected behavior is to separate the promotional item from the regular items, but the items will be grouped after adding client preferences data.
+
+Depending on the moment the client preferences data is added, it creates an inconsistent experience for the client in the cart, or the order is created with items grouped.
+
+
+##
+
+## Simulation
+
+
+
+- Add items to the cart to get a free or discounted one (the promotion and regular items will be splitted);
+- Add client preferences data to the orderForm (the items will be grouped).
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md b/docs/known-issues/en/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
new file mode 100644
index 000000000..8324fc276
--- /dev/null
+++ b/docs/known-issues/en/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
@@ -0,0 +1,44 @@
+---
+title: 'Promotion subscription with week, month and day frequency not working on recurring cycles'
+id: 70DNIBLC5kctaFZSLooOQ7
+status: PUBLISHED
+createdAt: 2024-01-12T17:00:50.068Z
+updatedAt: 2024-06-20T14:26:39.099Z
+publishedAt: 2024-06-20T14:26:39.099Z
+firstPublishedAt: 2024-01-12T17:00:50.823Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles
+locale: en
+kiStatus: Backlog
+internalReference: 965484
+---
+
+## Summary
+
+
+When a subscription promotion is set in the subscription module, the merchant has the possibility of choosing the frequency this promo will apply on the subscription.
+
+If the frequency chosen is "week" or "day" or "month" the promotion will not apply on the recurring cycles, despite the setup.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a subscription promotion that applies on the first and recurring cycles;
+2. Select the week/day/month frequency
+3. Check that the recurring orders do not have the subscription applied.
+
+
+##
+
+## Workaround
+
+
+-
+
diff --git a/docs/known-issues/en/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md b/docs/known-issues/en/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
new file mode 100644
index 000000000..af2e489be
--- /dev/null
+++ b/docs/known-issues/en/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
@@ -0,0 +1,52 @@
+---
+title: 'Promotional price table in large shopping carts can impact performance or lead to timeout errors'
+id: 22H47mc9qYLdzk2sFkbBut
+status: PUBLISHED
+createdAt: 2023-12-07T15:47:28.360Z
+updatedAt: 2023-12-07T15:57:49.789Z
+publishedAt: 2023-12-07T15:57:49.789Z
+firstPublishedAt: 2023-12-07T15:47:28.972Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors
+locale: en
+kiStatus: Backlog
+internalReference: 949389
+---
+
+## Summary
+
+
+
+When we have a store with promotional price tables created and large shopping carts applying the promotions, it causes slows in the performance of the purchase and leads to timeout errors in the cart.
+
+Any actions on the cart can trigger errors, such as adding items, editions, input zip code, etc will compromise the performance of the purchase.
+
+We cannot know for precise which number of promotional price tables being calculated in the cart or the quantity of items added in the cart will start triggering the timeout errors or slowing down the performance, from what was analyzed it can happen with any significant amount.
+
+
+
+##
+
+## Simulation
+
+
+
+Create multiple promotional price tables and a shopping cart with many items (here we cannot point a clear number, such as 50 or 100, it depends on the promotions)
+
+
+##
+
+## Workaround
+
+
+
+Unfortunately, we do not have any workarounds for this,
+deactivating the promotions and using the price module to insert the prices would help.
+
+
+
+
+
diff --git a/docs/known-issues/en/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md b/docs/known-issues/en/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
new file mode 100644
index 000000000..e769b2150
--- /dev/null
+++ b/docs/known-issues/en/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
@@ -0,0 +1,44 @@
+---
+title: "Promotions and taxes restricted by shipping method doesn't works for Whitelabel Sellers"
+id: 3ue1kZdbX1mMFqPCkl0tC4
+status: PUBLISHED
+createdAt: 2023-08-09T13:25:02.168Z
+updatedAt: 2023-08-09T13:26:13.874Z
+publishedAt: 2023-08-09T13:26:13.874Z
+firstPublishedAt: 2023-08-09T13:25:02.698Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers
+locale: en
+kiStatus: Backlog
+internalReference: 315485
+---
+
+## Summary
+
+
+Promotions and taxes restricted by shipping methods don't work for Whitelabel Sellers. They won't be applied in the simulation request (used for the cart and checkout) because the marketplace request doesn't specify the `selectedSla`, and so their values won't be presented to the user.
+
+But the order creation process will send this `selectedSla`, where the promotion/tax will be calculated and the values will change. But the divergence between the simulation and the order creation process can block the purchase from being finished since the customer will pay a value, calculated on the simulation request, different than the value calculated on the order creation.
+
+
+##
+
+## Simulation
+
+
+- create a tax in the Whitelabel Seller that is restricted to some shipping method
+- create a cart in the marketplace that will use this seller, and select the shipping method specified before
+
+The value won't be presented and the order can't be created.
+
+
+##
+
+## Workaround
+
+
+There's no known workaround to have a tax or promotion restricted by shipping method in a Whitelabel seller.
+
diff --git a/docs/known-issues/en/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md b/docs/known-issues/en/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
index fa6be455f..b0289609e 100644
--- a/docs/known-issues/en/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
+++ b/docs/known-issues/en/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
@@ -3,8 +3,8 @@ title: 'Promotions by order of payment methods do not appear on the product page
 id: HZ5IoCFFOhuxU0jQWkMPp
 status: PUBLISHED
 createdAt: 2019-08-13T20:45:50.232Z
-updatedAt: 2023-03-31T15:44:56.958Z
-publishedAt: 2023-03-31T15:44:56.958Z
+updatedAt: 2024-07-01T18:48:59.282Z
+publishedAt: 2024-07-01T18:48:59.282Z
 firstPublishedAt: 2019-08-13T21:10:58.244Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 781523
 ---
 
diff --git a/docs/known-issues/en/promotions-microrounding-divergence.md b/docs/known-issues/en/promotions-microrounding-divergence.md
new file mode 100644
index 000000000..73ad6c8bc
--- /dev/null
+++ b/docs/known-issues/en/promotions-microrounding-divergence.md
@@ -0,0 +1,95 @@
+---
+title: 'Promotions microrounding divergence'
+id: 603ZTMtdgi9olc6UiWLfmX
+status: PUBLISHED
+createdAt: 2023-12-22T18:48:32.438Z
+updatedAt: 2023-12-22T18:48:33.176Z
+publishedAt: 2023-12-22T18:48:33.176Z
+firstPublishedAt: 2023-12-22T18:48:33.176Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: promotions-microrounding-divergence
+locale: en
+kiStatus: Backlog
+internalReference: 957369
+---
+
+## Summary
+
+
+The promotions module rounds discounts in up to 3 significative digits, which can, in very specific scenarios, amount to slight divergences in the final price of a cart.
+
+For instance, let's say we have the following, example scenario:
+
+Item 1 - $10
+Item 2 - $20
+Item 3 - $32
+____________
+Total - $62
+
+And 2 promotions applying in all of them:
+
+Promotion A - $15 OFF
+Promotion B - 10% OFF.
+
+
+Usually, the discount to be calculated is sequential, with the nominal value off coming first:
+
+$62 - $15 = $47
+Then
+$47 * 0.9 = $42.3
+
+
+However, the discounts are distributed, even for the nominal discount, proportionally in the cart, so what really happens is:
+
+`item 1`:
+Original value = $10
+Nominal discount (15 * 10/62 of the cart) = -$2.41935484
+Percentual expected discount (12.5806452 * 0.9) = -$1.25806452
+Percentual real discount = -$1.258
+
+`item 2`:
+Original value = $20
+Nominal discount (15 * 20/62 of the cart) = -$4.83870968
+Percentual expected discount (15.1612903 * 0.9) = -$1.51612903
+Percentual real discount = -$1.516
+
+`item 3`:
+Original value = $32
+Nominal discount (15 * 32/62 of the cart) = -$7.74193548
+Percentual expected discount (24.2580645 * 0.9) = -$2.42580645
+Percentual real discount = -$2.426
+
+
+🔎 total diference: 0.00006452 + 0.000012903 + 0.000019355 = 0.0000270973
+
+We can see, above, that a "micro" difference was created.
+
+If, several items were added, with distinct prices, to this example cart, this difference could amount to 1 cent (0.01) or more.
+
+
+
+##
+
+## Simulation
+
+
+There are a multitude of ways to eventually recreate the case Fortunately, all of them are extremely specific.
+
+Given that, it's hard to replicate the issue, but, mostly, it's necesary to create a cart with several (~10+) different items and all of them with 2+ promotions, ideally, one of them being a nominal discount and the other one, a percentual discount.
+
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/en/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md b/docs/known-issues/en/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
new file mode 100644
index 000000000..461a3c19c
--- /dev/null
+++ b/docs/known-issues/en/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
@@ -0,0 +1,39 @@
+---
+title: 'Promotions resulting in wrong sorting/filtering by price or discount'
+id: 1qGJByINC3S7ibgiQccVcY
+status: PUBLISHED
+createdAt: 2023-08-28T17:51:44.627Z
+updatedAt: 2023-11-10T18:19:30.796Z
+publishedAt: 2023-11-10T18:19:30.796Z
+firstPublishedAt: 2023-08-28T17:55:21.450Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: authors_84
+tag: Intelligent Search
+slug: promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount
+locale: en
+kiStatus: Backlog
+internalReference: 888304
+---
+
+## Summary
+
+Product lists and search results may be badly sorted/filtered while using sorting or filtering by price or discount if there are outdated item prices at the index level, even if the storefront is showing the right price.
+
+The sorting for products is always based on previously indexed information (cold data), while the storefront usually recalculates all the information in runtime (hot data), so the presented prices are always correct in relation to the cart.
+
+It is expected every price change (and even other changes) will enqueue items to be reindexed so the index is up to date with the new conditions. The issue is that the Promotions module doesn't support sending notifications to the indexing service when a promotion begins or finishes, occasionally resulting in outdated items' prices, where the Search module isn't able to sort/filter the items correctly in comparison to real-time prices.
+
+Any action that reindexes the item's commercial conditions (like stock changes) will also organically update its price considering the promotion, eventually masking the issue for some items.
+
+Stores using `simulationBehavior=skip` won't see divergences between items sorting and applied filters in the PLP, as this parameter results in rendering the "cold data" there, but they'll appear while comparing the same item in the PLP with its PDP, which fixedly works like a `simulationBehavior=default`, retrieving updated information in runtime.
+
+
+## Simulation
+
+The easiest way to see the effects of this issue is to have a list of products sorted by lowest price, create a promotion for a product in the middle of the list, and watch its sorting not change after enabling the promotion, even when it gets cheaper than other products.
+
+## Workaround
+
+N/A
+
diff --git a/docs/known-issues/en/promotions-ui-loading-wrong-currency-information.md b/docs/known-issues/en/promotions-ui-loading-wrong-currency-information.md
index fb2458a11..b11aab39c 100644
--- a/docs/known-issues/en/promotions-ui-loading-wrong-currency-information.md
+++ b/docs/known-issues/en/promotions-ui-loading-wrong-currency-information.md
@@ -3,8 +3,8 @@ title: 'Promotions UI loading wrong currency information'
 id: 7liSZOtS1Hs2P84bXzRrG9
 status: PUBLISHED
 createdAt: 2022-12-19T14:41:51.129Z
-updatedAt: 2022-12-19T14:41:51.903Z
-publishedAt: 2022-12-19T14:41:51.903Z
+updatedAt: 2024-02-15T12:11:06.893Z
+publishedAt: 2024-02-15T12:11:06.893Z
 firstPublishedAt: 2022-12-19T14:41:51.903Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,14 +12,13 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: promotions-ui-loading-wrong-currency-information
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 718908
 ---
 
 ## Summary
 
 
-
 When opening the Promotions module very quickly and many times in a row a wrong behavior appears on the UI.
 
 The field "Restrict this promotion to seller products" does not load the correct placeholder, instead loads the placeholder "GLOBAL SELECT-A-SELLER..."
@@ -34,7 +33,6 @@ When Saving the promotion the final value is not the one expected by the client.
 ## Simulation
 
 
-
 There is not an easy way to reproduce this scenario. Sometimes, when opening the promotions module in different tabs very quickly the behavior happens.
 Check if the field "Restrict this promotion to seller products" is different to know you've reached the scenario.
 
@@ -44,6 +42,9 @@ Check if the field "Restrict this promotion to seller products" is different to
 ## Workaround
 
 
-
 Close the current promotions UI and open a new one where the behavior is not happening.
 
+
+
+
+
diff --git a/docs/known-issues/en/property-blockclass-from-infocard-not-working.md b/docs/known-issues/en/property-blockclass-from-infocard-not-working.md
index 17cd7406e..bd5f4137a 100644
--- a/docs/known-issues/en/property-blockclass-from-infocard-not-working.md
+++ b/docs/known-issues/en/property-blockclass-from-infocard-not-working.md
@@ -3,8 +3,8 @@ title: 'Property blockClass from infoCard not working'
 id: LTEEWCaZx2unBWSEJFDw6
 status: PUBLISHED
 createdAt: 2023-01-31T19:02:03.835Z
-updatedAt: 2023-01-31T19:02:04.299Z
-publishedAt: 2023-01-31T19:02:04.299Z
+updatedAt: 2024-07-01T18:48:42.227Z
+publishedAt: 2024-07-01T18:48:42.227Z
 firstPublishedAt: 2023-01-31T19:02:04.299Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: property-blockclass-from-infocard-not-working
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 743730
 ---
 
diff --git a/docs/known-issues/en/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md b/docs/known-issues/en/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
new file mode 100644
index 000000000..95de6e42c
--- /dev/null
+++ b/docs/known-issues/en/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
@@ -0,0 +1,44 @@
+---
+title: 'Proportional shipping costs shows negative values when there are promotion that split items and free shipping applied'
+id: 60gzoaN1WQC6OsEymBPdeq
+status: PUBLISHED
+createdAt: 2023-09-28T22:29:39.597Z
+updatedAt: 2023-09-28T22:33:53.751Z
+publishedAt: 2023-09-28T22:33:53.751Z
+firstPublishedAt: 2023-09-28T22:29:40.382Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied
+locale: en
+kiStatus: Backlog
+internalReference: 909925
+---
+
+## Summary
+
+
+When using promotions that split items, such as the "More for Less" type, proportional shipping costs may display negative values.
+
+This issue is visible when the "More for Less" discount is applied by the seller, and a free shipping promotion is applied by the marketplace, resulting in a discount being given. This behavior causes an infinite loop when attempting to complete a purchase.
+
+
+##
+
+## Simulation
+
+
+There may be different combinations causing the issue since the weight is used to calculate the proportional shipping costs, making it hard to reproduce.
+
+
+##
+
+## Workaround
+
+
+Configure the free shipping promotion to be applied by the seller.
+
+
+
+
diff --git a/docs/known-issues/en/pt-message-is-shown-in-the-license-manager-module.md b/docs/known-issues/en/pt-message-is-shown-in-the-license-manager-module.md
index 9e6f3da87..ec534d94f 100644
--- a/docs/known-issues/en/pt-message-is-shown-in-the-license-manager-module.md
+++ b/docs/known-issues/en/pt-message-is-shown-in-the-license-manager-module.md
@@ -3,8 +3,8 @@ title: 'PT message is shown in the License Manager module'
 id: 6nC0EfB2pO2pIyH9HEDDAP
 status: PUBLISHED
 createdAt: 2022-07-19T19:02:51.412Z
-updatedAt: 2022-11-25T21:57:09.655Z
-publishedAt: 2022-11-25T21:57:09.655Z
+updatedAt: 2024-07-01T18:48:30.289Z
+publishedAt: 2024-07-01T18:48:30.289Z
 firstPublishedAt: 2022-07-19T19:02:52.298Z
 contentType: knownIssue
 productTeam: Identity
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Identity
 slug: pt-message-is-shown-in-the-license-manager-module
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 620782
 ---
 
diff --git a/docs/known-issues/en/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md b/docs/known-issues/en/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
index e94a3ba9a..5a7d37f81 100644
--- a/docs/known-issues/en/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
+++ b/docs/known-issues/en/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
@@ -3,8 +3,8 @@ title: '/pub/portal/pagetype not mapping correctly when 2+ categories have the s
 id: 7ykvMnWt3PhGAqWhEFmnp3
 status: PUBLISHED
 createdAt: 2022-03-18T15:40:04.430Z
-updatedAt: 2022-11-25T22:10:11.690Z
-publishedAt: 2022-11-25T22:10:11.690Z
+updatedAt: 2024-02-16T20:27:59.429Z
+publishedAt: 2024-02-16T20:27:59.429Z
 firstPublishedAt: 2022-03-18T15:40:04.877Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 314551
 ---
 
diff --git a/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
new file mode 100644
index 000000000..577ac9f00
--- /dev/null
+++ b/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -0,0 +1,45 @@
+---
+title: "Purchase can't be finished and is stuck on "freight type has changed""
+id: mgewQ8QmZ3V3dkc7vdJkV
+status: PUBLISHED
+createdAt: 2023-09-25T13:28:28.121Z
+updatedAt: 2024-03-27T14:37:54.335Z
+publishedAt: 2024-03-27T14:37:54.335Z
+firstPublishedAt: 2023-09-25T13:28:28.557Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed
+locale: en
+kiStatus: Backlog
+internalReference: 449341
+---
+
+## Summary
+
+
+When using any promotion that cause an item split and any two different sellers are selected , clicking 'Buy Now' will display the message 'freight type has changed,' preventing the purchase from being completed.
+
+
+##
+
+## Simulation
+
+
+
+- Configure a "more for less" promotion for example;
+- Add to the cart the item from the promotion;
+- Add another item from another seller;
+- Try to finish the purchase; the message "freight type has changed" will be shown.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/put-price-overwrites-kit-price-logic.md b/docs/known-issues/en/put-price-overwrites-kit-price-logic.md
index 9410e5bb2..afcf6ea6f 100644
--- a/docs/known-issues/en/put-price-overwrites-kit-price-logic.md
+++ b/docs/known-issues/en/put-price-overwrites-kit-price-logic.md
@@ -3,8 +3,8 @@ title: 'Put Price Overwrites KIT Price Logic'
 id: 6eUXEJkxQUl6NCiFWrIiFw
 status: PUBLISHED
 createdAt: 2022-06-28T16:56:02.848Z
-updatedAt: 2022-11-25T22:12:23.543Z
-publishedAt: 2022-11-25T22:12:23.543Z
+updatedAt: 2023-11-09T13:43:40.623Z
+publishedAt: 2023-11-09T13:43:40.623Z
 firstPublishedAt: 2022-06-28T16:56:03.203Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -19,12 +19,35 @@ internalReference: 404486
 ## Summary
 
 
+The KIT price composition should be based upon the calculation of it's components and their quantities.
+
+That is, a KIT's price should be:
+`SKU_KIT_Price= (component_1*qty_1) + (component_2*qty_2) + (...) + (component_n*qty_n)`
+
+However, there is currently a way to bypass this logic if the user insert a PUT Price directly on the kit sku on the Pricing Module.
+
+
+
+##
 
 ## Simulation
 
 
 
+1. Create a KIT with at least 2 components and set their price and quantities;
+2. Check that the KIT price is set according to their logic mentioned above.
+3. Update the KIT price on the pricing module by inserting a PUT Price on the kit sku;
+4. Check that even when updating the price components and their quantities, the KIT price will remain as the put price set before.
+
+
+##
+
 ## Workaround
 
 
+Make any changes in the components, a new PUT Price with the new calculation and the correct logic will overwrite it again, then normalizing the "wrong" behavior.
+
+
+
+
 
diff --git a/docs/known-issues/en/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md b/docs/known-issues/en/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
index a9d6b6b3d..2c71eed77 100644
--- a/docs/known-issues/en/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
+++ b/docs/known-issues/en/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
@@ -3,8 +3,8 @@ title: "Quantity selector component doesn't return to the limit value when user
 id: 4QRAzY1A0UD8hOUEkxAawz
 status: PUBLISHED
 createdAt: 2022-09-16T16:27:15.880Z
-updatedAt: 2022-11-25T22:13:30.254Z
-publishedAt: 2022-11-25T22:13:30.254Z
+updatedAt: 2024-02-16T20:28:10.783Z
+publishedAt: 2024-02-16T20:28:10.783Z
 firstPublishedAt: 2022-09-16T16:27:16.745Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 659909
 ---
 
diff --git a/docs/known-issues/en/quantity-selector-wont-let-me-change-the-value-by-typing.md b/docs/known-issues/en/quantity-selector-wont-let-me-change-the-value-by-typing.md
new file mode 100644
index 000000000..37d5e967b
--- /dev/null
+++ b/docs/known-issues/en/quantity-selector-wont-let-me-change-the-value-by-typing.md
@@ -0,0 +1,48 @@
+---
+title: "Quantity Selector won't let me change the value by typing"
+id: 4whARKlTiLQhTluJrIRfO5
+status: PUBLISHED
+createdAt: 2024-06-28T15:01:34.187Z
+updatedAt: 2024-07-05T16:17:08.672Z
+publishedAt: 2024-07-05T16:17:08.672Z
+firstPublishedAt: 2024-06-28T15:01:35.225Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: quantity-selector-wont-let-me-change-the-value-by-typing
+locale: en
+kiStatus: Fixed
+internalReference: 1057544
+---
+
+## Summary
+
+
+The quantity selector component on Faststore is presenting a bug. If the minimum value of a product is 10 and I want to type 15, the selector won't let me delete the 0 because it will let us with 1, and it would be a lower value than the minimum quantity. If I want to type 15 I need to type 150 and then I can delete the 0.
+
+
+##
+
+## Simulation
+
+
+You can test it on our default store on our documentation page:
+https://developers.vtex.com/docs/guides/faststore/molecules-quantity-selector
+https://starter.vtex.app/handmade-plastic-chips-9009169/p
+
+In this case, the minimum value is 1 and the maximum value is 10.
+Try typing 2 by deleting the 1 value, it won't let you because once you delete the 1, the value will be lesser than the minimum value.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md b/docs/known-issues/en/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
index 338a32eaf..263a277ea 100644
--- a/docs/known-issues/en/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
+++ b/docs/known-issues/en/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
@@ -3,8 +3,8 @@ title: "Quantity-selector on stepper mode doesn't refresh after reaching max ava
 id: 77bK8oIAPR8LEMtOn6QEqs
 status: PUBLISHED
 createdAt: 2022-12-23T12:20:23.568Z
-updatedAt: 2022-12-23T12:20:24.148Z
-publishedAt: 2022-12-23T12:20:24.148Z
+updatedAt: 2024-02-16T20:27:43.811Z
+publishedAt: 2024-02-16T20:27:43.811Z
 firstPublishedAt: 2022-12-23T12:20:24.148Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 704458
 ---
 
diff --git a/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index 2276fbfca..5ada9f921 100644
--- a/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -21,7 +21,7 @@ internalReference:
 At present, the possibility to display the "Receive | Pick up" options is subject to a CEP (ZIP code) search in any of the tabs. This means that, if for example you would search for a ZIP code that doesn't offer the pick-up point option in the "Receive" tab, the "Pick-up" tab would not be displayed.
 
 
-![Captura de Tela 2018-11-21 às 14.25.40](https://images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
+![Captura de Tela 2018-11-21 às 14.25.40](//images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
 
 ## Simulation
 
diff --git a/docs/known-issues/en/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md b/docs/known-issues/en/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
index 9027c6639..e857555e8 100644
--- a/docs/known-issues/en/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
+++ b/docs/known-issues/en/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
@@ -3,8 +3,8 @@ title: "Received Skus: Association approvals don't add the seller's available sa
 id: 5ob4jquCm8l84MhX6285h8
 status: PUBLISHED
 createdAt: 2022-04-18T17:15:41.091Z
-updatedAt: 2023-05-09T19:06:08.893Z
-publishedAt: 2023-05-09T19:06:08.893Z
+updatedAt: 2024-02-16T20:25:58.313Z
+publishedAt: 2024-02-16T20:25:58.313Z
 firstPublishedAt: 2022-04-18T17:15:41.436Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 562472
 ---
 
diff --git a/docs/known-issues/en/received-skus-filter-do-not-work-with-special-characters.md b/docs/known-issues/en/received-skus-filter-do-not-work-with-special-characters.md
new file mode 100644
index 000000000..d37541734
--- /dev/null
+++ b/docs/known-issues/en/received-skus-filter-do-not-work-with-special-characters.md
@@ -0,0 +1,49 @@
+---
+title: 'Received Skus filter do not work with special characters'
+id: 6aSErtF2Xv5RuKuIHUEEPg
+status: PUBLISHED
+createdAt: 2023-11-29T17:58:26.201Z
+updatedAt: 2023-11-29T17:58:26.900Z
+publishedAt: 2023-11-29T17:58:26.900Z
+firstPublishedAt: 2023-11-29T17:58:26.900Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: received-skus-filter-do-not-work-with-special-characters
+locale: en
+kiStatus: Backlog
+internalReference: 944533
+---
+
+## Summary
+
+
+When trying to filter the skus on the Received Skus module, the marketplace can choose to filter by seller, category and/or brand.
+
+However, when selecting a brand that has special characters (like "&" or "+") the result is that there are no skus in that filter, which is not actually correct.
+
+
+##
+
+## Simulation
+
+
+
+1. Filter by one of the options on the Received Skus module;
+2. Select a value with special character;
+3. Check that the result is no skus;
+4. Now search by the value on the search and check that in fact there are some skus.
+
+
+##
+
+## Workaround
+
+
+No workaround to fix the filter, but using the search could bring a close result of the skus.
+
+
+
+
+
diff --git a/docs/known-issues/en/received-skus-review-tab-missing-products.md b/docs/known-issues/en/received-skus-review-tab-missing-products.md
new file mode 100644
index 000000000..bb4a1acea
--- /dev/null
+++ b/docs/known-issues/en/received-skus-review-tab-missing-products.md
@@ -0,0 +1,51 @@
+---
+title: 'Received Skus "Review" tab missing products'
+id: 2UM0JQUZVq5o7NHCjmrg8N
+status: PUBLISHED
+createdAt: 2023-11-23T16:30:51.874Z
+updatedAt: 2024-02-01T12:54:26.917Z
+publishedAt: 2024-02-01T12:54:26.917Z
+firstPublishedAt: 2023-11-23T16:30:52.647Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: received-skus-review-tab-missing-products
+locale: en
+kiStatus: Fixed
+internalReference: 939877
+---
+
+## Summary
+
+
+The offers sent by the sellers can eventually go to the Review tab of the Marketplace's Received Skus depending if they passed or not the Offer Quality rules.
+
+Once they are on this tab, the seller can update their skus with the correct information (or any new information).
+
+However, when this happens, the sku changes it's status from "WaitingReview" to "Reviewed", disappearing from the Review tab and the entire Received Skus.
+
+
+##
+
+## Simulation
+
+
+
+1. Set up a "Optional requirements" rule on the Offer Quality module on the marketplace side;
+2. Wait for a sku go to the Review tab for not passing the rule;
+3. Wait for a sku update on the seller side;
+4. Check that the sku is no longer on the Review tab
+
+
+##
+
+## Workaround
+
+
+Approve the product via API: https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerskuid-/versions/-version-/matches/-matchid-
+
+
+
+
+
diff --git a/docs/known-issues/en/redirects-are-being-counted-multiple-times.md b/docs/known-issues/en/redirects-are-being-counted-multiple-times.md
new file mode 100644
index 000000000..2652dcf11
--- /dev/null
+++ b/docs/known-issues/en/redirects-are-being-counted-multiple-times.md
@@ -0,0 +1,48 @@
+---
+title: 'Redirects are being counted multiple times'
+id: 51JfHBdp72duH5cBWMYl0t
+status: PUBLISHED
+createdAt: 2024-07-16T19:48:36.586Z
+updatedAt: 2024-07-16T19:49:42.290Z
+publishedAt: 2024-07-16T19:49:42.290Z
+firstPublishedAt: 2024-07-16T19:48:37.314Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: redirects-are-being-counted-multiple-times
+locale: en
+kiStatus: Backlog
+internalReference: 1066548
+---
+
+## Summary
+
+
+When trying to upload a file with more than 200 redirects, the front gets into a loop and reads those redirects three times. This can lead to more redirects on the error message on the screen or in the loading modal. The redirects are not being duplicated, but we are reading them more than once.
+
+
+##
+
+## Simulation
+
+
+Try uploading a file with 930 redirects, for example. The loading modal will appear with a higher number than 930:
+ ![](https://vtexhelp.zendesk.com/attachments/token/vypbPdcFp4KtjVvI5rL4tHQXU/?name=image.png)
+
+if the file contains an error, you can find a similar error message as this:
+ ![](https://vtexhelp.zendesk.com/collaboration/graphql/attachments/download/s3-145778c5-53eb-4002-9b91-1b43f7394896/image.png)
+This is just a front error, and it is not impacting the upload of redirects itself.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/redirects-for-preview-links-when-using-in-the-final-of-the-url.md b/docs/known-issues/en/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
new file mode 100644
index 000000000..deb97fea9
--- /dev/null
+++ b/docs/known-issues/en/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
@@ -0,0 +1,44 @@
+---
+title: 'Redirects for preview links when using / in the final of the URL'
+id: 7mO7pEA0DMclbWy2pPPUkd
+status: PUBLISHED
+createdAt: 2023-10-27T19:00:01.248Z
+updatedAt: 2023-10-27T19:00:01.916Z
+publishedAt: 2023-10-27T19:00:01.916Z
+firstPublishedAt: 2023-10-27T19:00:01.916Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: redirects-for-preview-links-when-using-in-the-final-of-the-url
+locale: en
+kiStatus: Backlog
+internalReference: 927041
+---
+
+## Summary
+
+
+On Faststore, if you access a preview link with the / on the final of the URL the link will be redirected to a page like this https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
+
+
+##
+
+## Simulation
+
+
+Try to access a preview page of the Faststore with a / on the final of the URL, such as https://starter.vtex.app/s/
+It will redirect you to https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/refid-behavior-not-consistent-between-api-and-ui.md b/docs/known-issues/en/refid-behavior-not-consistent-between-api-and-ui.md
new file mode 100644
index 000000000..f4c287c69
--- /dev/null
+++ b/docs/known-issues/en/refid-behavior-not-consistent-between-api-and-ui.md
@@ -0,0 +1,47 @@
+---
+title: 'RefId behavior not consistent between API and UI'
+id: 4007iEJ8bCN96PBY0nsIB4
+status: PUBLISHED
+createdAt: 2023-09-29T13:11:04.826Z
+updatedAt: 2023-10-20T13:41:48.679Z
+publishedAt: 2023-10-20T13:41:48.679Z
+firstPublishedAt: 2023-09-29T13:11:05.384Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: refid-behavior-not-consistent-between-api-and-ui
+locale: en
+kiStatus: Backlog
+internalReference: 910050
+---
+
+## Summary
+
+
+
+Currently, we have two behaviors for the refid code, via API it is not possible to be the same as other products, but via UI it allows us to insert the same value as other products already have.
+
+
+##
+
+## Simulation
+
+
+
+Create a product with a redIf code
+Create another product and try to use the same refId code as the other one, via API it won't be possible but via UI it will.
+
+
+##
+
+## Workaround
+
+
+
+If you need to use the same refIds for different products, insert them via UI.
+
+
+
+
+
diff --git a/docs/known-issues/en/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md b/docs/known-issues/en/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
new file mode 100644
index 000000000..9d6af6f8d
--- /dev/null
+++ b/docs/known-issues/en/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
@@ -0,0 +1,49 @@
+---
+title: 'Regex conflict causes us to misidentify Mastercard as Visa'
+id: MzUm8xH6vDeGxWcj6GCbZ
+status: PUBLISHED
+createdAt: 2023-09-04T17:51:08.019Z
+updatedAt: 2023-11-30T15:25:47.066Z
+publishedAt: 2023-11-30T15:25:47.066Z
+firstPublishedAt: 2023-09-04T17:51:09.705Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: regex-conflict-causes-us-to-misidentify-mastercard-as-visa
+locale: en
+kiStatus: Backlog
+internalReference: 893588
+---
+
+## Summary
+
+
+Regex conflict causes us to misidentify the Cards Brand at the checkout.
+
+
+##
+
+## Simulation
+
+
+
+1. Configure two Payment Conditions one for Visa credit card processing and one for Mastercard credit card processing
+2. Buy a random item in the store and choose to pay it by credit card.
+3. Fill in the card number with the Mastercard BIN 523431 and complete with random numbers.
+4. Fill the rest card information with fake data
+5. Finish the purchase
+6. Go to admin and search for the transaction already created and the payment will be identified as Visa instead of Mastercard
+
+
+##
+
+## Workaround
+
+
+N/a
+
+
+
+
+
diff --git a/docs/known-issues/en/region-api-returns-seller-list-due-to-cache.md b/docs/known-issues/en/region-api-returns-seller-list-due-to-cache.md
new file mode 100644
index 000000000..5d5ab7bcf
--- /dev/null
+++ b/docs/known-issues/en/region-api-returns-seller-list-due-to-cache.md
@@ -0,0 +1,45 @@
+---
+title: 'Region API returns seller list due to cache'
+id: 1uDscW8Z3tG4EXS23fCfci
+status: PUBLISHED
+createdAt: 2024-01-22T17:34:18.690Z
+updatedAt: 2024-01-22T17:48:47.576Z
+publishedAt: 2024-01-22T17:48:47.576Z
+firstPublishedAt: 2024-01-22T17:34:19.518Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: region-api-returns-seller-list-due-to-cache
+locale: en
+kiStatus: Backlog
+internalReference: 969692
+---
+
+## Summary
+
+
+When using a subaccount structure with region, if the API Get sellers by region or address is used in both accounts for the same sales channel, and one of them is not available for that sales channel, it will return a seller list due to cache.
+
+
+##
+
+## Simulation
+
+
+
+- Create a new store;
+- Set different sales channel for the store;
+- Use the API Get sellers by region or address in the store;
+- Use again the API for the same sales channel in the other store.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 2d5071075..08393b335 100644
--- a/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,10 +1,10 @@
 ---
 title: "Regions API doesn't calculate the "seller 1" correctly while requesting non-whitelabel sellers"
 id: 20sT9AMMi7Ob5IZc7FeiCB
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
-updatedAt: 2022-11-25T21:53:57.112Z
-publishedAt: 2022-11-25T21:53:57.112Z
+updatedAt: 2024-03-14T13:47:34.269Z
+publishedAt: 
 firstPublishedAt: 2022-03-28T20:45:28.144Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/en/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md b/docs/known-issues/en/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
new file mode 100644
index 000000000..a7681c358
--- /dev/null
+++ b/docs/known-issues/en/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
@@ -0,0 +1,47 @@
+---
+title: 'Registered users (not logged in) cannot finish checkout when changing from delivery to pick-up on the checkout page'
+id: hmQ2riW1Ptjxyhk6gcWxN
+status: PUBLISHED
+createdAt: 2023-07-28T19:49:16.993Z
+updatedAt: 2024-04-17T15:46:57.958Z
+publishedAt: 2024-04-17T15:46:57.958Z
+firstPublishedAt: 2023-07-28T19:49:17.732Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page
+locale: en
+kiStatus: Fixed
+internalReference: 870845
+---
+
+## Summary
+
+
+When an registered user (not logged in) start the checkout with Delivery as the shipping option, and later changes to pickup, when trying to finish the checkout the error message "The Number field in the shipping attachment is invalid" will appear and not allow to place the order.
+
+
+##
+
+## Simulation
+
+
+
+1. Go to checkout and add a new item
+2. Input a zipcode to calculate shipping and keep **Delivery** selected
+3. Proceed to checkout and when asked to input an email use one from a registered user
+4. Checkout will show a pop-up message informing your personal data was retrieved from past purchases
+5. Change from Delivery to Pick-Up and try to complete the order (the error message will show)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/removing-ean-via-api-is-not-inactivating-skus-without-refids.md b/docs/known-issues/en/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
index 0c0b7fa06..84df4c463 100644
--- a/docs/known-issues/en/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
+++ b/docs/known-issues/en/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
@@ -3,8 +3,8 @@ title: 'Removing EAN via API is not inactivating SKUs without RefIDs'
 id: 2DIKKs93S41F38c3PrekSO
 status: PUBLISHED
 createdAt: 2022-08-01T11:37:52.731Z
-updatedAt: 2022-11-25T21:44:12.277Z
-publishedAt: 2022-11-25T21:44:12.277Z
+updatedAt: 2024-07-01T18:48:35.030Z
+publishedAt: 2024-07-01T18:48:35.030Z
 firstPublishedAt: 2022-08-01T11:37:53.288Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: removing-ean-via-api-is-not-inactivating-skus-without-refids
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 626031
 ---
 
diff --git a/docs/known-issues/en/render-component-issues-on-site-editor.md b/docs/known-issues/en/render-component-issues-on-site-editor.md
index 100487bd7..b1e5380a9 100644
--- a/docs/known-issues/en/render-component-issues-on-site-editor.md
+++ b/docs/known-issues/en/render-component-issues-on-site-editor.md
@@ -3,8 +3,8 @@ title: 'Render component issues on site editor'
 id: 66gcFw8LwnL6WsvuXPRzFn
 status: PUBLISHED
 createdAt: 2022-04-19T19:41:08.520Z
-updatedAt: 2023-03-10T14:17:10.739Z
-publishedAt: 2023-03-10T14:17:10.739Z
+updatedAt: 2024-06-21T12:24:51.158Z
+publishedAt: 2024-06-21T12:24:51.158Z
 firstPublishedAt: 2022-04-19T19:41:09.223Z
 contentType: knownIssue
 productTeam: CMS
@@ -19,7 +19,14 @@ internalReference: 415674
 ## Summary
 
 
-This behavior occurs intermittently, sometimes components are not rendered and sometimes it's rendered twice based on clicks on the page.
+Due to the quantity of information on the page, the site editor may have problems when rendering blocks. This behavior occurs intermittently, sometimes components are not rendered and sometimes it's rendered twice. It can happen that no blocks will appear at all on the site editor:
+ ![](https://vtexhelp.zendesk.com/attachments/token/miNCNkBPcmbXcVHmb9f5HWxIS/?name=image.png)
+
+Or it can happen with fewer blocks.
+
+You can also experience a delay after saving new content. The content is saved but the screen will keep loading:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/BwlA7jzWiWCxYMLOGxMb0N84N/?name=image.png)
 
 
 ##
@@ -27,7 +34,9 @@ This behavior occurs intermittently, sometimes components are not rendered and s
 ## Simulation
 
 
-Try editing Site Editor, sometimes it won't be rendered and sometimes some blocks will be rendered twice.
+1 - Try editing Site Editor, sometimes it won't be rendered and sometimes some blocks will be rendered twice.
+
+2 - Try saving a content change, the content is saved but the screen will keep loading
 
 
 ##
@@ -37,3 +46,5 @@ Try editing Site Editor, sometimes it won't be rendered and sometimes some block
 
 No known workaround is available.
 
+
+
diff --git a/docs/known-issues/en/replacing-orders-with-different-sales-channel.md b/docs/known-issues/en/replacing-orders-with-different-sales-channel.md
new file mode 100644
index 000000000..c653ce0e7
--- /dev/null
+++ b/docs/known-issues/en/replacing-orders-with-different-sales-channel.md
@@ -0,0 +1,45 @@
+---
+title: 'Replacing orders with different Sales Channel'
+id: 2gShXcwLLHu7R8JyPjP0W6
+status: PUBLISHED
+createdAt: 2024-02-16T13:02:17.686Z
+updatedAt: 2024-02-16T13:05:20.998Z
+publishedAt: 2024-02-16T13:05:20.998Z
+firstPublishedAt: 2024-02-16T13:02:18.609Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: replacing-orders-with-different-sales-channel
+locale: en
+kiStatus: Backlog
+internalReference: 982965
+---
+
+## Summary
+
+
+We have identified that it is not possible to replace a SKU in the order if the Sales Channel (SC), equal to 1, is not available for the account.
+
+For example, account A does not have sales channel=1, only SC=2, in the order replacement request we are sending sales channel=1 and not 2.
+
+
+##
+
+## Simulation
+
+
+Account A, does not have sales channel=1, only SC=2, in the order replacement request, when they request the replacement of a SKU, we are sent sales channel=1 and not 2, therefore, it is not possible to carry out the replacement.
+
+
+##
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/en/replicated-pending-payment-emails.md b/docs/known-issues/en/replicated-pending-payment-emails.md
index f46c63d4a..0501a5d52 100644
--- a/docs/known-issues/en/replicated-pending-payment-emails.md
+++ b/docs/known-issues/en/replicated-pending-payment-emails.md
@@ -3,8 +3,8 @@ title: 'Replicated Pending Payment E-mails'
 id: 6ibJCSrep1aWEKi1DRTLDv
 status: PUBLISHED
 createdAt: 2022-05-18T18:30:57.906Z
-updatedAt: 2022-11-25T22:02:18.499Z
-publishedAt: 2022-11-25T22:02:18.499Z
+updatedAt: 2024-02-16T20:29:35.766Z
+publishedAt: 2024-02-16T20:29:35.766Z
 firstPublishedAt: 2022-05-18T18:30:58.383Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: replicated-pending-payment-emails
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 348932
 ---
 
diff --git a/docs/known-issues/en/request-routing-is-inconsistent-when-running-ab-tests.md b/docs/known-issues/en/request-routing-is-inconsistent-when-running-ab-tests.md
new file mode 100644
index 000000000..020334809
--- /dev/null
+++ b/docs/known-issues/en/request-routing-is-inconsistent-when-running-ab-tests.md
@@ -0,0 +1,38 @@
+---
+title: 'Request routing is inconsistent when running A/B tests'
+id: 5ukS8DTwmWsM0fNWQLYFQ1
+status: PUBLISHED
+createdAt: 2023-11-08T21:42:53.184Z
+updatedAt: 2023-11-08T21:45:26.642Z
+publishedAt: 2023-11-08T21:45:26.642Z
+firstPublishedAt: 2023-11-08T21:42:53.723Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: request-routing-is-inconsistent-when-running-ab-tests
+locale: en
+kiStatus: Backlog
+internalReference: 931246
+---
+
+## Summary
+
+
+Store navigation HTTP requests do not honor the workspace selection cookie during the session. In fact, during a single session, a user can receive responses from all workspaces being tested.
+
+## Simulation
+
+1. Create an A/B test in your store using the VTEX IO CLI
+2. Open the "Application" tab in Chrome DevTools (or equivalent in your browser)
+    1. Navigate through the store and clear your `VtexWorkspace` cookie after every click
+    2. You should see values change eventually, even though the session cookie did not change
+3. Open the "Network" tab in Chrome DevTools (or equivalent in your browser)
+    1. Navigate through the store and observe the HTTP requests that are made
+    2. You should see that the `workspace` query string is set to different values throughout the session
+
+## Workaround
+
+There is no workaround available. A/B testing is not recommended and their results should not be considered correct until this Known Issue is fixed.
+
+
diff --git a/docs/known-issues/en/reserved-stock-in-invoiced-orders.md b/docs/known-issues/en/reserved-stock-in-invoiced-orders.md
index 55a91e235..fccf1eb79 100644
--- a/docs/known-issues/en/reserved-stock-in-invoiced-orders.md
+++ b/docs/known-issues/en/reserved-stock-in-invoiced-orders.md
@@ -1,10 +1,10 @@
 ---
 title: 'Reserved stock in invoiced orders'
 id: TfDOKEybi6eSAEoCEEAqg
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-13T18:43:58.606Z
-updatedAt: 2022-12-22T14:51:09.663Z
-publishedAt: 2022-12-22T14:51:09.663Z
+updatedAt: 2023-10-17T15:29:19.908Z
+publishedAt: 
 firstPublishedAt: 2017-06-14T00:07:07.051Z
 contentType: knownIssue
 productTeam: Post-purchase
diff --git a/docs/known-issues/en/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md b/docs/known-issues/en/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
new file mode 100644
index 000000000..36a69871e
--- /dev/null
+++ b/docs/known-issues/en/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
@@ -0,0 +1,43 @@
+---
+title: 'Returned Itens with same SkuId on different UniqueId arrays it is not visible properly'
+id: 65uUpH4uSicaDzruCIBaTq
+status: PUBLISHED
+createdAt: 2024-06-14T20:48:37.328Z
+updatedAt: 2024-06-14T20:48:38.207Z
+publishedAt: 2024-06-14T20:48:38.207Z
+firstPublishedAt: 2024-06-14T20:48:38.207Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly
+locale: en
+kiStatus: Backlog
+internalReference: 1050294
+---
+
+## Summary
+
+
+Our integrated systems (OMS/SNO/UI) was not designed to use the same info for correlation to shows the correct information when an iten with the same SKU was crated on different uniqueid array. It happens because some systems uses skuid and others itemindex.
+
+
+##
+
+## Simulation
+
+
+Create an order with a more than one quantity items, creating an order with more than one array of itens with same skuid. Invoice the order and on return pages will be possible to see that the item has no information about diferences between each one.
+
+
+##
+
+## Workaround
+
+
+There is no workarround for that.
+
+
+
+
+
diff --git a/docs/known-issues/en/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md b/docs/known-issues/en/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
index 8c3e07c20..c24ddbe3a 100644
--- a/docs/known-issues/en/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
+++ b/docs/known-issues/en/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
@@ -3,8 +3,8 @@ title: 'Reward value not added or have a different value added to gift card'
 id: 3i9TwGKpYOkwnHUXDON9V7
 status: PUBLISHED
 createdAt: 2023-06-14T16:06:37.154Z
-updatedAt: 2023-06-14T16:06:37.696Z
-publishedAt: 2023-06-14T16:06:37.696Z
+updatedAt: 2023-06-27T12:44:59.727Z
+publishedAt: 2023-06-27T12:44:59.727Z
 firstPublishedAt: 2023-06-14T16:06:37.696Z
 contentType: knownIssue
 productTeam: Checkout
@@ -19,7 +19,7 @@ internalReference: 844079
 ## Summary
 
 
-Reward value may not be or have a different value added to the shopper's gift card.
+Reward value may not be or have a different value added to the shopper's gift card when the promotion is configured to apply the reward amount when the order status changes to payment approved.
 
 
 ##
@@ -28,7 +28,7 @@ Reward value may not be or have a different value added to the shopper's gift ca
 
 
 
-- Create a reward value promotion;
+- Create a reward value promotion to apply when the order status changes to payment approved;
 - Finish a purchase;
 - Check the interactions in Order Details in admin; there will not be the message "_XX added to the user's fidelity program_"
 
@@ -38,7 +38,9 @@ Reward value may not be or have a different value added to the shopper's gift ca
 ## Workaround
 
 
-Select via admin the "Gift Cards" option in the menu, select the shopper's gift card, and click on "Statement" under the Actions column to add the proper value.
+
+- Select via admin the "Gift Cards" option in the menu, select the shopper's gift card, and click on "Statement" under the Actions column to add the proper value;
+- Configure the reward value promotion to apply when the order status changes to invoiced.
 
 
 
diff --git a/docs/known-issues/en/rewriter-is-not-receiving-url-updates.md b/docs/known-issues/en/rewriter-is-not-receiving-url-updates.md
new file mode 100644
index 000000000..29d0f32de
--- /dev/null
+++ b/docs/known-issues/en/rewriter-is-not-receiving-url-updates.md
@@ -0,0 +1,59 @@
+---
+title: 'Rewriter is not receiving URL updates'
+id: 4c3S9s57SzQCv8zv4L77Fu
+status: PUBLISHED
+createdAt: 2024-07-16T19:24:56.813Z
+updatedAt: 2024-07-16T19:24:57.773Z
+publishedAt: 2024-07-16T19:24:57.773Z
+firstPublishedAt: 2024-07-16T19:24:57.773Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: rewriter-is-not-receiving-url-updates
+locale: en
+kiStatus: Backlog
+internalReference: 1066527
+---
+
+## Summary
+
+
+When a URL is changed/deleted on the catalog, the rewriter does not receive this change. Since the rewriter is not notified about it, the URL is still pointing to the wrong type, which can also lead to problems on the IS.
+
+This can also happen when creating new category/subcategory routes on the catalog. The rewriter sometimes will need you to run the bootstrap query to receive those routes.
+
+
+##
+
+## Simulation
+
+
+Try deleting an existing brand from the catalog
+Run the mutation to see how this path is being received on the rewriter
+
+    {internal{ get(path:"/brand"){   from   declarer   query   disableSitemapEntry }}}
+
+If you look for that brand on the storefront, it will still be pointing to a `map=b`
+
+You can also check how this path is being returned on the pageType; if it is a fullText, the pageType was updated, and the rewriter didn't.
+
+
+##
+
+## Workaround
+
+
+Try deleting the route manually from the rewriter:
+
+      mutation{ internal{   delete(path:"/path"){     from     id     resolveAs   } }}
+
+
+Try running the bootstrap query to update the rewriter:
+
+    {bootstrap { brands categories}}
+
+
+
+
+
diff --git a/docs/known-issues/en/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md b/docs/known-issues/en/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
new file mode 100644
index 000000000..0f0d1794f
--- /dev/null
+++ b/docs/known-issues/en/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
@@ -0,0 +1,54 @@
+---
+title: 'roundingmode ceiling/floor not working properly among items with unitmultiplier other than 1'
+id: 5KzOM5kEp8QpkBTX7hdil1
+status: PUBLISHED
+createdAt: 2024-01-18T17:53:08.668Z
+updatedAt: 2024-01-18T17:53:09.229Z
+publishedAt: 2024-01-18T17:53:09.229Z
+firstPublishedAt: 2024-01-18T17:53:09.229Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1
+locale: en
+kiStatus: Backlog
+internalReference: 968349
+---
+
+## Summary
+
+
+
+It is possible to set, via task for the product team, to change how the discount value is rounded in the cart.
+In a scenario where the account is using a ceiling or floor rounding mode, this rounding won't work properly with items with unitmultiplier other than 1.
+
+That's because the unitMultiplier of this item is 100.0. When RnB rounds up the discount value for the checkout, it rounds up the unit price. So it takes the value of a small unit and rounds it up. Then it takes the entire discount, divides it by the quantity times the unitMultiplier, and rounds it up to two decimal places.
+As RnB only takes into account two decimal places, it either rounds to 0.01 or 0.02.
+
+
+##
+
+## Simulation
+
+
+
+Example:
+Total discount: -3.96
+Unit discount = -3.96 / (2*100) = -0.0198
+
+So, which item will take 0.0198% of the discount, instead of 3,96%
+
+
+##
+
+## Workaround
+
+
+
+A valid workaround would be set back to no roundingMode, so the problem will stop happening.
+
+
+
+
+
diff --git a/docs/known-issues/en/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md b/docs/known-issues/en/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
new file mode 100644
index 000000000..e4c650b4c
--- /dev/null
+++ b/docs/known-issues/en/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
@@ -0,0 +1,44 @@
+---
+title: 'Route prioritization does not offer the best option in terms of quantity of packages and items'
+id: 4verafDuoFnC5vGDI4UV1m
+status: PUBLISHED
+createdAt: 2023-10-30T18:28:52.771Z
+updatedAt: 2023-10-30T18:28:53.648Z
+publishedAt: 2023-10-30T18:28:53.648Z
+firstPublishedAt: 2023-10-30T18:28:53.648Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items
+locale: en
+kiStatus: Backlog
+internalReference: 927747
+---
+
+## Summary
+
+
+In Logistics, the first tiebreaker criteria when the system is choosing the route (warehouse + dock + shipping policy), is related to the number of packages needed for this specific route, less package means that the route should be better.
+Although, the system can't consider the relationship between the number of package and number of items in each package.
+This means that for an example an order with 2 package and 2 items, can be prioritise when it has an available route that deliveries only 1 package with all the items.
+
+
+##
+
+## Simulation
+
+
+There is no easy way to simulate this scenario, as this is very specific and the system can behave differently in each case, but we have an example very clear where the system choose the SLA that divides the package in 2 instead of offering the SLA with only 1 package.
+
+
+##
+
+## Workaround
+
+
+The merchant can separate the warehouse + dock + shipping policy, with different shipping method name, in order to not depend on the prioritization of the route.
+
+
+
+
diff --git a/docs/known-issues/en/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/en/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
new file mode 100644
index 000000000..e6676b566
--- /dev/null
+++ b/docs/known-issues/en/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -0,0 +1,51 @@
+---
+title: 'Sales channel configured in B2B Settings is not assigned after approving Organizations'
+id: 7kxMtk2YHJdk5uPdj5wBs5
+status: PUBLISHED
+createdAt: 2023-07-21T20:03:44.671Z
+updatedAt: 2023-07-21T20:03:45.295Z
+publishedAt: 2023-07-21T20:03:45.295Z
+firstPublishedAt: 2023-07-21T20:03:45.295Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations
+locale: en
+kiStatus: Backlog
+internalReference: 866933
+---
+
+## Summary
+
+
+The sales channel configured in B2B Organizations Settings is not saved in the Organization Details.
+
+
+##
+
+## Simulation
+
+
+
+- Configure a default sales channel in B2B Organizations Settings;
+- Create an Organization Request;
+- Approve the Organization Request;
+- Check the Organization details; it won't have any sales channel assigned.
+
+
+##
+
+## Workaround
+
+
+
+- Assign the sales channel to the organization via admin;
+- Create a trigger for the organizations entity's schema:
+
+    "v-triggers": [{ "name": "define-salesChannel-default", "active": true, "condition": "salesChannel is null", "action": { "type": "save", "dataEntity": "organizations", "json": { "id": "{!id}", "salesChannel": "{add here the salesChannelId defined in B2B Organizations Settings}" } } }]
+
+
+
+
+
diff --git a/docs/known-issues/en/schema-validation-failing-for-custom-types-in-headless-cms.md b/docs/known-issues/en/schema-validation-failing-for-custom-types-in-headless-cms.md
new file mode 100644
index 000000000..ed3707ea7
--- /dev/null
+++ b/docs/known-issues/en/schema-validation-failing-for-custom-types-in-headless-cms.md
@@ -0,0 +1,49 @@
+---
+title: 'Schema validation failing for custom types in Headless CMS'
+id: 2dcDsFQkqbNqJZXEzztQ11
+status: PUBLISHED
+createdAt: 2023-09-19T21:43:59.145Z
+updatedAt: 2023-09-19T21:43:59.945Z
+publishedAt: 2023-09-19T21:43:59.945Z
+firstPublishedAt: 2023-09-19T21:43:59.945Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: schema-validation-failing-for-custom-types-in-headless-cms
+locale: en
+kiStatus: Backlog
+internalReference: 903687
+---
+
+## Summary
+
+
+
+We have failing schema validations in required fields without default value in Headless CMS for custom page types, the lib that we use is considering it failing but the required fields are filled correctly
+
+
+##
+
+## Simulation
+
+
+
+Create a schema structure for a specific page with a required field and don't put a default value for this required field
+
+
+    ..."required": ["field1"],"properties": { "field1": { "title": "Field", "type": "string", "description": "Some description" }}...
+
+
+
+##
+
+## Workaround
+
+
+Put a default value in the required fields
+
+
+
+
+
diff --git a/docs/known-issues/en/scroll-issue-when-zooming-after-search-page-render.md b/docs/known-issues/en/scroll-issue-when-zooming-after-search-page-render.md
new file mode 100644
index 000000000..41878c2c6
--- /dev/null
+++ b/docs/known-issues/en/scroll-issue-when-zooming-after-search-page-render.md
@@ -0,0 +1,47 @@
+---
+title: 'Scroll issue when zooming after search page render'
+id: 2FcX9UNvBOanE3EhH9q0DT
+status: PUBLISHED
+createdAt: 2024-02-08T16:51:28.278Z
+updatedAt: 2024-03-06T14:17:07.639Z
+publishedAt: 2024-03-06T14:17:07.639Z
+firstPublishedAt: 2024-02-08T16:51:29.011Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: scroll-issue-when-zooming-after-search-page-render
+locale: en
+kiStatus: Fixed
+internalReference: 979464
+---
+
+## Summary
+
+
+
+When changing the viewport or zooming the screen on search pages after the first load, it's not allowed to scroll the page properly.
+
+
+##
+
+## Simulation
+
+
+
+
+- Load your search page
+- Change your browser's zoom
+- Try to scroll the page
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md b/docs/known-issues/en/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
new file mode 100644
index 000000000..5bb34bd0b
--- /dev/null
+++ b/docs/known-issues/en/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
@@ -0,0 +1,48 @@
+---
+title: "Scroll issues when swiping in mobile in quick view when there's a slider layout on background"
+id: 5B7g5Wt1iyh0BLwIUprO2C
+status: PUBLISHED
+createdAt: 2024-02-20T17:58:53.942Z
+updatedAt: 2024-02-20T17:58:54.806Z
+publishedAt: 2024-02-20T17:58:54.806Z
+firstPublishedAt: 2024-02-20T17:58:54.806Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background
+locale: en
+kiStatus: Backlog
+internalReference: 985097
+---
+
+## Summary
+
+
+When swiping a product image in quick view on mobile when there's a slider layout in the background, both sliders are going to move to the next instead of just the image in quick view
+
+
+##
+
+## Simulation
+
+
+
+
+- Open a quick view on mobile with a slider layout on the background
+- Try swiping the product image
+
+The expected behavior is that not only the product image from quick view will change, but also the products in slider layout/shelf
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/search-analytics-duplicated-events.md b/docs/known-issues/en/search-analytics-duplicated-events.md
new file mode 100644
index 000000000..045a2d4b5
--- /dev/null
+++ b/docs/known-issues/en/search-analytics-duplicated-events.md
@@ -0,0 +1,60 @@
+---
+title: 'Search Analytics duplicated events'
+id: 48h3ObR7qqRHvU36weCvjC
+status: PUBLISHED
+createdAt: 2023-03-15T19:40:23.229Z
+updatedAt: 2023-09-20T18:49:19.673Z
+publishedAt: 2023-09-20T18:49:19.673Z
+firstPublishedAt: 2023-03-15T19:40:23.835Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: search-analytics-duplicated-events
+locale: en
+kiStatus: Fixed
+internalReference: 771986
+---
+
+## Summary
+
+
+Some events of the Intelligent Search reports are duplicated, which can impact the analytics view on the search admin module.
+
+
+#### FAQ
+
+**1. Does it affect all VTEX events (e.g., Request Capture, Admin Home page dashboards, etc.)?**
+
+No, Intelligent Search analytics are calculated differently and independently from those metrics and events for now. This issue only affects the Search > Analytics page.
+
+**2. Are all metrics being over-computed?**
+
+Yes, all raw metrics shown on the Search > Analytics page are being over-computed at the moment.
+
+Those are: search count, clicks on a term, unique clicks on a term, count of transactions after a term is searched and revenue generated from those transactions, click-through rate, and conversion.
+
+**3. Was the “Export to CSV” data also affected?**
+
+Yes, data exported to CSV is also impacted by the over-computed data.
+
+**4. Does this affect the Search Relevance algorithm and search results?**
+
+No, although the search relevance algorithm also uses the analytics events to calculate the product popularity score, it does not use the aggregated metrics.
+
+
+##
+
+## Simulation
+
+
+The scenario can be seen when checking the search admin page for the reports/analytics.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md b/docs/known-issues/en/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
new file mode 100644
index 000000000..23e1a8b56
--- /dev/null
+++ b/docs/known-issues/en/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
@@ -0,0 +1,46 @@
+---
+title: 'Search analytics report divergences between versions with/without funnel metrics'
+id: 33lXZb4Nr2NOPgW2Cth9ry
+status: PUBLISHED
+createdAt: 2024-02-09T19:01:45.952Z
+updatedAt: 2024-02-09T19:01:46.857Z
+publishedAt: 2024-02-09T19:01:46.857Z
+firstPublishedAt: 2024-02-09T19:01:46.857Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: search-analytics-report-divergences-between-versions-withwithout-funnel-metrics
+locale: en
+kiStatus: Backlog
+internalReference: 980297
+---
+
+## Summary
+
+
+The search analytics report exported as CSV may diverge between its version with funnel metrics and its version without.
+
+The regular report (without funnel metrics) is exported using the same method as the data presented on the page itself, but the export with funnel metrics uses a different method to compute additional data, which sometimes can result in different information.
+
+
+##
+
+## Simulation
+
+
+Export the two versions of the report for the same period and compare the listed search terms and the first columns between them.
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md b/docs/known-issues/en/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
index 5ff22c5a3..9c17c36f9 100644
--- a/docs/known-issues/en/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
+++ b/docs/known-issues/en/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
@@ -3,8 +3,8 @@ title: 'Search API not returning showIfNotAvailable=true SKUs for &fq=specificat
 id: 7p26JmS8pyPA8H0b1QJHyU
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:27.329Z
-updatedAt: 2022-11-25T22:10:15.920Z
-publishedAt: 2022-11-25T22:10:15.920Z
+updatedAt: 2024-02-16T20:29:43.164Z
+publishedAt: 2024-02-16T20:29:43.164Z
 firstPublishedAt: 2022-06-28T16:55:28.384Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 336896
 ---
 
diff --git a/docs/known-issues/en/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md b/docs/known-issues/en/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
index 3c58127be..e397a7264 100644
--- a/docs/known-issues/en/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
+++ b/docs/known-issues/en/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
@@ -3,8 +3,8 @@ title: 'Search API not working properly after login in using the Call Center Ope
 id: 3YxbokaDhYnthzy1dc5VHs
 status: PUBLISHED
 createdAt: 2022-01-21T18:24:15.316Z
-updatedAt: 2022-11-25T22:11:01.363Z
-publishedAt: 2022-11-25T22:11:01.363Z
+updatedAt: 2024-02-16T20:29:54.425Z
+publishedAt: 2024-02-16T20:29:54.425Z
 firstPublishedAt: 2022-03-16T16:50:03.972Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: search-api-not-working-properly-after-login-in-using-the-call-center-operator
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 304586
 ---
 
diff --git a/docs/known-issues/en/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md b/docs/known-issues/en/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
new file mode 100644
index 000000000..90ae28a15
--- /dev/null
+++ b/docs/known-issues/en/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
@@ -0,0 +1,42 @@
+---
+title: 'Search autocomplete providing outdated URL after navigating through suggestions'
+id: 168oT3vpuAcRdZbE7sahtF
+status: PUBLISHED
+createdAt: 2024-01-19T01:28:08.775Z
+updatedAt: 2024-01-19T01:28:09.627Z
+publishedAt: 2024-01-19T01:28:09.627Z
+firstPublishedAt: 2024-01-19T01:28:09.627Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: search-autocomplete-providing-outdated-url-after-navigating-through-suggestions
+locale: en
+kiStatus: Backlog
+internalReference: 968604
+---
+
+## Summary
+
+
+At the component "search-bar" with "autocomplete-result-list.v2", hovering the search suggestions will also change the suggested products as well as the text from the "see all {n} products" to mention the selected search, but the hyperlink from "see all" follows the original search term instead of the selected.
+
+
+##
+
+## Simulation
+
+
+
+- search for a partial term
+- hover the mouse over suggested terms
+- click on "see all products"
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md
new file mode 100644
index 000000000..ce86b1486
--- /dev/null
+++ b/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -0,0 +1,52 @@
+---
+title: 'Search banners not following the operator "AND" for trigger conditions'
+id: 4nQLt5q3Mz2DxvBIyZknXj
+status: PUBLISHED
+createdAt: 2024-06-20T21:17:46.485Z
+updatedAt: 2024-06-20T21:17:47.308Z
+publishedAt: 2024-06-20T21:17:47.308Z
+firstPublishedAt: 2024-06-20T21:17:47.308Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: search-banners-not-following-the-operator-and-for-trigger-conditions
+locale: en
+kiStatus: Backlog
+internalReference: 1053614
+---
+
+## Summary
+
+
+Conditions for search banners (managed via "/admin/search/v4/banners/") don't support the operator "AND" as presented in their trigger rules. The UI is wrong, and the operator behaves as "OR" fixedly.
+
+Any of the conditions filled there will be enough to present the banner on the page (PLP).
+
+Be mindful that setting a department there (category level 1) will apply the banner on any of its subcategories, as this is part of the full category path.
+
+
+##
+
+## Simulation
+
+
+Create a banner with the following trigger rules:
+
+- where "department" is "appliances"
+- **and**"category" is "refrigerators"
+
+The banner will not be restricted to the full category path "/appliances/refrigerators?map=c,c". It will be applied in the department and its subcategories, and any category named "refrigerators", even if it's not part of this specific department.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/search-by-ean-not-working-on-received-skus.md b/docs/known-issues/en/search-by-ean-not-working-on-received-skus.md
index cf6f1fcda..5ccadb63d 100644
--- a/docs/known-issues/en/search-by-ean-not-working-on-received-skus.md
+++ b/docs/known-issues/en/search-by-ean-not-working-on-received-skus.md
@@ -1,18 +1,18 @@
 ---
 title: 'Search by EAN not working on Received Skus'
 id: PKdNXxjVPFbJbVBSTFvep
-status: DRAFT
+status: PUBLISHED
 createdAt: 2022-01-26T19:24:01.975Z
-updatedAt: 2022-01-31T18:31:27.337Z
-publishedAt: 
+updatedAt: 2024-02-16T20:24:48.686Z
+publishedAt: 2024-02-16T20:24:48.686Z
 firstPublishedAt: 2022-01-26T19:25:13.218Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
-tag: 
+tag: Marketplace
 slug: search-by-ean-not-working-on-received-skus
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 510907
 ---
 
@@ -27,17 +27,23 @@ The Received Skus search feature allows the marketplace to search for a product
 Currently, the EAN search is not behaving as expected by not giving any results.
 
 
+##
 
 ## Simulation
 
 
-Try to find a sku by searching it using it's EAN.
+Try to find a sku by searching for it using it's EAN.
 The result should be the sku instead of a blank area.
 
 
+##
 
 ## Workaround
 
 
 Use the other search criteria, such as Sku Name or ID.
 
+
+
+
+
diff --git a/docs/known-issues/en/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md b/docs/known-issues/en/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
new file mode 100644
index 000000000..124328f81
--- /dev/null
+++ b/docs/known-issues/en/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
@@ -0,0 +1,54 @@
+---
+title: 'Search has no products if seller 1 name in the Seller Management differs from trading name in Account Management when using B2B Suite'
+id: 7a3bwqRmeSClHMoFmyIY2a
+status: PUBLISHED
+createdAt: 2023-12-01T20:06:13.492Z
+updatedAt: 2023-12-01T20:15:07.659Z
+publishedAt: 2023-12-01T20:15:07.659Z
+firstPublishedAt: 2023-12-01T20:06:14.083Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite
+locale: en
+kiStatus: Backlog
+internalReference: 946391
+---
+
+## Summary
+
+
+B2B organizations use the sellers' names from the Seller Management. If an organization has seller 1 assigned, the name saved will be from Seller Management, but no products may be shown in the search if it differs from the trading name in Account Management.
+
+
+##
+
+## Simulation
+
+
+
+- Have an account with seller 1 named in Seller Management different from the trading name in Account Management;
+- Create a B2B Organization and assign the seller 1;
+- Login to the account; no products are shown.
+
+
+##
+
+## Workaround
+
+
+
+- Access GraphQL IDE and select vtex.b2b-organizations-graphql;
+- Use the query below to get all the organization details:
+
+    { getOrganizationById(id:"insert here the organization id"){ id name tradeName status collections{ id name } paymentTerms{ id name } priceTables customFields{ name type value dropdownValues{ value label } useOnRegistration } salesChannel sellers { id name } }}
+
+- Send a mutation to update the seller name for seller 1 using the information retrieved above:
+
+    mutation { updateOrganization( id: "" name: "" tradeName: "" status: "active" collections: [{ id: "" name: "" }] paymentTerms: [{ id: "" name: "" }] priceTables: [""] customFields: [] salesChannel: "" sellers: [{ id: "1", name: "trade name from Account Management" }] ){ id status message }}
+
+
+
+
+
diff --git a/docs/known-issues/en/search-navigator-filter-price-range-yielding-incorrect-results.md b/docs/known-issues/en/search-navigator-filter-price-range-yielding-incorrect-results.md
index 8bc1dcddd..6269384ae 100644
--- a/docs/known-issues/en/search-navigator-filter-price-range-yielding-incorrect-results.md
+++ b/docs/known-issues/en/search-navigator-filter-price-range-yielding-incorrect-results.md
@@ -3,8 +3,8 @@ title: 'Search Navigator filter + Price Range yielding incorrect results'
 id: 6s4vJr6DVPLU9JlxIPWqhx
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.208Z
-updatedAt: 2022-11-25T22:10:01.089Z
-publishedAt: 2022-11-25T22:10:01.089Z
+updatedAt: 2024-02-16T20:24:11.551Z
+publishedAt: 2024-02-16T20:24:11.551Z
 firstPublishedAt: 2022-06-28T16:55:53.927Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: search-navigator-filter-price-range-yielding-incorrect-results
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 504992
 ---
 
diff --git a/docs/known-issues/en/search-resolver-applying-messages-translations-over-already-translated-content.md b/docs/known-issues/en/search-resolver-applying-messages-translations-over-already-translated-content.md
new file mode 100644
index 000000000..170817028
--- /dev/null
+++ b/docs/known-issues/en/search-resolver-applying-messages-translations-over-already-translated-content.md
@@ -0,0 +1,50 @@
+---
+title: 'Search Resolver applying Messages translations over already translated content'
+id: 7OIKmmhO3Pa2z0pIU33kY
+status: PUBLISHED
+createdAt: 2023-07-20T15:28:57.078Z
+updatedAt: 2024-06-13T20:51:17.597Z
+publishedAt: 2024-06-13T20:51:17.597Z
+firstPublishedAt: 2023-07-20T15:28:57.934Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: search-resolver-applying-messages-translations-over-already-translated-content
+locale: en
+kiStatus: Backlog
+internalReference: 865918
+---
+
+## Summary
+
+
+The Search Resolver (GraphQL layer for Intelligent Search) requests translations from the Messages service even for single-language stores or already translated content in a multi-language store.
+
+In practice, these translations are made on top of the same "from" and "to" languages, but if the store has the automatic translation feature enabled, the string may change to something unexpected.
+
+This affects especially strings with multiple words that may be considered from different languages, such as English words in the name of a product name that is majorly in French, and potentially dates (between the "dd/mm/yyyy" and "mm/dd/yyyy" notations).
+
+
+##
+
+## Simulation
+
+
+
+- Translate any content from the store's catalog to a language different from the default;
+- Make sure there is still at least one word in a different language than the translated one;
+- Check the storefront; it won't match the translation.
+
+
+##
+
+## Workaround
+
+
+
+- Disable the automatic translation;
+- Create translations for these contents using the same language as "from" and "to", for example, translating it from "fr-FR" to "fr-FR".
+
+
+
diff --git a/docs/known-issues/en/searching-not-return-document-when-the-value-contains-a-plus-symbol.md b/docs/known-issues/en/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
new file mode 100644
index 000000000..2463008be
--- /dev/null
+++ b/docs/known-issues/en/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
@@ -0,0 +1,62 @@
+---
+title: 'Searching not return document when the value contains a + (plus) symbol.'
+id: 7oWiN8Esh9iKy8144Tpglx
+status: PUBLISHED
+createdAt: 2024-07-08T18:52:21.794Z
+updatedAt: 2024-07-08T21:46:18.259Z
+publishedAt: 2024-07-08T21:46:18.259Z
+firstPublishedAt: 2024-07-08T18:52:22.908Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: searching-not-return-document-when-the-value-contains-a-plus-symbol
+locale: en
+kiStatus: No Fix
+internalReference: 828170
+---
+
+## Summary
+
+
+When searching for a document using a field value that includes the "+" symbol, the search does not return the document. This happens because the "+" symbol is incorrectly interpreted, resulting in the search value not matching the existing value.
+_This issue happens both in the API and in the CRM_
+
+
+##
+
+## Simulation
+
+
+
+1. Use the search API to query a field that includes a "+" symbol.
+2. The search will return an empty array. Example:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=+5512345678901&_fields=id,userId,email,homePhone,firstName
+
+
+In CRM UI:
+If you search for an email that contains the symbol "+" an error will be returned.
+
+    An unexpected error has occurred. Please try again. If the problem persists, contact support.
+
+
+
+##
+
+## Workaround
+
+
+There are two ways to handle this issue:
+Encode the "+" symbol to "%2B", so the search query becomes:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=%2B5512345678901&_fields=id,userId,email,homePhone,firstName
+
+
+Use the "*" symbol as a wildcard, which will allow the search to match any character(s) before the specified value:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=*12345678901&_fields=id,userId,email,homePhone,firstName
+
+This issue arises when searching for documents using field values that include the "+" symbol. The search API does not correctly interpret the "+" symbol, causing the search to fail by not matching the existing values. This problem is not limited to the "homePhone" field but can occur with other fields like email that might include special characters.
+To work around this issue, you can either encode the "+" symbol as "%2B" in the search query or use the "*" symbol as a wildcard to ensure the search retrieves the correct documents.
+
diff --git a/docs/known-issues/en/segment-cookie-updated-only-after-refreshing-the-page.md b/docs/known-issues/en/segment-cookie-updated-only-after-refreshing-the-page.md
index 2a0f45d3b..005c1f9fb 100644
--- a/docs/known-issues/en/segment-cookie-updated-only-after-refreshing-the-page.md
+++ b/docs/known-issues/en/segment-cookie-updated-only-after-refreshing-the-page.md
@@ -3,8 +3,8 @@ title: 'Segment Cookie updated only after refreshing the page'
 id: 3QBmp4D2tvIAxEzEy2LpNf
 status: PUBLISHED
 createdAt: 2022-11-01T16:33:05.698Z
-updatedAt: 2023-03-08T20:36:59.962Z
-publishedAt: 2023-03-08T20:36:59.962Z
+updatedAt: 2024-01-10T17:18:13.115Z
+publishedAt: 2024-01-10T17:18:13.115Z
 firstPublishedAt: 2022-11-01T16:33:06.403Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/en/seller-commission-updates-does-not-index-binded-skus.md b/docs/known-issues/en/seller-commission-updates-does-not-index-binded-skus.md
new file mode 100644
index 000000000..46287aff4
--- /dev/null
+++ b/docs/known-issues/en/seller-commission-updates-does-not-index-binded-skus.md
@@ -0,0 +1,53 @@
+---
+title: 'Seller commission updates does not index binded skus'
+id: GNX6sFV0thQkMLWEwxya9
+status: PUBLISHED
+createdAt: 2023-08-31T14:44:39.162Z
+updatedAt: 2023-08-31T14:44:39.748Z
+publishedAt: 2023-08-31T14:44:39.748Z
+firstPublishedAt: 2023-08-31T14:44:39.748Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: seller-commission-updates-does-not-index-binded-skus
+locale: en
+kiStatus: Backlog
+internalReference: 891162
+---
+
+## Summary
+
+
+When the merchant updates the seller commission on the Seller Management UI the binded skus related to this seller are not automatically indexed.
+
+Our checkout system uses the stockkeepingunitbyid API to get the updated information of the sku.
+
+On this API we have the object SkuSellers that contains the commission information. But if the sku is not indexed this object gets outdated.
+
+This implicates in the checkout getting the old value for the commission.
+
+
+##
+
+## Simulation
+
+
+
+1. Change the seller commission on the Seller Management UI.
+2. Wait for cache time, around 10min.
+3. Check that on the checkout simulation that the commission is outdated.
+
+
+##
+
+## Workaround
+
+
+To prevent closing orders with the outdated commission value, the merchant can manually index the affected skus.
+
+
+
+
+
+
diff --git a/docs/known-issues/en/seller-group-creation-does-not-add-selected-sellers.md b/docs/known-issues/en/seller-group-creation-does-not-add-selected-sellers.md
new file mode 100644
index 000000000..cc4852194
--- /dev/null
+++ b/docs/known-issues/en/seller-group-creation-does-not-add-selected-sellers.md
@@ -0,0 +1,51 @@
+---
+title: 'Seller group creation does not add selected sellers'
+id: 5J14RCg9E4LzBcvJQyOAYy
+status: PUBLISHED
+createdAt: 2023-10-27T17:33:45.625Z
+updatedAt: 2024-01-26T16:54:12.089Z
+publishedAt: 2024-01-26T16:54:12.089Z
+firstPublishedAt: 2023-10-27T17:33:46.214Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: seller-group-creation-does-not-add-selected-sellers
+locale: en
+kiStatus: Fixed
+internalReference: 926969
+---
+
+## Summary
+
+
+The marketplace can create groups with some sellers on the Seller Management UI.
+ ![](https://vtexhelp.zendesk.com/attachments/token/Mi9PZxDSnInogb65PbJ3fEduu/?name=image.png)
+
+However, when adding a group name and sellers on this UI, only the group name is being saved. An error message appears:
+"Sorry, something went wrong when adding the sellers to the XXX group."
+ ![](https://vtexhelp.zendesk.com/attachments/token/Gd0FRbqKLDnCGFmIjuXIctxwX/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+
+1. Go the Seller Management area and click on Manage groups;
+2. Click on Add Group and add the information like name and sellers;
+3. Check that the group is created but without any sellers.
+
+
+##
+
+## Workaround
+
+
+Add the sellers to the group manually later on their "Seller Details" UI
+
+
+
+
+
diff --git a/docs/known-issues/en/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md b/docs/known-issues/en/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
new file mode 100644
index 000000000..3979241a7
--- /dev/null
+++ b/docs/known-issues/en/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
@@ -0,0 +1,47 @@
+---
+title: 'Seller Portal Promotion Minimum Item Price condition not working as expected'
+id: d0qJRHP3ngtNH5gwSPaNi
+status: PUBLISHED
+createdAt: 2023-10-31T20:42:03.072Z
+updatedAt: 2023-10-31T20:42:03.763Z
+publishedAt: 2023-10-31T20:42:03.763Z
+firstPublishedAt: 2023-10-31T20:42:03.763Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: seller-portal-promotion-minimum-item-price-condition-not-working-as-expected
+locale: en
+kiStatus: Backlog
+internalReference: 928558
+---
+
+## Summary
+
+
+
+Currently, it is not possible to create a promotion and set a minimum item price condition, via interface it is not possible to save.
+
+
+##
+
+## Simulation
+
+
+
+Create a promotion and set a minimum price in the Conditions
+
+
+##
+
+## Workaround
+
+
+
+Via API it is possible to save the restriction.
+Warning: saving again via interface, after saving via API, will overwrite any alterations made.
+
+
+
+
+
diff --git a/docs/known-issues/en/seller-portal-select-specifications-dropdown-malfunctioning.md b/docs/known-issues/en/seller-portal-select-specifications-dropdown-malfunctioning.md
index a50a2b9de..50e37f769 100644
--- a/docs/known-issues/en/seller-portal-select-specifications-dropdown-malfunctioning.md
+++ b/docs/known-issues/en/seller-portal-select-specifications-dropdown-malfunctioning.md
@@ -3,8 +3,8 @@ title: 'Seller Portal Select Specifications Dropdown Malfunctioning'
 id: 7DeU9mKh7gseN7svVPtDzb
 status: PUBLISHED
 createdAt: 2022-12-06T14:27:57.920Z
-updatedAt: 2023-05-09T19:08:09.706Z
-publishedAt: 2023-05-09T19:08:09.706Z
+updatedAt: 2024-02-16T20:24:15.024Z
+publishedAt: 2024-02-16T20:24:15.024Z
 firstPublishedAt: 2022-12-06T14:27:58.644Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: seller-portal-select-specifications-dropdown-malfunctioning
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 711303
 ---
 
diff --git a/docs/known-issues/en/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md b/docs/known-issues/en/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
new file mode 100644
index 000000000..8da6cb7cb
--- /dev/null
+++ b/docs/known-issues/en/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
@@ -0,0 +1,45 @@
+---
+title: "Seller register UI doesn't send products to reindex when inactivating a seller"
+id: 0iAMGhIOKDyMbEykB4pfx
+status: PUBLISHED
+createdAt: 2023-10-06T19:45:08.963Z
+updatedAt: 2023-10-06T19:45:29.372Z
+publishedAt: 2023-10-06T19:45:29.372Z
+firstPublishedAt: 2023-10-06T19:45:09.832Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller
+locale: en
+kiStatus: Backlog
+internalReference: 915970
+---
+
+## Summary
+
+
+When using the new seller experience UI, /admin/sellers, the action of inactivating a seller should reindex its related products so they can be removed from the associated marketplaces, which isn't currently happening.
+
+
+##
+
+## Simulation
+
+
+Access the aforementioned UI and, for a store that is integrating with a marketplace, with an affiliate endpoint (https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187) and then try inactivating a seller available for this same trade policy.
+
+The items, in the marketplace, will not be updated.
+
+
+##
+
+## Workaround
+
+
+Either reindex the base or use the legacy seller UI ( https://accountname.vtexcommercestable.com.br/admin/site/seller.aspx), which does trigger the indexing properly.
+
+
+
+
+
diff --git a/docs/known-issues/en/sellers-order-invoiced-with-problem-in-the-payment-capture.md b/docs/known-issues/en/sellers-order-invoiced-with-problem-in-the-payment-capture.md
new file mode 100644
index 000000000..304836001
--- /dev/null
+++ b/docs/known-issues/en/sellers-order-invoiced-with-problem-in-the-payment-capture.md
@@ -0,0 +1,62 @@
+---
+title: "Seller's order invoiced with problem in the payment capture"
+id: 59M66kN7D6qy8ErLnbdT9r
+status: PUBLISHED
+createdAt: 2024-01-29T16:51:46.993Z
+updatedAt: 2024-01-29T16:51:47.674Z
+publishedAt: 2024-01-29T16:51:47.674Z
+firstPublishedAt: 2024-01-29T16:51:47.674Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: sellers-order-invoiced-with-problem-in-the-payment-capture
+locale: en
+kiStatus: Backlog
+internalReference: 376646
+---
+
+## Summary
+
+
+Right now, the way our architecture is built, both Seller and Marketplace are two totally different entities. The way it works is, Marketplace is responsible for receiving the money from the client and the Seller is responsible for all the logistics up to when it delivers the client its goods.
+
+The “receiving money” part is divided into Authorization and Capture. Both are separate actions in the Gateway and are executed in two distinct moments. The first one is when the client makes the purchase and the second one is when an invoice is inserted into the system. After the Authorization process, the Marketplace “tells” the Seller that it can proceed to prepare and send the client its goods. Since there is a gap in time between the Authorization and Capture and since they are separate actions, there is no guarantee that the Capture action will execute properly.
+
+This leaves us with the problem that the Seller received a notification to send the goods, inserted an invoice notification into the system, and the Marketplace had a problem in trying to make the Capture action.
+
+In these cases of Authorization and Capture notification, the Gateway always initially notifies the Marketplace which in turn notifies the Seller.
+
+The problem is that the flow of the Seller is not stopped by problems it may have in the Capture of payment, but it is reflected in the flow of the Marketplace.
+
+
+##
+
+## Simulation
+
+
+We do not have a step by step to replicate, however, it is possible to validate an example order.
+
+We can see that the Marketplace order reported a problem in the capture and was unable to complete the flow, displaying the error: "Settlement operation has returned Failed"
+
+In the flow, the order status in the Marketplace will be "Verifying invoice" and in the interactions the message: "Settlement operation has returned Failed" will be displayed.
+
+In transaction events, the message: "Error: Response was Entity_Declined" will be displayed.
+
+While the Seller's order reached Invoiced, because, for the Seller in the current architecture, the capture of the payment is not their responsibility even being the owner of the payment.
+
+
+
+##
+
+## Workaround
+
+
+At this moment we do not have a workaround to complete the Marketplace flow, as this depends on the capture being carried out correctly. Without confirmation from the Gateway, the order will not be able to advance. Unfortunately, the way out of this type of inconsistency is to cancel the MKT order and try to do a new one manually.
+
+It is important to always validate that the payment capture is completed before delivering the products
+
+
+
+
+
diff --git a/docs/known-issues/en/service-type-name-field-wrongly-returned-via-api.md b/docs/known-issues/en/service-type-name-field-wrongly-returned-via-api.md
new file mode 100644
index 000000000..162ba593c
--- /dev/null
+++ b/docs/known-issues/en/service-type-name-field-wrongly-returned-via-api.md
@@ -0,0 +1,45 @@
+---
+title: 'Service type name field wrongly returned via API'
+id: 1FdozyiQb5DLe7TPICyCDR
+status: PUBLISHED
+createdAt: 2024-01-04T16:36:17.926Z
+updatedAt: 2024-01-04T16:36:18.628Z
+publishedAt: 2024-01-04T16:36:18.628Z
+firstPublishedAt: 2024-01-04T16:36:18.628Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: service-type-name-field-wrongly-returned-via-api
+locale: en
+kiStatus: Backlog
+internalReference: 961278
+---
+
+## Summary
+
+
+Currently the SKU Catalog APIs are not returning correctly the name of a service type. Instead is being returned the name of the service value.
+
+
+##
+
+## Simulation
+
+
+
+1. Make a GET SKU request on a sku associated with a service: https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/stockkeepingunit/-skuId-
+2. Note that the services object returns a serviceTypeId field and a Name, however the Name field is not showing the service type name itself.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/services-prices-are-not-updated-when-added-to-items.md b/docs/known-issues/en/services-prices-are-not-updated-when-added-to-items.md
index 296e76378..37898c146 100644
--- a/docs/known-issues/en/services-prices-are-not-updated-when-added-to-items.md
+++ b/docs/known-issues/en/services-prices-are-not-updated-when-added-to-items.md
@@ -3,8 +3,8 @@ title: 'Services prices are not updated when added to items'
 id: 5hJ7TbHzX4zFbdNWqPnMRQ
 status: PUBLISHED
 createdAt: 2023-05-09T14:27:37.283Z
-updatedAt: 2023-05-09T14:27:37.766Z
-publishedAt: 2023-05-09T14:27:37.766Z
+updatedAt: 2023-06-23T18:37:32.624Z
+publishedAt: 2023-06-23T18:37:32.624Z
 firstPublishedAt: 2023-05-09T14:27:37.766Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/en/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md b/docs/known-issues/en/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
new file mode 100644
index 000000000..0a2c5616c
--- /dev/null
+++ b/docs/known-issues/en/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
@@ -0,0 +1,46 @@
+---
+title: 'Session cookies are shared between different bindings when they are not in the same path level'
+id: 4pKeUI7qtdByaQowYs19Et
+status: PUBLISHED
+createdAt: 2023-10-25T01:06:04.190Z
+updatedAt: 2023-10-25T01:06:04.707Z
+publishedAt: 2023-10-25T01:06:04.707Z
+firstPublishedAt: 2023-10-25T01:06:04.707Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level
+locale: en
+kiStatus: No Fix
+internalReference: 925071
+---
+
+## Summary
+
+
+Cookies for Session information are exclusive to the specific account binding, but bindings that are not under the same path level may receive cookies from lower levels, leading to issues.
+
+If they are from the same account, Session information will be mixed and override critical parameters. If they are from different accounts, it may block requests, generating errors like "cross-account requests are not allowed".
+
+
+##
+
+## Simulation
+
+
+An example of a scenario is a store that uses the root path `/` for its default language (English) and `/fr` for a second language (French). Information from the store in English may affect the French store and vice-versa.
+
+Another example is a B2C store under `/us` for the specific country and the B2B store under `/us/corporate`.
+
+
+##
+
+## Workaround
+
+
+Stores that share the same host/domain may keep the same pattern for their path without mixing different levels. Ideas of alternatives for the presented examples would be `/en` versus `/fr` (both using a single-level path) and `/us/personal` versus `/us/corporate` (two-level path).
+
+
+
+
diff --git a/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
new file mode 100644
index 000000000..738696d7d
--- /dev/null
+++ b/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -0,0 +1,53 @@
+---
+title: "Settings UI doesn't update "expiration period" of quotes"
+id: 4CmuAYwDn7tcCiR9DQHSFb
+status: PUBLISHED
+createdAt: 2023-08-07T19:42:22.810Z
+updatedAt: 2024-05-08T18:04:41.362Z
+publishedAt: 2024-05-08T18:04:41.362Z
+firstPublishedAt: 2023-08-07T19:43:56.788Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: settings-ui-doesnt-update-expiration-period-of-quotes
+locale: en
+kiStatus: Backlog
+internalReference: 876576
+---
+
+## Summary
+
+
+B2B Quote settings UI does not update the expiration period value; it is always 30.
+
+
+##
+
+## Simulation
+
+
+
+- Access the B2B Quotes settings page and change the "expiration period".
+- Refresh the page; no changes are applied.
+
+
+##
+
+## Workaround
+
+
+
+- Access GraphQL IDE and select vtex.b2b-quotes-graphql;
+- Use the query below to get the expiration date:
+
+    { getAppSettings{ adminSetup { cartLifeSpan } }}
+
+- Send a mutation to update the expiration date to a different value:
+
+    mutation SaveAppSettings($input: AppSettingsInput!) { saveAppSettings(input: $input) { adminSetup { cartLifeSpan } }}{ "input": { "cartLifeSpan": }}
+
+
+
+
+
diff --git a/docs/known-issues/en/shipping-options-gets-frozen-when-trying-to-select-an-option.md b/docs/known-issues/en/shipping-options-gets-frozen-when-trying-to-select-an-option.md
new file mode 100644
index 000000000..857827fc4
--- /dev/null
+++ b/docs/known-issues/en/shipping-options-gets-frozen-when-trying-to-select-an-option.md
@@ -0,0 +1,46 @@
+---
+title: 'Shipping options gets frozen when trying to select an option'
+id: 7zrMuzLq8kpNLDc2l2FswA
+status: PUBLISHED
+createdAt: 2023-09-13T14:42:26.106Z
+updatedAt: 2024-05-21T14:04:53.005Z
+publishedAt: 2024-05-21T14:04:53.005Z
+firstPublishedAt: 2023-09-13T14:42:26.860Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: shipping-options-gets-frozen-when-trying-to-select-an-option
+locale: en
+kiStatus: Fixed
+internalReference: 898888
+---
+
+## Summary
+
+
+When using the B2B Checkout Setting and going back and forth between shipping and payment steps, the shipping gets frozen when trying to select an option.
+
+
+##
+
+## Simulation
+
+
+
+- Make sure you have at least 2 addresses registered in the Cost Center;
+- Add any product to the cart and go to payment step;
+- Edit the shipping, go back to go to payment step and refresh the page;
+- Edit the shipping again and try to select an option, the UI will be frozen
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md b/docs/known-issues/en/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
new file mode 100644
index 000000000..7d869fdc8
--- /dev/null
+++ b/docs/known-issues/en/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
@@ -0,0 +1,46 @@
+---
+title: 'Shipping policy stuck in processing status is displayed as active in the new logistics UI'
+id: 6c6JrnkhTdz5kM8kGzsRXQ
+status: PUBLISHED
+createdAt: 2023-10-25T23:48:45.891Z
+updatedAt: 2023-11-27T21:18:03.811Z
+publishedAt: 2023-11-27T21:18:03.811Z
+firstPublishedAt: 2023-10-25T23:48:46.471Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui
+locale: en
+kiStatus: Fixed
+internalReference: 925914
+---
+
+## Summary
+
+
+Sometimes the shipping policy can be stuck in the processing status, but in the new logitics UI you can't see it because it informs you that the status is active.
+This behavior can get in the way when uploading a new freight spreadsheet, as the user will assume that the process has been completed by displaying an active status, but the new data will not be reflected.
+
+
+
+##
+
+## Simulation
+
+
+Have a shipping policy in active status in the new UI, where when trying to upload a new spreadsheet, the data is not reflected.
+
+
+
+##
+
+## Workaround
+
+
+In order for the shipping policy to leave the processing status in which it is stuck, a team action is required, after which the spreadsheet can be uploaded and the process will continue as normal.
+
+
+
+
+
diff --git a/docs/known-issues/en/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md b/docs/known-issues/en/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
index 68c75e485..4d0b66f2e 100644
--- a/docs/known-issues/en/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
+++ b/docs/known-issues/en/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
@@ -3,8 +3,8 @@ title: 'Shipping policy that does not deliver on weekends is being considered'
 id: 25bhUZXA9sZvyFVNeMUSJl
 status: PUBLISHED
 createdAt: 2022-06-08T18:32:07.971Z
-updatedAt: 2022-11-25T21:59:34.643Z
-publishedAt: 2022-11-25T21:59:34.643Z
+updatedAt: 2024-02-16T20:25:34.078Z
+publishedAt: 2024-02-16T20:25:34.078Z
 firstPublishedAt: 2022-06-08T18:32:08.836Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: shipping-policy-that-does-not-deliver-on-weekends-is-being-considered
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 594828
 ---
 
diff --git a/docs/known-issues/en/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md b/docs/known-issues/en/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
index bf28da744..608426b3d 100644
--- a/docs/known-issues/en/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
+++ b/docs/known-issues/en/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
@@ -3,8 +3,8 @@ title: 'Shipping Policy with incorrect MaxVolume on spreadsheet does not show Me
 id: 7zIbmadcOfI3oHmkm8LmkY
 status: PUBLISHED
 createdAt: 2022-05-18T18:19:04.901Z
-updatedAt: 2022-11-25T21:59:49.182Z
-publishedAt: 2022-11-25T21:59:49.182Z
+updatedAt: 2024-02-16T20:25:21.794Z
+publishedAt: 2024-02-16T20:25:21.794Z
 firstPublishedAt: 2022-05-18T18:19:05.868Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 380471
 ---
 
diff --git a/docs/known-issues/en/shipping-preview-does-not-use-sla-name-for-display-in-ui.md b/docs/known-issues/en/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
index 927dec42b..b3bf61817 100644
--- a/docs/known-issues/en/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
+++ b/docs/known-issues/en/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
@@ -3,8 +3,8 @@ title: 'Shipping Preview does not use SLA name for display in UI'
 id: 6v7vh0CSUfpiF04brZ0bgb
 status: PUBLISHED
 createdAt: 2022-05-06T20:46:38.910Z
-updatedAt: 2022-11-25T21:52:23.344Z
-publishedAt: 2022-11-25T21:52:23.344Z
+updatedAt: 2024-02-16T20:25:44.430Z
+publishedAt: 2024-02-16T20:25:44.430Z
 firstPublishedAt: 2022-05-06T20:46:39.731Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: shipping-preview-does-not-use-sla-name-for-display-in-ui
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 574651
 ---
 
diff --git a/docs/known-issues/en/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md b/docs/known-issues/en/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
new file mode 100644
index 000000000..a6c6bdd9a
--- /dev/null
+++ b/docs/known-issues/en/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
@@ -0,0 +1,45 @@
+---
+title: 'Shipping preview shows pick-up postal code for shipping when there is package split for pick-up and shipping'
+id: 7gGu9EUZGGXp4dRCCGipsA
+status: PUBLISHED
+createdAt: 2024-06-26T20:36:39.627Z
+updatedAt: 2024-06-26T20:36:40.541Z
+publishedAt: 2024-06-26T20:36:40.541Z
+firstPublishedAt: 2024-06-26T20:36:40.541Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping
+locale: en
+kiStatus: Backlog
+internalReference: 938124
+---
+
+## Summary
+
+
+In the shipping preview, when selecting pick up in store, but not all items are available for that pick-up, the address displayed for shipping is from the chosen pick-up, and it's not possible to change it. In the orderForm, the selected address for shipping is correct though.
+
+
+##
+
+## Simulation
+
+
+
+- Add items to the cart where at least one is not available for pickup;
+- Add a postal code to the cart;
+- Change to pick up in store;
+- The postal code shown for shipping is from the chosen pick-up.
+
+
+##
+
+## Workaround
+
+
+Change the postal code in the shipping step.
+
+
+
diff --git a/docs/known-issues/en/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md b/docs/known-issues/en/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
index e6b62b521..2ee229a64 100644
--- a/docs/known-issues/en/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
+++ b/docs/known-issues/en/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: "Shipping Preview wrongly displaying the date when it's scheduled deliver
 id: 6pbufuWTFkL4NK3xLIxj1z
 status: PUBLISHED
 createdAt: 2023-01-31T19:36:58.137Z
-updatedAt: 2023-01-31T19:36:58.933Z
-publishedAt: 2023-01-31T19:36:58.933Z
+updatedAt: 2024-07-01T18:48:44.228Z
+publishedAt: 2024-07-01T18:48:44.228Z
 firstPublishedAt: 2023-01-31T19:36:58.933Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 743774
 ---
 
diff --git a/docs/known-issues/en/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md b/docs/known-issues/en/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
index 3badc2cca..8f239787d 100644
--- a/docs/known-issues/en/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
+++ b/docs/known-issues/en/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: "Shipping Preview wrongly displaying the price when it's scheduled delive
 id: 1348f4mDxoxAT7pTKBxm29
 status: PUBLISHED
 createdAt: 2023-01-31T19:16:25.118Z
-updatedAt: 2023-02-01T20:32:44.535Z
-publishedAt: 2023-02-01T20:32:44.535Z
+updatedAt: 2024-03-27T15:40:02.745Z
+publishedAt: 2024-03-27T15:40:02.745Z
 firstPublishedAt: 2023-01-31T19:16:25.874Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 532487
 ---
 
diff --git a/docs/known-issues/en/shipping-previews-postal-code-input-field-is-not-hidden.md b/docs/known-issues/en/shipping-previews-postal-code-input-field-is-not-hidden.md
index 992a8bfcd..51536b071 100644
--- a/docs/known-issues/en/shipping-previews-postal-code-input-field-is-not-hidden.md
+++ b/docs/known-issues/en/shipping-previews-postal-code-input-field-is-not-hidden.md
@@ -3,8 +3,8 @@ title: "Shipping preview's postal code input field is not hidden"
 id: 6YCl40YEzu1HGkfHkcjGqu
 status: PUBLISHED
 createdAt: 2023-05-09T13:27:51.259Z
-updatedAt: 2023-05-09T13:27:51.724Z
-publishedAt: 2023-05-09T13:27:51.724Z
+updatedAt: 2024-02-20T22:22:29.335Z
+publishedAt: 2024-02-20T22:22:29.335Z
 firstPublishedAt: 2023-05-09T13:27:51.724Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: shipping-previews-postal-code-input-field-is-not-hidden
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 821984
 ---
 
diff --git a/docs/known-issues/en/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md b/docs/known-issues/en/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
new file mode 100644
index 000000000..13e421e86
--- /dev/null
+++ b/docs/known-issues/en/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
@@ -0,0 +1,44 @@
+---
+title: 'Shipping promotions applying in different SLAs causing divergence in Tax Hub'
+id: 3uI0b4FmXUh4uue5kFyFNy
+status: PUBLISHED
+createdAt: 2023-10-09T13:42:08.767Z
+updatedAt: 2023-10-23T11:59:12.329Z
+publishedAt: 2023-10-23T11:59:12.329Z
+firstPublishedAt: 2023-10-09T13:42:09.636Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub
+locale: en
+kiStatus: Fixed
+internalReference: 916423
+---
+
+## Summary
+
+
+When shipping promotions apply for different SLAs, one of them is free shipping, it causes divergence in the request sent by the Tax Hub, preventing the order from being placed.
+
+
+##
+
+## Simulation
+
+
+
+- Create a free shipping promotion for a specific SLA;
+- Create any other shipping promotion for another SLA;
+- Try placing an order, the message "The requested order could not be created. Please try again".
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/en/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md b/docs/known-issues/en/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
new file mode 100644
index 000000000..0ed761c3b
--- /dev/null
+++ b/docs/known-issues/en/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
@@ -0,0 +1,56 @@
+---
+title: 'Shipping step with postal code does not work for some countries (United Arab Emirates)'
+id: 2nlXX0e1q1MLiSjCG1U1Uf
+status: PUBLISHED
+createdAt: 2024-06-21T16:31:14.956Z
+updatedAt: 2024-07-16T13:10:07.140Z
+publishedAt: 2024-07-16T13:10:07.140Z
+firstPublishedAt: 2024-06-21T16:31:15.891Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates
+locale: en
+kiStatus: Fixed
+internalReference: 312132
+---
+
+## Summary
+
+
+The United Arab Emirates doesn't have postal codes, and the Checkout UI only accepts two inputs: postal code or geocoordinates.
+
+If the store configures postal code input, when arriving at the shipping step at checkout, the United Arab Emirates country does not work correctly – and potentially others.
+
+It is not possible to add anything to the component.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/EZeQLV41SRmxv7v9e0eUlzFqA/?name=inline358044226.png)
+
+##
+
+## Simulation
+
+
+
+- Go to the shipping step;
+- No field to add the postal code is shown;
+
+
+##
+
+## Workaround
+
+
+Add any dummy postal code via API, the fields will be shown then, for example, via console:
+
+    vtexjs.checkout.sendAttachment('shippingData', { "selectedAddresses": [{ addressType: "residential", country: "ARE", postalCode: "0" }]}).done(r=>{ console.log(r)})
+
+Result:
+ ![](https://vtexhelp.zendesk.com/attachments/token/cqRElEMi1ukYyP7WR8UjRilyn/?name=image.png)
+
+
+## **Workaround**
+For geocoordinates, it's possible to move with the purchase:
+ ![](https://vtexhelp.zendesk.com/attachments/token/fGQtJOaturVNnARJIm9erMyEa/?name=image.png)
+
diff --git a/docs/known-issues/en/shopee-failed-to-create-product-variations.md b/docs/known-issues/en/shopee-failed-to-create-product-variations.md
index f28925757..8ffe87ca6 100644
--- a/docs/known-issues/en/shopee-failed-to-create-product-variations.md
+++ b/docs/known-issues/en/shopee-failed-to-create-product-variations.md
@@ -3,8 +3,8 @@ title: '[Shopee] Failed to create product variations'
 id: 5IKAkqtm8eejg2IhzrCgSz
 status: PUBLISHED
 createdAt: 2022-10-25T16:29:19.572Z
-updatedAt: 2023-02-07T12:56:37.721Z
-publishedAt: 2023-02-07T12:56:37.721Z
+updatedAt: 2024-02-16T20:24:45.182Z
+publishedAt: 2024-02-16T20:24:45.182Z
 firstPublishedAt: 2022-10-25T16:29:20.906Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: shopee-failed-to-create-product-variations
 locale: en
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 685160
 ---
 
diff --git a/docs/known-issues/en/similar-products-ui-brokes-with-too-many-products.md b/docs/known-issues/en/similar-products-ui-brokes-with-too-many-products.md
new file mode 100644
index 000000000..93ba7700b
--- /dev/null
+++ b/docs/known-issues/en/similar-products-ui-brokes-with-too-many-products.md
@@ -0,0 +1,49 @@
+---
+title: 'Similar products UI brokes with too many products'
+id: 1gaBTJ1VlwLkoBb1636qoH
+status: PUBLISHED
+createdAt: 2023-07-25T15:53:49.976Z
+updatedAt: 2023-08-15T17:28:32.114Z
+publishedAt: 2023-08-15T17:28:32.114Z
+firstPublishedAt: 2023-07-25T15:53:50.941Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: similar-products-ui-brokes-with-too-many-products
+locale: en
+kiStatus: Backlog
+internalReference: 868425
+---
+
+## Summary
+
+
+
+When opening a product form with more than 6 similar products the UI visualization brokes
+in order to grow in a list format, starts to add in a stair format
+
+
+##
+
+## Simulation
+
+
+
+Add 10 similar products to a product
+
+
+##
+
+## Workaround
+
+
+
+
+- We recommend using API to manage the similar products
+- Try to minimize the zoom in the page helps to fits better, will work in some cases
+
+
+
+
+
diff --git a/docs/known-issues/en/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md b/docs/known-issues/en/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
index 0605b51bb..11734c103 100644
--- a/docs/known-issues/en/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
+++ b/docs/known-issues/en/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
@@ -3,8 +3,8 @@ title: 'Simulation Is not possible find Products from Catalog V2 on Shipping Sim
 id: 7jZBMAZHNilokDdbCxWzSs
 status: PUBLISHED
 createdAt: 2022-05-18T18:26:09.456Z
-updatedAt: 2022-11-25T21:59:14.900Z
-publishedAt: 2022-11-25T21:59:14.900Z
+updatedAt: 2024-02-16T20:28:57.548Z
+publishedAt: 2024-02-16T20:28:57.548Z
 firstPublishedAt: 2022-05-18T18:26:10.048Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 488362
 ---
 
diff --git a/docs/known-issues/en/single-installment-payment-condition-does-not-appear-at-chekout.md b/docs/known-issues/en/single-installment-payment-condition-does-not-appear-at-chekout.md
new file mode 100644
index 000000000..27fa93561
--- /dev/null
+++ b/docs/known-issues/en/single-installment-payment-condition-does-not-appear-at-chekout.md
@@ -0,0 +1,48 @@
+---
+title: 'Single installment payment condition does not appear at chekout.'
+id: 3L7GJTRaWWA9Wjw2zkQqtS
+status: PUBLISHED
+createdAt: 2022-06-29T11:57:22.859Z
+updatedAt: 2024-04-26T15:49:53.973Z
+publishedAt: 2024-04-26T15:49:53.973Z
+firstPublishedAt: 2022-06-29T11:57:23.251Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: single-installment-payment-condition-does-not-appear-at-chekout
+locale: en
+kiStatus: Backlog
+internalReference: 605568
+---
+
+## Summary
+
+
+When configuring a single Payment Condition with only one installment option or multiple payment conditions where only one installment option is available for a specific cart, this installment option is not displayed at checkout. Although it appears correctly in `paymentData`, it is not visible to the user. Instead, only the option to pay the total value is shown. However, when the transaction is completed, the payment is processed with the correct installment option.
+
+
+##
+
+## Simulation
+
+
+
+- Set up a single installment Payment Condition.
+- Go to the checkout page by purchasing any random item.
+- Navigate to the Network tab in devtools and verify that the installment option is correctly loaded in the `paymentData` response.
+- Check the installment options dropdown on the checkout page. Note that the configured installment option is missing, instead, the total amount is displayed.
+- Despite this issue, upon completing the purchase, the transaction correctly reflects the chosen installment option.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+Atenciosamente,
+Gisely Lacerda
+Product Support Engineer, Shopper Journey squad
+
diff --git a/docs/known-issues/en/site-editor-doesnt-allow-changes-on-the-conditional-template.md b/docs/known-issues/en/site-editor-doesnt-allow-changes-on-the-conditional-template.md
new file mode 100644
index 000000000..acf5565f2
--- /dev/null
+++ b/docs/known-issues/en/site-editor-doesnt-allow-changes-on-the-conditional-template.md
@@ -0,0 +1,46 @@
+---
+title: "Site editor doesn't allow changes on the conditional template"
+id: dGuXWBUUZdMB0nfndLPZ9
+status: PUBLISHED
+createdAt: 2023-07-13T20:05:31.326Z
+updatedAt: 2023-07-13T20:05:31.834Z
+publishedAt: 2023-07-13T20:05:31.834Z
+firstPublishedAt: 2023-07-13T20:05:31.834Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: site-editor-doesnt-allow-changes-on-the-conditional-template
+locale: en
+kiStatus: Backlog
+internalReference: 861920
+---
+
+## Summary
+
+
+When a template is set as the conditional one you're not able to perform changes on it through the site editor.
+
+
+##
+
+## Simulation
+
+
+
+- add a conditional template to one of the pages on CMS pages
+- be sure that the condition for it to work is being applied
+- try to edit that page through the site editor
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md b/docs/known-issues/en/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
index 24c923c93..a4eeef6f9 100644
--- a/docs/known-issues/en/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
+++ b/docs/known-issues/en/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
@@ -3,8 +3,8 @@ title: 'Site rendering Desktop Version when accessing via IPad on Safari'
 id: 17jzhKnc8X1bKo5ExwEY5L
 status: PUBLISHED
 createdAt: 2023-01-17T18:24:02.908Z
-updatedAt: 2023-01-17T18:27:50.296Z
-publishedAt: 2023-01-17T18:27:50.296Z
+updatedAt: 2024-02-16T20:26:44.446Z
+publishedAt: 2024-02-16T20:26:44.446Z
 firstPublishedAt: 2023-01-17T18:24:03.621Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: site-rendering-desktop-version-when-accessing-via-ipad-on-safari
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 735208
 ---
 
diff --git a/docs/known-issues/en/sitemap-isnt-being-generatedupdated.md b/docs/known-issues/en/sitemap-isnt-being-generatedupdated.md
new file mode 100644
index 000000000..ae8f109c4
--- /dev/null
+++ b/docs/known-issues/en/sitemap-isnt-being-generatedupdated.md
@@ -0,0 +1,75 @@
+---
+title: "Sitemap isn't being generated/updated"
+id: 1tJ4XHtbnFsfS30JWXwxb0
+status: PUBLISHED
+createdAt: 2023-05-17T13:58:46.443Z
+updatedAt: 2024-02-16T18:17:17.707Z
+publishedAt: 2024-02-16T18:17:17.707Z
+firstPublishedAt: 2023-05-17T13:58:47.102Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: sitemap-isnt-being-generatedupdated
+locale: en
+kiStatus: Backlog
+internalReference: 827104
+---
+
+## Summary
+
+
+
+There are three scenarios where the sitemap is not being generated/updated:
+
+
+
+1. When we have a product not found or with some kind of problem on the catalog the sitemap is not generated. You can search for the logs on OpenSearch, in this case, to check which product has a problem;
+
+
+
+2. When the account has the app `search.resolver@1.x`  the sitemap can have errors when:
+
+
+
+- A category has its first product coming from a similar category (the merch rules can have an impact on this case depending on the product you're promoting);
+
+- The search/brand/category page has no products, in this case, the page is not indexed on the sitemap, and its generation crashes
+
+
+3. Products that don't have the trade policy set on the catalog won't be received by the sitemap
+
+
+
+##
+
+## Simulation
+
+
+
+Try to generate the sitemap for an account that has one of the scenarios described above and it will crash
+
+
+##
+
+## Workaround
+
+
+
+
+- Create a new workspace
+- Install the search-resolver@0.x `(vtex install vtex.search-resolver@0.x)`
+- Generate the new sitemap
+- Now you can rollback search-resolver to 1.x (`vtex install vtex.search-resolver@1.x`)
+- Promote the created workspace to master
+
+Obs: This workaround may not work at all times. Sometimes the store can have so many invalid products that even the `search-resolver@0.x` will not update the sitemap.
+
+But eventually, you will need to fix the scenario that prevents the sitemap from being generated
+
+Stay in mind that updating the store to resolver@0.x and generate the sitemap in a workspace is the workaround because some invalid cases don't happen in our legacy search
+
+
+
+
+
diff --git a/docs/known-issues/en/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md b/docs/known-issues/en/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
new file mode 100644
index 000000000..8229da6ba
--- /dev/null
+++ b/docs/known-issues/en/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
@@ -0,0 +1,49 @@
+---
+title: 'SKU admin breaks when sending a reference code longer than 50 characters'
+id: 3AhyVsOpwkRUEHT77Wcc1A
+status: PUBLISHED
+createdAt: 2023-08-21T17:52:27.931Z
+updatedAt: 2023-08-21T17:52:28.799Z
+publishedAt: 2023-08-21T17:52:28.799Z
+firstPublishedAt: 2023-08-21T17:52:28.799Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters
+locale: en
+kiStatus: Backlog
+internalReference: 884789
+---
+
+## Summary
+
+
+It is expected that the user will be able to change the SKU's Reference code using the admin. However, when a value longer than 50 characters is passed in, the admin crashes, displaying a "something went wrong" message.
+
+
+##
+
+## Simulation
+
+
+
+- Go to the admin of an SKU: `/admin/Site/SkuForm.aspx?IdSku=`
+- Go to the **Reference code** field and put a value with more than 50 characters like:
+
+    ABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEW
+
+- Click on salve
+- A "something went wrong" message will be displayed on the front.
+
+
+##
+
+## Workaround
+
+
+Send no more than 50 characters on the **Reference code** field of an SKU
+
+
+
+
diff --git a/docs/known-issues/en/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md b/docs/known-issues/en/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
new file mode 100644
index 000000000..0f5ae3c1f
--- /dev/null
+++ b/docs/known-issues/en/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
@@ -0,0 +1,44 @@
+---
+title: 'Sku denied on Received Skus after throttling on marketplace catalog'
+id: 4fleOaKNp6ALXdmZcAVCg0
+status: PUBLISHED
+createdAt: 2024-01-23T12:50:23.697Z
+updatedAt: 2024-01-23T12:50:24.398Z
+publishedAt: 2024-01-23T12:50:24.398Z
+firstPublishedAt: 2024-01-23T12:50:24.398Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: sku-denied-on-received-skus-after-throttling-on-marketplace-catalog
+locale: en
+kiStatus: Backlog
+internalReference: 970208
+---
+
+## Summary
+
+
+When approving a new product on Received Skus (automatically or manually) the suggestions module communicates with the Marketplace's catalog to perform the action.
+If at this time the catalog module returns an throttling error, the sku ends up being rejected by the matcher despite having all the information correct.
+
+
+##
+
+## Simulation
+
+
+This is not an easy (or usual) scenario to replicate because it depends on another system not performing as it should and returning throttling.
+
+
+##
+
+## Workaround
+
+
+Approve the sku manually from the rejected area of Received Skus.
+
+
+
+
+
diff --git a/docs/known-issues/en/sku-file-update-does-not-update-v-version-tags.md b/docs/known-issues/en/sku-file-update-does-not-update-v-version-tags.md
new file mode 100644
index 000000000..eec8a1782
--- /dev/null
+++ b/docs/known-issues/en/sku-file-update-does-not-update-v-version-tags.md
@@ -0,0 +1,49 @@
+---
+title: 'SKU File Update does not update ?v version tags'
+id: 5Uw2VIBtTNDY3Ha5WDzGXJ
+status: PUBLISHED
+createdAt: 2023-06-29T14:37:56.437Z
+updatedAt: 2024-07-01T18:49:06.220Z
+publishedAt: 2024-07-01T18:49:06.220Z
+firstPublishedAt: 2023-06-29T14:37:57.352Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: sku-file-update-does-not-update-v-version-tags
+locale: en
+kiStatus: No Fix
+internalReference: 852869
+---
+
+## Summary
+
+
+Currently, when a SKU image file is updated via API to be on the same position as a previous one, it's version tag (?v=) on the product page is not correctly updated.
+
+
+##
+
+## Simulation
+
+
+
+
+- For a sku that already has files in it, try updating one image to a new one.
+- For a proper interpretation of the file being changed for the user and/or systems, the version tag (?v=) under the href image on the product page HTML should be updated.
+- Hoever, this doesn't happen when using this API to perform such updates.
+
+
+
+
+##
+
+## Workaround
+
+
+Deleting all SKU files and re-inserting them from scratch forces it to be updated.
+
+OR
+
+An indexer deletion forces the update.
+
diff --git a/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md
new file mode 100644
index 000000000..e5a979869
--- /dev/null
+++ b/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -0,0 +1,47 @@
+---
+title: 'SKU Insert File API is not responding with the "Text" property.'
+id: 2rPsyAkpGNCVIM4yGlcMBw
+status: PUBLISHED
+createdAt: 2024-04-10T14:59:14.341Z
+updatedAt: 2024-07-22T19:38:40.304Z
+publishedAt: 2024-07-22T19:38:40.304Z
+firstPublishedAt: 2024-04-10T14:59:15.416Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: sku-insert-file-api-is-not-responding-with-the-text-property
+locale: en
+kiStatus: Fixed
+internalReference: 1014787
+---
+
+## Summary
+
+
+Currently, the API to create a sku file https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file is not responding with the "Text" property correctly.
+
+This field's data is accepted and sent to the database, however, the response body of any of the SKU file's methods (GET, PUT, POST) are always responding the JSON response body containing the "Text" property as null, even when it has a saved value in it.
+
+
+##
+
+## Simulation
+
+
+1 - Using the aforementioned API, send a request body for a valid image that has a "Text" field with a non-null data.
+2 - Check either the response body of this API or use a GET request to fetch this file's data, the Text field will be null.
+3 - However, if you go to the store's admin, in https://VTEX.myvtex.com/admin/Site/SkuForm.aspx?IdSku= you will see that the text displays the data from the sent field.
+
+
+##
+
+## Workaround
+
+
+Fetch data, for the Text field from the admin, spreadsheets or search APIs.
+
+
+
+
+
diff --git a/docs/known-issues/en/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md b/docs/known-issues/en/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
index e7a53b9cf..f4e8023e2 100644
--- a/docs/known-issues/en/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
+++ b/docs/known-issues/en/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
@@ -3,8 +3,8 @@ title: 'SKU removed from Amazon SC is not being disable in Amazon Portal'
 id: 9yeLgMrhp9nSu9MtJ518G
 status: PUBLISHED
 createdAt: 2023-05-18T11:43:30.694Z
-updatedAt: 2023-05-18T11:43:31.301Z
-publishedAt: 2023-05-18T11:43:31.301Z
+updatedAt: 2023-08-14T17:50:14.349Z
+publishedAt: 2023-08-14T17:50:14.349Z
 firstPublishedAt: 2023-05-18T11:43:31.301Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 827760
 ---
 
diff --git a/docs/known-issues/en/sku-selector-display-mode-select-not-working-in-shelfs.md b/docs/known-issues/en/sku-selector-display-mode-select-not-working-in-shelfs.md
index 5ec012f0b..730393be0 100644
--- a/docs/known-issues/en/sku-selector-display-mode-select-not-working-in-shelfs.md
+++ b/docs/known-issues/en/sku-selector-display-mode-select-not-working-in-shelfs.md
@@ -3,8 +3,8 @@ title: 'SKU Selector display mode SELECT not working in shelfs'
 id: 4viowN3tnbsdc0f1bqXrux
 status: PUBLISHED
 createdAt: 2023-01-18T12:24:32.528Z
-updatedAt: 2023-01-18T12:24:33.003Z
-publishedAt: 2023-01-18T12:24:33.003Z
+updatedAt: 2024-02-16T20:24:43.422Z
+publishedAt: 2024-02-16T20:24:43.422Z
 firstPublishedAt: 2023-01-18T12:24:33.003Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: sku-selector-display-mode-select-not-working-in-shelfs
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 682152
 ---
 
diff --git a/docs/known-issues/en/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md b/docs/known-issues/en/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
new file mode 100644
index 000000000..fc8e63e63
--- /dev/null
+++ b/docs/known-issues/en/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
@@ -0,0 +1,52 @@
+---
+title: 'SKU Selector not choosing correct SKU when having similar variations with substrings'
+id: 7EY2RMqoJM7bbLZvyVDdRn
+status: PUBLISHED
+createdAt: 2024-06-11T18:15:27.243Z
+updatedAt: 2024-07-03T20:19:45.157Z
+publishedAt: 2024-07-03T20:19:45.157Z
+firstPublishedAt: 2024-06-11T18:15:28.029Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings
+locale: en
+kiStatus: Fixed
+internalReference: 1047992
+---
+
+## Summary
+
+
+When having a substring of the variation in the chosen SKU in another variation available, we might not select the picked SKU
+
+
+##
+
+## Simulation
+
+
+
+You need to have a variation available that has a substring of another available variation from the same product, for example:
+
+Variation value: 5
+Other Variation with substring: 5.5
+
+OR
+
+Variation value: black
+Other Variation with substring: black and white
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/sku-selector-with-multilpe-contexts.md b/docs/known-issues/en/sku-selector-with-multilpe-contexts.md
new file mode 100644
index 000000000..245db1006
--- /dev/null
+++ b/docs/known-issues/en/sku-selector-with-multilpe-contexts.md
@@ -0,0 +1,49 @@
+---
+title: 'SKU Selector with multilpe contexts'
+id: 4n6ap30jnJOrzflLCnVziO
+status: PUBLISHED
+createdAt: 2024-01-29T13:31:21.812Z
+updatedAt: 2024-07-11T19:19:22.383Z
+publishedAt: 2024-07-11T19:19:22.383Z
+firstPublishedAt: 2024-01-29T13:31:22.391Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: sku-selector-with-multilpe-contexts
+locale: en
+kiStatus: Fixed
+internalReference: 341322
+---
+
+## Summary
+
+
+
+SKU selector inside modal/quick view is not in the same context that is in the search page and product page.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/zIQ15WW7s1Zo24Z1I5tFT4H3y/?name=image.png)
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/gnAeV75W2Sip3Pl1zfQyAiWOI/?name=image.png)
+
+
+##
+
+## Simulation
+
+
+
+- Go to any store that has a quick view and sku-selector.
+- Pick an SKU and go to the quick view mode
+- Change the SKU inside the quick view modal
+- Exit quick view mode and you will notice that the sku didn't change, it just changed inside the quick view context
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md b/docs/known-issues/en/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
index 085937133..432f76296 100644
--- a/docs/known-issues/en/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
+++ b/docs/known-issues/en/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
@@ -3,8 +3,8 @@ title: "SKU Specification filters aren't loaded when the SKU is only available i
 id: 5SpoacD49oxDDGJjepUEoL
 status: PUBLISHED
 createdAt: 2022-03-21T17:41:20.048Z
-updatedAt: 2022-11-25T21:58:05.886Z
-publishedAt: 2022-11-25T21:58:05.886Z
+updatedAt: 2024-02-16T20:29:10.321Z
+publishedAt: 2024-02-16T20:29:10.321Z
 firstPublishedAt: 2022-03-21T17:41:20.389Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 431888
 ---
 
diff --git a/docs/known-issues/en/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/en/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
index 3f1ac18e3..e050cb187 100644
--- a/docs/known-issues/en/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/en/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
@@ -3,8 +3,8 @@ title: 'Skus from the same product being created separately (accounts with Autoa
 id: 1nkfd9OuKTFsnBWe1k6dif
 status: PUBLISHED
 createdAt: 2023-02-15T12:22:35.143Z
-updatedAt: 2023-02-15T12:22:35.839Z
-publishedAt: 2023-02-15T12:22:35.839Z
+updatedAt: 2023-11-28T19:01:37.291Z
+publishedAt: 2023-11-28T19:01:37.291Z
 firstPublishedAt: 2023-02-15T12:22:35.839Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 467112
 ---
 
diff --git a/docs/known-issues/en/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/en/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
new file mode 100644
index 000000000..bc1f469b4
--- /dev/null
+++ b/docs/known-issues/en/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
@@ -0,0 +1,54 @@
+---
+title: 'Skus from the same product being created separately on accounts with Autoapprove flag enabled'
+id: 5xWm9hzTO0Yuv0e2UuMgH6
+status: PUBLISHED
+createdAt: 2024-01-09T12:39:19.465Z
+updatedAt: 2024-07-22T19:31:17.990Z
+publishedAt: 2024-07-22T19:31:17.990Z
+firstPublishedAt: 2024-01-09T19:59:00.420Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled
+locale: en
+kiStatus: Fixed
+internalReference: 962986
+---
+
+## Summary
+
+
+The seller sends a batch with skus from the same product (all the possible variations of the product).
+
+Instead of being created as a product with it's variations, all the skus are being created separately.
+
+This behavior is happening because the marketplace account has the Autoapprove flag enabled and the seller is sending all the skus at once.
+
+Normally, the system has a lock, by product name, to prevent this kind of situation since the Matcher has more than one queue processing the skus. But this lock isn't implemented on the Autoapprove workflow.
+
+
+##
+
+## Simulation
+
+
+1. Enable the Autoapprove flag on the Marketplace;
+2. Seller send a batch of products and it's skus (variations) at once;
+3. The first skus of the product is created correctly, but the others are created separately.
+
+
+##
+
+## Workaround
+
+
+To prevent this situation, there are two possible ways.
+
+1. Seller send the skus slowly within a time frame;
+2. Disable the Autoapprove flag on the Marketplace.
+
+
+
+
+
diff --git a/docs/known-issues/en/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md b/docs/known-issues/en/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
index 7cc9ebaba..936b3bb1b 100644
--- a/docs/known-issues/en/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
+++ b/docs/known-issues/en/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
@@ -3,8 +3,8 @@ title: 'SkuServicoForm.aspx not listing Value Tables at first for a Value type'
 id: 2QrjRVvJXiWmRXTYf8DrMK
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:32.216Z
-updatedAt: 2022-11-25T21:50:15.511Z
-publishedAt: 2022-11-25T21:50:15.511Z
+updatedAt: 2024-02-16T20:27:50.659Z
+publishedAt: 2024-02-16T20:27:50.659Z
 firstPublishedAt: 2022-06-28T16:55:32.529Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 335819
 ---
 
diff --git a/docs/known-issues/en/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md b/docs/known-issues/en/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
new file mode 100644
index 000000000..2f0081bbb
--- /dev/null
+++ b/docs/known-issues/en/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
@@ -0,0 +1,48 @@
+---
+title: 'SLA offer fluctuating between different shipping policies due to cache in estimated date of 30 seconds'
+id: 2uN3bVrxHhj6Xs6TeQTJDr
+status: PUBLISHED
+createdAt: 2024-05-21T19:34:50.437Z
+updatedAt: 2024-05-21T19:38:10.682Z
+publishedAt: 2024-05-21T19:38:10.682Z
+firstPublishedAt: 2024-05-21T19:34:53.918Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds
+locale: en
+kiStatus: Backlog
+internalReference: 1036916
+---
+
+## Summary
+
+
+The logistics simulation can oscillate between offering SLAs if the client has shipping policies with the same price, delivery time, SlaType, dock cost and warehouse configuration, but different dock priority.
+We have a cache that stores the delivery time for 30 seconds, so when a new simulation is made, another shipping policy with the same configurations that has a longer dock time may be offered when it shouldn't be.
+
+
+
+##
+
+## Simulation
+
+
+Shipping policies A and B with the same total delivery time (1 day for example), price, dock cost and warehouse, but with different dock priorities.
+Make a quote at 16:00:00 where shipping policy A with lower dock priority will be offered, then the estimate result would be for the next day at 16:01:00, this data is cached for 30 seconds;
+When making a new quote at 16:00:10 for example, shipping policy B with a higher dock priority will be offered, because in the first quote the delivery time would be for example at 16:01:00 cached for 30 seconds, while the second quote B is chosen because it also has the estimate for the next day but at 16:00:00.
+
+
+
+##
+
+## Workaround
+
+
+There is no workaround for a scenario with the same settings as described above.
+
+
+
+
+
diff --git a/docs/known-issues/en/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md b/docs/known-issues/en/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
new file mode 100644
index 000000000..18752863e
--- /dev/null
+++ b/docs/known-issues/en/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
@@ -0,0 +1,46 @@
+---
+title: 'Slider-layout bug when using prop infinite as always on mobile'
+id: 4JERnak05tr2K8ICjjPjrN
+status: PUBLISHED
+createdAt: 2023-10-17T17:38:34.443Z
+updatedAt: 2023-10-17T17:38:35.106Z
+publishedAt: 2023-10-17T17:38:35.106Z
+firstPublishedAt: 2023-10-17T17:38:35.106Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile
+locale: en
+kiStatus: Backlog
+internalReference: 920725
+---
+
+## Summary
+
+
+When the slider-layout is set to `infinite: "always"` on the mobile the component presents an intermittent bug. After a while scrolling the shelf the products will stop to appear and a blank space will appear instead.
+
+
+##
+
+## Simulation
+
+
+
+- Set the prop `infinite: "always"`
+- On mobile, try to scroll the products
+- Eventually the products will stop to appear and the slider will become blank
+
+
+##
+
+## Workaround
+
+
+Use the `showNavigationArrows: "always"`, the problem only happens when scrolling
+
+
+
+
+
diff --git a/docs/known-issues/en/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md b/docs/known-issues/en/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
new file mode 100644
index 000000000..4b2de11e3
--- /dev/null
+++ b/docs/known-issues/en/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
@@ -0,0 +1,54 @@
+---
+title: 'Slug and Link returned in the Catalog Facets API have different formats.'
+id: 3LbYdhZhjsvUuQNC7VJN5G
+status: PUBLISHED
+createdAt: 2024-03-12T15:43:07.017Z
+updatedAt: 2024-03-12T15:43:08.057Z
+publishedAt: 2024-03-12T15:43:08.057Z
+firstPublishedAt: 2024-03-12T15:43:08.057Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: slug-and-link-returned-in-the-catalog-facets-api-have-different-formats
+locale: en
+kiStatus: Backlog
+internalReference: 998397
+---
+
+## Summary
+
+
+Catalog Facets API described here: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/facets/search/-term-
+The response objects have the field "Slug", "Link" and "LinkEncoded". However, these fields should have the same format, but they diverge on the PriceRanges object when the value has decimal cases.
+
+Example:
+Slug: "de-100-a-199.99"
+Link: "/category-test/de-100-a-199-99?map=c,priceFrom"
+
+The Slug has the character "." while the Link has the character "-".
+
+
+
+##
+
+## Simulation
+
+
+
+1. Have a category with a priceRange with decimal values.
+2. Request the facets API
+3. Check that the characters are different.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/sms-configuration-link-in-email-template-redirects-user-to-404-page.md b/docs/known-issues/en/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
new file mode 100644
index 000000000..0cdb5d7a1
--- /dev/null
+++ b/docs/known-issues/en/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
@@ -0,0 +1,46 @@
+---
+title: 'SMS configuration link in email template redirects user to 404 page'
+id: ZjIBvieBRNlN5lThuvtBf
+status: PUBLISHED
+createdAt: 2024-06-21T17:58:11.722Z
+updatedAt: 2024-06-21T17:58:12.707Z
+publishedAt: 2024-06-21T17:58:12.707Z
+firstPublishedAt: 2024-06-21T17:58:12.707Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: sms-configuration-link-in-email-template-redirects-user-to-404-page
+locale: en
+kiStatus: Backlog
+internalReference: 1054007
+---
+
+## Summary
+
+
+On the template configuration screen of the message center system, there is a link that should take the user to the configuration of the SMS sending app, but this app is no longer available and the link now returns 404, displaying a screen with the message "`store/not-found-box-title`".
+
+
+##
+
+## Simulation
+
+
+
+Access any template ;
+Go to the SMS tab and click on the link "Install it through the VTEX App Store."
+This link directs the user to the app store, but the app is no longer available.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md b/docs/known-issues/en/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
index ef3038a67..b3bcd5636 100644
--- a/docs/known-issues/en/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
+++ b/docs/known-issues/en/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
@@ -3,8 +3,8 @@ title: 'Some addresses autocompleted by Google are not able to be saved on My Ac
 id: DgYKHOqC0nnpHKEdcTeXQ
 status: PUBLISHED
 createdAt: 2022-04-28T19:44:12.222Z
-updatedAt: 2023-01-06T17:13:51.809Z
-publishedAt: 2023-01-06T17:13:51.809Z
+updatedAt: 2023-10-18T00:06:40.142Z
+publishedAt: 2023-10-18T00:06:40.142Z
 firstPublishedAt: 2022-05-10T18:17:39.573Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 415388
 ---
 
@@ -48,3 +48,6 @@ Example:
 
 There is no solution available for this.
 
+
+
+
diff --git a/docs/known-issues/en/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md b/docs/known-issues/en/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
new file mode 100644
index 000000000..149f56c36
--- /dev/null
+++ b/docs/known-issues/en/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
@@ -0,0 +1,45 @@
+---
+title: "Some functions of the sticky layout component won't work as expected when viewed through Safari browser"
+id: 6qXYzloLLowKzEqIUX1IB0
+status: PUBLISHED
+createdAt: 2023-11-08T13:34:35.513Z
+updatedAt: 2024-02-16T20:55:46.662Z
+publishedAt: 2024-02-16T20:55:46.662Z
+firstPublishedAt: 2023-11-08T13:34:36.172Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser
+locale: en
+kiStatus: Backlog
+internalReference: 868535
+---
+
+## Summary
+
+
+Some functions of the sticky layout component won't work as expected when viewed through Safari browser
+
+
+##
+
+## Simulation
+
+
+Using the sticky layout and trying to view it on Safari will sometimes not behave properly. Bellow are some of the observed behaviors:
+
+- the menus might appear floating even thought they are set to be fixed position
+
+
+##
+
+## Workaround
+
+
+Since this is a very specific use case for a very specific browser, there is currently no workaround for it.
+
+
+
+
+
diff --git a/docs/known-issues/en/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/en/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
new file mode 100644
index 000000000..70b6a9a07
--- /dev/null
+++ b/docs/known-issues/en/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
@@ -0,0 +1,50 @@
+---
+title: 'Some Inventory Management features not working properly on seller portal accounts'
+id: uJ4qws662c8pUnyfOV1fV
+status: PUBLISHED
+createdAt: 2024-03-18T17:54:20.400Z
+updatedAt: 2024-03-18T17:54:21.597Z
+publishedAt: 2024-03-18T17:54:21.597Z
+firstPublishedAt: 2024-03-18T17:54:21.597Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: some-inventory-management-features-not-working-properly-on-seller-portal-accounts
+locale: en
+kiStatus: Backlog
+internalReference: 1001665
+---
+
+## Summary
+
+
+Inventory Management features (like the links to the products) does not behave as expected on seller portal accounts. This happens because these kind of accounts use a different version of the catalog.
+
+The Logistics module use on this UI an API from catalogV1.
+
+However, we don't have a proxy from seller portal catalog to this API on catalogV1.
+
+The impact is that the links provided on the products do not open the catalog page, but instead it returns an error.
+
+
+##
+
+## Simulation
+
+
+
+1. Try to open the links to the products on a seller portal inventory management.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md b/docs/known-issues/en/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
new file mode 100644
index 000000000..ce414e1e4
--- /dev/null
+++ b/docs/known-issues/en/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
@@ -0,0 +1,52 @@
+---
+title: 'Some special characters are not stripped from product searches or indexing'
+id: 3qbzEcCkXpaPA0U23trlwT
+status: DRAFT
+createdAt: 2022-04-26T22:41:20.214Z
+updatedAt: 2023-11-29T20:24:51.268Z
+publishedAt: 
+firstPublishedAt: 2022-04-26T22:42:16.929Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: some-special-characters-are-not-stripped-from-product-searches-or-indexing
+locale: en
+kiStatus: Backlog
+internalReference: 382382
+---
+
+## Summary
+
+
+Some special characters are not completely stripped from the searched keywords or product indexing, which may affect searches in some specific scenarios.
+
+The known characters that lead to this scenario are commas (`,`), dots (`.`), and colons (`:`). Others are usually ignored and don't generate problems.
+
+While registering a product, commas and dots at the end of words are removed while indexing the product, but if in the middle of a word, they are kept. Keywords are split by spaces.
+
+While searching, colons are a reserved value and will invalidate the whole text query.
+
+
+##
+
+## Simulation
+
+
+For commas and dots, a product field that has a value like comma-separated keywords like `"car,specialbrand,blue"` will be read as a single word. Searching for `specialbrand` won't find this product.
+
+For colons, a product with the name `"red wine: special version"` can be found by searching by `wine`, but searching by `wine: special version` won't work. The whole search will be invalid, and no text filters will be applied.
+
+
+##
+
+## Workaround
+
+
+For commas and dots, a space after the character is required to split the keywords.
+
+For a search using colons, there's no workaround.
+
+
+
+
diff --git a/docs/known-issues/en/some-unexpected-behavior-in-masterdata.md b/docs/known-issues/en/some-unexpected-behavior-in-masterdata.md
new file mode 100644
index 000000000..52ae16ae1
--- /dev/null
+++ b/docs/known-issues/en/some-unexpected-behavior-in-masterdata.md
@@ -0,0 +1,48 @@
+---
+title: 'Some unexpected behavior in MasterData'
+id: 4E9jB5vkUMucnAuwUMOGQL
+status: PUBLISHED
+createdAt: 2023-09-18T21:27:15.291Z
+updatedAt: 2023-10-10T21:16:04.759Z
+publishedAt: 2023-10-10T21:16:04.759Z
+firstPublishedAt: 2023-09-18T21:27:15.908Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: some-unexpected-behavior-in-masterdata
+locale: en
+kiStatus: Backlog
+internalReference: 669048
+---
+
+## Summary
+
+
+Even with data available (documents), the information is not returned as expected.
+This behavior can impact some of the following functionalities:
+
+- Images in the Site Editor (CMS) are not available, due error message "_Something went wrong. Please try again._";
+- It is not possible to access entities and its documents due error message "_An unexpected error has occurred. Please try again. If the problem persists, contact support._";
+- The `_sort` is not respected on Search documents API;
+- No information is returned when using Search Documents API (an empty response, like `[]`), even when they contain documents.
+
+
+##
+
+## Simulation
+
+
+As this is an occasional behavior (cluster-related event), it cannot be simulated.
+
+
+##
+
+## Workaround
+
+
+The VTEX team must check the cluster and eventually re-index the data or change the cluster, so that the data will be available again.
+
+
+
+
diff --git a/docs/known-issues/en/something-went-wrong-error-is-displayed-in-the-catalog-admin.md b/docs/known-issues/en/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
new file mode 100644
index 000000000..d9998e5fb
--- /dev/null
+++ b/docs/known-issues/en/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
@@ -0,0 +1,49 @@
+---
+title: 'Something Went Wrong error is displayed in the catalog admin'
+id: 5TZLWNau0Vo6yp8URPsGcn
+status: PUBLISHED
+createdAt: 2023-09-26T17:00:49.516Z
+updatedAt: 2023-09-26T17:00:50.184Z
+publishedAt: 2023-09-26T17:00:50.184Z
+firstPublishedAt: 2023-09-26T17:00:50.184Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: something-went-wrong-error-is-displayed-in-the-catalog-admin
+locale: en
+kiStatus: Backlog
+internalReference: 907567
+---
+
+## Summary
+
+
+It is expected to use the admin without restrictions. However, sometimes a **Something Went Wrong** error is displayed in the catalog admin.
+
+
+##
+
+## Simulation
+
+
+
+1. Open the Catalog admin
+2. Open a section of the catalog, for example: `/admin/Site/ValeForm.aspx`, `Product.aspx` , `ProdutoCategoriaSimilarForm.aspx` or `SkuForm.aspx`
+3. Receive a **Something Went Wrong** error on the admin
+
+
+##
+
+## Workaround
+
+
+
+- Try to use the legacy admin: `.vtexcommercestable.com.br/admin`
+- Try to reload the page a few times, or
+- Try to wait for a few minutes and access the page again
+
+
+
+
+
diff --git a/docs/known-issues/en/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md b/docs/known-issues/en/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
new file mode 100644
index 000000000..8fec90af7
--- /dev/null
+++ b/docs/known-issues/en/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
@@ -0,0 +1,48 @@
+---
+title: 'Something went wrong message when accessing /a and /p routes in Portal stores'
+id: 2XGAGH8xpNqjJpAir6DKzz
+status: PUBLISHED
+createdAt: 2023-11-30T16:31:45.428Z
+updatedAt: 2023-11-30T16:31:45.990Z
+publishedAt: 2023-11-30T16:31:45.990Z
+firstPublishedAt: 2023-11-30T16:31:45.990Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores
+locale: en
+kiStatus: Backlog
+internalReference: 945226
+---
+
+## Summary
+
+
+It is expected to search for any term in the Portal's stores; however, the letters "A" and "P" are not directly searchable via the URL.
+So, a "Something went wrong" message will appear when accessing `/a` and `/p` routes in Portal stores
+
+
+##
+
+## Simulation
+
+
+
+1. Go to a portal store
+2. Go to the link `site.com/a` or `site.com/p`
+3. See a "Something went wrong" on the front
+
+
+##
+
+## Workaround
+
+
+N/A to `/a` path
+Register a redirect in the legacy CMS from `/p` to `/?ft=p`
+
+
+
+
+
diff --git a/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
new file mode 100644
index 000000000..c13e67a62
--- /dev/null
+++ b/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -0,0 +1,47 @@
+---
+title: '"Something went wrong" when adding an incomplete address and tried to edit it'
+id: 3rWGAr4K86JAetSBJ75q3h
+status: PUBLISHED
+createdAt: 2024-01-02T21:11:17.425Z
+updatedAt: 2024-01-02T21:11:17.955Z
+publishedAt: 2024-01-02T21:11:17.955Z
+firstPublishedAt: 2024-01-02T21:11:17.955Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it
+locale: en
+kiStatus: Backlog
+internalReference: 960064
+---
+
+## Summary
+
+
+During the checkout stage using a shopper with a complete profile, in the step of filling in the shipping data, by clicking on the option "Deliver to another address", if only the postal code is added and the shopper comes back to the address list (using the button "back to address book") and click on "Update selected address information" there is an error with message "Something went wrong".
+
+
+##
+
+## Simulation
+
+
+
+- Add items to cart and use an email with  a complete profile;
+- During the Checkout stage, when filling in the shipping data, click on "Deliver to another address";
+- Add a postal code and return to the shipping data by clicking on the "Back to address list" button;
+- Click on "Update selected address information".
+
+
+##
+
+## Workaround
+
+
+
+- Refresh the page if the error shows up.
+
+
+
+
diff --git a/docs/known-issues/en/sort-by-name-working-different-on-stores-integrated-before-a-date.md b/docs/known-issues/en/sort-by-name-working-different-on-stores-integrated-before-a-date.md
index 4b9102318..f9adec9af 100644
--- a/docs/known-issues/en/sort-by-name-working-different-on-stores-integrated-before-a-date.md
+++ b/docs/known-issues/en/sort-by-name-working-different-on-stores-integrated-before-a-date.md
@@ -3,8 +3,8 @@ title: 'Sort by name working different on stores integrated before a date'
 id: 96cQG19ZAmAtVT0ykZ4nF
 status: PUBLISHED
 createdAt: 2022-06-20T12:11:22.846Z
-updatedAt: 2022-11-25T21:58:18.041Z
-publishedAt: 2022-11-25T21:58:18.041Z
+updatedAt: 2024-07-01T18:48:26.055Z
+publishedAt: 2024-07-01T18:48:26.055Z
 firstPublishedAt: 2022-06-20T12:11:23.353Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: sort-by-name-working-different-on-stores-integrated-before-a-date
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 600468
 ---
 
diff --git a/docs/known-issues/en/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md b/docs/known-issues/en/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
new file mode 100644
index 000000000..7c1289f8d
--- /dev/null
+++ b/docs/known-issues/en/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
@@ -0,0 +1,45 @@
+---
+title: 'Space in street property in Postal Code JSON affects address field display at checkout'
+id: Rr3wSsdC5hxMS8ttK4kIj
+status: PUBLISHED
+createdAt: 2023-08-01T22:30:35.290Z
+updatedAt: 2024-07-01T18:49:10.379Z
+publishedAt: 2024-07-01T18:49:10.379Z
+firstPublishedAt: 2023-08-01T22:30:36.187Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout
+locale: en
+kiStatus: No Fix
+internalReference: 872935
+---
+
+## Summary
+
+
+When activating the use of the postal code API in the address form for countries that are not in the BR model (country, state, city, neighborhood, street), these countries that do not have all these fields filled in the API and need to be able to enter the other address data in the address form at checkout, the street field of the address block will not be available if the street property of JSON is with space, as it will be understood as filled and valid, which does not allow to proceed with the order.
+
+
+
+##
+
+## Simulation
+
+
+Create a cart in an EMEA store that uses Postal code and address form and in the postal code base the street field is with space " " .
+The address field will not be available to be filled in.
+
+
+##
+
+## Workaround
+
+
+Does not exist
+
+
+
+
+
diff --git a/docs/known-issues/en/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md b/docs/known-issues/en/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
index f39957306..f7b3014af 100644
--- a/docs/known-issues/en/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
+++ b/docs/known-issues/en/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
@@ -3,8 +3,8 @@ title: 'Space in warehouse ID causes internal logistics requests to fail'
 id: M8SsnABs2HgYsUvNnjCFx
 status: PUBLISHED
 createdAt: 2022-09-20T21:51:05.157Z
-updatedAt: 2023-01-05T19:34:07.126Z
-publishedAt: 2023-01-05T19:34:07.126Z
+updatedAt: 2024-02-16T20:24:53.145Z
+publishedAt: 2024-02-16T20:24:53.145Z
 firstPublishedAt: 2022-09-20T21:51:05.702Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: space-in-warehouse-id-causes-internal-logistics-requests-to-fail
 locale: en
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 654370
 ---
 
diff --git a/docs/known-issues/en/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md b/docs/known-issues/en/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
index a70b9ddc4..d215d1e2e 100644
--- a/docs/known-issues/en/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
+++ b/docs/known-issues/en/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
@@ -3,8 +3,8 @@ title: 'Special Characters cannot be used for CNPJ search on MasterData'
 id: 4sgob00QXkGYPC3TjSpQeN
 status: PUBLISHED
 createdAt: 2022-06-21T15:35:26.675Z
-updatedAt: 2022-11-25T22:13:02.870Z
-publishedAt: 2022-11-25T22:13:02.870Z
+updatedAt: 2023-08-07T13:52:30.392Z
+publishedAt: 2023-08-07T13:52:30.392Z
 firstPublishedAt: 2022-06-21T15:35:27.341Z
 contentType: knownIssue
 productTeam: Storage
diff --git a/docs/known-issues/en/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md b/docs/known-issues/en/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
new file mode 100644
index 000000000..c87879ada
--- /dev/null
+++ b/docs/known-issues/en/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
@@ -0,0 +1,49 @@
+---
+title: 'Special characters in invoiceNumber cause post-purchase flow to fail'
+id: 1tVPSLsB9SSZIF1KrNn3k2
+status: PUBLISHED
+createdAt: 2023-12-14T18:31:27.213Z
+updatedAt: 2023-12-14T18:31:27.801Z
+publishedAt: 2023-12-14T18:31:27.801Z
+firstPublishedAt: 2023-12-14T18:31:27.801Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail
+locale: en
+kiStatus: Backlog
+internalReference: 953285
+---
+
+## Summary
+
+
+Currently, SNO (Shipping Notification Order) accepts that an invoice number (invoiceNumber) is sent via API and UI with a "special character" at the end or beginning of the data, for example: "#123456".
+
+However, when invoices are received in this format, some flows carried out by the system involved in the post-purchase flow end up returning an error because they are unable to process or pass on the amount received. Examples of flows that may fail include tracking updates, order status updates for invoiced orders, communication with the gifcard hub system, and any other system that uses invoiceNumber data may have its flow compromised due to the use of special characters in the invoiceNumber field.
+
+
+##
+
+## Simulation
+
+
+1- Invoice an order by entering the following example invoice number: "#123456"; (special characters at the beginning of the number or at the end)
+
+2- Note that the order will not be updated to invoiced status
+
+3- In the case of flows involving a seller, in the Get Order of the seller's order it will be possible to see the saved invoice, but even then the marketplace order will not be updated to invoiced, as the system will not be able to pass on the invoice.
+
+
+##
+
+## Workaround
+
+
+For these cases, the alternative solution is not to use the "special characters" in the invoiceNumber composition.
+
+
+
+
+
diff --git a/docs/known-issues/en/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md b/docs/known-issues/en/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
index 92c336819..219b91c61 100644
--- a/docs/known-issues/en/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
+++ b/docs/known-issues/en/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
@@ -3,8 +3,8 @@ title: 'Special Characters on the SKU name breaks SKU selection on Portal Web St
 id: 1G4FSBVZqn44ke7YJTuBJA
 status: PUBLISHED
 createdAt: 2022-03-16T16:26:36.035Z
-updatedAt: 2022-11-25T22:11:14.593Z
-publishedAt: 2022-11-25T22:11:14.593Z
+updatedAt: 2024-02-16T20:29:47.269Z
+publishedAt: 2024-02-16T20:29:47.269Z
 firstPublishedAt: 2022-03-16T16:26:36.503Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 337933
 ---
 
diff --git a/docs/known-issues/en/specifications-multiplied-on-catalog.md b/docs/known-issues/en/specifications-multiplied-on-catalog.md
new file mode 100644
index 000000000..73e3a2d5e
--- /dev/null
+++ b/docs/known-issues/en/specifications-multiplied-on-catalog.md
@@ -0,0 +1,52 @@
+---
+title: 'Specifications multiplied on catalog'
+id: 2d4LXPrbVibMR8atXO6o8X
+status: PUBLISHED
+createdAt: 2023-10-16T12:48:03.714Z
+updatedAt: 2023-10-16T12:48:59.814Z
+publishedAt: 2023-10-16T12:48:59.814Z
+firstPublishedAt: 2023-10-16T12:48:04.717Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: specifications-multiplied-on-catalog
+locale: en
+kiStatus: Backlog
+internalReference: 919761
+---
+
+## Summary
+
+
+The marketplace can approve products sent by sellers on the Received Skus module.
+
+When a product has a sku specification that matches the specification that exists on the marketplace's category but is a new value, this new value is created on the marketplace's specification.
+
+The multiplied values can occur when more than one sku with the same "new value" is being approved at the same time on Received Skus in the same category (or tree) that the specification was created.
+
+If the specification is created on the root category (not recommended) this scenario could happen more easily.
+
+
+##
+
+## Simulation
+
+
+
+1. Create a sku specification on the root category;
+2. Choose 2 (or more)skus to approve on the Received Skus module that have the same sku specification value (the value can't previous exist on the marketplace side)
+3. Approve the skus (at the same time or in a small gap) and check if the specification values were multiplied by the number of skus approved.
+
+
+##
+
+## Workaround
+
+
+Approve the skus more slowly and avoid create specifications on the root category.
+
+
+
+
+
diff --git a/docs/known-issues/en/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md b/docs/known-issues/en/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
index 9ace7e109..50fcadcc2 100644
--- a/docs/known-issues/en/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
+++ b/docs/known-issues/en/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
@@ -3,8 +3,8 @@ title: 'spotPrice from the skuJson is incorrect for products with multiple Selle
 id: 6rgLJCE1DYPXZj1Pqt6hA2
 status: PUBLISHED
 createdAt: 2022-02-24T15:32:40.223Z
-updatedAt: 2022-11-25T22:10:27.000Z
-publishedAt: 2022-11-25T22:10:27.000Z
+updatedAt: 2024-02-16T20:30:08.928Z
+publishedAt: 2024-02-16T20:30:08.928Z
 firstPublishedAt: 2022-02-24T15:32:41.286Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 264791
 ---
 
diff --git a/docs/known-issues/en/status-on-transactions-list-doesnt-match-actual-state.md b/docs/known-issues/en/status-on-transactions-list-doesnt-match-actual-state.md
new file mode 100644
index 000000000..ad92eab51
--- /dev/null
+++ b/docs/known-issues/en/status-on-transactions-list-doesnt-match-actual-state.md
@@ -0,0 +1,43 @@
+---
+title: "Status on Transactions list doesn't match actual state"
+id: 3L0eXIO6aHmv9GSlPwCq3t
+status: PUBLISHED
+createdAt: 2024-03-22T16:23:32.369Z
+updatedAt: 2024-03-22T16:23:33.304Z
+publishedAt: 2024-03-22T16:23:33.304Z
+firstPublishedAt: 2024-03-22T16:23:33.304Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: status-on-transactions-list-doesnt-match-actual-state
+locale: en
+kiStatus: Backlog
+internalReference: 1004883
+---
+
+## Summary
+
+
+Some transactions may not match the actual state when you open them (indexing issue).
+
+
+##
+
+## Simulation
+
+
+There's no way to reproduce as this happens with random transactions.
+
+
+##
+
+## Workaround
+
+
+NA
+
+
+
+
+
diff --git a/docs/known-issues/en/stock-change-is-completed-even-after-receiving-error-500.md b/docs/known-issues/en/stock-change-is-completed-even-after-receiving-error-500.md
index 4a4fd756a..602675c83 100644
--- a/docs/known-issues/en/stock-change-is-completed-even-after-receiving-error-500.md
+++ b/docs/known-issues/en/stock-change-is-completed-even-after-receiving-error-500.md
@@ -3,8 +3,8 @@ title: 'Stock change is completed even after receiving error 500'
 id: 3dlP8iOBiL2tfPRvjm2kUZ
 status: PUBLISHED
 createdAt: 2022-06-20T12:40:08.834Z
-updatedAt: 2022-11-25T21:59:29.796Z
-publishedAt: 2022-11-25T21:59:29.796Z
+updatedAt: 2024-07-03T18:12:47.665Z
+publishedAt: 2024-07-03T18:12:47.665Z
 firstPublishedAt: 2022-06-20T12:40:09.126Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: stock-change-is-completed-even-after-receiving-error-500
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 388176
 ---
 
@@ -22,6 +22,7 @@ internalReference: 388176
 Client is trying to update the sku quantity in the inventory and the request received error 500. Despite the error, the quantity in stock is changed.
 
 
+##
 
 ## Simulation
 
@@ -32,6 +33,7 @@ But in the response we see the error 500, and the inventory we see the same valu
 
 
 
+##
 
 ## Workaround
 
diff --git a/docs/known-issues/en/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md b/docs/known-issues/en/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
index 9094ef0f9..33d6805ae 100644
--- a/docs/known-issues/en/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
+++ b/docs/known-issues/en/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
@@ -3,8 +3,8 @@ title: 'stockkeepingunit catalog API allows invalid commercial condition values'
 id: 1ONAspL4Wj9fdu2tYcX4Ur
 status: PUBLISHED
 createdAt: 2023-03-10T20:44:01.459Z
-updatedAt: 2023-03-10T20:44:02.006Z
-publishedAt: 2023-03-10T20:44:02.006Z
+updatedAt: 2024-07-01T18:48:57.278Z
+publishedAt: 2024-07-01T18:48:57.278Z
 firstPublishedAt: 2023-03-10T20:44:02.006Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 769053
 ---
 
diff --git a/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 4c1e6b418..57b0bc687 100644
--- a/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -3,7 +3,7 @@ title: 'StockKeepingUnitByEAN returns 404 for EANs with "/"'
 id: Pp3lE5Gu54gOw6liInte4
 status: DRAFT
 createdAt: 2022-02-25T12:23:55.903Z
-updatedAt: 2022-06-28T16:56:27.547Z
+updatedAt: 2024-02-16T20:28:49.215Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: stockkeepingunitbyean-returns-404-for-eans-with-
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 479244
 ---
 
diff --git a/docs/known-issues/en/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md b/docs/known-issues/en/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
index 0c96a6850..eb868feff 100644
--- a/docs/known-issues/en/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
+++ b/docs/known-issues/en/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
@@ -3,8 +3,8 @@ title: 'StockKeepingUnitInsertUpdate WebService method allows to insert existent
 id: 7wQ9uztQCTIQIWajMd6vaU
 status: PUBLISHED
 createdAt: 2022-01-21T15:19:32.095Z
-updatedAt: 2022-11-25T21:42:03.381Z
-publishedAt: 2022-11-25T21:42:03.381Z
+updatedAt: 2024-02-16T20:29:15.782Z
+publishedAt: 2024-02-16T20:29:15.782Z
 firstPublishedAt: 2022-11-02T13:54:17.227Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 419460
 ---
 
diff --git a/docs/known-issues/en/storefront-permissions-considers-inactive-organizations.md b/docs/known-issues/en/storefront-permissions-considers-inactive-organizations.md
new file mode 100644
index 000000000..e09bbd659
--- /dev/null
+++ b/docs/known-issues/en/storefront-permissions-considers-inactive-organizations.md
@@ -0,0 +1,45 @@
+---
+title: 'Storefront Permissions considers inactive organizations'
+id: 2GANYaXFMQpLGADajl4CbS
+status: PUBLISHED
+createdAt: 2023-10-27T22:08:14.267Z
+updatedAt: 2023-10-27T22:15:24.802Z
+publishedAt: 2023-10-27T22:15:24.802Z
+firstPublishedAt: 2023-10-27T22:08:14.965Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: storefront-permissions-considers-inactive-organizations
+locale: en
+kiStatus: Backlog
+internalReference: 927174
+---
+
+## Summary
+
+
+When a user has more than one organization assigned to them, and the first registered is inactive, it's not recognized as any organization is assigned after login.
+
+
+##
+
+## Simulation
+
+
+
+- Create two organizations and assign the same user/email;
+- Inactive the 1st organization created;
+- Log in to the website.
+
+
+##
+
+## Workaround
+
+
+Remove the user/email from the inactive organization.
+
+
+
+
diff --git a/docs/known-issues/en/stucked-not-found-routes-on-platform.md b/docs/known-issues/en/stucked-not-found-routes-on-platform.md
index bed4316cf..8da5baaf4 100644
--- a/docs/known-issues/en/stucked-not-found-routes-on-platform.md
+++ b/docs/known-issues/en/stucked-not-found-routes-on-platform.md
@@ -3,8 +3,8 @@ title: 'Stucked not found routes on platform'
 id: iAGlRJtK1KMBGxH2tAsrX
 status: PUBLISHED
 createdAt: 2023-04-19T15:54:48.241Z
-updatedAt: 2023-04-19T16:00:28.874Z
-publishedAt: 2023-04-19T16:00:28.874Z
+updatedAt: 2023-06-28T15:56:47.493Z
+publishedAt: 2023-06-28T15:56:47.493Z
 firstPublishedAt: 2023-04-19T15:54:48.788Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/en/subscribers-report-does-not-show-active-subscriptions-correctly.md b/docs/known-issues/en/subscribers-report-does-not-show-active-subscriptions-correctly.md
index b67a69dee..7d51d6814 100644
--- a/docs/known-issues/en/subscribers-report-does-not-show-active-subscriptions-correctly.md
+++ b/docs/known-issues/en/subscribers-report-does-not-show-active-subscriptions-correctly.md
@@ -3,8 +3,8 @@ title: 'Subscribers report does not show active subscriptions correctly'
 id: 4sqvm1v4CbCJLQ3HBBVTmp
 status: PUBLISHED
 createdAt: 2022-05-27T19:44:57.301Z
-updatedAt: 2022-11-25T22:02:30.682Z
-publishedAt: 2022-11-25T22:02:30.682Z
+updatedAt: 2024-07-01T18:48:23.947Z
+publishedAt: 2024-07-01T18:48:23.947Z
 firstPublishedAt: 2022-05-27T19:44:57.688Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: subscribers-report-does-not-show-active-subscriptions-correctly
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 587556
 ---
 
diff --git a/docs/known-issues/en/subscription-event-history-out-of-order.md b/docs/known-issues/en/subscription-event-history-out-of-order.md
new file mode 100644
index 000000000..fbce47bb0
--- /dev/null
+++ b/docs/known-issues/en/subscription-event-history-out-of-order.md
@@ -0,0 +1,48 @@
+---
+title: 'Subscription event history out of order'
+id: 5w78uE60pzjfOagGnRA2d5
+status: PUBLISHED
+createdAt: 2023-08-01T18:53:21.754Z
+updatedAt: 2023-08-01T18:53:22.303Z
+publishedAt: 2023-08-01T18:53:22.303Z
+firstPublishedAt: 2023-08-01T18:53:22.303Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: subscription-event-history-out-of-order
+locale: en
+kiStatus: Backlog
+internalReference: 872697
+---
+
+## Summary
+
+
+Currently, the Subscription History in My subscription area , does not display the events in a predefined order, so it can show the events in non-chronological order;
+
+
+##
+
+## Simulation
+
+
+Using a subscription that has had more than one order generated;
+
+1-  Enter the history area;
+2- The list of events displayed will not be in chronological order;
+
+NOTE: In some cases, the scenario may not be noticed because only a few events are out of chronological order.
+
+
+##
+
+## Workaround
+
+
+
+there is currently no workaround for this behavior
+
+
+
+
diff --git a/docs/known-issues/en/subscriptions-dashboard-with-conflicting-information.md b/docs/known-issues/en/subscriptions-dashboard-with-conflicting-information.md
index 88d306f58..082122acc 100644
--- a/docs/known-issues/en/subscriptions-dashboard-with-conflicting-information.md
+++ b/docs/known-issues/en/subscriptions-dashboard-with-conflicting-information.md
@@ -3,8 +3,8 @@ title: 'Subscriptions dashboard with conflicting information'
 id: WvoqrD7xvaAJ6NVOLpU1G
 status: PUBLISHED
 createdAt: 2022-05-27T20:01:11.189Z
-updatedAt: 2022-11-25T22:02:26.699Z
-publishedAt: 2022-11-25T22:02:26.699Z
+updatedAt: 2024-02-16T20:28:30.718Z
+publishedAt: 2024-02-16T20:28:30.718Z
 firstPublishedAt: 2022-05-27T20:01:11.715Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: subscriptions-dashboard-with-conflicting-information
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 587579
 ---
 
diff --git a/docs/known-issues/en/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md b/docs/known-issues/en/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
new file mode 100644
index 000000000..a966a7514
--- /dev/null
+++ b/docs/known-issues/en/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
@@ -0,0 +1,45 @@
+---
+title: 'Subscriptions not executed due to data indexing failure or masterdata query failure'
+id: 1PspxNexEEz4GvJ5BpZZgH
+status: PUBLISHED
+createdAt: 2024-01-04T20:27:03.576Z
+updatedAt: 2024-07-09T17:24:39.295Z
+publishedAt: 2024-07-09T17:24:39.295Z
+firstPublishedAt: 2024-01-04T20:27:04.193Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure
+locale: en
+kiStatus: Backlog
+internalReference: 961526
+---
+
+## Summary
+
+
+The creation of subscription requests depends on the return of a query made to the subscriptions' database, this query is made periodically to identify which subscriptions should be executed in that period, if this query fails or does not return a particular subscription, its cycle is not executed, and no error is logged, thus resulting in a subscription with the nextPurchaseDate in the past.
+
+
+##
+
+## Simulation
+
+
+We have no way of simulating this scenario due to the dependence on other systems.
+
+
+##
+
+## Workaround
+
+
+To adjust the `nextPurchaseDate`, the end user can pause the subscription and reactivate it. This action will cause the subscription system to recalculate the execution date and the `nextPurchaseDate` will be updated correctly.
+
+Or the customer can update the `nextPurchaseDate` of the user's subscription to a future date via the API.
+
+
+
+
+
diff --git a/docs/known-issues/en/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md b/docs/known-issues/en/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
new file mode 100644
index 000000000..c94359b0a
--- /dev/null
+++ b/docs/known-issues/en/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
@@ -0,0 +1,45 @@
+---
+title: 'Subscriptions simulation returned error when PickupPointID contains special characters'
+id: aM2So6TmVffZ1ywtQsknS
+status: PUBLISHED
+createdAt: 2023-09-19T17:31:47.442Z
+updatedAt: 2024-07-01T18:49:12.303Z
+publishedAt: 2024-07-01T18:49:12.303Z
+firstPublishedAt: 2023-09-19T17:31:48.217Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters
+locale: en
+kiStatus: No Fix
+internalReference: 903332
+---
+
+## Summary
+
+
+To place a subscription order or update a subscription, the subscription system carries out a simulation, and in this simulation it uses the delivery data returned by the logistics system, and if within this data there is a pick up point whose ID is underline, the subscription system will not be able to choose the SLA correctly, thus generating the error "Invalid AddressProvider:...." in the simulation and consequently will not generate the order.
+
+
+##
+
+## Simulation
+
+
+1- Create a pick point whose ID has an underline
+2- Make a subscription request by choosing the pick point created in step 1.
+3- Wait for the first cycle to run and see that it doesn't run and that the subscription panel registers an error saying that the address is invalid.
+
+
+##
+
+## Workaround
+
+
+Delete the pick up point whose ID is underlined and create a new one and update the subscription so that it uses this new pick up point.
+
+
+
+
+
diff --git a/docs/known-issues/en/substitute-words-with-less-than-3-characters-does-not-work.md b/docs/known-issues/en/substitute-words-with-less-than-3-characters-does-not-work.md
index 477fedaad..f850a8398 100644
--- a/docs/known-issues/en/substitute-words-with-less-than-3-characters-does-not-work.md
+++ b/docs/known-issues/en/substitute-words-with-less-than-3-characters-does-not-work.md
@@ -3,8 +3,8 @@ title: 'Substitute words with less than 3 characters does not work'
 id: 5sAdcBkmVVnRoQD3WUBNJ0
 status: PUBLISHED
 createdAt: 2022-06-08T20:03:47.576Z
-updatedAt: 2022-11-25T21:45:35.491Z
-publishedAt: 2022-11-25T21:45:35.491Z
+updatedAt: 2024-07-01T18:47:49.328Z
+publishedAt: 2024-07-01T18:47:49.328Z
 firstPublishedAt: 2022-06-08T20:03:48.005Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: substitute-words-with-less-than-3-characters-does-not-work
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 282500
 ---
 
diff --git a/docs/known-issues/en/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md b/docs/known-issues/en/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
new file mode 100644
index 000000000..c204cfae3
--- /dev/null
+++ b/docs/known-issues/en/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
@@ -0,0 +1,47 @@
+---
+title: 'Summary information translate into English after logging in via update selected address information'
+id: 6g05yZcdGHZqm0zeozUH8f
+status: PUBLISHED
+createdAt: 2024-02-07T14:58:10.527Z
+updatedAt: 2024-02-07T14:58:11.389Z
+publishedAt: 2024-02-07T14:58:11.389Z
+firstPublishedAt: 2024-02-07T14:58:11.389Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: summary-information-translate-into-english-after-logging-in-via-update-selected-address-information
+locale: en
+kiStatus: Backlog
+internalReference: 978571
+---
+
+## Summary
+
+
+In Spanish accounts, logging in at checkout via "Update selected address information" after identification with a complete profile makes some texts in the summary to translate into English.
+
+
+##
+
+## Simulation
+
+
+
+- Add an item to the cart and identify it using an email with a complete profile so the data is filled automatically;
+- The personal and address will be masked;
+- Go to the Shipping step and click on "Update selected address information";
+- Log in;
+- Notice that some texts in the Summary will be switched to English.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md b/docs/known-issues/en/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
new file mode 100644
index 000000000..e982397bb
--- /dev/null
+++ b/docs/known-issues/en/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
@@ -0,0 +1,45 @@
+---
+title: 'Swiping product-image after zooming in does not revert the zoom, causing display issues'
+id: 41UVOcLabjyv29Buupj1MO
+status: PUBLISHED
+createdAt: 2024-01-29T18:05:22.470Z
+updatedAt: 2024-01-29T18:05:23.035Z
+publishedAt: 2024-01-29T18:05:23.035Z
+firstPublishedAt: 2024-01-29T18:05:23.035Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues
+locale: en
+kiStatus: Backlog
+internalReference: 491180
+---
+
+## Summary
+
+
+When using the vtex.store-components product-image, when swiping an image to the side after clicking it for zoom, the first image will keep zoomed in, causing rendering issues when the user swipes back to it.
+
+
+##
+
+## Simulation
+
+
+In a PDP that uses vtex.store-components product-image, access the mobile version of a product with at least two images.
+Click to zoom in the first image, then swipe to the next one.
+Click to zoom the second one, and swipe back to the first.
+Doing it back and forth will eventually cause some display issues to the currently zoomed in image.
+Clicking on the image again to zoom out resets it back to normal.
+
+
+##
+
+## Workaround
+
+
+Use arrows to navigate between images and reduce the chance of users opting to swipe it.
+
+Set the prop "zoomMode": "hover" or "zoomMode":"open-modal". It prevents swiping when the image is zoomed, but changes behavior slightly.
+
diff --git a/docs/known-issues/en/synonyms-import-presenting-success-even-for-failed-actions.md b/docs/known-issues/en/synonyms-import-presenting-success-even-for-failed-actions.md
new file mode 100644
index 000000000..86729a072
--- /dev/null
+++ b/docs/known-issues/en/synonyms-import-presenting-success-even-for-failed-actions.md
@@ -0,0 +1,42 @@
+---
+title: 'Synonyms import presenting success even for failed actions'
+id: 4EhvPXp1vXBf2596mANlX6
+status: PUBLISHED
+createdAt: 2024-02-19T22:05:46.953Z
+updatedAt: 2024-02-19T22:05:47.817Z
+publishedAt: 2024-02-19T22:05:47.817Z
+firstPublishedAt: 2024-02-19T22:05:47.817Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: synonyms-import-presenting-success-even-for-failed-actions
+locale: en
+kiStatus: Backlog
+internalReference: 984557
+---
+
+## Summary
+
+
+The synonyms importing for CSV files will return a success message even for actions that failed.
+
+
+##
+
+## Simulation
+
+
+Try importing an invalid CSV file, for example, out from the expected formatting of three columns.
+
+
+##
+
+## Workaround
+
+
+Not required. Note that successfully imported synonyms should instantly appear on the list after reloading the page.
+
+
+
+
diff --git a/docs/known-issues/en/synonyms-not-shown-in-the-explained-search.md b/docs/known-issues/en/synonyms-not-shown-in-the-explained-search.md
new file mode 100644
index 000000000..424957162
--- /dev/null
+++ b/docs/known-issues/en/synonyms-not-shown-in-the-explained-search.md
@@ -0,0 +1,42 @@
+---
+title: 'Synonyms not shown in the explained search'
+id: 6twjWHNHdarFV5pz1aTfeb
+status: PUBLISHED
+createdAt: 2023-03-20T16:57:15.640Z
+updatedAt: 2023-10-18T00:50:47.829Z
+publishedAt: 2023-10-18T00:50:47.829Z
+firstPublishedAt: 2023-03-20T16:57:16.425Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: synonyms-not-shown-in-the-explained-search
+locale: en
+kiStatus: Backlog
+internalReference: 774307
+---
+
+## Summary
+
+
+Some products may not present their synonyms on the explained search admin page. This usually happens with unidirectional synonyms.
+
+
+##
+
+## Simulation
+
+
+Create a unidirectional synonym and then check it on the explained search. If it doesn't appear, it doesn't mean today that the synonym isn't working.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/system-considering-seller-1-for-rule-sellers-limit.md b/docs/known-issues/en/system-considering-seller-1-for-rule-sellers-limit.md
index 47361b89e..be24c9be6 100644
--- a/docs/known-issues/en/system-considering-seller-1-for-rule-sellers-limit.md
+++ b/docs/known-issues/en/system-considering-seller-1-for-rule-sellers-limit.md
@@ -3,8 +3,8 @@ title: 'System considering seller 1 for rule sellers limit'
 id: 1bUax0hSCVrnFPZ4g1VWOa
 status: PUBLISHED
 createdAt: 2022-04-20T20:43:57.392Z
-updatedAt: 2022-11-25T21:52:50.788Z
-publishedAt: 2022-11-25T21:52:50.788Z
+updatedAt: 2024-02-16T20:28:37.189Z
+publishedAt: 2024-02-16T20:28:37.189Z
 firstPublishedAt: 2022-04-20T20:43:57.844Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: system-considering-seller-1-for-rule-sellers-limit
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 564614
 ---
 
diff --git a/docs/known-issues/en/tags-wont-sometimes-appear-on-list-format-plp-view.md b/docs/known-issues/en/tags-wont-sometimes-appear-on-list-format-plp-view.md
new file mode 100644
index 000000000..55c3690b8
--- /dev/null
+++ b/docs/known-issues/en/tags-wont-sometimes-appear-on-list-format-plp-view.md
@@ -0,0 +1,46 @@
+---
+title: "Tags won't sometimes appear on List Format PLP View"
+id: 4CPSP7GjBfUgxFvmnAhK8z
+status: PUBLISHED
+createdAt: 2024-02-15T13:58:42.405Z
+updatedAt: 2024-02-15T13:58:43.494Z
+publishedAt: 2024-02-15T13:58:43.494Z
+firstPublishedAt: 2024-02-15T13:58:43.494Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: tags-wont-sometimes-appear-on-list-format-plp-view
+locale: en
+kiStatus: No Fix
+internalReference: 982200
+---
+
+## Summary
+
+
+When viewing the PLP in list view, tags for items.
+
+
+##
+
+## Simulation
+
+
+Create tags for your items and make the necessary configurations change.
+Enable your PLP to be viewed in both grid and list style.
+In grid style, tags will appear as they should.
+In list style, the tags are missing.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md b/docs/known-issues/en/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
new file mode 100644
index 000000000..dfe69ecd7
--- /dev/null
+++ b/docs/known-issues/en/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
@@ -0,0 +1,48 @@
+---
+title: 'Tax Form UI is not displayng Marketing Tags DropDown'
+id: Xqg6yYfOvVtP0TwZ2RIAk
+status: PUBLISHED
+createdAt: 2024-07-01T13:33:50.657Z
+updatedAt: 2024-07-01T13:34:05.936Z
+publishedAt: 2024-07-01T13:34:05.936Z
+firstPublishedAt: 2024-07-01T13:33:51.430Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: tax-form-ui-is-not-displayng-marketing-tags-dropdown
+locale: en
+kiStatus: Backlog
+internalReference: 1058148
+---
+
+## Summary
+
+
+When saving taxes in the promotions module, the dropdown value for "at least one of the following" or "all of the following" is not shown after the tax is saved. Consequently, the user cannot figure out which of them is being used.
+
+
+##
+
+## Simulation
+
+
+1 - In the promotions module, open the tax form.
+2 - Fill in the Marketing tags form with multiple values.
+3 -  Save the form
+4 - check it again, the form will come out empty:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/kGbgj8MON0fVzgmv19hKS1F9u/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/en/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md b/docs/known-issues/en/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
new file mode 100644
index 000000000..617235c0d
--- /dev/null
+++ b/docs/known-issues/en/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
@@ -0,0 +1,44 @@
+---
+title: "Tax hub request doesn't sum discounts when manual price is applied"
+id: 3p8mpZALGS95pB9j4CclHi
+status: PUBLISHED
+createdAt: 2023-11-08T18:07:23.968Z
+updatedAt: 2024-07-01T18:49:18.565Z
+publishedAt: 2024-07-01T18:49:18.565Z
+firstPublishedAt: 2023-11-08T18:07:24.393Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied
+locale: en
+kiStatus: No Fix
+internalReference: 932667
+---
+
+## Summary
+
+
+When a manual price is applied to an item to decrease the price, the tax hub request doesn't sum it and shows the discount totals always as 0.
+
+
+##
+
+## Simulation
+
+
+
+- Set a manual price lower than the current price for an item;
+- The tax hub request won't sum the discount in the totals.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md b/docs/known-issues/en/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
new file mode 100644
index 000000000..dcf805ef0
--- /dev/null
+++ b/docs/known-issues/en/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
@@ -0,0 +1,45 @@
+---
+title: 'Tax Service consider the same price for items that appear more than once when using Assembly Option'
+id: 62a1S9SZmGsY58BcV6D58C
+status: PUBLISHED
+createdAt: 2023-09-25T13:27:15.638Z
+updatedAt: 2023-09-27T12:47:49.130Z
+publishedAt: 2023-09-27T12:47:49.130Z
+firstPublishedAt: 2023-09-25T13:27:16.233Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option
+locale: en
+kiStatus: Fixed
+internalReference: 906518
+---
+
+## Summary
+
+
+When using Assembly Options, if the item is added again to the cart, it will appear twice and the Tax Service will consider only the price for that item that is first in the cart, causing tax divergence values when placing an order.
+
+
+##
+
+## Simulation
+
+
+
+- Configure Tax Hub in an account;
+- Configure Assembly Options;
+- Add an item that was included in the Assembly Option to the cart;
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md b/docs/known-issues/en/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
new file mode 100644
index 000000000..df621daf6
--- /dev/null
+++ b/docs/known-issues/en/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
@@ -0,0 +1,46 @@
+---
+title: "Tax Service doesn't apply free shipping promotions with promotion that splits items"
+id: 5w7mcNyJhTA77sRULPgrTx
+status: PUBLISHED
+createdAt: 2024-03-06T20:07:56.556Z
+updatedAt: 2024-03-06T20:07:57.240Z
+publishedAt: 2024-03-06T20:07:57.240Z
+firstPublishedAt: 2024-03-06T20:07:57.240Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items
+locale: en
+kiStatus: Backlog
+internalReference: 995527
+---
+
+## Summary
+
+
+When using the tax service, if there is a promotion that splits items, for example, a More for Less promotion and a free shipping promotion, the free shipping is not applied correctly for all items in the tax service request, causing a wrong calculation and avoiding the order being created with the message "The requested order could not be created. Please try again."
+
+
+##
+
+## Simulation
+
+
+
+- Configure Tax Service;
+- Create a More for Less promotion;
+- Create a free shipping promotion;
+- Assemble a cart and try to place the order.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md b/docs/known-issues/en/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
new file mode 100644
index 000000000..8679e8a8e
--- /dev/null
+++ b/docs/known-issues/en/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
@@ -0,0 +1,45 @@
+---
+title: "Tax Service doesn't consider nominal promotions when placing orders"
+id: 1vCs62opRc2iDw0NmYqlT7
+status: PUBLISHED
+createdAt: 2023-09-14T17:48:37.761Z
+updatedAt: 2023-09-14T17:48:38.630Z
+publishedAt: 2023-09-14T17:48:38.630Z
+firstPublishedAt: 2023-09-14T17:48:38.630Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-doesnt-consider-nominal-promotions-when-placing-orders
+locale: en
+kiStatus: Backlog
+internalReference: 900120
+---
+
+## Summary
+
+
+When using tax service, if there is a nominal promotion applied in the cart and an item split happens, the request checkout doesn't have the nominal promotion applied, not allowing to finish the purchase, and the message "The requested order could not be created. Please try again" will be shown.
+
+
+##
+
+## Simulation
+
+
+
+- Create a nominal promotion;
+- Add items to the cart, make sure the items split;
+- Try to finish the purchase.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md b/docs/known-issues/en/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
new file mode 100644
index 000000000..775f441d4
--- /dev/null
+++ b/docs/known-issues/en/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
@@ -0,0 +1,44 @@
+---
+title: 'Tax service request uses shippingData.address even when a cart has two selected address'
+id: 21t5R3AmcllYam4mXqX6lY
+status: PUBLISHED
+createdAt: 2024-08-01T13:11:10.623Z
+updatedAt: 2024-08-01T13:11:11.796Z
+publishedAt: 2024-08-01T13:11:11.796Z
+firstPublishedAt: 2024-08-01T13:11:11.796Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address
+locale: en
+kiStatus: Backlog
+internalReference: 1074168
+---
+
+## Summary
+
+
+In a cart with items for pickup and delivery, checkout's simulation only considers the information on the shippingData.address object for the tax service request. For example, considering those addresses are from different states, and the tax provider considers different taxes for each state, one of the items will have the wrong tax applied.
+
+
+##
+
+## Simulation
+
+
+
+- Configure Tax Service;
+- Add two items to a cart with different selected addresses: one for pickup and the other for delivery.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/tax-service-uses-document-data-instead-of-customer-email.md b/docs/known-issues/en/tax-service-uses-document-data-instead-of-customer-email.md
index 3fdf895a9..8978e802f 100644
--- a/docs/known-issues/en/tax-service-uses-document-data-instead-of-customer-email.md
+++ b/docs/known-issues/en/tax-service-uses-document-data-instead-of-customer-email.md
@@ -3,8 +3,8 @@ title: 'Tax service uses document data instead of customer email'
 id: IOu1ZV40Q5yHjgbcS9C15
 status: PUBLISHED
 createdAt: 2022-03-23T17:50:15.754Z
-updatedAt: 2022-11-25T21:53:38.397Z
-publishedAt: 2022-11-25T21:53:38.397Z
+updatedAt: 2024-02-16T20:28:42.991Z
+publishedAt: 2024-02-16T20:28:42.991Z
 firstPublishedAt: 2022-03-23T17:50:16.302Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: tax-service-uses-document-data-instead-of-customer-email
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 548671
 ---
 
diff --git a/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
new file mode 100644
index 000000000..668017aa5
--- /dev/null
+++ b/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -0,0 +1,50 @@
+---
+title: "Telesales search doesn't accept special characters aside from "@"."
+id: 5eTb6KlR07dOP06BGhovoL
+status: PUBLISHED
+createdAt: 2024-07-29T17:21:34.828Z
+updatedAt: 2024-07-29T17:21:35.918Z
+publishedAt: 2024-07-29T17:21:35.918Z
+firstPublishedAt: 2024-07-29T17:21:35.918Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: telesales-search-doesnt-accept-special-characters-aside-from
+locale: en
+kiStatus: Backlog
+internalReference: 1072418
+---
+
+## Summary
+
+
+Currently, when using the telesales search box, an user can impersonate shoppers to assist in purchases and, to do so, it is necessary to input, in the native searchbox, the email of whom's going to be impersonated.
+
+However, when using this tool, emails that contains special characters, such as "+", "$", "#", etc... Are not identified by the search tool, making it return a "not found" response.
+
+
+##
+
+## Simulation
+
+
+1 - in a store that has the telesales (https://help.vtex.com/en/tutorial/telesales-features--UqhiccIRIK2KD0OqkzJaS) implemented, access it via a user with the required authentication.
+
+2 - create an email, in the store's masterdata, that uses a special character such as "+"
+
+3 - try usingthe telesales impersonate toolbar for search for the given email - it will return a "not found" response.
+
+4 - adjusting this same email to remove the special character and then searching again will normalize the situation.
+
+
+##
+
+## Workaround
+
+
+Adapt the user email addresses to not use special characters.
+
+
+
+
diff --git a/docs/known-issues/en/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md b/docs/known-issues/en/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..64060a056
--- /dev/null
+++ b/docs/known-issues/en/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
@@ -0,0 +1,50 @@
+---
+title: 'Text in Add to Cart Button are not being translated using site editor'
+id: 7rA62h80a1LpDWjgd3SImp
+status: PUBLISHED
+createdAt: 2024-05-02T17:33:41.019Z
+updatedAt: 2024-07-03T18:28:56.642Z
+publishedAt: 2024-07-03T18:28:56.642Z
+firstPublishedAt: 2024-05-02T17:33:42.188Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: text-in-add-to-cart-button-are-not-being-translated-using-site-editor
+locale: en
+kiStatus: Backlog
+internalReference: 1026103
+---
+
+## Summary
+
+
+When trying to translate a text using the site editor for the Add to Cart Button, the changes won't apply in the store front.
+
+
+##
+
+## Simulation
+
+
+
+1. Open site editor
+2. Select Add to Cart Button
+3. Change the text label in the button to anything desired
+4. Save changes
+5. Visualize the page and the text will be the same no matter the locale selected
+
+
+##
+
+## Workaround
+
+
+Make sure iconLabel is empty in both the store code and site editor.
+If you are not sure if it's empty in the site editor, you can reset the content by going through the site editor version > reset.
+
+Follow the documentation here and the contexts here to set the label as desired instead.
+
+
+
+
diff --git a/docs/known-issues/en/text-in-infocard-is-not-being-translated-using-site-editor.md b/docs/known-issues/en/text-in-infocard-is-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..4141dc029
--- /dev/null
+++ b/docs/known-issues/en/text-in-infocard-is-not-being-translated-using-site-editor.md
@@ -0,0 +1,52 @@
+---
+title: 'Text in InfoCard is not being translated using site editor'
+id: 5HYTZvxkPoTZltMkZcVfVO
+status: PUBLISHED
+createdAt: 2024-06-13T18:47:41.470Z
+updatedAt: 2024-07-03T13:58:33.037Z
+publishedAt: 2024-07-03T13:58:33.037Z
+firstPublishedAt: 2024-06-13T18:47:42.396Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: text-in-infocard-is-not-being-translated-using-site-editor
+locale: en
+kiStatus: Backlog
+internalReference: 1049491
+---
+
+## Summary
+
+
+When trying to translate a text using the site editor for the info card component, the changes won't apply in the store front.
+
+
+##
+
+## Simulation
+
+
+
+1. Open site editor
+2. Select info card component
+3. Change the text label
+4. Save changes
+5. Visualize the page and the text will be the same no matter the locale selected
+
+
+##
+
+## Workaround
+
+
+Make sure the headline is empty in both the store code and site editor.
+If you are not sure if it's empty in the site editor, you can reset the content by going through the site editor version > reset.
+
+Follow the documentation here and the contexts here to set the label as desired instead.
+
+If this still doesn't solve you can you a rich text and an image component separately inside the info card.
+
+
+
+
diff --git a/docs/known-issues/en/text-in-store-login-are-not-being-translated-using-site-editor.md b/docs/known-issues/en/text-in-store-login-are-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..e54c87a36
--- /dev/null
+++ b/docs/known-issues/en/text-in-store-login-are-not-being-translated-using-site-editor.md
@@ -0,0 +1,53 @@
+---
+title: 'Text in Store Login are not being translated using site editor'
+id: 6DptiKTxtOcYIJEgJlZCmo
+status: PUBLISHED
+createdAt: 2023-11-08T13:33:41.296Z
+updatedAt: 2024-07-03T18:29:45.491Z
+publishedAt: 2024-07-03T18:29:45.491Z
+firstPublishedAt: 2023-11-08T13:33:41.967Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: text-in-store-login-are-not-being-translated-using-site-editor
+locale: en
+kiStatus: Backlog
+internalReference: 911757
+---
+
+## Summary
+
+
+When trying to translate a text using the site editor for the Store Login, the changes won't apply in the store front.
+
+
+##
+
+## Simulation
+
+
+
+1. Open site editor
+2. Select Store Login block
+3. Change the text label in the login to anything desired
+4. Save changes
+5. Visualize the page and the text will be the same no matter the locale selected
+
+
+
+##
+
+## Workaround
+
+
+Make sure iconLabel is empty in both the store code and site editor.
+If you are not sure if it's empty in the site editor, you can reset the content by going through the site editor version > reset.
+ ![](https://vtexhelp.zendesk.com/attachments/token/PXovY6zVHdqqhxjodbtMqdXAa/?name=image.png)
+
+Follow the documentation here and the contexts here to set the label as desired instead.
+
+
+
+
+
diff --git a/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index 9a21db818..dacdb49fd 100644
--- a/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -3,8 +3,8 @@ title: 'Textlink created with " " on Marketplace upon approvals - Reoccurence'
 id: 2afynQ9MwaHPMPWyhx80Tp
 status: PUBLISHED
 createdAt: 2023-04-24T19:36:10.185Z
-updatedAt: 2023-05-08T17:47:01.002Z
-publishedAt: 2023-05-08T17:47:01.002Z
+updatedAt: 2023-07-13T15:25:43.450Z
+publishedAt: 2023-07-13T15:25:43.450Z
 firstPublishedAt: 2023-04-24T19:36:10.701Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: textlink-created-with-on-marketplace-upon-approvals-reoccurence
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 795900
 ---
 
@@ -25,15 +25,11 @@ The SKU is sent back for approval on the Received Skus module, but it isn't poss
 
 
 
-
-
 ##
 
 ## Simulation
 
 
-
-
 1) It usually occurs with an received skus generic error upon attempting to approve (this doest not happen for every case).
 
 2) A product will be created on the marketplace's catalog with the faulty textlinks.
@@ -43,8 +39,6 @@ The SKU is sent back for approval on the Received Skus module, but it isn't poss
 4) Attempting to approve it once again will display an error.
 
 
-
-
 ##
 
 ## Workaround
@@ -52,3 +46,6 @@ The SKU is sent back for approval on the Received Skus module, but it isn't poss
 
 Manually/API updating the textlinks of the product under this scenario.
 
+
+
+
diff --git a/docs/known-issues/en/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md b/docs/known-issues/en/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
index e3a1c5aab..445923a9f 100644
--- a/docs/known-issues/en/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
+++ b/docs/known-issues/en/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
@@ -3,8 +3,8 @@ title: 'The field Judet county is not showing as saved when address editing on R
 id: 5aOtbUdNXPzOpuvLnmJtMf
 status: PUBLISHED
 createdAt: 2022-02-24T14:52:37.615Z
-updatedAt: 2022-11-25T22:02:22.409Z
-publishedAt: 2022-11-25T22:02:22.409Z
+updatedAt: 2024-02-16T20:25:19.581Z
+publishedAt: 2024-02-16T20:25:19.581Z
 firstPublishedAt: 2022-05-18T18:46:59.023Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 394658
 ---
 
@@ -22,6 +22,7 @@ internalReference: 394658
 For stores from Romania on _**My Account**_ page there is a field named "Judet", county in english, that is not showing as saved when editing address.
 
 
+##
 
 ## Simulation
 
@@ -32,9 +33,14 @@ For stores from Romania on _**My Account**_ page there is a field named "Judet",
 - Click on Edit Address and the previous address is still in the fields of address except for Judet.
 
 
+##
 
 ## Workaround
 
 
 There is no workaround available for that in the My Account itself, but maybe using our Master Data APIs can update or create those addresses.
 
+
+
+
+
diff --git a/docs/known-issues/en/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md b/docs/known-issues/en/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
index 4b17e5b1a..5575483cd 100644
--- a/docs/known-issues/en/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
+++ b/docs/known-issues/en/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
@@ -3,8 +3,8 @@ title: 'The holiday is not shown in the list after using the API to create (PUT)
 id: WqzSTP6oFwk4MbGaO5mIU
 status: PUBLISHED
 createdAt: 2022-05-02T22:26:55.630Z
-updatedAt: 2022-11-25T22:00:07.142Z
-publishedAt: 2022-11-25T22:00:07.142Z
+updatedAt: 2024-02-16T20:28:28.551Z
+publishedAt: 2024-02-16T20:28:28.551Z
 firstPublishedAt: 2022-05-02T22:26:56.888Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 571040
 ---
 
diff --git a/docs/known-issues/en/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md b/docs/known-issues/en/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
index 4a4f8e2fa..c1de3abb1 100644
--- a/docs/known-issues/en/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
+++ b/docs/known-issues/en/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
@@ -3,8 +3,8 @@ title: 'The installments request at the gateway to a merchant other than the mar
 id: Xo2YO6ZM9Jj0ONZjXrrrJ
 status: PUBLISHED
 createdAt: 2022-03-27T21:08:39.176Z
-updatedAt: 2022-11-25T22:05:55.885Z
-publishedAt: 2022-11-25T22:05:55.885Z
+updatedAt: 2024-02-16T20:29:17.920Z
+publishedAt: 2024-02-16T20:29:17.920Z
 firstPublishedAt: 2022-03-27T21:08:39.738Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 391197
 ---
 
diff --git a/docs/known-issues/en/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md b/docs/known-issues/en/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
new file mode 100644
index 000000000..44c5a58ed
--- /dev/null
+++ b/docs/known-issues/en/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
@@ -0,0 +1,43 @@
+---
+title: 'The legacy Adyen connector is unable of asynchronously denying payment capture'
+id: 5tdNyMfA5zeNg4sCbPQgUc
+status: PUBLISHED
+createdAt: 2024-02-02T15:15:57.980Z
+updatedAt: 2024-02-02T15:15:58.839Z
+publishedAt: 2024-02-02T15:15:58.839Z
+firstPublishedAt: 2024-02-02T15:15:58.839Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture
+locale: en
+kiStatus: Backlog
+internalReference: 976005
+---
+
+## Summary
+
+
+The legacy Adyen connector captures the payment whenever it receives the `"response":"[capture-received]"` field. However, this event only indicates that the capture has been received and will be processed asynchronously. This behavior prevents captures from being denied, as the asynchronous notification encounters an already captured payment and does not refund it.
+
+
+##
+
+## Simulation
+
+
+It depends on Adyen's capture response; therefore, a payment needs to be captured to receive a capture-failed notification.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/en/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
new file mode 100644
index 000000000..76f7ce4cc
--- /dev/null
+++ b/docs/known-issues/en/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
@@ -0,0 +1,51 @@
+---
+title: 'The MercadoPagoV1 and V2 Integration does not work with save card functionality'
+id: 2V8kdA60OTl7VQoUUNgBci
+status: PUBLISHED
+createdAt: 2022-05-03T15:45:09.856Z
+updatedAt: 2024-01-09T13:23:20.203Z
+publishedAt: 2024-01-09T13:23:20.203Z
+firstPublishedAt: 2022-05-03T15:45:10.554Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality
+locale: en
+kiStatus: Backlog
+internalReference: 283727
+---
+
+## Summary
+
+
+The integration of MercadoPagoV1 and MercadoPagoV2 does not function properly with the save card functionality in the "My Account" section for countries that do not permit transactions with decimals.
+
+This issue arises because the "My Cards" feature generates a new transaction with a value of $1.5. However, some countries do not allow transactions with such decimal amounts, resulting in the rejection of any attempts to approve these transactions.
+
+
+##
+
+## Simulation
+
+
+
+1. Go to the VTEX **Admin.**
+2. Configure the acquirer MercadoPagoV1 or MercadoPagoV2.
+3. Configure a credit card payment method — such as Mastercard, Visa, American Express, etc. — to be processed by the acquirer.
+4. Go to your store's home page.
+5. Log in by entering your email address and password.
+6. Click on **My account**.
+7. Go to the **Credit cards** section.
+8. Click on **Add new card**.
+9. Fill in all the fields and click on **Save new card**.
+10. This process will return _an error occurred while trying to register the card_
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/en/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md b/docs/known-issues/en/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
new file mode 100644
index 000000000..93cfb8abd
--- /dev/null
+++ b/docs/known-issues/en/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
@@ -0,0 +1,50 @@
+---
+title: 'The PayU connector is unable to process payments when there is shipping data containing more than 40 characters.'
+id: 1SEaraqWshBYzjOcL9LxsN
+status: PUBLISHED
+createdAt: 2023-09-18T21:02:32.217Z
+updatedAt: 2023-09-18T21:02:32.812Z
+publishedAt: 2023-09-18T21:02:32.812Z
+firstPublishedAt: 2023-09-18T21:02:32.812Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters
+locale: en
+kiStatus: Backlog
+internalReference: 902539
+---
+
+## Summary
+
+
+PayU's connector does not handle address data received from the checkout and sends it to the provider as is, without any modifications. However, it is stated in the provider's documentation that such data should not exceed 40 characters.
+
+This causes the transaction to be canceled due to a payment authorization error with the message:
+
+    message: El tamaño debe estar entre 0 y 40 property: , message: El tamaño debe estar entre 0 y 40
+
+
+
+##
+
+## Simulation
+
+
+
+- During the shipping step at checkout, select a delivery address with more than 40 characters, such as 'Región Del Libertador General Bernardo O’Higgins (VI)' in Chile.
+- Select a payment method processed through the PayU connector.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md b/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md
index 91349e5aa..2e8da74d0 100644
--- a/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md
+++ b/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md
@@ -21,10 +21,10 @@ internalReference:
 The <i class="fas fa-info-circle"></i> button available on the **Product and SKUs** listing on the **Catalog** module does not always display the product information. See the images below to understand the normal behavior of the button.
 
 **Product is not available**
-![info vazia](https://images.ctfassets.net/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/695d568800f3c1ee1443b9632ebe5de9/image.png)
+![info vazia](//images.ctfassets.net/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/695d568800f3c1ee1443b9632ebe5de9/image.png)
 
 **Product is available**
-![info preenchida](https://images.ctfassets.net/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/0d029051c2061caccefa64d1184a5d9e/image.png)
+![info preenchida](//images.ctfassets.net/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/0d029051c2061caccefa64d1184a5d9e/image.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md b/docs/known-issues/en/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
index bc9d0fc91..afcd20073 100644
--- a/docs/known-issues/en/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
+++ b/docs/known-issues/en/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
@@ -3,8 +3,8 @@ title: 'The purchase button stays active even with insufficient credit of Paymen
 id: 76oPdoBKDn3PSn2KhomgQc
 status: PUBLISHED
 createdAt: 2022-03-27T14:14:51.967Z
-updatedAt: 2022-11-25T22:06:26.792Z
-publishedAt: 2022-11-25T22:06:26.792Z
+updatedAt: 2024-02-16T20:29:57.111Z
+publishedAt: 2024-02-16T20:29:57.111Z
 firstPublishedAt: 2022-03-27T14:14:52.312Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 309820
 ---
 
diff --git a/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index 96cae3d42..eea9c4c60 100644
--- a/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -3,8 +3,8 @@ title: 'The "Save new card" option does not work for asynchronous Payment Provid
 id: 3B4gVSNrSeCc8EBXwk5sAu
 status: PUBLISHED
 createdAt: 2022-03-11T17:54:35.664Z
-updatedAt: 2022-11-25T22:06:23.711Z
-publishedAt: 2022-11-25T22:06:23.711Z
+updatedAt: 2024-04-29T17:58:58.889Z
+publishedAt: 2024-04-29T17:58:58.889Z
 firstPublishedAt: 2022-03-11T17:54:36.273Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: the-save-new-card-option-does-not-work-for-asynchronous-payment-providers
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 308892
 ---
 
@@ -24,6 +24,7 @@ When the customer tries to add a new card in the My account section of stores wh
 This error occurs because My Cards wait for a synchronous answer from credit card acquirers and most of them doesn't return an immediate response.
 
 
+##
 
 ## Simulation
 
@@ -41,6 +42,7 @@ This error occurs because My Cards wait for a synchronous answer from credit car
 10. This process will return an error and the customer will be charged the amount R$ 1,50, which may or may not be automatically returned later.
 
 
+##
 
 ## Workaround
 
diff --git a/docs/known-issues/en/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md b/docs/known-issues/en/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
new file mode 100644
index 000000000..c3f72da52
--- /dev/null
+++ b/docs/known-issues/en/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
@@ -0,0 +1,46 @@
+---
+title: 'The Scroll API returns 429 and/or 408 errors when querying entities with a large number of documents, typically exceeding millions'
+id: 1Yx7s4kDAJOzpNCxro7TmW
+status: PUBLISHED
+createdAt: 2024-05-20T15:01:15.646Z
+updatedAt: 2024-05-20T15:01:16.679Z
+publishedAt: 2024-05-20T15:01:16.679Z
+firstPublishedAt: 2024-05-20T15:01:16.679Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions
+locale: en
+kiStatus: Backlog
+internalReference: 1035873
+---
+
+## Summary
+
+
+The Scroll API is designed to handle large datasets by enabling the retrieval of documents in a scrollable manner. However, when querying entities with a significant number of documents, typically in the millions, users may encounter 429 (Too Many Requests) and/or 408 (Request Timeout) errors. These errors arise due to the high volume of data being processed, which can overwhelm the API and result in request rate limiting or timeouts.
+
+
+##
+
+## Simulation
+
+
+
+1. Use the Scroll API to query an entity containing a large number of documents (e.g., millions).
+2. Observe the responses from the API.
+3. Note if the API returns 429 (Too Many Requests) and/or 408 (Request Timeout) errors during the process.
+
+
+##
+
+## Workaround
+
+
+Optimize the query implementing filters to reduce the load on the API by breaking down the request into smaller chunks or batches.
+When choosing filters, it is important to pay attention to whether all documents will be included to ensure that the scroll will go through all of the entity's documents.
+
+
+
+
diff --git a/docs/known-issues/en/the-system-does-not-allow-multiple-cancellation-with-giftcard.md b/docs/known-issues/en/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
index 1ab472bde..1a28ec10a 100644
--- a/docs/known-issues/en/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
+++ b/docs/known-issues/en/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
@@ -3,8 +3,8 @@ title: 'The system does not allow multiple cancellation with Giftcard'
 id: 2htvtVV2158piX4lTYhAvE
 status: PUBLISHED
 createdAt: 2022-03-27T12:54:40.811Z
-updatedAt: 2022-11-25T22:05:17.362Z
-publishedAt: 2022-11-25T22:05:17.362Z
+updatedAt: 2024-06-25T13:51:28.086Z
+publishedAt: 2024-06-25T13:51:28.086Z
 firstPublishedAt: 2022-03-27T12:54:41.420Z
 contentType: knownIssue
 productTeam: Payments
@@ -20,10 +20,10 @@ internalReference: 309117
 
 
 The system is not sending the partial cancellation of a Giftcard transaction.
-
 We also found a scenario where the same thing happens, however the cancelation works. This leaves the refund amount higher than the transaction amount because the value refunded is the first partial refund + the second refund with the full amount.
 
 
+##
 
 ## Simulation
 
@@ -31,9 +31,14 @@ We also found a scenario where the same thing happens, however the cancelation w
 Find a transaction where a partial refund/cancellation was requested using Giftcard.
 
 
+##
 
 ## Workaround
 
 
 There's no workaround, however, the user can add the refundable credit via admin UI.
 
+
+
+
+
diff --git a/docs/known-issues/en/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md b/docs/known-issues/en/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
index 3c17955de..224eaf1ed 100644
--- a/docs/known-issues/en/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
+++ b/docs/known-issues/en/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
@@ -3,8 +3,8 @@ title: "The system doesn't work with more than one extension payment affiliation
 id: 3bXtVPHqsrSFpJk9ZfyP4v
 status: PUBLISHED
 createdAt: 2022-03-03T18:45:02.639Z
-updatedAt: 2022-11-25T22:05:27.547Z
-publishedAt: 2022-11-25T22:05:27.547Z
+updatedAt: 2024-02-16T20:25:40.644Z
+publishedAt: 2024-02-16T20:25:40.644Z
 firstPublishedAt: 2022-03-03T18:45:03.463Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 319750
 ---
 
diff --git a/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index 9084dcc98..a3f436e5f 100644
--- a/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -3,8 +3,8 @@ title: 'The template "relatorio-de-importacao-de-estoque" does not support multi
 id: 5R8b0jnibOQdXupo0hIyts
 status: PUBLISHED
 createdAt: 2022-05-25T18:25:43.394Z
-updatedAt: 2022-11-25T21:59:26.792Z
-publishedAt: 2022-11-25T21:59:26.792Z
+updatedAt: 2024-02-16T20:24:28.851Z
+publishedAt: 2024-02-16T20:24:28.851Z
 firstPublishedAt: 2022-05-25T18:25:43.976Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 585906
 ---
 
diff --git a/docs/known-issues/en/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md b/docs/known-issues/en/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
index a51cdaf50..0f69b8680 100644
--- a/docs/known-issues/en/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
+++ b/docs/known-issues/en/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
@@ -3,8 +3,8 @@ title: 'The user cannot make a daily subscription directly from the my-subscript
 id: QJrZvOmlRusACgS2iGRyT
 status: PUBLISHED
 createdAt: 2022-05-18T18:37:18.099Z
-updatedAt: 2022-11-25T22:02:05.580Z
-publishedAt: 2022-11-25T22:02:05.580Z
+updatedAt: 2024-02-16T20:27:15.017Z
+publishedAt: 2024-02-16T20:27:15.017Z
 firstPublishedAt: 2022-05-18T18:37:18.579Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 430650
 ---
 
diff --git a/docs/known-issues/en/time-out-import-and-export-admin.md b/docs/known-issues/en/time-out-import-and-export-admin.md
index 2b042ec77..176486696 100644
--- a/docs/known-issues/en/time-out-import-and-export-admin.md
+++ b/docs/known-issues/en/time-out-import-and-export-admin.md
@@ -3,8 +3,8 @@ title: 'Time Out - Import and Export Admin'
 id: 5sPtDgOXtiGcYMvZL7aCf8
 status: PUBLISHED
 createdAt: 2022-03-10T12:36:57.023Z
-updatedAt: 2022-11-25T21:46:35.375Z
-publishedAt: 2022-11-25T21:46:35.375Z
+updatedAt: 2024-01-19T15:24:38.444Z
+publishedAt: 2024-01-19T15:24:38.444Z
 firstPublishedAt: 2022-03-10T12:36:57.461Z
 contentType: knownIssue
 productTeam: Catalog
@@ -23,6 +23,7 @@ For some accounts with lots of products, the import and export admin does not lo
 
 
 
+##
 
 ## Simulation
 
@@ -31,6 +32,7 @@ Go to `/admin/Site/Relatorio_Skus.aspx `
 
 
 
+##
 
 ## Workaround
 
diff --git a/docs/known-issues/en/time-out-on-category-keywords-change-with-many-products.md b/docs/known-issues/en/time-out-on-category-keywords-change-with-many-products.md
index 69a8dcac9..0e6e5e66c 100644
--- a/docs/known-issues/en/time-out-on-category-keywords-change-with-many-products.md
+++ b/docs/known-issues/en/time-out-on-category-keywords-change-with-many-products.md
@@ -3,8 +3,8 @@ title: 'Time out on category keywords change with many products'
 id: 14rC5XqGCOj1THVdYwbudS
 status: PUBLISHED
 createdAt: 2022-02-25T11:40:37.024Z
-updatedAt: 2022-11-25T21:55:02.673Z
-publishedAt: 2022-11-25T21:55:02.673Z
+updatedAt: 2024-02-16T20:26:33.631Z
+publishedAt: 2024-02-16T20:26:33.631Z
 firstPublishedAt: 2022-02-25T11:40:37.550Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: time-out-on-category-keywords-change-with-many-products
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 497335
 ---
 
diff --git a/docs/known-issues/en/timeout-generating-internal-application-keys.md b/docs/known-issues/en/timeout-generating-internal-application-keys.md
new file mode 100644
index 000000000..33976ceba
--- /dev/null
+++ b/docs/known-issues/en/timeout-generating-internal-application-keys.md
@@ -0,0 +1,46 @@
+---
+title: 'Timeout Generating internal application keys'
+id: 11U62yvD8i6Mp79rUC38FU
+status: PUBLISHED
+createdAt: 2024-05-08T11:28:41.002Z
+updatedAt: 2024-05-09T12:04:05.533Z
+publishedAt: 2024-05-09T12:04:05.533Z
+firstPublishedAt: 2024-05-08T11:28:41.857Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: timeout-generating-internal-application-keys
+locale: en
+kiStatus: Fixed
+internalReference: 1029425
+---
+
+## Summary
+
+
+
+Currently we have an issue that it can affect some clients while generating Applications keys.
+
+
+##
+
+## Simulation
+
+
+
+When the client uses their own SMTP for License Manager template in the message center, the Application Key UI will try to use their SMTP to send the e-mail, but if we have a timeout while sending the e-mail the Application Key won't be generated as well.
+
+
+##
+
+## Workaround
+
+
+
+The client can change the License manager SMTP in the message center, to configure VTEX SMTP rather than their own SMTP, avoiding the timeout. Or they can only try to solve the issue with their SMTP timeout.
+
+
+
+
+
diff --git a/docs/known-issues/en/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md b/docs/known-issues/en/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
new file mode 100644
index 000000000..652df28fe
--- /dev/null
+++ b/docs/known-issues/en/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
@@ -0,0 +1,44 @@
+---
+title: 'Timeout in the query to Analytics preventing to check the inventory log'
+id: 2gQhc3JF0bcm1JeLr0lluO
+status: PUBLISHED
+createdAt: 2024-02-19T20:54:22.012Z
+updatedAt: 2024-07-03T15:26:48.484Z
+publishedAt: 2024-07-03T15:26:48.484Z
+firstPublishedAt: 2024-02-19T20:54:22.861Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log
+locale: en
+kiStatus: Fixed
+internalReference: 984482
+---
+
+## Summary
+
+
+Update log in the inventory UI sometimes returns the error: Request failed with status code 500 for some specific SKUs, due to a timeout in the query to Analytics (where the data is stored), and no log for the SKU will be shown in the UI.
+
+This timeout could be due a high volume of updates in the SKU, or any other factor that makes this query takes longer than the maximum time of 40s;
+
+
+##
+
+## Simulation
+
+
+Due to the variable being the response time for the query to Analytics, it is not possible to replicate in a concise way.
+
+
+##
+
+## Workaround
+
+
+There is no workaround available.
+
+
+
+
diff --git a/docs/known-issues/en/total-reservation-item-with-negative-value-in-inventory-ui.md b/docs/known-issues/en/total-reservation-item-with-negative-value-in-inventory-ui.md
new file mode 100644
index 000000000..8b80c81e1
--- /dev/null
+++ b/docs/known-issues/en/total-reservation-item-with-negative-value-in-inventory-ui.md
@@ -0,0 +1,67 @@
+---
+title: 'Total reservation item with negative value in inventory UI'
+id: 5W8BeBZjSgN30YXwXfT8kV
+status: PUBLISHED
+createdAt: 2024-02-29T22:05:19.854Z
+updatedAt: 2024-03-01T13:46:07.440Z
+publishedAt: 2024-03-01T13:46:07.440Z
+firstPublishedAt: 2024-02-29T22:05:20.674Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: total-reservation-item-with-negative-value-in-inventory-ui
+locale: en
+kiStatus: Backlog
+internalReference: 991735
+---
+
+## Summary
+
+
+
+A specific scenario in which more than one order is placed with the same sku and coming from the same warehouse, can leave the reservation number negative in the inventory UI.
+
+**Specific scenario:**
+order A: 4 units of the sku X from warehouse 1;
+order B: 6 units of the sku X from warehouse 1;
+
+order A: `status=handling`, the reservation acknowledge;
+order B: `status=window-to-cancel`, the reservation is not acknowledge yet;
+
+After this the merchant update the inventory considering the units from order A as delivered, if the merchant cancels the order A, and then later move the order B to `status=handling` (acknowledge the reservation), this will leave the inventory UI with -4 of this sku as reserved.
+
+
+##
+
+##
+
+## Simulation
+
+
+
+1- Update inventory for sku X with 10 units from warehouse 1;
+2- Create an order A with 4 units of sku X from warehouse 1;
+3- Create an order B with 6 units of sku X from warehoue 1;
+4- Move order A to `status=handling` (this will acknowledge the reservation);
+5- Update inventory for sku X with 6 units from warehouse 1 (which is the number you still have for order B);
+6- Cancel order A;
+7- Move order B to `status=handling` (this will acknowledge the reservation);
+8- Check inventory for sku X in warehouse 1, it will have -4 units reserved.
+
+
+
+##
+
+##
+
+## Workaround
+
+
+
+There is no workaround available.
+
+
+
+
+
diff --git a/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md
new file mode 100644
index 000000000..446bbefb5
--- /dev/null
+++ b/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md
@@ -0,0 +1,44 @@
+---
+title: 'Transaction cancellation error with "Unreachable code" message'
+id: 2Y4joZlyDhbNWU9ycw32U3
+status: PUBLISHED
+createdAt: 2024-03-12T16:34:10.113Z
+updatedAt: 2024-03-12T16:34:11.037Z
+publishedAt: 2024-03-12T16:34:11.037Z
+firstPublishedAt: 2024-03-12T16:34:11.037Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transaction-cancellation-error-with-unreachable-code-message
+locale: en
+kiStatus: Backlog
+internalReference: 998435
+---
+
+## Summary
+
+
+A full transaction cancellation can fail returning the message `Unreachable code` (only visible via API).
+
+This error happens in payment split scenario, in the UI you can see the cancellation attempt logs but no response.
+
+
+##
+
+## Simulation
+
+
+We were not able to simulate this error.
+
+
+##
+
+## Workaround
+
+
+It's possible to cancel the payments separately (starting with the lowest value).
+
+
+
+
diff --git a/docs/known-issues/en/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md b/docs/known-issues/en/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
new file mode 100644
index 000000000..b1491c256
--- /dev/null
+++ b/docs/known-issues/en/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
@@ -0,0 +1,42 @@
+---
+title: 'Transaction stuck in a status prior to the state that it should be'
+id: 60oG2yj6wb1MomGh7Bbh9C
+status: PUBLISHED
+createdAt: 2024-05-22T17:58:05.800Z
+updatedAt: 2024-07-25T21:12:34.583Z
+publishedAt: 2024-07-25T21:12:34.583Z
+firstPublishedAt: 2024-05-22T17:58:06.594Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be
+locale: en
+kiStatus: Backlog
+internalReference: 1037765
+---
+
+## Summary
+
+
+The most common case is transaction stuck in authorized when it should be approved, in this scenario the order can't be invoiced.
+
+
+##
+
+## Simulation
+
+
+It's not possible to simulate.
+
+
+##
+
+## Workaround
+
+
+Support team can call internal APIs to move the transaction forward.
+
+
+
+
diff --git a/docs/known-issues/en/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md b/docs/known-issues/en/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
index 0ef2f0b53..a3d9df133 100644
--- a/docs/known-issues/en/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
+++ b/docs/known-issues/en/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
@@ -1,10 +1,10 @@
 ---
 title: 'Transaction stuck in canceling when one of the card is denied'
 id: RdKtB6LsKfaukjT9kiqZ4
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-03-03T18:39:59.580Z
-updatedAt: 2022-06-29T11:57:29.612Z
-publishedAt: 2022-06-28T17:06:24.520Z
+updatedAt: 2024-02-16T20:29:06.755Z
+publishedAt: 2024-02-16T20:29:06.755Z
 firstPublishedAt: 2022-03-03T18:39:59.922Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: transaction-stuck-in-canceling-when-one-of-the-card-is-denied
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429082
 ---
 
diff --git a/docs/known-issues/en/transaction-stuck-in-status-approved-with-payment-canceled.md b/docs/known-issues/en/transaction-stuck-in-status-approved-with-payment-canceled.md
new file mode 100644
index 000000000..ea5c80780
--- /dev/null
+++ b/docs/known-issues/en/transaction-stuck-in-status-approved-with-payment-canceled.md
@@ -0,0 +1,48 @@
+---
+title: 'Transaction stuck in status approved with payment canceled'
+id: 5SwwnGi26tagIXuTmvToc
+status: PUBLISHED
+createdAt: 2024-06-07T14:21:22.809Z
+updatedAt: 2024-06-12T17:33:43.967Z
+publishedAt: 2024-06-12T17:33:43.967Z
+firstPublishedAt: 2024-06-07T14:21:23.608Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transaction-stuck-in-status-approved-with-payment-canceled
+locale: en
+kiStatus: Backlog
+internalReference: 1046365
+---
+
+## Summary
+
+
+The transaction was stuck in status approved, even though the payment was canceled.
+
+When tried to settle it manually, the gateway returns the following error:
+
+    "error": {"code": "1506","message": "The payment with ID = xxxxx was not settled because the settlement value was -x.xx.","exception": null}
+
+
+
+##
+
+## Simulation
+
+
+There is no way to simulate this behavior.
+
+
+##
+
+## Workaround
+
+
+There aren't any workarounds in this case.
+
+
+
+
+
diff --git a/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md b/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md
index 36cbf04ad..adb30a22d 100644
--- a/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md
+++ b/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md
@@ -19,10 +19,10 @@ internalReference:
 ## Summary
 
 When an item is removed from the order:
-![item removido](https://images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
+![item removido](//images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
 
 The transactional email doesn't consider the removed item and shows both items in the email:
-![email transacional](https://images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
+![email transacional](//images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
 
 
 
diff --git a/docs/known-issues/en/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/en/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
new file mode 100644
index 000000000..2fe1d02ed
--- /dev/null
+++ b/docs/known-issues/en/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -0,0 +1,43 @@
+---
+title: 'Transactions with Konduto are taking longer than expected to update status'
+id: 5yUSXenLjlEdESoj5VVvoH
+status: PUBLISHED
+createdAt: 2022-03-11T18:56:45.293Z
+updatedAt: 2023-07-10T18:01:59.163Z
+publishedAt: 2023-07-10T18:01:59.163Z
+firstPublishedAt: 2022-03-11T18:56:45.712Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transactions-with-konduto-are-taking-longer-than-expected-to-update-status
+locale: en
+kiStatus: Backlog
+internalReference: 541149
+---
+
+## Summary
+
+
+Automatic retries are getting stuck in some transactions using Kondutor as an anti-fraud provider and taking longer than expected to call a new retry in order to change its status. This is blocking customers' inventory.
+
+
+##
+
+## Simulation
+
+
+Unable to simulate, this behavior occurs intermittently.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md b/docs/known-issues/en/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
index fcd75c155..7d0279189 100644
--- a/docs/known-issues/en/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
+++ b/docs/known-issues/en/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
@@ -3,8 +3,8 @@ title: 'Transactions with the TNSPay connector being denied by error: Card not E
 id: 2jZefzH8LYqPJxkmylmyA0
 status: PUBLISHED
 createdAt: 2022-03-14T13:21:56.187Z
-updatedAt: 2023-04-10T16:10:48.998Z
-publishedAt: 2023-04-10T16:10:48.998Z
+updatedAt: 2024-02-16T20:24:33.195Z
+publishedAt: 2024-02-16T20:24:33.195Z
 firstPublishedAt: 2022-03-14T13:21:56.952Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 541687
 ---
 
diff --git a/docs/known-issues/en/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md b/docs/known-issues/en/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
new file mode 100644
index 000000000..4e6d7d53b
--- /dev/null
+++ b/docs/known-issues/en/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
@@ -0,0 +1,47 @@
+---
+title: 'Translation issues when using a subaccount to implement multi-language stores'
+id: 5FOCZE7pI4npyfo7TjsFaY
+status: PUBLISHED
+createdAt: 2023-06-21T20:36:33.483Z
+updatedAt: 2024-02-29T15:19:42.862Z
+publishedAt: 2024-02-29T15:19:42.862Z
+firstPublishedAt: 2023-06-21T20:36:33.922Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores
+locale: en
+kiStatus: Backlog
+internalReference: 848524
+---
+
+## Summary
+
+
+Catalog Unified Indexing considers the messages' translations only from the main account, even when using a subaccount architecture to implement cross-border stores.
+
+This leads to a different translation in the search and product page, as the content from the search page is based only on the translations retrieved by the Catalog Indexer.
+
+
+##
+
+## Simulation
+
+
+
+- Create a subaccount and implement cross-border stores;
+- Translate the catalog content in the subaccount;
+- Compare the search and product page; they will have different translations.
+
+
+##
+
+## Workaround
+
+
+Set the additional languages (bindings and Messages content) in the main account, replicating the translations from the subaccount also in the main account.
+
+
+
+
diff --git a/docs/known-issues/en/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md b/docs/known-issues/en/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
new file mode 100644
index 000000000..3b7f94974
--- /dev/null
+++ b/docs/known-issues/en/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
@@ -0,0 +1,70 @@
+---
+title: 'Transliteration only being saved in vbase and not into rewriter'
+id: 3ngFt1qXOUjmY5L84dk6in
+status: PUBLISHED
+createdAt: 2023-12-12T19:54:12.171Z
+updatedAt: 2024-02-16T20:26:46.444Z
+publishedAt: 2024-02-16T20:26:46.444Z
+firstPublishedAt: 2023-12-12T19:54:13.102Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: transliteration-only-being-saved-in-vbase-and-not-into-rewriter
+locale: en
+kiStatus: No Fix
+internalReference: 738334
+---
+
+## Summary
+
+
+
+When transliterating the urls through the catalog rewriter is not storing it, or is not receiving any notification through the broadcaster, we are only storing it in vbase
+
+
+##
+
+## Simulation
+
+
+
+Transl
+
+Check the rewriter with the linkId that you created at admin/graphql-ide and choose the rewriter app:
+
+
+    { internal{ get(path: "yourLinkdIdHere"){ id } }}
+
+
+
+
+##
+
+## Workaround
+
+
+
+Run the following query on the rewriter
+
+
+    { internal{ get(path: "yourTranslatedCategoryNameSlugified"){ id from declarer type query binding  origin resolveAs } }}
+
+
+Save the returned values, you will need to use them in the next step
+
+Run the following mutation just changing the from parameter, the others must be the same as above:
+
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "yourLinkId", "declarer": "yourSavedDeclarer", "type": "yourSavedType", "binding": "yourSavedBinding", "id": "yourSavedId", "origin": "yourSavedOrigin", "resolveAs": "TheOriginalNameOfTheCategory" --here in cyrilic }}
+
+
+
+> For more information regarding those params, you can consult: https://developers.vtex.com/vtex-developer-docs/docs/rewriter
+
+
+Now, we are going to delete the old route (the one saved with the name)
+
+
+    mutation saveInternal($route: InternalInput!) { internal { delete(path: "yourTranslatedCategoryNameSlugified") { id } }}
+
diff --git a/docs/known-issues/en/ui-does-not-update-best-sla-choice-in-cart.md b/docs/known-issues/en/ui-does-not-update-best-sla-choice-in-cart.md
index 45576f270..587bd6059 100644
--- a/docs/known-issues/en/ui-does-not-update-best-sla-choice-in-cart.md
+++ b/docs/known-issues/en/ui-does-not-update-best-sla-choice-in-cart.md
@@ -3,8 +3,8 @@ title: 'UI does not update best SLA choice in cart'
 id: 5H05jLUJA0gmSDTO6nMsPE
 status: PUBLISHED
 createdAt: 2022-03-26T02:30:36.692Z
-updatedAt: 2022-11-25T21:54:03.143Z
-publishedAt: 2022-11-25T21:54:03.143Z
+updatedAt: 2024-02-16T20:26:13.531Z
+publishedAt: 2024-02-16T20:26:13.531Z
 firstPublishedAt: 2022-03-26T02:30:37.014Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: ui-does-not-update-best-sla-choice-in-cart
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 550201
 ---
 
diff --git a/docs/known-issues/en/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md b/docs/known-issues/en/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
new file mode 100644
index 000000000..7f825969c
--- /dev/null
+++ b/docs/known-issues/en/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
@@ -0,0 +1,48 @@
+---
+title: "UI doesn't show delivery window selection for pick-up points when an item from a seller is between items for pick-up from another seller"
+id: 5SyIw04UtNiZhmy0ELNLCD
+status: PUBLISHED
+createdAt: 2023-12-15T20:18:48.433Z
+updatedAt: 2023-12-15T20:18:49.218Z
+publishedAt: 2023-12-15T20:18:49.218Z
+firstPublishedAt: 2023-12-15T20:18:49.218Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller
+locale: en
+kiStatus: Backlog
+internalReference: 954108
+---
+
+## Summary
+
+
+In a cart with at least three products, where the item orders are: 1st is for scheduled pick-up 1, 2nd for scheduled pick-up 2 (different seller), and 3rd is for scheduled pick-up 1, the UI will not show the delivery windows to select the date/hour for the 2nd pickup. This happens because the API will group the 1st item and 3rd item since it's the same SLA.
+
+It's not possible to go to the payment step and finish the purchase.
+
+
+##
+
+## Simulation
+
+
+
+- Add an item to the cart for pick-up from seller A;
+- Add an item to the cart for pick-up from seller B;
+- Add another item to the cart for pick-up from seller A;
+- In the shipping step, the pick-up delivery windows to select the date/hour won't be shown.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md b/docs/known-issues/en/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
index 1c990c6e6..ed0a8ad2d 100644
--- a/docs/known-issues/en/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
+++ b/docs/known-issues/en/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
@@ -3,8 +3,8 @@ title: "UI doesn't show the form to edit address when selecting to add a new add
 id: 4rqphb66vAzsAyx9mUmNLu
 status: PUBLISHED
 createdAt: 2023-02-06T13:15:57.816Z
-updatedAt: 2023-02-06T13:15:58.251Z
-publishedAt: 2023-02-06T13:15:58.251Z
+updatedAt: 2023-06-23T17:47:10.184Z
+publishedAt: 2023-06-23T17:47:10.184Z
 firstPublishedAt: 2023-02-06T13:15:58.251Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 747772
 ---
 
diff --git a/docs/known-issues/en/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md b/docs/known-issues/en/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
new file mode 100644
index 000000000..44d772a5b
--- /dev/null
+++ b/docs/known-issues/en/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
@@ -0,0 +1,42 @@
+---
+title: 'UI gets frozen if an error occurs in the place order internal process'
+id: pt5Orot3i9BlYCt4E2Kj5
+status: PUBLISHED
+createdAt: 2023-11-28T18:55:54.950Z
+updatedAt: 2023-11-28T18:55:55.649Z
+publishedAt: 2023-11-28T18:55:55.649Z
+firstPublishedAt: 2023-11-28T18:55:55.649Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process
+locale: en
+kiStatus: Backlog
+internalReference: 943771
+---
+
+## Summary
+
+
+When an error occurs during the place order internal process, UI gets frozen in loading with no error/warning message.
+
+
+##
+
+## Simulation
+
+
+This behavior was seen when Tax Service times out during the place order request, but it's not limited to this.
+
+
+##
+
+## Workaround
+
+
+Refresh the page.
+
+
+
+
diff --git a/docs/known-issues/en/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md b/docs/known-issues/en/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
new file mode 100644
index 000000000..434d05010
--- /dev/null
+++ b/docs/known-issues/en/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
@@ -0,0 +1,46 @@
+---
+title: "UI shows a pick-up was selected in cart with subscriptions but it wasn't in API"
+id: 6WUGylIHWZtfeAm7hplYHD
+status: PUBLISHED
+createdAt: 2024-03-08T19:08:16.010Z
+updatedAt: 2024-03-08T19:08:17.012Z
+publishedAt: 2024-03-08T19:08:17.012Z
+firstPublishedAt: 2024-03-08T19:08:17.012Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api
+locale: en
+kiStatus: Backlog
+internalReference: 996976
+---
+
+## Summary
+
+
+Pick-up options are offered to shoppers in a cart with an item with a subscription. When one of the pick-ups is selected, checkout changes to delivery automatically, but the UI still shows that the pick-up was selected.
+
+
+##
+
+## Simulation
+
+
+
+- Configure a subscription;
+- Add the item with the subscription to the cart;
+- In the shipping step, select "Pick up in store";
+- Check the orderForm via API, and delivery will be selected.
+
+
+##
+
+## Workaround
+
+
+Open a ticket to VTEX Support asking to enable pickup points for subscription orders.
+
+
+
+
diff --git a/docs/known-issues/en/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md b/docs/known-issues/en/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
new file mode 100644
index 000000000..e8b5ffaf8
--- /dev/null
+++ b/docs/known-issues/en/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
@@ -0,0 +1,48 @@
+---
+title: 'UI shows duplicated pick-up points when an item for delivery is between items for pick-up'
+id: lIP6kRDsi23lNQd7RzNfY
+status: PUBLISHED
+createdAt: 2023-09-25T13:50:27.481Z
+updatedAt: 2023-10-18T14:36:11.434Z
+publishedAt: 2023-10-18T14:36:11.434Z
+firstPublishedAt: 2023-09-25T13:50:28.066Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup
+locale: en
+kiStatus: Backlog
+internalReference: 906549
+---
+
+## Summary
+
+
+In a cart with at least three products, where the item orders are: 1st is for pick-up, 2nd is for delivery, and 3rd is for pick-up, the UI will show the pick-up point duplicated. This happens because the API will group the 1st item and 3rd item since it's the same SLA.
+
+It's possible to go to the payment step and finish the purchase.
+
+
+##
+
+## Simulation
+
+
+
+- Add an item to the cart for pick-up;
+- Add an item to the cart for delivery;
+- Add another item to the cart for pick-up;
+- In the shipping step, the pick-up will be duplicated
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md
new file mode 100644
index 000000000..79cd50a30
--- /dev/null
+++ b/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -0,0 +1,45 @@
+---
+title: 'UI shows "Gifts picked!" when using Order replacement feature'
+id: 4efm7L6hQhad98uYkjzrXO
+status: PUBLISHED
+createdAt: 2023-09-27T20:57:46.944Z
+updatedAt: 2023-09-27T20:57:47.516Z
+publishedAt: 2023-09-27T20:57:47.516Z
+firstPublishedAt: 2023-09-27T20:57:47.516Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: ui-shows-gifts-picked-when-using-order-replacement-feature
+locale: en
+kiStatus: Backlog
+internalReference: 909137
+---
+
+## Summary
+
+
+When using the Order replacement feature, Checkout UI shows "Gifts picked!" even though there is no gift promotion configured.
+
+
+##
+
+## Simulation
+
+
+
+- Access My Orders and select an order;
+- Click on "Change Order" and select the reason "I bought the wrong number/size and want to change it";
+- You will be redirected to checkout and there will be "Gifts picked!" in the screen.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md b/docs/known-issues/en/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
new file mode 100644
index 000000000..e0c3d1c5a
--- /dev/null
+++ b/docs/known-issues/en/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
@@ -0,0 +1,51 @@
+---
+title: 'UI triggers separate requests for each key/field of an attachment'
+id: 5IF3veMFTFi9dERoEokokt
+status: PUBLISHED
+createdAt: 2024-03-01T21:05:37.154Z
+updatedAt: 2024-03-01T21:07:41.105Z
+publishedAt: 2024-03-01T21:07:41.105Z
+firstPublishedAt: 2024-03-01T21:05:37.941Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: ui-triggers-separate-requests-for-each-keyfield-of-an-attachment
+locale: en
+kiStatus: Backlog
+internalReference: 336371
+---
+
+## Summary
+
+
+When you set the value for an item attachment field through the UI, this triggers a request to update the orderForm, even if there are still more fields left.
+This request will then be processed, and the response with the updated orderForm.
+
+In cases where the attachment has multiple open text fields, this may cause subsequent fields to be overwritten while you're typing their values.
+This happens because the update request will have been sent when this field was still blank, so it will also be blank in the response.
+
+In cases where the item has a subscription attachment with multiple keys, it may trigger an error message like "unable to communicate with seller" / "não foi possível se comunicar com o seller".
+This happens because the subscription will expect multiple keys to have been filled, but the first request will only have sent one.
+
+
+##
+
+## Simulation
+
+
+Create an attachment with at least two keys/fields.
+Add an item linked to this attachment to your cart, then add the attachment.
+Finally, set the value for one field, and observe the behavior that follows.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/unable-to-cancel-transactions-that-had-payout-split-config-change.md b/docs/known-issues/en/unable-to-cancel-transactions-that-had-payout-split-config-change.md
index bf89cf591..c9e394988 100644
--- a/docs/known-issues/en/unable-to-cancel-transactions-that-had-payout-split-config-change.md
+++ b/docs/known-issues/en/unable-to-cancel-transactions-that-had-payout-split-config-change.md
@@ -3,8 +3,8 @@ title: 'Unable to cancel transactions that had payout split config change'
 id: 2bhsI5119DLOhNjk2cb6q
 status: PUBLISHED
 createdAt: 2022-06-28T16:44:10.992Z
-updatedAt: 2022-11-25T22:06:55.006Z
-publishedAt: 2022-11-25T22:06:55.006Z
+updatedAt: 2024-02-16T20:24:09.734Z
+publishedAt: 2024-02-16T20:24:09.734Z
 firstPublishedAt: 2022-06-28T16:44:11.460Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: unable-to-cancel-transactions-that-had-payout-split-config-change
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 364382
 ---
 
diff --git a/docs/known-issues/en/unable-to-log-in-through-the-google-app-on-ios.md b/docs/known-issues/en/unable-to-log-in-through-the-google-app-on-ios.md
new file mode 100644
index 000000000..0c6d80593
--- /dev/null
+++ b/docs/known-issues/en/unable-to-log-in-through-the-google-app-on-ios.md
@@ -0,0 +1,45 @@
+---
+title: 'Unable to log in through the Google App on iOS'
+id: 1YxuqHJbbKnzdv1d6LrfR2
+status: PUBLISHED
+createdAt: 2023-10-26T16:50:11.505Z
+updatedAt: 2024-03-20T20:34:16.469Z
+publishedAt: 2024-03-20T20:34:16.469Z
+firstPublishedAt: 2023-10-26T16:50:12.188Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: unable-to-log-in-through-the-google-app-on-ios
+locale: en
+kiStatus: Backlog
+internalReference: 926239
+---
+
+## Summary
+
+
+When logging into the store from the Google app (only the Google app and not in the Google Chrome browser on iOS devices), the option loops and never opens Google to choose the account.
+
+
+##
+
+## Simulation
+
+
+-Use the Google App on IOS;
+-Access the site that has Google authentication enabled in the webstore;
+-Click on sign in and choose "Sign in with Google";
+
+
+##
+
+## Workaround
+
+
+Use another more conventional browser to access the store, for example Google Chrome.
+
+
+
+
+
diff --git a/docs/known-issues/en/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md b/docs/known-issues/en/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
new file mode 100644
index 000000000..26e31fb8c
--- /dev/null
+++ b/docs/known-issues/en/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
@@ -0,0 +1,51 @@
+---
+title: 'Unable to upload spreadsheet Images with host services using protocol encryption protocol SSL1.3'
+id: sqoXJSms7bhmdNe0Id111
+status: PUBLISHED
+createdAt: 2023-06-28T12:23:54.884Z
+updatedAt: 2023-06-28T12:25:18.545Z
+publishedAt: 2023-06-28T12:25:18.545Z
+firstPublishedAt: 2023-06-28T12:23:55.364Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13
+locale: en
+kiStatus: Backlog
+internalReference: 851911
+---
+
+## Summary
+
+
+When the images host of the spreadsheet uses a protocol encryption protocol SSL1.3, a error appears when trying to upload the spreadsheet:
+
+"Fail to process record. Make sure your worksheet data is consistent and try again. Error details: An error ocurred while sending the request."
+
+This error happens because our windows service only allows older versions like 1.2 or 1.1.
+
+
+
+##
+
+## Simulation
+
+
+
+1. Use a host with a more recent protocol version;
+2. Try to upload a image, using spreadsheet, that is hosted there;
+3. Check that the error message appears.
+
+
+##
+
+## Workaround
+
+
+Use a different host or validate with the host to use an older version.
+
+
+
+
+
diff --git a/docs/known-issues/en/unavailable-products-pdp-are-still-being-returned.md b/docs/known-issues/en/unavailable-products-pdp-are-still-being-returned.md
new file mode 100644
index 000000000..b2329d72f
--- /dev/null
+++ b/docs/known-issues/en/unavailable-products-pdp-are-still-being-returned.md
@@ -0,0 +1,43 @@
+---
+title: "Unavailable product's PDP are still being returned"
+id: 6Q2TOp3UPHuCXDpZceV1Dn
+status: PUBLISHED
+createdAt: 2024-05-31T14:43:14.505Z
+updatedAt: 2024-06-04T12:10:43.840Z
+publishedAt: 2024-06-04T12:10:43.840Z
+firstPublishedAt: 2024-05-31T14:43:15.347Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: unavailable-products-pdp-are-still-being-returned
+locale: en
+kiStatus: Backlog
+internalReference: 1041920
+---
+
+## Summary
+
+
+When a product is unavailable, its PDP can still be returned.
+
+
+##
+
+## Simulation
+
+
+Try to access the PDP of a product that is unavailable in Faststore.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md b/docs/known-issues/en/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
new file mode 100644
index 000000000..fed9a5be7
--- /dev/null
+++ b/docs/known-issues/en/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
@@ -0,0 +1,43 @@
+---
+title: 'Unecessary search results prioritization by diacritics for Portuguese'
+id: 3lbgwHFc9RLusAnZnvnE1H
+status: PUBLISHED
+createdAt: 2024-05-07T15:24:18.404Z
+updatedAt: 2024-05-07T16:55:01.818Z
+publishedAt: 2024-05-07T16:55:01.818Z
+firstPublishedAt: 2024-05-07T15:24:19.224Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: unecessary-search-results-prioritization-by-diacritics-for-portuguese
+locale: en
+kiStatus: Backlog
+internalReference: 1028763
+---
+
+## Summary
+
+
+The Intelligent Search prioritizes results that have an exact match, considering the diacritics of the searched term and the products.
+
+In some languages, they can generate completely different words, but for others, this is not important enough or can be related to frequent typos.
+
+In Portuguese, diacritics like acute accent, circumflex accent, and tilde fall into this scenario. A product or a search term missing the diacritic will prioritize some products over others depending on how they are registered. For this language, normalization is expected.
+
+
+##
+
+## Simulation
+
+
+In a Portuguese store, searching for "tennis" will present first the products with "tenis" (exact match with diacritics) and only later the results with "tênis" (exact match ignoring diacritics).
+
+
+##
+
+## Workaround
+
+
+It's recommended that the product catalog always keep the same writing for its products. If not applicable, a synonym can help to keep terms equivalent.
+
diff --git a/docs/known-issues/en/unecessary-simulation-requests-and-components-being-reloaded.md b/docs/known-issues/en/unecessary-simulation-requests-and-components-being-reloaded.md
index 0469b4567..7dba650ac 100644
--- a/docs/known-issues/en/unecessary-simulation-requests-and-components-being-reloaded.md
+++ b/docs/known-issues/en/unecessary-simulation-requests-and-components-being-reloaded.md
@@ -3,8 +3,8 @@ title: 'Unecessary simulation requests and components being reloaded'
 id: 1qXJU1XC4r0e9KWxNUKp3L
 status: PUBLISHED
 createdAt: 2022-08-30T17:34:47.635Z
-updatedAt: 2022-11-25T21:50:25.658Z
-publishedAt: 2022-11-25T21:50:25.658Z
+updatedAt: 2024-02-16T20:25:15.198Z
+publishedAt: 2024-02-16T20:25:15.198Z
 firstPublishedAt: 2022-08-30T17:34:48.111Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: unecessary-simulation-requests-and-components-being-reloaded
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 648298
 ---
 
diff --git a/docs/known-issues/en/unexpected-reload-happening-when-registeringupdating-a-product.md b/docs/known-issues/en/unexpected-reload-happening-when-registeringupdating-a-product.md
new file mode 100644
index 000000000..a4a823d16
--- /dev/null
+++ b/docs/known-issues/en/unexpected-reload-happening-when-registeringupdating-a-product.md
@@ -0,0 +1,48 @@
+---
+title: 'Unexpected reload happening when registering/updating a product'
+id: 4XAYOJG7cgEJG6PqcmOkAY
+status: PUBLISHED
+createdAt: 2023-07-17T19:00:56.863Z
+updatedAt: 2023-10-20T13:42:32.569Z
+publishedAt: 2023-10-20T13:42:32.569Z
+firstPublishedAt: 2023-07-17T19:00:57.611Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: unexpected-reload-happening-when-registeringupdating-a-product
+locale: en
+kiStatus: Backlog
+internalReference: 863542
+---
+
+## Summary
+
+
+
+When registering or updating a product form, some users are reporting that when doing this action several times in a row, at some point the page forces and refreshes on its own.
+
+We couldn't find a pattern to justify this
+
+
+##
+
+## Simulation
+
+
+
+Updating/registering a product form several times in a row.
+it is hard do simulate since it is totally random
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md
new file mode 100644
index 000000000..5c836f4c2
--- /dev/null
+++ b/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md
@@ -0,0 +1,53 @@
+---
+title: '"Unhandled exception" error when changing edition of account'
+id: 1NVjCrlRkadscl8fW9rOdA
+status: PUBLISHED
+createdAt: 2023-09-26T12:45:44.999Z
+updatedAt: 2024-02-26T17:22:29.322Z
+publishedAt: 2024-02-26T17:22:29.322Z
+firstPublishedAt: 2023-09-26T12:45:45.927Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: unhandled-exception-error-when-changing-edition-of-account
+locale: en
+kiStatus: Backlog
+internalReference: 907294
+---
+
+## Summary
+
+
+Sometimes when we change the edition of an account or workspace we can find the following error:
+
+
+    - error: Unhandled exception - error: Please report the issue in https://github.com/vtex/toolbelt/issues
+
+
+The error is not consistent, it doesn't happen all the time.
+
+If the master of the store is using the `edition-business` and they want to change the edition to `edition-store` on a workspace, this error is more likely to happen.
+
+
+##
+
+## Simulation
+
+
+Try to change the edition of any test account or workspace, this error will eventually happen in the process.
+
+
+##
+
+## Workaround
+
+
+
+- Run the command `vtex edition get` to be sure that the edition didn't change. Sometimes the edition changes even when the error shows;
+- If the apps didn't update as well try running the `vtex update` command;
+- Wait a while and try again;
+- It can also happen that the Unhandled exception error will not appear, the edition will change but the apps will not update. In this case just sun `vtex update`
+
+
+
diff --git a/docs/known-issues/en/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md b/docs/known-issues/en/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
index 483c01054..656e74069 100644
--- a/docs/known-issues/en/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
+++ b/docs/known-issues/en/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
@@ -3,8 +3,8 @@ title: 'Unspecific Error Message When Exporting ProdutoExportacaoImportacaoEspec
 id: 3rtDeX0QppmbXOvuCtC1Lr
 status: PUBLISHED
 createdAt: 2022-03-22T13:09:32.153Z
-updatedAt: 2022-11-25T21:44:55.880Z
-publishedAt: 2022-11-25T21:44:55.880Z
+updatedAt: 2024-02-16T20:29:49.944Z
+publishedAt: 2024-02-16T20:29:49.944Z
 firstPublishedAt: 2022-03-22T13:09:32.886Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 314227
 ---
 
diff --git a/docs/known-issues/en/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md b/docs/known-issues/en/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
new file mode 100644
index 000000000..87706f0eb
--- /dev/null
+++ b/docs/known-issues/en/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
@@ -0,0 +1,50 @@
+---
+title: 'Unsupported fields by the Intelligent Search API return wrong or empty data'
+id: Jvm9oLhUM6NqCslpBqSti
+status: PUBLISHED
+createdAt: 2024-05-13T21:03:14.026Z
+updatedAt: 2024-06-25T19:11:41.925Z
+publishedAt: 2024-06-25T19:11:41.925Z
+firstPublishedAt: 2024-05-13T21:03:15.346Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data
+locale: en
+kiStatus: Backlog
+internalReference: 1032531
+---
+
+## Summary
+
+
+The Intelligent Search API is mainly based on the legacy Catalog Search API for compatibility reasons, but not every property returns the same information. In some cases, it is different or empty.
+
+Some affected properties:
+
+- "modalType" (returns empty)
+- "imageText" (returns the same as "imageLabel")
+- "kitItems" (returns empty)
+
+
+##
+
+## Simulation
+
+
+
+- register value for an affected field in the Catalog module
+- compare the response for the specific field between the Catalog Search and Intelligent Search APIs
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md b/docs/known-issues/en/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
index 0768d97e4..c871e5e29 100644
--- a/docs/known-issues/en/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
+++ b/docs/known-issues/en/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
@@ -3,8 +3,8 @@ title: 'Update seller using Admin is setting some fields back to the default val
 id: 2gtqnZmCW59OKoqRpU3UaQ
 status: PUBLISHED
 createdAt: 2022-06-30T12:21:23.852Z
-updatedAt: 2022-11-25T22:00:35.980Z
-publishedAt: 2022-11-25T22:00:35.980Z
+updatedAt: 2024-02-16T20:28:26.435Z
+publishedAt: 2024-02-16T20:28:26.435Z
 firstPublishedAt: 2022-06-30T12:21:24.538Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 608120
 ---
 
diff --git a/docs/known-issues/en/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md b/docs/known-issues/en/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
new file mode 100644
index 000000000..95e25a7bb
--- /dev/null
+++ b/docs/known-issues/en/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
@@ -0,0 +1,53 @@
+---
+title: "Update seller's available trade policies does not trigger automatic indexation"
+id: 45FOjSN4a5ZhCqilQfUX99
+status: PUBLISHED
+createdAt: 2024-05-31T13:49:57.732Z
+updatedAt: 2024-05-31T13:49:58.764Z
+publishedAt: 2024-05-31T13:49:58.764Z
+firstPublishedAt: 2024-05-31T13:49:58.764Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: update-sellers-available-trade-policies-does-not-trigger-automatic-indexation
+locale: en
+kiStatus: Backlog
+internalReference: 1041874
+---
+
+## Summary
+
+
+At the seller management UI, remove or add a new trade policy to a seller.
+
+This process is saved successfully, however the information is not automatically updated at the indexer of products related to that specific seller.
+
+As a consequence, the seller's offer at these products will be outdated as:
+- still available at the trade policy (if the action was to remove it);
+- not available at the trade policy (if the action was to add it).
+
+
+
+##
+
+## Simulation
+
+
+
+- Check a product that has an offer by a seller at a specific trade policy;
+- Remove the trade policy from this seller using the Seller Management UI;
+- Check that the action did not reflected at the product.
+
+
+##
+
+## Workaround
+
+
+Index the product manually.
+
+
+
+
+
diff --git a/docs/known-issues/en/update-users-name-in-the-login-section.md b/docs/known-issues/en/update-users-name-in-the-login-section.md
index 77d69e707..1850e5dde 100644
--- a/docs/known-issues/en/update-users-name-in-the-login-section.md
+++ b/docs/known-issues/en/update-users-name-in-the-login-section.md
@@ -3,8 +3,8 @@ title: "Update user's name in the login section"
 id: 2jshd2ApTq7hKNLbQiCWdS
 status: PUBLISHED
 createdAt: 2022-03-14T17:20:40.732Z
-updatedAt: 2022-11-25T21:57:07.628Z
-publishedAt: 2022-11-25T21:57:07.628Z
+updatedAt: 2024-02-16T20:26:07.889Z
+publishedAt: 2024-02-16T20:26:07.889Z
 firstPublishedAt: 2022-03-14T17:20:42.505Z
 contentType: knownIssue
 productTeam: Identity
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Identity
 slug: update-users-name-in-the-login-section
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 542029
 ---
 
diff --git a/docs/known-issues/en/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md b/docs/known-issues/en/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
index a351d19d4..b49cb4708 100644
--- a/docs/known-issues/en/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
+++ b/docs/known-issues/en/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
@@ -3,8 +3,8 @@ title: 'Updating Product Specifications Unviable due to Lacking Property on GET
 id: 6FeuIyF2E5WdS0PNRRzgdA
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:06.720Z
-updatedAt: 2022-11-25T21:44:35.149Z
-publishedAt: 2022-11-25T21:44:35.149Z
+updatedAt: 2024-02-16T20:29:52.260Z
+publishedAt: 2024-02-16T20:29:52.260Z
 firstPublishedAt: 2022-06-28T16:55:07.124Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 301725
 ---
 
diff --git a/docs/known-issues/en/upload-file-not-working-on-adminportalsitesdefaultcode.md b/docs/known-issues/en/upload-file-not-working-on-adminportalsitesdefaultcode.md
new file mode 100644
index 000000000..7d65bc851
--- /dev/null
+++ b/docs/known-issues/en/upload-file-not-working-on-adminportalsitesdefaultcode.md
@@ -0,0 +1,49 @@
+---
+title: 'Upload file not working on admin/portal/#/sites/default/code'
+id: 5pFAkaymcuOQMAqUDGPQZK
+status: PUBLISHED
+createdAt: 2023-09-12T13:37:36.429Z
+updatedAt: 2023-09-12T13:37:37.323Z
+publishedAt: 2023-09-12T13:37:37.323Z
+firstPublishedAt: 2023-09-12T13:37:37.323Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: upload-file-not-working-on-adminportalsitesdefaultcode
+locale: en
+kiStatus: Backlog
+internalReference: 897956
+---
+
+## Summary
+
+
+When trying to upload a new file on admin/portal/#/sites/default/code nothing happens. Checking the console on devTools we can see an error message:
+"eventTrackerService is not defined"
+
+
+##
+
+## Simulation
+
+
+
+1. Go to admin/portal/#/sites/default/code
+2. Go to New -> Upload File -> select the file you wish to import -> click on create
+ ![](https://vtexhelp.zendesk.com/attachments/token/4uSgPeUxG9xAOkTq1HUs8khX6/?name=image.png)
+3. Check that nothing happens.
+
+
+##
+
+## Workaround
+
+
+The WA is to create the file directly on this UI.
+Go to New -> File -> Name your file and click on create -> Insert the code and click on save.
+
+
+
+
+
diff --git a/docs/known-issues/en/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md b/docs/known-issues/en/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
new file mode 100644
index 000000000..5e624a543
--- /dev/null
+++ b/docs/known-issues/en/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
@@ -0,0 +1,53 @@
+---
+title: 'User can still see and access CMS features even without the correct permission'
+id: n2BmrCyzXD04sysczRuyt
+status: PUBLISHED
+createdAt: 2024-06-07T12:22:10.494Z
+updatedAt: 2024-06-07T12:22:11.466Z
+publishedAt: 2024-06-07T12:22:11.466Z
+firstPublishedAt: 2024-06-07T12:22:11.466Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: user-can-still-see-and-access-cms-features-even-without-the-correct-permission
+locale: en
+kiStatus: Backlog
+internalReference: 1046263
+---
+
+## Summary
+
+
+If the user doesn't have any of the CMS permissions the user shouldn't be able to access or even see the CMS modules. But it is not happening.
+
+
+##
+
+## Simulation
+
+
+Try accessing the CMS modules using a user that doesn't have the following LM permissions:
+
+      CMS:
+
+- See CMS menu on the top-bar
+- Settings
+
+GraphQL:
+- CMS GraphQL API
+
+The user will still be able to access and see the resources (but not edit).
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
new file mode 100644
index 000000000..cc6ee8db8
--- /dev/null
+++ b/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -0,0 +1,53 @@
+---
+title: 'User only with the role "User Administrator - RESTRICTED" is not able to list the users'
+id: ifXUAzgJ1xr8ezhqKpRUI
+status: PUBLISHED
+createdAt: 2023-11-08T18:07:14.508Z
+updatedAt: 2023-11-08T18:07:15.030Z
+publishedAt: 2023-11-08T18:07:15.030Z
+firstPublishedAt: 2023-11-08T18:07:15.030Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users
+locale: en
+kiStatus: Backlog
+internalReference: 932666
+---
+
+## Summary
+
+
+If an admin user only has the role "**User Administrator - RESTRICTED**" ("**Save user**" resource), the list of users is not available and it is not possible to make any necessary edits or deletions.
+
+
+##
+
+## Simulation
+
+
+
+- Have an user with only the role "**User Administrator - RESTRICTED**";
+- Access the "**Admin Users**" page with this user (e.g. https://my-account-here.myvtex.com/admin/users);
+- You may notice that the list is empty, even with users already registered ("_No users found :: The user search returned an empty list. Try removing any search filters or adding new users to this account._"):
+ ![](https://vtexhelp.zendesk.com/attachments/token/fZ2k11R3xPrhNv5yHVkv9alam/?name=image.png)
+
+- It is possible to add the user you want, and include the necessary roles, but we can't access the users to add/edit/remove roles, or even delete the user through their registration, but only through the role.
+
+
+##
+
+## Workaround
+
+
+You can add or remove the user to the role by accessing the role directly.
+
+You can also create a custom role with only the resources "**Get paged roles**" and "**Get paged users**":
+ ![](https://vtexhelp.zendesk.com/attachments/token/yjNfjlnfFaBrXZE6gx97OaxHy/?name=image.png)
+And then, add it to the user who can save users.
+
+
+
+
+
diff --git a/docs/known-issues/en/users-cant-access-gift-card-admin-looping-page.md b/docs/known-issues/en/users-cant-access-gift-card-admin-looping-page.md
new file mode 100644
index 000000000..491e41761
--- /dev/null
+++ b/docs/known-issues/en/users-cant-access-gift-card-admin-looping-page.md
@@ -0,0 +1,42 @@
+---
+title: "Users can't access Gift Card admin (looping page)"
+id: 5FowAAf8VulbVXcQIeSmHd
+status: PUBLISHED
+createdAt: 2024-05-02T15:26:57.386Z
+updatedAt: 2024-05-02T15:26:58.463Z
+publishedAt: 2024-05-02T15:26:58.463Z
+firstPublishedAt: 2024-05-02T15:26:58.463Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: users-cant-access-gift-card-admin-looping-page
+locale: en
+kiStatus: Backlog
+internalReference: 1025971
+---
+
+## Summary
+
+
+If users block third-party cookies (browser settings) they won't be able to access the Gift Card module in admin, there's a cookie set in another VTEX domain.
+
+
+##
+
+## Simulation
+
+
+After blocking third-party cookies is possible to simulate the issue mentioned above, you can also inspect the page (developer tools) and go to Network tab (search for Vale.aspx), there will be a 302 status code.
+
+
+##
+
+## Workaround
+
+
+Whitelist third-party cookies present in myvtex.com domain.
+
+
+
+
diff --git a/docs/known-issues/en/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md b/docs/known-issues/en/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
new file mode 100644
index 000000000..9919b17f5
--- /dev/null
+++ b/docs/known-issues/en/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
@@ -0,0 +1,48 @@
+---
+title: 'Users with more than one order registered on BK entity with different emails can not see the orders on My Account page'
+id: 43NLxAbOtyVzOCdS9Dns8c
+status: PUBLISHED
+createdAt: 2024-02-21T22:30:42.218Z
+updatedAt: 2024-02-21T22:30:43.137Z
+publishedAt: 2024-02-21T22:30:43.137Z
+firstPublishedAt: 2024-02-21T22:30:43.137Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page
+locale: en
+kiStatus: Backlog
+internalReference: 986324
+---
+
+## Summary
+
+
+Due profile unification some users can have orders with diffents emails, and this a problem to show the orders on my account (my orders) page.
+
+The my orders request this info on BK entity of Master Data to remove the impact of indexing delay, but the BK has the history and orders with different emails. But the OMS has the code line to check if the email returned is correct, checking the consultant email and the email registered on orders.
+
+
+##
+
+## Simulation
+
+
+Two orders created with different emails, example joao@gmail.com and joao2@gmail.com, when this user has the unification profile only one email will be valid.
+After that if the joao2@gmail.com log in on my account page, it will not be possible to see the orders because there is an old order without character "2" on email, so different main key (email.)
+
+
+
+
+##
+
+## Workaround
+
+
+There is no workaround for now.
+
+
+
+
+
diff --git a/docs/known-issues/en/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md b/docs/known-issues/en/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
new file mode 100644
index 000000000..689e47445
--- /dev/null
+++ b/docs/known-issues/en/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
@@ -0,0 +1,45 @@
+---
+title: "UseSessionRegionAtCheckout doesn't work properly when adding the first item to the cart"
+id: 2NzgWTbaHF47f5dl49A2D5
+status: PUBLISHED
+createdAt: 2023-10-24T22:51:27.435Z
+updatedAt: 2023-10-26T10:55:29.843Z
+publishedAt: 2023-10-26T10:55:29.843Z
+firstPublishedAt: 2023-10-24T22:51:28.246Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart
+locale: en
+kiStatus: Backlog
+internalReference: 925049
+---
+
+## Summary
+
+
+If an account has the toggle 'UseSessionRegionAtCheckout' configured, when adding an item and the orderForm has no 'shippingData', the seller is not set, showing different prices and availability.
+
+
+##
+
+## Simulation
+
+
+
+- The account must be using UseSessionRegionAtCheckout;
+- Set a regionId in the session;
+- Add an item to the cart; it may show different prices and availability.
+
+
+##
+
+## Workaround
+
+
+Refresh the orderForm (API Get current or create a new cart) using the parameter `?refreshOutdatedData=true`.
+
+
+
+
diff --git a/docs/known-issues/en/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md b/docs/known-issues/en/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
index a5051781d..2826c207f 100644
--- a/docs/known-issues/en/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
+++ b/docs/known-issues/en/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
@@ -3,8 +3,8 @@ title: 'Using many filters in the OMS list affects the results in the report'
 id: WO9AvZxmUkmil35OZb8Lr
 status: PUBLISHED
 createdAt: 2023-02-17T17:45:57.039Z
-updatedAt: 2023-02-17T17:52:41.370Z
-publishedAt: 2023-02-17T17:52:41.370Z
+updatedAt: 2024-06-28T19:28:50.107Z
+publishedAt: 2024-06-28T19:28:50.107Z
 firstPublishedAt: 2023-02-17T17:50:29.929Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,12 +12,13 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: using-many-filters-in-the-oms-list-affects-the-results-in-the-report
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 756198
 ---
 
 ## Summary
 
+
 The use of filters in the Order Management List generates a parameter in the URL that helps define what is shown when the page loads and to generate the exported orders report. In that sense, as we use more and more filters, the parameters included in the URL increase proportionally, and the query string increase, reaching points (size) that can generate various types of unwanted behaviors.
 
 In this case, the problem caused by using many filters at the same time (size of the **Query String** in the URL) affects the results of the exported report, showing fewer orders than expected.
@@ -25,13 +26,19 @@ In this case, the problem caused by using many filters at the same time (size of
 It is important to note that here we are talking about the **size of the Query String generated in the URL**, this means that it is not the number of filters used directly, but the size of each parameter. Very large filter names can  limit the number of filter you are able to use to generate a consistent report.
 
 
+##
+
 ## Simulation
 
+
 This scenario can be simulated by using multiple "long" filters in the OMS list and exporting the orders. You can see that the export shows fewer orders than the OMS list.
 
 
+##
+
 ## Workaround
 
+
 It is possible to think of alternative ways to avoid this type of issue in the report. Here are some points that may be useful:
 
 - Optimizing the name of the parameters could be a good practice.
@@ -41,3 +48,6 @@ It is possible to think of alternative ways to avoid this type of issue in the r
 These are just ideas to avoid accumulating filters and generating this inconsistency in the exported information. Other solutions can be used.
 
 
+
+
+
diff --git a/docs/known-issues/en/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md b/docs/known-issues/en/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
new file mode 100644
index 000000000..51d6d359a
--- /dev/null
+++ b/docs/known-issues/en/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
@@ -0,0 +1,48 @@
+---
+title: 'Using slider-layout with the prop navigationStep to 1 causes last dots to be empty'
+id: 28hbmflHNhAQmHN51Y6abX
+status: PUBLISHED
+createdAt: 2023-09-29T14:41:34.387Z
+updatedAt: 2023-09-29T14:57:48.863Z
+publishedAt: 2023-09-29T14:57:48.863Z
+firstPublishedAt: 2023-09-29T14:41:35.227Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty
+locale: en
+kiStatus: Backlog
+internalReference: 910125
+---
+
+## Summary
+
+
+When we have a slider-layout block with the `navigationStep` prop set to 1 and the `itemsPerPage` different than 1 the last dot will be empty and it is not possible to delete it.
+
+
+##
+
+## Simulation
+
+
+
+- Create a new slider-layout block
+- Set the `navigationStep` to 1
+- Set the `itemsPerPage` in a value different than 1
+- Using the slider arrows, try to navigate to the last dot on the slider
+- You'll see that the last dot is empty
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md b/docs/known-issues/en/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
index 1e736f35c..5eb4dce83 100644
--- a/docs/known-issues/en/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
+++ b/docs/known-issues/en/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
@@ -3,8 +3,8 @@ title: 'utmi_p e utmi_pc not being kept on the URL after login'
 id: 7e8EO8EWEJCLbXs16ZofQk
 status: PUBLISHED
 createdAt: 2022-03-16T16:17:55.535Z
-updatedAt: 2022-11-25T22:11:21.772Z
-publishedAt: 2022-11-25T22:11:21.772Z
+updatedAt: 2024-02-16T20:29:25.217Z
+publishedAt: 2024-02-16T20:29:25.217Z
 firstPublishedAt: 2022-03-16T16:17:55.979Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: utmip-e-utmipc-not-being-kept-on-the-url-after-login
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 372787
 ---
 
diff --git a/docs/known-issues/en/validatecartmutation-failing-when-large-payload.md b/docs/known-issues/en/validatecartmutation-failing-when-large-payload.md
new file mode 100644
index 000000000..b517a37ee
--- /dev/null
+++ b/docs/known-issues/en/validatecartmutation-failing-when-large-payload.md
@@ -0,0 +1,46 @@
+---
+title: 'ValidateCartMutation failing when large payload'
+id: 5YmPMVGsi92owcmICg3CY3
+status: PUBLISHED
+createdAt: 2024-02-21T15:23:44.054Z
+updatedAt: 2024-02-21T15:23:44.919Z
+publishedAt: 2024-02-21T15:23:44.919Z
+firstPublishedAt: 2024-02-21T15:23:44.919Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: validatecartmutation-failing-when-large-payload
+locale: en
+kiStatus: Backlog
+internalReference: 985867
+---
+
+## Summary
+
+
+
+When adding several products in minicart, depending on the information associated with those products, if we receive a payloadTooLarge error, the product will be added to the cart but will not pass to orderForm correctly
+
+
+##
+
+## Simulation
+
+
+
+
+- Add products to the cart till you receive a 413 Payload Too Large error
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md b/docs/known-issues/en/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
index 0664a0e63..610cac0c5 100644
--- a/docs/known-issues/en/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
+++ b/docs/known-issues/en/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
@@ -3,8 +3,8 @@ title: 'Verification transactions when saving card in MyCards are not automatica
 id: 3VqRlcnzHqDEx7v1IIlBuf
 status: PUBLISHED
 createdAt: 2022-03-27T15:14:55.382Z
-updatedAt: 2022-11-25T22:08:31.611Z
-publishedAt: 2022-11-25T22:08:31.611Z
+updatedAt: 2024-02-16T20:27:46.524Z
+publishedAt: 2024-02-16T20:27:46.524Z
 firstPublishedAt: 2022-03-27T15:14:56.630Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 347084
 ---
 
diff --git a/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md
new file mode 100644
index 000000000..4aa94de7c
--- /dev/null
+++ b/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -0,0 +1,60 @@
+---
+title: 'Version author "Note: Not found on VTEX ID." on the profile'
+id: 0X6Aj6YdCXXfNweAkDS46
+status: PUBLISHED
+createdAt: 2023-10-04T21:48:14.699Z
+updatedAt: 2023-10-04T22:14:45.195Z
+publishedAt: 2023-10-04T22:14:45.195Z
+firstPublishedAt: 2023-10-04T21:48:15.379Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: version-author-note-not-found-on-vtex-id-on-the-profile
+locale: en
+kiStatus: Scheduled
+internalReference: 914314
+---
+
+## Summary
+
+
+When the customer makes a purchase, the author of the version is given an user id (guid) or a service, followed by the login/name/description "`Note: Not found on VTEX ID.`" on the profile.
+This behavior does not impact the profile or shopper experience, once this is only about the UI, and it is possible to check the information by version API.
+
+
+##
+
+## Simulation
+
+
+
+- Access Master Data CRM (for example https://my-account-here.vtexcrm.com.br);
+- Access CL (Clientes) Data Entity tab:
+- Select a document and click on the eye icon to view the data;
+- Click on "_Change Log_" button;
+- Open a recent version;
+- Check the "_Version author_", it will be an user id, and the name "`Note: Not found on VTEX ID.`", for example:
+ ![](https://vtexhelp.zendesk.com/attachments/token/9ngSibhlO4er0Df3Fi7oQAhot/?name=image.png)
+ ![](https://vtexhelp.zendesk.com/attachments/token/8tlsDbxNSFFHdJMVHf2yvctem/?name=image.png)
+
+- Checking by Get version API:
+ ![](https://vtexhelp.zendesk.com/attachments/token/MRrTRox5E0t91F3OpsDcRmJ9z/?name=image.png)
+
+    "updatedBy_USER": "{\"Id\":\"d6d8269f-e7cc-4e4b-8b89-3b46a1407937\",\"Login\":\"vtex-service::checkout::stable\",\"Name\":null}",
+
+
+
+##
+
+## Workaround
+
+
+You can check the author using our APIs:
+
+- List versions
+- Get version
+
+
+
+
diff --git a/docs/known-issues/en/via-integration-not-sending-the-description-in-card.md b/docs/known-issues/en/via-integration-not-sending-the-description-in-card.md
index 1f256cee7..6a36630f4 100644
--- a/docs/known-issues/en/via-integration-not-sending-the-description-in-card.md
+++ b/docs/known-issues/en/via-integration-not-sending-the-description-in-card.md
@@ -3,8 +3,8 @@ title: 'Via Integration not sending the description in card'
 id: Da5jnqoSO8an64jy29VhM
 status: PUBLISHED
 createdAt: 2023-05-16T16:47:19.803Z
-updatedAt: 2023-05-18T18:03:54.502Z
-publishedAt: 2023-05-18T18:03:54.502Z
+updatedAt: 2023-06-19T12:30:03.552Z
+publishedAt: 2023-06-19T12:30:03.552Z
 firstPublishedAt: 2023-05-16T16:47:20.416Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: via-integration-not-sending-the-description-in-card
 locale: en
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 826488
 ---
 
diff --git a/docs/known-issues/en/video-attribute-is-not-being-sent-from-seller-to-marketplace.md b/docs/known-issues/en/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
index e5dc8d5e1..53a4ef354 100644
--- a/docs/known-issues/en/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
+++ b/docs/known-issues/en/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
@@ -3,8 +3,8 @@ title: 'Video attribute is not being sent from seller to marketplace'
 id: 6JfHpP6F8TGmJofoKc99ON
 status: PUBLISHED
 createdAt: 2022-02-07T20:07:23.358Z
-updatedAt: 2023-05-09T19:03:49.838Z
-publishedAt: 2023-05-09T19:03:49.838Z
+updatedAt: 2024-02-16T20:23:28.657Z
+publishedAt: 2024-02-16T20:23:28.657Z
 firstPublishedAt: 2022-02-07T20:07:23.814Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: video-attribute-is-not-being-sent-from-seller-to-marketplace
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 519412
 ---
 
diff --git a/docs/known-issues/en/video-component-doesnt-work-properly-on-ios-devices.md b/docs/known-issues/en/video-component-doesnt-work-properly-on-ios-devices.md
index f24fa0289..6291ba5e2 100644
--- a/docs/known-issues/en/video-component-doesnt-work-properly-on-ios-devices.md
+++ b/docs/known-issues/en/video-component-doesnt-work-properly-on-ios-devices.md
@@ -3,8 +3,8 @@ title: "Video component doesn't work properly on iOS devices"
 id: 2bRQkTdRk2OJQMw5CKVieW
 status: PUBLISHED
 createdAt: 2022-07-01T17:21:47.912Z
-updatedAt: 2022-11-25T22:13:54.314Z
-publishedAt: 2022-11-25T22:13:54.314Z
+updatedAt: 2024-02-16T20:25:23.862Z
+publishedAt: 2024-02-16T20:25:23.862Z
 firstPublishedAt: 2022-07-01T17:21:48.826Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: video-component-doesnt-work-properly-on-ios-devices
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 609462
 ---
 
diff --git a/docs/known-issues/en/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md b/docs/known-issues/en/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
new file mode 100644
index 000000000..ef6766d1a
--- /dev/null
+++ b/docs/known-issues/en/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
@@ -0,0 +1,45 @@
+---
+title: 'view_cart event is only received on the dataLayer every other time'
+id: 73fimN0XczGQch20BhGAOo
+status: PUBLISHED
+createdAt: 2024-06-12T12:58:59.438Z
+updatedAt: 2024-06-12T12:59:00.499Z
+publishedAt: 2024-06-12T12:59:00.499Z
+firstPublishedAt: 2024-06-12T12:59:00.499Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: viewcart-event-is-only-received-on-the-datalayer-every-other-time
+locale: en
+kiStatus: Backlog
+internalReference: 1048306
+---
+
+## Summary
+
+
+The event view_cart is only received on the dataLayer every other time.
+
+
+##
+
+## Simulation
+
+
+Try opening the minicart for the first time, this time the event will be received
+When you try opening for the second time the event will not be received
+On the third time, the event will be received again and so on
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md b/docs/known-issues/en/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
new file mode 100644
index 000000000..0d6f57450
--- /dev/null
+++ b/docs/known-issues/en/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
@@ -0,0 +1,46 @@
+---
+title: 'view_cart event is triggered twice when we change product quantity in minicart'
+id: 3NlB10z0ulKu7sySxPgkmp
+status: PUBLISHED
+createdAt: 2024-05-28T20:13:35.657Z
+updatedAt: 2024-05-28T20:13:36.602Z
+publishedAt: 2024-05-28T20:13:36.602Z
+firstPublishedAt: 2024-05-28T20:13:36.602Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart
+locale: en
+kiStatus: Backlog
+internalReference: 1040772
+---
+
+## Summary
+
+
+When we change the quantity of a product in the minicart the view_cart event is triggered twice
+
+
+##
+
+## Simulation
+
+
+
+- Add a product to the minicart;
+- Open the minicart;
+- Change the quantity of the product on the minicart;
+- Check your dataLayer, the view_cart event is triggered twice
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/visited-product-feature-does-not-work-properly.md b/docs/known-issues/en/visited-product-feature-does-not-work-properly.md
index 5bffc9d93..cb82a8d9e 100644
--- a/docs/known-issues/en/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/en/visited-product-feature-does-not-work-properly.md
@@ -3,8 +3,8 @@ title: ' "Visited product" feature does not work properly'
 id: 5AiCVwLkGToEgtLkZVPe5i
 status: PUBLISHED
 createdAt: 2022-11-25T18:45:15.389Z
-updatedAt: 2022-11-30T19:05:56.190Z
-publishedAt: 2022-11-30T19:05:56.190Z
+updatedAt: 2024-02-16T20:27:41.835Z
+publishedAt: 2024-02-16T20:27:41.835Z
 firstPublishedAt: 2022-11-25T18:45:15.854Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: visited-product-feature-does-not-work-properly
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 701169
 ---
 
diff --git a/docs/known-issues/en/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md b/docs/known-issues/en/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
new file mode 100644
index 000000000..388405c28
--- /dev/null
+++ b/docs/known-issues/en/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
@@ -0,0 +1,51 @@
+---
+title: 'Visual merchandising rules do not work when multiple search terms are provided'
+id: 6FkfnnvFiYXYqPgMrpDgM1
+status: PUBLISHED
+createdAt: 2024-06-20T21:41:14.250Z
+updatedAt: 2024-06-20T21:41:15.088Z
+publishedAt: 2024-06-20T21:41:15.088Z
+firstPublishedAt: 2024-06-20T21:41:15.088Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided
+locale: en
+kiStatus: Backlog
+internalReference: 1053623
+---
+
+## Summary
+
+
+Although it's possible to provide multiple search terms while creating a visual merchandising rule for the Intelligent Search, they can not be used. The rule will be considered invalid and will not be applied.
+
+Different search terms can return completely different products in a search result in a different order, which is incompatible with the action of pinning (_promote_) or hiding (_remove_) some products that a visual rule offers.
+
+As an invalid action, this condition is not expected to be provided and will be removed from the interface.
+
+
+##
+
+## Simulation
+
+
+
+- Create a visual merchandising rule
+- Apply multiple search terms as a condition for the rule
+- Select some products to pin and/or hide
+- Search for one of these search terms and observe that the results won't have the rule applied
+- It's also possible to observe the same through the explained search function from the admin, which will highlight that no rules were applied to the search
+
+
+##
+
+## Workaround
+
+
+This objective is achieved through manual merchandising rules. The action of pinning and hiding products is directly compatible with the promote and remove actions for a manual rule.
+
+
+
+
diff --git a/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 7ffc0ca7c..e189b32d0 100644
--- a/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -42,6 +42,6 @@ Don’t worry: turning off this option will not make your store unprotected.
 If after these steps your Admin or store is still not loading, we advise you to try another browser.
 </div>
 
-![Firefox bug EN](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/06a078dc34744d8e07cf858e2288679a/Firefox_bug_EN.jpg)
+![Firefox bug EN](//images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/06a078dc34744d8e07cf858e2288679a/Firefox_bug_EN.jpg)
 
 
diff --git a/docs/known-issues/en/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md b/docs/known-issues/en/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
new file mode 100644
index 000000000..beafd3628
--- /dev/null
+++ b/docs/known-issues/en/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
@@ -0,0 +1,49 @@
+---
+title: '<vtex.cmc ProductGifts/> does not work before acessing checkout'
+id: 3blfXfhPvY2cNEzBYGEmAo
+status: PUBLISHED
+createdAt: 2024-05-08T17:11:51.770Z
+updatedAt: 2024-05-08T17:11:52.715Z
+publishedAt: 2024-05-08T17:11:52.715Z
+firstPublishedAt: 2024-05-08T17:11:52.715Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: vtexcmc-productgifts-does-not-work-before-acessing-checkout
+locale: en
+kiStatus: Backlog
+internalReference: 1029719
+---
+
+## Summary
+
+
+Currenlty, the <vtex.cmc ProductGifts> legacy controller doesn't load the expected gifts before an user first accesses a store's checkout.
+
+In other words, it is necessary to first go to the cart for the gifts to properly render on the checkout and then, in this given session, the user would have to return to the product page for these gifts to be exhibited in the controller.
+
+
+##
+
+## Simulation
+
+
+1 - Create a product page using the <vtex.cmc ProductGifts> controller.
+2 - Create a Buy One, Get One promotion to lead the related gifts.
+3 - Load the product page, no gifts will be rendered.
+4 - Go to the checkout page and the gifts will load.
+5 - Return to the product page and then the gifts will be loading in the product page.
+
+
+##
+
+## Workaround
+
+
+Use other cross selling controllers to customize and display items as gifts, such as similar, suggestions and accessories
+
+
+
+
+
diff --git a/docs/known-issues/en/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md b/docs/known-issues/en/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
index 937ae4ab1..3e21e0def 100644
--- a/docs/known-issues/en/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
+++ b/docs/known-issues/en/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
@@ -3,8 +3,8 @@ title: 'We have a problem validating the ClientId field of the Giftcard on admin
 id: 4S7CziQfj5P2NLAgUKnJnP
 status: PUBLISHED
 createdAt: 2022-03-28T00:29:38.482Z
-updatedAt: 2022-11-25T22:07:33.502Z
-publishedAt: 2022-11-25T22:07:33.502Z
+updatedAt: 2024-02-16T20:24:40.988Z
+publishedAt: 2024-02-16T20:24:40.988Z
 firstPublishedAt: 2022-03-28T00:29:39.028Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 454388
 ---
 
diff --git a/docs/known-issues/en/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md b/docs/known-issues/en/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
index d949ecf81..dd3095ed5 100644
--- a/docs/known-issues/en/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
+++ b/docs/known-issues/en/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
@@ -3,8 +3,8 @@ title: "Webanalytics Viewpart Shows success even when it isn't working"
 id: 73oMf2Wxkgw1feWUvntX6s
 status: PUBLISHED
 createdAt: 2023-03-09T18:20:47.358Z
-updatedAt: 2023-03-09T18:20:52.456Z
-publishedAt: 2023-03-09T18:20:52.456Z
+updatedAt: 2024-07-01T18:48:55.053Z
+publishedAt: 2024-07-01T18:48:55.053Z
 firstPublishedAt: 2023-03-09T18:20:48.023Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: webanalytics-viewpart-shows-success-even-when-it-isnt-working
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 768059
 ---
 
diff --git a/docs/known-issues/en/webops-app-is-not-fully-integrated-with-headless-cms.md b/docs/known-issues/en/webops-app-is-not-fully-integrated-with-headless-cms.md
new file mode 100644
index 000000000..72a04d82a
--- /dev/null
+++ b/docs/known-issues/en/webops-app-is-not-fully-integrated-with-headless-cms.md
@@ -0,0 +1,42 @@
+---
+title: 'Webops app is not fully integrated with Headless CMS'
+id: 577fIocKB9BYYCOkN9dZfW
+status: PUBLISHED
+createdAt: 2024-06-12T19:42:12.627Z
+updatedAt: 2024-06-27T17:35:21.924Z
+publishedAt: 2024-06-27T17:35:21.924Z
+firstPublishedAt: 2024-06-12T19:42:13.699Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: webops-app-is-not-fully-integrated-with-headless-cms
+locale: en
+kiStatus: Backlog
+internalReference: 1048810
+---
+
+## Summary
+
+
+The app `vtex.webops` is not fully integrated with the headless CMS, this is related to externally hosted Github repositories and the publishing process
+
+
+##
+
+## Simulation
+
+
+Try making an update on the headless CMS using the webops app, this will fail and there's not going to be a commit on the repository
+
+
+##
+
+## Workaround
+
+
+The workaround is to manually create a commit in your store's Git repository to trigger the store build and apply the changes made in the Headless CMS.
+
+
+
+
diff --git a/docs/known-issues/en/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md b/docs/known-issues/en/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
index d609576b4..4f00e58e5 100644
--- a/docs/known-issues/en/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
+++ b/docs/known-issues/en/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
@@ -1,38 +1,38 @@
 ---
 title: 'When a component of the kit look is out of stock, the kit is shown as sold out on searching'
-id: 56QpnBz2ayEAe00L9ojSI0
-status: DRAFT
-createdAt: 2022-01-21T18:06:21.645Z
-updatedAt: 2022-03-16T16:22:00.845Z
-publishedAt: 
-firstPublishedAt: 
+id: 5PRtTKk1HyGkKciOussWEI
+status: PUBLISHED
+createdAt: 2017-03-29T23:44:56.615Z
+updatedAt: 2022-12-22T20:43:08.857Z
+publishedAt: 2022-12-22T20:43:08.857Z
+firstPublishedAt: 2017-03-29T23:46:36.720Z
 contentType: knownIssue
-productTeam: Portal
+productTeam: Marketing & Merchandising
 author: 2mXZkbi0oi061KicTExNjo
-tag: Portal
+tag: Catalog
 slug: when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching
 locale: en
 kiStatus: Backlog
-internalReference: 342720
+internalReference: 
 ---
 
 ## Summary
 
-
 When a component of kit look is without stock, the entire kit is shown as sold out on searching.
 
+## Simulation
 
+<!--- Conta original era automacaoqa, removemos por conta de EDU-2582 --->
 
-## Simulation
+Kit Look: `https://lojateste.vtexcommercebeta.com.br/admin/site/ProdutoForm.aspx?id=2000205`
 
+Component unavailable: `https://lojateste.vtexcommercebeta.com.br/admin/site/SkuForm.aspx?IdSku=2000362`
 
-- Create a Kit Look;
-- Set the stock of one of the components to unavailable;
-- The Kit Look page will be unavailable.
+Correct exhibition on the product page: `https://lojateste.vtexcommercebeta.com.br/admin/site/SkuForm.aspx?IdSku=2000362`
 
+Incorrect exhibition on searching: `https://lojateste.vtexcommercebeta.com.br/kits`
 
 ## Workaround
 
-
 Only use kit look if you're sure that all the components have stock.
 
diff --git a/docs/known-issues/en/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md b/docs/known-issues/en/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
new file mode 100644
index 000000000..7513a5e13
--- /dev/null
+++ b/docs/known-issues/en/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
@@ -0,0 +1,44 @@
+---
+title: 'When accessing my orders, the name that appears is the name of the ProductName without the SKU Name information.'
+id: 1PTEStTC2MDQwZpE0myF44
+status: PUBLISHED
+createdAt: 2024-03-08T13:16:01.672Z
+updatedAt: 2024-03-08T13:16:02.950Z
+publishedAt: 2024-03-08T13:16:02.950Z
+firstPublishedAt: 2024-03-08T13:16:02.950Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information
+locale: en
+kiStatus: No Fix
+internalReference: 694809
+---
+
+## Summary
+
+
+When accessing "my orders", the name that appears is the name of the "ProductName" without the "SKU Name" information, only in the IO interface.
+
+
+
+##
+
+## Simulation
+
+
+Accessing my orders, you will see that the product name is composed only by the "ProductName" without the information of the "SKU Name".
+
+
+##
+
+## Workaround
+
+
+We have no workaround at the moment.
+
+
+
+
+
diff --git a/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 3dc59ccad..6a8bb04c0 100644
--- a/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -3,8 +3,8 @@ title: 'When adding a SKU through our "Change Order" functionality, the product
 id: 35Q3KoOSsUr9n9XEDIk7nk
 status: PUBLISHED
 createdAt: 2022-04-07T14:53:35.829Z
-updatedAt: 2022-11-25T22:02:48.606Z
-publishedAt: 2022-11-25T22:02:48.606Z
+updatedAt: 2024-02-16T20:24:27.100Z
+publishedAt: 2024-02-16T20:24:27.100Z
 firstPublishedAt: 2022-04-07T14:53:36.256Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 557978
 ---
 
diff --git a/docs/known-issues/en/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md b/docs/known-issues/en/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
index f36d2dd87..d204ab335 100644
--- a/docs/known-issues/en/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
+++ b/docs/known-issues/en/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
@@ -3,8 +3,8 @@ title: "When disabling native service worker it's not possible to use a custom o
 id: 1GpzVam1nuGbrKR4Izx6D9
 status: PUBLISHED
 createdAt: 2023-03-14T18:20:55.443Z
-updatedAt: 2023-03-14T18:20:55.953Z
-publishedAt: 2023-03-14T18:20:55.953Z
+updatedAt: 2024-02-02T21:00:43.540Z
+publishedAt: 2024-02-02T21:00:43.540Z
 firstPublishedAt: 2023-03-14T18:20:55.953Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index dc8d64217..f97880e29 100644
--- a/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -3,8 +3,8 @@ title: 'When loading the "Catalog Maping" page on admin the initial message is n
 id: 4WszmRZ5jpeSDNTEuFIdwF
 status: PUBLISHED
 createdAt: 2022-12-15T12:32:17.741Z
-updatedAt: 2022-12-15T12:32:18.420Z
-publishedAt: 2022-12-15T12:32:18.420Z
+updatedAt: 2024-02-16T20:23:22.033Z
+publishedAt: 2024-02-16T20:23:22.033Z
 firstPublishedAt: 2022-12-15T12:32:18.420Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 717066
 ---
 
diff --git a/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index a3b6c27de..8f691bdeb 100644
--- a/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -3,8 +3,8 @@ title: 'When settleId is sent as null and code as "refund-manually" our gateway
 id: 2PdRRjHDODY2Tk0VItO4Fo
 status: PUBLISHED
 createdAt: 2022-07-11T17:37:43.961Z
-updatedAt: 2022-11-25T22:04:38.681Z
-publishedAt: 2022-11-25T22:04:38.681Z
+updatedAt: 2024-02-16T20:28:17.704Z
+publishedAt: 2024-02-16T20:28:17.704Z
 firstPublishedAt: 2022-07-11T17:37:44.954Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 615050
 ---
 
diff --git a/docs/known-issues/en/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md b/docs/known-issues/en/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
index ad5af7d84..219a38db8 100644
--- a/docs/known-issues/en/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
+++ b/docs/known-issues/en/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
@@ -3,8 +3,8 @@ title: 'When shippingEstimate is = 0, the deliverySlaInMinutes calculation retur
 id: UGk2WYb3w3ZWH4pL07TNg
 status: PUBLISHED
 createdAt: 2022-02-01T13:04:45.737Z
-updatedAt: 2022-11-25T21:51:01.802Z
-publishedAt: 2022-11-25T21:51:01.802Z
+updatedAt: 2024-02-16T20:24:38.902Z
+publishedAt: 2024-02-16T20:24:38.902Z
 firstPublishedAt: 2022-02-01T13:04:46.164Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null
 locale: en
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 514835
 ---
 
diff --git a/docs/known-issues/en/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md b/docs/known-issues/en/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
new file mode 100644
index 000000000..10271ba47
--- /dev/null
+++ b/docs/known-issues/en/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
@@ -0,0 +1,46 @@
+---
+title: "When using horizontal filters, after choosing three of them, the filter's options doesn't colapse anymore"
+id: 7xPLXjZMqwxQmWwJsd63eC
+status: PUBLISHED
+createdAt: 2023-07-11T12:30:50.198Z
+updatedAt: 2024-02-16T19:16:06.662Z
+publishedAt: 2024-02-16T19:16:06.662Z
+firstPublishedAt: 2023-07-11T12:30:50.962Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore
+locale: en
+kiStatus: Backlog
+internalReference: 859382
+---
+
+## Summary
+
+
+When the store is using the filters on the horizontal option every time you click on a filter its options will collapse. But, when you click on a filter for the third time the filter will not collapse anymore. It will crash.
+
+
+##
+
+## Simulation
+
+
+
+- Find a store using the horizontal filter option
+- Choose three different filters
+- On the third one, it will crash
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md b/docs/known-issues/en/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
new file mode 100644
index 000000000..4d03d24b3
--- /dev/null
+++ b/docs/known-issues/en/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
@@ -0,0 +1,46 @@
+---
+title: 'Wrong SpotPrice for items with UnitMultiplier greater than 1 in Intelligent Search APIs'
+id: 50Ufh8uqYt76Ddxrz0Id99
+status: PUBLISHED
+createdAt: 2023-11-11T00:26:08.800Z
+updatedAt: 2023-11-11T00:26:09.509Z
+publishedAt: 2023-11-11T00:26:09.509Z
+firstPublishedAt: 2023-11-11T00:26:09.509Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis
+locale: en
+kiStatus: Backlog
+internalReference: 934687
+---
+
+## Summary
+
+
+In the Intelligent Search APIs (GraphQL or REST), the `spotPrice` property from the object `items.sellers.commertialOffer` is wrong for items where the `unitMultiplier` is greater than `1`.
+
+The `spotPrice` should represent the cheapest payment method in its single installment option in order to show the "cash price", with a discount (if any), but in this case, it ends up returning the regular price for the item.
+
+It does not happen for items where the multiplier is lower than `1` (fracioned items).
+
+
+##
+
+## Simulation
+
+
+At the Intelligent Search's REST API or GraphQL, check the property for items in this specific scenario.
+
+
+##
+
+## Workaround
+
+
+The right value for `spotPrice` can be retrieved from the `Installments` array inside the same `commertialOffer` object.
+
+
+
+
diff --git a/docs/known-issues/en/wrong-translation-for-different-fields-under-the-same-original-value.md b/docs/known-issues/en/wrong-translation-for-different-fields-under-the-same-original-value.md
new file mode 100644
index 000000000..9676ed115
--- /dev/null
+++ b/docs/known-issues/en/wrong-translation-for-different-fields-under-the-same-original-value.md
@@ -0,0 +1,52 @@
+---
+title: 'Wrong translation for different fields under the same original value'
+id: 5amLWqGy7TPh7tk4KnLTmW
+status: PUBLISHED
+createdAt: 2024-02-16T00:05:00.562Z
+updatedAt: 2024-02-16T00:05:01.618Z
+publishedAt: 2024-02-16T00:05:01.618Z
+firstPublishedAt: 2024-02-16T00:05:01.618Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: wrong-translation-for-different-fields-under-the-same-original-value
+locale: en
+kiStatus: Backlog
+internalReference: 982848
+---
+
+## Summary
+
+
+Intelligent Search may use the wrong translation for a field whose value in the primary language is the same between different fields.
+
+
+##
+
+## Simulation
+
+
+Considering two fields (category and specification) from a product in a store with "nl-BE" as its default language and "fr-BE" as an additional language with the following values:
+
+- category
+  - nl-BE = medium
+  - fr-BE = moyens
+- specification
+  - nl-BE = medium
+  - fr-BE = midi
+
+In a mismatch, the "fr-BE" translation for the specification field may be wrongly indexed  as "moyens" instead of "midi"
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md b/docs/known-issues/en/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
new file mode 100644
index 000000000..94819910d
--- /dev/null
+++ b/docs/known-issues/en/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
@@ -0,0 +1,43 @@
+---
+title: 'Wrong value for priceDefinition in the chain order for a multilevel marketplace'
+id: 75qEjhgv1tTQNho0MArnJo
+status: PUBLISHED
+createdAt: 2023-11-27T13:50:18.505Z
+updatedAt: 2023-11-27T13:51:42.434Z
+publishedAt: 2023-11-27T13:51:42.434Z
+firstPublishedAt: 2023-11-27T13:51:42.434Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace
+locale: en
+kiStatus: Backlog
+internalReference: 663203
+---
+
+## Summary
+
+
+The "priceDefinition" property for orders in the "chain" level in a multilevel marketplace isn't following the "sellingPrice" as expected. Instead, it's following the "price" property.
+
+
+##
+
+## Simulation
+
+
+Create an order with a discount applied since the marketplace layer (level 1), in relation to the seller layer (chain, level 2), in a multilevel relationship. The fulfillment layer (level 3) will present the values correctly, but the "chain" won't.
+
+
+##
+
+## Workaround
+
+
+Avoid using the "priceDefinition" property in these type of orders and do the maths using the price, quantity, unitMultiplier, and priceTag properties – to avoid issues with the "sellingPrice", which isn't a precise value.
+
+
+
+
+
diff --git a/docs/known-issues/en/xml-currency-symbol-in-the-installment.md b/docs/known-issues/en/xml-currency-symbol-in-the-installment.md
index 79ce38e42..9d0e0baf0 100644
--- a/docs/known-issues/en/xml-currency-symbol-in-the-installment.md
+++ b/docs/known-issues/en/xml-currency-symbol-in-the-installment.md
@@ -1,10 +1,10 @@
 ---
 title: 'XML - Currency symbol in the "Installment"'
 id: 4s7hBA1MAUgeEC2Q4K8gKM
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-26T15:22:31.980Z
-updatedAt: 2022-12-22T20:48:49.927Z
-publishedAt: 2022-12-22T20:48:49.927Z
+updatedAt: 2024-02-02T20:08:19.240Z
+publishedAt: 
 firstPublishedAt: 2017-06-26T23:18:58.653Z
 contentType: knownIssue
 productTeam: Marketing & Merchandising
@@ -22,7 +22,8 @@ When you set a currency in an XML, it applies to all fields except the **Parcela
 
 The **Parcelamento** field always shows the currency "R$", regardless of whether the currency is set differently.
 
-![Parcelamento](//files.slack.com/files-pri/T02BCPD0X-F5WHSHM5E/image.png)
+![Parcelamento](https://github.com/vtexdocs/devportal/assets/77292838/7a6323e9-da76-4645-a13a-fcd1202efe52)
+
 
 ## Simulation
 
diff --git a/docs/known-issues/en/xml-global-category-field-showing-the-information-defined-on-category-global-level.md b/docs/known-issues/en/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
new file mode 100644
index 000000000..102e8cf94
--- /dev/null
+++ b/docs/known-issues/en/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
@@ -0,0 +1,41 @@
+---
+title: 'XML Global category field showing the information defined on Category Global Level.'
+id: 508Gdn8StafQKOa2Wyfr8u
+status: PUBLISHED
+createdAt: 2022-01-21T17:38:16.365Z
+updatedAt: 2024-02-16T20:30:04.149Z
+publishedAt: 2024-02-16T20:30:04.149Z
+firstPublishedAt: 2024-01-23T15:32:13.423Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: xml-global-category-field-showing-the-information-defined-on-category-global-level
+locale: en
+kiStatus: No Fix
+internalReference: 282231
+---
+
+## Summary
+
+
+On XML Files,  the field for Global Category is delivering the information from the Global Category defined on Category Level and not on Product Level (product level should be prioritize).
+
+
+##
+
+## Simulation
+
+
+- Use a product with a Global category defined on the Product, and a different Global Category defined on the Category Level;
+- Create a XML file and use the filed Global Category;
+- Check the product on the XML showing the Global Category defined on the Category.
+
+
+##
+
+## Workaround
+
+
+There is no workaround.
+
diff --git a/docs/known-issues/en/xml-installment-currency-does-not-apply.md b/docs/known-issues/en/xml-installment-currency-does-not-apply.md
new file mode 100644
index 000000000..0cc77cd16
--- /dev/null
+++ b/docs/known-issues/en/xml-installment-currency-does-not-apply.md
@@ -0,0 +1,47 @@
+---
+title: 'XML - Installment currency does not apply'
+id: 7kPbxbGnpqeqU8XCD576hZ
+status: PUBLISHED
+createdAt: 2024-02-02T19:16:59.053Z
+updatedAt: 2024-07-01T18:49:23.913Z
+publishedAt: 2024-07-01T18:49:23.913Z
+firstPublishedAt: 2024-02-02T19:16:59.992Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: xml-installment-currency-does-not-apply
+locale: en
+kiStatus: No Fix
+internalReference: 976295
+---
+
+## Summary
+
+
+When setting up a currency in an XML, it applies to all fields except the "Installment" field.
+
+The "Installment" field always displays the currency as "R$", regardless of the configured currency.
+
+
+##
+
+## Simulation
+
+
+
+1. Create/Update a XML with a currency different from "R$" and enable the Installment field.
+2. Check that all price fields on XML are correctly returning the currency, except the Installment.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/en/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md b/docs/known-issues/en/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
new file mode 100644
index 000000000..e4321de57
--- /dev/null
+++ b/docs/known-issues/en/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
@@ -0,0 +1,49 @@
+---
+title: 'XML <price> related tags do not load contents for unavailable items'
+id: 7u2WDGV9FJl4fXwfOhRx8N
+status: PUBLISHED
+createdAt: 2024-01-31T19:11:20.119Z
+updatedAt: 2024-01-31T19:11:20.846Z
+publishedAt: 2024-01-31T19:11:20.846Z
+firstPublishedAt: 2024-01-31T19:11:20.846Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: xml-price-related-tags-do-not-load-contents-for-unavailable-items
+locale: en
+kiStatus: Backlog
+internalReference: 974722
+---
+
+## Summary
+
+
+The XML integration loads any tag related to price, such as minPrice, maxPrice, currentPrice, are loaded as a null value tag (<![CDATA[]]>) when the item is not available and also set to show if unavailable.
+
+
+##
+
+## Simulation
+
+
+1 - Configure an unavailable SKU in your store to "show even if unavailable".
+2 - for a valid XML integration config https://myaccountname.myvtex.com/admin/Site/XmlForm.aspx, set up the "Availability" tag and any availability tag to show.
+3 - Use either a GET request or load the created XML URL in your browser.
+
+The result will be an unavailable item, still showing in the XML, but without any price tags:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/1CzUarsM3O05aG9z5otDZZ1Yg/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+There is no workaround. The only option to not integrate items without price is to turn off the "showIfNotAvailable" option.
+
+
+
+
+
diff --git a/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
new file mode 100644
index 000000000..2273b0695
--- /dev/null
+++ b/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
@@ -0,0 +1,47 @@
+---
+title: "XML's "Product Name" flag not working properly"
+id: 6YDbpRns3LCN02bVKM8aaf
+status: PUBLISHED
+createdAt: 2023-10-26T11:35:14.500Z
+updatedAt: 2023-10-26T11:35:15.285Z
+publishedAt: 2023-10-26T11:35:15.285Z
+firstPublishedAt: 2023-10-26T11:35:15.285Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: xmls-product-name-flag-not-working-properly
+locale: en
+kiStatus: Backlog
+internalReference: 925965
+---
+
+## Summary
+
+
+When creating an XML, we have two different options to set the product name, on the flags "Product name" and "Product Name + SKU Name". However, the flag "Product Name" is being disregarded, and the product name on the file follows the rule:
+- If the product has more than one SKU or the SKU name is equal to the product name = it will display only the Product Name
+- If the product has only one SKU and the SKU name is not equal to the product name = it will concatenate the Product and SKU Name
+
+
+##
+
+## Simulation
+
+
+
+1. Check if you have on the catalog products that match the description above
+2. Create an XML by selecting the flag "Product Name"
+3. See that for the products with only one SKU, the product name will be concatenated with the SKU name
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/en/xmls-returning-500-error.md b/docs/known-issues/en/xmls-returning-500-error.md
index 91e273597..5e1407bde 100644
--- a/docs/known-issues/en/xmls-returning-500-error.md
+++ b/docs/known-issues/en/xmls-returning-500-error.md
@@ -3,8 +3,8 @@ title: 'XMLs returning 500 error'
 id: 6L48cBRaKQmjAOnNza3aNA
 status: PUBLISHED
 createdAt: 2022-06-07T17:53:45.884Z
-updatedAt: 2022-11-25T22:10:40.212Z
-publishedAt: 2022-11-25T22:10:40.212Z
+updatedAt: 2024-05-23T18:54:18.843Z
+publishedAt: 2024-05-23T18:54:18.843Z
 firstPublishedAt: 2022-06-07T17:53:46.260Z
 contentType: knownIssue
 productTeam: Portal
@@ -23,6 +23,8 @@ Eventually, the XML can return a 500 error, it happens mainly on big XML files.
 
 
 
+##
+
 ## Simulation
 
 
@@ -30,6 +32,8 @@ Try loading a big XML file.
 
 
 
+##
+
 ## Workaround
 
 
@@ -37,3 +41,7 @@ Try loading a big XML file.
 - Try to reload the XML usually solves the issue;
 - Use more than one XML.
 
+
+
+
+
diff --git a/docs/known-issues/es/.md b/docs/known-issues/es/.md
index d446bbabb..64b90475e 100644
--- a/docs/known-issues/es/.md
+++ b/docs/known-issues/es/.md
@@ -35,8 +35,8 @@ rkaround
 
 
 
-## Workaround
 
+## Workaround
 
 
 
diff --git a/docs/known-issues/es/403-error-for-all-urls-containing-develop.md b/docs/known-issues/es/403-error-for-all-urls-containing-develop.md
new file mode 100644
index 000000000..5f0cd53b3
--- /dev/null
+++ b/docs/known-issues/es/403-error-for-all-urls-containing-develop.md
@@ -0,0 +1,50 @@
+---
+title: 'Error 403 para todas las URL que contengan develop-.'
+id: X6JDmLhD0StgHPGXJd9cZ
+status: PUBLISHED
+createdAt: 2024-02-01T13:46:53.024Z
+updatedAt: 2024-02-01T13:46:54.008Z
+publishedAt: 2024-02-01T13:46:54.008Z
+firstPublishedAt: 2024-02-01T13:46:54.008Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: error-403-para-todas-las-url-que-contengan-develop
+locale: es
+kiStatus: Backlog
+internalReference: 975182
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera que una URL pueda contener cualquier palabra sin generar un error, pero la palabra "**desarrollar "** seguida del carácter "**-**" genera un error 403 automático.
+Por ejemplo, un producto con el enlace de texto `how-to-develot-a-culture-of-custumer-centricity` mostrará un error 403, ya que contiene la cadena "develop-".
+
+
+##
+
+## Simulación
+
+
+
+1. Poner la cadena "desarrollar-" en un enlace de texto
+2. Cargar el producto
+3. Ver el error 403
+
+
+
+## Workaround
+
+
+No utilizar la cadena "develop-"
+
+
+
+
+
diff --git a/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
new file mode 100644
index 000000000..ad6335718
--- /dev/null
+++ b/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -0,0 +1,47 @@
+---
+title: 'Una SKU puede estar activa y tener el indicador "activar si es posible" desmarcado'
+id: 5uXQ65flkoEbYeLkNSw4ig
+status: PUBLISHED
+createdAt: 2023-11-07T11:01:20.612Z
+updatedAt: 2023-11-07T11:01:21.419Z
+publishedAt: 2023-11-07T11:01:21.419Z
+firstPublishedAt: 2023-11-07T11:01:21.419Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: una-sku-puede-estar-activa-y-tener-el-indicador-activar-si-es-posible-desmarcado
+locale: es
+kiStatus: Backlog
+internalReference: 931324
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera que una SKU activa tenga marcada la opción "activar si es posible", sin embargo, no siempre es así.
+Una SKU puede estar activa y tener el indicador "activar si es posible" sin marcar.
+
+
+
+## Simulación
+
+
+Abra el administrador de SKU
+Ver en el formulario que la SKU está activa y que la opción "activar si es posible" no está marcada.
+
+
+
+## Workaround
+
+
+Guarde la SKU directamente a través del admin
+
+
+
+
+
diff --git a/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md b/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
new file mode 100644
index 000000000..d22f83c38
--- /dev/null
+++ b/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
@@ -0,0 +1,48 @@
+---
+title: 'Un valor válido de especificación de producto puede ser devuelto en blanco en el catálogo admin'
+id: 46IZtoT2nSKE71g2Tj0m8y
+status: PUBLISHED
+createdAt: 2024-01-16T00:28:14.900Z
+updatedAt: 2024-01-16T00:28:15.482Z
+publishedAt: 2024-01-16T00:28:15.482Z
+firstPublishedAt: 2024-01-16T00:28:15.482Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: un-valor-valido-de-especificacion-de-producto-puede-ser-devuelto-en-blanco-en-el-catalogo-admin
+locale: es
+kiStatus: Backlog
+internalReference: 966499
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera que el administrador de especificaciones de producto siempre muestre los valores correctos para las especificaciones de un producto. Sin embargo, puede que no siempre sea así.
+El valor de la especificación puede ser devuelto en blanco en el admin como si no tuviera ningún valor asociado.
+Además del problema de visualización, si el usuario guarda el producto utilizando el administrador de productos, el valor de especificación en blanco sobrescribirá el valor original.
+
+
+
+## Simulación
+
+
+Abra un formulario de especificación de producto y compare el valor mostrado en el admin con el valor devuelto por la API.
+
+
+
+
+## Workaround
+
+
+Gestionar las especificaciones del producto a través de la API
+
+
+
+
+
diff --git a/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md b/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
new file mode 100644
index 000000000..eb0ae658d
--- /dev/null
+++ b/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
@@ -0,0 +1,48 @@
+---
+title: 'La aplicación AB Tester muestra información errónea sobre sesiones y conversión'
+id: 2Sgvlldl0kyDcWBVi4KMzg
+status: PUBLISHED
+createdAt: 2023-07-20T12:42:25.435Z
+updatedAt: 2024-07-01T18:49:08.433Z
+publishedAt: 2024-07-01T18:49:08.433Z
+firstPublishedAt: 2023-07-20T12:42:26.335Z
+contentType: knownIssue
+productTeam: Cloud Services
+author: 2mXZkbi0oi061KicTExNjo
+tag: Cloud Services
+slug: la-aplicacion-ab-tester-muestra-informacion-erronea-sobre-sesiones-y-conversion
+locale: es
+kiStatus: No Fix
+internalReference: 865727
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La aplicación AB Tester muestra información mal calculada para las sesiones y la conversión al ejecutar las pruebas, lo que provoca una interpretación no deseada de los resultados. La funcionalidad de división del espacio de trabajo sigue funcionando como se esperaba.
+
+
+##
+
+## Simulación
+
+
+
+- Cree una prueba A/B;
+- Deje que la prueba se ejecute durante algún tiempo;
+- Compruebe los valores de sesiones y conversiones; mostrará información mal calculada.
+
+
+
+## Workaround
+
+
+Utilice una herramienta de análisis externa para analizar los datos.
+
+
+
+
diff --git a/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md b/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
index bb7c395da..b48048103 100644
--- a/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
+++ b/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
@@ -1,16 +1,16 @@
 ---
-title: 'Activar servicio en la importación (SkuVincularValorServico.aspx) no funciona'
+title: 'Activar servicio al importar (SkuVincularValorServico.aspx) no funciona'
 id: 1gM3bYz0IX4ozLrIkWIicb
 status: PUBLISHED
 createdAt: 2022-02-25T14:56:50.052Z
-updatedAt: 2022-11-25T21:44:43.603Z
-publishedAt: 2022-11-25T21:44:43.603Z
+updatedAt: 2024-05-10T14:24:13.156Z
+publishedAt: 2024-05-10T14:24:13.156Z
 firstPublishedAt: 2022-02-25T14:56:50.569Z
 contentType: knownIssue
 productTeam: Catalog
 author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
-slug: activar-servicio-en-la-importacion-skuvincularvalorservicoaspx-no-funciona
+slug: activar-servicio-al-importar-skuvincularvalorservicoaspx-no-funciona
 locale: es
 kiStatus: Backlog
 internalReference: 339894
@@ -23,12 +23,36 @@ internalReference: 339894
 </div>
 
 
+Actualmente, en la usabilidad de importación de SkuVincularValorServico.aspx, cuando se intenta cambiar los servicios previamente salidos de inactivos a activos, los valores no se cambian. La interfaz de usuario indica que se han cambiado los valores, pero en realidad no ocurre nada.
+
+(Lo contrario no es cierto, el cambio de activo a inactivo funciona).
+
+
+##
 
 ## Simulación
 
 
+1) Ir a la UI https://account.myvtex.com/admin/Site/SkuVincularValorServico.aspx cambiando las filas de la hoja adjunta de 0 a 1 y viceversa:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ladK39V5My6gjGixeHuNTaV2b/?name=inline-1801216200.png)
+
+2) Comprueba los efectos finales en la SKU cuyos valores has cambiado:
+ ![](https://vtexhelp.zendesk.com/attachments/token/znYEzQhMevPcRVYKlBQYa73fF/?name=inline1216426643.png)
+
+Podrá establecerlos como inactivos, pero no como activos. La interfaz de usuario de importación indica que se han realizado cambios:
+ ![](https://vtexhelp.zendesk.com/attachments/token/6iKARGtVqTbKaL0vY9s7XPvt6/?name=inline2110004305.png)
+
+En realidad, no se ha modificado ningún valor en la base de datos de la cuenta en cuestión.
+
+
 
 ## Workaround
 
 
+Usando la UI para hacer cambios de inactivo -->> activo y/o nuestro servicio APIs:
+https://developers.vtex.com/vtex-developer-docs/reference/catalog-api-sku-service
+
+
+
 
diff --git a/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
index 5134c8199..b0a7ecf5b 100644
--- a/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
@@ -31,5 +31,5 @@ Crear un nuevo diccionario en el módulo CMS que no tenga ningún Host previamen
 
 Acceda al módulo CMS, haga clic en los botones lupa y limpiar en secuencia y se desbloqueará el botón agregar nuevo host.
 
-![PT - Criar dicionário não disponibiliza opção de "Add"](https://images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/d9118e018381d7733489a862eb7140ad/image__1_.png)
+![PT - Criar dicionário não disponibiliza opção de "Add"](//images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/d9118e018381d7733489a862eb7140ad/image__1_.png)
 
diff --git a/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md b/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md
index 928f9e416..dfc3e92ef 100644
--- a/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md
+++ b/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md
@@ -3,8 +3,8 @@ title: 'Añadir una nueva dirección en Dirección de factura devuelve resultado
 id: 43eiz4YORQv1u4yDahZdvC
 status: PUBLISHED
 createdAt: 2023-02-07T13:15:36.832Z
-updatedAt: 2023-02-07T13:15:52.825Z
-publishedAt: 2023-02-07T13:15:52.825Z
+updatedAt: 2024-07-01T18:48:46.296Z
+publishedAt: 2024-07-01T18:48:46.296Z
 firstPublishedAt: 2023-02-07T13:15:37.293Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: anadir-una-nueva-direccion-en-direccion-de-factura-devuelve-resultados-nulos-de-la-api
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 748668
 ---
 
diff --git a/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md b/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
new file mode 100644
index 000000000..92c0983be
--- /dev/null
+++ b/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
@@ -0,0 +1,56 @@
+---
+title: 'El formulario de dirección no se muestra cuando el comprador opta por insertar una nueva dirección.'
+id: 4HOP82OvC4smfjPFT8aXJA
+status: PUBLISHED
+createdAt: 2024-07-05T21:16:00.552Z
+updatedAt: 2024-07-05T21:16:01.340Z
+publishedAt: 2024-07-05T21:16:01.340Z
+firstPublishedAt: 2024-07-05T21:16:01.340Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-formulario-de-direccion-no-se-muestra-cuando-el-comprador-opta-por-insertar-una-nueva-direccion
+locale: es
+kiStatus: Backlog
+internalReference: 1061637
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+A veces, cuando un comprador identificado intenta añadir una nueva dirección en el paso de envío de la caja, se solicita un mensaje que requiere autenticación, pero el formulario de dirección no se muestra y no se puede rellenar.
+
+
+##
+
+## Simulación
+
+
+
+- Vaya a la caja, identifíquese como comprador con un perfil completo y proceda al paso de envío;
+- Elija la opción de entrega a una nueva dirección;
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/TFgWp6jleflU5LlPZ3rd4KcTQ/?name=image.png)
+
+
+- Introduzca el código postal y aparecerá un mensaje solicitando autenticación.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/iTNky5H9cDijZ00prjAwQv24h/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md b/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md
index edcaf8485..d25dc173f 100644
--- a/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md
+++ b/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md
@@ -3,8 +3,8 @@ title: 'El flujo de revisión de direcciones está eliminando la información es
 id: 416pFRk6KsWIfgPr8pzWii
 status: PUBLISHED
 createdAt: 2022-08-11T18:33:49.548Z
-updatedAt: 2022-11-25T21:50:56.733Z
-publishedAt: 2022-11-25T21:50:56.733Z
+updatedAt: 2024-02-16T20:23:20.195Z
+publishedAt: 2024-02-16T20:23:20.195Z
 firstPublishedAt: 2022-08-11T18:33:50.049Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-flujo-de-revision-de-direcciones-esta-eliminando-la-informacion-esencial-de-la-direccion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 618756
 ---
 
diff --git a/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
new file mode 100644
index 000000000..1ad069193
--- /dev/null
+++ b/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -0,0 +1,51 @@
+---
+title: 'Las direcciones se muestran en la caja cuando el comprador tiene permiso para "Añadir envío".'
+id: 2ssiTryGJ6kGoZWxWkGnFF
+status: PUBLISHED
+createdAt: 2024-05-21T22:03:55.172Z
+updatedAt: 2024-05-21T22:03:56.435Z
+publishedAt: 2024-05-21T22:03:56.435Z
+firstPublishedAt: 2024-05-21T22:03:56.435Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: las-direcciones-se-muestran-en-la-caja-cuando-el-comprador-tiene-permiso-para-anadir-envio
+locale: es
+kiStatus: Backlog
+internalReference: 1037067
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un rol tiene el permiso "Puede añadir envío" en la Configuración de Pago B2B y un comprador tiene direcciones registradas en el Sistema de Perfiles, al hacer clic en "Entregar en otra dirección" en el paso de envío y hacer clic en "Volver a la lista de direcciones" se muestran las direcciones del Sistema de Perfiles.
+
+
+##
+
+## Simulación
+
+
+
+- Añada a un rol el permiso "Puede añadir envío" en la Configuración de Pago B2B a través del administrador;
+- Añadir el rol a un comprador;
+- Accede a la tienda y monta un carrito;
+- Después de acceder a la caja, haga clic en "Cambiar opciones de envío"
+- Haga clic en "Entregar en otra dirección" en el paso de envío y haga clic en "Volver a la lista de direcciones",
+- Diferentes direcciones del centro de costes están en el carrito.
+
+
+
+## Workaround
+
+
+Habilite la opción Guardar datos de usuario para que no se añadan direcciones al Sistema de perfiles.
+
+
+
+
diff --git a/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md b/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
new file mode 100644
index 000000000..3ecaa8a32
--- /dev/null
+++ b/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
@@ -0,0 +1,48 @@
+---
+title: 'Las direcciones del sistema de perfiles se muestran cuando se suplanta la identidad mediante VTEX Telemarketing'
+id: 5fFacgD8grxKqJoOO2fwU7
+status: PUBLISHED
+createdAt: 2023-07-12T13:19:48.090Z
+updatedAt: 2023-08-31T19:38:04.369Z
+publishedAt: 2023-08-31T19:38:04.369Z
+firstPublishedAt: 2023-07-12T13:19:48.807Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: las-direcciones-del-sistema-de-perfiles-se-muestran-cuando-se-suplanta-la-identidad-mediante-vtex-telemarketing
+locale: es
+kiStatus: No Fix
+internalReference: 860375
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el comprador tiene direcciones registradas en el Sistema de Perfiles, y es suplantado utilizando VTEX Telemarketing, se muestran las direcciones del Sistema de Perfiles y Organizaciones
+
+
+##
+
+## Simulación
+
+
+
+- Suplantar a un comprador que tiene direcciones registradas en el Sistema de Perfiles;
+- Arme un carrito y vaya a Envíos;
+- Seleccione una dirección; el componente se actualizará y mostrará todas las direcciones del Sistema de Perfiles y Organizaciones.
+
+
+
+## Workaround
+
+
+
+- Utilice la función de suplantación de Organizaciones B2B.
+
+
+
diff --git a/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
new file mode 100644
index 000000000..1cf7e27d8
--- /dev/null
+++ b/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -0,0 +1,59 @@
+---
+title: 'La falta de coincidencia de AddressId provoca el error "dirección no válida para un artículo".'
+id: 5bSac85eHb9NmrOhcTjHNw
+status: PUBLISHED
+createdAt: 2024-03-01T19:28:52.074Z
+updatedAt: 2024-03-01T19:28:52.875Z
+publishedAt: 2024-03-01T19:28:52.875Z
+firstPublishedAt: 2024-03-01T19:28:52.875Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-falta-de-coincidencia-de-addressid-provoca-el-error-direccion-no-valida-para-un-articulo
+locale: es
+kiStatus: Backlog
+internalReference: 992503
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El adjunto del carrito `shippingData` soporta el campo `addressId` dentro de algunos objetos diferentes: `logisticsInfo`, `address`, y `selectedAddresses`.
+El campo `addressId` también se mantiene en las direcciones guardadas del usuario, dentro de la entidad AD de Master Data.
+
+Al realizar un pedido, la API de pago compara la dirección de envío seleccionada en el formulario de pedido con las direcciones disponibles en el perfil del usuario.
+Si se produce una coincidencia, el `addressId` de `address` y `selectedAddresses` del formulario de pedido se sustituye por el valor existente en su perfil.
+
+Sin embargo, en un punto posterior de las validaciones de la API, también se comparará este `addressId` con el del objeto `logisticsInfo`.
+Como el objeto `logisticsInfo` no ha sido sustituido por el proceso anterior, es posible que no coincidan, y esta validación posterior fallará.
+Esto desencadena un "**dirección inválida para un artículo**" / "endereço inválido para um ítem", impidiendo que se complete la compra.
+
+
+
+##
+
+## Simulación
+
+
+
+- Guardar dos direcciones diferentes dentro del perfil de un usuario, y tomar nota de sus valores `addressId`.
+- Cree una solicitud de pedido. Utiliza una de las direcciones creadas en el paso anterior, pero utiliza el `addressId` de la otra.
+- Envíe la solicitud. La respuesta contendrá el mensaje de error "dirección no válida para un artículo".
+
+
+
+## Workaround
+
+
+Cuando envíe la solicitud de realización de pedido con una dirección previamente guardada, asegúrese de que el valor utilizado para `addressId` coincide con los datos reales de la dirección.
+También puede omitir `addressId` en la solicitud.
+
+
+
+
+
diff --git a/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md b/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
index e125e4458..9cb40d278 100644
--- a/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
+++ b/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
@@ -3,8 +3,8 @@ title: 'Ajustar la consulta de envío cuando el pedido tiene más de un producto
 id: 5VsGJar6FBHbGi4OZpxvbk
 status: PUBLISHED
 createdAt: 2022-06-15T19:08:37.828Z
-updatedAt: 2022-11-25T21:56:35.720Z
-publishedAt: 2022-11-25T21:56:35.720Z
+updatedAt: 2024-02-16T20:25:35.893Z
+publishedAt: 2024-02-16T20:25:35.893Z
 firstPublishedAt: 2022-06-15T19:08:38.488Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: ajustar-la-consulta-de-envio-cuando-el-pedido-tiene-mas-de-un-producto-centauro
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 599380
 ---
 
diff --git a/docs/known-issues/es/admin-collection-brand-list-timeout.md b/docs/known-issues/es/admin-collection-brand-list-timeout.md
index 44acdcc87..8ad7a5884 100644
--- a/docs/known-issues/es/admin-collection-brand-list-timeout.md
+++ b/docs/known-issues/es/admin-collection-brand-list-timeout.md
@@ -3,8 +3,8 @@ title: 'Timeout de la lista de marcas de la colección en el Admin'
 id: 4de4lqAIhr9mU77EPAbvq1
 status: PUBLISHED
 createdAt: 2022-08-17T15:58:26.950Z
-updatedAt: 2022-11-25T21:43:44.331Z
-publishedAt: 2022-11-25T21:43:44.331Z
+updatedAt: 2024-07-01T18:48:37.335Z
+publishedAt: 2024-07-01T18:48:37.335Z
 firstPublishedAt: 2022-08-17T15:58:27.573Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: timeout-de-la-lista-de-marcas-de-la-coleccion-en-el-admin
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639905
 ---
 
diff --git a/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
new file mode 100644
index 000000000..ab462b3ce
--- /dev/null
+++ b/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -0,0 +1,52 @@
+---
+title: '[Admin] La búsqueda global no reconoce los "Elementos del menú de perfil".'
+id: 4AZiu9NXouL6b8z5EHJIWK
+status: PUBLISHED
+createdAt: 2024-01-22T17:09:55.423Z
+updatedAt: 2024-01-22T17:09:55.944Z
+publishedAt: 2024-01-22T17:09:55.944Z
+firstPublishedAt: 2024-01-22T17:09:55.944Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-la-busqueda-global-no-reconoce-los-elementos-del-menu-de-perfil
+locale: es
+kiStatus: Backlog
+internalReference: 969645
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La Búsqueda Global no reconoce los "Elementos del Menú de Perfil"
+
+
+##
+
+## Simulación
+
+
+En algunos casos, la búsqueda no devuelve ningún resultado.
+Por ejemplo: "Usuarios" "Autenticación"
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/QwUkKwavO6WM00STA32BVwyvn/?name=image.png)
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/weT1QdMEqTne83NxeJRN1ilFm/?name=image.png)
+
+
+
+## Workaround
+
+
+Utilice el menú lateral para acceder a estos módulos
+
+
+
+
+
diff --git a/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index 2cfb32c8c..aa8162916 100644
--- a/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -31,7 +31,7 @@ Esto se debía a que el número `1` se había configurado por defecto, incluso c
 
 Accede al **Admin VTEX > Home > Cómo mejorar > Catálogo**. Si la sección indica que hay `1` problema encontrado, al hacer clic en `Productos sin stock en los más vistos`, serás redirigido a la página del Catálogo.
 
-![Como melhorar ES](https://images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/6315fb589d4ac05737e3bd3cd76c0dd4/Como_melhorar_ES.png)
+![Como melhorar ES](//images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/6315fb589d4ac05737e3bd3cd76c0dd4/Como_melhorar_ES.png)
 
 
 ## Workaround
@@ -40,6 +40,6 @@ No es necesario que el usuario realice ninguna acción porque ya hemos soluciona
 
 `No encontramos ningún problema en su catálogo.`
 
-![Como melhorar fixed ES](https://images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/67494d3447838a49e35454aafa2f5e3a/Como_melhorar_fixed_ES.png)
+![Como melhorar fixed ES](//images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/67494d3447838a49e35454aafa2f5e3a/Como_melhorar_fixed_ES.png)
 
 
diff --git a/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md b/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
index 09713ad8e..31c58ba0d 100644
--- a/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
+++ b/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
@@ -3,8 +3,8 @@ title: 'El administrador muestra la extensión de la imagen como .jpg incluso cu
 id: 1nVCuVnNjT7e1E9Cy0Veer
 status: PUBLISHED
 createdAt: 2022-02-02T18:48:49.607Z
-updatedAt: 2022-11-25T21:48:51.993Z
-publishedAt: 2022-11-25T21:48:51.993Z
+updatedAt: 2024-02-16T20:26:18.176Z
+publishedAt: 2024-02-16T20:26:18.176Z
 firstPublishedAt: 2022-02-02T18:48:49.929Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-administrador-muestra-la-extension-de-la-imagen-como-jpg-incluso-cuando-la-imagen-es-png
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 516269
 ---
 
diff --git a/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md b/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
new file mode 100644
index 000000000..8f714bc0d
--- /dev/null
+++ b/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
@@ -0,0 +1,57 @@
+---
+title: 'Módulo [Admin] Datos Maestros, el buscador del admin los redirige a una URL errónea.'
+id: NPUIMi5uS5ngHZBeemIMe
+status: PUBLISHED
+createdAt: 2023-08-28T18:39:23.578Z
+updatedAt: 2023-09-06T15:03:32.872Z
+publishedAt: 2023-09-06T15:03:32.872Z
+firstPublishedAt: 2023-08-28T18:39:24.558Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: modulo-admin-datos-maestros-el-buscador-del-admin-los-redirige-a-una-url-erronea
+locale: es
+kiStatus: Fixed
+internalReference: 889045
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El módulo de Datos Maestros, el motor de búsqueda admin los redirige a la URL equivocada.
+
+
+##
+
+## Simulación
+
+
+
+Pasos:
+Admin > Buscar > Datos maestros >
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/DhvSEUDDmPjgGdIlWV4PJvh0A/?name=image.png)
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/9nUmLbZLPdCzBgvNziUi1WCvw/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+
+se puede acceder normalmente usando el menú lateral:
+Admin > Tienda > Datos maestros
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/59KwJCdK91ol1f4edT4hjNBHQ/?name=image.png)
+
+
+
+
+
diff --git a/docs/known-issues/es/admin-review-global-search.md b/docs/known-issues/es/admin-review-global-search.md
new file mode 100644
index 000000000..5f2712586
--- /dev/null
+++ b/docs/known-issues/es/admin-review-global-search.md
@@ -0,0 +1,50 @@
+---
+title: '[admin] revisar búsqueda global'
+id: 1r83M4ug7WVoF1gb22NMh0
+status: PUBLISHED
+createdAt: 2023-08-29T20:01:07.327Z
+updatedAt: 2023-08-29T20:01:08.251Z
+publishedAt: 2023-08-29T20:01:08.251Z
+firstPublishedAt: 2023-08-29T20:01:08.251Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-revisar-busqueda-global
+locale: es
+kiStatus: Backlog
+internalReference: 889993
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+la búsqueda global no encuentra información sobre "usuarios"
+
+
+##
+
+## Simulación
+
+
+Pasos:
+Admin > búsqueda global > Datos maestros > Usuario
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/bT7SSj1ApVwcvNCxCwtOB8yJj/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+es posible acceder directamente a través de la URL .com/admin/users
+
+
+
+
+
diff --git a/docs/known-issues/es/admin-timeout.md b/docs/known-issues/es/admin-timeout.md
new file mode 100644
index 000000000..e7d22d78c
--- /dev/null
+++ b/docs/known-issues/es/admin-timeout.md
@@ -0,0 +1,53 @@
+---
+title: 'Tiempo de espera de administración'
+id: 6Kp2viMZSnmGucJnciDNKx
+status: PUBLISHED
+createdAt: 2024-06-17T18:07:48.342Z
+updatedAt: 2024-06-17T18:07:49.170Z
+publishedAt: 2024-06-17T18:07:49.170Z
+firstPublishedAt: 2024-06-17T18:07:49.170Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: tiempo-de-espera-de-administracion
+locale: es
+kiStatus: Backlog
+internalReference: 1051070
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La aplicación de mensajes está recibiendo un error de tiempo de espera al azar y algunas páginas de administración pueden necesitar una actualización para funcionar correctamente.
+
+Esto puede estar relacionado con las consultas GraphQL. Normalmente verás errores en la ruta `/meta` o un tiempo de espera de la aplicación de mensajes relacionado con la consulta `translateWithDeps`.
+
+
+##
+
+## Simulación
+
+
+Intenta acceder a algunas páginas en el admin de una cuenta y aleatoriamente esta página puede recibir el error de abajo:
+ ![](https://vtexhelp.zendesk.com/attachments/token/zNzGxtaY5SszSHGFiKRMiCXda/?name=image.png)
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/KqbIgf2qqZIAdpYgXJcaiu5FJ/?name=image.png)
+
+Al actualizar la página todo debería volver a la normalidad
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md b/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md
index 306f8d3f4..925902ead 100644
--- a/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md
+++ b/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md
@@ -3,8 +3,8 @@ title: 'Dirección sin país que interrumpe la ordenCambios de formulario'
 id: 3LfFmUaetyqZij8MCBJtcY
 status: PUBLISHED
 createdAt: 2022-05-16T19:58:42.987Z
-updatedAt: 2022-11-25T21:52:11.051Z
-publishedAt: 2022-11-25T21:52:11.051Z
+updatedAt: 2024-02-16T20:23:23.949Z
+publishedAt: 2024-02-16T20:23:23.949Z
 firstPublishedAt: 2022-05-16T19:58:43.429Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: direccion-sin-pais-que-interrumpe-la-ordencambios-de-formulario
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 579814
 ---
 
diff --git a/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md b/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md
new file mode 100644
index 000000000..040a135bb
--- /dev/null
+++ b/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md
@@ -0,0 +1,55 @@
+---
+title: 'La doble solicitud de Adyen 3DS2 genera una denegación de autorización de pago'
+id: 3yR8LzaUjclJ22PkAymvoe
+status: PUBLISHED
+createdAt: 2023-09-20T13:09:29.771Z
+updatedAt: 2023-09-20T13:09:30.507Z
+publishedAt: 2023-09-20T13:09:30.507Z
+firstPublishedAt: 2023-09-20T13:09:30.507Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: la-doble-solicitud-de-adyen-3ds2-genera-una-denegacion-de-autorizacion-de-pago
+locale: es
+kiStatus: Backlog
+internalReference: 884154
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la solicitud 3DS2 de Adyen se envía dos veces, obtiene un error en la respuesta y el pago se deniega automáticamente.
+
+Respuesta de autorización:
+
+`{"status":409, "errorCode": "704", "message": "solicitud ya procesada o en curso", "errorType": "validation"}`
+
+Tras el mensaje:
+
+`Respuesta no esperada [].`
+
+Este es un problema cuando el pago está realmente autorizado por Adyen pero como no hay liquidación por nuestra parte no podemos enviar una solicitud de reembolso.
+
+
+##
+
+## Simulación
+
+
+No hemos sido capaces de reproducir este escenario o encontrar un patrón hasta el momento.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md b/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
new file mode 100644
index 000000000..00f96dd1b
--- /dev/null
+++ b/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
@@ -0,0 +1,48 @@
+---
+title: 'AdyenV1 no envía correctamente el paymentMethod.type para Amex cuando se utiliza Apple Pay.'
+id: UCCG0Lwe3U6dO7MHwFebO
+status: PUBLISHED
+createdAt: 2023-10-17T14:58:27.621Z
+updatedAt: 2023-10-17T14:58:28.348Z
+publishedAt: 2023-10-17T14:58:28.348Z
+firstPublishedAt: 2023-10-17T14:58:28.348Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: adyenv1-no-envia-correctamente-el-paymentmethodtype-para-amex-cuando-se-utiliza-apple-pay
+locale: es
+kiStatus: Backlog
+internalReference: 920563
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Aunque Apple Pay permite al usuario realizar un pedido utilizando una tarjeta Amex, nuestro conector heredado AdyenV1 no es compatible con esta marca.
+
+En los registros de interacción, se observa que el campo` paymentMethod.type` se rellena con "scheme", lo que provoca un error de Adyen.
+
+
+##
+
+## Simulación
+
+
+Intento de realizar un pedido utilizando Apple Pay con una tarjeta Amex. La transacción será denegada
+
+
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md b/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
index 29c761621..fb6c31457 100644
--- a/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
+++ b/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
@@ -3,8 +3,8 @@ title: 'La alerta para llenar la selección de entrega programada aparece sólo
 id: f668KUV24RqlpUvDvoIEm
 status: PUBLISHED
 createdAt: 2022-04-25T14:49:29.983Z
-updatedAt: 2022-11-25T21:51:08.681Z
-publishedAt: 2022-11-25T21:51:08.681Z
+updatedAt: 2024-02-16T20:26:02.010Z
+publishedAt: 2024-02-16T20:26:02.010Z
 firstPublishedAt: 2022-04-25T14:49:30.465Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-alerta-para-llenar-la-seleccion-de-entrega-programada-aparece-solo-una-vez
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 565982
 ---
 
diff --git a/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index 344624890..6d959d983 100644
--- a/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -3,7 +3,7 @@ title: 'ALT attribute not showing in <vtex.cmc:ProductImage zoom="on" />'
 id: 4P1Eys9Q2WFddrMLQVDvM9
 status: DRAFT
 createdAt: 2022-02-17T13:08:53.295Z
-updatedAt: 2022-03-18T15:38:31.951Z
+updatedAt: 2024-02-16T20:26:26.971Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 526563
 ---
 
diff --git a/docs/known-issues/es/amazon-category-implementation.md b/docs/known-issues/es/amazon-category-implementation.md
index 5f93e939b..9cb1931ee 100644
--- a/docs/known-issues/es/amazon-category-implementation.md
+++ b/docs/known-issues/es/amazon-category-implementation.md
@@ -3,8 +3,8 @@ title: 'Implementación de la categoría de Amazon'
 id: 5drX2V0avfk1X2llMyTlK1
 status: PUBLISHED
 createdAt: 2022-03-25T11:33:04.920Z
-updatedAt: 2022-12-02T18:00:24.056Z
-publishedAt: 2022-12-02T18:00:24.056Z
+updatedAt: 2024-02-16T20:24:37.027Z
+publishedAt: 2024-02-16T20:24:37.027Z
 firstPublishedAt: 2022-03-25T11:33:15.226Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: implementacion-de-la-categoria-de-amazon
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 549924
 ---
 
diff --git a/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md b/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
new file mode 100644
index 000000000..6a0893ec8
--- /dev/null
+++ b/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
@@ -0,0 +1,52 @@
+---
+title: '[Amazon] Código de error 13013 al enviar un producto al mercado de Amazon'
+id: 5bmPQ4Jzi8HvoDoTaDFv9b
+status: PUBLISHED
+createdAt: 2023-10-27T11:24:52.357Z
+updatedAt: 2023-12-18T17:35:20.302Z
+publishedAt: 2023-12-18T17:35:20.302Z
+firstPublishedAt: 2023-10-27T11:24:53.258Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: amazon-codigo-de-error-13013-al-enviar-un-producto-al-mercado-de-amazon
+locale: es
+kiStatus: Fixed
+internalReference: 926656
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema al tratar de exportar productos para el mercado de Amazon, hay algunos casos Amazon devuelve un error 13013. pero el error a veces no se registra en el menú Puente, y algunos productos se mantiene con el estado de éxito, pero cuando en realidad tienen el error de abajo
+
+
+    "code": "13013", "message": "Não há registo do código SKU correspondente a esta atualização em sua conta. Esto suele ocurrir cuando hay otros problemas con el código SKU.", "severity": "ERROR",
+
+
+
+##
+
+## Simulación
+
+
+
+Dentro del menú de productos puente, es posible que vea un error, mostrando el código de error 13013, o cualquier otro mensaje, pero al comprobar el Portal de Amazon que SKU podría no ser exportado a Amazon.
+
+
+
+## Workaround
+
+
+¿Existe alguna solución para este error? En caso afirmativo, descríbala aquí. En caso negativo, escriba "N/A" o "No hay solución disponible". No elimine esta sección si no hay solución, por favor.
+
+
+
+
+
diff --git a/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md b/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
new file mode 100644
index 000000000..39ee89d2e
--- /dev/null
+++ b/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
@@ -0,0 +1,54 @@
+---
+title: '[Amazon] Error en el flujo de actualización sku no se está registrando en el puente'
+id: 1oBkaT6GWZfhB4t2Qpn6c0
+status: PUBLISHED
+createdAt: 2024-02-27T19:40:49.825Z
+updatedAt: 2024-02-27T19:40:50.483Z
+publishedAt: 2024-02-27T19:40:50.483Z
+firstPublishedAt: 2024-02-27T19:40:50.483Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: amazon-error-en-el-flujo-de-actualizacion-sku-no-se-esta-registrando-en-el-puente
+locale: es
+kiStatus: Backlog
+internalReference: 990197
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Error en el flujo de actualización sku no se está registrando en el puente
+
+**Mercado:Amazon
+**Causa: Producto
+
+
+1. no sucede con todos los skus;
+
+
+##
+
+## Simulación
+
+
+Admin > Mercado > Productos > Amazon
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/l7i4mRjrhA0eo5BWd92YCS46m/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+Reprocesar SKU
+
+
+
+
diff --git a/docs/known-issues/es/amazon-global-category-not-working.md b/docs/known-issues/es/amazon-global-category-not-working.md
index e53d66d58..8d2702651 100644
--- a/docs/known-issues/es/amazon-global-category-not-working.md
+++ b/docs/known-issues/es/amazon-global-category-not-working.md
@@ -3,8 +3,8 @@ title: 'La categoría global de Amazon no funciona'
 id: 4xG37vNjH3XWVdb57w6zzV
 status: PUBLISHED
 createdAt: 2022-08-12T11:49:47.214Z
-updatedAt: 2022-12-02T18:32:25.769Z
-publishedAt: 2022-12-02T18:32:25.769Z
+updatedAt: 2024-02-16T20:25:10.435Z
+publishedAt: 2024-02-16T20:25:10.435Z
 firstPublishedAt: 2022-08-12T11:49:47.743Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: la-categoria-global-de-amazon-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 634199
 ---
 
diff --git a/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md b/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md
index f5b53ce88..bef1e9079 100644
--- a/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md
+++ b/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md
@@ -3,8 +3,8 @@ title: 'Atributo de integración de Amazon Número de itens'
 id: 75Afw210mMY9h6dbk3AV8V
 status: PUBLISHED
 createdAt: 2022-04-07T12:18:04.361Z
-updatedAt: 2022-11-25T21:56:13.168Z
-publishedAt: 2022-11-25T21:56:13.168Z
+updatedAt: 2024-02-16T20:25:56.485Z
+publishedAt: 2024-02-16T20:25:56.485Z
 firstPublishedAt: 2022-04-07T12:18:05.650Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: atributo-de-integracion-de-amazon-numero-de-itens
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 557788
 ---
 
diff --git a/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md b/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md
index 095eb0853..560e74009 100644
--- a/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md
+++ b/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md
@@ -3,8 +3,8 @@ title: 'Integración de Amazon reservas de stock para KITS'
 id: 6ZEvHuGCOEcuQTya1oDOyu
 status: PUBLISHED
 createdAt: 2023-05-22T14:28:54.846Z
-updatedAt: 2023-05-22T14:28:55.337Z
-publishedAt: 2023-05-22T14:28:55.337Z
+updatedAt: 2023-09-27T14:37:26.343Z
+publishedAt: 2023-09-27T14:37:26.343Z
 firstPublishedAt: 2023-05-22T14:28:55.337Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: integracion-de-amazon-reservas-de-stock-para-kits
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 829583
 ---
 
diff --git a/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md b/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md
index 63242acfb..9c7cc1c47 100644
--- a/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md
+++ b/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md
@@ -3,8 +3,8 @@ title: '[Amazon][casacaso] - Erros de rastreamento'
 id: 6a8QqrvjiQBBI2EM22581P
 status: PUBLISHED
 createdAt: 2022-03-10T17:59:48.309Z
-updatedAt: 2022-11-25T21:57:04.066Z
-publishedAt: 2022-11-25T21:57:04.066Z
+updatedAt: 2023-08-16T12:26:16.960Z
+publishedAt: 2023-08-16T12:26:16.960Z
 firstPublishedAt: 2022-03-10T17:59:48.640Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazoncasacaso-erros-de-rastreamento
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 360564
 ---
 
@@ -23,17 +23,18 @@ internalReference: 360564
 </div>
 
 
-En algunos casos, el flujo de trabajo de seguimiento de Amazon no funciona.
+Estamos teniendo problemas en algunos casos en los que el flujo de trabajo de seguimiento para Amazon no está funcionando.
 
 
+##
 
 ## Simulación
 
 
 
-El siguiente mensaje se muestra en la interfaz de usuario del puente para el seguimiento del menú:
+El siguiente mensaje se muestra en la interfaz de bridge para el menú de seguimiento:
 
-Las cantidades proporcionadas para el ID del pedido (XXXXXXXXXXXX) eran superiores a las cantidades que podían satisfacerse. Revisar la cantidad del informe de pedidos y tener en cuenta los productos que se han cancelado o que ya se han cerrado
+Las cantidades proporcionadas para el ID de pedido (XXXXXXXXXXXX) eran superiores a las cantidades que se podían cumplir. Revise la cantidad del informe del pedido y tenga en cuenta los productos que se han cancelado o que ya se han cerrado.
 
 
 
@@ -42,3 +43,7 @@ Las cantidades proporcionadas para el ID del pedido (XXXXXXXXXXXX) eran superior
 
 N/A
 
+
+
+
+
diff --git a/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md b/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
index b20a961e9..6db522e89 100644
--- a/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
+++ b/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
@@ -3,8 +3,8 @@ title: 'La API Shipping Estimate devuelve información errónea cuando la SC es
 id: 6bxlw1nQ27JGbiOmNbgyn2
 status: PUBLISHED
 createdAt: 2022-04-01T23:33:47.015Z
-updatedAt: 2022-11-25T21:59:23.170Z
-publishedAt: 2022-11-25T21:59:23.170Z
+updatedAt: 2024-07-01T18:48:14.728Z
+publishedAt: 2024-07-01T18:48:14.728Z
 firstPublishedAt: 2022-05-18T18:27:53.441Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: la-api-shipping-estimate-devuelve-informacion-erronea-cuando-la-sc-es-nula
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 554948
 ---
 
diff --git a/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md b/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
index b7c8d5db0..f07720a3c 100644
--- a/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
+++ b/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
@@ -3,8 +3,8 @@ title: 'La API para listar los puntos de recogida no devuelve el campo additiona
 id: 5YY5srSA2ZRiOSZiMY9UF9
 status: PUBLISHED
 createdAt: 2022-09-02T12:09:09.980Z
-updatedAt: 2022-11-25T21:50:17.504Z
-publishedAt: 2022-11-25T21:50:17.504Z
+updatedAt: 2024-02-16T20:24:50.684Z
+publishedAt: 2024-02-16T20:24:50.684Z
 firstPublishedAt: 2022-09-02T12:09:10.777Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-api-para-listar-los-puntos-de-recogida-no-devuelve-el-campo-additionalinfo
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 650714
 ---
 
diff --git a/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md b/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md
new file mode 100644
index 000000000..300ed6585
--- /dev/null
+++ b/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md
@@ -0,0 +1,59 @@
+---
+title: 'La configuración de la aplicación no se borra al eliminarla.'
+id: 7KXfKLgbc3UDeDSsCgT0Sk
+status: PUBLISHED
+createdAt: 2024-07-15T22:29:24.058Z
+updatedAt: 2024-07-15T22:29:24.867Z
+publishedAt: 2024-07-15T22:29:24.867Z
+firstPublishedAt: 2024-07-15T22:29:24.867Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: la-configuracion-de-la-aplicacion-no-se-borra-al-eliminarla
+locale: es
+kiStatus: Backlog
+internalReference: 1065954
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Vaya a la "App Store";
+- Selecciona la app;
+- Haz clic en "Obtener app";
+- Haz clic en "Instalar app";
+- Sigue las instrucciones para instalar la aplicación;
+- Rellene los ajustes (si procede) y "Guardar";
+- Haga clic en "Eliminar". Aparecerá el siguiente mensaje:
+ ![](https://vtexhelp.zendesk.com/attachments/token/kM5EhsfVaHLlISckht8rRYumU/?name=image.png)
+
+> ¿Desea eliminar la aplicación X?
+>
+> ¿Está seguro de que desea eliminar esta aplicación? Se perderán todas las configuraciones guardadas en todos los espacios de trabajo y la aplicación se eliminará de la lista de aplicaciones.
+
+- Haz clic de nuevo en "Eliminar" para confirmar. La aplicación se eliminará;
+- Vuelve a los primeros pasos e instala la misma aplicación;
+- Compruebe su configuración, y vea que la información no ha sido borrada como se esperaba (la información previamente rellenada aparecerá allí).
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible. Pero puedes poner información ficticia.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md b/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
new file mode 100644
index 000000000..26eb093a4
--- /dev/null
+++ b/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
@@ -0,0 +1,54 @@
+---
+title: 'Aplicar el descuento a los artículos más caros - UI no ahorrar datos.'
+id: 6VQuVOAtzbA6OyjDEi2bHh
+status: PUBLISHED
+createdAt: 2024-04-03T17:29:36.171Z
+updatedAt: 2024-04-03T17:29:37.024Z
+publishedAt: 2024-04-03T17:29:37.024Z
+firstPublishedAt: 2024-04-03T17:29:37.024Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: aplicar-el-descuento-a-los-articulos-mas-caros-ui-no-ahorrar-datos
+locale: es
+kiStatus: Backlog
+internalReference: 1011071
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar la interfaz de usuario de promociones, al intentar guardar manualmente la opción "Aplicar a los artículos más caros" no funcionará y el selector permanecerá en la opción de tipo más barato.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ofDGJuHHbNRwvbYDMOSSCznvB/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+1 - Ir a la interfaz de usuario de promociones: https://account_name.myvtex.com/admin/promotions
+
+2 - En la interfaz de promociones, seleccione la opción "Aplicar el descuento a los artículos más caros".
+
+3 - Guarde la promoción
+
+4 - Acceda de nuevo a ella, en su lugar se seleccionará la casilla de aplicar a la opción más barata.
+
+
+
+## Workaround
+
+
+Utilice la API de guardar promociones en su lugar https://developers.vtex.com/docs/api-reference/promotions-and-taxes-api#post-/api/rnb/pvt/calculatorconfiguration
+
+
+
+
+
diff --git a/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md b/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md
index 8a9ceb8de..50ee62f17 100644
--- a/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md
+++ b/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md
@@ -3,8 +3,8 @@ title: 'La hoja de cálculo de Skus aprobados no muestra el precio'
 id: 3nWwzGYX1Ys0rKkoSZZpdz
 status: PUBLISHED
 createdAt: 2022-03-29T19:22:12.977Z
-updatedAt: 2022-11-25T22:00:49.862Z
-publishedAt: 2022-11-25T22:00:49.862Z
+updatedAt: 2024-02-16T20:23:36.636Z
+publishedAt: 2024-02-16T20:23:36.636Z
 firstPublishedAt: 2022-03-29T19:22:13.346Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: la-hoja-de-calculo-de-skus-aprobados-no-muestra-el-precio
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 552155
 ---
 
diff --git a/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
new file mode 100644
index 000000000..3e3333649
--- /dev/null
+++ b/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -0,0 +1,70 @@
+---
+title: 'La API de Attachents no permite "domainValues" nulos (y debería)'
+id: 7KMb6nh0ulcWdEfz7USbPg
+status: PUBLISHED
+createdAt: 2023-09-11T19:02:51.514Z
+updatedAt: 2023-09-11T19:02:52.164Z
+publishedAt: 2023-09-11T19:02:52.164Z
+firstPublishedAt: 2023-09-11T19:02:52.164Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-api-de-attachents-no-permite-domainvalues-nulos-y-deberia
+locale: es
+kiStatus: Backlog
+internalReference: 897480
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las solicitudes de actualización para la API /api/catalog/pvt/attachment/ no están permitiendo actualizaciones para el campo Valor del dominio como valor nulo.
+
+Este campo es nullable, por lo que esta respuesta de la API está respondiendo incorrectamente con:
+
+`{`
+` "Mensaje": "DomainValues in Domain at position 1 can not be null or empty value"`
+`}`
+
+
+##
+
+## Simulación
+
+
+1 - Crear un archivo adjunto mediante la interfaz de usuario o la API: https://help.vtex.com/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU
+
+2 - intente actualizarlo enviando el campo domainValue como null, por ejemplo:
+
+`{`
+` "Id": 123,`
+` "Nombre": "payload con dominio nulo",`
+` "IsRequired": true,`
+` "IsActive": true,`
+` "Domains": [`
+` {`
+` "FieldName": "Basic test",`
+` "MaxCaracters": "354534",`
+` "DomainValues": ""`
+` }`
+` ]`
+`}`
+
+3 - se le mostrará un tipo de respuesta "Solicitud incorrecta", cuando en realidad debería aceptar valores nulos para este campo.
+
+
+
+## Workaround
+
+
+Actualice los valores permitidos manualmente, vía UI o créelos ya nulos (el método POST funciona, el PUT no).
+
+
+
+
+
diff --git a/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md b/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
index 4d5438c75..662bf6686 100644
--- a/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
+++ b/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
@@ -3,8 +3,8 @@ title: 'La validación de la API de actualización y creación de archivos adjun
 id: 1NAwwi7C65xM2G61uaTLrB
 status: PUBLISHED
 createdAt: 2023-02-09T16:10:03.814Z
-updatedAt: 2023-02-09T16:10:04.449Z
-publishedAt: 2023-02-09T16:10:04.449Z
+updatedAt: 2024-07-01T18:48:48.654Z
+publishedAt: 2024-07-01T18:48:48.654Z
 firstPublishedAt: 2023-02-09T16:10:04.449Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-validacion-de-la-api-de-actualizacion-y-creacion-de-archivos-adjuntos-en-el-campo-domainvalues-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 751091
 ---
 
diff --git a/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md b/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
new file mode 100644
index 000000000..0a48a927a
--- /dev/null
+++ b/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
@@ -0,0 +1,65 @@
+---
+title: 'Validación de adjuntos sólo en el mercado al añadir un artículo de un vendedor con adjunto.'
+id: 638N4urP08NY7v8jdH7U5N
+status: PUBLISHED
+createdAt: 2023-12-22T18:18:59.194Z
+updatedAt: 2023-12-22T18:18:59.909Z
+publishedAt: 2023-12-22T18:18:59.909Z
+firstPublishedAt: 2023-12-22T18:18:59.909Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: validacion-de-adjuntos-solo-en-el-mercado-al-anadir-un-articulo-de-un-vendedor-con-adjunto
+locale: es
+kiStatus: Backlog
+internalReference: 957343
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Añadir un artículo de un vendedor con un archivo adjunto en la misma solicitud de API, la validación de archivos adjuntos se produce sólo en el mercado.
+
+**Escenario 1:**
+Si el marketplace tiene el mismo nombre de adjunto y las claves difieren de las del vendedor, se mostrará el mensaje de error "Item attachment has an invalid value for key", y el artículo no se añadirá al carrito.
+
+**Escenario 2:**
+Si el marketplace no tiene el mismo adjunto, se mostrará el mensaje de error "El nombre del adjunto no es válido", y el artículo no se añadirá al carrito.
+
+Este comportamiento ocurre en ambas APIs para añadir artículos: Añadir artículos al carrito y Manejar artículos del carrito.
+
+
+##
+
+## Simulación
+
+
+
+- Configurar el mismo adjunto en el marketplace y vendedor con diferentes claves de campo;
+- Asociar con un artículo;
+- Añadir el artículo a través de Añadir artículos del carrito o Manejar artículos del carrito, con archivos adjuntos.
+
+
+- Configurar un anexo en el vendedor y asociarlo a un artículo;
+- Añadir el artículo a través de Añadir artículos del carro o Gestionar artículos del carro, con archivos adjuntos.
+
+
+
+## Workaround
+
+
+
+- Añada el artículo primero y el adjunto después en solicitudes diferentes. Para enviar el adjunto, puede
+  - enviar los archivos adjuntos a través de Manejar artículos del carrito;
+  - enviar los archivos adjuntos a través de Añadir un archivo adjunto a un artículo, por ejemplo:
+
+    curl --location 'https://{accountName}.{environment}.com.br/api/checkout/pub/orderForm/{orderFormId}/items/{itemIndex}/attachments/{attachmentName}' \--header 'Content-Type: application/json' \--data '{"content": { "key": "value" }, "noSplitItem": true}'
+
+
+
+
diff --git a/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md b/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
new file mode 100644
index 000000000..fa86a36cf
--- /dev/null
+++ b/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
@@ -0,0 +1,49 @@
+---
+title: 'Los valores permitidos de los anexos no se actualizan cuando se añaden a los artículos.'
+id: 1JjFJJGsUaLWvthJ7kxSBw
+status: PUBLISHED
+createdAt: 2023-10-17T20:16:40.973Z
+updatedAt: 2023-10-17T20:16:41.571Z
+publishedAt: 2023-10-17T20:16:41.571Z
+firstPublishedAt: 2023-10-17T20:16:41.571Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-valores-permitidos-de-los-anexos-no-se-actualizan-cuando-se-anaden-a-los-articulos
+locale: es
+kiStatus: Backlog
+internalReference: 920970
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los valores permitidos del adjunto no se actualizan si se añadió a un artículo antes de cambiar sus valores en el admin. Esto provocará un error en el carrito con el mensaje "Imposible comunicarse con el vendedor".
+
+
+##
+
+## Simulación
+
+
+
+- Crear un archivo adjunto con los valores permitidos;
+- Añadir un elemento con el adjunto;
+- Cambiar los valores permitidos del adjunto;
+- Actualizar el carrito.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md b/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md
new file mode 100644
index 000000000..80cd5f1b9
--- /dev/null
+++ b/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md
@@ -0,0 +1,51 @@
+---
+title: 'El atributo meli_shipping_mode no se actualiza en la integración MELI'
+id: 7DMsCqv2AsOEsL3LGLhxWq
+status: PUBLISHED
+createdAt: 2023-08-03T10:19:05.524Z
+updatedAt: 2024-06-10T13:38:07.225Z
+publishedAt: 2024-06-10T13:38:07.225Z
+firstPublishedAt: 2023-08-03T10:19:06.574Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: el-atributo-melishippingmode-no-se-actualiza-en-la-integracion-meli
+locale: es
+kiStatus: Fixed
+internalReference: 873993
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema con el atributo del producto llamado "meli_shipping_mode" que no se está actualizando en la integración MELI
+
+
+##
+
+## Simulación
+
+
+
+Dentro de la especificación del producto, el vendedor puede utilizar el atributo "meli_shipping_mode" y establecer ME1 o ME2 para definir la estrategia de envío en MELI.
+
+Pero actualmente sólo podemos enviar este valor al crear el SKU en MELI, y no estamos actualizando con el valor correcto.
+
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
new file mode 100644
index 000000000..577999bee
--- /dev/null
+++ b/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
@@ -0,0 +1,49 @@
+---
+title: 'Registros de precios de auditoría que muestran información "desconocida".'
+id: 7b8UDsiBo7VOHCN3pgcfd0
+status: PUBLISHED
+createdAt: 2023-07-05T18:51:22.120Z
+updatedAt: 2023-07-05T18:51:22.566Z
+publishedAt: 2023-07-05T18:51:22.566Z
+firstPublishedAt: 2023-07-05T18:51:22.566Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: registros-de-precios-de-auditoria-que-muestran-informacion-desconocida
+locale: es
+kiStatus: Backlog
+internalReference: 856420
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas acciones de usuario relativas a modificaciones de precios se están registrando en el módulo de auditoría como "desconocidas".
+
+
+##
+
+## Simulación
+
+
+
+1. El comerciante realiza algunas modificaciones en el módulo de precios.
+2. Algunas acciones se registrarán correctamente en la auditoría.
+3. 3. Compruebe que algunas acciones se registrarán con los campos "Acción" y "Detalles del evento" configurados como "desconocidos".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md b/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
new file mode 100644
index 000000000..96db2e179
--- /dev/null
+++ b/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
@@ -0,0 +1,46 @@
+---
+title: 'El estado de autorización se bloquea para transacciones asíncronas con 2 o más pagos cuando se cancela el primero.'
+id: 7kEU8P6lkSQYZWzgaC16nY
+status: PUBLISHED
+createdAt: 2023-11-02T15:49:18.723Z
+updatedAt: 2023-11-02T19:37:18.326Z
+publishedAt: 2023-11-02T19:37:18.326Z
+firstPublishedAt: 2023-11-02T15:49:19.524Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-estado-de-autorizacion-se-bloquea-para-transacciones-asincronas-con-2-o-mas-pagos-cuando-se-cancela-el-primero
+locale: es
+kiStatus: Backlog
+internalReference: 929517
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una transacción tiene múltiples pagos y se vuelve asíncrona debido al modo Sherlock o Defensa, y si el primer intento de autorización de pago falla, puede resultar en que los otros pagos se queden atascados en un estado "Autorizado". Esto se debe a que se cancela toda la transacción, pero nuestro trabajador no lo reconoce y procede con un intento de autorización para el segundo pago. En consecuencia, el segundo pago no puede ser cancelado, ya que la transacción ya ha sido cancelada, y no permite una solicitud de cancelación.
+
+
+##
+
+## Simulación
+
+
+Cree una transacción con dos pagos, en la que esté activado el Modo Defensa o cualquier otra característica que haga que la transacción sea asíncrona. A continuación, utilice un conector de proveedor personalizado para rechazar el primer intento de autorización de pago mientras aprueba el otro.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/auto-approve-api-accepts-any-values.md b/docs/known-issues/es/auto-approve-api-accepts-any-values.md
index 1a810aebe..e7327f67c 100644
--- a/docs/known-issues/es/auto-approve-api-accepts-any-values.md
+++ b/docs/known-issues/es/auto-approve-api-accepts-any-values.md
@@ -3,8 +3,8 @@ title: 'La API de aprobación automática acepta cualquier valor'
 id: kLl4mtwKPPqW6jk5hZMWs
 status: PUBLISHED
 createdAt: 2022-12-12T14:18:51.059Z
-updatedAt: 2022-12-12T14:18:51.733Z
-publishedAt: 2022-12-12T14:18:51.733Z
+updatedAt: 2024-02-16T20:27:19.981Z
+publishedAt: 2024-02-16T20:27:19.981Z
 firstPublishedAt: 2022-12-12T14:18:51.733Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-api-de-aprobacion-automatica-acepta-cualquier-valor
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 713704
 ---
 
diff --git a/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md b/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md
index 9b2af53df..e65da5c0a 100644
--- a/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md
+++ b/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md
@@ -3,8 +3,8 @@ title: 'Autocompletar trayendo productos de sugerencia mostrados con retraso'
 id: 26ydVkjgikjeBq8Jxuh0Vr
 status: PUBLISHED
 createdAt: 2022-07-12T12:21:25.537Z
-updatedAt: 2023-02-08T13:50:52.209Z
-publishedAt: 2023-02-08T13:50:52.209Z
+updatedAt: 2024-07-01T18:48:28.298Z
+publishedAt: 2024-07-01T18:48:28.298Z
 firstPublishedAt: 2022-07-12T12:21:26.029Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: autocompletar-trayendo-productos-de-sugerencia-mostrados-con-retraso
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 615616
 ---
 
diff --git a/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md b/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md
index 9f873fffb..fb1eaf7bc 100644
--- a/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md
+++ b/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md
@@ -1,18 +1,18 @@
 ---
-title: 'El autocompletado no responde a los arranques en frío'
+title: 'Autocompletar no responde al arranque en frío'
 id: 2lgYjT8lmFIvLV3vKOXKmt
 status: PUBLISHED
 createdAt: 2022-02-23T22:01:05.141Z
-updatedAt: 2022-11-25T21:58:01.186Z
-publishedAt: 2022-11-25T21:58:01.186Z
+updatedAt: 2024-03-14T18:48:50.406Z
+publishedAt: 2024-03-14T18:48:50.406Z
 firstPublishedAt: 2022-02-23T22:01:05.666Z
 contentType: knownIssue
 productTeam: Intelligent Search
 author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
-slug: el-autocompletado-no-responde-a-los-arranques-en-frio
+slug: autocompletar-no-responde-al-arranque-en-frio
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 418573
 ---
 
@@ -23,10 +23,11 @@ internalReference: 418573
 </div>
 
 
-La función de búsqueda inteligente conocida como **autocompletar** no funciona en algunas tiendas nuevas incluso después de ejecutar un proceso interno llamado _inicio en frío_.
+La función de búsqueda inteligente conocida como **autocompletar** no funciona en algunas tiendas nuevas incluso después de ejecutar un proceso interno llamado _cold start_.
 
 
 
+##
 
 ## Simulación
 
@@ -38,5 +39,8 @@ N/A.
 ## Workaround
 
 
-Actualmente no hay una solución para este problema conocido, pero la función de autocompletar funciona correctamente y seguirá aprendiendo en función de la experiencia de los usuarios, lo que significa que un tiempo después de la puesta en marcha funcionará bien para las nuevas cuentas.
+Actualmente no existe una solución para este problema conocido, pero la función de autocompletar funciona correctamente y seguirá aprendiendo en función de la experiencia de los usuarios, lo que significa que un tiempo después de la puesta en marcha funcionará correctamente para las cuentas nuevas.
+
+
+
 
diff --git a/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
new file mode 100644
index 000000000..6ca0c1abd
--- /dev/null
+++ b/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -0,0 +1,53 @@
+---
+title: 'La API de sugerencia de autocompletar elimina el punto "." del nombre del producto'
+id: 55185IvERIwGQ3kH6H510O
+status: PUBLISHED
+createdAt: 2024-04-10T13:58:51.138Z
+updatedAt: 2024-04-10T13:58:52.084Z
+publishedAt: 2024-04-10T13:58:52.084Z
+firstPublishedAt: 2024-04-10T13:58:52.084Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: la-api-de-sugerencia-de-autocompletar-elimina-el-punto-del-nombre-del-producto
+locale: es
+kiStatus: Backlog
+internalReference: 1014701
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Este problema se produce cuando se busca un término y la sugerencia de autocompletar devuelve el nombre del producto sin el carácter de punto ".", aunque exista en el nombre del producto, lo que da lugar a resultados de búsqueda incorrectos.
+
+
+##
+
+## Simulación
+
+
+
+1. GET` https://..com.br/api/io/_v/api/intelligent-search/autocomplete_suggestions?query=`.
+2. Observa las sugerencias de autocompletar que te proporciona el sistema.
+3. Observe que falta el carácter punto en el nombre del producto seleccionado.
+
+Por ejemplo, si se busca el término "auriculares" en la API de sugerencias de autocompletar, los resultados de la sugerencia, si contienen un punto en el nombre, se mostrarán como "Auriculares Bluetooth 5 0" en lugar de tener el punto en el número "5.0". El formato correcto debería ser "Auriculares Bluetooth 5.0".
+
+Cuando se utilice esta sugerencia en la API product_search, no devolverá resultados.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index 8cf4552f7..75cd2e1c1 100644
--- a/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumario
 
-El Campo Automático (campo calculado) funciona correctamente cuando "Recalcular este campo:" está establecido para "solo cuando ingrese el registro", pero deja de funcionar cuando está programado para recalcular "en la primera hora..." y susvariantes. ![inline1511102536](https://images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
+El Campo Automático (campo calculado) funciona correctamente cuando "Recalcular este campo:" está establecido para "solo cuando ingrese el registro", pero deja de funcionar cuando está programado para recalcular "en la primera hora..." y susvariantes. ![inline1511102536](//images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md b/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md
new file mode 100644
index 000000000..f6b8d3bb8
--- /dev/null
+++ b/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md
@@ -0,0 +1,60 @@
+---
+title: 'Liquidación automática de pagos configurada incorrectamente'
+id: 6KOQwBKNgOPNL7TM80Bqjf
+status: PUBLISHED
+createdAt: 2024-06-19T22:12:10.705Z
+updatedAt: 2024-06-19T22:12:11.484Z
+publishedAt: 2024-06-19T22:12:11.484Z
+firstPublishedAt: 2024-06-19T22:12:11.484Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: liquidacion-automatica-de-pagos-configurada-incorrectamente
+locale: es
+kiStatus: Backlog
+internalReference: 1053010
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El problema es que la pasarela ignoraba el valor `delayToAutoSettleAfterAntifraud`.
+
+Estos campos son obligatorios en la respuesta de autorización, pero la pasarela acepta su ausencia. Nuestra documentación relacionada con esto.
+
+        "delayToAutoSettle": 1200, "delayToAutoSettleAfterAntifraud": 1200
+
+En el escenario perfecto, la pasarela no debería aceptar la respuesta sin ellos.
+
+Cuando el campo `delayToAutoSettleAfterAntifraud` no está en la carga útil de la respuesta de autorización. La pasarela no puede definir el valor correcto, por lo que el valor por defecto de la liquidación automática del pago será de 4 días (por defecto).
+
+
+##
+
+## Simulación
+
+
+
+1. Cree un pago.
+2. Configurar el conector para que responda sin que este requerido el campo delayToAutoSettle, pero enviando el delayToAutoSettleAfterAntifraud.
+3. Comprueba la respuesta de Autorización, y sólo tendrá el valor al que respondió el conector
+4. Compruebe la tarjeta morada para ver qué valor ha establecido. La liquidación automática del pago se programará para cuatro días después de la aprobación del pago.
+
+
+
+
+## Workaround
+
+
+
+Establecer el **delayAutoSettle** como el mismo valor que **delayAutoSettleAfterAntifraud.**
+
+
+
+
+
diff --git a/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md b/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
new file mode 100644
index 000000000..f350c1194
--- /dev/null
+++ b/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
@@ -0,0 +1,46 @@
+---
+title: 'La traducción automática de URL no se produce debido a caracteres especiales'
+id: 7G0WKfFFZxZ7mMEoasePld
+status: PUBLISHED
+createdAt: 2024-07-09T19:45:44.410Z
+updatedAt: 2024-07-10T12:45:50.061Z
+publishedAt: 2024-07-10T12:45:50.061Z
+firstPublishedAt: 2024-07-09T19:45:45.704Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: la-traduccion-automatica-de-url-no-se-produce-debido-a-caracteres-especiales
+locale: es
+kiStatus: Backlog
+internalReference: 1062858
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Intenta traducir el enlace de un producto que tiene una palabra con caracteres especiales como `calça`. Si quieres traducir esta palabra en una URL probablemente será `calca`, que no existe en el idioma portugués por lo que la `messages app` no podrá traducirla automáticamente.
+
+
+
+## Workaround
+
+
+** **
+Debe cambiar la URL del producto manualmente ejecutando la siguiente mutación:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "ruta": { "origen": "/yourTranslatedLinkdId/p", "declarer": "vtex.store@2.x", "type": "product", "id": "productId", "resolveAs": "/yourOrinalLinkdId/p", "binding": "bindingId" }}
+
+
+
+
+
+
diff --git a/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
index 3dd4763c7..fab67d978 100644
--- a/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
@@ -3,8 +3,8 @@ title: 'Actualización automática del rastreo de entregas vía Correios'
 id: 7hKUU5Qp4AyCW2QaMQC0S6
 status: PUBLISHED
 createdAt: 2017-08-16T22:07:06.254Z
-updatedAt: 2022-12-22T14:52:07.213Z
-publishedAt: 2022-12-22T14:52:07.213Z
+updatedAt: 2024-02-29T18:16:47.090Z
+publishedAt: 2024-02-29T18:16:47.090Z
 firstPublishedAt: 2017-08-16T23:00:56.342Z
 contentType: knownIssue
 productTeam: Post-purchase
@@ -34,5 +34,9 @@ Es posible enviar actualizaciones de rastreo vía API, manteniendo el comportami
 
 La confirmación de entrega hecha vía OMS también se retransmite a los marketplaces.
 
+<div class = "alert alert-info">
+Actualmente, ofrecemos el <a href="https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib">VTEX Shipping Network</a>, nuestra solución logística para integrar su operación con Correios y/o transportadoras asociadas. Todos los pedidos de su tienda vinculados a esta solución tendrán seguimiento (tracking) con actualizaciones automáticas. (Exclusivo Brasil)
+</div>
+
 Otra opción es utilizar soluciones desarrolladas por parceros para el seguimiento de las entregas de Correios, como el [rastreo de XP Agência](https://rastreio.xpagencia.com.br/).
 
diff --git a/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
new file mode 100644
index 000000000..9af4be58c
--- /dev/null
+++ b/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -0,0 +1,53 @@
+---
+title: 'El campo "disponibilidad" es incorrecto en la Simulación de Cumplimiento para productos sin stock o precio'
+id: 1k2zcLEN5vG6mnksLwEXxp
+status: PUBLISHED
+createdAt: 2023-10-04T14:22:53.519Z
+updatedAt: 2023-10-04T14:22:54.219Z
+publishedAt: 2023-10-04T14:22:54.219Z
+firstPublishedAt: 2023-10-04T14:22:54.219Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-campo-disponibilidad-es-incorrecto-en-la-simulacion-de-cumplimiento-para-productos-sin-stock-o-precio
+locale: es
+kiStatus: Backlog
+internalReference: 773537
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un producto está agotado o no tiene precio, la simulación de cumplimiento informa incorrectamente del campo "disponibilidad" como "disponible".
+Este comportamiento también se aplica al contexto de la selección de regalos, donde el campo `selectableGifts` también se ve afectado por este problema.
+
+
+1. Si el artículo tiene un precio, pero no hay existencias, la simulación de cumplimiento devolverá `"disponibilidad": "nullPrice"` cuando no haya dirección;
+2. 2. Si el artículo tiene precio, pero no hay existencias, la simulación de cumplimiento devolverá `"disponibilidad": "disponible"` cuando haya una dirección.
+
+
+##
+
+## Simulación
+
+
+
+- Tener un producto sin stock ni precio en un vendedor
+- Hacer una Simulación de Cumplimiento
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md b/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
new file mode 100644
index 000000000..262ccb7ee
--- /dev/null
+++ b/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
@@ -0,0 +1,69 @@
+---
+title: 'En la lista de direcciones disponibles de la interfaz de pago faltan datos de la dirección recién creada.'
+id: 1BEDcoXLVAs5L039eKXsXv
+status: PUBLISHED
+createdAt: 2024-07-05T21:08:40.994Z
+updatedAt: 2024-07-11T15:56:34.357Z
+publishedAt: 2024-07-11T15:56:34.357Z
+firstPublishedAt: 2024-07-05T21:08:42.246Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: en-la-lista-de-direcciones-disponibles-de-la-interfaz-de-pago-faltan-datos-de-la-direccion-recien-creada
+locale: es
+kiStatus: Backlog
+internalReference: 1061630
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario añade una nueva dirección durante el paso de envío de la caja, avanza al paso de pago y, a continuación, vuelve a la lista de direcciones disponibles del paso de envío, es posible que esta dirección recién creada no aparezca en la lista o que muestre información incompleta en la interfaz de usuario.
+
+
+
+## Simulación
+
+
+
+Caso 1, para usuarios autenticados:
+
+1. Accede a la tienda con un usuario que tenga al menos una dirección guardada y crea un carrito.
+2. Proceda al Pago y llegue a la pantalla de Pago.
+3. Haz clic en "Cambiar opciones de envío".
+4. Haz clic en "Entregar en otra dirección".
+5. Rellene una nueva dirección y haga clic en "Ir al pago".
+6. Haz clic de nuevo en "Cambiar opciones de envío".
+7. Haga clic de nuevo en "Entregar en otra dirección".
+8. Haga clic en "Volver a la lista de direcciones".
+9. Es posible que la dirección recién creada no aparezca en la lista.
+
+Caso 2, para usuarios identificados pero no autentificados:
+
+1. Crea un carrito e identifícate con el email de un usuario que tenga al menos una dirección guardada.
+2. Proceder al Checkout y llegar a la pantalla de Pago.
+3. Haz clic en "Cambiar opciones de envío".
+4. Haz clic en "Entregar en otra dirección".
+5. Rellene una nueva dirección y haga clic en "Ir al pago".
+6. Haz clic de nuevo en "Cambiar opciones de envío".
+7. Haga clic de nuevo en "Entregar en otra dirección".
+8. 8. Pulse "Volver a la lista de direcciones".
+9. Para algunos países, la dirección recién añadida puede mostrar información incompleta, como mostrar sólo el código postal y el nombre del país.
+
+
+
+## Workaround
+
+
+Actualice la página.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md b/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
new file mode 100644
index 000000000..7fc22aa12
--- /dev/null
+++ b/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
@@ -0,0 +1,46 @@
+---
+title: 'Valor de AvailableQuantity incoherente debido al gran número de rutas creadas para entregar el artículo.'
+id: 4kKVjSNsIEU8ZVGcpwvzQw
+status: PUBLISHED
+createdAt: 2024-05-16T12:14:20.776Z
+updatedAt: 2024-05-16T12:15:36.200Z
+publishedAt: 2024-05-16T12:15:36.200Z
+firstPublishedAt: 2024-05-16T12:14:21.778Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: valor-de-availablequantity-incoherente-debido-al-gran-numero-de-rutas-creadas-para-entregar-el-articulo
+locale: es
+kiStatus: Backlog
+internalReference: 1034211
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Durante el pipeline de indexación de un artículo, se realiza una simulación sin uso de código postal para validar la disponibilidad, esta simulación, cuando llega al sistema logístico, realiza una validación combinando todos los muelles, almacenes y políticas de envío disponibles para un canal de venta, la respuesta a este cálculo determina la disponibilidad del artículo, sin embargo esta respuesta tiene un límite de lectura de 10.000 rutas, por lo que cuando un cálculo da como resultado más de 10.000, el resto de rutas no se tienen en cuenta, lo que puede provocar que el sistema devuelva una respuesta inconsistente.
+
+
+##
+
+## Simulación
+
+
+No existe una forma sencilla de simular un escenario de este tipo, ya que es necesario disponer de numerosas configuraciones logísticas.
+
+
+
+## Workaround
+
+
+Eliminar las configuraciones no utilizadas del canal de ventas (Muelles, Almacenes y Políticas de envío), reduciendo así el número de rutas creadas por el sistema durante el cálculo, situando el número de rutas por debajo del límite recomendado por el sistema (10.000).
+
+
+
+
+
diff --git a/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md b/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md
new file mode 100644
index 000000000..8e298580a
--- /dev/null
+++ b/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md
@@ -0,0 +1,49 @@
+---
+title: 'Los datos de suplantación B2B no se eliminan tras cerrar la sesión'
+id: bHYLV4reDQl4epmPbYwmJ
+status: PUBLISHED
+createdAt: 2024-07-18T21:56:41.780Z
+updatedAt: 2024-07-18T21:56:42.802Z
+publishedAt: 2024-07-18T21:56:42.802Z
+firstPublishedAt: 2024-07-18T21:56:42.802Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: los-datos-de-suplantacion-b2b-no-se-eliminan-tras-cerrar-la-sesion
+locale: es
+kiStatus: Backlog
+internalReference: 1067969
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El cierre de sesión después de hacerse pasar por un usuario en B2B Suite no elimina los permisos de la tienda de la sesión.
+
+Esto permite al usuario navegar por el sitio web e incluso realizar pedidos si el usuario suplantado tiene acceso a la caja.
+
+
+
+## Simulación
+
+
+
+- Iniciar sesión con un usuario con roles de suplantación;
+- Suplantar a otro usuario;
+- Cerrar sesión.
+
+
+
+## Workaround
+
+
+Haga clic en "Detener suplantación" para eliminar los datos suplantados de la sesión.
+
+
+
+
diff --git a/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md b/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md
new file mode 100644
index 000000000..7c8ce38a0
--- /dev/null
+++ b/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md
@@ -0,0 +1,46 @@
+---
+title: 'El historial de pedidos B2B no funciona en el dominio web'
+id: 4Y7lpxWvMBZFaAA4wuvbGP
+status: PUBLISHED
+createdAt: 2023-06-22T21:53:45.542Z
+updatedAt: 2023-08-02T19:09:35.905Z
+publishedAt: 2023-08-02T19:09:35.905Z
+firstPublishedAt: 2023-06-22T21:53:46.030Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: el-historial-de-pedidos-b2b-no-funciona-en-el-dominio-web
+locale: es
+kiStatus: Fixed
+internalReference: 849394
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El Historial de Pedidos B2B no funciona en el dominio web, mostrando el mensaje "No tiene permiso para acceder a esto".
+
+
+##
+
+## Simulación
+
+
+
+- Acceda a Mi cuenta - Pedidos en el dominio del sitio web;
+- Se mostrará el mensaje "No tiene permiso para acceder a esto".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md b/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
new file mode 100644
index 000000000..155153f37
--- /dev/null
+++ b/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
@@ -0,0 +1,48 @@
+---
+title: 'La organización B2B no tiene en cuenta las cuentas que utilizan la geolocalización al registrar la dirección'
+id: 2o6k71zZQWGVNDVSTwMZSx
+status: PUBLISHED
+createdAt: 2023-09-21T16:10:29.092Z
+updatedAt: 2023-09-21T16:10:59.672Z
+publishedAt: 2023-09-21T16:10:59.672Z
+firstPublishedAt: 2023-09-21T16:10:29.723Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: la-organizacion-b2b-no-tiene-en-cuenta-las-cuentas-que-utilizan-la-geolocalizacion-al-registrar-la-direccion
+locale: es
+kiStatus: Backlog
+internalReference: 904907
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La Organización B2B no tiene nada para configurar una dirección cuando las cuentas usan geolocalización, causando que los artículos no estén disponibles.
+
+
+##
+
+## Simulación
+
+
+
+- Configure una cuenta para utilizar la geolocalización en el pago;
+- Asegúrese de que es una cuenta de países que utilizan opciones predefinidas, por ejemplo, Argentina, Chile, Colombia, etc;
+- Cree una organización;
+- Intente comprar cualquier producto, siempre estará no disponible.
+
+
+
+## Workaround
+
+
+Cambie la configuración para utilizar sólo el código postal.
+
+
+
diff --git a/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md b/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
new file mode 100644
index 000000000..c851dfd60
--- /dev/null
+++ b/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
@@ -0,0 +1,56 @@
+---
+title: 'La interfaz de usuario detallada de las organizaciones B2B sólo muestra 100 primeros vendedores'
+id: 6gZm70bIF0p92u6WtDZqdO
+status: PUBLISHED
+createdAt: 2024-01-15T21:29:19.105Z
+updatedAt: 2024-01-15T21:29:45.018Z
+publishedAt: 2024-01-15T21:29:45.018Z
+firstPublishedAt: 2024-01-15T21:29:19.660Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: la-interfaz-de-usuario-detallada-de-las-organizaciones-b2b-solo-muestra-100-primeros-vendedores
+locale: es
+kiStatus: Backlog
+internalReference: 966450
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+B2B Organizations Detail UI sólo muestra 100 primeros vendedores; la UI no tiene paginación, lo que hace imposible seleccionar un vendedor si no está en la primera página.
+
+
+##
+
+## Simulación
+
+
+
+- Asegúrese de que la cuenta tiene más de 100 vendedores registrados;
+- Acceda a la pestaña de vendedores en la Interfaz detallada de organizaciones B2B;
+- Sólo se mostrarán los 100 primeros vendedores.
+
+
+
+## Workaround
+
+
+
+- Realiza un getOrganizationById vía graphQL usando la app:
+
+    { getOrganizationById(id:""){ id name tradeName status collections { id } paymentTerms { id } priceTables customFields { name type value useOnRegistration } salesChannel sellers { id name }}
+
+- Realiza una mutación utilizando los datos del graphQL anterior:
+
+    mutation { updateOrganization ( id: "", name: "" tradeName: "" status: "active" collections: [] paymentTerms: [] priceTables: [] customFields: [] salesChannel: null sellers: [{ id: "", name: "" }] ) { id }}
+
+
+
+
+
diff --git a/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md b/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
new file mode 100644
index 000000000..e64774aa6
--- /dev/null
+++ b/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
@@ -0,0 +1,44 @@
+---
+title: 'La función de suplantación de identidad de las organizaciones B2B no registra la información en los pedidos'
+id: 48IPJWvzeN0uPjGVyOd3Ff
+status: PUBLISHED
+createdAt: 2024-06-27T13:04:27.839Z
+updatedAt: 2024-06-27T13:04:28.879Z
+publishedAt: 2024-06-27T13:04:28.879Z
+firstPublishedAt: 2024-06-27T13:04:28.879Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: la-funcion-de-suplantacion-de-identidad-de-las-organizaciones-b2b-no-registra-la-informacion-en-los-pedidos
+locale: es
+kiStatus: Backlog
+internalReference: 1056736
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Suplantar a un miembro;
+- Montar un carrito;
+- Realizar un pedido y comprobar que no se guarda información sobre la suplantación.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md b/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
new file mode 100644
index 000000000..2702a1cd8
--- /dev/null
+++ b/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
@@ -0,0 +1,48 @@
+---
+title: 'B2B Quotes no aplica el descuento al pagar en el dominio web'
+id: 2VWm5NVqW1LRSZINAAjM7B
+status: PUBLISHED
+createdAt: 2023-06-22T17:17:04.039Z
+updatedAt: 2024-01-31T21:13:13.614Z
+publishedAt: 2024-01-31T21:13:13.614Z
+firstPublishedAt: 2023-06-22T17:17:04.726Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-quotes-no-aplica-el-descuento-al-pagar-en-el-dominio-web
+locale: es
+kiStatus: Fixed
+internalReference: 849080
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una cotización tiene un descuento aplicado por un vendedor, las Cotizaciones B2B no aplicarán el descuento al momento de pagar en el dominio del sitio web.
+
+
+##
+
+## Simulación
+
+
+
+- Cree un presupuesto;
+- En el dominio del sitio web, haga clic en "Usar presupuesto";
+- En el carrito, no hay cambios en el precio del artículo.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md b/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
new file mode 100644
index 000000000..a2f9de87c
--- /dev/null
+++ b/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
@@ -0,0 +1,49 @@
+---
+title: 'B2B Suite no utiliza geocoordenadas para calcular el Id de región'
+id: 7ITcf4hiOD1k6XBIhaCclj
+status: PUBLISHED
+createdAt: 2024-06-24T21:48:19.921Z
+updatedAt: 2024-06-27T20:58:12.541Z
+publishedAt: 2024-06-27T20:58:12.541Z
+firstPublishedAt: 2024-06-24T21:48:20.731Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: b2b-suite-no-utiliza-geocoordenadas-para-calcular-el-id-de-region
+locale: es
+kiStatus: Backlog
+internalReference: 1055033
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Es posible utilizar tarifas de envío utilizando códigos postales o geocoordenadas, pero las Organizaciones B2B utilizan sólo códigos postales para calcular los ID de región. Si una cuenta tiene geolocalización (polígonos) registrada en sus tarifas de envío, los productos se mostrarán como no disponibles en el escaparate.
+
+
+##
+
+## Simulación
+
+
+
+- Registrar tarifas de envío con polígonos;
+- Crear una organización;
+- Entrar en la tienda;
+- No se muestra ningún producto.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 11ac5ee8c..a96869244 100644
--- a/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -3,8 +3,8 @@ title: '[B2W] Pedido "B2W directo" (FOB) integrando con transportista'
 id: 20nA7vm1RFMhv7yhaJ43GG
 status: PUBLISHED
 createdAt: 2022-12-12T18:14:19.975Z
-updatedAt: 2022-12-12T18:14:20.451Z
-publishedAt: 2022-12-12T18:14:20.451Z
+updatedAt: 2024-02-16T20:27:21.732Z
+publishedAt: 2024-02-16T20:27:21.732Z
 firstPublishedAt: 2022-12-12T18:14:20.451Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: b2w-pedido-b2w-directo-fob-integrando-con-transportista
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 714879
 ---
 
diff --git a/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md b/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md
index 5d2d86aea..d847d8eef 100644
--- a/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md
+++ b/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md
@@ -3,8 +3,8 @@ title: '[B2W] Valor de la carga en OMS VTEX'
 id: 7kVoMojCNmOHatg2L1ykBP
 status: PUBLISHED
 createdAt: 2022-10-04T19:43:17.116Z
-updatedAt: 2022-11-25T21:55:17.709Z
-publishedAt: 2022-11-25T21:55:17.709Z
+updatedAt: 2024-02-16T20:23:26.779Z
+publishedAt: 2024-02-16T20:23:26.779Z
 firstPublishedAt: 2022-10-04T19:43:20.129Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: b2w-valor-de-la-carga-en-oms-vtex
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 671748
 ---
 
diff --git a/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
index 40c9500b3..006f8b930 100644
--- a/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
@@ -3,8 +3,8 @@ title: 'Solicitud incorrecta al buscar términos con "%" directamente a través
 id: 3gdZ8egQRa4zcNRe2f5CbT
 status: PUBLISHED
 createdAt: 2023-03-21T22:51:46.273Z
-updatedAt: 2023-03-21T22:51:46.888Z
-publishedAt: 2023-03-21T22:51:46.888Z
+updatedAt: 2024-02-16T17:45:27.298Z
+publishedAt: 2024-02-16T17:45:27.298Z
 firstPublishedAt: 2023-03-21T22:51:46.888Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -39,8 +39,8 @@ Al buscar un término con "%" directamente vía URL, la página devuelve un 400
 
 ## Workaround
 
-**
-Buscar sin el "%"
+
+N/A
 
 
 
diff --git a/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
new file mode 100644
index 000000000..6a5025db3
--- /dev/null
+++ b/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -0,0 +1,46 @@
+---
+title: 'Solicitud incorrecta al buscar términos con "#" mediante autocompletar'
+id: 18pMsxubB9eSPGlULAN35p
+status: PUBLISHED
+createdAt: 2024-02-06T20:07:52.739Z
+updatedAt: 2024-02-06T20:07:53.531Z
+publishedAt: 2024-02-06T20:07:53.531Z
+firstPublishedAt: 2024-02-06T20:07:53.531Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: solicitud-incorrecta-al-buscar-terminos-con-mediante-autocompletar
+locale: es
+kiStatus: Backlog
+internalReference: 978136
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al buscar un término con "#" directamente mediante autocompletar, la página nunca se carga
+
+
+##
+
+## Simulación
+
+
+
+- Buscar cualquier término con "#", por ejemplo, "Camisa#" en autocompletar;
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md b/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
new file mode 100644
index 000000000..841e65975
--- /dev/null
+++ b/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
@@ -0,0 +1,45 @@
+---
+title: 'Solicitud incorrecta al intentar acceder a un inventario con una gran cantidad de artículos reservados.'
+id: 4DujUMKeYTlx2MXAjnHlS5
+status: PUBLISHED
+createdAt: 2024-07-03T20:18:55.508Z
+updatedAt: 2024-07-03T20:23:50.434Z
+publishedAt: 2024-07-03T20:23:50.434Z
+firstPublishedAt: 2024-07-03T20:18:56.626Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: solicitud-incorrecta-al-intentar-acceder-a-un-inventario-con-una-gran-cantidad-de-articulos-reservados
+locale: es
+kiStatus: Fixed
+internalReference: 296066
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Cuando intentamos ver el detalle de las reservas de una SKU en el módulo de logística, en el listado de inventario de productos (**Inventario y envío** > **Gestión de inventario**), podemos tener un problema cuando hay demasiadas reservas activas.
+
+No es posible acceder o actualizar el inventario de una SKU con una gran cantidad de artículos reservados, como por ejemplo, 100000 reservas activas.
+
+El usuario puede ver en la UI el error: **"Error al intentar obtener la reserva "**
+
+O en los detalles de respuesta de la API el error **"Demasiadas reservas activas "**
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md b/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
new file mode 100644
index 000000000..a359a1ac0
--- /dev/null
+++ b/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
@@ -0,0 +1,51 @@
+---
+title: 'Texto mal formateado para títulos de búsqueda y migas de pan en escenarios específicos con reglas de comercialización.'
+id: 3dQskVnI1sbF6jgsopjUUt
+status: PUBLISHED
+createdAt: 2024-03-13T20:52:33.781Z
+updatedAt: 2024-03-13T20:52:34.698Z
+publishedAt: 2024-03-13T20:52:34.698Z
+firstPublishedAt: 2024-03-13T20:52:34.698Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: texto-mal-formateado-para-titulos-de-busqueda-y-migas-de-pan-en-escenarios-especificos-con-reglas-de-comercializacion
+locale: es
+kiStatus: Backlog
+internalReference: 999476
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas páginas de resultados de búsqueda ocultan los filtros aplicados - puesto que ya forman parte de la propia página, por lo que se establecen como "initialAttributes" - para centrarse en los filtros adicionales que se pueden aplicar. En estos escenarios, los valores para el título de la página y las migas de pan están básicamente definidos por el primer producto de la página.
+
+Las reglas de merchandising que colocan productos de diferentes contextos en las primeras posiciones de una página afectan a esta cadena. Cuando los "initialAttributes" de la página no coinciden con ninguno de los atributos del primer producto, como alternativa, estos textos se definen por el slug - un texto simplificado sin mayúsculas, diacríticos o cualquier otro carácter especial.
+
+Tenga en cuenta que este tipo de regla de merchandising puede ser una mala práctica.
+
+
+##
+
+## Simulación
+
+
+
+- Considere una categoría con el árbol como "Alimentos > Frutas > Manzanas y Peras", que se traduce como "Maçãs e Peras" en portugués (por lo que tenemos diacríticos/acentos para un mejor ejemplo);
+- Añadir un producto de un árbol de categorías diferente a través de una Regla de Merchandising, como una cortadora de la categoría "Cocina > Accesorios > Cortadoras" a la categoría "Alimentos > Frutas";
+- Como el primer producto de la categoría "Manzanas y Peras" será esta cortadora, el título de la página y las migas de pan se presentarán como "Macas E Peras".
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
diff --git a/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md b/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
new file mode 100644
index 000000000..b4dd331e2
--- /dev/null
+++ b/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
@@ -0,0 +1,49 @@
+---
+title: 'Benefits.items array dentro de ProductContextProvider baraja los items cuando la promoción es del tipo Buy Together'
+id: 1VeBqJAKwpVR5YHqtEJ7Xz
+status: PUBLISHED
+createdAt: 2023-10-05T19:57:59.828Z
+updatedAt: 2023-10-05T19:58:00.724Z
+publishedAt: 2023-10-05T19:58:00.724Z
+firstPublishedAt: 2023-10-05T19:58:00.724Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: benefitsitems-array-dentro-de-productcontextprovider-baraja-los-items-cuando-la-promocion-es-del-tipo-buy-together
+locale: es
+kiStatus: Backlog
+internalReference: 915213
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al mirar el array de beneficios dentro del ProductContextProvider en el PDP de un producto podemos ver que no se devuelven todos los productos y se barajan los que se devuelven. Ambas listas de productos dentro de la promoción están juntas en el mismo array. Esto sólo ocurre cuando la promoción es del tipo Buy Together.
+
+
+##
+
+## Simulación
+
+
+Vaya al PDP de un producto que tenga una promoción Buy Together
+Intenta mirar el array de beneficios dentro del ProductContextProvider
+No todos los productos serán devueltos en el array de artículos, y no habrá diferenciación entre las listas de productos dentro de la promoción
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md b/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md
new file mode 100644
index 000000000..5f2a8e573
--- /dev/null
+++ b/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md
@@ -0,0 +1,58 @@
+---
+title: 'El filtro booleano en la aplicación de formularios no funciona correctamente'
+id: 4x77xCLrvU4gDWZ4s1faHw
+status: PUBLISHED
+createdAt: 2023-10-11T21:15:13.342Z
+updatedAt: 2023-10-11T21:31:06.894Z
+publishedAt: 2023-10-11T21:31:06.894Z
+firstPublishedAt: 2023-10-11T21:15:13.935Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: el-filtro-booleano-en-la-aplicacion-de-formularios-no-funciona-correctamente
+locale: es
+kiStatus: Backlog
+internalReference: 918537
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se selecciona un filtro booleano, se devuelve el siguiente mensaje:
+`Ha ocurrido un error inesperado. Por favor, inténtelo de nuevo. Si el problema persiste, póngase en contacto con el servicio de asistencia.`
+ ![](https://vtexhelp.zendesk.com/attachments/token/HAwA6Uf51x49bxGLiziKpdQnj/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+
+- Acceda al CRM de Datos Maestros (por ejemplo https://my-account-here.vtexcrm.com.br);
+- Acceder a una Solicitud de Formulario con opción de filtro booleano:
+ ![](https://vtexhelp.zendesk.com/attachments/token/tyRYoZP61rVzhVBx3A1rHbGgf/?name=image.png)
+
+- Seleccione la opción 0 o 1;
+- Pulse el botón "_Filtro_";
+- Se abrirá un mensaje emergente con el error "`Ha ocurrido un error inesperado. Por favor, inténtelo de nuevo. Si el problema persiste, póngase en contacto con el servicio de asistencia.`":
+ ![](https://vtexhelp.zendesk.com/attachments/token/HAwA6Uf51x49bxGLiziKpdQnj/?name=image.png)
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md b/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
index 3dfeb18f5..1a17f5783 100644
--- a/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
+++ b/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
@@ -3,8 +3,8 @@ title: 'Las propiedades HTML booleanas de vídeo/audio no se validan en el CMS h
 id: 2WjsLZ7vw0KO023rGQd77L
 status: PUBLISHED
 createdAt: 2022-03-16T19:27:06.599Z
-updatedAt: 2022-11-25T22:10:23.568Z
-publishedAt: 2022-11-25T22:10:23.568Z
+updatedAt: 2024-02-16T20:28:59.288Z
+publishedAt: 2024-02-16T20:28:59.288Z
 firstPublishedAt: 2022-03-16T19:27:07.097Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: las-propiedades-html-booleanas-de-videoaudio-no-se-validan-en-el-cms-heredado
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 491898
 ---
 
diff --git a/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md b/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
new file mode 100644
index 000000000..14a806969
--- /dev/null
+++ b/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
@@ -0,0 +1,43 @@
+---
+title: 'Las marcas con caracteres especiales no se pueden buscar en el administrador de marcas.'
+id: 296otMWGge4c2LJMvVhKEr
+status: PUBLISHED
+createdAt: 2024-01-04T13:57:15.861Z
+updatedAt: 2024-02-16T20:26:37.632Z
+publishedAt: 2024-02-16T20:26:37.632Z
+firstPublishedAt: 2024-01-04T13:57:16.584Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-marcas-con-caracteres-especiales-no-se-pueden-buscar-en-el-administrador-de-marcas
+locale: es
+kiStatus: No Fix
+internalReference: 503496
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La interfaz de usuario de marcas, `.myvtex.com/admin/Site/Marca.aspx`, no permite a los usuarios buscar marcas con algunos caracteres especiales en el nombre, como los apóstrofes `'`. Además, tampoco se pueden buscar letras de alfabetos no latinos, por ejemplo del alfabeto polaco como `Ż`.
+
+
+##
+
+## Simulación
+
+
+- Buscar cualquier marca con apóstrofes en la interfaz de usuario de la marca;
+- La búsqueda no encontrará marcas con apóstrofes.
+
+
+
+## Workaround
+
+
+No hay solución.
+
diff --git a/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md b/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
index e8dea5998..e91e6dc2e 100644
--- a/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
+++ b/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
@@ -3,8 +3,8 @@ title: 'La emisora no notifica todos los cambios de stock al módulo de búsqued
 id: XLozPnuonjPImtZa8bWAz
 status: PUBLISHED
 createdAt: 2022-10-24T12:26:59.536Z
-updatedAt: 2023-03-29T13:40:37.657Z
-publishedAt: 2023-03-29T13:40:37.657Z
+updatedAt: 2023-07-05T17:37:16.708Z
+publishedAt: 2023-07-05T17:37:16.708Z
 firstPublishedAt: 2022-10-24T12:27:00.490Z
 contentType: knownIssue
 productTeam: Intelligent Search
diff --git a/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md b/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md
index f5163386f..2b74b5597 100644
--- a/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md
+++ b/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md
@@ -3,8 +3,8 @@ title: 'Buscacep no funciona en la creación del formulario GiftList.'
 id: 3VRPSO1wYFX5XWrpTSD78X
 status: PUBLISHED
 createdAt: 2022-11-02T13:00:43.442Z
-updatedAt: 2022-11-25T21:42:09.907Z
-publishedAt: 2022-11-25T21:42:09.907Z
+updatedAt: 2024-02-16T20:29:33.235Z
+publishedAt: 2024-02-16T20:29:33.235Z
 firstPublishedAt: 2022-11-02T13:00:44.422Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: buscacep-no-funciona-en-la-creacion-del-formulario-giftlist
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 342418
 ---
 
diff --git a/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index 40e1068a4..c275db7fe 100644
--- a/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -3,8 +3,8 @@ title: 'Botón "Cancelar" dentro de la página de MyCards no traducido al españ
 id: 5wIEEoF7gTLYlWnANxDZ7h
 status: PUBLISHED
 createdAt: 2022-02-24T13:18:00.062Z
-updatedAt: 2022-11-25T22:07:29.627Z
-publishedAt: 2022-11-25T22:07:29.627Z
+updatedAt: 2024-02-16T20:25:05.684Z
+publishedAt: 2024-02-16T20:25:05.684Z
 firstPublishedAt: 2022-02-24T13:18:00.593Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: boton-cancelar-dentro-de-la-pagina-de-mycards-no-traducido-al-espanol
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 431200
 ---
 
diff --git a/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md b/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
new file mode 100644
index 000000000..e1e1e9858
--- /dev/null
+++ b/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
@@ -0,0 +1,49 @@
+---
+title: 'Es posible que los botones no funcionen a la primera en fullcleanup admin'
+id: 4spOMbnKZPCcnQghKTP6Zb
+status: PUBLISHED
+createdAt: 2023-04-14T17:39:56.758Z
+updatedAt: 2024-06-17T13:39:35.332Z
+publishedAt: 2024-06-17T13:39:35.332Z
+firstPublishedAt: 2023-04-14T17:39:57.290Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: es-posible-que-los-botones-no-funcionen-a-la-primera-en-fullcleanup-admin
+locale: es
+kiStatus: Backlog
+internalReference: 790828
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el administrador de Fullcleanup, se espera que los botones actúen al primer intento. Sin embargo, para realizar la acción, puede ser necesario hacer clic en el botón varias veces.
+
+
+##
+
+## Simulación
+
+
+
+1. Abrir Fullcleanup admin - `/Admin/Site/FullCleanUp.aspx `
+2. Haga clic en el botón **Reindexar base de datos**
+3. Puede que no ocurra nada
+
+
+
+## Workaround
+
+
+Intente hacer clic en la parte inferior más veces
+
+
+
+
+
diff --git a/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md b/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
new file mode 100644
index 000000000..16f765830
--- /dev/null
+++ b/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
@@ -0,0 +1,51 @@
+---
+title: 'La promoción Comprar juntos con muchas referencias puede hacer que los productos elegibles no se carguen en la parte delantera (tiempo de espera).'
+id: e1OJuUhZhYidnoRaDoDRc
+status: PUBLISHED
+createdAt: 2022-01-21T17:36:41.181Z
+updatedAt: 2024-02-16T20:29:59.287Z
+publishedAt: 2024-02-16T20:29:59.287Z
+firstPublishedAt: 2024-01-23T15:09:22.474Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: la-promocion-comprar-juntos-con-muchas-referencias-puede-hacer-que-los-productos-elegibles-no-se-carguen-en-la-parte-delantera-tiempo-de-espera
+locale: es
+kiStatus: No Fix
+internalReference: 301463
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La promoción Buy Together con muchas SKU puede hacer que los productos elegibles no se carguen en la portada debido al tiempo de espera. Las páginas de producto utilizan el control de producto `<vtex.cmc:BuyTogether/>`. Este control es responsable de llevar la información de todos los SKUs elegibles establecidos en la promoción a la página del producto.
+
+El problema es que si el cliente pone muchas SKUs en esta promoción, el Portal tendrá que traer esta información (precio, stock, etc) de todos los productos de estas SKUs a la página de producto. Y Portal hace esto simulando sus productos con el checkout. Si tenemos una promoción que se estableció con por ejemplo con 50 SKUs, y estos SKUs son de productos que tienen al menos 5 SKUs por producto) y están disponibles por ejemplo 3 Canales de Venta, Portal tendrá que simular con el checkout cada SKU para cada SC de cada producto elegible en esta promoción sólo para mostrar esta página de producto específica. En este ejemplo, Portal tendrá que hacer 750 simulaciones con la caja (50 SKUs establecidos en la promoción, suponiendo que estos SKus son de productos que tienen 5 SKUs, son 250 SKUs, y todos deben ser simulados para cada SC, lo que nos da 750 simulaciones).
+
+ps: no tenemos un número correcto a establecer en la SKU List, ya que dependerá de cada cliente. Si el cliente tiene productos con pocas SKUs y sólo una SC disponible, podrá utilizar más SKUs en este tipo de Promo.
+
+
+##
+
+## Simulación
+
+
+- Crear una Promoción Buy Together
+- Ponga en la SKU List 1 o en la SKU list 2 muchas SKUs, como más de 50.
+- Intente cargar la página Producto que utiliza el control `<vtex.cmc:BuyTogether/>`, la página no debería cargarse debido a un tiempo de espera.
+
+
+
+## Workaround
+
+
+Hay dos formas de "solucionar" este problema:
+- Eliminar el control de plantilla <vtex.cmc:BuyTogether/>, esto hará que la página del producto no cargue la información sobre este producto disponible en esta promoción;
+- Utilizar menos SKUs en la lista de la promoción Buy Together. Una vez más, desafortunadamente, no tenemos un número específico que funcione. Aconsejo al cliente que pruebe con algo como 10 y empiece a aumentar y probar.
+
+
diff --git a/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md b/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
new file mode 100644
index 000000000..3552677d9
--- /dev/null
+++ b/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
@@ -0,0 +1,47 @@
+---
+title: 'Los compradores no pueden iniciar sesión si hay una configuración incorrecta en las organizaciones/centros de costes'
+id: r5p7K15FkbZUDSOUQ6hGz
+status: PUBLISHED
+createdAt: 2023-11-30T22:21:39.852Z
+updatedAt: 2023-12-01T20:19:35.375Z
+publishedAt: 2023-12-01T20:19:35.375Z
+firstPublishedAt: 2023-11-30T22:21:40.638Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: los-compradores-no-pueden-iniciar-sesion-si-hay-una-configuracion-incorrecta-en-las-organizacionescentros-de-costes
+locale: es
+kiStatus: Backlog
+internalReference: 945609
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario tiene la primera organización asignada es inválida con el id de centro de coste incorrecto el login falla sin ningún mensaje.
+
+Aparecerá el mensaje `"App storefront-permissions failed, resulting in an error building the session"` en la respuesta de la sesión.
+
+
+
+## Simulación
+
+
+
+- Cree una organización con un identificador de centro de costes incorrecto;
+- Inicie sesión en el sitio.
+
+
+
+## Workaround
+
+
+Corrija el identificador del centro de costes asociado a la organización o elimine la organización.
+
+
+
diff --git a/docs/known-issues/es/calculation-issue-in-comissionamount.md b/docs/known-issues/es/calculation-issue-in-comissionamount.md
new file mode 100644
index 000000000..97d970ffc
--- /dev/null
+++ b/docs/known-issues/es/calculation-issue-in-comissionamount.md
@@ -0,0 +1,44 @@
+---
+title: 'Problema de cálculo en comissionAmount'
+id: 1E8DRneWHVncTu5bZ9hNtF
+status: PUBLISHED
+createdAt: 2024-03-15T21:13:28.729Z
+updatedAt: 2024-03-15T21:13:29.705Z
+publishedAt: 2024-03-15T21:13:29.705Z
+firstPublishedAt: 2024-03-15T21:13:29.705Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: problema-de-calculo-en-comissionamount
+locale: es
+kiStatus: Backlog
+internalReference: 1001005
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Esto ocurre en un escenario específico de división de pagos con múltiples pagos y vendedores (donde ambos son responsables de los gastos de procesamiento de pagos y devoluciones). La suma de `comissionAmount` de los vendedores no es igual a `amount` del mercado (problema de redondeo), esta diferencia puede causar una denegación de liquidación por parte de la entidad adquirente.
+
+
+
+## Simulación
+
+
+No hemos podido simular este problema, ya que implica varias condiciones.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md b/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
new file mode 100644
index 000000000..4d0af64f8
--- /dev/null
+++ b/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
@@ -0,0 +1,50 @@
+---
+title: 'El correo electrónico del operador del centro de llamadas se envía a orderForm cuando se añaden artículos al carrito desde el front-end de Store Framework.'
+id: 3KwP4q7VZsu6e3c1DwWY5t
+status: PUBLISHED
+createdAt: 2024-07-16T20:06:11.748Z
+updatedAt: 2024-07-16T20:06:12.844Z
+publishedAt: 2024-07-16T20:06:12.844Z
+firstPublishedAt: 2024-07-16T20:06:12.844Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-correo-electronico-del-operador-del-centro-de-llamadas-se-envia-a-orderform-cuando-se-anaden-articulos-al-carrito-desde-el-frontend-de-store-framework
+locale: es
+kiStatus: Backlog
+internalReference: 1066571
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utilizan componentes de Store Framework para añadir artículos a un carrito mientras se ha iniciado sesión como operador de un centro de llamadas y no se suplanta la identidad de ningún cliente, el correo electrónico del operador se rellena en el archivo adjunto clientProfileData del orderForm.
+
+
+##
+
+## Simulación
+
+
+
+1. Accede a una tienda construida sobre Store Framework.
+2. Autentícate como operador de un centro de llamadas.
+3. Sin suplantar a ningún cliente, añade un artículo al carrito con un componente como add-to-cart-button.
+4. 4. Compruebe que la cesta contiene la dirección de correo electrónico del operador del centro de llamadas.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md b/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
new file mode 100644
index 000000000..e38cfd189
--- /dev/null
+++ b/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
@@ -0,0 +1,45 @@
+---
+title: 'Las devoluciones de llamada tras la aprobación pueden provocar que PaymentAuthorizationWorker vuelva a intentar el pago, lo que también puede denegarlo.'
+id: 1dbTbMRMvJQaxzXjWwQplD
+status: PUBLISHED
+createdAt: 2023-09-15T18:22:54.533Z
+updatedAt: 2023-09-15T18:22:55.496Z
+publishedAt: 2023-09-15T18:22:55.496Z
+firstPublishedAt: 2023-09-15T18:22:55.496Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: las-devoluciones-de-llamada-tras-la-aprobacion-pueden-provocar-que-paymentauthorizationworker-vuelva-a-intentar-el-pago-lo-que-tambien-puede-denegarlo
+locale: es
+kiStatus: Backlog
+internalReference: 740499
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el proveedor envía una devolución de llamada justo después de la autorización, puede desencadenar un nuevo intento de autorización. Por lo tanto, en algunos casos cuando la transacción tiene más de 1 pago y uno de ellos es una tarjeta regalo, un nuevo reintento de autorización puede cancelar la transacción cuando no tiene fondos.
+
+
+##
+
+## Simulación
+
+
+No se puede simular ya que depende del callback del proveedor.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
new file mode 100644
index 000000000..09ee63f01
--- /dev/null
+++ b/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -0,0 +1,56 @@
+---
+title: 'Interfaz de usuario de la audiencia de la campaña cambiando "Diferente de" a "Igual a" con una colección'
+id: 6IkWioZ9WRgg1DFEMdnthB
+status: PUBLISHED
+createdAt: 2023-08-15T15:12:54.580Z
+updatedAt: 2023-08-15T15:18:11.108Z
+publishedAt: 2023-08-15T15:18:11.108Z
+firstPublishedAt: 2023-08-15T15:12:55.461Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: interfaz-de-usuario-de-la-audiencia-de-la-campana-cambiando-diferente-de-a-igual-a-con-una-coleccion
+locale: es
+kiStatus: Backlog
+internalReference: 881131
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al crear un público objetivo y establecer Colecciones **Diferente a** esta opción se guarda en la interfaz de usuario, después de volver al público objetivo se mostrará como Igual a en la interfaz de usuario, pero mantiene su primera opción en la API.
+
+
+
+## Simulación
+
+
+
+** **
+Cree un público de Campaña con un público objetivo, en Colecciones, seleccione Diferente de y guarde.
+Vuelve al público objetivo y comprueba que la opción Diferente de ha cambiado a Igual a
+
+Antes de guardar:
+ ![](https://vtexhelp.zendesk.com/attachments/token/kHN5aLHsNDPz5pblzihtgsw28/?name=Captura+de+Tela+2023-08-15+a%CC%80s+12.09.12.png)
+
+Después de guardar:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/hLAnRYl94mE99yyyRWVo461j5/?name=Captura+de+Tela+2023-08-15+a%CC%80s+12.09.24.png)
+
+
+
+## Workaround
+
+
+Dado que se trata de un error visual, no hay ninguna solución disponible. Simplemente comprueba en la API si tu opción se guardó correctamente y el objetivo se aplicará en consecuencia.
+
+
+
+
+
diff --git a/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md b/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md
index b3d519761..1391abf98 100644
--- a/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md
+++ b/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md
@@ -3,8 +3,8 @@ title: 'El botón de guardar de CampoValorForm.aspx requiere dos clics'
 id: G0YtmOpdB4nNdw8w87ZNz
 status: PUBLISHED
 createdAt: 2022-02-16T13:28:52.922Z
-updatedAt: 2022-11-25T21:45:10.712Z
-publishedAt: 2022-11-25T21:45:10.712Z
+updatedAt: 2024-02-16T20:26:25.672Z
+publishedAt: 2024-02-16T20:26:25.672Z
 firstPublishedAt: 2022-02-16T13:28:53.505Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-boton-de-guardar-de-campovalorformaspx-requiere-dos-clics
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 525616
 ---
 
diff --git a/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md b/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md
new file mode 100644
index 000000000..1275fae6f
--- /dev/null
+++ b/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md
@@ -0,0 +1,49 @@
+---
+title: 'Las etiquetas canónicas no se aplican a partir del tercer nivel de categoría.'
+id: 6HU8WLT5yVRBqeBmGgYRsi
+status: PUBLISHED
+createdAt: 2023-11-08T13:31:23.182Z
+updatedAt: 2024-02-19T19:24:10.757Z
+publishedAt: 2024-02-19T19:24:10.757Z
+firstPublishedAt: 2023-11-08T13:31:24.275Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: las-etiquetas-canonicas-no-se-aplican-a-partir-del-tercer-nivel-de-categoria
+locale: es
+kiStatus: Backlog
+internalReference: 932349
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las etiquetas canónicas no se aplican después del 3er nivel de categoría cuando se tiene un árbol de categorías con más de 3 niveles (departamento, categoría y subcategoría), los otros niveles por encima no se muestran en canónica
+
+
+##
+
+## Simulación
+
+
+
+1. Crear cualquier subcategoría de 4º nivel
+2. Acceder a la página creada
+3. Compruebe el Canonical de la misma en la consola, no mostrará nada después del 3er nivel. Sólo el 3º y siguientes.
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md b/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md
new file mode 100644
index 000000000..f7813fd58
--- /dev/null
+++ b/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md
@@ -0,0 +1,46 @@
+---
+title: 'No se puede editar el nombre de la plantilla Estilos'
+id: 5czxRVaMCZFgvOadfYKl1h
+status: PUBLISHED
+createdAt: 2023-08-16T17:41:40.059Z
+updatedAt: 2023-08-16T17:41:41.113Z
+publishedAt: 2023-08-16T17:41:41.113Z
+firstPublishedAt: 2023-08-16T17:41:41.113Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: no-se-puede-editar-el-nombre-de-la-plantilla-estilos
+locale: es
+kiStatus: Backlog
+internalReference: 882147
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Una vez creado un nuevo estilo en el módulo Estilos no es posible editar su nombre.
+
+
+##
+
+## Simulación
+
+
+Crea tu plantilla de estilo en el módulo Estilos y guárdala. Intenta editar su nombre, verás que no hay opción para ello.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md b/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md
new file mode 100644
index 000000000..99a1def01
--- /dev/null
+++ b/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md
@@ -0,0 +1,45 @@
+---
+title: 'Marcas de tarjetas procesadas incorrectamente como Visa'
+id: 7xXie4JWGLWe0ImmHAHzSy
+status: PUBLISHED
+createdAt: 2024-04-30T13:28:23.035Z
+updatedAt: 2024-04-30T20:35:47.075Z
+publishedAt: 2024-04-30T20:35:47.075Z
+firstPublishedAt: 2024-04-30T13:28:24.008Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: marcas-de-tarjetas-procesadas-incorrectamente-como-visa
+locale: es
+kiStatus: Backlog
+internalReference: 1024823
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas tarjetas de crédito pueden ser procesadas como Visa cuando en realidad son de otra marca.
+
+
+##
+
+## Simulación
+
+
+No hemos sido capaces de replicar este problema, esto parece ocurrir en dispositivos móviles y tarjetas guardadas.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md b/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md
index a21e4f03a..0acf26d15 100644
--- a/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md
+++ b/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md
@@ -3,8 +3,8 @@ title: 'La pantalla de integración de facebook no guarda algunos ajustes'
 id: 4MTMozT5bmub7Y96TXCl09
 status: PUBLISHED
 createdAt: 2022-03-23T18:52:58.216Z
-updatedAt: 2022-12-02T18:05:07.099Z
-publishedAt: 2022-12-02T18:05:07.099Z
+updatedAt: 2024-02-16T20:26:09.791Z
+publishedAt: 2024-02-16T20:26:09.791Z
 firstPublishedAt: 2022-03-23T18:52:58.849Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: la-pantalla-de-integracion-de-facebook-no-guarda-algunos-ajustes
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 548763
 ---
 
diff --git a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
new file mode 100644
index 000000000..d2131a97a
--- /dev/null
+++ b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
@@ -0,0 +1,46 @@
+---
+title: 'El carro creado a partir de un pedido antiguo no trae las opciones de montaje'
+id: 530zUKzAm8oafA8BKl7G8F
+status: PUBLISHED
+createdAt: 2024-04-19T20:21:41.131Z
+updatedAt: 2024-04-19T20:21:42.184Z
+publishedAt: 2024-04-19T20:21:42.184Z
+firstPublishedAt: 2024-04-19T20:21:42.184Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-carro-creado-a-partir-de-un-pedido-antiguo-no-trae-las-opciones-de-montaje
+locale: es
+kiStatus: Backlog
+internalReference: 1020278
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+1. Pide un producto con opciones de montaje;
+2. Accede a la pantalla "Mis pedidos";
+3. Haga clic en "Pedir de nuevo";
+4. Observe que el carro que se generó entonces sólo traía las referencias del pedido anterior, sin sus conjuntos.
+
+
+
+## Workaround
+
+
+Actualmente, no existe ninguna solución para este caso.
+
+
+
+
+
diff --git a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
index ca493c323..b5d3047ad 100644
--- a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
+++ b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
@@ -3,8 +3,8 @@ title: 'El carrito creado a partir de un pedido antiguo no trae los archivos adj
 id: 2TGthMyZOUQWkc2Wo6wgIg
 status: PUBLISHED
 createdAt: 2019-01-08T16:58:19.057Z
-updatedAt: 2023-05-08T18:33:57.918Z
-publishedAt: 2023-05-08T18:33:57.918Z
+updatedAt: 2024-07-01T18:49:01.443Z
+publishedAt: 2024-07-01T18:49:01.443Z
 firstPublishedAt: 2019-01-08T18:21:16.502Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-carrito-creado-a-partir-de-un-pedido-antiguo-no-trae-los-archivos-adjuntos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 802464
 ---
 
diff --git a/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
new file mode 100644
index 000000000..cc59f134e
--- /dev/null
+++ b/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -0,0 +1,57 @@
+---
+title: 'Carro creado a partir de una opción "pedir de nuevo" en Mis pedidos, el correo electrónico del cliente no se está colocando como se esperaba en el orderForm'
+id: 6dDhkaIhquOqaDuNkVZuln
+status: PUBLISHED
+createdAt: 2023-12-04T22:41:21.385Z
+updatedAt: 2023-12-04T22:41:22.139Z
+publishedAt: 2023-12-04T22:41:22.139Z
+firstPublishedAt: 2023-12-04T22:41:22.139Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: carro-creado-a-partir-de-una-opcion-pedir-de-nuevo-en-mis-pedidos-el-correo-electronico-del-cliente-no-se-esta-colocando-como-se-esperaba-en-el-orderform
+locale: es
+kiStatus: Backlog
+internalReference: 947563
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+En la sección **Mis Pedidos** dentro de **Mi Cuenta**, existe la opción de configurar un carrito basado en un pedido que el cliente haya realizado previamente.
+
+En este caso, el problema es que en un **flujo de televenta**, al **personificar al cliente e intentar montar un carrito en base a un pedido anterior**, al pulsar sobre el **Mis Pedidos (Lista)** en la opción "**Pedir de nuevo**", se coloca en los datos del perfil del cliente del formulario de pedido el email del agente de televenta y no el del cliente como se esperaba.
+
+Cabe destacar que este comportamiento sólo se produce al pulsar sobre el botón "volver a pedir" en la lista de pedidos de Mis Pedidos.
+
+
+##
+
+## Simulación
+
+
+
+1. Inicio de sesión con un usuario de televenta
+2. Hacerse pasar por un cliente
+3. Ir a la sección Mis pedidos dentro de Mi cuenta
+4. En la lista de pedidos, haz clic en "volver a pedir" en cualquiera de ellos.
+5. Valide la información del cliente en el orderForm (clientProfileData.email)
+
+
+
+## Workaround
+
+
+
+Para realizar pedidos basados en uno anterior, se recomienda introducir primero los detalles del pedido y, a continuación, hacer clic en la opción "volver a pedir".
+
+
+
+
+
diff --git a/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md b/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
new file mode 100644
index 000000000..70efe4d2f
--- /dev/null
+++ b/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
@@ -0,0 +1,46 @@
+---
+title: 'carrito item.deliveryType falta enviado por pago en AdditionalData'
+id: lV8VxXUPOzO9cSMgNV4fj
+status: PUBLISHED
+createdAt: 2024-03-19T12:59:17.599Z
+updatedAt: 2024-03-19T12:59:18.450Z
+publishedAt: 2024-03-19T12:59:18.450Z
+firstPublishedAt: 2024-03-19T12:59:18.450Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: carrito-itemdeliverytype-falta-enviado-por-pago-en-additionaldata
+locale: es
+kiStatus: Backlog
+internalReference: 1002115
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando hay una cantidad dividida en el `priceDefinition` debido al redondeo para el multiplicador de unidades, la pasarela no puede recibir ningún valor para `deliveryType` en el objeto del carrito. Por lo tanto, esto podría causar que el proveedor de pago denegar el pago si utilizan este campo..
+
+
+##
+
+## Simulación
+
+
+
+- Realiza un pedido con un carrito con una cantidad dividida en el campo `priceDefinition` del orderForm;
+- Comprueba el "miniCart.Items", puede que no tenga ``deliveryType``.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md b/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md
new file mode 100644
index 000000000..e6e5c0d94
--- /dev/null
+++ b/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md
@@ -0,0 +1,44 @@
+---
+title: 'Cart Itens se guardan en pedidos con valor total cero'
+id: 66D6RuacgCeCMQDmLPrlNP
+status: PUBLISHED
+createdAt: 2024-06-24T20:59:07.721Z
+updatedAt: 2024-06-24T20:59:08.668Z
+publishedAt: 2024-06-24T20:59:08.668Z
+firstPublishedAt: 2024-06-24T20:59:08.668Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: cart-itens-se-guardan-en-pedidos-con-valor-total-cero
+locale: es
+kiStatus: Backlog
+internalReference: 1054999
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Crear un carrito con valor total `0`;
+- Finalice la compra;
+- Vuelva a acceder al carrito después de algún tiempo; no habrá ningún cambio en el contenido del carrito.
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
diff --git a/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md b/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
new file mode 100644
index 000000000..4c9b554b8
--- /dev/null
+++ b/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
@@ -0,0 +1,47 @@
+---
+title: 'Los carritos con direcciones de varios países pierden la dirección de recogida si la tienda no puede enviar a todos los países.'
+id: 5yDJ05btQxQq8BuZzfopqv
+status: PUBLISHED
+createdAt: 2024-07-19T15:02:39.647Z
+updatedAt: 2024-07-19T15:02:41.579Z
+publishedAt: 2024-07-19T15:02:41.579Z
+firstPublishedAt: 2024-07-19T15:02:41.579Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-carritos-con-direcciones-de-varios-paises-pierden-la-direccion-de-recogida-si-la-tienda-no-puede-enviar-a-todos-los-paises
+locale: es
+kiStatus: Backlog
+internalReference: 1068197
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si un comprador tiene varias direcciones de distintos países en su perfil y la tienda no realiza entregas en ninguna de esas direcciones, al seleccionar la recogida en una dirección válida y pasar al paso de pago, la interfaz de usuario de la caja redirige al comprador de nuevo al paso de envío.
+
+
+
+## Simulación
+
+
+
+- Registrar direcciones de un país en el que la tienda no ofrece entrega;
+- Ir a la caja y seleccionar una dirección válida con el país que la tienda entrega;
+- Haga clic en "Ir al pago".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md b/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
new file mode 100644
index 000000000..c09cfddb4
--- /dev/null
+++ b/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
@@ -0,0 +1,46 @@
+---
+title: 'Los carros creados a partir de la sustitución de pedidos no reciben correctamente las promociones'
+id: 2ODIE9RNP7Q5LCglXsztzf
+status: PUBLISHED
+createdAt: 2023-10-20T17:47:40.494Z
+updatedAt: 2023-10-20T17:47:41.099Z
+publishedAt: 2023-10-20T17:47:41.099Z
+firstPublishedAt: 2023-10-20T17:47:41.099Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-carros-creados-a-partir-de-la-sustitucion-de-pedidos-no-reciben-correctamente-las-promociones
+locale: es
+kiStatus: Backlog
+internalReference: 473424
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Tener una promoción para múltiples métodos de pago
+- Cerrar el pedido pagando con "A", que debe tener un descuento
+- En la pantalla de mis pedidos, elegir cambiar la forma de pago del pedido
+- De vuelta al carrito, elija pagar con "B"
+- El descuento no se mostrará
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md b/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md
new file mode 100644
index 000000000..b35f8159e
--- /dev/null
+++ b/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md
@@ -0,0 +1,48 @@
+---
+title: 'Las promociones de devolución de dinero no tienen en cuenta los artículos retirados de los pedidos'
+id: lm9v37jvUSCeh9FVFHjsr
+status: PUBLISHED
+createdAt: 2024-04-19T13:50:10.264Z
+updatedAt: 2024-04-19T13:50:11.130Z
+publishedAt: 2024-04-19T13:50:11.130Z
+firstPublishedAt: 2024-04-19T13:50:11.130Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-promociones-de-devolucion-de-dinero-no-tienen-en-cuenta-los-articulos-retirados-de-los-pedidos
+locale: es
+kiStatus: Backlog
+internalReference: 1019864
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+1 - Cree una promoción de cashback del 10%, restringida sólo a usted (para evitar aplicaciones incorrectas) y con la condición de facturado para aplicar los créditos.
+
+2 - Cierre un pedido de 100$ compuesto por 2 artículos: uno que cuesta 80$ y otro 20$.
+
+3 - Los créditos aplicados deberían ser de 10$. Elimine el artículo de 8$ del pedido y factúrelo.
+
+4 - Se le seguirán abonando 10 $ en concepto de cashback, a pesar de que el valor esperado sea ahora de 2 $, lo que ocurre porque los cálculos de la promoción se realizan durante la simulación de pago, antes de cerrar el pedido.
+
+
+
+## Workaround
+
+
+No hay solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md b/docs/known-issues/es/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
index 133e3d8e8..041082d80 100644
--- a/docs/known-issues/es/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
+++ b/docs/known-issues/es/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
@@ -3,8 +3,8 @@ title: 'Catalog API /catalog/pvt/stockkeepingunit with query parameter refId ret
 id: 71Y9CFaM10xaVyQkcgKydQ
 status: PUBLISHED
 createdAt: 2022-01-21T15:28:34.187Z
-updatedAt: 2022-12-22T15:16:11.363Z
-publishedAt: 2022-12-22T15:16:11.363Z
+updatedAt: 2024-02-16T20:24:19.402Z
+publishedAt: 2024-02-16T20:24:19.402Z
 firstPublishedAt: 2022-12-22T15:16:11.363Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 388869
 ---
 
diff --git a/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md b/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
new file mode 100644
index 000000000..eaaba4b9e
--- /dev/null
+++ b/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
@@ -0,0 +1,50 @@
+---
+title: 'La API del catálogo no responde correctamente a los espacios al final de las cadenas'
+id: 37TmHtc19126iarlQ4IL2p
+status: PUBLISHED
+createdAt: 2024-02-05T16:49:35.136Z
+updatedAt: 2024-07-01T18:49:25.845Z
+publishedAt: 2024-07-01T18:49:25.845Z
+firstPublishedAt: 2024-02-05T16:49:36.178Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-api-del-catalogo-no-responde-correctamente-a-los-espacios-al-final-de-las-cadenas
+locale: es
+kiStatus: No Fix
+internalReference: 977033
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza la colección de la API de catálogo, si se envía un campo JSON de cadena que termina con espacios (por ejemplo productName: "myProductName ") las API de catálogo responderán con una respuesta 400 incorrecta y un cuerpo de respuesta vacío, dejando al usuario sin saber qué se envió incorrectamente.
+
+La respuesta correcta debería seguir siendo 400 (solicitud incorrecta) pero con un tratamiento de errores que informe de qué campo es incorrecto y por qué.
+
+
+##
+
+## Simulación
+
+
+Para cualquier API de catálogo (https://developers.vtex.com/docs/api-reference/catalog-api) inserte 1+ espacios vacíos al final de un campo de cadena, como se ejemplifica arriba.
+
+
+
+## Workaround
+
+
+n/a
+
+Este tipo de cadena no debe aceptarse, pero debe ajustarse el tratamiento de errores.
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md b/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md
new file mode 100644
index 000000000..8e21ae2ad
--- /dev/null
+++ b/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md
@@ -0,0 +1,50 @@
+---
+title: 'La exportación de catálogos no admite los caracteres ț y ș.'
+id: 1c28limdEHowD4LKDeHAB1
+status: PUBLISHED
+createdAt: 2023-12-11T17:40:16.688Z
+updatedAt: 2023-12-11T17:40:17.536Z
+publishedAt: 2023-12-11T17:40:17.536Z
+firstPublishedAt: 2023-12-11T17:40:17.536Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-exportacion-de-catalogos-no-admite-los-caracteres-t-y-s
+locale: es
+kiStatus: Backlog
+internalReference: 950933
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, la importación/exportación de catálogos corta nuestros caracteres especiales ț y ș al exportar datos.
+
+
+##
+
+## Simulación
+
+
+1 - Crear un producto que tenga ș en su nombre.
+
+2 - en la pestaña exportar del módulo catálogo, intenta exportar una hoja de cálculo.
+
+3 - este carácter no se mostrará en la hoja de cálculo exportada.
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md b/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md
new file mode 100644
index 000000000..e015f83fe
--- /dev/null
+++ b/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md
@@ -0,0 +1,54 @@
+---
+title: 'Exportación de catálogos para recortes de anexos > 50 caracteres'
+id: 7hX23y19wmMNPTUgbhh2WX
+status: PUBLISHED
+createdAt: 2023-12-14T16:46:58.819Z
+updatedAt: 2023-12-14T16:46:59.522Z
+publishedAt: 2023-12-14T16:46:59.522Z
+firstPublishedAt: 2023-12-14T16:46:59.522Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: exportacion-de-catalogos-para-recortes-de-anexos-50-caracteres
+locale: es
+kiStatus: Backlog
+internalReference: 953161
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al importar datos de adjuntos en el módulo catálogo, si dicho adjunto tiene más de 50 caracteres, se corta la cadena, lo que provoca que no se actualicen estos datos.
+
+
+##
+
+## Simulación
+
+
+1 - crear un adjunto con un nombre de más de 50 caracteres, por ejemplo, "Este es un nombre de adjunto muy largo que se crea para probar una incidencia".
+
+2 - asociarlo a un producto
+
+3 - exportar estos datos utilizando la interfaz de usuario /admin/Site/Relatorio_Skus.aspx
+
+4 - Compruebe la columna relacionada con esto y se mostrará como "`Este es un nombre de archivo adjunto muy largo que se crea`" (exactamente a 50 caracteres).
+
+5 - tendrá que ajustar manualmente esta información si desea importarlo correctamente
+
+
+
+## Workaround
+
+
+Actualice los archivos adjuntos a través de la API, la interfaz de usuario o cambie manualmente su cadena incorrecta en la hoja.
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-filters-timeout.md b/docs/known-issues/es/catalog-filters-timeout.md
new file mode 100644
index 000000000..58de30041
--- /dev/null
+++ b/docs/known-issues/es/catalog-filters-timeout.md
@@ -0,0 +1,47 @@
+---
+title: 'Tiempo de espera de los filtros de catálogo'
+id: 5KtT2SvTSO6xMdJOSYz5VZ
+status: PUBLISHED
+createdAt: 2023-10-19T17:11:37.486Z
+updatedAt: 2023-10-19T17:11:38.181Z
+publishedAt: 2023-10-19T17:11:38.181Z
+firstPublishedAt: 2023-10-19T17:11:38.181Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: tiempo-de-espera-de-los-filtros-de-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 922350
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Para las tiendas con una gran cantidad de skus (1 millón o más), a menudo, al filtrar utilizando los filtros de la interfaz de usuario del catálogo, ya sea para el menú principal o para la sección de informes, si la consulta de filtro devuelve un resultado muy grande, la interfaz de usuario se agota (504 tiempo de espera de la puerta de enlace).
+
+
+
+## Simulación
+
+
+No hay forma fiable de simularlo de forma consistente - sólo consultas específicas de gran tamaño para pocas cuentas acaban en error.
+
+
+
+## Workaround
+
+
+Solicite una "limpieza del filtro de usuario" al equipo de producto.
+
+Además, si la misma consulta está generando a menudo un tiempo de espera (es decir, se filtra para un departamento específico y se agota el tiempo de espera), considere la posibilidad de realizar filtros que seleccionen un subconjunto de lo que desea (en el mismo ejemplo, una categoría dentro del departamento dado)
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md b/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md
new file mode 100644
index 000000000..c00288702
--- /dev/null
+++ b/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md
@@ -0,0 +1,49 @@
+---
+title: 'Catalog GraphQL CategoryInputTranslation no funciona'
+id: 1Zue7Roia2sYa4xNP9hF2y
+status: PUBLISHED
+createdAt: 2024-04-29T14:30:53.743Z
+updatedAt: 2024-04-29T14:30:54.577Z
+publishedAt: 2024-04-29T14:30:54.577Z
+firstPublishedAt: 2024-04-29T14:30:54.577Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-graphql-categoryinputtranslation-no-funciona
+locale: es
+kiStatus: Backlog
+internalReference: 1024172
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, el método CategoryInputTranslation, para el catálogo graphQL no está generando una actualización en los datos traducidos para las cuentas.
+
+
+##
+
+## Simulación
+
+
+1 - Acceda al IDE graphQL de VTEX y seleccione la aplicación vtex.catalog-graphql@1.103.1
+2 - Crear una mutación para el método CategoryInputTranslation
+3 - Compruebe si dicha actualización se ha reflejado en los datos traducidos en el sitio web
+
+
+##
+
+## Workaround
+
+
+Utilizar directamente la aplicación de mensajes VTEX para traducir los datos (vtex.messages)
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md b/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md
new file mode 100644
index 000000000..cda73dc07
--- /dev/null
+++ b/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md
@@ -0,0 +1,47 @@
+---
+title: 'El indexador de catálogos genera documentos de traducción no válidos'
+id: 3pbXOA3DQILdu05tAwjlVM
+status: PUBLISHED
+createdAt: 2024-02-29T18:02:38.600Z
+updatedAt: 2024-07-01T18:49:27.852Z
+publishedAt: 2024-07-01T18:49:27.852Z
+firstPublishedAt: 2024-02-29T18:02:39.430Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-indexador-de-catalogos-genera-documentos-de-traduccion-no-validos
+locale: es
+kiStatus: No Fix
+internalReference: 991494
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al indexar un producto con información traducida se solicitan los mensajes de la aplicación. Se supone que estas solicitudes son menos de 3s y cuando toman más de que la indexación falla y genera un documento de traducción no válida.
+
+
+
+##
+
+## Simulación
+
+
+No hay una manera fácil de reproducir este escenario, pero las cuentas con muchos idiomas o muchos campos para traducir son más susceptibles a este escenario.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
index 5e25b5161..502e36f05 100644
--- a/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
@@ -3,8 +3,8 @@ title: 'Error de cálculo de la sección "total" del informe de indexación del
 id: 6TJXux104P2c0mruo5vlEn
 status: PUBLISHED
 createdAt: 2022-02-25T11:39:42.098Z
-updatedAt: 2022-11-25T21:45:40.741Z
-publishedAt: 2022-11-25T21:45:40.741Z
+updatedAt: 2024-02-16T20:26:35.750Z
+publishedAt: 2024-02-16T20:26:35.750Z
 firstPublishedAt: 2022-02-25T11:39:42.485Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: error-de-calculo-de-la-seccion-total-del-informe-de-indexacion-del-catalogo
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 499450
 ---
 
diff --git a/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md b/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md
new file mode 100644
index 000000000..ffaf689d4
--- /dev/null
+++ b/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md
@@ -0,0 +1,47 @@
+---
+title: 'El campo de código fiscal XML de la integración de catálogos no se muestra'
+id: 19Ubw33gsHcyIeMUQA3LGh
+status: PUBLISHED
+createdAt: 2024-05-10T14:28:22.117Z
+updatedAt: 2024-05-10T14:28:23.190Z
+publishedAt: 2024-05-10T14:28:23.190Z
+firstPublishedAt: 2024-05-10T14:28:23.190Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-campo-de-codigo-fiscal-xml-de-la-integracion-de-catalogos-no-se-muestra
+locale: es
+kiStatus: Backlog
+internalReference: 1031109
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+1 - Registra un código fiscal en un producto de tu tienda.
+2 - En la configuración XML de su cuenta https://myaccountname.myvtex.com/admin/Site/Xml.aspx, configure el campo XML de código fiscal
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/LHjBFETlon2zWcRX7pXYF0xjP/?name=image.png)
+
+3 - Cargue el XML generado y, a pesar de que el producto contenga datos válidos, las etiquetas XML de código fiscal no cargarán contenido válido.
+
+
+
+## Workaround
+
+
+Utilice otros medios de integración del catálogo si un código fiscal es absolutamente necesario en las operaciones de su tienda.
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md b/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md
new file mode 100644
index 000000000..703cd582b
--- /dev/null
+++ b/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md
@@ -0,0 +1,50 @@
+---
+title: 'API de búsqueda en catálogos limitada a 2.500 resultados'
+id: 33kKjUGKN5tlxvksnbnw7n
+status: PUBLISHED
+createdAt: 2023-08-31T14:59:31.132Z
+updatedAt: 2023-08-31T14:59:31.766Z
+publishedAt: 2023-08-31T14:59:31.766Z
+firstPublishedAt: 2023-08-31T14:59:31.766Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: api-de-busqueda-en-catalogos-limitada-a-2500-resultados
+locale: es
+kiStatus: Backlog
+internalReference: 891184
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar la API de Búsqueda por Catálogo el máximo de resultados obtenidos es de 2500, aunque haya más productos.
+La paginación es hasta 50 productos y funciona correctamente hasta que el parámetro _from alcanza el número de 2500. Cuando establecen `_from` por encima de 2500 obtienen `"Parameter _from can't be greater than 2500."`.
+
+
+##
+
+## Simulación
+
+
+Esta situación puede ocurrir al solicitar la API utilizando postman o utilizando el catálogo compartido en las cuentas del portal del vendedor (utiliza la misma API en la interfaz de usuario).
+
+Cuando se utiliza la API: - hacer la solicitud utilizando el paramenter `_from` por encima de 2500
+Al utilizar el catálogo compartido - omita la paginación en la pestaña de productos disponibles hasta llegar a 2500. Las páginas siguientes no se actualizarán y mostrarán los mismos resultados que la página anterior a 2500.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md b/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
index d4f6437fd..0e12896de 100644
--- a/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
+++ b/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
@@ -3,8 +3,8 @@ title: 'La API de Facetas de Búsqueda del Catálogo no devuelve la información
 id: 1JrbscqI4BQgFqfVuRZIl8
 status: PUBLISHED
 createdAt: 2022-05-23T13:58:53.501Z
-updatedAt: 2022-11-25T21:45:53.573Z
-publishedAt: 2022-11-25T21:45:53.573Z
+updatedAt: 2024-02-16T20:25:52.080Z
+publishedAt: 2024-02-16T20:25:52.080Z
 firstPublishedAt: 2022-05-23T13:58:53.924Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-api-de-facetas-de-busqueda-del-catalogo-no-devuelve-la-informacion-de-los-productos-no-disponibles
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 583623
 ---
 
diff --git a/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md b/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md
new file mode 100644
index 000000000..a019c0bc0
--- /dev/null
+++ b/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md
@@ -0,0 +1,57 @@
+---
+title: 'Las traducciones del catálogo no se reflejan en el frontend'
+id: 4c6Qzdn6NQfHhEN5U76WOi
+status: PUBLISHED
+createdAt: 2023-07-13T19:43:10.669Z
+updatedAt: 2023-07-13T19:43:11.858Z
+publishedAt: 2023-07-13T19:43:11.858Z
+firstPublishedAt: 2023-07-13T19:43:11.858Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-traducciones-del-catalogo-no-se-reflejan-en-el-frontend
+locale: es
+kiStatus: Backlog
+internalReference: 861892
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el comerciante realiza una acción en la aplicación Mensajes para que se traduzcan algunos datos del producto en el frontend, esta acción no se está reflejando realmente.
+
+
+##
+
+## Simulación
+
+
+
+1. Realiza un cambio en la aplicación de mensajes;
+2. 2. Compruebe en el indexInfo si el campo GenerateAndSaveTranslationsDocument está configurado como 'false'.
+3. No vuelva a indexar el producto;
+4. 4. Compruebe que el cambio no se ha reflejado en el sitio web traducido.
+
+
+
+## Workaround
+
+
+Para forzar la aparición de las traducciones es necesario reindexar el producto. Una de las siguientes acciones debe hacer el truco:
+
+- Cambiar el nombre;
+- Cambiar las palabras clave;
+- Cambiar el texto;
+- Cambiar la categoría;
+- Cambiar la marca;
+- Cambiar la bandera activa.
+
+
+
+
+
diff --git a/docs/known-issues/es/catalogv2-user-roles-not-applying.md b/docs/known-issues/es/catalogv2-user-roles-not-applying.md
index 7c37aa70d..38308357f 100644
--- a/docs/known-issues/es/catalogv2-user-roles-not-applying.md
+++ b/docs/known-issues/es/catalogv2-user-roles-not-applying.md
@@ -3,8 +3,8 @@ title: 'Los roles de usuario de CatalogV2 no se aplican'
 id: 3cDaOuqpAJyCL5JOMzD5nL
 status: PUBLISHED
 createdAt: 2022-02-25T12:18:17.776Z
-updatedAt: 2022-11-25T21:55:04.311Z
-publishedAt: 2022-11-25T21:55:04.311Z
+updatedAt: 2024-02-16T20:26:53.078Z
+publishedAt: 2024-02-16T20:26:53.078Z
 firstPublishedAt: 2022-02-25T12:18:18.632Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: los-roles-de-usuario-de-catalogv2-no-se-aplican
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 489297
 ---
 
diff --git a/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md b/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
new file mode 100644
index 000000000..0b5ab1428
--- /dev/null
+++ b/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
@@ -0,0 +1,51 @@
+---
+title: 'La asignación de categorías y marcas de la hoja de cálculo no se actualiza con los valores de la pestaña Revisar skus.'
+id: 50p9fJ63Loml6pWqcKxm9Y
+status: PUBLISHED
+createdAt: 2024-05-03T13:51:01.537Z
+updatedAt: 2024-05-03T13:51:02.491Z
+publishedAt: 2024-05-03T13:51:02.491Z
+firstPublishedAt: 2024-05-03T13:51:02.491Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: la-asignacion-de-categorias-y-marcas-de-la-hoja-de-calculo-no-se-actualiza-con-los-valores-de-la-pestana-revisar-skus
+locale: es
+kiStatus: Backlog
+internalReference: 1026699
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un vendedor envía al marketplace una sku con una categoría o marca que aún no está mapeada en la hoja de cálculo, ésta se actualiza con este nuevo valor en la 3ª columna para poder ser mapeada.
+
+Si el sku se envía a la pestaña Revisar, esta actualización no se produce.
+
+
+
+## Simulación
+
+
+
+1. El vendedor envía una sku con una marca/categoría no asignada al marketplace;
+2. El sku incumple alguna regla opcional sobre la calidad de la oferta;
+3. El sku pasa a la pestaña de revisión;
+4. Compruebe que la hoja de cálculo de asignación no está actualizada.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/category-score-field-is-not-being-saved.md b/docs/known-issues/es/category-score-field-is-not-being-saved.md
index fc3950d64..3ced98101 100644
--- a/docs/known-issues/es/category-score-field-is-not-being-saved.md
+++ b/docs/known-issues/es/category-score-field-is-not-being-saved.md
@@ -3,8 +3,8 @@ title: 'Campo Score de categoría no se está guardando'
 id: 3YxhdI31I4SY62w6oY806s
 status: PUBLISHED
 createdAt: 2018-06-01T17:24:40.180Z
-updatedAt: 2022-12-22T20:48:43.605Z
-publishedAt: 2022-12-22T20:48:43.605Z
+updatedAt: 2024-03-05T15:28:44.072Z
+publishedAt: 2024-03-05T15:28:44.072Z
 firstPublishedAt: 2018-06-01T17:39:02.287Z
 contentType: knownIssue
 productTeam: Marketing & Merchandising
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: campo-score-de-categoria-no-se-esta-guardando
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 
 ---
 
diff --git a/docs/known-issues/es/centauro-to-implement-centauro-envios.md b/docs/known-issues/es/centauro-to-implement-centauro-envios.md
index b847e68b4..3edc8fbe6 100644
--- a/docs/known-issues/es/centauro-to-implement-centauro-envios.md
+++ b/docs/known-issues/es/centauro-to-implement-centauro-envios.md
@@ -3,8 +3,8 @@ title: '[Centauro] Implementar "Centauro Envios"'
 id: 1xkjyfVfT8Fs2as9mbNjj3
 status: PUBLISHED
 createdAt: 2022-11-25T21:23:23.849Z
-updatedAt: 2022-11-25T21:23:24.283Z
-publishedAt: 2022-11-25T21:23:24.283Z
+updatedAt: 2024-02-16T20:24:05.883Z
+publishedAt: 2024-02-16T20:24:05.883Z
 firstPublishedAt: 2022-11-25T21:23:24.283Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: centauro-implementar-centauro-envios
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 618941
 ---
 
diff --git a/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md b/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
new file mode 100644
index 000000000..2fc7ed9fc
--- /dev/null
+++ b/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
@@ -0,0 +1,58 @@
+---
+title: 'El enlace de cambio de pedido en la página de pago/pedido realizado lleva a myAccount en lugar de a la página de pedido.'
+id: 6bP44VBdFIujX072rY6wCA
+status: PUBLISHED
+createdAt: 2023-06-15T16:13:03.752Z
+updatedAt: 2023-06-15T16:13:04.279Z
+publishedAt: 2023-06-15T16:13:04.279Z
+firstPublishedAt: 2023-06-15T16:13:04.279Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-enlace-de-cambio-de-pedido-en-la-pagina-de-pagopedido-realizado-lleva-a-myaccount-en-lugar-de-a-la-pagina-de-pedido
+locale: es
+kiStatus: Backlog
+internalReference: 844893
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la cuenta ha configurado la posibilidad de que el comprador cambie el pedido por sí mismo, el enlace de cambio de pedido aparecerá en la plantilla de pago/pedido realizado.
+
+Sin embargo, este enlace no redirige al cliente a la página de edición, sino a myAccount, que aparece vacía.
+
+
+
+##
+
+## Simulación
+
+
+Configure la opción Permitir a los clientes realizar cambios en los pedidos en Admin -> configuración -> configuración de pedidos
+ ![](https://vtexhelp.zendesk.com/attachments/token/GqrSJ7cBhZc844LR3kXH7WMlX/?name=image.png)
+
+El comprador realiza un pedido y pasa por caja/pedidoRealizado
+
+Compruebe que el enlace no le redirige al área de edición de pedidos.
+
+
+
+## Workaround
+
+
+
+1. El comprador tiene que hacer clic en Mis Pedidos en la sección myAccount;
+2. Elegir de nuevo el pedido que quieren modificar;
+3. 3. Hacer clic en Cambiar pedido.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md b/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
index 8063808dc..4c8cb1a55 100644
--- a/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
+++ b/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
@@ -3,8 +3,8 @@ title: 'La orden de cambio a través de la UI no tiene en cuenta el cálculo de
 id: 3rvsDyCggYirvH7WT9rBVZ
 status: PUBLISHED
 createdAt: 2022-03-15T20:25:17.217Z
-updatedAt: 2022-11-25T22:03:48.329Z
-publishedAt: 2022-11-25T22:03:48.329Z
+updatedAt: 2024-02-16T20:23:38.705Z
+publishedAt: 2024-02-16T20:23:38.705Z
 firstPublishedAt: 2022-03-15T20:25:17.513Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: la-orden-de-cambio-a-traves-de-la-ui-no-tiene-en-cuenta-el-calculo-de-las-promociones-toma-3-paga-2
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 472882
 ---
 
diff --git a/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md b/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md
index e7ac94c6a..ecbacd69b 100644
--- a/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md
+++ b/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md
@@ -3,8 +3,8 @@ title: 'Modificación de la orden a través de la API sin correo electrónico or
 id: 1KMglga4xM1s7EvNO1mmua
 status: PUBLISHED
 createdAt: 2022-05-18T18:40:48.935Z
-updatedAt: 2022-11-25T22:02:43.384Z
-publishedAt: 2022-11-25T22:02:43.384Z
+updatedAt: 2024-02-16T20:27:31.478Z
+publishedAt: 2024-02-16T20:27:31.478Z
 firstPublishedAt: 2022-05-18T18:40:49.234Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: modificacion-de-la-orden-a-traves-de-la-api-sin-correo-electronico-orderchanged
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 380509
 ---
 
diff --git a/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md b/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
new file mode 100644
index 000000000..36f148a2d
--- /dev/null
+++ b/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
@@ -0,0 +1,49 @@
+---
+title: 'Los cambios realizados en la página de administración de Estilos no se guardan correctamente'
+id: 4XmBeVMf0yZJElH85mSxC3
+status: PUBLISHED
+createdAt: 2024-01-25T19:13:16.165Z
+updatedAt: 2024-01-25T19:13:16.858Z
+publishedAt: 2024-01-25T19:13:16.858Z
+firstPublishedAt: 2024-01-25T19:13:16.858Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: los-cambios-realizados-en-la-pagina-de-administracion-de-estilos-no-se-guardan-correctamente
+locale: es
+kiStatus: No Fix
+internalReference: 971948
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los cambios que se realizan utilizando la página de estilos de la interfaz de usuario de administración no se están guardando correctamente y no siempre se aplicarán a la página web.
+
+
+##
+
+## Simulación
+
+
+Intente realizar cambios en el estilo del sitio web a través de la página de estilos.
+Guarde los cambios.
+Los cambios no se reflejan y no se guardan.
+No se registran errores en la consola y se muestra el mensaje de "Guardado correctamente".
+
+
+
+## Workaround
+
+
+No hay solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md b/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md
new file mode 100644
index 000000000..541c9adce
--- /dev/null
+++ b/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md
@@ -0,0 +1,50 @@
+---
+title: 'El cambio de accesorios no provoca la indexación'
+id: 5asLRh4ChyuSEg1mRwWbgT
+status: PUBLISHED
+createdAt: 2024-05-22T18:30:14.578Z
+updatedAt: 2024-05-22T18:30:15.412Z
+publishedAt: 2024-05-22T18:30:15.412Z
+firstPublishedAt: 2024-05-22T18:30:15.412Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-cambio-de-accesorios-no-provoca-la-indexacion
+locale: es
+kiStatus: Backlog
+internalReference: 1037800
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el comerciante realiza cambios o añade nuevos accesorios a la sku, el indexador no se activa automáticamente.
+
+Esto hace que los cambios no se reflejen en la interfaz de usuario hasta que otra acción active el indexador.
+
+
+
+## Simulación
+
+
+Realiza un cambio o añade un accesorio a un sku.
+Compruebe (después del tiempo de caché) que el PDP no se actualiza automáticamente.
+Haga otro cambio en el sku.
+Compruebe (después del tiempo de caché) que el PDP reflejará ambos cambios.
+
+
+
+## Workaround
+
+
+Forzar al indexador realizando otra acción sobre el sku.
+
+
+
+
+
diff --git a/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md b/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
index bfaf95845..602995561 100644
--- a/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
+++ b/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
@@ -3,8 +3,8 @@ title: 'Cambiar el orden de una especificación de SKU en el Admin podría hacer
 id: 5MuozhOKaYLGShytNH5k8Z
 status: PUBLISHED
 createdAt: 2022-08-10T13:57:53.322Z
-updatedAt: 2022-11-25T21:43:51.741Z
-publishedAt: 2022-11-25T21:43:51.741Z
+updatedAt: 2024-02-16T20:26:58.129Z
+publishedAt: 2024-02-16T20:26:58.129Z
 firstPublishedAt: 2022-08-10T13:57:53.867Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: cambiar-el-orden-de-una-especificacion-de-sku-en-el-admin-podria-hacer-que-la-pagina-no-funcione-correctamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 460329
 ---
 
diff --git a/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md b/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
index e55c7ec85..0c9634abc 100644
--- a/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
+++ b/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
@@ -3,8 +3,8 @@ title: 'El pago permite pasar al formulario de pago sin la dirección de envío
 id: 3k9zxMq6Pl9WBnIz5Hy6Xf
 status: PUBLISHED
 createdAt: 2022-11-18T18:42:08.326Z
-updatedAt: 2022-11-25T23:17:39.653Z
-publishedAt: 2022-11-25T23:17:39.653Z
+updatedAt: 2024-02-16T20:27:39.990Z
+publishedAt: 2024-02-16T20:27:39.990Z
 firstPublishedAt: 2022-11-18T18:42:08.914Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-pago-permite-pasar-al-formulario-de-pago-sin-la-direccion-de-envio-en-la-interfaz-de-usuario-solamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 699317
 ---
 
diff --git a/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md b/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md
new file mode 100644
index 000000000..55f448537
--- /dev/null
+++ b/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md
@@ -0,0 +1,49 @@
+---
+title: 'El pago permite añadir 2 direcciones diferentes para la entrega'
+id: 2z7iq68qdHXAfY8RLDHXDg
+status: PUBLISHED
+createdAt: 2023-11-06T22:03:24.983Z
+updatedAt: 2023-11-07T21:28:43.164Z
+publishedAt: 2023-11-07T21:28:43.164Z
+firstPublishedAt: 2023-11-06T22:03:25.472Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-pago-permite-anadir-2-direcciones-diferentes-para-la-entrega
+locale: es
+kiStatus: Backlog
+internalReference: 931225
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Checkout permite añadir dos direcciones diferentes para la entrega en el orderForm, por ejemplo, una "comercial" y una "residencial" (definidas por el campo 'addressType'), cuando una de ellas es desechable.
+
+Cuando se seleccionan ambas direcciones, aparece el mensaje de error "Imposible comunicarse con el vendedor", y el comprador no puede continuar con los siguientes pasos.
+
+
+##
+
+## Simulación
+
+
+
+- Enviar una nueva dirección a través de API Añadir dirección de envío y seleccionar opción de entrega;
+- Añadir un cliente que ya tiene un perfil completo a través de API Añadir perfil de cliente.
+
+
+
+## Workaround
+
+ provisional
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md b/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
new file mode 100644
index 000000000..77855c236
--- /dev/null
+++ b/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
@@ -0,0 +1,44 @@
+---
+title: "Checkout permite a los usuarios saltar al paso de pago con un 'shippingData' vacío cuando se utiliza geolocalización"
+id: 7uv85LIrjoPaHxVgCAoy7I
+status: PUBLISHED
+createdAt: 2023-10-23T17:48:05.377Z
+updatedAt: 2023-10-23T17:58:49.908Z
+publishedAt: 2023-10-23T17:58:49.908Z
+firstPublishedAt: 2023-10-23T17:48:06.206Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-permite-a-los-usuarios-saltar-al-paso-de-pago-con-un-shippingdata-vacio-cuando-se-utiliza-geolocalizacion
+locale: es
+kiStatus: Backlog
+internalReference: 343056
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Enviar la dirección vía API con datos incompletos;
+- Añadir cualquier producto a la cesta;
+- Ir al carrito y pasar por caja;
+- Añadir la información del perfil.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md b/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
index 00b98216c..dd096adc2 100644
--- a/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
+++ b/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'La caja no calcula correctamente el valor del envío para un solo artíc
 id: 4jX7JT0Wxt9S4xBe9FSwO
 status: PUBLISHED
 createdAt: 2022-02-21T19:48:04.202Z
-updatedAt: 2022-11-25T21:53:42.846Z
-publishedAt: 2022-11-25T21:53:42.846Z
+updatedAt: 2024-02-16T20:26:29.918Z
+publishedAt: 2024-02-16T20:26:29.918Z
 firstPublishedAt: 2022-02-21T19:48:04.748Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-caja-no-calcula-correctamente-el-valor-del-envio-para-un-solo-articulo-que-tiene-envio-gratuito-y-entrega-programada
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 529043
 ---
 
diff --git a/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md b/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
index f5cb73b1d..dc457b74f 100644
--- a/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
+++ b/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
@@ -3,8 +3,8 @@ title: 'El pago no muestra la promoción de envío en el primer instante para un
 id: 14rQaM53csQQeA1wu5lRj8
 status: PUBLISHED
 createdAt: 2022-05-20T17:46:10.644Z
-updatedAt: 2022-11-25T21:53:02.607Z
-publishedAt: 2022-11-25T21:53:02.607Z
+updatedAt: 2024-01-15T14:35:39.473Z
+publishedAt: 2024-01-15T14:35:39.473Z
 firstPublishedAt: 2022-05-20T17:46:11.046Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-pago-no-muestra-la-promocion-de-envio-en-el-primer-instante-para-una-condicion-especifica
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 280144
 ---
 
@@ -23,23 +23,36 @@ internalReference: 280144
 </div>
 
 
-La caja (backend) tiene un comportamiento de preselección del mejor método de entrega para el usuario tan pronto como se informa de un código postal.
+El checkout (backend) tiene un comportamiento de pre-seleccionar el mejor método de entrega para el usuario tan pronto como un código postal es informado.
 
-Las promociones que utilizan la restricción de "Aplicar el descuento sólo cuando uno de los transportistas anteriores es seleccionado por el cliente" de hecho sólo se aplican después de que el cliente elige el método de entrega específico.
+Las promociones que utilizan la restricción de "Aplicar el descuento sólo cuando uno de los transportistas anteriores es seleccionado por el cliente", de hecho, sólo se aplican después de que el cliente elige el método de entrega específico.
 
-Ocurre que, si la opción de entrega seleccionada automáticamente en el momento de la compra entra en alguna promoción con la restricción anterior, el descuento no se aplicará La opción mencionada es la que dice "Aplicar el descuento sólo cuando uno de los transportistas anteriores es seleccionado por el cliente").
+Sucede que, si la opción de entrega seleccionada automáticamente al realizar el pago se ajusta a cualquier promoción con la restricción anterior, el descuento no se aplicará (la opción mencionada es la que dice "Aplicar el descuento sólo cuando uno de los transportistas anteriores es seleccionado por el cliente").
 
-Esto sólo ocurre en el primer momento, ya que el checkout no recalcula las promociones al hacer esta elección de entrega automática. Esto se debe a que, si recalcula las promociones, eventualmente la mejor opción de entrega puede ser diferente, y esto dejaría al sistema en un bucle, buscando siempre la mejor opción. En la futura actualización del orderForm, se recalcula todo su contexto, esta vez con la forma de entrega realmente seleccionada, y entonces se aplicará la promoción.
+Esto sólo ocurre en el primer momento, ya que el checkout no recalcula las promociones al hacer esta elección de entrega automática. Esto se debe a que, si recalcula las promociones, eventualmente la mejor opción de entrega puede ser diferente, y esto dejaría al sistema en un bucle, buscando siempre la mejor opción. En futuras actualizaciones de orderForm, se recalcula todo su contexto, esta vez con la forma de entrega realmente seleccionada, y entonces se aplicará la promoción.
 
-Además de este hecho, la simulación de envío del carrito (shipping-preview) realiza peticiones adicionales a la API, no sólo utilizando el contexto de orderForm. Esto hace que reciba la promoción, mientras que los totales del carrito están restringidos al contexto del orderForm, que aún no tiene la promoción, lo que da lugar a valores divergentes.
+Además de este hecho, la simulación de envío del carrito (shipping-preview) realiza peticiones adicionales a la API, no sólo utilizando el contexto del orderForm. Esto hace que reciba la promoción, mientras que los totales del carrito se restringen al contexto del orderForm, que aún no tiene la promoción, lo que da lugar a valores divergentes.
 
 
+##
 
 ## Simulación
 
 
+- tener una promoción de envío gratuito restringida a una opción "A", y con la opción adicional anterior activada
+- tener un carrito y un código postal con dos o más tipos de envío, donde "A" es el envío más barato (ejemplo, A = R$10; B = R$20)
+- introduzca el código postal y tenga en cuenta que "A" (el más barato) se seleccionará automáticamente, pero seguirá apareciendo como R$10
+- seleccione el envío "B" (20 R$) y vuelva al envío "A" (10 R$)
+- en este momento el valor de "A" se volverá a calcular y aparecerá como gratuito
+
+
 
 ## Workaround
 
+**
+No se recomienda utilizar esta restricción en las promociones de envío.
+
+
+
 
 
diff --git a/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md b/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md
new file mode 100644
index 000000000..e40ad9903
--- /dev/null
+++ b/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md
@@ -0,0 +1,47 @@
+---
+title: 'Checkout no admite la codificación de nombres de opciones de montaje'
+id: 29YnOA15HDzJSRwiOLLNfR
+status: PUBLISHED
+createdAt: 2024-05-06T19:01:35.962Z
+updatedAt: 2024-05-06T19:01:36.828Z
+publishedAt: 2024-05-06T19:01:36.828Z
+firstPublishedAt: 2024-05-06T19:01:36.828Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-no-admite-la-codificacion-de-nombres-de-opciones-de-montaje
+locale: es
+kiStatus: Backlog
+internalReference: 378842
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los nombres de las opciones de ensamblaje se utilizan en la ruta API. Por ello, es necesario soportar la codificación de estos nombres para no crear problemas en la URL con caracteres especiales, como "/". Al añadir una opción de montaje con "/" en el carrito, simplemente no se añade y tampoco se notifica al usuario.
+
+
+##
+
+## Simulación
+
+
+
+- Añada una "/" en el nombre de la opción de montaje;
+- Intente añadir un producto con la opción de montaje;
+- El artículo se añadirá al carrito sin la opción de montaje.
+
+
+
+## Workaround
+
+
+Elimine "/" del nombre de la opción de montaje.
+
+
+
diff --git a/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md b/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md
index 2f551d9ed..b610f3ac3 100644
--- a/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md
+++ b/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md
@@ -3,8 +3,8 @@ title: 'El pago envía incorrectamente los detalles del artículo a la transacci
 id: YxjZNKuIxkKQioS7lkmu8
 status: PUBLISHED
 createdAt: 2022-03-04T15:08:55.326Z
-updatedAt: 2022-11-25T21:52:34.380Z
-publishedAt: 2022-11-25T21:52:34.380Z
+updatedAt: 2024-02-16T20:28:39.301Z
+publishedAt: 2024-02-16T20:28:39.301Z
 firstPublishedAt: 2022-03-04T15:08:55.710Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-pago-envia-incorrectamente-los-detalles-del-articulo-a-la-transaccion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 535859
 ---
 
diff --git a/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md b/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
new file mode 100644
index 000000000..75ac70a0c
--- /dev/null
+++ b/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
@@ -0,0 +1,46 @@
+---
+title: 'El proceso de pago no actualiza los impuestos teniendo en cuenta el vendedor correcto al combinar la información del carro.'
+id: 4HDGps2Ez5kWKuW1UNX1JQ
+status: PUBLISHED
+createdAt: 2024-07-03T20:21:23.533Z
+updatedAt: 2024-07-03T20:21:24.413Z
+publishedAt: 2024-07-03T20:21:24.413Z
+firstPublishedAt: 2024-07-03T20:21:24.413Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-proceso-de-pago-no-actualiza-los-impuestos-teniendo-en-cuenta-el-vendedor-correcto-al-combinar-la-informacion-del-carro
+locale: es
+kiStatus: Backlog
+internalReference: 759842
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando hay 2 vendedores en el método "SellerElection", uno de ellos es seleccionado como el que tiene el precio más barato para la entrega, y el otro el precio más barato para la recogida en el punto, la fusión de la información del carrito no actualiza los impuestos al seleccionar la recogida en el punto, causando un error al finalizar la compra.
+
+
+
+## Simulación
+
+
+
+- Tener configurados dos vendedores: 1 es el más barato en entrega y el otro en recogida en destino
+- Configure los impuestos _sólo_ para el vendedor que realizará la recogida en el punto de entrega o diferentes impuestos entre ellos
+- Realice una Simulación de Pago y verá que no habrá impuestos en "priceTags" y no finalizará la compra
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
new file mode 100644
index 000000000..ed5be0f20
--- /dev/null
+++ b/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -0,0 +1,47 @@
+---
+title: 'La simulación de pago devuelve el valor 0 en el campo "slas.tax" para los impuestos del porcentaje de envío.'
+id: 54Mtsj8EKuo0SaQCoWyYzj
+status: PUBLISHED
+createdAt: 2024-04-05T18:55:32.183Z
+updatedAt: 2024-04-05T18:55:33.336Z
+publishedAt: 2024-04-05T18:55:33.336Z
+firstPublishedAt: 2024-04-05T18:55:33.336Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-simulacion-de-pago-devuelve-el-valor-0-en-el-campo-slastax-para-los-impuestos-del-porcentaje-de-envio
+locale: es
+kiStatus: Backlog
+internalReference: 1012724
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los impuestos del porcentaje de envío no se devuelven en el campo `logisticsInfo.slas.tax` al realizar una simulación de pago aunque la información de los impuestos individuales esté disponible en el campo `items.priceTags`.
+
+
+
+## Simulación
+
+
+
+- Configurar un Impuesto de Porcentaje de Envío
+- Realizar una solicitud de simulación de carrito con el ANS seleccionado
+- El campo `tax` devuelve el valor `0
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md b/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
new file mode 100644
index 000000000..3c5a1953d
--- /dev/null
+++ b/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
@@ -0,0 +1,51 @@
+---
+title: 'Simulación de pago con una gran cantidad de la misma sku recibe un tiempo de espera Logística'
+id: 753MDZbcyN9BTHAaSTpOlY
+status: PUBLISHED
+createdAt: 2024-06-18T12:42:44.404Z
+updatedAt: 2024-06-18T12:42:45.419Z
+publishedAt: 2024-06-18T12:42:45.419Z
+firstPublishedAt: 2024-06-18T12:42:45.419Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: simulacion-de-pago-con-una-gran-cantidad-de-la-misma-sku-recibe-un-tiempo-de-espera-logistica
+locale: es
+kiStatus: No Fix
+internalReference: 330775
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Tenemos un error en el servicio de Logística cuando intentamos simular una compra con miles de unidades del mismo SKU. Ese error se produce porque la solicitud para dividir el paquete tarda demasiado.
+
+El detalle del error en la API es: "La operación fue cancelada".
+
+
+##
+
+## Simulación
+
+
+
+1. Intenta hacer una **Simulación de caja** o una simulación en el **Carro de la compra** con miles de unidades del mismo SKU (como 50k).
+2. Revisa los detalles en la respuesta de la API, y probablemente veas un error al procesar esa petición (**timeout**)
+
+
+
+## Workaround
+
+
+Recomendamos aumentar los límites de paquetes del transportista para acomodar las unidades en un solo paquete. Proporcionaría una solicitud más rápida y no devolvería un tiempo de espera.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md b/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
new file mode 100644
index 000000000..454378e9f
--- /dev/null
+++ b/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
@@ -0,0 +1,50 @@
+---
+title: 'La interfaz de usuario de pago pasa a Pago con una dirección de factura incompleta para compradores con perfil completo.'
+id: NmN6oNKp1isyxssTE5jPR
+status: PUBLISHED
+createdAt: 2023-11-27T17:40:11.335Z
+updatedAt: 2023-12-12T15:46:39.789Z
+publishedAt: 2023-12-12T15:46:39.789Z
+firstPublishedAt: 2023-11-27T17:40:12.008Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-de-pago-pasa-a-pago-con-una-direccion-de-factura-incompleta-para-compradores-con-perfil-completo
+locale: es
+kiStatus: Fixed
+internalReference: 937615
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un comprador tiene un perfil completo y la tienda está configurada para utilizar una dirección de factura para la recogida, la interfaz de usuario pasará a Pago con una dirección de factura incompleta.
+
+
+##
+
+## Simulación
+
+
+
+- Configurar la dirección de factura para la recogida;
+ ![](https://vtexhelp.zendesk.com/attachments/token/1zJ19Lq9oJ5CHdkaHUfw4SAka/?name=image.png)
+
+- Después de añadir productos a la cesta, utilice un correo electrónico con un perfil completo;
+- La interfaz de usuario pasará al pago incluso con una dirección de factura incompleta en el sistema de perfiles.
+
+
+
+## Workaround
+
+
+Actualice la dirección de facturación a través de Datos Maestros.
+
+
+
+
diff --git a/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
new file mode 100644
index 000000000..937abbf58
--- /dev/null
+++ b/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -0,0 +1,53 @@
+---
+title: 'La interfaz de usuario de la caja no utiliza automáticamente el "envío reducido" para los artículos sin métodos de envío comunes.'
+id: 2LXp8VCAay7Ic9MBfbtirT
+status: PUBLISHED
+createdAt: 2024-04-02T15:27:23.003Z
+updatedAt: 2024-04-02T15:27:24.004Z
+publishedAt: 2024-04-02T15:27:24.004Z
+firstPublishedAt: 2024-04-02T15:27:24.004Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-de-la-caja-no-utiliza-automaticamente-el-envio-reducido-para-los-articulos-sin-metodos-de-envio-comunes
+locale: es
+kiStatus: Backlog
+internalReference: 329846
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La configuración de Checkout UI permite desactivar el lean shipping (optimizaciones del modo de entrega), pero esto sólo es posible si todos los artículos del carrito tienen en común los mismos métodos de entrega. De lo contrario, el lean shipping debe aparecer forzosamente en el carrito incluso con la opción desactivada.
+Sin embargo, en algunos escenarios, el comportamiento reportado arriba no sucede, y todos los métodos de entrega disponibles son presentados individualmente al comprador.
+
+Como resultado, al no haber forma de seleccionar un método de entrega diferente para cada artículo, ningún envío mostrado corresponde a una única opción de entrega para todo el carro, presentándose opciones y paquetes sin sentido.
+
+
+##
+
+## Simulación
+
+
+
+- Desactivar las **Opciones de envío optimizadas****;**
+- Montar un carrito donde no todos los artículos tengan el mismo método de entrega;
+- También es necesario que la tienda tenga activado "allowMultipleDeliveries";
+- El escenario reportado mostrará las opciones abiertamente en lugar de lean shipping.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md b/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
index efa17a60b..b515fdcd5 100644
--- a/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
+++ b/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
@@ -1,10 +1,10 @@
 ---
 title: 'Checkout UI loops when not receiving correct SLA values from logistics system'
 id: 4tACwwmorLZ7NAt3zWldWL
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-04T19:28:24.852Z
-updatedAt: 2022-06-27T12:27:43.525Z
-publishedAt: 2022-06-26T16:28:26.833Z
+updatedAt: 2024-02-16T20:28:53.645Z
+publishedAt: 2024-02-16T20:28:53.645Z
 firstPublishedAt: 2022-05-04T19:28:25.322Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 485016
 ---
 
diff --git a/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md b/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
new file mode 100644
index 000000000..5f5a9e6bf
--- /dev/null
+++ b/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
@@ -0,0 +1,50 @@
+---
+title: 'Checkout UI envía guión en el código postal a orderForm'
+id: 3cqrBqq5x8nixjAFt8BxCx
+status: PUBLISHED
+createdAt: 2024-01-16T12:37:56.497Z
+updatedAt: 2024-01-16T12:37:57.041Z
+publishedAt: 2024-01-16T12:37:57.041Z
+firstPublishedAt: 2024-01-16T12:37:57.041Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: checkout-ui-envia-guion-en-el-codigo-postal-a-orderform
+locale: es
+kiStatus: Backlog
+internalReference: 937692
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Checkout UI envía un guión para el código postal a orderForm, causando problemas al calcular los ANS cuando un país tiene 7 dígitos + el guión. Esto sucede porque el módulo de Logística considera el guión como un dígito y dependiendo de cómo se registraron las tarifas de envío en la política de envío.
+
+Portugal y Japón son los únicos en este escenario.
+
+
+##
+
+## Simulación
+
+
+
+- Tener una cuenta para Portugal o Japón;
+- Después de añadir productos a la cesta, escriba el código postal;
+- El producto puede aparecer como no disponible.
+
+
+
+## Workaround
+
+
+
+- Revise las tarifas de envío para incluir una gama más amplia.
+
+
+
diff --git a/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md b/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
new file mode 100644
index 000000000..1b110db6e
--- /dev/null
+++ b/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
@@ -0,0 +1,47 @@
+---
+title: 'La interfaz de pago muestra el envío gratuito cuando el usuario cambia las opciones de entrega.'
+id: 5ibXQuVSU5vLfihL8uImyX
+status: PUBLISHED
+createdAt: 2023-09-27T20:40:02.973Z
+updatedAt: 2023-10-02T19:35:11.231Z
+publishedAt: 2023-10-02T19:35:11.231Z
+firstPublishedAt: 2023-09-27T20:40:03.494Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-pago-muestra-el-envio-gratuito-cuando-el-usuario-cambia-las-opciones-de-entrega
+locale: es
+kiStatus: Backlog
+internalReference: 897109
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La interfaz de usuario de la caja muestra la entrega gratuita cuando el usuario cambia el método de entrega de envío normal a entrega programada. El problema solo se produce en el cuadro de entrega y cuando la cuenta tiene configurada la función LeanShipping. aunque la IU muestra el envío gratuito, los valores totales de la compra se muestran y cobran correctamente.
+
+
+##
+
+## Simulación
+
+
+
+1. Vaya a la página de pago comprando un artículo al azar
+2. en la sección de envío, seleccione envío programado y, a continuación, vuelva a seleccionar envío normal y aparecerá el precio de envío gratuito en la sección de envío
+
+
+
+## Workaround
+
+
+No hay solución.
+
+
+
+
diff --git a/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md b/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
index f66ebe6f9..c0fd44533 100644
--- a/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
+++ b/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
@@ -3,8 +3,8 @@ title: 'La ciudad y el estado no se envían a PayPalPlus cuando sólo hay una di
 id: 5ScWTMLqT9oBMUYFc6WGo2
 status: PUBLISHED
 createdAt: 2023-06-01T13:47:08.477Z
-updatedAt: 2023-06-01T13:47:09.590Z
-publishedAt: 2023-06-01T13:47:09.590Z
+updatedAt: 2023-09-12T13:10:53.169Z
+publishedAt: 2023-09-12T13:10:53.169Z
 firstPublishedAt: 2023-06-01T13:47:09.590Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-ciudad-y-el-estado-no-se-envian-a-paypalplus-cuando-solo-hay-una-direccion-de-recogida-disponible
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 836025
 ---
 
@@ -47,3 +47,4 @@ Seleccione "Entrega", añada el código postal y cambie a "Recogida en tienda".
 
 
 
+
diff --git a/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md b/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
new file mode 100644
index 000000000..7796ef717
--- /dev/null
+++ b/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
@@ -0,0 +1,42 @@
+---
+title: 'El botón Borrar filtro no gestiona correctamente los filtros múltiples'
+id: TVLYkkJXq5bxmFvHZyRS6
+status: PUBLISHED
+createdAt: 2024-01-03T22:35:40.705Z
+updatedAt: 2024-01-03T22:35:41.328Z
+publishedAt: 2024-01-03T22:35:41.328Z
+firstPublishedAt: 2024-01-03T22:35:41.328Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: el-boton-borrar-filtro-no-gestiona-correctamente-los-filtros-multiples
+locale: es
+kiStatus: Backlog
+internalReference: 960905
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En algunos casos, como en páginas de destino y páginas de colección, los filtros adicionales no se borran correctamente después de hacer clic en el botón "Borrar filtro". La URL puede ir a filtros no válidos o erróneos y el listado de productos puede quedar vacío o con productos inesperados.
+
+
+##
+
+## Simulación
+
+
+En un tema de tienda con el botón "Borrar filtros" activado, pruébalo en una página de destino o de colección después de aplicar filtros adicionales.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md b/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
new file mode 100644
index 000000000..9f057f62c
--- /dev/null
+++ b/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
@@ -0,0 +1,53 @@
+---
+title: 'El valor del documento del cliente no se actualiza correctamente a veces en la configuración Global Checkout'
+id: 3846jcrfuMvULJt5dZkJxf
+status: PUBLISHED
+createdAt: 2023-07-17T20:50:26.133Z
+updatedAt: 2023-07-17T20:50:27.048Z
+publishedAt: 2023-07-17T20:50:27.048Z
+firstPublishedAt: 2023-07-17T20:50:27.048Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-valor-del-documento-del-cliente-no-se-actualiza-correctamente-a-veces-en-la-configuracion-global-checkout
+locale: es
+kiStatus: Backlog
+internalReference: 863726
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza Global Checkout, y el cambio de utilizar el documento por defecto y un documento auto-identificado y el valor informado para el campo de número de documento no "tomarlo" correctamente.
+
+Se adjunta un video que muestra el comportamiento.
+
+
+
+
+##
+
+## Simulación
+
+
+Aplique las personalizaciones para habilitar el checkout global.
+Proceda a añadir un documento ajeno y guarde los cambios del perfil.
+Edite el perfil, cambie a entrada de documento normal e introduzca un valor diferente, luego guarde los cambios
+Abra el perfil de nuevo, a veces el valor mostrado fue reemplazado por el valor extranjero
+
+
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md b/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
new file mode 100644
index 000000000..42ed8cc05
--- /dev/null
+++ b/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
@@ -0,0 +1,47 @@
+---
+title: 'clientProfileData se vacía si la solicitud Añadir perfil de cliente se realiza dos veces'
+id: 1TG7cnnMyWHNKrCjoouKoC
+status: PUBLISHED
+createdAt: 2023-10-02T15:51:35.989Z
+updatedAt: 2023-10-02T15:51:36.771Z
+publishedAt: 2023-10-02T15:51:36.771Z
+firstPublishedAt: 2023-10-02T15:51:36.771Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: clientprofiledata-se-vacia-si-la-solicitud-anadir-perfil-de-cliente-se-realiza-dos-veces
+locale: es
+kiStatus: Backlog
+internalReference: 911203
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se envía la petición Añadir perfil de cliente dos veces y el email tiene un perfil completo, "clientProfileData" se queda vacío, mostrando sólo el email.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir perfil de cliente vía API;
+- Vuelva a enviar la misma solicitud autenticada, el "clientProfileData" tendrá sólo el correo electrónico.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md b/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
index 0cce2183a..bc9905e15 100644
--- a/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
+++ b/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
@@ -3,8 +3,8 @@ title: 'El CMS permite la creación pero no la edición de carpetas con los mism
 id: q2Fvxfwv5MjAcqxb81avH
 status: PUBLISHED
 createdAt: 2022-04-26T14:09:30.508Z
-updatedAt: 2022-11-25T22:10:43.268Z
-publishedAt: 2022-11-25T22:10:43.268Z
+updatedAt: 2024-02-16T20:26:06.081Z
+publishedAt: 2024-02-16T20:26:06.081Z
 firstPublishedAt: 2022-04-26T14:09:31.061Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: el-cms-permite-la-creacion-pero-no-la-edicion-de-carpetas-con-los-mismos-nombres-que-los-predeterminados
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 566791
 ---
 
diff --git a/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md b/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md
index 4747e7eee..da92bb71d 100644
--- a/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md
+++ b/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md
@@ -20,7 +20,7 @@ internalReference:
 
 Al acceder al CMS a través del nuevo ambiente administrativo (My VTEX - `{AccountName}.myvtex.com/admin`), se muestra una página de error, no siendo posible acceder al CMS.
 
-![4JSc1cw](https://images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
+![4JSc1cw](//images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/cms-legacy-collections-timeout.md b/docs/known-issues/es/cms-legacy-collections-timeout.md
index 46161b5b5..0aa6162b3 100644
--- a/docs/known-issues/es/cms-legacy-collections-timeout.md
+++ b/docs/known-issues/es/cms-legacy-collections-timeout.md
@@ -3,8 +3,8 @@ title: 'CMS Legacy Collections Tiempo de espera'
 id: 3TgWP83kn8G8NClnUHmaoS
 status: PUBLISHED
 createdAt: 2022-02-25T12:33:00.051Z
-updatedAt: 2023-05-19T18:23:32.371Z
-publishedAt: 2023-05-19T18:23:32.371Z
+updatedAt: 2023-06-20T13:24:40.031Z
+publishedAt: 2023-06-20T13:24:40.031Z
 firstPublishedAt: 2022-02-25T12:33:00.399Z
 contentType: knownIssue
 productTeam: Catalog
@@ -18,37 +18,29 @@ internalReference: 434026
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
-
 A menudo, al intentar guardar los datos de un grupo de colecciones utilizando la aplicación de colecciones heredada, en la ruta /admin/a e intentando Guardar grupo, el usuario, en casos de catálogos grandes (gran cantidad de categorías, marcas, productos), se encontrará con un mensaje de error de tiempo de espera y no podrá guardar sus cambios.
 
 `{cuenta}.myvtex.com/admin/a/`
 
  ![](https://vtexhelp.zendesk.com/attachments/token/pBcpo1sWfBMio0mpL5iMc4Iek/?name=inline-1265713773.png)
 
-
-##
-
 ## Simulación
 
 
-1) Vaya a la aplicación CMS UI con una tienda que tenga una base de catálogo grande, por ejemplo, >10000 productos.
-2) Vaya a "Grupos de productos (Colecciones) y seleccione "_nuevo grupo_".
-3) Cree un grupo y luego seleccione algunas casillas en el formulario
-4) Intente guardar estos cambios
-5) Si la solicitud tarda más de 50 segundos en guardarse, lo que suele ocurrir en cuentas con gran cantidad de datos, la solicitud se detendrá y los datos no se guardarán.
-
+1. Vaya a la aplicación CMS UI con una tienda que tenga una base de catálogo grande, por ejemplo, >10000 productos.
+2. Vaya a "Grupos de productos (Colecciones) y seleccione "_nuevo grupo_".
+3. Cree un grupo y luego seleccione algunas casillas en el formulario
+4. Intente guardar estos cambios
+5. Si la solicitud tarda más de 50 segundos en guardarse, lo que suele ocurrir en cuentas con gran cantidad de datos, la solicitud se detendrá y los datos no se guardarán.
 
 
 ## Workaround
 
 
-Utilizando el nuevo administrador de cobros O utilizando nuestros puntos finales de la API de cobros: https://developers.vtex.com/vtex-rest-api/reference/collection-cms
-
-
-
+Utilizando el nuevo administrador de cobros O utilizando nuestros puntos finales de la [Collections API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection).
 
 
diff --git a/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md b/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
index 53e055712..6e41e47d6 100644
--- a/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
+++ b/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
@@ -3,8 +3,8 @@ title: 'La configuración del CMS no permite eliminar el valor del campo Unidad
 id: QVmSN1VuGQUiklZDkarEI
 status: PUBLISHED
 createdAt: 2022-03-11T13:49:28.490Z
-updatedAt: 2022-11-25T22:11:28.148Z
-publishedAt: 2022-11-25T22:11:28.148Z
+updatedAt: 2024-02-16T20:28:41.042Z
+publishedAt: 2024-02-16T20:28:41.042Z
 firstPublishedAt: 2022-03-11T13:49:28.850Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: la-configuracion-del-cms-no-permite-eliminar-el-valor-del-campo-unidad-de-masa
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 540756
 ---
 
diff --git a/docs/known-issues/es/cms-settings-role-not-working-as-expected.md b/docs/known-issues/es/cms-settings-role-not-working-as-expected.md
new file mode 100644
index 000000000..3452c7fa0
--- /dev/null
+++ b/docs/known-issues/es/cms-settings-role-not-working-as-expected.md
@@ -0,0 +1,57 @@
+---
+title: 'CMS Settings Role no funciona como se esperaba'
+id: 1xAUvtkD2gbvc3yaoYXT2d
+status: PUBLISHED
+createdAt: 2023-06-19T12:31:33.137Z
+updatedAt: 2023-06-19T12:31:33.699Z
+publishedAt: 2023-06-19T12:31:33.699Z
+firstPublishedAt: 2023-06-19T12:31:33.699Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: cms-settings-role-no-funciona-como-se-esperaba
+locale: es
+kiStatus: Backlog
+internalReference: 538706
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+CMS Settings Role no funciona como se esperaba. A veces el usuario no puede acceder al CMS incluso después de ser añadido al rol.
+Otro comportamiento inesperado es que otros módulos siguen estando disponibles para el rol CMS incluso sin los permisos necesarios.
+
+
+##
+
+## Simulación
+
+
+
+- Cree un rol en la aplicación Roles del Gestor de Licencias dando acceso únicamente a:
+  - Menú CMS en la barra superior;
+  - Ajustes CMS.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/fbpObVoVdnEYGeYjd3GDh9Qqf/?name=image.png)
+
+
+- Asocie este rol a un usuario;
+- Inicie sesión con este usuario e intente acceder al menú de configuración del CMS, no podrá.
+- Compruebe que los demás módulos siguen estando disponibles.
+
+
+
+## Workaround
+
+
+Para acceder al menú CMS, el usuario debe ser un Admin Super.
+
+
+
+
+
diff --git a/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md b/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md
index bf7346aa4..2215a0b04 100644
--- a/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md
+++ b/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md
@@ -3,8 +3,8 @@ title: 'Problemas con el menú desplegable al mostrar todos los elementos'
 id: 1iOlmwj8DvaxCQCmvyHQww
 status: PUBLISHED
 createdAt: 2022-05-23T19:39:49.204Z
-updatedAt: 2022-11-25T22:13:59.079Z
-publishedAt: 2022-11-25T22:13:59.079Z
+updatedAt: 2024-02-16T20:24:35.010Z
+publishedAt: 2024-02-16T20:24:35.010Z
 firstPublishedAt: 2022-05-23T19:39:49.609Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: problemas-con-el-menu-desplegable-al-mostrar-todos-los-elementos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 542091
 ---
 
diff --git a/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md b/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md
index 18ed48fb3..8e58a01bb 100644
--- a/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md
+++ b/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md
@@ -3,8 +3,8 @@ title: 'Recogidas no permite más de 1000 SKU por carga'
 id: 4XC2ZLCsBkQhexRB4YrNMn
 status: PUBLISHED
 createdAt: 2023-04-19T13:53:02.339Z
-updatedAt: 2023-04-19T13:53:02.926Z
-publishedAt: 2023-04-19T13:53:02.926Z
+updatedAt: 2023-10-10T13:31:27.610Z
+publishedAt: 2023-10-10T13:31:27.610Z
 firstPublishedAt: 2023-04-19T13:53:02.926Z
 contentType: knownIssue
 productTeam: Catalog
diff --git a/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md b/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
new file mode 100644
index 000000000..66019514b
--- /dev/null
+++ b/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
@@ -0,0 +1,49 @@
+---
+title: 'Las colecciones no funcionan en las páginas de resultados de búsqueda personalizadas en B2B Suite'
+id: 2O2UmKrMJHimDunDRbLBe
+status: PUBLISHED
+createdAt: 2024-06-03T22:13:10.775Z
+updatedAt: 2024-06-21T14:57:27.454Z
+publishedAt: 2024-06-21T14:57:27.454Z
+firstPublishedAt: 2024-06-03T22:13:11.591Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: las-colecciones-no-funcionan-en-las-paginas-de-resultados-de-busqueda-personalizadas-en-b2b-suite
+locale: es
+kiStatus: Backlog
+internalReference: 1043470
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las páginas de resultados de búsqueda personalizadas configuradas con el id de colección no funcionan cuando se asignan diferentes colecciones de productos a una organización.
+
+El comportamiento esperado al utilizar Colecciones es definir el surtido de productos que los usuarios de la organización verán en el escaparate, pero como las Organizaciones B2B también utilizan `productClusterId` en la búsqueda, al acceder a páginas de resultados de búsqueda personalizadas configuradas con un `productClusterId` diferente, los resultados de la búsqueda muestran productos de ambas colecciones.
+
+
+
+## Simulación
+
+
+
+- Configure una colección de productos para una organización;
+- Cree una página de resultados de búsqueda personalizada con una colección diferente;
+- Inicie sesión y acceda a la página de resultados de búsqueda personalizada; se muestran los productos de ambas colecciones.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/collections-dont-open-on-subaccounts.md b/docs/known-issues/es/collections-dont-open-on-subaccounts.md
new file mode 100644
index 000000000..26d036e23
--- /dev/null
+++ b/docs/known-issues/es/collections-dont-open-on-subaccounts.md
@@ -0,0 +1,47 @@
+---
+title: 'Los cobros no se abren en las subcuentas'
+id: Ly7eHGXdzg0aJLYF2c4eZ
+status: PUBLISHED
+createdAt: 2024-07-31T18:50:48.046Z
+updatedAt: 2024-07-31T18:50:49.007Z
+publishedAt: 2024-07-31T18:50:49.007Z
+firstPublishedAt: 2024-07-31T18:50:49.007Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: los-cobros-no-se-abren-en-las-subcuentas
+locale: es
+kiStatus: Backlog
+internalReference: 649948
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar abrir una colección en el módulo de nuevas colecciones de una subcuenta se devuelve un error "Lo sentimos, se ha producido un error desconocido".
+
+
+##
+
+## Simulación
+
+
+
+1. Introduzca una subcuenta;
+2. Ir al módulo de nuevos cobros;
+3. Intente abrir cualquier cobro;
+4. 4. Compruebe si se ha producido algún error.
+
+
+
+## Workaround
+
+
+
+Dado que el catálogo se comparte entre cuentas, abra la colección en la cuenta principal O utilice el antiguo módulo de colecciones en el CMS.
+
diff --git a/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md b/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md
new file mode 100644
index 000000000..f1d103140
--- /dev/null
+++ b/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md
@@ -0,0 +1,49 @@
+---
+title: 'La exportación de colecciones sólo muestra el primer SKU del producto inactivo'
+id: 7FegROKSwxpadN5NYVFR8M
+status: PUBLISHED
+createdAt: 2024-05-28T19:56:23.549Z
+updatedAt: 2024-05-28T19:56:24.303Z
+publishedAt: 2024-05-28T19:56:24.303Z
+firstPublishedAt: 2024-05-28T19:56:24.303Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-exportacion-de-colecciones-solo-muestra-el-primer-sku-del-producto-inactivo
+locale: es
+kiStatus: Backlog
+internalReference: 1040753
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza el módulo de colecciones y se intenta exportar registros, si el producto listado en una colección dada tiene todos sus skus configurados como inactivos, la hoja exportada sólo listará 1 de los skus del producto, en lugar de todos.
+
+
+##
+
+## Simulación
+
+
+1 - Obtenga un producto que tenga varios skus y configure todos ellos como inactivos.
+2 - Insértelos en una colección de catálogo /admin/collections
+3 - utilizar la función de exportación
+4 - sólo el SKU superior del producto aparecerá en la hoja, en lugar de todos
+
+
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index 780c9ea58..11c46ec8d 100644
--- a/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -3,8 +3,8 @@ title: 'El campo de las colecciones siempre aparece como "Igual a" en el formula
 id: 2NPEh7LZkrpO0gf802I7HZ
 status: PUBLISHED
 createdAt: 2022-11-11T21:18:53.386Z
-updatedAt: 2022-11-25T22:11:31.863Z
-publishedAt: 2022-11-25T22:11:31.863Z
+updatedAt: 2024-02-16T20:27:37.566Z
+publishedAt: 2024-02-16T20:27:37.566Z
 firstPublishedAt: 2022-11-11T21:18:54.385Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: el-campo-de-las-colecciones-siempre-aparece-como-igual-a-en-el-formulario-de-audiencia-de-la-campana
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 697168
 ---
 
diff --git a/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md b/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md
new file mode 100644
index 000000000..844c964b3
--- /dev/null
+++ b/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md
@@ -0,0 +1,48 @@
+---
+title: 'Las colecciones nombradas con caracteres especiales no se pueden exportar'
+id: 516zuwek2Gfwd0U99si2XU
+status: PUBLISHED
+createdAt: 2023-08-22T12:46:46.230Z
+updatedAt: 2023-12-12T14:21:31.164Z
+publishedAt: 2023-12-12T14:21:31.164Z
+firstPublishedAt: 2023-08-22T12:46:46.895Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-colecciones-nombradas-con-caracteres-especiales-no-se-pueden-exportar
+locale: es
+kiStatus: Backlog
+internalReference: 683343
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera que una colección pueda ser exportada en el admin. Sin embargo, las colecciones con nombres que contienen símbolos como `$` , `+` o `,` no se pueden exportar.
+
+
+##
+
+## Simulación
+
+
+
+- Crear una colección con `$` , `+` o `,` en el nombre
+- Intente exportar la colección
+- Aparecerá un error en el admin
+
+
+
+## Workaround
+
+
+Elimine el carácter
+
+
+
+
diff --git a/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md b/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md
new file mode 100644
index 000000000..d6ac05511
--- /dev/null
+++ b/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md
@@ -0,0 +1,55 @@
+---
+title: 'La página Colecciones en Detalles de la organización sólo muestra 20 colecciones'
+id: 1NL46GlhANQoa6IzGSSwdS
+status: PUBLISHED
+createdAt: 2023-08-31T20:02:37.675Z
+updatedAt: 2024-04-23T21:35:34.440Z
+publishedAt: 2024-04-23T21:35:34.440Z
+firstPublishedAt: 2023-08-31T20:02:38.351Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: la-pagina-colecciones-en-detalles-de-la-organizacion-solo-muestra-20-colecciones
+locale: es
+kiStatus: Fixed
+internalReference: 891511
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La página Colecciones en Detalles de la Organización muestra sólo 20 colecciones incluso después de cambiar la cantidad de filas en la parte inferior de la página.
+
+
+##
+
+## Simulación
+
+
+
+- Asegúrese de que tiene más de 20 colecciones activas;
+- En el administrador, vaya a la página Organizaciones B2B, seleccione una organización;
+- Vaya a la pestaña Colecciones; verá sólo 20 colecciones disponibles.
+
+
+
+## Workaround
+
+
+Si la colección deseada no aparece en la pestaña Colecciones, asígnela utilizando GraphQL IDE:
+
+- Acceda a GraphQL IDE;
+- Seleccione la aplicación `vtex.b2b-organizations-graphql`;
+- Utilice la siguiente mutación y añada los valores de `id`, `name`, `collections.id` y `collections.name`.
+
+    mutation { updateOrganization ( id: "" name: "" status: "active" collections: [{ id: "" name: "" }] ){ status message }}
+
+
+
+
+
diff --git a/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md b/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md
new file mode 100644
index 000000000..26cd13b92
--- /dev/null
+++ b/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md
@@ -0,0 +1,50 @@
+---
+title: 'El activador de cobros no funciona como se esperaba en los Descuentos Progresivos'
+id: 78b9yQnTm1bxgOM2cfMlql
+status: PUBLISHED
+createdAt: 2023-11-06T16:42:53.081Z
+updatedAt: 2023-11-06T16:42:53.722Z
+publishedAt: 2023-11-06T16:42:53.722Z
+firstPublishedAt: 2023-11-06T16:42:53.722Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: el-activador-de-cobros-no-funciona-como-se-esperaba-en-los-descuentos-progresivos
+locale: es
+kiStatus: Backlog
+internalReference: 930849
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al crear una promoción de descuento progresivo el cliente puede establecer el activador por colección, por una lista de SKU o por ambas.
+
+Sin embargo, cuando ambos están configurados en la promoción, la condición que debería ser o bien la colección o bien la lista de SKU desencadena la promoción se comporta en realidad como si sólo la lista de SKU fuera el desencadenante.
+
+
+
+## Simulación
+
+
+
+1. Crear una promoción de descuento progresivo;
+2. En los activadores de la promoción, seleccione una colección y una lista de SKU con un sku que no pertenezca a la colección;
+3. 3. Compruebe en el carrito que la promoción sólo está activa cuando la SKU que pertenece a la lista de SKU está presente.
+
+
+
+## Workaround
+
+
+Para activar ambos activadores al mismo tiempo no hay solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md b/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
index 75917fc23..97268741b 100644
--- a/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
+++ b/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
@@ -1,16 +1,16 @@
 ---
-title: 'Pedidos completos con error de creación por fallo en gatewaycallbak'
+title: 'Pedidos completos con error en creación por fallo en gatewaycallbak'
 id: 2qVa686QBsvkgXY8wwmc8Y
 status: PUBLISHED
 createdAt: 2022-05-04T19:28:00.775Z
-updatedAt: 2022-11-25T21:52:28.991Z
-publishedAt: 2022-11-25T21:52:28.991Z
+updatedAt: 2024-04-04T16:46:47.602Z
+publishedAt: 2024-04-04T16:46:47.602Z
 firstPublishedAt: 2022-05-04T19:28:01.142Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: pedidos-completos-con-error-de-creacion-por-fallo-en-gatewaycallbak
+slug: pedidos-completos-con-error-en-creacion-por-fallo-en-gatewaycallbak
 locale: es
 kiStatus: Backlog
 internalReference: 416936
@@ -23,21 +23,31 @@ internalReference: 416936
 </div>
 
 
-Hemos recibido algunas consultas sobre pedidos que estaban atascados en el estado de pago aprobado, pero que ya habían sido aprobados, lo que no debería ocurrir en el flujo normal de pedidos.
+Hemos recibido algunas consultas sobre pedidos que estaban atascados en el estado de pago aprobado pero que ya lo estaban, lo que no debería ocurrir en el flujo normal de pedidos.
 
 Basándonos en el análisis de los casos, entendemos que una posible ocurrencia de este suceso fue;
 
-El pedido de marketplace fue creado incompleto, el pedido de marketplace recibe la llamada de gatewaycallback y, en este momento, se produce un fallo, y esto hace que se inicie un proceso de cancelación del pedido, pero el pedido de marketppace recibe una segunda llamada de gatewaycallback que hace que el pedido esté autorizado y completo, evitando así que se cancele la transacción, y este escenario genera un pedido completo (marketplace / checkout), pero con un error de creación y el pedido fullfiment cancelado, lo que podría evitarse implementando una validación en gatewaycallback para no proceder con pedidos incompletos.
+El pedido de marketplace fue creado incompleto, el pedido de marketplace recibe la llamada de gatewaycallback y, en este momento, se produce un fallo, y esto hace que se inicie un proceso de cancelación del pedido, pero el pedido de marketppace recibe una segunda llamada de gatewaycallback que hace que el pedido sea autorizado y completo, evitando así que la transacción sea cancelada, y este escenario genera un pedido completo (marketplace / checkout), pero con un error de creación y el pedido fullfiment cancelado, lo que podría evitarse implementando una validación en gatewaycallback para no proceder con pedidos incompletos.
+En algunos casos, el pedido del vendedor puede no ser cancelado.
 
 
+##
 
+## Simulación
 
 
-## Simulación
+
+No podemos simular debido a la complejidad del flujo, el análisis debe hacerse teniendo en cuenta los datos reportados aquí.
+
 
 
 
 ## Workaround
 
 
+En los casos en que el pedido del Vendedor no se cancela, debe cancelar el pedido manualmente, o esperar el plazo de 30 días.
+
+
+
+
 
diff --git a/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md b/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
index 44d8064f7..0511d5bfc 100644
--- a/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
+++ b/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
@@ -3,8 +3,8 @@ title: 'Componente cajón no funciona cuando se implementa en el producto-resume
 id: 75145kfQE8swAef57Yr4Aj
 status: PUBLISHED
 createdAt: 2023-05-29T13:22:57.856Z
-updatedAt: 2023-05-29T13:22:58.422Z
-publishedAt: 2023-05-29T13:22:58.422Z
+updatedAt: 2024-02-19T18:51:53.024Z
+publishedAt: 2024-02-19T18:51:53.024Z
 firstPublishedAt: 2023-05-29T13:22:58.422Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md b/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
index 5f1c19df2..d6ba76598 100644
--- a/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
+++ b/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
@@ -3,8 +3,8 @@ title: 'El selector de vendedores de componentes puede presentar incoherencias e
 id: 2agLvjXgT76ngdu3YsA6uh
 status: PUBLISHED
 createdAt: 2022-09-14T22:26:22.177Z
-updatedAt: 2022-11-25T22:13:07.124Z
-publishedAt: 2022-11-25T22:13:07.124Z
+updatedAt: 2024-02-16T20:28:08.976Z
+publishedAt: 2024-02-16T20:28:08.976Z
 firstPublishedAt: 2022-09-14T22:26:22.762Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: el-selector-de-vendedores-de-componentes-puede-presentar-incoherencias-en-los-precios-de-entregaenvio
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 658452
 ---
 
diff --git a/docs/known-issues/es/components-in-a-kit-with-the-same-price.md b/docs/known-issues/es/components-in-a-kit-with-the-same-price.md
new file mode 100644
index 000000000..2e5e0caba
--- /dev/null
+++ b/docs/known-issues/es/components-in-a-kit-with-the-same-price.md
@@ -0,0 +1,50 @@
+---
+title: 'Componentes en un kit con el mismo precio'
+id: 6TIDKJ6nEGUu3E5bzAea65
+status: PUBLISHED
+createdAt: 2024-02-26T19:53:43.754Z
+updatedAt: 2024-02-26T19:53:45.011Z
+publishedAt: 2024-02-26T19:53:45.011Z
+firstPublishedAt: 2024-02-26T19:53:45.011Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: componentes-en-un-kit-con-el-mismo-precio
+locale: es
+kiStatus: Backlog
+internalReference: 989371
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los componentes de un kit tienen el mismo precio cuando se configura una promoción de regalo y la realiza un vendedor habitual.
+
+
+##
+
+## Simulación
+
+
+
+- Registrar un kit;
+- Establecer una promoción de regalo;
+- Añadir un artículo a la cesta utilizando un vendedor normal;
+- Realizar el pedido; El precio de los componentes será el mismo.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/confirmed-order-email-not-being-sent.md b/docs/known-issues/es/confirmed-order-email-not-being-sent.md
index 2c98845f8..cd30f7b00 100644
--- a/docs/known-issues/es/confirmed-order-email-not-being-sent.md
+++ b/docs/known-issues/es/confirmed-order-email-not-being-sent.md
@@ -3,8 +3,8 @@ title: 'No se envía el correo electrónico de confirmación del pedido'
 id: 4RelMFApLldLtf0GxhYzdt
 status: PUBLISHED
 createdAt: 2023-03-10T22:07:59.908Z
-updatedAt: 2023-05-29T20:07:11.271Z
-publishedAt: 2023-05-29T20:07:11.271Z
+updatedAt: 2023-08-28T14:53:51.322Z
+publishedAt: 2023-08-28T14:53:51.322Z
 firstPublishedAt: 2023-03-10T22:08:01.026Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md b/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
new file mode 100644
index 000000000..adcd872a4
--- /dev/null
+++ b/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
@@ -0,0 +1,53 @@
+---
+title: 'Conflicto entre especificaciones con el mismo nombre en la Búsqueda Inteligente'
+id: 1TcMLTNMMGqjgbGArywSeh
+status: PUBLISHED
+createdAt: 2023-11-10T00:13:18.275Z
+updatedAt: 2024-06-24T13:48:09.391Z
+publishedAt: 2024-06-24T13:48:09.391Z
+firstPublishedAt: 2023-11-10T00:13:18.980Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: conflicto-entre-especificaciones-con-el-mismo-nombre-en-la-busqueda-inteligente
+locale: es
+kiStatus: Fixed
+internalReference: 933958
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Múltiples especificaciones con el mismo nombre son agrupadas en la misma _"faceta"_ por la Búsqueda Inteligente, lo que puede ser un problema si tienen diferentes configuraciones.
+
+Algunos atributos que pueden verse afectados son el filtro, los conmutadores oculto e indexado/buscable, el tipo de campo y la posición del valor. No hay diferencia entre ser una especificación de producto o de SKU.
+
+No es posible saber qué propiedad tendrá prioridad sobre la otra.
+
+
+##
+
+## Simulación
+
+
+Para una tienda con:
+- una especificación llamada "foo" (ID 1) establecida como filtro (para aparecer en el escaparate) y con el valor "bar" para un producto;
+- otra especificación llamada "foo" (pero ID 2), que no es un filtro, y con el valor "baz" para el mismo u otro producto.
+
+El escaparate puede mostrar un filtro de búsqueda para la faceta/especificación "foo" con los valores "bar" y "baz" o incluso ocultar todo el filtro.
+
+
+
+## Workaround
+
+
+Aunque el módulo Catálogo no bloquea los nombres de especificación repetidos, este uso debe considerarse incorrecto.
+
+
+
+
diff --git a/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md b/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
new file mode 100644
index 000000000..1bdc587f3
--- /dev/null
+++ b/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
@@ -0,0 +1,54 @@
+---
+title: 'Error de consola [Sólo informe] - Se ha denegado la aplicación del estilo en línea porque infringe la siguiente seguridad de contenido'
+id: mix75F8F7a7D4iTWyHLyM
+status: PUBLISHED
+createdAt: 2024-04-16T10:30:41.610Z
+updatedAt: 2024-04-16T10:30:42.934Z
+publishedAt: 2024-04-16T10:30:42.934Z
+firstPublishedAt: 2024-04-16T10:30:42.934Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-de-consola-solo-informe-se-ha-denegado-la-aplicacion-del-estilo-en-linea-porque-infringe-la-siguiente-seguridad-de-contenido
+locale: es
+kiStatus: Backlog
+internalReference: 1017370
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Tenemos algunos logs en la consola informando de bloqueos de script debido a restricciones a través de la cabecera CSP.
+Las llamadas de estilo inline al host io2.vtex.com tienen este registro bloqueante porque no se libera en el CSP del host anterior, generando así mensajes de error en la consola.
+
+
+    [Sólo informe] Se ha denegado la ejecución del script inline porque infringe la siguiente directiva de la Política de seguridad de contenidos: "script-src 'self' https://io.vtex.com.br https://*.vtex.com.br https://*.vtexpayments.com.br https://*.myvtex.com https://*.vtexcommercestable.com.br https://*.vtexcommercebeta.com.br https://*.vteximg.com.br https://*.vtexassets.com 'report-sample'". Se requiere la palabra clave 'unsafe-inline', un hash ('sha256-AdqydPwVZwz4OteEhuvEEzsFBDTM/J6q0/ZlIWf9Wr4='), o un nonce ('nonce-...') para permitir la ejecución en línea.
+
+
+
+
+##
+
+## Simulación
+
+
+
+1. Ir a la caja de la tienda;
+2. Abra la consola y compruebe los mensajes de informe;
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/cookie-broken-the-apisessions.md b/docs/known-issues/es/cookie-broken-the-apisessions.md
index 4a02cd879..404795569 100644
--- a/docs/known-issues/es/cookie-broken-the-apisessions.md
+++ b/docs/known-issues/es/cookie-broken-the-apisessions.md
@@ -3,8 +3,8 @@ title: 'Cookie rota la API/Sesiones'
 id: 5knDMVZabZRYaEtITjkDbE
 status: PUBLISHED
 createdAt: 2023-03-27T19:54:42.696Z
-updatedAt: 2023-03-27T19:54:43.232Z
-publishedAt: 2023-03-27T19:54:43.232Z
+updatedAt: 2024-03-20T20:34:36.743Z
+publishedAt: 2024-03-20T20:34:36.743Z
 firstPublishedAt: 2023-03-27T19:54:43.232Z
 contentType: knownIssue
 productTeam: Identity
diff --git a/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md b/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
new file mode 100644
index 000000000..3dbed70cb
--- /dev/null
+++ b/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
@@ -0,0 +1,49 @@
+---
+title: 'El desplegable de centros de coste sólo muestra 25 opciones en B2B Admin Clientes'
+id: 1ynkpOppe8iqbwB3CF0euV
+status: PUBLISHED
+createdAt: 2023-10-17T23:11:29.713Z
+updatedAt: 2023-10-17T23:11:30.187Z
+publishedAt: 2023-10-17T23:11:30.187Z
+firstPublishedAt: 2023-10-17T23:11:30.187Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: el-desplegable-de-centros-de-coste-solo-muestra-25-opciones-en-b2b-admin-clientes
+locale: es
+kiStatus: Backlog
+internalReference: 921115
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al dar de alta un nuevo cliente mediante el Admin Clientes B2B, el desplegable del centro de coste sólo muestra 25 opciones.
+
+
+##
+
+## Simulación
+
+
+
+- Registrar más de 25 centros de coste para una organización;
+- Acceda a Clientes B2B a través de admin;
+- Haga clic en "Nuevo" y "Añadir nuevo" en la parte inferior de la ventana emergente;
+- Al seleccionar el centro de coste, el desplegable sólo muestra 25 opciones.
+
+
+
+## Workaround
+
+
+Utilice Organizaciones B2B para añadir nuevos usuarios para organizaciones con más de 25 centros de coste.
+
+
+
+
diff --git a/docs/known-issues/es/country-field-as-null-in-invoicedata.md b/docs/known-issues/es/country-field-as-null-in-invoicedata.md
new file mode 100644
index 000000000..12a6b5e13
--- /dev/null
+++ b/docs/known-issues/es/country-field-as-null-in-invoicedata.md
@@ -0,0 +1,48 @@
+---
+title: 'Campo país como null en invoiceData'
+id: 6TbzOvnKw5Uhcr1C5Jrneb
+status: PUBLISHED
+createdAt: 2023-12-13T15:53:26.073Z
+updatedAt: 2023-12-19T21:22:09.038Z
+publishedAt: 2023-12-19T21:22:09.038Z
+firstPublishedAt: 2023-12-13T15:53:26.800Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: campo-pais-como-null-en-invoicedata
+locale: es
+kiStatus: Fixed
+internalReference: 382175
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El campo País en invoiceData puede ser nulo si se envía vía API o hay una dirección de factura en el Sistema de Perfiles con el país como nulo, por lo que se crearán pedidos con datos incompletos en invoiceData.
+
+
+##
+
+## Simulación
+
+
+
+- Monta un carrito con artículos;
+- Envía la facturaData sin el campo país rellenado vía API;
+- Finaliza la compra.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md b/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
index 980fd04ac..f367f1c01 100644
--- a/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
+++ b/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
@@ -3,8 +3,8 @@ title: 'El selector de país para la dirección de facturación mientras está e
 id: 5lHG60ATBiCdPBQnE1CEuP
 status: PUBLISHED
 createdAt: 2022-05-24T13:38:13.922Z
-updatedAt: 2022-11-25T21:51:33.189Z
-publishedAt: 2022-11-25T21:51:33.189Z
+updatedAt: 2024-02-16T20:29:40.951Z
+publishedAt: 2024-02-16T20:29:40.951Z
 firstPublishedAt: 2022-05-24T13:38:14.583Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-selector-de-pais-para-la-direccion-de-facturacion-mientras-esta-en-modo-internacional-permanece-restringido-a-los-paises-de-entrega
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 335581
 ---
 
diff --git a/docs/known-issues/es/coupons-created-as-archived-temporarrily.md b/docs/known-issues/es/coupons-created-as-archived-temporarrily.md
new file mode 100644
index 000000000..9909da47d
--- /dev/null
+++ b/docs/known-issues/es/coupons-created-as-archived-temporarrily.md
@@ -0,0 +1,49 @@
+---
+title: 'Cupones creados como archivados temporalmente'
+id: 783FJICQzATVkJ2uPgk9Mq
+status: PUBLISHED
+createdAt: 2023-09-01T13:34:21.842Z
+updatedAt: 2023-09-01T13:34:22.607Z
+publishedAt: 2023-09-01T13:34:22.607Z
+firstPublishedAt: 2023-09-01T13:34:22.607Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: cupones-creados-como-archivados-temporalmente
+locale: es
+kiStatus: Backlog
+internalReference: 892041
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, cuando se crea un cupón, la UI/API muestra que está archivado durante unos minutos (~2) cuando en realidad (en la base de datos de precios), el cupón está activo.
+
+Después de unos minutos, el cupón muestra sus datos correctos.
+
+Es importante señalar que esto no afecta a la información del cupón "real", incluso cuando se muestra incorrectamente como "archivado" en la interfaz de usuario debido a este problema, será utilizable en la caja.
+
+
+
+## Simulación
+
+
+Simplemente creando un cupón y comprobando su daata ya se muestra como archivado.
+
+
+
+## Workaround
+
+
+No hay más solución que esperar un poco.
+
+
+
+
+
diff --git a/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md b/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md
new file mode 100644
index 000000000..3cc064166
--- /dev/null
+++ b/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md
@@ -0,0 +1,48 @@
+---
+title: 'La API de creación de productos no envía valores nulos como fecha de lanzamiento.'
+id: 6IjwYVm9SdNEtW9aNYkSrj
+status: PUBLISHED
+createdAt: 2024-04-29T15:10:44.454Z
+updatedAt: 2024-04-29T15:10:45.337Z
+publishedAt: 2024-04-29T15:10:45.337Z
+firstPublishedAt: 2024-04-29T15:10:45.337Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-api-de-creacion-de-productos-no-envia-valores-nulos-como-fecha-de-lanzamiento
+locale: es
+kiStatus: Backlog
+internalReference: 1024207
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar las API de creación o actualización de productos en la aplicación de catálogo: https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product y enviar el campo releaseDate como null, en su valor, se crea con la fecha actual en su lugar.
+
+
+##
+
+## Simulación
+
+
+1 - Crea o actualiza un nuevo producto, en tu tienda, a través de la API mencionada, pasando, en su cuerpo de petición, el campo releaseDate como null.
+2 - Acceda a la interfaz de administración del catálogo o utilice un GET en la misma ruta de la API para obtener los datos enviados.
+3 - El campo releaseDate mostrará el valor de la fecha enviada en lugar de un null.
+
+
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md b/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
new file mode 100644
index 000000000..1c71a4b93
--- /dev/null
+++ b/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
@@ -0,0 +1,50 @@
+---
+title: 'La creación de un canal de ventas regionalizado con una encuadernación ya utilizada no actualiza el saldo de existencias del artículo.'
+id: 7CqZPslfGY8mTmBLuWe5SQ
+status: PUBLISHED
+createdAt: 2024-03-22T19:39:26.469Z
+updatedAt: 2024-07-01T18:49:34.061Z
+publishedAt: 2024-07-01T18:49:34.061Z
+firstPublishedAt: 2024-03-22T19:39:27.432Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-creacion-de-un-canal-de-ventas-regionalizado-con-una-encuadernacion-ya-utilizada-no-actualiza-el-saldo-de-existencias-del-articulo
+locale: es
+kiStatus: No Fix
+internalReference: 1005112
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Para las cuentas regionalizadas el sistema de índices filtra por los canales de venta regionalizados el stockbalance que debe aparecer, para no mostrar vinculaciones de ventas que no están regionalizadas.
+
+Si es necesario regionalizar un nuevo canal en una vinculación que ya está en producción, la indexación no se activará. Causando algunas inconsistencias en la disponibilidad de los productos.
+
+
+##
+
+## Simulación
+
+
+
+1. Crear un canal de ventas regionalizado en una encuadernación de producción;
+2. Compruebe si las existencias y la disponibilidad son coherentes con todos los productos.
+
+
+
+## Workaround
+
+
+Forzar un reindexado con stockSimulation. Actualizar stock por ejemplo.
+
+
+
+
+
diff --git a/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md b/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
new file mode 100644
index 000000000..93a135cbe
--- /dev/null
+++ b/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
@@ -0,0 +1,51 @@
+---
+title: 'Crear y eliminar un gran número de redirecciones rompe la página de redirecciones.'
+id: 5uFuid4a5f7uiRVW9LdT5Q
+status: PUBLISHED
+createdAt: 2024-04-02T19:45:07.540Z
+updatedAt: 2024-04-02T19:45:08.762Z
+publishedAt: 2024-04-02T19:45:08.762Z
+firstPublishedAt: 2024-04-02T19:45:08.762Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: crear-y-eliminar-un-gran-numero-de-redirecciones-rompe-la-pagina-de-redirecciones
+locale: es
+kiStatus: Backlog
+internalReference: 1010392
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Tratar con una cantidad masiva de redirecciones puede romper la página de la interfaz de usuario. Si tiene muchas redirecciones o necesita borrar una gran cantidad de redirecciones esto puede llevar a un error en el que la página de la interfaz de usuario se carga para siempre y nunca devuelve la información de las redirecciones. Creemos que esto puede ocurrir porque cuando borramos una gran cantidad de redirecciones las primeras páginas de la consulta `listRedirects` están en blanco y la interfaz de usuario buscará estas primeras páginas para cargar las primeras redirecciones y nunca las encontrará.
+
+Esto también puede afectar a la importación/exportación CLI.
+
+
+##
+
+## Simulación
+
+
+
+- Crear una gran cantidad de redirecciones
+- Pruebe a borrarlas (a través de la interfaz de usuario o utilizando el rewriter)
+- Al volver a la página de la interfaz de usuario, las redirecciones no se cargarán.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md b/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
new file mode 100644
index 000000000..95b00d8b3
--- /dev/null
+++ b/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
@@ -0,0 +1,51 @@
+---
+title: 'Creación de redirecciones erróneas que contienen caracteres/consultas que no deberían cargarse la carga/descarga del csv a través de la CLI no funciona'
+id: 6ShJSvo6g8ZJFaejSo0gx3
+status: PUBLISHED
+createdAt: 2024-01-25T19:00:17.586Z
+updatedAt: 2024-01-25T19:00:18.204Z
+publishedAt: 2024-01-25T19:00:18.204Z
+firstPublishedAt: 2024-01-25T19:00:18.204Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: creacion-de-redirecciones-erroneas-que-contienen-caracteresconsultas-que-no-deberian-cargarse-la-cargadescarga-del-csv-a-traves-de-la-cli-no-funciona
+locale: es
+kiStatus: No Fix
+internalReference: 971936
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Después de crear redirecciones erróneas que contienen caracteres que no deben ser subidos: ie.: #, consultas, o redirecciones que deberían ser creadas a nivel de servidor, la carga/descarga masiva del csv a través del CLI ya no funciona.
+
+
+##
+
+## Simulación
+
+
+Crear una redirección para una consulta por ejemplo: /?binding=XXXXX
+Borra la redirección por el IDE de graphql (no podrás borrarla de otra forma)
+Intenta descargar o subir el CSV de las redirecciones a través del CLI y querrás poder hacerlo.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/etn94WlrSAYOFFj0rZfVwoowE/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+Actualmente no hay solución para esto y la descarga masiva CLI será inutilizable.
+
+
+
+
+
diff --git a/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md b/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md
new file mode 100644
index 000000000..ff50f2203
--- /dev/null
+++ b/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md
@@ -0,0 +1,46 @@
+---
+title: 'La composición de los criterios no se devuelve en la interfaz de búsqueda explicada'
+id: 5IyEZe5GBlt732g0rbU5T4
+status: PUBLISHED
+createdAt: 2023-06-29T15:05:18.815Z
+updatedAt: 2023-06-29T15:05:19.578Z
+publishedAt: 2023-06-29T15:05:19.578Z
+firstPublishedAt: 2023-06-29T15:05:19.578Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: la-composicion-de-los-criterios-no-se-devuelve-en-la-interfaz-de-busqueda-explicada
+locale: es
+kiStatus: Backlog
+internalReference: 852898
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se busca un término en el que la respuesta es un solo producto, ese producto no tendrá la composición de criterios que aparece en la pantalla de la búsqueda explicada.
+
+
+##
+
+## Simulación
+
+
+Al intentar abrir la búsqueda explicada y buscar un término en el que la respuesta sea sólo un producto, ese producto no tendrá su composición de criterios en la pantalla.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/crm-error-when-searching-with-spaces.md b/docs/known-issues/es/crm-error-when-searching-with-spaces.md
index 63cb94683..7e27c6371 100644
--- a/docs/known-issues/es/crm-error-when-searching-with-spaces.md
+++ b/docs/known-issues/es/crm-error-when-searching-with-spaces.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumario
 
-El usuario recibe un mensaje de error al buscar un documento con un atributo que contenga espacio [Screen Shot 2018-12-26 at 14.38.55](https://images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
+El usuario recibe un mensaje de error al buscar un documento con un atributo que contenga espacio [Screen Shot 2018-12-26 at 14.38.55](//images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
 Ejemplo: Buscando/filtrando por el campo "Ciudad" con el atributo "Rio de Janeiro" producirá un mensaje de error.
 
 
@@ -36,7 +36,7 @@ Ejemplo: Buscando/filtrando por el campo "Ciudad" con el atributo "Rio de Janeir
 
 ## Workaround
 
-![Screen Shot 2018-12-26 at 14.40.03](https://images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
+![Screen Shot 2018-12-26 at 14.40.03](//images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
 Felizmente hay una alternativa simple que no necesita el uso de API.
 Al hacer clic en "Todos" en el menú desplegable, la misma búsqueda puede realizarse sin causar error.
 
diff --git a/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md b/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md
new file mode 100644
index 000000000..f0c99f4b0
--- /dev/null
+++ b/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md
@@ -0,0 +1,50 @@
+---
+title: 'El símbolo de moneda no sigue el lenguaje admin'
+id: 7gEGdkDSbRCtk2Q1u2nW6k
+status: PUBLISHED
+createdAt: 2024-03-15T19:37:45.395Z
+updatedAt: 2024-03-15T19:40:56.682Z
+publishedAt: 2024-03-15T19:40:56.682Z
+firstPublishedAt: 2024-03-15T19:37:46.387Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: el-simbolo-de-moneda-no-sigue-el-lenguaje-admin
+locale: es
+kiStatus: Backlog
+internalReference: 1000915
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario accede a la pantalla de configuración del carrito en la zona de pedidos (`https://{accountname}}.myvtex.com/admin/checkout/#/configurations )` el símbolo de la moneda sigue las convenciones de la configuración regional indicada por el admin, el intercambio de este símbolo se realiza siempre que el admin indica una configuración regional diferente, sin embargo según nuestro análisis este intercambio está fallando en determinados momentos, provocando que el símbolo de la moneda indicado sea el predeterminado de la página que en este caso es R$.
+
+
+##
+
+## Simulación
+
+
+
+
+- Inicie sesión en admin
+- Vaya a https://.myvtex.com/admin/checkout/#/configurations
+- Cambie la configuración regional a PT y vuelva a EN;
+- Actualice la página y verá que el símbolo de moneda sigue siendo R$;
+
+
+
+## Workaround
+
+
+Actualmente no tenemos una solución para este caso, pero no afecta al funcionamiento de la tienda, ya que el símbolo de moneda en esta área es sólo visual y no tiene ningún impacto operativo en la tienda.
+
+
+
+
diff --git a/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md b/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md
new file mode 100644
index 000000000..9fe8de218
--- /dev/null
+++ b/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md
@@ -0,0 +1,47 @@
+---
+title: 'Mapeador de atributos personalizado Mercado Livre'
+id: 4A7inX7nFte4jRhZRLkPRO
+status: PUBLISHED
+createdAt: 2023-12-12T09:59:40.945Z
+updatedAt: 2024-02-16T20:26:22.091Z
+publishedAt: 2024-02-16T20:26:22.091Z
+firstPublishedAt: 2023-12-12T09:59:41.722Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mapeador-de-atributos-personalizado-mercado-livre
+locale: es
+kiStatus: No Fix
+internalReference: 521197
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+En la nueva pantalla del mapeador, no tenemos la opción de crear un atributo personalizado en MELI.
+
+
+##
+
+## Simulación
+
+
+
+Dentro de la pantalla del mapeador, falta el atributo personalizado que teníamos en la hoja de cálculo.
+
+
+
+## Workaround
+
+
+Actualmente no hay solución disponible, sólo se permite crear un valor personalizado dentro del atributo, pero no un atributo personalizado.
+
+
+
+
diff --git a/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md b/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
new file mode 100644
index 000000000..406730dc4
--- /dev/null
+++ b/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
@@ -0,0 +1,49 @@
+---
+title: 'Elementos personalizados en cms heredados no funcionan con más de un HTML'
+id: 6hGraRq2ffsw5c3jJ8nwh0
+status: PUBLISHED
+createdAt: 2023-07-31T16:35:04.392Z
+updatedAt: 2023-07-31T16:35:05.018Z
+publishedAt: 2023-07-31T16:35:05.018Z
+firstPublishedAt: 2023-07-31T16:35:05.018Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: elementos-personalizados-en-cms-heredados-no-funcionan-con-mas-de-un-html
+locale: es
+kiStatus: Backlog
+internalReference: 871480
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se crea un elemento personalizado con más de un elemento HTML, sólo se carga el primero en la plantilla.
+
+
+##
+
+## Simulación
+
+
+
+1. Crear un elemento personalizado con tipo HTML;
+2. Crea al menos 2 códigos html sobre este elemento personalizado;
+3. Compruebe que la plantilla que tiene este elemento personalizado sólo carga el primer HTML.
+
+
+
+## Workaround
+
+
+Reúne todos los htmls en un solo elemento sobre el elemento personalizado.
+
+
+
+
+
diff --git a/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md b/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
index 1010df35b..24937ca5b 100644
--- a/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
+++ b/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
@@ -3,8 +3,8 @@ title: 'La imagen en miniatura del vídeo personalizado no se muestra en la vers
 id: 5d71mBz4kXdwX7AhspYhit
 status: PUBLISHED
 createdAt: 2022-03-21T17:51:55.027Z
-updatedAt: 2022-11-25T21:54:30.917Z
-publishedAt: 2022-11-25T21:54:30.917Z
+updatedAt: 2024-07-01T18:48:03.005Z
+publishedAt: 2024-07-01T18:48:03.005Z
 firstPublishedAt: 2022-03-21T17:51:55.483Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: la-imagen-en-miniatura-del-video-personalizado-no-se-muestra-en-la-version-movil
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 412632
 ---
 
diff --git a/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md b/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
index 50286ec4e..14a22d5f9 100644
--- a/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
+++ b/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
@@ -3,8 +3,8 @@ title: 'El estado de las facturas de crédito de los clientes en la página MyCr
 id: 413knN4Gtk9GuZV5zFlw7k
 status: PUBLISHED
 createdAt: 2022-03-27T17:49:32.464Z
-updatedAt: 2022-11-25T22:06:46.582Z
-publishedAt: 2022-11-25T22:06:46.582Z
+updatedAt: 2024-02-16T20:25:28.872Z
+publishedAt: 2024-02-16T20:25:28.872Z
 firstPublishedAt: 2022-03-27T17:49:33.246Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: el-estado-de-las-facturas-de-credito-de-los-clientes-en-la-pagina-mycredits-no-es-correcto
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 369457
 ---
 
diff --git a/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
new file mode 100644
index 000000000..71e44b14f
--- /dev/null
+++ b/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -0,0 +1,46 @@
+---
+title: 'Se pierde la información del cliente cuando tiene algún pedido con "profileErrorOnLoading"'
+id: 7B0eutLBOCKOun4iwALVpq
+status: PUBLISHED
+createdAt: 2023-06-27T12:51:33.790Z
+updatedAt: 2023-06-27T12:51:34.237Z
+publishedAt: 2023-06-27T12:51:34.237Z
+firstPublishedAt: 2023-06-27T12:51:34.237Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: se-pierde-la-informacion-del-cliente-cuando-tiene-algun-pedido-con-profileerroronloading
+locale: es
+kiStatus: Backlog
+internalReference: 340036
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el pedido tiene "profileErrorOnLoading=true", el comportamiento esperado es que el perfil del cliente, la dirección y la tarjeta de crédito no se guarden/actualicen en el Sistema de Perfiles.
+
+El problema es que el checkout sigue haciendo algunas peticiones para registrar el e-mail del comprador, naturalmente, sin enviar otros campos como nombre y teléfono. Por lo tanto, si el cliente ya está registrado en la tienda, estos campos se borran, y los datos del cliente se pierden.
+
+
+##
+
+## Simulación
+
+
+No podemos simular el comportamiento ya que el "profileErrorOnLoading" es sólo para excepciones inesperadas.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md b/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md
index d99baab2c..f509427ed 100644
--- a/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md
+++ b/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md
@@ -3,8 +3,8 @@ title: 'La información del cliente no se guarda en el sistema de perfiles'
 id: 1MCiEAJ3ZueJVM04T7x9z2
 status: PUBLISHED
 createdAt: 2023-04-04T22:47:43.035Z
-updatedAt: 2023-04-06T17:51:29.025Z
-publishedAt: 2023-04-06T17:51:29.025Z
+updatedAt: 2023-11-01T12:37:24.071Z
+publishedAt: 2023-11-01T12:37:24.071Z
 firstPublishedAt: 2023-04-04T22:47:43.593Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-informacion-del-cliente-no-se-guarda-en-el-sistema-de-perfiles
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 784763
 ---
 
diff --git a/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md b/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
index 7cc012317..63a9a1379 100644
--- a/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
+++ b/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
@@ -3,8 +3,8 @@ title: 'La expresión de cluster personalizada no funciona en la promoción de e
 id: 27QJfNVhuPNiRxqQiXPRt2
 status: PUBLISHED
 createdAt: 2022-03-16T19:36:36.102Z
-updatedAt: 2022-11-25T22:12:51.339Z
-publishedAt: 2022-11-25T22:12:51.339Z
+updatedAt: 2024-02-16T20:29:37.996Z
+publishedAt: 2024-02-16T20:29:37.996Z
 firstPublishedAt: 2022-03-16T19:36:36.504Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: la-expresion-de-cluster-personalizada-no-funciona-en-la-promocion-de-envio-gratuito-canal-de-ventas-por-defecto-1
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 334027
 ---
 
diff --git a/docs/known-issues/es/cvv-without-validation-of-characters-type.md b/docs/known-issues/es/cvv-without-validation-of-characters-type.md
index 248f64baa..f9ef20401 100644
--- a/docs/known-issues/es/cvv-without-validation-of-characters-type.md
+++ b/docs/known-issues/es/cvv-without-validation-of-characters-type.md
@@ -3,8 +3,8 @@ title: 'CVV sin validación del tipo de caracteres'
 id: 63MJ3ODCvr3ayfgJiuN1ja
 status: PUBLISHED
 createdAt: 2022-03-27T20:25:43.400Z
-updatedAt: 2022-11-25T22:07:55.541Z
-publishedAt: 2022-11-25T22:07:55.541Z
+updatedAt: 2024-02-16T20:29:04.636Z
+publishedAt: 2024-02-16T20:29:04.636Z
 firstPublishedAt: 2022-03-27T20:25:43.819Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: cvv-sin-validacion-del-tipo-de-caracteres
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 425204
 ---
 
diff --git a/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md b/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md
new file mode 100644
index 000000000..715f24bdd
--- /dev/null
+++ b/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md
@@ -0,0 +1,45 @@
+---
+title: 'Sistema de pago desactivado al pasar por caja'
+id: 2LQYOKtkURQoWUU1InCRUo
+status: PUBLISHED
+createdAt: 2024-06-13T19:37:58.649Z
+updatedAt: 2024-06-13T19:37:59.481Z
+publishedAt: 2024-06-13T19:37:59.481Z
+firstPublishedAt: 2024-06-13T19:37:59.481Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: sistema-de-pago-desactivado-al-pasar-por-caja
+locale: es
+kiStatus: Backlog
+internalReference: 1049543
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El problema parece ocurrir sólo en las subcuentas, incluso desactivado (también eliminado) el método de pago rinde en la caja
+
+
+##
+
+## Simulación
+
+
+No hemos podido simularlo.
+
+
+
+## Workaround
+
+
+Se puede realizar una corrección manual, para ello debe ponerse en contacto con el equipo de soporte.
+
+
+
+
diff --git a/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md b/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md
new file mode 100644
index 000000000..38468865a
--- /dev/null
+++ b/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md
@@ -0,0 +1,44 @@
+---
+title: 'error de bloqueo al utilizar las API de catálogo'
+id: 6A4jBKBKIzn87mxNQJ4YQN
+status: PUBLISHED
+createdAt: 2023-07-14T18:29:11.937Z
+updatedAt: 2023-07-19T14:16:39.062Z
+publishedAt: 2023-07-19T14:16:39.062Z
+firstPublishedAt: 2023-07-14T18:29:13.088Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: error-de-bloqueo-al-utilizar-las-api-de-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 862626
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+1. Utilice, por ejemplo, la API Add SKU to Subcollection (https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/subcollection/-subCollectionId-/stockkeepingunit) para añadir muchos skus a una colección en poco tiempo;
+2. 2. Compruebe que pueden producirse errores, como un bloqueo.
+
+
+
+## Workaround
+
+
+Intenta hacer menos peticiones por minuto.
+
+
+
+
+
diff --git a/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md b/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
index d8f192e9d..5979d4656 100644
--- a/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
+++ b/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
@@ -1,18 +1,18 @@
 ---
-title: 'Los pagos de débito que utilizan el conector Firstdata no pueden liquidarse debido a un error en el campo TransactionState'
+title: 'Los pagos a débito que utilizan el conector Firstdata no pueden liquidarse debido a un error en el campo TransactionState'
 id: 6imTj4PTpJGGFqyhSLTPu9
 status: PUBLISHED
 createdAt: 2022-03-03T21:59:55.119Z
-updatedAt: 2022-11-25T22:05:01.885Z
-publishedAt: 2022-11-25T22:05:01.885Z
+updatedAt: 2024-02-16T20:24:59.932Z
+publishedAt: 2024-02-16T20:24:59.932Z
 firstPublishedAt: 2022-03-03T21:59:55.506Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: los-pagos-de-debito-que-utilizan-el-conector-firstdata-no-pueden-liquidarse-debido-a-un-error-en-el-campo-transactionstate
+slug: los-pagos-a-debito-que-utilizan-el-conector-firstdata-no-pueden-liquidarse-debido-a-un-error-en-el-campo-transactionstate
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 461095
 ---
 
@@ -23,26 +23,28 @@ internalReference: 461095
 </div>
 
 
-Al utilizar el conector Firstdata para procesar pagos de débito, nuestro código espera que el campo `TransactionState` sea "CAPTURED". Sin embargo, el proveedor envía tanto "CAPTURED" como "SETTLED", lo que provoca un error:
+Al utilizar el conector Firstdata para procesar pagos de débito, nuestro código está diseñado para esperar que el campo TransactionState se establezca como "CAPTURED". Sin embargo, hemos encontrado un problema en el que el proveedor está enviando ambos valores "CAPTURED" y "SETTLED", lo que está causando un error:
 
-Mensaje: Unknown Error on AutoSettleHay un error en el documento XML (1, 745).
-&
-Error en la ejecución de la operación de liquidación. Por favor, vea la excepción interna. Conector = Firstdata. Mensaje = La cadena de entrada no estaba en un formato correcto.
 
-No he podido encontrar en la documentación de firstdata cuál es el correcto, pero hay ejemplos para ambos.
+    Mensaje de error: Unknown Error on AutoSettle. Hay un error en el documento XML (1, 745). & Error al ejecutar la operación de Liquidación. Consulte la excepción interna. Conector: Firstdata. Mensaje: La cadena de entrada no tenía el formato correcto.
 
 
 
-## Simulación
+##
 
+## Simulación
 
 
-A veces, cuando se cancela una transacción utilizando este conector es posible observar este comportamiento.
+No es posible simular ya que es un comportamiento intermitente que depende de la respuesta del proveedor de pago.
 
 
 
 ## Workaround
 
 
-No hay ninguna solución disponible.
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md b/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
new file mode 100644
index 000000000..3a80108d9
--- /dev/null
+++ b/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
@@ -0,0 +1,41 @@
+---
+title: 'Las reglas de crédito de cliente eliminadas aparecerán en la caja si no se han desactivado previamente'
+id: 7culNJ04UcZfzgHFREyNEs
+status: PUBLISHED
+createdAt: 2024-03-04T23:12:22.826Z
+updatedAt: 2024-03-04T23:12:23.859Z
+publishedAt: 2024-03-04T23:12:23.859Z
+firstPublishedAt: 2024-03-04T23:12:23.859Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: las-reglas-de-credito-de-cliente-eliminadas-apareceran-en-la-caja-si-no-se-han-desactivado-previamente
+locale: es
+kiStatus: Backlog
+internalReference: 994066
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Con `vtex.custom-payments` instalado en la cuenta cree varias reglas de pago de Crédito de cliente y elimine una sin desactivar, la verá en el checkout.
+
+
+
+## Workaround
+
+
+Es posible arreglar esto manualmente con la ayuda del equipo de soporte.
+
+
+
+
diff --git a/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md b/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
new file mode 100644
index 000000000..cfdaa825e
--- /dev/null
+++ b/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
@@ -0,0 +1,49 @@
+---
+title: 'La capacidad de entrega no se respeta si hay espacio en el Id de la política de envío'
+id: 1OyY54G05o15EI2zAmW4Vq
+status: PUBLISHED
+createdAt: 2023-07-14T21:25:50.522Z
+updatedAt: 2024-03-19T19:26:55.344Z
+publishedAt: 2024-03-19T19:26:55.344Z
+firstPublishedAt: 2023-07-14T21:25:51.117Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: la-capacidad-de-entrega-no-se-respeta-si-hay-espacio-en-el-id-de-la-politica-de-envio
+locale: es
+kiStatus: Backlog
+internalReference: 862830
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si la función de programación de entregas está en uso y la capacidad de entrega está habilitada, hay dos escenarios conocidos que pueden hacer que la ventana esté disponible incluso después de haber alcanzado su límite máximo de capacidad configurada.
+Los escenarios son: ID de política de envío con un espacio o demasiados caracteres formando la cadena, `AccountName+ShippingPolicyId` no puede superar los 60 caracteres.
+
+
+##
+
+## Simulación
+
+
+Cree una política de envío y, en su Id, inserte un espacio, o `AccountName+ShippingPolicyId` que resulte en más de 60 caracteres, configure la entrega programada y la capacidad de entrega.
+Realice los pedidos seleccionando la ventana registrada, compruebe que será posible crear más pedidos que el máximo configurado en la capacidad de entrega.
+En el momento del pago, cuando se alcance el límite configurado, la ventana no dejará de estar disponible, sino que permanecerá visible y podrá ser seleccionada.
+
+
+
+## Workaround
+
+
+No registre ningún Id con un espacio en la política de envío o con más de 60 caracteres sumando los caracteres del `AccountName+ShippingPolicyId`.
+
+
+
+
+
diff --git a/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md b/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md
new file mode 100644
index 000000000..40d0ad195
--- /dev/null
+++ b/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md
@@ -0,0 +1,51 @@
+---
+title: 'Entrega fraccionada con Lean Shipping ofreciendo SLA inválidos'
+id: 61Yq1WhmCclFtcum3YMtXn
+status: PUBLISHED
+createdAt: 2024-02-27T19:21:21.615Z
+updatedAt: 2024-02-27T19:26:27.513Z
+publishedAt: 2024-02-27T19:26:27.513Z
+firstPublishedAt: 2024-02-27T19:21:22.667Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: entrega-fraccionada-con-lean-shipping-ofreciendo-sla-invalidos
+locale: es
+kiStatus: Backlog
+internalReference: 990155
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un carro de la compra incluye productos de diferentes vendedores, con diferentes canales de entrega e ID de SLA entre ellos, la interfaz de usuario de Checkout activa Lean Shipping, resumiendo los SLA disponibles para mostrar sólo las opciones "más rápida" y "más barata" para cada artículo.
+
+Sin embargo, si existe una opción de entrega programada pero no es la más rápida ni la más barata, el conmutador de programación seguirá apareciendo en la IU, aunque Lean Shipping no la seleccionará como opción viable.
+
+
+
+## Simulación
+
+
+
+- Montar un carro con al menos 2 vendedores diferentes, donde un artículo tiene 3 ANS, donde el programado no es ni la opción más rápida ni la más barata (y por lo tanto no se ofrecerá a través de Lean Shipping).
+- Seleccione recogida en tienda.
+- Utilice la interfaz de programación de la interfaz de usuario para la entrega del otro artículo.
+- Observe que sigue aplicando el SLA más rápido/barato (no programado), en lugar del programado, ignorando de hecho su selección de ventana de entrega del paso anterior.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md b/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md
new file mode 100644
index 000000000..45e85982b
--- /dev/null
+++ b/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md
@@ -0,0 +1,50 @@
+---
+title: 'El nombre del departamento no se carga en la interfaz de usuario de las comisiones de gestión de vendedores'
+id: 5TkKtfYi5oFxNOk0mTTeiQ
+status: PUBLISHED
+createdAt: 2024-03-25T17:20:22.888Z
+updatedAt: 2024-03-25T17:20:23.761Z
+publishedAt: 2024-03-25T17:20:23.761Z
+firstPublishedAt: 2024-03-25T17:20:23.761Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: el-nombre-del-departamento-no-se-carga-en-la-interfaz-de-usuario-de-las-comisiones-de-gestion-de-vendedores
+locale: es
+kiStatus: Backlog
+internalReference: 1005799
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al seleccionar un departamento para establecer una comisión específica en la gestión de vendedores la tabla no está cargando el nombre del departamento. Este comportamiento no ocurre con las categorías inferiores.
+ ![](https://vtexhelp.zendesk.com/attachments/token/irbcBV8R7kNO4F5XsLHtaxUMO/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+
+1. Activar la opción "Añadir comisiones por categoría"
+2. Seleccione un departamento para asignar las comisiones y guarde el vendedor
+3. Compruebe que la interfaz de usuario no está cargando el nombre del departamento.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md b/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md
index efea11fb6..077eb8e68 100644
--- a/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md
+++ b/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md
@@ -3,8 +3,8 @@ title: 'Los diacríticos se eliminan en CatalogAPI'
 id: 2iVyAQ8TSaT3jFYzcQGjSs
 status: PUBLISHED
 createdAt: 2022-07-22T18:18:04.236Z
-updatedAt: 2022-11-25T21:44:21.525Z
-publishedAt: 2022-11-25T21:44:21.525Z
+updatedAt: 2024-02-16T20:28:19.994Z
+publishedAt: 2024-02-16T20:28:19.994Z
 firstPublishedAt: 2022-07-22T18:18:05.160Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: los-diacriticos-se-eliminan-en-catalogapi
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 623345
 ---
 
diff --git a/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md b/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md
new file mode 100644
index 000000000..5aa58afd5
--- /dev/null
+++ b/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md
@@ -0,0 +1,49 @@
+---
+title: 'Diferencia de precios entre PDP, PLP y Checkout Cart'
+id: 3Oo5ccYOG7hcEXYaROxXMV
+status: PUBLISHED
+createdAt: 2023-06-29T20:02:13.485Z
+updatedAt: 2023-06-29T20:02:14.572Z
+publishedAt: 2023-06-29T20:02:14.572Z
+firstPublishedAt: 2023-06-29T20:02:14.572Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: diferencia-de-precios-entre-pdp-plp-y-checkout-cart
+locale: es
+kiStatus: Backlog
+internalReference: 853175
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+El portal está entregando el mismo contenido en los PDPs y PLPs incluso después de algunas actualizaciones como promociones.
+
+
+
+## Simulación
+
+
+
+Con una caché caducada, el CDN pregunta al sistema del portal si se ha modificado la página. Si es así, el portal entrega la nueva página para ser renderizada, de lo contrario, el CDN redibuja la página que ya tiene.
+
+En este caso, vimos que aunque la página había presentado algunos cambios, la inclusión de una promoción, el portal devolvía al CDN que no había ningún cambio en comparación con la página en caché y, por lo tanto, la capa de borde estaba renderizando la página sin promoción.
+
+
+
+## Workaround
+
+
+
+Una forma de solucionarlo era **cambiar la plantilla de la página del producto (como incluir un comentario**), de forma que el portal informara de que había un cambio en la estructura, y el CDN obtuviera la nueva página para almacenarla en caché.
+
+
+
+
diff --git a/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md b/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md
new file mode 100644
index 000000000..454159698
--- /dev/null
+++ b/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md
@@ -0,0 +1,41 @@
+---
+title: 'Diferencias entre el valor de especificación en las API y el portal'
+id: 29Utcf4B7PBZitEHxrZwbE
+status: PUBLISHED
+createdAt: 2023-06-29T20:11:49.484Z
+updatedAt: 2023-07-06T13:41:29.683Z
+publishedAt: 2023-07-06T13:41:29.683Z
+firstPublishedAt: 2023-06-29T20:11:50.157Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: diferencias-entre-el-valor-de-especificacion-en-las-api-y-el-portal
+locale: es
+kiStatus: Backlog
+internalReference: 853184
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente estas dos APIs ("api/catalog" y "api/catalog_system" GET Specification Value) están consultando diferentes tablas en la base de datos de catálogos. Se supone que los valores son los mismos en ambas tablas, sin embargo los escenarios con caracteres especiales pueden divergir.
+
+Esto también se refleja en el Portal y en los PDP, ya que la información se está generando basándose en la tabla incorrecta. Los caracteres especiales aparecen como "????" en el frontend.
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md b/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
index 87dc5d8f7..0eab98da8 100644
--- a/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
+++ b/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
@@ -3,8 +3,8 @@ title: 'Disclosure Layout no se puede utilizar correctamente cuando prop animado
 id: 14QweVpzLO8TsyI68H79ZG
 status: PUBLISHED
 createdAt: 2022-04-19T19:53:22.409Z
-updatedAt: 2022-11-25T22:13:15.022Z
-publishedAt: 2022-11-25T22:13:15.022Z
+updatedAt: 2024-07-01T18:48:05.329Z
+publishedAt: 2024-07-01T18:48:05.329Z
 firstPublishedAt: 2022-04-19T19:53:23.090Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: disclosure-layout-no-se-puede-utilizar-correctamente-cuando-prop-animado-se-establece-como-verdadero
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 417947
 ---
 
diff --git a/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md b/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
new file mode 100644
index 000000000..6406993d4
--- /dev/null
+++ b/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
@@ -0,0 +1,47 @@
+---
+title: 'Discrepancia en el recuento de cupones utilizados en OMS y en la interfaz de usuario de cupones'
+id: 5PyOeirr1XqXREmQJpSHs1
+status: PUBLISHED
+createdAt: 2023-12-18T21:53:26.360Z
+updatedAt: 2023-12-18T21:53:27.039Z
+publishedAt: 2023-12-18T21:53:27.039Z
+firstPublishedAt: 2023-12-18T21:53:27.039Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: discrepancia-en-el-recuento-de-cupones-utilizados-en-oms-y-en-la-interfaz-de-usuario-de-cupones
+locale: es
+kiStatus: Backlog
+internalReference: 954959
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunos pedidos no están siendo recuperados en el uso de los cupones, hemos identificado que algunos pedidos no estaban siendo contados por el administrador de cupones.
+
+
+##
+
+## Simulación
+
+
+Comprobar si entre el 10/09 y el 13/09 hay alguna discrepancia entre los usos de los cupones.
+
+
+
+## Workaround
+
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md b/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md
index a2dea15b0..cad976877 100644
--- a/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md
+++ b/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md
@@ -26,7 +26,7 @@ El pedido se cierra y se transacciona normalmente en VTEX. Pero dependiendo de l
 
 Ejemplo de ocurrencia:
 
-![image](https://images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
 
 En ese caso, el valor total del pedido cobrado del cliente quedó en `R$ 7,98`. Sin embargo, al sumar los valores de venta registrados en cada producto, el total sería de `R$ 7,95`.
 
diff --git a/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md b/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
new file mode 100644
index 000000000..7443ca715
--- /dev/null
+++ b/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
@@ -0,0 +1,50 @@
+---
+title: 'Divergencia en la configuración avanzada de la tienda en cuentas o espacios de trabajo nuevos'
+id: 1Jt8McqXjYAxfJNkBZHt4j
+status: PUBLISHED
+createdAt: 2024-07-11T18:16:01.106Z
+updatedAt: 2024-07-11T18:16:02.006Z
+publishedAt: 2024-07-11T18:16:02.006Z
+firstPublishedAt: 2024-07-11T18:16:02.006Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: divergencia-en-la-configuracion-avanzada-de-la-tienda-en-cuentas-o-espacios-de-trabajo-nuevos
+locale: es
+kiStatus: Backlog
+internalReference: 1064235
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En nuevos espacios de trabajo o cuentas que nunca cambiaron las configuraciones avanzadas de la Configuración de la Tienda se puede verificar una inconsistencia entre la información en la UI y la bandera aplicada a la cuenta.
+
+
+##
+
+## Simulación
+
+
+
+- Crear un nuevo espacio de trabajo
+- Vaya a la Configuración de la tienda en la pestaña Avanzado
+- Ver que algunas banderas se establecen en la interfaz de usuario
+- Verifique las configuraciones usando el plugin settings con el siguiente comando `vtex settings get vtex.store`.
+- Compruebe que los indicadores no están aplicados.
+
+
+
+## Workaround
+
+
+Haga clic en el botón "Guardar" de la interfaz de usuario
+
+
+
+
diff --git a/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md b/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md
index 9734fbaba..4c5546a9e 100644
--- a/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md
+++ b/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md
@@ -3,8 +3,8 @@ title: 'Estado divergente en la lista de transacciones y en la transacción'
 id: 1LD32IQJFbvlOJzD12KL64
 status: PUBLISHED
 createdAt: 2022-03-03T18:41:10.292Z
-updatedAt: 2022-11-25T22:09:15.186Z
-publishedAt: 2022-11-25T22:09:15.186Z
+updatedAt: 2023-12-12T22:12:02.916Z
+publishedAt: 2023-12-12T22:12:02.916Z
 firstPublishedAt: 2022-03-03T18:41:10.764Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: estado-divergente-en-la-lista-de-transacciones-y-en-la-transaccion
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 308919
 ---
 
@@ -26,12 +26,13 @@ internalReference: 308919
 El estado de las transacciones es diferente una vez que las abre en comparación con lo que se muestra en la lista de transacciones.
 
 
+##
 
 ## Simulación
 
 
-Como no ocurre en todas las transacciones, la forma de simularlo es entrar en una transacción al azar y comprobar si el estado dentro de la misma es el mismo que se establece en la lista de transacciones.
-Una vez que se entra en la transacción, de hecho, el estado es diferente
+Como no ocurre en todas las transacciones, la forma de simularlo es entrar en una transacción aleatoria y comprobar si el estado dentro de ella es el mismo que aparece en la lista de transacciones.
+Una vez dentro de la transacción, efectivamente, el estado es diferente
 
 
 
@@ -40,3 +41,6 @@ Una vez que se entra en la transacción, de hecho, el estado es diferente
 
 No hay ninguna solución.
 
+
+
+
diff --git a/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md b/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
new file mode 100644
index 000000000..dd01dbe8c
--- /dev/null
+++ b/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
@@ -0,0 +1,38 @@
+---
+title: 'Campo de número de documento (RUT) se borra aleatoriamente el último dígito en iOS'
+id: 6KcbAWPN3AylZEm6IkSw3I
+status: PUBLISHED
+createdAt: 2023-10-18T22:53:27.101Z
+updatedAt: 2023-10-19T13:02:18.095Z
+publishedAt: 2023-10-19T13:02:18.095Z
+firstPublishedAt: 2023-10-18T22:53:27.624Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: campo-de-numero-de-documento-rut-se-borra-aleatoriamente-el-ultimo-digito-en-ios
+locale: es
+kiStatus: Backlog
+internalReference: 921944
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Sólo en Safari/iOS, al rellenar el número de documento y desplazarse por los campos de datos del cliente, el campo número de documento (RUT) tendrá el último dígito borrado.
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md b/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
index f781690a5..ef79ef648 100644
--- a/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
+++ b/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
@@ -3,8 +3,8 @@ title: 'Entradas duplicadas para categorías/valores de especificación en el mi
 id: IoWI8yx1cabm4bWhSU4Ek
 status: PUBLISHED
 createdAt: 2022-04-18T18:53:37.507Z
-updatedAt: 2022-11-25T21:58:08.677Z
-publishedAt: 2022-11-25T21:58:08.677Z
+updatedAt: 2024-02-16T20:26:00.077Z
+publishedAt: 2024-02-16T20:26:00.077Z
 firstPublishedAt: 2022-04-18T18:53:38.097Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: entradas-duplicadas-para-categoriasvalores-de-especificacion-en-el-mismo-nivel
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 562588
 ---
 
diff --git a/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md b/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md
new file mode 100644
index 000000000..c0b1b44ae
--- /dev/null
+++ b/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md
@@ -0,0 +1,49 @@
+---
+title: 'Organizaciones duplicadas en el modal para cambiar entre organizaciones'
+id: 7pOIj0RzcmA5mZy60OpfRk
+status: PUBLISHED
+createdAt: 2024-02-22T16:51:15.327Z
+updatedAt: 2024-02-22T16:51:16.213Z
+publishedAt: 2024-02-22T16:51:16.213Z
+firstPublishedAt: 2024-02-22T16:51:16.213Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: organizaciones-duplicadas-en-el-modal-para-cambiar-entre-organizaciones
+locale: es
+kiStatus: Backlog
+internalReference: 986868
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario tiene muchas organizaciones registradas y utiliza el modal para cambiar entre organizaciones, algunas organizaciones se mostrarán duplicadas en la lista.
+
+
+##
+
+## Simulación
+
+
+
+- Configure muchas organizaciones para el mismo correo electrónico;
+- Inicie sesión y abra el modal para cambiar de organización;
+- Algunas organizaciones estarán duplicadas en la lista.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md b/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
new file mode 100644
index 000000000..b94ce3185
--- /dev/null
+++ b/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
@@ -0,0 +1,49 @@
+---
+title: 'El campo Ean como cadena se ignora cuando se aprueba en Skus recibidos'
+id: 3ubVdtlt8ElWzQGFM9OTTq
+status: PUBLISHED
+createdAt: 2023-09-11T16:37:06.258Z
+updatedAt: 2023-11-28T16:54:04.790Z
+publishedAt: 2023-11-28T16:54:04.790Z
+firstPublishedAt: 2023-09-11T16:37:07.098Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: el-campo-ean-como-cadena-se-ignora-cuando-se-aprueba-en-skus-recibidos
+locale: es
+kiStatus: Backlog
+internalReference: 897301
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El vendedor envía el sku con todos los campos declarados en este artículo (https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-) para que el marketplace lo apruebe en el módulo Skus Recibidos.
+
+El campo ean está declarado como tipo string en el artículo anterior. Sin embargo, a pesar de aparecer en la interfaz de usuario de Skus Recibidos, está siendo ignorado por el sistema de matcher backend y también por el módulo de catálogo, lo que significa que el sku se está creando con este campo vacío.
+
+
+##
+
+## Simulación
+
+
+1. Enviar un sku al marketplace con el campo ean configurado como cadena: `"ean": "123456"`
+2. Aprobar el sku como nuevo producto en el módulo Skus Recibidos del marketplace;
+3. 3. Compruebe que en el catálogo este campo está vacío.
+
+
+## Workaround
+
+
+**Antes de que este problema se solucione y el sistema funcione de acuerdo con nuestros documentos**, el formato que funciona actualmente es enviar el campo ean como un array:
+`"ean": ["123456"]`
+
+Otra forma es establecer este campo manualmente en el catálogo una vez que el sku es aprobado.
+
+
diff --git a/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md b/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
new file mode 100644
index 000000000..f3b663e4b
--- /dev/null
+++ b/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
@@ -0,0 +1,59 @@
+---
+title: 'Early Capture compite injustamente con Automatic Capture en AuthorizeDotNet'
+id: 2IDoJIBiGzhkVZGHurLsnj
+status: PUBLISHED
+createdAt: 2023-07-20T18:08:30.934Z
+updatedAt: 2023-07-20T18:08:31.479Z
+publishedAt: 2023-07-20T18:08:31.479Z
+firstPublishedAt: 2023-07-20T18:08:31.479Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: early-capture-compite-injustamente-con-automatic-capture-en-authorizedotnet
+locale: es
+kiStatus: Backlog
+internalReference: 866068
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Para que podamos entender este comportamiento, primero tenemos que comprender la diferencia entre captura automática y captura anticipada:
+
+**Captura Automática:** Llamará a la solicitud de liquidación automáticamente una vez alcanzada la fecha, sin importar si la transacción es o no aprobada por la adquirente y el antifraude.
+
+**Captura Temprana:** Llamará a la solicitud de liquidación después de que el antifraude apruebe la transacción, una vez que se alcance la cantidad de días configurada.
+
+En este conector, la captura automática está codificada para que se produzca a los 4 días, mientras que la captura temprana puede configurarse hasta un máximo de 10 días después de la aprobación del antifraude. Terminan compitiendo entre sí, y si la captura anticipada se configura con un valor superior a 4 días, la captura automática siempre se producirá antes, por lo que siempre se llamará primero.
+
+Esto hace que los valores permitidos en la captura temprana sean inútiles si son mayores de 4 días.
+
+
+##
+
+## Simulación
+
+
+
+
+1. Configure el conector AuthorizeDotNet en su tienda;
+2. Configure el campo "Captura anticipada" con un importe superior a 4 días;
+3. Realice una transacción de prueba;
+4. 4. Vaya a la interfaz de usuario de la transacción y compruebe que el valor programado para la captura automática se llama primero.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md b/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
index 9f7599eec..408bffe15 100644
--- a/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
+++ b/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
@@ -3,8 +3,8 @@ title: 'Las transacciones de la marca de tarjetas de Elo con ERedeRest no respet
 id: 2OSpQyzDkiGioqcEmhuXpk
 status: PUBLISHED
 createdAt: 2023-05-08T20:29:59.412Z
-updatedAt: 2023-05-08T20:36:20.200Z
-publishedAt: 2023-05-08T20:36:20.200Z
+updatedAt: 2024-02-16T20:27:48.477Z
+publishedAt: 2024-02-16T20:27:48.477Z
 firstPublishedAt: 2023-05-08T20:29:59.878Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: las-transacciones-de-la-marca-de-tarjetas-de-elo-con-erederest-no-respetan-la-captura-anticipada
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 350814
 ---
 
diff --git a/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md b/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md
new file mode 100644
index 000000000..4c9617ede
--- /dev/null
+++ b/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md
@@ -0,0 +1,48 @@
+---
+title: 'El correo electrónico no se rellena automáticamente para los nuevos compradores después de iniciar sesión'
+id: 2H6REXZGS6utlWmYKoPmGq
+status: PUBLISHED
+createdAt: 2023-10-17T16:22:21.667Z
+updatedAt: 2023-11-03T17:17:12.530Z
+publishedAt: 2023-11-03T17:17:12.530Z
+firstPublishedAt: 2023-10-17T16:22:22.650Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-correo-electronico-no-se-rellena-automaticamente-para-los-nuevos-compradores-despues-de-iniciar-sesion
+locale: es
+kiStatus: Fixed
+internalReference: 920634
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un nuevo comprador inicia sesión y procede al pago, el correo electrónico no se rellena automáticamente, lo que requiere que el cliente vuelva a introducir su correo electrónico. Esto también ocurre utilizando APIs y enviando cabeceras con las cookies del comprador.
+
+
+
+## Simulación
+
+
+
+- Inicie sesión con un correo electrónico nunca antes utilizado en la tienda;
+- Añadir productos al carrito;
+- Ir a la caja;
+- El email no se rellenará, y deberá escribirse de nuevo.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md b/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md
new file mode 100644
index 000000000..08f0909c2
--- /dev/null
+++ b/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md
@@ -0,0 +1,62 @@
+---
+title: 'El correo electrónico no se rellena automáticamente para los nuevos usuarios en el checkout-ui'
+id: 6XBghXwc93RBF53dCHr35y
+status: DRAFT
+createdAt: 2023-08-25T15:29:58.242Z
+updatedAt: 2023-08-25T16:47:25.505Z
+publishedAt: 
+firstPublishedAt: 
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-correo-electronico-no-se-rellena-automaticamente-para-los-nuevos-usuarios-en-el-checkoutui
+locale: es
+kiStatus: Backlog
+internalReference: 887949
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un nuevo usuario introduce un nuevo correo electrónico en el paso de correo electrónico y pasa a la página siguiente, en el componente de datos del cliente, el correo electrónico no se rellena automáticamente.
+Esto se debe a que no hay ningún usuario registrado con ese email. Como resultado, el `orderForm` cargado también contiene un campo de email vacío, haciendo que permanezca en blanco y requiriendo que el cliente vuelva a introducir su email.
+
+
+##
+
+## Simulación
+
+
+
+1. Navegue hasta la página de pago en la que los clientes introducen su correo electrónico.
+2. Poner un email nunca usado antes en la tienda.
+3. Vaya al componente de perfil del cliente.
+4. La casilla de correo electrónico estará vacía, y entonces tendrás que escribirlo de nuevo.
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
+que escribirlo de nuevo.
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md b/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
new file mode 100644
index 000000000..583756ff3
--- /dev/null
+++ b/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
@@ -0,0 +1,47 @@
+---
+title: 'Los correos electrónicos con funciones de ventas no pueden suplantar la identidad mediante la función Organizaciones B2B.'
+id: 4HKDawkaTmzWcTZyrIhhuj
+status: PUBLISHED
+createdAt: 2023-09-29T18:15:08.398Z
+updatedAt: 2023-10-09T14:21:48.982Z
+publishedAt: 2023-10-09T14:21:48.982Z
+firstPublishedAt: 2023-09-29T18:15:09.110Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: los-correos-electronicos-con-funciones-de-ventas-no-pueden-suplantar-la-identidad-mediante-la-funcion-organizaciones-b2b
+locale: es
+kiStatus: Fixed
+internalReference: 910328
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si los correos electrónicos tienen algún rol de ventas asociado, no se les permite suplantar utilizando la función Organizaciones B2B.
+
+
+##
+
+## Simulación
+
+
+
+- Cree un usuario para una Organización y asígnele cualquier rol de ventas;
+- Accede a la web e intenta suplantar a cualquier otro usuario.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/encoding-error-in-apple-mail-app.md b/docs/known-issues/es/encoding-error-in-apple-mail-app.md
index 6707961ba..5331aac64 100644
--- a/docs/known-issues/es/encoding-error-in-apple-mail-app.md
+++ b/docs/known-issues/es/encoding-error-in-apple-mail-app.md
@@ -29,7 +29,7 @@ Montar un trigger de envío de correo electrónico que tenga carácter especial
 
 Resultado:
 
-![png](https://images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
+![png](//images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md b/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
new file mode 100644
index 000000000..aca00eb58
--- /dev/null
+++ b/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
@@ -0,0 +1,44 @@
+---
+title: 'Los problemas de codificación de determinados caracteres provocan una búsqueda inesperada de productos.'
+id: O0dM1H8ofJU0ahJRa6217
+status: PUBLISHED
+createdAt: 2024-04-24T22:09:33.395Z
+updatedAt: 2024-04-24T22:09:34.217Z
+publishedAt: 2024-04-24T22:09:34.217Z
+firstPublishedAt: 2024-04-24T22:09:34.217Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-problemas-de-codificacion-de-determinados-caracteres-provocan-una-busqueda-inesperada-de-productos
+locale: es
+kiStatus: Backlog
+internalReference: 1022550
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Este problema se produce especialmente con el símbolo "+".
+
+El término de búsqueda "A+" funciona correctamente cuando se indica a través de la ruta URL, pero se comporta como "A " cuando se indica a través del parámetro "query".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index d4b7764a3..9b47ce16c 100644
--- a/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -3,8 +3,8 @@ title: 'Erro "Categoría XXX no encontrada en el mapeo del nodo de navegación p
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
-updatedAt: 2022-11-25T21:56:57.092Z
-publishedAt: 2022-11-25T21:56:57.092Z
+updatedAt: 2024-02-16T20:29:13.856Z
+publishedAt: 2024-02-16T20:29:13.856Z
 firstPublishedAt: 2022-03-10T17:58:43.266Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: erro-categoria-xxx-no-encontrada-en-el-mapeo-del-nodo-de-navegacion-para-la-especificacion-del-departamento-de-sku-elija-una-categoria-global-mas-especifica-persistente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 417639
 ---
 
diff --git a/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md b/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
new file mode 100644
index 000000000..eab9bd5c7
--- /dev/null
+++ b/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
@@ -0,0 +1,55 @@
+---
+title: 'Error al aprobar skus rechazados o revisados por Calidad de la Oferta'
+id: 7fRMTxq7CFRkyZeK08AGIg
+status: PUBLISHED
+createdAt: 2023-11-23T13:46:30.453Z
+updatedAt: 2024-03-25T12:22:46.687Z
+publishedAt: 2024-03-25T12:22:46.687Z
+firstPublishedAt: 2023-11-23T13:46:31.370Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: error-al-aprobar-skus-rechazados-o-revisados-por-calidad-de-la-oferta
+locale: es
+kiStatus: Fixed
+internalReference: 940998
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un sku falla las reglas de Calidad de Oferta creadas por el Marketplace, va directamente a la "Pestaña de Revisión" o "Pestaña de Rechazados" de Skus Recibidos.
+
+Sin embargo, al intentar aprobar el sku, se devuelve un mensaje de error: "Lo sentimos, algo ha ido mal en el Catálogo. Por favor, inténtelo de nuevo o póngase en contacto con VTEX si el problema persiste".
+
+Esto sucede porque el módulo Matcher no fue capaz de llenar la información del producto y del sku después de enviar el sku a estas Fichas (puedes verificar esto usando las APIs):
+ ![](https://vtexhelp.zendesk.com/attachments/token/0Dti3ak7twOpuVzvzntmPCGit/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+
+1. Crear una regla opcional u obligatoria sobre la Calidad de la Oferta;
+2. 2. Espere a que un sku falle la regla y vaya a la pestaña Revisado/Rechazado;
+3. Intente aprobar el sku y obtenga un mensaje de error;
+4. 4. Compruebe a través de la API si el objeto de coincidencias se rellena como en la imagen anterior.
+
+
+
+## Workaround
+
+
+Aprobar el sku a través de la API pasando la información correcta del producto y del sku manualmente.
+
+
+
+
+
diff --git a/docs/known-issues/es/error-cancelling-customer-credit-invoices.md b/docs/known-issues/es/error-cancelling-customer-credit-invoices.md
new file mode 100644
index 000000000..caf84c018
--- /dev/null
+++ b/docs/known-issues/es/error-cancelling-customer-credit-invoices.md
@@ -0,0 +1,47 @@
+---
+title: 'Error al anular facturas de crédito de clientes'
+id: 75nZNOHGYGBlAoTOjG6gs
+status: PUBLISHED
+createdAt: 2023-10-26T21:09:54.255Z
+updatedAt: 2024-05-29T17:25:32.948Z
+publishedAt: 2024-05-29T17:25:32.948Z
+firstPublishedAt: 2023-10-26T21:09:54.992Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-al-anular-facturas-de-credito-de-clientes
+locale: es
+kiStatus: Backlog
+internalReference: 926563
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En algunos casos las facturas no se pueden cancelar, al ejecutar la API DELETE obtenemos un error 500 con la siguiente respuesta:
+
+`"mensaje": "Se ha producido un error."`
+
+
+##
+
+## Simulación
+
+
+No hemos podido reproducir este error.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index 0e2e90967..f476af950 100644
--- a/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -3,8 +3,8 @@ title: 'Error "¡no se pueden crear criterios de búsqueda! error: el filtro ya
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
-updatedAt: 2022-11-25T22:11:53.363Z
-publishedAt: 2022-11-25T22:11:53.363Z
+updatedAt: 2024-02-16T20:23:47.779Z
+publishedAt: 2024-02-16T20:23:47.779Z
 firstPublishedAt: 2022-09-22T15:53:16.277Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: error-no-se-pueden-crear-criterios-de-busqueda-error-el-filtro-ya-existe-brandid-al-crear-una-promocion-que-excluye-mas-de-1-marca
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 663698
 ---
 
diff --git a/docs/known-issues/es/error-closing-customer-credit-account.md b/docs/known-issues/es/error-closing-customer-credit-account.md
new file mode 100644
index 000000000..decdcb31a
--- /dev/null
+++ b/docs/known-issues/es/error-closing-customer-credit-account.md
@@ -0,0 +1,47 @@
+---
+title: 'Error al cerrar la cuenta de crédito del cliente'
+id: zp8Bd8sIijJVNHws4nrkh
+status: PUBLISHED
+createdAt: 2023-09-20T21:38:28.253Z
+updatedAt: 2023-09-20T21:38:28.888Z
+publishedAt: 2023-09-20T21:38:28.888Z
+firstPublishedAt: 2023-09-20T21:38:28.888Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-al-cerrar-la-cuenta-de-credito-del-cliente
+locale: es
+kiStatus: Backlog
+internalReference: 904432
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando las cuentas principales y secundarias tienen instalada la aplicación de Crédito a Clientes, la creación de una creditAccount se produce en todas ellas. En este escenario hay casos en los que cerrar la creditAccount no funciona, aparece el siguiente error:
+
+Error al cerrar la cuenta
+
+
+##
+
+## Simulación
+
+
+No hemos sido capaces de replicar o identificar la causa, en algunas cuentas este problema no ocurre.
+
+
+
+## Workaround
+
+
+NA, lo que se puede hacer es cambiar el límite de crédito a cero para que el método de pago no funcione para el correo electrónico registrado.
+
+
+
+
diff --git a/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md b/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md
new file mode 100644
index 000000000..a0f5efc20
--- /dev/null
+++ b/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md
@@ -0,0 +1,50 @@
+---
+title: 'Error al exportar una entidad con demasiados documentos'
+id: 1uLEk6e9z3011GaoJ4DNU0
+status: PUBLISHED
+createdAt: 2023-07-07T15:59:46.214Z
+updatedAt: 2023-07-07T15:59:46.899Z
+publishedAt: 2023-07-07T15:59:46.899Z
+firstPublishedAt: 2023-07-07T15:59:46.899Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-al-exportar-una-entidad-con-demasiados-documentos
+locale: es
+kiStatus: Backlog
+internalReference: 857894
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La exportación de un gran número de documentos de una entidad provoca un procesamiento excesivo, causando errores en la cola de proceso e impidiendo la exportación de la lista de documentos.
+
+
+##
+
+## Simulación
+
+
+
+1. Accede a la plataforma CRM de Datos Maestros y navega hasta el formulario de la entidad deseada.
+2. Localice el botón "Exportar XLS" dentro de la interfaz y haga clic sobre él.
+3. Localice el botón "Exportar XLS" y haga clic sobre él.
+4. Inicie el proceso de exportación confirmando la selección e iniciando la exportación.
+5. Para supervisar el progreso de la exportación, navegue hasta la pestaña Aplicaciones dentro de la plataforma.
+6. Busque el botón "Exportaciones" y haga clic en él para ver la lista en curso.
+7. 7. Observe el estado de la exportación y compruebe si se ha producido algún error o problema durante el proceso de exportación.
+
+
+
+
+## Workaround
+
+
+Una solución para este problema es utilizar la API de desplazamiento.
+
diff --git a/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md b/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md
index 61fb1b6ae..c91ffa526 100644
--- a/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md
+++ b/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md
@@ -1,10 +1,10 @@
 ---
 title: 'Error al exportar una gran cantidad de tarjetas de regalo'
 id: 2EZ9XmZwYmcWdRxKbTNEBJ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-03-27T12:37:51.512Z
-updatedAt: 2022-11-25T22:09:09.150Z
-publishedAt: 2022-11-25T22:09:09.150Z
+updatedAt: 2023-07-03T17:14:32.962Z
+publishedAt: 
 firstPublishedAt: 2022-03-27T12:37:52.279Z
 contentType: knownIssue
 productTeam: Payments
@@ -39,3 +39,12 @@ N/A
 
 N/A
 
+ceso de exportación con más de 50000 giftcards.
+
+
+
+## Workaround
+
+
+Exportar en cantidades menores o periodos de tiempo menores.
+
diff --git a/docs/known-issues/es/error-exporting-prices-with-metadata.md b/docs/known-issues/es/error-exporting-prices-with-metadata.md
new file mode 100644
index 000000000..1d585669b
--- /dev/null
+++ b/docs/known-issues/es/error-exporting-prices-with-metadata.md
@@ -0,0 +1,51 @@
+---
+title: 'Error al exportar precios con metadatos'
+id: 7nYPmatUXq57ZUsKHvfYJo
+status: PUBLISHED
+createdAt: 2023-07-12T11:49:06.370Z
+updatedAt: 2023-07-12T11:49:07.185Z
+publishedAt: 2023-07-12T11:49:07.185Z
+firstPublishedAt: 2023-07-12T11:49:07.185Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: error-al-exportar-precios-con-metadatos
+locale: es
+kiStatus: Backlog
+internalReference: 860290
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En ocasiones, al intentar exportar los precios con la opción de metadatos activada y sin utilizar filtros, puede producirse un error. Comprobando el mensaje en devTools aparecerá algo similar a "Polly broken circuit on service...".
+
+Este error se produce debido a un estrangulamiento en el módulo de catálogo al intentar recuperar los metadatos de muchos skus.
+
+
+##
+
+## Simulación
+
+
+
+1. Exportar los precios con metadatos sin utilizar ningún filtro;
+2. En ocasiones aparecerá un mensaje de error;
+3. Compruebe en inspect devtools si el mensaje es similar al anterior.
+
+
+
+## Workaround
+
+
+Utiliza los filtros para reducir la cantidad de skus en la hoja de cálculo y el módulo de catálogo devolverá los datos sin problemas.
+
+
+
+
+
diff --git a/docs/known-issues/es/error-in-checkout-error-message.md b/docs/known-issues/es/error-in-checkout-error-message.md
index 3cc3a0762..61060dabc 100644
--- a/docs/known-issues/es/error-in-checkout-error-message.md
+++ b/docs/known-issues/es/error-in-checkout-error-message.md
@@ -3,8 +3,8 @@ title: 'Error en el mensaje de error de la compra'
 id: 7jCEQoDRPvNwYCJmAt78im
 status: PUBLISHED
 createdAt: 2022-03-25T14:46:49.548Z
-updatedAt: 2022-11-25T22:07:18.470Z
-publishedAt: 2022-11-25T22:07:18.470Z
+updatedAt: 2024-02-16T20:27:24.748Z
+publishedAt: 2024-02-16T20:27:24.748Z
 firstPublishedAt: 2022-03-25T15:30:16.292Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: error-en-el-mensaje-de-error-de-la-compra
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 409895
 ---
 
diff --git a/docs/known-issues/es/error-in-custom-payments-creation.md b/docs/known-issues/es/error-in-custom-payments-creation.md
new file mode 100644
index 000000000..a6be1e11c
--- /dev/null
+++ b/docs/known-issues/es/error-in-custom-payments-creation.md
@@ -0,0 +1,46 @@
+---
+title: 'Error en la creación de pagos personalizados'
+id: 28jwG2jyT5FkSTbb85KlLX
+status: PUBLISHED
+createdAt: 2024-03-06T14:19:49.398Z
+updatedAt: 2024-07-01T18:49:29.959Z
+publishedAt: 2024-07-01T18:49:29.959Z
+firstPublishedAt: 2024-03-06T14:19:50.201Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-en-la-creacion-de-pagos-personalizados
+locale: es
+kiStatus: No Fix
+internalReference: 995110
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los comerciantes pueden experimentar un error al crear un pago personalizado, después de rellenar todo y pulsar guardar aparece el mensaje "Pago personalizado se ha configurado correctamente", pero en realidad la creación falló (no aparece en la interfaz de usuario).
+
+
+##
+
+## Simulación
+
+
+Vaya a la pestaña de Pagos Personalizados y configure cualquier regla de pago, es posible que experimente el problema anterior.
+
+
+
+## Workaround
+
+
+La única solución sería reintentar la creación hasta que aparezca en la interfaz de usuario.
+
+
+
+
+
diff --git a/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
new file mode 100644
index 000000000..e4783987d
--- /dev/null
+++ b/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -0,0 +1,49 @@
+---
+title: 'Error en operaciones de reembolso y captura con Payout Split - "Valor en destinatarios * es diferente al valor de la operación *."'
+id: 3Wo9ltN7Ju0ZqVLAQZcd7m
+status: PUBLISHED
+createdAt: 2023-08-23T13:57:20.424Z
+updatedAt: 2024-02-02T20:52:54.054Z
+publishedAt: 2024-02-02T20:52:54.054Z
+firstPublishedAt: 2023-08-23T13:57:21.389Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-en-operaciones-de-reembolso-y-captura-con-payout-split-valor-en-destinatarios-es-diferente-al-valor-de-la-operacion
+locale: es
+kiStatus: Backlog
+internalReference: 698005
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Debido a problemas de redondeo al recalcular los destinatarios de una transacción con Payout Split, ya sea en la captura o en el reembolso, recibimos la siguiente excepción de la pasarela, ya que la suma del valor del destinatario difiere del valor de la transacción.
+
+
+    Vtex.Practices.ExceptionHandling.ValidationException: Value in recipients (xx.989999999999999999999999988) is different than operation value (xx.99). at Vtex.PaymentGateway.PaymentSplit.RecipientsBuilder.ValidateRecipientsValue(List`1 recipients, Decimal value)...
+
+
+
+##
+
+## Simulación
+
+
+No se puede simular
+
+
+
+## Workaround
+
+
+No hay solución
+
+
+
+
diff --git a/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
new file mode 100644
index 000000000..040b96997
--- /dev/null
+++ b/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -0,0 +1,49 @@
+---
+title: 'Error en el reembolso - "El valor no puede ser nulo. Nombre del parámetro: valor"'
+id: 6TZFYB9zb02oMoN5IJMxR3
+status: PUBLISHED
+createdAt: 2024-06-13T18:49:16.797Z
+updatedAt: 2024-06-13T18:49:17.823Z
+publishedAt: 2024-06-13T18:49:17.823Z
+firstPublishedAt: 2024-06-13T18:49:17.823Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-en-el-reembolso-el-valor-no-puede-ser-nulo-nombre-del-parametro-valor
+locale: es
+kiStatus: Backlog
+internalReference: 1049494
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar reembolsar una transacción puede producirse un error 500 con el mensaje:
+
+`Value cannot be null. Nombre del parámetro: value`
+
+ En este caso, los intentos de reembolso aparecen en los registros de transacciones sin respuesta.
+
+
+##
+
+## Simulación
+
+
+No hemos podido replicarlo.
+
+
+
+## Workaround
+
+
+NA, el comerciante tendrá que solicitar el reembolso directamente a la entidad adquirente.
+
+
+
+
diff --git a/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md b/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
new file mode 100644
index 000000000..858f37279
--- /dev/null
+++ b/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
@@ -0,0 +1,49 @@
+---
+title: 'Error en el proceso de cancelación. ERedeRest y E-Rede V2 sólo permiten la cancelación cuando el returnCode es 359'
+id: 5lNLTmKp1xRfewx9OyhcNk
+status: PUBLISHED
+createdAt: 2023-01-26T18:29:35.310Z
+updatedAt: 2023-12-01T16:41:01.605Z
+publishedAt: 2023-12-01T16:41:01.605Z
+firstPublishedAt: 2023-01-26T18:29:36.467Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-en-el-proceso-de-cancelacion-erederest-y-erede-v2-solo-permiten-la-cancelacion-cuando-el-returncode-es-359
+locale: es
+kiStatus: Backlog
+internalReference: 740084
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los conectores heredados, ERedeRest y E-Rede V2, inician las cancelaciones enviando una petición al proveedor y esperan un "returnCode": "359" indicando una cancelación exitosa. Cualquier otro código es interpretado por nuestra pasarela como un estado indefinido, provocando que la transacción se quede atascada en un estado de cancelación. Aunque en algunos casos, la solicitud de reembolso/cancelación se realiza correctamente. Esto provocaba repetidos intentos de cancelación, incluso cuando la cancelación ya había sido procesada por el proveedor.
+
+
+##
+
+## Simulación
+
+
+No se puede simular ya que dependemos de la respuesta del proveedor.
+
+
+
+## Workaround
+
+
+Si el pago por parte del proveedor ya está cancelado
+
+    {"returnCode": "355", "returnMessage": "Transacción ya cancelada."}
+
+El equipo de soporte del producto tiene la opción de utilizar una API interna, `force-cancel-status`, para actualizar el estado del pago y de la transacción a `cancelado`.
+
+
+
+
diff --git a/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md b/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
new file mode 100644
index 000000000..759bdcd59
--- /dev/null
+++ b/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
@@ -0,0 +1,62 @@
+---
+title: 'Error en la visualización de la UI de pedidos tras solicitar la factura vía App'
+id: 1yrb25L1Skj3sRRWyiFDSA
+status: PUBLISHED
+createdAt: 2024-07-24T14:24:29.799Z
+updatedAt: 2024-07-24T14:24:30.583Z
+publishedAt: 2024-07-24T14:24:30.583Z
+firstPublishedAt: 2024-07-24T14:24:30.583Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: error-en-la-visualizacion-de-la-ui-de-pedidos-tras-solicitar-la-factura-via-app
+locale: es
+kiStatus: Backlog
+internalReference: 1070299
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando ejecutamos un `change V2` eliminando o añadiendo un ítem a un pedido, creamos un cambio en la lista de ítems del pedido, que puede aumentar o disminuir el número de índices de la lista de ítems en el json. Este cambio, a su vez, puede no ser consumido por todas las apps o bases de datos implicadas en la gestión del pedido, como la app notificadora de facturas;
+
+Como resultado, al solicitar la factura a través de la app notificadora de facturas antes de haber realizado una acción para eliminar o añadir un ítem, el usuario acaba provocando un escenario de ruptura en la UI, ya que la `aplicación notificadora de facturas` comienza a devolver un error por tener más o menos ítems de los esperados por la UI, dando lugar a un error de "referencia nula" que impide que el pedido se muestre en la UI;
+
+
+##
+
+## Simulación
+
+
+
+**NOTA**: Para simular este escenario, debe haber configurado la `aplicación notificadora de facturas` y también estar utilizando el flujo `Cambiar V2`;
+
+
+- En un pedido con más de un artículo, vaya al estado de tramitación;
+
+
+- Desde la interfaz de usuario, haga clic en la opción "Solicitar factura" (Notifique a su ERP).
+
+
+- Antes de que el ERP le devuelva la factura, realice un cambio en el pedido eliminando o añadiendo algún artículo al mismo;
+
+
+- Espere hasta que el ERP envíe la factura al sistema de Pedidos, entonces acceda de nuevo al pedido desde la UI de Pedidos, en ese momento la UI devolverá un mensaje de error y el pedido no podrá ser visualizado;
+
+
+
+## Workaround
+
+
+Realice la solicitud de factura a través del notificador de factura sólo después de realizar el cambio de posiciones del pedido.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md b/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
new file mode 100644
index 000000000..43f7f1e7b
--- /dev/null
+++ b/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
@@ -0,0 +1,50 @@
+---
+title: 'Error (LeituraDeDadosDoAdministrador) al intentar acceder a las páginas del catálogo en admin'
+id: 40EruMGkO9DVEwb7RZ5nxF
+status: PUBLISHED
+createdAt: 2024-06-25T18:30:24.815Z
+updatedAt: 2024-06-25T18:30:25.929Z
+publishedAt: 2024-06-25T18:30:25.929Z
+firstPublishedAt: 2024-06-25T18:30:25.929Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: error-leituradedadosdoadministrador-al-intentar-acceder-a-las-paginas-del-catalogo-en-admin
+locale: es
+kiStatus: Backlog
+internalReference: 1055578
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunos usuarios incluso con el rol correcto reciben un error "El usuario xx no tiene acceso a la página solicitada (LeituraDeDadosDoAdministrador)" al acceder a las páginas del catálogo en admin.
+
+Esto suele ocurrir con usuarios nuevos creados en cuentas PII.
+
+
+##
+
+## Simulación
+
+
+
+1. Utilizando una cuenta PII crear un nuevo usuario y darle el acceso correcto a los módulos del catálogo.
+2. 2. Compruebe si el usuario puede acceder realmente a estas páginas.
+
+
+
+## Workaround
+
+
+Crear un ticket a VTEX.
+
+
+
+
+
diff --git a/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md b/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
index b24e14aed..956df124a 100644
--- a/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
+++ b/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
@@ -3,8 +3,8 @@ title: 'Mensaje de error en la gestión de ofertas no se actualiza después de s
 id: 5tMKDMsFTZlXQrkVM4WeJD
 status: PUBLISHED
 createdAt: 2022-12-08T14:02:22.948Z
-updatedAt: 2022-12-08T14:03:27.764Z
-publishedAt: 2022-12-08T14:03:27.764Z
+updatedAt: 2024-02-16T20:24:16.785Z
+publishedAt: 2024-02-16T20:24:16.785Z
 firstPublishedAt: 2022-12-08T14:02:23.384Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: mensaje-de-error-en-la-gestion-de-ofertas-no-se-actualiza-despues-de-sku-esta-vinculado-en-vtexvtex-integraciones
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 712956
 ---
 
diff --git a/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
new file mode 100644
index 000000000..ccfcbf2a9
--- /dev/null
+++ b/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -0,0 +1,49 @@
+---
+title: 'Se produce un error al intentar realizar una búsqueda utilizando el campo "Todos" en VTEX CRM'
+id: 1OKMTJuUZx6mnDmYW3MBjP
+status: PUBLISHED
+createdAt: 2023-10-25T18:46:48.120Z
+updatedAt: 2023-10-25T18:46:48.731Z
+publishedAt: 2023-10-25T18:46:48.731Z
+firstPublishedAt: 2023-10-25T18:46:48.731Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: se-produce-un-error-al-intentar-realizar-una-busqueda-utilizando-el-campo-todos-en-vtex-crm
+locale: es
+kiStatus: Backlog
+internalReference: 925679
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Este caso ocurre con entidades que contienen un gran número de campos y millones de registros en una entidad. El problema surge debido a que el buscador utiliza el campo "Todos", que envía peticiones individuales para cada campo consultable de la entidad y multiplica la carga de peticiones para cada documento.
+
+
+##
+
+## Simulación
+
+
+
+1. Acceda a `https://.vtexcrm.com.br/`.
+2. Navegar hasta una vista que representa una entidad con millones de registros.
+3. Inicie una búsqueda utilizando el campo "Todos".
+ ![](https://vtexhelp.zendesk.com/attachments/token/NGWvp5vsTzd31GA07N6vp0Wev/?name=Captura+de+Tela+2023-10-25+a%CC%80s+15.42.35.png)
+4. Observa la respuesta del sistema y comprueba si devuelve un error o experimenta problemas de rendimiento significativos.
+ ![](https://vtexhelp.zendesk.com/attachments/token/aFWGBmUtDtl9ppgmMNOkDX8Fu/?name=Captura+de+Tela+2023-10-25+a%CC%80s+15.40.50.png)
+5. Repita la búsqueda con un campo de búsqueda específico para confirmar si el problema está relacionado con el mecanismo de búsqueda del campo "Todos".
+
+
+
+## Workaround
+
+
+Buscar con un campo de búsqueda específico.
+
diff --git a/docs/known-issues/es/error-on-duplicate-payment-method.md b/docs/known-issues/es/error-on-duplicate-payment-method.md
new file mode 100644
index 000000000..89640f2c1
--- /dev/null
+++ b/docs/known-issues/es/error-on-duplicate-payment-method.md
@@ -0,0 +1,53 @@
+---
+title: 'Error en el método de pago duplicado'
+id: 1wdiEae6sehlnTDnanWT7n
+status: PUBLISHED
+createdAt: 2023-11-02T12:23:14.027Z
+updatedAt: 2023-11-02T12:23:15.109Z
+publishedAt: 2023-11-02T12:23:15.109Z
+firstPublishedAt: 2023-11-02T12:23:15.109Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-en-el-metodo-de-pago-duplicado
+locale: es
+kiStatus: Backlog
+internalReference: 929428
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al duplicar una forma de pago que no tiene fraccionamiento, el operador recibe en pantalla el siguiente mensaje: "El sistema de pago actual no permite opciones de fraccionamiento". Esto sucede porque al crear el cuerpo de la solicitud de creación de la nueva regla, se insertan por defecto algunos campos, entre ellos installmentOptions, pero este campo no existe para pagos en efectivo como débito y boleto(Brasil).
+
+
+##
+
+## Simulación
+
+
+
+1. Accede a la pantalla de condiciones de pago
+2. Selecciona una forma de pago que no tenga plazos.
+3. Haga clic en el botón para duplicar la regla.
+4. Aparecerá en pantalla el siguiente mensaje de error: "El sistema de pago actual no permite opciones de pago a plazos"
+
+
+
+## Workaround
+
+
+Tenemos dos maneras de evitar este problema:
+
+1. 1. Crea otro con la misma configuración que el que quieres duplicar;
+2. Crear la regla a través de la API, `https://.myvtex.com/api/payments/pvt/rules/`, eliminando el campo installmentOptions del cuerpo.
+
+
+
+
+
diff --git a/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md b/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
index 116a0bfe9..1f415fded 100644
--- a/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
+++ b/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
@@ -22,7 +22,7 @@ Las tiendas VTEX pueden convertirse en [sellers](https://help.vtex.com/es/tutori
 
 Esto se debe a que los productos que son vendidos tanto por el marketplace como por sus sellers no son reconocidos por el sistema al ser enviados. Solo es posible enviar productos que se venden en solo una de las tiendas.
 
-![arquitetura circular](https://images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/8fde1676b4fb9b405e56b4e52689f982/arquitetura_circular.JPG)
+![arquitetura circular](//images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/8fde1676b4fb9b405e56b4e52689f982/arquitetura_circular.JPG)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
new file mode 100644
index 000000000..a0e2f3cce
--- /dev/null
+++ b/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -0,0 +1,50 @@
+---
+title: 'Error "Algo ha ido mal. Por favor, inténtelo de nuevo" al añadir imágenes a través del Editor de Sitios.'
+id: r3QVP1kp8HApP83bOi6t9
+status: PUBLISHED
+createdAt: 2023-11-07T22:33:02.296Z
+updatedAt: 2023-11-07T22:34:52.005Z
+publishedAt: 2023-11-07T22:34:52.005Z
+firstPublishedAt: 2023-11-07T22:33:03.046Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: error-algo-ha-ido-mal-por-favor-intentelo-de-nuevo-al-anadir-imagenes-a-traves-del-editor-de-sitios
+locale: es
+kiStatus: Backlog
+internalReference: 932126
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al añadir imágenes a través del Editor de Sitios, el mensaje "`Algo salió mal. Por favor inténtelo de nuevo.`" puede ocurrir ocasionalmente.
+Esto se debe al número de imágenes por bloque. Por el momento, no tenemos un número exacto de imágenes que cause este problema, pero hemos notado este comportamiento por encima de 20 imágenes en el mismo bloque.
+
+
+##
+
+## Simulación
+
+
+
+- Acceda al Editor de Sitios CMS (por ejemplo https://my-account-here.myvtex.com/admin/cms/site-editor);
+- Seleccione el bloque con las nuevas imágenes a añadir;
+- Cuando la adición se guarda, el mensaje "`Algo salió mal. Por favor, inténtelo de nuevo.`" aparecerá en la esquina inferior derecha:
+ ![](https://vtexhelp.zendesk.com/attachments/token/97C4wewa6iz3f7bsmHtdnXu1H/?name=image.png)
+
+
+
+## Workaround
+
+
+Puedes añadir las imágenes directamente al tema, o dividirlas en bloques con flex layout (ref https://developers.vtex.com/docs/apps/vtex.flex-layout).
+
+
+
+
diff --git a/docs/known-issues/es/error-sww-on-product-pdp.md b/docs/known-issues/es/error-sww-on-product-pdp.md
index 6efc12b53..b88b8e779 100644
--- a/docs/known-issues/es/error-sww-on-product-pdp.md
+++ b/docs/known-issues/es/error-sww-on-product-pdp.md
@@ -3,8 +3,8 @@ title: 'Error SWW en el producto PDP'
 id: 3DhuWocQwqiWxuAffdwYkg
 status: PUBLISHED
 createdAt: 2023-01-23T12:38:30.711Z
-updatedAt: 2023-01-23T12:38:31.382Z
-publishedAt: 2023-01-23T12:38:31.382Z
+updatedAt: 2023-09-19T19:15:13.868Z
+publishedAt: 2023-09-19T19:15:13.868Z
 firstPublishedAt: 2023-01-23T12:38:31.382Z
 contentType: knownIssue
 productTeam: Catalog
@@ -23,7 +23,8 @@ internalReference: 738108
 </div>
 
 
-En algunas ocasiones, al abrir el PDP del producto a través de la página de administración (o del dominio final) aparece en pantalla un error Algo ha ido mal.
+En algunas ocasiones, al abrir la PDP del producto a través de la página de administración (o del dominio final) aparece en pantalla un error Algo ha ido mal.
+Este comportamiento puede ocurrir debido a movimientos previos de la categoría en el árbol de categorías provocando una validación errónea de las especificaciones del producto/sku en el sistema de catálogos.
 
 
 ##
@@ -31,8 +32,20 @@ En algunas ocasiones, al abrir el PDP del producto a través de la página de ad
 ## Simulación
 
 
+Abrir el enlace PDP del producto
+Obtener un Algo salió mal en el frente
+
+
 
 ## Workaround
 
 
+Para corregir este comportamiento, la especificación que causa el error no debe tener un valor en el producto.
+O
+Cualquier especificación SKU debe rellenarse porque puede considerarse erróneamente obligatoria
+(compruebe si hay una SKU que tiene una especificación sin rellenar, pero las demás SKU del producto están rellenas)
+
+
+
+
 
diff --git a/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md b/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
index 3847ef979..717fa3c5e 100644
--- a/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
+++ b/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
@@ -3,8 +3,8 @@ title: 'Error provocado por un TOKEN anulado en el conector heredado de PayPal p
 id: 5GrnhD8fwte7qu50Az8r3Y
 status: PUBLISHED
 createdAt: 2023-06-13T22:35:16.397Z
-updatedAt: 2023-06-13T22:38:27.909Z
-publishedAt: 2023-06-13T22:38:27.909Z
+updatedAt: 2024-07-01T18:47:54.680Z
+publishedAt: 2024-07-01T18:47:54.680Z
 firstPublishedAt: 2023-06-13T22:35:16.955Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: error-provocado-por-un-token-anulado-en-el-conector-heredado-de-paypal-para-el-estado-de-pago-pendiente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 308214
 ---
 
diff --git a/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md b/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md
new file mode 100644
index 000000000..97d2ff5ba
--- /dev/null
+++ b/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md
@@ -0,0 +1,46 @@
+---
+title: 'Error al modificar un índice si los campos son idénticos.'
+id: Ckic7QH3kKyW3IA92A3Cm
+status: PUBLISHED
+createdAt: 2023-07-03T18:48:49.070Z
+updatedAt: 2023-07-03T18:48:49.971Z
+publishedAt: 2023-07-03T18:48:49.971Z
+firstPublishedAt: 2023-07-03T18:48:49.971Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-al-modificar-un-indice-si-los-campos-son-identicos
+locale: es
+kiStatus: Backlog
+internalReference: 854634
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La actualización de un índice de esquema puede dar lugar a un error 500 Internal Server cuando no hay cambios que realizar, esto significa que los valores de los campos son idénticos a los actuales.
+Realizar una petición GET en la API para comprobar los índices revela que no es necesaria ninguna actualización, ya que el índice es idéntico al cuerpo proporcionado en la petición PUT.
+
+
+##
+
+## Simulación
+
+
+
+1. Enviar una solicitud PUT para actualizar un índice de esquema a través de la API, proporcionando la carga útil necesaria en el cuerpo de la solicitud.
+2. Verificar la respuesta de la API y observar si devuelve un **500 Internal Server Error**.
+3. Realice una solicitud GET posterior en la API para recuperar los índices de esquema y compárelos con el cuerpo proporcionado en la solicitud PUT.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md b/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md
index 12c2e85a0..3dac76480 100644
--- a/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md
+++ b/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md
@@ -3,8 +3,8 @@ title: 'Error al cambiar el tipo de entrega cuando el vendedor tiene recursivida
 id: 7JLnqVWHz94sQZKMOGUkKC
 status: PUBLISHED
 createdAt: 2022-06-14T14:07:38.881Z
-updatedAt: 2022-11-25T21:52:59.031Z
-publishedAt: 2022-11-25T21:52:59.031Z
+updatedAt: 2024-02-16T20:24:13.311Z
+publishedAt: 2024-02-16T20:24:13.311Z
 firstPublishedAt: 2022-06-14T14:07:39.358Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: error-al-cambiar-el-tipo-de-entrega-cuando-el-vendedor-tiene-recursividad
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 597915
 ---
 
diff --git a/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md b/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md
new file mode 100644
index 000000000..e921aa8b2
--- /dev/null
+++ b/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md
@@ -0,0 +1,60 @@
+---
+title: 'Error al publicar una entidad de datos de almacenamiento dinámico'
+id: 1yNh5CV41vrrrU5F7Vj2tG
+status: PUBLISHED
+createdAt: 2023-10-04T16:33:03.051Z
+updatedAt: 2023-10-04T16:37:00.614Z
+publishedAt: 2023-10-04T16:37:00.614Z
+firstPublishedAt: 2023-10-04T16:33:03.847Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: error-al-publicar-una-entidad-de-datos-de-almacenamiento-dinamico
+locale: es
+kiStatus: Backlog
+internalReference: 666357
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la tienda crea o actualiza una Entidad de Datos y luego intenta publicarla, puede ocurrir el siguiente error:
+
+
+    Error inesperado. Por favor, inténtelo de nuevo o póngase en contacto con el servicio de atención al cliente.
+
+
+
+
+## Simulación
+
+
+
+- Acceda a la aplicación Sistema de almacenamiento dinámico / Estructura de datos (https://my-account-here.ds.vtexcrm.com.br);
+- Accede a la pestaña Entidades de Datos:
+ ![](https://vtexhelp.zendesk.com/attachments/token/65UPKYKl3vuaeweF46K91bpI5/?name=image.png)
+
+- Haga clic en el icono del disco para publicar la Entidad de Datos que fue creada o actualizada:
+ ![](https://vtexhelp.zendesk.com/attachments/token/C1nUZnpG8lmDWOL8wrXRBiGj0/?name=image.png)
+
+- A continuación se mostrará el siguiente mensaje:
+ ![](https://vtexhelp.zendesk.com/attachments/token/DFKVanOk3noBMaN8aBd6CQssp/?name=image.png)
+
+    Error inesperado. Vuelva a intentarlo o póngase en contacto con el servicio de atención al cliente.
+
+
+
+
+## Workaround
+
+
+Para estos escenarios, una solución es abrir un ticket para VTEX, para que podamos validar una posible actualización del cluster de esta cuenta.
+
+
+
+
diff --git a/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
index f34973483..4b1c1265c 100644
--- a/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
@@ -29,7 +29,7 @@ El mensaje de autorización de error puede cambiar de `node` a `react` de acuerd
 1. Instalar el VTEX CLI (ToolBelt);
 2. Navegar hasta el directorio de la app;
 3. Ejecutar el comando "vtex-link" en el terminal.
-4. ![image (8)](https://images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
+4. ![image (8)](//images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md b/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md
index 011b2024a..57e336f9a 100644
--- a/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md
+++ b/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md
@@ -3,8 +3,8 @@ title: 'Error al liquidar la transacción con 2 tarjetas - MercadoPagoV1'
 id: 1WFFLHywLePfl5v5IMhili
 status: PUBLISHED
 createdAt: 2022-03-03T21:30:42.237Z
-updatedAt: 2022-11-25T22:05:14.074Z
-publishedAt: 2022-11-25T22:05:14.074Z
+updatedAt: 2024-02-16T20:27:28.600Z
+publishedAt: 2024-02-16T20:27:28.600Z
 firstPublishedAt: 2022-03-03T21:30:42.610Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: error-al-liquidar-la-transaccion-con-2-tarjetas-mercadopagov1
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 395943
 ---
 
diff --git a/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md b/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md
new file mode 100644
index 000000000..81a53eeb0
--- /dev/null
+++ b/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md
@@ -0,0 +1,50 @@
+---
+title: 'Error al intentar publicar o vincular una aplicación'
+id: 2WPukfSHWzzIUjIzMJaAEK
+status: PUBLISHED
+createdAt: 2024-06-27T15:39:00.583Z
+updatedAt: 2024-06-27T19:46:21.021Z
+publishedAt: 2024-06-27T19:46:21.021Z
+firstPublishedAt: 2024-06-27T15:39:01.543Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: error-al-intentar-publicar-o-vincular-una-aplicacion
+locale: es
+kiStatus: Backlog
+internalReference: 1056882
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Nuestro equipo investigó que esto está normalmente asociado con el desarrollo de una aplicación de gran tamaño. Esto ocurre porque el builder hub explota su memoria debido a la gran cantidad de archivos en la app. Los retrasos en la vinculación de la aplicación también pueden estar asociados con este problema.
+
+
+##
+
+## Simulación
+
+
+Pruebe a utilizar `vtex link` en una aplicación con un gran tamaño o muchos archivos. Puedes recibir los siguientes errores:
+
+    11:51:13.298 - error: Workerpool Worker terminated Unexpectedly exitCode: `null` signalCode: `SIGABRT` workerpool.script: `/usr/local/data/service/src/node/utils/workers/worker.js` spawnArgs: `/usr/local/bin/node,/usr/local/data/service/src/node/utils/workers/worker.js` spawnfile: `/usr/local/bin/node` stdout: `null` stderr: `null` vtex.builder-hub@0.299.0 11:51:13.299 - error: App build failed with message: Workerpool Worker terminated Unexpectedly exitCode: `null` signalCode: `SIGABRT` workerpool.script: `/usr/local/data/service/src/node/utils/workers/worker.js` spawnArgs: `/usr/local/bin/node,/usr/local/data/service/src/node/utils/workers/worker.js` spawnfile: `/usr/local/bin/node` stdout: `null` stderr: `null`
+
+    13:30:05.456 - error: La aplicación ha finalizado con el código de salida 15. Se reiniciará en 10s. service-node@6.38.3
+
+
+
+
+## Workaround
+
+
+Analiza el tamaño de la app y sus archivos, si es necesario intenta dividir la app en apps más pequeñas para que el tamaño se reduzca.
+
+
+
+
diff --git a/docs/known-issues/es/event-inconsistency.md b/docs/known-issues/es/event-inconsistency.md
index 4a68d0a23..1424a110e 100644
--- a/docs/known-issues/es/event-inconsistency.md
+++ b/docs/known-issues/es/event-inconsistency.md
@@ -1,36 +1,57 @@
 ---
-title: 'Event Inconsistency'
+title: 'Incoherencia de eventos'
 id: 2YnhehJXuJcsy3f3Rezn6X
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-06-20T23:00:31.430Z
-updatedAt: 2022-06-27T12:52:29.346Z
-publishedAt: 2022-06-27T12:52:28.556Z
+updatedAt: 2024-05-23T12:45:46.343Z
+publishedAt: 2024-05-23T12:45:46.343Z
 firstPublishedAt: 2022-06-20T23:00:31.899Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: event-inconsistency
+slug: incoherencia-de-eventos
 locale: es
-kiStatus: Scheduled
+kiStatus: Fixed
 internalReference: 267299
 ---
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
+
+
+Cuando el usuario realiza un pedido en caja, se inicia un nuevo flujo de pedidos. A partir de este momento, se consulta la pasarela VTEX cuando se identifican los siguientes estados del pedido: "Pendiente de pago" y "Verificando factura". En el estado "Pendiente de pago", se espera que se envíe una notificación de pago al módulo Pedidos. Durante este periodo, pueden producirse algunos problemas con el procesamiento de eventos. Aunque no existe una única causa raíz directamente relacionada con el problema de procesamiento de eventos, cualquier otro problema interno o externo relacionado con el sistema de notificación puede provocar el bloqueo del flujo de pedidos en estado "pendiente de pago".
+
+La cola de mensajes proporciona un protocolo de comunicación asíncrono, en el que los eventos se colocan en una cola para ser consumidos en un momento predeterminado en el futuro. Así pues, ya hemos trazado algunos escenarios en los que se produce una incoherencia en este flujo para clasificarlos y resolverlos uno por uno.
+
+
+- Evento perdido/no generado;
+- Evento atascado y no procesado;
+- Errores de procesamiento que pueden causar inconsistencias en la base de datos.
+
+Este KI se refiere explícitamente a los escenarios mencionados anteriormente y no pretende agotar todas las posibilidades de problemas de procesamiento de eventos que puedan ocurrir. Nuevas causas raíz o problemas relacionados, como malas respuestas del proveedor (algo que ocurre con regularidad), pueden dar lugar a situaciones en las que el pedido quede atascado. Cada caso debe investigarse individualmente para determinar la causa raíz del problema.
+
+
+##
+
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+
+
+No hay forma de simular este comportamiento.
+
+
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+
+Póngase en contacto con nuestro equipo de soporte para volver a procesar manualmente el evento.
+
+
+
+
 
diff --git a/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md b/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
index 8cde39cd7..b940e9319 100644
--- a/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
+++ b/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
@@ -1,10 +1,10 @@
 ---
-title: 'ew UI no sugiere el artículo correcto a devolver una vez que el pedido tiene un cambio'
+title: 'New UI no sugiere el artículo correcto a devolver una vez que el pedido tiene un cambio'
 id: 7hjZaUZ1GNiGjMnSKe0pZu
 status: PUBLISHED
 createdAt: 2023-01-18T17:05:53.889Z
-updatedAt: 2023-01-18T17:05:54.590Z
-publishedAt: 2023-01-18T17:05:54.590Z
+updatedAt: 2024-05-28T18:33:17.977Z
+publishedAt: 2024-05-28T18:33:17.977Z
 firstPublishedAt: 2023-01-18T17:05:54.590Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/es/exclude-products-from-collection-not-working.md b/docs/known-issues/es/exclude-products-from-collection-not-working.md
new file mode 100644
index 000000000..2a93b3f06
--- /dev/null
+++ b/docs/known-issues/es/exclude-products-from-collection-not-working.md
@@ -0,0 +1,52 @@
+---
+title: 'Excluir productos de la colección no funciona.'
+id: 102Z3QRDo07OM6IPJCDlsY
+status: PUBLISHED
+createdAt: 2023-10-20T16:30:13.646Z
+updatedAt: 2023-10-20T16:30:14.840Z
+publishedAt: 2023-10-20T16:30:14.840Z
+firstPublishedAt: 2023-10-20T16:30:14.840Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: excluir-productos-de-la-coleccion-no-funciona
+locale: es
+kiStatus: Backlog
+internalReference: 923016
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La cuenta puede crear colecciones utilizando la versión anterior y añadir colecciones y marcas completas.
+
+Sin embargo, al intentar excluir algunos productos de estas colecciones o marcas utilizando la subcolección "exclusao" no ocurre nada. A pesar de que no aparece ningún mensaje de error, los skus siguen estando en la colección.
+
+
+##
+
+## Simulación
+
+
+
+1. Crear una colección y añadir una categoría en el grupo de subcolección "Inclusão".
+2. 2. Crear un grupo de subcolección "Exclusão" con al menos un producto (todos los skus) en la parte de añadir skus.
+3. 3. Compruebe que el sku sigue estando en la colección;
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md b/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md
new file mode 100644
index 000000000..5b29fc538
--- /dev/null
+++ b/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md
@@ -0,0 +1,50 @@
+---
+title: 'Los redireccionamientos temporales caducados no apuntan a la ruta antigua'
+id: 1kI87EueEtHIyfZ4KmUJSF
+status: PUBLISHED
+createdAt: 2023-09-12T14:41:09.843Z
+updatedAt: 2023-09-12T14:41:11.758Z
+publishedAt: 2023-09-12T14:41:11.758Z
+firstPublishedAt: 2023-09-12T14:41:11.758Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: los-redireccionamientos-temporales-caducados-no-apuntan-a-la-ruta-antigua
+locale: es
+kiStatus: Backlog
+internalReference: 898062
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Cuando se crea una ruta de redirección, la ruta interna se elimina, pero, cuando la redirección expira la ruta no vuelve
+
+
+##
+
+## Simulación
+
+
+
+
+- Crear una redirección temporal
+- Compruébelo y se redirigirá correctamente
+- Después de la fecha de caducidad, compruébelo de nuevo
+- La ruta original no se cargará correctamente
+
+
+
+## Workaround
+
+
+La ruta sólo volverá a funcionar si la crea de nuevo en el rewriter
+
+
+
diff --git a/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md b/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
new file mode 100644
index 000000000..53eaba11f
--- /dev/null
+++ b/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
@@ -0,0 +1,45 @@
+---
+title: 'Interfaz de búsqueda explicada superposición de textos largos entre diferentes áreas o productos'
+id: 5BMYpoif30DAOjPOVHMDfS
+status: PUBLISHED
+createdAt: 2023-09-21T00:25:00.402Z
+updatedAt: 2023-09-21T00:25:00.874Z
+publishedAt: 2023-09-21T00:25:00.874Z
+firstPublishedAt: 2023-09-21T00:25:00.874Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: interfaz-de-busqueda-explicada-superposicion-de-textos-largos-entre-diferentes-areas-o-productos
+locale: es
+kiStatus: Backlog
+internalReference: 904482
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La página de administración de búsqueda explicada tiene problemas con las reglas de comercialización y las áreas de campo de búsqueda cuando una búsqueda o un producto tiene demasiada información allí, textos superpuestos entre diferentes secciones/productos.
+
+
+##
+
+## Simulación
+
+
+Registrar un buen número de palabras en un campo en el que se puedan realizar búsquedas.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md b/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
new file mode 100644
index 000000000..1e647f811
--- /dev/null
+++ b/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
@@ -0,0 +1,41 @@
+---
+title: 'Exportar muchos productos/SKU lleva mucho tiempo y a veces no se puede completar la solicitud.'
+id: 4MBgn0t3jm698ZkkcF1o5G
+status: PUBLISHED
+createdAt: 2022-01-21T14:33:34.881Z
+updatedAt: 2024-02-16T20:25:42.392Z
+publishedAt: 2024-02-16T20:25:42.392Z
+firstPublishedAt: 2024-01-23T15:58:51.944Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: exportar-muchos-productossku-lleva-mucho-tiempo-y-a-veces-no-se-puede-completar-la-solicitud
+locale: es
+kiStatus: No Fix
+internalReference: 284386
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Exportar muchos productos/SKUs lleva mucho tiempo y a veces no se puede completar la solicitud. Este problema también afecta a otras exportaciones de catálogos.
+
+
+##
+
+## Simulación
+
+
+Intente exportar más de 100k productos.
+
+
+## Workaround
+
+
+Utilice el filtro para filtrar los productos en grupos de menos de 10000 productos.
+
diff --git a/docs/known-issues/es/export-redirects-not-working-as-intended.md b/docs/known-issues/es/export-redirects-not-working-as-intended.md
index 88296d810..2cdc3564b 100644
--- a/docs/known-issues/es/export-redirects-not-working-as-intended.md
+++ b/docs/known-issues/es/export-redirects-not-working-as-intended.md
@@ -1,16 +1,16 @@
 ---
-title: 'Los redireccionamientos de exportación no funcionan como es debido'
+title: 'Los redireccionamientos de exportación no funcionan correctamente'
 id: 5WoiJDQCSMDCwCn1auNwC4
 status: PUBLISHED
 createdAt: 2022-04-05T12:53:18.824Z
-updatedAt: 2022-11-25T21:54:34.008Z
-publishedAt: 2022-11-25T21:54:34.008Z
+updatedAt: 2024-01-29T18:40:08.833Z
+publishedAt: 2024-01-29T18:40:08.833Z
 firstPublishedAt: 2022-04-05T12:53:19.875Z
 contentType: knownIssue
-productTeam: CMS
+productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
-tag: CMS
-slug: los-redireccionamientos-de-exportacion-no-funcionan-como-es-debido
+tag: Store Framework
+slug: los-redireccionamientos-de-exportacion-no-funcionan-correctamente
 locale: es
 kiStatus: Backlog
 internalReference: 537962
@@ -24,15 +24,30 @@ internalReference: 537962
 
 
 
-Cuando se intenta exportar la redirección, ya sea a través del terminal o a través de la página en el CMS trae diferentes tamaños de archivo, con posibles resultados diferentes en su interior, este no es el comportamiento esperado ya que no hay cambios realizados en las redirecciones que podrían explicar las diferencias.
+Cuando se intenta exportar la redirección, ya sea a través del terminal o a través de la página en el CMS trae diferentes tamaños de archivos, con posibles resultados diferentes en el interior, este no es el comportamiento esperado ya que no hay cambios realizados en las redirecciones que podrían explicar las diferencias.
 
 
 
+##
+
 ## Simulación
 
 
 
+(Terminal) Siga los pasos de la documentación: https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-managing-url-redirects
+
+Comprueba los ficheros devueltos y podrás ver en algunos casos la diferencia entre los dos ficheros extraídos.
+
+(Admin UI) Ir al admin > CMS > Redirecciones cambiar entre las páginas en la paginación y haga clic en exportar podrás ver las diferencias en los archivos que se devuelven.
+
+
+
 ## Workaround
 
 
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md b/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md
index 650d5b08c..40825268c 100644
--- a/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md
+++ b/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md
@@ -3,13 +3,13 @@ title: 'Exportar el CSV en el módulo de rendimiento de ventas'
 id: 7qnlFfnImq7N6Nrz0xIT8L
 status: PUBLISHED
 createdAt: 2023-05-11T13:42:36.411Z
-updatedAt: 2023-05-11T13:42:37.027Z
-publishedAt: 2023-05-11T13:42:37.027Z
+updatedAt: 2023-09-13T20:08:40.788Z
+publishedAt: 2023-09-13T20:08:40.788Z
 firstPublishedAt: 2023-05-11T13:42:37.027Z
 contentType: knownIssue
-productTeam: Admin
+productTeam: Analytics
 author: 2mXZkbi0oi061KicTExNjo
-tag: Admin
+tag: Analytics
 slug: exportar-el-csv-en-el-modulo-de-rendimiento-de-ventas
 locale: es
 kiStatus: Backlog
diff --git a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
new file mode 100644
index 000000000..021774453
--- /dev/null
+++ b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -0,0 +1,50 @@
+---
+title: "Al exportar imágenes SKU para cuentas que empiezan por 'h','t' o 'p' se corta este carácter en las filas "URL de la imagen"."
+id: 1IZdnE8IGwkBlbcFhjLrzn
+status: PUBLISHED
+createdAt: 2023-10-13T15:20:49.703Z
+updatedAt: 2023-10-13T15:20:50.483Z
+publishedAt: 2023-10-13T15:20:50.483Z
+firstPublishedAt: 2023-10-13T15:20:50.483Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: al-exportar-imagenes-sku-para-cuentas-que-empiezan-por-ht-o-p-se-corta-este-caracter-en-las-filas-url-de-la-imagen
+locale: es
+kiStatus: Backlog
+internalReference: 919199
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El informe de imágenes SKU, /admin/Site/ProdutoImagemExportacao.aspx, para nombres de cuenta que empiezan por "h", "t" o "p", como "testaccount", mostrará un carácter que falta en la hoja de exportación para la fila imageURL.
+
+
+
+## Simulación
+
+
+1 - para una cuenta que comienza con los caracteres iniciales mencionados, vaya a /admin/Site/ProdutoImagemExportacao.aspx y exporte una hoja para cualquier sku que tenga por lo menos 1 imagen.
+2 - abra la hoja exportada y compruebe la columna "UrlImagem": será sin el carácter inicial
+
+Por ejemplo, si la cuenta se llama "testaccount":
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/3VxPtxFSDjU1obEtgqkS16BXM/?name=image.png)
+
+
+
+## Workaround
+
+
+Cree una subcuenta que empiece por otro carácter (por ejemplo, "mytestaccount") y acceda a la interfaz de usuario de exportación utilizando esta subcuenta. La exportación mostrará entonces la cadena URL completa sin ningún recorte incorrecto.
+
+
+
+
+
diff --git a/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md b/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
new file mode 100644
index 000000000..a8a9e77ac
--- /dev/null
+++ b/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
@@ -0,0 +1,54 @@
+---
+title: '[Facebook] Hoy Facebook mira sellingPrice y listPrice para actualizar el precio en el catálogo de Facebook'
+id: 4CDh12JM3y9AqBnuGDHgnT
+status: PUBLISHED
+createdAt: 2024-04-03T12:41:15.144Z
+updatedAt: 2024-04-03T12:41:16.005Z
+publishedAt: 2024-04-03T12:41:16.005Z
+firstPublishedAt: 2024-04-03T12:41:16.005Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: facebook-hoy-facebook-mira-sellingprice-y-listprice-para-actualizar-el-precio-en-el-catalogo-de-facebook
+locale: es
+kiStatus: Backlog
+internalReference: 924411
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Hoy Facebook mira sellingPrice y listPrice para actualizar el precio en el catálogo de Facebook.
+
+
+##
+
+## Simulación
+
+
+El vendedor utiliza unitMultiplier = 0.5
+
+Checkout realiza el siguiente cálculo cuando el artículo tiene una unidad multiplicadora, por lo que sellingPrice = price * unitMultiplier = 3999 * 0.5 = 1999.5. El redondeo de Checkout ignorará el decimal y considerará 1999
+
+¿Cuál es el problema con este cálculo?
+Cuando el vendedor utiliza 0,5, por ejemplo, en Facebook lo estamos actualizando como el precio de liquidación en Facebook.
+2. Cuando el vendedor utiliza un multiplicador superior a 1,39, entra dentro del precio promocional aunque sea superior al listPrice
+
+
+
+##
+
+## Workaround
+
+
+vendedor usa multiplicador unitario = 10000
+
+
+
+
+
diff --git a/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md b/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
new file mode 100644
index 000000000..c35d18ea3
--- /dev/null
+++ b/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
@@ -0,0 +1,51 @@
+---
+title: 'Facetas del Segmento que afectan a las migas de pan, al título de la página y a los filtros adicionales'
+id: 3lBgcsjxiZxoDvnPhbMXgo
+status: PUBLISHED
+createdAt: 2024-06-27T22:57:42.875Z
+updatedAt: 2024-06-27T22:57:43.965Z
+publishedAt: 2024-06-27T22:57:43.965Z
+firstPublishedAt: 2024-06-27T22:57:43.965Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: facetas-del-segmento-que-afectan-a-las-migas-de-pan-al-titulo-de-la-pagina-y-a-los-filtros-adicionales
+locale: es
+kiStatus: Backlog
+internalReference: 1057254
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La propiedad "facets" almacenada en el Segmento/Sesión para un contexto de navegación funciona para limitar los resultados de búsqueda a filtros predefinidos. Por ejemplo, es utilizada por "Organizaciones B2B" para restringir lo que un usuario puede ver en la tienda.
+
+Estas facetas pueden afectar al comportamiento de los títulos de página y las migas de pan generando valores inesperados que no forman parte de los filtros aplicados en la página. Se tienen en cuenta todos los filtros al generar estos valores, no sólo los filtros explícitos de la página, que deberían ignorar las facetas de Segmento.
+
+También puede afectar a la URL de la página al aplicar filtros adicionales, que se fusionarán con las facetas de Segment.
+
+
+##
+
+## Simulación
+
+
+
+- Adjunte un usuario a una organización B2B que esté limitada a algunas colecciones de productos (A);
+- Crear una página de destino que muestre una colección diferente (B);
+- Las migas de pan y el título de la página pueden mostrar el nombre de la colección A en lugar de la colección B
+- Seleccione filtros de búsqueda adicionales en la página de destino, como categoría o marca;
+- Observe que la URL (y también las migas de pan y el título de la página) también mostrarán la colección A en lugar de limitarse a la colección B.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md b/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md
index 3a734a946..c50e48c46 100644
--- a/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md
+++ b/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md
@@ -3,8 +3,8 @@ title: 'Fallo en la cancelación (PPP) cuando cancellationId=null'
 id: 4yNCRQ1xhA8lEp5AGRs5eu
 status: PUBLISHED
 createdAt: 2022-06-21T21:37:04.567Z
-updatedAt: 2022-11-25T22:07:04.838Z
-publishedAt: 2022-11-25T22:07:04.838Z
+updatedAt: 2023-08-11T19:16:35.985Z
+publishedAt: 2023-08-11T19:16:35.985Z
 firstPublishedAt: 2022-06-21T21:37:05.374Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: fallo-en-la-cancelacion-ppp-cuando-cancellationidnull
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 333897
 ---
 
diff --git a/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
new file mode 100644
index 000000000..3edece709
--- /dev/null
+++ b/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -0,0 +1,48 @@
+---
+title: 'Si no se añaden los datos en el paso "entregar en otra dirección", desaparece el botón "ir al pago".'
+id: cdZO8gGXDB1JZSj42AnVh
+status: PUBLISHED
+createdAt: 2022-01-24T21:42:52.750Z
+updatedAt: 2023-10-13T15:29:14.854Z
+publishedAt: 2023-10-13T15:29:14.854Z
+firstPublishedAt: 2023-10-13T15:29:14.854Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: si-no-se-anaden-los-datos-en-el-paso-entregar-en-otra-direccion-desaparece-el-boton-ir-al-pago
+locale: es
+kiStatus: Backlog
+internalReference: 467419
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Durante la etapa de pago, en el paso de rellenar los datos de envío, pulsando sobre la opción "Entregar en otra dirección", si no se añade ninguna dirección y el comprador vuelve a la lista de direcciones (utilizando el botón "volver a la libreta de direcciones") el botón "Ir al pago" desaparece.
+
+
+##
+
+## Simulación
+
+
+
+- Durante la etapa de Pago, al rellenar los datos de envío, si hay una lista de direcciones, haga clic en "Entregar en otra dirección";
+- No añada ninguna dirección y vuelva a los datos de envío pulsando el botón "Volver a la lista de direcciones";
+- El botón "Ir al pago" desaparece.
+
+
+
+## Workaround
+
+
+Para que el botón vuelva a aparecer, basta con hacer clic en una de las direcciones de la libreta de direcciones. Sin embargo, no existe ninguna solución para evitar este comportamiento.
+
+
+
+
diff --git a/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md b/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md
new file mode 100644
index 000000000..cc61c75cd
--- /dev/null
+++ b/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md
@@ -0,0 +1,46 @@
+---
+title: 'El carro FastStore fusiona los artículos de la cadena de montaje'
+id: 4NBNaTZpr6PnRxPfrtGj77
+status: PUBLISHED
+createdAt: 2024-06-14T17:25:47.764Z
+updatedAt: 2024-06-14T17:25:48.655Z
+publishedAt: 2024-06-14T17:25:48.655Z
+firstPublishedAt: 2024-06-14T17:25:48.655Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: el-carro-faststore-fusiona-los-articulos-de-la-cadena-de-montaje
+locale: es
+kiStatus: Backlog
+internalReference: 1050068
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si la misma opción de montaje se añade a diferentes productos FastStore los fusionará en una única partida.
+
+
+##
+
+## Simulación
+
+
+Intente añadir al carrito dos o más productos que tengan la misma opción de montaje, los productos se añadirán en la misma línea
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md b/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
new file mode 100644
index 000000000..7a4b6ecb1
--- /dev/null
+++ b/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
@@ -0,0 +1,50 @@
+---
+title: 'Faststore facets considerando no eliminar facets configuradas como ne hidden'
+id: 4EElvOEvMzcu52fhNOVJGM
+status: PUBLISHED
+createdAt: 2024-05-08T18:35:17.015Z
+updatedAt: 2024-05-08T18:36:15.922Z
+publishedAt: 2024-05-08T18:36:15.922Z
+firstPublishedAt: 2024-05-08T18:35:18.742Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-facets-considerando-no-eliminar-facets-configuradas-como-ne-hidden
+locale: es
+kiStatus: Backlog
+internalReference: 1029837
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+El comportamiento esperado en la API de facetas IS es no traer facetas con hidden true, pero, hay algunas excepciones para eso, por ejemplo cuando la faceta es seleccionada en la consulta, la API trae la faceta en los resultados con la prop hidden como true, y no estamos considerando esta información
+
+
+
+## Simulación
+
+
+
+Filtro para una consulta con la faceta oculta, como por ejemplo:
+
+https://storeframework.vtex.app/new-collection?productclusternames=new-collection&fuzzy=0&operator=and&facets=productclusternames%2Cfuzzy%2Coperator&sort=score_desc&page=0
+
+En este caso, productClusterNames está oculto pero, como se está filtrando, aparece en el navegador de filtros
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md b/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md
new file mode 100644
index 000000000..47a2d383b
--- /dev/null
+++ b/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md
@@ -0,0 +1,46 @@
+---
+title: 'Faststore search api considerando fuzzy como auto por defecto'
+id: 2zedXBMhlD8pu4gZMXsrSp
+status: PUBLISHED
+createdAt: 2023-08-28T23:35:04.009Z
+updatedAt: 2024-03-27T14:10:53.090Z
+publishedAt: 2024-03-27T14:10:53.090Z
+firstPublishedAt: 2023-08-28T23:35:04.608Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-search-api-considerando-fuzzy-como-auto-por-defecto
+locale: es
+kiStatus: Fixed
+internalReference: 889321
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el paquete @fatstore/api, para el Intelligent Search resolver, estamos considerando fuzzy como auto por defecto cuando deberia ser 0, esto esta causando que el comportamiento de fuzzy se aplique causando un "fake missmatch" en los resultados de busqueda cuando realmente tenemos una coincidencia exacta con el termino buscado, pero, mostramos mas resultados a pesar de que
+
+
+##
+
+## Simulación
+
+
+Esto es fácil de replicar cuando se busca cualquier producto, sku, o ref ID, el resultado esperado es mostrar sólo los productos que coincide con el ID, pero, se mostrará más de uno
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md b/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md
new file mode 100644
index 000000000..eafd9c54c
--- /dev/null
+++ b/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md
@@ -0,0 +1,49 @@
+---
+title: 'Faststore V1 no devuelve información SEO en la consulta Graphql'
+id: 4nZnX8sj9J90xtkNpYIgZ4
+status: PUBLISHED
+createdAt: 2023-11-01T17:08:35.090Z
+updatedAt: 2023-11-01T17:13:13.061Z
+publishedAt: 2023-11-01T17:13:13.061Z
+firstPublishedAt: 2023-11-01T17:08:35.767Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: faststore-v1-no-devuelve-informacion-seo-en-la-consulta-graphql
+locale: es
+kiStatus: No Fix
+internalReference: 929029
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al acceder al playground de Graphql para ejecutar consultas en Faststore V1 tenemos una consulta de producto. La documentación indica que el campo SEO de esa consulta debería devolver la información SEO, pero esto no está ocurriendo.
+
+
+##
+
+## Simulación
+
+
+
+- accede a tu tienda usando el playground Graphql
+- ejecute la consulta de productos con los campos SEO
+- compare con la información SEO del producto en el catálogo
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md b/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
index c851859ee..eadd9a388 100644
--- a/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
+++ b/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
@@ -3,8 +3,8 @@ title: 'FetchMore mantiene el estado de nextPage y se bloquea la paginación'
 id: 3hyeUjVRNKE8A2UYIQiw2x
 status: PUBLISHED
 createdAt: 2022-04-11T20:53:26.480Z
-updatedAt: 2022-11-25T21:58:27.486Z
-publishedAt: 2022-11-25T21:58:27.486Z
+updatedAt: 2024-07-01T18:48:17.176Z
+publishedAt: 2024-07-01T18:48:17.176Z
 firstPublishedAt: 2022-04-11T20:53:26.870Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: fetchmore-mantiene-el-estado-de-nextpage-y-se-bloquea-la-paginacion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 560014
 ---
 
diff --git a/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md b/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
index a3b7f73d3..5c962c5f4 100644
--- a/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
+++ b/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
@@ -3,8 +3,8 @@ title: 'Los decimales del campo de la moneda en la política comercial no se ref
 id: 1QxxwRvFDUVnGHh5icIPpo
 status: PUBLISHED
 createdAt: 2022-11-09T17:40:35.832Z
-updatedAt: 2022-11-25T21:41:45.862Z
-publishedAt: 2022-11-25T21:41:45.862Z
+updatedAt: 2024-02-16T20:24:30.832Z
+publishedAt: 2024-02-16T20:24:30.832Z
 firstPublishedAt: 2022-11-09T17:40:36.610Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: los-decimales-del-campo-de-la-moneda-en-la-politica-comercial-no-se-reflejan-en-el-pdp-plp
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 695044
 ---
 
diff --git a/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index c5cbdc8b9..9e397f9ce 100644
--- a/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -1,18 +1,18 @@
 ---
-title: 'El campo "Cambios y devoluciones" no se actualiza en la interfaz de gestión del vendedor después de guardar'
+title: 'El campo "Cambios y devoluciones" no se actualiza en la interfaz de usuario de gestión de vendedores después de guardar.'
 id: 1z8LrsbGk5B2ejZ1PV9vaB
 status: PUBLISHED
 createdAt: 2022-11-01T17:47:30.359Z
-updatedAt: 2022-11-25T22:00:22.743Z
-publishedAt: 2022-11-25T22:00:22.743Z
+updatedAt: 2023-10-30T19:28:26.143Z
+publishedAt: 2023-10-30T19:28:26.143Z
 firstPublishedAt: 2022-11-01T17:47:31.132Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
-slug: el-campo-cambios-y-devoluciones-no-se-actualiza-en-la-interfaz-de-gestion-del-vendedor-despues-de-guardar
+slug: el-campo-cambios-y-devoluciones-no-se-actualiza-en-la-interfaz-de-usuario-de-gestion-de-vendedores-despues-de-guardar
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 689886
 ---
 
@@ -23,32 +23,31 @@ internalReference: 689886
 </div>
 
 
-
 Después de guardar el campo "Cambios y devoluciones" en la UI la información se actualiza por primera vez pero si intentamos salir del área de gestión o refrescar la página la información se pierde.
 
-
-
-La información mostrada en la UI es la misma que la del campo "Política de envíos".
-
-
+La información que se muestra en la UI es la misma que la del campo "Política de envíos".
 
 Sin embargo, esto parece estar ocurriendo sólo en la interfaz de usuario, a través de la API la información es correcta.
 
 
-
+##
 
 ## Simulación
 
 
 
 1. Introduzca un vendedor en el área de gestión de vendedores;
-2. Cambia la información en el campo "Cambios y devoluciones" y guarda;
-3. 3. Volver a entrar en el mismo vendedor y comprobar que la información es correcta.
+2. Cambia la información del campo "Cambios y devoluciones" y guarda;
+3. 3. Vuelva a introducir el mismo vendedor y compruebe que la información es correcta.
 
 
 
 ## Workaround
 
 
-No hay necesidad de hacer un workaround, la información es correcta en el backend del sistema.
+No hay necesidad de solución, la información es correcta en el backend del sistema.
+
+
+
+
 
diff --git a/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md b/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
index 4728cb705..f9b3ae078 100644
--- a/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
+++ b/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
@@ -3,16 +3,16 @@ title: 'Los campos de la configuración de orderForm se actualizan a null cuando
 id: jKGnwUGdfmCXtKjGPe6hj
 status: PUBLISHED
 createdAt: 2023-02-06T21:00:09.224Z
-updatedAt: 2023-04-03T14:22:00.794Z
-publishedAt: 2023-04-03T14:22:00.794Z
+updatedAt: 2024-05-09T12:44:51.823Z
+publishedAt: 2024-05-09T12:44:51.823Z
 firstPublishedAt: 2023-02-06T21:00:09.753Z
 contentType: knownIssue
-productTeam: Checkout
+productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
-tag: Checkout
+tag: Order Management
 slug: los-campos-de-la-configuracion-de-orderform-se-actualizan-a-null-cuando-se-produce-algun-cambio-en-la-configuracion-de-la-gestion-de-pedidos
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 748404
 ---
 
@@ -33,7 +33,7 @@ Al actualizar cualquier información en la configuración de la gestión de pedi
 
 - Establezca los campos `paymentSystemToCheckFirstInstallment` y `defaultPaymentSystemToApplyOnUserOrderForm` en la configuración de orderForm a través de la API.
 - Cambiar cualquier cosa en la configuración de gestión de pedidos (admin)
-- Cuando haga Get orderForm Configuration, verá esos campos como `null`.
+- Cuando obtenga la configuración de orderForm, verá esos campos como "nulos".
 
 
 
diff --git a/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md b/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
index d6e070cc9..71aa9402a 100644
--- a/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
+++ b/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
@@ -1,18 +1,18 @@
 ---
-title: 'La carga del Administrador de Archivos con dos o más archivos existentes no actualiza todos los archivos, sólo el primero'
+title: 'La carga de archivos con dos o más archivos existentes no actualiza todos los archivos, sólo el primero.'
 id: 2LHdzsFFe83E1Tf0Z4j66y
 status: PUBLISHED
 createdAt: 2022-03-17T00:20:51.454Z
-updatedAt: 2022-11-25T22:10:54.509Z
-publishedAt: 2022-11-25T22:10:54.509Z
+updatedAt: 2024-02-16T20:23:18.080Z
+publishedAt: 2024-02-16T20:23:18.080Z
 firstPublishedAt: 2022-03-17T00:20:52.317Z
 contentType: knownIssue
 productTeam: Portal
 author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
-slug: la-carga-del-administrador-de-archivos-con-dos-o-mas-archivos-existentes-no-actualiza-todos-los-archivos-solo-el-primero
+slug: la-carga-de-archivos-con-dos-o-mas-archivos-existentes-no-actualiza-todos-los-archivos-solo-el-primero
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 418253
 ---
 
@@ -23,25 +23,26 @@ internalReference: 418253
 </div>
 
 
-La carga del Administrador de Archivos con dos o más archivos existentes no actualiza todos los archivos, sólo el primero
+La carga de archivos con dos o más archivos existentes no actualiza todos los archivos, sólo el primero.
 
 
+##
 
 ## Simulación
 
 
 - Ve a /admin/a, administrador de archivos, y añade 2 o más archivos para subir;
 - Ahora sube otros dos archivos con el mismo nombre:
-- Recibiremos un aviso diciéndonos que el archivo existe, preguntándonos si queremos reemplazarlo.
+- Recibiremos un aviso indicándonos que el fichero existe, preguntándonos si queremos reemplazarlo.
 
-Esta advertencia nos está diciendo sólo sobre un archivo, el segundo no está siendo validado.
+Esta advertencia nos está diciendo sólo acerca de un archivo, el segundo no está siendo validado.
 
-- Ambos archivos se cargan, pero sólo uno reemplazará al más antiguo.
+- Ambos archivos se cargan, pero sólo uno reemplazará al anterior.
 
 
 
 ## Workaround
 
 
-Actualizar un archivo por vez.
+Actualice un archivo cada vez.
 
diff --git a/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md b/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
index d2c7f2929..f8d1efc3b 100644
--- a/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
+++ b/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
@@ -3,8 +3,8 @@ title: ' El filtro por SkuName en Sales Performance no acepta mayúsculas.'
 id: 3FCDeEn8xmEvOXKgBxqyL5
 status: PUBLISHED
 createdAt: 2022-08-16T18:06:02.919Z
-updatedAt: 2022-11-30T19:08:14.148Z
-publishedAt: 2022-11-30T19:08:14.148Z
+updatedAt: 2024-02-16T20:24:21.760Z
+publishedAt: 2024-02-16T20:24:21.760Z
 firstPublishedAt: 2022-08-16T18:06:03.474Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: el-filtro-por-skuname-en-sales-performance-no-acepta-mayusculas
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639219
 ---
 
diff --git a/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
new file mode 100644
index 000000000..fe472dd0d
--- /dev/null
+++ b/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -0,0 +1,47 @@
+---
+title: 'El filtro "productClusterIds" es sobrescrito por "productClusterNames" al aplicar filtros adicionales'
+id: 3d4BIZQBZgeK3eKwT8B1PZ
+status: PUBLISHED
+createdAt: 2023-09-13T22:42:57.138Z
+updatedAt: 2023-09-21T18:04:57.946Z
+publishedAt: 2023-09-21T18:04:57.946Z
+firstPublishedAt: 2023-09-13T22:42:57.682Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: el-filtro-productclusterids-es-sobrescrito-por-productclusternames-al-aplicar-filtros-adicionales
+locale: es
+kiStatus: Backlog
+internalReference: 899508
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se inicia una búsqueda desde el filtro "productClusterIds", al aplicar cualquier filtro adicional se convertirá en "productClusterNames", perdiendo la característica de presentar los ítems con la ordenación definida manualmente en la colección de productos.
+
+
+##
+
+## Simulación
+
+
+El escenario se puede ver en cualquier página, como `"store.com/111?map=productClusterIds"`, y aplicando cualquier filtro adicional, como una categoría, especificación, etc.
+
+El usuario será dirigido a `"store.com/clothing/special-sale?initialMap=productClusterIds&initialQuery=111&map=category,productclusternames"`.
+
+
+
+## Workaround
+
+
+No hay ninguna solución para el problema específico si necesita la clasificación especial, pero asegúrese de utilizar "productClusterIds" sólo en los casos necesarios. De lo contrario, utilice el filtro como "productClusterNames".
+
+
+
+
diff --git a/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md b/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md
new file mode 100644
index 000000000..db4449183
--- /dev/null
+++ b/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md
@@ -0,0 +1,53 @@
+---
+title: 'Filtros por especificaciones SKU sin tener en cuenta la disponibilidad regionalizada'
+id: 3CeTfHaNBfhrC5qIi3nTLh
+status: PUBLISHED
+createdAt: 2024-06-05T20:52:53.211Z
+updatedAt: 2024-06-05T20:52:54.055Z
+publishedAt: 2024-06-05T20:52:54.055Z
+firstPublishedAt: 2024-06-05T20:52:54.055Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: filtros-por-especificaciones-sku-sin-tener-en-cuenta-la-disponibilidad-regionalizada
+locale: es
+kiStatus: Backlog
+internalReference: 1045111
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al filtrar la búsqueda por una especificación de SKU también se aplicará un filtro por disponibilidad de SKU, eliminando los productos en los que la variación seleccionada esté agotada, pero no se aplica a las tiendas regionalizadas.
+
+Las navegaciones regionalizadas pueden devolver productos en los que la variación filtrada no está disponible porque la disponibilidad indexada para una especificación SKU se basa en todos los vendedores habituales y de marca blanca.
+
+
+##
+
+## Simulación
+
+
+Considerando una tienda con dos vendedores y la siguiente matriz de disponibilidad para un producto específico:
+
+- tamaño: pequeño; vendedor A: disponible; vendedor B: no disponible
+- talla: grande; vendedor A: no disponible; vendedor B: no disponible
+
+En una navegación con "regionId: vendedor B", al filtrar por "talla: pequeña" se obtendrá el producto (ya que estaría disponible) y con "talla: grande" se ocultará el producto (porque no está disponible en todas partes).
+
+
+##
+
+## Workaround
+
+
+NO DISPONIBLE
+
+
+
+
diff --git a/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md b/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
new file mode 100644
index 000000000..d7631e653
--- /dev/null
+++ b/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
@@ -0,0 +1,42 @@
+---
+title: 'Los filtros ocultos en la tienda también se ocultan en las páginas de administración de la Búsqueda Inteligente.'
+id: 3TvpIUFzdXWesADHDhjyLQ
+status: PUBLISHED
+createdAt: 2022-02-23T21:59:22.607Z
+updatedAt: 2023-10-19T16:24:57.801Z
+publishedAt: 2023-10-19T16:24:57.801Z
+firstPublishedAt: 2022-02-23T21:59:22.977Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-filtros-ocultos-en-la-tienda-tambien-se-ocultan-en-las-paginas-de-administracion-de-la-busqueda-inteligente
+locale: es
+kiStatus: Backlog
+internalReference: 416638
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas especificaciones tienen un uso interno o escenarios que necesitan ser ocultados, pero la tienda necesita esa especificación para propósitos de la búsqueda, como usarlo para Reglas de Mercadeo.
+
+
+##
+
+## Simulación
+
+
+En algunas cuentas, la especificación SKU "color" no aparece como opción en "Utilizar especificaciones SKU para mostrar productos individuales en los resultados de búsqueda". Vemos que "color" es una de las especificaciones en "Ocultar facetas".
+
+
+
+## Workaround
+
+
+Elimine el atributo de la configuración de "Ocultar facetas", cree la regla de comercialización o realice la configuración esperada y vuelva a ocultar el atributo.
+
diff --git a/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md b/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
new file mode 100644
index 000000000..e2a7a5cf0
--- /dev/null
+++ b/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
@@ -0,0 +1,48 @@
+---
+title: 'Dominio final diferente de myvtex debido a la versión antigua del componente en el Editor de Sitios'
+id: 7bf2mMbpcxUd6Q32DYP6vz
+status: PUBLISHED
+createdAt: 2023-12-05T18:07:50.089Z
+updatedAt: 2024-01-26T17:52:03.169Z
+publishedAt: 2024-01-26T17:52:03.169Z
+firstPublishedAt: 2023-12-05T18:07:50.675Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: dominio-final-diferente-de-myvtex-debido-a-la-version-antigua-del-componente-en-el-editor-de-sitios
+locale: es
+kiStatus: Backlog
+internalReference: 948071
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+A veces puedes hacer cambios en el Editor de Sitios y esos cambios se reflejan en el entorno myvtex, pero cuando intentas actualizar el dominio final, esos cambios no se reflejan. Esto ocurre normalmente cuando el componente que intentas cambiar tiene más de una versión. El front sigue utilizando la versión inactiva del componente mientras que el myvtex está utilizando la versión activa. La única forma de solucionar esto es borrando la versión inactiva del componente.
+
+
+##
+
+## Simulación
+
+
+
+- Intenta cambiar algo en el editor del sitio en una nueva versión de un componente
+- Comprueba si tus cambios se reflejan en el dominio final y en el entorno myvtex
+
+
+
+## Workaround
+
+
+Elimine la versión antigua, esto hará que el dominio final utilice la versión correcta del componente
+
+
+
+
+
diff --git a/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md b/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
new file mode 100644
index 000000000..cf0b7e7ea
--- /dev/null
+++ b/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
@@ -0,0 +1,48 @@
+---
+title: 'La primera dirección de la lista de direcciones incompleta no rellena los datos de perfil/envío en el pago'
+id: 2AqDZb1AGBjmeMOBU0JkLQ
+status: PUBLISHED
+createdAt: 2024-01-03T20:44:07.692Z
+updatedAt: 2024-01-03T20:49:41.249Z
+publishedAt: 2024-01-03T20:49:41.249Z
+firstPublishedAt: 2024-01-03T20:44:11.604Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-primera-direccion-de-la-lista-de-direcciones-incompleta-no-rellena-los-datos-de-perfilenvio-en-el-pago
+locale: es
+kiStatus: Backlog
+internalReference: 366975
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario tiene más de una dirección en su perfil y la primera dirección de la lista de direcciones está incompleta, independientemente de que las demás sean válidas, la caja no rellena automáticamente sus datos de perfil/envío después de añadir su correo electrónico.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir 2 direcciones a un perfil, donde la 1ª está incompleta;
+- Montar un carrito, y añadir el email;
+- No se rellena ningún dato del perfil/dirección.
+
+
+
+## Workaround
+
+
+Elimine la dirección incompleta del perfil a través de Datos maestros
+
+
+
+
diff --git a/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md b/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
new file mode 100644
index 000000000..a3431633d
--- /dev/null
+++ b/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
@@ -0,0 +1,47 @@
+---
+title: 'El primer dígito se elimina de corporateDocument si empieza por letras'
+id: sfKdoiEwBRR73CbhvSHJF
+status: PUBLISHED
+createdAt: 2023-10-17T17:26:20.683Z
+updatedAt: 2024-03-14T22:02:01.236Z
+publishedAt: 2024-03-14T22:02:01.236Z
+firstPublishedAt: 2023-10-17T17:26:21.490Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: el-primer-digito-se-elimina-de-corporatedocument-si-empieza-por-letras
+locale: es
+kiStatus: Fixed
+internalReference: 920703
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el documento corporativo de una organización comienza con letras, el primer dígito se elimina después de acceder a la comprobación.
+
+
+##
+
+## Simulación
+
+
+
+- Registrar una organización cuyo documento corporativo empiece por letras;
+- Añadir artículos a la cesta;
+- Ir a la caja y comprobar el orderForm, se eliminará el primer dígito del campo corporateDocument.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/first-subscription-cycle-is-skipped.md b/docs/known-issues/es/first-subscription-cycle-is-skipped.md
new file mode 100644
index 000000000..314895ba3
--- /dev/null
+++ b/docs/known-issues/es/first-subscription-cycle-is-skipped.md
@@ -0,0 +1,54 @@
+---
+title: 'Se salta el primer ciclo de suscripción'
+id: 2VX6uoop56wK6jecAly40G
+status: PUBLISHED
+createdAt: 2024-02-05T14:10:40.701Z
+updatedAt: 2024-02-05T14:10:41.599Z
+publishedAt: 2024-02-05T14:10:41.599Z
+firstPublishedAt: 2024-02-05T14:10:41.599Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: se-salta-el-primer-ciclo-de-suscripcion
+locale: es
+kiStatus: Backlog
+internalReference: 528556
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El sistema de suscripción utiliza información como la frecuencia de compra y la fecha del ciclo de suscripción para generar un pedido de suscripción. Sin embargo, en función de la zona horaria del consumidor y de la hora a la que se realiza el pedido, se omite el primer ciclo y sólo se genera el segundo mes.
+Supongamos que el 9 de mayo, a las 23.00 horas, un cliente creó una suscripción mensual y fijó la fecha del ciclo de suscripción para el día 9 de cada mes, esperando que el primer pedido se realizara el 9 de junio.
+El sistema de gestión de pedidos funciona en la zona horaria establecida previamente en la tienda. En este caso, consideraremos GMT-5, hora de Chicago. Sin embargo, el sistema de suscripción opera en la zona horaria GMT 0. Esto significa que, aunque la suscripción se haya creado a las 11 de la noche, el sistema de suscripciones considera que se creó 5 horas más tarde, por tanto, el 10 de mayo.
+En este caso, el sistema tiene en cuenta la fecha de creación de la suscripción, el 10 de mayo, para calcular el siguiente ciclo de suscripción. Como la fecha del ciclo de suscripción, el 9 de junio, no cumpliría la condición del periodo de 30 días, en total 29 días, el sistema fija la siguiente fecha de compra para julio. Por lo tanto, el cliente acaba recibiendo el producto después de la fecha prevista.
+
+
+##
+
+## Simulación
+
+
+Tenga una SKU configurada para suscripción, con frecuencia mensual y día de compra;
+Realizar un pedido después de las 23 horas, por ejemplo.
+Comprobar que el primer ciclo, que debería generarse en el mes siguiente, se saltará, generándose sólo en el segundo mes.
+
+
+
+##
+
+## Workaround
+
+
+n/a
+
+
+
+
+
+
diff --git a/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md b/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
index 6e294e43c..8441252d4 100644
--- a/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
+++ b/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
@@ -3,8 +3,8 @@ title: 'Precio fijo que se crea en la política comercial 1 al guardar los preci
 id: 3Xbh5GVn0jm2yhaOiRg3Le
 status: PUBLISHED
 createdAt: 2022-11-28T12:41:07.808Z
-updatedAt: 2022-11-28T12:41:08.426Z
-publishedAt: 2022-11-28T12:41:08.426Z
+updatedAt: 2024-02-16T20:24:01.848Z
+publishedAt: 2024-02-16T20:24:01.848Z
 firstPublishedAt: 2022-11-28T12:41:08.426Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: precio-fijo-que-se-crea-en-la-politica-comercial-1-al-guardar-los-precios-de-los-paquetes
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 705869
 ---
 
diff --git a/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index 7930c6c65..9e4e89b9e 100644
--- a/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -3,8 +3,8 @@ title: 'El mercado externo FOB integra un pedido (código Erro: "FMT010")'
 id: 3qzV4zJRkPIwQnAZuK5dWu
 status: PUBLISHED
 createdAt: 2022-02-25T16:33:49.641Z
-updatedAt: 2022-11-25T22:00:10.646Z
-publishedAt: 2022-11-25T22:00:10.646Z
+updatedAt: 2024-02-16T20:26:31.795Z
+publishedAt: 2024-02-16T20:26:31.795Z
 firstPublishedAt: 2022-02-25T16:33:50.398Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: el-mercado-externo-fob-integra-un-pedido-codigo-erro-fmt010
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 532377
 ---
 
diff --git a/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md b/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
index 6285a221b..a12e8cedc 100644
--- a/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
+++ b/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
@@ -3,8 +3,8 @@ title: 'La promoción de envío gratuito se está aplicando en pedidos divididos
 id: APAIGZx8tdtIjGsQJmvgu
 status: PUBLISHED
 createdAt: 2023-01-12T16:19:47.878Z
-updatedAt: 2023-01-12T16:19:48.479Z
-publishedAt: 2023-01-12T16:19:48.479Z
+updatedAt: 2024-02-16T20:23:58.107Z
+publishedAt: 2024-02-16T20:23:58.107Z
 firstPublishedAt: 2023-01-12T16:19:48.479Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: la-promocion-de-envio-gratuito-se-esta-aplicando-en-pedidos-divididos-fuera-de-la-restriccion-de-la-promocion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 732302
 ---
 
diff --git a/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md b/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
new file mode 100644
index 000000000..2630ea38b
--- /dev/null
+++ b/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
@@ -0,0 +1,51 @@
+---
+title: 'La limpieza completa de vendedores no funciona si la cuenta tiene grupos de vendedores en Gestión de vendedores.'
+id: 3U9tS11FQU0JLUxEDSt5rL
+status: PUBLISHED
+createdAt: 2023-10-19T19:54:36.389Z
+updatedAt: 2024-07-01T18:49:14.530Z
+publishedAt: 2024-07-01T18:49:14.530Z
+firstPublishedAt: 2023-10-19T19:54:37.266Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: la-limpieza-completa-de-vendedores-no-funciona-si-la-cuenta-tiene-grupos-de-vendedores-en-gestion-de-vendedores
+locale: es
+kiStatus: No Fix
+internalReference: 922541
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el área de Gestión de Vendedores el marketplace puede agrupar a sus vendedores como desee y gestionarlos en la pestaña de gestión de grupos.
+
+Sin embargo, si desean eliminar todos los datos de los vendedores en el área de limpieza completa, el proceso fallará si hay grupos creados.
+
+
+##
+
+## Simulación
+
+
+
+1. Cree un grupo de vendedores en Gestión de vendedores;
+2. Realizar una limpieza completa del vendedor;
+3. Compruebe que aparece un error.
+
+
+
+## Workaround
+
+
+En primer lugar, elimine los grupos de vendedores manualmente en la gestión de vendedores y, a continuación, intente realizar de nuevo la limpieza completa de vendedores.
+
+
+
+
+
diff --git a/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md b/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
new file mode 100644
index 000000000..128a2fc97
--- /dev/null
+++ b/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
@@ -0,0 +1,47 @@
+---
+title: 'El evento de compra GA4 no tiene el árbol de categorías en item_category en dataLayer'
+id: 6GCrgcG8PJHaZp80hi4Gb1
+status: PUBLISHED
+createdAt: 2023-07-12T16:42:17.087Z
+updatedAt: 2023-07-12T16:43:37.976Z
+publishedAt: 2023-07-12T16:43:37.976Z
+firstPublishedAt: 2023-07-12T16:42:17.674Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-evento-de-compra-ga4-no-tiene-el-arbol-de-categorias-en-itemcategory-en-datalayer
+locale: es
+kiStatus: Backlog
+internalReference: 860655
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El evento de compra GA4 no tiene el árbol de categorías en item_category en dataLayer, por lo que la única categoría disponible es la categoría de último nivel del producto.
+
+
+##
+
+## Simulación
+
+
+
+- Configurar la aplicación Google Tag Manager y activar "Enviar eventos de Google Analytics 4";
+- Finalice una compra;
+- En la consola, compruebe los eventos en dataLayer; sólo habrá la categoría de último nivel en item_category.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md b/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
index ce2a4d1dd..90e229f12 100644
--- a/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
+++ b/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
@@ -3,8 +3,8 @@ title: 'Los datos de GeoCoordinates no pueden ser informados para algunos cultur
 id: 4MjLbyrniWsPKpFBHgn8sG
 status: PUBLISHED
 createdAt: 2022-05-19T16:19:45.245Z
-updatedAt: 2022-11-25T21:52:55.550Z
-publishedAt: 2022-11-25T21:52:55.550Z
+updatedAt: 2024-07-01T18:48:21.888Z
+publishedAt: 2024-07-01T18:48:21.888Z
 firstPublishedAt: 2022-05-19T16:19:45.749Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: los-datos-de-geocoordinates-no-pueden-ser-informados-para-algunos-cultureinfo
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 582065
 ---
 
diff --git a/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 9192ece1d..7d7944773 100644
--- a/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -1,10 +1,10 @@
 ---
-title: 'La API "Obtener todas las sugerencias de SKU" no mantiene el mismo orden de sku al cambiar los límites'
+title: 'La API "Obtener todas las sugerencias de SKU" no mantiene el mismo orden de SKU al cambiar los límites.'
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
-updatedAt: 2022-12-05T14:50:25.991Z
-publishedAt: 2022-12-05T14:50:25.991Z
+updatedAt: 2024-03-01T21:06:12.857Z
+publishedAt: 2024-03-01T21:06:12.857Z
 firstPublishedAt: 2022-12-05T14:49:47.309Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: la-api-obtener-todas-las-sugerencias-de-sku-no-mantiene-el-mismo-orden-de-sku-al-cambiar-los-limites
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 367187
 ---
 
@@ -30,7 +30,7 @@ Documentación de la API: https://developers.vtex.com/vtex-rest-api/reference/ge
 
 En el día a día esto perturba el funcionamiento del Marketplace porque cada vez que el marketplace hace una petición cambiando los límites para obtener los siguientes 20 skus, el orden de los skus también cambia y esto da la impresión de tener skus duplicados.
 
-Cuando se solicita esta API utilizando parámetros de consulta como "sellerId" se produce este comportamiento. Al solicitar la API sin parámetros de consulta, es posible utilizar el recurso "Next" para evitar este problema.
+Al solicitar esta API utilizando parámetros de consulta como "sellerId" se produce este comportamiento. Al solicitar la API sin parámetros de consulta, es posible utilizar el recurso "Next" para evitar este problema.
 
 
 
@@ -40,7 +40,17 @@ Cuando se solicita esta API utilizando parámetros de consulta como "sellerId" s
 
 
 
+1. Solicite la API "Obtener todas las sugerencias de SKU" utilizando los parámetros de consulta: "sellerId";
+2. Cambia los límites en los params "**_de "** y "**_a "** para obtener los siguientes skus;
+3. 3. Compruebe si en esta página hay una SKU que ya aparecía en las páginas anteriores.
+
+
+
+
+
 ## Workaround
 
 
 
+Para evitar esta situación, utilice la hoja de cálculo de exportación en la interfaz de usuario o utilice la API sin parámetros.
+
diff --git a/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md b/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
new file mode 100644
index 000000000..f318c6064
--- /dev/null
+++ b/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
@@ -0,0 +1,50 @@
+---
+title: 'La API de uso de cupones GET no muestra varios pedidos del mismo cupón.'
+id: 7B9Qlcx2XMGxWj9OB5Xl8n
+status: PUBLISHED
+createdAt: 2023-09-08T17:54:13.642Z
+updatedAt: 2023-09-08T17:54:14.220Z
+publishedAt: 2023-09-08T17:54:14.220Z
+firstPublishedAt: 2023-09-08T17:54:14.220Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: la-api-de-uso-de-cupones-get-no-muestra-varios-pedidos-del-mismo-cupon
+locale: es
+kiStatus: Backlog
+internalReference: 326662
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+La API de uso de cupones GET https://developers.vtex.com/vtex-rest-api/reference/catalog-api-overview no está listando actualmente todos los pedidos cerrados en los que se utilizó este cupón, está listando total-1
+
+
+
+##
+
+## Simulación
+
+
+1) Cierre dos pedidos distintos con el mismo cupón.
+
+2) Obtener los datos de uso de este cupón https://developers.vtex.com/vtex-rest-api/reference/coupons#getusage
+
+3) Se listará el total menos un pedido.
+
+
+
+##
+
+## Workaround
+
+
+n/a
+
diff --git a/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md b/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md
index e64a8b6dc..60ae513c0 100644
--- a/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md
+++ b/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md
@@ -3,8 +3,8 @@ title: 'La API de la lista de ofertas coincidentes no funciona correctamente'
 id: 7mxrjTDYB8yLeKmQkB5D9h
 status: PUBLISHED
 createdAt: 2022-03-31T13:49:41.374Z
-updatedAt: 2022-11-25T22:00:46.842Z
-publishedAt: 2022-11-25T22:00:46.842Z
+updatedAt: 2024-07-01T18:48:12.526Z
+publishedAt: 2024-07-01T18:48:12.526Z
 firstPublishedAt: 2022-03-31T13:49:42.277Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: la-api-de-la-lista-de-ofertas-coincidentes-no-funciona-correctamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 553456
 ---
 
diff --git a/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
index b89d36f6f..2671bb99b 100644
--- a/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
@@ -3,8 +3,8 @@ title: 'GET Product by Refid Devuelve "Null" cuando no se encuentra'
 id: 6yiM9gJT5DB77pZSBNfGZ3
 status: PUBLISHED
 createdAt: 2023-05-16T19:35:46.743Z
-updatedAt: 2023-05-16T19:35:47.468Z
-publishedAt: 2023-05-16T19:35:47.468Z
+updatedAt: 2024-07-01T18:49:03.498Z
+publishedAt: 2024-07-01T18:49:03.498Z
 firstPublishedAt: 2023-05-16T19:35:47.468Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: get-product-by-refid-devuelve-null-cuando-no-se-encuentra
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 826702
 ---
 
diff --git a/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md b/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md
index bf9d6b54f..95a695792 100644
--- a/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md
+++ b/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md
@@ -3,8 +3,8 @@ title: 'La API GET SKU by EAN sólo devuelve las SKU activas'
 id: 5NiuB1Lgf3CM5kXSSVdfuu
 status: PUBLISHED
 createdAt: 2020-03-23T15:10:23.842Z
-updatedAt: 2022-11-25T22:00:19.153Z
-publishedAt: 2022-11-25T22:00:19.153Z
+updatedAt: 2023-10-24T17:25:02.496Z
+publishedAt: 2023-10-24T17:25:02.496Z
 firstPublishedAt: 2020-03-27T19:32:53.914Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-api-get-sku-by-ean-solo-devuelve-las-sku-activas
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 699007
 ---
 
diff --git a/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md b/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
index b0ae47ab0..7949912b3 100644
--- a/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
+++ b/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
@@ -3,8 +3,8 @@ title: 'La función getCurrentProductWithVariations de VTEX.js trae los datos de
 id: 1m1bMbNXZVpQo9bQG1iSjn
 status: PUBLISHED
 createdAt: 2022-03-16T16:35:51.214Z
-updatedAt: 2022-11-25T22:10:09.849Z
-publishedAt: 2022-11-25T22:10:09.849Z
+updatedAt: 2024-02-16T20:24:03.691Z
+publishedAt: 2024-02-16T20:24:03.691Z
 firstPublishedAt: 2022-03-16T16:35:51.652Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: la-funcion-getcurrentproductwithvariations-de-vtexjs-trae-los-datos-del-sku-del-componente-y-no-del-sku-del-kit
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 324416
 ---
 
diff --git a/docs/known-issues/es/gift-card-creation-error-via-admin.md b/docs/known-issues/es/gift-card-creation-error-via-admin.md
new file mode 100644
index 000000000..e4ac565e9
--- /dev/null
+++ b/docs/known-issues/es/gift-card-creation-error-via-admin.md
@@ -0,0 +1,50 @@
+---
+title: 'Error de creación de tarjeta regalo vía admin'
+id: 6GUhpZbxYr0wTIuqN3S95A
+status: PUBLISHED
+createdAt: 2024-02-21T22:45:26.869Z
+updatedAt: 2024-02-21T22:45:27.647Z
+publishedAt: 2024-02-21T22:45:27.647Z
+firstPublishedAt: 2024-02-21T22:45:27.647Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-de-creacion-de-tarjeta-regalo-via-admin
+locale: es
+kiStatus: Backlog
+internalReference: 986327
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas cuentas no podrán crear una Tarjeta Regalo por primera vez vía admin, el mensaje de abajo aparecerá en la pantalla:
+
+Algo salió mal
+Error al conectar con el servidor.
+Por favor, vuelva a nuestra tienda en unos momentos.
+
+
+##
+
+## Simulación
+
+
+Después de rellenar toda la información de la tarjeta regalo y pulsar el botón "Guardar", los usuarios verán el mensaje de error mencionado anteriormente.
+
+
+
+## Workaround
+
+
+Si la primera tarjeta regalo se crea a través de la API, el error dejará de producirse y los comerciantes podrán crear tarjetas regalo a través del administrador con normalidad.
+
+
+
+
+
diff --git a/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md b/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
index 02d758f9d..cd6ab6fa5 100644
--- a/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
+++ b/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
@@ -3,8 +3,8 @@ title: 'La fecha de caducidad de la tarjeta regalo no coincide con la fecha eleg
 id: 57GeuSubkdDkQNwzL3nmup
 status: PUBLISHED
 createdAt: 2022-03-27T14:08:35.577Z
-updatedAt: 2022-11-25T22:07:21.976Z
-publishedAt: 2022-11-25T22:07:21.976Z
+updatedAt: 2024-07-01T18:48:00.399Z
+publishedAt: 2024-07-01T18:48:00.399Z
 firstPublishedAt: 2022-03-27T14:08:36.056Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: la-fecha-de-caducidad-de-la-tarjeta-regalo-no-coincide-con-la-fecha-elegida-al-crearla
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 378436
 ---
 
diff --git a/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md b/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
new file mode 100644
index 000000000..11f48ed47
--- /dev/null
+++ b/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
@@ -0,0 +1,45 @@
+---
+title: 'El HUB de la tarjeta regalo acepta un ID no válido/vacío como respuesta para crear una transacción.'
+id: 3ODSXijmpvkk55FUqMcGvQ
+status: PUBLISHED
+createdAt: 2023-07-05T12:50:36.661Z
+updatedAt: 2023-07-05T12:51:07.938Z
+publishedAt: 2023-07-05T12:51:07.938Z
+firstPublishedAt: 2023-07-05T12:50:37.274Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-hub-de-la-tarjeta-regalo-acepta-un-id-no-validovacio-como-respuesta-para-crear-una-transaccion
+locale: es
+kiStatus: Backlog
+internalReference: 855864
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La documentación de nuestro protocolo para proveedores de tarjetas regalo especifica que la API de creación de transacciones debe incluir un ID válido en la respuesta. Sin embargo, la implementación actual del protocolo permite a los proveedores responder a esta solicitud con un ID vacío o no válido. Como resultado, al intentar liquidar el pago, la transacción se bloquea porque falta el ID requerido. Esto provoca que se lance un error y que la transacción se quede atascada en el proceso.
+
+
+
+## Simulación
+
+
+Responder a la llamada de crear transacción con un ID no válido e intentar finalizar una transacción.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index f7362076a..ec14102eb 100644
--- a/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -3,8 +3,8 @@ title: 'Gift Card hub está añadiendo una barra invertida extra ("/") al llamar
 id: 2ZstMKKGUbrdXGuhS2Rr1f
 status: PUBLISHED
 createdAt: 2022-09-30T21:07:47.856Z
-updatedAt: 2022-11-25T22:04:08.181Z
-publishedAt: 2022-11-25T22:04:08.181Z
+updatedAt: 2024-02-16T20:24:58.109Z
+publishedAt: 2024-02-16T20:24:58.109Z
 firstPublishedAt: 2022-09-30T21:07:48.985Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: gift-card-hub-esta-anadiendo-una-barra-invertida-extra-al-llamar-a-los-proveedores
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 669575
 ---
 
diff --git a/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
new file mode 100644
index 000000000..3052fe59e
--- /dev/null
+++ b/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -0,0 +1,46 @@
+---
+title: 'Tarjeta regalo - No devuelve los campos "caption" y "relationName" cuando hacemos una petición get.'
+id: 2nh2Cc3Hc2Zm0b1INtwDep
+status: PUBLISHED
+createdAt: 2023-06-23T19:33:35.774Z
+updatedAt: 2024-02-16T20:25:03.806Z
+publishedAt: 2024-02-16T20:25:03.806Z
+firstPublishedAt: 2023-06-23T19:33:36.777Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: tarjeta-regalo-no-devuelve-los-campos-caption-y-relationname-cuando-hacemos-una-peticion-get
+locale: es
+kiStatus: No Fix
+internalReference: 428725
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se ejecuta el método GET para una tarjeta regalo existente, no devuelve el campo "caption" ni el campo "relationName" aunque estos parámetros tengan valor.
+
+
+##
+
+## Simulación
+
+
+Realice una solicitud get en la API: https://developers.vtex.com/vtex-rest-api/reference/gift-card#getgiftcardbyid
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md b/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md
index 195b945e1..0a602b918 100644
--- a/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md
+++ b/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md
@@ -3,8 +3,8 @@ title: 'Los artículos de regalo lanzan una excepción genérica si no tienen pr
 id: 7Jw1Nihqp3Sg2ecg7R9IEt
 status: PUBLISHED
 createdAt: 2022-05-12T14:52:18.546Z
-updatedAt: 2022-11-25T21:51:44.617Z
-publishedAt: 2022-11-25T21:51:44.617Z
+updatedAt: 2024-02-16T20:27:57.698Z
+publishedAt: 2024-02-16T20:27:57.698Z
 firstPublishedAt: 2022-05-12T14:52:18.968Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: los-articulos-de-regalo-lanzan-una-excepcion-generica-si-no-tienen-precio
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 510490
 ---
 
diff --git a/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md b/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
index 5fdd9da74..1364b3598 100644
--- a/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
+++ b/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
@@ -3,8 +3,8 @@ title: 'Las promociones de regalo no funcionan como se esperaba cuando actúan j
 id: 7p037qcaXYMYKC3kJPztc3
 status: PUBLISHED
 createdAt: 2023-01-09T21:08:49.800Z
-updatedAt: 2023-01-09T21:08:50.899Z
-publishedAt: 2023-01-09T21:08:50.899Z
+updatedAt: 2024-02-16T20:23:54.228Z
+publishedAt: 2024-02-16T20:23:54.228Z
 firstPublishedAt: 2023-01-09T21:08:50.899Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: las-promociones-de-regalo-no-funcionan-como-se-esperaba-cuando-actuan-junto-a-otra-promocion-de-regalo
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 729980
 ---
 
diff --git a/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md b/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
index be1399755..f7969e4c4 100644
--- a/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
+++ b/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
@@ -3,8 +3,8 @@ title: 'La configuración de la tarjeta de regalo recargable no funciona cuando
 id: 3MXPd85Km51KpO4FNPqlDf
 status: PUBLISHED
 createdAt: 2022-05-23T14:21:10.608Z
-updatedAt: 2022-11-25T22:05:59.003Z
-publishedAt: 2022-11-25T22:05:59.003Z
+updatedAt: 2024-02-16T20:25:54.496Z
+publishedAt: 2024-02-16T20:25:54.496Z
 firstPublishedAt: 2022-05-23T14:21:11.126Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: la-configuracion-de-la-tarjeta-de-regalo-recargable-no-funciona-cuando-se-intenta-anadir-credito-a-la-tarjeta-de-regalo-a-traves-de-la-api
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 583669
 ---
 
diff --git a/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md b/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
index a761ea121..32741e738 100644
--- a/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
+++ b/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
@@ -3,8 +3,8 @@ title: '[Giftlist] La fecha del evento guardada en la UI no es la misma que se r
 id: 6PUBzRdtno8ypsPMg97B6K
 status: PUBLISHED
 createdAt: 2022-07-25T17:45:12.568Z
-updatedAt: 2022-11-25T21:42:07.374Z
-publishedAt: 2022-11-25T21:42:07.374Z
+updatedAt: 2024-02-16T20:28:47.100Z
+publishedAt: 2024-02-16T20:28:47.100Z
 firstPublishedAt: 2022-07-25T17:45:13.009Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: giftlist-la-fecha-del-evento-guardada-en-la-ui-no-es-la-misma-que-se-refleja-en-la-bd
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 402134
 ---
 
diff --git a/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md b/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md
index 24c12efbf..b05f242a4 100644
--- a/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md
+++ b/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md
@@ -3,8 +3,8 @@ title: 'Categorías globales del catálogo obsoletas en comparación con Google'
 id: 4vH5NRdMsuZmOohdHFn16H
 status: PUBLISHED
 createdAt: 2023-02-14T19:42:08.121Z
-updatedAt: 2023-02-14T19:42:08.712Z
-publishedAt: 2023-02-14T19:42:08.712Z
+updatedAt: 2024-07-01T18:48:52.824Z
+publishedAt: 2024-07-01T18:48:52.824Z
 firstPublishedAt: 2023-02-14T19:42:08.712Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: categorias-globales-del-catalogo-obsoletas-en-comparacion-con-google
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 754062
 ---
 
diff --git a/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md b/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
new file mode 100644
index 000000000..b6360748a
--- /dev/null
+++ b/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
@@ -0,0 +1,49 @@
+---
+title: 'El componente iframe de Google Customer Reviews no se muestra correctamente'
+id: 7BDB9yYv3ZHbhE4ExCXgZK
+status: PUBLISHED
+createdAt: 2023-12-22T17:55:39.082Z
+updatedAt: 2024-02-16T20:25:48.248Z
+publishedAt: 2024-02-16T20:25:48.248Z
+firstPublishedAt: 2023-12-22T17:55:39.764Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-componente-iframe-de-google-customer-reviews-no-se-muestra-correctamente
+locale: es
+kiStatus: No Fix
+internalReference: 578443
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El iframe, responsable de la insignia de Opiniones de clientes de Google, tiene una representación incoherente dentro del elemento div del componente Opiniones de clientes de Google.
+
+Opiniones de clientes de Google:
+https://developers.vtex.com/vtex-developer-docs/docs/vtex-google-customer-reviews
+
+
+##
+
+## Simulación
+
+
+En una cuenta que utiliza el componente Google Customer Reviews, al abrir la pestaña Elemento en el inspector del navegador, se puede ver siempre el div Google Customer Review, pero, a veces, el elemento está vacío, sin el iframe de Google.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md b/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
index fce154a40..ef92fbd8b 100644
--- a/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
+++ b/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
@@ -3,8 +3,8 @@ title: ' La agrupación por método de entrega en el rendimiento de las ventas n
 id: 8zHND5pzrt0mrIrb061Zq
 status: PUBLISHED
 createdAt: 2022-11-30T19:02:13.548Z
-updatedAt: 2022-12-01T22:14:52.118Z
-publishedAt: 2022-12-01T22:14:52.118Z
+updatedAt: 2024-02-16T20:25:12.853Z
+publishedAt: 2024-02-16T20:25:12.853Z
 firstPublishedAt: 2022-11-30T19:02:13.994Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: la-agrupacion-por-metodo-de-entrega-en-el-rendimiento-de-las-ventas-no-funciona-como-se-esperaba
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639294
 ---
 
diff --git a/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md b/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md
new file mode 100644
index 000000000..df225fcea
--- /dev/null
+++ b/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md
@@ -0,0 +1,51 @@
+---
+title: 'Headless CMS ignora la configuración de validación de matrices'
+id: 1szfagZFJHmevSWDTyd45e
+status: PUBLISHED
+createdAt: 2024-06-07T14:22:41.366Z
+updatedAt: 2024-06-07T14:22:41.992Z
+publishedAt: 2024-06-07T14:22:41.992Z
+firstPublishedAt: 2024-06-07T14:22:41.992Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: headless-cms-ignora-la-configuracion-de-validacion-de-matrices
+locale: es
+kiStatus: Backlog
+internalReference: 1046372
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se intentan configurar reglas de validación de arrays en Headless CMS, como elementos de arrays mínimos y máximos, los errores de validación no se muestran al usuario y es posible guardar el esquema sin pasar la validación.
+
+El escenario esperado sería bloquear la pantalla y mostrar un mensaje como:
+
+    "keyword": "minItems", "message": "NO debe tener menos de 3 elementos",
+
+
+
+##
+
+## Simulación
+
+
+Prueba a añadir una sección que tenga una regla de validación. Si no respetas la validación el hCMS te dejará publicar el contenido normalmente.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md b/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
new file mode 100644
index 000000000..dfb1c301e
--- /dev/null
+++ b/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
@@ -0,0 +1,50 @@
+---
+title: 'Los formatos de imagen JPG o PNG no funcionan en el catálogo del portal del vendedor.'
+id: 19s9bGcpNsOkIkA0iGkWRi
+status: PUBLISHED
+createdAt: 2024-04-22T12:41:43.272Z
+updatedAt: 2024-04-22T12:41:44.252Z
+publishedAt: 2024-04-22T12:41:44.252Z
+firstPublishedAt: 2024-04-22T12:41:44.252Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: los-formatos-de-imagen-jpg-o-png-no-funcionan-en-el-catalogo-del-portal-del-vendedor
+locale: es
+kiStatus: Backlog
+internalReference: 1020505
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar crear un producto con un formato de imagen establecido como JPG o PNG, el producto se crea con una imagen rota. Este comportamiento no ocurre si el formato se establece como jpg o png (sin capslock).
+
+
+##
+
+## Simulación
+
+
+
+1. Crear un producto en una cuenta del portal del vendedor
+2. Importar una imagen con formato JPG o PNG
+3. Guardar el producto
+4. Compruebe que la imagen se rompe en la interfaz de usuario si abre el producto creado.
+
+
+
+## Workaround
+
+
+Importe imágenes con formato jpg o png (minúsculas).
+
+
+
+
+
diff --git a/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md b/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md
new file mode 100644
index 000000000..f43f8c797
--- /dev/null
+++ b/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md
@@ -0,0 +1,51 @@
+---
+title: 'La suplantación de identidad se ignora después de completar una compra'
+id: 4mHKOlwaLwfIEf8HFh4y4Y
+status: PUBLISHED
+createdAt: 2024-03-20T20:10:26.200Z
+updatedAt: 2024-03-20T20:10:27.029Z
+publishedAt: 2024-03-20T20:10:27.029Z
+firstPublishedAt: 2024-03-20T20:10:27.029Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-suplantacion-de-identidad-se-ignora-despues-de-completar-una-compra
+locale: es
+kiStatus: Backlog
+internalReference: 1003545
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un operador del centro de llamadas se hace pasar por un comprador, completa una compra y es enviado a la página orderPlaced, se generará un nuevo orderForm.
+
+Este nuevo orderForm tendrá su clientProfileData adjunto con el email del operador del call center en lugar del comprador suplantado, aunque los datos de suplantación se persisten normalmente dentro de la Sesión.
+
+
+##
+
+## Simulación
+
+
+
+1. Inicie sesión en el entorno myvtex como operador de un centro de llamadas.
+2. Hacerse pasar por un comprador y completar una compra.
+3. Después, mientras sigue suplantando al usuario, inicie una nueva compra, y observe como los datos del carrito contendrán el email de su operador de call center dentro de clientProfileData.
+
+
+
+## Workaround
+
+
+Si necesita crear más de un pedido para el mismo comprador, asegúrese de volver a realizar el proceso de suplantación entre pedidos.
+
+
+
+
+
diff --git a/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md b/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
new file mode 100644
index 000000000..d67a05fea
--- /dev/null
+++ b/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
@@ -0,0 +1,47 @@
+---
+title: 'Widget de suplantación de usuario no se muestra si showModal está activado'
+id: 19IHgjxPOEFC6HsAc5FD96
+status: PUBLISHED
+createdAt: 2024-06-03T15:55:49.797Z
+updatedAt: 2024-06-03T15:55:50.539Z
+publishedAt: 2024-06-03T15:55:50.539Z
+firstPublishedAt: 2024-06-03T15:55:50.539Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: widget-de-suplantacion-de-usuario-no-se-muestra-si-showmodal-esta-activado
+locale: es
+kiStatus: Backlog
+internalReference: 1043039
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Después de suplantar otro email, se espera que se muestre un botón "Detener suplantación", pero cuando el `showModal` está habilitado, no se muestra.
+
+
+##
+
+## Simulación
+
+
+
+- Activa "Usar modal para cambiar de empresa" en la configuración de Organizaciones B2B;
+- Inicie sesión y suplante otro correo electrónico.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
new file mode 100644
index 000000000..50ffc468f
--- /dev/null
+++ b/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -0,0 +1,52 @@
+---
+title: 'La colección de importación sólo acepta el orden de los productos si la importación se realiza basándose en "skuId"'
+id: 7vXi2bDVyGHSMLluQi2ZWZ
+status: PUBLISHED
+createdAt: 2023-12-15T16:35:11.545Z
+updatedAt: 2023-12-21T18:55:17.090Z
+publishedAt: 2023-12-21T18:55:17.090Z
+firstPublishedAt: 2023-12-15T16:35:12.450Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-coleccion-de-importacion-solo-acepta-el-orden-de-los-productos-si-la-importacion-se-realiza-basandose-en-skuid
+locale: es
+kiStatus: Fixed
+internalReference: 953862
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al importar una hoja de cálculo de productos a una colección, el usuario puede elegir seleccionar los productos por "skuId", "productId", "skuRefId" o "productRefId".
+
+Sin embargo, el orden de los productos en la colección sólo se respeta cuando la hoja de cálculo utiliza "skuId".
+
+
+##
+
+## Simulación
+
+
+
+1. Crear una nueva colección;
+2. Utilizar hoja de cálculo de importación para añadir productos;
+3. Elija un campo distinto de "skuId" para rellenar la hoja de cálculo;
+4. 4. Compruebe que el orden de los productos en las colecciones es diferente del orden en la hoja de cálculo.
+
+
+
+## Workaround
+
+
+Utiliza la columna "skuId" para rellenar la hoja de cálculo.
+
+
+
+
+
diff --git a/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md b/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
new file mode 100644
index 000000000..bb477a539
--- /dev/null
+++ b/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
@@ -0,0 +1,48 @@
+---
+title: 'En algunos casos en los que hay un descuento en el pedido, tenemos una discrepancia en el valor total del campo Artículos a facturar en la interfaz de usuario del pedido.'
+id: 20xiOKxpvdCODmDJDKunST
+status: PUBLISHED
+createdAt: 2024-05-06T20:17:01.162Z
+updatedAt: 2024-05-06T20:17:01.968Z
+publishedAt: 2024-05-06T20:17:01.968Z
+firstPublishedAt: 2024-05-06T20:17:01.968Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: en-algunos-casos-en-los-que-hay-un-descuento-en-el-pedido-tenemos-una-discrepancia-en-el-valor-total-del-campo-articulos-a-facturar-en-la-interfaz-de-usuario-del-pedido
+locale: es
+kiStatus: Backlog
+internalReference: 1028210
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se ha detectado que en algunos pedidos en los que existe un descuento asociado a uno o varios artículos, podemos tener una discrepancia en el valor total del campo "artículos a facturar" en la interfaz de usuario del pedido, ya que el cálculo de este campo tiene en cuenta el parámetro "precioVenta", en lugar del parámetro "precioDefiniciones". Por lo tanto, es posible notar diferencias de 0,01 o un poco más del valor total del pedido.
+
+Hacemos hincapié en que este campo es ilustrativo, ya que el campo principal es el valor total (importe) del pedido y NO hay discrepancias en este campo.
+
+
+##
+
+## Simulación
+
+
+No es posible simular este escenario.
+
+
+
+## Workaround
+
+
+No sería una solución, sólo un consejo para facturar el pedido con el importe total, informado en el campo "importe", o en el caso de facturas parciales, informar del valor del artículo(s).
+
+
+
+
+
diff --git a/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md b/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
index f1925b56b..3a10753c9 100644
--- a/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
+++ b/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
@@ -3,8 +3,8 @@ title: 'En la declaración parcial, los valores de los impuestos en la UI aparec
 id: 2I5a9hwrUo6s1htxOg8H1U
 status: PUBLISHED
 createdAt: 2022-04-11T13:15:06.455Z
-updatedAt: 2022-11-25T22:03:40.667Z
-publishedAt: 2022-11-25T22:03:40.667Z
+updatedAt: 2024-02-16T20:28:35.114Z
+publishedAt: 2024-02-16T20:28:35.114Z
 firstPublishedAt: 2022-04-11T13:15:07.028Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: en-la-declaracion-parcial-los-valores-de-los-impuestos-en-la-ui-aparecen-el-total
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 559458
 ---
 
diff --git a/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md b/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md
index 1f257abf0..77985d083 100644
--- a/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md
+++ b/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md
@@ -3,8 +3,8 @@ title: 'Imposibilidad de realizar una cancelación parcial con MercadoPagoV1'
 id: 59aimeqhjGVOVkP9f6A9ls
 status: PUBLISHED
 createdAt: 2022-06-28T16:44:19.059Z
-updatedAt: 2022-11-25T22:06:36.432Z
-publishedAt: 2022-11-25T22:06:36.432Z
+updatedAt: 2024-02-16T20:30:01.307Z
+publishedAt: 2024-02-16T20:30:01.307Z
 firstPublishedAt: 2022-06-28T16:44:19.331Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: imposibilidad-de-realizar-una-cancelacion-parcial-con-mercadopagov1
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 286738
 ---
 
diff --git a/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md b/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
index 1726fcfab..99b1de843 100644
--- a/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
+++ b/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
@@ -3,8 +3,8 @@ title: 'Imposibilidad de utilizar dos o más credenciales de PayPal diferentes p
 id: 3cVh2SbvToH8yGOOYcWgDB
 status: PUBLISHED
 createdAt: 2022-03-03T18:39:24.442Z
-updatedAt: 2022-11-25T22:05:45.390Z
-publishedAt: 2022-11-25T22:05:45.390Z
+updatedAt: 2024-02-16T20:25:01.876Z
+publishedAt: 2024-02-16T20:25:01.876Z
 firstPublishedAt: 2022-03-03T18:39:25.004Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: imposibilidad-de-utilizar-dos-o-mas-credenciales-de-paypal-diferentes-para-la-misma-cuenta
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 459704
 ---
 
@@ -23,15 +23,15 @@ internalReference: 459704
 </div>
 
 
-Cuando el cliente registra dos afiliaciones diferentes en la misma cuenta utilizando PayPalPlus, la plataforma no actualiza la caché para cuando hay un cambio en una regla de pago, es decir, sólo es posible utilizar una credencial por cuenta.
-
+Cuando el usuario registra dos afiliaciones diferentes en la misma cuenta utilizando PayPalPlus, la plataforma no actualiza la caché para cuando se produce un cambio en una regla de pago, es decir, sólo es posible utilizar una credencial por cuenta.
 
 
+##
 
 ## Simulación
 
 
-Registre dos afiliaciones diferentes con credenciales distintas y cree reglas que tengan en cuenta estas dos afiliaciones.
+Registre dos afiliaciones diferentes con credenciales diferentes y cree reglas teniendo en cuenta estas dos afiliaciones.
 Cierra dos compras, cada una con una de las reglas, y en el payload de la transacción puedes ver que a pesar de introducir las reglas correctas, el merchant_id (identificación de la cuenta en la que caerá el dinero) es el mismo.
 
 
@@ -39,5 +39,9 @@ Cierra dos compras, cada una con una de las reglas, y en el payload de la transa
 ## Workaround
 
 
-No hay ninguna solución
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md b/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md
new file mode 100644
index 000000000..bdc84fb0f
--- /dev/null
+++ b/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md
@@ -0,0 +1,47 @@
+---
+title: 'Transacciones incompletas que aparecen con moneda brasileña'
+id: 7g0j3FGa5E8kNi9PM3kBOf
+status: PUBLISHED
+createdAt: 2024-04-01T13:37:35.197Z
+updatedAt: 2024-04-01T13:37:36.114Z
+publishedAt: 2024-04-01T13:37:36.114Z
+firstPublishedAt: 2024-04-01T13:37:36.114Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transacciones-incompletas-que-aparecen-con-moneda-brasilena
+locale: es
+kiStatus: Backlog
+internalReference: 1007953
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Transacciones incompletas (cliente "Sin nombre") pueden aparecer en la sección de Transacciones con moneda R$, estos son resultado de un error de creación (los datos de pago no fueron enviados) pero las órdenes son creadas correctamente en moneda local.
+
+Como estas transacciones ya están perdidas no hay impacto operacional (error visual).
+
+
+
+## Simulación
+
+
+Al finalizar un pago en checkout se puede recargar la página para "romper" el proceso y comprobar en UI si ha fallado la creación de la transacción completa (buscando la de "Sin nombre").
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
+
diff --git a/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md b/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
index e44582555..376a30e8e 100644
--- a/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
+++ b/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
@@ -28,7 +28,7 @@ En los productos con personalización de Assembly options, un ítem principal ti
 3. Selecciona el ítem secundario del producto, en la misma cantidad;
 4. Revisa los ítems en el carrito.
 
-![KI assembly](https://images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/01c933c01f3b6b361b06de22d8160e9a/KI_assembly.png)
+![KI assembly](//images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/01c933c01f3b6b361b06de22d8160e9a/KI_assembly.png)
 
 Observa que el carrito contiene una unidad más del ítem secundario en comparación con el ítem principal.
 
diff --git a/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md b/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
new file mode 100644
index 000000000..b94ebbc89
--- /dev/null
+++ b/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
@@ -0,0 +1,47 @@
+---
+title: 'Información de condiciones de pago incoherente entre los detalles del centro de costes en Mi organización y los ajustes de pago B2B.'
+id: VB70gSEsPOdTHVi3SPMaB
+status: PUBLISHED
+createdAt: 2023-06-20T18:29:30.859Z
+updatedAt: 2023-07-17T14:34:00.520Z
+publishedAt: 2023-07-17T14:34:00.520Z
+firstPublishedAt: 2023-06-20T18:29:31.475Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: informacion-de-condiciones-de-pago-incoherente-entre-los-detalles-del-centro-de-costes-en-mi-organizacion-y-los-ajustes-de-pago-b2b
+locale: es
+kiStatus: Fixed
+internalReference: 847340
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Información inconsistente entre los Detalles del Centro de Coste en Mi Organización y los Ajustes de Pago B2B donde Mi Organización muestra un término de pago desactivado, pero el término de pago se sigue mostrando al acceder al pago.
+
+
+
+## Simulación
+
+
+
+- Acceda a Mi organización en Mi cuenta con un rol de "Administrador de la organización";
+- Haga clic en el Centro de costes;
+- En la sección "Condiciones de pago", desactive una condición de pago;
+- Acceda a la caja y vaya a Pago; la opción desactivada sigue disponible.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md b/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
index 573b0f5a6..ccc91a89b 100644
--- a/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
+++ b/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
@@ -1,16 +1,16 @@
 ---
-title: 'Precio inconsistente cuando el SKU tiene un multiplicador de unidades diferente a 1'
+title: 'Precio incoherente cuando la SKU tiene un multiplicador unitario distinto de 1'
 id: NVtFiuWgptqa2gBEVmpOC
 status: PUBLISHED
 createdAt: 2022-09-05T13:05:50.789Z
-updatedAt: 2023-02-27T14:22:04.935Z
-publishedAt: 2023-02-27T14:22:04.935Z
+updatedAt: 2024-02-02T16:50:00.987Z
+publishedAt: 2024-02-02T16:50:00.987Z
 firstPublishedAt: 2022-09-05T13:05:51.613Z
 contentType: knownIssue
 productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
-slug: precio-inconsistente-cuando-el-sku-tiene-un-multiplicador-de-unidades-diferente-a-1
+slug: precio-incoherente-cuando-la-sku-tiene-un-multiplicador-unitario-distinto-de-1
 locale: es
 kiStatus: Backlog
 internalReference: 651102
@@ -23,22 +23,31 @@ internalReference: 651102
 </div>
 
 
-Cuando algún SKU contiene un multiplicador de unidades diferente a 1, en algunas situaciones, el precio devuelto en store-graphql puede tener inconsistencias basadas en la división del precio devuelto desde la API de simulación:
+Cuando algún SKU contiene un multiplicador de unidades diferente de 1 (puede ser int como 10 o 100, o float como 0.8, por ejemplo), en algunas situaciones, el precio devuelto en store-graphql puede tener inconsistencias basadas en la división del precio devuelto desde la API de simulación:
 
 calculatedSellingPrice / (unitMultiplier * 100)
 
-También se aplica a los valores en cuotas que no consideran el valor del multiplicador unitario y la llamada de simulación envía el valor con el multiplicador unitario que se considera
-
-Basado en:
-https://vtexhelp.zendesk.com/agent/tickets/578022
+Puede aplicarse a todos los valores de precio que utilicen el multiplicador unitario como en los plazos (que no consideran el valor del multiplicador unitario y la llamada de simulación envía el valor con el multiplicador unitario considerado), precio PDP, precio PLP, o carrito.
 
 
+##
 
 ## Simulación
 
 
+Comprobar la simulación llamada para un producto con multiplicador unitario
+Comprobar el precio del producto en una página de búsqueda o utilizando una consulta de búsqueda de productos desde search-graphql
+Los precios pueden ser divergentes en céntimos
+
+
+##
 
 ## Workaround
 
 
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/es/incorrect-currency-on-payment-form.md b/docs/known-issues/es/incorrect-currency-on-payment-form.md
index 54d29ff36..eafcdfc8f 100644
--- a/docs/known-issues/es/incorrect-currency-on-payment-form.md
+++ b/docs/known-issues/es/incorrect-currency-on-payment-form.md
@@ -3,8 +3,8 @@ title: 'Moneda incorrecta en el formulario de pago'
 id: 636reFJs0MeHQJO0NlQV7Z
 status: PUBLISHED
 createdAt: 2022-03-13T21:29:33.920Z
-updatedAt: 2022-11-25T22:05:48.750Z
-publishedAt: 2022-11-25T22:05:48.750Z
+updatedAt: 2024-02-16T20:27:07.481Z
+publishedAt: 2024-02-16T20:27:07.481Z
 firstPublishedAt: 2022-03-13T21:29:34.493Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: moneda-incorrecta-en-el-formulario-de-pago
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 449286
 ---
 
diff --git a/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md b/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
new file mode 100644
index 000000000..0c763d94f
--- /dev/null
+++ b/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
@@ -0,0 +1,53 @@
+---
+title: 'Actualización incorrecta del precio cuando una promoción no aplica el descuento a todos los mismos artículos de un carrito.'
+id: 1nXGR7pKjyc0Rmo0UzMOns
+status: PUBLISHED
+createdAt: 2024-05-01T20:07:04.369Z
+updatedAt: 2024-05-01T20:07:16.339Z
+publishedAt: 2024-05-01T20:07:16.339Z
+firstPublishedAt: 2024-05-01T20:07:05.363Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: actualizacion-incorrecta-del-precio-cuando-una-promocion-no-aplica-el-descuento-a-todos-los-mismos-articulos-de-un-carrito
+locale: es
+kiStatus: Backlog
+internalReference: 1025539
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una promoción aplica un descuento a un solo artículo de la misma SKU (por ejemplo, una promoción Más por Menos), si hay una segunda promoción para esa misma SKU, el cálculo del descuento se aplicará a la cantidad ya descontada por la primera promoción - resultando en un descuento menor que el que se aplicaría si la segunda promoción se aplicara al precio inicial de la SKU.
+
+El problema se produce en la actualización de precios cuando una promoción no aplica el descuento a todos los mismos artículos de un carrito y esto provoca una "división" (dos mismos artículos con precios diferentes). Cuando se aplica la segunda promoción, se aplica al precio incorrecto.
+
+El fallo no se da por una promoción concreta.
+
+
+##
+
+## Simulación
+
+
+
+- Crear una promoción Más por Menos, aplicando el descuento a un solo artículo de la misma SKU
+- Cree una promoción de porcentaje normal para la misma SKU
+- En la caja, compruebe que el descuento de la segunda promoción se basa en el valor inferior de la SKU, que ya había sido descontado por la primera promoción.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
new file mode 100644
index 000000000..937142821
--- /dev/null
+++ b/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -0,0 +1,55 @@
+---
+title: 'Cálculo de reembolso incorrecto en Payout Split - "Valor en destinatarios * es diferente al valor de operación *".'
+id: 7Fxtwnntpmi0DrUD5a603W
+status: PUBLISHED
+createdAt: 2024-07-29T15:07:07.716Z
+updatedAt: 2024-07-29T15:07:12.565Z
+publishedAt: 2024-07-29T15:07:12.565Z
+firstPublishedAt: 2024-07-29T15:07:12.565Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: calculo-de-reembolso-incorrecto-en-payout-split-valor-en-destinatarios-es-diferente-al-valor-de-operacion
+locale: es
+kiStatus: Backlog
+internalReference: 1072285
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al llamar a un reembolso (en transacciones con división de pago) puede ocurrir el error de abajo con importes divergentes:
+
+(Ejemplo)
+
+    Vtex.Practices.ExceptionHandling.ValidationException: Value in recipients (45.00) is different than operation value (299.99). at Vtex.PaymentGateway.PaymentSplit.RecipientsBuilder.ValidateRecipientsValue(List`1 recipients, Decimal value)...
+
+
+Tenga en cuenta que este KI es diferente del siguiente (problema de cálculo relacionado con el redondeo - la diferencia de valores es pequeña):
+
+https://help.vtex.com/en/known-issues/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value--3Wo9ltN7Ju0ZqVLAQZcd7m
+
+
+##
+
+## Simulación
+
+
+Esto parece ocurrir cuando el carrito no tiene productos del mercado pero no hemos podido simular este error.
+
+
+
+## Workaround
+
+
+NA, los comerciantes deben solicitar el reembolso manual directamente a la entidad adquirente.
+
+
+
+
+
diff --git a/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md b/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md
index d614b173c..3ea7ae513 100644
--- a/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md
+++ b/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md
@@ -3,8 +3,8 @@ title: 'ShippingEstimateDate incorrecto para el pedido FOB'
 id: 3WLcrdw0tEdOvlMCYx9uyd
 status: PUBLISHED
 createdAt: 2023-01-05T20:26:07.074Z
-updatedAt: 2023-01-05T20:26:07.500Z
-publishedAt: 2023-01-05T20:26:07.500Z
+updatedAt: 2024-02-16T20:23:32.848Z
+publishedAt: 2024-02-16T20:23:32.848Z
 firstPublishedAt: 2023-01-05T20:26:07.500Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: shippingestimatedate-incorrecto-para-el-pedido-fob
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 269104
 ---
 
diff --git a/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md b/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
new file mode 100644
index 000000000..d1d67cd39
--- /dev/null
+++ b/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
@@ -0,0 +1,50 @@
+---
+title: 'Indexaciones incorrectas/faltantes para cuentas en las que el nombre de cuenta es diferente del registrado en el fulfillmentEndpoint.'
+id: 3TPRChOVHGpOYVeVo4zGOK
+status: PUBLISHED
+createdAt: 2024-06-14T16:45:39.257Z
+updatedAt: 2024-07-09T16:49:07.942Z
+publishedAt: 2024-07-09T16:49:07.942Z
+firstPublishedAt: 2024-06-14T16:45:40.852Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: indexaciones-incorrectasfaltantes-para-cuentas-en-las-que-el-nombre-de-cuenta-es-diferente-del-registrado-en-el-fulfillmentendpoint
+locale: es
+kiStatus: Backlog
+internalReference: 1050023
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, una cuenta de franquicia puede tener su registro fulFillmentEndpoint diferente de su nombre de cuenta "oficial", lo cual es una práctica común para arquitecturas específicas de vendedor<>marketplace que necesitan múltiples precios y/o stock para distintos canales de venta utilizando la característica de franquicia con múltiples vendedores para la misma franquicia.
+
+Aunque esta característica funciona en términos de mostrar el contenido necesario para los compradores, cuando los datos relevantes para las ventas, como el precio/existencias, se actualizan para el vendedor principal de una franquicia determinada, las otras cuentas asociadas no se indexan correctamente junto a él, generando una disponibilidad y visualización de precios incoherentes entre los canales de venta de una tienda.
+
+
+
+## Simulación
+
+
+
+- Para una tienda que tiene múltiples vendedores y 1+ cuentas de franquicia, configurar 2+ vendedores apuntando, en el fulfillmentendpoint, hacia la misma cuenta de franquicia en sus ajustes de vendedor.
+- Intente actualizar los datos de precio/stock de cualquier artículo de la cuenta de franquicia.
+- Compruebe los datos actualizados en los otros vendedores asociados que utilizan la cuenta de franquicia en sus puntos finales FFM, estarán desactualizados.
+
+
+
+## Workaround
+
+
+Utilice la función salesChannelMapping para implementar esta arquitectura en su lugar
+
+
+
+
+
diff --git a/docs/known-issues/es/incorrectly-updated-inventory.md b/docs/known-issues/es/incorrectly-updated-inventory.md
index 94d8cf90d..3b8dd9f21 100644
--- a/docs/known-issues/es/incorrectly-updated-inventory.md
+++ b/docs/known-issues/es/incorrectly-updated-inventory.md
@@ -3,8 +3,8 @@ title: 'Inventario incorrectamente actualizado'
 id: 2M8DqNY1pGQWZnF9ZXNycq
 status: PUBLISHED
 createdAt: 2022-05-03T12:32:14.192Z
-updatedAt: 2022-11-25T21:56:29.965Z
-publishedAt: 2022-11-25T21:56:29.965Z
+updatedAt: 2024-02-16T20:24:24.243Z
+publishedAt: 2024-02-16T20:24:24.243Z
 firstPublishedAt: 2022-05-03T12:32:14.713Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: inventario-incorrectamente-actualizado
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 556514
 ---
 
diff --git a/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md b/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
index ee73a41b9..35dc65f2e 100644
--- a/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
+++ b/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
@@ -3,8 +3,8 @@ title: 'Precio indexado de un producto considerando la SKU con el precio más al
 id: 333mavl9dvgO4Jrgv8ECE6
 status: PUBLISHED
 createdAt: 2023-05-09T14:39:56.338Z
-updatedAt: 2023-05-09T14:39:56.771Z
-publishedAt: 2023-05-09T14:39:56.771Z
+updatedAt: 2023-08-18T17:24:09.314Z
+publishedAt: 2023-08-18T17:24:09.314Z
 firstPublishedAt: 2023-05-09T14:39:56.771Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: precio-indexado-de-un-producto-considerando-la-sku-con-el-precio-mas-alto-en-lugar-del-mas-bajo
 locale: es
-kiStatus: Scheduled
+kiStatus: Fixed
 internalReference: 822120
 ---
 
diff --git a/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md b/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
index 76df20ebb..6f6f3e295 100644
--- a/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
+++ b/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
@@ -3,8 +3,8 @@ title: 'Las exportaciones de almacenes individuales (inventario) no funcionan en
 id: 7GoxwXFUWnebmCqF1sm7rm
 status: PUBLISHED
 createdAt: 2022-10-24T19:21:06.182Z
-updatedAt: 2022-11-25T21:43:01.961Z
-publishedAt: 2022-11-25T21:43:01.961Z
+updatedAt: 2024-07-01T18:48:39.414Z
+publishedAt: 2024-07-01T18:48:39.414Z
 firstPublishedAt: 2022-10-24T19:21:06.574Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: las-exportaciones-de-almacenes-individuales-inventario-no-funcionan-en-las-cuentas-del-seller-portal
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 684464
 ---
 
diff --git a/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md b/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
new file mode 100644
index 000000000..677cb789e
--- /dev/null
+++ b/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
@@ -0,0 +1,52 @@
+---
+title: 'El sistema de facturación por inferencia no funciona correctamente cuando hay el mismo SKUid en diferentes elementos de la matriz.'
+id: 3fSQGwIPj0ekewMuaxPPEe
+status: PUBLISHED
+createdAt: 2024-03-28T19:00:12.852Z
+updatedAt: 2024-04-04T13:33:04.775Z
+publishedAt: 2024-04-04T13:33:04.775Z
+firstPublishedAt: 2024-03-28T19:00:14.053Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: el-sistema-de-facturacion-por-inferencia-no-funciona-correctamente-cuando-hay-el-mismo-skuid-en-diferentes-elementos-de-la-matriz
+locale: es
+kiStatus: Backlog
+internalReference: 1008459
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunos pedidos tienen el mismo SKUid en un conjunto separado de artículos, esto ocurre en el momento de la compra en la caja por diferentes razones como el descuento a aplicar, por ejemplo.
+Esto no es un problema sino una condición para el cálculo de la compra.
+
+El problema está en la fase de facturación de esos artículos. A veces el sistema de inferencia no puede hacer coincidir los itens a insertar correctamente en los artículos de referencia en packageAttachment, debido a la misma SKUid y precios de venta.
+Incluso si el cliente envía la cantidad de itens correctamente, la inferencia será incorrecta.
+
+¿Es posible ver la diferencia entre el sistema SNO y los artículos del packageAttachment en el pedido?
+
+
+
+## Simulación
+
+
+Cree un pedido con más de una cantidad de artículos y aplique algún descuento, creando un pedido con más de un conjunto de artículos con diferentes precios de venta. Después de eso, intente facturar todos los artículos del pedido.
+
+
+
+
+## Workaround
+
+
+No hay ninguna solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/infocard-mobile-images-wont-apply.md b/docs/known-issues/es/infocard-mobile-images-wont-apply.md
new file mode 100644
index 000000000..81a02a42e
--- /dev/null
+++ b/docs/known-issues/es/infocard-mobile-images-wont-apply.md
@@ -0,0 +1,50 @@
+---
+title: 'Las imágenes de móvil Infocard no se aplicarán'
+id: 1vx5fwa5nL3SO27HpihLFd
+status: PUBLISHED
+createdAt: 2024-02-19T19:12:18.516Z
+updatedAt: 2024-02-19T19:12:19.362Z
+publishedAt: 2024-02-19T19:12:19.362Z
+firstPublishedAt: 2024-02-19T19:12:19.362Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: las-imagenes-de-movil-infocard-no-se-aplicaran
+locale: es
+kiStatus: Backlog
+internalReference: 909647
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando cambias la imagen de una infocard para que se muestre en la versión móvil, no se muestra. En su lugar, se sigue mostrando la imagen principal.
+
+
+##
+
+## Simulación
+
+
+
+- Abra una infotarjeta en el editor de sitios para editarla.
+- Cambiar la imagen principal de la infocard y aplicar.
+- Cambie la imagen para la versión móvil de la infocard y aplique.
+- Observe los resultados, la imagen seguirá siendo la imagen principal en lugar de la establecida para móvil cuando esté en modo móvil.
+
+
+
+## Workaround
+
+
+En su lugar, intente utilizar un diseño flexible con una imagen de la tienda + otras aplicaciones para crear el banner deseado.
+
+
+
+
+
diff --git a/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
new file mode 100644
index 000000000..7950ea2e9
--- /dev/null
+++ b/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -0,0 +1,52 @@
+---
+title: 'La API Insertar Archivo SKU no acepta URLs de servidores que requieren "Agentes de Usuario".'
+id: 5Z1PmRXyW78mohsKTMQfzj
+status: PUBLISHED
+createdAt: 2024-07-22T19:49:14.140Z
+updatedAt: 2024-07-22T19:49:15.319Z
+publishedAt: 2024-07-22T19:49:15.319Z
+firstPublishedAt: 2024-07-22T19:49:15.319Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-api-insertar-archivo-sku-no-acepta-urls-de-servidores-que-requieren-agentes-de-usuario
+locale: es
+kiStatus: Backlog
+internalReference: 1069222
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Un **user-agent** es una cadena de texto que un navegador web u otro cliente envía a un servidor web en una cabecera de petición HTTP para identificarse. Esta cadena contiene información sobre el tipo de navegador, sistema operativo, y a veces detalles adicionales como la versión del navegador y el motor de renderizado utilizado.
+
+A menudo se solicita como medida de seguridad por parte de servidores, como los que alojan imágenes, que pueden pasarse a través de una URL en el cuerpo de la solicitud de la API de inserción de archivos SKU.
+
+Este tipo de autenticación, sin embargo, no está soportada actualmente por las APIs VTEX.
+
+
+
+## Simulación
+
+
+1 - Utilizar la API de creación o actualización (métodos de escritura) de archivos SKU pasando una URL que tenga requisitos de agente de usuario del lado del servidor para obtener datos https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file
+
+2 - Se mostrará una respuesta de tipo 40x, ya sea un 400 genérico o un 403 más específico dependiendo del tipo de respuesta implementada.
+
+
+
+
+## Workaround
+
+
+O bien optar por la carga de archivos va hoja de cálculo, formulario de datos (utilizando las API) o desactivar los requisitos de agente de usuario en el lado del servidor.
+
+
+
+
+
diff --git a/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md b/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md
new file mode 100644
index 000000000..627f70ad8
--- /dev/null
+++ b/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md
@@ -0,0 +1,38 @@
+---
+title: 'Las opciones de pago a plazos no se actualizan automáticamente en PDP/PLP'
+id: 1PSjCEZyKatCZ9Q1W1zQOc
+status: PUBLISHED
+createdAt: 2024-02-23T12:31:32.446Z
+updatedAt: 2024-02-23T12:31:33.262Z
+publishedAt: 2024-02-23T12:31:33.262Z
+firstPublishedAt: 2024-02-23T12:31:33.262Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-opciones-de-pago-a-plazos-no-se-actualizan-automaticamente-en-pdpplp
+locale: es
+kiStatus: Backlog
+internalReference: 987467
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una cuenta cambia las opciones de pago a plazos de un producto, a pesar de que el producto está correctamente indexado, las opciones de pago a plazos no se actualizan en el PLP o en el PDP (a veces en ambos).
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md b/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
index aaa72eb78..a4f5bbd7a 100644
--- a/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
+++ b/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
@@ -3,8 +3,8 @@ title: 'La actualización del banner de búsqueda inteligente a través de la UR
 id: bMFrVUmfbjvTWs4Ag6U57
 status: PUBLISHED
 createdAt: 2023-01-17T14:34:02.195Z
-updatedAt: 2023-01-17T14:34:10.348Z
-publishedAt: 2023-01-17T14:34:10.348Z
+updatedAt: 2023-09-06T22:35:01.155Z
+publishedAt: 2023-09-06T22:35:01.155Z
 firstPublishedAt: 2023-01-17T14:34:02.912Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -23,7 +23,7 @@ internalReference: 734833
 </div>
 
 
-En Admin V4, en el módulo Banners, el usuario tiene la posibilidad de crear o actualizar banners ya creados. Al seleccionar un banner para actualizar, puede elegir entre utilizar un campo HTML o insertar un enlace de imagen directo con una URL externa. Al seleccionar insertar el banner mediante un enlace de imagen directo, se lanza la consulta GraphQL `setBanner`, que actualmente no funciona correctamente, devolviendo `syntaxError`, en consecuencia, error 500.
+En Admin V4, en el módulo Banners, el usuario tiene la posibilidad de crear o actualizar banners ya creados. Al seleccionar un banner para actualizar, puede elegir entre utilizar un campo HTML o insertar un enlace de imagen directo con una URL externa. Al seleccionar insertar el banner mediante un enlace de imagen directo, se lanza la consulta GraphQL, que actualmente no funciona correctamente, devolviendo `syntaxError`, en consecuencia, error 500.
 
 
 ##
@@ -43,7 +43,7 @@ Al hacer clic en Guardar, la pantalla mostrará un error GraphQL;
 ## Workaround
 
 
-Crear un nuevo banner con las mismas especificaciones (la consulta de creación del banner es `createBanner` y funciona correctamente);
+N/A
 
 
 
diff --git a/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md b/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
new file mode 100644
index 000000000..6b7478a4f
--- /dev/null
+++ b/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
@@ -0,0 +1,67 @@
+---
+title: 'Los ajustes de idioma de la búsqueda inteligente no están sincronizados con las configuraciones de las tiendas.'
+id: 1GqoAyUSbTxwHvzoMoAYfD
+status: PUBLISHED
+createdAt: 2024-02-27T21:30:40.309Z
+updatedAt: 2024-03-06T15:38:20.358Z
+publishedAt: 2024-03-06T15:38:20.358Z
+firstPublishedAt: 2024-02-27T21:30:41.209Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-ajustes-de-idioma-de-la-busqueda-inteligente-no-estan-sincronizados-con-las-configuraciones-de-las-tiendas
+locale: es
+kiStatus: Backlog
+internalReference: 990343
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El idioma principal de la Búsqueda Inteligente no se actualiza automáticamente según la política comercial y la configuración de vinculación, lo que hace que no esté sincronizado.
+
+En las tiendas con un solo idioma, los contenidos de la Búsqueda Inteligente, como sinónimos, reglas de comercialización, banners de búsqueda y redireccionamientos de búsqueda, se crean sobre las configuraciones regionales registradas en el enlace. La presentación de la tienda también se basa en la política comercial, que puede anular la vinculación y no coincidir con el contenido registrado.
+
+En el caso de las tiendas multilingües, también puede afectar a las traducciones proporcionadas en el escaparate y las API.
+
+
+
+## Simulación
+
+
+
+- Crear una tienda en "pt-BR";
+- Activar/configurar el módulo de Búsqueda Inteligente;
+- Cambiar la política comercial de "pt-BR" a "en-US";
+- Idioma único:
+  - Mantener la vinculación como "pt-BR";
+  - Crear contenido de búsqueda inteligente;
+  - Acceda a la página del escaparate que debe presentar el contenido registrado;
+  - El contenido/comportamiento no será visible.
+- Multi-idioma:
+  - Registre los productos en inglés;
+  - Añadir el portugués como segundo idioma/idioma alternativo en los enlaces
+  - Registrar traducciones del catálogo para portugués;
+  - En este escenario, la navegación entre ambos idiomas puede presentar problemas.
+
+
+
+
+## Workaround
+
+
+Asegúrese de que los enlaces y las políticas comerciales coinciden, de lo contrario, el contenido de la búsqueda no será válido.
+
+El contenido previamente registrado no seguirá el nuevo idioma principal si éste cambia; permanecerá unido a su idioma de creación. Es necesario registrar al menos dos locales en la configuración de bindings (el idioma antiguo/no esperado y el idioma nuevo/esperado) para ver el selector de idioma en el editor de contenidos y poder corregirlos manualmente para que utilicen el idioma esperado. Otro método es recrear el contenido.
+
+En algunos casos, como las traducciones multilingües y de catálogos, es posible que también tenga que ponerse en contacto con nuestro servicio de asistencia para revisar la configuración interna del idioma para la búsqueda inteligente.
+
+
+
+
+
diff --git a/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md b/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md
new file mode 100644
index 000000000..80e6b3304
--- /dev/null
+++ b/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md
@@ -0,0 +1,45 @@
+---
+title: 'La búsqueda inteligente no captura los eventos de venta para FastStore'
+id: 4sT3tm37DP6E6jWzYNHJQe
+status: PUBLISHED
+createdAt: 2024-06-05T22:21:23.343Z
+updatedAt: 2024-06-05T22:21:24.206Z
+publishedAt: 2024-06-05T22:21:24.206Z
+firstPublishedAt: 2024-06-05T22:21:24.206Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: la-busqueda-inteligente-no-captura-los-eventos-de-venta-para-faststore
+locale: es
+kiStatus: Scheduled
+internalReference: 1045163
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La Búsqueda Inteligente no está capturando los eventos de pedidos finalizados para las tiendas que utilizan FastStore. Estos eventos componen los criterios de relevancia y la clasificación de productos por ventas.
+
+
+##
+
+## Simulación
+
+
+El escenario se puede reproducir en cualquier tienda que utilice FastStore. La forma más fácil de ver el problema es observando que el informe de análisis de búsqueda no computa las ventas.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md b/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
new file mode 100644
index 000000000..68ba08511
--- /dev/null
+++ b/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
@@ -0,0 +1,44 @@
+---
+title: 'La barra de búsqueda distingue entre mayúsculas y minúsculas.'
+id: 5QEkcyhCQWyw093UkDCeOq
+status: PUBLISHED
+createdAt: 2023-09-26T23:50:50.661Z
+updatedAt: 2023-09-26T23:50:51.661Z
+publishedAt: 2023-09-26T23:50:51.661Z
+firstPublishedAt: 2023-09-26T23:50:51.661Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: la-barra-de-busqueda-distingue-entre-mayusculas-y-minusculas
+locale: es
+kiStatus: Backlog
+internalReference: 361894
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La página de configuración de Redirección de Búsqueda Inteligente tiene una barra de búsqueda para ayudar a encontrar configuraciones de redirección específicas, pero distingue entre mayúsculas y minúsculas y sólo encontrará términos si coinciden exactamente.
+
+
+##
+
+## Simulación
+
+
+Acceda a `/admin/search/redirects`.
+
+Buscar un nombre de configuración, pero cambiando una letra a mayúscula. La búsqueda no obtendrá ningún resultado.
+
+
+
+## Workaround
+
+
+Generar nombres de ruta con un patrón consistente, sólo minúsculas, sólo mayúsculas o camel case.
+
diff --git a/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md b/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
new file mode 100644
index 000000000..3cd22c398
--- /dev/null
+++ b/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
@@ -0,0 +1,50 @@
+---
+title: 'El analizador de palabras de la Búsqueda Inteligente no normaliza el género en las palabras portuguesas'
+id: 2oVUQnXZK6FNXg7co88C1B
+status: PUBLISHED
+createdAt: 2024-07-26T22:55:32.746Z
+updatedAt: 2024-07-26T22:55:46.558Z
+publishedAt: 2024-07-26T22:55:46.558Z
+firstPublishedAt: 2024-07-26T22:55:33.875Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: el-analizador-de-palabras-de-la-busqueda-inteligente-no-normaliza-el-genero-en-las-palabras-portuguesas
+locale: es
+kiStatus: Backlog
+internalReference: 1072003
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera que los términos buscados se normalicen entre sus diferentes formas (plural/singular, género y otras posibilidades), un proceso formalmente llamado stemming. El analizador es diferente para cada idioma para ajustarse a sus necesidades.
+
+El analizador para el portugués no normaliza el género de las palabras.
+
+
+##
+
+## Simulación
+
+
+Considere una palabra registrada en diferentes productos con diferentes géneros, como "camiseta listrada" y "vestido listrado".
+
+Aunque "listrada" y "listrado" son la misma palabra pero en formas de distinto género, la búsqueda de "listrada" no devolverá los "vestidos", y viceversa.
+
+
+
+## Workaround
+
+
+Registre sinónimos bidireccionales para palabras con variaciones de género relevantes.
+
+
+
+
+
diff --git a/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md b/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
new file mode 100644
index 000000000..ccf082de8
--- /dev/null
+++ b/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
@@ -0,0 +1,49 @@
+---
+title: 'Interactuar con el componente de direcciones mientras algunos datos de la interfaz de usuario aún están en estado de carga cambia el modo de inserción de direcciones.'
+id: 7t3jzIpIppmZDAc9R2BgpS
+status: PUBLISHED
+createdAt: 2023-09-13T20:39:43.294Z
+updatedAt: 2023-09-13T20:39:44.079Z
+publishedAt: 2023-09-13T20:39:44.079Z
+firstPublishedAt: 2023-09-13T20:39:44.079Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: interactuar-con-el-componente-de-direcciones-mientras-algunos-datos-de-la-interfaz-de-usuario-aun-estan-en-estado-de-carga-cambia-el-modo-de-insercion-de-direcciones
+locale: es
+kiStatus: Backlog
+internalReference: 423811
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el usuario elige cambiar su dirección mientras algunos datos respectivos todavía se están cargando en la página, el componente de dirección cambia de geolocalización al componente con un desplegable. Los datos pueden ser, por ejemplo, la selección de una tienda para recoger. Mientras los datos se cargan en la interfaz, el usuario hace clic en "cambiar dirección", con eso, la dirección de vuelta está en otro componente, no en el componente de geolocalización.
+
+
+##
+
+## Simulación
+
+
+
+- Configurar una cuenta para utilizar geocoordenadas en el pago;
+- Buscar una dirección en el paso de envío;
+- Haga clic en Cambiar mientras se carga la página;
+- El componente de la dirección cambiará y le pedirá que rellene la información de la dirección
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md b/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
new file mode 100644
index 000000000..0cc64c0e2
--- /dev/null
+++ b/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
@@ -0,0 +1,48 @@
+---
+title: 'Al interactuar con el componente de pago cuando aún se encuentra en estado de carga, se envía la opción de pago incorrecta.'
+id: 4kSvM6fti8YfgcUyl4qFJs
+status: PUBLISHED
+createdAt: 2023-12-12T22:07:58.762Z
+updatedAt: 2023-12-12T22:07:59.474Z
+publishedAt: 2023-12-12T22:07:59.474Z
+firstPublishedAt: 2023-12-12T22:07:59.474Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: al-interactuar-con-el-componente-de-pago-cuando-aun-se-encuentra-en-estado-de-carga-se-envia-la-opcion-de-pago-incorrecta
+locale: es
+kiStatus: Backlog
+internalReference: 952086
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el comprador cambia el método de pago mientras el componente de pago todavía se está cargando en la página, si el método de pago tiene opciones, el pago enviado al orderForm es incorrecto. Cuando se produce este comportamiento, el pedido no se crea y se muestra un mensaje para revisar la información de pago.
+
+
+##
+
+## Simulación
+
+
+
+- Añada artículos al carrito y muévase hasta los datos de pago;
+- Haga clic en un método de pago diferente mientras se carga la página y seleccione otra opción dentro del componente;
+- El pago enviado al orderForm es erróneo, siendo la primera opción.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/intermitent-site-editor-content-loss.md b/docs/known-issues/es/intermitent-site-editor-content-loss.md
new file mode 100644
index 000000000..1e8af4429
--- /dev/null
+++ b/docs/known-issues/es/intermitent-site-editor-content-loss.md
@@ -0,0 +1,52 @@
+---
+title: 'Pérdida intermitente de contenido del Editor de Sitios'
+id: 3a5MlAoD2Z7Gu6HDS8wihD
+status: PUBLISHED
+createdAt: 2022-07-05T17:07:24.733Z
+updatedAt: 2024-03-21T20:37:27.369Z
+publishedAt: 2024-03-21T20:37:27.369Z
+firstPublishedAt: 2022-07-05T17:07:25.091Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: perdida-intermitente-de-contenido-del-editor-de-sitios
+locale: es
+kiStatus: Scheduled
+internalReference: 610533
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cada cambio de contenido en el Editor de Sitios inserta cambios en el archivo content.json, que se almacena en un bucket en AWS S3. Algunos clientes han informado de la pérdida de contenido del Editor de Sitios tras algunos procedimientos habituales de actualización de temas.
+
+
+##
+
+## Simulación
+
+
+El escenario es intermitente, sin embargo, se ha reportado en dos escenarios diferentes:
+
+**1. Al promover un espacio de trabajo de producción a maestro:**
+Los clientes informaron de que al promover un espacio de trabajo de producción, que contenía cambios en los componentes, al entorno maestro, se producía una pérdida de contenido en otros espacios de trabajo.
+
+**2. Al instalar una nueva versión en un espacio de trabajo de prueba:**
+Los clientes informaron de que, al instalar una nueva versión del tema en un espacio de trabajo de prueba, se eliminaba el contenido de las páginas de categorías.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md b/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md
new file mode 100644
index 000000000..7f015de44
--- /dev/null
+++ b/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md
@@ -0,0 +1,48 @@
+---
+title: 'Tiempos de espera de InternalSearchError en el Portal'
+id: 6D6mdJ3zQypy1lcuht7WuU
+status: PUBLISHED
+createdAt: 2024-06-03T15:25:56.353Z
+updatedAt: 2024-07-30T13:55:06.518Z
+publishedAt: 2024-07-30T13:55:06.518Z
+firstPublishedAt: 2024-06-03T15:25:57.378Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: tiempos-de-espera-de-internalsearcherror-en-el-portal
+locale: es
+kiStatus: Backlog
+internalReference: 1043003
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En la actualidad, las tiendas que utilizan la búsqueda heredada del Portal pueden enfrentarse, al utilizar varios filtros en su tienda, como filtros de colección en plantillas, a tiempos de espera aleatorios e intermitentes que a menudo se muestran como un error "Algo ha ido mal" para los clientes.
+
+Este problema es, internamente, un tiempo de espera, que está siendo analizado por los equipos técnicos para aumentar su tiempo.
+
+
+##
+
+## Simulación
+
+
+Este error es muy intermitente y difícil de replicar de forma consistente. Suele ser más frecuente en cuentas que utilizan varios filtros de recogida en sus plantillas, pero no hay una forma fiable de replicarlo.
+
+
+
+## Workaround
+
+
+Mientras no se investigan y aumentan los tiempos de espera, se recomienda reducir la cantidad de filtros que se utilizan en las búsquedas y los menús, aunque no se garantiza que se eliminen por completo dichos tiempos de espera, pero sí que se reducen significativamente.
+
+
+
+
+
diff --git a/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
new file mode 100644
index 000000000..7ad921710
--- /dev/null
+++ b/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -0,0 +1,50 @@
+---
+title: 'Mensaje "Código postal no válido" en la interfaz de usuario de la caja cuando la dirección está en las direcciones disponibles con un país diferente.'
+id: 4VggIx4xWPNW6OBIrQ0js4
+status: PUBLISHED
+createdAt: 2024-06-21T17:08:59.860Z
+updatedAt: 2024-06-21T17:09:00.771Z
+publishedAt: 2024-06-21T17:09:00.771Z
+firstPublishedAt: 2024-06-21T17:09:00.771Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: mensaje-codigo-postal-no-valido-en-la-interfaz-de-usuario-de-la-caja-cuando-la-direccion-esta-en-las-direcciones-disponibles-con-un-pais-diferente
+locale: es
+kiStatus: Backlog
+internalReference: 1053959
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Checkout UI utiliza el país registrado en su estado para validar la entrada del código postal.
+
+Cuando las direcciones están registradas en direcciones disponibles, pero el orderForm se cambia a otro canal de venta, y este canal de venta tiene un país diferente para enviar, se muestra el mensaje "Código postal no válido" justo debajo de la entrada del código postal, no pudiendo seguir adelante con la compra.
+
+
+##
+
+## Simulación
+
+
+
+- Montar un carrito y añadir una dirección;
+- Cambie el canal de venta, donde envía a un país diferente;
+- Intente añadir el nuevo código postal; se muestra "Código postal no válido".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md b/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md
new file mode 100644
index 000000000..264473225
--- /dev/null
+++ b/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md
@@ -0,0 +1,55 @@
+---
+title: 'Las notificaciones de inventario al indexador se almacenan en caché'
+id: 2eFmUbO1PR7ahxAGiMkqZd
+status: PUBLISHED
+createdAt: 2023-10-05T12:48:05.930Z
+updatedAt: 2024-05-14T11:26:36.897Z
+publishedAt: 2024-05-14T11:26:36.897Z
+firstPublishedAt: 2023-10-05T12:48:06.727Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-notificaciones-de-inventario-al-indexador-se-almacenan-en-cache
+locale: es
+kiStatus: Fixed
+internalReference: 914545
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una cuenta de franquicia o vendedor notifica a la cuenta principal (o marketplace) sobre cambios en el inventario, la cuenta envía el producto al indexador para tener la información más actualizada.
+
+El sistema responsable de recibir las notificaciones y pasarlas al indexador es Broadcaster.
+
+El problema es que el flujo de trabajo Disponibilidad -> Emisor -> Indexador funciona a un ritmo muy rápido y en algunos casos la información sigue almacenada en caché. De esta forma el Indexador se queda con la información antigua hasta una nueva indexación.
+
+
+##
+
+## Simulación
+
+
+No hay una forma fácil de simular este escenario, ya que no ocurre en todas las ocasiones.
+El proceso debería ser:
+
+1. La cuenta de la franquicia actualiza un inventario;
+2. El emisor envía el producto al indexador;
+3. 3. El indexador actualiza el sku de la cuenta principal con la información antigua.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/inventory-reserved-items-error.md b/docs/known-issues/es/inventory-reserved-items-error.md
index b41ee1172..24776d768 100644
--- a/docs/known-issues/es/inventory-reserved-items-error.md
+++ b/docs/known-issues/es/inventory-reserved-items-error.md
@@ -1,36 +1,41 @@
 ---
-title: 'Inventory Reserved Items Error'
+title: 'Error de artículos reservados de inventario'
 id: 37cO3T4D0exvOMhStKYds9
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-18T15:13:46.087Z
-updatedAt: 2022-06-27T12:33:44.492Z
-publishedAt: 2022-06-20T12:39:37.793Z
+updatedAt: 2024-07-03T20:14:35.313Z
+publishedAt: 2024-07-03T20:14:35.313Z
 firstPublishedAt: 2022-05-18T15:13:46.568Z
 contentType: knownIssue
 productTeam: Logistics
 author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
-slug: inventory-reserved-items-error
+slug: error-de-articulos-reservados-de-inventario
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 347924
 ---
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
+
+
+Comprobando los artículos de estado reservado en **Gestión de Inventario**, hay un error al mostrar los pedidos relacionados.
+
+No es posible ver los pedidos pulsando sobre el número de artículos reservados, muestra el mensaje de error "Se ha producido un error al cargar las reservas. Por favor, inténtelo de nuevo".
+
+
+##
+
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+
 
diff --git a/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
new file mode 100644
index 000000000..f0f03c11d
--- /dev/null
+++ b/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -0,0 +1,49 @@
+---
+title: 'Los caracteres invisibles en los nombres de categoría provocan errores de "página no encontrada".'
+id: 4np2BZUF1EmlLmV0KTpnrf
+status: PUBLISHED
+createdAt: 2024-07-05T13:11:13.031Z
+updatedAt: 2024-07-05T13:11:14.090Z
+publishedAt: 2024-07-05T13:11:14.090Z
+firstPublishedAt: 2024-07-05T13:11:14.090Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: los-caracteres-invisibles-en-los-nombres-de-categoria-provocan-errores-de-pagina-no-encontrada
+locale: es
+kiStatus: Backlog
+internalReference: 1061149
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al crear categorías a través de la API o del panel de administración, el nombre de la categoría no se valida correctamente, lo que permite incluir caracteres invisibles. Dado que el nombre de la categoría se utiliza para generar la URL de la categoría, estos caracteres invisibles también se incluyen en la URL. Esto provoca que la página de la categoría no funcione correctamente y devuelva un error de "Página no encontrada".
+
+
+##
+
+## Simulación
+
+
+
+1. Crea una categoría con un carácter invisible en su nombre utilizando la API o el panel de administración.
+2. Acceda a la URL de la API para esta categoría.
+3. Observe el error "Página no encontrada".
+
+
+
+## Workaround
+
+
+
+La solución consiste en eliminar el carácter invisible del nombre de la categoría, lo que también actualizará la URL de la página, resolviendo el problema.
+
+
+
+
diff --git a/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md b/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
index a46e80211..c50dfcd9c 100644
--- a/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
+++ b/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
@@ -3,8 +3,8 @@ title: 'El parámetro isAvailablePerSalesChannel no funciona como se espera en l
 id: 6vexCZQTib8fFI6sCSTdWL
 status: PUBLISHED
 createdAt: 2022-09-12T16:03:25.215Z
-updatedAt: 2022-11-25T21:43:40.015Z
-publishedAt: 2022-11-25T21:43:40.015Z
+updatedAt: 2024-02-16T20:24:54.890Z
+publishedAt: 2024-02-16T20:24:54.890Z
 firstPublishedAt: 2022-09-12T16:03:25.837Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-parametro-isavailablepersaleschannel-no-funciona-como-se-espera-en-la-api-de-busqueda
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 656284
 ---
 
diff --git a/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md b/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md
index dc6bd19d5..59c7c9bff 100644
--- a/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md
+++ b/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md
@@ -3,8 +3,8 @@ title: 'Problema en la Búsqueda Explicada para las búsquedas con tildes'
 id: 5rh2FSzIeSjnO7bUlEkJ9S
 status: PUBLISHED
 createdAt: 2022-02-23T21:59:57.268Z
-updatedAt: 2022-11-25T21:58:45.841Z
-publishedAt: 2022-11-25T21:58:45.841Z
+updatedAt: 2024-02-16T20:28:06.748Z
+publishedAt: 2024-02-16T20:28:06.748Z
 firstPublishedAt: 2022-02-23T21:59:57.508Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: problema-en-la-busqueda-explicada-para-las-busquedas-con-tildes
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 434752
 ---
 
diff --git a/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md b/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md
index 203ad0335..ba09ed1f4 100644
--- a/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md
+++ b/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md
@@ -3,8 +3,8 @@ title: 'Problema al traducir los títulos de algunas facetas'
 id: iG3Kb1AfH7QIqYn1ewnuw
 status: PUBLISHED
 createdAt: 2023-03-22T19:26:31.477Z
-updatedAt: 2023-03-22T19:26:31.933Z
-publishedAt: 2023-03-22T19:26:31.933Z
+updatedAt: 2023-10-27T00:51:10.361Z
+publishedAt: 2023-10-27T00:51:10.361Z
 firstPublishedAt: 2023-03-22T19:26:31.933Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: problema-al-traducir-los-titulos-de-algunas-facetas
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 776353
 ---
 
@@ -23,7 +23,7 @@ internalReference: 776353
 </div>
 
 
-Hay algunos casos en los que el título de la página es incorrecto para las tiendas multilingües en páginas como categoría, subcategoría y marcas, donde la ruta tiene un valor en ella y al mirar el título de la página tiene un nombre diferente que no coincide con el esperado.
+Hay algunos casos en los que el título de la página es incorrecto para las tiendas multilingües en páginas como categoría, subcategoría y marcas, donde la ruta tiene un valor en él y al mirar el título de la página tiene un nombre diferente que no coincide con el esperado.
 
 
 ##
@@ -31,8 +31,12 @@ Hay algunos casos en los que el título de la página es incorrecto para las tie
 ## Simulación
 
 
+Comprobar la ruta que se está montando también comprobar si la tienda es multilenguaje, y si esta no coincide con la ruta y las respectivas traducciones, si no coincide esto es un bug.
+
+
 
 ## Workaround
 
 
+N/A
 
diff --git a/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md b/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
new file mode 100644
index 000000000..725d1700f
--- /dev/null
+++ b/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
@@ -0,0 +1,46 @@
+---
+title: 'Problema con las API de sesión que utilizan propiedades públicas que empiezan por el mismo prefijo'
+id: RAoSKg2hwwiC6L7wFPyNv
+status: PUBLISHED
+createdAt: 2023-08-21T20:00:45.403Z
+updatedAt: 2023-08-21T20:11:44.751Z
+publishedAt: 2023-08-21T20:11:44.751Z
+firstPublishedAt: 2023-08-21T20:00:46.132Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: problema-con-las-api-de-sesion-que-utilizan-propiedades-publicas-que-empiezan-por-el-mismo-prefijo
+locale: es
+kiStatus: Backlog
+internalReference: 885011
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La API de sesión está generando algunas inconsistencias. El equipo de ingeniería ha identificado el fallo, el fallo está relacionado con propiedades que empiezan por la misma palabra.
+
+
+##
+
+## Simulación
+
+
+Si haces un POST enviando 2 valores públicos con el mismo prefijo, la API sólo recibe uno. Si lo intentas de nuevo, haciendo el mismo POST enviando los mismos 2 valores, la API recibe ambos.
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md b/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
new file mode 100644
index 000000000..3868b8798
--- /dev/null
+++ b/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
@@ -0,0 +1,46 @@
+---
+title: 'Problemas al insertar valores en la tarjeta regalo de fidelización en la caja'
+id: 74bFvs0PmQzRGzkOdnwiLw
+status: PUBLISHED
+createdAt: 2023-11-28T17:16:34.758Z
+updatedAt: 2023-11-28T17:16:35.407Z
+publishedAt: 2023-11-28T17:16:35.407Z
+firstPublishedAt: 2023-11-28T17:16:35.407Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: problemas-al-insertar-valores-en-la-tarjeta-regalo-de-fidelizacion-en-la-caja
+locale: es
+kiStatus: Backlog
+internalReference: 943629
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar la tarjeta regalo de fidelización, los usuarios pueden tener una mala experiencia al seleccionar la opción "Utilizar sólo parte del valor", ya que no hay ningún botón "Añadir" después de rellenar "Valor a utilizar" (la entrada se acepta automáticamente), por lo que si un valor no se rellena lo suficientemente rápido, se actualizará sólo con los primeros dígitos, obligando al usuario a repetir el procedimiento. Esta experiencia es peor a través del sitio web para móviles.
+
+
+
+## Simulación
+
+
+Después de crear una tarjeta regalo de fidelización a un correo electrónico aparecerá en la caja y se podrá proceder con el escenario descrito anteriormente.
+
+https://support.vtex.com/hc/en-us/articles/12897485276443
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md b/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md
new file mode 100644
index 000000000..eda50deff
--- /dev/null
+++ b/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md
@@ -0,0 +1,51 @@
+---
+title: 'Problemas con BillingAddress que provocan cancelaciones de transacciones'
+id: 14RT6S4Hm7H30L0FBzdDRY
+status: PUBLISHED
+createdAt: 2024-05-06T16:34:12.989Z
+updatedAt: 2024-05-06T16:34:14.299Z
+publishedAt: 2024-05-06T16:34:14.299Z
+firstPublishedAt: 2024-05-06T16:34:14.299Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: problemas-con-billingaddress-que-provocan-cancelaciones-de-transacciones
+locale: es
+kiStatus: Backlog
+internalReference: 1027901
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Se están cancelando transacciones durante el análisis antifraude debido a que falta información esencial en la `billingAddress`.
+
+La `billingAddress` se envía durante el proceso de pago y puede ser una copia de la `shippingAddress` si el usuario decide no diferenciarlas (marcando `isBillingAddressDifferent` como `false`) durante el pago. Alternativamente, puede ser una nueva dirección proporcionada por el usuario si la opción `isBillingAddressDifferent` está marcada como `true`. Esta dirección se utiliza en la solicitud de autorización antifraude, y la ausencia de información obligatoria puede dar lugar a cancelaciones de transacciones.
+
+Hemos observado que este comportamiento se produce con pagos realizados con tarjetas nuevas, que no se han guardado previamente en la tienda, y cuando el usuario elige no diferenciar las direcciones (`isBillingAddressDifferent`: `false`). Es importante destacar que la `shippingAaddress` contiene todos los campos obligatorios correctamente rellenados, mientras que la `billingAddress`, que debería ser una copia de la `shippingAddress`, queda incompleta.
+
+
+##
+
+## Simulación
+
+
+No hemos podido reproducir este problema
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/issues-with-my-account-links.md b/docs/known-issues/es/issues-with-my-account-links.md
new file mode 100644
index 000000000..49e050d67
--- /dev/null
+++ b/docs/known-issues/es/issues-with-my-account-links.md
@@ -0,0 +1,48 @@
+---
+title: 'Problemas con los enlaces de Mi cuenta'
+id: 1p23CCNhJwnEXm501P9Nxh
+status: PUBLISHED
+createdAt: 2023-07-03T17:26:59.597Z
+updatedAt: 2023-07-03T17:27:00.108Z
+publishedAt: 2023-07-03T17:27:00.108Z
+firstPublishedAt: 2023-07-03T17:27:00.108Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: problemas-con-los-enlaces-de-mi-cuenta
+locale: es
+kiStatus: Backlog
+internalReference: 522514
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los enlaces en Mi Cuenta (menú de cabecera) no funcionan si el usuario ya está en la sección Mi Cuenta
+
+
+##
+
+## Simulación
+
+
+Acceso a la página Mi cuenta
+Hacer clic en el enlace del menú de cabecera (como la opción Pedidos, por ejemplo)
+Compruebe que la url se modifica, pero la página no se carga
+
+
+
+## Workaround
+
+
+No hay solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md b/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
new file mode 100644
index 000000000..168bd1d4b
--- /dev/null
+++ b/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
@@ -0,0 +1,54 @@
+---
+title: 'No es posible añadir un artículo con accesorio a la cesta si ya hay otra unidad de este artículo sin accesorio en la cesta'
+id: 3l41VmdtPCxUjYChuO7o9O
+status: PUBLISHED
+createdAt: 2021-09-15T15:24:52.309Z
+updatedAt: 2024-02-02T15:01:32.297Z
+publishedAt: 2024-02-02T15:01:32.297Z
+firstPublishedAt: 2021-09-15T15:30:26.487Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: no-es-posible-anadir-un-articulo-con-accesorio-a-la-cesta-si-ya-hay-otra-unidad-de-este-articulo-sin-accesorio-en-la-cesta
+locale: es
+kiStatus: No Fix
+internalReference: 412041
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Durante el proceso de compra, si el cliente añade un artículo que ya ha sido incluido en el carrito anteriormente y la nueva inclusión tiene opciones de montaje, el segundo artículo no se añade al carrito.
+
+Por ejemplo, si durante el proceso de compra, el cliente añade un SKU al carrito y, a continuación, otra unidad del mismo SKU pero con garantía ampliada (mediante assemblyOptions), el último artículo añadido (el artículo con garantía ampliada) no estará disponible en el carrito.
+
+
+##
+
+## Simulación
+
+
+Para realizar la simulación, asegúrese de que hay artículos con opciones de montaje en su tienda.
+
+
+1. Acceda al almacén;
+2. Añadir un producto al carrito;
+3. Añadir de nuevo el producto e incluir una opción de montaje al artículo (una personalización o una ampliación de garantía, por ejemplo);
+4. 4. Compruebe la cesta y verifique que no se ha añadido el artículo con la opción de montaje.
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md b/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
new file mode 100644
index 000000000..f1485b0ac
--- /dev/null
+++ b/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
@@ -0,0 +1,50 @@
+---
+title: 'No es posible crear una ruta utilizando el tipo de contenido a través de UI'
+id: 3jVjkZYCATrnDNhR0IKSEA
+status: PUBLISHED
+createdAt: 2023-10-23T13:19:09.970Z
+updatedAt: 2024-07-01T18:49:16.580Z
+publishedAt: 2024-07-01T18:49:16.580Z
+firstPublishedAt: 2023-10-23T13:19:10.738Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: no-es-posible-crear-una-ruta-utilizando-el-tipo-de-contenido-a-traves-de-ui
+locale: es
+kiStatus: No Fix
+internalReference: 923619
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si intentamos crear una ruta usando tipos de contenido a través de la UI la página no funcionará. Sólo funciona si la creamos a través del tema.
+
+
+##
+
+## Simulación
+
+
+
+- Crea una ruta utilizando un tipo de contenido en el módulo Pages, por ejemplo, `storeTest/:test_id`.
+- Guárdala
+- Intenta acceder a ella desde el front
+- No funcionará
+
+
+
+## Workaround
+
+
+Si añadimos la ruta usando el tipo de contenido a través del tema, la página aparecerá en la UI y funcionará
+
+
+
+
+
diff --git a/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md b/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
new file mode 100644
index 000000000..d1208f2cb
--- /dev/null
+++ b/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
@@ -0,0 +1,49 @@
+---
+title: 'El autocompletado de artículos no se muestra en la etiqueta blanca del vendedor (cambiar orden)'
+id: 1jvkXj20gVHNtpp3KNL5GW
+status: PUBLISHED
+createdAt: 2024-03-05T21:55:53.411Z
+updatedAt: 2024-03-11T20:00:01.928Z
+publishedAt: 2024-03-11T20:00:01.928Z
+firstPublishedAt: 2024-03-05T21:55:54.222Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: el-autocompletado-de-articulos-no-se-muestra-en-la-etiqueta-blanca-del-vendedor-cambiar-orden
+locale: es
+kiStatus: Backlog
+internalReference: 348841
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al modificar un artículo (orden de modificación) desde una cuenta de vendedor de Marca Blanca, el autocompletado no muestra el artículo como se esperaba.
+
+
+
+##
+
+## Simulación
+
+
+- Accede a un pedido desde una cuenta de vendedor de marca blanca, y solicita la opción de cambio de artículo:
+- Al rellenar el nombre SKU en la búsqueda, no se muestra por autocompletar:
+- Lo mismo ocurre con el vendedor de marca blanca con la nueva versión de admin-orders:
+
+
+
+## Workaround
+
+
+Puede realizar el cambio de artículo a través de la API Registrar cambio en pedido.
+
+
+
+
+
diff --git a/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md b/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md
new file mode 100644
index 000000000..ba30d5f27
--- /dev/null
+++ b/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md
@@ -0,0 +1,50 @@
+---
+title: 'Artículo disponible cuando la ubicación del cliente no está definida sin existencias'
+id: 7vDywP0WtfpJ4bCiNkXNfw
+status: PUBLISHED
+createdAt: 2024-07-30T22:51:30.425Z
+updatedAt: 2024-07-30T22:54:29.056Z
+publishedAt: 2024-07-30T22:54:29.056Z
+firstPublishedAt: 2024-07-30T22:51:31.764Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: articulo-disponible-cuando-la-ubicacion-del-cliente-no-esta-definida-sin-existencias
+locale: es
+kiStatus: Backlog
+internalReference: 1073363
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la ubicación del cliente no está definida, los artículos aparecen disponibles incluso cuando no hay existencias disponibles y la marca blanca del vendedor no es completa. Esto solo ocurre si la SKU tiene existencias en el vendedor de marca blanca en un almacén asociado a un canal de ventas distinto al registrado en el punto final de cumplimiento del vendedor.
+
+
+##
+
+## Simulación
+
+
+
+- No hay stock para el vendedor 1;
+- Ningún vendedor integral configurado;
+- Stock en un vendedor de marca blanca en un canal de ventas diferente al punto final de cumplimiento, por ejemplo:
+Punto final de cumplimiento con sc=1;
+Stock en el vendedor para sc=2.
+
+
+
+## Workaround
+
+ provisional
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md b/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
new file mode 100644
index 000000000..378e1e5fc
--- /dev/null
+++ b/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
@@ -0,0 +1,49 @@
+---
+title: 'item_name del evento de compra es diferente de item_name del evento de añadir al carrito en Google Analytics'
+id: 3FV2cJIV7uOIoH0lpl0iMP
+status: PUBLISHED
+createdAt: 2023-08-10T12:59:26.495Z
+updatedAt: 2023-08-10T12:59:27.432Z
+publishedAt: 2023-08-10T12:59:27.432Z
+firstPublishedAt: 2023-08-10T12:59:27.432Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: itemname-del-evento-de-compra-es-diferente-de-itemname-del-evento-de-anadir-al-carrito-en-google-analytics
+locale: es
+kiStatus: Backlog
+internalReference: 878629
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el SKU tiene el mismo nombre que el producto, el item_name de la compra es diferente del item_name del evento add-to-cart.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir un producto al carrito cuyo nombre es similar al nombre de su SKU. Por ejemplo, "Calcetines" es el nombre del producto y el nombre SKU es "Calcetines - G"
+- Busca su item_name en el evento add-to-cart
+- Finalice la compra y busque el item_name en el evento de compra
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md b/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
new file mode 100644
index 000000000..c26fe60a0
--- /dev/null
+++ b/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
@@ -0,0 +1,55 @@
+---
+title: 'Partidas en beneficios no generados en promociones con cobros asociados'
+id: 9HrnxMcq7VWFQOPhg9ywd
+status: PUBLISHED
+createdAt: 2024-02-21T15:09:01.111Z
+updatedAt: 2024-02-21T15:09:01.913Z
+publishedAt: 2024-02-21T15:09:01.913Z
+firstPublishedAt: 2024-02-21T15:09:01.913Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: partidas-en-beneficios-no-generados-en-promociones-con-cobros-asociados
+locale: es
+kiStatus: Backlog
+internalReference: 985850
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al tener una promoción con productos/skus asociados a través de una colección, el productContext no está preparado para crear el array de items dentro de los beneficios asociados a los productos de la colección
+
+
+##
+
+## Simulación
+
+
+
+
+- Crear una promoción
+- Asociar los productos para esta promoción a través de una colección
+- Abra uno de los productos que debe tener una promoción
+- Abre la consola de tu navegador
+- Comprueba en tu extensión React Dev Tools el productContextProvider
+- Abre benefits.items, estará vacío o con el sku con el mismo id de la colección
+
+
+
+## Workaround
+
+
+
+La única forma posible de tener benefits.items lleno es llenando todos los skus asociados a la promoción en lugar de un cluster/colección
+
+
+
+
+
diff --git a/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md b/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md
index 25137f252..90575704a 100644
--- a/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md
+++ b/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md
@@ -3,8 +3,8 @@ title: 'La API de creación de kits no calcula los precios de los componentes'
 id: 3yyIEv6o3CjIbUg4KoLOWT
 status: PUBLISHED
 createdAt: 2023-03-28T16:34:55.491Z
-updatedAt: 2023-03-28T16:34:55.990Z
-publishedAt: 2023-03-28T16:34:55.990Z
+updatedAt: 2024-04-02T18:36:44.624Z
+publishedAt: 2024-04-02T18:36:44.624Z
 firstPublishedAt: 2023-03-28T16:34:55.990Z
 contentType: knownIssue
 productTeam: Catalog
@@ -36,9 +36,7 @@ El Precio del kit debería ser: 10*2 + 25 === 45.
 
 Esto es lo que ocurre en el KIT UI SkuKit.aspx.
 
-Sin embargo, la API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit no tiene en cuenta los componentes múltiples en la suma, por lo que el precio sólo considera cada componente una vez en el cálculo (entonces, nuestro ejemplo anterior sería, incorrectamente, 10 + 25 = 35).
-
-
+Sin embargo, la API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit no realiza estas actualizaciones de precios para componentes distintos del primero que se añade.
 
 
 
@@ -47,7 +45,7 @@ Sin embargo, la API https://developers.vtex.com/docs/api-reference/catalog-api#p
 ## Simulación
 
 
-Crear un kit utilizando la siguiente API con un componente con una cantidad de 2 o más https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit y luego comprobar su precio en la interfaz de usuario del módulo de precios.
+Cree un kit utilizando la siguiente API con un componente con una cantidad de 2 o más https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit y, a continuación, compruebe su precio en la interfaz de usuario del módulo de precios.
 
 
 
@@ -57,5 +55,5 @@ Crear un kit utilizando la siguiente API con un componente con una cantidad de 2
 ## Workaround
 
 
-Al crear un kit, vaya a la interfaz de usuario y guarde los componentes una vez más para ejecutar la lógica de cálculo de la suma ponderada mencionada.
+Introduzca el precio final del kit directamente a través de la API de precios.
 
diff --git a/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md b/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md
index f533c737d..4558701f2 100644
--- a/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md
+++ b/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md
@@ -3,8 +3,8 @@ title: 'El peso del kit puede ser sobrescrito por la API/servicio web'
 id: Dlrs4qgHsnwIHxqqV0Rmg
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:40.711Z
-updatedAt: 2022-11-25T21:43:12.999Z
-publishedAt: 2022-11-25T21:43:12.999Z
+updatedAt: 2024-02-16T20:29:08.522Z
+publishedAt: 2024-02-16T20:29:08.522Z
 firstPublishedAt: 2022-06-28T16:55:40.971Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-peso-del-kit-puede-ser-sobrescrito-por-la-apiservicio-web
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429993
 ---
 
diff --git a/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md b/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
index c575ca87c..9282aa658 100644
--- a/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
+++ b/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
@@ -3,8 +3,8 @@ title: 'Konduto AF no puede completar una solicitud cuando falta el accountId.'
 id: CGHZoCfr01ATsbtiLU9ym
 status: PUBLISHED
 createdAt: 2022-03-03T22:09:57.638Z
-updatedAt: 2022-11-25T22:05:52.845Z
-publishedAt: 2022-11-25T22:05:52.845Z
+updatedAt: 2023-06-20T17:54:26.840Z
+publishedAt: 2023-06-20T17:54:26.840Z
 firstPublishedAt: 2022-03-03T22:09:58.094Z
 contentType: knownIssue
 productTeam: Payments
@@ -23,22 +23,27 @@ internalReference: 496298
 </div>
 
 
-
-Algunas transacciones no pueden ser terminadas porque el antifraude de Konduto no hace la solicitud adecuada porque falta el accountId utilizado para obtener la información de pago de la tabla de la base de datos de cuentas. Esto se puede validar mirando la ruta /payment donde el nodo "usedAccountId" es falso en este caso.
+Existe un problema para aprobar algunas transacciones que está relacionado con el sistema antifraude Konduto. Este problema surge cuando el sistema no puede realizar la petición necesaria debido a la ausencia del accountId, que es necesario para recuperar la información del pago de la base de datos de cuentas. Puede comprobarlo examinando la ruta "/payment", donde encontrará el nodo "usedAccountId" con valor "False" en estos casos.
 
 **{**"name": "usedAccountId", "value": "False "**}**
 
+Además, este problema suele observarse cuando un usuario elimina su propia tarjeta de la página MiCuenta inmediatamente después de realizar un pedido.
+
 
 
 ## Simulación
 
 
-Este error no se puede reproducir en este momento, se produce de forma intermitente.
+Siga el paso anterior, que consiste en eliminar una tarjeta inmediatamente después de realizar un pedido utilizando Konduto Antifraude.
 
 
 
 ## Workaround
 
 
-No hay ninguna solución disponible.
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md b/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md
index 7ff59b27e..e90398b26 100644
--- a/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md
+++ b/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md
@@ -3,8 +3,8 @@ title: 'Error al importar/exportar una hoja de cálculo grande en el nuevo admin
 id: 6xbBVR2Z7CCpIC0iCAKHgN
 status: PUBLISHED
 createdAt: 2023-02-16T19:04:08.298Z
-updatedAt: 2023-02-16T19:04:08.784Z
-publishedAt: 2023-02-16T19:04:08.784Z
+updatedAt: 2023-12-12T21:08:23.871Z
+publishedAt: 2023-12-12T21:08:23.871Z
 firstPublishedAt: 2023-02-16T19:04:08.784Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: error-al-importarexportar-una-hoja-de-calculo-grande-en-el-nuevo-administrador-de-cobros
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 362017
 ---
 
@@ -23,9 +23,8 @@ internalReference: 362017
 </div>
 
 
-Actualmente, el administrador de la nueva colección, en la función de importación de una inclusión SKU, utilizando la fila SKU, suele devolver una respuesta de error inespecífica al intentar importar un archivo con demasiados registros.
-
-"Su archivo no se ha importado. Por favor, intente importar este archivo de nuevo.`"
+Actualmente, subir artículos al nuevo módulo de colecciones con una lista de más de 1000 SKUs es imposible, ya que el proceso se agota. Devuelve una respuesta de error inespecífica
+"Su archivo no fue importado. Por favor, intente importar este archivo de nuevo.`"
 
 
 ##
@@ -34,7 +33,19 @@ Actualmente, el administrador de la nueva colección, en la función de importac
 
 
 
+1. Ir al módulo de nuevas colecciones
+2. Selecciona la pestaña "Importar"
+3. Utilice una hoja que tenga más de 1000 SKUs (es decir, 300 productos con 50 SKUs, cada uno)
+4. La importación generará un tiempo de espera.
+
+
+
 ## Workaround
 
 
+Cargue gradualmente utilizando hojas más pequeñas, las colecciones CMS heredadas y/o la API de inserción de SKU a subcolección https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/subcollection/-subCollectionId-/stockkeepingunit
+
+
+
+
 
diff --git a/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md b/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
index 06c3e632f..c5813c6be 100644
--- a/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
+++ b/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
@@ -1,18 +1,18 @@
 ---
-title: 'El Lean Shipping es forzado incluso cuando los artículos tienen los mismos SLAs, pero en una ordenación diferente'
+title: 'Lean Shipping forzado incluso cuando los artículos tienen los mismos ANS, pero en una ordenación diferente.'
 id: 2YTqsVWPm73msQZVQX9x80
 status: PUBLISHED
 createdAt: 2022-05-13T17:26:15.513Z
-updatedAt: 2022-11-25T21:52:30.793Z
-publishedAt: 2022-11-25T21:52:30.793Z
+updatedAt: 2023-09-11T21:38:39.068Z
+publishedAt: 2023-09-11T21:38:39.068Z
 firstPublishedAt: 2022-05-13T17:26:16.378Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: el-lean-shipping-es-forzado-incluso-cuando-los-articulos-tienen-los-mismos-slas-pero-en-una-ordenacion-diferente
+slug: lean-shipping-forzado-incluso-cuando-los-articulos-tienen-los-mismos-ans-pero-en-una-ordenacion-diferente
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 455218
 ---
 
@@ -23,12 +23,25 @@ internalReference: 455218
 </div>
 
 
+En algunos escenarios es posible que aunque la función LeanShipping esté desactivada en la configuración, el sistema aún considere necesario agrupar las opciones de envío, y con ello no desactivará leanShipping, esto se debe a que la regla utilizada por el sistema para definir el uso o no de leanShipping distinta a la configuración está activada o desactivada y existen los mismos o diferentes ANS disponibles para los artículos del carrito;
+Sin embargo, hay escenarios donde sólo el orden de cómo se entregan los ANS hace que el sistema entienda que son ANS diferentes y active leanShipping en el checkout y comience a mostrar las etiquetas más rápidas y baratas para el método de envío.
+
+
+##
 
 ## Simulación
 
 
+No existe una forma lineal de replicar el escenario, sin embargo puede ocurrir siempre que tengamos un carrito con dos o más artículos cuyos slas son similares entre los artículos, y se están presentando en diferentes órdenes dentro del objeto sla de cada artículo;
+
+
+##
 
 ## Workaround
 
 
+N/A
+
+
+
 
diff --git a/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
new file mode 100644
index 000000000..4d4a5f9ff
--- /dev/null
+++ b/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -0,0 +1,52 @@
+---
+title: 'Lean shipping provoca "Algo salió mal" tras cambiar los puntos de recogida'
+id: 45jQODtjZ4vLXniNJIlQZc
+status: PUBLISHED
+createdAt: 2024-06-20T21:11:53.067Z
+updatedAt: 2024-06-20T21:15:28.608Z
+publishedAt: 2024-06-20T21:15:28.608Z
+firstPublishedAt: 2024-06-20T21:11:53.899Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: lean-shipping-provoca-algo-salio-mal-tras-cambiar-los-puntos-de-recogida
+locale: es
+kiStatus: Backlog
+internalReference: 1053609
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Un comprador puede buscar diferentes puntos de recogida en diferentes códigos postales. Al utilizar lean shipping, después de añadir un código postal con puntos de recogida disponibles y cambiar a un código postal sin puntos de recogida, el paso de envío se bloquea con el mensaje "Algo ha ido mal".
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/i0jCDFlz5EGPnKyk5Nfw0Etl0/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+
+- Montar un carro y seleccionar recogida en punto en el carro;
+- Añadir un código postal con recogida;
+- Seleccionar una de las recogidas
+- Cambiar a un código postal sin puntos de recogida;
+- Ir a la caja y aparece el mensaje "Algo ha ido mal" en el paso de envío.
+
+
+
+## Workaround
+
+
+Actualice la página o desactive el envío flexible.
+
+
+
+
diff --git a/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md b/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
new file mode 100644
index 000000000..9b032414e
--- /dev/null
+++ b/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
@@ -0,0 +1,49 @@
+---
+title: 'Lean Shipping no se desactiva después de quitar artículos del carrito'
+id: 4dZZz28csz9BLhJNvQGHQV
+status: PUBLISHED
+createdAt: 2023-10-09T14:20:03.767Z
+updatedAt: 2023-10-09T14:20:04.692Z
+publishedAt: 2023-10-09T14:20:04.692Z
+firstPublishedAt: 2023-10-09T14:20:04.692Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: lean-shipping-no-se-desactiva-despues-de-quitar-articulos-del-carrito
+locale: es
+kiStatus: Backlog
+internalReference: 916461
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Lean Shipping no se desactiva automáticamente después de eliminar artículos del carrito, manteniendo sólo uno donde debería mostrar todas las opciones.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir 2 o más artículos de diferentes vendedores que tienen diferentes SLAs;
+- Lean shipping estará activo;
+- Eliminar todos los artículos, manteniendo sólo 1;
+- Lean shipping seguirá activo.
+
+
+
+## Workaround
+
+
+Actualice la página
+
+
+
+
diff --git a/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
new file mode 100644
index 000000000..d05743498
--- /dev/null
+++ b/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
@@ -0,0 +1,52 @@
+---
+title: 'El botón "eliminar" de la interfaz de usuario del catálogo heredado no funciona'
+id: 2soNSJfiQMZcxlpW6jT2FR
+status: PUBLISHED
+createdAt: 2022-01-23T02:51:17.884Z
+updatedAt: 2024-05-21T16:03:51.417Z
+publishedAt: 2024-05-21T16:03:51.417Z
+firstPublishedAt: 2024-05-21T16:03:51.417Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-boton-eliminar-de-la-interfaz-de-usuario-del-catalogo-heredado-no-funciona
+locale: es
+kiStatus: Backlog
+internalReference: 326408
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El botón para eliminar productos en el catálogo no funciona, simplemente no reconoce ningún clic del usuario
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ZR7ogOzhfLN3yC61V9RzTMRlZ/?name=inline-652081372.png)
+
+Esta acción puede funcionar si el producto se acaba de crear y no tiene asociados skus, imágenes o cualquier otro tipo de dato.
+
+
+##
+
+## Simulación
+
+
+- Vaya a la página principal del catálogo;
+- Intente eliminar un producto: no se ejecutará ninguna acción
+
+
+
+
+
+## Workaround
+
+
+No hay forma de borrar un solo producto, sólo la base completa. Para lograr el mismo resultado que una eliminación, intente reemplazar este producto con los datos que ya utilizaría para un nuevo producto de todos modos.
+
+
+
+
diff --git a/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md b/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md
new file mode 100644
index 000000000..c685fd21d
--- /dev/null
+++ b/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md
@@ -0,0 +1,57 @@
+---
+title: 'El elemento personalizado del banner del CMS heredado no funciona'
+id: 3ezW1BTc2nSvHpp0mAYhwh
+status: PUBLISHED
+createdAt: 2024-02-07T13:44:20.722Z
+updatedAt: 2024-02-07T13:44:21.554Z
+publishedAt: 2024-02-07T13:44:21.554Z
+firstPublishedAt: 2024-02-07T13:44:21.554Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-elemento-personalizado-del-banner-del-cms-heredado-no-funciona
+locale: es
+kiStatus: Backlog
+internalReference: 978466
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, la pestaña "elementos personalizados" de las configuraciones del CMS heredado no funciona correctamente.
+
+Configurar un elemento personalizado de este tipo no producirá efectos en la mayoría de los casos y se recomienda configurarlo directamente en el HTML del diseño.
+
+Esto sólo ocurre en las tiendas de plantillas heredadas.
+
+
+##
+
+## Simulación
+
+
+1 - vaya al CMS heredado y seleccione la pestaña de elementos personalizados
+2 - cargue un elemento personalizado de tipo "banner
+3 - haga referencia a este banner en su html
+4 - el banner configurado no se mostrará correctamente
+
+
+
+## Workaround
+
+
+configure los banners utilizando el tipo de diseño HTML y/o las subplantillas asociadas al mismo.
+
+O
+
+migrar al marco de la tienda VTEX
+
+
+
+
+
diff --git a/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md b/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
index 3a47502c5..0a2bf4c3e 100644
--- a/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
+++ b/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
@@ -3,8 +3,8 @@ title: 'El filtro de categorías de la interfaz de usuario de la colección here
 id: 1IlioZpOSQf5t4TWqZreiS
 status: PUBLISHED
 createdAt: 2022-10-31T20:42:26.100Z
-updatedAt: 2022-12-20T16:37:12.340Z
-publishedAt: 2022-12-20T16:37:12.340Z
+updatedAt: 2024-02-16T20:28:22.357Z
+publishedAt: 2024-02-16T20:28:22.357Z
 firstPublishedAt: 2022-10-31T20:42:26.591Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-filtro-de-categorias-de-la-interfaz-de-usuario-de-la-coleccion-heredada-selecciona-productos-erroneamente-en-la-coleccion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 590934
 ---
 
diff --git a/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md b/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
new file mode 100644
index 000000000..4111eb932
--- /dev/null
+++ b/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
@@ -0,0 +1,51 @@
+---
+title: 'Los controles heredados de plantillas de plazos y estanterías no tienen en cuenta los multiplicadores de unidades'
+id: 1E0Co7ssCUAKAgxCzlJoVn
+status: PUBLISHED
+createdAt: 2024-02-08T13:39:40.663Z
+updatedAt: 2024-02-08T13:48:30.740Z
+publishedAt: 2024-02-08T13:48:30.740Z
+firstPublishedAt: 2024-02-08T13:39:41.744Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: los-controles-heredados-de-plantillas-de-plazos-y-estanterias-no-tienen-en-cuenta-los-multiplicadores-de-unidades
+locale: es
+kiStatus: Backlog
+internalReference: 979205
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, para la tienda que utiliza el CMS heredado, la plantilla heredada y los controles de estantería no se ajustan si el SKU tiene un multiplicador de unidades.
+
+Por ejemplo, si tiene un artículo con un multiplicador de unidades de 2 y un controlador de plazos, los datos mostrados en las estanterías solo mostrarán las opciones de plazos de una sola unidad, en lugar de ajustarse a esta configuración.
+
+
+##
+
+## Simulación
+
+
+1 - crear una sku con un multiplicador de unidades
+2 - configure las opciones de instalación
+3 - configure un controlador relacionado con la cuota, como $product.InstallmentValue
+4 - los datos mostrados serán relativos a una sola unidad, solamente.
+
+
+
+## Workaround
+
+
+implementar una personalización front-end para sobrescribir los datos originales que se muestran.
+
+
+
+
+
diff --git a/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md b/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md
index 2644b690e..1c160fe3d 100644
--- a/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md
+++ b/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md
@@ -3,8 +3,8 @@ title: 'Los textos de los controladores de Let Me Know no se traducen'
 id: 4UXWf34IXNVAEKgH4hQLTx
 status: PUBLISHED
 createdAt: 2022-02-03T17:18:23.078Z
-updatedAt: 2022-12-02T18:35:11.786Z
-publishedAt: 2022-12-02T18:35:11.786Z
+updatedAt: 2024-02-16T20:26:19.991Z
+publishedAt: 2024-02-16T20:26:19.991Z
 firstPublishedAt: 2022-02-03T17:18:23.416Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: los-textos-de-los-controladores-de-let-me-know-no-se-traducen
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 517165
 ---
 
diff --git a/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md b/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
new file mode 100644
index 000000000..ff26a8300
--- /dev/null
+++ b/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
@@ -0,0 +1,51 @@
+---
+title: 'Vincular los valores de los servicios a la hoja de cálculo SKUS sólo devuelve los servicios activos'
+id: 1FqAokiJLWwWnsPodyTMKY
+status: PUBLISHED
+createdAt: 2023-08-23T17:51:58.839Z
+updatedAt: 2023-08-23T17:51:59.677Z
+publishedAt: 2023-08-23T17:51:59.677Z
+firstPublishedAt: 2023-08-23T17:51:59.677Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: vincular-los-valores-de-los-servicios-a-la-hoja-de-calculo-skus-solo-devuelve-los-servicios-activos
+locale: es
+kiStatus: Backlog
+internalReference: 886486
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al exportar valores de servicios de una categoría específica en el admin el resultado solo trae los servicios activos. No permitiendo al comerciante activar servicios previamente inactivos por hoja de cálculo.
+
+
+##
+
+## Simulación
+
+
+
+1. Crear un servicio y asociarlo a un sku;
+2. Desactivar el servicio en el sku;
+3. Exporte la hoja de cálculo ENLAZAR VALORES DE SERVICIO A SKU;
+4. 4. Compruebe que no se devuelve el servicio anterior.
+
+
+
+## Workaround
+
+
+Utilice la API o ir directamente en el sku - servicios de administración con el fin de actualizar el servicio:
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/skuservice/-skuServiceId-
+
+
+
+
+
diff --git a/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index 9461054fd..eb7923699 100644
--- a/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -3,8 +3,8 @@ title: 'El enlace "¿Por qué rellenar la Categoría Global VTEX?" en la configu
 id: 3u7aq2otUovQbO98lzjbus
 status: PUBLISHED
 createdAt: 2022-03-16T17:59:14.355Z
-updatedAt: 2022-12-20T16:36:51.563Z
-publishedAt: 2022-12-20T16:36:51.563Z
+updatedAt: 2024-02-16T20:23:34.672Z
+publishedAt: 2024-02-16T20:23:34.672Z
 firstPublishedAt: 2022-03-16T17:59:14.784Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-enlace-por-que-rellenar-la-categoria-global-vtex-en-la-configuracion-de-la-categoria-solo-funciona-abriendose-en-una-nueva-pestana
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 544034
 ---
 
diff --git a/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
new file mode 100644
index 000000000..c22542260
--- /dev/null
+++ b/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -0,0 +1,93 @@
+---
+title: 'linkId no se está registrando en rewriter cuando se traduce con graphql catálogo'
+id: 7b7KOHlxyIO4zKy2xrMuSD
+status: PUBLISHED
+createdAt: 2022-09-08T21:27:03.855Z
+updatedAt: 2024-07-10T12:47:32.306Z
+publishedAt: 2024-07-10T12:47:32.306Z
+firstPublishedAt: 2022-09-08T21:27:04.567Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: linkid-no-se-esta-registrando-en-rewriter-cuando-se-traduce-con-graphql-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 654951
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza el catálogo graphQL y se traduce la URL utilizando el linkId el rewriter debería almacenar el linkId, pero no está sucediendo: https://developers.vtex.com/docs/guides/catalog-internationalization
+
+
+##
+
+## Simulación
+
+
+
+- Sigue la guía de documentación para traducir el contenido del catálogo: https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization#mutation
+- **Para enlaces de categoría:**
+  - Comprueba el linkId que creaste en admin/graphql-ide y elige la aplicación de reescritura:
+
+    { internal{ get(ruta: "tuLinkdIdAquí"){ id } }}
+
+
+
+- Esto devolverá null;
+- Compruebe de nuevo con el nombre de su categoría traducida pero, slugified:
+
+    { internal{ get(ruta: "tuNombreCategoriaTraducidoSlugified"){ id } }}
+
+
+
+- Esto devolverá los resultados.
+
+
+
+- Para los enlaces de productos
+  - Acceda a la página del producto utilizando el enlace traducido creado mediante el graphQL del catálogo;
+  - Se mostrará un 404 No encontrado.
+
+
+
+## Workaround
+
+
+
+- Para enlaces de categoría
+  - Ejecute la siguiente consulta en rewriter:
+
+    { internal{ get(path: "yourTranslatedLinkdId"){ id from declarer type query binding origin resolveAs } }}
+
+
+
+- Guarde los valores devueltos, necesitará utilizarlos en el siguiente paso;
+- Ejecuta la siguiente mutación cambiando sólo el parámetro from, los demás deben ser iguales que los anteriores:
+
+    mutation saveInternal($ruta: InternalInput!) { internal { save(ruta: $ruta) { from declarador tipo id binding resolveAs origen } }}{ "ruta": { "from": "yourLinkId", "declarer": "tuDeclaradorGuardado", "tipo": "yourSavedType", "binding": "yourSavedBinding", "id": "yourSavedId", "origin": "yourSavedOrigin", "resolveAs": "yourSavedResolveAs" }}
+
+> Para más información sobre estos parámetros, puede consultar: https://developers.vtex.com/vtex-developer-docs/docs/rewriter
+
+
+
+- Ahora, vamos a borrar la ruta antigua (la guardada con el nombre)
+
+    mutation saveInternal($ruta: InternalInput!) { internal { delete(ruta: "tuTraducidoLinkdId") { id } }}
+
+
+
+- Para enlaces de productos:**
+  - Ejecute la siguiente mutación cambiando únicamente el parámetro from, los demás deben ser iguales que los anteriores:
+
+    mutación saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "ruta": { "origen": "/yourTranslatedLinkdId/p", "declarer": "vtex.store@2.x", "type": "product", "id": "productId", "resolveAs": "/yourOrinalLinkdId/p", "binding": "bindingId" }}
+
+
+
+
diff --git a/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md b/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md
index 3a1998870..de72abfed 100644
--- a/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md
+++ b/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md
@@ -3,8 +3,8 @@ title: 'Locale Switcher no funciona en el entorno myvtex'
 id: 1ZB56egPjPbTaUUnws5juK
 status: PUBLISHED
 createdAt: 2023-03-27T12:26:31.974Z
-updatedAt: 2023-03-27T14:55:12.486Z
-publishedAt: 2023-03-27T14:55:12.486Z
+updatedAt: 2024-02-02T21:03:39.535Z
+publishedAt: 2024-02-02T21:03:39.535Z
 firstPublishedAt: 2023-03-27T12:26:32.649Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md b/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md
new file mode 100644
index 000000000..1e2dc072e
--- /dev/null
+++ b/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md
@@ -0,0 +1,57 @@
+---
+title: 'La preferencia de inicio de sesión con contraseña no se puede deshacer en Admin.'
+id: 5OPVJusw14TQzKdAVS71wx
+status: PUBLISHED
+createdAt: 2024-04-22T13:30:15.401Z
+updatedAt: 2024-05-06T20:40:26.631Z
+publishedAt: 2024-05-06T20:40:26.631Z
+firstPublishedAt: 2024-04-22T13:30:16.436Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: la-preferencia-de-inicio-de-sesion-con-contrasena-no-se-puede-deshacer-en-admin
+locale: es
+kiStatus: Backlog
+internalReference: 1020548
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario se conecta a la plataforma VTEX por primera vez (Admin), se le pide que elija su preferencia de inicio de sesión para la próxima vez que se conecte. A continuación, puede elegir entre introducir su dirección de correo electrónico y contraseña, o introducir un código que se le enviará a su dirección de correo electrónico;
+
+Sin embargo, cuando el usuario elige introducir su dirección de correo electrónico y contraseña, no puede deshacer esta elección, ya que es una elección irrevocable a nivel de la interfaz de usuario, y se requiere una acción sistémica para deshacer esta elección.
+
+
+
+## Simulación
+
+
+**NOTA**: Para simular este escenario, debe iniciar sesión por primera vez;
+
+Iniciar sesión en admin
+
+Introduzca su dirección de correo electrónico y cree una contraseña;
+
+En este punto se le preguntará si desea seguir recibiendo el código de acceso o si desea que el sistema le pida siempre su dirección de correo electrónico y contraseña.
+
+Solicite que el sistema le pida siempre su dirección de correo electrónico y su contraseña.
+
+La próxima vez que se conecte, no podrá deshacer su elección de inicio de sesión y siempre se le pedirá su dirección de correo electrónico y contraseña.
+
+
+
+## Workaround
+
+
+Para que el usuario pueda realizar una nueva elección, es necesario solicitar al equipo de ingeniería que revoque la preferencia guardada en el perfil del usuario, de modo que en su próximo inicio de sesión se le vuelva a preguntar por su preferencia de inicio de sesión y pueda realizar una nueva elección.
+
+
+
+
+
diff --git a/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md b/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
index 1fc52caf3..de7271699 100644
--- a/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
+++ b/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
@@ -3,8 +3,8 @@ title: 'La simulación logística con el precio mínimo y máximo en la polític
 id: 5gsBLbPMIZjZvkl5QHudVY
 status: PUBLISHED
 createdAt: 2022-03-30T20:10:30.205Z
-updatedAt: 2022-11-25T21:59:57.297Z
-publishedAt: 2022-11-25T21:59:57.297Z
+updatedAt: 2024-02-16T20:26:15.370Z
+publishedAt: 2024-02-16T20:26:15.370Z
 firstPublishedAt: 2022-05-17T14:23:38.006Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: la-simulacion-logistica-con-el-precio-minimo-y-maximo-en-la-politica-de-envio-no-funciona-cuando-productprice-es-0-cero
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 553080
 ---
 
diff --git a/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md b/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
index 3d1aa1033..afc967f4e 100644
--- a/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
+++ b/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
@@ -3,8 +3,8 @@ title: 'Bucle en la ventana emergente de autenticación cuando la primera condic
 id: 7fU6wnrTjS0aJqRmertSFg
 status: PUBLISHED
 createdAt: 2023-06-14T17:54:36.973Z
-updatedAt: 2023-06-14T17:55:47.281Z
-publishedAt: 2023-06-14T17:55:47.281Z
+updatedAt: 2023-12-21T15:50:16.992Z
+publishedAt: 2023-12-21T15:50:16.992Z
 firstPublishedAt: 2023-06-14T17:54:37.537Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md b/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
index 170ce5d8c..b0dbc2c3a 100644
--- a/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
+++ b/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
@@ -3,8 +3,8 @@ title: '[Magalu] Sku que se integra con las especificaciones de otro marketplace
 id: 4AYsfMTB2HVmp2PnOG2plY
 status: PUBLISHED
 createdAt: 2022-10-31T19:29:16.911Z
-updatedAt: 2022-12-02T18:30:12.315Z
-publishedAt: 2022-12-02T18:30:12.315Z
+updatedAt: 2024-03-19T20:33:58.929Z
+publishedAt: 2024-03-19T20:33:58.929Z
 firstPublishedAt: 2022-10-31T19:29:18.080Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: magalu-sku-que-se-integra-con-las-especificaciones-de-otro-marketplace
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 689151
 ---
 
diff --git a/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md b/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
new file mode 100644
index 000000000..b92ae7796
--- /dev/null
+++ b/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
@@ -0,0 +1,50 @@
+---
+title: '[Magazine Luiza] Pedido cancelado en marketplace no actualiza estado en VTEX'
+id: 4C1G20Iwj6x1mvqzsSDU0P
+status: PUBLISHED
+createdAt: 2023-07-20T15:33:25.631Z
+updatedAt: 2023-07-20T15:33:26.222Z
+publishedAt: 2023-07-20T15:33:26.222Z
+firstPublishedAt: 2023-07-20T15:33:26.222Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: magazine-luiza-pedido-cancelado-en-marketplace-no-actualiza-estado-en-vtex
+locale: es
+kiStatus: Backlog
+internalReference: 865926
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Orden cancelada en marketplace no actualiza estado en VTEX
+
+**Mercado:Revista Luiza
+**Causa principal:** Integración del pedido
+**Tipo:** Estado no actualizado en marketplace
+**Impacto:** Pocos pedidos
+
+
+##
+
+## Simulación
+
+
+No se han encontrado errores en los logs, pero el pedido en OMS/VTEX está `Facturado` pero en el marketplace el pedido está como `cancelado`.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md b/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md
new file mode 100644
index 000000000..3abf82aeb
--- /dev/null
+++ b/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md
@@ -0,0 +1,56 @@
+---
+title: '[Magazine Luiza] Algunos skus no actualizan el precio'
+id: NXb7Bb4BTJepPphcK9z0V
+status: PUBLISHED
+createdAt: 2023-08-17T14:14:36.434Z
+updatedAt: 2023-08-17T14:14:37.098Z
+publishedAt: 2023-08-17T14:14:37.098Z
+firstPublishedAt: 2023-08-17T14:14:37.098Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: magazine-luiza-algunos-skus-no-actualizan-el-precio
+locale: es
+kiStatus: Backlog
+internalReference: 882919
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Necesitamos entender por qué algunos skus no actualizan el precio en el marketplace.
+Importante: no ocurre con todos los skus
+
+
+##
+
+## Simulación
+
+
+Flujo: Precio actualizado en el catálogo VTEX
+
+emisora
+recibe notificación de cambio de precio
+
+Integración
+notificación recibida de modificación de precios
+
+mercado
+El precio no se ha actualizado y no se han encontrado errores en el registro
+
+
+
+## Workaround
+
+
+Reindexar sku en catálogo VTEX
+
+
+
+
+
diff --git a/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md b/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
new file mode 100644
index 000000000..cf1042f68
--- /dev/null
+++ b/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
@@ -0,0 +1,53 @@
+---
+title: "[Magazine Luiza] [tracking] Error: 'Customer Delivery Date' debe ser mayor que 'Delivery Date' y debe ser igual o menor que la fecha de hoy"
+id: 7ublDwKHM4JJxsCtcbLqq8
+status: PUBLISHED
+createdAt: 2023-07-06T14:06:45.020Z
+updatedAt: 2023-07-06T14:06:45.783Z
+publishedAt: 2023-07-06T14:06:45.783Z
+firstPublishedAt: 2023-07-06T14:06:45.783Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: magazine-luiza-tracking-error-customer-delivery-date-debe-ser-mayor-que-delivery-date-y-debe-ser-igual-o-menor-que-la-fecha-de-hoy
+locale: es
+kiStatus: Backlog
+internalReference: 856984
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el paso de seguimiento algunos pedidos están devolviendo el siguiente error `"Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"`
+
+**Mercado:** Revista Luiza
+**Estado:** Seguimiento
+**Impacto:** Algunos Pedidos
+
+
+##
+
+## Simulación
+
+
+1. Integraciones
+2. Puente
+3. Seguimiento
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/mlpzu59MIDWuvUP6n8zJc8GI6/?name=image.png)
+
+
+
+## Workaround
+
+
+Normalmente reprocesar manualmente la petición desde el puente soluciona el error.
+
+
+
+
diff --git a/docs/known-issues/es/mandatory-service-working-as-optional.md b/docs/known-issues/es/mandatory-service-working-as-optional.md
new file mode 100644
index 000000000..b59c55aa9
--- /dev/null
+++ b/docs/known-issues/es/mandatory-service-working-as-optional.md
@@ -0,0 +1,49 @@
+---
+title: 'Servicio obligatorio que funciona como opcional'
+id: 6bcdioCSYL7ZGoOy0nEtJC
+status: PUBLISHED
+createdAt: 2023-08-01T15:15:29.008Z
+updatedAt: 2023-08-01T15:15:30.099Z
+publishedAt: 2023-08-01T15:15:30.099Z
+firstPublishedAt: 2023-08-01T15:15:30.099Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: servicio-obligatorio-que-funciona-como-opcional
+locale: es
+kiStatus: Backlog
+internalReference: 872411
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al crear un servicio el comerciante puede elegir si va a ser un campo obligatorio en el pago o no.
+Sin embargo, actualmente esta funcionalidad no funciona como se esperaba. Incluso cuando el campo obligatorio está marcado como verdadero, el producto se puede comprar sin añadirlo en la caja.
+
+
+
+## Simulación
+
+
+
+1. Crear un servicio como obligatorio;
+2. Asociar a un sku;
+3. Comprobar que en el checkout el servicio se puede añadir o eliminar sin problemas.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md b/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
new file mode 100644
index 000000000..9b2d7f0f6
--- /dev/null
+++ b/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
@@ -0,0 +1,47 @@
+---
+title: 'marketingData no se guarda en los pedidos cuando se utiliza la función de cupones múltiples y utms'
+id: OUMc8x9sEcdp8ZbLIka4b
+status: PUBLISHED
+createdAt: 2023-11-22T21:53:36.924Z
+updatedAt: 2024-04-09T13:33:02.091Z
+publishedAt: 2024-04-09T13:33:02.091Z
+firstPublishedAt: 2023-11-22T21:53:37.493Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketingdata-no-se-guarda-en-los-pedidos-cuando-se-utiliza-la-funcion-de-cupones-multiples-y-utms
+locale: es
+kiStatus: Fixed
+internalReference: 936458
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza la función de cupones múltiples y hay cupones y utms, o 'marketingTags', en el 'orderForm', no se guarda ningún 'marketingData' en el pedido.
+
+
+
+## Simulación
+
+
+
+- Tiene una cuenta que utiliza la función de cupones múltiples;
+- Utilice un cupón y establezca cualquier utm o 'marketingTags', ambos deben estar en el orderForm;
+- Finalice la compra; no habrá ningún 'marketingData' en el pedido.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md b/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md
new file mode 100644
index 000000000..f12be8177
--- /dev/null
+++ b/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md
@@ -0,0 +1,49 @@
+---
+title: 'marketingTags con valor nulo cuando coincide el público de la campaña'
+id: 17pTWB1gLNJgFy7KEZd8pk
+status: PUBLISHED
+createdAt: 2024-06-19T20:08:49.413Z
+updatedAt: 2024-06-19T20:08:50.452Z
+publishedAt: 2024-06-19T20:08:50.452Z
+firstPublishedAt: 2024-06-19T20:08:50.452Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketingtags-con-valor-nulo-cuando-coincide-el-publico-de-la-campana
+locale: es
+kiStatus: Backlog
+internalReference: 1052895
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una cuenta tiene un público de campaña y se hace coincidir con un usuario logueado, el checkout utiliza la información registrada en la sesión, que sólo tiene el id de la campaña. En `marketingTags`, debería tener el nombre de la campaña, pero es `null` ya que no hay información disponible en la sesión.
+
+
+##
+
+## Simulación
+
+
+
+- Crear un público para la campaña;
+- Inicie sesión con un usuario con el que coincida la campaña;
+- Comprueba el campo `marketingData.marketingTags` en el orderForm, tendrá un valor nulo y el nombre de la campaña.
+ ![](https://vtexhelp.zendesk.com/attachments/token/1i6d9cIyg1Hx2fs9QsVZ6BFCY/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md b/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
new file mode 100644
index 000000000..b3a4b17ae
--- /dev/null
+++ b/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
@@ -0,0 +1,52 @@
+---
+title: 'Marketplace y Fulfillment pueden esperar valores de pedido diferentes debido a ciertas condiciones de compra'
+id: 5LoC3DwesBWH5kr2b5u6WD
+status: PUBLISHED
+createdAt: 2024-05-13T20:04:19.094Z
+updatedAt: 2024-05-13T20:34:01.432Z
+publishedAt: 2024-05-13T20:34:01.432Z
+firstPublishedAt: 2024-05-13T20:04:20.144Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketplace-y-fulfillment-pueden-esperar-valores-de-pedido-diferentes-debido-a-ciertas-condiciones-de-compra
+locale: es
+kiStatus: Backlog
+internalReference: 1032473
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las capas de Marketplace y Fulfillment pueden esperar valores diferentes para el pedido, impidiendo la finalización de la compra.
+En estos casos, el "precio de venta" del artículo en el mercado no coincide con el "precio" de cumplimiento.
+
+
+##
+
+## Simulación
+
+
+El problema no se limita necesariamente a este paso exacto, pero es más fácil de reproducir de la siguiente manera:
+
+1. Pon a cero los decimales del Mercado y del vendedor.
+2. En la cuenta del vendedor, fije el precio de un artículo en 49950,00, y una promoción de Cumplimiento que le aplique un descuento del 15%.
+3. En un Marketplace, añade 3 unidades del artículo del vendedor a tu cesta.
+4. 4. Intenta completar la compra. Aparecerá el mensaje de error "No se ha podido crear el pedido solicitado. Por favor, inténtelo de nuevo".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
new file mode 100644
index 000000000..116085e9b
--- /dev/null
+++ b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
@@ -0,0 +1,48 @@
+---
+title: 'La solicitud del centro tributario del mercado no tiene en cuenta el precio manual para los descuentos'
+id: 2pGgbPB7Qm4dXtQauohvx7
+status: PUBLISHED
+createdAt: 2023-11-08T17:59:41.102Z
+updatedAt: 2023-12-06T19:27:50.006Z
+publishedAt: 2023-12-06T19:27:50.006Z
+firstPublishedAt: 2023-11-08T17:59:41.695Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-solicitud-del-centro-tributario-del-mercado-no-tiene-en-cuenta-el-precio-manual-para-los-descuentos
+locale: es
+kiStatus: Fixed
+internalReference: 932657
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la cuenta tiene configurado isMarketplaceResponsibleForTaxes, la solicitud del centro de impuestos no tiene en cuenta los precios manuales para los descuentos de artículos.
+
+
+##
+
+## Simulación
+
+
+
+- Configure taxConfiguration.isMarketplaceResponsibleForTaxes en la configuración de orderForm;
+- Establecer el precio manual de un artículo;
+- La solicitud del centro de impuestos no aplicará la diferencia como descuento.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
new file mode 100644
index 000000000..7280d4fa6
--- /dev/null
+++ b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
@@ -0,0 +1,48 @@
+---
+title: 'La solicitud del centro tributario del mercado no tiene en cuenta algunos tipos de descuentos'
+id: 630nSPu8y5G6CSFtiH3MOL
+status: PUBLISHED
+createdAt: 2023-11-30T21:14:13.709Z
+updatedAt: 2023-12-06T19:27:05.930Z
+publishedAt: 2023-12-06T19:27:05.930Z
+firstPublishedAt: 2023-11-30T21:14:14.259Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-solicitud-del-centro-tributario-del-mercado-no-tiene-en-cuenta-algunos-tipos-de-descuentos
+locale: es
+kiStatus: Fixed
+internalReference: 945580
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la cuenta tiene configurado isMarketplaceResponsibleForTaxes, la solicitud del hub de impuestos no considera algunos tipos de descuento: Nominal, Porcentaje y Precio máximo por artículo. Esto afecta al cálculo de impuestos, y el precio final es más alto de lo esperado.
+
+
+##
+
+## Simulación
+
+
+
+- Configure taxConfiguration.isMarketplaceResponsibleForTaxes en la configuración de orderForm;
+- Configure uno de los tipos de descuento Nominal, Porcentaje o Precio máximo por artículo de la promoción regular;
+- La solicitud del centro de impuestos no aplicará el descuento.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md b/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md
new file mode 100644
index 000000000..1079a0b20
--- /dev/null
+++ b/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md
@@ -0,0 +1,45 @@
+---
+title: 'Las transacciones con tarjeta de crédito Mastercard se procesan como Visa'
+id: 4B547KIrO7xBUWdCUhPkjs
+status: PUBLISHED
+createdAt: 2024-05-02T19:12:19.672Z
+updatedAt: 2024-05-02T19:12:20.545Z
+publishedAt: 2024-05-02T19:12:20.545Z
+firstPublishedAt: 2024-05-02T19:12:20.545Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: las-transacciones-con-tarjeta-de-credito-mastercard-se-procesan-como-visa
+locale: es
+kiStatus: Backlog
+internalReference: 1026263
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas transacciones se están registrando erróneamente bajo la marca Visa, cuando en realidad las tarjetas son Mastercard. Este problema se produce específicamente con tarjetas nuevas, aunque podemos verificar que el BIN de la tarjeta coincide correctamente con el regex del validador para la marca correcta.
+
+
+
+## Simulación
+
+
+No hemos podido reproducir este problema.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/masterdata-export-download-link-unavailable.md b/docs/known-issues/es/masterdata-export-download-link-unavailable.md
index 07a1a625d..99dbb45f5 100644
--- a/docs/known-issues/es/masterdata-export-download-link-unavailable.md
+++ b/docs/known-issues/es/masterdata-export-download-link-unavailable.md
@@ -3,8 +3,8 @@ title: 'Masterdata Export Enlace de descarga no disponible'
 id: 2oi0ABhQQxfPsKETeNUyvE
 status: PUBLISHED
 createdAt: 2022-07-08T13:50:43.220Z
-updatedAt: 2023-01-19T14:19:49.870Z
-publishedAt: 2023-01-19T14:19:49.870Z
+updatedAt: 2023-07-28T17:14:13.207Z
+publishedAt: 2023-07-28T17:14:13.207Z
 firstPublishedAt: 2022-07-08T13:50:43.638Z
 contentType: knownIssue
 productTeam: Storage
@@ -32,8 +32,16 @@ Actualmente, para las entidades de datos con varios campos, cuando se intenta ex
 ## Simulación
 
 
+1 - para una entidad de datos en la que tiene varios campos, intente exportar todos sus campos al mismo tiempo o varios registros
+
+2 - el enlace de descarga no generará un archivo en su navegador
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/nQdUqbk7BiOK5RcigZhNZR9Rr/?name=image.png)
+
+
 
 ## Workaround
 
 
+**Haga clic con el botón derecho del ratón en el enlace de descarga y copie el enlace; a continuación, péguelo en otra pestaña y se iniciará la descarga o bien obtenga los datos a través de la API https://developers.vtex.com/docs/api-reference/masterdata-api#get-/api/dataentities/-acronym-/search y/o descargue los datos en varias hojas de cálculo más pequeñas.
 
diff --git a/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
new file mode 100644
index 000000000..8f08ca096
--- /dev/null
+++ b/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -0,0 +1,55 @@
+---
+title: 'La API recibe varios SKU y devuelve "Invalid sellerId".'
+id: 60aL2Chds0Jo3m6XMkxmnG
+status: PUBLISHED
+createdAt: 2023-10-17T16:26:27.980Z
+updatedAt: 2023-10-17T16:26:40.592Z
+publishedAt: 2023-10-17T16:26:40.592Z
+firstPublishedAt: 2023-10-17T16:26:28.466Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: la-api-recibe-varios-sku-y-devuelve-invalid-sellerid
+locale: es
+kiStatus: Fixed
+internalReference: 506660
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La API Match Multiple Received SKUs (doc: https://developers.vtex.com/vtex-rest-api/reference/match-received-skus#matchmultiple) está devolviendo el mensaje de error "Invalid sellerId" para cualquier intento de aprobación de nuevos productos, incluso si el vendedor está correctamente activo en el marketplace.
+
+
+##
+
+## Simulación
+
+
+1. Copia el curl de la documentación anterior;
+2. Pégalo en tu herramienta API (postman, insomnia...);
+3. Sustituye los valores del objeto por los datos del sku que intentas aprobar;
+4. Comprueba si el sellerId está activo y es válido en la gestión de vendedores del marketplace;
+5. La respuesta de la API no debe ser:
+
+    "errorResponse": { "Code": 33, "Message": "Invalid sellerId" }
+
+
+
+
+
+## Workaround
+
+
+La API Match Received SKUs individually funciona correctamente y puede sustituir a la API anterior para aprobar nuevos productos uno a uno.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md b/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md
new file mode 100644
index 000000000..662845a7e
--- /dev/null
+++ b/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md
@@ -0,0 +1,52 @@
+---
+title: 'Igualador que convierte Altura, Anchura, Peso y Longitud a 0,1'
+id: j3rz875eWVHFMLYxcYsDL
+status: PUBLISHED
+createdAt: 2023-08-23T13:38:55.976Z
+updatedAt: 2023-08-23T20:01:37.842Z
+publishedAt: 2023-08-23T20:01:37.842Z
+firstPublishedAt: 2023-08-23T13:38:58.327Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: igualador-que-convierte-altura-anchura-peso-y-longitud-a-01
+locale: es
+kiStatus: Fixed
+internalReference: 886168
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el Matcher procesa los skus en el módulo de sugerencias del marketplace las infos de Altura, Anchura, Peso y Longitud se están poniendo a 0.1 en lugar de respetar los valores enviados por el vendedor.
+
+
+##
+
+## Simulación
+
+
+
+1. El vendedor envía el sku a marketplace con Altura, Anchura, Peso y Longitud con valores normales;
+2. El sku llega al marketplace y es procesado por el matcher;
+3. Compruebe en la siguiente API si el objeto Matcher tiene los campos Height, Width, Weight y Length configurados como 0.1
+https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/-sellerId-/-sellerSkuId-
+ ![](https://vtexhelp.zendesk.com/attachments/token/vCdMBFKEJ0243C9Ew7PPFDgp3/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md b/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
new file mode 100644
index 000000000..9585a5717
--- /dev/null
+++ b/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
@@ -0,0 +1,49 @@
+---
+title: 'El comparador no funciona como se espera cuando el nombre del Producto/SKU contiene caracteres especiales'
+id: 1kRjFExdSRMAJMgFgC7Bbj
+status: PUBLISHED
+createdAt: 2023-10-19T15:37:17.652Z
+updatedAt: 2023-10-19T15:37:18.601Z
+publishedAt: 2023-10-19T15:37:18.601Z
+firstPublishedAt: 2023-10-19T15:37:18.601Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: el-comparador-no-funciona-como-se-espera-cuando-el-nombre-del-productosku-contiene-caracteres-especiales
+locale: es
+kiStatus: Fixed
+internalReference: 736164
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al integrar productos que tienen caracteres especiales en el nombre, como `. - + # /` , Matcher da una puntuación del 50% y hace que los productos se queden en Pendiente. Con esto, los productos dependen de la aprobación manual o vía API.
+
+
+
+##
+
+## Simulación
+
+
+
+1. A través de un vendedor VTEX, envía una SKU que contiene caracteres especiales en el nombre
+2. En la página SKU Recibida, observa que la SKU en cuestión tendrá una puntuación del 50%, en la pestaña Pendiente
+
+
+
+## Workaround
+
+
+Para resolver el escenario se indica que el vendedor cambie el SKU/nombre del producto, eliminando los caracteres especiales. Si esto no es posible, el marketplace puede utilizar la API https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/api.vtex.com/-accountName-/suggestions/matches/action/-actionName- para hacer coincidir los productos
+
+
+
+
+
diff --git a/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md b/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md
new file mode 100644
index 000000000..976545fc2
--- /dev/null
+++ b/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md
@@ -0,0 +1,50 @@
+---
+title: 'Max Shipping Discount no actualiza priceTags'
+id: uA0KFnyIOHq3ikcaZmYGr
+status: PUBLISHED
+createdAt: 2023-09-20T17:54:59.620Z
+updatedAt: 2023-10-02T18:20:48.375Z
+publishedAt: 2023-10-02T18:20:48.375Z
+firstPublishedAt: 2023-09-20T17:55:00.609Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: max-shipping-discount-no-actualiza-pricetags
+locale: es
+kiStatus: Backlog
+internalReference: 904190
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+##
+Descuento máximo de envío no devuelve etiquetas de precio, cuando el vendedor intenta calcular el impuesto, el chk no tiene el valor a considerar y considerar el descuento en el valor final del impuesto.
+
+
+
+##
+
+## Simulación
+
+
+Crear un descuento máximo de envío y un impuesto
+simule un carrito con ambos, verá que la etiqueta de precio no se rellena.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
new file mode 100644
index 000000000..23bf232e3
--- /dev/null
+++ b/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -0,0 +1,70 @@
+---
+title: '"número máximo de artículos elegibles para cada cesta" + más por menos aplica un descuento incorrecto al utilizar el mismo artículo.'
+id: gWIMhi9RCv9BE1RvV6GiM
+status: PUBLISHED
+createdAt: 2024-07-30T17:14:36.972Z
+updatedAt: 2024-07-30T17:14:37.931Z
+publishedAt: 2024-07-30T17:14:37.931Z
+firstPublishedAt: 2024-07-30T17:14:37.931Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: numero-maximo-de-articulos-elegibles-para-cada-cesta-mas-por-menos-aplica-un-descuento-incorrecto-al-utilizar-el-mismo-articulo
+locale: es
+kiStatus: Backlog
+internalReference: 1073080
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar un descuento de más por menos junto con otra promoción que utiliza el "máximo de artículos por carrito" para el mismo artículo, acumulándose ambos, se produce un descuento incorrecto, superando la configuración inicialmente configurada.
+
+Esto ocurre debido a la forma en que la caja divide los artículos.
+
+Por ejemplo, supongamos que tiene una promoción "más por menos" (A) configurada para dar un "100% de descuento para 1 artículo de cada 8 insertados en el carrito".
+
+Junto a ella, tiene otra promoción (B) que, para este mismo SKU, da un 50% de descuento, limitado a un máximo de 2 artículos.
+
+**Lo que se espera**:
+
+Si se introducen 80 artículos en la caja, deberían regalarse un total de 11 artículos.  10 procedentes de (A), 1 procedente de (B).
+
+**Lo que ocurre en la práctica**:
+
+Los artículos se dividen en 3 cantidades diferentes en la caja
+
+(1) los que sólo han obtenido el descuento (A)
+(2) los que sólo tienen descuento (B)
+(3) los que obtuvieron ambos descuentos (AB)
+
+Sin embargo, la línea (2), que debería tener sólo 2 artículos con un descuento del 50%, en realidad reproduce el descuento del 100% de la línea (1), con lo que se obtienen 2 artículos más de descuento, en un total de 13 artículos, en lugar de 11.
+
+
+
+
+
+## Simulación
+
+
+Cree un escenario de promoción como el descrito anteriormente o similar, utilizando el "número máximo de artículos elegibles para cada carrito" y una promoción de más por menos, ambos configurados para acumular.
+
+Es importante tener en cuenta que este problema solo se produce cuando **todas las promociones están configuradas para el mismo SKU**.
+
+
+
+## Workaround
+
+
+n/a (evite utilizar estos 2 ajustes específicos a la vez cuando opere con descuentos para el mismo SKU).
+
+
+
+
+
+
diff --git a/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md b/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
new file mode 100644
index 000000000..65a1e8fbd
--- /dev/null
+++ b/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
@@ -0,0 +1,48 @@
+---
+title: 'La configuración de la cantidad máxima del mismo artículo en el carro no puede ser modificada por las cuentas de franquicia'
+id: 5NqcSpcmPXEJE4KIkp6eZE
+status: PUBLISHED
+createdAt: 2022-05-12T14:52:33.074Z
+updatedAt: 2023-10-18T14:34:56.570Z
+publishedAt: 2023-10-18T14:34:56.570Z
+firstPublishedAt: 2022-05-12T14:52:33.334Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-configuracion-de-la-cantidad-maxima-del-mismo-articulo-en-el-carro-no-puede-ser-modificada-por-las-cuentas-de-franquicia
+locale: es
+kiStatus: Backlog
+internalReference: 325273
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La configuración de la cantidad máxima de un mismo artículo en el carrito no puede ser modificada por las cuentas franquiciadas (vendedor whitelabel), ya que tiene lugar en una pantalla heredada del catálogo (/admin/Site/ConfigForm.aspx) - módulo que se elimina de las cuentas franquiciadas, ya que heredan los productos de la cuenta padre.
+
+
+##
+
+## Simulación
+
+
+
+- Entrar en un entorno de cuenta de franquicia o vendedor de marca blanca
+- Acceda a la pantalla "CMS > Configuración > pestaña General" desde el admin, o vaya directamente a la página /admin/Site/ConfigForm.aspx
+- Tenga en cuenta que no es posible acceder al contenido de esta área
+
+
+
+## Workaround
+
+
+Solicite la configuración vía ticket a VTEX.
+
+
+
+
diff --git a/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
new file mode 100644
index 000000000..f8db2cf34
--- /dev/null
+++ b/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -0,0 +1,34 @@
+---
+title: 'MDv2 devuelve el error "504 Gateway Timeout" cuando intentamos actualizar un documento pasando un símbolo o carácter especial.'
+id: 6GP5QBWyIAir2oKe08giT2
+status: PUBLISHED
+createdAt: 2023-08-09T13:04:34.819Z
+updatedAt: 2023-08-09T13:04:35.446Z
+publishedAt: 2023-08-09T13:04:35.446Z
+firstPublishedAt: 2023-08-09T13:04:35.446Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: mdv2-devuelve-el-error-504-gateway-timeout-cuando-intentamos-actualizar-un-documento-pasando-un-simbolo-o-caracter-especial
+locale: es
+kiStatus: Backlog
+internalReference: 852966
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md b/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
new file mode 100644
index 000000000..f135c33d8
--- /dev/null
+++ b/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
@@ -0,0 +1,52 @@
+---
+title: '[MELI] El atributo se envía a MELI sin que el vendedor lo asigne.'
+id: CILYWlvEAlXkcvEYuZ99m
+status: PUBLISHED
+createdAt: 2023-10-30T10:09:31.578Z
+updatedAt: 2023-11-30T11:05:05.907Z
+publishedAt: 2023-11-30T11:05:05.907Z
+firstPublishedAt: 2023-10-30T10:09:32.150Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-el-atributo-se-envia-a-meli-sin-que-el-vendedor-lo-asigne
+locale: es
+kiStatus: Fixed
+internalReference: 791380
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema que todavía necesita más investigación y detalles, Pero hay algunas categorías mapeadas dentro de la característica Mapper, y para algunos atributos que no fueron mapeados pero que actualmente están siendo enviados a MELI.
+
+Esto resultará en que algunos SKUs serán exportados y otros no ya que el primer SKU incluye un atributo no deseado, y el segundo SKU no será exportado ya que MELI tiene reglas que requieren que todas las variantes dentro del mismo producto deben tener las mismas combinaciones de atributos.
+
+
+
+## Simulación
+
+
+
+Dentro del menú de productos puente, verá un error para algunos SKUs como se ve a continuación:
+**No se permiten variaciones con diferentes combinaciones de atributos.**
+
+Esto se debe a que el primer SKU exportado tiene un atributo no deseado, y el resto de SKUs no están siendo enviados a ese atributo.
+
+
+
+## Workaround
+
+
+¿Existe alguna solución para este error? En caso afirmativo, descríbala aquí. En caso negativo, escriba "N/A" o "No hay solución disponible". No elimine esta sección si no hay solución, por favor.
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md b/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
index 2bd65b2c2..08856a5d9 100644
--- a/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
+++ b/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
@@ -3,8 +3,8 @@ title: '[Meli] Atributos Negro_#000000 integración con un comportamiento no esp
 id: 1GPrObE1SQPP4ScyNHyjDt
 status: PUBLISHED
 createdAt: 2022-09-19T14:04:56.594Z
-updatedAt: 2022-11-25T21:55:27.032Z
-publishedAt: 2022-11-25T21:55:27.032Z
+updatedAt: 2024-02-16T20:28:12.568Z
+publishedAt: 2024-02-16T20:28:12.568Z
 firstPublishedAt: 2022-09-19T14:04:57.386Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: meli-atributos-negro000000-integracion-con-un-comportamiento-no-esperado
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 660703
 ---
 
diff --git a/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md b/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md
index dba94ff06..4adbcd7fb 100644
--- a/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md
+++ b/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md
@@ -3,8 +3,8 @@ title: 'Mensajes automáticos MELI Mercado Livre - Mensajes'
 id: 6WZy5RNesYJtJOaBAFnbkW
 status: PUBLISHED
 createdAt: 2023-05-04T11:22:21.762Z
-updatedAt: 2023-05-08T18:33:14.421Z
-publishedAt: 2023-05-08T18:33:14.421Z
+updatedAt: 2024-01-30T10:48:09.504Z
+publishedAt: 2024-01-30T10:48:09.504Z
 firstPublishedAt: 2023-05-04T11:22:22.366Z
 contentType: knownIssue
 productTeam: Connections
@@ -24,7 +24,7 @@ internalReference: 615164
 
 
 
-Actualmente nuestra APP MELI para enviar mensajes automáticos a MELI está teniendo algunos problemas con el modo logístico ME2.
+Actualmente nuestra APP MELI para enviar mensajes automáticos a MELI está teniendo algunos problemas al utilizar los mensajes de plantilla.
 
 
 ##
@@ -33,7 +33,7 @@ Actualmente nuestra APP MELI para enviar mensajes automáticos a MELI está teni
 
 
 
-Los mensajes automáticos en VTEX admin para el modo logístico ME2, no serán enviados al vendedor.
+Los mensajes automáticos en VTEX admin a veces no se envían a MELI..
 
 
 
diff --git a/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md b/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md
new file mode 100644
index 000000000..b81604d00
--- /dev/null
+++ b/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md
@@ -0,0 +1,48 @@
+---
+title: 'El menú MELI Bridge Orders no muestra la información del OrderID'
+id: ZBc9ny043rVpYFqkZIQ1K
+status: PUBLISHED
+createdAt: 2023-08-16T10:46:52.015Z
+updatedAt: 2023-10-05T18:51:13.700Z
+publishedAt: 2023-10-05T18:51:13.700Z
+firstPublishedAt: 2023-08-16T10:46:53.089Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: el-menu-meli-bridge-orders-no-muestra-la-informacion-del-orderid
+locale: es
+kiStatus: Fixed
+internalReference: 881733
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema que solo afecta a la visibilidad de algunos Pedidos MELI, lo que ocurre es que actualmente estamos registrando el ShipmentID en el menu del puente de pedidos, pero en algunos mensajes de error falta el OrderID, y es necesario para algunos casos ya que el orderID es la informacion que los vendedores tienen en el Portal MELI
+
+
+##
+
+## Simulación
+
+
+
+Dentro del menú de pedidos puente, algunos mensajes de error no están registrando el OrderID, lo que da la impresión de que algunos pedidos no están en el brige VTEX, pero los vendedores pueden encontrar los pedidos buscando el shipmentID.
+
+
+
+## Workaround
+
+
+Buscar el shipmentID en lugar del orderID
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md b/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
new file mode 100644
index 000000000..db4f8bc68
--- /dev/null
+++ b/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
@@ -0,0 +1,48 @@
+---
+title: 'Las AD de MELI Buybox no se pausan cuando se pausa la AD del mercado'
+id: 5OFALDi7lY93D7KkZ4scvg
+status: PUBLISHED
+createdAt: 2023-09-29T19:12:14.424Z
+updatedAt: 2023-10-09T20:52:25.672Z
+publishedAt: 2023-10-09T20:52:25.672Z
+firstPublishedAt: 2023-09-29T19:12:15.051Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: las-ad-de-meli-buybox-no-se-pausan-cuando-se-pausa-la-ad-del-mercado
+locale: es
+kiStatus: Fixed
+internalReference: 910371
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema con Buybox MELI flujo, que es cuando se quita el SKU de SC, por ejemplo, el mercado AD está en pausa en MELi, pero el Buybox AD permanece activo.
+
+
+##
+
+## Simulación
+
+
+
+Cuando el mercado AD está en pausa en MELI, por la razón de ser removido de VTEX SC por ejemplo, el Buybox AD necesitaría estar en pausa también.
+
+
+
+## Workaround
+
+
+¿Existe alguna solución para este error? En caso afirmativo, descríbala aquí. En caso negativo, escriba "N/A" o "No hay solución disponible". No elimine esta sección si no hay solución, por favor.
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md b/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md
index 9627d17bf..d640b558b 100644
--- a/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md
+++ b/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md
@@ -3,8 +3,8 @@ title: 'Error MELI al enviar el seguimiento del pedido'
 id: 4wdzb5xjelAkFnbuRCFXAt
 status: PUBLISHED
 createdAt: 2023-03-06T10:06:58.255Z
-updatedAt: 2023-03-06T10:06:59.162Z
-publishedAt: 2023-03-06T10:06:59.162Z
+updatedAt: 2023-10-20T17:28:38.314Z
+publishedAt: 2023-10-20T17:28:38.314Z
 firstPublishedAt: 2023-03-06T10:06:59.162Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: error-meli-al-enviar-el-seguimiento-del-pedido
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 764885
 ---
 
@@ -35,7 +35,19 @@ Es importante señalar que esto no está afectando el flujo como el seguimiento
 
 
 
+Dentro del menú Bridge - Tracking se mostrará un mensaje de error como el siguiente.
+
+"Mensagem de erro não mapeada pela integração. Póngase en contacto con VTEX para informarle de lo ocurrido y realizar la reparación.
+Mensaje de error Mercado Libre:"
+
+
+
 ## Workaround
 
 
 
+No se requiere ninguna acción, es importante tener en cuenta que a pesar de que el mensaje de error se muestra esto no está afectando el flujo de seguimiento, el XML se envía a MELI y el estado del pedido se actualiza.
+
+
+
+
diff --git a/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md b/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md
new file mode 100644
index 000000000..6581e05d8
--- /dev/null
+++ b/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md
@@ -0,0 +1,47 @@
+---
+title: 'Oferta de flete MELI para varios officialStoreIDs'
+id: 4KdPYtRbDdsBrn2k0dz7oc
+status: PUBLISHED
+createdAt: 2024-02-07T11:19:11.169Z
+updatedAt: 2024-06-19T11:43:56.663Z
+publishedAt: 2024-06-19T11:43:56.663Z
+firstPublishedAt: 2024-02-07T11:19:12.139Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: oferta-de-flete-meli-para-varios-officialstoreids
+locale: es
+kiStatus: Fixed
+internalReference: 978358
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente tenemos un problema con la integración de MELI con respecto a la API de cotización de flete de MELI, esto se aplica sólo para los vendedores que utilizan múltiples officialStoreIDs en MELI, pero utilizando sólo una cuenta en VTEX utilizando el mismo sellerID en MELI
+
+
+##
+
+## Simulación
+
+
+
+Si se aplica este escenario, la cotización de flete de MELI devolverá error, y MELI redirigirá al vendedor a la hoja de cálculo de flete en lugar de utilizar la API de flete.
+
+
+
+## Workaround
+
+
+mantener actualizada la hoja de cálculo de fletes para evitar incoherencias entre VTEX y MELI
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md b/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md
new file mode 100644
index 000000000..22596b670
--- /dev/null
+++ b/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md
@@ -0,0 +1,47 @@
+---
+title: 'Los pedidos MELI FULL no crean factura en VTEX'
+id: 6SNkDcqCWeDDPm01RrM0FQ
+status: PUBLISHED
+createdAt: 2024-02-05T11:14:30.020Z
+updatedAt: 2024-02-05T11:14:31.187Z
+publishedAt: 2024-02-05T11:14:31.187Z
+firstPublishedAt: 2024-02-05T11:14:31.187Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: los-pedidos-meli-full-no-crean-factura-en-vtex
+locale: es
+kiStatus: Backlog
+internalReference: 976614
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema con los pedidos MELI FULL, si el pedido presenta algún error durante la creación en VTEX, como error de SLA, fuera de stock, etc. el proceso para crear la factura en VTEX no se ejecuta. Básicamente el XML dentro de embeddedInvocie de OMS no se está creando en estos casos.
+
+
+
+## Simulación
+
+
+
+Si el pedido presenta algún error durante su creación, el XML no se colocará dentro de VTEX OMS.
+
+
+
+## Workaround
+
+
+para evitar este error las órdenes no deben ser pegadas en VTEX Bridge, para ello siempre configurar los SLAs necesarios para evitar este error
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md b/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md
new file mode 100644
index 000000000..10b1cd455
--- /dev/null
+++ b/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md
@@ -0,0 +1,49 @@
+---
+title: 'MELI valor incorrecto cuando el cliente tiene Cupón en MELI'
+id: 3PvNKqG2BMZDBLLVuriIHy
+status: PUBLISHED
+createdAt: 2024-01-22T11:58:00.747Z
+updatedAt: 2024-01-22T11:58:01.431Z
+publishedAt: 2024-01-22T11:58:01.431Z
+firstPublishedAt: 2024-01-22T11:58:01.431Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-valor-incorrecto-cuando-el-cliente-tiene-cupon-en-meli
+locale: es
+kiStatus: Backlog
+internalReference: 969297
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente el cliente utiliza un cupón en MELI, hay una variedad de tipos de cupones en MELI. Y algunos de ellos no están incluidos en los cálculos de VTEX OMS.
+
+
+##
+
+## Simulación
+
+
+
+En VTEX OMS, el valor de la orden puede ser diferente de lo que MELI vendió al cliente, debido a que algunos tipos de cupones no están siendo considerados al crear la orden en VTEX.
+
+
+
+## Workaround
+
+
+
+Para los pedidos ME1, si el vendedor necesita tener el valor correcto del pedido, con el fin de enviar el valor de la factura a MELI, puede utilizar el campo en VTEX OMS llamado "total_paid_amount", este campo está considerando actualmente todos los valores de los cupones.
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
new file mode 100644
index 000000000..4362376ba
--- /dev/null
+++ b/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -0,0 +1,54 @@
+---
+title: 'La integración MELI está recibiendo errores de MELI "429 demasiadas peticiones"'
+id: 1e4g9nzZFyanywmLbSHq4D
+status: PUBLISHED
+createdAt: 2023-08-03T10:47:41.602Z
+updatedAt: 2023-08-14T14:08:12.646Z
+publishedAt: 2023-08-14T14:08:12.646Z
+firstPublishedAt: 2023-08-03T10:47:43.214Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: la-integracion-meli-esta-recibiendo-errores-de-meli-429-demasiadas-peticiones
+locale: es
+kiStatus: Fixed
+internalReference: 873998
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema con algunas cuentas en MELi que están recibiendo un error al intentar actualizar productos, stock o precio en MELI.
+
+Esto no afecta a todas las cuentas ni a todas las SKU, sino sólo a una parte de ellas, y se debe a que se envían más solicitudes de las que MELI está preparado para recibir.
+
+
+##
+
+## Simulación
+
+
+
+Dentro del menú de integración stock/precio/producto algunas cuentas pueden ver un error:
+
+**Lo sentimos, no hemos podido procesar esta solicitud. Por favor, espere unos minutos y vuelva a procesarla**.
+
+Estamos trabajando en cómo gestionar mejor las solicitudes para evitar obtener este error de MELI.
+
+
+
+## Workaround
+
+
+La única solución disponible por ahora es volver a procesar la solicitud directamente en el menú del puente.
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md b/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
new file mode 100644
index 000000000..c02fb0fb8
--- /dev/null
+++ b/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
@@ -0,0 +1,48 @@
+---
+title: 'Tipos de listados de integración MELI para Perú, Venezuela, Ecuador y Uruguai'
+id: 77DQc7iQ4KgiWZGRAGdTgT
+status: PUBLISHED
+createdAt: 2023-10-25T11:48:14.580Z
+updatedAt: 2023-10-25T11:48:15.479Z
+publishedAt: 2023-10-25T11:48:15.479Z
+firstPublishedAt: 2023-10-25T11:48:15.479Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: tipos-de-listados-de-integracion-meli-para-peru-venezuela-ecuador-y-uruguai
+locale: es
+kiStatus: Backlog
+internalReference: 925139
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente nuestra aplicación MELI no está enviando el tipo de listado correcto para los países **Perú, Venezuela, Ecuador y Uruguai**.
+
+
+##
+
+## Simulación
+
+
+
+Siempre que los vendedores habiliten MELI Classic en VTEX para los países **Perú, Venezuela, Ecuador y Uruguai** los anuncios serán creados como Premium.
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
index 351bdbac5..5106b85bc 100644
--- a/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -3,8 +3,8 @@ title: 'Integración MELI Códigos postales "11111" Meli - Lima/Perú'
 id: 7ICcek0NOUczgtA65CaZk5
 status: PUBLISHED
 createdAt: 2023-05-16T17:50:38.417Z
-updatedAt: 2023-05-16T17:50:39.140Z
-publishedAt: 2023-05-16T17:50:39.140Z
+updatedAt: 2023-08-16T12:43:27.706Z
+publishedAt: 2023-08-16T12:43:27.706Z
 firstPublishedAt: 2023-05-16T17:50:39.140Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: integracion-meli-codigos-postales-11111-meli-limaperu
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 826566
 ---
 
diff --git a/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md b/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md
new file mode 100644
index 000000000..ec0be5dbd
--- /dev/null
+++ b/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md
@@ -0,0 +1,46 @@
+---
+title: 'MELI Map envía incorrectamente la especificación del producto como variación'
+id: 6b49pUUxL3B3RtUWofLjL8
+status: PUBLISHED
+createdAt: 2023-06-27T11:20:49.475Z
+updatedAt: 2023-06-27T11:20:50.484Z
+publishedAt: 2023-06-27T11:20:50.484Z
+firstPublishedAt: 2023-06-27T11:20:50.484Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-map-envia-incorrectamente-la-especificacion-del-producto-como-variacion
+locale: es
+kiStatus: Backlog
+internalReference: 851021
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema en la función MELI Mapper, que decidimos enviar un SKU como variación basado en los atributos de categoría de MELI, y no basado en lo que el vendedor ha mapeado en VTEX, lo que significa que una especificación de producto mapeada en VTEX puede ser enviada como variación a MELI.
+
+
+
+## Simulación
+
+
+
+Dentro de la función de mapeo, siempre que el vendedor mapee un atributo que acepte variación en MELI, será enviado como variación, incluso si el vendedor mapeó dentro de la especificación del producto.
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
diff --git a/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md b/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
new file mode 100644
index 000000000..d05cf16d9
--- /dev/null
+++ b/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
@@ -0,0 +1,49 @@
+---
+title: 'Las órdenes MELI no se cancelan en el escenario VTEX OMS para cuentas múltiples'
+id: 4u9ue93sHNWcfVm3sRL2qx
+status: PUBLISHED
+createdAt: 2024-02-06T11:04:52.918Z
+updatedAt: 2024-02-06T11:04:54.082Z
+publishedAt: 2024-02-06T11:04:54.082Z
+firstPublishedAt: 2024-02-06T11:04:54.082Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: las-ordenes-meli-no-se-cancelan-en-el-escenario-vtex-oms-para-cuentas-multiples
+locale: es
+kiStatus: Backlog
+internalReference: 977453
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente nuestra integración MELI tiene un problema relacionado con el proceso de cancelación de pedidos. Cuando MELI cancela un pedido y el vendedor tiene más de 4 cuentas en VTEX existe la posibilidad de que no se intente cancelar el pedido en la quinta cuenta
+
+
+##
+
+## Simulación
+
+
+
+Si la cancelación de la orden no puede ser completada el vendedor puede ver la orden no cancelada en VTEX pero cancelada en MELI, para este caso se requiere una cancelación manual directamente en OMS.
+Esto sólo se aplica para los casos en que el vendedor tiene más de 4 cuentas en VTEX, utilizando el mismo MELI UserID.
+
+
+
+## Workaround
+
+ provisional
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md b/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md
new file mode 100644
index 000000000..87b95b7f7
--- /dev/null
+++ b/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md
@@ -0,0 +1,54 @@
+---
+title: 'La tabla de tallas MELI no funciona para las tallas con letras'
+id: 7vAViV3MmC7zOSTF0cFTYy
+status: PUBLISHED
+createdAt: 2023-07-24T12:04:19.589Z
+updatedAt: 2023-09-12T15:04:46.716Z
+publishedAt: 2023-09-12T15:04:46.716Z
+firstPublishedAt: 2023-07-24T12:04:20.171Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: la-tabla-de-tallas-meli-no-funciona-para-las-tallas-con-letras
+locale: es
+kiStatus: Fixed
+internalReference: 867262
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente nuestra característica MELI Size Chart no está funcionando para los tamaños con letras ejemplo:
+
+Talla = "P", "M", "G".
+
+
+##
+
+## Simulación
+
+
+
+Dentro de la pantalla del mapeador, podemos la función de tabla de tallas disponible para la integración MELI, por lo que si los vendedores mapean una talla con sus valores como letras no funcionará y se mostrará un mensaje de error en el producto puente como el siguiente:
+
+"El valor del atributo TALLA no es válido: P. Este valor debe ser igual al de la tabla de medidas".
+
+
+##
+
+## Workaround
+
+
+
+Actualmente las tallas funcionan con números, por lo que los vendedores pueden utilizar los números en lugar de las letras.
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md b/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md
new file mode 100644
index 000000000..54182f444
--- /dev/null
+++ b/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md
@@ -0,0 +1,47 @@
+---
+title: 'Atributo de emisión MELI SizeChart no válido'
+id: 3t6zqW9aE6pvW9b3Zvj0MB
+status: PUBLISHED
+createdAt: 2024-03-08T13:59:23.756Z
+updatedAt: 2024-03-11T20:00:06.480Z
+publishedAt: 2024-03-11T20:00:06.480Z
+firstPublishedAt: 2024-03-08T13:59:24.514Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: atributo-de-emision-meli-sizechart-no-valido
+locale: es
+kiStatus: Fixed
+internalReference: 996639
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Mercado Livre ha incluido recientemente nuevos atributos obligatorios en la función de integración de tablas de tallas, por lo que ahora debemos arreglar nuestra integración con estos nuevos atributos para que los vendedores puedan exportar correctamente las tablas de tallas a MELI.
+
+
+
+## Simulación
+
+
+
+Al cargar la tabla de tallas en la interfaz de usuario, es posible que aparezca el error "El atributo XXX no es válido", lo que puede estar relacionado con este error
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/es/meli-update-stockprice-issue.md b/docs/known-issues/es/meli-update-stockprice-issue.md
new file mode 100644
index 000000000..757a24329
--- /dev/null
+++ b/docs/known-issues/es/meli-update-stockprice-issue.md
@@ -0,0 +1,48 @@
+---
+title: 'Actualización de MELI Emisión de acciones/precios'
+id: 7LQ81vG5nsbBn4Wj7Z9VJe
+status: PUBLISHED
+createdAt: 2023-12-12T10:22:28.961Z
+updatedAt: 2024-01-10T17:51:59.853Z
+publishedAt: 2024-01-10T17:51:59.853Z
+firstPublishedAt: 2023-12-12T10:22:29.656Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: actualizacion-de-meli-emision-de-accionesprecios
+locale: es
+kiStatus: Fixed
+internalReference: 939329
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un escenario muy específico que afecta a pocos casos de SKUs que no pueden actualizar el stock en MELI.
+
+
+##
+
+## Simulación
+
+
+
+Lo que ocurre es que en algunos casos el campo seller_custom_field que debería rellenarse con la SKU VTEX, en realidad está en blanco, por lo que la integración no es capaz de actualizar el stock de MELI en estos casos.
+
+
+
+## Workaround
+
+
+Rellenar la hoja de cálculo de migración con estos casos y enviar al equipo de producto para establecer nuestro SKU dentro de seller_custom_field.
+
+
+
+
+
diff --git a/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md b/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
new file mode 100644
index 000000000..fff66d6ba
--- /dev/null
+++ b/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
@@ -0,0 +1,59 @@
+---
+title: '[Mercado Livre] AD BuyBox no actualiza shipping_mode para ME2'
+id: 5XmZsbZz1171a04dWPs2MY
+status: PUBLISHED
+createdAt: 2024-06-03T11:38:34.337Z
+updatedAt: 2024-06-03T11:38:35.242Z
+publishedAt: 2024-06-03T11:38:35.242Z
+firstPublishedAt: 2024-06-03T11:38:35.242Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-ad-buybox-no-actualiza-shippingmode-para-me2
+locale: es
+kiStatus: Backlog
+internalReference: 1042779
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+AD BuyBox no actualiza shipping_mode para ME2
+
+
+##
+
+## Simulación
+
+
+
+P: ¿Por qué el anuncio está en under_review cuando intento actualizar ME2?
+R: A día de hoy el estado de este anuncio en MELI es under_review, esto ocurre porque es un anuncio tipo BuyBox y en este caso no podemos actualizarlo a ME2 porque MELI no lo permite, y por este motivo cuando intentamos actualizar MELI nos devuelve la siguiente moderación:
+
+
+    Não é possível processar uma solicitação de um anúncio moderado pelo Mercado Livre.<br><br>Resumo da moderação: <br><br>Resolución: Cancelamos el aviso porque usted sólo puede vender este producto con su aviso de catálogo. <br>Remisión: Cancelamos la suscripción porque ya puede vender este producto con su número de catálogo.
+
+
+P: ¿Esto ocurrirá con todos los anuncios buybox?
+R: No, este escenario sólo ocurrirá cuando el caso sea para "Restringir catálogo" donde sólo puede haber un anuncio BuyBox, no porque sea BuyBox sino porque es este tipo específico de Restringir.
+
+**SOLUCIÓN**
+Como no tenemos este flujo de actualización ME2 para anuncios buybox, estamos abriendo este KI
+
+
+
+## Workaround
+
+
+Abre un ticket al equipo de conexiones solicitando una actualización para ME2, informando siempre del anuncio buybox ej: MLB36470123456
+
+
+
+
+
+
diff --git a/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
new file mode 100644
index 000000000..67342d0a4
--- /dev/null
+++ b/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
@@ -0,0 +1,53 @@
+---
+title: '[Mercado Livre] [Bridge] Bridge no registra algunos mensajes de error'
+id: 3KmdcY6hlLQx5h1FgKHAbS
+status: PUBLISHED
+createdAt: 2024-06-21T12:38:31.025Z
+updatedAt: 2024-06-26T11:07:40.994Z
+publishedAt: 2024-06-26T11:07:40.994Z
+firstPublishedAt: 2024-06-21T12:38:31.845Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-bridge-bridge-no-registra-algunos-mensajes-de-error
+locale: es
+kiStatus: Backlog
+internalReference: 1053742
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Error en el flujo de actualización sku no se está registrando en el puente
+
+**Mercado:** Mercado Livre
+**Causa principal:** Admin > Puente > Producto
+
+**Importante:** no ocurre con todos los skus;
+
+
+##
+
+## Simulación
+
+
+Admin > Mercado > Productos > Amazon
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/3MxTLEnmPv9lgG7UE8iUEd1Ft/?name=image.png)
+
+
+
+## Workaround
+
+
+En algunos casos, reprocesando el sku en el puente se resuelve el problema.
+
+
+
+
+
diff --git a/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md b/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
new file mode 100644
index 000000000..4ecc7e18f
--- /dev/null
+++ b/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
@@ -0,0 +1,50 @@
+---
+title: '[Mercado Livre] El menú de pedidos del puente no muestra la información del ID de envío.'
+id: 2fXDbejpPJ04NDfPCCcr0j
+status: PUBLISHED
+createdAt: 2024-03-18T20:56:17.859Z
+updatedAt: 2024-03-18T20:56:18.697Z
+publishedAt: 2024-03-18T20:56:18.697Z
+firstPublishedAt: 2024-03-18T20:56:18.697Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-el-menu-de-pedidos-del-puente-no-muestra-la-informacion-del-id-de-envio
+locale: es
+kiStatus: Backlog
+internalReference: 1001903
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente tenemos un problema que solo afecta a la visibilidad de algunos Pedidos MELI, lo que ocurre es que actualmente estamos registrando el ShipmentID en el menu del puente de pedidos, pero en algunos mensajes de error falta el OrderID, y es necesario para algunos casos ya que el orderID es la informacion que los vendedores tienen en el Portal MELI
+
+Mercado Livre > Puente > OrderId
+
+
+##
+
+## Simulación
+
+
+Dentro del menú de pedidos del puente, algunos mensajes de error no están registrando el orderID, lo que da la impresión de que algunos pedidos no están en VTEX brige, pero los vendedores pueden encontrar los pedidos buscando por el shipmentID.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/OZk1c79PgvKBKq6wGldvIbHM6/?name=image.png)
+
+
+
+## Workaround
+
+
+GET el OrderID, y obtener el ShipmentID y buscarlo en el puente
+
+
+
+
+
diff --git a/docs/known-issues/es/mercado-livre-mapper-attribute-size.md b/docs/known-issues/es/mercado-livre-mapper-attribute-size.md
index 347be9d71..e0618f551 100644
--- a/docs/known-issues/es/mercado-livre-mapper-attribute-size.md
+++ b/docs/known-issues/es/mercado-livre-mapper-attribute-size.md
@@ -1,18 +1,18 @@
 ---
-title: 'Tamaño del atributo Mercado Book Mapper'
+title: 'Tamaño del atributo Mercado Livre Mapper'
 id: 3dLrm6SVsPB4tU46SC3Xdi
 status: PUBLISHED
 createdAt: 2022-07-26T19:53:34.899Z
-updatedAt: 2022-11-25T21:55:42.119Z
-publishedAt: 2022-11-25T21:55:42.119Z
+updatedAt: 2024-02-16T20:28:24.174Z
+publishedAt: 2024-02-16T20:28:24.174Z
 firstPublishedAt: 2022-07-26T19:53:35.449Z
 contentType: knownIssue
 productTeam: Connections
 author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
-slug: tamano-del-atributo-mercado-book-mapper
+slug: tamano-del-atributo-mercado-livre-mapper
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 592577
 ---
 
@@ -24,9 +24,10 @@ internalReference: 592577
 
 
 
-Incluso mapeando correctamente el atributo "Tamaño" en el mapeador, para algunas categorías MELI no está funcionando correctamente.
+Incluso mapeando correctamente el atributo "Tamaño" en mapper, para algunas categorías MELI no está funcionando correctamente.
 
 
+##
 
 ## Simulación
 
@@ -39,5 +40,9 @@ Dentro del menú de productos del puente, verá un error sobre el atributo Tama
 ## Workaround
 
 
-n/a
+¿Existe alguna solución para este error? En caso afirmativo, descríbala aquí. En caso negativo, escriba "N/A" o "No hay solución disponible". No elimine esta sección si no hay solución, por favor.
+
+
+
+
 
diff --git a/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md b/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md
new file mode 100644
index 000000000..a6bca9d9b
--- /dev/null
+++ b/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md
@@ -0,0 +1,42 @@
+---
+title: '[Mercado Livre] Eliminar validación under_review en Actualizar SKU'
+id: 1yeZeigiok3zaltkI7RTMW
+status: PUBLISHED
+createdAt: 2023-08-30T18:15:25.269Z
+updatedAt: 2023-08-30T18:15:25.924Z
+publishedAt: 2023-08-30T18:15:25.924Z
+firstPublishedAt: 2023-08-30T18:15:25.924Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-eliminar-validacion-underreview-en-actualizar-sku
+locale: es
+kiStatus: Backlog
+internalReference: 890658
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+SKU fue moderado por estar en una categoría incorrecta, ya se hizo la corrección y ahora tiene el mapeo correcto en mapepr, pero sigue sin exportarse de acuerdo a la categoría del mapeador.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
new file mode 100644
index 000000000..c3b68a55b
--- /dev/null
+++ b/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
@@ -0,0 +1,48 @@
+---
+title: '[Mercado Livre] [Sku] Bridge no registra algunos mensajes de error'
+id: 2GcnFE9TKcivoPekYuCNF9
+status: PUBLISHED
+createdAt: 2024-07-23T16:00:26.447Z
+updatedAt: 2024-07-23T16:08:16.661Z
+publishedAt: 2024-07-23T16:08:16.661Z
+firstPublishedAt: 2024-07-23T16:00:27.366Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-sku-bridge-no-registra-algunos-mensajes-de-error
+locale: es
+kiStatus: Backlog
+internalReference: 1069692
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Contexto correcto: En algunos casos, el vendedor no puede integrar el SKU, ya que el mensaje de error con el motivo por el que se moderó el artículo no aparece correctamente en Bridge.
+
+
+
+##
+
+## Simulación
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/8b6ggO2OjPCsPZlU5NanwK645/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
new file mode 100644
index 000000000..f5941d2fc
--- /dev/null
+++ b/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -0,0 +1,52 @@
+---
+title: 'Las reglas de comercialización no funcionan para la faceta "productClusterIds".'
+id: 6sLODMgjuoyJD52uc0DBW1
+status: PUBLISHED
+createdAt: 2024-07-09T00:02:40.930Z
+updatedAt: 2024-07-09T00:02:41.798Z
+publishedAt: 2024-07-09T00:02:41.798Z
+firstPublishedAt: 2024-07-09T00:02:41.798Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: las-reglas-de-comercializacion-no-funcionan-para-la-faceta-productclusterids
+locale: es
+kiStatus: Backlog
+internalReference: 1062457
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las reglas de merchandising no se aplican a la faceta "productClusterIds". Esto ocurre porque esta faceta tiene el comportamiento especial de ordenar los productos por el orden de colección en lugar de por relevancia y reglas de merchandising.
+
+Esta faceta no debe considerarse válida para una regla de merchandising.
+
+
+
+## Simulación
+
+
+
+- crear una colección con algunos productos en un orden específico
+- crear una regla comercial filtrada explícitamente por "productClusterIds" o "productClusterSearchableIds"
+- establecer esta regla para ordenar los productos en un orden diferente
+- comprobar en la tienda que los productos mantendrán la ordenación de la colección
+
+
+
+## Workaround
+
+
+La forma esperada de gestionar y ordenar los productos de una colección es hacerlo directamente en la colección añadiendo/eliminando productos o cambiando su posición.
+
+También es posible aplicar la regla de ordenación a la faceta "productClusterNames" en su lugar. Esta faceta sigue las reglas de relevancia en lugar del orden de la colección y funciona con las reglas de merchandising.
+
+
+
+
diff --git a/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md b/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
new file mode 100644
index 000000000..563a61aa5
--- /dev/null
+++ b/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
@@ -0,0 +1,54 @@
+---
+title: 'El comerciante no puede abrir una cuenta para algunos clientes en la API de crédito de clientes.'
+id: 4NGCingtQxzFV1gMbxFzT1
+status: PUBLISHED
+createdAt: 2023-09-25T13:22:58.063Z
+updatedAt: 2023-09-25T13:22:58.651Z
+publishedAt: 2023-09-25T13:22:58.651Z
+firstPublishedAt: 2023-09-25T13:22:58.651Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-comerciante-no-puede-abrir-una-cuenta-para-algunos-clientes-en-la-api-de-credito-de-clientes
+locale: es
+kiStatus: Backlog
+internalReference: 906509
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Por alguna razón, al intentar abrir una nueva cuenta para clientes específicos a través de la API, devuelve el siguiente error:
+
+{
+"código": 1099,
+"mensaje": "La cuenta de crédito ya está abierta".
+}
+
+
+En este escenario, los datos del cliente (Nombre, documento, etc.) nunca se han utilizado antes en ninguna otra cuenta.
+
+
+##
+
+## Simulación
+
+
+Esto ocurre de forma inconsistente, por lo que sólo ocurrirá cada dos intentos.
+
+
+
+## Workaround
+
+
+Cree la cuenta a través de la interfaz de administración.
+
+
+
+
+
diff --git a/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md b/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md
new file mode 100644
index 000000000..f92dff269
--- /dev/null
+++ b/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md
@@ -0,0 +1,43 @@
+---
+title: 'La aplicación Mensajes tarda demasiado en devolver la información.'
+id: 5GnHyQaPlqCW0KNar1tlMC
+status: PUBLISHED
+createdAt: 2024-01-30T14:16:58.627Z
+updatedAt: 2024-01-30T14:16:59.326Z
+publishedAt: 2024-01-30T14:16:59.326Z
+firstPublishedAt: 2024-01-30T14:16:59.326Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: la-aplicacion-mensajes-tarda-demasiado-en-devolver-la-informacion
+locale: es
+kiStatus: Backlog
+internalReference: 567305
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el proceso de indexación, llamamos a la aplicación de mensajes para guardar la información traducida de los productos, el principal problema es que las peticiones están tardando demasiado en volver y con eso, algunas tiendas que tienen muchos idiomas no indexan completamente o tienen sus indexaciones atascadas.
+
+
+##
+
+## Simulación
+
+
+Comprueba cualquier tienda que tenga una gran cantidad de idiomas, más de 10 y empezará a ralentizar la respuesta de los mensajes.
+Puede reflejarse en otros sistemas que dependen de los mensajes para traducir información.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md b/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md
new file mode 100644
index 000000000..fb468a5b4
--- /dev/null
+++ b/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md
@@ -0,0 +1,46 @@
+---
+title: "El campo 'MetaTagDescription' no se puede eliminar a través de Admin"
+id: 7h0HlpuQnE8nWylgSWJ1lR
+status: PUBLISHED
+createdAt: 2024-02-08T20:21:00.735Z
+updatedAt: 2024-02-08T20:21:01.739Z
+publishedAt: 2024-02-08T20:21:01.739Z
+firstPublishedAt: 2024-02-08T20:21:01.739Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-campo-metatagdescription-no-se-puede-eliminar-a-traves-de-admin
+locale: es
+kiStatus: Backlog
+internalReference: 979691
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Haga clic en el producto a editar
+- Borre el valor del campo `MetaTagDescription`.
+- Haga clic en "Guardar" y volver al producto
+- Compruebe que el valor original ya no está allí, pero el valor de la `description` se duplicó
+
+
+
+## Workaround
+
+
+Utilice la API para eliminar el valor no deseado después de actualizar el producto en el Admin
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/product/-productId-?endpoint=put-/api/catalog/pvt/product/-productId-
+
+
+
+
diff --git a/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md b/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md
new file mode 100644
index 000000000..5952713f8
--- /dev/null
+++ b/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md
@@ -0,0 +1,52 @@
+---
+title: 'Los mensajes de error de los cupones Minicart sólo aparecen tras un segundo intento'
+id: 6ZdpXaHJFudXXwUDC00lcr
+status: PUBLISHED
+createdAt: 2023-12-18T16:22:10.537Z
+updatedAt: 2023-12-18T16:22:11.359Z
+publishedAt: 2023-12-18T16:22:11.359Z
+firstPublishedAt: 2023-12-18T16:22:11.359Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: los-mensajes-de-error-de-los-cupones-minicart-solo-aparecen-tras-un-segundo-intento
+locale: es
+kiStatus: No Fix
+internalReference: 938379
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los mensajes de error de cupón en Minicart no aparecerán la primera vez que intente un cupón, incluso si no existe.
+
+
+##
+
+## Simulación
+
+
+
+1. Añade el producto al carrito.
+2. Abrir el minicarrito.
+3. Introduce un cupón aleatorio dentro del minicarrito.
+4. No aparecerá el mensaje de error.
+5. Introduce otro cupón falso.
+6. Aparecerá el mensaje de error.
+
+
+
+## Workaround
+
+
+No existe ninguna solución. Sin embargo, introduciendo el código en cualquier momento después del primer intento se mostrará el mensaje de error correctamente.
+
+
+
+
+
diff --git a/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md b/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md
index 63c3c7982..05d6b733d 100644
--- a/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md
+++ b/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md
@@ -3,8 +3,8 @@ title: 'Minicart no muestra las especificaciones de las SKU en el escenario B2B'
 id: 4eOpxrLEkyHyobCDuWzsMK
 status: PUBLISHED
 createdAt: 2022-10-27T19:11:58.877Z
-updatedAt: 2022-11-25T22:13:10.845Z
-publishedAt: 2022-11-25T22:13:10.845Z
+updatedAt: 2024-02-16T20:28:02.341Z
+publishedAt: 2024-02-16T20:28:02.341Z
 firstPublishedAt: 2022-10-27T19:11:59.318Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: minicart-no-muestra-las-especificaciones-de-las-sku-en-el-escenario-b2b
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 687308
 ---
 
diff --git a/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index 268c97c64..7fd74de95 100644
--- a/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -3,8 +3,8 @@ title: 'Comportamiento erróneo de la mutación addToCart de checkout-graphql al
 id: 1lMWbgmBsOis9gAKcMm8ob
 status: PUBLISHED
 createdAt: 2022-05-03T20:42:18.655Z
-updatedAt: 2022-11-25T22:44:04.555Z
-publishedAt: 2022-11-25T22:44:04.555Z
+updatedAt: 2023-11-16T16:46:29.538Z
+publishedAt: 2023-11-16T16:46:29.538Z
 firstPublishedAt: 2022-05-03T20:42:18.940Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: comportamiento-erroneo-de-la-mutacion-addtocart-de-checkout-graphql-al-enviar-las-opciones-de-los-articulos-ya-anadidos
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 452053
 ---
 
diff --git a/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md b/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
index 2e54f9ffe..fe5e3feea 100644
--- a/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
+++ b/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
@@ -29,9 +29,9 @@ Principales causas de una aplicación mal configurada:
 
 En el caso de un JSON Schema inexistente, coloque en el campo `model` el nombre correcto del JSON Schema.
 
-Por ejemplo: ![Screen Shot 2019-01-03 at 19.31.53](https://images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
+Por ejemplo: ![Screen Shot 2019-01-03 at 19.31.53](//images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
 
-Observe cómo el borde de la aplicación se vuelve rojo y el mensaje de error en la consola indica el error "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](https://images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
+Observe cómo el borde de la aplicación se vuelve rojo y el mensaje de error en la consola indica el error "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](//images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
 
 
 ## Workaround
diff --git a/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md b/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
index ee47027d5..90991c755 100644
--- a/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
+++ b/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
@@ -3,8 +3,8 @@ title: 'La falta del campo minicart.buyer.id hace que el antifraude cancele tran
 id: 6dvOH9b96qGAHXIzW3wBe1
 status: PUBLISHED
 createdAt: 2023-05-23T17:10:17.329Z
-updatedAt: 2023-05-23T17:10:17.964Z
-publishedAt: 2023-05-23T17:10:17.964Z
+updatedAt: 2024-02-16T20:26:42.045Z
+publishedAt: 2024-02-16T20:26:42.045Z
 firstPublishedAt: 2023-05-23T17:10:17.964Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: la-falta-del-campo-minicartbuyerid-hace-que-el-antifraude-cancele-transacciones
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 514335
 ---
 
diff --git a/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md b/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
new file mode 100644
index 000000000..3301482be
--- /dev/null
+++ b/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
@@ -0,0 +1,47 @@
+---
+title: 'Falta la traducción de la faceta/filtro de precios en la Búsqueda Inteligente'
+id: 6c6GnC1dKGViJ2h0ZoY5pm
+status: PUBLISHED
+createdAt: 2024-01-31T21:33:04.796Z
+updatedAt: 2024-01-31T21:33:05.556Z
+publishedAt: 2024-01-31T21:33:05.556Z
+firstPublishedAt: 2024-01-31T21:33:05.556Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: falta-la-traduccion-de-la-facetafiltro-de-precios-en-la-busqueda-inteligente
+locale: es
+kiStatus: Backlog
+internalReference: 974840
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La Búsqueda Inteligente no aplica la traducción al nombre del filtro/facet "precio" para idiomas adicionales cuando se consulta a través de REST API.
+
+El idioma principal sigue devolviendo la cadena esperada como configuración interna, pero cualquier otro idioma lo devolverá con "Precio" como valor fijo.
+
+
+##
+
+## Simulación
+
+
+En una tienda con varios idiomas, configure las traducciones para el contexto de búsqueda inteligente a través del servicio de mensajes a los idiomas secundarios y consúltelo mediante la API de facetas. Los valores para "Precio" no se tendrán en cuenta, mientras que funciona para cualquier otra etiqueta, como las categorías y la marca.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md b/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
index 7ff0e9c8b..583a3f60f 100644
--- a/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
+++ b/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
@@ -3,8 +3,8 @@ title: 'Modal como Razón Genérica incluso este tipo de Modal están configurad
 id: 2ftzXjtPZcPypFpsnZMcIK
 status: PUBLISHED
 createdAt: 2022-05-18T18:23:53.248Z
-updatedAt: 2022-11-25T21:59:39.823Z
-publishedAt: 2022-11-25T21:59:39.823Z
+updatedAt: 2024-02-16T20:25:38.358Z
+publishedAt: 2024-02-16T20:25:38.358Z
 firstPublishedAt: 2022-05-18T18:23:53.787Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: modal-como-razon-generica-incluso-este-tipo-de-modal-estan-configurados-ok
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 488339
 ---
 
diff --git a/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md b/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md
index d560b73fd..dd5d7e535 100644
--- a/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md
+++ b/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md
@@ -3,8 +3,8 @@ title: 'Configuración de las divergencias de los modales obsoletos - Política
 id: TYWgIv5xOTUBWdC63FbK5
 status: PUBLISHED
 createdAt: 2022-05-18T18:20:55.870Z
-updatedAt: 2022-11-25T21:59:19.021Z
-publishedAt: 2022-11-25T21:59:19.021Z
+updatedAt: 2024-02-16T20:27:05.367Z
+publishedAt: 2024-02-16T20:27:05.367Z
 firstPublishedAt: 2022-05-18T18:20:56.247Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: configuracion-de-las-divergencias-de-los-modales-obsoletos-politica-de-envios
 locale: es
-kiStatus: Scheduled
+kiStatus: No Fix
 internalReference: 445866
 ---
 
diff --git a/docs/known-issues/es/multiple-sku-promotion-api-not-working.md b/docs/known-issues/es/multiple-sku-promotion-api-not-working.md
index fe8b717a3..8dd440cbc 100644
--- a/docs/known-issues/es/multiple-sku-promotion-api-not-working.md
+++ b/docs/known-issues/es/multiple-sku-promotion-api-not-working.md
@@ -3,8 +3,8 @@ title: 'La API de promoción de múltiples Sku no funciona'
 id: 38CLe2oIWHGNgjL4L0uIxz
 status: PUBLISHED
 createdAt: 2023-01-09T21:18:05.077Z
-updatedAt: 2023-01-09T21:18:05.807Z
-publishedAt: 2023-01-09T21:18:05.807Z
+updatedAt: 2024-02-16T20:23:56.065Z
+publishedAt: 2024-02-16T20:23:56.065Z
 firstPublishedAt: 2023-01-09T21:18:05.807Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: la-api-de-promocion-de-multiples-sku-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 729990
 ---
 
diff --git a/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md b/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
new file mode 100644
index 000000000..df7f00a19
--- /dev/null
+++ b/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
@@ -0,0 +1,49 @@
+---
+title: 'El pie de página de mis tarjetas tiembla al intentar añadir una nueva tarjeta'
+id: 5JRsJqm0PmVkdCh7td3DIr
+status: PUBLISHED
+createdAt: 2024-04-05T16:09:59.991Z
+updatedAt: 2024-04-05T16:11:11.933Z
+publishedAt: 2024-04-05T16:11:11.933Z
+firstPublishedAt: 2024-04-05T16:10:01.510Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-pie-de-pagina-de-mis-tarjetas-tiembla-al-intentar-anadir-una-nueva-tarjeta
+locale: es
+kiStatus: Backlog
+internalReference: 1012542
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El pie de página de "Mis tarjetas" tiembla en la pantalla al intentar añadir una nueva tarjeta.
+
+
+##
+
+## Simulación
+
+
+
+1. Ir a una cuenta aleatoria
+2. Hacer login
+3. Acceder a Mi cuenta> Mis tarjetas
+4. Intenta guardar una nueva tarjeta falsa y cuando el proceso falle, pulsa guardar de nuevo, y entonces la pantalla temblará hasta que el proceso termine
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md b/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
index ea2ddfd5b..e63cc4dff 100644
--- a/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
+++ b/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
@@ -3,8 +3,8 @@ title: 'La interfaz de usuario de My Cards permite a los clientes guardar tarjet
 id: 7Ab61xaPRXqxA7VYEnFu8J
 status: PUBLISHED
 createdAt: 2022-02-10T12:34:15.351Z
-updatedAt: 2022-11-25T22:07:26.657Z
-publishedAt: 2022-11-25T22:07:26.657Z
+updatedAt: 2024-02-16T20:26:23.845Z
+publishedAt: 2024-02-16T20:26:23.845Z
 firstPublishedAt: 2022-02-10T12:34:15.869Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: la-interfaz-de-usuario-de-my-cards-permite-a-los-clientes-guardar-tarjetas-de-credito-sin-el-campo-del-numero-rellenado-en-la-informacion-de-la-direccion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 521542
 ---
 
diff --git a/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md b/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
index dd56cb7ef..6d6a3e76a 100644
--- a/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
+++ b/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
@@ -3,8 +3,8 @@ title: 'Mi suscripción muestra un mensaje de error cuando la suscripción está
 id: 4p9jzcVzB6E5b6PTm2Ng5E
 status: PUBLISHED
 createdAt: 2022-12-15T19:08:41.210Z
-updatedAt: 2022-12-15T19:08:42.066Z
-publishedAt: 2022-12-15T19:08:42.066Z
+updatedAt: 2024-03-11T19:58:56.132Z
+publishedAt: 2024-03-11T19:58:56.132Z
 firstPublishedAt: 2022-12-15T19:08:42.066Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md b/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
index 381dea1bb..a5b944aad 100644
--- a/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
+++ b/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
@@ -3,8 +3,8 @@ title: 'Mis suscripciones Al introducir la dirección de la línea 2 ésta apare
 id: 1VbFyW5rQcfUSEJgKphrqb
 status: PUBLISHED
 createdAt: 2022-05-30T13:50:13.717Z
-updatedAt: 2022-11-25T22:02:34.424Z
-publishedAt: 2022-11-25T22:02:34.424Z
+updatedAt: 2024-02-16T20:28:33.052Z
+publishedAt: 2024-02-16T20:28:33.052Z
 firstPublishedAt: 2022-05-30T13:50:14.433Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: mis-suscripciones-al-introducir-la-direccion-de-la-linea-2-esta-aparece-como-nula
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 588046
 ---
 
diff --git a/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md b/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md
index a2c7e0ccd..7def9a992 100644
--- a/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md
+++ b/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md
@@ -3,8 +3,8 @@ title: 'El botón giratorio de MyCards no funciona correctamente'
 id: 2Y1IHSesmqAKYsep1JzIND
 status: PUBLISHED
 createdAt: 2023-03-29T19:18:47.318Z
-updatedAt: 2023-03-29T19:18:47.732Z
-publishedAt: 2023-03-29T19:18:47.732Z
+updatedAt: 2023-11-06T13:02:14.964Z
+publishedAt: 2023-11-06T13:02:14.964Z
 firstPublishedAt: 2023-03-29T19:18:47.732Z
 contentType: knownIssue
 productTeam: Payments
diff --git a/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md b/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
index 508787720..f0a303aa8 100644
--- a/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
+++ b/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
@@ -3,8 +3,8 @@ title: 'MyCredits tiene un error al acceder desde una cuenta dependiente'
 id: 6QJWAD7Q2PSEMsmZYXqMag
 status: PUBLISHED
 createdAt: 2022-03-27T16:19:47.411Z
-updatedAt: 2022-11-25T22:08:20.276Z
-publishedAt: 2022-11-25T22:08:20.276Z
+updatedAt: 2024-02-16T20:29:22.908Z
+publishedAt: 2024-02-16T20:29:22.908Z
 firstPublishedAt: 2022-03-27T16:19:47.994Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: mycredits-tiene-un-error-al-acceder-desde-una-cuenta-dependiente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 367276
 ---
 
diff --git a/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md b/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md
index 1db7a820f..3c6c92e19 100644
--- a/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md
+++ b/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md
@@ -34,39 +34,3 @@ internalReference:
   <p>Este contenido sólo está disponible en Inglês.</p>
 </div>
 
-e de fecha de lanzamiento en el pasado reciente. Está presente en el siguiente componente de la interfaz de usuario:
-
- ![](https://vtexhelp.zendesk.com/attachments/token/pFLlcE3tDbGcA0bgmlAhPNccB/?name=image.png)
-
-Sin embargo, al combinar esta funcionalidad con la exportación de hojas, este filtro se ignora, trayendo todos los productos dentro de la colección.
-
-
-
-
-
-
-## Simulación
-
-
-1 - Vaya al módulo de nuevas colecciones y elija una colección
-
-2 - En el listado principal de la colección, utilice el filtro "Recién lanzado", tenga en cuenta que necesita tener al menos 1 producto con el valor "Fecha de lanzamiento" establecido en el rango filtrado. Este valor puede establecerse en la página de configuración del producto.
-
-3 - Un valor determinado de productos "Recién lanzados" será filtrado y listado en la UI.
-
-4 - Seleccione la función "Exportar".
-
-5 - Exporte una hoja de SKU para esta colección
-
-6 - Compruebe el número de registros exportados, será la cantidad total de productos de la colección, no los Recién Salidos.
-
-
-
-
-
-
-## Workaround
-
-
-Utilice filtros alternativos para su exportación.
-
diff --git a/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md b/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
index fbc1c0e47..44731df09 100644
--- a/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
+++ b/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
@@ -3,8 +3,8 @@ title: 'La nueva interfaz de usuario no muestra el documento de identidad del cl
 id: 7y7Npcr6krhsnnEy54vQFa
 status: PUBLISHED
 createdAt: 2022-12-08T22:21:07.966Z
-updatedAt: 2022-12-08T22:21:08.507Z
-publishedAt: 2022-12-08T22:21:08.507Z
+updatedAt: 2024-02-16T20:27:18.190Z
+publishedAt: 2024-02-16T20:27:18.190Z
 firstPublishedAt: 2022-12-08T22:21:08.507Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: la-nueva-interfaz-de-usuario-no-muestra-el-documento-de-identidad-del-cliente-por-ejemplo-el-cpf
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 713480
 ---
 
diff --git a/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md b/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
index 4f6d82ca4..d4b4c35a6 100644
--- a/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
+++ b/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
@@ -3,8 +3,8 @@ title: 'La nueva interfaz de usuario no muestra el valor facturado en la página
 id: 3DBFXzWoz7jxSdgSLICV8i
 status: PUBLISHED
 createdAt: 2022-09-27T19:34:46.895Z
-updatedAt: 2022-11-25T22:01:19.774Z
-publishedAt: 2022-11-25T22:01:19.774Z
+updatedAt: 2024-02-16T20:28:14.405Z
+publishedAt: 2024-02-16T20:28:14.405Z
 firstPublishedAt: 2022-09-27T19:34:47.384Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: la-nueva-interfaz-de-usuario-no-muestra-el-valor-facturado-en-la-pagina-de-articulos-devueltos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 664838
 ---
 
diff --git a/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md b/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
index cd6bb9799..aa4a27657 100644
--- a/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
+++ b/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
@@ -20,7 +20,7 @@ internalReference:
 
 El campo NIF (documento) del checkout de Portugal (IU) está permitiendo introducir caracteres especiales en sus valores. Sin embargo, los pedidos que se cierran con caracteres especiales quedan bloqueados con error en el OMS.
 
-![OMS](https://images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
+![OMS](//images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md b/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
new file mode 100644
index 000000000..1d7608482
--- /dev/null
+++ b/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
@@ -0,0 +1,75 @@
+---
+title: 'No se puede crear ninguna ventana de entrega debido a la incoherencia en estimateDate y lastDeliveryDay para timecost alto'
+id: 3E5ZPyrjSOPD68vH4SXunM
+status: PUBLISHED
+createdAt: 2024-03-06T19:38:26.954Z
+updatedAt: 2024-03-06T19:38:27.765Z
+publishedAt: 2024-03-06T19:38:27.765Z
+firstPublishedAt: 2024-03-06T19:38:27.765Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: no-se-puede-crear-ninguna-ventana-de-entrega-debido-a-la-incoherencia-en-estimatedate-y-lastdeliveryday-para-timecost-alto
+locale: es
+kiStatus: Backlog
+internalReference: 995491
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+El `estimateDate` tiene en cuenta el tiempo total de entrega pero sólo considerando los días que entrega el transportista, por lo que en el caso de este ejemplo no considera los fines de semana.
+Pero el `lastDeliveryDay` se calcula como días naturales (días consecutivos), que es `today date + delivery time + maximum number of days` configurado para la entrega programada, como cuenta días consecutivos, considerará los fines de semana.
+
+Para que el sistema arme la ventana de entrega disponible, comparará si:
+
+    lastDeliveryDay > estimateDate : TRUE
+
+
+Y sólo si cumple esta condición creará la ventana de entrega.
+
+Pero con un tránsito total `timecost` excesivamente alto, hay una inconsistencia con la variable `estimateDate` y `lastDeliveryDay`, la condición devolverá `false`, y por tanto no se creará ninguna ventana de entrega.
+
+
+
+##
+
+## Simulación
+
+
+
+Cambie la configuración de envío a la siguiente:
+
+- Días y horas de proceso de almacén con 100 días;
+- Timecost en el fichero de tarifas de la hoja de cálculo con 1 día;
+- Eliminar fines de semana y festivos para la configuración de la política de envío;
+- Programar la entrega de lunes a viernes de 0h a 23:59h;
+- Tiempo máximo de entrega en la configuración de Programar entrega para 5 días;
+
+Esta configuración dará como resultado `lastDeliveryDay=10/05/2024` y `estimateDate=14/06/2024`;
+Y por lo tanto la condición será falsa:
+
+    10/05/2024 > 14/06/2024 : FALSE
+
+
+y no se creará ninguna ventana de entrega;
+
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md b/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
new file mode 100644
index 000000000..9b1a5dd0b
--- /dev/null
+++ b/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
@@ -0,0 +1,55 @@
+---
+title: 'El descuento nominal basado en la fórmula no funciona como se esperaba con las operaciones de resta'
+id: 50YsRuiICJNdH2e1QqYnn0
+status: DRAFT
+createdAt: 2023-08-24T13:30:36.935Z
+updatedAt: 2023-08-28T20:44:40.744Z
+publishedAt: 
+firstPublishedAt: 2023-08-24T13:30:37.863Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: el-descuento-nominal-basado-en-la-formula-no-funciona-como-se-esperaba-con-las-operaciones-de-resta
+locale: es
+kiStatus: Backlog
+internalReference: 886980
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al crear una promoción utilizando Descuento nominal basado en fórmula, el comerciante puede utilizar las siguientes operaciones de acuerdo con esta documentación: https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV
+ ![](https://vtexhelp.zendesk.com/attachments/token/1EhryrRZDsiXZ31kaSV2VcegW/?name=image.png)
+
+Sin embargo, al utilizar la operación de resta, el valor del descuento se sustituye por el valor total del pedido.
+
+
+##
+
+## Simulación
+
+
+Cree una promoción utilizando el descuento nominal basado en la fórmula y utilice una operación de resta, así
+ ![](https://vtexhelp.zendesk.com/attachments/token/3wIEiPGtF9oX2daeQ3F3AZqCk/?name=image.png)
+
+Comprueba en la caja que el descuento se sustituye por lo que debería ser el valor total del pedido:
+ ![](https://vtexhelp.zendesk.com/attachments/token/r2bWktL4reNcVnnhSqr4hT0FC/?name=image.png)
+
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md b/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
index 1f6a7ad89..f705f564a 100644
--- a/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
+++ b/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
@@ -3,8 +3,8 @@ title: 'El descuento nominal no se distribuye entre todos los artículos de la c
 id: gt1qMqN71YkaHuZgk9Ibs
 status: PUBLISHED
 createdAt: 2023-01-25T17:33:59.274Z
-updatedAt: 2023-01-25T17:33:59.996Z
-publishedAt: 2023-01-25T17:33:59.996Z
+updatedAt: 2024-07-20T02:22:10.021Z
+publishedAt: 2024-07-20T02:22:10.021Z
 firstPublishedAt: 2023-01-25T17:33:59.996Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -24,14 +24,13 @@ internalReference: 334130
 
 
 
-El descuento nominal no se está distribuyendo entre todos los artículos de la cesta.
+El Descuento Nominal de las promociones no se está distribuyendo entre todos los artículos del carrito.
 
-Este escenario sólo está ocurriendo en algunas cuentas.
+Este escenario está ocurriendo sólo en algunas cuentas.
 
-La tienda tiene una promoción nominal y el descuento sólo se está aplicando en un artículo del carrito, no distribuyendo proporcionalmente el descuento a todos los artículos como se supone que debería.
+La tienda tiene una promoción nominal y el descuento sólo se está aplicando a un artículo del carrito, no distribuyendo proporcionalmente el descuento a todos los artículos como se supone que debería.
 
 
-##
 
 ## Simulación
 
@@ -39,7 +38,7 @@ La tienda tiene una promoción nominal y el descuento sólo se está aplicando e
 
 
 1. Crear una promoción periódica con un descuento nominal;
-2. Cree un enlace de carro en el que se aplique la promoción;
+2. Crear un enlace al carrito donde se aplique la promoción;
 3. 3. Compruebe que el descuento se aplica íntegramente a un solo artículo en lugar de distribuirse entre todos los artículos.
 
 PD: Esto no ocurre siempre y con todas las cuentas.
@@ -49,5 +48,9 @@ PD: Esto no ocurre siempre y con todas las cuentas.
 ## Workaround
 
 
-No hay solución.
+Para mitigar este problema, puede utilizar la API Crear o Actualizar cupón para aumentar el campo `maxItemsPerClient`. Esto permite que el cupón se aplique a tantos SKU como permita este campo.
+
+
+
+
 
diff --git a/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md b/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
new file mode 100644
index 000000000..c2e7fee98
--- /dev/null
+++ b/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
@@ -0,0 +1,67 @@
+---
+title: 'Descuento nominal + Más por menos + Dividir por segundo artículo --> descuento incorrecto'
+id: 4hxRWUY6P8aDR9T1KHd3Yf
+status: PUBLISHED
+createdAt: 2024-07-25T16:48:26.511Z
+updatedAt: 2024-07-25T16:48:27.336Z
+publishedAt: 2024-07-25T16:48:27.336Z
+firstPublishedAt: 2024-07-25T16:48:27.336Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: descuento-nominal-mas-por-menos-dividir-por-segundo-articulo-descuento-incorrecto
+locale: es
+kiStatus: Backlog
+internalReference: 1071119
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al configurar una promoción de descuento nominal que se acumula con la promoción más por menos, cuando hay un descuento en la promoción más por menos sólo para 1 de 2 artículos, se produce un descuento incorrecto en el artículo del segundo pedido debido a la división de la caja.
+
+Por ejemplo, digamos que hay un 50% de descuento sólo para 1 de 2 artículos en un compra y gana y luego un -$300 de descuento, con ambas promociones acumulándose.
+
+Digamos que el artículo cuesta $200 y se insertan 2.
+
+Los descuentos **esperados** serían:
+
+Artículo (1) ---> -$100 + -$100 --> el 2º artículo es sólo $100 porque no hay "espacio" adicional para ser reducido de su precio.
+Artículo (2) --> -$200 ---> el resto del descuento para componer el total -$300
+
+Sin embargo, el escenario que **actualmente ocurre** es:
+
+Artículo (1) ---> -$100 + -$100 --> el segundo artículo es sólo $100 porque no hay "espacio" adicional para ser reducido de su precio.
+Artículo (2) --> **-$100 ---> el precio del 1er artículo, a partir de la división se replica**.
+
+Esto sólo ocurre si los artículos rebajados son 2+ unidades del mismo SKU y el "combo" de promociones especificado arriba.
+
+
+##
+
+## Simulación
+
+
+1 - crear una promoción porcentual
+2 - crear una promoción "comprar y ganar" que ofrezca descuento sólo para el 2º artículo
+3 - introducir 2 unidades de dicho artículo en el carrito
+
+OBS: la combinación de precios y descuentos debe ser tal que el "importe a descontar" del precio del 1er artículo no sea suficiente para componer el 50%+ del valor nominal del descuento
+
+
+
+## Workaround
+
+
+-
+
+
+
+
+
+
diff --git a/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md b/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
new file mode 100644
index 000000000..cf3e34a46
--- /dev/null
+++ b/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
@@ -0,0 +1,49 @@
+---
+title: 'No se puede abrir la SKU adecuada en PDP en una nueva pestaña'
+id: 26kt6vcKm02TMXDFQPA3ES
+status: PUBLISHED
+createdAt: 2023-07-31T21:20:31.271Z
+updatedAt: 2023-07-31T21:20:31.900Z
+publishedAt: 2023-07-31T21:20:31.900Z
+firstPublishedAt: 2023-07-31T21:20:31.900Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: no-se-puede-abrir-la-sku-adecuada-en-pdp-en-una-nueva-pestana
+locale: es
+kiStatus: Backlog
+internalReference: 871848
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza la función detach para dividir productos por alguna especificación SKU y se intenta abrir una nueva pestaña de PLP a PDP, no reconoce el parámetro de propiedad que se pasa a la URL para seleccionar el SKU correcto, sólo muestra el SKU adecuado al abrir en la misma pestaña.
+
+
+##
+
+## Simulación
+
+
+Para ello, necesitará tener una tienda que utilice la función de desvinculación del módulo de búsqueda inteligentehttps://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE
+
+- Vaya a cualquier página de PLP
+- Para el efecto visual, debe seleccionar cualquier SKU separada que no sea la SKU por defecto de PDP y abrirla en una nueva pestaña
+- Observará que la SKU que ha seleccionado no es la misma SKU que se muestra.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md b/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
index 6e6e618f2..a39e5711d 100644
--- a/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
+++ b/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
@@ -3,8 +3,8 @@ title: 'No es posible cargar nuevos medios/documentos en un espacio de trabajo d
 id: zhDX1xoXAifH9tYroXCFn
 status: PUBLISHED
 createdAt: 2023-04-24T20:01:04.211Z
-updatedAt: 2023-05-08T18:00:19.246Z
-publishedAt: 2023-05-08T18:00:19.246Z
+updatedAt: 2024-06-28T16:07:27.058Z
+publishedAt: 2024-06-28T16:07:27.058Z
 firstPublishedAt: 2023-04-24T20:01:04.779Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: no-es-posible-cargar-nuevos-mediosdocumentos-en-un-espacio-de-trabajo-de-desarrollo-cuando-la-entidad-tiene-mas-de-10k-documentos
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 795940
 ---
 
diff --git a/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md b/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
new file mode 100644
index 000000000..741ba9eeb
--- /dev/null
+++ b/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
@@ -0,0 +1,49 @@
+---
+title: 'El informe Notifícame genera un archivo dañado cuando no se encuentran SKUs'
+id: 4UXSRdwdh7TTqGvQ3HrBX4
+status: PUBLISHED
+createdAt: 2023-12-20T20:13:33.873Z
+updatedAt: 2023-12-20T20:13:34.707Z
+publishedAt: 2023-12-20T20:13:34.707Z
+firstPublishedAt: 2023-12-20T20:13:34.707Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-informe-notificame-genera-un-archivo-danado-cuando-no-se-encuentran-skus
+locale: es
+kiStatus: Backlog
+internalReference: 956264
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el informe 'Notifícame' no tiene SKUs, al intentar exportarlo se generará un archivo corrupto a Excel
+
+
+##
+
+## Simulación
+
+
+
+- Compruebe si el informe "Notificarme" está vacío
+- En caso afirmativo, haga clic en "Exportar a Excel
+- Descargue el archivo y compruebe si es posible abrirlo
+
+
+
+## Workaround
+
+
+Abra el archivo en otro programa o rellene el informe para poder exportarlo
+
+
+
+
+
diff --git a/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md b/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
index cc0838998..bcfcf5bef 100644
--- a/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
+++ b/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
@@ -3,8 +3,8 @@ title: 'El número de itens en el filtro de precios no se corresponde con el nú
 id: 1FyjpY1K6JfAQ0gRIuXyuO
 status: PUBLISHED
 createdAt: 2022-03-16T19:37:02.943Z
-updatedAt: 2022-11-25T22:12:33.361Z
-publishedAt: 2022-11-25T22:12:33.361Z
+updatedAt: 2024-02-16T20:24:00.118Z
+publishedAt: 2024-02-16T20:24:00.118Z
 firstPublishedAt: 2022-03-16T19:37:03.370Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: el-numero-de-itens-en-el-filtro-de-precios-no-se-corresponde-con-el-numero-correcto
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 371405
 ---
 
diff --git a/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md b/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
new file mode 100644
index 000000000..ae1310c46
--- /dev/null
+++ b/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
@@ -0,0 +1,51 @@
+---
+title: 'El componente Omnishipping no rellenará el campo PickupReceiver cuando el cliente informe por primera vez de una dirección para la entrega'
+id: 0vYgYP5NTflaVEBiAchhL
+status: DRAFT
+createdAt: 2023-12-01T14:11:00.160Z
+updatedAt: 2023-12-04T13:28:38.612Z
+publishedAt: 
+firstPublishedAt: 2023-12-01T14:11:00.848Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-componente-omnishipping-no-rellenara-el-campo-pickupreceiver-cuando-el-cliente-informe-por-primera-vez-de-una-direccion-para-la-entrega
+locale: es
+kiStatus: Backlog
+internalReference: 945896
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Cuando se utiliza el componente **Omnishipping** en el pago, el campo **Recogida** se muestra en blanco cuando debería tener el nombre introducido por el cliente en el paso de Identificación. Esto sólo ocurre si el cliente primero informa una dirección para la entrega y luego hace clic en la pestaña Recogida para seleccionar un punto de recogida.
+
+
+
+## Simulación
+
+
+
+1. Instalar el componente Omnishipping en una tienda sin personalizaciones en el checkout.
+2. Iniciar un proceso de compra y rellenar los datos de identificación
+3. Seleccione una dirección para la entrega pero luego haga clic en la opción de recogida
+4. El campo RecogidaReceptor aparecerá en blanco
+
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md b/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
new file mode 100644
index 000000000..fe4fd1baa
--- /dev/null
+++ b/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
@@ -0,0 +1,46 @@
+---
+title: 'En Mi Cuenta la edición de la dirección con Información Roja de Campo Obligatorio aparece incluso después de rellenar hasta guardar los datos'
+id: 1QWktgA1c4iyONb8sFCaIh
+status: PUBLISHED
+createdAt: 2023-07-28T20:52:37.170Z
+updatedAt: 2023-07-28T20:52:38.569Z
+publishedAt: 2023-07-28T20:52:38.569Z
+firstPublishedAt: 2023-07-28T20:52:38.569Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: en-mi-cuenta-la-edicion-de-la-direccion-con-informacion-roja-de-campo-obligatorio-aparece-incluso-despues-de-rellenar-hasta-guardar-los-datos
+locale: es
+kiStatus: Backlog
+internalReference: 870891
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En la página de edición de Mi dirección de Mi cuenta, aunque se rellene la dirección aparece la información roja de "Campo obligatorio" hasta que se guardan los datos.
+
+
+##
+
+## Simulación
+
+
+Voy a la página de mi dirección, elijo la opción de edición y después de rellenar la dirección el mensaje de información sigue apareciendo hasta que guarde los datos.
+
+
+
+## Workaround
+
+
+No hay solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md b/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
index d90fbcf26..5194e658c 100644
--- a/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
+++ b/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
@@ -3,8 +3,8 @@ title: 'En la página Order Placed, el DataLayer sólo captura la información d
 id: 5cTy3dCZ6x7FNMKvBbc9s8
 status: PUBLISHED
 createdAt: 2023-01-04T21:06:17.111Z
-updatedAt: 2023-01-10T19:08:17.450Z
-publishedAt: 2023-01-10T19:08:17.450Z
+updatedAt: 2024-02-16T20:23:30.519Z
+publishedAt: 2024-02-16T20:23:30.519Z
 firstPublishedAt: 2023-01-04T21:14:00.744Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: authors_84
 tag: Order Management
 slug: en-la-pagina-order-placed-el-datalayer-solo-captura-la-informacion-del
 locale: es
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 727339
 ---
 
diff --git a/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md b/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
new file mode 100644
index 000000000..88b83571a
--- /dev/null
+++ b/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
@@ -0,0 +1,55 @@
+---
+title: 'O=OrderByPriceASC (o OrderByPriceDESC) podría dar lugar a un pedido erróneo'
+id: 2XCplZQutilKeD2bNnjYDx
+status: PUBLISHED
+createdAt: 2022-05-20T15:48:15.215Z
+updatedAt: 2024-06-21T11:29:11.233Z
+publishedAt: 2024-06-21T11:29:11.233Z
+firstPublishedAt: 2022-05-20T15:48:16.089Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: oorderbypriceasc-o-orderbypricedesc-podria-dar-lugar-a-un-pedido-erroneo
+locale: es
+kiStatus: Backlog
+internalReference: 582861
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+**O=OrderByPriceASC** (o **OrderByPriceDESC**) puede utilizar una política incorrecta para ordenar los precios. Además, como el precio indexado sólo tiene un decimal, no se tendrá en cuenta el segundo decimal del precio.
+
+Además, en la ordenación no se tienen en cuenta los precios de los vendedores no regionalizados. En consecuencia, las tiendas regionalizadas del Portal no pueden utilizar el parámetro **pedirPorPrecio**.
+
+
+
+## Simulación
+
+
+
+- Introducir más de un precio en el producto. Ej: dos precios de lista diferentes en vendedores diferentes.
+- Poner ordenación de la página por precio (ej: O=OrderByPriceASC)
+- Ver que la clasificación no está en el orden de los precios que se muestran
+o
+
+- Buscar dos productos con precios decimales. Ej: precio 1 = 14.04 y precio 2 = 14.01
+- Poner la página ordenando por precio (ej: O=OrderByPriceASC)
+- Ver que la ordenación no es en el orden de los precios que se muestran
+
+
+
+## Workaround
+
+
+Ninguna en el Portal. Sin embargo, la cuenta puede cambiar a Búsqueda Inteligente.
+
+
+
+
+
diff --git a/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md b/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md
new file mode 100644
index 000000000..8aacd1191
--- /dev/null
+++ b/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md
@@ -0,0 +1,49 @@
+---
+title: 'El gancho para abrir/cerrar modales afecta a todos los modales de la página'
+id: l1G3HN5Y3LxYVzuMnhjkL
+status: PUBLISHED
+createdAt: 2024-05-31T19:16:13.601Z
+updatedAt: 2024-06-04T12:14:19.271Z
+publishedAt: 2024-06-04T12:14:19.271Z
+firstPublishedAt: 2024-05-31T19:16:14.596Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: el-gancho-para-abrircerrar-modales-afecta-a-todos-los-modales-de-la-pagina
+locale: es
+kiStatus: Backlog
+internalReference: 1042165
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al abrir/cerrar un modal la acción afecta a todos los modales de la página
+
+
+##
+
+## Simulación
+
+
+Prueba a abrir un modal en una página con más de uno
+Busca los otros modales, verás que el comportamiento será el mismo
+
+
+
+## Workaround
+
+
+Puedes usar un estado personalizado en lugar del nativo. Aquí tienes un ejemplo:
+
+     import { useState } from "react";import { Modal, ModalHeader, ModalBody, LinkButton, Icon } from "@faststore/ui";import ModalContent from "./ModalContent";import section from "./styles.module.scss";const ModalSelector = () => {const [showModal, setShowModal] = useState(false);const ToggleModal = () => {setShowModal((showModal) => !showModal);};return (} > Entrega {showModal && ( <> )});};export default ModalSelector;
+
+
+
+
+
diff --git a/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md b/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
new file mode 100644
index 000000000..9314224a6
--- /dev/null
+++ b/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
@@ -0,0 +1,41 @@
+---
+title: 'Las operaciones no pueden realizarse correctamente debido a que el campo documentType es nulo.'
+id: 5cZWkKc0ZXnMZCw4bvXJjA
+status: PUBLISHED
+createdAt: 2023-05-11T17:33:04.077Z
+updatedAt: 2023-12-06T15:21:16.013Z
+publishedAt: 2023-12-06T15:21:16.013Z
+firstPublishedAt: 2023-05-11T17:33:04.511Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: las-operaciones-no-pueden-realizarse-correctamente-debido-a-que-el-campo-documenttype-es-nulo
+locale: es
+kiStatus: Backlog
+internalReference: 697107
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Este problema se produce cuando un cliente utiliza información de una empresa para completar un pedido.
+Si se utiliza el nombre de la empresa para completar la transacción, el campo `documentType` queda sin rellenar, causando problemas con la aprobación del pago.
+
+
+
+## Workaround
+
+
+
+En el primer caso, es posible utilizar una API interna para omitir el paso de análisis antifraude.
+A pesar de estar totalmente desaconsejado, es una operación posible.
+
diff --git a/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md b/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md
index 3e7ff0287..93160023e 100644
--- a/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md
+++ b/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md
@@ -3,8 +3,8 @@ title: 'Volver a pedir desde el historial de pedidos B2B no funciona'
 id: 2kT6UJsivYRgEaYpeRpEWa
 status: PUBLISHED
 createdAt: 2023-05-05T13:16:44.403Z
-updatedAt: 2023-05-08T18:34:38.873Z
-publishedAt: 2023-05-08T18:34:38.873Z
+updatedAt: 2023-09-19T21:46:58.308Z
+publishedAt: 2023-09-19T21:46:58.308Z
 firstPublishedAt: 2023-05-05T13:16:45.530Z
 contentType: knownIssue
 productTeam: B2B
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: B2B
 slug: volver-a-pedir-desde-el-historial-de-pedidos-b2b-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 819920
 ---
 
diff --git a/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md b/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md
new file mode 100644
index 000000000..80bbb4437
--- /dev/null
+++ b/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md
@@ -0,0 +1,53 @@
+---
+title: 'Autorización de pedido inferior a 100 va con la corriente'
+id: 51vxznnbek6mtVtQgKEW9d
+status: PUBLISHED
+createdAt: 2024-02-16T13:44:05.199Z
+updatedAt: 2024-02-16T13:44:05.932Z
+publishedAt: 2024-02-16T13:44:05.932Z
+firstPublishedAt: 2024-02-16T13:44:05.932Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: autorizacion-de-pedido-inferior-a-100-va-con-la-corriente
+locale: es
+kiStatus: Backlog
+internalReference: 983031
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Identificamos que cuando el sistema de Autorización de ordenes (OrderAuth) se configura con el valor "lessThan: 100", en el "Rules-list.CreateDoEffect" , no puede entender que es menor o igual al 100%, solo que es menor al 100% y cuando la orden tiene un descuento del 100%, el sistema autoriza la orden para que siga el flujo normal.
+
+
+##
+
+## Simulación
+
+
+Para simular es necesario configurar orderAuth:
+Acceso: https://.myvtex.com/admin/order-auth
+Configurar divergencia de precios > insertar los siguientes valores en la regla:
+Rules-list.denyEffect :0 a 60%
+
+Reglas-lista.CreateDoEffect: 61 a 100%
+
+Al configurar la regla "Rules-list.CreateDoEffect" al 100%, no puede entender que sea menor o igual, sólo que es menor y por tanto autoriza a que la petición siga el flujo normal cuando es igual al 100%.
+
+
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/es/order-card-info-causing-confusing-on-status.md b/docs/known-issues/es/order-card-info-causing-confusing-on-status.md
index 7943be7bc..b0bb58cb1 100644
--- a/docs/known-issues/es/order-card-info-causing-confusing-on-status.md
+++ b/docs/known-issues/es/order-card-info-causing-confusing-on-status.md
@@ -3,8 +3,8 @@ title: 'La información de la tarjeta de pedido causa confusión en el Estado'
 id: 2f0nEqccswuyWEcwdqiRZS
 status: PUBLISHED
 createdAt: 2022-08-18T19:04:12.824Z
-updatedAt: 2022-11-25T22:01:43.687Z
-publishedAt: 2022-11-25T22:01:43.687Z
+updatedAt: 2024-02-16T20:24:07.700Z
+publishedAt: 2024-02-16T20:24:07.700Z
 firstPublishedAt: 2022-08-18T19:04:13.465Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: la-informacion-de-la-tarjeta-de-pedido-causa-confusion-en-el-estado
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 619778
 ---
 
diff --git a/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md b/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
index d66060a29..37f10a8b1 100644
--- a/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
+++ b/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
@@ -3,8 +3,8 @@ title: 'La creación de la orden falló debido a la divergencia de precios en la
 id: 31fiMPNRULuOH73AhlzU5K
 status: PUBLISHED
 createdAt: 2022-02-03T15:24:07.791Z
-updatedAt: 2022-11-25T21:52:40.751Z
-publishedAt: 2022-11-25T21:52:40.751Z
+updatedAt: 2024-02-16T20:26:40.128Z
+publishedAt: 2024-02-16T20:26:40.128Z
 firstPublishedAt: 2022-02-03T15:24:08.353Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-creacion-de-la-orden-fallo-debido-a-la-divergencia-de-precios-en-la-capa-de-cumplimiento
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 512393
 ---
 
diff --git a/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md b/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
index dd401165b..360af0124 100644
--- a/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
+++ b/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
@@ -3,8 +3,8 @@ title: 'El informe de exportación de pedidos no funciona correctamente debido a
 id: 3dVPZEs544WyPDBNzTesWx
 status: PUBLISHED
 createdAt: 2023-04-06T20:22:47.489Z
-updatedAt: 2023-04-06T20:22:48.141Z
-publishedAt: 2023-04-06T20:22:48.141Z
+updatedAt: 2024-06-28T17:44:15.662Z
+publishedAt: 2024-06-28T17:44:15.662Z
 firstPublishedAt: 2023-04-06T20:22:48.141Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: el-informe-de-exportacion-de-pedidos-no-funciona-correctamente-debido-al-doble-espacio-en-el-nombre-de-la-promocion
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 786216
 ---
 
@@ -23,8 +23,7 @@ internalReference: 786216
 </div>
 
 
-Para la promoción de pedidos, no es correcto el uso de doble espacio o carácter especial en los nombres, esto puede romper el filtro o la falta de algunos pedidos en el informe de exportación de pedidos.
-Nombre en el array "ratesAndBenefitsData".
+El sistema de reporte de pedidos actualmente no puede construir un archivo a partir de filtros de promoción que contengan doble espacio en sus nombres, al intentar construir el reporte el sistema genera un error y no se realiza la exportación, dando como resultado el mensaje "_Exportación completada. Se enviaron 0 pedidos a su correo electrónico"_.
 
 
 ##
@@ -32,17 +31,19 @@ Nombre en el array "ratesAndBenefitsData".
 ## Simulación
 
 
-Crear un pedido usando una promoción con un nombre incorrecto, por ejemplo con doble espacio en el nombre.
-Después de esto, vaya a la gestión de pedidos y ejecute un filtro con esta promoción como condición.
-En ese momento se puede ver el pedido en la lista de pedidos filtrado, pero al elegir el informe de exportación no aparecerá el pedido con la promoción con doble espacio.
 
+Crear pedido utilizando alguna promoción cuyo nombre contenga espacios dobles;
 
+Después de eso, vaya a la gestión de pedidos y ejecute un filtro con esta promoción como condición.
+
+En este punto, la interfaz de usuario de OMS mostrará normalmente una lista de pedidos con la condición elegida, pero al seleccionar exportar pedidos la interfaz de usuario devolverá el siguiente mensaje "_Exportación completada. Se han enviado 0 pedidos a su correo electrónico_".
 
-## Workaround
 
 
-No hay ninguna solución disponible.
+## Workaround
+
 
+Filtre los pedidos en la UI por otro parámetro, por ejemplo, fecha, forma de pago, etc., luego exporte los pedidos y fíltrelos por promoción directamente en el archivo Excel generado por el sistema.
 
 
 
diff --git a/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
new file mode 100644
index 000000000..5eba8fb2f
--- /dev/null
+++ b/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -0,0 +1,58 @@
+---
+title: 'El filtro de pedidos no funciona correctamente debido a la presencia de comillas dobles (") en el nombre de la promoción o del SKU.'
+id: 4Qm0akQTQXR8sSbkTDiBL7
+status: PUBLISHED
+createdAt: 2024-06-06T15:42:19.747Z
+updatedAt: 2024-06-06T15:42:20.627Z
+publishedAt: 2024-06-06T15:42:20.627Z
+firstPublishedAt: 2024-06-06T15:42:20.627Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: el-filtro-de-pedidos-no-funciona-correctamente-debido-a-la-presencia-de-comillas-dobles-en-el-nombre-de-la-promocion-o-del-sku
+locale: es
+kiStatus: Backlog
+internalReference: 1045623
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El sistema de filtrado de pedidos actualmente no devuelve los pedidos con promociones que contienen comillas dobles `"` en sus nombres, esto también se aplica al nombre SKU.
+
+
+##
+
+## Simulación
+
+
+Para reproducir este escenario, siga los siguientes pasos.
+
+1. Cree una promoción/sku con comillas dobles `"` en el nombre;
+Ejemplo: Nombre de la promoción como `10% de descuento usando o cupom "DIAGEO" (8)`.
+2. Crear un pedido de prueba:
+
+  1. En el entorno de la tienda (storefront), seleccione un artículo y añádalo al carrito;
+  2. Asegúrate de que se aplica la promoción;
+  3. Vaya a la caja y realice el pedido.
+3. Vaya a **Pedidos > Gestión de pedidos**;
+4. Haga clic en `Todos los pedidos`;
+5. Utiliza el **filtro** para seleccionar la promoción que has añadido;
+6. Observe que no se encuentran pedidos con el filtro seleccionado, y el mensaje devuelto en la interfaz de usuario es: `Nenhum pedido encontrado. Limpe seus filtros e tente uma pesquisa diferente.`
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md b/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md
new file mode 100644
index 000000000..fd6b67749
--- /dev/null
+++ b/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md
@@ -0,0 +1,46 @@
+---
+title: 'El pedido no notificado al transportista deja incompleto el código de barras de la etiqueta'
+id: 2QjxFv2Ul2wKCdnYtrlF0T
+status: PUBLISHED
+createdAt: 2023-08-01T16:55:39.774Z
+updatedAt: 2023-09-18T22:52:54.573Z
+publishedAt: 2023-09-18T22:52:54.573Z
+firstPublishedAt: 2023-08-01T16:55:40.545Z
+contentType: knownIssue
+productTeam: VTEX Shipping Network (VTEX Log)
+author: 2mXZkbi0oi061KicTExNjo
+tag: VTEX Shipping Network (VTEX Log)
+slug: el-pedido-no-notificado-al-transportista-deja-incompleto-el-codigo-de-barras-de-la-etiqueta
+locale: es
+kiStatus: Backlog
+internalReference: 872530
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los clientes que utilizan transportistas asociados a la Red de Envíos, al solicitar la emisión de etiquetas en Listo para enviar, pueden obtener el archivo con el código de barras incompleto, lo que puede impedir que se envíe el paquete.
+
+
+##
+
+## Simulación
+
+
+No se ha podido reproducir, sólo verificar comprobando las etiquetas enviadas por los clientes con el código de barras incompleto y confirmando vía API que el paquete no ha sido notificado.
+
+
+
+## Workaround
+
+
+Notificando de nuevo el pedido manualmente, se asegura que se notifica al transportista y el código de barras está completo y se puede utilizar la etiqueta.
+
+
+
+
+
diff --git a/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md b/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md
index ef3c9f324..a5b8fd95c 100644
--- a/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md
+++ b/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md
@@ -1,10 +1,10 @@
 ---
 title: 'La devolución parcial del pedido provocó el reembolso total de la transacción'
 id: 5cPpyvV4t6swxDPrEmuzrn
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-04-04T21:20:39.334Z
-updatedAt: 2022-11-25T22:03:29.435Z
-publishedAt: 2022-11-25T22:03:29.435Z
+updatedAt: 2024-05-28T19:09:23.158Z
+publishedAt: 
 firstPublishedAt: 2022-04-04T21:20:40.180Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md b/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
new file mode 100644
index 000000000..4bacdbf04
--- /dev/null
+++ b/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
@@ -0,0 +1,48 @@
+---
+title: 'La función de sustitución de pedidos no funciona cuando el carro sustituido y el pedido original tienen el mismo valor.'
+id: 7eHiC34Pgsr1XcfIVHl7Sc
+status: PUBLISHED
+createdAt: 2023-07-21T14:49:31.057Z
+updatedAt: 2023-12-18T20:17:32.757Z
+publishedAt: 2023-12-18T20:17:32.757Z
+firstPublishedAt: 2023-07-21T14:49:31.682Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-funcion-de-sustitucion-de-pedidos-no-funciona-cuando-el-carro-sustituido-y-el-pedido-original-tienen-el-mismo-valor
+locale: es
+kiStatus: Fixed
+internalReference: 866622
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La característica de reemplazo de pedidos no funciona cuando el carrito reemplazado tiene el mismo valor que el pedido original, y el sistema de pago es "Reutilizar Pago".
+
+
+##
+
+## Simulación
+
+
+
+- Active la función de sustitución de pedidos;
+- Complete un pedido y cambie algo, por ejemplo, de talla pequeña a grande;
+- Asegúrese de que el carrito reemplazado tiene el mismo valor que el pedido original;
+- En el paso de pago, seleccione "Reutilizar pago".
+
+
+
+## Workaround
+
+
+Seleccione un método de pago distinto de "Reutilizar pago". La transacción anterior será cancelada y reembolsada; se creará una nueva.
+
+
+
diff --git a/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md b/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
new file mode 100644
index 000000000..58d6d9891
--- /dev/null
+++ b/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
@@ -0,0 +1,54 @@
+---
+title: 'Incoherencia en el informe de pedido cuando el campo tid está duplicado en el campo connectorResponses de la API de detalles de pago GET.'
+id: 4xXSp2RMyHMeHpEUXgmpAZ
+status: PUBLISHED
+createdAt: 2023-09-06T21:18:05.941Z
+updatedAt: 2023-09-06T21:18:06.733Z
+publishedAt: 2023-09-06T21:18:06.733Z
+firstPublishedAt: 2023-09-06T21:18:06.733Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: incoherencia-en-el-informe-de-pedido-cuando-el-campo-tid-esta-duplicado-en-el-campo-connectorresponses-de-la-api-de-detalles-de-pago-get
+locale: es
+kiStatus: Backlog
+internalReference: 895664
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los conectores de esa lista necesitan guardar más campos para el conector que trabaja con "Venda direta" - Sales app. En concreto, para los conectores de la siguiente lista, y sólo para ellos, todo el contenido de la carga útil debe dirigirse al campo "`connectorResponses`". Esto resulta en una duplicación del campo "`tid`", que ya existe en el "`connectorResponses`". Aunque esta duplicación no plantea ningún problema en cuanto al ciclo de vida de la transacción, sí crea una incoherencia a la hora de generar informes desde la página de pedido.
+
+
+- PagarMeV3
+- PagarMeV3Stg
+- Adyen V3
+
+
+##
+
+## Simulación
+
+
+
+1. Accede a la página de pedidos del administrador.
+2. Generar el informe del pedido.
+3. Busque la columna `tId` donde se realizaron los pedidos utilizando uno de estos conectores
+
+
+
+## Workaround
+
+
+Utilice la ruta /payment o la API de pedidos GET para recuperar estos datos
+
+
+
+
+
diff --git a/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md b/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
new file mode 100644
index 000000000..679bb6b59
--- /dev/null
+++ b/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
@@ -0,0 +1,58 @@
+---
+title: 'Pedido bloqueado en el estado del vendedor cancellation-request-denied-ffm'
+id: 5hBeTQMKmo5C63QRAOSvT2
+status: PUBLISHED
+createdAt: 2024-03-22T17:50:37.946Z
+updatedAt: 2024-03-22T17:50:38.822Z
+publishedAt: 2024-03-22T17:50:38.822Z
+firstPublishedAt: 2024-03-22T17:50:38.822Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: pedido-bloqueado-en-el-estado-del-vendedor-cancellationrequestdeniedffm
+locale: es
+kiStatus: Backlog
+internalReference: 1004978
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Hemos identificado que algunos vendedores, en la estructura de vendedores y marketplace de VTEX, cuando solicitan la cancelación, luego deniegan esta cancelación a través de la UI, o llaman a la API "cancellation-request-denied-ffm", esto es como si denegaran la propia solicitud de cancelación, por alguna razón, la solicitud de denegar la cancelación se solapa con la solicitud de cancelar.
+Como resultado, el pedido se queda atascado en el vendedor, en el estado "cancellation-request-denied-ffm".
+Y en algunos casos, el propio mercado intenta solicitar la cancelación, como resultado, el mercado también está atascado en el estado "solicitud de cancelación".
+Por otro lado, tenemos el caso en el que el marketplace no recibe esta notificación de cancelación y continúa con su pedido hasta el estado "Facturado".
+En todos los casos, no podemos cambiar el estado de estos pedidos.
+
+
+##
+
+## Simulación
+
+
+1- Crear un pedido, con marca blanca del vendedor;
+2- En el pedido del vendedor, adelantar el estado a "tramitación";
+3- Todavía en el vendedor, solicitar la anulación del pedido;
+4- En el pedido del vendedor, tendremos el mensaje, "acepta o rechaza la cancelación", pulsa en la opción rechazar del vendedor o utiliza la API, verás que el pedido del vendedor pasará al estado "cancelación-solicitud-denegada-ffm".
+5- En el pedido del Mercado, haga clic en cancelar;
+6- El pedido del Marketplace se atascará en "Pedido-Cancelar";
+
+Puede ocurrir que el pedido del Marketplace continúe con el pedido y pase a factura, cuando envíe la factura.
+
+
+
+## Workaround
+
+
+Esto no es una solución, sino una orientación a las cuentas, una vez que el vendedor solicita la cancelación, no rechazar la solicitud en sí.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md b/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
new file mode 100644
index 000000000..ada93e1d4
--- /dev/null
+++ b/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
@@ -0,0 +1,51 @@
+---
+title: 'Pedido bloqueado en estado Pendiente de pago por falta de notificación de pago aprobado'
+id: 1yM3alrrYhrpdZhBPLslZC
+status: PUBLISHED
+createdAt: 2024-05-24T15:04:47.795Z
+updatedAt: 2024-05-24T15:04:48.820Z
+publishedAt: 2024-05-24T15:04:48.820Z
+firstPublishedAt: 2024-05-24T15:04:48.820Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: pedido-bloqueado-en-estado-pendiente-de-pago-por-falta-de-notificacion-de-pago-aprobado
+locale: es
+kiStatus: Backlog
+internalReference: 1031035
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+En el estado "Pago pendiente", se espera que se envíe una notificación de pago al módulo Pedidos. Durante este periodo, pueden producirse algunos problemas con el procesamiento de eventos.
+La cola de mensajes proporciona un protocolo de comunicación asíncrono, en el que los eventos se colocan en una cola para ser consumidos en un momento predeterminado en el futuro.
+Este KI se refiere explícitamente a los escenarios con conectores PPP y no pretende agotar todas las posibilidades de problemas de procesamiento de eventos que puedan ocurrir.
+
+
+##
+
+## Simulación
+
+
+
+No hay forma de simular este comportamiento.
+
+
+
+## Workaround
+
+
+
+Póngase en contacto con nuestro equipo de soporte para volver a procesar manualmente el evento.
+
+
+
+
+
diff --git a/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md b/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
new file mode 100644
index 000000000..7f2c78270
--- /dev/null
+++ b/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
@@ -0,0 +1,53 @@
+---
+title: 'El pedido con intereses tiene problemas al intentar devolver todos los artículos y reembolsar el pago total'
+id: 2J5XD9jjQfZWMVg0yYMzUa
+status: PUBLISHED
+createdAt: 2023-09-18T20:53:08.156Z
+updatedAt: 2023-09-18T20:53:08.813Z
+publishedAt: 2023-09-18T20:53:08.813Z
+firstPublishedAt: 2023-09-18T20:53:08.813Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: el-pedido-con-intereses-tiene-problemas-al-intentar-devolver-todos-los-articulos-y-reembolsar-el-pago-total
+locale: es
+kiStatus: Backlog
+internalReference: 376077
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La plataforma impide la devolución de importes superiores al total del pedido. Esto se convierte en un problema para la devolución de pedidos en los que la forma de pago conlleva intereses.
+Además del **importe total**, los pedidos tienen un **importe facturado** que, por motivos legales, no puede incluir los intereses aplicados en función de la forma de pago.
+En consecuencia, la plataforma devuelve un error con estado 400 cuando se intenta emitir una factura de devolución con un importe superior al facturado previamente.
+
+###
+
+###
+
+## Simulación
+
+
+
+1. En su tienda, cree un pedido con intereses aplicados al pago;
+2. Intenta realizar una devolución del importe total pagado a través de la API con la solicitud de envío de factura;
+3. Observe que la API devuelve un error con el estado 400, indicando que no es posible emitir una factura de tipo INPUT con un importe superior al importe total del pedido.
+
+###
+
+###
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md b/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
index 5a09c7ee3..22ed0021e 100644
--- a/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
+++ b/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
@@ -3,8 +3,8 @@ title: 'Pedido sin suscripción Creado y sin correo electrónico de Nuevos Pedid
 id: 747TGL3sy1mmM1LnVkEjuO
 status: PUBLISHED
 createdAt: 2022-02-21T20:54:35.174Z
-updatedAt: 2022-11-25T22:03:15.831Z
-publishedAt: 2022-11-25T22:03:15.831Z
+updatedAt: 2024-02-16T20:23:42.061Z
+publishedAt: 2024-02-16T20:23:42.061Z
 firstPublishedAt: 2022-05-18T18:43:19.767Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: pedido-sin-suscripcion-creado-y-sin-correo-electronico-de-nuevos-pedidos-en-casos-relacionados-con-el-metodo-de-pago-utilizando-conectores-como-payment-app-o-redirect
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 529143
 ---
 
diff --git a/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md b/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md
index b9f889dc2..91bf1ac44 100644
--- a/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md
+++ b/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md
@@ -1,18 +1,18 @@
 ---
-title: 'Pedido con estado de anulado pero el pago sigue autorizado'
+title: 'Pedido con estado cancelado pero el pago sigue autorizado'
 id: 19WmIjIbAQmJ19AOC4q56N
 status: PUBLISHED
 createdAt: 2022-05-11T12:49:23.081Z
-updatedAt: 2022-11-25T21:51:23.997Z
-publishedAt: 2022-11-25T21:51:23.997Z
+updatedAt: 2024-06-28T17:45:57.362Z
+publishedAt: 2024-06-28T17:45:57.362Z
 firstPublishedAt: 2022-05-11T12:49:23.599Z
 contentType: knownIssue
-productTeam: Checkout
+productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
-tag: Checkout
-slug: pedido-con-estado-de-anulado-pero-el-pago-sigue-autorizado
+tag: Order Management
+slug: pedido-con-estado-cancelado-pero-el-pago-sigue-autorizado
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 420019
 ---
 
@@ -23,14 +23,15 @@ internalReference: 420019
 </div>
 
 
-En algunos casos en los que el pedido está incompleto o se cancela cuando hay algún fallo de comunicación con la Pasarela, el pago permanece autorizado y/o aprobado, no entrando en el flujo de cancelación y no se devuelve automáticamente el importe pagado. Además, los correos electrónicos transaccionales pueden ser enviados accidentalmente, lo que también permite el pago de recibos bancarios, ya que la URL irá con él.
+En algunos casos en los que el pedido queda incompleto o anulado al producirse algún fallo de comunicación con la Pasarela, el pago queda autorizado y/o aprobado, no entrando en el flujo de anulación y no devolviéndose automáticamente el importe pagado. Además, se pueden enviar accidentalmente correos electrónicos transaccionales, que también permiten el pago de recibos bancarios, ya que la URL irá con él.
 
 
+##
 
 ## Simulación
 
 
-No hay forma de simularlo. Pero tenemos algunos casos en los que esto ha ocurrido antes.
+No hay manera de simular. Pero tenemos algunos casos que esto sucedió antes.
 
 
 
diff --git a/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md b/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
index 21cdbb0b8..624bc84e7 100644
--- a/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
+++ b/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
@@ -1,18 +1,18 @@
 ---
-title: 'La API de OrderForm impide la selección del método de envío para el mismo artículo en diferentes vendedores.'
+title: 'La API de OrderForm impide la selección del método de envío para el mismo artículo con diferentes vendedores.'
 id: 4dEfq7lNqTLF7SFIOaRsc2
 status: PUBLISHED
 createdAt: 2023-01-27T21:56:04.190Z
-updatedAt: 2023-01-27T22:03:21.165Z
-publishedAt: 2023-01-27T22:03:21.165Z
+updatedAt: 2023-07-05T14:33:51.370Z
+publishedAt: 2023-07-05T14:33:51.370Z
 firstPublishedAt: 2023-01-27T21:56:04.914Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: la-api-de-orderform-impide-la-seleccion-del-metodo-de-envio-para-el-mismo-articulo-en-diferentes-vendedores
+slug: la-api-de-orderform-impide-la-seleccion-del-metodo-de-envio-para-el-mismo-articulo-con-diferentes-vendedores
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 742139
 ---
 
diff --git a/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md b/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
index bc8a794c2..38f00029e 100644
--- a/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
+++ b/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
@@ -1,16 +1,16 @@
 ---
-title: "orderForm (Chk API) suggesting invalid scheduled delivery that can't be used"
+title: 'orderForm (Chk API) sugiere una entrega programada no válida que no se puede utilizar'
 id: 7e2bSJSJa938QCrOHkRibZ
 status: PUBLISHED
 createdAt: 2022-01-24T20:20:11.732Z
-updatedAt: 2023-03-21T19:26:09.280Z
-publishedAt: 2023-03-21T19:26:09.280Z
+updatedAt: 2023-12-01T14:08:09.892Z
+publishedAt: 2023-12-01T14:08:09.892Z
 firstPublishedAt: 2023-03-21T19:26:09.280Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
-tag: 
-slug: orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used
+tag: Checkout
+slug: orderform-chk-api-sugiere-una-entrega-programada-no-valida-que-no-se-puede-utilizar
 locale: es
 kiStatus: Backlog
 internalReference: 298665
@@ -18,28 +18,38 @@ internalReference: 298665
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
-Cuando un carrito/pedido tiene múltiples artículos con entrega programada, las opciones programadas que tienen el mismo ID (por lo tanto, considerado el mismo método de envío) necesitan tener las mismas ventanas de entrega entre ellas. Si no hay intersección, el método de envío será descartado para algunos artículos.
 
-El problema es que, en algunos flujos, como la API "GET orderForm", este comportamiento de filtrado no se aplica, ofreciendo una entrega programada no válida (sin intersección). En otros flujos, como en la "simulación orderForm" o al seleccionar de hecho el método de envío, la opción ofrecida será correctamente filtrada/eliminada.
+Cuando un carrito/pedido tiene varios artículos con entrega programada del mismo vendedor, las opciones programadas con el mismo ID (consideradas el mismo método de envío) necesitan tener las mismas ventanas de entrega entre ellas. Si no hay intersección, el método de envío será descartado para algunos artículos.
 
-Efecto secundario: la aplicación Chk UI intentará utilizar/simular la opción no válida y puede quedarse bloqueada en un **bucle de peticiones**, ya que el método de envío está disponible en un primer momento, pero no se puede utilizar en un segundo momento, y la aplicación UI vuelve a intentar el primer paso mientras revisa las opciones disponibles en el orderForm.
+El problema es que, en algunos flujos, como la API "GET orderForm", este comportamiento de filtrado no se aplica, ofreciendo una entrega programada no válida (sin intersección). En otros flujos, como en la "simulación orderForm" o al seleccionar el método de envío, la opción ofrecida se filtrará/eliminará correctamente.
 
+Efecto secundario: el Chk UI intentará usar/simular la opción inválida y puede quedarse bloqueado en un **bucle de peticiones** porque el método de envío está disponible en un primer momento pero no puede usarse en un segundo momento, y el UI vuelve a intentar el primer paso mientras revisa las opciones disponibles en el orderForm.
+
+
+##
 
 ## Simulación
 
-- tener dos políticas de envío diferentes (transportistas) con el mismo "tipo de carga" (que define el "slaId")
-- ambos programados, pero con una ventana de entrega diferente entre ellos
-- tener un artículo para cada política de envío
-- incluir ambos artículos en el carrito y simular el envío
 
-En este momento, la interfaz de usuario puede quedar bloqueada en un bucle debido a la divergencia entre el "GET orderForm" y la "simulación de orderForm".
+
+- Desde el mismo vendedor, configure dos políticas de envío diferentes (transportistas) con el mismo "tipo de flete" (que define el "slaId");
+- Ambas con entrega programada, pero con una ventana de entrega diferente entre ellas;
+- Añadir 2 artículos al carrito, un artículo de cada política de envío.
+
+La interfaz de usuario puede quedar bloqueada en un bucle debido a la divergencia entre el "GET orderForm" y la "simulación de orderForm".
+
 
 
 ## Workaround
 
-Es necesario fijar la ventana de entrega entre los métodos de envío que tienen el mismo ID (para tener las mismas ventanas de entrega), o tratarlos como diferentes métodos de envío, por lo que utilizan diferentes IDs.
+
+Es necesario fijar la ventana de entrega entre los métodos de envío con el mismo ID (para tener las mismas ventanas de entrega), o tratarlos como diferentes métodos de envío, por lo que utilizar diferentes IDs.
+
+
+
+
 
diff --git a/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md b/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md
index dc87939db..8cea78482 100644
--- a/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md
+++ b/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md
@@ -3,8 +3,8 @@ title: 'OrderForm no devuelve los datos del cliente incluso para credenciales au
 id: JcjDusU8YP0kerWXC6LXK
 status: PUBLISHED
 createdAt: 2022-05-19T16:25:28.039Z
-updatedAt: 2023-02-01T21:29:33.875Z
-publishedAt: 2023-02-01T21:29:33.875Z
+updatedAt: 2023-09-27T20:39:27.746Z
+publishedAt: 2023-09-27T20:39:27.746Z
 firstPublishedAt: 2022-05-19T16:25:28.427Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: orderform-no-devuelve-los-datos-del-cliente-incluso-para-credenciales-autorizadas
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 582070
 ---
 
diff --git a/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md b/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md
new file mode 100644
index 000000000..9cc9eccf7
--- /dev/null
+++ b/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md
@@ -0,0 +1,53 @@
+---
+title: 'OrderForm no se actualiza después de realizar el pedido'
+id: 4Xkk9LA95PRXbKxFYy189f
+status: PUBLISHED
+createdAt: 2024-06-27T15:22:19.922Z
+updatedAt: 2024-06-28T11:47:47.958Z
+publishedAt: 2024-06-28T11:47:47.958Z
+firstPublishedAt: 2024-06-27T15:22:20.951Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: orderform-no-se-actualiza-despues-de-realizar-el-pedido
+locale: es
+kiStatus: Backlog
+internalReference: 1056870
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Después de realizar un pedido, el orderFormId no se actualiza, lo que provoca que los artículos permanezcan visibles en el carrito. Este problema afecta a las cuentas FastStore
+Este problema puede estar relacionado con el retraso en la actualización del orderFormId debido a cambios relacionados con la cookie de pago.
+
+Tras la respuesta gatewayCallback, lo esperado sería una nueva cookie orderFormId para el usuario. Este escenario se rompe porque el dominio de la nueva cookie no coincide con el dominio de la cookie anterior del usuario (debido al dominio seguro).
+
+
+##
+
+## Simulación
+
+
+
+- Completar un pedido en una cuenta Faststore
+- Volver a la página de inicio
+- Los artículos que acaba de comprar permanecerán en su cesta
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md b/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md
index 2dc051b98..fc2e94f3e 100644
--- a/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md
+++ b/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md
@@ -20,7 +20,7 @@ internalReference:
 
 Actualmente los horarios de entrega para una entrega programada están fuera de orden, o en orden decreciente. Para una mejor legibilidad, se espera que esta información se ordene de forma creciente.
 
-![image](https://images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md b/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md
index e9860ced0..4d8e8ac4b 100644
--- a/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md
+++ b/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md
@@ -3,8 +3,8 @@ title: 'La ordenación de los grupos de especificaciones desde la categoría ra
 id: 5iuLxVdAuK70VMYGts7CzJ
 status: PUBLISHED
 createdAt: 2022-08-09T00:46:23.102Z
-updatedAt: 2022-11-25T21:43:59.468Z
-publishedAt: 2022-11-25T21:43:59.468Z
+updatedAt: 2024-02-16T20:25:08.305Z
+publishedAt: 2024-02-16T20:25:08.305Z
 firstPublishedAt: 2022-08-09T00:46:23.684Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-ordenacion-de-los-grupos-de-especificaciones-desde-la-categoria-raiz-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 634129
 ---
 
diff --git a/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md b/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
index 6406e189b..7edff1441 100644
--- a/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
+++ b/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
@@ -3,8 +3,8 @@ title: 'Pedidos facturados en VTEX pero que no actualizan la factura en Netshoes
 id: 1SrJBQj0iTYh4AdvmJQqIg
 status: PUBLISHED
 createdAt: 2022-05-11T19:45:30.831Z
-updatedAt: 2022-11-25T21:56:22.896Z
-publishedAt: 2022-11-25T21:56:22.896Z
+updatedAt: 2024-02-16T20:25:46.426Z
+publishedAt: 2024-02-16T20:25:46.426Z
 firstPublishedAt: 2022-05-11T19:45:31.187Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: pedidos-facturados-en-vtex-pero-que-no-actualizan-la-factura-en-netshoes
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 577219
 ---
 
diff --git a/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md b/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
new file mode 100644
index 000000000..e3a1c1faf
--- /dev/null
+++ b/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
@@ -0,0 +1,54 @@
+---
+title: 'Cálculo de la facturación de pedidos utilizando el valor de la factura de entrada en la validación de la factura de salida'
+id: kEjeBKkJMpUDR0JdX6fZv
+status: PUBLISHED
+createdAt: 2023-11-06T11:39:27.169Z
+updatedAt: 2023-11-09T20:47:52.250Z
+publishedAt: 2023-11-09T20:47:52.250Z
+firstPublishedAt: 2023-11-06T11:39:28.035Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: calculo-de-la-facturacion-de-pedidos-utilizando-el-valor-de-la-factura-de-entrada-en-la-validacion-de-la-factura-de-salida
+locale: es
+kiStatus: Fixed
+internalReference: 930491
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Durante el proceso de envío de facturas, es posible que el usuario envíe facturas de salida y de entrada, pero si en un pedido se realizan dos facturas parciales, una de salida y otra de entrada, el sistema suma estos valores para validar si el pedido puede recibir una nueva factura, imposibilitando que los pedidos cuyo artículo fue facturado y luego devuelto no tengan facturado su valor total.
+
+Esto se debe a que actualmente la API de Pedidos realiza una validación de valores para determinar si debe permitir que se realice una nueva factura de salida para el pedido, pero el cálculo está considerando la suma de todas las facturas independientemente de su tipo (entrada o salida), haciendo que el sistema entienda que no hay más valor a facturar.
+
+
+##
+
+## Simulación
+
+
+
+1- Crear un pedido con dos unidades de la misma SKU
+2- Factura sólo una de estas unidades
+3- Realiza ahora una nueva factura de entrada por la unidad facturada en el paso anterior.
+4- Ahora intenta facturar la unidad restante del pedido.
+5- En este punto recibirás un mensaje genérico en la interfaz de usuario indicando que no es posible facturar el artículo.
+
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md b/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md
new file mode 100644
index 000000000..2ef15524c
--- /dev/null
+++ b/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md
@@ -0,0 +1,55 @@
+---
+title: 'Pedidos con asteriscos en la dirección y el perfil'
+id: 6AaZ4p042LZwvfeKIqavjw
+status: PUBLISHED
+createdAt: 2023-08-25T17:03:49.755Z
+updatedAt: 2024-06-06T20:16:16.607Z
+publishedAt: 2024-06-06T20:16:16.607Z
+firstPublishedAt: 2023-08-25T17:03:50.594Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: pedidos-con-asteriscos-en-la-direccion-y-el-perfil
+locale: es
+kiStatus: Backlog
+internalReference: 360783
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Hay pedidos en los que la `invoiceAddress`, `shippingAddress` o `clientProfileData` se están enviando como `masked` en lugar de la dirección real. Este comportamiento se produce cuando un usuario completa la compra con un formulario de pedido que contiene datos enmascarados que están "encadenados". Como se trata de campos de cadena, los datos del pedido se rellenan con la máscara "***".
+
+Así pues, el fallo radica en que nuestra API para realizar pedidos permite objetos con caracteres especiales en estos campos.
+
+
+##
+
+## Simulación
+
+
+
+1. Añade algunos productos a tu cesta;
+2. Durante el proceso de pago, introduzca una dirección de facturación válida e inicie sesión en su cuenta;
+3. Abandonar el carrito o salir del sitio web sin completar la compra;
+4. Utilizar nuestra API para insertar un archivo adjunto y poner una dirección con "***" en algunos campos, como el del barrio;
+5. Realizar un pedido utilizando este mismo carrito;
+6. Tenga en cuenta que el pedido tendrá los datos de envío con estos caracteres especiales.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md b/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
index 3557cfc8c..bcbdbe01c 100644
--- a/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
+++ b/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
@@ -1,18 +1,18 @@
 ---
-title: 'Los pedidos con artículos en la matriz MarketplaceItems no se abren en la Nueva UI Admin'
+title: 'Los pedidos con artículos en el array MarketplaceItems no se abren en New UI Admin'
 id: 3tj9AKklBHm4tCKYgrfDi5
 status: PUBLISHED
 createdAt: 2022-09-13T03:06:57.141Z
-updatedAt: 2022-11-25T22:01:26.839Z
-publishedAt: 2022-11-25T22:01:26.839Z
+updatedAt: 2023-09-28T15:01:19.205Z
+publishedAt: 2023-09-28T15:01:19.205Z
 firstPublishedAt: 2022-09-13T03:06:57.675Z
 contentType: knownIssue
 productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
-slug: los-pedidos-con-articulos-en-la-matriz-marketplaceitems-no-se-abren-en-la-nueva-ui-admin
+slug: los-pedidos-con-articulos-en-el-array-marketplaceitems-no-se-abren-en-new-ui-admin
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 656821
 ---
 
@@ -23,27 +23,24 @@ internalReference: 656821
 </div>
 
 
-Algunos pedidos tienen el array "marketplace Items" lleno de más artículos que el array "items" del pedido json. Esta configuración es normal y se refiere por ejemplo a la "lista de regalos de boda".
-Pero la nueva interfaz de usuario no está preparada para manejar este tipo de pedidos con artículos en "marketplace Items" y rompe la página con un mensaje de error:
 
+Algunos pedidos tienen el array "marketplace Items" lleno con más artículos que el array "items" del pedido json. Esta configuración es normal y se refiere por ejemplo a "lista de regalos de boda".
+Pero la Nueva UI no está preparada para manejar este tipo de pedidos con items en "marketplace Items" y rompe la página con un mensaje de error:
 
 
-
-
-"Lo siento, algo salió mal de nuestro lado.
-
+"Lo sentimos, algo ha ido mal por nuestra parte.
 Por favor, inténtelo de nuevo o actualice la página.
-
 Volver a la lista"
 
 
 
+##
 
 ## Simulación
 
 
-Cree un pedido con el catálogo utilizando el array "marketplace Items", después de eso puede intentar ver el pedido en la UI admin. La UI se romperá y mostrará un mensaje de error.
 
+Cree un pedido con el catálogo usando el array "marketplace Items", después puede intentar ver el pedido en la UI admin. La interfaz de usuario se romperá y mostrará un mensaje de error.
 
 
 
@@ -52,3 +49,7 @@ Cree un pedido con el catálogo utilizando el array "marketplace Items", despué
 
 Utilice la antigua interfaz de usuario para abrir esa orden.
 
+
+
+
+
diff --git a/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md b/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md
index 45e2028b1..996b9d711 100644
--- a/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md
+++ b/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md
@@ -1,18 +1,18 @@
 ---
-title: 'Pedidos sin invoiceAddress creados a través de la UI nativa'
+title: 'Pedidos sin invoiceAddress creados a través de la interfaz de usuario nativa'
 id: 1XjNZhcTJ5rZJP4w3kJtcW
 status: PUBLISHED
 createdAt: 2022-01-24T20:21:07.893Z
-updatedAt: 2022-11-25T21:52:06.721Z
-publishedAt: 2022-11-25T21:52:06.721Z
+updatedAt: 2023-12-19T21:34:15.743Z
+publishedAt: 2023-12-19T21:34:15.743Z
 firstPublishedAt: 2022-06-27T19:49:05.878Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: pedidos-sin-invoiceaddress-creados-a-traves-de-la-ui-nativa
+slug: pedidos-sin-invoiceaddress-creados-a-traves-de-la-interfaz-de-usuario-nativa
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 306140
 ---
 
@@ -23,10 +23,6 @@ internalReference: 306140
 </div>
 
 
-En algunos casos todavía es posible crear pedidos sin `invoiceAddress` a través de la interfaz de usuario de la caja.
-La dirección de la factura debe ser obligatoria en la UI de todas las tiendas que tengan la funcionalidad activada.
-
-
 
 ## Simulación
 
@@ -34,17 +30,17 @@ La dirección de la factura debe ser obligatoria en la UI de todas las tiendas q
 Hasta ahora los pasos conocidos para reproducir el escenario son:
 
 
-1. Acceder a la tienda sin estar conectado/identificado
+1. Acceder a la tienda sin estar logueado/identificado.
 2. Poner un producto en el carrito
-3. En el carrito haga clic en cerrar el pedido
-4. En la pantalla de correo electrónico poner un correo de un comprador existente - el usuario probablemente será dirigido al paso de pago
+3. En el carrito haz clic en Cerrar pedido
+4. En la pantalla de correo electrónico poner un correo electrónico de un comprador existente - el usuario probablemente será dirigido al paso de pago
 5. Haga clic para editar el paso de entrega y seleccione "retirada"
 6. No rellene la dirección de la nota
 7. Haga clic para editar los "Datos personales"
 8. Se le pedirá que inicie sesión.
-9. Después de iniciar la sesión, en el paso de edición de "Datos personales" aparecerá el botón para ir directamente al pago, aunque no se haya rellenado la dirección de la factura.
+9. Después de iniciar sesión, en el paso de edición de "Datos personales" aparecerá el botón para ir directamente al pago, aunque no se haya rellenado la dirección de facturación.
 
-Además de lo anterior, el comportamiento se puede observar cuando el usuario está en la etapa de envío y al recargar la página, se le lleva automáticamente al pago sin llenar los datos de la factura.
+Además de lo anterior, el comportamiento se puede observar cuando el usuario se encuentra en la etapa de envío y al recargar la página, es llevado automáticamente al pago sin llenar los datos de la Factura.
 Otro escenario que induce el comportamiento es cambiar entre la lista de direcciones previamente registradas y una nueva dirección, lo que permite al usuario proceder al pago sin rellenar el código postal (de una nueva dirección).
 
 
@@ -52,5 +48,9 @@ Otro escenario que induce el comportamiento es cambiar entre la lista de direcci
 ## Workaround
 
 
-No hay ninguna solución conocida para evitar el escenario de la raíz.
+No se conoce ninguna solución para evitar el escenario raíz.
+
+
+
+
 
diff --git a/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md b/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md
index 528746f53..7059d4eb0 100644
--- a/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md
+++ b/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md
@@ -3,8 +3,8 @@ title: 'No funciona la ordenación de imágenes al subir una nueva versión'
 id: 2Oq65YHU6uIQpQ5g8ZpjTE
 status: PUBLISHED
 createdAt: 2023-01-25T15:08:43.356Z
-updatedAt: 2023-01-25T15:08:43.873Z
-publishedAt: 2023-01-25T15:08:43.873Z
+updatedAt: 2024-02-16T20:26:48.206Z
+publishedAt: 2024-02-16T20:26:48.206Z
 firstPublishedAt: 2023-01-25T15:08:43.873Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: no-funciona-la-ordenacion-de-imagenes-al-subir-una-nueva-version
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 739814
 ---
 
diff --git a/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
new file mode 100644
index 000000000..72359e985
--- /dev/null
+++ b/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
@@ -0,0 +1,50 @@
+---
+title: 'Una regex de Elo obsoleta nos hace identificar erróneamente algunos BINs'
+id: 45vx88VCQ0yZynkVxGqSq8
+status: PUBLISHED
+createdAt: 2024-04-10T17:25:57.376Z
+updatedAt: 2024-04-10T17:25:58.309Z
+publishedAt: 2024-04-10T17:25:58.309Z
+firstPublishedAt: 2024-04-10T17:25:58.309Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: una-regex-de-elo-obsoleta-nos-hace-identificar-erroneamente-algunos-bins
+locale: es
+kiStatus: Backlog
+internalReference: 1015043
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunos BIN no se identifican correctamente en la caja. La marca de la tarjeta se determina mediante una regex que podría quedar obsoleta, dando lugar a marcas de tarjeta no identificadas o mal identificadas.
+
+
+
+## Simulación
+
+
+
+1. Configure dos Condiciones de Pago una para Elo
+2. Añade un artículo al azar a tu carrito en la tienda y elige pagarlo con Tarjeta de Crédito
+3. Rellena el número de tarjeta con el BIN de Elo 65057000 y complétalo con números aleatorios
+4. Rellena el resto de la información de la tarjeta con datos falsos
+5. Como no se ha podido identificar la tarjeta, la caja pedirá confirmar el número de tarjeta y la marca de la tarjeta ya puede estar seleccionada como otra marca de tarjeta
+
+
+
+## Workaround
+
+
+
+El usuario debe cambiar la marca de tarjeta seleccionada en la caja haciendo clic en la marca correcta.
+
+
+
+
diff --git a/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md b/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
new file mode 100644
index 000000000..62d1ef073
--- /dev/null
+++ b/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
@@ -0,0 +1,52 @@
+---
+title: 'Información indexada desactualizada al realizar 2 cambios de producto seguidos.'
+id: 66aX8MktRogeUD9bbTo0vF
+status: PUBLISHED
+createdAt: 2023-09-26T14:44:57.146Z
+updatedAt: 2023-09-26T14:44:57.895Z
+publishedAt: 2023-09-26T14:44:57.895Z
+firstPublishedAt: 2023-09-26T14:44:57.895Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: informacion-indexada-desactualizada-al-realizar-2-cambios-de-producto-seguidos
+locale: es
+kiStatus: No Fix
+internalReference: 907428
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Para las tiendas que utilizan el motor de búsqueda heredado, si se realizan dos cambios en los datos de un producto en una sucesión rápida (es decir, has desactivado un producto y lo has reactivado justo después), y el último cambio devuelve la información del producto a lo que era justo antes, el estado de dicho artículo puede quedarse atascado en el primer cambio, ya que este último no se reconoce correctamente.
+
+Este problema no ocurre en las tiendas que utilizan la aplicación de búsqueda inteligente.
+
+
+##
+
+## Simulación
+
+
+1 - Obtenga un artículo activo en su tienda y desactívelo.
+2 - Justo después (< 5min), reactívalo.
+3 - Pasados unos minutos, comprueba tu producto: no se mostrará en la tienda, a pesar de estar configurado para ello. (en otras palabras, se quedó "atascado" en ese estado intermedio).
+
+
+
+## Workaround
+
+
+1 - Reindexe dichos productos después de 5+ min de experimentar el problema.
+2 - Utilice el motor de búsqueda inteligente, que no se enfrenta a este problema en absoluto.
+3 - Evite realizar más de dos cambios seguidos en un producto, ya que el último cambio revierte el anterior.
+
+
+
+
+
diff --git a/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
index 0948754de..b37832673 100644
--- a/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
@@ -1,16 +1,16 @@
 ---
-title: 'La regex de Mastercard no está actualizada, lo que hace que identifiquemos mal algunos BINs'
+title: 'La regex obsoleta de Mastercard Debit está provocando que identifiquemos erróneamente algunos BIN.'
 id: 5gx4dSY2P5gGE0JI661hGL
 status: PUBLISHED
 createdAt: 2022-08-20T00:03:11.640Z
-updatedAt: 2022-11-25T22:04:24.418Z
-publishedAt: 2022-11-25T22:04:24.418Z
+updatedAt: 2024-04-02T19:13:02.839Z
+publishedAt: 2024-04-02T19:13:02.839Z
 firstPublishedAt: 2022-08-20T00:03:12.490Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: la-regex-de-mastercard-no-esta-actualizada-lo-que-hace-que-identifiquemos-mal-algunos-bins
+slug: la-regex-obsoleta-de-mastercard-debit-esta-provocando-que-identifiquemos-erroneamente-algunos-bin
 locale: es
 kiStatus: Backlog
 internalReference: 642136
@@ -23,7 +23,7 @@ internalReference: 642136
 </div>
 
 
-Algunos BINs no están siendo identificados correctamente en la caja. La marca de la tarjeta está determinada por una regex que eventualmente puede estar desactualizada, causando que la marca de la tarjeta no sea identificada o sea identificada erróneamente.
+Algunos códigos BIN no se identifican correctamente en la caja. La marca de la tarjeta se determina mediante una regex que puede quedar obsoleta, provocando que la marca de la tarjeta no se identifique o se identifique erróneamente.
 
 
 
@@ -31,16 +31,19 @@ Algunos BINs no están siendo identificados correctamente en la caja. La marca d
 
 
 
-1. Configure dos condiciones de pago, una para Mastercard Débito
+1. Configure dos Condiciones de Pago una para Mastercard Débito
 2. Añade un artículo al azar al carrito en la tienda y elige pagarlo con tarjeta de débito
 3. Rellena el número de tarjeta con el BIN 551898 de Mastercard Débito y complétalo con números aleatorios
-4. Rellena el resto de la información de la tarjeta con datos falsos
-5. Como la tarjeta no ha podido ser identificada, la caja pedirá que se confirme el número de tarjeta y la marca de la tarjeta puede ser ya seleccionada como otra marca de tarjeta
+4. Rellena el resto de información de la tarjeta con datos falsos
+5. Como no se ha podido identificar la tarjeta, la caja pedirá que se confirme el número de tarjeta y la marca de la tarjeta ya puede estar seleccionada como otra marca de tarjeta
 
 
 
 ## Workaround
 
 
-No hay ninguna solución.
+No hay solución.
+
+
+
 
diff --git a/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md b/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md
new file mode 100644
index 000000000..928a7dcad
--- /dev/null
+++ b/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md
@@ -0,0 +1,53 @@
+---
+title: 'URL obsoleta en la interfaz de usuario de actualización de enlaces'
+id: 7bgh2LIJTFovgoz0TaBr5B
+status: PUBLISHED
+createdAt: 2023-08-30T20:04:23.301Z
+updatedAt: 2023-08-30T20:04:23.905Z
+publishedAt: 2023-08-30T20:04:23.905Z
+firstPublishedAt: 2023-08-30T20:04:23.905Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: url-obsoleta-en-la-interfaz-de-usuario-de-actualizacion-de-enlaces
+locale: es
+kiStatus: Backlog
+internalReference: 890791
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el comerciante es la actualización de una licitación de la interfaz de usuario es como sigue:
+ ![](https://vtexhelp.zendesk.com/attachments/token/UfffIyuM7K7isQMiPnAqRvSiW/?name=image.png)
+
+Al intentar ir al enlace del gestor de licencias, se les redirige a una página de SWW.
+
+
+##
+
+## Simulación
+
+
+
+1. Ir a la configuración de CMS (.../admin/a)
+2. Seleccione un sitio web y haga clic en actualizar vinculante
+3. Haga clic en el enlace Administrador de licencias
+4. Compruebe que aparece un SWW de error.
+
+
+
+## Workaround
+
+
+Utilice directamente la url: (.../admin/account/stores/)
+
+
+
+
+
diff --git a/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md b/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md
new file mode 100644
index 000000000..214b8db12
--- /dev/null
+++ b/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md
@@ -0,0 +1,47 @@
+---
+title: 'pageView se activa dos veces al acceder a Mi Cuenta'
+id: 2jV0cIVxNUhb170tBgBQo6
+status: PUBLISHED
+createdAt: 2023-07-03T16:33:09.076Z
+updatedAt: 2023-07-03T16:33:09.652Z
+publishedAt: 2023-07-03T16:33:09.652Z
+firstPublishedAt: 2023-07-03T16:33:09.652Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: pageview-se-activa-dos-veces-al-acceder-a-mi-cuenta
+locale: es
+kiStatus: Backlog
+internalReference: 854480
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al acceder a Mi Cuenta, el evento pageView se dispara dos veces, duplicando los datos en Analytics.
+
+
+##
+
+## Simulación
+
+
+
+- Configure la aplicación Google Tag Manager,
+- Acceda a Mi Cuenta;
+- Abra las Herramientas de Desarrollador del navegador y escriba "dataLayer" en la Consola; habrá dos eventos pageView.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md b/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
new file mode 100644
index 000000000..a286b3b87
--- /dev/null
+++ b/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
@@ -0,0 +1,63 @@
+---
+title: 'Los activadores de páginas en G4A se duplican en las páginas de búsqueda personalizadas.'
+id: 4hIwZ2v9bbyyZXrxoDglyx
+status: PUBLISHED
+createdAt: 2023-11-08T13:35:27.802Z
+updatedAt: 2024-02-19T18:43:16.271Z
+publishedAt: 2024-02-19T18:43:16.271Z
+firstPublishedAt: 2023-11-08T13:35:28.390Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: los-activadores-de-paginas-en-g4a-se-duplican-en-las-paginas-de-busqueda-personalizadas
+locale: es
+kiStatus: Backlog
+internalReference: 888042
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El evento pageView se muestra duplicado en dataLayer cuando en las páginas de búsqueda personalizada
+
+
+##
+
+## Simulación
+
+
+
+- Vaya a cualquier página de búsqueda personalizada
+- Abre la consola de tu navegador
+- Escribe dataLayer y comprueba el evento pageView
+
+El comportamiento esperado es el evento duplicado
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+## **Notas Internas**
+
+También encontré algo curioso en la página del departamento con pageView y page_view
+
+https://storetheme.vtex.com/apparel---accessories/
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/dXFuDY5Q9XhZ7hgIvA8m8ugJ3/?name=image.png)
+
+Pero, este problema específico es replicable en
+
+https://www.dzarm.com.br/outlet
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/EVakZYSBKtcrCQoNXBe92uAzQ/?name=image.png)
+
diff --git a/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md b/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md
index 8d353ad8b..c50328f49 100644
--- a/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md
+++ b/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md
@@ -3,8 +3,8 @@ title: 'Los enlaces de paginación en los resultados de la búsqueda no funciona
 id: 1w6h5MwZthKMM8rvqXZtQi
 status: PUBLISHED
 createdAt: 2022-11-02T14:01:35.650Z
-updatedAt: 2022-11-25T21:41:59.731Z
-publishedAt: 2022-11-25T21:41:59.731Z
+updatedAt: 2024-02-16T20:26:50.585Z
+publishedAt: 2024-02-16T20:26:50.585Z
 firstPublishedAt: 2022-11-02T14:01:36.502Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: los-enlaces-de-paginacion-en-los-resultados-de-la-busqueda-no-funcionan-en-las-paginas-de-la-lista-de-regalos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 481330
 ---
 
diff --git a/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md b/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
new file mode 100644
index 000000000..950ea64fc
--- /dev/null
+++ b/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
@@ -0,0 +1,53 @@
+---
+title: 'La paginación en la página de búsqueda no se reinicia al cambiar el contexto de búsqueda'
+id: 2lNL95NDZvO8NqxhJDrA6G
+status: PUBLISHED
+createdAt: 2023-07-06T19:54:29.289Z
+updatedAt: 2023-07-06T19:58:59.059Z
+publishedAt: 2023-07-06T19:58:59.059Z
+firstPublishedAt: 2023-07-06T19:54:29.968Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: la-paginacion-en-la-pagina-de-busqueda-no-se-reinicia-al-cambiar-el-contexto-de-busqueda
+locale: es
+kiStatus: Scheduled
+internalReference: 857392
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Mientras navegamos por una determinada página de un PLP, realizamos una búsqueda para mostrar más resultados, y cambiamos el contexto para navegar por un departamento diferente, el parámetro de paginación se mantendrá y el resultado de la búsqueda comenzará en la nueva categoría en la misma página en la que estábamos anteriormente.
+
+
+##
+
+## Simulación
+
+
+
+Siguiendo los pasos:
+
+
+- Vaya a: https://starter.vtex.app/computer---software
+- Haga clic en Cargar más productos (el parámetro de página en su URL va a cambiar)
+- Haga clic en un departamento diferente (por ejemplo Tecnología)
+- Compruebe que la página de tecnología se iniciará con la paginación que estaba anteriormente
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md b/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
index e2e2b127c..8b9307940 100644
--- a/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
+++ b/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
@@ -1,16 +1,16 @@
 ---
-title: 'Al pegar el código postal en el carrito de la vista previa del envío, a veces se obtiene un resultado nulo de la API'
+title: 'Al pegar el código postal en la vista previa del envío, a veces el resultado de la API es nulo.'
 id: 5Lq32htqC7M9xiqajfn7y7
 status: PUBLISHED
 createdAt: 2022-06-01T15:30:08.776Z
-updatedAt: 2022-11-25T21:53:05.306Z
-publishedAt: 2022-11-25T21:53:05.306Z
+updatedAt: 2024-05-21T13:03:32.812Z
+publishedAt: 2024-05-21T13:03:32.812Z
 firstPublishedAt: 2022-06-01T15:30:09.241Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: al-pegar-el-codigo-postal-en-el-carrito-de-la-vista-previa-del-envio-a-veces-se-obtiene-un-resultado-nulo-de-la-api
+slug: al-pegar-el-codigo-postal-en-la-vista-previa-del-envio-a-veces-el-resultado-de-la-api-es-nulo
 locale: es
 kiStatus: Backlog
 internalReference: 481878
@@ -23,16 +23,22 @@ internalReference: 481878
 </div>
 
 
-Después de introducir el código postal una vez en la vista previa del envío y elegir pegar el código postal de nuevo, a veces ocurre que se hace una petición nula a la API de código postal.
 
+## Simulación
 
 
 
-## Simulación
+- Vaya al carrito y añada un código postal;
+- Haga clic para cambiarlo y pegue otro código postal (o incluso el mismo);
+- Ir al paso de envío, y la dirección puede estar incompleta.
 
 
 
 ## Workaround
 
 
+El usuario tendrá que hacer clic en el botón "Calcular" o pulsar la tecla intro, en algunos casos escribiendo el código postal sin insertarlo.
+
+
+
 
diff --git a/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md b/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
new file mode 100644
index 000000000..76cba7845
--- /dev/null
+++ b/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
@@ -0,0 +1,49 @@
+---
+title: 'Condiciones de pago establecidas para procesar transacciones a plazos distintas de 1x están procesando transacciones como prepagadas en su totalidad'
+id: 2z9cDiCAovzKVFZO7RSqOD
+status: PUBLISHED
+createdAt: 2024-05-09T18:47:33.319Z
+updatedAt: 2024-05-09T18:47:34.221Z
+publishedAt: 2024-05-09T18:47:34.221Z
+firstPublishedAt: 2024-05-09T18:47:34.221Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: condiciones-de-pago-establecidas-para-procesar-transacciones-a-plazos-distintas-de-1x-estan-procesando-transacciones-como-prepagadas-en-su-totalidad
+locale: es
+kiStatus: Backlog
+internalReference: 1030652
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las condiciones de pago configuradas para procesar transacciones en un número de plazos distinto de 1x están pudiendo procesar pagos en 1x. El problema solo se produce en los pagos en los que el usuario ha optado por el prepago total.
+
+
+##
+
+## Simulación
+
+
+
+1. Establezca 3 condiciones de pago para tarjetas de crédito de cualquier marca: Condición de Pago A - con cuota en 1x, Condición de Pago B - con cuota en 2x, y Condición de Pago C - con cuota en 3x.
+2. Vaya a la página de Pago añadiendo cualquier artículo al carrito y proceda a la pantalla de pago. Elija pagar con tarjeta de crédito en 1x y complete la compra.
+3. Vaya al administrador y abra la transacción recién creada, haga clic en el botón "+ Información", y observe que el campo `AvailableRules` contendrá una lista con todos los IDs de Condiciones de Pago, Condición de Pago A, Condición de Pago B, y Condición de Pago C, como capaces de procesar la transacción en cuestión.
+
+
+
+## Workaround
+
+
+s posible establecer la Condición de Pago 1x como predeterminada, de forma que cuando haya un empate entre todas las Condiciones de Pago, la pasarela dará prioridad a la regla predeterminada.
+
+
+
+
+
diff --git a/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md b/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
index 79fbaa042..3285f1ab3 100644
--- a/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
+++ b/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
@@ -3,8 +3,8 @@ title: 'El método de pago de Marketplace coincide con el de SWL cuando se utili
 id: 4AHyl5z7ySagx6Myx0KqM7
 status: PUBLISHED
 createdAt: 2022-03-15T22:06:35.540Z
-updatedAt: 2022-11-25T22:12:10.257Z
-publishedAt: 2022-11-25T22:12:10.257Z
+updatedAt: 2024-02-16T20:29:19.824Z
+publishedAt: 2024-02-16T20:29:19.824Z
 firstPublishedAt: 2022-03-15T22:06:36.030Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: el-metodo-de-pago-de-marketplace-coincide-con-el-de-swl-cuando-se-utilizan-tipos-identicosids
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 402140
 ---
 
diff --git a/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md b/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
index 611cd41f6..bd85b45d9 100644
--- a/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
+++ b/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'Los métodos de pago mostrados en la caja difieren de las condiciones de
 id: 1cpVNspn5G6je4EZKzvCF9
 status: PUBLISHED
 createdAt: 2022-09-27T16:32:55.806Z
-updatedAt: 2023-04-10T15:14:18.718Z
-publishedAt: 2023-04-10T15:14:18.718Z
+updatedAt: 2024-06-07T21:23:28.431Z
+publishedAt: 2024-06-07T21:23:28.431Z
 firstPublishedAt: 2023-04-10T15:11:01.389Z
 contentType: knownIssue
 productTeam: Payments
@@ -36,8 +36,14 @@ Se trata de un problema intermitente y no se sabe cómo reproducir este comporta
 ## Simulación
 
 
+N/A
+
+
 
 ## Workaround
 
 
 
+1. Guardando de nuevo la regla.
+2. Reindexar todos los sistemas de pago en la caja a través de la API.
+
diff --git a/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md b/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
new file mode 100644
index 000000000..da6953427
--- /dev/null
+++ b/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
@@ -0,0 +1,66 @@
+---
+title: 'Los cambios en las condiciones de pago no se aplican en la configuración del pago B2B'
+id: 12PfZx6O0MIUSIFdpQdUdI
+status: PUBLISHED
+createdAt: 2024-04-18T19:07:22.743Z
+updatedAt: 2024-07-25T21:47:29.442Z
+publishedAt: 2024-07-25T21:47:29.442Z
+firstPublishedAt: 2024-04-18T19:07:23.644Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: los-cambios-en-las-condiciones-de-pago-no-se-aplican-en-la-configuracion-del-pago-b2b
+locale: es
+kiStatus: Fixed
+internalReference: 1019548
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La actualización de las condiciones de pago en la interfaz de usuario de detalles de la organización para una organización no se aplica a la configuración de pago B2B.
+
+Este comportamiento se debe a que la actualización solo se produce para la organización, pero la configuración de pago B2B utiliza información del centro de costes, que no se actualiza en la interfaz de detalles de la organización.
+
+
+
+## Simulación
+
+
+
+- Cree una organización;
+- En la interfaz de usuario de detalles de la organización, actualice las condiciones de pago;
+- Acceda al sitio web, monte un carrito y acceda a la caja; las Condiciones de pago seguirán siendo las mismas.
+
+
+
+## Workaround
+
+
+
+- Acceda a GraphQL IDE y seleccione vtex.b2b-organizations-graphql;
+- Utilice la siguiente consulta para obtener los detalles del centro de costes:
+
+    { getCostCenterById (id: "introduzca aquí el id del centro de costes"){ name addresses{ addressId addressType addressQuery postalCode country receiverName city state street number complement neighborhood geoCoordinates reference } phoneNumber businessDocument customFields{ name type value dropdownValues{ value label } useOnRegistration } stateRegistration paymentTerms{ id name } }}
+
+- Utilice la siguiente consulta para obtener las condiciones de pago de la organización:
+
+    { getOrganizationById(id: "introduzca aquí el id de la organización"){ paymentTerms{ id name } }}
+
+
+
+- Enviar una mutación para actualizar el centro de coste, añadiendo las condiciones de pago de la organización a la respuesta del centro de coste:
+
+    mutation updateCostCenter($id: ID!, $input: CostCenterInput!) { updateCostCenter( id: $id input: $input ){ id status }}{ "id": "", "input": { "nombre": "", "addresses": [{"addressId": "", "addressType": "", "addressQuery": "", "postalCode": "", "country": "", "receiverName": "", "city": "", "state": "", "street": "", "número": "", "complemento": null, "barrio": "", "geoCoordinates": [], "reference": null } ], "phoneNumber": "", "businessDocument": "", "customFields": [], "stateRegistration": "", "paymentTerms": [{ "id": "", "name": "" }, { "id": "", "name": "" }] }}
+
+
+
+
+
+
+
diff --git a/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
new file mode 100644
index 000000000..93ac8ea6e
--- /dev/null
+++ b/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -0,0 +1,51 @@
+---
+title: 'Las condiciones de pago configuradas en Configuración B2B no se asignan tras aprobar Organizaciones'
+id: 7pUMnYPWPHlhPzlWwTtWsL
+status: PUBLISHED
+createdAt: 2024-02-26T22:29:03.516Z
+updatedAt: 2024-02-26T22:29:04.387Z
+publishedAt: 2024-02-26T22:29:04.387Z
+firstPublishedAt: 2024-02-26T22:29:04.387Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: las-condiciones-de-pago-configuradas-en-configuracion-b2b-no-se-asignan-tras-aprobar-organizaciones
+locale: es
+kiStatus: Backlog
+internalReference: 989507
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las condiciones de pago configuradas en los Ajustes de Organizaciones B2B no se guardan en los Detalles de la Organización.
+
+
+##
+
+## Simulación
+
+
+
+- Configure las condiciones de pago por defecto en los Ajustes de Organizaciones B2B;
+- Crear una solicitud de organización;
+- Apruebe la solicitud de organización;
+- Compruebe los detalles de la Organización; no tendrá ninguna condición de pago asignada.
+
+
+
+## Workaround
+
+
+
+- Asigne las condiciones de pago a la organización a través del administrador;
+- Cree un disparador para el esquema de la entidad de la organización.
+
+
+
+
diff --git a/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md b/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
new file mode 100644
index 000000000..ef8cdd7b6
--- /dev/null
+++ b/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
@@ -0,0 +1,49 @@
+---
+title: 'PaymentSystems no se devuelven en orderForm cuando el precio de un carrito proviene exclusivamente de manualPrice'
+id: 3KPNFtPgEwshbv6WiGrqOF
+status: PUBLISHED
+createdAt: 2024-04-30T20:06:52.774Z
+updatedAt: 2024-04-30T20:06:53.756Z
+publishedAt: 2024-04-30T20:06:53.756Z
+firstPublishedAt: 2024-04-30T20:06:53.756Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: paymentsystems-no-se-devuelven-en-orderform-cuando-el-precio-de-un-carrito-proviene-exclusivamente-de-manualprice
+locale: es
+kiStatus: Backlog
+internalReference: 1025321
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el valor total de un carrito proviene exclusivamente de un precio manual, el `precio` de los artículos y el `precio` de la entrega son `0`, no se ofrecen otros sistemas de pago que la Tarjeta Regalo (si está activa).
+
+
+##
+
+## Simulación
+
+
+
+- Añadir un artículo con precio `0` y seleccionar una opción de entrega con precio `0`.
+- Añada un importe de "precio manual" al artículo.
+- Procede al paso de pago en la caja y no se devuelve ningún método de pago como disponible
+
+
+
+## Workaround
+
+
+No hay ninguna solución conocida aparte de añadir una cantidad al precio del artículo.
+
+
+
+
+
diff --git a/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md b/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
index 8ae9f1efd..c63f0bb20 100644
--- a/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
+++ b/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
@@ -3,8 +3,8 @@ title: 'El pago y la división de transacciones no funcionan en el mismo orden p
 id: 3rFyqzEnSwx2czwdlgDovU
 status: PUBLISHED
 createdAt: 2023-03-23T19:03:22.498Z
-updatedAt: 2023-03-27T12:27:57.714Z
-publishedAt: 2023-03-27T12:27:57.714Z
+updatedAt: 2024-02-16T20:25:26.525Z
+publishedAt: 2024-02-16T20:25:26.525Z
 firstPublishedAt: 2023-03-23T19:03:23.526Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-pago-y-la-division-de-transacciones-no-funcionan-en-el-mismo-orden-para-el-inventario-omnicanal-multinivel
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 777201
 ---
 
diff --git a/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md b/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md
index 03d65715c..7c8632f0f 100644
--- a/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md
+++ b/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md
@@ -3,8 +3,8 @@ title: 'PayPalPlus no respeta el importe mínimo de la cuota'
 id: 1IGzNPtXaaUsPkaq0qRgfK
 status: PUBLISHED
 createdAt: 2022-03-26T23:00:59.044Z
-updatedAt: 2022-11-25T22:06:43.067Z
-publishedAt: 2022-11-25T22:06:43.067Z
+updatedAt: 2024-02-16T20:25:30.693Z
+publishedAt: 2024-02-16T20:25:30.693Z
 firstPublishedAt: 2022-03-26T23:00:59.445Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: paypalplus-no-respeta-el-importe-minimo-de-la-cuota
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 370271
 ---
 
diff --git a/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md b/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md
index 2cff18222..33f42f896 100644
--- a/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md
+++ b/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md
@@ -3,8 +3,8 @@ title: 'Puntos de recogida descartados según la prioridad'
 id: 3bbsm8TELPBa0DpFtnlAGz
 status: PUBLISHED
 createdAt: 2021-09-29T14:38:08.930Z
-updatedAt: 2022-12-22T20:41:01.800Z
-publishedAt: 2022-12-22T20:41:01.800Z
+updatedAt: 2024-06-14T16:56:59.120Z
+publishedAt: 2024-06-14T16:56:59.120Z
 firstPublishedAt: 2021-09-29T14:49:34.443Z
 contentType: knownIssue
 productTeam: Post-purchase
@@ -13,7 +13,7 @@ tag: Logistics
 slug: puntos-de-recogida-descartados-segun-la-prioridad
 locale: es
 kiStatus: Backlog
-internalReference: 
+internalReference: 380545
 ---
 
 ## Sumario
@@ -39,7 +39,7 @@ To simulate the described scenario, at least two shipping policies serving the s
 4. See which pickup point has been selected;
 5. Check which pickup points were disregarded and note the message displayed.
 
-![KIpontoderetirada ES](https://images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/3a5671abaf682e8a0a52e73e5db41896/KIpontoderetirada_ES.png)
+![KIpontoderetirada ES](//images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/3a5671abaf682e8a0a52e73e5db41896/KIpontoderetirada_ES.png)
 
 The pickup point was disregarded because there was another shipping method already named as **SCS Mall**.
 
diff --git a/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md b/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
new file mode 100644
index 000000000..98427ff10
--- /dev/null
+++ b/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
@@ -0,0 +1,51 @@
+---
+title: 'El modo de punto de recogida no utiliza las coordenadas geográficas sin una clave de Google Maps.'
+id: 5aPNjLlsVVeyGe0Vywt0H9
+status: PUBLISHED
+createdAt: 2024-05-29T20:31:46.863Z
+updatedAt: 2024-07-03T15:56:30.595Z
+publishedAt: 2024-07-03T15:56:30.595Z
+firstPublishedAt: 2024-05-29T20:31:47.737Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-modo-de-punto-de-recogida-no-utiliza-las-coordenadas-geograficas-sin-una-clave-de-google-maps
+locale: es
+kiStatus: Backlog
+internalReference: 1041462
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al insertar un código postal en el modal del selector de punto de recogida, se activa una solicitud para obtener los ANS disponibles para esa ubicación. Si la cuenta no tiene una clave de API de Google Maps definida en su configuración de Pago, esta solicitud no incluirá información de geoCoordenadas. Esto puede provocar que no se muestren los puntos de recogida dentro de un rango válido, como aquellos cuyas tablas de carga se basan en polígonos.
+
+
+
+## Simulación
+
+
+
+1. Utiliza una tienda que no tenga definida una clave API de Google Maps.
+2. Configura un punto de recogida, y enlázalo a un transportista cuya tabla de carga esté basada en polígonos.
+3. Añade un producto al carrito.
+4. En la vista previa del envío, seleccione la opción de recogida e introduzca un código postal que tenga disponibilidad para el punto de recogida que ha creado.
+5. 5. Inspeccione la solicitud shippingData generada por esta acción. No contendrá geoCoordenadas.
+
+
+
+
+## Workaround
+
+
+Establezca una clave de API de Google Maps en la configuración de pago de la tienda.
+
+
+
+
+
diff --git a/docs/known-issues/es/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md b/docs/known-issues/es/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
index 4f166872f..8c57b82d2 100644
--- a/docs/known-issues/es/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
+++ b/docs/known-issues/es/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
@@ -3,7 +3,7 @@ title: 'Pickup point not visible for selection in shipping policy (UI)'
 id: 84BhCZGoAxxuu1eljw0Uh
 status: DRAFT
 createdAt: 2021-12-28T14:52:46.105Z
-updatedAt: 2022-01-05T21:09:34.658Z
+updatedAt: 2024-02-16T20:27:08.666Z
 publishedAt: 
 firstPublishedAt: 2021-12-28T22:18:57.306Z
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: 
 slug: pickup-point-not-visible-for-selection-in-shipping-policy-ui
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 449813
 ---
 
diff --git a/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md b/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
new file mode 100644
index 000000000..d1553f982
--- /dev/null
+++ b/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
@@ -0,0 +1,46 @@
+---
+title: 'Las etiquetas de punto de recogida se siguen mostrando en la política de envíos tras la eliminación.'
+id: 2ZcIGeYUud4bQJrAd5MMLb
+status: PUBLISHED
+createdAt: 2024-04-10T18:52:17.457Z
+updatedAt: 2024-04-10T18:52:18.169Z
+publishedAt: 2024-04-10T18:52:18.169Z
+firstPublishedAt: 2024-04-10T18:52:18.169Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: las-etiquetas-de-punto-de-recogida-se-siguen-mostrando-en-la-politica-de-envios-tras-la-eliminacion
+locale: es
+kiStatus: Backlog
+internalReference: 1015158
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las etiquetas registradas en el punto de recogida están disponibles en un desplegable en las políticas de envío para enlazar el PUP con la Política de Envío, sin embargo cuando alguna de estas etiquetas es eliminada en el PUP, permanecen disponibles en el desplegable dentro de la política de envío.
+
+
+##
+
+## Simulación
+
+
+Registre una etiqueta en un PUP, compruebe que estará disponible en la política de envíos para vincularla al PUP, luego en el propio PUP elimine la etiqueta y compruebe de nuevo en la política de envíos, la etiqueta seguirá estando ahí.
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible
+
+
+
+
+
diff --git a/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md b/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
index 4de8af617..cb7422252 100644
--- a/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
+++ b/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
@@ -3,8 +3,8 @@ title: 'La lista de puntos de recogida no se puede desplazar después de buscar
 id: 3e0JgNoWSQ0GAw8kurGrIR
 status: PUBLISHED
 createdAt: 2022-08-11T18:35:48.300Z
-updatedAt: 2022-11-25T21:50:52.987Z
-publishedAt: 2022-11-25T21:50:52.987Z
+updatedAt: 2024-07-01T18:48:32.968Z
+publishedAt: 2024-07-01T18:48:32.968Z
 firstPublishedAt: 2022-08-11T18:35:48.775Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-lista-de-puntos-de-recogida-no-se-puede-desplazar-despues-de-buscar-direcciones-en-el-modo-mapa
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 624646
 ---
 
diff --git a/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md b/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md
new file mode 100644
index 000000000..7cde89048
--- /dev/null
+++ b/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md
@@ -0,0 +1,50 @@
+---
+title: 'Puntos de recogida no indexados en los datos maestros'
+id: 6OHjbM6GXBEvgepaod3AyT
+status: PUBLISHED
+createdAt: 2023-12-14T22:29:26.240Z
+updatedAt: 2024-04-30T12:56:14.390Z
+publishedAt: 2024-04-30T12:56:14.390Z
+firstPublishedAt: 2023-12-14T22:29:26.972Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: puntos-de-recogida-no-indexados-en-los-datos-maestros
+locale: es
+kiStatus: Fixed
+internalReference: 530824
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, el sistema logístico utiliza MasterData para almacenar la información de los Puntos de Recogida. Como resultado, podemos tener problemas para indexar esta entidad interna cuando se utiliza la ruta de búsqueda. Esto puede dar lugar a información obsoleta, como por ejemplo:
+
+- Borrado realizado en Logística que no se refleja en el listado;
+- Punto de Recogida activado/inactivado en Logística pero que sigue volviendo con el estado anterior;
+- Cambios de coordenadas que no se reflejan;
+- Y otros.
+
+
+##
+
+## Simulación
+
+
+No hay forma fiable de reproducir este problema.
+
+
+
+## Workaround
+
+
+El equipo de VTEX debe comprobar los datos y, en su caso, volver a indexarlos para que se actualicen.
+
+
+
+
diff --git a/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md b/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
new file mode 100644
index 000000000..eece6e37a
--- /dev/null
+++ b/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
@@ -0,0 +1,49 @@
+---
+title: 'Los puntos de recogida que comienzan con el mismo patrón de identificación muestran el producto disponible'
+id: 1iCnOFHyKNTLvY20VS58HP
+status: PUBLISHED
+createdAt: 2024-01-10T16:01:39.766Z
+updatedAt: 2024-01-10T16:01:40.403Z
+publishedAt: 2024-01-10T16:01:40.403Z
+firstPublishedAt: 2024-01-10T16:01:40.403Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-puntos-de-recogida-que-comienzan-con-el-mismo-patron-de-identificacion-muestran-el-producto-disponible
+locale: es
+kiStatus: Backlog
+internalReference: 964036
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando los dos puntos de recogida con IDs comienzan con el mismo patrón, la UI de caja los valida como la misma tienda, mostrando un producto disponible.
+
+
+##
+
+## Simulación
+
+
+
+- Registre dos puntos de recogida: uno con ID 8 y otro con ID 835;
+- Asócielos con diferentes estrategias de envío, donde sólo uno de los puntos de recogida debe tener un producto disponible;
+- Montar un carrito y seleccionar el punto de recogida donde el producto no debería estar disponible;
+- El producto aparecerá como disponible.
+
+
+
+## Workaround
+
+
+NO DISPONIBLE
+
+
+
+
diff --git a/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md b/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
new file mode 100644
index 000000000..e70cd577b
--- /dev/null
+++ b/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
@@ -0,0 +1,49 @@
+---
+title: 'El punto de recogida y la entrega programada en el mismo carro no funcionan correctamente'
+id: 6ZCy8a4K6655BANe2yvz6e
+status: PUBLISHED
+createdAt: 2023-06-16T21:14:13.927Z
+updatedAt: 2023-06-16T21:14:14.834Z
+publishedAt: 2023-06-16T21:14:14.834Z
+firstPublishedAt: 2023-06-16T21:14:14.834Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-punto-de-recogida-y-la-entrega-programada-en-el-mismo-carro-no-funcionan-correctamente
+locale: es
+kiStatus: Backlog
+internalReference: 482256
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La interfaz de usuario no funciona correctamente en un carrito con más de un artículo con una división de entrega en la que uno de los artículos está disponible para recogida y los otros sólo para entrega programada.
+
+La fecha para elegir los artículos de recogida se establece sin problemas. Pero las fechas para la entrega programada no se comportan como se espera.
+
+
+
+## Simulación
+
+
+
+- Montar un carro con al menos dos artículos donde uno de los artículos está disponible para recogida y los otros sólo para entrega programada;
+- En el paso de envío, seleccione Recoger en tienda y seleccione una ventana de entrega ;
+- Intente seleccionar una ventana de entrega para la entrega programada.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md b/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
new file mode 100644
index 000000000..9f51fa893
--- /dev/null
+++ b/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
@@ -0,0 +1,60 @@
+---
+title: 'Al colocar el código postal en la vista previa de envío del carro, se duplican las opciones de dirección para los clientes recurrentes.'
+id: 4J8TMlhGmMtnHKXGES4qie
+status: PUBLISHED
+createdAt: 2023-12-20T21:36:52.612Z
+updatedAt: 2023-12-20T21:36:53.238Z
+publishedAt: 2023-12-20T21:36:53.238Z
+firstPublishedAt: 2023-12-20T21:36:53.238Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: al-colocar-el-codigo-postal-en-la-vista-previa-de-envio-del-carro-se-duplican-las-opciones-de-direccion-para-los-clientes-recurrentes
+locale: es
+kiStatus: Backlog
+internalReference: 956338
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Tenemos algunos problemas a la hora de colocar los códigos postales en el módulo **Previsualización de envíos** del carrito, algunos de ellos se describen en estos KIs:
+
+
+- Ref. 1: [KI] Al pegar el código postal en el carrito de vista previa de envío a veces se devuelve un resultado nulo de la API
+- Ref. 2: [KI] El campo de entrada de código postal de la vista previa de envío no está oculto
+
+En este caso, lo que ocurre es que para los clientes que ya tienen direcciones registradas en su perfil (compradores recurrentes), al colocar un código postal en la Vista previa de envío ya utilizado en una compra anterior, en la API se está colocando una opción de dirección de entrega adicional (`shippingData.availableAddresses`), al avanzar por los pasos del Checkout y llegar a la selección de dirección (`/checkout/#/shipping`), resulta que en lugar de seleccionar la dirección correspondiente a dicho código postal, se abre una nueva opción de selección incompleta, y en algunos casos oculta, obligando al cliente a seleccionar una de la lista o complementar la "nueva" para llegar al siguiente paso.
+
+
+##
+
+## Simulación
+
+
+
+1. Utilizar un usuario que ya ha realizado algunas compras y cuyo perfil tiene alguna dirección de entrega.
+2. Añade algunos artículos al carrito y luego pasa por caja.
+3. 3. En el carrito utilice la vista previa de envío para colocar un código postal de uno en su perfil.
+  1. Intente revisar el `orderForm`, y busque el `shippingData.availableAddresses`.
+  2. La dirección en su perfil aparecerá con un detalle clave, la dirección ya tiene el número de la calle (`shippingData.availableAddresses.[].number`)
+  3. La nueva opción en el array que genera el problema no tiene el `number`, lo que la convierte en una opción de dirección incompleta.
+4. Prueba a ir al paso de envío del checkout (`/checkout/#/shipping`) y verás que no puedes pasar al paso de pago si no completas la dirección seleccionada, o seleccionas otra de las opciones.
+
+
+
+## Workaround
+
+
+En el paso de envío del checkout, intente seleccionar la dirección deseada (fuerce la selección de una de las anteriores del cliente).
+
+
+
+
+
+
diff --git a/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md b/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
index af3dfba8a..01f763d59 100644
--- a/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
+++ b/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
@@ -3,8 +3,8 @@ title: 'El portal no borra las cookies cuando el cliente cierra la sesión al fi
 id: 5GPBW2TBOUzJkw5u47KC5z
 status: PUBLISHED
 createdAt: 2022-03-16T16:13:44.658Z
-updatedAt: 2022-11-25T22:10:31.240Z
-publishedAt: 2022-11-25T22:10:31.240Z
+updatedAt: 2024-04-26T18:05:09.421Z
+publishedAt: 2024-04-26T18:05:09.421Z
 firstPublishedAt: 2022-03-16T16:13:45.038Z
 contentType: knownIssue
 productTeam: Portal
@@ -25,27 +25,32 @@ internalReference: 417322
 
 En la caja de una tienda, tenemos una opción para cerrar la sesión.
 
-Desgraciadamente, la petición realizada a la aplicación del portal, no está borrando las cookies del usuario, permaneciendo en el OrderForm con el email ID de este cliente, por lo que el cliente no puede cerrar la sesión utilizando esta opción
+Desafortunadamente, la petición realizada a la aplicación del portal, no está borrando las cookies del usuario, permaneciendo en el OrderForm con el email ID de este cliente, por lo que el cliente no puede cerrar la sesión usando esta opción
 
 
+##
 
 ## Simulación
 
 
 1. Vaya a `.myvtex.com` e inicie sesión desde Mi Cuenta utilizando el correo electrónico y el código;
 
-2. 2. Una vez que hayas entrado, haz una cesta y ve a la caja;
+2. 2. Una vez que haya iniciado sesión, haga una cesta y vaya a la caja;
 
-3. Completa el paso de Perfil y ve a Envío, luego intenta cerrar la sesión desde el enlace "No soy yo, termina la sesión".
+3. Completa el paso Perfil y ve a Envíos, luego intenta cerrar sesión desde el enlace "No soy yo, finalizar sesión".
 
-El checkout realiza la petición normalmente, haciendo la petición junto con el `orderFormId`.
+Checkout realiza la petición normalmente, haciendo la petición junto con el `orderFormId`.
 
-Sin embargo, la aplicación del portal no está borrando la cookie de este usuario y por lo tanto devuelve el mismo usuario, con esto el correo electrónico se mantiene en el orderForm y en consecuencia, no se cierra la sesión.
+Sin embargo, Portal Application no está borrando la cookie de este usuario y por lo tanto devolviendo el mismo usuario, con esto el email se mantiene en el orderForm y en consecuencia, no se cierra la sesión.
 
 
 
 ## Workaround
 
 
-Cerrar la sesión a través de la página de inicio.
+Utilice un JS personalizado para forzar el cierre de sesión
+
+
+
+
 
diff --git a/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md b/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
index e38ae731b..596df85f6 100644
--- a/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
+++ b/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
@@ -3,8 +3,8 @@ title: "El portal mantiene las UTM's después de cerrar la sesión cuando se uti
 id: 4dogeU7iMoTXBWwv5DyR8u
 status: PUBLISHED
 createdAt: 2022-03-18T19:04:54.519Z
-updatedAt: 2022-11-25T22:10:46.942Z
-publishedAt: 2022-11-25T22:10:46.942Z
+updatedAt: 2024-02-16T20:27:34.500Z
+publishedAt: 2024-02-16T20:27:34.500Z
 firstPublishedAt: 2022-03-18T19:04:55.239Z
 contentType: knownIssue
 productTeam: Portal
diff --git a/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md b/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
index 0c09808c3..7517350bf 100644
--- a/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
+++ b/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
@@ -3,8 +3,8 @@ title: 'El portal recarga todos los resultados de la búsqueda cuando se accede
 id: 18Y8yYKByGTzMxyYhk1pdl
 status: PUBLISHED
 createdAt: 2022-01-23T02:35:50.182Z
-updatedAt: 2022-11-25T22:11:17.525Z
-publishedAt: 2022-11-25T22:11:17.525Z
+updatedAt: 2024-02-16T20:29:31.154Z
+publishedAt: 2024-02-16T20:29:31.154Z
 firstPublishedAt: 2022-03-16T16:22:55.043Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: el-portal-recarga-todos-los-resultados-de-la-busqueda-cuando-se-accede-a-la-url-con-el-parametro-de-paginacion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 342378
 ---
 
diff --git a/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md b/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
new file mode 100644
index 000000000..a00362de2
--- /dev/null
+++ b/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
@@ -0,0 +1,46 @@
+---
+title: 'Posibles errores en la notificación de órdenes de cambio en la interfaz de usuario, la API y la pasarela.'
+id: 1UeG6MyFYIUVCnH8kPwNIJ
+status: PUBLISHED
+createdAt: 2023-12-19T19:37:47.313Z
+updatedAt: 2023-12-19T19:37:47.950Z
+publishedAt: 2023-12-19T19:37:47.950Z
+firstPublishedAt: 2023-12-19T19:37:47.950Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: posibles-errores-en-la-notificacion-de-ordenes-de-cambio-en-la-interfaz-de-usuario-la-api-y-la-pasarela
+locale: es
+kiStatus: Backlog
+internalReference: 955489
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se identificaron algunos problemas en la arquitectura Change Orders V1, donde algunos casos no eran notificados en la interacción de la orden en la UI, no eran notificados en la API Get Orders, sin embargo, había un descuento o incremento en el valor. También hemos visto escenarios donde la notificación ocurre en la UI y API, sin embargo, el descuento o incremento no se realiza en el gateway.
+
+
+##
+
+## Simulación
+
+
+No es posible realizar una simulación, ya que los escenarios son esporádicos y generalmente se producen debido a un error de tiempo de espera, para el que ya hemos aumentado el temporizador.
+
+
+
+## Workaround
+
+
+Inicialmente no tenemos una solución, sin embargo, vale la pena mencionar que algunos escenarios podremos ajustarlos manualmente, como por ejemplo si el registro de órdenes de cambio ocurre en el gateway y no ocurre en el Marketplace o en la interacción de órdenes de cumplimiento y en la API también.
+
+
+
+
+
diff --git a/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md b/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md
new file mode 100644
index 000000000..3e58282a2
--- /dev/null
+++ b/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md
@@ -0,0 +1,52 @@
+---
+title: 'La preventa de la colección CMS heredada no funciona'
+id: 1bRqhWCmtckyCbYf1SQa5N
+status: PUBLISHED
+createdAt: 2023-08-22T18:51:34.059Z
+updatedAt: 2023-08-22T18:51:34.595Z
+publishedAt: 2023-08-22T18:51:34.595Z
+firstPublishedAt: 2023-08-22T18:51:34.595Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: la-preventa-de-la-coleccion-cms-heredada-no-funciona
+locale: es
+kiStatus: Backlog
+internalReference: 885693
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se esperaba que, al seleccionar la casilla de verificación de pre-pedido, la colección se poblaría con productos cuya fecha de lanzamiento se hubiera rellenado para una fecha futura.
+Sin embargo, esto no sucede, ya que la colección no se rellena, sino que permanece siempre vacía.
+
+
+##
+
+## Simulación
+
+
+
+- Establecer una fecha de lanzamiento en algunos productos para una fecha futura
+- Crear una colección
+- Vaya al administrador de la colección en el CMS heredado
+- Configure la colección para productos en preventa
+- Compruebe que la colección nunca se rellena
+
+
+
+## Workaround
+
+
+Gestione manualmente los productos de la colección
+
+
+
+
+
diff --git a/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
new file mode 100644
index 000000000..7e5c099cf
--- /dev/null
+++ b/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -0,0 +1,55 @@
+---
+title: 'El filtro de precios se aplica sobre el "precio al contado" en lugar del precio normal'
+id: 2EEgRV1NxYuns4eF7F0ZqD
+status: PUBLISHED
+createdAt: 2024-02-15T19:39:53.576Z
+updatedAt: 2024-02-15T19:39:54.436Z
+publishedAt: 2024-02-15T19:39:54.436Z
+firstPublishedAt: 2024-02-15T19:39:54.436Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: el-filtro-de-precios-se-aplica-sobre-el-precio-al-contado-en-lugar-del-precio-normal
+locale: es
+kiStatus: Backlog
+internalReference: 982664
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los filtros de precio se aplican sobre el valor "spotPrice", que es el precio para condiciones especiales de pago, en lugar del precio normal del artículo.
+
+Esto puede afectar a las expectativas a la vez que diverge de la mayoría de sitios, que se centran en el precio regular, como suelen hacer las estanterías y el carrito, o propiedades como "priceRange" de la API.
+
+
+##
+
+## Simulación
+
+
+Considere un producto con un precio de 430 $ con un 10% de descuento en un método de pago específico, generando un "precio al contado" de 387 $.
+
+Al filtrar por artículos con un precio entre 300 y 400 dólares se obtendrá este producto, que normalmente se mostrará en el lineal como 430 dólares (su precio habitual), generando la percepción de divergencia.
+
+Del mismo modo, la propiedad "priceRange" de la API responderá con los siguientes valores (considerando este producto como el único resultado para esta consulta de búsqueda), alimentando la sensación de divergencia:
+
+    "priceRange": { "sellingPrice": { "highPrice": 430, "lowPrice": 430 }, "listPrice": { "highPrice": 430, "lowPrice": 430 }}
+
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md b/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
new file mode 100644
index 000000000..09f150032
--- /dev/null
+++ b/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
@@ -0,0 +1,47 @@
+---
+title: 'El rango de precios en la API de facetas no se corresponde con los resultados de búsqueda'
+id: 2X9Z21u9kJh55uWu6o6sP3
+status: PUBLISHED
+createdAt: 2024-03-08T22:36:43.149Z
+updatedAt: 2024-03-08T22:36:44.086Z
+publishedAt: 2024-03-08T22:36:44.086Z
+firstPublishedAt: 2024-03-08T22:36:44.086Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: el-rango-de-precios-en-la-api-de-facetas-no-se-corresponde-con-los-resultados-de-busqueda
+locale: es
+kiStatus: Backlog
+internalReference: 997121
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los rangos de precios de la API de facetas ("Obtener lista de las facetas posibles para una consulta dada") pueden variar entre devolver cubos de valores "desde" y "hasta" con precios redondeados y los precios mínimos y máximos entre los resultados de la búsqueda.
+
+Mientras que los precios redondeados generan una mejor UX para presentar una lista de rangos de precios al comprador, no es deseable utilizarlos como un "deslizador" de precios.
+
+Además, como los precios mínimos y máximos se aplican en un segundo momento, los rangos de precios como "cubos" en una búsqueda que ya aplica un filtro de precios se salen de los límites en relación con los precios especificados.
+
+
+##
+
+## Simulación
+
+
+Utilizando la API, realice una petición con y sin un filtro de precios del tipo "/precio/100:500" y observe los rangos de precios devueltos (desde/hasta) en el objeto "valores" para la faceta con tipo "PRICERANGE".
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/price-range-disregards-sales-policy.md b/docs/known-issues/es/price-range-disregards-sales-policy.md
index ad2b642ec..17de878de 100644
--- a/docs/known-issues/es/price-range-disregards-sales-policy.md
+++ b/docs/known-issues/es/price-range-disregards-sales-policy.md
@@ -1,36 +1,33 @@
 ---
-title: 'Price range disregards sales policy'
-id: 4isnfk4T2UB3CId8bXcvFT
-status: DRAFT
-createdAt: 2022-03-16T16:35:57.963Z
-updatedAt: 2022-06-08T14:01:22.874Z
-publishedAt: 
-firstPublishedAt: 
+title: 'La franja de precios no respeta la política comercial'
+id: 3OsmwHOZyM0AQWA8CuK0aC
+status: PUBLISHED
+createdAt: 2017-10-17T17:50:40.970Z
+updatedAt: 2022-12-22T20:46:23.778Z
+publishedAt: 2022-12-22T20:46:23.778Z
+firstPublishedAt: 2017-10-17T18:03:23.731Z
 contentType: knownIssue
-productTeam: Portal
+productTeam: Marketing & Merchandising
 author: 2mXZkbi0oi061KicTExNjo
-tag: Portal
-slug: price-range-disregards-sales-policy
+tag: Portal (CMS)
+slug: la-franja-de-precios-no-respeta-la-politica-comercial
 locale: es
 kiStatus: Backlog
-internalReference: 322764
+internalReference: 
 ---
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+El filtro por rango de precio, que se configura en las opciones de categoría, considera el precio registrado en todas las políticas comerciales de la tienda, es decir, siempre va a imprimir el considerando el valor más bajo registrado entre todas las políticas comerciales, posibilitando la exhibición de un producto que no está en el rango de precios de la política comercial específica.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+1. Registre precios diferentes en políticas comerciales diferentes para el mismo SKU;
+2. Registre franjas de precio en la categoría donde los precios registrados queden en franjas diferentes;
+3. En la política comercial con el precio del SKU más caro, haga el filtro por rango de precio;
+4. Véase que el valor del SKU considerado es el de la otra política comercial, pues considera el valor más barato entre todas las políticas.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+No hay solución de contorno para el escenario.
 
diff --git a/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md b/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
new file mode 100644
index 000000000..d51bf5b29
--- /dev/null
+++ b/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
@@ -0,0 +1,54 @@
+---
+title: 'El control deslizante de la gama de precios adopta por defecto el valor mínimo después de seleccionar un filtro.'
+id: 15ABXMTT9cqieizxYWqC2V
+status: PUBLISHED
+createdAt: 2023-11-08T13:34:50.960Z
+updatedAt: 2023-11-08T13:34:51.373Z
+publishedAt: 2023-11-08T13:34:51.373Z
+firstPublishedAt: 2023-11-08T13:34:51.373Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-control-deslizante-de-la-gama-de-precios-adopta-por-defecto-el-valor-minimo-despues-de-seleccionar-un-filtro
+locale: es
+kiStatus: Backlog
+internalReference: 843442
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Este es un rango de precios, es un deslizador y tiene dos selectores (marcadores), uno para el mínimo y otro para el máximo para saber dónde posicionarse en el deslizador.
+Al aplicarle un filtro de marca el selector no moverá su valor mínimo a los valores mínimos de la marca, mantendrá el valor mínimo por defecto y el marcador aparecerá fuera del rango.
+
+
+##
+
+## Simulación
+
+
+1- Acceda a la página de una Categoría y observe el filtro de rango de precios y sus valores min y max.
+2- Selecciona un filtro marcándolo a la izquierda (category2/3/4)
+3- Con el filtro aplicado, observa que el deslizador de rango de precios mantendrá el valor mínimo como antes y estará fuera del rango del deslizador.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/RuhwOHLwbPslKpeZ4VUq4Y995/?name=image.png)
+
+Filtro con el comportamiento descrito para el valor min.
+
+
+##
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md b/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
new file mode 100644
index 000000000..6951687d6
--- /dev/null
+++ b/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
@@ -0,0 +1,52 @@
+---
+title: 'Precio intercambiado si el mismo artículo está dos veces en la cesta y uno es de Opciones de montaje'
+id: 6ASEyEYPt9wjj4eSzMqdc0
+status: PUBLISHED
+createdAt: 2024-07-24T14:51:12.922Z
+updatedAt: 2024-07-24T14:51:13.713Z
+publishedAt: 2024-07-24T14:51:13.713Z
+firstPublishedAt: 2024-07-24T14:51:13.713Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: precio-intercambiado-si-el-mismo-articulo-esta-dos-veces-en-la-cesta-y-uno-es-de-opciones-de-montaje
+locale: es
+kiStatus: Backlog
+internalReference: 1070336
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si un artículo se añade al carrito como opción (también conocido como hijo) desde Opciones de montaje, y el mismo artículo se añade al carrito como artículo normal; los precios se mezclan, y cada uno se aplica al incorrecto.
+
+Por ejemplo:
+
+- Artículo como opción con un precio de 0;
+- Artículo como normal con un precio de 100.
+En el pedido, el artículo como opción tendrá el precio de 100 y el normal con el precio de 0.
+
+
+##
+
+## Simulación
+
+
+
+- Añade un artículo con una opción de montaje al carrito, y asegúrate de que una de las opciones tiene una lista de precios diferente en la configuración;
+- Añade el mismo artículo como opción.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/price-updates-with-cache-on-end-applications.md b/docs/known-issues/es/price-updates-with-cache-on-end-applications.md
new file mode 100644
index 000000000..3bc98098e
--- /dev/null
+++ b/docs/known-issues/es/price-updates-with-cache-on-end-applications.md
@@ -0,0 +1,45 @@
+---
+title: 'Actualizaciones de precios con caché en las aplicaciones finales'
+id: 1ZDl8C3DDoACmxRqRlYDJo
+status: PUBLISHED
+createdAt: 2023-09-08T16:08:24.445Z
+updatedAt: 2023-09-08T16:08:25.900Z
+publishedAt: 2023-09-08T16:08:25.900Z
+firstPublishedAt: 2023-09-08T16:08:25.900Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: actualizaciones-de-precios-con-cache-en-las-aplicaciones-finales
+locale: es
+kiStatus: Backlog
+internalReference: 896520
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+1. Actualizar el precio de un sku;
+2. 2. Comprobar en los registros del puente si el precio enviado a las integraciones del mercado era el actualizado o el valor antiguo.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
new file mode 100644
index 000000000..fc6e25de8
--- /dev/null
+++ b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -0,0 +1,45 @@
+---
+title: 'Precios restringidos al valor máximo "Int32" en la API de cambio de precio'
+id: 5mzOjCUYs7vXUkttbsK0za
+status: PUBLISHED
+createdAt: 2022-04-25T17:28:05.159Z
+updatedAt: 2024-02-16T20:26:04.281Z
+publishedAt: 2024-02-16T20:26:04.281Z
+firstPublishedAt: 2022-04-25T17:28:05.773Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: precios-restringidos-al-valor-maximo-int32-en-la-api-de-cambio-de-precio
+locale: es
+kiStatus: No Fix
+internalReference: 566142
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La API REST de Checkout Cambiar precio no admite precios superiores a un valor "Int32". Por lo tanto, aplicar un "precio manual" estará restringido hasta el número "2.147.483.647" (número en decimales).
+
+
+##
+
+## Simulación
+
+
+Al utilizar la API "Cambiar precio" (https://developers.vtex.com/vtex-rest-api/reference/pricechange), el envío de una carga útil como "{"precio":2500000000}" (que representa 25.000.000,00 $) devolverá un error 500 con el mensaje "Value was either too large or too small for an Int32.".
+
+
+
+## Workaround
+
+
+Utilice la API "Handle cart items" para actualizar el precio.
+
+
+
+
diff --git a/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
new file mode 100644
index 000000000..1c3caa913
--- /dev/null
+++ b/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -0,0 +1,48 @@
+---
+title: 'Priorización por "palabra clave" del producto sin tener en cuenta las "stopwords'
+id: 55S7nFg61dAyCeGQCIw6aK
+status: PUBLISHED
+createdAt: 2024-05-30T22:05:25.328Z
+updatedAt: 2024-05-30T22:05:26.335Z
+publishedAt: 2024-05-30T22:05:26.335Z
+firstPublishedAt: 2024-05-30T22:05:26.335Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: priorizacion-por-palabra-clave-del-producto-sin-tener-en-cuenta-las-stopwords
+locale: es
+kiStatus: Backlog
+internalReference: 1041743
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los productos pueden ser priorizados en los resultados de búsqueda por su "palabra clave", una palabra del nombre del producto establecida como relevante por un algoritmo. Las palabras clave son términos de búsqueda filtrados de los términos originales porque no son significativos para la búsqueda.
+
+Si la palabra clave de un producto es una "stopword", este producto puede perder prioridad en los resultados de búsqueda.
+
+
+##
+
+## Simulación
+
+
+
+- Un producto con el nombre "La vida en el océano" tendrá "la" como palabra clave.
+- Considerando una tienda en español, una búsqueda de este nombre de producto se hará efectivamente como "vida el oceano" después de eliminar las stopwords.
+- Los productos con "vida" como palabra clave tendrán prioridad sobre el producto buscado.
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md b/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md
index 11eab9f00..4f04be86a 100644
--- a/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md
+++ b/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md
@@ -3,8 +3,8 @@ title: 'Problema al validar el campo de valor al comprar con dos tarjetas'
 id: 6dr0p9WQPSHLkFaSbjI9J7
 status: PUBLISHED
 createdAt: 2022-03-28T01:05:19.734Z
-updatedAt: 2022-11-25T22:06:10.550Z
-publishedAt: 2022-11-25T22:06:10.550Z
+updatedAt: 2024-07-01T18:48:07.379Z
+publishedAt: 2024-07-01T18:48:07.379Z
 firstPublishedAt: 2022-03-28T01:05:20.361Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: problema-al-validar-el-campo-de-valor-al-comprar-con-dos-tarjetas
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 460683
 ---
 
diff --git a/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md b/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md
new file mode 100644
index 000000000..413ac1e1b
--- /dev/null
+++ b/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md
@@ -0,0 +1,49 @@
+---
+title: 'Problema con la validación del teléfono en dispositivos móviles'
+id: 2KpjpNZEbAZ7PFFPvMvwNA
+status: PUBLISHED
+createdAt: 2024-01-12T14:24:34.604Z
+updatedAt: 2024-01-12T14:24:56.084Z
+publishedAt: 2024-01-12T14:24:56.084Z
+firstPublishedAt: 2024-01-12T14:24:35.388Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: problema-con-la-validacion-del-telefono-en-dispositivos-moviles
+locale: es
+kiStatus: Backlog
+internalReference: 964802
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La validación del campo del teléfono en dispositivos móviles no se comporta como es debido. Cuando se alcanza el número esperado de caracteres, la validación marca correctamente el campo con un check. Sin embargo, cuando se añaden caracteres adicionales y luego se eliminan uno a uno, la validación no reconoce que el recuento de caracteres sigue siendo superior al esperado, marcando incorrectamente la entrada como válida. La validación también marca como válidas las entradas con menos caracteres de los esperados.
+
+
+
+## Simulación
+
+
+
+1. Navega hasta la página de pago comprando cualquier artículo al azar.
+2. Durante el paso de perfil, introduzca un número de teléfono hasta que el campo se valide y se marque con un check.
+3. 3. Experimente añadiendo más caracteres al número de teléfono y luego eliminándolos uno a uno, observando cómo el campo conserva la marca de verificación incluso con un número reducido de caracteres en comparación con la validación inicial.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md b/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md
new file mode 100644
index 000000000..a2d60c919
--- /dev/null
+++ b/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md
@@ -0,0 +1,73 @@
+---
+title: 'La visualización de la disponibilidad del producto se retrasa cuando se utilizan varios canales de venta'
+id: 7JluVogO4pom0l57UobYIP
+status: PUBLISHED
+createdAt: 2023-12-07T16:18:59.300Z
+updatedAt: 2023-12-07T16:19:00.098Z
+publishedAt: 2023-12-07T16:19:00.098Z
+firstPublishedAt: 2023-12-07T16:19:00.098Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-visualizacion-de-la-disponibilidad-del-producto-se-retrasa-cuando-se-utilizan-varios-canales-de-venta
+locale: es
+kiStatus: Backlog
+internalReference: 949411
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La visualización, para tiendas de portales heredados, de productos en PLPs se basa en el canal de venta de la tienda y sus datos básicos de disponibilidad.
+
+Si un producto tiene stock, precio y sus datos básicos para ser vendido correctamente en una tienda + pertenece a dicho canal de venta, este producto está y debe estar listado en la tienda.
+
+Sin embargo, cuando dicho producto tiene la opción "mostrar si no está disponible" establecida en false, debe ser eliminado de las páginas de la tienda cuando no se puede vender.
+
+En la mayoría de los casos, este proceso se lleva a cabo de forma eficiente, pero en los casos en los que dicho producto no está disponible para un canal de ventas determinado pero sí para otros, puede seguir mostrándose en los canales no deseados.
+
+
+**Ejemplo**:
+
+1 - El producto 1 está disponible en los canales de venta 1, 2 y 3.
+
+2 - Se ha agotado en el canal de venta 2. Se supone que ya no aparece en él.
+
+3 - Como aún está disponible en los canales 1 y 3, podría "atascarse" y seguir mostrándose durante un tiempo prolongado en el canal 2, a pesar de no estar disponible.
+
+*Este problema sólo se produce cuando un producto con el indicador = false pasa de disponible a no disponible en un canal de venta mientras sigue apareciendo en los demás. Esta incoherencia no se produce a la inversa (pasando de no disponible a disponible).
+
+
+
+##
+
+## Simulación
+
+
+Para una tienda con múltiples canales de venta y que utiliza diferentes dominios para cada uno, obtener un producto que esté disponible en ambos y que se muestre bajo un resultado de búsqueda específico.
+
+Este producto de prueba debe tener la opción "mostrar incluso si no está disponible" establecida como false en él.
+
+A continuación, configúrelo como agotado en uno de los canales de venta.
+
+Seguirá apareciendo, incluso después de mucho tiempo, en los resultados de búsqueda de ambos dominios, a pesar de no estar disponible en uno de los canales.
+
+
+
+## Workaround
+
+
+**Opción A**) Realice un borrado del indexador y un reindexado de la base de datos si su tienda tiene menos de 10000 productos y tiene varios artículos en este escenario.
+
+**Opción B**) Para un pequeño conjunto de productos, elimine su disponibilidad de la tienda por completo (hágalo no disponible en todos los canales de venta) y luego revierta inmediatamente estos cambios.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md b/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
index 61678f09a..8c3c09557 100644
--- a/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
+++ b/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
@@ -3,8 +3,8 @@ title: 'La disponibilidad del producto se muestra incorrectamente en el modo de
 id: 6aoRWAMSGDwcuUPvGd8bI9
 status: PUBLISHED
 createdAt: 2022-03-30T17:24:21.013Z
-updatedAt: 2022-11-25T21:53:23.560Z
-publishedAt: 2022-11-25T21:53:23.560Z
+updatedAt: 2024-02-16T20:28:45.041Z
+publishedAt: 2024-02-16T20:28:45.041Z
 firstPublishedAt: 2022-03-30T17:24:21.669Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-disponibilidad-del-producto-se-muestra-incorrectamente-en-el-modo-de-visualizacion-de-las-recogidas-en-el-carro
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 552875
 ---
 
diff --git a/docs/known-issues/es/product-comissioning-inconsistent-cache.md b/docs/known-issues/es/product-comissioning-inconsistent-cache.md
new file mode 100644
index 000000000..2e10c8ce3
--- /dev/null
+++ b/docs/known-issues/es/product-comissioning-inconsistent-cache.md
@@ -0,0 +1,64 @@
+---
+title: 'Puesta en servicio del producto Caché incoherente'
+id: 7queBSJcAG9yIlKbvWOVgY
+status: PUBLISHED
+createdAt: 2023-08-01T17:48:39.144Z
+updatedAt: 2023-08-01T17:56:01.673Z
+publishedAt: 2023-08-01T17:56:01.673Z
+firstPublishedAt: 2023-08-01T17:54:19.969Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: puesta-en-servicio-del-producto-cache-incoherente
+locale: es
+kiStatus: Backlog
+internalReference: 872364
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+Hay, a partir de 2023, dos conjuntos de API distintos para actualizar la información de un vendedor en un mercado, son:
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
+https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/seller-register/pvt/sellers/-sellerId-/commissions/categories
+
+Estas deberían ser coherentes entre sí (y en gran medida, lo son) pero, al actualizar los datos de comisión para todas las categorías en la última, se tarda mucho en actualizar la información en la respuesta de la API catalog_system.
+
+Esto sucede cuando la comisión se establece para la categoría raíz (por ejemplo, la carga útil a continuación)
+
+```
+[
+ {
+      ""categoryId"": ""default"",
+      ""categoryName"": null,
+      ""categoryFullPath"": [],
+      ""productCommissionPercentage"": 50.0,
+      ""freightCommissionPercentage"": 0.0
+  }
+]
+```
+
+La principal consecuencia de este retraso es que el checkout y los marktplaces utilizan mayoritariamente la respuesta catalog_system, lo que puede dar lugar a comisiones incorrectas en los pedidos.
+
+
+## Simulación
+
+
+1. En un marketplace, prueba a realizar una solicitud GET utilizando la API de catálogo para un vendedor determinado https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/seller/-sellerId-
+2. Actualiza sus datos de comisionado de productos a través de un PUT a la misma ruta https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
+3. Realiza otra GET y verás que la información se ha actualizado correctamente.
+4. Ahora, intenta hacer lo mismo utilizando la API de registro de vendedores https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-/commissions
+5. Envía un payload para la categoría raíz (es decir, para toda la tienda, aparte de otras categorías con comisiones específicas) configurando cualquier productComissionPercentage https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/seller-register/pvt/sellers/-sellerId-/commissions/categories
+6. Si obtiene datos a través de GET para esta misma colección, verá la información actualizada: https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-/commissions
+7. Sin embargo, al intentar obtener estos mismos datos a través de la API catalog_system, tardará días en actualizarse si no se realiza ninguna otra actualización.
+
+## Workaround
+
+- Configurar otros datos en la API de registro de vendedor, lo que fuerza una pérdida de caché.
+- Actualizar directamente a través de la api catalog_system.
+- Utilizar la interfaz de usuario para realizar actualizaciones.
+
diff --git a/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md b/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md
new file mode 100644
index 000000000..f0dbfadd8
--- /dev/null
+++ b/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md
@@ -0,0 +1,52 @@
+---
+title: 'La imagen del producto en admin cambia con más de 70 skus.'
+id: 6EtUyiWzpm5moEN6hkY4B0
+status: PUBLISHED
+createdAt: 2024-03-21T15:18:20.218Z
+updatedAt: 2024-03-21T15:18:21.405Z
+publishedAt: 2024-03-21T15:18:21.405Z
+firstPublishedAt: 2024-03-21T15:18:21.405Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-imagen-del-producto-en-admin-cambia-con-mas-de-70-skus
+locale: es
+kiStatus: Backlog
+internalReference: 1003966
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un producto tiene más de 70 variaciones de skus su imagen en admin (y sólo en admin) cambia a una imagen de información:
+ ![](https://vtexhelp.zendesk.com/attachments/token/3oAwbW4sgou7su2F6Ls5CGqoR/?name=image.png)
+
+con el texto: "ATENÇÃO: não foi possível excluir este produto porque ele tem mais SKUs do que o permitido pelo sistema."
+
+
+##
+
+## Simulación
+
+
+
+- Añadir más de 70 skus en un producto
+- Compruebe que la imagen en admin cambia a la presentada anteriormente
+- Compruebe que el producto sigue siendo el mismo en PDP.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 4b7ef9ef2..7b4756cbe 100644
--- a/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -3,8 +3,8 @@ title: 'La API de inserción/actualización de productos permite "\n" en el camp
 id: 5TfUw5tTxBEu9HkL3ypBKw
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.325Z
-updatedAt: 2022-11-25T21:44:48.430Z
-publishedAt: 2022-11-25T21:44:48.430Z
+updatedAt: 2024-02-16T20:28:55.474Z
+publishedAt: 2024-02-16T20:28:55.474Z
 firstPublishedAt: 2022-06-28T16:55:54.138Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-api-de-insercionactualizacion-de-productos-permite-n-en-el-campo-textlink
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 486459
 ---
 
diff --git a/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
new file mode 100644
index 000000000..1d434be0f
--- /dev/null
+++ b/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -0,0 +1,49 @@
+---
+title: 'La búsqueda "El nombre del producto contiene" con más de un término no funciona en la interfaz de usuario rediseñada del catálogo.'
+id: 2kI6ab0kdpLG6m63ETGGqf
+status: PUBLISHED
+createdAt: 2024-06-05T13:38:38.836Z
+updatedAt: 2024-06-05T13:38:39.630Z
+publishedAt: 2024-06-05T13:38:39.630Z
+firstPublishedAt: 2024-06-05T13:38:39.630Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-busqueda-el-nombre-del-producto-contiene-con-mas-de-un-termino-no-funciona-en-la-interfaz-de-usuario-redisenada-del-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 1044571
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En la lista de productos rediseñada del catálogo, uno de los campos de búsqueda es "El nombre del producto contiene". Actualmente, al buscar un nombre de producto con más de un término, pueden darse dos situaciones:
+
+- devuelve cualquier producto que tenga cualquiera de los términos
+- no devuelve el producto con el nombre exacto buscado
+
+
+##
+
+## Simulación
+
+
+Buscar un nombre de producto con dos o más términos en un catálogo rediseñado y observar que se pueden devolver productos que contengan sólo uno de los términos
+
+
+
+## Workaround
+
+
+Utilice la búsqueda "Nombre SKU" o las demás opciones de búsqueda disponibles
+
+
+
+
+
diff --git a/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md b/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
index 8be79634d..d37575868 100644
--- a/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
+++ b/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
@@ -3,8 +3,8 @@ title: 'El campo del nombre del producto en el XML devuelve el nombre del produc
 id: 7sNNzBe5pLn7oigDgoCKjv
 status: PUBLISHED
 createdAt: 2022-09-19T19:06:55.572Z
-updatedAt: 2022-11-25T21:43:35.947Z
-publishedAt: 2022-11-25T21:43:35.947Z
+updatedAt: 2024-02-16T20:23:45.927Z
+publishedAt: 2024-02-16T20:23:45.927Z
 firstPublishedAt: 2022-09-19T19:06:56.137Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-campo-del-nombre-del-producto-en-el-xml-devuelve-el-nombre-del-producto-el-nombre-del-sku-cuando-el-producto-solo-tiene-un-sku
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 661089
 ---
 
diff --git a/docs/known-issues/es/product-page-sessions-not-working.md b/docs/known-issues/es/product-page-sessions-not-working.md
new file mode 100644
index 000000000..65dd4138f
--- /dev/null
+++ b/docs/known-issues/es/product-page-sessions-not-working.md
@@ -0,0 +1,45 @@
+---
+title: 'Las sesiones de las páginas de productos no funcionan'
+id: 6Hgk9lBPmrZ9byc6eeRiki
+status: PUBLISHED
+createdAt: 2024-01-04T21:34:51.613Z
+updatedAt: 2024-01-04T21:36:00.900Z
+publishedAt: 2024-01-04T21:36:00.900Z
+firstPublishedAt: 2024-01-04T21:34:52.264Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: las-sesiones-de-las-paginas-de-productos-no-funcionan
+locale: es
+kiStatus: Backlog
+internalReference: 961591
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El resumen del administrador tiene alguna información analítica. La información sobre las sesiones de la página de productos debería devolver los valores de este evento, pero a veces devuelve cero.
+
+
+
+## Simulación
+
+
+Acceda al administrador de la tienda e intente buscar las sesiones de la página de productos. Comprueba si devuelve cero
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md b/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md
index 3f04e37fd..768cca16f 100644
--- a/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md
+++ b/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md
@@ -3,8 +3,8 @@ title: 'El precio del producto no tiene en cuenta al vendedor por defecto en el
 id: 4VOIW6kCTfFZ3S9u3xtdDF
 status: PUBLISHED
 createdAt: 2022-02-23T21:52:42.520Z
-updatedAt: 2022-11-25T22:13:37.983Z
-publishedAt: 2022-11-25T22:13:37.983Z
+updatedAt: 2024-02-16T20:27:12.071Z
+publishedAt: 2024-02-16T20:27:12.071Z
 firstPublishedAt: 2022-03-07T22:34:44.879Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: el-precio-del-producto-no-tiene-en-cuenta-al-vendedor-por-defecto-en-el-pdp
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429888
 ---
 
diff --git a/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md b/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
index 77bc7549f..84d83708f 100644
--- a/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
+++ b/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
@@ -3,8 +3,8 @@ title: 'La sustitución de productos en un pedido OMS no funciona en las cuentas
 id: 1wQTfSR6OB6CL0sRpCYARp
 status: PUBLISHED
 createdAt: 2023-02-14T12:25:00.911Z
-updatedAt: 2023-02-14T12:25:01.506Z
-publishedAt: 2023-02-14T12:25:01.506Z
+updatedAt: 2024-07-01T18:48:50.766Z
+publishedAt: 2024-07-01T18:48:50.766Z
 firstPublishedAt: 2023-02-14T12:25:01.506Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-sustitucion-de-productos-en-un-pedido-oms-no-funciona-en-las-cuentas-del-portal-del-vendedor
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 753484
 ---
 
diff --git a/docs/known-issues/es/product-specification-export-index-out-of-range.md b/docs/known-issues/es/product-specification-export-index-out-of-range.md
index 9afe31034..10c27f670 100644
--- a/docs/known-issues/es/product-specification-export-index-out-of-range.md
+++ b/docs/known-issues/es/product-specification-export-index-out-of-range.md
@@ -1,16 +1,16 @@
 ---
-title: 'La exportación de especificación del producto retorna Index Out of Range'
+title: 'Especificación del producto Índice de exportación fuera de la gama'
 id: 2Qu9QCZvfcjmNfAh3uvPkf
 status: PUBLISHED
 createdAt: 2022-02-25T12:22:04.014Z
-updatedAt: 2022-11-25T21:45:45.357Z
-publishedAt: 2022-11-25T21:45:45.357Z
+updatedAt: 2024-01-10T20:25:32.586Z
+publishedAt: 2024-01-10T20:25:32.586Z
 firstPublishedAt: 2022-02-25T12:22:04.405Z
 contentType: knownIssue
 productTeam: Catalog
 author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
-slug: la-exportacion-de-especificacion-del-producto-retorna-index-out-of-range
+slug: especificacion-del-producto-indice-de-exportacion-fuera-de-la-gama
 locale: es
 kiStatus: Backlog
 internalReference: 481095
@@ -23,18 +23,18 @@ internalReference: 481095
 </div>
 
 
-Al intentar exportar, mediante la UI: , los datos de las fichas de producto, si no tienen ningún campo válido registrado directamente en la categoría a exportar, el proceso fallará con un mensaje de "Índice fuera de rango".
-
+Al intentar exportar Especificaciones de Producto desde la UI "Importar y Exportar", si existe algún valor nulo o relación nula en la categoría a exportar, el proceso fallará con un mensaje de "Índice fuera de Rango". En otras palabras, la categoría debe tener registrado directamente a su nivel un campo de producto, productos y productos con valores asociados.
 
 
 
+##
 
 ## Simulación
 
 
-1) Vaya a la UI de exportación de la especificación del producto: ProdutoExportacaoImportacaoEspecificacaoV2.aspx
+1) Ir a la UI de exportación de Especificación de Producto: ProdutoExportacaoImportacaoEspecificacaoV2.aspx
 
-2) Haga clic con el botón derecho del ratón en una categoría en la que no haya ningún campo de especificación de producto registrado
+2) Haga clic con el botón derecho en una categoría en la que no haya ningún campo de especificación de producto registrado
 
 3) Aparecerá un mensaje de error de "Índice fuera de bonos".
 
@@ -46,9 +46,9 @@ Al intentar exportar, mediante la UI: , los datos de las fichas de producto, si
 ## Workaround
 
 
-Exportar el padre o el hijo de la categoría deseada
+Exporte la categoría padre o hija deseada
 
 o
 
-Utilizar la API de obtención de especificaciones de productos para obtener los datos: https://developers.vtex.com/vtex-rest-api/reference/catalog-api-product-specification
+Utilice la API de obtención de especificaciones de productos para obtener los datos: https://developers.vtex.com/vtex-rest-api/reference/catalog-api-product-specification
 
diff --git a/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
new file mode 100644
index 000000000..f7104f269
--- /dev/null
+++ b/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -0,0 +1,49 @@
+---
+title: 'El filtro "Especificación del producto" del módulo de recogida asume valores incorrectos.'
+id: 2vg3t5kp7j4Ttla53pVjck
+status: PUBLISHED
+createdAt: 2023-10-26T22:22:44.895Z
+updatedAt: 2023-10-26T22:22:45.413Z
+publishedAt: 2023-10-26T22:22:45.413Z
+firstPublishedAt: 2023-10-26T22:22:45.413Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-filtro-especificacion-del-producto-del-modulo-de-recogida-asume-valores-incorrectos
+locale: es
+kiStatus: Backlog
+internalReference: 926593
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el módulo Recogida, el filtro Especificaciones del producto no funciona correctamente cuando la especificación tiene el tipo "Texto" y "Texto grande". Cuando se selecciona este tipo de especificación, se abre un cuadro de texto para insertar los posibles valores separados por una coma, tabulador o enter. Sin embargo, cuando se teclea un solo carácter, el sistema lo asume como valor incluso sin separar los términos.
+
+
+##
+
+## Simulación
+
+
+
+1. Cree una Especificación de Producto con el tipo "Texto"
+2. Vaya al Módulo de Recogida, haga clic en el filtro "Más", seleccione "Especificación de Producto"
+3. Localice la especificación que ha creado y escriba cualquier cosa, verá que incluso un solo carácter se convertirá en un término de búsqueda
+
+
+
+## Workaround
+
+
+Continúe escribiendo hasta completar el término y, a continuación, elimine los términos incorrectos
+
+
+
+
+
diff --git a/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md b/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
new file mode 100644
index 000000000..5b69b6890
--- /dev/null
+++ b/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
@@ -0,0 +1,48 @@
+---
+title: 'El filtro de especificación de productos del módulo de recogida no enumera la categoría raíz'
+id: 6ZDaMBc9G5TtuwMJ5b0nuK
+status: PUBLISHED
+createdAt: 2023-10-12T14:29:57.985Z
+updatedAt: 2023-10-12T14:29:58.698Z
+publishedAt: 2023-10-12T14:29:58.698Z
+firstPublishedAt: 2023-10-12T14:29:58.698Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-filtro-de-especificacion-de-productos-del-modulo-de-recogida-no-enumera-la-categoria-raiz
+locale: es
+kiStatus: Backlog
+internalReference: 918687
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el módulo de recogida, al utilizar los filtros para añadir productos, el filtro Especificación de producto no lista los campos registrados en la categoría raíz
+
+
+##
+
+## Simulación
+
+
+
+- En una colección, en la opción "Más", seleccione el filtro Especificación de productos
+- Se abrirá un nuevo campo "Escriba una categoría"
+- Intente encontrar la categoría raíz
+
+
+
+## Workaround
+
+
+Utilice los otros filtros del módulo, importe los productos a través de una hoja de cálculo o añada productos individualmente en la interfaz de usuario.
+
+
+
+
diff --git a/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
new file mode 100644
index 000000000..dfdc57600
--- /dev/null
+++ b/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -0,0 +1,49 @@
+---
+title: 'La importación de especificaciones de producto con el tipo "texto" no activa la indexación del producto.'
+id: 5eQB7LCCyDbVNQBQvWti33
+status: PUBLISHED
+createdAt: 2024-03-12T19:36:58.647Z
+updatedAt: 2024-03-12T19:36:59.477Z
+publishedAt: 2024-03-12T19:36:59.477Z
+firstPublishedAt: 2024-03-12T19:36:59.477Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-importacion-de-especificaciones-de-producto-con-el-tipo-texto-no-activa-la-indexacion-del-producto
+locale: es
+kiStatus: Backlog
+internalReference: 998658
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al importar especificaciones de producto, los tipos con valores pre-registrados (como Checkbox o Radio) activan la indexación del producto, pero cuando el tipo es "Texto" no ocurre lo mismo.
+
+
+##
+
+## Simulación
+
+
+
+- Registrar un campo con el tipo texto dentro de la categoría
+- Importar un archivo con un nuevo valor
+- Tenga en cuenta que el valor se actualizará en el Admin, pero el producto no se reindexará
+
+
+
+## Workaround
+
+
+Configure este tipo de campo a través de Admin o API
+
+
+
+
+
diff --git a/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md b/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
index 3c6384002..78e5c47ba 100644
--- a/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
+++ b/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
@@ -3,8 +3,8 @@ title: 'El valor del TaxPercentage del producto guardado por el search-resolver
 id: 5zalMbGTuKaxpepVEdW3Dt
 status: PUBLISHED
 createdAt: 2022-03-21T17:38:14.386Z
-updatedAt: 2022-11-25T22:12:35.742Z
-publishedAt: 2022-11-25T22:12:35.742Z
+updatedAt: 2024-02-16T20:27:03.136Z
+publishedAt: 2024-02-16T20:27:03.136Z
 firstPublishedAt: 2022-03-21T17:38:14.760Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: el-valor-del-taxpercentage-del-producto-guardado-por-el-searchresolver-es-incorrecto-debido-al-redondeo
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 470143
 ---
 
diff --git a/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md b/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
index 8fbe026a0..b8fd1b88c 100644
--- a/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
+++ b/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
@@ -3,8 +3,8 @@ title: 'Los productos no se emparejan correctamente cuando el productName contie
 id: 7Kr0VtRScH54j04Rh2uuOj
 status: PUBLISHED
 createdAt: 2023-03-01T18:55:20.183Z
-updatedAt: 2023-03-01T18:55:20.910Z
-publishedAt: 2023-03-01T18:55:20.910Z
+updatedAt: 2023-10-19T12:08:30.076Z
+publishedAt: 2023-10-19T12:08:30.076Z
 firstPublishedAt: 2023-03-01T18:55:20.910Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: los-productos-no-se-emparejan-correctamente-cuando-el-productname-contiene-numeros
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 762525
 ---
 
@@ -35,7 +35,17 @@ Sin embargo, esta búsqueda no siempre funciona cuando en este Nombre de product
 
 
 
+1. El vendedor envía los skus al mercado con números en el Nombre del Producto;
+2. Los skus se aprobarán por separado (en lugar de tener una coincidencia) en el catálogo del marketplace.
+
+
+
 ## Workaround
 
 
+Envíe el producto sin números en su nombre.
+
+
+
+
 
diff --git a/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md b/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md
new file mode 100644
index 000000000..c0ea9906a
--- /dev/null
+++ b/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md
@@ -0,0 +1,45 @@
+---
+title: 'Productos que muestran la bandera y el descuento tras finalizar la promoción'
+id: 21qXD9XIfaxsxCH4jMGLJX
+status: PUBLISHED
+createdAt: 2024-06-07T19:50:09.302Z
+updatedAt: 2024-06-07T19:50:10.154Z
+publishedAt: 2024-06-07T19:50:10.154Z
+firstPublishedAt: 2024-06-07T19:50:10.154Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: productos-que-muestran-la-bandera-y-el-descuento-tras-finalizar-la-promocion
+locale: es
+kiStatus: Backlog
+internalReference: 383911
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+A veces las banderas de promoción y los descuentos se muestran en PLP y PLP después de la fecha de caducidad de la promoción. Esto ocurre porque la promoción no activa la indexación del producto, resultando en la exposición errónea del descuento.
+
+
+##
+
+## Simulación
+
+
+1- Crear una promoción con una bandera
+2- Fije una fecha de caducidad
+3- Comprobar que la promoción sigue activa en PLP y PDP
+
+
+
+
+## Workaround
+
+
+Reindexar los productos incluidos en la promoción
+
diff --git a/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md b/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
new file mode 100644
index 000000000..60d08408d
--- /dev/null
+++ b/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
@@ -0,0 +1,45 @@
+---
+title: 'Productos con precio cero mostrados como no disponibles en Búsqueda Inteligente'
+id: 4oh4ROvCp7JrfWeSAc0dE0
+status: PUBLISHED
+createdAt: 2024-06-05T23:34:05.987Z
+updatedAt: 2024-06-05T23:34:07.147Z
+publishedAt: 2024-06-05T23:34:07.147Z
+firstPublishedAt: 2024-06-05T23:34:07.147Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: productos-con-precio-cero-mostrados-como-no-disponibles-en-busqueda-inteligente
+locale: es
+kiStatus: Backlog
+internalReference: 1045184
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Los productos con precio cero son mostrados como no disponibles por la Búsqueda Inteligente. A diferencia de un producto sin precio registrado, el precio fijado como cero define un producto libre.
+
+
+##
+
+## Simulación
+
+
+Es posible simular el escenario simplemente cambiando su precio a "$ 0,00". Afectará al frontend de los resultados de búsqueda y a las APIs.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md b/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
new file mode 100644
index 000000000..fbb0bf813
--- /dev/null
+++ b/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
@@ -0,0 +1,50 @@
+---
+title: 'Los productos con variaciones de sku aprobadas en Skus Recibidos se están creando con skus duplicados en el Catálogo.'
+id: 2RqrBOeHDBZmfmqe6Rowl2
+status: PUBLISHED
+createdAt: 2023-08-29T15:50:44.042Z
+updatedAt: 2023-08-29T15:50:44.976Z
+publishedAt: 2023-08-29T15:50:44.976Z
+firstPublishedAt: 2023-08-29T15:50:44.976Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: los-productos-con-variaciones-de-sku-aprobadas-en-skus-recibidos-se-estan-creando-con-skus-duplicados-en-el-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 889676
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El vendedor puede enviar un producto con múltiples variaciones de sku.
+En el módulo Skus Recibidos del marketplace estos skus aparecerán por separado para ser aprobados.
+El vendedor puede aprobar manualmente estos skus.
+
+El escenario que está ocurriendo es que algunos de los skus se están creando duplicados en el catálogo del marketplace debido a un fallo en la comunicación del catálogo.
+
+
+
+## Simulación
+
+
+Aprobar skus en el área pendiente de Skus Recibidos del mismo producto en un intervalo corto de tiempo.
+Comprobar en el catálogo si algún sku se ha creado duplicado
+
+
+
+## Workaround
+
+
+Apruebe lentamente los skus del mismo producto para evitar errores en el catálogo.
+
+
+
+
+
diff --git a/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
new file mode 100644
index 000000000..92ebef841
--- /dev/null
+++ b/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -0,0 +1,48 @@
+---
+title: 'Productos con "unitMultiplier" marcados erróneamente como "con promoción" para los filtros de búsqueda'
+id: 2rCi8K01DHsNuYsefE7oR2
+status: PUBLISHED
+createdAt: 2024-02-15T22:52:17.434Z
+updatedAt: 2024-02-15T22:52:18.189Z
+publishedAt: 2024-02-15T22:52:18.189Z
+firstPublishedAt: 2024-02-15T22:52:18.189Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: productos-con-unitmultiplier-marcados-erroneamente-como-con-promocion-para-los-filtros-de-busqueda
+locale: es
+kiStatus: Backlog
+internalReference: 982830
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Un producto cuyo precio de venta sea inferior a su precio de lista será marcado como parte de una promoción a efectos de filtrado de búsqueda. Los productos con algún multiplicador de unidades pueden dar lugar a un cálculo erróneo que puede afectar a esta comparación, dando lugar a que reciban erróneamente esta bandera.
+
+
+##
+
+## Simulación
+
+
+La simulación depende de la aparición de problemas específicos de redondeo, pero un ejemplo de ello es un producto con un precio de lista y un precio normal de 264,20 $ y un multiplicador de unidades de 3,07.
+
+Aunque el precio de lista y el precio normal sean iguales, este artículo se devolverá en el filtro de búsqueda "promotion=yes".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md b/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
index fb322350c..3ae184535 100644
--- a/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
+++ b/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
@@ -3,8 +3,8 @@ title: 'Los productos sin stock en los vendedores de marca blanca aparecen en el
 id: 5WCKWky2gKGTZyp9ydnFnL
 status: PUBLISHED
 createdAt: 2022-04-20T15:52:50.807Z
-updatedAt: 2022-11-25T21:57:51.904Z
-publishedAt: 2022-11-25T21:57:51.904Z
+updatedAt: 2024-07-01T18:48:10.012Z
+publishedAt: 2024-07-01T18:48:10.012Z
 firstPublishedAt: 2022-04-20T15:52:51.421Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: los-productos-sin-stock-en-los-vendedores-de-marca-blanca-aparecen-en-el-final-de-la-plp
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 495741
 ---
 
diff --git a/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md b/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md
index 967a77661..58a8833a0 100644
--- a/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md
+++ b/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md
@@ -3,8 +3,8 @@ title: 'El formulario de carga de productos/SKU permite cargar/descargar el form
 id: 3NSxmGXvgFKHd2C4v2EwWV
 status: PUBLISHED
 createdAt: 2022-06-08T20:04:18.508Z
-updatedAt: 2022-11-25T22:12:28.497Z
-publishedAt: 2022-11-25T22:12:28.497Z
+updatedAt: 2024-02-16T20:26:55.864Z
+publishedAt: 2024-02-16T20:26:55.864Z
 firstPublishedAt: 2022-06-08T20:04:19.062Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: el-formulario-de-carga-de-productossku-permite-cargardescargar-el-formato-utf16
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 493402
 ---
 
diff --git a/docs/known-issues/es/productsskus-import-does-not-support-lb.md b/docs/known-issues/es/productsskus-import-does-not-support-lb.md
index 1ded49885..791faebfe 100644
--- a/docs/known-issues/es/productsskus-import-does-not-support-lb.md
+++ b/docs/known-issues/es/productsskus-import-does-not-support-lb.md
@@ -3,8 +3,8 @@ title: "La importación de productos&SKUs no es compatible con 'lb'"
 id: 1OjtnFf9MpY1IFzQa8Ua2t
 status: PUBLISHED
 createdAt: 2022-06-17T19:38:17.726Z
-updatedAt: 2023-01-05T20:03:49.367Z
-publishedAt: 2023-01-05T20:03:49.367Z
+updatedAt: 2024-02-16T20:29:45.337Z
+publishedAt: 2024-02-16T20:29:45.337Z
 firstPublishedAt: 2022-06-17T19:38:18.052Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-importacion-de-productosskus-no-es-compatible-con-lb
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 337860
 ---
 
diff --git a/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md b/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
new file mode 100644
index 000000000..913345533
--- /dev/null
+++ b/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
@@ -0,0 +1,50 @@
+---
+title: "Los datos del perfil se cargan vacíos en la interfaz de usuario para un perfil completo con 'ignoreProfileData'."
+id: 10B1QKgN42sjapDEALmKOp
+status: PUBLISHED
+createdAt: 2024-04-15T11:41:06.841Z
+updatedAt: 2024-04-15T11:41:07.691Z
+publishedAt: 2024-04-15T11:41:07.691Z
+firstPublishedAt: 2024-04-15T11:41:07.691Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-datos-del-perfil-se-cargan-vacios-en-la-interfaz-de-usuario-para-un-perfil-completo-con-ignoreprofiledata
+locale: es
+kiStatus: Backlog
+internalReference: 1016582
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al configurar 'ignoreProfileData' a través de la API Ignorar datos de perfil en el pago, si el comprador tiene un perfil completo pero no ha iniciado sesión, los datos se cargarán vacíos en la interfaz de usuario.
+
+
+
+## Simulación
+
+
+
+- Enviar ignoreProfileData vía API Ignorar los datos de perfil en el pago;
+- Añadir un artículo al carrito;
+- Añadir un correo con un perfil completo; no se cargarán datos y requerirá inicio de sesión.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/jVk0tmcR7R4BmaEkDcCedJgBP/?name=image.png)
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md b/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
new file mode 100644
index 000000000..c34999c25
--- /dev/null
+++ b/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
@@ -0,0 +1,43 @@
+---
+title: 'El artículo de promoción no se mostrará dividido después de añadir los datos de preferencias del cliente'
+id: 3bme5oDKxbRyQzozUP6XNp
+status: PUBLISHED
+createdAt: 2023-06-12T20:09:11.042Z
+updatedAt: 2024-01-31T15:20:39.646Z
+publishedAt: 2024-01-31T15:20:39.646Z
+firstPublishedAt: 2023-06-12T20:09:11.600Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-articulo-de-promocion-no-se-mostrara-dividido-despues-de-anadir-los-datos-de-preferencias-del-cliente
+locale: es
+kiStatus: Backlog
+internalReference: 842575
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+- Añade artículos al carrito para conseguir uno gratis o con descuento (los artículos en promoción y los normales se dividirán);
+- Añadir datos de preferencias del cliente al orderForm (los artículos se agruparán).
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md b/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
new file mode 100644
index 000000000..679f00618
--- /dev/null
+++ b/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
@@ -0,0 +1,46 @@
+---
+title: 'La suscripción promocional con frecuencia de semana, mes y día no funciona en ciclos recurrentes'
+id: 70DNIBLC5kctaFZSLooOQ7
+status: PUBLISHED
+createdAt: 2024-01-12T17:00:50.068Z
+updatedAt: 2024-06-20T14:26:39.099Z
+publishedAt: 2024-06-20T14:26:39.099Z
+firstPublishedAt: 2024-01-12T17:00:50.823Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: la-suscripcion-promocional-con-frecuencia-de-semana-mes-y-dia-no-funciona-en-ciclos-recurrentes
+locale: es
+kiStatus: Backlog
+internalReference: 965484
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se establece una promoción de suscripción en el módulo de suscripción, el comerciante tiene la posibilidad de elegir la frecuencia con la que se aplicará esta promoción en la suscripción.
+
+Si la frecuencia elegida es "semana" o "día" o "mes", la promoción no se aplicará en los ciclos recurrentes, a pesar de la configuración.
+
+
+
+## Simulación
+
+
+
+1. Crear una promoción de suscripción que se aplique en el primer ciclo y en los ciclos recurrentes;
+2. Seleccione la frecuencia semana/día/mes
+3. Compruebe que los pedidos recurrentes no tienen la suscripción aplicada.
+
+
+
+## Workaround
+
+
+-
+
diff --git a/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md b/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
new file mode 100644
index 000000000..92974374b
--- /dev/null
+++ b/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
@@ -0,0 +1,55 @@
+---
+title: 'La tabla de precios promocionales en carros de la compra de gran tamaño puede afectar al rendimiento o provocar errores de tiempo de espera.'
+id: 22H47mc9qYLdzk2sFkbBut
+status: PUBLISHED
+createdAt: 2023-12-07T15:47:28.360Z
+updatedAt: 2023-12-07T15:57:49.789Z
+publishedAt: 2023-12-07T15:57:49.789Z
+firstPublishedAt: 2023-12-07T15:47:28.972Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: la-tabla-de-precios-promocionales-en-carros-de-la-compra-de-gran-tamano-puede-afectar-al-rendimiento-o-provocar-errores-de-tiempo-de-espera
+locale: es
+kiStatus: Backlog
+internalReference: 949389
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Cuando tenemos una tienda con tablas de precios promocionales creadas y grandes carros de compra aplicando las promociones, provoca ralentizaciones en el rendimiento de la compra y provoca errores de timeout en el carro.
+
+Cualquier acción en el carrito puede desencadenar errores, como añadir artículos, ediciones, introducir código postal, etc comprometerá el rendimiento de la compra.
+
+No podemos saber con precisión qué número de tablas de precios promocionales que se calculan en el carro o la cantidad de artículos añadidos en el carro comenzará a desencadenar los errores de tiempo de espera o ralentizar el rendimiento, de lo que se analizó que puede suceder con cualquier cantidad significativa.
+
+
+
+##
+
+## Simulación
+
+
+
+Crear varias tablas de precios promocionales y un carrito de la compra con muchos artículos (aquí no podemos señalar un número claro, como 50 o 100, depende de las promociones)
+
+
+
+## Workaround
+
+
+
+Desafortunadamente, no tenemos ninguna solución para esto,
+desactivar las promociones y utilizar el módulo de precios para insertar los precios ayudaría.
+
+
+
+
+
diff --git a/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md b/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
new file mode 100644
index 000000000..f4b586ecd
--- /dev/null
+++ b/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
@@ -0,0 +1,47 @@
+---
+title: 'Las promociones e impuestos restringidos por método de envío no funcionan para los vendedores de marca blanca'
+id: 3ue1kZdbX1mMFqPCkl0tC4
+status: PUBLISHED
+createdAt: 2023-08-09T13:25:02.168Z
+updatedAt: 2023-08-09T13:26:13.874Z
+publishedAt: 2023-08-09T13:26:13.874Z
+firstPublishedAt: 2023-08-09T13:25:02.698Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: las-promociones-e-impuestos-restringidos-por-metodo-de-envio-no-funcionan-para-los-vendedores-de-marca-blanca
+locale: es
+kiStatus: Backlog
+internalReference: 315485
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las promociones e impuestos restringidos por métodos de envío no funcionan para los Vendedores de Marca Blanca. No se aplicarán en la solicitud de simulación (utilizada para el carrito y el pago) porque la solicitud de marketplace no especifica la `selectedSla`, por lo que sus valores no se presentarán al usuario.
+
+Pero el proceso de creación del pedido enviará esta `selectedSla`, donde se calculará la promoción/impuesto y cambiarán los valores. Pero la divergencia entre la simulación y el proceso de creación del pedido puede bloquear la finalización de la compra, ya que el cliente pagará un valor, calculado en la solicitud de simulación, diferente del valor calculado en la creación del pedido.
+
+
+##
+
+## Simulación
+
+
+- crear un impuesto en el vendedor de etiqueta blanca que esté restringido a algún método de envío
+- crear un carrito en el marketplace que utilizará este vendedor, y seleccionar el método de envío especificado anteriormente
+
+El valor no se presentará y no se podrá crear el pedido.
+
+
+
+## Workaround
+
+
+No se conoce ninguna solución para restringir un impuesto o una promoción por método de envío en un vendedor de marca blanca.
+
diff --git a/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md b/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
index 53897be8e..b41049750 100644
--- a/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
+++ b/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
@@ -3,8 +3,8 @@ title: 'Las promociones por orden de formas de pago no aparecen en la página de
 id: HZ5IoCFFOhuxU0jQWkMPp
 status: PUBLISHED
 createdAt: 2019-08-13T20:45:50.232Z
-updatedAt: 2023-03-31T15:44:56.958Z
-publishedAt: 2023-03-31T15:44:56.958Z
+updatedAt: 2024-07-01T18:48:59.282Z
+publishedAt: 2024-07-01T18:48:59.282Z
 firstPublishedAt: 2019-08-13T21:10:58.244Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: las-promociones-por-orden-de-formas-de-pago-no-aparecen-en-la-pagina-del-producto
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 781523
 ---
 
diff --git a/docs/known-issues/es/promotions-microrounding-divergence.md b/docs/known-issues/es/promotions-microrounding-divergence.md
new file mode 100644
index 000000000..fa2fe08ea
--- /dev/null
+++ b/docs/known-issues/es/promotions-microrounding-divergence.md
@@ -0,0 +1,99 @@
+---
+title: 'Promociones divergencia microrredonda'
+id: 603ZTMtdgi9olc6UiWLfmX
+status: PUBLISHED
+createdAt: 2023-12-22T18:48:32.438Z
+updatedAt: 2023-12-22T18:48:33.176Z
+publishedAt: 2023-12-22T18:48:33.176Z
+firstPublishedAt: 2023-12-22T18:48:33.176Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: promociones-divergencia-microrredonda
+locale: es
+kiStatus: Backlog
+internalReference: 957369
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El módulo de promociones redondea los descuentos hasta en 3 dígitos significativos, lo que puede, en escenarios muy concretos, suponer ligeras divergencias en el precio final de un carrito.
+
+Por ejemplo, supongamos que tenemos el siguiente escenario de ejemplo:
+
+Artículo 1 - 10
+Artículo 2 - 20
+Artículo 3 - 32
+____________
+Total - 62
+
+Y 2 promociones aplicando en todos ellos:
+
+Promoción A - $15 OFF
+Promoción B - 10% DE DESCUENTO.
+
+
+Por lo general, el descuento que se calcula es secuencial, y el descuento por valor nominal es el primero:
+
+$62 - $15 = $47
+A continuación
+$47 * 0.9 = $42.3
+
+
+Sin embargo, los descuentos se distribuyen, incluso para el descuento nominal, proporcionalmente en el carro, por lo que lo que realmente sucede es:
+
+`artículo 1
+Valor original = 10
+Descuento nominal (15 * 10/62 del carrito) = -$2.41935484
+Descuento porcentual esperado (12.5806452 * 0.9) = -$1.25806452
+Descuento real porcentual = -$1.258
+
+Artículo 2
+Valor original = 20 $
+Descuento nominal (15 * 20/62 del carrito) = -$4.83870968
+Descuento porcentual esperado (15.1612903 * 0.9) = -$1.51612903
+Descuento real porcentual = -$1.516
+
+partida 3
+Valor original = 32
+Descuento nominal (15 * 32/62 del carro) = -$7.74193548
+Descuento porcentual esperado (24.2580645 * 0.9) = -$2.42580645
+Descuento real porcentual = -$2.426
+
+
+🔎 diferencia total: 0.00006452 + 0.000012903 + 0.000019355 = 0.0000270973
+
+Podemos ver, más arriba, que se creó una "micro" diferencia.
+
+Si se añadieran varios artículos, con precios distintos, a este carro de ejemplo, esta diferencia podría ascender a 1 céntimo (0,01) o más.
+
+
+
+##
+
+## Simulación
+
+
+Existen multitud de formas de recrear eventualmente el caso Afortunadamente, todas ellas son extremadamente específicas.
+
+Dado esto, es difícil replicar el problema, pero, sobre todo, es necesario crear un carrito con varios (~10+) artículos diferentes y todos ellos con 2+ promociones, idealmente, siendo una de ellas un descuento nominal y la otra, un descuento porcentual.
+
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
+
diff --git a/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md b/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
new file mode 100644
index 000000000..d5f937a23
--- /dev/null
+++ b/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
@@ -0,0 +1,42 @@
+---
+title: 'Las promociones dan lugar a una clasificación/filtrado erróneo por precio o descuento'
+id: 1qGJByINC3S7ibgiQccVcY
+status: PUBLISHED
+createdAt: 2023-08-28T17:51:44.627Z
+updatedAt: 2023-11-10T18:19:30.796Z
+publishedAt: 2023-11-10T18:19:30.796Z
+firstPublishedAt: 2023-08-28T17:55:21.450Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: authors_84
+tag: Intelligent Search
+slug: las-promociones-dan-lugar-a-una-clasificacion-filtrado-erroneo-por-precio-o
+locale: es
+kiStatus: Backlog
+internalReference: 888304
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+Las listas de productos y los resultados de búsqueda pueden estar mal ordenados/filtrados al utilizar la ordenación o el filtrado por precio o descuento si hay precios de artículos obsoletos a nivel de índice, incluso si el escaparate muestra el precio correcto.
+
+La ordenación de los productos se basa siempre en la información indexada previamente (datos fríos), mientras que el escaparate suele recalcular toda la información en tiempo de ejecución (datos calientes), por lo que los precios presentados son siempre correctos en relación con el carrito.
+
+Se espera que cada cambio de precio (e incluso otros cambios) haga que los artículos se vuelvan a indexar para que el índice esté actualizado con las nuevas condiciones. El problema es que el módulo de Promociones no soporta el envío de notificaciones al servicio de indexación cuando una promoción comienza o termina, lo que ocasionalmente resulta en precios de artículos desactualizados, donde el módulo de Búsqueda no es capaz de ordenar/filtrar los artículos correctamente en comparación con los precios en tiempo real.
+
+Cualquier acción que reindexe las condiciones comerciales del artículo (como cambios de stock) también actualizará orgánicamente su precio teniendo en cuenta la promoción, enmascarando finalmente el problema para algunos artículos.
+
+Las tiendas que utilicen `simulationBehavior=skip` no verán divergencias entre la clasificación de artículos y los filtros aplicados en el PLP, ya que este parámetro hace que se representen los "datos fríos" allí, pero aparecerán al comparar el mismo artículo en el PLP con su PDP, que funciona de forma fija como un `simulationBehavior=default`, recuperando información actualizada en tiempo de ejecución.
+
+## Simulación
+
+La forma más fácil de ver los efectos de este problema es tener una lista de productos ordenados por precio más bajo, crear una promoción para un producto en el medio de la lista, y ver que su ordenación no cambia después de activar la promoción, incluso cuando se vuelve más barato que otros productos.
+
+## Workaround
+
+N/A
+
diff --git a/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md b/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md
index fffc8853d..4884144e8 100644
--- a/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md
+++ b/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md
@@ -3,8 +3,8 @@ title: 'La interfaz de usuario de las promociones carga información incorrecta
 id: 7liSZOtS1Hs2P84bXzRrG9
 status: PUBLISHED
 createdAt: 2022-12-19T14:41:51.129Z
-updatedAt: 2022-12-19T14:41:51.903Z
-publishedAt: 2022-12-19T14:41:51.903Z
+updatedAt: 2024-02-15T12:11:06.893Z
+publishedAt: 2024-02-15T12:11:06.893Z
 firstPublishedAt: 2022-12-19T14:41:51.903Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: la-interfaz-de-usuario-de-las-promociones-carga-informacion-incorrecta-sobre-la-divisa
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 718908
 ---
 
@@ -23,8 +23,7 @@ internalReference: 718908
 </div>
 
 
-
-Al abrir el módulo Promociones muy rápidamente y muchas veces seguidas aparece un comportamiento erróneo en la UI.
+Al abrir el módulo de Promociones muy rápidamente y muchas veces seguidas aparece un comportamiento erróneo en la UI.
 
 El campo "Restringir esta promoción a los productos del vendedor" no carga el marcador de posición correcto, en su lugar carga el marcador de posición "GLOBAL SELECCIONA UN VENDEDOR..."
 
@@ -38,8 +37,17 @@ Al Guardar la promoción el valor final no es el esperado por el cliente.
 ## Simulación
 
 
+No hay una manera fácil de reproducir este escenario. A veces, al abrir el módulo de promociones en diferentes pestañas muy rápidamente se produce este comportamiento.
+Compruebe si el campo "Restringir esta promoción a los productos del vendedor" es diferente para saber que ha llegado al escenario.
+
+
 
 ## Workaround
 
 
+Cierre la interfaz de usuario de promociones actual y abra una nueva en la que no se produzca el comportamiento.
+
+
+
+
 
diff --git a/docs/known-issues/es/property-blockclass-from-infocard-not-working.md b/docs/known-issues/es/property-blockclass-from-infocard-not-working.md
index 196195c27..d9c21eb5c 100644
--- a/docs/known-issues/es/property-blockclass-from-infocard-not-working.md
+++ b/docs/known-issues/es/property-blockclass-from-infocard-not-working.md
@@ -3,8 +3,8 @@ title: 'Propiedad blockClass de infoCard no funciona'
 id: LTEEWCaZx2unBWSEJFDw6
 status: PUBLISHED
 createdAt: 2023-01-31T19:02:03.835Z
-updatedAt: 2023-01-31T19:02:04.299Z
-publishedAt: 2023-01-31T19:02:04.299Z
+updatedAt: 2024-07-01T18:48:42.227Z
+publishedAt: 2024-07-01T18:48:42.227Z
 firstPublishedAt: 2023-01-31T19:02:04.299Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: propiedad-blockclass-de-infocard-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 743730
 ---
 
diff --git a/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md b/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
new file mode 100644
index 000000000..3034be878
--- /dev/null
+++ b/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
@@ -0,0 +1,41 @@
+---
+title: 'Los gastos de envío proporcionales muestran valores negativos cuando hay promociones que fraccionan artículos y se aplican gastos de envío gratuitos.'
+id: 60gzoaN1WQC6OsEymBPdeq
+status: PUBLISHED
+createdAt: 2023-09-28T22:29:39.597Z
+updatedAt: 2023-09-28T22:33:53.751Z
+publishedAt: 2023-09-28T22:33:53.751Z
+firstPublishedAt: 2023-09-28T22:29:40.382Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-gastos-de-envio-proporcionales-muestran-valores-negativos-cuando-hay-promociones-que-fraccionan-articulos-y-se-aplican-gastos-de-envio-gratuitos
+locale: es
+kiStatus: Backlog
+internalReference: 909925
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Puede haber diferentes combinaciones que causen el problema, ya que el peso se utiliza para calcular los gastos de envío proporcionales, por lo que es difícil de reproducir.
+
+
+
+## Workaround
+
+
+Configure la promoción de envío gratuito para que la aplique el vendedor.
+
+
+
+
diff --git a/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md b/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md
index 22a8747ca..fe70ba900 100644
--- a/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md
+++ b/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md
@@ -3,8 +3,8 @@ title: 'El mensaje PT se muestra en el módulo License Manager'
 id: 6nC0EfB2pO2pIyH9HEDDAP
 status: PUBLISHED
 createdAt: 2022-07-19T19:02:51.412Z
-updatedAt: 2022-11-25T21:57:09.655Z
-publishedAt: 2022-11-25T21:57:09.655Z
+updatedAt: 2024-07-01T18:48:30.289Z
+publishedAt: 2024-07-01T18:48:30.289Z
 firstPublishedAt: 2022-07-19T19:02:52.298Z
 contentType: knownIssue
 productTeam: Identity
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Identity
 slug: el-mensaje-pt-se-muestra-en-el-modulo-license-manager
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 620782
 ---
 
diff --git a/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md b/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
index 49628b64f..a99c97965 100644
--- a/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
+++ b/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
@@ -3,8 +3,8 @@ title: '/pub/portal/pagetype no se mapea correctamente cuando 2+ categorías tie
 id: 7ykvMnWt3PhGAqWhEFmnp3
 status: PUBLISHED
 createdAt: 2022-03-18T15:40:04.430Z
-updatedAt: 2022-11-25T22:10:11.690Z
-publishedAt: 2022-11-25T22:10:11.690Z
+updatedAt: 2024-02-16T20:27:59.429Z
+publishedAt: 2024-02-16T20:27:59.429Z
 firstPublishedAt: 2022-03-18T15:40:04.877Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: pubportalpagetype-no-se-mapea-correctamente-cuando-2-categorias-tienen-el-mismo-nombre
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 314551
 ---
 
diff --git a/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
new file mode 100644
index 000000000..03aed88ee
--- /dev/null
+++ b/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -0,0 +1,48 @@
+---
+title: 'La compra no se puede finalizar y se queda atascada en "el tipo de carga ha cambiado"'
+id: mgewQ8QmZ3V3dkc7vdJkV
+status: PUBLISHED
+createdAt: 2023-09-25T13:28:28.121Z
+updatedAt: 2024-03-27T14:37:54.335Z
+publishedAt: 2024-03-27T14:37:54.335Z
+firstPublishedAt: 2023-09-25T13:28:28.557Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-compra-no-se-puede-finalizar-y-se-queda-atascada-en-el-tipo-de-carga-ha-cambiado
+locale: es
+kiStatus: Backlog
+internalReference: 449341
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar cualquier promoción que provoque la división de un artículo y se seleccionen dos vendedores diferentes, al hacer clic en "Comprar ahora" aparecerá el mensaje "El tipo de carga ha cambiado", lo que impedirá que se complete la compra.
+
+
+##
+
+## Simulación
+
+
+
+- Configure una promoción "más por menos" por ejemplo;
+- Añadir al carrito el artículo de la promoción;
+- Añada otro artículo de otro vendedor;
+- Intente finalizar la compra; se mostrará el mensaje "el tipo de carga ha cambiado".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/put-price-overwrites-kit-price-logic.md b/docs/known-issues/es/put-price-overwrites-kit-price-logic.md
index 6508b52d4..648104aac 100644
--- a/docs/known-issues/es/put-price-overwrites-kit-price-logic.md
+++ b/docs/known-issues/es/put-price-overwrites-kit-price-logic.md
@@ -1,16 +1,16 @@
 ---
-title: 'El precio de venta sobrescribe la lógica del precio del KIT'
+title: 'El precio de venta sobrescribe la lógica del precio KIT'
 id: 6eUXEJkxQUl6NCiFWrIiFw
 status: PUBLISHED
 createdAt: 2022-06-28T16:56:02.848Z
-updatedAt: 2022-11-25T22:12:23.543Z
-publishedAt: 2022-11-25T22:12:23.543Z
+updatedAt: 2023-11-09T13:43:40.623Z
+publishedAt: 2023-11-09T13:43:40.623Z
 firstPublishedAt: 2022-06-28T16:56:03.203Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
 author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
-slug: el-precio-de-venta-sobrescribe-la-logica-del-precio-del-kit
+slug: el-precio-de-venta-sobrescribe-la-logica-del-precio-kit
 locale: es
 kiStatus: Backlog
 internalReference: 404486
@@ -23,12 +23,33 @@ internalReference: 404486
 </div>
 
 
+La composición del precio del KIT debe basarse en el cálculo de sus componentes y sus cantidades.
+
+Es decir, el precio de un KIT debe ser:
+`Precio_KKU_KIT= (componente_1*cantidad_1) + (componente_2*cantidad_2) + (...) + (componente_n*cantidad_n)`.
+
+Sin embargo, actualmente existe una forma de evitar esta lógica si el usuario inserta un Precio PUT directamente en el sku del kit en el Módulo de Precios.
+
+
+
 
 ## Simulación
 
 
 
+1. Crea un KIT con al menos 2 componentes y establece su precio y cantidades;
+2. 2. Compruebe que el precio del KIT se establece de acuerdo con la lógica mencionada anteriormente.
+3. Actualice el precio del KIT en el módulo de precios insertando un PUT Price en el sku del kit;
+4. 4. Verifique que aun cuando se actualicen los componentes del precio y sus cantidades, el precio del KIT permanezca como el precio put establecido anteriormente.
+
+
+
 ## Workaround
 
 
+Realice cualquier cambio en los componentes, un nuevo Precio PUT con el nuevo cálculo y la lógica correcta lo sobrescribirá de nuevo, normalizando entonces el comportamiento "erróneo".
+
+
+
+
 
diff --git a/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md b/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
index b3d53389d..541487239 100644
--- a/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
+++ b/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
@@ -3,8 +3,8 @@ title: 'El componente selector de cantidad no vuelve al valor límite cuando el
 id: 4QRAzY1A0UD8hOUEkxAawz
 status: PUBLISHED
 createdAt: 2022-09-16T16:27:15.880Z
-updatedAt: 2022-11-25T22:13:30.254Z
-publishedAt: 2022-11-25T22:13:30.254Z
+updatedAt: 2024-02-16T20:28:10.783Z
+publishedAt: 2024-02-16T20:28:10.783Z
 firstPublishedAt: 2022-09-16T16:27:16.745Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: el-componente-selector-de-cantidad-no-vuelve-al-valor-limite-cuando-el-usuario-hace-clic-rapidamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 659909
 ---
 
diff --git a/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md b/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md
new file mode 100644
index 000000000..d26e321c1
--- /dev/null
+++ b/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md
@@ -0,0 +1,51 @@
+---
+title: 'El Selector de Cantidad no me permite cambiar el valor escribiendo'
+id: 4whARKlTiLQhTluJrIRfO5
+status: PUBLISHED
+createdAt: 2024-06-28T15:01:34.187Z
+updatedAt: 2024-07-05T16:17:08.672Z
+publishedAt: 2024-07-05T16:17:08.672Z
+firstPublishedAt: 2024-06-28T15:01:35.225Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: el-selector-de-cantidad-no-me-permite-cambiar-el-valor-escribiendo
+locale: es
+kiStatus: Fixed
+internalReference: 1057544
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El componente selector de cantidades en Faststore está presentando un bug. Si el valor mínimo de un producto es 10 y quiero teclear 15, el selector no me deja borrar el 0 porque nos dejará con 1, y sería un valor inferior a la cantidad mínima. Si quiero escribir 15 tengo que escribir 150 y entonces puedo borrar el 0.
+
+
+##
+
+## Simulación
+
+
+Puedes probarlo en nuestra tienda por defecto en nuestra página de documentación:
+https://developers.vtex.com/docs/guides/faststore/molecules-quantity-selector
+https://starter.vtex.app/handmade-plastic-chips-9009169/p
+
+En este caso, el valor mínimo es 1 y el valor máximo es 10.
+Intenta escribir 2 borrando el valor 1, no te dejará porque una vez borrado el 1, el valor será menor que el valor mínimo.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md b/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
index 09ccec75e..7633a8c79 100644
--- a/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
+++ b/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
@@ -3,8 +3,8 @@ title: 'El selector de cantidad en modo paso a paso no se actualiza después de
 id: 77bK8oIAPR8LEMtOn6QEqs
 status: PUBLISHED
 createdAt: 2022-12-23T12:20:23.568Z
-updatedAt: 2022-12-23T12:20:24.148Z
-publishedAt: 2022-12-23T12:20:24.148Z
+updatedAt: 2024-02-16T20:27:43.811Z
+publishedAt: 2024-02-16T20:27:43.811Z
 firstPublishedAt: 2022-12-23T12:20:24.148Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: el-selector-de-cantidad-en-modo-paso-a-paso-no-se-actualiza-despues-de-alcanzar-la-maxima-cantidad-disponible
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 704458
 ---
 
diff --git a/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index adec58422..32c4e476e 100644
--- a/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -20,7 +20,7 @@ internalReference:
 
 Actualmente, el escenario de exhibición de las opciones "Recibir | Retirar" está condicionado a la búsqueda del código postal en cualquiera de las pestañas. Esto significa que, si se busca en la pestaña "Recibir" un código postal que no se atienda en un punto de recogida, la pestaña "Retirar" no se mostrará al usuario.
 
-![Captura de Pantalla 2018-11-21 a las  14.25.40](https://images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png)
+![Captura de Pantalla 2018-11-21 a las  14.25.40](//images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png)
 
 
 ## Simulación
diff --git a/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md b/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
index 1f8df390a..d4f0c4432 100644
--- a/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
+++ b/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
@@ -3,8 +3,8 @@ title: 'Skus recibidos: Las aprobaciones de asociación no añaden el canal de v
 id: 5ob4jquCm8l84MhX6285h8
 status: PUBLISHED
 createdAt: 2022-04-18T17:15:41.091Z
-updatedAt: 2023-05-09T19:06:08.893Z
-publishedAt: 2023-05-09T19:06:08.893Z
+updatedAt: 2024-02-16T20:25:58.313Z
+publishedAt: 2024-02-16T20:25:58.313Z
 firstPublishedAt: 2022-04-18T17:15:41.436Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: skus-recibidos-las-aprobaciones-de-asociacion-no-anaden-el-canal-de-ventas-disponible-del-vendedor-en-el-producto-cuando-el-sku-es-vendido-por-mas-de-1-vendedor
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 562472
 ---
 
diff --git a/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md b/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md
new file mode 100644
index 000000000..2353f6b07
--- /dev/null
+++ b/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md
@@ -0,0 +1,52 @@
+---
+title: 'El filtro Skus recibidos no funciona con caracteres especiales'
+id: 6aSErtF2Xv5RuKuIHUEEPg
+status: PUBLISHED
+createdAt: 2023-11-29T17:58:26.201Z
+updatedAt: 2023-11-29T17:58:26.900Z
+publishedAt: 2023-11-29T17:58:26.900Z
+firstPublishedAt: 2023-11-29T17:58:26.900Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: el-filtro-skus-recibidos-no-funciona-con-caracteres-especiales
+locale: es
+kiStatus: Backlog
+internalReference: 944533
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar filtrar los skus en el módulo de Skus Recibidos, el marketplace puede elegir filtrar por vendedor, categoría y/o marca.
+
+Sin embargo, cuando se selecciona una marca que tiene caracteres especiales (como "&" o "+") el resultado es que no hay skus en ese filtro, lo que en realidad no es correcto.
+
+
+##
+
+## Simulación
+
+
+
+1. Filtrar por una de las opciones del módulo Skus recibidos;
+2. Seleccionar un valor con carácter especial;
+3. Comprobar que el resultado es sin skus;
+4. Ahora busque por el valor en la búsqueda y compruebe que efectivamente hay algún skus.
+
+
+
+## Workaround
+
+
+No hay solución para arreglar el filtro, pero utilizando la búsqueda podría traer un resultado cercano de los skus.
+
+
+
+
+
diff --git a/docs/known-issues/es/received-skus-review-tab-missing-products.md b/docs/known-issues/es/received-skus-review-tab-missing-products.md
new file mode 100644
index 000000000..54e774d69
--- /dev/null
+++ b/docs/known-issues/es/received-skus-review-tab-missing-products.md
@@ -0,0 +1,54 @@
+---
+title: 'Recibidos Skus "Revisión" ficha productos que faltan'
+id: 2UM0JQUZVq5o7NHCjmrg8N
+status: PUBLISHED
+createdAt: 2023-11-23T16:30:51.874Z
+updatedAt: 2024-02-01T12:54:26.917Z
+publishedAt: 2024-02-01T12:54:26.917Z
+firstPublishedAt: 2023-11-23T16:30:52.647Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: recibidos-skus-revision-ficha-productos-que-faltan
+locale: es
+kiStatus: Fixed
+internalReference: 939877
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las ofertas enviadas por los vendedores pueden eventualmente ir a la pestaña de Revisión de los Skus Recibidos del Marketplace dependiendo si pasaron o no las reglas de Calidad de la Oferta.
+
+Una vez en esta pestaña, el vendedor puede actualizar sus skus con la información correcta (o cualquier información nueva).
+
+Sin embargo, cuando esto ocurre, el sku cambia su estado de "EsperandoRevisión" a "Revisado", desapareciendo de la pestaña Revisión y de todos los Skus Recibidos.
+
+
+##
+
+## Simulación
+
+
+
+1. Establezca una regla de "Requisitos opcionales" en el módulo de Calidad de la oferta en el lado del mercado;
+2. Esperar a que un sku vaya a la pestaña Revisar por no pasar la regla;
+3. Espera a que se actualice un sku en el lado del vendedor;
+4. 4. Comprobar que el sku ya no está en la pestaña Revisión.
+
+
+
+## Workaround
+
+
+Aprobar el producto a través de la API: https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerskuid-/versions/-version-/matches/-matchid-
+
+
+
+
+
diff --git a/docs/known-issues/es/redirects-are-being-counted-multiple-times.md b/docs/known-issues/es/redirects-are-being-counted-multiple-times.md
new file mode 100644
index 000000000..a2fd35390
--- /dev/null
+++ b/docs/known-issues/es/redirects-are-being-counted-multiple-times.md
@@ -0,0 +1,51 @@
+---
+title: 'Los redireccionamientos se cuentan varias veces'
+id: 51JfHBdp72duH5cBWMYl0t
+status: PUBLISHED
+createdAt: 2024-07-16T19:48:36.586Z
+updatedAt: 2024-07-16T19:49:42.290Z
+publishedAt: 2024-07-16T19:49:42.290Z
+firstPublishedAt: 2024-07-16T19:48:37.314Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: los-redireccionamientos-se-cuentan-varias-veces
+locale: es
+kiStatus: Backlog
+internalReference: 1066548
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar cargar un archivo con más de 200 redirecciones, el frente entra en un bucle y lee esas redirecciones tres veces. Esto puede llevar a más redirecciones en el mensaje de error en pantalla o en el modal de carga. Las redirecciones no se están duplicando, pero las estamos leyendo más de una vez.
+
+
+##
+
+## Simulación
+
+
+Pruebe a cargar un archivo con 930 redirecciones, por ejemplo. El modal de carga aparecerá con un número superior a 930:
+ ![](https://vtexhelp.zendesk.com/attachments/token/vypbPdcFp4KtjVvI5rL4tHQXU/?name=image.png)
+
+si el archivo contiene un error, puedes encontrar un mensaje de error similar a este:
+ ![](https://vtexhelp.zendesk.com/collaboration/graphql/attachments/download/s3-145778c5-53eb-4002-9b91-1b43f7394896/image.png)
+Esto es sólo un error frontal, y no está afectando a la carga de redirecciones en sí.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md b/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
new file mode 100644
index 000000000..8dc6e1b89
--- /dev/null
+++ b/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
@@ -0,0 +1,47 @@
+---
+title: 'Redirecciones para los enlaces de previsualización cuando se utiliza / en la parte final de la URL'
+id: 7mO7pEA0DMclbWy2pPPUkd
+status: PUBLISHED
+createdAt: 2023-10-27T19:00:01.248Z
+updatedAt: 2023-10-27T19:00:01.916Z
+publishedAt: 2023-10-27T19:00:01.916Z
+firstPublishedAt: 2023-10-27T19:00:01.916Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: redirecciones-para-los-enlaces-de-previsualizacion-cuando-se-utiliza-en-la-parte-final-de-la-url
+locale: es
+kiStatus: Backlog
+internalReference: 927041
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En Faststore, si accede a un enlace de previsualización con el / al final de la URL el enlace será redirigido a una página como esta https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
+
+
+##
+
+## Simulación
+
+
+Intente acceder a una página de previsualización de Faststore con un / al final de la URL, como https://starter.vtex.app/s/
+Se le redirigirá a https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md b/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md
new file mode 100644
index 000000000..797c41328
--- /dev/null
+++ b/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md
@@ -0,0 +1,50 @@
+---
+title: 'El comportamiento de RefId no es coherente entre la API y la interfaz de usuario'
+id: 4007iEJ8bCN96PBY0nsIB4
+status: PUBLISHED
+createdAt: 2023-09-29T13:11:04.826Z
+updatedAt: 2023-10-20T13:41:48.679Z
+publishedAt: 2023-10-20T13:41:48.679Z
+firstPublishedAt: 2023-09-29T13:11:05.384Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-comportamiento-de-refid-no-es-coherente-entre-la-api-y-la-interfaz-de-usuario
+locale: es
+kiStatus: Backlog
+internalReference: 910050
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos dos comportamientos para el código refid, vía API no es posible que sea el mismo que otros productos, pero vía UI nos permite insertar el mismo valor que ya tienen otros productos.
+
+
+##
+
+## Simulación
+
+
+
+Crear un producto con un código redIf
+Cree otro producto e intente utilizar el mismo código refId que el otro, vía API no será posible pero vía UI sí.
+
+
+
+## Workaround
+
+
+
+Si necesita utilizar los mismos refIds para diferentes productos, introdúzcalos a través de la interfaz de usuario.
+
+
+
+
+
diff --git a/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md b/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
new file mode 100644
index 000000000..af099feeb
--- /dev/null
+++ b/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
@@ -0,0 +1,52 @@
+---
+title: 'Un conflicto de Regex hace que identifiquemos erróneamente Mastercard como Visa'
+id: MzUm8xH6vDeGxWcj6GCbZ
+status: PUBLISHED
+createdAt: 2023-09-04T17:51:08.019Z
+updatedAt: 2023-11-30T15:25:47.066Z
+publishedAt: 2023-11-30T15:25:47.066Z
+firstPublishedAt: 2023-09-04T17:51:09.705Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: un-conflicto-de-regex-hace-que-identifiquemos-erroneamente-mastercard-como-visa
+locale: es
+kiStatus: Backlog
+internalReference: 893588
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Un conflicto de Regex hace que identifiquemos erróneamente la marca de las tarjetas en la caja.
+
+
+##
+
+## Simulación
+
+
+
+1. Configure dos Condiciones de Pago una para el procesamiento de tarjetas de crédito Visa y otra para el procesamiento de tarjetas de crédito Mastercard
+2. Compra un artículo al azar en la tienda y elige pagarlo con tarjeta de crédito.
+3. Rellene el número de tarjeta con el BIN 523431 de Mastercard y complete con números aleatorios.
+4. Rellena el resto de información de la tarjeta con datos falsos
+5. Finalizar la compra
+6. Vaya a admin y busque la transacción ya creada y el pago se identificará como Visa en lugar de Mastercard
+
+
+
+## Workaround
+
+
+N/D
+
+
+
+
+
diff --git a/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md b/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md
new file mode 100644
index 000000000..88145c2c0
--- /dev/null
+++ b/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md
@@ -0,0 +1,48 @@
+---
+title: 'La API de la región devuelve la lista de vendedores debido a la caché'
+id: 1uDscW8Z3tG4EXS23fCfci
+status: PUBLISHED
+createdAt: 2024-01-22T17:34:18.690Z
+updatedAt: 2024-01-22T17:48:47.576Z
+publishedAt: 2024-01-22T17:48:47.576Z
+firstPublishedAt: 2024-01-22T17:34:19.518Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-api-de-la-region-devuelve-la-lista-de-vendedores-debido-a-la-cache
+locale: es
+kiStatus: Backlog
+internalReference: 969692
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza una estructura de subcuenta con región, si la API Obtener vendedores por región o dirección se utiliza en ambas cuentas para el mismo canal de ventas, y una de ellas no está disponible para ese canal de ventas, devolverá una lista de vendedores debido a la caché.
+
+
+##
+
+## Simulación
+
+
+
+- Crear una nueva tienda;
+- Establecer diferentes canales de venta para la tienda;
+- Utilizar la API Obtener vendedores por región o dirección en la tienda;
+- Utilizar de nuevo la API para el mismo canal de ventas en la otra tienda.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 5ddcd5c90..390ae0e81 100644
--- a/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,10 +1,10 @@
 ---
 title: 'La API de Regions no calcula correctamente el "seller 1" al solicitar sellers que no son white label'
 id: 20sT9AMMi7Ob5IZc7FeiCB
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
-updatedAt: 2022-11-25T21:53:57.112Z
-publishedAt: 2022-11-25T21:53:57.112Z
+updatedAt: 2024-03-14T13:47:34.269Z
+publishedAt: 
 firstPublishedAt: 2022-03-28T20:45:28.144Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md b/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
new file mode 100644
index 000000000..8b17c1004
--- /dev/null
+++ b/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
@@ -0,0 +1,50 @@
+---
+title: 'Los usuarios registrados (que no han iniciado sesión) no pueden finalizar el proceso de pago cuando cambian de entrega a recogida en la página de pago.'
+id: hmQ2riW1Ptjxyhk6gcWxN
+status: PUBLISHED
+createdAt: 2023-07-28T19:49:16.993Z
+updatedAt: 2024-04-17T15:46:57.958Z
+publishedAt: 2024-04-17T15:46:57.958Z
+firstPublishedAt: 2023-07-28T19:49:17.732Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: los-usuarios-registrados-que-no-han-iniciado-sesion-no-pueden-finalizar-el-proceso-de-pago-cuando-cambian-de-entrega-a-recogida-en-la-pagina-de-pago
+locale: es
+kiStatus: Fixed
+internalReference: 870845
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario registrado (no logueado) inicia el checkout con Entrega como opción de envío, y posteriormente cambia a recolección, al intentar finalizar el checkout aparece el mensaje de error "El campo Número en el adjunto de envío no es válido" y no permite realizar el pedido.
+
+
+##
+
+## Simulación
+
+
+
+1. Ir a la caja y añadir un nuevo artículo
+2. Introduzca un código postal para calcular el envío y mantenga **Entrega** seleccionado
+3. Cuando se le pida que introduzca una dirección de correo electrónico, utilice la de un usuario registrado.
+4. En la caja aparecerá un mensaje emergente informando de que sus datos personales han sido recuperados de compras anteriores
+5. 5. Cambie de Entrega a Recogida e intente completar el pedido (aparecerá el mensaje de error)
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md b/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
index 2f468ebde..40353c513 100644
--- a/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
+++ b/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
@@ -3,8 +3,8 @@ title: 'Eliminar el EAN a través de la API no es desactivar las SKU sin RefID'
 id: 2DIKKs93S41F38c3PrekSO
 status: PUBLISHED
 createdAt: 2022-08-01T11:37:52.731Z
-updatedAt: 2022-11-25T21:44:12.277Z
-publishedAt: 2022-11-25T21:44:12.277Z
+updatedAt: 2024-07-01T18:48:35.030Z
+publishedAt: 2024-07-01T18:48:35.030Z
 firstPublishedAt: 2022-08-01T11:37:53.288Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: eliminar-el-ean-a-traves-de-la-api-no-es-desactivar-las-sku-sin-refid
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 626031
 ---
 
diff --git a/docs/known-issues/es/render-component-issues-on-site-editor.md b/docs/known-issues/es/render-component-issues-on-site-editor.md
index c0d3d7b25..73581451d 100644
--- a/docs/known-issues/es/render-component-issues-on-site-editor.md
+++ b/docs/known-issues/es/render-component-issues-on-site-editor.md
@@ -3,8 +3,8 @@ title: 'Problemas con los componentes de renderizado en el editor de sitios'
 id: 66gcFw8LwnL6WsvuXPRzFn
 status: PUBLISHED
 createdAt: 2022-04-19T19:41:08.520Z
-updatedAt: 2023-03-10T14:17:10.739Z
-publishedAt: 2023-03-10T14:17:10.739Z
+updatedAt: 2024-06-21T12:24:51.158Z
+publishedAt: 2024-06-21T12:24:51.158Z
 firstPublishedAt: 2022-04-19T19:41:09.223Z
 contentType: knownIssue
 productTeam: CMS
@@ -23,7 +23,14 @@ internalReference: 415674
 </div>
 
 
-Este comportamiento ocurre de forma intermitente, a veces los componentes no se renderizan y a veces se renderizan dos veces en función de los clics en la página.
+Debido a la cantidad de información en la página, el editor del sitio puede tener problemas al renderizar bloques. Este comportamiento ocurre de forma intermitente, a veces los componentes no se renderizan y otras veces se renderizan dos veces. Puede ocurrir que no aparezca ningún bloque en el editor del sitio:
+ ![](https://vtexhelp.zendesk.com/attachments/token/miNCNkBPcmbXcVHmb9f5HWxIS/?name=image.png)
+
+O puede ocurrir que aparezcan menos bloques.
+
+También puede ocurrir que se produzca un retraso después de guardar un nuevo contenido. El contenido se guarda pero la pantalla se sigue cargando:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/BwlA7jzWiWCxYMLOGxMb0N84N/?name=image.png)
 
 
 ##
@@ -31,7 +38,9 @@ Este comportamiento ocurre de forma intermitente, a veces los componentes no se
 ## Simulación
 
 
-Pruebe a editar el Editor de Sitios, a veces no se renderiza y a veces algunos bloques se renderizan dos veces.
+1 - Prueba a editar el Editor de Sitios, a veces no se renderiza y a veces algunos bloques se renderizan dos veces.
+
+2 - Intente guardar un cambio de contenido, el contenido se guarda pero la pantalla seguirá cargando.
 
 
 
@@ -40,3 +49,5 @@ Pruebe a editar el Editor de Sitios, a veces no se renderiza y a veces algunos b
 
 No se conoce ninguna solución.
 
+
+
diff --git a/docs/known-issues/es/replacing-orders-with-different-sales-channel.md b/docs/known-issues/es/replacing-orders-with-different-sales-channel.md
new file mode 100644
index 000000000..f7b3078d7
--- /dev/null
+++ b/docs/known-issues/es/replacing-orders-with-different-sales-channel.md
@@ -0,0 +1,48 @@
+---
+title: 'Sustitución de pedidos por otro canal de ventas'
+id: 2gShXcwLLHu7R8JyPjP0W6
+status: PUBLISHED
+createdAt: 2024-02-16T13:02:17.686Z
+updatedAt: 2024-02-16T13:05:20.998Z
+publishedAt: 2024-02-16T13:05:20.998Z
+firstPublishedAt: 2024-02-16T13:02:18.609Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: sustitucion-de-pedidos-por-otro-canal-de-ventas
+locale: es
+kiStatus: Backlog
+internalReference: 982965
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Hemos identificado que no es posible reemplazar un SKU en el pedido si el Canal de Ventas (SC), igual a 1, no está disponible para la cuenta.
+
+Por ejemplo, la cuenta A no tiene canal de ventas=1, sólo SC=2, en la solicitud de sustitución de pedido estamos enviando canal de ventas=1 y no 2.
+
+
+##
+
+## Simulación
+
+
+La cuenta A, no tiene canal de ventas=1, solo SC=2, en la solicitud de reposición de pedido, cuando solicitan la reposición de una referencia, nos envían canal de ventas=1 y no 2, por lo tanto, no es posible realizar la reposición.
+
+
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/es/replicated-pending-payment-emails.md b/docs/known-issues/es/replicated-pending-payment-emails.md
index d572df0c3..7c0f497d2 100644
--- a/docs/known-issues/es/replicated-pending-payment-emails.md
+++ b/docs/known-issues/es/replicated-pending-payment-emails.md
@@ -3,8 +3,8 @@ title: 'Correos electrónicos de pagos pendientes replicados'
 id: 6ibJCSrep1aWEKi1DRTLDv
 status: PUBLISHED
 createdAt: 2022-05-18T18:30:57.906Z
-updatedAt: 2022-11-25T22:02:18.499Z
-publishedAt: 2022-11-25T22:02:18.499Z
+updatedAt: 2024-02-16T20:29:35.766Z
+publishedAt: 2024-02-16T20:29:35.766Z
 firstPublishedAt: 2022-05-18T18:30:58.383Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: correos-electronicos-de-pagos-pendientes-replicados
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 348932
 ---
 
diff --git a/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md b/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md
new file mode 100644
index 000000000..ec15c43af
--- /dev/null
+++ b/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md
@@ -0,0 +1,42 @@
+---
+title: 'El enrutamiento de solicitudes es incoherente al ejecutar pruebas A/B'
+id: 5ukS8DTwmWsM0fNWQLYFQ1
+status: PUBLISHED
+createdAt: 2023-11-08T21:42:53.184Z
+updatedAt: 2023-11-08T21:45:26.642Z
+publishedAt: 2023-11-08T21:45:26.642Z
+firstPublishedAt: 2023-11-08T21:42:53.723Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-enrutamiento-de-solicitudes-es-incoherente-al-ejecutar-pruebas-ab
+locale: es
+kiStatus: Backlog
+internalReference: 931246
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+Las peticiones HTTP de navegación de tienda no respetan la cookie de selección de espacio de trabajo durante la sesión. De hecho, durante una única sesión, un usuario puede recibir respuestas de todos los espacios de trabajo que se estén probando.
+
+## Simulación
+
+1. Crea un test A/B en tu tienda utilizando la CLI de VTEX IO.
+2. Abre la pestaña "Aplicación" en Chrome DevTools (o equivalente en tu navegador)
+    1. Navega por la tienda y borra tu cookie `VtexWorkspace` después de cada clic
+    2. Deberías ver que los valores cambian eventualmente, aunque la cookie de sesión no haya cambiado
+3. Abre la pestaña "Red" en Chrome DevTools (o equivalente en tu navegador)
+    1. Navega por la tienda y observa las peticiones HTTP que se realizan
+    2. Deberías ver que la cadena de consulta `workspace` se establece en diferentes valores a lo largo de la sesión
+
+
+## Workaround
+
+No hay ninguna solución disponible. No se recomienda realizar pruebas A/B y sus resultados no deben considerarse correctos hasta que se solucione este problema conocido.
+
+
diff --git a/docs/known-issues/es/reserved-stock-in-invoiced-orders.md b/docs/known-issues/es/reserved-stock-in-invoiced-orders.md
index bab9e1db6..0416c0e7e 100644
--- a/docs/known-issues/es/reserved-stock-in-invoiced-orders.md
+++ b/docs/known-issues/es/reserved-stock-in-invoiced-orders.md
@@ -1,10 +1,10 @@
 ---
 title: 'Stock reservado en pedidos facturados'
 id: TfDOKEybi6eSAEoCEEAqg
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-13T18:43:58.606Z
-updatedAt: 2022-12-22T14:51:09.663Z
-publishedAt: 2022-12-22T14:51:09.663Z
+updatedAt: 2023-10-17T15:29:19.908Z
+publishedAt: 
 firstPublishedAt: 2017-06-14T00:07:07.051Z
 contentType: knownIssue
 productTeam: Post-purchase
diff --git a/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md b/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
new file mode 100644
index 000000000..dcf8e815f
--- /dev/null
+++ b/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
@@ -0,0 +1,45 @@
+---
+title: 'Itens devueltos con el mismo SkuId en diferentes arrays UniqueId no es visible correctamente'
+id: 65uUpH4uSicaDzruCIBaTq
+status: PUBLISHED
+createdAt: 2024-06-14T20:48:37.328Z
+updatedAt: 2024-06-14T20:48:38.207Z
+publishedAt: 2024-06-14T20:48:38.207Z
+firstPublishedAt: 2024-06-14T20:48:38.207Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: itens-devueltos-con-el-mismo-skuid-en-diferentes-arrays-uniqueid-no-es-visible-correctamente
+locale: es
+kiStatus: Backlog
+internalReference: 1050294
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Nuestros sistemas integrados (OMS/SNO/UI) no fueron diseñados para utilizar la misma información para la correlación para mostrar la información correcta cuando un iten con el mismo SKU fue creado en diferente matriz uniqueid. Esto sucede porque algunos sistemas utilizan skuid y otros itemindex.
+
+
+
+## Simulación
+
+
+Crear un pedido con más de una cantidad de artículos, creando un pedido con más de un array de itens con el mismo skuid. Facturar el pedido y en las páginas de devolución se podrá ver que el artículo no tiene información sobre las diferencias entre cada uno.
+
+
+
+## Workaround
+
+
+No hay solución para esto.
+
+
+
+
+
diff --git a/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md b/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
index c9fa20561..a79b27780 100644
--- a/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
+++ b/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
@@ -3,8 +3,8 @@ title: 'No se ha añadido el valor de la recompensa o se ha añadido un valor di
 id: 3i9TwGKpYOkwnHUXDON9V7
 status: PUBLISHED
 createdAt: 2023-06-14T16:06:37.154Z
-updatedAt: 2023-06-14T16:06:37.696Z
-publishedAt: 2023-06-14T16:06:37.696Z
+updatedAt: 2023-06-27T12:44:59.727Z
+publishedAt: 2023-06-27T12:44:59.727Z
 firstPublishedAt: 2023-06-14T16:06:37.696Z
 contentType: knownIssue
 productTeam: Checkout
@@ -23,7 +23,7 @@ internalReference: 844079
 </div>
 
 
-El valor de la recompensa puede no ser o tener un valor diferente añadido a la tarjeta regalo del comprador.
+El valor de la recompensa puede no ser o tener un valor diferente añadido a la tarjeta regalo del comprador cuando la promoción está configurada para aplicar el importe de la recompensa cuando el estado del pedido cambia a pago aprobado.
 
 
 ##
@@ -32,8 +32,8 @@ El valor de la recompensa puede no ser o tener un valor diferente añadido a la
 
 
 
-- Cree una promoción de valor de recompensa;
-- Finalice una compra;
+- Cree una promoción de valor de recompensa para que se aplique cuando el estado del pedido cambie a pago aprobado;
+- Finalice la compra;
 - Compruebe las interacciones en Detalles del pedido en admin; no aparecerá el mensaje "_XX añadido al programa de fidelidad del usuario_"
 
 
@@ -41,7 +41,9 @@ El valor de la recompensa puede no ser o tener un valor diferente añadido a la
 ## Workaround
 
 
-Seleccione a través de admin la opción "Tarjetas regalo" en el menú, seleccione la tarjeta regalo del comprador y haga clic en "Extracto" en la columna Acciones para añadir el valor adecuado.
+
+- Seleccione a través de admin la opción "Tarjetas regalo" en el menú, seleccione la tarjeta regalo del comprador y haga clic en "Extracto" en la columna Acciones para añadir el valor adecuado;
+- Configure la promoción del valor de la recompensa para que se aplique cuando el estado del pedido cambie a facturado.
 
 
 
diff --git a/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md b/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md
new file mode 100644
index 000000000..ed54697d0
--- /dev/null
+++ b/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md
@@ -0,0 +1,62 @@
+---
+title: 'El reescritor no recibe actualizaciones de URL'
+id: 4c3S9s57SzQCv8zv4L77Fu
+status: PUBLISHED
+createdAt: 2024-07-16T19:24:56.813Z
+updatedAt: 2024-07-16T19:24:57.773Z
+publishedAt: 2024-07-16T19:24:57.773Z
+firstPublishedAt: 2024-07-16T19:24:57.773Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-reescritor-no-recibe-actualizaciones-de-url
+locale: es
+kiStatus: Backlog
+internalReference: 1066527
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se cambia/elimina una URL en el catálogo, la reescritura no recibe este cambio. Dado que la reescritura no recibe ninguna notificación al respecto, la URL sigue apuntando al tipo incorrecto, lo que también puede provocar problemas en el SI.
+
+Esto también puede ocurrir al crear nuevas rutas de categoría/subcategoría en el catálogo. El reescritor a veces necesitará que ejecute la consulta bootstrap para recibir esas rutas.
+
+
+##
+
+## Simulación
+
+
+Prueba a eliminar una marca existente del catálogo
+Ejecute la mutación para ver cómo se recibe esta ruta en la regrabadora
+
+    {internal{ get(path:"/marca"){ from declarer query disableSitemapEntry }}}
+
+Si busca esa marca en el escaparate, seguirá apuntando a un `map=b`.
+
+También puedes comprobar cómo se está devolviendo esta ruta en el pageType; si es un fullText, el pageType se actualizó, y el rewriter no.
+
+
+
+## Workaround
+
+
+Intente borrar la ruta manualmente de la reescritura:
+
+      mutation{ internal{ delete(ruta:"/ruta"){ from id resolveAs } }}
+
+
+Intenta ejecutar la consulta bootstrap para actualizar el rewriter:
+
+    {bootstrap { marcas categorías}}
+
+
+
+
+
diff --git a/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md b/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
new file mode 100644
index 000000000..aa1f2e4b3
--- /dev/null
+++ b/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
@@ -0,0 +1,57 @@
+---
+title: 'el modo redondeo techo/suelo no funciona correctamente entre los elementos con multiplicador unitario distinto de 1'
+id: 5KzOM5kEp8QpkBTX7hdil1
+status: PUBLISHED
+createdAt: 2024-01-18T17:53:08.668Z
+updatedAt: 2024-01-18T17:53:09.229Z
+publishedAt: 2024-01-18T17:53:09.229Z
+firstPublishedAt: 2024-01-18T17:53:09.229Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: el-modo-redondeo-techosuelo-no-funciona-correctamente-entre-los-elementos-con-multiplicador-unitario-distinto-de-1
+locale: es
+kiStatus: Backlog
+internalReference: 968349
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Es posible establecer, a través de una tarea para el equipo de producto, cambiar cómo se redondea el valor del descuento en el carrito.
+En un escenario en el que la cuenta esté utilizando un modo de redondeo de techo o suelo, este redondeo no funcionará correctamente con artículos con unitmultiplier distinto de 1.
+
+Esto se debe a que el unitMultiplier de este artículo es 100.0. Cuando RnB redondea el valor del descuento para la caja, redondea el precio unitario. Así que toma el valor de una unidad pequeña y lo redondea. Luego toma todo el descuento, lo divide por la cantidad multiplicada por el unitMultiplier y lo redondea a dos decimales.
+Como RnB sólo tiene en cuenta dos decimales, redondea a 0,01 ó 0,02.
+
+
+##
+
+## Simulación
+
+
+
+Ejemplo:
+Descuento total: -3.96
+Descuento unitario = -3,96 / (2*100) = -0,0198
+
+Entonces, ¿qué artículo se llevará el 0,0198% del descuento, en lugar del 3,96%?
+
+
+
+## Workaround
+
+
+
+Una solución válida sería volver a no roundingMode, por lo que el problema dejará de ocurrir.
+
+
+
+
+
diff --git a/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md b/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
new file mode 100644
index 000000000..4f8bd30f0
--- /dev/null
+++ b/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
@@ -0,0 +1,46 @@
+---
+title: 'La priorización de rutas no ofrece la mejor opción en cuanto a cantidad de paquetes y artículos'
+id: 4verafDuoFnC5vGDI4UV1m
+status: PUBLISHED
+createdAt: 2023-10-30T18:28:52.771Z
+updatedAt: 2023-10-30T18:28:53.648Z
+publishedAt: 2023-10-30T18:28:53.648Z
+firstPublishedAt: 2023-10-30T18:28:53.648Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: la-priorizacion-de-rutas-no-ofrece-la-mejor-opcion-en-cuanto-a-cantidad-de-paquetes-y-articulos
+locale: es
+kiStatus: Backlog
+internalReference: 927747
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En Logística, el primer criterio de desempate cuando el sistema está eligiendo la ruta (almacén + muelle + política de envío), está relacionado con el número de paquetes necesarios para esta ruta específica, menos paquetes significa que la ruta debería ser mejor.
+Sin embargo, el sistema no puede tener en cuenta la relación entre el número de paquetes y el número de artículos de cada paquete.
+Esto significa que, por ejemplo, un pedido con 2 paquetes y 2 artículos, puede ser priorizado cuando tiene una ruta disponible que entrega sólo 1 paquete con todos los artículos.
+
+
+
+## Simulación
+
+
+No hay una manera fácil de simular este escenario, ya que es muy específico y el sistema puede comportarse de manera diferente en cada caso, pero tenemos un ejemplo muy claro donde el sistema elige el ANS que divide el paquete en 2 en lugar de ofrecer el ANS con sólo 1 paquete.
+
+
+
+## Workaround
+
+
+El comerciante puede separar el almacén + muelle + política de envío, con diferente nombre de método de envío, para no depender de la priorización de la ruta.
+
+
+
+
diff --git a/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
new file mode 100644
index 000000000..a83989da9
--- /dev/null
+++ b/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -0,0 +1,54 @@
+---
+title: 'El canal de ventas configurado en Configuración B2B no se asigna después de aprobar Organizaciones'
+id: 7kxMtk2YHJdk5uPdj5wBs5
+status: PUBLISHED
+createdAt: 2023-07-21T20:03:44.671Z
+updatedAt: 2023-07-21T20:03:45.295Z
+publishedAt: 2023-07-21T20:03:45.295Z
+firstPublishedAt: 2023-07-21T20:03:45.295Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: el-canal-de-ventas-configurado-en-configuracion-b2b-no-se-asigna-despues-de-aprobar-organizaciones
+locale: es
+kiStatus: Backlog
+internalReference: 866933
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El canal de ventas configurado en los Ajustes de Organizaciones B2B no se guarda en los Detalles de la Organización.
+
+
+##
+
+## Simulación
+
+
+
+- Configure un canal de ventas predeterminado en Configuración de Organizaciones B2B;
+- Crear una solicitud de organización;
+- Apruebe la solicitud de organización;
+- Compruebe los detalles de la Organización; no tendrá ningún canal de ventas asignado.
+
+
+
+## Workaround
+
+
+
+- Asigne el canal de ventas a la organización a través del administrador;
+- Cree un disparador para el esquema de la entidad de la organización:
+
+    "v-triggers": [{ "name": "define-canal-deventas-por-defecto", "active": true, "condition": "salesChannel is null", "action": {"type": "guardar", "dataEntity": "organizaciones", "json": { "id": "{!id}", "salesChannel": "{añade aquí el salesChannelId definido en Configuración de organizaciones B2B}" } } }]
+
+
+
+
+
diff --git a/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md b/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md
new file mode 100644
index 000000000..f849da5a6
--- /dev/null
+++ b/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md
@@ -0,0 +1,53 @@
+---
+title: 'Fallo de validación de esquema para tipos personalizados en Headless CMS'
+id: 2dcDsFQkqbNqJZXEzztQ11
+status: PUBLISHED
+createdAt: 2023-09-19T21:43:59.145Z
+updatedAt: 2023-09-19T21:43:59.945Z
+publishedAt: 2023-09-19T21:43:59.945Z
+firstPublishedAt: 2023-09-19T21:43:59.945Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: fallo-de-validacion-de-esquema-para-tipos-personalizados-en-headless-cms
+locale: es
+kiStatus: Backlog
+internalReference: 903687
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Tenemos validaciones de esquema que fallan en campos requeridos sin valor por defecto en Headless CMS para tipos de página personalizados, la librería que usamos está considerando que falla pero los campos requeridos se rellenan correctamente
+
+
+##
+
+## Simulación
+
+
+
+Crear una estructura de esquema para una página específica con un campo obligatorio y no poner un valor por defecto para este campo obligatorio
+
+
+    ... "obligatorio": ["field1"],"properties": {"field1": {"title": "campo", "type": "string", "description": "Some description" }}...
+
+
+
+##
+
+## Workaround
+
+
+Ponga un valor por defecto en los campos obligatorios
+
+
+
+
+
diff --git a/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md b/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md
new file mode 100644
index 000000000..491b2b175
--- /dev/null
+++ b/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md
@@ -0,0 +1,50 @@
+---
+title: 'Problema de desplazamiento al hacer zoom tras el renderizado de la página de búsqueda'
+id: 2FcX9UNvBOanE3EhH9q0DT
+status: PUBLISHED
+createdAt: 2024-02-08T16:51:28.278Z
+updatedAt: 2024-03-06T14:17:07.639Z
+publishedAt: 2024-03-06T14:17:07.639Z
+firstPublishedAt: 2024-02-08T16:51:29.011Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: problema-de-desplazamiento-al-hacer-zoom-tras-el-renderizado-de-la-pagina-de-busqueda
+locale: es
+kiStatus: Fixed
+internalReference: 979464
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al cambiar la ventana gráfica o ampliar la pantalla en las páginas de búsqueda después de la primera carga, no se permite desplazar la página correctamente.
+
+
+##
+
+## Simulación
+
+
+
+
+- Cargar la página de búsqueda
+- Cambia el zoom de tu navegador
+- Intenta desplazar la página
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md b/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
new file mode 100644
index 000000000..e07b347a4
--- /dev/null
+++ b/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
@@ -0,0 +1,51 @@
+---
+title: 'Problemas de desplazamiento al deslizar en móvil en vista rápida cuando hay un diseño deslizante en segundo plano.'
+id: 5B7g5Wt1iyh0BLwIUprO2C
+status: PUBLISHED
+createdAt: 2024-02-20T17:58:53.942Z
+updatedAt: 2024-02-20T17:58:54.806Z
+publishedAt: 2024-02-20T17:58:54.806Z
+firstPublishedAt: 2024-02-20T17:58:54.806Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: problemas-de-desplazamiento-al-deslizar-en-movil-en-vista-rapida-cuando-hay-un-diseno-deslizante-en-segundo-plano
+locale: es
+kiStatus: Backlog
+internalReference: 985097
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al deslizar la imagen de un producto en la vista rápida en el móvil cuando hay un diseño deslizante en el fondo, ambos deslizadores se van a mover a la siguiente en lugar de sólo la imagen en la vista rápida
+
+
+##
+
+## Simulación
+
+
+
+
+- Abrir una vista rápida en el móvil con un diseño deslizante en el fondo
+- Intente deslizar la imagen del producto
+
+El comportamiento esperado es que no sólo cambie la imagen del producto de la vista rápida, sino también los productos de la presentación deslizante/estante.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/search-analytics-duplicated-events.md b/docs/known-issues/es/search-analytics-duplicated-events.md
new file mode 100644
index 000000000..915344753
--- /dev/null
+++ b/docs/known-issues/es/search-analytics-duplicated-events.md
@@ -0,0 +1,63 @@
+---
+title: 'Buscar eventos duplicados en Analytics'
+id: 48h3ObR7qqRHvU36weCvjC
+status: PUBLISHED
+createdAt: 2023-03-15T19:40:23.229Z
+updatedAt: 2023-09-20T18:49:19.673Z
+publishedAt: 2023-09-20T18:49:19.673Z
+firstPublishedAt: 2023-03-15T19:40:23.835Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: buscar-eventos-duplicados-en-analytics
+locale: es
+kiStatus: Fixed
+internalReference: 771986
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunos eventos de los informes de búsqueda inteligente están duplicados, lo que puede afectar a la vista de análisis del módulo de administración de búsqueda.
+
+
+#### FAQ
+
+**1. ¿Afecta a todos los eventos VTEX (por ejemplo, captura de solicitudes, paneles de la página de inicio del administrador, etc.)?
+
+No, los análisis de Búsqueda Inteligente se calculan de forma diferente e independiente de esas métricas y eventos por ahora. Este problema sólo afecta a la página Búsqueda > Análisis.
+
+**2. ¿Se sobrecalculan todas las métricas?**.
+
+Sí, todas las métricas sin procesar que se muestran en la página Búsqueda > Análisis se calculan en exceso en este momento.
+
+Son los siguientes: recuento de búsquedas, clics en un término, clics únicos en un término, recuento de transacciones tras la búsqueda de un término e ingresos generados por esas transacciones, porcentaje de clics y conversión.
+
+**3. ¿También se han visto afectados los datos de exportación a CSV?
+
+Sí, los datos exportados a CSV también se ven afectados por los datos sobrecomputados.
+
+**4. ¿Afecta esto al algoritmo Search Relevance y a los resultados de las búsquedas?
+
+No, aunque el algoritmo de relevancia de búsqueda también utiliza los eventos de análisis para calcular la puntuación de popularidad del producto, no utiliza las métricas agregadas.
+
+
+##
+
+## Simulación
+
+
+El escenario se puede ver al comprobar la página de administración de búsqueda para los informes/análisis.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md b/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
new file mode 100644
index 000000000..703b2268c
--- /dev/null
+++ b/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
@@ -0,0 +1,49 @@
+---
+title: 'Los análisis de búsqueda informan de divergencias entre versiones con o sin métricas de embudo'
+id: 33lXZb4Nr2NOPgW2Cth9ry
+status: PUBLISHED
+createdAt: 2024-02-09T19:01:45.952Z
+updatedAt: 2024-02-09T19:01:46.857Z
+publishedAt: 2024-02-09T19:01:46.857Z
+firstPublishedAt: 2024-02-09T19:01:46.857Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-analisis-de-busqueda-informan-de-divergencias-entre-versiones-con-o-sin-metricas-de-embudo
+locale: es
+kiStatus: Backlog
+internalReference: 980297
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El informe de análisis de búsqueda exportado como CSV puede divergir entre su versión con métricas de embudo y su versión sin ellas.
+
+El informe normal (sin métricas de embudo) se exporta utilizando el mismo método que los datos presentados en la propia página, pero la exportación con métricas de embudo utiliza un método diferente para calcular los datos adicionales, lo que a veces puede dar lugar a información diferente.
+
+
+##
+
+## Simulación
+
+
+Exporte las dos versiones del informe para el mismo periodo y compare los términos de búsqueda listados y las primeras columnas entre ellas.
+
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md b/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
index a217f31d0..5f5e4fd4e 100644
--- a/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
+++ b/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
@@ -3,8 +3,8 @@ title: 'La API de búsqueda no devuelve los SKUs showIfNotAvailable=true para la
 id: 7p26JmS8pyPA8H0b1QJHyU
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:27.329Z
-updatedAt: 2022-11-25T22:10:15.920Z
-publishedAt: 2022-11-25T22:10:15.920Z
+updatedAt: 2024-02-16T20:29:43.164Z
+publishedAt: 2024-02-16T20:29:43.164Z
 firstPublishedAt: 2022-06-28T16:55:28.384Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: la-api-de-busqueda-no-devuelve-los-skus-showifnotavailabletrue-para-las-consultas-fqspecificationfilter
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 336896
 ---
 
diff --git a/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md b/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
index 11e193130..71490a603 100644
--- a/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
+++ b/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
@@ -3,8 +3,8 @@ title: 'La API de búsqueda no funciona correctamente después de iniciar sesió
 id: 3YxbokaDhYnthzy1dc5VHs
 status: PUBLISHED
 createdAt: 2022-01-21T18:24:15.316Z
-updatedAt: 2022-11-25T22:11:01.363Z
-publishedAt: 2022-11-25T22:11:01.363Z
+updatedAt: 2024-02-16T20:29:54.425Z
+publishedAt: 2024-02-16T20:29:54.425Z
 firstPublishedAt: 2022-03-16T16:50:03.972Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: la-api-de-busqueda-no-funciona-correctamente-despues-de-iniciar-sesion-con-el-operador-del-centro-de-llamadas
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 304586
 ---
 
diff --git a/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md b/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
new file mode 100644
index 000000000..868536c87
--- /dev/null
+++ b/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
@@ -0,0 +1,46 @@
+---
+title: 'El autocompletado de búsqueda proporciona una URL obsoleta después de navegar por las sugerencias.'
+id: 168oT3vpuAcRdZbE7sahtF
+status: PUBLISHED
+createdAt: 2024-01-19T01:28:08.775Z
+updatedAt: 2024-01-19T01:28:09.627Z
+publishedAt: 2024-01-19T01:28:09.627Z
+firstPublishedAt: 2024-01-19T01:28:09.627Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: el-autocompletado-de-busqueda-proporciona-una-url-obsoleta-despues-de-navegar-por-las-sugerencias
+locale: es
+kiStatus: Backlog
+internalReference: 968604
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En el componente "search-bar" con "autocomplete-result-list.v2", al pasar el ratón por las sugerencias de búsqueda también cambiarán los productos sugeridos, así como el texto de "ver todos {n} los productos" para mencionar la búsqueda seleccionada, pero el hipervínculo de "ver todos" sigue el término de búsqueda original en lugar del seleccionado.
+
+
+##
+
+## Simulación
+
+
+
+- buscar un término parcial
+- pase el ratón por encima de los términos sugeridos
+- haga clic en "ver todos los productos
+
+
+##
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
new file mode 100644
index 000000000..2456a174f
--- /dev/null
+++ b/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -0,0 +1,54 @@
+---
+title: 'Los banners de búsqueda no siguen el operador "AND" para las condiciones de activación'
+id: 4nQLt5q3Mz2DxvBIyZknXj
+status: PUBLISHED
+createdAt: 2024-06-20T21:17:46.485Z
+updatedAt: 2024-06-20T21:17:47.308Z
+publishedAt: 2024-06-20T21:17:47.308Z
+firstPublishedAt: 2024-06-20T21:17:47.308Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-banners-de-busqueda-no-siguen-el-operador-and-para-las-condiciones-de-activacion
+locale: es
+kiStatus: Backlog
+internalReference: 1053614
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las condiciones para los banners de búsqueda (gestionados a través de "/admin/search/v4/banners/") no soportan el operador "AND" tal y como se presenta en sus reglas de activación. La interfaz de usuario es incorrecta, y el operador se comporta como "OR" de forma fija.
+
+Cualquiera de las condiciones rellenadas allí será suficiente para presentar el banner en la página (PLP).
+
+Tenga en cuenta que al establecer un departamento allí (nivel de categoría 1) se aplicará el banner en cualquiera de sus subcategorías, ya que esto es parte de la ruta de categoría completa.
+
+
+
+## Simulación
+
+
+Cree un banner con las siguientes reglas de activación:
+
+- donde "departamento" es "electrodomésticos"
+- y**"categoría" es "frigoríficos".
+
+El banner no se restringirá a la ruta completa de la categoría "/appliances/refrigerators?map=c,c". Se aplicará en el departamento y sus subcategorías, y en cualquier categoría denominada "frigoríficos", aunque no forme parte de este departamento en concreto.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md b/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md
index adf7e50f6..48fe67085 100644
--- a/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md
+++ b/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md
@@ -1,36 +1,52 @@
 ---
-title: 'Search by EAN not working on Received Skus'
+title: 'La búsqueda por EAN no funciona en Skus recibidos'
 id: PKdNXxjVPFbJbVBSTFvep
-status: DRAFT
+status: PUBLISHED
 createdAt: 2022-01-26T19:24:01.975Z
-updatedAt: 2022-01-31T18:31:27.337Z
-publishedAt: 
+updatedAt: 2024-02-16T20:24:48.686Z
+publishedAt: 2024-02-16T20:24:48.686Z
 firstPublishedAt: 2022-01-26T19:25:13.218Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
-tag: 
-slug: search-by-ean-not-working-on-received-skus
+tag: Marketplace
+slug: la-busqueda-por-ean-no-funciona-en-skus-recibidos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 510907
 ---
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
+
+La función de búsqueda de Skus Recibidos permite al marketplace buscar un producto o sku por los siguientes criterios:
+- Sku Nombre;
+- ID;
+- EAN.
+
+Actualmente, la búsqueda EAN no se comporta como se esperaba, ya que no ofrece ningún resultado.
+
+
+##
+
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+
+Intente encontrar un sku buscándolo utilizando su EAN.
+El resultado debería ser el código en lugar de un espacio en blanco.
+
+
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+
+Utilice los otros criterios de búsqueda, como Sku Name o ID.
+
+
+
+
 
diff --git a/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md b/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
new file mode 100644
index 000000000..894a77223
--- /dev/null
+++ b/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
@@ -0,0 +1,58 @@
+---
+title: 'La búsqueda no tiene productos si el nombre del vendedor 1 en la Gestión de vendedores difiere del nombre comercial en la Gestión de cuentas al utilizar B2B Suite.'
+id: 7a3bwqRmeSClHMoFmyIY2a
+status: PUBLISHED
+createdAt: 2023-12-01T20:06:13.492Z
+updatedAt: 2023-12-01T20:15:07.659Z
+publishedAt: 2023-12-01T20:15:07.659Z
+firstPublishedAt: 2023-12-01T20:06:14.083Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: la-busqueda-no-tiene-productos-si-el-nombre-del-vendedor-1-en-la-gestion-de-vendedores-difiere-del-nombre-comercial-en-la-gestion-de-cuentas-al-utilizar-b2b-suite
+locale: es
+kiStatus: Backlog
+internalReference: 946391
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las organizaciones B2B utilizan los nombres de los vendedores desde la Gestión de Vendedores. Si una organización tiene asignado el vendedor 1, el nombre guardado será de la Gestión de vendedores, pero es posible que no se muestren productos en la búsqueda si difiere del nombre comercial en la Gestión de cuentas.
+
+
+##
+
+## Simulación
+
+
+
+- Tenga una cuenta con el vendedor 1 cuyo nombre en Gestión de Vendedores sea diferente del nombre comercial en Gestión de Cuentas;
+- Cree una Organización B2B y asigne al vendedor 1;
+- Acceda a la cuenta; no se muestra ningún producto.
+
+
+
+## Workaround
+
+
+
+- Acceda a GraphQL IDE y seleccione vtex.b2b-organizations-graphql;
+- Utilice la siguiente consulta para obtener todos los detalles de la organización:
+
+    { getOrganizationById(id: "introduzca aquí el id de la organización"){ id name tradeName status collections{ id name } paymentTerms{ id name } priceTables customFields{ name type value dropdownValues{ value label } useOnRegistration } salesChannel sellers { id name } }}
+
+- Envíe una mutación para actualizar el nombre del vendedor para el vendedor 1 utilizando la información recuperada anteriormente:
+
+    mutación { updateOrganization( id: "" name: "" tradeName: "" status: "active" collections: [{ id: "" name: "" }] paymentTerms: [{ id: "" name: "" }] priceTables: [""] customFields: [] salesChannel: "" vendedores: [{ id: "1", name: "nombre comercial de Gestión de Cuentas" }] ){ id status message }}
+
+
+
+
+
+
diff --git a/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md b/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md
index e03ad0414..4cf7d8e32 100644
--- a/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md
+++ b/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md
@@ -3,8 +3,8 @@ title: 'El filtro del Navegador de Búsqueda + Rango de Precios produce resultad
 id: 6s4vJr6DVPLU9JlxIPWqhx
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.208Z
-updatedAt: 2022-11-25T22:10:01.089Z
-publishedAt: 2022-11-25T22:10:01.089Z
+updatedAt: 2024-02-16T20:24:11.551Z
+publishedAt: 2024-02-16T20:24:11.551Z
 firstPublishedAt: 2022-06-28T16:55:53.927Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: el-filtro-del-navegador-de-busqueda-rango-de-precios-produce-resultados-incorrectos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 504992
 ---
 
diff --git a/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md b/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md
new file mode 100644
index 000000000..05b4222a4
--- /dev/null
+++ b/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md
@@ -0,0 +1,53 @@
+---
+title: 'Search Resolver aplicando traducciones de Mensajes sobre contenido ya traducido'
+id: 7OIKmmhO3Pa2z0pIU33kY
+status: PUBLISHED
+createdAt: 2023-07-20T15:28:57.078Z
+updatedAt: 2024-06-13T20:51:17.597Z
+publishedAt: 2024-06-13T20:51:17.597Z
+firstPublishedAt: 2023-07-20T15:28:57.934Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: search-resolver-aplicando-traducciones-de-mensajes-sobre-contenido-ya-traducido
+locale: es
+kiStatus: Backlog
+internalReference: 865918
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El Search Resolver (capa GraphQL para la Búsqueda Inteligente) solicita traducciones al servicio de Mensajes incluso para tiendas de un solo idioma o contenido ya traducido en una tienda multi-idioma.
+
+En la práctica, estas traducciones se realizan sobre los mismos idiomas "de" y "a", pero si la tienda tiene activada la función de traducción automática, la cadena puede cambiar a algo inesperado.
+
+Esto afecta especialmente a las cadenas con varias palabras que pueden considerarse de idiomas diferentes, como palabras en inglés en el nombre de un producto que está mayoritariamente en francés, y potencialmente fechas (entre las notaciones "dd/mm/aaaa" y "mm/dd/aaaa").
+
+
+##
+
+## Simulación
+
+
+
+- Traduzca cualquier contenido del catálogo de la tienda a un idioma distinto del predeterminado;
+- Asegúrese de que todavía hay al menos una palabra en un idioma diferente al traducido;
+- Compruebe el escaparate; no coincidirá con la traducción.
+
+
+
+## Workaround
+
+
+
+- Desactiva la traducción automática;
+- Cree traducciones para estos contenidos utilizando el mismo idioma que "de" y "a", por ejemplo, traduciéndolo de "fr-FR" a "fr-FR".
+
+
+
diff --git a/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md b/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
new file mode 100644
index 000000000..1a3edf7af
--- /dev/null
+++ b/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
@@ -0,0 +1,66 @@
+---
+title: 'La búsqueda no devuelve el documento cuando el valor contiene un símbolo + (más).'
+id: 7oWiN8Esh9iKy8144Tpglx
+status: PUBLISHED
+createdAt: 2024-07-08T18:52:21.794Z
+updatedAt: 2024-07-08T21:46:18.259Z
+publishedAt: 2024-07-08T21:46:18.259Z
+firstPublishedAt: 2024-07-08T18:52:22.908Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: la-busqueda-no-devuelve-el-documento-cuando-el-valor-contiene-un-simbolo-mas
+locale: es
+kiStatus: No Fix
+internalReference: 828170
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se busca un documento utilizando un valor de campo que incluye el símbolo "+", la búsqueda no devuelve el documento. Esto ocurre porque el símbolo "+" se interpreta incorrectamente, lo que provoca que el valor de búsqueda no coincida con el valor existente.
+Este problema ocurre tanto en la API como en el CRM_.
+
+
+##
+
+## Simulación
+
+
+
+1. Utiliza la API de búsqueda para consultar un campo que incluya un símbolo "+".
+2. La búsqueda devolverá un array vacío. Ejemplo:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=+5512345678901&_fields=id,userId,email,homePhone,firstName
+
+
+En la interfaz de usuario de CRM:
+Si se busca un email que contiene el símbolo "+" se devuelve un error.
+
+    Se ha producido un error inesperado. Inténtelo de nuevo. Si el problema persiste, póngase en contacto con el servicio de asistencia.
+
+
+
+
+## Workaround
+
+
+Hay dos formas de solucionar este problema:
+Codifique el símbolo "+" en "%2B", de modo que la consulta de búsqueda se convierta en:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=%2B5512345678901&_fields=id,userId,email,homePhone,firstName
+
+
+Utilice el símbolo "*" como comodín, que permitirá que la búsqueda coincida con cualquier carácter anterior al valor especificado:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=*12345678901&_fields=id,userId,email,homePhone,firstName
+
+Este problema surge al buscar documentos utilizando valores de campo que incluyen el símbolo "+". La API de búsqueda no interpreta correctamente el símbolo "+", lo que provoca que la búsqueda falle al no coincidir con los valores existentes. Este problema no se limita al campo "homePhone", sino que puede ocurrir con otros campos, como el correo electrónico, que pueden incluir caracteres especiales.
+Para solucionar este problema, puede codificar el símbolo "+" como "%2B" en la consulta de búsqueda o utilizar el símbolo "*" como comodín para asegurarse de que la búsqueda recupera los documentos correctos.
+
+
diff --git a/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md b/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md
index 5ff27c66c..0887c365f 100644
--- a/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md
+++ b/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md
@@ -3,8 +3,8 @@ title: 'Segmento Cookie actualizado sólo después de actualizar la página'
 id: 3QBmp4D2tvIAxEzEy2LpNf
 status: PUBLISHED
 createdAt: 2022-11-01T16:33:05.698Z
-updatedAt: 2023-03-08T20:36:59.962Z
-publishedAt: 2023-03-08T20:36:59.962Z
+updatedAt: 2024-01-10T17:18:13.115Z
+publishedAt: 2024-01-10T17:18:13.115Z
 firstPublishedAt: 2022-11-01T16:33:06.403Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -23,7 +23,7 @@ internalReference: 647116
 </div>
 
 
-Algunas funciones y componentes de VTEX pueden utilizar datos solicitados a la cookie de segmento para presentar información (como precio, datos de promoción, disponibilidad de SKU, etc.) en el escaparate. Esta cookie se almacena en el navegador del usuario cuando se crea la sesión. A veces, sobre todo en escenarios dinámicos donde se necesita hacer cambios en el frente donde se desencadena una actualización del Segmento Cookie, la cookie en sí pierde algunos datos que es de un comportamiento en render-runtime que no desencadena el cambio de segmento en el contexto.
+Algunas funciones y componentes de VTEX pueden utilizar datos solicitados a la cookie de segmento para presentar información (como precio, datos de promoción, disponibilidad de SKU, etc.) en el escaparate. Esta cookie se almacena en el navegador del usuario cuando se crea la sesión. A veces, sobre todo en escenarios dinámicos donde se necesita hacer cambios en el frente donde se desencadena una actualización del Segmento Cookie, la cookie en sí pierde algunos datos que es de un comportamiento en render-runtime que no desencadena el cambio de segmento al contexto.
 
 Cómo recuperar la información de la sesión:
 https://developers.vtex.com/vtex-rest-api/reference/getsession
diff --git a/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md b/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md
new file mode 100644
index 000000000..4e8e9958a
--- /dev/null
+++ b/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md
@@ -0,0 +1,56 @@
+---
+title: 'Las actualizaciones de las comisiones de los vendedores no indexan las skus vinculadas'
+id: GNX6sFV0thQkMLWEwxya9
+status: PUBLISHED
+createdAt: 2023-08-31T14:44:39.162Z
+updatedAt: 2023-08-31T14:44:39.748Z
+publishedAt: 2023-08-31T14:44:39.748Z
+firstPublishedAt: 2023-08-31T14:44:39.748Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-actualizaciones-de-las-comisiones-de-los-vendedores-no-indexan-las-skus-vinculadas
+locale: es
+kiStatus: Backlog
+internalReference: 891162
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el vendedor actualiza la comisión del vendedor en la interfaz de usuario de gestión de vendedores, los skus vinculados relacionados con este vendedor no se indexan automáticamente.
+
+Nuestro sistema de pago utiliza la API stockkeepingunitbyid para obtener la información actualizada de la sku.
+
+En esta API tenemos el objeto SkuSellers que contiene la información de la comisión. Pero si el sku no está indexado este objeto queda desactualizado.
+
+Esto implica que en el checkout se obtiene el valor antiguo de la comisión.
+
+
+##
+
+## Simulación
+
+
+
+1. Cambie la comisión del vendedor en la interfaz de usuario de gestión de vendedores.
+2. Espere el tiempo de caché, alrededor de 10min.
+3. Compruebe que en la simulación de pago la comisión está desactualizada.
+
+
+
+## Workaround
+
+
+Para evitar cerrar pedidos con el valor de comisión desactualizado, el comerciante puede indexar manualmente los skus afectados.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md b/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md
new file mode 100644
index 000000000..663ffeb82
--- /dev/null
+++ b/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md
@@ -0,0 +1,54 @@
+---
+title: 'La creación de grupos de vendedores no añade los vendedores seleccionados'
+id: 5J14RCg9E4LzBcvJQyOAYy
+status: PUBLISHED
+createdAt: 2023-10-27T17:33:45.625Z
+updatedAt: 2024-01-26T16:54:12.089Z
+publishedAt: 2024-01-26T16:54:12.089Z
+firstPublishedAt: 2023-10-27T17:33:46.214Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: la-creacion-de-grupos-de-vendedores-no-anade-los-vendedores-seleccionados
+locale: es
+kiStatus: Fixed
+internalReference: 926969
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El mercado puede crear grupos con algunos vendedores en la interfaz de usuario de gestión de vendedores.
+ ![](https://vtexhelp.zendesk.com/attachments/token/Mi9PZxDSnInogb65PbJ3fEduu/?name=image.png)
+
+Sin embargo, al añadir un nombre de grupo y vendedores en esta interfaz, sólo se guarda el nombre del grupo. Aparece un mensaje de error:
+"Lo sentimos, algo ha ido mal al añadir los vendedores al grupo XXX".
+ ![](https://vtexhelp.zendesk.com/attachments/token/Gd0FRbqKLDnCGFmIjuXIctxwX/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+
+1. Vaya al área de Gestión de vendedores y pulse en Gestionar grupos;
+2. Pulsa en Añadir Grupo y añade la información como nombre y vendedores;
+3. 3. Compruebe que el grupo está creado pero sin ningún vendedor.
+
+
+
+## Workaround
+
+
+Añada los vendedores al grupo manualmente más tarde en su "Detalles del vendedor" UI
+
+
+
+
+
diff --git a/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md b/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
new file mode 100644
index 000000000..fe0e87683
--- /dev/null
+++ b/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
@@ -0,0 +1,50 @@
+---
+title: 'Portal del vendedor Promoción Precio mínimo del artículo condición no funciona como se esperaba'
+id: d0qJRHP3ngtNH5gwSPaNi
+status: PUBLISHED
+createdAt: 2023-10-31T20:42:03.072Z
+updatedAt: 2023-10-31T20:42:03.763Z
+publishedAt: 2023-10-31T20:42:03.763Z
+firstPublishedAt: 2023-10-31T20:42:03.763Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: portal-del-vendedor-promocion-precio-minimo-del-articulo-condicion-no-funciona-como-se-esperaba
+locale: es
+kiStatus: Backlog
+internalReference: 928558
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente, no es posible crear una promoción y establecer una condición de precio mínimo del artículo, a través de la interfaz no es posible guardar.
+
+
+##
+
+## Simulación
+
+
+
+Crear una promoción y establecer un precio mínimo en las Condiciones
+
+
+
+## Workaround
+
+
+
+A través de la API es posible guardar la restricción.
+Advertencia: guardar de nuevo a través de la interfaz, después de guardar a través de la API, sobrescribirá cualquier alteración realizada.
+
+
+
+
+
diff --git a/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md b/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md
index 669683b60..c402c1027 100644
--- a/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md
+++ b/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md
@@ -3,8 +3,8 @@ title: 'El desplegable de selección de especificaciones del portal del vendedor
 id: 7DeU9mKh7gseN7svVPtDzb
 status: PUBLISHED
 createdAt: 2022-12-06T14:27:57.920Z
-updatedAt: 2023-05-09T19:08:09.706Z
-publishedAt: 2023-05-09T19:08:09.706Z
+updatedAt: 2024-02-16T20:24:15.024Z
+publishedAt: 2024-02-16T20:24:15.024Z
 firstPublishedAt: 2022-12-06T14:27:58.644Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-desplegable-de-seleccion-de-especificaciones-del-portal-del-vendedor-no-funciona-correctamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 711303
 ---
 
diff --git a/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md b/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
new file mode 100644
index 000000000..f0f740af3
--- /dev/null
+++ b/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
@@ -0,0 +1,48 @@
+---
+title: 'La interfaz de usuario de registro de vendedores no envía los productos a reindexar al desactivar un vendedor.'
+id: 0iAMGhIOKDyMbEykB4pfx
+status: PUBLISHED
+createdAt: 2023-10-06T19:45:08.963Z
+updatedAt: 2023-10-06T19:45:29.372Z
+publishedAt: 2023-10-06T19:45:29.372Z
+firstPublishedAt: 2023-10-06T19:45:09.832Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: la-interfaz-de-usuario-de-registro-de-vendedores-no-envia-los-productos-a-reindexar-al-desactivar-un-vendedor
+locale: es
+kiStatus: Backlog
+internalReference: 915970
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar la nueva interfaz de usuario de experiencia del vendedor, /admin/sellers, la acción de desactivar un vendedor debería reindexar sus productos relacionados para que puedan eliminarse de los mercados asociados, lo que no ocurre actualmente.
+
+
+##
+
+## Simulación
+
+
+Acceda a la interfaz de usuario antes mencionada y, para una tienda que se está integrando con un mercado, con un punto final de afiliado (https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187) y, a continuación, intente desactivar un vendedor disponible para esta misma política comercial.
+
+Los artículos, en el marketplace, no se actualizarán.
+
+
+
+## Workaround
+
+
+Reindexe la base o utilice la interfaz de vendedor heredada ( https://accountname.vtexcommercestable.com.br/admin/site/seller.aspx), que activa la indexación correctamente.
+
+
+
+
+
diff --git a/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md b/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md
new file mode 100644
index 000000000..8d200210c
--- /dev/null
+++ b/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md
@@ -0,0 +1,66 @@
+---
+title: 'Pedido del vendedor facturado con problema en la captura del pago'
+id: 59M66kN7D6qy8ErLnbdT9r
+status: PUBLISHED
+createdAt: 2024-01-29T16:51:46.993Z
+updatedAt: 2024-01-29T16:51:47.674Z
+publishedAt: 2024-01-29T16:51:47.674Z
+firstPublishedAt: 2024-01-29T16:51:47.674Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: pedido-del-vendedor-facturado-con-problema-en-la-captura-del-pago
+locale: es
+kiStatus: Backlog
+internalReference: 376646
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Ahora mismo, tal y como está construida nuestra arquitectura, tanto el Vendedor como el Marketplace son dos entidades totalmente diferentes. Marketplace se encarga de recibir el dinero del cliente y el vendedor es responsable de toda la logística hasta el momento en que entrega los productos al cliente.
+
+La parte de "recibir dinero" se divide en Autorización y Captura. Ambas son acciones separadas en el Gateway y se ejecutan en dos momentos distintos. El primero es cuando el cliente realiza la compra y el segundo es cuando se inserta una factura en el sistema. Tras el proceso de Autorización, el Marketplace "indica" al Vendedor que puede proceder a preparar y enviar al cliente su mercancía. Como hay un espacio de tiempo entre la Autorización y la Captura y como son acciones separadas, no hay garantía de que la acción de Captura se ejecute correctamente.
+
+Esto nos deja con el problema de que el Vendedor recibió una notificación para enviar la mercancía, insertó una notificación de factura en el sistema, y el Marketplace tuvo un problema al intentar realizar la acción de Captura.
+
+En estos casos de notificación de Autorización y Captura, el Gateway siempre notifica inicialmente al Marketplace que a su vez notifica al Vendedor.
+
+El problema es que el flujo del Vendedor no se detiene por los problemas que pueda tener en la Captura de pago, sino que se refleja en el flujo del Mercado.
+
+
+##
+
+## Simulación
+
+
+No tenemos un paso a paso para replicar, sin embargo, es posible validar una orden de ejemplo.
+
+Podemos ver que la orden de Mercado reportó un problema en la captura y no pudo completar el flujo, mostrando el error: "La operación de liquidación ha vuelto Fallida"
+
+En el flujo, el estado del pedido en el Marketplace será "Verificando factura" y en las interacciones el mensaje: "La operación de liquidación ha vuelto Fallida".
+
+En los eventos de transacción, aparecerá el mensaje: "Error: La respuesta fue Entidad_Rechazada".
+
+Mientras el pedido del Vendedor llegó a Facturado, porque, para el Vendedor en la arquitectura actual, la captura del pago no es su responsabilidad aún siendo el dueño del pago.
+
+
+
+
+## Workaround
+
+
+En este momento no contamos con una solución para completar el flujo del Mercado, ya que esto depende de que la captura se realice correctamente. Sin la confirmación del Gateway, el pedido no podrá avanzar. Desafortunadamente, la salida a este tipo de inconsistencia es cancelar la orden MKT e intentar hacer una nueva manualmente.
+
+Es importante validar siempre que se ha completado la captura del pago antes de entregar los productos
+
+
+
+
+
+
diff --git a/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md b/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md
new file mode 100644
index 000000000..789bd7434
--- /dev/null
+++ b/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md
@@ -0,0 +1,48 @@
+---
+title: 'El campo del nombre del tipo de servicio se devuelve erróneamente a través de la API'
+id: 1FdozyiQb5DLe7TPICyCDR
+status: PUBLISHED
+createdAt: 2024-01-04T16:36:17.926Z
+updatedAt: 2024-01-04T16:36:18.628Z
+publishedAt: 2024-01-04T16:36:18.628Z
+firstPublishedAt: 2024-01-04T16:36:18.628Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-campo-del-nombre-del-tipo-de-servicio-se-devuelve-erroneamente-a-traves-de-la-api
+locale: es
+kiStatus: Backlog
+internalReference: 961278
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente las APIs del Catálogo SKU no están devolviendo correctamente el nombre de un tipo de servicio. En su lugar se está devolviendo el nombre del valor del servicio.
+
+
+##
+
+## Simulación
+
+
+
+1. Hacer una petición GET SKU sobre un sku asociado a un servicio: https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/stockkeepingunit/-skuId-
+2. Observa que el objeto services devuelve un campo serviceTypeId y un Name, sin embargo el campo Name no muestra el nombre del tipo de servicio en sí.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md b/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md
index 707ed568f..36b10c0c0 100644
--- a/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md
+++ b/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md
@@ -3,8 +3,8 @@ title: 'Los precios de los servicios no se actualizan cuando se añaden a los ar
 id: 5hJ7TbHzX4zFbdNWqPnMRQ
 status: PUBLISHED
 createdAt: 2023-05-09T14:27:37.283Z
-updatedAt: 2023-05-09T14:27:37.766Z
-publishedAt: 2023-05-09T14:27:37.766Z
+updatedAt: 2023-06-23T18:37:32.624Z
+publishedAt: 2023-06-23T18:37:32.624Z
 firstPublishedAt: 2023-05-09T14:27:37.766Z
 contentType: knownIssue
 productTeam: Checkout
@@ -34,7 +34,7 @@ Los precios de los servicios no se actualizan si se añadió a un artículo ante
 
 - Crear un servicio;
 - Añadir un artículo con servicio al carrito;
-- Cambiar el precio del servicio;
+- Modificar el precio del servicio;
 - Comprobar el carro previamente montado; el servicio no se actualiza.
 
 
diff --git a/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md b/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
new file mode 100644
index 000000000..bc0a80e1d
--- /dev/null
+++ b/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
@@ -0,0 +1,49 @@
+---
+title: 'Las cookies de sesión se comparten entre distintos enlaces cuando no se encuentran en el mismo nivel de ruta'
+id: 4pKeUI7qtdByaQowYs19Et
+status: PUBLISHED
+createdAt: 2023-10-25T01:06:04.190Z
+updatedAt: 2023-10-25T01:06:04.707Z
+publishedAt: 2023-10-25T01:06:04.707Z
+firstPublishedAt: 2023-10-25T01:06:04.707Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: las-cookies-de-sesion-se-comparten-entre-distintos-enlaces-cuando-no-se-encuentran-en-el-mismo-nivel-de-ruta
+locale: es
+kiStatus: No Fix
+internalReference: 925071
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las cookies para la información de sesión son exclusivas de la vinculación de cuenta específica, pero las vinculaciones que no están en el mismo nivel de ruta pueden recibir cookies de niveles inferiores, lo que provoca problemas.
+
+Si son de la misma cuenta, la información de Sesión se mezclará y anulará parámetros críticos. Si son de cuentas diferentes, puede bloquear las peticiones, generando errores como "las peticiones entre cuentas no están permitidas".
+
+
+##
+
+## Simulación
+
+
+Un ejemplo de escenario es una tienda que utiliza la ruta raíz `/` para su idioma por defecto (inglés) y `/fr` para un segundo idioma (francés). La información de la tienda en inglés puede afectar a la tienda en francés y viceversa.
+
+Otro ejemplo es una tienda B2C bajo `/us` para el país específico y la tienda B2B bajo `/us/corporate`.
+
+
+
+## Workaround
+
+
+Las tiendas que comparten el mismo host/dominio pueden mantener el mismo patrón para su ruta sin mezclar diferentes niveles. Ideas de alternativas para los ejemplos presentados serían `/en` frente a `/fr` (ambos utilizando una ruta de un solo nivel) y `/us/personal` frente a `/us/corporativo` (ruta de dos niveles).
+
+
+
+
diff --git a/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
new file mode 100644
index 000000000..792e074da
--- /dev/null
+++ b/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -0,0 +1,56 @@
+---
+title: 'La interfaz de usuario de la configuración no actualiza el "periodo de caducidad" de las cotizaciones'
+id: 4CmuAYwDn7tcCiR9DQHSFb
+status: PUBLISHED
+createdAt: 2023-08-07T19:42:22.810Z
+updatedAt: 2024-05-08T18:04:41.362Z
+publishedAt: 2024-05-08T18:04:41.362Z
+firstPublishedAt: 2023-08-07T19:43:56.788Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: la-interfaz-de-usuario-de-la-configuracion-no-actualiza-el-periodo-de-caducidad-de-las-cotizaciones
+locale: es
+kiStatus: Backlog
+internalReference: 876576
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+B2B Quote settings UI no actualiza el valor del periodo de expiración; siempre es 30.
+
+
+##
+
+## Simulación
+
+
+
+- Acceda a la página de configuración de Cotizaciones B2B y cambie el "periodo de caducidad".
+- Actualice la página; no se aplica ningún cambio.
+
+
+
+## Workaround
+
+
+
+- Acceda a GraphQL IDE y seleccione vtex.b2b-quotes-graphql;
+- Utilice la siguiente consulta para obtener la fecha de caducidad:
+
+    { getAppSettings{ adminSetup { cartLifeSpan } }}
+
+- Envíe una mutación para actualizar la fecha de caducidad a un valor diferente:
+
+    mutation SaveAppSettings($input: AppSettingsInput!) { saveAppSettings(input: $input) { adminSetup { cartLifeSpan } }}{ "input": { "cartLifeSpan": }}
+
+
+
+
+
diff --git a/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md b/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md
new file mode 100644
index 000000000..cff1af4bf
--- /dev/null
+++ b/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md
@@ -0,0 +1,49 @@
+---
+title: 'Las opciones de envío se congelan al intentar seleccionar una opción'
+id: 7zrMuzLq8kpNLDc2l2FswA
+status: PUBLISHED
+createdAt: 2023-09-13T14:42:26.106Z
+updatedAt: 2024-05-21T14:04:53.005Z
+publishedAt: 2024-05-21T14:04:53.005Z
+firstPublishedAt: 2023-09-13T14:42:26.860Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: las-opciones-de-envio-se-congelan-al-intentar-seleccionar-una-opcion
+locale: es
+kiStatus: Fixed
+internalReference: 898888
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza la configuración de pago B2B y se va y viene entre los pasos de envío y pago, el envío se congela al intentar seleccionar una opción.
+
+
+##
+
+## Simulación
+
+
+
+- Asegúrese de que tiene al menos 2 direcciones registradas en el Centro de Costes;
+- Añada cualquier producto a la cesta y vaya al paso de pago;
+- Edite el envío, vuelva al paso de pago y actualice la página;
+- Edite el envío de nuevo e intente seleccionar una opción, la interfaz de usuario se congelará
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md b/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
new file mode 100644
index 000000000..4499cf996
--- /dev/null
+++ b/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
@@ -0,0 +1,49 @@
+---
+title: 'La política de envíos bloqueada en estado de tramitación se muestra como activa en la nueva interfaz de usuario de logística.'
+id: 6c6JrnkhTdz5kM8kGzsRXQ
+status: PUBLISHED
+createdAt: 2023-10-25T23:48:45.891Z
+updatedAt: 2023-11-27T21:18:03.811Z
+publishedAt: 2023-11-27T21:18:03.811Z
+firstPublishedAt: 2023-10-25T23:48:46.471Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: la-politica-de-envios-bloqueada-en-estado-de-tramitacion-se-muestra-como-activa-en-la-nueva-interfaz-de-usuario-de-logistica
+locale: es
+kiStatus: Fixed
+internalReference: 925914
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En ocasiones la póliza de transporte puede quedarse atascada en el estado de tramitación, pero en la nueva UI de logística no se ve porque informa de que el estado está activo.
+Este comportamiento puede estorbar a la hora de subir una nueva hoja de cálculo de portes, ya que el usuario asumirá que el proceso se ha completado al mostrar un estado activo, pero los nuevos datos no se verán reflejados.
+
+
+
+##
+
+## Simulación
+
+
+Tener una póliza de transporte en estado activo en la nueva UI, donde al intentar subir una nueva hoja de cálculo, los datos no se reflejan.
+
+
+
+
+## Workaround
+
+
+Para que la póliza de envío abandone el estado de tramitación en el que se encuentra, es necesaria una acción del equipo, tras la cual se podrá subir la hoja de cálculo y el proceso continuará con normalidad.
+
+
+
+
+
diff --git a/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md b/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
index 84534d0a0..d2c87a422 100644
--- a/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
+++ b/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
@@ -3,8 +3,8 @@ title: 'Se está estudiando una política de envíos que no entregue los fines d
 id: 25bhUZXA9sZvyFVNeMUSJl
 status: PUBLISHED
 createdAt: 2022-06-08T18:32:07.971Z
-updatedAt: 2022-11-25T21:59:34.643Z
-publishedAt: 2022-11-25T21:59:34.643Z
+updatedAt: 2024-02-16T20:25:34.078Z
+publishedAt: 2024-02-16T20:25:34.078Z
 firstPublishedAt: 2022-06-08T18:32:08.836Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: se-esta-estudiando-una-politica-de-envios-que-no-entregue-los-fines-de-semana
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 594828
 ---
 
diff --git a/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md b/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
index bfa6b217e..ac06e01a6 100644
--- a/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
+++ b/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
@@ -3,8 +3,8 @@ title: 'La política de envío con un MaxVolume incorrecto en la hoja de cálcul
 id: 7zIbmadcOfI3oHmkm8LmkY
 status: PUBLISHED
 createdAt: 2022-05-18T18:19:04.901Z
-updatedAt: 2022-11-25T21:59:49.182Z
-publishedAt: 2022-11-25T21:59:49.182Z
+updatedAt: 2024-02-16T20:25:21.794Z
+publishedAt: 2024-02-16T20:25:21.794Z
 firstPublishedAt: 2022-05-18T18:19:05.868Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: la-politica-de-envio-con-un-maxvolume-incorrecto-en-la-hoja-de-calculo-no-muestra-el-error-del-mensaje-en-la-simulacion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 380471
 ---
 
diff --git a/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md b/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
index 93b1d52da..7c6be0ed3 100644
--- a/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
+++ b/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
@@ -3,8 +3,8 @@ title: 'La vista previa de los envíos no utiliza el nombre del ANS para su visu
 id: 6v7vh0CSUfpiF04brZ0bgb
 status: PUBLISHED
 createdAt: 2022-05-06T20:46:38.910Z
-updatedAt: 2022-11-25T21:52:23.344Z
-publishedAt: 2022-11-25T21:52:23.344Z
+updatedAt: 2024-02-16T20:25:44.430Z
+publishedAt: 2024-02-16T20:25:44.430Z
 firstPublishedAt: 2022-05-06T20:46:39.731Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-vista-previa-de-los-envios-no-utiliza-el-nombre-del-ans-para-su-visualizacion-en-la-interfaz-de-usuario
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 574651
 ---
 
diff --git a/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md b/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
new file mode 100644
index 000000000..48471fc1c
--- /dev/null
+++ b/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
@@ -0,0 +1,47 @@
+---
+title: 'La vista previa del envío muestra el código postal de recogida para el envío cuando hay un paquete dividido para la recogida y el envío.'
+id: 7gGu9EUZGGXp4dRCCGipsA
+status: PUBLISHED
+createdAt: 2024-06-26T20:36:39.627Z
+updatedAt: 2024-06-26T20:36:40.541Z
+publishedAt: 2024-06-26T20:36:40.541Z
+firstPublishedAt: 2024-06-26T20:36:40.541Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-vista-previa-del-envio-muestra-el-codigo-postal-de-recogida-para-el-envio-cuando-hay-un-paquete-dividido-para-la-recogida-y-el-envio
+locale: es
+kiStatus: Backlog
+internalReference: 938124
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En la vista previa del envío, cuando se selecciona recoger en tienda, pero no todos los artículos están disponibles para esa recogida, la dirección mostrada para el envío es la de la recogida elegida, y no es posible cambiarla. Sin embargo, en el formulario de pedido, la dirección seleccionada para el envío es correcta.
+
+
+
+## Simulación
+
+
+
+- Añadir artículos al carrito donde al menos uno no está disponible para su recogida;
+- Añadir un código postal al carrito;
+- Cambiar a recogida en tienda;
+- El código postal mostrado para el envío es el de la recogida elegida.
+
+
+
+## Workaround
+
+
+Cambie el código postal en el paso de envío.
+
+
+
diff --git a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
index 7cc2231eb..2a2ab06c5 100644
--- a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
+++ b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'La vista previa de envío muestra erróneamente la fecha en la que está
 id: 6pbufuWTFkL4NK3xLIxj1z
 status: PUBLISHED
 createdAt: 2023-01-31T19:36:58.137Z
-updatedAt: 2023-01-31T19:36:58.933Z
-publishedAt: 2023-01-31T19:36:58.933Z
+updatedAt: 2024-07-01T18:48:44.228Z
+publishedAt: 2024-07-01T18:48:44.228Z
 firstPublishedAt: 2023-01-31T19:36:58.933Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-vista-previa-de-envio-muestra-erroneamente-la-fecha-en-la-que-esta-programada-la-entrega
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 743774
 ---
 
diff --git a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
index 4d5874689..e25b4d0b5 100644
--- a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
+++ b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
@@ -1,18 +1,18 @@
 ---
-title: 'Vista previa de envío muestra erróneamente el precio cuando es entrega programada'
+title: 'La vista previa del envío muestra erróneamente el precio cuando se trata de una entrega programada'
 id: 1348f4mDxoxAT7pTKBxm29
 status: PUBLISHED
 createdAt: 2023-01-31T19:16:25.118Z
-updatedAt: 2023-02-01T20:32:44.535Z
-publishedAt: 2023-02-01T20:32:44.535Z
+updatedAt: 2024-03-27T15:40:02.745Z
+publishedAt: 2024-03-27T15:40:02.745Z
 firstPublishedAt: 2023-01-31T19:16:25.874Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: vista-previa-de-envio-muestra-erroneamente-el-precio-cuando-es-entrega-programada
+slug: la-vista-previa-del-envio-muestra-erroneamente-el-precio-cuando-se-trata-de-una-entrega-programada
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 532487
 ---
 
diff --git a/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md b/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md
index 9e7d1676f..fc43b3917 100644
--- a/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md
+++ b/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md
@@ -3,8 +3,8 @@ title: 'El campo de código postal de la vista previa de envío no está oculto'
 id: 6YCl40YEzu1HGkfHkcjGqu
 status: PUBLISHED
 createdAt: 2023-05-09T13:27:51.259Z
-updatedAt: 2023-05-09T13:27:51.724Z
-publishedAt: 2023-05-09T13:27:51.724Z
+updatedAt: 2024-02-20T22:22:29.335Z
+publishedAt: 2024-02-20T22:22:29.335Z
 firstPublishedAt: 2023-05-09T13:27:51.724Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-campo-de-codigo-postal-de-la-vista-previa-de-envio-no-esta-oculto
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 821984
 ---
 
diff --git a/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md b/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
new file mode 100644
index 000000000..08db353fd
--- /dev/null
+++ b/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
@@ -0,0 +1,48 @@
+---
+title: 'Las promociones de envío que se aplican en distintos SLA provocan divergencias en el Tax Hub'
+id: 3uI0b4FmXUh4uue5kFyFNy
+status: PUBLISHED
+createdAt: 2023-10-09T13:42:08.767Z
+updatedAt: 2023-10-23T11:59:12.329Z
+publishedAt: 2023-10-23T11:59:12.329Z
+firstPublishedAt: 2023-10-09T13:42:09.636Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: las-promociones-de-envio-que-se-aplican-en-distintos-sla-provocan-divergencias-en-el-tax-hub
+locale: es
+kiStatus: Fixed
+internalReference: 916423
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando las promociones de envío aplican para diferentes SLAs, siendo uno de ellos el envío gratuito, causa divergencia en la solicitud enviada por el Tax Hub, impidiendo que el pedido sea realizado.
+
+
+##
+
+## Simulación
+
+
+
+- Crear una promoción de envío gratuito para un SLA específico;
+- Crear cualquier otra promoción de envío para otro ANS;
+- Intentar realizar un pedido, aparece el mensaje "No se ha podido crear el pedido solicitado. Por favor, inténtelo de nuevo".
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md b/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
new file mode 100644
index 000000000..e44ac24e8
--- /dev/null
+++ b/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
@@ -0,0 +1,34 @@
+---
+title: 'El paso de envío con código postal no funciona para algunos países (Emiratos Árabes Unidos)'
+id: 2nlXX0e1q1MLiSjCG1U1Uf
+status: PUBLISHED
+createdAt: 2024-06-21T16:31:14.956Z
+updatedAt: 2024-07-16T13:10:07.140Z
+publishedAt: 2024-07-16T13:10:07.140Z
+firstPublishedAt: 2024-06-21T16:31:15.891Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: el-paso-de-envio-con-codigo-postal-no-funciona-para-algunos-paises-emiratos-arabes-unidos
+locale: es
+kiStatus: Fixed
+internalReference: 312132
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+## **Resumen**
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/shopee-failed-to-create-product-variations.md b/docs/known-issues/es/shopee-failed-to-create-product-variations.md
index 8316ed702..ee61dd9c4 100644
--- a/docs/known-issues/es/shopee-failed-to-create-product-variations.md
+++ b/docs/known-issues/es/shopee-failed-to-create-product-variations.md
@@ -3,8 +3,8 @@ title: '[Shopee] Error al crear variaciones de producto'
 id: 5IKAkqtm8eejg2IhzrCgSz
 status: PUBLISHED
 createdAt: 2022-10-25T16:29:19.572Z
-updatedAt: 2023-02-07T12:56:37.721Z
-publishedAt: 2023-02-07T12:56:37.721Z
+updatedAt: 2024-02-16T20:24:45.182Z
+publishedAt: 2024-02-16T20:24:45.182Z
 firstPublishedAt: 2022-10-25T16:29:20.906Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: shopee-error-al-crear-variaciones-de-producto
 locale: es
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 685160
 ---
 
diff --git a/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md b/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md
new file mode 100644
index 000000000..a21a1c033
--- /dev/null
+++ b/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md
@@ -0,0 +1,52 @@
+---
+title: 'Productos similares La IU se rompe con demasiados productos'
+id: 1gaBTJ1VlwLkoBb1636qoH
+status: PUBLISHED
+createdAt: 2023-07-25T15:53:49.976Z
+updatedAt: 2023-08-15T17:28:32.114Z
+publishedAt: 2023-08-15T17:28:32.114Z
+firstPublishedAt: 2023-07-25T15:53:50.941Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: productos-similares-la-iu-se-rompe-con-demasiados-productos
+locale: es
+kiStatus: Backlog
+internalReference: 868425
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al abrir un formulario de producto con más de 6 productos similares la visualización UI se rompe
+para crecer en formato lista, empieza a añadir en formato escalera
+
+
+##
+
+## Simulación
+
+
+
+Añadir 10 productos similares a un producto
+
+
+
+## Workaround
+
+
+
+
+- Recomendamos utilizar la API para gestionar los productos similares
+- Trate de minimizar el zoom en la página ayuda a encajar mejor, funcionará en algunos casos
+
+
+
+
+
diff --git a/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md b/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
index 4d052aa3e..f5478e694 100644
--- a/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
+++ b/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
@@ -3,8 +3,8 @@ title: 'Simulación No es posible encontrar Productos del Catálogo V2 en la Pá
 id: 7jZBMAZHNilokDdbCxWzSs
 status: PUBLISHED
 createdAt: 2022-05-18T18:26:09.456Z
-updatedAt: 2022-11-25T21:59:14.900Z
-publishedAt: 2022-11-25T21:59:14.900Z
+updatedAt: 2024-02-16T20:28:57.548Z
+publishedAt: 2024-02-16T20:28:57.548Z
 firstPublishedAt: 2022-05-18T18:26:10.048Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: simulacion-no-es-posible-encontrar-productos-del-catalogo-v2-en-la-pagina-de-simulacion-de-envio
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 488362
 ---
 
diff --git a/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md b/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md
new file mode 100644
index 000000000..dea28de1d
--- /dev/null
+++ b/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md
@@ -0,0 +1,51 @@
+---
+title: 'La condición de pago único no aparece en el chekout.'
+id: 3L7GJTRaWWA9Wjw2zkQqtS
+status: PUBLISHED
+createdAt: 2022-06-29T11:57:22.859Z
+updatedAt: 2024-04-26T15:49:53.973Z
+publishedAt: 2024-04-26T15:49:53.973Z
+firstPublishedAt: 2022-06-29T11:57:23.251Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: la-condicion-de-pago-unico-no-aparece-en-el-chekout
+locale: es
+kiStatus: Backlog
+internalReference: 605568
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se configura una única condición de pago con una única opción de pago a plazos o múltiples condiciones de pago en las que sólo hay disponible una opción de pago a plazos para un carro específico, esta opción de pago a plazos no se muestra en el proceso de pago. Aunque aparece correctamente en `paymentData`, no es visible para el usuario. En su lugar, sólo se muestra la opción de pagar el valor total. Sin embargo, cuando se completa la transacción, el pago se procesa con la opción de pago a plazos correcta.
+
+
+##
+
+## Simulación
+
+
+
+- Configure una única condición de pago a plazos.
+- Vaya a la página de pago comprando cualquier artículo al azar.
+- Vaya a la pestaña Red en devtools y compruebe que la opción de pago a plazos se carga correctamente en la respuesta `paymentData`.
+- Compruebe el desplegable de opciones de pago en la página de pago. Observe que no aparece la opción de pago a plazos configurada; en su lugar, se muestra el importe total.
+- A pesar de este problema, al finalizar la compra, la transacción refleja correctamente la opción de pago a plazos elegida.
+
+
+
+## Workaround
+
+
+N/A
+
+Atenciosamente,
+Gisely Lacerda
+Ingeniera de Soporte de Producto, Equipo Shopper Journey
+
diff --git a/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md b/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md
new file mode 100644
index 000000000..956e349da
--- /dev/null
+++ b/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md
@@ -0,0 +1,49 @@
+---
+title: 'El editor del sitio no permite cambios en la plantilla condicional'
+id: dGuXWBUUZdMB0nfndLPZ9
+status: PUBLISHED
+createdAt: 2023-07-13T20:05:31.326Z
+updatedAt: 2023-07-13T20:05:31.834Z
+publishedAt: 2023-07-13T20:05:31.834Z
+firstPublishedAt: 2023-07-13T20:05:31.834Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: el-editor-del-sitio-no-permite-cambios-en-la-plantilla-condicional
+locale: es
+kiStatus: Backlog
+internalReference: 861920
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando una plantilla se establece como la condicional no es capaz de realizar cambios en él a través del editor del sitio.
+
+
+##
+
+## Simulación
+
+
+
+- añada una plantilla condicional a una de las páginas del CMS
+- asegúrese de que se aplica la condición para que funcione
+- intente editar esa página a través del editor del sitio
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md b/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
index 5c6706e9d..48dd0bb16 100644
--- a/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
+++ b/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
@@ -3,8 +3,8 @@ title: 'Versión de escritorio del sitio cuando se accede a través de IPad en S
 id: 17jzhKnc8X1bKo5ExwEY5L
 status: PUBLISHED
 createdAt: 2023-01-17T18:24:02.908Z
-updatedAt: 2023-01-17T18:27:50.296Z
-publishedAt: 2023-01-17T18:27:50.296Z
+updatedAt: 2024-02-16T20:26:44.446Z
+publishedAt: 2024-02-16T20:26:44.446Z
 firstPublishedAt: 2023-01-17T18:24:03.621Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: version-de-escritorio-del-sitio-cuando-se-accede-a-traves-de-ipad-en-safari
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 735208
 ---
 
diff --git a/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md b/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md
new file mode 100644
index 000000000..6e1e33c1e
--- /dev/null
+++ b/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md
@@ -0,0 +1,79 @@
+---
+title: 'El sitemap no se genera/actualiza'
+id: 1tJ4XHtbnFsfS30JWXwxb0
+status: PUBLISHED
+createdAt: 2023-05-17T13:58:46.443Z
+updatedAt: 2024-02-16T18:17:17.707Z
+publishedAt: 2024-02-16T18:17:17.707Z
+firstPublishedAt: 2023-05-17T13:58:47.102Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-sitemap-no-se-generaactualiza
+locale: es
+kiStatus: Backlog
+internalReference: 827104
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Hay tres escenarios en los que el mapa del sitio no está siendo generado/actualizado:
+
+
+
+1. Cuando tenemos un producto no encontrado o con algún tipo de problema en el catálogo no se genera el mapa del sitio. Puedes buscar los logs en OpenSearch, en este caso, para comprobar qué producto tiene un problema;
+
+
+
+2. Cuando la cuenta tiene la aplicación `search.resolver@1.x` el mapa del sitio puede tener errores cuando:
+
+
+
+- Una categoría tiene su primer producto procedente de una categoría similar (las reglas de comercio pueden tener un impacto en este caso dependiendo del producto que estés promocionando);
+
+- La página de búsqueda/marca/categoría no tiene productos, en este caso, la página no está indexada en el mapa del sitio, y su generación se bloquea.
+
+
+3. Los productos que no tienen la política comercial establecida en el catálogo no serán recibidos por el sitemap
+
+
+
+##
+
+## Simulación
+
+
+
+Trate de generar el mapa del sitio para una cuenta que tiene uno de los escenarios descritos anteriormente y se bloqueará
+
+
+
+## Workaround
+
+
+
+
+- Crear un nuevo espacio de trabajo
+- Instale search-resolver@0.x `(vtex install vtex.search-resolver@0.x)`.
+- Generar el nuevo mapa del sitio
+- Ahora puede revertir search-resolver a 1.x (`vtex install vtex.search-resolver@1.x`)
+- Promover el espacio de trabajo creado a maestro
+
+Obs: Esta solución puede no funcionar siempre. A veces la tienda puede tener tantos productos inválidos que incluso el `search-resolver@0.x` no actualizará el mapa del sitio.
+
+Pero eventualmente, usted necesitará arreglar el escenario que impide que el mapa del sitio sea generado.
+
+Tenga en cuenta que la actualización de la tienda a resolver@0.x y generar el mapa del sitio en un espacio de trabajo es la solución porque algunos casos no válidos no se producen en nuestra búsqueda de legado
+
+
+
+
+
+
diff --git a/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md b/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
new file mode 100644
index 000000000..08b15e734
--- /dev/null
+++ b/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
@@ -0,0 +1,52 @@
+---
+title: 'SKU admin se rompe al enviar un código de referencia de más de 50 caracteres'
+id: 3AhyVsOpwkRUEHT77Wcc1A
+status: PUBLISHED
+createdAt: 2023-08-21T17:52:27.931Z
+updatedAt: 2023-08-21T17:52:28.799Z
+publishedAt: 2023-08-21T17:52:28.799Z
+firstPublishedAt: 2023-08-21T17:52:28.799Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: sku-admin-se-rompe-al-enviar-un-codigo-de-referencia-de-mas-de-50-caracteres
+locale: es
+kiStatus: Backlog
+internalReference: 884789
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera que el usuario pueda cambiar el código de referencia de la SKU utilizando el admin. Sin embargo, cuando se introduce un valor de más de 50 caracteres, el administrador se bloquea y muestra un mensaje de error.
+
+
+##
+
+## Simulación
+
+
+
+- Ir al admin de una SKU: `/admin/Site/SkuForm.aspx?IdSku=`
+- Ir al campo **Código de referencia** y poner un valor con más de 50 caracteres como:
+
+    ABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEABCDEW
+
+- Haga clic en salve
+- Aparecerá un mensaje "algo ha ido mal" en la parte frontal.
+
+
+
+## Workaround
+
+
+No envíe más de 50 caracteres en el campo **Código de referencia** de una SKU
+
+
+
+
diff --git a/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md b/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
new file mode 100644
index 000000000..cb0fbc5c7
--- /dev/null
+++ b/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
@@ -0,0 +1,47 @@
+---
+title: 'Sku denegado en Skus recibidos después de la aceleración en el catálogo del mercado'
+id: 4fleOaKNp6ALXdmZcAVCg0
+status: PUBLISHED
+createdAt: 2024-01-23T12:50:23.697Z
+updatedAt: 2024-01-23T12:50:24.398Z
+publishedAt: 2024-01-23T12:50:24.398Z
+firstPublishedAt: 2024-01-23T12:50:24.398Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: sku-denegado-en-skus-recibidos-despues-de-la-aceleracion-en-el-catalogo-del-mercado
+locale: es
+kiStatus: Backlog
+internalReference: 970208
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al aprobar un nuevo producto en Skus Recibidos (automática o manualmente) el módulo de sugerencias se comunica con el catálogo del Marketplace para realizar la acción.
+Si en este momento el módulo de catálogo devuelve un error de estrangulamiento, el sku acaba siendo rechazado por el matcher a pesar de tener toda la información correcta.
+
+
+##
+
+## Simulación
+
+
+Este no es un escenario fácil (o habitual) de replicar porque depende de que otro sistema no funcione como debería y devuelva un throttling.
+
+
+
+## Workaround
+
+
+Aprobar el sku manualmente desde el área de rechazados de Skus Recibidos.
+
+
+
+
+
diff --git a/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md b/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md
new file mode 100644
index 000000000..a9983935d
--- /dev/null
+++ b/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md
@@ -0,0 +1,52 @@
+---
+title: 'La actualización de archivos SKU no actualiza las etiquetas de versión ?v'
+id: 5Uw2VIBtTNDY3Ha5WDzGXJ
+status: PUBLISHED
+createdAt: 2023-06-29T14:37:56.437Z
+updatedAt: 2024-07-01T18:49:06.220Z
+publishedAt: 2024-07-01T18:49:06.220Z
+firstPublishedAt: 2023-06-29T14:37:57.352Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-actualizacion-de-archivos-sku-no-actualiza-las-etiquetas-de-version-v
+locale: es
+kiStatus: No Fix
+internalReference: 852869
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, cuando un archivo de imagen SKU se actualiza a través de la API para estar en la misma posición que uno anterior, su etiqueta de versión (?v=) en la página del producto no se actualiza correctamente.
+
+
+##
+
+## Simulación
+
+
+
+
+- Para un sku que ya tiene archivos en él, intente actualizar una imagen a una nueva.
+- Para que el usuario y/o los sistemas interpreten correctamente el archivo que se está cambiando, la etiqueta de versión (?v=) bajo la imagen href en el HTML de la página del producto debería actualizarse.
+- Sin embargo, esto no ocurre cuando se utiliza esta API para realizar dichas actualizaciones.
+
+
+
+
+
+## Workaround
+
+
+Borrar todos los archivos SKU y reinsertarlos desde cero obliga a actualizarlo.
+
+O
+
+Un borrado del indexador fuerza la actualización.
+
diff --git a/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
new file mode 100644
index 000000000..b2c865d00
--- /dev/null
+++ b/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -0,0 +1,50 @@
+---
+title: 'La API de inserción de archivos de SKU no responde con la propiedad "Texto".'
+id: 2rPsyAkpGNCVIM4yGlcMBw
+status: PUBLISHED
+createdAt: 2024-04-10T14:59:14.341Z
+updatedAt: 2024-07-22T19:38:40.304Z
+publishedAt: 2024-07-22T19:38:40.304Z
+firstPublishedAt: 2024-04-10T14:59:15.416Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-api-de-insercion-de-archivos-de-sku-no-responde-con-la-propiedad-texto
+locale: es
+kiStatus: Fixed
+internalReference: 1014787
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, la API para crear un archivo sku https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file no responde con la propiedad "Texto" correctamente.
+
+Los datos de este campo se aceptan y se envían a la base de datos, sin embargo, el cuerpo de respuesta de cualquiera de los métodos del archivo SKU (GET, PUT, POST) siempre responden el cuerpo de respuesta JSON que contiene la propiedad "Text" como null, incluso cuando tiene un valor guardado en él.
+
+
+##
+
+## Simulación
+
+
+1 - Usando la API mencionada, envíe un cuerpo de petición para una imagen válida que tenga un campo "Texto" con un dato no nulo.
+2 - Compruebe el cuerpo de respuesta de esta API o utilice una solicitud GET para obtener los datos de este archivo, el campo "Texto" será nulo.
+3 - Sin embargo, si va a la administración de la tienda, en https://VTEX.myvtex.com/admin/Site/SkuForm.aspx?IdSku= verá que el texto muestra los datos del campo enviado.
+
+
+
+## Workaround
+
+
+Obtenga los datos del campo Texto desde el administrador, las hojas de cálculo o las API de búsqueda.
+
+
+
+
+
diff --git a/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md b/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
index 40577bfa4..86b3bb766 100644
--- a/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
+++ b/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
@@ -3,8 +3,8 @@ title: 'SKU eliminado de Amazon SC no se desactiva en el Portal de Amazon'
 id: 9yeLgMrhp9nSu9MtJ518G
 status: PUBLISHED
 createdAt: 2023-05-18T11:43:30.694Z
-updatedAt: 2023-05-18T11:43:31.301Z
-publishedAt: 2023-05-18T11:43:31.301Z
+updatedAt: 2023-08-14T17:50:14.349Z
+publishedAt: 2023-08-14T17:50:14.349Z
 firstPublishedAt: 2023-05-18T11:43:31.301Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: sku-eliminado-de-amazon-sc-no-se-desactiva-en-el-portal-de-amazon
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 827760
 ---
 
diff --git a/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md b/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md
index fdf1a5d0d..d7f288320 100644
--- a/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md
+++ b/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md
@@ -3,8 +3,8 @@ title: 'El modo de visualización SELECT del selector SKU no funciona en las est
 id: 4viowN3tnbsdc0f1bqXrux
 status: PUBLISHED
 createdAt: 2023-01-18T12:24:32.528Z
-updatedAt: 2023-01-18T12:24:33.003Z
-publishedAt: 2023-01-18T12:24:33.003Z
+updatedAt: 2024-02-16T20:24:43.422Z
+publishedAt: 2024-02-16T20:24:43.422Z
 firstPublishedAt: 2023-01-18T12:24:33.003Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: el-modo-de-visualizacion-select-del-selector-sku-no-funciona-en-las-estanterias
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 682152
 ---
 
diff --git a/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md b/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
new file mode 100644
index 000000000..e11e861fa
--- /dev/null
+++ b/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
@@ -0,0 +1,56 @@
+---
+title: 'El selector de SKU no elige el SKU correcto cuando hay variaciones similares con subcadenas.'
+id: 7EY2RMqoJM7bbLZvyVDdRn
+status: PUBLISHED
+createdAt: 2024-06-11T18:15:27.243Z
+updatedAt: 2024-07-03T20:19:45.157Z
+publishedAt: 2024-07-03T20:19:45.157Z
+firstPublishedAt: 2024-06-11T18:15:28.029Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: el-selector-de-sku-no-elige-el-sku-correcto-cuando-hay-variaciones-similares-con-subcadenas
+locale: es
+kiStatus: Fixed
+internalReference: 1047992
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al tener una subcadena de la variación en la SKU elegida en otra variación disponible, podríamos no seleccionar la SKU elegida
+
+
+##
+
+## Simulación
+
+
+
+Necesitamos tener una variación disponible que tenga una subcadena de otra variación disponible del mismo producto, por ejemplo:
+
+Valor de la variación: 5
+Otra Variación con subcadena: 5.5
+
+O
+
+Valor de la variación: negro
+Otra Variación con subcadena: blanco y negro
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/sku-selector-with-multilpe-contexts.md b/docs/known-issues/es/sku-selector-with-multilpe-contexts.md
new file mode 100644
index 000000000..89c328752
--- /dev/null
+++ b/docs/known-issues/es/sku-selector-with-multilpe-contexts.md
@@ -0,0 +1,52 @@
+---
+title: 'Selector de SKU con contextos multilpe'
+id: 4n6ap30jnJOrzflLCnVziO
+status: PUBLISHED
+createdAt: 2024-01-29T13:31:21.812Z
+updatedAt: 2024-07-11T19:19:22.383Z
+publishedAt: 2024-07-11T19:19:22.383Z
+firstPublishedAt: 2024-01-29T13:31:22.391Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: selector-de-sku-con-contextos-multilpe
+locale: es
+kiStatus: Fixed
+internalReference: 341322
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+El selector SKU dentro de la vista modal/rápida no está en el mismo contexto que está en la página de búsqueda y en la página de producto.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/zIQ15WW7s1Zo24Z1I5tFT4H3y/?name=image.png)
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/gnAeV75W2Sip3Pl1zfQyAiWOI/?name=image.png)
+
+
+##
+
+## Simulación
+
+
+
+- Ve a cualquier tienda que tenga vista rápida y selector de SKU.
+- Elija un SKU y vaya al modo de vista rápida
+- Cambia el SKU dentro del modal de vista rápida
+- Salga del modo de vista rápida y notará que el SKU no cambió, sólo cambió dentro del contexto de vista rápida
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md b/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
index a875744a3..f4362508b 100644
--- a/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
+++ b/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
@@ -3,8 +3,8 @@ title: 'Los filtros de especificación de SKU no se cargan cuando la SKU sólo e
 id: 5SpoacD49oxDDGJjepUEoL
 status: PUBLISHED
 createdAt: 2022-03-21T17:41:20.048Z
-updatedAt: 2022-11-25T21:58:05.886Z
-publishedAt: 2022-11-25T21:58:05.886Z
+updatedAt: 2024-02-16T20:29:10.321Z
+publishedAt: 2024-02-16T20:29:10.321Z
 firstPublishedAt: 2022-03-21T17:41:20.389Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: los-filtros-de-especificacion-de-sku-no-se-cargan-cuando-la-sku-solo-esta-disponible-en-un-vendedor-de-etiqueta-blanca
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 431888
 ---
 
diff --git a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
index 83f2225ae..333a748a5 100644
--- a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
@@ -3,8 +3,8 @@ title: 'Skus de un mismo producto creados por separado (cuentas con el indicador
 id: 1nkfd9OuKTFsnBWe1k6dif
 status: PUBLISHED
 createdAt: 2023-02-15T12:22:35.143Z
-updatedAt: 2023-02-15T12:22:35.839Z
-publishedAt: 2023-02-15T12:22:35.839Z
+updatedAt: 2023-11-28T19:01:37.291Z
+publishedAt: 2023-11-28T19:01:37.291Z
 firstPublishedAt: 2023-02-15T12:22:35.839Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: skus-de-un-mismo-producto-creados-por-separado-cuentas-con-el-indicador-autoaprobar-activado
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 467112
 ---
 
diff --git a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
new file mode 100644
index 000000000..c77bc0243
--- /dev/null
+++ b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
@@ -0,0 +1,57 @@
+---
+title: 'Skus de un mismo producto creados por separado en cuentas con el indicador Autoaprobar activado.'
+id: 5xWm9hzTO0Yuv0e2UuMgH6
+status: PUBLISHED
+createdAt: 2024-01-09T12:39:19.465Z
+updatedAt: 2024-07-22T19:31:17.990Z
+publishedAt: 2024-07-22T19:31:17.990Z
+firstPublishedAt: 2024-01-09T19:59:00.420Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: skus-de-un-mismo-producto-creados-por-separado-en-cuentas-con-el-indicador-autoaprobar-activado
+locale: es
+kiStatus: Fixed
+internalReference: 962986
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El vendedor envía un lote con skus del mismo producto (todas las variaciones posibles del producto).
+
+En lugar de crearse como un producto con sus variaciones, todos los skus se crean por separado.
+
+Este comportamiento está ocurriendo porque la cuenta del marketplace tiene activado el flag de Autoaprobación y el vendedor está enviando todos los skus a la vez.
+
+Normalmente, el sistema tiene un bloqueo, por nombre de producto, para prevenir este tipo de situación ya que el Matcher tiene más de una cola procesando los skus. Pero este bloqueo no está implementado en el flujo de trabajo Autoaprobar.
+
+
+##
+
+## Simulación
+
+
+1. Habilite la bandera de Autoaprobación en el Mercado;
+2. El vendedor envía un lote de productos y sus skus (variaciones) a la vez;
+3. El primer skus del producto se crea correctamente, pero los demás se crean por separado.
+
+
+
+## Workaround
+
+
+Para evitar esta situación, hay dos maneras posibles.
+
+1. El vendedor envía los skus lentamente dentro de un plazo;
+2. 2. Desactivar el indicador Autoaprobar en el Mercado.
+
+
+
+
+
diff --git a/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md b/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
index adfd294ab..7a6ff2fa4 100644
--- a/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
+++ b/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
@@ -3,8 +3,8 @@ title: 'SkuServicoForm.aspx no lista las tablas de valores al principio para un
 id: 2QrjRVvJXiWmRXTYf8DrMK
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:32.216Z
-updatedAt: 2022-11-25T21:50:15.511Z
-publishedAt: 2022-11-25T21:50:15.511Z
+updatedAt: 2024-02-16T20:27:50.659Z
+publishedAt: 2024-02-16T20:27:50.659Z
 firstPublishedAt: 2022-06-28T16:55:32.529Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: skuservicoformaspx-no-lista-las-tablas-de-valores-al-principio-para-un-tipo-de-valor
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 335819
 ---
 
diff --git a/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md b/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
new file mode 100644
index 000000000..57b345582
--- /dev/null
+++ b/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
@@ -0,0 +1,51 @@
+---
+title: 'La oferta de SLA fluctúa entre diferentes políticas de envío debido al caché en la fecha estimada de 30 segundos'
+id: 2uN3bVrxHhj6Xs6TeQTJDr
+status: PUBLISHED
+createdAt: 2024-05-21T19:34:50.437Z
+updatedAt: 2024-05-21T19:38:10.682Z
+publishedAt: 2024-05-21T19:38:10.682Z
+firstPublishedAt: 2024-05-21T19:34:53.918Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: la-oferta-de-sla-fluctua-entre-diferentes-politicas-de-envio-debido-al-cache-en-la-fecha-estimada-de-30-segundos
+locale: es
+kiStatus: Backlog
+internalReference: 1036916
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La simulación logística puede oscilar entre ofrecer SLAs si el cliente tiene políticas de envío con el mismo precio, tiempo de entrega, SlaType, coste de muelle y configuración de almacén, pero diferente prioridad de muelle.
+Tenemos una caché que almacena el tiempo de entrega durante 30 segundos, por lo que cuando se hace una nueva simulación, otra política de envío con las mismas configuraciones que tiene un tiempo de muelle más largo puede ser ofrecida cuando no debería serlo.
+
+
+
+##
+
+## Simulación
+
+
+Políticas de envío A y B con el mismo tiempo total de entrega (1 día por ejemplo), precio, coste de muelle y almacén, pero con diferentes prioridades de muelle.
+Realizar un presupuesto a las 16:00:00 donde se ofrecerá la política de envío A con menor prioridad de muelle, entonces el resultado de la estimación sería para el día siguiente a las 16:01:00, estos datos se almacenan en caché durante 30 segundos;
+Al realizar un nuevo presupuesto a las 16:00:10 por ejemplo, se ofrecerá la política de envío B con mayor prioridad de muelle, ya que en el primer presupuesto la hora de entrega sería por ejemplo a las 16:01:00 almacenada en caché durante 30 segundos, mientras que el segundo presupuesto B se elige porque también tiene la estimación para el día siguiente pero a las 16:00:00.
+
+
+
+
+## Workaround
+
+
+No existe ninguna solución para un escenario con la misma configuración que la descrita anteriormente.
+
+
+
+
+
diff --git a/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md b/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
new file mode 100644
index 000000000..e5ff478b6
--- /dev/null
+++ b/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
@@ -0,0 +1,49 @@
+---
+title: 'Slider-layout bug when using prop infinite as always on mobile'
+id: 4JERnak05tr2K8ICjjPjrN
+status: PUBLISHED
+createdAt: 2023-10-17T17:38:34.443Z
+updatedAt: 2023-10-17T17:38:35.106Z
+publishedAt: 2023-10-17T17:38:35.106Z
+firstPublishedAt: 2023-10-17T17:38:35.106Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile
+locale: es
+kiStatus: Backlog
+internalReference: 920725
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el slider-layout está configurado como `infinite: "always"` en el móvil el componente presenta un bug intermitente. Después de un rato desplazando la estantería los productos dejarán de aparecer y en su lugar aparecerá un espacio en blanco.
+
+
+##
+
+## Simulación
+
+
+
+- Establezca la propiedad `infinite: "always"`.
+- En el móvil, intente desplazar los productos
+- Eventualmente los productos dejarán de aparecer y el deslizador quedará en blanco
+
+
+
+## Workaround
+
+
+Utilice la opción `showNavigationArrows: "always"`, el problema solo ocurre al desplazarse
+
+
+
+
+
diff --git a/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md b/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
new file mode 100644
index 000000000..aa3088f94
--- /dev/null
+++ b/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
@@ -0,0 +1,58 @@
+---
+title: 'Slug y Link devueltos en la API Catalog Facets tienen formatos diferentes.'
+id: 3LbYdhZhjsvUuQNC7VJN5G
+status: PUBLISHED
+createdAt: 2024-03-12T15:43:07.017Z
+updatedAt: 2024-03-12T15:43:08.057Z
+publishedAt: 2024-03-12T15:43:08.057Z
+firstPublishedAt: 2024-03-12T15:43:08.057Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: slug-y-link-devueltos-en-la-api-catalog-facets-tienen-formatos-diferentes
+locale: es
+kiStatus: Backlog
+internalReference: 998397
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+API de Facetas de Catálogo descrita aquí: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/facets/search/-term-
+Los objetos de respuesta tienen el campo "Slug", "Link" y "LinkEncoded". Sin embargo, estos campos deberían tener el mismo formato, pero divergen en el objeto PriceRanges cuando el valor tiene casos decimales.
+
+Ejemplo:
+Slug: "de-100-a-199.99"
+Enlace: "/category-test/de-100-a-199-99?map=c,priceFrom"
+
+El Slug tiene el carácter "." mientras que el Link tiene el carácter "-".
+
+
+
+##
+
+## Simulación
+
+
+
+1. Tener una categoría con un priceRange con valores decimales.
+2. Solicitar la API de facetas
+3. Compruebe que los caracteres son diferentes.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md b/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
new file mode 100644
index 000000000..010481730
--- /dev/null
+++ b/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
@@ -0,0 +1,38 @@
+---
+title: 'El enlace de configuración de SMS en la plantilla de correo electrónico redirige al usuario a la página 404'
+id: ZjIBvieBRNlN5lThuvtBf
+status: PUBLISHED
+createdAt: 2024-06-21T17:58:11.722Z
+updatedAt: 2024-06-21T17:58:12.707Z
+publishedAt: 2024-06-21T17:58:12.707Z
+firstPublishedAt: 2024-06-21T17:58:12.707Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: el-enlace-de-configuracion-de-sms-en-la-plantilla-de-correo-electronico-redirige-al-usuario-a-la-pagina-404
+locale: es
+kiStatus: Backlog
+internalReference: 1054007
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En la pantalla de configuración de plantillas del sistema de centro de mensajes, hay un enlace que debería llevar al usuario a la configuración de la app de envío de SMS, pero esta app ya no está disponible y el enlace ahora devuelve 404, mostrando una pantalla con el mensaje "`store/not-found-box-title`".
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md b/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
index 3436a7e7e..4a352fb45 100644
--- a/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
+++ b/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
@@ -3,8 +3,8 @@ title: 'Algunas direcciones autocompletadas por Google no se pueden guardar en M
 id: DgYKHOqC0nnpHKEdcTeXQ
 status: PUBLISHED
 createdAt: 2022-04-28T19:44:12.222Z
-updatedAt: 2023-01-06T17:13:51.809Z
-publishedAt: 2023-01-06T17:13:51.809Z
+updatedAt: 2023-10-18T00:06:40.142Z
+publishedAt: 2023-10-18T00:06:40.142Z
 firstPublishedAt: 2022-05-10T18:17:39.573Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: algunas-direcciones-autocompletadas-por-google-no-se-pueden-guardar-en-mi-cuenta
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 415388
 ---
 
@@ -50,3 +50,6 @@ Ejemplo:
 
 No hay solución disponible para esto.
 
+
+
+
diff --git a/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md b/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
new file mode 100644
index 000000000..714628cb2
--- /dev/null
+++ b/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
@@ -0,0 +1,48 @@
+---
+title: 'Algunas funciones del componente de diseño adhesivo no funcionarán como se espera cuando se visualicen a través del navegador Safari.'
+id: 6qXYzloLLowKzEqIUX1IB0
+status: PUBLISHED
+createdAt: 2023-11-08T13:34:35.513Z
+updatedAt: 2024-02-16T20:55:46.662Z
+publishedAt: 2024-02-16T20:55:46.662Z
+firstPublishedAt: 2023-11-08T13:34:36.172Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: algunas-funciones-del-componente-de-diseno-adhesivo-no-funcionaran-como-se-espera-cuando-se-visualicen-a-traves-del-navegador-safari
+locale: es
+kiStatus: Backlog
+internalReference: 868535
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas funciones del componente de diseño pegajoso no funcionan como se espera cuando se ve a través del navegador Safari
+
+
+##
+
+## Simulación
+
+
+Utilizar el sticky layout e intentar visualizarlo en Safari a veces no se comporta correctamente. A continuación se muestran algunos de los comportamientos observados:
+
+- los menús pueden aparecer flotando aunque estén configurados en posición fija
+
+
+
+## Workaround
+
+
+Dado que se trata de un caso de uso muy específico para un navegador muy específico, actualmente no existe ninguna solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
new file mode 100644
index 000000000..bcdddef67
--- /dev/null
+++ b/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
@@ -0,0 +1,53 @@
+---
+title: 'Algunas funciones de gestión de inventario no funcionan correctamente en las cuentas del portal del vendedor'
+id: uJ4qws662c8pUnyfOV1fV
+status: PUBLISHED
+createdAt: 2024-03-18T17:54:20.400Z
+updatedAt: 2024-03-18T17:54:21.597Z
+publishedAt: 2024-03-18T17:54:21.597Z
+firstPublishedAt: 2024-03-18T17:54:21.597Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: algunas-funciones-de-gestion-de-inventario-no-funcionan-correctamente-en-las-cuentas-del-portal-del-vendedor
+locale: es
+kiStatus: Backlog
+internalReference: 1001665
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las funciones de gestión de inventario (como los enlaces a los productos) no se comportan como se espera en las cuentas del portal del vendedor. Esto ocurre porque este tipo de cuentas utilizan una versión diferente del catálogo.
+
+El módulo de Logística utiliza en esta UI una API de catalogV1.
+
+Sin embargo, no tenemos un proxy desde el catálogo del portal del vendedor a esta API en catalogV1.
+
+El impacto es que los enlaces proporcionados en los productos no abren la página del catálogo, pero en su lugar devuelve un error.
+
+
+##
+
+## Simulación
+
+
+
+1. Intente abrir los enlaces a los productos en una gestión de inventario portal vendedor.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md b/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
new file mode 100644
index 000000000..539a710fc
--- /dev/null
+++ b/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
@@ -0,0 +1,55 @@
+---
+title: 'Algunos caracteres especiales no se eliminan de las búsquedas de productos ni de la indexación'
+id: 3qbzEcCkXpaPA0U23trlwT
+status: DRAFT
+createdAt: 2022-04-26T22:41:20.214Z
+updatedAt: 2023-11-29T20:24:51.268Z
+publishedAt: 
+firstPublishedAt: 2022-04-26T22:42:16.929Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: algunos-caracteres-especiales-no-se-eliminan-de-las-busquedas-de-productos-ni-de-la-indexacion
+locale: es
+kiStatus: Backlog
+internalReference: 382382
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunos caracteres especiales no se eliminan completamente de las palabras clave buscadas o de la indexación de productos, lo que puede afectar a las búsquedas en algunos escenarios específicos.
+
+Los caracteres conocidos que dan lugar a este escenario son las comas (`,`), los puntos (`.`) y los dos puntos (`:`). Los demás suelen ignorarse y no generan problemas.
+
+Al registrar un producto, las comas y los puntos al final de las palabras se eliminan al indexar el producto, pero si están en medio de una palabra, se mantienen. Las palabras clave se dividen por espacios.
+
+Durante la búsqueda, los dos puntos son un valor reservado e invalidarán toda la consulta de texto.
+
+
+##
+
+## Simulación
+
+
+Para comas y puntos, un campo de producto que tiene un valor como palabras clave separadas por comas como `"coche,marcaespecial,azul"` se leerá como una sola palabra. La búsqueda de `marcaespecial` no encontrará este producto.
+
+En el caso de los dos puntos, un producto con el nombre `"vino tinto: versión especial"` puede encontrarse buscando por `vino`, pero buscar por `vino: versión especial` no funcionará. Toda la búsqueda será inválida y no se aplicará ningún filtro de texto.
+
+
+
+## Workaround
+
+
+En el caso de las comas y los puntos, se requiere un espacio después del carácter para dividir las palabras clave.
+
+Para una búsqueda usando dos puntos, no hay solución.
+
+
+
+
diff --git a/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md b/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md
new file mode 100644
index 000000000..5b88da2e7
--- /dev/null
+++ b/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md
@@ -0,0 +1,51 @@
+---
+title: 'Comportamiento inesperado en MasterData'
+id: 4E9jB5vkUMucnAuwUMOGQL
+status: PUBLISHED
+createdAt: 2023-09-18T21:27:15.291Z
+updatedAt: 2023-10-10T21:16:04.759Z
+publishedAt: 2023-10-10T21:16:04.759Z
+firstPublishedAt: 2023-09-18T21:27:15.908Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: comportamiento-inesperado-en-masterdata
+locale: es
+kiStatus: Backlog
+internalReference: 669048
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Incluso con datos disponibles (documentos), la información no se devuelve como se esperaba.
+Este comportamiento puede afectar a algunas de las siguientes funcionalidades:
+
+- Las imágenes en el Editor del Sitio (CMS) no están disponibles, debido mensaje de error "_Algo salió mal. Por favor, inténtelo de nuevo._";
+- No es posible acceder a las entidades y sus documentos, debido mensaje de error "_Ha ocurrido un error inesperado. Por favor, inténtelo de nuevo. Si el problema persiste, póngase en contacto con el servicio de asistencia._";
+- No se respeta el `_sort` en la API Buscar documentos;
+- No se devuelve información al utilizar Search documents API (una respuesta vacía, como `[]`), aunque contengan documentos.
+
+
+##
+
+## Simulación
+
+
+Como se trata de un comportamiento ocasional (evento relacionado con el clúster), no se puede simular.
+
+
+
+## Workaround
+
+
+El equipo de VTEX debe comprobar el clúster y, eventualmente, volver a indexar los datos o cambiar el clúster, para que los datos vuelvan a estar disponibles.
+
+
+
+
diff --git a/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md b/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
new file mode 100644
index 000000000..68b8d81a6
--- /dev/null
+++ b/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
@@ -0,0 +1,52 @@
+---
+title: 'Aparece un error en la administración del catálogo'
+id: 5TZLWNau0Vo6yp8URPsGcn
+status: PUBLISHED
+createdAt: 2023-09-26T17:00:49.516Z
+updatedAt: 2023-09-26T17:00:50.184Z
+publishedAt: 2023-09-26T17:00:50.184Z
+firstPublishedAt: 2023-09-26T17:00:50.184Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: aparece-un-error-en-la-administracion-del-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 907567
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera utilizar el admin sin restricciones. Sin embargo, a veces se muestra un error **Something Went Wrong** en el admin del catálogo.
+
+
+##
+
+## Simulación
+
+
+
+1. Abrir el Catálogo admin
+2. 2. Abra una sección del catálogo, por ejemplo: `/admin/Site/ValeForm.aspx`, `Product.aspx` , `ProdutoCategoriaSimilarForm.aspx` o `SkuForm.aspx`.
+3. Recibir un error **Algo ha ido mal** en el admin
+
+
+
+## Workaround
+
+
+
+- Intente utilizar el admin legado: `.vtexcommercestable.com.br/admin`
+- Intente recargar la página varias veces, o
+- Intente esperar algunos minutos y acceda nuevamente a la página
+
+
+
+
+
diff --git a/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md b/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
new file mode 100644
index 000000000..2c6f6a2b2
--- /dev/null
+++ b/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
@@ -0,0 +1,51 @@
+---
+title: 'Mensaje "Algo ha ido mal" al acceder a las rutas /a y /p en los almacenes de Portal'
+id: 2XGAGH8xpNqjJpAir6DKzz
+status: PUBLISHED
+createdAt: 2023-11-30T16:31:45.428Z
+updatedAt: 2023-11-30T16:31:45.990Z
+publishedAt: 2023-11-30T16:31:45.990Z
+firstPublishedAt: 2023-11-30T16:31:45.990Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: mensaje-algo-ha-ido-mal-al-acceder-a-las-rutas-a-y-p-en-los-almacenes-de-portal
+locale: es
+kiStatus: Backlog
+internalReference: 945226
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Se espera poder buscar cualquier término en los almacenes del Portal; sin embargo, las letras "A" y "P" no se pueden buscar directamente a través de la URL.
+Así, aparecerá un mensaje "Algo ha ido mal" al acceder a las rutas `/a` y `/p` en los almacenes del Portal
+
+
+##
+
+## Simulación
+
+
+
+1. Ir a una tienda del portal
+2. Ir al enlace `site.com/a` o `site.com/p`
+3. Ver un "Algo ha ido mal" en la portada
+
+
+
+## Workaround
+
+
+N/A a la ruta `/a
+Registrar una redirección en el CMS heredado de `/p` a `/?ft=p`
+
+
+
+
+
diff --git a/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
new file mode 100644
index 000000000..1f15ea2e2
--- /dev/null
+++ b/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -0,0 +1,50 @@
+---
+title: '"Algo salió mal" al añadir una dirección incompleta e intentar editarla'
+id: 3rWGAr4K86JAetSBJ75q3h
+status: PUBLISHED
+createdAt: 2024-01-02T21:11:17.425Z
+updatedAt: 2024-01-02T21:11:17.955Z
+publishedAt: 2024-01-02T21:11:17.955Z
+firstPublishedAt: 2024-01-02T21:11:17.955Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: algo-salio-mal-al-anadir-una-direccion-incompleta-e-intentar-editarla
+locale: es
+kiStatus: Backlog
+internalReference: 960064
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Durante la etapa de pago utilizando un comprador con un perfil completo, en el paso de rellenar los datos de envío, pulsando en la opción "Entregar en otra dirección", si sólo se añade el código postal y el comprador vuelve a la lista de direcciones (utilizando el botón "volver a la libreta de direcciones") y pulsa en "Actualizar la información de la dirección seleccionada" se produce un error con el mensaje "Algo ha ido mal".
+
+
+##
+
+## Simulación
+
+
+
+- Añadir artículos a la cesta y utilizar un correo electrónico con un perfil completo;
+- Durante la etapa de pago, al rellenar los datos de envío, haga clic en "Entregar en otra dirección";
+- Añada un código postal y vuelva a los datos de envío haciendo clic en el botón "Volver a la lista de direcciones";
+- Haga clic en "Actualizar la información de la dirección seleccionada".
+
+
+
+## Workaround
+
+
+
+- Actualice la página si aparece el error.
+
+
+
+
diff --git a/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md b/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md
index 2ea1fa645..b69dc1554 100644
--- a/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md
+++ b/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md
@@ -3,8 +3,8 @@ title: 'La ordenación por nombre funciona de forma diferente en las tiendas int
 id: 96cQG19ZAmAtVT0ykZ4nF
 status: PUBLISHED
 createdAt: 2022-06-20T12:11:22.846Z
-updatedAt: 2022-11-25T21:58:18.041Z
-publishedAt: 2022-11-25T21:58:18.041Z
+updatedAt: 2024-07-01T18:48:26.055Z
+publishedAt: 2024-07-01T18:48:26.055Z
 firstPublishedAt: 2022-06-20T12:11:23.353Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: la-ordenacion-por-nombre-funciona-de-forma-diferente-en-las-tiendas-integradas-antes-de-una-fecha
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 600468
 ---
 
diff --git a/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md b/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
new file mode 100644
index 000000000..a6dde768f
--- /dev/null
+++ b/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
@@ -0,0 +1,48 @@
+---
+title: 'El espacio en la propiedad street en Postal Code JSON afecta a la visualización del campo de dirección en la caja'
+id: Rr3wSsdC5hxMS8ttK4kIj
+status: PUBLISHED
+createdAt: 2023-08-01T22:30:35.290Z
+updatedAt: 2024-07-01T18:49:10.379Z
+publishedAt: 2024-07-01T18:49:10.379Z
+firstPublishedAt: 2023-08-01T22:30:36.187Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: el-espacio-en-la-propiedad-street-en-postal-code-json-afecta-a-la-visualizacion-del-campo-de-direccion-en-la-caja
+locale: es
+kiStatus: No Fix
+internalReference: 872935
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al activar el uso de la API de código postal en el formulario de dirección para países que no están en el modelo BR (country, state, city, neighborhood, street), estos países que no tienen todos estos campos rellenados en la API y necesitan poder introducir el resto de datos de dirección en el formulario de dirección en el checkout, el campo street del bloque de dirección no estará disponible si la propiedad street del JSON está con espacio, ya que se entenderá como rellenado y válido, lo que no permite proceder con el pedido.
+
+
+
+##
+
+## Simulación
+
+
+Crear un carrito en una tienda EMEA que utilice código postal y formulario de dirección y en la base de código postal el campo calle esté con espacio " " .
+El campo dirección no estará disponible para ser rellenado.
+
+
+
+## Workaround
+
+
+No existe
+
+
+
+
+
diff --git a/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md b/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
index c042ed7d1..6894a3291 100644
--- a/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
+++ b/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
@@ -3,8 +3,8 @@ title: 'El espacio en la identificación del almacén hace que fallen las solici
 id: M8SsnABs2HgYsUvNnjCFx
 status: PUBLISHED
 createdAt: 2022-09-20T21:51:05.157Z
-updatedAt: 2023-01-05T19:34:07.126Z
-publishedAt: 2023-01-05T19:34:07.126Z
+updatedAt: 2024-02-16T20:24:53.145Z
+publishedAt: 2024-02-16T20:24:53.145Z
 firstPublishedAt: 2022-09-20T21:51:05.702Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: el-espacio-en-la-identificacion-del-almacen-hace-que-fallen-las-solicitudes-de-logistica-interna
 locale: es
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 654370
 ---
 
diff --git a/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md b/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
index 5b0455660..1282869e6 100644
--- a/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
+++ b/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
@@ -3,8 +3,8 @@ title: 'Los caracteres especiales no pueden utilizarse para la búsqueda de CNPJ
 id: 4sgob00QXkGYPC3TjSpQeN
 status: PUBLISHED
 createdAt: 2022-06-21T15:35:26.675Z
-updatedAt: 2022-11-25T22:13:02.870Z
-publishedAt: 2022-11-25T22:13:02.870Z
+updatedAt: 2023-08-07T13:52:30.392Z
+publishedAt: 2023-08-07T13:52:30.392Z
 firstPublishedAt: 2022-06-21T15:35:27.341Z
 contentType: knownIssue
 productTeam: Storage
diff --git a/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md b/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
new file mode 100644
index 000000000..e1b927bfb
--- /dev/null
+++ b/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
@@ -0,0 +1,53 @@
+---
+title: 'Los caracteres especiales en invoiceNumber hacen que falle el flujo posterior a la compra'
+id: 1tVPSLsB9SSZIF1KrNn3k2
+status: PUBLISHED
+createdAt: 2023-12-14T18:31:27.213Z
+updatedAt: 2023-12-14T18:31:27.801Z
+publishedAt: 2023-12-14T18:31:27.801Z
+firstPublishedAt: 2023-12-14T18:31:27.801Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: los-caracteres-especiales-en-invoicenumber-hacen-que-falle-el-flujo-posterior-a-la-compra
+locale: es
+kiStatus: Backlog
+internalReference: 953285
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, SNO (Shipping Notification Order) acepta que se envíe un número de factura (invoiceNumber) a través de API y UI con un "carácter especial" al final o al principio de los datos, por ejemplo: "#123456".
+
+Sin embargo, cuando se reciben facturas en este formato, algunos flujos llevados a cabo por el sistema implicado en el flujo posterior a la compra acaban devolviendo un error porque son incapaces de procesar o pasar el importe recibido. Algunos ejemplos de flujos que pueden fallar son las actualizaciones de seguimiento, las actualizaciones del estado de los pedidos facturados, la comunicación con el sistema gifcard hub, y cualquier otro sistema que utilice datos invoiceNumber puede ver comprometido su flujo debido al uso de caracteres especiales en el campo invoiceNumber.
+
+
+##
+
+## Simulación
+
+
+1- Facture un pedido introduciendo el siguiente número de factura de ejemplo: "#123456"; (caracteres especiales al principio del número o al final)
+
+2- Tenga en cuenta que el pedido no se actualizará al estado facturado
+
+3- En el caso de flujos que impliquen a un vendedor, en el Obtener Pedido del pedido del vendedor será posible ver la factura guardada, pero aún así el pedido del marketplace no se actualizará a facturado, ya que el sistema no podrá pasar la factura.
+
+
+
+## Workaround
+
+
+Para estos casos, la solución alternativa es no utilizar los "caracteres especiales" en la composición invoiceNumber.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md b/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
index ea6bc03d2..cb793d0f2 100644
--- a/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
+++ b/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
@@ -3,8 +3,8 @@ title: 'Caracteres especiales en el nombre de la SKU rompe la selección de la S
 id: 1G4FSBVZqn44ke7YJTuBJA
 status: PUBLISHED
 createdAt: 2022-03-16T16:26:36.035Z
-updatedAt: 2022-11-25T22:11:14.593Z
-publishedAt: 2022-11-25T22:11:14.593Z
+updatedAt: 2024-02-16T20:29:47.269Z
+publishedAt: 2024-02-16T20:29:47.269Z
 firstPublishedAt: 2022-03-16T16:26:36.503Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: caracteres-especiales-en-el-nombre-de-la-sku-rompe-la-seleccion-de-la-sku-en-las-paginas-del-portal-web-store-pdp-para-la-caja-de-radio-tipo-de-seleccion-de-la-categoria
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 337933
 ---
 
diff --git a/docs/known-issues/es/specifications-multiplied-on-catalog.md b/docs/known-issues/es/specifications-multiplied-on-catalog.md
new file mode 100644
index 000000000..8701b084f
--- /dev/null
+++ b/docs/known-issues/es/specifications-multiplied-on-catalog.md
@@ -0,0 +1,54 @@
+---
+title: 'Especificaciones multiplicadas sobre catálogo'
+id: 2d4LXPrbVibMR8atXO6o8X
+status: PUBLISHED
+createdAt: 2023-10-16T12:48:03.714Z
+updatedAt: 2023-10-16T12:48:59.814Z
+publishedAt: 2023-10-16T12:48:59.814Z
+firstPublishedAt: 2023-10-16T12:48:04.717Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: especificaciones-multiplicadas-sobre-catalogo
+locale: es
+kiStatus: Backlog
+internalReference: 919761
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El mercado puede aprobar los productos enviados por los vendedores en el módulo de Skus Recibidos.
+
+Cuando un producto tiene una especificación sku que coincide con la especificación que existe en la categoría del marketplace pero es un nuevo valor, este nuevo valor se crea en la especificación del marketplace.
+
+Los valores multiplicados pueden ocurrir cuando más de un sku con el mismo "nuevo valor" está siendo aprobado al mismo tiempo en Skus Recibidos en la misma categoría (o árbol) en la que se creó la especificación.
+
+Si la especificación se crea en la categoría raíz (no recomendado) este escenario podría ocurrir más fácilmente.
+
+
+
+## Simulación
+
+
+
+1. Cree una especificación sku en la categoría raíz;
+2. 2. Elegir 2 (o más) skus para aprobar en el módulo de Skus Recibidos que tengan el mismo valor de especificación sku (el valor no puede existir previamente en el marketplace).
+3. 3. Apruebe los skus (al mismo tiempo o en un pequeño intervalo) y compruebe si los valores de especificación se han multiplicado por el número de skus aprobados.
+
+
+
+## Workaround
+
+
+Apruebe los skus más lentamente y evite crear especificaciones en la categoría raíz.
+
+
+
+
+
diff --git a/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md b/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
index 29f5592a9..4c32a502e 100644
--- a/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
+++ b/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
@@ -3,8 +3,8 @@ title: 'El precio al contado del skuJson es incorrecto para los productos con m
 id: 6rgLJCE1DYPXZj1Pqt6hA2
 status: PUBLISHED
 createdAt: 2022-02-24T15:32:40.223Z
-updatedAt: 2022-11-25T22:10:27.000Z
-publishedAt: 2022-11-25T22:10:27.000Z
+updatedAt: 2024-02-16T20:30:08.928Z
+publishedAt: 2024-02-16T20:30:08.928Z
 firstPublishedAt: 2022-02-24T15:32:41.286Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: el-precio-al-contado-del-skujson-es-incorrecto-para-los-productos-con-multiples-vendedores
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 264791
 ---
 
diff --git a/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md b/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md
new file mode 100644
index 000000000..5549a5286
--- /dev/null
+++ b/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md
@@ -0,0 +1,46 @@
+---
+title: 'El estado en la lista de transacciones no coincide con el estado real'
+id: 3L0eXIO6aHmv9GSlPwCq3t
+status: PUBLISHED
+createdAt: 2024-03-22T16:23:32.369Z
+updatedAt: 2024-03-22T16:23:33.304Z
+publishedAt: 2024-03-22T16:23:33.304Z
+firstPublishedAt: 2024-03-22T16:23:33.304Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-estado-en-la-lista-de-transacciones-no-coincide-con-el-estado-real
+locale: es
+kiStatus: Backlog
+internalReference: 1004883
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Algunas transacciones pueden no coincidir con el estado real al abrirlas (problema de indexación).
+
+
+##
+
+## Simulación
+
+
+No hay forma de reproducirlo ya que esto ocurre con transacciones aleatorias.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
+
diff --git a/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md b/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md
index 4367375c9..4206cfe14 100644
--- a/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md
+++ b/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md
@@ -3,8 +3,8 @@ title: 'El cambio de stock se completa incluso después de recibir el error 500'
 id: 3dlP8iOBiL2tfPRvjm2kUZ
 status: PUBLISHED
 createdAt: 2022-06-20T12:40:08.834Z
-updatedAt: 2022-11-25T21:59:29.796Z
-publishedAt: 2022-11-25T21:59:29.796Z
+updatedAt: 2024-07-03T18:12:47.665Z
+publishedAt: 2024-07-03T18:12:47.665Z
 firstPublishedAt: 2022-06-20T12:40:09.126Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: el-cambio-de-stock-se-completa-incluso-despues-de-recibir-el-error-500
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 388176
 ---
 
@@ -26,13 +26,14 @@ internalReference: 388176
 El cliente está tratando de actualizar la cantidad de sku en el inventario y la solicitud recibió el error 500. A pesar del error, la cantidad en el inventario se cambia.
 
 
+##
 
 ## Simulación
 
 
 No ha sido posible reproducir el error.
 
-Pero en la respuesta vemos el error 500, y en el inventario vemos el mismo valor antes de la actualización.
+Pero en la respuesta vemos el error 500, y el inventario vemos el mismo valor antes de actualizar.
 
 
 
@@ -40,5 +41,5 @@ Pero en la respuesta vemos el error 500, y en el inventario vemos el mismo valor
 ## Workaround
 
 
-No hay ninguna solución. Pero es importante comprobar esta actualización ocurrió.
+No hay ninguna solución. Pero es importante comprobar esta actualización se produjo.
 
diff --git a/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md b/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
index 1de7000d7..099096a37 100644
--- a/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
+++ b/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
@@ -3,8 +3,8 @@ title: 'La API del catálogo stockkeepingunit permite valores de condición come
 id: 1ONAspL4Wj9fdu2tYcX4Ur
 status: PUBLISHED
 createdAt: 2023-03-10T20:44:01.459Z
-updatedAt: 2023-03-10T20:44:02.006Z
-publishedAt: 2023-03-10T20:44:02.006Z
+updatedAt: 2024-07-01T18:48:57.278Z
+publishedAt: 2024-07-01T18:48:57.278Z
 firstPublishedAt: 2023-03-10T20:44:02.006Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: la-api-del-catalogo-stockkeepingunit-permite-valores-de-condicion-comercial-no-validos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 769053
 ---
 
diff --git a/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 38d73ef7c..8c89cc253 100644
--- a/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -3,7 +3,7 @@ title: 'StockKeepingUnitByEAN returns 404 for EANs with "/"'
 id: Pp3lE5Gu54gOw6liInte4
 status: DRAFT
 createdAt: 2022-02-25T12:23:55.903Z
-updatedAt: 2022-06-28T16:56:27.547Z
+updatedAt: 2024-02-16T20:28:49.215Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: stockkeepingunitbyean-returns-404-for-eans-with-
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 479244
 ---
 
diff --git a/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md b/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
index 7a8713dd3..8913d5461 100644
--- a/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
+++ b/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
@@ -3,8 +3,8 @@ title: 'El método WebService StockKeepingUnitInsertUpdate permite insertar un R
 id: 7wQ9uztQCTIQIWajMd6vaU
 status: PUBLISHED
 createdAt: 2022-01-21T15:19:32.095Z
-updatedAt: 2022-11-25T21:42:03.381Z
-publishedAt: 2022-11-25T21:42:03.381Z
+updatedAt: 2024-02-16T20:29:15.782Z
+publishedAt: 2024-02-16T20:29:15.782Z
 firstPublishedAt: 2022-11-02T13:54:17.227Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-metodo-webservice-stockkeepingunitinsertupdate-permite-insertar-un-refid-existente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 419460
 ---
 
diff --git a/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md b/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md
new file mode 100644
index 000000000..eadcf6990
--- /dev/null
+++ b/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md
@@ -0,0 +1,48 @@
+---
+title: 'Los permisos del escaparate tienen en cuenta a las organizaciones inactivas'
+id: 2GANYaXFMQpLGADajl4CbS
+status: PUBLISHED
+createdAt: 2023-10-27T22:08:14.267Z
+updatedAt: 2023-10-27T22:15:24.802Z
+publishedAt: 2023-10-27T22:15:24.802Z
+firstPublishedAt: 2023-10-27T22:08:14.965Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: los-permisos-del-escaparate-tienen-en-cuenta-a-las-organizaciones-inactivas
+locale: es
+kiStatus: Backlog
+internalReference: 927174
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un usuario tiene asignada más de una organización, y la primera registrada está inactiva, no se reconoce como asignada ninguna organización tras el login.
+
+
+##
+
+## Simulación
+
+
+
+- Crear dos organizaciones y asignar el mismo usuario/email;
+- Inactiva la 1ª organización creada;
+- Inicie sesión en el sitio web.
+
+
+
+## Workaround
+
+
+Eliminar el usuario/email de la organización inactiva.
+
+
+
+
diff --git a/docs/known-issues/es/stucked-not-found-routes-on-platform.md b/docs/known-issues/es/stucked-not-found-routes-on-platform.md
index 3736de140..c214da439 100644
--- a/docs/known-issues/es/stucked-not-found-routes-on-platform.md
+++ b/docs/known-issues/es/stucked-not-found-routes-on-platform.md
@@ -3,8 +3,8 @@ title: 'Rutas atascadas no encontradas en la plataforma'
 id: iAGlRJtK1KMBGxH2tAsrX
 status: PUBLISHED
 createdAt: 2023-04-19T15:54:48.241Z
-updatedAt: 2023-04-19T16:00:28.874Z
-publishedAt: 2023-04-19T16:00:28.874Z
+updatedAt: 2023-06-28T15:56:47.493Z
+publishedAt: 2023-06-28T15:56:47.493Z
 firstPublishedAt: 2023-04-19T15:54:48.788Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -31,8 +31,26 @@ Debido a la falta de notificaciones y problemas de caché, algunas rutas son cac
 ## Simulación
 
 
+Este es un problema intermitente, por lo que, básicamente, no es fácil de simular, pero una vez que se almacenan rutas en vbase y/o rewriter como no encontradas, existe la posibilidad de no recibir una notificación en poco tiempo para actualizar eso
+
+
+
 
 ## Workaround
 
 
+Para los productos,
+
+- Intenta no almacenar rutas dentro del rewriter, a menos que sea estrictamente necesario
+- Restablecer o eliminar rutas en vbase entrando en la aplicación rewriter - admin/apps/vtex.rewriter@x.x.x/setup/ - y actualizando su versión de rutas a una nueva
+- Reindexar las rutas usando store-indexer
+- Guardar el producto para notificar al emisor que el producto ha cambiado y que debe enviar nuevas notificaciones
+Para otras rutas
+
+- Compruebe si la ruta se almacena en rewriter como no encontrada si se actualiza para nuevos valores
+- Comprueba si la API de tipo de página está atascada en un no encontrado y notifica al equipo de catálogo: `https://.vtexcommercestable.com.br/api/catalog_system/pub/portal/pagetype/`
+
+
+
+
 
diff --git a/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md b/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md
index f6a329bbf..67676fa2c 100644
--- a/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md
+++ b/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md
@@ -3,8 +3,8 @@ title: 'El informe de suscriptores no muestra correctamente las suscripciones ac
 id: 4sqvm1v4CbCJLQ3HBBVTmp
 status: PUBLISHED
 createdAt: 2022-05-27T19:44:57.301Z
-updatedAt: 2022-11-25T22:02:30.682Z
-publishedAt: 2022-11-25T22:02:30.682Z
+updatedAt: 2024-07-01T18:48:23.947Z
+publishedAt: 2024-07-01T18:48:23.947Z
 firstPublishedAt: 2022-05-27T19:44:57.688Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: el-informe-de-suscriptores-no-muestra-correctamente-las-suscripciones-activas
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 587556
 ---
 
diff --git a/docs/known-issues/es/subscription-event-history-out-of-order.md b/docs/known-issues/es/subscription-event-history-out-of-order.md
new file mode 100644
index 000000000..b7b620af0
--- /dev/null
+++ b/docs/known-issues/es/subscription-event-history-out-of-order.md
@@ -0,0 +1,51 @@
+---
+title: 'Historial de eventos de suscripción desordenado'
+id: 5w78uE60pzjfOagGnRA2d5
+status: PUBLISHED
+createdAt: 2023-08-01T18:53:21.754Z
+updatedAt: 2023-08-01T18:53:22.303Z
+publishedAt: 2023-08-01T18:53:22.303Z
+firstPublishedAt: 2023-08-01T18:53:22.303Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: historial-de-eventos-de-suscripcion-desordenado
+locale: es
+kiStatus: Backlog
+internalReference: 872697
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, el Historial de suscripciones en el área Mi suscripción , no muestra los eventos en un orden predefinido, por lo que puede mostrar los eventos en orden no cronológico;
+
+
+##
+
+## Simulación
+
+
+Utilizando una suscripción que ha tenido más de un pedido generado;
+
+1- Accede al área de histórico;
+2- La lista de eventos mostrada no estará en orden cronológico;
+
+NOTA: En algunos casos, el escenario puede pasar desapercibido porque sólo unos pocos eventos están fuera de orden cronológico.
+
+
+
+## Workaround
+
+
+
+actualmente no hay solución para este comportamiento
+
+
+
+
diff --git a/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md b/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md
index ee81a116f..ad8ec044b 100644
--- a/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md
+++ b/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md
@@ -3,8 +3,8 @@ title: 'Cuadro de mandos de las suscripciones con información contradictoria'
 id: WvoqrD7xvaAJ6NVOLpU1G
 status: PUBLISHED
 createdAt: 2022-05-27T20:01:11.189Z
-updatedAt: 2022-11-25T22:02:26.699Z
-publishedAt: 2022-11-25T22:02:26.699Z
+updatedAt: 2024-02-16T20:28:30.718Z
+publishedAt: 2024-02-16T20:28:30.718Z
 firstPublishedAt: 2022-05-27T20:01:11.715Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: cuadro-de-mandos-de-las-suscripciones-con-informacion-contradictoria
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 587579
 ---
 
diff --git a/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md b/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
new file mode 100644
index 000000000..56b3764e2
--- /dev/null
+++ b/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
@@ -0,0 +1,47 @@
+---
+title: 'Suscripciones no ejecutadas por fallo en la indexación de datos o en la consulta de datos maestros'
+id: 1PspxNexEEz4GvJ5BpZZgH
+status: PUBLISHED
+createdAt: 2024-01-04T20:27:03.576Z
+updatedAt: 2024-07-09T17:24:39.295Z
+publishedAt: 2024-07-09T17:24:39.295Z
+firstPublishedAt: 2024-01-04T20:27:04.193Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: suscripciones-no-ejecutadas-por-fallo-en-la-indexacion-de-datos-o-en-la-consulta-de-datos-maestros
+locale: es
+kiStatus: Backlog
+internalReference: 961526
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La creación de solicitudes de suscripción depende del retorno de una consulta realizada a la base de datos de suscripciones, esta consulta se realiza periódicamente para identificar qué suscripciones deben ejecutarse en ese periodo, si esta consulta falla o no devuelve una suscripción en particular, su ciclo no se ejecuta, y no se registra ningún error, resultando así una suscripción con la próximaFechaDeCompra en el pasado.
+
+
+
+## Simulación
+
+
+No tenemos forma de simular este escenario debido a la dependencia de otros sistemas.
+
+
+
+## Workaround
+
+
+Para ajustar la `NextPurchaseDate`, el usuario final puede pausar la suscripción y reactivarla. Esta acción hará que el sistema de suscripción recalcule la fecha de ejecución y la `nextPurchaseDate` se actualizará correctamente.
+
+O el cliente puede actualizar la `nextPurchaseDate` de la suscripción del usuario a una fecha futura a través de la API.
+
+
+
+
+
diff --git a/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md b/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
new file mode 100644
index 000000000..ae60ef5f8
--- /dev/null
+++ b/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
@@ -0,0 +1,48 @@
+---
+title: 'La simulación de suscripciones devuelve un error cuando PickupPointID contiene caracteres especiales'
+id: aM2So6TmVffZ1ywtQsknS
+status: PUBLISHED
+createdAt: 2023-09-19T17:31:47.442Z
+updatedAt: 2024-07-01T18:49:12.303Z
+publishedAt: 2024-07-01T18:49:12.303Z
+firstPublishedAt: 2023-09-19T17:31:48.217Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: la-simulacion-de-suscripciones-devuelve-un-error-cuando-pickuppointid-contiene-caracteres-especiales
+locale: es
+kiStatus: No Fix
+internalReference: 903332
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Para realizar un pedido de suscripción o actualizar una suscripción, el sistema de suscripción realiza una simulación, y en esta simulación utiliza los datos de entrega devueltos por el sistema logístico, y si dentro de estos datos hay un punto de recogida cuyo ID está subrayado, el sistema de suscripción no podrá elegir correctamente el ANS, generando así el error "AddressProvider inválido:...." en la simulación y en consecuencia no generará el pedido.
+
+
+##
+
+## Simulación
+
+
+1- Crear un punto de recogida cuyo ID tenga un subrayado
+2- Realice una solicitud de suscripción eligiendo el punto de picking creado en el paso 1.
+3- Espera a que se ejecute el primer ciclo y comprueba que no se ejecuta y que el panel de suscripción registra un error diciendo que la dirección no es válida.
+
+
+
+## Workaround
+
+
+Elimina el punto de recogida cuyo ID aparece subrayado y crea uno nuevo y actualiza la suscripción para que utilice este nuevo punto de recogida.
+
+
+
+
+
diff --git a/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md b/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md
index 2de8094e2..94c66ae3a 100644
--- a/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md
+++ b/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md
@@ -3,8 +3,8 @@ title: 'Sustituir palabras con menos de 3 caracteres no funciona'
 id: 5sAdcBkmVVnRoQD3WUBNJ0
 status: PUBLISHED
 createdAt: 2022-06-08T20:03:47.576Z
-updatedAt: 2022-11-25T21:45:35.491Z
-publishedAt: 2022-11-25T21:45:35.491Z
+updatedAt: 2024-07-01T18:47:49.328Z
+publishedAt: 2024-07-01T18:47:49.328Z
 firstPublishedAt: 2022-06-08T20:03:48.005Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: sustituir-palabras-con-menos-de-3-caracteres-no-funciona
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 282500
 ---
 
diff --git a/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md b/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
new file mode 100644
index 000000000..a9aa10833
--- /dev/null
+++ b/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
@@ -0,0 +1,50 @@
+---
+title: 'La información resumida se traduce al inglés después de iniciar sesión a través de la actualización de la información de la dirección seleccionada.'
+id: 6g05yZcdGHZqm0zeozUH8f
+status: PUBLISHED
+createdAt: 2024-02-07T14:58:10.527Z
+updatedAt: 2024-02-07T14:58:11.389Z
+publishedAt: 2024-02-07T14:58:11.389Z
+firstPublishedAt: 2024-02-07T14:58:11.389Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-informacion-resumida-se-traduce-al-ingles-despues-de-iniciar-sesion-a-traves-de-la-actualizacion-de-la-informacion-de-la-direccion-seleccionada
+locale: es
+kiStatus: Backlog
+internalReference: 978571
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En las cuentas españolas, el inicio de sesión en la caja a través de "Actualizar la información de la dirección seleccionada" después de identificarse con un perfil completo hace que algunos textos del resumen se traduzcan al inglés.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir un artículo al carrito e identificarse mediante un email con un perfil completo para que los datos se rellenen automáticamente;
+- Los datos personales y la dirección estarán enmascarados;
+- Vaya al paso Envío y haga clic en "Actualizar la información de la dirección seleccionada";
+- Inicie sesión;
+- Observe que algunos textos del Resumen pasarán a estar en inglés.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md b/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
new file mode 100644
index 000000000..dc3a575e4
--- /dev/null
+++ b/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
@@ -0,0 +1,48 @@
+---
+title: 'Deslizar la imagen del producto después de hacer zoom no revierte el zoom, lo que causa problemas de visualización.'
+id: 41UVOcLabjyv29Buupj1MO
+status: PUBLISHED
+createdAt: 2024-01-29T18:05:22.470Z
+updatedAt: 2024-01-29T18:05:23.035Z
+publishedAt: 2024-01-29T18:05:23.035Z
+firstPublishedAt: 2024-01-29T18:05:23.035Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: deslizar-la-imagen-del-producto-despues-de-hacer-zoom-no-revierte-el-zoom-lo-que-causa-problemas-de-visualizacion
+locale: es
+kiStatus: Backlog
+internalReference: 491180
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utiliza el vtex.store-components product-image, al deslizar una imagen hacia un lado después de hacer clic en ella para el zoom, la primera imagen se mantendrá ampliada, causando problemas de renderización cuando el usuario desliza de nuevo a ella.
+
+
+##
+
+## Simulación
+
+
+En una PDP que utiliza vtex.store-components product-image, accede a la versión móvil de un producto con al menos dos imágenes.
+Haz clic para hacer zoom en la primera imagen, y pasa a la siguiente.
+Haz clic para ampliar la segunda imagen y vuelve a la primera.
+Hacerlo una y otra vez puede causar problemas de visualización en la imagen ampliada.
+Si vuelves a hacer clic en la imagen para alejarla, volverá a la normalidad.
+
+
+
+## Workaround
+
+
+Utiliza flechas para navegar entre las imágenes y reducir la posibilidad de que los usuarios opten por deslizarlas.
+
+Establezca la propiedad "zoomMode": "hover" o "zoomMode": "open-modal". Evita el deslizamiento cuando la imagen está ampliada, pero cambia ligeramente el comportamiento.
+
diff --git a/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md b/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md
new file mode 100644
index 000000000..fa4501df8
--- /dev/null
+++ b/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md
@@ -0,0 +1,45 @@
+---
+title: 'Los sinónimos importan presentar el éxito incluso para las acciones fallidas'
+id: 4EhvPXp1vXBf2596mANlX6
+status: PUBLISHED
+createdAt: 2024-02-19T22:05:46.953Z
+updatedAt: 2024-02-19T22:05:47.817Z
+publishedAt: 2024-02-19T22:05:47.817Z
+firstPublishedAt: 2024-02-19T22:05:47.817Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-sinonimos-importan-presentar-el-exito-incluso-para-las-acciones-fallidas
+locale: es
+kiStatus: Backlog
+internalReference: 984557
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La importación de sinónimos para archivos CSV devolverá un mensaje de éxito incluso para las acciones que fallaron.
+
+
+##
+
+## Simulación
+
+
+Intente importar un archivo CSV no válido, por ejemplo, fuera del formato esperado de tres columnas.
+
+
+
+## Workaround
+
+
+No es necesaria. Tenga en cuenta que los sinónimos importados correctamente deberían aparecer instantáneamente en la lista tras recargar la página.
+
+
+
+
diff --git a/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md b/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md
new file mode 100644
index 000000000..9c14a6360
--- /dev/null
+++ b/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md
@@ -0,0 +1,38 @@
+---
+title: 'Sinónimos no mostrados en la búsqueda explicada'
+id: 6twjWHNHdarFV5pz1aTfeb
+status: PUBLISHED
+createdAt: 2023-03-20T16:57:15.640Z
+updatedAt: 2023-10-18T00:50:47.829Z
+publishedAt: 2023-10-18T00:50:47.829Z
+firstPublishedAt: 2023-03-20T16:57:16.425Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: sinonimos-no-mostrados-en-la-busqueda-explicada
+locale: es
+kiStatus: Backlog
+internalReference: 774307
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Es posible que algunos productos no presenten sus sinónimos en la página de administración de búsqueda explicada. Esto suele ocurrir con los sinónimos unidireccionales.
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md b/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md
index c9119636c..53ad2f577 100644
--- a/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md
+++ b/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md
@@ -3,8 +3,8 @@ title: 'Sistema que considera al vendedor 1 para el límite de vendedores de la
 id: 1bUax0hSCVrnFPZ4g1VWOa
 status: PUBLISHED
 createdAt: 2022-04-20T20:43:57.392Z
-updatedAt: 2022-11-25T21:52:50.788Z
-publishedAt: 2022-11-25T21:52:50.788Z
+updatedAt: 2024-02-16T20:28:37.189Z
+publishedAt: 2024-02-16T20:28:37.189Z
 firstPublishedAt: 2022-04-20T20:43:57.844Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: sistema-que-considera-al-vendedor-1-para-el-limite-de-vendedores-de-la-regla
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 564614
 ---
 
diff --git a/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md b/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md
new file mode 100644
index 000000000..e4e534d3a
--- /dev/null
+++ b/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md
@@ -0,0 +1,49 @@
+---
+title: 'Las etiquetas a veces no aparecen en la vista PLP con formato de lista'
+id: 4CPSP7GjBfUgxFvmnAhK8z
+status: PUBLISHED
+createdAt: 2024-02-15T13:58:42.405Z
+updatedAt: 2024-02-15T13:58:43.494Z
+publishedAt: 2024-02-15T13:58:43.494Z
+firstPublishedAt: 2024-02-15T13:58:43.494Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: las-etiquetas-a-veces-no-aparecen-en-la-vista-plp-con-formato-de-lista
+locale: es
+kiStatus: No Fix
+internalReference: 982200
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al visualizar el PLP en vista de lista, las etiquetas de los elementos.
+
+
+##
+
+## Simulación
+
+
+Cree etiquetas para sus artículos y modifique las configuraciones necesarias.
+Habilite su PLP para ser visualizado tanto en estilo rejilla como en estilo lista.
+En el estilo de cuadrícula, las etiquetas aparecerán como deberían.
+En el estilo lista, las etiquetas no aparecerán.
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
diff --git a/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md b/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
new file mode 100644
index 000000000..91559e07b
--- /dev/null
+++ b/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
@@ -0,0 +1,51 @@
+---
+title: 'Tax Form UI is not displayng Marketing Tags DropDown'
+id: Xqg6yYfOvVtP0TwZ2RIAk
+status: PUBLISHED
+createdAt: 2024-07-01T13:33:50.657Z
+updatedAt: 2024-07-01T13:34:05.936Z
+publishedAt: 2024-07-01T13:34:05.936Z
+firstPublishedAt: 2024-07-01T13:33:51.430Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: tax-form-ui-is-not-displayng-marketing-tags-dropdown
+locale: es
+kiStatus: Backlog
+internalReference: 1058148
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al guardar impuestos en el módulo de promociones, el valor desplegable para "al menos uno de los siguientes" o "todos los siguientes" no se muestra después de guardar el impuesto. En consecuencia, el usuario no puede averiguar cuál de ellos se está utilizando.
+
+
+##
+
+## Simulación
+
+
+1 - En el módulo de promociones, abra el formulario de impuestos.
+2 - Rellene el formulario de etiquetas de marketing con varios valores.
+3 - Guarde el formulario
+4 - Compruébelo de nuevo, el formulario saldrá vacío:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/kGbgj8MON0fVzgmv19hKS1F9u/?name=image.png)
+
+
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md b/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
new file mode 100644
index 000000000..38e2b5357
--- /dev/null
+++ b/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
@@ -0,0 +1,47 @@
+---
+title: 'La solicitud del centro de impuestos no suma los descuentos cuando se aplica el precio manual'
+id: 3p8mpZALGS95pB9j4CclHi
+status: PUBLISHED
+createdAt: 2023-11-08T18:07:23.968Z
+updatedAt: 2024-07-01T18:49:18.565Z
+publishedAt: 2024-07-01T18:49:18.565Z
+firstPublishedAt: 2023-11-08T18:07:24.393Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-solicitud-del-centro-de-impuestos-no-suma-los-descuentos-cuando-se-aplica-el-precio-manual
+locale: es
+kiStatus: No Fix
+internalReference: 932667
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se aplica un precio manual a un artículo para disminuir el precio, la solicitud del centro de impuestos no lo suma y muestra los totales de descuento siempre como 0.
+
+
+##
+
+## Simulación
+
+
+
+- Establecer un precio manual inferior al precio actual para un artículo;
+- La solicitud del centro de impuestos no sumará el descuento en los totales.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md b/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
new file mode 100644
index 000000000..f19d7c678
--- /dev/null
+++ b/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
@@ -0,0 +1,49 @@
+---
+title: 'Tax Service considera el mismo precio para los artículos que aparecen más de una vez cuando se utiliza la opción de montaje'
+id: 62a1S9SZmGsY58BcV6D58C
+status: PUBLISHED
+createdAt: 2023-09-25T13:27:15.638Z
+updatedAt: 2023-09-27T12:47:49.130Z
+publishedAt: 2023-09-27T12:47:49.130Z
+firstPublishedAt: 2023-09-25T13:27:16.233Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-considera-el-mismo-precio-para-los-articulos-que-aparecen-mas-de-una-vez-cuando-se-utiliza-la-opcion-de-montaje
+locale: es
+kiStatus: Fixed
+internalReference: 906518
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se utilizan Opciones de Montaje, si el artículo se añade de nuevo al carrito, aparecerá dos veces y el Servicio de Impuestos considerará sólo el precio para ese artículo que está primero en el carrito, causando valores de divergencia de impuestos al realizar un pedido.
+
+
+##
+
+## Simulación
+
+
+
+- Configurar Tax Hub en una cuenta;
+- Configurar Opciones de Montaje;
+- Añadir al carrito un artículo incluido en la Opción de Montaje;
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md b/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
new file mode 100644
index 000000000..eb6d1bd4e
--- /dev/null
+++ b/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
@@ -0,0 +1,49 @@
+---
+title: 'Tax Service no aplica promociones de envío gratis con promoción que divide artículos'
+id: 5w7mcNyJhTA77sRULPgrTx
+status: PUBLISHED
+createdAt: 2024-03-06T20:07:56.556Z
+updatedAt: 2024-03-06T20:07:57.240Z
+publishedAt: 2024-03-06T20:07:57.240Z
+firstPublishedAt: 2024-03-06T20:07:57.240Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-no-aplica-promociones-de-envio-gratis-con-promocion-que-divide-articulos
+locale: es
+kiStatus: Backlog
+internalReference: 995527
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar el servicio de impuestos, si hay una promoción que divide artículos, por ejemplo, una promoción Más por menos y una promoción de envío gratuito, el envío gratuito no se aplica correctamente para todos los artículos en la solicitud del servicio de impuestos, lo que provoca un cálculo erróneo y evita que el pedido se cree con el mensaje "No se ha podido crear el pedido solicitado. Por favor, inténtelo de nuevo".
+
+
+##
+
+## Simulación
+
+
+
+- Configurar el Servicio de Impuestos;
+- Crear una promoción Más por menos;
+- Crear una promoción de envío gratuito;
+- Montar un carrito e intentar realizar el pedido.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md b/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
new file mode 100644
index 000000000..5dea8ac3d
--- /dev/null
+++ b/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
@@ -0,0 +1,48 @@
+---
+title: 'Tax Service no tiene en cuenta las promociones nominales a la hora de hacer pedidos'
+id: 1vCs62opRc2iDw0NmYqlT7
+status: PUBLISHED
+createdAt: 2023-09-14T17:48:37.761Z
+updatedAt: 2023-09-14T17:48:38.630Z
+publishedAt: 2023-09-14T17:48:38.630Z
+firstPublishedAt: 2023-09-14T17:48:38.630Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: tax-service-no-tiene-en-cuenta-las-promociones-nominales-a-la-hora-de-hacer-pedidos
+locale: es
+kiStatus: Backlog
+internalReference: 900120
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar el servicio de impuestos, si hay una promoción nominal aplicada en el carrito y se produce una división de artículos, la solicitud de pago no tiene la promoción nominal aplicada, no permitiendo finalizar la compra, y se mostrará el mensaje "No se ha podido crear el pedido solicitado. Por favor, inténtelo de nuevo".
+
+
+##
+
+## Simulación
+
+
+
+- Cree una promoción nominal;
+- Añada artículos al carrito, asegúrese de que los artículos se dividen;
+- Intente finalizar la compra.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md b/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
new file mode 100644
index 000000000..f6f8cdf56
--- /dev/null
+++ b/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
@@ -0,0 +1,47 @@
+---
+title: 'La solicitud de servicio de impuestos utiliza shippingData.address incluso cuando un carro tiene dos direcciones seleccionadas'
+id: 21t5R3AmcllYam4mXqX6lY
+status: PUBLISHED
+createdAt: 2024-08-01T13:11:10.623Z
+updatedAt: 2024-08-01T13:11:11.796Z
+publishedAt: 2024-08-01T13:11:11.796Z
+firstPublishedAt: 2024-08-01T13:11:11.796Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-solicitud-de-servicio-de-impuestos-utiliza-shippingdataaddress-incluso-cuando-un-carro-tiene-dos-direcciones-seleccionadas
+locale: es
+kiStatus: Backlog
+internalReference: 1074168
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En un carrito con artículos para recogida y entrega, la simulación de checkout sólo considera la información del objeto shippingData.address para la solicitud del servicio de impuestos. Por ejemplo, considerando que esas direcciones son de diferentes estados, y el proveedor de impuestos considera diferentes impuestos para cada estado, a uno de los artículos se le aplicará el impuesto incorrecto.
+
+
+##
+
+## Simulación
+
+
+
+- Configurar Servicio de Impuestos;
+- Añadir dos artículos a un carrito con diferentes direcciones seleccionadas: una para recogida y otra para entrega.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md b/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md
index ce1edfb01..f0556f128 100644
--- a/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md
+++ b/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md
@@ -3,8 +3,8 @@ title: 'El servicio fiscal utiliza los datos del documento en lugar del correo e
 id: IOu1ZV40Q5yHjgbcS9C15
 status: PUBLISHED
 createdAt: 2022-03-23T17:50:15.754Z
-updatedAt: 2022-11-25T21:53:38.397Z
-publishedAt: 2022-11-25T21:53:38.397Z
+updatedAt: 2024-02-16T20:28:42.991Z
+publishedAt: 2024-02-16T20:28:42.991Z
 firstPublishedAt: 2022-03-23T17:50:16.302Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: el-servicio-fiscal-utiliza-los-datos-del-documento-en-lugar-del-correo-electronico-del-cliente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 548671
 ---
 
diff --git a/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
new file mode 100644
index 000000000..30fab17bc
--- /dev/null
+++ b/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -0,0 +1,53 @@
+---
+title: 'La búsqueda de televentas no acepta caracteres especiales aparte de "@".'
+id: 5eTb6KlR07dOP06BGhovoL
+status: PUBLISHED
+createdAt: 2024-07-29T17:21:34.828Z
+updatedAt: 2024-07-29T17:21:35.918Z
+publishedAt: 2024-07-29T17:21:35.918Z
+firstPublishedAt: 2024-07-29T17:21:35.918Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: la-busqueda-de-televentas-no-acepta-caracteres-especiales-aparte-de
+locale: es
+kiStatus: Backlog
+internalReference: 1072418
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Actualmente, al utilizar el buscador de televentas, un usuario puede suplantar la identidad de compradores para ayudar en las compras y, para ello, es necesario introducir, en el buscador nativo, el email de quien se va a suplantar.
+
+Sin embargo, al utilizar esta herramienta, los emails que contengan caracteres especiales, como "+", "$", "#", etc... no son identificados por la herramienta de búsqueda, haciendo que devuelva una respuesta de "no encontrado".
+
+
+##
+
+## Simulación
+
+
+1 - en una tienda que tenga implementada la televenta (https://help.vtex.com/en/tutorial/telesales-features--UqhiccIRIK2KD0OqkzJaS), acceder a través de un usuario con la autenticación requerida.
+
+2 - crear un correo electrónico, en el masterdata de la tienda, que utiliza un carácter especial como "+".
+
+3 - intente utilizar la barra de herramientas de suplantación de televentas para buscar el correo electrónico dado - devolverá una respuesta "no encontrado".
+
+4 - ajustar este mismo correo electrónico para eliminar el carácter especial y luego buscar de nuevo normalizará la situación.
+
+
+
+## Workaround
+
+
+Adapte las direcciones de correo electrónico de los usuarios para que no utilicen caracteres especiales.
+
+
+
+
diff --git a/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md b/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..4484b06ca
--- /dev/null
+++ b/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
@@ -0,0 +1,53 @@
+---
+title: 'El texto del botón Añadir al carro no se traduce con el editor del sitio.'
+id: 7rA62h80a1LpDWjgd3SImp
+status: PUBLISHED
+createdAt: 2024-05-02T17:33:41.019Z
+updatedAt: 2024-07-03T18:28:56.642Z
+publishedAt: 2024-07-03T18:28:56.642Z
+firstPublishedAt: 2024-05-02T17:33:42.188Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-texto-del-boton-anadir-al-carro-no-se-traduce-con-el-editor-del-sitio
+locale: es
+kiStatus: Backlog
+internalReference: 1026103
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar traducir un texto utilizando el editor del sitio para el botón Añadir al carro, los cambios no se aplicarán en el frente de la tienda.
+
+
+##
+
+## Simulación
+
+
+
+1. Abrir el editor del sitio
+2. Seleccione el botón Añadir a la cesta
+3. Cambie la etiqueta de texto del botón por la que desee
+4. Guardar cambios
+5. Visualice la página y el texto será el mismo independientemente de la configuración regional seleccionada.
+
+
+
+## Workaround
+
+
+Asegúrese de que iconLabel está vacío tanto en el código de la tienda como en el editor del sitio.
+Si no está seguro de si está vacío en el editor del sitio, puede restablecer el contenido pasando por la versión del editor del sitio > restablecer.
+
+Siga la documentación aquí y los contextos aquí para establecer la etiqueta como desee en su lugar.
+
+
+
+
diff --git a/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md b/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..5f187adc0
--- /dev/null
+++ b/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md
@@ -0,0 +1,55 @@
+---
+title: 'El texto de la InfoCard no se traduce con el editor del sitio.'
+id: 5HYTZvxkPoTZltMkZcVfVO
+status: PUBLISHED
+createdAt: 2024-06-13T18:47:41.470Z
+updatedAt: 2024-07-03T13:58:33.037Z
+publishedAt: 2024-07-03T13:58:33.037Z
+firstPublishedAt: 2024-06-13T18:47:42.396Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-texto-de-la-infocard-no-se-traduce-con-el-editor-del-sitio
+locale: es
+kiStatus: Backlog
+internalReference: 1049491
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar traducir un texto utilizando el editor del sitio para el componente de la tarjeta de información, los cambios no se aplicarán en el frente de la tienda.
+
+
+##
+
+## Simulación
+
+
+
+1. Abrir el editor del sitio
+2. Seleccione el componente tarjeta de información
+3. Cambiar la etiqueta de texto
+4. 4. Guardar los cambios
+5. Visualice la página y el texto será el mismo independientemente de la configuración regional seleccionada.
+
+
+
+## Workaround
+
+
+Asegúrese de que el encabezado está vacío tanto en el código de la tienda como en el editor del sitio.
+Si no está seguro de que esté vacío en el editor del sitio, puede restablecer el contenido pasando por la versión del editor del sitio > restablecer.
+
+Siga la documentación aquí y los contextos aquí para establecer la etiqueta como desee en su lugar.
+
+Si esto todavía no resuelve usted puede un texto enriquecido y un componente de imagen por separado dentro de la tarjeta de información.
+
+
+
+
diff --git a/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md b/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..5aec72f7b
--- /dev/null
+++ b/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md
@@ -0,0 +1,56 @@
+---
+title: 'El texto de inicio de sesión en la tienda no se traduce con el editor del sitio.'
+id: 6DptiKTxtOcYIJEgJlZCmo
+status: PUBLISHED
+createdAt: 2023-11-08T13:33:41.296Z
+updatedAt: 2024-07-03T18:29:45.491Z
+publishedAt: 2024-07-03T18:29:45.491Z
+firstPublishedAt: 2023-11-08T13:33:41.967Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-texto-de-inicio-de-sesion-en-la-tienda-no-se-traduce-con-el-editor-del-sitio
+locale: es
+kiStatus: Backlog
+internalReference: 911757
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al tratar de traducir un texto utilizando el editor de sitio para el inicio de sesión de la tienda, los cambios no se aplicarán en el frente de la tienda.
+
+
+##
+
+## Simulación
+
+
+
+1. Abrir el editor del sitio
+2. Seleccione el bloque Store Login
+3. Cambia la etiqueta de texto del inicio de sesión por la que desees
+4. Guardar cambios
+5. Visualice la página y el texto será el mismo independientemente de la configuración regional seleccionada.
+
+
+
+
+## Workaround
+
+
+Asegúrese de que iconLabel está vacío tanto en el código de la tienda como en el editor del sitio.
+Si no está seguro de que esté vacío en el editor del sitio, puede restablecer el contenido pasando por la versión del editor del sitio > restablecer.
+ ![](https://vtexhelp.zendesk.com/attachments/token/PXovY6zVHdqqhxjodbtMqdXAa/?name=image.png)
+
+Siga la documentación aquí y los contextos aquí para establecer la etiqueta como desee en su lugar.
+
+
+
+
+
diff --git a/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index 674a371c7..f83486067 100644
--- a/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -3,8 +3,8 @@ title: 'Enlace de texto creado con " " en Marketplace tras las aprobaciones - Re
 id: 2afynQ9MwaHPMPWyhx80Tp
 status: PUBLISHED
 createdAt: 2023-04-24T19:36:10.185Z
-updatedAt: 2023-05-08T17:47:01.002Z
-publishedAt: 2023-05-08T17:47:01.002Z
+updatedAt: 2023-07-13T15:25:43.450Z
+publishedAt: 2023-07-13T15:25:43.450Z
 firstPublishedAt: 2023-04-24T19:36:10.701Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: enlace-de-texto-creado-con-en-marketplace-tras-las-aprobaciones-reoccurrence
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 795900
 ---
 
@@ -29,15 +29,11 @@ La SKU se devuelve para su aprobación en el módulo de SKUs Recibidas, pero no
 
 
 
-
-
 ##
 
 ## Simulación
 
 
-
-
 1) Suele ocurrir con un error genérico de skus recibidos al intentar aprobar (esto no ocurre en todos los casos).
 
 2) Se creará un producto en el catálogo del marketplace con los textlinks defectuosos.
@@ -48,10 +44,11 @@ La SKU se devuelve para su aprobación en el módulo de SKUs Recibidas, pero no
 
 
 
-
-
 ## Workaround
 
 
 Actualizar manualmente/API los enlaces de texto del producto en este escenario.
 
+
+
+
diff --git a/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md b/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
index 083df6567..44b69a36c 100644
--- a/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
+++ b/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
@@ -1,18 +1,18 @@
 ---
-title: 'El campo Condado de Judet no aparece como guardado al editar la dirección en Rumanía mi cuenta.'
+title: 'El campo Judet county no aparece como guardado al editar la dirección en Romania my account.'
 id: 5aOtbUdNXPzOpuvLnmJtMf
 status: PUBLISHED
 createdAt: 2022-02-24T14:52:37.615Z
-updatedAt: 2022-11-25T22:02:22.409Z
-publishedAt: 2022-11-25T22:02:22.409Z
+updatedAt: 2024-02-16T20:25:19.581Z
+publishedAt: 2024-02-16T20:25:19.581Z
 firstPublishedAt: 2022-05-18T18:46:59.023Z
 contentType: knownIssue
 productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
-slug: el-campo-condado-de-judet-no-aparece-como-guardado-al-editar-la-direccion-en-rumania-mi-cuenta
+slug: el-campo-judet-county-no-aparece-como-guardado-al-editar-la-direccion-en-romania-my-account
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 394658
 ---
 
@@ -23,9 +23,10 @@ internalReference: 394658
 </div>
 
 
-Para las tiendas de Rumanía en la página _**Mi cuenta**_ hay un campo llamado "Judet", condado en inglés, que no aparece como guardado al editar la dirección.
+Para las tiendas de Rumania en la página _**Mi Cuenta**_ hay un campo llamado "Judet", condado en inglés, que no se muestra como guardado al editar la dirección.
 
 
+##
 
 ## Simulación
 
@@ -33,12 +34,17 @@ Para las tiendas de Rumanía en la página _**Mi cuenta**_ hay un campo llamado
 
 - Comprobando la dirección de Mi Cuenta, se puede ver la dirección previamente guardada.
 - Entonces es posible ver que el comportamiento de este campo no es el mismo que el de los otros campos.
-- Haga clic en Editar dirección y la dirección anterior sigue estando en los campos de dirección excepto en Judet.
+- Se pulsa en Editar Dirección y la dirección anterior sigue en los campos de dirección excepto en Judet.
 
 
+##
 
 ## Workaround
 
 
-No hay ninguna solución disponible para eso en la propia Mi Cuenta, pero tal vez utilizando nuestras API de Datos Maestros se puedan actualizar o crear esas direcciones.
+No hay ninguna solución disponible para eso en la propia Mi Cuenta, pero quizás usando nuestras APIs de Datos Maestros se puedan actualizar o crear esas direcciones.
+
+
+
+
 
diff --git a/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md b/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
index f80097a2f..a168c57e6 100644
--- a/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
+++ b/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
@@ -3,8 +3,8 @@ title: 'Las vacaciones no se muestran en la lista después de utilizar la API pa
 id: WqzSTP6oFwk4MbGaO5mIU
 status: PUBLISHED
 createdAt: 2022-05-02T22:26:55.630Z
-updatedAt: 2022-11-25T22:00:07.142Z
-publishedAt: 2022-11-25T22:00:07.142Z
+updatedAt: 2024-02-16T20:28:28.551Z
+publishedAt: 2024-02-16T20:28:28.551Z
 firstPublishedAt: 2022-05-02T22:26:56.888Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: las-vacaciones-no-se-muestran-en-la-lista-despues-de-utilizar-la-api-para-crear-put
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 571040
 ---
 
diff --git a/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md b/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
index 8123ab831..c30e5d650 100644
--- a/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
+++ b/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
@@ -3,8 +3,8 @@ title: 'La solicitud de cuotas en la pasarela a un comerciante distinto del merc
 id: Xo2YO6ZM9Jj0ONZjXrrrJ
 status: PUBLISHED
 createdAt: 2022-03-27T21:08:39.176Z
-updatedAt: 2022-11-25T22:05:55.885Z
-publishedAt: 2022-11-25T22:05:55.885Z
+updatedAt: 2024-02-16T20:29:17.920Z
+publishedAt: 2024-02-16T20:29:17.920Z
 firstPublishedAt: 2022-03-27T21:08:39.738Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: la-solicitud-de-cuotas-en-la-pasarela-a-un-comerciante-distinto-del-mercado-se-realiza-siempre-con-saleschannel-1
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 391197
 ---
 
diff --git a/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md b/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
new file mode 100644
index 000000000..ba7240442
--- /dev/null
+++ b/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
@@ -0,0 +1,42 @@
+---
+title: 'El conector Adyen heredado es incapaz de denegar de forma asíncrona la captura de pagos'
+id: 5tdNyMfA5zeNg4sCbPQgUc
+status: PUBLISHED
+createdAt: 2024-02-02T15:15:57.980Z
+updatedAt: 2024-02-02T15:15:58.839Z
+publishedAt: 2024-02-02T15:15:58.839Z
+firstPublishedAt: 2024-02-02T15:15:58.839Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-conector-adyen-heredado-es-incapaz-de-denegar-de-forma-asincrona-la-captura-de-pagos
+locale: es
+kiStatus: Backlog
+internalReference: 976005
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Depende de la respuesta de captura de Adyen; por lo tanto, es necesario capturar un pago para recibir una notificación de captura fallida.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
new file mode 100644
index 000000000..7dbe4b2fc
--- /dev/null
+++ b/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
@@ -0,0 +1,53 @@
+---
+title: 'La integración de MercadoPagoV1 y V2 no funciona con la función de guardar tarjeta'
+id: 2V8kdA60OTl7VQoUUNgBci
+status: PUBLISHED
+createdAt: 2022-05-03T15:45:09.856Z
+updatedAt: 2024-01-09T13:23:20.203Z
+publishedAt: 2024-01-09T13:23:20.203Z
+firstPublishedAt: 2022-05-03T15:45:10.554Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: la-integracion-de-mercadopagov1-y-v2-no-funciona-con-la-funcion-de-guardar-tarjeta
+locale: es
+kiStatus: Backlog
+internalReference: 283727
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La integración de MercadoPagoV1 y MercadoPagoV2 no funciona correctamente con la funcionalidad de guardar tarjeta en la sección "Mi Cuenta" para países que no permiten transacciones con decimales.
+
+Este problema surge porque la función "Mis tarjetas" genera una nueva transacción con un valor de 1,5 $. Sin embargo, algunos países no permiten transacciones con tales importes decimales, lo que provoca el rechazo de cualquier intento de aprobar estas transacciones.
+
+
+
+## Simulación
+
+
+
+1. 1. Vaya a VTEX **Admin.**
+2. Configurar el adquirente MercadoPagoV1 o MercadoPagoV2.
+3. Configura un método de pago con tarjeta de crédito -como Mastercard, Visa, American Express, etc.- para que sea procesado por la entidad adquirente.
+4. Vaya a la página de inicio de su tienda.
+5. Inicie sesión introduciendo su dirección de correo electrónico y contraseña.
+6. Haz clic en **Mi cuenta**.
+7. Vaya a la sección **Tarjetas de crédito**.
+8. Haga clic en **Añadir nueva tarjeta**.
+9. Rellena todos los campos y pulsa en **Guardar nueva tarjeta**.
+10. Este proceso devolverá _se ha producido un error al intentar registrar la tarjeta_.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md b/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
new file mode 100644
index 000000000..8fd6d5019
--- /dev/null
+++ b/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
@@ -0,0 +1,54 @@
+---
+title: 'El conector PayU no puede procesar pagos cuando hay datos de envío que contienen más de 40 caracteres.'
+id: 1SEaraqWshBYzjOcL9LxsN
+status: PUBLISHED
+createdAt: 2023-09-18T21:02:32.217Z
+updatedAt: 2023-09-18T21:02:32.812Z
+publishedAt: 2023-09-18T21:02:32.812Z
+firstPublishedAt: 2023-09-18T21:02:32.812Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: el-conector-payu-no-puede-procesar-pagos-cuando-hay-datos-de-envio-que-contienen-mas-de-40-caracteres
+locale: es
+kiStatus: Backlog
+internalReference: 902539
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El conector de PayU no maneja los datos de dirección recibidos de la caja y los envía al proveedor tal cual, sin ninguna modificación. Sin embargo, en la documentación del proveedor se indica que dichos datos no deben superar los 40 caracteres.
+
+Esto provoca que la transacción se cancele por un error de autorización de pago con el mensaje:
+
+    mensaje: El tamaño debe estar entre 0 y 40 propiedad: , mensaje: El tamaño debe estar entre 0 y 40
+
+
+
+##
+
+## Simulación
+
+
+
+- Durante el paso de envío en la caja, seleccione una dirección de entrega con más de 40 caracteres, como 'Región Del Libertador General Bernardo O'Higgins (VI)' en Chile.
+- Seleccione un método de pago procesado a través del conector PayU.
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md b/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
index 655d416ee..4e04c0430 100644
--- a/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
+++ b/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
@@ -3,8 +3,8 @@ title: 'El botón de compra se mantiene activo incluso con un crédito insuficie
 id: 76oPdoBKDn3PSn2KhomgQc
 status: PUBLISHED
 createdAt: 2022-03-27T14:14:51.967Z
-updatedAt: 2022-11-25T22:06:26.792Z
-publishedAt: 2022-11-25T22:06:26.792Z
+updatedAt: 2024-02-16T20:29:57.111Z
+publishedAt: 2024-02-16T20:29:57.111Z
 firstPublishedAt: 2022-03-27T14:14:52.312Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: el-boton-de-compra-se-mantiene-activo-incluso-con-un-credito-insuficiente-del-metodo-de-pago-credito-del-cliente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 309820
 ---
 
diff --git a/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index f300e9e74..1089145ab 100644
--- a/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -1,10 +1,10 @@
 ---
-title: 'La opción "Guardar nueva tarjeta" no funciona para los proveedores de pago asíncronos'
+title: 'La opción "Guardar nueva tarjeta" no funciona para los proveedores de pago asíncronos.'
 id: 3B4gVSNrSeCc8EBXwk5sAu
 status: PUBLISHED
 createdAt: 2022-03-11T17:54:35.664Z
-updatedAt: 2022-11-25T22:06:23.711Z
-publishedAt: 2022-11-25T22:06:23.711Z
+updatedAt: 2024-04-29T17:58:58.889Z
+publishedAt: 2024-04-29T17:58:58.889Z
 firstPublishedAt: 2022-03-11T17:54:36.273Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: la-opcion-guardar-nueva-tarjeta-no-funciona-para-los-proveedores-de-pago-asincronos
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 308892
 ---
 
@@ -23,26 +23,27 @@ internalReference: 308892
 </div>
 
 
-Cuando el cliente intenta añadir una nueva tarjeta en la sección Mi cuenta de las tiendas cuyas afiliaciones no devuelven una respuesta sincrónica, el sistema devolverá _se ha producido un error al intentar registrar la tarjeta_ y puede generarse un cargo indebido de R$1,50.
+Cuando el cliente intenta añadir una nueva tarjeta en la sección Mi cuenta de las tiendas cuyas afiliaciones no devuelven una respuesta sincrónica, el sistema devolverá _ocurrió un error al intentar registrar la tarjeta_ y se podrá generar un cargo indebido de R$1,50.
 
-Este error se produce porque Mis tarjetas esperan una respuesta sincrónica de los adquirentes de tarjetas de crédito y la mayoría de ellos no devuelve una respuesta inmediata.
+Este error ocurre porque Mis tarjetas esperan una respuesta sincrónica de los adquirentes de tarjetas de crédito y la mayoría de ellos no devuelve una respuesta inmediata.
 
 
+##
 
 ## Simulación
 
 
 
-1. Vaya a la sección VTEX **Admin.**
+1. 1. Vaya a VTEX **Admin.**
 2. Configurar el adquirente Mundi.
 3. Configure un método de pago con tarjeta de crédito -como Mastercard, Visa, American Express, etc.- para que sea procesado por la entidad adquirente.
 4. Vaya a la página de inicio de su tienda.
-5. Inicie sesión introduciendo su dirección de correo electrónico y su contraseña.
-6. Haga clic en **Mi cuenta**.
+5. Inicie sesión introduciendo su dirección de correo electrónico y contraseña.
+6. Haz clic en **Mi cuenta**.
 7. Vaya a la sección **Tarjetas de crédito**.
-8. Pulse en **Añadir nueva tarjeta**.
+8. Haga clic en **Añadir nueva tarjeta**.
 9. Rellena todos los campos y pulsa en **Guardar nueva tarjeta**.
-10. Este proceso devolverá un error y al cliente se le cargará el importe de R$ 1,50, que podrá o no ser devuelto automáticamente posteriormente.
+10. Este proceso devolverá un error y se cargará al cliente el importe de R$ 1,50, que podrá o no ser devuelto automáticamente más tarde.
 
 
 
diff --git a/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md b/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
new file mode 100644
index 000000000..22be6fe3d
--- /dev/null
+++ b/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
@@ -0,0 +1,48 @@
+---
+title: 'La API de desplazamiento devuelve errores 429 y/o 408 cuando se consultan entidades con un gran número de documentos, que suelen superar los millones.'
+id: 1Yx7s4kDAJOzpNCxro7TmW
+status: PUBLISHED
+createdAt: 2024-05-20T15:01:15.646Z
+updatedAt: 2024-05-20T15:01:16.679Z
+publishedAt: 2024-05-20T15:01:16.679Z
+firstPublishedAt: 2024-05-20T15:01:16.679Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: la-api-de-desplazamiento-devuelve-errores-429-yo-408-cuando-se-consultan-entidades-con-un-gran-numero-de-documentos-que-suelen-superar-los-millones
+locale: es
+kiStatus: Backlog
+internalReference: 1035873
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La API de desplazamiento está diseñada para manejar grandes conjuntos de datos permitiendo la recuperación de documentos de forma desplazable. Sin embargo, cuando se consultan entidades con un número significativo de documentos, normalmente millones, los usuarios pueden encontrarse con errores 429 (Demasiadas solicitudes) y/o 408 (Tiempo de espera de la solicitud). Estos errores surgen debido al elevado volumen de datos que se procesan, que puede saturar la API y provocar la limitación de la tasa de solicitudes o tiempos de espera.
+
+
+
+## Simulación
+
+
+
+1. Utilice la API de desplazamiento para consultar una entidad que contenga un gran número de documentos (por ejemplo, millones).
+2. Observa las respuestas de la API.
+3. Observe si la API devuelve errores 429 (Demasiadas solicitudes) y/o 408 (Tiempo de espera de la solicitud) durante el proceso.
+
+
+
+## Workaround
+
+
+Optimice la consulta implementando filtros para reducir la carga de la API dividiendo la solicitud en trozos o lotes más pequeños.
+Al elegir los filtros, es importante prestar atención a si se incluirán todos los documentos para garantizar que el desplazamiento recorra todos los documentos de la entidad.
+
+
+
+
diff --git a/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md b/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
index 096132fa8..18d57c459 100644
--- a/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
+++ b/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
@@ -1,16 +1,16 @@
 ---
-title: 'El sistema no permite la cancelación múltiple con la Tarjeta de Regalo'
+title: 'El sistema no permite la cancelación múltiple con Giftcard'
 id: 2htvtVV2158piX4lTYhAvE
 status: PUBLISHED
 createdAt: 2022-03-27T12:54:40.811Z
-updatedAt: 2022-11-25T22:05:17.362Z
-publishedAt: 2022-11-25T22:05:17.362Z
+updatedAt: 2024-06-25T13:51:28.086Z
+publishedAt: 2024-06-25T13:51:28.086Z
 firstPublishedAt: 2022-03-27T12:54:41.420Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: el-sistema-no-permite-la-cancelacion-multiple-con-la-tarjeta-de-regalo
+slug: el-sistema-no-permite-la-cancelacion-multiple-con-giftcard
 locale: es
 kiStatus: Backlog
 internalReference: 309117
@@ -23,21 +23,24 @@ internalReference: 309117
 </div>
 
 
-El sistema no envía la cancelación parcial de una transacción de Tarjeta de Regalo.
-
-También encontramos un escenario en el que ocurre lo mismo, sin embargo la cancelación funciona. Esto deja el importe del reembolso más alto que el importe de la transacción porque el valor reembolsado es el primer reembolso parcial + el segundo reembolso con el importe completo.
+El sistema no está enviando la cancelación parcial de una transacción de Giftcard.
+También hemos encontrado un escenario en el que ocurre lo mismo, sin embargo la cancelación funciona. Esto deja el importe del reembolso más alto que el importe de la transacción porque el valor reembolsado es el primer reembolso parcial + el segundo reembolso con el importe completo.
 
 
 
 ## Simulación
 
 
-Encuentre una transacción en la que se haya solicitado un reembolso/cancelación parcial utilizando la Tarjeta de Regalo.
+Busque una transacción en la que se haya solicitado un reembolso parcial/cancelación utilizando Giftcard.
 
 
 
 ## Workaround
 
 
-No hay ninguna solución, sin embargo, el usuario puede añadir el crédito reembolsable a través de la interfaz de administración.
+No hay solución, pero el usuario puede añadir el crédito reembolsable a través de la interfaz de administración.
+
+
+
+
 
diff --git a/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md b/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
index 362c10e96..98fd99d7e 100644
--- a/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
+++ b/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
@@ -3,8 +3,8 @@ title: 'El sistema no funciona con más de una afiliación de pago de extensión
 id: 3bXtVPHqsrSFpJk9ZfyP4v
 status: PUBLISHED
 createdAt: 2022-03-03T18:45:02.639Z
-updatedAt: 2022-11-25T22:05:27.547Z
-publishedAt: 2022-11-25T22:05:27.547Z
+updatedAt: 2024-02-16T20:25:40.644Z
+publishedAt: 2024-02-16T20:25:40.644Z
 firstPublishedAt: 2022-03-03T18:45:03.463Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: el-sistema-no-funciona-con-mas-de-una-afiliacion-de-pago-de-extension-para-el-metodo-de-debito-en-linea
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 319750
 ---
 
diff --git a/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index ba24c24b8..d17e9619c 100644
--- a/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -3,8 +3,8 @@ title: 'La plantilla "relatorio-de-importacao-de-estoque" no admite el multiling
 id: 5R8b0jnibOQdXupo0hIyts
 status: PUBLISHED
 createdAt: 2022-05-25T18:25:43.394Z
-updatedAt: 2022-11-25T21:59:26.792Z
-publishedAt: 2022-11-25T21:59:26.792Z
+updatedAt: 2024-02-16T20:24:28.851Z
+publishedAt: 2024-02-16T20:24:28.851Z
 firstPublishedAt: 2022-05-25T18:25:43.976Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: la-plantilla-relatoriodeimportacaodeestoque-no-admite-el-multilinguismo
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 585906
 ---
 
diff --git a/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md b/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
index 3150a75dd..d6b0da88f 100644
--- a/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
+++ b/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
@@ -3,8 +3,8 @@ title: 'El usuario no puede realizar una suscripción diaria directamente desde
 id: QJrZvOmlRusACgS2iGRyT
 status: PUBLISHED
 createdAt: 2022-05-18T18:37:18.099Z
-updatedAt: 2022-11-25T22:02:05.580Z
-publishedAt: 2022-11-25T22:02:05.580Z
+updatedAt: 2024-02-16T20:27:15.017Z
+publishedAt: 2024-02-16T20:27:15.017Z
 firstPublishedAt: 2022-05-18T18:37:18.579Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: el-usuario-no-puede-realizar-una-suscripcion-diaria-directamente-desde-el-area-de-mis-suscripciones
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 430650
 ---
 
diff --git a/docs/known-issues/es/time-out-import-and-export-admin.md b/docs/known-issues/es/time-out-import-and-export-admin.md
index a40cf9a6c..da09eedbc 100644
--- a/docs/known-issues/es/time-out-import-and-export-admin.md
+++ b/docs/known-issues/es/time-out-import-and-export-admin.md
@@ -1,16 +1,16 @@
 ---
-title: 'Time Out - Administración de importaciones y exportaciones'
+title: 'Time Out - Importar y Exportar Admin'
 id: 5sPtDgOXtiGcYMvZL7aCf8
 status: PUBLISHED
 createdAt: 2022-03-10T12:36:57.023Z
-updatedAt: 2022-11-25T21:46:35.375Z
-publishedAt: 2022-11-25T21:46:35.375Z
+updatedAt: 2024-01-19T15:24:38.444Z
+publishedAt: 2024-01-19T15:24:38.444Z
 firstPublishedAt: 2022-03-10T12:36:57.461Z
 contentType: knownIssue
 productTeam: Catalog
 author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
-slug: time-out-administracion-de-importaciones-y-exportaciones
+slug: time-out-importar-y-exportar-admin
 locale: es
 kiStatus: Backlog
 internalReference: 424902
@@ -23,15 +23,16 @@ internalReference: 424902
 </div>
 
 
-En algunas cuentas con muchos productos, el administrador de importación y exportación no se carga, generando un tiempo de espera
+Para algunas cuentas con muchos productos, el administrador de importación y exportación no se carga, generando un tiempo de espera
 
 
 
+##
 
 ## Simulación
 
 
-Vaya a `/admin/Site/Relatorio_Skus.aspx `
+Vaya a `/admin/Site/Relatorio_Skus.aspx `.
 
 
 
@@ -39,5 +40,5 @@ Vaya a `/admin/Site/Relatorio_Skus.aspx `
 ## Workaround
 
 
-Recargar la página unas cuantas veces después del error podría cargar el admin.
+Recargar la página varias veces después del error puede cargar el admin.
 
diff --git a/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md b/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md
index 1fe3a0aa6..69c155523 100644
--- a/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md
+++ b/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md
@@ -3,8 +3,8 @@ title: 'Timeout al cambiar las palabras clave de la categoría con muchos produc
 id: 14rC5XqGCOj1THVdYwbudS
 status: PUBLISHED
 createdAt: 2022-02-25T11:40:37.024Z
-updatedAt: 2022-11-25T21:55:02.673Z
-publishedAt: 2022-11-25T21:55:02.673Z
+updatedAt: 2024-02-16T20:26:33.631Z
+publishedAt: 2024-02-16T20:26:33.631Z
 firstPublishedAt: 2022-02-25T11:40:37.550Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: timeout-al-cambiar-las-palabras-clave-de-la-categoria-con-muchos-productos
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 497335
 ---
 
diff --git a/docs/known-issues/es/timeout-generating-internal-application-keys.md b/docs/known-issues/es/timeout-generating-internal-application-keys.md
new file mode 100644
index 000000000..7cf21660e
--- /dev/null
+++ b/docs/known-issues/es/timeout-generating-internal-application-keys.md
@@ -0,0 +1,49 @@
+---
+title: 'Tiempo de espera Generación de claves internas de la aplicación'
+id: 11U62yvD8i6Mp79rUC38FU
+status: PUBLISHED
+createdAt: 2024-05-08T11:28:41.002Z
+updatedAt: 2024-05-09T12:04:05.533Z
+publishedAt: 2024-05-09T12:04:05.533Z
+firstPublishedAt: 2024-05-08T11:28:41.857Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: tiempo-de-espera-generacion-de-claves-internas-de-la-aplicacion
+locale: es
+kiStatus: Fixed
+internalReference: 1029425
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Actualmente tenemos un problema que puede afectar a algunos clientes al generar claves de Aplicaciones.
+
+
+##
+
+## Simulación
+
+
+
+Cuando el cliente utiliza su propio SMTP para la plantilla del Gestor de Licencias en el centro de mensajes, la interfaz de usuario de la Clave de Aplicación intentará utilizar su SMTP para enviar el correo electrónico, pero si tenemos un tiempo de espera mientras se envía el correo electrónico, la Clave de Aplicación no se generará también.
+
+
+
+## Workaround
+
+
+
+El cliente puede cambiar el SMTP del Gestor de Licencias en el centro de mensajes, para configurar el SMTP de VTEX en lugar de su propio SMTP, evitando el timeout. O puede intentar resolver el problema con su propio SMTP.
+
+
+
+
+
diff --git a/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md b/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
new file mode 100644
index 000000000..ef3b108f8
--- /dev/null
+++ b/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
@@ -0,0 +1,47 @@
+---
+title: 'Tiempo de espera en la consulta a Analytics que impide comprobar el registro de inventario'
+id: 2gQhc3JF0bcm1JeLr0lluO
+status: PUBLISHED
+createdAt: 2024-02-19T20:54:22.012Z
+updatedAt: 2024-07-03T15:26:48.484Z
+publishedAt: 2024-07-03T15:26:48.484Z
+firstPublishedAt: 2024-02-19T20:54:22.861Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: tiempo-de-espera-en-la-consulta-a-analytics-que-impide-comprobar-el-registro-de-inventario
+locale: es
+kiStatus: Fixed
+internalReference: 984482
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El registro de actualización en la interfaz de usuario de inventario a veces devuelve el error: Request failed with status code 500 for some specific SKUs, due to a timeout in the query to Analytics (where the data is stored), and no log for the SKU will be shown in the UI.
+
+Este tiempo de espera puede deberse a un alto volumen de actualizaciones en la SKU, o a cualquier otro factor que haga que esta consulta tarde más del tiempo máximo de 40s;
+
+
+##
+
+## Simulación
+
+
+Debido a que la variable es el tiempo de respuesta de la consulta a Analytics, no es posible replicarla de forma concisa.
+
+
+
+## Workaround
+
+
+No hay ninguna solución disponible.
+
+
+
+
diff --git a/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md b/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md
new file mode 100644
index 000000000..72b30890b
--- /dev/null
+++ b/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md
@@ -0,0 +1,71 @@
+---
+title: 'Elemento de reserva total con valor negativo en la interfaz de usuario del inventario'
+id: 5W8BeBZjSgN30YXwXfT8kV
+status: PUBLISHED
+createdAt: 2024-02-29T22:05:19.854Z
+updatedAt: 2024-03-01T13:46:07.440Z
+publishedAt: 2024-03-01T13:46:07.440Z
+firstPublishedAt: 2024-02-29T22:05:20.674Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: elemento-de-reserva-total-con-valor-negativo-en-la-interfaz-de-usuario-del-inventario
+locale: es
+kiStatus: Backlog
+internalReference: 991735
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Un escenario específico en el que se realiza más de un pedido con el mismo sku y procedente del mismo almacén, puede dejar el número de reserva negativo en la UI de inventario.
+
+**Escenario específico:**
+pedido A: 4 unidades de la sku X procedentes del almacén 1;
+pedido B: 6 unidades de la sku X del almacén 1;
+
+pedido A: `status=handling`, se acusa recibo de la reserva;
+pedido B: `status=window-to-cancel`, la reserva aún no se ha confirmado;
+
+Después de esto, el comerciante actualiza el inventario considerando las unidades del pedido A como entregadas, si el comerciante cancela el pedido A, y más tarde mueve el pedido B a `status=handling` (reconocer la reserva), esto dejará la interfaz de usuario del inventario con -4 de este sku como reservado.
+
+
+##
+
+##
+
+## Simulación
+
+
+
+1- Actualizar el inventario de la referencia X con 10 unidades del almacén 1;
+2- Crear un pedido A con 4 unidades de sku X del almacén 1;
+3- Crear un pedido B con 6 unidades de sku X del almacén 1;
+4- Mueve el pedido A a `status=handling` (esto reconocerá la reserva);
+5- Actualiza el inventario de la referencia X con 6 unidades del almacén 1 (que es el número que te queda para el pedido B);
+6- Cancelar el pedido A;
+7- Mover el pedido B a `status=handling` (esto reconocerá la reserva);
+8- Compruebe el inventario para sku X en el almacén 1, tendrá -4 unidades reservadas.
+
+
+
+##
+
+
+## Workaround
+
+
+
+No hay ninguna solución disponible.
+
+
+
+
+
+
diff --git a/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
new file mode 100644
index 000000000..799ec8761
--- /dev/null
+++ b/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
@@ -0,0 +1,41 @@
+---
+title: 'Error de cancelación de transacción con el mensaje "Código no localizable".'
+id: 2Y4joZlyDhbNWU9ycw32U3
+status: PUBLISHED
+createdAt: 2024-03-12T16:34:10.113Z
+updatedAt: 2024-03-12T16:34:11.037Z
+publishedAt: 2024-03-12T16:34:11.037Z
+firstPublishedAt: 2024-03-12T16:34:11.037Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: error-de-cancelacion-de-transaccion-con-el-mensaje-codigo-no-localizable
+locale: es
+kiStatus: Backlog
+internalReference: 998435
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+No hemos podido simular este error.
+
+
+
+## Workaround
+
+
+Es posible cancelar los pagos por separado (empezando por el valor más bajo).
+
+
+
+
diff --git a/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md b/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
new file mode 100644
index 000000000..773840e27
--- /dev/null
+++ b/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
@@ -0,0 +1,38 @@
+---
+title: 'Transacción atascada en un estado anterior al que debería estar'
+id: 60oG2yj6wb1MomGh7Bbh9C
+status: PUBLISHED
+createdAt: 2024-05-22T17:58:05.800Z
+updatedAt: 2024-07-25T21:12:34.583Z
+publishedAt: 2024-07-25T21:12:34.583Z
+firstPublishedAt: 2024-05-22T17:58:06.594Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transaccion-atascada-en-un-estado-anterior-al-que-deberia-estar
+locale: es
+kiStatus: Backlog
+internalReference: 1037765
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El caso más común es la transacción atascada en autorizada cuando debería estar aprobada, en este escenario el pedido no puede ser facturado.
+
+
+##
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md b/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
index 6b3186193..33445415a 100644
--- a/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
+++ b/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
@@ -1,10 +1,10 @@
 ---
 title: 'Transaction stuck in canceling when one of the card is denied'
 id: RdKtB6LsKfaukjT9kiqZ4
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-03-03T18:39:59.580Z
-updatedAt: 2022-06-29T11:57:29.612Z
-publishedAt: 2022-06-28T17:06:24.520Z
+updatedAt: 2024-02-16T20:29:06.755Z
+publishedAt: 2024-02-16T20:29:06.755Z
 firstPublishedAt: 2022-03-03T18:39:59.922Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: transaction-stuck-in-canceling-when-one-of-the-card-is-denied
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429082
 ---
 
diff --git a/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md b/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md
new file mode 100644
index 000000000..484e5825c
--- /dev/null
+++ b/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md
@@ -0,0 +1,51 @@
+---
+title: 'Transacción bloqueada en estado aprobado con pago cancelado'
+id: 5SwwnGi26tagIXuTmvToc
+status: PUBLISHED
+createdAt: 2024-06-07T14:21:22.809Z
+updatedAt: 2024-06-12T17:33:43.967Z
+publishedAt: 2024-06-12T17:33:43.967Z
+firstPublishedAt: 2024-06-07T14:21:23.608Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transaccion-bloqueada-en-estado-aprobado-con-pago-cancelado
+locale: es
+kiStatus: Backlog
+internalReference: 1046365
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La transacción estaba atascada en estado aprobado, a pesar de que el pago fue cancelado.
+
+Al intentar liquidarla manualmente, la pasarela devuelve el siguiente error:
+
+    "error": {"code": "1506", "mensaje": "El pago con ID = xxxxx no se ha liquidado porque el valor de liquidación era -x.xx.", "exception": null}.
+
+
+
+##
+
+## Simulación
+
+
+No hay forma de simular este comportamiento.
+
+
+
+## Workaround
+
+
+No hay ninguna solución en este caso.
+
+
+
+
+
diff --git a/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md b/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md
index b59df20f4..c342f52dd 100644
--- a/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md
+++ b/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md
@@ -19,10 +19,10 @@ internalReference:
 ## Sumario
 
 Cuando un ítem es excluído del pedido:
-![item removido](https://images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
+![item removido](//images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
 
 El e-mail transaccional no considera el item removido y presenta los dos ítems en el e-mail:
-![email transacional](https://images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
+![email transacional](//images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
 
 
 
diff --git a/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
new file mode 100644
index 000000000..a6a2b7282
--- /dev/null
+++ b/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -0,0 +1,42 @@
+---
+title: 'Las transacciones con Konduto tardan más de lo previsto en actualizarse'
+id: 5yUSXenLjlEdESoj5VVvoH
+status: PUBLISHED
+createdAt: 2022-03-11T18:56:45.293Z
+updatedAt: 2023-07-10T18:01:59.163Z
+publishedAt: 2023-07-10T18:01:59.163Z
+firstPublishedAt: 2022-03-11T18:56:45.712Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: las-transacciones-con-konduto-tardan-mas-de-lo-previsto-en-actualizarse
+locale: es
+kiStatus: Backlog
+internalReference: 541149
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+No se puede simular, este comportamiento se produce de forma intermitente.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md b/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
index 50d8bf1d8..fd9b15458 100644
--- a/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
+++ b/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
@@ -3,8 +3,8 @@ title: 'Transacciones con el conector TNSPay denegadas por error: Tarjeta no REG
 id: 2jZefzH8LYqPJxkmylmyA0
 status: PUBLISHED
 createdAt: 2022-03-14T13:21:56.187Z
-updatedAt: 2023-04-10T16:10:48.998Z
-publishedAt: 2023-04-10T16:10:48.998Z
+updatedAt: 2024-02-16T20:24:33.195Z
+publishedAt: 2024-02-16T20:24:33.195Z
 firstPublishedAt: 2022-03-14T13:21:56.952Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: transacciones-con-el-conector-tnspay-denegadas-por-error-tarjeta-no-registrada-en-3ds
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 541687
 ---
 
diff --git a/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md b/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
new file mode 100644
index 000000000..408c37f6f
--- /dev/null
+++ b/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
@@ -0,0 +1,50 @@
+---
+title: 'Problemas de traducción al utilizar una subcuenta para implantar tiendas multilingües'
+id: 5FOCZE7pI4npyfo7TjsFaY
+status: PUBLISHED
+createdAt: 2023-06-21T20:36:33.483Z
+updatedAt: 2024-02-29T15:19:42.862Z
+publishedAt: 2024-02-29T15:19:42.862Z
+firstPublishedAt: 2023-06-21T20:36:33.922Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: problemas-de-traduccion-al-utilizar-una-subcuenta-para-implantar-tiendas-multilingues
+locale: es
+kiStatus: Backlog
+internalReference: 848524
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La indexación unificada de catálogos sólo tiene en cuenta las traducciones de los mensajes de la cuenta principal, incluso cuando se utiliza una arquitectura de subcuentas para implementar almacenes transfronterizos.
+
+Esto conduce a una traducción diferente en la página de búsqueda y de producto, ya que el contenido de la página de búsqueda se basa únicamente en las traducciones recuperadas por el Indexador de Catálogo.
+
+
+##
+
+## Simulación
+
+
+
+- Cree una subcuenta e implemente tiendas transfronterizas;
+- Traduzca el contenido del catálogo en la subcuenta;
+- Comparar la página de búsqueda y la de producto; tendrán traducciones diferentes.
+
+
+
+## Workaround
+
+
+Establezca los idiomas adicionales (enlaces y contenido de Mensajes) en la cuenta principal, replicando las traducciones de la subcuenta también en la cuenta principal.
+
+
+
+
diff --git a/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md b/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
new file mode 100644
index 000000000..580408ebb
--- /dev/null
+++ b/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
@@ -0,0 +1,74 @@
+---
+title: 'La transliteración sólo se guarda en vbase y no en rewriter'
+id: 3ngFt1qXOUjmY5L84dk6in
+status: PUBLISHED
+createdAt: 2023-12-12T19:54:12.171Z
+updatedAt: 2024-02-16T20:26:46.444Z
+publishedAt: 2024-02-16T20:26:46.444Z
+firstPublishedAt: 2023-12-12T19:54:13.102Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: la-transliteracion-solo-se-guarda-en-vbase-y-no-en-rewriter
+locale: es
+kiStatus: No Fix
+internalReference: 738334
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al transliterar las urls a través del catalogo rewriter no lo almacena, o no recibe ninguna notificación a través del broadcaster, solo lo almacenamos en vbase
+
+
+##
+
+## Simulación
+
+
+
+Traducir
+
+Comprueba el rewriter con el linkId que creaste en admin/graphql-ide y elige la app rewriter:
+
+
+    { internal{ get(ruta: "tuLinkdIdAquí"){ id } }}
+
+
+
+
+
+## Workaround
+
+
+
+Ejecute la siguiente consulta en la regrabadora
+
+
+    { internal{ get(path: "tuNombreCategoriaTraducidoSlugified"){ id from declarer type query binding origin resolveAs } }}
+
+
+Guarde los valores devueltos, necesitará utilizarlos en el siguiente paso
+
+Ejecute la siguiente mutación cambiando únicamente el parámetro from, los demás deben ser iguales que los anteriores:
+
+
+    mutation saveInternal($ruta: InternalInput!) { internal { save(ruta: $ruta) { from declarer type id binding resolveAs origin } }}{ "ruta": { "from": "yourLinkId", "declarer": "tuDeclaradorGuardado", "tipo": "yourSavedType", "binding": "yourSavedBinding", "id": "yourSavedId", "origin": "yourSavedOrigin", "resolveAs": "TheOriginalNameOfTheCategory" -aquí en cirílico }}
+
+
+
+> Para más información sobre estos parámetros, puede consultar: https://developers.vtex.com/vtex-developer-docs/docs/rewriter
+
+
+Ahora, vamos a borrar la ruta antigua (la guardada con el nombre)
+
+
+    mutation guardarInterna($ruta: ¡EntradaInterna!) { interna { borrar(ruta: "tuNombreCategoriaTraducidoSlugificado") { id } }}
+
+
diff --git a/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md b/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md
index 64a757274..61263bbae 100644
--- a/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md
+++ b/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md
@@ -3,8 +3,8 @@ title: 'La interfaz de usuario no actualiza la mejor opción de SLA en el carro'
 id: 5H05jLUJA0gmSDTO6nMsPE
 status: PUBLISHED
 createdAt: 2022-03-26T02:30:36.692Z
-updatedAt: 2022-11-25T21:54:03.143Z
-publishedAt: 2022-11-25T21:54:03.143Z
+updatedAt: 2024-02-16T20:26:13.531Z
+publishedAt: 2024-02-16T20:26:13.531Z
 firstPublishedAt: 2022-03-26T02:30:37.014Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-interfaz-de-usuario-no-actualiza-la-mejor-opcion-de-sla-en-el-carro
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 550201
 ---
 
diff --git a/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md b/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
new file mode 100644
index 000000000..1d4baa51a
--- /dev/null
+++ b/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
@@ -0,0 +1,51 @@
+---
+title: 'La interfaz de usuario no muestra la selección de la ventana de entrega para los puntos de recogida cuando un artículo de un vendedor está entre artículos para recoger de otro vendedor.'
+id: 5SyIw04UtNiZhmy0ELNLCD
+status: PUBLISHED
+createdAt: 2023-12-15T20:18:48.433Z
+updatedAt: 2023-12-15T20:18:49.218Z
+publishedAt: 2023-12-15T20:18:49.218Z
+firstPublishedAt: 2023-12-15T20:18:49.218Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-no-muestra-la-seleccion-de-la-ventana-de-entrega-para-los-puntos-de-recogida-cuando-un-articulo-de-un-vendedor-esta-entre-articulos-para-recoger-de-otro-vendedor
+locale: es
+kiStatus: Backlog
+internalReference: 954108
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En un carro con al menos tres productos, donde los pedidos de artículos son: El 1º es para recogida programada 1, el 2º para recogida programada 2 (vendedor diferente), y el 3º es para recogida programada 1, la UI no mostrará las ventanas de entrega para seleccionar la fecha/hora de la 2ª recogida. Esto sucede porque la API agrupará el 1er artículo y el 3er artículo ya que es el mismo SLA.
+
+No es posible ir al paso de pago y finalizar la compra.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir un artículo al carrito para recogerlo del vendedor A;
+- Añadir un artículo a la cesta para recoger del vendedor B;
+- Añadir otro artículo a la cesta para recoger del vendedor A;
+- En el paso de envío, las ventanas de entrega de recogida para seleccionar la fecha/hora no se mostrarán.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md b/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
index 6a750af81..9962130ca 100644
--- a/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
+++ b/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
@@ -3,8 +3,8 @@ title: 'La interfaz de usuario no muestra el formulario para editar la direcció
 id: 4rqphb66vAzsAyx9mUmNLu
 status: PUBLISHED
 createdAt: 2023-02-06T13:15:57.816Z
-updatedAt: 2023-02-06T13:15:58.251Z
-publishedAt: 2023-02-06T13:15:58.251Z
+updatedAt: 2023-06-23T17:47:10.184Z
+publishedAt: 2023-06-23T17:47:10.184Z
 firstPublishedAt: 2023-02-06T13:15:58.251Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: la-interfaz-de-usuario-no-muestra-el-formulario-para-editar-la-direccion-cuando-se-selecciona-anadir-primero-una-nueva-direccion
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 747772
 ---
 
@@ -42,7 +42,7 @@ La interfaz de usuario no muestra el formulario correcto para editar la direcci
 ## Workaround
 
 
-Vuelva a cargar la página para poder editar de nuevo la dirección seleccionada.
+Recargue la página para poder editar de nuevo la dirección seleccionada.
 
 
 
diff --git a/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md b/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
new file mode 100644
index 000000000..fb054897a
--- /dev/null
+++ b/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
@@ -0,0 +1,45 @@
+---
+title: 'La interfaz de usuario se congela si se produce un error en el proceso interno del pedido de plaza'
+id: pt5Orot3i9BlYCt4E2Kj5
+status: PUBLISHED
+createdAt: 2023-11-28T18:55:54.950Z
+updatedAt: 2023-11-28T18:55:55.649Z
+publishedAt: 2023-11-28T18:55:55.649Z
+firstPublishedAt: 2023-11-28T18:55:55.649Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-se-congela-si-se-produce-un-error-en-el-proceso-interno-del-pedido-de-plaza
+locale: es
+kiStatus: Backlog
+internalReference: 943771
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se produce un error durante el proceso interno de realizar un pedido, la interfaz de usuario se congela en la carga sin ningún mensaje de error/advertencia.
+
+
+##
+
+## Simulación
+
+
+Este comportamiento se ha observado cuando el Servicio de Impuestos ha agotado el tiempo de espera durante la solicitud de pedido, pero no se limita a esto.
+
+
+
+## Workaround
+
+
+Actualice la página.
+
+
+
+
diff --git a/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md b/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
new file mode 100644
index 000000000..ccbb0b632
--- /dev/null
+++ b/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
@@ -0,0 +1,48 @@
+---
+title: 'La interfaz de usuario muestra que se ha seleccionado una recogida en el carro con suscripciones, pero no en la API.'
+id: 6WUGylIHWZtfeAm7hplYHD
+status: PUBLISHED
+createdAt: 2024-03-08T19:08:16.010Z
+updatedAt: 2024-03-08T19:08:17.012Z
+publishedAt: 2024-03-08T19:08:17.012Z
+firstPublishedAt: 2024-03-08T19:08:17.012Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-muestra-que-se-ha-seleccionado-una-recogida-en-el-carro-con-suscripciones-pero-no-en-la-api
+locale: es
+kiStatus: Backlog
+internalReference: 996976
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Las opciones de recogida se ofrecen a los compradores en un carro con un artículo con una suscripción. Cuando se selecciona una de las opciones de recogida, el proceso de pago cambia automáticamente a entrega, pero la interfaz de usuario sigue mostrando que se ha seleccionado la opción de recogida.
+
+
+
+## Simulación
+
+
+
+- Configurar una suscripción;
+- Añadir el artículo con la suscripción al carrito;
+- En el paso de envío, seleccione "Recoger en tienda";
+- Compruebe el orderForm a través de la API, y se seleccionará la entrega.
+
+
+
+## Workaround
+
+
+Abra un ticket al Soporte de VTEX solicitando habilitar puntos de recogida para pedidos de suscripción.
+
+
+
+
diff --git a/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md b/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
new file mode 100644
index 000000000..2f009440c
--- /dev/null
+++ b/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
@@ -0,0 +1,51 @@
+---
+title: 'La interfaz de usuario muestra puntos de recogida duplicados cuando un artículo para entrega se encuentra entre artículos para recogida.'
+id: lIP6kRDsi23lNQd7RzNfY
+status: PUBLISHED
+createdAt: 2023-09-25T13:50:27.481Z
+updatedAt: 2023-10-18T14:36:11.434Z
+publishedAt: 2023-10-18T14:36:11.434Z
+firstPublishedAt: 2023-09-25T13:50:28.066Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-muestra-puntos-de-recogida-duplicados-cuando-un-articulo-para-entrega-se-encuentra-entre-articulos-para-recogida
+locale: es
+kiStatus: Backlog
+internalReference: 906549
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En un carro con al menos tres productos, donde los pedidos de artículos son: 1º es para recogida, 2º es para entrega y 3º es para recogida, la IU mostrará el punto de recogida duplicado. Esto sucede porque la API agrupará el 1er artículo y el 3er artículo ya que es el mismo SLA.
+
+Es posible ir al paso de pago y finalizar la compra.
+
+
+##
+
+## Simulación
+
+
+
+- Añadir un artículo al carrito para su recogida;
+- Añadir un artículo a la cesta para su entrega;
+- Añadir otro artículo al carro para su recogida;
+- En el paso de envío, la recogida se duplicará
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
new file mode 100644
index 000000000..1441e839a
--- /dev/null
+++ b/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -0,0 +1,48 @@
+---
+title: 'La interfaz de usuario muestra "¡Regalos elegidos!" cuando se utiliza la función de sustitución de pedidos.'
+id: 4efm7L6hQhad98uYkjzrXO
+status: PUBLISHED
+createdAt: 2023-09-27T20:57:46.944Z
+updatedAt: 2023-09-27T20:57:47.516Z
+publishedAt: 2023-09-27T20:57:47.516Z
+firstPublishedAt: 2023-09-27T20:57:47.516Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-muestra-regalos-elegidos-cuando-se-utiliza-la-funcion-de-sustitucion-de-pedidos
+locale: es
+kiStatus: Backlog
+internalReference: 909137
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al utilizar la función de sustitución de pedidos, la interfaz de usuario de la caja muestra "¡Regalos seleccionados!" aunque no haya ninguna promoción de regalos configurada.
+
+
+
+## Simulación
+
+
+
+- Acceda a Mis Pedidos y seleccione un pedido;
+- Haz clic en "Cambiar pedido" y selecciona el motivo "He comprado un número/talla equivocado y quiero cambiarlo";
+- Será redirigido a la caja y en la pantalla aparecerá el mensaje "¡Regalos elegidos!
+
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md b/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
new file mode 100644
index 000000000..86e96f54a
--- /dev/null
+++ b/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
@@ -0,0 +1,54 @@
+---
+title: 'La interfaz de usuario lanza solicitudes separadas para cada clave/campo de un archivo adjunto.'
+id: 5IF3veMFTFi9dERoEokokt
+status: PUBLISHED
+createdAt: 2024-03-01T21:05:37.154Z
+updatedAt: 2024-03-01T21:07:41.105Z
+publishedAt: 2024-03-01T21:07:41.105Z
+firstPublishedAt: 2024-03-01T21:05:37.941Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: la-interfaz-de-usuario-lanza-solicitudes-separadas-para-cada-clavecampo-de-un-archivo-adjunto
+locale: es
+kiStatus: Backlog
+internalReference: 336371
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se establece el valor de un campo de adjunto de artículo a través de la interfaz de usuario, esto desencadena una solicitud para actualizar el orderForm, incluso si todavía hay más campos restantes.
+Esta solicitud será procesada, y la respuesta con el orderForm actualizado.
+
+En los casos en los que el archivo adjunto tenga varios campos de texto abiertos, esto puede provocar que los campos posteriores se sobrescriban mientras se escriben sus valores.
+Esto ocurre porque la solicitud de actualización se habrá enviado cuando este campo aún estaba en blanco, por lo que también estará en blanco en la respuesta.
+
+En los casos en los que el artículo tiene una suscripción adjunta con múltiples claves, puede aparecer un mensaje de error como "unable to communicate with seller" / "não foi possível se comunicar com o vendedor".
+Esto ocurre porque la suscripción esperará que se hayan rellenado múltiples claves, pero la primera solicitud sólo habrá enviado una.
+
+
+##
+
+## Simulación
+
+
+Cree un archivo adjunto con al menos dos claves/campos.
+Añada un artículo vinculado a este archivo adjunto a su cesta y, a continuación, añada el archivo adjunto.
+Por último, establezca el valor de un campo, y observe el comportamiento que sigue.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md b/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md
index 474df49f5..4f4c4a8b0 100644
--- a/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md
+++ b/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md
@@ -3,8 +3,8 @@ title: 'No se pueden cancelar las transacciones que han cambiado la configuraci
 id: 2bhsI5119DLOhNjk2cb6q
 status: PUBLISHED
 createdAt: 2022-06-28T16:44:10.992Z
-updatedAt: 2022-11-25T22:06:55.006Z
-publishedAt: 2022-11-25T22:06:55.006Z
+updatedAt: 2024-02-16T20:24:09.734Z
+publishedAt: 2024-02-16T20:24:09.734Z
 firstPublishedAt: 2022-06-28T16:44:11.460Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: no-se-pueden-cancelar-las-transacciones-que-han-cambiado-la-configuracion-de-la-division-del-pago
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 364382
 ---
 
diff --git a/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md b/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md
new file mode 100644
index 000000000..7847565f2
--- /dev/null
+++ b/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md
@@ -0,0 +1,34 @@
+---
+title: 'No se puede iniciar sesión a través de la aplicación de Google en iOS'
+id: 1YxuqHJbbKnzdv1d6LrfR2
+status: PUBLISHED
+createdAt: 2023-10-26T16:50:11.505Z
+updatedAt: 2024-03-20T20:34:16.469Z
+publishedAt: 2024-03-20T20:34:16.469Z
+firstPublishedAt: 2023-10-26T16:50:12.188Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: no-se-puede-iniciar-sesion-a-traves-de-la-aplicacion-de-google-en-ios
+locale: es
+kiStatus: Backlog
+internalReference: 926239
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md b/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
new file mode 100644
index 000000000..70b3f540a
--- /dev/null
+++ b/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
@@ -0,0 +1,54 @@
+---
+title: 'No se pueden cargar imágenes de hojas de cálculo con servicios de host que utilizan el protocolo de cifrado SSL1.3'
+id: sqoXJSms7bhmdNe0Id111
+status: PUBLISHED
+createdAt: 2023-06-28T12:23:54.884Z
+updatedAt: 2023-06-28T12:25:18.545Z
+publishedAt: 2023-06-28T12:25:18.545Z
+firstPublishedAt: 2023-06-28T12:23:55.364Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: no-se-pueden-cargar-imagenes-de-hojas-de-calculo-con-servicios-de-host-que-utilizan-el-protocolo-de-cifrado-ssl13
+locale: es
+kiStatus: Backlog
+internalReference: 851911
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el host de imágenes de la hoja de cálculo utiliza un protocolo de encriptación SSL1.3, aparece un error al intentar subir la hoja de cálculo:
+
+"Fallo al procesar el registro. Asegúrese de que los datos de la hoja de cálculo son coherentes e inténtelo de nuevo. Detalles del error: Se ha producido un error al enviar la solicitud".
+
+Este error se produce porque nuestro servicio windows sólo permite versiones antiguas como 1.2 o 1.1.
+
+
+
+##
+
+## Simulación
+
+
+
+1. Utiliza un host con una versión de protocolo más reciente;
+2. Intenta subir una imagen, usando hoja de cálculo, que esté alojada allí;
+3. 3. Compruebe que aparece el mensaje de error.
+
+
+
+## Workaround
+
+
+Utilice un host diferente o valide con el host para utilizar una versión anterior.
+
+
+
+
+
diff --git a/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md b/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md
new file mode 100644
index 000000000..565679d7d
--- /dev/null
+++ b/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md
@@ -0,0 +1,46 @@
+---
+title: 'Se siguen devolviendo PDP de productos no disponibles'
+id: 6Q2TOp3UPHuCXDpZceV1Dn
+status: PUBLISHED
+createdAt: 2024-05-31T14:43:14.505Z
+updatedAt: 2024-06-04T12:10:43.840Z
+publishedAt: 2024-06-04T12:10:43.840Z
+firstPublishedAt: 2024-05-31T14:43:15.347Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: se-siguen-devolviendo-pdp-de-productos-no-disponibles
+locale: es
+kiStatus: Backlog
+internalReference: 1041920
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando un producto no está disponible, todavía se puede devolver su PDP.
+
+
+##
+
+## Simulación
+
+
+Intenta acceder a la PDP de un producto que no está disponible en Faststore.
+
+
+
+## Workaround
+
+
+NO DISPONIBLE
+
+
+
+
+
diff --git a/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md b/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
new file mode 100644
index 000000000..569994231
--- /dev/null
+++ b/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
@@ -0,0 +1,46 @@
+---
+title: 'Priorización innecesaria de los resultados de búsqueda por diacríticos en portugués'
+id: 3lbgwHFc9RLusAnZnvnE1H
+status: PUBLISHED
+createdAt: 2024-05-07T15:24:18.404Z
+updatedAt: 2024-05-07T16:55:01.818Z
+publishedAt: 2024-05-07T16:55:01.818Z
+firstPublishedAt: 2024-05-07T15:24:19.224Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: priorizacion-innecesaria-de-los-resultados-de-busqueda-por-diacriticos-en-portugues
+locale: es
+kiStatus: Backlog
+internalReference: 1028763
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La Búsqueda Inteligente prioriza los resultados que tienen una coincidencia exacta, teniendo en cuenta los diacríticos del término buscado y los productos.
+
+En algunos idiomas, pueden generar palabras completamente diferentes, pero para otros, esto no es lo suficientemente importante o puede estar relacionado con errores tipográficos frecuentes.
+
+En portugués, diacríticos como el acento agudo, el acento circunflejo y la tilde entran en este supuesto. Un producto o un término de búsqueda al que le falte el diacrítico dará prioridad a unos productos sobre otros en función de cómo estén registrados. Para esta lengua, se espera la normalización.
+
+
+##
+
+## Simulación
+
+
+En una tienda portuguesa, la búsqueda de "tenis" presentará primero los productos con "tenis" (coincidencia exacta con diacríticos) y sólo después los resultados con "tênis" (coincidencia exacta ignorando los diacríticos).
+
+
+
+## Workaround
+
+
+Se recomienda que el catálogo de productos mantenga siempre la misma escritura para sus productos. Si no es el caso, un sinónimo puede ayudar a mantener los términos equivalentes.
+
diff --git a/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md b/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md
index 0b0246442..146a4af64 100644
--- a/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md
+++ b/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md
@@ -3,8 +3,8 @@ title: 'Solicitudes de simulación innecesarias y componentes que se recargan'
 id: 1qXJU1XC4r0e9KWxNUKp3L
 status: PUBLISHED
 createdAt: 2022-08-30T17:34:47.635Z
-updatedAt: 2022-11-25T21:50:25.658Z
-publishedAt: 2022-11-25T21:50:25.658Z
+updatedAt: 2024-02-16T20:25:15.198Z
+publishedAt: 2024-02-16T20:25:15.198Z
 firstPublishedAt: 2022-08-30T17:34:48.111Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: solicitudes-de-simulacion-innecesarias-y-componentes-que-se-recargan
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 648298
 ---
 
diff --git a/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md b/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md
new file mode 100644
index 000000000..2b6136e2e
--- /dev/null
+++ b/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md
@@ -0,0 +1,51 @@
+---
+title: 'Recarga inesperada al registrar/actualizar un producto'
+id: 4XAYOJG7cgEJG6PqcmOkAY
+status: PUBLISHED
+createdAt: 2023-07-17T19:00:56.863Z
+updatedAt: 2023-10-20T13:42:32.569Z
+publishedAt: 2023-10-20T13:42:32.569Z
+firstPublishedAt: 2023-07-17T19:00:57.611Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: recarga-inesperada-al-registraractualizar-un-producto
+locale: es
+kiStatus: Backlog
+internalReference: 863542
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al registrar o actualizar un formulario de producto, algunos usuarios están reportando que al realizar esta acción varias veces seguidas, en algún momento la página se fuerza y refresca sola.
+
+No hemos podido encontrar un patrón que justifique esto
+
+
+##
+
+## Simulación
+
+
+
+Actualizar/registrar un formulario de producto varias veces seguidas.
+es difícil de simular ya que es totalmente aleatorio
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
new file mode 100644
index 000000000..bce363441
--- /dev/null
+++ b/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
@@ -0,0 +1,56 @@
+---
+title: 'Error "Unhandled exception" al cambiar la edición de la cuenta'
+id: 1NVjCrlRkadscl8fW9rOdA
+status: PUBLISHED
+createdAt: 2023-09-26T12:45:44.999Z
+updatedAt: 2024-02-26T17:22:29.322Z
+publishedAt: 2024-02-26T17:22:29.322Z
+firstPublishedAt: 2023-09-26T12:45:45.927Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: error-unhandled-exception-al-cambiar-la-edicion-de-la-cuenta
+locale: es
+kiStatus: Backlog
+internalReference: 907294
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+A veces cuando cambiamos la edición de una cuenta o espacio de trabajo nos podemos encontrar con el siguiente error:
+
+
+    - error: Unhandled exception - error: Por favor, informe del problema en https://github.com/vtex/toolbelt/issues
+
+
+El error no es consistente, no ocurre todo el tiempo.
+
+Si el maestro de la tienda está utilizando la `edición-negocio` y quieren cambiar la edición a `edición-tienda` en un espacio de trabajo, este error es más probable que suceda.
+
+
+##
+
+## Simulación
+
+
+Intente cambiar la edición de cualquier cuenta de prueba o espacio de trabajo, este error ocurrirá eventualmente en el proceso.
+
+
+
+## Workaround
+
+
+
+- Ejecute el comando `vtex edition get` para asegurarse de que la edición no ha cambiado. A veces la edición cambia incluso cuando aparece el error;
+- Si las aplicaciones no se actualizaron también intente ejecutar el comando `vtex update`;
+- Espera un poco e inténtalo de nuevo;
+- También puede ocurrir que el error de excepción no manejada no aparezca, la edición cambiará pero las aplicaciones no se actualizarán. En este caso simplemente sun `vtex update`.
+
+
+
diff --git a/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md b/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
index 5ebacb505..1cfca1f7f 100644
--- a/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
+++ b/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
@@ -3,8 +3,8 @@ title: 'Mensaje de error no específico al exportar ProdutoExportacaoImportacaoE
 id: 3rtDeX0QppmbXOvuCtC1Lr
 status: PUBLISHED
 createdAt: 2022-03-22T13:09:32.153Z
-updatedAt: 2022-11-25T21:44:55.880Z
-publishedAt: 2022-11-25T21:44:55.880Z
+updatedAt: 2024-02-16T20:29:49.944Z
+publishedAt: 2024-02-16T20:29:49.944Z
 firstPublishedAt: 2022-03-22T13:09:32.886Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: mensaje-de-error-no-especifico-al-exportar-produtoexportacaoimportacaoespecificacaov2aspx
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 314227
 ---
 
diff --git a/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md b/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
new file mode 100644
index 000000000..928aa4b18
--- /dev/null
+++ b/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
@@ -0,0 +1,53 @@
+---
+title: 'Los campos no admitidos por la API de búsqueda inteligente devuelven datos erróneos o vacíos'
+id: Jvm9oLhUM6NqCslpBqSti
+status: PUBLISHED
+createdAt: 2024-05-13T21:03:14.026Z
+updatedAt: 2024-06-25T19:11:41.925Z
+publishedAt: 2024-06-25T19:11:41.925Z
+firstPublishedAt: 2024-05-13T21:03:15.346Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: los-campos-no-admitidos-por-la-api-de-busqueda-inteligente-devuelven-datos-erroneos-o-vacios
+locale: es
+kiStatus: Backlog
+internalReference: 1032531
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La API de búsqueda inteligente se basa principalmente en la API de búsqueda por catálogo heredada por motivos de compatibilidad, pero no todas las propiedades devuelven la misma información. En algunos casos, es diferente o está vacía.
+
+Algunas propiedades afectadas:
+
+- "modalType" (devuelve vacío)
+- "imageText" (devuelve lo mismo que "imageLabel")
+- "kitItems" (devuelve vacío)
+
+
+##
+
+## Simulación
+
+
+
+- registrar el valor de un campo afectado en el módulo Catálogo
+- comparar la respuesta para el campo específico entre las API de búsqueda en el catálogo y de búsqueda inteligente
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md b/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
index 49e07466c..38b4039f6 100644
--- a/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
+++ b/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
@@ -3,8 +3,8 @@ title: 'La actualización del vendedor a través de Admin está devolviendo algu
 id: 2gtqnZmCW59OKoqRpU3UaQ
 status: PUBLISHED
 createdAt: 2022-06-30T12:21:23.852Z
-updatedAt: 2022-11-25T22:00:35.980Z
-publishedAt: 2022-11-25T22:00:35.980Z
+updatedAt: 2024-02-16T20:28:26.435Z
+publishedAt: 2024-02-16T20:28:26.435Z
 firstPublishedAt: 2022-06-30T12:21:24.538Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: la-actualizacion-del-vendedor-a-traves-de-admin-esta-devolviendo-algunos-campos-al-valor-por-defecto-despues-de-cambiarlo-a-traves-de-la-api
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 608120
 ---
 
diff --git a/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md b/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
new file mode 100644
index 000000000..3e2508a32
--- /dev/null
+++ b/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
@@ -0,0 +1,56 @@
+---
+title: 'Actualizar las políticas comerciales disponibles del vendedor no activa la indexación automática'
+id: 45FOjSN4a5ZhCqilQfUX99
+status: PUBLISHED
+createdAt: 2024-05-31T13:49:57.732Z
+updatedAt: 2024-05-31T13:49:58.764Z
+publishedAt: 2024-05-31T13:49:58.764Z
+firstPublishedAt: 2024-05-31T13:49:58.764Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: actualizar-las-politicas-comerciales-disponibles-del-vendedor-no-activa-la-indexacion-automatica
+locale: es
+kiStatus: Backlog
+internalReference: 1041874
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En la interfaz de usuario de gestión de vendedores, elimine o añada una nueva política comercial a un vendedor.
+
+Este proceso se guarda correctamente, sin embargo la información no se actualiza automáticamente en el indexador de productos relacionados con ese vendedor específico.
+
+Como consecuencia, la oferta del vendedor en estos productos estará desactualizada como:
+- aún disponible en la política comercial (si la acción fue eliminarla);
+- no disponible en la política comercial (si la acción fue añadirla).
+
+
+
+##
+
+## Simulación
+
+
+
+- Compruebe un producto que tiene una oferta de un vendedor con una política comercial específica;
+- Elimine la política comercial de este vendedor utilizando la interfaz de usuario de gestión de vendedores;
+- Compruebe que la acción no se ha reflejado en el producto.
+
+
+
+## Workaround
+
+
+Indexe el producto manualmente.
+
+
+
+
+
diff --git a/docs/known-issues/es/update-users-name-in-the-login-section.md b/docs/known-issues/es/update-users-name-in-the-login-section.md
index ef4696518..cb09e203c 100644
--- a/docs/known-issues/es/update-users-name-in-the-login-section.md
+++ b/docs/known-issues/es/update-users-name-in-the-login-section.md
@@ -3,8 +3,8 @@ title: 'Actualizar el nombre del usuario en la sección de inicio de sesión'
 id: 2jshd2ApTq7hKNLbQiCWdS
 status: PUBLISHED
 createdAt: 2022-03-14T17:20:40.732Z
-updatedAt: 2022-11-25T21:57:07.628Z
-publishedAt: 2022-11-25T21:57:07.628Z
+updatedAt: 2024-02-16T20:26:07.889Z
+publishedAt: 2024-02-16T20:26:07.889Z
 firstPublishedAt: 2022-03-14T17:20:42.505Z
 contentType: knownIssue
 productTeam: Identity
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Identity
 slug: actualizar-el-nombre-del-usuario-en-la-seccion-de-inicio-de-sesion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 542029
 ---
 
diff --git a/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md b/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
index 10447a7c2..01d7e2d30 100644
--- a/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
+++ b/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
@@ -3,8 +3,8 @@ title: 'Actualización de las especificaciones del producto inviable debido a la
 id: 6FeuIyF2E5WdS0PNRRzgdA
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:06.720Z
-updatedAt: 2022-11-25T21:44:35.149Z
-publishedAt: 2022-11-25T21:44:35.149Z
+updatedAt: 2024-02-16T20:29:52.260Z
+publishedAt: 2024-02-16T20:29:52.260Z
 firstPublishedAt: 2022-06-28T16:55:07.124Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: actualizacion-de-las-especificaciones-del-producto-inviable-debido-a-la-falta-de-propiedad-en-get-resp-json
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 301725
 ---
 
diff --git a/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md b/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md
new file mode 100644
index 000000000..229be0744
--- /dev/null
+++ b/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md
@@ -0,0 +1,53 @@
+---
+title: 'Subir archivo no funciona en admin/portal/#/sites/default/code'
+id: 5pFAkaymcuOQMAqUDGPQZK
+status: PUBLISHED
+createdAt: 2023-09-12T13:37:36.429Z
+updatedAt: 2023-09-12T13:37:37.323Z
+publishedAt: 2023-09-12T13:37:37.323Z
+firstPublishedAt: 2023-09-12T13:37:37.323Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: subir-archivo-no-funciona-en-adminportalsitesdefaultcode
+locale: es
+kiStatus: Backlog
+internalReference: 897956
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al intentar subir un nuevo fichero en admin/portal/#/sites/default/code no ocurre nada. Comprobando la consola en devTools podemos ver un mensaje de error:
+"eventTrackerService no está definido"
+
+
+##
+
+## Simulación
+
+
+
+1. 1. Vaya a admin/portal/#/sites/default/code
+2. Vaya a Nuevo -> Subir Archivo -> seleccione el archivo que desea importar -> pulse crear
+ ![](https://vtexhelp.zendesk.com/attachments/token/4uSgPeUxG9xAOkTq1HUs8khX6/?name=image.png)
+3. Compruebe que no ocurre nada.
+
+
+##
+
+## Workaround
+
+
+La WA es crear el fichero directamente en esta UI.
+Ir a Nuevo -> Archivo -> Nombre del archivo y haga clic en crear -> Inserte el código y haga clic en guardar.
+
+
+
+
+
diff --git a/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md b/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
new file mode 100644
index 000000000..3631c409b
--- /dev/null
+++ b/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
@@ -0,0 +1,56 @@
+---
+title: 'El usuario puede ver y acceder a las funciones del CMS incluso sin el permiso correcto'
+id: n2BmrCyzXD04sysczRuyt
+status: PUBLISHED
+createdAt: 2024-06-07T12:22:10.494Z
+updatedAt: 2024-06-07T12:22:11.466Z
+publishedAt: 2024-06-07T12:22:11.466Z
+firstPublishedAt: 2024-06-07T12:22:11.466Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: el-usuario-puede-ver-y-acceder-a-las-funciones-del-cms-incluso-sin-el-permiso-correcto
+locale: es
+kiStatus: Backlog
+internalReference: 1046263
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si el usuario no tiene ninguno de los permisos de CMS el usuario no debería ser capaz de acceder o incluso ver los módulos de CMS. Pero esto no sucede.
+
+
+##
+
+## Simulación
+
+
+Intente acceder a los módulos CMS usando un usuario que no tenga los siguientes permisos LM:
+
+      CMS:
+
+- Ver menú CMS en la barra superior
+- Configuración
+
+GraphQL:
+- API GraphQL de CMS
+
+El usuario podrá seguir accediendo y viendo los recursos (pero no editarlos).
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
new file mode 100644
index 000000000..e895b5353
--- /dev/null
+++ b/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -0,0 +1,56 @@
+---
+title: 'El usuario sólo con el rol "Administrador de usuarios - RESTRINGIDO" no puede listar los usuarios'
+id: ifXUAzgJ1xr8ezhqKpRUI
+status: PUBLISHED
+createdAt: 2023-11-08T18:07:14.508Z
+updatedAt: 2023-11-08T18:07:15.030Z
+publishedAt: 2023-11-08T18:07:15.030Z
+firstPublishedAt: 2023-11-08T18:07:15.030Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: el-usuario-solo-con-el-rol-administrador-de-usuarios-restringido-no-puede-listar-los-usuarios
+locale: es
+kiStatus: Backlog
+internalReference: 932666
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si un usuario administrador sólo tiene el rol "**Administrador de usuarios - RESTRINGIDO**" (recurso "**Guardar usuario**"), la lista de usuarios no está disponible y no es posible realizar las ediciones o eliminaciones necesarias.
+
+
+##
+
+## Simulación
+
+
+
+- Tener un usuario sólo con el rol "**Usuario Administrador - RESTRINGIDO**";
+- Acceda a la página "**Admin Usuarios**" con este usuario (por ejemplo, https://my-account-here.myvtex.com/admin/users);
+- Puede observar que la lista está vacía, incluso con usuarios ya registrados ("_No users found :: The user search returned an empty list. Intente eliminar cualquier filtro de búsqueda o añadir nuevos usuarios a esta cuenta._"):
+ ![](https://vtexhelp.zendesk.com/attachments/token/fZ2k11R3xPrhNv5yHVkv9alam/?name=image.png)
+
+- Es posible añadir el usuario que queramos, e incluir los roles necesarios, pero no podemos acceder a los usuarios para añadir/editar/eliminar roles, o incluso borrar al usuario a través de su registro, sino sólo a través del rol.
+
+
+
+## Workaround
+
+
+Puedes añadir o eliminar el usuario al rol accediendo directamente al rol.
+
+También puedes crear un rol personalizado sólo con los recursos "**Obtener roles paginados**" y "**Obtener usuarios paginados**":
+ ![](https://vtexhelp.zendesk.com/attachments/token/yjNfjlnfFaBrXZE6gx97OaxHy/?name=image.png)
+Y luego, añadirlo al usuario que puede guardar usuarios.
+
+
+
+
+
diff --git a/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md b/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md
new file mode 100644
index 000000000..d79683909
--- /dev/null
+++ b/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md
@@ -0,0 +1,45 @@
+---
+title: 'Los usuarios no pueden acceder a la administración de la tarjeta regalo (página en bucle)'
+id: 5FowAAf8VulbVXcQIeSmHd
+status: PUBLISHED
+createdAt: 2024-05-02T15:26:57.386Z
+updatedAt: 2024-05-02T15:26:58.463Z
+publishedAt: 2024-05-02T15:26:58.463Z
+firstPublishedAt: 2024-05-02T15:26:58.463Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: los-usuarios-no-pueden-acceder-a-la-administracion-de-la-tarjeta-regalo-pagina-en-bucle
+locale: es
+kiStatus: Backlog
+internalReference: 1025971
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si los usuarios bloquean las cookies de terceros (configuración del navegador) no podrán acceder al módulo de Tarjeta Regalo en admin, hay una cookie establecida en otro dominio VTEX.
+
+
+##
+
+## Simulación
+
+
+Después de bloquear las cookies de terceros es posible simular el problema mencionado anteriormente, también puede inspeccionar la página (herramientas de desarrollador) e ir a la pestaña Red (buscar Vale.aspx), habrá un código de estado 302.
+
+
+
+## Workaround
+
+
+Ponga en la lista blanca las cookies de terceros presentes en el dominio myvtex.com.
+
+
+
+
diff --git a/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md b/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
new file mode 100644
index 000000000..406a1cfec
--- /dev/null
+++ b/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
@@ -0,0 +1,51 @@
+---
+title: 'Los usuarios con más de un pedido registrado en la entidad BK con diferentes correos electrónicos no pueden ver los pedidos en la página Mi cuenta'
+id: 43NLxAbOtyVzOCdS9Dns8c
+status: PUBLISHED
+createdAt: 2024-02-21T22:30:42.218Z
+updatedAt: 2024-02-21T22:30:43.137Z
+publishedAt: 2024-02-21T22:30:43.137Z
+firstPublishedAt: 2024-02-21T22:30:43.137Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: los-usuarios-con-mas-de-un-pedido-registrado-en-la-entidad-bk-con-diferentes-correos-electronicos-no-pueden-ver-los-pedidos-en-la-pagina-mi-cuenta
+locale: es
+kiStatus: Backlog
+internalReference: 986324
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Debido a la unificación de perfiles algunos usuarios pueden tener pedidos con diferentes emails, y esto es un problema para mostrar los pedidos en la página de mi cuenta (mis pedidos).
+
+Mis pedidos solicita esta información en la entidad BK de Datos Maestros para eliminar el impacto del retraso de indexación, pero el BK tiene el historial y los pedidos con diferentes correos electrónicos. Pero el OMS tiene la línea de código para comprobar si el correo electrónico devuelto es correcto, comprobando el correo electrónico del consultor y el correo electrónico registrado en los pedidos.
+
+
+##
+
+## Simulación
+
+
+Dos pedidos creados con diferentes correos electrónicos, por ejemplo joao@gmail.com y joao2@gmail.com, cuando este usuario tiene el perfil de unificación sólo un correo electrónico será válido.
+Después si el joao2@gmail.com entra en la página de mi cuenta, no será posible ver los pedidos porque hay un pedido antiguo sin el carácter "2" en el email, por lo que la clave principal (email.) es diferente.
+
+
+
+
+
+## Workaround
+
+
+Por ahora no hay solución.
+
+
+
+
+
diff --git a/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md b/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
new file mode 100644
index 000000000..f17a5b0f0
--- /dev/null
+++ b/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
@@ -0,0 +1,48 @@
+---
+title: 'UseSessionRegionAtCheckout no funciona correctamente al añadir el primer artículo al carrito.'
+id: 2NzgWTbaHF47f5dl49A2D5
+status: PUBLISHED
+createdAt: 2023-10-24T22:51:27.435Z
+updatedAt: 2023-10-26T10:55:29.843Z
+publishedAt: 2023-10-26T10:55:29.843Z
+firstPublishedAt: 2023-10-24T22:51:28.246Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: usesessionregionatcheckout-no-funciona-correctamente-al-anadir-el-primer-articulo-al-carrito
+locale: es
+kiStatus: Backlog
+internalReference: 925049
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Si una cuenta tiene configurado el toggle 'UseSessionRegionAtCheckout', al añadir un artículo y el orderForm no tiene 'shippingData', no se configura el vendedor, mostrando precios y disponibilidad diferentes.
+
+
+##
+
+## Simulación
+
+
+
+- La cuenta debe estar usando UseSessionRegionAtCheckout;
+- Establecer un regionId en la sesión;
+- Añadir un artículo al carrito; puede mostrar diferentes precios y disponibilidad.
+
+
+
+## Workaround
+
+
+Actualice el orderForm (API Get current o cree un nuevo carrito) utilizando el parámetro `?refreshOutdatedData=true`.
+
+
+
+
diff --git a/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md b/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
index 50d82e76d..78ac017b4 100644
--- a/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
+++ b/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
@@ -3,8 +3,8 @@ title: 'El uso de muchos filtros en la lista OMS afecta a los resultados del inf
 id: WO9AvZxmUkmil35OZb8Lr
 status: PUBLISHED
 createdAt: 2023-02-17T17:45:57.039Z
-updatedAt: 2023-02-17T17:52:41.370Z
-publishedAt: 2023-02-17T17:52:41.370Z
+updatedAt: 2024-06-28T19:28:50.107Z
+publishedAt: 2024-06-28T19:28:50.107Z
 firstPublishedAt: 2023-02-17T17:50:29.929Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,35 +12,46 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: el-uso-de-muchos-filtros-en-la-lista-oms-afecta-a-los-resultados-del-informe
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 756198
 ---
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
+
 El uso de filtros en la Lista de Gestión de Pedidos genera un parámetro en la URL que ayuda a definir lo que se muestra al cargar la página y a generar el informe de pedidos exportados. En ese sentido, a medida que usamos más y más filtros, los parámetros incluidos en la URL aumentan proporcionalmente, y la cadena de consulta también, alcanzando puntos (tamaño) que pueden generar varios tipos de comportamientos no deseados.
 
 En este caso, el problema causado por utilizar muchos filtros a la vez (tamaño de la **Query String** en la URL) afecta a los resultados del informe exportado, mostrando menos pedidos de los esperados.
 
-Es importante tener en cuenta que aquí estamos hablando del **tamaño del Query String generado en la URL**, esto significa que no es el número de filtros utilizados directamente, sino el tamaño de cada parámetro. Nombres de filtros muy grandes pueden limitar el número de filtros que se pueden utilizar para generar un informe coherente.
+Es importante tener en cuenta que aquí estamos hablando del **tamaño del Query String generado en la URL**, esto significa que no es el número de filtros utilizados directamente, sino el tamaño de cada parámetro. Nombres de filtros muy grandes pueden limitar el número de filtros que puede utilizar para generar un informe coherente.
+
 
+##
 
 ## Simulación
 
+
 Este escenario puede simularse utilizando varios filtros "largos" en la lista OMS y exportando los pedidos. Puede ver que la exportación muestra menos pedidos que la lista OMS.
 
 
+
 ## Workaround
 
+
 Es posible pensar en formas alternativas para evitar este tipo de problemas en el informe. He aquí algunos puntos que pueden ser útiles:
 
 - Optimizar el nombre de los parámetros podría ser una buena práctica.
 - Exportar el informe con pocos filtros y luego en el documento exportado, realizar los filtros adicionales o necesarios para obtener la información deseada.
-- Pensar en dividir el informe en más de uno, es decir, utilizar unos filtros para generar una parte de la información y luego otro con el resto y unificar después de ser descargado.
+- Piense en dividir el informe en más de uno, es decir, utilizar unos filtros para generar una parte de la información y luego otro con el resto y unificar después de ser descargado.
 
 Estas son solo ideas para evitar acumular filtros y generar esta inconsistencia en la información exportada. Se pueden utilizar otras soluciones.
 
+
+
+
+
+
diff --git a/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md b/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
new file mode 100644
index 000000000..4a81dae4f
--- /dev/null
+++ b/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
@@ -0,0 +1,51 @@
+---
+title: 'Usando slider-layout con el prop navigationStep a 1 causa que los últimos puntos estén vacíos'
+id: 28hbmflHNhAQmHN51Y6abX
+status: PUBLISHED
+createdAt: 2023-09-29T14:41:34.387Z
+updatedAt: 2023-09-29T14:57:48.863Z
+publishedAt: 2023-09-29T14:57:48.863Z
+firstPublishedAt: 2023-09-29T14:41:35.227Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: usando-sliderlayout-con-el-prop-navigationstep-a-1-causa-que-los-ultimos-puntos-esten-vacios
+locale: es
+kiStatus: Backlog
+internalReference: 910125
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando tenemos un bloque slider-layout con la prop `navigationStep` puesta a 1 y el `itemsPerPage` diferente de 1 el último punto estará vacío y no es posible borrarlo.
+
+
+##
+
+## Simulación
+
+
+
+- Crear un nuevo bloque deslizante
+- Establece el `navigationStep` en 1
+- Establece `itemsPerPage` en un valor diferente a 1
+- Utilizando las flechas del deslizador, intenta navegar hasta el último punto del deslizador
+- Verás que el último punto está vacío
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md b/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
index d65ba7c20..f85a8d004 100644
--- a/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
+++ b/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
@@ -3,8 +3,8 @@ title: 'utmi_p e utmi_pc no se mantienen en la URL después del inicio de sesió
 id: 7e8EO8EWEJCLbXs16ZofQk
 status: PUBLISHED
 createdAt: 2022-03-16T16:17:55.535Z
-updatedAt: 2022-11-25T22:11:21.772Z
-publishedAt: 2022-11-25T22:11:21.772Z
+updatedAt: 2024-02-16T20:29:25.217Z
+publishedAt: 2024-02-16T20:29:25.217Z
 firstPublishedAt: 2022-03-16T16:17:55.979Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: utmip-e-utmipc-no-se-mantienen-en-la-url-despues-del-inicio-de-sesion
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 372787
 ---
 
diff --git a/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md b/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md
new file mode 100644
index 000000000..6ce0c012c
--- /dev/null
+++ b/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md
@@ -0,0 +1,49 @@
+---
+title: 'ValidateCartMutation falla cuando la carga útil es grande'
+id: 5YmPMVGsi92owcmICg3CY3
+status: PUBLISHED
+createdAt: 2024-02-21T15:23:44.054Z
+updatedAt: 2024-02-21T15:23:44.919Z
+publishedAt: 2024-02-21T15:23:44.919Z
+firstPublishedAt: 2024-02-21T15:23:44.919Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: validatecartmutation-falla-cuando-la-carga-util-es-grande
+locale: es
+kiStatus: Backlog
+internalReference: 985867
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+Al añadir varios productos en minicart, dependiendo de la información asociada a esos productos, si recibimos un error payloadTooLarge, el producto se añadirá al carrito pero no pasará a orderForm correctamente
+
+
+##
+
+## Simulación
+
+
+
+
+- Añade productos al carrito hasta que recibas un error 413 Payload Too Large
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md b/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
index 1dc6ddd5b..b7df993ed 100644
--- a/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
+++ b/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
@@ -3,8 +3,8 @@ title: 'Las transacciones de verificación al guardar la tarjeta en MyCards no s
 id: 3VqRlcnzHqDEx7v1IIlBuf
 status: PUBLISHED
 createdAt: 2022-03-27T15:14:55.382Z
-updatedAt: 2022-11-25T22:08:31.611Z
-publishedAt: 2022-11-25T22:08:31.611Z
+updatedAt: 2024-02-16T20:27:46.524Z
+publishedAt: 2024-02-16T20:27:46.524Z
 firstPublishedAt: 2022-03-27T15:14:56.630Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: las-transacciones-de-verificacion-al-guardar-la-tarjeta-en-mycards-no-se-cancelan-automaticamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 347084
 ---
 
diff --git a/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
new file mode 100644
index 000000000..e65315138
--- /dev/null
+++ b/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -0,0 +1,63 @@
+---
+title: 'Autor de la versión "Nota: No encontrado en VTEX ID." en el perfil'
+id: 0X6Aj6YdCXXfNweAkDS46
+status: PUBLISHED
+createdAt: 2023-10-04T21:48:14.699Z
+updatedAt: 2023-10-04T22:14:45.195Z
+publishedAt: 2023-10-04T22:14:45.195Z
+firstPublishedAt: 2023-10-04T21:48:15.379Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: autor-de-la-version-nota-no-encontrado-en-vtex-id-en-el-perfil
+locale: es
+kiStatus: Scheduled
+internalReference: 914314
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando el cliente realiza una compra, el autor de la versión recibe un id de usuario (guid) o un servicio, seguido del login/nombre/descripción "`Note: Not found on VTEX ID.`" en el perfil.
+Este comportamiento no tiene impacto en el perfil o la experiencia del comprador, una vez que esto es sólo acerca de la interfaz de usuario, y es posible comprobar la información por versión API.
+
+
+##
+
+## Simulación
+
+
+
+- Acceso Datos Maestros CRM (por ejemplo https://my-account-here.vtexcrm.com.br);
+- Acceda a la pestaña Entidad de Datos CL (Clientes):
+- Seleccione un documento y haga clic en el icono del ojo para ver los datos;
+- Haga clic en el botón "_Cambiar registro_";
+- Abra una versión reciente;
+- Compruebe el "_Autor de la versión_", será un identificador de usuario, y el nombre "`Nota: No encontrado en VTEX ID.`", por ejemplo:
+ ![](https://vtexhelp.zendesk.com/attachments/token/9ngSibhlO4er0Df3Fi7oQAhot/?name=image.png)
+ ![](https://vtexhelp.zendesk.com/attachments/token/8tlsDbxNSFFHdJMVHf2yvctem/?name=image.png)
+
+- Comprobación mediante la API Get version:
+ ![](https://vtexhelp.zendesk.com/attachments/token/MRrTRox5E0t91F3OpsDcRmJ9z/?name=image.png)
+
+    "updatedBy_USER": "{\"Id\":\"d6d8269f-e7cc-4e4b-8b89-3b46a1407937\",\"Login\":\"vtex-service::checkout::stable\",\"Name\":null}",
+
+
+
+
+## Workaround
+
+
+Puede comprobar el autor utilizando nuestras API:
+
+- Listar versiones
+- Obtener versión
+
+
+
+
diff --git a/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md b/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md
index d09c0d555..71a4e2c96 100644
--- a/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md
+++ b/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md
@@ -3,8 +3,8 @@ title: 'Via Integration no envía la descripción en la tarjeta'
 id: Da5jnqoSO8an64jy29VhM
 status: PUBLISHED
 createdAt: 2023-05-16T16:47:19.803Z
-updatedAt: 2023-05-18T18:03:54.502Z
-publishedAt: 2023-05-18T18:03:54.502Z
+updatedAt: 2023-06-19T12:30:03.552Z
+publishedAt: 2023-06-19T12:30:03.552Z
 firstPublishedAt: 2023-05-16T16:47:20.416Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: via-integration-no-envia-la-descripcion-en-la-tarjeta
 locale: es
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 826488
 ---
 
diff --git a/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md b/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
index 720cfa237..de7a5acdc 100644
--- a/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
+++ b/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
@@ -3,8 +3,8 @@ title: 'El atributo de vídeo no se envía del vendedor al mercado'
 id: 6JfHpP6F8TGmJofoKc99ON
 status: PUBLISHED
 createdAt: 2022-02-07T20:07:23.358Z
-updatedAt: 2023-05-09T19:03:49.838Z
-publishedAt: 2023-05-09T19:03:49.838Z
+updatedAt: 2024-02-16T20:23:28.657Z
+publishedAt: 2024-02-16T20:23:28.657Z
 firstPublishedAt: 2022-02-07T20:07:23.814Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: el-atributo-de-video-no-se-envia-del-vendedor-al-mercado
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 519412
 ---
 
diff --git a/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md b/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md
index 341ebeac5..0b60b19c0 100644
--- a/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md
+++ b/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md
@@ -3,8 +3,8 @@ title: 'El componente de vídeo no funciona correctamente en los dispositivos iO
 id: 2bRQkTdRk2OJQMw5CKVieW
 status: PUBLISHED
 createdAt: 2022-07-01T17:21:47.912Z
-updatedAt: 2022-11-25T22:13:54.314Z
-publishedAt: 2022-11-25T22:13:54.314Z
+updatedAt: 2024-02-16T20:25:23.862Z
+publishedAt: 2024-02-16T20:25:23.862Z
 firstPublishedAt: 2022-07-01T17:21:48.826Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: el-componente-de-video-no-funciona-correctamente-en-los-dispositivos-ios
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 609462
 ---
 
diff --git a/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md b/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
new file mode 100644
index 000000000..bc9528d4e
--- /dev/null
+++ b/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
@@ -0,0 +1,48 @@
+---
+title: 'el evento view_cart sólo se recibe en el dataLayer cada dos por tres'
+id: 73fimN0XczGQch20BhGAOo
+status: PUBLISHED
+createdAt: 2024-06-12T12:58:59.438Z
+updatedAt: 2024-06-12T12:59:00.499Z
+publishedAt: 2024-06-12T12:59:00.499Z
+firstPublishedAt: 2024-06-12T12:59:00.499Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-evento-viewcart-solo-se-recibe-en-el-datalayer-cada-dos-por-tres
+locale: es
+kiStatus: Backlog
+internalReference: 1048306
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+El evento view_cart sólo se recibe en el dataLayer cada dos por tres.
+
+
+##
+
+## Simulación
+
+
+Intenta abrir el minicart por primera vez, esta vez se recibirá el evento
+Al intentar abrir por segunda vez el evento no se recibirá
+A la tercera vez, el evento se recibirá de nuevo y así sucesivamente
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md b/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
new file mode 100644
index 000000000..2f2fade43
--- /dev/null
+++ b/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
@@ -0,0 +1,49 @@
+---
+title: 'El evento view_cart se dispara dos veces cuando cambiamos la cantidad de productos en el minicart'
+id: 3NlB10z0ulKu7sySxPgkmp
+status: PUBLISHED
+createdAt: 2024-05-28T20:13:35.657Z
+updatedAt: 2024-05-28T20:13:36.602Z
+publishedAt: 2024-05-28T20:13:36.602Z
+firstPublishedAt: 2024-05-28T20:13:36.602Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: el-evento-viewcart-se-dispara-dos-veces-cuando-cambiamos-la-cantidad-de-productos-en-el-minicart
+locale: es
+kiStatus: Backlog
+internalReference: 1040772
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando cambiamos la cantidad de un producto en el minicart el evento view_cart se dispara dos veces
+
+
+##
+
+## Simulación
+
+
+
+- Añadir un producto a la mini-tienda;
+- Abrir el minicarro;
+- Cambiar la cantidad del producto en el minicart;
+- Comprueba tu dataLayer, el evento view_cart se dispara dos veces
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/visited-product-feature-does-not-work-properly.md b/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
index 56df2e55c..4270ddd83 100644
--- a/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
@@ -3,8 +3,8 @@ title: ' La función "Producto visitado" no funciona correctamente'
 id: 5AiCVwLkGToEgtLkZVPe5i
 status: PUBLISHED
 createdAt: 2022-11-25T18:45:15.389Z
-updatedAt: 2022-11-30T19:05:56.190Z
-publishedAt: 2022-11-30T19:05:56.190Z
+updatedAt: 2024-02-16T20:27:41.835Z
+publishedAt: 2024-02-16T20:27:41.835Z
 firstPublishedAt: 2022-11-25T18:45:15.854Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: la-funcion-producto-visitado-no-funciona-correctamente
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 701169
 ---
 
diff --git a/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md b/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
new file mode 100644
index 000000000..84db0ec1a
--- /dev/null
+++ b/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
@@ -0,0 +1,54 @@
+---
+title: 'Las reglas de merchandising visual no funcionan cuando se proporcionan varios términos de búsqueda'
+id: 6FkfnnvFiYXYqPgMrpDgM1
+status: PUBLISHED
+createdAt: 2024-06-20T21:41:14.250Z
+updatedAt: 2024-06-20T21:41:15.088Z
+publishedAt: 2024-06-20T21:41:15.088Z
+firstPublishedAt: 2024-06-20T21:41:15.088Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: las-reglas-de-merchandising-visual-no-funcionan-cuando-se-proporcionan-varios-terminos-de-busqueda
+locale: es
+kiStatus: Backlog
+internalReference: 1053623
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Aunque es posible proporcionar varios términos de búsqueda al crear una regla de merchandising visual para la Búsqueda Inteligente, no se pueden utilizar. La regla se considerará inválida y no se aplicará.
+
+Diferentes términos de búsqueda pueden devolver productos completamente diferentes en un resultado de búsqueda en un orden diferente, lo que es incompatible con la acción de fijar (_promover_) u ocultar (_eliminar_) algunos productos que ofrece una regla visual.
+
+Al tratarse de una acción no válida, no se espera que se proporcione esta condición y se eliminará de la interfaz.
+
+
+##
+
+## Simulación
+
+
+
+- Crear una regla de merchandising visual
+- Aplicar varios términos de búsqueda como condición para la regla
+- Seleccione algunos productos para fijar y/u ocultar
+- Busque uno de estos términos de búsqueda y observe que los resultados no tendrán la regla aplicada
+- También es posible observar lo mismo a través de la función de búsqueda explicada del administrador, que resaltará que no se han aplicado reglas a la búsqueda.
+
+
+
+## Workaround
+
+
+Este objetivo se consigue a través de reglas manuales de merchandising. La acción de fijar y ocultar productos es directamente compatible con las acciones de promover y eliminar para una regla manual.
+
+
+
+
diff --git a/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 33209d0ae..fe299ccf3 100644
--- a/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -41,5 +41,5 @@ No se preocupe: desactivar esta opción no significa que su tienda estará despr
 Si después de estos pasos su Admin VTEX o tienda aún no se carga, le sugerimos que intente acceder con otro navegador.
 </div>
 
-![Firefox bug ES](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/5d89ca13799da3ada490e383f0913573/Firefox_bug_ES.jpg)
+![Firefox bug ES](//images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/5d89ca13799da3ada490e383f0913573/Firefox_bug_ES.jpg)
 
diff --git a/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md b/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
new file mode 100644
index 000000000..773ebaa35
--- /dev/null
+++ b/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
@@ -0,0 +1,46 @@
+---
+title: '<vtex.cmc RegalosProducto/> no funciona antes de acceder a la caja'
+id: 3blfXfhPvY2cNEzBYGEmAo
+status: PUBLISHED
+createdAt: 2024-05-08T17:11:51.770Z
+updatedAt: 2024-05-08T17:11:52.715Z
+publishedAt: 2024-05-08T17:11:52.715Z
+firstPublishedAt: 2024-05-08T17:11:52.715Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: vtexcmc-regalosproducto-no-funciona-antes-de-acceder-a-la-caja
+locale: es
+kiStatus: Backlog
+internalReference: 1029719
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+1 - Crear una página de producto utilizando el controlador <vtex.cmc RegalosProducto>.
+2 - Cree una promoción Compre uno, llévese otro para dirigir los regalos relacionados.
+3 - Cargue la página de producto, no se renderizará ningún regalo.
+4 - Vaya a la página de pago y los regalos se cargarán.
+5 - Vuelva a la página del producto y los regalos se cargarán en la página del producto.
+
+
+
+## Workaround
+
+
+Utilice otros controladores de venta cruzada para personalizar y mostrar artículos como regalos, como similares, sugerencias y accesorios
+
+
+
+
+
diff --git a/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md b/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
index c1885e40a..ffe5f1213 100644
--- a/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
+++ b/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
@@ -3,8 +3,8 @@ title: 'Tenemos un problema al validar el campo ClientId de la Giftcard en admin
 id: 4S7CziQfj5P2NLAgUKnJnP
 status: PUBLISHED
 createdAt: 2022-03-28T00:29:38.482Z
-updatedAt: 2022-11-25T22:07:33.502Z
-publishedAt: 2022-11-25T22:07:33.502Z
+updatedAt: 2024-02-16T20:24:40.988Z
+publishedAt: 2024-02-16T20:24:40.988Z
 firstPublishedAt: 2022-03-28T00:29:39.028Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: tenemos-un-problema-al-validar-el-campo-clientid-de-la-giftcard-en-admin
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 454388
 ---
 
diff --git a/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md b/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
index d4642fb12..6c29810a9 100644
--- a/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
+++ b/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
@@ -3,8 +3,8 @@ title: 'Webanalytics Viewpart Muestra el éxito incluso cuando no está funciona
 id: 73oMf2Wxkgw1feWUvntX6s
 status: PUBLISHED
 createdAt: 2023-03-09T18:20:47.358Z
-updatedAt: 2023-03-09T18:20:52.456Z
-publishedAt: 2023-03-09T18:20:52.456Z
+updatedAt: 2024-07-01T18:48:55.053Z
+publishedAt: 2024-07-01T18:48:55.053Z
 firstPublishedAt: 2023-03-09T18:20:48.023Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: webanalytics-viewpart-muestra-el-exito-incluso-cuando-no-esta-funcionando
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 768059
 ---
 
diff --git a/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md b/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md
new file mode 100644
index 000000000..11670a471
--- /dev/null
+++ b/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md
@@ -0,0 +1,41 @@
+---
+title: 'La aplicación Webops no está totalmente integrada con Headless CMS'
+id: 577fIocKB9BYYCOkN9dZfW
+status: PUBLISHED
+createdAt: 2024-06-12T19:42:12.627Z
+updatedAt: 2024-06-27T17:35:21.924Z
+publishedAt: 2024-06-27T17:35:21.924Z
+firstPublishedAt: 2024-06-12T19:42:13.699Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: la-aplicacion-webops-no-esta-totalmente-integrada-con-headless-cms
+locale: es
+kiStatus: Backlog
+internalReference: 1048810
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+Intenta hacer una actualización en el CMS headless usando la app webops, esto fallará y no habrá un commit en el repositorio
+
+
+
+## Workaround
+
+
+La solución es crear manualmente un commit en el repositorio Git de su tienda para activar la compilación de la tienda y aplicar los cambios realizados en el Headless CMS.
+
+
+
+
diff --git a/docs/known-issues/es/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md b/docs/known-issues/es/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
index eefa3b946..1b666be38 100644
--- a/docs/known-issues/es/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
+++ b/docs/known-issues/es/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
@@ -1,36 +1,38 @@
 ---
-title: 'When a component of the kit look is out of stock, the kit is shown as sold out on searching'
-id: 56QpnBz2ayEAe00L9ojSI0
-status: DRAFT
-createdAt: 2022-01-21T18:06:21.645Z
-updatedAt: 2022-03-16T16:22:00.845Z
-publishedAt: 
-firstPublishedAt: 
+title: 'Cuando un componente de kit look no tiene stock, el kit aparece agotado en la búsqueda'
+id: 5PRtTKk1HyGkKciOussWEI
+status: PUBLISHED
+createdAt: 2017-03-29T23:44:56.615Z
+updatedAt: 2022-12-22T20:43:08.857Z
+publishedAt: 2022-12-22T20:43:08.857Z
+firstPublishedAt: 2017-03-29T23:46:36.720Z
 contentType: knownIssue
-productTeam: Portal
+productTeam: Marketing & Merchandising
 author: 2mXZkbi0oi061KicTExNjo
-tag: Portal
-slug: when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching
+tag: Catalog
+slug: cuando-un-componente-de-kit-look-no-tiene-stock-el-kit-aparece-agotado-en-la-busqueda
 locale: es
 kiStatus: Backlog
-internalReference: 342720
+internalReference: 
 ---
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+Cuando un componente de un kit look se queda sin stock, todo el kit se exhibe como agotado en la búsqueda.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+<!--- Conta original era automacaoqa, removemos por conta de EDU-2582 --->
+
+Kit Look: `https://lojateste.vtexcommercebeta.com.br/admin/site/ProdutoForm.aspx?id=2000205`
+
+Componente no disponible: `https://lojateste.vtexcommercebeta.com.br/admin/site/SkuForm.aspx?IdSku=2000362`
+
+Exhibición correcta en la página de producto: `https://lojateste.vtexcommercebeta.com.br/admin/site/SkuForm.aspx?IdSku=2000362`
+
+Exhibición incorrecta en la búsqueda: `https://lojateste.vtexcommercebeta.com.br/kits`
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+Solo utiliza el Kit Look si es posible asegurar que todos los componentes poseen stock.
 
diff --git a/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md b/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
new file mode 100644
index 000000000..d8d05d707
--- /dev/null
+++ b/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
@@ -0,0 +1,47 @@
+---
+title: 'Al acceder a mis pedidos, el nombre que aparece es el nombre del ProductName sin la información del SKU Name.'
+id: 1PTEStTC2MDQwZpE0myF44
+status: PUBLISHED
+createdAt: 2024-03-08T13:16:01.672Z
+updatedAt: 2024-03-08T13:16:02.950Z
+publishedAt: 2024-03-08T13:16:02.950Z
+firstPublishedAt: 2024-03-08T13:16:02.950Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: al-acceder-a-mis-pedidos-el-nombre-que-aparece-es-el-nombre-del-productname-sin-la-informacion-del-sku-name
+locale: es
+kiStatus: No Fix
+internalReference: 694809
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al acceder a "mis pedidos", el nombre que aparece es el nombre del "ProductName" sin la información del "SKU Name", sólo en la interfaz IO.
+
+
+
+##
+
+## Simulación
+
+
+Al acceder a "mis pedidos", verá que el nombre del producto está compuesto únicamente por el "ProductName" sin la información del "SKU Name".
+
+
+
+## Workaround
+
+
+No tenemos ninguna solución por el momento.
+
+
+
+
+
diff --git a/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index dc6cc67a0..6cb16b78f 100644
--- a/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -3,8 +3,8 @@ title: 'Al añadir una SKU a través de nuestra funcionalidad "Cambiar pedido",
 id: 35Q3KoOSsUr9n9XEDIk7nk
 status: PUBLISHED
 createdAt: 2022-04-07T14:53:35.829Z
-updatedAt: 2022-11-25T22:02:48.606Z
-publishedAt: 2022-11-25T22:02:48.606Z
+updatedAt: 2024-02-16T20:24:27.100Z
+publishedAt: 2024-02-16T20:24:27.100Z
 firstPublishedAt: 2022-04-07T14:53:36.256Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: al-anadir-una-sku-a-traves-de-nuestra-funcionalidad-cambiar-pedido-el-nombre-del-producto-no-se-muestra-en-el-pedido-ni-en-la-notificacion-por-correo-electronico
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 557978
 ---
 
diff --git a/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md b/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
index 486fdd2ed..b24b57096 100644
--- a/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
+++ b/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
@@ -3,8 +3,8 @@ title: 'Cuando se desactiva el service worker nativo no es posible utilizar uno
 id: 1GpzVam1nuGbrKR4Izx6D9
 status: PUBLISHED
 createdAt: 2023-03-14T18:20:55.443Z
-updatedAt: 2023-03-14T18:20:55.953Z
-publishedAt: 2023-03-14T18:20:55.953Z
+updatedAt: 2024-02-02T21:00:43.540Z
+publishedAt: 2024-02-02T21:00:43.540Z
 firstPublishedAt: 2023-03-14T18:20:55.953Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index 463739d71..bbea01c51 100644
--- a/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -3,8 +3,8 @@ title: 'Al cargar la página "Catalog Maping" en admin no se traduce el mensaje
 id: 4WszmRZ5jpeSDNTEuFIdwF
 status: PUBLISHED
 createdAt: 2022-12-15T12:32:17.741Z
-updatedAt: 2022-12-15T12:32:18.420Z
-publishedAt: 2022-12-15T12:32:18.420Z
+updatedAt: 2024-02-16T20:23:22.033Z
+publishedAt: 2024-02-16T20:23:22.033Z
 firstPublishedAt: 2022-12-15T12:32:18.420Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: al-cargar-la-pagina-catalog-maping-en-admin-no-se-traduce-el-mensaje-inicial
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 717066
 ---
 
diff --git a/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 05cd97149..3674fd1e2 100644
--- a/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -3,8 +3,8 @@ title: 'Cuando settleId se envía como null y el código como "refund-manually"
 id: 2PdRRjHDODY2Tk0VItO4Fo
 status: PUBLISHED
 createdAt: 2022-07-11T17:37:43.961Z
-updatedAt: 2022-11-25T22:04:38.681Z
-publishedAt: 2022-11-25T22:04:38.681Z
+updatedAt: 2024-02-16T20:28:17.704Z
+publishedAt: 2024-02-16T20:28:17.704Z
 firstPublishedAt: 2022-07-11T17:37:44.954Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: cuando-settleid-se-envia-como-null-y-el-codigo-como-refundmanually-nuestra-pasarela-realiza-un-doble-reembolso
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 615050
 ---
 
diff --git a/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md b/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
index a357820ba..775d2ceee 100644
--- a/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
+++ b/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
@@ -3,8 +3,8 @@ title: 'Cuando shippingEstimate es = 0, el cálculo de deliverySlaInMinutes devu
 id: UGk2WYb3w3ZWH4pL07TNg
 status: PUBLISHED
 createdAt: 2022-02-01T13:04:45.737Z
-updatedAt: 2022-11-25T21:51:01.802Z
-publishedAt: 2022-11-25T21:51:01.802Z
+updatedAt: 2024-02-16T20:24:38.902Z
+publishedAt: 2024-02-16T20:24:38.902Z
 firstPublishedAt: 2022-02-01T13:04:46.164Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: cuando-shippingestimate-es-0-el-calculo-de-deliveryslainminutes-devuelve-null
 locale: es
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 514835
 ---
 
diff --git a/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md b/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
new file mode 100644
index 000000000..dcb20847b
--- /dev/null
+++ b/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
@@ -0,0 +1,49 @@
+---
+title: 'Al usar filtros horizontales, después de elegir tres de ellos, las opciones del filtro ya no se colapsan.'
+id: 7xPLXjZMqwxQmWwJsd63eC
+status: PUBLISHED
+createdAt: 2023-07-11T12:30:50.198Z
+updatedAt: 2024-02-16T19:16:06.662Z
+publishedAt: 2024-02-16T19:16:06.662Z
+firstPublishedAt: 2023-07-11T12:30:50.962Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: al-usar-filtros-horizontales-despues-de-elegir-tres-de-ellos-las-opciones-del-filtro-ya-no-se-colapsan
+locale: es
+kiStatus: Backlog
+internalReference: 859382
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando la tienda está utilizando los filtros en la opción horizontal cada vez que haga clic en un filtro de sus opciones se derrumbará. Pero, cuando se hace clic en un filtro por tercera vez el filtro no se derrumbará más. Se bloqueará.
+
+
+##
+
+## Simulación
+
+
+
+- Encuentra una tienda utilizando la opción de filtro horizontal
+- Elige tres filtros diferentes
+- En el tercero, se bloqueará
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md b/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
new file mode 100644
index 000000000..e2e6f1309
--- /dev/null
+++ b/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
@@ -0,0 +1,41 @@
+---
+title: 'Precio al contado incorrecto para artículos con UnitMultiplier superior a 1 en API de búsqueda inteligente'
+id: 50Ufh8uqYt76Ddxrz0Id99
+status: PUBLISHED
+createdAt: 2023-11-11T00:26:08.800Z
+updatedAt: 2023-11-11T00:26:09.509Z
+publishedAt: 2023-11-11T00:26:09.509Z
+firstPublishedAt: 2023-11-11T00:26:09.509Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: precio-al-contado-incorrecto-para-articulos-con-unitmultiplier-superior-a-1-en-api-de-busqueda-inteligente
+locale: es
+kiStatus: Backlog
+internalReference: 934687
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+
+## Simulación
+
+
+En la API REST o GraphQL de Intelligent Search, compruebe la propiedad para los elementos en este escenario específico.
+
+
+
+## Workaround
+
+
+El valor correcto para `spotPrice` se puede recuperar del array `Installments` dentro del mismo objeto `commertialOffer`.
+
+
+
+
diff --git a/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md b/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md
new file mode 100644
index 000000000..6819d7bc3
--- /dev/null
+++ b/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md
@@ -0,0 +1,55 @@
+---
+title: 'Traducción errónea para diferentes campos bajo el mismo valor original'
+id: 5amLWqGy7TPh7tk4KnLTmW
+status: PUBLISHED
+createdAt: 2024-02-16T00:05:00.562Z
+updatedAt: 2024-02-16T00:05:01.618Z
+publishedAt: 2024-02-16T00:05:01.618Z
+firstPublishedAt: 2024-02-16T00:05:01.618Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: traduccion-erronea-para-diferentes-campos-bajo-el-mismo-valor-original
+locale: es
+kiStatus: Backlog
+internalReference: 982848
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La Búsqueda Inteligente puede utilizar una traducción errónea para un campo cuyo valor en el idioma primario es el mismo entre diferentes campos.
+
+
+##
+
+## Simulación
+
+
+Considerando dos campos (categoría y especificación) de un producto en una tienda con "nl-BE" como idioma por defecto y "fr-BE" como idioma adicional con los siguientes valores:
+
+- categoría
+  - nl-BE = medio
+  - fr-BE = medio
+- especificación
+  - nl-BE = medio
+  - fr-BE = medio
+
+En caso de discordancia, la traducción "fr-BE" para el campo de especificación puede indexarse erróneamente como "moyens" en lugar de "midi".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md b/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
new file mode 100644
index 000000000..53e024b89
--- /dev/null
+++ b/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
@@ -0,0 +1,46 @@
+---
+title: 'Valor incorrecto para el precioDefinición en el orden de la cadena para un mercado multinivel'
+id: 75qEjhgv1tTQNho0MArnJo
+status: PUBLISHED
+createdAt: 2023-11-27T13:50:18.505Z
+updatedAt: 2023-11-27T13:51:42.434Z
+publishedAt: 2023-11-27T13:51:42.434Z
+firstPublishedAt: 2023-11-27T13:51:42.434Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: valor-incorrecto-para-el-preciodefinicion-en-el-orden-de-la-cadena-para-un-mercado-multinivel
+locale: es
+kiStatus: Backlog
+internalReference: 663203
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La propiedad "priceDefinition" para órdenes en el nivel "cadena" en un mercado multinivel no está siguiendo el "sellingPrice" como se esperaba. En su lugar, está siguiendo la propiedad "precio".
+
+
+##
+
+## Simulación
+
+
+Crear un pedido con un descuento aplicado desde la capa de marketplace (nivel 1), en relación con la capa de vendedor (cadena, nivel 2), en una relación multinivel. La capa de cumplimiento (nivel 3) presentará los valores correctamente, pero la "cadena" no.
+
+
+
+## Workaround
+
+
+Evite utilizar la propiedad "priceDefinition" en este tipo de pedidos y haga los cálculos utilizando las propiedades price, quantity, unitMultiplier, y priceTag - para evitar problemas con el "sellingPrice", que no es un valor preciso.
+
+
+
+
+
diff --git a/docs/known-issues/es/xml-currency-symbol-in-the-installment.md b/docs/known-issues/es/xml-currency-symbol-in-the-installment.md
index d25f98863..02fea633e 100644
--- a/docs/known-issues/es/xml-currency-symbol-in-the-installment.md
+++ b/docs/known-issues/es/xml-currency-symbol-in-the-installment.md
@@ -1,10 +1,10 @@
 ---
 title: 'XML - Simbolo de moneda en campo "Parcelamento"'
 id: 4s7hBA1MAUgeEC2Q4K8gKM
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-26T15:22:31.980Z
-updatedAt: 2022-12-22T20:48:49.927Z
-publishedAt: 2022-12-22T20:48:49.927Z
+updatedAt: 2024-02-02T20:08:19.240Z
+publishedAt: 
 firstPublishedAt: 2017-06-26T23:18:58.653Z
 contentType: knownIssue
 productTeam: Marketing & Merchandising
@@ -22,7 +22,8 @@ Al configurar una moneda en un XML, la misma se aplica a todos los campos, excep
 
 El campo **Parcelamento** siempre muestra la moneda "R$", independientemente de que la moneda configurada sea diferente.
 
-![Parcelamento](//files.slack.com/files-pri/T02BCPD0X-F5WHSHM5E/image.png)
+![Parcelamento](https://github.com/vtexdocs/devportal/assets/77292838/7a6323e9-da76-4645-a13a-fcd1202efe52)
+
 
 ## Simulación
 
diff --git a/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md b/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
new file mode 100644
index 000000000..7cb456da6
--- /dev/null
+++ b/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
@@ -0,0 +1,44 @@
+---
+title: 'Campo de categoría global XML que muestra la información definida en el nivel global de categoría.'
+id: 508Gdn8StafQKOa2Wyfr8u
+status: PUBLISHED
+createdAt: 2022-01-21T17:38:16.365Z
+updatedAt: 2024-02-16T20:30:04.149Z
+publishedAt: 2024-02-16T20:30:04.149Z
+firstPublishedAt: 2024-01-23T15:32:13.423Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: campo-de-categoria-global-xml-que-muestra-la-informacion-definida-en-el-nivel-global-de-categoria
+locale: es
+kiStatus: No Fix
+internalReference: 282231
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+En los archivos XML, el campo para la categoría global está entregando la información de la categoría global definida en el nivel de categoría y no en el nivel de producto (el nivel de producto debe ser priorizado).
+
+
+##
+
+## Simulación
+
+
+- Utilice un producto con una categoría global definida en el producto, y una categoría global diferente definida en el nivel de categoría;
+- Cree un archivo XML y utilice la Categoría Global archivada;
+- Compruebe el producto en el XML que muestra la categoría global definida en la categoría.
+
+
+
+## Workaround
+
+
+No hay solución.
+
diff --git a/docs/known-issues/es/xml-installment-currency-does-not-apply.md b/docs/known-issues/es/xml-installment-currency-does-not-apply.md
new file mode 100644
index 000000000..c5a61850a
--- /dev/null
+++ b/docs/known-issues/es/xml-installment-currency-does-not-apply.md
@@ -0,0 +1,49 @@
+---
+title: 'XML - No se aplica la moneda a plazos'
+id: 7kPbxbGnpqeqU8XCD576hZ
+status: PUBLISHED
+createdAt: 2024-02-02T19:16:59.053Z
+updatedAt: 2024-07-01T18:49:23.913Z
+publishedAt: 2024-07-01T18:49:23.913Z
+firstPublishedAt: 2024-02-02T19:16:59.992Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: xml-no-se-aplica-la-moneda-a-plazos
+locale: es
+kiStatus: No Fix
+internalReference: 976295
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Cuando se configura una moneda en un XML, se aplica a todos los campos excepto al campo "Cuota".
+
+El campo "Cuota" siempre muestra la moneda como "R$", independientemente de la moneda configurada.
+
+
+
+## Simulación
+
+
+
+1. Cree/Actualice un XML con una moneda diferente a "R$" y habilite el campo Cuota.
+2. 2. Compruebe que todos los campos de precio en el XML devuelven correctamente la moneda, excepto la cuota.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md b/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
new file mode 100644
index 000000000..6465cecaa
--- /dev/null
+++ b/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
@@ -0,0 +1,52 @@
+---
+title: 'Las etiquetas XML <precio> relacionadas no cargan el contenido de los artículos no disponibles'
+id: 7u2WDGV9FJl4fXwfOhRx8N
+status: PUBLISHED
+createdAt: 2024-01-31T19:11:20.119Z
+updatedAt: 2024-01-31T19:11:20.846Z
+publishedAt: 2024-01-31T19:11:20.846Z
+firstPublishedAt: 2024-01-31T19:11:20.846Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: las-etiquetas-xml-precio-relacionadas-no-cargan-el-contenido-de-los-articulos-no-disponibles
+locale: es
+kiStatus: Backlog
+internalReference: 974722
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+La integración XML carga cualquier etiqueta relacionada con el precio, como minPrice, maxPrice, currentPrice, se cargan como una etiqueta de valor nulo (<![CDATA[]]>) cuando el artículo no está disponible y también se establece para mostrar si no está disponible.
+
+
+##
+
+## Simulación
+
+
+1 - Configure un SKU no disponible en su tienda para "mostrar aunque no esté disponible".
+2 - para una integración XML válida config https://myaccountname.myvtex.com/admin/Site/XmlForm.aspx, configure la etiqueta "Disponibilidad" y cualquier etiqueta de disponibilidad para mostrar.
+3 - Utilice una solicitud GET o cargue la URL XML creada en su navegador.
+
+El resultado será un artículo no disponible, aún mostrándose en el XML, pero sin ninguna etiqueta de precio:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/1CzUarsM3O05aG9z5otDZZ1Yg/?name=image.png)
+
+
+
+## Workaround
+
+**
+No existe ninguna solución. La única opción para no integrar artículos sin precio es desactivar la opción "showIfNotAvailable".
+
+
+
+
+
diff --git a/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
new file mode 100644
index 000000000..7c8f4971a
--- /dev/null
+++ b/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
@@ -0,0 +1,49 @@
+---
+title: 'El indicador "Nombre del producto" de XML no funciona correctamente'
+id: 6YDbpRns3LCN02bVKM8aaf
+status: PUBLISHED
+createdAt: 2023-10-26T11:35:14.500Z
+updatedAt: 2023-10-26T11:35:15.285Z
+publishedAt: 2023-10-26T11:35:15.285Z
+firstPublishedAt: 2023-10-26T11:35:15.285Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: el-indicador-nombre-del-producto-de-xml-no-funciona-correctamente
+locale: es
+kiStatus: Backlog
+internalReference: 925965
+---
+
+## Sumario
+
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+</div>
+
+
+Al crear un XML, tenemos dos opciones diferentes para establecer el nombre del producto, en las banderas "Nombre del producto" y "Nombre del producto + Nombre SKU". Sin embargo, la bandera "Nombre del producto" no se tiene en cuenta, y el nombre del producto en el archivo sigue la regla:
+- Si el producto tiene más de un SKU o el nombre del SKU es igual al nombre del producto = se mostrará sólo el Nombre del producto.
+- Si el producto sólo tiene una SKU y el nombre de la SKU no es igual al nombre del producto = se concatenarán los nombres del producto y de la SKU.
+
+
+
+## Simulación
+
+
+
+1. Compruebe si tiene en el catálogo productos que coincidan con la descripción anterior
+2. Crea un XML seleccionando la bandera "Nombre del producto"
+3. Ver que para los productos con un solo SKU, el nombre del producto será concatenado con el nombre SKU
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/es/xmls-returning-500-error.md b/docs/known-issues/es/xmls-returning-500-error.md
index b85594ed3..d0ed289c8 100644
--- a/docs/known-issues/es/xmls-returning-500-error.md
+++ b/docs/known-issues/es/xmls-returning-500-error.md
@@ -1,16 +1,16 @@
 ---
-title: 'Los XMLs devuelven el error 500'
+title: 'Los XML devuelven un error 500'
 id: 6L48cBRaKQmjAOnNza3aNA
 status: PUBLISHED
 createdAt: 2022-06-07T17:53:45.884Z
-updatedAt: 2022-11-25T22:10:40.212Z
-publishedAt: 2022-11-25T22:10:40.212Z
+updatedAt: 2024-05-23T18:54:18.843Z
+publishedAt: 2024-05-23T18:54:18.843Z
 firstPublishedAt: 2022-06-07T17:53:46.260Z
 contentType: knownIssue
 productTeam: Portal
 author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
-slug: los-xmls-devuelven-el-error-500
+slug: los-xml-devuelven-un-error-500
 locale: es
 kiStatus: Backlog
 internalReference: 268042
@@ -23,14 +23,17 @@ internalReference: 268042
 </div>
 
 
-Eventualmente, el XML puede devolver un error 500, esto sucede principalmente en archivos XML grandes.
+Eventualmente, el XML puede devolver un error 500, ocurre principalmente en archivos XML grandes.
 
 
 
+##
+
 ## Simulación
 
 
-Intenta cargar un archivo XML grande.
+Intente cargar un archivo XML grande.
+
 
 
 
@@ -41,3 +44,7 @@ Intenta cargar un archivo XML grande.
 - Intentar recargar el XML suele resolver el problema;
 - Utiliza más de un XML.
 
+
+
+
+
diff --git a/docs/known-issues/pt/.md b/docs/known-issues/pt/.md
index e562409e3..edb9412da 100644
--- a/docs/known-issues/pt/.md
+++ b/docs/known-issues/pt/.md
@@ -1,16 +1,16 @@
 ---
-title: 'Especificação duplicada ou errada na página do produto'
-id: 602UddMuqWmq2emQUymsyI
+title: 'Entrega agendada aparece valor "Grátis" enquanto janela de entrega não é selecionada'
+id: 6KUkwO1vTq04IoCKgywKQs
 status: DRAFT
-createdAt: 2017-06-05T20:01:41.057Z
-updatedAt: 2019-12-31T15:17:09.475Z
+createdAt: 2018-11-30T19:23:41.543Z
+updatedAt: 2019-12-31T15:16:41.013Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
-productTeam: Marketing & Merchandising
+productTeam: Post-purchase
 author: 
 tag: 
-slug: especificacao-duplicada-ou-errada-na-pagina-do-produto
+slug: entrega-agendada-aparece-valor-gratis-enquanto-janela-de-entrega-nao-e
 locale: pt
 kiStatus: 
 internalReference: 
@@ -18,13 +18,17 @@ internalReference:
 
 ## Sumário
 
-A exibição de campos de especificações incorretos pode ocorrer quando um produto é alterado de categoria. Isto, pois os campos de especificações da categoria anterior permanecem associados ao produto, mesmo após a alteração.
+Os valores de frete para a entrega agendada são cadastrados nas janelas de entrega, ou seja, enquanto a data e hora de entrega não for selecionada, não é possível informar exatamente qual o valor de frete. Porém,  
 
 ## Simulação
 
 
-1. Acesse a edição de um produto
-2. Altere a categoria do produto
+
+## Workaround
+
+
+
+Altere a categoria do produto
 
 Se a categoria anterior tiver especificações, pode ser que permaneçam aparecendo na página de produto.
 
diff --git a/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md b/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md
new file mode 100644
index 000000000..2e9290d1f
--- /dev/null
+++ b/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md
@@ -0,0 +1,47 @@
+---
+title: 'Erro 403 para todos os URLs que contêm develop-'
+id: X6JDmLhD0StgHPGXJd9cZ
+status: PUBLISHED
+createdAt: 2024-02-01T13:46:53.024Z
+updatedAt: 2024-02-01T13:46:54.008Z
+publishedAt: 2024-02-01T13:46:54.008Z
+firstPublishedAt: 2024-02-01T13:46:54.008Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: erro-403-para-todos-os-urls-que-contem-develop
+locale: pt
+kiStatus: Backlog
+internalReference: 975182
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que um URL possa conter qualquer palavra sem gerar um erro, mas a palavra "**develop "** seguida pelo caractere "**-**" gera um erro 403 automático.
+Por exemplo, um produto com o link de texto `how-to-develot-a-culture-of-custumer-centricity` exibirá um erro 403, pois contém a string "develop-".
+
+## Simulação
+
+
+
+1. Coloque a string "develop-" em um link de texto
+2. Carregue o produto
+3. Veja o erro 403
+
+
+
+## Workaround
+
+
+Não usar a string "develop-"
+
+
+
+
+
diff --git a/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
new file mode 100644
index 000000000..6b71a7142
--- /dev/null
+++ b/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -0,0 +1,45 @@
+---
+title: 'Uma SKU pode estar ativa e ter o sinalizador "ativar se possível" desmarcado'
+id: 5uXQ65flkoEbYeLkNSw4ig
+status: PUBLISHED
+createdAt: 2023-11-07T11:01:20.612Z
+updatedAt: 2023-11-07T11:01:21.419Z
+publishedAt: 2023-11-07T11:01:21.419Z
+firstPublishedAt: 2023-11-07T11:01:21.419Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: uma-sku-pode-estar-ativa-e-ter-o-sinalizador-ativar-se-possivel-desmarcado
+locale: pt
+kiStatus: Backlog
+internalReference: 931324
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que uma SKU ativa tenha o sinalizador "ativar se possível" marcado; no entanto, esse nem sempre é o caso.
+Uma SKU pode estar ativa e ter o sinalizador "ativar se possível" desmarcado.
+
+## Simulação
+
+
+Abra o administrador da SKU
+Veja no formulário que a SKU está ativa e que o sinalizador "ativar se possível" está desmarcado
+
+
+
+## Workaround
+
+
+Salvar a SKU diretamente por meio do administrador
+
+
+
+
+
diff --git a/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md b/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
new file mode 100644
index 000000000..0e0034929
--- /dev/null
+++ b/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
@@ -0,0 +1,46 @@
+---
+title: 'Um valor de especificação de produto válido pode ser retornado em branco no administrador do catálogo'
+id: 46IZtoT2nSKE71g2Tj0m8y
+status: PUBLISHED
+createdAt: 2024-01-16T00:28:14.900Z
+updatedAt: 2024-01-16T00:28:15.482Z
+publishedAt: 2024-01-16T00:28:15.482Z
+firstPublishedAt: 2024-01-16T00:28:15.482Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: um-valor-de-especificacao-de-produto-valido-pode-ser-retornado-em-branco-no-administrador-do-catalogo
+locale: pt
+kiStatus: Backlog
+internalReference: 966499
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que o administrador de especificações do produto sempre apresente os valores corretos para as especificações de um produto. No entanto, isso pode não ser sempre o caso.
+O valor da especificação pode ser retornado em branco no administrador, como se não tivesse nenhum valor associado.
+Além do problema de visualização, se o usuário salvar o produto usando o administrador do produto, o valor da especificação em branco substituirá o valor original
+
+## Simulação
+
+
+Abra um formulário de especificação de produto e compare o valor mostrado no administrador com o valor retornado pela API.
+
+
+
+
+## Workaround
+
+
+Gerenciar especificações de produtos via API
+
+
+
+
+
diff --git a/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md b/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
new file mode 100644
index 000000000..6b2aa814e
--- /dev/null
+++ b/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
@@ -0,0 +1,43 @@
+---
+title: 'O aplicativo AB Tester mostra informações mal calculadas para sessões e conversão'
+id: 2Sgvlldl0kyDcWBVi4KMzg
+status: PUBLISHED
+createdAt: 2023-07-20T12:42:25.435Z
+updatedAt: 2024-07-01T18:49:08.433Z
+publishedAt: 2024-07-01T18:49:08.433Z
+firstPublishedAt: 2023-07-20T12:42:26.335Z
+contentType: knownIssue
+productTeam: Cloud Services
+author: 2mXZkbi0oi061KicTExNjo
+tag: Cloud Services
+slug: o-aplicativo-ab-tester-mostra-informacoes-mal-calculadas-para-sessoes-e-conversao
+locale: pt
+kiStatus: No Fix
+internalReference: 865727
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O aplicativo AB Tester mostra informações mal calculadas para sessões e conversão ao executar testes, causando interpretação indesejada dos resultados. A funcionalidade de divisão do espaço de trabalho ainda funciona conforme o esperado.
+
+## Simulação
+
+
+
+- Crie um teste A/B;
+- Deixe o teste ser executado por algum tempo;
+- Verifique os valores de sessões e conversões; ele mostrará informações mal calculadas
+
+## Workaround
+
+
+Use uma ferramenta de análise externa para analisar os dados.
+
+
+
+
diff --git a/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md b/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
index a7bbc241e..c5e44b0a0 100644
--- a/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
+++ b/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
@@ -1,16 +1,16 @@
 ---
-title: 'Ativar serviço na importação (SkuVincularValorServico.aspx) não funciona'
+title: 'Ativar serviço na importação (SkuVincularValorServico.aspx) não está funcionando'
 id: 1gM3bYz0IX4ozLrIkWIicb
 status: PUBLISHED
 createdAt: 2022-02-25T14:56:50.052Z
-updatedAt: 2022-11-25T21:44:43.603Z
-publishedAt: 2022-11-25T21:44:43.603Z
+updatedAt: 2024-05-10T14:24:13.156Z
+publishedAt: 2024-05-10T14:24:13.156Z
 firstPublishedAt: 2022-02-25T14:56:50.569Z
 contentType: knownIssue
 productTeam: Catalog
 author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
-slug: ativar-servico-na-importacao-skuvincularvalorservicoaspx-nao-funciona
+slug: ativar-servico-na-importacao-skuvincularvalorservicoaspx-nao-esta-funcionando
 locale: pt
 kiStatus: Backlog
 internalReference: 339894
@@ -23,12 +23,31 @@ internalReference: 339894
 </div>
 
 
+Atualmente, na usabilidade de importação do SkuVincularValorServico.aspx, ao tentar alterar os serviços que saíram anteriormente de inativos para ativos, os valores não são alterados. A interface do usuário avisa que os valores foram alterados, mas nada acontece de fato.
+
+(O oposto não é verdadeiro, a alteração de ativo para inativo funciona).
 
 ## Simulação
 
 
+1) Acesse a interface do usuário https://account.myvtex.com/admin/Site/SkuVincularValorServico.aspx e altere as linhas da planilha anexa de 0 para 1 e vice-versa:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ladK39V5My6gjGixeHuNTaV2b/?name=inline-1801216200.png)
+
+2) Verifique os efeitos finais na SKU cujos valores você alterou:
+ ![](https://vtexhelp.zendesk.com/attachments/token/znYEzQhMevPcRVYKlBQYa73fF/?name=inline1216426643.png)
+
+Você poderá defini-los como inativos, mas não como ativos. A interface de importação avisa que as alterações foram feitas:
+ ![](https://vtexhelp.zendesk.com/attachments/token/6iKARGtVqTbKaL0vY9s7XPvt6/?name=inline2110004305.png)
+
+Nenhum valor é realmente alterado no banco de dados da conta fornecida
 
 ## Workaround
 
 
+Usar a interface do usuário para fazer alterações de inativo -->> ativo e/ou nossas APIs de serviço:
+https://developers.vtex.com/vtex-developer-docs/reference/catalog-api-sku-service
+
+
+
 
diff --git a/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
index c33f22ff1..825fc6eef 100644
--- a/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
@@ -30,5 +30,5 @@ Criar um novo dicionário no Módulo CMS que não possua nenhum Host previamente
 
 Acesse o módulo CMS, clique nos botões lupa e limpar em sequência e o botão adicionar novo host será desbloqueado.
 
-![PT - Criar dicionário não disponibiliza opção de "Add"](https://images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
+![PT - Criar dicionário não disponibiliza opção de "Add"](//images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
 
diff --git a/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md b/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md
index 748e0b631..7794467d3 100644
--- a/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md
+++ b/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md
@@ -3,8 +3,8 @@ title: 'A adição de um novo endereço no endereço da fatura retorna resultado
 id: 43eiz4YORQv1u4yDahZdvC
 status: PUBLISHED
 createdAt: 2023-02-07T13:15:36.832Z
-updatedAt: 2023-02-07T13:15:52.825Z
-publishedAt: 2023-02-07T13:15:52.825Z
+updatedAt: 2024-07-01T18:48:46.296Z
+publishedAt: 2024-07-01T18:48:46.296Z
 firstPublishedAt: 2023-02-07T13:15:37.293Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-adicao-de-um-novo-endereco-no-endereco-da-fatura-retorna-resultados-api-nulos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 748668
 ---
 
diff --git a/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md b/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
new file mode 100644
index 000000000..e6bcb606d
--- /dev/null
+++ b/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
@@ -0,0 +1,50 @@
+---
+title: 'O Formulário de endereço não é exibido quando o comprador opta por inserir um novo endereço'
+id: 4HOP82OvC4smfjPFT8aXJA
+status: PUBLISHED
+createdAt: 2024-07-05T21:16:00.552Z
+updatedAt: 2024-07-05T21:16:01.340Z
+publishedAt: 2024-07-05T21:16:01.340Z
+firstPublishedAt: 2024-07-05T21:16:01.340Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-formulario-de-endereco-nao-e-exibido-quando-o-comprador-opta-por-inserir-um-novo-endereco
+locale: pt
+kiStatus: Backlog
+internalReference: 1061637
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Às vezes, quando um comprador identificado tenta adicionar um novo endereço na etapa de envio do checkout, uma mensagem solicitando autenticação é solicitada, mas o formulário de endereço não é exibido e não pode ser preenchido.
+
+## Simulação
+
+
+
+- Vá para o checkout, identifique-se como um comprador com um perfil completo e prossiga para a etapa de envio;
+- Escolha a opção de entrega em um novo endereço;
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/TFgWp6jleflU5LlPZ3rd4KcTQ/?name=image.png)
+
+
+- Digite o código postal e uma mensagem solicitando autenticação será exibida.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/iTNky5H9cDijZ00prjAwQv24h/?name=image.png
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md b/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md
index a789583dc..24a8cb364 100644
--- a/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md
+++ b/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md
@@ -3,8 +3,8 @@ title: 'O fluxo de revisão de endereço está removendo informações essenciai
 id: 416pFRk6KsWIfgPr8pzWii
 status: PUBLISHED
 createdAt: 2022-08-11T18:33:49.548Z
-updatedAt: 2022-11-25T21:50:56.733Z
-publishedAt: 2022-11-25T21:50:56.733Z
+updatedAt: 2024-02-16T20:23:20.195Z
+publishedAt: 2024-02-16T20:23:20.195Z
 firstPublishedAt: 2022-08-11T18:33:50.049Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-fluxo-de-revisao-de-endereco-esta-removendo-informacoes-essenciais-de-endereco
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 618756
 ---
 
diff --git a/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
new file mode 100644
index 000000000..7faf8d91e
--- /dev/null
+++ b/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -0,0 +1,46 @@
+---
+title: 'Os endereços são exibidos no Checkout quando o comprador tem a permissão "Can add shipping" (Pode adicionar frete)'
+id: 2ssiTryGJ6kGoZWxWkGnFF
+status: PUBLISHED
+createdAt: 2024-05-21T22:03:55.172Z
+updatedAt: 2024-05-21T22:03:56.435Z
+publishedAt: 2024-05-21T22:03:56.435Z
+firstPublishedAt: 2024-05-21T22:03:56.435Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: os-enderecos-sao-exibidos-no-checkout-quando-o-comprador-tem-a-permissao-can-add-shipping-pode-adicionar-frete
+locale: pt
+kiStatus: Backlog
+internalReference: 1037067
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma função tem a permissão "Pode adicionar envio" nas configurações de checkout B2B e um comprador tem endereços registrados no sistema de perfil, clicar em "Entregar em outro endereço" na etapa de envio e clicar em "Voltar à lista de endereços" mostra os endereços do sistema de perfil.
+
+## Simulação
+
+
+
+- Adicione a permissão "Can add shipping" (Pode adicionar remessa) nas B2B Checkout Settings (Configurações de checkout B2B) via administrador a uma função;
+- Adicione a função a um comprador;
+- Faça login na loja e monte um carrinho;
+- Depois de acessar o checkout, clique em "Change shipping options" (Alterar opções de envio)
+- Clique em "Deliver to another address" (Entregar em outro endereço) na etapa de envio e clique em "Back to address list" (Voltar à lista de endereços),
+- Diferentes endereços do centro de custo estão no carrinho
+
+## Workaround
+
+
+Ative a opção Salvar dados do usuário para que nenhum endereço seja adicionado ao sistema de perfil.
+
+
+
+
diff --git a/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md b/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
new file mode 100644
index 000000000..a933a9e1f
--- /dev/null
+++ b/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
@@ -0,0 +1,43 @@
+---
+title: 'Os endereços do sistema de perfil são exibidos quando se faz passar por uma pessoa usando a VTEX Telemarketing'
+id: 5fFacgD8grxKqJoOO2fwU7
+status: PUBLISHED
+createdAt: 2023-07-12T13:19:48.090Z
+updatedAt: 2023-08-31T19:38:04.369Z
+publishedAt: 2023-08-31T19:38:04.369Z
+firstPublishedAt: 2023-07-12T13:19:48.807Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: os-enderecos-do-sistema-de-perfil-sao-exibidos-quando-se-faz-passar-por-uma-pessoa-usando-a-vtex-telemarketing
+locale: pt
+kiStatus: No Fix
+internalReference: 860375
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o comprador tem endereços registrados no Profile System e se faz passar por ele usando a VTEX Telemarketing, os endereços do Profile System e das Organizações são mostrados
+
+## Simulação
+
+
+
+- Faça-se passar por um comprador que tenha endereços registrados no Profile System;
+- Monte um carrinho e vá para Shipping;
+- Selecione um endereço; o componente será atualizado e mostrará todos os endereços do Profile System e das organizações
+
+## Workaround
+
+
+
+- Use a função de representação de organizações B2B.
+
+
+
diff --git a/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
new file mode 100644
index 000000000..c79005de7
--- /dev/null
+++ b/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -0,0 +1,54 @@
+---
+title: 'A incompatibilidade de AddressId causa o erro "endereço inválido para um item"'
+id: 5bSac85eHb9NmrOhcTjHNw
+status: PUBLISHED
+createdAt: 2024-03-01T19:28:52.074Z
+updatedAt: 2024-03-01T19:28:52.875Z
+publishedAt: 2024-03-01T19:28:52.875Z
+firstPublishedAt: 2024-03-01T19:28:52.875Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-incompatibilidade-de-addressid-causa-o-erro-endereco-invalido-para-um-item
+locale: pt
+kiStatus: Backlog
+internalReference: 992503
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O anexo de carrinho `shippingData` suporta o campo `addressId` em alguns objetos diferentes: `logisticsInfo`, `address` e `selectedAddresses`.
+O campo `addressId` também é mantido nos endereços salvos do usuário, mantidos na entidade AD do Master Data.
+
+Ao fazer um pedido, a API de checkout compara o endereço de entrega selecionado no formulário de pedido com os endereços disponíveis no perfil do usuário.
+Se ocorrer uma correspondência, o `addressId` em `address` e `selectedAddresses` do formulário de pedido será substituído pelo valor existente no perfil do usuário.
+
+No entanto, em um ponto posterior das validações da API, ela também comparará esse `addressId` com o do objeto `logisticsInfo`.
+Como o `logisticsInfo` não foi substituído pelo processo mencionado anteriormente, eles podem não corresponder, e essa validação posterior falhará.
+Isso aciona a mensagem "**endereço inválido para um item**" / "endereço inválido para um item", impedindo que a compra seja concluída.
+
+
+## Simulação
+
+
+
+- Salve dois endereços diferentes no perfil de um usuário e anote seus valores `addressId`.
+- Monte uma solicitação Place Order. Use um de seus endereços criados na etapa anterior, mas use o `addressId` do outro.
+- Envie a solicitação. A resposta conterá a mensagem de erro "endereço inválido para um item"
+
+## Workaround
+
+
+Ao enviar a solicitação Place Order com um endereço salvo anteriormente, verifique se o valor usado para `addressId` corresponde aos dados reais do endereço.
+Como alternativa, você também pode omitir o `addressId` da solicitação.
+
+
+
+
+
diff --git a/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md b/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
index 3a7937d32..f112e35e9 100644
--- a/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
+++ b/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
@@ -3,8 +3,8 @@ title: 'Ajuste a consulta de envio quando o pedido tem mais de um produto - Cent
 id: 5VsGJar6FBHbGi4OZpxvbk
 status: PUBLISHED
 createdAt: 2022-06-15T19:08:37.828Z
-updatedAt: 2022-11-25T21:56:35.720Z
-publishedAt: 2022-11-25T21:56:35.720Z
+updatedAt: 2024-02-16T20:25:35.893Z
+publishedAt: 2024-02-16T20:25:35.893Z
 firstPublishedAt: 2022-06-15T19:08:38.488Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: ajuste-a-consulta-de-envio-quando-o-pedido-tem-mais-de-um-produto-centauro
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 599380
 ---
 
diff --git a/docs/known-issues/pt/admin-collection-brand-list-timeout.md b/docs/known-issues/pt/admin-collection-brand-list-timeout.md
index 05f5ffcc9..b034363ec 100644
--- a/docs/known-issues/pt/admin-collection-brand-list-timeout.md
+++ b/docs/known-issues/pt/admin-collection-brand-list-timeout.md
@@ -3,8 +3,8 @@ title: 'Timeout da lista de marcas de coleção no Admin'
 id: 4de4lqAIhr9mU77EPAbvq1
 status: PUBLISHED
 createdAt: 2022-08-17T15:58:26.950Z
-updatedAt: 2022-11-25T21:43:44.331Z
-publishedAt: 2022-11-25T21:43:44.331Z
+updatedAt: 2024-07-01T18:48:37.335Z
+publishedAt: 2024-07-01T18:48:37.335Z
 firstPublishedAt: 2022-08-17T15:58:27.573Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: timeout-da-lista-de-marcas-de-colecao-no-admin
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639905
 ---
 
diff --git a/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
new file mode 100644
index 000000000..757d663cd
--- /dev/null
+++ b/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -0,0 +1,47 @@
+---
+title: '[Admin] A Pesquisa global não reconhece os "Itens do menu de perfil"'
+id: 4AZiu9NXouL6b8z5EHJIWK
+status: PUBLISHED
+createdAt: 2024-01-22T17:09:55.423Z
+updatedAt: 2024-01-22T17:09:55.944Z
+publishedAt: 2024-01-22T17:09:55.944Z
+firstPublishedAt: 2024-01-22T17:09:55.944Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-a-pesquisa-global-nao-reconhece-os-itens-do-menu-de-perfil
+locale: pt
+kiStatus: Backlog
+internalReference: 969645
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A Pesquisa global não reconhece "Itens do menu de perfil"
+
+## Simulação
+
+
+Em alguns casos, a pesquisa não retorna nenhum resultado.
+Por exemplo: "Usuários" "Autenticação"
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/QwUkKwavO6WM00STA32BVwyvn/?name=image.png)
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/weT1QdMEqTne83NxeJRN1ilFm/?name=image.png
+
+## Workaround
+
+
+Use o menu lateral para acessar esses módulos
+
+
+
+
+
diff --git a/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index 06e156e3a..7c748d4a4 100644
--- a/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -31,7 +31,7 @@ Isso ocorria porque o número `1` tinha sido configurado como padrão, mesmo qua
 
 Acesse seu **Admin VTEX > Início > Como melhorar > Catálogo**. Se a seção indicar que há `1` problema encontrado, ao clicar em `Produtos populares sem estoque`, você será redirecionado para a página do Catálogo.
 
-![Como melhorar PT](https://images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/0c7b4d56e4f469c92c9cb4568e1b2268/Como_melhorar_PT.png)
+![Como melhorar PT](//images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/0c7b4d56e4f469c92c9cb4568e1b2268/Como_melhorar_PT.png)
 
 ## Workaround
 
@@ -39,5 +39,5 @@ Não é necessário que o usuário realize nenhuma ação, pois já corrigimos o
 
 `Não encontramos problemas no seu catálogo.`
 
-![Como melhorar fixed PT](https://images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/9db429271ca62c42c8b4fc9fa3f5fe37/Como_melhorar_fixed_PT.png)
+![Como melhorar fixed PT](//images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/9db429271ca62c42c8b4fc9fa3f5fe37/Como_melhorar_fixed_PT.png)
 
diff --git a/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md b/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
index 3b5e6a680..740e274a5 100644
--- a/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
+++ b/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
@@ -3,8 +3,8 @@ title: 'Admin está mostrando a extensão da imagem como .jpg mesmo quando a ima
 id: 1nVCuVnNjT7e1E9Cy0Veer
 status: PUBLISHED
 createdAt: 2022-02-02T18:48:49.607Z
-updatedAt: 2022-11-25T21:48:51.993Z
-publishedAt: 2022-11-25T21:48:51.993Z
+updatedAt: 2024-02-16T20:26:18.176Z
+publishedAt: 2024-02-16T20:26:18.176Z
 firstPublishedAt: 2022-02-02T18:48:49.929Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: admin-esta-mostrando-a-extensao-da-imagem-como-jpg-mesmo-quando-a-imagem-e-png
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 516269
 ---
 
diff --git a/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md b/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
new file mode 100644
index 000000000..281c7f3f3
--- /dev/null
+++ b/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
@@ -0,0 +1,51 @@
+---
+title: 'Módulo [Admin] Master Data, o mecanismo de pesquisa do administrador os redireciona para o URL errado.'
+id: NPUIMi5uS5ngHZBeemIMe
+status: PUBLISHED
+createdAt: 2023-08-28T18:39:23.578Z
+updatedAt: 2023-09-06T15:03:32.872Z
+publishedAt: 2023-09-06T15:03:32.872Z
+firstPublishedAt: 2023-08-28T18:39:24.558Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: modulo-admin-master-data-o-mecanismo-de-pesquisa-do-administrador-os-redireciona-para-o-url-errado
+locale: pt
+kiStatus: Fixed
+internalReference: 889045
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No módulo Master Data, o mecanismo de pesquisa do administrador redireciona para o URL errado.
+
+## Simulação
+
+
+
+Etapas:
+Admin > Pesquisar > Dados mestre >
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/DhvSEUDDmPjgGdIlWV4PJvh0A/?name=image.png)
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/9nUmLbZLPdCzBgvNziUi1WCvw/?name=image.png
+
+## Workaround
+
+
+
+é possível acessá-lo normalmente usando o menu lateral:
+Admin > Frente de loja > Dados mestre
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/59KwJCdK91ol1f4edT4hjNBHQ/?name=image.png)
+
+
+
+
+
diff --git a/docs/known-issues/pt/admin-review-global-search.md b/docs/known-issues/pt/admin-review-global-search.md
new file mode 100644
index 000000000..b33d90076
--- /dev/null
+++ b/docs/known-issues/pt/admin-review-global-search.md
@@ -0,0 +1,44 @@
+---
+title: '[admin] revisar pesquisa global'
+id: 1r83M4ug7WVoF1gb22NMh0
+status: PUBLISHED
+createdAt: 2023-08-29T20:01:07.327Z
+updatedAt: 2023-08-29T20:01:08.251Z
+publishedAt: 2023-08-29T20:01:08.251Z
+firstPublishedAt: 2023-08-29T20:01:08.251Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: admin-revisar-pesquisa-global
+locale: pt
+kiStatus: Backlog
+internalReference: 889993
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A pesquisa global não está encontrando informações sobre "usuários"
+
+## Simulação
+
+
+Etapas:
+Administrador > pesquisa global > Dados mestre > Usuário
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/bT7SSj1ApVwcvNCxCwtOB8yJj/?name=image.png
+
+## Workaround
+
+
+é possível acessar diretamente pelo URL .com/admin/users
+
+
+
+
+
diff --git a/docs/known-issues/pt/admin-timeout.md b/docs/known-issues/pt/admin-timeout.md
new file mode 100644
index 000000000..5c3509ff6
--- /dev/null
+++ b/docs/known-issues/pt/admin-timeout.md
@@ -0,0 +1,48 @@
+---
+title: 'Tempo limite do administrador'
+id: 6Kp2viMZSnmGucJnciDNKx
+status: PUBLISHED
+createdAt: 2024-06-17T18:07:48.342Z
+updatedAt: 2024-06-17T18:07:49.170Z
+publishedAt: 2024-06-17T18:07:49.170Z
+firstPublishedAt: 2024-06-17T18:07:49.170Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: tempo-limite-do-administrador
+locale: pt
+kiStatus: Backlog
+internalReference: 1051070
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O aplicativo de mensagens está recebendo um erro de tempo limite aleatoriamente e algumas páginas de administração podem precisar de uma atualização para funcionar corretamente.
+
+Isso pode estar relacionado a consultas GraphQL. Normalmente, você verá erros na rota `/meta` ou um timeout do aplicativo de mensagens relacionado à consulta `translateWithDeps`.
+
+## Simulação
+
+
+Tente acessar algumas páginas no administrador de uma conta e, aleatoriamente, essa página pode receber o erro abaixo:
+ ![](https://vtexhelp.zendesk.com/attachments/token/zNzGxtaY5SszSHGFiKRMiCXda/?name=image.png)
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/KqbIgf2qqZIAdpYgXJcaiu5FJ/?name=image.png)
+
+Quando você atualizar a página, tudo deverá voltar ao norma
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md b/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md
index a4de90741..5921ec459 100644
--- a/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md
+++ b/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md
@@ -3,8 +3,8 @@ title: 'Endereço sem país perturbando o pedidoMudanças na forma'
 id: 3LfFmUaetyqZij8MCBJtcY
 status: PUBLISHED
 createdAt: 2022-05-16T19:58:42.987Z
-updatedAt: 2022-11-25T21:52:11.051Z
-publishedAt: 2022-11-25T21:52:11.051Z
+updatedAt: 2024-02-16T20:23:23.949Z
+publishedAt: 2024-02-16T20:23:23.949Z
 firstPublishedAt: 2022-05-16T19:58:43.429Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: endereco-sem-pais-perturbando-o-pedidomudancas-na-forma
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 579814
 ---
 
diff --git a/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md b/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md
new file mode 100644
index 000000000..ae78d1357
--- /dev/null
+++ b/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md
@@ -0,0 +1,52 @@
+---
+title: 'Solicitação dupla do Adyen 3DS2 gera recusa de autorização de pagamento'
+id: 3yR8LzaUjclJ22PkAymvoe
+status: PUBLISHED
+createdAt: 2023-09-20T13:09:29.771Z
+updatedAt: 2023-09-20T13:09:30.507Z
+publishedAt: 2023-09-20T13:09:30.507Z
+firstPublishedAt: 2023-09-20T13:09:30.507Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: solicitacao-dupla-do-adyen-3ds2-gera-recusa-de-autorizacao-de-pagamento
+locale: pt
+kiStatus: Backlog
+internalReference: 884154
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a solicitação 3DS2 da Adyen é enviada duas vezes, ela obtém um erro na resposta e o pagamento é automaticamente negado.
+
+Resposta de autorização:
+
+`{"status":409, "errorCode": "704", "message": "request already processed or in progress", "errorType": "validation"}`
+
+Seguindo a mensagem:
+
+`Resposta não esperada [].`
+
+Esse é um problema quando o pagamento é realmente autorizado no lado da Adyen, mas como não há liquidação do nosso lado, não podemos enviar uma solicitação de reembolso.
+
+## Simulação
+
+
+Não conseguimos reproduzir esse cenário ou encontrar um padrão até o momento.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md b/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
new file mode 100644
index 000000000..b53be15fc
--- /dev/null
+++ b/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
@@ -0,0 +1,45 @@
+---
+title: 'A AdyenV1 não envia corretamente o paymentMethod.type para a Amex ao usar o Apple Pay.'
+id: UCCG0Lwe3U6dO7MHwFebO
+status: PUBLISHED
+createdAt: 2023-10-17T14:58:27.621Z
+updatedAt: 2023-10-17T14:58:28.348Z
+publishedAt: 2023-10-17T14:58:28.348Z
+firstPublishedAt: 2023-10-17T14:58:28.348Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: a-adyenv1-nao-envia-corretamente-o-paymentmethodtype-para-a-amex-ao-usar-o-apple-pay
+locale: pt
+kiStatus: Backlog
+internalReference: 920563
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Embora o Apple Pay permita que o usuário faça um pedido usando um cartão Amex, nosso conector legado AdyenV1 não é compatível com essa marca.
+
+Nos registros de interação, nota-se que o campo` paymentMethod.type` é preenchido com "scheme", o que resulta em um erro da Adyen.
+
+## Simulação
+
+
+Tentativa de fazer um pedido usando o Apple Pay com um cartão Amex. A transação será negada
+
+
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md b/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
index 87fe08b9d..23605656b 100644
--- a/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
+++ b/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
@@ -3,8 +3,8 @@ title: 'Alerta para preencher a seleção de entrega programada aparece apenas u
 id: f668KUV24RqlpUvDvoIEm
 status: PUBLISHED
 createdAt: 2022-04-25T14:49:29.983Z
-updatedAt: 2022-11-25T21:51:08.681Z
-publishedAt: 2022-11-25T21:51:08.681Z
+updatedAt: 2024-02-16T20:26:02.010Z
+publishedAt: 2024-02-16T20:26:02.010Z
 firstPublishedAt: 2022-04-25T14:49:30.465Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: alerta-para-preencher-a-selecao-de-entrega-programada-aparece-apenas-uma-vez
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 565982
 ---
 
diff --git a/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index e58d81f2a..a3088d15a 100644
--- a/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -3,7 +3,7 @@ title: 'ALT attribute not showing in <vtex.cmc:ProductImage zoom="on" />'
 id: 4P1Eys9Q2WFddrMLQVDvM9
 status: DRAFT
 createdAt: 2022-02-17T13:08:53.295Z
-updatedAt: 2022-03-18T15:38:31.951Z
+updatedAt: 2024-02-16T20:26:26.971Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 526563
 ---
 
diff --git a/docs/known-issues/pt/amazon-category-implementation.md b/docs/known-issues/pt/amazon-category-implementation.md
index c8ca94e55..04d73f369 100644
--- a/docs/known-issues/pt/amazon-category-implementation.md
+++ b/docs/known-issues/pt/amazon-category-implementation.md
@@ -3,8 +3,8 @@ title: 'Implementação da categoria Amazon'
 id: 5drX2V0avfk1X2llMyTlK1
 status: PUBLISHED
 createdAt: 2022-03-25T11:33:04.920Z
-updatedAt: 2022-12-02T18:00:24.056Z
-publishedAt: 2022-12-02T18:00:24.056Z
+updatedAt: 2024-02-16T20:24:37.027Z
+publishedAt: 2024-02-16T20:24:37.027Z
 firstPublishedAt: 2022-03-25T11:33:15.226Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: implementacao-da-categoria-amazon
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 549924
 ---
 
diff --git a/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md b/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
new file mode 100644
index 000000000..39a868b09
--- /dev/null
+++ b/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
@@ -0,0 +1,49 @@
+---
+title: '[Amazon] Código de erro 13013 ao enviar um produto para o Amazon marketplace'
+id: 5bmPQ4Jzi8HvoDoTaDFv9b
+status: PUBLISHED
+createdAt: 2023-10-27T11:24:52.357Z
+updatedAt: 2023-12-18T17:35:20.302Z
+publishedAt: 2023-12-18T17:35:20.302Z
+firstPublishedAt: 2023-10-27T11:24:53.258Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: amazon-codigo-de-erro-13013-ao-enviar-um-produto-para-o-amazon-marketplace
+locale: pt
+kiStatus: Fixed
+internalReference: 926656
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema ao tentar exportar produtos para o Amazon Marketplace. Em alguns casos, a própria Amazon retorna um erro 13013, mas o erro às vezes não é registrado no menu Bridge, e alguns produtos permanecem com status de sucesso, mas quando realmente apresentam o erro abaixo
+
+
+    "code" (código): "13013", "message": "Não há registro do código SKU correspondente a esta atualização em sua conta. Isso geralmente ocorre quando há outros problemas com o código SKU.", "severity": "ERRO",
+
+
+## Simulação
+
+
+
+Dentro do menu de produtos da ponte, você pode ver um erro, mostrando o código de erro 13013, ou qualquer outra mensagem, mas ao verificar o Portal da Amazon, a SKU pode não ser exportada para a Amazon.
+
+
+
+## Workaround
+
+
+Existe uma solução alternativa para esse erro? Se sim, descreva-a aqui. Caso contrário, escreva "N/A" ou "Não há nenhuma solução alternativa disponível". Não remova esta seção se não houver solução alternativa, por favor.
+
+
+
+
+
diff --git a/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md b/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
new file mode 100644
index 000000000..1f1a6f845
--- /dev/null
+++ b/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
@@ -0,0 +1,48 @@
+---
+title: '[Amazon] Erro no fluxo de atualização: o sku não está sendo registrado na ponte'
+id: 1oBkaT6GWZfhB4t2Qpn6c0
+status: PUBLISHED
+createdAt: 2024-02-27T19:40:49.825Z
+updatedAt: 2024-02-27T19:40:50.483Z
+publishedAt: 2024-02-27T19:40:50.483Z
+firstPublishedAt: 2024-02-27T19:40:50.483Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: amazon-erro-no-fluxo-de-atualizacao-o-sku-nao-esta-sendo-registrado-na-ponte
+locale: pt
+kiStatus: Backlog
+internalReference: 990197
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Erro no fluxo de atualização: o sku não está sendo registrado na ponte
+
+**Marketplace:** Amazon
+**Causa raiz:** Produto
+
+
+1. não acontece com todos os skus;
+
+## Simulação
+
+
+Admin > Marketplace > Produtos > Amazon
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/l7i4mRjrhA0eo5BWd92YCS46m/?name=image.png
+
+## Workaround
+
+
+Reprocessar SKU
+
+
+
+
diff --git a/docs/known-issues/pt/amazon-global-category-not-working.md b/docs/known-issues/pt/amazon-global-category-not-working.md
index 3194e5b1b..b03272951 100644
--- a/docs/known-issues/pt/amazon-global-category-not-working.md
+++ b/docs/known-issues/pt/amazon-global-category-not-working.md
@@ -3,8 +3,8 @@ title: 'Categoria global da Amazon não funciona'
 id: 4xG37vNjH3XWVdb57w6zzV
 status: PUBLISHED
 createdAt: 2022-08-12T11:49:47.214Z
-updatedAt: 2022-12-02T18:32:25.769Z
-publishedAt: 2022-12-02T18:32:25.769Z
+updatedAt: 2024-02-16T20:25:10.435Z
+publishedAt: 2024-02-16T20:25:10.435Z
 firstPublishedAt: 2022-08-12T11:49:47.743Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: categoria-global-da-amazon-nao-funciona
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 634199
 ---
 
diff --git a/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md b/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md
index 907d1c66f..4cd1e35f6 100644
--- a/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md
+++ b/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md
@@ -3,8 +3,8 @@ title: 'Atributo de integração da Amazônia Número de itens'
 id: 75Afw210mMY9h6dbk3AV8V
 status: PUBLISHED
 createdAt: 2022-04-07T12:18:04.361Z
-updatedAt: 2022-11-25T21:56:13.168Z
-publishedAt: 2022-11-25T21:56:13.168Z
+updatedAt: 2024-02-16T20:25:56.485Z
+publishedAt: 2024-02-16T20:25:56.485Z
 firstPublishedAt: 2022-04-07T12:18:05.650Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: atributo-de-integracao-da-amazonia-numero-de-itens
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 557788
 ---
 
diff --git a/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md b/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md
index b649d4ab7..615da298e 100644
--- a/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md
+++ b/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md
@@ -3,8 +3,8 @@ title: 'Reservas de estoque de integração da Amazon para KITS'
 id: 6ZEvHuGCOEcuQTya1oDOyu
 status: PUBLISHED
 createdAt: 2023-05-22T14:28:54.846Z
-updatedAt: 2023-05-22T14:28:55.337Z
-publishedAt: 2023-05-22T14:28:55.337Z
+updatedAt: 2023-09-27T14:37:26.343Z
+publishedAt: 2023-09-27T14:37:26.343Z
 firstPublishedAt: 2023-05-22T14:28:55.337Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: reservas-de-estoque-de-integracao-da-amazon-para-kits
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 829583
 ---
 
diff --git a/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md b/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md
index 4ceb02903..498734ed8 100644
--- a/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md
+++ b/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md
@@ -3,8 +3,8 @@ title: '[Amazon][casacaso] - Erros de rastreamento'
 id: 6a8QqrvjiQBBI2EM22581P
 status: PUBLISHED
 createdAt: 2022-03-10T17:59:48.309Z
-updatedAt: 2022-11-25T21:57:04.066Z
-publishedAt: 2022-11-25T21:57:04.066Z
+updatedAt: 2023-08-16T12:26:16.960Z
+publishedAt: 2023-08-16T12:26:16.960Z
 firstPublishedAt: 2022-03-10T17:59:48.640Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: amazoncasacaso-erros-de-rastreamento
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 360564
 ---
 
@@ -23,22 +23,12 @@ internalReference: 360564
 </div>
 
 
-Estamos tendo problemas em alguns casos em que o fluxo de trabalho de rastreamento para a Amazônia não está funcionando.
-
-
 
 ## Simulação
 
 
 
-The below message is shown in bridge UI for tracking Menu:
-
-As quantidades fornecidas para a ID do pedido (XXXXXXXXXXXX) eram maiores do que as quantidades que podiam ser atendidas. Revise a quantidade a partir do relatório de pedido e leve em conta quaisquer produtos que foram cancelados ou já foram encerrados
-
-
-
 ## Workaround
 
 
-N/A
 
diff --git a/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md b/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
index 5ca845c13..a182e0fef 100644
--- a/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
+++ b/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
@@ -3,8 +3,8 @@ title: 'API Shipping Estimate devolve informações erradas quando SC é nulo'
 id: 6bxlw1nQ27JGbiOmNbgyn2
 status: PUBLISHED
 createdAt: 2022-04-01T23:33:47.015Z
-updatedAt: 2022-11-25T21:59:23.170Z
-publishedAt: 2022-11-25T21:59:23.170Z
+updatedAt: 2024-07-01T18:48:14.728Z
+publishedAt: 2024-07-01T18:48:14.728Z
 firstPublishedAt: 2022-05-18T18:27:53.441Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: api-shipping-estimate-devolve-informacoes-erradas-quando-sc-e-nulo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 554948
 ---
 
diff --git a/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md b/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
index da826465f..8220cb9db 100644
--- a/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
+++ b/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
@@ -3,8 +3,8 @@ title: 'API para listar pontos de coleta não retorna campo de informações adi
 id: 5YY5srSA2ZRiOSZiMY9UF9
 status: PUBLISHED
 createdAt: 2022-09-02T12:09:09.980Z
-updatedAt: 2022-11-25T21:50:17.504Z
-publishedAt: 2022-11-25T21:50:17.504Z
+updatedAt: 2024-02-16T20:24:50.684Z
+publishedAt: 2024-02-16T20:24:50.684Z
 firstPublishedAt: 2022-09-02T12:09:10.777Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: api-para-listar-pontos-de-coleta-nao-retorna-campo-de-informacoes-adicionais
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 650714
 ---
 
diff --git a/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md b/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md
new file mode 100644
index 000000000..df51bff0e
--- /dev/null
+++ b/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md
@@ -0,0 +1,59 @@
+---
+title: 'As configurações do aplicativo não são apagadas quando você exclui o aplicativo'
+id: 7KXfKLgbc3UDeDSsCgT0Sk
+status: PUBLISHED
+createdAt: 2024-07-15T22:29:24.058Z
+updatedAt: 2024-07-15T22:29:24.867Z
+publishedAt: 2024-07-15T22:29:24.867Z
+firstPublishedAt: 2024-07-15T22:29:24.867Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: as-configuracoes-do-aplicativo-nao-sao-apagadas-quando-voce-exclui-o-aplicativo
+locale: pt
+kiStatus: Backlog
+internalReference: 1065954
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando você instala um aplicativo da App Store e acessa suas configurações, você tem a opção "**Uninstall**", que exclui o aplicativo do espaço de trabalho, mas mantém suas configurações, e a opção "**Delete**", que exclui o aplicativo e suas configurações.
+No entanto, quando você seleciona a opção "**Delete**" e instala o aplicativo novamente, percebe que a configuração não foi excluída.
+
+## Simulação
+
+
+
+- Vá para a "App Store";
+- Selecione o aplicativo;
+- Clique em "Get app" (Obter aplicativo);
+- Clique em "Install app" (Instalar aplicativo);
+- Siga as instruções para instalar o aplicativo;
+- Preencha as configurações (se aplicável) e "Salvar";
+- Clique em "Delete" (Excluir). A seguinte mensagem será exibida:
+ ![](https://vtexhelp.zendesk.com/attachments/token/kM5EhsfVaHLlISckht8rRYumU/?name=image.png)
+
+> _**Do you want to remove the app X?**_
+>
+> _Tem certeza de que deseja excluir esse aplicativo? Todas as configurações salvas em todos os espaços de trabalho serão perdidas e o aplicativo será removido da sua lista de aplicativos.
+
+- Clique em "Excluir" novamente para confirmar. O aplicativo será excluído;
+- Vá para as primeiras etapas e instale o mesmo aplicativo;
+- Verifique suas configurações e veja se as informações não foram excluídas como esperado (as informações preenchidas anteriormente aparecerão lá)
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível. Mas você pode colocar informações fictícias.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md b/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
new file mode 100644
index 000000000..1400aa0dd
--- /dev/null
+++ b/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
@@ -0,0 +1,49 @@
+---
+title: 'Aplique o desconto aos itens mais caros - a interface do usuário não está economizando dados.'
+id: 6VQuVOAtzbA6OyjDEi2bHh
+status: PUBLISHED
+createdAt: 2024-04-03T17:29:36.171Z
+updatedAt: 2024-04-03T17:29:37.024Z
+publishedAt: 2024-04-03T17:29:37.024Z
+firstPublishedAt: 2024-04-03T17:29:37.024Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: aplique-o-desconto-aos-itens-mais-caros-a-interface-do-usuario-nao-esta-economizando-dados
+locale: pt
+kiStatus: Backlog
+internalReference: 1011071
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar a UI de promoções, a tentativa de salvar manualmente a opção "Aplicar aos itens mais caros" não funcionará e o seletor permanecerá na opção do tipo mais barato.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ofDGJuHHbNRwvbYDMOSSCznvB/?name=image.png)
+
+## Simulação
+
+
+1 - Acesse a interface do usuário de promoções: https://account_name.myvtex.com/admin/promotions
+
+2 - Na interface de usuário de promoções, selecione a opção "Apply the discount to the most expensive items" (Aplicar o desconto aos itens mais caros)
+
+3 - Salve a promoção
+
+4 - Acesse-a novamente, e a caixa para aplicar o desconto na opção mais barata será selecionada
+
+## Workaround
+
+
+Em vez disso, use a API de salvamento de promoções https://developers.vtex.com/docs/api-reference/promotions-and-taxes-api#post-/api/rnb/pvt/calculatorconfiguration
+
+
+
+
+
diff --git a/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md b/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md
index 54c7fccf5..9e43e589d 100644
--- a/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md
+++ b/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md
@@ -3,8 +3,8 @@ title: 'Folha de cálculo aprovada Skus que não mostra o preço'
 id: 3nWwzGYX1Ys0rKkoSZZpdz
 status: PUBLISHED
 createdAt: 2022-03-29T19:22:12.977Z
-updatedAt: 2022-11-25T22:00:49.862Z
-publishedAt: 2022-11-25T22:00:49.862Z
+updatedAt: 2024-02-16T20:23:36.636Z
+publishedAt: 2024-02-16T20:23:36.636Z
 firstPublishedAt: 2022-03-29T19:22:13.346Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: folha-de-calculo-aprovada-skus-que-nao-mostra-o-preco
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 552155
 ---
 
diff --git a/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
new file mode 100644
index 000000000..8174330a5
--- /dev/null
+++ b/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -0,0 +1,65 @@
+---
+title: 'A API da Attachents não permite "domainValues" nulos (e deveria)'
+id: 7KMb6nh0ulcWdEfz7USbPg
+status: PUBLISHED
+createdAt: 2023-09-11T19:02:51.514Z
+updatedAt: 2023-09-11T19:02:52.164Z
+publishedAt: 2023-09-11T19:02:52.164Z
+firstPublishedAt: 2023-09-11T19:02:52.164Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-api-da-attachents-nao-permite-domainvalues-nulos-e-deveria
+locale: pt
+kiStatus: Backlog
+internalReference: 897480
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As solicitações de atualização para a API /api/catalog/pvt/attachment/ não estão permitindo atualizações para o campo Valor do domínio como um valor nulo.
+
+Esse campo é anulável, portanto, essa resposta da API está respondendo incorretamente com:
+
+`{`
+` "Mensagem": "DomainValues in Domain at position 1 can not be null or empty value"`
+`}`
+
+## Simulação
+
+
+1 - Criar um anexo via UI ou API: https://help.vtex.com/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU
+
+2 - tente atualizá-lo enviando o campo domainValue como um nulo, por exemplo:
+
+`{`
+` "Id": 123,`
+` "Name": "payload com domínio nulo",`
+` "IsRequired": true,`
+` "IsActive": true,`
+` "Domains" (Domínios): [`
+` {`
+` "FieldName": "Basic test",`
+` "MaxCaracters": "354534",`
+` "DomainValues": ""`
+` }`
+` ]`
+`}`
+
+3 - um tipo de resposta "Bad request" será exibido para você, quando na verdade deveria aceitar valores nulos para esse campo
+
+## Workaround
+
+
+Atualize os valores permitidos manualmente, por meio da interface do usuário, ou crie-os já nulos (o método POST está funcionando, mas o PUT não).
+
+
+
+
+
diff --git a/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md b/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
index 40a3f4015..2d78ce577 100644
--- a/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
+++ b/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
@@ -3,8 +3,8 @@ title: 'Atualização de anexos e criação de validação API em campos de valo
 id: 1NAwwi7C65xM2G61uaTLrB
 status: PUBLISHED
 createdAt: 2023-02-09T16:10:03.814Z
-updatedAt: 2023-02-09T16:10:04.449Z
-publishedAt: 2023-02-09T16:10:04.449Z
+updatedAt: 2024-07-01T18:48:48.654Z
+publishedAt: 2024-07-01T18:48:48.654Z
 firstPublishedAt: 2023-02-09T16:10:04.449Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: atualizacao-de-anexos-e-criacao-de-validacao-api-em-campos-de-valores-de-dominio-que-nao-funcionam
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 751091
 ---
 
diff --git a/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md b/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
new file mode 100644
index 000000000..edf781556
--- /dev/null
+++ b/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
@@ -0,0 +1,60 @@
+---
+title: 'Validação de anexo somente no marketplace ao adicionar um item de um vendedor com anexo'
+id: 638N4urP08NY7v8jdH7U5N
+status: PUBLISHED
+createdAt: 2023-12-22T18:18:59.194Z
+updatedAt: 2023-12-22T18:18:59.909Z
+publishedAt: 2023-12-22T18:18:59.909Z
+firstPublishedAt: 2023-12-22T18:18:59.909Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: validacao-de-anexo-somente-no-marketplace-ao-adicionar-um-item-de-um-vendedor-com-anexo
+locale: pt
+kiStatus: Backlog
+internalReference: 957343
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao adicionar um item de um vendedor com um anexo na mesma solicitação de API, a validação do anexo ocorre somente no marketplace.
+
+**Cenário 1:**
+Se o marketplace tiver o mesmo nome de anexo e as chaves forem diferentes das do vendedor, a mensagem de erro "Item attachment has an invalid value for key" será exibida e o item não será adicionado ao carrinho.
+
+**Cenário 2:**
+Se o marketplace não tiver o mesmo anexo, a mensagem de erro "O nome do anexo é inválido" será exibida e o item não será adicionado ao carrinho.
+
+Esse comportamento ocorre em ambas as APIs para adicionar itens: Adicionar itens do carrinho e Manipular itens do carrinho.
+
+## Simulação
+
+
+
+- Configure o mesmo anexo no marketplace e no vendedor com chaves de campo diferentes;
+- Associar a um item;
+- Adicionar o item por meio de Adicionar itens do carrinho ou Manipular itens do carrinho, com anexos.
+
+
+- Configurar um anexo no vendedor e associá-lo a um item;
+- Adicione o item por meio de Adicionar itens do carrinho ou Manusear itens do carrinho, com anexos
+
+## Workaround
+
+
+
+- Adicione o item primeiro e o anexo depois em solicitações diferentes. Para enviar o anexo, você pode:
+  - enviar os anexos por meio de Manusear itens do carrinho;
+  - enviar os anexos por meio de Adicionar um anexo a um item, por exemplo:
+
+    curl --location 'https://{accountName}.{environment}.com.br/api/checkout/pub/orderForm/{orderFormId}/items/{itemIndex}/attachments/{attachmentName}' \--header 'Content-Type: application/json' \--data '{ "content": { "key": "value" }, "noSplitItem": true}'
+
+
+
+
diff --git a/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md b/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
new file mode 100644
index 000000000..32fbacaf1
--- /dev/null
+++ b/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
@@ -0,0 +1,43 @@
+---
+title: 'Os valores permitidos do anexo não são atualizados quando ele é adicionado aos itens'
+id: 1JjFJJGsUaLWvthJ7kxSBw
+status: PUBLISHED
+createdAt: 2023-10-17T20:16:40.973Z
+updatedAt: 2023-10-17T20:16:41.571Z
+publishedAt: 2023-10-17T20:16:41.571Z
+firstPublishedAt: 2023-10-17T20:16:41.571Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-valores-permitidos-do-anexo-nao-sao-atualizados-quando-ele-e-adicionado-aos-itens
+locale: pt
+kiStatus: Backlog
+internalReference: 920970
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os valores permitidos do anexo não são atualizados se ele foi adicionado a um item antes de alterar seus valores no administrador. Isso causará um erro no carrinho com a mensagem "Não foi possível se comunicar com o vendedor".
+
+## Simulação
+
+
+
+- Crie um anexo com valores permitidos;
+- Adicionar um item com o anexo;
+- Alterar os valores permitidos do anexo;
+- Atualizar o carrinho
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md b/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md
new file mode 100644
index 000000000..be5426020
--- /dev/null
+++ b/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md
@@ -0,0 +1,45 @@
+---
+title: 'O atributo meli_shipping_mode não está sendo atualizado na integração MELI'
+id: 7DMsCqv2AsOEsL3LGLhxWq
+status: PUBLISHED
+createdAt: 2023-08-03T10:19:05.524Z
+updatedAt: 2024-06-10T13:38:07.225Z
+publishedAt: 2024-06-10T13:38:07.225Z
+firstPublishedAt: 2023-08-03T10:19:06.574Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: o-atributo-melishippingmode-nao-esta-sendo-atualizado-na-integracao-meli
+locale: pt
+kiStatus: Fixed
+internalReference: 873993
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema com o atributo de produto chamado "meli_shipping_mode" que não está sendo atualizado na integração do MELI
+
+## Simulação
+
+
+
+Dentro da especificação do produto, o vendedor pode usar o atributo "meli_shipping_mode" e definir ME1 ou ME2 para definir a estratégia de envio no MELI.
+
+Mas atualmente só podemos enviar esse valor ao criar o SKU no MELI e não estamos atualizando com o valor correto.
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
new file mode 100644
index 000000000..e1f6d719f
--- /dev/null
+++ b/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
@@ -0,0 +1,46 @@
+---
+title: 'Registros de preços de auditoria mostrando informações "desconhecidas"'
+id: 7b8UDsiBo7VOHCN3pgcfd0
+status: PUBLISHED
+createdAt: 2023-07-05T18:51:22.120Z
+updatedAt: 2023-07-05T18:51:22.566Z
+publishedAt: 2023-07-05T18:51:22.566Z
+firstPublishedAt: 2023-07-05T18:51:22.566Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: registros-de-precos-de-auditoria-mostrando-informacoes-desconhecidas
+locale: pt
+kiStatus: Backlog
+internalReference: 856420
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas ações do usuário relacionadas a modificações de preço estão sendo registradas no módulo de auditoria como "desconhecidas".
+
+## Simulação
+
+
+
+1. O comerciante faz algumas modificações no módulo de preços.
+2. Algumas ações serão registradas corretamente na auditoria.
+3. Verifique se algumas ações serão registradas com os campos "Action" (Ação) e "Event Details" (Detalhes do evento) definidos como "unknow" (desconhecido).
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md b/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
new file mode 100644
index 000000000..d17a8b1e7
--- /dev/null
+++ b/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
@@ -0,0 +1,43 @@
+---
+title: 'O status da autorização é mantido para transações assíncronas com 2 ou mais pagamentos quando o primeiro é cancelado.'
+id: 7kEU8P6lkSQYZWzgaC16nY
+status: PUBLISHED
+createdAt: 2023-11-02T15:49:18.723Z
+updatedAt: 2023-11-02T19:37:18.326Z
+publishedAt: 2023-11-02T19:37:18.326Z
+firstPublishedAt: 2023-11-02T15:49:19.524Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-status-da-autorizacao-e-mantido-para-transacoes-assincronas-com-2-ou-mais-pagamentos-quando-o-primeiro-e-cancelado
+locale: pt
+kiStatus: Backlog
+internalReference: 929517
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma transação tem vários pagamentos e se torna assíncrona devido ao modo Sherlock ou Defense, e se a primeira tentativa de autorização de pagamento falhar, isso pode fazer com que os outros pagamentos fiquem presos em um status "Autorizado". Isso ocorre porque a transação inteira é cancelada, mas nosso funcionário não reconhece isso e prossegue com uma tentativa de autorização para o segundo pagamento. Consequentemente, o segundo pagamento não pode ser cancelado, pois a transação já foi cancelada e não permite uma solicitação de cancelamento.
+
+## Simulação
+
+
+Crie uma transação com dois pagamentos, na qual o Modo de defesa ou qualquer outro recurso que torne a transação assíncrona esteja ativado. Em seguida, use um conector de provedor personalizado para recusar a primeira tentativa de autorização de pagamento e aprovar a outra.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/auto-approve-api-accepts-any-values.md b/docs/known-issues/pt/auto-approve-api-accepts-any-values.md
index 77a3bac31..5ba52dd80 100644
--- a/docs/known-issues/pt/auto-approve-api-accepts-any-values.md
+++ b/docs/known-issues/pt/auto-approve-api-accepts-any-values.md
@@ -3,8 +3,8 @@ title: 'Auto aprova API aceita quaisquer valores'
 id: kLl4mtwKPPqW6jk5hZMWs
 status: PUBLISHED
 createdAt: 2022-12-12T14:18:51.059Z
-updatedAt: 2022-12-12T14:18:51.733Z
-publishedAt: 2022-12-12T14:18:51.733Z
+updatedAt: 2024-02-16T20:27:19.981Z
+publishedAt: 2024-02-16T20:27:19.981Z
 firstPublishedAt: 2022-12-12T14:18:51.733Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: auto-aprova-api-aceita-quaisquer-valores
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 713704
 ---
 
diff --git a/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md b/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md
index 484b48d65..b4e508fcd 100644
--- a/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md
+++ b/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md
@@ -3,8 +3,8 @@ title: 'Autocompletar trazendo produtos de sugestão mostrados com atraso'
 id: 26ydVkjgikjeBq8Jxuh0Vr
 status: PUBLISHED
 createdAt: 2022-07-12T12:21:25.537Z
-updatedAt: 2023-02-08T13:50:52.209Z
-publishedAt: 2023-02-08T13:50:52.209Z
+updatedAt: 2024-07-01T18:48:28.298Z
+publishedAt: 2024-07-01T18:48:28.298Z
 firstPublishedAt: 2022-07-12T12:21:26.029Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: autocompletar-trazendo-produtos-de-sugestao-mostrados-com-atraso
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 615616
 ---
 
diff --git a/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md b/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md
index ef89850eb..a9ac6de77 100644
--- a/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md
+++ b/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md
@@ -1,18 +1,18 @@
 ---
-title: 'Autocompletar não respondendo a partidas frias'
+title: 'O preenchimento automático não responde a partidas a frio'
 id: 2lgYjT8lmFIvLV3vKOXKmt
 status: PUBLISHED
 createdAt: 2022-02-23T22:01:05.141Z
-updatedAt: 2022-11-25T21:58:01.186Z
-publishedAt: 2022-11-25T21:58:01.186Z
+updatedAt: 2024-03-14T18:48:50.406Z
+publishedAt: 2024-03-14T18:48:50.406Z
 firstPublishedAt: 2022-02-23T22:01:05.666Z
 contentType: knownIssue
 productTeam: Intelligent Search
 author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
-slug: autocompletar-nao-respondendo-a-partidas-frias
+slug: o-preenchimento-automatico-nao-responde-a-partidas-a-frio
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 418573
 ---
 
@@ -23,9 +23,7 @@ internalReference: 418573
 </div>
 
 
-O recurso de busca inteligente conhecido como **autocompleto** não está funcionando para algumas lojas novas, mesmo depois de executar um processo interno chamado _início frio_.
-
-
+O recurso de pesquisa inteligente conhecido como **autocompletar** não está funcionando em algumas lojas novas, mesmo após a execução de um processo interno chamado _cold start_.
 
 
 ## Simulação
@@ -33,10 +31,11 @@ O recurso de busca inteligente conhecido como **autocompleto** não está funcio
 
 N/A.
 
+## Workaround
 
 
-## Workaround
+No momento, não há solução alternativa para esse problema conhecido, mas o autocompletar em si está funcionando corretamente e continuará aprendendo com base na experiência do usuário, o que significa que, um pouco depois de entrar em operação, ele funcionará muito bem para novas contas.
+
 
 
-Atualmente não há solução para este problema conhecido, mas o auto-completar por si só está funcionando corretamente e continuará aprendendo com base na experiência do usuário, o que significa que um tempo depois de viver, ele funcionará bem para novas contas.
 
diff --git a/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
new file mode 100644
index 000000000..f4343482c
--- /dev/null
+++ b/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -0,0 +1,48 @@
+---
+title: 'A API de sugestão de preenchimento automático remove o ponto "." do nome do produto'
+id: 55185IvERIwGQ3kH6H510O
+status: PUBLISHED
+createdAt: 2024-04-10T13:58:51.138Z
+updatedAt: 2024-04-10T13:58:52.084Z
+publishedAt: 2024-04-10T13:58:52.084Z
+firstPublishedAt: 2024-04-10T13:58:52.084Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: a-api-de-sugestao-de-preenchimento-automatico-remove-o-ponto-do-nome-do-produto
+locale: pt
+kiStatus: Backlog
+internalReference: 1014701
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Esse problema ocorre quando se pesquisa um termo e a sugestão de preenchimento automático retorna o nome do produto sem o caractere de ponto ".", mesmo que ele exista no nome do produto, resultando em resultados de pesquisa incorretos.
+
+## Simulação
+
+
+
+1. GET` https://..com.br/api/io/_v/api/intelligent-search/autocomplete_suggestions?query=`.
+2. Observe as sugestões de preenchimento automático fornecidas pelo sistema.
+3. Observe que o caractere de ponto está faltando no nome do produto selecionado.
+
+Por exemplo, se o termo "headphone" (fone de ouvido) for pesquisado na API de sugestões de autocompletar, os resultados da sugestão, se contiverem um ponto no nome, serão exibidos como "Headphone Bluetooth 5 0" em vez de ter o ponto no número "5.0". O formato correto deve ser "Headphone Bluetooth 5.0".
+
+Ao usar essa sugestão na API product_search, os resultados não serão retornados
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index 03783e2f3..ea127337e 100644
--- a/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumário
 
-O Campo automático (campo calculado) funciona corretamente quando  "Recalcular esse campo:" é setado para "somente quando inserir registro", mas para de funcionar quando é programado para recalcular "na primeira hora..." e suas variantes.![inline1511102536](https://images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
+O Campo automático (campo calculado) funciona corretamente quando  "Recalcular esse campo:" é setado para "somente quando inserir registro", mas para de funcionar quando é programado para recalcular "na primeira hora..." e suas variantes.![inline1511102536](//images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md b/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md
new file mode 100644
index 000000000..c341d5e18
--- /dev/null
+++ b/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md
@@ -0,0 +1,54 @@
+---
+title: 'Configuração incorreta da liquidação automática de pagamentos'
+id: 6KOQwBKNgOPNL7TM80Bqjf
+status: PUBLISHED
+createdAt: 2024-06-19T22:12:10.705Z
+updatedAt: 2024-06-19T22:12:11.484Z
+publishedAt: 2024-06-19T22:12:11.484Z
+firstPublishedAt: 2024-06-19T22:12:11.484Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: configuracao-incorreta-da-liquidacao-automatica-de-pagamentos
+locale: pt
+kiStatus: Backlog
+internalReference: 1053010
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O problema é que o gateway ignorou o valor `delayToAutoSettleAfterAntifraud`.
+
+Esses campos são obrigatórios na resposta de autorização, mas o gateway aceita a ausência deles. Nossa documentação está relacionada a isso.
+
+        "delayToAutoSettle": 1200, "delayToAutoSettleAfterAntifraud": 1200
+
+Em um cenário perfeito, o gateway não deveria aceitar a resposta sem eles.
+
+Quando o campo `delayToAutoSettleAfterAntifraud` não está no payload da resposta de autorização. O gateway não pode definir o valor correto, portanto, o valor padrão da liquidação automática do pagamento será de 4 dias (padrão).
+
+## Simulação
+
+
+
+1. Crie um pagamento.
+2. Configure o conector para responder sem que seja necessário o campo delayToAutoSettle, mas enviando o delayToAutoSettleAfterAntifraud
+3. Verifique a resposta de autorização, e ela terá apenas o valor que o conector respondeu
+4. Verifique o cartão roxo para ver qual valor foi configurado. A liquidação automática do pagamento será agendada para quatro dias após a aprovação do pagamento.
+
+## Workaround
+
+
+
+Defina o **delayAutoSettle** como o mesmo valor do **delayAutoSettleAfterAntifraud**.
+
+
+
+
+
diff --git a/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md b/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
new file mode 100644
index 000000000..20056a942
--- /dev/null
+++ b/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
@@ -0,0 +1,45 @@
+---
+title: 'Tradução automática de URLs que não ocorrem devido a caracteres especiais'
+id: 7G0WKfFFZxZ7mMEoasePld
+status: PUBLISHED
+createdAt: 2024-07-09T19:45:44.410Z
+updatedAt: 2024-07-10T12:45:50.061Z
+publishedAt: 2024-07-10T12:45:50.061Z
+firstPublishedAt: 2024-07-09T19:45:45.704Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: traducao-automatica-de-urls-que-nao-ocorrem-devido-a-caracteres-especiais
+locale: pt
+kiStatus: Backlog
+internalReference: 1062858
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o aplicativo `admin-catalog-translations` para traduzir automaticamente o conteúdo do catálogo, o linkId pode ter problemas para ser traduzido quando tiver caracteres especiais, como `ç`. O `admin-catalog-translations` usa o `messages app` para fazer as traduções e algumas palavras podem não ser traduzidas corretamente devido a esses caracteres.
+
+## Simulação
+
+
+Tente traduzir o link de um produto que tenha uma palavra com caracteres especiais, como "calça". Se quiser traduzir essa palavra em uma URL, ela provavelmente será `calca`, que não existe no idioma português, portanto o aplicativo `message` não poderá traduzi-la automaticamente
+
+## Workaround
+
+
+** **
+Você deve alterar o URL do produto manualmente, executando a seguinte mutação:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "/yourTranslatedLinkdId/p", "declarer": "vtex.store@2.x", "type": "product", "id": "productId", "resolveAs": "/yourOrinalLinkdId/p", "binding": "bindingId" }}
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
index e759f771e..6b9ac42cf 100644
--- a/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
@@ -3,8 +3,8 @@ title: 'Atualização automática do rastreio de entregas via Correios'
 id: 7hKUU5Qp4AyCW2QaMQC0S6
 status: PUBLISHED
 createdAt: 2017-08-16T22:07:06.254Z
-updatedAt: 2022-12-22T14:52:07.213Z
-publishedAt: 2022-12-22T14:52:07.213Z
+updatedAt: 2024-02-29T18:16:47.090Z
+publishedAt: 2024-02-29T18:16:47.090Z
 firstPublishedAt: 2017-08-16T23:00:56.342Z
 contentType: knownIssue
 productTeam: Post-purchase
@@ -22,6 +22,7 @@ O OMS possui um recurso que acompanha automaticamente as entregas dos Correios (
 
 Alterações recentes dos Correios fizeram a nossa integração deixar de funcionar, sendo necessário reescrever o serviço responsável por essa tarefa.
 
+
 ## Simulação
 
 Basta ter um código de rastreio válido em qualquer pedido. Nos dias seguintes, conforme houver atualização nesse código de rastreio, deveria haver o envio de e-mails, que notavelmente não irá acontecer.
@@ -34,5 +35,9 @@ Basta ter um código de rastreio válido em qualquer pedido. Nos dias seguintes,
 
 A confirmação de entrega feita via OMS também é repassada aos marketplaces.
 
+<div class = "alert alert-info">
+Atualmente, oferecemos o <a href="https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib">VTEX Shipping Network</a>, nossa solução logística para integrar sua operação aos serviços dos Correios e/ou transportadoras parceiras. Todos os pedidos da loja que estiverem vinculados a essa solução vão dispor de rastreamento com atualização automática.
+</div>
+
 Outra opção é utilizar soluções desenvolvidas por parceiros para acompanhar entregas dos Correios, como o [rastreio da XP Agência](https://rastreio.xpagencia.com.br/).
 
diff --git a/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
new file mode 100644
index 000000000..ddaed9b98
--- /dev/null
+++ b/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -0,0 +1,47 @@
+---
+title: 'O campo "disponibilidade" está incorreto na Simulação de Cumprimento para produtos sem estoque ou preço'
+id: 1k2zcLEN5vG6mnksLwEXxp
+status: PUBLISHED
+createdAt: 2023-10-04T14:22:53.519Z
+updatedAt: 2023-10-04T14:22:54.219Z
+publishedAt: 2023-10-04T14:22:54.219Z
+firstPublishedAt: 2023-10-04T14:22:54.219Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-campo-disponibilidade-esta-incorreto-na-simulacao-de-cumprimento-para-produtos-sem-estoque-ou-preco
+locale: pt
+kiStatus: Backlog
+internalReference: 773537
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um produto está fora de estoque ou não tem preço, a simulação de atendimento informa incorretamente o campo `disponibilidade` como `disponível`.
+Esse comportamento também se aplica ao contexto da seleção de presentes, em que o campo `selectableGifts` também é afetado por esse problema.
+
+
+1. Se o item tiver um preço, mas não tiver estoque, a simulação de atendimento retornará `"availability": "nullPrice"` quando não houver endereço;
+2. Se o item tiver um preço, mas não houver estoque, a simulação de atendimento retornará `"availability": "available"` quando houver um endereço.
+
+## Simulação
+
+
+
+- Tenha um produto sem estoque ou preço em um vendedor
+- Faça uma simulação de atendiment
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md b/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
new file mode 100644
index 000000000..c69ac1d36
--- /dev/null
+++ b/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
@@ -0,0 +1,67 @@
+---
+title: 'Lista de endereços disponíveis na interface do usuário do checkout sem dados para o endereço recém-criado'
+id: 1BEDcoXLVAs5L039eKXsXv
+status: PUBLISHED
+createdAt: 2024-07-05T21:08:40.994Z
+updatedAt: 2024-07-11T15:56:34.357Z
+publishedAt: 2024-07-11T15:56:34.357Z
+firstPublishedAt: 2024-07-05T21:08:42.246Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: lista-de-enderecos-disponiveis-na-interface-do-usuario-do-checkout-sem-dados-para-o-endereco-recemcriado
+locale: pt
+kiStatus: Backlog
+internalReference: 1061630
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário adiciona um novo endereço durante a etapa de envio do Checkout, avança para a etapa de pagamento e, em seguida, retorna à lista de endereços disponíveis da etapa de envio, esse endereço recém-criado pode estar ausente da lista ou exibir informações incompletas na interface do usuário.
+
+## Simulação
+
+
+
+Caso 1, para usuários autenticados:
+
+1. Faça login na loja com um usuário que tenha pelo menos um endereço salvo e crie um carrinho.
+2. Prossiga para o Checkout e acesse a tela de pagamento.
+3. Clique em "Change shipping options" (Alterar opções de envio).
+4. Clique em "Deliver to another address" (Entregar em outro endereço).
+5. Preencha um novo endereço e clique em "Go to payment" (Ir para pagamento).
+6. Clique novamente em "Change shipping options" (Alterar opções de envio).
+7. Clique novamente em "Deliver to another address" (Entregar em outro endereço).
+8. Clique em "Back to address list" (Voltar à lista de endereços).
+9. O endereço recém-criado pode estar faltando na lista.
+
+Caso 2, para usuários identificados, mas não autenticados:
+
+1. Crie um carrinho e identifique-se com o e-mail de um usuário que tenha pelo menos um endereço salvo.
+2. Prossiga para o Checkout e acesse a tela Payment (Pagamento).
+3. Clique em "Change shipping options" (Alterar opções de envio).
+4. Clique em "Deliver to another address" (Entregar em outro endereço).
+5. Preencha um novo endereço e clique em "Go to payment" (Ir para pagamento).
+6. Clique novamente em "Change shipping options" (Alterar opções de envio).
+7. Clique novamente em "Deliver to another address" (Entregar em outro endereço).
+8. Clique em "Back to address list" (Voltar à lista de endereços).
+9. Para alguns países, o endereço recém-adicionado pode mostrar informações incompletas, como apenas o código postal e o nome do país.
+
+
+
+## Workaround
+
+
+Atualize a página.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md b/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
new file mode 100644
index 000000000..5ca4316fd
--- /dev/null
+++ b/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
@@ -0,0 +1,41 @@
+---
+title: 'Valor de AvailableQuantity inconsistente devido ao grande número de rotas criadas para entregar o item'
+id: 4kKVjSNsIEU8ZVGcpwvzQw
+status: PUBLISHED
+createdAt: 2024-05-16T12:14:20.776Z
+updatedAt: 2024-05-16T12:15:36.200Z
+publishedAt: 2024-05-16T12:15:36.200Z
+firstPublishedAt: 2024-05-16T12:14:21.778Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: valor-de-availablequantity-inconsistente-devido-ao-grande-numero-de-rotas-criadas-para-entregar-o-item
+locale: pt
+kiStatus: Backlog
+internalReference: 1034211
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Durante o pipeline de indexação de um item, é realizada uma simulação sem o uso de um código postal para validar a disponibilidade, essa simulação, quando chega ao sistema de logística, realiza uma validação combinando todas as docas, armazéns e políticas de remessa disponíveis para um canal de vendas, a resposta a esse cálculo determina a disponibilidade do item, porém essa resposta tem um limite de leitura de 10.000 rotas, portanto, quando um cálculo resulta em mais de 10.000, as rotas restantes são desconsideradas, o que pode fazer com que o sistema retorne uma resposta inconsistente.
+
+## Simulação
+
+
+Não há uma maneira simples de simular esse cenário, pois você precisa ter várias configurações de logística em vigor
+
+## Workaround
+
+
+Remova as configurações não utilizadas do canal de vendas (docas, armazéns e políticas de expedição), reduzindo assim o número de rotas criadas pelo sistema durante o cálculo, fazendo com que o número de rotas fique abaixo do limite recomendado pelo sistema (10.000).
+
+
+
+
+
diff --git a/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md b/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md
new file mode 100644
index 000000000..ee35771e4
--- /dev/null
+++ b/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md
@@ -0,0 +1,47 @@
+---
+title: 'Os dados de personificação B2B não são removidos após o logout'
+id: bHYLV4reDQl4epmPbYwmJ
+status: PUBLISHED
+createdAt: 2024-07-18T21:56:41.780Z
+updatedAt: 2024-07-18T21:56:42.802Z
+publishedAt: 2024-07-18T21:56:42.802Z
+firstPublishedAt: 2024-07-18T21:56:42.802Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: os-dados-de-personificacao-b2b-nao-sao-removidos-apos-o-logout
+locale: pt
+kiStatus: Backlog
+internalReference: 1067969
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O logout após a representação de um usuário no B2B Suite não remove as permissões de vitrine da sessão.
+
+Isso permite que o usuário navegue no site e até mesmo faça pedidos se o usuário personificado tiver acesso ao checkout.
+
+## Simulação
+
+
+
+- Faça login com um usuário com funções de representação;
+- Fazer-se passar por outro usuário;
+- Fazer logout.
+
+
+
+## Workaround
+
+
+Clique em "Stop Impersonation" (Interromper personificação) para remover os dados personificados da sessão.
+
+
+
+
diff --git a/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md b/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md
new file mode 100644
index 000000000..62e1024fe
--- /dev/null
+++ b/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md
@@ -0,0 +1,41 @@
+---
+title: 'O histórico de pedidos B2B não funciona no domínio do site'
+id: 4Y7lpxWvMBZFaAA4wuvbGP
+status: PUBLISHED
+createdAt: 2023-06-22T21:53:45.542Z
+updatedAt: 2023-08-02T19:09:35.905Z
+publishedAt: 2023-08-02T19:09:35.905Z
+firstPublishedAt: 2023-06-22T21:53:46.030Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: o-historico-de-pedidos-b2b-nao-funciona-no-dominio-do-site
+locale: pt
+kiStatus: Fixed
+internalReference: 849394
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O histórico de pedidos B2B não funciona no domínio do site, mostrando a mensagem "Você não tem permissão para acessar isso".
+
+## Simulação
+
+
+
+- Acesse My Account - Orders (Minha conta - Pedidos) no domínio do site;
+- A mensagem "You don't have permission to access this." (Você não tem permissão para acessar isso) será exibida
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md b/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
new file mode 100644
index 000000000..2b2a885a9
--- /dev/null
+++ b/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
@@ -0,0 +1,43 @@
+---
+title: 'A organização B2B não considera as contas que usam geolocalização ao registrar o endereço'
+id: 2o6k71zZQWGVNDVSTwMZSx
+status: PUBLISHED
+createdAt: 2023-09-21T16:10:29.092Z
+updatedAt: 2023-09-21T16:10:59.672Z
+publishedAt: 2023-09-21T16:10:59.672Z
+firstPublishedAt: 2023-09-21T16:10:29.723Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: a-organizacao-b2b-nao-considera-as-contas-que-usam-geolocalizacao-ao-registrar-o-endereco
+locale: pt
+kiStatus: Backlog
+internalReference: 904907
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A organização B2B não tem nada para configurar um endereço quando as contas usam geolocalização, fazendo com que os itens fiquem indisponíveis.
+
+## Simulação
+
+
+
+- Configure uma conta para usar a geolocalização no checkout;
+- Certifique-se de que seja uma conta de países que usam opções predefinidas, por exemplo, Argentina, Chile, Colômbia, etc;
+- Crie uma organização;
+- Tente comprar qualquer produto, ele sempre estará indisponível
+
+## Workaround
+
+
+Altere a configuração para usar somente o código postal.
+
+
+
diff --git a/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md b/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
new file mode 100644
index 000000000..0b4a318a3
--- /dev/null
+++ b/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
@@ -0,0 +1,51 @@
+---
+title: 'A interface de usuário detalhada das organizações B2B mostra apenas 100 primeiros vendedores'
+id: 6gZm70bIF0p92u6WtDZqdO
+status: PUBLISHED
+createdAt: 2024-01-15T21:29:19.105Z
+updatedAt: 2024-01-15T21:29:45.018Z
+publishedAt: 2024-01-15T21:29:45.018Z
+firstPublishedAt: 2024-01-15T21:29:19.660Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: a-interface-de-usuario-detalhada-das-organizacoes-b2b-mostra-apenas-100-primeiros-vendedores
+locale: pt
+kiStatus: Backlog
+internalReference: 966450
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A interface de usuário de detalhes das organizações B2B mostra apenas os 100 primeiros vendedores; a interface de usuário não tem paginação, tornando impossível selecionar um vendedor se não estiver na primeira página
+
+## Simulação
+
+
+
+- Certifique-se de que a conta tenha mais de 100 vendedores registrados;
+- Acesse a guia vendedor na interface de usuário de detalhes de organizações B2B;
+- Somente os 100 primeiros vendedores serão exibidos
+
+## Workaround
+
+
+
+- Execute um getOrganizationById via graphQL usando o aplicativo:
+
+    { getOrganizationById(id:""){ id name tradeName status collections { id } paymentTerms { id } priceTables customFields { name type value useOnRegistration } salesChannel sellers { id name }}}
+
+- Executar uma mutação usando os dados do graphQL anterior:
+
+    mutation { updateOrganization ( id: "", name: "" tradeName: "" status: "active" collections: [] paymentTerms: [] priceTables: [] customFields: [] salesChannel: null sellers: [{ id: "", name: "" }] ) { id }}
+
+
+
+
+
diff --git a/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md b/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
new file mode 100644
index 000000000..3ee780f0a
--- /dev/null
+++ b/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
@@ -0,0 +1,45 @@
+---
+title: 'O recurso de personificação das organizações B2B não registra informações nos pedidos'
+id: 48IPJWvzeN0uPjGVyOd3Ff
+status: PUBLISHED
+createdAt: 2024-06-27T13:04:27.839Z
+updatedAt: 2024-06-27T13:04:28.879Z
+publishedAt: 2024-06-27T13:04:28.879Z
+firstPublishedAt: 2024-06-27T13:04:28.879Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: o-recurso-de-personificacao-das-organizacoes-b2b-nao-registra-informacoes-nos-pedidos
+locale: pt
+kiStatus: Backlog
+internalReference: 1056736
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As organizações B2B têm um recurso nativo para se passar por outros membros da organização ou do centro de custo.
+
+Quando um e-mail tem as permissões adequadas e se faz passar por outro membro, nenhuma informação de personificação sobre quem concluiu a compra é registrada no pedido.
+
+## Simulação
+
+
+
+- Fazer-se passar por um membro;
+- Montar um carrinho;
+- Faça um pedido e verifique se nenhuma informação sobre a personificação foi salva
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md b/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
new file mode 100644
index 000000000..99bb939a3
--- /dev/null
+++ b/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
@@ -0,0 +1,42 @@
+---
+title: 'A B2B Quotes não aplica o desconto no checkout no domínio do site'
+id: 2VWm5NVqW1LRSZINAAjM7B
+status: PUBLISHED
+createdAt: 2023-06-22T17:17:04.039Z
+updatedAt: 2024-01-31T21:13:13.614Z
+publishedAt: 2024-01-31T21:13:13.614Z
+firstPublishedAt: 2023-06-22T17:17:04.726Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: a-b2b-quotes-nao-aplica-o-desconto-no-checkout-no-dominio-do-site
+locale: pt
+kiStatus: Fixed
+internalReference: 849080
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma cotação tem um desconto aplicado por um vendedor, o B2B Quotes não aplica o desconto no checkout no domínio do site.
+
+## Simulação
+
+
+
+- Crie uma cotação;
+- No domínio do site, clique em "Usar cotação";
+- No carrinho, não há alteração no preço do item
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md b/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
new file mode 100644
index 000000000..bbc6997ce
--- /dev/null
+++ b/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
@@ -0,0 +1,44 @@
+---
+title: 'O B2B Suite não usa coordenadas geográficas para calcular a Id da região'
+id: 7ITcf4hiOD1k6XBIhaCclj
+status: PUBLISHED
+createdAt: 2024-06-24T21:48:19.921Z
+updatedAt: 2024-06-27T20:58:12.541Z
+publishedAt: 2024-06-27T20:58:12.541Z
+firstPublishedAt: 2024-06-24T21:48:20.731Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: o-b2b-suite-nao-usa-coordenadas-geograficas-para-calcular-a-id-da-regiao
+locale: pt
+kiStatus: Backlog
+internalReference: 1055033
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+É possível usar taxas de remessa usando códigos postais ou coordenadas geográficas, mas as organizações B2B usam somente códigos postais para calcular IDs de região. Se uma conta tiver geolocalização (polígonos) registrada em suas taxas de envio, os produtos serão mostrados como indisponíveis na vitrine.
+
+## Simulação
+
+
+
+- Registre as taxas de envio com polígonos;
+- Criar uma organização;
+- Faça login na loja;
+- Nenhum produto é mostrado
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 72fc12029..1fa2ef38c 100644
--- a/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -3,8 +3,8 @@ title: '[Ordem "B2W direta" (FOB) integrando-se com a transportadora'
 id: 20nA7vm1RFMhv7yhaJ43GG
 status: PUBLISHED
 createdAt: 2022-12-12T18:14:19.975Z
-updatedAt: 2022-12-12T18:14:20.451Z
-publishedAt: 2022-12-12T18:14:20.451Z
+updatedAt: 2024-02-16T20:27:21.732Z
+publishedAt: 2024-02-16T20:27:21.732Z
 firstPublishedAt: 2022-12-12T18:14:20.451Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: ordem-b2w-direta-fob-integrandose-com-a-transportadora
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 714879
 ---
 
diff --git a/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md b/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md
index ba76aca2a..7f452b72b 100644
--- a/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md
+++ b/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md
@@ -3,8 +3,8 @@ title: '[B2W] Valor do frete em OMS VTEX'
 id: 7kVoMojCNmOHatg2L1ykBP
 status: PUBLISHED
 createdAt: 2022-10-04T19:43:17.116Z
-updatedAt: 2022-11-25T21:55:17.709Z
-publishedAt: 2022-11-25T21:55:17.709Z
+updatedAt: 2024-02-16T20:23:26.779Z
+publishedAt: 2024-02-16T20:23:26.779Z
 firstPublishedAt: 2022-10-04T19:43:20.129Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: b2w-valor-do-frete-em-oms-vtex
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 671748
 ---
 
diff --git a/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
index 70701f62a..37adf5bd6 100644
--- a/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
@@ -1,16 +1,16 @@
 ---
-title: 'Má solicitação ao pesquisar termos com "%" diretamente via URL'
+title: 'Solicitação incorreta ao pesquisar termos com "%" diretamente via URL'
 id: 3gdZ8egQRa4zcNRe2f5CbT
 status: PUBLISHED
 createdAt: 2023-03-21T22:51:46.273Z
-updatedAt: 2023-03-21T22:51:46.888Z
-publishedAt: 2023-03-21T22:51:46.888Z
+updatedAt: 2024-02-16T17:45:27.298Z
+publishedAt: 2024-02-16T17:45:27.298Z
 firstPublishedAt: 2023-03-21T22:51:46.888Z
 contentType: knownIssue
 productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
-slug: ma-solicitacao-ao-pesquisar-termos-com-diretamente-via-url
+slug: solicitacao-incorreta-ao-pesquisar-termos-com-diretamente-via-url
 locale: pt
 kiStatus: Backlog
 internalReference: 775524
@@ -23,25 +23,21 @@ internalReference: 775524
 </div>
 
 
-Ao procurar um termo com "%" diretamente via URL, a página retorna um pedido 400 Bad Request.
-
-
-##
+Ao pesquisar um termo com "%" diretamente via URL, a página retorna uma solicitação 400 Bad Request.
 
 ## Simulação
 
 
 
-- Procure qualquer termo com "%", por exemplo, "100% algodão";
-- Refresque a página
+- Pesquise qualquer termo com "%", por exemplo, "100% algodão";
+- Atualizar a página
 
 
-##
 
 ## Workaround
 
 
-Busca sem o "%".
+N/A
 
 
 
diff --git a/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
new file mode 100644
index 000000000..32119cdb4
--- /dev/null
+++ b/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -0,0 +1,43 @@
+---
+title: 'Solicitação incorreta ao pesquisar termos com "#" por meio do preenchimento automático'
+id: 18pMsxubB9eSPGlULAN35p
+status: PUBLISHED
+createdAt: 2024-02-06T20:07:52.739Z
+updatedAt: 2024-02-06T20:07:53.531Z
+publishedAt: 2024-02-06T20:07:53.531Z
+firstPublishedAt: 2024-02-06T20:07:53.531Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: solicitacao-incorreta-ao-pesquisar-termos-com-por-meio-do-preenchimento-automatico
+locale: pt
+kiStatus: Backlog
+internalReference: 978136
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao pesquisar um termo com "#" diretamente por meio do preenchimento automático, a página nunca é carregada
+
+## Simulação
+
+
+
+- Pesquise qualquer termo com "#", por exemplo, "Shirt#" no preenchimento automático;
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md b/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
new file mode 100644
index 000000000..595c2e7d2
--- /dev/null
+++ b/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
@@ -0,0 +1,42 @@
+---
+title: 'Solicitação incorreta ao tentar acessar um inventário com uma grande quantidade de itens reservados'
+id: 4DujUMKeYTlx2MXAjnHlS5
+status: PUBLISHED
+createdAt: 2024-07-03T20:18:55.508Z
+updatedAt: 2024-07-03T20:23:50.434Z
+publishedAt: 2024-07-03T20:23:50.434Z
+firstPublishedAt: 2024-07-03T20:18:56.626Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: solicitacao-incorreta-ao-tentar-acessar-um-inventario-com-uma-grande-quantidade-de-itens-reservados
+locale: pt
+kiStatus: Fixed
+internalReference: 296066
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Quando tentamos ver os detalhes das reservas de um SKU no módulo de logística, na lista de inventário de produtos (**Inventory & Shipping** > **Inventory management**), podemos ter um problema quando há muitas reservas ativas.
+
+Não é possível acessar ou atualizar um inventário de SKU com uma grande quantidade de itens reservados, como, por exemplo, 100.000 reservas ativas.
+
+O usuário pode ver na interface do usuário o erro: **"Erro ao tentar buscar a reserva "**
+
+Ou, nos detalhes da resposta da API, o erro: **"Muitas reservas ativas "**
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md b/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
new file mode 100644
index 000000000..09ba8021b
--- /dev/null
+++ b/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
@@ -0,0 +1,45 @@
+---
+title: 'Texto mal formatado para títulos de pesquisa e breadcrumbs em cenários específicos com regras de merchandising'
+id: 3dQskVnI1sbF6jgsopjUUt
+status: PUBLISHED
+createdAt: 2024-03-13T20:52:33.781Z
+updatedAt: 2024-03-13T20:52:34.698Z
+publishedAt: 2024-03-13T20:52:34.698Z
+firstPublishedAt: 2024-03-13T20:52:34.698Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: texto-mal-formatado-para-titulos-de-pesquisa-e-breadcrumbs-em-cenarios-especificos-com-regras-de-merchandising
+locale: pt
+kiStatus: Backlog
+internalReference: 999476
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas páginas de resultados de pesquisa ocultam os filtros aplicados - já que eles já fazem parte da própria página, portanto, são definidos como "initialAttributes" - para se concentrar nos filtros adicionais que podem ser aplicados. Nesses cenários, os valores do título da página e dos breadcrumbs são basicamente definidos pelo primeiro produto da página.
+
+As regras de merchandising que colocam produtos de diferentes contextos nas primeiras posições de uma página afetam essa string. Quando os "initialAttributes" da página não correspondem a nenhum dos atributos do primeiro produto, como alternativa, esses textos são definidos pela slug - um texto simplificado sem capitalização, diacríticos ou outros caracteres especiais.
+
+Lembre-se de que esse tipo de regra de merchandising pode ser uma prática ruim.
+
+## Simulação
+
+
+
+- Considere uma categoria com a árvore "Food > Fruits > Apples and Pears" (Alimentos > Frutas > Maçãs e Peras), que se traduz em "Maçãs e Peras" em português (portanto, temos diacríticos/acentos para um exemplo melhor);
+- Adicionar um produto de uma árvore de categoria diferente por meio de uma regra de merchandising, como um fatiador da categoria "Cozinha > Acessórios > Fatiadores" à categoria "Alimentos > Frutas";
+- Como o primeiro produto da categoria "Maçãs e Peras" será esse cortador, o título da página e as migalhas de pão serão apresentados como "Maçãs e Peras"
+
+## Workaround
+
+
+N/A
+
+
diff --git a/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md b/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
new file mode 100644
index 000000000..843c79452
--- /dev/null
+++ b/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
@@ -0,0 +1,35 @@
+---
+title: 'A matriz Benefits.items dentro do ProductContextProvider embaralha os itens quando a promoção é do tipo Buy Together'
+id: 1VeBqJAKwpVR5YHqtEJ7Xz
+status: PUBLISHED
+createdAt: 2023-10-05T19:57:59.828Z
+updatedAt: 2023-10-05T19:58:00.724Z
+publishedAt: 2023-10-05T19:58:00.724Z
+firstPublishedAt: 2023-10-05T19:58:00.724Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: a-matriz-benefitsitems-dentro-do-productcontextprovider-embaralha-os-itens-quando-a-promocao-e-do-tipo-buy-together
+locale: pt
+kiStatus: Backlog
+internalReference: 915213
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao examinar a matriz de benefícios dentro do ProductContextProvider no PDP de um produto, podemos ver que nem todos os produtos são retornados e os que são retornados são embaralhados. As duas listas de produtos dentro da promoção estão juntas na mesma matriz. Isso só acontece quando a promoção é do tipo Buy Together.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md b/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md
new file mode 100644
index 000000000..687691efb
--- /dev/null
+++ b/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md
@@ -0,0 +1,51 @@
+---
+title: 'O filtro booleano no aplicativo de formulário não funciona corretamente'
+id: 4x77xCLrvU4gDWZ4s1faHw
+status: PUBLISHED
+createdAt: 2023-10-11T21:15:13.342Z
+updatedAt: 2023-10-11T21:31:06.894Z
+publishedAt: 2023-10-11T21:31:06.894Z
+firstPublishedAt: 2023-10-11T21:15:13.935Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: o-filtro-booleano-no-aplicativo-de-formulario-nao-funciona-corretamente
+locale: pt
+kiStatus: Backlog
+internalReference: 918537
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um filtro booleano é selecionado, a seguinte mensagem é retornada:
+Ocorreu um erro inesperado. Tente novamente. Se o problema persistir, entre em contato com o suporte.
+ ![](https://vtexhelp.zendesk.com/attachments/token/HAwA6Uf51x49bxGLiziKpdQnj/?name=image.png)
+
+## Simulação
+
+
+
+- Acesse o CRM de dados mestre (por exemplo, https://my-account-here.vtexcrm.com.br);
+- Acessar um aplicativo de formulário com opção de filtro booleano:
+ ![](https://vtexhelp.zendesk.com/attachments/token/tyRYoZP61rVzhVBx3A1rHbGgf/?name=image.png)
+
+- Selecione 0 ou 1 opção;
+- Clique no botão "_Filtro_";
+- Uma mensagem pop-up será aberta com o erro "`Ocorreu um erro inesperado. Tente novamente. Se o problema persistir, entre em contato com o suporte.`":
+ ![](https://vtexhelp.zendesk.com/attachments/token/HAwA6Uf51x49bxGLiziKpdQnj/?name=image.png)
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md b/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
index 2f5b7b876..b882ecf9e 100644
--- a/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
+++ b/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
@@ -3,8 +3,8 @@ title: 'Propriedades Booleanas de Vídeo/Áudio HTML não validadas no CMS Legac
 id: 2WjsLZ7vw0KO023rGQd77L
 status: PUBLISHED
 createdAt: 2022-03-16T19:27:06.599Z
-updatedAt: 2022-11-25T22:10:23.568Z
-publishedAt: 2022-11-25T22:10:23.568Z
+updatedAt: 2024-02-16T20:28:59.288Z
+publishedAt: 2024-02-16T20:28:59.288Z
 firstPublishedAt: 2022-03-16T19:27:07.097Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: propriedades-booleanas-de-videoaudio-html-nao-validadas-no-cms-legacy
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 491898
 ---
 
diff --git a/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md b/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
new file mode 100644
index 000000000..878e3acf4
--- /dev/null
+++ b/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
@@ -0,0 +1,40 @@
+---
+title: 'As marcas com alguns caracteres especiais não podem ser pesquisadas no administrador da marca'
+id: 296otMWGge4c2LJMvVhKEr
+status: PUBLISHED
+createdAt: 2024-01-04T13:57:15.861Z
+updatedAt: 2024-02-16T20:26:37.632Z
+publishedAt: 2024-02-16T20:26:37.632Z
+firstPublishedAt: 2024-01-04T13:57:16.584Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-marcas-com-alguns-caracteres-especiais-nao-podem-ser-pesquisadas-no-administrador-da-marca
+locale: pt
+kiStatus: No Fix
+internalReference: 503496
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A interface do usuário da marca, `.myvtex.com/admin/Site/Marca.aspx`, não permite que os usuários pesquisem marcas com alguns caracteres especiais no nome, como apóstrofos `'`. Além disso, letras de alfabetos não latinos também não podem ser pesquisadas, por exemplo, do alfabeto polonês, como `Ż`.
+
+## Simulação
+
+
+- Pesquise qualquer marca com apóstrofos na UI da marca;
+- A pesquisa não encontrará marcas com apóstrofos.
+
+
+
+## Workaround
+
+
+Não há solução alternativa.
+
diff --git a/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md b/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
index 71d7340f6..89b4655f6 100644
--- a/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
+++ b/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
@@ -3,8 +3,8 @@ title: 'Emissora que não notifica todas as mudanças de estoque no módulo de B
 id: XLozPnuonjPImtZa8bWAz
 status: PUBLISHED
 createdAt: 2022-10-24T12:26:59.536Z
-updatedAt: 2023-03-29T13:40:37.657Z
-publishedAt: 2023-03-29T13:40:37.657Z
+updatedAt: 2023-07-05T17:37:16.708Z
+publishedAt: 2023-07-05T17:37:16.708Z
 firstPublishedAt: 2022-10-24T12:27:00.490Z
 contentType: knownIssue
 productTeam: Intelligent Search
diff --git a/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md b/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md
index fe68aaa27..b10e2be9e 100644
--- a/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md
+++ b/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md
@@ -3,8 +3,8 @@ title: 'Buscacep não trabalha em forma de GiftList.'
 id: 3VRPSO1wYFX5XWrpTSD78X
 status: PUBLISHED
 createdAt: 2022-11-02T13:00:43.442Z
-updatedAt: 2022-11-25T21:42:09.907Z
-publishedAt: 2022-11-25T21:42:09.907Z
+updatedAt: 2024-02-16T20:29:33.235Z
+publishedAt: 2024-02-16T20:29:33.235Z
 firstPublishedAt: 2022-11-02T13:00:44.422Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: buscacep-nao-trabalha-em-forma-de-giftlist
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 342418
 ---
 
diff --git a/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index 465c1f09d..6572c7dca 100644
--- a/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -3,8 +3,8 @@ title: 'Botão "Cancelar" dentro da página MyCards não traduzido para o espanh
 id: 5wIEEoF7gTLYlWnANxDZ7h
 status: PUBLISHED
 createdAt: 2022-02-24T13:18:00.062Z
-updatedAt: 2022-11-25T22:07:29.627Z
-publishedAt: 2022-11-25T22:07:29.627Z
+updatedAt: 2024-02-16T20:25:05.684Z
+publishedAt: 2024-02-16T20:25:05.684Z
 firstPublishedAt: 2022-02-24T13:18:00.593Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: botao-cancelar-dentro-da-pagina-mycards-nao-traduzido-para-o-espanhol
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 431200
 ---
 
diff --git a/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md b/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
new file mode 100644
index 000000000..5734378c1
--- /dev/null
+++ b/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
@@ -0,0 +1,35 @@
+---
+title: 'Os botões podem não funcionar na primeira tentativa no administrador de limpeza completa'
+id: 4spOMbnKZPCcnQghKTP6Zb
+status: PUBLISHED
+createdAt: 2023-04-14T17:39:56.758Z
+updatedAt: 2024-06-17T13:39:35.332Z
+publishedAt: 2024-06-17T13:39:35.332Z
+firstPublishedAt: 2023-04-14T17:39:57.290Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: os-botoes-podem-nao-funcionar-na-primeira-tentativa-no-administrador-de-limpeza-completa
+locale: pt
+kiStatus: Backlog
+internalReference: 790828
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No administrador do Fullcleanup, espera-se que os botões ajam na primeira tentativa. No entanto, para executar a ação, pode ser necessário clicar no botão várias vezes.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md b/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
new file mode 100644
index 000000000..d68f75cba
--- /dev/null
+++ b/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
@@ -0,0 +1,46 @@
+---
+title: 'A promoção Buy Together com muitos SKUs pode fazer com que os produtos qualificados não sejam carregados na frente (tempo limite)'
+id: e1OJuUhZhYidnoRaDoDRc
+status: PUBLISHED
+createdAt: 2022-01-21T17:36:41.181Z
+updatedAt: 2024-02-16T20:29:59.287Z
+publishedAt: 2024-02-16T20:29:59.287Z
+firstPublishedAt: 2024-01-23T15:09:22.474Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: a-promocao-buy-together-com-muitos-skus-pode-fazer-com-que-os-produtos-qualificados-nao-sejam-carregados-na-frente-tempo-limite
+locale: pt
+kiStatus: No Fix
+internalReference: 301463
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A promoção Buy Together com muitos SKUs pode fazer com que os produtos qualificados não sejam carregados na frente devido ao tempo limite. As páginas de produto usam o controle de produto `<vtex.cmc:BuyTogether/>`. Esse controle é responsável por trazer informações de todos os SKUs qualificados definidos na promoção para a página do produto.
+
+O problema é que, se o cliente definir muitos SKUs nessa promoção, o Portal terá que trazer essas informações (preço, estoque etc.) de todos os produtos desses SKUs para a página do produto. E o Portal faz isso simulando seus produtos com o checkout. Se tivermos uma promoção que foi definida, por exemplo, com 50 SKUs, e esses SKUs são de produtos que têm pelo menos 5 SKUs por produto) e estão disponíveis, por exemplo, em 3 Canais de Vendas, o Portal terá que simular com o checkout cada SKU para cada SC de cada produto elegível nessa promoção apenas para mostrar essa página de produto específica. Nesse exemplo, o Portal terá que fazer 750 simulações com o checkout (50 SKUs definidos na promoção, assumindo que esses SKus são de produtos que têm 5 SKUs, são 250 SKUs, e todos devem ser simulados para cada SC, o que nos dá 750 simulações).
+
+ps: não temos um número correto para definir na lista de SKUs, pois isso dependerá de cada cliente. Se o cliente tiver produtos com poucos SKUs e apenas um SC disponível, ele poderá usar mais SKUs nesse tipo de promoção.
+
+## Simulação
+
+
+- Criar uma promoção Buy Together
+- Coloque na lista de SKUs 1 ou na lista de SKUs 2 muitos SKUs, como mais de 50.
+- Tente carregar a página do produto que usa o controle `<vtex.cmc:BuyTogether/>`, a página não deve ser carregada devido a um tempo limite
+
+## Workaround
+
+
+Há duas maneiras de "resolver" esse problema:
+- Remover o controle do modelo <vtex.cmc:BuyTogether/>, isso fará com que a página do produto não carregue as informações sobre esse produto disponíveis nessa promoção;
+- Usar menos SKUs na lista da promoção Buy Together. Mais uma vez, infelizmente, não temos um número específico que funcione. Aconselho o cliente a tentar com algo como 10 e começar a aumentar e testar.
+
+
diff --git a/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md b/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
new file mode 100644
index 000000000..0dd3fc320
--- /dev/null
+++ b/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
@@ -0,0 +1,43 @@
+---
+title: 'Os compradores não podem fazer login se houver uma configuração incorreta nas organizações/centros de custo'
+id: r5p7K15FkbZUDSOUQ6hGz
+status: PUBLISHED
+createdAt: 2023-11-30T22:21:39.852Z
+updatedAt: 2023-12-01T20:19:35.375Z
+publishedAt: 2023-12-01T20:19:35.375Z
+firstPublishedAt: 2023-11-30T22:21:40.638Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: os-compradores-nao-podem-fazer-login-se-houver-uma-configuracao-incorreta-nas-organizacoescentros-de-custo
+locale: pt
+kiStatus: Backlog
+internalReference: 945609
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário tem a primeira organização atribuída a ele inválida com o ID do centro de custo errado, o login falha sem nenhuma mensagem.
+
+Haverá a mensagem `"App storefront-permissions failed, resulting in an error building the session"` na resposta da sessão.
+
+## Simulação
+
+
+
+- Crie uma organização com o ID de centro de custo incorreto;
+- Faça login no site
+
+## Workaround
+
+
+Corrija o ID do centro de custo associado à organização ou exclua a organização.
+
+
+
diff --git a/docs/known-issues/pt/calculation-issue-in-comissionamount.md b/docs/known-issues/pt/calculation-issue-in-comissionamount.md
new file mode 100644
index 000000000..883c193a3
--- /dev/null
+++ b/docs/known-issues/pt/calculation-issue-in-comissionamount.md
@@ -0,0 +1,40 @@
+---
+title: 'Problema de cálculo em comissionAmount'
+id: 1E8DRneWHVncTu5bZ9hNtF
+status: PUBLISHED
+createdAt: 2024-03-15T21:13:28.729Z
+updatedAt: 2024-03-15T21:13:29.705Z
+publishedAt: 2024-03-15T21:13:29.705Z
+firstPublishedAt: 2024-03-15T21:13:29.705Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: problema-de-calculo-em-comissionamount
+locale: pt
+kiStatus: Backlog
+internalReference: 1001005
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Isso ocorre em um cenário específico de divisão de pagamento com vários pagamentos e vendedores (em que ambos são responsáveis por encargos de processamento de pagamento e estornos). A soma do `comissionAmount` dos vendedores não é igual ao `amount` do marketplace (problema de arredondamento), essa diferença pode causar uma recusa de liquidação pelo adquirente.
+
+## Simulação
+
+
+Não foi possível simular esse problema, pois ele envolve várias condições
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md b/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
new file mode 100644
index 000000000..927e08986
--- /dev/null
+++ b/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
@@ -0,0 +1,45 @@
+---
+title: 'O e-mail do operador do call center é enviado para o orderForm ao adicionar itens ao carrinho no front-end do Store Framework'
+id: 3KwP4q7VZsu6e3c1DwWY5t
+status: PUBLISHED
+createdAt: 2024-07-16T20:06:11.748Z
+updatedAt: 2024-07-16T20:06:12.844Z
+publishedAt: 2024-07-16T20:06:12.844Z
+firstPublishedAt: 2024-07-16T20:06:12.844Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-email-do-operador-do-call-center-e-enviado-para-o-orderform-ao-adicionar-itens-ao-carrinho-no-frontend-do-store-framework
+locale: pt
+kiStatus: Backlog
+internalReference: 1066571
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar os componentes do Store Framework para adicionar itens a um carrinho enquanto estiver conectado como um operador de call center e não estiver se passando por um cliente, o e-mail do operador é preenchido no anexo clientProfileData do formulário de pedido.
+
+## Simulação
+
+
+
+1. Acesse uma loja criada no Store Framework.
+2. Autentique-se como um operador de call center.
+3. Sem se passar por nenhum cliente, adicione um item ao carrinho com um componente como o botão add-to-cart.
+4. Verifique se o carrinho agora contém o endereço de e-mail do operador da central de atendimento
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md b/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
new file mode 100644
index 000000000..0c9ee9a43
--- /dev/null
+++ b/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
@@ -0,0 +1,42 @@
+---
+title: 'As chamadas de retorno após a aprovação podem acionar o PaymentAuthorizationWorker para tentar novamente o pagamento, o que também pode negá-lo.'
+id: 1dbTbMRMvJQaxzXjWwQplD
+status: PUBLISHED
+createdAt: 2023-09-15T18:22:54.533Z
+updatedAt: 2023-09-15T18:22:55.496Z
+publishedAt: 2023-09-15T18:22:55.496Z
+firstPublishedAt: 2023-09-15T18:22:55.496Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: as-chamadas-de-retorno-apos-a-aprovacao-podem-acionar-o-paymentauthorizationworker-para-tentar-novamente-o-pagamento-o-que-tambem-pode-negalo
+locale: pt
+kiStatus: Backlog
+internalReference: 740499
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o provedor envia um retorno de chamada logo após a autorização, ele pode acionar uma nova tentativa de autorização. Portanto, em alguns casos, quando a transação tiver mais de um pagamento e um deles for um cartão-presente, uma nova tentativa de autorização poderá cancelar a transação quando ela não tiver fundos.
+
+## Simulação
+
+
+Não pode ser simulado, pois depende do retorno de chamada do provedor.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
new file mode 100644
index 000000000..4107cc932
--- /dev/null
+++ b/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -0,0 +1,36 @@
+---
+title: 'IU do público-alvo da campanha alterando "Diferente de" para "Igual a" com uma coleção'
+id: 6IkWioZ9WRgg1DFEMdnthB
+status: PUBLISHED
+createdAt: 2023-08-15T15:12:54.580Z
+updatedAt: 2023-08-15T15:18:11.108Z
+publishedAt: 2023-08-15T15:18:11.108Z
+firstPublishedAt: 2023-08-15T15:12:55.461Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: iu-do-publicoalvo-da-campanha-alterando-diferente-de-para-igual-a-com-uma-colecao
+locale: pt
+kiStatus: Backlog
+internalReference: 881131
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao criar um público-alvo e definir Coleções **Diferente de**, essa opção é salva na interface do usuário; depois de retornar ao público-alvo, ela será exibida como Igual a na interface do usuário, mas manterá sua primeira opção na API.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md b/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md
index 248fe3105..9dfc4c127 100644
--- a/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md
+++ b/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md
@@ -3,8 +3,8 @@ title: 'O botão Salvar do CampoValorForm.aspx requer dois cliques'
 id: G0YtmOpdB4nNdw8w87ZNz
 status: PUBLISHED
 createdAt: 2022-02-16T13:28:52.922Z
-updatedAt: 2022-11-25T21:45:10.712Z
-publishedAt: 2022-11-25T21:45:10.712Z
+updatedAt: 2024-02-16T20:26:25.672Z
+publishedAt: 2024-02-16T20:26:25.672Z
 firstPublishedAt: 2022-02-16T13:28:53.505Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: o-botao-salvar-do-campovalorformaspx-requer-dois-cliques
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 525616
 ---
 
diff --git a/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md b/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md
new file mode 100644
index 000000000..281463dc3
--- /dev/null
+++ b/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md
@@ -0,0 +1,46 @@
+---
+title: 'As tags canônicas não são aplicadas após o terceiro nível de categoria'
+id: 6HU8WLT5yVRBqeBmGgYRsi
+status: PUBLISHED
+createdAt: 2023-11-08T13:31:23.182Z
+updatedAt: 2024-02-19T19:24:10.757Z
+publishedAt: 2024-02-19T19:24:10.757Z
+firstPublishedAt: 2023-11-08T13:31:24.275Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: as-tags-canonicas-nao-sao-aplicadas-apos-o-terceiro-nivel-de-categoria
+locale: pt
+kiStatus: Backlog
+internalReference: 932349
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As tags canônicas não são aplicadas após o terceiro nível de categoria quando há uma árvore de categorias com mais de três níveis (departamento, categoria e subcategoria), os outros níveis acima não são exibidos na canônica
+
+## Simulação
+
+
+
+1. Crie qualquer subcategoria de 4º nível
+2. Acesse a página criada
+3. Verifique a Canonical para ela no console. Ela não mostrará nada após o terceiro nível. Somente o terceiro e os seguintes.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md b/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md
new file mode 100644
index 000000000..f31cccf3c
--- /dev/null
+++ b/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md
@@ -0,0 +1,43 @@
+---
+title: 'Não é possível editar o nome do modelo Styles'
+id: 5czxRVaMCZFgvOadfYKl1h
+status: PUBLISHED
+createdAt: 2023-08-16T17:41:40.059Z
+updatedAt: 2023-08-16T17:41:41.113Z
+publishedAt: 2023-08-16T17:41:41.113Z
+firstPublishedAt: 2023-08-16T17:41:41.113Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: nao-e-possivel-editar-o-nome-do-modelo-styles
+locale: pt
+kiStatus: Backlog
+internalReference: 882147
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Depois de criar um novo estilo no módulo Styles, não é possível editar seu nome.
+
+## Simulação
+
+
+Crie seu modelo de estilo no módulo Styles e salve-o. Tente editar seu nome. Tente editar seu nome e você verá que não há opção para isso.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md b/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md
new file mode 100644
index 000000000..f9f26fac7
--- /dev/null
+++ b/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md
@@ -0,0 +1,42 @@
+---
+title: 'Marcas de cartão processadas incorretamente como Visa'
+id: 7xXie4JWGLWe0ImmHAHzSy
+status: PUBLISHED
+createdAt: 2024-04-30T13:28:23.035Z
+updatedAt: 2024-04-30T20:35:47.075Z
+publishedAt: 2024-04-30T20:35:47.075Z
+firstPublishedAt: 2024-04-30T13:28:24.008Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: marcas-de-cartao-processadas-incorretamente-como-visa
+locale: pt
+kiStatus: Backlog
+internalReference: 1024823
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns cartões de crédito podem ser processados como Visa quando, na verdade, são de outra marca.
+
+## Simulação
+
+
+Não foi possível replicar esse problema; ele parece ocorrer em dispositivos móveis e cartões salvos.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md b/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md
index 79f9e404c..b21fd443c 100644
--- a/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md
+++ b/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md
@@ -3,8 +3,8 @@ title: 'O card do Facebook não salva algumas configurações'
 id: 4MTMozT5bmub7Y96TXCl09
 status: PUBLISHED
 createdAt: 2022-03-23T18:52:58.216Z
-updatedAt: 2022-12-02T18:05:07.099Z
-publishedAt: 2022-12-02T18:05:07.099Z
+updatedAt: 2024-02-16T20:26:09.791Z
+publishedAt: 2024-02-16T20:26:09.791Z
 firstPublishedAt: 2022-03-23T18:52:58.849Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: o-facebook-do-cartao-nao-salva-algumas-configuracoes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 548763
 ---
 
diff --git a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
new file mode 100644
index 000000000..06ad0d1ab
--- /dev/null
+++ b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
@@ -0,0 +1,47 @@
+---
+title: 'O carrinho criado a partir de um pedido antigo não traz as opções de montagem'
+id: 530zUKzAm8oafA8BKl7G8F
+status: PUBLISHED
+createdAt: 2024-04-19T20:21:41.131Z
+updatedAt: 2024-04-19T20:21:42.184Z
+publishedAt: 2024-04-19T20:21:42.184Z
+firstPublishedAt: 2024-04-19T20:21:42.184Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-carrinho-criado-a-partir-de-um-pedido-antigo-nao-traz-as-opcoes-de-montagem
+locale: pt
+kiStatus: Backlog
+internalReference: 1020278
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar um carrinho a partir de um pedido antigo (botão "Pedir novamente" na tela "Meus pedidos"), as opções de montagem do pedido original não serão mantidas.
+
+## Simulação
+
+
+
+1. Faça o pedido de um produto com opções de montagem;
+2. Acesse a tela "My orders" (Meus pedidos);
+3. Clique em "Order again";
+4. Observe que o carrinho que foi gerado em seguida trouxe apenas os SKUs do pedido anterior, sem as respectivas montagens.
+
+
+
+## Workaround
+
+
+Atualmente, não há solução alternativa para esse cenário.
+
+
+
+
+
diff --git a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
index 4d7ead6ec..e23a283fd 100644
--- a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
+++ b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
@@ -3,8 +3,8 @@ title: 'O carrinho criado a partir de um pedido antigo não traz os anexos'
 id: 2TGthMyZOUQWkc2Wo6wgIg
 status: PUBLISHED
 createdAt: 2019-01-08T16:58:19.057Z
-updatedAt: 2023-05-08T18:33:57.918Z
-publishedAt: 2023-05-08T18:33:57.918Z
+updatedAt: 2024-07-01T18:49:01.443Z
+publishedAt: 2024-07-01T18:49:01.443Z
 firstPublishedAt: 2019-01-08T18:21:16.502Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-carrinho-criado-a-partir-de-um-pedido-antigo-nao-traz-os-anexos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 802464
 ---
 
diff --git a/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
new file mode 100644
index 000000000..17876d77b
--- /dev/null
+++ b/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -0,0 +1,52 @@
+---
+title: 'Carrinho criado a partir de uma opção "pedir novamente" em Meus pedidos, o e-mail do cliente não está sendo colocado como esperado no formulário de pedido'
+id: 6dDhkaIhquOqaDuNkVZuln
+status: PUBLISHED
+createdAt: 2023-12-04T22:41:21.385Z
+updatedAt: 2023-12-04T22:41:22.139Z
+publishedAt: 2023-12-04T22:41:22.139Z
+firstPublishedAt: 2023-12-04T22:41:22.139Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: carrinho-criado-a-partir-de-uma-opcao-pedir-novamente-em-meus-pedidos-o-email-do-cliente-nao-esta-sendo-colocado-como-esperado-no-formulario-de-pedido
+locale: pt
+kiStatus: Backlog
+internalReference: 947563
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Na seção **My Orders** (Meus pedidos) em **My Account** (Minha conta), há a opção de configurar um carrinho com base em um pedido que o cliente fez anteriormente.
+
+Nesse caso, o problema é que, em um **fluxo de televendas**, ao **pessoar o cliente e tentar montar um carrinho com base em um pedido anterior**, ao clicar em **My Orders (List)** na opção "**Order again**", o e-mail do agente de televendas é colocado nos dados do perfil do cliente do formulário de pedido, e não do cliente, como esperado.
+
+Vale a pena mencionar que esse comportamento só acontece quando se clica no botão "pedir novamente" na lista de pedidos Meus pedidos.
+
+## Simulação
+
+
+
+1. Faça login com um usuário de televendas
+2. Fazer-se passar por um cliente
+3. Vá para a seção My Orders (Meus pedidos) em My Account (Minha conta)
+4. Na lista de pedidos, clique em "order again" em qualquer um deles.
+5. Valide as informações do cliente no formulário de pedido (clientProfileData.email
+
+## Workaround
+
+
+
+Para fazer pedidos com base em um pedido antigo, é recomendável inserir os detalhes do pedido primeiro e, em seguida, clicar na opção "order again" (fazer novo pedido).
+
+
+
+
+
diff --git a/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md b/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
new file mode 100644
index 000000000..3faa256ef
--- /dev/null
+++ b/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
@@ -0,0 +1,41 @@
+---
+title: 'item.deliveryType do carrinho não foi enviado pelo checkout em AdditionalData'
+id: lV8VxXUPOzO9cSMgNV4fj
+status: PUBLISHED
+createdAt: 2024-03-19T12:59:17.599Z
+updatedAt: 2024-03-19T12:59:18.450Z
+publishedAt: 2024-03-19T12:59:18.450Z
+firstPublishedAt: 2024-03-19T12:59:18.450Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: itemdeliverytype-do-carrinho-nao-foi-enviado-pelo-checkout-em-additionaldata
+locale: pt
+kiStatus: Backlog
+internalReference: 1002115
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando há uma divisão de quantidade na `priceDefinition` devido ao arredondamento do multiplicador de unidades, o gateway não pode receber nenhum valor para `deliveryType` no objeto do carrinho. Portanto, isso pode fazer com que o provedor de pagamento negue o pagamento se ele usar esse campo...
+
+## Simulação
+
+
+
+- Faça um pedido com um carrinho com uma quantidade dividida no campo `priceDefinition` no formulário de pedido;
+- Verifique o "miniCart.Items", ele pode não ter o ``deliveryType`
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md b/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md
new file mode 100644
index 000000000..2c01f9a87
--- /dev/null
+++ b/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md
@@ -0,0 +1,45 @@
+---
+title: 'Os Itens do carrinho são mantidos em ordens com valor total zero'
+id: 66D6RuacgCeCMQDmLPrlNP
+status: PUBLISHED
+createdAt: 2024-06-24T20:59:07.721Z
+updatedAt: 2024-06-24T20:59:08.668Z
+publishedAt: 2024-06-24T20:59:08.668Z
+firstPublishedAt: 2024-06-24T20:59:08.668Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-itens-do-carrinho-sao-mantidos-em-ordens-com-valor-total-zero
+locale: pt
+kiStatus: Backlog
+internalReference: 1054999
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Sempre que um carrinho tiver um valor total de "0", nenhuma transação será criada ao finalizar um pedido.  Ao concluir um pedido por meio da interface do usuário do checkout, não ocorre nenhuma solicitação de processamento de pedido, portanto, os itens e os dados do carrinho são mantidos e o comprador pode criar um pedido com o mesmo carrinho novamente.
+
+## Simulação
+
+
+
+- Crie um carrinho com valor total `0`;
+- Concluir a compra;
+- Acesse novamente o carrinho depois de algum tempo; não haverá alteração no conteúdo do carrinho.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
diff --git a/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md b/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
new file mode 100644
index 000000000..3d5643b6f
--- /dev/null
+++ b/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
@@ -0,0 +1,43 @@
+---
+title: 'O carrinho com endereços de vários países perde o endereço de retirada se a loja não puder enviar para todos os países'
+id: 5yDJ05btQxQq8BuZzfopqv
+status: PUBLISHED
+createdAt: 2024-07-19T15:02:39.647Z
+updatedAt: 2024-07-19T15:02:41.579Z
+publishedAt: 2024-07-19T15:02:41.579Z
+firstPublishedAt: 2024-07-19T15:02:41.579Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-carrinho-com-enderecos-de-varios-paises-perde-o-endereco-de-retirada-se-a-loja-nao-puder-enviar-para-todos-os-paises
+locale: pt
+kiStatus: Backlog
+internalReference: 1068197
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se um comprador tiver vários endereços em seu perfil de diferentes países e a loja não fizer entregas em nenhum desses endereços, ao selecionar a retirada em um endereço válido e passar para a etapa de pagamento, a interface do usuário do checkout redirecionará o comprador de volta para a etapa de envio.
+
+## Simulação
+
+
+
+- Registre endereços de um país para o qual a loja não oferece entrega;
+- Vá para o checkout e selecione um endereço válido com o país para o qual a loja faz entregas;
+- Clique em "Go to payment" (Ir para pagamento)
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md b/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
new file mode 100644
index 000000000..6a065b931
--- /dev/null
+++ b/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
@@ -0,0 +1,45 @@
+---
+title: 'Os carrinhos criados a partir da substituição de pedidos não recebem promoções corretamente'
+id: 2ODIE9RNP7Q5LCglXsztzf
+status: PUBLISHED
+createdAt: 2023-10-20T17:47:40.494Z
+updatedAt: 2023-10-20T17:47:41.099Z
+publishedAt: 2023-10-20T17:47:41.099Z
+firstPublishedAt: 2023-10-20T17:47:41.099Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-carrinhos-criados-a-partir-da-substituicao-de-pedidos-nao-recebem-promocoes-corretamente
+locale: pt
+kiStatus: Backlog
+internalReference: 473424
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os carrinhos criados a partir de pedidos existentes por meio da funcionalidade "substituir pedidos" apresentada na página "meus pedidos" estão restritos à promoção original, mas sem considerar que a mesma promoção pode se aplicar a diferentes contextos, como diferentes métodos de pagamento ou opções de envio.
+
+## Simulação
+
+
+
+- Tenha uma promoção para vários métodos de pagamento
+- Feche o pedido pagando com "A", que deve ter um desconto
+- Na tela Meus pedidos, escolha alterar o método de pagamento do pedido
+- De volta ao carrinho, escolha pagar com "B"
+- O desconto não será exibid
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md b/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md
new file mode 100644
index 000000000..c02a1c158
--- /dev/null
+++ b/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md
@@ -0,0 +1,51 @@
+---
+title: 'As promoções de reembolso não consideram os itens removidos dos pedidos'
+id: lm9v37jvUSCeh9FVFHjsr
+status: PUBLISHED
+createdAt: 2024-04-19T13:50:10.264Z
+updatedAt: 2024-04-19T13:50:11.130Z
+publishedAt: 2024-04-19T13:50:11.130Z
+firstPublishedAt: 2024-04-19T13:50:11.130Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-promocoes-de-reembolso-nao-consideram-os-itens-removidos-dos-pedidos
+locale: pt
+kiStatus: Backlog
+internalReference: 1019864
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, ao usar promoções de cashback, os cálculos são totalmente realizados no momento em que os itens são inseridos no carrinho.
+
+Portanto, quaisquer alterações nos pedidos feitas depois disso não são consideradas. Consequentemente, os pedidos que removeram itens e só consideram a aplicação do cashback após uma fatura, o principal caso para esse problema, ainda levarão em conta o cashback do item removido, mesmo que ele tenha sido removido.
+
+## Simulação
+
+
+1 - Crie uma promoção de cashback de 10%, restrita apenas a você (para evitar aplicações incorretas) e com a condição de faturamento para aplicar os créditos.
+
+2 - Feche um pedido de US$ 100 composto por 2 itens: um que custa US$ 80 e o outro US$ 20.
+
+3 - Os créditos aplicados devem ser de US$ 10. Remova o item de US$ 8 do pedido e fature-o.
+
+4 - Você ainda receberá o crédito de $10 como cashback, apesar de o valor esperado agora ser de $2, o que acontece porque os cálculos da promoção são feitos durante a simulação do checkout, antes de o pedido ser fechado.
+
+
+
+## Workaround
+
+
+Não há solução alternativa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md b/docs/known-issues/pt/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
index ed658739c..5654c66e5 100644
--- a/docs/known-issues/pt/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
+++ b/docs/known-issues/pt/catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return.md
@@ -3,8 +3,8 @@ title: 'Catalog API /catalog/pvt/stockkeepingunit with query parameter refId ret
 id: 71Y9CFaM10xaVyQkcgKydQ
 status: PUBLISHED
 createdAt: 2022-01-21T15:28:34.187Z
-updatedAt: 2022-12-22T15:16:11.363Z
-publishedAt: 2022-12-22T15:16:11.363Z
+updatedAt: 2024-02-16T20:24:19.402Z
+publishedAt: 2024-02-16T20:24:19.402Z
 firstPublishedAt: 2022-12-22T15:16:11.363Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalog-api-catalog-pvt-stockkeepingunit-with-query-parameter-refid-return
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 388869
 ---
 
diff --git a/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md b/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
new file mode 100644
index 000000000..53d50e4a6
--- /dev/null
+++ b/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
@@ -0,0 +1,45 @@
+---
+title: 'A API do catálogo não responde adequadamente ao espaço no final das cadeias de caracteres'
+id: 37TmHtc19126iarlQ4IL2p
+status: PUBLISHED
+createdAt: 2024-02-05T16:49:35.136Z
+updatedAt: 2024-07-01T18:49:25.845Z
+publishedAt: 2024-07-01T18:49:25.845Z
+firstPublishedAt: 2024-02-05T16:49:36.178Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-api-do-catalogo-nao-responde-adequadamente-ao-espaco-no-final-das-cadeias-de-caracteres
+locale: pt
+kiStatus: No Fix
+internalReference: 977033
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar a coleção de APIs de catálogo, se um campo JSON de cadeia de caracteres for enviado terminando com espaços (por exemplo, productName: "myProductName"), as APIs de catálogo responderão com uma resposta 400 imprópria e um corpo de resposta vazio, deixando o usuário sem saber o que foi enviado de forma imprópria.
+
+A resposta correta ainda deve ser 400 (solicitação incorreta), mas com um tratamento de erro informando qual campo está incorreto e por quê.
+
+## Simulação
+
+
+Para qualquer API de catálogo (https://developers.vtex.com/docs/api-reference/catalog-api), insira mais de 1 espaço vazio no final de um campo de string, como exemplificado acima.
+
+## Workaround
+
+
+n/a
+
+Esse tipo de string não deve ser aceito, mas o tratamento de erros deve ser ajustado.
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md b/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md
new file mode 100644
index 000000000..6877ce106
--- /dev/null
+++ b/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md
@@ -0,0 +1,45 @@
+---
+title: 'A exportação do catálogo não pode manipular caracteres ț e ș.'
+id: 1c28limdEHowD4LKDeHAB1
+status: PUBLISHED
+createdAt: 2023-12-11T17:40:16.688Z
+updatedAt: 2023-12-11T17:40:17.536Z
+publishedAt: 2023-12-11T17:40:17.536Z
+firstPublishedAt: 2023-12-11T17:40:17.536Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-exportacao-do-catalogo-nao-pode-manipular-caracteres-t-e-s
+locale: pt
+kiStatus: Backlog
+internalReference: 950933
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, o catálogo de importação/exportação corta os caracteres especiais ț e ș ao exportar dados.
+
+## Simulação
+
+
+1 - Crie um produto que tenha ș em seu nome.
+
+2 - Na guia de exportação do módulo de catálogo, tente exportar uma planilha.
+
+3 - Esse caractere não será mostrado na planilha exportada
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md b/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md
new file mode 100644
index 000000000..cfd018dfd
--- /dev/null
+++ b/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md
@@ -0,0 +1,51 @@
+---
+title: 'Exportação de catálogo para cortes de anexos > 50 caracteres'
+id: 7hX23y19wmMNPTUgbhh2WX
+status: PUBLISHED
+createdAt: 2023-12-14T16:46:58.819Z
+updatedAt: 2023-12-14T16:46:59.522Z
+publishedAt: 2023-12-14T16:46:59.522Z
+firstPublishedAt: 2023-12-14T16:46:59.522Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: exportacao-de-catalogo-para-cortes-de-anexos-50-caracteres
+locale: pt
+kiStatus: Backlog
+internalReference: 953161
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao importar dados para anexos no módulo de catálogo, se o referido anexo tiver mais de 50 caracteres, a cadeia de caracteres é cortada, o que faz com que não haja atualizações para esses dados.
+
+## Simulação
+
+
+1 - Crie um anexo com um nome de mais de 50 caracteres, por exemplo, "Esse é um nome de anexo muito longo criado para testar um problema".
+
+2 - Associe-o a um produto
+
+3 - exportar esses dados usando a interface do usuário /admin/Site/Relatorio_Skus.aspx
+
+4 - Verifique a coluna relacionada a isso e ela será exibida como "`Este é um nome de anexo muito longo que é criado`" (exatamente com 50 caracteres).
+
+5 - Você precisará ajustar manualmente essas informações se quiser importá-las corretamente
+
+
+
+## Workaround
+
+
+Atualize os anexos por meio da API, da interface do usuário ou altere manualmente a string incorreta na planilha.
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-filters-timeout.md b/docs/known-issues/pt/catalog-filters-timeout.md
new file mode 100644
index 000000000..d612fa3cc
--- /dev/null
+++ b/docs/known-issues/pt/catalog-filters-timeout.md
@@ -0,0 +1,45 @@
+---
+title: 'Tempo limite dos filtros do catálogo'
+id: 5KtT2SvTSO6xMdJOSYz5VZ
+status: PUBLISHED
+createdAt: 2023-10-19T17:11:37.486Z
+updatedAt: 2023-10-19T17:11:38.181Z
+publishedAt: 2023-10-19T17:11:38.181Z
+firstPublishedAt: 2023-10-19T17:11:38.181Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: tempo-limite-dos-filtros-do-catalogo
+locale: pt
+kiStatus: Backlog
+internalReference: 922350
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Para lojas com uma grande quantidade de skus (1 milhão ou mais), muitas vezes, ao filtrar usando os filtros da interface do usuário do catálogo, seja para o menu principal ou para a seção de relatórios, se a consulta de filtro retornar um resultado muito grande, a interface do usuário não funcionará mais (504 gateway timeout)
+
+## Simulação
+
+
+Não há uma maneira confiável de simular isso de forma consistente - apenas consultas grandes específicas para algumas contas acabam gerando o erro.
+
+
+
+## Workaround
+
+
+Solicite uma "limpeza de filtro de usuário" à equipe de produtos.
+
+Além disso, se a mesma consulta estiver gerando um tempo limite com frequência (ou seja, você filtra um departamento específico e o tempo limite é atingido), considere a possibilidade de executar filtros que selecionem um subconjunto do que você deseja (no mesmo exemplo, uma categoria dentro de um determinado departamento)
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md b/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md
new file mode 100644
index 000000000..1f11ce315
--- /dev/null
+++ b/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md
@@ -0,0 +1,43 @@
+---
+title: 'Catalog GraphQL CategoryInputTranslation não está funcionando'
+id: 1Zue7Roia2sYa4xNP9hF2y
+status: PUBLISHED
+createdAt: 2024-04-29T14:30:53.743Z
+updatedAt: 2024-04-29T14:30:54.577Z
+publishedAt: 2024-04-29T14:30:54.577Z
+firstPublishedAt: 2024-04-29T14:30:54.577Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: catalog-graphql-categoryinputtranslation-nao-esta-funcionando
+locale: pt
+kiStatus: Backlog
+internalReference: 1024172
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, o método CategoryInputTranslation, para o catálogo graphQL, não está gerando uma atualização nos dados traduzidos para as contas.
+
+## Simulação
+
+
+1 - Acesse o IDE graphQL da VTEX e selecione o aplicativo vtex.catalog-graphql@1.103.1
+2 - Crie uma mutação para o método CategoryInputTranslation
+3 - Verifique se essa atualização se refletiu nos dados traduzidos no sit
+
+## Workaround
+
+
+Em vez disso, use diretamente o aplicativo de mensagens da VTEX para traduzir os dados (vtex.messages)
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md b/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md
new file mode 100644
index 000000000..36e36c50e
--- /dev/null
+++ b/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md
@@ -0,0 +1,44 @@
+---
+title: 'Indexador de catálogo gerando documentos de tradução inválidos'
+id: 3pbXOA3DQILdu05tAwjlVM
+status: PUBLISHED
+createdAt: 2024-02-29T18:02:38.600Z
+updatedAt: 2024-07-01T18:49:27.852Z
+publishedAt: 2024-07-01T18:49:27.852Z
+firstPublishedAt: 2024-02-29T18:02:39.430Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: indexador-de-catalogo-gerando-documentos-de-traducao-invalidos
+locale: pt
+kiStatus: No Fix
+internalReference: 991494
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao indexar um produto com informações traduzidas, as mensagens do aplicativo são solicitadas. Essas solicitações devem ter menos de 3s e, quando demoram mais do que isso, a indexação falha e gera um documento de tradução inválido.
+
+
+## Simulação
+
+
+Não há uma maneira fácil de reproduzir esse cenário, mas as contas com muitos idiomas ou muitos campos para traduzir são mais suscetíveis a esse cenário.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
index 730caf73b..ace8e0823 100644
--- a/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
@@ -3,8 +3,8 @@ title: 'Erro de Cálculo da Seção "Total" do Relatório de Indexação do Cat
 id: 6TJXux104P2c0mruo5vlEn
 status: PUBLISHED
 createdAt: 2022-02-25T11:39:42.098Z
-updatedAt: 2022-11-25T21:45:40.741Z
-publishedAt: 2022-11-25T21:45:40.741Z
+updatedAt: 2024-02-16T20:26:35.750Z
+publishedAt: 2024-02-16T20:26:35.750Z
 firstPublishedAt: 2022-02-25T11:39:42.485Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: erro-de-calculo-da-secao-total-do-relatorio-de-indexacao-do-catalogo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 499450
 ---
 
diff --git a/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md b/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md
new file mode 100644
index 000000000..b0ec7b32e
--- /dev/null
+++ b/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md
@@ -0,0 +1,46 @@
+---
+title: 'O campo de código fiscal XML do Catalog Integration não está sendo renderizado'
+id: 19Ubw33gsHcyIeMUQA3LGh
+status: PUBLISHED
+createdAt: 2024-05-10T14:28:22.117Z
+updatedAt: 2024-05-10T14:28:23.190Z
+publishedAt: 2024-05-10T14:28:23.190Z
+firstPublishedAt: 2024-05-10T14:28:23.190Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-campo-de-codigo-fiscal-xml-do-catalog-integration-nao-esta-sendo-renderizado
+locale: pt
+kiStatus: Backlog
+internalReference: 1031109
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, a configuração XML do catálogo para o campo de código fiscal não está gerando os resultados esperados, pois sempre retorna um <![CDATA[]]>
+
+## Simulação
+
+
+1 - Registre um código fiscal em um produto de sua loja.
+2 - Na configuração XML de sua conta https://myaccountname.myvtex.com/admin/Site/Xml.aspx, configure o campo XML do código fiscal
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/LHjBFETlon2zWcRX7pXYF0xjP/?name=image.png)
+
+3 - Carregue o XML gerado e, apesar de o produto ter dados válidos, as tags do XML do código fiscal não carregarão conteúdo válido
+
+## Workaround
+
+
+Use outros meios de integração de catálogos se um código fiscal for absolutamente necessário nas operações de sua loja.
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md b/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md
new file mode 100644
index 000000000..8eed2ab14
--- /dev/null
+++ b/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md
@@ -0,0 +1,45 @@
+---
+title: 'API de pesquisa de catálogo limitada a 2500 resultados'
+id: 33kKjUGKN5tlxvksnbnw7n
+status: PUBLISHED
+createdAt: 2023-08-31T14:59:31.132Z
+updatedAt: 2023-08-31T14:59:31.766Z
+publishedAt: 2023-08-31T14:59:31.766Z
+firstPublishedAt: 2023-08-31T14:59:31.766Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: api-de-pesquisa-de-catalogo-limitada-a-2500-resultados
+locale: pt
+kiStatus: Backlog
+internalReference: 891184
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar a API Catalog Search, o máximo de resultados obtidos é 2500, mesmo que haja mais produtos.
+A paginação é de até 50 produtos e funciona corretamente até que o parâmetro _from atinja o número de 2500. Quando eles definem `_from` acima de 2500, obtêm `"O parâmetro _from não pode ser maior que 2500."`
+
+## Simulação
+
+
+Essa situação pode ocorrer ao solicitar a API usando o postman ou ao usar o catálogo compartilhado nas contas do portal do vendedor (ele usa a mesma API na interface do usuário).
+
+Ao usar a API: - faça a solicitação usando o paramenter `_from` acima 2500
+Ao usar o catálogo compartilhado: - pule a paginação na guia de produtos disponíveis até chegar a 2500. As próximas páginas não serão atualizadas e mostrarão os mesmos resultados que a página anterior a 2500
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md b/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
index af4565624..dae59fe0f 100644
--- a/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
+++ b/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
@@ -3,8 +3,8 @@ title: 'Facetas de busca na API do Catálogo não retornam informações para pr
 id: 1JrbscqI4BQgFqfVuRZIl8
 status: PUBLISHED
 createdAt: 2022-05-23T13:58:53.501Z
-updatedAt: 2022-11-25T21:45:53.573Z
-publishedAt: 2022-11-25T21:45:53.573Z
+updatedAt: 2024-02-16T20:25:52.080Z
+publishedAt: 2024-02-16T20:25:52.080Z
 firstPublishedAt: 2022-05-23T13:58:53.924Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: facetas-de-busca-na-api-do-catalogo-nao-retornam-informacoes-para-produtos-nao-disponiveis
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 583623
 ---
 
diff --git a/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md b/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md
new file mode 100644
index 000000000..cf392f816
--- /dev/null
+++ b/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md
@@ -0,0 +1,52 @@
+---
+title: 'As traduções do catálogo não são refletidas no front-end'
+id: 4c6Qzdn6NQfHhEN5U76WOi
+status: PUBLISHED
+createdAt: 2023-07-13T19:43:10.669Z
+updatedAt: 2023-07-13T19:43:11.858Z
+publishedAt: 2023-07-13T19:43:11.858Z
+firstPublishedAt: 2023-07-13T19:43:11.858Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-traducoes-do-catalogo-nao-sao-refletidas-no-frontend
+locale: pt
+kiStatus: Backlog
+internalReference: 861892
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o comerciante executa uma ação no aplicativo Messages para que alguns dados do produto sejam traduzidos no frontend, essa ação não está sendo refletida de fato.
+
+## Simulação
+
+
+
+1. Faça uma alteração no aplicativo de mensagens;
+2. Verifique no indexInfo se o campo GenerateAndSaveTranslationsDocument está definido como 'false'
+3. Não reindexar o produto;
+4. Verifique se a alteração não foi refletida no site traduzido
+
+## Workaround
+
+
+Para forçar a exibição das traduções, é necessário reindexar o produto. Uma das seguintes ações deve resolver o problema:
+
+- Alterar o nome;
+- Alterar as palavras-chave;
+- Alterar o texto;
+- Alterar a categoria;
+- Alterar a marca;
+- Alterar a bandeira ativa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/catalogv2-user-roles-not-applying.md b/docs/known-issues/pt/catalogv2-user-roles-not-applying.md
index 38f949ee5..7b93d7e4e 100644
--- a/docs/known-issues/pt/catalogv2-user-roles-not-applying.md
+++ b/docs/known-issues/pt/catalogv2-user-roles-not-applying.md
@@ -3,8 +3,8 @@ title: 'CatalogV2 Funções do usuário que não se aplicam'
 id: 3cDaOuqpAJyCL5JOMzD5nL
 status: PUBLISHED
 createdAt: 2022-02-25T12:18:17.776Z
-updatedAt: 2022-11-25T21:55:04.311Z
-publishedAt: 2022-11-25T21:55:04.311Z
+updatedAt: 2024-02-16T20:26:53.078Z
+publishedAt: 2024-02-16T20:26:53.078Z
 firstPublishedAt: 2022-02-25T12:18:18.632Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: catalogv2-funcoes-do-usuario-que-nao-se-aplicam
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 489297
 ---
 
diff --git a/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md b/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
new file mode 100644
index 000000000..212edafe9
--- /dev/null
+++ b/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
@@ -0,0 +1,47 @@
+---
+title: 'O mapeamento da planilha de categorias e marcas não é atualizado com os valores da guia Review Skus'
+id: 50p9fJ63Loml6pWqcKxm9Y
+status: PUBLISHED
+createdAt: 2024-05-03T13:51:01.537Z
+updatedAt: 2024-05-03T13:51:02.491Z
+publishedAt: 2024-05-03T13:51:02.491Z
+firstPublishedAt: 2024-05-03T13:51:02.491Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: o-mapeamento-da-planilha-de-categorias-e-marcas-nao-e-atualizado-com-os-valores-da-guia-review-skus
+locale: pt
+kiStatus: Backlog
+internalReference: 1026699
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um vendedor envia ao marketplace um sku com uma categoria ou marca que ainda não está mapeada na planilha, a planilha é atualizada com esse novo valor na 3ª coluna para ser mapeada.
+
+Se o sku for enviado para a guia Review (Revisão), essa atualização não ocorrerá.
+
+## Simulação
+
+
+
+1. O vendedor envia um sku com uma marca/categoria não mapeada para o marketplace;
+2. O sku falha em alguma regra opcional sobre a qualidade da oferta;
+3. O sku vai para a guia de revisão;
+4. Verifique se a planilha de mapeamento não foi atualizada
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/category-score-field-is-not-being-saved.md b/docs/known-issues/pt/category-score-field-is-not-being-saved.md
index c57f4b550..c6c827a02 100644
--- a/docs/known-issues/pt/category-score-field-is-not-being-saved.md
+++ b/docs/known-issues/pt/category-score-field-is-not-being-saved.md
@@ -3,8 +3,8 @@ title: 'Campo Score categoria não está sendo salvo'
 id: 3YxhdI31I4SY62w6oY806s
 status: PUBLISHED
 createdAt: 2018-06-01T17:24:40.180Z
-updatedAt: 2022-12-22T20:48:43.605Z
-publishedAt: 2022-12-22T20:48:43.605Z
+updatedAt: 2024-03-05T15:28:44.072Z
+publishedAt: 2024-03-05T15:28:44.072Z
 firstPublishedAt: 2018-06-01T17:39:02.287Z
 contentType: knownIssue
 productTeam: Marketing & Merchandising
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: campo-score-categoria-nao-esta-sendo-salvo
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 
 ---
 
diff --git a/docs/known-issues/pt/centauro-to-implement-centauro-envios.md b/docs/known-issues/pt/centauro-to-implement-centauro-envios.md
index 7986ad327..6d5cbfd35 100644
--- a/docs/known-issues/pt/centauro-to-implement-centauro-envios.md
+++ b/docs/known-issues/pt/centauro-to-implement-centauro-envios.md
@@ -3,8 +3,8 @@ title: '[Para implementar o "Centauro Envios'
 id: 1xkjyfVfT8Fs2as9mbNjj3
 status: PUBLISHED
 createdAt: 2022-11-25T21:23:23.849Z
-updatedAt: 2022-11-25T21:23:24.283Z
-publishedAt: 2022-11-25T21:23:24.283Z
+updatedAt: 2024-02-16T20:24:05.883Z
+publishedAt: 2024-02-16T20:24:05.883Z
 firstPublishedAt: 2022-11-25T21:23:24.283Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: para-implementar-o-centauro-envios
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 618941
 ---
 
diff --git a/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md b/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
new file mode 100644
index 000000000..c2d693ceb
--- /dev/null
+++ b/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
@@ -0,0 +1,53 @@
+---
+title: 'O link Alterar pedido no checkout/orderPlaced está direcionando para myAccount em vez da página do pedido'
+id: 6bP44VBdFIujX072rY6wCA
+status: PUBLISHED
+createdAt: 2023-06-15T16:13:03.752Z
+updatedAt: 2023-06-15T16:13:04.279Z
+publishedAt: 2023-06-15T16:13:04.279Z
+firstPublishedAt: 2023-06-15T16:13:04.279Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-link-alterar-pedido-no-checkoutorderplaced-esta-direcionando-para-myaccount-em-vez-da-pagina-do-pedido
+locale: pt
+kiStatus: Backlog
+internalReference: 844893
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a conta tiver configurado a possibilidade de o comprador alterar o pedido por conta própria, o link de alteração de pedido aparecerá no modelo checkout/orderPlaced.
+
+No entanto, esse link não está redirecionando o cliente para a página de edição, mas para a myAccount, que aparece vazia.
+
+
+## Simulação
+
+
+Configure o sinalizador Permitir que os clientes façam alterações nos pedidos em Admin -> configurações -> configurações de pedidos
+ ![](https://vtexhelp.zendesk.com/attachments/token/GqrSJ7cBhZc844LR3kXH7WMlX/?name=image.png)
+
+O comprador preenche um pedido e vai para o checkout/orderPlaced
+
+Verifique se o link não o redirecionará para a área de edição do pedido
+
+## Workaround
+
+
+
+1. O comprador deve clicar em My Orders (Meus pedidos) na seção myAccount (Minha conta);
+2. Selecionar novamente o pedido que deseja alterar;
+3. Clique em change order (alterar pedido).
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md b/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
index 4a1b88ddf..8df6434eb 100644
--- a/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
+++ b/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
@@ -3,8 +3,8 @@ title: 'Mudança de ordem através da IU não leva em conta o cálculo das promo
 id: 3rvsDyCggYirvH7WT9rBVZ
 status: PUBLISHED
 createdAt: 2022-03-15T20:25:17.217Z
-updatedAt: 2022-11-25T22:03:48.329Z
-publishedAt: 2022-11-25T22:03:48.329Z
+updatedAt: 2024-02-16T20:23:38.705Z
+publishedAt: 2024-02-16T20:23:38.705Z
 firstPublishedAt: 2022-03-15T20:25:17.513Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: mudanca-de-ordem-atraves-da-iu-nao-leva-em-conta-o-calculo-das-promocoes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 472882
 ---
 
diff --git a/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md b/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md
index cee56e58a..f9a57abe0 100644
--- a/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md
+++ b/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md
@@ -3,8 +3,8 @@ title: 'Alterar pedido usando API sem troca de pedido por e-mail'
 id: 1KMglga4xM1s7EvNO1mmua
 status: PUBLISHED
 createdAt: 2022-05-18T18:40:48.935Z
-updatedAt: 2022-11-25T22:02:43.384Z
-publishedAt: 2022-11-25T22:02:43.384Z
+updatedAt: 2024-02-16T20:27:31.478Z
+publishedAt: 2024-02-16T20:27:31.478Z
 firstPublishedAt: 2022-05-18T18:40:49.234Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: alterar-pedido-usando-api-sem-troca-de-pedido-por-email
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 380509
 ---
 
diff --git a/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md b/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
new file mode 100644
index 000000000..b104ee9df
--- /dev/null
+++ b/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
@@ -0,0 +1,46 @@
+---
+title: 'As alterações feitas na página de administração de estilos não são salvas corretamente'
+id: 4XmBeVMf0yZJElH85mSxC3
+status: PUBLISHED
+createdAt: 2024-01-25T19:13:16.165Z
+updatedAt: 2024-01-25T19:13:16.858Z
+publishedAt: 2024-01-25T19:13:16.858Z
+firstPublishedAt: 2024-01-25T19:13:16.858Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: as-alteracoes-feitas-na-pagina-de-administracao-de-estilos-nao-sao-salvas-corretamente
+locale: pt
+kiStatus: No Fix
+internalReference: 971948
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As alterações feitas usando a página de estilos da interface do usuário do administrador não estão sendo salvas corretamente no momento e nem sempre são aplicadas ao site.
+
+## Simulação
+
+
+Tente fazer alterações no estilo do site por meio da página de estilos.
+Salve as alterações.
+As alterações não serão refletidas e não serão salvas.
+Não há erros registrados no console e a mensagem "Saved sucesfully" é exibida.
+
+
+
+## Workaround
+
+
+Não há solução alternativa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md b/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md
new file mode 100644
index 000000000..210372962
--- /dev/null
+++ b/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md
@@ -0,0 +1,37 @@
+---
+title: 'A mudança de acessórios não está acionando a indexação'
+id: 5asLRh4ChyuSEg1mRwWbgT
+status: PUBLISHED
+createdAt: 2024-05-22T18:30:14.578Z
+updatedAt: 2024-05-22T18:30:15.412Z
+publishedAt: 2024-05-22T18:30:15.412Z
+firstPublishedAt: 2024-05-22T18:30:15.412Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-mudanca-de-acessorios-nao-esta-acionando-a-indexacao
+locale: pt
+kiStatus: Backlog
+internalReference: 1037800
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o comerciante faz alterações ou adiciona novos acessórios à sku, o indexador não está sendo acionado automaticamente.
+
+Isso faz com que as alterações não sejam refletidas na interface do usuário até que outra ação acione o indexador.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md b/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
index 9b0128393..b42acc50d 100644
--- a/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
+++ b/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
@@ -3,8 +3,8 @@ title: 'Alterar a ordem de uma especificação de SKU no Admin pode fazer a pág
 id: 5MuozhOKaYLGShytNH5k8Z
 status: PUBLISHED
 createdAt: 2022-08-10T13:57:53.322Z
-updatedAt: 2022-11-25T21:43:51.741Z
-publishedAt: 2022-11-25T21:43:51.741Z
+updatedAt: 2024-02-16T20:26:58.129Z
+publishedAt: 2024-02-16T20:26:58.129Z
 firstPublishedAt: 2022-08-10T13:57:53.867Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: alterar-a-ordem-de-uma-especificacao-de-sku-no-admin-pode-fazer-a-pagina-nao-funcionar-corretamente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 460329
 ---
 
diff --git a/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md b/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
index 6ca8fbc67..8d60d35b4 100644
--- a/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
+++ b/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
@@ -3,8 +3,8 @@ title: 'O checkout permite proceder ao formulário de pagamento sem endereço de
 id: 3k9zxMq6Pl9WBnIz5Hy6Xf
 status: PUBLISHED
 createdAt: 2022-11-18T18:42:08.326Z
-updatedAt: 2022-11-25T23:17:39.653Z
-publishedAt: 2022-11-25T23:17:39.653Z
+updatedAt: 2024-02-16T20:27:39.990Z
+publishedAt: 2024-02-16T20:27:39.990Z
 firstPublishedAt: 2022-11-18T18:42:08.914Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-checkout-permite-proceder-ao-formulario-de-pagamento-sem-endereco-de-remessa-somente-na-iu
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 699317
 ---
 
diff --git a/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md b/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md
new file mode 100644
index 000000000..d0be7c284
--- /dev/null
+++ b/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md
@@ -0,0 +1,46 @@
+---
+title: 'O checkout permite adicionar dois endereços diferentes para entrega'
+id: 2z7iq68qdHXAfY8RLDHXDg
+status: PUBLISHED
+createdAt: 2023-11-06T22:03:24.983Z
+updatedAt: 2023-11-07T21:28:43.164Z
+publishedAt: 2023-11-07T21:28:43.164Z
+firstPublishedAt: 2023-11-06T22:03:25.472Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-checkout-permite-adicionar-dois-enderecos-diferentes-para-entrega
+locale: pt
+kiStatus: Backlog
+internalReference: 931225
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O checkout permite adicionar dois endereços diferentes para entrega no formulário de pedido, por exemplo, um "comercial" e um "residencial" (definido pelo campo "addressType"), quando um deles é descartável.
+
+Quando ambos os endereços forem selecionados, haverá um erro de mensagem "Unable to communicate with seller" (Não é possível se comunicar com o vendedor), e o comprador não poderá prosseguir para as próximas etapas.
+
+## Simulação
+
+
+
+- Enviar um novo endereço via API Adicionar endereço de entrega e selecionar a opção de entrega;
+- Adicionar um cliente que já tenha um perfil completo via API Adicionar perfil de cliente.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md b/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
new file mode 100644
index 000000000..268fbfb34
--- /dev/null
+++ b/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
@@ -0,0 +1,43 @@
+---
+title: "O checkout permite que os usuários pulem para a etapa de pagamento com um 'shippingData' vazio ao usar a geolocalização"
+id: 7uv85LIrjoPaHxVgCAoy7I
+status: PUBLISHED
+createdAt: 2023-10-23T17:48:05.377Z
+updatedAt: 2023-10-23T17:58:49.908Z
+publishedAt: 2023-10-23T17:58:49.908Z
+firstPublishedAt: 2023-10-23T17:48:06.206Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-checkout-permite-que-os-usuarios-pulem-para-a-etapa-de-pagamento-com-um-shippingdata-vazio-ao-usar-a-geolocalizacao
+locale: pt
+kiStatus: Backlog
+internalReference: 343056
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar a geolocalização no checkout, os usuários podem pular para a etapa de pagamento com o `shippingData` incompleto.
+
+## Simulação
+
+
+
+- Enviar o endereço via API com dados incompletos;
+- Adicionar qualquer produto ao carrinho;
+- Ir para o carrinho e depois para o checkout;
+- Adicionar as informações do perfil
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md b/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
index 6f3ff6216..9a4145b5c 100644
--- a/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
+++ b/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'O checkout não calcula corretamente o valor do frete para um único ite
 id: 4jX7JT0Wxt9S4xBe9FSwO
 status: PUBLISHED
 createdAt: 2022-02-21T19:48:04.202Z
-updatedAt: 2022-11-25T21:53:42.846Z
-publishedAt: 2022-11-25T21:53:42.846Z
+updatedAt: 2024-02-16T20:26:29.918Z
+publishedAt: 2024-02-16T20:26:29.918Z
 firstPublishedAt: 2022-02-21T19:48:04.748Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-checkout-nao-calcula-corretamente-o-valor-do-frete-para-um-unico-item-que-tenha-frete-gratuito-e-entrega-programada
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 529043
 ---
 
diff --git a/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md b/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
index 79f99e37a..6f08edd84 100644
--- a/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
+++ b/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
@@ -1,18 +1,18 @@
 ---
-title: 'O checkout não exibe promoção de remessa no primeiro instante para condições específicas'
+title: 'O checkout não exibe a promoção de frete no primeiro instante para uma condição específica'
 id: 14rQaM53csQQeA1wu5lRj8
 status: PUBLISHED
 createdAt: 2022-05-20T17:46:10.644Z
-updatedAt: 2022-11-25T21:53:02.607Z
-publishedAt: 2022-11-25T21:53:02.607Z
+updatedAt: 2024-01-15T14:35:39.473Z
+publishedAt: 2024-01-15T14:35:39.473Z
 firstPublishedAt: 2022-05-20T17:46:11.046Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: o-checkout-nao-exibe-promocao-de-remessa-no-primeiro-instante-para-condicoes-especificas
+slug: o-checkout-nao-exibe-a-promocao-de-frete-no-primeiro-instante-para-uma-condicao-especifica
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 280144
 ---
 
@@ -23,23 +23,31 @@ internalReference: 280144
 </div>
 
 
-O checkout (backend) tem um comportamento de pré-selecionar o melhor método de entrega para o usuário assim que um código postal é informado.
+O checkout (backend) tem o comportamento de pré-selecionar o melhor método de entrega para o usuário assim que um código postal é informado.
 
-As promoções que utilizam a restrição de "Aplicar o desconto somente quando um dos transportadores acima é selecionado pelo cliente" na verdade só são aplicadas depois que o cliente escolhe o método de entrega específico.
+As promoções que usam a restrição "Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente", na verdade, só são aplicadas depois que o cliente escolhe o método de entrega específico.
 
-Acontece que, se a opção de entrega selecionada automaticamente por caixa se encaixa em qualquer promoção com a restrição acima, o desconto não será aplicado A opção mencionada é a que diz "Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente").
-
-Isto só ocorre no primeiro momento, pois o checkout não recalcula as promoções ao fazer esta escolha de entrega automática. Isto porque, se você recalcular as promoções, eventualmente a melhor opção de entrega poderá ser diferente, e isto deixaria o sistema em um loop, sempre procurando a melhor opção. Em futuras atualizações do OrderForm, todo seu contexto é recalculado, desta vez com a forma de entrega realmente selecionada, e então a promoção será aplicada.
-
-Além deste fato, a simulação de envio do carrinho (shipping-preview) faz pedidos adicionais à API, não apenas utilizando o contexto do OrderForm. Isto faz com que ele receba a promoção, enquanto os totais do carrinho são restritos ao contexto do OrderForm, que ainda não tem a promoção, resultando em valores divergentes.
+Ocorre que, se a opção de entrega selecionada automaticamente no checkout se enquadrar em alguma promoção com a restrição acima, o desconto não será aplicado (a opção mencionada é a que diz "Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente").
 
+Isso só ocorre em um primeiro momento, pois o checkout não recalcula as promoções ao fazer essa escolha automática de entrega. Isso ocorre porque, se você recalcular as promoções, eventualmente a melhor opção de entrega pode ser diferente, e isso deixaria o sistema em um loop, sempre procurando a melhor opção. Na atualização futura do orderForm, todo o seu contexto é recalculado, dessa vez com a forma de entrega realmente selecionada, e então a promoção será aplicada.
 
+Além desse fato, a simulação de envio do carrinho (shipping-preview) faz solicitações adicionais à API, não utilizando apenas o contexto do orderForm. Isso faz com que ele receba a promoção, enquanto os totais do carrinho ficam restritos ao contexto do orderForm, que ainda não tem a promoção, resultando em valores divergentes.
 
 ## Simulação
 
 
+- ter uma promoção de frete grátis restrita a uma opção "A" e com a opção adicional acima ativada
+- tenha um carrinho e um CEP com dois ou mais tipos de frete, em que "A" é o frete mais barato (exemplo, A = R$10; B = R$20)
+- digite o código postal e observe que "A" (o mais barato) será selecionado automaticamente, mas ainda aparecerá como R$10
+- selecione o frete "B" (R$ 20) e retorne ao frete "A" (R$ 10)
+- nesse momento, o valor de "A" será recalculado e será exibido como gratuit
 
 ## Workaround
 
 
+Não é recomendável usar essa restrição em promoções de frete.
+
+
+
+
 
diff --git a/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md b/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md
new file mode 100644
index 000000000..584cab92b
--- /dev/null
+++ b/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md
@@ -0,0 +1,42 @@
+---
+title: 'O checkout não é compatível com a codificação de nomes de opções de montagem'
+id: 29YnOA15HDzJSRwiOLLNfR
+status: PUBLISHED
+createdAt: 2024-05-06T19:01:35.962Z
+updatedAt: 2024-05-06T19:01:36.828Z
+publishedAt: 2024-05-06T19:01:36.828Z
+firstPublishedAt: 2024-05-06T19:01:36.828Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-checkout-nao-e-compativel-com-a-codificacao-de-nomes-de-opcoes-de-montagem
+locale: pt
+kiStatus: Backlog
+internalReference: 378842
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O nome das opções de montagem é usado na rota da API. Portanto, é necessário oferecer suporte à codificação desses nomes para não criar problemas na URL com caracteres especiais, como "/". Ao adicionar uma opção de montagem com "/" no carrinho, ela simplesmente não é adicionada e também não notifica o usuário.
+
+## Simulação
+
+
+
+- Adicione um "/" ao nome da opção de montagem;
+- Tente adicionar um produto com a opção de montagem;
+- O item será adicionado ao carrinho sem a opção de montagem
+
+## Workaround
+
+
+Remova "/" do nome da opção de montagem.
+
+
+
diff --git a/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md b/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md
index c3ed0df46..1bd22b492 100644
--- a/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md
+++ b/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md
@@ -3,8 +3,8 @@ title: 'Checkout incorretamente enviando detalhes do item para a transação'
 id: YxjZNKuIxkKQioS7lkmu8
 status: PUBLISHED
 createdAt: 2022-03-04T15:08:55.326Z
-updatedAt: 2022-11-25T21:52:34.380Z
-publishedAt: 2022-11-25T21:52:34.380Z
+updatedAt: 2024-02-16T20:28:39.301Z
+publishedAt: 2024-02-16T20:28:39.301Z
 firstPublishedAt: 2022-03-04T15:08:55.710Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-incorretamente-enviando-detalhes-do-item-para-a-transacao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 535859
 ---
 
diff --git a/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md b/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
new file mode 100644
index 000000000..0bf3d882d
--- /dev/null
+++ b/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
@@ -0,0 +1,44 @@
+---
+title: 'O pipeline de checkout não atualiza os impostos considerando o vendedor correto ao mesclar as informações do carrinho'
+id: 4HDGps2Ez5kWKuW1UNX1JQ
+status: PUBLISHED
+createdAt: 2024-07-03T20:21:23.533Z
+updatedAt: 2024-07-03T20:21:24.413Z
+publishedAt: 2024-07-03T20:21:24.413Z
+firstPublishedAt: 2024-07-03T20:21:24.413Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-pipeline-de-checkout-nao-atualiza-os-impostos-considerando-o-vendedor-correto-ao-mesclar-as-informacoes-do-carrinho
+locale: pt
+kiStatus: Backlog
+internalReference: 759842
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando há dois vendedores no método "SellerElection", um deles é selecionado como tendo o preço mais barato para entrega e o outro como o preço mais barato para retirada no ponto, a mesclagem de informações do carrinho não atualiza os impostos ao selecionar a retirada no ponto, causando um erro ao concluir a compra
+
+## Simulação
+
+
+
+- Ter dois vendedores configurados: um é o mais barato para entrega e o outro para retirada no ponto
+- Configure os impostos _somente_ para o vendedor que atenderá à retirada no ponto ou impostos diferentes entre eles
+- Faça uma simulação de checkout e você verá que não haverá impostos em "priceTags" e a compra não será concluída.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
new file mode 100644
index 000000000..679cfdbcf
--- /dev/null
+++ b/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -0,0 +1,42 @@
+---
+title: 'A simulação de checkout retorna o valor 0 no campo "slas.tax" para impostos de porcentagem de frete'
+id: 54Mtsj8EKuo0SaQCoWyYzj
+status: PUBLISHED
+createdAt: 2024-04-05T18:55:32.183Z
+updatedAt: 2024-04-05T18:55:33.336Z
+publishedAt: 2024-04-05T18:55:33.336Z
+firstPublishedAt: 2024-04-05T18:55:33.336Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-simulacao-de-checkout-retorna-o-valor-0-no-campo-slastax-para-impostos-de-porcentagem-de-frete
+locale: pt
+kiStatus: Backlog
+internalReference: 1012724
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os impostos de porcentagem de envio não são retornados no campo `logisticsInfo.slas.tax` ao realizar uma simulação de checkout, embora as informações de impostos individuais estejam disponíveis no campo `items.priceTags`.
+
+## Simulação
+
+
+
+- Configurar um imposto de porcentagem de envio
+- Fazer uma solicitação de simulação de carrinho com o SLA selecionado
+- O campo `tax` retorna o valor `0
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md b/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
new file mode 100644
index 000000000..99d4e1448
--- /dev/null
+++ b/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
@@ -0,0 +1,46 @@
+---
+title: 'A simulação de checkout com uma grande quantidade do mesmo item recebe um tempo limite de logística'
+id: 753MDZbcyN9BTHAaSTpOlY
+status: PUBLISHED
+createdAt: 2024-06-18T12:42:44.404Z
+updatedAt: 2024-06-18T12:42:45.419Z
+publishedAt: 2024-06-18T12:42:45.419Z
+firstPublishedAt: 2024-06-18T12:42:45.419Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: a-simulacao-de-checkout-com-uma-grande-quantidade-do-mesmo-item-recebe-um-tempo-limite-de-logistica
+locale: pt
+kiStatus: No Fix
+internalReference: 330775
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Temos um erro no serviço de logística ao tentar simular uma compra com milhares de unidades da mesma SKU. Esse erro ocorre porque a solicitação para dividir o pacote leva muito tempo.
+
+O detalhe do erro na API é: "A operação foi cancelada".
+
+## Simulação
+
+
+
+1. Tente fazer uma **Simulação de checkout** ou uma simulação no **Carrinho de compras** com milhares de unidades do mesmo SKU (como 50 mil)
+2. Analise os detalhes na resposta da API e você provavelmente verá um erro ao processar essa solicitação (**timeout**
+
+## Workaround
+
+
+Recomendamos aumentar os limites de pacote da transportadora para acomodar as unidades em um único pacote. Isso forneceria uma solicitação mais rápida e não retornaria um tempo limite.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md b/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
new file mode 100644
index 000000000..4896fc69d
--- /dev/null
+++ b/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
@@ -0,0 +1,45 @@
+---
+title: 'A interface do usuário do checkout vai para Pagamento com um endereço de fatura incompleto para compradores com perfil completo'
+id: NmN6oNKp1isyxssTE5jPR
+status: PUBLISHED
+createdAt: 2023-11-27T17:40:11.335Z
+updatedAt: 2023-12-12T15:46:39.789Z
+publishedAt: 2023-12-12T15:46:39.789Z
+firstPublishedAt: 2023-11-27T17:40:12.008Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-do-checkout-vai-para-pagamento-com-um-endereco-de-fatura-incompleto-para-compradores-com-perfil-completo
+locale: pt
+kiStatus: Fixed
+internalReference: 937615
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um comprador tiver um perfil completo e a loja estiver configurada para usar um endereço de fatura para retirada, a interface do usuário avançará para o pagamento com um endereço de fatura incompleto.
+
+## Simulação
+
+
+
+- Configure o endereço da fatura para retirada;
+ ![](https://vtexhelp.zendesk.com/attachments/token/1zJ19Lq9oJ5CHdkaHUfw4SAka/?name=image.png)
+
+- Depois de adicionar produtos ao carrinho, use um e-mail com um perfil completo;
+- A interface do usuário avançará para o pagamento mesmo com um endereço de fatura incompleto no sistema de perfil
+
+## Workaround
+
+
+Atualize o endereço da fatura por meio dos dados mestre.
+
+
+
+
diff --git a/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
new file mode 100644
index 000000000..d337a1cf7
--- /dev/null
+++ b/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -0,0 +1,47 @@
+---
+title: 'A interface de usuário do checkout não está usando automaticamente o "envio enxuto" para itens sem métodos de envio comuns'
+id: 2LXp8VCAay7Ic9MBfbtirT
+status: PUBLISHED
+createdAt: 2024-04-02T15:27:23.003Z
+updatedAt: 2024-04-02T15:27:24.004Z
+publishedAt: 2024-04-02T15:27:24.004Z
+firstPublishedAt: 2024-04-02T15:27:24.004Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-de-usuario-do-checkout-nao-esta-usando-automaticamente-o-envio-enxuto-para-itens-sem-metodos-de-envio-comuns
+locale: pt
+kiStatus: Backlog
+internalReference: 329846
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As configurações da interface do usuário do checkout permitem que você desative o envio simples (otimizações do modo de entrega), mas isso só é possível se todos os itens no carrinho tiverem os mesmos métodos de entrega em comum. Caso contrário, o envio enxuto deve aparecer de forma forçada no carrinho, mesmo com a opção desativada.
+Entretanto, em alguns cenários, o comportamento relatado acima não acontece e todos os métodos de entrega disponíveis são apresentados individualmente ao comprador.
+
+Como resultado, como não há como selecionar um método de entrega diferente para cada item, nenhuma entrega exibida corresponde a uma única opção de entrega para todo o carrinho, com opções e pacotes sem sentido sendo apresentados.
+
+## Simulação
+
+
+
+- Desativar as **Optimized Shipping Options****;**
+- Monte um carrinho em que nem todos os itens tenham o mesmo método de entrega;
+- Também é necessário que a loja tenha a opção "allowMultipleDeliveries" ativada;
+- O cenário relatado mostrará as opções abertamente em vez do envio enxuto
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md b/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
index d3da407ab..37f7f8e71 100644
--- a/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
+++ b/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
@@ -1,10 +1,10 @@
 ---
 title: 'Checkout UI loops when not receiving correct SLA values from logistics system'
 id: 4tACwwmorLZ7NAt3zWldWL
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-04T19:28:24.852Z
-updatedAt: 2022-06-27T12:27:43.525Z
-publishedAt: 2022-06-26T16:28:26.833Z
+updatedAt: 2024-02-16T20:28:53.645Z
+publishedAt: 2024-02-16T20:28:53.645Z
 firstPublishedAt: 2022-05-04T19:28:25.322Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 485016
 ---
 
diff --git a/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md b/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
new file mode 100644
index 000000000..e14b1ee74
--- /dev/null
+++ b/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
@@ -0,0 +1,45 @@
+---
+title: 'A interface do usuário do checkout envia o hífen no código postal para o orderForm'
+id: 3cqrBqq5x8nixjAFt8BxCx
+status: PUBLISHED
+createdAt: 2024-01-16T12:37:56.497Z
+updatedAt: 2024-01-16T12:37:57.041Z
+publishedAt: 2024-01-16T12:37:57.041Z
+firstPublishedAt: 2024-01-16T12:37:57.041Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-do-checkout-envia-o-hifen-no-codigo-postal-para-o-orderform
+locale: pt
+kiStatus: Backlog
+internalReference: 937692
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A interface do usuário do checkout envia um hífen para o código postal para o formulário de pedido, causando problemas no cálculo de SLAs quando um país tem 7 dígitos + o hífen. Isso acontece porque o módulo Logistics considera o hífen como um dígito e depende de como as taxas de envio foram registradas na política de envio.
+
+Portugal e Japão são os únicos nesse cenário.
+
+## Simulação
+
+
+
+- Tenha uma conta em Portugal ou no Japão;
+- Após adicionar produtos ao carrinho, digite o código postal;
+- O produto pode ser mostrado como indisponível
+
+## Workaround
+
+
+
+- Revise as taxas de envio para incluir uma faixa mais ampla.
+
+
+
diff --git a/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md b/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
new file mode 100644
index 000000000..3365dd796
--- /dev/null
+++ b/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
@@ -0,0 +1,44 @@
+---
+title: 'A interface de usuário do checkout mostra o frete grátis quando o usuário alterna as opções de entrega'
+id: 5ibXQuVSU5vLfihL8uImyX
+status: PUBLISHED
+createdAt: 2023-09-27T20:40:02.973Z
+updatedAt: 2023-10-02T19:35:11.231Z
+publishedAt: 2023-10-02T19:35:11.231Z
+firstPublishedAt: 2023-09-27T20:40:03.494Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-de-usuario-do-checkout-mostra-o-frete-gratis-quando-o-usuario-alterna-as-opcoes-de-entrega
+locale: pt
+kiStatus: Backlog
+internalReference: 897109
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A interface de usuário do checkout mostra a entrega gratuita quando o usuário muda o método de entrega de envio normal para entrega programada. O problema ocorre somente na caixa de entrega e quando a conta tem o recurso LeanShipping configurado. Embora a interface do usuário mostre o frete grátis, os valores totais da compra são exibidos e cobrados corretamente.
+
+## Simulação
+
+
+
+1. Vá para a página de checkout comprando um item aleatório
+2. na seção de envio, selecione agendar entrega e, em seguida, selecione envio normal novamente e o preço da entrega gratuita aparecerá na seção de entrega
+
+
+
+## Workaround
+
+
+Não há solução alternativa.
+
+
+
+
diff --git a/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md b/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
index 05b57ed88..0a070a8fc 100644
--- a/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
+++ b/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
@@ -3,8 +3,8 @@ title: 'A cidade e o estado não são enviados ao PayPalPlus quando há apenas u
 id: 5ScWTMLqT9oBMUYFc6WGo2
 status: PUBLISHED
 createdAt: 2023-06-01T13:47:08.477Z
-updatedAt: 2023-06-01T13:47:09.590Z
-publishedAt: 2023-06-01T13:47:09.590Z
+updatedAt: 2023-09-12T13:10:53.169Z
+publishedAt: 2023-09-12T13:10:53.169Z
 firstPublishedAt: 2023-06-01T13:47:09.590Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-cidade-e-o-estado-nao-sao-enviados-ao-paypalplus-quando-ha-apenas-um-endereco-de-retirada-disponivel
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 836025
 ---
 
@@ -41,3 +41,4 @@ Selecione "Delivery" (Entrega), adicione o código postal e mude para "Pick up i
 
 
 
+
diff --git a/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md b/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
new file mode 100644
index 000000000..ecd221572
--- /dev/null
+++ b/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
@@ -0,0 +1,39 @@
+---
+title: 'O botão Limpar filtro não lida corretamente com vários filtros'
+id: TVLYkkJXq5bxmFvHZyRS6
+status: PUBLISHED
+createdAt: 2024-01-03T22:35:40.705Z
+updatedAt: 2024-01-03T22:35:41.328Z
+publishedAt: 2024-01-03T22:35:41.328Z
+firstPublishedAt: 2024-01-03T22:35:41.328Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: o-botao-limpar-filtro-nao-lida-corretamente-com-varios-filtros
+locale: pt
+kiStatus: Backlog
+internalReference: 960905
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Em alguns cenários, como páginas de destino e páginas de coleção, os filtros adicionais não são limpos corretamente após clicar no botão "limpar filtro". O URL pode ir para filtros inválidos ou errados e a listagem de produtos pode ficar vazia ou com produtos inesperados.
+
+## Simulação
+
+
+Em um tema de loja com o botão "limpar filtros" ativado, experimente-o em uma página de destino ou página de coleção depois de aplicar filtros adicionais.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md b/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
new file mode 100644
index 000000000..39f8a5f18
--- /dev/null
+++ b/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
@@ -0,0 +1,48 @@
+---
+title: 'Às vezes, o valor do documento do cliente não é atualizado corretamente na configuração do Global Checkout'
+id: 3846jcrfuMvULJt5dZkJxf
+status: PUBLISHED
+createdAt: 2023-07-17T20:50:26.133Z
+updatedAt: 2023-07-17T20:50:27.048Z
+publishedAt: 2023-07-17T20:50:27.048Z
+firstPublishedAt: 2023-07-17T20:50:27.048Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: as-vezes-o-valor-do-documento-do-cliente-nao-e-atualizado-corretamente-na-configuracao-do-global-checkout
+locale: pt
+kiStatus: Backlog
+internalReference: 863726
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o Global Checkout, a alteração do uso do documento padrão para um documento autoidentificado e o valor informado para o campo de número do documento não "pegará" corretamente.
+
+Em anexo, há um vídeo que mostra o comportamento.
+
+
+
+## Simulação
+
+
+Aplique as personalizações para ativar o checkout global.
+Prossiga para adicionar um documento estrangeiro e salve as alterações no perfil.
+Edite o perfil, mude para a entrada de documento regular e introduza um valor diferente, depois salve as alterações
+Abra o perfil novamente, às vezes o valor mostrado foi substituído pelo valor estrangeir
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md b/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
new file mode 100644
index 000000000..eb0cd1252
--- /dev/null
+++ b/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
@@ -0,0 +1,42 @@
+---
+title: 'clientProfileData fica vazio se a solicitação Add client profile for executada duas vezes'
+id: 1TG7cnnMyWHNKrCjoouKoC
+status: PUBLISHED
+createdAt: 2023-10-02T15:51:35.989Z
+updatedAt: 2023-10-02T15:51:36.771Z
+publishedAt: 2023-10-02T15:51:36.771Z
+firstPublishedAt: 2023-10-02T15:51:36.771Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: clientprofiledata-fica-vazio-se-a-solicitacao-add-client-profile-for-executada-duas-vezes
+locale: pt
+kiStatus: Backlog
+internalReference: 911203
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao enviar a solicitação Adicionar perfil de cliente duas vezes e o e-mail tiver um perfil completo, "clientProfileData" fica vazio, mostrando apenas o e-mail.
+
+## Simulação
+
+
+
+- Adicionar perfil de cliente via API;
+- Reenvie a mesma solicitação autenticada, o "clientProfileData" terá apenas o e-mail
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md b/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
index 6996483e6..f7fba702e 100644
--- a/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
+++ b/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
@@ -3,8 +3,8 @@ title: 'O CMS permite a criação mas não a edição de pastas com os mesmos no
 id: q2Fvxfwv5MjAcqxb81avH
 status: PUBLISHED
 createdAt: 2022-04-26T14:09:30.508Z
-updatedAt: 2022-11-25T22:10:43.268Z
-publishedAt: 2022-11-25T22:10:43.268Z
+updatedAt: 2024-02-16T20:26:06.081Z
+publishedAt: 2024-02-16T20:26:06.081Z
 firstPublishedAt: 2022-04-26T14:09:31.061Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: o-cms-permite-a-criacao-mas-nao-a-edicao-de-pastas-com-os-mesmos-nomes-que-as-pastas-padrao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 566791
 ---
 
diff --git a/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md b/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md
index 8704049c5..3ca3eb934 100644
--- a/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md
+++ b/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md
@@ -20,7 +20,7 @@ internalReference:
 
 Ao acessar o CMS por meio do novo ambiente administrativo (My VTEX - `{AccountName}.myvtex.com/admin`), é apresentada uma página de erro, não sendo possível acessá-lo.
 
-![4JSc1cw](https://images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
+![4JSc1cw](//images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/cms-legacy-collections-timeout.md b/docs/known-issues/pt/cms-legacy-collections-timeout.md
index 216cc80d6..144b67fee 100644
--- a/docs/known-issues/pt/cms-legacy-collections-timeout.md
+++ b/docs/known-issues/pt/cms-legacy-collections-timeout.md
@@ -3,8 +3,8 @@ title: 'Tempo limite das coleções herdadas do CMS'
 id: 3TgWP83kn8G8NClnUHmaoS
 status: PUBLISHED
 createdAt: 2022-02-25T12:33:00.051Z
-updatedAt: 2023-05-19T18:23:32.371Z
-publishedAt: 2023-05-19T18:23:32.371Z
+updatedAt: 2023-06-20T13:24:40.031Z
+publishedAt: 2023-06-20T13:24:40.031Z
 firstPublishedAt: 2022-02-25T12:33:00.399Z
 contentType: knownIssue
 productTeam: Catalog
@@ -18,11 +18,10 @@ internalReference: 434026
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
-
 Frequentemente, ao tentar salvar os dados de um grupo de coleções usando o aplicativo de coleções legado, no caminho /admin/a e ao tentar salvar o grupo, o usuário, em casos de catálogos grandes (grande quantidade de categorias, marcas, produtos), recebe uma mensagem de erro de tempo limite e não consegue salvar as alterações.
 
 `{account}.myvtex.com/admin/a/`
@@ -32,18 +31,15 @@ Frequentemente, ao tentar salvar os dados de um grupo de coleções usando o apl
 ## Simulação
 
 
-1) Acesse o aplicativo CMS UI usando uma loja que tenha uma base de catálogo grande, por exemplo, >10000 produtos.
-2) Vá para "Product Clusters (Collections)" (Grupos de produtos (coleções)) e selecione "_new group_" (novo grupo)
-3) Crie um grupo e, em seguida, marque algumas caixas de seleção no formulário
-4) Tente salvar essas alterações
-5) Se a solicitação demorar mais de 50 segundos para ser salva, o que geralmente acontece em contas com uma grande quantidade de dados, a solicitação será interrompida e os dados não serão salvos
+1. Acesse o aplicativo CMS UI usando uma loja que tenha uma base de catálogo grande, por exemplo, >10000 produtos.
+2. Vá para "Product Clusters (Collections)" (Grupos de produtos (coleções)) e selecione "_new group_" (novo grupo)
+3. Crie um grupo e, em seguida, marque algumas caixas de seleção no formulário
+4. Tente salvar essas alterações
+5. Se a solicitação demorar mais de 50 segundos para ser salva, o que geralmente acontece em contas com uma grande quantidade de dados, a solicitação será interrompida e os dados não serão salvos
 
 ## Workaround
 
 
-Use o novo administrador de coleções OU use nossos pontos de extremidade da API de coleções: https://developers.vtex.com/vtex-rest-api/reference/collection-cms
-
-
-
+Use o novo Admin de coleções OU use nossos endpoints da [Collections API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection).
 
 
diff --git a/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md b/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
index 0a30a8f8c..a2c45134e 100644
--- a/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
+++ b/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
@@ -3,8 +3,8 @@ title: 'As configurações do CMS não permitem retirar valor do campo Unidade d
 id: QVmSN1VuGQUiklZDkarEI
 status: PUBLISHED
 createdAt: 2022-03-11T13:49:28.490Z
-updatedAt: 2022-11-25T22:11:28.148Z
-publishedAt: 2022-11-25T22:11:28.148Z
+updatedAt: 2024-02-16T20:28:41.042Z
+publishedAt: 2024-02-16T20:28:41.042Z
 firstPublishedAt: 2022-03-11T13:49:28.850Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: as-configuracoes-do-cms-nao-permitem-retirar-valor-do-campo-unidade-de-massa
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 540756
 ---
 
diff --git a/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md b/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md
new file mode 100644
index 000000000..07c5c049b
--- /dev/null
+++ b/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md
@@ -0,0 +1,52 @@
+---
+title: 'A função de configurações do CMS não está funcionando como esperado'
+id: 1xAUvtkD2gbvc3yaoYXT2d
+status: PUBLISHED
+createdAt: 2023-06-19T12:31:33.137Z
+updatedAt: 2023-06-19T12:31:33.699Z
+publishedAt: 2023-06-19T12:31:33.699Z
+firstPublishedAt: 2023-06-19T12:31:33.699Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: a-funcao-de-configuracoes-do-cms-nao-esta-funcionando-como-esperado
+locale: pt
+kiStatus: Backlog
+internalReference: 538706
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A função de configurações do CMS não está funcionando como esperado. Às vezes, o usuário não consegue acessar o CMS mesmo depois de ser adicionado à função.
+Outro comportamento inesperado é que outros módulos continuam disponíveis para a função CMS, mesmo sem as permissões necessárias.
+
+## Simulação
+
+
+
+- Crie uma função no aplicativo License Manager Roles que dê acesso apenas a:
+  - Menu CMS na barra superior;
+  - Configurações do CMS.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/fbpObVoVdnEYGeYjd3GDh9Qqf/?name=image.png)
+
+
+- Associe essa função a um usuário;
+- Faça login com esse usuário e tente acessar o menu de configurações do CMS, mas não conseguirá.
+- Verifique se os outros módulos continuam disponíveis
+
+## Workaround
+
+
+Para acessar o menu CMS, o usuário deve ser um Superadministrador.
+
+
+
+
+
diff --git a/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md b/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md
index e31bad0ec..d309e8547 100644
--- a/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md
+++ b/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md
@@ -3,8 +3,8 @@ title: 'Questões do menu dobrável que rendem todos os itens'
 id: 1iOlmwj8DvaxCQCmvyHQww
 status: PUBLISHED
 createdAt: 2022-05-23T19:39:49.204Z
-updatedAt: 2022-11-25T22:13:59.079Z
-publishedAt: 2022-11-25T22:13:59.079Z
+updatedAt: 2024-02-16T20:24:35.010Z
+publishedAt: 2024-02-16T20:24:35.010Z
 firstPublishedAt: 2022-05-23T19:39:49.609Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: questoes-do-menu-dobravel-que-rendem-todos-os-itens
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 542091
 ---
 
diff --git a/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md b/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md
index a40ad363e..d0f29ef26 100644
--- a/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md
+++ b/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md
@@ -3,8 +3,8 @@ title: 'Cobranças não permitem mais de 1000 SKUs por Upload'
 id: 4XC2ZLCsBkQhexRB4YrNMn
 status: PUBLISHED
 createdAt: 2023-04-19T13:53:02.339Z
-updatedAt: 2023-04-19T13:53:02.926Z
-publishedAt: 2023-04-19T13:53:02.926Z
+updatedAt: 2023-10-10T13:31:27.610Z
+publishedAt: 2023-10-10T13:31:27.610Z
 firstPublishedAt: 2023-04-19T13:53:02.926Z
 contentType: knownIssue
 productTeam: Catalog
diff --git a/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md b/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
new file mode 100644
index 000000000..e642f9d8f
--- /dev/null
+++ b/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
@@ -0,0 +1,45 @@
+---
+title: 'As coleções não funcionam em páginas de resultados de pesquisa personalizados no B2B Suite'
+id: 2O2UmKrMJHimDunDRbLBe
+status: PUBLISHED
+createdAt: 2024-06-03T22:13:10.775Z
+updatedAt: 2024-06-21T14:57:27.454Z
+publishedAt: 2024-06-21T14:57:27.454Z
+firstPublishedAt: 2024-06-03T22:13:11.591Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: as-colecoes-nao-funcionam-em-paginas-de-resultados-de-pesquisa-personalizados-no-b2b-suite
+locale: pt
+kiStatus: Backlog
+internalReference: 1043470
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As páginas de resultados de pesquisa personalizados configuradas com o ID da coleção não funcionam quando coleções de produtos diferentes são atribuídas a uma organização.
+
+O comportamento esperado ao usar coleções é definir a variedade de produtos que os usuários da organização verão na vitrine, mas como as organizações B2B também usam `productClusterId` na pesquisa, ao acessar páginas de resultados de pesquisa personalizadas configuradas com um `productClusterId` diferente, os resultados da pesquisa mostram produtos de ambas as coleções.
+
+## Simulação
+
+
+
+- Configure um produto Collections para uma organização;
+- Crie uma página de resultados de pesquisa personalizada com uma coleção diferente;
+- Faça login e acesse a página de resultados de pesquisa personalizada; os produtos de ambas as coleções são exibidos
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/collections-dont-open-on-subaccounts.md b/docs/known-issues/pt/collections-dont-open-on-subaccounts.md
new file mode 100644
index 000000000..d5178c83b
--- /dev/null
+++ b/docs/known-issues/pt/collections-dont-open-on-subaccounts.md
@@ -0,0 +1,42 @@
+---
+title: 'As cobranças não são abertas em subcontas'
+id: Ly7eHGXdzg0aJLYF2c4eZ
+status: PUBLISHED
+createdAt: 2024-07-31T18:50:48.046Z
+updatedAt: 2024-07-31T18:50:49.007Z
+publishedAt: 2024-07-31T18:50:49.007Z
+firstPublishedAt: 2024-07-31T18:50:49.007Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-cobrancas-nao-sao-abertas-em-subcontas
+locale: pt
+kiStatus: Backlog
+internalReference: 649948
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar abrir uma coleção no novo módulo de coleções de uma subconta, é retornado o erro "Desculpe, ocorreu um erro desconhecido".
+
+## Simulação
+
+
+
+1. Insira uma subconta;
+2. Vá para o novo módulo de cobranças;
+3. Tente abrir qualquer coleção;
+4. Verifique se ocorreu um erro
+
+## Workaround
+
+
+
+Como o catálogo é compartilhado entre contas, abra a coleção na conta principal OU use o módulo de coleções antigo no CMS.
+
diff --git a/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md b/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md
new file mode 100644
index 000000000..14c560df0
--- /dev/null
+++ b/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md
@@ -0,0 +1,44 @@
+---
+title: 'A exportação de coleções mostra apenas o primeiro SKU do produto inativo'
+id: 7FegROKSwxpadN5NYVFR8M
+status: PUBLISHED
+createdAt: 2024-05-28T19:56:23.549Z
+updatedAt: 2024-05-28T19:56:24.303Z
+publishedAt: 2024-05-28T19:56:24.303Z
+firstPublishedAt: 2024-05-28T19:56:24.303Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-exportacao-de-colecoes-mostra-apenas-o-primeiro-sku-do-produto-inativo
+locale: pt
+kiStatus: Backlog
+internalReference: 1040753
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o módulo de coleções e tentar exportar registros, se o produto listado em uma determinada coleção tiver todos os seus skus definidos como inativos, a planilha exportada listará apenas um dos skus do produto, em vez de todos.
+
+## Simulação
+
+
+1 - Obtenha um produto que tenha vários skus e defina todos eles como inativos.
+2 - Insira-os em uma coleção do catálogo /admin/collections
+3 - Use o recurso de exportação
+4 - apenas a SKU mais alta do produto será listada na planilha, em vez de toda
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index f379ad7df..965d9a39b 100644
--- a/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -3,8 +3,8 @@ title: 'O campo de coleções sempre aparece como "Igual a" no formulário da ca
 id: 2NPEh7LZkrpO0gf802I7HZ
 status: PUBLISHED
 createdAt: 2022-11-11T21:18:53.386Z
-updatedAt: 2022-11-25T22:11:31.863Z
-publishedAt: 2022-11-25T22:11:31.863Z
+updatedAt: 2024-02-16T20:27:37.566Z
+publishedAt: 2024-02-16T20:27:37.566Z
 firstPublishedAt: 2022-11-11T21:18:54.385Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: o-campo-de-colecoes-sempre-aparece-como-igual-a-no-formulario-da-campanha-para-o-publico
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 697168
 ---
 
diff --git a/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md b/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md
new file mode 100644
index 000000000..649a14451
--- /dev/null
+++ b/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md
@@ -0,0 +1,45 @@
+---
+title: 'As coleções nomeadas com caracteres especiais não podem ser exportadas'
+id: 516zuwek2Gfwd0U99si2XU
+status: PUBLISHED
+createdAt: 2023-08-22T12:46:46.230Z
+updatedAt: 2023-12-12T14:21:31.164Z
+publishedAt: 2023-12-12T14:21:31.164Z
+firstPublishedAt: 2023-08-22T12:46:46.895Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-colecoes-nomeadas-com-caracteres-especiais-nao-podem-ser-exportadas
+locale: pt
+kiStatus: Backlog
+internalReference: 683343
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que uma coleção possa ser exportada no administrador. Entretanto, coleções com nomes que contenham símbolos como `$` , `+` ou `,` não podem ser exportadas.
+
+## Simulação
+
+
+
+- Crie uma coleção com `$` , `+` ou `,` no nome
+- Tente exportar a coleção
+- Um erro será exibido no administrador
+
+
+
+## Workaround
+
+
+Remova o caractere
+
+
+
+
diff --git a/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md b/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md
new file mode 100644
index 000000000..962ce3911
--- /dev/null
+++ b/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md
@@ -0,0 +1,50 @@
+---
+title: 'A página Coleções em Detalhes da organização mostra apenas 20 coleções'
+id: 1NL46GlhANQoa6IzGSSwdS
+status: PUBLISHED
+createdAt: 2023-08-31T20:02:37.675Z
+updatedAt: 2024-04-23T21:35:34.440Z
+publishedAt: 2024-04-23T21:35:34.440Z
+firstPublishedAt: 2023-08-31T20:02:38.351Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: a-pagina-colecoes-em-detalhes-da-organizacao-mostra-apenas-20-colecoes
+locale: pt
+kiStatus: Fixed
+internalReference: 891511
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A página Coleções em Detalhes da organização mostra apenas 20 coleções, mesmo depois de alterar a quantidade de linhas na parte inferior da página.
+
+## Simulação
+
+
+
+- Certifique-se de que você tenha mais de 20 coleções ativas;
+- No administrador, vá para a página B2B Organizations (Organizações B2B) e selecione uma organização;
+- Vá para a guia Collections (Coleções); você verá apenas 20 coleções disponíveis
+
+## Workaround
+
+
+Se a coleção desejada não aparecer na guia Collections (Coleções), atribua-a usando o GraphQL IDE:
+
+- Acesse o GraphQL IDE;
+- Selecione o aplicativo `vtex.b2b-organizations-graphql`;
+- Use a mutação abaixo e adicione os valores para `id`, `name`, `collections.id` e `collections.name`
+
+    mutation { updateOrganization ( id: "" name: "" status: "active" collections: [{ id: "" name: "" }] ){ status message }}
+
+
+
+
+
diff --git a/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md b/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md
new file mode 100644
index 000000000..eeeddf2b0
--- /dev/null
+++ b/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md
@@ -0,0 +1,46 @@
+---
+title: 'O acionador de cobranças não está funcionando como esperado nos descontos progressivos'
+id: 78b9yQnTm1bxgOM2cfMlql
+status: PUBLISHED
+createdAt: 2023-11-06T16:42:53.081Z
+updatedAt: 2023-11-06T16:42:53.722Z
+publishedAt: 2023-11-06T16:42:53.722Z
+firstPublishedAt: 2023-11-06T16:42:53.722Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: o-acionador-de-cobrancas-nao-esta-funcionando-como-esperado-nos-descontos-progressivos
+locale: pt
+kiStatus: Backlog
+internalReference: 930849
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar uma promoção de desconto progressivo, o cliente pode definir o acionador por coleção, por uma lista de SKUs ou por ambos.
+
+No entanto, quando ambos são configurados na promoção, a condição que deveria ser a coleção ou a lista de SKUs aciona a promoção está, na verdade, se comportando como se apenas a lista de SKUs fosse o acionador.
+
+## Simulação
+
+
+
+1. Crie uma promoção de desconto progressivo;
+2. Nos acionadores da promoção, selecione uma coleção e uma lista de SKUs com um sku que não pertença à coleção;
+3. Verifique no carrinho se a promoção só estará ativa quando o sku que pertence à lista de sku estiver presente
+
+## Workaround
+
+
+Para ativar os dois acionadores ao mesmo tempo, não há solução alternativa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md b/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
index e83c9bec7..7b2db1973 100644
--- a/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
+++ b/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
@@ -3,8 +3,8 @@ title: 'Pedidos completos com erro na criação devido a falha no gatewaycallbak
 id: 2qVa686QBsvkgXY8wwmc8Y
 status: PUBLISHED
 createdAt: 2022-05-04T19:28:00.775Z
-updatedAt: 2022-11-25T21:52:28.991Z
-publishedAt: 2022-11-25T21:52:28.991Z
+updatedAt: 2024-04-04T16:46:47.602Z
+publishedAt: 2024-04-04T16:46:47.602Z
 firstPublishedAt: 2022-05-04T19:28:01.142Z
 contentType: knownIssue
 productTeam: Checkout
@@ -23,21 +23,25 @@ internalReference: 416936
 </div>
 
 
-Recebemos algumas consultas sobre pedidos que estavam presos no status de aprovação de pagamento, mas que já foram aprovados, o que o fluxo normal de pedidos não deveria acontecer.
+Recebemos algumas consultas sobre pedidos que estavam presos no status de pagamento aprovado, mas já aprovados, o que não deveria acontecer no fluxo normal de pedidos.
 
-Com base na análise dos casos, entendemos que uma possível ocorrência desta ocorrência foi;
+Com base na análise dos casos, entendemos que uma possível ocorrência desse fato foi;
 
-A ordem de mercado foi criada incompleta, a ordem de mercado recebe a chamada de gatewaycallback e, neste momento, ocorre uma falha, e isto faz com que um processo de cancelamento de ordem seja iniciado, mas a ordem de marketppace recebe uma segunda chamada de gatewaycallback que faz com que a ordem seja autorizada e completa, impedindo assim que a transação seja cancelada, e este cenário gera uma ordem completa (marketplace / checkout), mas com um erro de criação e a ordem de preenchimento cancelada, o que poderia ser evitado implementando uma validação em gatewaycallback para não proceder com pedidos incompletos.
+O pedido do marketplace foi criado incompleto, o pedido do marketplace recebe a chamada do gatewaycallback e, nesse momento, ocorre uma falha, e isso faz com que se inicie um processo de cancelamento do pedido, mas o pedido do marketppace recebe uma segunda chamada do gatewaycallback que faz com que o pedido seja autorizado e concluído, impedindo assim que a transação seja cancelada, e esse cenário gera um pedido completo (marketplace/checkout), mas com um erro de criação e o pedido completo cancelado, o que poderia ser evitado implementando uma validação no gatewaycallback para não prosseguir com pedidos incompletos.
+Em alguns casos, o pedido do vendedor pode não ser cancelado.
 
+## Simulação
 
 
 
+Não podemos simular devido à complexidade do fluxo, a análise deve ser feita considerando os dados aqui informados.
 
-## Simulação
+## Workaround
 
 
+Nos casos em que o pedido do vendedor não for cancelado, você deverá cancelar o pedido manualmente ou aguardar o prazo de 30 dias.
+
 
-## Workaround
 
 
 
diff --git a/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md b/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
index 17587b35b..0c0fc0be7 100644
--- a/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
+++ b/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
@@ -3,8 +3,8 @@ title: 'A gaveta de componentes não funciona quando implementada no resumo do p
 id: 75145kfQE8swAef57Yr4Aj
 status: PUBLISHED
 createdAt: 2023-05-29T13:22:57.856Z
-updatedAt: 2023-05-29T13:22:58.422Z
-publishedAt: 2023-05-29T13:22:58.422Z
+updatedAt: 2024-02-19T18:51:53.024Z
+publishedAt: 2024-02-19T18:51:53.024Z
 firstPublishedAt: 2023-05-29T13:22:58.422Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md b/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
index 77ce1d28c..635b51b83 100644
--- a/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
+++ b/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
@@ -3,8 +3,8 @@ title: 'O seletor de componentes do vendedor pode apresentar inconsistência nos
 id: 2agLvjXgT76ngdu3YsA6uh
 status: PUBLISHED
 createdAt: 2022-09-14T22:26:22.177Z
-updatedAt: 2022-11-25T22:13:07.124Z
-publishedAt: 2022-11-25T22:13:07.124Z
+updatedAt: 2024-02-16T20:28:08.976Z
+publishedAt: 2024-02-16T20:28:08.976Z
 firstPublishedAt: 2022-09-14T22:26:22.762Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: o-seletor-de-componentes-do-vendedor-pode-apresentar-inconsistencia-nos-precos-de-entregaremessa
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 658452
 ---
 
diff --git a/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md b/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md
new file mode 100644
index 000000000..d514d9791
--- /dev/null
+++ b/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md
@@ -0,0 +1,44 @@
+---
+title: 'Componentes em um kit com o mesmo preço'
+id: 6TIDKJ6nEGUu3E5bzAea65
+status: PUBLISHED
+createdAt: 2024-02-26T19:53:43.754Z
+updatedAt: 2024-02-26T19:53:45.011Z
+publishedAt: 2024-02-26T19:53:45.011Z
+firstPublishedAt: 2024-02-26T19:53:45.011Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: componentes-em-um-kit-com-o-mesmo-preco
+locale: pt
+kiStatus: Backlog
+internalReference: 989371
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os componentes em um kit têm o mesmo preço quando uma promoção de presente é configurada e um vendedor regular a cumpre.
+
+## Simulação
+
+
+
+- Registre um kit;
+- Definir uma promoção de presente;
+- Adicione um item ao carrinho usando um vendedor regular;
+- Faça o pedido; o preço dos componentes será o mesmo
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/confirmed-order-email-not-being-sent.md b/docs/known-issues/pt/confirmed-order-email-not-being-sent.md
index b05c4b56a..3317b8fb0 100644
--- a/docs/known-issues/pt/confirmed-order-email-not-being-sent.md
+++ b/docs/known-issues/pt/confirmed-order-email-not-being-sent.md
@@ -3,8 +3,8 @@ title: 'O e-mail de confirmação do pedido não está sendo enviado'
 id: 4RelMFApLldLtf0GxhYzdt
 status: PUBLISHED
 createdAt: 2023-03-10T22:07:59.908Z
-updatedAt: 2023-05-29T20:07:11.271Z
-publishedAt: 2023-05-29T20:07:11.271Z
+updatedAt: 2023-08-28T14:53:51.322Z
+publishedAt: 2023-08-28T14:53:51.322Z
 firstPublishedAt: 2023-03-10T22:08:01.026Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md b/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
new file mode 100644
index 000000000..429bce919
--- /dev/null
+++ b/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
@@ -0,0 +1,48 @@
+---
+title: 'Conflito entre especificações com o mesmo nome na Intelligent Search'
+id: 1TcMLTNMMGqjgbGArywSeh
+status: PUBLISHED
+createdAt: 2023-11-10T00:13:18.275Z
+updatedAt: 2024-06-24T13:48:09.391Z
+publishedAt: 2024-06-24T13:48:09.391Z
+firstPublishedAt: 2023-11-10T00:13:18.980Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: conflito-entre-especificacoes-com-o-mesmo-nome-na-intelligent-search
+locale: pt
+kiStatus: Fixed
+internalReference: 933958
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Várias especificações com o mesmo nome são agrupadas na mesma _"faceta"_ pela Pesquisa Inteligente, o que pode ser um problema se elas tiverem configurações diferentes.
+
+Alguns atributos que podem ser afetados são o filtro, as alternâncias de oculto e indexado/pesquisável, o tipo de campo e a posição do valor. Não há diferença entre ser uma especificação de produto ou de SKU.
+
+Não é possível saber qual propriedade terá precedência sobre a outra.
+
+## Simulação
+
+
+Para uma loja com:
+- uma especificação chamada "foo" (ID 1) definida como um filtro (para aparecer na vitrine) e com o valor "bar" para um produto;
+- outra especificação chamada "foo" (mas ID 2), que não é um filtro, e com o valor "baz" para o mesmo ou outro produto.
+
+A vitrine pode renderizar um filtro de pesquisa para a faceta/especificação "foo" com os valores "bar" e "baz" ou até mesmo ocultar o filtro inteiro
+
+## Workaround
+
+
+Embora o módulo Catalog não bloqueie nomes de especificações repetidos, esse uso deve ser considerado incorreto.
+
+
+
+
diff --git a/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md b/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
new file mode 100644
index 000000000..44537903f
--- /dev/null
+++ b/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
@@ -0,0 +1,51 @@
+---
+title: 'Erro de console [Report Only] - Recusou-se a aplicar o estilo inline porque ele viola a seguinte segurança de conteúdo'
+id: mix75F8F7a7D4iTWyHLyM
+status: PUBLISHED
+createdAt: 2024-04-16T10:30:41.610Z
+updatedAt: 2024-04-16T10:30:42.934Z
+publishedAt: 2024-04-16T10:30:42.934Z
+firstPublishedAt: 2024-04-16T10:30:42.934Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-de-console-report-only-recusouse-a-aplicar-o-estilo-inline-porque-ele-viola-a-seguinte-seguranca-de-conteudo
+locale: pt
+kiStatus: Backlog
+internalReference: 1017370
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Temos alguns logs no console que relatam bloqueios de script devido a restrições por meio do cabeçalho CSP.
+As chamadas de estilo inline para o host io2.vtex.com têm esse log de bloqueio porque ele não é liberado no CSP do host anterior, gerando, assim, mensagens de erro no console.
+
+
+    [Report Only] Recusou-se a executar o script inline porque ele viola a seguinte diretiva da Política de Segurança de Conteúdo: "script-src 'self' https://io.vtex.com.br https://*.vtex.com.br https://*.vtexpayments.com.br https://*.myvtex.com https://*.vtexcommercestable.com.br https://*.vtexcommercebeta.com.br https://*.vteximg.com.br https://*.vtexassets.com 'report-sample'". É necessária a palavra-chave 'unsafe-inline', um hash ('sha256-AdqydPwVZwz4OteEhuvEEzsFBDTM/J6q0/ZlIWf9Wr4=') ou um nonce ('nonce-...') para permitir a execução inline.
+
+
+
+## Simulação
+
+
+
+1. Vá para o caixa da loja;
+2. Abra o console e verifique as mensagens de relatório;
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/cookie-broken-the-apisessions.md b/docs/known-issues/pt/cookie-broken-the-apisessions.md
index 5783b6cfe..81d76a1e7 100644
--- a/docs/known-issues/pt/cookie-broken-the-apisessions.md
+++ b/docs/known-issues/pt/cookie-broken-the-apisessions.md
@@ -3,8 +3,8 @@ title: 'Cookie quebrou a API/Sessões'
 id: 5knDMVZabZRYaEtITjkDbE
 status: PUBLISHED
 createdAt: 2023-03-27T19:54:42.696Z
-updatedAt: 2023-03-27T19:54:43.232Z
-publishedAt: 2023-03-27T19:54:43.232Z
+updatedAt: 2024-03-20T20:34:36.743Z
+publishedAt: 2024-03-20T20:34:36.743Z
 firstPublishedAt: 2023-03-27T19:54:43.232Z
 contentType: knownIssue
 productTeam: Identity
@@ -23,10 +23,7 @@ internalReference: 779014
 </div>
 
 
-Quando há um script que gera um cookie para rastrear os usuários e seu cookie quebrou a chamada para /api/sessões, por exemplo, porque ele tem uma carta especial no cookie de valor. Então precisamos descartar esses cookies mal-formados de nosso lado e manter todos os outros, para que isso não afete o comportamento.
-
-
-##
+Quando há um script que gera um cookie para rastrear os usuários e seu cookie interrompe a chamada para /api/sessions, por exemplo, porque ele tem um caractere especial no cookie de valor. Então, precisamos descartar esses cookies malformados do nosso lado e manter todos os outros, para que isso não afete o comportamento.
 
 ## Simulação
 
@@ -34,12 +31,9 @@ Quando há um script que gera um cookie para rastrear os usuários e seu cookie
 
 O cenário foi mapeado no Facebook:
 
-Quando você entra na página de um anúncio no Facebook, automaticamente carrega a página no navegador META nativo e quando você chega à página de checkout não carrega corretamente, portanto, não é possível finalizar a compra.
-
-O Facebook costumava redirecionar para os navegadores, mas eles não o fazem mais porque integraram seu navegador ao seu aplicativo.
-
+Quando você entra na página a partir de um anúncio do Facebook, a página é carregada automaticamente no navegador META nativo e, quando você chega à página de checkout, ela não é carregada corretamente e, portanto, não é possível finalizar a compra.
 
-##
+O Facebook costumava redirecionar para os navegadores, mas não faz mais isso porque integrou o navegador ao aplicativo
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md b/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
new file mode 100644
index 000000000..18d8133d8
--- /dev/null
+++ b/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
@@ -0,0 +1,44 @@
+---
+title: 'O menu suspenso do centro de custo mostra apenas 25 opções nos clientes do B2B Admin'
+id: 1ynkpOppe8iqbwB3CF0euV
+status: PUBLISHED
+createdAt: 2023-10-17T23:11:29.713Z
+updatedAt: 2023-10-17T23:11:30.187Z
+publishedAt: 2023-10-17T23:11:30.187Z
+firstPublishedAt: 2023-10-17T23:11:30.187Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: o-menu-suspenso-do-centro-de-custo-mostra-apenas-25-opcoes-nos-clientes-do-b2b-admin
+locale: pt
+kiStatus: Backlog
+internalReference: 921115
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao registrar um novo cliente usando o B2B Admin Customers, o menu suspenso do centro de custo mostra apenas 25 opções.
+
+## Simulação
+
+
+
+- Registre mais de 25 centros de custo para uma organização;
+- Acesse os clientes B2B por meio do administrador;
+- Clique em "New" (Novo) e "Add New" (Adicionar novo) na parte inferior da janela pop-up;
+- Ao selecionar o centro de custo, o menu suspenso mostra apenas 25 opções
+
+## Workaround
+
+
+Use o B2B Organizations para adicionar novos usuários para organizações com mais de 25 centros de custo.
+
+
+
+
diff --git a/docs/known-issues/pt/country-field-as-null-in-invoicedata.md b/docs/known-issues/pt/country-field-as-null-in-invoicedata.md
new file mode 100644
index 000000000..7b6d91b41
--- /dev/null
+++ b/docs/known-issues/pt/country-field-as-null-in-invoicedata.md
@@ -0,0 +1,42 @@
+---
+title: 'Campo Country como nulo em invoiceData'
+id: 6TbzOvnKw5Uhcr1C5Jrneb
+status: PUBLISHED
+createdAt: 2023-12-13T15:53:26.073Z
+updatedAt: 2023-12-19T21:22:09.038Z
+publishedAt: 2023-12-19T21:22:09.038Z
+firstPublishedAt: 2023-12-13T15:53:26.800Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: campo-country-como-nulo-em-invoicedata
+locale: pt
+kiStatus: Fixed
+internalReference: 382175
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O campo Country em invoiceData pode ser nulo se for enviado via API ou se houver um endereço de fatura no Profile System com o país como nulo, portanto, os pedidos serão criados com dados incompletos em invoiceData.
+
+## Simulação
+
+
+
+- Montar um carrinho com itens;
+- Envia o invoiceData sem o campo country preenchido via API;
+- Concluir a compra
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md b/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
index c65990eb2..fae00a652 100644
--- a/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
+++ b/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
@@ -3,8 +3,8 @@ title: 'O seletor de país para endereço de faturamento enquanto no modo intern
 id: 5lHG60ATBiCdPBQnE1CEuP
 status: PUBLISHED
 createdAt: 2022-05-24T13:38:13.922Z
-updatedAt: 2022-11-25T21:51:33.189Z
-publishedAt: 2022-11-25T21:51:33.189Z
+updatedAt: 2024-02-16T20:29:40.951Z
+publishedAt: 2024-02-16T20:29:40.951Z
 firstPublishedAt: 2022-05-24T13:38:14.583Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-seletor-de-pais-para-endereco-de-faturamento-enquanto-no-modo-internacional-permanece-restrito-aos-paises-de-entrega
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 335581
 ---
 
diff --git a/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md b/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md
new file mode 100644
index 000000000..f54c18d57
--- /dev/null
+++ b/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md
@@ -0,0 +1,47 @@
+---
+title: 'Cupons criados como arquivados temporariamente'
+id: 783FJICQzATVkJ2uPgk9Mq
+status: PUBLISHED
+createdAt: 2023-09-01T13:34:21.842Z
+updatedAt: 2023-09-01T13:34:22.607Z
+publishedAt: 2023-09-01T13:34:22.607Z
+firstPublishedAt: 2023-09-01T13:34:22.607Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: cupons-criados-como-arquivados-temporariamente
+locale: pt
+kiStatus: Backlog
+internalReference: 892041
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, quando um cupom é criado, a interface do usuário/API mostra que ele está arquivado por alguns minutos (~2) quando, na verdade (no banco de dados de preços), o cupom está ativo.
+
+Após alguns minutos, os cupons exibem seus dados corretos.
+
+É importante observar que isso não afeta as informações "reais" do cupom, mesmo que ele seja exibido incorretamente como "arquivado" na interface do usuário devido a esse problema, ele poderá ser usado no checkout.
+
+## Simulação
+
+
+A simples criação de um cupom e a verificação de seus dados já o mostra como arquivado.
+
+
+
+## Workaround
+
+
+Não há outra solução além de esperar por um curto período de tempo.
+
+
+
+
+
diff --git a/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md b/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md
new file mode 100644
index 000000000..643e7de07
--- /dev/null
+++ b/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md
@@ -0,0 +1,43 @@
+---
+title: 'A API de criação de produtos não envia nulos como valores de data de lançamento.'
+id: 6IjwYVm9SdNEtW9aNYkSrj
+status: PUBLISHED
+createdAt: 2024-04-29T15:10:44.454Z
+updatedAt: 2024-04-29T15:10:45.337Z
+publishedAt: 2024-04-29T15:10:45.337Z
+firstPublishedAt: 2024-04-29T15:10:45.337Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-api-de-criacao-de-produtos-nao-envia-nulos-como-valores-de-data-de-lancamento
+locale: pt
+kiStatus: Backlog
+internalReference: 1024207
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar as APIs de criação ou atualização de produtos no aplicativo de catálogo: https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product e enviar o campo releaseDate como nulo, em seu valor, ele é criado com a data atual.
+
+## Simulação
+
+
+1 - Criar ou atualizar um novo produto, em sua loja, por meio da API mencionada, passando, no corpo da solicitação, o campo releaseDate como nulo.
+2 - Acesse a UI de administração do catálogo ou use um GET no mesmo caminho da API para buscar os dados enviados
+3 - O campo releaseDate exibirá o valor da data enviada em vez de um valor nulo
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md b/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
new file mode 100644
index 000000000..31f2a3267
--- /dev/null
+++ b/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
@@ -0,0 +1,45 @@
+---
+title: 'A criação de um canal de vendas regionalizado com uma ligação já usada não atualiza o saldo de estoque do item'
+id: 7CqZPslfGY8mTmBLuWe5SQ
+status: PUBLISHED
+createdAt: 2024-03-22T19:39:26.469Z
+updatedAt: 2024-07-01T18:49:34.061Z
+publishedAt: 2024-07-01T18:49:34.061Z
+firstPublishedAt: 2024-03-22T19:39:27.432Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-criacao-de-um-canal-de-vendas-regionalizado-com-uma-ligacao-ja-usada-nao-atualiza-o-saldo-de-estoque-do-item
+locale: pt
+kiStatus: No Fix
+internalReference: 1005112
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Para contas regionalizadas, o sistema de índice filtra, pelos canais de vendas regionalizados, o saldo de estoque que deve aparecer, para não mostrar vínculos de vendas que não são regionalizados.
+
+Se um novo canal precisar ser regionalizado em uma vinculação que já esteja em produção, a indexação não será acionada. Causando alguma inconsistência na disponibilidade dos produtos.
+
+## Simulação
+
+
+
+1. Crie um canal de vendas regionalizado em uma ligação de produção;
+2. Verifique se os estoques e a disponibilidade são consistentes com todos os produtos
+
+## Workaround
+
+
+Force uma reindexação com stockSimulation. Atualize o estoque, por exemplo.
+
+
+
+
+
diff --git a/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md b/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
new file mode 100644
index 000000000..99177cde5
--- /dev/null
+++ b/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
@@ -0,0 +1,46 @@
+---
+title: 'A criação e a exclusão de um grande número de redirecionamentos quebram a página de redirecionamentos'
+id: 5uFuid4a5f7uiRVW9LdT5Q
+status: PUBLISHED
+createdAt: 2024-04-02T19:45:07.540Z
+updatedAt: 2024-04-02T19:45:08.762Z
+publishedAt: 2024-04-02T19:45:08.762Z
+firstPublishedAt: 2024-04-02T19:45:08.762Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: a-criacao-e-a-exclusao-de-um-grande-numero-de-redirecionamentos-quebram-a-pagina-de-redirecionamentos
+locale: pt
+kiStatus: Backlog
+internalReference: 1010392
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Lidar com uma grande quantidade de redirecionamentos pode quebrar a página da interface do usuário. Se você tiver muitos redirecionamentos ou precisar excluir essa grande quantidade, isso poderá levar a um erro em que a página da interface do usuário estará sempre carregando e nunca retornará as informações dos redirecionamentos. Achamos que isso pode acontecer porque, quando excluímos uma grande quantidade de redirecionamentos, as primeiras páginas da consulta `listRedirects` ficam em branco e a interface do usuário procura essas primeiras páginas para carregar os primeiros redirecionamentos e nunca as encontra.
+
+Isso também pode afetar a importação/exportação da CLI.
+
+## Simulação
+
+
+
+- Crie uma grande quantidade de redirecionamentos
+- Tente excluí-los (por meio da interface do usuário ou usando o reescritor)
+- Ao retornar à página da interface do usuário, os redirecionamentos não serão carregado
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md b/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
new file mode 100644
index 000000000..b2b0de365
--- /dev/null
+++ b/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
@@ -0,0 +1,45 @@
+---
+title: 'Criação de redirecionamentos errados contendo caracteres/consultas que não deveriam ser carregados o upload/download do csv por meio da CLI não funciona'
+id: 6ShJSvo6g8ZJFaejSo0gx3
+status: PUBLISHED
+createdAt: 2024-01-25T19:00:17.586Z
+updatedAt: 2024-01-25T19:00:18.204Z
+publishedAt: 2024-01-25T19:00:18.204Z
+firstPublishedAt: 2024-01-25T19:00:18.204Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: criacao-de-redirecionamentos-errados-contendo-caracteresconsultas-que-nao-deveriam-ser-carregados-o-uploaddownload-do-csv-por-meio-da-cli-nao-funciona
+locale: pt
+kiStatus: No Fix
+internalReference: 971936
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Após criar redirecionamentos incorretos contendo caracteres que não devem ser carregados, ou seja, #, consultas ou redirecionamentos que devem ser criados no nível do servidor, o upload/download em massa do csv por meio da CLI não funciona mais: #, consultas ou redirecionamentos que devem ser criados no nível do servidor, o upload/download em massa do csv por meio da CLI não funciona mais.
+
+## Simulação
+
+
+Crie um redirecionamento para uma consulta, por exemplo: /?binding=XXXXX
+Exclua o redirecionamento pelo IDE do Graphql (você não conseguirá excluir de outra forma)
+Tente fazer download ou upload do CSV dos redirecionamentos por meio da CLI e você conseguirá fazer isso.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/etn94WlrSAYOFFj0rZfVwoowE/?name=image.png
+
+## Workaround
+
+
+No momento, não há solução alternativa para isso e o download em massa da CLI não poderá ser usado.
+
+
+
+
+
diff --git a/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md b/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md
new file mode 100644
index 000000000..5ade64065
--- /dev/null
+++ b/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md
@@ -0,0 +1,43 @@
+---
+title: 'A composição dos critérios não é retornada na UI de pesquisa explicada'
+id: 5IyEZe5GBlt732g0rbU5T4
+status: PUBLISHED
+createdAt: 2023-06-29T15:05:18.815Z
+updatedAt: 2023-06-29T15:05:19.578Z
+publishedAt: 2023-06-29T15:05:19.578Z
+firstPublishedAt: 2023-06-29T15:05:19.578Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: a-composicao-dos-criterios-nao-e-retornada-na-ui-de-pesquisa-explicada
+locale: pt
+kiStatus: Backlog
+internalReference: 852898
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando você pesquisa um termo cuja resposta é apenas um produto, esse produto não terá a composição de critérios exibida na tela da pesquisa explicada.
+
+## Simulação
+
+
+Tente abrir a pesquisa explicada e pesquisar um termo cuja resposta seja apenas um produto; esse produto não terá sua composição de critérios na tela.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/crm-error-when-searching-with-spaces.md b/docs/known-issues/pt/crm-error-when-searching-with-spaces.md
index c5cd75265..7fd3a1c91 100644
--- a/docs/known-issues/pt/crm-error-when-searching-with-spaces.md
+++ b/docs/known-issues/pt/crm-error-when-searching-with-spaces.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumário
 
-Usuário recebe uma mensagem de erro ao buscar por um documento com um atributo contendo espaço [Screen Shot 2018-12-26 at 14.38.55](https://images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
+Usuário recebe uma mensagem de erro ao buscar por um documento com um atributo contendo espaço [Screen Shot 2018-12-26 at 14.38.55](//images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
 
 
 Exemplo:  Buscando/filtrando pelo Campo "Cidade" com o atributo "Rio de Janeiro" produzirá uma mensagem de erro.
@@ -32,6 +32,6 @@ Exemplo:  Buscando/filtrando pelo Campo "Cidade" com o atributo "Rio de Janeiro"
 
 ## Workaround
 
-![Screen Shot 2018-12-26 at 14.40.03](https://images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)Felizmente ha um workaround simples que não necessita o uso da API.
+![Screen Shot 2018-12-26 at 14.40.03](//images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)Felizmente ha um workaround simples que não necessita o uso da API.
 Ao clicar em "Todos" no dropdown, a mesma busca pode ser feita sem causar erro.
 
diff --git a/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md b/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md
new file mode 100644
index 000000000..2d573f4fd
--- /dev/null
+++ b/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md
@@ -0,0 +1,45 @@
+---
+title: 'O símbolo da moeda não segue o idioma do administrador'
+id: 7gEGdkDSbRCtk2Q1u2nW6k
+status: PUBLISHED
+createdAt: 2024-03-15T19:37:45.395Z
+updatedAt: 2024-03-15T19:40:56.682Z
+publishedAt: 2024-03-15T19:40:56.682Z
+firstPublishedAt: 2024-03-15T19:37:46.387Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-simbolo-da-moeda-nao-segue-o-idioma-do-administrador
+locale: pt
+kiStatus: Backlog
+internalReference: 1000915
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário acessa a tela de configuração do carrinho na área de pedidos (`https://{accountname}}.myvtex.com/admin/checkout/#/configurations )` o símbolo da moeda segue as convenções da localidade indicada pelo administrador, a troca desse símbolo é feita sempre que o administrador indica uma localidade diferente, porém de acordo com nossa análise essa troca está falhando em determinados momentos, fazendo com que o símbolo da moeda indicada seja o padrão da página que nesse caso é R$.
+
+## Simulação
+
+
+
+
+- Faça login no administrador
+- Vá para https://.myvtex.com/admin/checkout/#/configurations
+- Altere a localidade para PT e de volta para EN;
+- Atualize a página e você verá que o símbolo da moeda ainda é R$
+
+## Workaround
+
+
+No momento, não temos uma solução alternativa para esse cenário, mas ele não afeta a operação da loja, pois o símbolo de moeda nessa área é apenas visual, sem impacto operacional na loja.
+
+
+
+
diff --git a/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md b/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md
new file mode 100644
index 000000000..a535016d4
--- /dev/null
+++ b/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md
@@ -0,0 +1,44 @@
+---
+title: 'Mapeador de atributos personalizado Mercado Livre'
+id: 4A7inX7nFte4jRhZRLkPRO
+status: PUBLISHED
+createdAt: 2023-12-12T09:59:40.945Z
+updatedAt: 2024-02-16T20:26:22.091Z
+publishedAt: 2024-02-16T20:26:22.091Z
+firstPublishedAt: 2023-12-12T09:59:41.722Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mapeador-de-atributos-personalizado-mercado-livre
+locale: pt
+kiStatus: No Fix
+internalReference: 521197
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Na nova tela do mapeador, não temos a opção de criar um atributo personalizado no MELI.
+
+## Simulação
+
+
+
+Dentro da tela do Mapper, o atributo personalizado está ausente do que tínhamos na planilha.
+
+
+
+## Workaround
+
+
+No momento, não há solução alternativa disponível, pois só é permitido criar um valor personalizado dentro do atributo, mas não um atributo personalizado.
+
+
+
+
diff --git a/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md b/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
new file mode 100644
index 000000000..0eb2cd3bc
--- /dev/null
+++ b/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
@@ -0,0 +1,44 @@
+---
+title: 'Elementos personalizados em cms legados não funcionam com mais de um HTML'
+id: 6hGraRq2ffsw5c3jJ8nwh0
+status: PUBLISHED
+createdAt: 2023-07-31T16:35:04.392Z
+updatedAt: 2023-07-31T16:35:05.018Z
+publishedAt: 2023-07-31T16:35:05.018Z
+firstPublishedAt: 2023-07-31T16:35:05.018Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: elementos-personalizados-em-cms-legados-nao-funcionam-com-mais-de-um-html
+locale: pt
+kiStatus: Backlog
+internalReference: 871480
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar um elemento personalizado com mais de um elemento HTML, somente o primeiro é carregado no modelo.
+
+## Simulação
+
+
+
+1. Crie um elemento personalizado com o tipo HTML;
+2. Crie pelo menos 2 códigos html nesse elemento personalizado;
+3. Verifique se o modelo que tem esse elemento personalizado carrega apenas o primeiro HTML
+
+## Workaround
+
+
+Reúna todos os htmls em apenas um elemento no elemento personalizado.
+
+
+
+
+
diff --git a/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md b/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
index 440126c19..49ed8b57d 100644
--- a/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
+++ b/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
@@ -3,8 +3,8 @@ title: 'A imagem em miniatura de vídeo personalizada não é exibida na versão
 id: 5d71mBz4kXdwX7AhspYhit
 status: PUBLISHED
 createdAt: 2022-03-21T17:51:55.027Z
-updatedAt: 2022-11-25T21:54:30.917Z
-publishedAt: 2022-11-25T21:54:30.917Z
+updatedAt: 2024-07-01T18:48:03.005Z
+publishedAt: 2024-07-01T18:48:03.005Z
 firstPublishedAt: 2022-03-21T17:51:55.483Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: a-imagem-em-miniatura-de-video-personalizada-nao-e-exibida-na-versao-movel
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 412632
 ---
 
diff --git a/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md b/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
index 42272376e..fc36411f9 100644
--- a/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
+++ b/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
@@ -3,8 +3,8 @@ title: 'O status das faturas de crédito do cliente na página MyCredits não es
 id: 413knN4Gtk9GuZV5zFlw7k
 status: PUBLISHED
 createdAt: 2022-03-27T17:49:32.464Z
-updatedAt: 2022-11-25T22:06:46.582Z
-publishedAt: 2022-11-25T22:06:46.582Z
+updatedAt: 2024-02-16T20:25:28.872Z
+publishedAt: 2024-02-16T20:25:28.872Z
 firstPublishedAt: 2022-03-27T17:49:33.246Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: o-status-das-faturas-de-credito-do-cliente-na-pagina-mycredits-nao-esta-correto
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 369457
 ---
 
diff --git a/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
new file mode 100644
index 000000000..4b0f6ea44
--- /dev/null
+++ b/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -0,0 +1,43 @@
+---
+title: 'As informações do cliente estão sendo perdidas quando há algum pedido com "profileErrorOnLoading"'
+id: 7B0eutLBOCKOun4iwALVpq
+status: PUBLISHED
+createdAt: 2023-06-27T12:51:33.790Z
+updatedAt: 2023-06-27T12:51:34.237Z
+publishedAt: 2023-06-27T12:51:34.237Z
+firstPublishedAt: 2023-06-27T12:51:34.237Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: as-informacoes-do-cliente-estao-sendo-perdidas-quando-ha-algum-pedido-com-profileerroronloading
+locale: pt
+kiStatus: Backlog
+internalReference: 340036
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o pedido tem "profileErrorOnLoading=true", o comportamento esperado é que o perfil do cliente, o endereço e o cartão de crédito não sejam salvos/atualizados no Profile System.
+
+O problema é que o checkout ainda está fazendo algumas solicitações para registrar o e-mail do comprador, naturalmente, sem enviar outros campos como nome e telefone. Assim, se o cliente já estiver registrado na loja, esses campos são apagados e os dados do cliente são perdidos.
+
+## Simulação
+
+
+Não podemos simular o comportamento, pois o "profileErrorOnLoading" é apenas para exceções inesperadas.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md b/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md
index 1d76f4e40..a08d98a72 100644
--- a/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md
+++ b/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md
@@ -1,18 +1,18 @@
 ---
-title: 'As informações do cliente não são salvas no Sistema de Perfil'
+title: 'As informações do cliente não são salvas no Profile System'
 id: 1MCiEAJ3ZueJVM04T7x9z2
 status: PUBLISHED
 createdAt: 2023-04-04T22:47:43.035Z
-updatedAt: 2023-04-06T17:51:29.025Z
-publishedAt: 2023-04-06T17:51:29.025Z
+updatedAt: 2023-11-01T12:37:24.071Z
+publishedAt: 2023-11-01T12:37:24.071Z
 firstPublishedAt: 2023-04-04T22:47:43.593Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: as-informacoes-do-cliente-nao-sao-salvas-no-sistema-de-perfil
+slug: as-informacoes-do-cliente-nao-sao-salvas-no-profile-system
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 784763
 ---
 
@@ -23,20 +23,16 @@ internalReference: 784763
 </div>
 
 
-s vezes, as informações de um novo cliente não são salvas no Sistema de Perfil.
+Às vezes, as informações de um novo cliente não são salvas no Profile System.
 
-Ao verificar as interações do pedido, haverá um evento chamado "Perfil do usuário salvo no Sistema de Perfis", mas ao procurar o e-mail do cliente no Master Data, não haverá resultados.
-
-
-##
+Ao verificar as interações do pedido, haverá um evento chamado "Perfil do usuário salvo no Sistema de Perfis", mas ao pesquisar o e-mail do cliente nos dados mestre, não haverá resultados.
 
 ## Simulação
 
 
-Não há uma maneira direta de reproduzir este cenário.
+Não há uma maneira direta de reproduzir esse cenário.
 
 
-##
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md b/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
index c5e330609..d700008ea 100644
--- a/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
+++ b/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
@@ -3,8 +3,8 @@ title: 'Expressão de cluster personalizada não funcionando em promoção de re
 id: 27QJfNVhuPNiRxqQiXPRt2
 status: PUBLISHED
 createdAt: 2022-03-16T19:36:36.102Z
-updatedAt: 2022-11-25T22:12:51.339Z
-publishedAt: 2022-11-25T22:12:51.339Z
+updatedAt: 2024-02-16T20:29:37.996Z
+publishedAt: 2024-02-16T20:29:37.996Z
 firstPublishedAt: 2022-03-16T19:36:36.504Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: expressao-de-cluster-personalizada-nao-funcionando-em-promocao-de-remessa-gratuita-canal-de-vendas-padrao-1
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 334027
 ---
 
diff --git a/docs/known-issues/pt/cvv-without-validation-of-characters-type.md b/docs/known-issues/pt/cvv-without-validation-of-characters-type.md
index 957e3a185..0dc52990e 100644
--- a/docs/known-issues/pt/cvv-without-validation-of-characters-type.md
+++ b/docs/known-issues/pt/cvv-without-validation-of-characters-type.md
@@ -3,8 +3,8 @@ title: 'CVV sem validação de caracteres tipo'
 id: 63MJ3ODCvr3ayfgJiuN1ja
 status: PUBLISHED
 createdAt: 2022-03-27T20:25:43.400Z
-updatedAt: 2022-11-25T22:07:55.541Z
-publishedAt: 2022-11-25T22:07:55.541Z
+updatedAt: 2024-02-16T20:29:04.636Z
+publishedAt: 2024-02-16T20:29:04.636Z
 firstPublishedAt: 2022-03-27T20:25:43.819Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: cvv-sem-validacao-de-caracteres-tipo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 425204
 ---
 
diff --git a/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md b/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md
new file mode 100644
index 000000000..22b83c782
--- /dev/null
+++ b/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md
@@ -0,0 +1,40 @@
+---
+title: 'Renderização do sistema de pagamento desativado no checkout'
+id: 2LQYOKtkURQoWUU1InCRUo
+status: PUBLISHED
+createdAt: 2024-06-13T19:37:58.649Z
+updatedAt: 2024-06-13T19:37:59.481Z
+publishedAt: 2024-06-13T19:37:59.481Z
+firstPublishedAt: 2024-06-13T19:37:59.481Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: renderizacao-do-sistema-de-pagamento-desativado-no-checkout
+locale: pt
+kiStatus: Backlog
+internalReference: 1049543
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O problema parece ocorrer apenas em subcontas, mesmo desativado (também excluído) o método de pagamento é renderizado no checkout
+
+## Simulação
+
+
+Não foi possível fazer a simulação
+
+## Workaround
+
+
+Uma correção manual pode ser realizada; a equipe de suporte deve ser contatada para isso.
+
+
+
+
diff --git a/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md b/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md
new file mode 100644
index 000000000..1b3e33d1e
--- /dev/null
+++ b/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md
@@ -0,0 +1,45 @@
+---
+title: 'Erro de deadlocked ao usar as APIs do Catalog'
+id: 6A4jBKBKIzn87mxNQJ4YQN
+status: PUBLISHED
+createdAt: 2023-07-14T18:29:11.937Z
+updatedAt: 2023-07-19T14:16:39.062Z
+publishedAt: 2023-07-19T14:16:39.062Z
+firstPublishedAt: 2023-07-14T18:29:13.088Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: erro-de-deadlocked-ao-usar-as-apis-do-catalog
+locale: pt
+kiStatus: Backlog
+internalReference: 862626
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O uso constante de algumas APIs de catálogo, como "Add SKU to Subcollection" (Adicionar SKU à subcoleção) ou a tentativa de vincular produtos por meio do módulo de sugestões pode causar erros de bloqueio para o comerciante.
+
+Os erros de deadlocked podem ocorrer quando há uma simultaneidade na gravação dos dados no banco de dados. Portanto, quando se solicita muito da API em um curto período de tempo, esses erros são mais evidentes.
+
+## Simulação
+
+
+
+1. Use, por exemplo, a API Add SKU to Subcollection (https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/subcollection/-subCollectionId-/stockkeepingunit) para adicionar muitos skus a uma coleção em um curto período de tempo;
+2. Verifique se podem ocorrer erros, como um deadlocked
+
+## Workaround
+
+
+Tente fazer menos solicitações por minuto.
+
+
+
+
+
diff --git a/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md b/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
index 93e34946f..e50ea71dd 100644
--- a/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
+++ b/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
@@ -3,8 +3,8 @@ title: 'Os pagamentos de débito usando o conector Firstdata não podem ser liqu
 id: 6imTj4PTpJGGFqyhSLTPu9
 status: PUBLISHED
 createdAt: 2022-03-03T21:59:55.119Z
-updatedAt: 2022-11-25T22:05:01.885Z
-publishedAt: 2022-11-25T22:05:01.885Z
+updatedAt: 2024-02-16T20:24:59.932Z
+publishedAt: 2024-02-16T20:24:59.932Z
 firstPublishedAt: 2022-03-03T21:59:55.506Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: os-pagamentos-de-debito-usando-o-conector-firstdata-nao-podem-ser-liquidados-devido-a-um-erro-no-campo-transactionstate
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 461095
 ---
 
@@ -23,26 +23,25 @@ internalReference: 461095
 </div>
 
 
-Ao utilizar o conector Firstdata para processar pagamentos de débito, nosso código espera que o campo `TransactionState` seja "CAPTURADO". Entretanto, o provedor está enviando "CAPTURED", bem como "SETTLED", o que desencadeia um erro:
+Ao utilizar o conector Firstdata para processar pagamentos de débito, nosso código foi projetado para esperar que o campo TransactionState seja definido como "CAPTURED". No entanto, encontramos um problema em que o provedor está enviando os valores "CAPTURED" e "SETTLED", o que está causando um erro:
 
-Mensagem: Unknown Error on AutoSettleHá um erro no documento XML (1, 745).
-&
-Erro ao executar a operação de liquidação. Por favor, veja a exceção interna. Conector = Primeiros dados. Mensagem = A cadeia de entrada não estava em um formato correto.
-
-Não consegui encontrar na documentação dos primeiros dados qual é a correta, mas existem exemplos para ambos.
 
+    Mensagem de erro: Erro desconhecido no AutoSettle. Há um erro no documento XML (1, 745). & Erro ao executar a operação de liquidação. Consulte a exceção interna. Conector: Firstdata. Mensagem: A string de entrada não estava no formato correto.
 
 
 ## Simulação
 
 
-
-Às vezes, quando uma transação é cancelada usando este conector, é possível observar este comportamento.
+Não é possível simular, pois esse é um comportamento intermitente que depende da resposta do provedor de pagamento.
 
 
 
 ## Workaround
 
 
-Não há nenhuma solução disponível.
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md b/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
new file mode 100644
index 000000000..55df12047
--- /dev/null
+++ b/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
@@ -0,0 +1,42 @@
+---
+title: 'As regras de Crédito ao Cliente excluídas aparecerão no checkout se não tiverem sido desativadas anteriormente'
+id: 7culNJ04UcZfzgHFREyNEs
+status: PUBLISHED
+createdAt: 2024-03-04T23:12:22.826Z
+updatedAt: 2024-03-04T23:12:23.859Z
+publishedAt: 2024-03-04T23:12:23.859Z
+firstPublishedAt: 2024-03-04T23:12:23.859Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: as-regras-de-credito-ao-cliente-excluidas-aparecerao-no-checkout-se-nao-tiverem-sido-desativadas-anteriormente
+locale: pt
+kiStatus: Backlog
+internalReference: 994066
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se você tiver o aplicativo `vtex.custom-payments` instalado e excluir uma regra de pagamento de crédito do cliente sem desativá-la primeiro, ela será processada no checkout.
+
+## Simulação
+
+
+Com o `vtex.custom-payments` instalado na conta, crie várias regras de parcelamento do Customer Credit e exclua uma delas sem desativá-la; você a verá no checkout.
+
+
+
+## Workaround
+
+
+É possível corrigir isso manualmente com a ajuda da equipe de suporte.
+
+
+
+
diff --git a/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md b/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
new file mode 100644
index 000000000..ccfe96344
--- /dev/null
+++ b/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
@@ -0,0 +1,44 @@
+---
+title: 'A capacidade de entrega não é respeitada se houver espaço no Id da Política de Remessa'
+id: 1OyY54G05o15EI2zAmW4Vq
+status: PUBLISHED
+createdAt: 2023-07-14T21:25:50.522Z
+updatedAt: 2024-03-19T19:26:55.344Z
+publishedAt: 2024-03-19T19:26:55.344Z
+firstPublishedAt: 2023-07-14T21:25:51.117Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: a-capacidade-de-entrega-nao-e-respeitada-se-houver-espaco-no-id-da-politica-de-remessa
+locale: pt
+kiStatus: Backlog
+internalReference: 862830
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se o recurso de agendamento de entrega estiver em uso e a capacidade de entrega estiver ativada, há dois cenários conhecidos que podem tornar a janela disponível mesmo depois de ter atingido o limite máximo de capacidade configurado.
+Os cenários são: O ID da política de remessa com um espaço ou um número excessivo de caracteres na cadeia de caracteres, `AccountName+ShippingPolicyId` não pode exceder 60 caracteres.
+
+## Simulação
+
+
+Crie uma política de remessa e, em seu Id, insira um espaço ou `AccountName+ShippingPolicyId` que resulte em mais de 60 caracteres, configure a entrega programada e a capacidade de entrega.
+Faça os pedidos selecionando a janela registrada, verifique se será possível criar mais pedidos do que o máximo configurado na capacidade de entrega.
+No checkout, quando o limite configurado for atingido, a janela não deverá ficar indisponível, mas permanecerá visível e poderá ser selecionada
+
+## Workaround
+
+
+Não registre nenhum Id com um espaço na política de envio ou com mais de 60 caracteres somando os caracteres no `AccountName+ShippingPolicyId`.
+
+
+
+
+
diff --git a/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md b/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md
new file mode 100644
index 000000000..277359696
--- /dev/null
+++ b/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md
@@ -0,0 +1,47 @@
+---
+title: 'Divisão da entrega com o Lean Shipping oferecendo SLA inválido'
+id: 61Yq1WhmCclFtcum3YMtXn
+status: PUBLISHED
+createdAt: 2024-02-27T19:21:21.615Z
+updatedAt: 2024-02-27T19:26:27.513Z
+publishedAt: 2024-02-27T19:26:27.513Z
+firstPublishedAt: 2024-02-27T19:21:22.667Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: divisao-da-entrega-com-o-lean-shipping-oferecendo-sla-invalido
+locale: pt
+kiStatus: Backlog
+internalReference: 990155
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um carrinho de compras inclui produtos de diferentes vendedores, com diferentes canais de entrega e IDs de SLA entre eles, a interface do usuário do Checkout ativa o Lean Shipping, resumindo os SLAs disponíveis para exibir apenas as opções "mais rápida" e "mais barata" para cada item.
+
+No entanto, se houver uma opção de entrega agendada, mas ela não for a mais rápida ou a mais barata, a alternância de agendamento ainda aparecerá na interface do usuário, embora o Lean Shipping não a selecione como uma opção viável.
+
+## Simulação
+
+
+
+- Monte um carrinho com pelo menos 2 vendedores diferentes, em que um item tenha 3 SLAs, em que o agendado não seja a opção mais rápida nem a mais barata (e, portanto, não será oferecido pelo Lean Shipping).
+- Selecione a retirada na loja.
+- Use a interface de agendamento da interface do usuário para a entrega do outro item.
+- Observe que ele ainda aplica o SLA mais rápido/mais barato (não programado), em vez do programado, ignorando efetivamente a seleção da janela de entrega da etapa anterior
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md b/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md
new file mode 100644
index 000000000..99a630cde
--- /dev/null
+++ b/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md
@@ -0,0 +1,45 @@
+---
+title: 'O nome do departamento não está sendo carregado na interface do usuário das comissões de gerenciamento de vendedores'
+id: 5TkKtfYi5oFxNOk0mTTeiQ
+status: PUBLISHED
+createdAt: 2024-03-25T17:20:22.888Z
+updatedAt: 2024-03-25T17:20:23.761Z
+publishedAt: 2024-03-25T17:20:23.761Z
+firstPublishedAt: 2024-03-25T17:20:23.761Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: o-nome-do-departamento-nao-esta-sendo-carregado-na-interface-do-usuario-das-comissoes-de-gerenciamento-de-vendedores
+locale: pt
+kiStatus: Backlog
+internalReference: 1005799
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao selecionar um departamento para definir uma comissão específica no gerenciamento de vendedores, a tabela não está carregando o nome do departamento. O comportamento não ocorre em categorias secundárias.
+ ![](https://vtexhelp.zendesk.com/attachments/token/irbcBV8R7kNO4F5XsLHtaxUMO/?name=image.png)
+
+## Simulação
+
+
+
+1. Ative a opção "Add commissions by category" (Adicionar comissões por categoria)
+2. Selecione um departamento para mapear as comissões e salve o vendedor
+3. Verifique se a interface do usuário não está carregando o nome do departamento
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md b/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md
index 86a8f3b5f..652de59a9 100644
--- a/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md
+++ b/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md
@@ -3,8 +3,8 @@ title: 'Os diacríticos são removidos no CatalogAPI'
 id: 2iVyAQ8TSaT3jFYzcQGjSs
 status: PUBLISHED
 createdAt: 2022-07-22T18:18:04.236Z
-updatedAt: 2022-11-25T21:44:21.525Z
-publishedAt: 2022-11-25T21:44:21.525Z
+updatedAt: 2024-02-16T20:28:19.994Z
+publishedAt: 2024-02-16T20:28:19.994Z
 firstPublishedAt: 2022-07-22T18:18:05.160Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: os-diacriticos-sao-removidos-no-catalogapi
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 623345
 ---
 
diff --git a/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md b/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md
new file mode 100644
index 000000000..d8caa3102
--- /dev/null
+++ b/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md
@@ -0,0 +1,45 @@
+---
+title: 'Diferença de preços entre PDP, PLP e carrinho de compras'
+id: 3Oo5ccYOG7hcEXYaROxXMV
+status: PUBLISHED
+createdAt: 2023-06-29T20:02:13.485Z
+updatedAt: 2023-06-29T20:02:14.572Z
+publishedAt: 2023-06-29T20:02:14.572Z
+firstPublishedAt: 2023-06-29T20:02:14.572Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: diferenca-de-precos-entre-pdp-plp-e-carrinho-de-compras
+locale: pt
+kiStatus: Backlog
+internalReference: 853175
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+O portal está fornecendo o mesmo conteúdo nos PDPs e PLPs, mesmo após algumas atualizações, como promoções.
+
+## Simulação
+
+
+
+Com um cache expirado, a CDN pergunta ao sistema do portal se a página foi alterada. Em caso afirmativo, o portal fornece a nova página a ser renderizada; caso contrário, a CDN redesenha a página que já possui.
+
+Nesse caso, vimos que, embora a página tenha sofrido algumas alterações, a inclusão de uma promoção, o portal retornou à CDN que não houve alteração em comparação com a página em cache e, portanto, a camada de borda estava renderizando a página sem promoção
+
+## Workaround
+
+
+
+Uma maneira de contornar isso era **alterar o modelo da página do produto (como incluir um comentário**), para que o portal informasse que havia uma alteração na estrutura e a CDN recebesse a nova página para ser armazenada em cache.
+
+
+
+
diff --git a/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md b/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md
new file mode 100644
index 000000000..6f9a478b1
--- /dev/null
+++ b/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md
@@ -0,0 +1,50 @@
+---
+title: 'Diferenças entre o valor da especificação nas APIs e no portal'
+id: 29Utcf4B7PBZitEHxrZwbE
+status: PUBLISHED
+createdAt: 2023-06-29T20:11:49.484Z
+updatedAt: 2023-07-06T13:41:29.683Z
+publishedAt: 2023-07-06T13:41:29.683Z
+firstPublishedAt: 2023-06-29T20:11:50.157Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: diferencas-entre-o-valor-da-especificacao-nas-apis-e-no-portal
+locale: pt
+kiStatus: Backlog
+internalReference: 853184
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, essas duas APIs ("api/catalog" e "api/catalog_system" GET Specification Value) estão consultando tabelas diferentes no banco de dados do catálogo. Os valores devem ser os mesmos em ambas as tabelas, mas os cenários com caracteres especiais podem divergir.
+
+Isso também se reflete no Portal e nos PDPs, pois as informações estão sendo geradas com base na tabela errada. Os caracteres especiais aparecem como "????" no frontend.
+
+## Simulação
+
+
+
+1. Ter um valor de especificação com caracteres especiais;
+2. Verifique os resultados nas APIs "api/catalog" e "api/catalog_system";
+3. Verifique as informações do PDP;
+4. Verificar se foram iguais.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md b/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
index bfe6d0d47..fc2ee810c 100644
--- a/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
+++ b/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
@@ -3,8 +3,8 @@ title: 'O layout de divulgação não pode ser usado corretamente quando a anima
 id: 14QweVpzLO8TsyI68H79ZG
 status: PUBLISHED
 createdAt: 2022-04-19T19:53:22.409Z
-updatedAt: 2022-11-25T22:13:15.022Z
-publishedAt: 2022-11-25T22:13:15.022Z
+updatedAt: 2024-07-01T18:48:05.329Z
+publishedAt: 2024-07-01T18:48:05.329Z
 firstPublishedAt: 2022-04-19T19:53:23.090Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: o-layout-de-divulgacao-nao-pode-ser-usado-corretamente-quando-a-animacao-de-propulsao-e-definida-como-verdadeira
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 417947
 ---
 
diff --git a/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md b/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
new file mode 100644
index 000000000..31bce83a0
--- /dev/null
+++ b/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
@@ -0,0 +1,42 @@
+---
+title: 'Discrepância na contagem de uso de cupons no OMS e na interface do usuário de cupons'
+id: 5PyOeirr1XqXREmQJpSHs1
+status: PUBLISHED
+createdAt: 2023-12-18T21:53:26.360Z
+updatedAt: 2023-12-18T21:53:27.039Z
+publishedAt: 2023-12-18T21:53:27.039Z
+firstPublishedAt: 2023-12-18T21:53:27.039Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: discrepancia-na-contagem-de-uso-de-cupons-no-oms-e-na-interface-do-usuario-de-cupons
+locale: pt
+kiStatus: Backlog
+internalReference: 954959
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns pedidos não estão sendo recuperados no uso dos cupons, identificamos que alguns pedidos não estavam sendo contados pelo administrador de cupons.
+
+## Simulação
+
+
+Verificar se entre 10/09 e 13/09 há alguma discrepância entre os usos dos cupon
+
+## Workaround
+
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md b/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md
index 24f0b10ce..74b242838 100644
--- a/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md
+++ b/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md
@@ -26,7 +26,7 @@ O pedido é fechado e transacionado normalmente na VTEX mas, dependendo dos flux
 
 Exemplo de ocorrência:
 
-![image](https://images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
 
 Nesse caso, o valor total do pedido cobrado do cliente ficou em `R$ 7,98`. No entanto, ao somar os valores de venda registrados em cada produto, o total seria de `R$ 7,95`.
 
diff --git a/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md b/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
new file mode 100644
index 000000000..66f26fd83
--- /dev/null
+++ b/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
@@ -0,0 +1,45 @@
+---
+title: 'Divergência nas configurações avançadas do Store em novas contas ou espaços de trabalho'
+id: 1Jt8McqXjYAxfJNkBZHt4j
+status: PUBLISHED
+createdAt: 2024-07-11T18:16:01.106Z
+updatedAt: 2024-07-11T18:16:02.006Z
+publishedAt: 2024-07-11T18:16:02.006Z
+firstPublishedAt: 2024-07-11T18:16:02.006Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: divergencia-nas-configuracoes-avancadas-do-store-em-novas-contas-ou-espacos-de-trabalho
+locale: pt
+kiStatus: Backlog
+internalReference: 1064235
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Em novos espaços de trabalho ou contas que nunca alteraram as configurações avançadas das Configurações da loja, é possível verificar uma inconsistência entre as informações na interface do usuário e o sinalizador aplicado à conta.
+
+## Simulação
+
+
+
+- Criar um novo espaço de trabalho
+- Vá para Configurações do Store na guia Avançado
+- Veja que alguns sinalizadores estão definidos na interface do usuário
+- Verifique as configurações usando o plug-in de configurações com o seguinte comando `vtex settings get vtex.store`.
+- Veja que os sinalizadores não são aplicados
+
+## Workaround
+
+
+Clique no botão "Save" (Salvar) na interface do usuário
+
+
+
+
diff --git a/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md b/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md
index 6c59943f4..3f4f6d553 100644
--- a/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md
+++ b/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md
@@ -3,8 +3,8 @@ title: 'Status divergente na lista de transações e na transação'
 id: 1LD32IQJFbvlOJzD12KL64
 status: PUBLISHED
 createdAt: 2022-03-03T18:41:10.292Z
-updatedAt: 2022-11-25T22:09:15.186Z
-publishedAt: 2022-11-25T22:09:15.186Z
+updatedAt: 2023-12-12T22:12:02.916Z
+publishedAt: 2023-12-12T22:12:02.916Z
 firstPublishedAt: 2022-03-03T18:41:10.764Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: status-divergente-na-lista-de-transacoes-e-na-transacao
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 308919
 ---
 
@@ -23,20 +23,21 @@ internalReference: 308919
 </div>
 
 
-O status das transações é diferente uma vez que você as abre em comparação com o que é mostrado na lista da transação.
-
-
+O status das transações é diferente quando você as abre em comparação com o que é mostrado na lista de transações.
 
 ## Simulação
 
 
-Como isso não acontece em todas as transações, a maneira de simular é entrar em uma transação aleatória e verificar se o status dentro dela é o mesmo que está definido na lista de transações.
-Uma vez que se entra na transação, de fato, o status é diferente
+Como isso não acontece em todas as transações, a maneira de simulá-lo é entrar em uma transação aleatória e verificar se o status dentro dela é o mesmo que está definido na lista de transações.
+Quando você entra na transação, de fato, o status é diferente
 
 
 
 ## Workaround
 
 
-Não há uma solução.
+Não há uma solução alternativa.
+
+
+
 
diff --git a/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md b/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
new file mode 100644
index 000000000..73e44d7c7
--- /dev/null
+++ b/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
@@ -0,0 +1,44 @@
+---
+title: 'O campo de número de documento (RUT) está tendo o último dígito excluído aleatoriamente no iOS'
+id: 6KcbAWPN3AylZEm6IkSw3I
+status: PUBLISHED
+createdAt: 2023-10-18T22:53:27.101Z
+updatedAt: 2023-10-19T13:02:18.095Z
+publishedAt: 2023-10-19T13:02:18.095Z
+firstPublishedAt: 2023-10-18T22:53:27.624Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-campo-de-numero-de-documento-rut-esta-tendo-o-ultimo-digito-excluido-aleatoriamente-no-ios
+locale: pt
+kiStatus: Backlog
+internalReference: 921944
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Somente no Safari/iOS, ao preencher o número do documento e percorrer os campos de dados do cliente, o campo do número do documento (RUT) terá o último dígito excluído.
+
+## Simulação
+
+
+
+- Insira um número de documento válido no campo RUT;
+- Vá para o campo seguinte (telefone);
+- Volte ao campo de documento, exclua e digite o mesmo número;
+- Altere a entrada novamente, e o último dígito do campo RUT será excluído
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md b/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
index 0ceae7309..1d417cdbe 100644
--- a/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
+++ b/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
@@ -3,8 +3,8 @@ title: 'Entradas duplicadas para categorias/valores de especificação no mesmo
 id: IoWI8yx1cabm4bWhSU4Ek
 status: PUBLISHED
 createdAt: 2022-04-18T18:53:37.507Z
-updatedAt: 2022-11-25T21:58:08.677Z
-publishedAt: 2022-11-25T21:58:08.677Z
+updatedAt: 2024-02-16T20:26:00.077Z
+publishedAt: 2024-02-16T20:26:00.077Z
 firstPublishedAt: 2022-04-18T18:53:38.097Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: entradas-duplicadas-para-categoriasvalores-de-especificacao-no-mesmo-nivel
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 562588
 ---
 
diff --git a/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md b/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md
new file mode 100644
index 000000000..0420a7ba8
--- /dev/null
+++ b/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md
@@ -0,0 +1,44 @@
+---
+title: 'Organizações duplicadas no modal para alternar entre organizações'
+id: 7pOIj0RzcmA5mZy60OpfRk
+status: PUBLISHED
+createdAt: 2024-02-22T16:51:15.327Z
+updatedAt: 2024-02-22T16:51:16.213Z
+publishedAt: 2024-02-22T16:51:16.213Z
+firstPublishedAt: 2024-02-22T16:51:16.213Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: organizacoes-duplicadas-no-modal-para-alternar-entre-organizacoes
+locale: pt
+kiStatus: Backlog
+internalReference: 986868
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário tem muitas organizações registradas e usa o modal para alternar entre organizações, algumas organizações serão mostradas duplicadas na lista.
+
+## Simulação
+
+
+
+- Configure várias organizações para o mesmo e-mail;
+- Faça login e abra o modal para alternar a organização;
+- Algumas organizações serão duplicadas na lista
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md b/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
new file mode 100644
index 000000000..707e344d7
--- /dev/null
+++ b/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
@@ -0,0 +1,45 @@
+---
+title: 'Campo Ean como string sendo ignorado quando aprovado em Skus recebidos'
+id: 3ubVdtlt8ElWzQGFM9OTTq
+status: PUBLISHED
+createdAt: 2023-09-11T16:37:06.258Z
+updatedAt: 2023-11-28T16:54:04.790Z
+publishedAt: 2023-11-28T16:54:04.790Z
+firstPublishedAt: 2023-09-11T16:37:07.098Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: campo-ean-como-string-sendo-ignorado-quando-aprovado-em-skus-recebidos
+locale: pt
+kiStatus: Backlog
+internalReference: 897301
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O vendedor envia o sku com todos os campos declarados neste artigo (https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-) para o marketplace aprovar no módulo Received Skus.
+
+O campo ean é declarado como do tipo string no artigo acima. No entanto, apesar de aparecer na UI Received Skus, está sendo ignorado pelo sistema de backend do matcher e também pelo módulo de catálogo, o que significa que o sku está sendo criado com esse campo vazio.
+
+## Simulação
+
+
+1. Envie um sku para o marketplace com o campo ean definido como string: `"ean": "123456"`
+2. Aprovar o sku como um novo produto no módulo Received Skus do marketplace;
+3. Verifique se no catálogo esse campo está definido como vazio.
+
+## Workaround
+
+
+**Até que esse problema seja corrigido e o sistema esteja funcionando de acordo com nossos documentos**, o formato que está funcionando atualmente está enviando o campo ean como um array:
+`"ean": ["123456"]`
+
+Outra maneira é definir esse campo manualmente no lado do catálogo depois que o sku for aprovado.
+
+
diff --git a/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md b/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
new file mode 100644
index 000000000..f4bceb23f
--- /dev/null
+++ b/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
@@ -0,0 +1,54 @@
+---
+title: 'A Early Capture está competindo indevidamente com a Automatic Capture na AuthorizeDotNet'
+id: 2IDoJIBiGzhkVZGHurLsnj
+status: PUBLISHED
+createdAt: 2023-07-20T18:08:30.934Z
+updatedAt: 2023-07-20T18:08:31.479Z
+publishedAt: 2023-07-20T18:08:31.479Z
+firstPublishedAt: 2023-07-20T18:08:31.479Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: a-early-capture-esta-competindo-indevidamente-com-a-automatic-capture-na-authorizedotnet
+locale: pt
+kiStatus: Backlog
+internalReference: 866068
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Para que possamos entender esse comportamento, primeiro precisamos compreender a diferença entre captura automática e captura antecipada:
+
+**Captura automática:** Chamará a solicitação de liquidação automaticamente assim que a data for atingida, independentemente de a transação ser ou não aprovada pelo adquirente e pela antifraude.
+
+**Captura Antecipada: Chamará a solicitação de liquidação depois que a antifraude aprovar a transação, quando a quantidade de dias configurada for atingida.
+
+Nesse conector, a captura automática é codificada para ocorrer após 4 dias, enquanto a captura antecipada pode ser configurada para um máximo de 10 dias após a aprovação da antifraude. Elas acabam competindo entre si e, se a captura antecipada for configurada com um valor maior que 4 dias, a captura automática sempre ocorrerá mais cedo, portanto, sempre será chamada primeiro.
+
+Isso faz com que os valores permitidos na captura antecipada sejam inúteis se forem maiores que 4 dias.
+
+## Simulação
+
+
+
+
+1. Configure o conector AuthorizeDotNet em sua loja;
+2. Defina o campo "Early Capture" (Captura antecipada) como um valor superior a 4 dias;
+3. Faça uma transação de teste;
+4. Vá para a interface do usuário da transação e veja como o valor da programação para a captura automática é chamado primeiro
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md b/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
index aa0a4d11f..210cb95f2 100644
--- a/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
+++ b/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
@@ -3,8 +3,8 @@ title: 'As transações da marca de cartão da Elo com a ERedeRest não estão r
 id: 2OSpQyzDkiGioqcEmhuXpk
 status: PUBLISHED
 createdAt: 2023-05-08T20:29:59.412Z
-updatedAt: 2023-05-08T20:36:20.200Z
-publishedAt: 2023-05-08T20:36:20.200Z
+updatedAt: 2024-02-16T20:27:48.477Z
+publishedAt: 2024-02-16T20:27:48.477Z
 firstPublishedAt: 2023-05-08T20:29:59.878Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: as-transacoes-da-marca-de-cartao-da-elo-com-a-erederest-nao-estao-respeitando-a-captura-antecipada
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 350814
 ---
 
diff --git a/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md b/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md
new file mode 100644
index 000000000..5afd8b1f5
--- /dev/null
+++ b/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md
@@ -0,0 +1,44 @@
+---
+title: 'O e-mail não é preenchido automaticamente para novos compradores após o login'
+id: 2H6REXZGS6utlWmYKoPmGq
+status: PUBLISHED
+createdAt: 2023-10-17T16:22:21.667Z
+updatedAt: 2023-11-03T17:17:12.530Z
+publishedAt: 2023-11-03T17:17:12.530Z
+firstPublishedAt: 2023-10-17T16:22:22.650Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-email-nao-e-preenchido-automaticamente-para-novos-compradores-apos-o-login
+locale: pt
+kiStatus: Fixed
+internalReference: 920634
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um novo comprador faz login e prossegue com o checkout, o e-mail não é preenchido automaticamente, exigindo que o cliente insira novamente o e-mail. Isso também acontece com o uso de APIs e o envio de cabeçalhos com os cookies do comprador.
+
+## Simulação
+
+
+
+- Faça login com um e-mail nunca usado antes na loja;
+- Adicionar produtos ao carrinho;
+- Vá para o checkout;
+- O e-mail não será preenchido e deverá ser digitado novamente
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md b/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md
new file mode 100644
index 000000000..dbc374bbc
--- /dev/null
+++ b/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md
@@ -0,0 +1,61 @@
+---
+title: 'O e-mail não é preenchido automaticamente para novos usuários no checkout-ui'
+id: 6XBghXwc93RBF53dCHr35y
+status: DRAFT
+createdAt: 2023-08-25T15:29:58.242Z
+updatedAt: 2023-08-25T16:47:25.505Z
+publishedAt: 
+firstPublishedAt: 
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-email-nao-e-preenchido-automaticamente-para-novos-usuarios-no-checkoutui
+locale: pt
+kiStatus: Backlog
+internalReference: 887949
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um novo usuário insere um novo e-mail na etapa de e-mail e prossegue para a próxima página, no componente de dados do cliente, o e-mail não é preenchido automaticamente.
+Isso ocorre porque não há nenhum usuário registrado com esse e-mail. Como resultado, o `orderForm` carregado também contém um campo de e-mail vazio, fazendo com que ele permaneça em branco e exigindo que o cliente insira novamente seu e-mail.
+
+## Simulação
+
+
+
+1. Navegue até a página de checkout onde os clientes inserem seus e-mails.
+2. Coloque um e-mail nunca usado antes na loja.
+3. Vá para o componente de perfil do cliente.
+4. A caixa de e-mail estará vazia e você terá que digitá-la novamente.
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
+digitá-la novamente.
+
+##
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md b/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
new file mode 100644
index 000000000..6b6843704
--- /dev/null
+++ b/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
@@ -0,0 +1,42 @@
+---
+title: 'Não é permitido que e-mails com funções de vendas se façam passar por outros usando o recurso Organizações B2B'
+id: 4HKDawkaTmzWcTZyrIhhuj
+status: PUBLISHED
+createdAt: 2023-09-29T18:15:08.398Z
+updatedAt: 2023-10-09T14:21:48.982Z
+publishedAt: 2023-10-09T14:21:48.982Z
+firstPublishedAt: 2023-09-29T18:15:09.110Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: nao-e-permitido-que-emails-com-funcoes-de-vendas-se-facam-passar-por-outros-usando-o-recurso-organizacoes-b2b
+locale: pt
+kiStatus: Fixed
+internalReference: 910328
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se os e-mails tiverem alguma função de vendas associada, eles não terão permissão para se passar por outra pessoa usando o recurso Organizações B2B.
+
+## Simulação
+
+
+
+- Crie um usuário para uma organização e atribua qualquer função de vendas;
+- Acesse o site e tente se passar por qualquer outro usuário
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/encoding-error-in-apple-mail-app.md b/docs/known-issues/pt/encoding-error-in-apple-mail-app.md
index a35041a17..5c32b2596 100644
--- a/docs/known-issues/pt/encoding-error-in-apple-mail-app.md
+++ b/docs/known-issues/pt/encoding-error-in-apple-mail-app.md
@@ -29,7 +29,7 @@ Montar um trigger de envio de e-mail que possua caracter especial no "Assunto" d
 
 Resultado:
 
-![png](https://images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
+![png](//images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md b/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
new file mode 100644
index 000000000..90a89107f
--- /dev/null
+++ b/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
@@ -0,0 +1,45 @@
+---
+title: 'Problemas de codificação para caracteres específicos levam a uma pesquisa inesperada de produtos'
+id: O0dM1H8ofJU0ahJRa6217
+status: PUBLISHED
+createdAt: 2024-04-24T22:09:33.395Z
+updatedAt: 2024-04-24T22:09:34.217Z
+publishedAt: 2024-04-24T22:09:34.217Z
+firstPublishedAt: 2024-04-24T22:09:34.217Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: problemas-de-codificacao-para-caracteres-especificos-levam-a-uma-pesquisa-inesperada-de-produtos
+locale: pt
+kiStatus: Backlog
+internalReference: 1022550
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Um problema de codificação pode afetar as pesquisas com caracteres especiais quando eles são indicados por meio do parâmetro "query", levando a resultados de pesquisa incorretos.
+
+As pesquisas sem nenhum filtro podem usar o primeiro caminho do URL para indicar o termo de pesquisa, mas as pesquisas com filtros dependem do parâmetro "query" do URL.
+
+## Simulação
+
+
+Esse problema ocorre especialmente com o símbolo "+".
+
+O termo de pesquisa "A+" funciona corretamente quando indicado pelo caminho do URL, mas se comportará como "A" quando indicado pelo parâmetro "query"
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index 4e52b90b7..6fcb74e39 100644
--- a/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -3,8 +3,8 @@ title: 'Erro "Categoria XXX não encontrada no mapeamento de nós de navegação
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
-updatedAt: 2022-11-25T21:56:57.092Z
-publishedAt: 2022-11-25T21:56:57.092Z
+updatedAt: 2024-02-16T20:29:13.856Z
+publishedAt: 2024-02-16T20:29:13.856Z
 firstPublishedAt: 2022-03-10T17:58:43.266Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: erro-categoria-xxx-nao-encontrada-no-mapeamento-de-nos-de-navegacao-para-a-especificacao-do-departamento-da-sku-escolha-uma-categoria-global-mais-especifica-persistente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 417639
 ---
 
diff --git a/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md b/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
new file mode 100644
index 000000000..8836c8efa
--- /dev/null
+++ b/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
@@ -0,0 +1,50 @@
+---
+title: 'Erro ao aprovar skus que foram rejeitados ou revisados pelo Offer Quality'
+id: 7fRMTxq7CFRkyZeK08AGIg
+status: PUBLISHED
+createdAt: 2023-11-23T13:46:30.453Z
+updatedAt: 2024-03-25T12:22:46.687Z
+publishedAt: 2024-03-25T12:22:46.687Z
+firstPublishedAt: 2023-11-23T13:46:31.370Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: erro-ao-aprovar-skus-que-foram-rejeitados-ou-revisados-pelo-offer-quality
+locale: pt
+kiStatus: Fixed
+internalReference: 940998
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um sku é reprovado nas regras de Qualidade da Oferta criadas pelo Marketplace, ele vai diretamente para a "Guia Revisão" ou "Guia Rejeitado" dos Skus Recebidos.
+
+No entanto, ao tentar aprovar o sku, uma mensagem de erro é retornada: "Desculpe, algo deu errado no Catálogo. Tente novamente ou entre em contato com a VTEX se o problema persistir."
+
+Isso acontece porque o módulo Matcher não conseguiu preencher as informações do produto e do sku depois de enviar o sku para essas guias (você pode verificar isso usando as APIs):
+ ![](https://vtexhelp.zendesk.com/attachments/token/0Dti3ak7twOpuVzvzntmPCGit/?name=image.png)
+
+## Simulação
+
+
+
+1. Crie uma regra opcional ou obrigatória sobre a qualidade da oferta;
+2. Aguarde até que um sku falhe na regra e vá para a guia Review/Rejected (Revisar/Rejeitado);
+3. Tente aprovar o sku e receba uma mensagem de erro;
+4. Verificar via API se o objeto de correspondência está preenchido como na imagem acima
+
+## Workaround
+
+
+Aprovar o sku via API passando manualmente as informações corretas do produto e do sku.
+
+
+
+
+
diff --git a/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md b/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md
new file mode 100644
index 000000000..e6d9c8b35
--- /dev/null
+++ b/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md
@@ -0,0 +1,44 @@
+---
+title: 'Erro ao cancelar faturas de crédito do cliente'
+id: 75nZNOHGYGBlAoTOjG6gs
+status: PUBLISHED
+createdAt: 2023-10-26T21:09:54.255Z
+updatedAt: 2024-05-29T17:25:32.948Z
+publishedAt: 2024-05-29T17:25:32.948Z
+firstPublishedAt: 2023-10-26T21:09:54.992Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-ao-cancelar-faturas-de-credito-do-cliente
+locale: pt
+kiStatus: Backlog
+internalReference: 926563
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Em alguns casos, as faturas não podem ser canceladas; ao executar a API DELETE, recebemos um erro 500 com a resposta abaixo:
+
+`"message": "Ocorreu um erro."`
+
+## Simulação
+
+
+Não foi possível replicar esse erro.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index 0564c3f78..9c50978e8 100644
--- a/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -3,8 +3,8 @@ title: 'Erro "não pode criar critérios de busca! erro: o filtro já existe: "b
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
-updatedAt: 2022-11-25T22:11:53.363Z
-publishedAt: 2022-11-25T22:11:53.363Z
+updatedAt: 2024-02-16T20:23:47.779Z
+publishedAt: 2024-02-16T20:23:47.779Z
 firstPublishedAt: 2022-09-22T15:53:16.277Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: erro-nao-pode-criar-criterios-de-busca-erro-o-filtro-ja-existe-brandid-ao-criar-uma-promocao-excluindo-mais-de-1-marca
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 663698
 ---
 
diff --git a/docs/known-issues/pt/error-closing-customer-credit-account.md b/docs/known-issues/pt/error-closing-customer-credit-account.md
new file mode 100644
index 000000000..c24d26a90
--- /dev/null
+++ b/docs/known-issues/pt/error-closing-customer-credit-account.md
@@ -0,0 +1,42 @@
+---
+title: 'Erro ao fechar a conta de crédito do cliente'
+id: zp8Bd8sIijJVNHws4nrkh
+status: PUBLISHED
+createdAt: 2023-09-20T21:38:28.253Z
+updatedAt: 2023-09-20T21:38:28.888Z
+publishedAt: 2023-09-20T21:38:28.888Z
+firstPublishedAt: 2023-09-20T21:38:28.888Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-ao-fechar-a-conta-de-credito-do-cliente
+locale: pt
+kiStatus: Backlog
+internalReference: 904432
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando as contas principais e secundárias têm o aplicativo Customer Credit instalado, a criação de uma creditAccount ocorre em todas elas. Nesse cenário, há casos em que o fechamento da creditAccount não funciona, e o erro a seguir é exibido:
+
+`Erro ao fechar a conta.`
+
+## Simulação
+
+
+Não foi possível replicar ou identificar a causa desse problema; em algumas contas, ele não ocorre.
+
+## Workaround
+
+
+NA, o que pode ser feito é alterar o limite de crédito para zero para que o método de pagamento não funcione para o e-mail registrado.
+
+
+
+
diff --git a/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md b/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md
new file mode 100644
index 000000000..b516e9459
--- /dev/null
+++ b/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md
@@ -0,0 +1,47 @@
+---
+title: 'Erro ao exportar entidade com muitos documentos'
+id: 1uLEk6e9z3011GaoJ4DNU0
+status: PUBLISHED
+createdAt: 2023-07-07T15:59:46.214Z
+updatedAt: 2023-07-07T15:59:46.899Z
+publishedAt: 2023-07-07T15:59:46.899Z
+firstPublishedAt: 2023-07-07T15:59:46.899Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: erro-ao-exportar-entidade-com-muitos-documentos
+locale: pt
+kiStatus: Backlog
+internalReference: 857894
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A exportação de um grande número de documentos de uma entidade resulta em processamento excessivo, causando erros na fila do processo e impedindo a exportação da lista de documentos.
+
+## Simulação
+
+
+
+1. Acesse a plataforma de CRM de dados mestres e navegue até o formulário da entidade desejada.
+2. Localize o botão "Export XLS" na interface e clique nele.
+3. Localize e clique no botão "Export XLS".
+4. Inicie o processo de exportação confirmando a seleção e iniciando a exportação.
+5. Para monitorar o andamento da exportação, navegue até a guia Applications (Aplicativos) na plataforma.
+6. Procure o botão "Exports" (Exportações) e clique nele para ver a lista em andamento.
+7. Observe o status da exportação e verifique se há erros ou problemas encontrados durante o processo de exportação.
+
+
+
+
+## Workaround
+
+
+Uma solução alternativa para esse problema é utilizar a API de rolagem.
+
diff --git a/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md b/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md
index 39b315b90..f84f87b25 100644
--- a/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md
+++ b/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md
@@ -1,10 +1,10 @@
 ---
 title: 'Erro ao exportar grande quantidade de Giftcards'
 id: 2EZ9XmZwYmcWdRxKbTNEBJ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-03-27T12:37:51.512Z
-updatedAt: 2022-11-25T22:09:09.150Z
-publishedAt: 2022-11-25T22:09:09.150Z
+updatedAt: 2023-07-03T17:14:32.962Z
+publishedAt: 
 firstPublishedAt: 2022-03-27T12:37:52.279Z
 contentType: knownIssue
 productTeam: Payments
@@ -39,3 +39,15 @@ N/A
 
 N/A
 
+ulação
+
+
+Tente fazer o processo de exportação com mais de 50000 giftcards.
+
+
+
+## Workaround
+
+
+Exporte em quantidades menores ou em períodos de tempo menores.
+
diff --git a/docs/known-issues/pt/error-exporting-prices-with-metadata.md b/docs/known-issues/pt/error-exporting-prices-with-metadata.md
new file mode 100644
index 000000000..64ae1b6af
--- /dev/null
+++ b/docs/known-issues/pt/error-exporting-prices-with-metadata.md
@@ -0,0 +1,46 @@
+---
+title: 'Erro ao exportar preços com metadados'
+id: 7nYPmatUXq57ZUsKHvfYJo
+status: PUBLISHED
+createdAt: 2023-07-12T11:49:06.370Z
+updatedAt: 2023-07-12T11:49:07.185Z
+publishedAt: 2023-07-12T11:49:07.185Z
+firstPublishedAt: 2023-07-12T11:49:07.185Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: erro-ao-exportar-precos-com-metadados
+locale: pt
+kiStatus: Backlog
+internalReference: 860290
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Às vezes, ao tentar exportar os preços com a opção de metadados ativada e sem usar filtros, pode ocorrer um erro. Ao verificar a mensagem no devTools, aparecerá algo semelhante a "Polly broken circuit on service...".
+
+Esse erro ocorre devido à limitação no módulo de catálogo ao tentar recuperar os metadados de muitos skus.
+
+## Simulação
+
+
+
+1. Exportar os preços com metadados sem usar nenhum filtro;
+2. Às vezes, uma mensagem de erro será exibida;
+3. Verifique no inspect devtools se a mensagem é semelhante à mensagem acima
+
+## Workaround
+
+
+Use os filtros para reduzir a quantidade de skus na planilha e o módulo de catálogo retornará os dados sem problemas.
+
+
+
+
+
diff --git a/docs/known-issues/pt/error-in-checkout-error-message.md b/docs/known-issues/pt/error-in-checkout-error-message.md
index c2cb1b182..4fe8f6c15 100644
--- a/docs/known-issues/pt/error-in-checkout-error-message.md
+++ b/docs/known-issues/pt/error-in-checkout-error-message.md
@@ -3,8 +3,8 @@ title: 'Erro na mensagem de erro de checkout'
 id: 7jCEQoDRPvNwYCJmAt78im
 status: PUBLISHED
 createdAt: 2022-03-25T14:46:49.548Z
-updatedAt: 2022-11-25T22:07:18.470Z
-publishedAt: 2022-11-25T22:07:18.470Z
+updatedAt: 2024-02-16T20:27:24.748Z
+publishedAt: 2024-02-16T20:27:24.748Z
 firstPublishedAt: 2022-03-25T15:30:16.292Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: erro-na-mensagem-de-erro-de-checkout
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 409895
 ---
 
diff --git a/docs/known-issues/pt/error-in-custom-payments-creation.md b/docs/known-issues/pt/error-in-custom-payments-creation.md
new file mode 100644
index 000000000..67d0d55ce
--- /dev/null
+++ b/docs/known-issues/pt/error-in-custom-payments-creation.md
@@ -0,0 +1,43 @@
+---
+title: 'Erro na criação de pagamentos personalizados'
+id: 28jwG2jyT5FkSTbb85KlLX
+status: PUBLISHED
+createdAt: 2024-03-06T14:19:49.398Z
+updatedAt: 2024-07-01T18:49:29.959Z
+publishedAt: 2024-07-01T18:49:29.959Z
+firstPublishedAt: 2024-03-06T14:19:50.201Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-na-criacao-de-pagamentos-personalizados
+locale: pt
+kiStatus: No Fix
+internalReference: 995110
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os comerciantes podem enfrentar um erro ao criar um pagamento personalizado. Depois de preencher tudo e clicar em salvar, a mensagem "O pagamento personalizado foi configurado com sucesso" aparece, mas a criação realmente falhou (não aparece na interface do usuário).
+
+## Simulação
+
+
+Vá para a guia Custom Payments (Pagamentos personalizados) e configure qualquer regra de pagamento, você poderá ter o problema acima.
+
+
+
+## Workaround
+
+
+A única solução alternativa seria tentar novamente a criação até que ela apareça na interface do usuário.
+
+
+
+
+
diff --git a/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
new file mode 100644
index 000000000..245a75039
--- /dev/null
+++ b/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -0,0 +1,46 @@
+---
+title: 'Erro nas operações de reembolso e captura com divisão de pagamento - "O valor nos destinatários * é diferente do valor da operação *".'
+id: 3Wo9ltN7Ju0ZqVLAQZcd7m
+status: PUBLISHED
+createdAt: 2023-08-23T13:57:20.424Z
+updatedAt: 2024-02-02T20:52:54.054Z
+publishedAt: 2024-02-02T20:52:54.054Z
+firstPublishedAt: 2023-08-23T13:57:21.389Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-nas-operacoes-de-reembolso-e-captura-com-divisao-de-pagamento-o-valor-nos-destinatarios-e-diferente-do-valor-da-operacao
+locale: pt
+kiStatus: Backlog
+internalReference: 698005
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Devido a problemas de arredondamento ao recalcular os destinatários de uma transação com Payout Split, seja na captura ou no reembolso, recebemos a seguinte exceção do gateway, pois a soma do valor do destinatário é diferente do valor da transação.
+
+
+    Vtex.Practices.ExceptionHandling.ValidationException: O valor nos destinatários (xx.989999999999999999999999988) é diferente do valor da operação (xx.99). at Vtex.PaymentGateway.PaymentSplit.RecipientsBuilder.ValidateRecipientsValue(List`1 recipients, Decimal value)...
+
+
+## Simulação
+
+
+Não é possível simular
+
+
+
+## Workaround
+
+
+Não há solução alternativa
+
+
+
+
diff --git a/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
new file mode 100644
index 000000000..b66f05b6a
--- /dev/null
+++ b/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -0,0 +1,46 @@
+---
+title: 'Erro no reembolso - "Value cannot be null. Nome do parâmetro: value"'
+id: 6TZFYB9zb02oMoN5IJMxR3
+status: PUBLISHED
+createdAt: 2024-06-13T18:49:16.797Z
+updatedAt: 2024-06-13T18:49:17.823Z
+publishedAt: 2024-06-13T18:49:17.823Z
+firstPublishedAt: 2024-06-13T18:49:17.823Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-no-reembolso-value-cannot-be-null-nome-do-parametro-value
+locale: pt
+kiStatus: Backlog
+internalReference: 1049494
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar reembolsar uma transação, pode ocorrer um erro 500 com a mensagem:
+
+`Value cannot be null. Nome do parâmetro: value`
+
+ Nesse cenário, as tentativas de reembolso são visíveis nos registros de transações sem resposta.
+
+## Simulação
+
+
+Não foi possível replicar.
+
+
+
+## Workaround
+
+
+NA, o comerciante precisará solicitar o reembolso diretamente com o adquirente.
+
+
+
+
diff --git a/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md b/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
new file mode 100644
index 000000000..7a26b67f5
--- /dev/null
+++ b/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
@@ -0,0 +1,46 @@
+---
+title: 'Erro no processo de cancelamento. O ERedeRest e o E-Rede V2 só permitem o cancelamento quando o returnCode é 359'
+id: 5lNLTmKp1xRfewx9OyhcNk
+status: PUBLISHED
+createdAt: 2023-01-26T18:29:35.310Z
+updatedAt: 2023-12-01T16:41:01.605Z
+publishedAt: 2023-12-01T16:41:01.605Z
+firstPublishedAt: 2023-01-26T18:29:36.467Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-no-processo-de-cancelamento-o-erederest-e-o-erede-v2-so-permitem-o-cancelamento-quando-o-returncode-e-359
+locale: pt
+kiStatus: Backlog
+internalReference: 740084
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os conectores legados, ERedeRest e E-Rede V2, iniciam os cancelamentos enviando uma solicitação ao provedor e esperam um "returnCode": "359" indicando um cancelamento bem-sucedido. Qualquer outro código é interpretado pelo nosso gateway como um status indefinido, fazendo com que a transação fique presa em um estado de cancelamento. Mesmo que, em alguns casos, a solicitação de reembolso/cancelamento seja bem-sucedida. Isso levou a repetidas tentativas de cancelamento, mesmo quando o cancelamento já havia sido processado pelo provedor.
+
+## Simulação
+
+
+Não pode ser simulado, pois dependemos da resposta do provedor.
+
+
+
+## Workaround
+
+
+Se o pagamento no lado do provedor já tiver sido cancelado
+
+    {"returnCode": "355", "returnMessage": "Transação já cancelada."}
+
+A equipe de suporte ao produto tem a opção de utilizar uma API interna, "`force-cancel-status`", para atualizar o status do pagamento e da transação para "cancelado".
+
+
+
+
diff --git a/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md b/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
new file mode 100644
index 000000000..713136060
--- /dev/null
+++ b/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
@@ -0,0 +1,57 @@
+---
+title: 'Erro na visualização da interface do usuário de pedidos após a solicitação da fatura via aplicativo'
+id: 1yrb25L1Skj3sRRWyiFDSA
+status: PUBLISHED
+createdAt: 2024-07-24T14:24:29.799Z
+updatedAt: 2024-07-24T14:24:30.583Z
+publishedAt: 2024-07-24T14:24:30.583Z
+firstPublishedAt: 2024-07-24T14:24:30.583Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: erro-na-visualizacao-da-interface-do-usuario-de-pedidos-apos-a-solicitacao-da-fatura-via-aplicativo
+locale: pt
+kiStatus: Backlog
+internalReference: 1070299
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando executamos uma "alteração V2" removendo ou adicionando um item a um pedido, criamos uma alteração na lista de itens do pedido, o que pode aumentar ou diminuir o número de índices na lista de itens no json. Essa alteração, por sua vez, pode não ser consumida por todos os aplicativos ou bancos de dados envolvidos no processamento do pedido, como o aplicativo notificador de faturas;
+
+Como resultado, ao solicitar a fatura por meio do aplicativo notificador de faturas antes de ter realizado uma ação para remover ou adicionar um item, o usuário acaba causando um cenário de interrupção na interface do usuário, pois o "aplicativo notificador de faturas" começa a retornar um erro por ter mais ou menos itens do que o esperado pela interface do usuário, resultando em um erro de "referência nula" que impede que o pedido seja exibido na interface do usuário;
+
+## Simulação
+
+
+
+**NOTA**: Para simular esse cenário, você deve ter configurado o aplicativo `invoice notifier` e também estar usando o fluxo `Change V2`;
+
+
+- Em um pedido com mais de um item, vá para o status de processamento;
+
+
+- Na interface do usuário, clique na opção "Request invoice" (Notificar seu ERP).
+
+
+- Antes que a fatura seja devolvida pelo ERP, faça uma alteração no pedido, removendo ou adicionando qualquer item ao pedido;
+
+
+- Aguarde até que o ERP envie a fatura para o sistema de Pedidos e, em seguida, acesse o pedido novamente na interface do usuário de Pedidos; nesse momento, a interface do usuário retornará uma mensagem de erro e o pedido não poderá ser exibido
+
+## Workaround
+
+
+Faça a solicitação de fatura por meio do notificador de fatura somente após realizar a alteração dos itens do pedido.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md b/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
new file mode 100644
index 000000000..abf058401
--- /dev/null
+++ b/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
@@ -0,0 +1,47 @@
+---
+title: 'Erro (LeituraDeDadosDoAdministrador) ao tentar acessar as páginas do catálogo no admin'
+id: 40EruMGkO9DVEwb7RZ5nxF
+status: PUBLISHED
+createdAt: 2024-06-25T18:30:24.815Z
+updatedAt: 2024-06-25T18:30:25.929Z
+publishedAt: 2024-06-25T18:30:25.929Z
+firstPublishedAt: 2024-06-25T18:30:25.929Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: erro-leituradedadosdoadministrador-ao-tentar-acessar-as-paginas-do-catalogo-no-admin
+locale: pt
+kiStatus: Backlog
+internalReference: 1055578
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns usuários, mesmo com a função correta, recebem um erro "O usuário xx não tem acesso à página solicitada (LeituraDeDadosDoAdministrador)" ao acessar páginas de catálogo no admin.
+
+Isso geralmente acontece com novos usuários criados em contas PII.
+
+## Simulação
+
+
+
+1. Usando uma conta PII, crie um novo usuário e dê a ele o acesso correto aos módulos do catálogo.
+2. Verifique se o usuário pode realmente acessar essas páginas.
+
+
+
+## Workaround
+
+
+Crie um tíquete para a VTEX.
+
+
+
+
+
diff --git a/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md b/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
index 0da496ae8..fb7cdb130 100644
--- a/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
+++ b/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
@@ -3,8 +3,8 @@ title: 'Mensagem de erro na gestão de ofertas não é atualizada depois que o s
 id: 5tMKDMsFTZlXQrkVM4WeJD
 status: PUBLISHED
 createdAt: 2022-12-08T14:02:22.948Z
-updatedAt: 2022-12-08T14:03:27.764Z
-publishedAt: 2022-12-08T14:03:27.764Z
+updatedAt: 2024-02-16T20:24:16.785Z
+publishedAt: 2024-02-16T20:24:16.785Z
 firstPublishedAt: 2022-12-08T14:02:23.384Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: mensagem-de-erro-na-gestao-de-ofertas-nao-e-atualizada-depois-que-o-sku-e-vinculado-a-integracoes-vtexvtex
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 712956
 ---
 
diff --git a/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
new file mode 100644
index 000000000..3dbf9c6f4
--- /dev/null
+++ b/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -0,0 +1,44 @@
+---
+title: 'Ocorre um erro ao tentar realizar uma pesquisa usando o campo "Todos" no VTEX CRM'
+id: 1OKMTJuUZx6mnDmYW3MBjP
+status: PUBLISHED
+createdAt: 2023-10-25T18:46:48.120Z
+updatedAt: 2023-10-25T18:46:48.731Z
+publishedAt: 2023-10-25T18:46:48.731Z
+firstPublishedAt: 2023-10-25T18:46:48.731Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: ocorre-um-erro-ao-tentar-realizar-uma-pesquisa-usando-o-campo-todos-no-vtex-crm
+locale: pt
+kiStatus: Backlog
+internalReference: 925679
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Esse caso ocorre com entidades que contêm um grande número de campos e milhões de registros em uma entidade. O problema ocorre porque o mecanismo de busca usa o campo "All", que envia solicitações individuais para cada campo pesquisável da entidade e multiplica a carga de solicitações para cada documento.
+
+## Simulação
+
+
+
+1. Acesse `https://.vtexcrm.com.br/`.
+2. Navegue até uma visualização que represente uma entidade com milhões de registros.
+3. Inicie uma pesquisa usando o campo "All".
+ ![](https://vtexhelp.zendesk.com/attachments/token/NGWvp5vsTzd31GA07N6vp0Wev/?name=Captura+de+Tela+2023-10-25+a%CC%80s+15.42.35.png)
+4. Observe a resposta do sistema e verifique se ele retorna um erro ou apresenta problemas significativos de desempenho.
+ ![](https://vtexhelp.zendesk.com/attachments/token/aFWGBmUtDtl9ppgmMNOkDX8Fu/?name=Captura+de+Tela+2023-10-25+a%CC%80s+15.40.50.png)
+5. Repita a pesquisa com um campo pesquisável específico para confirmar se o problema está relacionado ao mecanismo de pesquisa do campo "Todos"
+
+## Workaround
+
+
+Pesquise com um campo pesquisável específico.
+
diff --git a/docs/known-issues/pt/error-on-duplicate-payment-method.md b/docs/known-issues/pt/error-on-duplicate-payment-method.md
new file mode 100644
index 000000000..884f8462b
--- /dev/null
+++ b/docs/known-issues/pt/error-on-duplicate-payment-method.md
@@ -0,0 +1,50 @@
+---
+title: 'Erro no método de pagamento duplicado'
+id: 1wdiEae6sehlnTDnanWT7n
+status: PUBLISHED
+createdAt: 2023-11-02T12:23:14.027Z
+updatedAt: 2023-11-02T12:23:15.109Z
+publishedAt: 2023-11-02T12:23:15.109Z
+firstPublishedAt: 2023-11-02T12:23:15.109Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-no-metodo-de-pagamento-duplicado
+locale: pt
+kiStatus: Backlog
+internalReference: 929428
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao duplicar um método de pagamento que não possui parcelas, o operador recebe a seguinte mensagem na tela: "O sistema de pagamento atual não permite opções de parcelamento". Isso acontece porque, quando o corpo da solicitação de criação na nova regra é criado, alguns campos são inseridos por padrão, incluindo installmentOptions, mas esse campo não existe para pagamentos à vista, como débito e boleto.
+
+## Simulação
+
+
+
+1. Vá para a tela de condições de pagamento
+2. Selecione um método de pagamento que não tenha parcelas.
+3. Clique no botão para duplicar a regra.
+4. A seguinte mensagem de erro será exibida na tela: "O sistema de pagamento atual não permite opções de parcelamento"
+
+
+
+## Workaround
+
+
+Temos duas maneiras de contornar esse problema:
+
+1. Crie outra com as mesmas configurações da que você deseja duplicar;
+2. Criar a regra via API, `https://.myvtex.com/api/payments/pvt/rules/`, removendo o campo installmentOptions do corpo.
+
+
+
+
+
diff --git a/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
new file mode 100644
index 000000000..4f2ff0bc0
--- /dev/null
+++ b/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -0,0 +1,45 @@
+---
+title: 'Erro "Algo deu errado. Tente novamente." ao adicionar imagens pelo Site Editor'
+id: r3QVP1kp8HApP83bOi6t9
+status: PUBLISHED
+createdAt: 2023-11-07T22:33:02.296Z
+updatedAt: 2023-11-07T22:34:52.005Z
+publishedAt: 2023-11-07T22:34:52.005Z
+firstPublishedAt: 2023-11-07T22:33:03.046Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: erro-algo-deu-errado-tente-novamente-ao-adicionar-imagens-pelo-site-editor
+locale: pt
+kiStatus: Backlog
+internalReference: 932126
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao adicionar imagens por meio do Site Editor, a mensagem "`Algo deu errado. Tente novamente.`" pode ocorrer ocasionalmente.
+Isso se deve ao número de imagens por bloco. No momento, não temos um número exato de imagens que cause esse problema, mas notamos esse comportamento acima de 20 imagens no mesmo bloco.
+
+## Simulação
+
+
+
+- Acesse o CMS Site Editor (por exemplo, https://my-account-here.myvtex.com/admin/cms/site-editor);
+- Selecione o bloco com as novas imagens a serem adicionadas;
+- Quando a adição for salva, a mensagem "`Algo deu errado. Please try again.`" será exibida no canto inferior direito:
+ ![](https://vtexhelp.zendesk.com/attachments/token/97C4wewa6iz3f7bsmHtdnXu1H/?name=image.png
+
+## Workaround
+
+
+Você pode adicionar as imagens diretamente ao tema ou dividi-las em blocos com o layout flexível (ref. https://developers.vtex.com/docs/apps/vtex.flex-layout).
+
+
+
+
diff --git a/docs/known-issues/pt/error-sww-on-product-pdp.md b/docs/known-issues/pt/error-sww-on-product-pdp.md
index 6b123fb23..e1f254573 100644
--- a/docs/known-issues/pt/error-sww-on-product-pdp.md
+++ b/docs/known-issues/pt/error-sww-on-product-pdp.md
@@ -3,8 +3,8 @@ title: 'Erro SWW no produto PDP'
 id: 3DhuWocQwqiWxuAffdwYkg
 status: PUBLISHED
 createdAt: 2023-01-23T12:38:30.711Z
-updatedAt: 2023-01-23T12:38:31.382Z
-publishedAt: 2023-01-23T12:38:31.382Z
+updatedAt: 2023-09-19T19:15:13.868Z
+publishedAt: 2023-09-19T19:15:13.868Z
 firstPublishedAt: 2023-01-23T12:38:31.382Z
 contentType: knownIssue
 productTeam: Catalog
@@ -23,26 +23,14 @@ internalReference: 738108
 </div>
 
 
-Em algumas ocasiões, ao abrir o produto PDP através da página de administração (ou do domínio final), aparece na tela um erro Something Went Wrong.
-
-
-##
+Em algumas ocasiões, ao abrir o PDP do produto por meio da página de administração (ou do domínio final), um erro Something Went Wrong (Algo deu errado) é exibido na tela.
+Esse comportamento pode ocorrer devido a movimentos de categorias anteriores na árvore de categorias, causando uma validação incorreta das especificações do produto/sku no sistema de catálogo.
 
 ## Simulação
 
 
-Este comportamento pode acontecer devido a movimentos anteriores da categoria na árvore de categorias, causando uma validação errada das especificações do produto/sku no sistema de catálogo.
-
-A mensagem de erro real por trás do erro SWW (que pode ser verificado através de logs internos) é "Nome da variação do produto não encontrado".
-
-
-##
 
 ## Workaround
 
 
-A fim de corrigir este comportamento, a especificação que causa o erro não deve ter valor no produto.
-
-
-
 
diff --git a/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md b/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
index fa78c64d1..c0f892d47 100644
--- a/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
+++ b/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
@@ -3,8 +3,8 @@ title: 'Erro acionado por TOKEN substituído no conector do PayPal legado para s
 id: 5GrnhD8fwte7qu50Az8r3Y
 status: PUBLISHED
 createdAt: 2023-06-13T22:35:16.397Z
-updatedAt: 2023-06-13T22:38:27.909Z
-publishedAt: 2023-06-13T22:38:27.909Z
+updatedAt: 2024-07-01T18:47:54.680Z
+publishedAt: 2024-07-01T18:47:54.680Z
 firstPublishedAt: 2023-06-13T22:35:16.955Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: erro-acionado-por-token-substituido-no-conector-do-paypal-legado-para-status-de-pagamento-pendente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 308214
 ---
 
diff --git a/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md b/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md
new file mode 100644
index 000000000..ca5019ef7
--- /dev/null
+++ b/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md
@@ -0,0 +1,41 @@
+---
+title: 'Erro ao alterar um índice se os campos forem idênticos.'
+id: Ckic7QH3kKyW3IA92A3Cm
+status: PUBLISHED
+createdAt: 2023-07-03T18:48:49.070Z
+updatedAt: 2023-07-03T18:48:49.971Z
+publishedAt: 2023-07-03T18:48:49.971Z
+firstPublishedAt: 2023-07-03T18:48:49.971Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: erro-ao-alterar-um-indice-se-os-campos-forem-identicos
+locale: pt
+kiStatus: Backlog
+internalReference: 854634
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Uma atualização de um índice de esquema pode resultar em um erro 500 Internal Server quando não há alterações a serem feitas, o que significa que os valores de campo são idênticos aos atuais.
+A execução de uma solicitação GET na API para verificar os índices revela que nenhuma atualização é necessária, pois o índice é idêntico ao corpo fornecido na solicitação PUT.
+
+## Simulação
+
+
+
+1. Envie uma solicitação PUT para atualizar um índice de esquema por meio da API, fornecendo a carga útil necessária no corpo da solicitação.
+2. Verifique a resposta da API e observe se ela retorna um **500 Internal Server Error**.
+3. Execute uma solicitação GET subsequente na API para recuperar os índices de esquema e compare-os com o corpo fornecido na solicitação PUT
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md b/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md
index e1dd320d6..1dd736339 100644
--- a/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md
+++ b/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md
@@ -3,8 +3,8 @@ title: 'Erro ao mudar o tipo de entrega quando o vendedor tem recorrência'
 id: 7JLnqVWHz94sQZKMOGUkKC
 status: PUBLISHED
 createdAt: 2022-06-14T14:07:38.881Z
-updatedAt: 2022-11-25T21:52:59.031Z
-publishedAt: 2022-11-25T21:52:59.031Z
+updatedAt: 2024-02-16T20:24:13.311Z
+publishedAt: 2024-02-16T20:24:13.311Z
 firstPublishedAt: 2022-06-14T14:07:39.358Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: erro-ao-mudar-o-tipo-de-entrega-quando-o-vendedor-tem-recorrencia
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 597915
 ---
 
diff --git a/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md b/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md
new file mode 100644
index 000000000..9223662b5
--- /dev/null
+++ b/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md
@@ -0,0 +1,58 @@
+---
+title: 'Erro ao publicar entidade de dados de armazenamento dinâmico'
+id: 1yNh5CV41vrrrU5F7Vj2tG
+status: PUBLISHED
+createdAt: 2023-10-04T16:33:03.051Z
+updatedAt: 2023-10-04T16:37:00.614Z
+publishedAt: 2023-10-04T16:37:00.614Z
+firstPublishedAt: 2023-10-04T16:33:03.847Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: erro-ao-publicar-entidade-de-dados-de-armazenamento-dinamico
+locale: pt
+kiStatus: Backlog
+internalReference: 666357
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o armazenamento cria ou atualiza uma entidade de dados e tenta publicá-la, pode ocorrer o seguinte erro:
+
+
+    Erro inesperado. Tente novamente ou entre em contato com o suporte ao cliente.
+
+
+## Simulação
+
+
+
+- Acesse o aplicativo Sistema de armazenamento dinâmico / Estrutura de dados (https://my-account-here.ds.vtexcrm.com.br);
+- Acesse a guia Data Entities (Entidades de dados):
+ ![](https://vtexhelp.zendesk.com/attachments/token/65UPKYKl3vuaeweF46K91bpI5/?name=image.png)
+
+- Clique no ícone do disco para publicar a entidade de dados que foi criada ou atualizada:
+ ![](https://vtexhelp.zendesk.com/attachments/token/C1nUZnpG8lmDWOL8wrXRBiGj0/?name=image.png)
+
+- Em seguida, a seguinte mensagem será exibida:
+ ![](https://vtexhelp.zendesk.com/attachments/token/DFKVanOk3noBMaN8aBd6CQssp/?name=image.png)
+
+    Erro inesperado. Tente novamente ou entre em contato com o suporte ao cliente.
+
+
+
+
+## Workaround
+
+
+Para esses cenários, uma solução alternativa é abrir um tíquete para a VTEX, para que possamos validar uma possível atualização do cluster dessa conta.
+
+
+
+
diff --git a/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
index 50a9b8c04..010cc365d 100644
--- a/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
@@ -29,7 +29,7 @@ A mensagem de autorização de erro pode mudar de `node` para `react` de acordo
 1. Instalar o VTEX CLI (ToolBelt)
 2. Navegar até o diretorio da app
 3. Executar o comando "vtex-link" no terminal
-4. ![image (8)](https://images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
+4. ![image (8)](//images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md b/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md
index 30eb53917..24a6fc296 100644
--- a/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md
+++ b/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md
@@ -3,8 +3,8 @@ title: 'Erro ao liquidar transação com 2 cartões - MercadoPagoV1'
 id: 1WFFLHywLePfl5v5IMhili
 status: PUBLISHED
 createdAt: 2022-03-03T21:30:42.237Z
-updatedAt: 2022-11-25T22:05:14.074Z
-publishedAt: 2022-11-25T22:05:14.074Z
+updatedAt: 2024-02-16T20:27:28.600Z
+publishedAt: 2024-02-16T20:27:28.600Z
 firstPublishedAt: 2022-03-03T21:30:42.610Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: erro-ao-liquidar-transacao-com-2-cartoes-mercadopagov1
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 395943
 ---
 
diff --git a/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md b/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md
new file mode 100644
index 000000000..9ace037bd
--- /dev/null
+++ b/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md
@@ -0,0 +1,44 @@
+---
+title: 'Erro ao tentar publicar ou vincular um aplicativo'
+id: 2WPukfSHWzzIUjIzMJaAEK
+status: PUBLISHED
+createdAt: 2024-06-27T15:39:00.583Z
+updatedAt: 2024-06-27T19:46:21.021Z
+publishedAt: 2024-06-27T19:46:21.021Z
+firstPublishedAt: 2024-06-27T15:39:01.543Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: erro-ao-tentar-publicar-ou-vincular-um-aplicativo
+locale: pt
+kiStatus: Backlog
+internalReference: 1056882
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Nossa equipe investigou que isso normalmente está associado ao desenvolvimento de um aplicativo de grande porte. Isso acontece porque o hub do construtor estourou sua memória devido a muitos arquivos no aplicativo. Atrasos na vinculação do aplicativo também podem estar associados a esse problema
+
+## Simulação
+
+
+Tente usar o `vtex link` em um aplicativo com um tamanho enorme ou com muitos arquivos. Você poderá receber os seguintes erros:
+
+    11:51:13.298 - error: Workerpool Worker terminado inesperadamente exitCode: `null` signalCode: `SIGABRT` workerpool.script: `/usr/local/data/service/src/node/utils/workers/worker.js` spawnArgs: `/usr/local/bin/node,/usr/local/data/service/src/node/utils/workers/worker.js` spawnfile: `/usr/local/bin/node` stdout: `null` stderr: `null` vtex.builder-hub@0.299.0 11:51:13.299 - error: Falha na compilação do aplicativo com a mensagem: Workerpool Worker terminado Unexpectedly exitCode: `null` signalCode: `SIGABRT` workerpool.script: `/usr/local/data/service/src/node/utils/workers/worker.js` spawnArgs: `/usr/local/bin/node,/usr/local/data/service/src/node/utils/workers/worker.js` spawnfile: `/usr/local/bin/node` stdout: `null` stderr: `null`
+
+    13:30:05.456 - Erro: O aplicativo terminou com o código de saída 15. Será reiniciado em 10s. service-node@6.38.3
+
+## Workaround
+
+
+Analise o tamanho do aplicativo e de seus arquivos. Se for necessário, tente dividir o aplicativo em aplicativos menores para reduzir o tamanho.
+
+
+
+
diff --git a/docs/known-issues/pt/event-inconsistency.md b/docs/known-issues/pt/event-inconsistency.md
index 67e591564..d4516a55c 100644
--- a/docs/known-issues/pt/event-inconsistency.md
+++ b/docs/known-issues/pt/event-inconsistency.md
@@ -1,36 +1,54 @@
 ---
-title: 'Event Inconsistency'
+title: 'Inconsistência de eventos'
 id: 2YnhehJXuJcsy3f3Rezn6X
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-06-20T23:00:31.430Z
-updatedAt: 2022-06-27T12:52:29.346Z
-publishedAt: 2022-06-27T12:52:28.556Z
+updatedAt: 2024-05-23T12:45:46.343Z
+publishedAt: 2024-05-23T12:45:46.343Z
 firstPublishedAt: 2022-06-20T23:00:31.899Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: event-inconsistency
+slug: inconsistencia-de-eventos
 locale: pt
-kiStatus: Scheduled
+kiStatus: Fixed
 internalReference: 267299
 ---
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
+
+
+Quando o usuário faz um pedido no checkout, um novo fluxo de pedidos é iniciado. A partir desse momento, o gateway da VTEX é consultado quando os seguintes status de pedido são identificados: "Payment pending" (Pagamento pendente) e "Verifying invoice" (Verificando fatura). No status "Payment Pending", espera-se que uma notificação de pagamento seja enviada ao módulo Orders. Durante esse período, podem ocorrer alguns problemas com o processamento de eventos. Embora não haja apenas uma causa raiz diretamente relacionada ao problema do evento de processamento, qualquer outro problema interno ou externo vinculado ao sistema de notificação pode fazer com que o fluxo de pedidos seja bloqueado no status "pagamento pendente".
+
+A fila de mensagens fornece um protocolo de comunicação assíncrono, no qual os eventos são colocados em uma fila para serem consumidos em um momento predeterminado no futuro. Assim, já mapeamos alguns cenários em que há inconsistência nesse fluxo para categorizá-los e resolvê-los um a um.
+
+
+- Perda de evento/não gerado;
+- Evento preso e não processado;
+- Erros de processamento que podem causar inconsistências no banco de dados.
+
+Este KI refere-se explicitamente aos cenários mencionados acima e não tem a intenção de esgotar todas as possibilidades de problemas de processamento de eventos que possam ocorrer. Novas causas-raiz ou problemas relacionados, como respostas ruins do provedor (o que acontece regularmente), podem levar a situações em que o pedido fica preso. Cada caso precisa ser investigado individualmente para determinar a causa raiz do problema.
+
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+
+Não há como simular esse comportamento.
+
+
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+Entre em contato com nossa equipe de suporte para reprocessar manualmente o evento.
+
+
+
+
 
diff --git a/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md b/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
index 5b6657278..ed04a7eeb 100644
--- a/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
+++ b/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
@@ -1,10 +1,10 @@
 ---
-title: 'ew UI não sugere o item correto a ser devolvido quando o pedido tem uma mudança'
+title: 'New UI não sugere o item correto a ser devolvido quando o pedido tem uma mudança'
 id: 7hjZaUZ1GNiGjMnSKe0pZu
 status: PUBLISHED
 createdAt: 2023-01-18T17:05:53.889Z
-updatedAt: 2023-01-18T17:05:54.590Z
-publishedAt: 2023-01-18T17:05:54.590Z
+updatedAt: 2024-05-28T18:33:17.977Z
+publishedAt: 2024-05-28T18:33:17.977Z
 firstPublishedAt: 2023-01-18T17:05:54.590Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/pt/exclude-products-from-collection-not-working.md b/docs/known-issues/pt/exclude-products-from-collection-not-working.md
new file mode 100644
index 000000000..cae662afa
--- /dev/null
+++ b/docs/known-issues/pt/exclude-products-from-collection-not-working.md
@@ -0,0 +1,46 @@
+---
+title: 'Excluir produtos da coleção que não estão funcionando.'
+id: 102Z3QRDo07OM6IPJCDlsY
+status: PUBLISHED
+createdAt: 2023-10-20T16:30:13.646Z
+updatedAt: 2023-10-20T16:30:14.840Z
+publishedAt: 2023-10-20T16:30:14.840Z
+firstPublishedAt: 2023-10-20T16:30:14.840Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: excluir-produtos-da-colecao-que-nao-estao-funcionando
+locale: pt
+kiStatus: Backlog
+internalReference: 923016
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A conta pode criar coleções usando a versão antiga e adicionar coleções e marcas inteiras.
+
+No entanto, ao tentar excluir alguns produtos dessas coleções ou marcas usando a subcoleção "exclusao", nada acontece. Apesar de não aparecerem mensagens de erro, os skus continuam na coleção.
+
+## Simulação
+
+
+
+1. Crie uma coleção e adicione uma categoria no subgrupo de coleção "Inclusão".
+2. Crie um subgrupo de coleção "exclusão" com pelo menos um produto (todos os skus) na parte de adição de skus.
+3. Verifique se o sku continua na coleção
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md b/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md
new file mode 100644
index 000000000..e88d13f99
--- /dev/null
+++ b/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md
@@ -0,0 +1,36 @@
+---
+title: 'Redirecionamentos temporários expirados não apontam de volta para a rota antiga'
+id: 1kI87EueEtHIyfZ4KmUJSF
+status: PUBLISHED
+createdAt: 2023-09-12T14:41:09.843Z
+updatedAt: 2023-09-12T14:41:11.758Z
+publishedAt: 2023-09-12T14:41:11.758Z
+firstPublishedAt: 2023-09-12T14:41:11.758Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: redirecionamentos-temporarios-expirados-nao-apontam-de-volta-para-a-rota-antiga
+locale: pt
+kiStatus: Backlog
+internalReference: 898062
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Quando uma rota de redirecionamento é criada, a rota interna é removida, mas, quando o redirecionamento expira, a rota não volta
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md b/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
new file mode 100644
index 000000000..8bd74dba9
--- /dev/null
+++ b/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
@@ -0,0 +1,42 @@
+---
+title: 'Interface de pesquisa explicada com sobreposição de textos longos entre diferentes áreas ou produtos'
+id: 5BMYpoif30DAOjPOVHMDfS
+status: PUBLISHED
+createdAt: 2023-09-21T00:25:00.402Z
+updatedAt: 2023-09-21T00:25:00.874Z
+publishedAt: 2023-09-21T00:25:00.874Z
+firstPublishedAt: 2023-09-21T00:25:00.874Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: interface-de-pesquisa-explicada-com-sobreposicao-de-textos-longos-entre-diferentes-areas-ou-produtos
+locale: pt
+kiStatus: Backlog
+internalReference: 904482
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A página de administração da pesquisa explicada tem problemas com as regras de comercialização e as áreas de campos pesquisáveis quando uma pesquisa ou um produto tem muitas informações, sobrepondo textos entre diferentes seções/produtos.
+
+## Simulação
+
+
+Registre um bom número de palavras em um campo que possa ser pesquisado.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md b/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
new file mode 100644
index 000000000..2f8a0a547
--- /dev/null
+++ b/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
@@ -0,0 +1,38 @@
+---
+title: 'A exportação de muitos produtos/SKUs leva muito tempo e, às vezes, a solicitação não pode ser concluída'
+id: 4MBgn0t3jm698ZkkcF1o5G
+status: PUBLISHED
+createdAt: 2022-01-21T14:33:34.881Z
+updatedAt: 2024-02-16T20:25:42.392Z
+publishedAt: 2024-02-16T20:25:42.392Z
+firstPublishedAt: 2024-01-23T15:58:51.944Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-exportacao-de-muitos-produtosskus-leva-muito-tempo-e-as-vezes-a-solicitacao-nao-pode-ser-concluida
+locale: pt
+kiStatus: No Fix
+internalReference: 284386
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A exportação de muitos produtos/SKUs leva muito tempo e, às vezes, a solicitação não pode ser concluída. Esse problema também afeta outras exportações de catálogos.
+
+## Simulação
+
+
+Tente exportar mais de 100 mil produtos.
+
+
+## Workaround
+
+
+Use o filtro para filtrar os produtos em grupos de menos de 10.000 produtos.
+
diff --git a/docs/known-issues/pt/export-redirects-not-working-as-intended.md b/docs/known-issues/pt/export-redirects-not-working-as-intended.md
index 86577ac04..8b37d6145 100644
--- a/docs/known-issues/pt/export-redirects-not-working-as-intended.md
+++ b/docs/known-issues/pt/export-redirects-not-working-as-intended.md
@@ -1,16 +1,16 @@
 ---
-title: 'Export Redireciona não funciona como pretendido'
+title: 'Os redirecionamentos de exportação não estão funcionando como esperado'
 id: 5WoiJDQCSMDCwCn1auNwC4
 status: PUBLISHED
 createdAt: 2022-04-05T12:53:18.824Z
-updatedAt: 2022-11-25T21:54:34.008Z
-publishedAt: 2022-11-25T21:54:34.008Z
+updatedAt: 2024-01-29T18:40:08.833Z
+publishedAt: 2024-01-29T18:40:08.833Z
 firstPublishedAt: 2022-04-05T12:53:19.875Z
 contentType: knownIssue
-productTeam: CMS
+productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
-tag: CMS
-slug: export-redireciona-nao-funciona-como-pretendido
+tag: Store Framework
+slug: os-redirecionamentos-de-exportacao-nao-estao-funcionando-como-esperado
 locale: pt
 kiStatus: Backlog
 internalReference: 537962
@@ -24,15 +24,25 @@ internalReference: 537962
 
 
 
-Quando você tenta exportar o redirecionamento, seja através do terminal ou através da página no CMS ele traz tamanhos diferentes de arquivo, com possíveis resultados diferentes dentro, este não é o comportamento esperado, uma vez que não há mudanças feitas nos redirecionamentos que poderiam explicar as diferenças.
-
+Quando você tenta exportar o redirecionamento, seja por meio do terminal ou da página no CMS, ele traz arquivos de tamanhos diferentes, com possíveis resultados diferentes dentro dele. Esse não é o comportamento esperado, pois não há alterações feitas nos redirecionamentos que possam explicar as diferenças.
 
 
 ## Simulação
 
 
 
+(Terminal) Siga as etapas na documentação: https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-managing-url-redirects
+
+Verifique os arquivos retornados e você poderá ver, em alguns casos, a diferença entre os dois arquivos extraídos.
+
+(IU do administrador) Vá para admin > CMS > Redirecionamentos, altere entre as páginas na paginação e clique em exportar para ver as diferenças nos arquivos que são retornados
+
 ## Workaround
 
 
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md b/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md
index 04a3d7a85..f91050152 100644
--- a/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md
+++ b/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md
@@ -3,13 +3,13 @@ title: 'Exportar o CSV no módulo de desempenho de vendas'
 id: 7qnlFfnImq7N6Nrz0xIT8L
 status: PUBLISHED
 createdAt: 2023-05-11T13:42:36.411Z
-updatedAt: 2023-05-11T13:42:37.027Z
-publishedAt: 2023-05-11T13:42:37.027Z
+updatedAt: 2023-09-13T20:08:40.788Z
+publishedAt: 2023-09-13T20:08:40.788Z
 firstPublishedAt: 2023-05-11T13:42:37.027Z
 contentType: knownIssue
-productTeam: Admin
+productTeam: Analytics
 author: 2mXZkbi0oi061KicTExNjo
-tag: Admin
+tag: Analytics
 slug: exportar-o-csv-no-modulo-de-desempenho-de-vendas
 locale: pt
 kiStatus: Backlog
diff --git a/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
new file mode 100644
index 000000000..5d90b229a
--- /dev/null
+++ b/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -0,0 +1,46 @@
+---
+title: 'A exportação de imagens de SKU para contas que começam com "h", "t" ou "p" recebe esse corte de caracteres nas linhas de "URL da imagem".'
+id: 1IZdnE8IGwkBlbcFhjLrzn
+status: PUBLISHED
+createdAt: 2023-10-13T15:20:49.703Z
+updatedAt: 2023-10-13T15:20:50.483Z
+publishedAt: 2023-10-13T15:20:50.483Z
+firstPublishedAt: 2023-10-13T15:20:50.483Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-exportacao-de-imagens-de-sku-para-contas-que-comecam-com-h-t-ou-p-recebe-esse-corte-de-caracteres-nas-linhas-de-url-da-imagem
+locale: pt
+kiStatus: Backlog
+internalReference: 919199
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O relatório de imagem SKU, /admin/Site/ProdutoImagemExportacao.aspx, para nomes de contas que começam com "h", "t" ou "p", como "testaccount", mostrará um caractere ausente na planilha de exportação para a linha imageURL.
+
+## Simulação
+
+
+1 - Para uma conta que começa com os caracteres iniciais mencionados, vá para /admin/Site/ProdutoImagemExportacao.aspx e exporte uma planilha para qualquer sku que tenha pelo menos uma imagem.
+2 - abra a planilha exportada e verifique a coluna "UrlImagem": ela estará sem o caractere inicial
+
+Por exemplo, se a conta tiver o nome "testaccount":
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/3VxPtxFSDjU1obEtgqkS16BXM/?name=image.png
+
+## Workaround
+
+
+Crie uma subconta que comece com outro caractere (por exemplo, "mytestaccount") e acesse a interface do usuário de exportação usando essa subconta. A exportação mostrará toda a cadeia de caracteres de URL sem nenhum corte incorreto.
+
+
+
+
+
diff --git a/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md b/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
new file mode 100644
index 000000000..a4b376efc
--- /dev/null
+++ b/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
@@ -0,0 +1,47 @@
+---
+title: '[Facebook] Hoje, o Facebook analisa o sellingPrice e o listPrice para atualizar o preço no catálogo do Facebook'
+id: 4CDh12JM3y9AqBnuGDHgnT
+status: PUBLISHED
+createdAt: 2024-04-03T12:41:15.144Z
+updatedAt: 2024-04-03T12:41:16.005Z
+publishedAt: 2024-04-03T12:41:16.005Z
+firstPublishedAt: 2024-04-03T12:41:16.005Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: facebook-hoje-o-facebook-analisa-o-sellingprice-e-o-listprice-para-atualizar-o-preco-no-catalogo-do-facebook
+locale: pt
+kiStatus: Backlog
+internalReference: 924411
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Hoje, o Facebook analisa o sellingPrice e o listPrice para atualizar o preço no catálogo do Facebook.
+
+## Simulação
+
+
+O vendedor está usando unitMultiplier = 0,5
+
+O Checkout faz o seguinte cálculo quando o item tem uma unidade multiplicadora, portanto, sellingPrice = price * unitMultiplier = 3999 * 0,5 = 1999,5. O arredondamento do checkout ignorará o decimal e considerará 1999
+
+Qual é o problema com esse cálculo?
+Quando o vendedor usa 0,5, por exemplo, no Facebook, estamos atualizando-o como o preço de liquidação no Facebook.
+2. Quando o vendedor usa um multiplicador maior que 1,39, ele se enquadra no preço promocional, embora seja maior que o listPrice
+
+## Workaround
+
+
+o vendedor usa unitMultiplier = 10000
+
+
+
+
+
diff --git a/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md b/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
new file mode 100644
index 000000000..20008b90f
--- /dev/null
+++ b/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
@@ -0,0 +1,46 @@
+---
+title: 'Facetas do Segmento que afetam os breadcrumbs, o título da página e os filtros adicionais'
+id: 3lBgcsjxiZxoDvnPhbMXgo
+status: PUBLISHED
+createdAt: 2024-06-27T22:57:42.875Z
+updatedAt: 2024-06-27T22:57:43.965Z
+publishedAt: 2024-06-27T22:57:43.965Z
+firstPublishedAt: 2024-06-27T22:57:43.965Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: facetas-do-segmento-que-afetam-os-breadcrumbs-o-titulo-da-pagina-e-os-filtros-adicionais
+locale: pt
+kiStatus: Backlog
+internalReference: 1057254
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A propriedade "facets" armazenada no Segmento/Sessão para um contexto de navegação funciona para limitar os resultados da pesquisa a filtros predefinidos. Por exemplo, ela é usada por "B2B Organizations" para restringir o que um usuário pode ver na loja.
+
+Essas facetas podem afetar o comportamento de títulos de página e breadcrumbs, gerando valores inesperados que não fazem parte dos filtros aplicados na página. Todos os filtros são considerados ao gerar esses valores, não apenas os filtros explícitos da página, que devem ignorar as facetas do Segment.
+
+Isso também pode afetar o URL da página à medida que você aplica filtros adicionais, que serão mesclados com as facetas do Segment.
+
+## Simulação
+
+
+
+- Associe um usuário a uma organização B2B que esteja limitada a algumas coleções de produtos (A);
+- Crie uma página de destino que mostre uma coleção diferente (B);
+- Os breadcrumbs e o título da página podem mostrar o nome da coleção A em vez da coleção B
+- Selecione filtros de pesquisa adicionais na página de destino, como uma categoria ou marca;
+- Observe que o URL (e também os breadcrumbs e o título da página) também mostrará a coleção A em vez de ficar limitado à coleção B
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md b/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md
index 683d8e8f1..0ae6bbf0d 100644
--- a/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md
+++ b/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md
@@ -3,8 +3,8 @@ title: 'Falha no cancelamento (PPP) quando o cancelamentoId=nulo'
 id: 4yNCRQ1xhA8lEp5AGRs5eu
 status: PUBLISHED
 createdAt: 2022-06-21T21:37:04.567Z
-updatedAt: 2022-11-25T22:07:04.838Z
-publishedAt: 2022-11-25T22:07:04.838Z
+updatedAt: 2023-08-11T19:16:35.985Z
+publishedAt: 2023-08-11T19:16:35.985Z
 firstPublishedAt: 2022-06-21T21:37:05.374Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: falha-no-cancelamento-ppp-quando-o-cancelamentoidnulo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 333897
 ---
 
diff --git a/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
new file mode 100644
index 000000000..3ff43ed9a
--- /dev/null
+++ b/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -0,0 +1,43 @@
+---
+title: 'A não adição de dados na etapa "entregar em outro endereço" faz com que o botão "ir para o pagamento" desapareça'
+id: cdZO8gGXDB1JZSj42AnVh
+status: PUBLISHED
+createdAt: 2022-01-24T21:42:52.750Z
+updatedAt: 2023-10-13T15:29:14.854Z
+publishedAt: 2023-10-13T15:29:14.854Z
+firstPublishedAt: 2023-10-13T15:29:14.854Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-nao-adicao-de-dados-na-etapa-entregar-em-outro-endereco-faz-com-que-o-botao-ir-para-o-pagamento-desapareca
+locale: pt
+kiStatus: Backlog
+internalReference: 467419
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Durante a etapa de checkout, na etapa de preenchimento dos dados de envio, ao clicar na opção "Entregar em outro endereço", se nenhum endereço for adicionado e o comprador voltar à lista de endereços (usando o botão "voltar ao catálogo de endereços"), o botão "Ir para o pagamento" desaparecerá.
+
+## Simulação
+
+
+
+- Durante a etapa de Checkout, ao preencher os dados de envio, se houver uma lista de endereços, clique em "Deliver to another address" (Entregar em outro endereço);
+- Não adicione nenhum endereço e retorne aos dados de envio clicando no botão "Back to address list" (Voltar à lista de endereços);
+- O botão "Go to payment" desaparece
+
+## Workaround
+
+
+Para que o botão seja exibido novamente, basta clicar em um dos endereços do catálogo de endereços. Entretanto, não há nenhuma solução alternativa para evitar esse comportamento.
+
+
+
+
diff --git a/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md b/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md
new file mode 100644
index 000000000..2ce99e68d
--- /dev/null
+++ b/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md
@@ -0,0 +1,43 @@
+---
+title: 'O carrinho FastStore mescla itens da linha de montagem'
+id: 4NBNaTZpr6PnRxPfrtGj77
+status: PUBLISHED
+createdAt: 2024-06-14T17:25:47.764Z
+updatedAt: 2024-06-14T17:25:48.655Z
+publishedAt: 2024-06-14T17:25:48.655Z
+firstPublishedAt: 2024-06-14T17:25:48.655Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-carrinho-faststore-mescla-itens-da-linha-de-montagem
+locale: pt
+kiStatus: Backlog
+internalReference: 1050068
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se a mesma opção de montagem for adicionada a produtos diferentes, o FastStore os mesclará em um único item de linha.
+
+## Simulação
+
+
+Tente adicionar dois ou mais produtos que tenham o mesmo item de montagem ao carrinho, os produtos serão adicionados na mesma linha
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md b/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
new file mode 100644
index 000000000..db64bd581
--- /dev/null
+++ b/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
@@ -0,0 +1,46 @@
+---
+title: 'Facetas do Faststore considerando não remover facetas definidas como ne hidden'
+id: 4EElvOEvMzcu52fhNOVJGM
+status: PUBLISHED
+createdAt: 2024-05-08T18:35:17.015Z
+updatedAt: 2024-05-08T18:36:15.922Z
+publishedAt: 2024-05-08T18:36:15.922Z
+firstPublishedAt: 2024-05-08T18:35:18.742Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: facetas-do-faststore-considerando-nao-remover-facetas-definidas-como-ne-hidden
+locale: pt
+kiStatus: Backlog
+internalReference: 1029837
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+O comportamento esperado na API de facetas do IS é não trazer facetas com true oculto, mas há algumas exceções para isso, por exemplo, quando a faceta é selecionada na consulta, a API traz a faceta nos resultados com a propriedade oculta como true, e não estamos considerando essa informação
+
+## Simulação
+
+
+
+Filtro para uma consulta com a faceta oculta, como, por exemplo:
+
+https://storeframework.vtex.app/new-collection?productclusternames=new-collection&fuzzy=0&operator=and&facets=productclusternames%2Cfuzzy%2Coperator&sort=score_desc&page=0
+
+Nesse caso, productClusterNames é definido como oculto, mas, como está sendo filtrado, é exibido no navegador de filtro
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md b/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md
new file mode 100644
index 000000000..bdb37adf1
--- /dev/null
+++ b/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md
@@ -0,0 +1,35 @@
+---
+title: 'A API de pesquisa da Faststore considera o fuzzy como automático por padrão'
+id: 2zedXBMhlD8pu4gZMXsrSp
+status: PUBLISHED
+createdAt: 2023-08-28T23:35:04.009Z
+updatedAt: 2024-03-27T14:10:53.090Z
+publishedAt: 2024-03-27T14:10:53.090Z
+firstPublishedAt: 2023-08-28T23:35:04.608Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: a-api-de-pesquisa-da-faststore-considera-o-fuzzy-como-automatico-por-padrao
+locale: pt
+kiStatus: Fixed
+internalReference: 889321
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No pacote @fatstore/api, para o resolvedor da Pesquisa Inteligente, estamos considerando o fuzzy como automático por padrão quando deveria ser 0. Isso está fazendo com que o comportamento do fuzzy seja aplicado, causando uma "falsa correspondência incorreta" nos resultados da pesquisa quando realmente temos uma correspondência exata com o termo pesquisado, mas exibimos mais resultados independentemente disso
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md b/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md
new file mode 100644
index 000000000..0b26e221b
--- /dev/null
+++ b/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md
@@ -0,0 +1,44 @@
+---
+title: 'O Faststore V1 não retorna informações de SEO na consulta Graphql'
+id: 4nZnX8sj9J90xtkNpYIgZ4
+status: PUBLISHED
+createdAt: 2023-11-01T17:08:35.090Z
+updatedAt: 2023-11-01T17:13:13.061Z
+publishedAt: 2023-11-01T17:13:13.061Z
+firstPublishedAt: 2023-11-01T17:08:35.767Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-faststore-v1-nao-retorna-informacoes-de-seo-na-consulta-graphql
+locale: pt
+kiStatus: No Fix
+internalReference: 929029
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao acessar o playground do Graphql para executar consultas no Faststore V1, temos uma consulta de produto. A documentação afirma que o campo SEO dessa consulta deve retornar as informações de SEO, mas isso não está acontecendo.
+
+## Simulação
+
+
+
+- acesse sua loja usando o playground do Graphql
+- executar a consulta do produto com os campos SEO
+- compare com as informações de SEO do produto no catálog
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md b/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
index 56392362c..11199f241 100644
--- a/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
+++ b/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
@@ -3,8 +3,8 @@ title: 'Buscar Mais mantendo o status da próxima página e bloqueando a pagina
 id: 3hyeUjVRNKE8A2UYIQiw2x
 status: PUBLISHED
 createdAt: 2022-04-11T20:53:26.480Z
-updatedAt: 2022-11-25T21:58:27.486Z
-publishedAt: 2022-11-25T21:58:27.486Z
+updatedAt: 2024-07-01T18:48:17.176Z
+publishedAt: 2024-07-01T18:48:17.176Z
 firstPublishedAt: 2022-04-11T20:53:26.870Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: buscar-mais-mantendo-o-status-da-proxima-pagina-e-bloqueando-a-paginacao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 560014
 ---
 
diff --git a/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md b/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
index 9cf6d04f5..e6ac52333 100644
--- a/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
+++ b/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
@@ -3,8 +3,8 @@ title: 'Casas decimais do campo Moeda na Política Comercial não refletem no PD
 id: 1QxxwRvFDUVnGHh5icIPpo
 status: PUBLISHED
 createdAt: 2022-11-09T17:40:35.832Z
-updatedAt: 2022-11-25T21:41:45.862Z
-publishedAt: 2022-11-25T21:41:45.862Z
+updatedAt: 2024-02-16T20:24:30.832Z
+publishedAt: 2024-02-16T20:24:30.832Z
 firstPublishedAt: 2022-11-09T17:40:36.610Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: casas-decimais-do-campo-moeda-na-politica-comercial-nao-refletem-no-pdpplp
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 695044
 ---
 
diff --git a/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index cd4d2c93b..553da380d 100644
--- a/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -1,18 +1,18 @@
 ---
-title: 'O campo "Trocas e devoluções" não está atualizando a interface de gestão do vendedor após salvar'
+title: 'O campo "Exchanges and returns" (Trocas e devoluções) não está sendo atualizado na IU de gerenciamento do vendedor após o salvamento'
 id: 1z8LrsbGk5B2ejZ1PV9vaB
 status: PUBLISHED
 createdAt: 2022-11-01T17:47:30.359Z
-updatedAt: 2022-11-25T22:00:22.743Z
-publishedAt: 2022-11-25T22:00:22.743Z
+updatedAt: 2023-10-30T19:28:26.143Z
+publishedAt: 2023-10-30T19:28:26.143Z
 firstPublishedAt: 2022-11-01T17:47:31.132Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
-slug: o-campo-trocas-e-devolucoes-nao-esta-atualizando-a-interface-de-gestao-do-vendedor-apos-salvar
+slug: o-campo-exchanges-and-returns-trocas-e-devolucoes-nao-esta-sendo-atualizado-na-iu-de-gerenciamento-do-vendedor-apos-o-salvamento
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 689886
 ---
 
@@ -23,32 +23,17 @@ internalReference: 689886
 </div>
 
 
+Depois de salvar o campo "Trocas e devoluções" na interface do usuário, as informações são atualizadas pela primeira vez, mas se tentarmos sair da área de gerenciamento ou atualizar a página, as informações serão perdidas.
 
-Após salvar o campo "Trocas e devoluções" na IU, a informação é primeiramente atualizada, mas se tentarmos deixar a área de gerenciamento ou atualizar a página, a informação é perdida.
-
-
-
-As informações mostradas na IU são as mesmas do campo "Política de embarque".
-
-
-
-Entretanto, isto parece estar acontecendo somente na IU, via API as informações estão corretas.
-
-
+As informações exibidas na interface do usuário são as mesmas do campo "Política de envio".
 
+No entanto, isso parece estar acontecendo somente na interface do usuário; via API, as informações estão corretas.
 
 ## Simulação
 
 
 
-1. Entre com um vendedor na área de gerenciamento de vendas;
-2. Alterar as informações no campo "Trocas e devoluções" e salvar;
-3. Digite novamente o mesmo vendedor e verifique se as informações não estão corretas.
-
-
-
 ## Workaround
 
 
-Não há necessidade de trabalhar em conjunto, as informações estão corretas no backend do sistema.
 
diff --git a/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md b/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
index 3e50ae715..ae7b2d25a 100644
--- a/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
+++ b/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
@@ -1,18 +1,18 @@
 ---
-title: 'Os campos na configuração do OrderForm são atualizados para zero quando há qualquer mudança nas configurações de gerenciamento de pedidos'
+title: 'Os campos na configuração do orderForm são atualizados para nulos quando há alguma alteração nas configurações do Order Management.'
 id: jKGnwUGdfmCXtKjGPe6hj
 status: PUBLISHED
 createdAt: 2023-02-06T21:00:09.224Z
-updatedAt: 2023-04-03T14:22:00.794Z
-publishedAt: 2023-04-03T14:22:00.794Z
+updatedAt: 2024-05-09T12:44:51.823Z
+publishedAt: 2024-05-09T12:44:51.823Z
 firstPublishedAt: 2023-02-06T21:00:09.753Z
 contentType: knownIssue
-productTeam: Checkout
+productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
-tag: Checkout
-slug: os-campos-na-configuracao-do-orderform-sao-atualizados-para-zero-quando-ha-qualquer-mudanca-nas-configuracoes-de-gerenciamento-de-pedidos
+tag: Order Management
+slug: os-campos-na-configuracao-do-orderform-sao-atualizados-para-nulos-quando-ha-alguma-alteracao-nas-configuracoes-do-order-management
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 748404
 ---
 
@@ -23,26 +23,20 @@ internalReference: 748404
 </div>
 
 
-Ao atualizar qualquer informação nas Configurações de Gerenciamento de Pedidos (na administração), os campos "Sistema de PagamentoPagarPrimeiro Pedido" e "Sistema de PagamentoPagarPagarPadrãoAplicarNo Formulário de Pedido/Usuário" são configurados como "nulo" na Configuração do Formulário de Pedido
-
-
-##
+Ao atualizar qualquer informação nas configurações de gerenciamento de pedidos (no administrador), os campos `paymentSystemToCheckFirstInstallment` e `defaultPaymentSystemToApplyOnUserOrderForm` são definidos como `null` na configuração do formulário de pedido
 
 ## Simulação
 
 
 
-- Configurar os campos `paymentSystemToCheckFirstInstallment' e `defaultPaymentSystemToApplyOnUserOrderOrderForm' na ordemForm de configuração via API
+- Configure os campos `paymentSystemToCheckFirstInstallment` e `defaultPaymentSystemToApplyOnUserOrderForm` na configuração do orderForm via API
 - Alterar qualquer coisa nas configurações de gerenciamento de pedidos (admin)
-- Quando você fizer o pedidoFormar configuração, você verá esses campos como 'nulos'.
-
-
-##
+- Ao obter a configuração do orderForm, você verá esses campos como "nulos"
 
 ## Workaround
 
 
-Salvar a configuração do OrderForm com os valores corretos para os campos `paymentSystemToCheckFirstInstallment' e `defaultPaymentSystemToApplyOnUserOrderOrderForm' após a mudança nas configurações de gerenciamento de pedidos
+Salve a configuração do orderForm com os valores corretos para os campos `paymentSystemToCheckFirstInstallment` e `defaultPaymentSystemToApplyOnUserOrderForm` após a alteração nas configurações do Order Management
 
 
 
diff --git a/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md b/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md
index 249253ace..c4067fbdb 100644
--- a/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md
+++ b/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md
@@ -22,7 +22,7 @@ Ao obter os endereços que um cliente pode ter, o checkout não está validando
 
 Mensagem: Não são permitidos múltiplos países nos endereços
 Vale lembrar que, na entidade de dados "endereços" (AD), dentro do Master Data, esses campos são abertos, ou seja, podem ser colocados como não obrigatórios, e podem estar vazios. Então, nos momentos em que esta informação é alimentada por meio de integrações (usando nossas APIs), a porta se abre para ter registros que não possuem, por exemplo, os dados de "País", terminando no erro mencionado acima.
-![image1](https://images.ctfassets.net/alneenqid6w5/3eMExnt2FHAFOsBEt4nldh/80f92f5e5f02611d394cf3e1037a6865/image1.png)
+![image1](//images.ctfassets.net/alneenqid6w5/3eMExnt2FHAFOsBEt4nldh/80f92f5e5f02611d394cf3e1037a6865/image1.png)
 
 __Comportamento esperado__
 
@@ -35,10 +35,10 @@ O checkout recebe as informações dos endereços que estão associados ao dito
 As opções são mostradas e, apesar de não ter os dados do país dentro do JSON (country) do OrderForm (selectedAddresses.[0].country), na interface do usuário, os endereços mostram o país. Isto significa que o cliente ou o gerente da loja não pode perceber facilmente que algumas informações críticas são necessárias para continuar a compra.
 
 __JSON__
-![image2](https://images.ctfassets.net/alneenqid6w5/4uAXxjyD8rI8hdA0fq5T5B/d45c179e4038ca6be57883d307228cf6/image2.png)
+![image2](//images.ctfassets.net/alneenqid6w5/4uAXxjyD8rI8hdA0fq5T5B/d45c179e4038ca6be57883d307228cf6/image2.png)
 
 __Checkout UI__
-![image3](https://images.ctfassets.net/alneenqid6w5/5Q1zZJRzUxPIziPp0Giqy3/79d822c3e9d6042e7399c6fa53958d47/image3.png)
+![image3](//images.ctfassets.net/alneenqid6w5/5Q1zZJRzUxPIziPp0Giqy3/79d822c3e9d6042e7399c6fa53958d47/image3.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md b/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
index 9f5a125d0..e041a2532 100644
--- a/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
+++ b/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
@@ -1,18 +1,18 @@
 ---
-title: 'O File Manager upload com mais dois arquivos existentes não atualiza todos os arquivos, apenas o primeiro'
+title: 'O upload do File Manager com dois ou mais arquivos existentes não atualiza todos os arquivos, apenas o primeiro'
 id: 2LHdzsFFe83E1Tf0Z4j66y
 status: PUBLISHED
 createdAt: 2022-03-17T00:20:51.454Z
-updatedAt: 2022-11-25T22:10:54.509Z
-publishedAt: 2022-11-25T22:10:54.509Z
+updatedAt: 2024-02-16T20:23:18.080Z
+publishedAt: 2024-02-16T20:23:18.080Z
 firstPublishedAt: 2022-03-17T00:20:52.317Z
 contentType: knownIssue
 productTeam: Portal
 author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
-slug: o-file-manager-upload-com-mais-dois-arquivos-existentes-nao-atualiza-todos-os-arquivos-apenas-o-primeiro
+slug: o-upload-do-file-manager-com-dois-ou-mais-arquivos-existentes-nao-atualiza-todos-os-arquivos-apenas-o-primeiro
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 418253
 ---
 
@@ -23,25 +23,21 @@ internalReference: 418253
 </div>
 
 
-O File Manager upload com mais dois arquivos existentes não atualiza todos os arquivos, apenas o primeiro
-
-
+O upload do gerenciador de arquivos com dois ou mais arquivos existentes não atualiza todos os arquivos, apenas o primeiro
 
 ## Simulação
 
 
-- Ir para /admin/a, gerenciador de arquivos, e adicionar 2 ou mais arquivos para carregar;
-- Agora faça o upload de outros dois arquivos com o mesmo nome:
-- Receberemos um aviso informando que o arquivo existe, perguntando-nos se queremos substituí-lo.
-
-Este aviso nos fala apenas de um arquivo, o segundo não está sendo validado.
-
-- Ambos os arquivos são carregados, mas apenas um irá substituir o mais antigo.
+- Vá para /admin/a, gerenciador de arquivos e adicione dois ou mais arquivos para upload;
+- Agora carregue dois outros arquivos com o mesmo nome:
+- Receberemos um aviso informando que o arquivo existe e perguntando se queremos substituí-lo.
 
+Esse aviso está nos informando apenas sobre um arquivo, o segundo não está sendo validado.
 
+- Ambos os arquivos são carregados, mas apenas um substituirá o mais antigo
 
 ## Workaround
 
 
-Atualizar um arquivo por vez.
+Atualize um arquivo por vez.
 
diff --git a/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md b/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
index 63115d263..09bec7dc8 100644
--- a/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
+++ b/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
@@ -3,8 +3,8 @@ title: ' Filtrar por SkuName no desempenho de vendas não está aceitando maiús
 id: 3FCDeEn8xmEvOXKgBxqyL5
 status: PUBLISHED
 createdAt: 2022-08-16T18:06:02.919Z
-updatedAt: 2022-11-30T19:08:14.148Z
-publishedAt: 2022-11-30T19:08:14.148Z
+updatedAt: 2024-02-16T20:24:21.760Z
+publishedAt: 2024-02-16T20:24:21.760Z
 firstPublishedAt: 2022-08-16T18:06:03.474Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: filtrar-por-skuname-no-desempenho-de-vendas-nao-esta-aceitando-maiusculas
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639219
 ---
 
diff --git a/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
new file mode 100644
index 000000000..ee65018f7
--- /dev/null
+++ b/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -0,0 +1,44 @@
+---
+title: 'O filtro "productClusterIds" é substituído por "productClusterNames" ao aplicar filtros adicionais'
+id: 3d4BIZQBZgeK3eKwT8B1PZ
+status: PUBLISHED
+createdAt: 2023-09-13T22:42:57.138Z
+updatedAt: 2023-09-21T18:04:57.946Z
+publishedAt: 2023-09-21T18:04:57.946Z
+firstPublishedAt: 2023-09-13T22:42:57.682Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: o-filtro-productclusterids-e-substituido-por-productclusternames-ao-aplicar-filtros-adicionais
+locale: pt
+kiStatus: Backlog
+internalReference: 899508
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma pesquisa é iniciada com o filtro "productClusterIds", a aplicação de qualquer filtro adicional o converterá em "productClusterNames", perdendo a característica de apresentar os itens com a classificação definida manualmente na coleção de produtos.
+
+## Simulação
+
+
+O cenário pode ser visto em qualquer página, como `"store.com/111?map=productClusterIds"`, e aplicando qualquer filtro adicional, como uma categoria, especificação etc.
+
+O usuário será direcionado para `"store.com/clothing/special-sale?initialMap=productClusterIds&initialQuery=111&map=category,productclusternames"`.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa para o problema específico se você precisar da classificação especial, mas certifique-se de usar "productClusterIds" somente nos cenários necessários. Caso contrário, use o filtro como "productClusterNames".
+
+
+
+
diff --git a/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md b/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md
new file mode 100644
index 000000000..8ac3cb41d
--- /dev/null
+++ b/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md
@@ -0,0 +1,47 @@
+---
+title: 'Filtra por especificações de SKU sem considerar a disponibilidade regionalizada'
+id: 3CeTfHaNBfhrC5qIi3nTLh
+status: PUBLISHED
+createdAt: 2024-06-05T20:52:53.211Z
+updatedAt: 2024-06-05T20:52:54.055Z
+publishedAt: 2024-06-05T20:52:54.055Z
+firstPublishedAt: 2024-06-05T20:52:54.055Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: filtra-por-especificacoes-de-sku-sem-considerar-a-disponibilidade-regionalizada
+locale: pt
+kiStatus: Backlog
+internalReference: 1045111
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A filtragem da pesquisa por uma especificação de SKU também aplicará um filtro por disponibilidade de SKU, removendo os produtos em que a variação selecionada estiver em falta, mas isso não se aplica a lojas regionalizadas.
+
+As navegações regionalizadas podem retornar produtos em que a variação filtrada não está disponível porque a disponibilidade indexada para uma especificação de SKU é baseada em todos os vendedores regulares e de marca branca.
+
+## Simulação
+
+
+Considerando uma loja com dois vendedores e a seguinte matriz de disponibilidade para um produto específico:
+
+- tamanho: pequeno; vendedor A: disponível; vendedor B: indisponível
+- tamanho: grande; vendedor A: indisponível; vendedor B: indisponível
+
+Em uma navegação com "regionId: seller B", a filtragem por "size: small" retornará o produto (como se ele estivesse disponível) e "size: large" ocultará o produto (porque ele não está disponível em todos os lugares)
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md b/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
new file mode 100644
index 000000000..5968e086d
--- /dev/null
+++ b/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
@@ -0,0 +1,35 @@
+---
+title: 'Os filtros ocultos na loja também são ocultos nas páginas de administração do Intelligent Search'
+id: 3TvpIUFzdXWesADHDhjyLQ
+status: PUBLISHED
+createdAt: 2022-02-23T21:59:22.607Z
+updatedAt: 2023-10-19T16:24:57.801Z
+publishedAt: 2023-10-19T16:24:57.801Z
+firstPublishedAt: 2022-02-23T21:59:22.977Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: os-filtros-ocultos-na-loja-tambem-sao-ocultos-nas-paginas-de-administracao-do-intelligent-search
+locale: pt
+kiStatus: Backlog
+internalReference: 416638
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas especificações têm uso interno ou cenários que precisam ser ocultados, mas a loja precisa dessa especificação para fins de pesquisa, como usá-la para Regras de comercialização.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md b/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
new file mode 100644
index 000000000..aa40a4b96
--- /dev/null
+++ b/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
@@ -0,0 +1,35 @@
+---
+title: 'O domínio final é diferente do myvtex devido à versão antiga do componente no Site Editor'
+id: 7bf2mMbpcxUd6Q32DYP6vz
+status: PUBLISHED
+createdAt: 2023-12-05T18:07:50.089Z
+updatedAt: 2024-01-26T17:52:03.169Z
+publishedAt: 2024-01-26T17:52:03.169Z
+firstPublishedAt: 2023-12-05T18:07:50.675Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: o-dominio-final-e-diferente-do-myvtex-devido-a-versao-antiga-do-componente-no-site-editor
+locale: pt
+kiStatus: Backlog
+internalReference: 948071
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Às vezes, você pode fazer alterações no Site Editor e essas alterações são refletidas no ambiente myvtex, mas quando você tenta atualizar o domínio final, essas alterações não são refletidas. Isso normalmente acontece quando o componente que você está tentando alterar tem mais de uma versão. O front continua usando a versão inativa do componente, enquanto o myvtex está usando a versão ativa. A única maneira de resolver isso é excluir a versão inativa do componente.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md b/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
new file mode 100644
index 000000000..bc68d7443
--- /dev/null
+++ b/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
@@ -0,0 +1,43 @@
+---
+title: 'O primeiro endereço da lista de endereços incompleto não preenche os dados de perfil/envio no checkout'
+id: 2AqDZb1AGBjmeMOBU0JkLQ
+status: PUBLISHED
+createdAt: 2024-01-03T20:44:07.692Z
+updatedAt: 2024-01-03T20:49:41.249Z
+publishedAt: 2024-01-03T20:49:41.249Z
+firstPublishedAt: 2024-01-03T20:44:11.604Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-primeiro-endereco-da-lista-de-enderecos-incompleto-nao-preenche-os-dados-de-perfilenvio-no-checkout
+locale: pt
+kiStatus: Backlog
+internalReference: 366975
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário tem mais de um endereço em seu perfil e o primeiro endereço na lista de endereços está incompleto, independentemente de os outros serem válidos, o checkout não preenche automaticamente os dados de perfil/envio após a adição do e-mail.
+
+## Simulação
+
+
+
+- Adicione 2 endereços a um perfil, sendo que o primeiro está incompleto;
+- Montar um carrinho e adicionar o e-mail;
+- Nenhum dado de perfil/endereço é preenchido
+
+## Workaround
+
+
+Remova o endereço incompleto do perfil por meio dos dados mestre
+
+
+
+
diff --git a/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md b/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
new file mode 100644
index 000000000..4d7ad639d
--- /dev/null
+++ b/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
@@ -0,0 +1,42 @@
+---
+title: 'O primeiro dígito é removido de corporateDocument se começar com letras'
+id: sfKdoiEwBRR73CbhvSHJF
+status: PUBLISHED
+createdAt: 2023-10-17T17:26:20.683Z
+updatedAt: 2024-03-14T22:02:01.236Z
+publishedAt: 2024-03-14T22:02:01.236Z
+firstPublishedAt: 2023-10-17T17:26:21.490Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: o-primeiro-digito-e-removido-de-corporatedocument-se-comecar-com-letras
+locale: pt
+kiStatus: Fixed
+internalReference: 920703
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o documento corporativo de uma organização começa com letras, o primeiro dígito é removido após o acesso ao checkout.
+
+## Simulação
+
+
+
+- Registre uma organização cujo documento corporativo comece com letras;
+- Adicione itens ao carrinho;
+- Vá para o checkout e verifique o formulário de pedido, o primeiro dígito do campo corporateDocument será removido
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/first-subscription-cycle-is-skipped.md b/docs/known-issues/pt/first-subscription-cycle-is-skipped.md
new file mode 100644
index 000000000..8e001f74c
--- /dev/null
+++ b/docs/known-issues/pt/first-subscription-cycle-is-skipped.md
@@ -0,0 +1,47 @@
+---
+title: 'O primeiro ciclo de assinatura é ignorado'
+id: 2VX6uoop56wK6jecAly40G
+status: PUBLISHED
+createdAt: 2024-02-05T14:10:40.701Z
+updatedAt: 2024-02-05T14:10:41.599Z
+publishedAt: 2024-02-05T14:10:41.599Z
+firstPublishedAt: 2024-02-05T14:10:41.599Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-primeiro-ciclo-de-assinatura-e-ignorado
+locale: pt
+kiStatus: Backlog
+internalReference: 528556
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O sistema de assinatura usa informações como a frequência de compra e a data do ciclo de assinatura para gerar um pedido de assinatura. No entanto, dependendo do fuso horário do consumidor e da hora em que o pedido é feito, o primeiro ciclo é ignorado e gerado somente no segundo mês.
+Suponha que em 9 de maio, às 23h, um cliente tenha criado uma assinatura mensal e definido a data do ciclo de assinatura para o nono dia de cada mês, esperando que o primeiro pedido fosse feito em 9 de junho.
+O sistema de gerenciamento de pedidos opera no fuso horário definido anteriormente na loja. Nesse caso, consideraremos GMT-5, horário de Chicago. No entanto, o sistema de assinatura opera no fuso horário GMT 0. Isso significa que, embora a assinatura tenha sido criada às 23h, o sistema de assinatura considera que ela foi criada 5 horas depois, portanto, em 10 de maio.
+Nesse caso, o sistema leva em consideração a data de criação da assinatura, 10 de maio, para calcular o próximo ciclo de assinatura. Como a data do ciclo de assinatura em 9 de junho não atenderia à condição do período de 30 dias, totalizando 29 dias, o sistema define a próxima data de compra para julho. Portanto, o cliente acaba recebendo o produto após a data esperada.
+
+## Simulação
+
+
+Tenha uma SKU configurada para assinatura, com frequência mensal e dia de compra;
+Fazer um pedido após as 23h, por exemplo
+Verifique se o primeiro ciclo, que deveria ser gerado no mês seguinte, será ignorado, sendo gerado apenas no segundo mês.
+
+## Workaround
+
+
+n/a
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md b/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
index 8c4699045..e1a2943fe 100644
--- a/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
+++ b/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
@@ -3,8 +3,8 @@ title: 'Preço fixo sendo criado na política comercial 1 ao economizar preços
 id: 3Xbh5GVn0jm2yhaOiRg3Le
 status: PUBLISHED
 createdAt: 2022-11-28T12:41:07.808Z
-updatedAt: 2022-11-28T12:41:08.426Z
-publishedAt: 2022-11-28T12:41:08.426Z
+updatedAt: 2024-02-16T20:24:01.848Z
+publishedAt: 2024-02-16T20:24:01.848Z
 firstPublishedAt: 2022-11-28T12:41:08.426Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: preco-fixo-sendo-criado-na-politica-comercial-1-ao-economizar-precos-de-pacote
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 705869
 ---
 
diff --git a/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index 5d156cab6..1da7bcecc 100644
--- a/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -3,8 +3,8 @@ title: 'FOB External Marketplace integra uma ordem (código Erro: "FMT010")'
 id: 3qzV4zJRkPIwQnAZuK5dWu
 status: PUBLISHED
 createdAt: 2022-02-25T16:33:49.641Z
-updatedAt: 2022-11-25T22:00:10.646Z
-publishedAt: 2022-11-25T22:00:10.646Z
+updatedAt: 2024-02-16T20:26:31.795Z
+publishedAt: 2024-02-16T20:26:31.795Z
 firstPublishedAt: 2022-02-25T16:33:50.398Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: fob-external-marketplace-integra-uma-ordem-codigo-erro-fmt010
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 532377
 ---
 
diff --git a/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md b/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
index 0d0415cd4..31dd2281e 100644
--- a/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
+++ b/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
@@ -3,8 +3,8 @@ title: 'Promoção de remessa gratuita sendo aplicada em pedidos divididos fora
 id: APAIGZx8tdtIjGsQJmvgu
 status: PUBLISHED
 createdAt: 2023-01-12T16:19:47.878Z
-updatedAt: 2023-01-12T16:19:48.479Z
-publishedAt: 2023-01-12T16:19:48.479Z
+updatedAt: 2024-02-16T20:23:58.107Z
+publishedAt: 2024-02-16T20:23:58.107Z
 firstPublishedAt: 2023-01-12T16:19:48.479Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: promocao-de-remessa-gratuita-sendo-aplicada-em-pedidos-divididos-fora-da-restricao-de-promocao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 732302
 ---
 
diff --git a/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md b/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
new file mode 100644
index 000000000..92778452c
--- /dev/null
+++ b/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
@@ -0,0 +1,46 @@
+---
+title: 'A limpeza completa dos vendedores não funciona se a conta tiver grupos de vendedores no Gerenciamento de vendedores'
+id: 3U9tS11FQU0JLUxEDSt5rL
+status: PUBLISHED
+createdAt: 2023-10-19T19:54:36.389Z
+updatedAt: 2024-07-01T18:49:14.530Z
+publishedAt: 2024-07-01T18:49:14.530Z
+firstPublishedAt: 2023-10-19T19:54:37.266Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: a-limpeza-completa-dos-vendedores-nao-funciona-se-a-conta-tiver-grupos-de-vendedores-no-gerenciamento-de-vendedores
+locale: pt
+kiStatus: No Fix
+internalReference: 922541
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na área de gerenciamento de vendedores, o marketplace pode agrupar seus vendedores como desejar e gerenciá-los na guia de gerenciamento de grupos.
+
+No entanto, se desejar excluir todos os dados do vendedor na área de limpeza completa, o processo falhará se houver grupos criados.
+
+## Simulação
+
+
+
+1. Crie um grupo de vendedores no Seller Management;
+2. Realize uma limpeza completa do vendedor;
+3. Verifique se aparece um erro
+
+## Workaround
+
+
+Primeiro, exclua os grupos de vendedores manualmente no gerenciamento de vendedores e, em seguida, tente executar a limpeza completa do vendedor novamente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md b/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
new file mode 100644
index 000000000..0df9517bd
--- /dev/null
+++ b/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
@@ -0,0 +1,42 @@
+---
+title: 'O evento de compra GA4 não tem a árvore de categorias em item_category no dataLayer'
+id: 6GCrgcG8PJHaZp80hi4Gb1
+status: PUBLISHED
+createdAt: 2023-07-12T16:42:17.087Z
+updatedAt: 2023-07-12T16:43:37.976Z
+publishedAt: 2023-07-12T16:43:37.976Z
+firstPublishedAt: 2023-07-12T16:42:17.674Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-evento-de-compra-ga4-nao-tem-a-arvore-de-categorias-em-itemcategory-no-datalayer
+locale: pt
+kiStatus: Backlog
+internalReference: 860655
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O evento de compra do GA4 não tem a árvore de categorias em item_category no dataLayer, portanto, a única categoria disponível é a categoria de último nível do produto.
+
+## Simulação
+
+
+
+- Configure o aplicativo Google Tag Manager e ative "Send Google Analytics 4 Events" (Enviar eventos do Google Analytics 4);
+- Conclua uma compra;
+- No console, verifique os eventos em dataLayer; haverá apenas a categoria de último nível em item_category
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md b/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
index 4a40e0dcb..c44c387ec 100644
--- a/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
+++ b/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
@@ -3,8 +3,8 @@ title: 'Os dados GeoCoordinates não podem ser informados para alguma culturaInf
 id: 4MjLbyrniWsPKpFBHgn8sG
 status: PUBLISHED
 createdAt: 2022-05-19T16:19:45.245Z
-updatedAt: 2022-11-25T21:52:55.550Z
-publishedAt: 2022-11-25T21:52:55.550Z
+updatedAt: 2024-07-01T18:48:21.888Z
+publishedAt: 2024-07-01T18:48:21.888Z
 firstPublishedAt: 2022-05-19T16:19:45.749Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: os-dados-geocoordinates-nao-podem-ser-informados-para-alguma-culturainfo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 582065
 ---
 
diff --git a/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md b/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md
index e387190ce..86952e551 100644
--- a/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md
+++ b/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md
@@ -35,7 +35,7 @@ Se a localização do seu navegador satisfaz a condição acima, siga com estes
 5. Durante o checkout, selecione a opção de entrega: ponto de retirada. 
 6. Verifique que a tela apresenta uma mensagem contínua sobre carregamento da localização.
 
-![erro PT](https://images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/c3a49aa994fb5e5042a0d5a06f40c336/erro_PT.png)
+![erro PT](//images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/c3a49aa994fb5e5042a0d5a06f40c336/erro_PT.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index c5d0dfd4c..545f095d4 100644
--- a/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -1,18 +1,18 @@
 ---
-title: '"Obtenha todas as sugestões de SKU" API não mantém a mesma ordem de sku ao mudar os limites'
+title: 'A API "Obter todas as sugestões de SKU" não mantém a mesma ordem de SKU ao alterar os limites'
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
-updatedAt: 2022-12-05T14:50:25.991Z
-publishedAt: 2022-12-05T14:50:25.991Z
+updatedAt: 2024-03-01T21:06:12.857Z
+publishedAt: 2024-03-01T21:06:12.857Z
 firstPublishedAt: 2022-12-05T14:49:47.309Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
-slug: obtenha-todas-as-sugestoes-de-sku-api-nao-mantem-a-mesma-ordem-de-sku-ao-mudar-os-limites
+slug: a-api-obter-todas-as-sugestoes-de-sku-nao-mantem-a-mesma-ordem-de-sku-ao-alterar-os-limites
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 367187
 ---
 
@@ -22,35 +22,13 @@ internalReference: 367187
   <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
-
-
-A API "Get all SKU suggestions" tem um limite de 20 skus por página.
-
-Documentação API: https://developers.vtex.com/vtex-rest-api/reference/get-suggestions#getsuggestions
-
-No dia-a-dia de trabalho isso perturba o funcionamento do Marketplace porque toda vez que o Marketplace faz um pedido mudando os limites para obter os próximos 20 skus, a ordem dos skus também muda e isso dá a impressão de ter os skus duplicados.
-
-Ao solicitar esta API usando parâmetros de consulta como "sellerId", este comportamento acontece. Ao solicitar esta API sem os parâmetros de consulta, é possível utilizar o recurso "Next" (Próximo) para evitar este problema.
-
-
-
-###
+### **Resumo**
 
 ## Simulação
 
 
 
-1. Solicitar a API "Obter todas as sugestões de SKU" usando os parâmetros de consulta: "sellerId";
-2. Altere os limites nos parâmetros "**_de "** e "**_até "** para obter o próximo skus;
-3. Verificar se há um sku nesta página que já tenha aparecido nas páginas anteriores.
-
-
-
-###
-
 ## Workaround
 
 
 
-Para evitar esta situação, utilize a planilha de exportação na interface de usuário ou utilize o API sem os parâmetros.
-
diff --git a/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md b/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
new file mode 100644
index 000000000..bc8c615e9
--- /dev/null
+++ b/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
@@ -0,0 +1,40 @@
+---
+title: 'A API GET Coupon Usage não lista vários pedidos para o mesmo cupom'
+id: 7B9Qlcx2XMGxWj9OB5Xl8n
+status: PUBLISHED
+createdAt: 2023-09-08T17:54:13.642Z
+updatedAt: 2023-09-08T17:54:14.220Z
+publishedAt: 2023-09-08T17:54:14.220Z
+firstPublishedAt: 2023-09-08T17:54:14.220Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: a-api-get-coupon-usage-nao-lista-varios-pedidos-para-o-mesmo-cupom
+locale: pt
+kiStatus: Backlog
+internalReference: 326662
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+## Simulação
+
+
+1) Feche dois pedidos distintos com o mesmo cupom.
+
+2) Obter os dados de uso desse cupom https://developers.vtex.com/vtex-rest-api/reference/coupons#getusage
+
+3) Será listado o total menos um pedido.
+
+## Workaround
+
+
+n/a
+
diff --git a/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md b/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md
index 599fc65f6..79c24c7b7 100644
--- a/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md
+++ b/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md
@@ -3,8 +3,8 @@ title: 'Obter a Lista de Ofertas Combinadas API não funciona corretamente'
 id: 7mxrjTDYB8yLeKmQkB5D9h
 status: PUBLISHED
 createdAt: 2022-03-31T13:49:41.374Z
-updatedAt: 2022-11-25T22:00:46.842Z
-publishedAt: 2022-11-25T22:00:46.842Z
+updatedAt: 2024-07-01T18:48:12.526Z
+publishedAt: 2024-07-01T18:48:12.526Z
 firstPublishedAt: 2022-03-31T13:49:42.277Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: obter-a-lista-de-ofertas-combinadas-api-nao-funciona-corretamente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 553456
 ---
 
diff --git a/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
index 0ce0ce773..53163076d 100644
--- a/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
@@ -3,8 +3,8 @@ title: 'GET Product by Refid retorna "Null" quando não é encontrado'
 id: 6yiM9gJT5DB77pZSBNfGZ3
 status: PUBLISHED
 createdAt: 2023-05-16T19:35:46.743Z
-updatedAt: 2023-05-16T19:35:47.468Z
-publishedAt: 2023-05-16T19:35:47.468Z
+updatedAt: 2024-07-01T18:49:03.498Z
+publishedAt: 2024-07-01T18:49:03.498Z
 firstPublishedAt: 2023-05-16T19:35:47.468Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: get-product-by-refid-retorna-null-quando-nao-e-encontrado
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 826702
 ---
 
diff --git a/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md b/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md
index 33c3b3aa8..dc75d566b 100644
--- a/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md
+++ b/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md
@@ -3,8 +3,8 @@ title: 'GET SKU by EAN API retorna apenas SKUs ativas'
 id: 5NiuB1Lgf3CM5kXSSVdfuu
 status: PUBLISHED
 createdAt: 2020-03-23T15:10:23.842Z
-updatedAt: 2022-11-25T22:00:19.153Z
-publishedAt: 2022-11-25T22:00:19.153Z
+updatedAt: 2023-10-24T17:25:02.496Z
+publishedAt: 2023-10-24T17:25:02.496Z
 firstPublishedAt: 2020-03-27T19:32:53.914Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: get-sku-by-ean-api-retorna-apenas-skus-ativas
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 699007
 ---
 
diff --git a/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md b/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
index eb5733826..e3ec6e46b 100644
--- a/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
+++ b/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
@@ -3,8 +3,8 @@ title: 'getCurrentProductWithVariations da VTEX.js traz dados do Componente SKU
 id: 1m1bMbNXZVpQo9bQG1iSjn
 status: PUBLISHED
 createdAt: 2022-03-16T16:35:51.214Z
-updatedAt: 2022-11-25T22:10:09.849Z
-publishedAt: 2022-11-25T22:10:09.849Z
+updatedAt: 2024-02-16T20:24:03.691Z
+publishedAt: 2024-02-16T20:24:03.691Z
 firstPublishedAt: 2022-03-16T16:35:51.652Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: getcurrentproductwithvariations-da-vtexjs-traz-dados-do-componente-sku-e-nao-do-kit-sku
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 324416
 ---
 
diff --git a/docs/known-issues/pt/gift-card-creation-error-via-admin.md b/docs/known-issues/pt/gift-card-creation-error-via-admin.md
new file mode 100644
index 000000000..21d7d5a65
--- /dev/null
+++ b/docs/known-issues/pt/gift-card-creation-error-via-admin.md
@@ -0,0 +1,39 @@
+---
+title: 'Erro de criação de cartão-presente via administrador'
+id: 6GUhpZbxYr0wTIuqN3S95A
+status: PUBLISHED
+createdAt: 2024-02-21T22:45:26.869Z
+updatedAt: 2024-02-21T22:45:27.647Z
+publishedAt: 2024-02-21T22:45:27.647Z
+firstPublishedAt: 2024-02-21T22:45:27.647Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-de-criacao-de-cartaopresente-via-administrador
+locale: pt
+kiStatus: Backlog
+internalReference: 986327
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas contas não conseguirão criar um Gift Card pela primeira vez por meio do admin, a mensagem abaixo aparecerá na tela:
+
+`Algo deu errado`
+`Erro ao conectar-se ao servidor backend`.
+`Por favor, retorne à nossa loja em alguns instantes`.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md b/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
index 1757a5606..5b555d22c 100644
--- a/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
+++ b/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
@@ -3,8 +3,8 @@ title: 'A data de vencimento do cartão-presente não coincide com a data escolh
 id: 57GeuSubkdDkQNwzL3nmup
 status: PUBLISHED
 createdAt: 2022-03-27T14:08:35.577Z
-updatedAt: 2022-11-25T22:07:21.976Z
-publishedAt: 2022-11-25T22:07:21.976Z
+updatedAt: 2024-07-01T18:48:00.399Z
+publishedAt: 2024-07-01T18:48:00.399Z
 firstPublishedAt: 2022-03-27T14:08:36.056Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: a-data-de-vencimento-do-cartaopresente-nao-coincide-com-a-data-escolhida-quando-ele-foi-criado
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 378436
 ---
 
diff --git a/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md b/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
new file mode 100644
index 000000000..f1ff8c6bf
--- /dev/null
+++ b/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
@@ -0,0 +1,43 @@
+---
+title: 'O HUB do Gift Card aceita ID inválida/vazia em resposta à criação da transação'
+id: 3ODSXijmpvkk55FUqMcGvQ
+status: PUBLISHED
+createdAt: 2023-07-05T12:50:36.661Z
+updatedAt: 2023-07-05T12:51:07.938Z
+publishedAt: 2023-07-05T12:51:07.938Z
+firstPublishedAt: 2023-07-05T12:50:37.274Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-hub-do-gift-card-aceita-id-invalidavazia-em-resposta-a-criacao-da-transacao
+locale: pt
+kiStatus: Backlog
+internalReference: 855864
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A documentação do protocolo do nosso provedor de cartão-presente especifica que a API de criação de transação deve incluir um ID válido na resposta. No entanto, a implementação atual do protocolo permite que os provedores respondam a essa solicitação com um ID vazio ou inválido. Como resultado, ao tentar liquidar o pagamento, a transação fica presa porque a ID necessária está faltando. Isso faz com que um erro seja lançado e a transação permaneça presa no processo.
+
+## Simulação
+
+
+Responda à chamada de criação de transação com um ID inválido e tente concluir uma transação.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index 33b3d56f5..5cd43aa74 100644
--- a/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -3,8 +3,8 @@ title: 'O hub do Gift Card está adicionando uma contrabarra extra ("/") ao liga
 id: 2ZstMKKGUbrdXGuhS2Rr1f
 status: PUBLISHED
 createdAt: 2022-09-30T21:07:47.856Z
-updatedAt: 2022-11-25T22:04:08.181Z
-publishedAt: 2022-11-25T22:04:08.181Z
+updatedAt: 2024-02-16T20:24:58.109Z
+publishedAt: 2024-02-16T20:24:58.109Z
 firstPublishedAt: 2022-09-30T21:07:48.985Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: o-hub-do-gift-card-esta-adicionando-uma-contrabarra-extra-ao-ligar-para-os-fornecedores
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 669575
 ---
 
diff --git a/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
new file mode 100644
index 000000000..195b4f2d8
--- /dev/null
+++ b/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -0,0 +1,43 @@
+---
+title: 'Cartão-presente - Ele não retorna os campos "caption" e "relationName" quando fazemos uma solicitação get.'
+id: 2nh2Cc3Hc2Zm0b1INtwDep
+status: PUBLISHED
+createdAt: 2023-06-23T19:33:35.774Z
+updatedAt: 2024-02-16T20:25:03.806Z
+publishedAt: 2024-02-16T20:25:03.806Z
+firstPublishedAt: 2023-06-23T19:33:36.777Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: cartaopresente-ele-nao-retorna-os-campos-caption-e-relationname-quando-fazemos-uma-solicitacao-get
+locale: pt
+kiStatus: No Fix
+internalReference: 428725
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o método GET é executado para um cartão-presente existente, ele não retorna o campo "caption" nem o campo "relationName", embora esses parâmetros tenham valor.
+
+## Simulação
+
+
+Faça uma solicitação get na API: https://developers.vtex.com/vtex-rest-api/reference/gift-card#getgiftcardbyid
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md b/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md
index b46ac555b..e4ac17fd9 100644
--- a/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md
+++ b/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md
@@ -3,8 +3,8 @@ title: 'Os artigos de presente lançam uma exceção genérica se não tiver pre
 id: 7Jw1Nihqp3Sg2ecg7R9IEt
 status: PUBLISHED
 createdAt: 2022-05-12T14:52:18.546Z
-updatedAt: 2022-11-25T21:51:44.617Z
-publishedAt: 2022-11-25T21:51:44.617Z
+updatedAt: 2024-02-16T20:27:57.698Z
+publishedAt: 2024-02-16T20:27:57.698Z
 firstPublishedAt: 2022-05-12T14:52:18.968Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: os-artigos-de-presente-lancam-uma-excecao-generica-se-nao-tiver-preco
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 510490
 ---
 
diff --git a/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md b/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
index 0a28cd037..947ac73f0 100644
--- a/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
+++ b/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
@@ -3,8 +3,8 @@ title: 'Promoções de presentes que não funcionam como esperado quando atuam e
 id: 7p037qcaXYMYKC3kJPztc3
 status: PUBLISHED
 createdAt: 2023-01-09T21:08:49.800Z
-updatedAt: 2023-01-09T21:08:50.899Z
-publishedAt: 2023-01-09T21:08:50.899Z
+updatedAt: 2024-02-16T20:23:54.228Z
+publishedAt: 2024-02-16T20:23:54.228Z
 firstPublishedAt: 2023-01-09T21:08:50.899Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: promocoes-de-presentes-que-nao-funcionam-como-esperado-quando-atuam-em-conjunto-com-outras-promocoes-de-presentes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 729980
 ---
 
diff --git a/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md b/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
index dca8c1fce..643d890ed 100644
--- a/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
+++ b/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
@@ -3,8 +3,8 @@ title: 'A configuração do Giftcard Recarregável não funciona quando se tenta
 id: 3MXPd85Km51KpO4FNPqlDf
 status: PUBLISHED
 createdAt: 2022-05-23T14:21:10.608Z
-updatedAt: 2022-11-25T22:05:59.003Z
-publishedAt: 2022-11-25T22:05:59.003Z
+updatedAt: 2024-02-16T20:25:54.496Z
+publishedAt: 2024-02-16T20:25:54.496Z
 firstPublishedAt: 2022-05-23T14:21:11.126Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: a-configuracao-do-giftcard-recarregavel-nao-funciona-quando-se-tenta-adicionar-credito-ao-cartao-presente-atraves-de-api
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 583669
 ---
 
diff --git a/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md b/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
index 7e3da909f..ad5005ac8 100644
--- a/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
+++ b/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
@@ -3,8 +3,8 @@ title: '[Giftlist] Data de evento salva na UI não é a mesma que reflete no bd'
 id: 6PUBzRdtno8ypsPMg97B6K
 status: PUBLISHED
 createdAt: 2022-07-25T17:45:12.568Z
-updatedAt: 2022-11-25T21:42:07.374Z
-publishedAt: 2022-11-25T21:42:07.374Z
+updatedAt: 2024-02-16T20:28:47.100Z
+publishedAt: 2024-02-16T20:28:47.100Z
 firstPublishedAt: 2022-07-25T17:45:13.009Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 402134
 ---
 
diff --git a/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md b/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md
index fa1b38be6..640fc737e 100644
--- a/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md
+++ b/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md
@@ -3,8 +3,8 @@ title: 'Categorias globais em catálogo desatualizadas em comparação com o Goo
 id: 4vH5NRdMsuZmOohdHFn16H
 status: PUBLISHED
 createdAt: 2023-02-14T19:42:08.121Z
-updatedAt: 2023-02-14T19:42:08.712Z
-publishedAt: 2023-02-14T19:42:08.712Z
+updatedAt: 2024-07-01T18:48:52.824Z
+publishedAt: 2024-07-01T18:48:52.824Z
 firstPublishedAt: 2023-02-14T19:42:08.712Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: categorias-globais-em-catalogo-desatualizadas-em-comparacao-com-o-google
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 754062
 ---
 
diff --git a/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md b/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
new file mode 100644
index 000000000..b0f66b6d7
--- /dev/null
+++ b/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
@@ -0,0 +1,44 @@
+---
+title: 'O iframe do componente Avaliações de clientes do Google tem renderização inconsistente'
+id: 7BDB9yYv3ZHbhE4ExCXgZK
+status: PUBLISHED
+createdAt: 2023-12-22T17:55:39.082Z
+updatedAt: 2024-02-16T20:25:48.248Z
+publishedAt: 2024-02-16T20:25:48.248Z
+firstPublishedAt: 2023-12-22T17:55:39.764Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-iframe-do-componente-avaliacoes-de-clientes-do-google-tem-renderizacao-inconsistente
+locale: pt
+kiStatus: No Fix
+internalReference: 578443
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O iframe, responsável pelo emblema do Google Customer Review, tem renderização inconsistente dentro do elemento div do componente Google Customer Reviews.
+
+Avaliações de clientes do Google:
+https://developers.vtex.com/vtex-developer-docs/docs/vtex-google-customer-reviews
+
+## Simulação
+
+
+Em uma conta que usa o componente Google Customer Reviews, abrindo a guia Element (Elemento) no inspetor do navegador, é possível ver sempre a div do Google Customer Review, mas, às vezes, o elemento está vazio, sem o iframe do Google
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md b/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
index 599b52c89..cad3daa14 100644
--- a/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
+++ b/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
@@ -3,8 +3,8 @@ title: ' Método de entrega por grupo no desempenho de vendas não funciona como
 id: 8zHND5pzrt0mrIrb061Zq
 status: PUBLISHED
 createdAt: 2022-11-30T19:02:13.548Z
-updatedAt: 2022-12-01T22:14:52.118Z
-publishedAt: 2022-12-01T22:14:52.118Z
+updatedAt: 2024-02-16T20:25:12.853Z
+publishedAt: 2024-02-16T20:25:12.853Z
 firstPublishedAt: 2022-11-30T19:02:13.994Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: metodo-de-entrega-por-grupo-no-desempenho-de-vendas-nao-funciona-como-esperado
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 639294
 ---
 
diff --git a/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md b/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md
new file mode 100644
index 000000000..040310af3
--- /dev/null
+++ b/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md
@@ -0,0 +1,48 @@
+---
+title: 'O Headless CMS ignora as configurações de validação de matriz'
+id: 1szfagZFJHmevSWDTyd45e
+status: PUBLISHED
+createdAt: 2024-06-07T14:22:41.366Z
+updatedAt: 2024-06-07T14:22:41.992Z
+publishedAt: 2024-06-07T14:22:41.992Z
+firstPublishedAt: 2024-06-07T14:22:41.992Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: o-headless-cms-ignora-as-configuracoes-de-validacao-de-matriz
+locale: pt
+kiStatus: Backlog
+internalReference: 1046372
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar configurar regras de validação de matriz no CMS Headless, como itens de matriz mínimos e máximos, os erros de validação não são mostrados ao usuário e é possível salvar o esquema sem passar pela validação.
+
+O cenário esperado seria bloquear a tela e mostrar uma mensagem como:
+
+    "keyword": "minItems", "message": "NÃO deve ter menos de 3 itens",
+
+
+## Simulação
+
+
+Tente adicionar uma seção que tenha uma regra de validação. Se você não respeitar a validação, o hCMS permitirá que você publique o conteúdo normalmente.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md b/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
new file mode 100644
index 000000000..f18396704
--- /dev/null
+++ b/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
@@ -0,0 +1,47 @@
+---
+title: 'O formato de imagem como JPG ou PNG não funciona no catálogo do portal do vendedor'
+id: 19s9bGcpNsOkIkA0iGkWRi
+status: PUBLISHED
+createdAt: 2024-04-22T12:41:43.272Z
+updatedAt: 2024-04-22T12:41:44.252Z
+publishedAt: 2024-04-22T12:41:44.252Z
+firstPublishedAt: 2024-04-22T12:41:44.252Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-formato-de-imagem-como-jpg-ou-png-nao-funciona-no-catalogo-do-portal-do-vendedor
+locale: pt
+kiStatus: Backlog
+internalReference: 1020505
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar criar um produto com um formato de imagem definido como JPG ou PNG, o produto é criado com uma imagem quebrada. Esse comportamento não ocorre se o formato for definido como jpg ou png (sem capslock).
+
+## Simulação
+
+
+
+1. Crie um produto em uma conta do portal do vendedor
+2. Importar uma imagem com formato JPG ou PNG
+3. Salvar o produto
+4. Verifique se a imagem está quebrada na interface do usuário se você abrir o produto criado.
+
+
+
+## Workaround
+
+
+Importe imagens com formato jpg ou png (letras minúsculas).
+
+
+
+
+
diff --git a/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md b/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md
new file mode 100644
index 000000000..a29ae402c
--- /dev/null
+++ b/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md
@@ -0,0 +1,46 @@
+---
+title: 'A falsificação de identidade é ignorada após a conclusão de uma compra'
+id: 4mHKOlwaLwfIEf8HFh4y4Y
+status: PUBLISHED
+createdAt: 2024-03-20T20:10:26.200Z
+updatedAt: 2024-03-20T20:10:27.029Z
+publishedAt: 2024-03-20T20:10:27.029Z
+firstPublishedAt: 2024-03-20T20:10:27.029Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-falsificacao-de-identidade-e-ignorada-apos-a-conclusao-de-uma-compra
+locale: pt
+kiStatus: Backlog
+internalReference: 1003545
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um operador de call center se faz passar por um comprador, conclui uma compra e é enviado para a página orderPlaced, um novo orderForm será gerado.
+
+Esse novo orderForm terá seu anexo clientProfileData com o e-mail do operador da central de atendimento em vez do comprador personificado, embora os dados de personificação sejam mantidos normalmente na sessão.
+
+## Simulação
+
+
+
+1. Faça login no ambiente myvtex como um operador de call center.
+2. Faça-se passar por um comprador e conclua uma compra.
+3. Depois disso, enquanto ainda estiver se passando pelo usuário, inicie uma nova compra e observe como os dados do carrinho conterão o e-mail do operador da central de atendimento em clientProfileData
+
+## Workaround
+
+
+Se você precisar criar mais de um pedido para o mesmo comprador, certifique-se de refazer o processo de personificação entre os pedidos.
+
+
+
+
+
diff --git a/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md b/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
new file mode 100644
index 000000000..cd4f0b142
--- /dev/null
+++ b/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
@@ -0,0 +1,42 @@
+---
+title: 'Widget de usuário de personificação não exibido se showModal estiver ativado'
+id: 19IHgjxPOEFC6HsAc5FD96
+status: PUBLISHED
+createdAt: 2024-06-03T15:55:49.797Z
+updatedAt: 2024-06-03T15:55:50.539Z
+publishedAt: 2024-06-03T15:55:50.539Z
+firstPublishedAt: 2024-06-03T15:55:50.539Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: widget-de-usuario-de-personificacao-nao-exibido-se-showmodal-estiver-ativado
+locale: pt
+kiStatus: Backlog
+internalReference: 1043039
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Após a representação de outro e-mail, espera-se que seja exibido um botão "Stop Impersonation", mas quando o `showModal` está ativado, ele não é exibido.
+
+## Simulação
+
+
+
+- Ative "Use modal to switch company" (Usar modal para mudar de empresa) nas configurações de organizações B2B;
+- Faça login e passe-se por outro e-mail
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
new file mode 100644
index 000000000..dea1156ac
--- /dev/null
+++ b/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -0,0 +1,47 @@
+---
+title: 'A coleção de importação só aceita a ordem dos produtos se a importação for feita com base no "skuId"'
+id: 7vXi2bDVyGHSMLluQi2ZWZ
+status: PUBLISHED
+createdAt: 2023-12-15T16:35:11.545Z
+updatedAt: 2023-12-21T18:55:17.090Z
+publishedAt: 2023-12-21T18:55:17.090Z
+firstPublishedAt: 2023-12-15T16:35:12.450Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-colecao-de-importacao-so-aceita-a-ordem-dos-produtos-se-a-importacao-for-feita-com-base-no-skuid
+locale: pt
+kiStatus: Fixed
+internalReference: 953862
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao importar uma planilha de produtos para uma coleção, o usuário pode optar por selecionar os produtos por "skuId", "productId", "skuRefId" ou "productRefId".
+
+No entanto, a ordem dos produtos na coleção só está sendo respeitada quando a planilha está usando "skuId".
+
+## Simulação
+
+
+
+1. Crie uma nova coleção;
+2. Use a planilha de importação para adicionar produtos;
+3. Escolha um campo diferente de "skuId" para preencher a planilha;
+4. Verifique se a ordem dos produtos nas coleções é diferente da ordem na planilha
+
+## Workaround
+
+
+Use a coluna "skuId" para preencher a planilha.
+
+
+
+
+
diff --git a/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md b/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
new file mode 100644
index 000000000..cd58a3310
--- /dev/null
+++ b/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
@@ -0,0 +1,43 @@
+---
+title: 'Em alguns casos em que há um desconto no pedido, temos uma discrepância no valor total do campo Itens para fatura na interface do usuário do pedido.'
+id: 20xiOKxpvdCODmDJDKunST
+status: PUBLISHED
+createdAt: 2024-05-06T20:17:01.162Z
+updatedAt: 2024-05-06T20:17:01.968Z
+publishedAt: 2024-05-06T20:17:01.968Z
+firstPublishedAt: 2024-05-06T20:17:01.968Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: em-alguns-casos-em-que-ha-um-desconto-no-pedido-temos-uma-discrepancia-no-valor-total-do-campo-itens-para-fatura-na-interface-do-usuario-do-pedido
+locale: pt
+kiStatus: Backlog
+internalReference: 1028210
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Foi identificado que, em alguns pedidos em que há um desconto associado a um ou mais itens, podemos ter uma discrepância no valor total do campo "itens a faturar" na interface do usuário do pedido, pois o cálculo desse campo leva em conta o parâmetro "sellingPrice", em vez do parâmetro "priceDefinitions". Portanto, é possível notar diferenças de 0,01 ou um pouco mais no valor total do pedido.
+
+Ressaltamos que esse campo é ilustrativo, pois o campo principal é o valor total (montante) do pedido e NÃO há discrepância nesse campo.
+
+## Simulação
+
+
+Não é possível simular esse cenário
+
+## Workaround
+
+
+Não seria um workaround, apenas uma dica para faturar o pedido com o valor total, informado no campo "amount", ou no caso de faturas parciais, informar o valor do(s) item(ns).
+
+
+
+
+
diff --git a/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md b/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
index 1951bfebe..2bb6dccbd 100644
--- a/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
+++ b/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
@@ -3,8 +3,8 @@ title: 'No retorno parcial, os valores do Imposto na IU aparecem o total'
 id: 2I5a9hwrUo6s1htxOg8H1U
 status: PUBLISHED
 createdAt: 2022-04-11T13:15:06.455Z
-updatedAt: 2022-11-25T22:03:40.667Z
-publishedAt: 2022-11-25T22:03:40.667Z
+updatedAt: 2024-02-16T20:28:35.114Z
+publishedAt: 2024-02-16T20:28:35.114Z
 firstPublishedAt: 2022-04-11T13:15:07.028Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: no-retorno-parcial-os-valores-do-imposto-na-iu-aparecem-o-total
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 559458
 ---
 
diff --git a/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md b/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md
index 46151743c..c5300422b 100644
--- a/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md
+++ b/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md
@@ -3,8 +3,8 @@ title: 'Incapacidade de fazer cancelamento parcial com MercadoPagoV1'
 id: 59aimeqhjGVOVkP9f6A9ls
 status: PUBLISHED
 createdAt: 2022-06-28T16:44:19.059Z
-updatedAt: 2022-11-25T22:06:36.432Z
-publishedAt: 2022-11-25T22:06:36.432Z
+updatedAt: 2024-02-16T20:30:01.307Z
+publishedAt: 2024-02-16T20:30:01.307Z
 firstPublishedAt: 2022-06-28T16:44:19.331Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: incapacidade-de-fazer-cancelamento-parcial-com-mercadopagov1
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 286738
 ---
 
diff --git a/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md b/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
index 82f867713..31f4095d6 100644
--- a/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
+++ b/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
@@ -3,8 +3,8 @@ title: 'Impossibilidade de usar duas ou mais credenciais diferentes do PayPal pa
 id: 3cVh2SbvToH8yGOOYcWgDB
 status: PUBLISHED
 createdAt: 2022-03-03T18:39:24.442Z
-updatedAt: 2022-11-25T22:05:45.390Z
-publishedAt: 2022-11-25T22:05:45.390Z
+updatedAt: 2024-02-16T20:25:01.876Z
+publishedAt: 2024-02-16T20:25:01.876Z
 firstPublishedAt: 2022-03-03T18:39:25.004Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: impossibilidade-de-usar-duas-ou-mais-credenciais-diferentes-do-paypal-para-a-mesma-conta
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 459704
 ---
 
@@ -23,21 +23,20 @@ internalReference: 459704
 </div>
 
 
-Quando o cliente registra duas afiliações diferentes na mesma conta usando PayPalPlus, a plataforma não atualiza o cache para quando há uma mudança na regra de pagamento, ou seja, é possível usar apenas uma credencial por conta.
-
+Quando o usuário registra duas afiliações diferentes na mesma conta usando o PayPalPlus, a plataforma não atualiza o cache para quando houver uma alteração em uma regra de pagamento, ou seja, é possível usar apenas uma credencial por conta.
 
+## Simulação
 
 
-## Simulação
+Registre duas afiliações diferentes com credenciais diferentes e crie regras considerando essas duas afiliações.
+Feche duas compras, cada uma com uma das regras, e no payload da transação você pode ver que, apesar de inserir as regras corretas, o merchant_id (identificação da conta na qual o dinheiro cairá) é o mesmo
 
+## Workaround
 
-Registre duas filiações diferentes com credenciais diferentes e crie regras considerando estas duas filiações.
-Feche duas compras, cada uma com uma das regras, e na carga útil da transação você pode ver que apesar de entrar com as regras corretas, o merchant_id (identificação da conta na qual o dinheiro cairá) é o mesmo.
 
+N/A
 
 
-## Workaround
 
 
-Não há solução
 
diff --git a/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md b/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md
new file mode 100644
index 000000000..11dd8acdb
--- /dev/null
+++ b/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md
@@ -0,0 +1,43 @@
+---
+title: 'Transações incompletas que aparecem com a moeda brasileira'
+id: 7g0j3FGa5E8kNi9PM3kBOf
+status: PUBLISHED
+createdAt: 2024-04-01T13:37:35.197Z
+updatedAt: 2024-04-01T13:37:36.114Z
+publishedAt: 2024-04-01T13:37:36.114Z
+firstPublishedAt: 2024-04-01T13:37:36.114Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transacoes-incompletas-que-aparecem-com-a-moeda-brasileira
+locale: pt
+kiStatus: Backlog
+internalReference: 1007953
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Transações incompletas (cliente "Sem nome") podem aparecer na seção Transações com a moeda R$, resultado de um erro de criação (os dados de pagamento não foram enviados), mas os pedidos são criados corretamente na moeda local.
+
+Como essas transações já foram perdidas, não há impacto operacional (bug visual).
+
+## Simulação
+
+
+Ao concluir um pagamento no checkout, você pode recarregar a página para "interromper" o processo e verificar na interface do usuário se a criação completa da transação falhou (procurando por "No name")
+
+## Workaround
+
+
+NA
+
+
+
+
+
diff --git a/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md b/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
new file mode 100644
index 000000000..0d0250e3c
--- /dev/null
+++ b/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
@@ -0,0 +1,43 @@
+---
+title: 'Informações inconsistentes sobre as condições de pagamento entre os detalhes do centro de custo em Minha organização e as configurações de checkout B2B'
+id: VB70gSEsPOdTHVi3SPMaB
+status: PUBLISHED
+createdAt: 2023-06-20T18:29:30.859Z
+updatedAt: 2023-07-17T14:34:00.520Z
+publishedAt: 2023-07-17T14:34:00.520Z
+firstPublishedAt: 2023-06-20T18:29:31.475Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: informacoes-inconsistentes-sobre-as-condicoes-de-pagamento-entre-os-detalhes-do-centro-de-custo-em-minha-organizacao-e-as-configuracoes-de-checkout-b2b
+locale: pt
+kiStatus: Fixed
+internalReference: 847340
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Informações inconsistentes entre os detalhes do centro de custo em Minha organização e as configurações de checkout B2B, em que Minha organização mostra uma condição de pagamento desativada, mas a condição de pagamento ainda é mostrada ao acessar o checkout.
+
+## Simulação
+
+
+
+- Acesse My Organization (Minha organização) em My Account (Minha conta) com a função "Organization Admin" (Administrador da organização);
+- Clique no centro de custos;
+- Na seção "Payment Terms" (Condições de pagamento), desative uma condição de pagamento;
+- Acesse o checkout e vá para Payment (Pagamento); a opção desativada ainda está disponível
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md b/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
index 9589da433..4e8337a45 100644
--- a/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
+++ b/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
@@ -1,16 +1,16 @@
 ---
-title: 'Preço inconsistente quando a SKU tem multiplicador de unidade diferente de 1'
+title: 'Preço inconsistente quando a SKU tem um multiplicador de unidades diferente de 1'
 id: NVtFiuWgptqa2gBEVmpOC
 status: PUBLISHED
 createdAt: 2022-09-05T13:05:50.789Z
-updatedAt: 2023-02-27T14:22:04.935Z
-publishedAt: 2023-02-27T14:22:04.935Z
+updatedAt: 2024-02-02T16:50:00.987Z
+publishedAt: 2024-02-02T16:50:00.987Z
 firstPublishedAt: 2022-09-05T13:05:51.613Z
 contentType: knownIssue
 productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
-slug: preco-inconsistente-quando-a-sku-tem-multiplicador-de-unidade-diferente-de-1
+slug: preco-inconsistente-quando-a-sku-tem-um-multiplicador-de-unidades-diferente-de-1
 locale: pt
 kiStatus: Backlog
 internalReference: 651102
@@ -23,22 +23,25 @@ internalReference: 651102
 </div>
 
 
-Quando alguns SKU contêm um multiplicador de unidade diferente de 1, em algumas situações, o preço devolvido no store-graphql pode ter inconsistências com base na divisão do preço devolvido da API de simulação:
+Quando alguma SKU contém um multiplicador de unidade diferente de 1 (pode ser int como 10 ou 100, ou float como 0,8, por exemplo), em algumas situações, o preço retornado no store-graphql pode ter inconsistências com base na divisão do preço retornado da API de simulação:
 
-calculadoPreço de venda / (unidadeMultiplicador * 100)
+calculatedSellingPrice / (unitMultiplier * 100)
 
-Também se aplica a valores em parcelas que não consideram valor multiplicador de unidade e a chamada de simulação envia o valor com o multiplicador de unidade sendo considerado
+Isso pode se aplicar a todos os valores de preço que usam o multiplicador unitário, como em parcelas (que não consideram o valor do multiplicador unitário e a chamada de simulação envia o valor com o multiplicador unitário sendo considerado), preço PDP, preço PLP ou carrinho.
 
-Baseado em:
-https://vtexhelp.zendesk.com/agent/tickets/578022
+## Simulação
 
 
+Verificar a simulação chamada para um produto com um multiplicador de unidade
+Verifique o preço do produto em uma página de pesquisa ou usando uma consulta de pesquisa de produto do search-graphql
+Os preços podem ser divergentes em centavo
 
-## Simulação
+## Workaround
 
 
+N/A
+
 
-## Workaround
 
 
 
diff --git a/docs/known-issues/pt/inconsistent-shipping-calculator.md b/docs/known-issues/pt/inconsistent-shipping-calculator.md
index 21d128a0e..e20f7781e 100644
--- a/docs/known-issues/pt/inconsistent-shipping-calculator.md
+++ b/docs/known-issues/pt/inconsistent-shipping-calculator.md
@@ -24,7 +24,7 @@ Nestes casos, o calculador de frete tem comportamento inconsistente, exibindo do
 
 Isso acontece somente na versão 5 do checkout.
 
-![image](https://images.ctfassets.net/alneenqid6w5/5jaAAeUm9q4c4oy6GcYeO6/c08fe588cedc9d9a30453985a1589df9/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/5jaAAeUm9q4c4oy6GcYeO6/c08fe588cedc9d9a30453985a1589df9/image.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/incorrect-currency-on-payment-form.md b/docs/known-issues/pt/incorrect-currency-on-payment-form.md
index 7a8dcbb56..4d2995532 100644
--- a/docs/known-issues/pt/incorrect-currency-on-payment-form.md
+++ b/docs/known-issues/pt/incorrect-currency-on-payment-form.md
@@ -3,8 +3,8 @@ title: 'Moeda incorreta no formulário de pagamento'
 id: 636reFJs0MeHQJO0NlQV7Z
 status: PUBLISHED
 createdAt: 2022-03-13T21:29:33.920Z
-updatedAt: 2022-11-25T22:05:48.750Z
-publishedAt: 2022-11-25T22:05:48.750Z
+updatedAt: 2024-02-16T20:27:07.481Z
+publishedAt: 2024-02-16T20:27:07.481Z
 firstPublishedAt: 2022-03-13T21:29:34.493Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: moeda-incorreta-no-formulario-de-pagamento
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 449286
 ---
 
diff --git a/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md b/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
new file mode 100644
index 000000000..36f64092e
--- /dev/null
+++ b/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
@@ -0,0 +1,39 @@
+---
+title: 'Atualização incorreta do preço quando uma promoção não aplica o desconto a todos os mesmos itens em um carrinho'
+id: 1nXGR7pKjyc0Rmo0UzMOns
+status: PUBLISHED
+createdAt: 2024-05-01T20:07:04.369Z
+updatedAt: 2024-05-01T20:07:16.339Z
+publishedAt: 2024-05-01T20:07:16.339Z
+firstPublishedAt: 2024-05-01T20:07:05.363Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: atualizacao-incorreta-do-preco-quando-uma-promocao-nao-aplica-o-desconto-a-todos-os-mesmos-itens-em-um-carrinho
+locale: pt
+kiStatus: Backlog
+internalReference: 1025539
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma promoção aplica um desconto a apenas um item da mesma SKU (por exemplo, uma promoção Mais por Menos), se houver uma segunda promoção para essa mesma SKU, o cálculo do desconto será aplicado ao valor já descontado pela primeira promoção, resultando em um desconto menor do que o que seria concedido se a segunda promoção fosse aplicada ao preço inicial da SKU.
+
+O problema ocorre na atualização de preços quando uma promoção não aplica o desconto a todos os mesmos itens em um carrinho e isso causa uma "divisão" (dois itens iguais com preços diferentes). Quando a segunda promoção é aplicada, ela é aplicada ao preço errado.
+
+O erro não ocorre por causa de uma promoção específica.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
new file mode 100644
index 000000000..19d7890d2
--- /dev/null
+++ b/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -0,0 +1,50 @@
+---
+title: 'Cálculo incorreto de reembolso na divisão de pagamentos - "O valor nos destinatários * é diferente do valor da operação *."'
+id: 7Fxtwnntpmi0DrUD5a603W
+status: PUBLISHED
+createdAt: 2024-07-29T15:07:07.716Z
+updatedAt: 2024-07-29T15:07:12.565Z
+publishedAt: 2024-07-29T15:07:12.565Z
+firstPublishedAt: 2024-07-29T15:07:12.565Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: calculo-incorreto-de-reembolso-na-divisao-de-pagamentos-o-valor-nos-destinatarios-e-diferente-do-valor-da-operacao
+locale: pt
+kiStatus: Backlog
+internalReference: 1072285
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao chamar um reembolso (em transações com divisão de pagamento), o erro abaixo pode ocorrer com valores divergentes:
+
+(Exemplo)
+
+    Vtex.Practices.ExceptionHandling.ValidationException: O valor nos destinatários (45,00) é diferente do valor da operação (299,99). at Vtex.PaymentGateway.PaymentSplit.RecipientsBuilder.ValidateRecipientsValue(List`1 recipients, Decimal value)...
+
+
+Observe que esse KI é diferente do abaixo (problema de cálculo relacionado ao arredondamento - a diferença de valores é pequena):
+
+https://help.vtex.com/en/known-issues/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value--3Wo9ltN7Ju0ZqVLAQZcd7m
+
+## Simulação
+
+
+Isso parece acontecer quando o carrinho não tem produtos do marketplace, mas não conseguimos simular esse erro
+
+## Workaround
+
+
+NA, os comerciantes precisam solicitar o reembolso manual diretamente com o adquirente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md b/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md
index 82fb875c1..73cadfe33 100644
--- a/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md
+++ b/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md
@@ -3,8 +3,8 @@ title: 'Envio incorretoData de EnvioEstimativa para pedido FOB'
 id: 3WLcrdw0tEdOvlMCYx9uyd
 status: PUBLISHED
 createdAt: 2023-01-05T20:26:07.074Z
-updatedAt: 2023-01-05T20:26:07.500Z
-publishedAt: 2023-01-05T20:26:07.500Z
+updatedAt: 2024-02-16T20:23:32.848Z
+publishedAt: 2024-02-16T20:23:32.848Z
 firstPublishedAt: 2023-01-05T20:26:07.500Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: envio-incorretodata-de-envioestimativa-para-pedido-fob
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 269104
 ---
 
diff --git a/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md b/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
new file mode 100644
index 000000000..3701543fa
--- /dev/null
+++ b/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
@@ -0,0 +1,46 @@
+---
+title: 'Indexações incorretas/faltas para contas em que o nome da conta é diferente do registrado no fulfillmentEndpoint'
+id: 3TPRChOVHGpOYVeVo4zGOK
+status: PUBLISHED
+createdAt: 2024-06-14T16:45:39.257Z
+updatedAt: 2024-07-09T16:49:07.942Z
+publishedAt: 2024-07-09T16:49:07.942Z
+firstPublishedAt: 2024-06-14T16:45:40.852Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: indexacoes-incorretasfaltas-para-contas-em-que-o-nome-da-conta-e-diferente-do-registrado-no-fulfillmentendpoint
+locale: pt
+kiStatus: Backlog
+internalReference: 1050023
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, uma conta de franquia pode ter seu registro fulFillmentEndpoint diferente de seu nome de conta "oficial", o que é uma prática comum para arquiteturas específicas de vendedor<>marketplace que precisam de vários preços e/ou estoque para canais de vendas distintos usando o recurso de franquia com vários vendedores para a mesma franquia.
+
+Embora esse recurso funcione em termos de exibição do conteúdo necessário para os compradores, quando os dados relevantes para as vendas, como preço/estoque, são atualizados para o vendedor principal de uma determinada franquia, as outras contas associadas não são indexadas corretamente, gerando disponibilidade e exibições de preços inconsistentes entre os canais de venda de uma loja.
+
+## Simulação
+
+
+
+- Para uma loja que tenha vários vendedores e mais de uma conta de franquia, configure mais de dois vendedores apontando, no fulfillmentendpoint, para a mesma conta de franquia em suas configurações de vendedor.
+- Tente atualizar os dados de preço/estoque de qualquer item da conta de franquia.
+- Verifique os dados atualizados nos outros vendedores associados que usam a conta de franquia em seus pontos de extremidade do FFM; eles estarão desatualizados
+
+## Workaround
+
+
+Em vez disso, use o recurso salesChannelMapping para implementar essa arquitetura
+
+
+
+
+
diff --git a/docs/known-issues/pt/incorrectly-updated-inventory.md b/docs/known-issues/pt/incorrectly-updated-inventory.md
index ce796e3cd..3408beb29 100644
--- a/docs/known-issues/pt/incorrectly-updated-inventory.md
+++ b/docs/known-issues/pt/incorrectly-updated-inventory.md
@@ -3,8 +3,8 @@ title: 'Inventário incorretamente atualizado'
 id: 2M8DqNY1pGQWZnF9ZXNycq
 status: PUBLISHED
 createdAt: 2022-05-03T12:32:14.192Z
-updatedAt: 2022-11-25T21:56:29.965Z
-publishedAt: 2022-11-25T21:56:29.965Z
+updatedAt: 2024-02-16T20:24:24.243Z
+publishedAt: 2024-02-16T20:24:24.243Z
 firstPublishedAt: 2022-05-03T12:32:14.713Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: inventario-incorretamente-atualizado
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 556514
 ---
 
diff --git a/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md b/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
index 148f63698..f8741b1eb 100644
--- a/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
+++ b/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
@@ -3,8 +3,8 @@ title: 'Preço indexado para um produto considerando a SKU com o preço mais alt
 id: 333mavl9dvgO4Jrgv8ECE6
 status: PUBLISHED
 createdAt: 2023-05-09T14:39:56.338Z
-updatedAt: 2023-05-09T14:39:56.771Z
-publishedAt: 2023-05-09T14:39:56.771Z
+updatedAt: 2023-08-18T17:24:09.314Z
+publishedAt: 2023-08-18T17:24:09.314Z
 firstPublishedAt: 2023-05-09T14:39:56.771Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: preco-indexado-para-um-produto-considerando-a-sku-com-o-preco-mais-alto-em-vez-do-mais-baixo
 locale: pt
-kiStatus: Scheduled
+kiStatus: Fixed
 internalReference: 822120
 ---
 
diff --git a/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md b/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
index 9c2f4f8af..1b49771ab 100644
--- a/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
+++ b/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
@@ -3,8 +3,8 @@ title: 'As exportações de estoques individuais (inventários) não funcionam n
 id: 7GoxwXFUWnebmCqF1sm7rm
 status: PUBLISHED
 createdAt: 2022-10-24T19:21:06.182Z
-updatedAt: 2022-11-25T21:43:01.961Z
-publishedAt: 2022-11-25T21:43:01.961Z
+updatedAt: 2024-07-01T18:48:39.414Z
+publishedAt: 2024-07-01T18:48:39.414Z
 firstPublishedAt: 2022-10-24T19:21:06.574Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: as-exportacoes-de-estoques-individuais-inventarios-nao-funcionam-nas-contas-do-seller-portal
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 684464
 ---
 
diff --git a/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md b/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
new file mode 100644
index 000000000..57c2f3bbd
--- /dev/null
+++ b/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
@@ -0,0 +1,50 @@
+---
+title: 'O Inference Invoice System não está funcionando corretamente quando há o mesmo SKUid em diferentes itens de matriz'
+id: 3fSQGwIPj0ekewMuaxPPEe
+status: PUBLISHED
+createdAt: 2024-03-28T19:00:12.852Z
+updatedAt: 2024-04-04T13:33:04.775Z
+publishedAt: 2024-04-04T13:33:04.775Z
+firstPublishedAt: 2024-03-28T19:00:14.053Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-inference-invoice-system-nao-esta-funcionando-corretamente-quando-ha-o-mesmo-skuid-em-diferentes-itens-de-matriz
+locale: pt
+kiStatus: Backlog
+internalReference: 1008459
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns pedidos têm o mesmo SKUid em uma matriz separada de itens, o que acontece no momento da compra no checkout por diferentes motivos, como desconto a ser aplicado, por exemplo.
+Isso não é um problema, mas uma condição para um cálculo de compra.
+
+O problema está na fase da fatura para esses itens. Às vezes, o sistema de inferência não consegue fazer a correspondência correta dos itens a serem inseridos nos itens de referência no packageAttachment, devido ao mesmo SKUid e preços de venda.
+Mesmo que o cliente envie a quantidade de itens corretamente, a inferência estará errada.
+
+É possível ver a diferença no sistema SNO versus os itens do packageAttachment no pedido.
+
+## Simulação
+
+
+Crie um pedido com mais de uma quantidade de itens e aplique algum desconto, criando um pedido com mais de uma matriz de itens com preços de venda diferentes. Depois disso, tente faturar todos os itens do pedido.
+
+
+
+
+## Workaround
+
+
+Não há solução alternativa para isso.
+
+
+
+
+
diff --git a/docs/known-issues/pt/infocard-mobile-images-wont-apply.md b/docs/known-issues/pt/infocard-mobile-images-wont-apply.md
new file mode 100644
index 000000000..f8dc83bee
--- /dev/null
+++ b/docs/known-issues/pt/infocard-mobile-images-wont-apply.md
@@ -0,0 +1,47 @@
+---
+title: 'As imagens do Infocard para celular não serão aplicadas'
+id: 1vx5fwa5nL3SO27HpihLFd
+status: PUBLISHED
+createdAt: 2024-02-19T19:12:18.516Z
+updatedAt: 2024-02-19T19:12:19.362Z
+publishedAt: 2024-02-19T19:12:19.362Z
+firstPublishedAt: 2024-02-19T19:12:19.362Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: as-imagens-do-infocard-para-celular-nao-serao-aplicadas
+locale: pt
+kiStatus: Backlog
+internalReference: 909647
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando você altera a imagem em um infocard para ser exibida na versão móvel, ela não será exibida. Em vez disso, a imagem principal continua sendo exibida.
+
+## Simulação
+
+
+
+- Abra um infocard no site-editor para edição.
+- Altere a imagem principal do infocard e aplique.
+- Altere a imagem da versão móvel do infocard e aplique.
+- Observe os resultados: a imagem continuará sendo a imagem principal em vez da imagem definida para celular quando estiver no modo móvel.
+
+
+
+## Workaround
+
+
+Em vez disso, tente usar um layout flexível com uma imagem de loja + outros aplicativos para criar o banner desejado.
+
+
+
+
+
diff --git a/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
new file mode 100644
index 000000000..a7f666c33
--- /dev/null
+++ b/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -0,0 +1,47 @@
+---
+title: 'A API Insert SKU File não aceita URLs de servidores que exigem "User Agents"'
+id: 5Z1PmRXyW78mohsKTMQfzj
+status: PUBLISHED
+createdAt: 2024-07-22T19:49:14.140Z
+updatedAt: 2024-07-22T19:49:15.319Z
+publishedAt: 2024-07-22T19:49:15.319Z
+firstPublishedAt: 2024-07-22T19:49:15.319Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-api-insert-sku-file-nao-aceita-urls-de-servidores-que-exigem-user-agents
+locale: pt
+kiStatus: Backlog
+internalReference: 1069222
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Um **agente de usuário** é uma sequência de texto que um navegador da Web ou outro cliente envia a um servidor da Web em um cabeçalho de solicitação HTTP para se identificar. Essa cadeia contém informações sobre o tipo de navegador, o sistema operacional e, às vezes, detalhes adicionais, como a versão do navegador e o mecanismo de renderização usado.
+
+Isso geralmente é solicitado como medida de segurança por servidores, como os que hospedam imagens, que podem ser passadas via URL no corpo da solicitação da API de inserção de arquivo SKU.
+
+Esse tipo de autenticação, no entanto, não é suportado atualmente pelas APIs da VTEX.
+
+## Simulação
+
+
+1 - Usando a API de arquivo SKU Create ou Update (métodos de gravação), transmitindo um URL que tem o requisito de agente de usuário do lado do servidor para buscar dados https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file
+
+2 - Uma resposta do tipo 40x será mostrada, seja um 400 genérico ou um 403 mais específico, dependendo do tipo de resposta implementada.
+
+## Workaround
+
+
+Opte pelo upload de arquivos, planilhas e dados de formulário (usando as APIs) ou desative os requisitos de agente de usuário no lado do servidor.
+
+
+
+
+
diff --git a/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md b/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md
new file mode 100644
index 000000000..cf65f4032
--- /dev/null
+++ b/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md
@@ -0,0 +1,46 @@
+---
+title: 'As opções de parcelamento não são atualizadas automaticamente no PDP/PLP'
+id: 1PSjCEZyKatCZ9Q1W1zQOc
+status: PUBLISHED
+createdAt: 2024-02-23T12:31:32.446Z
+updatedAt: 2024-02-23T12:31:33.262Z
+publishedAt: 2024-02-23T12:31:33.262Z
+firstPublishedAt: 2024-02-23T12:31:33.262Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-opcoes-de-parcelamento-nao-sao-atualizadas-automaticamente-no-pdpplp
+locale: pt
+kiStatus: Backlog
+internalReference: 987467
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma conta altera as opções de parcelamento de um produto, apesar de o produto estar corretamente indexado, as opções de parcelamento não são atualizadas no PLP ou no PDP (às vezes em ambos).
+
+## Simulação
+
+
+
+1. Crie uma opção de parcelamento e verifique se ela se reflete corretamente no PDP/PLP
+2. Atualize essa mesma parcela
+3. Verifique se nem todos os PDPs e PLPs foram atualizados com as novas informações corretas.
+
+
+
+## Workaround
+
+
+Reindexar os produtos afetados novamente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md b/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
index ff22eb133..08a768d15 100644
--- a/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
+++ b/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
@@ -1,16 +1,16 @@
 ---
-title: 'A atualização inteligente do Banner de busca via URL da imagem não funciona corretamente'
+title: 'A atualização do banner do Intelligent Search por meio do URL da imagem não funciona corretamente'
 id: bMFrVUmfbjvTWs4Ag6U57
 status: PUBLISHED
 createdAt: 2023-01-17T14:34:02.195Z
-updatedAt: 2023-01-17T14:34:10.348Z
-publishedAt: 2023-01-17T14:34:10.348Z
+updatedAt: 2023-09-06T22:35:01.155Z
+publishedAt: 2023-09-06T22:35:01.155Z
 firstPublishedAt: 2023-01-17T14:34:02.912Z
 contentType: knownIssue
 productTeam: Intelligent Search
 author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
-slug: a-atualizacao-inteligente-do-banner-de-busca-via-url-da-imagem-nao-funciona-corretamente
+slug: a-atualizacao-do-banner-do-intelligent-search-por-meio-do-url-da-imagem-nao-funciona-corretamente
 locale: pt
 kiStatus: Backlog
 internalReference: 734833
@@ -23,27 +23,21 @@ internalReference: 734833
 </div>
 
 
-Em Admin V4, no módulo Banners, o usuário tem a possibilidade de criar ou atualizar os banners já criados. Ao selecionar um banner para atualização, ele pode escolher entre usar um campo HTML ou inserir um link direto de imagem com uma URL externa. Ao selecionar a inserção do banner através de um link direto de imagem, a consulta GraphQL `setBanner` é acionada, que atualmente não está funcionando corretamente, retornando `syntaxError`, conseqüentemente, erro 500.
-
-
-##
+No Admin V4, no módulo Banners, o usuário tem a possibilidade de criar ou atualizar banners já criados. Ao selecionar um banner para atualização, o usuário pode escolher entre usar um campo HTML ou inserir um link de imagem direto com um URL externo. Ao selecionar a inserção do banner por meio de um link de imagem direto, é acionada a consulta GraphQL, que atualmente não está funcionando corretamente, retornando `syntaxError` e, consequentemente, o erro 500.
 
 ## Simulação
 
 
-Em uma loja com Admin V4, acesse o módulo Banners, dentro de Search;
-Selecione um banner previamente criado;
-Em Type, selecione Image;
-Preencha os campos do link;
-Ao clicar em Save, a tela mostrará um erro GraphQL;
-
-
-##
+Em uma loja com o Admin V4, acesse o módulo Banners, dentro de Search;
+Selecione um banner criado anteriormente;
+Em Type (Tipo), selecione Image (Imagem);
+Preencha os campos de link;
+Ao clicar em Save, a tela mostrará um erro GraphQL
 
 ## Workaround
 
 
-Criar um novo banner com as mesmas especificações (a consulta de criação de banner é `criateBanner` e está funcionando corretamente);
+N/A
 
 
 
diff --git a/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md b/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
new file mode 100644
index 000000000..08389bb48
--- /dev/null
+++ b/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
@@ -0,0 +1,62 @@
+---
+title: 'As configurações de idioma do Intelligent Search não estão sincronizadas com as configurações da loja'
+id: 1GqoAyUSbTxwHvzoMoAYfD
+status: PUBLISHED
+createdAt: 2024-02-27T21:30:40.309Z
+updatedAt: 2024-03-06T15:38:20.358Z
+publishedAt: 2024-03-06T15:38:20.358Z
+firstPublishedAt: 2024-02-27T21:30:41.209Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: as-configuracoes-de-idioma-do-intelligent-search-nao-estao-sincronizadas-com-as-configuracoes-da-loja
+locale: pt
+kiStatus: Backlog
+internalReference: 990343
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O idioma principal da Pesquisa Inteligente não é atualizado automaticamente de acordo com a política comercial e as configurações de vinculação, o que o torna fora de sincronia.
+
+Para lojas de idioma único, o conteúdo do Intelligent Search, como sinônimos, regras de merchandising, banners de pesquisa e redirecionamentos de pesquisa, é criado sobre os locais registrados na associação. A vitrine é renderizada com base também na política comercial, que pode substituir a vinculação e não corresponderá ao conteúdo registrado.
+
+Para lojas multilíngues, potencialmente, isso também afeta as traduções fornecidas na vitrine e nas APIs.
+
+## Simulação
+
+
+
+- Crie uma loja em "pt-BR";
+- Habilite/configure o módulo Intelligent Search;
+- Alterar a política comercial de "pt-BR" para "en-US";
+- Idioma único:
+  - Manter a vinculação como "pt-BR";
+  - Criar conteúdo do Intelligent Search;
+  - Acesse a página da loja que deve apresentar o conteúdo registrado;
+  - O conteúdo/comportamento não estará visível.
+- Vários idiomas:
+  - Registre os produtos em inglês;
+  - Adicionar o português como segundo idioma/alternativo nos bindings
+  - Registre as traduções do catálogo para o português;
+  - Nesse cenário, a navegação entre os dois idiomas pode apresentar problemas.
+
+## Workaround
+
+
+Certifique-se de que os vínculos e as políticas comerciais correspondam; caso contrário, o conteúdo da pesquisa será inválido.
+
+O conteúdo registrado anteriormente não seguirá o novo idioma principal se ele for alterado; ele permanecerá vinculado ao idioma de criação. É necessário registrar pelo menos dois locais na configuração de vinculações (o idioma antigo/inesperado e o novo/esperado) para ver o seletor de idioma no editor de conteúdo, de modo que você possa corrigi-los manualmente para usar o idioma esperado. Outro método é recriar o conteúdo.
+
+Em alguns cenários, como traduções em vários idiomas e catálogos, talvez seja necessário entrar em contato com o nosso suporte para revisar as configurações de idioma interno do Intelligent Search.
+
+
+
+
+
diff --git a/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md b/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md
new file mode 100644
index 000000000..5009acbcc
--- /dev/null
+++ b/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md
@@ -0,0 +1,42 @@
+---
+title: 'O Intelligent Search não está capturando eventos de vendas para o FastStore'
+id: 4sT3tm37DP6E6jWzYNHJQe
+status: PUBLISHED
+createdAt: 2024-06-05T22:21:23.343Z
+updatedAt: 2024-06-05T22:21:24.206Z
+publishedAt: 2024-06-05T22:21:24.206Z
+firstPublishedAt: 2024-06-05T22:21:24.206Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: o-intelligent-search-nao-esta-capturando-eventos-de-vendas-para-o-faststore
+locale: pt
+kiStatus: Scheduled
+internalReference: 1045163
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O Intelligent Search não está capturando eventos de pedidos concluídos para lojas que usam o FastStore. Esses eventos compõem os critérios de relevância e a classificação de produtos por vendas.
+
+## Simulação
+
+
+O cenário pode ser reproduzido em qualquer loja que use o FastStore. A maneira mais fácil de ver o problema é observar que o relatório de análise de pesquisa não computará as vendas.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md b/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
new file mode 100644
index 000000000..164cc18c0
--- /dev/null
+++ b/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurações do Intelligent Search Redirect A barra de pesquisa diferencia maiúsculas de minúsculas'
+id: 5QEkcyhCQWyw093UkDCeOq
+status: PUBLISHED
+createdAt: 2023-09-26T23:50:50.661Z
+updatedAt: 2023-09-26T23:50:51.661Z
+publishedAt: 2023-09-26T23:50:51.661Z
+firstPublishedAt: 2023-09-26T23:50:51.661Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: configuracoes-do-intelligent-search-redirect-a-barra-de-pesquisa-diferencia-maiusculas-de-minusculas
+locale: pt
+kiStatus: Backlog
+internalReference: 361894
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A página de configurações do Intelligent Search Redirect tem uma barra de pesquisa para ajudar a encontrar configurações de redirecionamento específicas, mas ela diferencia maiúsculas de minúsculas e só encontrará termos se eles corresponderem exatamente.
+
+## Simulação
+
+
+Acesse `/admin/search/redirects`.
+
+Pesquise o nome de uma configuração, mas alterando uma letra para maiúscula. A pesquisa não obterá nenhum resultado
+
+## Workaround
+
+
+Gere nomes de rotas com um padrão consistente, somente letras minúsculas, somente letras maiúsculas ou camel case.
+
diff --git a/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md b/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
new file mode 100644
index 000000000..705976571
--- /dev/null
+++ b/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
@@ -0,0 +1,45 @@
+---
+title: 'O analisador de palavras do Intelligent Search não normaliza o gênero em palavras em português'
+id: 2oVUQnXZK6FNXg7co88C1B
+status: PUBLISHED
+createdAt: 2024-07-26T22:55:32.746Z
+updatedAt: 2024-07-26T22:55:46.558Z
+publishedAt: 2024-07-26T22:55:46.558Z
+firstPublishedAt: 2024-07-26T22:55:33.875Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: o-analisador-de-palavras-do-intelligent-search-nao-normaliza-o-genero-em-palavras-em-portugues
+locale: pt
+kiStatus: Backlog
+internalReference: 1072003
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que os termos pesquisados sejam normalizados entre suas diferentes formas (plural/singular, gênero e outras possibilidades), um processo formalmente chamado de stemming. O analisador é diferente para cada idioma para atender às suas necessidades.
+
+O analisador para o português não está normalizando o gênero das palavras.
+
+## Simulação
+
+
+Considere uma palavra registrada em diferentes produtos com gêneros diferentes, como "camiseta listrada" e "vestido listrado".
+
+Embora "listrada" e "listrado" sejam a mesma palavra, mas em formas de gênero diferentes, a busca por "listrada" não retornará os "vestidos" e vice-versa
+
+## Workaround
+
+
+Registre sinônimos bidirecionais para palavras com variações relevantes de forma de gênero.
+
+
+
+
+
diff --git a/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md b/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
new file mode 100644
index 000000000..979db3fbb
--- /dev/null
+++ b/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
@@ -0,0 +1,44 @@
+---
+title: 'A interação com o componente de endereço enquanto alguns dados na interface do usuário ainda estão em um estado de carregamento altera o modo de inserção de endereço'
+id: 7t3jzIpIppmZDAc9R2BgpS
+status: PUBLISHED
+createdAt: 2023-09-13T20:39:43.294Z
+updatedAt: 2023-09-13T20:39:44.079Z
+publishedAt: 2023-09-13T20:39:44.079Z
+firstPublishedAt: 2023-09-13T20:39:44.079Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interacao-com-o-componente-de-endereco-enquanto-alguns-dados-na-interface-do-usuario-ainda-estao-em-um-estado-de-carregamento-altera-o-modo-de-insercao-de-endereco
+locale: pt
+kiStatus: Backlog
+internalReference: 423811
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o usuário decide alterar seu endereço enquanto alguns dados respectivos ainda estão sendo carregados na página, o componente de endereço muda de geolocalização para o componente com um menu suspenso. Os dados podem ser, por exemplo, a seleção de uma loja para retirada. Enquanto os dados são carregados na interface, o usuário clica em "alterar endereço" e, com isso, o endereço de retorno fica em outro componente, não no componente de geolocalização.
+
+## Simulação
+
+
+
+- Configure uma conta para usar coordenadas geográficas no checkout;
+- Procure um endereço na etapa de envio;
+- Clique em Change (Alterar) enquanto a página estiver carregando;
+- O componente de endereço será alterado e solicitará que você preencha as informações de endereç
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md b/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
new file mode 100644
index 000000000..1402d5854
--- /dev/null
+++ b/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
@@ -0,0 +1,43 @@
+---
+title: 'A interação com o componente de pagamento enquanto ele ainda está em um estado de carregamento envia a opção de pagamento errada'
+id: 4kSvM6fti8YfgcUyl4qFJs
+status: PUBLISHED
+createdAt: 2023-12-12T22:07:58.762Z
+updatedAt: 2023-12-12T22:07:59.474Z
+publishedAt: 2023-12-12T22:07:59.474Z
+firstPublishedAt: 2023-12-12T22:07:59.474Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interacao-com-o-componente-de-pagamento-enquanto-ele-ainda-esta-em-um-estado-de-carregamento-envia-a-opcao-de-pagamento-errada
+locale: pt
+kiStatus: Backlog
+internalReference: 952086
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o comprador altera o método de pagamento enquanto o componente de pagamento ainda está sendo carregado na página, se o método de pagamento tiver opções, o pagamento enviado ao formulário de pedido está errado. Quando esse comportamento ocorre, o pedido não é criado e uma mensagem para revisar as informações de pagamento é exibida.
+
+## Simulação
+
+
+
+- Adicione itens ao carrinho e vá até os dados de pagamento;
+- Clique em um método de pagamento diferente enquanto a página estiver carregando e selecione outra opção dentro do componente;
+- O pagamento enviado ao orderForm está errado, sendo a primeira opção
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/intermitent-site-editor-content-loss.md b/docs/known-issues/pt/intermitent-site-editor-content-loss.md
new file mode 100644
index 000000000..7c4706e28
--- /dev/null
+++ b/docs/known-issues/pt/intermitent-site-editor-content-loss.md
@@ -0,0 +1,49 @@
+---
+title: 'Perda intermitente de conteúdo do Site Editor'
+id: 3a5MlAoD2Z7Gu6HDS8wihD
+status: PUBLISHED
+createdAt: 2022-07-05T17:07:24.733Z
+updatedAt: 2024-03-21T20:37:27.369Z
+publishedAt: 2024-03-21T20:37:27.369Z
+firstPublishedAt: 2022-07-05T17:07:25.091Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: perda-intermitente-de-conteudo-do-site-editor
+locale: pt
+kiStatus: Scheduled
+internalReference: 610533
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Cada alteração de conteúdo no Site Editor insere alterações no arquivo content.json, que é armazenado em um bucket no AWS S3. Alguns clientes relataram uma perda de conteúdo do Site Editor após alguns procedimentos comuns de atualizações de temas.
+
+## Simulação
+
+
+O cenário é intermitente, no entanto, foi relatado em dois cenários diferentes:
+
+**1. Ao promover um espaço de trabalho de produção para o mestre:**
+Os clientes relataram que, ao promover um espaço de trabalho de produção, contendo alterações em componentes, para o ambiente mestre, houve uma perda de conteúdo em outros espaços de trabalho.
+
+**2. Ao instalar uma nova versão em um espaço de trabalho de teste:**
+Os clientes relataram que, ao instalar uma nova versão de tema em um espaço de trabalho de teste, o conteúdo das páginas de categoria era excluído.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md b/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md
new file mode 100644
index 000000000..1b628d607
--- /dev/null
+++ b/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md
@@ -0,0 +1,45 @@
+---
+title: 'Tempo limite do InternalSearchError no Portal'
+id: 6D6mdJ3zQypy1lcuht7WuU
+status: PUBLISHED
+createdAt: 2024-06-03T15:25:56.353Z
+updatedAt: 2024-07-30T13:55:06.518Z
+publishedAt: 2024-07-30T13:55:06.518Z
+firstPublishedAt: 2024-06-03T15:25:57.378Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: tempo-limite-do-internalsearcherror-no-portal
+locale: pt
+kiStatus: Backlog
+internalReference: 1043003
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, as lojas que usam a pesquisa legada do Portal podem enfrentar, ao usar vários filtros em sua loja, como filtros de coleção em modelos, tempos limite aleatórios e intermitentes que geralmente são exibidos como um erro "Algo deu errado" para os clientes.
+
+Esse problema é, internamente, um tempo limite que está sendo analisado pelas equipes de tecnologia para que seu tempo seja aumentado.
+
+## Simulação
+
+
+Esse erro é altamente intermitente e difícil de replicar de forma consistente. Ele costuma ser mais frequente em contas que usam vários filtros de coleção em seus modelos, mas não há uma maneira confiável de replicá-lo.
+
+
+
+## Workaround
+
+
+Enquanto os tempos limite não são investigados e aumentados, recomenda-se reduzir a quantidade de filtros que estão sendo usados em pesquisas e menus, o que não garante a eliminação completa desses tempos limite, mas os reduz significativamente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
new file mode 100644
index 000000000..a1bc94ed7
--- /dev/null
+++ b/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -0,0 +1,47 @@
+---
+title: 'Mensagem "Código postal inválido" na interface do usuário do checkout quando o endereço está em endereços disponíveis com país diferente'
+id: 4VggIx4xWPNW6OBIrQ0js4
+status: PUBLISHED
+createdAt: 2024-06-21T17:08:59.860Z
+updatedAt: 2024-06-21T17:09:00.771Z
+publishedAt: 2024-06-21T17:09:00.771Z
+firstPublishedAt: 2024-06-21T17:09:00.771Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: mensagem-codigo-postal-invalido-na-interface-do-usuario-do-checkout-quando-o-endereco-esta-em-enderecos-disponiveis-com-pais-diferente
+locale: pt
+kiStatus: Backlog
+internalReference: 1053959
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A interface do usuário do checkout usa o país registrado em seu estado para validar a entrada do código postal.
+
+Quando os endereços são registrados em endereços disponíveis, mas o formulário de pedido é alterado para outro canal de vendas, e esse canal de vendas tem um país diferente para envio, a mensagem "Código postal inválido" é exibida logo abaixo da entrada do código postal, não sendo possível prosseguir com a compra.
+
+## Simulação
+
+
+
+- Monte um carrinho e adicione um endereço;
+- Altere o canal de vendas, onde ele é enviado para um país diferente;
+- Tente adicionar o novo código postal; é exibida a mensagem "Código postal inválido".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md b/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md
new file mode 100644
index 000000000..efabd48cd
--- /dev/null
+++ b/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md
@@ -0,0 +1,50 @@
+---
+title: 'As notificações de inventário para o indexador são armazenadas em cache'
+id: 2eFmUbO1PR7ahxAGiMkqZd
+status: PUBLISHED
+createdAt: 2023-10-05T12:48:05.930Z
+updatedAt: 2024-05-14T11:26:36.897Z
+publishedAt: 2024-05-14T11:26:36.897Z
+firstPublishedAt: 2023-10-05T12:48:06.727Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-notificacoes-de-inventario-para-o-indexador-sao-armazenadas-em-cache
+locale: pt
+kiStatus: Fixed
+internalReference: 914545
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma conta de franquia ou um vendedor notifica a conta principal (ou o marketplace) sobre alterações no estoque, a conta envia o produto ao indexador para ter as informações mais atualizadas.
+
+O sistema responsável por receber as notificações e passá-las ao indexador é o Broadcaster.
+
+O problema é que o fluxo de trabalho Disponibilidade -> Broadcaster -> Indexador está funcionando em um ritmo muito rápido e, em alguns casos, as informações ainda são armazenadas em cache. Dessa forma, o indexador permanece com as informações antigas até uma nova indexação.
+
+## Simulação
+
+
+Não há uma maneira fácil de simular esse cenário, pois ele não acontece em todas as ocasiões.
+O processo deve ser:
+
+1. A conta da franquia atualiza um inventário;
+2. A emissora envia o produto para o indexador;
+3. O indexador atualiza o sku da conta principal com as informações antigas
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/inventory-reserved-items-error.md b/docs/known-issues/pt/inventory-reserved-items-error.md
index 4ffb7f3f2..042b8a016 100644
--- a/docs/known-issues/pt/inventory-reserved-items-error.md
+++ b/docs/known-issues/pt/inventory-reserved-items-error.md
@@ -1,36 +1,42 @@
 ---
-title: 'Inventory Reserved Items Error'
+title: 'Erro de itens reservados de estoque'
 id: 37cO3T4D0exvOMhStKYds9
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-18T15:13:46.087Z
-updatedAt: 2022-06-27T12:33:44.492Z
-publishedAt: 2022-06-20T12:39:37.793Z
+updatedAt: 2024-07-03T20:14:35.313Z
+publishedAt: 2024-07-03T20:14:35.313Z
 firstPublishedAt: 2022-05-18T15:13:46.568Z
 contentType: knownIssue
 productTeam: Logistics
 author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
-slug: inventory-reserved-items-error
+slug: erro-de-itens-reservados-de-estoque
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 347924
 ---
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
+
+
+Ao verificar os itens de status reservado no **Inventory Management**, há um erro ao mostrar os pedidos relacionados.
+
+Não é possível ver os pedidos; ao clicar no número de itens reservados, é exibida a mensagem de erro "There was an error loading reservations. Por favor, tente novamente."
+
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+
+A simulação não é possível
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+
+Não há nenhuma solução alternativa disponível.
 
diff --git a/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
new file mode 100644
index 000000000..4fcb39130
--- /dev/null
+++ b/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -0,0 +1,44 @@
+---
+title: 'Caracteres invisíveis em nomes de categorias causam erros de "página não encontrada'
+id: 4np2BZUF1EmlLmV0KTpnrf
+status: PUBLISHED
+createdAt: 2024-07-05T13:11:13.031Z
+updatedAt: 2024-07-05T13:11:14.090Z
+publishedAt: 2024-07-05T13:11:14.090Z
+firstPublishedAt: 2024-07-05T13:11:14.090Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: caracteres-invisiveis-em-nomes-de-categorias-causam-erros-de-pagina-nao-encontrada
+locale: pt
+kiStatus: Backlog
+internalReference: 1061149
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar categorias por meio da API ou do painel de administração, o nome da categoria não é validado corretamente, permitindo a inclusão de caracteres invisíveis. Como o nome da categoria é usado para gerar o URL da categoria, esses caracteres invisíveis também são incluídos no URL. Isso faz com que a página da categoria não funcione corretamente e retorne um erro "Página não encontrada".
+
+## Simulação
+
+
+
+1. Crie uma categoria com um caractere invisível em seu nome usando a API ou o painel de administração.
+2. Acesse o URL da API para essa categoria.
+3. Observe o erro "Página não encontrada"
+
+## Workaround
+
+
+
+A solução alternativa é remover o caractere invisível do nome da categoria, o que também atualizará o URL da página, resolvendo o problema.
+
+
+
+
diff --git a/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md b/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
index 27bcb73ee..fcaaefb50 100644
--- a/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
+++ b/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
@@ -3,8 +3,8 @@ title: 'O parâmetro isAvailablePerSalesChannel não funciona como esperado na A
 id: 6vexCZQTib8fFI6sCSTdWL
 status: PUBLISHED
 createdAt: 2022-09-12T16:03:25.215Z
-updatedAt: 2022-11-25T21:43:40.015Z
-publishedAt: 2022-11-25T21:43:40.015Z
+updatedAt: 2024-02-16T20:24:54.890Z
+publishedAt: 2024-02-16T20:24:54.890Z
 firstPublishedAt: 2022-09-12T16:03:25.837Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: o-parametro-isavailablepersaleschannel-nao-funciona-como-esperado-na-api-de-pesquisa
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 656284
 ---
 
diff --git a/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md b/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md
index 9d97e5c2f..a12b8db98 100644
--- a/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md
+++ b/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md
@@ -3,8 +3,8 @@ title: 'Edição na Busca Explicada de buscas com acentos'
 id: 5rh2FSzIeSjnO7bUlEkJ9S
 status: PUBLISHED
 createdAt: 2022-02-23T21:59:57.268Z
-updatedAt: 2022-11-25T21:58:45.841Z
-publishedAt: 2022-11-25T21:58:45.841Z
+updatedAt: 2024-02-16T20:28:06.748Z
+publishedAt: 2024-02-16T20:28:06.748Z
 firstPublishedAt: 2022-02-23T21:59:57.508Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: edicao-na-busca-explicada-de-buscas-com-acentos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 434752
 ---
 
diff --git a/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md b/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md
index 14f687cbd..5908ab983 100644
--- a/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md
+++ b/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md
@@ -1,18 +1,18 @@
 ---
-title: 'Edição sobre a tradução de títulos para algumas facetas'
+title: 'Problema na tradução de títulos para algumas facetas'
 id: iG3Kb1AfH7QIqYn1ewnuw
 status: PUBLISHED
 createdAt: 2023-03-22T19:26:31.477Z
-updatedAt: 2023-03-22T19:26:31.933Z
-publishedAt: 2023-03-22T19:26:31.933Z
+updatedAt: 2023-10-27T00:51:10.361Z
+publishedAt: 2023-10-27T00:51:10.361Z
 firstPublishedAt: 2023-03-22T19:26:31.933Z
 contentType: knownIssue
 productTeam: Intelligent Search
 author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
-slug: edicao-sobre-a-traducao-de-titulos-para-algumas-facetas
+slug: problema-na-traducao-de-titulos-para-algumas-facetas
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 776353
 ---
 
@@ -23,25 +23,15 @@ internalReference: 776353
 </div>
 
 
-Há alguns casos em que o título da página está incorreto para lojas multilíngües em páginas como categoria, subcategoria e marcas, onde o caminho tem um valor e quando se olha o título da página tem um nome diferente que não combina com o esperado.
-
-
-##
+Há alguns casos em que o título da página está incorreto para lojas multilíngues em páginas como categoria, subcategoria e marcas, em que o caminho tem um valor e, ao examinar o título da página, ele tem um nome diferente que não corresponde ao esperado.
 
 ## Simulação
 
 
-Verifique o caminho que está sendo montado também verifique se a loja é multilíngüe, e se isto não combina com o caminho e as respectivas traduções, se isto não combina é um bug.
-
-
-##
+Verifique o caminho que está sendo montado e verifique também se a loja é multilíngue e, se isso não corresponder ao caminho e às respectivas traduções, se não corresponder, isso é um bug
 
 ## Workaround
 
 
-Não há nenhum
-
-
-
-
+N/A
 
diff --git a/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md b/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
new file mode 100644
index 000000000..e97933f6d
--- /dev/null
+++ b/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
@@ -0,0 +1,43 @@
+---
+title: 'Problema com APIs de sessão usando propriedades públicas que começam com o mesmo prefixo'
+id: RAoSKg2hwwiC6L7wFPyNv
+status: PUBLISHED
+createdAt: 2023-08-21T20:00:45.403Z
+updatedAt: 2023-08-21T20:11:44.751Z
+publishedAt: 2023-08-21T20:11:44.751Z
+firstPublishedAt: 2023-08-21T20:00:46.132Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: problema-com-apis-de-sessao-usando-propriedades-publicas-que-comecam-com-o-mesmo-prefixo
+locale: pt
+kiStatus: Backlog
+internalReference: 885011
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A API de sessão está gerando algumas inconsistências. A equipe de engenharia identificou o erro, que está relacionado a propriedades que começam com a mesma palavra.
+
+## Simulação
+
+
+Se você fizer um POST enviando 2 valores públicos com o mesmo prefixo, a API receberá apenas um. Se você tentar novamente, fazendo o mesmo POST enviando os mesmos 2 valores, a API receberá ambos.
+
+
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md b/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
new file mode 100644
index 000000000..078c626ac
--- /dev/null
+++ b/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
@@ -0,0 +1,42 @@
+---
+title: 'Problemas ao inserir valores no cartão-presente de fidelidade no checkout'
+id: 74bFvs0PmQzRGzkOdnwiLw
+status: PUBLISHED
+createdAt: 2023-11-28T17:16:34.758Z
+updatedAt: 2023-11-28T17:16:35.407Z
+publishedAt: 2023-11-28T17:16:35.407Z
+firstPublishedAt: 2023-11-28T17:16:35.407Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: problemas-ao-inserir-valores-no-cartaopresente-de-fidelidade-no-checkout
+locale: pt
+kiStatus: Backlog
+internalReference: 943629
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o cartão-presente de fidelidade, os usuários podem ter uma experiência ruim ao selecionar a opção "Use only part of the value" (Usar apenas parte do valor), pois não há botão "Add" (Adicionar) após preencher "Value to use" (Valor a ser usado) (a entrada é aceita automaticamente), portanto, se um valor não for preenchido com rapidez suficiente, ele será atualizado apenas com os primeiros dígitos, fazendo com que o usuário tenha de repetir o procedimento. Essa experiência é pior no site para celular.
+
+## Simulação
+
+
+Depois de criar um cartão-presente de fidelidade para um e-mail, ele aparecerá no checkout e você poderá prosseguir com o cenário descrito acima.
+
+https://support.vtex.com/hc/en-us/articles/1289748527644
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md b/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md
new file mode 100644
index 000000000..8ceedc3c3
--- /dev/null
+++ b/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md
@@ -0,0 +1,48 @@
+---
+title: 'Problemas com BillingAddress que levam ao cancelamento de transações'
+id: 14RT6S4Hm7H30L0FBzdDRY
+status: PUBLISHED
+createdAt: 2024-05-06T16:34:12.989Z
+updatedAt: 2024-05-06T16:34:14.299Z
+publishedAt: 2024-05-06T16:34:14.299Z
+firstPublishedAt: 2024-05-06T16:34:14.299Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: problemas-com-billingaddress-que-levam-ao-cancelamento-de-transacoes
+locale: pt
+kiStatus: Backlog
+internalReference: 1027901
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+As transações estão sendo canceladas durante a análise antifraude devido à falta de informações essenciais no `billingAddress`.
+
+O `billingAddress` é enviado durante o processo de pagamento e pode ser uma cópia do `shippingAddress` se o usuário optar por não diferenciá-los (marcando `isBillingAddressDifferent` como `false`) durante o checkout. Como alternativa, pode ser um novo endereço fornecido pelo usuário se a opção `isBillingAddressDifferent` for marcada como `true`. Esse endereço é usado na solicitação de autorização antifraude e a ausência de informações obrigatórias pode levar ao cancelamento de transações.
+
+Observamos que esse comportamento ocorre com pagamentos feitos com novos cartões, que não foram salvos anteriormente na loja, e quando o usuário opta por não diferenciar os endereços (`isBillingAddressDifferent`: `false`). É importante ressaltar que o `shippingAaddress` contém todos os campos obrigatórios preenchidos corretamente, enquanto o `billingAddress`, que deveria ser uma cópia do `shippingAddress`, permanece incompleto.
+
+## Simulação
+
+
+Não foi possível replicar esse problema
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/issues-with-my-account-links.md b/docs/known-issues/pt/issues-with-my-account-links.md
new file mode 100644
index 000000000..55aee3c38
--- /dev/null
+++ b/docs/known-issues/pt/issues-with-my-account-links.md
@@ -0,0 +1,45 @@
+---
+title: 'Problemas com os links de Minha conta'
+id: 1p23CCNhJwnEXm501P9Nxh
+status: PUBLISHED
+createdAt: 2023-07-03T17:26:59.597Z
+updatedAt: 2023-07-03T17:27:00.108Z
+publishedAt: 2023-07-03T17:27:00.108Z
+firstPublishedAt: 2023-07-03T17:27:00.108Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: problemas-com-os-links-de-minha-conta
+locale: pt
+kiStatus: Backlog
+internalReference: 522514
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os links em Minha conta (menu do cabeçalho) não funcionam se o usuário já estiver na seção Minha conta
+
+## Simulação
+
+
+Acesso à página My account (Minha conta)
+Clique no link do menu do cabeçalho (como a opção Orders (Pedidos), por exemplo)
+Verificar se a url foi modificada, mas a página não é carregada
+
+
+
+## Workaround
+
+
+Não há solução alternativa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md b/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
new file mode 100644
index 000000000..226f8c870
--- /dev/null
+++ b/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
@@ -0,0 +1,51 @@
+---
+title: 'Não é possível adicionar um item com anexo ao carrinho se já houver outra unidade desse item sem anexo no carrinho'
+id: 3l41VmdtPCxUjYChuO7o9O
+status: PUBLISHED
+createdAt: 2021-09-15T15:24:52.309Z
+updatedAt: 2024-02-02T15:01:32.297Z
+publishedAt: 2024-02-02T15:01:32.297Z
+firstPublishedAt: 2021-09-15T15:30:26.487Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: nao-e-possivel-adicionar-um-item-com-anexo-ao-carrinho-se-ja-houver-outra-unidade-desse-item-sem-anexo-no-carrinho
+locale: pt
+kiStatus: No Fix
+internalReference: 412041
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Durante o processo de compra, se o cliente adicionar um item que já tenha sido incluído no carrinho anteriormente e a nova inclusão tiver opções de montagem, o segundo item não será adicionado ao carrinho.
+
+Por exemplo, se, durante o processo de compra, o cliente adicionar uma SKU ao carrinho e, em seguida, outra unidade da mesma SKU, mas com garantia estendida (via assemblyOptions), o último item adicionado (o item com garantia estendida) não estará disponível no carrinho.
+
+## Simulação
+
+
+Para executar a simulação, verifique se há itens com opções de montagem em sua loja.
+
+
+1. Acesse a loja;
+2. Adicionar um produto ao carrinho;
+3. Adicione o produto mais uma vez e inclua uma opção de montagem ao item (uma personalização ou uma garantia estendida, por exemplo);
+4. Verifique o carrinho e verifique se o item com a opção de montagem não foi adicionado.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md b/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
new file mode 100644
index 000000000..d8196ccb1
--- /dev/null
+++ b/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
@@ -0,0 +1,47 @@
+---
+title: 'Não é possível criar um caminho usando o tipo de conteúdo por meio da interface do usuário'
+id: 3jVjkZYCATrnDNhR0IKSEA
+status: PUBLISHED
+createdAt: 2023-10-23T13:19:09.970Z
+updatedAt: 2024-07-01T18:49:16.580Z
+publishedAt: 2024-07-01T18:49:16.580Z
+firstPublishedAt: 2023-10-23T13:19:10.738Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: nao-e-possivel-criar-um-caminho-usando-o-tipo-de-conteudo-por-meio-da-interface-do-usuario
+locale: pt
+kiStatus: No Fix
+internalReference: 923619
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se tentarmos criar um caminho usando tipos de conteúdo por meio da interface do usuário, a página não funcionará. Ela só funcionará se a criarmos por meio do tema.
+
+## Simulação
+
+
+
+- Crie um caminho usando um tipo de conteúdo no módulo Pages, por exemplo, `storeTest/:test_id`
+- Salve-o
+- Tente acessá-lo no front
+- Não funcionará
+
+
+
+## Workaround
+
+
+Se adicionarmos o caminho usando o tipo de conteúdo por meio do tema, a página aparecerá na interface do usuário e funcionará
+
+
+
+
+
diff --git a/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md b/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
new file mode 100644
index 000000000..2eeedae11
--- /dev/null
+++ b/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
@@ -0,0 +1,44 @@
+---
+title: 'O preenchimento automático do item não é exibido na etiqueta branca do vendedor (ordem de modificação)'
+id: 1jvkXj20gVHNtpp3KNL5GW
+status: PUBLISHED
+createdAt: 2024-03-05T21:55:53.411Z
+updatedAt: 2024-03-11T20:00:01.928Z
+publishedAt: 2024-03-11T20:00:01.928Z
+firstPublishedAt: 2024-03-05T21:55:54.222Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-preenchimento-automatico-do-item-nao-e-exibido-na-etiqueta-branca-do-vendedor-ordem-de-modificacao
+locale: pt
+kiStatus: Backlog
+internalReference: 348841
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao alterar um item (ordem de alteração) de uma conta de vendedor WhiteLabel, o preenchimento automático não mostra o item como esperado.
+
+
+## Simulação
+
+
+- Acesse um pedido de uma conta de vendedor de marca branca e solicite a opção de alteração de item:
+- Ao preencher o nome do SKU na pesquisa, ele não é exibido pelo preenchimento automático:
+- O mesmo se aplica ao vendedor de marca branca com a nova versão de pedidos administrativos
+
+## Workaround
+
+
+Você pode fazer a alteração do item por meio da API Register Change on Order.
+
+
+
+
+
diff --git a/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md b/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md
new file mode 100644
index 000000000..b2b58c989
--- /dev/null
+++ b/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md
@@ -0,0 +1,45 @@
+---
+title: 'Item disponível quando a localização do cliente não está definida e não há estoque'
+id: 7vDywP0WtfpJ4bCiNkXNfw
+status: PUBLISHED
+createdAt: 2024-07-30T22:51:30.425Z
+updatedAt: 2024-07-30T22:54:29.056Z
+publishedAt: 2024-07-30T22:54:29.056Z
+firstPublishedAt: 2024-07-30T22:51:31.764Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: item-disponivel-quando-a-localizacao-do-cliente-nao-esta-definida-e-nao-ha-estoque
+locale: pt
+kiStatus: Backlog
+internalReference: 1073363
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a localização do cliente não é definida, os itens aparecem disponíveis mesmo quando não há estoque disponível e nenhuma etiqueta branca do vendedor é abrangente. Isso acontece somente se a SKU tiver estoque no vendedor de etiqueta branca em um depósito associado a um canal de vendas diferente daquele registrado no endpoint de atendimento do vendedor.
+
+## Simulação
+
+
+
+- Não há estoque para o vendedor 1;
+- Nenhum vendedor abrangente configurado;
+- Estoque em um vendedor de marca branca em um canal de vendas diferente do ponto de extremidade de atendimento, por exemplo:
+Ponto de extremidade de atendimento com sc=1;
+Estoque no vendedor para sc=2
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md b/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
new file mode 100644
index 000000000..7fd6e236b
--- /dev/null
+++ b/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
@@ -0,0 +1,35 @@
+---
+title: 'O item_name do evento de compra é diferente do item_name do evento de adição ao carrinho no Google Analytics'
+id: 3FV2cJIV7uOIoH0lpl0iMP
+status: PUBLISHED
+createdAt: 2023-08-10T12:59:26.495Z
+updatedAt: 2023-08-10T12:59:27.432Z
+publishedAt: 2023-08-10T12:59:27.432Z
+firstPublishedAt: 2023-08-10T12:59:27.432Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-itemname-do-evento-de-compra-e-diferente-do-itemname-do-evento-de-adicao-ao-carrinho-no-google-analytics
+locale: pt
+kiStatus: Backlog
+internalReference: 878629
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a SKU tem o mesmo nome que o produto, o item_name da compra é diferente do item_name do evento add-to-cart.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md b/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
new file mode 100644
index 000000000..3dd8c41a9
--- /dev/null
+++ b/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
@@ -0,0 +1,50 @@
+---
+title: 'Itens em benefícios não gerados em promoções com coleções associadas'
+id: 9HrnxMcq7VWFQOPhg9ywd
+status: PUBLISHED
+createdAt: 2024-02-21T15:09:01.111Z
+updatedAt: 2024-02-21T15:09:01.913Z
+publishedAt: 2024-02-21T15:09:01.913Z
+firstPublishedAt: 2024-02-21T15:09:01.913Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: itens-em-beneficios-nao-gerados-em-promocoes-com-colecoes-associadas
+locale: pt
+kiStatus: Backlog
+internalReference: 985850
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao fazer uma promoção com produtos/skus associados por meio de uma coleção, o productContext não está preparado para criar a matriz de itens dentro dos benefícios associados aos produtos da coleção
+
+## Simulação
+
+
+
+
+- Criar uma promoção
+- Associar os produtos para essa promoção por meio de uma coleção
+- Abra um dos produtos que deve ter uma promoção
+- Abra o console do seu navegador
+- Verifique se há productContextProvider em sua extensão React Dev Tools
+- Abra benefits.items, ele estará vazio ou com o sku com o mesmo id da coleçã
+
+## Workaround
+
+
+
+A única maneira possível de preencher o benefits.items é preencher todos os skus associados à promoção em vez de um cluster/coleção
+
+
+
+
+
diff --git a/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md b/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md
index c43f9cc22..deb9497ec 100644
--- a/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md
+++ b/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md
@@ -3,8 +3,8 @@ title: 'A API de criação de kits não está calculando os preços dos componen
 id: 3yyIEv6o3CjIbUg4KoLOWT
 status: PUBLISHED
 createdAt: 2023-03-28T16:34:55.491Z
-updatedAt: 2023-03-28T16:34:55.990Z
-publishedAt: 2023-03-28T16:34:55.990Z
+updatedAt: 2024-04-02T18:36:44.624Z
+publishedAt: 2024-04-02T18:36:44.624Z
 firstPublishedAt: 2023-03-28T16:34:55.990Z
 contentType: knownIssue
 productTeam: Catalog
@@ -23,7 +23,7 @@ internalReference: 739693
 </div>
 
 
-Atualmente, a carga útil do KIT API de inserção tem um formato que solicita os componentes que compõem este kit e suas quantidades e preços de acordo com as quantidades.
+Atualmente, a carga útil da API de inserção de KIT tem um formato que solicita os componentes que compõem esse kit e suas respectivas quantidades e preços.
 
 O preço esperado de um KIT deve ser uma soma ponderada dos preços de seus componentes * suas quantidades necessárias para compor o kit.
 
@@ -34,29 +34,20 @@ Componente (B) --> $25, 1 unidade
 
 O preço do kit deve ser: 10*2 + 25 === 45.
 
-Isto é o que acontece no KIT UI SkuKit.aspx.
+Isso é o que acontece no KIT UI SkuKit.aspx.
 
-Entretanto, a API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit não contabiliza múltiplos componentes na soma, portanto, o preço só considera cada componente uma vez no cálculo (então, nosso exemplo acima seria, incorretamente, 10 + 25 = 35).
+Entretanto, a API https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit não está fazendo essas atualizações de preço para outros componentes além do primeiro adicionado.
 
 
-
-
-
-##
-
 ## Simulação
 
 
-Crie um kit utilizando o seguinte API com um componente com uma quantidade de 2 ou mais https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit e depois verifique seu preço no módulo de preços UI.
-
-
-
+Crie um kit usando a seguinte API com um componente com uma quantidade de 2 ou mais https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunitkit e, em seguida, verifique seu preço na interface do usuário do módulo de preços.
 
 
-##
 
 ## Workaround
 
 
-Ao criar um kit, vá até a IU e salve os componentes mais uma vez para executar a lógica de cálculo da referida soma ponderada.
+Insira o preço final do kit diretamente por meio da API de preços.
 
diff --git a/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md b/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md
index c8c4c6b37..10192f13f 100644
--- a/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md
+++ b/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md
@@ -3,8 +3,8 @@ title: 'O peso do kit pode ser sobreescrito por API/Webservice'
 id: Dlrs4qgHsnwIHxqqV0Rmg
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:40.711Z
-updatedAt: 2022-11-25T21:43:12.999Z
-publishedAt: 2022-11-25T21:43:12.999Z
+updatedAt: 2024-02-16T20:29:08.522Z
+publishedAt: 2024-02-16T20:29:08.522Z
 firstPublishedAt: 2022-06-28T16:55:40.971Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: o-peso-do-kit-pode-ser-sobreescrito-por-apiwebservice
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429993
 ---
 
diff --git a/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md b/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
index 5065371cb..fab10d73c 100644
--- a/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
+++ b/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
@@ -1,16 +1,16 @@
 ---
-title: 'Konduto AF não pode completar um pedido quando falta a contaId.'
+title: 'O Konduto AF não pode concluir uma solicitação quando o accountId está ausente.'
 id: CGHZoCfr01ATsbtiLU9ym
 status: PUBLISHED
 createdAt: 2022-03-03T22:09:57.638Z
-updatedAt: 2022-11-25T22:05:52.845Z
-publishedAt: 2022-11-25T22:05:52.845Z
+updatedAt: 2023-06-20T17:54:26.840Z
+publishedAt: 2023-06-20T17:54:26.840Z
 firstPublishedAt: 2022-03-03T22:09:58.094Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: konduto-af-nao-pode-completar-um-pedido-quando-falta-a-contaid
+slug: o-konduto-af-nao-pode-concluir-uma-solicitacao-quando-o-accountid-esta-ausente
 locale: pt
 kiStatus: Backlog
 internalReference: 496298
@@ -23,22 +23,25 @@ internalReference: 496298
 </div>
 
 
+Há um problema para aprovar algumas transações relacionadas ao sistema antifraude da Konduto. Esse problema ocorre quando o sistema não consegue fazer a solicitação necessária devido à ausência do accountId, que é necessário para recuperar as informações de pagamento do banco de dados da conta. Você pode verificar isso examinando a rota "/payment", onde encontrará o nó "usedAccountId" com um valor de "False" nesses casos.
 
-Algumas transações não podem ser concluídas porque a Konduto antifraude não faz o pedido apropriado porque falta a conta utilizada para obter informações de pagamento na tabela de banco de dados da conta. Isto pode ser validado observando a rota de pagamento onde o nó "useAccountId" é falso neste caso.
-
-**{**"nome": "usedAccountId", "valor": "Falso "**}****
-
+**{**"name": "usedAccountId", "value": "False "**}**
 
+Além disso, esse problema é comumente observado quando um usuário remove seu próprio cartão da página MyAccount imediatamente após fazer um pedido.
 
 ## Simulação
 
 
-Este erro não pode ser reproduzido neste momento, ele ocorre de forma intermitente.
+Siga a etapa mencionada anteriormente, que envolve a exclusão de um cartão imediatamente após a realização de um pedido utilizando o Konduto Antifraud.
 
 
 
 ## Workaround
 
 
-Não há nenhuma solução disponível.
+N/A
+
+
+
+
 
diff --git a/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md b/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md
index 800a0378b..52e590de7 100644
--- a/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md
+++ b/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md
@@ -1,18 +1,18 @@
 ---
-title: 'Grande Erro de Planilha de Importação/Exportação em Nova Administração de Cobranças'
+title: 'Erro de planilha grande de importação/exportação no New Collections Admin'
 id: 6xbBVR2Z7CCpIC0iCAKHgN
 status: PUBLISHED
 createdAt: 2023-02-16T19:04:08.298Z
-updatedAt: 2023-02-16T19:04:08.784Z
-publishedAt: 2023-02-16T19:04:08.784Z
+updatedAt: 2023-12-12T21:08:23.871Z
+publishedAt: 2023-12-12T21:08:23.871Z
 firstPublishedAt: 2023-02-16T19:04:08.784Z
 contentType: knownIssue
 productTeam: Catalog
 author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
-slug: grande-erro-de-planilha-de-importacaoexportacao-em-nova-administracao-de-cobrancas
+slug: erro-de-planilha-grande-de-importacaoexportacao-no-new-collections-admin
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 362017
 ---
 
@@ -23,31 +23,22 @@ internalReference: 362017
 </div>
 
 
-Atualmente, o administrador da nova coleção, no recurso de importação para uma inclusão de SKU, usando a linha SKU, freqüentemente retorna uma resposta de erro não específica ao tentar importar um arquivo com muitos registros.
-
-"O seu arquivo não foi importado". Por favor, tente importar este arquivo novamente.`"
-
-
-##
+Atualmente, o carregamento de itens para o novo módulo de coleções com uma lista com mais de 1.000 SKUs é impossível, pois o processo atingirá o tempo limite. Ele retorna uma resposta de erro não específica:
+"Seu arquivo não foi importado. Tente importar esse arquivo novamente.`"
 
 ## Simulação
 
 
-1) Em uma loja em que o catálogo é muito grande, os produtos 50K+ acessam as novas coleções admin /admin/collections
-
-2) Em uma coleção, tente importar novos registros com mais de 100 SKUs em uma única importação.
 
-
-##
+1. Vá para o novo módulo de coleções
+2. Selecione a guia "Import" (Importar)
+3. Use uma planilha que tenha mais de 1.000 SKUs (ou seja, 300 produtos com 50 SKUs cada)
+4. A importação gerará um tempo limite
 
 ## Workaround
 
 
-1) Utilizar as coleções legadas para a importação maciça de SKUs.
-
-2) Dividir as importações em folhas menores e fazer o processo gradualmente.
-
-3) Utilizar as ações maciças da IU para atingir o efeito desejado.
+Faça o upload gradualmente usando planilhas menores, as coleções legadas do CMS e/ou a API de inserção de SKU na subcoleção https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/subcollection/-subCollectionId-/stockkeepingunit
 
 
 
diff --git a/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md b/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
index a4be4b1f3..d55cdecb8 100644
--- a/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
+++ b/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
@@ -1,18 +1,18 @@
 ---
-title: 'O envio enxuto sendo forçado mesmo quando os itens têm os mesmos SLAs, mas em uma ordenação diferente'
+title: 'O envio enxuto é forçado mesmo quando os itens têm os mesmos SLAs, mas em uma ordenação diferente'
 id: 2YTqsVWPm73msQZVQX9x80
 status: PUBLISHED
 createdAt: 2022-05-13T17:26:15.513Z
-updatedAt: 2022-11-25T21:52:30.793Z
-publishedAt: 2022-11-25T21:52:30.793Z
+updatedAt: 2023-09-11T21:38:39.068Z
+publishedAt: 2023-09-11T21:38:39.068Z
 firstPublishedAt: 2022-05-13T17:26:16.378Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: o-envio-enxuto-sendo-forcado-mesmo-quando-os-itens-tem-os-mesmos-slas-mas-em-uma-ordenacao-diferente
+slug: o-envio-enxuto-e-forcado-mesmo-quando-os-itens-tem-os-mesmos-slas-mas-em-uma-ordenacao-diferente
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 455218
 ---
 
@@ -23,12 +23,19 @@ internalReference: 455218
 </div>
 
 
+Em alguns cenários, é possível que, mesmo que o recurso LeanShipping esteja desativado nas configurações, o sistema ainda considere necessário agrupar as opções de envio e, com isso, não desative o LeanShipping, isso porque a regra usada pelo sistema para definir o uso ou não do LeanShipping além da configuração está ativada ou desativada e há SLAs iguais ou diferentes disponíveis para os itens do carrinho;
+No entanto, há cenários em que apenas a ordem de como os SLAs são entregues faz com que o sistema entenda que são SLAs diferentes e ative o leanShipping no checkout e comece a exibir as etiquetas mais rápidas e mais baratas para o método de envio.
 
 ## Simulação
 
 
+Não há uma maneira linear de replicar o cenário, mas ele pode ocorrer sempre que tivermos um carrinho com dois ou mais itens cujos slas sejam semelhantes entre os itens e que estejam sendo apresentados em ordens diferentes dentro do objeto sla de cada item
 
 ## Workaround
 
 
+N/A
+
+
+
 
diff --git a/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
new file mode 100644
index 000000000..3366f853c
--- /dev/null
+++ b/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -0,0 +1,47 @@
+---
+title: 'O transporte enxuto causa "Algo deu errado" depois de mudar os pontos de coleta'
+id: 45jQODtjZ4vLXniNJIlQZc
+status: PUBLISHED
+createdAt: 2024-06-20T21:11:53.067Z
+updatedAt: 2024-06-20T21:15:28.608Z
+publishedAt: 2024-06-20T21:15:28.608Z
+firstPublishedAt: 2024-06-20T21:11:53.899Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-transporte-enxuto-causa-algo-deu-errado-depois-de-mudar-os-pontos-de-coleta
+locale: pt
+kiStatus: Backlog
+internalReference: 1053609
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Um comprador pode pesquisar diferentes pontos de coleta em diferentes códigos postais. Ao usar o envio enxuto, depois de adicionar um código postal com pontos de coleta disponíveis e mudar para um código postal sem pontos de coleta, a etapa de envio é bloqueada com a mensagem "Algo deu errado".
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/i0jCDFlz5EGPnKyk5Nfw0Etl0/?name=image.png)
+
+## Simulação
+
+
+
+- Monte um carrinho e selecione a retirada no ponto no carrinho;
+- Adicione um código postal com a retirada;
+- Selecione uma das coletas
+- Alterar para um código postal sem pontos de retirada;
+- Vá para o checkout e a mensagem "Something went wrong" (Algo deu errado) é exibida na etapa de envio
+
+## Workaround
+
+
+Atualize a página ou desative o envio enxuto.
+
+
+
+
diff --git a/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md b/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
new file mode 100644
index 000000000..347032e3a
--- /dev/null
+++ b/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
@@ -0,0 +1,44 @@
+---
+title: 'O Lean Shipping não é desativado após a remoção de itens do carrinho'
+id: 4dZZz28csz9BLhJNvQGHQV
+status: PUBLISHED
+createdAt: 2023-10-09T14:20:03.767Z
+updatedAt: 2023-10-09T14:20:04.692Z
+publishedAt: 2023-10-09T14:20:04.692Z
+firstPublishedAt: 2023-10-09T14:20:04.692Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-lean-shipping-nao-e-desativado-apos-a-remocao-de-itens-do-carrinho
+locale: pt
+kiStatus: Backlog
+internalReference: 916461
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O Lean Shipping não é desativado automaticamente após a remoção de itens do carrinho, mantendo apenas um onde deveria mostrar todas as opções.
+
+## Simulação
+
+
+
+- Adicione 2 ou mais itens de vendedores diferentes que tenham SLAs diferentes;
+- O envio enxuto estará ativo;
+- Remover todos os itens, mantendo apenas 1;
+- O envio enxuto ainda estará ativo
+
+## Workaround
+
+
+Atualizar a página
+
+
+
+
diff --git a/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
new file mode 100644
index 000000000..277053d8a
--- /dev/null
+++ b/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
@@ -0,0 +1,39 @@
+---
+title: 'O botão "excluir" da interface do usuário do catálogo legado não funciona'
+id: 2soNSJfiQMZcxlpW6jT2FR
+status: PUBLISHED
+createdAt: 2022-01-23T02:51:17.884Z
+updatedAt: 2024-05-21T16:03:51.417Z
+publishedAt: 2024-05-21T16:03:51.417Z
+firstPublishedAt: 2024-05-21T16:03:51.417Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-botao-excluir-da-interface-do-usuario-do-catalogo-legado-nao-funciona
+locale: pt
+kiStatus: Backlog
+internalReference: 326408
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O botão para excluir produtos no catálogo não está funcionando, ele simplesmente não reconhece nenhum clique do usuário
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/ZR7ogOzhfLN3yC61V9RzTMRlZ/?name=inline-652081372.png)
+
+Essa ação pode funcionar se o produto tiver acabado de ser criado e não houver skus, imagens ou qualquer outro tipo de dados associados a ele.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md b/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md
new file mode 100644
index 000000000..8fb887ecc
--- /dev/null
+++ b/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md
@@ -0,0 +1,54 @@
+---
+title: 'O elemento personalizado de banner do CMS legado não está funcionando'
+id: 3ezW1BTc2nSvHpp0mAYhwh
+status: PUBLISHED
+createdAt: 2024-02-07T13:44:20.722Z
+updatedAt: 2024-02-07T13:44:21.554Z
+publishedAt: 2024-02-07T13:44:21.554Z
+firstPublishedAt: 2024-02-07T13:44:21.554Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-elemento-personalizado-de-banner-do-cms-legado-nao-esta-funcionando
+locale: pt
+kiStatus: Backlog
+internalReference: 978466
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, a guia "elementos personalizados" das configurações do CMS legado não está funcionando corretamente.
+
+A configuração de um elemento personalizado desse tipo não produzirá efeitos na maioria dos casos, e recomenda-se configurá-lo diretamente no HTML do layout.
+
+Isso só ocorre em lojas de modelos herdadas.
+
+## Simulação
+
+
+1 - vá para o CMS antigo e selecione a guia de elementos personalizados
+2 - Carregue um elemento personalizado do tipo "banner".
+3 - faça referência a esse banner em seu html
+4 - o banner configurado não será renderizado corretamente
+
+
+
+## Workaround
+
+
+Configure os banners usando o layout HTML do tipo e/ou os subtemplates associados a ele.
+
+OU
+
+migrar para a estrutura de loja da VTEX
+
+
+
+
+
diff --git a/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md b/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
index f5f9274d6..35253f2c5 100644
--- a/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
+++ b/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
@@ -3,8 +3,8 @@ title: 'Filtro da categoria UI Legacy Collection selecionando produtos erroneame
 id: 1IlioZpOSQf5t4TWqZreiS
 status: PUBLISHED
 createdAt: 2022-10-31T20:42:26.100Z
-updatedAt: 2022-12-20T16:37:12.340Z
-publishedAt: 2022-12-20T16:37:12.340Z
+updatedAt: 2024-02-16T20:28:22.357Z
+publishedAt: 2024-02-16T20:28:22.357Z
 firstPublishedAt: 2022-10-31T20:42:26.591Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: filtro-da-categoria-ui-legacy-collection-selecionando-produtos-erroneamente-para-a-colecao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 590934
 ---
 
diff --git a/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md b/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
new file mode 100644
index 000000000..8daacbb3b
--- /dev/null
+++ b/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
@@ -0,0 +1,46 @@
+---
+title: 'O modelo de parcelamento legado e os controles de prateleira não consideram os multiplicadores de unidades'
+id: 1E0Co7ssCUAKAgxCzlJoVn
+status: PUBLISHED
+createdAt: 2024-02-08T13:39:40.663Z
+updatedAt: 2024-02-08T13:48:30.740Z
+publishedAt: 2024-02-08T13:48:30.740Z
+firstPublishedAt: 2024-02-08T13:39:41.744Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: o-modelo-de-parcelamento-legado-e-os-controles-de-prateleira-nao-consideram-os-multiplicadores-de-unidades
+locale: pt
+kiStatus: Backlog
+internalReference: 979205
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, para a loja que usa o CMS legado, o modelo legado e os controles de prateleira não são ajustados se o SKU tiver um multiplicador de unidades.
+
+Por exemplo, se você tiver um item com um multiplicador de unidades de 2 e um controlador de parcelamento, os dados exibidos nas prateleiras mostrarão apenas as opções de parcelamento de uma única unidade, em vez de se ajustarem a essa configuração.
+
+## Simulação
+
+
+1 - criar um sku com um multiplicador de unidades
+2 - configure opções de parcelamento para ele
+3 - configure um controlador relacionado a parcelas, como $product.InstallmentValue
+4 - os dados exibidos serão relativos a uma única unidade, apenas
+
+## Workaround
+
+
+implemente uma personalização de front-end para substituir os dados originais que estão sendo exibidos.
+
+
+
+
+
diff --git a/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md b/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md
index 1fe1268ca..dcd416037 100644
--- a/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md
+++ b/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md
@@ -3,8 +3,8 @@ title: 'Os textos do controle Avise-me não estão sendo traduzidos'
 id: 4UXWf34IXNVAEKgH4hQLTx
 status: PUBLISHED
 createdAt: 2022-02-03T17:18:23.078Z
-updatedAt: 2022-12-02T18:35:11.786Z
-publishedAt: 2022-12-02T18:35:11.786Z
+updatedAt: 2024-02-16T20:26:19.991Z
+publishedAt: 2024-02-16T20:26:19.991Z
 firstPublishedAt: 2022-02-03T17:18:23.416Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: os-textos-do-controle-avise-me-nao-estao-sendo-traduzidos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 517165
 ---
 
diff --git a/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md b/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
new file mode 100644
index 000000000..068da9990
--- /dev/null
+++ b/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
@@ -0,0 +1,46 @@
+---
+title: 'LINK SERVICE VALUES TO SKUS planilha que retorna apenas os serviços ativos'
+id: 1FqAokiJLWwWnsPodyTMKY
+status: PUBLISHED
+createdAt: 2023-08-23T17:51:58.839Z
+updatedAt: 2023-08-23T17:51:59.677Z
+publishedAt: 2023-08-23T17:51:59.677Z
+firstPublishedAt: 2023-08-23T17:51:59.677Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: link-service-values-to-skus-planilha-que-retorna-apenas-os-servicos-ativos
+locale: pt
+kiStatus: Backlog
+internalReference: 886486
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao exportar valores de serviços de uma categoria específica no admin, o resultado está trazendo apenas os serviços ativos. Não permitindo que o comerciante ative serviços anteriormente inativos por planilha.
+
+## Simulação
+
+
+
+1. Crie um serviço e associe-o a um sku;
+2. Inative o serviço no sku;
+3. Exportar a planilha LINK SERVICE VALUES TO SKUS;
+4. Verifique se o serviço anterior não foi devolvido
+
+## Workaround
+
+
+Use a API ou vá diretamente para o sku - administrador de serviços para atualizar o serviço:
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/skuservice/-skuServiceId-
+
+
+
+
+
diff --git a/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index 4ea3d3285..993b339c9 100644
--- a/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -3,8 +3,8 @@ title: 'Link "Por que preencher a categoria VTEX Global?" na configuração da c
 id: 3u7aq2otUovQbO98lzjbus
 status: PUBLISHED
 createdAt: 2022-03-16T17:59:14.355Z
-updatedAt: 2022-12-20T16:36:51.563Z
-publishedAt: 2022-12-20T16:36:51.563Z
+updatedAt: 2024-02-16T20:23:34.672Z
+publishedAt: 2024-02-16T20:23:34.672Z
 firstPublishedAt: 2022-03-16T17:59:14.784Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: link-por-que-preencher-a-categoria-vtex-global-na-configuracao-da-categoria-so-funciona-abrindo-em-uma-nova-aba
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 544034
 ---
 
diff --git a/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
new file mode 100644
index 000000000..d8c3a4b6a
--- /dev/null
+++ b/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -0,0 +1,90 @@
+---
+title: 'O linkId não está sendo registrado no rewriter ao traduzir com o catálogo graphql'
+id: 7b7KOHlxyIO4zKy2xrMuSD
+status: PUBLISHED
+createdAt: 2022-09-08T21:27:03.855Z
+updatedAt: 2024-07-10T12:47:32.306Z
+publishedAt: 2024-07-10T12:47:32.306Z
+firstPublishedAt: 2022-09-08T21:27:04.567Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-linkid-nao-esta-sendo-registrado-no-rewriter-ao-traduzir-com-o-catalogo-graphql
+locale: pt
+kiStatus: Backlog
+internalReference: 654951
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o catálogo graphQL e traduzir o URL usando o linkId, o reescritor deve armazenar o linkId, mas isso não está acontecendo: https://developers.vtex.com/docs/guides/catalog-internationalization
+
+## Simulação
+
+
+
+- Siga o guia de documentação para traduzir o conteúdo do catálogo: https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization#mutation
+- **Para links de categoria:**
+  - Verifique o linkId que você criou em admin/graphql-ide e escolha o aplicativo de reescrita:
+
+    { internal{ get(path: "yourLinkdIdHere"){ id } }}
+
+
+
+- Isso retornará nulo;
+- Verifique novamente com o nome de sua categoria traduzida, mas com a slugificação:
+
+    { internal{ get(path: "yourTranslatedCategoryNameSlugified"){ id } }}
+
+
+
+- Isso retornará resultados.
+
+
+
+- Para links de produtos:**
+  - Acesse a página do produto usando o link traduzido criado usando o graphQL do catálogo;
+  - Será exibido um erro 404 Not Found.
+
+
+
+## Workaround
+
+
+
+- **Para links de categoria:**
+  - Execute a seguinte consulta no rewriter:
+
+    { internal{ get(path: "yourTranslatedLinkdId"){ id from declarer type query binding origin resolveAs } }}
+
+
+
+- Salve os valores retornados, pois você precisará usá-los na próxima etapa;
+- Execute a seguinte mutação, alterando apenas o parâmetro from; os outros devem ser iguais aos anteriores:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "yourLinkId", "declarer": "yourSavedDeclarer", "type": "yourSavedType", "binding": "yourSavedBinding", "id": "yourSavedId", "origin": "yourSavedOrigin", "resolveAs": "yourSavedResolveAs" }}
+
+> Para obter mais informações sobre esses parâmetros, consulte: https://developers.vtex.com/vtex-developer-docs/docs/rewriter
+
+
+
+- Agora, vamos excluir a rota antiga (a que foi salva com o nome)
+
+    mutation saveInternal($route: InternalInput!) { internal { delete(path: "yourTranslatedLinkdId") { id } }}
+
+
+
+- **Para links de produtos:**
+  - Execute a seguinte mutação alterando apenas o parâmetro from; os outros devem ser iguais aos anteriores:
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "/yourTranslatedLinkdId/p", "declarer": "vtex.store@2.x", "type": "product", "id": "productId", "resolveAs": "/yourOrinalLinkdId/p", "binding": "bindingId" }}
+
+
+
+
diff --git a/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md b/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md
index db514a76e..28b46a53b 100644
--- a/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md
+++ b/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md
@@ -3,8 +3,8 @@ title: 'O Locale Switcher não funciona no ambiente myvtex'
 id: 1ZB56egPjPbTaUUnws5juK
 status: PUBLISHED
 createdAt: 2023-03-27T12:26:31.974Z
-updatedAt: 2023-03-27T14:55:12.486Z
-publishedAt: 2023-03-27T14:55:12.486Z
+updatedAt: 2024-02-02T21:03:39.535Z
+publishedAt: 2024-02-02T21:03:39.535Z
 firstPublishedAt: 2023-03-27T12:26:32.649Z
 contentType: knownIssue
 productTeam: Store Framework
diff --git a/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md b/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md
new file mode 100644
index 000000000..2f455fb4d
--- /dev/null
+++ b/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md
@@ -0,0 +1,53 @@
+---
+title: 'A preferência de login com senha não pode ser desfeita no Admin'
+id: 5OPVJusw14TQzKdAVS71wx
+status: PUBLISHED
+createdAt: 2024-04-22T13:30:15.401Z
+updatedAt: 2024-05-06T20:40:26.631Z
+publishedAt: 2024-05-06T20:40:26.631Z
+firstPublishedAt: 2024-04-22T13:30:16.436Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: a-preferencia-de-login-com-senha-nao-pode-ser-desfeita-no-admin
+locale: pt
+kiStatus: Backlog
+internalReference: 1020548
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário faz logon na plataforma VTEX pela primeira vez (Admin), ele é solicitado a escolher sua preferência de login para a próxima vez que fizer logon. Em seguida, ele pode escolher entre digitar seu endereço de e-mail e senha ou digitar um código que será enviado para seu endereço de e-mail;
+
+No entanto, quando o usuário opta por inserir seu endereço de e-mail e senha, ele não pode desfazer essa escolha, pois é uma escolha irrevogável no nível da interface do usuário, e é necessária uma ação sistêmica para desfazer essa escolha.
+
+## Simulação
+
+
+**NOTA**: Para simular esse cenário, você deve fazer login pela primeira vez;
+
+Faça login no admin
+
+Digite seu endereço de e-mail e crie uma senha;
+
+Nesse momento, será perguntado se você deseja continuar recebendo o código de acesso ou se deseja que o sistema sempre solicite seu endereço de e-mail e senha.
+
+Solicite que você sempre faça login usando seu endereço de e-mail e senha.
+
+Na próxima vez que fizer login, não será possível desfazer sua escolha de login e sempre serão solicitados seu endereço de e-mail e senha
+
+## Workaround
+
+
+Para que o usuário possa fazer uma nova escolha, é necessário solicitar à equipe de engenharia que revogue a preferência salva no perfil do usuário, de modo que, em seu próximo login, ele seja questionado novamente sobre sua preferência de login e possa fazer uma nova escolha
+
+
+
+
+
diff --git a/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md b/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
index 50344033b..bc1e1d16e 100644
--- a/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
+++ b/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
@@ -3,8 +3,8 @@ title: 'Simulação Logística com preço mínimo e máximo na Política de Emba
 id: 5gsBLbPMIZjZvkl5QHudVY
 status: PUBLISHED
 createdAt: 2022-03-30T20:10:30.205Z
-updatedAt: 2022-11-25T21:59:57.297Z
-publishedAt: 2022-11-25T21:59:57.297Z
+updatedAt: 2024-02-16T20:26:15.370Z
+publishedAt: 2024-02-16T20:26:15.370Z
 firstPublishedAt: 2022-05-17T14:23:38.006Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: simulacao-logistica-com-preco-minimo-e-maximo-na-politica-de-embarque-nao-funciona-quando-o-preco-do-produto-como-0-zero
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 553080
 ---
 
diff --git a/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md b/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
index e352d7487..f7d03cb88 100644
--- a/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
+++ b/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
@@ -3,8 +3,8 @@ title: 'Faça um loop na janela pop-up de autenticação quando a primeira condi
 id: 7fU6wnrTjS0aJqRmertSFg
 status: PUBLISHED
 createdAt: 2023-06-14T17:54:36.973Z
-updatedAt: 2023-06-14T17:55:47.281Z
-publishedAt: 2023-06-14T17:55:47.281Z
+updatedAt: 2023-12-21T15:50:16.992Z
+publishedAt: 2023-12-21T15:50:16.992Z
 firstPublishedAt: 2023-06-14T17:54:37.537Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md b/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
index c34100aa5..b3a1d889f 100644
--- a/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
+++ b/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
@@ -3,8 +3,8 @@ title: '[Magalu] Sku sendo integrado com especificações de outro marketplace'
 id: 4AYsfMTB2HVmp2PnOG2plY
 status: PUBLISHED
 createdAt: 2022-10-31T19:29:16.911Z
-updatedAt: 2022-12-02T18:30:12.315Z
-publishedAt: 2022-12-02T18:30:12.315Z
+updatedAt: 2024-03-19T20:33:58.929Z
+publishedAt: 2024-03-19T20:33:58.929Z
 firstPublishedAt: 2022-10-31T19:29:18.080Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: magalu-sku-sendo-integrado-com-especificacoes-de-outro-marketplace
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 689151
 ---
 
diff --git a/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md b/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
new file mode 100644
index 000000000..892c202d8
--- /dev/null
+++ b/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
@@ -0,0 +1,47 @@
+---
+title: '[Magazine Luiza] Pedido cancelado no marketplace não atualizou o status na VTEX'
+id: 4C1G20Iwj6x1mvqzsSDU0P
+status: PUBLISHED
+createdAt: 2023-07-20T15:33:25.631Z
+updatedAt: 2023-07-20T15:33:26.222Z
+publishedAt: 2023-07-20T15:33:26.222Z
+firstPublishedAt: 2023-07-20T15:33:26.222Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: magazine-luiza-pedido-cancelado-no-marketplace-nao-atualizou-o-status-na-vtex
+locale: pt
+kiStatus: Backlog
+internalReference: 865926
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A ordem cancelada no marketplace não atualizou o status na VTEX
+
+**Marketplace:** Magazine Luiza
+**Causa Raiz:** Integração do pedido
+**Tipo:** Status não atualizado no marketplace
+**Impacto:** Poucos pedidos
+
+## Simulação
+
+
+Nenhum erro foi encontrado nos registros, mas o pedido no OMS/VTEX é "faturado", mas no marketplace o pedido está como "cancelado".
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md b/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md
new file mode 100644
index 000000000..8fe8d93ce
--- /dev/null
+++ b/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md
@@ -0,0 +1,51 @@
+---
+title: '[Magazine Luiza] Alguns skus não atualizam o preço'
+id: NXb7Bb4BTJepPphcK9z0V
+status: PUBLISHED
+createdAt: 2023-08-17T14:14:36.434Z
+updatedAt: 2023-08-17T14:14:37.098Z
+publishedAt: 2023-08-17T14:14:37.098Z
+firstPublishedAt: 2023-08-17T14:14:37.098Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: magazine-luiza-alguns-skus-nao-atualizam-o-preco
+locale: pt
+kiStatus: Backlog
+internalReference: 882919
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Precisamos entender por que alguns skus não atualizam o preço no marketplace.
+Importante: não acontece com todas as skus
+
+## Simulação
+
+
+Fluxo: preço atualizado no catálogo da VTEX
+
+emissora
+recebeu notificação de alteração de preço
+
+Integração
+recebeu notificação de modificação de preço
+
+mercado
+O preço não foi atualizado e nenhum erro foi encontrado no registr
+
+## Workaround
+
+
+Reindexar o sku no catálogo da VTEX
+
+
+
+
+
diff --git a/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md b/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
new file mode 100644
index 000000000..3819cf842
--- /dev/null
+++ b/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
@@ -0,0 +1,48 @@
+---
+title: "[Magazine Luiza] [tracking] Erro: Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"
+id: 7ublDwKHM4JJxsCtcbLqq8
+status: PUBLISHED
+createdAt: 2023-07-06T14:06:45.020Z
+updatedAt: 2023-07-06T14:06:45.783Z
+publishedAt: 2023-07-06T14:06:45.783Z
+firstPublishedAt: 2023-07-06T14:06:45.783Z
+contentType: knownIssue
+productTeam: Admin
+author: 2mXZkbi0oi061KicTExNjo
+tag: Admin
+slug: magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje
+locale: pt
+kiStatus: Backlog
+internalReference: 856984
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na etapa de rastreamento, alguns pedidos estão retornando o seguinte erro `"Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"`
+
+**Marketplace:** Magazine Luiza
+**Status:** rastreamento
+**Impacto:** Alguns pedidos
+
+## Simulação
+
+
+1. Integrações
+2. Ponte
+3. Rastreamento
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/mlpzu59MIDWuvUP6n8zJc8GI6/?name=image.png
+
+## Workaround
+
+
+Normalmente, reprocessar manualmente a solicitação da ponte corrige o erro.
+
+
+
+
diff --git a/docs/known-issues/pt/mandatory-service-working-as-optional.md b/docs/known-issues/pt/mandatory-service-working-as-optional.md
new file mode 100644
index 000000000..8c23bcbe3
--- /dev/null
+++ b/docs/known-issues/pt/mandatory-service-working-as-optional.md
@@ -0,0 +1,44 @@
+---
+title: 'Serviço obrigatório funcionando como opcional'
+id: 6bcdioCSYL7ZGoOy0nEtJC
+status: PUBLISHED
+createdAt: 2023-08-01T15:15:29.008Z
+updatedAt: 2023-08-01T15:15:30.099Z
+publishedAt: 2023-08-01T15:15:30.099Z
+firstPublishedAt: 2023-08-01T15:15:30.099Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: servico-obrigatorio-funcionando-como-opcional
+locale: pt
+kiStatus: Backlog
+internalReference: 872411
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar um serviço, o comerciante pode escolher se será um campo obrigatório no checkout ou não.
+No entanto, atualmente essa funcionalidade não está funcionando como esperado. Mesmo quando o campo obrigatório é marcado como verdadeiro, o produto pode ser comprado sem adicioná-lo no checkout.
+
+## Simulação
+
+
+
+1. Crie um serviço como obrigatório;
+2. Associe-o a um sku;
+3. Verifique se, no checkout, o serviço pode ser adicionado ou removido sem problemas
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md b/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
new file mode 100644
index 000000000..6384fe2d6
--- /dev/null
+++ b/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
@@ -0,0 +1,43 @@
+---
+title: 'marketingData não é salvo nos pedidos ao usar o recurso de vários cupons e utms'
+id: OUMc8x9sEcdp8ZbLIka4b
+status: PUBLISHED
+createdAt: 2023-11-22T21:53:36.924Z
+updatedAt: 2024-04-09T13:33:02.091Z
+publishedAt: 2024-04-09T13:33:02.091Z
+firstPublishedAt: 2023-11-22T21:53:37.493Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketingdata-nao-e-salvo-nos-pedidos-ao-usar-o-recurso-de-varios-cupons-e-utms
+locale: pt
+kiStatus: Fixed
+internalReference: 936458
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o recurso de vários cupons e houver cupons e utms, ou 'marketingTags', no 'orderForm', nenhum 'marketingData' é salvo no pedido.
+
+## Simulação
+
+
+
+- Tenha uma conta usando o recurso de vários cupons;
+- Use um cupom e defina qualquer utm ou 'marketingTags', ambos devem estar no formulário de pedido;
+- Concluir a compra; não haverá nenhum 'marketingData' no pedido
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md b/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md
new file mode 100644
index 000000000..7206576fb
--- /dev/null
+++ b/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md
@@ -0,0 +1,43 @@
+---
+title: 'marketingTags com valor nulo quando o público-alvo da campanha é correspondido'
+id: 17pTWB1gLNJgFy7KEZd8pk
+status: PUBLISHED
+createdAt: 2024-06-19T20:08:49.413Z
+updatedAt: 2024-06-19T20:08:50.452Z
+publishedAt: 2024-06-19T20:08:50.452Z
+firstPublishedAt: 2024-06-19T20:08:50.452Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: marketingtags-com-valor-nulo-quando-o-publicoalvo-da-campanha-e-correspondido
+locale: pt
+kiStatus: Backlog
+internalReference: 1052895
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma conta tem um público-alvo de campanha e um usuário conectado é correspondido, o checkout usa as informações registradas na sessão, que tem apenas o ID da campanha. Em `marketingTags`, ele deveria ter o nome da campanha, mas é `nulo`, pois não há informações disponíveis na sessão.
+
+## Simulação
+
+
+
+- Crie um público-alvo de campanha;
+- Faça login com um usuário ao qual a campanha corresponda;
+- Verifique o campo `marketingData.marketingTags` no formulário de pedido, ele terá um valor nulo e o nome da campanha.
+ ![](https://vtexhelp.zendesk.com/attachments/token/1i6d9cIyg1Hx2fs9QsVZ6BFCY/?name=image.png
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md b/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
new file mode 100644
index 000000000..6129644c7
--- /dev/null
+++ b/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
@@ -0,0 +1,47 @@
+---
+title: 'O Marketplace e o Fulfillment podem esperar valores de pedidos diferentes devido a determinadas condições de compra'
+id: 5LoC3DwesBWH5kr2b5u6WD
+status: PUBLISHED
+createdAt: 2024-05-13T20:04:19.094Z
+updatedAt: 2024-05-13T20:34:01.432Z
+publishedAt: 2024-05-13T20:34:01.432Z
+firstPublishedAt: 2024-05-13T20:04:20.144Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-marketplace-e-o-fulfillment-podem-esperar-valores-de-pedidos-diferentes-devido-a-determinadas-condicoes-de-compra
+locale: pt
+kiStatus: Backlog
+internalReference: 1032473
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As camadas do Marketplace e do Fulfillment podem esperar valores diferentes para o pedido, impedindo a conclusão da compra.
+Nesses casos, o `sellingPrice` do Marketplace para o item não corresponde ao `price` do Fulfillment.
+
+## Simulação
+
+
+O problema não está necessariamente restrito a esse passo a passo exato, mas é mais fácil de reproduzir da seguinte forma:
+
+1. Defina as casas decimais do Marketplace e do vendedor como zero.
+2. Na conta do vendedor, defina o preço de um item como 49950,00 e uma promoção de Fulfillment que aplique um desconto de 15% a ele.
+3. Em um Marketplace, adicione 3 unidades do item do vendedor ao seu carrinho.
+4. Tente concluir a compra. A mensagem de erro "O pedido solicitado não pôde ser criado. Please try again." será exibida
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
new file mode 100644
index 000000000..ecafa901c
--- /dev/null
+++ b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
@@ -0,0 +1,43 @@
+---
+title: 'A solicitação do hub de impostos do Marketplace não considera o preço manual para descontos'
+id: 2pGgbPB7Qm4dXtQauohvx7
+status: PUBLISHED
+createdAt: 2023-11-08T17:59:41.102Z
+updatedAt: 2023-12-06T19:27:50.006Z
+publishedAt: 2023-12-06T19:27:50.006Z
+firstPublishedAt: 2023-11-08T17:59:41.695Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-solicitacao-do-hub-de-impostos-do-marketplace-nao-considera-o-preco-manual-para-descontos
+locale: pt
+kiStatus: Fixed
+internalReference: 932657
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a conta tem isMarketplaceResponsibleForTaxes configurado, a solicitação do hub de impostos não considera preços manuais para descontos de itens.
+
+## Simulação
+
+
+
+- Configure taxConfiguration.isMarketplaceResponsibleForTaxes na configuração do orderForm;
+- Definir o preço manual de um item;
+- A solicitação do hub de impostos não aplicará a diferença como um desconto
+
+## Workaround
+
+
+NA
+
+
+
+
diff --git a/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
new file mode 100644
index 000000000..87bd27dc1
--- /dev/null
+++ b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
@@ -0,0 +1,42 @@
+---
+title: 'A solicitação do hub fiscal do Marketplace não considera alguns tipos de desconto'
+id: 630nSPu8y5G6CSFtiH3MOL
+status: PUBLISHED
+createdAt: 2023-11-30T21:14:13.709Z
+updatedAt: 2023-12-06T19:27:05.930Z
+publishedAt: 2023-12-06T19:27:05.930Z
+firstPublishedAt: 2023-11-30T21:14:14.259Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-solicitacao-do-hub-fiscal-do-marketplace-nao-considera-alguns-tipos-de-desconto
+locale: pt
+kiStatus: Fixed
+internalReference: 945580
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a conta tem isMarketplaceResponsibleForTaxes configurado, a solicitação do hub de impostos não considera alguns tipos de desconto: Nominal, Porcentagem e Preço máximo por item. Isso afeta o cálculo do imposto, e o preço final é maior do que o esperado.
+
+## Simulação
+
+
+
+- Configure taxConfiguration.isMarketplaceResponsibleForTaxes na configuração do orderForm;
+- Configure um dos tipos de desconto Nominal, Percentual ou Preço máximo por item da promoção regular;
+- A solicitação do hub de impostos não aplicará o desconto
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md b/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md
new file mode 100644
index 000000000..2cb4793c2
--- /dev/null
+++ b/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md
@@ -0,0 +1,43 @@
+---
+title: 'As transações com cartão de crédito Mastercard estão sendo processadas como Visa'
+id: 4B547KIrO7xBUWdCUhPkjs
+status: PUBLISHED
+createdAt: 2024-05-02T19:12:19.672Z
+updatedAt: 2024-05-02T19:12:20.545Z
+publishedAt: 2024-05-02T19:12:20.545Z
+firstPublishedAt: 2024-05-02T19:12:20.545Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: as-transacoes-com-cartao-de-credito-mastercard-estao-sendo-processadas-como-visa
+locale: pt
+kiStatus: Backlog
+internalReference: 1026263
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas transações estão sendo registradas erroneamente sob a marca Visa, quando na verdade os cartões são Mastercard. Esse problema ocorre especificamente com cartões novos, embora possamos verificar se o BIN do cartão corresponde corretamente ao regex do validador para a marca correta.
+
+## Simulação
+
+
+Não foi possível replicar esse problema.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/masterdata-export-download-link-unavailable.md b/docs/known-issues/pt/masterdata-export-download-link-unavailable.md
index 842c586a1..8f4cd08cf 100644
--- a/docs/known-issues/pt/masterdata-export-download-link-unavailable.md
+++ b/docs/known-issues/pt/masterdata-export-download-link-unavailable.md
@@ -1,16 +1,16 @@
 ---
-title: 'Link para download do Masterdata Export Não disponível'
+title: 'Link de download do Masterdata Export indisponível'
 id: 2oi0ABhQQxfPsKETeNUyvE
 status: PUBLISHED
 createdAt: 2022-07-08T13:50:43.220Z
-updatedAt: 2023-01-19T14:19:49.870Z
-publishedAt: 2023-01-19T14:19:49.870Z
+updatedAt: 2023-07-28T17:14:13.207Z
+publishedAt: 2023-07-28T17:14:13.207Z
 firstPublishedAt: 2022-07-08T13:50:43.638Z
 contentType: knownIssue
 productTeam: Storage
 author: 2mXZkbi0oi061KicTExNjo
 tag: Storage
-slug: link-para-download-do-masterdata-export-nao-disponivel
+slug: link-de-download-do-masterdata-export-indisponivel
 locale: pt
 kiStatus: Backlog
 internalReference: 613864
@@ -23,26 +23,20 @@ internalReference: 613864
 </div>
 
 
-Atualmente, para entidades de dados com vários campos, quando há uma tentativa de exportar uma folha e baixá-la, tanto via e-mail ou diretamente via UI, o link de download não salva o arquivo em seu navegador.
+Atualmente, para entidades de dados com vários campos, quando há uma tentativa de exportar uma planilha e baixá-la, por e-mail ou diretamente pela interface do usuário, o link de download não salva o arquivo em seu navegador.
 
 
-
-##
-
 ## Simulação
 
 
-1 - para uma entidade de dados na qual você tem vários campos, tente exportar todos os seus campos ao mesmo tempo ou vários registros
-
-2 - o link para download não irá gerar um arquivo em seu navegador
-
- ![](https://vtexhelp.zendesk.com/attachments/token/nQdUqbk7BiOK5RcigZhNZR9Rr/?name=image.png)
+1 - para uma entidade de dados com vários campos, tente exportar todos os seus campos ao mesmo tempo ou vários registros
 
+2 - o link de download não gerará um arquivo em seu navegador
 
-##
+ ![](https://vtexhelp.zendesk.com/attachments/token/nQdUqbk7BiOK5RcigZhNZR9Rr/?name=image.png
 
 ## Workaround
 
 
-buscar dados via API https://developers.vtex.com/docs/api-reference/masterdata-api#get-/api/dataentities/-acronym-/search e/ou baixar dados em várias planilhas menores
+**Clique com o botão direito do mouse no link Download e copie o link; em seguida, cole o link em outra guia e o download será iniciado ou** busque dados via API https://developers.vtex.com/docs/api-reference/masterdata-api#get-/api/dataentities/-acronym-/search e/ou baixe os dados em várias planilhas menores
 
diff --git a/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
new file mode 100644
index 000000000..c9e80cd7c
--- /dev/null
+++ b/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -0,0 +1,49 @@
+---
+title: 'API Match Multiple Received SKUs retornando "Invalid sellerId"'
+id: 60aL2Chds0Jo3m6XMkxmnG
+status: PUBLISHED
+createdAt: 2023-10-17T16:26:27.980Z
+updatedAt: 2023-10-17T16:26:40.592Z
+publishedAt: 2023-10-17T16:26:40.592Z
+firstPublishedAt: 2023-10-17T16:26:28.466Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: api-match-multiple-received-skus-retornando-invalid-sellerid
+locale: pt
+kiStatus: Fixed
+internalReference: 506660
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A API Match Multiple Received SKUs (doc: https://developers.vtex.com/vtex-rest-api/reference/match-received-skus#matchmultiple) está retornando a mensagem de erro "Invalid sellerId" para qualquer tentativa de aprovação de novos produtos, mesmo que o vendedor esteja corretamente ativo no marketplace.
+
+## Simulação
+
+
+1. Copie o curl da documentação anterior;
+2. Cole-o em sua ferramenta de API (postman, insomnia...);
+3. Substitua os valores do objeto pelos dados do sku que você está tentando aprovar;
+4. Verifique se o sellerId está ativo e é válido no gerenciamento de vendedores do marketplace;
+5. A resposta da API não deve ser:
+
+    "errorResponse": {"Code": 33, "Message": "Invalid sellerId" }
+
+
+## Workaround
+
+
+A API Match Received SKUs individually está funcionando corretamente e pode substituir a API anterior para aprovar novos produtos um a um.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md b/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md
new file mode 100644
index 000000000..b9ced1744
--- /dev/null
+++ b/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md
@@ -0,0 +1,46 @@
+---
+title: 'Conversor que converte Altura, Largura, Peso e Comprimento para 0,1'
+id: j3rz875eWVHFMLYxcYsDL
+status: PUBLISHED
+createdAt: 2023-08-23T13:38:55.976Z
+updatedAt: 2023-08-23T20:01:37.842Z
+publishedAt: 2023-08-23T20:01:37.842Z
+firstPublishedAt: 2023-08-23T13:38:58.327Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: conversor-que-converte-altura-largura-peso-e-comprimento-para-01
+locale: pt
+kiStatus: Fixed
+internalReference: 886168
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o Matcher processa os skus no módulo de sugestões do marketplace, as informações de Altura, Largura, Peso e Comprimento estão sendo definidas como 0,1 em vez de respeitar os valores enviados pelo vendedor.
+
+## Simulação
+
+
+
+1. O vendedor envia o sku para o marketplace com Altura, Largura, Peso e Comprimento com valores normais;
+2. O sku chega ao marketplace e é processado pelo matcher;
+3. Verifique na API a seguir se o objeto Matcher tem os campos Height (Altura), Width (Largura), Weight (Peso) e Length (Comprimento) definidos como 0,1
+https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#get-/suggestions/-sellerId-/-sellerSkuId-
+ ![](https://vtexhelp.zendesk.com/attachments/token/vCdMBFKEJ0243C9Ew7PPFDgp3/?name=image.png
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md b/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
new file mode 100644
index 000000000..16192e360
--- /dev/null
+++ b/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
@@ -0,0 +1,46 @@
+---
+title: 'O Matcher não funciona como esperado quando o nome do Produto/SKU contém caracteres especiais'
+id: 1kRjFExdSRMAJMgFgC7Bbj
+status: PUBLISHED
+createdAt: 2023-10-19T15:37:17.652Z
+updatedAt: 2023-10-19T15:37:18.601Z
+publishedAt: 2023-10-19T15:37:18.601Z
+firstPublishedAt: 2023-10-19T15:37:18.601Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: o-matcher-nao-funciona-como-esperado-quando-o-nome-do-produtosku-contem-caracteres-especiais
+locale: pt
+kiStatus: Fixed
+internalReference: 736164
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao integrar produtos que têm caracteres especiais no nome, como `. - + # /` , o Matcher dá uma pontuação de 50% e faz com que os produtos fiquem em Pending. Com isso, os produtos dependem de aprovação manual ou via API.
+
+
+## Simulação
+
+
+
+1. Por meio de um vendedor VTEX, envie uma SKU que contenha caracteres especiais no nome
+2. Na página SKU Received (SKU Recebida), veja que a SKU em questão terá uma pontuação de 50%, na guia Pending (Pendente)
+
+
+
+## Workaround
+
+
+Para resolver o cenário, é indicado que o vendedor altere o nome do SKU/produto, removendo os caracteres especiais. Se isso não for possível, o marketplace pode usar a API https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/api.vtex.com/-accountName-/suggestions/matches/action/-actionName- para fazer a correspondência entre os produtos
+
+
+
+
+
diff --git a/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md b/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md
new file mode 100644
index 000000000..2e81d0eac
--- /dev/null
+++ b/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md
@@ -0,0 +1,47 @@
+---
+title: 'O Max Shipping Discount não está atualizando as priceTags'
+id: uA0KFnyIOHq3ikcaZmYGr
+status: PUBLISHED
+createdAt: 2023-09-20T17:54:59.620Z
+updatedAt: 2023-10-02T18:20:48.375Z
+publishedAt: 2023-10-02T18:20:48.375Z
+firstPublishedAt: 2023-09-20T17:55:00.609Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: o-max-shipping-discount-nao-esta-atualizando-as-pricetags
+locale: pt
+kiStatus: Backlog
+internalReference: 904190
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+##
+O desconto máximo de frete não retorna nas etiquetas de preço, quando o vendedor tenta calcular o imposto, o chk não tem o valor para considerar e considera o desconto no valor final do imposto.
+
+
+## Simulação
+
+
+Crie um desconto máximo de frete e um imposto
+simule um carrinho com ambos, você verá que a etiqueta de preço não é preenchida.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
new file mode 100644
index 000000000..6a632dfbc
--- /dev/null
+++ b/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -0,0 +1,66 @@
+---
+title: '"número máximo de itens qualificados para cada carrinho" + more for less aplica desconto incorreto ao usar o mesmo item.'
+id: gWIMhi9RCv9BE1RvV6GiM
+status: PUBLISHED
+createdAt: 2024-07-30T17:14:36.972Z
+updatedAt: 2024-07-30T17:14:37.931Z
+publishedAt: 2024-07-30T17:14:37.931Z
+firstPublishedAt: 2024-07-30T17:14:37.931Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: numero-maximo-de-itens-qualificados-para-cada-carrinho-more-for-less-aplica-desconto-incorreto-ao-usar-o-mesmo-item
+locale: pt
+kiStatus: Backlog
+internalReference: 1073080
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar um desconto do tipo "mais por menos" junto com outra promoção que usa o "máximo de itens por carrinho" para o mesmo item, ambos se acumulando, um desconto incorreto é concedido, excedendo a configuração inicialmente configurada.
+
+Isso ocorre devido à forma como o checkout divide os itens.
+
+Por exemplo, digamos que você tenha uma promoção mais por menos (A) configurada para dar um "desconto de 100% para 1 item de cada 8 inseridos no carrinho".
+
+Além disso, você tem outra promoção (B) que, para essa mesma SKU, dá um desconto de 50%, limitado a um máximo de 2 itens.
+
+**O que é esperado**:
+
+Se 80 itens forem inseridos no checkout, um total de 11 itens deverá ser oferecido gratuitamente.  10 provenientes de (A), 1 proveniente de (B).
+
+**O que realmente acontece**:
+
+Os itens são divididos em 3 quantidades diferentes no checkout
+
+(1) aqueles que receberam apenas o desconto (A)
+(2) aqueles que receberam apenas o desconto (B)
+(3) os que receberam ambos os descontos (AB)
+
+No entanto, a linha (2), que deveria ter apenas 2 itens com 50% de desconto, na verdade replica o desconto de 100% da linha (1), essencialmente dando 2 itens extras de desconto, em um total de 13 itens, em vez de 11.
+
+
+
+## Simulação
+
+
+Crie um cenário de promoção conforme descrito acima ou semelhante a ele, usando o "número máximo de itens qualificados para cada carrinho" e uma promoção "mais por menos", ambos definidos para acumular.
+
+É importante observar que esse problema só ocorre quando **todas as promoções são configuradas para o mesmo SKU**
+
+## Workaround
+
+
+n/a (evite usar essas duas configurações específicas juntas ao operar com descontos para a mesma SKU).
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md b/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
new file mode 100644
index 000000000..60651d693
--- /dev/null
+++ b/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
@@ -0,0 +1,43 @@
+---
+title: 'A configuração da quantidade máxima do mesmo item no carrinho não pode ser alterada pelas contas de franquia'
+id: 5NqcSpcmPXEJE4KIkp6eZE
+status: PUBLISHED
+createdAt: 2022-05-12T14:52:33.074Z
+updatedAt: 2023-10-18T14:34:56.570Z
+publishedAt: 2023-10-18T14:34:56.570Z
+firstPublishedAt: 2022-05-12T14:52:33.334Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-configuracao-da-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-pelas-contas-de-franquia
+locale: pt
+kiStatus: Backlog
+internalReference: 325273
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A configuração da quantidade máxima do mesmo item no carrinho não pode ser alterada por contas de franquia (vendedor whitelabel), pois ocorre em uma tela de catálogo herdada (/admin/Site/ConfigForm.aspx) - módulo que é removido das contas de franquia, pois elas herdam os produtos da conta principal.
+
+## Simulação
+
+
+
+- Entre em um ambiente de conta de franquia ou de vendedor whitelabel
+- Acesse a tela "CMS > Configurações > guia Geral" no administrador ou vá diretamente para a página /admin/Site/ConfigForm.aspx
+- Observe que não é possível acessar o conteúdo dessa áre
+
+## Workaround
+
+
+Solicite a configuração via ticket para a VTEX.
+
+
+
+
diff --git a/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
new file mode 100644
index 000000000..7d579c917
--- /dev/null
+++ b/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -0,0 +1,42 @@
+---
+title: 'O MDv2 retorna o erro "504 Gateway Timeout" quando tentamos atualizar um documento passando um símbolo ou caractere especial.'
+id: 6GP5QBWyIAir2oKe08giT2
+status: PUBLISHED
+createdAt: 2023-08-09T13:04:34.819Z
+updatedAt: 2023-08-09T13:04:35.446Z
+publishedAt: 2023-08-09T13:04:35.446Z
+firstPublishedAt: 2023-08-09T13:04:35.446Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: o-mdv2-retorna-o-erro-504-gateway-timeout-quando-tentamos-atualizar-um-documento-passando-um-simbolo-ou-caractere-especial
+locale: pt
+kiStatus: Backlog
+internalReference: 852966
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O comportamento da API ao tentar atualizar um documento que contém um símbolo em um campo do tipo string, como `"name": "Product1 14€"`, retornará o erro 504 Gateway timeout e não atualizará o documento.
+
+## Simulação
+
+
+
+1. Faça uma solicitação PUT para atualizar um documento por meio da API e, no corpo, inclua o caractere especial em um campo do tipo string.
+
+    { "name": "Product1 14€", ...}
+
+2.  Observe a resposta da API e verifique se ela retorna o erro 504 Gateway timeout
+
+## Workaround
+
+
+Exclua o caractere especial e digite o nome do símbolo. Por exemplo: "`14 euros`"
+
diff --git a/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md b/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
new file mode 100644
index 000000000..e79526125
--- /dev/null
+++ b/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
@@ -0,0 +1,50 @@
+---
+title: '[MELI] O atributo está sendo enviado para o MELI sem ser mapeado pelo vendedor'
+id: CILYWlvEAlXkcvEYuZ99m
+status: PUBLISHED
+createdAt: 2023-10-30T10:09:31.578Z
+updatedAt: 2023-11-30T11:05:05.907Z
+publishedAt: 2023-11-30T11:05:05.907Z
+firstPublishedAt: 2023-10-30T10:09:32.150Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: meli-o-atributo-esta-sendo-enviado-para-o-meli-sem-ser-mapeado-pelo-vendedor
+locale: pt
+kiStatus: Fixed
+internalReference: 791380
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema que ainda precisa de mais investigação e detalhes, mas há algumas categorias mapeadas dentro do recurso Mapper e alguns atributos que não foram mapeados, mas estão sendo enviados para o MELI.
+
+Isso fará com que algumas SKUs sejam exportadas e outras não, pois a primeira SKU inclui um atributo indesejado e a segunda SKU não será exportada, pois o MELI tem regras que exigem que todas as variações dentro do mesmo produto tenham as mesmas combinações de atributos.
+
+## Simulação
+
+
+
+Dentro do menu do produto bridge, você verá um erro para alguns SKUs, conforme mostrado abaixo:
+**Variações com diferentes combinações de atributos não são permitidas.**
+
+Isso se deve ao fato de a primeira SKU ter sido exportada com um atributo indesejado, e o restante das SKUs não está sendo enviado para esse atributo.
+
+
+
+## Workaround
+
+
+Existe uma solução alternativa para esse bug? Se sim, descreva-a aqui. Caso contrário, escreva "N/A" ou "Não há nenhuma solução alternativa disponível". Não remova esta seção se não houver solução alternativa, por favor.
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md b/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
index 77a01ac06..ac0a8ed94 100644
--- a/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
+++ b/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
@@ -3,8 +3,8 @@ title: '[Atributos da integração Negro_#000000 com um comportamento não esper
 id: 1GPrObE1SQPP4ScyNHyjDt
 status: PUBLISHED
 createdAt: 2022-09-19T14:04:56.594Z
-updatedAt: 2022-11-25T21:55:27.032Z
-publishedAt: 2022-11-25T21:55:27.032Z
+updatedAt: 2024-02-16T20:28:12.568Z
+publishedAt: 2024-02-16T20:28:12.568Z
 firstPublishedAt: 2022-09-19T14:04:57.386Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: atributos-da-integracao-negro000000-com-um-comportamento-nao-esperado
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 660703
 ---
 
diff --git a/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md b/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md
index d094525d5..7e22b20d3 100644
--- a/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md
+++ b/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md
@@ -3,8 +3,8 @@ title: 'Mensagens automáticas do MELI Mercado Livre - Mensagens'
 id: 6WZy5RNesYJtJOaBAFnbkW
 status: PUBLISHED
 createdAt: 2023-05-04T11:22:21.762Z
-updatedAt: 2023-05-08T18:33:14.421Z
-publishedAt: 2023-05-08T18:33:14.421Z
+updatedAt: 2024-01-30T10:48:09.504Z
+publishedAt: 2024-01-30T10:48:09.504Z
 firstPublishedAt: 2023-05-04T11:22:22.366Z
 contentType: knownIssue
 productTeam: Connections
@@ -24,13 +24,13 @@ internalReference: 615164
 
 
 
-Atualmente, nosso aplicativo MELI para enviar mensagens automáticas ao MELI está tendo alguns problemas com o modo de logística ME2.
+Atualmente, nosso aplicativo MELI para enviar mensagens automáticas ao MELI está tendo alguns problemas ao usar as mensagens modelo.
 
 ## Simulação
 
 
 
-As mensagens automáticas no administrador da VTEX para o modo de logística ME2 não serão enviadas ao vendedor.
+As mensagens automáticas no administrador da VTEX às vezes não estão sendo enviadas para o MELI.
 
 
 
diff --git a/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md b/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md
new file mode 100644
index 000000000..7ccb328a7
--- /dev/null
+++ b/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md
@@ -0,0 +1,43 @@
+---
+title: 'O menu MELI Bridge Orders não exibe as informações de ID do pedido'
+id: ZBc9ny043rVpYFqkZIQ1K
+status: PUBLISHED
+createdAt: 2023-08-16T10:46:52.015Z
+updatedAt: 2023-10-05T18:51:13.700Z
+publishedAt: 2023-10-05T18:51:13.700Z
+firstPublishedAt: 2023-08-16T10:46:53.089Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: o-menu-meli-bridge-orders-nao-exibe-as-informacoes-de-id-do-pedido
+locale: pt
+kiStatus: Fixed
+internalReference: 881733
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema que afeta apenas a visibilidade de alguns pedidos MELI. O que acontece é que estamos registrando o ShipmentID no menu de ponte de pedidos, mas algumas mensagens de erro não têm o OrderID, e isso é necessário em alguns casos, pois o OrderID é a informação que os vendedores têm no Portal MELI.
+
+## Simulação
+
+
+
+Dentro do menu de pedidos em ponte, algumas mensagens de erro não estão registrando o orderID, o que dá a impressão de que alguns pedidos não estão na biblioteca VTEX, mas os vendedores podem encontrar os pedidos pesquisando pelo shipmentID
+
+## Workaround
+
+
+Pesquise o shipmentID em vez do orderID
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md b/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
new file mode 100644
index 000000000..13426ce82
--- /dev/null
+++ b/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
@@ -0,0 +1,45 @@
+---
+title: 'Os ADs do MELI Buybox não estão sendo pausados quando o AD do marketplace é pausado'
+id: 5OFALDi7lY93D7KkZ4scvg
+status: PUBLISHED
+createdAt: 2023-09-29T19:12:14.424Z
+updatedAt: 2023-10-09T20:52:25.672Z
+publishedAt: 2023-10-09T20:52:25.672Z
+firstPublishedAt: 2023-09-29T19:12:15.051Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: os-ads-do-meli-buybox-nao-estao-sendo-pausados-quando-o-ad-do-marketplace-e-pausado
+locale: pt
+kiStatus: Fixed
+internalReference: 910371
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema com o fluxo MELI do Buybox, que é quando se remove a SKU do SC, por exemplo, o AD do marketplace está sendo pausado no MELi, mas o AD do Buybox permanece ativo.
+
+## Simulação
+
+
+
+Quando o AD do marketplace é pausado no MELI, pelo motivo de ser removido do VTEX SC, por exemplo, o AD do Buybox também precisaria ser pausado.
+
+
+
+## Workaround
+
+
+Existe uma solução alternativa para esse erro? Se sim, descreva-a aqui. Caso contrário, escreva "N/A" ou "Não há nenhuma solução alternativa disponível". Não remova esta seção se não houver solução alternativa, por favor.
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md b/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md
index 589b904bc..60bfbd2e1 100644
--- a/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md
+++ b/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md
@@ -1,18 +1,18 @@
 ---
-title: 'Erro da MELI ao enviar o rastreamento do pedido'
+title: 'Erro MELI ao enviar o rastreamento do pedido'
 id: 4wdzb5xjelAkFnbuRCFXAt
 status: PUBLISHED
 createdAt: 2023-03-06T10:06:58.255Z
-updatedAt: 2023-03-06T10:06:59.162Z
-publishedAt: 2023-03-06T10:06:59.162Z
+updatedAt: 2023-10-20T17:28:38.314Z
+publishedAt: 2023-10-20T17:28:38.314Z
 firstPublishedAt: 2023-03-06T10:06:59.162Z
 contentType: knownIssue
 productTeam: Connections
 author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
-slug: erro-da-meli-ao-enviar-o-rastreamento-do-pedido
+slug: erro-meli-ao-enviar-o-rastreamento-do-pedido
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 764885
 ---
 
@@ -24,30 +24,24 @@ internalReference: 764885
 
 
 
-Estamos atualmente registrando uma mensagem de erro dentro do menu Brige - Tracking, este erro está sendo devolvido pela MELI quando enviamos o fluxo de rastreamento para eles.
+No momento, estamos registrando uma mensagem de erro dentro do menu Brige - Tracking, esse erro está sendo retornado pelo MELI quando enviamos o fluxo de rastreamento para ele.
 
-Importante notar que isto não está impactando o fluxo, pois o rastreamento está funcionando corretamente, mas a questão é que estamos criando o log como uma mensagem de erro quando, em vez disso, ele deve ser bem sucedido.(devido ao que a MELI retorna)
-
-
-##
+É importante observar que isso não está afetando o fluxo, pois o rastreamento está funcionando corretamente, mas o problema é que estamos criando o registro como uma mensagem de erro quando deveria ser de sucesso (devido ao que o MELI retorna).
 
 ## Simulação
 
 
 
-Inside Bridge - Menu de rastreamento será mostrada uma mensagem de erro como abaixo.
-
-"Mensagem de erro não mapeada pela integração". Entre em contato com a VTEX informando o ocorrido para que o mapeamento seja realizado.
-Mensagem de erro Mercado Livre:".
-
+Dentro do menu Bridge - Tracking (Ponte - Rastreamento), uma mensagem de erro como a mostrada abaixo será exibida.
 
-##
+"Mensagem de erro não mapeada pela integração. Entre em contato com a VTEX informando o ocorrido para que o mapeamento seja realizado.
+Mensagem de erro Mercado Livre:
 
 ## Workaround
 
 
 
-Nenhuma ação é necessária, importante notar que embora a mensagem de erro seja exibida, isto não está impactando o fluxo de rastreamento, o XML está sendo enviado à MELI e o status do pedido está sendo atualizado.
+Nenhuma ação é necessária, é importante observar que, embora a mensagem de erro seja exibida, isso não está afetando o fluxo de rastreamento, o XML está sendo enviado para o MELI e o status do pedido está sendo atualizado.
 
 
 
diff --git a/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md b/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md
new file mode 100644
index 000000000..6bbce0a1b
--- /dev/null
+++ b/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md
@@ -0,0 +1,42 @@
+---
+title: 'Cotação de frete MELI para múltiplos officialStoreIDs'
+id: 4KdPYtRbDdsBrn2k0dz7oc
+status: PUBLISHED
+createdAt: 2024-02-07T11:19:11.169Z
+updatedAt: 2024-06-19T11:43:56.663Z
+publishedAt: 2024-06-19T11:43:56.663Z
+firstPublishedAt: 2024-02-07T11:19:12.139Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: cotacao-de-frete-meli-para-multiplos-officialstoreids
+locale: pt
+kiStatus: Fixed
+internalReference: 978358
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, temos um problema com a integração do MELI em relação à API de cotação de frete do MELI, que se aplica apenas a vendedores que usam vários officialStoreIDs no MELI, mas usam apenas uma conta na VTEX usando o mesmo sellerID no MELI
+
+## Simulação
+
+
+
+Se esse cenário for aplicado, a cotação de frete do MELI retornará um erro e o MELI redirecionará o vendedor para a planilha de frete em vez de usar a API de frete.
+
+## Workaround
+
+
+manter a planilha de frete atualizada para evitar inconsistências entre a VTEX e o MELI
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md b/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md
new file mode 100644
index 000000000..bcc1c2acb
--- /dev/null
+++ b/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md
@@ -0,0 +1,43 @@
+---
+title: 'Pedidos MELI FULL não criam fatura na VTEX'
+id: 6SNkDcqCWeDDPm01RrM0FQ
+status: PUBLISHED
+createdAt: 2024-02-05T11:14:30.020Z
+updatedAt: 2024-02-05T11:14:31.187Z
+publishedAt: 2024-02-05T11:14:31.187Z
+firstPublishedAt: 2024-02-05T11:14:31.187Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: pedidos-meli-full-nao-criam-fatura-na-vtex
+locale: pt
+kiStatus: Backlog
+internalReference: 976614
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente temos um problema com os pedidos MELI FULL, se o pedido apresentar algum erro durante a criação na VTEX, como erro de SLA, falta de estoque, etc., o processo de criação da fatura na VTEX não é executado. Basicamente, o XML dentro da embeddedInvocie do OMS não está sendo criado nesses casos.
+
+## Simulação
+
+
+
+Se a ordem apresentar algum erro durante sua criação, o XML não será colocado dentro do VTEX OMS
+
+## Workaround
+
+
+Para evitar esse erro, as ordens não devem ser armazenadas no VTEX Bridge, para isso, sempre configure os SLAs necessários para evitar esse erro
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md b/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md
new file mode 100644
index 000000000..3db72388f
--- /dev/null
+++ b/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md
@@ -0,0 +1,44 @@
+---
+title: 'Valor incorreto da MELI quando o cliente tem cupom na MELI'
+id: 3PvNKqG2BMZDBLLVuriIHy
+status: PUBLISHED
+createdAt: 2024-01-22T11:58:00.747Z
+updatedAt: 2024-01-22T11:58:01.431Z
+publishedAt: 2024-01-22T11:58:01.431Z
+firstPublishedAt: 2024-01-22T11:58:01.431Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: valor-incorreto-da-meli-quando-o-cliente-tem-cupom-na-meli
+locale: pt
+kiStatus: Backlog
+internalReference: 969297
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, o cliente usou um cupom no MELI, há uma variedade de tipos de cupom no MELI. E alguns deles não estão incluídos nos cálculos do VTEX OMS.
+
+## Simulação
+
+
+
+Na VTEX OMS, o valor da ordem pode ser diferente do que a MELI vendeu ao cliente, devido a alguns tipos de cupons que não estão sendo considerados durante a criação da ordem na VTEX
+
+## Workaround
+
+
+
+Para pedidos ME1, se o vendedor precisa ter o valor correto do pedido, a fim de enviar o valor da fatura para MELI, ele pode usar o campo no VTEX OMS chamado "total_paid_amount", este campo está atualmente considerando todos os valores de cupom.
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
new file mode 100644
index 000000000..790c53692
--- /dev/null
+++ b/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -0,0 +1,51 @@
+---
+title: 'A integração do MELI está recebendo erros do MELI "429 solicitações demais"'
+id: 1e4g9nzZFyanywmLbSHq4D
+status: PUBLISHED
+createdAt: 2023-08-03T10:47:41.602Z
+updatedAt: 2023-08-14T14:08:12.646Z
+publishedAt: 2023-08-14T14:08:12.646Z
+firstPublishedAt: 2023-08-03T10:47:43.214Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: a-integracao-do-meli-esta-recebendo-erros-do-meli-429-solicitacoes-demais
+locale: pt
+kiStatus: Fixed
+internalReference: 873998
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema com algumas contas no MELI que estão recebendo um erro ao tentar atualizar produtos, estoque ou preço no MELI.
+
+Isso não está afetando todas as contas e nem todos os SKUs, mas apenas parte deles, e isso é causado devido ao envio de mais solicitações do que o MELI está atualmente preparado para receber.
+
+## Simulação
+
+
+
+Dentro do menu de integração estoque/preço/produto, algumas contas podem apresentar um erro:
+
+**Sorry, we couldn't process this request. Aguarde alguns minutos e processe-a novamente**
+
+Estamos trabalhando em como lidar melhor com as solicitações para evitar receber esse erro do MELI.
+
+
+
+## Workaround
+
+
+A única solução alternativa disponível no momento é reprocessar a solicitação diretamente no menu bridge.
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md b/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
new file mode 100644
index 000000000..3fe9da47d
--- /dev/null
+++ b/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
@@ -0,0 +1,36 @@
+---
+title: 'Tipos de listagem de integração MELI para Peru, Venezuela, Equador e Uruguai'
+id: 77DQc7iQ4KgiWZGRAGdTgT
+status: PUBLISHED
+createdAt: 2023-10-25T11:48:14.580Z
+updatedAt: 2023-10-25T11:48:15.479Z
+publishedAt: 2023-10-25T11:48:15.479Z
+firstPublishedAt: 2023-10-25T11:48:15.479Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: tipos-de-listagem-de-integracao-meli-para-peru-venezuela-equador-e-uruguai
+locale: pt
+kiStatus: Backlog
+internalReference: 925139
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, nosso aplicativo MELI não está enviando o tipo de listagem correto para os países **Peru, Venezuela, Equador e Uruguai**
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
index 6f44d7223..10026ea05 100644
--- a/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -3,8 +3,8 @@ title: 'Códigos postais de integração MELI "11111" Meli - Lima/Perú'
 id: 7ICcek0NOUczgtA65CaZk5
 status: PUBLISHED
 createdAt: 2023-05-16T17:50:38.417Z
-updatedAt: 2023-05-16T17:50:39.140Z
-publishedAt: 2023-05-16T17:50:39.140Z
+updatedAt: 2023-08-16T12:43:27.706Z
+publishedAt: 2023-08-16T12:43:27.706Z
 firstPublishedAt: 2023-05-16T17:50:39.140Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: codigos-postais-de-integracao-meli-11111-meli-limaperu
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 826566
 ---
 
diff --git a/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md b/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md
new file mode 100644
index 000000000..28085f562
--- /dev/null
+++ b/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md
@@ -0,0 +1,42 @@
+---
+title: 'O MELI Mapper envia incorretamente a especificação do produto como variação'
+id: 6b49pUUxL3B3RtUWofLjL8
+status: PUBLISHED
+createdAt: 2023-06-27T11:20:49.475Z
+updatedAt: 2023-06-27T11:20:50.484Z
+publishedAt: 2023-06-27T11:20:50.484Z
+firstPublishedAt: 2023-06-27T11:20:50.484Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: o-meli-mapper-envia-incorretamente-a-especificacao-do-produto-como-variacao
+locale: pt
+kiStatus: Backlog
+internalReference: 851021
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema no recurso MELI Mapper, no qual decidimos enviar um SKU como variação com base nos atributos de categoria do MELI, e não com base no que o vendedor mapeou no VTEX, o que significa que uma especificação de produto mapeada no VTEX pode ser enviada como variação para o MELI.
+
+## Simulação
+
+
+
+Dentro do recurso de mapeamento, sempre que o vendedor mapear um atributo que aceita variação no MELI, ele será enviado como variação, mesmo que o vendedor tenha mapeado dentro da especificação do produto
+
+## Workaround
+
+
+n/a
+
+
+
+
diff --git a/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md b/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
new file mode 100644
index 000000000..dd4c3fe5c
--- /dev/null
+++ b/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
@@ -0,0 +1,44 @@
+---
+title: 'Os pedidos MELI não estão sendo cancelados no VTEX OMS para o cenário de contas múltiplas'
+id: 4u9ue93sHNWcfVm3sRL2qx
+status: PUBLISHED
+createdAt: 2024-02-06T11:04:52.918Z
+updatedAt: 2024-02-06T11:04:54.082Z
+publishedAt: 2024-02-06T11:04:54.082Z
+firstPublishedAt: 2024-02-06T11:04:54.082Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: os-pedidos-meli-nao-estao-sendo-cancelados-no-vtex-oms-para-o-cenario-de-contas-multiplas
+locale: pt
+kiStatus: Backlog
+internalReference: 977453
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, nossa integração MELI tem um problema relacionado ao processo de cancelamento de ordens. Quando o MELI cancela uma ordem e o vendedor tem mais de 4 contas na VTEX, há uma chance de não tentar cancelar a ordem na quinta conta
+
+## Simulação
+
+
+
+Se o cancelamento da ordem não puder ser concluído, o vendedor poderá ver a ordem não cancelada na VTEX, mas cancelada na MELI; nesse caso, um cancelamento manual é necessário diretamente no OMS.
+Isso só é aplicado para casos em que o vendedor tem mais de 4 contas na VTEX, usando o mesmo MELI UserID
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md b/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md
new file mode 100644
index 000000000..285f74ac4
--- /dev/null
+++ b/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md
@@ -0,0 +1,48 @@
+---
+title: 'A tabela de tamanhos MELI não está funcionando para tamanhos com letras'
+id: 7vAViV3MmC7zOSTF0cFTYy
+status: PUBLISHED
+createdAt: 2023-07-24T12:04:19.589Z
+updatedAt: 2023-09-12T15:04:46.716Z
+publishedAt: 2023-09-12T15:04:46.716Z
+firstPublishedAt: 2023-07-24T12:04:20.171Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: a-tabela-de-tamanhos-meli-nao-esta-funcionando-para-tamanhos-com-letras
+locale: pt
+kiStatus: Fixed
+internalReference: 867262
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, nosso recurso MELI Size Chart não está funcionando para tamanhos com letras, por exemplo:
+
+Tamanho = "P", "M", "G".
+
+## Simulação
+
+
+
+Dentro da tela do mapeador, podemos ver o recurso de tabela de tamanhos disponível para a integração do MELI. Portanto, se os vendedores mapearem um tamanho com seus valores como letras, ele não funcionará e uma mensagem de erro será exibida no produto da ponte, como abaixo:
+
+"O valor do atributo SIZE é inválido: P. Este valor deve ser igual ao da tabela de medidas.
+
+## Workaround
+
+
+
+Os tamanhos estão funcionando atualmente com números, portanto, os vendedores podem usar os números em vez de letras.
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md b/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md
new file mode 100644
index 000000000..d2dc67130
--- /dev/null
+++ b/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md
@@ -0,0 +1,43 @@
+---
+title: 'Atributo de problema do MELI SizeChart não é válido'
+id: 3t6zqW9aE6pvW9b3Zvj0MB
+status: PUBLISHED
+createdAt: 2024-03-08T13:59:23.756Z
+updatedAt: 2024-03-11T20:00:06.480Z
+publishedAt: 2024-03-11T20:00:06.480Z
+firstPublishedAt: 2024-03-08T13:59:24.514Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: atributo-de-problema-do-meli-sizechart-nao-e-valido
+locale: pt
+kiStatus: Fixed
+internalReference: 996639
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+O Mercado Livre incluiu recentemente novos atributos obrigatórios no recurso de integração de gráficos de tamanho, portanto, agora devemos corrigir nossa integração com esses novos atributos para que os vendedores possam exportar corretamente os gráficos de tamanho para o MELI.
+
+## Simulação
+
+
+
+Ao carregar o gráfico de tamanho na UI, você pode ver um erro "Attribute XXX is not valid" (O atributo XXX não é válido), isso pode estar relacionado a este err
+
+## Workaround
+
+
+n/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/meli-update-stockprice-issue.md b/docs/known-issues/pt/meli-update-stockprice-issue.md
new file mode 100644
index 000000000..e1e520bb6
--- /dev/null
+++ b/docs/known-issues/pt/meli-update-stockprice-issue.md
@@ -0,0 +1,43 @@
+---
+title: 'Atualização do MELI Problema de estoque/preço'
+id: 7LQ81vG5nsbBn4Wj7Z9VJe
+status: PUBLISHED
+createdAt: 2023-12-12T10:22:28.961Z
+updatedAt: 2024-01-10T17:51:59.853Z
+publishedAt: 2024-01-10T17:51:59.853Z
+firstPublishedAt: 2023-12-12T10:22:29.656Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: atualizacao-do-meli-problema-de-estoquepreco
+locale: pt
+kiStatus: Fixed
+internalReference: 939329
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um cenário muito específico que afeta alguns casos de SKUs que não conseguem atualizar o estoque no MELI.
+
+## Simulação
+
+
+
+O que acontece é que, em alguns casos, o campo seller_custom_field, que deveria ser preenchido com o SKU da VTEX, está realmente em branco e, portanto, a integração não consegue atualizar o estoque do MELI nesses casos
+
+## Workaround
+
+
+Preencha a planilha de migração com esses casos e envie para a equipe de produto para definir nosso SKU dentro do campo seller_custom_field.
+
+
+
+
+
diff --git a/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md b/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
new file mode 100644
index 000000000..9210f3453
--- /dev/null
+++ b/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
@@ -0,0 +1,56 @@
+---
+title: '[Mercado Livre] AD BuyBox não atualiza o shipping_mode para ME2'
+id: 5XmZsbZz1171a04dWPs2MY
+status: PUBLISHED
+createdAt: 2024-06-03T11:38:34.337Z
+updatedAt: 2024-06-03T11:38:35.242Z
+publishedAt: 2024-06-03T11:38:35.242Z
+firstPublishedAt: 2024-06-03T11:38:35.242Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-ad-buybox-nao-atualiza-o-shippingmode-para-me2
+locale: pt
+kiStatus: Backlog
+internalReference: 1042779
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+AD BuyBox não atualiza shipping_mode para ME2
+
+## Simulação
+
+
+
+P: Por que o anúncio está em under_review quando tento atualizar o ME2?
+R: Hoje o status desse anúncio no MELI é under_review, isso acontece porque é um anúncio do tipo BuyBox e, nesse caso, não podemos atualizá-lo para ME2 porque o MELI não permite isso e, por esse motivo, quando tentamos atualizar o MELI, ele retorna a seguinte moderação:
+
+
+    Não é possível processar uma solicitação de um anúncio moderado pelo Mercado Livre.<br><br>Resumo da moderação: <br><br>Razão: Cancelamos o anúncio porque você só pode vender este produto com seu anúncio de catálogo. <br>Remédio: Cancelamos o anúncio porque você só pode vender este produto com seu anúncio de catálogo.
+
+
+P: Então, isso acontecerá com todos os anúncios do buybox?
+R: Não, esse cenário só ocorrerá quando o caso for de "Catálogo restrito", em que só pode haver um anúncio BuyBox, não porque é BuyBox, mas porque é esse tipo específico de Restrict.
+
+**SOLUÇÃO**
+Como não temos esse fluxo de atualização ME2 para anúncios buybox, estamos abrindo este KI
+
+
+
+## Workaround
+
+
+Abra um ticket para a equipe de conexões solicitando uma atualização para o ME2, sempre informando o anúncio buybox ex: MLB36470123456
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
new file mode 100644
index 000000000..be52b5826
--- /dev/null
+++ b/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
@@ -0,0 +1,48 @@
+---
+title: '[Mercado Livre] [Bridge] O Bridge não está registrando algumas mensagens de erro'
+id: 3KmdcY6hlLQx5h1FgKHAbS
+status: PUBLISHED
+createdAt: 2024-06-21T12:38:31.025Z
+updatedAt: 2024-06-26T11:07:40.994Z
+publishedAt: 2024-06-26T11:07:40.994Z
+firstPublishedAt: 2024-06-21T12:38:31.845Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-bridge-o-bridge-nao-esta-registrando-algumas-mensagens-de-erro
+locale: pt
+kiStatus: Backlog
+internalReference: 1053742
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Erro no fluxo de atualização: o sku não está sendo registrado na ponte
+
+**Marketplace:** Mercado Livre
+**Causa raiz:** Admin > Bridge > Produto
+
+**Importante:** não acontece com todos os skus;
+
+## Simulação
+
+
+Admin > Marketplace > Produtos > Amazon
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/3MxTLEnmPv9lgG7UE8iUEd1Ft/?name=image.png
+
+## Workaround
+
+
+Em alguns casos, o reprocessamento do sku na ponte resolve o problema.
+
+
+
+
+
diff --git a/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md b/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
new file mode 100644
index 000000000..c9345a5fc
--- /dev/null
+++ b/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
@@ -0,0 +1,45 @@
+---
+title: '[Mercado Livre] Menu Bridge Orders, não mostra as informações de shippingID'
+id: 2fXDbejpPJ04NDfPCCcr0j
+status: PUBLISHED
+createdAt: 2024-03-18T20:56:17.859Z
+updatedAt: 2024-03-18T20:56:18.697Z
+publishedAt: 2024-03-18T20:56:18.697Z
+firstPublishedAt: 2024-03-18T20:56:18.697Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-menu-bridge-orders-nao-mostra-as-informacoes-de-shippingid
+locale: pt
+kiStatus: Backlog
+internalReference: 1001903
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, temos um problema que afeta apenas a visibilidade de alguns pedidos MELI. O que acontece é que estamos registrando o ShipmentID no menu de ponte de pedidos, mas algumas mensagens de erro não têm o OrderID, e isso é necessário em alguns casos, pois o OrderID é a informação que os vendedores têm no Portal MELI.
+
+Mercado Livre > Bridge > OrderId
+
+## Simulação
+
+
+Dentro do menu de pedidos do Bridge, algumas mensagens de erro não estão registrando o orderID, o que dá a impressão de que alguns pedidos não estão no VTEX brige, mas os vendedores podem encontrar os pedidos pesquisando o shipmentID.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/OZk1c79PgvKBKq6wGldvIbHM6/?name=image.png
+
+## Workaround
+
+
+Obtenha o OrderID, obtenha o ShipmentID e procure-o na ponte
+
+
+
+
+
diff --git a/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md b/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md
index 5838b0db5..9eebf740f 100644
--- a/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md
+++ b/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md
@@ -1,18 +1,18 @@
 ---
-title: 'Mercado Book Mapper atributo Tamanho'
+title: 'Tamanho do atributo do Mercado Livre Mapper'
 id: 3dLrm6SVsPB4tU46SC3Xdi
 status: PUBLISHED
 createdAt: 2022-07-26T19:53:34.899Z
-updatedAt: 2022-11-25T21:55:42.119Z
-publishedAt: 2022-11-25T21:55:42.119Z
+updatedAt: 2024-02-16T20:28:24.174Z
+publishedAt: 2024-02-16T20:28:24.174Z
 firstPublishedAt: 2022-07-26T19:53:35.449Z
 contentType: knownIssue
 productTeam: Connections
 author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
-slug: mercado-book-mapper-atributo-tamanho
+slug: tamanho-do-atributo-do-mercado-livre-mapper
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 592577
 ---
 
@@ -24,20 +24,20 @@ internalReference: 592577
 
 
 
-Mesmo mapeando corretamente o atributo "Tamanho" no mapeador, para algumas categorias MELI não está funcionando corretamente.
+Mesmo mapeando corretamente o atributo "Size" no mapeador, para algumas categorias MELI ele não está funcionando corretamente.
 
+## Simulação
 
 
-## Simulação
 
+Dentro do menu de produtos da ponte, você verá um erro sobre o atributo Size no MELI.
 
+## Workaround
 
-Dentro do menu de produtos bridge, você verá um erro sobre o tamanho do atributo em MELI.
 
+Existe uma solução alternativa para esse erro? Se sim, descreva-a aqui. Caso contrário, escreva "N/A" ou "Não há nenhuma solução alternativa disponível". Não remova esta seção se não houver solução alternativa, por favor.
 
 
-## Workaround
 
 
-n/d
 
diff --git a/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md b/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md
new file mode 100644
index 000000000..d2a8c439c
--- /dev/null
+++ b/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md
@@ -0,0 +1,41 @@
+---
+title: '[Mercado Livre] Remover a validação under_review em Atualizar SKU'
+id: 1yeZeigiok3zaltkI7RTMW
+status: PUBLISHED
+createdAt: 2023-08-30T18:15:25.269Z
+updatedAt: 2023-08-30T18:15:25.924Z
+publishedAt: 2023-08-30T18:15:25.924Z
+firstPublishedAt: 2023-08-30T18:15:25.924Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-remover-a-validacao-underreview-em-atualizar-sku
+locale: pt
+kiStatus: Backlog
+internalReference: 890658
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Remover a validação under_review no fluxo Update SKU porque quando o vendedor aplica as ações para corrigir os casos de moderação e estes estão relacionados com o catálogo, não estamos enviando essas alterações para o MELI e, finalmente, os anúncios MELI continuam sendo moderados.
+
+## Simulação
+
+
+O SKU foi moderado por estar na categoria errada, a correção já foi feita e agora ele tem o mapeamento correto no mapepr, mas ainda não está sendo exportado de acordo com a categoria do mapeador
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
new file mode 100644
index 000000000..370f0b6ea
--- /dev/null
+++ b/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
@@ -0,0 +1,44 @@
+---
+title: '[Mercado Livre] [Sku] O Bridge não está registrando algumas mensagens de erro'
+id: 2GcnFE9TKcivoPekYuCNF9
+status: PUBLISHED
+createdAt: 2024-07-23T16:00:26.447Z
+updatedAt: 2024-07-23T16:08:16.661Z
+publishedAt: 2024-07-23T16:08:16.661Z
+firstPublishedAt: 2024-07-23T16:00:27.366Z
+contentType: knownIssue
+productTeam: Connections
+author: 2mXZkbi0oi061KicTExNjo
+tag: Connections
+slug: mercado-livre-sku-o-bridge-nao-esta-registrando-algumas-mensagens-de-erro
+locale: pt
+kiStatus: Backlog
+internalReference: 1069692
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Contexto correto: Em alguns casos, o vendedor não consegue integrar a SKU, pois a mensagem de erro com o motivo pelo qual o item foi moderado não aparece corretamente no Bridge.
+
+
+## Simulação
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/8b6ggO2OjPCsPZlU5NanwK645/?name=image.png)
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
new file mode 100644
index 000000000..8a96a389a
--- /dev/null
+++ b/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -0,0 +1,48 @@
+---
+title: 'As regras de merchandising não estão funcionando para a faceta "productClusterIds"'
+id: 6sLODMgjuoyJD52uc0DBW1
+status: PUBLISHED
+createdAt: 2024-07-09T00:02:40.930Z
+updatedAt: 2024-07-09T00:02:41.798Z
+publishedAt: 2024-07-09T00:02:41.798Z
+firstPublishedAt: 2024-07-09T00:02:41.798Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: as-regras-de-merchandising-nao-estao-funcionando-para-a-faceta-productclusterids
+locale: pt
+kiStatus: Backlog
+internalReference: 1062457
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As regras de merchandising não são aplicadas à faceta "productClusterIds". Isso acontece porque essa faceta tem o comportamento especial de classificar os produtos pela ordem da coleção, em vez de regras de relevância e de merchandising.
+
+Essa faceta não deve ser considerada válida para uma regra de comercialização.
+
+## Simulação
+
+
+
+- criar uma coleção com alguns produtos em uma ordem específica
+- criar uma regra de comercialização explicitamente filtrada por "productClusterIds" ou "productClusterSearchableIds"
+- definir essa regra para classificar os produtos em uma ordem diferente
+- verificar na loja se os produtos manterão a classificação da coleçã
+
+## Workaround
+
+
+A maneira esperada de gerenciar e classificar produtos em uma coleção é fazê-lo diretamente na coleção, adicionando/retirando produtos ou alterando sua posição.
+
+Também é possível aplicar a regra de comercialização à faceta "productClusterNames". Essa faceta segue as regras de relevância em vez da ordem da coleção e funciona com regras de merchandising.
+
+
+
+
diff --git a/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md b/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
new file mode 100644
index 000000000..93debcbdc
--- /dev/null
+++ b/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
@@ -0,0 +1,51 @@
+---
+title: 'O comerciante não consegue abrir uma conta para alguns clientes na API de crédito ao cliente'
+id: 4NGCingtQxzFV1gMbxFzT1
+status: PUBLISHED
+createdAt: 2023-09-25T13:22:58.063Z
+updatedAt: 2023-09-25T13:22:58.651Z
+publishedAt: 2023-09-25T13:22:58.651Z
+firstPublishedAt: 2023-09-25T13:22:58.651Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-comerciante-nao-consegue-abrir-uma-conta-para-alguns-clientes-na-api-de-credito-ao-cliente
+locale: pt
+kiStatus: Backlog
+internalReference: 906509
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Por algum motivo, ao tentar abrir uma nova conta para clientes específicos por meio da API, ele retorna o seguinte erro:
+
+{
+"code": 1099,
+"message": "A conta de crédito já está aberta".
+}
+
+
+Nesse cenário, os dados do cliente (nome, documento etc.) nunca foram usados antes em nenhuma outra conta.
+
+## Simulação
+
+
+Isso ocorre de forma inconsistente, portanto, só ocorrerá a cada duas tentativas.
+
+
+
+## Workaround
+
+
+Crie a conta por meio da interface do usuário do administrador.
+
+
+
+
+
diff --git a/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md b/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md
new file mode 100644
index 000000000..3e0c9c49f
--- /dev/null
+++ b/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md
@@ -0,0 +1,40 @@
+---
+title: 'O aplicativo de mensagens está demorando muito para retornar as informações'
+id: 5GnHyQaPlqCW0KNar1tlMC
+status: PUBLISHED
+createdAt: 2024-01-30T14:16:58.627Z
+updatedAt: 2024-01-30T14:16:59.326Z
+publishedAt: 2024-01-30T14:16:59.326Z
+firstPublishedAt: 2024-01-30T14:16:59.326Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-aplicativo-de-mensagens-esta-demorando-muito-para-retornar-as-informacoes
+locale: pt
+kiStatus: Backlog
+internalReference: 567305
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No processo de indexação, chamamos o aplicativo de mensagens para salvar informações traduzidas sobre os produtos. O principal problema é que as solicitações estão demorando muito para retornar e, com isso, algumas lojas que têm muitos idiomas não indexam totalmente ou têm suas indexações travadas.
+
+## Simulação
+
+
+Verifique qualquer loja que tenha uma grande quantidade de idiomas, mais de 10, e isso começará a tornar a resposta das mensagens mais lenta.
+Isso pode refletir em outros sistemas que dependem das mensagens para traduzir informações.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md b/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
new file mode 100644
index 000000000..c27214bea
--- /dev/null
+++ b/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
@@ -0,0 +1,45 @@
+---
+title: 'O campo "MetaTagDescription" não pode ser excluído por meio do Admin'
+id: 7h0HlpuQnE8nWylgSWJ1lR
+status: PUBLISHED
+createdAt: 2024-02-08T20:21:00.735Z
+updatedAt: 2024-02-08T20:21:01.739Z
+publishedAt: 2024-02-08T20:21:01.739Z
+firstPublishedAt: 2024-02-08T20:21:01.739Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-campo-metatagdescription-nao-pode-ser-excluido-por-meio-do-admin
+locale: pt
+kiStatus: Backlog
+internalReference: 979691
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Há um comportamento inconsistente no campo `MetaTagDescription` no registro do produto, que não pode ser excluído por meio do Admin, mas é possível excluir por meio da API. No Admin, ao clicar em "salvar" com esse campo vazio, o valor do campo `Description` é copiado. Esse cenário não acontece quando se usa a API, o valor é excluído corretamente.
+
+## Simulação
+
+
+
+- Clique no produto a ser editado
+- Exclua o valor do campo `MetaTagDescription`
+- Clique em "salvar" e retorne ao produto
+- Verifique se o valor original não está mais lá, mas o valor da `description` foi duplicad
+
+## Workaround
+
+
+Use a API para excluir o valor indesejado após atualizar o produto no Admin
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/product/-productId-?endpoint=put-/api/catalog/pvt/product/-productId-
+
+
+
+
diff --git a/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md b/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md
new file mode 100644
index 000000000..330ee2e4d
--- /dev/null
+++ b/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md
@@ -0,0 +1,49 @@
+---
+title: 'As mensagens de erro do Minicart Coupon só aparecem após uma segunda tentativa'
+id: 6ZdpXaHJFudXXwUDC00lcr
+status: PUBLISHED
+createdAt: 2023-12-18T16:22:10.537Z
+updatedAt: 2023-12-18T16:22:11.359Z
+publishedAt: 2023-12-18T16:22:11.359Z
+firstPublishedAt: 2023-12-18T16:22:11.359Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: as-mensagens-de-erro-do-minicart-coupon-so-aparecem-apos-uma-segunda-tentativa
+locale: pt
+kiStatus: No Fix
+internalReference: 938379
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As mensagens de erro de cupom no Minicart não aparecerão na primeira vez que você tentar um cupom, mesmo que ele não exista.
+
+## Simulação
+
+
+
+1. Adicione o produto ao carrinho.
+2. Abra o minicarro.
+3. Insira um cupom aleatório dentro do minicarro.
+4. A mensagem de erro não aparecerá.
+5. Insira outro cupom falso.
+6. O erro será exibido.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível. Entretanto, inserir o código a qualquer momento após a primeira tentativa mostrará a mensagem de erro corretamente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md b/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md
index 44751e041..2e1345464 100644
--- a/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md
+++ b/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md
@@ -3,8 +3,8 @@ title: 'O Minicart não mostra as especificações do SKU no cenário B2B'
 id: 4eOpxrLEkyHyobCDuWzsMK
 status: PUBLISHED
 createdAt: 2022-10-27T19:11:58.877Z
-updatedAt: 2022-11-25T22:13:10.845Z
-publishedAt: 2022-11-25T22:13:10.845Z
+updatedAt: 2024-02-16T20:28:02.341Z
+publishedAt: 2024-02-16T20:28:02.341Z
 firstPublishedAt: 2022-10-27T19:11:59.318Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: o-minicart-nao-mostra-as-especificacoes-do-sku-no-cenario-b2b
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 687308
 ---
 
diff --git a/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index 2968a3b03..01e5dd75d 100644
--- a/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -3,8 +3,8 @@ title: 'Comportamentos incorretos para a mutação addToCart a partir do checkou
 id: 1lMWbgmBsOis9gAKcMm8ob
 status: PUBLISHED
 createdAt: 2022-05-03T20:42:18.655Z
-updatedAt: 2022-11-25T22:44:04.555Z
-publishedAt: 2022-11-25T22:44:04.555Z
+updatedAt: 2023-11-16T16:46:29.538Z
+publishedAt: 2023-11-16T16:46:29.538Z
 firstPublishedAt: 2022-05-03T20:42:18.940Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: comportamentos-incorretos-para-a-mutacao-addtocart-a-partir-do-checkout-graphql-enquanto-envia-opcoes-para-itens-ja-adicionados
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 452053
 ---
 
diff --git a/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md b/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
index 94fbd2e1b..1a7e55fa7 100644
--- a/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
+++ b/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
@@ -29,9 +29,9 @@ Principais causas de uma app mal configurada:
 
 No caso de um JSON Schema inexistente, coloque no campo `model` o nome correto do JSON Schema.
 
-Por exemplo: ![Screen Shot 2019-01-03 at 19.31.53](https://images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
+Por exemplo: ![Screen Shot 2019-01-03 at 19.31.53](//images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
 
-Observe como a borda da app fica vermelha e a mensagem de erro no console indica o erro "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](https://images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
+Observe como a borda da app fica vermelha e a mensagem de erro no console indica o erro "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](//images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md b/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
index 3d66221c8..c0a5402f0 100644
--- a/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
+++ b/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
@@ -3,8 +3,8 @@ title: 'O campo minicart.buyer.id ausente faz com que o antifraude cancele trans
 id: 6dvOH9b96qGAHXIzW3wBe1
 status: PUBLISHED
 createdAt: 2023-05-23T17:10:17.329Z
-updatedAt: 2023-05-23T17:10:17.964Z
-publishedAt: 2023-05-23T17:10:17.964Z
+updatedAt: 2024-02-16T20:26:42.045Z
+publishedAt: 2024-02-16T20:26:42.045Z
 firstPublishedAt: 2023-05-23T17:10:17.964Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: o-campo-minicartbuyerid-ausente-faz-com-que-o-antifraude-cancele-transacoes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 514335
 ---
 
diff --git a/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md b/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
new file mode 100644
index 000000000..6d8a102ba
--- /dev/null
+++ b/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
@@ -0,0 +1,44 @@
+---
+title: 'Falta de tradução para a faceta/filtro de preço na Intelligent Search'
+id: 6c6GnC1dKGViJ2h0ZoY5pm
+status: PUBLISHED
+createdAt: 2024-01-31T21:33:04.796Z
+updatedAt: 2024-01-31T21:33:05.556Z
+publishedAt: 2024-01-31T21:33:05.556Z
+firstPublishedAt: 2024-01-31T21:33:05.556Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: falta-de-traducao-para-a-facetafiltro-de-preco-na-intelligent-search
+locale: pt
+kiStatus: Backlog
+internalReference: 974840
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O Intelligent Search não aplica a tradução ao nome do filtro/faceta "price" para idiomas adicionais quando consultado via REST API.
+
+O idioma principal ainda retorna a cadeia de caracteres esperada como sua configuração interna, mas qualquer outro idioma retornará isso com "Price" como um valor fixo.
+
+## Simulação
+
+
+Em uma loja com vários idiomas, defina as traduções para o contexto da Pesquisa inteligente por meio do serviço de mensagens para os idiomas secundários e consulte-o usando a API de facetas. Os valores de "Price" não serão considerados, embora funcionem para qualquer outro rótulo, como as categorias e a marca.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md b/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
index 848538577..9fa308790 100644
--- a/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
+++ b/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
@@ -3,8 +3,8 @@ title: 'Modal como Generic Reason mesmo este tipo de Modal são configurados OK'
 id: 2ftzXjtPZcPypFpsnZMcIK
 status: PUBLISHED
 createdAt: 2022-05-18T18:23:53.248Z
-updatedAt: 2022-11-25T21:59:39.823Z
-publishedAt: 2022-11-25T21:59:39.823Z
+updatedAt: 2024-02-16T20:25:38.358Z
+publishedAt: 2024-02-16T20:25:38.358Z
 firstPublishedAt: 2022-05-18T18:23:53.787Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: modal-como-generic-reason-mesmo-este-tipo-de-modal-sao-configurados-ok
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 488339
 ---
 
diff --git a/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md b/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md
index edada1f4b..fd615baff 100644
--- a/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md
+++ b/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md
@@ -3,8 +3,8 @@ title: 'Modais Configuração de Divergências Deprecated Divergences - Polític
 id: TYWgIv5xOTUBWdC63FbK5
 status: PUBLISHED
 createdAt: 2022-05-18T18:20:55.870Z
-updatedAt: 2022-11-25T21:59:19.021Z
-publishedAt: 2022-11-25T21:59:19.021Z
+updatedAt: 2024-02-16T20:27:05.367Z
+publishedAt: 2024-02-16T20:27:05.367Z
 firstPublishedAt: 2022-05-18T18:20:56.247Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: modais-configuracao-de-divergencias-deprecated-divergences-politica-de-embarque
 locale: pt
-kiStatus: Scheduled
+kiStatus: No Fix
 internalReference: 445866
 ---
 
diff --git a/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md b/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md
index 21a2d31dc..c83d008dd 100644
--- a/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md
+++ b/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md
@@ -3,8 +3,8 @@ title: 'Múltiplos API de promoção Sku não funcionam'
 id: 38CLe2oIWHGNgjL4L0uIxz
 status: PUBLISHED
 createdAt: 2023-01-09T21:18:05.077Z
-updatedAt: 2023-01-09T21:18:05.807Z
-publishedAt: 2023-01-09T21:18:05.807Z
+updatedAt: 2024-02-16T20:23:56.065Z
+publishedAt: 2024-02-16T20:23:56.065Z
 firstPublishedAt: 2023-01-09T21:18:05.807Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: multiplos-api-de-promocao-sku-nao-funcionam
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 729990
 ---
 
diff --git a/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md b/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
new file mode 100644
index 000000000..e52f45963
--- /dev/null
+++ b/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
@@ -0,0 +1,44 @@
+---
+title: 'O rodapé dos meus cartões está tremendo ao tentar adicionar um novo cartão'
+id: 5JRsJqm0PmVkdCh7td3DIr
+status: PUBLISHED
+createdAt: 2024-04-05T16:09:59.991Z
+updatedAt: 2024-04-05T16:11:11.933Z
+publishedAt: 2024-04-05T16:11:11.933Z
+firstPublishedAt: 2024-04-05T16:10:01.510Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-rodape-dos-meus-cartoes-esta-tremendo-ao-tentar-adicionar-um-novo-cartao
+locale: pt
+kiStatus: Backlog
+internalReference: 1012542
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O rodapé em "Meus cartões" treme na tela quando se tenta adicionar um novo cartão.
+
+## Simulação
+
+
+
+1. Acesse uma conta aleatória
+2. Faça login
+3. Acesse My Account > My Cards
+4. Tente salvar um novo cartão falso e, quando o processo falhar, clique para salvar novamente e a tela tremerá até que o processo termin
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md b/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
index c753ce127..2793a31c4 100644
--- a/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
+++ b/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
@@ -3,8 +3,8 @@ title: 'My Cards UI permite aos clientes salvar cartões de crédito sem campo d
 id: 7Ab61xaPRXqxA7VYEnFu8J
 status: PUBLISHED
 createdAt: 2022-02-10T12:34:15.351Z
-updatedAt: 2022-11-25T22:07:26.657Z
-publishedAt: 2022-11-25T22:07:26.657Z
+updatedAt: 2024-02-16T20:26:23.845Z
+publishedAt: 2024-02-16T20:26:23.845Z
 firstPublishedAt: 2022-02-10T12:34:15.869Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: my-cards-ui-permite-aos-clientes-salvar-cartoes-de-credito-sem-campo-de-numero-preenchido-nas-informacoes-de-endereco
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 521542
 ---
 
diff --git a/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md b/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
index 9f6d30a29..94821994b 100644
--- a/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
+++ b/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
@@ -1,16 +1,16 @@
 ---
-title: 'Minha assinatura mostrando mensagem de erro quando a assinatura está associada a um ponto de retirada'
+title: 'Minha assinatura mostra uma mensagem de erro quando a assinatura está associada a um ponto de coleta'
 id: 4p9jzcVzB6E5b6PTm2Ng5E
 status: PUBLISHED
 createdAt: 2022-12-15T19:08:41.210Z
-updatedAt: 2022-12-15T19:08:42.066Z
-publishedAt: 2022-12-15T19:08:42.066Z
+updatedAt: 2024-03-11T19:58:56.132Z
+publishedAt: 2024-03-11T19:58:56.132Z
 firstPublishedAt: 2022-12-15T19:08:42.066Z
 contentType: knownIssue
 productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
-slug: minha-assinatura-mostrando-mensagem-de-erro-quando-a-assinatura-esta-associada-a-um-ponto-de-retirada
+slug: minha-assinatura-mostra-uma-mensagem-de-erro-quando-a-assinatura-esta-associada-a-um-ponto-de-coleta
 locale: pt
 kiStatus: Backlog
 internalReference: 692523
@@ -24,26 +24,20 @@ internalReference: 692523
 
 
 
-Quando um usuário fecha um pedido de assinatura, a área my-subscription exibe o endereço de entrega, mas quando isto é feito com um ponto de retirada, a IU não pode fazer a associação e exibe a seguinte mensagem de erro "Endereço inválido ou inexistente"; Entretanto, o fluxo de assinatura continuará normalmente;
-
-
-##
+Quando um usuário fecha uma solicitação de assinatura, a área my-subscription exibe o endereço de entrega, mas quando isso é feito com um ponto de coleta, a interface do usuário não consegue fazer a associação e exibe a seguinte mensagem de erro: "Endereço inválido ou inexistente"; no entanto, o fluxo de assinatura continuará normalmente;
 
 ## Simulação
 
 
 
 
-- Criar uma assinatura com a opção de retirada em um ponto de retirada;
-- Entrar na área de minhas assinaturas;
-- Nesta área você verá um aviso na UI indicando que há um erro no registro de seu endereço;
-
-
-##
+- Crie uma assinatura com a opção de retirada em um ponto de coleta;
+- Entre na área de minhas assinaturas;
+- Nessa área, você verá um aviso na interface do usuário indicando que há um erro no registro do seu endereço
 
 ## Workaround
 
 
 
-Não há solução para este cenário;
+Não há nenhuma solução alternativa para esse cenário;
 
diff --git a/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md b/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
index a4c3a38b0..0b0b8ffee 100644
--- a/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
+++ b/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
@@ -3,8 +3,8 @@ title: 'Minhas assinaturas Ao entrar na linha de endereço 2 isto aparece como n
 id: 1VbFyW5rQcfUSEJgKphrqb
 status: PUBLISHED
 createdAt: 2022-05-30T13:50:13.717Z
-updatedAt: 2022-11-25T22:02:34.424Z
-publishedAt: 2022-11-25T22:02:34.424Z
+updatedAt: 2024-02-16T20:28:33.052Z
+publishedAt: 2024-02-16T20:28:33.052Z
 firstPublishedAt: 2022-05-30T13:50:14.433Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: minhas-assinaturas-ao-entrar-na-linha-de-endereco-2-isto-aparece-como-nulo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 588046
 ---
 
diff --git a/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md b/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md
index 8bd49aeb0..d91f269a3 100644
--- a/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md
+++ b/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md
@@ -3,8 +3,8 @@ title: 'O botão giratório MyCards não está funcionando corretamente'
 id: 2Y1IHSesmqAKYsep1JzIND
 status: PUBLISHED
 createdAt: 2023-03-29T19:18:47.318Z
-updatedAt: 2023-03-29T19:18:47.732Z
-publishedAt: 2023-03-29T19:18:47.732Z
+updatedAt: 2023-11-06T13:02:14.964Z
+publishedAt: 2023-11-06T13:02:14.964Z
 firstPublishedAt: 2023-03-29T19:18:47.732Z
 contentType: knownIssue
 productTeam: Payments
diff --git a/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md b/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
index 6a9e5fc8f..55936934a 100644
--- a/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
+++ b/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
@@ -3,8 +3,8 @@ title: 'MyCredits tem um erro ao acessar de uma conta dependente'
 id: 6QJWAD7Q2PSEMsmZYXqMag
 status: PUBLISHED
 createdAt: 2022-03-27T16:19:47.411Z
-updatedAt: 2022-11-25T22:08:20.276Z
-publishedAt: 2022-11-25T22:08:20.276Z
+updatedAt: 2024-02-16T20:29:22.908Z
+publishedAt: 2024-02-16T20:29:22.908Z
 firstPublishedAt: 2022-03-27T16:19:47.994Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: mycredits-tem-um-erro-ao-acessar-de-uma-conta-dependente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 367276
 ---
 
diff --git a/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md b/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md
index 62f80db7d..9f74c962c 100644
--- a/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md
+++ b/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md
@@ -34,39 +34,3 @@ internalReference:
   <p>Este conteúdo só está disponível em Inglês.</p>
 </div>
 
-recente. Ele está presente no seguinte componente da IU:
-
- ![](https://vtexhelp.zendesk.com/attachments/token/pFLlcE3tDbGcA0bgmlAhPNccB/?name=image.png)
-
-No entanto, ao combinar esta funcionalidade com a exportação de chapas, este filtro é ignorado, trazendo todos os produtos dentro da coleção.
-
-
-
-
-
-
-## Simulação
-
-
-1 - Vá para o novo módulo de coleções e escolha uma coleção
-
-2 - Na listagem da coleção principal, use o filtro "Recém-liberado", observe que você precisa ter pelo menos 1 produto com o valor "Data de liberação" definido na faixa filtrada. Este valor pode ser definido na página de Configuração do Produto.
-
-3 - Um dado valor de produtos "recém-lançados" será filtrado e listado na interface de usuário.
-
-4 - Selecione a funcionalidade "Exportar
-
-5 - Exportar uma folha SKU para esta coleção
-
-6 - Tcheca o número de registros exportados, será a quantidade total de produtos da coleção, não os recém-libertados.
-
-
-
-
-
-
-## Workaround
-
-
-Utilize filtros alternativos para sua exportação.
-
diff --git a/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md b/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
index 8c5d0c0ad..2702a06b6 100644
--- a/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
+++ b/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
@@ -3,8 +3,8 @@ title: 'A nova IU não mostra o documento de identificação do cliente, por exe
 id: 7y7Npcr6krhsnnEy54vQFa
 status: PUBLISHED
 createdAt: 2022-12-08T22:21:07.966Z
-updatedAt: 2022-12-08T22:21:08.507Z
-publishedAt: 2022-12-08T22:21:08.507Z
+updatedAt: 2024-02-16T20:27:18.190Z
+publishedAt: 2024-02-16T20:27:18.190Z
 firstPublishedAt: 2022-12-08T22:21:08.507Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: a-nova-iu-nao-mostra-o-documento-de-identificacao-do-cliente-por-exemplo-cpf
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 713480
 ---
 
diff --git a/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md b/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
index 11806eba8..07c8c54ad 100644
--- a/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
+++ b/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
@@ -3,8 +3,8 @@ title: 'A nova IU não mostra o valor faturado na página de itens de retorno'
 id: 3DBFXzWoz7jxSdgSLICV8i
 status: PUBLISHED
 createdAt: 2022-09-27T19:34:46.895Z
-updatedAt: 2022-11-25T22:01:19.774Z
-publishedAt: 2022-11-25T22:01:19.774Z
+updatedAt: 2024-02-16T20:28:14.405Z
+publishedAt: 2024-02-16T20:28:14.405Z
 firstPublishedAt: 2022-09-27T19:34:47.384Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: a-nova-iu-nao-mostra-o-valor-faturado-na-pagina-de-itens-de-retorno
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 664838
 ---
 
diff --git a/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md b/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
index 4a1dc54d4..773d88ae3 100644
--- a/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
+++ b/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
@@ -20,7 +20,7 @@ internalReference:
 
 O campo NIF (document) do checkout de Portugal (UI) está permitindo entrada de caracteres especiais nos seus valores. No entanto, os pedidos que forem fechados com caracteres especiais ficam travados com erro no OMS.
 
-![OMS](https://images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
+![OMS](//images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md b/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
new file mode 100644
index 000000000..ac410daed
--- /dev/null
+++ b/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
@@ -0,0 +1,72 @@
+---
+title: 'Nenhuma janela de entrega pode ser criada devido à inconsistência em estimateDate e lastDeliveryDay para timecost alto'
+id: 3E5ZPyrjSOPD68vH4SXunM
+status: PUBLISHED
+createdAt: 2024-03-06T19:38:26.954Z
+updatedAt: 2024-03-06T19:38:27.765Z
+publishedAt: 2024-03-06T19:38:27.765Z
+firstPublishedAt: 2024-03-06T19:38:27.765Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: nenhuma-janela-de-entrega-pode-ser-criada-devido-a-inconsistencia-em-estimatedate-e-lastdeliveryday-para-timecost-alto
+locale: pt
+kiStatus: Backlog
+internalReference: 995491
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+O `estimateDate` leva em conta o tempo total de entrega, mas considerando apenas os dias em que a transportadora entrega, portanto, no caso deste exemplo, não considera os finais de semana.
+Já o `lastDeliveryDay` é calculado como dias corridos (dias consecutivos), que é `data de hoje + tempo de entrega + número máximo de dias` configurado para entrega programada, pois ao contar dias consecutivos, considerará os finais de semana.
+
+Para que o sistema monte a janela de entrega disponível, ele comparará se:
+
+    lastDeliveryDay > estimateDate : TRUE
+
+
+E somente se essa condição for atendida, ele criará a janela de entrega.
+
+Mas com um `timecost` de trânsito total excessivamente alto, há uma inconsistência com a variável `estimateDate` e `lastDeliveryDay`, a condição retornará `false` e, portanto, nenhuma janela de entrega será criada.
+
+
+## Simulação
+
+
+
+Altere a configuração de envio para o seguinte:
+
+- Dias e horas de processamento do depósito com 100 dias;
+- Timecost no arquivo de taxa da planilha com 1 dia;
+- Remova os finais de semana e feriados da configuração da política de remessa;
+- Agendar a entrega para segunda a sexta-feira, das 0h às 23h59;
+- Tempo máximo de entrega na configuração Programar entrega para 5 dias;
+
+Pois essa configuração levará a `lastDeliveryDay=10/05/2024` e a `estimateDate=14/06/2024`;
+E, portanto, a condição será falsa:
+
+    10/05/2024 > 14/06/2024 : FALSO
+
+
+e nenhuma janela de entrega será criada;
+
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md b/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
new file mode 100644
index 000000000..6520beeeb
--- /dev/null
+++ b/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
@@ -0,0 +1,48 @@
+---
+title: 'O desconto nominal baseado na fórmula não está funcionando como esperado com operações de subtração'
+id: 50YsRuiICJNdH2e1QqYnn0
+status: DRAFT
+createdAt: 2023-08-24T13:30:36.935Z
+updatedAt: 2023-08-28T20:44:40.744Z
+publishedAt: 
+firstPublishedAt: 2023-08-24T13:30:37.863Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: o-desconto-nominal-baseado-na-formula-nao-esta-funcionando-como-esperado-com-operacoes-de-subtracao
+locale: pt
+kiStatus: Backlog
+internalReference: 886980
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar uma promoção usando o desconto nominal com base na fórmula, o comerciante pode usar as seguintes operações de acordo com esta documentação: https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV
+ ![](https://vtexhelp.zendesk.com/attachments/token/1EhryrRZDsiXZ31kaSV2VcegW/?name=image.png)
+
+No entanto, ao usar a operação de subtração, o valor do desconto é substituído pelo valor total do pedido.
+
+## Simulação
+
+
+Crie uma promoção usando o desconto nominal com base na fórmula e use uma operação de subtração, como esta:
+ ![](https://vtexhelp.zendesk.com/attachments/token/3wIEiPGtF9oX2daeQ3F3AZqCk/?name=image.png)
+
+Verifique no checkout se o desconto foi substituído pelo que deveria ser o valor total do pedido:
+ ![](https://vtexhelp.zendesk.com/attachments/token/r2bWktL4reNcVnnhSqr4hT0FC/?name=image.png)
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md b/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
index 3766c6f3d..db9508aca 100644
--- a/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
+++ b/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
@@ -3,8 +3,8 @@ title: 'O desconto nominal não está sendo distribuído entre todos os itens do
 id: gt1qMqN71YkaHuZgk9Ibs
 status: PUBLISHED
 createdAt: 2023-01-25T17:33:59.274Z
-updatedAt: 2023-01-25T17:33:59.996Z
-publishedAt: 2023-01-25T17:33:59.996Z
+updatedAt: 2024-07-20T02:22:10.021Z
+publishedAt: 2024-07-20T02:22:10.021Z
 firstPublishedAt: 2023-01-25T17:33:59.996Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -24,31 +24,29 @@ internalReference: 334130
 
 
 
-O desconto nominal não está sendo distribuído entre todos os itens do carrinho.
+O desconto nominal das promoções não está sendo distribuído entre todos os itens do carrinho.
 
-Este cenário está acontecendo apenas em alguns relatos.
+Esse cenário está ocorrendo apenas em algumas contas.
 
-A loja tem uma promoção nominal e o desconto está sendo aplicado apenas em um item do carrinho, não distribuindo proporcionalmente o desconto a todos os itens como é suposto.
+A loja tem uma promoção nominal e o desconto só está sendo aplicado a um item no carrinho, não distribuindo proporcionalmente o desconto a todos os itens, como deveria.
 
+## Simulação
 
-##
 
-## Simulação
 
 
+1. Crie uma promoção regular com um desconto nominal;
+2. Crie um link de carrinho no qual a promoção seja aplicável;
+3. Verifique se o desconto está sendo totalmente aplicado a apenas um item em vez de ser distribuído entre todos os itens.
 
+PS: Isso não acontece sempre e com todas as contas
 
-1. Criar uma promoção regular com um desconto nominal;
-2. Criar um cartlink onde a promoção seja aplicável;
-3. Verificar se o desconto está sendo aplicado inteiramente em apenas um item, em vez de ser distribuído entre todos os itens.
+## Workaround
 
-PS: Isto não acontece sempre e com todas as contas.
 
+Para atenuar esse problema, você pode usar a API Create or Update Coupon API para aumentar o campo `maxItemsPerClient`. Isso permite que o cupom seja aplicado a tantas SKUs quantas forem permitidas nesse campo.
 
-##
 
-## Workaround
 
 
-Nenhuma solução.
 
diff --git a/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md b/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
new file mode 100644
index 000000000..33dae2776
--- /dev/null
+++ b/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
@@ -0,0 +1,62 @@
+---
+title: 'Desconto nominal + Mais por menos + Divisão para o segundo item --> desconto incorreto'
+id: 4hxRWUY6P8aDR9T1KHd3Yf
+status: PUBLISHED
+createdAt: 2024-07-25T16:48:26.511Z
+updatedAt: 2024-07-25T16:48:27.336Z
+publishedAt: 2024-07-25T16:48:27.336Z
+firstPublishedAt: 2024-07-25T16:48:27.336Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: desconto-nominal-mais-por-menos-divisao-para-o-segundo-item-desconto-incorreto
+locale: pt
+kiStatus: Backlog
+internalReference: 1071119
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao configurar uma promoção de desconto nominal acumulada com a promoção "mais por menos", quando há um desconto na promoção "mais por menos" apenas para 1 de 2 itens, isso leva a um desconto incorreto no segundo item do pedido devido à divisão do checkout.
+
+Por exemplo, digamos que haja um desconto de 50% somente para 1 de 2 itens em uma compra e ganhe e, em seguida, um desconto de -$300, com ambas as promoções acumuladas.
+
+Digamos que o item custe US$ 200 e 2 sejam inseridos.
+
+Os descontos **esperados** seriam:
+
+Item (1) ---> -$100 + -$100 --> o segundo item custa apenas $100 porque não há "espaço" adicional para ser reduzido de seu preço.
+Item (2) --> -$200 ---> o restante do desconto para compor o total de -$300
+
+No entanto, o cenário que **acontece atualmente** é:
+
+Item (1) ---> -$100 + -$100 --> o segundo item é de apenas $100 porque não há "espaço" adicional para ser reduzido de seu preço.
+Item (2) --> **-$100 ---> o preço do primeiro item, a partir da divisão, é replicado**
+
+Isso só acontece se os itens com desconto forem mais de 2 unidades do mesmo SKU e o "combo" de promoções especificado acima.
+
+## Simulação
+
+
+1 - criar uma promoção percentual
+2 - crie uma promoção "compre e ganhe" que dê desconto apenas para o segundo item
+3 - insira 2 unidades do referido item no carrinho
+
+OBS: a combinação de preços e descontos deve ser feita de forma que o "valor a ser descontado" do preço do 1º item não seja suficiente para compor 50%+ do valor nominal do descont
+
+## Workaround
+
+
+-
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md b/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
new file mode 100644
index 000000000..f8f67c07e
--- /dev/null
+++ b/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
@@ -0,0 +1,44 @@
+---
+title: 'Não é possível abrir a SKU separada adequada no PDP em uma nova guia'
+id: 26kt6vcKm02TMXDFQPA3ES
+status: PUBLISHED
+createdAt: 2023-07-31T21:20:31.271Z
+updatedAt: 2023-07-31T21:20:31.900Z
+publishedAt: 2023-07-31T21:20:31.900Z
+firstPublishedAt: 2023-07-31T21:20:31.900Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: nao-e-possivel-abrir-a-sku-separada-adequada-no-pdp-em-uma-nova-guia
+locale: pt
+kiStatus: Backlog
+internalReference: 871848
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o recurso de desanexação para dividir produtos por alguma especificação de SKU e tentar abrir uma nova guia do PLP para o PDP, ele não reconhece o parâmetro de propriedade que está sendo passado para o URL para selecionar o SKU correto, apenas exibe o SKU adequado ao abrir na mesma guia.
+
+## Simulação
+
+
+Para isso, você precisará ter uma loja que use o recurso de desvinculação do módulo de pesquisa inteligentehttps://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE
+
+- Ir para qualquer página do PLP
+- Para obter o efeito visual, você deve selecionar qualquer SKU destacada que não seja a SKU padrão do PDP e abri-la em uma nova guia
+- Você notará que a SKU que selecionou não é a mesma SKU que está sendo exibid
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md b/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
index 88a21ed41..776b4289c 100644
--- a/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
+++ b/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
@@ -3,8 +3,8 @@ title: 'Não é possível fazer upload de novas mídias/documentos em um espaço
 id: zhDX1xoXAifH9tYroXCFn
 status: PUBLISHED
 createdAt: 2023-04-24T20:01:04.211Z
-updatedAt: 2023-05-08T18:00:19.246Z
-publishedAt: 2023-05-08T18:00:19.246Z
+updatedAt: 2024-06-28T16:07:27.058Z
+publishedAt: 2024-06-28T16:07:27.058Z
 firstPublishedAt: 2023-04-24T20:01:04.779Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: nao-e-possivel-fazer-upload-de-novas-midiasdocumentos-em-um-espaco-de-trabalho-de-desenvolvimento-quando-a-entidade-tem-mais-de-10-mil-documentos
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 795940
 ---
 
diff --git a/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md b/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
new file mode 100644
index 000000000..5667de272
--- /dev/null
+++ b/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
@@ -0,0 +1,44 @@
+---
+title: 'O relatório Notify-me gera um arquivo corrompido quando não há SKUs encontrados'
+id: 4UXSRdwdh7TTqGvQ3HrBX4
+status: PUBLISHED
+createdAt: 2023-12-20T20:13:33.873Z
+updatedAt: 2023-12-20T20:13:34.707Z
+publishedAt: 2023-12-20T20:13:34.707Z
+firstPublishedAt: 2023-12-20T20:13:34.707Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-relatorio-notifyme-gera-um-arquivo-corrompido-quando-nao-ha-skus-encontrados
+locale: pt
+kiStatus: Backlog
+internalReference: 956264
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o relatório "Notifique-me" não tiver SKUs, a tentativa de exportá-lo gerará um arquivo corrompido para o Excel
+
+## Simulação
+
+
+
+- Verifique se o relatório "Notify Me" está vazio
+- Em caso afirmativo, clique em "Export to Excel" (Exportar para o Excel)
+- Faça o download do arquivo e verifique se é possível abri-l
+
+## Workaround
+
+
+Abra o arquivo em outro software ou preencha o relatório para poder exportar
+
+
+
+
+
diff --git a/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md b/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
index e7b2024f1..c2c8b5b95 100644
--- a/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
+++ b/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
@@ -3,8 +3,8 @@ title: 'O número de itens no filtro de preços não corresponde ao número corr
 id: 1FyjpY1K6JfAQ0gRIuXyuO
 status: PUBLISHED
 createdAt: 2022-03-16T19:37:02.943Z
-updatedAt: 2022-11-25T22:12:33.361Z
-publishedAt: 2022-11-25T22:12:33.361Z
+updatedAt: 2024-02-16T20:24:00.118Z
+publishedAt: 2024-02-16T20:24:00.118Z
 firstPublishedAt: 2022-03-16T19:37:03.370Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: o-numero-de-itens-no-filtro-de-precos-nao-corresponde-ao-numero-correto
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 371405
 ---
 
diff --git a/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md b/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
new file mode 100644
index 000000000..1e4b1b28c
--- /dev/null
+++ b/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
@@ -0,0 +1,49 @@
+---
+title: 'O componente Omnishipping não preencherá o campo PickupReceiver quando o cliente informar pela primeira vez um endereço para entrega'
+id: 0vYgYP5NTflaVEBiAchhL
+status: DRAFT
+createdAt: 2023-12-01T14:11:00.160Z
+updatedAt: 2023-12-04T13:28:38.612Z
+publishedAt: 
+firstPublishedAt: 2023-12-01T14:11:00.848Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-componente-omnishipping-nao-preenchera-o-campo-pickupreceiver-quando-o-cliente-informar-pela-primeira-vez-um-endereco-para-entrega
+locale: pt
+kiStatus: Backlog
+internalReference: 945896
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao usar o componente **Omnishipping** no checkout, o campo **PickupReceiver** aparecerá em branco quando deveria ter o nome que o cliente inseriu na etapa de Identificação. Isso só acontece se o cliente informar primeiro um endereço para entrega e depois clicar na guia Pickup para selecionar um ponto de coleta.
+
+## Simulação
+
+
+
+1. Instale o componente Omnishipping em uma loja sem nenhuma personalização no checkout
+2. Inicie um processo de checkout e preencha as informações de identificação
+3. Selecione um endereço para entrega e, em seguida, clique em Pickup Option (Opção de coleta)
+4. O campo PickupReceiver aparecerá em branco
+
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md b/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
new file mode 100644
index 000000000..b30c67453
--- /dev/null
+++ b/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
@@ -0,0 +1,41 @@
+---
+title: 'Em My Account, a edição do endereço com a informação vermelha de campo obrigatório aparece mesmo depois de preenchida até salvar os dados'
+id: 1QWktgA1c4iyONb8sFCaIh
+status: PUBLISHED
+createdAt: 2023-07-28T20:52:37.170Z
+updatedAt: 2023-07-28T20:52:38.569Z
+publishedAt: 2023-07-28T20:52:38.569Z
+firstPublishedAt: 2023-07-28T20:52:38.569Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: em-my-account-a-edicao-do-endereco-com-a-informacao-vermelha-de-campo-obrigatorio-aparece-mesmo-depois-de-preenchida-ate-salvar-os-dados
+locale: pt
+kiStatus: Backlog
+internalReference: 870891
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na página de edição My Address (Meu endereço) de Minha conta, mesmo que o endereço seja preenchido, a informação vermelha de "Campo obrigatório" aparece até que os dados sejam salvos.
+
+## Simulação
+
+
+Vá para a página Meu endereço, escolha a opção de edição e, depois de preencher o endereço, a mensagem de informação ainda aparecerá até que os dados sejam salvos.
+
+## Workaround
+
+
+Não há solução alternativa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md b/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
index e5d596cc2..f82a5c081 100644
--- a/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
+++ b/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
@@ -3,8 +3,8 @@ title: 'Na página Order Placed, o DataLayer captura apenas as informações do
 id: 5cTy3dCZ6x7FNMKvBbc9s8
 status: PUBLISHED
 createdAt: 2023-01-04T21:06:17.111Z
-updatedAt: 2023-01-10T19:08:17.450Z
-publishedAt: 2023-01-10T19:08:17.450Z
+updatedAt: 2024-02-16T20:23:30.519Z
+publishedAt: 2024-02-16T20:23:30.519Z
 firstPublishedAt: 2023-01-04T21:14:00.744Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: authors_84
 tag: Order Management
 slug: na-pagina-order-placed-o-datalayer-captura-apenas-as-informacoes-do-primeiro
 locale: pt
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 727339
 ---
 
diff --git a/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md b/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
new file mode 100644
index 000000000..ea00a3719
--- /dev/null
+++ b/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
@@ -0,0 +1,37 @@
+---
+title: 'O=OrderByPriceASC (ou OrderByPriceDESC) pode gerar o pedido errado'
+id: 2XCplZQutilKeD2bNnjYDx
+status: PUBLISHED
+createdAt: 2022-05-20T15:48:15.215Z
+updatedAt: 2024-06-21T11:29:11.233Z
+publishedAt: 2024-06-21T11:29:11.233Z
+firstPublishedAt: 2022-05-20T15:48:16.089Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: oorderbypriceasc-ou-orderbypricedesc-pode-gerar-o-pedido-errado
+locale: pt
+kiStatus: Backlog
+internalReference: 582861
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+**O=OrderByPriceASC** (ou **OrderByPriceDESC**) pode usar a política errada para pedir preços. Além disso, como o preço indexado tem apenas uma casa decimal, a segunda casa decimal do preço não será considerada.
+
+Além disso, os preços de vendedores não abrangentes não são considerados na classificação. Como resultado, as lojas regionalizadas no Portal não podem usar o parâmetro **orderByPrice**.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md b/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md
new file mode 100644
index 000000000..0e3460367
--- /dev/null
+++ b/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md
@@ -0,0 +1,35 @@
+---
+title: 'O gancho para abrir/fechar modais afeta todos os modais da página'
+id: l1G3HN5Y3LxYVzuMnhjkL
+status: PUBLISHED
+createdAt: 2024-05-31T19:16:13.601Z
+updatedAt: 2024-06-04T12:14:19.271Z
+publishedAt: 2024-06-04T12:14:19.271Z
+firstPublishedAt: 2024-05-31T19:16:14.596Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-gancho-para-abrirfechar-modais-afeta-todos-os-modais-da-pagina
+locale: pt
+kiStatus: Backlog
+internalReference: 1042165
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao abrir/fechar um modal, a ação afeta todos os modais da página
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md b/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
new file mode 100644
index 000000000..0ff60c6ba
--- /dev/null
+++ b/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
@@ -0,0 +1,47 @@
+---
+title: 'As operações não podem ser executadas corretamente devido ao campo documentType nulo.'
+id: 5cZWkKc0ZXnMZCw4bvXJjA
+status: PUBLISHED
+createdAt: 2023-05-11T17:33:04.077Z
+updatedAt: 2023-12-06T15:21:16.013Z
+publishedAt: 2023-12-06T15:21:16.013Z
+firstPublishedAt: 2023-05-11T17:33:04.511Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: as-operacoes-nao-podem-ser-executadas-corretamente-devido-ao-campo-documenttype-nulo
+locale: pt
+kiStatus: Backlog
+internalReference: 697107
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns provedores precisam necessariamente que `documentType` seja diferente de `null`, ou seja, que seja preenchido corretamente para realizar algumas operações de pagamento.
+
+Até o momento, temos dois cenários conhecidos:
+
+1. A ausência desse campo não permite que o pagamento seja analisado corretamente pelo antifraude, o que faz com que a transação corra risco.
+2. A ausência do campo impede que o pagamento seja autorizado e, consequentemente, faz com que a transação seja cancelada.
+
+## Simulação
+
+
+Esse problema ocorre quando um cliente usa informações de uma empresa para concluir um pedido.
+Se o nome da empresa for usado para concluir a transação, o campo `documentType` não será preenchido, causando problemas com a aprovação do pagamento.
+
+
+
+## Workaround
+
+
+
+Para o primeiro cenário, é possível usar uma API interna para ignorar a etapa de análise antifraude.
+Apesar de ser fortemente desencorajada, essa é uma operação possível.
+
diff --git a/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md b/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md
index 9ea106816..b73fcf00a 100644
--- a/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md
+++ b/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md
@@ -3,8 +3,8 @@ title: 'O pedido novamente do histórico de pedidos B2B não funciona'
 id: 2kT6UJsivYRgEaYpeRpEWa
 status: PUBLISHED
 createdAt: 2023-05-05T13:16:44.403Z
-updatedAt: 2023-05-08T18:34:38.873Z
-publishedAt: 2023-05-08T18:34:38.873Z
+updatedAt: 2023-09-19T21:46:58.308Z
+publishedAt: 2023-09-19T21:46:58.308Z
 firstPublishedAt: 2023-05-05T13:16:45.530Z
 contentType: knownIssue
 productTeam: B2B
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: B2B
 slug: o-pedido-novamente-do-historico-de-pedidos-b2b-nao-funciona
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 819920
 ---
 
diff --git a/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md b/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md
new file mode 100644
index 000000000..1fc191d16
--- /dev/null
+++ b/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md
@@ -0,0 +1,48 @@
+---
+title: 'A autorização de pedido inferior a 100 segue o fluxo'
+id: 51vxznnbek6mtVtQgKEW9d
+status: PUBLISHED
+createdAt: 2024-02-16T13:44:05.199Z
+updatedAt: 2024-02-16T13:44:05.932Z
+publishedAt: 2024-02-16T13:44:05.932Z
+firstPublishedAt: 2024-02-16T13:44:05.932Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: a-autorizacao-de-pedido-inferior-a-100-segue-o-fluxo
+locale: pt
+kiStatus: Backlog
+internalReference: 983031
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Identificamos que quando o sistema de Autorização de Pedidos (OrderAuth) é configurado com o valor "lessThan: 100", no "Rules-list.CreateDoEffect" , ele não consegue entender que é menor ou igual a 100%, apenas que é menor que 100% e quando o pedido tem um desconto de 100%, o sistema autoriza que o pedido siga o fluxo normal.
+
+## Simulação
+
+
+Para simular é necessário configurar o orderAuth:
+Acesso: https://.myvtex.com/admin/order-auth
+Configure a divergência de preços > insira os seguintes valores na regra:
+Rules-list.denyEffect :0 a 60%
+
+Rules-list.CreateDoEffect: 61 a 100%
+
+Ao configurar a regra "Rules-list.CreateDoEffect" para 100%, ele não consegue entender que é menor ou igual, apenas que é menor e, portanto, autoriza que a solicitação siga o fluxo normal quando for igual a 100%
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md b/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md
index 45c30928d..9af6c8649 100644
--- a/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md
+++ b/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md
@@ -3,8 +3,8 @@ title: 'Informações do cartão de pedido causando confusão no Status'
 id: 2f0nEqccswuyWEcwdqiRZS
 status: PUBLISHED
 createdAt: 2022-08-18T19:04:12.824Z
-updatedAt: 2022-11-25T22:01:43.687Z
-publishedAt: 2022-11-25T22:01:43.687Z
+updatedAt: 2024-02-16T20:24:07.700Z
+publishedAt: 2024-02-16T20:24:07.700Z
 firstPublishedAt: 2022-08-18T19:04:13.465Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: informacoes-do-cartao-de-pedido-causando-confusao-no-status
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 619778
 ---
 
diff --git a/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md b/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
index 2cd0d90a3..1e1fd5821 100644
--- a/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
+++ b/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
@@ -3,8 +3,8 @@ title: 'A criação de pedidos falhou devido à divergência de preços na camad
 id: 31fiMPNRULuOH73AhlzU5K
 status: PUBLISHED
 createdAt: 2022-02-03T15:24:07.791Z
-updatedAt: 2022-11-25T21:52:40.751Z
-publishedAt: 2022-11-25T21:52:40.751Z
+updatedAt: 2024-02-16T20:26:40.128Z
+publishedAt: 2024-02-16T20:26:40.128Z
 firstPublishedAt: 2022-02-03T15:24:08.353Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-criacao-de-pedidos-falhou-devido-a-divergencia-de-precos-na-camada-de-cumprimento
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 512393
 ---
 
diff --git a/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md b/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
index ce723737e..67001b9ae 100644
--- a/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
+++ b/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
@@ -1,10 +1,10 @@
 ---
-title: 'O Relatório de Exportação de Pedidos não está funcionando corretamente devido ao espaço duplo no nome da Promoção'
+title: 'O relatório de exportação de pedidos não está funcionando corretamente devido ao espaço duplo no nome da promoção'
 id: 3dVPZEs544WyPDBNzTesWx
 status: PUBLISHED
 createdAt: 2023-04-06T20:22:47.489Z
-updatedAt: 2023-04-06T20:22:48.141Z
-publishedAt: 2023-04-06T20:22:48.141Z
+updatedAt: 2024-06-28T17:44:15.662Z
+publishedAt: 2024-06-28T17:44:15.662Z
 firstPublishedAt: 2023-04-06T20:22:48.141Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: o-relatorio-de-exportacao-de-pedidos-nao-esta-funcionando-corretamente-devido-ao-espaco-duplo-no-nome-da-promocao
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 786216
 ---
 
@@ -23,27 +23,22 @@ internalReference: 786216
 </div>
 
 
-Para promoção de pedidos, não é correto usar espaço doble ou caráter especial nos nomes, isto pode quebrar o filtro ou faltar algum pedido no relatório de exportação do pedido.
-Nome na matriz "ratesAndBenefitsData".
-
-
-##
+O sistema de relatório de pedidos atualmente não consegue criar um arquivo a partir de filtros de promoção que contêm espaços duplos em seus nomes. Ao tentar criar o relatório, o sistema gera um erro e a exportação não é realizada, resultando na mensagem "_Exportação concluída. 0 pedidos foram enviados para seu e-mail"_.
 
 ## Simulação
 
 
-Criar pedido usando alguma promoção com nome incorreto, por exemplo, com espaço doble no nome.
-Depois disso, vai para o gerenciamento de pedidos todos os pedidos e executa um filtro com esta promoção como condição.
-Nesse momento você pode ver o pedido na lista de pedidos filtrados, mas escolhendo o relatório de exportação que a exportação não obterá o pedido com promoção com espaço duplo.
 
+Crie um pedido usando alguma promoção cujo nome contenha espaços duplos;
 
-##
+Depois disso, vá para o gerenciamento de pedidos e execute um filtro com essa promoção como condição.
 
-## Workaround
+Nesse ponto, a IU do OMS exibirá normalmente uma lista de pedidos com a condição escolhida, mas, ao selecionar a exportação de pedidos, a IU retornará a seguinte mensagem: "_Exportação concluída. 0 pedidos foram enviados para seu e-mail_"
 
+## Workaround
 
-Não há nenhuma solução disponível.
 
+Filtre os pedidos na interface do usuário por outro parâmetro, por exemplo, data, forma de pagamento etc., depois exporte os pedidos e filtre-os por promoção diretamente no arquivo Excel gerado pelo sistema.
 
 
 
diff --git a/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
new file mode 100644
index 000000000..2cdd9a57d
--- /dev/null
+++ b/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -0,0 +1,55 @@
+---
+title: 'O filtro de pedidos não funciona corretamente devido a aspas duplas (") no nome da promoção ou no nome da SKU'
+id: 4Qm0akQTQXR8sSbkTDiBL7
+status: PUBLISHED
+createdAt: 2024-06-06T15:42:19.747Z
+updatedAt: 2024-06-06T15:42:20.627Z
+publishedAt: 2024-06-06T15:42:20.627Z
+firstPublishedAt: 2024-06-06T15:42:20.627Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-filtro-de-pedidos-nao-funciona-corretamente-devido-a-aspas-duplas-no-nome-da-promocao-ou-no-nome-da-sku
+locale: pt
+kiStatus: Backlog
+internalReference: 1045623
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, o sistema de filtro de pedidos não retorna os pedidos com promoções que contenham aspas duplas `"` em seus nomes, o que também se aplica ao nome da SKU.
+
+## Simulação
+
+
+Para reproduzir esse cenário, siga as etapas abaixo.
+
+1. Crie uma promoção/sku com aspas duplas `"` no nome;
+Exemplo: Nome da promoção como `10% de desconto usando o cupom "DIAGEO" (8)`
+2. Crie um pedido de teste:
+
+  1. No ambiente da loja (storefront), selecione um item e adicione-o ao carrinho;
+  2. Certifique-se de que a promoção seja aplicada;
+  3. Vá para o checkout e faça o pedido.
+3. Vá para **Orders > Order management**;
+4. Clique em "Todos os pedidos";
+5. Use o **filtro** para selecionar a promoção que você adicionou;
+6. Observe que nenhum pedido é encontrado com o filtro selecionado, e a mensagem retornada na interface do usuário é: `Nenhum pedido encontrado. Limpe seus filtros e tente uma pesquisa diferente.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md b/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md
new file mode 100644
index 000000000..75ae372c0
--- /dev/null
+++ b/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md
@@ -0,0 +1,43 @@
+---
+title: 'Pedido não notificado, transportadora deixa etiqueta com código de barras incompleto'
+id: 2QjxFv2Ul2wKCdnYtrlF0T
+status: PUBLISHED
+createdAt: 2023-08-01T16:55:39.774Z
+updatedAt: 2023-09-18T22:52:54.573Z
+publishedAt: 2023-09-18T22:52:54.573Z
+firstPublishedAt: 2023-08-01T16:55:40.545Z
+contentType: knownIssue
+productTeam: VTEX Shipping Network (VTEX Log)
+author: 2mXZkbi0oi061KicTExNjo
+tag: VTEX Shipping Network (VTEX Log)
+slug: pedido-nao-notificado-transportadora-deixa-etiqueta-com-codigo-de-barras-incompleto
+locale: pt
+kiStatus: Backlog
+internalReference: 872530
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os clientes que usam transportadoras parceiras da Shipping Network, ao solicitarem a emissão de etiquetas no Ready to Ship, podem receber o arquivo com o código de barras incompleto, o que pode impedir que o pacote seja postado.
+
+## Simulação
+
+
+Não foi possível reproduzir, apenas verificar conferindo as etiquetas enviadas pelos clientes com o código de barras incompleto e confirmando via API que o pacote não foi notificado.
+
+
+
+## Workaround
+
+
+A notificação manual do pedido novamente garante que a transportadora seja notificada e que o código de barras esteja completo e a etiqueta possa ser usada.
+
+
+
+
+
diff --git a/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md b/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md
index 172aeb7ce..27fd4c20a 100644
--- a/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md
+++ b/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md
@@ -1,10 +1,10 @@
 ---
 title: 'A devolução parcial do pedido acionou a devolução total da transação'
 id: 5cPpyvV4t6swxDPrEmuzrn
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-04-04T21:20:39.334Z
-updatedAt: 2022-11-25T22:03:29.435Z
-publishedAt: 2022-11-25T22:03:29.435Z
+updatedAt: 2024-05-28T19:09:23.158Z
+publishedAt: 
 firstPublishedAt: 2022-04-04T21:20:40.180Z
 contentType: knownIssue
 productTeam: Order Management
diff --git a/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md b/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
new file mode 100644
index 000000000..3c81d6967
--- /dev/null
+++ b/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
@@ -0,0 +1,43 @@
+---
+title: 'O recurso de substituição de pedidos não funciona quando o carrinho substituído e o pedido original têm o mesmo valor'
+id: 7eHiC34Pgsr1XcfIVHl7Sc
+status: PUBLISHED
+createdAt: 2023-07-21T14:49:31.057Z
+updatedAt: 2023-12-18T20:17:32.757Z
+publishedAt: 2023-12-18T20:17:32.757Z
+firstPublishedAt: 2023-07-21T14:49:31.682Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-recurso-de-substituicao-de-pedidos-nao-funciona-quando-o-carrinho-substituido-e-o-pedido-original-tem-o-mesmo-valor
+locale: pt
+kiStatus: Fixed
+internalReference: 866622
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O recurso de substituição de pedidos não funciona quando o carrinho substituído tem o mesmo valor do pedido original e o sistema de pagamento é "Reutilizar pagamento".
+
+## Simulação
+
+
+
+- Ative o recurso de substituição de pedidos;
+- Conclua um pedido e altere algo, por exemplo, do tamanho pequeno para o grande;
+- Certifique-se de que o carrinho substituído tenha o mesmo valor que o pedido original;
+- Na etapa de pagamento, selecione "Reuse Payment" (Reutilizar pagamento)
+
+## Workaround
+
+
+Selecione um método de pagamento diferente de "Reuse Payment" (Reutilizar pagamento). A transação anterior será cancelada e reembolsada; uma nova transação será criada.
+
+
+
diff --git a/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md b/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
new file mode 100644
index 000000000..69b1c7650
--- /dev/null
+++ b/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
@@ -0,0 +1,49 @@
+---
+title: 'Inconsistência no relatório de pedidos quando o campo tid é duplicado no campo connectorResponses da API de detalhes de pagamento GET.'
+id: 4xXSp2RMyHMeHpEUXgmpAZ
+status: PUBLISHED
+createdAt: 2023-09-06T21:18:05.941Z
+updatedAt: 2023-09-06T21:18:06.733Z
+publishedAt: 2023-09-06T21:18:06.733Z
+firstPublishedAt: 2023-09-06T21:18:06.733Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: inconsistencia-no-relatorio-de-pedidos-quando-o-campo-tid-e-duplicado-no-campo-connectorresponses-da-api-de-detalhes-de-pagamento-get
+locale: pt
+kiStatus: Backlog
+internalReference: 895664
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os conectores dessa lista precisam salvar mais campos para o conector que funciona com o aplicativo "Venda direta" - Vendas. Especificamente, para os conectores listados abaixo, e somente para eles, todo o conteúdo do payload deve ser direcionado para o campo "`connectorResponses`". Isso resulta em uma duplicação do campo "`tid`", que já existe em "`connectorResponses`". Embora essa duplicação não represente um problema em termos do ciclo de vida da transação, ela cria uma inconsistência ao gerar relatórios a partir da página do pedido.
+
+
+- PagarMeV3
+- PagarMeV3Stg
+- Adyen V3
+
+## Simulação
+
+
+
+1. Acesse a página de pedidos do administrador.
+2. Gerar o relatório de pedidos.
+3. Procure a coluna `tId` onde os pedidos foram feitos usando um destes conectore
+
+## Workaround
+
+
+Use a rota /payment ou a API GET order para recuperar esses dados
+
+
+
+
+
diff --git a/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md b/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
new file mode 100644
index 000000000..4217221a7
--- /dev/null
+++ b/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
@@ -0,0 +1,55 @@
+---
+title: 'Pedido preso no status de vendedor cancellation-request-denied-ffm'
+id: 5hBeTQMKmo5C63QRAOSvT2
+status: PUBLISHED
+createdAt: 2024-03-22T17:50:37.946Z
+updatedAt: 2024-03-22T17:50:38.822Z
+publishedAt: 2024-03-22T17:50:38.822Z
+firstPublishedAt: 2024-03-22T17:50:38.822Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: pedido-preso-no-status-de-vendedor-cancellationrequestdeniedffm
+locale: pt
+kiStatus: Backlog
+internalReference: 1004978
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Identificamos que alguns vendedores, na estrutura do vendedor e do marketplace da VTEX, ao solicitarem o cancelamento, recusam esse cancelamento por meio da interface do usuário ou chamam a API "cancellation-request-denied-ffm", como se estivessem negando a própria solicitação de cancelamento, por algum motivo, a solicitação para negar o cancelamento se sobrepõe à solicitação de cancelamento.
+Como resultado, o pedido fica preso no vendedor, no status "cancellation-request-denied-ffm".
+E, em alguns casos, o próprio marketplace tenta solicitar o cancelamento e, como resultado, o marketplace também fica preso no status "request cancellation".
+Por outro lado, temos o caso em que o marketplace não recebe essa notificação de cancelamento e continua com seu pedido até o status Invoiced!
+Em todos os casos, não podemos alterar o status desses pedidos.
+
+## Simulação
+
+
+1- Crie um pedido, com o vendedor whiteLabel;
+2- No pedido do vendedor, avançar o status para "handling";
+3- Ainda no vendedor, solicitar o cancelamento do pedido;
+4- Na solicitação do vendedor, teremos a mensagem, "accept or refuse cancellation", clique na opção refuse no vendedor ou utilize a API, você verá que a solicitação do vendedor irá para o status "cancellation-request-denied-ffm".
+5- No pedido do Marketplace, clique em cancelar;
+6- O pedido do Marketplace ficará preso em "Request-Cancel";
+
+Pode acontecer que o pedido do Marketplace continue com o pedido e vá para a fatura, quando ele envia a fatura.
+
+
+
+## Workaround
+
+
+Esta não é uma solução alternativa, mas uma orientação para as contas, uma vez que o vendedor solicite o cancelamento, não recuse a solicitação em si.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md b/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
new file mode 100644
index 000000000..145b955a9
--- /dev/null
+++ b/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
@@ -0,0 +1,48 @@
+---
+title: 'Pedido preso no status Pendente de pagamento devido à falta de notificação de pagamento aprovado'
+id: 1yM3alrrYhrpdZhBPLslZC
+status: PUBLISHED
+createdAt: 2024-05-24T15:04:47.795Z
+updatedAt: 2024-05-24T15:04:48.820Z
+publishedAt: 2024-05-24T15:04:48.820Z
+firstPublishedAt: 2024-05-24T15:04:48.820Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: pedido-preso-no-status-pendente-de-pagamento-devido-a-falta-de-notificacao-de-pagamento-aprovado
+locale: pt
+kiStatus: Backlog
+internalReference: 1031035
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+No status "Payment Pending" (Pagamento pendente), espera-se que uma notificação de pagamento seja enviada ao módulo Orders (Pedidos). Durante esse período, podem ocorrer alguns problemas com o processamento de eventos.
+A fila de mensagens fornece um protocolo de comunicação assíncrono, no qual os eventos são colocados em uma fila para serem consumidos em um momento predeterminado no futuro.
+Este KI refere-se explicitamente aos cenários com conectores PPP e não tem a intenção de esgotar todas as possibilidades de problemas de processamento de eventos que possam ocorrer.
+
+## Simulação
+
+
+
+Não há como simular esse comportamento.
+
+
+
+## Workaround
+
+
+
+Entre em contato com nossa equipe de suporte para reprocessar manualmente o evento.
+
+
+
+
+
diff --git a/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md b/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
new file mode 100644
index 000000000..3b3b97b13
--- /dev/null
+++ b/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
@@ -0,0 +1,34 @@
+---
+title: 'O pedido com juros tem problemas ao tentar devolver todos os itens e reembolsar o pagamento total'
+id: 2J5XD9jjQfZWMVg0yYMzUa
+status: PUBLISHED
+createdAt: 2023-09-18T20:53:08.156Z
+updatedAt: 2023-09-18T20:53:08.813Z
+publishedAt: 2023-09-18T20:53:08.813Z
+firstPublishedAt: 2023-09-18T20:53:08.813Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-pedido-com-juros-tem-problemas-ao-tentar-devolver-todos-os-itens-e-reembolsar-o-pagamento-total
+locale: pt
+kiStatus: Backlog
+internalReference: 376077
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+### **Resumo**
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md b/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
index 4d5ec37c6..764db3f5f 100644
--- a/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
+++ b/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
@@ -3,8 +3,8 @@ title: 'Pedido sem assinatura Criado e sem e-mail de Novos Pedidos em Casos rela
 id: 747TGL3sy1mmM1LnVkEjuO
 status: PUBLISHED
 createdAt: 2022-02-21T20:54:35.174Z
-updatedAt: 2022-11-25T22:03:15.831Z
-publishedAt: 2022-11-25T22:03:15.831Z
+updatedAt: 2024-02-16T20:23:42.061Z
+publishedAt: 2024-02-16T20:23:42.061Z
 firstPublishedAt: 2022-05-18T18:43:19.767Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: pedido-sem-assinatura-criado-e-sem-email-de-novos-pedidos-em-casos-relacionados-ao-metodo-de-pagamento-usando-conectadores-como-payment-app-ou-redirect
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 529143
 ---
 
diff --git a/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md b/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md
index 774fce7e6..fb70c283c 100644
--- a/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md
+++ b/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md
@@ -1,18 +1,18 @@
 ---
-title: 'Pedido com status de cancelado mas o pagamento continua autorizado'
+title: 'Pedido com status de cancelado, mas o pagamento continua autorizado'
 id: 19WmIjIbAQmJ19AOC4q56N
 status: PUBLISHED
 createdAt: 2022-05-11T12:49:23.081Z
-updatedAt: 2022-11-25T21:51:23.997Z
-publishedAt: 2022-11-25T21:51:23.997Z
+updatedAt: 2024-06-28T17:45:57.362Z
+publishedAt: 2024-06-28T17:45:57.362Z
 firstPublishedAt: 2022-05-11T12:49:23.599Z
 contentType: knownIssue
-productTeam: Checkout
+productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
-tag: Checkout
+tag: Order Management
 slug: pedido-com-status-de-cancelado-mas-o-pagamento-continua-autorizado
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 420019
 ---
 
@@ -23,14 +23,12 @@ internalReference: 420019
 </div>
 
 
-Em alguns casos em que o pedido é incompleto ou cancelado quando há qualquer falha de comunicação com o Gateway, o pagamento permanece autorizado e/ou aprovado, não entrando no fluxo de cancelamento e o valor pago não é automaticamente reembolsado. Além disso, e-mails transacionais podem ser enviados acidentalmente, o que também permite o pagamento de boletos bancários, uma vez que a URL irá com ele.
-
-
+Em alguns casos em que o pedido é incompleto ou cancelado quando há alguma falha de comunicação com o Gateway, o pagamento permanece autorizado e/ou aprovado, não entrando no fluxo de cancelamento e o valor pago não é reembolsado automaticamente. Além disso, e-mails transacionais podem ser enviados acidentalmente, o que também permite o pagamento de boletos bancários, pois a URL irá junto.
 
 ## Simulação
 
 
-Não há como simular. Mas temos alguns casos em que isto já aconteceu antes.
+Não há como simular. Mas temos alguns casos em que isso aconteceu antes.
 
 
 
diff --git a/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md b/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
index 6d2754c8b..b4cd79fea 100644
--- a/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
+++ b/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
@@ -1,18 +1,18 @@
 ---
-title: 'OrderForm API impedindo a seleção do método de envio para o mesmo item sob vendedores diferentes'
+title: 'A API do OrderForm impede a seleção do método de envio para o mesmo item em diferentes vendedores'
 id: 4dEfq7lNqTLF7SFIOaRsc2
 status: PUBLISHED
 createdAt: 2023-01-27T21:56:04.190Z
-updatedAt: 2023-01-27T22:03:21.165Z
-publishedAt: 2023-01-27T22:03:21.165Z
+updatedAt: 2023-07-05T14:33:51.370Z
+publishedAt: 2023-07-05T14:33:51.370Z
 firstPublishedAt: 2023-01-27T21:56:04.914Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: orderform-api-impedindo-a-selecao-do-metodo-de-envio-para-o-mesmo-item-sob-vendedores-diferentes
+slug: a-api-do-orderform-impede-a-selecao-do-metodo-de-envio-para-o-mesmo-item-em-diferentes-vendedores
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 742139
 ---
 
@@ -23,20 +23,14 @@ internalReference: 742139
 </div>
 
 
-Embora um formulário de pedido suporte o mesmo SKU a ser adicionado várias vezes através de diferentes vendedores, ele não permite que o método de envio (SLA) seja selecionado individualmente - onde a logística para um vendedor é completamente independente dos outros.
+Embora um formulário de pedido ofereça suporte para que a mesma SKU seja adicionada várias vezes por meio de diferentes vendedores, ele não permite que o método de envio (SLA) seja selecionado individualmente, onde a logística de um vendedor é completamente independente dos outros.
 
-Apesar disso, após informar o endereço ou escolher um método de envio disponível apenas para uma ocorrência específica da SKU, as outras ocorrências estarão sob um SLA diferente sem que isso seja um problema. Portanto, a questão é restrita à solicitação selecionando o SLA entre os itens neste cenário ou através de simulação do OrderForm.
-
-
-##
+Apesar disso, após informar o endereço ou escolher um método de envio disponível apenas para uma ocorrência específica do SKU, as demais ocorrências estarão sob um SLA diferente sem que isso seja um problema. Portanto, o problema se restringe à solicitação de seleção do SLA entre itens nesse cenário ou via simulação de orderForm.
 
 ## Simulação
 
 
-Em um carrinho com o mesmo item adicionado mais de uma vez, mas através de vendedores diferentes, tente selecionar seus métodos de envio (SLAs) através do API, usando opções diferentes para cada um. O mesmo cenário também pode ser experimentado através do API de simulação, declarando um "selectedSlaId". O API recusará a ação apresentando a mensagem "O mesmo item não pode ter mais de um SLA selecionado".
-
-
-##
+Em um carrinho com o mesmo item adicionado mais de uma vez, mas por meio de vendedores diferentes, tente selecionar seus métodos de envio (SLAs) por meio da API usando opções diferentes para cada um. O mesmo cenário também pode ser tentado por meio da API de simulação, declarando um "selectedSlaId". A API recusará a ação apresentando a mensagem "Same item cannot have more than one SLA selected" (O mesmo item não pode ter mais de um SLA selecionado)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md b/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
index b396dd47c..a06a7584a 100644
--- a/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
+++ b/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
@@ -1,16 +1,16 @@
 ---
-title: "orderForm (Chk API) suggesting invalid scheduled delivery that can't be used"
+title: 'orderForm (Chk API) sugerindo uma entrega programada inválida que não pode ser usada'
 id: 7e2bSJSJa938QCrOHkRibZ
 status: PUBLISHED
 createdAt: 2022-01-24T20:20:11.732Z
-updatedAt: 2023-03-21T19:26:09.280Z
-publishedAt: 2023-03-21T19:26:09.280Z
+updatedAt: 2023-12-01T14:08:09.892Z
+publishedAt: 2023-12-01T14:08:09.892Z
 firstPublishedAt: 2023-03-21T19:26:09.280Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
-tag: 
-slug: orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used
+tag: Checkout
+slug: orderform-chk-api-sugerindo-uma-entrega-programada-invalida-que-nao-pode-ser-usada
 locale: pt
 kiStatus: Backlog
 internalReference: 298665
@@ -18,26 +18,33 @@ internalReference: 298665
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
-Quando um carrinho/ordemForm tem vários itens com entrega programada, as opções programadas que têm a mesma identificação (portanto, considerado o mesmo método de envio) precisam ter as mesmas janelas de entrega entre eles. Se não houver interseção, o método de envio será descartado para alguns itens.
 
-A questão é que, em alguns fluxos, como o "GET orderForm" API, este comportamento de filtragem não está sendo aplicado, oferecendo uma entrega programada inválida (sem interseção). Em outros fluxos, como na "orderForm simulation" ou enquanto de fato se seleciona o método de envio, a opção oferecida será corretamente filtrada/removida.
+Quando um carrinho/formulário de pedido tem vários itens com entrega programada do mesmo vendedor, as opções programadas com o mesmo ID (consideradas o mesmo método de envio) precisam ter as mesmas janelas de entrega entre elas. Se não houver interseção, o método de envio será descartado para alguns itens.
 
-Efeito colateral: o Chk UI tentará usar/simular a opção inválida e pode ficar trancado em um loop de **pedidos**, porque o método de envio está disponível no primeiro momento, mas não pode ser usado em um segundo momento, e o aplicativo UI tentará novamente o primeiro passo enquanto revisa as opções disponíveis no orderForm.
+O problema é que, em alguns fluxos, como a API "GET orderForm", esse comportamento de filtragem não está sendo aplicado, oferecendo uma entrega agendada inválida (sem interseção). Em outros fluxos, como na "simulação do orderForm" ou ao selecionar o método de envio, a opção oferecida será corretamente filtrada/removida.
+
+Efeito colateral: a interface do usuário do Chk tentará usar/simular a opção inválida e poderá ficar travada em um **requests loop** porque o método de envio está disponível no primeiro momento, mas não pode ser usado em um segundo momento, e a interface do usuário tenta a primeira etapa novamente ao revisar as opções disponíveis no orderForm.
 
 ## Simulação
 
-- ter duas políticas de transporte marítimo diferentes (transportadores) com o mesmo "tipo de frete" (que define o "slaId")
-- ambos programados, mas com uma janela de entrega diferente entre eles
-- ter um item para cada política de embarque
-- incluir ambos os itens no carrinho e simular o envio
 
-Neste momento, a IU pode permanecer fechada em um loop devido à divergência entre o "GET orderForm" e a "orderForm simulação".
+
+- No mesmo vendedor, configure duas políticas de remessa diferentes (transportadoras) com o mesmo "tipo de frete" (que define o "slaId");
+- Ambas têm entrega programada, mas com uma janela de entrega diferente entre elas;
+- Adicione 2 itens ao carrinho, um item de cada política de envio.
+
+A interface do usuário pode ficar travada em um loop devido à divergência entre o "GET orderForm" e a "simulação do orderForm"
 
 ## Workaround
 
-É necessário fixar a janela de entrega entre os métodos de envio que têm a mesma identificação (para ter as mesmas janelas de entrega), ou tratá-los como métodos de envio diferentes, assim utilizando identificações diferentes.
+
+É necessário corrigir a janela de entrega entre os métodos de envio com o mesmo ID (para ter as mesmas janelas de entrega) ou tratá-los como métodos de envio diferentes, usando IDs diferentes.
+
+
+
+
 
diff --git a/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md b/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md
index 09180ae1e..97f9f184c 100644
--- a/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md
+++ b/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md
@@ -1,18 +1,18 @@
 ---
-title: 'OrderForm não devolve os dados do cliente mesmo para credenciais autorizadas'
+title: 'O OrderForm não retorna os dados do cliente mesmo para credenciais autorizadas'
 id: JcjDusU8YP0kerWXC6LXK
 status: PUBLISHED
 createdAt: 2022-05-19T16:25:28.039Z
-updatedAt: 2023-02-01T21:29:33.875Z
-publishedAt: 2023-02-01T21:29:33.875Z
+updatedAt: 2023-09-27T20:39:27.746Z
+publishedAt: 2023-09-27T20:39:27.746Z
 firstPublishedAt: 2022-05-19T16:25:28.427Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: orderform-nao-devolve-os-dados-do-cliente-mesmo-para-credenciais-autorizadas
+slug: o-orderform-nao-retorna-os-dados-do-cliente-mesmo-para-credenciais-autorizadas
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 582070
 ---
 
@@ -23,30 +23,24 @@ internalReference: 582070
 </div>
 
 
-Interagindo com um formulário de pedidoFormulário na situação específica em que os dados do cliente foram importados automaticamente após o login removerá seus dados do formulário de pedidoFormulário mesmo para "superusuários", identificados por seus appKeys.
+Interagir com um orderForm na situação específica em que os dados do cliente foram importados automaticamente após o login removerá seus dados do orderForm, mesmo para "superusuários", identificados por suas appKeys.
 
-Esta ação é feita para evitar o acesso não intencional aos dados dos clientes, mas não deve ser aplicada a usuários administrativos e integrações identificadas por credenciais autorizadas.
-
-
-##
+Essa ação é feita para evitar o acesso não intencional aos dados dos clientes, mas não deve ser aplicada a usuários administrativos e integrações identificados por credenciais autorizadas.
 
 ## Simulação
 
 
 
-- Ter um usuário com um perfil completo, garantindo que seja válido para o comportamento do SmartCheckout
-- Faça o processo de login para este usuário
-- Revise através do navegador se suas informações foram importadas para o pedidoFormulário
-- Fazer um pedido "Get OrderForm" enquanto usa credenciais autorizadas
-- OrderForm não retornará os "clientProfileData" e os endereços que estavam disponíveis no navegador
-
-
-##
+- Tenha um usuário com um perfil completo, garantindo que ele seja válido para o comportamento do SmartCheckout
+- Faça o processo de login para esse usuário
+- Verificar pelo navegador se as informações do usuário foram importadas para o orderForm
+- Fazer uma solicitação "Get OrderForm" usando credenciais autorizadas
+- O OrderForm não retornará os "clientProfileData" e os endereços que estavam disponíveis no navegado
 
 ## Workaround
 
 
-Utilize o parâmetro `?disableAutoCompletion=true` na URL "Get OrderForm". Este parâmetro evita que o OrderForm seja recalculado, os dados do cliente serão devolvidos então
+Use o parâmetro `?disableAutoCompletion=true` no URL "Get OrderForm". Esse parâmetro evita que o orderForm seja recalculado, e os dados do cliente serão retornados em seguida
 
 
 
diff --git a/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md b/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md
new file mode 100644
index 000000000..af76e1540
--- /dev/null
+++ b/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md
@@ -0,0 +1,43 @@
+---
+title: 'O OrderForm não é atualizado depois que o pedido é feito'
+id: 4Xkk9LA95PRXbKxFYy189f
+status: PUBLISHED
+createdAt: 2024-06-27T15:22:19.922Z
+updatedAt: 2024-06-28T11:47:47.958Z
+publishedAt: 2024-06-28T11:47:47.958Z
+firstPublishedAt: 2024-06-27T15:22:20.951Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-orderform-nao-e-atualizado-depois-que-o-pedido-e-feito
+locale: pt
+kiStatus: Backlog
+internalReference: 1056870
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+## Simulação
+
+
+
+- Concluir um pedido em uma conta Faststore
+- Retornar à página inicial
+- Os itens que você acabou de comprar permanecerão em seu carrinh
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md b/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md
index 235334f13..bd3131684 100644
--- a/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md
+++ b/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md
@@ -20,7 +20,7 @@ internalReference:
 
 Atualmente os horários de entrega para uma entrega agendada estão fora de ordem, ou em ordenação decrescente. Para melhor legibilidade, é esperado que estas informações sejam ordenadas de forma crescente.
 
-![image](https://images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md b/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md
index b9ad38b09..f28dce030 100644
--- a/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md
+++ b/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md
@@ -3,8 +3,8 @@ title: 'A ordenação de grupos de especificação da categoria raiz não funcio
 id: 5iuLxVdAuK70VMYGts7CzJ
 status: PUBLISHED
 createdAt: 2022-08-09T00:46:23.102Z
-updatedAt: 2022-11-25T21:43:59.468Z
-publishedAt: 2022-11-25T21:43:59.468Z
+updatedAt: 2024-02-16T20:25:08.305Z
+publishedAt: 2024-02-16T20:25:08.305Z
 firstPublishedAt: 2022-08-09T00:46:23.684Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: a-ordenacao-de-grupos-de-especificacao-da-categoria-raiz-nao-funciona
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 634129
 ---
 
diff --git a/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md b/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
index 0b88e82d9..88fd863c8 100644
--- a/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
+++ b/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
@@ -3,8 +3,8 @@ title: 'Pedidos faturados na VTEX mas que não atualizam a fatura na Netshoes'
 id: 1SrJBQj0iTYh4AdvmJQqIg
 status: PUBLISHED
 createdAt: 2022-05-11T19:45:30.831Z
-updatedAt: 2022-11-25T21:56:22.896Z
-publishedAt: 2022-11-25T21:56:22.896Z
+updatedAt: 2024-02-16T20:25:46.426Z
+publishedAt: 2024-02-16T20:25:46.426Z
 firstPublishedAt: 2022-05-11T19:45:31.187Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: pedidos-faturados-na-vtex-mas-que-nao-atualizam-a-fatura-na-netshoes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 577219
 ---
 
diff --git a/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md b/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
new file mode 100644
index 000000000..b722e6f52
--- /dev/null
+++ b/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
@@ -0,0 +1,51 @@
+---
+title: 'Cálculo de faturamento de ordens usando o valor da fatura de entrada na validação da fatura de saída'
+id: kEjeBKkJMpUDR0JdX6fZv
+status: PUBLISHED
+createdAt: 2023-11-06T11:39:27.169Z
+updatedAt: 2023-11-09T20:47:52.250Z
+publishedAt: 2023-11-09T20:47:52.250Z
+firstPublishedAt: 2023-11-06T11:39:28.035Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: calculo-de-faturamento-de-ordens-usando-o-valor-da-fatura-de-entrada-na-validacao-da-fatura-de-saida
+locale: pt
+kiStatus: Fixed
+internalReference: 930491
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Durante o processo de envio de faturas, é possível que o usuário envie faturas de saída e de entrada, mas se forem feitas duas faturas parciais em um pedido, uma de saída e outra de entrada, o sistema soma esses valores para validar se o pedido pode receber uma nova fatura, impossibilitando que pedidos cujo item foi faturado e depois devolvido não tenham seu valor total faturado.
+
+Isso ocorre porque a API Orders atualmente realiza uma validação de valor para determinar se deve permitir que uma nova fatura de saída seja feita para o pedido, mas o cálculo está considerando a soma de todas as faturas, independentemente do tipo (entrada ou saída), fazendo com que o sistema entenda que não há mais valor a ser faturado.
+
+## Simulação
+
+
+
+1- Criar um pedido com duas unidades do mesmo SKU
+2- Faturar apenas uma dessas unidades
+3- Agora faça uma nova fatura de entrada para a unidade faturada na etapa anterior.
+4- Agora tente faturar a unidade restante do pedido.
+5- Nesse momento, você receberá uma mensagem genérica na interface do usuário indicando que não é possível faturar o item.
+
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md b/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md
new file mode 100644
index 000000000..c34e51525
--- /dev/null
+++ b/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md
@@ -0,0 +1,49 @@
+---
+title: 'Pedidos com asteriscos no endereço e no perfil'
+id: 6AaZ4p042LZwvfeKIqavjw
+status: PUBLISHED
+createdAt: 2023-08-25T17:03:49.755Z
+updatedAt: 2024-06-06T20:16:16.607Z
+publishedAt: 2024-06-06T20:16:16.607Z
+firstPublishedAt: 2023-08-25T17:03:50.594Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: pedidos-com-asteriscos-no-endereco-e-no-perfil
+locale: pt
+kiStatus: Backlog
+internalReference: 360783
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Há pedidos em que `invoiceAddress`, `shippingAddress` ou `clientProfileData` estão sendo enviados como "mascarados" em vez do endereço real. Esse comportamento ocorre quando um usuário conclui a compra com um formulário de pedido que contém dados mascarados que são "stringificados". Como esses campos são de cadeia de caracteres, os dados do pedido são preenchidos com a máscara '***'.
+
+Portanto, o erro está no fato de que nossa API para fazer pedidos permite objetos com caracteres especiais nesses campos.
+
+## Simulação
+
+
+
+1. Adicione alguns produtos ao seu carrinho;
+2. Durante o processo de checkout, insira um endereço de cobrança válido e faça login em sua conta;
+3. Abandonar o carrinho ou sair do site sem concluir a compra;
+4. Usar nossa API para inserir um anexo e colocar um endereço com "***" em alguns campos, como o do bairro;
+5. Fazer um pedido usando esse mesmo carrinho;
+6. Observe que o pedido terá os dados de envio com esses caracteres especiais
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md b/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
index fdbd4242d..6980ebf7f 100644
--- a/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
+++ b/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
@@ -1,18 +1,18 @@
 ---
-title: 'Pedidos com itens em array MarketplaceItems não está abrindo em New UI Admin'
+title: 'Os pedidos com itens na matriz MarketplaceItems não estão abrindo na Nova IU de administração'
 id: 3tj9AKklBHm4tCKYgrfDi5
 status: PUBLISHED
 createdAt: 2022-09-13T03:06:57.141Z
-updatedAt: 2022-11-25T22:01:26.839Z
-publishedAt: 2022-11-25T22:01:26.839Z
+updatedAt: 2023-09-28T15:01:19.205Z
+publishedAt: 2023-09-28T15:01:19.205Z
 firstPublishedAt: 2022-09-13T03:06:57.675Z
 contentType: knownIssue
 productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
-slug: pedidos-com-itens-em-array-marketplaceitems-nao-esta-abrindo-em-new-ui-admin
+slug: os-pedidos-com-itens-na-matriz-marketplaceitems-nao-estao-abrindo-na-nova-iu-de-administracao
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 656821
 ---
 
@@ -23,32 +23,28 @@ internalReference: 656821
 </div>
 
 
-Alguns pedidos têm a matriz "itens de mercado" cheia de mais itens do que a matriz "itens" do pedido da json. Esta configuração é normal e diz respeito, por exemplo, à "lista de presentes de casamento".
-Mas a Nova IU não está preparada para lidar com este tipo de ordem com itens em "itens de mercado" e quebrou a página com uma mensagem de erro:
 
+Alguns pedidos têm a matriz "marketplace Items" preenchida com mais itens do que a matriz "items" do pedido json. Essa configuração é normal e se refere, por exemplo, à "lista de presentes de casamento".
+Mas a nova interface do usuário não está preparada para lidar com esse tipo de pedido com itens em "marketplace Items" e quebrou a página com uma mensagem de erro:
 
 
+"Sorry, something went wrong on our side.
+Tente novamente ou atualize a página.
+Voltar para a lista"
 
 
-"Desculpe, algo deu errado do nosso lado.
-
-Por favor, tente novamente ou atualize a página.
-
-Voltar para a lista".
-
-
+## Simulação
 
 
-## Simulação
 
+Crie um pedido com o catálogo usando a matriz "marketplace Items". Depois disso, você pode tentar ver o pedido na interface de usuário do administrador. A interface do usuário falhará e mostrará uma mensagem de erro
 
-Crie um pedido com catálogo usando a matriz "itens de mercado", depois disso você pode tentar ver o pedido no UI admin. A UI irá quebrar e mostrará uma mensagem de erro.
+## Workaround
 
 
+Use a IU antiga para abrir o pedido.
 
 
-## Workaround
 
 
-Use a velha UI para abrir essa ordem.
 
diff --git a/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md b/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md
index 85a7190c5..2a9a27c2a 100644
--- a/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md
+++ b/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md
@@ -1,18 +1,18 @@
 ---
-title: 'Pedidos sem invocaçãoEndereço criado através da IU nativa'
+title: 'Pedidos sem invoiceAddress criados por meio da UI nativa'
 id: 1XjNZhcTJ5rZJP4w3kJtcW
 status: PUBLISHED
 createdAt: 2022-01-24T20:21:07.893Z
-updatedAt: 2022-11-25T21:52:06.721Z
-publishedAt: 2022-11-25T21:52:06.721Z
+updatedAt: 2023-12-19T21:34:15.743Z
+publishedAt: 2023-12-19T21:34:15.743Z
 firstPublishedAt: 2022-06-27T19:49:05.878Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: pedidos-sem-invocacaoendereco-criado-atraves-da-iu-nativa
+slug: pedidos-sem-invoiceaddress-criados-por-meio-da-ui-nativa
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 306140
 ---
 
@@ -23,34 +23,36 @@ internalReference: 306140
 </div>
 
 
-Em alguns casos ainda é possível criar pedidos sem "invoiceAddress" através da UI de checkout.
-O endereço da fatura deve ser obrigatório na IU de todas as lojas que têm a funcionalidade habilitada.
-
-
+Em alguns casos, ainda é possível criar pedidos sem o `invoiceAddress` por meio da interface de checkout.
+O endereço da fatura deve ser obrigatório na interface do usuário de todas as lojas que tenham a funcionalidade ativada.
 
 ## Simulação
 
 
-Até agora, os passos conhecidos para reproduzir o cenário são:
+Até o momento, as etapas conhecidas para reproduzir o cenário são:
 
 
-1. Acessar a loja sem estar logado/identificado
+1. Acessar a loja sem estar conectado/identificado
 2. Colocar um produto no carrinho
-3. No carrinho, clique em Fechar ordem
-4. Na tela de e-mail coloque um e-mail de um comprador existente - o usuário provavelmente será direcionado para a etapa de pagamento
-5. Clique para editar a etapa de entrega e selecione "retirada".
-6. Não preencher o endereço da nota
-7. Clique para editar "Dados pessoais".
-8. Você será solicitado a fazer o login.
-9. Após o login, na etapa de edição de "Dados Pessoais" o botão aparecerá para ir direto para o pagamento, mesmo se o endereço da fatura não for preenchido.
+3. No carrinho, clique em Fechar pedido
+4. Na tela de e-mail, coloque um e-mail de um comprador existente - o usuário provavelmente será direcionado para a etapa de pagamento
+5. Clique para editar a etapa de entrega e selecione "withdrawal" (retirada)
+6. Não preencha o endereço da nota
+7. Clique para editar "Personal Data" (Dados pessoais)
+8. Você será solicitado a fazer login.
+9. Após o login, na etapa de edição de "Personal Data", aparecerá o botão para ir direto ao pagamento, mesmo que o endereço da fatura não esteja preenchido.
 
-Além do acima mencionado, o comportamento pode ser observado quando o usuário está na etapa de envio e ao recarregar a página, eles são automaticamente levados ao pagamento sem preencher os dados da Fatura.
-Outro cenário que induz o comportamento é a troca entre a lista de endereços previamente registrados e um novo endereço, o que permite ao usuário proceder ao pagamento sem preencher o código postal (de um novo endereço).
+Além dos casos acima, o comportamento pode ser observado quando o usuário está na etapa de envio e, ao recarregar a página, é levado automaticamente para o pagamento sem preencher os dados da fatura.
+Outro cenário que induz o comportamento é alternar entre a lista de endereços registrados anteriormente e um novo endereço, o que permite que o usuário prossiga para o pagamento sem preencher o CEP (de um novo endereço).
 
 
 
 ## Workaround
 
 
-Não há nenhuma solução conhecida para evitar o cenário de raiz.
+Não há nenhuma solução alternativa conhecida para evitar o cenário raiz.
+
+
+
+
 
diff --git a/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md b/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md
index 81df8ac84..3b2bfbbd4 100644
--- a/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md
+++ b/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md
@@ -3,8 +3,8 @@ title: 'Ordenação de imagens ao fazer upload de uma nova versão não funciona
 id: 2Oq65YHU6uIQpQ5g8ZpjTE
 status: PUBLISHED
 createdAt: 2023-01-25T15:08:43.356Z
-updatedAt: 2023-01-25T15:08:43.873Z
-publishedAt: 2023-01-25T15:08:43.873Z
+updatedAt: 2024-02-16T20:26:48.206Z
+publishedAt: 2024-02-16T20:26:48.206Z
 firstPublishedAt: 2023-01-25T15:08:43.873Z
 contentType: knownIssue
 productTeam: CMS
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
 slug: ordenacao-de-imagens-ao-fazer-upload-de-uma-nova-versao-nao-funcionando
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 739814
 ---
 
diff --git a/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
new file mode 100644
index 000000000..8b9bf0a32
--- /dev/null
+++ b/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
@@ -0,0 +1,46 @@
+---
+title: 'O regex Elo desatualizado está nos levando a identificar incorretamente alguns BINs'
+id: 45vx88VCQ0yZynkVxGqSq8
+status: PUBLISHED
+createdAt: 2024-04-10T17:25:57.376Z
+updatedAt: 2024-04-10T17:25:58.309Z
+publishedAt: 2024-04-10T17:25:58.309Z
+firstPublishedAt: 2024-04-10T17:25:58.309Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-regex-elo-desatualizado-esta-nos-levando-a-identificar-incorretamente-alguns-bins
+locale: pt
+kiStatus: Backlog
+internalReference: 1015043
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns BINs não estão sendo identificados corretamente no checkout. A bandeira do cartão é determinada por um regex que pode ficar desatualizado, levando a marcas de cartão não identificadas ou identificadas incorretamente.
+
+## Simulação
+
+
+
+1. Configure duas condições de pagamento, uma para a Elo
+2. Adicione um item aleatório ao seu carrinho na loja e opte por pagá-lo com cartão de crédito
+3. Preencha o número do cartão com o Elo BIN 65057000 e complete-o com números aleatórios
+4. Preencha o restante das informações do cartão com dados falsos
+5. Como o cartão não pôde ser identificado, o caixa solicitará a confirmação do número do cartão e a marca do cartão já pode ser selecionada como outra marca de cartã
+
+## Workaround
+
+
+
+O usuário deve alterar a bandeira do cartão selecionada no checkout clicando na bandeira correta.
+
+
+
+
diff --git a/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md b/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
new file mode 100644
index 000000000..a88ccca2e
--- /dev/null
+++ b/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
@@ -0,0 +1,47 @@
+---
+title: 'Informações indexadas desatualizadas ao realizar duas alterações de produto em uma linha.'
+id: 66aX8MktRogeUD9bbTo0vF
+status: PUBLISHED
+createdAt: 2023-09-26T14:44:57.146Z
+updatedAt: 2023-09-26T14:44:57.895Z
+publishedAt: 2023-09-26T14:44:57.895Z
+firstPublishedAt: 2023-09-26T14:44:57.895Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: informacoes-indexadas-desatualizadas-ao-realizar-duas-alteracoes-de-produto-em-uma-linha
+locale: pt
+kiStatus: No Fix
+internalReference: 907428
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Para lojas que usam o mecanismo de pesquisa legado, se duas alterações nos dados de um produto forem feitas em uma sucessão rápida (ou seja, você inativou um produto e o reativou logo em seguida) e a última alteração retornar as informações do produto para o que era antes, o estado desse item pode ficar preso na primeira alteração, pois a última não é reconhecida corretamente.
+
+Esse problema não ocorre em lojas que usam o aplicativo de pesquisa inteligente.
+
+## Simulação
+
+
+1 - Obtenha um item ativo em sua loja e desative-o
+2 - Logo em seguida (< 5 minutos), reative-o.
+3 - Após alguns minutos, verifique seu produto: ele não será exibido na loja, apesar de estar configurado para isso. (em outras palavras, ele ficou "preso" nesse estado intermediário)
+
+## Workaround
+
+
+1 - Reindexar os referidos produtos após mais de 5 minutos de ocorrência do problema.
+2 - Use o mecanismo de busca inteligente, que não apresenta esse problema de forma alguma.
+3 - Evite fazer mais de duas alterações consecutivas em um produto, pois a última alteração apenas reverte a primeira.
+
+
+
+
+
diff --git a/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
index 8856b4b0e..09d6d0968 100644
--- a/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
@@ -1,16 +1,16 @@
 ---
-title: 'A desactualização do Mastercard Debit regex está nos levando a identificar erroneamente alguns BINs'
+title: 'O regex desatualizado do Mastercard Debit está nos levando a identificar incorretamente alguns BINs'
 id: 5gx4dSY2P5gGE0JI661hGL
 status: PUBLISHED
 createdAt: 2022-08-20T00:03:11.640Z
-updatedAt: 2022-11-25T22:04:24.418Z
-publishedAt: 2022-11-25T22:04:24.418Z
+updatedAt: 2024-04-02T19:13:02.839Z
+publishedAt: 2024-04-02T19:13:02.839Z
 firstPublishedAt: 2022-08-20T00:03:12.490Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: a-desactualizacao-do-mastercard-debit-regex-esta-nos-levando-a-identificar-erroneamente-alguns-bins
+slug: o-regex-desatualizado-do-mastercard-debit-esta-nos-levando-a-identificar-incorretamente-alguns-bins
 locale: pt
 kiStatus: Backlog
 internalReference: 642136
@@ -23,24 +23,25 @@ internalReference: 642136
 </div>
 
 
-Alguns BINs não estão sendo identificados corretamente no checkout. A marca do cartão é determinada por um regex que pode eventualmente estar desatualizado, fazendo com que a marca do cartão não seja identificada ou seja mal identificada.
-
-
+Alguns BINs não estão sendo identificados corretamente no checkout. A bandeira do cartão é determinada por um regex que pode eventualmente estar desatualizado, fazendo com que a bandeira do cartão não seja identificada ou seja identificada incorretamente.
 
 ## Simulação
 
 
 
-1. Configurar duas Condições de Pagamento uma para débito com cartão Mastercard
-2. Adicione um item aleatório ao seu carrinho na loja e opte por pagá-lo com cartão de débito
-3. Preencha o número do cartão com o Mastercard Debit BIN 551898 e complete-o com números aleatórios.
-4. Preencher as demais informações do cartão com dados falsos
-5. Como o cartão não pôde ser identificado, o checkout pedirá para confirmar o número do cartão e a marca do cartão já pode ser selecionada como outra marca de cartão.
+1. Configure duas condições de pagamento, uma para débito Mastercard
+2. Adicione um item aleatório ao seu carrinho na loja e escolha pagá-lo com cartão de débito
+3. Preencha o número do cartão com o Mastercard Debit BIN 551898 e complete-o com números aleatórios
+4. Preencha as demais informações do cartão com dados falsos
+5. Como o cartão não pôde ser identificado, o caixa solicitará a confirmação do número do cartão e a marca do cartão já pode ser selecionada como outra marca de cartão
 
 
 
 ## Workaround
 
 
-Não há solução.
+Não há solução alternativa.
+
+
+
 
diff --git a/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md b/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md
new file mode 100644
index 000000000..a553d443b
--- /dev/null
+++ b/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md
@@ -0,0 +1,48 @@
+---
+title: 'URL desatualizado na interface de usuário de atualização de vinculação'
+id: 7bgh2LIJTFovgoz0TaBr5B
+status: PUBLISHED
+createdAt: 2023-08-30T20:04:23.301Z
+updatedAt: 2023-08-30T20:04:23.905Z
+publishedAt: 2023-08-30T20:04:23.905Z
+firstPublishedAt: 2023-08-30T20:04:23.905Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: url-desatualizado-na-interface-de-usuario-de-atualizacao-de-vinculacao
+locale: pt
+kiStatus: Backlog
+internalReference: 890791
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o comerciante está atualizando uma oferta, a interface do usuário é a seguinte:
+ ![](https://vtexhelp.zendesk.com/attachments/token/UfffIyuM7K7isQMiPnAqRvSiW/?name=image.png)
+
+Ao tentar acessar o link do gerenciador de licenças, ele é redirecionado para uma página SWW.
+
+## Simulação
+
+
+
+1. Vá para a configuração do CMS (.../admin/a)
+2. Selecione um site e clique em atualizar vinculação
+3. Clique no link License Manager
+4. Verifique se aparece um erro SWW
+
+## Workaround
+
+
+Use a url diretamente: (.../admin/account/stores/)
+
+
+
+
+
diff --git a/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md b/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md
new file mode 100644
index 000000000..c3b8400f1
--- /dev/null
+++ b/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md
@@ -0,0 +1,42 @@
+---
+title: 'O pageView é acionado duas vezes ao acessar o My Account'
+id: 2jV0cIVxNUhb170tBgBQo6
+status: PUBLISHED
+createdAt: 2023-07-03T16:33:09.076Z
+updatedAt: 2023-07-03T16:33:09.652Z
+publishedAt: 2023-07-03T16:33:09.652Z
+firstPublishedAt: 2023-07-03T16:33:09.652Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-pageview-e-acionado-duas-vezes-ao-acessar-o-my-account
+locale: pt
+kiStatus: Backlog
+internalReference: 854480
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao acessar o My Account, o evento pageView é acionado duas vezes, duplicando os dados no Analytics.
+
+## Simulação
+
+
+
+- Configure o aplicativo Google Tag Manager,
+- Acesse My Account (Minha conta);
+- Abra as Ferramentas do desenvolvedor do navegador e digite "dataLayer" no Console; haverá dois eventos pageView
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md b/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
new file mode 100644
index 000000000..a9459b9da
--- /dev/null
+++ b/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
@@ -0,0 +1,59 @@
+---
+title: 'Os acionadores de exibição de página no G4A estão sendo duplicados em páginas de pesquisa personalizadas'
+id: 4hIwZ2v9bbyyZXrxoDglyx
+status: PUBLISHED
+createdAt: 2023-11-08T13:35:27.802Z
+updatedAt: 2024-02-19T18:43:16.271Z
+publishedAt: 2024-02-19T18:43:16.271Z
+firstPublishedAt: 2023-11-08T13:35:28.390Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: os-acionadores-de-exibicao-de-pagina-no-g4a-estao-sendo-duplicados-em-paginas-de-pesquisa-personalizadas
+locale: pt
+kiStatus: Backlog
+internalReference: 888042
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O evento pageView está sendo exibido duplicado no dataLayer quando em páginas de pesquisa personalizadas
+
+## Simulação
+
+
+
+- Vá para qualquer página de pesquisa personalizada
+- Abra o console do seu navegador
+- Digite dataLayer e verifique o evento pageView
+
+O comportamento esperado é o evento duplicado
+
+
+
+## Workaround
+
+
+N/A
+
+
+## **Notas internas**
+
+Também encontrei algo curioso na página do departamento com pageView e page_view
+
+https://storetheme.vtex.com/apparel---accessories/
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/dXFuDY5Q9XhZ7hgIvA8m8ugJ3/?name=image.png)
+
+Porém, esse problema específico pode ser replicado em
+
+https://www.dzarm.com.br/outlet
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/EVakZYSBKtcrCQoNXBe92uAzQ/?name=image.png)
+
diff --git a/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md b/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md
index 02aa212cd..cf22fb3f9 100644
--- a/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md
+++ b/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md
@@ -3,8 +3,8 @@ title: 'Links de paginação nos resultados da pesquisa que não funcionam nas p
 id: 1w6h5MwZthKMM8rvqXZtQi
 status: PUBLISHED
 createdAt: 2022-11-02T14:01:35.650Z
-updatedAt: 2022-11-25T21:41:59.731Z
-publishedAt: 2022-11-25T21:41:59.731Z
+updatedAt: 2024-02-16T20:26:50.585Z
+publishedAt: 2024-02-16T20:26:50.585Z
 firstPublishedAt: 2022-11-02T14:01:36.502Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: links-de-paginacao-nos-resultados-da-pesquisa-que-nao-funcionam-nas-paginas-da-giftlist
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 481330
 ---
 
diff --git a/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md b/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
new file mode 100644
index 000000000..57cbedabb
--- /dev/null
+++ b/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
@@ -0,0 +1,50 @@
+---
+title: 'A paginação na página de pesquisa não é redefinida ao alterar o contexto da pesquisa'
+id: 2lNL95NDZvO8NqxhJDrA6G
+status: PUBLISHED
+createdAt: 2023-07-06T19:54:29.289Z
+updatedAt: 2023-07-06T19:58:59.059Z
+publishedAt: 2023-07-06T19:58:59.059Z
+firstPublishedAt: 2023-07-06T19:54:29.968Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: a-paginacao-na-pagina-de-pesquisa-nao-e-redefinida-ao-alterar-o-contexto-da-pesquisa
+locale: pt
+kiStatus: Scheduled
+internalReference: 857392
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao navegar em uma determinada página de um PLP, buscar para mostrar mais resultados e alterar o contexto para navegar em um departamento diferente, o parâmetro de paginação será mantido e o resultado da pesquisa começará na nova categoria na mesma página em que estávamos anteriormente
+
+## Simulação
+
+
+
+Seguindo as etapas:
+
+
+- Acesse: https://starter.vtex.app/computer---software
+- Clique em Load more products (o parâmetro da página em seu URL será alterado)
+- Clique em um departamento diferente (por exemplo, Tecnologia)
+- Verifique se a página de tecnologia começará com a paginação que você estava fazendo anteriormente
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md b/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
index 1738adae5..05bcd9279 100644
--- a/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
+++ b/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
@@ -1,16 +1,16 @@
 ---
-title: 'Colar o código postal no carrinho de pré-visualização de remessa às vezes retorna resultado API nulo'
+title: 'Colar o código postal no carrinho de visualização de remessa às vezes retorna um resultado de API nulo'
 id: 5Lq32htqC7M9xiqajfn7y7
 status: PUBLISHED
 createdAt: 2022-06-01T15:30:08.776Z
-updatedAt: 2022-11-25T21:53:05.306Z
-publishedAt: 2022-11-25T21:53:05.306Z
+updatedAt: 2024-05-21T13:03:32.812Z
+publishedAt: 2024-05-21T13:03:32.812Z
 firstPublishedAt: 2022-06-01T15:30:09.241Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: colar-o-codigo-postal-no-carrinho-de-previsualizacao-de-remessa-as-vezes-retorna-resultado-api-nulo
+slug: colar-o-codigo-postal-no-carrinho-de-visualizacao-de-remessa-as-vezes-retorna-um-resultado-de-api-nulo
 locale: pt
 kiStatus: Backlog
 internalReference: 481878
@@ -23,16 +23,23 @@ internalReference: 481878
 </div>
 
 
-Depois de inserir o código postal uma vez na visualização do envio e escolher colar o código postal novamente, às vezes ocorre de fazer um pedido nulo para o código postal API.
-
-
+Depois de inserir o código postal uma vez na visualização do envio e optar por colá-lo novamente, às vezes ocorre de fazer uma solicitação nula para a API do código postal.
 
+A solicitação é `/api/checkout/pub/postal-code/null/postalcodenumber` e retorna um erro 500.
 
 ## Simulação
 
 
 
+- Vá até o carrinho e adicione um código postal;
+- Clique para alterá-lo e cole outro código postal (ou até mesmo o mesmo);
+- Vá para a etapa de envio, e o endereço pode estar incompleto
+
 ## Workaround
 
 
+O usuário precisará clicar no botão "Calculate" (Calcular) ou pressionar a tecla Enter, em alguns casos digitando o código postal sem inseri-lo.
+
+
+
 
diff --git a/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md b/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
new file mode 100644
index 000000000..bdb79face
--- /dev/null
+++ b/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
@@ -0,0 +1,44 @@
+---
+title: 'As condições de pagamento definidas para processar transações em parcelas diferentes de 1x estão processando transações como pré-pagas integralmente'
+id: 2z9cDiCAovzKVFZO7RSqOD
+status: PUBLISHED
+createdAt: 2024-05-09T18:47:33.319Z
+updatedAt: 2024-05-09T18:47:34.221Z
+publishedAt: 2024-05-09T18:47:34.221Z
+firstPublishedAt: 2024-05-09T18:47:34.221Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: as-condicoes-de-pagamento-definidas-para-processar-transacoes-em-parcelas-diferentes-de-1x-estao-processando-transacoes-como-prepagas-integralmente
+locale: pt
+kiStatus: Backlog
+internalReference: 1030652
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As condições de pagamento configuradas para processar transações em um número de parcelas diferente de 1x estão sendo capazes de processar pagamentos em 1x. O problema ocorre apenas para pagamentos em que o usuário optou por pagar como pré-pago integralmente.
+
+## Simulação
+
+
+
+1. Configure 3 condições de pagamento para cartões de crédito de qualquer marca: Condição de Pagamento A - com parcelamento em 1x, Condição de Pagamento B - com parcelamento em 2x, e Condição de Pagamento C - com parcelamento em 3x.
+2. Vá para a página Checkout adicionando qualquer item ao carrinho e prossiga para a tela de pagamento. Escolha pagar com um cartão de crédito em 1x e conclua a compra.
+3. Vá até o admin e abra a transação recém-criada, clique no botão "+ Information" e observe que o campo `AvailableRules` conterá uma lista com todos os IDs das Condições de Pagamento, Condição de Pagamento A, Condição de Pagamento B e Condição de Pagamento C, como sendo capazes de processar a transação em questão
+
+## Workaround
+
+
+É possível definir a condição de pagamento 1x como padrão, de modo que, quando houver um empate entre todas as condições de pagamento, o gateway priorizará a regra padrão.
+
+
+
+
+
diff --git a/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md b/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
index d129a57fe..71d25252c 100644
--- a/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
+++ b/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
@@ -3,8 +3,8 @@ title: 'O método de pagamento do Marketplace combina com o SWL ao utilizar tipo
 id: 4AHyl5z7ySagx6Myx0KqM7
 status: PUBLISHED
 createdAt: 2022-03-15T22:06:35.540Z
-updatedAt: 2022-11-25T22:12:10.257Z
-publishedAt: 2022-11-25T22:12:10.257Z
+updatedAt: 2024-02-16T20:29:19.824Z
+publishedAt: 2024-02-16T20:29:19.824Z
 firstPublishedAt: 2022-03-15T22:06:36.030Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: o-metodo-de-pagamento-do-marketplace-combina-com-o-swl-ao-utilizar-tipos-identicosids
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 402140
 ---
 
diff --git a/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md b/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
index 0420eb11a..02ac9e3db 100644
--- a/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
+++ b/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'Os métodos de pagamento exibidos no checkout diferem das condições de
 id: 1cpVNspn5G6je4EZKzvCF9
 status: PUBLISHED
 createdAt: 2022-09-27T16:32:55.806Z
-updatedAt: 2023-04-10T15:14:18.718Z
-publishedAt: 2023-04-10T15:14:18.718Z
+updatedAt: 2024-06-07T21:23:28.431Z
+publishedAt: 2024-06-07T21:23:28.431Z
 firstPublishedAt: 2023-04-10T15:11:01.389Z
 contentType: knownIssue
 productTeam: Payments
@@ -23,15 +23,6 @@ internalReference: 666469
 </div>
 
 
-Este KI se manifesta de duas maneiras no checkout:
-
-1. Métodos de pagamento **não*** aparecem na página de checkout, mesmo quando a condição de pagamento associada estiver ativa por mais de 10 minutos.
-2. Métodos de pagamento **supremain** na página de checkout, mesmo quando a condição de pagamento associada estiver desativada por mais de 10 min.
-
-Esta é uma questão intermitente e não há evidências de como reproduzir este comportamento. Há uma maior incidência nos métodos de pagamento personalizados.
-
-
-##
 
 ## Simulação
 
@@ -39,12 +30,11 @@ Esta é uma questão intermitente e não há evidências de como reproduzir este
 N/A
 
 
-##
 
 ## Workaround
 
 
 
-1. Resgatando a regra.
-2. Reindexando todos os sistemas de pagamento no checkout via API.
+1. Salvando novamente a regra.
+2. Reindexar todos os sistemas de pagamento no checkout via API.
 
diff --git a/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md b/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
new file mode 100644
index 000000000..0115f00b3
--- /dev/null
+++ b/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
@@ -0,0 +1,62 @@
+---
+title: 'Alterações nas condições de pagamento não aplicadas nas configurações de checkout B2B'
+id: 12PfZx6O0MIUSIFdpQdUdI
+status: PUBLISHED
+createdAt: 2024-04-18T19:07:22.743Z
+updatedAt: 2024-07-25T21:47:29.442Z
+publishedAt: 2024-07-25T21:47:29.442Z
+firstPublishedAt: 2024-04-18T19:07:23.644Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: alteracoes-nas-condicoes-de-pagamento-nao-aplicadas-nas-configuracoes-de-checkout-b2b
+locale: pt
+kiStatus: Fixed
+internalReference: 1019548
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A atualização das condições de pagamento na UI de detalhes da organização para uma organização não se aplica às configurações de checkout B2B.
+
+Esse comportamento ocorre porque a atualização ocorre apenas para a organização, mas as configurações de checkout B2B usam informações do centro de custo, que não são atualizadas pela interface do usuário de detalhes da organização.
+
+## Simulação
+
+
+
+- Crie uma organização;
+- Na interface do usuário de detalhes da organização, atualize as condições de pagamento;
+- Acesse o site, monte um carrinho e acesse o checkout; os Termos de pagamento permanecerão os mesmos
+
+## Workaround
+
+
+
+- Acesse o GraphQL IDE e selecione vtex.b2b-organizations-graphql;
+- Use a consulta abaixo para obter os detalhes do centro de custo:
+
+    { getCostCenterById (id: "insira aqui o id do centro de custo"){ name addresses{ addressId addressType addressQuery postalCode country receiverName city state street number complement neighborhood geoCoordinates reference } phoneNumber businessDocument customFields{ name type value dropdownValues{ value label } useOnRegistration } stateRegistration paymentTerms{ id name } }}
+
+- Use a consulta abaixo para obter as condições de pagamento da organização:
+
+    { getOrganizationById(id: "insira aqui o id da organização"){ paymentTerms{ id name } }}
+
+
+
+- Envie uma mutação para atualizar o centro de custo, adicionando as condições de pagamento da organização à resposta do centro de custo:
+
+    mutation updateCostCenter($id: ID!, $input: CostCenterInput!) { updateCostCenter( id: $id input: $input ){ id status }}{ "id": "", "input": { "name": "", "addresses": [{ "addressId": "", "addressType": "", "addressQuery": "", "postalCode": "", "country": "", "receiverName": "", "city": "", "state": "", "street": "", "number": "", "complement": null, "neighborhood": "", "geoCoordinates": [], "reference": null } ], "phoneNumber": "", "businessDocument": "", "customFields": [], "stateRegistration": "", "paymentTerms": [{"id": "", "name": "" }, {"id": "", "name": "" }] }}
+
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
new file mode 100644
index 000000000..feffea2e8
--- /dev/null
+++ b/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -0,0 +1,46 @@
+---
+title: 'As condições de pagamento configuradas nas configurações B2B não são atribuídas após a aprovação das organizações'
+id: 7pUMnYPWPHlhPzlWwTtWsL
+status: PUBLISHED
+createdAt: 2024-02-26T22:29:03.516Z
+updatedAt: 2024-02-26T22:29:04.387Z
+publishedAt: 2024-02-26T22:29:04.387Z
+firstPublishedAt: 2024-02-26T22:29:04.387Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: as-condicoes-de-pagamento-configuradas-nas-configuracoes-b2b-nao-sao-atribuidas-apos-a-aprovacao-das-organizacoes
+locale: pt
+kiStatus: Backlog
+internalReference: 989507
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As condições de pagamento configuradas nas configurações de organizações B2B não são salvas nos detalhes da organização.
+
+## Simulação
+
+
+
+- Configure as condições de pagamento padrão nas configurações de organizações B2B;
+- Criar uma solicitação de organização;
+- Aprovar a solicitação da organização;
+- Verifique os detalhes da organização; ela não terá nenhuma condição de pagamento atribuída
+
+## Workaround
+
+
+
+- Atribua as condições de pagamento à organização por meio do administrador;
+- Crie um acionador para o esquema da entidade da organização.
+
+
+
+
diff --git a/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md b/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
new file mode 100644
index 000000000..03c89975f
--- /dev/null
+++ b/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
@@ -0,0 +1,46 @@
+---
+title: 'Os PaymentSystems não são retornados no orderForm quando o preço do carrinho vem exclusivamente do manualPrice'
+id: 3KPNFtPgEwshbv6WiGrqOF
+status: PUBLISHED
+createdAt: 2024-04-30T20:06:52.774Z
+updatedAt: 2024-04-30T20:06:53.756Z
+publishedAt: 2024-04-30T20:06:53.756Z
+firstPublishedAt: 2024-04-30T20:06:53.756Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-paymentsystems-nao-sao-retornados-no-orderform-quando-o-preco-do-carrinho-vem-exclusivamente-do-manualprice
+locale: pt
+kiStatus: Backlog
+internalReference: 1025321
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o valor total de um carrinho provém exclusivamente de um preço manual, os itens `preço` e `preço de entrega` são `0`, nenhum sistema de pagamento além do Gift Card (se ativo) é oferecido.
+
+## Simulação
+
+
+
+- Adicionar um item com preço `0` e selecionar uma opção de entrega com preço `0`
+- Adicionar um valor `manualPrice` ao item
+- Prossiga para a etapa de pagamento no checkout e nenhum método de pagamento é retornado como disponível
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa conhecida além de adicionar algum valor ao preço do item.
+
+
+
+
+
diff --git a/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md b/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
index 5ee57d591..bdcde572e 100644
--- a/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
+++ b/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
@@ -3,8 +3,8 @@ title: 'O pagamento e a divisão da transação não funcionam na mesma ordem pa
 id: 3rFyqzEnSwx2czwdlgDovU
 status: PUBLISHED
 createdAt: 2023-03-23T19:03:22.498Z
-updatedAt: 2023-03-27T12:27:57.714Z
-publishedAt: 2023-03-27T12:27:57.714Z
+updatedAt: 2024-02-16T20:25:26.525Z
+publishedAt: 2024-02-16T20:25:26.525Z
 firstPublishedAt: 2023-03-23T19:03:23.526Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-pagamento-e-a-divisao-da-transacao-nao-funcionam-na-mesma-ordem-para-o-inventario-multilevel-omnichannel
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 777201
 ---
 
diff --git a/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md b/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md
index 93f0ca773..2aa863264 100644
--- a/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md
+++ b/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md
@@ -3,8 +3,8 @@ title: 'O PayPalPlus não respeita o valor mínimo da parcela'
 id: 1IGzNPtXaaUsPkaq0qRgfK
 status: PUBLISHED
 createdAt: 2022-03-26T23:00:59.044Z
-updatedAt: 2022-11-25T22:06:43.067Z
-publishedAt: 2022-11-25T22:06:43.067Z
+updatedAt: 2024-02-16T20:25:30.693Z
+publishedAt: 2024-02-16T20:25:30.693Z
 firstPublishedAt: 2022-03-26T23:00:59.445Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: o-paypalplus-nao-respeita-o-valor-minimo-da-parcela
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 370271
 ---
 
diff --git a/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md b/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md
index 7e66121f2..060c8e125 100644
--- a/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md
+++ b/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md
@@ -3,8 +3,8 @@ title: 'Ponto de retirada desconsiderado por questão de prioridade'
 id: 3bbsm8TELPBa0DpFtnlAGz
 status: PUBLISHED
 createdAt: 2021-09-29T14:38:08.930Z
-updatedAt: 2022-12-22T20:41:01.800Z
-publishedAt: 2022-12-22T20:41:01.800Z
+updatedAt: 2024-06-14T16:56:59.120Z
+publishedAt: 2024-06-14T16:56:59.120Z
 firstPublishedAt: 2021-09-29T14:49:34.443Z
 contentType: knownIssue
 productTeam: Post-purchase
@@ -13,7 +13,7 @@ tag: Logistics
 slug: ponto-de-retirada-desconsiderado-por-questao-de-prioridade
 locale: pt
 kiStatus: Backlog
-internalReference: 
+internalReference: 380545
 ---
 
 ## Sumário
diff --git a/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md b/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
new file mode 100644
index 000000000..2cf3bb865
--- /dev/null
+++ b/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
@@ -0,0 +1,46 @@
+---
+title: 'O modal de ponto de coleta não utiliza geoCoordinates sem uma chave do Google Maps'
+id: 5aPNjLlsVVeyGe0Vywt0H9
+status: PUBLISHED
+createdAt: 2024-05-29T20:31:46.863Z
+updatedAt: 2024-07-03T15:56:30.595Z
+publishedAt: 2024-07-03T15:56:30.595Z
+firstPublishedAt: 2024-05-29T20:31:47.737Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-modal-de-ponto-de-coleta-nao-utiliza-geocoordinates-sem-uma-chave-do-google-maps
+locale: pt
+kiStatus: Backlog
+internalReference: 1041462
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A inserção de um código postal no modal do seletor de ponto de coleta aciona uma solicitação para obter os SLAs disponíveis para esse local. Se a conta não tiver uma chave de API do Google Maps definida em suas configurações de Checkout, essa solicitação não incluirá informações de geoCoordinates. Isso pode fazer com que os pontos de coleta dentro de um intervalo válido não sejam exibidos, como aqueles cujas tabelas de frete são baseadas em polígonos.
+
+## Simulação
+
+
+
+1. Use uma loja que não tenha uma chave de API do Google Maps definida.
+2. Configure um ponto de coleta e vincule-o a uma transportadora cuja tabela de frete seja baseada em polígonos.
+3. Adicione um produto ao seu carrinho.
+4. Na visualização da remessa, selecione a opção de coleta e insira um código postal que tenha disponibilidade para o ponto de coleta que você criou.
+5. Inspecione a solicitação shippingData gerada por essa ação. Ela não conterá geoCoordinates.
+
+## Workaround
+
+
+Defina uma chave de API do Google Maps nas configurações de checkout da loja.
+
+
+
+
+
diff --git a/docs/known-issues/pt/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md b/docs/known-issues/pt/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
index e17a41377..f649c5334 100644
--- a/docs/known-issues/pt/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
+++ b/docs/known-issues/pt/pickup-point-not-visible-for-selection-in-shipping-policy-ui.md
@@ -3,7 +3,7 @@ title: 'Ponto de retirada não fica visível durante associação com política
 id: 84BhCZGoAxxuu1eljw0Uh
 status: DRAFT
 createdAt: 2021-12-28T14:52:46.105Z
-updatedAt: 2022-01-05T21:09:34.658Z
+updatedAt: 2024-02-16T20:27:08.666Z
 publishedAt: 
 firstPublishedAt: 2021-12-28T22:18:57.306Z
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: 
 slug: pickup-point-not-visible-for-selection-in-shipping-policy-ui
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 449813
 ---
 
diff --git a/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md b/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
new file mode 100644
index 000000000..273ebce7e
--- /dev/null
+++ b/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
@@ -0,0 +1,43 @@
+---
+title: 'As tags de ponto de coleta continuam a ser exibidas na política de remessa após a exclusão.'
+id: 2ZcIGeYUud4bQJrAd5MMLb
+status: PUBLISHED
+createdAt: 2024-04-10T18:52:17.457Z
+updatedAt: 2024-04-10T18:52:18.169Z
+publishedAt: 2024-04-10T18:52:18.169Z
+firstPublishedAt: 2024-04-10T18:52:18.169Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: as-tags-de-ponto-de-coleta-continuam-a-ser-exibidas-na-politica-de-remessa-apos-a-exclusao
+locale: pt
+kiStatus: Backlog
+internalReference: 1015158
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As tags registradas no ponto de coleta estão disponíveis em um menu suspenso nas políticas de remessa para vincular o PUP à política de remessa; no entanto, quando qualquer uma dessas tags é excluída no PUP, elas permanecem disponíveis no menu suspenso da política de remessa.
+
+## Simulação
+
+
+Registre uma tag em um PPI, verifique se ela estará disponível na política de remessa para vinculá-la ao PPI e, em seguida, no próprio PPI, exclua a tag e verifique novamente na política de remessa; a tag ainda estará lá.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível
+
+
+
+
+
diff --git a/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md b/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
index 84d2e58c6..93594c717 100644
--- a/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
+++ b/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
@@ -3,8 +3,8 @@ title: 'A lista de pontos de coleta não pode ser rolada depois de procurar ende
 id: 3e0JgNoWSQ0GAw8kurGrIR
 status: PUBLISHED
 createdAt: 2022-08-11T18:35:48.300Z
-updatedAt: 2022-11-25T21:50:52.987Z
-publishedAt: 2022-11-25T21:50:52.987Z
+updatedAt: 2024-07-01T18:48:32.968Z
+publishedAt: 2024-07-01T18:48:32.968Z
 firstPublishedAt: 2022-08-11T18:35:48.775Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-lista-de-pontos-de-coleta-nao-pode-ser-rolada-depois-de-procurar-enderecos-no-modo-de-mapa
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 624646
 ---
 
diff --git a/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md b/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md
new file mode 100644
index 000000000..a5ef49f58
--- /dev/null
+++ b/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md
@@ -0,0 +1,47 @@
+---
+title: 'Pontos de coleta não indexados nos dados mestre'
+id: 6OHjbM6GXBEvgepaod3AyT
+status: PUBLISHED
+createdAt: 2023-12-14T22:29:26.240Z
+updatedAt: 2024-04-30T12:56:14.390Z
+publishedAt: 2024-04-30T12:56:14.390Z
+firstPublishedAt: 2023-12-14T22:29:26.972Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: pontos-de-coleta-nao-indexados-nos-dados-mestre
+locale: pt
+kiStatus: Fixed
+internalReference: 530824
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, o sistema de logística usa o MasterData para armazenar informações de pontos de coleta. Como resultado, podemos ter problemas para indexar essa entidade interna ao usar a rota de pesquisa. Isso pode levar a informações desatualizadas, como:
+
+- Exclusão feita em Logística que não é refletida na lista;
+- Ponto de coleta sendo ativado/inativado em Logística, mas ainda retornando com o status anterior;
+- Alterações de coordenadas que não estão sendo refletidas;
+- E outros.
+
+## Simulação
+
+
+Não há uma maneira confiável de reproduzir esse problema.
+
+
+
+## Workaround
+
+
+A equipe da VTEX deve verificar os dados e, eventualmente, reindexá-los, para que os dados sejam atualizados.
+
+
+
+
diff --git a/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md b/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
new file mode 100644
index 000000000..7ed2a10c1
--- /dev/null
+++ b/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
@@ -0,0 +1,44 @@
+---
+title: 'Os pontos de coleta que começam com o mesmo padrão de ID mostram o produto disponível'
+id: 1iCnOFHyKNTLvY20VS58HP
+status: PUBLISHED
+createdAt: 2024-01-10T16:01:39.766Z
+updatedAt: 2024-01-10T16:01:40.403Z
+publishedAt: 2024-01-10T16:01:40.403Z
+firstPublishedAt: 2024-01-10T16:01:40.403Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-pontos-de-coleta-que-comecam-com-o-mesmo-padrao-de-id-mostram-o-produto-disponivel
+locale: pt
+kiStatus: Backlog
+internalReference: 964036
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando os dois pontos de coleta com IDs começam com o mesmo padrão, a interface do usuário do checkout os valida como a mesma loja, mostrando um produto disponível.
+
+## Simulação
+
+
+
+- Registre dois pontos de retirada: um com ID 8 e outro com ID 835;
+- Associe-os a diferentes estratégias de remessa, em que apenas uma retirada deve ter um produto disponível;
+- Monte um carrinho e selecione a retirada em que o produto não deve estar disponível;
+- O produto aparecerá como disponível
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md b/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
new file mode 100644
index 000000000..c4723f729
--- /dev/null
+++ b/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
@@ -0,0 +1,47 @@
+---
+title: 'O ponto de coleta e a programação de entrega no mesmo carrinho não estão funcionando corretamente'
+id: 6ZCy8a4K6655BANe2yvz6e
+status: PUBLISHED
+createdAt: 2023-06-16T21:14:13.927Z
+updatedAt: 2023-06-16T21:14:14.834Z
+publishedAt: 2023-06-16T21:14:14.834Z
+firstPublishedAt: 2023-06-16T21:14:14.834Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-ponto-de-coleta-e-a-programacao-de-entrega-no-mesmo-carrinho-nao-estao-funcionando-corretamente
+locale: pt
+kiStatus: Backlog
+internalReference: 482256
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A interface do usuário não funciona corretamente em um carrinho com mais de um item com uma divisão de entrega em que um dos itens está disponível para retirada e os outros apenas para entrega programada.
+
+A data para escolher os itens de retirada é definida sem problemas. Mas as datas para a entrega programada não se comportam como esperado.
+
+## Simulação
+
+
+
+- Monte um carrinho com pelo menos dois itens em que um dos itens esteja disponível para retirada e os outros somente para entrega programada;
+- Na etapa de envio, selecione Retirar na loja e selecione uma janela de entrega;
+- Tente selecionar uma janela de entrega para a entrega programada.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md b/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
new file mode 100644
index 000000000..8e66a4fe2
--- /dev/null
+++ b/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
@@ -0,0 +1,55 @@
+---
+title: 'A colocação do código postal na visualização de frete do carrinho está duplicando as opções de endereço para clientes recorrentes'
+id: 4J8TMlhGmMtnHKXGES4qie
+status: PUBLISHED
+createdAt: 2023-12-20T21:36:52.612Z
+updatedAt: 2023-12-20T21:36:53.238Z
+publishedAt: 2023-12-20T21:36:53.238Z
+firstPublishedAt: 2023-12-20T21:36:53.238Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-colocacao-do-codigo-postal-na-visualizacao-de-frete-do-carrinho-esta-duplicando-as-opcoes-de-endereco-para-clientes-recorrentes
+locale: pt
+kiStatus: Backlog
+internalReference: 956338
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Temos alguns problemas quando se trata de colocar códigos postais no módulo **Shipping Preview** no carrinho, alguns deles estão descritos nestes KIs:
+
+
+- Ref. 1: [KI] Colar o código postal no carrinho de visualização de envio às vezes retorna um resultado de API nulo
+- Ref. 2: [KI] O campo de entrada do código postal da visualização de remessa não está oculto
+
+Nesse caso, o que acontece é que, para os clientes que já têm endereços registrados em seu perfil (compradores recorrentes), ao colocar um código postal na visualização de envio já usado em uma compra anterior, na API está sendo colocada uma opção adicional de endereço de entrega (`shippingData.availableAddresses`), ao avançar nas etapas do Checkout e chegar à seleção do endereço (`/checkout/#/shipping`), verifica-se que, em vez de selecionar o endereço correspondente ao referido código postal, abre uma nova opção de seleção incompleta e, em alguns casos, oculta, obrigando o cliente a selecionar uma na lista ou complementar a "nova" para passar para a próxima etapa.
+
+## Simulação
+
+
+
+1. Use um usuário que já tenha feito algumas compras e cujo perfil tenha algum endereço para entrega.
+2. Adicione alguns itens ao carrinho e, em seguida, vá para o checkout.
+3. No carrinho, use o Shipping Preview para colocar um código postal de um de seu perfil.
+  1. Tente revisar o `orderForm` e procure por `shippingData.availableAddresses`
+  2. O endereço em seu perfil será listado com um detalhe importante, o endereço já tem o número da rua (`shippingData.availableAddresses.[].number`)
+  3. A nova opção na matriz que gera o problema não tem o `número`, o que a converte em uma opção de endereço incompleto.
+4. Tente ir para a etapa de envio do checkout (`/checkout/#/shipping`) e você verá que não é possível passar para a etapa de pagamento se você não completar o endereço selecionado ou selecionar outra opção
+
+## Workaround
+
+
+Na etapa de envio do checkout, tente selecionar o endereço listado desejado (force a seleção de um dos endereços anteriores do cliente).
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md b/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
index 1d5875223..44656fe5f 100644
--- a/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
+++ b/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
@@ -1,16 +1,16 @@
 ---
-title: 'O portal não exclui cookies quando o cliente faz o logout no checkout'
+title: 'O portal não exclui cookies quando o cliente faz logout no checkout'
 id: 5GPBW2TBOUzJkw5u47KC5z
 status: PUBLISHED
 createdAt: 2022-03-16T16:13:44.658Z
-updatedAt: 2022-11-25T22:10:31.240Z
-publishedAt: 2022-11-25T22:10:31.240Z
+updatedAt: 2024-04-26T18:05:09.421Z
+publishedAt: 2024-04-26T18:05:09.421Z
 firstPublishedAt: 2022-03-16T16:13:45.038Z
 contentType: knownIssue
 productTeam: Portal
 author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
-slug: o-portal-nao-exclui-cookies-quando-o-cliente-faz-o-logout-no-checkout
+slug: o-portal-nao-exclui-cookies-quando-o-cliente-faz-logout-no-checkout
 locale: pt
 kiStatus: Backlog
 internalReference: 417322
@@ -23,29 +23,29 @@ internalReference: 417322
 </div>
 
 
-Na caixa de uma loja, temos a opção de sair da loja.
+No checkout de uma loja, temos uma opção para fazer logout.
 
-Infelizmente, o pedido feito ao aplicativo do portal, não está excluindo os cookies do usuário, permanecendo no OrderForm com o e-mail de identificação deste cliente, de modo que o cliente não pode sair usando esta opção
+Infelizmente, a solicitação feita ao aplicativo do portal não está excluindo os cookies do usuário, que permanecem no OrderForm com o ID de e-mail desse cliente, de modo que o cliente não pode fazer logout usando essa opção
 
+## Simulação
 
 
-## Simulação
+1. Vá para `.myvtex.com` e faça login em My Account usando e-mail e código;
 
+2. Depois de fazer login, crie um carrinho e vá para o checkout;
 
-1. Ir para `.myvtex.com' e fazer login a partir de Minha Conta utilizando e-mail e código;
+3. Conclua a etapa Profile (Perfil) e vá para Shipping (Remessa) e, em seguida, tente fazer logout no link "It's not me, end session" (Não sou eu, encerre a sessão).
 
-2. Uma vez conectado, faça um carrinho e vá para o check-out;
+O checkout executa a solicitação normalmente, fazendo a solicitação junto com o `orderFormId`
 
-3. Complete o passo Perfil e vá para Shipping, depois tente sair do link "It's not me, end session".
+No entanto, o Portal Application não está excluindo o cookie desse usuário e, portanto, retornando o mesmo usuário, com isso o e-mail é mantido no orderForm e, consequentemente, ele não é desconectado
 
-O Checkout executa o pedido normalmente, fazendo o pedido junto com o "OrderFormId".
+## Workaround
 
-Entretanto, o Portal Application não está apagando o cookie deste usuário e assim devolvendo o mesmo usuário, com isso o e-mail é mantido no OrderForm e conseqüentemente, não é desconectado.
 
+Use um JS personalizado para forçar o logout
 
 
-## Workaround
 
 
-Sair usando a página inicial.
 
diff --git a/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md b/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
index 652a32377..cd9af05b5 100644
--- a/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
+++ b/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
@@ -3,8 +3,8 @@ title: "O Portal mantém os UTM's após o log out quando se utiliza o Callcenter
 id: 4dogeU7iMoTXBWwv5DyR8u
 status: PUBLISHED
 createdAt: 2022-03-18T19:04:54.519Z
-updatedAt: 2022-11-25T22:10:46.942Z
-publishedAt: 2022-11-25T22:10:46.942Z
+updatedAt: 2024-02-16T20:27:34.500Z
+publishedAt: 2024-02-16T20:27:34.500Z
 firstPublishedAt: 2022-03-18T19:04:55.239Z
 contentType: knownIssue
 productTeam: Portal
diff --git a/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md b/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
index 2002830d5..ea848355b 100644
--- a/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
+++ b/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
@@ -3,8 +3,8 @@ title: 'O portal recarrega todos os resultados da busca ao acessar a URL com par
 id: 18Y8yYKByGTzMxyYhk1pdl
 status: PUBLISHED
 createdAt: 2022-01-23T02:35:50.182Z
-updatedAt: 2022-11-25T22:11:17.525Z
-publishedAt: 2022-11-25T22:11:17.525Z
+updatedAt: 2024-02-16T20:29:31.154Z
+publishedAt: 2024-02-16T20:29:31.154Z
 firstPublishedAt: 2022-03-16T16:22:55.043Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: o-portal-recarrega-todos-os-resultados-da-busca-ao-acessar-a-url-com-parametro-de-paginacao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 342378
 ---
 
diff --git a/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md b/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
new file mode 100644
index 000000000..f742e3120
--- /dev/null
+++ b/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
@@ -0,0 +1,43 @@
+---
+title: 'Possíveis erros na notificação de ordens de alteração na interface do usuário, na API e no gateway.'
+id: 1UeG6MyFYIUVCnH8kPwNIJ
+status: PUBLISHED
+createdAt: 2023-12-19T19:37:47.313Z
+updatedAt: 2023-12-19T19:37:47.950Z
+publishedAt: 2023-12-19T19:37:47.950Z
+firstPublishedAt: 2023-12-19T19:37:47.950Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: possiveis-erros-na-notificacao-de-ordens-de-alteracao-na-interface-do-usuario-na-api-e-no-gateway
+locale: pt
+kiStatus: Backlog
+internalReference: 955489
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns problemas foram identificados na arquitetura Change Orders V1, onde alguns casos não eram notificados na interação do pedido na UI, não eram notificados na API Get Orders, porém, havia um desconto ou aumento no valor. Também vimos cenários em que a notificação ocorre na UI e na API, mas o desconto ou aumento não é feito no gateway.
+
+## Simulação
+
+
+Não é possível realizar uma simulação, pois os cenários são esporádicos e geralmente ocorrem devido a um erro de tempo limite, para o qual já aumentamos o cronômetro.
+
+
+
+## Workaround
+
+
+Inicialmente não temos uma solução alternativa, no entanto, vale mencionar que alguns cenários poderemos ajustar manualmente, como, por exemplo, se o registro de pedidos de alteração ocorrer no gateway e não ocorrer no Marketplace ou na interação do pedido de atendimento e também na API.
+
+
+
+
+
diff --git a/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md b/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md
new file mode 100644
index 000000000..0c63193a6
--- /dev/null
+++ b/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md
@@ -0,0 +1,49 @@
+---
+title: 'A pré-venda da coleção de CMS herdada não está funcionando'
+id: 1bRqhWCmtckyCbYf1SQa5N
+status: PUBLISHED
+createdAt: 2023-08-22T18:51:34.059Z
+updatedAt: 2023-08-22T18:51:34.595Z
+publishedAt: 2023-08-22T18:51:34.595Z
+firstPublishedAt: 2023-08-22T18:51:34.595Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: a-prevenda-da-colecao-de-cms-herdada-nao-esta-funcionando
+locale: pt
+kiStatus: Backlog
+internalReference: 885693
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Esperava-se que, ao marcar a caixa de seleção de pré-venda, a coleção fosse preenchida com produtos cuja data de lançamento tivesse sido preenchida para uma data futura.
+No entanto, isso não está acontecendo, pois a coleção não é preenchida, mas permanece sempre vazia.
+
+## Simulação
+
+
+
+- Definir uma data de lançamento em alguns produtos para uma data futura
+- Criar uma coleção
+- Acesse o administrador da coleção no CMS legado
+- Configure a coleção para produtos de pré-venda
+- Verifique se a coleção nunca é preenchida
+
+
+
+## Workaround
+
+
+Gerenciar manualmente os produtos na coleção
+
+
+
+
+
diff --git a/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
new file mode 100644
index 000000000..ee599b182
--- /dev/null
+++ b/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -0,0 +1,49 @@
+---
+title: 'Filtro de preço aplicado sobre o "preço à vista" em vez do preço normal'
+id: 2EEgRV1NxYuns4eF7F0ZqD
+status: PUBLISHED
+createdAt: 2024-02-15T19:39:53.576Z
+updatedAt: 2024-02-15T19:39:54.436Z
+publishedAt: 2024-02-15T19:39:54.436Z
+firstPublishedAt: 2024-02-15T19:39:54.436Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: filtro-de-preco-aplicado-sobre-o-preco-a-vista-em-vez-do-preco-normal
+locale: pt
+kiStatus: Backlog
+internalReference: 982664
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os filtros de preço são aplicados sobre o valor "spotPrice", que é o preço para condições especiais de pagamento, em vez do preço normal do item.
+
+Isso pode afetar as expectativas e, ao mesmo tempo, divergir da maioria dos lugares, que se concentram no preço normal, como normalmente fazem as prateleiras e o carrinho, ou propriedades como "priceRange" da API.
+
+## Simulação
+
+
+Considere um produto com preço de US$ 430 com 10% de desconto em um método de pagamento específico, gerando um "preço à vista" de US$ 387.
+
+A filtragem por itens com preço entre US$ 300 e US$ 400 retornará esse produto, que normalmente será exibido na prateleira como US$ 430 (seu preço normal), gerando a percepção de divergência.
+
+Da mesma forma, a propriedade "priceRange" da API responderá com os seguintes valores (considerando esse produto como o único resultado para essa consulta de pesquisa), alimentando a sensação de divergência:
+
+    "priceRange": { "sellingPrice": { "highPrice": 430, "lowPrice": 430 }, "listPrice": { "highPrice": 430, "lowPrice": 430 }}
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md b/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
new file mode 100644
index 000000000..c6007a477
--- /dev/null
+++ b/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
@@ -0,0 +1,41 @@
+---
+title: 'A faixa de preço na API de facetas não corresponde aos resultados da pesquisa'
+id: 2X9Z21u9kJh55uWu6o6sP3
+status: PUBLISHED
+createdAt: 2024-03-08T22:36:43.149Z
+updatedAt: 2024-03-08T22:36:44.086Z
+publishedAt: 2024-03-08T22:36:44.086Z
+firstPublishedAt: 2024-03-08T22:36:44.086Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: a-faixa-de-preco-na-api-de-facetas-nao-corresponde-aos-resultados-da-pesquisa
+locale: pt
+kiStatus: Backlog
+internalReference: 997121
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As faixas de preço da API de facetas ("Obter lista das facetas possíveis para uma determinada consulta") podem variar entre o retorno de baldes de valores "de" e "para" com preços arredondados e os preços mínimo e máximo entre os resultados da pesquisa.
+
+Embora os preços arredondados gerem uma experiência de usuário melhor para apresentar uma lista de faixas de preço ao comprador, não é desejável usá-los como um "controle deslizante" de preço.
+
+Além disso, como os preços mínimo e máximo são aplicados em um segundo momento, as faixas de preço como "baldes" em uma pesquisa que já aplica um filtro de preço ficam fora dos limites em relação aos preços especificados.
+
+## Simulação
+
+
+Usando a API, faça uma solicitação com e sem um filtro de preço como "/price/100:500" e observe as faixas de preço retornadas (de/para) no objeto "values" para a faceta com o tipo "PRICERANGE"
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/price-range-disregards-sales-policy.md b/docs/known-issues/pt/price-range-disregards-sales-policy.md
index 58bed48fa..93745c00d 100644
--- a/docs/known-issues/pt/price-range-disregards-sales-policy.md
+++ b/docs/known-issues/pt/price-range-disregards-sales-policy.md
@@ -1,36 +1,35 @@
 ---
-title: 'Price range disregards sales policy'
-id: 4isnfk4T2UB3CId8bXcvFT
-status: DRAFT
-createdAt: 2022-03-16T16:35:57.963Z
-updatedAt: 2022-06-08T14:01:22.874Z
-publishedAt: 
-firstPublishedAt: 
+title: 'Faixa de preço não respeita política comercial'
+id: 3OsmwHOZyM0AQWA8CuK0aC
+status: PUBLISHED
+createdAt: 2017-10-17T17:50:40.970Z
+updatedAt: 2022-12-22T20:46:23.778Z
+publishedAt: 2022-12-22T20:46:23.778Z
+firstPublishedAt: 2017-10-17T18:03:23.731Z
 contentType: knownIssue
-productTeam: Portal
+productTeam: Marketing & Merchandising
 author: 2mXZkbi0oi061KicTExNjo
-tag: Portal
-slug: price-range-disregards-sales-policy
+tag: Portal (CMS)
+slug: faixa-de-preco-nao-respeita-politica-comercial
 locale: pt
 kiStatus: Backlog
-internalReference: 322764
+internalReference: 
 ---
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+O filtro por faixa de preço, que é configurado nas opções de categoria, considera o preço cadastrado em todas as políticas comerciais da loja, ou seja, sempre vai imprimir o considerando o valor mais baixo cadastrado entre todas as políticas comerciais, possibilitando a exibição de um produto que não está na faixa de preço da política comercial específica.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+1. Cadastre preços diferentes em políticas comerciais diferentes para o mesmo SKU;
+2. Cadastre faixas de preço na categoria onde os preços cadastrados fiquem em faixas diferentes;
+3. Na política comercial com o preço do SKU mais caro, faça o filtro por faixa de preço;
+4. Veja que o valor do SKU considerado é o da outra política comercial, pois ele considera o valor mais barato entre todas as políticas.
+
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+Não existe solução de contorno para o cenário.
 
diff --git a/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md b/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
new file mode 100644
index 000000000..7581f7460
--- /dev/null
+++ b/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
@@ -0,0 +1,50 @@
+---
+title: 'O controle deslizante de faixa de preço tem como padrão o valor mínimo após a seleção de um filtro'
+id: 15ABXMTT9cqieizxYWqC2V
+status: PUBLISHED
+createdAt: 2023-11-08T13:34:50.960Z
+updatedAt: 2023-11-08T13:34:51.373Z
+publishedAt: 2023-11-08T13:34:51.373Z
+firstPublishedAt: 2023-11-08T13:34:51.373Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-controle-deslizante-de-faixa-de-preco-tem-como-padrao-o-valor-minimo-apos-a-selecao-de-um-filtro
+locale: pt
+kiStatus: Backlog
+internalReference: 843442
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Esta é uma faixa de preço, é um controle deslizante e tem dois seletores (marcadores), um para o mínimo e outro para o máximo, para que ele saiba onde se posicionar no controle deslizante.
+Ao aplicar um filtro de marca a ele, o seletor não moverá seu valor mínimo para os valores mínimos da marca, ele manterá o valor mínimo padrão e o marcador aparecerá fora do intervalo.
+
+## Simulação
+
+
+1 - Acesse uma página de categoria e observe o filtro de faixa de preço e seus valores mínimo e máximo.
+2- Selecione um filtro marcando-o à esquerda (category2/3/4)
+3- Com o filtro aplicado, observe que o controle deslizante de faixa de preço manterá o valor mínimo como antes e estará fora da faixa do controle deslizante.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/RuhwOHLwbPslKpeZ4VUq4Y995/?name=image.png)
+
+Filtrar com o comportamento descrito para o valor mínimo.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md b/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
new file mode 100644
index 000000000..bdd0bfec5
--- /dev/null
+++ b/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
@@ -0,0 +1,47 @@
+---
+title: 'Preço trocado se o mesmo item estiver no carrinho duas vezes e um deles for de Opções de montagem'
+id: 6ASEyEYPt9wjj4eSzMqdc0
+status: PUBLISHED
+createdAt: 2024-07-24T14:51:12.922Z
+updatedAt: 2024-07-24T14:51:13.713Z
+publishedAt: 2024-07-24T14:51:13.713Z
+firstPublishedAt: 2024-07-24T14:51:13.713Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: preco-trocado-se-o-mesmo-item-estiver-no-carrinho-duas-vezes-e-um-deles-for-de-opcoes-de-montagem
+locale: pt
+kiStatus: Backlog
+internalReference: 1070336
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se um item for adicionado ao carrinho como uma opção (também conhecida como filho) das Opções de montagem, e o mesmo item for adicionado ao carrinho como um item normal, os preços serão misturados e cada um será aplicado ao item incorreto.
+
+Por exemplo:
+
+- Item como uma opção com um preço de 0;
+- Item como regular com um preço de 100.
+No pedido, o item como opção terá o preço de 100 e o regular terá o preço de 0.
+
+## Simulação
+
+
+
+- Adicione um item com uma opção de montagem ao carrinho e certifique-se de que uma das opções tenha uma lista de preços diferente na configuração;
+- Adicione o mesmo item que a opção
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md b/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md
new file mode 100644
index 000000000..cef035eb7
--- /dev/null
+++ b/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md
@@ -0,0 +1,47 @@
+---
+title: 'Atualizações de preços com cache em aplicativos finais'
+id: 1ZDl8C3DDoACmxRqRlYDJo
+status: PUBLISHED
+createdAt: 2023-09-08T16:08:24.445Z
+updatedAt: 2023-09-08T16:08:25.900Z
+publishedAt: 2023-09-08T16:08:25.900Z
+firstPublishedAt: 2023-09-08T16:08:25.900Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: atualizacoes-de-precos-com-cache-em-aplicativos-finais
+locale: pt
+kiStatus: Backlog
+internalReference: 896520
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As modificações de preço feitas na conta são atualizadas quase em tempo real nas APIs de preço. No entanto, as simulações de checkout levam cerca de 5 minutos para ter o preço mais atualizado no produto devido ao cache. Isso é esperado.
+
+No entanto, em aplicativos finais, como afiliados externos ou integrações de mercado, como o Google Shopping, os preços podem, **às vezes**, ser entregues errados.
+
+Isso acontece porque o módulo de preços notifica todos os sistemas internos de que o preço foi atualizado assim que a ação ocorre, não dando tempo suficiente para que os aplicativos finais que consultam as simulações de checkout obtenham o preço sem o cache.
+
+## Simulação
+
+
+
+1. Atualizar o preço em uma sku;
+2. Verifique nos registros da ponte se o preço enviado para as integrações do marketplace foi o que deve ser atualizado ou o valor antigo
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
new file mode 100644
index 000000000..ea87aa091
--- /dev/null
+++ b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -0,0 +1,40 @@
+---
+title: 'Preços restritos ao valor máximo "Int32" na API Change Price'
+id: 5mzOjCUYs7vXUkttbsK0za
+status: PUBLISHED
+createdAt: 2022-04-25T17:28:05.159Z
+updatedAt: 2024-02-16T20:26:04.281Z
+publishedAt: 2024-02-16T20:26:04.281Z
+firstPublishedAt: 2022-04-25T17:28:05.773Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: precos-restritos-ao-valor-maximo-int32-na-api-change-price
+locale: pt
+kiStatus: No Fix
+internalReference: 566142
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O Checkout REST API Change price não suporta preços maiores que um valor "Int32". Portanto, a aplicação de um "preço manual" será restrita ao número "2.147.483.647" (número em decimais).
+
+## Simulação
+
+
+Ao usar a API "Change price" (https://developers.vtex.com/vtex-rest-api/reference/pricechange), o envio de uma carga útil como "{"price":2500000000}" (que representa US$ 25.000.000,00) retornará um erro 500 com a mensagem "Value was too large or too small for an Int32."
+
+## Workaround
+
+
+Use a API Handle cart items para atualizar o preço.
+
+
+
+
diff --git a/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
new file mode 100644
index 000000000..2eab29a6a
--- /dev/null
+++ b/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -0,0 +1,42 @@
+---
+title: 'Priorização por "palavra-chave" do produto, sem considerar stopwords'
+id: 55S7nFg61dAyCeGQCIw6aK
+status: PUBLISHED
+createdAt: 2024-05-30T22:05:25.328Z
+updatedAt: 2024-05-30T22:05:26.335Z
+publishedAt: 2024-05-30T22:05:26.335Z
+firstPublishedAt: 2024-05-30T22:05:26.335Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: priorizacao-por-palavrachave-do-produto-sem-considerar-stopwords
+locale: pt
+kiStatus: Backlog
+internalReference: 1041743
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os produtos podem ser priorizados nos resultados da pesquisa por sua "palavra-chave", uma palavra do nome do produto definida como relevante por um algoritmo. Stopwords são termos de pesquisa filtrados dos termos originais porque não são significativos para a pesquisa.
+
+Em um cenário em que a palavra-chave de um produto é uma palavra de parada, esse produto pode perder a prioridade nos resultados da pesquisa.
+
+## Simulação
+
+
+
+- Um produto com o nome "La vida en el oceano" terá "la" como palavra-chave.
+- Considerando uma loja em espanhol, uma busca por esse nome de produto será efetivamente feita como "vida el oceano" depois de remover as palavras de parada.
+- Os produtos com "vida" como palavra-chave serão priorizados em relação ao produto pesquisado
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md b/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md
index 0c10e265b..ae286ff98 100644
--- a/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md
+++ b/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md
@@ -3,8 +3,8 @@ title: 'Problema ao validar o campo de valor ao comprar com dois cartões'
 id: 6dr0p9WQPSHLkFaSbjI9J7
 status: PUBLISHED
 createdAt: 2022-03-28T01:05:19.734Z
-updatedAt: 2022-11-25T22:06:10.550Z
-publishedAt: 2022-11-25T22:06:10.550Z
+updatedAt: 2024-07-01T18:48:07.379Z
+publishedAt: 2024-07-01T18:48:07.379Z
 firstPublishedAt: 2022-03-28T01:05:20.361Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: problema-ao-validar-o-campo-de-valor-ao-comprar-com-dois-cartoes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 460683
 ---
 
diff --git a/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md b/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md
new file mode 100644
index 000000000..3d9f2b34d
--- /dev/null
+++ b/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md
@@ -0,0 +1,35 @@
+---
+title: 'Problema com a validação do telefone em dispositivos móveis'
+id: 2KpjpNZEbAZ7PFFPvMvwNA
+status: PUBLISHED
+createdAt: 2024-01-12T14:24:34.604Z
+updatedAt: 2024-01-12T14:24:56.084Z
+publishedAt: 2024-01-12T14:24:56.084Z
+firstPublishedAt: 2024-01-12T14:24:35.388Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: problema-com-a-validacao-do-telefone-em-dispositivos-moveis
+locale: pt
+kiStatus: Backlog
+internalReference: 964802
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A validação do campo do telefone em dispositivos móveis não está se comportando como pretendido. Quando o número esperado de caracteres é atingido, a validação marca corretamente o campo com uma verificação. Entretanto, quando caracteres adicionais são adicionados e, em seguida, removidos um a um, a validação não reconhece que a contagem de caracteres ainda é maior do que a esperada, marcando incorretamente a entrada como válida. A validação também marca como válidas entradas com menos caracteres do que o esperado.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md b/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md
new file mode 100644
index 000000000..5f1d0ecea
--- /dev/null
+++ b/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md
@@ -0,0 +1,68 @@
+---
+title: 'Exibição da disponibilidade do produto atrasada ao usar vários canais de vendas'
+id: 7JluVogO4pom0l57UobYIP
+status: PUBLISHED
+createdAt: 2023-12-07T16:18:59.300Z
+updatedAt: 2023-12-07T16:19:00.098Z
+publishedAt: 2023-12-07T16:19:00.098Z
+firstPublishedAt: 2023-12-07T16:19:00.098Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: exibicao-da-disponibilidade-do-produto-atrasada-ao-usar-varios-canais-de-vendas
+locale: pt
+kiStatus: Backlog
+internalReference: 949411
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A exibição, para lojas de portais antigos, de produtos em PLPs é baseada no canal de vendas da loja e em seus dados básicos de disponibilidade.
+
+Se um produto tiver estoque, preço e seus dados básicos para ser vendido adequadamente em uma loja e pertencer ao canal de vendas mencionado, esse produto estará e deverá ser listado na loja.
+
+No entanto, quando esse produto tiver a tag da opção "mostrar se não estiver disponível" definida como falsa, ele deverá ser removido das páginas da loja quando não puder ser vendido.
+
+Na maioria das vezes, esse processo ocorre de forma eficiente, mas nos casos em que o produto não está disponível para um determinado canal de vendas, mas está para outros, ele ainda pode ser exibido nos canais não intencionais.
+
+
+**Exemplo**:
+
+1 - O produto 1 está disponível nos canais de vendas 1, 2 e 3.
+
+2 - Ele ficou fora de estoque no canal de vendas 2. Ele não deve mais ser exibido nesse canal.
+
+3 - Como ainda está disponível nos canais 1 e 3, ele pode ficar "preso" e continuar sendo exibido por um longo período no canal 2, apesar de sua indisponibilidade.
+
+*Esse problema só ocorre quando um produto com o referido sinalizador = falso passa de disponível para indisponível em um único canal de vendas e continua sendo exibido nos demais. Essa inconsistência não ocorre no sentido inverso (passando de indisponível para disponível).
+
+
+## Simulação
+
+
+Para uma loja com vários canais de vendas e que usa domínios diferentes para cada um, obtenha um produto que esteja disponível em ambos e seja exibido em um resultado de pesquisa específico.
+
+Esse produto de teste deve ter a opção "mostrar mesmo se não estiver disponível" definida como falsa.
+
+Em seguida, defina-o como fora de estoque em um dos canais de vendas.
+
+Ele ainda será exibido, mesmo depois de muito tempo, nos resultados de pesquisa de ambos os domínios, apesar da indisponibilidade em um dos canais
+
+## Workaround
+
+
+**Opção A**) Execute uma exclusão de indexador e uma reindexação do banco de dados se sua loja tiver menos de 10.000 produtos e tiver vários itens nesse cenário.
+
+**Opção B**) Para um pequeno conjunto de produtos, remova sua disponibilidade da loja por completo (torne-o indisponível em todos os canais de vendas) e, em seguida, reverta imediatamente essas alterações.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md b/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
index 8fcad85c5..d98e480b3 100644
--- a/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
+++ b/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
@@ -3,8 +3,8 @@ title: 'A disponibilidade do produto é mostrada incorretamente nos pickups no m
 id: 6aoRWAMSGDwcuUPvGd8bI9
 status: PUBLISHED
 createdAt: 2022-03-30T17:24:21.013Z
-updatedAt: 2022-11-25T21:53:23.560Z
-publishedAt: 2022-11-25T21:53:23.560Z
+updatedAt: 2024-02-16T20:28:45.041Z
+publishedAt: 2024-02-16T20:28:45.041Z
 firstPublishedAt: 2022-03-30T17:24:21.669Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-disponibilidade-do-produto-e-mostrada-incorretamente-nos-pickups-no-modal-de-exibicao-do-carrinho
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 552875
 ---
 
diff --git a/docs/known-issues/pt/product-comissioning-inconsistent-cache.md b/docs/known-issues/pt/product-comissioning-inconsistent-cache.md
new file mode 100644
index 000000000..4d767df28
--- /dev/null
+++ b/docs/known-issues/pt/product-comissioning-inconsistent-cache.md
@@ -0,0 +1,65 @@
+---
+title: 'Comissionamento de produtos Cache inconsistente'
+id: 7queBSJcAG9yIlKbvWOVgY
+status: PUBLISHED
+createdAt: 2023-08-01T17:48:39.144Z
+updatedAt: 2023-08-01T17:56:01.673Z
+publishedAt: 2023-08-01T17:56:01.673Z
+firstPublishedAt: 2023-08-01T17:54:19.969Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: comissionamento-de-produtos-cache-inconsistente
+locale: pt
+kiStatus: Backlog
+internalReference: 872364
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+Existem, a partir de 2023, dois conjuntos de APIs distintos para atualizar as informações de um vendedor em um marketplace, são eles:
+https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
+https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/seller-register/pvt/sellers/-sellerId-/commissions/categories
+
+Eles devem ser consistentes entre si (e, em sua maioria, são), mas, ao atualizar os dados de comissionamento de todas as categorias no último, leva muito tempo para atualizar as informações na resposta da API catalog_system.
+
+Isso acontece quando a comissão é definida para a categoria raiz (por exemplo, o payload abaixo)
+
+```
+[
+ {
+      ""categoryId"": ""default"",
+      ""categoryName"": nulo,
+      ""categoryFullPath"": [],
+      ""productCommissionPercentage"": 50.0,
+      ""freightCommissionPercentage"": 0.0
+  }
+]
+```
+
+A principal consequência desse atraso é que o checkout e os marktplaces usam principalmente a resposta do catalog_system, o que pode levar a comissões incorretas nos pedidos.
+
+
+## Simulação
+
+
+1. Em um marketplace, tente usar uma solicitação GET usando a API do catálogo para um determinado vendedor https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/seller/-sellerId-
+2. Atualize seus dados de comissionamento de produtos por meio de um PUT para o mesmo caminho https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
+3. Execute outro GET e você verá que as informações foram atualizadas corretamente.
+4. Agora, tente fazer o mesmo usando a API de registro do vendedor https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-/commissions
+5. Envie um payload para a categoria raiz (ou seja, para toda a loja, além de outras categorias com comissões específicas) configurando qualquer productComissionPercentage https://developers.vtex.com/docs/api-reference/marketplace-apis#put-/seller-register/pvt/sellers/-sellerId-/commissions/categories
+6. Se você buscar dados por meio de GET para essa mesma coleção, verá as informações atualizadas: https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-/commissions
+7. No entanto, ao tentar obter esses mesmos dados por meio da API catalog_system, levará dias para atualizá-los se você não fizer nenhuma outra atualização.
+
+
+## Workaround
+
+- Configurar outros dados na API de registro do vendedor, o que força uma falha de cache.
+- Atualizar diretamente por meio da API catalog_system
+- Usando a interface do usuário para realizar atualizações"
+
diff --git a/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md b/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md
new file mode 100644
index 000000000..7d1490d81
--- /dev/null
+++ b/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md
@@ -0,0 +1,47 @@
+---
+title: 'A imagem do produto no admin muda com mais de 70 skus.'
+id: 6EtUyiWzpm5moEN6hkY4B0
+status: PUBLISHED
+createdAt: 2024-03-21T15:18:20.218Z
+updatedAt: 2024-03-21T15:18:21.405Z
+publishedAt: 2024-03-21T15:18:21.405Z
+firstPublishedAt: 2024-03-21T15:18:21.405Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-imagem-do-produto-no-admin-muda-com-mais-de-70-skus
+locale: pt
+kiStatus: Backlog
+internalReference: 1003966
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um produto tem mais de 70 variações de skus, sua imagem no admin (e somente no admin) é alterada para uma imagem de informações:
+ ![](https://vtexhelp.zendesk.com/attachments/token/3oAwbW4sgou7su2F6Ls5CGqoR/?name=image.png)
+
+com o texto: "ATENÇÃO: não foi possível excluir este produto porque ele tem mais SKUs do que o permitido pelo sistema."
+
+## Simulação
+
+
+
+- Adicionar mais de 70 skus em um produto
+- Verifique se a imagem no admin muda para a apresentada anteriormente
+- Verifique se o produto permanece o mesmo no PDP
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
index b70699804..0c4d0fac6 100644
--- a/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -3,8 +3,8 @@ title: 'A API de Inserção/Atualização de Produto permite "\n" no campo de te
 id: 5TfUw5tTxBEu9HkL3ypBKw
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.325Z
-updatedAt: 2022-11-25T21:44:48.430Z
-publishedAt: 2022-11-25T21:44:48.430Z
+updatedAt: 2024-02-16T20:28:55.474Z
+publishedAt: 2024-02-16T20:28:55.474Z
 firstPublishedAt: 2022-06-28T16:55:54.138Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: a-api-de-insercaoatualizacao-de-produto-permite-n-no-campo-de-textolink
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 486459
 ---
 
diff --git a/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
new file mode 100644
index 000000000..80f2f07d7
--- /dev/null
+++ b/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -0,0 +1,44 @@
+---
+title: 'A pesquisa "Product name contains" (O nome do produto contém) com mais de um termo não funciona na IU reformulada do catálogo'
+id: 2kI6ab0kdpLG6m63ETGGqf
+status: PUBLISHED
+createdAt: 2024-06-05T13:38:38.836Z
+updatedAt: 2024-06-05T13:38:39.630Z
+publishedAt: 2024-06-05T13:38:39.630Z
+firstPublishedAt: 2024-06-05T13:38:39.630Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-pesquisa-product-name-contains-o-nome-do-produto-contem-com-mais-de-um-termo-nao-funciona-na-iu-reformulada-do-catalogo
+locale: pt
+kiStatus: Backlog
+internalReference: 1044571
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na lista de produtos reformulada do catálogo, um dos campos de pesquisa é "Product name contains" (O nome do produto contém). Atualmente, ao pesquisar um nome de produto com mais de um termo, podem ocorrer duas situações:
+
+- ele retorna qualquer produto que tenha qualquer um dos termos
+- não retorna o produto com o nome exato pesquisado
+
+## Simulação
+
+
+Pesquise um nome de produto com dois ou mais termos em um catálogo reformulado e observe que podem ser retornados produtos que contenham apenas um dos termo
+
+## Workaround
+
+
+Use a pesquisa "SKU name" ou as outras opções de pesquisa disponíveis
+
+
+
+
+
diff --git a/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md b/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
index ff8474246..ad161ca6c 100644
--- a/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
+++ b/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
@@ -3,8 +3,8 @@ title: 'Campo Nome do produto em XML retorna Nome do produto + Nome do Sku quand
 id: 7sNNzBe5pLn7oigDgoCKjv
 status: PUBLISHED
 createdAt: 2022-09-19T19:06:55.572Z
-updatedAt: 2022-11-25T21:43:35.947Z
-publishedAt: 2022-11-25T21:43:35.947Z
+updatedAt: 2024-02-16T20:23:45.927Z
+publishedAt: 2024-02-16T20:23:45.927Z
 firstPublishedAt: 2022-09-19T19:06:56.137Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: campo-nome-do-produto-em-xml-retorna-nome-do-produto-nome-do-sku-quando-o-produto-tem-apenas-1-sku
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 661089
 ---
 
diff --git a/docs/known-issues/pt/product-page-sessions-not-working.md b/docs/known-issues/pt/product-page-sessions-not-working.md
new file mode 100644
index 000000000..936825a1d
--- /dev/null
+++ b/docs/known-issues/pt/product-page-sessions-not-working.md
@@ -0,0 +1,43 @@
+---
+title: 'As sessões da página do produto não estão funcionando'
+id: 6Hgk9lBPmrZ9byc6eeRiki
+status: PUBLISHED
+createdAt: 2024-01-04T21:34:51.613Z
+updatedAt: 2024-01-04T21:36:00.900Z
+publishedAt: 2024-01-04T21:36:00.900Z
+firstPublishedAt: 2024-01-04T21:34:52.264Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: as-sessoes-da-pagina-do-produto-nao-estao-funcionando
+locale: pt
+kiStatus: Backlog
+internalReference: 961591
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A visão geral do administrador tem algumas informações de análise. A informação sobre as sessões da página do produto deveria retornar os valores desse evento, mas às vezes está retornando zero
+
+## Simulação
+
+
+Acesse o administrador da loja e tente procurar as sessões da página do produto. Verifique se ele está retornando zero
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md b/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md
index c4d75e894..9cbc0c047 100644
--- a/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md
+++ b/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md
@@ -3,8 +3,8 @@ title: 'Preço do produto não considerando o vendedor padrão no PDP'
 id: 4VOIW6kCTfFZ3S9u3xtdDF
 status: PUBLISHED
 createdAt: 2022-02-23T21:52:42.520Z
-updatedAt: 2022-11-25T22:13:37.983Z
-publishedAt: 2022-11-25T22:13:37.983Z
+updatedAt: 2024-02-16T20:27:12.071Z
+publishedAt: 2024-02-16T20:27:12.071Z
 firstPublishedAt: 2022-03-07T22:34:44.879Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: preco-do-produto-nao-considerando-o-vendedor-padrao-no-pdp
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429888
 ---
 
diff --git a/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md b/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
index 9c4b299a9..38ed12b49 100644
--- a/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
+++ b/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
@@ -3,8 +3,8 @@ title: 'Substituição de produto em pedido OMS não funcionando nas contas do p
 id: 1wQTfSR6OB6CL0sRpCYARp
 status: PUBLISHED
 createdAt: 2023-02-14T12:25:00.911Z
-updatedAt: 2023-02-14T12:25:01.506Z
-publishedAt: 2023-02-14T12:25:01.506Z
+updatedAt: 2024-07-01T18:48:50.766Z
+publishedAt: 2024-07-01T18:48:50.766Z
 firstPublishedAt: 2023-02-14T12:25:01.506Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: substituicao-de-produto-em-pedido-oms-nao-funcionando-nas-contas-do-portal-do-vendedor
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 753484
 ---
 
diff --git a/docs/known-issues/pt/product-specification-export-index-out-of-range.md b/docs/known-issues/pt/product-specification-export-index-out-of-range.md
index f9308b177..f12fcbdfa 100644
--- a/docs/known-issues/pt/product-specification-export-index-out-of-range.md
+++ b/docs/known-issues/pt/product-specification-export-index-out-of-range.md
@@ -1,16 +1,16 @@
 ---
-title: 'Exportação de Especificação do produto retorna Index Out of Range'
+title: 'Especificação do produto Índice de exportação fora da faixa'
 id: 2Qu9QCZvfcjmNfAh3uvPkf
 status: PUBLISHED
 createdAt: 2022-02-25T12:22:04.014Z
-updatedAt: 2022-11-25T21:45:45.357Z
-publishedAt: 2022-11-25T21:45:45.357Z
+updatedAt: 2024-01-10T20:25:32.586Z
+publishedAt: 2024-01-10T20:25:32.586Z
 firstPublishedAt: 2022-02-25T12:22:04.405Z
 contentType: knownIssue
 productTeam: Catalog
 author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
-slug: exportacao-de-especificacao-do-produto-retorna-index-out-of-range
+slug: especificacao-do-produto-indice-de-exportacao-fora-da-faixa
 locale: pt
 kiStatus: Backlog
 internalReference: 481095
@@ -23,32 +23,26 @@ internalReference: 481095
 </div>
 
 
-Ao tentar exportar, utilizando a IU: , dados das especificações do produto, se eles não tiverem campos válidos registrados diretamente na categoria a ser exportada, o processo falhará com uma mensagem "Index out of Range".
-
-
-
+Ao tentar exportar especificações de produtos da interface do usuário "Importar e exportar", se houver algum valor nulo ou relação nula na categoria a ser exportada, o processo falhará com uma mensagem "Índice fora do intervalo". Em outras palavras, a categoria deve ter registrado diretamente em seu nível um campo de produto, produtos e produtos com valores associados.
 
 
 ## Simulação
 
 
-1) Ir para a IU de exportação de SPecification do produto: ProdutoExportacaoImportacaoEspecificacaoV2.aspx
-
-2) Clique com o botão direito em uma categoria na qual não há nenhum campo de especificação de produto registrado
-
-3) Uma mensagem de erro de "Index out of bonds" será solicitada.
-
+1) Acesse a UI de exportação da Especificação do produto: ProdutoExportacaoImportacaoEspecificacaoV2.aspx
 
+2) Clique com o botão direito do mouse em uma categoria na qual não haja um campo de especificação de produto registrado
 
+3) Será exibida uma mensagem de erro do tipo "Index out of bonds".
 
 
 
 ## Workaround
 
 
-Exportar os pais ou filhos da categoria desejada
+Exporte a categoria pai ou filha da categoria desejada
 
 ou
 
-Use a API de obtenção de especificações de produto para buscar dados: https://developers.vtex.com/vtex-rest-api/reference/catalog-api-product-specification
+Use a API de obtenção de especificações do produto para obter dados: https://developers.vtex.com/vtex-rest-api/reference/catalog-api-product-specification
 
diff --git a/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
new file mode 100644
index 000000000..b8dae0cf4
--- /dev/null
+++ b/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -0,0 +1,35 @@
+---
+title: 'Filtro "Product Specification" no Collection Module assumindo valores incorretos'
+id: 2vg3t5kp7j4Ttla53pVjck
+status: PUBLISHED
+createdAt: 2023-10-26T22:22:44.895Z
+updatedAt: 2023-10-26T22:22:45.413Z
+publishedAt: 2023-10-26T22:22:45.413Z
+firstPublishedAt: 2023-10-26T22:22:45.413Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: filtro-product-specification-no-collection-module-assumindo-valores-incorretos
+locale: pt
+kiStatus: Backlog
+internalReference: 926593
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No módulo Collection, o filtro Product Specifications (Especificações do produto) não está funcionando corretamente quando a especificação tem o tipo "Text" (Texto) e "Large Text" (Texto grande). Quando esse tipo de especificação é selecionado, uma caixa de texto é aberta para inserir os valores possíveis separados por vírgula, tabulação ou enter. Entretanto, ao digitar apenas um caractere, o sistema o assume como um valor mesmo sem separar os termos.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md b/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
new file mode 100644
index 000000000..924d3f9fe
--- /dev/null
+++ b/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
@@ -0,0 +1,35 @@
+---
+title: 'O filtro de especificação do produto no Collection Module não lista a categoria raiz'
+id: 6ZDaMBc9G5TtuwMJ5b0nuK
+status: PUBLISHED
+createdAt: 2023-10-12T14:29:57.985Z
+updatedAt: 2023-10-12T14:29:58.698Z
+publishedAt: 2023-10-12T14:29:58.698Z
+firstPublishedAt: 2023-10-12T14:29:58.698Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-filtro-de-especificacao-do-produto-no-collection-module-nao-lista-a-categoria-raiz
+locale: pt
+kiStatus: Backlog
+internalReference: 918687
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No módulo de coleção, ao usar os filtros para adicionar produtos, o filtro Product Specification não lista os campos registrados na categoria raiz
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
new file mode 100644
index 000000000..347c1ce08
--- /dev/null
+++ b/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -0,0 +1,44 @@
+---
+title: 'A importação da especificação do produto com o tipo "texto" não aciona a indexação do produto'
+id: 5eQB7LCCyDbVNQBQvWti33
+status: PUBLISHED
+createdAt: 2024-03-12T19:36:58.647Z
+updatedAt: 2024-03-12T19:36:59.477Z
+publishedAt: 2024-03-12T19:36:59.477Z
+firstPublishedAt: 2024-03-12T19:36:59.477Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-importacao-da-especificacao-do-produto-com-o-tipo-texto-nao-aciona-a-indexacao-do-produto
+locale: pt
+kiStatus: Backlog
+internalReference: 998658
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao importar especificações de produtos, os tipos com valores pré-registrados (como Checkbox ou Radio) acionam a indexação do produto, mas quando o tipo é "Texto" o mesmo não ocorre.
+
+## Simulação
+
+
+
+- Registre um campo com o tipo texto dentro da categoria
+- Importar um arquivo preenchido com um novo valor
+- Observe que o valor será atualizado no Admin, mas o produto não será reindexad
+
+## Workaround
+
+
+Configure esse tipo de campo por meio do Admin ou da API
+
+
+
+
+
diff --git a/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md b/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
index d53b14ed3..74667d7e9 100644
--- a/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
+++ b/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
@@ -3,8 +3,8 @@ title: 'Imposto sobre o produtoValor percentual economizado pelo resolvedor de b
 id: 5zalMbGTuKaxpepVEdW3Dt
 status: PUBLISHED
 createdAt: 2022-03-21T17:38:14.386Z
-updatedAt: 2022-11-25T22:12:35.742Z
-publishedAt: 2022-11-25T22:12:35.742Z
+updatedAt: 2024-02-16T20:27:03.136Z
+publishedAt: 2024-02-16T20:27:03.136Z
 firstPublishedAt: 2022-03-21T17:38:14.760Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: imposto-sobre-o-produtovalor-percentual-economizado-pelo-resolvedor-de-busca-e-incorreto-devido-ao-arredondamento
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 470143
 ---
 
diff --git a/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md b/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
index 756843fb9..f0cf36780 100644
--- a/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
+++ b/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
@@ -1,18 +1,18 @@
 ---
-title: 'Produtos que não correspondem corretamente quando o produtoNome contém números'
+title: 'Os produtos não estão sendo correspondidos corretamente quando o productName contém números'
 id: 7Kr0VtRScH54j04Rh2uuOj
 status: PUBLISHED
 createdAt: 2023-03-01T18:55:20.183Z
-updatedAt: 2023-03-01T18:55:20.910Z
-publishedAt: 2023-03-01T18:55:20.910Z
+updatedAt: 2023-10-19T12:08:30.076Z
+publishedAt: 2023-10-19T12:08:30.076Z
 firstPublishedAt: 2023-03-01T18:55:20.910Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
-slug: produtos-que-nao-correspondem-corretamente-quando-o-produtonome-contem-numeros
+slug: os-produtos-nao-estao-sendo-correspondidos-corretamente-quando-o-productname-contem-numeros
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 762525
 ---
 
@@ -23,28 +23,24 @@ internalReference: 762525
 </div>
 
 
-Quando o vendedor envia um sku para o mercado, o sistema Matcher é responsável por consultar o catálogo do mercado e verificar se já existe um produto similar ao skus do vendedor.
-Ele faz isso primariamente pelo ProductName.
+Quando o vendedor envia um sku para o marketplace, o sistema Matcher é responsável por consultar o catálogo do marketplace e verificar se já existe um produto semelhante aos skus do vendedor.
+Ele faz isso principalmente pelo ProductName.
 
-Entretanto, esta busca nem sempre está funcionando quando neste nome de produto há caracteres numéricos.
-
-
-##
+No entanto, essa pesquisa nem sempre está funcionando quando no nome do produto há caracteres numéricos.
 
 ## Simulação
 
 
 
-1. O vendedor envia skus para o marktplace com números no nome do produto;
-2. Os skus serão aprovados separadamente (em vez de terem uma correspondência) no catálogo do mercado.
+1. O vendedor envia skus para o mercado com números no nome do produto;
+2. Os skus serão aprovados separadamente (em vez de terem uma correspondência) no catálogo do marketplace.
 
 
-##
 
 ## Workaround
 
 
-Enviar o produto sem números em seu nome.
+Envie o produto sem números em seu nome.
 
 
 
diff --git a/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md b/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md
new file mode 100644
index 000000000..a56f84f99
--- /dev/null
+++ b/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md
@@ -0,0 +1,42 @@
+---
+title: 'Produtos que mostram a bandeira e o desconto após o término da promoção'
+id: 21qXD9XIfaxsxCH4jMGLJX
+status: PUBLISHED
+createdAt: 2024-06-07T19:50:09.302Z
+updatedAt: 2024-06-07T19:50:10.154Z
+publishedAt: 2024-06-07T19:50:10.154Z
+firstPublishedAt: 2024-06-07T19:50:10.154Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: produtos-que-mostram-a-bandeira-e-o-desconto-apos-o-termino-da-promocao
+locale: pt
+kiStatus: Backlog
+internalReference: 383911
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Às vezes, as bandeiras de promoção e os descontos são exibidos no PLP e no PLP após a data de expiração da promoção. Isso acontece porque a promoção não aciona a indexação do produto, resultando na exibição incorreta do desconto.
+
+## Simulação
+
+
+1- Criar uma promoção com uma bandeira
+2- Definir uma data de expiração
+3- Verifique se a promoção continua ativa no PLP e no PDP
+
+
+
+
+## Workaround
+
+
+Reindexar os produtos incluídos na promoção
+
diff --git a/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md b/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
new file mode 100644
index 000000000..0971cac0c
--- /dev/null
+++ b/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
@@ -0,0 +1,42 @@
+---
+title: 'Produtos com preço zero mostrados como indisponíveis no Intelligent Search'
+id: 4oh4ROvCp7JrfWeSAc0dE0
+status: PUBLISHED
+createdAt: 2024-06-05T23:34:05.987Z
+updatedAt: 2024-06-05T23:34:07.147Z
+publishedAt: 2024-06-05T23:34:07.147Z
+firstPublishedAt: 2024-06-05T23:34:07.147Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: produtos-com-preco-zero-mostrados-como-indisponiveis-no-intelligent-search
+locale: pt
+kiStatus: Backlog
+internalReference: 1045184
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os produtos com preço zero são mostrados como indisponíveis pela Pesquisa Inteligente. Diferentemente de um produto sem preço registrado, o preço definido como zero define um produto gratuito.
+
+## Simulação
+
+
+É possível simular o cenário apenas alterando seu preço para "R$ 0,00". Isso afetará o frontend dos resultados de pesquisa e as APIs.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md b/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
new file mode 100644
index 000000000..b479fcf00
--- /dev/null
+++ b/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
@@ -0,0 +1,48 @@
+---
+title: 'Produtos com variações de sku aprovadas em Skus Recebidos estão sendo criados com skus duplicados no Catálogo.'
+id: 2RqrBOeHDBZmfmqe6Rowl2
+status: PUBLISHED
+createdAt: 2023-08-29T15:50:44.042Z
+updatedAt: 2023-08-29T15:50:44.976Z
+publishedAt: 2023-08-29T15:50:44.976Z
+firstPublishedAt: 2023-08-29T15:50:44.976Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: produtos-com-variacoes-de-sku-aprovadas-em-skus-recebidos-estao-sendo-criados-com-skus-duplicados-no-catalogo
+locale: pt
+kiStatus: Backlog
+internalReference: 889676
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O vendedor pode enviar um produto com várias variações de sku.
+No módulo Received Skus do marketplace, esses skus aparecerão separadamente para serem aprovados.
+O comerciante pode aprovar manualmente esses skus.
+
+O cenário que está ocorrendo é que alguns dos skus estão sendo criados duplicados no catálogo do marketplace devido a uma falha na comunicação do catálogo.
+
+## Simulação
+
+
+Aprovar skus na área de Skus pendentes recebidos do mesmo produto em um curto intervalo de tempo.
+Verificar no catálogo se algum sku foi criado duplicado
+
+
+
+## Workaround
+
+
+Aprovar lentamente os skus do mesmo produto para evitar erros no catálogo.
+
+
+
+
+
diff --git a/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
new file mode 100644
index 000000000..bfd9ce2c3
--- /dev/null
+++ b/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -0,0 +1,43 @@
+---
+title: 'Produtos com "unitMultiplier" sinalizados erroneamente como "com promoção" para filtros de pesquisa'
+id: 2rCi8K01DHsNuYsefE7oR2
+status: PUBLISHED
+createdAt: 2024-02-15T22:52:17.434Z
+updatedAt: 2024-02-15T22:52:18.189Z
+publishedAt: 2024-02-15T22:52:18.189Z
+firstPublishedAt: 2024-02-15T22:52:18.189Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: produtos-com-unitmultiplier-sinalizados-erroneamente-como-com-promocao-para-filtros-de-pesquisa
+locale: pt
+kiStatus: Backlog
+internalReference: 982830
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Um produto cujo preço de venda é menor do que o preço de tabela será sinalizado como parte de uma promoção para fins de filtragem de pesquisa. Os produtos com algum multiplicador de unidade podem resultar em um cálculo incorreto que pode afetar essa comparação, fazendo com que eles recebam esse sinalizador erroneamente.
+
+## Simulação
+
+
+A simulação depende da ocorrência de problemas específicos de arredondamento, mas um exemplo disso é um produto com preço de tabela e preço normal de US$ 264,20 e um multiplicador de unidade de 3,07.
+
+Embora o preço de tabela e o preço normal sejam os mesmos, esse item será retornado no filtro de pesquisa "promotion=yes"
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md b/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
index 8040b0500..87bddb035 100644
--- a/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
+++ b/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
@@ -3,8 +3,8 @@ title: 'Produtos sem estoque em vendedores de whitelabel estão aparecendo no fi
 id: 5WCKWky2gKGTZyp9ydnFnL
 status: PUBLISHED
 createdAt: 2022-04-20T15:52:50.807Z
-updatedAt: 2022-11-25T21:57:51.904Z
-publishedAt: 2022-11-25T21:57:51.904Z
+updatedAt: 2024-07-01T18:48:10.012Z
+publishedAt: 2024-07-01T18:48:10.012Z
 firstPublishedAt: 2022-04-20T15:52:51.421Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: produtos-sem-estoque-em-vendedores-de-whitelabel-estao-aparecendo-no-final-do-plp
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 495741
 ---
 
diff --git a/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md b/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md
index 50567b0be..89f0764bc 100644
--- a/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md
+++ b/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md
@@ -3,8 +3,8 @@ title: 'O formulário de upload do produto/SKU permite upload/download do format
 id: 3NSxmGXvgFKHd2C4v2EwWV
 status: PUBLISHED
 createdAt: 2022-06-08T20:04:18.508Z
-updatedAt: 2022-11-25T22:12:28.497Z
-publishedAt: 2022-11-25T22:12:28.497Z
+updatedAt: 2024-02-16T20:26:55.864Z
+publishedAt: 2024-02-16T20:26:55.864Z
 firstPublishedAt: 2022-06-08T20:04:19.062Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
 slug: o-formulario-de-upload-do-produtosku-permite-uploaddownload-do-formato-utf16
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 493402
 ---
 
diff --git a/docs/known-issues/pt/productsskus-import-does-not-support-lb.md b/docs/known-issues/pt/productsskus-import-does-not-support-lb.md
index 0a0a0571a..5f58d6954 100644
--- a/docs/known-issues/pt/productsskus-import-does-not-support-lb.md
+++ b/docs/known-issues/pt/productsskus-import-does-not-support-lb.md
@@ -3,8 +3,8 @@ title: "Produtos&SKUs Importação não suporta 'lb'."
 id: 1OjtnFf9MpY1IFzQa8Ua2t
 status: PUBLISHED
 createdAt: 2022-06-17T19:38:17.726Z
-updatedAt: 2023-01-05T20:03:49.367Z
-publishedAt: 2023-01-05T20:03:49.367Z
+updatedAt: 2024-02-16T20:29:45.337Z
+publishedAt: 2024-02-16T20:29:45.337Z
 firstPublishedAt: 2022-06-17T19:38:18.052Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: produtosskus-importacao-nao-suporta-lb
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 337860
 ---
 
diff --git a/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md b/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
new file mode 100644
index 000000000..03b79e24c
--- /dev/null
+++ b/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
@@ -0,0 +1,45 @@
+---
+title: "Dados do perfil carregados vazios na interface do usuário para o perfil completo com 'ignoreProfileData'"
+id: 10B1QKgN42sjapDEALmKOp
+status: PUBLISHED
+createdAt: 2024-04-15T11:41:06.841Z
+updatedAt: 2024-04-15T11:41:07.691Z
+publishedAt: 2024-04-15T11:41:07.691Z
+firstPublishedAt: 2024-04-15T11:41:07.691Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: dados-do-perfil-carregados-vazios-na-interface-do-usuario-para-o-perfil-completo-com-ignoreprofiledata
+locale: pt
+kiStatus: Backlog
+internalReference: 1016582
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao definir "ignoreProfileData" via API Ignore profile data on checkout, se o comprador tiver um perfil completo, mas não estiver conectado, os dados serão carregados vazios na interface do usuário.
+
+## Simulação
+
+
+
+- Enviar o ignoreProfileData via API Ignorar dados de perfil no checkout;
+- Adicionar um item ao carrinho;
+- Adicionar um e-mail com um perfil completo; nenhum dado será carregado e será necessário fazer login.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/jVk0tmcR7R4BmaEkDcCedJgBP/?name=image.png
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md b/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
new file mode 100644
index 000000000..a2255e041
--- /dev/null
+++ b/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
@@ -0,0 +1,44 @@
+---
+title: 'O item de promoção não será exibido dividido após a adição de dados de preferências do cliente'
+id: 3bme5oDKxbRyQzozUP6XNp
+status: PUBLISHED
+createdAt: 2023-06-12T20:09:11.042Z
+updatedAt: 2024-01-31T15:20:39.646Z
+publishedAt: 2024-01-31T15:20:39.646Z
+firstPublishedAt: 2023-06-12T20:09:11.600Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-item-de-promocao-nao-sera-exibido-dividido-apos-a-adicao-de-dados-de-preferencias-do-cliente
+locale: pt
+kiStatus: Backlog
+internalReference: 842575
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao aplicar uma promoção Mais por Menos, o comportamento esperado é separar o item promocional dos itens regulares, mas os itens serão agrupados após a adição dos dados de preferências do cliente.
+
+Dependendo do momento em que os dados de preferências do cliente são adicionados, isso cria uma experiência inconsistente para o cliente no carrinho ou o pedido é criado com itens agrupados.
+
+## Simulação
+
+
+
+- Adicionar itens ao carrinho para obter um item gratuito ou com desconto (a promoção e os itens regulares serão divididos);
+- Adicionar dados de preferências do cliente ao formulário de pedido (os itens serão agrupados)
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md b/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
new file mode 100644
index 000000000..17741fefe
--- /dev/null
+++ b/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
@@ -0,0 +1,42 @@
+---
+title: 'A assinatura de promoção com frequência de semana, mês e dia não está funcionando em ciclos recorrentes'
+id: 70DNIBLC5kctaFZSLooOQ7
+status: PUBLISHED
+createdAt: 2024-01-12T17:00:50.068Z
+updatedAt: 2024-06-20T14:26:39.099Z
+publishedAt: 2024-06-20T14:26:39.099Z
+firstPublishedAt: 2024-01-12T17:00:50.823Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: a-assinatura-de-promocao-com-frequencia-de-semana-mes-e-dia-nao-esta-funcionando-em-ciclos-recorrentes
+locale: pt
+kiStatus: Backlog
+internalReference: 965484
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma promoção de assinatura é definida no módulo de assinatura, o comerciante tem a possibilidade de escolher a frequência com que essa promoção será aplicada à assinatura.
+
+Se a frequência escolhida for "semana", "dia" ou "mês", a promoção não será aplicada nos ciclos recorrentes, apesar da configuração.
+
+## Simulação
+
+
+
+1. Crie uma promoção de assinatura que se aplique ao primeiro ciclo e aos ciclos recorrentes;
+2. Selecione a frequência de semana/dia/mês
+3. Verifique se os pedidos recorrentes não têm a assinatura aplicada
+
+## Workaround
+
+
+-
+
diff --git a/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md b/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
new file mode 100644
index 000000000..b6a209f99
--- /dev/null
+++ b/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
@@ -0,0 +1,52 @@
+---
+title: 'A tabela de preços promocionais em carrinhos de compras grandes pode afetar o desempenho ou levar a erros de tempo limite'
+id: 22H47mc9qYLdzk2sFkbBut
+status: PUBLISHED
+createdAt: 2023-12-07T15:47:28.360Z
+updatedAt: 2023-12-07T15:57:49.789Z
+publishedAt: 2023-12-07T15:57:49.789Z
+firstPublishedAt: 2023-12-07T15:47:28.972Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: a-tabela-de-precos-promocionais-em-carrinhos-de-compras-grandes-pode-afetar-o-desempenho-ou-levar-a-erros-de-tempo-limite
+locale: pt
+kiStatus: Backlog
+internalReference: 949389
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Quando temos uma loja com tabelas de preços promocionais criadas e grandes carrinhos de compras aplicando as promoções, isso causa lentidão no desempenho da compra e leva a erros de timeout no carrinho.
+
+Qualquer ação no carrinho pode desencadear erros, como adicionar itens, edições, inserir CEP, etc., comprometendo o desempenho da compra.
+
+Não podemos saber com precisão qual o número de tabelas de preços promocionais que estão sendo calculadas no carrinho ou a quantidade de itens adicionados ao carrinho que começará a disparar os erros de timeout ou a tornar o desempenho mais lento, pelo que foi analisado pode acontecer com qualquer quantidade significativa.
+
+
+## Simulação
+
+
+
+Crie várias tabelas de preços promocionais e um carrinho de compras com muitos itens (aqui não podemos apontar um número claro, como 50 ou 100, isso depende das promoções)
+
+
+
+## Workaround
+
+
+
+Infelizmente, não temos nenhuma solução alternativa para isso,
+desativar as promoções e usar o módulo de preços para inserir os preços ajudaria.
+
+
+
+
+
diff --git a/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md b/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
new file mode 100644
index 000000000..ac9b3dffc
--- /dev/null
+++ b/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
@@ -0,0 +1,44 @@
+---
+title: 'As promoções e os impostos restritos por método de envio não funcionam para os vendedores Whitelabel'
+id: 3ue1kZdbX1mMFqPCkl0tC4
+status: PUBLISHED
+createdAt: 2023-08-09T13:25:02.168Z
+updatedAt: 2023-08-09T13:26:13.874Z
+publishedAt: 2023-08-09T13:26:13.874Z
+firstPublishedAt: 2023-08-09T13:25:02.698Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: as-promocoes-e-os-impostos-restritos-por-metodo-de-envio-nao-funcionam-para-os-vendedores-whitelabel
+locale: pt
+kiStatus: Backlog
+internalReference: 315485
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As promoções e os impostos restritos por métodos de envio não funcionam para os vendedores Whitelabel. Eles não serão aplicados na solicitação de simulação (usada para o carrinho e o checkout) porque a solicitação do marketplace não especifica o `selectedSla` e, portanto, seus valores não serão apresentados ao usuário.
+
+Mas o processo de criação do pedido enviará esse `selectedSla`, onde a promoção/imposto será calculada e os valores serão alterados. Mas a divergência entre a simulação e o processo de criação do pedido pode impedir que a compra seja concluída, pois o cliente pagará um valor, calculado na solicitação de simulação, diferente do valor calculado na criação do pedido.
+
+## Simulação
+
+
+- criar um imposto no Whitelabel Seller que seja restrito a algum método de envio
+- crie um carrinho no marketplace que usará esse vendedor e selecione o método de envio especificado anteriormente
+
+O valor não será apresentado e o pedido não poderá ser criado.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa conhecida para restringir um imposto ou uma promoção por método de envio em um vendedor Whitelabel.
+
diff --git a/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md b/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
index 5c8cc7fa0..eedcd088f 100644
--- a/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
+++ b/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
@@ -3,8 +3,8 @@ title: 'As promoções por ordem de pagamento não aparecem na página do produt
 id: HZ5IoCFFOhuxU0jQWkMPp
 status: PUBLISHED
 createdAt: 2019-08-13T20:45:50.232Z
-updatedAt: 2023-03-31T15:44:56.958Z
-publishedAt: 2023-03-31T15:44:56.958Z
+updatedAt: 2024-07-01T18:48:59.282Z
+publishedAt: 2024-07-01T18:48:59.282Z
 firstPublishedAt: 2019-08-13T21:10:58.244Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: as-promocoes-por-ordem-de-pagamento-nao-aparecem-na-pagina-do-produto
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 781523
 ---
 
diff --git a/docs/known-issues/pt/promotions-microrounding-divergence.md b/docs/known-issues/pt/promotions-microrounding-divergence.md
new file mode 100644
index 000000000..0b7f63d3a
--- /dev/null
+++ b/docs/known-issues/pt/promotions-microrounding-divergence.md
@@ -0,0 +1,93 @@
+---
+title: 'Promoções divergência de microrredes'
+id: 603ZTMtdgi9olc6UiWLfmX
+status: PUBLISHED
+createdAt: 2023-12-22T18:48:32.438Z
+updatedAt: 2023-12-22T18:48:33.176Z
+publishedAt: 2023-12-22T18:48:33.176Z
+firstPublishedAt: 2023-12-22T18:48:33.176Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: promocoes-divergencia-de-microrredes
+locale: pt
+kiStatus: Backlog
+internalReference: 957369
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O módulo de promoções arredonda os descontos em até 3 dígitos significativos, o que pode, em cenários muito específicos, resultar em pequenas divergências no preço final de um carrinho.
+
+Por exemplo, digamos que temos o seguinte cenário de exemplo:
+
+Item 1 - $10
+Item 2 - US$ 20
+Item 3 - $32
+____________
+Total - US$ 62
+
+E 2 promoções são aplicadas em todos eles:
+
+Promoção A - $15 OFF
+Promoção B - 10% de desconto.
+
+
+Normalmente, o desconto a ser calculado é sequencial, com o valor nominal de desconto vindo primeiro:
+
+$62 - $15 = $47
+Em seguida
+$47 * 0.9 = $42.3
+
+
+No entanto, os descontos são distribuídos, mesmo para o desconto nominal, proporcionalmente no carrinho, portanto, o que realmente acontece é:
+
+`item 1`:
+Valor original = $10
+Desconto nominal (15 * 10/62 do carrinho) = -$2,41935484
+Desconto percentual esperado (12,5806452 * 0,9) = -$1,25806452
+Desconto real percentual = -$1,258
+
+`item 2`:
+Valor original = US$ 20
+Desconto nominal (15 * 20/62 do carrinho) = -$4,83870968
+Desconto percentual esperado (15,1612903 * 0,9) = -$1,51612903
+Desconto real percentual = -$1,516
+
+`item 3`:
+Valor original = US$ 32
+Desconto nominal (15 * 32/62 do carrinho) = -$7,74193548
+Desconto percentual esperado (24,2580645 * 0,9) = -$2,42580645
+Desconto real percentual = -$2,426
+
+
+🔎 diferença total: 0.00006452 + 0.000012903 + 0.000019355 = 0.0000270973
+
+Podemos ver, acima, que foi criada uma "micro" diferença.
+
+Se vários itens fossem adicionados, com preços distintos, a esse carrinho de exemplo, essa diferença poderia chegar a 1 centavo (0,01) ou mais.
+
+
+## Simulação
+
+
+Há várias maneiras de recriar o caso. Felizmente, todas elas são extremamente específicas.
+
+Por isso, é difícil replicar o problema, mas, na maioria das vezes, é necessário criar um carrinho com vários (~10+) itens diferentes e todos eles com mais de duas promoções, sendo que o ideal é que uma delas seja um desconto nominal e a outra, um desconto percentual.
+
+## Workaround
+
+
+n/a
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md b/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
new file mode 100644
index 000000000..c2f6a9442
--- /dev/null
+++ b/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
@@ -0,0 +1,42 @@
+---
+title: 'Promoções que resultam em classificação/filtragem incorreta por preço ou desconto'
+id: 1qGJByINC3S7ibgiQccVcY
+status: PUBLISHED
+createdAt: 2023-08-28T17:51:44.627Z
+updatedAt: 2023-11-10T18:19:30.796Z
+publishedAt: 2023-11-10T18:19:30.796Z
+firstPublishedAt: 2023-08-28T17:55:21.450Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: authors_84
+tag: Intelligent Search
+slug: promocoes-que-resultam-em-classificacao-filtragem-incorreta-por-preco-ou
+locale: pt
+kiStatus: Backlog
+internalReference: 888304
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+As listas de produtos e os resultados de pesquisa podem ser mal classificados/filtrados ao usar a classificação ou a filtragem por preço ou desconto se houver preços de itens desatualizados no nível do índice, mesmo que a vitrine esteja mostrando o preço correto.
+
+A classificação dos produtos é sempre baseada em informações indexadas anteriormente (dados frios), enquanto a vitrine geralmente recalcula todas as informações em tempo de execução (dados quentes), de modo que os preços apresentados estão sempre corretos em relação ao carrinho.
+
+Espera-se que cada alteração de preço (e até mesmo outras alterações) faça com que os itens sejam reindexados para que o índice esteja atualizado com as novas condições. O problema é que o módulo Promoções não suporta o envio de notificações para o serviço de indexação quando uma promoção começa ou termina, resultando ocasionalmente em preços de itens desatualizados, em que o módulo Pesquisa não é capaz de classificar/filtrar os itens corretamente em comparação com os preços em tempo real.
+
+Qualquer ação que reindexe as condições comerciais do item (como alterações de estoque) também atualizará organicamente seu preço considerando a promoção, o que acaba mascarando o problema para alguns itens.
+
+As lojas que usam `simulationBehavior=skip` não verão divergências entre a classificação de itens e os filtros aplicados no PLP, pois esse parâmetro resulta na renderização dos "dados frios" ali, mas elas aparecerão ao comparar o mesmo item no PLP com seu PDP, que funciona de forma fixa como um `simulationBehavior=default`, recuperando informações atualizadas em tempo de execução.
+
+## Simulação
+
+A maneira mais fácil de ver os efeitos desse problema é ter uma lista de produtos classificados pelo menor preço, criar uma promoção para um produto no meio da lista e observar se a classificação não muda depois de ativar a promoção, mesmo quando ele fica mais barato do que outros produtos.
+
+## Workaround
+
+N/A
+
diff --git a/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md b/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md
index a67b1cc52..c2eeade50 100644
--- a/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md
+++ b/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md
@@ -1,18 +1,18 @@
 ---
-title: 'Promoções UI carregando informações erradas sobre moeda'
+title: 'IU de promoções carregando informações de moeda incorretas'
 id: 7liSZOtS1Hs2P84bXzRrG9
 status: PUBLISHED
 createdAt: 2022-12-19T14:41:51.129Z
-updatedAt: 2022-12-19T14:41:51.903Z
-publishedAt: 2022-12-19T14:41:51.903Z
+updatedAt: 2024-02-15T12:11:06.893Z
+publishedAt: 2024-02-15T12:11:06.893Z
 firstPublishedAt: 2022-12-19T14:41:51.903Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
 author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
-slug: promocoes-ui-carregando-informacoes-erradas-sobre-moeda
+slug: iu-de-promocoes-carregando-informacoes-de-moeda-incorretas
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 718908
 ---
 
@@ -23,31 +23,26 @@ internalReference: 718908
 </div>
 
 
+Ao abrir o módulo Promoções muito rapidamente e várias vezes seguidas, um comportamento incorreto aparece na interface do usuário.
 
-Ao abrir o módulo Promoções muito rapidamente e muitas vezes em uma fila, um comportamento errado aparece na IU.
+O campo "Restrict this promotion to seller products" (Restringir esta promoção a produtos do vendedor) não carrega o espaço reservado correto, mas sim o espaço reservado "GLOBAL SELECT-A-SELLER..." (Selecionar um vendedor global).
 
-O campo "Restringir esta promoção aos produtos do vendedor" não carrega o lugar correto, em vez disso carrega o lugar correto "GLOBAL SELECT-A-SELLLER...".
-
-A informação da moeda é carregada como R$ (real)
+As informações de moeda são carregadas como R$ (real)
 
 Ao salvar a promoção, o valor final não é o esperado pelo cliente.
 
-
-##
-
 ## Simulação
 
 
+Não há uma maneira fácil de reproduzir esse cenário. Às vezes, ao abrir o módulo de promoções em guias diferentes muito rapidamente, o comportamento acontece.
+Verifique se o campo "Restrict this promotion to seller products" (Restringir esta promoção a produtos do vendedor) está diferente para saber se você alcançou o cenário
 
-Não há uma maneira fácil de reproduzir este cenário. Às vezes, ao abrir o módulo de promoções em diferentes abas muito rapidamente, o comportamento acontece.
-Verifique se o campo "Restringir esta promoção aos produtos do vendedor" é diferente para saber se você chegou ao cenário.
+## Workaround
 
 
-##
+Feche a IU de promoções atual e abra uma nova em que o comportamento não esteja ocorrendo.
 
-## Workaround
 
 
 
-Feche a atual UI de promoções e abra uma nova onde o comportamento não esteja acontecendo.
 
diff --git a/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md b/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md
index 6d2cd28c6..5afd98189 100644
--- a/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md
+++ b/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md
@@ -3,8 +3,8 @@ title: 'Bloqueio de propriedadeClass de infoCard não funciona'
 id: LTEEWCaZx2unBWSEJFDw6
 status: PUBLISHED
 createdAt: 2023-01-31T19:02:03.835Z
-updatedAt: 2023-01-31T19:02:04.299Z
-publishedAt: 2023-01-31T19:02:04.299Z
+updatedAt: 2024-07-01T18:48:42.227Z
+publishedAt: 2024-07-01T18:48:42.227Z
 firstPublishedAt: 2023-01-31T19:02:04.299Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: bloqueio-de-propriedadeclass-de-infocard-nao-funciona
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 743730
 ---
 
diff --git a/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md b/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
new file mode 100644
index 000000000..cd08abdc2
--- /dev/null
+++ b/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
@@ -0,0 +1,44 @@
+---
+title: 'Os custos de frete proporcionais mostram valores negativos quando há promoções que dividem itens e frete grátis aplicado'
+id: 60gzoaN1WQC6OsEymBPdeq
+status: PUBLISHED
+createdAt: 2023-09-28T22:29:39.597Z
+updatedAt: 2023-09-28T22:33:53.751Z
+publishedAt: 2023-09-28T22:33:53.751Z
+firstPublishedAt: 2023-09-28T22:29:40.382Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-custos-de-frete-proporcionais-mostram-valores-negativos-quando-ha-promocoes-que-dividem-itens-e-frete-gratis-aplicado
+locale: pt
+kiStatus: Backlog
+internalReference: 909925
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar promoções que dividem itens, como o tipo "Mais por menos", os custos de envio proporcionais podem exibir valores negativos.
+
+Esse problema é visível quando o desconto "Mais por menos" é aplicado pelo vendedor e uma promoção de frete grátis é aplicada pelo marketplace, resultando na concessão de um desconto. Esse comportamento causa um loop infinito quando se tenta concluir uma compra.
+
+## Simulação
+
+
+Pode haver diferentes combinações causando o problema, pois o peso é usado para calcular os custos proporcionais de envio, o que dificulta a reprodução.
+
+
+
+## Workaround
+
+
+Configure a promoção de frete grátis a ser aplicada pelo vendedor.
+
+
+
+
diff --git a/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md b/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md
index 57ac77637..7e5a9912c 100644
--- a/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md
+++ b/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md
@@ -3,8 +3,8 @@ title: 'A mensagem PT é mostrada no módulo License Manager'
 id: 6nC0EfB2pO2pIyH9HEDDAP
 status: PUBLISHED
 createdAt: 2022-07-19T19:02:51.412Z
-updatedAt: 2022-11-25T21:57:09.655Z
-publishedAt: 2022-11-25T21:57:09.655Z
+updatedAt: 2024-07-01T18:48:30.289Z
+publishedAt: 2024-07-01T18:48:30.289Z
 firstPublishedAt: 2022-07-19T19:02:52.298Z
 contentType: knownIssue
 productTeam: Identity
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Identity
 slug: a-mensagem-pt-e-mostrada-no-modulo-license-manager
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 620782
 ---
 
diff --git a/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md b/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
index 672091a80..4a54f3db0 100644
--- a/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
+++ b/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
@@ -3,8 +3,8 @@ title: '/pub/portal/pagetype não mapeia corretamente quando 2+ categorias têm
 id: 7ykvMnWt3PhGAqWhEFmnp3
 status: PUBLISHED
 createdAt: 2022-03-18T15:40:04.430Z
-updatedAt: 2022-11-25T22:10:11.690Z
-publishedAt: 2022-11-25T22:10:11.690Z
+updatedAt: 2024-02-16T20:27:59.429Z
+publishedAt: 2024-02-16T20:27:59.429Z
 firstPublishedAt: 2022-03-18T15:40:04.877Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: pubportalpagetype-nao-mapeia-corretamente-quando-2-categorias-tem-o-mesmo-nome
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 314551
 ---
 
diff --git a/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
new file mode 100644
index 000000000..c2febef23
--- /dev/null
+++ b/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -0,0 +1,43 @@
+---
+title: 'A compra não pode ser concluída e está travada em "o tipo de frete foi alterado"'
+id: mgewQ8QmZ3V3dkc7vdJkV
+status: PUBLISHED
+createdAt: 2023-09-25T13:28:28.121Z
+updatedAt: 2024-03-27T14:37:54.335Z
+publishedAt: 2024-03-27T14:37:54.335Z
+firstPublishedAt: 2023-09-25T13:28:28.557Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-compra-nao-pode-ser-concluida-e-esta-travada-em-o-tipo-de-frete-foi-alterado
+locale: pt
+kiStatus: Backlog
+internalReference: 449341
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar qualquer promoção que cause a divisão de um item e dois vendedores diferentes forem selecionados, clicar em "Comprar agora" exibirá a mensagem "o tipo de frete foi alterado", impedindo a conclusão da compra.
+
+## Simulação
+
+
+
+- Configure uma promoção "mais por menos", por exemplo;
+- Adicionar ao carrinho o item da promoção;
+- Adicione outro item de outro vendedor;
+- Tente concluir a compra; a mensagem "o tipo de frete foi alterado" será exibida
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md b/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md
index 584331225..a0faf4cca 100644
--- a/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md
+++ b/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md
@@ -1,16 +1,16 @@
 ---
-title: 'Coloca Preço Sobrescreve Lógica de Preço do KIT'
+title: 'O preço de venda substitui a lógica de preço do KIT'
 id: 6eUXEJkxQUl6NCiFWrIiFw
 status: PUBLISHED
 createdAt: 2022-06-28T16:56:02.848Z
-updatedAt: 2022-11-25T22:12:23.543Z
-publishedAt: 2022-11-25T22:12:23.543Z
+updatedAt: 2023-11-09T13:43:40.623Z
+publishedAt: 2023-11-09T13:43:40.623Z
 firstPublishedAt: 2022-06-28T16:56:03.203Z
 contentType: knownIssue
 productTeam: Pricing & Promotions
 author: 2mXZkbi0oi061KicTExNjo
 tag: Pricing & Promotions
-slug: coloca-preco-sobrescreve-logica-de-preco-do-kit
+slug: o-preco-de-venda-substitui-a-logica-de-preco-do-kit
 locale: pt
 kiStatus: Backlog
 internalReference: 404486
@@ -23,12 +23,29 @@ internalReference: 404486
 </div>
 
 
+A composição do preço do KIT deve ser baseada no cálculo de seus componentes e suas quantidades.
+
+Ou seja, o preço de um KIT deve ser:
+`SKU_KIT_Price= (component_1*qty_1) + (component_2*qty_2) + (...) + (component_n*qty_n)`
+
+No entanto, atualmente há uma maneira de contornar essa lógica se o usuário inserir um PUT Price diretamente no sku do kit no Pricing Module.
+
 
 ## Simulação
 
 
 
+1. Crie um KIT com pelo menos dois componentes e defina seus preços e quantidades;
+2. Verifique se o preço do KIT está definido de acordo com a lógica mencionada acima.
+3. Atualize o preço do KIT no módulo de preços inserindo um PUT Price no sku do kit;
+4. Verifique se, mesmo ao atualizar os componentes de preço e suas quantidades, o preço do KIT permanecerá como o preço de venda definido anteriormente
+
 ## Workaround
 
 
+Ao fazer qualquer alteração nos componentes, um novo preço de venda com o novo cálculo e a lógica correta o substituirá novamente, normalizando o comportamento "errado".
+
+
+
+
 
diff --git a/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md b/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
index 008a76f2e..74dc4aad9 100644
--- a/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
+++ b/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
@@ -3,8 +3,8 @@ title: 'O componente seletor de quantidade não retorna ao valor limite quando o
 id: 4QRAzY1A0UD8hOUEkxAawz
 status: PUBLISHED
 createdAt: 2022-09-16T16:27:15.880Z
-updatedAt: 2022-11-25T22:13:30.254Z
-publishedAt: 2022-11-25T22:13:30.254Z
+updatedAt: 2024-02-16T20:28:10.783Z
+publishedAt: 2024-02-16T20:28:10.783Z
 firstPublishedAt: 2022-09-16T16:27:16.745Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: o-componente-seletor-de-quantidade-nao-retorna-ao-valor-limite-quando-o-usuario-clica-rapidamente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 659909
 ---
 
diff --git a/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md b/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md
new file mode 100644
index 000000000..1e9df0302
--- /dev/null
+++ b/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md
@@ -0,0 +1,46 @@
+---
+title: 'O Quantity Selector não permite que eu altere o valor digitando'
+id: 4whARKlTiLQhTluJrIRfO5
+status: PUBLISHED
+createdAt: 2024-06-28T15:01:34.187Z
+updatedAt: 2024-07-05T16:17:08.672Z
+publishedAt: 2024-07-05T16:17:08.672Z
+firstPublishedAt: 2024-06-28T15:01:35.225Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-quantity-selector-nao-permite-que-eu-altere-o-valor-digitando
+locale: pt
+kiStatus: Fixed
+internalReference: 1057544
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O componente seletor de quantidade na Faststore está apresentando um bug. Se o valor mínimo de um produto for 10 e eu quiser digitar 15, o seletor não permitirá que eu exclua o 0 porque ele permitirá que digitemos 1, que seria um valor menor do que a quantidade mínima. Se eu quiser digitar 15, preciso digitar 150 e então poderei excluir o 0.
+
+## Simulação
+
+
+Você pode testá-lo em nossa loja padrão em nossa página de documentação:
+https://developers.vtex.com/docs/guides/faststore/molecules-quantity-selector
+https://starter.vtex.app/handmade-plastic-chips-9009169/p
+
+Nesse caso, o valor mínimo é 1 e o valor máximo é 10.
+Tente digitar 2 excluindo o valor 1, mas ele não permitirá que você digite porque, depois de excluir o 1, o valor será menor que o valor mínimo
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md b/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
index 286efe8da..ec1d9b8f3 100644
--- a/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
+++ b/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
@@ -3,8 +3,8 @@ title: 'O seletor de quantidade no modo stepper não se atualiza após atingir a
 id: 77bK8oIAPR8LEMtOn6QEqs
 status: PUBLISHED
 createdAt: 2022-12-23T12:20:23.568Z
-updatedAt: 2022-12-23T12:20:24.148Z
-publishedAt: 2022-12-23T12:20:24.148Z
+updatedAt: 2024-02-16T20:27:43.811Z
+publishedAt: 2024-02-16T20:27:43.811Z
 firstPublishedAt: 2022-12-23T12:20:24.148Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: o-seletor-de-quantidade-no-modo-stepper-nao-se-atualiza-apos-atingir-a-qunatity-maxima-disponivel
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 704458
 ---
 
diff --git a/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index be7ca6043..a03f1d98d 100644
--- a/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -21,7 +21,7 @@ internalReference:
 Atualmente, o cenário de exibição das opções "Receber | Retirar" é condicionado ao CEP buscado em qualquer uma das abas. Isso significa que, se na aba de "Receber" for buscado um CEP que não é atendido por um ponto de retirada, a aba "Retirar" não será exibida ao usuário.
 
 
-![Captura de Tela 2018-11-21 às 14.25.40](https://images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
+![Captura de Tela 2018-11-21 às 14.25.40](//images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md b/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
index 7e12f642c..2c2f72b9f 100644
--- a/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
+++ b/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
@@ -3,8 +3,8 @@ title: 'Skus recebidos: As aprovações de associação não adicionam o canal d
 id: 5ob4jquCm8l84MhX6285h8
 status: PUBLISHED
 createdAt: 2022-04-18T17:15:41.091Z
-updatedAt: 2023-05-09T19:06:08.893Z
-publishedAt: 2023-05-09T19:06:08.893Z
+updatedAt: 2024-02-16T20:25:58.313Z
+publishedAt: 2024-02-16T20:25:58.313Z
 firstPublishedAt: 2022-04-18T17:15:41.436Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: skus-recebidos-as-aprovacoes-de-associacao-nao-adicionam-o-canal-de-vendas-disponivel-do-vendedor-no-produto-quando-o-sku-e-vendido-por-mais-de-um-vendedor
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 562472
 ---
 
diff --git a/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md b/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md
new file mode 100644
index 000000000..99b930d60
--- /dev/null
+++ b/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md
@@ -0,0 +1,49 @@
+---
+title: 'O filtro Skus recebido não funciona com caracteres especiais'
+id: 6aSErtF2Xv5RuKuIHUEEPg
+status: PUBLISHED
+createdAt: 2023-11-29T17:58:26.201Z
+updatedAt: 2023-11-29T17:58:26.900Z
+publishedAt: 2023-11-29T17:58:26.900Z
+firstPublishedAt: 2023-11-29T17:58:26.900Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: o-filtro-skus-recebido-nao-funciona-com-caracteres-especiais
+locale: pt
+kiStatus: Backlog
+internalReference: 944533
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar filtrar os skus no módulo Received Skus, o marketplace pode optar por filtrar por vendedor, categoria e/ou marca.
+
+No entanto, ao selecionar uma marca que tenha caracteres especiais (como "&" ou "+"), o resultado é que não há skus nesse filtro, o que não é correto.
+
+## Simulação
+
+
+
+1. Filtre por uma das opções no módulo Received Skus;
+2. Selecione um valor com um caractere especial;
+3. Verifique se o resultado é nenhum skus;
+4. Agora, pesquise pelo valor na busca e verifique se, de fato, há alguns skus.
+
+
+
+## Workaround
+
+
+Não há solução alternativa para corrigir o filtro, mas o uso da pesquisa pode trazer um resultado próximo dos skus.
+
+
+
+
+
diff --git a/docs/known-issues/pt/received-skus-review-tab-missing-products.md b/docs/known-issues/pt/received-skus-review-tab-missing-products.md
new file mode 100644
index 000000000..173e088ae
--- /dev/null
+++ b/docs/known-issues/pt/received-skus-review-tab-missing-products.md
@@ -0,0 +1,51 @@
+---
+title: 'Produtos ausentes na guia "Revisão" da Skus recebida'
+id: 2UM0JQUZVq5o7NHCjmrg8N
+status: PUBLISHED
+createdAt: 2023-11-23T16:30:51.874Z
+updatedAt: 2024-02-01T12:54:26.917Z
+publishedAt: 2024-02-01T12:54:26.917Z
+firstPublishedAt: 2023-11-23T16:30:52.647Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: produtos-ausentes-na-guia-revisao-da-skus-recebida
+locale: pt
+kiStatus: Fixed
+internalReference: 939877
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As ofertas enviadas pelos vendedores podem eventualmente ir para a guia Revisão do Skus Recebido do Marketplace, dependendo se foram aprovadas ou não nas regras de Qualidade da Oferta.
+
+Quando estiverem nessa guia, o vendedor poderá atualizar seus skus com as informações corretas (ou quaisquer novas informações).
+
+No entanto, quando isso acontece, o sku muda seu status de "WaitingReview" (Aguardando revisão) para "Reviewed" (Revisado), desaparecendo da guia Review (Revisão) e de todos os Skus recebidos.
+
+## Simulação
+
+
+
+1. Configure uma regra "Optional requirements" (Requisitos opcionais) no módulo Offer Quality (Qualidade da oferta) no lado do marketplace;
+2. Aguarde até que um sku vá para a guia Review (Revisão) por não passar na regra;
+3. Aguarde uma atualização do sku no lado do vendedor;
+4. Verifique se o sku não está mais na guia Review (Revisão)
+
+
+
+## Workaround
+
+
+Aprovar o produto via API: https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerskuid-/versions/-version-/matches/-matchid-
+
+
+
+
+
diff --git a/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md b/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md
new file mode 100644
index 000000000..b8e09762e
--- /dev/null
+++ b/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md
@@ -0,0 +1,46 @@
+---
+title: 'Os redirecionamentos estão sendo contados várias vezes'
+id: 51JfHBdp72duH5cBWMYl0t
+status: PUBLISHED
+createdAt: 2024-07-16T19:48:36.586Z
+updatedAt: 2024-07-16T19:49:42.290Z
+publishedAt: 2024-07-16T19:49:42.290Z
+firstPublishedAt: 2024-07-16T19:48:37.314Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: os-redirecionamentos-estao-sendo-contados-varias-vezes
+locale: pt
+kiStatus: Backlog
+internalReference: 1066548
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar carregar um arquivo com mais de 200 redirecionamentos, o front entra em um loop e lê esses redirecionamentos três vezes. Isso pode levar a mais redirecionamentos na mensagem de erro na tela ou no modal de carregamento. Os redirecionamentos não estão sendo duplicados, mas estão sendo lidos mais de uma vez.
+
+## Simulação
+
+
+Tente fazer upload de um arquivo com 930 redirecionamentos, por exemplo. O modal de carregamento aparecerá com um número maior que 930:
+ ![](https://vtexhelp.zendesk.com/attachments/token/vypbPdcFp4KtjVvI5rL4tHQXU/?name=image.png)
+
+Se o arquivo contiver um erro, você poderá encontrar uma mensagem de erro semelhante a esta:
+ ![](https://vtexhelp.zendesk.com/collaboration/graphql/attachments/download/s3-145778c5-53eb-4002-9b91-1b43f7394896/image.png)
+Esse é apenas um erro frontal e não está afetando o carregamento dos redirecionamentos em si
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md b/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
new file mode 100644
index 000000000..ea1642c10
--- /dev/null
+++ b/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
@@ -0,0 +1,44 @@
+---
+title: 'Redirecionamentos para links de visualização ao usar / no final do URL'
+id: 7mO7pEA0DMclbWy2pPPUkd
+status: PUBLISHED
+createdAt: 2023-10-27T19:00:01.248Z
+updatedAt: 2023-10-27T19:00:01.916Z
+publishedAt: 2023-10-27T19:00:01.916Z
+firstPublishedAt: 2023-10-27T19:00:01.916Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: redirecionamentos-para-links-de-visualizacao-ao-usar-no-final-do-url
+locale: pt
+kiStatus: Backlog
+internalReference: 927041
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na Faststore, se você acessar um link de visualização com o / no final do URL, o link será redirecionado para uma página como esta https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
+
+## Simulação
+
+
+Tente acessar uma página de visualização da Faststore com um / no final do URL, como https://starter.vtex.app/s/
+Você será redirecionado para https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md b/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md
new file mode 100644
index 000000000..d52eab647
--- /dev/null
+++ b/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md
@@ -0,0 +1,45 @@
+---
+title: 'O comportamento do RefId não é consistente entre a API e a interface do usuário'
+id: 4007iEJ8bCN96PBY0nsIB4
+status: PUBLISHED
+createdAt: 2023-09-29T13:11:04.826Z
+updatedAt: 2023-10-20T13:41:48.679Z
+publishedAt: 2023-10-20T13:41:48.679Z
+firstPublishedAt: 2023-09-29T13:11:05.384Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-comportamento-do-refid-nao-e-consistente-entre-a-api-e-a-interface-do-usuario
+locale: pt
+kiStatus: Backlog
+internalReference: 910050
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos dois comportamentos para o código refid: por meio da API, não é possível ser igual a outros produtos, mas por meio da interface do usuário, é possível inserir o mesmo valor que outros produtos já têm.
+
+## Simulação
+
+
+
+Criar um produto com um código redIf
+Crie outro produto e tente usar o mesmo código refId que o outro; via API não será possível, mas via UI será
+
+## Workaround
+
+
+
+Se você precisar usar os mesmos refIds para produtos diferentes, insira-os por meio da interface do usuário.
+
+
+
+
+
diff --git a/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md b/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
new file mode 100644
index 000000000..cd3b862ff
--- /dev/null
+++ b/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
@@ -0,0 +1,49 @@
+---
+title: 'O conflito de regex nos faz identificar erroneamente Mastercard como Visa'
+id: MzUm8xH6vDeGxWcj6GCbZ
+status: PUBLISHED
+createdAt: 2023-09-04T17:51:08.019Z
+updatedAt: 2023-11-30T15:25:47.066Z
+publishedAt: 2023-11-30T15:25:47.066Z
+firstPublishedAt: 2023-09-04T17:51:09.705Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-conflito-de-regex-nos-faz-identificar-erroneamente-mastercard-como-visa
+locale: pt
+kiStatus: Backlog
+internalReference: 893588
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O conflito de regex nos faz identificar incorretamente a marca dos cartões no checkout.
+
+## Simulação
+
+
+
+1. Configure duas condições de pagamento, uma para processamento de cartão de crédito Visa e outra para processamento de cartão de crédito Mastercard
+2. Compre um item aleatório na loja e opte por pagá-lo com cartão de crédito.
+3. Preencha o número do cartão com o Mastercard BIN 523431 e complete com números aleatórios.
+4. Preencha as demais informações do cartão com dados falsos
+5. Finalize a compra
+6. Vá para o admin e procure a transação já criada e o pagamento será identificado como Visa em vez de Mastercard
+
+
+
+## Workaround
+
+
+N/a
+
+
+
+
+
diff --git a/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md b/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md
new file mode 100644
index 000000000..0008f29e9
--- /dev/null
+++ b/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md
@@ -0,0 +1,43 @@
+---
+title: 'A API da região retorna a lista de vendedores devido ao cache'
+id: 1uDscW8Z3tG4EXS23fCfci
+status: PUBLISHED
+createdAt: 2024-01-22T17:34:18.690Z
+updatedAt: 2024-01-22T17:48:47.576Z
+publishedAt: 2024-01-22T17:48:47.576Z
+firstPublishedAt: 2024-01-22T17:34:19.518Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-api-da-regiao-retorna-a-lista-de-vendedores-devido-ao-cache
+locale: pt
+kiStatus: Backlog
+internalReference: 969692
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar uma estrutura de subconta com região, se a API Get sellers by region or address for usada em ambas as contas para o mesmo canal de vendas e uma delas não estiver disponível para esse canal de vendas, ela retornará uma lista de vendedores devido ao cache.
+
+## Simulação
+
+
+
+- Crie uma nova loja;
+- Defina um canal de vendas diferente para a loja;
+- Use a API Get sellers by region or address in the store (Obter vendedores por região ou endereço na loja);
+- Usar novamente a API para o mesmo canal de vendas na outra loja
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 2ab471e18..de0f7d42d 100644
--- a/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,10 +1,10 @@
 ---
 title: 'Regions API não calcula corretamente o "seller 1" ao solicitar sellers que não são white label'
 id: 20sT9AMMi7Ob5IZc7FeiCB
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
-updatedAt: 2022-11-25T21:53:57.112Z
-publishedAt: 2022-11-25T21:53:57.112Z
+updatedAt: 2024-03-14T13:47:34.269Z
+publishedAt: 
 firstPublishedAt: 2022-03-28T20:45:28.144Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md b/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
new file mode 100644
index 000000000..32033374a
--- /dev/null
+++ b/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
@@ -0,0 +1,45 @@
+---
+title: 'Os usuários registrados (não conectados) não conseguem concluir o checkout ao mudar de entrega para retirada na página de checkout'
+id: hmQ2riW1Ptjxyhk6gcWxN
+status: PUBLISHED
+createdAt: 2023-07-28T19:49:16.993Z
+updatedAt: 2024-04-17T15:46:57.958Z
+publishedAt: 2024-04-17T15:46:57.958Z
+firstPublishedAt: 2023-07-28T19:49:17.732Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: os-usuarios-registrados-nao-conectados-nao-conseguem-concluir-o-checkout-ao-mudar-de-entrega-para-retirada-na-pagina-de-checkout
+locale: pt
+kiStatus: Fixed
+internalReference: 870845
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário registrado (não conectado) inicia o checkout com Entrega como opção de envio e, posteriormente, muda para retirada, ao tentar concluir o checkout, a mensagem de erro "O campo Número no anexo de envio é inválido" será exibida e não permitirá a realização do pedido.
+
+## Simulação
+
+
+
+1. Vá para o checkout e adicione um novo item
+2. Insira um código postal para calcular o frete e mantenha **Delivery** selecionado
+3. Prossiga para a finalização da compra e, quando solicitado a inserir um e-mail, use o de um usuário registrado
+4. O checkout mostrará uma mensagem pop-up informando que seus dados pessoais foram recuperados de compras anteriores
+5. Mude de Delivery para Pick-Up e tente concluir o pedido (a mensagem de erro será exibida
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md b/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
index 2ce5bae86..6bbf70f8d 100644
--- a/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
+++ b/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
@@ -3,8 +3,8 @@ title: 'A remoção do EAN via API não está inativando SKUs sem RefIDs'
 id: 2DIKKs93S41F38c3PrekSO
 status: PUBLISHED
 createdAt: 2022-08-01T11:37:52.731Z
-updatedAt: 2022-11-25T21:44:12.277Z
-publishedAt: 2022-11-25T21:44:12.277Z
+updatedAt: 2024-07-01T18:48:35.030Z
+publishedAt: 2024-07-01T18:48:35.030Z
 firstPublishedAt: 2022-08-01T11:37:53.288Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: a-remocao-do-ean-via-api-nao-esta-inativando-skus-sem-refids
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 626031
 ---
 
diff --git a/docs/known-issues/pt/render-component-issues-on-site-editor.md b/docs/known-issues/pt/render-component-issues-on-site-editor.md
index 4613341ee..38348cc1c 100644
--- a/docs/known-issues/pt/render-component-issues-on-site-editor.md
+++ b/docs/known-issues/pt/render-component-issues-on-site-editor.md
@@ -1,16 +1,16 @@
 ---
-title: 'Editores de componentes de renderização no site'
+title: 'Problemas com o componente de renderização no editor de sites'
 id: 66gcFw8LwnL6WsvuXPRzFn
 status: PUBLISHED
 createdAt: 2022-04-19T19:41:08.520Z
-updatedAt: 2023-03-10T14:17:10.739Z
-publishedAt: 2023-03-10T14:17:10.739Z
+updatedAt: 2024-06-21T12:24:51.158Z
+publishedAt: 2024-06-21T12:24:51.158Z
 firstPublishedAt: 2022-04-19T19:41:09.223Z
 contentType: knownIssue
 productTeam: CMS
 author: 2mXZkbi0oi061KicTExNjo
 tag: CMS
-slug: editores-de-componentes-de-renderizacao-no-site
+slug: problemas-com-o-componente-de-renderizacao-no-editor-de-sites
 locale: pt
 kiStatus: Backlog
 internalReference: 415674
@@ -23,21 +23,28 @@ internalReference: 415674
 </div>
 
 
-Este comportamento ocorre de forma intermitente, às vezes os componentes não são renderizados e às vezes é renderizado duas vezes com base em cliques na página.
+Devido à quantidade de informações na página, o editor do site pode ter problemas ao renderizar blocos. Esse comportamento ocorre de forma intermitente, às vezes os componentes não são renderizados e às vezes são renderizados duas vezes. Pode acontecer de nenhum bloco aparecer no editor do site:
+ ![](https://vtexhelp.zendesk.com/attachments/token/miNCNkBPcmbXcVHmb9f5HWxIS/?name=image.png)
 
+Ou pode acontecer com menos blocos.
 
-##
+Também pode ocorrer um atraso após salvar um novo conteúdo. O conteúdo é salvo, mas a tela continua carregando:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/BwlA7jzWiWCxYMLOGxMb0N84N/?name=image.png)
 
 ## Simulação
 
 
-Tente editar o Site Editor, às vezes ele não será renderizado e às vezes alguns blocos serão renderizados duas vezes.
+1 - Tente editar o Site Editor, às vezes ele não será renderizado e, às vezes, alguns blocos serão renderizados duas vezes.
+
+2 - Tente salvar uma alteração de conteúdo, o conteúdo é salvo, mas a tela continua carregando
 
 
-##
 
 ## Workaround
 
 
-Não há nenhuma solução de trabalho conhecida.
+Nenhuma solução alternativa conhecida está disponível.
+
+
 
diff --git a/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md b/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md
new file mode 100644
index 000000000..122336871
--- /dev/null
+++ b/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md
@@ -0,0 +1,43 @@
+---
+title: 'Substituição de pedidos por outro canal de vendas'
+id: 2gShXcwLLHu7R8JyPjP0W6
+status: PUBLISHED
+createdAt: 2024-02-16T13:02:17.686Z
+updatedAt: 2024-02-16T13:05:20.998Z
+publishedAt: 2024-02-16T13:05:20.998Z
+firstPublishedAt: 2024-02-16T13:02:18.609Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: substituicao-de-pedidos-por-outro-canal-de-vendas
+locale: pt
+kiStatus: Backlog
+internalReference: 982965
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Identificamos que não é possível substituir uma SKU no pedido se o canal de vendas (SC), igual a 1, não estiver disponível para a conta.
+
+Por exemplo, a conta A não tem canal de vendas=1, apenas SC=2, na solicitação de substituição do pedido estamos enviando canal de vendas=1 e não 2.
+
+## Simulação
+
+
+A conta A não tem canal de vendas=1, apenas SC=2, na solicitação de substituição de pedido, quando eles solicitam a substituição de uma SKU, estamos enviando o canal de vendas=1 e não o 2, portanto, não é possível realizar a substituição
+
+## Workaround
+
+
+N/A.
+
+
+
+
+
diff --git a/docs/known-issues/pt/replicated-pending-payment-emails.md b/docs/known-issues/pt/replicated-pending-payment-emails.md
index 50ca36774..25f6ca5cb 100644
--- a/docs/known-issues/pt/replicated-pending-payment-emails.md
+++ b/docs/known-issues/pt/replicated-pending-payment-emails.md
@@ -3,8 +3,8 @@ title: 'E-mails de Pagamento Pendente Replicado'
 id: 6ibJCSrep1aWEKi1DRTLDv
 status: PUBLISHED
 createdAt: 2022-05-18T18:30:57.906Z
-updatedAt: 2022-11-25T22:02:18.499Z
-publishedAt: 2022-11-25T22:02:18.499Z
+updatedAt: 2024-02-16T20:29:35.766Z
+publishedAt: 2024-02-16T20:29:35.766Z
 firstPublishedAt: 2022-05-18T18:30:58.383Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: emails-de-pagamento-pendente-replicado
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 348932
 ---
 
diff --git a/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md b/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md
new file mode 100644
index 000000000..1289cb7ed
--- /dev/null
+++ b/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md
@@ -0,0 +1,41 @@
+---
+title: 'O roteamento de solicitações é inconsistente ao executar testes A/B'
+id: 5ukS8DTwmWsM0fNWQLYFQ1
+status: PUBLISHED
+createdAt: 2023-11-08T21:42:53.184Z
+updatedAt: 2023-11-08T21:45:26.642Z
+publishedAt: 2023-11-08T21:45:26.642Z
+firstPublishedAt: 2023-11-08T21:42:53.723Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-roteamento-de-solicitacoes-e-inconsistente-ao-executar-testes-ab
+locale: pt
+kiStatus: Backlog
+internalReference: 931246
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+As solicitações HTTP de navegação da loja não respeitam o cookie de seleção de espaço de trabalho durante a sessão. Na verdade, durante uma única sessão, um usuário pode receber respostas de todos os espaços de trabalho que estão sendo testados.
+
+## Simulação
+
+1. Crie um teste A/B em sua loja usando o VTEX IO CLI
+2. Abra a guia "Application" (Aplicativo) no Chrome DevTools (ou equivalente em seu navegador)
+    1. Navegue pela loja e limpe o cookie `VtexWorkspace` após cada clique
+    2. Você deverá ver os valores mudarem eventualmente, mesmo que o cookie da sessão não tenha sido alterado.
+3. Abra a guia "Network" (Rede) no Chrome DevTools (ou equivalente em seu navegador)
+    1. Navegue pela loja e observe as solicitações HTTP que são feitas
+    2. Você deve ver que a string de consulta `workspace` é definida com valores diferentes durante toda a sessão
+
+## Workaround
+
+Não há nenhuma solução alternativa disponível. Os testes A/B não são recomendados e seus resultados não devem ser considerados corretos até que esse problema conhecido seja corrigido.
+
+
diff --git a/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md b/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md
index 7ea19e6a6..4c1145f0e 100644
--- a/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md
+++ b/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md
@@ -1,10 +1,10 @@
 ---
 title: 'Estoque reservado em pedidos faturados'
 id: TfDOKEybi6eSAEoCEEAqg
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-13T18:43:58.606Z
-updatedAt: 2022-12-22T14:51:09.663Z
-publishedAt: 2022-12-22T14:51:09.663Z
+updatedAt: 2023-10-17T15:29:19.908Z
+publishedAt: 
 firstPublishedAt: 2017-06-14T00:07:07.051Z
 contentType: knownIssue
 productTeam: Post-purchase
diff --git a/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md b/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
new file mode 100644
index 000000000..cee827f55
--- /dev/null
+++ b/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
@@ -0,0 +1,42 @@
+---
+title: 'Itens retornados com o mesmo SkuId em matrizes UniqueId diferentes não estão visíveis corretamente'
+id: 65uUpH4uSicaDzruCIBaTq
+status: PUBLISHED
+createdAt: 2024-06-14T20:48:37.328Z
+updatedAt: 2024-06-14T20:48:38.207Z
+publishedAt: 2024-06-14T20:48:38.207Z
+firstPublishedAt: 2024-06-14T20:48:38.207Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: itens-retornados-com-o-mesmo-skuid-em-matrizes-uniqueid-diferentes-nao-estao-visiveis-corretamente
+locale: pt
+kiStatus: Backlog
+internalReference: 1050294
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+## Simulação
+
+
+Crie um pedido com mais de uma quantidade de itens, criando um pedido com mais de uma matriz de itens com o mesmo skuid. Faturar o pedido e, nas páginas de retorno, será possível ver que o item não tem informações sobre as diferenças entre cada um deles.
+
+
+
+## Workaround
+
+
+Não há solução para isso.
+
+
+
+
+
diff --git a/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md b/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
index 6d2b71c4f..4c271a0ad 100644
--- a/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
+++ b/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
@@ -3,8 +3,8 @@ title: 'O valor do prêmio não foi adicionado ou foi adicionado um valor difere
 id: 3i9TwGKpYOkwnHUXDON9V7
 status: PUBLISHED
 createdAt: 2023-06-14T16:06:37.154Z
-updatedAt: 2023-06-14T16:06:37.696Z
-publishedAt: 2023-06-14T16:06:37.696Z
+updatedAt: 2023-06-27T12:44:59.727Z
+publishedAt: 2023-06-27T12:44:59.727Z
 firstPublishedAt: 2023-06-14T16:06:37.696Z
 contentType: knownIssue
 productTeam: Checkout
@@ -23,20 +23,22 @@ internalReference: 844079
 </div>
 
 
-O valor do prêmio pode não ser ou ter um valor diferente adicionado ao cartão-presente do comprador.
+O valor do prêmio pode não ser ou ter um valor diferente adicionado ao cartão-presente do comprador quando a promoção estiver configurada para aplicar o valor do prêmio quando o status do pedido mudar para pagamento aprovado.
 
 ## Simulação
 
 
 
-- Crie uma promoção de valor de prêmio;
+- Crie uma promoção de valor de prêmio para aplicar quando o status do pedido mudar para pagamento aprovado;
 - Conclua uma compra;
 - Verifique as interações em Detalhes do pedido no admin; não haverá a mensagem "_XX adicionado ao programa de fidelidade do usuário_
 
 ## Workaround
 
 
-Selecione via admin a opção "Gift Cards" no menu, selecione o cartão-presente do comprador e clique em "Statement" (Declaração) na coluna Actions (Ações) para adicionar o valor adequado.
+
+- Selecione via admin a opção "Gift Cards" (Cartões-presente) no menu, selecione o cartão-presente do comprador e clique em "Statement" (Declaração) na coluna Actions (Ações) para adicionar o valor adequado;
+- Configure a promoção do valor do prêmio para ser aplicada quando o status do pedido mudar para faturado.
 
 
 
diff --git a/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md b/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md
new file mode 100644
index 000000000..3a671d5c1
--- /dev/null
+++ b/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md
@@ -0,0 +1,57 @@
+---
+title: 'O reescritor não está recebendo atualizações de URL'
+id: 4c3S9s57SzQCv8zv4L77Fu
+status: PUBLISHED
+createdAt: 2024-07-16T19:24:56.813Z
+updatedAt: 2024-07-16T19:24:57.773Z
+publishedAt: 2024-07-16T19:24:57.773Z
+firstPublishedAt: 2024-07-16T19:24:57.773Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-reescritor-nao-esta-recebendo-atualizacoes-de-url
+locale: pt
+kiStatus: Backlog
+internalReference: 1066527
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando uma URL é alterada/excluída no catálogo, o reescritor não recebe essa alteração. Como o reescritor não é notificado sobre isso, o URL ainda está apontando para o tipo errado, o que também pode levar a problemas no IS.
+
+Isso também pode acontecer ao criar novas rotas de categoria/subcategoria no catálogo. Às vezes, o reescritor precisará que você execute a consulta bootstrap para receber essas rotas.
+
+## Simulação
+
+
+Tente excluir uma marca existente do catálogo
+Execute a mutação para ver como esse caminho está sendo recebido no reescritor
+
+    {internal{ get(path:"/brand"){ from declarer query disableSitemapEntry }}}
+
+Se você procurar essa marca na vitrine, ela ainda estará apontando para um `map=b`
+
+Você também pode verificar como esse caminho está sendo retornado no pageType; se for um fullText, o pageType foi atualizado e o rewriter não
+
+## Workaround
+
+
+Tente excluir a rota manualmente do reescritor:
+
+      mutation{ internal{ delete(path:"/path"){ from id resolveAs } }}
+
+
+Tente executar a consulta bootstrap para atualizar o reescritor:
+
+    {bootstrap { brands categories}}
+
+
+
+
+
diff --git a/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md b/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
new file mode 100644
index 000000000..2fa3534d1
--- /dev/null
+++ b/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
@@ -0,0 +1,52 @@
+---
+title: 'O modo de arredondamento de teto/piso não está funcionando corretamente entre itens com multiplicador de unidade diferente de 1'
+id: 5KzOM5kEp8QpkBTX7hdil1
+status: PUBLISHED
+createdAt: 2024-01-18T17:53:08.668Z
+updatedAt: 2024-01-18T17:53:09.229Z
+publishedAt: 2024-01-18T17:53:09.229Z
+firstPublishedAt: 2024-01-18T17:53:09.229Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: o-modo-de-arredondamento-de-tetopiso-nao-esta-funcionando-corretamente-entre-itens-com-multiplicador-de-unidade-diferente-de-1
+locale: pt
+kiStatus: Backlog
+internalReference: 968349
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+É possível definir, por meio de uma tarefa para a equipe de produtos, a alteração da forma como o valor do desconto é arredondado no carrinho.
+Em um cenário em que a conta está usando um modo de arredondamento de teto ou piso, esse arredondamento não funcionará corretamente com itens com unitmultiplier diferente de 1.
+
+Isso ocorre porque o unitMultiplier desse item é 100,0. Quando o RnB arredonda o valor do desconto para o checkout, ele arredonda o preço unitário. Portanto, ele pega o valor de uma unidade pequena e o arredonda para cima. Em seguida, ele pega o desconto total, divide-o pela quantidade vezes o unitMultiplier e arredonda-o para duas casas decimais.
+Como o RnB leva em conta apenas duas casas decimais, ele arredonda para 0,01 ou 0,02.
+
+## Simulação
+
+
+
+Exemplo:
+Desconto total: -3.96
+Desconto unitário = -3,96 / (2*100) = -0,0198
+
+Então, qual item receberá 0,0198% do desconto, em vez de 3,96%
+
+## Workaround
+
+
+
+Uma solução válida seria voltar a definir no roundingMode, para que o problema pare de ocorrer.
+
+
+
+
+
diff --git a/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md b/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
new file mode 100644
index 000000000..8ede44a56
--- /dev/null
+++ b/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
@@ -0,0 +1,42 @@
+---
+title: 'A priorização de rotas não oferece a melhor opção em termos de quantidade de pacotes e itens'
+id: 4verafDuoFnC5vGDI4UV1m
+status: PUBLISHED
+createdAt: 2023-10-30T18:28:52.771Z
+updatedAt: 2023-10-30T18:28:53.648Z
+publishedAt: 2023-10-30T18:28:53.648Z
+firstPublishedAt: 2023-10-30T18:28:53.648Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: a-priorizacao-de-rotas-nao-oferece-a-melhor-opcao-em-termos-de-quantidade-de-pacotes-e-itens
+locale: pt
+kiStatus: Backlog
+internalReference: 927747
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na logística, o primeiro critério de desempate quando o sistema está escolhendo a rota (armazém + doca + política de remessa) está relacionado ao número de pacotes necessários para essa rota específica; menos pacotes significa que a rota deve ser melhor.
+No entanto, o sistema não pode considerar a relação entre o número de pacotes e o número de itens em cada pacote.
+Isso significa que, por exemplo, um pedido com 2 pacotes e 2 itens pode ser priorizado quando houver uma rota disponível que entregue apenas 1 pacote com todos os itens.
+
+## Simulação
+
+
+Não há uma maneira fácil de simular esse cenário, pois ele é muito específico e o sistema pode se comportar de maneira diferente em cada caso, mas temos um exemplo bem claro em que o sistema escolhe o SLA que divide o pacote em 2 em vez de oferecer o SLA com apenas 1 pacote
+
+## Workaround
+
+
+O comerciante pode separar a política de armazém + doca + envio, com nome de método de envio diferente, para não depender da priorização da rota.
+
+
+
+
diff --git a/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
new file mode 100644
index 000000000..94f422ef2
--- /dev/null
+++ b/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -0,0 +1,49 @@
+---
+title: 'O canal de vendas configurado nas Configurações B2B não é atribuído após a aprovação das Organizações'
+id: 7kxMtk2YHJdk5uPdj5wBs5
+status: PUBLISHED
+createdAt: 2023-07-21T20:03:44.671Z
+updatedAt: 2023-07-21T20:03:45.295Z
+publishedAt: 2023-07-21T20:03:45.295Z
+firstPublishedAt: 2023-07-21T20:03:45.295Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: o-canal-de-vendas-configurado-nas-configuracoes-b2b-nao-e-atribuido-apos-a-aprovacao-das-organizacoes
+locale: pt
+kiStatus: Backlog
+internalReference: 866933
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O canal de vendas configurado nas configurações de organizações B2B não é salvo nos detalhes da organização.
+
+## Simulação
+
+
+
+- Configure um canal de vendas padrão nas configurações de organizações B2B;
+- Criar uma solicitação de organização;
+- Aprovar a solicitação da organização;
+- Verifique os detalhes da organização; ela não terá nenhum canal de vendas atribuído
+
+## Workaround
+
+
+
+- Atribua o canal de vendas à organização por meio do administrador;
+- Crie um acionador para o esquema da entidade da organização:
+
+    "v-triggers": [{"name": "define-salesChannel-default", "active": true, "condition": "salesChannel is null", "action": { "type": "save" (salvar), "dataEntity" (entidade de dados): "organizations", "json": { "id": "{!id}", "salesChannel": "{adicione aqui o salesChannelId definido nas configurações de organizações B2B}" } } }]
+
+
+
+
+
diff --git a/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md b/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md
new file mode 100644
index 000000000..467e5b216
--- /dev/null
+++ b/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md
@@ -0,0 +1,46 @@
+---
+title: 'Falha na validação do esquema para tipos personalizados no Headless CMS'
+id: 2dcDsFQkqbNqJZXEzztQ11
+status: PUBLISHED
+createdAt: 2023-09-19T21:43:59.145Z
+updatedAt: 2023-09-19T21:43:59.945Z
+publishedAt: 2023-09-19T21:43:59.945Z
+firstPublishedAt: 2023-09-19T21:43:59.945Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: falha-na-validacao-do-esquema-para-tipos-personalizados-no-headless-cms
+locale: pt
+kiStatus: Backlog
+internalReference: 903687
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Temos falhas nas validações de esquema em campos obrigatórios sem valor padrão no Headless CMS para tipos de página personalizados, a biblioteca que usamos está considerando a falha, mas os campos obrigatórios são preenchidos corretamente
+
+## Simulação
+
+
+
+Criar uma estrutura de esquema para uma página específica com um campo obrigatório e não colocar um valor padrão para esse campo obrigatório
+
+
+    ... "required": ["field1"],"properties": {"field1": { "title": "Field" (Campo), "type" (Tipo): "string", "description": "Alguma descrição" }}...
+
+## Workaround
+
+
+Coloque um valor padrão nos campos obrigatórios
+
+
+
+
+
diff --git a/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md b/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md
new file mode 100644
index 000000000..47a5059ed
--- /dev/null
+++ b/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md
@@ -0,0 +1,45 @@
+---
+title: 'Problema de rolagem ao aplicar zoom após a renderização da página de pesquisa'
+id: 2FcX9UNvBOanE3EhH9q0DT
+status: PUBLISHED
+createdAt: 2024-02-08T16:51:28.278Z
+updatedAt: 2024-03-06T14:17:07.639Z
+publishedAt: 2024-03-06T14:17:07.639Z
+firstPublishedAt: 2024-02-08T16:51:29.011Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: problema-de-rolagem-ao-aplicar-zoom-apos-a-renderizacao-da-pagina-de-pesquisa
+locale: pt
+kiStatus: Fixed
+internalReference: 979464
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao alterar a janela de visualização ou aumentar o zoom da tela nas páginas de pesquisa após o primeiro carregamento, não é permitido rolar a página corretamente.
+
+## Simulação
+
+
+
+
+- Carregue sua página de pesquisa
+- Altere o zoom do seu navegador
+- Tentar rolar a págin
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md b/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
new file mode 100644
index 000000000..36966e36b
--- /dev/null
+++ b/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
@@ -0,0 +1,48 @@
+---
+title: 'Problemas de rolagem ao deslizar no celular na visualização rápida quando há um layout de controle deslizante em segundo plano'
+id: 5B7g5Wt1iyh0BLwIUprO2C
+status: PUBLISHED
+createdAt: 2024-02-20T17:58:53.942Z
+updatedAt: 2024-02-20T17:58:54.806Z
+publishedAt: 2024-02-20T17:58:54.806Z
+firstPublishedAt: 2024-02-20T17:58:54.806Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: problemas-de-rolagem-ao-deslizar-no-celular-na-visualizacao-rapida-quando-ha-um-layout-de-controle-deslizante-em-segundo-plano
+locale: pt
+kiStatus: Backlog
+internalReference: 985097
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao deslizar a imagem de um produto na visualização rápida em dispositivos móveis quando há um layout de controle deslizante em segundo plano, ambos os controles deslizantes são movidos para o próximo em vez de apenas a imagem na visualização rápida
+
+## Simulação
+
+
+
+
+- Abra uma visualização rápida no celular com um layout de controle deslizante no plano de fundo
+- Tente deslizar a imagem do produto
+
+O comportamento esperado é que não apenas a imagem do produto da visualização rápida seja alterada, mas também os produtos no layout/prateleira do controle deslizante
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/search-analytics-duplicated-events.md b/docs/known-issues/pt/search-analytics-duplicated-events.md
new file mode 100644
index 000000000..52093dfec
--- /dev/null
+++ b/docs/known-issues/pt/search-analytics-duplicated-events.md
@@ -0,0 +1,60 @@
+---
+title: 'Pesquisar eventos duplicados do Analytics'
+id: 48h3ObR7qqRHvU36weCvjC
+status: PUBLISHED
+createdAt: 2023-03-15T19:40:23.229Z
+updatedAt: 2023-09-20T18:49:19.673Z
+publishedAt: 2023-09-20T18:49:19.673Z
+firstPublishedAt: 2023-03-15T19:40:23.835Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: pesquisar-eventos-duplicados-do-analytics
+locale: pt
+kiStatus: Fixed
+internalReference: 771986
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns eventos dos relatórios da Pesquisa Inteligente estão duplicados, o que pode afetar a exibição de análise no módulo de administração de pesquisa.
+
+
+#### FAQ
+
+**1. Isso afeta todos os eventos da VTEX (por exemplo, Request Capture, painéis da página inicial do administrador, etc.)?
+
+Não, as análises do Intelligent Search são calculadas de forma diferente e independente dessas métricas e eventos por enquanto. Esse problema afeta apenas a página Search > Analytics.
+
+**2. Todas as métricas estão sendo calculadas em excesso?
+
+Sim, todas as métricas brutas mostradas na página Search > Analytics estão sendo computadas em excesso no momento.
+
+São elas: contagem de pesquisas, cliques em um termo, cliques exclusivos em um termo, contagem de transações após a pesquisa de um termo e receita gerada por essas transações, taxa de cliques e conversão.
+
+**3. Os dados de "Exportar para CSV" também foram afetados?
+
+Sim, os dados exportados para CSV também são afetados pelos dados supercomputados.
+
+**4. Isso afeta o algoritmo Search Relevance e os resultados da pesquisa?
+
+Não, embora o algoritmo de relevância da pesquisa também use os eventos de análise para calcular a pontuação de popularidade do produto, ele não usa as métricas agregadas.
+
+## Simulação
+
+
+O cenário pode ser visto ao verificar a página de administração de pesquisa para os relatórios/análises.
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md b/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
new file mode 100644
index 000000000..1632028ff
--- /dev/null
+++ b/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
@@ -0,0 +1,46 @@
+---
+title: 'As análises de pesquisa relatam divergências entre versões com/sem métricas de funil'
+id: 33lXZb4Nr2NOPgW2Cth9ry
+status: PUBLISHED
+createdAt: 2024-02-09T19:01:45.952Z
+updatedAt: 2024-02-09T19:01:46.857Z
+publishedAt: 2024-02-09T19:01:46.857Z
+firstPublishedAt: 2024-02-09T19:01:46.857Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: as-analises-de-pesquisa-relatam-divergencias-entre-versoes-comsem-metricas-de-funil
+locale: pt
+kiStatus: Backlog
+internalReference: 980297
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O relatório de análise de pesquisa exportado como CSV pode divergir entre sua versão com métricas de funil e sua versão sem elas.
+
+O relatório normal (sem métricas de funil) é exportado usando o mesmo método que os dados apresentados na própria página, mas a exportação com métricas de funil usa um método diferente para computar dados adicionais, o que às vezes pode resultar em informações diferentes.
+
+## Simulação
+
+
+Exporte as duas versões do relatório para o mesmo período e compare os termos de pesquisa listados e as primeiras colunas entre eles.
+
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md b/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
index f3af29e7d..92d4c9f84 100644
--- a/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
+++ b/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
@@ -3,8 +3,8 @@ title: 'Pesquisar API não retornando mostrarIfNotAvailable=true SKUs for &fq=sp
 id: 7p26JmS8pyPA8H0b1QJHyU
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:27.329Z
-updatedAt: 2022-11-25T22:10:15.920Z
-publishedAt: 2022-11-25T22:10:15.920Z
+updatedAt: 2024-02-16T20:29:43.164Z
+publishedAt: 2024-02-16T20:29:43.164Z
 firstPublishedAt: 2022-06-28T16:55:28.384Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: pesquisar-api-nao-retornando-mostrarifnotavailabletrue-skus-for-fqspecificationfilter-queries
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 336896
 ---
 
diff --git a/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md b/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
index c7d310ca2..0981fda61 100644
--- a/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
+++ b/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
@@ -3,8 +3,8 @@ title: 'Busca API que não funciona corretamente após o login no uso do Call Ce
 id: 3YxbokaDhYnthzy1dc5VHs
 status: PUBLISHED
 createdAt: 2022-01-21T18:24:15.316Z
-updatedAt: 2022-11-25T22:11:01.363Z
-publishedAt: 2022-11-25T22:11:01.363Z
+updatedAt: 2024-02-16T20:29:54.425Z
+publishedAt: 2024-02-16T20:29:54.425Z
 firstPublishedAt: 2022-03-16T16:50:03.972Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: busca-api-que-nao-funciona-corretamente-apos-o-login-no-uso-do-call-center-operator
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 304586
 ---
 
diff --git a/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md b/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
new file mode 100644
index 000000000..8e89114d7
--- /dev/null
+++ b/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
@@ -0,0 +1,40 @@
+---
+title: 'O preenchimento automático da pesquisa fornece um URL desatualizado após a navegação pelas sugestões'
+id: 168oT3vpuAcRdZbE7sahtF
+status: PUBLISHED
+createdAt: 2024-01-19T01:28:08.775Z
+updatedAt: 2024-01-19T01:28:09.627Z
+publishedAt: 2024-01-19T01:28:09.627Z
+firstPublishedAt: 2024-01-19T01:28:09.627Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: o-preenchimento-automatico-da-pesquisa-fornece-um-url-desatualizado-apos-a-navegacao-pelas-sugestoes
+locale: pt
+kiStatus: Backlog
+internalReference: 968604
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No componente "barra de pesquisa" com "autocomplete-result-list.v2", passar o mouse sobre as sugestões de pesquisa também altera os produtos sugeridos, bem como o texto de "ver todos os {n} produtos" para mencionar a pesquisa selecionada, mas o hiperlink de "ver todos" segue o termo de pesquisa original em vez do selecionado.
+
+## Simulação
+
+
+
+- pesquisar um termo parcial
+- passe o mouse sobre os termos sugeridos
+- clique em "ver todos os produtos
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
new file mode 100644
index 000000000..162341f02
--- /dev/null
+++ b/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -0,0 +1,50 @@
+---
+title: 'Os banners de pesquisa não seguem o operador "AND" para condições de acionamento'
+id: 4nQLt5q3Mz2DxvBIyZknXj
+status: PUBLISHED
+createdAt: 2024-06-20T21:17:46.485Z
+updatedAt: 2024-06-20T21:17:47.308Z
+publishedAt: 2024-06-20T21:17:47.308Z
+firstPublishedAt: 2024-06-20T21:17:47.308Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: os-banners-de-pesquisa-nao-seguem-o-operador-and-para-condicoes-de-acionamento
+locale: pt
+kiStatus: Backlog
+internalReference: 1053614
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As condições para banners de pesquisa (gerenciados por meio de "/admin/search/v4/banners/") não são compatíveis com o operador "AND", conforme apresentado em suas regras de acionamento. A interface do usuário está errada, e o operador se comporta como "OR" de forma fixa.
+
+Qualquer uma das condições preenchidas ali será suficiente para apresentar o banner na página (PLP).
+
+Lembre-se de que a configuração de um departamento ali (nível de categoria 1) aplicará o banner em qualquer uma de suas subcategorias, pois isso faz parte do caminho completo da categoria.
+
+## Simulação
+
+
+Crie um banner com as seguintes regras de acionamento:
+
+- onde "departamento" é "eletrodomésticos"
+- **e**"categoria" é "refrigeradores"
+
+O banner não será restrito ao caminho completo da categoria "/appliances/refrigerators?map=c,c". Ele será aplicado no departamento e em suas subcategorias, e em qualquer categoria chamada "refrigeradores", mesmo que não faça parte desse departamento específico
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md b/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md
index 1056c5696..25aebef11 100644
--- a/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md
+++ b/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md
@@ -1,36 +1,47 @@
 ---
-title: 'Search by EAN not working on Received Skus'
+title: 'A pesquisa por EAN não está funcionando em Skus recebidos'
 id: PKdNXxjVPFbJbVBSTFvep
-status: DRAFT
+status: PUBLISHED
 createdAt: 2022-01-26T19:24:01.975Z
-updatedAt: 2022-01-31T18:31:27.337Z
-publishedAt: 
+updatedAt: 2024-02-16T20:24:48.686Z
+publishedAt: 2024-02-16T20:24:48.686Z
 firstPublishedAt: 2022-01-26T19:25:13.218Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
-tag: 
-slug: search-by-ean-not-working-on-received-skus
+tag: Marketplace
+slug: a-pesquisa-por-ean-nao-esta-funcionando-em-skus-recebidos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 510907
 ---
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
+
+O recurso de pesquisa Received Skus permite que o marketplace pesquise um produto ou sku pelos seguintes critérios:
+- Nome do Sku;
+- ID;
+- EAN.
+
+Atualmente, a pesquisa de EAN não está se comportando como esperado, não fornecendo nenhum resultado.
+
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+Tente encontrar um sku pesquisando-o usando seu EAN.
+O resultado deve ser a sku em vez de uma área em branco
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+
+Use os outros critérios de pesquisa, como Sku Name ou ID.
+
+
+
+
 
diff --git a/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md b/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
new file mode 100644
index 000000000..80629e5fb
--- /dev/null
+++ b/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
@@ -0,0 +1,53 @@
+---
+title: 'A pesquisa não tem produtos se o nome do vendedor 1 no Gerenciamento de Vendedores for diferente do nome comercial no Gerenciamento de Contas ao usar o B2B Suite'
+id: 7a3bwqRmeSClHMoFmyIY2a
+status: PUBLISHED
+createdAt: 2023-12-01T20:06:13.492Z
+updatedAt: 2023-12-01T20:15:07.659Z
+publishedAt: 2023-12-01T20:15:07.659Z
+firstPublishedAt: 2023-12-01T20:06:14.083Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: a-pesquisa-nao-tem-produtos-se-o-nome-do-vendedor-1-no-gerenciamento-de-vendedores-for-diferente-do-nome-comercial-no-gerenciamento-de-contas-ao-usar-o-b2b-suite
+locale: pt
+kiStatus: Backlog
+internalReference: 946391
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As organizações B2B usam os nomes dos vendedores do Gerenciamento de vendedores. Se uma organização tiver o vendedor 1 atribuído, o nome salvo será do Gerenciamento de vendedores, mas nenhum produto poderá ser mostrado na pesquisa se for diferente do nome comercial no Gerenciamento de contas.
+
+## Simulação
+
+
+
+- Tenha uma conta com o vendedor 1 nomeado no Seller Management diferente do nome comercial no Account Management;
+- Crie uma organização B2B e atribua o vendedor 1;
+- Faça login na conta; nenhum produto é exibido
+
+## Workaround
+
+
+
+- Acesse o GraphQL IDE e selecione vtex.b2b-organizations-graphql;
+- Use a consulta abaixo para obter todos os detalhes da organização:
+
+    { getOrganizationById(id: "insira aqui o id da organização"){ id name tradeName status collections{ id name } paymentTerms{ id name } priceTables customFields{ name type value dropdownValues{ value label } useOnRegistration } salesChannel sellers { id name } }}
+
+- Envie uma mutação para atualizar o nome do vendedor 1 usando as informações recuperadas acima:
+
+    mutation { updateOrganization( id: "" name: "" tradeName: "" status: "active" collections: [{ id: "" name: "" }] paymentTerms: [{ id: "" name: "" }] priceTables: [""] customFields: [] salesChannel: "" sellers: [{ id: "1", name: "trade name from Account Management" }] ){ id status message }}
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md b/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md
index 670796cbb..8bdfd1a04 100644
--- a/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md
+++ b/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md
@@ -3,8 +3,8 @@ title: 'Busca Filtro Navigator + Faixa de preço que produz resultados incorreto
 id: 6s4vJr6DVPLU9JlxIPWqhx
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.208Z
-updatedAt: 2022-11-25T22:10:01.089Z
-publishedAt: 2022-11-25T22:10:01.089Z
+updatedAt: 2024-02-16T20:24:11.551Z
+publishedAt: 2024-02-16T20:24:11.551Z
 firstPublishedAt: 2022-06-28T16:55:53.927Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: busca-filtro-navigator-faixa-de-preco-que-produz-resultados-incorretos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 504992
 ---
 
diff --git a/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md b/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md
new file mode 100644
index 000000000..a72bdf3d1
--- /dev/null
+++ b/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md
@@ -0,0 +1,48 @@
+---
+title: 'O Search Resolver aplica traduções de mensagens sobre conteúdo já traduzido'
+id: 7OIKmmhO3Pa2z0pIU33kY
+status: PUBLISHED
+createdAt: 2023-07-20T15:28:57.078Z
+updatedAt: 2024-06-13T20:51:17.597Z
+publishedAt: 2024-06-13T20:51:17.597Z
+firstPublishedAt: 2023-07-20T15:28:57.934Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: o-search-resolver-aplica-traducoes-de-mensagens-sobre-conteudo-ja-traduzido
+locale: pt
+kiStatus: Backlog
+internalReference: 865918
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O Search Resolver (camada GraphQL para Pesquisa Inteligente) solicita traduções do serviço de Mensagens, mesmo para lojas de um único idioma ou conteúdo já traduzido em uma loja de vários idiomas.
+
+Na prática, essas traduções são feitas sobre os mesmos idiomas "de" e "para", mas se a loja tiver o recurso de tradução automática ativado, a string poderá mudar para algo inesperado.
+
+Isso afeta especialmente as cadeias de caracteres com várias palavras que podem ser consideradas de idiomas diferentes, como palavras em inglês no nome de um produto que é majoritariamente em francês e, potencialmente, datas (entre as notações "dd/mm/aaaa" e "mm/dd/aaaa").
+
+## Simulação
+
+
+
+- Traduza qualquer conteúdo do catálogo da loja para um idioma diferente do padrão;
+- Verifique se ainda há pelo menos uma palavra em um idioma diferente do traduzido;
+- Verifique a vitrine da loja; ela não corresponderá à tradução
+
+## Workaround
+
+
+
+- Desative a tradução automática;
+- Crie traduções para esses conteúdos usando o mesmo idioma de "from" e "to", por exemplo, traduzindo-o de "fr-FR" para "fr-FR".
+
+
+
diff --git a/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md b/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
new file mode 100644
index 000000000..628c1e6cf
--- /dev/null
+++ b/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
@@ -0,0 +1,63 @@
+---
+title: 'A pesquisa não retorna o documento quando o valor contém um símbolo + (mais).'
+id: 7oWiN8Esh9iKy8144Tpglx
+status: PUBLISHED
+createdAt: 2024-07-08T18:52:21.794Z
+updatedAt: 2024-07-08T21:46:18.259Z
+publishedAt: 2024-07-08T21:46:18.259Z
+firstPublishedAt: 2024-07-08T18:52:22.908Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: a-pesquisa-nao-retorna-o-documento-quando-o-valor-contem-um-simbolo-mais
+locale: pt
+kiStatus: No Fix
+internalReference: 828170
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao pesquisar um documento usando um valor de campo que inclui o símbolo "+", a pesquisa não retorna o documento. Isso acontece porque o símbolo "+" é interpretado incorretamente, o que faz com que o valor da pesquisa não corresponda ao valor existente.
+Esse problema ocorre tanto na API quanto no CRM_
+
+## Simulação
+
+
+
+1. Use a API de pesquisa para consultar um campo que inclua um símbolo "+".
+2. A pesquisa retornará uma matriz vazia. Exemplo:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=+5512345678901&_fields=id,userId,email,homePhone,firstName
+
+
+Na interface do usuário do CRM:
+Se você pesquisar um e-mail que contenha o símbolo "+", será retornado um erro.
+
+    Ocorreu um erro inesperado. Tente novamente. Se o problema persistir, entre em contato com o suporte.
+
+
+
+
+## Workaround
+
+
+Há duas maneiras de lidar com esse problema:
+Codificar o símbolo "+" para "%2B", de modo que a consulta de pesquisa se torne:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=%2B5512345678901&_fields=id,userId,email,homePhone,firstName
+
+
+Use o símbolo "*" como um curinga, o que permitirá que a pesquisa corresponda a qualquer caractere antes do valor especificado:
+
+    https://{accountName}.environment.com.br/api/dataentities/{entity}/search?_where=homePhone=*12345678901&_fields=id,userId,email,homePhone,firstName
+
+Esse problema surge ao pesquisar documentos usando valores de campo que incluem o símbolo "+". A API de pesquisa não interpreta corretamente o símbolo "+", fazendo com que a pesquisa falhe por não corresponder aos valores existentes. Esse problema não se limita ao campo "homePhone", mas pode ocorrer com outros campos, como e-mail, que podem incluir caracteres especiais.
+Para contornar esse problema, você pode codificar o símbolo "+" como "%2B" na consulta de pesquisa ou usar o símbolo "*" como curinga para garantir que a pesquisa recupere os documentos corretos.
+
+
diff --git a/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md b/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md
index e37412f09..58bafd895 100644
--- a/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md
+++ b/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md
@@ -1,16 +1,16 @@
 ---
-title: 'Cookie de segmento atualizado somente depois de atualizar a página'
+title: 'Cookie de segmento atualizado somente após a atualização da página'
 id: 3QBmp4D2tvIAxEzEy2LpNf
 status: PUBLISHED
 createdAt: 2022-11-01T16:33:05.698Z
-updatedAt: 2023-03-08T20:36:59.962Z
-publishedAt: 2023-03-08T20:36:59.962Z
+updatedAt: 2024-01-10T17:18:13.115Z
+publishedAt: 2024-01-10T17:18:13.115Z
 firstPublishedAt: 2022-11-01T16:33:06.403Z
 contentType: knownIssue
 productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
-slug: cookie-de-segmento-atualizado-somente-depois-de-atualizar-a-pagina
+slug: cookie-de-segmento-atualizado-somente-apos-a-atualizacao-da-pagina
 locale: pt
 kiStatus: Backlog
 internalReference: 647116
@@ -23,36 +23,32 @@ internalReference: 647116
 </div>
 
 
-Algumas características e componentes da VTEX podem usar os dados solicitados ao Cookie do Segmento para apresentar informações (como preço, dados de promoção, disponibilidade de SKU, etc.) na vitrine. Este cookie é armazenado no navegador do usuário quando a sessão é criada. Algumas vezes, principalmente em cenários dinâmicos onde é necessário fazer mudanças na frente onde aciona uma atualização do Segmento do Cookie, o próprio cookie perde alguns dados que é um comportamento em render-runtime que não aciona uma mudança de segmento no contexto
+Alguns recursos e componentes da VTEX podem usar dados solicitados do cookie de segmento para apresentar informações (como preço, dados de promoção, disponibilidade de SKU etc.) na vitrine. Esse cookie é armazenado no navegador do usuário quando a sessão é criada. Às vezes, principalmente em cenários dinâmicos em que é necessário fazer alterações na fachada, o que aciona uma atualização do Cookie Segment, o cookie em si perde alguns dados, o que é resultado de um comportamento no tempo de execução de renderização que não aciona a alteração do segmento no contexto
 
-Como recuperar informações sobre a sessão:
+Como recuperar informações da sessão:
 https://developers.vtex.com/vtex-rest-api/reference/getsession
 
-Você pode obter os dados do Cookie do segmento através do símbolo do segmento:
+Você pode obter os dados do cookie de segmento por meio do token de segmento:
 
 - Abra o console do navegador;
-- Decodificar a ficha de segmento apresentada no objeto de tempo de execução de renderização;
+- Decodifique o token de segmento apresentado no objeto de tempo de execução de renderização;
 - No console, execute:` atob(__RUNTIME__.segmentToken)`
  ![](https://vtexhelp.zendesk.com/attachments/token/wHuslnrutSh5W2CZS4FlHBm0d/?name=Captura+de+Tela+2022-09-23+a%CC%80s+14.09.57.png)
 
-
-##
-
 ## Simulação
 
 
 
-- Selecione uma loja que apresente informações com base nos dados de um Cookie de Segmento:
-- Ex.: Diferentes preços são mostrados com base na identificação do cliente - relacionados às tabelas de preços;
-- Obtenha os dados do Segmento de Cookie em diferentes cenários usando o aplicativo que recupera a identificação do usuário;
+- Selecione uma loja que apresente informações com base nos dados de um cookie de segmento:
+- Ex.: Preços diferentes são mostrados com base na identificação do cliente - relacionados a tabelas de preços;
+- Obtenha os dados do cookie de segmento em diferentes cenários usando o aplicativo que recupera a identificação do usuário;
 
 
-##
 
 ## Workaround
 
 
-Atualize a página
+Atualizar a página
 
 
 
diff --git a/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md b/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md
new file mode 100644
index 000000000..e101d0cbd
--- /dev/null
+++ b/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md
@@ -0,0 +1,51 @@
+---
+title: 'As atualizações da comissão do vendedor não indexam os skus vinculados'
+id: GNX6sFV0thQkMLWEwxya9
+status: PUBLISHED
+createdAt: 2023-08-31T14:44:39.162Z
+updatedAt: 2023-08-31T14:44:39.748Z
+publishedAt: 2023-08-31T14:44:39.748Z
+firstPublishedAt: 2023-08-31T14:44:39.748Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-atualizacoes-da-comissao-do-vendedor-nao-indexam-os-skus-vinculados
+locale: pt
+kiStatus: Backlog
+internalReference: 891162
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o comerciante atualiza a comissão do vendedor na interface do usuário de gerenciamento do vendedor, os skus vinculados relacionados a esse vendedor não são indexados automaticamente.
+
+Nosso sistema de checkout usa a API stockkeepingunitbyid para obter as informações atualizadas do sku.
+
+Nessa API, temos o objeto SkuSellers que contém as informações de comissão. Mas se o sku não for indexado, esse objeto ficará desatualizado.
+
+Isso faz com que o checkout obtenha o valor antigo da comissão.
+
+## Simulação
+
+
+
+1. Altere a comissão do vendedor na interface de gerenciamento do vendedor.
+2. Aguarde o tempo de cache, cerca de 10 minutos.
+3. Verifique se na simulação de checkout a comissão está desatualizada
+
+## Workaround
+
+
+Para evitar o fechamento de pedidos com o valor de comissão desatualizado, o comerciante pode indexar manualmente os skus afetados.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md b/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md
new file mode 100644
index 000000000..3edb77654
--- /dev/null
+++ b/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md
@@ -0,0 +1,51 @@
+---
+title: 'A criação de um grupo de vendedores não adiciona os vendedores selecionados'
+id: 5J14RCg9E4LzBcvJQyOAYy
+status: PUBLISHED
+createdAt: 2023-10-27T17:33:45.625Z
+updatedAt: 2024-01-26T16:54:12.089Z
+publishedAt: 2024-01-26T16:54:12.089Z
+firstPublishedAt: 2023-10-27T17:33:46.214Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: a-criacao-de-um-grupo-de-vendedores-nao-adiciona-os-vendedores-selecionados
+locale: pt
+kiStatus: Fixed
+internalReference: 926969
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O marketplace pode criar grupos com alguns vendedores na interface de gerenciamento do vendedor.
+ ![](https://vtexhelp.zendesk.com/attachments/token/Mi9PZxDSnInogb65PbJ3fEduu/?name=image.png)
+
+No entanto, ao adicionar um nome de grupo e vendedores nessa interface do usuário, somente o nome do grupo está sendo salvo. É exibida uma mensagem de erro:
+"Desculpe, algo deu errado ao adicionar os vendedores ao grupo XXX."
+ ![](https://vtexhelp.zendesk.com/attachments/token/Gd0FRbqKLDnCGFmIjuXIctxwX/?name=image.png)
+
+## Simulação
+
+
+
+1. Vá para a área Seller Management (Gerenciamento de vendedores) e clique em Manage groups (Gerenciar grupos);
+2. Clique em Add Group (Adicionar grupo) e adicione as informações, como nome e vendedores;
+3. Verifique se o grupo foi criado, mas sem nenhum vendedor.
+
+
+
+## Workaround
+
+
+Adicione os vendedores ao grupo manualmente mais tarde na interface do usuário "Seller Details" (Detalhes do vendedor)
+
+
+
+
+
diff --git a/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md b/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
new file mode 100644
index 000000000..0c663e8ad
--- /dev/null
+++ b/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
@@ -0,0 +1,47 @@
+---
+title: 'A condição da Promoção do Portal do Vendedor Preço mínimo do item não está funcionando como esperado'
+id: d0qJRHP3ngtNH5gwSPaNi
+status: PUBLISHED
+createdAt: 2023-10-31T20:42:03.072Z
+updatedAt: 2023-10-31T20:42:03.763Z
+publishedAt: 2023-10-31T20:42:03.763Z
+firstPublishedAt: 2023-10-31T20:42:03.763Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: a-condicao-da-promocao-do-portal-do-vendedor-preco-minimo-do-item-nao-esta-funcionando-como-esperado
+locale: pt
+kiStatus: Backlog
+internalReference: 928558
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, não é possível criar uma promoção e definir uma condição de preço mínimo do item, por meio da interface não é possível salvar.
+
+## Simulação
+
+
+
+Criar uma promoção e definir um preço mínimo nas condições
+
+
+
+## Workaround
+
+
+
+Por meio da API, é possível salvar a restrição.
+Aviso: salvar novamente por meio da interface, depois de salvar por meio da API, sobrescreverá todas as alterações feitas.
+
+
+
+
+
diff --git a/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md b/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md
index fce8e483c..3d131bbde 100644
--- a/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md
+++ b/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md
@@ -3,8 +3,8 @@ title: 'O menu suspenso Selecionar especificações do Portal do Vendedor não e
 id: 7DeU9mKh7gseN7svVPtDzb
 status: PUBLISHED
 createdAt: 2022-12-06T14:27:57.920Z
-updatedAt: 2023-05-09T19:08:09.706Z
-publishedAt: 2023-05-09T19:08:09.706Z
+updatedAt: 2024-02-16T20:24:15.024Z
+publishedAt: 2024-02-16T20:24:15.024Z
 firstPublishedAt: 2022-12-06T14:27:58.644Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: o-menu-suspenso-selecionar-especificacoes-do-portal-do-vendedor-nao-esta-funcionando-corretamente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 711303
 ---
 
diff --git a/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md b/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
new file mode 100644
index 000000000..088205070
--- /dev/null
+++ b/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
@@ -0,0 +1,43 @@
+---
+title: 'A interface de usuário de registro do vendedor não envia produtos para reindexação ao inativar um vendedor'
+id: 0iAMGhIOKDyMbEykB4pfx
+status: PUBLISHED
+createdAt: 2023-10-06T19:45:08.963Z
+updatedAt: 2023-10-06T19:45:29.372Z
+publishedAt: 2023-10-06T19:45:29.372Z
+firstPublishedAt: 2023-10-06T19:45:09.832Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: a-interface-de-usuario-de-registro-do-vendedor-nao-envia-produtos-para-reindexacao-ao-inativar-um-vendedor
+locale: pt
+kiStatus: Backlog
+internalReference: 915970
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar a nova interface de usuário de experiência do vendedor, /admin/sellers, a ação de inativar um vendedor deve reindexar seus produtos relacionados para que possam ser removidos dos mercados associados, o que não está acontecendo atualmente.
+
+## Simulação
+
+
+Acesse a interface do usuário mencionada acima e, para uma loja que esteja se integrando a um marketplace, com um ponto de extremidade de afiliado (https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187) e, em seguida, tente inativar um vendedor disponível para essa mesma política comercial.
+
+Os itens, no marketplace, não serão atualizados
+
+## Workaround
+
+
+Reindexe a base ou use a interface do usuário do vendedor herdada (https://accountname.vtexcommercestable.com.br/admin/site/seller.aspx), que aciona a indexação corretamente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md b/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md
new file mode 100644
index 000000000..f9726f2d2
--- /dev/null
+++ b/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md
@@ -0,0 +1,60 @@
+---
+title: 'Pedido do vendedor faturado com problema na captura do pagamento'
+id: 59M66kN7D6qy8ErLnbdT9r
+status: PUBLISHED
+createdAt: 2024-01-29T16:51:46.993Z
+updatedAt: 2024-01-29T16:51:47.674Z
+publishedAt: 2024-01-29T16:51:47.674Z
+firstPublishedAt: 2024-01-29T16:51:47.674Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: pedido-do-vendedor-faturado-com-problema-na-captura-do-pagamento
+locale: pt
+kiStatus: Backlog
+internalReference: 376646
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+No momento, da forma como nossa arquitetura foi construída, tanto o vendedor quanto o marketplace são duas entidades totalmente diferentes. Funciona assim: o Marketplace é responsável por receber o dinheiro do cliente e o Vendedor é responsável por toda a logística até o momento em que entrega as mercadorias ao cliente.
+
+A parte do "recebimento de dinheiro" é dividida em Autorização e Captura. Ambas são ações separadas no Gateway e são executadas em dois momentos distintos. O primeiro é quando o cliente faz a compra e o segundo é quando uma fatura é inserida no sistema. Após o processo de Autorização, o Marketplace "informa" ao Vendedor que ele pode prosseguir com a preparação e o envio das mercadorias ao cliente. Como há um intervalo de tempo entre a Autorização e a Captura e como são ações separadas, não há garantia de que a ação de Captura será executada corretamente.
+
+Isso nos deixa com o problema de que o Vendedor recebeu uma notificação para enviar as mercadorias, inseriu uma notificação de fatura no sistema e o Marketplace teve um problema ao tentar realizar a ação de Captura.
+
+Nesses casos de notificação de Autorização e Captura, o Gateway sempre notifica inicialmente o Marketplace que, por sua vez, notifica o Vendedor.
+
+O problema é que o fluxo do vendedor não é interrompido por problemas que ele possa ter na captura de pagamento, mas isso se reflete no fluxo do Marketplace.
+
+## Simulação
+
+
+Não temos um passo a passo para replicar, porém, é possível validar um pedido de exemplo.
+
+Podemos ver que a ordem do Marketplace relatou um problema na captura e não conseguiu concluir o fluxo, exibindo o erro: "Settlement operation has returned Failed" (A operação de liquidação retornou com falha)
+
+No fluxo, o status da ordem no Marketplace será "Verifying invoice" e nas interações a mensagem: "Settlement operation has returned Failed" (A operação de liquidação retornou com falha) será exibida.
+
+Nos eventos de transação, a mensagem: "Error: A resposta foi Entity_Declined" será exibida.
+
+Enquanto o pedido do vendedor chega a Invoiced, porque, para o vendedor na arquitetura atual, a captura do pagamento não é de sua responsabilidade, mesmo sendo o proprietário do pagamento.
+
+## Workaround
+
+
+No momento, não temos uma solução alternativa para completar o fluxo do Marketplace, pois isso depende de a captura ser realizada corretamente. Sem a confirmação do Gateway, o pedido não poderá avançar. Infelizmente, a saída para esse tipo de inconsistência é cancelar a ordem de MKT e tentar fazer uma nova ordem manualmente.
+
+É importante sempre validar se a captura do pagamento foi concluída antes de entregar os produtos
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md b/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md
new file mode 100644
index 000000000..0e1abc943
--- /dev/null
+++ b/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md
@@ -0,0 +1,45 @@
+---
+title: 'Campo de nome do tipo de serviço retornado incorretamente via API'
+id: 1FdozyiQb5DLe7TPICyCDR
+status: PUBLISHED
+createdAt: 2024-01-04T16:36:17.926Z
+updatedAt: 2024-01-04T16:36:18.628Z
+publishedAt: 2024-01-04T16:36:18.628Z
+firstPublishedAt: 2024-01-04T16:36:18.628Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: campo-de-nome-do-tipo-de-servico-retornado-incorretamente-via-api
+locale: pt
+kiStatus: Backlog
+internalReference: 961278
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, as APIs do Catálogo de SKU não estão retornando corretamente o nome de um tipo de serviço. Em vez disso, está sendo retornado o nome do valor do serviço.
+
+## Simulação
+
+
+
+1. Faça uma solicitação GET SKU em um sku associado a um serviço: https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/stockkeepingunit/-skuId-
+2. Observe que o objeto services retorna um campo serviceTypeId e um Name, mas o campo Name não está mostrando o nome do tipo de serviço em si.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md b/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md
index 23eeca7b3..c98e387bd 100644
--- a/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md
+++ b/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md
@@ -3,8 +3,8 @@ title: 'Os preços dos serviços não são atualizados quando adicionados aos it
 id: 5hJ7TbHzX4zFbdNWqPnMRQ
 status: PUBLISHED
 createdAt: 2023-05-09T14:27:37.283Z
-updatedAt: 2023-05-09T14:27:37.766Z
-publishedAt: 2023-05-09T14:27:37.766Z
+updatedAt: 2023-06-23T18:37:32.624Z
+publishedAt: 2023-06-23T18:37:32.624Z
 firstPublishedAt: 2023-05-09T14:27:37.766Z
 contentType: knownIssue
 productTeam: Checkout
diff --git a/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md b/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
new file mode 100644
index 000000000..b7db56b26
--- /dev/null
+++ b/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
@@ -0,0 +1,44 @@
+---
+title: 'Os cookies de sessão são compartilhados entre diferentes vinculações quando não estão no mesmo nível de caminho'
+id: 4pKeUI7qtdByaQowYs19Et
+status: PUBLISHED
+createdAt: 2023-10-25T01:06:04.190Z
+updatedAt: 2023-10-25T01:06:04.707Z
+publishedAt: 2023-10-25T01:06:04.707Z
+firstPublishedAt: 2023-10-25T01:06:04.707Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: os-cookies-de-sessao-sao-compartilhados-entre-diferentes-vinculacoes-quando-nao-estao-no-mesmo-nivel-de-caminho
+locale: pt
+kiStatus: No Fix
+internalReference: 925071
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os cookies para informações da sessão são exclusivos da vinculação de conta específica, mas as vinculações que não estão no mesmo nível de caminho podem receber cookies de níveis inferiores, causando problemas.
+
+Se forem da mesma conta, as informações da sessão serão misturadas e substituirão os parâmetros críticos. Se forem de contas diferentes, isso poderá bloquear as solicitações, gerando erros como "solicitações entre contas não são permitidas".
+
+## Simulação
+
+
+Um exemplo de cenário é uma loja que usa o caminho raiz `/` para seu idioma padrão (inglês) e `/fr` para um segundo idioma (francês). As informações da loja em inglês podem afetar a loja em francês e vice-versa.
+
+Outro exemplo é uma loja B2C em `/us` para o país específico e a loja B2B em `/us/corporate`
+
+## Workaround
+
+
+As lojas que compartilham o mesmo host/domínio podem manter o mesmo padrão para seu caminho sem misturar níveis diferentes. Ideias de alternativas para os exemplos apresentados seriam `/en` versus `/fr` (ambos usando um caminho de nível único) e `/us/personal` versus `/us/corporate` (caminho de dois níveis).
+
+
+
+
diff --git a/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
new file mode 100644
index 000000000..8b28c7071
--- /dev/null
+++ b/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -0,0 +1,51 @@
+---
+title: 'A interface do usuário de configurações não atualiza o "período de expiração" das cotações'
+id: 4CmuAYwDn7tcCiR9DQHSFb
+status: PUBLISHED
+createdAt: 2023-08-07T19:42:22.810Z
+updatedAt: 2024-05-08T18:04:41.362Z
+publishedAt: 2024-05-08T18:04:41.362Z
+firstPublishedAt: 2023-08-07T19:43:56.788Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: a-interface-do-usuario-de-configuracoes-nao-atualiza-o-periodo-de-expiracao-das-cotacoes
+locale: pt
+kiStatus: Backlog
+internalReference: 876576
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A UI de configurações de cotação B2B não atualiza o valor do período de expiração; ele é sempre 30.
+
+## Simulação
+
+
+
+- Acesse a página de configurações de cotações B2B e altere o "período de expiração".
+- Atualize a página; nenhuma alteração é aplicada
+
+## Workaround
+
+
+
+- Acesse o GraphQL IDE e selecione vtex.b2b-quotes-graphql;
+- Use a consulta abaixo para obter a data de expiração:
+
+    { getAppSettings{ adminSetup { cartLifeSpan } }}
+
+- Envie uma mutação para atualizar a data de expiração para um valor diferente:
+
+    mutation SaveAppSettings($input: AppSettingsInput!) { saveAppSettings(input: $input) { adminSetup { cartLifeSpan } }}{ "input": { "cartLifeSpan": }}
+
+
+
+
+
diff --git a/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md b/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md
new file mode 100644
index 000000000..de50dee7b
--- /dev/null
+++ b/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md
@@ -0,0 +1,44 @@
+---
+title: 'As opções de envio ficam congeladas ao tentar selecionar uma opção'
+id: 7zrMuzLq8kpNLDc2l2FswA
+status: PUBLISHED
+createdAt: 2023-09-13T14:42:26.106Z
+updatedAt: 2024-05-21T14:04:53.005Z
+publishedAt: 2024-05-21T14:04:53.005Z
+firstPublishedAt: 2023-09-13T14:42:26.860Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: as-opcoes-de-envio-ficam-congeladas-ao-tentar-selecionar-uma-opcao
+locale: pt
+kiStatus: Fixed
+internalReference: 898888
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar a configuração de checkout B2B e ir e voltar entre as etapas de envio e pagamento, o envio fica congelado ao tentar selecionar uma opção.
+
+## Simulação
+
+
+
+- Certifique-se de ter pelo menos dois endereços registrados no centro de custos;
+- Adicione qualquer produto ao carrinho e vá para a etapa de pagamento;
+- Edite o frete, volte para a etapa de pagamento e atualize a página;
+- Edite o frete novamente e tente selecionar uma opção, a interface do usuário será congelad
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md b/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
new file mode 100644
index 000000000..3fb06444e
--- /dev/null
+++ b/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
@@ -0,0 +1,46 @@
+---
+title: 'A política de remessa presa no status de processamento é exibida como ativa na nova UI de logística'
+id: 6c6JrnkhTdz5kM8kGzsRXQ
+status: PUBLISHED
+createdAt: 2023-10-25T23:48:45.891Z
+updatedAt: 2023-11-27T21:18:03.811Z
+publishedAt: 2023-11-27T21:18:03.811Z
+firstPublishedAt: 2023-10-25T23:48:46.471Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: a-politica-de-remessa-presa-no-status-de-processamento-e-exibida-como-ativa-na-nova-ui-de-logistica
+locale: pt
+kiStatus: Fixed
+internalReference: 925914
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Às vezes, a política de remessa pode ficar presa no status de processamento, mas na nova interface de usuário de logística você não consegue vê-la porque ela informa que o status está ativo.
+Esse comportamento pode atrapalhar o carregamento de uma nova planilha de frete, pois o usuário presumirá que o processo foi concluído com a exibição de um status ativo, mas os novos dados não serão refletidos.
+
+
+## Simulação
+
+
+Tenha uma política de remessa com status ativo na nova interface do usuário, mas ao tentar carregar uma nova planilha, os dados não são refletidos.
+
+
+
+
+## Workaround
+
+
+Para que a política de envio saia do status de processamento em que está presa, é necessária uma ação da equipe, após a qual a planilha pode ser carregada e o processo continuará normalmente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md b/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
index 25e72c285..c25fef962 100644
--- a/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
+++ b/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
@@ -3,8 +3,8 @@ title: 'A política de remessa que não entrega nos finais de semana está sendo
 id: 25bhUZXA9sZvyFVNeMUSJl
 status: PUBLISHED
 createdAt: 2022-06-08T18:32:07.971Z
-updatedAt: 2022-11-25T21:59:34.643Z
-publishedAt: 2022-11-25T21:59:34.643Z
+updatedAt: 2024-02-16T20:25:34.078Z
+publishedAt: 2024-02-16T20:25:34.078Z
 firstPublishedAt: 2022-06-08T18:32:08.836Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: a-politica-de-remessa-que-nao-entrega-nos-finais-de-semana-esta-sendo-considerada
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 594828
 ---
 
diff --git a/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md b/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
index 3eef084e3..1108c10d3 100644
--- a/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
+++ b/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
@@ -3,8 +3,8 @@ title: 'Política de envio com MaxVolume incorreto na planilha não mostra erro
 id: 7zIbmadcOfI3oHmkm8LmkY
 status: PUBLISHED
 createdAt: 2022-05-18T18:19:04.901Z
-updatedAt: 2022-11-25T21:59:49.182Z
-publishedAt: 2022-11-25T21:59:49.182Z
+updatedAt: 2024-02-16T20:25:21.794Z
+publishedAt: 2024-02-16T20:25:21.794Z
 firstPublishedAt: 2022-05-18T18:19:05.868Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: politica-de-envio-com-maxvolume-incorreto-na-planilha-nao-mostra-erro-de-mensagem-na-simulacao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 380471
 ---
 
diff --git a/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md b/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
index a82c1d033..59d2e4172 100644
--- a/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
+++ b/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
@@ -3,8 +3,8 @@ title: 'A visualização prévia da expedição não usa o nome SLA para exibiç
 id: 6v7vh0CSUfpiF04brZ0bgb
 status: PUBLISHED
 createdAt: 2022-05-06T20:46:38.910Z
-updatedAt: 2022-11-25T21:52:23.344Z
-publishedAt: 2022-11-25T21:52:23.344Z
+updatedAt: 2024-02-16T20:25:44.430Z
+publishedAt: 2024-02-16T20:25:44.430Z
 firstPublishedAt: 2022-05-06T20:46:39.731Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-visualizacao-previa-da-expedicao-nao-usa-o-nome-sla-para-exibicao-na-interface-de-usuario
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 574651
 ---
 
diff --git a/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md b/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
new file mode 100644
index 000000000..fe4783acb
--- /dev/null
+++ b/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
@@ -0,0 +1,43 @@
+---
+title: 'A visualização da remessa mostra o código postal de retirada para remessa quando há divisão de pacotes para retirada e remessa'
+id: 7gGu9EUZGGXp4dRCCGipsA
+status: PUBLISHED
+createdAt: 2024-06-26T20:36:39.627Z
+updatedAt: 2024-06-26T20:36:40.541Z
+publishedAt: 2024-06-26T20:36:40.541Z
+firstPublishedAt: 2024-06-26T20:36:40.541Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-visualizacao-da-remessa-mostra-o-codigo-postal-de-retirada-para-remessa-quando-ha-divisao-de-pacotes-para-retirada-e-remessa
+locale: pt
+kiStatus: Backlog
+internalReference: 938124
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na visualização do envio, ao selecionar a retirada na loja, mas nem todos os itens estão disponíveis para essa retirada, o endereço exibido para envio é o da retirada escolhida, e não é possível alterá-lo. No formulário de pedido, o endereço selecionado para envio está correto.
+
+## Simulação
+
+
+
+- Adicione itens ao carrinho em que pelo menos um não esteja disponível para retirada;
+- Adicionar um código postal ao carrinho;
+- Alterar para retirada na loja;
+- O código postal mostrado para envio é o da retirada escolhida
+
+## Workaround
+
+
+Altere o código postal na etapa de envio.
+
+
+
diff --git a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
index 51b0009d3..7094c5d0c 100644
--- a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
+++ b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'Pré-visualização de embarque exibindo erroneamente a data em que est
 id: 6pbufuWTFkL4NK3xLIxj1z
 status: PUBLISHED
 createdAt: 2023-01-31T19:36:58.137Z
-updatedAt: 2023-01-31T19:36:58.933Z
-publishedAt: 2023-01-31T19:36:58.933Z
+updatedAt: 2024-07-01T18:48:44.228Z
+publishedAt: 2024-07-01T18:48:44.228Z
 firstPublishedAt: 2023-01-31T19:36:58.933Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: previsualizacao-de-embarque-exibindo-erroneamente-a-data-em-que-esta-programada-a-entrega
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 743774
 ---
 
diff --git a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
index e4f756f1b..e801b5d6a 100644
--- a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
+++ b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
@@ -1,18 +1,18 @@
 ---
-title: 'Pré-visualização de embarque exibindo erroneamente o preço quando a entrega é programada'
+title: 'A visualização do frete está exibindo erroneamente o preço quando a entrega está programada'
 id: 1348f4mDxoxAT7pTKBxm29
 status: PUBLISHED
 createdAt: 2023-01-31T19:16:25.118Z
-updatedAt: 2023-02-01T20:32:44.535Z
-publishedAt: 2023-02-01T20:32:44.535Z
+updatedAt: 2024-03-27T15:40:02.745Z
+publishedAt: 2024-03-27T15:40:02.745Z
 firstPublishedAt: 2023-01-31T19:16:25.874Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: previsualizacao-de-embarque-exibindo-erroneamente-o-preco-quando-a-entrega-e-programada
+slug: a-visualizacao-do-frete-esta-exibindo-erroneamente-o-preco-quando-a-entrega-esta-programada
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 532487
 ---
 
@@ -23,18 +23,14 @@ internalReference: 532487
 </div>
 
 
-O preço de entrega exibido na visualização de remessa (carrinho) está incorreto quando os itens são entregues programados e todos esses itens saem no mesmo SLA. Mesmo com a API devolvendo o valor correto, a IU não reflete esta informação e exibe o valor incorreto.
-
-
-##
+O preço de entrega exibido no shipping-preview (carrinho) está incorreto quando os itens têm entrega programada e todos esses itens saem no mesmo SLA. Mesmo com a API retornando o valor correto, a interface do usuário não reflete essa informação e exibe o valor incorreto.
 
 ## Simulação
 
 
-Adicione dois ou mais itens no carrinho com entrega programada, a IU mostrará um valor diferente do que a devolução API
+Se você adicionar dois ou mais itens ao carrinho com entrega programada, a interface do usuário mostrará um valor diferente do valor retornado pela API
 
 
-##
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md b/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md
index 950bdd2d7..be9f7d74f 100644
--- a/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md
+++ b/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md
@@ -3,8 +3,8 @@ title: 'O campo de entrada do código postal da visualização do envio não est
 id: 6YCl40YEzu1HGkfHkcjGqu
 status: PUBLISHED
 createdAt: 2023-05-09T13:27:51.259Z
-updatedAt: 2023-05-09T13:27:51.724Z
-publishedAt: 2023-05-09T13:27:51.724Z
+updatedAt: 2024-02-20T22:22:29.335Z
+publishedAt: 2024-02-20T22:22:29.335Z
 firstPublishedAt: 2023-05-09T13:27:51.724Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-campo-de-entrada-do-codigo-postal-da-visualizacao-do-envio-nao-esta-oculto
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 821984
 ---
 
diff --git a/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md b/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
new file mode 100644
index 000000000..6c9af3ee4
--- /dev/null
+++ b/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
@@ -0,0 +1,42 @@
+---
+title: 'Promoções de remessa aplicadas em SLAs diferentes causando divergência no Tax Hub'
+id: 3uI0b4FmXUh4uue5kFyFNy
+status: PUBLISHED
+createdAt: 2023-10-09T13:42:08.767Z
+updatedAt: 2023-10-23T11:59:12.329Z
+publishedAt: 2023-10-23T11:59:12.329Z
+firstPublishedAt: 2023-10-09T13:42:09.636Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: promocoes-de-remessa-aplicadas-em-slas-diferentes-causando-divergencia-no-tax-hub
+locale: pt
+kiStatus: Fixed
+internalReference: 916423
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando as promoções de frete se aplicam a diferentes SLAs, sendo um deles o frete grátis, isso causa divergência na solicitação enviada pelo Tax Hub, impedindo que o pedido seja feito.
+
+## Simulação
+
+
+
+- Crie uma promoção de frete grátis para um SLA específico;
+- Crie qualquer outra promoção de frete para outro SLA;
+- Ao tentar fazer um pedido, a mensagem "O pedido solicitado não pôde ser criado. Por favor, tente novamente"
+
+## Workaround
+
+
+N/A
+
+
+
diff --git a/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md b/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
new file mode 100644
index 000000000..ee6aae0ff
--- /dev/null
+++ b/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
@@ -0,0 +1,34 @@
+---
+title: 'A etapa de envio com código postal não funciona em alguns países (Emirados Árabes Unidos)'
+id: 2nlXX0e1q1MLiSjCG1U1Uf
+status: PUBLISHED
+createdAt: 2024-06-21T16:31:14.956Z
+updatedAt: 2024-07-16T13:10:07.140Z
+publishedAt: 2024-07-16T13:10:07.140Z
+firstPublishedAt: 2024-06-21T16:31:15.891Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-etapa-de-envio-com-codigo-postal-nao-funciona-em-alguns-paises-emirados-arabes-unidos
+locale: pt
+kiStatus: Fixed
+internalReference: 312132
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+## **Resumo**
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/shopee-failed-to-create-product-variations.md b/docs/known-issues/pt/shopee-failed-to-create-product-variations.md
index d691f4795..b1e6c9bbc 100644
--- a/docs/known-issues/pt/shopee-failed-to-create-product-variations.md
+++ b/docs/known-issues/pt/shopee-failed-to-create-product-variations.md
@@ -3,8 +3,8 @@ title: '[Falha em criar variações de produtos'
 id: 5IKAkqtm8eejg2IhzrCgSz
 status: PUBLISHED
 createdAt: 2022-10-25T16:29:19.572Z
-updatedAt: 2023-02-07T12:56:37.721Z
-publishedAt: 2023-02-07T12:56:37.721Z
+updatedAt: 2024-02-16T20:24:45.182Z
+publishedAt: 2024-02-16T20:24:45.182Z
 firstPublishedAt: 2022-10-25T16:29:20.906Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: falha-em-criar-variacoes-de-produtos
 locale: pt
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 685160
 ---
 
diff --git a/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md b/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md
new file mode 100644
index 000000000..38ac75d3a
--- /dev/null
+++ b/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md
@@ -0,0 +1,49 @@
+---
+title: 'Produtos similares UI brokes with too many products'
+id: 1gaBTJ1VlwLkoBb1636qoH
+status: PUBLISHED
+createdAt: 2023-07-25T15:53:49.976Z
+updatedAt: 2023-08-15T17:28:32.114Z
+publishedAt: 2023-08-15T17:28:32.114Z
+firstPublishedAt: 2023-07-25T15:53:50.941Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: produtos-similares-ui-brokes-with-too-many-products
+locale: pt
+kiStatus: Backlog
+internalReference: 868425
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao abrir um formulário de produto com mais de 6 produtos semelhantes, a visualização da interface do usuário é interrompida
+para crescer em um formato de lista, começa a adicionar em um formato de escada
+
+## Simulação
+
+
+
+Adicionar 10 produtos semelhantes a um produto
+
+
+
+## Workaround
+
+
+
+
+- Recomendamos o uso da API para gerenciar os produtos semelhantes
+- Tentar minimizar o zoom na página ajuda a se ajustar melhor, o que funcionará em alguns casos
+
+
+
+
+
diff --git a/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md b/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
index 1a70c4874..65d331550 100644
--- a/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
+++ b/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
@@ -3,8 +3,8 @@ title: 'Simulação Não é possível encontrar Produtos do Catálogo V2 na Pág
 id: 7jZBMAZHNilokDdbCxWzSs
 status: PUBLISHED
 createdAt: 2022-05-18T18:26:09.456Z
-updatedAt: 2022-11-25T21:59:14.900Z
-publishedAt: 2022-11-25T21:59:14.900Z
+updatedAt: 2024-02-16T20:28:57.548Z
+publishedAt: 2024-02-16T20:28:57.548Z
 firstPublishedAt: 2022-05-18T18:26:10.048Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: simulacao-nao-e-possivel-encontrar-produtos-do-catalogo-v2-na-pagina-de-simulacao-de-embarque
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 488362
 ---
 
diff --git a/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md b/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md
new file mode 100644
index 000000000..030737d1f
--- /dev/null
+++ b/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md
@@ -0,0 +1,46 @@
+---
+title: 'A condição de pagamento em uma única parcela não aparece no checkout.'
+id: 3L7GJTRaWWA9Wjw2zkQqtS
+status: PUBLISHED
+createdAt: 2022-06-29T11:57:22.859Z
+updatedAt: 2024-04-26T15:49:53.973Z
+publishedAt: 2024-04-26T15:49:53.973Z
+firstPublishedAt: 2022-06-29T11:57:23.251Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: a-condicao-de-pagamento-em-uma-unica-parcela-nao-aparece-no-checkout
+locale: pt
+kiStatus: Backlog
+internalReference: 605568
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao configurar uma única condição de pagamento com apenas uma opção de parcelamento ou várias condições de pagamento em que apenas uma opção de parcelamento está disponível para um carrinho específico, essa opção de parcelamento não é exibida no checkout. Embora seja exibida corretamente em `paymentData`, ela não é visível para o usuário. Em vez disso, apenas a opção de pagar o valor total é exibida. Entretanto, quando a transação é concluída, o pagamento é processado com a opção de parcelamento correta.
+
+## Simulação
+
+
+
+- Configure uma condição de pagamento de parcela única.
+- Vá para a página de checkout comprando qualquer item aleatório.
+- Navegue até a guia Rede no devtools e verifique se a opção de parcelamento está carregada corretamente na resposta `paymentData`.
+- Verifique o menu suspenso de opções de parcelamento na página de checkout. Observe que a opção de parcelamento configurada está ausente; em vez disso, o valor total é exibido.
+- Apesar desse problema, ao concluir a compra, a transação reflete corretamente a opção de parcelamento escolhida
+
+## Workaround
+
+
+N/A
+
+Atenciosamente,
+Gisely Lacerda
+Engenheira de suporte ao produto, equipe de jornada do comprador
+
diff --git a/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md b/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md
new file mode 100644
index 000000000..04fd9697b
--- /dev/null
+++ b/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md
@@ -0,0 +1,46 @@
+---
+title: 'O editor do site não permite alterações no modelo condicional'
+id: dGuXWBUUZdMB0nfndLPZ9
+status: PUBLISHED
+createdAt: 2023-07-13T20:05:31.326Z
+updatedAt: 2023-07-13T20:05:31.834Z
+publishedAt: 2023-07-13T20:05:31.834Z
+firstPublishedAt: 2023-07-13T20:05:31.834Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: o-editor-do-site-nao-permite-alteracoes-no-modelo-condicional
+locale: pt
+kiStatus: Backlog
+internalReference: 861920
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um modelo é definido como condicional, não é possível fazer alterações nele por meio do editor do site.
+
+## Simulação
+
+
+
+- adicione um modelo condicional a uma das páginas nas páginas do CMS
+- certifique-se de que a condição para que ele funcione esteja sendo aplicada
+- tente editar essa página por meio do editor do site
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md b/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
index 3c6ea1c76..bacc88945 100644
--- a/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
+++ b/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
@@ -3,8 +3,8 @@ title: 'Versão Desktop da renderização do site ao acessar via IPad no Safari'
 id: 17jzhKnc8X1bKo5ExwEY5L
 status: PUBLISHED
 createdAt: 2023-01-17T18:24:02.908Z
-updatedAt: 2023-01-17T18:27:50.296Z
-publishedAt: 2023-01-17T18:27:50.296Z
+updatedAt: 2024-02-16T20:26:44.446Z
+publishedAt: 2024-02-16T20:26:44.446Z
 firstPublishedAt: 2023-01-17T18:24:03.621Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: versao-desktop-da-renderizacao-do-site-ao-acessar-via-ipad-no-safari
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 735208
 ---
 
diff --git a/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md b/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md
new file mode 100644
index 000000000..639c77ebe
--- /dev/null
+++ b/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md
@@ -0,0 +1,76 @@
+---
+title: 'O Sitemap não está sendo gerado/atualizado'
+id: 1tJ4XHtbnFsfS30JWXwxb0
+status: PUBLISHED
+createdAt: 2023-05-17T13:58:46.443Z
+updatedAt: 2024-02-16T18:17:17.707Z
+publishedAt: 2024-02-16T18:17:17.707Z
+firstPublishedAt: 2023-05-17T13:58:47.102Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-sitemap-nao-esta-sendo-geradoatualizado
+locale: pt
+kiStatus: Backlog
+internalReference: 827104
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Há três cenários em que o mapa do site não está sendo gerado/atualizado:
+
+
+
+1. Quando temos um produto não encontrado ou com algum tipo de problema no catálogo, o mapa do site não é gerado. Você pode pesquisar os registros no OpenSearch, nesse caso, para verificar qual produto tem um problema;
+
+
+
+2. Quando a conta tem o aplicativo `search.resolver@1.x`, o mapa do site pode apresentar erros quando:
+
+
+
+- Uma categoria tem seu primeiro produto proveniente de uma categoria semelhante (as regras de comercialização podem ter um impacto nesse caso, dependendo do produto que você está promovendo);
+
+- A página de pesquisa/marca/categoria não tem produtos; nesse caso, a página não é indexada no mapa do site e sua geração falha
+
+
+3. Os produtos que não têm a política comercial definida no catálogo não serão recebidos pelo mapa do site
+
+
+## Simulação
+
+
+
+Tente gerar o mapa do site para uma conta que tenha um dos cenários descritos acima e ele falhará
+
+
+
+## Workaround
+
+
+
+
+- Crie um novo espaço de trabalho
+- Instale o search-resolver@0.x `(vtex install vtex.search-resolver@0.x)`
+- Gerar o novo mapa do site
+- Agora você pode reverter o search-resolver para a versão 1.x (`vtex install vtex.search-resolver@1.x`)
+- Promover o espaço de trabalho criado para mestre
+
+Obs: Essa solução alternativa pode não funcionar em todos os momentos. Às vezes, a loja pode ter tantos produtos inválidos que nem mesmo o `search-resolver@0.x` atualizará o mapa do site.
+
+Mas, eventualmente, você precisará corrigir o cenário que impede a geração do mapa do site
+
+Lembre-se de que atualizar a loja para resolver@0.x e gerar o mapa do site em um espaço de trabalho é a solução alternativa, pois alguns casos inválidos não ocorrem em nossa pesquisa herdada.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md b/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
new file mode 100644
index 000000000..9495f7459
--- /dev/null
+++ b/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
@@ -0,0 +1,35 @@
+---
+title: 'O administrador da SKU quebra ao enviar um código de referência com mais de 50 caracteres'
+id: 3AhyVsOpwkRUEHT77Wcc1A
+status: PUBLISHED
+createdAt: 2023-08-21T17:52:27.931Z
+updatedAt: 2023-08-21T17:52:28.799Z
+publishedAt: 2023-08-21T17:52:28.799Z
+firstPublishedAt: 2023-08-21T17:52:28.799Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-administrador-da-sku-quebra-ao-enviar-um-codigo-de-referencia-com-mais-de-50-caracteres
+locale: pt
+kiStatus: Backlog
+internalReference: 884789
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que o usuário possa alterar o código de referência do SKU usando o administrador. No entanto, quando um valor maior que 50 caracteres é passado, o administrador falha, exibindo uma mensagem de "algo deu errado".
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md b/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
new file mode 100644
index 000000000..5e97ef51c
--- /dev/null
+++ b/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
@@ -0,0 +1,44 @@
+---
+title: 'Sku negado em Skus recebidos após limitação no catálogo do marketplace'
+id: 4fleOaKNp6ALXdmZcAVCg0
+status: PUBLISHED
+createdAt: 2024-01-23T12:50:23.697Z
+updatedAt: 2024-01-23T12:50:24.398Z
+publishedAt: 2024-01-23T12:50:24.398Z
+firstPublishedAt: 2024-01-23T12:50:24.398Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: sku-negado-em-skus-recebidos-apos-limitacao-no-catalogo-do-marketplace
+locale: pt
+kiStatus: Backlog
+internalReference: 970208
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao aprovar um novo produto em Skus recebidos (automática ou manualmente), o módulo de sugestões se comunica com o catálogo do Marketplace para executar a ação.
+Se, nesse momento, o módulo de catálogo retornar um erro de limitação, o sku acabará sendo rejeitado pelo matcher, apesar de ter todas as informações corretas.
+
+## Simulação
+
+
+Esse não é um cenário fácil (ou comum) de replicar, pois depende de outro sistema que não esteja funcionando como deveria e retorne limitação.
+
+
+
+## Workaround
+
+
+Aprovar o sku manualmente na área rejeitada de Skus recebidos.
+
+
+
+
+
diff --git a/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md b/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md
new file mode 100644
index 000000000..35499d943
--- /dev/null
+++ b/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md
@@ -0,0 +1,46 @@
+---
+title: 'A atualização do arquivo SKU não atualiza as tags de versão ?v'
+id: 5Uw2VIBtTNDY3Ha5WDzGXJ
+status: PUBLISHED
+createdAt: 2023-06-29T14:37:56.437Z
+updatedAt: 2024-07-01T18:49:06.220Z
+publishedAt: 2024-07-01T18:49:06.220Z
+firstPublishedAt: 2023-06-29T14:37:57.352Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-atualizacao-do-arquivo-sku-nao-atualiza-as-tags-de-versao-v
+locale: pt
+kiStatus: No Fix
+internalReference: 852869
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, quando um arquivo de imagem SKU é atualizado por meio da API para ficar na mesma posição de um arquivo anterior, sua tag de versão (?v=) na página do produto não é atualizada corretamente.
+
+## Simulação
+
+
+
+
+- Para um sku que já tenha arquivos, tente atualizar uma imagem para uma nova.
+- Para uma interpretação adequada do arquivo que está sendo alterado para o usuário e/ou sistemas, a tag de versão (?v=) sob a imagem href no HTML da página do produto deve ser atualizada.
+- No entanto, isso não acontece quando se usa essa API para realizar essas atualizações.
+
+
+## Workaround
+
+
+Excluir todos os arquivos SKU e reinseri-los do zero força a atualização.
+
+OU
+
+A exclusão de um indexador força a atualização.
+
diff --git a/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
new file mode 100644
index 000000000..1dc35a300
--- /dev/null
+++ b/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -0,0 +1,45 @@
+---
+title: 'A API SKU Insert File não está respondendo com a propriedade "Text".'
+id: 2rPsyAkpGNCVIM4yGlcMBw
+status: PUBLISHED
+createdAt: 2024-04-10T14:59:14.341Z
+updatedAt: 2024-07-22T19:38:40.304Z
+publishedAt: 2024-07-22T19:38:40.304Z
+firstPublishedAt: 2024-04-10T14:59:15.416Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-api-sku-insert-file-nao-esta-respondendo-com-a-propriedade-text
+locale: pt
+kiStatus: Fixed
+internalReference: 1014787
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, a API para criar um arquivo sku https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file não está respondendo corretamente à propriedade "Text".
+
+Os dados desse campo são aceitos e enviados ao banco de dados, mas o corpo de resposta de qualquer método do arquivo SKU (GET, PUT, POST) está sempre respondendo ao corpo de resposta JSON que contém a propriedade "Text" como nulo, mesmo quando ela tem um valor salvo.
+
+## Simulação
+
+
+1 - Usando a API mencionada anteriormente, envie um corpo de solicitação para uma imagem válida que tenha um campo "Text" com um dado não nulo.
+2 - Verifique o corpo da resposta dessa API ou use uma solicitação GET para buscar os dados desse arquivo, o campo Text será nulo.
+3 - No entanto, se você acessar o administrador da loja, em https://VTEX.myvtex.com/admin/Site/SkuForm.aspx?IdSku=, verá que o texto exibe os dados do campo enviado
+
+## Workaround
+
+
+Busque dados para o campo Text no administrador, nas planilhas ou nas APIs de pesquisa.
+
+
+
+
+
diff --git a/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md b/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
index 59695f69c..8200a2678 100644
--- a/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
+++ b/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
@@ -3,8 +3,8 @@ title: 'A SKU removida do Amazon SC não está sendo desabilitada no Amazon Port
 id: 9yeLgMrhp9nSu9MtJ518G
 status: PUBLISHED
 createdAt: 2023-05-18T11:43:30.694Z
-updatedAt: 2023-05-18T11:43:31.301Z
-publishedAt: 2023-05-18T11:43:31.301Z
+updatedAt: 2023-08-14T17:50:14.349Z
+publishedAt: 2023-08-14T17:50:14.349Z
 firstPublishedAt: 2023-05-18T11:43:31.301Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: a-sku-removida-do-amazon-sc-nao-esta-sendo-desabilitada-no-amazon-portal
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 827760
 ---
 
diff --git a/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md b/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md
index f9c5226fc..4382c8bf2 100644
--- a/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md
+++ b/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md
@@ -3,8 +3,8 @@ title: 'Modo de exibição do seletor de SKU SELECT não funciona em prateleiras
 id: 4viowN3tnbsdc0f1bqXrux
 status: PUBLISHED
 createdAt: 2023-01-18T12:24:32.528Z
-updatedAt: 2023-01-18T12:24:33.003Z
-publishedAt: 2023-01-18T12:24:33.003Z
+updatedAt: 2024-02-16T20:24:43.422Z
+publishedAt: 2024-02-16T20:24:43.422Z
 firstPublishedAt: 2023-01-18T12:24:33.003Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: modo-de-exibicao-do-seletor-de-sku-select-nao-funciona-em-prateleiras
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 682152
 ---
 
diff --git a/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md b/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
new file mode 100644
index 000000000..a81f630d3
--- /dev/null
+++ b/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
@@ -0,0 +1,35 @@
+---
+title: 'O seletor de SKU não escolhe a SKU correta quando há variações semelhantes com substrings'
+id: 7EY2RMqoJM7bbLZvyVDdRn
+status: PUBLISHED
+createdAt: 2024-06-11T18:15:27.243Z
+updatedAt: 2024-07-03T20:19:45.157Z
+publishedAt: 2024-07-03T20:19:45.157Z
+firstPublishedAt: 2024-06-11T18:15:28.029Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-seletor-de-sku-nao-escolhe-a-sku-correta-quando-ha-variacoes-semelhantes-com-substrings
+locale: pt
+kiStatus: Fixed
+internalReference: 1047992
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando houver uma substring da variação na SKU escolhida em outra variação disponível, talvez não selecionemos a SKU escolhida
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md b/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md
new file mode 100644
index 000000000..e4c25cac2
--- /dev/null
+++ b/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md
@@ -0,0 +1,47 @@
+---
+title: 'Seletor de SKU com contextos múltiplos'
+id: 4n6ap30jnJOrzflLCnVziO
+status: PUBLISHED
+createdAt: 2024-01-29T13:31:21.812Z
+updatedAt: 2024-07-11T19:19:22.383Z
+publishedAt: 2024-07-11T19:19:22.383Z
+firstPublishedAt: 2024-01-29T13:31:22.391Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: seletor-de-sku-com-contextos-multiplos
+locale: pt
+kiStatus: Fixed
+internalReference: 341322
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+O seletor de SKU dentro da exibição modal/rápida não está no mesmo contexto que está na página de pesquisa e na página do produto.
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/zIQ15WW7s1Zo24Z1I5tFT4H3y/?name=image.png)
+
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/gnAeV75W2Sip3Pl1zfQyAiWOI/?name=image.png)
+
+## Simulação
+
+
+
+- Vá para qualquer loja que tenha uma visualização rápida e um seletor de SKU.
+- Escolha uma SKU e vá para o modo de visualização rápida
+- Altere a SKU dentro do modal de visualização rápida
+- Saia do modo de visualização rápida e você perceberá que o SKU não mudou, ele apenas mudou dentro do contexto da visualização rápid
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md b/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
index 416ef0c8f..017a550d3 100644
--- a/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
+++ b/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
@@ -3,8 +3,8 @@ title: 'Os filtros de especificação SKU não são carregados quando o SKU só
 id: 5SpoacD49oxDDGJjepUEoL
 status: PUBLISHED
 createdAt: 2022-03-21T17:41:20.048Z
-updatedAt: 2022-11-25T21:58:05.886Z
-publishedAt: 2022-11-25T21:58:05.886Z
+updatedAt: 2024-02-16T20:29:10.321Z
+publishedAt: 2024-02-16T20:29:10.321Z
 firstPublishedAt: 2022-03-21T17:41:20.389Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: os-filtros-de-especificacao-sku-nao-sao-carregados-quando-o-sku-so-esta-disponivel-em-um-vendedor-de-whitelabel
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 431888
 ---
 
diff --git a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
index 167dddbe2..e00faa6b1 100644
--- a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
@@ -1,18 +1,18 @@
 ---
-title: 'Skus do mesmo produto sendo criado separadamente (contas com a bandeira Autoapprove habilitada)'
+title: 'Skus do mesmo produto sendo criados separadamente (contas com o sinalizador Autoapprove ativado)'
 id: 1nkfd9OuKTFsnBWe1k6dif
 status: PUBLISHED
 createdAt: 2023-02-15T12:22:35.143Z
-updatedAt: 2023-02-15T12:22:35.839Z
-publishedAt: 2023-02-15T12:22:35.839Z
+updatedAt: 2023-11-28T19:01:37.291Z
+publishedAt: 2023-11-28T19:01:37.291Z
 firstPublishedAt: 2023-02-15T12:22:35.839Z
 contentType: knownIssue
 productTeam: Marketplace
 author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
-slug: skus-do-mesmo-produto-sendo-criado-separadamente-contas-com-a-bandeira-autoapprove-habilitada
+slug: skus-do-mesmo-produto-sendo-criados-separadamente-contas-com-o-sinalizador-autoapprove-ativado
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 467112
 ---
 
@@ -25,32 +25,26 @@ internalReference: 467112
 
 O vendedor envia um lote com skus do mesmo produto (todas as variações possíveis do produto).
 
-Em vez de ser criado como um produto com suas variações, todos os skus estão sendo criados separadamente.
+Em vez de serem criados como um produto com suas variações, todos os skus estão sendo criados separadamente.
 
-Este comportamento está acontecendo porque a conta no mercado tem a bandeira Autoapprove habilitada e o vendedor está enviando todos os skus de uma só vez.
+Esse comportamento está ocorrendo porque a conta do marketplace tem o sinalizador Autoapprove ativado e o vendedor está enviando todos os skus de uma vez.
 
-Normalmente, o sistema tem um cadeado, pelo nome do produto, para evitar este tipo de situação, já que o Matcher tem mais de uma fila processando o skus. Mas esta fechadura não é implementada no fluxo de trabalho da Auto-aprovação.
-
-
-##
+Normalmente, o sistema tem um bloqueio, por nome de produto, para evitar esse tipo de situação, pois o Matcher tem mais de uma fila para processar os skus. Mas esse bloqueio não está implementado no fluxo de trabalho Autoapprove.
 
 ## Simulação
 
 
-1. Habilitar a bandeira Autoaprovar no Mercado;
+1. Ative o sinalizador Autoapprove no Marketplace;
 2. O vendedor envia um lote de produtos e seus skus (variações) de uma só vez;
-3. O primeiro skus do produto é criado corretamente, mas os outros são criados separadamente.
-
-
-##
+3. O primeiro skus do produto é criado corretamente, mas os outros são criados separadamente
 
 ## Workaround
 
 
-Para evitar esta situação, há duas maneiras possíveis.
+Para evitar essa situação, há duas maneiras possíveis.
 
-1. O vendedor envia o skus lentamente dentro de um período de tempo;
-2. Desativar a bandeira Autoapprove no Mercado.
+1. O vendedor envia os skus lentamente dentro de um período de tempo;
+2. Desativar o sinalizador Autoapprove no Marketplace.
 
 
 
diff --git a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
new file mode 100644
index 000000000..86dd4ee83
--- /dev/null
+++ b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
@@ -0,0 +1,52 @@
+---
+title: 'Skus do mesmo produto sendo criados separadamente em contas com o sinalizador de aprovação automática ativado'
+id: 5xWm9hzTO0Yuv0e2UuMgH6
+status: PUBLISHED
+createdAt: 2024-01-09T12:39:19.465Z
+updatedAt: 2024-07-22T19:31:17.990Z
+publishedAt: 2024-07-22T19:31:17.990Z
+firstPublishedAt: 2024-01-09T19:59:00.420Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: skus-do-mesmo-produto-sendo-criados-separadamente-em-contas-com-o-sinalizador-de-aprovacao-automatica-ativado
+locale: pt
+kiStatus: Fixed
+internalReference: 962986
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O vendedor envia um lote com skus do mesmo produto (todas as variações possíveis do produto).
+
+Em vez de serem criados como um produto com suas variações, todos os skus estão sendo criados separadamente.
+
+Esse comportamento está ocorrendo porque a conta do marketplace tem o sinalizador Autoapprove ativado e o vendedor está enviando todos os skus de uma vez.
+
+Normalmente, o sistema tem um bloqueio, por nome de produto, para evitar esse tipo de situação, pois o Matcher tem mais de uma fila para processar os skus. Mas esse bloqueio não está implementado no fluxo de trabalho Autoapprove.
+
+## Simulação
+
+
+1. Ative o sinalizador Autoapprove no Marketplace;
+2. O vendedor envia um lote de produtos e seus skus (variações) de uma só vez;
+3. O primeiro skus do produto é criado corretamente, mas os outros são criados separadamente
+
+## Workaround
+
+
+Para evitar essa situação, há duas maneiras possíveis.
+
+1. O vendedor envia os skus lentamente dentro de um período de tempo;
+2. Desativar o sinalizador Autoapprove no Marketplace.
+
+
+
+
+
diff --git a/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md b/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
index 8528c1494..300f4d006 100644
--- a/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
+++ b/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
@@ -3,8 +3,8 @@ title: 'SkuServicoForm.aspx não listando Tabelas de Valores no início para um
 id: 2QrjRVvJXiWmRXTYf8DrMK
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:32.216Z
-updatedAt: 2022-11-25T21:50:15.511Z
-publishedAt: 2022-11-25T21:50:15.511Z
+updatedAt: 2024-02-16T20:27:50.659Z
+publishedAt: 2024-02-16T20:27:50.659Z
 firstPublishedAt: 2022-06-28T16:55:32.529Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: skuservicoformaspx-nao-listando-tabelas-de-valores-no-inicio-para-um-tipo-de-valor
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 335819
 ---
 
diff --git a/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md b/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
new file mode 100644
index 000000000..a0e8955e3
--- /dev/null
+++ b/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
@@ -0,0 +1,48 @@
+---
+title: 'Oferta de SLA flutuante entre diferentes políticas de envio devido ao cache na data estimada de 30 segundos'
+id: 2uN3bVrxHhj6Xs6TeQTJDr
+status: PUBLISHED
+createdAt: 2024-05-21T19:34:50.437Z
+updatedAt: 2024-05-21T19:38:10.682Z
+publishedAt: 2024-05-21T19:38:10.682Z
+firstPublishedAt: 2024-05-21T19:34:53.918Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: oferta-de-sla-flutuante-entre-diferentes-politicas-de-envio-devido-ao-cache-na-data-estimada-de-30-segundos
+locale: pt
+kiStatus: Backlog
+internalReference: 1036916
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A simulação de logística pode oscilar entre a oferta de SLAs se o cliente tiver políticas de remessa com o mesmo preço, tempo de entrega, SlaType, custo de doca e configuração de armazém, mas prioridade de doca diferente.
+Temos um cache que armazena o tempo de entrega por 30 segundos, portanto, quando uma nova simulação é feita, outra política de remessa com as mesmas configurações que tem um tempo de doca mais longo pode ser oferecida quando não deveria.
+
+
+## Simulação
+
+
+Políticas de remessa A e B com o mesmo tempo total de entrega (1 dia, por exemplo), preço, custo de doca e depósito, mas com prioridades de doca diferentes.
+Faça uma cotação às 16:00:00 em que a política de remessa A com prioridade de doca mais baixa será oferecida, então o resultado da estimativa seria para o dia seguinte às 16:01:00, esses dados são armazenados em cache por 30 segundos;
+Ao fazer uma nova cotação às 16:00:10, por exemplo, será oferecida a política de remessa B com uma prioridade de doca mais alta, porque na primeira cotação o tempo de entrega seria, por exemplo, às 16:01:00, armazenado em cache por 30 segundos, enquanto a segunda cotação B é escolhida porque também tem a estimativa para o dia seguinte, mas às 16:00:00.
+
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa para um cenário com as mesmas configurações descritas acima.
+
+
+
+
+
diff --git a/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md b/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
new file mode 100644
index 000000000..fce85ba37
--- /dev/null
+++ b/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
@@ -0,0 +1,35 @@
+---
+title: 'Erro no layout do controle deslizante ao usar prop infinite como sempre no celular'
+id: 4JERnak05tr2K8ICjjPjrN
+status: PUBLISHED
+createdAt: 2023-10-17T17:38:34.443Z
+updatedAt: 2023-10-17T17:38:35.106Z
+publishedAt: 2023-10-17T17:38:35.106Z
+firstPublishedAt: 2023-10-17T17:38:35.106Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: erro-no-layout-do-controle-deslizante-ao-usar-prop-infinite-como-sempre-no-celular
+locale: pt
+kiStatus: Backlog
+internalReference: 920725
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o layout do controle deslizante é definido como `infinito: "sempre"` no celular, o componente apresenta um bug intermitente. Após algum tempo de rolagem da prateleira, os produtos param de aparecer e, em vez disso, aparece um espaço em branco.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md b/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
new file mode 100644
index 000000000..bc7f192b7
--- /dev/null
+++ b/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
@@ -0,0 +1,52 @@
+---
+title: 'O Slug e o Link retornados na API Catalog Facets têm formatos diferentes.'
+id: 3LbYdhZhjsvUuQNC7VJN5G
+status: PUBLISHED
+createdAt: 2024-03-12T15:43:07.017Z
+updatedAt: 2024-03-12T15:43:08.057Z
+publishedAt: 2024-03-12T15:43:08.057Z
+firstPublishedAt: 2024-03-12T15:43:08.057Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-slug-e-o-link-retornados-na-api-catalog-facets-tem-formatos-diferentes
+locale: pt
+kiStatus: Backlog
+internalReference: 998397
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+API do Catalog Facets descrita aqui: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/facets/search/-term-
+Os objetos de resposta têm o campo "Slug", "Link" e "LinkEncoded". No entanto, esses campos deveriam ter o mesmo formato, mas divergem no objeto PriceRanges quando o valor tem casas decimais.
+
+Exemplo:
+Slug: "de-100-a-199.99"
+Link: "/category-test/de-100-a-199-99?map=c,priceFrom"
+
+O Slug tem o caractere ".", enquanto o Link tem o caractere "-".
+
+
+## Simulação
+
+
+
+1. Tenha uma categoria com um priceRange com valores decimais.
+2. Solicite a API de facetas
+3. Verifique se os caracteres são diferentes
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md b/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
new file mode 100644
index 000000000..96b042ebd
--- /dev/null
+++ b/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
@@ -0,0 +1,44 @@
+---
+title: 'O link de configuração de SMS no modelo de e-mail redireciona o usuário para a página 404'
+id: ZjIBvieBRNlN5lThuvtBf
+status: PUBLISHED
+createdAt: 2024-06-21T17:58:11.722Z
+updatedAt: 2024-06-21T17:58:12.707Z
+publishedAt: 2024-06-21T17:58:12.707Z
+firstPublishedAt: 2024-06-21T17:58:12.707Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: o-link-de-configuracao-de-sms-no-modelo-de-email-redireciona-o-usuario-para-a-pagina-404
+locale: pt
+kiStatus: Backlog
+internalReference: 1054007
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na tela de configuração do modelo do sistema do centro de mensagens, há um link que deve levar o usuário à configuração do aplicativo de envio de SMS, mas esse aplicativo não está mais disponível e o link agora retorna 404, exibindo uma tela com a mensagem "`store/not-found-box-title`".
+
+## Simulação
+
+
+
+Acesse qualquer modelo;
+Vá para a guia SMS e clique no link "Install it through the VTEX App Store".
+Esse link direciona o usuário para a loja de aplicativos, mas o aplicativo não está mais disponível
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md b/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
index 30b9c0f93..e7fbdb55b 100644
--- a/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
+++ b/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
@@ -1,18 +1,18 @@
 ---
-title: 'Alguns endereços autocompletados pelo Google não podem ser salvos em Minha Conta'
+title: 'Alguns endereços preenchidos automaticamente pelo Google não podem ser salvos em My Account'
 id: DgYKHOqC0nnpHKEdcTeXQ
 status: PUBLISHED
 createdAt: 2022-04-28T19:44:12.222Z
-updatedAt: 2023-01-06T17:13:51.809Z
-publishedAt: 2023-01-06T17:13:51.809Z
+updatedAt: 2023-10-18T00:06:40.142Z
+publishedAt: 2023-10-18T00:06:40.142Z
 firstPublishedAt: 2022-05-10T18:17:39.573Z
 contentType: knownIssue
 productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
-slug: alguns-enderecos-autocompletados-pelo-google-nao-podem-ser-salvos-em-minha-conta
+slug: alguns-enderecos-preenchidos-automaticamente-pelo-google-nao-podem-ser-salvos-em-my-account
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 415388
 ---
 
@@ -23,32 +23,28 @@ internalReference: 415388
 </div>
 
 
-Alguns endereços retornados do campo de busca do Google não estão sendo salvos quando adicionados através do fluxo Minha conta, e a IU não retorna nenhum feedback ao usuário.
-NOTA: isto ocorre mesmo que o endereço esteja aparentemente correto
-
-
-##
+Alguns endereços retornados do campo de pesquisa do Google não estão sendo salvos quando adicionados por meio do fluxo Minha conta, e a interface do usuário não retorna nenhum feedback para o usuário.
+OBSERVAÇÃO: isso ocorre mesmo que o endereço esteja aparentemente correto
 
 ## Simulação
 
 
-1- Entrar na minha conta - Meus endereços;
-2- Escolha um endereço digitando-o no campo de busca do Google, localizado nesta área.
+1- Faça login na minha conta - Meus endereços;
+2- Escolha um endereço digitando-o no campo de pesquisa do Google localizado nessa área.
 
 Exemplo:
 * Calle Capón, Cercado de Lima
 * Avenida Nicolás de Piérola
 
 3- Clique em salvar
-4- Observe que o endereço não será salvo, mas também nenhuma mensagem de erro será exibida na interface de usuário.
+4- Observe que o endereço não será salvo, mas também não será exibida nenhuma mensagem de erro na interface do usuário.
 
 
+## Workaround
 
 
-##
+Não há solução disponível para isso.
 
-## Workaround
 
 
-Não há solução disponível para isto.
 
diff --git a/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md b/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
new file mode 100644
index 000000000..be097469c
--- /dev/null
+++ b/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
@@ -0,0 +1,35 @@
+---
+title: 'Algumas funções do componente sticky layout não funcionarão como esperado quando visualizadas no navegador Safari'
+id: 6qXYzloLLowKzEqIUX1IB0
+status: PUBLISHED
+createdAt: 2023-11-08T13:34:35.513Z
+updatedAt: 2024-02-16T20:55:46.662Z
+publishedAt: 2024-02-16T20:55:46.662Z
+firstPublishedAt: 2023-11-08T13:34:36.172Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: algumas-funcoes-do-componente-sticky-layout-nao-funcionarao-como-esperado-quando-visualizadas-no-navegador-safari
+locale: pt
+kiStatus: Backlog
+internalReference: 868535
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas funções do componente sticky layout não funcionam como esperado quando visualizadas no navegador Safari
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
new file mode 100644
index 000000000..0af72c231
--- /dev/null
+++ b/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
@@ -0,0 +1,48 @@
+---
+title: 'Alguns recursos do Inventory Management não estão funcionando corretamente nas contas do portal do vendedor'
+id: uJ4qws662c8pUnyfOV1fV
+status: PUBLISHED
+createdAt: 2024-03-18T17:54:20.400Z
+updatedAt: 2024-03-18T17:54:21.597Z
+publishedAt: 2024-03-18T17:54:21.597Z
+firstPublishedAt: 2024-03-18T17:54:21.597Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: alguns-recursos-do-inventory-management-nao-estao-funcionando-corretamente-nas-contas-do-portal-do-vendedor
+locale: pt
+kiStatus: Backlog
+internalReference: 1001665
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Os recursos de gerenciamento de estoque (como os links para os produtos) não se comportam como esperado nas contas do portal do vendedor. Isso acontece porque esse tipo de conta usa uma versão diferente do catálogo.
+
+O módulo Logistics usa nessa UI uma API do catalogV1.
+
+No entanto, não temos um proxy do catálogo do portal do vendedor para essa API no catalogV1.
+
+O impacto é que os links fornecidos nos produtos não abrem a página do catálogo, mas, em vez disso, retornam um erro.
+
+## Simulação
+
+
+
+1. Tente abrir os links para os produtos em um gerenciamento de inventário do portal do vendedor
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md b/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
new file mode 100644
index 000000000..72e8ea63a
--- /dev/null
+++ b/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
@@ -0,0 +1,50 @@
+---
+title: 'Alguns caracteres especiais não são removidos das pesquisas ou da indexação de produtos'
+id: 3qbzEcCkXpaPA0U23trlwT
+status: DRAFT
+createdAt: 2022-04-26T22:41:20.214Z
+updatedAt: 2023-11-29T20:24:51.268Z
+publishedAt: 
+firstPublishedAt: 2022-04-26T22:42:16.929Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: alguns-caracteres-especiais-nao-sao-removidos-das-pesquisas-ou-da-indexacao-de-produtos
+locale: pt
+kiStatus: Backlog
+internalReference: 382382
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns caracteres especiais não são completamente removidos das palavras-chave pesquisadas ou da indexação de produtos, o que pode afetar as pesquisas em alguns cenários específicos.
+
+Os caracteres conhecidos que levam a esse cenário são vírgulas (`,`), pontos (`.`) e dois-pontos (`:`). Outros são normalmente ignorados e não geram problemas.
+
+Durante o registro de um produto, as vírgulas e os pontos no final das palavras são removidos durante a indexação do produto, mas se estiverem no meio de uma palavra, são mantidos. As palavras-chave são divididas por espaços.
+
+Durante a pesquisa, os dois pontos são um valor reservado e invalidam toda a consulta de texto.
+
+## Simulação
+
+
+Para vírgulas e pontos, um campo de produto que tenha um valor como palavras-chave separadas por vírgulas, como `"car,specialbrand,blue"`, será lido como uma única palavra. A pesquisa por `specialbrand` não encontrará esse produto.
+
+No caso de dois-pontos, um produto com o nome `"vinho tinto: versão especial"` pode ser encontrado por meio da pesquisa por `vinho`, mas a pesquisa por `vinho: versão especial` não funcionará. A pesquisa inteira será inválida e nenhum filtro de texto será aplicado
+
+## Workaround
+
+
+Para vírgulas e pontos, é necessário um espaço após o caractere para dividir as palavras-chave.
+
+Para uma pesquisa com dois pontos, não há solução alternativa.
+
+
+
+
diff --git a/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md b/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md
new file mode 100644
index 000000000..b775b08b9
--- /dev/null
+++ b/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md
@@ -0,0 +1,41 @@
+---
+title: 'Alguns comportamentos inesperados no MasterData'
+id: 4E9jB5vkUMucnAuwUMOGQL
+status: PUBLISHED
+createdAt: 2023-09-18T21:27:15.291Z
+updatedAt: 2023-10-10T21:16:04.759Z
+publishedAt: 2023-10-10T21:16:04.759Z
+firstPublishedAt: 2023-09-18T21:27:15.908Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: alguns-comportamentos-inesperados-no-masterdata
+locale: pt
+kiStatus: Backlog
+internalReference: 669048
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Mesmo com dados disponíveis (documentos), as informações não são retornadas como esperado.
+Esse comportamento pode afetar algumas das seguintes funcionalidades:
+
+- As imagens no Editor do site (CMS) não estão disponíveis, devido à mensagem de erro "_Algo deu errado. Por favor, tente novamente.";
+- Não é possível acessar entidades e seus documentos devido à mensagem de erro "_Ocorreu um erro inesperado. Por favor, tente novamente. Se o problema persistir, entre em contato com o suporte._";
+- O `_sort` não é respeitado na API Search documents;
+- Nenhuma informação é retornada ao usar a API Search Documents (uma resposta vazia, como `[]`), mesmo quando eles contêm documentos.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md b/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
new file mode 100644
index 000000000..c89dbdde0
--- /dev/null
+++ b/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
@@ -0,0 +1,47 @@
+---
+title: 'O erro Something Went Wrong é exibido no administrador do catálogo'
+id: 5TZLWNau0Vo6yp8URPsGcn
+status: PUBLISHED
+createdAt: 2023-09-26T17:00:49.516Z
+updatedAt: 2023-09-26T17:00:50.184Z
+publishedAt: 2023-09-26T17:00:50.184Z
+firstPublishedAt: 2023-09-26T17:00:50.184Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-erro-something-went-wrong-e-exibido-no-administrador-do-catalogo
+locale: pt
+kiStatus: Backlog
+internalReference: 907567
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que o administrador seja usado sem restrições. No entanto, às vezes um erro **Algo deu errado** é exibido no administrador do catálogo.
+
+## Simulação
+
+
+
+1. Abra o administrador do catálogo
+2. Abra uma seção do catálogo, por exemplo: `/admin/Site/ValeForm.aspx`, `Product.aspx`, `ProdutoCategoriaSimilarForm.aspx` ou `SkuForm.aspx`
+3. Receber um erro **Algo deu errado** no admi
+
+## Workaround
+
+
+
+- Tente usar o administrador legado: `.vtexcommercestable.com.br/admin`
+- Tente recarregar a página algumas vezes, ou
+- Tente aguardar alguns minutos e acessar a página novamente
+
+
+
+
+
diff --git a/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md b/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
new file mode 100644
index 000000000..d4b39e756
--- /dev/null
+++ b/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
@@ -0,0 +1,46 @@
+---
+title: 'Mensagem de que algo deu errado ao acessar as rotas /a e /p nos repositórios do Portal'
+id: 2XGAGH8xpNqjJpAir6DKzz
+status: PUBLISHED
+createdAt: 2023-11-30T16:31:45.428Z
+updatedAt: 2023-11-30T16:31:45.990Z
+publishedAt: 2023-11-30T16:31:45.990Z
+firstPublishedAt: 2023-11-30T16:31:45.990Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: mensagem-de-que-algo-deu-errado-ao-acessar-as-rotas-a-e-p-nos-repositorios-do-portal
+locale: pt
+kiStatus: Backlog
+internalReference: 945226
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Espera-se que seja possível pesquisar qualquer termo nas lojas do Portal; no entanto, as letras "A" e "P" não são diretamente pesquisáveis por meio da URL.
+Portanto, uma mensagem "Algo deu errado" será exibida ao acessar as rotas `/a` e `/p` nas lojas do Portal
+
+## Simulação
+
+
+
+1. Vá para uma loja de portal
+2. Acesse o link `site.com/a` ou `site.com/p`
+3. Veja uma mensagem "Algo deu errado" na frent
+
+## Workaround
+
+
+N/A para o caminho `/a
+Registre um redirecionamento no CMS legado de `/p` para `/?ft=p`
+
+
+
+
+
diff --git a/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
new file mode 100644
index 000000000..2b25a7d12
--- /dev/null
+++ b/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -0,0 +1,45 @@
+---
+title: '"Algo deu errado" ao adicionar um endereço incompleto e tentar editá-lo'
+id: 3rWGAr4K86JAetSBJ75q3h
+status: PUBLISHED
+createdAt: 2024-01-02T21:11:17.425Z
+updatedAt: 2024-01-02T21:11:17.955Z
+publishedAt: 2024-01-02T21:11:17.955Z
+firstPublishedAt: 2024-01-02T21:11:17.955Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: algo-deu-errado-ao-adicionar-um-endereco-incompleto-e-tentar-editalo
+locale: pt
+kiStatus: Backlog
+internalReference: 960064
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Durante a etapa de checkout, usando um comprador com um perfil completo, na etapa de preenchimento dos dados de envio, clicando na opção "Entregar em outro endereço", se apenas o código postal for adicionado e o comprador voltar à lista de endereços (usando o botão "voltar ao catálogo de endereços") e clicar em "Atualizar informações de endereço selecionadas", haverá um erro com a mensagem "Algo deu errado".
+
+## Simulação
+
+
+
+- Adicione itens ao carrinho e use um e-mail com um perfil completo;
+- Durante a etapa de Checkout, ao preencher os dados de envio, clique em "Deliver to another address" (Entregar em outro endereço);
+- Adicione um código postal e retorne aos dados de envio clicando no botão "Back to address list" (Voltar à lista de endereços);
+- Clique em "Update selected address information" (Atualizar informações de endereço selecionadas)
+
+## Workaround
+
+
+
+- Atualize a página se o erro for exibido.
+
+
+
+
diff --git a/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md b/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md
index 6d834e491..a47935adf 100644
--- a/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md
+++ b/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md
@@ -3,8 +3,8 @@ title: 'Classificar pelo nome trabalhando de forma diferente em lojas integradas
 id: 96cQG19ZAmAtVT0ykZ4nF
 status: PUBLISHED
 createdAt: 2022-06-20T12:11:22.846Z
-updatedAt: 2022-11-25T21:58:18.041Z
-publishedAt: 2022-11-25T21:58:18.041Z
+updatedAt: 2024-07-01T18:48:26.055Z
+publishedAt: 2024-07-01T18:48:26.055Z
 firstPublishedAt: 2022-06-20T12:11:23.353Z
 contentType: knownIssue
 productTeam: Intelligent Search
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Intelligent Search
 slug: classificar-pelo-nome-trabalhando-de-forma-diferente-em-lojas-integradas-antes-de-uma-data
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 600468
 ---
 
diff --git a/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md b/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
new file mode 100644
index 000000000..0c382c80a
--- /dev/null
+++ b/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
@@ -0,0 +1,43 @@
+---
+title: 'O espaço na propriedade da rua no JSON do código postal afeta a exibição do campo de endereço no checkout'
+id: Rr3wSsdC5hxMS8ttK4kIj
+status: PUBLISHED
+createdAt: 2023-08-01T22:30:35.290Z
+updatedAt: 2024-07-01T18:49:10.379Z
+publishedAt: 2024-07-01T18:49:10.379Z
+firstPublishedAt: 2023-08-01T22:30:36.187Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: o-espaco-na-propriedade-da-rua-no-json-do-codigo-postal-afeta-a-exibicao-do-campo-de-endereco-no-checkout
+locale: pt
+kiStatus: No Fix
+internalReference: 872935
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao ativar o uso da API de código postal no formulário de endereço para países que não estão no modelo BR (país, estado, cidade, bairro, rua), esses países que não têm todos esses campos preenchidos na API e precisam ser capazes de inserir os outros dados de endereço no formulário de endereço no checkout, o campo rua do bloco de endereço não estará disponível se a propriedade rua do JSON estiver com espaço, pois será entendido como preenchido e válido, o que não permite prosseguir com o pedido.
+
+
+## Simulação
+
+
+Crie um carrinho em uma loja EMEA que use o código postal e o formulário de endereço e, na base do código postal, o campo street esteja com espaço " " .
+O campo de endereço não estará disponível para ser preenchido
+
+## Workaround
+
+
+Não existe
+
+
+
+
+
diff --git a/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md b/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
index cb2ba810b..6c7bf652e 100644
--- a/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
+++ b/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
@@ -3,8 +3,8 @@ title: 'O espaço na identificação do armazém faz com que os pedidos logísti
 id: M8SsnABs2HgYsUvNnjCFx
 status: PUBLISHED
 createdAt: 2022-09-20T21:51:05.157Z
-updatedAt: 2023-01-05T19:34:07.126Z
-publishedAt: 2023-01-05T19:34:07.126Z
+updatedAt: 2024-02-16T20:24:53.145Z
+publishedAt: 2024-02-16T20:24:53.145Z
 firstPublishedAt: 2022-09-20T21:51:05.702Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: o-espaco-na-identificacao-do-armazem-faz-com-que-os-pedidos-logisticos-internos-falhem
 locale: pt
-kiStatus: Fixed
+kiStatus: No Fix
 internalReference: 654370
 ---
 
diff --git a/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md b/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
index 2feb22c11..d41d06ac8 100644
--- a/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
+++ b/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
@@ -3,8 +3,8 @@ title: 'Caracteres especiais não podem ser usados para busca CNPJ em MasterData
 id: 4sgob00QXkGYPC3TjSpQeN
 status: PUBLISHED
 createdAt: 2022-06-21T15:35:26.675Z
-updatedAt: 2022-11-25T22:13:02.870Z
-publishedAt: 2022-11-25T22:13:02.870Z
+updatedAt: 2023-08-07T13:52:30.392Z
+publishedAt: 2023-08-07T13:52:30.392Z
 firstPublishedAt: 2022-06-21T15:35:27.341Z
 contentType: knownIssue
 productTeam: Storage
diff --git a/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md b/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
new file mode 100644
index 000000000..4a04812ee
--- /dev/null
+++ b/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
@@ -0,0 +1,48 @@
+---
+title: 'Caracteres especiais no invoiceNumber causam falha no fluxo pós-compra'
+id: 1tVPSLsB9SSZIF1KrNn3k2
+status: PUBLISHED
+createdAt: 2023-12-14T18:31:27.213Z
+updatedAt: 2023-12-14T18:31:27.801Z
+publishedAt: 2023-12-14T18:31:27.801Z
+firstPublishedAt: 2023-12-14T18:31:27.801Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: caracteres-especiais-no-invoicenumber-causam-falha-no-fluxo-poscompra
+locale: pt
+kiStatus: Backlog
+internalReference: 953285
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, o SNO (Shipping Notification Order) aceita que um número de fatura (invoiceNumber) seja enviado via API e UI com um "caractere especial" no final ou no início dos dados, por exemplo: "#123456".
+
+No entanto, quando as faturas são recebidas nesse formato, alguns fluxos executados pelo sistema envolvido no fluxo pós-compra acabam retornando um erro porque não conseguem processar ou repassar o valor recebido. Exemplos de fluxos que podem falhar incluem atualizações de rastreamento, atualizações de status de pedidos faturados, comunicação com o sistema de hub de gifcard e qualquer outro sistema que use dados invoiceNumber pode ter seu fluxo comprometido devido ao uso de caracteres especiais no campo invoiceNumber.
+
+## Simulação
+
+
+1- Fature um pedido inserindo o seguinte exemplo de número de fatura: "#123456"; (caracteres especiais no início do número ou no final)
+
+2- Observe que o pedido não será atualizado para o status de faturado
+
+3- No caso de fluxos que envolvam um vendedor, no Get Order do pedido do vendedor será possível ver a fatura salva, mas mesmo assim o pedido do marketplace não será atualizado para faturado, pois o sistema não conseguirá repassar a fatura
+
+## Workaround
+
+
+Para esses casos, a solução alternativa é não usar os "caracteres especiais" na composição do invoiceNumber.
+
+
+
+
+
+
diff --git a/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md b/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
index 4da518816..eb91ad3da 100644
--- a/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
+++ b/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
@@ -3,8 +3,8 @@ title: 'Caracteres especiais no nome SKU quebra a seleção SKU nas páginas PDP
 id: 1G4FSBVZqn44ke7YJTuBJA
 status: PUBLISHED
 createdAt: 2022-03-16T16:26:36.035Z
-updatedAt: 2022-11-25T22:11:14.593Z
-publishedAt: 2022-11-25T22:11:14.593Z
+updatedAt: 2024-02-16T20:29:47.269Z
+publishedAt: 2024-02-16T20:29:47.269Z
 firstPublishedAt: 2022-03-16T16:26:36.503Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: caracteres-especiais-no-nome-sku-quebra-a-selecao-sku-nas-paginas-pdp-do-portal-web-store-para-caixa-de-radio-tipo-de-selecao-de-categoria
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 337933
 ---
 
diff --git a/docs/known-issues/pt/specifications-multiplied-on-catalog.md b/docs/known-issues/pt/specifications-multiplied-on-catalog.md
new file mode 100644
index 000000000..52ed98e3c
--- /dev/null
+++ b/docs/known-issues/pt/specifications-multiplied-on-catalog.md
@@ -0,0 +1,41 @@
+---
+title: 'Especificações multiplicadas pelo catálogo'
+id: 2d4LXPrbVibMR8atXO6o8X
+status: PUBLISHED
+createdAt: 2023-10-16T12:48:03.714Z
+updatedAt: 2023-10-16T12:48:59.814Z
+publishedAt: 2023-10-16T12:48:59.814Z
+firstPublishedAt: 2023-10-16T12:48:04.717Z
+contentType: knownIssue
+productTeam: Marketplace
+author: 2mXZkbi0oi061KicTExNjo
+tag: Marketplace
+slug: especificacoes-multiplicadas-pelo-catalogo
+locale: pt
+kiStatus: Backlog
+internalReference: 919761
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O marketplace pode aprovar produtos enviados por vendedores no módulo Received Skus.
+
+Quando um produto tem uma especificação de sku que corresponde à especificação existente na categoria do marketplace, mas é um novo valor, esse novo valor é criado na especificação do marketplace.
+
+Os valores multiplicados podem ocorrer quando mais de um sku com o mesmo "novo valor" está sendo aprovado ao mesmo tempo em Skus recebidos na mesma categoria (ou árvore) em que a especificação foi criada.
+
+Se a especificação for criada na categoria raiz (não recomendado), esse cenário poderá ocorrer mais facilmente.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md b/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
index a8a40ee13..d9fccf72c 100644
--- a/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
+++ b/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
@@ -3,8 +3,8 @@ title: 'spotPrice do skuJson é incorreto para produtos com múltiplos Vendedore
 id: 6rgLJCE1DYPXZj1Pqt6hA2
 status: PUBLISHED
 createdAt: 2022-02-24T15:32:40.223Z
-updatedAt: 2022-11-25T22:10:27.000Z
-publishedAt: 2022-11-25T22:10:27.000Z
+updatedAt: 2024-02-16T20:30:08.928Z
+publishedAt: 2024-02-16T20:30:08.928Z
 firstPublishedAt: 2022-02-24T15:32:41.286Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: spotprice-do-skujson-e-incorreto-para-produtos-com-multiplos-vendedores
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 264791
 ---
 
diff --git a/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md b/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md
new file mode 100644
index 000000000..466a9ec2b
--- /dev/null
+++ b/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md
@@ -0,0 +1,43 @@
+---
+title: 'O status na lista de transações não corresponde ao estado real'
+id: 3L0eXIO6aHmv9GSlPwCq3t
+status: PUBLISHED
+createdAt: 2024-03-22T16:23:32.369Z
+updatedAt: 2024-03-22T16:23:33.304Z
+publishedAt: 2024-03-22T16:23:33.304Z
+firstPublishedAt: 2024-03-22T16:23:33.304Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-status-na-lista-de-transacoes-nao-corresponde-ao-estado-real
+locale: pt
+kiStatus: Backlog
+internalReference: 1004883
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Algumas transações podem não corresponder ao estado real quando você as abre (problema de indexação).
+
+## Simulação
+
+
+Não há como reproduzir, pois isso acontece com transações aleatórias.
+
+
+
+## Workaround
+
+
+NA
+
+
+
+
+
diff --git a/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md b/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md
index 0344c3f4a..398fb47ea 100644
--- a/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md
+++ b/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md
@@ -1,18 +1,18 @@
 ---
-title: 'A mudança de estoque é concluída mesmo após o recebimento do erro 500'
+title: 'A alteração de estoque é concluída mesmo depois de receber o erro 500'
 id: 3dlP8iOBiL2tfPRvjm2kUZ
 status: PUBLISHED
 createdAt: 2022-06-20T12:40:08.834Z
-updatedAt: 2022-11-25T21:59:29.796Z
-publishedAt: 2022-11-25T21:59:29.796Z
+updatedAt: 2024-07-03T18:12:47.665Z
+publishedAt: 2024-07-03T18:12:47.665Z
 firstPublishedAt: 2022-06-20T12:40:09.126Z
 contentType: knownIssue
 productTeam: Logistics
 author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
-slug: a-mudanca-de-estoque-e-concluida-mesmo-apos-o-recebimento-do-erro-500
+slug: a-alteracao-de-estoque-e-concluida-mesmo-depois-de-receber-o-erro-500
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 388176
 ---
 
@@ -23,16 +23,14 @@ internalReference: 388176
 </div>
 
 
-O cliente está tentando atualizar a quantidade do sku no inventário e o pedido recebeu erro 500. Apesar do erro, a quantidade em estoque é alterada.
-
-
+O cliente está tentando atualizar a quantidade de sku no inventário e a solicitação recebeu o erro 500. Apesar do erro, a quantidade em estoque é alterada.
 
 ## Simulação
 
 
 Não foi possível reproduzir o erro.
 
-Mas na resposta vemos o erro 500, e no inventário vemos o mesmo valor antes da atualização.
+Mas, na resposta, vemos o erro 500 e, no inventário, vemos o mesmo valor antes da atualização.
 
 
 
@@ -40,5 +38,5 @@ Mas na resposta vemos o erro 500, e no inventário vemos o mesmo valor antes da
 ## Workaround
 
 
-Não há solução. Mas é importante verificar que esta atualização ocorreu.
+Não há solução alternativa. Mas é importante verificar se essa atualização ocorreu.
 
diff --git a/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md b/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
index 846be1557..2b4ed48a5 100644
--- a/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
+++ b/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
@@ -3,8 +3,8 @@ title: 'API do catálogo da unidade de estocagem permite valores de condição c
 id: 1ONAspL4Wj9fdu2tYcX4Ur
 status: PUBLISHED
 createdAt: 2023-03-10T20:44:01.459Z
-updatedAt: 2023-03-10T20:44:02.006Z
-publishedAt: 2023-03-10T20:44:02.006Z
+updatedAt: 2024-07-01T18:48:57.278Z
+publishedAt: 2024-07-01T18:48:57.278Z
 firstPublishedAt: 2023-03-10T20:44:02.006Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: api-do-catalogo-da-unidade-de-estocagem-permite-valores-de-condicao-comercial-invalidos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 769053
 ---
 
diff --git a/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 0c30e281a..7effbeb13 100644
--- a/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -3,7 +3,7 @@ title: 'StockKeepingUnitByEAN returns 404 for EANs with "/"'
 id: Pp3lE5Gu54gOw6liInte4
 status: DRAFT
 createdAt: 2022-02-25T12:23:55.903Z
-updatedAt: 2022-06-28T16:56:27.547Z
+updatedAt: 2024-02-16T20:28:49.215Z
 publishedAt: 
 firstPublishedAt: 
 contentType: knownIssue
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: stockkeepingunitbyean-returns-404-for-eans-with-
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 479244
 ---
 
diff --git a/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md b/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
index 7f20118d7..1381f6cda 100644
--- a/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
+++ b/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
@@ -3,8 +3,8 @@ title: 'O método StockKeepingUnitInsertUpdate WebService permite a inserção d
 id: 7wQ9uztQCTIQIWajMd6vaU
 status: PUBLISHED
 createdAt: 2022-01-21T15:19:32.095Z
-updatedAt: 2022-11-25T21:42:03.381Z
-publishedAt: 2022-11-25T21:42:03.381Z
+updatedAt: 2024-02-16T20:29:15.782Z
+publishedAt: 2024-02-16T20:29:15.782Z
 firstPublishedAt: 2022-11-02T13:54:17.227Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: o-metodo-stockkeepingunitinsertupdate-webservice-permite-a-insercao-de-refid-existentes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 419460
 ---
 
diff --git a/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md b/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md
new file mode 100644
index 000000000..ebe7fd8a3
--- /dev/null
+++ b/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md
@@ -0,0 +1,43 @@
+---
+title: 'As permissões do Storefront consideram as organizações inativas'
+id: 2GANYaXFMQpLGADajl4CbS
+status: PUBLISHED
+createdAt: 2023-10-27T22:08:14.267Z
+updatedAt: 2023-10-27T22:15:24.802Z
+publishedAt: 2023-10-27T22:15:24.802Z
+firstPublishedAt: 2023-10-27T22:08:14.965Z
+contentType: knownIssue
+productTeam: B2B
+author: 2mXZkbi0oi061KicTExNjo
+tag: B2B
+slug: as-permissoes-do-storefront-consideram-as-organizacoes-inativas
+locale: pt
+kiStatus: Backlog
+internalReference: 927174
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um usuário tem mais de uma organização atribuída a ele e a primeira registrada está inativa, ela não é reconhecida como uma organização atribuída após o login.
+
+## Simulação
+
+
+
+- Crie duas organizações e atribua o mesmo usuário/e-mail;
+- Inative a primeira organização criada;
+- Faça login no site
+
+## Workaround
+
+
+Remova o usuário/e-mail da organização inativa.
+
+
+
+
diff --git a/docs/known-issues/pt/stucked-not-found-routes-on-platform.md b/docs/known-issues/pt/stucked-not-found-routes-on-platform.md
index b81557ffe..2ab1b3b49 100644
--- a/docs/known-issues/pt/stucked-not-found-routes-on-platform.md
+++ b/docs/known-issues/pt/stucked-not-found-routes-on-platform.md
@@ -1,16 +1,16 @@
 ---
-title: 'Rotas presas não encontradas na plataforma'
+title: 'Rotas bloqueadas e não encontradas na plataforma'
 id: iAGlRJtK1KMBGxH2tAsrX
 status: PUBLISHED
 createdAt: 2023-04-19T15:54:48.241Z
-updatedAt: 2023-04-19T16:00:28.874Z
-publishedAt: 2023-04-19T16:00:28.874Z
+updatedAt: 2023-06-28T15:56:47.493Z
+publishedAt: 2023-06-28T15:56:47.493Z
 firstPublishedAt: 2023-04-19T15:54:48.788Z
 contentType: knownIssue
 productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
-slug: rotas-presas-nao-encontradas-na-plataforma
+slug: rotas-bloqueadas-e-nao-encontradas-na-plataforma
 locale: pt
 kiStatus: Backlog
 internalReference: 793457
@@ -23,33 +23,26 @@ internalReference: 793457
 </div>
 
 
-Devido à falta de notificações e problemas de cache, algumas rotas são armazenadas em cache em não encontradas no vbase e no reescritor por meio de store-indexer impactando a experiência quando essas rotas estão disponíveis novamente, sendo necessário enviar uma nova indexação e novas notificações ou esperar o tempo de store-indexer para acionar a nova indexação novamente
-
-
-##
+Devido à falta de notificações e a problemas de cache, algumas rotas são armazenadas em cache como não encontradas no vbase e no rewriter pelo store-indexer, afetando a experiência quando essas rotas estão disponíveis novamente, sendo necessário enviar uma nova indexação e novas notificações ou aguardar o tempo do store-indexer para acionar a nova indexação novamente
 
 ## Simulação
 
 
-Esta é uma questão intermitente, portanto, basicamente, não é fácil de simular, mas uma vez que você armazena rotas no vbase e/ou reescritor como não encontrado, há uma chance de não receber uma notificação em um curto espaço de tempo para atualizar que
-
-
-
-##
+Esse é um problema intermitente, portanto, basicamente, não é fácil de simular, mas uma vez que você armazena rotas no vbase e/ou no rewriter como não encontradas, há uma chance de não receber uma notificação em um curto espaço de tempo para atualizar isso
 
 ## Workaround
 
 
 Para produtos,
 
-- Tente não armazenar rotas dentro do reescritor, a menos que seja estritamente necessário
-- Redefinir ou remover rotas no vbase indo para o aplicativo reescritor - admin/apps/vtex.rewriter@x.x.x/setup/ - e atualizando sua versão de rotas para uma nova
-- Reindexar as rotas utilizando store-indexer
-- Salvar o produto para notificar a emissora de que o produto mudou e então ele precisa enviar novas notificações
+- Tente não armazenar rotas dentro do rewriter, a menos que seja estritamente necessário
+- Redefina ou remova as rotas no vbase acessando o aplicativo do rewriter - admin/apps/vtex.rewriter@x.x.x/setup/ - e atualizando a versão das rotas para uma nova
+- Reindexar as rotas usando o store-indexer
+- Salvar o produto para notificar o transmissor de que o produto foi alterado e que ele precisa enviar novas notificações
 Para outras rotas
 
-- Verificar se a rota está armazenada em reescrita como não encontrada se for atualizada para novos valores
-- Verifique se a página tipo API está presa em uma página não encontrada e notifique a equipe do catálogo: https://.vtexcommercestable.com.br/api/catalog_system/pub/portal/pagetype/
+- Verifique se a rota está armazenada no rewriter como não encontrada se ela for atualizada para novos valores
+- Verifique se a API do tipo de página está presa em um não encontrado e notifique a equipe do catálogo: `https://.vtexcommercestable.com.br/api/catalog_system/pub/portal/pagetype/`
 
 
 
diff --git a/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md b/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md
index c4e9681f4..b7c8ea467 100644
--- a/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md
+++ b/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md
@@ -3,8 +3,8 @@ title: 'O relatório dos assinantes não mostra corretamente as assinaturas ativ
 id: 4sqvm1v4CbCJLQ3HBBVTmp
 status: PUBLISHED
 createdAt: 2022-05-27T19:44:57.301Z
-updatedAt: 2022-11-25T22:02:30.682Z
-publishedAt: 2022-11-25T22:02:30.682Z
+updatedAt: 2024-07-01T18:48:23.947Z
+publishedAt: 2024-07-01T18:48:23.947Z
 firstPublishedAt: 2022-05-27T19:44:57.688Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: o-relatorio-dos-assinantes-nao-mostra-corretamente-as-assinaturas-ativas
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 587556
 ---
 
diff --git a/docs/known-issues/pt/subscription-event-history-out-of-order.md b/docs/known-issues/pt/subscription-event-history-out-of-order.md
new file mode 100644
index 000000000..6a34dfbe4
--- /dev/null
+++ b/docs/known-issues/pt/subscription-event-history-out-of-order.md
@@ -0,0 +1,46 @@
+---
+title: 'Histórico de eventos de assinatura fora de ordem'
+id: 5w78uE60pzjfOagGnRA2d5
+status: PUBLISHED
+createdAt: 2023-08-01T18:53:21.754Z
+updatedAt: 2023-08-01T18:53:22.303Z
+publishedAt: 2023-08-01T18:53:22.303Z
+firstPublishedAt: 2023-08-01T18:53:22.303Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: historico-de-eventos-de-assinatura-fora-de-ordem
+locale: pt
+kiStatus: Backlog
+internalReference: 872697
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, o Histórico de assinatura na área Minha assinatura não exibe os eventos em uma ordem predefinida, portanto, pode mostrar os eventos em ordem não cronológica;
+
+## Simulação
+
+
+Usando uma assinatura que teve mais de um pedido gerado;
+
+1- Entre na área de histórico;
+2- A lista de eventos exibida não estará em ordem cronológica;
+
+OBSERVAÇÃO: Em alguns casos, o cenário pode não ser percebido porque apenas alguns eventos estão fora da ordem cronológica
+
+## Workaround
+
+
+
+Atualmente, não há nenhuma solução alternativa para esse comportamento
+
+
+
+
diff --git a/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md b/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md
index beac5b4e7..5a7559964 100644
--- a/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md
+++ b/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md
@@ -3,8 +3,8 @@ title: 'Painel de controle das assinaturas com informações conflitantes'
 id: WvoqrD7xvaAJ6NVOLpU1G
 status: PUBLISHED
 createdAt: 2022-05-27T20:01:11.189Z
-updatedAt: 2022-11-25T22:02:26.699Z
-publishedAt: 2022-11-25T22:02:26.699Z
+updatedAt: 2024-02-16T20:28:30.718Z
+publishedAt: 2024-02-16T20:28:30.718Z
 firstPublishedAt: 2022-05-27T20:01:11.715Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: painel-de-controle-das-assinaturas-com-informacoes-conflitantes
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 587579
 ---
 
diff --git a/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md b/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
new file mode 100644
index 000000000..95cd2a824
--- /dev/null
+++ b/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
@@ -0,0 +1,43 @@
+---
+title: 'Assinaturas não executadas devido a falha na indexação de dados ou falha na consulta de dados mestre'
+id: 1PspxNexEEz4GvJ5BpZZgH
+status: PUBLISHED
+createdAt: 2024-01-04T20:27:03.576Z
+updatedAt: 2024-07-09T17:24:39.295Z
+publishedAt: 2024-07-09T17:24:39.295Z
+firstPublishedAt: 2024-01-04T20:27:04.193Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: assinaturas-nao-executadas-devido-a-falha-na-indexacao-de-dados-ou-falha-na-consulta-de-dados-mestre
+locale: pt
+kiStatus: Backlog
+internalReference: 961526
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A criação de solicitações de assinatura depende do retorno de uma consulta feita ao banco de dados de assinaturas; essa consulta é feita periodicamente para identificar quais assinaturas devem ser executadas naquele período; se essa consulta falhar ou não retornar uma assinatura específica, seu ciclo não será executado e nenhum erro será registrado, resultando, assim, em uma assinatura com a nextPurchaseDate no passado.
+
+## Simulação
+
+
+Não temos como simular esse cenário devido à dependência de outros sistemas
+
+## Workaround
+
+
+Para ajustar a `nextPurchaseDate`, o usuário final pode pausar a assinatura e reativá-la. Essa ação fará com que o sistema de assinatura recalcule a data de execução e o `nextPurchaseDate` será atualizado corretamente.
+
+Ou o cliente pode atualizar a `nextPurchaseDate` da assinatura do usuário para uma data futura por meio da API.
+
+
+
+
+
diff --git a/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md b/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
new file mode 100644
index 000000000..19d22b4d1
--- /dev/null
+++ b/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
@@ -0,0 +1,43 @@
+---
+title: 'A simulação de assinaturas retornou um erro quando o PickupPointID contém caracteres especiais'
+id: aM2So6TmVffZ1ywtQsknS
+status: PUBLISHED
+createdAt: 2023-09-19T17:31:47.442Z
+updatedAt: 2024-07-01T18:49:12.303Z
+publishedAt: 2024-07-01T18:49:12.303Z
+firstPublishedAt: 2023-09-19T17:31:48.217Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: a-simulacao-de-assinaturas-retornou-um-erro-quando-o-pickuppointid-contem-caracteres-especiais
+locale: pt
+kiStatus: No Fix
+internalReference: 903332
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Para realizar um pedido de assinatura ou atualizar uma assinatura, o sistema de assinatura realiza uma simulação e, nessa simulação, utiliza os dados de entrega retornados pelo sistema de logística e, se nesses dados houver um ponto de coleta cujo ID esteja sublinhado, o sistema de assinatura não conseguirá escolher o SLA corretamente, gerando o erro "Invalid AddressProvider:...." na simulação e, consequentemente, não gerará o pedido.
+
+## Simulação
+
+
+1- Crie um ponto de coleta cujo ID tenha um sublinhado
+2- Faça uma solicitação de assinatura escolhendo o ponto de coleta criado na etapa 1.
+3- Aguarde a execução do primeiro ciclo e veja que ele não é executado e que o painel de assinatura registra um erro dizendo que o endereço é inválido
+
+## Workaround
+
+
+Exclua o ponto de coleta cujo ID está sublinhado, crie um novo e atualize a assinatura para que ela use esse novo ponto de coleta.
+
+
+
+
+
diff --git a/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md b/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md
index 1aca47e3c..ee859291c 100644
--- a/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md
+++ b/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md
@@ -3,8 +3,8 @@ title: 'Palavras substitutas com menos de 3 caracteres não funcionam'
 id: 5sAdcBkmVVnRoQD3WUBNJ0
 status: PUBLISHED
 createdAt: 2022-06-08T20:03:47.576Z
-updatedAt: 2022-11-25T21:45:35.491Z
-publishedAt: 2022-11-25T21:45:35.491Z
+updatedAt: 2024-07-01T18:47:49.328Z
+publishedAt: 2024-07-01T18:47:49.328Z
 firstPublishedAt: 2022-06-08T20:03:48.005Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: palavras-substitutas-com-menos-de-3-caracteres-nao-funcionam
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 282500
 ---
 
diff --git a/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md b/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
new file mode 100644
index 000000000..92881fa7f
--- /dev/null
+++ b/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
@@ -0,0 +1,45 @@
+---
+title: 'As informações de resumo são traduzidas para o inglês após o login por meio da atualização das informações de endereço selecionadas'
+id: 6g05yZcdGHZqm0zeozUH8f
+status: PUBLISHED
+createdAt: 2024-02-07T14:58:10.527Z
+updatedAt: 2024-02-07T14:58:11.389Z
+publishedAt: 2024-02-07T14:58:11.389Z
+firstPublishedAt: 2024-02-07T14:58:11.389Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: as-informacoes-de-resumo-sao-traduzidas-para-o-ingles-apos-o-login-por-meio-da-atualizacao-das-informacoes-de-endereco-selecionadas
+locale: pt
+kiStatus: Backlog
+internalReference: 978571
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Nas contas em espanhol, fazer login no checkout por meio de "Atualizar informações de endereço selecionadas" após a identificação com um perfil completo faz com que alguns textos do resumo sejam traduzidos para o inglês.
+
+## Simulação
+
+
+
+- Adicione um item ao carrinho e identifique-o usando um e-mail com um perfil completo para que os dados sejam preenchidos automaticamente;
+- Os dados pessoais e o endereço serão mascarados;
+- Vá para a etapa de envio e clique em "Update selected address information" (Atualizar informações de endereço selecionadas);
+- Faça o login;
+- Observe que alguns textos do Resumo serão alterados para o inglês
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md b/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
new file mode 100644
index 000000000..fca50c734
--- /dev/null
+++ b/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
@@ -0,0 +1,45 @@
+---
+title: 'Passar a imagem do produto depois de aumentar o zoom não reverte o zoom, causando problemas de exibição'
+id: 41UVOcLabjyv29Buupj1MO
+status: PUBLISHED
+createdAt: 2024-01-29T18:05:22.470Z
+updatedAt: 2024-01-29T18:05:23.035Z
+publishedAt: 2024-01-29T18:05:23.035Z
+firstPublishedAt: 2024-01-29T18:05:23.035Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: passar-a-imagem-do-produto-depois-de-aumentar-o-zoom-nao-reverte-o-zoom-causando-problemas-de-exibicao
+locale: pt
+kiStatus: Backlog
+internalReference: 491180
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o vtex.store-components product-image, ao deslizar uma imagem para o lado depois de clicar nela para aumentar o zoom, a primeira imagem continuará ampliada, causando problemas de renderização quando o usuário deslizar de volta para ela.
+
+## Simulação
+
+
+Em um PDP que usa vtex.store-components product-image, acesse a versão móvel de um produto com pelo menos duas imagens.
+Clique para ampliar a primeira imagem e, em seguida, passe para a próxima.
+Clique para ampliar a segunda e deslize de volta para a primeira.
+Fazer isso para frente e para trás acabará causando alguns problemas de exibição na imagem atualmente ampliada.
+Clicar na imagem novamente para reduzir o zoom a redefine de volta ao normal.
+
+
+
+## Workaround
+
+
+Use setas para navegar entre as imagens e reduzir a chance de os usuários optarem por deslizá-las.
+
+Defina a propriedade "zoomMode": "hover" ou "zoomMode": "open-modal". Isso impede o deslizamento quando a imagem é ampliada, mas altera ligeiramente o comportamento.
+
diff --git a/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md b/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md
new file mode 100644
index 000000000..ca6d8201a
--- /dev/null
+++ b/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md
@@ -0,0 +1,42 @@
+---
+title: 'Sinônimos importam apresentar sucesso mesmo para ações fracassadas'
+id: 4EhvPXp1vXBf2596mANlX6
+status: PUBLISHED
+createdAt: 2024-02-19T22:05:46.953Z
+updatedAt: 2024-02-19T22:05:47.817Z
+publishedAt: 2024-02-19T22:05:47.817Z
+firstPublishedAt: 2024-02-19T22:05:47.817Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: sinonimos-importam-apresentar-sucesso-mesmo-para-acoes-fracassadas
+locale: pt
+kiStatus: Backlog
+internalReference: 984557
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A importação de sinônimos para arquivos CSV retornará uma mensagem de sucesso mesmo para ações que falharam.
+
+## Simulação
+
+
+Tente importar um arquivo CSV inválido, por exemplo, fora da formatação esperada de três colunas.
+
+
+
+## Workaround
+
+
+Não é necessário. Observe que os sinônimos importados com sucesso devem aparecer instantaneamente na lista depois de recarregar a página.
+
+
+
+
diff --git a/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md b/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md
new file mode 100644
index 000000000..4843a6d2d
--- /dev/null
+++ b/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md
@@ -0,0 +1,42 @@
+---
+title: 'Sinônimos não mostrados na pesquisa explicada'
+id: 6twjWHNHdarFV5pz1aTfeb
+status: PUBLISHED
+createdAt: 2023-03-20T16:57:15.640Z
+updatedAt: 2023-10-18T00:50:47.829Z
+publishedAt: 2023-10-18T00:50:47.829Z
+firstPublishedAt: 2023-03-20T16:57:16.425Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: sinonimos-nao-mostrados-na-pesquisa-explicada
+locale: pt
+kiStatus: Backlog
+internalReference: 774307
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Alguns produtos podem não apresentar seus sinônimos na página de administração da pesquisa explicada. Isso geralmente acontece com sinônimos unidirecionais.
+
+## Simulação
+
+
+Crie um sinônimo unidirecional e verifique-o na busca explicada. Se ele não aparecer, isso não significa que o sinônimo não esteja funcionando.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md b/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md
index fc00b5ab0..a980b4f4e 100644
--- a/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md
+++ b/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md
@@ -3,8 +3,8 @@ title: 'Sistema considerando vendedor 1 para limite de vendedores de regras'
 id: 1bUax0hSCVrnFPZ4g1VWOa
 status: PUBLISHED
 createdAt: 2022-04-20T20:43:57.392Z
-updatedAt: 2022-11-25T21:52:50.788Z
-publishedAt: 2022-11-25T21:52:50.788Z
+updatedAt: 2024-02-16T20:28:37.189Z
+publishedAt: 2024-02-16T20:28:37.189Z
 firstPublishedAt: 2022-04-20T20:43:57.844Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: sistema-considerando-vendedor-1-para-limite-de-vendedores-de-regras
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 564614
 ---
 
diff --git a/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md b/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md
new file mode 100644
index 000000000..c497f8ea5
--- /dev/null
+++ b/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md
@@ -0,0 +1,46 @@
+---
+title: 'Às vezes, as tags não aparecem na visualização PLP do formato de lista'
+id: 4CPSP7GjBfUgxFvmnAhK8z
+status: PUBLISHED
+createdAt: 2024-02-15T13:58:42.405Z
+updatedAt: 2024-02-15T13:58:43.494Z
+publishedAt: 2024-02-15T13:58:43.494Z
+firstPublishedAt: 2024-02-15T13:58:43.494Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: as-vezes-as-tags-nao-aparecem-na-visualizacao-plp-do-formato-de-lista
+locale: pt
+kiStatus: No Fix
+internalReference: 982200
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao exibir o PLP na visualização de lista, as tags dos itens.
+
+## Simulação
+
+
+Crie tags para seus itens e faça as alterações necessárias nas configurações.
+Permita que o PLP seja visualizado no estilo de grade e de lista.
+No estilo de grade, as tags aparecerão como deveriam.
+No estilo de lista, as tags estão ausentes.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
+
diff --git a/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md b/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
new file mode 100644
index 000000000..bd67a8865
--- /dev/null
+++ b/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
@@ -0,0 +1,46 @@
+---
+title: 'A interface do usuário do formulário de imposto não está exibindo o menu suspenso de tags de marketing'
+id: Xqg6yYfOvVtP0TwZ2RIAk
+status: PUBLISHED
+createdAt: 2024-07-01T13:33:50.657Z
+updatedAt: 2024-07-01T13:34:05.936Z
+publishedAt: 2024-07-01T13:34:05.936Z
+firstPublishedAt: 2024-07-01T13:33:51.430Z
+contentType: knownIssue
+productTeam: Pricing & Promotions
+author: 2mXZkbi0oi061KicTExNjo
+tag: Pricing & Promotions
+slug: a-interface-do-usuario-do-formulario-de-imposto-nao-esta-exibindo-o-menu-suspenso-de-tags-de-marketing
+locale: pt
+kiStatus: Backlog
+internalReference: 1058148
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao salvar impostos no módulo de promoções, o valor do menu suspenso para "pelo menos um dos seguintes" ou "todos os seguintes" não é mostrado depois que o imposto é salvo. Consequentemente, o usuário não consegue descobrir qual deles está sendo usado.
+
+## Simulação
+
+
+1 - No módulo de promoções, abra o formulário de imposto.
+2 - Preencha o formulário Tags de marketing com vários valores.
+3 - Salve o formulário
+4 - Verifique novamente, o formulário sairá vazio:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/kGbgj8MON0fVzgmv19hKS1F9u/?name=image.png
+
+## Workaround
+
+
+-
+
+
+
+
+
diff --git a/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md b/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
new file mode 100644
index 000000000..6cf1117f1
--- /dev/null
+++ b/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
@@ -0,0 +1,41 @@
+---
+title: 'A solicitação do hub de impostos não soma os descontos quando o preço manual é aplicado'
+id: 3p8mpZALGS95pB9j4CclHi
+status: PUBLISHED
+createdAt: 2023-11-08T18:07:23.968Z
+updatedAt: 2024-07-01T18:49:18.565Z
+publishedAt: 2024-07-01T18:49:18.565Z
+firstPublishedAt: 2023-11-08T18:07:24.393Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-solicitacao-do-hub-de-impostos-nao-soma-os-descontos-quando-o-preco-manual-e-aplicado
+locale: pt
+kiStatus: No Fix
+internalReference: 932667
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+## Simulação
+
+
+
+- Defina um preço manual menor do que o preço atual de um item;
+- A solicitação do hub de impostos não somará o desconto nos totais
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md b/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
new file mode 100644
index 000000000..b83e31172
--- /dev/null
+++ b/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
@@ -0,0 +1,43 @@
+---
+title: 'O Tax Service considera o mesmo preço para itens que aparecem mais de uma vez ao usar a opção de montagem'
+id: 62a1S9SZmGsY58BcV6D58C
+status: PUBLISHED
+createdAt: 2023-09-25T13:27:15.638Z
+updatedAt: 2023-09-27T12:47:49.130Z
+publishedAt: 2023-09-27T12:47:49.130Z
+firstPublishedAt: 2023-09-25T13:27:16.233Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-tax-service-considera-o-mesmo-preco-para-itens-que-aparecem-mais-de-uma-vez-ao-usar-a-opcao-de-montagem
+locale: pt
+kiStatus: Fixed
+internalReference: 906518
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar Opções de montagem, se o item for adicionado novamente ao carrinho, ele aparecerá duas vezes e o Serviço de impostos considerará apenas o preço do item que está primeiro no carrinho, causando divergência de valores de impostos ao fazer um pedido.
+
+## Simulação
+
+
+
+- Configure o Tax Hub em uma conta;
+- Configurar opções de montagem;
+- Adicionar ao carrinho um item que foi incluído na opção de montagem
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md b/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
new file mode 100644
index 000000000..060c9fd16
--- /dev/null
+++ b/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
@@ -0,0 +1,44 @@
+---
+title: 'O Tax Service não aplica promoções de frete grátis com promoções que dividem itens'
+id: 5w7mcNyJhTA77sRULPgrTx
+status: PUBLISHED
+createdAt: 2024-03-06T20:07:56.556Z
+updatedAt: 2024-03-06T20:07:57.240Z
+publishedAt: 2024-03-06T20:07:57.240Z
+firstPublishedAt: 2024-03-06T20:07:57.240Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-tax-service-nao-aplica-promocoes-de-frete-gratis-com-promocoes-que-dividem-itens
+locale: pt
+kiStatus: Backlog
+internalReference: 995527
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o serviço de impostos, se houver uma promoção que divida os itens, por exemplo, uma promoção "Mais por menos" e uma promoção de frete grátis, o frete grátis não é aplicado corretamente para todos os itens na solicitação do serviço de impostos, causando um cálculo errado e evitando que o pedido seja criado com a mensagem "O pedido solicitado não pôde ser criado. Please try again."
+
+## Simulação
+
+
+
+- Configurar o serviço fiscal;
+- Criar uma promoção "Mais por menos";
+- Criar uma promoção de frete grátis;
+- Montar um carrinho e tentar fazer o pedido
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md b/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
new file mode 100644
index 000000000..cd84d7c50
--- /dev/null
+++ b/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
@@ -0,0 +1,43 @@
+---
+title: 'O Tax Service não considera promoções nominais ao fazer pedidos'
+id: 1vCs62opRc2iDw0NmYqlT7
+status: PUBLISHED
+createdAt: 2023-09-14T17:48:37.761Z
+updatedAt: 2023-09-14T17:48:38.630Z
+publishedAt: 2023-09-14T17:48:38.630Z
+firstPublishedAt: 2023-09-14T17:48:38.630Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: o-tax-service-nao-considera-promocoes-nominais-ao-fazer-pedidos
+locale: pt
+kiStatus: Backlog
+internalReference: 900120
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o serviço de impostos, se houver uma promoção nominal aplicada no carrinho e ocorrer uma divisão de item, o checkout da solicitação não terá a promoção nominal aplicada, não permitindo concluir a compra, e a mensagem "O pedido solicitado não pôde ser criado. Please try again" será exibida.
+
+## Simulação
+
+
+
+- Crie uma promoção nominal;
+- Adicione itens ao carrinho e verifique se os itens estão divididos;
+- Tente concluir a compra
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md b/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
new file mode 100644
index 000000000..5fedc29d7
--- /dev/null
+++ b/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
@@ -0,0 +1,42 @@
+---
+title: 'A solicitação de serviço de imposto usa shippingData.address mesmo quando um carrinho tem dois endereços selecionados'
+id: 21t5R3AmcllYam4mXqX6lY
+status: PUBLISHED
+createdAt: 2024-08-01T13:11:10.623Z
+updatedAt: 2024-08-01T13:11:11.796Z
+publishedAt: 2024-08-01T13:11:11.796Z
+firstPublishedAt: 2024-08-01T13:11:11.796Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-solicitacao-de-servico-de-imposto-usa-shippingdataaddress-mesmo-quando-um-carrinho-tem-dois-enderecos-selecionados
+locale: pt
+kiStatus: Backlog
+internalReference: 1074168
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Em um carrinho com itens para retirada e entrega, a simulação do checkout considera apenas as informações do objeto shippingData.address para a solicitação do serviço de imposto. Por exemplo, considerando que esses endereços são de estados diferentes e que o provedor de impostos considera impostos diferentes para cada estado, um dos itens terá o imposto errado aplicado.
+
+## Simulação
+
+
+
+- Configurar o serviço de impostos;
+- Adicione dois itens a um carrinho com diferentes endereços selecionados: um para retirada e outro para entrega
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md b/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md
index 4dfde9fac..560b58101 100644
--- a/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md
+++ b/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md
@@ -3,8 +3,8 @@ title: 'O serviço de impostos usa dados de documentos em vez de e-mail do clien
 id: IOu1ZV40Q5yHjgbcS9C15
 status: PUBLISHED
 createdAt: 2022-03-23T17:50:15.754Z
-updatedAt: 2022-11-25T21:53:38.397Z
-publishedAt: 2022-11-25T21:53:38.397Z
+updatedAt: 2024-02-16T20:28:42.991Z
+publishedAt: 2024-02-16T20:28:42.991Z
 firstPublishedAt: 2022-03-23T17:50:16.302Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: o-servico-de-impostos-usa-dados-de-documentos-em-vez-de-email-do-cliente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 548671
 ---
 
diff --git a/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
new file mode 100644
index 000000000..d0ac08436
--- /dev/null
+++ b/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -0,0 +1,48 @@
+---
+title: 'A pesquisa de televendas não aceita caracteres especiais além de "@".'
+id: 5eTb6KlR07dOP06BGhovoL
+status: PUBLISHED
+createdAt: 2024-07-29T17:21:34.828Z
+updatedAt: 2024-07-29T17:21:35.918Z
+publishedAt: 2024-07-29T17:21:35.918Z
+firstPublishedAt: 2024-07-29T17:21:35.918Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-pesquisa-de-televendas-nao-aceita-caracteres-especiais-alem-de
+locale: pt
+kiStatus: Backlog
+internalReference: 1072418
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Atualmente, ao usar a caixa de pesquisa de televendas, um usuário pode se passar por comprador para ajudar nas compras e, para isso, é necessário inserir, na caixa de pesquisa nativa, o e-mail de quem será representado.
+
+No entanto, ao usar essa ferramenta, os e-mails que contêm caracteres especiais, como "+", "$", "#", etc., não são identificados pela ferramenta de pesquisa. não são identificados pela ferramenta de pesquisa, fazendo com que ela retorne uma resposta "não encontrado".
+
+## Simulação
+
+
+1 - Em uma loja que tenha o televendas (https://help.vtex.com/en/tutorial/telesales-features--UqhiccIRIK2KD0OqkzJaS) implementado, acesse-o por meio de um usuário com a autenticação necessária.
+
+2 - crie um e-mail, nos dados mestre da loja, que use um caractere especial, como "+"
+
+3 - tente usar a barra de ferramentas de personificação do telesales para pesquisar o e-mail fornecido - ela retornará uma resposta "não encontrado".
+
+4 - ajustar esse mesmo e-mail para remover o caractere especial e pesquisar novamente normalizará a situação
+
+## Workaround
+
+
+Adapte os endereços de e-mail dos usuários para que não usem caracteres especiais.
+
+
+
+
diff --git a/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md b/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..88fb295d4
--- /dev/null
+++ b/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
@@ -0,0 +1,50 @@
+---
+title: 'O texto no botão Adicionar ao carrinho não está sendo traduzido usando o editor do site'
+id: 7rA62h80a1LpDWjgd3SImp
+status: PUBLISHED
+createdAt: 2024-05-02T17:33:41.019Z
+updatedAt: 2024-07-03T18:28:56.642Z
+publishedAt: 2024-07-03T18:28:56.642Z
+firstPublishedAt: 2024-05-02T17:33:42.188Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-texto-no-botao-adicionar-ao-carrinho-nao-esta-sendo-traduzido-usando-o-editor-do-site
+locale: pt
+kiStatus: Backlog
+internalReference: 1026103
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar traduzir um texto usando o editor do site para o botão Adicionar ao carrinho, as alterações não são aplicadas na frente da loja.
+
+## Simulação
+
+
+
+1. Abra o editor do site
+2. Selecione o botão Adicionar ao carrinho
+3. Altere o rótulo do texto no botão para o que desejar
+4. Salve as alterações
+5. Visualize a página e o texto será o mesmo, independentemente da localidade selecionada
+
+
+
+## Workaround
+
+
+Certifique-se de que iconLabel esteja vazio tanto no código da loja quanto no editor do site.
+Se não tiver certeza de que está vazio no editor do site, você pode redefinir o conteúdo acessando a versão do editor do site > redefinir.
+
+Em vez disso, siga a documentação aqui e os contextos aqui para definir o rótulo conforme desejado.
+
+
+
+
diff --git a/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md b/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..5d1e56212
--- /dev/null
+++ b/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md
@@ -0,0 +1,52 @@
+---
+title: 'O texto no InfoCard não está sendo traduzido usando o editor do site'
+id: 5HYTZvxkPoTZltMkZcVfVO
+status: PUBLISHED
+createdAt: 2024-06-13T18:47:41.470Z
+updatedAt: 2024-07-03T13:58:33.037Z
+publishedAt: 2024-07-03T13:58:33.037Z
+firstPublishedAt: 2024-06-13T18:47:42.396Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-texto-no-infocard-nao-esta-sendo-traduzido-usando-o-editor-do-site
+locale: pt
+kiStatus: Backlog
+internalReference: 1049491
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar traduzir um texto usando o editor do site para o componente do cartão de informações, as alterações não são aplicadas na frente da loja.
+
+## Simulação
+
+
+
+1. Abra o editor do site
+2. Selecione o componente do cartão de informações
+3. Altere o rótulo do texto
+4. Salvar as alterações
+5. Visualize a página e o texto será o mesmo, independentemente da localidade selecionada
+
+
+
+## Workaround
+
+
+Certifique-se de que o título esteja vazio no código da loja e no editor do site.
+Se não tiver certeza de que está vazio no editor do site, você pode redefinir o conteúdo acessando a versão do editor do site > redefinir.
+
+Siga a documentação aqui e os contextos aqui para definir o rótulo conforme desejado.
+
+Se isso ainda não resolver o problema, você pode usar um componente de rich text e um componente de imagem separadamente dentro do cartão de informações.
+
+
+
+
diff --git a/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md b/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md
new file mode 100644
index 000000000..f1fc39598
--- /dev/null
+++ b/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md
@@ -0,0 +1,53 @@
+---
+title: 'O texto no login da loja não está sendo traduzido usando o editor do site'
+id: 6DptiKTxtOcYIJEgJlZCmo
+status: PUBLISHED
+createdAt: 2023-11-08T13:33:41.296Z
+updatedAt: 2024-07-03T18:29:45.491Z
+publishedAt: 2024-07-03T18:29:45.491Z
+firstPublishedAt: 2023-11-08T13:33:41.967Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-texto-no-login-da-loja-nao-esta-sendo-traduzido-usando-o-editor-do-site
+locale: pt
+kiStatus: Backlog
+internalReference: 911757
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar traduzir um texto usando o editor do site para o login da loja, as alterações não serão aplicadas na frente da loja.
+
+## Simulação
+
+
+
+1. Abra o editor do site
+2. Selecione o bloco Store Login
+3. Altere o rótulo de texto no login para o que desejar
+4. Salve as alterações
+5. Visualize a página e o texto será o mesmo, independentemente da localidade selecionada
+
+
+
+
+## Workaround
+
+
+Certifique-se de que iconLabel esteja vazio tanto no código da loja quanto no editor do site.
+Se não tiver certeza de que está vazio no editor do site, você pode redefinir o conteúdo acessando a versão do editor do site > redefinir.
+ ![](https://vtexhelp.zendesk.com/attachments/token/PXovY6zVHdqqhxjodbtMqdXAa/?name=image.png)
+
+Siga a documentação aqui e os contextos aqui para definir o rótulo conforme desejado.
+
+
+
+
+
diff --git a/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index e4fc9b7c4..44b9ee226 100644
--- a/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -3,8 +3,8 @@ title: 'Link de texto criado com " " no Marketplace após as aprovações - Reoc
 id: 2afynQ9MwaHPMPWyhx80Tp
 status: PUBLISHED
 createdAt: 2023-04-24T19:36:10.185Z
-updatedAt: 2023-05-08T17:47:01.002Z
-publishedAt: 2023-05-08T17:47:01.002Z
+updatedAt: 2023-07-13T15:25:43.450Z
+publishedAt: 2023-07-13T15:25:43.450Z
 firstPublishedAt: 2023-04-24T19:36:10.701Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: link-de-texto-criado-com-no-marketplace-apos-as-aprovacoes-reocorrencia
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 795900
 ---
 
@@ -28,13 +28,10 @@ Em alguns cenários, ao aprovar um produto em um Marketplace, no aplicativo Rece
 O SKU é enviado de volta para aprovação no módulo Received Skus, mas não é possível aprová-lo novamente, pois já haverá um produto com um textlink igual.
 
 
-
 ## Simulação
 
 
-
-
-1) Geralmente ocorre com um erro genérico de skus recebido ao tentar aprovar (isso não acontece em todos os casos).
+1) Geralmente ocorre um erro genérico de skus recebido ao tentar aprovar (isso não acontece em todos os casos).
 
 2) Um produto será criado no catálogo do marketplace com os links de texto defeituosos.
 
@@ -45,5 +42,8 @@ O SKU é enviado de volta para aprovação no módulo Received Skus, mas não é
 ## Workaround
 
 
-Atualização manual/API dos links de texto do produto nesse cenário.
+Atualizar manualmente/API os links de texto do produto nesse cenário.
+
+
+
 
diff --git a/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md b/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
index fcc6d74f9..9f59369d6 100644
--- a/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
+++ b/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
@@ -1,18 +1,18 @@
 ---
-title: 'O campo Judet County não é mostrado como salvo quando a edição de endereço na Romênia minha conta.'
+title: 'O campo Judet county não está aparecendo como salvo ao editar o endereço na minha conta na Romênia.'
 id: 5aOtbUdNXPzOpuvLnmJtMf
 status: PUBLISHED
 createdAt: 2022-02-24T14:52:37.615Z
-updatedAt: 2022-11-25T22:02:22.409Z
-publishedAt: 2022-11-25T22:02:22.409Z
+updatedAt: 2024-02-16T20:25:19.581Z
+publishedAt: 2024-02-16T20:25:19.581Z
 firstPublishedAt: 2022-05-18T18:46:59.023Z
 contentType: knownIssue
 productTeam: Order Management
 author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
-slug: o-campo-judet-county-nao-e-mostrado-como-salvo-quando-a-edicao-de-endereco-na-romenia-minha-conta
+slug: o-campo-judet-county-nao-esta-aparecendo-como-salvo-ao-editar-o-endereco-na-minha-conta-na-romenia
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 394658
 ---
 
@@ -23,22 +23,24 @@ internalReference: 394658
 </div>
 
 
-Para lojas da Romênia na página _**Minha conta**_ há um campo chamado "Judet", município em inglês, que não está sendo exibido como salvo ao editar endereço.
-
-
+Para lojas da Romênia, na página _**My Account**_, há um campo chamado "Judet", município em inglês, que não está sendo exibido como salvo ao editar o endereço.
 
 ## Simulação
 
 
 
-- Verificando o endereço de Minha Conta, você pode ver o endereço salvo anteriormente.
-- Então é possível ver que o comportamento deste campo não é o mesmo que os outros campos.
-- Clique em Edit Address e o endereço anterior ainda se encontra nos campos de endereço, exceto para Judet.
+- Ao verificar o endereço de My Account, você pode ver o endereço salvo anteriormente.
+- Em seguida, é possível ver que o comportamento desse campo não é o mesmo que o dos outros campos.
+- Clique em Edit Address (Editar endereço) e o endereço anterior ainda estará nos campos de endereço, exceto no Judet.
 
 
 
 ## Workaround
 
 
-Não há nenhuma solução disponível para isso na própria Minha Conta, mas talvez usando nossas APIs de Dados Mestres possa atualizar ou criar esses endereços.
+Não há nenhuma solução alternativa disponível para isso no próprio My Account, mas talvez o uso de nossas APIs de dados mestre possa atualizar ou criar esses endereços.
+
+
+
+
 
diff --git a/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md b/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
index 8e0ea5f2f..57c6ee253 100644
--- a/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
+++ b/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
@@ -3,8 +3,8 @@ title: 'O feriado não é mostrado na lista depois de usar o API para criar (PUT
 id: WqzSTP6oFwk4MbGaO5mIU
 status: PUBLISHED
 createdAt: 2022-05-02T22:26:55.630Z
-updatedAt: 2022-11-25T22:00:07.142Z
-publishedAt: 2022-11-25T22:00:07.142Z
+updatedAt: 2024-02-16T20:28:28.551Z
+publishedAt: 2024-02-16T20:28:28.551Z
 firstPublishedAt: 2022-05-02T22:26:56.888Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: o-feriado-nao-e-mostrado-na-lista-depois-de-usar-o-api-para-criar-put
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 571040
 ---
 
diff --git a/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md b/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
index 43adb99cc..b1df82bd4 100644
--- a/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
+++ b/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
@@ -3,8 +3,8 @@ title: 'A solicitação de parcelas na porta de entrada de um comerciante que n
 id: Xo2YO6ZM9Jj0ONZjXrrrJ
 status: PUBLISHED
 createdAt: 2022-03-27T21:08:39.176Z
-updatedAt: 2022-11-25T22:05:55.885Z
-publishedAt: 2022-11-25T22:05:55.885Z
+updatedAt: 2024-02-16T20:29:17.920Z
+publishedAt: 2024-02-16T20:29:17.920Z
 firstPublishedAt: 2022-03-27T21:08:39.738Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: a-solicitacao-de-parcelas-na-porta-de-entrada-de-um-comerciante-que-nao-o-mercado-e-sempre-feita-com-canal-de-vendas-1
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 391197
 ---
 
diff --git a/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md b/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
new file mode 100644
index 000000000..dda20dae0
--- /dev/null
+++ b/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
@@ -0,0 +1,43 @@
+---
+title: 'O conector legado da Adyen não consegue negar assincronamente a captura de pagamentos'
+id: 5tdNyMfA5zeNg4sCbPQgUc
+status: PUBLISHED
+createdAt: 2024-02-02T15:15:57.980Z
+updatedAt: 2024-02-02T15:15:58.839Z
+publishedAt: 2024-02-02T15:15:58.839Z
+firstPublishedAt: 2024-02-02T15:15:58.839Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-conector-legado-da-adyen-nao-consegue-negar-assincronamente-a-captura-de-pagamentos
+locale: pt
+kiStatus: Backlog
+internalReference: 976005
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O conector antigo da Adyen captura o pagamento sempre que recebe o campo `"response":"[capture-received]"`. No entanto, esse evento indica apenas que a captura foi recebida e será processada de forma assíncrona. Esse comportamento evita que as capturas sejam negadas, pois a notificação assíncrona encontra um pagamento já capturado e não o reembolsa.
+
+## Simulação
+
+
+Depende da resposta de captura da Adyen; portanto, um pagamento precisa ser capturado para receber uma notificação de falha de captura.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
new file mode 100644
index 000000000..e95947f3a
--- /dev/null
+++ b/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
@@ -0,0 +1,51 @@
+---
+title: 'A integração do MercadoPagoV1 e V2 não funciona com a funcionalidade de salvar cartão'
+id: 2V8kdA60OTl7VQoUUNgBci
+status: PUBLISHED
+createdAt: 2022-05-03T15:45:09.856Z
+updatedAt: 2024-01-09T13:23:20.203Z
+publishedAt: 2024-01-09T13:23:20.203Z
+firstPublishedAt: 2022-05-03T15:45:10.554Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: a-integracao-do-mercadopagov1-e-v2-nao-funciona-com-a-funcionalidade-de-salvar-cartao
+locale: pt
+kiStatus: Backlog
+internalReference: 283727
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A integração do MercadoPagoV1 e do MercadoPagoV2 não funciona corretamente com a funcionalidade de salvar cartão na seção "Minha conta" para países que não permitem transações com decimais.
+
+Esse problema ocorre porque o recurso "Meus cartões" gera uma nova transação com um valor de US$ 1,5. No entanto, alguns países não permitem transações com esses valores decimais, o que resulta na rejeição de qualquer tentativa de aprovação dessas transações.
+
+## Simulação
+
+
+
+1. Acesse o VTEX **Admin.**
+2. Configure o adquirente MercadoPagoV1 ou MercadoPagoV2.
+3. Configure um método de pagamento com cartão de crédito - como Mastercard, Visa, American Express, etc. - a ser processado pelo adquirente.
+4. Vá para a página inicial de sua loja.
+5. Faça login inserindo seu endereço de e-mail e senha.
+6. Clique em **My account**.
+7. Vá para a seção **Cartões de crédito**.
+8. Clique em **Add new card**.
+9. Preencha todos os campos e clique em **Salvar novo cartão**.
+10. Esse processo retornará _ocorreu um erro ao tentar registrar o cartão_
+
+
+
+## Workaround
+
+
+N/A
+
diff --git a/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md b/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
new file mode 100644
index 000000000..c8c3db30c
--- /dev/null
+++ b/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
@@ -0,0 +1,48 @@
+---
+title: 'O conector PayU não consegue processar pagamentos quando há dados de envio com mais de 40 caracteres.'
+id: 1SEaraqWshBYzjOcL9LxsN
+status: PUBLISHED
+createdAt: 2023-09-18T21:02:32.217Z
+updatedAt: 2023-09-18T21:02:32.812Z
+publishedAt: 2023-09-18T21:02:32.812Z
+firstPublishedAt: 2023-09-18T21:02:32.812Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: o-conector-payu-nao-consegue-processar-pagamentos-quando-ha-dados-de-envio-com-mais-de-40-caracteres
+locale: pt
+kiStatus: Backlog
+internalReference: 902539
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O conector da PayU não trata os dados de endereço recebidos do checkout e os envia ao provedor como estão, sem nenhuma modificação. No entanto, a documentação do provedor afirma que esses dados não devem exceder 40 caracteres.
+
+Isso faz com que a transação seja cancelada devido a um erro de autorização de pagamento com a mensagem:
+
+    message: El tamaño debe estar entre 0 y 40 property: , message: El tamaño debe estar entre 0 y 40
+
+
+## Simulação
+
+
+
+- Durante a etapa de envio no checkout, selecione um endereço de entrega com mais de 40 caracteres, como "Región Del Libertador General Bernardo O'Higgins (VI)" no Chile.
+- Selecione um método de pagamento processado por meio do conector PayU
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md b/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
index e47bbd8b6..808ce9a62 100644
--- a/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
+++ b/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
@@ -3,8 +3,8 @@ title: 'O botão de compra permanece ativo mesmo com crédito insuficiente do M
 id: 76oPdoBKDn3PSn2KhomgQc
 status: PUBLISHED
 createdAt: 2022-03-27T14:14:51.967Z
-updatedAt: 2022-11-25T22:06:26.792Z
-publishedAt: 2022-11-25T22:06:26.792Z
+updatedAt: 2024-02-16T20:29:57.111Z
+publishedAt: 2024-02-16T20:29:57.111Z
 firstPublishedAt: 2022-03-27T14:14:52.312Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: o-botao-de-compra-permanece-ativo-mesmo-com-credito-insuficiente-do-metodo-de-pagamento-credito-ao-cliente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 309820
 ---
 
diff --git a/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index 603ea68cc..b699fea8e 100644
--- a/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -1,18 +1,18 @@
 ---
-title: 'A opção "Salvar novo cartão" não funciona para provedores assíncronos de pagamento'
+title: 'A opção "Salvar novo cartão" não funciona para provedores de pagamento assíncronos'
 id: 3B4gVSNrSeCc8EBXwk5sAu
 status: PUBLISHED
 createdAt: 2022-03-11T17:54:35.664Z
-updatedAt: 2022-11-25T22:06:23.711Z
-publishedAt: 2022-11-25T22:06:23.711Z
+updatedAt: 2024-04-29T17:58:58.889Z
+publishedAt: 2024-04-29T17:58:58.889Z
 firstPublishedAt: 2022-03-11T17:54:36.273Z
 contentType: knownIssue
 productTeam: Payments
 author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
-slug: a-opcao-salvar-novo-cartao-nao-funciona-para-provedores-assincronos-de-pagamento
+slug: a-opcao-salvar-novo-cartao-nao-funciona-para-provedores-de-pagamento-assincronos
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 308892
 ---
 
@@ -23,28 +23,24 @@ internalReference: 308892
 </div>
 
 
-Quando o cliente tenta adicionar um novo cartão na seção Minha conta das lojas cujas afiliações não retornam uma resposta síncrona, o sistema retornará _um erro ocorrido ao tentar registrar o cartão_ e uma cobrança indevida de R$1,50 poderá ser gerada.
-
-Este erro ocorre porque Meus Cartões esperam por uma resposta síncrona dos compradores de cartões de crédito e a maioria deles não retorna uma resposta imediata.
-
+Quando o cliente tenta adicionar um novo cartão na seção Minha conta de lojas cujas afiliações não retornam uma resposta síncrona, o sistema retorna _ocorreu um erro ao tentar registrar o cartão_ e uma cobrança indevida de R$ 1,50 pode ser gerada.
 
+Esse erro ocorre porque a My Cards aguarda uma resposta síncrona das adquirentes de cartão de crédito e a maioria delas não retorna uma resposta imediata.
 
 ## Simulação
 
 
 
-1. Ir para a VTEX **Admin.**
+1. Acesse o VTEX **Admin.**
 2. Configure o adquirente Mundi.
-3. Configurar um método de pagamento com cartão de crédito - como Mastercard, Visa, American Express, etc. - para ser processado pelo adquirente.
-4. Ir para a home page de sua loja.
-5. Faça o login digitando seu endereço de e-mail e senha.
-6. Clique em **Minha conta***.
-7. Vá para a seção **Cartões de crédito***.
-8. Clique em **Adicionar novo cartão**.
-9. Preencha todos os campos e clique em **Salvar novo cartão***.
-10. Este processo devolverá um erro e o cliente será cobrado o valor de R$ 1,50, que pode ou não ser devolvido automaticamente mais tarde.
-
-
+3. Configure um método de pagamento com cartão de crédito - como Mastercard, Visa, American Express, etc. - a ser processado pelo adquirente.
+4. Vá para a página inicial de sua loja.
+5. Faça login inserindo seu endereço de e-mail e senha.
+6. Clique em **My account**.
+7. Vá para a seção **Cartões de crédito**.
+8. Clique em **Add new card**.
+9. Preencha todos os campos e clique em **Salvar novo cartão**.
+10. Esse processo retornará um erro e será cobrado do cliente o valor de R$ 1,50, que poderá ou não ser devolvido automaticamente mais tarde
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md b/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
new file mode 100644
index 000000000..0a8e5e864
--- /dev/null
+++ b/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
@@ -0,0 +1,44 @@
+---
+title: 'A API Scroll retorna erros 429 e/ou 408 ao consultar entidades com um grande número de documentos, geralmente superior a milhões'
+id: 1Yx7s4kDAJOzpNCxro7TmW
+status: PUBLISHED
+createdAt: 2024-05-20T15:01:15.646Z
+updatedAt: 2024-05-20T15:01:16.679Z
+publishedAt: 2024-05-20T15:01:16.679Z
+firstPublishedAt: 2024-05-20T15:01:16.679Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: a-api-scroll-retorna-erros-429-eou-408-ao-consultar-entidades-com-um-grande-numero-de-documentos-geralmente-superior-a-milhoes
+locale: pt
+kiStatus: Backlog
+internalReference: 1035873
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A API Scroll foi projetada para lidar com grandes conjuntos de dados, permitindo a recuperação de documentos de forma rolável. No entanto, ao consultar entidades com um número significativo de documentos, normalmente na casa dos milhões, os usuários podem encontrar erros 429 (Too Many Requests) e/ou 408 (Request Timeout). Esses erros ocorrem devido ao alto volume de dados que estão sendo processados, o que pode sobrecarregar a API e resultar em limitação da taxa de solicitações ou timeouts.
+
+## Simulação
+
+
+
+1. Use a API Scroll para consultar uma entidade que contém um grande número de documentos (por exemplo, milhões).
+2. Observe as respostas da API.
+3. Observe se a API retorna erros 429 (Too Many Requests) e/ou 408 (Request Timeout) durante o processo
+
+## Workaround
+
+
+Otimize a consulta implementando filtros para reduzir a carga na API, dividindo a solicitação em pedaços ou lotes menores.
+Ao escolher os filtros, é importante prestar atenção se todos os documentos serão incluídos para garantir que a rolagem percorrerá todos os documentos da entidade.
+
+
+
+
diff --git a/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md b/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
index 1e8fea1ee..4635b3d5a 100644
--- a/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
+++ b/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
@@ -3,8 +3,8 @@ title: 'O sistema não permite o cancelamento múltiplo com Giftcard'
 id: 2htvtVV2158piX4lTYhAvE
 status: PUBLISHED
 createdAt: 2022-03-27T12:54:40.811Z
-updatedAt: 2022-11-25T22:05:17.362Z
-publishedAt: 2022-11-25T22:05:17.362Z
+updatedAt: 2024-06-25T13:51:28.086Z
+publishedAt: 2024-06-25T13:51:28.086Z
 firstPublishedAt: 2022-03-27T12:54:41.420Z
 contentType: knownIssue
 productTeam: Payments
@@ -23,21 +23,22 @@ internalReference: 309117
 </div>
 
 
-O sistema não está enviando o cancelamento parcial de uma transação Giftcard.
+O sistema não está enviando o cancelamento parcial de uma transação de Giftcard.
+Também encontramos um cenário em que a mesma coisa acontece, mas o cancelamento funciona. Isso deixa o valor do reembolso maior do que o valor da transação porque o valor reembolsado é o primeiro reembolso parcial + o segundo reembolso com o valor total.
 
-Também encontramos um cenário onde a mesma coisa acontece, porém o cancelamento funciona. Isto deixa o valor do reembolso maior que o valor da transação porque o valor reembolsado é o primeiro reembolso parcial + o segundo reembolso com o valor total.
+## Simulação
 
 
+Encontre uma transação em que um reembolso/cancelamento parcial foi solicitado usando o Giftcard.
 
-## Simulação
 
 
-Encontre uma transação onde um reembolso/cancelamento parcial foi solicitado utilizando o Giftcard.
+## Workaround
 
 
+Não há solução alternativa, no entanto, o usuário pode adicionar o crédito reembolsável por meio da UI do administrador.
+
 
-## Workaround
 
 
-Não há solução, entretanto, o usuário pode adicionar o crédito reembolsável através da interface administrativa.
 
diff --git a/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md b/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
index 61ee895a0..52723e642 100644
--- a/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
+++ b/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
@@ -3,8 +3,8 @@ title: 'O sistema não funciona com mais de uma filiação de pagamento de exten
 id: 3bXtVPHqsrSFpJk9ZfyP4v
 status: PUBLISHED
 createdAt: 2022-03-03T18:45:02.639Z
-updatedAt: 2022-11-25T22:05:27.547Z
-publishedAt: 2022-11-25T22:05:27.547Z
+updatedAt: 2024-02-16T20:25:40.644Z
+publishedAt: 2024-02-16T20:25:40.644Z
 firstPublishedAt: 2022-03-03T18:45:03.463Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: o-sistema-nao-funciona-com-mais-de-uma-filiacao-de-pagamento-de-extensao-para-debito-online
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 319750
 ---
 
diff --git a/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index fd6c828e6..cc86d5dd7 100644
--- a/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -3,8 +3,8 @@ title: 'O modelo "relatorio-de-importacao-de-estoque" não suporta multi-linguag
 id: 5R8b0jnibOQdXupo0hIyts
 status: PUBLISHED
 createdAt: 2022-05-25T18:25:43.394Z
-updatedAt: 2022-11-25T21:59:26.792Z
-publishedAt: 2022-11-25T21:59:26.792Z
+updatedAt: 2024-02-16T20:24:28.851Z
+publishedAt: 2024-02-16T20:24:28.851Z
 firstPublishedAt: 2022-05-25T18:25:43.976Z
 contentType: knownIssue
 productTeam: Logistics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Logistics
 slug: o-modelo-relatoriodeimportacaodeestoque-nao-suporta-multilinguagem
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 585906
 ---
 
diff --git a/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md b/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
index 8d1d71abf..83cbffc73 100644
--- a/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
+++ b/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
@@ -3,8 +3,8 @@ title: 'O usuário não pode fazer uma assinatura diária diretamente da área m
 id: QJrZvOmlRusACgS2iGRyT
 status: PUBLISHED
 createdAt: 2022-05-18T18:37:18.099Z
-updatedAt: 2022-11-25T22:02:05.580Z
-publishedAt: 2022-11-25T22:02:05.580Z
+updatedAt: 2024-02-16T20:27:15.017Z
+publishedAt: 2024-02-16T20:27:15.017Z
 firstPublishedAt: 2022-05-18T18:37:18.579Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: o-usuario-nao-pode-fazer-uma-assinatura-diaria-diretamente-da-area-mysubscriptions
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 430650
 ---
 
diff --git a/docs/known-issues/pt/time-out-import-and-export-admin.md b/docs/known-issues/pt/time-out-import-and-export-admin.md
index dce46202e..fd3e93477 100644
--- a/docs/known-issues/pt/time-out-import-and-export-admin.md
+++ b/docs/known-issues/pt/time-out-import-and-export-admin.md
@@ -1,10 +1,10 @@
 ---
-title: 'Time Out - Administração de Importação e Exportação'
+title: 'Time Out - Administração de importação e exportação'
 id: 5sPtDgOXtiGcYMvZL7aCf8
 status: PUBLISHED
 createdAt: 2022-03-10T12:36:57.023Z
-updatedAt: 2022-11-25T21:46:35.375Z
-publishedAt: 2022-11-25T21:46:35.375Z
+updatedAt: 2024-01-19T15:24:38.444Z
+publishedAt: 2024-01-19T15:24:38.444Z
 firstPublishedAt: 2022-03-10T12:36:57.461Z
 contentType: knownIssue
 productTeam: Catalog
@@ -23,15 +23,13 @@ internalReference: 424902
 </div>
 
 
-Para algumas contas com muitos produtos, a administração de importação e exportação não carrega, gerando um time out
-
-
+Para algumas contas com muitos produtos, o administrador de importação e exportação não é carregado, gerando um tempo limite
 
 
 ## Simulação
 
 
-Ir para `/admin/Site/Relatorio_Skus.aspx `
+Vá para `/admin/Site/Relatorio_Skus.aspx `
 
 
 
diff --git a/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md b/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md
index 388f0f2f8..4b8da212d 100644
--- a/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md
+++ b/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md
@@ -3,8 +3,8 @@ title: 'Timeout ao mudar as palavras-chave da categoria com muitos produtos'
 id: 14rC5XqGCOj1THVdYwbudS
 status: PUBLISHED
 createdAt: 2022-02-25T11:40:37.024Z
-updatedAt: 2022-11-25T21:55:02.673Z
-publishedAt: 2022-11-25T21:55:02.673Z
+updatedAt: 2024-02-16T20:26:33.631Z
+publishedAt: 2024-02-16T20:26:33.631Z
 firstPublishedAt: 2022-02-25T11:40:37.550Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: timeout-ao-mudar-as-palavraschave-da-categoria-com-muitos-produtos
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 497335
 ---
 
diff --git a/docs/known-issues/pt/timeout-generating-internal-application-keys.md b/docs/known-issues/pt/timeout-generating-internal-application-keys.md
new file mode 100644
index 000000000..03d4a183f
--- /dev/null
+++ b/docs/known-issues/pt/timeout-generating-internal-application-keys.md
@@ -0,0 +1,44 @@
+---
+title: 'Tempo limite Geração de chaves internas do aplicativo'
+id: 11U62yvD8i6Mp79rUC38FU
+status: PUBLISHED
+createdAt: 2024-05-08T11:28:41.002Z
+updatedAt: 2024-05-09T12:04:05.533Z
+publishedAt: 2024-05-09T12:04:05.533Z
+firstPublishedAt: 2024-05-08T11:28:41.857Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: tempo-limite-geracao-de-chaves-internas-do-aplicativo
+locale: pt
+kiStatus: Fixed
+internalReference: 1029425
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Atualmente, temos um problema que pode afetar alguns clientes durante a geração de chaves de aplicativos.
+
+## Simulação
+
+
+
+Quando o cliente usa seu próprio SMTP para o modelo do gerenciador de licenças no centro de mensagens, a interface do usuário da chave do aplicativo tentará usar seu SMTP para enviar o e-mail, mas se houver um tempo limite durante o envio do e-mail, a chave do aplicativo também não será gerada
+
+## Workaround
+
+
+
+O cliente pode alterar o SMTP do gerenciador de licenças no centro de mensagens para configurar o SMTP da VTEX em vez de seu próprio SMTP, evitando o tempo limite. Ou ele pode apenas tentar resolver o problema com o tempo limite do SMTP.
+
+
+
+
+
diff --git a/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md b/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
new file mode 100644
index 000000000..972c3bec8
--- /dev/null
+++ b/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
@@ -0,0 +1,44 @@
+---
+title: 'Tempo limite na consulta para que o Analytics impeça a verificação do registro de inventário'
+id: 2gQhc3JF0bcm1JeLr0lluO
+status: PUBLISHED
+createdAt: 2024-02-19T20:54:22.012Z
+updatedAt: 2024-07-03T15:26:48.484Z
+publishedAt: 2024-07-03T15:26:48.484Z
+firstPublishedAt: 2024-02-19T20:54:22.861Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: tempo-limite-na-consulta-para-que-o-analytics-impeca-a-verificacao-do-registro-de-inventario
+locale: pt
+kiStatus: Fixed
+internalReference: 984482
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O registro de atualização na interface do usuário do inventário às vezes retorna o erro: A solicitação falhou com o código de status 500 para algumas SKUs específicas, devido a um tempo limite na consulta ao Analytics (onde os dados são armazenados), e nenhum registro para a SKU será mostrado na interface do usuário.
+
+Esse tempo limite pode ser devido a um alto volume de atualizações na SKU ou a qualquer outro fator que faça com que essa consulta demore mais do que o tempo máximo de 40s;
+
+## Simulação
+
+
+Devido ao fato de a variável ser o tempo de resposta da consulta ao Analytics, não é possível replicar de forma concisa.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa disponível.
+
+
+
+
diff --git a/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md b/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md
new file mode 100644
index 000000000..837791954
--- /dev/null
+++ b/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md
@@ -0,0 +1,48 @@
+---
+title: 'Total de itens de reserva com valor negativo na interface do usuário do inventário'
+id: 5W8BeBZjSgN30YXwXfT8kV
+status: PUBLISHED
+createdAt: 2024-02-29T22:05:19.854Z
+updatedAt: 2024-03-01T13:46:07.440Z
+publishedAt: 2024-03-01T13:46:07.440Z
+firstPublishedAt: 2024-02-29T22:05:20.674Z
+contentType: knownIssue
+productTeam: Logistics
+author: 2mXZkbi0oi061KicTExNjo
+tag: Logistics
+slug: total-de-itens-de-reserva-com-valor-negativo-na-interface-do-usuario-do-inventario
+locale: pt
+kiStatus: Backlog
+internalReference: 991735
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Um cenário específico, no qual mais de um pedido é feito com o mesmo sku e proveniente do mesmo depósito, pode deixar o número da reserva negativo na interface do usuário do inventário.
+
+**Cenário específico:**
+Pedido A: 4 unidades do sku X do depósito 1;
+pedido B: 6 unidades da sku X do depósito 1;
+
+Pedido A: `status=handling`, a reserva é confirmada;
+pedido B: `status=window-to-cancel`, a reserva ainda não foi confirmada;
+
+Depois disso, o comerciante atualiza o estoque considerando as unidades do pedido A como entregues. Se o comerciante cancelar o pedido A e, posteriormente, mover o pedido B para `status=handling` (reconhecer a reserva), isso deixará a interface do usuário do estoque com -4 dessa sku como reservada.
+
+
+#
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
new file mode 100644
index 000000000..f1d9a27a4
--- /dev/null
+++ b/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
@@ -0,0 +1,44 @@
+---
+title: 'Erro de cancelamento de transação com a mensagem "Unreachable code" (código inacessível)'
+id: 2Y4joZlyDhbNWU9ycw32U3
+status: PUBLISHED
+createdAt: 2024-03-12T16:34:10.113Z
+updatedAt: 2024-03-12T16:34:11.037Z
+publishedAt: 2024-03-12T16:34:11.037Z
+firstPublishedAt: 2024-03-12T16:34:11.037Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: erro-de-cancelamento-de-transacao-com-a-mensagem-unreachable-code-codigo-inacessivel
+locale: pt
+kiStatus: Backlog
+internalReference: 998435
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O cancelamento de uma transação completa pode falhar ao retornar a mensagem `Código inacessível` (visível apenas por meio da API).
+
+Esse erro ocorre no cenário de divisão de pagamento; na interface do usuário, é possível ver os registros de tentativa de cancelamento, mas nenhuma resposta.
+
+## Simulação
+
+
+Não foi possível simular esse erro.
+
+
+
+## Workaround
+
+
+É possível cancelar os pagamentos separadamente (começando pelo valor mais baixo).
+
+
+
+
diff --git a/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md b/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
new file mode 100644
index 000000000..3cb202874
--- /dev/null
+++ b/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
@@ -0,0 +1,35 @@
+---
+title: 'Transação presa em um status anterior ao estado em que deveria estar'
+id: 60oG2yj6wb1MomGh7Bbh9C
+status: PUBLISHED
+createdAt: 2024-05-22T17:58:05.800Z
+updatedAt: 2024-07-25T21:12:34.583Z
+publishedAt: 2024-07-25T21:12:34.583Z
+firstPublishedAt: 2024-05-22T17:58:06.594Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transacao-presa-em-um-status-anterior-ao-estado-em-que-deveria-estar
+locale: pt
+kiStatus: Backlog
+internalReference: 1037765
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O caso mais comum é o de uma transação presa em autorizada quando deveria ser aprovada; nesse cenário, o pedido não pode ser faturado.
+
+## Simulação
+
+
+
+## Workaround
+
+
+
diff --git a/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md b/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
index a880c73eb..6dffe719a 100644
--- a/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
+++ b/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
@@ -1,10 +1,10 @@
 ---
 title: 'Transaction stuck in canceling when one of the card is denied'
 id: RdKtB6LsKfaukjT9kiqZ4
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-03-03T18:39:59.580Z
-updatedAt: 2022-06-29T11:57:29.612Z
-publishedAt: 2022-06-28T17:06:24.520Z
+updatedAt: 2024-02-16T20:29:06.755Z
+publishedAt: 2024-02-16T20:29:06.755Z
 firstPublishedAt: 2022-03-03T18:39:59.922Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: transaction-stuck-in-canceling-when-one-of-the-card-is-denied
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 429082
 ---
 
diff --git a/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md b/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md
new file mode 100644
index 000000000..a18231a34
--- /dev/null
+++ b/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md
@@ -0,0 +1,48 @@
+---
+title: 'Transação presa no status aprovado com pagamento cancelado'
+id: 5SwwnGi26tagIXuTmvToc
+status: PUBLISHED
+createdAt: 2024-06-07T14:21:22.809Z
+updatedAt: 2024-06-12T17:33:43.967Z
+publishedAt: 2024-06-12T17:33:43.967Z
+firstPublishedAt: 2024-06-07T14:21:23.608Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: transacao-presa-no-status-aprovado-com-pagamento-cancelado
+locale: pt
+kiStatus: Backlog
+internalReference: 1046365
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A transação ficou presa no status aprovado, mesmo que o pagamento tenha sido cancelado.
+
+Quando tentamos liquidá-la manualmente, o gateway retorna o seguinte erro:
+
+    "error": {"code": "1506", "message": "O pagamento com ID = xxxxx não foi liquidado porque o valor de liquidação foi -x.xx.", "exception": null}
+
+
+## Simulação
+
+
+Não há como simular esse comportamento.
+
+
+
+## Workaround
+
+
+Não há nenhuma solução alternativa nesse caso.
+
+
+
+
+
diff --git a/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md b/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md
index efe9030f4..e6d7d42cb 100644
--- a/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md
+++ b/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md
@@ -19,10 +19,10 @@ internalReference:
 ## Sumário
 
 Quando um item é removido do pedido:
-![item removido](https://images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
+![item removido](//images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
 
 O email transacional não considera o item removido e apresenta os dois itens no e-mail:
-![email transacional](https://images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
+![email transacional](//images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
 
 
 
diff --git a/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
new file mode 100644
index 000000000..e87107095
--- /dev/null
+++ b/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -0,0 +1,43 @@
+---
+title: 'As transações com a Konduto estão demorando mais do que o esperado para atualizar o status'
+id: 5yUSXenLjlEdESoj5VVvoH
+status: PUBLISHED
+createdAt: 2022-03-11T18:56:45.293Z
+updatedAt: 2023-07-10T18:01:59.163Z
+publishedAt: 2023-07-10T18:01:59.163Z
+firstPublishedAt: 2022-03-11T18:56:45.712Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: as-transacoes-com-a-konduto-estao-demorando-mais-do-que-o-esperado-para-atualizar-o-status
+locale: pt
+kiStatus: Backlog
+internalReference: 541149
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As novas tentativas automáticas estão ficando presas em algumas transações que usam o Kondutor como provedor antifraude e demoram mais do que o esperado para chamar uma nova tentativa a fim de alterar seu status. Isso está bloqueando o inventário dos clientes.
+
+## Simulação
+
+
+Não é possível simular, esse comportamento ocorre de forma intermitente.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md b/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
index 7948528e5..76cb0a56d 100644
--- a/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
+++ b/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
@@ -3,8 +3,8 @@ title: 'Transações com o conector TNSPay sendo negadas por erro: Cartão não
 id: 2jZefzH8LYqPJxkmylmyA0
 status: PUBLISHED
 createdAt: 2022-03-14T13:21:56.187Z
-updatedAt: 2023-04-10T16:10:48.998Z
-publishedAt: 2023-04-10T16:10:48.998Z
+updatedAt: 2024-02-16T20:24:33.195Z
+publishedAt: 2024-02-16T20:24:33.195Z
 firstPublishedAt: 2022-03-14T13:21:56.952Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: transacoes-com-o-conector-tnspay-sendo-negadas-por-erro-cartao-nao-proibido-em-3ds
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 541687
 ---
 
diff --git a/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md b/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
new file mode 100644
index 000000000..50b5f6997
--- /dev/null
+++ b/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
@@ -0,0 +1,45 @@
+---
+title: 'Problemas de tradução ao usar uma subconta para implementar lojas em vários idiomas'
+id: 5FOCZE7pI4npyfo7TjsFaY
+status: PUBLISHED
+createdAt: 2023-06-21T20:36:33.483Z
+updatedAt: 2024-02-29T15:19:42.862Z
+publishedAt: 2024-02-29T15:19:42.862Z
+firstPublishedAt: 2023-06-21T20:36:33.922Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: problemas-de-traducao-ao-usar-uma-subconta-para-implementar-lojas-em-varios-idiomas
+locale: pt
+kiStatus: Backlog
+internalReference: 848524
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A indexação unificada do catálogo considera as traduções das mensagens apenas da conta principal, mesmo quando se usa uma arquitetura de subconta para implementar armazenamentos internacionais.
+
+Isso leva a uma tradução diferente na página de pesquisa e na página do produto, pois o conteúdo da página de pesquisa baseia-se apenas nas traduções recuperadas pelo Catalog Indexer.
+
+## Simulação
+
+
+
+- Crie uma subconta e implemente lojas internacionais;
+- Traduza o conteúdo do catálogo na subconta;
+- Compare a página de pesquisa e a página do produto; elas terão traduções diferentes
+
+## Workaround
+
+
+Defina os idiomas adicionais (vinculações e conteúdo de Mensagens) na conta principal, replicando as traduções da subconta também na conta principal.
+
+
+
+
diff --git a/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md b/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
new file mode 100644
index 000000000..c07b0b6c5
--- /dev/null
+++ b/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
@@ -0,0 +1,68 @@
+---
+title: 'A transliteração só está sendo salva no vbase e não no rewriter'
+id: 3ngFt1qXOUjmY5L84dk6in
+status: PUBLISHED
+createdAt: 2023-12-12T19:54:12.171Z
+updatedAt: 2024-02-16T20:26:46.444Z
+publishedAt: 2024-02-16T20:26:46.444Z
+firstPublishedAt: 2023-12-12T19:54:13.102Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: a-transliteracao-so-esta-sendo-salva-no-vbase-e-nao-no-rewriter
+locale: pt
+kiStatus: No Fix
+internalReference: 738334
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao transliterar as urls por meio do catálogo, o rewriter não as armazena ou não recebe nenhuma notificação por meio do broadcaster, estamos armazenando-as apenas no vbase
+
+## Simulação
+
+
+
+Tradução
+
+Verifique o rewriter com o linkId que você criou em admin/graphql-ide e escolha o aplicativo rewriter:
+
+
+    { internal{ get(path: "yourLinkdIdHere"){ id } }}
+
+
+## Workaround
+
+
+
+Execute a seguinte consulta no reescritor
+
+
+    { internal{ get(path: "yourTranslatedCategoryNameSlugified"){ id from declarer type query binding origin resolveAs } }}
+
+
+Salve os valores retornados, pois você precisará usá-los na próxima etapa
+
+Execute a seguinte mutação, alterando apenas o parâmetro from; os outros devem ser iguais aos anteriores:
+
+
+    mutation saveInternal($route: InternalInput!) { internal { save(route: $route) { from declarer type id binding resolveAs origin } }}{ "route": { "from": "yourLinkId", "declarer": "yourSavedDeclarer", "type": "yourSavedType", "binding": "yourSavedBinding", "id": "yourSavedId", "origin": "yourSavedOrigin", "resolveAs": "TheOriginalNameOfTheCategory" -- aqui em cirílico }}
+
+
+
+> Para obter mais informações sobre esses parâmetros, você pode consultar: https://developers.vtex.com/vtex-developer-docs/docs/rewriter
+
+
+Agora, vamos excluir a rota antiga (a que foi salva com o nome)
+
+
+    mutation saveInternal($route: InternalInput!) { internal { delete(path: "yourTranslatedCategoryNameSlugified") { id } }}
+
+
diff --git a/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md b/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md
index 87ebb0609..80572e771 100644
--- a/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md
+++ b/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md
@@ -3,8 +3,8 @@ title: 'A UI não atualiza a melhor escolha de SLA no carrinho'
 id: 5H05jLUJA0gmSDTO6nMsPE
 status: PUBLISHED
 createdAt: 2022-03-26T02:30:36.692Z
-updatedAt: 2022-11-25T21:54:03.143Z
-publishedAt: 2022-11-25T21:54:03.143Z
+updatedAt: 2024-02-16T20:26:13.531Z
+publishedAt: 2024-02-16T20:26:13.531Z
 firstPublishedAt: 2022-03-26T02:30:37.014Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: a-ui-nao-atualiza-a-melhor-escolha-de-sla-no-carrinho
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 550201
 ---
 
diff --git a/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md b/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
new file mode 100644
index 000000000..28a4a62a6
--- /dev/null
+++ b/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
@@ -0,0 +1,46 @@
+---
+title: 'A interface do usuário não mostra a seleção da janela de entrega para pontos de retirada quando um item de um vendedor está entre itens para retirada de outro vendedor'
+id: 5SyIw04UtNiZhmy0ELNLCD
+status: PUBLISHED
+createdAt: 2023-12-15T20:18:48.433Z
+updatedAt: 2023-12-15T20:18:49.218Z
+publishedAt: 2023-12-15T20:18:49.218Z
+firstPublishedAt: 2023-12-15T20:18:49.218Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-nao-mostra-a-selecao-da-janela-de-entrega-para-pontos-de-retirada-quando-um-item-de-um-vendedor-esta-entre-itens-para-retirada-de-outro-vendedor
+locale: pt
+kiStatus: Backlog
+internalReference: 954108
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Em um carrinho com pelo menos três produtos, onde os pedidos de itens são: O primeiro é para a retirada programada 1, o segundo é para a retirada programada 2 (vendedor diferente) e o terceiro é para a retirada programada 1, a interface do usuário não mostrará as janelas de entrega para selecionar a data/hora da segunda retirada. Isso acontece porque a API agrupará o 1º item e o 3º item, já que se trata do mesmo SLA.
+
+Não é possível ir para a etapa de pagamento e concluir a compra.
+
+## Simulação
+
+
+
+- Adicione um item ao carrinho para retirada no vendedor A;
+- Adicione um item ao carrinho para retirada no vendedor B;
+- Adicionar outro item ao carrinho para retirada do vendedor A;
+- Na etapa de envio, as janelas de entrega de retirada para selecionar a data/hora não serão exibidas
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md b/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
index 3b8bc984f..5c940ccb1 100644
--- a/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
+++ b/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
@@ -1,18 +1,18 @@
 ---
-title: 'UI não mostra o formulário para editar endereço ao selecionar para adicionar um novo endereço primeiro'
+title: 'A interface do usuário não mostra o formulário para editar o endereço ao selecionar primeiro a adição de um novo endereço'
 id: 4rqphb66vAzsAyx9mUmNLu
 status: PUBLISHED
 createdAt: 2023-02-06T13:15:57.816Z
-updatedAt: 2023-02-06T13:15:58.251Z
-publishedAt: 2023-02-06T13:15:58.251Z
+updatedAt: 2023-06-23T17:47:10.184Z
+publishedAt: 2023-06-23T17:47:10.184Z
 firstPublishedAt: 2023-02-06T13:15:58.251Z
 contentType: knownIssue
 productTeam: Checkout
 author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
-slug: ui-nao-mostra-o-formulario-para-editar-endereco-ao-selecionar-para-adicionar-um-novo-endereco-primeiro
+slug: a-interface-do-usuario-nao-mostra-o-formulario-para-editar-o-endereco-ao-selecionar-primeiro-a-adicao-de-um-novo-endereco
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 747772
 ---
 
@@ -23,27 +23,23 @@ internalReference: 747772
 </div>
 
 
-A IU não mostra o formulário correto para editar o endereço selecionado na etapa de Envio ao selecionar para adicionar um novo endereço primeiro.
-
-
-##
+A interface do usuário não mostra o formulário correto para editar o endereço selecionado na etapa de envio ao selecionar a adição de um novo endereço primeiro.
 
 ## Simulação
 
 
 
-- Ter um usuário com um perfil completo;
+- Tenha um usuário com um perfil completo;
 - Clique para adicionar um novo endereço, não digite/selecione nada e volte para a lista de endereços;
 - Clique para editar o endereço selecionado;
-- Você verá a mesma forma como ao adicionar um novo endereço.
+- Você verá o mesmo formulário usado para adicionar um novo endereço.
 
 
-##
 
 ## Workaround
 
 
-Recarregue a página para poder editar novamente o endereço selecionado.
+Recarregue a página para poder editar o endereço selecionado novamente.
 
 
 
diff --git a/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md b/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
new file mode 100644
index 000000000..fbeb861fd
--- /dev/null
+++ b/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
@@ -0,0 +1,42 @@
+---
+title: 'A interface do usuário fica congelada se ocorrer um erro no processo interno da ordem de colocação'
+id: pt5Orot3i9BlYCt4E2Kj5
+status: PUBLISHED
+createdAt: 2023-11-28T18:55:54.950Z
+updatedAt: 2023-11-28T18:55:55.649Z
+publishedAt: 2023-11-28T18:55:55.649Z
+firstPublishedAt: 2023-11-28T18:55:55.649Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-fica-congelada-se-ocorrer-um-erro-no-processo-interno-da-ordem-de-colocacao
+locale: pt
+kiStatus: Backlog
+internalReference: 943771
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando ocorre um erro durante o processo interno de colocação de pedido, a interface do usuário fica congelada no carregamento sem nenhuma mensagem de erro/aviso.
+
+## Simulação
+
+
+Esse comportamento foi observado quando o Tax Service atingiu o tempo limite durante a solicitação de colocação de pedido, mas não se limita a isso.
+
+
+
+## Workaround
+
+
+Atualize a página.
+
+
+
+
diff --git a/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md b/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
new file mode 100644
index 000000000..fa1919e79
--- /dev/null
+++ b/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
@@ -0,0 +1,44 @@
+---
+title: 'A interface do usuário mostra que uma retirada foi selecionada no carrinho com assinaturas, mas não foi na API'
+id: 6WUGylIHWZtfeAm7hplYHD
+status: PUBLISHED
+createdAt: 2024-03-08T19:08:16.010Z
+updatedAt: 2024-03-08T19:08:17.012Z
+publishedAt: 2024-03-08T19:08:17.012Z
+firstPublishedAt: 2024-03-08T19:08:17.012Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-mostra-que-uma-retirada-foi-selecionada-no-carrinho-com-assinaturas-mas-nao-foi-na-api
+locale: pt
+kiStatus: Backlog
+internalReference: 996976
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+As opções de retirada são oferecidas aos compradores em um carrinho com um item com uma assinatura. Quando uma das retiradas é selecionada, o checkout muda automaticamente para entrega, mas a interface do usuário ainda mostra que a retirada foi selecionada.
+
+## Simulação
+
+
+
+- Configure uma assinatura;
+- Adicione o item com a assinatura ao carrinho;
+- Na etapa de envio, selecione "Pick up in store" (Retirar na loja);
+- Verifique o formulário de pedido via API, e a entrega será selecionada
+
+## Workaround
+
+
+Abra um ticket para o Suporte da VTEX solicitando a ativação de pontos de retirada para pedidos de assinatura.
+
+
+
+
diff --git a/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md b/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
new file mode 100644
index 000000000..379c48023
--- /dev/null
+++ b/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
@@ -0,0 +1,46 @@
+---
+title: 'A interface do usuário mostra pontos de coleta duplicados quando um item para entrega está entre itens para coleta'
+id: lIP6kRDsi23lNQd7RzNfY
+status: PUBLISHED
+createdAt: 2023-09-25T13:50:27.481Z
+updatedAt: 2023-10-18T14:36:11.434Z
+publishedAt: 2023-10-18T14:36:11.434Z
+firstPublishedAt: 2023-09-25T13:50:28.066Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-mostra-pontos-de-coleta-duplicados-quando-um-item-para-entrega-esta-entre-itens-para-coleta
+locale: pt
+kiStatus: Backlog
+internalReference: 906549
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Em um carrinho com pelo menos três produtos, onde os pedidos de itens são: O primeiro é para retirada, o segundo é para entrega e o terceiro é para retirada, a interface do usuário mostrará o ponto de retirada duplicado. Isso acontece porque a API agrupará o 1º item e o 3º item, já que se trata do mesmo SLA.
+
+É possível ir para a etapa de pagamento e concluir a compra.
+
+## Simulação
+
+
+
+- Adicionar um item ao carrinho para retirada;
+- Adicionar um item ao carrinho para entrega;
+- Adicionar outro item ao carrinho para retirada;
+- Na etapa de envio, a retirada será duplicad
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
new file mode 100644
index 000000000..fcb225f88
--- /dev/null
+++ b/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -0,0 +1,43 @@
+---
+title: 'A interface do usuário mostra "Presentes escolhidos!" ao usar o recurso de substituição de pedidos'
+id: 4efm7L6hQhad98uYkjzrXO
+status: PUBLISHED
+createdAt: 2023-09-27T20:57:46.944Z
+updatedAt: 2023-09-27T20:57:47.516Z
+publishedAt: 2023-09-27T20:57:47.516Z
+firstPublishedAt: 2023-09-27T20:57:47.516Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-mostra-presentes-escolhidos-ao-usar-o-recurso-de-substituicao-de-pedidos
+locale: pt
+kiStatus: Backlog
+internalReference: 909137
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao usar o recurso de substituição de pedidos, a interface do usuário do checkout mostra "Presentes escolhidos!" mesmo que não haja nenhuma promoção de presentes configurada.
+
+## Simulação
+
+
+
+- Acesse My Orders (Meus pedidos) e selecione um pedido;
+- Clique em "Change Order" (Alterar pedido) e selecione o motivo "I bought the wrong number/size and want to change it" (Comprei o número/tamanho errado e quero alterá-lo);
+- Você será redirecionado para o checkout e haverá a mensagem "Gifts picked!" na tela
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md b/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
new file mode 100644
index 000000000..f705d080c
--- /dev/null
+++ b/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
@@ -0,0 +1,49 @@
+---
+title: 'A interface do usuário aciona solicitações separadas para cada chave/campo de um anexo'
+id: 5IF3veMFTFi9dERoEokokt
+status: PUBLISHED
+createdAt: 2024-03-01T21:05:37.154Z
+updatedAt: 2024-03-01T21:07:41.105Z
+publishedAt: 2024-03-01T21:07:41.105Z
+firstPublishedAt: 2024-03-01T21:05:37.941Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: a-interface-do-usuario-aciona-solicitacoes-separadas-para-cada-chavecampo-de-um-anexo
+locale: pt
+kiStatus: Backlog
+internalReference: 336371
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando você define o valor de um campo de anexo de item por meio da interface do usuário, isso aciona uma solicitação para atualizar o orderForm, mesmo que ainda haja mais campos restantes.
+Essa solicitação será processada e a resposta será o orderForm atualizado.
+
+Nos casos em que o anexo tiver vários campos de texto abertos, isso poderá fazer com que os campos subsequentes sejam substituídos enquanto você estiver digitando seus valores.
+Isso acontece porque a solicitação de atualização terá sido enviada quando esse campo ainda estava em branco e, portanto, também estará em branco na resposta.
+
+Nos casos em que o item tiver um anexo de assinatura com várias chaves, isso poderá disparar uma mensagem de erro como "unable to communicate with seller" / "não foi possível se comunicar com o vendedor".
+Isso acontece porque a assinatura espera que várias chaves tenham sido preenchidas, mas a primeira solicitação só enviou uma.
+
+## Simulação
+
+
+Crie um anexo com pelo menos duas chaves/campos.
+Adicione um item vinculado a esse anexo em seu carrinho e, em seguida, adicione o anexo.
+Por fim, defina o valor de um campo e observe o comportamento que se segue
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md b/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md
index 7d5e47601..a0deac9e9 100644
--- a/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md
+++ b/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md
@@ -3,8 +3,8 @@ title: 'Incapaz de cancelar transações que tiveram mudança de configuração
 id: 2bhsI5119DLOhNjk2cb6q
 status: PUBLISHED
 createdAt: 2022-06-28T16:44:10.992Z
-updatedAt: 2022-11-25T22:06:55.006Z
-publishedAt: 2022-11-25T22:06:55.006Z
+updatedAt: 2024-02-16T20:24:09.734Z
+publishedAt: 2024-02-16T20:24:09.734Z
 firstPublishedAt: 2022-06-28T16:44:11.460Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: incapaz-de-cancelar-transacoes-que-tiveram-mudanca-de-configuracao-de-pagamento-dividido
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 364382
 ---
 
diff --git a/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md b/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md
new file mode 100644
index 000000000..7fad9a014
--- /dev/null
+++ b/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md
@@ -0,0 +1,45 @@
+---
+title: 'Não é possível fazer login pelo aplicativo do Google no iOS'
+id: 1YxuqHJbbKnzdv1d6LrfR2
+status: PUBLISHED
+createdAt: 2023-10-26T16:50:11.505Z
+updatedAt: 2024-03-20T20:34:16.469Z
+publishedAt: 2024-03-20T20:34:16.469Z
+firstPublishedAt: 2023-10-26T16:50:12.188Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: nao-e-possivel-fazer-login-pelo-aplicativo-do-google-no-ios
+locale: pt
+kiStatus: Backlog
+internalReference: 926239
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao fazer login na loja a partir do aplicativo do Google (somente no aplicativo do Google e não no navegador Google Chrome em dispositivos iOS), a opção entra em loop e nunca abre o Google para escolher a conta.
+
+## Simulação
+
+
+-Use o aplicativo do Google no IOS;
+-Acesse o site que tem a autenticação do Google ativada na webstore;
+-Clique em fazer login e escolha "Fazer login com o Google";
+
+
+
+## Workaround
+
+
+Use outro navegador mais convencional para acessar a loja, por exemplo, o Google Chrome.
+
+
+
+
+
diff --git a/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md b/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
new file mode 100644
index 000000000..2f68a7ae5
--- /dev/null
+++ b/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
@@ -0,0 +1,49 @@
+---
+title: 'Não é possível fazer upload de imagens de planilhas com serviços de host usando o protocolo de criptografia SSL1.3'
+id: sqoXJSms7bhmdNe0Id111
+status: PUBLISHED
+createdAt: 2023-06-28T12:23:54.884Z
+updatedAt: 2023-06-28T12:25:18.545Z
+publishedAt: 2023-06-28T12:25:18.545Z
+firstPublishedAt: 2023-06-28T12:23:55.364Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: nao-e-possivel-fazer-upload-de-imagens-de-planilhas-com-servicos-de-host-usando-o-protocolo-de-criptografia-ssl13
+locale: pt
+kiStatus: Backlog
+internalReference: 851911
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o host de imagens da planilha usa um protocolo de criptografia SSL1.3, aparece um erro ao tentar carregar a planilha:
+
+"Falha ao processar o registro. Verifique se os dados da planilha estão consistentes e tente novamente. Detalhes do erro: Ocorreu um erro ao enviar a solicitação."
+
+Esse erro ocorre porque nosso serviço do Windows só permite versões mais antigas, como 1.2 ou 1.1.
+
+
+## Simulação
+
+
+
+1. Use um host com uma versão de protocolo mais recente;
+2. Tente carregar uma imagem, usando a planilha eletrônica, que está hospedada lá;
+3. Verifique se a mensagem de erro é exibida
+
+## Workaround
+
+
+Use um host diferente ou valide com o host para usar uma versão mais antiga.
+
+
+
+
+
diff --git a/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md b/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md
new file mode 100644
index 000000000..295f44a37
--- /dev/null
+++ b/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md
@@ -0,0 +1,43 @@
+---
+title: 'Os PDPs de produtos indisponíveis ainda estão sendo devolvidos'
+id: 6Q2TOp3UPHuCXDpZceV1Dn
+status: PUBLISHED
+createdAt: 2024-05-31T14:43:14.505Z
+updatedAt: 2024-06-04T12:10:43.840Z
+publishedAt: 2024-06-04T12:10:43.840Z
+firstPublishedAt: 2024-05-31T14:43:15.347Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: os-pdps-de-produtos-indisponiveis-ainda-estao-sendo-devolvidos
+locale: pt
+kiStatus: Backlog
+internalReference: 1041920
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando um produto não está disponível, seu PDP ainda pode ser devolvido.
+
+## Simulação
+
+
+Tente acessar o PDP de um produto que não está disponível na Faststore.
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md b/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
new file mode 100644
index 000000000..6ef5bb6bd
--- /dev/null
+++ b/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
@@ -0,0 +1,41 @@
+---
+title: 'Priorização de resultados de pesquisa desnecessários por diacríticos para o português'
+id: 3lbgwHFc9RLusAnZnvnE1H
+status: PUBLISHED
+createdAt: 2024-05-07T15:24:18.404Z
+updatedAt: 2024-05-07T16:55:01.818Z
+publishedAt: 2024-05-07T16:55:01.818Z
+firstPublishedAt: 2024-05-07T15:24:19.224Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: priorizacao-de-resultados-de-pesquisa-desnecessarios-por-diacriticos-para-o-portugues
+locale: pt
+kiStatus: Backlog
+internalReference: 1028763
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A Pesquisa Inteligente prioriza os resultados que têm uma correspondência exata, considerando os diacríticos do termo pesquisado e os produtos.
+
+Em alguns idiomas, eles podem gerar palavras completamente diferentes, mas para outros, isso não é importante o suficiente ou pode estar relacionado a erros de digitação frequentes.
+
+Em português, diacríticos como acento agudo, acento circunflexo e til se enquadram nesse cenário. Um produto ou um termo de pesquisa sem o diacrítico priorizará alguns produtos em detrimento de outros, dependendo de como eles estão registrados. Para esse idioma, a normalização é esperada.
+
+## Simulação
+
+
+Em uma loja em português, a busca por "tênis" apresentará primeiro os produtos com "tenis" (correspondência exata com diacríticos) e só depois os resultados com "tênis" (correspondência exata ignorando os diacríticos)
+
+## Workaround
+
+
+Recomenda-se que o catálogo de produtos mantenha sempre a mesma escrita para seus produtos. Se não for aplicável, um sinônimo pode ajudar a manter os termos equivalentes.
+
diff --git a/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md b/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md
index 2f9a18b6a..0e96c9980 100644
--- a/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md
+++ b/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md
@@ -3,8 +3,8 @@ title: 'Pedidos desnecessários de simulação e componentes sendo recarregados'
 id: 1qXJU1XC4r0e9KWxNUKp3L
 status: PUBLISHED
 createdAt: 2022-08-30T17:34:47.635Z
-updatedAt: 2022-11-25T21:50:25.658Z
-publishedAt: 2022-11-25T21:50:25.658Z
+updatedAt: 2024-02-16T20:25:15.198Z
+publishedAt: 2024-02-16T20:25:15.198Z
 firstPublishedAt: 2022-08-30T17:34:48.111Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: pedidos-desnecessarios-de-simulacao-e-componentes-sendo-recarregados
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 648298
 ---
 
diff --git a/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md b/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md
new file mode 100644
index 000000000..c211f8fc9
--- /dev/null
+++ b/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md
@@ -0,0 +1,46 @@
+---
+title: 'Recarregamento inesperado ao registrar/atualizar um produto'
+id: 4XAYOJG7cgEJG6PqcmOkAY
+status: PUBLISHED
+createdAt: 2023-07-17T19:00:56.863Z
+updatedAt: 2023-10-20T13:42:32.569Z
+publishedAt: 2023-10-20T13:42:32.569Z
+firstPublishedAt: 2023-07-17T19:00:57.611Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: recarregamento-inesperado-ao-registraratualizar-um-produto
+locale: pt
+kiStatus: Backlog
+internalReference: 863542
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao registrar ou atualizar um formulário de produto, alguns usuários relatam que, ao realizar essa ação várias vezes seguidas, em algum momento a página é forçada e atualizada por conta própria.
+
+Não conseguimos encontrar um padrão que justifique isso
+
+## Simulação
+
+
+
+Atualização/registro de um formulário de produto várias vezes seguidas.
+é difícil simular, pois é totalmente aleatóri
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
new file mode 100644
index 000000000..7f82376a2
--- /dev/null
+++ b/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
@@ -0,0 +1,53 @@
+---
+title: 'Erro "Unhandled exception" ao alterar a edição da conta'
+id: 1NVjCrlRkadscl8fW9rOdA
+status: PUBLISHED
+createdAt: 2023-09-26T12:45:44.999Z
+updatedAt: 2024-02-26T17:22:29.322Z
+publishedAt: 2024-02-26T17:22:29.322Z
+firstPublishedAt: 2023-09-26T12:45:45.927Z
+contentType: knownIssue
+productTeam: Apps
+author: 2mXZkbi0oi061KicTExNjo
+tag: Apps
+slug: erro-unhandled-exception-ao-alterar-a-edicao-da-conta
+locale: pt
+kiStatus: Backlog
+internalReference: 907294
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Às vezes, quando alteramos a edição de uma conta ou espaço de trabalho, podemos encontrar o seguinte erro:
+
+
+    - error: Exceção não tratada - erro: Informe o problema em https://github.com/vtex/toolbelt/issues
+
+
+O erro não é consistente, não acontece o tempo todo.
+
+Se o mestre da loja estiver usando o `edition-business` e quiser alterar a edição para `edition-store` em um espaço de trabalho, é mais provável que esse erro ocorra.
+
+## Simulação
+
+
+Se você tentar alterar a edição de qualquer conta de teste ou espaço de trabalho, esse erro acabará ocorrendo no processo.
+
+
+
+## Workaround
+
+
+
+- Execute o comando `vtex edition get` para ter certeza de que a edição não foi alterada. Às vezes, a edição é alterada mesmo quando o erro é exibido;
+- Se os aplicativos também não foram atualizados, tente executar o comando `vtex update`;
+- Aguarde um pouco e tente novamente;
+- Também pode acontecer de o erro Unhandled exception não ser exibido, a edição será alterada, mas os aplicativos não serão atualizados. Nesse caso, basta executar o comando `vtex update`
+
+
+
diff --git a/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md b/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
index f7816f7e1..0003b8b3a 100644
--- a/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
+++ b/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
@@ -3,8 +3,8 @@ title: 'Mensagem de erro inespecífica ao exportar ProdutoExportacaoImportacaoEs
 id: 3rtDeX0QppmbXOvuCtC1Lr
 status: PUBLISHED
 createdAt: 2022-03-22T13:09:32.153Z
-updatedAt: 2022-11-25T21:44:55.880Z
-publishedAt: 2022-11-25T21:44:55.880Z
+updatedAt: 2024-02-16T20:29:49.944Z
+publishedAt: 2024-02-16T20:29:49.944Z
 firstPublishedAt: 2022-03-22T13:09:32.886Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: mensagem-de-erro-inespecifica-ao-exportar-produtoexportacaoimportacaoespecificacaov2aspx
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 314227
 ---
 
diff --git a/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md b/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
new file mode 100644
index 000000000..2433a33c2
--- /dev/null
+++ b/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
@@ -0,0 +1,48 @@
+---
+title: 'Campos não suportados pela Intelligent Search API retornam dados errados ou vazios'
+id: Jvm9oLhUM6NqCslpBqSti
+status: PUBLISHED
+createdAt: 2024-05-13T21:03:14.026Z
+updatedAt: 2024-06-25T19:11:41.925Z
+publishedAt: 2024-06-25T19:11:41.925Z
+firstPublishedAt: 2024-05-13T21:03:15.346Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: campos-nao-suportados-pela-intelligent-search-api-retornam-dados-errados-ou-vazios
+locale: pt
+kiStatus: Backlog
+internalReference: 1032531
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A API de pesquisa inteligente baseia-se principalmente na API de pesquisa de catálogo herdada por motivos de compatibilidade, mas nem todas as propriedades retornam as mesmas informações. Em alguns casos, elas são diferentes ou estão vazias.
+
+Algumas propriedades afetadas:
+
+- "modalType" (retorna vazio)
+- "imageText" (retorna o mesmo que "imageLabel")
+- "kitItems" (retorna vazio)
+
+## Simulação
+
+
+
+- registrar o valor de um campo afetado no módulo Catalog
+- comparar a resposta para o campo específico entre as APIs Catalog Search e Intelligent Searc
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md b/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
index 3ea424b15..2e8860a57 100644
--- a/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
+++ b/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
@@ -3,8 +3,8 @@ title: 'Atualizar vendedor usando Admin está definindo alguns campos de volta p
 id: 2gtqnZmCW59OKoqRpU3UaQ
 status: PUBLISHED
 createdAt: 2022-06-30T12:21:23.852Z
-updatedAt: 2022-11-25T22:00:35.980Z
-publishedAt: 2022-11-25T22:00:35.980Z
+updatedAt: 2024-02-16T20:28:26.435Z
+publishedAt: 2024-02-16T20:28:26.435Z
 firstPublishedAt: 2022-06-30T12:21:24.538Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: atualizar-vendedor-usando-admin-esta-definindo-alguns-campos-de-volta-para-o-valor-padrao-depois-de-modificalo-via-api
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 608120
 ---
 
diff --git a/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md b/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
new file mode 100644
index 000000000..a6ef8a525
--- /dev/null
+++ b/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
@@ -0,0 +1,51 @@
+---
+title: 'A atualização das políticas comerciais disponíveis do vendedor não aciona a indexação automática'
+id: 45FOjSN4a5ZhCqilQfUX99
+status: PUBLISHED
+createdAt: 2024-05-31T13:49:57.732Z
+updatedAt: 2024-05-31T13:49:58.764Z
+publishedAt: 2024-05-31T13:49:58.764Z
+firstPublishedAt: 2024-05-31T13:49:58.764Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: a-atualizacao-das-politicas-comerciais-disponiveis-do-vendedor-nao-aciona-a-indexacao-automatica
+locale: pt
+kiStatus: Backlog
+internalReference: 1041874
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Na UI de gerenciamento do vendedor, remova ou adicione uma nova política comercial a um vendedor.
+
+Esse processo é salvo com êxito, mas as informações não são atualizadas automaticamente no indexador de produtos relacionados a esse vendedor específico.
+
+Como consequência, a oferta do vendedor para esses produtos ficará desatualizada como:
+- ainda disponível na política comercial (se a ação foi removê-la);
+- não disponível na política comercial (se a ação foi adicioná-la).
+
+
+## Simulação
+
+
+
+- Verifique um produto que tenha uma oferta de um vendedor em uma política comercial específica;
+- Remova a política comercial desse vendedor usando a UI de gerenciamento do vendedor;
+- Verificar se a ação não foi refletida no produto
+
+## Workaround
+
+
+Indexar o produto manualmente.
+
+
+
+
+
diff --git a/docs/known-issues/pt/update-users-name-in-the-login-section.md b/docs/known-issues/pt/update-users-name-in-the-login-section.md
index ca261be87..17afc996b 100644
--- a/docs/known-issues/pt/update-users-name-in-the-login-section.md
+++ b/docs/known-issues/pt/update-users-name-in-the-login-section.md
@@ -3,8 +3,8 @@ title: 'Atualizar o nome do usuário na seção de login'
 id: 2jshd2ApTq7hKNLbQiCWdS
 status: PUBLISHED
 createdAt: 2022-03-14T17:20:40.732Z
-updatedAt: 2022-11-25T21:57:07.628Z
-publishedAt: 2022-11-25T21:57:07.628Z
+updatedAt: 2024-02-16T20:26:07.889Z
+publishedAt: 2024-02-16T20:26:07.889Z
 firstPublishedAt: 2022-03-14T17:20:42.505Z
 contentType: knownIssue
 productTeam: Identity
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Identity
 slug: atualizar-o-nome-do-usuario-na-secao-de-login
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 542029
 ---
 
diff --git a/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md b/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
index f947d468c..7d7e1f6b5 100644
--- a/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
+++ b/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
@@ -3,8 +3,8 @@ title: 'Atualização das especificações do produto Impossível devido à falt
 id: 6FeuIyF2E5WdS0PNRRzgdA
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:06.720Z
-updatedAt: 2022-11-25T21:44:35.149Z
-publishedAt: 2022-11-25T21:44:35.149Z
+updatedAt: 2024-02-16T20:29:52.260Z
+publishedAt: 2024-02-16T20:29:52.260Z
 firstPublishedAt: 2022-06-28T16:55:07.124Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: atualizacao-das-especificacoes-do-produto-impossivel-devido-a-falta-de-propriedade-no-get-resp-json
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 301725
 ---
 
diff --git a/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md b/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md
new file mode 100644
index 000000000..5050f5259
--- /dev/null
+++ b/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md
@@ -0,0 +1,47 @@
+---
+title: 'O upload de arquivo não está funcionando em admin/portal/#/sites/default/code'
+id: 5pFAkaymcuOQMAqUDGPQZK
+status: PUBLISHED
+createdAt: 2023-09-12T13:37:36.429Z
+updatedAt: 2023-09-12T13:37:37.323Z
+publishedAt: 2023-09-12T13:37:37.323Z
+firstPublishedAt: 2023-09-12T13:37:37.323Z
+contentType: knownIssue
+productTeam: Portal
+author: 2mXZkbi0oi061KicTExNjo
+tag: Portal
+slug: o-upload-de-arquivo-nao-esta-funcionando-em-adminportalsitesdefaultcode
+locale: pt
+kiStatus: Backlog
+internalReference: 897956
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao tentar carregar um novo arquivo em admin/portal/#/sites/default/code, nada acontece. Ao verificar o console no devTools, podemos ver uma mensagem de erro:
+"eventTrackerService não está definido"
+
+## Simulação
+
+
+
+1. Vá para admin/portal/#/sites/default/code
+2. Vá para New -> Upload File -> selecione o arquivo que deseja importar -> clique em create
+ ![](https://vtexhelp.zendesk.com/attachments/token/4uSgPeUxG9xAOkTq1HUs8khX6/?name=image.png)
+3. Verifique se nada acontece
+
+## Workaround
+
+
+O WA é criar o arquivo diretamente nesta UI.
+Vá para New -> File -> Nomeie seu arquivo e clique em create -> Insira o código e clique em save.
+
+
+
+
+
diff --git a/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md b/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
new file mode 100644
index 000000000..5280216f2
--- /dev/null
+++ b/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
@@ -0,0 +1,53 @@
+---
+title: 'O usuário ainda pode ver e acessar os recursos do CMS mesmo sem a permissão correta'
+id: n2BmrCyzXD04sysczRuyt
+status: PUBLISHED
+createdAt: 2024-06-07T12:22:10.494Z
+updatedAt: 2024-06-07T12:22:11.466Z
+publishedAt: 2024-06-07T12:22:11.466Z
+firstPublishedAt: 2024-06-07T12:22:11.466Z
+contentType: knownIssue
+productTeam: CMS
+author: 2mXZkbi0oi061KicTExNjo
+tag: CMS
+slug: o-usuario-ainda-pode-ver-e-acessar-os-recursos-do-cms-mesmo-sem-a-permissao-correta
+locale: pt
+kiStatus: Backlog
+internalReference: 1046263
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se o usuário não tiver nenhuma das permissões do CMS, ele não deverá ser capaz de acessar ou mesmo ver os módulos do CMS. Mas isso não está acontecendo.
+
+## Simulação
+
+
+Tente acessar os módulos CMS usando um usuário que não tenha as seguintes permissões LM:
+
+      CMS:
+
+- Consulte o menu CMS na barra superior
+- Configurações
+
+GraphQL:
+- API GraphQL do CMS
+
+O usuário ainda poderá acessar e ver os recursos (mas não editá-los).
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
new file mode 100644
index 000000000..39143a1e5
--- /dev/null
+++ b/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -0,0 +1,51 @@
+---
+title: 'O usuário apenas com a função "User Administrator - RESTRICTED" não consegue listar os usuários'
+id: ifXUAzgJ1xr8ezhqKpRUI
+status: PUBLISHED
+createdAt: 2023-11-08T18:07:14.508Z
+updatedAt: 2023-11-08T18:07:15.030Z
+publishedAt: 2023-11-08T18:07:15.030Z
+firstPublishedAt: 2023-11-08T18:07:15.030Z
+contentType: knownIssue
+productTeam: Identity
+author: 2mXZkbi0oi061KicTExNjo
+tag: Identity
+slug: o-usuario-apenas-com-a-funcao-user-administrator-restricted-nao-consegue-listar-os-usuarios
+locale: pt
+kiStatus: Backlog
+internalReference: 932666
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se um usuário administrador tiver apenas a função "**User Administrator - RESTRICTED**" (recurso "**Save user**"), a lista de usuários não estará disponível e não será possível fazer as edições ou exclusões necessárias.
+
+## Simulação
+
+
+
+- Tenha um usuário com apenas a função "**User Administrator - RESTRICTED**";
+- Acesse a página "**Admin Users**" com esse usuário (por exemplo, https://my-account-here.myvtex.com/admin/users);
+- Você pode notar que a lista está vazia, mesmo com usuários já registrados ("_No users found :: The user search returned an empty list. Tente remover qualquer filtro de pesquisa ou adicionar novos usuários a essa conta."):
+ ![](https://vtexhelp.zendesk.com/attachments/token/fZ2k11R3xPrhNv5yHVkv9alam/?name=image.png)
+
+- É possível adicionar o usuário desejado e incluir as funções necessárias, mas não podemos acessar os usuários para adicionar/editar/remover funções ou mesmo excluir o usuário por meio do registro, mas somente por meio da função
+
+## Workaround
+
+
+Você pode adicionar ou remover o usuário da função acessando a função diretamente.
+
+Você também pode criar uma função personalizada somente com os recursos "**Get paged roles**" e "**Get paged users**":
+ ![](https://vtexhelp.zendesk.com/attachments/token/yjNfjlnfFaBrXZE6gx97OaxHy/?name=image.png)
+Em seguida, adicione-a ao usuário que pode salvar usuários.
+
+
+
+
+
diff --git a/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md b/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md
new file mode 100644
index 000000000..5bae3b8f7
--- /dev/null
+++ b/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md
@@ -0,0 +1,40 @@
+---
+title: 'Os usuários não conseguem acessar a administração do Gift Card (página em loop)'
+id: 5FowAAf8VulbVXcQIeSmHd
+status: PUBLISHED
+createdAt: 2024-05-02T15:26:57.386Z
+updatedAt: 2024-05-02T15:26:58.463Z
+publishedAt: 2024-05-02T15:26:58.463Z
+firstPublishedAt: 2024-05-02T15:26:58.463Z
+contentType: knownIssue
+productTeam: Payments
+author: 2mXZkbi0oi061KicTExNjo
+tag: Payments
+slug: os-usuarios-nao-conseguem-acessar-a-administracao-do-gift-card-pagina-em-loop
+locale: pt
+kiStatus: Backlog
+internalReference: 1025971
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se os usuários bloquearem cookies de terceiros (configurações do navegador), eles não poderão acessar o módulo Gift Card no admin, pois há um cookie definido em outro domínio da VTEX.
+
+## Simulação
+
+
+Depois de bloquear os cookies de terceiros, é possível simular o problema mencionado acima. Você também pode inspecionar a página (ferramentas de desenvolvedor) e ir para a guia Rede (procure por Vale.aspx), haverá um código de status 302
+
+## Workaround
+
+
+Coloque na lista de permissões os cookies de terceiros presentes no domínio myvtex.com.
+
+
+
+
diff --git a/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md b/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
new file mode 100644
index 000000000..d2e36c0ef
--- /dev/null
+++ b/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
@@ -0,0 +1,48 @@
+---
+title: 'Os usuários com mais de um pedido registrado na entidade BK com e-mails diferentes não conseguem ver os pedidos na página My Account'
+id: 43NLxAbOtyVzOCdS9Dns8c
+status: PUBLISHED
+createdAt: 2024-02-21T22:30:42.218Z
+updatedAt: 2024-02-21T22:30:43.137Z
+publishedAt: 2024-02-21T22:30:43.137Z
+firstPublishedAt: 2024-02-21T22:30:43.137Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: os-usuarios-com-mais-de-um-pedido-registrado-na-entidade-bk-com-emails-diferentes-nao-conseguem-ver-os-pedidos-na-pagina-my-account
+locale: pt
+kiStatus: Backlog
+internalReference: 986324
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Devido à unificação de perfis, alguns usuários podem ter pedidos com e-mails diferentes, e isso é um problema para mostrar os pedidos na página minha conta (meus pedidos).
+
+O my orders solicita essas informações na entidade BK dos dados mestre para remover o impacto do atraso na indexação, mas o BK tem o histórico e os pedidos com e-mails diferentes. Mas o OMS tem a linha de código para verificar se o e-mail retornado está correto, verificando o e-mail do consultor e o e-mail registrado nos pedidos.
+
+## Simulação
+
+
+Dois pedidos criados com e-mails diferentes, por exemplo, joao@gmail.com e joao2@gmail.com, quando esse usuário tiver o perfil de unificação, somente um e-mail será válido.
+Depois disso, se o joao2@gmail.com fizer login na página my account (minha conta), não será possível ver os pedidos porque há um pedido antigo sem o caractere "2" no e-mail, portanto, a chave principal (e-mail) é diferente.
+
+
+
+
+
+## Workaround
+
+
+Não há solução alternativa no momento.
+
+
+
+
+
diff --git a/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md b/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
new file mode 100644
index 000000000..a7165c3a9
--- /dev/null
+++ b/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
@@ -0,0 +1,43 @@
+---
+title: 'UseSessionRegionAtCheckout não funciona corretamente ao adicionar o primeiro item ao carrinho'
+id: 2NzgWTbaHF47f5dl49A2D5
+status: PUBLISHED
+createdAt: 2023-10-24T22:51:27.435Z
+updatedAt: 2023-10-26T10:55:29.843Z
+publishedAt: 2023-10-26T10:55:29.843Z
+firstPublishedAt: 2023-10-24T22:51:28.246Z
+contentType: knownIssue
+productTeam: Checkout
+author: 2mXZkbi0oi061KicTExNjo
+tag: Checkout
+slug: usesessionregionatcheckout-nao-funciona-corretamente-ao-adicionar-o-primeiro-item-ao-carrinho
+locale: pt
+kiStatus: Backlog
+internalReference: 925049
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Se uma conta tiver a opção "UseSessionRegionAtCheckout" configurada, ao adicionar um item e o formulário de pedido não tiver "shippingData", o vendedor não será definido, mostrando preços e disponibilidade diferentes.
+
+## Simulação
+
+
+
+- A conta deve estar usando UseSessionRegionAtCheckout;
+- Defina um regionId na sessão;
+- Adicione um item ao carrinho; ele pode mostrar preços e disponibilidade diferentes
+
+## Workaround
+
+
+Atualize o orderForm (API Get current ou crie um novo carrinho) usando o parâmetro `?refreshOutdatedData=true`.
+
+
+
+
diff --git a/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md b/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
index 37cfb563a..031c04a87 100644
--- a/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
+++ b/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
@@ -3,8 +3,8 @@ title: 'O uso de muitos filtros na lista OMS afeta os resultados do relatório'
 id: WO9AvZxmUkmil35OZb8Lr
 status: PUBLISHED
 createdAt: 2023-02-17T17:45:57.039Z
-updatedAt: 2023-02-17T17:52:41.370Z
-publishedAt: 2023-02-17T17:52:41.370Z
+updatedAt: 2024-06-28T19:28:50.107Z
+publishedAt: 2024-06-28T19:28:50.107Z
 firstPublishedAt: 2023-02-17T17:50:29.929Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,34 +12,41 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: o-uso-de-muitos-filtros-na-lista-oms-afeta-os-resultados-do-relatorio
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 756198
 ---
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
 </div>
 
-O uso de filtros na Lista de Gerenciamento de Pedidos gera um parâmetro na URL que ajuda a definir o que é mostrado quando a página é carregada e a gerar o relatório de pedidos exportados. Nesse sentido, como usamos cada vez mais filtros, os parâmetros incluídos na URL aumentam proporcionalmente, e a cadeia de consulta aumenta, atingindo pontos (tamanho) que podem gerar vários tipos de comportamentos indesejados.
 
-Neste caso, o problema causado pelo uso de muitos filtros ao mesmo tempo (tamanho do **Query String** na URL) afeta os resultados do relatório exportado, mostrando menos pedidos do que o esperado.
+O uso de filtros na Lista de gerenciamento de pedidos gera um parâmetro no URL que ajuda a definir o que é mostrado quando a página é carregada e a gerar o relatório de pedidos exportados. Nesse sentido, à medida que usamos mais e mais filtros, os parâmetros incluídos no URL aumentam proporcionalmente e a string de consulta aumenta, chegando a pontos (tamanho) que podem gerar vários tipos de comportamentos indesejados.
 
-É importante notar que aqui estamos falando do tamanho ** da query String gerada na URL**, isto significa que não é o número de filtros usados diretamente, mas o tamanho de cada parâmetro. Nomes de filtros muito grandes podem limitar o número de filtros que você é capaz de usar para gerar um relatório consistente.
+Nesse caso, o problema causado pelo uso de muitos filtros ao mesmo tempo (tamanho da **Query String** no URL) afeta os resultados do relatório exportado, mostrando menos pedidos do que o esperado.
+
+É importante observar que aqui estamos falando do **tamanho da Query String gerada no URL**, o que significa que não é o número de filtros usados diretamente, mas o tamanho de cada parâmetro. Nomes de filtros muito grandes podem limitar o número de filtros que você pode usar para gerar um relatório consistente.
 
 ## Simulação
 
-Este cenário pode ser simulado usando múltiplos filtros "longos" na lista OMS e exportando os pedidos. Você pode ver que a exportação mostra menos pedidos do que a lista OMS.
 
+Esse cenário pode ser simulado usando-se vários filtros "longos" na lista do OMS e exportando os pedidos. Você pode ver que a exportação mostra menos pedidos do que a lista OMS
 
 ## Workaround
 
-É possível pensar em formas alternativas para evitar este tipo de problema no relatório. Aqui estão alguns pontos que podem ser úteis:
+
+É possível pensar em maneiras alternativas de evitar esse tipo de problema no relatório. Aqui estão alguns pontos que podem ser úteis:
 
 - Otimizar o nome dos parâmetros pode ser uma boa prática.
-- Exportar o relatório com poucos filtros e depois, no documento exportado, realizar os filtros adicionais ou necessários para obter as informações desejadas.
-- Pense em quebrar o relatório em mais de um, ou seja, use alguns filtros para gerar uma parte da informação e depois outro com o resto e unificar após ser descarregado.
+- Exportar o relatório com poucos filtros e, em seguida, no documento exportado, realizar os filtros adicionais ou necessários para obter as informações desejadas.
+- Pense em dividir o relatório em mais de um, ou seja, use alguns filtros para gerar uma parte das informações e, em seguida, outro com o restante e unifique após o download.
+
+Essas são apenas ideias para evitar o acúmulo de filtros e gerar essa inconsistência nas informações exportadas. Outras soluções podem ser usadas.
+
+
+
+
 
-Estas são apenas ideias para evitar a acumulação de filtros e gerar esta inconsistência nas informações exportadas. Outras soluções podem ser usadas.
 
diff --git a/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md b/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
new file mode 100644
index 000000000..3b052684d
--- /dev/null
+++ b/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
@@ -0,0 +1,46 @@
+---
+title: 'O uso do layout do controle deslizante com a propriedade navigationStep em 1 faz com que os últimos pontos fiquem vazios'
+id: 28hbmflHNhAQmHN51Y6abX
+status: PUBLISHED
+createdAt: 2023-09-29T14:41:34.387Z
+updatedAt: 2023-09-29T14:57:48.863Z
+publishedAt: 2023-09-29T14:57:48.863Z
+firstPublishedAt: 2023-09-29T14:41:35.227Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-uso-do-layout-do-controle-deslizante-com-a-propriedade-navigationstep-em-1-faz-com-que-os-ultimos-pontos-fiquem-vazios
+locale: pt
+kiStatus: Backlog
+internalReference: 910125
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando temos um bloco de layout de controle deslizante com a propriedade `navigationStep` definida como 1 e `itemsPerPage` diferente de 1, o último ponto fica vazio e não é possível excluí-lo.
+
+## Simulação
+
+
+
+- Crie um novo bloco de layout de controle deslizante
+- Defina o `navigationStep` como 1
+- Defina o `itemsPerPage` em um valor diferente de 1
+- Usando as setas do controle deslizante, tente navegar até o último ponto do controle deslizante
+- Você verá que o último ponto está vazi
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md b/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
index 27ce6b313..ca72e1a76 100644
--- a/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
+++ b/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
@@ -3,8 +3,8 @@ title: 'utmi_p e utmi_pc não sendo mantido na URL após o login'
 id: 7e8EO8EWEJCLbXs16ZofQk
 status: PUBLISHED
 createdAt: 2022-03-16T16:17:55.535Z
-updatedAt: 2022-11-25T22:11:21.772Z
-publishedAt: 2022-11-25T22:11:21.772Z
+updatedAt: 2024-02-16T20:29:25.217Z
+publishedAt: 2024-02-16T20:29:25.217Z
 firstPublishedAt: 2022-03-16T16:17:55.979Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: utmip-e-utmipc-nao-sendo-mantido-na-url-apos-o-login
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 372787
 ---
 
diff --git a/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md b/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md
new file mode 100644
index 000000000..b0d4b49b9
--- /dev/null
+++ b/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md
@@ -0,0 +1,46 @@
+---
+title: 'Falha no ValidateCartMutation quando a carga útil é grande'
+id: 5YmPMVGsi92owcmICg3CY3
+status: PUBLISHED
+createdAt: 2024-02-21T15:23:44.054Z
+updatedAt: 2024-02-21T15:23:44.919Z
+publishedAt: 2024-02-21T15:23:44.919Z
+firstPublishedAt: 2024-02-21T15:23:44.919Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: falha-no-validatecartmutation-quando-a-carga-util-e-grande
+locale: pt
+kiStatus: Backlog
+internalReference: 985867
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+Ao adicionar vários produtos no minicart, dependendo das informações associadas a esses produtos, se recebermos um erro payloadTooLarge, o produto será adicionado ao carrinho, mas não passará para o orderForm corretamente
+
+## Simulação
+
+
+
+
+- Adicione produtos ao carrinho até receber um erro 413 Payload Too Large
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md b/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
index 693cec98a..b37034e42 100644
--- a/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
+++ b/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
@@ -3,8 +3,8 @@ title: 'As transações de verificação ao salvar o cartão em MyCards não sã
 id: 3VqRlcnzHqDEx7v1IIlBuf
 status: PUBLISHED
 createdAt: 2022-03-27T15:14:55.382Z
-updatedAt: 2022-11-25T22:08:31.611Z
-publishedAt: 2022-11-25T22:08:31.611Z
+updatedAt: 2024-02-16T20:27:46.524Z
+publishedAt: 2024-02-16T20:27:46.524Z
 firstPublishedAt: 2022-03-27T15:14:56.630Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: as-transacoes-de-verificacao-ao-salvar-o-cartao-em-mycards-nao-sao-automaticamente-canceladas
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 347084
 ---
 
diff --git a/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
new file mode 100644
index 000000000..04dcb642e
--- /dev/null
+++ b/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -0,0 +1,57 @@
+---
+title: 'Autor da versão "Note: Not found on VTEX ID." no perfil'
+id: 0X6Aj6YdCXXfNweAkDS46
+status: PUBLISHED
+createdAt: 2023-10-04T21:48:14.699Z
+updatedAt: 2023-10-04T22:14:45.195Z
+publishedAt: 2023-10-04T22:14:45.195Z
+firstPublishedAt: 2023-10-04T21:48:15.379Z
+contentType: knownIssue
+productTeam: Storage
+author: 2mXZkbi0oi061KicTExNjo
+tag: Storage
+slug: autor-da-versao-note-not-found-on-vtex-id-no-perfil
+locale: pt
+kiStatus: Scheduled
+internalReference: 914314
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando o cliente faz uma compra, o autor da versão recebe um ID de usuário (guid) ou um serviço, seguido pelo login/nome/descrição "`Note: Not found on VTEX ID.`" no perfil.
+Esse comportamento não afeta o perfil ou a experiência do comprador, uma vez que se trata apenas da interface do usuário, e é possível verificar as informações pela API da versão.
+
+## Simulação
+
+
+
+- Acesse o CRM de dados mestre (por exemplo, https://my-account-here.vtexcrm.com.br);
+- Acesse a guia Entidade de dados CL (Clientes):
+- Selecione um documento e clique no ícone do olho para visualizar os dados;
+- Clique no botão "_Alterar registro_";
+- Abrir uma versão recente;
+- Verifique o "_Version author_", que será um ID de usuário, e o nome "`Note: Not found on VTEX ID.`", por exemplo:
+ ![](https://vtexhelp.zendesk.com/attachments/token/9ngSibhlO4er0Df3Fi7oQAhot/?name=image.png)
+ ![](https://vtexhelp.zendesk.com/attachments/token/8tlsDbxNSFFHdJMVHf2yvctem/?name=image.png)
+
+- Verificação pela API Get version:
+ ![](https://vtexhelp.zendesk.com/attachments/token/MRrTRox5E0t91F3OpsDcRmJ9z/?name=image.png)
+
+    "updatedBy_USER": "{\"Id\":\"d6d8269f-e7cc-4e4b-8b89-3b46a1407937\",\"Login\":\"vtex-service::checkout::stable\",\"Name\":null}",
+
+## Workaround
+
+
+Você pode verificar o autor usando nossas APIs:
+
+- Listar versões
+- Obter versão
+
+
+
+
diff --git a/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md b/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md
index f03793a84..80688dffc 100644
--- a/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md
+++ b/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md
@@ -3,8 +3,8 @@ title: 'A Via Integration não está enviando a descrição no cartão'
 id: Da5jnqoSO8an64jy29VhM
 status: PUBLISHED
 createdAt: 2023-05-16T16:47:19.803Z
-updatedAt: 2023-05-18T18:03:54.502Z
-publishedAt: 2023-05-18T18:03:54.502Z
+updatedAt: 2023-06-19T12:30:03.552Z
+publishedAt: 2023-06-19T12:30:03.552Z
 firstPublishedAt: 2023-05-16T16:47:20.416Z
 contentType: knownIssue
 productTeam: Connections
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Connections
 slug: a-via-integration-nao-esta-enviando-a-descricao-no-cartao
 locale: pt
-kiStatus: Backlog
+kiStatus: Fixed
 internalReference: 826488
 ---
 
diff --git a/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md b/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
index cc8a1b516..bb0476b78 100644
--- a/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
+++ b/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
@@ -3,8 +3,8 @@ title: 'O atributo de vídeo não está sendo enviado do vendedor para o marketp
 id: 6JfHpP6F8TGmJofoKc99ON
 status: PUBLISHED
 createdAt: 2022-02-07T20:07:23.358Z
-updatedAt: 2023-05-09T19:03:49.838Z
-publishedAt: 2023-05-09T19:03:49.838Z
+updatedAt: 2024-02-16T20:23:28.657Z
+publishedAt: 2024-02-16T20:23:28.657Z
 firstPublishedAt: 2022-02-07T20:07:23.814Z
 contentType: knownIssue
 productTeam: Catalog
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Catalog
 slug: o-atributo-de-video-nao-esta-sendo-enviado-do-vendedor-para-o-marketplace
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 519412
 ---
 
diff --git a/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md b/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md
index 26f2a9751..8cc6f48b2 100644
--- a/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md
+++ b/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md
@@ -3,8 +3,8 @@ title: 'O componente de vídeo não funciona corretamente nos dispositivos iOS'
 id: 2bRQkTdRk2OJQMw5CKVieW
 status: PUBLISHED
 createdAt: 2022-07-01T17:21:47.912Z
-updatedAt: 2022-11-25T22:13:54.314Z
-publishedAt: 2022-11-25T22:13:54.314Z
+updatedAt: 2024-02-16T20:25:23.862Z
+publishedAt: 2024-02-16T20:25:23.862Z
 firstPublishedAt: 2022-07-01T17:21:48.826Z
 contentType: knownIssue
 productTeam: Store Framework
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
 slug: o-componente-de-video-nao-funciona-corretamente-nos-dispositivos-ios
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 609462
 ---
 
diff --git a/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md b/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
new file mode 100644
index 000000000..8f851af72
--- /dev/null
+++ b/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
@@ -0,0 +1,43 @@
+---
+title: 'O evento view_cart só é recebido no dataLayer a cada duas vezes'
+id: 73fimN0XczGQch20BhGAOo
+status: PUBLISHED
+createdAt: 2024-06-12T12:58:59.438Z
+updatedAt: 2024-06-12T12:59:00.499Z
+publishedAt: 2024-06-12T12:59:00.499Z
+firstPublishedAt: 2024-06-12T12:59:00.499Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-evento-viewcart-so-e-recebido-no-datalayer-a-cada-duas-vezes
+locale: pt
+kiStatus: Backlog
+internalReference: 1048306
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O evento view_cart só é recebido no dataLayer a cada duas vezes.
+
+## Simulação
+
+
+Tente abrir o minicarro pela primeira vez, dessa vez o evento será recebido
+Quando você tentar abrir pela segunda vez, o evento não será recebido
+Na terceira vez, o evento será recebido novamente e assim por diant
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md b/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
new file mode 100644
index 000000000..b1e03782d
--- /dev/null
+++ b/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
@@ -0,0 +1,44 @@
+---
+title: 'O evento view_cart é acionado duas vezes quando alteramos a quantidade do produto no minicarro'
+id: 3NlB10z0ulKu7sySxPgkmp
+status: PUBLISHED
+createdAt: 2024-05-28T20:13:35.657Z
+updatedAt: 2024-05-28T20:13:36.602Z
+publishedAt: 2024-05-28T20:13:36.602Z
+firstPublishedAt: 2024-05-28T20:13:36.602Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: o-evento-viewcart-e-acionado-duas-vezes-quando-alteramos-a-quantidade-do-produto-no-minicarro
+locale: pt
+kiStatus: Backlog
+internalReference: 1040772
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando alteramos a quantidade de um produto no minicarro, o evento view_cart é acionado duas vezes
+
+## Simulação
+
+
+
+- Adicionar um produto ao minicarro;
+- Abra o minicarro;
+- Altere a quantidade do produto no minicarro;
+- Verifique seu dataLayer, o evento view_cart é acionado duas veze
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md b/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
index 1a3c08575..ba5d16c21 100644
--- a/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
@@ -3,8 +3,8 @@ title: ' O recurso "Produto visitado" não funciona corretamente'
 id: 5AiCVwLkGToEgtLkZVPe5i
 status: PUBLISHED
 createdAt: 2022-11-25T18:45:15.389Z
-updatedAt: 2022-11-30T19:05:56.190Z
-publishedAt: 2022-11-30T19:05:56.190Z
+updatedAt: 2024-02-16T20:27:41.835Z
+publishedAt: 2024-02-16T20:27:41.835Z
 firstPublishedAt: 2022-11-25T18:45:15.854Z
 contentType: knownIssue
 productTeam: Analytics
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Analytics
 slug: o-recurso-produto-visitado-nao-funciona-corretamente
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 701169
 ---
 
diff --git a/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md b/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
new file mode 100644
index 000000000..527f4ca9a
--- /dev/null
+++ b/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
@@ -0,0 +1,49 @@
+---
+title: 'As regras de visual merchandising não funcionam quando são fornecidos vários termos de pesquisa'
+id: 6FkfnnvFiYXYqPgMrpDgM1
+status: PUBLISHED
+createdAt: 2024-06-20T21:41:14.250Z
+updatedAt: 2024-06-20T21:41:15.088Z
+publishedAt: 2024-06-20T21:41:15.088Z
+firstPublishedAt: 2024-06-20T21:41:15.088Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: as-regras-de-visual-merchandising-nao-funcionam-quando-sao-fornecidos-varios-termos-de-pesquisa
+locale: pt
+kiStatus: Backlog
+internalReference: 1053623
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Embora seja possível fornecer vários termos de pesquisa ao criar uma regra de visual merchandising para a Pesquisa Inteligente, eles não podem ser usados. A regra será considerada inválida e não será aplicada.
+
+Termos de pesquisa diferentes podem retornar produtos completamente diferentes em um resultado de pesquisa em uma ordem diferente, o que é incompatível com a ação de fixar (_promover_) ou ocultar (_remover_) alguns produtos que uma regra visual oferece.
+
+Como uma ação inválida, não se espera que essa condição seja fornecida e ela será removida da interface.
+
+## Simulação
+
+
+
+- Criar uma regra de visual merchandising
+- Aplicar vários termos de pesquisa como uma condição para a regra
+- Selecione alguns produtos para fixar e/ou ocultar
+- Pesquise um desses termos de pesquisa e observe que os resultados não terão a regra aplicada
+- Também é possível observar o mesmo por meio da função de pesquisa explicada do administrador, que destacará que nenhuma regra foi aplicada à pesquis
+
+## Workaround
+
+
+Esse objetivo é alcançado por meio de regras manuais de merchandising. A ação de fixar e ocultar produtos é diretamente compatível com as ações de promover e remover de uma regra manual.
+
+
+
+
diff --git a/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 03de1111b..3caf89d8d 100644
--- a/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -41,5 +41,5 @@ Não se preocupe: desligar essa opção não significa que sua loja estará desp
 Se após estes passos o seu Admin ou loja ainda não carregarem, sugerimos que tente acessá-lo com outro navegador. 
 </div>  
 
-![Firefox bug PT](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/4ec41440848f1adad3924c07d5154369/Firefox_bug_PT.jpg)
+![Firefox bug PT](//images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/4ec41440848f1adad3924c07d5154369/Firefox_bug_PT.jpg)
 
diff --git a/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md b/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
new file mode 100644
index 000000000..ec35c96ca
--- /dev/null
+++ b/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
@@ -0,0 +1,44 @@
+---
+title: '<vtex.cmc ProductGifts/> não funciona antes de acessar o checkout'
+id: 3blfXfhPvY2cNEzBYGEmAo
+status: PUBLISHED
+createdAt: 2024-05-08T17:11:51.770Z
+updatedAt: 2024-05-08T17:11:52.715Z
+publishedAt: 2024-05-08T17:11:52.715Z
+firstPublishedAt: 2024-05-08T17:11:52.715Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: vtexcmc-productgifts-nao-funciona-antes-de-acessar-o-checkout
+locale: pt
+kiStatus: Backlog
+internalReference: 1029719
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+
+## Simulação
+
+
+1 - Crie uma página de produto usando o controlador <vtex.cmc ProductGifts>.
+2 - Crie uma promoção Buy One, Get One para conduzir os brindes relacionados.
+3 - Carregue a página do produto, nenhum brinde será renderizado.
+4 - Vá para a página de checkout e os brindes serão carregados.
+5 - Retorne à página do produto e os presentes estarão sendo carregados na página do produto
+
+## Workaround
+
+
+Use outros controladores de vendas cruzadas para personalizar e exibir itens como presentes, como similares, sugestões e acessórios
+
+
+
+
+
diff --git a/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md b/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
index ba57fe093..970aab24c 100644
--- a/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
+++ b/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
@@ -3,8 +3,8 @@ title: 'Temos um problema de validação do campo ClientId do Giftcard na admini
 id: 4S7CziQfj5P2NLAgUKnJnP
 status: PUBLISHED
 createdAt: 2022-03-28T00:29:38.482Z
-updatedAt: 2022-11-25T22:07:33.502Z
-publishedAt: 2022-11-25T22:07:33.502Z
+updatedAt: 2024-02-16T20:24:40.988Z
+publishedAt: 2024-02-16T20:24:40.988Z
 firstPublishedAt: 2022-03-28T00:29:39.028Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: temos-um-problema-de-validacao-do-campo-clientid-do-giftcard-na-administracao
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 454388
 ---
 
diff --git a/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md b/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
index 8dbc0a74b..bcbc1ebab 100644
--- a/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
+++ b/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
@@ -3,8 +3,8 @@ title: 'Webanalytics Viewpart Mostra o sucesso mesmo quando não está funcionan
 id: 73oMf2Wxkgw1feWUvntX6s
 status: PUBLISHED
 createdAt: 2023-03-09T18:20:47.358Z
-updatedAt: 2023-03-09T18:20:52.456Z
-publishedAt: 2023-03-09T18:20:52.456Z
+updatedAt: 2024-07-01T18:48:55.053Z
+publishedAt: 2024-07-01T18:48:55.053Z
 firstPublishedAt: 2023-03-09T18:20:48.023Z
 contentType: knownIssue
 productTeam: Portal
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
 slug: webanalytics-viewpart-mostra-o-sucesso-mesmo-quando-nao-esta-funcionando
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 768059
 ---
 
diff --git a/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md b/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md
new file mode 100644
index 000000000..5ade74313
--- /dev/null
+++ b/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md
@@ -0,0 +1,42 @@
+---
+title: 'O aplicativo Webops não está totalmente integrado ao Headless CMS'
+id: 577fIocKB9BYYCOkN9dZfW
+status: PUBLISHED
+createdAt: 2024-06-12T19:42:12.627Z
+updatedAt: 2024-06-27T17:35:21.924Z
+publishedAt: 2024-06-27T17:35:21.924Z
+firstPublishedAt: 2024-06-12T19:42:13.699Z
+contentType: knownIssue
+productTeam: FastStore
+author: 2mXZkbi0oi061KicTExNjo
+tag: FastStore
+slug: o-aplicativo-webops-nao-esta-totalmente-integrado-ao-headless-cms
+locale: pt
+kiStatus: Backlog
+internalReference: 1048810
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O aplicativo `vtex.webops` não está totalmente integrado ao CMS headless, isso está relacionado aos repositórios do Github hospedados externamente e ao processo de publicação
+
+## Simulação
+
+
+Tente fazer uma atualização no CMS headless usando o aplicativo webops; isso falhará e não haverá um commit no repositório
+
+
+
+## Workaround
+
+
+A solução alternativa é criar manualmente um commit no repositório Git da sua loja para acionar a compilação da loja e aplicar as alterações feitas no CMS headless.
+
+
+
+
diff --git a/docs/known-issues/pt/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md b/docs/known-issues/pt/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
index 6c250325b..6a547bad9 100644
--- a/docs/known-issues/pt/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
+++ b/docs/known-issues/pt/when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching.md
@@ -1,36 +1,38 @@
 ---
-title: 'When a component of the kit look is out of stock, the kit is shown as sold out on searching'
-id: 56QpnBz2ayEAe00L9ojSI0
-status: DRAFT
-createdAt: 2022-01-21T18:06:21.645Z
-updatedAt: 2022-03-16T16:22:00.845Z
-publishedAt: 
-firstPublishedAt: 
+title: 'Quando um componente de kit look não tem estoque, kit aparece esgotado na busca'
+id: 5PRtTKk1HyGkKciOussWEI
+status: PUBLISHED
+createdAt: 2017-03-29T23:44:56.615Z
+updatedAt: 2022-12-22T20:43:08.857Z
+publishedAt: 2022-12-22T20:43:08.857Z
+firstPublishedAt: 2017-03-29T23:46:36.720Z
 contentType: knownIssue
-productTeam: Portal
+productTeam: Marketing & Merchandising
 author: 2mXZkbi0oi061KicTExNjo
-tag: Portal
-slug: when-a-component-of-the-kit-look-is-out-of-stock-the-kit-is-shown-as-sold-out-on-searching
+tag: Catalog
+slug: quando-um-componente-de-kit-look-nao-tem-estoque-kit-aparece-esgotado-na-busca
 locale: pt
 kiStatus: Backlog
-internalReference: 342720
+internalReference: 
 ---
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+Quando um componente de um kit look fica sem estoque, todo o kit é exibido como esgotado na busca.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+<!--- Conta original era automacaoqa, removemos por conta de EDU-2582 --->
+
+Kit Look: `https://lojateste.vtexcommercebeta.com.br/admin/site/ProdutoForm.aspx?id=2000205`
+
+Componente indisponível: `https://lojateste.vtexcommercebeta.com.br/admin/site/SkuForm.aspx?IdSku=2000362`
+
+Exibição correta na página de produto: `https://lojateste.vtexcommercebeta.com.br/admin/site/SkuForm.aspx?IdSku=2000362`
+
+Exibição incorreta na busca: `https://lojateste.vtexcommercebeta.com.br/kits`
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+Apenas utilize Kit Look se puder garantir que todos os componentes possuem estoque.
 
diff --git a/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md b/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
new file mode 100644
index 000000000..e441fcf1a
--- /dev/null
+++ b/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
@@ -0,0 +1,42 @@
+---
+title: 'Ao acessar meus pedidos, o nome que aparece é o nome do ProductName sem as informações do SKU Name.'
+id: 1PTEStTC2MDQwZpE0myF44
+status: PUBLISHED
+createdAt: 2024-03-08T13:16:01.672Z
+updatedAt: 2024-03-08T13:16:02.950Z
+publishedAt: 2024-03-08T13:16:02.950Z
+firstPublishedAt: 2024-03-08T13:16:02.950Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: ao-acessar-meus-pedidos-o-nome-que-aparece-e-o-nome-do-productname-sem-as-informacoes-do-sku-name
+locale: pt
+kiStatus: No Fix
+internalReference: 694809
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao acessar "my orders", o nome que aparece é o nome do "ProductName" sem a informação "SKU Name", somente na interface IO.
+
+
+## Simulação
+
+
+Acessando my orders, você verá que o nome do produto é composto apenas pelo "ProductName" sem a informação do "SKU Name".
+
+## Workaround
+
+
+Não temos nenhuma solução alternativa no momento.
+
+
+
+
+
diff --git a/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 16e6d409b..3ae5a632f 100644
--- a/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -3,8 +3,8 @@ title: 'Ao adicionar um SKU através de nossa funcionalidade "Change Order", o n
 id: 35Q3KoOSsUr9n9XEDIk7nk
 status: PUBLISHED
 createdAt: 2022-04-07T14:53:35.829Z
-updatedAt: 2022-11-25T22:02:48.606Z
-publishedAt: 2022-11-25T22:02:48.606Z
+updatedAt: 2024-02-16T20:24:27.100Z
+publishedAt: 2024-02-16T20:24:27.100Z
 firstPublishedAt: 2022-04-07T14:53:36.256Z
 contentType: knownIssue
 productTeam: Order Management
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Order Management
 slug: ao-adicionar-um-sku-atraves-de-nossa-funcionalidade-change-order-o-nome-do-produto-nao-e-exibido-no-pedido-e-na-notificacao-por-email
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 557978
 ---
 
diff --git a/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md b/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
index a4ffa4be9..b7bfe59a1 100644
--- a/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
+++ b/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
@@ -1,16 +1,16 @@
 ---
-title: 'Ao desativar um trabalhador de serviço nativo, não é possível usar um serviço personalizado'
+title: 'Ao desativar o service worker nativo, não é possível usar um personalizado'
 id: 1GpzVam1nuGbrKR4Izx6D9
 status: PUBLISHED
 createdAt: 2023-03-14T18:20:55.443Z
-updatedAt: 2023-03-14T18:20:55.953Z
-publishedAt: 2023-03-14T18:20:55.953Z
+updatedAt: 2024-02-02T21:00:43.540Z
+publishedAt: 2024-02-02T21:00:43.540Z
 firstPublishedAt: 2023-03-14T18:20:55.953Z
 contentType: knownIssue
 productTeam: Store Framework
 author: 2mXZkbi0oi061KicTExNjo
 tag: Store Framework
-slug: ao-desativar-um-trabalhador-de-servico-nativo-nao-e-possivel-usar-um-servico-personalizado
+slug: ao-desativar-o-service-worker-nativo-nao-e-possivel-usar-um-personalizado
 locale: pt
 kiStatus: Backlog
 internalReference: 770949
@@ -24,17 +24,14 @@ internalReference: 770949
 
 
 
-Para usar um prestador de serviços personalizados, você precisa desativar nosso prestador de serviços nativo, mas, ao fazê-lo, não estamos reconhecendo o prestador de serviços personalizados
-
-
-##
+Para usar um service worker personalizado, você precisa desativar nosso service worker nativo, mas, ao fazer isso, não estamos reconhecendo o service worker personalizado
 
 ## Simulação
 
 
 
-Desativar nosso trabalhador de serviço nativo
-Tente ligar um novo
+Desativar nosso service worker nativo
+Tente vincular um novo
 
 Referências:
 
@@ -45,12 +42,11 @@ https://developers.vtex.com/docs/guides/vtex-io-documentation-using-several-serv
 https://developers.vtex.com/docs/guides/vtex-io-documentation-deactivating-the-vtex-io-native-service-worker
 
 
-##
 
 ## Workaround
 
 
-Não há solução
+Não há solução alternativa
 
 
 
diff --git a/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index 9fdfd409e..046ed61d8 100644
--- a/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -3,8 +3,8 @@ title: 'Ao carregar a página "Mapeamento do Catálogo" em admin a mensagem inic
 id: 4WszmRZ5jpeSDNTEuFIdwF
 status: PUBLISHED
 createdAt: 2022-12-15T12:32:17.741Z
-updatedAt: 2022-12-15T12:32:18.420Z
-publishedAt: 2022-12-15T12:32:18.420Z
+updatedAt: 2024-02-16T20:23:22.033Z
+publishedAt: 2024-02-16T20:23:22.033Z
 firstPublishedAt: 2022-12-15T12:32:18.420Z
 contentType: knownIssue
 productTeam: Marketplace
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Marketplace
 slug: ao-carregar-a-pagina-mapeamento-do-catalogo-em-admin-a-mensagem-inicial-nao-e-traduzida
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 717066
 ---
 
diff --git a/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 1f461973e..624998deb 100644
--- a/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -3,8 +3,8 @@ title: 'Quando o acordo é enviado tão nulo e codificado como "reembolso-manual
 id: 2PdRRjHDODY2Tk0VItO4Fo
 status: PUBLISHED
 createdAt: 2022-07-11T17:37:43.961Z
-updatedAt: 2022-11-25T22:04:38.681Z
-publishedAt: 2022-11-25T22:04:38.681Z
+updatedAt: 2024-02-16T20:28:17.704Z
+publishedAt: 2024-02-16T20:28:17.704Z
 firstPublishedAt: 2022-07-11T17:37:44.954Z
 contentType: knownIssue
 productTeam: Payments
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Payments
 slug: quando-o-acordo-e-enviado-tao-nulo-e-codificado-como-reembolsomanual-nosso-gateway-realiza-um-duplo-reembolso
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 615050
 ---
 
diff --git a/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md b/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
index e63c7921f..2c53150ab 100644
--- a/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
+++ b/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
@@ -3,8 +3,8 @@ title: 'Quando o shippingEstimate é = 0, o cálculo de entregaSlaInMinutes reto
 id: UGk2WYb3w3ZWH4pL07TNg
 status: PUBLISHED
 createdAt: 2022-02-01T13:04:45.737Z
-updatedAt: 2022-11-25T21:51:01.802Z
-publishedAt: 2022-11-25T21:51:01.802Z
+updatedAt: 2024-02-16T20:24:38.902Z
+publishedAt: 2024-02-16T20:24:38.902Z
 firstPublishedAt: 2022-02-01T13:04:46.164Z
 contentType: knownIssue
 productTeam: Checkout
@@ -12,7 +12,7 @@ author: 2mXZkbi0oi061KicTExNjo
 tag: Checkout
 slug: quando-o-shippingestimate-e-0-o-calculo-de-entregaslainminutes-retorna-nulo
 locale: pt
-kiStatus: Backlog
+kiStatus: No Fix
 internalReference: 514835
 ---
 
diff --git a/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md b/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
new file mode 100644
index 000000000..2f9cab316
--- /dev/null
+++ b/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
@@ -0,0 +1,44 @@
+---
+title: 'Ao usar filtros horizontais, depois de escolher três deles, as opções do filtro não são mais recolhidas'
+id: 7xPLXjZMqwxQmWwJsd63eC
+status: PUBLISHED
+createdAt: 2023-07-11T12:30:50.198Z
+updatedAt: 2024-02-16T19:16:06.662Z
+publishedAt: 2024-02-16T19:16:06.662Z
+firstPublishedAt: 2023-07-11T12:30:50.962Z
+contentType: knownIssue
+productTeam: Store Framework
+author: 2mXZkbi0oi061KicTExNjo
+tag: Store Framework
+slug: ao-usar-filtros-horizontais-depois-de-escolher-tres-deles-as-opcoes-do-filtro-nao-sao-mais-recolhidas
+locale: pt
+kiStatus: Backlog
+internalReference: 859382
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Quando a loja estiver usando os filtros na opção horizontal, toda vez que você clicar em um filtro, suas opções serão recolhidas. Porém, quando você clica em um filtro pela terceira vez, o filtro não é mais recolhido. Ele travará.
+
+## Simulação
+
+
+
+- Encontre uma loja usando a opção de filtro horizontal
+- Escolha três filtros diferentes
+- No terceiro, ele travar
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md b/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
new file mode 100644
index 000000000..b9f151d8b
--- /dev/null
+++ b/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
@@ -0,0 +1,44 @@
+---
+title: 'SpotPrice incorreto para itens com UnitMultiplier maior que 1 nas APIs de pesquisa inteligente'
+id: 50Ufh8uqYt76Ddxrz0Id99
+status: PUBLISHED
+createdAt: 2023-11-11T00:26:08.800Z
+updatedAt: 2023-11-11T00:26:09.509Z
+publishedAt: 2023-11-11T00:26:09.509Z
+firstPublishedAt: 2023-11-11T00:26:09.509Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: spotprice-incorreto-para-itens-com-unitmultiplier-maior-que-1-nas-apis-de-pesquisa-inteligente
+locale: pt
+kiStatus: Backlog
+internalReference: 934687
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Nas APIs de pesquisa inteligente (GraphQL ou REST), a propriedade `spotPrice` do objeto `items.sellers.commertialOffer` está incorreta para itens em que o `unitMultiplier` é maior que `1`.
+
+O `spotPrice` deveria representar o método de pagamento mais barato em sua opção de parcela única para mostrar o "preço à vista", com um desconto (se houver), mas, nesse caso, ele acaba retornando o preço normal do item.
+
+Isso não acontece para itens em que o multiplicador é menor que `1` (itens fracionados).
+
+## Simulação
+
+
+Na API REST ou GraphQL do Intelligent Search, verifique a propriedade dos itens nesse cenário específico
+
+## Workaround
+
+
+O valor correto para `spotPrice` pode ser recuperado da matriz `Installments` dentro do mesmo objeto `commertialOffer`.
+
+
+
+
diff --git a/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md b/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md
new file mode 100644
index 000000000..c108c18aa
--- /dev/null
+++ b/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md
@@ -0,0 +1,50 @@
+---
+title: 'Tradução incorreta para campos diferentes com o mesmo valor original'
+id: 5amLWqGy7TPh7tk4KnLTmW
+status: PUBLISHED
+createdAt: 2024-02-16T00:05:00.562Z
+updatedAt: 2024-02-16T00:05:01.618Z
+publishedAt: 2024-02-16T00:05:01.618Z
+firstPublishedAt: 2024-02-16T00:05:01.618Z
+contentType: knownIssue
+productTeam: Intelligent Search
+author: 2mXZkbi0oi061KicTExNjo
+tag: Intelligent Search
+slug: traducao-incorreta-para-campos-diferentes-com-o-mesmo-valor-original
+locale: pt
+kiStatus: Backlog
+internalReference: 982848
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+O Intelligent Search pode usar a tradução errada para um campo cujo valor no idioma principal é o mesmo entre campos diferentes.
+
+## Simulação
+
+
+Considerando dois campos (categoria e especificação) de um produto em uma loja com "nl-BE" como idioma padrão e "fr-BE" como um idioma adicional com os seguintes valores:
+
+- categoria
+  - nl-BE = médio
+  - fr-BE = moyens
+- especificação
+  - nl-BE = médio
+  - fr-BE = midi
+
+Em uma incompatibilidade, a tradução "fr-BE" para o campo de especificação pode ser indexada erroneamente como "moyens" em vez de "midi
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md b/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
new file mode 100644
index 000000000..1a187a5e4
--- /dev/null
+++ b/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
@@ -0,0 +1,41 @@
+---
+title: 'Valor incorreto para preçoDefinição na ordem da cadeia para um mercado multinível'
+id: 75qEjhgv1tTQNho0MArnJo
+status: PUBLISHED
+createdAt: 2023-11-27T13:50:18.505Z
+updatedAt: 2023-11-27T13:51:42.434Z
+publishedAt: 2023-11-27T13:51:42.434Z
+firstPublishedAt: 2023-11-27T13:51:42.434Z
+contentType: knownIssue
+productTeam: Order Management
+author: 2mXZkbi0oi061KicTExNjo
+tag: Order Management
+slug: valor-incorreto-para-precodefinicao-na-ordem-da-cadeia-para-um-mercado-multinivel
+locale: pt
+kiStatus: Backlog
+internalReference: 663203
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A propriedade "priceDefinition" para pedidos no nível "chain" em um marketplace multinível não está seguindo o "sellingPrice" como esperado. Em vez disso, está seguindo a propriedade "price".
+
+## Simulação
+
+
+Crie um pedido com um desconto aplicado desde a camada do marketplace (nível 1), em relação à camada do vendedor (cadeia, nível 2), em um relacionamento multinível. A camada de atendimento (nível 3) apresentará os valores corretamente, mas a "cadeia" não
+
+## Workaround
+
+
+Evite usar a propriedade "priceDefinition" nesses tipos de pedidos e faça as contas usando as propriedades price, quantity, unitMultiplier e priceTag - para evitar problemas com o "sellingPrice", que não é um valor preciso.
+
+
+
+
+
diff --git a/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md b/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md
index c9313ec2f..14aa21db0 100644
--- a/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md
+++ b/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md
@@ -1,10 +1,10 @@
 ---
 title: ' XML - Símbolo de moeda em campo "Parcelamento"'
 id: 4s7hBA1MAUgeEC2Q4K8gKM
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-26T15:22:31.980Z
-updatedAt: 2022-12-22T20:48:49.927Z
-publishedAt: 2022-12-22T20:48:49.927Z
+updatedAt: 2024-02-02T20:08:19.240Z
+publishedAt: 
 firstPublishedAt: 2017-06-26T23:18:58.653Z
 contentType: knownIssue
 productTeam: Marketing & Merchandising
@@ -22,7 +22,8 @@ Ao configurar uma moeda em um XML, a mesma se aplica a todos os campos, exceto o
 
 O campo **Parcelamento** sempre mostra a moeda "R$", independentemente do fato de que a moeda configurada seja diferente.
 
-![Parcelamento](//files.slack.com/files-pri/T02BCPD0X-F5WHSHM5E/image.png)
+![Parcelamento](https://github.com/vtexdocs/devportal/assets/77292838/7a6323e9-da76-4645-a13a-fcd1202efe52)
+
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md b/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
new file mode 100644
index 000000000..b91264011
--- /dev/null
+++ b/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
@@ -0,0 +1,41 @@
+---
+title: 'Campo de categoria global XML que mostra as informações definidas no nível global da categoria.'
+id: 508Gdn8StafQKOa2Wyfr8u
+status: PUBLISHED
+createdAt: 2022-01-21T17:38:16.365Z
+updatedAt: 2024-02-16T20:30:04.149Z
+publishedAt: 2024-02-16T20:30:04.149Z
+firstPublishedAt: 2024-01-23T15:32:13.423Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: campo-de-categoria-global-xml-que-mostra-as-informacoes-definidas-no-nivel-global-da-categoria
+locale: pt
+kiStatus: No Fix
+internalReference: 282231
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Nos arquivos XML, o campo para Categoria Global está fornecendo as informações da Categoria Global definida no Nível da Categoria e não no Nível do Produto (o nível do produto deve ser priorizado).
+
+## Simulação
+
+
+- Use um produto com uma categoria global definida no produto e uma categoria global diferente definida no nível da categoria;
+- Crie um arquivo XML e use a categoria global arquivada;
+- Verifique o produto no XML mostrando a categoria global definida na categoria.
+
+
+
+## Workaround
+
+
+Não há solução alternativa.
+
diff --git a/docs/known-issues/pt/xml-installment-currency-does-not-apply.md b/docs/known-issues/pt/xml-installment-currency-does-not-apply.md
new file mode 100644
index 000000000..feaf748e3
--- /dev/null
+++ b/docs/known-issues/pt/xml-installment-currency-does-not-apply.md
@@ -0,0 +1,45 @@
+---
+title: 'XML - A moeda da prestação não se aplica'
+id: 7kPbxbGnpqeqU8XCD576hZ
+status: PUBLISHED
+createdAt: 2024-02-02T19:16:59.053Z
+updatedAt: 2024-07-01T18:49:23.913Z
+publishedAt: 2024-07-01T18:49:23.913Z
+firstPublishedAt: 2024-02-02T19:16:59.992Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: xml-a-moeda-da-prestacao-nao-se-aplica
+locale: pt
+kiStatus: No Fix
+internalReference: 976295
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao configurar uma moeda em um XML, ela se aplica a todos os campos, exceto ao campo "Parcela".
+
+O campo "Prestação" sempre exibe a moeda como "R$", independentemente da moeda configurada.
+
+## Simulação
+
+
+
+1. Crie/atualize um XML com uma moeda diferente de "R$" e ative o campo Parcela.
+2. Verifique se todos os campos de preço no XML estão retornando corretamente a moeda, exceto o campo Parcela
+
+## Workaround
+
+
+N/A
+
+
+
+
+
diff --git a/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md b/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
new file mode 100644
index 000000000..517e24b3f
--- /dev/null
+++ b/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
@@ -0,0 +1,49 @@
+---
+title: 'As tags XML <price> relacionadas não carregam o conteúdo de itens indisponíveis'
+id: 7u2WDGV9FJl4fXwfOhRx8N
+status: PUBLISHED
+createdAt: 2024-01-31T19:11:20.119Z
+updatedAt: 2024-01-31T19:11:20.846Z
+publishedAt: 2024-01-31T19:11:20.846Z
+firstPublishedAt: 2024-01-31T19:11:20.846Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: as-tags-xml-price-relacionadas-nao-carregam-o-conteudo-de-itens-indisponiveis
+locale: pt
+kiStatus: Backlog
+internalReference: 974722
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+A integração XML carrega qualquer tag relacionada ao preço, como minPrice, maxPrice, currentPrice, que são carregadas como uma tag de valor nulo (<![CDATA[]]>) quando o item não está disponível e também são definidas para serem exibidas se não estiverem disponíveis.
+
+## Simulação
+
+
+1 - Configure um SKU indisponível em sua loja para "mostrar mesmo se não estiver disponível".
+2 - Para uma configuração de integração XML válida https://myaccountname.myvtex.com/admin/Site/XmlForm.aspx, configure a tag "Availability" e qualquer tag de disponibilidade para serem exibidas.
+3 - Use uma solicitação GET ou carregue o URL XML criado em seu navegador.
+
+O resultado será um item indisponível, ainda exibido no XML, mas sem nenhuma tag de preço:
+
+ ![](https://vtexhelp.zendesk.com/attachments/token/1CzUarsM3O05aG9z5otDZZ1Yg/?name=image.png)
+
+
+
+## Workaround
+
+
+Não há solução alternativa. A única opção para não integrar itens sem preço é desativar a opção "showIfNotAvailable".
+
+
+
+
+
diff --git a/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
new file mode 100644
index 000000000..a35eada4b
--- /dev/null
+++ b/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
@@ -0,0 +1,47 @@
+---
+title: 'O sinalizador "Nome do produto" do XML não está funcionando corretamente'
+id: 6YDbpRns3LCN02bVKM8aaf
+status: PUBLISHED
+createdAt: 2023-10-26T11:35:14.500Z
+updatedAt: 2023-10-26T11:35:15.285Z
+publishedAt: 2023-10-26T11:35:15.285Z
+firstPublishedAt: 2023-10-26T11:35:15.285Z
+contentType: knownIssue
+productTeam: Catalog
+author: 2mXZkbi0oi061KicTExNjo
+tag: Catalog
+slug: o-sinalizador-nome-do-produto-do-xml-nao-esta-funcionando-corretamente
+locale: pt
+kiStatus: Backlog
+internalReference: 925965
+---
+
+## Sumário
+
+<div class="alert alert-info">
+  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
+</div>
+
+
+Ao criar um XML, temos duas opções diferentes para definir o nome do produto, nos sinalizadores "Nome do produto" e "Nome do produto + Nome do SKU". No entanto, o sinalizador "Nome do produto" está sendo desconsiderado, e o nome do produto no arquivo segue a regra:
+- Se o produto tiver mais de um SKU ou o nome do SKU for igual ao nome do produto = será exibido somente o Nome do produto
+- Se o produto tiver apenas um SKU e o nome do SKU não for igual ao nome do produto = ele concatenará o nome do produto e do SKU
+
+## Simulação
+
+
+
+1. Verifique se você tem no catálogo produtos que correspondam à descrição acima
+2. Crie um XML selecionando o sinalizador "Product Name" (Nome do produto)
+3. Veja que, para os produtos com apenas uma SKU, o nome do produto será concatenado com o nome da SKU
+
+
+
+## Workaround
+
+
+N/A
+
+
+
+
diff --git a/docs/known-issues/pt/xmls-returning-500-error.md b/docs/known-issues/pt/xmls-returning-500-error.md
index efd1f85c2..032aa2e31 100644
--- a/docs/known-issues/pt/xmls-returning-500-error.md
+++ b/docs/known-issues/pt/xmls-returning-500-error.md
@@ -1,16 +1,16 @@
 ---
-title: 'erro de retorno de 500 XMLs'
+title: 'XMLs que retornam erro 500'
 id: 6L48cBRaKQmjAOnNza3aNA
 status: PUBLISHED
 createdAt: 2022-06-07T17:53:45.884Z
-updatedAt: 2022-11-25T22:10:40.212Z
-publishedAt: 2022-11-25T22:10:40.212Z
+updatedAt: 2024-05-23T18:54:18.843Z
+publishedAt: 2024-05-23T18:54:18.843Z
 firstPublishedAt: 2022-06-07T17:53:46.260Z
 contentType: knownIssue
 productTeam: Portal
 author: 2mXZkbi0oi061KicTExNjo
 tag: Portal
-slug: erro-de-retorno-de-500-xmls
+slug: xmls-que-retornam-erro-500
 locale: pt
 kiStatus: Backlog
 internalReference: 268042
@@ -23,14 +23,14 @@ internalReference: 268042
 </div>
 
 
-Eventualmente, o XML pode retornar um erro de 500, ele acontece principalmente em grandes arquivos XML.
-
+Eventualmente, o XML pode retornar um erro 500, o que acontece principalmente em arquivos XML grandes.
 
 
 ## Simulação
 
 
-Tente carregar um grande arquivo XML.
+Tente carregar um arquivo XML grande.
+
 
 
 
@@ -38,6 +38,10 @@ Tente carregar um grande arquivo XML.
 
 
 
-- Tente recarregar o XML geralmente resolve o problema;
+- Tentar recarregar o XML geralmente resolve o problema;
 - Use mais de um XML.
 
+
+
+
+
diff --git a/docs/tracks/en/.md b/docs/tracks/en/.md
index c0d84daa7..a1d24716f 100644
--- a/docs/tracks/en/.md
+++ b/docs/tracks/en/.md
@@ -1,9 +1,9 @@
 ---
 title: ''
-id: 3yqE1WNTOw4esgsEkEN50y
+id: dIgD5BkK1y7PCzJCIKXwv
 status: DRAFT
-createdAt: 2019-05-26T19:17:31.081Z
-updatedAt: 2020-02-13T19:05:58.442Z
+createdAt: 2019-05-26T19:23:24.682Z
+updatedAt: 2020-02-13T19:05:57.916Z
 publishedAt: 
 firstPublishedAt: 
 contentType: trackArticle
@@ -15,3 +15,4 @@ trackSlugEN:
 ---
 
 
+
diff --git a/docs/tracks/en/access-to-the-customers-last-cart.md b/docs/tracks/en/access-to-the-customers-last-cart.md
index a59017cd5..32adfbf35 100644
--- a/docs/tracks/en/access-to-the-customers-last-cart.md
+++ b/docs/tracks/en/access-to-the-customers-last-cart.md
@@ -20,4 +20,4 @@ When having access to this information, the sales associate can try to complete
 
 They just need to click `Access` to see the products in the abandoned cart.
 
-![last-cart-en](https://images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/fcddb8f976cb0a98d0bb459497b9ef59/last-cart-EN.png)
+![last-cart-en](//images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/fcddb8f976cb0a98d0bb459497b9ef59/last-cart-EN.png)
diff --git a/docs/tracks/en/accounts-and-architecture.md b/docs/tracks/en/accounts-and-architecture.md
new file mode 100644
index 000000000..bfaafd214
--- /dev/null
+++ b/docs/tracks/en/accounts-and-architecture.md
@@ -0,0 +1,125 @@
+---
+title: 'Accounts and architecture'
+id: 4yPqZQyj0t675QpcG7H6yl
+status: PUBLISHED
+createdAt: 2024-01-09T00:00:08.724Z
+updatedAt: 2024-02-22T17:18:14.922Z
+publishedAt: 2024-02-22T17:18:14.922Z
+firstPublishedAt: 2024-02-22T14:06:20.581Z
+contentType: trackArticle
+productTeam: Others
+slug: accounts-and-architecture
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+VTEX provides many features and products, but their availability can vary depending on the [account type](#vtex-account-types), as each one is designed for certain scenarios. Before you start planning your [store's architecture](#store-architecture) and defining [implementation partners](#implementation-partners), you need to know the main characteristics of the accounts.
+
+## VTEX account types
+
+The definition of a VTEX store's architecture depends on the VTEX account type, as some features are exclusive to certain account types, and each account is tailored to particular business models. The best account will be the one that best reflects the business model's structure.
+
+VTEX account types are:
+
+- **Main account (or standard):** The VTEX core account includes all the native settings and allows setting up a store website and requesting all platform features.
+- [Franchise account](https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl): The franchise account is associated with a main account. It does not have its own website, and its most remarkable characteristic is that it does not configure its own catalog, which comes from the main account. This account type is recommended for operations with physical stores, franchisees, and brand representatives, but the store does not necessarily need to have a franchise network to benefit from the advantages of a VTEX franchise account.
+- [Seller Portal account](https://help.vtex.com/en/tutorial/seller-criar-conta-no-seller-portal--3gn2Q5rMhgu0jjX7AiiHcs): This account is associated with a main account. It does not have its own website, and its main characteristic is to make the store a marketplace for [white label sellers](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) or sellers outside the VTEX ecosystem who can quickly integrate their catalog in the VTEX marketplace. In other words, it is a VTEX platform edition designed for the main account's sellers.
+
+The following image is an overview to help you [choose between standard, franchise, or Seller Portal accounts](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78):
+
+![main_account_franchise_seller_portal_EN](//images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/b8f887b2f84c72b3c20a38a020f9c53f/main_account_franchise_seller_portal_EN.png)
+
+## Account characteristics
+
+[Choosing between a standard, franchise, or Seller Portal account](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78) involves many factors. The table below shows the main characteristics of each to help guide your decision:  
+
+| **Account type** | **Main characteristics** |
+| :---: | :--- |
+| Main account (or standard) | <ul><li>Has its own frontend and website.</li><li>Can be multistore and have multiple sites and stores, each with its own trade policy.</li><li>Has its own VTEX Admin environment to manage its operation.</li><li>Allows you to have franchise and Seller Portal accounts and request new environments.</li><li>Allows you to natively become a <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller">VTEX seller</a> and a <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplace</a> and connect with all the stores within the VTEXecosystem.</li><li>Allows configuring <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label sellers</a> in franchise accounts.</li><li>Offers the ability to sell your franchise accounts' inventory in other VTEX marketplaces using the <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a> feature.</li><li>Can integrate with <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">external sellers</a> and <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-guide">external marketplaces.</a></li><li>Allows you to request add-on products.</li></ul> |
+| Franchise account | <ul><li>Does not have its own frontend or website.</li><li>Has its own VTEX Admin environment to manage its operation.</li><li>Does not have its own catalog; instead, it follows the exact catalog structure of the main account.</li><li>Allows configuring prices and promotions.</li><li>Has its own warehouse and inventory.</li><li>The franchise account inventory can be sold on other VTEX marketplaces connected to the main account via <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI).</a></li></ul> |
+| Seller Portal account | <ul><li>Does not have its own frontend or website.</li><li>The main account has an area for <a href="https://help.vtex.com/en/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv"> managing sellers</a>, and each seller has its environment in the Seller Portal Admin.</li><li>The seller can configure inventory and pricing, manage products shared with the marketplace, invoice orders, activate promotions, process payments, and have their own logistics.</li></ul> |
+
+<div class="alert alert-info">
+<p><b>Marketplace on VTEX</p></b><p>Besides offering great flexibility in store architecture, our ecosystem allows each store to have multiple <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">marketplace strategies</a>, such as:</p><ul><li>Becoming a seller or marketplace for other VTEXstores.</li><li>Integrating with the big players such as <a href="https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> and <a href="https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP">Amazon</a>.</li>
+<li>Integrating with <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-marketplaces-partners">partner marketplaces</a> certified by VTEX.</li>
+<li>Being a marketplace for sellers with a <a href="https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK">Seller Portal</a> account.</li>
+<li>Being a <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a>.</li><li>Creating your own integrations with <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">external marketplaces and external sellers.</a></li></ul>
+</div>
+
+## Store architecture
+
+The VTEX platform provides many business models and sizes with all the features and settings they need for your operations. For instance, a store can adopt a different strategy for each sales channel through [trade policies](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz#trade-policy) by configuring different catalog, price, and logistics settings for each one. To do so, the only requirement is to [request new trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X).
+
+However, using many trade policies simultaneously can compromise the store's performance and slow it down, as changes need to be updated across multiple trade policies. Therefore, depending on the business model and complexity of the operation, you can segment using the following options:
+
+- [Multistores](#multistore)  
+- [Additional environments](#additional-environment) 
+
+The image below is an example of how the main account, environment (sub-account), multi-store (stores), and trade policies are related:
+
+![multistore_aditional_environment_EN](//images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/4bf1e15428b5db24e4658c446eb5e2cf/multistore_aditional_environment_EN.png)
+
+### Multistore
+
+[Multistore, or multidomain](https://help.vtex.com/en/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL), is the feature that allows you to create other stores associated with the main account, all managed in the same admin environment. Each store will have its own [storefront](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) and domain, but they can share module settings, such as catalog, logistics, prices, and others.
+
+The main advantages of [creating multistores](https://help.vtex.com/en/tutorial/como-criar-multiloja-multidominio--tutorials_510) include the ease with which the company can sell different niche products, the convenience of selling multiple brands, and the agility of making different products available in different stores and channels.
+
+The following scenarios illustrate the strategic role of having multiple stores in the same environment:
+
+- **National and international stores:** One store is focused on the country of origin, and the other on the international market.
+- **Niche segmentation:** Companies with a broad niche, operating different stores, each segmented to offer a variety of products focused on distinct audiences.
+- **Different operations:** When a business operates both B2C and B2B models, for example, it can be strategic to have separate stores for each type of operation, but sharing settings and information, allowing unified management.
+
+In addition to combining trade policies and multistores, at VTEX, you can request a new environment, as described below.
+
+### Additional environment
+
+A standard VTEX account can completely separate the management space for your operations by [requesting a new environment.](https://help.vtex.com/en/tutorial/contratar-novo-ambiente--tutorials_2542) Each VTEX Admin will be associated with its own account and independently manage the storefront settings and platform modules.
+
+Some typical use cases for requesting a new environment are when you want an [environment exclusively for testing](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH#4-testing-before-the-go-live) (Quality Assurance - QA) or an environment dedicated to managing another operation, such as B2C, B2B, or B2E.
+
+## Choosing between multistore and additional environment
+
+The table below highlights important aspects to consider when deciding whether to have a multistore architecture, an additional environment, or a combination of both:  
+
+| **Characteristic** | **Multistore (stores)** | **Additional environment (subaccounts)**|
+| :---: | :--- | :--- |
+| Architecture | A **single admin environment** in the VTEXAdmin associated with two or more stores ([store names](https://help.vtex.com/en/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)). All stores are linked to the **same [account name](https://help.vtex.com/en/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC)**. | **Multiple admin environments** in the VTEX Admin with fully independent settings. Each environment has its own **[account name](https://help.vtex.com/en/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC)**. |
+| Sitemap | Has a single main account **[sitemap](https://help.vtex.com/en/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) shared** among all stores. | Each account has its own **[sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575)**. |
+| Sales segmentation | Stores can **segment shopping experiences using trade policies**. This also helps ensure store performance, as you don't need multiple active trade policies. | The possibilities for sales segmentation and customization are huge, as each environment can **combine different trade policies and multistores**. |
+| Team | A **single team manages the operation** or, despite different teams, the similarities in settings across stores make it more efficient for them to share catalog, logistics, and pricing settings, for example. All users are **managed by the same [License Manager](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager)**. | **Different teams** within the same company have different operational responsibilities. **Each environment has its License Manager**, so [users](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) in each of them are managed separately. |
+| Costs | **There is no cost** for creating new stores, but there is a cost for creating different storefronts, as you need to [request an additional trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X). | **There is a cost** to [request an additional environment](https://help.vtex.com/en/tutorial/contratar-novo-ambiente--tutorials_2542?&utm_source=autocomplete), but this already includes a trade policy.|  
+
+For more information, read the [Choosing between a multistore architecture or an additional environment](https://help.vtex.com/en/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL) article.
+
+## Architecture questionnaire
+
+To help you decide which products and settings to consider when planning your store's architecture, we've created the following table of questions:  
+
+| **Topic** | **Questions** |
+| :---: | :--- |
+| Mapping existing architecture | - Are there any [external integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) to consider? For example: <br><br>- Enterprise Resource Planning (ERP) <br><br>- Customer Relationship Management (CRM) <br><br>- Transportation Management System (TMS) <br><br>- Warehouse Management System (WMS) <br><br>- Business Intelligence (BI) <br><br>- Will external integrations connect directly to the platform via [VTEX APIs](https://developers.vtex.com/docs/api-reference)? <br><br>- Will I need to request a [back office integration](https://developers.vtex.com/docs/guides/erp-integration-guide) partner? |
+| How to set up a store | - Will the implementation be done using APIs from the [VTEX API Reference](https://developers.vtex.com/docs/api-reference)? <br><br>- Will the implementation be done via the VTEX Admin? <br><br>- Is it a headless commerce model that will use frontend technologies in the headless scenario? |
+| [Backend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) and [frontend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) general structure | - Will I need a [partner](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) to implement the store's [backend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu)? <br><br>- Will I need a partner to implement the [storefront](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)? <br><br>- Is the store frontend created with any of the [VTEX technologies](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#frontend-development-technologies-on-vtex)? ([Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) and [FastStore](https://vtex.com/br-pt/resources/faststore-acelerando-a-cultura-composable-commerce-de-desenvolvimento-headless-avanti/)) <br><br>- Will the Content Management System (CMS) [storefront](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC) in the VTEX Admin be used for store operations? <br><br>- Could the [VTEX authentication methods](https://developers.vtex.com/docs/guides/authentication) generate any friction when integrating with the VTEX platform? |
+| VTEX overall structure | - Will I need [franchise accounts](https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl)? <br><br>- Should I have [white label sellers](https://help.vtex.com/em/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa)? <br><br>- Is it worth leveraging [Multilevel Omnichannel Inventory (MOI)](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4)? <br><br>- Will I need [Seller Portal](https://help.vtex.com/en/tutorial/seller-criar-conta-no-seller-portal--3gn2Q5rMhgu0jjX7AiiHcs) accounts? <br><br>- Will I need to request an [additional environment](https://help.vtex.com/en/tutorial/contratar-novo-ambiente--tutorials_2542)? <br><br>- Does the operation involve a [multistore/multidomain](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#store-architecture)? <br><br>- Is it worth requesting an [additional trade policy](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#requesting-an-additional-trade-policy)? <br><br>- Is it advisable to have a native solution to integrate with [VTEX sellers](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller) and [VTEX marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace)? <br><br>- Is it advisable to integrate with [external sellers](https://developers.vtex.com/docs/guides/external-seller-integration-guide) and [external marketplaces](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide)? <br><br>- What [performance optimization](https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance) issues should be considered in a [Store Framework development](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework)? <br><br>- What internationalization issues should be considered in a Store Framework development? <br><br>- The operation is cross-border and needs to [manage content using bindings](https://help.vtex.com/en/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) to customize the store's layout based on the users' location. |
+| Industry | - What is the operation's industry? <br><br>- Is it [fashion-related](https://vtex.com/br-pt/moda-e-vestuario/) (clothes and apparel)? <br><br>- Is it [grocery-related](https://vtex.com/br-pt/supermercado/)? |
+| Use cases | - Does the business model involve [B2C](https://vtex.com/br-pt/digital-commerce/) or [B2B](https://help.vtex.com/pt/tutorial/setting-up-b2b-on-vtex--tutorials_238)? <br><br>- Do I need an [omnichannel solution](https://vtex.com/br-pt/omnichannel/)? |
+| [Catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog) | - How will the [catalog architecture](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) be structured? <br><br>- Will the [catalog configuration](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#catalog-architecture) be done via back office integration? <br><br>- Will [product import](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#importing-products) be done via back office integration? <br><br>- Should we [internationalize the catalog](https://developers.vtex.com/docs/guides/catalog-internationalization)? |
+| [Store search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) | - Do I need to install and configure [VTEX Intelligent Search](https://developers.vtex.com/docs/apps/vtex.search) so customers can have an intelligent search and autocomplete function on the store's website? <br><br>- Does the operation work in multiple countries, and does it need to provide customers with [search experiences in multiple languages](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO)? <br><br>- Do you want the search results to sort the products according to a [specific merchandising rule](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW)? <br><br>- Is it advisable to set up Region to have [seller regionalization](https://help.vtex.com/pt/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw)? |
+| [Pricing](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices) and [Promotions](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promotions) | - Considering the VTEX [pricing system architecture](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx), what types of prices should be added? <br><br>- Will product pricing be configured via [back office integration](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#prices)? <br><br>- Does the sales strategy use [price tables](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8)? <br><br>- Do you expect to [create promotions](https://help.vtex.com/pt/tutorial/lista-de-promocoes-beta--4yB7nNdliiFxBTXE19GCIi)? |
+| [Payments](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments) | - Which gateway or set of gateways will be contacted to [add gateway affiliations to the platform](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444)? <br><br>- What [payment settings](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) (credit, cash, etc.) will be required for the [payment conditions](https://help.vtex.com/en/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) offered to customers at checkout? <br><br>- Is it advisable to set up [split payments](https://help.vtex.com/en/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) for sellers and marketplaces? |
+| [Logistics and fulfillment](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistics) | - How will the [shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) be structured? <br><br>- Which [loading docks](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) will be used? <br><br>- Which [warehouses](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) will be used? <br><br>- Which [shipping policies](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) will be used? <br><br>- Which [carriers](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) will be on the [shipping rate templates](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127) configured in the shipping policies? <br><br>- Will I need to set up [pickup points](https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) so customers can pick up orders from physical stores or distribution centers? <br><br>- In [inventory management](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139), is it advisable to use [lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) (an optional shipping time setting at SKU level)? <br><br>- Will [inventory import](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#inventory) be done via back office integration? <br><br>- Is it desirable to activate the [VTEX Shipping Network Correios](https://help.vtex.com/en/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) for the operation to be integrated through the VTEX Admin with the Correios PAC and SEDEX services? (For Brazil only) <br><br>- Does the operation involve international stores and [cross-border](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs) sales? |
+| [Orders](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#orders) | - Is it advisable to set up a [Feed or Hook](https://developers.vtex.com/docs/guides/orders-feed) to track changes in [order status](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196)? <br><br>- Will I need a [back office integration](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-integration) to send order information from VTEX to external systems such as ERP or WMS, or to send order information from external systems to VTEX? |
+| [Checkout](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout) | - Is the store going to use [VTEX Checkout](https://help.vtex.com/en/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) or a third-party solution? <br><br>- Is it advisable to [configure SKU pricing and availability by region](https://help.vtex.com/en/tutorial/setting-up-price-and-availability-of-skus-by-region--12ne58BmvYsYuGsimmugoc) so that the customer, in their shopping experience, sees the available store items that can be delivered to their location? |
+
+## Implementation partners
+
+When building a store, it is common for agencies and [implementation partners](https://vtex.com/us-en/partners/) (System Integration partners) to be involved. VTEX is associated with a wide ecosystem of partners known for their excellence and reliability in developing VTEX store projects. Provided the [user](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) has permission to access the store's VTEX Admin, they can view the partner list on the [Partner Portal](https://partnerportal.vtex.com/) (available only in Portuguese).
+
+The [VTEX Quadrant](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) is a program in which VTEX internally evaluates the performance and successful results of its partners' operations. This annual acknowledgment and reward is for those with the highest commitment and excellence. See the results of the 2022 Quadrant [here](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/). The VTEX Quadrant is an exclusive program for implementation partners in Brazil.
+
+<div class="alert alert-info">
+The <a href="https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/">VTEX Quadrant</a> is an exclusive program for implementation partners in Brazil.
+</div>
diff --git a/docs/tracks/en/add-on-products.md b/docs/tracks/en/add-on-products.md
new file mode 100644
index 000000000..964838bba
--- /dev/null
+++ b/docs/tracks/en/add-on-products.md
@@ -0,0 +1,134 @@
+---
+title: 'Add-on products'
+id: 1t2QBZvrOBSLgvHaAV9fYm
+status: PUBLISHED
+createdAt: 2024-02-20T20:29:42.983Z
+updatedAt: 2024-07-03T11:38:12.320Z
+publishedAt: 2024-07-03T11:38:12.320Z
+firstPublishedAt: 2024-02-22T14:09:28.506Z
+contentType: trackArticle
+productTeam: Others
+slug: add-on-products
+locale: en
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugEN: next-steps-after-the-go-live
+---
+
+Add-on products are solutions offered by VTEX to meet the specific business needs. They can be purchased separately through a subscription agreement.
+
+<div class="alert alert-warning">
+  <p>To implement the solutions below, contact our<a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ"> VTEX Sales Support</a>.</p>
+</div>
+
+## VTEX Ad Network
+
+[VTEX Ad Network](https://help.vtex.com/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) connects VTEX stores with brands interested in advertising their products. This connection allows advertisers and merchants to boost their business:
+
+- **Advertisers:** Brands that can create ad campaigns to promote products in VTEX stores offering the same products in their catalogs, thus increasing sales.
+- **Merchants:** Can offer ad space in their stores for advertisers to promote products. In return, these merchants will receive a fee for each click on an ad in their stores.
+
+![vtex_ad_network_sponsored_EN](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/1abdea32c119ed4890e414ad7dbc8fea/vtex_ad_network_sponsored.png)
+
+## VTEX Assisted Sales
+
+[Assisted Sales (SuiteShare)](https://help.vtex.com/en/tracks/suiteshare--khP0p8mjIYRIpvM7Cb4Zr/onWmyS8j4Thhde67UBBsB) is the solution created by VTEX to boost sales through WhatsApp. It allows you to attract new customers, integrate sales tools, and manage user service data and result metrics.
+
+![suitshare-en](//images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/bb4f1b69fe157f9b529e108898a924ca/next_steps_image11_ONLYPT.JPG)
+
+## VTEX Live Shopping
+VTEX Live Shopping allows creating online broadcasts for live demos of store product features. Direct and instantaneous interactions with customers improve public engagement with the brand and help increase sales performance.
+
+![live-shopping-en](//images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/3f7ee6f650ddb4497166ca049f8a62e5/next_steps_image5_ALL.JPG)
+
+To schedule an app demo with an expert, go to the [VTEX Live Shopping](https://vtex.com/us-en/live-shopping/#contact) page.
+
+## VTEX Personal Shopper
+
+VTEX Personal Shopper allows offering a direct, personalized service between the customer and the sales associate, bringing the physical store shopping experience to the digital environment. The sales associate can show products, make recommendations, and answer customers' questions through this app. They can also add items to the shopping cart during a video call.
+
+![personal-shopper-en](//images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/529260928af943b74c4e8ff30fc61022/next_steps_image6_ALL.JPG)
+
+To schedule an app demo with an expert, go to the [VTEX Personal Shopper](https://vtex.com/us-en/vtex-personal-shopper/#contact) page.
+
+## VTEX Pick and Pack
+
+VTEX Pick and Pack is a solution for managing and ensuring complete visibility throughout the fulfillment process, from picking and packing products in physical stores or warehouses to their delivery at pickup points or customer locations.
+
+**VTEX Pick and Pack** consists of: 
+
+- [Pick and Pack app](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA): Manages orders in the store or warehouse, allowing you to customize the order picking method, select packaging types per product, and remove or add products according to the store's inventory.
+
+- [Last Mile app](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): Coordinates the shipping of packages from warehouses or stores to the customer's address by creating efficient delivery routes, selecting available drivers, and tracking the exact location of the order.
+
+![pick-and-pack-en](//images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/6031e1df55ab9664ca2bf5a32ee32f62/next_steps_image7_ALL.JPG)
+
+To watch an app demo or schedule a custom service with an expert, go to the[ VTEX Pick and Pack](https://content.vtex.com/en/pick-and-pack/) page. 
+
+## VTEX Sales App
+
+With [VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), sales associates from physical stores can expand their sales possibilities by integrating inventory data between physical and online stores while offering complete face-to-face monitoring of the customer's purchasing process. The app allows you to:
+
+ - Access information and sell products from your store and different locations, such as branch stores, partner stores, or distribution centers ([endless aisle](https://help.vtex.com/en/tracks/unified-commerce-strategies--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn)).
+ - Suggest products based on the customer profile.
+
+- Offer instant delivery options, scheduled pickup, or delivery at the customer's location.
+
+- Manage performance metrics for each sales associate.
+
+ ![sales-app-en](//images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/c573fe37979371d79899d3fe4761f0a5/next_steps_image8_ALL.JPG)
+
+To watch an app demo or schedule a custom service with an expert, go to the[ VTEX Sales App](https://assets.vtex.com/sales-app/) page.
+
+## VTEX Shipping Network
+
+<div class="alert alert-warning">
+  <p>VTEX Shipping Network and VTEX Shipping Network Correios solutions are exclusive to Brazil.</p>
+</div>
+
+Explore options for shipping products to all regions of Brazil with [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) and **VTEX Shipping Network Correios**.
+
+**VTEX Shipping Network** offers the option of connecting carriers to create an integrated delivery network. With currently over 20 partners, it provides customers with the best cost and delivery time options.
+
+![shipping-network-en](//images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/e962d9f6b9b97df93f8a536e3b48b96d/image7.png)
+
+Learn more on the [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) page.
+
+## VTEX Shipping Network Correios
+
+[VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) is a partnership between VTEX and Correios, the primary postal service in Brazil. This solution allows stores to use PAC and SEDEX shipping services directly through the VTEX Admin with special rates, thereby reducing operational shipping costs.
+
+![image6](//images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/7e85c1b51be49ce02b06036276fd3a0d/image6.png)
+
+Requesting this solution is simple and can be done in a few minutes. To do so, accept the Terms and Conditions and [enable](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) the solution in the store's Admin. These are the features available in the VTEX Shipping Network Correios:
+
+- Synchronization of shipping tables between Correios and VTEX. Every update made by Correios is automatically displayed in the VTEX environment.
+- Shipping tracking automatically updated and added to orders.
+- Shipping labels available to be printed via the VTEX Admin ([Ready to Dispatch](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) module) or via [API](https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration) for integration with external systems (e.g., ERP, WMS).
+- Direct communication channel with Correios in the Admin through the [Information request](https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq#solicitar-informacoes-do-pedido-aos-correios).
+
+Learn more on the [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/) page.
+
+## VTEX Shield
+
+[VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) offers additional, customizable protection layers for stores that prioritize platform resilience and the security standards guaranteed by VTEX's existing security [certifications and practices](https://vtex.com/br-pt/security/security-practices/).
+
+When requesting VTEX Shield, you can choose from the following features:
+
+* [Security Monitor](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#security-monitor)
+* [Penetration tests](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#penetration-tests)
+* [Web Application Firewall (WAF)](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#web-application-firewall-waf)
+
+## VTEX WhatsApp AI Campaigns
+[WhatsApp AI Campaigns](https://help.vtex.com/en/tutorial/recupere-checkouts-abandonados-com-whatsapp-ai-campaigns--20i0zLQHt72LKzVEmk1CRZ?&utm_source=autocomplete) is a feature developed by VTEX to recover abandoned checkouts.
+
+When a user leaves the payment page, the platform identifies this action. If the user does not return to complete the order within 1 hour, the feature sends them a notification via WhatsApp.
+
+The main advantages of this feature are:
+
+- **Improved customer experience:** Messages can be personalized to increase relevance and strengthen the relationship with the brand.
+
+- **Increased conversion rates and sales:** The feature encourages customers to return to the payment page to complete their purchase, thereby increasing sales and conversion rates for retailers.
+
+<div class = "alert alert-info">
+WhatsApp AI Campaigns is only available for stores using <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> that don't have Checkout customizations.
+</div>
diff --git a/docs/tracks/en/add-pickup-points.md b/docs/tracks/en/add-pickup-points.md
index 2c9190b17..e5123df4b 100644
--- a/docs/tracks/en/add-pickup-points.md
+++ b/docs/tracks/en/add-pickup-points.md
@@ -32,7 +32,7 @@ Follow the step-by-step below to add a pickup point in your store:
 
 
 
-![EN Cadastrar Pontos de Retirada GIF](https://images.ctfassets.net/alneenqid6w5/2vf3pXYddrDf1sybyoTon/efa6e8bc465fb5188c06b1d2deaa2eef/EN_Cadastrar_Pontos_de_Retirada_GIF.gif)
+![EN Cadastrar Pontos de Retirada GIF](//images.ctfassets.net/alneenqid6w5/2vf3pXYddrDf1sybyoTon/efa6e8bc465fb5188c06b1d2deaa2eef/EN_Cadastrar_Pontos_de_Retirada_GIF.gif)
 
 
 
diff --git a/docs/tracks/en/add-sku-specifications.md b/docs/tracks/en/add-sku-specifications.md
index 971666048..0951bba06 100644
--- a/docs/tracks/en/add-sku-specifications.md
+++ b/docs/tracks/en/add-sku-specifications.md
@@ -34,7 +34,7 @@ To add the specifications, your store already needs to have departments, categor
 7. Fill out the specification form fields. In the case of SKUs, the mandatory fields flag is selected by default. For more info on each field, access our article on [how to fill out SKU specification fields](https://help.vtex.com/en/tutorial/creating-sku-fields--tutorials_119) 
 8. Click on **Save**
 
-![EN.1novo](https://images.ctfassets.net/alneenqid6w5/1UNDWQPmeRtLkc1VKqctAF/4e5526d5496d6f0b0fd0c1cc97d4bb05/EN.1novo.gif)
+![EN.1novo](//images.ctfassets.net/alneenqid6w5/1UNDWQPmeRtLkc1VKqctAF/4e5526d5496d6f0b0fd0c1cc97d4bb05/EN.1novo.gif)
 
 The following steps will let you add SKU specification values:
 
@@ -48,7 +48,7 @@ The following steps will let you add SKU specification values:
 8. Click on **New Value**
 9. Type in the **Name** of the desired value and click on **Save**
 
-![EN.2novo](https://images.ctfassets.net/alneenqid6w5/2vwsLaRQy4JXIDCIreLhHg/db0b782d93a8ca16734a59105f9d264a/EN.2novo.gif)
+![EN.2novo](//images.ctfassets.net/alneenqid6w5/2vwsLaRQy4JXIDCIreLhHg/db0b782d93a8ca16734a59105f9d264a/EN.2novo.gif)
 
 ### Link specifications to a SKU
 
@@ -63,7 +63,7 @@ To include specifications to a **SKU**, complete the following steps:
 6. Select the **Specifications** tab and choose the specification value for this SKU
 7. Click on **Save**
 
-![EN.3novo](https://images.ctfassets.net/alneenqid6w5/5IitjVxPxsC0gRmx8Gclpr/7a07cbc2c58f06e8379bc4c1771cbea6/EN.3novo.gif)
+![EN.3novo](//images.ctfassets.net/alneenqid6w5/5IitjVxPxsC0gRmx8Gclpr/7a07cbc2c58f06e8379bc4c1771cbea6/EN.3novo.gif)
 
 ## Spreadsheet
 
@@ -92,7 +92,7 @@ After filling in the spreadsheet data, follow the instructions below to import y
 5. Click on **Select** to choose the filled out spreadsheet
 6. Click on **Import**
 
-![EN.4](https://images.ctfassets.net/alneenqid6w5/3hx1Cvscz5vuvSv05NRl4E/d2dd8151c493ee8d6765aa2ad1374c89/EN.4.gif)
+![EN.4](//images.ctfassets.net/alneenqid6w5/3hx1Cvscz5vuvSv05NRl4E/d2dd8151c493ee8d6765aa2ad1374c89/EN.4.gif)
 
 ## API 
 
diff --git a/docs/tracks/en/adding-a-fixed-price.md b/docs/tracks/en/adding-a-fixed-price.md
index 5e26a4ac6..7eeda3487 100644
--- a/docs/tracks/en/adding-a-fixed-price.md
+++ b/docs/tracks/en/adding-a-fixed-price.md
@@ -1,10 +1,10 @@
 ---
 title: 'Adding a fixed price'
 id: 3g39iXkQza4AW7C7L814mj
-status: CHANGED
+status: PUBLISHED
 createdAt: 2019-07-04T13:53:38.630Z
-updatedAt: 2023-03-29T21:16:34.391Z
-publishedAt: 2023-03-29T18:18:57.294Z
+updatedAt: 2024-05-15T16:01:59.100Z
+publishedAt: 2024-05-15T16:01:59.100Z
 firstPublishedAt: 2019-07-17T19:46:38.452Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -56,7 +56,7 @@ To delete an existing fixed price, follow the steps below.
 
 ## Pricing API
 
-To create a fixed price via API, use the [Create or update price or fixed price](https://developers.vtex.com/vtex-rest-api/reference/prices-and-fixed-prices#createupdatepriceorfixedprice) endpoint of the Pricing API.
+To create a fixed price via API, use the [Create or update price or fixed price](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-) endpoint of the Pricing API.
 
 ### Learn more
 
diff --git a/docs/tracks/en/adding-a-loading-dock.md b/docs/tracks/en/adding-a-loading-dock.md
index 7602ad8c0..ea45435fa 100644
--- a/docs/tracks/en/adding-a-loading-dock.md
+++ b/docs/tracks/en/adding-a-loading-dock.md
@@ -29,7 +29,7 @@ Follow the steps below to add a loading dock to your store:
 4. Fill out the data entry fields. For more details on each field's meaning, refer to section [data entry fields](#data-entry-fields) below.;
 5. **Save** changes.
 
-![EN Cadastrar Doca GIF](https://images.ctfassets.net/alneenqid6w5/5RGUQFBMdcOPn3xV49SSqW/202dce17e72e2fb8da79961326626f03/EN_Cadastrar_Doca_GIF.gif)
+![EN Cadastrar Doca GIF](//images.ctfassets.net/alneenqid6w5/5RGUQFBMdcOPn3xV49SSqW/202dce17e72e2fb8da79961326626f03/EN_Cadastrar_Doca_GIF.gif)
 
 ### Data entry fields
 
diff --git a/docs/tracks/en/adding-a-price-rule.md b/docs/tracks/en/adding-a-price-rule.md
index 489632d2e..da3ccaf37 100644
--- a/docs/tracks/en/adding-a-price-rule.md
+++ b/docs/tracks/en/adding-a-price-rule.md
@@ -3,8 +3,8 @@ title: 'Adding a price rule'
 id: 7fyZaYe1IGzL0qVC28tOBO
 status: PUBLISHED
 createdAt: 2019-07-04T13:53:15.461Z
-updatedAt: 2023-03-29T18:50:59.023Z
-publishedAt: 2023-03-29T18:50:59.023Z
+updatedAt: 2023-08-21T17:10:07.115Z
+publishedAt: 2023-08-21T17:10:07.115Z
 firstPublishedAt: 2019-07-17T19:42:10.960Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Follow the steps below to add a price rule to your store:
 
 ## Admin
 
-1. In the VTEX Admin, go to *Prices > Price rules*, or type *Price rules* in the search bar at the top of the page.
+1. In the VTEX Admin, go to **Prices > Price rules**, or type **Price rules** in the search bar at the top of the page.
 2. Click on the green **New Rule** button.
 3. In the first step, **What is the general data of this rule?**, select a trade policy from the *dropdown menu*.
 4. In the second step, **What items will this rule apply to?**, choose whether the rule will apply to *all products* or *only to chosen categories and brands*. If you select the second option, you should also choose the **Categories** and/or desired **Brands**.
diff --git a/docs/tracks/en/adding-extra-text-to-the-order-print.md b/docs/tracks/en/adding-extra-text-to-the-order-print.md
index bad208411..d30bfbb03 100644
--- a/docs/tracks/en/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/en/adding-extra-text-to-the-order-print.md
@@ -38,7 +38,7 @@ After reloading inStore, whenever a salesperson prints an order, this text will
 
 Before adding extra text, the printout of the order summary has the following format:
 
-![28. Adding extra text to the order print - 1](https://images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
+![28. Adding extra text to the order print - 1](//images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
 
 In our example, we changed the `checkout-instore-custom.js` file by inserting the following extra text:
 
@@ -50,4 +50,4 @@ window.INSTORE_CONFIG = {
 
 Now, whenever an order summary is printed, we will get the following result:
 
-![28. Adding extra text to the order print - 2](https://images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
+![28. Adding extra text to the order print - 2](//images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
diff --git a/docs/tracks/en/adding-new-stores-to-instore.md b/docs/tracks/en/adding-new-stores-to-instore.md
index b60b96b0c..2f2f9099b 100644
--- a/docs/tracks/en/adding-new-stores-to-instore.md
+++ b/docs/tracks/en/adding-new-stores-to-instore.md
@@ -3,8 +3,8 @@ title: 'Managing physical stores in VTEX Sales App'
 id: 5PSjRstg7UU4lOm0s8aqKN
 status: PUBLISHED
 createdAt: 2020-06-29T13:30:51.354Z
-updatedAt: 2023-05-31T15:07:31.507Z
-publishedAt: 2023-05-31T15:07:31.507Z
+updatedAt: 2023-07-26T18:59:24.074Z
+publishedAt: 2023-07-26T18:59:24.074Z
 firstPublishedAt: 2020-06-29T14:22:11.121Z
 contentType: trackArticle
 productTeam: Shopping
@@ -25,7 +25,7 @@ This page allows you to perform the following actions:
 * [Edit](#editing-a-physical-store)
 * [Inactivate](#inactivating-a-physical-store)
 
-![loja-fisica-EN](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
+![loja-fisica-EN](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
 
 The page displays the following information: 
 
@@ -50,7 +50,7 @@ You can add a physical store by following the steps below:
 
 ### Physical store fields
 
-![loja-fisica2-en](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
+![loja-fisica2-en](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
 
 #### Identification
 
diff --git a/docs/tracks/en/adding-product-specifications.md b/docs/tracks/en/adding-product-specifications.md
index 6269e5059..8705bf627 100644
--- a/docs/tracks/en/adding-product-specifications.md
+++ b/docs/tracks/en/adding-product-specifications.md
@@ -35,7 +35,7 @@ To add specifications, your store already needs to have departments, categories,
 7. Fill out the specification form fields. For more info on each field, access our article on [how to fill out product specification fields](https://help.vtex.com/en/tutorial/creating-a-product-field--tutorials_106).
 8. Click on **Save**.
 
-![EN.1novo](https://images.ctfassets.net/alneenqid6w5/2dF0ogtrRK8JwAfpklyJ7I/2ff6abcfd3e119739d8d383524b6305b/EN.1novo.gif)
+![EN.1novo](//images.ctfassets.net/alneenqid6w5/2dF0ogtrRK8JwAfpklyJ7I/2ff6abcfd3e119739d8d383524b6305b/EN.1novo.gif)
 
 The following steps will let you add specification values:
 
@@ -49,7 +49,7 @@ The following steps will let you add specification values:
 8. Click on **New Value**.
 9. Type in the **Name** of the desired value and click on **Save**.
 
-![EN.2novo](https://images.ctfassets.net/alneenqid6w5/2LBqRIgwrRKGFRZI1k66xV/c225f4b00ecd036deb541355d10278e8/EN.2novo.gif)
+![EN.2novo](//images.ctfassets.net/alneenqid6w5/2LBqRIgwrRKGFRZI1k66xV/c225f4b00ecd036deb541355d10278e8/EN.2novo.gif)
 
 ### Linking specifications to a product
 
@@ -63,7 +63,7 @@ To include specifications to a **Product**, complete the following steps:
 4. Select the **Specifications** tab and choose the specification value for this product.
 5. Click on the **Product** tab and then on **Save**.
 
-![EN.3novo](https://images.ctfassets.net/alneenqid6w5/6aLqyJEcn1gn7ZY6D1HOBR/b98761150ff82fce355480c78f7693e6/EN.3novo.gif)
+![EN.3novo](//images.ctfassets.net/alneenqid6w5/6aLqyJEcn1gn7ZY6D1HOBR/b98761150ff82fce355480c78f7693e6/EN.3novo.gif)
 
 ## Spreadsheet
 
@@ -92,7 +92,7 @@ After filling in the spreadsheet data, follow the instructions below to import y
 5. Click on **Select** to choose the filled-out spreadsheet.
 6. Click on **Import**.
 
-![EN.4](https://images.ctfassets.net/alneenqid6w5/38zcVf51x9HpqztCxmfgRy/d4d6d36b35f4d0717c3d97fcc9c9223b/EN.4.gif)
+![EN.4](//images.ctfassets.net/alneenqid6w5/38zcVf51x9HpqztCxmfgRy/d4d6d36b35f4d0717c3d97fcc9c9223b/EN.4.gif)
 
 ## API 
 
diff --git a/docs/tracks/en/adding-products.md b/docs/tracks/en/adding-products.md
index 77348df09..973f7abf9 100644
--- a/docs/tracks/en/adding-products.md
+++ b/docs/tracks/en/adding-products.md
@@ -30,7 +30,7 @@ In the VTEX Admin, follow the steps below.
 4.	Fill out the product form fields. For more on what each field means, read our article on [product registration fields](https://help.vtex.com/en/tutorial/product-registration-fields--4dYXWIK3zyS8IceKkQseke).
 5.	Click on `Save` or `Save and add new SKU`, in case you want to add SKUs associated to that product. 
 
-![Catalogo - Cadastrar produto EN.gif?h=250](https://images.ctfassets.net/alneenqid6w5/4Egs4EQBhRUeVCGRvIyNE2/0a89b7d303c4b2a67a686bd9d696bff4/Catalogo_-_Cadastrar_produto_EN.gif_h_250)
+![Catalogo - Cadastrar produto EN.gif?h=250](//images.ctfassets.net/alneenqid6w5/4Egs4EQBhRUeVCGRvIyNE2/0a89b7d303c4b2a67a686bd9d696bff4/Catalogo_-_Cadastrar_produto_EN.gif_h_250)
 
 ## Spreadsheet
 
diff --git a/docs/tracks/en/adding-skus.md b/docs/tracks/en/adding-skus.md
index dbef58c40..545c97b64 100644
--- a/docs/tracks/en/adding-skus.md
+++ b/docs/tracks/en/adding-skus.md
@@ -25,7 +25,7 @@ There are two flows which can be used to add SKUs through the VTEX Admin: creati
 ### Adding SKUs after creating a product
 
 1.	On the Product creation page, after filling out the fields, click on **Save and add new SKU**. 
-  ![picture1.en](https://images.ctfassets.net/alneenqid6w5/3J1j18vSKiyJ4Bwy5ZLywM/bb8974140c754821ea0d10006a5f943a/picture1.en.png) 
+  ![picture1.en](//images.ctfassets.net/alneenqid6w5/3J1j18vSKiyJ4Bwy5ZLywM/bb8974140c754821ea0d10006a5f943a/picture1.en.png) 
 2.	You will be redirected to the SKU form page, where you need to fill out fields. For more on each field’s meaning, access our article on [how to fill in SKU creation fields](https://help.vtex.com/en/tutorial/sku-fields--21DDItuEQc6mseiW8EakcY). 
 3.	Click on `Save`.
 
@@ -43,7 +43,7 @@ There are two flows which can be used to add SKUs through the VTEX Admin: creati
 After adding a SKU you’ll need to also link an image to it in order to activate it. Follow the steps below to add an image:
 
 1.	On the page where you added a SKU, click on the **Images** tab
-![picture6.en](https://images.ctfassets.net/alneenqid6w5/o99jKS63EZgaeahw9fQvn/47726c30833fd390f2c93f7ec6c0d404/picture6.en.png)
+![picture6.en](//images.ctfassets.net/alneenqid6w5/o99jKS63EZgaeahw9fQvn/47726c30833fd390f2c93f7ec6c0d404/picture6.en.png)
 2.	Click on `Insert` and choose the image you want to add.
 3.	Fill out the **Text** (image alt tag) and **Label** fields. The label will be used to assist with your site’s page template organization, by referencing the value contained within, i.e. front, side, upper side, etc.
 4.	Click on `Send`.
@@ -53,7 +53,7 @@ After adding a SKU you’ll need to also link an image to it in order to activat
 After adding the images, you must add the SKU specifications. The next step on this track will explain how to add specifications.
 
 1.	Click on the **Specifications** tab.
-![picture7.en](https://images.ctfassets.net/alneenqid6w5/4rKSynG7dNq1iwcwLZBKQo/6180b20ecf55cc6a841ac81757dd0f26/picture7.en.png) 
+![picture7.en](//images.ctfassets.net/alneenqid6w5/4rKSynG7dNq1iwcwLZBKQo/6180b20ecf55cc6a841ac81757dd0f26/picture7.en.png) 
 2.	Fill out the mandatory fields. Specifications may vary according to the selected SKU category.
 3.	Click on `Save`.
 
diff --git a/docs/tracks/en/adding-vendors.md b/docs/tracks/en/adding-vendors.md
index 85cbacdb5..cff96dcf1 100644
--- a/docs/tracks/en/adding-vendors.md
+++ b/docs/tracks/en/adding-vendors.md
@@ -18,7 +18,7 @@ If you have set up your store using the __Easy Setup__ flow you may have already
 
 When you enter VTable (https://{{AccountName}}.myvtex.com/admin/vtable) you will see two applications, __Stores Admin__ and __Vendors Admin__:
 
-![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Click __Vendors Admin__ to open the table where we will add a new vendor.
 
@@ -26,7 +26,7 @@ If you have already registered a seller through __Easy Setup__, just click on __
 
 > __IMPORTANT__: the email of each vendor __CAN'T__ be the same used in VTEX platform, because your admin email has permissions that a salesperson should not have, so it is necessary to use some other email without privileges on the platform.
 
-![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
+![inStore adicionando vendedor](//images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
 If you skipped the vendor creation step in __Easy Setup__ and you don't have any vendors created, you will need to get the __Store__ ID in the __Stores Admin__ in VTable.
 
diff --git a/docs/tracks/en/adding-warehouses.md b/docs/tracks/en/adding-warehouses.md
index 38c565312..137d31946 100644
--- a/docs/tracks/en/adding-warehouses.md
+++ b/docs/tracks/en/adding-warehouses.md
@@ -29,7 +29,7 @@ Follow the steps below to add a warehouse to your store:
 4. Fill out the inventory form fields. For more on each field's meaning, see the [Data Entry Fields](#data-entry-fields) section below.
 5. **Save**.
 
-![EN Cadastrar Estoque GIF](https://images.ctfassets.net/alneenqid6w5/4teusm8ha4Qp7z2SJ8C6R6/d1e9f85854f1da52135f6920b1ad8aaa/EN_Cadastrar_Estoque_GIF.gif)
+![EN Cadastrar Estoque GIF](//images.ctfassets.net/alneenqid6w5/4teusm8ha4Qp7z2SJ8C6R6/d1e9f85854f1da52135f6920b1ad8aaa/EN_Cadastrar_Estoque_GIF.gif)
 
 ### Data Entry Fields
 
diff --git a/docs/tracks/en/allowing-order-replacement.md b/docs/tracks/en/allowing-order-replacement.md
index ff3dd7481..5d53bd316 100644
--- a/docs/tracks/en/allowing-order-replacement.md
+++ b/docs/tracks/en/allowing-order-replacement.md
@@ -3,8 +3,8 @@ title: 'Allowing order replacement'
 id: 381eYJw7lrypjGq3hmPtGV
 status: PUBLISHED
 createdAt: 2019-11-18T11:57:28.677Z
-updatedAt: 2023-03-31T22:52:53.575Z
-publishedAt: 2023-03-31T22:52:53.575Z
+updatedAt: 2024-04-01T17:58:20.948Z
+publishedAt: 2024-04-01T17:58:20.948Z
 firstPublishedAt: 2019-11-18T12:20:58.872Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -18,6 +18,10 @@ trackSlugEN: orders
 
 The goal is to help them correct errors without having to manually place a new order or contact your support, which facilitates the operation of your store and reduces costs.
 
+<div class = "alert alert-warning">
+Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
+</div>
+
 ## Enabling order replacement
 
 This feature is available to all stores. To enable it, follow the steps below:
diff --git a/docs/tracks/en/amazon-account-settings.md b/docs/tracks/en/amazon-account-settings.md
index acc863e3e..9cc22ae1c 100644
--- a/docs/tracks/en/amazon-account-settings.md
+++ b/docs/tracks/en/amazon-account-settings.md
@@ -1,9 +1,9 @@
 ---
 title: 'Amazon account settings'
 id: 43L0dpbjLBz6tcim1BbTzf
-status: PUBLISHED
+status: CHANGED
 createdAt: 2019-02-28T23:01:18.628Z
-updatedAt: 2023-03-08T20:38:03.932Z
+updatedAt: 2023-11-09T22:36:18.079Z
 publishedAt: 2023-03-08T20:38:03.932Z
 firstPublishedAt: 2019-02-28T23:02:20.905Z
 contentType: trackArticle
diff --git a/docs/tracks/en/amazon.md b/docs/tracks/en/amazon.md
index 6311941b0..1cb10e9dc 100644
--- a/docs/tracks/en/amazon.md
+++ b/docs/tracks/en/amazon.md
@@ -16,7 +16,7 @@ trackSlugEN: amazon-integration
 
 Amazon is an ecommerce platform and is considered one of the five largest technology companies in the world. It currently sells a variety of products, such as toys, electronics, clothing, accessories and others In addition, the online retail giant offers streaming services, cloud storage, and virtual assistants.
 
-![amazon logo](https://images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
+![amazon logo](//images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
 
 The integration with Amazon sends products from your VTEX store's catalog to Amazon, allowing you to list your products and increase your sales. 
 
diff --git a/docs/tracks/en/apple-pay.md b/docs/tracks/en/apple-pay.md
new file mode 100644
index 000000000..0518dded9
--- /dev/null
+++ b/docs/tracks/en/apple-pay.md
@@ -0,0 +1,53 @@
+---
+title: 'Apple Pay'
+id: STKWiXJSR9ImPt5EEC2aL
+status: PUBLISHED
+createdAt: 2023-06-28T14:04:58.979Z
+updatedAt: 2024-06-25T21:02:43.540Z
+publishedAt: 2024-06-25T21:02:43.540Z
+firstPublishedAt: 2023-06-28T14:13:24.803Z
+contentType: trackArticle
+productTeam: Shopping
+slug: apple-pay
+locale: en
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugEN: digital-wallet-e-wallet
+---
+
+Your customers can shop using Apple Pay, the [digital wallet](https://help.vtex.com/en/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/7jLbdfch9Oe2yYbQa9zwE1) from Apple. For this, you need to fulfill some requirements:
+
+- Have an account in `developer.apple.com`.
+- Hire a provider that processes payments with Apple Pay.
+
+<div class="alert alert-warning">
+  Apple Pay currently only works on MacOs, IOS operating systems, and the Safari browser. For more information, go to <a href="https://support.apple.com/en-gb/HT208531">Devices compatible with Apple Pay</a>.
+</div>
+
+## Setting up the payment provider
+
+Firstly, you need to configure a provider in your store's Admin that processes transactions with Apple Pay, such as [Adyen](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3) and [Stripe](https://help.vtex.com/en/tutorial/configuring-stripe-gateway-affiliation--fwF2wk2FQKrODrWWkvSLO).
+
+To check all the provider options available for this payment method, access the list as described in Step 5 of the section [Set up payment with Apple Pay](#setting-up-payment-with-apple-pay).
+
+<div class="alert alert-warning">
+  Before starting to configure the provider, you must <a href="register your Merchant ID with Apple Pay">register your Merchant ID with Apple Pay</a>.
+</div>
+
+## Setting up payment with Apple Pay
+
+1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
+2. Click the __Payment conditions__ tab and then the `+` button.
+3. Select the __Apple Pay__ payment method.
+4. Click the `Status` button to enable this payment condition.
+5. In the __Process with provider__ field, select the provider that will be used to process the payments.
+6. If there is an anti-fraud set up in your store, you can activate it for this payment condition by checking the __Use anti-Fraud solution__ box.
+7. Choose whether you want payments to be made in cash or installments.
+8. If you wish, you can also opt for a [special payment condition](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+9. Click `Save`.
+
+After following the indicated steps, Apple Pay may take up to 10 minutes to appear at your store's checkout as a payment option.
+
+### Related articles
+
+- [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay)
+- [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456)
diff --git a/docs/tracks/en/associating-a-template-with-a-layout.md b/docs/tracks/en/associating-a-template-with-a-layout.md
index 8ceef1579..999174d06 100644
--- a/docs/tracks/en/associating-a-template-with-a-layout.md
+++ b/docs/tracks/en/associating-a-template-with-a-layout.md
@@ -30,4 +30,4 @@ This association is made in the layout properties setting. To get there, follow
 6. Select the template you want to associate with this layout.
 7. Type "yes" to confirm the change (this step is necessary because this is a critical change for the site, as the page's front-end will be replaced).
 
-![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tracks/en/autocomplete-search.md b/docs/tracks/en/autocomplete-search.md
index 8b80535b3..c8fa4fea6 100644
--- a/docs/tracks/en/autocomplete-search.md
+++ b/docs/tracks/en/autocomplete-search.md
@@ -55,22 +55,22 @@ Another advantage for the store's manager is the increase in conversion due to t
 
 This section displays the most searched terms on the website by other customers.
 
-![top-busca-EN](https://images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
+![top-busca-EN](//images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
 
 ## Last searches
 
 This section displays the last searches performed by the customer. This way, it is possible to start the interaction with the search instantly.
 
-![historico-EN](https://images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
+![historico-EN](//images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
 
 ## Search suggestions
 
 This section displays the terms and categories other users searched related to the search performed at that time. 
 
-![sugest-EN](https://images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
+![sugest-EN](//images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
 
 ## Product suggestion
 
 This section shows the products that correspond to the search carried out at that moment. By displaying products related to your search while you are typing, it reduces dropouts and gives the user the possibility to make a more dynamic purchase.
 
-![produtos-EN](https://images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
+![produtos-EN](//images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
diff --git a/docs/tracks/en/availability.md b/docs/tracks/en/availability.md
index d6b9ca40b..35d66a8c5 100644
--- a/docs/tracks/en/availability.md
+++ b/docs/tracks/en/availability.md
@@ -3,8 +3,8 @@ title: '​​Availability'
 id: 7LMQbWK5nElIkXo0NK8Kux
 status: PUBLISHED
 createdAt: 2021-10-04T18:01:24.137Z
-updatedAt: 2021-10-04T18:18:56.501Z
-publishedAt: 2021-10-04T18:18:56.501Z
+updatedAt: 2023-12-07T19:28:15.731Z
+publishedAt: 2023-12-07T19:28:15.731Z
 firstPublishedAt: 2021-10-04T18:18:56.501Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ trackSlugEN: vtex-intelligent-search
 
 To generate a search result, VTEX Intelligent Search takes into account the availability of each product found in the search. Available products will always have priority over unavailable products in the search results.
 
-When checking the availability of a product, VTEX Intelligent Search uses the **Show out of stock** field in the [Catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) to verify which products will be displayed even if they are unavailable. If the product configuration defines that it will not be displayed when it is out of stock, the platform will place it at the end of the search results. VTEX Intelligent Search also checks if:
+When checking the availability of a product, VTEX Intelligent Search uses the **Show out of stock** field in the [Catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) to verify which products will be displayed even if they are unavailable. If the product configuration specifies that it should not be displayed when out of stock, the platform will not showcase the product. However, if the configuration indicates that the product should be displayed even when out of stock, the platform will position it at the end of the search results. VTEX Intelligent Search also checks if:
 
 - The product in question is active.
 - At least one product SKU is active.
diff --git a/docs/tracks/en/b2b-form.md b/docs/tracks/en/b2b-form.md
index eb554d1ec..64e904408 100644
--- a/docs/tracks/en/b2b-form.md
+++ b/docs/tracks/en/b2b-form.md
@@ -46,12 +46,12 @@ Examples of how the form with legal entity is presented in inStore:
 
 __B2B Form__ - optional and closed:
 
-![b2b-opcional-fechado](https://images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
+![b2b-opcional-fechado](//images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
 
 __B2B Form__ - optional and open:
 
-![b2b-opcional-aberto](https://images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
+![b2b-opcional-aberto](//images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
 
 __B2B Form__ - mandatory (all fields come already open):
 
-![b2b-obrigatorio](https://images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
+![b2b-obrigatorio](//images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
diff --git a/docs/tracks/en/backend-integrations.md b/docs/tracks/en/backend-integrations.md
new file mode 100644
index 000000000..fcf3b4cdd
--- /dev/null
+++ b/docs/tracks/en/backend-integrations.md
@@ -0,0 +1,408 @@
+---
+title: 'Backend integrations'
+id: 7euXDZR5CCnVFSrXyczIhu
+status: PUBLISHED
+createdAt: 2024-02-05T13:23:32.848Z
+updatedAt: 2024-02-23T02:06:48.878Z
+publishedAt: 2024-02-23T02:06:48.878Z
+firstPublishedAt: 2024-02-22T14:06:58.203Z
+contentType: trackArticle
+productTeam: Others
+slug: backend-integrations
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+Integrations normally begin with back-office software, which allows the management of essential parts of the operation related to [Catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog), [Pricing](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices), [Logistics](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistics), and [Orders](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#pedidos). The main types of software in the back office are:
+
+- ERP (Enterprise Resource Planning)
+- WMS (Warehouse Management System)
+- PIM (Product Information Manager)
+- CRM (Customer Relationship Management)
+
+In addition to the back office, you can integrate the ecommerce platform with other systems that add new features. One example is [payment providers](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments), which allow you to communicate with providers to process payments and include additional payment methods in the [checkout](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout).
+
+## ERP integration
+
+A store's back-office integration setup begins with the ERP software. Other types of software may be used in the back office for specific purposes, such as PIM for managing product data, and WMS for managing inventory.
+
+ERPs and other types of software may have native integrations with VTEX. If not, you will need to implement your own middleware using [VTEX APIs](https://developers.vtex.com/docs/api-reference) to integrate the software with your VTEX account.
+
+The setup process consists of two phases: **initial setup** and **middleware configuration**. After completing these phases, the operational workflow, used for the store's daily operations, will be visible. Learn more about setup in the [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide).
+
+### Initial setup
+
+In this phase, all necessary procedures are conducted to ensure the [VTEX account](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#vtex-account-types) is furnished with all the product information. This includes integrating the catalog, products, prices, and store inventory. Generally, there are three methods to configure this phase: 
+
+- Integrating with external tools.
+- Importing spreadsheets.
+- Manual input via the VTEX Admin.
+
+You must follow the setup steps for this phase in the order shown below. Detailed descriptions of each step can be found in the respective subsections of the [Integrations](#integrations) section of this article.
+
+1. [Catalog architecture](#catalog-architecture)
+
+  a. Category tree
+
+  b. Brands
+
+  c. Specifications (groups and fields)
+
+2. [Importing products](#importing-products)
+
+  a. Importing products
+
+  b. Importing product specifications
+
+  c. Adding products to the trade policy
+
+  d. Importing SKUs
+
+  e. Importing SKU specifications
+
+  f. Importing SKU images
+
+3. [Importing prices](#prices)
+
+  a. Defining base prices
+
+  b. Defining fixed prices for specific contexts
+
+4. [Importing inventory](#inventory)
+
+  a. Creating warehouses
+
+  b. Updating SKU inventory
+
+### Middleware configuration
+
+In this phase, all necessary procedures enable the store to process orders. This includes integrating notifications about changes to orders and actions to process orders. The integrations can be performed in two ways:
+
+- **Platform integration:** This option involves using a third-party platform, known as Platform-as-a-Service (PaaS), which offers a ready-made solution to integrate with VTEX, requiring minimal development effort.
+- **In-house development:** This option involves developing and maintaining your own integration software. The middleware must be capable of handling scalability issues that may arise during sales peaks, such as those experienced during sales events like Black Friday.
+
+You must follow the setup steps for this phase in the order shown below. A detailed description of each step can be found in the respective subsections of the [Integrations](#integrations) section.
+
+1. [Order integration/notification](#order-integration)
+
+  a. Configuring a feed or hook
+
+2. [Order processing](#order-processing)
+
+  a. Change order
+
+  b. Cancellation
+
+  c. Invoicing
+
+  d. Tracking
+
+### ERP integration behavior
+
+After configuring the store and integrating with the middleware, the general flow of information will follow this format:
+
+![ERP-integrations-en](//images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/8e7c022f2bfa116bccf9ccdc80ac2ca7/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_2.jpg)
+
+Each request or process represented by the arrows in the diagram above is triggered by a different type of event in the operation of an ecommerce store. Learn more about this flow in the [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide#ongoing-middleware-flow).
+
+## Integrations
+
+In this section, we will cover the main integrations necessary for running a VTEX store. These integrations encompass a wide range of aspects, including catalog and customer data integration, order management, and single sign-on (SSO). Each integration will be detailed in the sections below.
+
+### Catalog architecture
+
+On VTEX, [Catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog) is the module used for configuring the characteristics of the store's products to make them available to customers. You must create your catalog in the following order:
+
+1. Creating the [category tree](#category-tree).
+2. Adding the [brands](#brands).
+3. Adding the [specifications](#specifications) (optional).
+4. Importing [products](#importing-products).
+5. Importing [SKUs](#importing-products).
+6. [Associating specifications with products and SKUs.](#importing-products)
+
+Learn more about Catalog and back office configuration in the [Catalog](https://developers.vtex.com/docs/guides/catalog-overview) and [Set up catalog](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog) articles.
+
+#### Category tree
+
+After understanding and planning the store's [catalog architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog-architecture), you can create categories in the following ways:
+
+1. **VTEX Admin:** Create each category through the user interface. For more details, see [Creating Categories](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1).
+2. **Catalog API:** Create each category by making API calls. For more details, see [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category).
+3. **Back-office integration:** Import categories from an external back-office software (ERP or PIM) integrated with VTEX. The software may already offer native integration with VTEX or require the development of middleware that uses the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview). See [Category migration from ERP](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#category-migration-from-erps) for more details.
+
+<div class="alert alert-warning">
+When importing categories from external software, the category structure in the software may differ from that of VTEX. In this case, we recommend creating an inactive "mock" category. This category will remain invisible on the storefront and serve as a temporary repository to receive all products and SKUs during the import process. Once the import is complete, you can manually organize the products within the VTEX Admin to match the desired category tree.
+</div>
+
+There are some limitations to be aware of when managing categories:
+
+- **Moving categories:** Although it is possible to move categories to different levels (higher/lower) and/or different departments, this is very risky due to the specifications attached to the category. This action can negatively affect product information since products inherit both previous and new specifications.
+- **Deleting categories:** Deleting a category requires a [complete clean-up](https://help.vtex.com/en/tutorial/database-maintenance-full-cleanup--34P9LGs7BCIQK6acQom802) of the store's catalog.
+
+For more information about importing categories into the back office, check the [Categories](https://developers.vtex.com/docs/guides/categories) article.
+
+#### Brands
+
+[Brands](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) are product attributes that help customers identify both the product and the company behind it. A product must be associated with a single brand, which means that creating brands is a mandatory step in configuring the catalog. Brands can be created through:
+
+1. **VTEX Admin:** Create each brand using the user interface. Learn more in [Registering Brands](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7lEGOSpAlQJCs5eUc5XFmR).
+2. **Catalog API:** Create each brand by making API calls. Learn more in [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand).
+3. **Back-office integration:** Import brands from an external back-office software (ERP or PIM) integrated with VTEX. The software may already offer native integration with VTEX or may require the development of middleware that uses the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Learn more in [Creating Brands in the Catalog configuration guide for back-office](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-brands).
+
+<div class="alert alert-warning">
+If the back-office system has no brand information, you can apply the same approach as mentioned previously for category migration by creating an inactive "mock" brand to be used exclusively for migration purposes. Subsequently, product information can then be manually entered.
+</div>
+
+For more information on importing brands into the back office, check the [Brands](https://developers.vtex.com/docs/guides/brands) article.
+
+#### Specifications
+
+[Specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) are additional properties that can be assigned to products and SKUs in the store. They will be used when creating search filters and distinguishing SKUs and products on the product page. Specifications can be created through [back-office integrations](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-specifications-groups) by using the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview).
+
+There are three types of specifications, which should be created in the following order:
+
+1. Specification groups
+2. Specification fields
+3. Specification values
+
+The diagram below illustrates this procedure.
+
+![catalog_specification_diagram_EN](//images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/2f813d423b73074446a2e2a743e22328/catalog_specification_diagram_EN.png)
+
+Specifications follow the Catalog hierarchy. When a group is created within a department or category, it will be inherited by the subsequent lower levels. 
+
+After creating groups, fields, and values, specifications must be associated with products and SKUs. These procedures are described in the next section: 
+[Importing products](#importing-products).
+
+To learn more about importing specifications into the back office, check the [Specifications](https://developers.vtex.com/docs/guides/specifications) article.
+
+### Importing products
+
+Importing products refers to the act of transferring all relevant product information from an ERP or PIM system to the VTEX platform. This step keeps the product catalog up to date and synced with the store. Whether managing a wide variety of products, SKUs, or different variations, effective product importing is essential to the customer experience.
+
+On VTEX, it is important to understand the distinction between products and SKUs:
+
+- [Product](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru): Abstract catalog unit, visible on the store shelves.
+- [SKU](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA): Concrete catalog unit in stock, representing specific variations of a product, such as color, size, and other attributes. SKUs are displayed as individual items on product pages. SKUs are displayed as individual items on product pages.
+
+<div class = "alert alert-info">
+The way in which products and SKUs are structured directly influences the customer's shopping experience.
+</div>
+
+You should import products in the order shown in the table below:
+
+| **Action** | **Description** | **Methods** |
+| :--- | :--- | :--- |
+| <a href="https://developers.vtex.com/docs/guides/products">1. Import products</a> | Add products to the catalog. | <ul><li>Integration via the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product">Catalog API</a>.</li><li>Import from spreadsheets <a href="https://help.vtex.com/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#spreadsheet">(classic method</a> and <a href="https://developers.vtex.com/docs/apps/vtex.google-drive-import@0.x">Google Drive-import app)</a>.</li><li>Manual input in the <a href="https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL">VTEX Admin</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/product-specifications">2. Import product specifications</a> | Complete the product specifications in the catalog. | <ul><li>Integration via the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/specification">Catalog API</a>.</li><li>Manual input in the <a href="https://help.vtex.com/en/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106">VTEX Admin</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/erp-integration-import-products#add-product-to-trade-policy">3. Add the products to the trade policy</a> | Associate products with their respective <a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">trade policies</a> by defining specific rules (pricing, payments, shipping strategy, etc.) based on the sales channel or audience. Ensure that all products are at least added to the main trade policy. | <ul><li>Integration via the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/salespolicy/-tradepolicyId-">Catalog API</a>.</li><li>Manual input in the <a href="https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL">VTEX Admin when adding a product</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/skus">4. Import SKUs</a> | Add SKUs to the products in the catalog. | <ul><li>Integration via the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit">Catalog API</a>.</li><li>Manual input in the <a href="https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ">VTEX Admin</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/sku-specifications">5. Import SKU specifications</a> | Complete the SKU specifications in the catalog. | <ul><li>Integration via the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/specification">Catalog API</a>.</li><li>Manual input in the <a href="https://help.vtex.com/en/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119">VTEX Admin</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/images">6. Import SKU images</a> | Add images to the SKUs. | <ul><li>Integration via the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file">Catalog API</a>.</li><li>Manual input in the <a href="https://help.vtex.com/en/tutorial/como-atualizar-a-imagem-de-um-sku--5PMb54FnvUuWOq2qGyAosu">VTEX Admin</a>.</li></ul> |
+
+<br>
+
+<div class="alert alert-warning">
+The product information in the ERP is often not suitable for use and display in the ecommerce store. For this reason, the information will need to undergo an enhancement process. This can include restructuring categories and creating more descriptive and appealing product descriptions.
+</div>
+
+After the import, it's also important to ensure that product and SKU information is kept up to date. You can check the instructions in the [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information) article.
+
+For more information about importing products into the back office, check the [Import products](https://developers.vtex.com/docs/guides/erp-integration-import-products) article.
+
+### Prices
+
+[Prices](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices) are the sales value of SKUs and are stored in [price tables](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8).  To ensure that your store products are competitively priced and tailored to various sales channels, you need to understand how pricing information is integrated into the VTEX platform. 
+
+In sales operations, it is common to delegate price calculation to the ERP, from which this data can be imported. Prices have a base value defined for each SKU and can vary depending on the context. The steps for importing prices are as follows:
+
+1. **Define the base price:** The base price is used as a reference for determining the price of a product in the VTEX pricing system. The base price of a SKU can be imported via integration using the [Pricing API](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-) or [created through the VTEX Admin](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29).
+2. **Define fixed prices for specific contexts:** The base price can be adjusted or modified based on specific rules, calculations, or fixed prices to arrive at the SKU's final retail price in different contexts. These contexts include the [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV), [customer group](https://help.vtex.com/en/tutorial/como-criar-um-cluster-de-clientes--frequentlyAskedQuestions_1724), [promotion](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR), among other factors. Fixed prices for specific contexts can be imported by integration using the [Pricing API](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-), [imported via spreadsheet](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#importing-prices), or [created through the VTEX Admin](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj#admin).
+
+After importing, it's also important to ensure that the pricing information is kept up to date. You can check the instructions in the [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information#pricing-updates) article.
+
+For more information about importing prices into the back office, check the [Import prices](https://developers.vtex.com/docs/guides/erp-integration-import-prices) article.
+
+### Inventory
+
+In the VTEX [Logistics](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistics) module, [inventory](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139) consists of the relationship between a store's sales items (SKUs) and the locations where these items are stored, known as [warehouses](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb). Efficient management of this inventory when importing data into VTEX is crucial to provide customers with accurate product availability, thereby enhancing the [logistics and shipping](https://help.vtex.com/en/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) process.
+
+These are the steps for importing inventory:
+
+1. **Create warehouses:** Define the physical or virtual locations where the SKUs will be stored. Warehouses can be imported via integration using the [Logistics API](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) or [created through the VTEX Admin](https://help.vtex.com/en/tutorial/gerenciar-estoque--tutorials_137).
+2. **Update SKU inventory:** Enter the available quantity of each item in the warehouses. Warehouses can be imported via integration using the [Logistics API](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-), via [spreadsheet](https://help.vtex.com/en/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034), or [updated through the VTEX Admin](https://help.vtex.com/en/tutorial/como-atualizar-estoque--2MDwYV1COA6YuoiY22AyGo).
+
+After importing, it is also important to ensure that the price information is kept up to date. You can check the instructions in the [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information#pricing-updates) article.
+
+For more information about importing inventory into the back office, check the [Import inventory](https://developers.vtex.com/docs/guides/erp-integration-import-inventory) article.
+
+### Customer data
+
+Importing customer data into VTEX facilitates the integration of information from external systems, such as CRM applications. By default, VTEX stores customer data in [Master Data V1](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). 
+
+Within Master Data, the information is structured into [data entities](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#data-entities), akin to tables in database systems, containing [documents](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#documents) that are similar to rows or records. Customer profile data is stored in the `CL` entity, while customer addresses are stored in the `AD` entity.
+
+These are the steps for importing customer data:
+
+1. **Create new customer profiles:** Create documents in the `CL` entity containing customer profile data, such as name, email, phone number, among others. This data can be imported via integration using the [Master Data API](https://developers.vtex.com/docs/api-reference/masterdata-api#post-/api/dataentities/-acronym-/documents).
+2. **Create addresses:** Create documents in the `AD` entity containing customer addresses, including information such as street, city, postal code, etc. Each address is associated with a customer, and a customer can have several addresses. This data can be imported via integration using the [Master Data API](https://developers.vtex.com/docs/api-reference/masterdata-api#post-/api/dataentities/-acronym-/documents).
+
+For more information about importing customer data into the back office, check the [Import customer data](https://developers.vtex.com/docs/guides/import-customer-data) article.
+
+### Order integration
+
+On the VTEX platform, [orders](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#orders) are generated when a customer places the order by clicking the place order button. Each order includes various details, such as the items in the cart, the purchase amount, the chosen payment method, and other relevant information.
+
+Order integration enables communication between the back-office application, ERP, or WMS, and VTEX's OMS (Order Management System). This integration plays a key role in:
+
+- Handling events related to [order status](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196) changes.
+- Obtaining [order details](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl).
+- Transmitting information related to [order processing](#order-processing).
+
+#### Receiving order updates
+
+With the back office receiving order updates, it is possible to accelerate and automate the procedures involved in [order processing](#order-processing), including invoicing and cancellations.
+
+There are two ways of tracking order status changes on VTEX:
+
+- [Feed v3](https://developers.vtex.com/docs/guides/orders-feed): This is a list of events about order updates. For this type of integration, VTEX provides an [endpoint](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/orders/feed/config?endpoint=get-/api/orders/feed/config) that allows the back office to query the items on the list, process the orders, and then remove the items from the list.
+- [Hook](https://developers.vtex.com/docs/guides/orders-feed#hook): This is a channel for automatically sending notifications about order updates. For this type of integration, the back-office application provides an [endpoint](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/orders/hook/config?endpoint=get-/api/orders/hook/config) for VTEX to send notifications regarding order updates. After receiving a notification, the back office proceeds to process the order.
+
+For both types of integration, you can apply [filters](https://developers.vtex.com/docs/guides/orders-feed#filter) to select the types of events that the back office should process.
+
+<div class = "alert alert-info">
+For most cases, VTEX recommends integrating orders via <a href="https://developers.vtex.com/docs/guides/orders-feed">Feed v3</a> due to its resilience.
+</div>
+
+#### Obtaining order details
+
+In addition to status changes, the operation may need to obtain additional information about an order. You can obtain detailed information about an order via the [Orders API](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-), which can be used in an integration with the desired back-office system.
+
+Order details are used in various procedures in order processing, such as the order items for handling and the purchase amount for invoicing purposes.
+
+#### Order handling
+
+After the order details have been submitted to the back office, the final step before starting order processing is to change the order status to `Start handling`. This procedure can be integrated with the back office via the [Orders API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
+
+For more information on back-office integration of orders, see [Set up order integration](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-integration) and [Feed v3](https://developers.vtex.com/docs/guides/orders-feed).
+
+### Order processing
+
+In this step, the integration is configured to send order updates from the back office, ERP, or WMS to VTEX. During order handling, various actions can be applied, including changes, cancellations, and invoicing.
+
+Below are the events that the back office can transmit to VTEX. The integration between VTEX and the back office for transmitting these events is done via the [Orders API](https://developers.vtex.com/docs/api-reference/orders-api).
+
+- **Change order:** Change order items or amounts.
+- **Cancel order:** Cancel the order and the payment.
+- **Invoice order:** [Add the invoice to the order](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT). This is the indication that the order has been successfully completed and is ready for shipment.
+- **Track order:** Send the tracking information. This could include the carrier's tracking code or URL, or updates about the order's tracking status.
+
+For more information about configuring order processing for the back office, check the [Set up order processing](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-processing) and [Change order](https://developers.vtex.com/docs/guides/change-order) articles.
+
+### Single Sign-On (SSO)
+
+Single sign-on is a method that allows users to authenticate on the platform using a single set of login credentials, eliminating the need to log in separately to each application. VTEX supports integration with external identity providers. Besides native integrations with services like [Google](https://help.vtex.com/en/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google--1lBgDmetUM4goie6mYEOK6), it also allows you to create new integrations with other providers.
+
+**VTEX ID** is the service that identifies users on the platform. This service operates based on the audience, the business rules, and the type of persona that can interact with each VTEX module. The available audiences are:
+
+| **Audience** | **Context** | **Technology** |
+| :---: | :--- | :--- |
+| [VTEX Admin](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) | Identification in the [VTEX Admin](https://help.vtex.com/en/tutorial/vtex-admin-start-here--531cHtUCUi3puRXNDmKziw) for store administrators and operators. | SAML 2.0 (Security Assertion Markup Language). |
+| [Webstore](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) | Identification in the VTEX storefront, intended for store customers. | OAuth 2.0 (Open Authorization). |
+
+Learn more in the [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) article.
+
+### Payments
+
+VTEX [Payment](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments) systems offer extensive features to support various [payment methods](https://developers.vtex.com/docs/guides/payments-integration-payment-methods), [conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento), and integrations. Payments on VTEX have the following [purchase flow](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows) options:
+
+- **Transparent:** The payment process is integrated directly into the checkout, where the buyer chooses the desired payment method.
+- **Redirect:** Opens a new window in the buyer's browser, where the payment is processed by an external service. After completing the payment, the buyer is redirected back to the checkout to place their order.
+- **Payment App:** Opens a modal window on the checkout page. When the payment is completed, the window closes and the purchase flow continues on the checkout page. This flow can also be used for the [3D Secure 2 (3DS2)](https://developers.vtex.com/docs/guides/payments-integration-payment-app#scenario-2-payment-app-and-3d-secure-2) authentication method.
+
+You have the following options to add payment options to a VTEX store:
+
+- **Natively supported payment provider:** If VTEX offers integration with the desired payment provider, you must have a contract with the provider and configure the payment options through the VTEX Admin. You can find more details in the [Payments](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments) article and the payment providers supported by VTEX in the [List of Payment Providers by Country](https://help.vtex.com/en/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).
+- **Custom payment provider:** If the desired payment provider does not have an integration with VTEX, you will need to implement your own payment connector using the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). This protocol includes the [API endpoints](https://developers.vtex.com/docs/api-reference/payment-provider-protocol) to connect to VTEX's [payment gateway](https://help.vtex.com/en/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk). The connector can be implemented by a [VTEX partner agency](https://partnerportal.vtex.com/). Once developed, the connector must be tested and go through the [homologation process](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation) before it can be made available on VTEX. 
+
+For more information about integrating a new payment provider, see [Integrating a new payment provider on VTEX](https://developers.vtex.com/docs/guides/integrating-a-new-payment-provider-on-vtex).
+
+### Gift cards
+
+On VTEX, gift cards can be used as a payment option at **Checkout**, and as part of loyalty programs. VTEX provides a native gift card solution and also supports integrations with external gift card providers.
+To add gift cards to a VTEX store, you have the following options:
+
+- **Native gift card solution:** If you want to use VTEX's native gift card solution or an existing integration, you must configure the gift cards via the VTEX Admin by following the steps in the article [Setting up Gift cards](https://help.vtex.com/en/tutorial/gift-card--tutorials_995).
+- **Custom gift card provider:** If the desired gift card provider does not have an integration with VTEX, you must implement your own integration using the [Gift Card Provider Protocol](https://help.vtex.com/en/tutorial/integrando-com-gift-card). Through this protocol, providers can develop an integration containing the endpoints described in our [Gift Card Provider Protocol API](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol#overview) and connect to our [Gift Card Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api#overview).
+
+### Anti-fraud solution
+
+The anti-fraud solution is a system specialized in analyzing purchases made on websites in order to identify fraudulent transactions. On VTEX, the payment operator first approves the purchase, and then the anti-fraud system evaluates the order.
+
+To add an anti-fraud system to the payments of a VTEX store, you have the following options:
+
+- **Natively supported anti-fraud system:** If there is already an integration with the desired anti-fraud system in VTEX, you must have a contract with one of the partner companies and configure it in the VTEX Admin. You can learn more in the [Configuring the anti-fraud](https://help.vtex.com/en/tutorial/como-configurar-antifraude--tutorials_446) and [What is anti-fraud?](https://help.vtex.com/en/tutorial/o-que-e-antifraude--69SjFCc4rC6Ii0OMAeYAsG) articles.
+- **Custom anti-fraud system:** If the desired anti-fraud system does not have an integration with VTEX, you will need to implement your own anti-fraud integration using the [Anti-fraud Provider Protocol](https://developers.vtex.com/docs/guides/how-the-integration-protocol-between-vtex-and-antifraud-companies-works) containing the [Anti-fraud Provider API](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol) endpoints.
+
+## Extensions and apps
+
+In addition to the core services offered by VTEX, you can enhance the features of VTEX stores by adding extensions. These extensions are tools that expand the capabilities of the VTEX platform. They offer a range of possibilities, such as adding payment and marketplace providers, customizing the storefront, building custom backend services, and creating new applications for the VTEX Admin.
+
+One way to add new features to the VTEX platform is by creating apps using [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io), our development platform that provides high-performance management, scalability, and robust security. With VTEX IO, developers can focus on designing business solutions without worrying about infrastructure issues.
+
+### What is an app on VTEX?
+
+An [app](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app) on VTEX refers to an application built using VTEX IO. Apps are a type of extension, i.e., they extend the features of the VTEX platform. [Development](https://developers.vtex.com/docs/app-development) can be local using custom code and then integrated into the stores operating on our infrastructure. In addition, apps can be offered and purchased through the [VTEX App Store](https://developers.vtex.com/docs/guides/vtex-app-store).
+
+These are the types of apps available on VTEX:
+
+- [Storefront](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ): Store themes developed with [Store Framework](https://help.vtex.com/en/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework).
+- [Frontend](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io): [React](https://react.dev/) components that compose store themes developed with Store Framework.
+- [Admin VTEX](https://learn.vtex.com/docs/course-admin-lang-en): Modules and features for the [VTEX Admin](https://help.vtex.com/en/tutorial/vtex-admin-start-here--531cHtUCUi3puRXNDmKziw).
+- [Services (backend)](https://developers.vtex.com/docs/guides/vtex-io-documentation-service): [Node](https://nodejs.org/en) or [.NET Core](https://dotnet.microsoft.com/en-us/) services capable of handling events and triggers, exporting HTTP routes, and exposing GraphQL resolvers.
+- [Pixel](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developnativeintegrationswithpixelapps): Scripts from third-party services that run on the frontend, providing solutions such as sales monitoring, user support, data collection, and marketing services.
+- [Edition](https://developers.vtex.com/docs/guides/vtex-io-documentation-edition-app): Set of settings, policies, backend, and frontend apps encapsulated and exported by a [Sponsor Account](https://developers.vtex.com/docs/guides/vtex-io-documentation-sponsor-account).
+
+To learn more about the options for implementing apps, check out the [list of builders](https://developers.vtex.com/docs/guides/vtex-io-documentation-builders#list-of-builders).
+
+You can find more information in the [What is a VTEX App](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app) article.
+
+### Before installing an app in your store
+
+Before starting the process of developing a new app, we recommend exploring solutions that are ready to be installed in your store. You can find these solutions in the [Extensions Hub](https://help.vtex.com/en/tracks/extensions-hub--AW7klkYMh557y5IUOgzco), the VTEX Admin section that centralizes extension management.  The following pages are available in the Extensions Hub:
+
+- **App Store:** Marketplace where apps developed by VTEX and third parties are available. On this page, you can view, purchase, and install apps for a VTEX account. There are free and paid apps, which have different billing methods.
+- **App Management:** Page that allows you to install, uninstall, remove, and configure apps in the store.
+
+Here are some examples of solutions available on the App Store:
+
+- [Assembly Options](https://developers.vtex.com/docs/guides/assembly-options-app): Adds [attachment](https://help.vtex.com/en/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm) options for customizing SKUs. For example, adding a phrase to a T-shirt or ingredients to a sandwich.
+- [Gift List](https://developers.vtex.com/docs/apps/vtex.list): Allows you to create gift lists, which can be shared so that others can purchase items for gifting. It is useful for events such as birthdays, weddings, and baby showers. The purchased items are converted into store credits, which can be used to buy any available items in the store.
+- [Live Shopping](https://developers.vtex.com/docs/apps/vtexventures.livestreaming): Enables live streaming on the store's website to engage customers in real time. It creates opportunities to promote products and includes several components besides the video player, such as the number of viewers, a like button, live chat, and a sidebar for presenting products.
+- **Customer chat apps:** Add a chat component to interact with customers. They can have a chatbot for automatic interaction, as well as providing human support. Some examples of apps are [JivoChat](https://developers.vtex.com/docs/apps/vtex.jivochat), [Tawk.to](https://developers.vtex.com/docs/apps/vtex.tawk-to), and [Zendesk Chat](https://developers.vtex.com/docs/apps/vtex.zendesk-chat).
+- **Analysis and review apps:** These apps add components for customers to review store products, usually with a numerical rating or with a review. Some examples of apps are [Reviews and Ratings by VTEX](https://developers.vtex.com/docs/apps/vtex.reviews-and-ratings), [Bazaarvoice](https://developers.vtex.com/docs/apps/vtex.bazaarvoice), and [PowerReviews](https://developers.vtex.com/docs/apps/vtex.powerreviews).
+- **Social media apps:** These apps allow interaction with social media. For example, they allow promoting store products through ads on the media platform. Examples of such apps include [TikTok for Business](https://developers.vtex.com/docs/apps/vtexbr.tiktok-tbp) and [Facebook Business Extension](https://developers.vtex.com/docs/apps/vtex.facebook-fbe).
+
+### Before creating an app for your store
+
+If you can't find an app that meets the needs of your VTEX store, you can develop a custom solution. When developing apps for VTEX, there are several aspects to consider:
+
+- **Who will develop and maintain the app?** Apps can be developed and maintained by the company's in-house development team or by a VTEX-certified agency. You can find [VTEX implementation partners](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) on our [Partner Portal](https://partnerportal.vtex.com/) (available only in Portuguese). In addition to development, the team or agency will also be responsible for maintaining and updating the app.
+- **What kind of app should be developed?** It is important to know the context in which the desired solution will operate. As [previously](#what-is-an-app-on-vtex) described, various types of apps are available. To assist in the development process, we have development guides for certain types of apps, such as [storefront](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io), [service](https://developers.vtex.com/docs/guides/vtex-io-documentation-developing-service-configuration-apps), and [Pixel](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developnativeintegrationswithpixelapps) apps.
+- **How do you develop an app?** Developing an app takes several stages. In general, the development process follows these steps:
+
+  a. **Prepare the development environment**: The main requirements before starting to develop an app are to [install](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install) the [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) (command-line interface) and [create a development workspace](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace) in the store account.
+
+  b. **Interact with the code**: Development usually starts with an initial template, followed by local implementation in the code. The template should be chosen based on the type of app you want. You can check the available templates by running the [CLI command](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-command-reference) `vtex init`. Additionally, you'll need to configure the [manifest.json](https://developers.vtex.com/docs/guides/vtex-io-documentation-manifest) file. This configuration involves defining various parameters such as the app name, the developer or <em>vendor</em> name, and the required [permissions](https://developers.vtex.com/docs/guides/vtex-io-documentation-policies). Once the code is edited, the app is deployed into the development workspace using the [CLI command vtex link](https://developers.vtex.com/docs/guides/vtex-io-documentation-linking-an-app) for testing purposes.
+
+  c. **Package the code into a new version:** After testing, you must follow the steps for [launching a new version of the app](https://developers.vtex.com/docs/guides/vtex-io-documentation-releasing-a-new-app-version) and [publishing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-publishing-an-app). This allows the code to be saved in the VTEX infrastructure and installed in [production workspaces](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace).
+
+  d. **(Optional) Validate whether the app meets your business needs:** Once the version has been published, it may be beneficial to install the app in a [production workspace](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace) and conduct an [A/B test](https://developers.vtex.com/docs/guides/ab-tests) in order to compare the sales conversion rate before and after using your new app.
+
+<div class = "alert alert-info">
+If you're interested in learning more about app development, we recommend visiting our <a href="https://learn.vtex.com/">Learning Center</a>.
+</div>
+
+- **Considering making your app publicly available?** You can [make the app available](https://developers.vtex.com/docs/guides/vtex-io-documentation-making-your-new-app-version-publicly-available) in the App Store, allowing other accounts to leverage the solution you've developed.
+- **Do you want to make your app available on the App Store?** There are some advantages to making your app available on the App Store, such as increasing its visibility and the potential for [monetization](https://developers.vtex.com/docs/guides/vtex-io-documentation-setting-your-apps-billing-model). To do this, you need to follow a few steps and comply with certain rules. In summary, you must become a [registered developer](https://developers.vtex.com/docs/guides/vtex-io-documentation-becoming-a-registered-vtex-app-store-developer), ensure the app code is stored in a [GitHub](https://github.com) repository, develop the app in accordance with the [App Store's best practices](https://developers.vtex.com/docs/guides/vtex-io-documentation-homologation-requirements-for-vtex-app-store), and [submit it](https://developers.vtex.com/docs/guides/vtex-io-documentation-submitting-your-app-in-the-vtex-app-store) to the homologation process. Once it is approved, your app will be available on the App Store.
diff --git a/docs/tracks/en/banners-en.md b/docs/tracks/en/banners-en.md
index d9cbfad06..4a1e55b13 100644
--- a/docs/tracks/en/banners-en.md
+++ b/docs/tracks/en/banners-en.md
@@ -33,7 +33,7 @@ On VTEX Admin, the page **Storefront** > **Banners** shows the full list of regi
 * [Edit a banner](#editing-a-banner)
 * [Delete a banner](#deleting-a-banner) 
 
-![banners-intro-en](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
+![banners-intro-en](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
 
 The page shows the following information:
 
diff --git a/docs/tracks/en/barcode-reading.md b/docs/tracks/en/barcode-reading.md
index f58990ca5..57a40007d 100644
--- a/docs/tracks/en/barcode-reading.md
+++ b/docs/tracks/en/barcode-reading.md
@@ -18,7 +18,7 @@ After identifying the customer, the sales associate is taken directly to the car
 
 If the sales associate is using a tablet or smartphone, they will see a barcode button <i class="fas fa-barcode"></i> on the top bar of the application.
 
-![31. VTEX Sales App - Product Overview - 6 - EN](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/2db81c47910586c71b8f4251f324d5f5/barcode.png)
+![31. VTEX Sales App - Product Overview - 6 - EN](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/2db81c47910586c71b8f4251f324d5f5/barcode.png)
 
 When clicking on it, the sales associate can use the camera to beep a product and, with that, be automatically taken to the details screen of that product.
 
diff --git a/docs/tracks/en/basic-vtex-io-developer-setup.md b/docs/tracks/en/basic-vtex-io-developer-setup.md
index bf18a7d29..2633c78cc 100644
--- a/docs/tracks/en/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/en/basic-vtex-io-developer-setup.md
@@ -38,7 +38,7 @@ This will open a browser window and ask for your credentials.
 
 When you are logged in, you can use the `vtex whoami` command to find out which *account* and *workspace* you are currently using.
 
-![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
+![Command Line](//images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
 <div class="alert alert-info">
 PROTIP: You can configure your terminal to display your current account and workspace automatically. The easiest way to do it is to use our <a href="https://github.com/vtex/dotfiles">dotfiles</a>, which automatically configure <a href="https://fishshell.com/">Fish Shell</a> and add a <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">prompt function</a> for you.
@@ -54,7 +54,7 @@ By default, when you log in to a store you are in the `master` workspace. You ca
 $ vtex ls
 ```
 
-![Command Line vtex ls](https://images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
+![Command Line vtex ls](//images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
 
 ## Creating your own workspace
 
@@ -72,6 +72,6 @@ TIP: You can switch to <em>and reset</em> a workspace to master in a single comm
 
 Workspaces can be named arbitrarily, but we find it’s usually convenient to name it after yourself when you want to develop something in your own environment.
 
-![command line workspace](https://images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
+![command line workspace](//images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
 
 Now you have your own workspace. You can call `vtex list` again and notice that the installed apps mirror those in `master`. Now, let’s `link` a local version of the store theme so you can start editing it.
diff --git a/docs/tracks/en/best-practices-for-testing-instore.md b/docs/tracks/en/best-practices-for-testing-instore.md
index 08a9733a4..6e00069be 100644
--- a/docs/tracks/en/best-practices-for-testing-instore.md
+++ b/docs/tracks/en/best-practices-for-testing-instore.md
@@ -17,7 +17,7 @@ trackSlugEN: instore-using-the-app
 
 After configuring the basic settings and installing VTEX Sales App on a device, it is important to run tests before you start using the app in your physical stores. In this article, you will learn about best practices for testing VTEX Sales App.
 
-![testes-instore-en](https://images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/52fda979578d04c818658558df9a753f/Group_5__1_.png)
+![testes-instore-en](//images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/52fda979578d04c818658558df9a753f/Group_5__1_.png)
 
 ## Technical testing
 
diff --git a/docs/tracks/en/billing-support.md b/docs/tracks/en/billing-support.md
new file mode 100644
index 000000000..7cb650abb
--- /dev/null
+++ b/docs/tracks/en/billing-support.md
@@ -0,0 +1,51 @@
+---
+title: 'Billing support'
+id: 3g2mhmPDx5GszNgLDICzsl
+status: PUBLISHED
+createdAt: 2024-02-20T21:41:41.795Z
+updatedAt: 2024-02-22T14:08:36.105Z
+publishedAt: 2024-02-22T14:08:36.105Z
+firstPublishedAt: 2024-02-22T14:08:36.105Z
+contentType: trackArticle
+productTeam: Others
+slug: billing-support
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+After [joining VTEX](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz), clients may have questions related to changing their account details, billing information, invoices, and other billing aspects of the account. To address these, billing support is available to help with contractual and billing issues related to stores and VTEX.
+
+You can start by exploring the [Help Center](https://help.vtex.com/pt/) articles and by checking the topics below.
+
+## Accounts payable
+
+VTEX is committed to ensuring compliance with the procedures and policies for payments to suppliers of its branches. To do so, VTEX has implemented location-specific practices that suppliers need to follow:
+
+- [Accounts Payable - Brazil](https://help.vtex.com/pt/tutorial/contas-a-pagar-brasil--tutorials_660): Practices to follow in all payments to suppliers related to the accounts payable procedures of VTEX branches in Brazil.
+
+- [Accounts Payable - International](https://help.vtex.com/en/tutorial/accounts-payable-international--3yea9sIlsA0KgUC28ASCGs): Practices to follow for all payments to suppliers related to the accounts payable procedures of VTEX branches outside Brazil.
+
+<div class = "alert alert-info">
+To check the list of VTEX international offices and to find out in which country the invoice is issued, see the <a href="https://help.vtex.com/en/tutorial/names-of-vtex-branches-worldwide--zg05n6OIOZOEmLW7dcq9z">Names of VTEX branches worldwide</a> article.
+</div>
+
+Revenue refers to orders with the `Approved orders` status on the [Order Details page](https://help.vtex.com/en/tutorial/order-details-page--2Y75n54Cc9VizrlG1N6ZNl). Once an order is financially approved, the invoice reflects the total amount, including shipping and taxes. This is regardless of subsequent cancellations due to using the platform's infrastructure.
+
+Through the **Orders module**, you can also download the financial report and view the invoice details and the approved revenue.
+
+For more information, read the articles [What does VTEX consider as revenues for invoice calculation?](https://help.vtex.com/en/tutorial/what-does-vtex-consider-as-revenue-in-the-billing-calculation--58j4cfoXfisWyemASACwSq) and [Understanding the value of approved revenues](https://help.vtex.com/en/tutorial/understanding-the-value-of-approved-revenues--tutorials_4322).
+
+## Changing the account details
+
+After the [first access](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz), you can change the store details, such as:
+
+- Changing and adding contacts.
+- Transferring responsibility.
+- Changing the account's ID document.
+
+To make these changes, you need to [open a ticket to billing support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#financial), indicating the type of change you need.
+
+<div class = "alert alert-info">
+For more information on how to request an SLA verification and the discounts granted for SLA violations, read the <a href="https://help.vtex.com/en/tutorial/how-to-request-sla-verification--3L99VeoLhYEwMqqkWKu86i">How to request a platform SLA verification? </a>
+</div>
diff --git a/docs/tracks/en/canceling-an-order.md b/docs/tracks/en/canceling-an-order.md
index a906882a1..cd93e9dfe 100644
--- a/docs/tracks/en/canceling-an-order.md
+++ b/docs/tracks/en/canceling-an-order.md
@@ -3,8 +3,8 @@ title: 'Canceling an order'
 id: 4ts2ItvjYo8wm5gg76miS3
 status: PUBLISHED
 createdAt: 2019-11-18T11:50:32.691Z
-updatedAt: 2023-03-22T23:28:21.211Z
-publishedAt: 2023-03-22T23:28:21.211Z
+updatedAt: 2024-04-01T18:04:36.603Z
+publishedAt: 2024-04-01T18:04:36.603Z
 firstPublishedAt: 2019-11-18T12:20:50.741Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -20,10 +20,14 @@ You can cancel an order with VTEX in three different ways:
 - Following the customer's request.
 
 <div class="alert alert-warning">
-Once an order is canceled, you cannot change its status. Orders that have <b>invoiced</b> status can not be cancelled.
+Once an order is canceled, you cannot change its status. Orders that have <b>invoiced</b> status can not be canceled.
 </div>
 
-## Cancellation through **Orders** module
+<div class = "alert alert-info">
+Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
+</div>
+
+## Cancellation through Orders module
 
 1. In the VTEX Admin, go to **Orders > All Orders**, or type **All Orders** in the search bar at the top of the page.
 2. Click the desired order.
diff --git a/docs/tracks/en/cart-transfer-and-capture.md b/docs/tracks/en/cart-transfer-and-capture.md
index 510ac2b5e..72265934a 100644
--- a/docs/tracks/en/cart-transfer-and-capture.md
+++ b/docs/tracks/en/cart-transfer-and-capture.md
@@ -20,11 +20,11 @@ VTEX Sales App allows you to [enable the cart transfer functionality](https://he
 
 For the sales associate to share a cart, they can generate a numeric code or a QR Code. To do this, while on the cart screen, just click on the __Transfer__ button. See an example in the image below.
 
-![24. Enable cart transfer between devices - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
 
 When they click this button, the app shows a QR Code and a four-digit numeric code.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Another sales associate logged into the same store can then capture that cart and continue selling from their device.
 
@@ -34,7 +34,7 @@ To capture a cart, enter the VTEX Sales App main menu and click on `Capture Cart
 
 Alternatively, on the app's home screen, the sales associate can slide the screen to the right. When they drag the screen to the right, they will see the __Cart Capture__ option, as shown in the image below.
 
-![24. Enable cart transfer between devices - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
 
 On this screen, they can capture a cart using one of three methods:
 
diff --git a/docs/tracks/en/cart-transfer.md b/docs/tracks/en/cart-transfer.md
index 8835c903e..d3c2f0b2c 100644
--- a/docs/tracks/en/cart-transfer.md
+++ b/docs/tracks/en/cart-transfer.md
@@ -31,14 +31,14 @@ window.INSTORE_CONFIG = {
 
 When making this change, you should notice that two polyesters appear at the bottom of the inStore ID page:
 
-![01 inStore slider transferencia](https://images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
+![01 inStore slider transferencia](//images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
 
 When dragging the screen to the side you will see the screen for __ "Capture Cart" __:
 
-![02 inStore capturar carrinho](https://images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
+![02 inStore capturar carrinho](//images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
 
 In it it is possible to capture a cart by the code of the cart, QR code or even by seller.
 
 In order to generate a QR code or code from a cart you must use the __ "Transfer" option __ in the inStore cart:
 
-![03 inStore transferir](https://images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
+![03 inStore transferir](//images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
diff --git a/docs/tracks/en/catalog-architecture.md b/docs/tracks/en/catalog-architecture.md
index fc99c3234..95a5c0a20 100644
--- a/docs/tracks/en/catalog-architecture.md
+++ b/docs/tracks/en/catalog-architecture.md
@@ -35,4 +35,4 @@ Such specifications are, for example, a product's composition or an SKU's voltag
 
 An example of a VTEX Catalog architecture blueprint is found below:
 
-![arquitetura-catalogo-EN](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
+![arquitetura-catalogo-EN](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
diff --git a/docs/tracks/en/catalog-concept-definition.md b/docs/tracks/en/catalog-concept-definition.md
index 201814760..958fdc2d5 100644
--- a/docs/tracks/en/catalog-concept-definition.md
+++ b/docs/tracks/en/catalog-concept-definition.md
@@ -16,7 +16,7 @@ trackSlugEN: catalog-101
 
 The **Catalog** menu contains the features related to the product assortment of your ecommerce store. In order for your customer to see the products on the website, you need to add them to this Admin menu first.
 
-![visao-geral-produto-EN](https://images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/be0aec115746ca9494e44e3f120983ed/image.png)
+![visao-geral-produto-EN](//images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/be0aec115746ca9494e44e3f120983ed/image.png)
 
 The **Catalog** section enables the setup of capabilities related to the assortment of ecommerce products, such as their categories, brands, and collections, for example. To sell your products, you must add them in this section.
 
diff --git a/docs/tracks/en/centauro-marketplace.md b/docs/tracks/en/centauro-marketplace.md
index 8589efe96..5674c5d4e 100644
--- a/docs/tracks/en/centauro-marketplace.md
+++ b/docs/tracks/en/centauro-marketplace.md
@@ -3,8 +3,8 @@ title: 'Centauro Marketplace'
 id: 5HXEYuDGxv7hNVUma3PKPC
 status: PUBLISHED
 createdAt: 2020-10-20T14:22:13.423Z
-updatedAt: 2021-03-22T15:41:41.809Z
-publishedAt: 2021-03-22T15:41:41.809Z
+updatedAt: 2023-09-22T20:08:49.350Z
+publishedAt: 2023-09-22T20:08:49.350Z
 firstPublishedAt: 2020-10-20T14:23:14.172Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/changing-the-instore-language.md b/docs/tracks/en/changing-the-instore-language.md
index 5ca03c9c0..abf7d42ef 100644
--- a/docs/tracks/en/changing-the-instore-language.md
+++ b/docs/tracks/en/changing-the-instore-language.md
@@ -80,4 +80,4 @@ After making the code change, save the file `checkout-instore-custom.js`.
 
 Then, in the inStore application, to see the reflected changes, enter the menu and click the __Reset app local data__ button, as shown in the image below.
 
-![22. Change the inStore language - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/7qVSATLXP6DBktXwwWsE0H/72515ce67429eaf6334a3cd1288e3884/22._Change_the_inStore_language_-_1_-_EN.png_h_250)
+![22. Change the inStore language - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/7qVSATLXP6DBktXwwWsE0H/72515ce67429eaf6334a3cd1288e3884/22._Change_the_inStore_language_-_1_-_EN.png_h_250)
diff --git a/docs/tracks/en/cms-vtex-io.md b/docs/tracks/en/cms-vtex-io.md
index 54474ac7a..79fdb500b 100644
--- a/docs/tracks/en/cms-vtex-io.md
+++ b/docs/tracks/en/cms-vtex-io.md
@@ -28,19 +28,19 @@ Configure the [store’s binding](https://help.vtex.com/en/tutorial/what-is-cms-
 
 Binding is the process to link your website to a store. For more details , please refer to the article [Linking a store to a folder structure in CMS (binding)](https://help.vtex.com/en/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![CMS - Sites and channels EN](https://images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/73e1c8e48c93825b917c547c624ff8de/cms-sites-and-channels-en.png)
+![CMS - Sites and channels EN](//images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/73e1c8e48c93825b917c547c624ff8de/cms-sites-and-channels-en.png)
 
 ## Pages
 In **[Pages](https://help.vtex.com/en/tutorial/pages-overview--5iBUUJbK5NqG6OxlDrGNzc)**, create a new URL and link it to a template already defined in your [Store theme code](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-4-configuringtemplates).
 
-![CMS - Pages](https://images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/0e439bd649959c6b451120e21fb95f75/cms-pages-en.png)
+![CMS - Pages](//images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/0e439bd649959c6b451120e21fb95f75/cms-pages-en.png)
 
 Also, this section contains the **Redirects** page, which redirects users and search engines from one URL to a more relevant or similar one. 
 
 ## Site Editor
 The **[Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1)** is a graphical interface for managing your storefront content. It allows you to create, edit, publish, and schedule changes in your storefront components and behavior.
 
-![CMS - Site Editor EN](https://images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/223fd5b5913716fa5d972779a2ee90ce/cms-siteeditor-en.png)
+![CMS - Site Editor EN](//images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/223fd5b5913716fa5d972779a2ee90ce/cms-siteeditor-en.png)
 
 ## Styles
 
@@ -50,12 +50,12 @@ The **[Styles](https://help.vtex.com/en/tutorial/styles-overview--v0Db5ohEKSFIkT
   This feature only works in <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-creating-a-production-workspace">production workspaces</a>.
 </div>
 
-![CMS - Styles](https://images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/7922d221d3e07ae06655f6f99a8b9882/cms-styles-en.png)
+![CMS - Styles](//images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/7922d221d3e07ae06655f6f99a8b9882/cms-styles-en.png)
 
 ## Store
 The **[Store](https://help.vtex.com/en/tutorial/cms-loja-visao-geral--3Eat287G6wUi6Mly5rW5Fs)** section is responsible for SEO configurations, performance optimization flags, and enabling PWA push notifications in your store.
 
-![CMS - Store](https://images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/11c316fb6a30988b9db10be80defa05d/cms-store-en.png)
+![CMS - Store](//images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/11c316fb6a30988b9db10be80defa05d/cms-store-en.png)
 
 ## References
 - [Concepts - VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6loFGF4nXvgIVIzsyyJA5c#concepts)
diff --git a/docs/tracks/en/commercial-support.md b/docs/tracks/en/commercial-support.md
new file mode 100644
index 000000000..4cb63237f
--- /dev/null
+++ b/docs/tracks/en/commercial-support.md
@@ -0,0 +1,35 @@
+---
+title: 'Commercial support'
+id: 3KQWGgkPOwbFTPfBxL7YwZ
+status: PUBLISHED
+createdAt: 2024-02-20T21:44:41.944Z
+updatedAt: 2024-02-22T14:08:28.702Z
+publishedAt: 2024-02-22T14:08:28.702Z
+firstPublishedAt: 2024-02-22T14:08:28.702Z
+contentType: trackArticle
+productTeam: Others
+slug: commercial-support
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+Besides the resources provided in the initial agreement with VTEX, you can purchase solutions and activate other features to expand your business operation. To do so, commercial support will guide you on:
+
+- Requesting an [additional trade policy](#requesting-an-additional-trade-policy), [additional environment](#requesting-a-new-environment), and franchise account.
+- Changing the [Sponsor user](https://help.vtex.com/en/tutorial/what-is-the-sponsor-user--3oPr7YuIkEYqUGmEqIMSEy).
+- Requesting [add-on solutions](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+
+You can [open a commercial support ticket](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#financial) if you need support with other topics or buy an add-on solution. Start by exploring the [Help Center](https://help.vtex.com/en/) articles and checking the sections below.
+
+## Requesting an additional trade policy
+
+[Trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) define the sales conditions and strategies for a sales channel, such as the store itself, marketplaces, physical stores, or B2B models. An operation can have a single trade policy or multiple policies; the business model determines the number of trade policies that will be associated with the account.
+
+To decide whether to [request additional trade policies](https://help.vtex.com/en/tutorial/requesting-an-additional-trade-policy--61vuFOw4yGh6nwSmkLJL1X), you need to understand if the account needs an additional or multistore environment. The [Accounts and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) article explains these concepts.
+
+## Requesting a new environment
+
+Only the main account can request new environments, which can be for testing (QA), B2C, B2B, and others. This request is made through [VTEX Support](https://help.vtex.com/en/support).
+
+Depending on your business model and strategy, you may need to request a new environment. To do so, you need to understand multistore and additional environments, as explained in the article [Accounts and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl).
diff --git a/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md b/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md
index dec7b44be..0f4c5e398 100644
--- a/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md
+++ b/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md
@@ -1,10 +1,10 @@
 ---
 title: 'Structure configuration for Live Support'
 id: SxhYiiqUJYiQX4CIWxmVE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T15:25:37.553Z
-updatedAt: 2023-04-27T15:32:38.909Z
-publishedAt: 2023-04-27T15:32:38.909Z
+updatedAt: 2024-01-05T17:14:19.560Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:47:18.082Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/en/configure-customer-identification.md b/docs/tracks/en/configure-customer-identification.md
index e1e4bd0bb..bfb18e1a7 100644
--- a/docs/tracks/en/configure-customer-identification.md
+++ b/docs/tracks/en/configure-customer-identification.md
@@ -26,11 +26,11 @@ To choose which identification methods you want to enable, access the VTEX admin
 
 In the __Customer's login__ box, you must select the identification methods you want to enable.
 
-![21. Configure client identification - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3E5pzs9HJLG8lt2MhxU8ej/962eaa1511cc39f933da2a5c94c97974/21._Configure_client_identification_-_1_-_EN.png_h_250)
+![21. Configure client identification - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3E5pzs9HJLG8lt2MhxU8ej/962eaa1511cc39f933da2a5c94c97974/21._Configure_client_identification_-_1_-_EN.png_h_250)
 
 You can also change the order of these methods. To do this, just drag them, as shown in the image below. The order of the methods defined on this screen determines the order in which they will appear to the salespeople in the app. Therefore, the first method will be the default.
 
-![21. Configure client identification - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6qpyKGeKGdLBckP50im7px/1a5b927292b28a85114c01195212d501/21._Configure_client_identification_-_2_-_EN.png_h_250)
+![21. Configure client identification - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6qpyKGeKGdLBckP50im7px/1a5b927292b28a85114c01195212d501/21._Configure_client_identification_-_2_-_EN.png_h_250)
 
 ## Enabling Anonymous User
 
@@ -38,7 +38,7 @@ It is possible to use the inStore to cater customers anonymously, that is, witho
 
 For this, still in the Customer Identification screen, you need to enable the __Anonymous user__ flag.
 
-![21. Configure client identification - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3MpFYKg99z1oW1w0ZPzCbN/2d6da3c24fa44ec72ed3cb385c49f96c/21._Configure_client_identification_-_3_-_EN.png_h_250)
+![21. Configure client identification - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3MpFYKg99z1oW1w0ZPzCbN/2d6da3c24fa44ec72ed3cb385c49f96c/21._Configure_client_identification_-_3_-_EN.png_h_250)
 
 ## Legal Entity Registration for B2B sales
 
@@ -50,10 +50,10 @@ You can then choose whether these fields are mandatory or optional.
 
 In the example below, the Legal Entity registration is activated and configured as optional.
 
-![21. Configure client identification - 4 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2bf1NMJMXF9JHnM67mFI2s/2c342420c8705dd137048a6ac6edee17/21._Configure_client_identification_-_4_-_EN.png_h_250)
+![21. Configure client identification - 4 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2bf1NMJMXF9JHnM67mFI2s/2c342420c8705dd137048a6ac6edee17/21._Configure_client_identification_-_4_-_EN.png_h_250)
 
 In this case, the application will show the salespeople a form like the one below:
 
-![21. Configure client identification - 5.png?h=250](https://images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/47968bd2948a339e964f5057b251b5f1/21._Configure_client_identification_-_5.png_h_250)
+![21. Configure client identification - 5.png?h=250](//images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/47968bd2948a339e964f5057b251b5f1/21._Configure_client_identification_-_5.png_h_250)
 
 Note that a flag is displayed that allows the salesperson to decide whether to show these additional fields or not. This is because, in the settings, we marked the legal entity registration fields as optional. If they are marked as mandatory, this flag will not show on the app.
diff --git a/docs/tracks/en/configure-integration-of-pick-up-points.md b/docs/tracks/en/configure-integration-of-pick-up-points.md
index 42c7c13bd..ecdd91f03 100644
--- a/docs/tracks/en/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/en/configure-integration-of-pick-up-points.md
@@ -1,16 +1,16 @@
 ---
 title: 'Configure integration of pick-up points '
 id: 52C1lm8gMovN8v68s6v89d
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-08-12T18:12:20.076Z
-updatedAt: 2021-09-08T17:52:30.570Z
-publishedAt: 2021-09-08T17:52:30.570Z
+updatedAt: 2024-03-11T22:19:05.610Z
+publishedAt: 
 firstPublishedAt: 2021-08-19T15:16:01.224Z
 contentType: trackArticle
 productTeam: Channels
 slug: configure-integration-of-pick-up-points
 locale: en
-trackId: 2YfvI3Jxe0CGIKoWIGQEIq
+trackId: 
 trackSlugEN: mercado-libre-integration-set-up
 ---
 
diff --git a/docs/tracks/en/configure-integration.md b/docs/tracks/en/configure-integration.md
index ae8b946f3..04db9a220 100644
--- a/docs/tracks/en/configure-integration.md
+++ b/docs/tracks/en/configure-integration.md
@@ -3,8 +3,8 @@ title: 'Configure integration'
 id: 3tZ4qVuMDDsC2jx2DCmjdA
 status: PUBLISHED
 createdAt: 2021-03-16T20:17:00.970Z
-updatedAt: 2022-09-06T22:49:30.916Z
-publishedAt: 2022-09-06T22:49:30.916Z
+updatedAt: 2024-07-26T19:06:41.787Z
+publishedAt: 2024-07-26T19:06:41.787Z
 firstPublishedAt: 2021-03-18T20:12:33.299Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,5 +14,4 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugEN: magazine-luiza-integration-set-up
 ---
 
-<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
-English speaking countries.</div>
+<div class="alert alert-warning">This is a regional exclusive content not applicable to English speaking countries.</div>
diff --git a/docs/tracks/en/configure-warranty-in-via-varejo.md b/docs/tracks/en/configure-warranty-in-via-varejo.md
index be24aee7b..c18e900ce 100644
--- a/docs/tracks/en/configure-warranty-in-via-varejo.md
+++ b/docs/tracks/en/configure-warranty-in-via-varejo.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configure warranty in Via Varejo'
+title: 'Configure warranty in Casas Bahia Marketplace'
 id: 3FFcVmL5Aod6tkFIz9vJmX
 status: PUBLISHED
 createdAt: 2020-10-01T19:13:10.864Z
-updatedAt: 2022-01-24T20:11:25.306Z
-publishedAt: 2022-01-24T20:11:25.306Z
+updatedAt: 2023-11-30T21:39:33.028Z
+publishedAt: 2023-11-30T21:39:33.028Z
 firstPublishedAt: 2020-10-01T20:32:16.599Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-a-payment-condition.md b/docs/tracks/en/configuring-a-payment-condition.md
index 4dc3d2b3b..ae4abc9c3 100644
--- a/docs/tracks/en/configuring-a-payment-condition.md
+++ b/docs/tracks/en/configuring-a-payment-condition.md
@@ -3,8 +3,8 @@ title: 'Configuring a payment condition'
 id: 6bzGxlz4inf8sKmvZ1c7i3
 status: PUBLISHED
 createdAt: 2019-11-26T17:47:27.426Z
-updatedAt: 2023-03-21T20:02:36.184Z
-publishedAt: 2023-03-21T20:02:36.184Z
+updatedAt: 2024-03-13T21:42:43.233Z
+publishedAt: 2024-03-13T21:42:43.233Z
 firstPublishedAt: 2019-11-26T20:43:48.321Z
 contentType: trackArticle
 productTeam: Financial
@@ -27,17 +27,18 @@ Payment conditions are rules that must be followed by a person who wants to buy
 That said, we can move on to configuring the payment conditions.
 
 ## General Settings
-To configure a payment condition, you must first add an affiliation, as explained in the [Gateway Affiliations](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444) document.
 
-What does not change from one payment method to another is the need to:
-- Define a name for the rule according to what it represents, to help you identify it.
-- Activate it.
-- Define by which gateway affiliation this condition will be processed.
-- Define if you will use [anti-fraud](https://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud--tutorials_446) or not.
+To set up a payment condition, you first need to register a payment provider, as described in [Register payment and anti-fraud providers](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
 
-In addition, it is possible to define whether the payment will be a prepayment in full or in installments, with or without interest and [special conditions](https://help.vtex.com/en/tutorial/condicoes-especiais--tutorials_456?locale=en "special conditions").
+Regardless of the payment condition to be chosen, the following actions must always be carried out:
+- Define the name of the rule according to what it represents, to help identify it;
+- Activate it;
+- Define which payment provider this condition will be processed by;
+- Define whether or not you will use [anti-fraud](https://help.vtex.com/en/tutorial/como-configurar-antifraude--tutorials_446).
 
-Since the payment method that allows all of these settings is **Credit Card**, follow the steps below for each of these settings.
+Furthermore, for some payment conditions it may be necessary to define whether payment will be made in cash or in installments, with or without interest and [special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+
+As the __Credit Card__ is a payment method that allows you to apply all these features, see below how to configure it:
 
 ## Prepayment in full
 
@@ -51,9 +52,9 @@ That done, follow the instructions:
 4. Choose a credit card brand.
 5. Name the rule in the **Rule Name** field.
 6. Activate the condition in the **Status** field.
-7. In the **Process with affiliation** field, choose the affiliation you configured.
+7. In the **Process with provider** field, choose the previously configured provider.
 8. In the **Prepaid in full or in installments?** field, select the **Prepaid in full** option.
-9. Click on the **Save** button.
+9. Click **Save**.
 
 ## In installments
 
@@ -69,11 +70,11 @@ It is noteworthy that the field **Billing** will only be taken into account for
 4. Choose a credit card brand.
 5. Name the rule in the **Rule Name** field.
 6. Activate the condition in the **Status** field;
-7. In the **Process with affiliation** field, choose the affiliation you configured.
+7. In the **Process with provider** field, choose the previously configured provider.
 8. In the **Prepaid in full or in installments?** field, select the **In installments** option.
 9. Configure the number of sequential or individual installments in the **Total installments** field.
 10. Define a minimum installment to be applied according to the value of each product.
-11. Click on the **Save** button.
+11. Click **Save**.
 
 ### With interest 
 
@@ -85,7 +86,7 @@ If you decide to configure a payment method that accepts installments with inter
 4. Choose a credit card brand.
 5. Name the rule in the **Rule Name** field.
 6. Activate the condition in the **Status** field.
-7. In the **Process with affiliation** field, choose the affiliation you configured.
+7. In the **Process with provider** field, choose the previously configured provider.
 8. In the **Prepaid in full or in installments?** field, select the **In installments** option.
 9. Configure the number of sequential or individual installments in the **Total installments** field.
 10. Define a minimum installment to be applied according to the value of each product.
@@ -93,19 +94,15 @@ If you decide to configure a payment method that accepts installments with inter
 12. Click on the **Set installment rate** button.
 13. Enter the amount of interest you want to apply to each installment.
 14. Click on **Compound interest applied. Change** to choose between compound or simple interest.
-15. Click on the **Save** button.
+15. Click **Save**.
 
 ### Automatic Installment
 The Automatic Installment option allows you to configure the details of the installments directly in the payment provider (outside the VTEX environment).
-To enable this option, select “Yes” in the **Use external installments** field during the [affiliation setup](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444) step.
-
-![automaticinstallment](https://images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/965203e926177f608618ed0048411de6/parcelamentoautomaticous.JPG)
+To enable this option, select “Yes” in the **Use external installments** field during the [provider setup](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444) step.
 
-<div class="alert alert-warning">
-  Currently, only the MercadoPagoV1 affiliation allows the automatic installment function.
-</div>
+![automaticinstallment](//images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/965203e926177f608618ed0048411de6/parcelamentoautomaticous.JPG)
 
-After enabling automatic installment payment on the affiliation, follow these steps:
+After enabling automatic installment payment on the provider, follow these steps:
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. Click on **Payment Conditions**.
@@ -113,9 +110,9 @@ After enabling automatic installment payment on the affiliation, follow these st
 4. Choose a credit card brand.
 5. Name the rule in the **Rule Name** field.
 6. Activate the condition in the **Status** field.
-7. In the **Process with affiliation** field, choose the affiliation you configured.
+7. In the **Process with provider** field, choose the previously configured provider.
 8. If you want to use an anti-fraud system, select the option **Use anti-fraud**.
 9. Select an anti-fraud option. 
 10. In the **Prepaid in full or in installments?** field, select the **Automatic** option.
-11. Click on the **Save** button.
+11. Click **Save**.
 
diff --git a/docs/tracks/en/configuring-banners.md b/docs/tracks/en/configuring-banners.md
index e3c0e40ca..f1e08d116 100644
--- a/docs/tracks/en/configuring-banners.md
+++ b/docs/tracks/en/configuring-banners.md
@@ -3,8 +3,8 @@ title: 'Configuring Banners'
 id: 4ViKEivLJtJsvpaW0aqIQ5
 status: PUBLISHED
 createdAt: 2019-11-27T16:34:24.404Z
-updatedAt: 2023-03-30T21:35:08.898Z
-publishedAt: 2023-03-30T21:35:08.898Z
+updatedAt: 2024-01-30T21:59:49.330Z
+publishedAt: 2024-01-30T21:59:49.330Z
 firstPublishedAt: 2020-03-05T19:58:30.009Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -28,7 +28,7 @@ After configuring the banner, you have to add it to a page on your store. To do
 <p> This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: Multilanguage settings (Beta)</a>.</p>
 </div>
 
-![banner-form-en](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
+![banner-form-en](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
 
 ## Banner fields
 
@@ -51,6 +51,7 @@ To add a banner, the following fields need to be completed:
 * **Start time**: Time when the banner will start being available.
 * **End date**: Date when the banner will stop being available. This allows the administrator to schedule future campaigns, which makes them easier to control.
 * **End time**: Time when the banner will stop being available.
+* **Locales:** Languages to which the banner will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 
 ### Trigger Rules
 
@@ -58,7 +59,7 @@ To add a banner, the following fields need to be completed:
 
 Click <i class="fas-solid fa-link"></i> `Autofill from URL` to add the URL of the search page to the trigger rules that will be applied.
 
-![banner-url-en](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
+![banner-url-en](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
 
 Click <i class="fas fa-plus"></i> `Add condition` to create a rule. Rules can be of two types:
 
diff --git a/docs/tracks/en/configuring-cash-payments-through-instore.md b/docs/tracks/en/configuring-cash-payments-through-instore.md
index 863f62086..06bca64d4 100644
--- a/docs/tracks/en/configuring-cash-payments-through-instore.md
+++ b/docs/tracks/en/configuring-cash-payments-through-instore.md
@@ -35,7 +35,7 @@ Now we will create the payment condition.
 1. Still on the **Settings** page of the **Payments** module in the VTEX Admin, click on the **Payment conditions** tab.
 2. Click on the green button with the `+` icon to add a new condition, as shown below.
 
-![en-add-payment-condition](https://images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/fefd28c063c5572c3dfe2852aac484f5/en-add-payment-condition-1.png)
+![en-add-payment-condition](//images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/fefd28c063c5572c3dfe2852aac484f5/en-add-payment-condition-1.png)
 
 3. In the **Custom payment** section, select the **Cash** option you have created.
 4. Enter a name for this payment condition, change the status to **Active**, and in the **Process with affiliation** field, select the custom payment you created in the previous step.
diff --git a/docs/tracks/en/configuring-dafiti-connector.md b/docs/tracks/en/configuring-dafiti-connector.md
index e4da8b7dc..8154d0edc 100644
--- a/docs/tracks/en/configuring-dafiti-connector.md
+++ b/docs/tracks/en/configuring-dafiti-connector.md
@@ -3,8 +3,8 @@ title: 'Configuring Dafiti connector'
 id: 3PV2OACP2E4O4uOKKW2sMg
 status: PUBLISHED
 createdAt: 2018-09-27T17:57:53.647Z
-updatedAt: 2022-01-25T15:51:13.004Z
-publishedAt: 2022-01-25T15:51:13.004Z
+updatedAt: 2024-07-02T19:17:57.983Z
+publishedAt: 2024-07-02T19:17:57.983Z
 firstPublishedAt: 2018-09-27T20:41:13.133Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-livelo-price-divergence-rule.md b/docs/tracks/en/configuring-livelo-price-divergence-rule.md
new file mode 100644
index 000000000..ad1c1d8a1
--- /dev/null
+++ b/docs/tracks/en/configuring-livelo-price-divergence-rule.md
@@ -0,0 +1,18 @@
+---
+title: 'Configuring Livelo Price Divergence rule'
+id: 4kocvdsHiLcLLcX6eQIVmD
+status: PUBLISHED
+createdAt: 2023-08-10T22:45:01.497Z
+updatedAt: 2024-02-19T19:09:00.244Z
+publishedAt: 2024-02-19T19:09:00.244Z
+firstPublishedAt: 2023-08-11T01:56:55.359Z
+contentType: trackArticle
+productTeam: Channels
+slug: configuring-livelo-price-divergence-rule
+locale: en
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugEN: livelo-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/configuring-login-with-facebook.md b/docs/tracks/en/configuring-login-with-facebook.md
index b810f509e..69b9198df 100644
--- a/docs/tracks/en/configuring-login-with-facebook.md
+++ b/docs/tracks/en/configuring-login-with-facebook.md
@@ -28,7 +28,7 @@ After configuring the Facebook registration, you need to configure this login op
 1. In the **Account Settings** module, click on the **Authentications** tab.
 2. Click on the **Edit** button corresponding to Facebook.
 3. Fill in the fields with the _Client Id_ and _Client Secret_ registered on **Facebook**.
-    ![Facebook OAuth EN](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/06b29f9c839316df31c736a315ba1786/facebook_EN.png)
+    ![Facebook OAuth EN](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/06b29f9c839316df31c736a315ba1786/facebook_EN.png)
 4. Click on the **Save** button.
 5. To confirm that your login was successful, go to the front-end of your store and click on **Login**. 
 6. The configured login options will be shown. Click on the **Facebook** option and check if your store name is displayed.
diff --git a/docs/tracks/en/configuring-login-with-google.md b/docs/tracks/en/configuring-login-with-google.md
index 5ce00dba7..e7dc96ec6 100644
--- a/docs/tracks/en/configuring-login-with-google.md
+++ b/docs/tracks/en/configuring-login-with-google.md
@@ -29,7 +29,7 @@ After configuring your Google identity platform, you need to configure your logi
 1. In the **Account Settings** module, click on the **Authentication** tab.
 2. Click on the **Edit** button corresponding to Google.
 3. Fill in the fields with the _Client Id_ and _Client Secret_ added to **Google**.
-    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
+    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
 4. Click on the **Save** button.
 5. To confirm whether your login was successfully configured, access the front-end of your store and click on **Login**.
 6. The configured login options will be shown. Click on the **Google** option and check whether your store name is displayed.
diff --git a/docs/tracks/en/configuring-merchandising-rules.md b/docs/tracks/en/configuring-merchandising-rules.md
index e828526a2..16790e8f3 100644
--- a/docs/tracks/en/configuring-merchandising-rules.md
+++ b/docs/tracks/en/configuring-merchandising-rules.md
@@ -3,8 +3,8 @@ title: 'Creating merchandising rules - Manual Editor'
 id: 2FpbarYzsnbg7aZZn3TGF8
 status: PUBLISHED
 createdAt: 2020-04-14T14:10:24.518Z
-updatedAt: 2023-04-03T22:07:36.546Z
-publishedAt: 2023-04-03T22:07:36.546Z
+updatedAt: 2024-01-29T16:58:41.850Z
+publishedAt: 2024-01-29T16:58:41.850Z
 firstPublishedAt: 2020-04-15T00:39:30.807Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -23,8 +23,8 @@ Follow the steps below to configure a [merchandising rule](https://help.vtex.com
    * **Rule name**: Name of the merchandising rule. Example: Promote product A when searching for a chocolate cookie.
    * **Start date (optional)**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
    * **End date (optional)**: Set a date on which the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
-   * **Locales:** Languages to which the merchandising rule will apply.
-5. Click **Manual Editor**. For more information about each editor, go to [Types of editing](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#types-of-editing).
+   * **Apply to locales:** Languages to which the merchandising rule will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Click on **Manual editor**. For more information on each editor, see [Types of editing](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#types-of-editing).
 6. Click `Next`.
 7. If necessary, you can change what you have already filled in about the new merchandising rule in the [General Information](#general-information) section.
 8. Define the [Trigger rules](#trigger-rules), the set of conditions that determine when the merchandising rule will be applied.
@@ -36,6 +36,8 @@ Follow the steps below to configure a [merchandising rule](https://help.vtex.com
   <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
 </div>
 
+## Example
+
 Imagine the following example: You want to promote Beautyx products during the 4th of July week. When the customer searches for "soap" or "shampoo", the search should promote the brand's products, so the configuration should be:
 
 * **Rule name**: 4th of July promotion
diff --git a/docs/tracks/en/configuring-payment-connectors.md b/docs/tracks/en/configuring-payment-connectors.md
index d3b8a5ef9..cc305f4a0 100644
--- a/docs/tracks/en/configuring-payment-connectors.md
+++ b/docs/tracks/en/configuring-payment-connectors.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configuring payment connectors'
+title: 'Configuring payment providers'
 id: 7pAEMAo4iqNHwYOarZ3zgm
 status: PUBLISHED
 createdAt: 2019-11-12T17:29:10.501Z
-updatedAt: 2023-03-21T20:10:49.512Z
-publishedAt: 2023-03-21T20:10:49.512Z
+updatedAt: 2024-07-29T14:50:02.445Z
+publishedAt: 2024-07-29T14:50:02.445Z
 firstPublishedAt: 2019-11-24T21:05:50.533Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,33 +14,19 @@ trackId: 6GAS7ZzGAm7AGoEAwDbwJG
 trackSlugEN: payments
 ---
 
-The **Payments** module allows you to configure a number of **connectors**, which are the communication protocols that your store uses to enable data transmission with acquirers, sub-acquirers or gateways.
+The __Payments__ module allows several payment providers (gateways, acquirers, sub-acquirers, [orchestrators](https://www.y.uno/br), [PSPs](https://en.wikipedia.org/wiki/Payment_service_provider), among others) to be configured in your store. This way, you can offer different payment methods and conditions to your customers.
 
-For your website to offer customers a certain payment method, you need to enable the **connector** that will communicate with the gateway responsible for processing.
+When a purchase is made in your store and the customer makes payment, data transmission between VTEX and the chosen provider occurs through communication protocols configured in the VTEX Admin.
 
-Another important feature is the connections parity. Just as a payment method can communicate with multiple connectors, a connector can establish communication with multiple payment methods. Because of this possibility, you must configure the connector through **gateway affiliations**.
+<div class="alert alert-info">
+  To check which payment providers are available in your region and the respective settings articles, visit <a href="https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp">List of payment providers by country</a>.</p>
+</div>
 
-**Gateway affiliations** is a set of configurations that represents your contract with a payment gateway.
+Below is an example of how to set up a payment provider:
 
-In addition to payment gateways, other affiliations include promissory, acquirers and sub-acquirers, for example. This allows you to decide which payment gateways will process the different types of transactions in your VTEX store.
-
-The VTEX Payments Module supports multiple affiliations with one or more Payment Gateways of your choice to process different payment methods.
-
-There are two ways to start accepting credit card payments:
-- Affiliate with a payment gateway by Admin.
-- Use [VTEX integrations](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-guide) with payment methods.
-
-## How to add gateway affiliations through Admin
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Click on the **Gateway Affiliations** option.
-3. Click on the **+** button to add a new affiliation.
-4. Choose your Payment Gateway.
-5. Name your affiliation.
-6. If an alert message appears indicating the need to install the app, click on the **Install app** button and follow the installation instructions. This message is only displayed for some types of gateway affiliations. 
-7. Fill in the available fields with the contract data sent by the chosen Gateway.
-8. Click on the **Save** button.
-
-This connector must be associated with a payment condition. For more information and examples of how to receive installment or cash payments with different affiliations, read our article about [Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455).
-
-If you want to check out the step by step of a specific connector, visit our [Tutorials & Solutions](https://help.vtex.com/en/tutorial/--531cHtUCUi3puRXNDmKziw) articles and search for the desired keyword.
+1. In the VTEX Admin, go to __Store Settings > Payments > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New provider` button.
+3. Type the desired payment provider in the search bar and click on its name.
+4. Fill in the available fields according to information from the payment provider with which you have a contract.
+5. Click `Save`.
 
diff --git a/docs/tracks/en/configuring-physical-stores-as-pickup-points.md b/docs/tracks/en/configuring-physical-stores-as-pickup-points.md
index 55522f1a6..c82800d27 100644
--- a/docs/tracks/en/configuring-physical-stores-as-pickup-points.md
+++ b/docs/tracks/en/configuring-physical-stores-as-pickup-points.md
@@ -3,8 +3,8 @@ title: 'Physical stores as pickup points'
 id: 4hXfgqXxS1lwAfnxgja3xW
 status: PUBLISHED
 createdAt: 2021-08-23T17:04:37.282Z
-updatedAt: 2023-05-31T14:45:23.483Z
-publishedAt: 2023-05-31T14:45:23.483Z
+updatedAt: 2023-07-26T18:51:23.201Z
+publishedAt: 2023-07-26T18:51:23.201Z
 firstPublishedAt: 2021-08-23T17:12:50.884Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/en/configuring-price-divergence-rule-dafiti.md b/docs/tracks/en/configuring-price-divergence-rule-dafiti.md
index b43f0a92c..c15e2d2e1 100644
--- a/docs/tracks/en/configuring-price-divergence-rule-dafiti.md
+++ b/docs/tracks/en/configuring-price-divergence-rule-dafiti.md
@@ -3,8 +3,8 @@ title: 'Configuring Price Divergence rule'
 id: 4rGMP9mEVOKCZCM71yzxnj
 status: PUBLISHED
 createdAt: 2022-01-05T16:09:05.484Z
-updatedAt: 2022-01-05T16:18:18.655Z
-publishedAt: 2022-01-05T16:18:18.655Z
+updatedAt: 2023-08-11T18:26:09.918Z
+publishedAt: 2023-08-11T18:26:09.918Z
 firstPublishedAt: 2022-01-05T16:11:57.454Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-price-divergence-rule-mercado-libre.md b/docs/tracks/en/configuring-price-divergence-rule-mercado-libre.md
index 3a6c9d0d5..3ac50165c 100644
--- a/docs/tracks/en/configuring-price-divergence-rule-mercado-libre.md
+++ b/docs/tracks/en/configuring-price-divergence-rule-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Configuring Price Divergence rule'
 id: 1ivH7sJoS771wZFMkaFdpt
 status: PUBLISHED
 createdAt: 2022-01-05T16:18:22.558Z
-updatedAt: 2022-01-05T16:22:48.459Z
-publishedAt: 2022-01-05T16:22:48.459Z
+updatedAt: 2024-03-27T20:43:18.424Z
+publishedAt: 2024-03-27T20:43:18.424Z
 firstPublishedAt: 2022-01-05T16:22:48.459Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-price-divergence-rule-via.md b/docs/tracks/en/configuring-price-divergence-rule-via.md
index bf550a5b5..575aa2404 100644
--- a/docs/tracks/en/configuring-price-divergence-rule-via.md
+++ b/docs/tracks/en/configuring-price-divergence-rule-via.md
@@ -3,8 +3,8 @@ title: 'Configuring Price Divergence rule'
 id: 6MeJhODLMCnYwUCe18QjzP
 status: PUBLISHED
 createdAt: 2022-01-05T16:01:03.231Z
-updatedAt: 2022-01-05T16:04:18.518Z
-publishedAt: 2022-01-05T16:04:18.518Z
+updatedAt: 2023-11-30T21:12:36.109Z
+publishedAt: 2023-11-30T21:12:36.109Z
 firstPublishedAt: 2022-01-05T16:04:18.518Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-rappi-price-divergence-rule.md b/docs/tracks/en/configuring-rappi-price-divergence-rule.md
new file mode 100644
index 000000000..7636bec0d
--- /dev/null
+++ b/docs/tracks/en/configuring-rappi-price-divergence-rule.md
@@ -0,0 +1,18 @@
+---
+title: 'Configuring rappi Price Divergence rule '
+id: VoIvBSldeT2A4MuRVMMi1
+status: PUBLISHED
+createdAt: 2024-05-31T20:36:17.323Z
+updatedAt: 2024-05-31T20:51:50.382Z
+publishedAt: 2024-05-31T20:51:50.382Z
+firstPublishedAt: 2024-05-31T20:51:50.382Z
+contentType: trackArticle
+productTeam: Channels
+slug: configuring-rappi-price-divergence-rule
+locale: en
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugEN: rappi-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/configuring-redirect.md b/docs/tracks/en/configuring-redirect.md
index c27f61151..6cafeecf0 100644
--- a/docs/tracks/en/configuring-redirect.md
+++ b/docs/tracks/en/configuring-redirect.md
@@ -3,8 +3,8 @@ title: 'Configuring Redirects'
 id: 4Gd2wLQFbCwTsh8RUDwSoL
 status: PUBLISHED
 createdAt: 2019-11-22T23:40:25.940Z
-updatedAt: 2023-03-30T19:34:08.021Z
-publishedAt: 2023-03-30T19:34:08.021Z
+updatedAt: 2024-06-17T12:20:22.176Z
+publishedAt: 2024-06-17T12:20:22.176Z
 firstPublishedAt: 2019-11-25T17:36:44.905Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -26,7 +26,7 @@ To configure a redirect, follow the steps below.
 
 You must fill in the fields below.
 
-![redirecionamentos-adminv4-EN](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
+![redirecionamentos-adminv4-EN](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
 
 ### General information
 
@@ -34,6 +34,7 @@ This section provides the following general information:
 
 - **Name:** name of the rule set for the redirect you created.
 - **Redirect URL**: URL to which the client will be forwarded. You must enter the full URL. Example: `https://www.store.com/_secure/account/#/orders` instead of `_secure/account/#/orders`.
+- **Locales:** Languages to which the redirect will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 
 ### Trigger rules
 
@@ -43,7 +44,7 @@ Select the type of rule, either by term or by filter.
 
 - **Term:** word searched by the customer that will be related to the rule. You can choose between two options:
     - `is`: the search must be an exact word search. Example: if you enter "Black Friday" and the customer searches for "Black Friday", the redirect will be triggered. If they search for "Black Friday promotion", the redirect will not be triggered.
-    - `contains`: the search does not have to be an exact word search. Example: if you enter "Black Friday" and the customer searches for "Black Friday", the redirect will be triggered. `If they search for "Black Friday promotion", the rule will not be triggered.`
+    - `contains`: the search does not have to be an exact word search. Example: if you enter "Black Friday" and the customer searches for "Black Friday", the redirect will be triggered. If the customer searches for "Black Friday promotion", it will also be activated.
 - **Filter:** searchable attribute already defined that restricts the search results. Selecting a registered filter enables the redirection created. Customers can choose from two filter options:
     - `is`: this option allows the customer to select not only the filter for the rule. Example: if the rule is ``is``: Filter _brand_, value _Nike_. The redirect is triggered even if the customer also selects adidas.
     - `only`: this option allows only the configured filter to be selected. Example: if the rule is ``only``: Filter _brand_, value _Nike_. If the customer selects adidas, the redirect will not be triggered. It will only work if the first brand filter is Nike.
diff --git a/docs/tracks/en/configuring-ship-from-store.md b/docs/tracks/en/configuring-ship-from-store.md
index dee845b2d..000906140 100644
--- a/docs/tracks/en/configuring-ship-from-store.md
+++ b/docs/tracks/en/configuring-ship-from-store.md
@@ -3,8 +3,8 @@ title: 'Ship From Store'
 id: 50GAmxxFsJoLWqcnMysWdl
 status: PUBLISHED
 createdAt: 2020-06-30T21:36:43.926Z
-updatedAt: 2023-05-31T14:45:10.189Z
-publishedAt: 2023-05-31T14:45:10.189Z
+updatedAt: 2023-07-26T18:44:48.356Z
+publishedAt: 2023-07-26T18:44:48.356Z
 firstPublishedAt: 2020-06-30T21:45:36.187Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,11 +16,11 @@ trackSlugEN: unified-commerce-strategies
 
 The **Ship From Store** strategy allows a customer who wants to receive the products at home to receive them from the warehouse of a physical store. In other words, in this scenario, the store functions as a mini distribution center.
 
-![35. Setting up Shipping From Store - 1](https://images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
+![35. Setting up Shipping From Store - 1](//images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
 
 This type of logistics helps your operation to reduce costs and shipping time. Instead of having only the main warehouses - usually away from the central areas of cities - you now have a more capillary delivery network.
 
-Consider this example: a customer who is at homeplaces an order on the e-commerce and wants to receive the products at home. Let's say you have a physical store in their neighborhood, 500 meters from the customer's home. If the store has the products they ordered in their local inventory, the Shipping From Store strategy allows these products to be shipped to the customer from that store - at a lower cost for you and with a better delivery time for the customer.
+Consider this example: a customer who is at homeplaces an order on the ecommerce and wants to receive the products at home. Let's say you have a physical store in their neighborhood, 500 meters from the customer's home. If the store has the products they ordered in their local inventory, the Shipping From Store strategy allows these products to be shipped to the customer from that store - at a lower cost for you and with a better delivery time for the customer.
 
 ## Prerequisites
 
diff --git a/docs/tracks/en/configuring-synonyms.md b/docs/tracks/en/configuring-synonyms.md
index d412f856a..8890a00d0 100644
--- a/docs/tracks/en/configuring-synonyms.md
+++ b/docs/tracks/en/configuring-synonyms.md
@@ -3,8 +3,8 @@ title: 'Configuring Synonyms'
 id: 3ExbC3QKNF4zH7Gs8jD1cL
 status: PUBLISHED
 createdAt: 2019-11-29T12:04:33.557Z
-updatedAt: 2023-03-30T19:19:37.658Z
-publishedAt: 2023-03-30T19:19:37.658Z
+updatedAt: 2024-01-30T22:46:15.605Z
+publishedAt: 2024-01-30T22:46:15.605Z
 firstPublishedAt: 2020-03-05T19:56:02.826Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,8 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
+<div class = "alert alert-info"> We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Synonyms</a> instead of <a href="https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Substitute Words</a> to associate words with products, as synonyms allow you to manage terms per product in a more scalable way. Contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a> for more information.</div>
+
 There are two ways to set up synonyms in VTEX Admin: [individually](#creating-synonyms-individually) or by [importing a spreadsheet in CSV format](#importing-csv-spreadsheet). If you need to register synonyms in bulk, we recommend using the spreadsheet. See the instructions for each configuration form in the following sections.
 
 The configuration of synonyms works recursively. This means that when you add a second synonym to an existing one, it will also become a synonym for the first one.
@@ -32,6 +34,7 @@ Follow the step-by-step procedure to configure synonyms individually in the VTEX
 4. Fill in the fields that correspond to the synonym:
    - __Type:__ defines the type of synonym. Check [Types of synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#types-of-synonyms) for more information.
    - __Terms:__ words or expressions to be defined as synonyms. You must press `Enter` after each term to insert another term.
+   - **Locales:** Languages to which the synonym will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
    - __Status:__ defines whether the synonym will be active or inactive.
 5. To finish, click on `Save`.
 
@@ -43,9 +46,22 @@ Changes can take up to two hours to take effect.
 
 ## Importing CSV spreadsheet
 
-In case there are many synonyms to be added, you can make a .csv file and import it in the Admin. The file must contain the following format, according to the [types of synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#types-of-synonyms) chosen:
+In case there are many synonyms to be added, you can make a .csv file and import it in the Admin.
+
+To import the file, follow the steps below:
+
+1. Create a CSV file in the format described on [Synonyms spreadsheet template](#synonyms-spreadsheet-template).
+2. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
+3. Under **Intelligent Search**, click **Synonyms**. 
+4. Click on <i class="fas fa-download"></i> `Import`.
+5. Drag the CSV file into the bounded area or click on `choose a file` to select the file on your device.
+6. Click on `Import`.
 
- - __Unidirectional:__ `{terms separated by comma};{expanded terms separated by comma};{status}`
+### Synonyms spreadsheet template
+
+The file must contain the following format, according to the [types of synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#types-of-synonyms) chosen:
+
+ - __Unidirectional:__ `{terms separated by comma};{equivalent term};{status}`
 
    __Examples:__
 
@@ -59,8 +75,21 @@ In case there are many synonyms to be added, you can make a .csv file and import
     - `tv,television,television set;true`: When searching for any of these terms, the products containing any of them will be returned.
     - `monitor,screen,display;true`: When searching for any of these terms, the products containing any of them will be returned.
 
-To import the file, follow the steps below:
+#### Multilanguage stores (Beta)
+
+Stores using  [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO) must follow the template below to import synonyms for specific locales.
+
+- __Unidirectional__: `{terms separated by comma};{equivalent term};{status};{locales separated by comma}`
+
+   __Example:__
+   - `smartphone;iPhone;true;en-GB`: When searching for smartphone in the English language store (`locale en-GB`), the website will return results for `iphone`. However, when searching for `iphone`, the website will not return results for `smartphone`.
+
+- __Bidirectional__: `{terms separated by comma};{status};{locales separated by comma}`
+
+    __Example:__
+    - `tv,smart tv;true;en-GB`: When searching for one of these terms in the store in English (`locale en-GB`), the search results will return any product that contains one of these terms.
+
+<div class="alert alert-warning">
+  <p>If the imported .csv file does not have the <code>locale</code>, the synonym will be valid for all languages available in the store.</p>
+</div>
 
-1. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
-2. Under **Intelligent Search**, click **Synonyms**. 
-3. Click on `Import`.
diff --git a/docs/tracks/en/configuring-the-amazon-integration.md b/docs/tracks/en/configuring-the-amazon-integration.md
index a07c73f18..8ac43dca3 100644
--- a/docs/tracks/en/configuring-the-amazon-integration.md
+++ b/docs/tracks/en/configuring-the-amazon-integration.md
@@ -3,8 +3,8 @@ title: 'Configuring the Amazon integration'
 id: 5J9CWPIbYQdAegJJWGsxan
 status: PUBLISHED
 createdAt: 2019-02-28T23:11:28.346Z
-updatedAt: 2022-02-03T23:25:36.883Z
-publishedAt: 2022-02-03T23:25:36.883Z
+updatedAt: 2023-09-22T20:17:01.064Z
+publishedAt: 2023-09-22T20:17:01.064Z
 firstPublishedAt: 2019-02-28T23:12:37.347Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-the-connector-b2w.md b/docs/tracks/en/configuring-the-connector-b2w.md
index 10eb15c81..1d0a2d1ed 100644
--- a/docs/tracks/en/configuring-the-connector-b2w.md
+++ b/docs/tracks/en/configuring-the-connector-b2w.md
@@ -3,8 +3,8 @@ title: 'Configuring the connector'
 id: 40eYElt1qwIqGeIeum2W4M
 status: PUBLISHED
 createdAt: 2018-09-27T22:25:49.315Z
-updatedAt: 2022-09-06T22:53:13.914Z
-publishedAt: 2022-09-06T22:53:13.914Z
+updatedAt: 2024-07-02T19:23:01.065Z
+publishedAt: 2024-07-02T19:23:01.065Z
 firstPublishedAt: 2018-09-27T22:41:30.135Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/configuring-the-connector.md b/docs/tracks/en/configuring-the-connector.md
index c0e375cbc..f460ea251 100644
--- a/docs/tracks/en/configuring-the-connector.md
+++ b/docs/tracks/en/configuring-the-connector.md
@@ -3,8 +3,8 @@ title: 'Configuring the connector'
 id: wWyl0Njxgs5KfXvxYZJrl
 status: PUBLISHED
 createdAt: 2021-04-14T21:01:49.270Z
-updatedAt: 2021-04-15T21:19:06.543Z
-publishedAt: 2021-04-15T21:19:06.543Z
+updatedAt: 2023-10-13T19:52:02.877Z
+publishedAt: 2023-10-13T19:52:02.877Z
 firstPublishedAt: 2021-04-15T17:41:17.442Z
 contentType: trackArticle
 productTeam: Channels
@@ -17,16 +17,16 @@ trackSlugEN: integrating-with-google-shopping
 You must configure the integration with Google Shopping in the Admin. Please follow the instructions below:
 
 1. Access the Admin.
-2. In the Marketplace module, click on `Integrations`.
-3. Select `Settings`.
-4. On the Google Shopping card, click on `Integrate`.
-5. Fill in the fields in the modal window (fields marked with an asterisk are mandatory). Then click on the `Save configuration` button. Below you can see a short description of each field to guide you.
+2. In the Marketplace module, click __Marketplace and Integrations.__
+3. In the __Google Shopping__ row, click `Connect`.
+4. Complete the fields displayed on the screen as described below, and then, at the top right of the screen, click `Connect` (the fields with * are required).
 
 - **Integration*:** click _ON_ to enable the integration.
 - **Ignore sending EAN (GTIN):** if you click _ON_, SKUs will be sent without their barcodes. If your product has a barcode, we recommend selecting _OFF_ to include this information in the integration. See the article[ Filling in the EAN field](https://help.vtex.com/en/tutorial/cadastrar-o-codigo-de-barra-dos-skus-para-o-instore--2jkOdRB4XSMG2ke0uUQIKS#cadastrar-o-campo-ean) for further details.
 - **Merchant Id*:** code assigned to your Google Merchant Center profile. It is a numeric sequence that appears in the upper right corner of your screen when you access your account.
-- **Sales Policy***: number of the trade policy that will define the catalog assortment and the price of the items used in the integration.
+- **Trade Policy***: number of the trade policy that will define the catalog assortment and the price of the items used in the integration.
 - **Google Merchant email*:** the email used to create the Google Merchant Center account.
+- **Apply discount to price sent*:** The seller must choose which type of discount they will send to Google Shopping, __Do not apply__ (sends the price set up on the VTEX platform), __To payment method configured in the Checkout API__ (must be selected if the seller has configured the discount), or, __Biggest discount configured__.
 - **Remove out-of-stock SKUs*:** if you select _OFF_, when a product is out of stock it will appear as unavailable on your Google Shopping feed, instead of being removed from it. If you select _ON_, the SKU temporarily removed for being out of stock will be displayed in the feed again as soon as the inventory is replenished.
 - **Merchant Id (Multi-Client):** this field should only be used when an advanced account is configured in Google Merchant Center. Advanced accounts are designed for the management of multiple sellers and domains on a large scale. You must fill in this field with the code assigned to your advanced account on Google Merchant Center, which can be identified in the same way as the Merchant Id (a numeric sequence in the upper right corner of the screen). See the Google article on how to [convert to an advanced account](https://support.google.com/merchants/answer/188487?hl=en) for more details.
 - **Send price*:** there are two options available — _without unit multiplier_, in which the product is sold by price per unit, and _with unit multiplier,_ when the product is sold by square footage.
diff --git a/docs/tracks/en/configuring-the-integration-rappi.md b/docs/tracks/en/configuring-the-integration-rappi.md
new file mode 100644
index 000000000..a4b7dd059
--- /dev/null
+++ b/docs/tracks/en/configuring-the-integration-rappi.md
@@ -0,0 +1,18 @@
+---
+title: 'Configuring the integration'
+id: 1SowuK4iQngOHebFMfizYY
+status: PUBLISHED
+createdAt: 2024-05-31T20:32:15.901Z
+updatedAt: 2024-05-31T20:51:41.392Z
+publishedAt: 2024-05-31T20:51:41.392Z
+firstPublishedAt: 2024-05-31T20:51:41.392Z
+contentType: trackArticle
+productTeam: Channels
+slug: configuring-the-integration-rappi
+locale: en
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugEN: rappi-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 823fbd33f..5a6190101 100644
--- a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -3,8 +3,8 @@ title: 'Configuring the integration with FBE in the VTEX Admin'
 id: jUtgjBDumr5oGWIU7mVLC
 status: PUBLISHED
 createdAt: 2021-09-30T16:07:29.101Z
-updatedAt: 2021-10-05T21:36:44.675Z
-publishedAt: 2021-10-05T21:36:44.675Z
+updatedAt: 2024-04-17T14:57:04.600Z
+publishedAt: 2024-04-17T14:57:04.600Z
 firstPublishedAt: 2021-09-30T18:49:18.739Z
 contentType: trackArticle
 productTeam: Channels
@@ -40,7 +40,7 @@ For the integration to work properly, we recommended that you grant all the perm
 10. Click on `Next`.
 11. In the pop-up window, a confirmation that the integration has been configured will be displayed. Click on `Done`.
 
-![gif_en_v1](https://drive.google.com/uc?export=download&id=1oijFLsjBALxOBWy0Vieem2s6a8vKHR1g)
+![gif en v1](//images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/6eec11fdae6edb9afd05f70a1814b248/gif_en_v1.gif)
 
 ## Sending product information to Facebook Business Extension
 
diff --git a/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index a172c25a3..7c0a6bc7f 100644
--- a/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -82,7 +82,7 @@ After completing the integration configuration form, you need to connect your Ti
 
 On the **Set Up TikTok for Business page**, as illustrated below, please follow the configuration instructions described next.
 
-![set-up-tiktok-for-business](https://images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
+![set-up-tiktok-for-business](//images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
 
 1. Click the __TikTok for Business Account__ section and check if your account is listed.
     * If you want to connect another account, click `Disconnect` and repeat the login step described in [Connecting the TikTok account](#2-connecting-the-tiktok-account).
diff --git a/docs/tracks/en/configuring-the-integration.md b/docs/tracks/en/configuring-the-integration.md
new file mode 100644
index 000000000..56bcdd096
--- /dev/null
+++ b/docs/tracks/en/configuring-the-integration.md
@@ -0,0 +1,18 @@
+---
+title: 'Configuring the integration'
+id: HgIbZEzbPr8FQid5MXURQ
+status: PUBLISHED
+createdAt: 2023-08-10T22:33:03.150Z
+updatedAt: 2024-07-26T18:36:22.560Z
+publishedAt: 2024-07-26T18:36:22.560Z
+firstPublishedAt: 2023-08-11T01:56:55.389Z
+contentType: trackArticle
+productTeam: Channels
+slug: configuring-the-integration
+locale: en
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugEN: livelo-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/configuring-the-relevance-feature.md b/docs/tracks/en/configuring-the-relevance-feature.md
index 85c2409c8..595050da1 100644
--- a/docs/tracks/en/configuring-the-relevance-feature.md
+++ b/docs/tracks/en/configuring-the-relevance-feature.md
@@ -34,7 +34,7 @@ The page is divided into two sections: __Priority criteria__ and __Criteria comp
   <li><b>Catalog Score:</b> 3</li>
 </ul>
 
-![default priority criteria EN](https://images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/398cdb38b52d775d9fe9058ace66fdf2/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_18.png)
+![default priority criteria EN](//images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/398cdb38b52d775d9fe9058ace66fdf2/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_18.png)
 
 To change Relevance settings, follow the steps below.
 
@@ -42,7 +42,7 @@ To change Relevance settings, follow the steps below.
 2. Click on __Relevance settings__.
 3. Choose the criterion whose weight you want to change.
 4. Drag the slider to choose its weight, as shown in the image below.
-  ![composicao-criterios-en](https://images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/4ab581d6ffbed81312d9d853dc79f917/composicao-criterios-en.gif)
+  ![composicao-criterios-en](//images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/4ab581d6ffbed81312d9d853dc79f917/composicao-criterios-en.gif)
   If you want to change a criterion from __Criteria composition__ to __Priority criteria__, click on the <i class="fas fa-bars"></i> icon and drag it to the Priority criteria block at the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight.
-  ![priority-criteria-en](https://images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/e81fd3673b90c0a48d166712f6017bdf/priority-criteria-en.gif)
+  ![priority-criteria-en](//images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/e81fd3673b90c0a48d166712f6017bdf/priority-criteria-en.gif)
 5. Click on __Save__.
diff --git a/docs/tracks/en/contract-termination.md b/docs/tracks/en/contract-termination.md
new file mode 100644
index 000000000..a27c90293
--- /dev/null
+++ b/docs/tracks/en/contract-termination.md
@@ -0,0 +1,22 @@
+---
+title: 'Contract termination'
+id: 3TUpFItxp8L1WZAD1JuYfF
+status: PUBLISHED
+createdAt: 2024-02-20T21:47:12.450Z
+updatedAt: 2024-02-22T14:08:21.680Z
+publishedAt: 2024-02-22T14:08:21.680Z
+firstPublishedAt: 2024-02-22T14:08:21.680Z
+contentType: trackArticle
+productTeam: Others
+slug: contract-termination
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+VTEX regrets a client's decision to withdraw and understands that the needs and circumstances of business partners can change. Although we regret the decision to terminate a contract, VTEX is committed to making this process as simple and transparent as possible to ensure a smooth transition.
+
+To terminate a contract with VTEX, you must contact [billing support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#financial). As for Brazil, Argentina, and Colombia, you must follow the guidelines in the following articles:
+
+- [Requesting contract termination in Brazil](https://help.vtex.com/pt/tutorial/como-solicitar-sua-rescisao-contratual-no-brasil--frequentlyAskedQuestions_1834)
+- [Requesting contract termination in Argentina and Colombia](https://help.vtex.com/es/tutorial/solicitar-la-rescision-contractual-en-argentina-y-colombia--33g6mUoYB9Mf04C06gSU0a)
diff --git a/docs/tracks/en/corporate-digital-account.md b/docs/tracks/en/corporate-digital-account.md
index ac07dab51..14c1eb662 100644
--- a/docs/tracks/en/corporate-digital-account.md
+++ b/docs/tracks/en/corporate-digital-account.md
@@ -1,10 +1,10 @@
 ---
 title: 'Corporate digital account'
 id: 3MVAuZJenHAEt8jsgX99GD
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T17:37:52.588Z
-updatedAt: 2023-03-14T22:07:22.796Z
-publishedAt: 2023-03-14T22:07:22.796Z
+updatedAt: 2023-10-05T14:13:52.213Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:48:20.683Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/en/create-brands.md b/docs/tracks/en/create-brands.md
index c617da332..fc9de5bc2 100644
--- a/docs/tracks/en/create-brands.md
+++ b/docs/tracks/en/create-brands.md
@@ -38,7 +38,7 @@ Information that is filled out can be updated at any time using the Catalog modu
 
 To delete a brand entry, click the arrow next to `Edit` and then click `Delete`.
 
-![editar-marca EN](https://images.ctfassets.net/alneenqid6w5/lAOk9EHq8WLoXs6SnrXsv/55b9ba52f46ae8582315ffda359a3b39/editar-marca_EN.png)
+![editar-marca EN](//images.ctfassets.net/alneenqid6w5/lAOk9EHq8WLoXs6SnrXsv/55b9ba52f46ae8582315ffda359a3b39/editar-marca_EN.png)
 
 ## API
 
diff --git a/docs/tracks/en/create-product-feed.md b/docs/tracks/en/create-product-feed.md
index 3ee708a77..554a4b243 100644
--- a/docs/tracks/en/create-product-feed.md
+++ b/docs/tracks/en/create-product-feed.md
@@ -28,11 +28,11 @@ To make product updates available to Lengow, you must [configure an XML feed](ht
 
 - **File Name:** `lengow.xml`
 - **Collection:** `Lengow` (or another name you chose)
-- **Show Unavailable SKUs:** <img src="https:https://images.ctfassets.net/alneenqid6w5/3tqaZgkyGMFRCdDIpQoU4v/ae419a4f9ff8c73c32964bcc8d3391f9/image3.png"/> (enabled)
+- **Show Unavailable SKUs:** <img src="https://images.ctfassets.net/alneenqid6w5/3tqaZgkyGMFRCdDIpQoU4v/ae419a4f9ff8c73c32964bcc8d3391f9/image3.png"/> (enabled)
 
 The feed itself should then be filled in as seen in the image below:
 
-![image2](https://images.ctfassets.net/alneenqid6w5/2TuXQFVWgd7liQ7jSxYHDu/c46858cd6a536d3f3290bafe2e105724/image2.png)
+![image2](//images.ctfassets.net/alneenqid6w5/2TuXQFVWgd7liQ7jSxYHDu/c46858cd6a536d3f3290bafe2e105724/image2.png)
 
 ## Verify XML feed consistency
 
@@ -42,7 +42,7 @@ Your product feed should now be available at the following URL:
 
 If you visit this URL in your browser, you should see an XML document tree like this:
 
-![image8](https://images.ctfassets.net/alneenqid6w5/7fBOjuxHDkRYtIoLPSnJcp/038cfb985ae364a3af5068ed5f69e489/image8.png)
+![image8](//images.ctfassets.net/alneenqid6w5/7fBOjuxHDkRYtIoLPSnJcp/038cfb985ae364a3af5068ed5f69e489/image8.png)
 
 The numbers seen in the XML feed correspond to the Product ID for all products in the collection you created for the Lengow connector.
 
diff --git a/docs/tracks/en/creating-accounts.md b/docs/tracks/en/creating-accounts.md
index 533e3b2c0..8abc3f5a8 100644
--- a/docs/tracks/en/creating-accounts.md
+++ b/docs/tracks/en/creating-accounts.md
@@ -3,8 +3,8 @@ title: 'Creating Customer Credit accounts'
 id: 7FHLd0cmxqqGeEUuc8uioU
 status: PUBLISHED
 createdAt: 2018-11-06T20:24:28.924Z
-updatedAt: 2023-05-12T12:20:09.076Z
-publishedAt: 2023-05-12T12:20:09.076Z
+updatedAt: 2024-02-08T19:08:32.443Z
+publishedAt: 2024-02-08T19:08:32.443Z
 firstPublishedAt: 2018-11-06T21:15:02.053Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,103 +14,82 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugEN: customer-credit-getting-started
 ---
 
-The next step is to create accounts for the customers you want to offer credit to your store.
+The next step is to create accounts for the customers you want to offer credit to in your store. Accounts can be created in three different ways:
 
-There are three ways to create them:
-
-- Via Admin;
-- Through the bulk import feature;
-- Via API.
+- [Individual account (Admin VTEX)](#create-accounts-individually)
+- [Multiple Accounts (Admin VTEX)](#create-multiple-accounts-bulk-import)
+- [Individual account (Customer Credit API)](#criar-conta-via-api)
 
 <div class="alert alert-info">
-<strong>Warning</strong>: Customer Credit accounts are not integrated with the customer base registered in Master Data entities. Accounts must be created in the app before or after the user has concluded in-store purchases.
+Accounts created in the Customer Credit app have no relationship or share data with the customer base registered in the store's <a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#data-entities">Master Data entities</a>. For a customer to be able to use Customer Credit as a payment method, their account must be registered by the merchant in the app even if the customer already has an account in the store. 
 </div>
 
-In addition, in all cases where users choose to update data by importing a spreadsheet into the system, it is necessary to make sure that all values are separated by commas. Otherwise, the operation will not be completed correctly.
-
-See how to create accounts in these three possible ways:
-
-## Creating accounts individually
+## Create accounts individually
 
-If users prefer, they can create multiple accounts manually through Admin.
+To register a new customer in Customer Credit, follow the steps below:
 
-Follow the step by step:
+1. In the VTEX Admin, access __Apps > Customer Credit > Accounts__, or type __Accounts__ in the search bar at the top of the page.
+2. On the __Accounts__ screen, click the `NEW` button.
+3. In __Identification__, select the __Document type__ and fill in the __Document__ and __Email__ fields with the information of the customer you want to register.
+4. In __Credit__, enter the __Credit Limit (BRL)__ and __Tolerance__ values that you want to make available to the customer.
+5. Click `Confirm`.
 
-1. Access the __Admin__;
-2. Click on the __Customer Credit__ module;
-3. Then click on __Accounts__;
-4. On the right side of the screen, click on the __“New”__ button;
-5. Select the __document type__ that will identify the account;
-6. Enter the document number in the __Document__ field;
-7. Fill in the __Email__ field;
-8. Set the __credit limit__ for the account;
-9. Click on the __"Confirm"__ button.
-
-Filling in the email field in the form is mandatory, because through the email (access key to the VTEX system), it is possible to authenticate the customer's access to the credit limits of an account. For more information about data protection, visit [SmartCheckout Security](https://help.vtex.com/en/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB).
-
-This way, the new account will be displayed on the main page of the “Accounts” section.
+<div class="alert alert-warning">
+Filling in the <b>Email</b> field is mandatory, as the VTEX platform uses this information to authenticate the customer's access to the credit limits of their account. For more information about data protection, visit <a href="https://help.vtex.com/en/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB">SmartCheckout Security</a>.
+</div>
 
-## Creating accounts via bulk import
+From this moment on, the new account created will be displayed on the __Accounts__ screen.
 
-To create accounts in bulk, users can use the CSV (comma-separated value, a spreadsheet format) file import feature. 
+![CC_new_account_1_EN](//images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/29c36c044a54c156d6dbf4d385da0dee/CC_new_account_1_EN.JPG)
 
-This functionality is very useful as it makes it possible to import thousands of accounts into the system at once.
+## Create multiple accounts (bulk import)
 
-1. Access the __Admin__;
-2. Click on the __Customer Credit__ module;
-3. Then click on __Accounts__;
-4. Next to the “New” button, click on __Import__ option;
-5. Select the __Create__ option;
-6. Click on the __"Continue"__ button;
-7. Then click on the __Download template__ option.
+To create multiple accounts at the same time (in bulk) in Customer Credit, you can use a template spreadsheet in CSV (Comma Separated Value) format containing each customer's information. Follow the steps below to create multiple accounts:
 
-This way, your computer will download a spreadsheet template in CSV format. You can find it in the Downloads folder.
+1. In the VTEX Admin, access __Apps > Customer Credit > Accounts__, or type __Accounts__ in the search bar at the top of the page.
+2. On the __Accounts__ screen, click the `IMPORT` button.
+3. In __Do you want to create or update accounts?__, select the __Create__ option and click `CONTINUE`.
+4. Click on `DOWNLOAD TEMPLATE`. A spreadsheet template in .csv format will be sent to your device (computer, cell phone or tablet).
+5. Fill in each line:
+<br>
+<ul>
+  <li>Columns <b>Email</b>, <b>Document</b> and <b>Document Type</b>: customer information.</li>
+  <li>Columns <b>Credit limit</b> and <b>Tolerance rate</b>: values available to each customer. The <b>Tolerance rate</b> must be entered in decimal format, for example, a tolerance of 5% must be indicated as 0.05.</li>
+</ul>
 
-The next step is to fill in the columns listed in the document with the information for each of the accounts you want to create.
+![CC_criar_conta_2_ALL](//images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
 
-The table has 13 columns, but the email column is the only required, since VTEX’s system uses this information to identify users in SmartCheckout.
+<blockquote><ui>6. Save the .csv spreadsheet.</ui>
 
-When you finish filling out the table and save the changes, proceed with the walkthrough:
+<blockquote><ui>7. Return to the <b>Accounts</b> screen and click the <b>IMPORT</b> button again.</ui>
 
-1. Return to the __Accounts__ section in the Admin;
-2. Click on the __Import__ option;
-3. Select the __Update__ option inside the box;
-4. Click on the __"Continue"__ button;
-5. Insert the spreadsheet in the space __“Drop the CSV here or choose file”__;
-6. Click on the __"Import file"__ button.
+<blockquote><ui>8. In <b>Do you want to create or update accounts?</b>, select the <b>Update</b> option and click <b>CONTINUE</b>.</ui>
 
-Done! Your accounts will be created and displayed on the Accounts section main page.
+<blockquote><ui>9. Insert or select the .csv spreadsheet in the space <b>Drop your CSV here or choose a file</b>.</ui>
 
-In the context of creating new accounts, you can check your import history. To do this, click on “Import history” on the main page of the Accounts section. This way, it is also possible to check if the imports were done correctly. Otherwise, the necessary corrections will be indicated in the interface.
+<blockquote><ui>10. Click on the <b>IMPORT FILE</b> button.</ui>
 
-### Updating Accounts via bulk import
-You can also update all your accounts’ data - email, credit limit, document, document type, status and tolerance - at once using the bulk import feature.
+From this moment on, new accounts created via the .csv spreadsheet will be available on the __Accounts__ screen.
 
-The process is similar to creating accounts. However, here it is assumed that you already have the CSV file template downloaded on your machine.
+<div class="alert alert-warning">
+It is also possible to track previous processes of creating multiple accounts, identifying whether the accounts were created correctly. To check this information, click on <b>Import History</b> on the <b>Accounts</b> screen.
+</div>  
 
-Follow the step by step:
+### Update multiple accounts (bulk import)
 
-1. Access the __Admin__;
-2. Click on the __Customer Credit__ module;
-3. Then click on __Accounts__;
-4. Next to the “New” button, click on the __Import__ option;
-5. Select the __Update__ option;
-6. Click on the __"Continue"__ button;
-7. Insert the updated CSV file into the *Drop Zone*;
-8. Click on the __"Import File"__ button.
+To update information, such as document, document type, email, credit limit and tolerance, in multiple accounts at the same time, you can also use the bulk import functionality.
 
-Finally, wait for the spreadsheet to be uploaded.
+The procedure is similar to [create multiple accounts](#create-multiple-accounts-bulk-import). However, you must already have the .csv spreadsheet downloaded and filled out on your device (computer, cell phone or tablet). Follow the steps below to update customer information: 
 
-## Creating accounts through API
-Another option is to create accounts through the `POST Open or Change Account` [endpoint](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-accountId- "endpoint").
+1. In the VTEX Admin, access __Apps > Customer Credit > Accounts__, or type __Accounts__ in the search bar at the top of the page.
+2. On the __Accounts__ screen, click the `IMPORT` button.
+3. In __Do you want to create or update accounts?__, select the __Update__ option and click `CONTINUE`.
+4. Insert or select the .csv spreadsheet in the space __Drop your CSV here or choose a file__ here.
+5. Click on the IMPORT FILE button.
+6. After the spreadsheet is loaded into Admin, check on the __Accounts__ screen whether the information was updated correctly in each customer's accounts.  
 
-Fill in the body with the following information:
+## Create account via API
 
-     {
-      "id": "id",
-      "creditLimit": "number",
-      "document": "CPF or CNPJ or Other",
-      "email": "email"
-    }
+You can also create accounts for your customers in Customer Credit through the endpoint [POST - Open an account](https://developers.vtex.com/docs/api-reference/customer-credit-api#post-/api/ creditcontrol/accounts).
 
-For more details, see our [technical documentation on Customer Credit APIs](https://developers.vtex.com/docs/guides/customer-credit-api-overview "technical documentation on Customer Credit API.").
+For more information about Customer Credit API endpoints, visit [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api#overview).  
diff --git a/docs/tracks/en/creating-and-editing-users.md b/docs/tracks/en/creating-and-editing-users.md
index 8deeefcae..4fd4cf7e0 100644
--- a/docs/tracks/en/creating-and-editing-users.md
+++ b/docs/tracks/en/creating-and-editing-users.md
@@ -3,8 +3,8 @@ title: 'Creating and editing users'
 id: 5enE0a0glnI0coEj7rRHBA
 status: PUBLISHED
 createdAt: 2019-11-22T15:16:38.307Z
-updatedAt: 2022-08-24T14:23:48.018Z
-publishedAt: 2022-08-24T14:23:48.018Z
+updatedAt: 2024-06-17T15:10:57.072Z
+publishedAt: 2024-06-17T15:10:57.072Z
 firstPublishedAt: 2020-01-13T14:33:11.563Z
 contentType: trackArticle
 productTeam: Identity
@@ -23,7 +23,7 @@ This is where we register the users that can access the administrative environme
 1. In the Account Management module, click on the **Users** tab.
 2. Click on the **New User** button.
 3. Enter the **Email** and **Full name**.
-4. Add or create the [roles](https://help.vtex.com/tutorial/configuring-access-profiles--tutorials_526) you want.
+4. Add or create the [roles](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) you want.
 5. Click on the **Save** button.
 
 The user will receive an email confirming the registration, with a link to create a password.
diff --git a/docs/tracks/en/creating-merchandising-rules-visual-editor.md b/docs/tracks/en/creating-merchandising-rules-visual-editor.md
new file mode 100644
index 000000000..6dc45ffb2
--- /dev/null
+++ b/docs/tracks/en/creating-merchandising-rules-visual-editor.md
@@ -0,0 +1,98 @@
+---
+title: 'Creating merchandising rules - Visual Editor'
+id: 2ejly01m1w28RsZlCKowEr
+status: PUBLISHED
+createdAt: 2024-01-29T17:01:20.082Z
+updatedAt: 2024-02-01T13:22:55.562Z
+publishedAt: 2024-02-01T13:22:55.562Z
+firstPublishedAt: 2024-01-29T17:04:11.061Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: creating-merchandising-rules-visual-editor
+locale: en
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugEN: vtex-intelligent-search
+---
+
+To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) using [Visual Editor](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), follow the steps below.
+
+1.	In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2.	Under **Intelligent Search**, click **Merchandising Rules**.
+3.	Click the `+ New` button.
+4.	Complete the following fields:
+
+	* **Rule name**: Merchandising rule name. Example: Promote product A when searching for a chocolate cookie.
+	* **Start date (optional)**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
+	* **End date (optional)**: Set a date when the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
+	* **Apply to locales:** Languages to which the merchandising rule will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5.	Click **Visual Editor**. Read the [Types of editing](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao) section for more information about each editor.
+6.	Click `Next`.
+7.	Define at least one search term or filter for applying the merchandising rule:
+
+	* To define a search term, type the term in the search bar (item **II** in the  [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section).
+	* To create a filter for applying the merchandising rule (item **III** in the  [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section), follow the steps described in the[ Adding filters and conditions](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes) section.
+8.	You can also perform the following additional actions to customize the search results.
+
+	* Define the number of items per row in the search results.
+	* Define the number of items per page in the search results.
+	* Hide products in the search results.
+	* Pin products to the top positions of the search results.
+	* Drag the pinned product to the desired position in the search results.
+	* Edit the initial settings of the merchandising rule, including the rule name, start and end dates, and the locales to which it will be applied if the store uses the[ Multilanguage settings (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+      Learn more about these actions in items **IV, V, VI, VIII, IX**, and **XI** of the [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section.
+9.	Click `Save`.
+
+<div class="alert alert-info">
+  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
+</div>
+
+## Actions available in the Visual Editor
+
+The Visual Editor for merchandising rules in VTEX Intelligent Search allows you to perform the actions shown in the image below:
+
+![visual-merch-rules-EN-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Edit the name of the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define search terms to apply the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Set <a href="#adding-filters-and-conditions" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filters</a>
+        to apply the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define the number of items per row in the search results.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define the number of items per page in the search results.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Hide products in the search results. Hidden products appear in gray with the crossed-out eye icon <i class="far fa-eye-slash"></i> in the Visual Editor. To display a hidden product again, hover over it and click the eye icon <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">View product details. The information displayed is:<br /><br />
+    	 <ul>
+			   <li class="t-body c-on-base mb5 lh-copy"><strong>Available:</strong> Indicates whether the product is available in the store.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Clicks:</strong> Number of clicks over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Orders:</strong> Number of orders containing the product that were placed over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Revenue:</strong> Revenue the product represented over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Launch date:</strong> Date on which the product was launched.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Promotion:</strong> Indicates whether the product participates in a promotion.</li> 
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Discount:</strong> Discount applied to the product.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Available matrix variety:</strong> Represents the percentage of SKUs available for a product. For example, if a product has five SKUs and only three are available, the available matrix variety will be 60%, represented as 0.6 in this field. If all the SKUs are available, the field value will be 1.</li>
+		    </ul>
+	    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Drag the pinned product to the desired position in the search results. You can only drag pinned products (action <strong>IX</strong> in this list).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Pin products to the top positions of the search results. By pinning product A and then product B, they will appear in this order in the search results, just before the others. To pin a product, hover over it and click the pin-crossed icon <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navigate between search result pages.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Cancel editing.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Save settings.</li>
+</ol>
+
+### Adding filters and conditions
+
+Filters are predefined selectable attributes that narrow the search results, such as filtering for all products in a category or brand, among other conditions. You can add one or more conditions to a filter.
+
+To add a condition using the Visual Editor, follow the steps below.
+
+1. Click `Filter`.
+2. Click `+ Add condition`.
+3. Fill in the desired conditions. The available options are detailed in [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+4. Click `Save`.
+
+The defined conditions can work together (`and`) or alternatively (`or`).
+
+In the <i class="far fa-ellipsis-v"></i> menu of each existing condition, you can `Duplicate` or `Delete` the condition. To deactivate all created conditions, click `Clear filters`.
diff --git a/docs/tracks/en/creating-or-editing-a-page-template.md b/docs/tracks/en/creating-or-editing-a-page-template.md
index 54bb7013d..f79b467e6 100644
--- a/docs/tracks/en/creating-or-editing-a-page-template.md
+++ b/docs/tracks/en/creating-or-editing-a-page-template.md
@@ -42,9 +42,9 @@ Check out the walk-through:
 </ul></p>
 </div>
 7. Then fill in the __Template XHTML__ box with your template code. 
-![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 9. Click on the __Save Template__ button.
-![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
+![4 2](//images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
 To edit an existing template, the process is almost identical.
 
diff --git a/docs/tracks/en/creating-regular-promotions.md b/docs/tracks/en/creating-regular-promotions.md
index 538907a9f..d996b4457 100644
--- a/docs/tracks/en/creating-regular-promotions.md
+++ b/docs/tracks/en/creating-regular-promotions.md
@@ -3,8 +3,8 @@ title: 'Creating Regular Promotions'
 id: 7FjbeZdE2KMwk5L1t98pZI
 status: PUBLISHED
 createdAt: 2020-01-14T13:11:35.010Z
-updatedAt: 2022-12-08T19:33:56.600Z
-publishedAt: 2022-12-08T19:33:56.600Z
+updatedAt: 2024-04-22T13:23:15.737Z
+publishedAt: 2024-04-22T13:23:15.737Z
 firstPublishedAt: 2020-01-22T13:55:43.369Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,152 +14,155 @@ trackId: 6asfF1vFYiZgTQtOzwJchR
 trackSlugEN: promotions
 ---
 
-VTEX allows you to [create many types of promotions](https://help.vtex.com/en/tutorial/creating-promotions--tutorials_320#como-criar-promocoes) for different scenarios, but the most used one is the Regular Promotion. It allows your store to offer discounts in a dynamic and flexible way, combining multiple conditions, restrictions and benefits.
-
-In this article, we describe each field in the regular promotion configuration steps listed below.
-
-1. [Promotion overview](#1-promotion-overview)
-    - [Restrict this promotion to products from sellers](#restrict-this-promotion-to-products-from-sellers)
-    - [Trade Policy](#trade-policy)
-2. [To which items will this promotion apply?](#2-to-which-items-will-this-promotion-apply)
-3. [What are the conditions for the promotion to be valid?](#3-what-are-the-conditions-for-the-promotion-to-be-valid)
-4. [Restrictions and limitations of use](#4-restrictions-and-limitations-of-use)
-
-To understand the implementation of promotions, read the article on [Promotion Examples](https://help.vtex.com/en/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD?&utm_source=autocomplete#).
-
-## 1. Promotion overview
-
-In this section, you must configure the general information of your promotion. The fields **Name**, **Expiration date** and **What is the type and amount of discount** are mandatory.
-
-- **Name**: Promotion name.
-- **Status:** Activate or deactivate the promotion.
-- **Description**: Promotion's internal description. This field is used in your store's internal communication to show the promotion's origin (campaign, stock clearance, etc).
-- **Expiration Date:** Promotion's start and end date and time. A future date and/or time can be used to launch the promotion on the website. If configured this way, the promotion will have a scheduled status until the set date and time are reached. As long as the promotion is valid, it will be active and, at the end of the set date and time, the status will change to inactive automatically.
-- **Use recurrence settings**: This option is a checkbox type options that when checked makes seven other checkboxes available to select the days of the week and the hours of the day during which the promotion will apply. If you want the promotion to apply on every day of the week, do not select this option.
-- **What is the type and amount of discount?**: A selection that defines the kind and amount of discount that will apply to the promotion. See the discount options below:
-
-  - **Nominal**: Exact discount to be applied for the total purchase value.
-  - **Nominal shipping**: Exact discount to be applied for the shipping value.
-  - **Percentage**: Percentage discount to be applied for total purchase value.
-  - **Maximum Price per Item**: The maximum price for each item of the purchase will be the price set up.
-  - **Percentage shipping**: Percentage discount to be applied for shipping value. 
-  - **Maximum shipping**: Shipping maximum value. 
-  - **Free Shipping**: 100% discount on shipping value.
-  - **Gift**: Total discount on the product value set as a gift. You can choose more than one SKU as a gift or more than one unit of an SKU. To set more than one gift, select **Activate gift multiplier** and set the maximum selectable quantity.  For more information, read this [article](https://help.vtex.com/en/tutorial/gift-multiplier-in-promotions--1gydgkmjEWcoo2CskUwuYK#).
+On VTEX, you can [create different types of promotions](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) for a range of scenarios, but the most commonly used is the regular promotion. This promotion type allows you to offer flexible discounts, combining multiple conditions, restrictions, and benefits.
+In this article, we'll explain the steps required to set up a regular promotion:
+
+1. [Promotion overview](#promotion-overview)
+   - [Restrict this promotion to seller products](#restrict-this-promotion-to-seller-products)
+   - [Trade policy](#trade-policy)
+2. [To which items will this promotion apply?](#to-which-items-will-this-promotion-apply)
+3. [Conditions for the promotion to be valid](#conditions-for-the-promotion-to-be-valid)
+4. [Restrictions and limitations of use](#restrictions-and-limitations-of-use)
+
+Read our article [Promotion examples](https://help.vtex.com/en/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD?&utm_source=autocomplete) for more information.
+
+## Creating a promotion
+
+To create a regular promotion, follow the steps below:
+
+1. In the VTEX Admin, go to **Promotions > Promotions**, or type **Promotions** in the search bar at the top of the page.
+2. Click the **Create Promotion** button.
+3. Select the **Regular** option.
+4. Complete the promotion fields.
+5. Click **Save**.
+
+# 1. Promotion overview
+
+In this section, you need to configure your promotion's general information. These are required fields: **Name**, **Expiration date**, and **What is the type and amount of discount?**.
+
+- **Name:** Promotion name. Required field.
+- **Status:** Activates or deactivates the promotion.
+- **Description:** An internal description of the promotion. The purpose of this field is to be used as internal communication in your store to indicate whether the promotion comes from a campaign, clearance sale, etc.
+- **Expiration date:** Start and end date and time of the promotion. You can use a future date and/or time for the promotion to start on your website. If configured this way, the promotion status will be displayed as follows:
+  - **Scheduled:** Before the selected start date and time.
+  - **Active:** During the scheduled promotion period.
+  - **Inactive:** After the selected end date and time.
+- **Use recurrence settings:** By selecting this option, you can configure the recurrence, such as the weekday and time.
+- **What is the type and amount of discount?:**  Allows you to select one of the options below:
+  - **Nominal:** Discount applied to the cart total.
+  - **Nominal shipping:** Discount applied to the shipping cost.
+  - **Percentage:** Percentage discount that will be applied to the product price.
+  - **Maximum price per item:** The maximum price for each eligible item will be the price set above.
+  - **Percentage:** Percentage discount that will be applied to the shipping cost.
+  - **Maximum shipping:** Maximum amount for the shipping cost.
+  - **Free shipping:** Full discount on shipping costs.
+  - **Gift:** Full discount on the product amount set as a gift. By selecting this option, you can indicate the SKU (by name or ID) that will be considered a gift, choose if you want to activate the gift multiplier, and the maximum number of products that can be used as gifts in the promotion.
 <div class = "alert alert-info">
-  <p>The gift also needs to have a nominal price, even if it's given for free to the customer.</p>
+The gift product must have a price associated with it, even though it is given to the customer for free.
 </div>
-  - **Nominal discount based on formula**: the discount is calculated based on the a formula that you can create using the products' total price (`total`), shipping fees (`freight`), and quantity of items (`quantity`) as variables. Note that the shipping value in the formula will be the lowest available for the order, regardless of the customer's selection. The decimal separator symbol must always be the decimal point. For example: if the discount is 30% of the total product value + shipping value, the formula should be `(total + freight) * 0.3`. For more information on the formula, read our [documentation](https://help.vtex.com/en/tutorial/regular-promotion-with-nominal-discount-based-on-formula--2Pwrq6THyGViNedQG381jV).
-  - **Nominal reward value**: Nominal value for rewards program. Read [Regular promotion with reward value](https://help.vtex.com/en/tutorial/regular-promotion-with-reward-value--3FCip23ZtvG0sDt0rVGVmR) for more information.
-  - **Percentage reward value**: Percentage value for rewards program. Read [Regular promotion with reward value](https://help.vtex.com/en/tutorial/regular-promotion-with-reward-value--3FCip23ZtvG0sDt0rVGVmR) for more information.
-  - **Promotional price table**: Price table used for promotions. The promotional price of each SKU will be its corresponding value in the selected price table.
 
-- **Promotion is highlighted:** If you select **Yes**, you can insert a flag with the promotion name used in the product's window display and page. This tag will only be added if you use the correct promotion display control in the template: `<vtex.cmc:discountHightLight/>`.
+  - **Nominal discount based on formula:** Discount calculated based on a formula you can create using the product total amount, shipping, and the number of items as variables. Please note that the shipping cost considered by the formula will be the lowest available for the order, regardless of the customer's selection. The decimal separator must always be a period. For example: If the discount is 30% of the product's total amount + shipping cost, the formula should be (total + freight) * 0.3. For more information about the formula, check out our [documentation](https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
+  - **Nominal reward value:** Credit that will be added to the store's reward program. For more information, check out the [Regular promotion with reward value](https://help.vtex.com/en/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) article.
+  - **Percentage reward value:** Percentage credit that will be added to the store's reward program. For more information, check out the [Regular promotion with reward value](https://help.vtex.com/en/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) article.
+  - **Promotional price table:** Price tables can be used as promotions. The promotional price of each SKU will be its corresponding price in the selected price table.
+  - **Additional information (optional):** Allows you to add a name and value to the promotion.
+  - **Promotion is highlighted:** Adds a tag with the promotion name to the window display and the product page. This tag will only be added if you use the right promotion display control in the template `<vtex.cmc:discountHightLight/>`.
 
 <div class = "alert alert-info">
-  <p><b>Nominal</b> promotions will only be displayed in the cart, not on the shelf or product page.</p>
+Nominal promotions will only be displayed in the cart, not in the window display or on the product page.
 </div>
 
-### Restrict this promotion to products from sellers
+## Restrict this promotion to seller products
 
-In this section, you can set which sellers the promotion will apply to as well as determine which ones will be included or excluded from the discount applied. 
+In this section, you can determine to which sellers the promotion will apply. You can specify the sellers you want to include or exclude from the discount.
 
-- **Equal to:** Select the desired sellers' names to include them.
-- **Different from:** Select the desired sellers' names to exclude them.
+- **Equal to:** Select the sellers you want to include.
+- **Different from:** Select the sellers you want to exclude.
 
-To enable a promotion for all sellers, leave the checkbox empty.
+For the promotion to be valid for all sellers, leave the field blank.
 
 <div class = "alert alert-warning">
   <p>You cannot directly select a white label seller. To include a white label seller to the promotion, there are two options:</p><ol>1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.</ol><ol>2. Leave the checkbox empty to include all sellers, meaning that all types of sellers - whether white label or not - will be added to the promotion.</ol>
 </div>
 
-### Trade Policy
+## Trade policy
 
-This section establishes the valid sales policies for the promotion. You can include or exclude sales policies from the discount applied.
+In this section, you can set the trade policies valid for the promotion. You can include or exclude trade policies from the discount.
 
-- **Equal to:** Select the desired sales policies to include.
-- **Different from:** Select the desired sales policies to exclude.
-- **Provided by me (My Store):** Select sales policies which apply to your store's products. More than one sales policy can be selected.
-- **Delivered by me (Other stores):** Selecting sales policies in which your products are from third-party stores. More than one sales policy can be selected.
+- Equal to: Select the trade policies you want to include.
+- Different from: Select the trade policies you want to exclude.
+- Provided by me (my store): Select trade policies with products from your store. You can select more than one trade policy.
+- Delivered by me (other stores): Select trade policies in which your products are available in third-party stores. You can select more than one trade policy.
 
-For the promotion to be valid for all sales policies, leave the checkboxes empty.
+For the promotion to be valid for all trade policies, leave the selection empty.
 
-## 2. To which items will this promotion apply?
+# 2. To which items will this promotion apply?
 
-In this section, you need to choose whether this promotion will apply to all products in your store or only to specific products, as illustrated below.
+In this section, you need to choose whether the promotion will apply to all your store products or only specific products, as detailed below:
 
-![promocoes-restricao-en](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
+- **Apply to all products:** Allows you to apply the promotion to your whole catalog.
+- **Apply to products that meet all of the following restrictions:** Allows you to limit your promotion to specific products. You must satisfy the selection criteria for categories, brands, collections, products, and SKUs.
+- **Products:** Allows you to choose the products to which the promotion will be applied. You can upload a file (.txt) with the product IDs.
+- **SKUs:** Allows you to choose the SKUs to which the promotion will be applied. You can upload a file (.txt) with the product SKUs.
 
-If you want the promotion to apply to your entire catalog, select the **Apply to all products** option.
+You can include or exclude **categories**, **brands**, **collections**, **products**, and **SKUs** from the promotion using the **Equal** to or **Different from** criteria.
 
-To limit your promotion to specific products, select **Apply to the following products** and then fill in the selection criteria for **Categories**, **Brands**, **Collections**, **Products** and **SKUs**.
+To be eligible for the promotion, products must meet all the conditions added in this section.
 
-You can add or remove **Categories**, **Brands**, **Collections**, **Products** and **SKUs** from the promotion using the **Equal to** or **Different from** criteria.
+![A quais itens esta promoção será aplicada - EN](//images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/2b8a18cfaa26f45756354a1a081cd2a0/A_quais_itens_-_EN.png)
 
-See an example below. In this case, the promotion includes all products from the category **Home Appliances** whose brand is **Brastemp**, except the product **Refrigerator 100**.
+# 3. Conditions for the promotion to be valid
 
-![exemplo-en](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
+The order must meet the conditions specified in this section for the promotion to apply.
 
-In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
+- **Order minimum or maximum amount:** The promotion will be applied based on the gross amount of the cart, not considering other promotions or shipping.
+- **Aggregate purchase value:** Discount given if the customer's total purchase amount reaches the specified amount.
+- **Item price between:** The discount will apply if the item price is within the range of values set by the store.
+- **Full price and discounted price are the same or Full price and discounted price are different:** Refers to the added product prices. Only one can be selected.
+- **Use restriction BINs:** Allows you to activate or deactivate the BIN restriction, limiting the credit cards used in the promotion. You can import a list of BINs, which must be saved in a text file (.txt) with each BIN listed on a different row.
+- **Marketing tags:** Used to limit the promotion's activation if the order is placed through the VTEX Subscriptions module.
+- **Affiliates:** Marketplace order identifier. The discount will be applied to the selected affiliates. Check out the What is an affiliate article for more information.
+- **Customer cluster:** The discount will be given if the customer is included in the cluster selected in this field. Note that the cluster name must be identical to the one registered; any misspelling will prevent the configuration from working correctly. For more information, check out the Create a cluster of customers article.
+- **Shipping countries:** The discount will apply to items shipped to the countries selected in this field.
+- **Shipping postal code should:** The discount will apply if the shipping postal code meets the configured rule. Note that postal codes not added will not be valid for the promotion.
+- **Shipping method:** The discount will apply only if the shipping method chosen by the customer is the same as the one specified in the promotion. This criterion will only be considered if the discount refers to the shipping cost, i.e., if it is one of the following: Percentage shipping, Nominal shipping, Maximum shipping, or Free shipping. Note that this configuration cannot be combined with "Only apply discount to the cheapest shipping option", as one option invalidates the other.
+- **Apply the selected discount only when one of the above carriers is selected by the customer:** The promotion will only be applied once the customer has selected the shipping method in question. If it is not selected, it will not be eligible for the discount. This criterion will only be considered if the promotion type refers to the shipping cost, i.e., only if it is one of the following types: Percentage shipping, Nominal shipping, Maximum shipping, or Free shipping.
+- **Payment method:** Allows you to choose if the promotion will be applied to one or more of the selected payment methods.
 
-<div class = "alert alert-warning">
-<p>If you select <strong>Apply to the following products</strong> and do not fill in any selection criteria, the promotion will not be created, and the following message will appear: <strong>Set eligible products or apply to all products</strong>. In this case, go to the previous field and fill in the selection criteria or select <strong>Apply to all products</strong>.</p>
+<div class = "alert alert-info">
+By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact [our Support](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue).
 </div>
 
-Products must meet all the conditions specified in this section to be available in the promotion.
-
-## 3. What are the conditions for the promotion to be valid?
-
-The customer's request must meet the conditions added in this section to be valid in the promotion.
-
-- **Minimum and maximum order value:** The promotion will apply considering the "gross" cart value, without taking other discounts/promotions or shipping into account.
-- **Aggregate value of purchases:** The discount will apply if the total value of all purchases made by the customer reaches the required value.
-- **Item price between:** The discount will apply if the value of the item is within the range of values set by the store.
-- **Price "From" and "to"; prices are the same** or **"from" and "to" prices are different:** Refers to the added product values. Only one can be selected.
-- **Use restriction BINs:** The discount will be granted if the card's BIN is given.
-- **Marketing Tags:** Field used to restrict the activation of the promotion if the purchase is made by the [VTEX Subscription System module](https://help.vtex.com/en/tutorial/how-do-subscriptions-work--frequentlyAskedQuestions_4453#). 
-- **Affiliates:** Marketplace order identifier. The discount will apply to selected affiliates. Read the article on [What is an affiliate](https://help.vtex.com/en/tutorial/what-is-an-affiliate--4bN3e1YarSEammk2yOeMc0?locale=en) for more information.
-- **Customer cluster:** The discount will apply if the client is part of the selected cluster. It is important to stress that the name of the cluster must be the same as the one added; any spelling error will prevent the correct functioning of the configuration.
-- **Shipping countries**: The discount will apply to the selected countries given in this field. 
-- **Shipping to postal code should:** The discount will apply if the postal code follows the configured rule.
-- **Shipping Method:** The discount will be granted if the shipping method is the same as the one given. This criterion is only applicable to shipping discounts, such as Percentage rate discount, Nominal rate discount, Maximum value rate or Free shipping.
-- **Apply the discount only to the cheapest shipping option:** Apply the discount only to the cheapest shipping option: If you enable this option, the shipping discount will be applied only to the cheapest shipping option. This option is already enabled by default, but you can disable it if you want to apply the discount to other shipping options. Read the article [Setting up shipping discounts](https://help.vtex.com/en/tutorial/configurar-promocoes-de-frete--6Lo5BR61KMiUFAAHGCdgfW) for more information. This criterion is only applicable to shipping discounts, such as Percentage rate discount, Nominal rate discount, Maximum value rate or Free shipping.
-- **Apply selected discount only when one of the above carriers is selected by the customer:** The promotion will apply only after the customer has effectively selected the delivery method in question. Until that method is selected, no discount is applied. This criterion is only applicable to shipping discounts, such as Percentage rate discount, Nominal rate discount, Maximum value rate or Free shipping.
-- **Payment method:** The discount will be granted if the payment method selected by the customer is the same as the one given. This discount will only be applied at checkout, when the customer selects the same payment method added for the promotion.
-
- <div class = "alert alert-info">
-  <p> By default, you can add up to 20 payment methods per promotion. In addition, you can include up to 100 payment methods via customization. If you need to use more than 20, contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
- </div>
-
-- **Number of installments:** The discount will apply if the number of installments selected by the customer is less than or equal to the maximum number set.
-
-<div class = "alert alert-warning">
-  <p><b>Warning</b>: Promotions by payment method and number of installments are not valid for orders paid using two cards or gift cards.</p>
+- **Number of installments:** Discount given if the number of installments selected by the customer is within the specified range. This field does not apply to boletos (Brazilian payment method).
+<div class="alert alert-warning">
+Promotions based on payment method and number of installments do not apply to orders paid for with two cards or vouchers.
 </div>
 
-- **Utm\_source:** The discount will apply if browsing is done through the **utm_source** that contains the set value. The customer can only enter one **utm_source** at checkout.
-- **Utm\_campaign:** The discount will apply if browsing is done with the utm_campaign that contains the set value.
-- **Create a new coupon with the UTMs above:** Create a coupon with given UTMs to give the customer access to the promotion without UTMs, simply by using a coupon code.
-- **Utmi\_cp:** The discount will apply if navigation is done with the utmi_cp that contains the set value (case sensitive).
+- **UTM source:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion. Note that the customer can only enter one **utm_source** at checkout.
+- **UTM campaign:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion.
+- **Create a new coupon with the UTMs above:** Creates a coupon from the added UTMs to give customers access to the promotion using just the coupon code, without the need for UTMs.
+- **utmi_cp:** The discount will be given if the customer navigation uses the utmi_cp parameter with the specified value, which is case-sensitive.
 
 <div class = "alert alert-info">
-  <p>The UTMs field must only contain the value that the UTMs will have to have to activate the discount. No need to insert <i>?utm_source=</i> in the field</p>
+In the UTMs field, enter only the value that the UTMs must match to activate the promotion. You don't need to enter ?utm_source= in the field.
 </div>
 
-- **Only if it's a first buy:** The discount will only apply for the customer's first purchase.
-- **Is a subscription order**: Option that defines that the promotion will apply to subscription orders. See the conditions below:
-  - **First orders**: Orders that generate subscriptions but are not yet part of subscription cycles.
-  - **Recurrent orders**: Orders from subscription cycles.
-  - **Filter by**: Selection that filters which subscription orders will be valid for the promotion.
-      - **Frequency**: A selection of the frequency of subscription orders - weekly, monthly and yearly.
-      - **Cycle number**: A selection of the subscription cycles that will be included in the promotion. This option is unlocked only if **Recurring orders** is selected.
+- **Only on first purchase:** The discount will only be given on the customer's first purchase.
+- **Apply the discount even if the user is not logged in?:** This field is available when the Only on first purchase field is selected. If this field is checked, the promotion will be applied even if the customer has not entered their email and password. When unchecked, the promotion will only be applied if the customer has logged in with their email and password.
+- **Is a subscription order:** Allows you to select one of the options below:
+  - **First orders:** Orders that generate subscriptions but are not part of subscription cycles yet.
+  - **Recurring orders:** Orders from subscription cycles.
+  - **Filter by:** Allows you to filter the subscription requests valid for the promotion.
+  - **Frequency:** Select the frequency of subscription orders — weekly, monthly, and annually. For more information, see [Configuring the frequency and date of the subscription cycle](https://help.vtex.com/en/tutorial/como-criar-um-anexo-de-assinatura--2bUuKyPflA8cOGLv8OvaKK).
+  - **Cycle number:** Allows you to select the subscription cycles valid for the promotion. This option is only unlocked if the **Recurring orders** option is selected.
+
+# 4. Restrictions and limitations of use
 
-- **Apply the discount even if the user is not logged in?:** This field is available when the field **Only on the first buy**; is selected. If this field is selected, the promotion will apply even if the consumer has not entered their email and password. If it is not selected, the promotion will only apply if the customer is browsing while logged in with the previously added email and password.
+In this section, you will find important information about the promotion conditions and restrictions.
 
-## 4. Restrictions and limitations of use
+- **How many times will this promotion be applied in your store:** Limits the number of times the promotion will be applied. If you uncheck the unlimited field, the **times** field becomes available to enter the maximum number of times the promotion can be used. This only applies for orders created after the condition has been set up. It will not affect orders placed previously.
+- **How many times per customer will this promotion be applied in your store:** This field's value determines the maximum number of times each customer can benefit from the promotion. For example, if you set a limit of three uses and the promotion is applied three times on a single order, this will be considered a single use in relation to the total limit. This way, the customer can still use the promotion on two different orders. Note that this calculation is done regardless of how many times the promotion has been used on each individual order.
+- **Set maximum number of eligible items for each cart:** Defines the maximum number of items in the cart that will be affected by the promotion. Check out [Restricting promotional products in cart](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#restricting-promotional-products-in-cart) to learn how to configure this field.
+- **Apply with other promotions:** If selected, more than one promotion can be applied simultaneously, regardless of the discount type. Learn more in the [How promotion competition works](https://help.vtex.com/en/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270) article.
+- **Apply with manual prices:** Allows the promotion to apply to products whose prices were manually added via telesales. To enable the manual pricing feature, use the [Update orderForm configuration endpoint](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
 
-- **How many times will your promotion be applied in your store:** Limits how many times the promotion can be applied. When the **unlimited** option is not selected, a field becomes available to set how many times you want the limit to be. Once the promotion is created, this condition will only be applied from the day it was configured, not affecting previous orders.
-- **How many times will your promotion be applied in your store for each client:** This restriction is not related to the global usage of the promotion, but to how many times each customer can receive this promotion. If the field above is also selected, its priority will come before this limit.
-- **Define maximum quantity of affected items by cart**: Sets how many items will be affected by the promotion from those present in the shopping cart. Find out how to configure this field in [this article](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho).
-- **Allow accumulated promotions:** Allows more than one promotion with the same discount type to apply concomitantly. For more information, read our articles on the [competition of promotions](https://help.vtex.com/en/tutorial/about-promotions-competition--tutorials_2270#).
-- **Allow to accumulate with manual prices:** Allows the promotion to apply to products whose prices have been manually added by a call-center operator. To enable manual pricing functionality, use the endpoint [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration).
diff --git a/docs/tracks/en/credit-card-payment-flow.md b/docs/tracks/en/credit-card-payment-flow.md
index e7e65bf62..f372b1b42 100644
--- a/docs/tracks/en/credit-card-payment-flow.md
+++ b/docs/tracks/en/credit-card-payment-flow.md
@@ -1,10 +1,10 @@
 ---
 title: 'Credit card payment flow'
 id: TEYVv2fcVkH7et9n3OnBS
-status: CHANGED
+status: PUBLISHED
 createdAt: 2019-11-12T15:51:05.024Z
-updatedAt: 2020-11-27T19:39:59.301Z
-publishedAt: 2020-02-13T15:38:53.526Z
+updatedAt: 2023-11-01T12:40:40.235Z
+publishedAt: 2023-11-01T12:40:40.235Z
 firstPublishedAt: 2019-11-22T19:30:16.374Z
 contentType: trackArticle
 productTeam: Financial
@@ -24,11 +24,12 @@ The basic flow of a credit card payment is performed by the following players:
 To learn more about the financial agents involved in the payment flow of an order in Brazil, check out [this article](https://help.vtex.com/en/tutorial/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil--1dyPJ3gQCCO4ea2o6OMgCi). <br/>
 <br/>
 
-
 ## Payment Flow
 
 The complete credit card payment flow at VTEX is shown in the following scheme:
 
+![Credit Card - Basic payment flow](//images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/dbee2595f3dda339db8010cb8d00f67d/payments_image1_EN.JPG)
+
 1. On the Checkout screen of your store, the customer chooses the _credit card_ **Payment Method** to complete the purchase.
 
 2. This payment information is passed to the **Payment Gateway**, which is the player responsible for ensuring that this payment is successful.
diff --git a/docs/tracks/en/customer-identification.md b/docs/tracks/en/customer-identification.md
index acae9fce8..bba6eeed5 100644
--- a/docs/tracks/en/customer-identification.md
+++ b/docs/tracks/en/customer-identification.md
@@ -27,7 +27,7 @@ You can [configure which identification methods you want to enable](https://deve
 
 In the example image below, Email and CPF are enabled.
 
-![31. VTEX Sales App - Product Overview - 2 - EN](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99343004a1e70a756f043ea293d5cd24/identify-customer-en.PNG)
+![31. VTEX Sales App - Product Overview - 2 - EN](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99343004a1e70a756f043ea293d5cd24/identify-customer-en.PNG)
 
 Just enter one of these data in the field and click on the `Confirm` button.
 
diff --git a/docs/tracks/en/customizing-instore.md b/docs/tracks/en/customizing-instore.md
index a3a2ce6d6..fc27853da 100644
--- a/docs/tracks/en/customizing-instore.md
+++ b/docs/tracks/en/customizing-instore.md
@@ -3,8 +3,8 @@ title: 'Customizing VTEX Sales App'
 id: Rby973h1l9tEM4C1YrzwZ
 status: PUBLISHED
 createdAt: 2021-09-16T00:55:10.885Z
-updatedAt: 2023-05-31T16:08:29.389Z
-publishedAt: 2023-05-31T16:08:29.389Z
+updatedAt: 2023-07-24T23:04:49.692Z
+publishedAt: 2023-07-24T23:04:49.692Z
 firstPublishedAt: 2021-09-16T01:00:39.153Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugEN: instore-getting-started-and-setting-up
 
 The VTEX Sales App experience is customizable: you can enable specific features and settings to suit your business needs, and you can also adapt the app layout to match your brand identity.
 
-This requires editing JavaScript and CSS files, as described in the [How to customize VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/how-to-customize-instore) developer guide.
+This requires editing JavaScript and CSS files, as described in the [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app) developer guide.
 
 <div class="alert alert-warning">
 <p>Only people with programming experience should customize VTEX Sales App as incorrect changes to these files can cause critical errors.</p>
@@ -24,16 +24,16 @@ This requires editing JavaScript and CSS files, as described in the [How to cust
 
 You can see the available VTEX Sales App customizations below. You can click the name of each customization to access its respective implementation guide.
 
-* [Customize VTEX Sales App login options](https://developers.vtex.com/vtex-rest-api/docs/customize-instore-login-options): allow users to log in to VTEX Sales App using their Google or Facebook account. 
-* [Change VTEX Sales App language](https://developers.vtex.com/vtex-rest-api/docs/change-instore-language): change the VTEX Sales App language to English or Spanish. The default language is Portuguese.
+* [Customize VTEX Sales App login options](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app#list-of-customizations): allow users to log in to VTEX Sales App using their Google or Facebook account. 
+* [Change VTEX Sales App language](https://developers.vtex.com/docs/guides/change-vtex-sales-app-language): change the VTEX Sales App language to English or Spanish. The default language is Portuguese.
 * [Enable the](https://developers.vtex.com/vtex-rest-api/docs/enable-the-remarks-field-in-the-order-screen) **[Observation](https://developers.vtex.com/vtex-rest-api/docs/enable-the-remarks-field-in-the-order-screen)** [field in the order screen](https://developers.vtex.com/vtex-rest-api/docs/enable-the-remarks-field-in-the-order-screen): enable a field to store additional information about the order. The data entered in this field is sent to **Orders Management**.
     * [Enable the sales associate code](https://developers.vtex.com/vtex-rest-api/docs/sales-associate-code): enable the sales associate code, in other words, an additional customization of the Observation field to make it a mandatory field where sales associates need to enter their personal codes during the purchase flow.
 * [Enable cart transfer and capture between devices](https://developers.vtex.com/vtex-rest-api/docs/enable-cart-transfer-between-devices): allow a purchase that was started in one device to be completed in any other device present in the purchase flow without having to add the products to the cart again.  For more information, go to [this article](https://help.vtex.com/pt/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/2hlBqxHlxgFo2o4R52pbsk).
 * [Enable order filter by sales associate](https://developers.vtex.com/vtex-rest-api/docs/enable-order-filter-by-sales-associate): change the default so that the sales associate view only shows the orders completed by them instead of showing all the store orders.
 * [Force stock availability](https://developers.vtex.com/vtex-rest-api/docs/force-stock-availability): allow selling items that are unavailable in the ecommerce stock. By default, if an item is out of stock in the store catalog, it cannot be sold through VTEX Sales App. However, there are situations where the item is available in the physical store. This customization allows processing the sale in those cases.
-* [Set up the order summary printing](https://developers.vtex.com/vtex-rest-api/docs/set-up-the-order-summary-printing): enable printing an order summary when the order is completed through VTEX Sales App.
+* [Set up the order summary printing](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app#list-of-customizations): enable printing an order summary when the order is completed through VTEX Sales App.
     * [Add extra text to the order summary print](https://developers.vtex.com/vtex-rest-api/docs/add-extra-text-to-the-order-print): add a custom text to the order summary printout.
 
 ## Learn more
 
-* [How to customize VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/how-to-customize-instore)
+* [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app)
diff --git a/docs/tracks/en/customizing-styles.md b/docs/tracks/en/customizing-styles.md
index f1727eb3c..051fb7ed6 100644
--- a/docs/tracks/en/customizing-styles.md
+++ b/docs/tracks/en/customizing-styles.md
@@ -48,7 +48,7 @@ Let's make some changes to our `style.json` file. We can change the colors a bit
 
 Now, see the results by `linking` our app:
 
-![style-json](https://images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
+![style-json](//images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
 
 Success! Now you know how to customize your store's styles.
 
@@ -98,4 +98,4 @@ Let’s type some CSS inside, giving us a nice solid red line:
 ```
 Our new category menu will now have a solid red line along the bottom of our menu.
 
-![red-line](https://images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
+![red-line](//images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
diff --git a/docs/tracks/en/customizing-templates.md b/docs/tracks/en/customizing-templates.md
index c97ff86a3..fb103c222 100644
--- a/docs/tracks/en/customizing-templates.md
+++ b/docs/tracks/en/customizing-templates.md
@@ -119,6 +119,6 @@ To add a component to this page, we simply need to declare a new shelf block and
 
 If you save this in `store/blocks.json` and `vtex link` your store, you should see a new shelf rendered when visiting the home.
 
-![shelf](https://images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
+![shelf](//images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
 
 You can customize the blocks declared by the `store-theme` app freely, and also declare new ones yourself. For now, you can find the documentation for each component on their [GitHub repositories](https://github.com/vtex-apps?q=store-components). There, you can find the available properties for each component.
diff --git a/docs/tracks/en/dafiti-marketplace.md b/docs/tracks/en/dafiti-marketplace.md
index fdf7f6703..dab47731f 100644
--- a/docs/tracks/en/dafiti-marketplace.md
+++ b/docs/tracks/en/dafiti-marketplace.md
@@ -3,8 +3,8 @@ title: 'Dafiti marketplace'
 id: 5lAIj7OCqizD5EisLJvatx
 status: PUBLISHED
 createdAt: 2021-05-26T15:09:29.538Z
-updatedAt: 2021-05-26T15:51:04.313Z
-publishedAt: 2021-05-26T15:51:04.313Z
+updatedAt: 2024-06-26T15:28:29.564Z
+publishedAt: 2024-06-26T15:28:29.564Z
 firstPublishedAt: 2021-05-26T15:28:12.852Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/dashboard.md b/docs/tracks/en/dashboard.md
index e9294af36..83e43bbec 100644
--- a/docs/tracks/en/dashboard.md
+++ b/docs/tracks/en/dashboard.md
@@ -1,10 +1,10 @@
 ---
 title: 'Dashboard'
 id: 7vg42kAdhUQeWBzncsSymN
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-01-24T15:01:36.426Z
-updatedAt: 2023-01-26T12:57:04.230Z
-publishedAt: 2023-01-26T12:57:04.230Z
+updatedAt: 2024-01-05T17:14:37.506Z
+publishedAt: 
 firstPublishedAt: 2023-01-25T14:42:22.919Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugEN: conversational-commerce
 
 On the Dashboard page, VTEX store owners have access to metrics from the [VTEX Conversational Commerce](https://help.vtex.com/en/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/1NwwADrU70v3roPUV7dWxI) channel. In this dashboard, you can view the sales performance and session indicators, filter them by period and export them to a CSV file.
 
-![Conversational Commerce Analytics Panel](https://images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/d138299cada7a34e32a0a5189ee1a5f7/Conversational_Commerce_Analytics_Panel_EN.png)
+![Conversational Commerce Analytics Panel](//images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/d138299cada7a34e32a0a5189ee1a5f7/Conversational_Commerce_Analytics_Panel_EN.png)
 
 ## Data
 
diff --git a/docs/tracks/en/data-protection-roles.md b/docs/tracks/en/data-protection-roles.md
new file mode 100644
index 000000000..082007f96
--- /dev/null
+++ b/docs/tracks/en/data-protection-roles.md
@@ -0,0 +1,85 @@
+---
+title: 'Data protection roles'
+id: 5f8hTEw3xOALgqzus9VXKd
+status: PUBLISHED
+createdAt: 2024-05-03T16:42:23.883Z
+updatedAt: 2024-05-03T21:10:00.990Z
+publishedAt: 2024-05-03T21:10:00.990Z
+firstPublishedAt: 2024-05-03T16:58:44.285Z
+contentType: trackArticle
+productTeam: Others
+slug: data-protection-roles
+locale: en
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugEN: data-and-privacy
+---
+
+To guarantee the security and privacy of information, there are different roles in the possession, control, and processing of personal data. In the table below, we explain each role in the data protection ecosystem:
+
+| Role | Description |
+|---|---|
+| Data subject | The data subject is the owner of their personal data. For example, a customer in a store is the owner of their personal data, which they use to make a purchase. |
+| Data controller | The data controller is the person who decides the purposes and criteria for using personal data in compliance with data protection laws. The controller also determines how the processors will use the data. <br><br> For example, a merchant is a data controller, since they decide which customer data is required for placing an order. |
+| Data processor | The processor is a third-party company that processes personal data on behalf of the controller. <br><br> For example, VTEX is the processor that processes end-customer data on behalf of the store. VTEX does not process sensitive end-customer data at its own discretion but only on the direct instructions of the store administrators. <br><br> This processing by VTEX is outlined in the [Data Processing Addendum (DPA)](#data-processing-addendum-dpa). |
+| Data subprocessors | The subprocessor is a third-party company that processes personal data on behalf of the processor. The controller must have visibility and agree with the selection of a subprocessor. <br><br> Infrastructure providers and VTEX affiliates are subprocessors. See the [full list of VTEX subprocessors](https://vtex.com/us-en/privacy-and-agreements/subprocessors/). |
+
+## Data Processing Addendum (DPA)
+
+The _Data Processing Addendum_ (DPA) is the agreement between the data controller (merchant) and the processor (VTEX), which regulates how VTEX processes personal data on behalf of the merchant.
+
+This document is an appendix to the [Master Services Agreement (MSA)](https://vtex.com/us-en/privacy-and-agreements/agreements/), the agreement that regulates the relationship between VTEX and the merchants. It establishes the rules for using the VTEX platform and any other requested services or products.
+
+The DPA follows the [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/) standard, the most restrictive legislation on data privacy.
+
+It includes information on:
+
+* Processor and controller roles.
+* Compliance with the rights of data subjects.
+* [Subprocessors](https://vtex.com/us-en/privacy-and-agreements/subprocessors/).
+* Our [technical and administrative](https://help.vtex.com/en/tracks/data-and-privacy--4Lc0i0an0DgnEtB0AUwlcq/7ANSqBP5DgOrVVyglo3Lbh) data security measures.
+* Security incident management.
+* Limitations of liability:
+    * Audit requests.
+    * International data transfers.
+    * VTEX's liability in the event of compensation for security incidents.
+* Integrity and confidentiality of personal data on VTEX.
+
+VTEX does not use end-customer data for any purpose other than to perform ecommerce operations as instructed by merchants.
+
+The DPA used must correspond to the specific region of the data subject (store customer).
+
+<div class="alert alert-warning">
+  <p>Check the<a href="https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/"> Data Processing Addendum - VTEX</a> to view the standard VTEX DPA for each region.</p>
+</div>
+
+## Shared responsibilities
+
+Both VTEX and merchants must ensure the security of personal data, each within a defined scope. VTEX's scope includes the platform infrastructure and its features, while the merchant's scope covers the storefront, Admin settings, access credentials, and local privacy regulations. Learn more in the following sections.
+
+## VTEX responsibilities
+
+VTEX, as the processor, can assist the merchant in complying with the data subject's rights, conducting privacy impact reports, and notifying the merchant of any incidents involving personal data of which it is aware. In addition, we are committed to complying with the [technical and administrative](https://help.vtex.com/en/tracks/data-and-privacy--4Lc0i0an0DgnEtB0AUwlcq/7ANSqBP5DgOrVVyglo3Lbh) security measures established in the [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/).
+
+## Merchant responsibilities
+
+Merchants, as controllers, determine the purposes and means of processing personal data. Therefore, merchants must instruct VTEX, under the terms of the [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/), so that personal data can be used on the platform to perform ecommerce operations.
+
+In the commercial context, the merchant defines the legal basis for using the personal data of customers (data subjects). Legal bases are the cases in which the law allows the use of personal data, such as consent. Legal bases do not apply to VTEX, as it only acts as a processor under the terms of the [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/) and does not decide the purposes for using personal data.
+
+### Privacy regulations
+
+Each merchant must conduct its own [Privacy Impact Assessments](https://gdpr-info.eu/issues/privacy-impact-assessment/), privacy policies, and technical and organizational measures and comply with the rights of the data subjects registered in their store. It is up to the merchant to choose the terms of their privacy policy and make it available on their website in compliance with local privacy laws.
+
+Merchants must implement their own security measures and, in the event of incidents involving personal data, must notify the data protection authorities and data subjects in compliance with the applicable laws. If you have specific questions about the laws applicable to your store, your end consumers, or other aspects of your business, contact a professional specialized in personal data protection.
+
+VTEX will support the merchant in some of these obligations under the [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/) terms, such as responses to subject rights and notification of security incidents.
+
+### Platform access
+
+Merchants play a crucial role in data security, as their decisions directly impact data protection. For example, by giving specific users or teams access to the platform or sharing [application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) (appKeys), the merchant affects the security of the data stored in that environment.
+
+To understand how to manage access credentials and ensure data integrity properly, see the following articles:
+
+- [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+-	[License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3)
+- [Application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet)
diff --git a/docs/tracks/en/define-payment-methods-displayed-on-instore.md b/docs/tracks/en/define-payment-methods-displayed-on-instore.md
index c4e4baa49..fda337427 100644
--- a/docs/tracks/en/define-payment-methods-displayed-on-instore.md
+++ b/docs/tracks/en/define-payment-methods-displayed-on-instore.md
@@ -3,8 +3,8 @@ title: 'Define payment methods displayed on VTEX Sales App'
 id: jHQQcyX3WKeUFidwSjmY1
 status: PUBLISHED
 createdAt: 2021-09-27T20:54:02.947Z
-updatedAt: 2023-05-31T16:13:49.825Z
-publishedAt: 2023-05-31T16:13:49.825Z
+updatedAt: 2023-07-05T17:16:01.041Z
+publishedAt: 2023-07-05T17:16:01.041Z
 firstPublishedAt: 2021-09-27T20:57:59.730Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugEN: instore-payments
 
 Once the payment condition has been created, you must create the filters that define which payment methods will appear in the VTEX Sales App checkout.
 
-To do this, your store developers must customize a JavaScript file. For more information, please refer to the guide [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/define-payment-methods-displayed-on-instore).
+To do this, your store developers must customize a JavaScript file. For more information, please refer to the guide [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/docs/guides/define-payment-methods-displayed-on-vtex-sales-app).
 
 <div class="alert alert-danger">
 <p>To enable payment conditions via the VTEX Sales App app, you must make changes to a JavaScript file. This operation must only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.</p>
diff --git a/docs/tracks/en/defining-centauro-trade-policy.md b/docs/tracks/en/defining-centauro-trade-policy.md
index ddd7693e0..71dbe80ad 100644
--- a/docs/tracks/en/defining-centauro-trade-policy.md
+++ b/docs/tracks/en/defining-centauro-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Defining Centauro trade policy'
 id: 2wFjrUoLI3q85r3QZA0Tp
 status: PUBLISHED
 createdAt: 2020-10-20T18:17:56.907Z
-updatedAt: 2022-12-08T20:35:41.540Z
-publishedAt: 2022-12-08T20:35:41.540Z
+updatedAt: 2023-10-19T14:10:07.750Z
+publishedAt: 2023-10-19T14:10:07.750Z
 firstPublishedAt: 2020-10-20T19:51:02.327Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/defining-dafiti-trade-policy.md b/docs/tracks/en/defining-dafiti-trade-policy.md
index fd8b864e6..cc0e437e1 100644
--- a/docs/tracks/en/defining-dafiti-trade-policy.md
+++ b/docs/tracks/en/defining-dafiti-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Defining Dafiti trade policy'
 id: 54cBCKrJgqdrm61vxihY1g
 status: PUBLISHED
 createdAt: 2021-02-23T21:32:12.282Z
-updatedAt: 2022-12-08T20:36:49.783Z
-publishedAt: 2022-12-08T20:36:49.783Z
+updatedAt: 2023-08-11T18:10:58.039Z
+publishedAt: 2023-08-11T18:10:58.039Z
 firstPublishedAt: 2021-02-23T21:41:19.622Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/defining-netshoes-trade-policy.md b/docs/tracks/en/defining-netshoes-trade-policy.md
index a21a765b8..7f7124d4f 100644
--- a/docs/tracks/en/defining-netshoes-trade-policy.md
+++ b/docs/tracks/en/defining-netshoes-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Defining Netshoes trade policy'
 id: 6ESk5Zk32baNfluXbL3Xmz
 status: PUBLISHED
 createdAt: 2021-02-23T20:04:34.470Z
-updatedAt: 2022-12-08T20:35:12.874Z
-publishedAt: 2022-12-08T20:35:12.874Z
+updatedAt: 2023-10-19T14:10:00.314Z
+publishedAt: 2023-10-19T14:10:00.314Z
 firstPublishedAt: 2021-02-23T20:20:32.953Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/defining-the-google-shopping-trade-policy.md b/docs/tracks/en/defining-the-google-shopping-trade-policy.md
index 72388beaf..5dc3d6023 100644
--- a/docs/tracks/en/defining-the-google-shopping-trade-policy.md
+++ b/docs/tracks/en/defining-the-google-shopping-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Defining the trade policy'
 id: 3AqbcsWrge8zLt0BC5CtGd
 status: PUBLISHED
 createdAt: 2021-04-14T17:58:41.545Z
-updatedAt: 2022-12-08T21:04:01.815Z
-publishedAt: 2022-12-08T21:04:01.815Z
+updatedAt: 2023-10-23T20:22:26.830Z
+publishedAt: 2023-10-23T20:22:26.830Z
 firstPublishedAt: 2021-04-15T17:41:14.352Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,13 +16,13 @@ trackSlugEN: integrating-with-google-shopping
 
 After creating your Google Merchant Center account, define the [trade policy](https://help.vtex.com/en/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) that you are going to use. When you [configure a trade policy for a marketplace](https://help.vtex.com/en/tutorial/configurando-a-politica-comercial-para-marketplace/), you determine which products will be submitted to Google Shopping and their price on the platform.
 
-In most cases, we recommend choosing the main trade policy (ID: 1), as Google Shopping results direct the buyer to make the purchase in the advertisers’ stores. Therefore, the integration will submit to Google all the products available in your store, at the same advertised prices.
+In most cases, we recommend choosing the main trade policy (ID: 1), as Google Shopping results direct buyers to purchase from advertisers’ stores. Therefore, the integration will submit all the products available in your store to Google at the same advertised prices.
 
-You will need to request the creation of a new trade policy only if you want to:
+You will need to request the creation of a new trade policy only if you want to: 
 - Offer a different product assortment on Google Shopping.
 - Sell products at different prices on Google Shopping.
 
-To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), simply fill out the [Trade Policy Release form](https://docs.google.com/forms/d/e/1FAIpQLSe9qCGB_KM_xsV5e9uNe06JE8tMZrWcv6EuHUOmqTiM8oRW7w/viewform). If you have any questions, please contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `Create a trade policy`.
+To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), please open a ticket to our [Support](https://help.vtex.com/en/support) by selecting Commercial and Create a trade policy.
 
 Requesting additional trade policies to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores is free of charge.
 
@@ -30,6 +30,33 @@ Requesting additional trade policies to integrate with [native connectors](https
 
 The [price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu) of your product on Google Shopping is determined when you choose the trade policy. It is essential to pay attention to a few things.
 
-If your trade policy includes [list prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) and [computed prices](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx#preco-computado), the latter will be sent to Google Shopping.
+If your trade policy includes [list prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) and [computed prices](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx#preco-computado), the latter will be sent to Google Shopping. For these promotions to be displayed on Google Shopping, the products must meet the following requirements in the Merchant Center:  
 
-When a product is linked to multiple [sellers](https://help.vtex.com/en/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) in your store, Google Shopping follows the rule to advertise the best available offer.
+- The base price, or a higher amount, must have been charged for 30 days, consecutively or not, in the last 200 days.
+- The base price must be valid.
+- The promotional price must be lower than the base price.
+- The promotion discount must be greater than 5% and less than 90% off the base price.  
+
+Once your products meet all the requirements listed above, the tool applies the promotional value previously configured on VTEX to the Google Shopping views.  
+
+## Discount linked to payment method  
+
+You can activate a discount linked to a payment method in two steps: First, [configure the discount](#configuring-discounts) and the payment method. Then, activate the discounts in the [connector configuration](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl). 
+
+### Configuring discounts  
+
+To configure a discount linked to a payment method, see the following documentation:
+
+1. [Set a discount using the checkout API](https://developers.vtex.com/docs/guides/set-a-discount-using-the-checkout-api) to enter the desired payment method in the `paymentSystemToCheckFirstInstallment` variable and simulate a shopping cart to make sure the payment method was updated. 
+2.  [Configuring a discount for orders prepaid in full](https://help.vtex.com/en/tutorial/configurar-desconto-de-preco-a-vista--7Lfcj9Wb5dpYfA2gKkACIt) to link an SKU to a payment method.
+3. [Configuring discounts for orders prepaid in full on Google Shopping](https://help.vtex.com/en/tutorial/configurar-desconto-de-preco-a-vista-para-google-shopping--40K3R5d4NogMvCzIWdWt3e)
+
+After following these instructions, you should activate the connector by [configuring the connector](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
+
+<div class="alert alert-warning">
+  When multiple sellers are linked to a product in your store, the rule for Google Shopping is to offer the best discount available.
+  </div>
+
+ <div class="alert alert-danger">
+  Each promotion created can belinked to only one payment method for the discount to be sent to Google Shopping.
+  </div> 
diff --git a/docs/tracks/en/defining-the-shipping-strategy-via.md b/docs/tracks/en/defining-the-shipping-strategy-via.md
index 79cbe5519..07143bfc4 100644
--- a/docs/tracks/en/defining-the-shipping-strategy-via.md
+++ b/docs/tracks/en/defining-the-shipping-strategy-via.md
@@ -3,8 +3,8 @@ title: 'Defining the shipping strategy'
 id: 69cLhDK7PGOqgSs2EyqMke
 status: PUBLISHED
 createdAt: 2018-09-24T19:51:55.267Z
-updatedAt: 2022-01-18T22:08:54.766Z
-publishedAt: 2022-01-18T22:08:54.766Z
+updatedAt: 2023-11-30T21:11:02.106Z
+publishedAt: 2023-11-30T21:11:02.106Z
 firstPublishedAt: 2018-09-27T22:13:49.998Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/delivery.md b/docs/tracks/en/delivery.md
index 426f24e0d..6fa611df6 100644
--- a/docs/tracks/en/delivery.md
+++ b/docs/tracks/en/delivery.md
@@ -27,18 +27,18 @@ You can choose between:
 - Pick up in a store.
 - Customize by item.
 
-![entrega-2-en](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/6acc2ea35a43a1056fc26336baff9db6/entrega-2-en.png)
+![entrega-2-en](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/6acc2ea35a43a1056fc26336baff9db6/entrega-2-en.png)
 
 ### Pickup points
 
 For pickup point options, the system selects the stores that have the SKUs in stock and shows the store closest to the customer's zip code, as a suggestion. If the sales associate wants to change the store where the customer will pick up the items, they just need to click the `Change pickup point` button.
 
-![entrega-retirada-en](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/f842bfa6851d45177338b3241e7c350c/entrega-retirada-en.png)
+![entrega-retirada-en](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/f842bfa6851d45177338b3241e7c350c/entrega-retirada-en.png)
 
 When choosing to change the pickup point, the sales associate first has access to the pickup point suggested by the system. To see all available pickup points, click `View all pickup points`.
 
-![31. VTEX Sales App - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
+![31. VTEX Sales App - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
 
 The app will then show the list of pick-up points ordered by the shortest distance from the customer's zip code. It's also possible to choose a pickup point on the map.
 
-![31. VTEX Sales App - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
+![31. VTEX Sales App - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
diff --git a/docs/tracks/en/detaching-skus-by-specification.md b/docs/tracks/en/detaching-skus-by-specification.md
index 175f22bae..45720af92 100644
--- a/docs/tracks/en/detaching-skus-by-specification.md
+++ b/docs/tracks/en/detaching-skus-by-specification.md
@@ -24,7 +24,7 @@ This tool is useful for clothing stores as it allows you to display the products
 
 See the following example of detaching SKUs by color. In the image below, the featured sandals are available in two different colors in the search results:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.</p></div>
diff --git a/docs/tracks/en/digital-wallet-e-wallet.md b/docs/tracks/en/digital-wallet-e-wallet.md
new file mode 100644
index 000000000..07d3c3568
--- /dev/null
+++ b/docs/tracks/en/digital-wallet-e-wallet.md
@@ -0,0 +1,23 @@
+---
+title: ' Digital wallet (ewallet)'
+id: 7jLbdfch9Oe2yYbQa9zwE1
+status: PUBLISHED
+createdAt: 2023-06-27T21:10:04.185Z
+updatedAt: 2023-09-26T15:11:41.781Z
+publishedAt: 2023-09-26T15:11:41.781Z
+firstPublishedAt: 2023-06-27T21:47:02.764Z
+contentType: trackArticle
+productTeam: Shopping
+slug: digital-wallet-e-wallet
+locale: en
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugEN: digital-wallet-e-wallet
+---
+
+A digital wallet (also known as an ewallet) is a secure environment where bank and credit card information can be stored. This information is encrypted in the system and, when accessed by its owner, can be used to make online purchases.
+
+Shopping with a digital wallet offers more security for the users, since they do not need to enter their payment information at the store checkout. Instead, the user is redirected to the digital wallet environment, where they must go through authentication steps.
+
+Once their identity is verified and they have selected a payment method, the order goes back to its normal flow and is completed. Some digital wallets also act as subacquirers, allowing unregistered users to make purchases in their environment.
+
+These are examples of digital wallets you can configure in your VTEX store for making payments: **Google Wallet**, **[Apple Pay](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-apple-pay--5L3NWMgvdKswWQa6eIc008)**, **Samsung Pay, **PayPal**, **Marketplace** **Pay**, **PagSeguro**, **Stelo**, among others.
diff --git a/docs/tracks/en/enabling-2-factor-authentication-login.md b/docs/tracks/en/enabling-2-factor-authentication-login.md
index 5ac510e52..7a2145f06 100644
--- a/docs/tracks/en/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/en/enabling-2-factor-authentication-login.md
@@ -32,7 +32,7 @@ There are two authentication options:
 - __App Google__ (key generated by an authentication app)
 - __SMS Message__ (key sent by text message)
 
-![2FA - Select - EN](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
+![2FA - Select - EN](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
 
 <div class="alert alert-warning">
   We recommend you to use a<a href="#enabling-2fa-por-aplicativo">authentication application</a> to prevent failures in your telephone provider from making your login impossible. Though the app, the access key will always be available for use.
@@ -48,17 +48,17 @@ To use a key generated by authentication application:
 
 1. Download the application **Google Authenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)).
 
-  ![2FA - App Download - EN](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
+  ![2FA - App Download - EN](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
 
 2. Use the application to read the QR Code with your phone's camera.
 
-  ![2FA - App QR Code - EN](https://images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/69de792a6a67c42dca1f35570dbaa562/2FA_-_App_QR_Code_-_EN.png)
+  ![2FA - App QR Code - EN](//images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/69de792a6a67c42dca1f35570dbaa562/2FA_-_App_QR_Code_-_EN.png)
 
 3. Your VTEX account will be added to the application, with a 6-digit code. Enter the code to finish your login.
 
   *The app code is regularly updated. It will not be necessary to memorize it, go to the application whenever you need it.*
 
-  ![2FA - App Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
+  ![2FA - App Insert Code - EN](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
 
 <div class="alert alert-info">
 If you log in using your email and password on the same computer, you will be asked for your access key every 3 days. When this happens, check the code in the application.
@@ -70,11 +70,11 @@ To use a key sent by text message:
 
 1. enter your phone number to receive the code by SMS - don't forget to enter your country and area code.
 
-  ![2FA - SMS Insert Phone - EN](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
+  ![2FA - SMS Insert Phone - EN](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
 
 2. You will receive a text message from VTEX on the indicated phone. Enter the 6-digit key to finish your login.
 
-   ![2FA - SMS Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
+   ![2FA - SMS Insert Code - EN](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
 
  <div class="alert alert-warning">
 We cannot guarantee that your telephone company will be able to deliver the access key whenever necessary. If the VTEX text message does not arrive, try resending the code or <a href="#enabling-2fa-through-an-app" >enable the 2FA per-application</a>.
@@ -86,10 +86,10 @@ To change the two-step verification settings:
 
 1. Access your user settings by clicking on the circle with your initials in the top-right corner of the Admin.
 
-  ![2FA - User Initials - EN](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
+  ![2FA - User Initials - EN](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
 
 2. Click **2-step verification** to see your settings.
 
-  ![2FA - My User - EN](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
+  ![2FA - My User - EN](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
 
 3. You can then change your settings by following similar steps as those described in the sections above to enable 2FA via [SMS](#enabling-2fa-via-sms) and [application](#enable-o-2fa-by-application). 
diff --git a/docs/tracks/en/enabling-a-sales-rep-code.md b/docs/tracks/en/enabling-a-sales-rep-code.md
index 1b9af7ed6..d67aeefac 100644
--- a/docs/tracks/en/enabling-a-sales-rep-code.md
+++ b/docs/tracks/en/enabling-a-sales-rep-code.md
@@ -42,7 +42,7 @@ After following these recommendations, access the __Store setup__ module. Then g
 
 On the right side of the screen, you will see the `checkout-instore-custom.js` file. 
 
-![codevendorEN](https://images.ctfassets.net/alneenqid6w5/71ZvVaWtn6hk5mYoISKE1y/2f4f5e201f6bc9b53fc694f7d70e05f3/codevendorEN.png)
+![codevendorEN](//images.ctfassets.net/alneenqid6w5/71ZvVaWtn6hk5mYoISKE1y/2f4f5e201f6bc9b53fc694f7d70e05f3/codevendorEN.png)
 
 Open the file and add the following piece of code to the `window.INSTORE_CONFIG` object:
 
@@ -64,7 +64,7 @@ The properties of the `window.INSTORE_CONFIG` object must be filled in according
 
 Click on the __Save__ blue button at the top of the page. 
 
-![codevendor2EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4T3vxA5Yatu9icLNPGuyCX/f456976ff81339225eef6bd0c458e6db/codevendor2EN.png)
+![codevendor2EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4T3vxA5Yatu9icLNPGuyCX/f456976ff81339225eef6bd0c458e6db/codevendor2EN.png)
 
 ## Understanding the priorities
 
diff --git a/docs/tracks/en/enabling-cart-transfer-between-devices.md b/docs/tracks/en/enabling-cart-transfer-between-devices.md
index b42e2f905..6af1ec564 100644
--- a/docs/tracks/en/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/en/enabling-cart-transfer-between-devices.md
@@ -34,11 +34,11 @@ window.INSTORE_CONFIG = {
 
 After making this change, open the inStore menu and update the data by clicking on the __Reset app local data__ button. Once this is done, a slider will appear at the bottom of the inStore identification page:
 
-![24. Enable cart transfer between devices - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6n8QGjNTdsUv8LYa5BS9k4/adb1f076df8c7c02a7210249f258016f/24._Enable_cart_transfer_between_devices_-_1_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6n8QGjNTdsUv8LYa5BS9k4/adb1f076df8c7c02a7210249f258016f/24._Enable_cart_transfer_between_devices_-_1_-_EN.png_h_250)
 
 When you drag the screen to the right, you will see the screen for __Cart Capture__, as shown in the image below.
 
-![24. Enable cart transfer between devices - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
 
 On this screen, you can capture a cart using one of three methods:
 - Cart code
@@ -49,4 +49,4 @@ On this screen, you can capture a cart using one of three methods:
 
 For the salesperson to share a cart, they can generate a numeric code or a QR Code. To do this, while on the cart screen, just click on the __Transfer__ button. See an example in the image below.
 
-![24. Enable cart transfer between devices - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
diff --git a/docs/tracks/en/enabling-product-recommendations.md b/docs/tracks/en/enabling-product-recommendations.md
index aa03e371c..b10cd0bf9 100644
--- a/docs/tracks/en/enabling-product-recommendations.md
+++ b/docs/tracks/en/enabling-product-recommendations.md
@@ -28,7 +28,7 @@ If you want to hide these recommendations, you need to edit the files `checkout-
 
 Like the inStore customization JavaScript file, `checkout-instore-custom.css` must be accessed through the VTEX administrative panel (as explained in the [inStore Customizations article](https://help.tex.com/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/4mwdBrFsmE2EPE0FzgX28b)).
 
-![25. Enable product recommendations - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/tPaSFJCJ0k3mk1GJh14r0/339b836008564c70f192820041a9df62/25._Enable_product_recommendations_-_1_-_EN.png_h_250)
+![25. Enable product recommendations - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/tPaSFJCJ0k3mk1GJh14r0/339b836008564c70f192820041a9df62/25._Enable_product_recommendations_-_1_-_EN.png_h_250)
 
 In the `checkout-instore-custom.css` file, include the following CSS rule:
 
diff --git a/docs/tracks/en/endless-aisle.md b/docs/tracks/en/endless-aisle.md
index 29f8c5575..68fdc1085 100644
--- a/docs/tracks/en/endless-aisle.md
+++ b/docs/tracks/en/endless-aisle.md
@@ -3,8 +3,8 @@ title: 'Endless Aisle'
 id: 40KMlmGI5tN0r0KPCDWgGn
 status: PUBLISHED
 createdAt: 2020-06-30T21:32:21.143Z
-updatedAt: 2023-05-31T15:34:48.839Z
-publishedAt: 2023-05-31T15:34:48.839Z
+updatedAt: 2023-07-26T18:46:19.274Z
+publishedAt: 2023-07-26T18:46:19.274Z
 firstPublishedAt: 2020-06-30T21:36:39.077Z
 contentType: trackArticle
 productTeam: Shopping
@@ -20,21 +20,21 @@ This is a basic concept of Omnichannel strategies, and essential for a real Unif
 
 ## Prerequisites
 
-First of all, you must consider the prerequisites that your store needs to ensure in order to start implementing an Endless Aisle strategy. Check our article on [Prerequisites for using inStore](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/1wtAanSRA3g2316dw7bw8u "Prerequisites for using inStore").
+First of all, you must consider the prerequisites that your store needs to ensure in order to start implementing an Endless Aisle strategy. Check our article on [Prerequisites for using VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/1wtAanSRA3g2316dw7bw8u "Prerequisites for using VTEX Sales App").
 
 ## Adding physical stores to VTEX Sales App
 
 To implement an Endless Aisle strategy, you must add your physical stores to the VTEX platform.
 
-To do this, follow the steps in the article [Managing physical stores and sales associates in inStore](https://help.vtex.com/en/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/5PSjRstg7UU4lOm0s8aqKN).
+To do this, follow the steps in the article [Managing physical stores and sales associates in VTEX Sales App](https://help.vtex.com/en/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/5PSjRstg7UU4lOm0s8aqKN).
 
 An important point of attention when registering a new store is the [Trade Policy](https://help.vtex.com/en/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) applied to it. It defines which assortment of products will be valid for the store.
 
-If the store's main Trade Policy is also used to sell on marketplaces, you must use a different Trade Policy for VTEX Sales App. Otherwise, the payment methods `Direct Selling Debit` and `Direct Selling Credit`, configured for inStore, will also be displayed at the checkout of marketplaces.
+If the store's main Trade Policy is also used to sell on marketplaces, you must use a different Trade Policy for VTEX Sales App. Otherwise, the payment methods `Direct Selling Debit` and `Direct Selling Credit`, configured for VTEX Sales App, will also be displayed at the checkout of marketplaces.
 
-If, on the other hand, your store uses a Trade Policy dedicated to inStore, make sure that:
+If, on the other hand, your store uses a Trade Policy dedicated to VTEX Sales App, make sure that:
 - Your products are priced according to this dedicated Trade Policy.
-- The dedicated Trade Policy is applied to the products that should serve the store where inStore will be used.
+- The dedicated Trade Policy is applied to the products that should serve the store where VTEX Sales App will be used.
 
 The Franchise-account and Pickup Point fields, in the store registration, should only be filled in if you want to work with product pickup in physical stores. If this is the case for you, also read the [Pickup Points Setup guide](https://help.vtex.com/en/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e).
 
diff --git a/docs/tracks/en/explained-search.md b/docs/tracks/en/explained-search.md
index d772c866b..5fda158b5 100644
--- a/docs/tracks/en/explained-search.md
+++ b/docs/tracks/en/explained-search.md
@@ -26,5 +26,5 @@ Follow the steps below to access it:
 1. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
 2. Under **Intelligent Search**, click __Explained Search__. 
 
-![Explained Search](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
+![Explained Search](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
 
diff --git a/docs/tracks/en/extensions-hub-1.md b/docs/tracks/en/extensions-hub-1.md
index fb8e6b95b..5fdf4d00c 100644
--- a/docs/tracks/en/extensions-hub-1.md
+++ b/docs/tracks/en/extensions-hub-1.md
@@ -18,6 +18,6 @@ The Extensions Hub is an Admin section that groups all extension information and
 
 To access the Extensions Hub, go to the left-side menu in the Admin and click the **Extensions** icon at the top.
 
-![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
+![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
 
 You can find three pages in the Extensions Hub section: **App Store**, **App Management**, and **Partners**. Documentation on each of these pages can be found in the articles below.
diff --git a/docs/tracks/en/extensions-hub-app-store.md b/docs/tracks/en/extensions-hub-app-store.md
index 224a9954b..da2d2f8f1 100644
--- a/docs/tracks/en/extensions-hub-app-store.md
+++ b/docs/tracks/en/extensions-hub-app-store.md
@@ -18,7 +18,7 @@ The App Store is the Admin page where you can search, view and get apps to expan
 
 ## Home page
 
-![Extensions Hub App Store home page](https://images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/3ee2d2f5b9ece590e163aad7fb5123ea/Extensions_Hub_App_Store_home_page_EN.png)
+![Extensions Hub App Store home page](//images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/3ee2d2f5b9ece590e163aad7fb5123ea/Extensions_Hub_App_Store_home_page_EN.png)
 
 When you log in to the store, you will see the home page with the following available options:
 
@@ -28,13 +28,13 @@ When you log in to the store, you will see the home page with the following avai
 
 ## Search
 
-![Extensions Hub App Store search](https://images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/d71df4490f5671670f04c6786ccc182f/Extensions_Hub_App_Store_search_EN.png)
+![Extensions Hub App Store search](//images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/d71df4490f5671670f04c6786ccc182f/Extensions_Hub_App_Store_search_EN.png)
 
 You can search for an app by typing its name in the search text box and pressing `Enter`. Then, you will be redirected to the search results page. The results will be the apps whose names match the text you entered in the search. The apps are displayed as square cards, where you can see the app name, headline, and price. Clicking an app will take you to the [app page](#app-page).
 
 ## App page
 
-![Extensions Hub App Store app page](https://images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/5b4946289b0a1ec0a29b9e12e1b94d69/Extensions_Hub_App_Store_app_page_EN.png)
+![Extensions Hub App Store app page](//images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/5b4946289b0a1ec0a29b9e12e1b94d69/Extensions_Hub_App_Store_app_page_EN.png)
 
 When you click an app on the home page or in the search results, you will be redirected to the app page. On this page, you will find detailed information about the app, including its price and the option to acquire it.
 
diff --git a/docs/tracks/en/extensions-hub-partners.md b/docs/tracks/en/extensions-hub-partners.md
new file mode 100644
index 000000000..c47523652
--- /dev/null
+++ b/docs/tracks/en/extensions-hub-partners.md
@@ -0,0 +1,19 @@
+---
+title: 'Partners'
+id: 3XkOpOSbeCJIcBL5dhuPq1
+status: PUBLISHED
+createdAt: 2023-08-02T13:04:06.286Z
+updatedAt: 2023-08-02T14:33:05.047Z
+publishedAt: 2023-08-02T14:33:05.047Z
+firstPublishedAt: 2023-08-02T14:33:05.047Z
+contentType: trackArticle
+productTeam: VTEX IO
+slug: extensions-hub-partners
+locale: en
+trackId: AW7klkYMh557y5IUOgzco
+trackSlugEN: extensions-hub
+---
+
+<div class="alert alert-warning">
+Content is not available yet.
+</div>
diff --git a/docs/tracks/en/filter-orders-by-vendor.md b/docs/tracks/en/filter-orders-by-vendor.md
index 5c1257a8b..0dc57bc7d 100644
--- a/docs/tracks/en/filter-orders-by-vendor.md
+++ b/docs/tracks/en/filter-orders-by-vendor.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-setup
 
 With inStore you can see the listing of all completed orders in a store:
 
-![pedidos finalizados](https://images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
+![pedidos finalizados](//images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
 
 However, sometimes it makes sense for a sales representative to see only the orders made by him. To enable this option you need to edit the `checkout-instore-custom.js` file in the Portal Admin. Because it is a JavaScript present in several streams of application use, it's important that you have programming knowledge before changing it, to avoid breaking other features.
 
@@ -37,4 +37,4 @@ __IMPORTANT__: Do not remove any of the other properties present in the `window.
 
 After reloading inStore the result should be as follows:
 
-![pedidos finalizados filtrados por vendedor](https://images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
+![pedidos finalizados filtrados por vendedor](//images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
diff --git a/docs/tracks/en/filters.md b/docs/tracks/en/filters.md
index 0aa8d2067..92d6402bb 100644
--- a/docs/tracks/en/filters.md
+++ b/docs/tracks/en/filters.md
@@ -3,8 +3,8 @@ title: 'Filters'
 id: 50Dh4mpv0Sax0XpbvsjAtP
 status: PUBLISHED
 createdAt: 2020-03-05T17:44:58.362Z
-updatedAt: 2023-05-05T19:32:35.780Z
-publishedAt: 2023-05-05T19:32:35.780Z
+updatedAt: 2024-06-04T15:34:47.299Z
+publishedAt: 2024-06-04T15:34:47.299Z
 firstPublishedAt: 2020-03-05T19:54:44.962Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -36,12 +36,13 @@ The Filters feature allows you to:
 
 - Search for a term within a filter.
 - Configure and define the maximum number of options in a filter before scrolling.
-- Configure the filter layout. You can choose between the following formats:  
-- Vertical list (standard format).
-- Horizontal list (used to display filters such as Size and Color).
-- Slider (used to select a range of numeric values).
-- Interval sets (to divide products into groups of values).
-- Value entry (the customer can inform the “from” and “to” values).
+- Configure the filter layout. You can choose between the following formats:
+   - Vertical list (standard format).
+   - Horizontal list (used to display filters such as Size and Color).
+   - Slider: Used to adjust the price range from a minimum to a maximum value.
+   - Price field: Allows entering the full price and discounted price for filtering results.
+
+Check out the [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) guide on the Developer Portal for more technical details on using filters.
 
 <div class="alert alert-warning">
   <p>While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.</p>
diff --git a/docs/tracks/en/frontend-implementation.md b/docs/tracks/en/frontend-implementation.md
new file mode 100644
index 000000000..4f0c9cac5
--- /dev/null
+++ b/docs/tracks/en/frontend-implementation.md
@@ -0,0 +1,322 @@
+---
+title: 'Frontend implementation'
+id: 67SCtUreXxKYWhZh8n0zvZ
+status: PUBLISHED
+createdAt: 2024-01-31T22:25:47.689Z
+updatedAt: 2024-03-07T17:10:29.946Z
+publishedAt: 2024-03-07T17:10:29.946Z
+firstPublishedAt: 2024-02-22T14:07:19.178Z
+contentType: trackArticle
+productTeam: Others
+slug: frontend-implementation
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+The frontend of an online store, also known as the storefront, is the store's visual and interactive interface. This is where customers interact with products and perform actions such as navigating categories, searching, and adding products to their cart.
+
+This article helps you choose the right technology for building your storefront and the settings required for it, considering the following aspects:
+
+- VTEX storefront development technologies.
+- Main features of each technology.
+- Development stages.
+
+The frontend implementation is a stage focused on defining the technologies to implement based on the business needs related to the storefront.
+
+<div class = "alert alert-info">
+The frontend can be implemented by the company's internal development team or our <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">implementation partners </a>.<a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512">Users</a> with access to the VTEX Admin can view our partner list through the <a href="https://partnernetwork.myvtex.com/Parceiros">Partner Portal</a>.
+</div>
+
+## Before you begin
+
+Before implementing the frontend, you should configure the following steps in your store:
+
+| Step | Description |
+|---|---|
+| Defining the store's architecture and sales strategy | The team defines your VTEX store's architecture based on your business model's strategies and needs.<br><br>Learn more in the [Accounts and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) article. |
+| Configuring roles | The team configures the roles needed for each [user](https://help.vtex.com/en/tutorial/managing-users--tutorials_512) to use the VTEX platform.<br><br>Learn more in the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) article. |
+| Configuring catalog | The team configures the product[ catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog), category tree, and related information, such as descriptions, images, and prices, to populate and test the store, including features such as product listing pages (PLP), search features, product details pages (PDP), and checkout.<br><br>Not having a catalog can result in incomplete testing and data integration problems, which delays implementation.<br><br>Learn more in the [VTEX modules I](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) article. |
+| Defining the apps needed to operate the store | The team defines the native and third-party apps needed to operate the store.<br><br>For stores that will be built using [Store Framework](#store-framework), there is a list of native and third-party apps.<br><br>Learn more in the [VTEX IO apps](https://developers.vtex.com/docs/vtex-io-apps) article. |
+
+<div class = "alert alert-info">
+The <a href="#development-stages">development stage</a> can run in parallel with other <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">backend integrations</a> and <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7">module configuration</a> steps, such as setting up payment methods and logistics. This will depend on the type of <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">architecture and planning</a> chosen for the VTEX store, and the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">implementing agency</a> or <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">VTEX Support</a> should monitor these processes.
+</div>
+
+## Frontend development technologies on VTEX
+
+VTEX has three different technologies for storefront development: [FastStore](#faststore), [Store Framework](#store-framework) and [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). Legacy CMS Portal was VTEX's first technology for building storefronts, based on HTML, CSS, and JavaScript, and all development and code editing for this technology is done via the VTEX Admin.
+
+<div class="alert alert-warning">
+Although some stores still use it, the <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> is a legacy technology and is no longer available to new stores starting with VTEX.
+</div>
+
+The following sections are about the main characteristics and features of FastStore and Store Framework.
+
+## FastStore
+
+FastStore is a fresh innovative storefront technology for development teams to create stores focused on performance and stability. It's also an easy-to-maintain technology when editing your store's pages.
+
+This technology is an open-source toolkit based on [React](https://react.dev/) and the [Jamstack](https://jamstack.org/) architecture. For more information, see the [FastStore](https://www.faststore.dev/docs) documentation portal.
+
+### FastStore main features
+
+The following table lists some of FastStore's main features:
+
+| Feature | Description |
+|---|---|
+| [Starter](https://starter.vtex.app/) | Functional template designed for fast store development, which seamlessly integrates the [FastStore UI](https://www.faststore.dev/components) components. It includes pages such as Home, product list pages (PLPs), product detail pages (PDPs), and minicart features. |
+| [FastStore UI](https://www.faststore.dev/components) | Component library for ecommerce that provides basic features and design, enabling faster implementation and storefront customization. |
+| Headless technology | Customization process that separates the store code developed by the development team from the base code provided by VTEX. This simplifies updates to the store's frontend, allowing updates without impacting the customized code. |
+| [GitHub](https://github.com/) integration | Development teams can manage all storefront code using [GitHub](https://github.com/). |
+| [Headless CMS](https://www.faststore.dev/docs/headless-cms-overview) | Content management system (CMS) that allows editing and creating new pages and previewing content changes. |
+| Automated checks | Functional tests and the store's performance and code quality assessment run continuously and automatically to identify slowdowns and bugs throughout the storefront development stage. |
+| [Intelligent Search](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account) integration | Autocomplete feature in the search bar, which also offers search suggestions and products based on configurable preferences. |
+| [Checkout](https://www.faststore.dev/docs/go-live/4-integrating-the-vtex-checkout), [My Account](https://www.faststore.dev/docs/go-live/5-integrating-the-vtex-order-placed-and-my-account), and [Login](https://www.faststore.dev/docs/go-live/3-integrating-the-the-vtex-login) integrations | Integration with other stages of the customer buying journey. VTEX stores previously developed using Store Framework can keep settings related to Checkout, My Account, and Login when migrated to FastStore, as they benefit from the same infrastructure. |
+
+## Store Framework
+
+Store Framework is a well-established solution providing a technology framework for low-code storefront implementation with a focus on the composable commerce model. In other words, the framework allows the combination of different [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) apps to build a storefront.
+
+In this technology, the store's implementation and launch are based on pre-built components, also known as blocks, and customization of these components tailored to specific business needs. This _framework_ is based on:
+
+- React
+- TypeScript
+- Node.js
+- GraphQL
+
+For more information, read the [What is VTEX Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) article.
+
+### Development environment
+
+When talking about frontend implementation, remember that [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) is not a storefront building technology, but rather a development platform. The Store Framework is a technology for building storefronts that runs on VTEX IO, a cloud-based environment and development solution for customized apps and storefronts.
+
+This means that with VTEX IO, you develop your code locally. However, when it comes to deploying and running the store, VTEX IO manages the infrastructure, CI/CD, and security and takes care of the deployment process. The image below shows how these concepts relate to each other:
+
+![Frontend development architecture](//images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/9d5da1e9f3ba8d7fe3f8808a0e8d639e/frontend_image1_EN.png)
+
+### Store Framework main features
+
+The following table shows some of Store Framework's main features:
+
+| Feature | Description |
+|---|---|
+| [Starter](https://github.com/vtex-apps/store-theme) | Functional template designed for fast store development, which seamlessly integrates pre-built components. |
+| [Pre-built components](https://developers.vtex.com/docs/vtex-io-apps) | *React-based* native components. |
+| Modular architecture | Customization and code reuse of interface elements to quickly launch and replicate stores. |
+| [Workspaces and test environments](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace) | It allows you to create different store versions and test them beforehand to make changes safely. |
+| [Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) | Content management system (CMS) for editing templates and building new pages on the store's website. |
+| [Native A/B testing](https://developers.vtex.com/docs/guides/ab-tests) | It allows you to test and validate the store version with the highest conversion rates. |
+| [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) integration | Autocomplete feature in the search bar, which also offers search suggestions and products based on configurable preferences. |
+| [Progressive Web App (PWA)](https://help.vtex.com/en/tutorial/enabling-pwa-push-notifications-in-your-store--1be3ZPhbsgZSbE7h5H46pG) | 
+Enables native app-like experiences on any device with PWA-ready technology.|
+| [Cross-border](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs) | It allows a VTEX [multistore](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multistore) to operate in different countries with a specific approach for each one. |
+| Checkout, [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), and Login integrations | Integration with other stages of the customer buying journey. |
+
+## Choosing the frontend technology
+
+When choosing between Store Framework and FastStore, the team must evaluate the project's specific needs and consider the team's experience with both technologies.
+
+The Store Framework is a more mature option that offers a flexible structure suitable for complex use cases and support for stores operating internationally and in multiple languages. 
+For B2B stores, Store Framework is a good choice, as it provides the [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite), an app that allows the management of organizations, storefront permissions, and checkout settings for B2B commerce relationships.
+
+FastStore is an evolving alternative focused on store performance. This solution offers a fast loading experience, crucial for keeping store visitors engaged and reducing cart abandonment rates. For simpler use cases with a focus on performance, FastStore cab be the recommended technology.
+
+<div class = "alert alert-info">
+The <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">VTEX support</a> team can help you choose between one of the available storefront technologies.
+</div>
+
+The table below compares the two technologies based on their main features:
+
+<table>
+    <tr>
+        <td><strong>Feature</strong></td>
+        <td><strong>Store Framework</strong></td>
+        <td><strong>FastStore</strong></td>
+    </tr>
+    <tr>
+        <td>Starter (initial template)</td>
+        <td>The <a href="https://github.com/vtex-apps/store-theme">Store Theme</a> is the initial template the team can use as a basis to launch the store project or start from scratch.</td>
+        <td>The <a href="https://starter.vtex.app/">FastStore Starter</a> is already available after completing the <a href="https://www.faststore.dev/docs/getting-started/1-faststore-onboarding/overview">FastStore Onboarding</a>. This allows the team to kick off the project with a base template focused on performance.</td>
+    </tr>
+    <tr>
+        <td>Performance</td>
+        <td>SSR (Server Side Rendering) features generate the complete HTML of a page on the server as a response to a page request, while SPA (Single Page Application) loads elements such as the header only once the page is loaded.</td>
+        <td>Maximum performance possible, as it uses <a href="https://jamstack.org/">Jamstack</a> architecture to create the store's website pages in advance, making site delivery faster and more resource-efficient.</td>
+    </tr>
+    <tr>
+        <td>Tech Stack</td>
+        <td>
+            <ul>
+                <li>TypeScript
+                <li>React
+                <li>GraphQL
+                <li>Node.js
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li>TypeScript
+                <li>React
+                <li>Next.js
+                <li>GraphQL
+                <li>Node.js
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Component customizations</td>
+        <td>Flexible and easy to customize.</td>
+        <td>It allows native component customization and guarantees store performance following best practices.</td>
+    </tr>
+    <tr>
+        <td>Code management</td>
+        <td>It uses <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace">workspaces</a> and the VTEX IO architecture for versioning, updating, and rolling back components and apps.</td>
+        <td>It uses GitHub and the <a href="https://docs.github.com/pt/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches">branch</a> concept for collaboration. Authorized users in the storefront repository on GitHub can view and work on the code.</td>
+    </tr>
+    <tr>
+        <td><em>Community and Support</em></td>
+        <td>
+            <ul>
+                <li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework">Official documentation</a>
+                <li><a href="https://community.vtex.com/c/store-development/store-framework/17">VTEX community</a>
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li><a href="https://www.faststore.dev/docs">Official documentation</a>
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td><em>Performance Monitoring and Analytics</em></td>
+        <td>
+            <ul>
+                <li>Possibility of configuring <a href="https://developers.vtex.com/docs/guides/google-tag-manager">VTEX Google Tag Manager</a> to analyze store navigation data.
+                <li>Possibility of increasing store performance using <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance">optimization tools</a>.
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li>Possibility of configuring the native Analytics module.
+                <li>Possibility of improving store performance using technology tools.
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Content Management Systems (CMS)</td>
+        <td>Compatible with <a href="https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1">Site Editor</a>.</td>
+        <td>Compatible with <a href="https://www.faststore.dev/docs/headless-cms-overview">Headless CMS</a>.</td>
+    </tr>
+</table>
+
+## Development stages
+
+Before launching the store into production and [going live](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), list the essential settings and features to add to the storefront. These definitions help you define the Minimum Viable Product (MVP) for the storefront. The following topics outline:
+
+- [FastStore MVP requirements](#faststore-mvp-requirements)
+- [Store Framework MVP requirements](#store-framework-mvp-requirements)
+
+<div class = "alert alert-info">
+The following recommendations are for basic storefront setup. Other settings may be required depending on the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">architecture chosen</a> for your store's operation.
+</div>
+
+### Developing using FastStore
+
+The development team must start a new project with FastStore through the [Onboarding](https://www.faststore.dev/docs/getting-started/1-faststore-onboarding/overview) process. The team will have a basic, functional store based on [FastStore Starter](https://starter.vtex.app/) at the end of this process. After this, the following basic requirements for the page will have been implemented:
+
+- Home
+- *Product Listing Page* (PLP)
+- *Product Details Page* (PDP)
+- *Minicart*
+
+![FastStore template](//images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
+
+#### FastStore MVP requirements
+
+Below are the requirements for each topic:
+
+- Catalog
+  - [Adding products and SKUs](https://help.vtex.com/en/tutorial/adding-products--tutorials_2567)
+  - [Creating a category tree](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206) ([departments](https://help.vtex.com/en/tutorial/what-is-a-department--22rKjmYWVmmKAK8CWa8yKw), [categories](https://help.vtex.com/en/tutorial/what-is-a-category--6HV4Q3E2FauUoOQoiCCgCg) and [subcategories](https://help.vtex.com/en/tutorial/what-is-a-subcategory--2cb0aRkG3i6AeiAMM24iwY))
+  - [Defining filters and types of specifications per category](https://help.vtex.com/en/tutorial/creating-a-specification-group-in-a-category--tutorials_246)
+  - [Adding SKU images](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY#images)
+  - [Adding SKU prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29)
+  - [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139)
+- VTEX Intelligent Search
+  - [Integrating the Intelligent Search app with the account](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account)
+- Headless CMS integration
+  - [Configuring Headless CMS in the account](https://www.faststore.dev/docs/headless-cms-integration/1-configuring-the-vtex-account)
+  - [Defining content types and sections that will be available](https://www.faststore.dev/docs/headless-cms-integration/2-setting-up-the-headless-cms)
+  - Creating and editing pages using Headless CMS in the VTEX Admin
+- Homepage
+  - Editing the components and layouts already listed in [Starter](https://starter.vtex.app/)
+- Login page
+  - [VTEX Login integration](https://www.faststore.dev/docs/go-live/3-integrating-the-the-vtex-login)
+  - Editing the components and layouts already listed in [Starter](https://starter.vtex.app/)
+- Product Listing Page (PLP)
+  - Editing the components and layouts already listed in [Starter](https://starter.vtex.app/office)
+- Product Details Page (PDP)
+  - Editing the components and layouts already listed in [Starter](https://starter.vtex.app/4k-philips-monitor-99988213/p)
+- Minicart configuration
+  - Editing the components and layouts already listed in [Starter](https://starter.vtex.app/)
+- Checkout
+  - [VTEX Checkout](https://www.faststore.dev/docs/go-live/4-integrating-the-vtex-checkout) integration
+  - [VTEX Order Placed e My Account](https://www.faststore.dev/docs/go-live/5-integrating-the-vtex-order-placed-and-my-account) integration
+- Logistics
+  - [Adding loading docks](https://help.vtex.com/en/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW)
+  - [Adding shipping strategies](https://help.vtex.com/en/tutorial/shipping-strategy--58vLBDbjYVQzJ6rRc5QNz3)
+  - [Associating a shipping strategy and warehouse with a loading dock](https://help.vtex.com/en/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW)
+- Payments
+  - [Configuring the Notes Payable provider](https://help.vtex.com/en/tutorial/setting-up-the-notes-payable-conector--7Gy0SJRVS0Qi2CuWMAqQc0)
+  - [Adding gateway providers](https://help.vtex.com/pt/tutorial/registering-gateway-affiliations/)
+- Performance and SEO
+  - Improving the store performance using the right[ technology](https://v1.faststore.dev/how-to-guides/performance) tools
+- Metrics
+  - Configuring the [Analytics](https://v1.faststore.dev/reference/sdk/analytics) module
+
+### Developing using Store Framework
+
+The development team must start a new project with Store Framework by cloning and [linking](https://developers.vtex.com/docs/guides/vtex-io-documentation-linking-an-app) the [store theme](https://github.com/vtex-apps/store-theme) to a [development workspace](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace). The store theme is a basic functional template to kick off the store with essential components and pages, such as:
+
+- *Homepage*
+- Product Listing Page (PLP)
+- Product Details Page (PDP)
+
+![Store Framework template](//images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
+
+#### Store Framework MVP requirements
+
+Below are the requirements for each topic:
+
+- Catalog
+  - [Adding products and SKUs](https://help.vtex.com/en/tutorial/adding-products--tutorials_2567)
+  - [Creating a category tree](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206) ([departments](https://help.vtex.com/en/tutorial/what-is-a-department--22rKjmYWVmmKAK8CWa8yKw), [categories](https://help.vtex.com/en/tutorial/what-is-a-category--6HV4Q3E2FauUoOQoiCCgCg) and [subcategories](https://help.vtex.com/en/tutorial/what-is-a-subcategory--2cb0aRkG3i6AeiAMM24iwY))
+  - [Defining filters and types of specifications per category](https://help.vtex.com/en/tutorial/creating-a-specification-group-in-a-category--tutorials_246)
+  - [Adding SKU images](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY#images)
+  - [Adding SKU prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29)
+  - [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139)
+- VTEX Intelligent Search
+  - [Integrating the Intelligent Search app with the account](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account)
+- Homepage
+  - Editing the components and layouts already listed in [Starter](https://storetheme.vtex.com/)
+- Login page
+  - Integrating with VTEX Login
+  - Editing the components and layouts already listed in [Starter](https://storetheme.vtex.com/)
+- Product Listing Page (PLP)
+  - Editing the components and layouts already listed in [Starter](https://storetheme.vtex.com/clothing?_q=clothing&map=ft)
+- Product Details Page (PDP)
+  - Editing the components and layouts already listed in [Starter](https://storetheme.vtex.com/ten-top-shirts/p)
+- Minicart configuration
+  - Editing the components and layouts already listed in [Starter](https://storetheme.vtex.com/)
+- Logistics
+  - [Adding loading docks](https://help.vtex.com/en/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW)
+  - [Adding shipping strategies](https://help.vtex.com/en/tutorial/shipping-strategy--58vLBDbjYVQzJ6rRc5QNz3)
+  - [Associating a shipping strategy and warehouse with a loading dock](https://help.vtex.com/en/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW)
+- Payments
+  - [Configuring the Notes Payable provider](https://help.vtex.com/en/tutorial/setting-up-the-notes-payable-conector--7Gy0SJRVS0Qi2CuWMAqQc0)
+  - [Adding gateway providers](https://help.vtex.com/pt/tutorial/registering-gateway-affiliations/)
+- Performance
+  - Improving the store performance using performance [optimization tools](https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance)
+- Metrics
+  - Configuring [Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager)
diff --git a/docs/tracks/en/frontend.md b/docs/tracks/en/frontend.md
index 3892e20df..5f9c740a8 100644
--- a/docs/tracks/en/frontend.md
+++ b/docs/tracks/en/frontend.md
@@ -26,7 +26,7 @@ The way this feature extension happens is through VTEX apps that are available g
 
 Store Framework is a solution for building storefronts that leverages VTEX IO. Using it, you can rely on the user-friendly interface of [Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) and easily manage store content.
 
-![vtex io](https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5b55c0f934c47034373e47f9be09c754/image3.png)
+![vtex io](//images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5b55c0f934c47034373e47f9be09c754/image3.png)
 
 Stores created with Store Framework also include: 
 - **[Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)**: Search tool that corrects spelling errors and enables conditional rules for displaying the search result.
diff --git a/docs/tracks/en/getting-started-with-logistics.md b/docs/tracks/en/getting-started-with-logistics.md
index d5ab89c2f..480a47eb6 100644
--- a/docs/tracks/en/getting-started-with-logistics.md
+++ b/docs/tracks/en/getting-started-with-logistics.md
@@ -56,7 +56,7 @@ Basically, the **Inventory & shipping** module is divided into the following sec
 * **Settings**: General logistics settings, such as enabling critical stock notification.
 * **[Pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R)**: For listing physical locations where customers can pick up their orders.
 
-![estoque e entregaEN](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/8286563b415555a4ab5e56cb8e6e290c/estoque_e_entregaEN.png)
+![estoque e entregaEN](//images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/8286563b415555a4ab5e56cb8e6e290c/estoque_e_entregaEN.png)
 
 <div class = "alert alert-info"> Clients using <a href="https://vtex.com/us-en/">VTEX Shipping Network</a> can access this feature in the Inventory & shipping module.
 </div>
diff --git a/docs/tracks/en/go-live-process.md b/docs/tracks/en/go-live-process.md
index 80cf3b669..873b540b7 100644
--- a/docs/tracks/en/go-live-process.md
+++ b/docs/tracks/en/go-live-process.md
@@ -1,10 +1,10 @@
 ---
 title: 'Go-live your store'
 id: 1iP90RcJvlrfQhnlxM54wo
-status: PUBLISHED
+status: CHANGED
 createdAt: 2022-12-09T19:12:28.218Z
-updatedAt: 2023-03-27T14:51:55.484Z
-publishedAt: 2023-03-27T14:51:55.484Z
+updatedAt: 2024-05-24T14:32:56.445Z
+publishedAt: 2024-01-31T13:30:12.446Z
 firstPublishedAt: 2022-12-09T22:09:43.345Z
 contentType: trackArticle
 productTeam: Reliability
@@ -18,7 +18,7 @@ If you have [configured your store's operation](https://help.vtex.com/pt/tracks)
 
 Here you will find detailed step-by-step instructions on how to go live with your store.
 
-![Go-live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/b1f21c5f9b94732df8e7ca5fd3b6ed69/go_live_en.jpg)
+![Go-live](//images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/b1f21c5f9b94732df8e7ca5fd3b6ed69/go_live_en.jpg)
 
 <div class = "alert alert-info">
 Note that a store in production is different from an account in production. In general, to have a store in production, you need to put the account in production and set up DNS pointing. See below all the steps involved in this process.
@@ -28,10 +28,10 @@ Note that a store in production is different from an account in production. In g
 
 Before going live, you need to ensure that you have set up all configurations for your store to run smoothly.
 
-Copy this [Store configuration checklist](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/1b0830db006f3c48289dbdcb1f1db707/Store_configuration_checklist.xlsx) and check if you have configured each item according to your desired operation.
+Copy this [Store configuration checklist](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/be48d84768e5fb014f3903ad23927a11/Store_configuration_checklist_EN.xlsx) and check if you have configured each item according to your desired operation.
 
 <div class="alert alert-warning">
-The checklist above lists the basic features and configurations required to run a VTEX store. It is your team's responsibility to determine which features to implement in your store and how to configure them to create the desired store experience. Therefore, this list may only cover some of the features your store uses, and you must check all aspects of your store's operation, even if they are not on the suggested list. Ainda assim é importante que verifique todos os aspectos do funcionamento da sua loja, mesmo que não estejam na lista sugerida.
+The checklist above lists the basic features and configurations required to run a VTEX store. It is your team's responsibility to determine which features to implement in your store and how to configure them to create the desired store experience. Therefore, this list may only cover some of the features your store uses, and you must check all aspects of your store's operation, even if they are not on the suggested list.
 </div>
 
 ## Instructions
diff --git a/docs/tracks/en/google-pay.md b/docs/tracks/en/google-pay.md
new file mode 100644
index 000000000..d856da80d
--- /dev/null
+++ b/docs/tracks/en/google-pay.md
@@ -0,0 +1,111 @@
+---
+title: 'Google Pay'
+id: 61JMBvM5Vanqj6RaJsP8CT
+status: PUBLISHED
+createdAt: 2023-06-27T21:28:37.755Z
+updatedAt: 2024-08-01T17:59:31.657Z
+publishedAt: 2024-08-01T17:59:31.657Z
+firstPublishedAt: 2023-06-27T21:46:39.537Z
+contentType: trackArticle
+productTeam: Shopping
+slug: google-pay
+locale: en
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugEN: digital-wallet-e-wallet
+---
+
+Google Pay™ is a digital payments service that allows users not to share their actual card information with the store, providing more security and streamlining the checkout step. With Google Pay, users can make payments using credit or debit cards without having to enter any information manually, and Google Pay is also available in various apps, websites and in the Google Wallet. 
+
+The Google Pay API Terms of Service apply whenever the Google Pay service is offered by a merchant. To read the terms, please see [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
+
+<div class="alert alert-warning">
+<p>Google Pay is not available for Checkout V5 or earlier versions of Checkout.</p>
+</div>
+
+## Enabling Google Pay
+
+To enable Google Pay, follow the steps below.
+
+1. In the VTEX Admin, go to **Store Settings > Payments > Wallets** or type **Wallets** in the search bar at the top of the page.
+2. Select **Activate** to include the Google Pay extension.
+
+<div class = "alert alert-info">
+<p>The card brands supported by the Google Pay extension are the ones configured in the payment conditions.</p>
+</div>
+
+![google-pay-checkout-en](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/2857562e61a935524807632c23be2e91/Screenshot_2024-08-01_at_14.21.39.png)
+
+Google Pay will then be available in your VTEX store's checkout as a new payment method. It may take around 10 minutes to be implemented.
+
+<div class = "alert alert-warning">
+<p>For now, Google Pay does not support subscriptions.</p>
+</div>
+
+To use Google Pay, you must meet the following requirements:
+
+* Having at least one active [payment condition](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) configured for credit or debit cards with an [acquirer](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente), establishing which acquirer will process the wallet payment.
+* Using [VTEX Checkout](https://help.vtex.com/en/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) in your store.
+
+<div class = "alert alert-warning">
+<p>For stores that have the <a href="https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> authentication flow configured and supported by the acquirer, payment with Google Pay will follow the card native flow and will use 3DS as well. For more information on how to configure the authentication flow, please refer to <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Setting up 3DS 2 authentication flow</a>.</p>
+</div>
+
+<div class="alert alert-info">
+<p>You can also set up Google Pay to be processed with Adyen or Stripe. To do this, access the <b>Payment Conditions</b> screen in Admin, click on <b>Google Pay</b> and select the desired option.</p>
+</div>
+
+## Viewing transactions completed with Google Pay
+
+To view transactions that have been completed with Google Pay, please follow the steps described in the article [Viewing transaction details](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy). In the search bar of the transactions page, type **Google Pay** to filter the transactions carried out with this type of payment.
+
+![Google Pay Transaction_1](//images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/e1521f4f47aff56a64d808f2f450ce38/Google_Pay_Transaction1_EN.png)
+
+After accessing the desired transaction, click on `+ Information` to verify the **Google Pay** information described in the `paymentOrigin` field.
+
+![Google Pay Transaction_2](//images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/a565b60f7ca5f541c836553140261985/Google_Pay_Transaction2_EN.png)
+
+<div class="alert alert-warning">
+  <p>It is also possible to identify transactions made with Google Pay through the <b>All Orders</b> page in Admin. You just need to select the desired search period, <a href="https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">export the orders</a> in a report in .csv and locate the Google Pay information in the "payment origin" field.</p>
+</div>
+
+## Adding Google Pay information to the purchase template
+
+To add the information that the order was placed with a Google Pay card to the email template that will be sent to the buyer, follow the steps below.
+
+1. In the VTEX Admin, go to **Store Settings > Email templates > Templates** or type **Templates** in the search bar at the top of the page.
+2. Access the checkout and payment approval templates.
+3. After** **all mentions** **of** `{{#if lastDigits}}` last digits `{{lastDigits}}`, add the following line:
+`{{/if}} {{#if paymentOrigin}} ({{paymentOrigin}}`
+
+After this change, whenever there is any mention of the last four digits of the card in these email templates, the "(Google Pay)" information will be added for payments made with a digital wallet.
+
+<div class = "alert alert-info">
+<p>For stores provisioned as of March 2023, the templates will already be updated with the information for payments made with Google Pay.</p>
+</div>
+
+## FAQ
+
+### Activation issues
+
+* Cannot enable the wallet because the toggle switch is disabled
+
+If you get the message "You don't have any networks enabled for Google Pay in your store.", you must go to the payment conditions and check if there are conditions associated with card transactions with acquirers.
+
+* The toggle switch is enabled, but it is not possible to finish the process
+
+If the message "Google Pay activated successfully." does not appear when activating the toggle switch, it means there may have been instability in the system. If the problem persists, the user will receive a message to contact [VTEX support](https://help.vtex.com/en/support).
+
+### Issues that may occur during the purchase process
+
+* The device used to complete the purchase does not support Google Pay
+
+If the message "Payment method not available in your browser" is displayed, the user must try to complete the purchase on another browser or device.
+
+* There are no rules configured for card payment in the store
+
+If a store has no card payment rules configured, the user will see an error message saying the method is not available when selecting Google Pay.
+
+### Learn more
+
+* [DPAN and FPAN: Understanding security in the online tokenized payment flow](https://help.vtex.com/en/tutorial/dpan-e-fpan-entendendo-a-seguranca-no-fluxo-de-pagamentos-tokenizados-online--3RM7RvhKZ057wja5xVEOqb)
+
diff --git a/docs/tracks/en/google-shopping-marketplace.md b/docs/tracks/en/google-shopping-marketplace.md
index a9530f603..d5f9a5b6b 100644
--- a/docs/tracks/en/google-shopping-marketplace.md
+++ b/docs/tracks/en/google-shopping-marketplace.md
@@ -3,8 +3,8 @@ title: 'Google Shopping'
 id: 2kGKxwD9HKJvTLDTikQ4zG
 status: PUBLISHED
 createdAt: 2021-04-14T14:19:25.417Z
-updatedAt: 2021-04-16T22:47:55.190Z
-publishedAt: 2021-04-16T22:47:55.190Z
+updatedAt: 2024-02-29T19:00:16.087Z
+publishedAt: 2024-02-29T19:00:16.087Z
 firstPublishedAt: 2021-04-15T17:41:07.946Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,7 +16,7 @@ trackSlugEN: integrating-with-google-shopping
 
 [Google Shopping](https://shopping.google.com/) is a platform that displays product offers in free, organic listings through Google searches. It is a price comparison and tracking service that displays local products for free in search results.
 
-![google-shopping](https://drive.google.com/uc?export=download&id=1htNbqBqTs4HSdnPnp4Q6__wDzMTYPl6-)
+![Google Shopping](//images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/93da7aae0e11388851c2d861817e73d5/logo_Google_shopping.png)
 
 Using Google Shopping, you can display to potential customers some of the attributes of your products, such as image, title, price, and the name of your store.
 
diff --git a/docs/tracks/en/hide-product-suggestions-recommendation.md b/docs/tracks/en/hide-product-suggestions-recommendation.md
index a4e273cd6..356ea7ac2 100644
--- a/docs/tracks/en/hide-product-suggestions-recommendation.md
+++ b/docs/tracks/en/hide-product-suggestions-recommendation.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-setup
 
 By default inStore includes a list of suggested products in the cart and in the product page.
 
-![inStore recommendation](https://images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
+![inStore recommendation](//images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
 
 If you want to hide the recommendations, you need to edit the `checkout-instore-custom.css` and `checkout-instore-custom.js` files in the Portal admin. This files are used across the application, so it is important that you have some programming knowledge before editing them, to avoid breaking other functionalities.
 
diff --git a/docs/tracks/en/how-a-split-payment-transaction-works.md b/docs/tracks/en/how-a-split-payment-transaction-works.md
index 3ca6b708c..0d0d45097 100644
--- a/docs/tracks/en/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/en/how-a-split-payment-transaction-works.md
@@ -59,4 +59,4 @@ The $ 6.50 will be split between the marketplace and the acquirer. As the MDR wa
 
 Check the diagram below:
 
-![Payment Split](https://images.ctfassets.net/alneenqid6w5/71DjeU0CjjxlDE1qrwr3n9/c228dc62dc40e68c34337c0d21fc8cce/Split-EN.png)
+![Payment Split](//images.ctfassets.net/alneenqid6w5/71DjeU0CjjxlDE1qrwr3n9/c228dc62dc40e68c34337c0d21fc8cce/Split-EN.png)
diff --git a/docs/tracks/en/how-does-vtex-intelligent-search-work.md b/docs/tracks/en/how-does-vtex-intelligent-search-work.md
index 0d159cd6f..db87fd382 100644
--- a/docs/tracks/en/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/en/how-does-vtex-intelligent-search-work.md
@@ -3,8 +3,8 @@ title: 'How does VTEX Intelligent Search work?'
 id: 23mytRDsEduqLO0Lo7yufy
 status: PUBLISHED
 createdAt: 2020-03-05T14:57:22.014Z
-updatedAt: 2023-04-13T23:00:35.423Z
-publishedAt: 2023-04-13T23:00:35.423Z
+updatedAt: 2024-04-25T16:53:08.559Z
+publishedAt: 2024-04-25T16:53:08.559Z
 firstPublishedAt: 2020-03-05T19:54:00.932Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -16,93 +16,134 @@ trackSlugEN: vtex-intelligent-search
 
 The Search Engine is the core of VTEX Intelligent Search's intelligence. It interprets the search term and displays a filtered and ordered list of products. This tool allows a more objective search through indexing and treatment of the catalog data.
 
-This feature is a default in VTEX Intelligent Search and covers the vast majority of scenarios. However, you can also adjust the Search Engine to improve search results.
+This feature is included by default in VTEX Intelligent Search and covers the vast majority of scenarios. However, you can also adjust the Search Engine to improve search results. This guide covers the following:
 
-There is a set of settings that change products displayed in search results and their order:  
+* [Standard search behavior](#standard-search-behavior)
+* [Search behavior configuration](#search-behavior-configuration)
+* [Alternative ways to search](#alternative-ways-to-search)
+* [Indexing](#indexing)
 
-- __Definition of search fields__: defines certain product information as searchable. With this configuration, every search performed verifies the contents of this field to assimilate the products. The __product name__, __brand__, __ProductID__, __ProductRefID__, __SKUID__, __SKURefID__, and __EAN__ fields are defined by default and cannot be changed. 
+## Standard search behavior
 
-  You can include special characters ( `-` and `/` ) when searching for a product.
+The following are characteristics of Intelligent Search's standard behavior.
 
- _For example_: the "color" field is set as configurable and the product was added with the name "Nike Total 90 Sneakers" and the color "black". If a customer searches for "Black Sneakers", the tool will return products that have the term "sneakers" and the color "black" at the top of search results.
+### Autocorrect
 
-- __Definition and sorting of filter fields__: in all search results, users can select filters. Some filters are pre-defined by default, but it is also possible to create them according to the store's needs. The display order is also customizable.
+Users can make spelling mistakes when searching. The tool interprets these misspellings and shows similar products.
 
- _Examples_: Price, Categories, and Brand.
+The search engine performs an automatic correction for each search based on the items added to the catalog. For each search term, a specific number of wrong characters is allowed. The number of accepted misspellings is called _fuzzy_.
 
-- __Autocorrect__: the user may make spelling mistakes when performing a search. The tool interprets these misspellings and shows similar products.
+The _fuzzy_ varies depending on the length of the search term. By default, if the term is 3 to 5 characters long, the _fuzzy_ applied will be 1, which means that 1 misspelled character is allowed. For terms of 6 characters or more, the _fuzzy_ applied will be 2.
 
- The Search Engine performs an automatic correction in each search. For each search term, a specific number of wrong characters is allowed. The number of accepted misspellings is called fuzzy.
+The predicted misspellings considering *fuzzy* = 1 are:
 
- The fuzzy varies according to the length of the search term. By default, if the term is 3 to 5 characters long, the fuzzy applied will be 1, which means that 1 misspelled character is allowed. For terms with 6 or more characters, the fuzzy used will be 2.
+* Add 1 more character.
+* Remove 1 character.
+* Change 1 character.
+* Swap 2 characters that are next to each other.
 
- The predicted misspellings considering ```fuzzy = 1``` are:
-   - Insert 1 extra character.
-   - Remove 1 character.
-   - Change 1 character.
-   - Exchange 2 characters that are side by side.
+Example: Suppose a customer wants to search for the term `ball`. Using the default configuration (*fuzzy* = 1 for terms of 3 to 5 characters), the search engine will return results for `ball` in any search that contains accepted errors, such as:
 
- _For example_:
- Suppose a customer wants to search for the term "case". Using the default configuration (```fuzzy = 1``` for terms of 3 to 5 characters), the Search Engine will show results for "case" in any search that contains accepted errors, such as:
-   - chase (insert 1 extra character)
-   - cae (remove 1 character)
-   - cast (change 1 character)
-   - csae (exchange 2 characters that are next to each other)
+* `bawll` (add 1 more character)
+* `bal` (remove 1 character)
+* `balk` (change 1 character)
+* `abll` (swap 2 characters next to each other)
 
-<div class="alert alert-info" role="alert">
-<p>Whitespace is not considered in fuzzy, so “base ball” will not be corrected to “baseball”. We recommend using synonyms for these cases.</p>
+<div class ="alert alert-info">
+  <p>Blank spaces are not considered in <em>fuzzy</em>, so <code>base ball</code> will not be corrected to <code>baseball</code>. We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">synonyms</a> for such cases.</p>
 </div>
 
-- __Relevance settings__: it is the ordering principle of search results. In this section, you can assign weights and prioritize certain criteria in the Search Engine, such as popularity, release date, and promotions. The relevance of a product is composed by the combination of weights and priorities defined by each retailer.
+### Minimum result
 
- _For example_: a retailer configured that "promotion" has greater relevance than other criteria. When a customer searches for "T-shirt", the tool might display the T-shirts on sale at the top of search results, depending on the weights assigned to other criteria.
+The minimum number of results displayed for any search is 1. If a search does not meet this minimum, [autocorrect](#autocorrect) is applied.
 
- For more information on how to customize the order of results according to your store's needs, read the article [Relevance settings](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+In a search with multiple terms, the following logic occurs:
 
-- __Minimum result__: allows you to set the minimum number of products for multi-term queries. If this number is not reached, the search returns more comprehensive results, considering only one of the searched terms.
+1. If the minimum result is not reached even after the initial autocorrect, the search starts to include more comprehensive results containing any of the search terms. For example, if a user searches for "nike sneakers" and the catalog doesn't have any products matching that name, the search will return products with only the term "sneakers" instead.
+2. If the comprehensive search doesn't return the minimum result, the process will be repeated, applying autocorrect again to each term.
 
- _For example_: it has been configured that the minimum result for multi-term queries is __three__. The user searched for "nike sneakers", but there is only __four__ products in the catalog with that name. The platform will first display products with the terms "nike sneakers", then products with the term "sneakers", and after that, those with the term "nike".
+<div class= "alert alert-warning">
+  <p>Searches with multiple terms are more efficient when customers sort the results by relevance, as such sorting can return more results than the initial search context. When sorted by relevance, items with multiple terms are prioritized. However, with other sorting criteria, such as price or bestsellers, the result ranking is based on these numerical values and does not necessarily prioritize items that match more search terms.</p>
+</div>
+
+### Pagination limit
+
+VTEX Intelligent Search limits the search results to 50 pages, which encourages the customer to use filters, creating a more relevant and focused experience.
+
+## Search behavior configuration
+
+There is a set of settings that change the products that are displayed in search results and their order. In the following sections, you will see the main definitions that affect search behavior.
+
+### Defining searchable fields
 
-- __Page limit__: limits search results to 50 pages. This feature encourages the customer to use filters, creating a more relevant and focused experience.
+Determines which product information is searchable. From this configuration, every search in the search bar checks the content of these fields to generate search results. Check the following table to understand which information is searchable by default and the other configuration options:
+
+| Information | Configuration |
+| - | - |
+| Product name, brand, product ID (`ProductID`), product reference code (`ProductRefID`), SKU ID (`SKUID`), SKU reference code (`SKURefID`), and EAN  | This information is searchable by default in VTEX Intelligent Search. To remove any of this information, please contact our [Support](https://help.vtex.com/support?/cultureInfo=en-us). |
+| Product and SKU specifications | To include the desired specifications as searchable fields, you must configure the **Searchable specifications** option in the VTEX Admin, under **Intelligent Search > Search Settings**.<br /><br /> For example, if a shirt doesn't have the color in the product name or SKU, by default, Intelligent Search won't identify this attribute in a search for "blue shirt", displaying shirts of different colors as results. However, if the color specification is configured as searchable, the search will likely return blue shirts at the top of search results.<br /><br /> For more details about defining searchable specifications, check out the [Search configuration](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#general-settings) guide. 
+<br /><br /> Learn more about specifications in [Product and SKU specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP). |
+| Manufacturer code (`ManufactureID`) | Please contact our [Support](https://help.vtex.com/support?/cultureInfo=en-us) to set this field as searchable. |
+
+For example: The "color" specification is set as searchable and the product was added with the name "Nike Total 90 Sneakers" and the color "black". If a customer searches for "Black Sneakers", the tool will return products that have the term "sneakers" and the color "black" at the top of search results.
+
+You can include special characters ( `-` and `/`) when searching for a product.
 
 <div class="alert alert-warning">
-  <p>The VTEX Intelligent Search does not offer the functionality of substitute words natively. To enable the use of substitute words with VTEX Intelligent Search, please contact <a href="https://support.vtex.com/hc/en-us/requests">our support</a>.</p>
+	<p>Choosing the search fields affects the <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">merchandising rule</a> options, as only searchable fields can be used to set up the rules. For example, if you set only the <strong><code>SKUID</code></strong> field as searchable, you cannot promote a<strong><code> ProductID</code></strong> or a <strong><code>ProductRefID</code></strong> using merchandising rules. </p>
+</div>
+
+### Defining and sorting filter fields
+
+In all search results, users can select filters. Some filters are pre-defined by default, but it is also possible to create more filters to meet  store needs. The display order is also customizable. Example: In a search results list, there can be filters for Price, Categories, and Brand.
+
+### Configuring relevance
+
+Relevance is the ordering principle of search results. In this section, you can assign weights and prioritize certain criteria in the Search Engine, such as popularity, release date, and promotions. The relevance of a product is composed by the combination of weights and priorities defined by each merchant.
+
+_For example_: a merchant configured that "promotion" has greater relevance than other criteria. When a customer searches for "t-shirt", the tool might display the t-shirts on sale at the top of search results, depending on the weights assigned to other criteria.
+
+For more information on how to customize the order of results to meet your store's needs, read the article [Relevance settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+<div class="alert alert-info">
+	<p>When using Intelligent Search, two options define the sorting order of your collections. By using the <code>map=productClusterIds</code> command, you are setting the order of your collections to be the one pre-defined by the merchant, with its relevance criteria. If you choose to use <code>productClusterNames</code>, you are setting that you want your collections to follow Intelligent Search's own relevance standards.</p>
 </div>
 
 ## Alternative ways to search
 
-You can search for IDs in the store URL bar or in the search bar. In addition, you can search for just one item or for a list of items. 
+It is possible to search by the ID of one or more items in the search bar or by adding search parameters (*query*) in the store URL.
+
+### Partial match
 
-To search in your store URL bar, follow the format below:
+By entering the exact first digits of the product ID (`ProductID`), product reference code (`ProductRefID`), SKU ID (`SKUID`), SKU reference code (`SKURefID`), or EAN in the search bar, Intelligent Search will partially match products and SKUs active in the store, adding them to the search results.
+
+For example, if the product ID is `123456789` and you search for `123`, it will be listed in the search results. However, the product will not be displayed if the search is `234` and does not include any of the first ID numbers.
+
+### URL
+
+To search from your store URL, add search parameters (*query*) at the end of the store URL, respecting one of the following structures:
 
 - Example for searching an item: `[account address]/[id type]:[id_1]?q=[id type]&map=ft`
 - Example for searching a list: `[account address]/[id type]:[id_1];[id_2];[id_3]?q=[id type]:[id_1];[id_2];[id_3]&map=ft`
 
-The possible value types for the ID type field are `product.id`, `sku.id`,`sku.ean`, `sku.reference` or `id` (ProductID, ProductRefID, SKUID, SKURefID and EAN). It is important that all IDs belong to the same type.
+The possible value types for the ID type field are `product.id`, `sku.id`,`sku.ean`, `sku.reference`, or `id` (ProductID, ProductRefID, SKUID, SKURefID, and EAN). All searched IDs should be of the same type.   
 
-You can search for IDs in the search bar in the following ways:
-
-1. By typing only the first digits of the ID in the search bar. Please note that the search must be exact: for example, if the ID is `0123-456-789` and you search for `123`, the product will not be displayed.
-2. By queries, following the format below:
-  - **Search by SKU ID:** `?q=sku.id:<id>` or `?q=sku:<id>` 
-  - **Search by EAN:** `?q=sku.ean:<id>` 
-  - **Search by reference ID:** `?q=sku.reference:<id>` 
-  - **Search by slug:** `?q=product.link:<link>` 
-  - **Search by product ID:** `?q=product:<id>` or `?q=product.id:<id>`
+- **Search by SKU ID:**  `?q=sku.id:<id>` or `?q=sku:<id>`
+- **Search by EAN:**  `?q=sku.ean:<id>`
+- **Search by reference ID:**  `?q=sku.reference:<id>`
+- **Search by slug:**  `?q=product.link:<link>`
+- **Search by product ID:**  `?q=product:<id>` or `?q=product.id:<id>`
 
 ## Indexing
 
-Indexing is the process of sync between store and search catalogs. This feature allows you to keep your content up to date with continuous updates of the product index. It also performs data processing to be used in the search.
+Indexing is the syncing process between store and search catalogs. This feature allows you to keep your content up to date with continuous updates of the product index. It also performs data processing to be used in the search.
 
-Initially, it synchronizes all the products from your VTEX catalog. After that, data changes — such as product name and status —  are updated in real time by the search indexer.
+Initially, it syncs all the products from your VTEX catalog. After that, data changes — such as product name and status — are updated in real time by the search indexer.
 
-In this synchronization process, the system queues up the information that has been updated to add it to the search catalog. Once all changes have been indexed, they will be available on the website. 
+In this sync process, the system queues up the information that has been updated to add it to the search catalog. Once all changes have been indexed, they will be available on the website.
 
-Indexing process is safe and has a retry mechanism — if an item is not indexed on the first attempt, the system makes subsequent attempts until it is successfully completed. 
+The indexing process is safe and has a retry mechanism — if an item is not indexed on the first attempt, the system makes subsequent attempts until it is successfully completed.
 
 Indexing is fundamental to analyze, process, and organize data as best as possible to improve your search results.
 
-<div class="alert alert-info" role="alert">
-<p>When using Intelligent Search, two commands can define the order of your collections. Using the command `map=productClusterIds` defines that the order of your collections will be defined by your own relevance rule. If you choose to use  `productClusterNames`, you’ll define that you want your collections to follow Intelligent Search’s relevance standards.  </p>
-</div>
-
+Check [Indexing History](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) for more information on how to monitor the indexing process.
diff --git a/docs/tracks/en/how-the-payments-module-works.md b/docs/tracks/en/how-the-payments-module-works.md
index 018f60b18..9e458928e 100644
--- a/docs/tracks/en/how-the-payments-module-works.md
+++ b/docs/tracks/en/how-the-payments-module-works.md
@@ -3,8 +3,8 @@ title: 'How the payments module works'
 id: kdPbEIWf8Xq8tESQvViMB
 status: PUBLISHED
 createdAt: 2019-11-13T18:30:00.279Z
-updatedAt: 2021-09-21T14:41:47.003Z
-publishedAt: 2021-09-21T14:41:47.003Z
+updatedAt: 2024-07-24T18:38:45.637Z
+publishedAt: 2024-07-24T18:38:45.637Z
 firstPublishedAt: 2019-11-21T22:49:51.417Z
 contentType: trackArticle
 productTeam: Financial
@@ -24,15 +24,15 @@ It is important to remember that each store has its own particularities and its
 
 ## Gateway 
 
-A gateway (also called a payment gateway) is a _system that transmits the data of purchases made in your store at checkout_.
+A gateway (also called a payment gateway) is a system that transmits the data of purchases made in your store at checkout.
 
 As the first player in the flow, it is responsible for sending the payment information - received at checkout - to the financial actors included in the payment flow sequence (such as acquirers, card brands, and issuing banks).
 
 Then it gets a response on the payment approval and continuation of the purchase flow, or its cancellation.
 
-As intermediaries between an e-commerce and its means of payment, **gateways** _act as a terminal_, integrating  all transactions made between players in the payment flow in one place.
+As intermediaries between an e-commerce and its means of payment, **gateways** act as a terminal, integrating  all transactions made between players in the payment flow in one place.
 
-> Examples of gateways: Braspag and Mundipagg.
+Gateways examples: Pagar.me and Stripe.
 
 ## Acquirer 
 
@@ -42,22 +42,22 @@ Through its network of accredited partners (or acquiring network), it enables a
 
 When everything is in order and a purchase is authorized by the other players in the purchase flow, the acquirer is responsible for transferring the amounts (charged from the customer by the issuing bank) to your store account.
 
-> Examples of acquirers: Rede, Cielo, GetNet and Stone.
+Acquirers examples: Rede, Cielo, GetNet and Stone.
 
 ## Sub-acquirer  
 
-A sub-acquirer is a _company that processes payments and transmits the generated data to the other players involved in the payment flow_.
+A sub-acquirer is a company that processes payments and transmits the generated data to the other players involved in the payment flow.
 
 As a facilitator, its role is similar to that of an acquirer, but it does not completely replace it because it lacks the autonomy to perform all of an acquirer's features.
 
 Therefore, the **sub-acquirer** can be considered an middleman between acquirer and store.
 
-> Examples of sub-acquirers: Paypal and PagSeguro.
+Sub-acquirers examples: Paypal and PagSeguro.
 
 To learn more about the [advantages and disadvantages of including a sub-acquirer in your flow](https://help.vtex.com/en/tutorial/difference-between-acquires-sub-acquirers-and-gateways--1dyPJ3gQCCO4ea2o6OMgCi), check out our article.
 
 ## Card brands
-Card brands are _companies that are responsible for defining the business rules for purchases made with credit cards_, such as the number of installments you can split a payment on and the facilities in which it is accepted, nationally and internationally.
+Card brands are companies that are responsible for defining the business rules for purchases made with credit cards_, such as the number of installments you can split a payment on and the facilities in which it is accepted, nationally and internationally.
 
 They set the standards by which acquirers must process transactions made through this payment method.
 
@@ -65,28 +65,28 @@ In the credit card payment flow, the **brand** receives information from the acq
 
 Thus, the brand serves both to regulate the use of the card and as a bridge between the acquirer and the bank.
 
-> Examples of card brands: Mastercard, American Express and Visa.
+Card brands examples: Mastercard, American Express and Visa.
 
 ## Issuing banks
-An issuing Bank is a _financial institution that is responsible for the means of payment, whether they are "boleto" (popular Brazilian off-line payment method), debit or credit cards_.
+An issuing Bank is a financial institution that is responsible for the means of payment, whether they are "boleto" (popular Brazilian off-line payment method), debit or credit cards.
 
 Upon receiving the data from a purchase made in your store, it will authorize the sale or not, depending on the credit limit or the money available in the user account.
 
 At VTEX, you can configure special conditions for payments made through specific **banks**, a feature that we will explore later.
 
-> Examples of issuing banks: Itaú, Santander, Bradesco and Citibank.
+Issuing banks examples: Itaú, Santander, Bradesco and Citibank.
 
 ## Anti-fraud
-Anti-fraud is a _system specialized in analyzing purchases made on websites in order to identify fraudulent transactions_.
+Anti-fraud is a system specialized in analyzing purchases made on websites in order to identify fraudulent transactions.
 
 It collects data on user behavior and compares it with suspicious standards, to then approve or deny the order. Thus, **anti-fraud** adds an extra layer of security to your store.
 
-> Examples of anti-fraud: ClearSale and Konduto.
+Anti-fraud examples: ClearSale and Konduto.
 
 ## PCI SSC certification
-PCI Security Standards Council is an _open global forum for the continued development, enhancement, storage, dissemination and implementation of data protection security standards_.
+PCI Security Standards Council is an open global forum for the continued development, enhancement, storage, dissemination and implementation of data protection security standards.
 
 [The VTEX platform has its own **PCI-certified** gateway](https://help.vtex.com/en/tutorial/what-is-pci-ssc--4jo3Vkox3amSO2w4qIWa0E "PCI SSC"), meaning that data from all payments made in your store is protected according to the highest security standards.
 
-> __If you want to learn more about the concepts of gateway, acquirer, sub-acquirer, brand, issuing banks and anti-fraud, check out our [article on financial agents in Brazil](https://help.vtex.com/en/tutorial/financial-agents-explained--1dyPJ3gQCCO4ea2o6OMgCi).
+If you want to learn more about the concepts of gateway, acquirer, sub-acquirer, brand, issuing banks and anti-fraud, check out our [article on financial agents in Brazil](https://help.vtex.com/en/tutorial/financial-agents-explained--1dyPJ3gQCCO4ea2o6OMgCi).
 
diff --git a/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md b/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md
index e0a99f2a2..f0778742c 100644
--- a/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md
+++ b/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md
@@ -33,7 +33,7 @@ After reloading the inStore, when you print an order you will see that extra tex
 Quick Example:
 
 Before adding the extra text we would have an impression as follows:
-![inStore recommended text before](https://images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
+![inStore recommended text before](//images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
 
 By changing the `checkout-instore-custom.js` file by putting the following extra text:
 
@@ -44,4 +44,4 @@ window.INSTORE_CONFIG = {
 ```
 
 Now when the order is printed, we will have:
-![inStore recommended text after](https://images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
+![inStore recommended text after](//images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
diff --git a/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md b/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md
index 2073d83fd..a97680411 100644
--- a/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md
+++ b/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-setup
 
 If you have set up your store using the __Easy Setup__ flow, a store for you has already been created in the __Stores Admin__ within VTEX VTable (https://{{AccountName}}.myvtex.com/admin/vtable).
 
-![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Click __Stores Admin__ to open the table where you will see the physical stores.
 
@@ -24,7 +24,7 @@ If you have not used the __Easy Setup__ and so don't see any registered stores,
 
 If you have already registered a store through __Easy Setup__, you will see the registry of this store created as in the following image.
 
-![vtable-admin-das-lojas-2](https://images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
+![vtable-admin-das-lojas-2](//images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
 
 To change any data, including the store's sales policy, simply change the related cell and then click the __Save__ button.
 
diff --git a/docs/tracks/en/how-to-configure-a-custom-payment.md b/docs/tracks/en/how-to-configure-a-custom-payment.md
index b8003f8ba..99c20f72e 100644
--- a/docs/tracks/en/how-to-configure-a-custom-payment.md
+++ b/docs/tracks/en/how-to-configure-a-custom-payment.md
@@ -3,8 +3,8 @@ title: 'How to configure a custom payment'
 id: 1wWt35dRwEboRs1nrSx7G0
 status: PUBLISHED
 createdAt: 2019-11-12T14:02:06.237Z
-updatedAt: 2023-03-21T19:57:00.742Z
-publishedAt: 2023-03-21T19:57:00.742Z
+updatedAt: 2023-10-18T14:41:42.080Z
+publishedAt: 2023-10-18T14:41:42.080Z
 firstPublishedAt: 2019-11-25T15:33:37.696Z
 contentType: trackArticle
 productTeam: Financial
@@ -18,8 +18,8 @@ The custom payment is an alternative to the standard options offered by Payments
 
 These payment methods are separated into three categories, and each category allows five configurations.
 
-## Promissory notes
-A promissory note is a promise of payment that needs manual approval of the seller to perform the transaction. It is often used to provide payment through money.
+## Notes Payable
+A Note Payable is a promise of payment that needs manual approval of the seller to perform the transaction. It is often used to provide payment through money.
 
 ## Store Cards (Own Brand)
 It allows the use of a store's credit card with its own brand.
diff --git a/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
index 1d6b56d1f..f50a6f3fe 100644
--- a/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
@@ -27,7 +27,7 @@ Today this configuration is included in the portal administrator, more specifica
 
 To enable the _“Configure device”_ option, you must find the **_window.INSTORE_CONFIG_** object present in this file and add the **_configureDeviceEnabled_** property with the value **_true_**, and also add the **_printingConfig_** object to the **_printByBroker_** property with the value true, so that inStore allows you to use the option within the menu, as shown in the example image below:
 
-![EN-Configurar dispositivo](https://images.ctfassets.net/alneenqid6w5/7sjOnFRRd3FFBFM4MQej7m/692f871ee51737c132a6df68e39591bd/EN-Configurar_dispositivo.png)
+![EN-Configurar dispositivo](//images.ctfassets.net/alneenqid6w5/7sjOnFRRd3FFBFM4MQej7m/692f871ee51737c132a6df68e39591bd/EN-Configurar_dispositivo.png)
 
 Do not delete any of the other properties included in this object. The result should be something like:
 
@@ -64,7 +64,7 @@ printPageAutomatically: true
   3. In the “Settings” block inside the inStore menu, the option “Configure device” should appear. Click there.
   4. You will find the summary of the configured device. If this is the first time, the information will be empty. If a device has been configured previously, some information about the device will appear _(Device Name and Standard Printer)_. Click on the "Edit" option.
   
-![EN-Device via Broadcast](https://images.ctfassets.net/alneenqid6w5/7DuIhb5gjLHpCoLx48DMvl/d51a551e1d23f6dae131ec9b34c184b7/EN-Device_via_Broadcast.png)
+![EN-Device via Broadcast](//images.ctfassets.net/alneenqid6w5/7DuIhb5gjLHpCoLx48DMvl/d51a551e1d23f6dae131ec9b34c184b7/EN-Device_via_Broadcast.png)
 
   5. A form will appear indicating the data of _AppKey_, _AppToken_ and the name by which you want to identify the device. After entering this data, click on “Configure”.
   6. Finally, after including the above data, it will be possible to select the printer from the list of options. The idea is to select one of these options and then click on “Configure” again.
diff --git a/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
index e907de240..fb2e1071d 100644
--- a/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
@@ -3,8 +3,8 @@ title: 'How to create and edit transactional email templates'
 id: 335JZKUYgvYlGOJgvJYxRO
 status: PUBLISHED
 createdAt: 2020-01-10T13:13:48.069Z
-updatedAt: 2021-02-11T13:19:34.511Z
-publishedAt: 2021-02-11T13:19:34.511Z
+updatedAt: 2024-06-11T19:54:28.554Z
+publishedAt: 2024-06-11T19:54:28.554Z
 firstPublishedAt: 2020-01-13T14:38:32.506Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -23,6 +23,10 @@ To edit a transactional email template, follow the steps below.
 3. Change the e-mail title and the recipient (values bounded by double braces are variable; in the next article we will learn how to handle them). You can add recipients on Carbon Copy (`CC`) and Blind Carbon Copy (`CCO`).  
 4. Check the box __Use default sender__ to use the registered email address as default, as explained in the previous article on this track.
 
+<div class = "alert alert-info">
+The list of templates is available in the article <a href="https://help.vtex.com/en/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">Order transactional email templates</a>.
+</div>
+
 In the __HTML__ field you will find the template's HTML code. You can edit the code in the field itself or copy it to an editor of your choice, edit it and then paste it back into the template field.
 
 The __preview__ rendered by this code is shown in the box below the HTML field. You can choose between three different screen sizes to test code responsiveness.
diff --git a/docs/tracks/en/how-vtex-support-works.md b/docs/tracks/en/how-vtex-support-works.md
new file mode 100644
index 000000000..63dd647b6
--- /dev/null
+++ b/docs/tracks/en/how-vtex-support-works.md
@@ -0,0 +1,43 @@
+---
+title: 'How VTEX Support works'
+id: 2Ik9CGbPeZIHHaYFsuyId3
+status: PUBLISHED
+createdAt: 2024-02-20T21:27:52.565Z
+updatedAt: 2024-02-22T14:09:20.551Z
+publishedAt: 2024-02-22T14:09:20.551Z
+firstPublishedAt: 2024-02-22T14:09:20.551Z
+contentType: trackArticle
+productTeam: Others
+slug: how-vtex-support-works
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+VTEX Support is provided online and allows you to open tickets with different priority levels, depending on your store location. Tickets can be opened on the [support page](https://help.vtex.com/en/support), which requires [user account authentication](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz#setting-roles-and-permissions-for-users). Three authentication methods are available:
+
+- Token received via the email added to the store.
+- Login using a Google account.
+- Email and password with two-factor authentication via app or SMS.
+
+<div class = "alert alert-warning">
+To get authentication authorization, the <a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512">user</a> must have access to the VTEX Admin and a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role </a>
+ associated with <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager resources. </a>.
+</div>
+
+VTEX Support is divided in regions, and each region has its own service level agreement (SLA), priority, and Customer Excellence (CX) team available for that region. These are the regions where support operates:
+
+- Brazil
+- Latin America (LATAM, except Brazil)
+- Asia-Pacific (APAC)
+- United States (US)
+- Europe, the Middle East and Africa (EMEA)
+
+The following table shows an overview of the Help Center's main articles by region:
+
+| **Region**        | **Help Center article**     |
+|-------------------|-----------------------------|
+| Global            | **Article:** [How does VTEX support work?](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe)<br><br>  It explains how support works globally, covering ticket management, regional schedules, satisfaction surveys, and services such as monitoring. It also includes resources such as the Help Center, Developer Portal, and announcements about platform updates. |
+| Brazil only       | **Article:** [VTEX Support - Brazil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)<br><br>  It shows the availability, SLA, and resources available to clients in Brazil. |
+| United States only | **Article:** [VTEX Support - United States](https://help.vtex.com/en/faq/vtex-support-united-states--Bm45YFp68QRe1Z5r2oa07)<br><br>  It shows the availability, SLA, and resources available to clients in the United States. Available only in English. |
+| Europe, the Middle East and Africa (EMEA) only | **Article:** [VTEX Support - EMEA](https://help.vtex.com/en/faq/suporte-vtex-emea--5ePu2qkCfmE0IEKDFKg53F)<br><br>  It shows availability, SLA, and resources available to clients in the EMEA region. Available only in English. |
diff --git a/docs/tracks/en/import-orders-from-lengow.md b/docs/tracks/en/import-orders-from-lengow.md
index 8da3bcebf..e2931090e 100644
--- a/docs/tracks/en/import-orders-from-lengow.md
+++ b/docs/tracks/en/import-orders-from-lengow.md
@@ -30,6 +30,6 @@ To import orders automatically, use any scheduling service to perform a periodic
 
 The image below provides an example of what that would look like in [EasyCron](https://www.easycron.com/):
 
-![Lengow - EasyCron](https://images.ctfassets.net/alneenqid6w5/34iwIOlV3gTIxg8JipHwu5/4d5e6b4419ea69cb66dddb923082b374/image14.png)
+![Lengow - EasyCron](//images.ctfassets.net/alneenqid6w5/34iwIOlV3gTIxg8JipHwu5/4d5e6b4419ea69cb66dddb923082b374/image14.png)
 
 For more information on how to set up cron jobs using EasyCron, refer to the [FAQ](https://www.easycron.com/faq) available in their website.
diff --git a/docs/tracks/en/including-order-variables-in-email-template.md b/docs/tracks/en/including-order-variables-in-email-template.md
index 4c0ecd742..72fac66f0 100644
--- a/docs/tracks/en/including-order-variables-in-email-template.md
+++ b/docs/tracks/en/including-order-variables-in-email-template.md
@@ -30,7 +30,7 @@ Let's say you want to enter the carrier's name in the order sent email.
 
 To do this, go to the order sent template and, in the __JSON Data__ field, look for the `courier` property.
 
-![EN Incluir variáveis do pedido no template de e-mail - 1](https://images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/338873a8e5b2558b0fa0df9c2bc3b4c6/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)
+![EN Incluir variáveis do pedido no template de e-mail - 1](//images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/338873a8e5b2558b0fa0df9c2bc3b4c6/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)
 
 The value entered for this property is just an example, but you can use it in the __HTML__ field so that when the email is sent, the customer will see the carrier actually responsible for delivering the order.
 
@@ -38,6 +38,6 @@ Note that the `courier` property is inside the `package` object. Therefore, you
 
 `{{package.courier}}`
 
-![EN Incluir variáveis do pedido no template de e-mail - 2](https://images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/cf78d7e9f4408c7eec101e5768aaef4b/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)
+![EN Incluir variáveis do pedido no template de e-mail - 2](//images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/cf78d7e9f4408c7eec101e5768aaef4b/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)
 
 See that the example value ("Carrier Teste Courier S.A.") was inserted in the preview screen, below the __HTML__ and __JSON Data__ fields.
diff --git a/docs/tracks/en/indexing-history.md b/docs/tracks/en/indexing-history.md
new file mode 100644
index 000000000..04ac40139
--- /dev/null
+++ b/docs/tracks/en/indexing-history.md
@@ -0,0 +1,66 @@
+---
+title: 'Indexing History'
+id: 4flMwTaQL8FRKl1YT58ezH
+status: PUBLISHED
+createdAt: 2020-04-14T13:33:20.167Z
+updatedAt: 2023-07-13T19:35:40.455Z
+publishedAt: 2023-07-13T19:35:40.455Z
+firstPublishedAt: 2020-04-14T23:55:09.210Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: indexing-history
+locale: en
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugEN: vtex-intelligent-search
+---
+
+**Indexing history** is the page that monitors the synchronization status of all products in the Catalog sent to Intelligent Search. It provides a broad view of the indexing progress of your store.
+
+![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+
+The **Indexing status** section displays the following information:
+
+* **Average indexing time:** The average time for products to be indexed, from the time the system received the change notification to the in-store update. Indexing time performance is measured by a green (healthy) or red (bad) dot. 
+![Historico Indexação 2 - EN](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
+* **Products in store:** Quantity of products with up-to-date information currently displayed in the store.
+* **Indexing status share:** The percentage of products in each indexing step. Status breakdown performance is measured by a green (healthy) or red (bad) dot. The steps displayed are:
+    * **Updated:** Latest product update has been entered in the store.
+    * **Updating:** New product information is being prepared and entered into the store.
+    * **Error**: Means that an error occurred during indexing. There was a problem adding the product and it cannot be indexed. If it is a new product, it will not be available in the store.
+
+You can filter the list of indexed products for a custom view. It is important to note that the average indexing time and status breakdown will be recalculated from the products filtered. 
+
+To filter the list of indexed products, click on `Filter` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
+
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
+
+If you filter by `Status` you can select which status you want to filter by, which could be `Updated`, `Updating`, `Error`.
+
+![Historico indexação 4 - EN](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
+
+If you filter by `Indexing time` you can select whether the time interval `Is greater than`, `Is equal to or greater than`, `Is shorter than` or `Is equal to or less than` a defined time.
+
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
+
+After defining the filter, click `Apply` to activate it. 
+
+To add a new filter, click <i class="fa-solid fa-plus"></i> `Add filter`. To remove the configured filters, click `Clear filters`.
+
+You can also filter the products displayed in the listing by **ID**, **Last update** and **Status**, by clicking on the desired column. To find a specific product in the list, you can search by ID in the search bar.
+
+If you want more information about the indexing of a specific product, you can click on the product row in the table to access a page that contains more details, as illustrated below.
+
+![Historico indexação 6 - EN](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
+
+In addition to the information displayed in the product list, you can also see:
+
+* **Indexing time:** Is an entry of how long the product indexing lasted using the `hh:mm:ss` format`.
+* **Indexing timeline:** Shows a log of every status change with date and time. You can view more details of each step by clicking the <i class="fa-solid fa-chevron-down"></i> icon.
+
+![Historico indexação 7 - EN](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
+
+It is possible to manually reindex a product without having to update the entry. To reindex a product, click <i class="fa-solid fa-arrows-rotate"></i> `Reindex`. Only products in **Updated** status can be indexed.
+
+You can access the product **Indexing history**, a list with the date and time of each update performed. Therefore, it is possible to have a record of every change that was made to the product. To access it, click <i class="fa-solid fa-arrows-rotate"></i> `History`. 
+
+![Histórico da Indexação 8 - EN](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
diff --git a/docs/tracks/en/initializing-your-store-theme.md b/docs/tracks/en/initializing-your-store-theme.md
index ceb1cb6ce..ea7a3e527 100644
--- a/docs/tracks/en/initializing-your-store-theme.md
+++ b/docs/tracks/en/initializing-your-store-theme.md
@@ -27,7 +27,7 @@ Select `store-theme` and confirm that you would like to download the template pr
 
 You will then be asked important app meta information like this app's vendor, name, title, and description. Use the __account name__ you're developing in as the __vendor__. This is important so you can correctly publish this app in this account later. You can use the default values by pressing enter.
 
-![store-theme](https://images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
+![store-theme](//images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
 
 ## Understanding the app structure
 
@@ -86,7 +86,7 @@ During a `link`, any changes you make to your code are automatically uploaded an
 
 Run `vtex link`  and watch your template app be compiled and published to the account and workspace you just created.
 
-![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
+![vtex-link](//images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
 <div class="alert alert-info">
 Remember: run <code>vtex whoami</code> to make sure you are in the correct account and in a test workspace, otherwise <code>VTEX Toolbelt</code> will complain about linking directly to master.
@@ -104,4 +104,4 @@ The `{{account}}.myvtex.com` is your private domain for testing new workspaces,
 
 Congratulations on linking your first VTEX IO App!
 
-![dreamstore](https://images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
+![dreamstore](//images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
diff --git a/docs/tracks/en/inserting-and-configuring-placeholders.md b/docs/tracks/en/inserting-and-configuring-placeholders.md
index 23e07b877..8d5674556 100644
--- a/docs/tracks/en/inserting-and-configuring-placeholders.md
+++ b/docs/tracks/en/inserting-and-configuring-placeholders.md
@@ -35,14 +35,14 @@ It creates a configurable element in the part of the code where it is inserted.
 It is important to enter an `id` value. It will be the identifier of that placeholder in the system.
 
 
-![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configuring the placeholder
 
 Once the placeholder control has been inserted into the template, you can configure it in the settings of the layout that uses this template.
 
 1. Open the layout and then click on the **Settings** tab. The new placeholder should appear there, with the name equal to the id value defined in the control. For now, this placeholder is empty, meaning there are no objects inside it.
-![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. To insert an object, click on **add object**.
 3. Then choose the object type and click on the **Add** button.
 4. Finally, click on the **Save Settings** button.
@@ -51,7 +51,7 @@ You can now edit the object inserted in the placeholder.
 
 To do this, click on the pencil icon inside the object, and then click on **add content**.
 
-![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 You can now name this object, upload images to it and configure the conditions under which it will be rendered.
 
diff --git a/docs/tracks/en/installation-and-setup.md b/docs/tracks/en/installation-and-setup.md
index 89c52114f..6590fd91b 100644
--- a/docs/tracks/en/installation-and-setup.md
+++ b/docs/tracks/en/installation-and-setup.md
@@ -40,13 +40,13 @@ To get started, we will fill out basic settings that allow VTEX and Lengow to co
 
 Once this is done, as seen in the image below, press **Save** to store the settings and move on to the next step.
 
-![Lengow Basic Setup](https://images.ctfassets.net/alneenqid6w5/47hHUySqAFsoAXKSX0ec8N/9be820ddefcc9e6893c634d7fe627b16/Screen_Shot_2020-07-01_at_22.44.34.png)
+![Lengow Basic Setup](//images.ctfassets.net/alneenqid6w5/47hHUySqAFsoAXKSX0ec8N/9be820ddefcc9e6893c634d7fe627b16/Screen_Shot_2020-07-01_at_22.44.34.png)
 
 ### Configure VTEX affiliate for Lengow
 
 To fill out the **Prefix to imported orders - Affilitiate ID** field you should configure an [affiliate](https://help.vtex.com/en/tutorial/configuring-affiliates--tutorials_187) for the Lengow connector in *Orders > Orders Management > Settings*. We recommend using the settings below, with LNG as the affiliate ID and your own e-mail address for notifications.
 
-![Lengow affiliate](https://images.ctfassets.net/alneenqid6w5/7384AJaO2ZFcECDGFqWHPT/78a10bd0370a43cdd65116f067fc814c/image9.png)
+![Lengow affiliate](//images.ctfassets.net/alneenqid6w5/7384AJaO2ZFcECDGFqWHPT/78a10bd0370a43cdd65116f067fc814c/image9.png)
 
 ### Get Lengow authentication credentials
 
@@ -55,7 +55,7 @@ You can find the information needed to fill out the **Lengow Account**, **Lengow
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/5RhkmJ5MSU7IAqKeaeIHOt/1a047d143644b5ede26e54ff0248d609/image10.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Lengow Account ID" title="Lengow Account ID">
+    <img src="https://images.ctfassets.net/alneenqid6w5/5RhkmJ5MSU7IAqKeaeIHOt/1a047d143644b5ede26e54ff0248d609/image10.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Lengow Account ID" title="Lengow Account ID">
    </td>
   </tr>
   <tr>
@@ -70,7 +70,7 @@ You can find the information needed to fill out the **Lengow Account**, **Lengow
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/4VSUTXCPjvJrDztQPuTHa7/114b813e20818cd9058ea47295f74f0c/image13.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Lengow API KEY / Secret" title="Lengow API KEY / Secret">
+    <img src="https://images.ctfassets.net/alneenqid6w5/4VSUTXCPjvJrDztQPuTHa7/114b813e20818cd9058ea47295f74f0c/image13.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Lengow API KEY / Secret" title="Lengow API KEY / Secret">
    </td>
   </tr>
   <tr>
diff --git a/docs/tracks/en/installing-customer-credit.md b/docs/tracks/en/installing-customer-credit.md
index 71e33a747..7d8c8e83f 100644
--- a/docs/tracks/en/installing-customer-credit.md
+++ b/docs/tracks/en/installing-customer-credit.md
@@ -3,8 +3,8 @@ title: ' Installing Customer Credit'
 id: 36grlQ69NK6OCuioeekyCs
 status: PUBLISHED
 createdAt: 2018-11-06T19:45:12.804Z
-updatedAt: 2020-08-17T22:17:50.649Z
-publishedAt: 2020-08-17T22:17:50.649Z
+updatedAt: 2024-02-08T11:31:30.622Z
+publishedAt: 2024-02-08T11:31:30.622Z
 firstPublishedAt: 2018-11-06T20:24:15.191Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,20 +14,14 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugEN: customer-credit-getting-started
 ---
 
-In this track, we will explain the step by step to install and configure Customer Credit.
+In this track you will find step-by-step instructions for installing and configuring the Customer Credit app. For more information about this app, visit [Customer Credit - Overview](https://help.vtex.com/en/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0).
 
-First of all, if this app’s concepts are new to you, we recommend that you read our article on [Customer Credit’s general concepts](https://help.vtex.com/en/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0).
+To install Customer Credit in your store, follow the steps below:
 
-After reading it, you should be able to make purchases at VTEX stores using Customer Credit as a payment method.
+1. In the VTEX Admin, go to __Applications > Extensions Hub > App Store__, or type __App Store__ in the search bar at the top of the page.
+2. Type __Customer Credit__ in the search bar on the App Store page and click on the app icon.
+3. Click on the `Get App` button.
+4. Then click `Install App` and `INSTALL`.
+5. Refresh the page (by pressing the __F5__ key or your browser's refresh button).
 
-This way, we can proceed to the first step, which is installing the app. Check out the walk-through below:
-
-1. Access the VTEX [App Store](https://apps.vtex.com/ "App Store") page;
-2. Find the __Customer Credit__ icon;
-3. Click on the __“Get”__ button;
-4. Fill in the __Account info__ field with your store's __"Account Name"__;
-5. Click on the __“Confirm order and begin installation”__ button.
-
-You will then be redirected to your store's Admin. Log in and complete the installation by clicking on the “Install” button, located in the upper right corner of the screen.
-
-With the app installed, the new Customer Credit section will appear in the Admin, within the Transactions module.
+After the page loads, the new Customer Credit section can be accessed in the VTEX Admin under __Apps > Customer Credit__.
diff --git a/docs/tracks/en/instore-basic-settings.md b/docs/tracks/en/instore-basic-settings.md
index e092d441f..8b55f586e 100644
--- a/docs/tracks/en/instore-basic-settings.md
+++ b/docs/tracks/en/instore-basic-settings.md
@@ -3,8 +3,8 @@ title: 'VTEX Sales App - Basic settings'
 id: 4L5SoLxE8O3YkxF7FKymrO
 status: PUBLISHED
 createdAt: 2020-06-28T13:51:53.895Z
-updatedAt: 2023-05-31T15:55:29.064Z
-publishedAt: 2023-05-31T15:55:29.064Z
+updatedAt: 2023-07-26T18:42:22.814Z
+publishedAt: 2023-07-26T18:42:22.814Z
 firstPublishedAt: 2020-06-28T14:01:36.462Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/en/instore-customizations.md b/docs/tracks/en/instore-customizations.md
index e8cc1588b..1ef5eaa1e 100644
--- a/docs/tracks/en/instore-customizations.md
+++ b/docs/tracks/en/instore-customizations.md
@@ -36,11 +36,11 @@ Alternatively, you can browse to the configuration file from the VTEX Admin home
 
 In the main menu, click on __Checkout__ and then click on the store's gear symbol, as shown in the image below.
 
-![20. inStore Customizations - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6AXuX4eeuPus1uiuyFcXkp/ce21c3df39b94600d4165f0b357321c0/20._inStore_Customizations_-_1_-_EN.png_h_250)
+![20. inStore Customizations - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6AXuX4eeuPus1uiuyFcXkp/ce21c3df39b94600d4165f0b357321c0/20._inStore_Customizations_-_1_-_EN.png_h_250)
 
 Then click on the __Code__ tab and finally on the `checkout-instore-custom.js` file, which is in the file list on the right-hand side of the screen.
 
-![20. inStore Customizations - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3TCYyx8ZthAnzwDPOQYdNZ/7a31e38624df1ffa2d0f649f2d9328d2/20._inStore_Customizations_-_2_-_EN.png_h_250)
+![20. inStore Customizations - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3TCYyx8ZthAnzwDPOQYdNZ/7a31e38624df1ffa2d0f649f2d9328d2/20._inStore_Customizations_-_2_-_EN.png_h_250)
 
 ## Changing the inStore customization file
 
@@ -48,7 +48,7 @@ Then click on the __Code__ tab and finally on the `checkout-instore-custom.js` f
 
 To make any changes, simply add or modify the lines of code directly in the file edit box, in the VTEX Admin, and—once you're done— click on the __Save__ button, as shown in the image below.
 
-![20. inStore Customizations - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6gxUvg8FcYg2b7zhNpoTj8/0137d152efa66e076f438e849a5bde87/20._inStore_Customizations_-_3_-_EN.png_h_250)
+![20. inStore Customizations - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6gxUvg8FcYg2b7zhNpoTj8/0137d152efa66e076f438e849a5bde87/20._inStore_Customizations_-_3_-_EN.png_h_250)
 
 <div class="alert alert-warning">
 Always follow the customization instructions in this documentation and only make changes as indicated here.
diff --git a/docs/tracks/en/instore-login.md b/docs/tracks/en/instore-login.md
index 38a5dff31..75f7836c8 100644
--- a/docs/tracks/en/instore-login.md
+++ b/docs/tracks/en/instore-login.md
@@ -18,7 +18,7 @@ The first contact between the the physical store sales associate and VTEX Sales
 
 Here, the email and password created for the sales associate in the [Basic Setup](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO#adding-a-sales-associates-email-and-name) must be used. Remember that you cannot use emails that already have access to the administrative panel of VTEX stores.
 
-![31. inStore - Product Overview - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/60fcdfec07dcf51a556bb1a80b2d987f/instore-login-EN__1_.png)
+![31. inStore - Product Overview - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/60fcdfec07dcf51a556bb1a80b2d987f/instore-login-EN__1_.png)
 
 Upon logging in, the sales associate accesses the VTEX Sales App application specific to a VTEX account. Although it is not a common scenario, the same sales associate may be linked to more than one account. If you need to switch accounts, just log out and, on the login screen, click on `Change store`.
 
diff --git a/docs/tracks/en/instore.md b/docs/tracks/en/instore.md
index 0d18e1816..642102f73 100644
--- a/docs/tracks/en/instore.md
+++ b/docs/tracks/en/instore.md
@@ -24,7 +24,7 @@ The first contact between the the physical store salesperson and inStore happens
 
 Here, the e-mail and password created for the salesperson in the [Basic Setup](https://help.vtex.com/en/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc) must be used. Remember that you cannot use emails that already have access to the administrative panel of VTEX stores.
 
-![31. inStore - Product Overview - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
+![31. inStore - Product Overview - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
 
 Upon logging in, the salesperson accesses the inStore application specific to a VTEX account. Although it is not a common scenario, the same salesperson may be linked to more than one account. If you need to switch accounts, just log out and, on the login screen, click on __Change Store__.
 
@@ -46,7 +46,7 @@ You can [configure which identification methods you want to enable](https://help
 
 In the example image below, E-mail and CPF are enabled.
 
-![31. inStore - Product Overview - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
+![31. inStore - Product Overview - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
 
 Just enter one of these data in the field and click on the __Confirm__ button.
 
@@ -60,11 +60,11 @@ Although it is possible to cater customers without identifying them, we always r
 
 The top bar of the inStore app offers some options frequently used by the salesperson. One of them is the SKU search, available in the upper right corner.
 
-![31. inStore - Product Overview - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
+![31. inStore - Product Overview - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
 
 In inStore the search is omnichannel. That is, when doing a search in the app, the salesperson is searching both in the local inventory (of the physical store itself) and in the catalog of other physical stores and the e-commerce.
 
-![31. inStore - Product Overview - 4 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
+![31. inStore - Product Overview - 4 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
 
 The delivery and pickup availability options will be shown later, in the delivery stage.
 
@@ -72,11 +72,11 @@ The delivery and pickup availability options will be shown later, in the deliver
 
 After identifying the customer, the salesperson is taken directly to the cart. There, if you are using the desktop version of inStore, connected to a barcode reader, simply beep the products and they will appear in the cart.
 
-![31. inStore - Product Overview - 5 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
+![31. inStore - Product Overview - 5 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
 
 If the salesperson is using a tablet or smartphone, they will see a barcode reading button on the top bar of the application.
 
-![31. inStore - Product Overview - 6 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
+![31. inStore - Product Overview - 6 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
 
 When clicking on it, the salesperson can use the camera to beep a product and, with that, be automatically taken to the details screen of that product.
 
@@ -119,7 +119,7 @@ Remember that all this information refers not only to the customer's experience
 
 When clicking on the details of a product that appears in the inStore search results, or when beeping a product, the salesperson is directed to the product details screen.
 
-![31. inStore - Product Overview - 7 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
+![31. inStore - Product Overview - 7 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
 
 This screen shows the name of the product, its photo gallery, variations, description and availability. On this screen, the salesperson can add the product to the cart.
 
@@ -137,7 +137,7 @@ InStore let's you [enable a cart transfer functionality](https://help.vtex.com/e
 
 Once in an order cart, the salesperson has access to the __Transfer__ button. When clicking this button, the app shows a QR Code and a four-digit numeric code.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Another salesperson logged into the same store can then capture that cart and continue selling from their device.
 
@@ -156,21 +156,21 @@ The next screen shows the delivery options. As inStore deals with the catalog of
 
 The example below shows two options: receive all items at home or pick up at another physical store within 5 working days.
 
-![31. inStore - Product Overview - 10](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
+![31. inStore - Product Overview - 10](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
 
 ### Pick-up Points
 
 For pick-up point options, the system selects the stores that have the SKUs in stock and shows the store closest to the customer's zip code, as a suggestion. If the salesperson wants to change the store where the customer will pick up the items, they just need to click the __Change pick-up point__ button.
 
-![31. inStore - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
+![31. inStore - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
 
 When choosing to change the pick-up point, the salesperson first has access to the pick-up point suggested by the system. To see all available pick-up points, click __View all pick-up points__.
 
-![31. inStore - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
+![31. inStore - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
 
 The app will then show the list of pick-up points ordered by the shortest distance from the customer's zip code. It's also possible to choose a pick-up point on the map.
 
-![31. inStore - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
+![31. inStore - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
 
 ## 12. Payment
 
@@ -178,17 +178,17 @@ In the payment step, the salesperson will see the [payment options that have bee
 
 An important feature allowed by inStore is multiple payments. For example, by choosing Cash and then clicking __Add another payment__, the salesperson can charge part of the amount in cash and part on credit or debit card.
 
-![31. inStore - Product Overview - 14](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
+![31. inStore - Product Overview - 14](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
 
 The top bar of the payment screen allows you to add a coupon and a gift card. It also allows changing the customer ID number that will appear on the invoice.
 
-![31. inStore - Product Overview - 15](https://images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
+![31. inStore - Product Overview - 15](//images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
 
 ## 13. Order placed
 
 The salesperson can see this same screen by clicking on __Completed Orders__ in inStore's main menu or searching for the order by order number or customer.
 
-![31. inStore - Product Overview - 16](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
+![31. inStore - Product Overview - 16](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
 
 ## 14. NFC-e printing
 
diff --git a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
index 605f834f8..a3abd66b2 100644
--- a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
@@ -16,7 +16,7 @@ trackSlugEN: integrating-instore-to-a-new-payment-acquirer
 
 This article aims to explain how the inStore app configures AppLinking for `payment` and `payment-reversal` actions with the acquirers' apps.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Setting fields
 
diff --git a/docs/tracks/en/integration-settings.md b/docs/tracks/en/integration-settings.md
index 263b3f533..e41ff0756 100644
--- a/docs/tracks/en/integration-settings.md
+++ b/docs/tracks/en/integration-settings.md
@@ -1,10 +1,10 @@
 ---
-title: 'Integration Settings'
+title: 'Integrations'
 id: 6wKQgKmu2FT6084BJT7z5V
 status: PUBLISHED
 createdAt: 2020-04-14T13:28:52.687Z
-updatedAt: 2020-04-20T20:15:39.952Z
-publishedAt: 2020-04-20T20:15:39.952Z
+updatedAt: 2024-01-24T19:12:30.626Z
+publishedAt: 2024-01-24T19:12:30.626Z
 firstPublishedAt: 2020-04-14T23:53:14.582Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,9 +14,17 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
-Integration settings is the functionality responsible for the initial indexing of the Catalog with VTEX Intelligent Search. After installing the application, this will be the first step to integrating it with the Catalog.
+The **Store Settings** > **Intelligent Search** > **Integrations** page in the VTEX Admin handles the initial indexing of the Catalog with VTEX Intelligent Search. After installing the app, this will be the first step in integrating the app with the Catalog.
 
-The tool consists of a text informing about the indexing process and a Start button. Upon pressing the button, indexing starts and a link to the __Indexing status__ screen is displayed.
+Follow the instructions to start the integration process:
 
+1. In the VTEX Admin, go to **Store Settings**, or type **Store Settings** in the search bar at the top of the page.
+2. Under **Intelligent Search**, click **Integrations**.
+3. Click `Start Integration`.
+
+The indexing process will start. Once completed, the screen shown below will be displayed.
+
+![integracoes-is-en](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/20ef33f4ff2b33fca08a777d6c3c90c2/integracoes-is-en.PNG)
+
+You don't need to repeat this process. After starting the integration, you can follow the indexing status on the [Indexing History](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) page.
 
-![config-int-EN](https://images.ctfassets.net/alneenqid6w5/6Dhh6x6Roi1vRePJDtbOFY/d642a9f13d421ef3f3062a5ff261ff39/config-int-EN.png)
diff --git a/docs/tracks/en/intelligent-synonyms.md b/docs/tracks/en/intelligent-synonyms.md
new file mode 100644
index 000000000..63c7dada5
--- /dev/null
+++ b/docs/tracks/en/intelligent-synonyms.md
@@ -0,0 +1,67 @@
+---
+title: 'Intelligent Synonyms'
+id: 36w9XnpEkoVWl46tAwlyIV
+status: DRAFT
+createdAt: 2024-04-02T12:59:23.678Z
+updatedAt: 2024-06-17T13:46:32.394Z
+publishedAt: 
+firstPublishedAt: 2024-04-02T13:04:21.646Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: intelligent-synonyms
+locale: en
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugEN: vtex-intelligent-search
+---
+
+
+<div class="alert alert-info">
+  <p>This feature is available for accounts that have a minimum number of sessions and orders for training the artificial intelligence model. If you would like to implement it, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>. Additional fees may apply in the future.</p>
+</div>
+
+The [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) allows you to add words, or similar sentences, as synonyms for customer search terms, increasing the chance of successful searches.
+
+With the Intelligent Synonyms feature, the **Synonyms** page in the VTEX Admin provides intelligent recommendations of terms, as well as manual configuration of synonyms. The platform leverages artificial intelligence to suggest synonyms based on customer search behavior in your store.
+
+VTEX Intelligent Search achieves this by counting how many times in the last 30 days  customers have searched for a term that returned few or no search results and replaced the original term with an alternative one.
+
+Example: Suppose five customers typed `facial soap` in their search but later changed it to `face soap`. The system records this behavior, and the most rewritten terms will be displayed as suggested synonyms.
+
+The suggestions are displayed in two categories in the list of synonyms, as shown below:
+
+* **New suggestions:** Suggestions generated by the platform that have not yet been viewed.
+* **Saved suggestions:** Suggestions saved for later, as described in step 5 of the [Reviewing suggestions](#revisar-sugestoes) section.
+
+![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
+
+You can review the suggestions and choose to save for later, decline, edit, or approve. See the steps in the next section.
+
+## Reviewing suggestions
+
+Follow these instructions to view the synonym suggestions and choose whether to decline, edit, or approve them:
+
+1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2. In **Intelligent Search**, click **Synonyms**.
+3. When accessing the **Synonyms** page, if there are suggestions that have not yet been reviewed, a modal will be displayed indicating the number of suggestions generated. In this case, click `Review` to review them.
+
+    If you click `Not Now`, the suggestions will remain in the **New suggestions** box, indicating the number of generated suggestions. To review them, click `Review`. 
+4. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
+
+   ![synonym-suggestion-en](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
+
+5. To review each suggestion, choose one of the following actions:
+    * <i class="fas fa-bookmark"></i> **Save for Later:** Removes the suggestion from the **New suggestions** count and stores it in the **Saved suggestions** box. To review the saved suggestions later, click `Review`.
+    * <i class="fas fa-times-circle"></i> **Decline**: Rejects the proposed suggestion.
+    * <i class="fas fa-pencil-alt"></i> **Edit**: Changes the suggested synonym configuration fields. After editing, you need to click <i class="fas fa-check-circle"></i> to save. To learn more about the available fields, read the[ Configuring Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL) article.
+    * <i class="fas fa-check-circle"></i> **Approve**: Applies and saves the proposed suggestion.
+6. After reviewing all suggestions, close the modal to access the list of synonyms configured in your store.
+
+<div class="alert alert-error">
+  <p>Once an action is performed, it cannot be undone, as the next available suggestion will be displayed immediately.</p>
+</div>
+
+## Learn more
+
+* [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV)
+* [Configuring Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL)
+* [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
diff --git a/docs/tracks/en/intro-to-vtex-io-builders.md b/docs/tracks/en/intro-to-vtex-io-builders.md
index 1286c488a..e4ab38d2b 100644
--- a/docs/tracks/en/intro-to-vtex-io-builders.md
+++ b/docs/tracks/en/intro-to-vtex-io-builders.md
@@ -19,6 +19,6 @@ Apps in VTEX IO export code or configuration to provide features or alter the be
 These pieces of code and configuration usually require some preparation or validation in order to serve their purpose. For example, React components need to have their dependencies pulled and be compiled into JavaScript bundles. 
 
 VTEX IO automatically takes care of all of these steps by implementing them as Builders. Once your app declares it uses a builder, the corresponding folder and its contents are processed by it upon linking. 
-![builders](https://images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
+![builders](//images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
 
 The store theme project uses two main builders (`store` and `styles`), but as you create apps with more advanced functionality, you will start using other, lower-level builders such as `react`, `messages`, `graphql` and `node`.
diff --git a/docs/tracks/en/introduction-to-vtex-io.md b/docs/tracks/en/introduction-to-vtex-io.md
index 280498881..153b379e3 100644
--- a/docs/tracks/en/introduction-to-vtex-io.md
+++ b/docs/tracks/en/introduction-to-vtex-io.md
@@ -22,7 +22,7 @@ In this track, we will teach you step by step how to develop an app using VTEX I
 
 See in the image below the hierarchical structure of VTEX IO:
 
-![VTEX IO Hierarchy](https://images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
+![VTEX IO Hierarchy](//images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
 
 - __Account__: To develop an app, you need to have a VTEX account.
 - __Workspaces__: These are the environments where the apps will be developed. These environments are linked to the account. You may have multiple workspaces for a single account.
diff --git a/docs/tracks/en/introduction-to-vtex.md b/docs/tracks/en/introduction-to-vtex.md
new file mode 100644
index 000000000..988ba87d5
--- /dev/null
+++ b/docs/tracks/en/introduction-to-vtex.md
@@ -0,0 +1,45 @@
+---
+title: 'Introduction to VTEX'
+id: 3QfoDZWg9YWl8lwS9MVrnU
+status: PUBLISHED
+createdAt: 2024-01-22T14:29:24.584Z
+updatedAt: 2024-02-22T14:58:02.855Z
+publishedAt: 2024-02-22T14:58:02.855Z
+firstPublishedAt: 2024-02-22T13:59:50.803Z
+contentType: trackArticle
+productTeam: Others
+slug: introduction-to-vtex
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+[VTEX](https://vtex.com/us-en/) is an integrated global commerce solution based on microservices. It provides a comprehensive end-to-end marketplace, native order management (OMS), and a composable commerce model. This enables stores across various segments to manage their operations efficiently and at scale, delivering exceptional shopping experiences to their customers.
+
+The following image shows VTEX's solutions and possibilities, which will be covered throughout this article series:
+
+![vtex_composable_complete_EN](//images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/d4622b765ea964b60da83fd11dffe865/vtex_composable_complete_EN.png)
+
+<div class="alert alert-info">
+Besides the resources available on the Help Center and <a href="https://developers.vtex.com/">Developer Portal</a>, as well as the <a href="https://community.vtex.com/">VTEX Community</a>, our <a href="https://vtex.com/us-en/">website</a> provides additional information about the platform through <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">demo videos</a> and <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> created by our <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">partners</a>. There is also a series of <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">onboarding videos</a> (available only in Portuguese).
+</div>
+
+## Track overview
+
+This track presents the journey of a VTEX store from its initial settings to the go-live. But before configuring the platform [modules](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), planning [backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), and choosing a [frontend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) technology for building the storefront, there's a preliminary step: determining the [account type and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) that best align with your business needs.
+
+<div class="alert alert-warning">
+Each ecommerce operation has its own particularities and this content is not intended to encompass all possible scenarios. Our goal is to provide a general model and present the features and possibilities of the VTEX platform.
+</div>
+
+The content is organized sequentially for educational purposes; however, this does not imply that the steps need to be executed in order or that the previous step is a block for the next. Some steps can be completed in parallel, at least partially, such as backend integrations, settings for some modules, and frontend implementation.
+
+## Onboarding guide overview
+
+The **VTEX store overview** is the first track in the **Onboarding guide**. After the go-live, there are several other [solutions](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) and [settings](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) on the platform to diversify your store's sales strategies and expand your business operations. This is the focus of the second track, called [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/7bORBaAr4rIG3JgRi68jIK).
+
+The third and final track of the **Onboarding guide** is [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) and aims to provide our customers with the best platform and support experiences. The track covers how [VTEX Support works](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) and explains how to open tickets to get help with [technical](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [billing](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) or [commercial](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) issues.
+
+Now we are ready to begin our journey.<br>
+Welcome to VTEX.
+
diff --git a/docs/tracks/en/inventory-and-shipping-module-overview.md b/docs/tracks/en/inventory-and-shipping-module-overview.md
index a3a58b0b6..b29628893 100644
--- a/docs/tracks/en/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/en/inventory-and-shipping-module-overview.md
@@ -22,7 +22,7 @@ The __Inventory and Shipping__ module is the service responsible for your store'
 
 The logistics system has several useful functionalities. These *features* allow you to come up with a shipping and inventory strategy tailored to your business. In this track's next steps, we'll have a closer look at each one of the functionalities highlighted below. In your store's admin, you'll come across the following sections: 
 
-![inventory-shipping-admin-en](https://images.ctfassets.net/alneenqid6w5/1nycgD4T0mrDjbvXG9FL6u/989a48356d35c559a958073f96cc77a0/inventory-shipping-admin-en.png)
+![inventory-shipping-admin-en](//images.ctfassets.net/alneenqid6w5/1nycgD4T0mrDjbvXG9FL6u/989a48356d35c559a958073f96cc77a0/inventory-shipping-admin-en.png)
 
 __Shipping strategy__ (Dashboard) - This section allows you to add logistics routes used for order shipping. A basic route consists of a __warehouse__,  a __loading dock__ and a __shipping policy__ (carrier).
 
diff --git a/docs/tracks/en/legacy-cms-portal.md b/docs/tracks/en/legacy-cms-portal.md
index e6d8a46a1..55d93c59f 100644
--- a/docs/tracks/en/legacy-cms-portal.md
+++ b/docs/tracks/en/legacy-cms-portal.md
@@ -18,7 +18,7 @@ trackSlugEN: cms
 
 The [Layout](https://help.vtex.com/en/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW) section allows you to create your storefront with HTML and CSS. It is organized into folders and files with specific purposes:
 
-![CMS - Layout EN](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/0e1fc8acb3b24882504c11d857508d68/cms-layout-en.png)
+![CMS - Layout EN](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/0e1fc8acb3b24882504c11d857508d68/cms-layout-en.png)
 
 - **HTML Templates:** build the HTML code and reference JavaScript and CSS files to be used in the website pages.
 
@@ -38,7 +38,7 @@ The [Layout](https://help.vtex.com/en/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW
 
 The [Settings](https://help.vtex.com/en/subcategory/cms-settings--6kovkwzMRyeOOc2iEC4suM) section allows you to configure settings related to your store website, such as its metadata, SEO tags, file types, and more. 
 
-![CMS - Settings EN](https://images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/852f9d3a206658b19dc33e3e857c97d9/cms-settings-en.png)
+![CMS - Settings EN](//images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/852f9d3a206658b19dc33e3e857c97d9/cms-settings-en.png)
 
 The **Settings** section is structured as follows.
 
diff --git a/docs/tracks/en/live-support.md b/docs/tracks/en/live-support.md
index c583050be..6cbe1ed2d 100644
--- a/docs/tracks/en/live-support.md
+++ b/docs/tracks/en/live-support.md
@@ -1,10 +1,10 @@
 ---
 title: 'Live Support'
 id: 1woBo299K5gvDG7MSa8HYL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-18T15:27:09.214Z
-updatedAt: 2023-04-27T15:25:57.212Z
-publishedAt: 2023-04-27T15:25:57.212Z
+updatedAt: 2024-01-05T17:14:29.070Z
+publishedAt: 
 firstPublishedAt: 2023-04-18T19:58:12.540Z
 contentType: trackArticle
 productTeam: Shopping
@@ -27,12 +27,12 @@ Follow the steps below to configure your store live support business hours.
 # General settings
 
 1. Set whether you want to enable human support in your store.
- ![Live Support en](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/aeabaad112b555b4b8275ef7e682bf49/general_settings.png)
+ ![Live Support en](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/aeabaad112b555b4b8275ef7e682bf49/general_settings.png)
 
 If you choose not to provide it, you need to define an unavailability message indicating the best service channel for your customer.
- ![Mensagem de indisponibilidade](https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/029fcd7b9d0eb4f7dfe59fbb2abebcbb/unaviability.png)
+ ![Mensagem de indisponibilidade](//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/029fcd7b9d0eb4f7dfe59fbb2abebcbb/unaviability.png)
 2. Set the time zone for your live support service.
-![fuso horário en](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/867851568c68409ae8242293cb30bdd6/horarios_de_funcionamento_en.png)
+![fuso horário en](//images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/867851568c68409ae8242293cb30bdd6/horarios_de_funcionamento_en.png)
 3. Select the days and set the business hours of your live support. You can specify more than one window per weekday.
 
 <div class="alert alert-info">
@@ -40,8 +40,8 @@ In case of bank or regional holidays or other dates when support will be unavail
 </div>
 
 <ol start="4">
-  <li>If there are any service exceptions, indicate the unavailability windows.<br><img src="https://images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/21c42d8dfb5bb4657ee02d5595431f66/image_3_en.png" alt="exceções ou feriados"></li>
-  <li>Create an unavailability message. This message will be displayed to the users when they contact via WhatsApp during unavailable hours.<br><img src="https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/029fcd7b9d0eb4f7dfe59fbb2abebcbb/unaviability.png" alt="Mensagem de indisponibilidade"></li>
+  <li>If there are any service exceptions, indicate the unavailability windows.<br><img src="//images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/21c42d8dfb5bb4657ee02d5595431f66/image_3_en.png" alt="exceções ou feriados"></li>
+  <li>Create an unavailability message. This message will be displayed to the users when they contact via WhatsApp during unavailable hours.<br><img src="//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/029fcd7b9d0eb4f7dfe59fbb2abebcbb/unaviability.png" alt="Mensagem de indisponibilidade"></li>
   <li>Click <code>Save</code>.</li>
 </ol> 
 
diff --git a/docs/tracks/en/livelo-integration-overview.md b/docs/tracks/en/livelo-integration-overview.md
new file mode 100644
index 000000000..3d0f26883
--- /dev/null
+++ b/docs/tracks/en/livelo-integration-overview.md
@@ -0,0 +1,18 @@
+---
+title: 'Livelo Integration overview'
+id: 5rhGcaM0SedoK7lDMBkVFD
+status: PUBLISHED
+createdAt: 2023-08-10T22:18:36.772Z
+updatedAt: 2023-08-11T02:18:04.456Z
+publishedAt: 2023-08-11T02:18:04.456Z
+firstPublishedAt: 2023-08-11T01:56:55.424Z
+contentType: trackArticle
+productTeam: Channels
+slug: livelo-integration-overview
+locale: en
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugEN: livelo-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/livelo-integration-registration.md b/docs/tracks/en/livelo-integration-registration.md
new file mode 100644
index 000000000..0f0e83c04
--- /dev/null
+++ b/docs/tracks/en/livelo-integration-registration.md
@@ -0,0 +1,18 @@
+---
+title: 'Livelo integration registration'
+id: 2h9cAUiAZONxc5xbqeRjvu
+status: PUBLISHED
+createdAt: 2023-08-11T00:50:23.667Z
+updatedAt: 2024-07-26T18:49:35.608Z
+publishedAt: 2024-07-26T18:49:35.608Z
+firstPublishedAt: 2023-08-11T01:56:55.329Z
+contentType: trackArticle
+productTeam: Channels
+slug: livelo-integration-registration
+locale: en
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugEN: livelo-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/magazine-luiza-marketplace.md b/docs/tracks/en/magazine-luiza-marketplace.md
index f4b6560be..66063e244 100644
--- a/docs/tracks/en/magazine-luiza-marketplace.md
+++ b/docs/tracks/en/magazine-luiza-marketplace.md
@@ -3,8 +3,8 @@ title: 'Magazine Luiza Marketplace'
 id: 5CEVGKgtrMuifbjNoo8jKX
 status: PUBLISHED
 createdAt: 2021-03-16T19:41:45.000Z
-updatedAt: 2021-03-19T16:23:48.653Z
-publishedAt: 2021-03-19T16:23:48.653Z
+updatedAt: 2024-07-26T18:58:37.335Z
+publishedAt: 2024-07-26T18:58:37.335Z
 firstPublishedAt: 2021-03-18T14:15:52.422Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/managing-accounts.md b/docs/tracks/en/managing-accounts.md
index d583b6ed5..a5780430a 100644
--- a/docs/tracks/en/managing-accounts.md
+++ b/docs/tracks/en/managing-accounts.md
@@ -3,8 +3,8 @@ title: 'Managing Customer Credit accounts'
 id: 4eknoeqaj6EGC20amsm6Gc
 status: PUBLISHED
 createdAt: 2018-11-06T21:15:25.330Z
-updatedAt: 2023-05-12T12:21:21.583Z
-publishedAt: 2023-05-12T12:21:21.583Z
+updatedAt: 2024-02-27T19:44:55.522Z
+publishedAt: 2024-02-27T19:44:55.522Z
 firstPublishedAt: 2018-11-07T17:10:45.883Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,97 +14,66 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugEN: customer-credit-getting-started
 ---
 
-The Account Details screen shows everything you need to know about an account and its settings.
+Through the accounts screen in the VTEX Admin (__Apps > Customer Credit > Accounts__), you can access information from all accounts registered in the Customer Credit app in your store. 
 
-## Credit limit
+When clicking on the name of a specific account, the __Account Details__ screen will display the following data:
 
-The credit limit indicates the maximum value of outstanding invoices that a client can have at any given time. Establishing it is required, and the account’s super Admin can change this value as many times as he/she wants.
+- [Holder Information](#holder)
+- [Credit Status](#status)
+- [Invoices issued](#invoices)
+- [Usage statement](#statements)
+- [Additional Holders](#additional-holders)
+- [Account closure](#account-closure)
+<br>
+<br>
+![Account_EN](//images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/a9f3a550884255677d837466ec63cf3c/Contas_EN.png)
 
-Also, remember that changes to the credit limit are updated in the system within minutes.
+## Holder
 
-## Invoices 
+It presents information about the account status (active, inactive), identification code, registered document and email of the holder, account opening dates and last data update.
 
-Invoices are documents generated when customers conclude purchases using Customer Credit as a payment method.
+## Status
 
-In cases of installment purchases, the number of invoices is the same as the number of installments. For example, if the customer has chosen to pay the order in 10 installments, the system will generate 10 invoices related to that same order.
+Displays the amount of credit available for the customer to use for purchases and the total amount to be paid (in invoices) for purchases already made using Customer Credit as a means of payment.
 
-Regardless of the payment method, all invoices in the system can be viewed and managed through the Admin and, like the accounts, can also be exported and edited in bulk.
+<div class="alert alert-warning">
+When the customer makes a purchase using Customer Credit, but the order has not yet been billed (invoice issued), the <b>Reserved Credit</b> field is also displayed on this screen containing information on the order value.
+</div>
 
-### Invoice status
-Invoices have four possible statuses:
+## Manage
 
-- Open;
-- Paid;
-- Overdue;
-- Canceled.
+Indicates the maximum amount of credit granted to the customer and the tolerance to be used in purchases. These values ​​can be edited at any time.
 
-When an invoice is created, its status is "open" and, depending on actions taken in the Admin or API calls, it can transition to “paid” or “canceled”.
+## Invoices
 
-#### Invoice settlement
-The store controls the way in which invoices will be settled.
+List containing the following information about all invoices issued in purchases made by the customer:
 
-One of the invoice settlement options is to generate a payment link. In this case, once it is configured, the customer will see a "Pay" button next to the invoice on the My Credits screen, which will redirect him to the payment link.
+- Due date
+- Comments (specific message for a invoice)
+- Order ID
+- Invoice amount
+- Invoice status (Open, Paid, Canceled, Expired)
 
-In addition, payment links can be added via CSV file through the Admin or via API.
+## Statements
 
-After receiving payment for an invoice, mark it as paid on our system. This can be done in three ways: individually, in bulk or via API.
+Displays a report of all payment and invoice transactions carried out for the customer during a selected period.
 
-#### Individual settlement
-Settling an invoice through Admin is simple:
+## Additional Holders
 
-1. Access the __Admin__;
-2. Click on the __Customer Credit__ module;
-3. Then click on the __Invoices__ section;
-4. Select the __invoice__ you want to edit;
-5. Click on the __"Mark as paid"__ button.
+The __Additional Holders__ functionality allows the customer to share credits available for purchases with other people registered in the account.
 
-This way, the invoice status will change to “paid”.
+To register a new dependent, follow the steps below:
 
-#### Bulk settlement
-If your account has a lot of outstanding invoices, it is not feasible to change each status individually.
+1. Within the customer account, under __Additional Holders__, click `NEW`.
+2. Enter the email of the person to be added as a dependent on the customer's account.
+3. Click `CONFIRM`.
 
-For that, you can use the bulk settlement feature, a process very similar to the accounts bulk update. The principle is the same: importing a CSV file with the new data to the Admin.
+From this moment on, the customer and their dependent will be able to share the amount in __Available credit__ to make their purchases through Customer Credit.
 
-In this case, you must change the values in the status column from "open" to "paid" and save the changes.
+## Account closure
 
-Then follow the step by step below:
+If you wish to close the customer's account, in the __Others__ section, click on `CLOSE ACCOUNT`.
 
-1. Access the __Admin__;
-2. Click on the __Customer Credit__ module;
-3. Click on the __Invoices__ section;
-4. Then click on the __“Bulk update”__ button;
-5. Click on the __“Choose file”__ button;
-6. Select the desired __CSV file__.
-
-Wait for the spreadsheet to be uploaded and the invoices will be settled all at once.
-
-#### Settlement via API
-To settle an invoice through an API, you can use the `PUT Change Invoice` [endpoint](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId- "endpoint"). This API can also be used to change the invoice’s status.
-
-Fill in the body with the following information:
-
-```json
-{
-"status": "string [Opened | Cancelled | Paid] (optional)", "observation": "string (optional)",
-"paymentLink": "string (URL) (optional)"
-}
-```
-
-For more details, check out our [technical documentation on Customer Credit](https://developers.vtex.com/docs/guides/customer-credit-api-overview "technical documentation on Customer Credit").
-
-## Additional dependents
-According to your business rules, you can share the account’s credit limit with other users.
-
-This functionality allows you to add new dependents to an account. They will share the available credit to pay for purchases on SmartCheckout.
-
-To add new dependents to an account, follow the step by step below:
-
-1. Access the __Admin__;
-2. Click on the __Customer Credit__ module;
-3. Then click on the __Accounts__ section;
-4. Select the __account__ you want to edit;
-5. At the bottom of the page, click on the __“New”__ button;
-6. Fill in the blank field with the new dependent’s __email__;
-7. Click on the __Confirm__ button.
-
-The newly added dependent will then appear in the box of additional dependents for that account.
+<div class="alert alert-warning">
+A closed Customer Credit account cannot be reopened again and invoice, statement and additional dependent data will be deleted. However, after completing the account closure, if you wish, you can <a href="https://help.vtex.com/en/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#creating-accounts-individually">open a new account</a> for the customer using the same email as the closed account.
+</div>
diff --git a/docs/tracks/en/managing-customer-credit-invoices.md b/docs/tracks/en/managing-customer-credit-invoices.md
new file mode 100644
index 000000000..c97c96139
--- /dev/null
+++ b/docs/tracks/en/managing-customer-credit-invoices.md
@@ -0,0 +1,73 @@
+---
+title: 'Managing Customer Credit invoices'
+id: vtf5UVQcmlb0kHBZYYmM3
+status: PUBLISHED
+createdAt: 2024-02-07T21:31:46.690Z
+updatedAt: 2024-02-09T12:30:53.684Z
+publishedAt: 2024-02-09T12:30:53.684Z
+firstPublishedAt: 2024-02-07T21:44:30.527Z
+contentType: trackArticle
+productTeam: Financial
+slug: managing-customer-credit-invoices
+locale: en
+trackId: 1hCRg21lXYy2seOKgqQ2CC
+trackSlugEN: customer-credit-getting-started
+---
+
+The __Invoices__ screen in the VTEX Admin (__Apps > Customer Credit > Invoices__), allows you to access information on all invoices issued by customers registered with Customer Credit in your store. Through this functionality, you can perform the following actions:
+
+- [Filter invoice view](#invoice-filter) 
+- [Check details of each invoice](#invoice-details)
+- [Settle invoices](#settle-invoices)
+<br>
+<br>
+![Invoices_EN](//images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/5f6f07bf3e43e11762d057b41b2277bb/Invoices_EN.JPG)
+
+## Invoice filter
+
+To select the list of invoices to be displayed, you can click on one of the four statuses (Open, Paid, Canceled or Expired), or enter the identification number of the order for which the invoice was issued.
+
+<div class="alert alert-warning">
+In Customer Credit, all invoices are created with the status <b>Open</b>.
+</div>
+
+## Invoice details
+
+When clicking on a specific invoice, the __Invoice Summary__ page displays the following information: value of the invoice issued, due date, payment link (if there is one), identification of the account where it was issued, identification of the order and observations (specific messages about the invoice).
+
+## Settle invoices
+
+To facilitate the payment process for a invoice, it is possible to provide a payment link directly to the customer. This link can be added to the title in two ways:
+
+- Use the `IMPORT` function to insert data from a .csv spreadsheet.
+- Via [PUT Change Invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-) endpoint of the Customer Credit API.
+
+<div class="alert alert-info">
+After carrying out one of the procedures above, the customer will have access to the <b>PAY</b> button that is available in their customer area on the store's website (<b>My Account > My Credits</b>).
+</div>
+
+### Individual settlement
+
+After confirming payment for a invoice, you can settle it as follows:
+
+1. In the VTEX Admin, access __Apps > Customer Credit > Invoices__, or type __Invoices__ in the search bar at the top of the page.
+2. Click on the desired invoice.
+3. On the __Invoice Summary__ page, click on __Mark as Paid__.
+4. On the __Invoices__ page, confirm that the invoice status is indicated as __Paid__.
+
+### Bulk settlement
+
+If you want to confirm the payment of several invoices at the same time, follow the steps below:
+
+1. In the VTEX Admin, access __Apps > Customer Credit > Invoices__, or type __Invoices__ in the search bar at the top of the page.
+2. Click on the `EXPORT` button.
+3. Access the downloaded .csv spreadsheet and modify the information in the `Status` field to `Paid` in the lines corresponding to the invoices you want to settle. Save the spreadsheet.
+4. Click on the `IMPORT` button.
+5. Select or insert the .csv spreadsheet in the space __Drop your CSV here or choose a file__.
+6. Click on the `IMPORT FILE` button.
+7. After the spreadsheet is loaded into Admin, check on the __Invoices__ screen if the updated invoices are described as __Paid__.
+
+### API settlement
+
+You can also settle a invoice through the [PUT - Change invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-). For more information about Customer Credit API endpoints, visit [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api#overview).
+
diff --git a/docs/tracks/en/managing-sales-associates-in-instore.md b/docs/tracks/en/managing-sales-associates-in-instore.md
index 491e489d1..da9689d9b 100644
--- a/docs/tracks/en/managing-sales-associates-in-instore.md
+++ b/docs/tracks/en/managing-sales-associates-in-instore.md
@@ -3,8 +3,8 @@ title: 'Managing sales associates in VTEX Sales App'
 id: 5pqtuvi97FFZiGf7MlSe8q
 status: PUBLISHED
 createdAt: 2023-04-17T21:01:21.431Z
-updatedAt: 2023-05-31T16:15:21.153Z
-publishedAt: 2023-05-31T16:15:21.153Z
+updatedAt: 2024-01-05T19:59:15.811Z
+publishedAt: 2024-01-05T19:59:15.811Z
 firstPublishedAt: 2023-04-25T20:13:04.431Z
 contentType: trackArticle
 productTeam: Shopping
@@ -15,44 +15,33 @@ trackSlugEN: instore-first-steps-and-configurations
 ---
 
 After configuring the [VTEX Sales App basic settings](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), you can add sales associates to the system or manage the existing ones in the VTEX Admin.
+On the VTEX Admin **Store Settings** page, there is a **Sales associates** category that displays a list of the sales associates added to your [VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). It allows you to manage sales associate information across all [franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) of your store, enabling you to [add](#adding-a-sales-associate), [search](#searching-for-a-sales-associate), [filter](#filtering-sales-associates), [edit](#editing-sales-associate-information), and [inactivate](#inactivating-a-sales-associate) them.
 
-**Sales associates** is a VTEX Admin **Store Settings** page that displays a list of the sales associates registered in your [VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) app. It allows you to manage sales associate information across all your store's [franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
+![vendedores-en](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/6011c48aa3efe75b2131b7870d237483/EN.png)
 
-This page allows you to manage your sellers from the following actions:
+The page displays the following information:
 
-* [Add](#adding-a-sales-associate)
-* [Search](#searching-for-a-sales-associate)
-* [Filter](#filtering-sales-associates)
-* [Edit](#editing-sales-associate-information)
-* [Inactivate](#inactivating-a-sales-associate)
-
-![vendedores-en](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/6011c48aa3efe75b2131b7870d237483/EN.png)
-
-The page displays the following information: 
-
-  | Column Fields | Description                                                                                                                                                                            |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Name             | Name that identifies the sales associate, defined in the [Add sales associate](#adding-a-sales-associate) step. |
-| Code           | Identifier code of each sales associate. It must be the same used in the physical store system.                                                                                                 |
-| Store             | Identifier name of the [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) in which the sales associate is registered.                              |
-| Email            | Sales associate access email.                                                                                                                                           |
+| Column Fields | Description                                                                                                                                                              |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Name          | Name that identifies the sales associate, defined in the[Add sales associate](#adding-a-sales-associate) step.                                                              |
+| Code          | Identifier code of each sales associate. It must be the same used in the physical store system.                                                                          |
+| Store         | Identifier name of the[franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) in which the sales associate is registered. |
+| Email         | Sales associate access email.                                                                                                                                            |
 
 ## Adding a sales associate
 
 You can add a sales associate by following the steps below:
 
-1. In the VTEX Admin, go to **Store Settings > inStore > Sales Associates**, or type **Sales Associates** in the search bar at the top of the page.
+1. In the VTEX Admin, go to **Store Settings > Sales App > Sales Associates**, or type **Sales Associates** in the search bar at the top of the page.
 2. Click the `+ Add Sales Associate` button.
 3. Fill in the [Sales associate fields](#sales-associate-fields).
 4. Click `Add`.
-5. Click `Save` to confirm the sales associate's registration.  
-
-After creation, the sales associate will receive a confirmation email and will be redirected to the sales associate's login option in the inStore app.
+5. Click `Save` to confirm the sales associate's registration.
 
-![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+After being added, the sales associate will receive a confirmation email and be redirected to the sales associate's login option in Sales App.
 
 <div class ="alert alert-warning">
-<p>Sales associates registered in inStore cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.</p> 
+<p>Sales associates registered in Sales App cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.</p>
 </div>
 
 ### Sales associate fields
@@ -61,14 +50,15 @@ After creation, the sales associate will receive a confirmation email and will b
 
 * **Sales associate name:** sales associate name. Mandatory field.
 * **Sales associate code:** the code that identifies the sales associate. It must be the same used in the physical store system.
-* **Email:** sales associate's inStore access email. Mandatory field.
+* **Email:** sales associate's Sales App access email. Mandatory field.
+* **Allow access to other sales associates' performances:** Checkbox that allows you to view other sales associates' sales performance (when checked) or only access information about your own sales performance (when unchecked).
 
 #### Physical store
 
 * **Store:** the [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) in which the sales associate will be registered. Mandatory field.
 
 <div class ="alert alert-info">
-<p>Changes can take up to 15 minutes to be processed and applied to inStore.</p> 
+<p>Changes can take up to 15 minutes to be processed and applied to Sales App.</p> 
 </div>
 
 ## Searching for a sales associate
@@ -77,7 +67,7 @@ You can search for a sales associate using the search bar by entering their name
 
 ## Filtering sales associates
 
-Click the `Store` filter to filter sales associates by the name of a specific physical store. 
+Click the `Store` filter to filter sales associates by the name of a specific physical store.
 
 ## Editing sales associate information
 
@@ -96,4 +86,4 @@ You can inactivate a sales associate by following the steps below:
 2. Click <i class="fa-solid fa-box-archive"></i> `Inactivate`.
 3. Click `Inactivate` again.
 
-Once the sales associate is inactivated, they will no longer have access to the inStore app nor be able to log in. To permanently delete a sales associate, please contact our [support](https://support.vtex.com/hc/en-us/requests).
+Once the sales associate is inactivated, they will no longer have access to the VTEX Sales App nor be able to log in. To permanently delete a sales associate, please contact our [support](https://support.vtex.com/hc/en-us/requests).
diff --git a/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 97cccc993..bd7899c8c 100644
--- a/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -18,7 +18,7 @@ After installing and configuring TikTok for Business, you can manage the integra
 
 After the configuration has been successfully completed, any user logged into the VTEX Admin can access the TikTok management area. However, when interacting with the buttons in this area, users will be redirected to  TikTok environments — TikTok Business Center, TikTok Ads Manager and TikTok Catalog Manager — where they need permissions to view content and make changes.
 
-![manage-tiktok-integration](https://images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
+![manage-tiktok-integration](//images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
 
 From that page, you can do the following:
 
diff --git a/docs/tracks/en/mapping-colors-and-sizes.md b/docs/tracks/en/mapping-colors-and-sizes.md
index 6e8562aa3..fffb1fb7a 100644
--- a/docs/tracks/en/mapping-colors-and-sizes.md
+++ b/docs/tracks/en/mapping-colors-and-sizes.md
@@ -66,7 +66,7 @@ You should choose the closest color match, which in Wish's case can be "White/Ic
 The table's header should be filled in exactly as in the example below. Remember to not add any special characters such as "enter" or "space" when filling this table in.   
 </div>
 
-![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
+![PT - Tabela Wish](//images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
 ## Uploading the spreadsheet
 
diff --git a/docs/tracks/en/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/en/mapping-product-categories-and-attributes-to-mercado-libre.md
index 968a9604c..545fdc9ab 100644
--- a/docs/tracks/en/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/en/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Mapping product categories and attributes to Mercado Libre'
 id: 5XNeiye4rS4oao2MueSUeA
 status: PUBLISHED
 createdAt: 2018-08-13T12:58:18.100Z
-updatedAt: 2022-09-05T19:01:28.441Z
-publishedAt: 2022-09-05T19:01:28.441Z
+updatedAt: 2024-07-23T21:39:55.195Z
+publishedAt: 2024-07-23T21:39:55.195Z
 firstPublishedAt: 2018-08-13T14:27:50.859Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/mapping-product-categories-and-attributes.md b/docs/tracks/en/mapping-product-categories-and-attributes.md
new file mode 100644
index 000000000..320a4b828
--- /dev/null
+++ b/docs/tracks/en/mapping-product-categories-and-attributes.md
@@ -0,0 +1,18 @@
+---
+title: 'Mapping product categories and attributes'
+id: 1Ue3UIHrelsvjYpkLL4IRx
+status: PUBLISHED
+createdAt: 2023-08-11T01:20:24.164Z
+updatedAt: 2023-08-11T02:32:16.459Z
+publishedAt: 2023-08-11T02:32:16.459Z
+firstPublishedAt: 2023-08-11T01:56:55.281Z
+contentType: trackArticle
+productTeam: Channels
+slug: mapping-product-categories-and-attributes
+locale: en
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugEN: livelo-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/mapping-rappi-product-categories-and-attributes.md b/docs/tracks/en/mapping-rappi-product-categories-and-attributes.md
new file mode 100644
index 000000000..884fd4d8c
--- /dev/null
+++ b/docs/tracks/en/mapping-rappi-product-categories-and-attributes.md
@@ -0,0 +1,18 @@
+---
+title: 'Mapping Rappi product categories and attributes'
+id: 6iVRkhA3WHvynIlwgQhjPc
+status: PUBLISHED
+createdAt: 2024-05-31T20:42:26.540Z
+updatedAt: 2024-05-31T20:52:02.358Z
+publishedAt: 2024-05-31T20:52:02.358Z
+firstPublishedAt: 2024-05-31T20:52:02.358Z
+contentType: trackArticle
+productTeam: Channels
+slug: mapping-rappi-product-categories-and-attributes
+locale: en
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugEN: rappi-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/mercado-libre-marketplace.md b/docs/tracks/en/mercado-libre-marketplace.md
index 32b1c2184..e47b34512 100644
--- a/docs/tracks/en/mercado-libre-marketplace.md
+++ b/docs/tracks/en/mercado-libre-marketplace.md
@@ -1,10 +1,10 @@
 ---
 title: 'Mercado Libre '
 id: 51oWBHvVxSs8eAwLQhSbSd
-status: CHANGED
+status: PUBLISHED
 createdAt: 2020-09-23T20:16:36.804Z
-updatedAt: 2023-03-28T21:46:05.528Z
-publishedAt: 2021-09-04T11:14:45.743Z
+updatedAt: 2024-03-11T22:19:17.941Z
+publishedAt: 2024-03-11T22:19:17.941Z
 firstPublishedAt: 2020-09-23T20:31:42.798Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/merchandising-rules.md b/docs/tracks/en/merchandising-rules.md
index 4014721ef..cad79a064 100644
--- a/docs/tracks/en/merchandising-rules.md
+++ b/docs/tracks/en/merchandising-rules.md
@@ -3,8 +3,8 @@ title: 'Merchandising rules'
 id: 5tBSYXb9EIdePa0MWTnFd0
 status: PUBLISHED
 createdAt: 2020-03-05T18:53:37.305Z
-updatedAt: 2023-04-03T22:01:51.692Z
-publishedAt: 2023-04-03T22:01:51.692Z
+updatedAt: 2024-01-29T17:07:18.414Z
+publishedAt: 2024-01-29T17:07:18.414Z
 firstPublishedAt: 2020-03-05T19:58:55.021Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -21,9 +21,7 @@ Merchandising rules are priority criteria. If you configure a rule to promote a
 You can set merchandising rules for:
 
 * **Brands:** You can set which brand products are more relevant than others. When the customer searches for "smartphone," for example, the products of this brand will appear at the beginning of the list, and the other brands' products below them.
-* **Product:** Another option is promoting a specific product. For example: set that when searching for "running t-shirt," the product "Running T-shirt" is the first result displayed in the list.
-
-## Merchandising rules listing page
+* **Products:** Another option is promoting a specific product. For example: set that when searching for "running t-shirt," the product "Running T-shirt" is the first result displayed in the list.
 
 On VTEX Admin, the page **Storefront** > **Intelligent Search** > **Merchandising Rules** allows you to do the following actions: 
 
@@ -32,33 +30,36 @@ On VTEX Admin, the page **Storefront** > **Intelligent Search** > **Merchandisin
 * [Edit](#editing-merchandising-rules)
 * [Delete](#deleting-merchandising-rules)
 
-![manage merchandising rules-en](https://images.ctfassets.net/alneenqid6w5/4RIkVevSJArI3LhEHjELHu/6a9a5125d69d32a448f22619ec8ad04e/image.png)
+![merch-rules-en](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/6b6dc34a4127cd654dab40fa17a70664/merch-rules-en.PNG)
 
 The page displays the following information: 
 
-| Column     | Description          |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Name       | Name that identifies the merchandising rule, defined in the "[Creating merchandising rules](#creating-merchandising-rules)" section. |
-| Start date | Date that sets the date the merchandising rule becomes available.                                                                                                                                                  |
-| End date   | Date that sets the date the merchandising rule is no longer available.                                                                                                                                             |
-| Active     | Option that enables or disables a merchandising rule.                                                                                                                                                              |
-| Actions    | Delete or edit a merchandising rule.                                                                                                                                                                               |
+| Column | Description |
+| - | - |
+| __Name__ | Name that identifies the merchandising rule, defined in the "[Creating merchandising rules](#creating-merchandising-rules)" section. |
+| __Start date__ | Date that sets the date the merchandising rule becomes available. |
+| __End date__ | Date that sets the date the merchandising rule is no longer available. |
+| __Type__ | Indicates the [type of editing](#type-of-editing) used in the merchandising rule. |
+| __Active__ | Option that enables or disables a merchandising rule. |
+| __Actions__ <i class="fas fa-ellipsis-v"></i>| Menu with actions to `Edit` or `Delete` a merchandising rule. |
 
 ## Creating merchandising rules
 
-To add a new merchandising rule, click `New`. Learn more about all the information needed to create a merchandising rule in the sections below.
+To add a new merchandising rule, click `+ New`. Learn more about all the information needed to create a merchandising rule in the sections below.
 
 ### Types of editing
 
-When creating or editing Merchandising rules, you can choose between two types of editing: the [Manual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) and the [Visual Editor (Beta)](https://help.vtex.com/en/tutorial/creating-merchandising-rules-visual-editor-beta--6xteumx9MsDt0uEppbChu3). Below are the features available to decide which one works best for you:
+There are two types of editor to create or modify Merchandising rules: the [Manual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) and the [Visual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr).
+
+Below are the features of each editor:
 
-| Feature | Description | Manual Editor | Visual Editor (Beta) |
+| Feature | Description | Manual Editor | Visual Editor |
 |---|---|---|---|
 | Trigger rules | Set conditions for the merchandising rule to be triggered. | Yes | Yes |
 | Customization Rules | Control search results using specific conditions. | Yes | No |
 | Preview | Preview how search results will be displayed to customers while navigating the store. | No | Yes |
 | Reorder search results | Change the order of the items listed as search results. | No | Yes |
-| Pinning a result in a given position | Set a fixed position for a given item in a search result. | No | Yes |
+| Pin products to the top positions | Determine that a given item in a search result will always be displayed in the top position among search results. | No | Yes |
 
 ## Searching for merchandising rules
 
@@ -68,11 +69,11 @@ Enter the name of the merchandising rule in the search bar to search for a merch
 
 You can edit the information in a merchandising rule by following the steps below.
 
-1. Click the pencil button <i class="fa-solid fa-pencil"></i>.
+1. Click the menu <i class="fas fa-ellipsis-v"></i> in the row of the merchandising rule, then click <i class="fas fa-pencil-alt"></i> `Edit`.
 2. Change the information you want in the merchandising rule.
 3. Click `Save`.
 
 ## Deleting merchandising rules
 
-You can delete a merchandising rule by clicking the trash button <i class="fa-solid fa-trash-can"></i>.
+You can delete a merchandising rule by clicking the menu <i class="fas fa-ellipsis-v"></i> in the row of the merchandising rule, then <i class="fas fa-trash"></i> `Delete`.
 
diff --git a/docs/tracks/en/next-steps.md b/docs/tracks/en/next-steps.md
new file mode 100644
index 000000000..dfa1fdc3c
--- /dev/null
+++ b/docs/tracks/en/next-steps.md
@@ -0,0 +1,28 @@
+---
+title: 'Next steps '
+id: 7bORBaAr4rIG3JgRi68jIK
+status: PUBLISHED
+createdAt: 2024-02-07T16:51:41.686Z
+updatedAt: 2024-04-03T12:10:02.808Z
+publishedAt: 2024-04-03T12:10:02.808Z
+firstPublishedAt: 2024-02-22T13:58:08.369Z
+contentType: trackArticle
+productTeam: Others
+slug: next-steps
+locale: en
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugEN: next-steps-after-the-go-live
+---
+
+Now that the store is configured in the VTEX environment and has [gone live](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), it's time to learn about the features and [add-on solutions](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) available to help increase sales performance and expand operations, contributing to your business's continuous improvement.
+
+<div class="alert alert-warning">
+  <p>Through the <a href="https://partnerportal.vtex.com/">VTEX Partner Portal</a>, you can hire <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">partners</a> to help develop your store and manage the solutions described in this article. To log in to the portal, the user needs <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz">access to a store's VTEX Admin</a>.</p>
+</div>
+
+## VTEX launches
+
+In our documentation portals, you can learn about the latest news and updates on VTEX solutions:
+
+- **Help Center:** [Updates](https://help.vtex.com/pt/announcements) dedicated to the store's operational public.
+- **Developer Portal:** [Release notes](https://developers.vtex.com/updates/release-notes) aimed at VTEX environment developers.
diff --git a/docs/tracks/en/opening-tickets.md b/docs/tracks/en/opening-tickets.md
new file mode 100644
index 000000000..34f1eb5fe
--- /dev/null
+++ b/docs/tracks/en/opening-tickets.md
@@ -0,0 +1,35 @@
+---
+title: 'Opening tickets'
+id: 6EboD7Y1BOLlWdT8JM15EE
+status: PUBLISHED
+createdAt: 2024-02-20T21:30:49.633Z
+updatedAt: 2024-02-22T14:09:13.418Z
+publishedAt: 2024-02-22T14:09:13.418Z
+firstPublishedAt: 2024-02-22T14:09:13.418Z
+contentType: trackArticle
+productTeam: Others
+slug: opening-tickets
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+Access to a VTEX account gives you access to the [support dashboard](https://support.vtex.com/hc/us/requests) to monitor your tickets. You can open a ticket by:
+
+- Accessing the [support page](https://support.vtex.com/hc/us/requests).
+- Going to any [Help Center](https://help.vtex.com/) page and click `Support` at the top or `Contact Us` at the bottom of the page.
+- Accessing the VTEX Admin, click the `?` question mark icon in the **Information Center** and choose the **Talk to Our Experts** option.
+
+![Support imagem 1 - EN](//images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/c0f1b4654f82949a438f82b2416a11c7/support_imagem1_EN.gif)
+
+<div class = "alert alert-info">
+Learn more about how to open a ticket and ticket types in the article <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Opening tickets to VTEX support. </a>
+</div>
+
+## Support types
+
+When opening a ticket, you need to select the type of support, which can be:
+
+- [Technical support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T): For issues or technical questions regarding the platform or VTEX solutions such as [Add-on solutions](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+- [Billing support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl): For agreements or financial issues related to the store and VTEX.
+- [Commercial support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ): For requesting an additional [trade policy](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#requesting-an-additional-trade-policy), [additional environment](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#requesting-a-new-environment), franchise account, or [user change](https://help.vtex.com/en/tutorial/what-is-the-sponsor-user--3oPr7YuIkEYqUGmEqIMSEy).
diff --git a/docs/tracks/en/order-delivery.md b/docs/tracks/en/order-delivery.md
index fa3fcf116..698fa4dab 100644
--- a/docs/tracks/en/order-delivery.md
+++ b/docs/tracks/en/order-delivery.md
@@ -23,7 +23,7 @@ See two examples of this scenario:
 
 In this case, items usually come from the warehouse of a distribution center, as illustrated below.
 
-![EN Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
+![EN Conceitos Logística](//images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
 
 Another shipping possibility that can optimize your store’s operation and reduce costs is implementing the [Ship From Store](https://help.vtex.com/en/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl) strategy. This strategy refers to in-store fulfillment, meaning items can also be shipped from physical stores' inventories.
 
diff --git a/docs/tracks/en/order-flow.md b/docs/tracks/en/order-flow.md
index 26f899f1c..bc3049a37 100644
--- a/docs/tracks/en/order-flow.md
+++ b/docs/tracks/en/order-flow.md
@@ -3,8 +3,8 @@ title: 'Order flow'
 id: 4811ExCe3WrEiRMV3sy9n8
 status: PUBLISHED
 createdAt: 2019-11-14T13:46:22.682Z
-updatedAt: 2022-08-08T22:25:52.457Z
-publishedAt: 2022-08-08T22:25:52.457Z
+updatedAt: 2023-10-24T15:32:07.852Z
+publishedAt: 2023-10-24T15:32:07.852Z
 firstPublishedAt: 2019-11-14T15:38:27.680Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -14,13 +14,13 @@ trackId: 2xkTisx4SXOWXQel8Jg8sa
 trackSlugEN: orders
 ---
 
-The __Order flow__ is the path taken by an order inside VTEX platform, from the moment the customer clicks the Checkout button until the order is invoiced or canceled.
+The [Order flow](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) is the path taken by an order inside VTEX platform, from the moment the customer clicks the Checkout button until the order is invoiced or canceled.
 
 Order changes - whether caused by the customer, the store, or external systems - generate changes to the __order status__. And with that, the order moves within the flow.
 
 ## Marketplaces and Sellers
 
-Marketplace and Seller concepts are critical to understanding the flow of an order at VTEX. Let's understand why:
+[Marketplace and Seller](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) concepts are critical to understanding the flow of an order at VTEX. Let's understand why:
 
 - __Marketplace__ is the environment where the order is closed, ie, where the customer performs the checkout process.
 - __Seller__ is the owner of the SKU. It is therefore responsible for the fulfillment - that is, for delivering the product to the customer.
@@ -33,7 +33,7 @@ It's important to understand these concepts because the Marketplace's order flow
 
 ## Marketplace Order Flow
 
-![screenshoot fluxo marketplace EN](https://images.ctfassets.net/alneenqid6w5/6S7796dGpdWlRojJbrSgg/0ca93f3020f0393abafa75e7dd5951aa/screenshoot_fluxo_marketplace_EN.JPG)
+![screenshoot fluxo marketplace EN](//images.ctfassets.net/alneenqid6w5/6S7796dGpdWlRojJbrSgg/0ca93f3020f0393abafa75e7dd5951aa/screenshoot_fluxo_marketplace_EN.JPG)
 
 It happens when the store acts exclusively as a Marketplace in the order. That is, when the store sells products from another store - its Seller.
 
@@ -47,7 +47,7 @@ The dispatch is then authorized and the order enters the status `Window to Cance
 
 ## Seller Order Flow
 
-![screenshoot fluxo seller EN](https://images.ctfassets.net/alneenqid6w5/14SsrA3HbuAxsYerakdGGf/9a50dbe872d8712670ce7a1ddbbf2e6e/screenshoot_fluxo_seller_EN.JPG)
+![screenshoot fluxo seller EN](//images.ctfassets.net/alneenqid6w5/14SsrA3HbuAxsYerakdGGf/9a50dbe872d8712670ce7a1ddbbf2e6e/screenshoot_fluxo_seller_EN.JPG)
 
 It happens when the store acts as a Seller. That is, when it is the owner of the product.
 
@@ -61,7 +61,7 @@ The next status is then `Handling Shipping`, when the Seller prepares the invoic
 
 ## Complete Order Flow
 
-![screenshoot fluxo completo EN](https://images.ctfassets.net/alneenqid6w5/5uYoEIqMJxUMFZzXKf72Sh/2cf49ed2ddd0cceac3f429e1f4492422/screenshoot_fluxo_completo_EN.JPG)
+![screenshoot fluxo completo EN](//images.ctfassets.net/alneenqid6w5/5uYoEIqMJxUMFZzXKf72Sh/2cf49ed2ddd0cceac3f429e1f4492422/screenshoot_fluxo_completo_EN.JPG)
 
 It happens when the store is both the Marketplace and the Seller. That is, it's when the order was closed in the store and the store itself is the owner of the product, being responsible for the fulfillment.
 
diff --git a/docs/tracks/en/other-vtex-module-settings.md b/docs/tracks/en/other-vtex-module-settings.md
new file mode 100644
index 000000000..4c0724ec8
--- /dev/null
+++ b/docs/tracks/en/other-vtex-module-settings.md
@@ -0,0 +1,105 @@
+---
+title: 'Other VTEX module settings'
+id: V1fs7IkfYMfn91ZVHTLu4
+status: PUBLISHED
+createdAt: 2024-02-20T20:25:49.450Z
+updatedAt: 2024-07-30T16:23:50.641Z
+publishedAt: 2024-07-30T16:23:50.641Z
+firstPublishedAt: 2024-02-22T14:09:20.283Z
+contentType: trackArticle
+productTeam: Others
+slug: other-vtex-module-settings
+locale: en
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugEN: next-steps-after-the-go-live
+---
+
+In the **VTEX Store Overview Track**, the [VTEX modules I](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) and [VTEX modules II](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ) articles cover the main configurations for each topic. The current article presents other module settings that are not required for the [go-live](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH).
+
+## Promotions
+
+Once you have configured the required [Promotions](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promocoes) settings, you should also learn more about [customer clusters](#customer-clusters), [promotion competition](#promotion-competition), and [marketplace promotions](#marketplace-promotions), as shown below.
+
+### Customer clusters
+
+To provide exclusive purchasing advantages for a specific group of people or companies, you can [create custom promotions](https://help.vtex.com/en/tutorial/creating-promotion-for-a-customer-cluster--tutorials_342) for a customer cluster in your store. In this context, promotion details will only be displayed in the shopping cart after the selected customers log in to the site. 
+
+### Promotion competition
+
+When the store has multiple active promotions with similar characteristics that could be applied to the same product simultaneously, we have a scenario of promotion competition. In this situation, you should understand the priority in which the promotions will be applied to the product to ensure that the sales strategy is being used correctly.
+
+Learn more in the [How promotion competition works](https://help.vtex.com/en/tutorial/how-promotion-competition-works--tutorials_2270) article.
+
+### Marketplace promotions
+
+Stores operating as a VTEX marketplace can only configure [regular promotions](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) for their products, such as:
+
+- Free shipping
+- Percentage shipping
+- Percentage price
+- Price tables
+
+Learn more in the [Configuring promotions for marketplaces](https://help.vtex.com/en/tutorial/configuring-promotions-for-marketplaces--tutorials_406) article.
+
+## Logistics
+
+After completing the required [logistics](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistc) settings, VTEX accounts with [multistore or multidomain](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multiloja) architecture can launch a sales strategy to other countries and become [cross-border stores](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs). The main advantages of this type of operation include:
+
+- **Improved total logistics capacity:** The accumulated experience gained in complex logistics processes (import and export) means that the entire logistics chain (national and international) can be managed more efficiently.
+- **Business expansion:** Reaching new customers and increasing the stores' sales potential.
+- **Tax advantages:** International operations may benefit from tax incentives, such as tax exemptions, which can reduce the total cost of selling a product.
+- **Brand internationalization:** Consolidating the company's image in different markets, increasing consumer confidence and sales at national and international levels.
+
+Cross-border operations must be planned considering the following aspects:
+
+- **Export type:**
+  -  **Direct:** The company is solely accountable for product distribution and delivery to customers.
+  -  **Indirect:** The products are purchased by third parties (business partners or intermediaries located in the country of destination), assuming full responsibility for managing the operation.
+
+- **Accepting products:** Checking sales strategies and public preferences in the market where you want to operate.
+
+- **Intelligent pricing:** Determining a pricing strategy based on local costs (transportation, fees, taxes).
+
+- **Partners:** Establishing partnerships with local carriers and suppliers.
+
+- **Competitive advantages:** Defining how the business can offer advantages to customers in the new market compared to current competitors.
+
+For more information on how to start a cross-border operation, contact your CX manager or [VTEX Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8).
+
+ ## Orders
+
+After configuring the required [Order](https://help.vtex.com/en/tracks/vtex-store-overview-eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#orders) settings, you can boost your store sales by offering recurring order subscriptions and optimizing order management in the VTEX Admin using VTEX DO.
+
+### Subscriptions
+
+To allow customers to make recurring purchases of their favorite products at their desired frequency automatically, you can set up a repurchase schedule in the platform's [Subscription System](https://help.vtex.com/en/tutorial/how-subscriptions-work--frequentlyAskedQuestions_4453).
+
+### VTEX DO
+
+[VTEX DO](https://help.vtex.com/en/tutorial/vtex-do-interface--7KMbRL4OslN8DTX9oiuCiu) is the management system for tasks related to order processing in the store. It allows store operators to manually process tasks that are automatically created by the VTEX Admin. VTEX DO offers the following features:
+
+- Search and filter by status (open, not assigned) or subject (catalog, commercial, infrastructure).
+- Access details and information for completing each task.
+- Assign [users](https://help.vtex.com/en/tutorial/managing-users--tutorials_512) to tasks.
+
+![vtex-do-en](//images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/9c4752761e0a8215e6938f8fdf2d4358/next_steps_image12_EN.JPG)
+
+### VTEX Social Selling
+
+[VTEX Social Selling](https://help.vtex.com/en/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg) allows sales associates to select products and share them with customers via communication channels such as WhatsApp, Facebook Messenger, and email. This feature can be used in online and physical store operations ([VTEX Sales App](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm#vtex-sales-app)).
+
+## B2B Suite
+[B2B Suite](https://help.vtex.com/en/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#b2b-suite-apps) is a collection of [VTEX IO apps](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) that helps stores manage organizations, permissions, and checkout settings in B2B scenarios, among other benefits. This is very important for streamlining the purchase flow, reducing costs, and providing a personalized shopping experience.
+
+### B2B Suite apps
+B2B Suite apps were developed to drive B2B operations. The main apps are described below.
+
+- **Storefront Permissions:** manages access permissions for different users and groups within the store.
+- **Storefront Permissions UI:** allows VTEX Admin users to manage B2B functions and associated app permissions through the Admin itself.
+- **B2B Organizations:** groups B2B users into organizations, to which specific payment methods, price tables, and product collections can be assigned.
+- **B2B Quotes & Carts:** allows the creation of quotes and the management of shopping carts for companies.
+- **B2B Checkout Settings:** configures specific payment methods, pre-filled addresses, purchase order numbers, and order quotes.
+- **B2B Orders History:** allows B2B users to view all previous orders placed by their organization or cost center.
+- **B2B Admin Customers:** manages information and relationships with B2B customers.
+
+For more information about the applications, access [B2B Suite Application Set](https://help.vtex.com/en/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#b2b-suite-apps).
diff --git a/docs/tracks/en/overview-intelligent-search.md b/docs/tracks/en/overview-intelligent-search.md
index 1962ef2c9..37ecd9d9f 100644
--- a/docs/tracks/en/overview-intelligent-search.md
+++ b/docs/tracks/en/overview-intelligent-search.md
@@ -1,10 +1,10 @@
 ---
 title: 'Intelligent Search'
 id: 3qgT47zY08biLP3d5os3DG
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-03-05T14:47:05.068Z
-updatedAt: 2023-04-13T22:52:19.619Z
-publishedAt: 2023-04-13T22:52:19.619Z
+updatedAt: 2023-08-22T17:03:02.484Z
+publishedAt: 2023-08-22T17:01:21.074Z
 firstPublishedAt: 2020-03-05T19:53:38.701Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,10 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
+<div class="alert alert-info" role="alert"><p>
+This app is only available for stores developed using VTEX IO. Before proceeding, you need to install and configure Intelligent Search in your store.</p>
+</div>
+
 Intelligent Search is an intelligent search platform for digital commerce. It is a native VTEX platform search solution, which helps the customer throughout their shopping journey, regardless of the channel (website, mobile app, conversational, etc.).
 
 It simply and intuitively displays relevant results based on the catalog from the user's first interaction with the store through the search bar, browsing categories, or even through the window displays.
@@ -21,9 +25,8 @@ It simply and intuitively displays relevant results based on the catalog from th
 The tool also offers features such as autocomplete, displaying search and product suggestions based on the shopper's context, and filters that help when searching for the desired product.
 
 In addition, Intelligent Search uses historical click and order data to dynamically improve search and handles misspellings, plural/singular, and gender errors. Finally, its configuration makes it possible to improve the customer experience and meet the merchant's business needs.
-<div class="alert alert-info" role="alert"><p>
-This app is only available for stores developed using VTEX IO. Before proceeding, you need to install and configure Intelligent Search in your store</p>
-</div>
+
+VTEX Intelligent Search supports the following languages: Arabic, Armenian, Basque, Bengali, Brazilian Portuguese, Bulgarian, Catalan, Chinese, Czech, Danish, Dutch, Estonian, Finnish, French, Galician, German, Greek, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Persian, Polish, Portuguese, Romanian, Russian, Sorani, Spanish, Swedish, Thai, Turkish, and Urdu.
 
 In the articles listed below, you will find an overview of each Intelligent Search feature.
 
diff --git a/docs/tracks/en/partial-invoices.md b/docs/tracks/en/partial-invoices.md
index d57c2980d..5cdfec9dc 100644
--- a/docs/tracks/en/partial-invoices.md
+++ b/docs/tracks/en/partial-invoices.md
@@ -3,8 +3,8 @@ title: 'Partial Invoices'
 id: q9GPspTb9cHlMeAZfdEUe
 status: PUBLISHED
 createdAt: 2022-06-20T20:13:46.342Z
-updatedAt: 2023-03-31T22:36:12.880Z
-publishedAt: 2023-03-31T22:36:12.880Z
+updatedAt: 2024-04-01T17:51:08.329Z
+publishedAt: 2024-04-01T17:51:08.329Z
 firstPublishedAt: 2022-06-20T20:21:34.641Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -29,7 +29,8 @@ Partial invoices generate the following actions in the **Orders** module and oth
 * Partial invoices added to orders also result in partial settlements in the transaction. The total order amount will be updated after adding the invoice, and it corresponds to the amount settled in the VTEX payment gateway.   
 * The customer is automatically refunded in case there is a chargeback.  
 * In case an item and its value have to be removed from an order, the retailer can change the order, discounting the item's value — only if the previous invoices settle the corresponding amounts and keep the rest of the settled amount open.  
-* As the partial invoice only settles the amount corresponding to the invoice, requesting changes to the order amount is possible. A partial invoice keeps the transaction open, waiting for the rest of the amount to be settled or canceled — as when changing an order by discounting the amount.   
+* As the partial invoice only settles the amount corresponding to the invoice, requesting changes to the order amount is possible. A partial invoice keeps the transaction open.
+* Orders with partial invoices cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 <div class = "alert alert-info">
 The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Legacy connectors do not support the functionality.
diff --git a/docs/tracks/en/payment.md b/docs/tracks/en/payment.md
index 52416fce6..2c5d91939 100644
--- a/docs/tracks/en/payment.md
+++ b/docs/tracks/en/payment.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-using-the-app
 
 In the VTEX Sales App payment step, the sales associate will see the [payment options that have been configured](https://help.vtex.com/en/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy) for your store.
 
-![instore-payment-en](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/37e9029b397ce3f04d2b6a87462c8666/Screenshot_2022-10-21_at_14-57-36_VTEX_VTEX Sales App_Checkout.png)
+![instore-payment-en](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/37e9029b397ce3f04d2b6a87462c8666/Screenshot_2022-10-21_at_14-57-36_VTEX_VTEX Sales App_Checkout.png)
 
 The top bar of the payment screen displays the following options:
 
@@ -45,7 +45,7 @@ To configure a payment method, follow the [VTEX Sales App - Payments](https://he
 
 The customer must select the **Cash** option and click `Complete Sale`. 
 
-![instore-dinheiro-en](https://images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/868ca0e64245ec78ed6794e0e4e5726f/Screenshot_2022-10-21_at_14-57-55_VTEX_VTEX Sales App_Checkout.png)
+![instore-dinheiro-en](//images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/868ca0e64245ec78ed6794e0e4e5726f/Screenshot_2022-10-21_at_14-57-55_VTEX_VTEX Sales App_Checkout.png)
 
 Then, you must complete the transaction with the sales associate. Depending on the store's configuration, it can be either [manual or automatic](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT). 
 
@@ -53,21 +53,21 @@ Then, you must complete the transaction with the sales associate. Depending on t
 
 The customer must select **Pix** and click `Complete Sale`. 
 
-![instore-pix-en](https://images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/a65732c1fb0af5e4f5a161b8b64c6186/Screenshot_2022-10-21_at_14-58-22_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix-en](//images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/a65732c1fb0af5e4f5a161b8b64c6186/Screenshot_2022-10-21_at_14-58-22_VTEX_VTEX Sales App_Checkout.png)
 
 After completing the sale, the QR Code will be displayed on the VTEX Sales App screen. The customer must scan it using their phone to proceed with payment. 
 
-![instore-pix2-en](https://images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/f252d0b00eff1385cc1e14cb7dbdf3bf/image.png)
+![instore-pix2-en](//images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/f252d0b00eff1385cc1e14cb7dbdf3bf/image.png)
 
 After payment, the sale will be processed and confirmed on the order page, as shown in the image below.
 
-![instore-pix3-en](https://images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/0c648cce0a942b1eb2d86420372d9729/Screenshot_2022-10-21_at_14-58-53_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix3-en](//images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/0c648cce0a942b1eb2d86420372d9729/Screenshot_2022-10-21_at_14-58-53_VTEX_VTEX Sales App_Checkout.png)
 
 ### Boleto (Brazil)
 
 The customer must select **Boleto** and click `Complete Sale`. 
 
-![instore-boleto-en](https://images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/61116b8b732842719e8783ec3711e22f/Screenshot_2022-10-21_at_14-57-50_VTEX_VTEX Sales App_Checkout.png)
+![instore-boleto-en](//images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/61116b8b732842719e8783ec3711e22f/Screenshot_2022-10-21_at_14-57-50_VTEX_VTEX Sales App_Checkout.png)
 
 The boleto will be sent to the customer by email. Once the boleto payment is confirmed, so is the purchase.
 
@@ -75,7 +75,7 @@ The boleto will be sent to the customer by email. Once the boleto payment is con
 
 The customer must select the **Credit Card** option, choose the number of installments for the purchase, and click `Complete Sale`. 
 
-![instore-credito-en](https://images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ef042ee59ae511b33c95c708597f6f99/Screenshot_2022-10-21_at_14-58-11_VTEX_VTEX Sales App_Checkout.png)
+![instore-credito-en](//images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ef042ee59ae511b33c95c708597f6f99/Screenshot_2022-10-21_at_14-58-11_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App will display a waiting screen while the payment is made though the store's card machine. Once the system accepts the payment, the transaction will be confirmed.
 
@@ -83,6 +83,6 @@ VTEX Sales App will display a waiting screen while the payment is made though th
 
 The customer must select **Debit Card** and click `Complete Sale`. 
 
-![instore-debito-en](https://images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/73fb933dcd5a70d63c7bc1c73bbad4c3/Screenshot_2022-10-21_at_14-58-01_VTEX_VTEX Sales App_Checkout.png)
+![instore-debito-en](//images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/73fb933dcd5a70d63c7bc1c73bbad4c3/Screenshot_2022-10-21_at_14-58-01_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App will display a waiting screen while the payment is made through the store's card machine. Once the system accepts the payment, the transaction will be confirmed.
diff --git a/docs/tracks/en/personal-data.md b/docs/tracks/en/personal-data.md
new file mode 100644
index 000000000..f9462bf34
--- /dev/null
+++ b/docs/tracks/en/personal-data.md
@@ -0,0 +1,47 @@
+---
+title: 'Personal data'
+id: 65ZqZlNWcmFSOqZQxr8gha
+status: PUBLISHED
+createdAt: 2024-05-03T14:39:14.904Z
+updatedAt: 2024-05-03T21:13:09.925Z
+publishedAt: 2024-05-03T21:13:09.925Z
+firstPublishedAt: 2024-05-03T16:42:08.464Z
+contentType: trackArticle
+productTeam: Others
+slug: personal-data
+locale: en
+trackId: 65ZqZlNWcmFSOqZQxr8gha
+trackSlugEN: data-and-privacy
+---
+
+Personal data or _Personally Identifiable Information_ (PII) is any information relating to a natural person that is capable of identifying them directly (such as name, ID number, and email address) or indirectly (such as IP addresses, physical addresses, and [cookies](https://vtex.com/us-en/privacy-and-agreements/vtex-platform-cookies-information/)).
+
+Sensitive personal data is information related to ethnicity, religious beliefs, political opinion, trade union membership, health or sexual life, and genetic or biometric data. Misuse of this type of data can lead to severe harm or discriminatory treatment of the data subject.
+
+## Personal data processed by VTEX
+
+VTEX processes customers' personal data only when necessary, complying with the requirements of each platform module to carry out ecommerce operations. See below the list of personal data that VTEX may process:
+
+* Name
+* Email
+* IP address
+* Navigation information ([cookies](https://vtex.com/us-en/privacy-and-agreements/vtex-platform-cookies-information/))
+* Cart information
+* Order details and history
+* Delivery address
+* Identification number (when required by the country where the store operates)
+* Gift card history
+* Abandoned cart
+* [Conversation Tracker](https://help.vtex.com/en/tutorial/conversation-tracker--tutorials_195) chat
+* Session passwords (encrypted)
+* Generated tokens
+
+The data list above is described in the [Data Processing Addendum (DPA)](#data-processing-addendum-dpa).
+
+VTEX does not sell, monetize, enrich, or transfer any customer personal data to other companies.
+
+## Data minimization
+
+The principle of data minimization refers to collecting, processing, and storing only the information strictly necessary to achieve a specific purpose. This principle makes it possible to limit the amount of personal data collected and retained, thus reducing the risks associated with excessive information processing.
+
+In this sense, VTEX collects only the minimum amount of data necessary to process the orders received, which means only the personal data strictly necessary for ecommerce operations.
diff --git a/docs/tracks/en/planning-the-go-live.md b/docs/tracks/en/planning-the-go-live.md
new file mode 100644
index 000000000..6ffa18cd4
--- /dev/null
+++ b/docs/tracks/en/planning-the-go-live.md
@@ -0,0 +1,195 @@
+---
+title: 'Planning the go-live'
+id: 6xYnNxDHUcY6FyChgziCoH
+status: PUBLISHED
+createdAt: 2024-01-08T13:11:05.385Z
+updatedAt: 2024-06-27T00:28:49.687Z
+publishedAt: 2024-06-27T00:28:49.687Z
+firstPublishedAt: 2024-02-22T14:07:27.548Z
+contentType: trackArticle
+productTeam: Others
+slug: planning-the-go-live
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+Go-live is when your store becomes available for customers to visit and make purchases. This article explains how to plan all the necessary steps for the go-live of a VTEX store. It is structured as follows:
+
+1. [Preparing for the go-live](#1-preparing-for-the-go-live)
+2. [Store settings](#2-store-settings)
+3. [Domain and account settings](#3-domain-and-account-settings)
+4. [Testing before the go-live](#4-testing-before-the-go-live)
+5. [Domain registration and pointing request](#5-domain-registration-and-pointing-request)
+6. [Go-live](#6-go-live)
+7. [Post-go-live actions](#7-post-go-live-actions)
+
+## Before you begin
+
+When preparing a store for go-live, you should have already defined the implementation team or [partner agency](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners), chosen the [VTEX account types](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#vtex-account-types) based on your operation, and planned the store's architecture. More information on these steps can be found in the [Accounts and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) article.
+
+## 1. Preparing for the go-live
+
+The process of a store's go-live, including the necessary settings and tests, can vary according to the store's operational complexity. For this reason, we recommend planning all the necessary steps for the go-live at least 15 days in advance.
+
+The following image shows the planning steps for the VTEX store go-live:
+
+![go-live-en](//images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/42ac375fd2ab83f78c34dfca3da81260/golive_1_EN.png)
+
+### Define the MVP
+
+First, you must determine what is essential for the _Minimum Viable Product_ (MVP), including the functionalities, pages, and information required for the store's official launch.
+
+It is important to list everything that must be implemented before going live. Features that are desirable but not essential should be listed separately and implemented as incremental changes after the launch.
+
+### Planning a penetration test (optional)
+
+Merchants who want to run a penetration test before going live need to request prior authorization, following the guidelines in the [Penetration tests and vulnerability notifications](https://help.vtex.com/en/tutorial/penetration-testing-and-vulnerability-notice--6jodF6s1I50Fg84ZwutOCb) guide. 
+
+You must send the report with the results to [VTEX Support](https://help.vtex.com/en/support) at least **45 days** before the go-live date. During this period, VTEX will analyze the results and address any vulnerabilities identified. 
+
+Therefore, the whole planning process should start at least 45 days in advance, plus additional time for the period between the request and running the test.
+
+### Set a schedule
+
+To organize the teams involved and go live on the planned date, you need to create a _roadmap_, i.e., a document with the actions required for the go-live, indicating who is accountable for each step and the agreed deadlines. The following image shows a timeline as an example:
+
+![golive 2 EN](//images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/bae691008a305280c7c3d14aeb319b11/golive_2_EN.png)
+
+We recommend scheduling regular meetings with the [implementation teams](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) to ensure alignment and, if necessary, establishing a _war room_ to deal with pending issues in the week before the go-live.
+
+### Plan a soft launch
+
+In addition to performing tests during project development, we recommend including a soft launch in the schedule, i.e., a launch restricted to a specific group or market before the official launch. This step can help refine and fix details missed during the implementation project.
+
+After the official launch date, when the store is fully operational, developers can continue to iterate the MVP and add improvements without disrupting sales.
+
+## 2. Store settings
+
+Before going live, you must ensure that all essential settings are configured for your store to operate smoothly. To do this, we recommend checking the [Store configuration checklist](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx). Each item must be checked to ensure the settings have been completed to meet the store's operational characteristics.
+
+<div class="alert alert-warning">
+  <p>The checklist above lists basic features and settings necessary for running a VTEX store. It is up to each store's<a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners"> implementation team</a> to determine the features and settings to apply to deliver the desired shopping experience for customers. We recommend checking all the store's operational aspects and adding them to the list, if necessary.</p>
+</div>
+
+## 3. Domain and account settings
+
+Once the store's internal settings have been completed, you'll need to configure the settings related to the domain and the VTEX account. These changes do not depend on the expected go-live date but must be made before the testing.
+
+1. [Check domain in CDNs](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#checking-domain-in-cdns): Make sure the domain is not previously registered on the [Cloudfront](https://aws.amazon.com/en/cloudfront/) or [Azion](https://www.azion.com) platform.
+2. [Configure CAA records](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#configuring-caa-records): Indicate that the **Let's Encrypt** certificate authority (CA) is authorized to generate and renew certificates attesting to the domain's identity. This step is only necessary if there is a CAA record on the DNS server.
+3. [Put your account in production](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#putting-your-account-into-production): Activate the VTEX account in production. Even after this activation, the store remains unavailable for access by external customers. Viewing and purchasing products in the store will only be possible after the go-live has been completed, according to the steps described in the following sections of this article.
+
+<div class="alert alert-warning">
+  <p>Once the account is active in production, all orders will be automatically charged, and the <a href="https://help.vtex.com/en/tutorial/understanding-the-value-of-approved-revenues--tutorials_4322#understanding-the-values-of-approved-revenues">take rate</a> will be applied based on the plan agreed upon with VTEX. This includes orders placed on the <code>{accountname}.myvtex.com</code> domain, even if they were placed for testing purposes.</p>
+</div>
+
+For more information, see the [Settings](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX) article, which is part of the detailed [Go-live](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/1iP90RcJvlrfQhnlxM54wo) track article.
+
+## 4. Testing before the go-live
+
+We recommend running tests before the go-live to check the store's behavior and avoid errors or pending issues during the official launch. The following sections explain the two most common test types: [Quality Assurance (QA)](#quality-assurance-qa) and [User Acceptance Testing (UAT)](#user-acceptance-testing-uat).
+
+On VTEX, you can create separate environments to run these tests. In this case, you need to replicate the settings of the main environment that will be tested. For example, to test how a promotion works, you must configure all the necessary settings to simulate a scenario in which it would be applied, including products, prices, logistics, checkout, payment methods, etc.
+
+To plan the testing step, contact [our support](https://help.vtex.com/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy) team, so you can [request a test environment](https://help.vtex.com/en/tutorial/requesting-a-test-environment--2nmZAHlfQoGsCWmEWGIoGy).
+
+<div class="alert alert-warning">
+  <p>If the store is<a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#development-environment"> built using VTEX IO</a>, you can run A/B tests between workspaces, i.e., compare the performance of storefront development environments. For more details, see the<a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing"> Running A/B tests</a> developer guide.</p>
+</div>
+
+### Quality Assurance (QA)
+
+The QA (Quality Assurance) testing step involves checking and validating all the store's elements and features before the store is available to the general public. This process includes testing every element thoroughly, from the site's navigability and performance to different purchase flow scenarios, payment processing, and system integrations.
+
+The objective is to identify and fix any issues, errors, or bugs to ensure the store is ready and consistent with the intended scope of the MVP at launch. In this step, you should document bugs and errors and plan how to fix them before the go-live date.
+
+### User Acceptance Testing (UAT)
+
+UAT, or User Acceptance Testing, is the final testing phase in which end users validate and verify if the store meets the expectations and features required for the MVP. Generally, this type of test involves the store's staff and, in some cases, a selected group of customers.
+
+During UAT, testers explore the site, make test purchases, and evaluate the overall user experience. This step provides another opportunity to report, document, and fix any issues or unwanted behavior in the experience before the official launch, thus enhancing the likelihood of success after the go-live.
+
+## 5. Domain registration and pointing request
+
+Once the necessary tests and fixes have been completed, you must prepare the store for the go-live. Between three and seven days before the official launch date, you should do the following:
+
+1. [Register the domain on VTEX](https://help.vtex.com/en/tutorial/configuring-domains-in-account-management--tutorials_2450): Go to **Account settings** in the VTEX Admin to connect the address to the store.
+
+   <div class="alert alert-warning">
+    <p>Once you have registered the domain, you have seven days to complete the go-live. If the store does not complete the necessary go-live procedures within this period, you will need to go back to the registration and save it again.</p>
+   </div>
+
+2. **Request internal pointing:** Open a ticket to [VTEX Support](https://help.vtex.com/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy) to request internal DNS pointing. It can take up to three working days to complete this request.
+
+    The request type forwarded must be consistent with the [technology chosen](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) for the storefront:
+
+  <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Technology</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Request</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Store Framework or FastStore (VTEX IO)</td>
+      <td class="t-body pa5" style="min-width: 10rem;">Request <a href="https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#requesting-io-pointing" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">internal DNS pointing for VTEX IO</a> by submitting a ticket to <a href="https://help.vtex.com/en/support" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">VTEX Support</a>.<br> <br>More information in the articles:<ul><li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-go-live" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Going live with a new store</a> (Store Framework)</li><li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-migrating-storefront-from-legacy-to-io" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Migrating your storefront from Legacy CMS Portal to Store Framework</a></li><li><a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Configuring external DNS for a custom domain</a> (FastStore)</li></ul></td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Legacy CMS Portal</td>
+      <td class="t-body pa5" style="min-width: 10rem;">If access to the store is restricted by a <a href="https://help.vtex.com/en/tutorial/creating-a-trade-policy--563tbcL0TYKEKeOY4IAgAE" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">trade policy</a> with a conditional rule, and your storefront was built using <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Legacy CMS Portal</a>, you need to request a <a href="https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#requesting-special-pointing" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">special internal pointing</a>. A typical example is B2B stores, which restrict access to pre-approved companies. The special pointing request is made by <a href="https://help.vtex.com/en/support" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">VTEX Support</a>, indicating the trade policy and the configured conditional rule.</td>
+    </tr>
+  </tbody>
+  </table>
+
+Regardless of the request type, the ticket to VTEX Support must have the following information:
+
+- Title stating the intention to go live.
+- If the [storefront technology](http://link-implement-frontend) was developed on VTEX IO or Legacy CMS Portal.
+- URL to be pointed to.
+- Time for internal pointing to be carried out, between 9 a.m. and 5 p.m. UTC-3.
+- Indicate if the store has conditional rules for [trade policies](https://help.vtex.com/en/tutorial/creating-a-trade-policy--563tbcL0TYKEKeOY4IAgAE).
+- If you are migrating a live site to VTEX, indicate whether it uses the Azion CDN or Cloudfront.
+
+<div class="alert alert-warning">
+  <p>After receiving confirmation of the internal pointing, you are required to complete the standard DNS pointing within five days. Otherwise, the internal pointing will be deleted, and you must submit a new request.</p>
+</div>
+
+## 6. Go-live
+
+At the time of go-live, after confirming the internal pointing from the previous step, you will need to execute the DNS pointing and then notify VTEX:
+
+1. [Set up DNS pointing](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#setting-up-dns-pointing): In the domain's DNS zone, create a CNAME entry in the desired subdomain for the destination ``{domain}.cdn.vtex.com``. The ``{domain}`` must be the same as the one registered on VTEX.
+
+   <div class="alert alert-warning">
+    <p>DNS propagation pointing can take between 24 and 48 hours. As a result, the configured address might not be immediately accessible to everyone after the configuration.</p>
+   </div>
+
+2. [Notify the pointing:](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#notifying-the-pointing) To make your store available to the general public, you must notify the VTEX platform that pointing has been completed. To do this, you must save your **Account settings** in the VTEX Admin again.
+
+   <div class="alert alert-warning">
+    <p>If the store was built using<a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#faststore"> FastStore</a>, you will also need to follow the steps described in the<a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns"> Configuring external DNS for a custom domain</a> article.</p>
+   </div>
+
+Once the above steps have been completed, the store will be available on the registered domain, allowing customers to access it and make purchases.
+
+## 7. Post-go-live actions
+
+After the store's official launch, you should ensure that customers have access to the correct address and monitor sales performance and site navigation by taking some important actions.
+
+### Configuring redirects
+
+After the go-live, you can access the store on the [registered domain](https://help.vtex.com/en/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#registering-the-domain-on-vtex). However, you may need to redirect old addresses or addresses without the `www` subdomain to ensure access to the new store address. To do this, we recommend checking the tutorials from the following articles:
+
+- [Redirection from other addresses](https://help.vtex.com/en/tutorial/redirection-from-other-addresses--3Xi2AeLUx2QpJQu8DTX8KQ)
+- [Configuring access without www](https://help.vtex.com/en/tutorial/configuring-access-without-www--tutorials_4278)
+
+### Monitoring store performance
+
+We recommend monitoring the store's performance after launch using the [Dashboards](https://help.vtex.com/en/tutorial/dashboards-overview--1yn2nZUoXtDO3teTEJsCNl) menu in the VTEX Admin, which includes the following pages:
+
+- [Overview](https://help.vtex.com/en/tutorial/store-overview--P8ahguoRs0U3PzmXg2wuQ): The main metrics that impact store revenue. In this dashboard, you can monitor the main sales evolution metrics by analyzing order trends, conversion rates, and sales funnel charts.
+- [Sales Performance](https://help.vtex.com/en/tutorial/sales-performance--3DMube0sEsK9vPcRYGas72): Dashboard for unified commerce, which helps stores grow their business and make more accurate decisions.
+
+Besides the tools available in the VTEX Admin, you can also monitor your store's performance through [Google Analytics](https://analytics.google.com/analytics/web/), provided it has been previously set up. For more information, see the [Configuring Google Analytics 4 in VTEX stores](https://help.vtex.com/en/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG) guide.
diff --git a/docs/tracks/en/preco-base-definicao-de-conceito.md b/docs/tracks/en/preco-base-definicao-de-conceito.md
index ebce13a25..2f59fa098 100644
--- a/docs/tracks/en/preco-base-definicao-de-conceito.md
+++ b/docs/tracks/en/preco-base-definicao-de-conceito.md
@@ -18,7 +18,7 @@ trackSlugEN: prices-101
 
 A SKU's base price is the value which results from merging the **Cost Price** with the **Markup**, the desired profit margin with the SKU's sale. It represents the SKU's __reference price__ for all price tables. 
 
-![base-price-en](https://images.ctfassets.net/alneenqid6w5/cbmJa638a5NuZHtjF1FPN/4bb70f39b01a19c15ec07525e8372329/base-price-en.png)
+![base-price-en](//images.ctfassets.net/alneenqid6w5/cbmJa638a5NuZHtjF1FPN/4bb70f39b01a19c15ec07525e8372329/base-price-en.png)
 
 This **base price** can be combined with a price table's applied **price rule**. If there are no registered price rules, a price table's selling price will be equal to the base price itself.
 
diff --git a/docs/tracks/en/preco-fixo-definicao-de-conceito.md b/docs/tracks/en/preco-fixo-definicao-de-conceito.md
index d7191119c..9571e8a4f 100644
--- a/docs/tracks/en/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/en/preco-fixo-definicao-de-conceito.md
@@ -73,7 +73,7 @@ Let's suppose that an SKU has two fixed prices linked to it. In addition, both p
 
 For example, the first fixed price is set at __U$ 50,00__ and its schedule runs from __10AM__ to __4PM__. The second price is set at __U$ 25,00__ and is scheduled from __noon__ to __8PM of the same day__. Therefore, the prices compete for the same schedule between *noon and 4PM*, which means that the __U$ 25,00__ SKU sales price will prevail during this time.
 
-![fixed price - example2](https://images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
+![fixed price - example2](//images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
 
 ### Competing criteria for minimum number of cart items
 
@@ -83,7 +83,7 @@ Let's suppose that you've added a fixed price of U$ 200,00 for __two of more ite
 
 Which price would in this case be applied to five or more items? The sales price would be the lower one, U$ 100,00. 
 
-![fixed price - example1](https://images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
+![fixed price - example1](//images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
 
 ## Examples 
 
diff --git a/docs/tracks/en/prerequisites-for-using-instore.md b/docs/tracks/en/prerequisites-for-using-instore.md
index b1870aebe..0be764dbb 100644
--- a/docs/tracks/en/prerequisites-for-using-instore.md
+++ b/docs/tracks/en/prerequisites-for-using-instore.md
@@ -3,8 +3,8 @@ title: 'Prerequisites for using VTEX Sales App'
 id: 1wtAanSRA3g2316dw7bw8u
 status: PUBLISHED
 createdAt: 2020-06-28T13:28:33.600Z
-updatedAt: 2023-05-31T15:30:38.223Z
-publishedAt: 2023-05-31T15:30:38.223Z
+updatedAt: 2024-06-27T16:50:09.189Z
+publishedAt: 2024-06-27T16:50:09.189Z
 firstPublishedAt: 2020-06-28T13:41:36.817Z
 contentType: trackArticle
 productTeam: Shopping
@@ -29,15 +29,12 @@ To maintain the equipment and the smooth running of your operation, it is import
 
 ### Tablets, smartphones and computers
 
-The VTEX Sales App app works on tablets and smartphones using **Android 6.0** (or newer) and **iOS 9** (or newer) operating systems.
+We recommend using devices updated to the latest operating system version or at least to one of the following:
 
-Some examples of devices that can be used:
+* Three most recent versions of iOS, or
+* Four most recent versions of Android.
 
-* Samsung Galaxy Tab A Note
-* Motorola G4
-* Samsung S8
-
-We recommend that the devices used to access VTEX Sales App have 4G chips for internet access. This way, your store will continue to function normally even if there are problems with the Wi-Fi network.
+When accessing VTEX Sales App, the devices must use 4G chips for internet connection. This ensures your store will operate seamlessly, even in the event of Wi-Fi connection issues.
 
 VTEX Sales App also works on computers that use the **Windows** operating system, provided that the following minimum requirements are met:
 
@@ -86,6 +83,16 @@ To print electronic invoices and credit card receipts, you will need a non-fisca
 
 VTEX has several partners who enable the operation of physical stores. Each partner has a specific role in ensuring that the entire sales process works safely.
 
+Among these partners are:
+
+- Integration with POS:
+    - Jitterbit
+    - Neomode
+Payment Integration:
+    - Pagarme
+    - Adyen
+    - Cielo
+
 VTEX has a standard contract with these partners to facilitate the implementation of your products, but you must better terms directly with them.
 
 ### Payments
diff --git a/docs/tracks/en/prices-module-overview.md b/docs/tracks/en/prices-module-overview.md
index 3e3800d00..69b0d574c 100644
--- a/docs/tracks/en/prices-module-overview.md
+++ b/docs/tracks/en/prices-module-overview.md
@@ -3,8 +3,8 @@ title: 'Pricing - Overview'
 id: 3N9xYhnampRQOrfaTAOxNu
 status: PUBLISHED
 createdAt: 2019-07-09T19:26:54.473Z
-updatedAt: 2023-03-29T19:18:12.146Z
-publishedAt: 2023-03-29T19:18:12.146Z
+updatedAt: 2023-08-21T17:16:35.856Z
+publishedAt: 2023-08-21T17:16:35.856Z
 firstPublishedAt: 2019-07-11T21:35:16.813Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
diff --git a/docs/tracks/en/pricing-system-architecture.md b/docs/tracks/en/pricing-system-architecture.md
index 0a9fdfad4..5400ade4c 100644
--- a/docs/tracks/en/pricing-system-architecture.md
+++ b/docs/tracks/en/pricing-system-architecture.md
@@ -3,8 +3,8 @@ title: 'Pricing system architecture'
 id: 7GptzvlPDVM11ojEjywIQx
 status: PUBLISHED
 createdAt: 2019-07-04T13:51:00.418Z
-updatedAt: 2022-07-27T20:39:31.113Z
-publishedAt: 2022-07-27T20:39:31.113Z
+updatedAt: 2024-04-22T19:20:30.485Z
+publishedAt: 2024-04-22T19:20:30.485Z
 firstPublishedAt: 2019-07-17T19:40:40.258Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -33,7 +33,7 @@ These may be:
 
 Below, we can see a blueprint of how the concepts of *prices*, *price table* and *context* are related to one another:
 
-![Architecture-EN](https://images.ctfassets.net/alneenqid6w5/6e0dbJq89EfPqJTKUiuju8/b0acbc822f1da5c78e100c075831982d/Architecture__2_.svg)
+![Architecture-EN](//images.ctfassets.net/alneenqid6w5/6e0dbJq89EfPqJTKUiuju8/b0acbc822f1da5c78e100c075831982d/Architecture__2_.svg)
 
 ## Computed price
 
@@ -47,23 +47,23 @@ The pricing module takes these 4 criteria into account when calculating a price
 - Fixed Price
 
 1. In cases where the SKU only has the *base price* set, the computed price for a specific price table will be equal to the **base price**.
-![rule1-EN](https://images.ctfassets.net/alneenqid6w5/49vh298CSTLJBLWRvAt9Wx/b6e4cd1212dfbcffbeff6e8feafc7a3d/rule1__1_.svg) 
+![rule1-EN](//images.ctfassets.net/alneenqid6w5/49vh298CSTLJBLWRvAt9Wx/b6e4cd1212dfbcffbeff6e8feafc7a3d/rule1__1_.svg) 
 
 2. When the SKU has a *price rule* configured for a specific price table, the computed price will be equal to **the base price, modified by the price rule**
-![rule2-EN](https://images.ctfassets.net/alneenqid6w5/49T4V2FxtwLPfQdPWp27Hm/746255f33fb8d0dc0fc6696808971e37/rule2__1_.svg) 
+![rule2-EN](//images.ctfassets.net/alneenqid6w5/49T4V2FxtwLPfQdPWp27Hm/746255f33fb8d0dc0fc6696808971e37/rule2__1_.svg) 
 
 3. In another scenario, we will consider a SKU with a *base price*, a *price rule* and *rounding rules*. **The computer price for a specific price table will be the result of these three factors**. First, the base price will be changed by the price rule. Afterwards, the psychological pricing's rounding takes place.
-![rule3-EN](https://images.ctfassets.net/alneenqid6w5/7xwUkHqOkGx6toE6qkXQ2M/ab20002cafca089dcfbb909970dd4e4b/rule3__1_.svg) 
+![rule3-EN](//images.ctfassets.net/alneenqid6w5/7xwUkHqOkGx6toE6qkXQ2M/ab20002cafca089dcfbb909970dd4e4b/rule3__1_.svg) 
 
 4. Lastly, if the SKU has a *fixed price*, **a specific price table's computed price will be equal to the fixed price**. This price weighs more than any of the others, which results in the pricing module *ignoring the other prices* when a fixed price is associated to an SKU. 
-![rule4-EN](https://images.ctfassets.net/alneenqid6w5/7qQe04LL529cFeyW2UjGws/3b80fb4386164dd52d792c81bf4956c0/rule4__1_.svg)
+![rule4-EN](//images.ctfassets.net/alneenqid6w5/7qQe04LL529cFeyW2UjGws/3b80fb4386164dd52d792c81bf4956c0/rule4__1_.svg)
 
 ## Validating a computed price
 
 To check an SKU's sales price for a specific price table, you can query the **computed price value** in the **Price List** section in admin. In the example below, we can see that the computed price for **SKU 14** in **trade policy table 1** is equal to **334,62**:
-![computed-price-en](https://images.ctfassets.net/alneenqid6w5/4LtPPVFSSHGOZAENhHeRyZ/56a5705d20dff8ebe13d8fdfa181a330/computed-price-en.png)
+![computed-price-en](//images.ctfassets.net/alneenqid6w5/4LtPPVFSSHGOZAENhHeRyZ/56a5705d20dff8ebe13d8fdfa181a330/computed-price-en.png)
 
-You can also check an SKU's computed price in a price table by **making an API request**. To achieve this, you'll need to send a **GET** to the [Get Computed Price by price table or trade policy](https://developers.vtex.com/vtex-rest-api/reference/getcomputedpricebypricetable) call.
+You can also check an SKU's computed price in a price table by **making an API request**. To achieve this, you'll need to send a **GET** to the [Get Computed Price by price table or trade policy](https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-) call.
 
 This request returns an SKU's `sellingPrice` from price table `1`. **This is the information that *Pricing* shows as *the SKU's selling price***. 
 
diff --git a/docs/tracks/en/printing-an-order-summary.md b/docs/tracks/en/printing-an-order-summary.md
index ae3b1b761..8deea3208 100644
--- a/docs/tracks/en/printing-an-order-summary.md
+++ b/docs/tracks/en/printing-an-order-summary.md
@@ -3,8 +3,8 @@ title: 'Printing an order summary'
 id: 5UeqJA3sHp5goJacvHwPoS
 status: PUBLISHED
 createdAt: 2021-08-05T14:40:53.752Z
-updatedAt: 2023-05-31T15:23:48.750Z
-publishedAt: 2023-05-31T15:23:48.750Z
+updatedAt: 2023-07-26T19:01:33.402Z
+publishedAt: 2023-07-26T19:01:33.402Z
 firstPublishedAt: 2021-08-05T14:47:18.680Z
 contentType: trackArticle
 productTeam: Shopping
@@ -18,7 +18,7 @@ When an order is placed using VTEX Sales App, it is possible to print the order
 
 To do this, the sales associate can click on the `Print order` button on the completed order screen, as illustrated below. Another option is to configure VTEX Sales App to print the order summary automatically as soon as an order is placed.
 
-![15. Configurar impressão de resumo do pedido - 1 - EN](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/790d42c635583e24fafdd613393184a4/print-order-en.png)
+![15. Configurar impressão de resumo do pedido - 1 - EN](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/790d42c635583e24fafdd613393184a4/print-order-en.png)
 
 To enable order summary printing, follow the steps below.
 
@@ -50,13 +50,13 @@ After obtaining the AppKey and AppToken, follow the steps below.
 2. Open the VTEX Sales App app and enter the name of the store where you want to configure the printer.
 3. In the VTEX Sales App main menu, go to **Settings** and click on the <i class="fas fa-cog"></i> **Configure device** option, as shown below.
 
-![15. Configurar impressão de resumo do pedido - 2 - EN](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/6b9437dbb66b4f0d86329a38ba619e5a/configuration-en.png)
+![15. Configurar impressão de resumo do pedido - 2 - EN](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/6b9437dbb66b4f0d86329a38ba619e5a/configuration-en.png)
 
 <ol start="4">
   <li>You will see the summary of the configured device. If this is the first time this configuration is performed, the fields on the screen will be empty, as shown in the image below. If a device has been previously configured, you will see the <b>Device name</b> and <b>Default printer</b>. Click on the <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">Edit</span> button.</li>
 </ol>
 
-![15. Configurar impressão de resumo do pedido - 4 - EN](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/19ce84bc4f5f802487e75c9ce03c8fd6/image_3.png)
+![15. Configurar impressão de resumo do pedido - 4 - EN](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/19ce84bc4f5f802487e75c9ce03c8fd6/image_3.png)
 
 <ol start="5">
   <li>Fill out the form according to the descriptions below.
diff --git a/docs/tracks/en/product-details.md b/docs/tracks/en/product-details.md
index b1ca273c9..f6d85fac1 100644
--- a/docs/tracks/en/product-details.md
+++ b/docs/tracks/en/product-details.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-using-the-app
 
 When clicking on the details of a product that appears in the VTEX Sales App search results, or when beeping a product, the sales associate is directed to the product details page.
 
-![instore-pdp-en](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/6f2be63cd50dfda6d84bae201315f387/pdp-en.png)
+![instore-pdp-en](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/6f2be63cd50dfda6d84bae201315f387/pdp-en.png)
 
 This page shows the name of the product, its photo gallery, variations, description and availability. On this screen, the sales associate can add the product to the cart.
 
diff --git a/docs/tracks/en/product-integration-errors-with-amazon.md b/docs/tracks/en/product-integration-errors-with-amazon.md
new file mode 100644
index 000000000..8121c4605
--- /dev/null
+++ b/docs/tracks/en/product-integration-errors-with-amazon.md
@@ -0,0 +1,156 @@
+---
+title: 'Product integration errors with Amazon'
+id: 4HsdzgoYxgQNtCBCRttKDA
+status: PUBLISHED
+createdAt: 2023-06-29T19:08:38.476Z
+updatedAt: 2023-09-26T15:02:03.011Z
+publishedAt: 2023-09-26T15:02:03.011Z
+firstPublishedAt: 2023-06-29T22:27:35.313Z
+contentType: trackArticle
+productTeam: Channels
+slug: product-integration-errors-with-amazon
+locale: en
+trackId: 6sgd4Pagy3wNsWKBvmIFrP
+trackSlugEN: product-integration-errors-with-amazon
+---
+
+There are several reasons why a product may not integrate correctly between Amazon and your VTEX store, and each one generates a notification about the nature of the error. You can find the error message in the VTEX Admin if you go to the **Marketplace > Connections > Products** module, or if you search for it in the search bar. On the Products page, filter by Amazon as the marketplace and click the product to view the message.  
+
+After fixing the error, you must manually reprocess the inventory integration for that SKU. You can do that from the same place where you view the error by clicking **Actions > Reprocess.**  
+
+In this article, we cover the following errors:  
+
+- [Errors in the Amazon category and attribute mapping spreadsheet](#Errors-in-the-Amazon-category-and-attribute-mapping-spreadsheet)
+- [Errors related to missing mandatory attributes on Amazon](#Errors-related-to-missing-mandatory-attributes-on-Amazon)
+- [Errors related to divergence between VTEX and Amazon catalogs (offer matching)](#Errors-related-to-divergence-between-VTEX-and-Amazon-catalogs-(offer-matching))
+- [Errors related to Amazon tokens and permissions](#Errors-related-to-Amazon-tokens-and-permissions)
+- [Errors related to the configuration of the Amazon integration](#Errors-related-to-the-configuration-of-the-Amazon-integration)
+- [Errors when submitting the VTEX global category](#Errors-when-submitting-the-VTEX-global-category)
+- [Inactive SKU warning](#Inactive-SKU-warning)
+
+## Errors in the Amazon category and attribute mapping spreadsheet
+
+  **The VTEX global category for this SKU was not completed or was completed incorrectly in the mapping spreadsheet**
+
+This error occurs when the [global category](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) is not configured or was configured incorrectly. Amazon uses the global category from the VTEX platform to map products. That is why it is important that the equivalence between the VTEX global category and the Amazon general categories is done correctly.
+
+To fix this error, [configure the global category](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#configuracao-da-categoria-global) of your product.
+
+  **Specification (X) from the mapping spreadsheet was not found in the product or SKU specification in your VTEX catalog**
+
+This error occurs when the spreadsheet contains a specification that does not exist in the VTEX catalog. To fix this error, you need to add a [product](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) or [SKU](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) specification. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) and check the `VALID VALUES` tab.
+
+  **Value (X) from the mapping spreadsheet is not an attribute/specification value supported by Amazon**
+
+This error occurs when specification X is not supported by Amazon. You need to [add a specification](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) that is supported by Amazon. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) and check the `VALID VALUES` tab.
+
+  **The VTEX global category ID for this product was not found in the mapping spreadsheet**
+
+This error occurs when the [global category](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) is not configured or was configured incorrectly. To fix this error, [configure the global category](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#configuracao-da-categoria-global) of your product.
+
+  **The "Material" or "Department" specification value from the spreadsheet is not an attribute/specification supported by Amazon**
+
+For both of these errors, the [VTEX global category](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) of the product selected by the seller requires the **Department** or **Material** attributes as mandatory in the product, and completing the [mapping spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento). [Add](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) the attribute to the product and complete it in the spreadsheet as shown in the example below:
+
+|**CategoryID**|**VariationTheme**|**Type**|**VTEXSpecification**|**AmazonSpecification**|**VTEXValue**|**AmazonValue**|
+| :- | :- | :- | :- | :- | :- | :- |
+|3||Information|Gender|Department|Women|Female|
+
+- **The category and attribute mapping spreadsheet was not uploaded**
+
+  This error occurred because the [Amazon mapping spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento) was not uploaded. You need to [complete](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#5-preenchimento-da-planilha-de-mapeamento) the Amazon mapping spreadsheet and [upload](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#6-upload-da-planilha-de-mapeamento) it once it is completed.
+
+- **The value of specification (X) from the spreadsheet does not exist in the VTEX product specification**
+
+  In this error, the attribute in question has not been added to the SKU in the VTEX catalog. You need to [add the attribute](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) and redo the [mapping](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) of the submitted product.
+
+- **The minimum age unit from the mapping spreadsheet is different from the value expected by Amazon.**
+
+  The minimum age unit is different from the value requested by Amazon. Amazon supports years or months as units. Resubmit the [mapping](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) using the values accepted by Amazon.
+
+- **Amazon does not accept the SKU variation from the mapping spreadsheet**
+
+  This error occurs when the **VariationTheme** column of the Amazon mapping spreadsheet contains a value that is not supported by Amazon [Check the supported values](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#5-preenchimento-da-planilha-de-mapeamento) and add a valid value to the mapping spreadsheet.
+
+- **The "SizeMap" attribute value from the mapping spreadsheet is not an attribute/specification value supported by Amazon**
+
+  You added an incorrect value for the SizeMap attribute. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) and check the `VALID VALUES` tab.
+
+- **The "TargetGender" specification value from the spreadsheet is not an attribute/specification value supported by Amazon**
+
+  You added an incorrect value for the TargetGender specification. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) and check the `VALID VALUES` tab.
+
+- **The color and size attributes for this SKU were not found in the mapping spreadsheet**
+
+  You did not add a value for the Color and Size specifications that are mandatory for the category of the product you want to submit. Check the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) to see the values supported by Amazon and add a valid value to the mapping spreadsheet.
+
+- **The SKU does not have a value for the "author" attribute or the mapping spreadsheet does not contain a value for it**
+
+  You did not add the mandatory Author attribute to the product you want to submit. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon), check the `VALID VALUES` tab, and [add a product specification](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) for this attribute.
+
+- **The "Size" attribute value from the mapping spreadsheet is not an attribute/specification value supported by Amazon**
+
+  You did not add the Size specification value correctly. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) and check the `VALID VALUES` tab.
+
+- **The "Color" attribute value from the mapping spreadsheet is not an attribute/specification value supported by Amazon**
+
+  You did not add the Color specification value correctly. To view the values supported by Amazon, open the [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) and check the `VALID VALUES` tab.
+
+## Errors related to missing mandatory attributes on Amazon
+
+- **The SKU does not have a value for the "Color" attribute or the mapping spreadsheet does not contain a value for it**
+
+  The Color attribute is required for the category of the product you are submitting to Amazon and the SKU does not have it, or it was not added to the mapping spreadsheet.
+You need to [add a SKU specification](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) for the Color attribute and/or redo the[mapping](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) for the submitted product.
+
+- **The "TargetGender" product specification is mandatory for integrating this product with Amazon**
+
+  The TargetGender product specification is mandatory for the category of the product you are submitting. Amazon may call it Department or TargetGender depending on the category.
+Add the TargetGender [product specification](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) and redo the [mapping](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).
+
+## Errors related to divergence between VTEX and Amazon catalogs (offer matching)
+
+- **The SKU already exists in the Amazon catalog and is ready for matching between VTEX and Amazon. However, the value of attribute (X) for this SKU on VTEX is different from the value it has on Amazon. It has value (X) on VTEX and value (Y) on Amazon.**
+
+  This error occurs when there are differences between attribute values (details of SKU characteristics) in the Amazon and VTEX catalogs. To fix this error, you need to [edit the attribute value](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) on VTEX to make it match the [attribute value on Amazon](https://drive.google.com/uc?export=download&id=1UkcrfPopMg-cnrSDOF0qt51NRIXgzi0r).  
+
+## Error Missing Attributes  
+
+- **`SKU XXXXX, Missing AttributesX`. SKU XXXXX doesn't match any ASINs. Make sure that all standard product ids (such as UPC, ISBN, EAN, or JAN codes) are correct.**  
+
+This error occurs when a SKU in your feed does not match any ASIN in Amazon's catalog, and the product attribute data is not sufficient to create an ASIN. To resolve it, make sure you are submitting the information correctly according to the values required [Amazon mandatory attribute spreadsheet](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon).
+
+## Errors related to the Amazon token and permissions
+
+- **The token entered in the Amazon configuration form on VTEX expired or does not have permission to access the flow**
+
+  This error occurred because the serial number of the **MWS authorization token** expired. Contact Amazon to fix this problem, and [reconfigure the Amazon integration](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan).
+
+- **Your account does not have permission on Amazon MWS**
+
+  Missing permissions on Amazon MWS. To fix this error, you need to contact Amazon through [Amazon Seller Central](https://sellercentral.amazon.com/ap/signin?clientContext=135-8176388-1570853&openid.return_to=https%3A%2F%2Fsellercentral.amazon.com%2Fgp%2Fhomepage.html&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=sc_na_amazon_v2&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&mons_redirect=sign_in&ssoResponse=eyJ6aXAiOiJERUYiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiQTI1NktXIn0.PRkHwAgdQ7WNNaYmsjVxyF4S14XtyFJ90kRs_cAwB1nM2UeBvdF4yg.waGuLtWTiFMKrHYm.k8i8i6uR4KHIjrZ2OXqDhbyVPnxdmQMrUYpB776Ct68tZmYGoG6TqCYWMLAsBB79dnCwlb7M35CRVUZe-irxeAO-KhYcKXNuYs51r56and5qSqGBmrSz7UAuOLFF2jK0NwSvy61ArqrUZJWupPq_jIoTcgjOEKn6XjMaH-SaQjnnetzoDYsuK5xiSAOo3_NuL_OU75zeq20.I6sO_vS2_iRVpuH7l8xHjg). You can see more information about accounts in the Amazon documentation under [Managing your AWS account](https://docs.aws.amazon.com/accounts/latest/reference/managing-accounts.html). To learn more about the security policy for Amazon seller accounts, read [Security in AWS Account Management](https://docs.aws.amazon.com/accounts/latest/reference/security.html).
+
+## Errors related to the configuration of the Amazon integration
+
+- **The value of the "Shipping type name" field in the configuration of the Amazon integration on VTEX is different from the value it has on Amazon Seller Central**
+
+  This error occurs when there is no equivalence between the value entered for the **Shipping type name** field in the [Configuring the Amazon integration](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan) step on VTEX and the value it has on Amazon Seller Central. Check the Amazon Seller Central documentation to clarify questions and fix the problem.
+
+- **The value of the "SELLER ID" field in the configuration of the Amazon integration on VTEX is different from the value it has on Amazon Seller Central**
+
+  This error occurs when there is no equivalence between the value entered for the **Seller ID** field in the [Configuring the Amazon integration](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan) step on VTEX and the value it has on Amazon Seller Central. Keep in mind that during the integration configuration, the **Seller ID** value you are asked to enter is the one from Amazon.
+[Check the Amazon Seller Central documentation](https://sellercentral.amazon.com/ap/signin?clientContext=135-8176388-1570853&openid.return_to=https%3A%2F%2Fsellercentral.amazon.com%2Fgp%2Fhomepage.html&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=sc_na_amazon_v2&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&mons_redirect=sign_in&ssoResponse=eyJ6aXAiOiJERUYiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiQTI1NktXIn0.btqAgOsEYCzMdO5m9YBtHULpOJ9zDulpquLZakKdx_i4EiYLCA8JRA.6JVG2JtMpz5o1_pj.esabEhqgD_QW-8Kuy32N5O363NO0Mu3-uF-ckJjSyajtUVJ5VIboj4u66Zz8JvOZOXqv8hbNo_8I_xCDO5-gyD_OmF5M674zXjsnuuA4thqW0LsQnN1FJJsomwlM0188J3j15mfmZi2VRscda1HEsvhWR3EI2wG_XRLGmBEnBJ0Q7A3_QCkdkDUwSE6V2u0kW3OqT_HNLw.DzX-HENfRu35E7yMNMkS7g) to clarify questions and fix the problem.
+
+## Errors when submitting the VTEX global category
+
+- **The VTEX global category (X) for this SKU is not configured correctly in the integration**
+
+  This error occurs when the [global category](https://help.vtex.com/en/tutorial/configurando-a-categoria-global--tutorials_188) that was selected in the mapping does not exist on Amazon. Check the product [global category mapping](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) and make sure that the selected category is linked with Amazon.
+
+## Inactive SKU warning
+
+- **The SKU you tried to submit is inactive on VTEX**
+
+  The [SKU](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) is not active on VTEX. Only active SKUs can be integrated. Sometimes this error is generated by old [collections](https://help.vtex.com/en/tutorial/como-deletar-colecao--6C620yHzwsGoS8iaCocAM2) linked to the Amazon trade policy that contain inactive SKUs.
+Check the SKU status on the Admin through the *PRODUCTS > Catalog > Products and SKUs* module and [activate the SKU](https://help.vtex.com/en/tutorial/ativar-skus-em-massa--4uMZATlSc0kEYiewWKSwEY) if needed.
+
diff --git a/docs/tracks/en/promotions-for-specific-scenarios.md b/docs/tracks/en/promotions-for-specific-scenarios.md
index 75dd7075d..26cf5fa58 100644
--- a/docs/tracks/en/promotions-for-specific-scenarios.md
+++ b/docs/tracks/en/promotions-for-specific-scenarios.md
@@ -1,10 +1,10 @@
 ---
 title: 'Promotions for specific scenarios'
 id: jOu9b69mKbrTDfSJYAawy
-status: CHANGED
+status: PUBLISHED
 createdAt: 2020-01-22T13:55:51.326Z
-updatedAt: 2020-11-27T19:40:32.581Z
-publishedAt: 2020-07-29T22:53:59.120Z
+updatedAt: 2023-10-23T17:08:04.859Z
+publishedAt: 2023-10-23T17:08:04.859Z
 firstPublishedAt: 2020-01-22T15:01:20.187Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -29,7 +29,6 @@ In order to meet these scenarios, we offer the following types of promotions:
 The configuration screens for any of the promotions mentioned above follow the same main sections as those explained in the Regular Promotion article. The options in these sections repeat themselves throughout the promotions, with the exception of some specific configurations regarding which conditions to apply the promotion to. Therefore, this article will focus on these specific configurations.
 </div>
 
-
 ### Buy Together - Bundle
 
 The Buy Together promotion is used to grant a discount for two or more products when placed at the same time in the cart.
@@ -38,20 +37,19 @@ The promotion configuration screen offers two SKU lists, which can be added manu
 
 You can define a discount value for each of these lists. If, for example, list 1 has a 10% discount and list 2 has a 5% discount, when the cart has at least one product from each of these lists, a total of 10% discount will be granted on the value of the items from list 1 and a 5% discount will be granted on the value of the items from list 2.
 
-![Compre junto - EN](https://images.ctfassets.net/alneenqid6w5/5BDhbniC14qWJbV6L8e3Kk/c7fdc229614791d92043d350ca5b1319/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_4_.png)
+![Compre junto - EN](//images.ctfassets.net/alneenqid6w5/5BDhbniC14qWJbV6L8e3Kk/c7fdc229614791d92043d350ca5b1319/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_4_.png)
 
 Two examples of this type of promotion would be "Buy a pair of pants and get 10% off when buying a belt" and "Buy a pair of sneakers + a pair of socks and get a 15% off".
 
 To understand the Buy Together promotion in more detail, read our article on <a href="https://help.vtex.com/en/tutorial/buy-together--tutorials_323">Creating a Buy Together Promotion</a>.
 
-
 ### More for Less
 
 The More for Less promotion is used to grant a discount when the customer adds several units of the same product to the cart. A classic example of this promotion would be "Buy 4 pay for 3".
 
 In the configuration of the More for Less promotion, the store must define which collections or SKUs it will apply to. Then, it must choose the minimum number of items in the cart for it to apply and the number of items that get a discount.
 
-![Leva Mais por menos - EN](https://images.ctfassets.net/alneenqid6w5/4JpSv0S2g7BkBpOVMoAKJ5/d50e206d9af27de3cdea385257dd2145/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_5_.png)
+![More less](//images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/823b88ebf22ca83427e4c9c809d31d2e/More_less.png)
 
 For example:
 - For every `3` products, the customer will get `1` `free` product.
@@ -59,7 +57,6 @@ For example:
 
 To understand the More for Less promotion in more detail, read the article <a href="https://help.vtex.com/en/tutorial/creating-more-for-less-promotion--tutorials_325">Creating More for Less promotion</a>.
 
-
 ### Progressive Discount
 
 The Progressive Discount promotion is used when the store wants to offer a percentage discount for a certain quantity of products inserted in the cart.
@@ -70,7 +67,7 @@ When configuring the Progressive Discount promotion, the store must define which
 
 To add more details to the progressive discount promotion, click on the "+" button. A new line will be added, and then you can add a new discount. For example: for the next 2 products, the customer will receive an additional 5% discount. And so on.
 
-![Desconto progressivo - EN](https://images.ctfassets.net/alneenqid6w5/7qZXWf05OIow5vgX5eYulO/808c44fcd80666575444d3d9d6afd560/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_6_.png)
+![Desconto progressivo - EN](//images.ctfassets.net/alneenqid6w5/7qZXWf05OIow5vgX5eYulO/808c44fcd80666575444d3d9d6afd560/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_6_.png)
 
 To understand the Progressive Discount promotion in more detail, read our article on <a href="https://help.vtex.com/en/tutorial/progressive-discount--tutorials_324">How progressive discount works</a>.
 
@@ -80,7 +77,7 @@ The Buy One Get One promotion is used to offer free shipping or a freebie when a
 
 The applied discount (free shipping or freebie) must be defined in the promotion's general data. Then the store must choose the collections or SKUs to which it will apply. Finally, you must define the minimum number of items in the cart for the promotion to apply.
 
-![Compre um e leve outro - EN](https://images.ctfassets.net/alneenqid6w5/L17yG5ZAgaGnCuamDWLwk/141c68c306baa0b2bedec04ee3d0c894/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_7_.png)
+![Compre um e leve outro - EN](//images.ctfassets.net/alneenqid6w5/L17yG5ZAgaGnCuamDWLwk/141c68c306baa0b2bedec04ee3d0c894/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_7_.png)
 
 To understand the Buy One Get One promotion in more detail, read our article on <a href="https://help.vtex.com/en/tutorial/buy-and-win--tutorials_322">How the Buy and Win promotion works</a>.
 
@@ -94,22 +91,22 @@ It is important to note that such restrictions are only <strong>valid for regula
 
 After filling in all the [regular promotion fields](https://help.vtex.com/en/tutorial/regular-promotion--tutorials_327) with the percentage discount, you can __set a maximum number of items affected per cart__ by checking the box for this option, found in the __restrictions__ section.
 
-![Limitação carrinho EN](https://images.ctfassets.net/alneenqid6w5/11eLuOcoCYcYOCrauDEzze/6bafe932057178894773c6ca3f9cf01c/image__13_.png)
+![Limite itens - EN](//images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/98c764ea9fd40bd809d3b7bf55c7a313/Limite_itens_-_EN.png)
 
 By default, the __unlimited__ selection is active, applying the promotion to all items in the cart, as illustrated in the diagram below:  
 
-![Caso ilimitado EN](https://images.ctfassets.net/alneenqid6w5/3H9q2Ywy6uPZmQaff7LgO2/5f69462ef9ecf3d57817ad0fba44a337/Caso_ilimitado_EN.png)
+![Caso ilimitado EN](//images.ctfassets.net/alneenqid6w5/3H9q2Ywy6uPZmQaff7LgO2/5f69462ef9ecf3d57817ad0fba44a337/Caso_ilimitado_EN.png)
 
 To restrict the number of items in the cart, you can choose one from the following options:
 
 - __Items by cart__: this setting restrict a promotion to a predetermined number of items in the cart. Once the limit is reached, the promotion will apply to the rest of the cart. The system uses price as a selection criterion so the items with the lowest prices will be affected first.
 
-![Caso por itens EN](https://images.ctfassets.net/alneenqid6w5/2UUHQC3AZW5g0QzFouGw0u/f414491e89bbd9f08b96914243584be2/Caso_por_itens_EN.png)
+![Caso por itens EN](//images.ctfassets.net/alneenqid6w5/2UUHQC3AZW5g0QzFouGw0u/f414491e89bbd9f08b96914243584be2/Caso_por_itens_EN.png)
 
 - __Items by product__: this setting restricts the promotion to a number of units per product. As in the example below, only two units per product will be eligible for the promotion. The lowest price determines which product items are eligible first.   
 
-![Caso por produto EN](https://images.ctfassets.net/alneenqid6w5/2WN8gDLFhTSjcpx16S3bjb/c4221f0b4901a7df2432d3951deec983/Caso_por_produto_EN.png)
+![Caso por produto EN](//images.ctfassets.net/alneenqid6w5/2WN8gDLFhTSjcpx16S3bjb/c4221f0b4901a7df2432d3951deec983/Caso_por_produto_EN.png)
 
 - __Items by SKU__: this setting restricts the promotion to a predetermined number of units for each SKU in the cart. As in the example below, only two units per SKU will be eligible. As seen in the previous case, the lowest price will determine the eligible items. 
 
-![Caso por SKU EN](https://images.ctfassets.net/alneenqid6w5/huuzHYSvrVxk2THs7zx2P/0a513d9fbd247797218c25089372c450/Caso_por_SKU_EN.png)
+![Caso por SKU EN](//images.ctfassets.net/alneenqid6w5/huuzHYSvrVxk2THs7zx2P/0a513d9fbd247797218c25089372c450/Caso_por_SKU_EN.png)
diff --git a/docs/tracks/en/rappi-integration-overview.md b/docs/tracks/en/rappi-integration-overview.md
new file mode 100644
index 000000000..4004d42bc
--- /dev/null
+++ b/docs/tracks/en/rappi-integration-overview.md
@@ -0,0 +1,18 @@
+---
+title: 'Rappi Integration overview'
+id: 7y40IL3ajiukMRHrX3XmC8
+status: PUBLISHED
+createdAt: 2024-05-31T20:24:26.112Z
+updatedAt: 2024-05-31T20:51:33.604Z
+publishedAt: 2024-05-31T20:51:33.604Z
+firstPublishedAt: 2024-05-31T20:51:33.604Z
+contentType: trackArticle
+productTeam: Channels
+slug: rappi-integration-overview
+locale: en
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugEN: rappi-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/rappi-integration-registration.md b/docs/tracks/en/rappi-integration-registration.md
new file mode 100644
index 000000000..594f78ec3
--- /dev/null
+++ b/docs/tracks/en/rappi-integration-registration.md
@@ -0,0 +1,18 @@
+---
+title: 'Rappi integration registration'
+id: 4Wu9gyd5xCRC0MOb5zG9BK
+status: PUBLISHED
+createdAt: 2024-05-31T20:39:08.338Z
+updatedAt: 2024-05-31T20:51:55.857Z
+publishedAt: 2024-05-31T20:51:55.857Z
+firstPublishedAt: 2024-05-31T20:51:55.857Z
+contentType: trackArticle
+productTeam: Channels
+slug: rappi-integration-registration
+locale: en
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugEN: rappi-integration
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tracks/en/receivables-management.md b/docs/tracks/en/receivables-management.md
index ac30234e4..f8bf7d0a7 100644
--- a/docs/tracks/en/receivables-management.md
+++ b/docs/tracks/en/receivables-management.md
@@ -1,10 +1,10 @@
 ---
 title: 'Receivables management'
 id: 4zO5DEg07BSqHsmlBrCgvr
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T18:01:47.594Z
-updatedAt: 2023-03-14T22:07:36.630Z
-publishedAt: 2023-03-14T22:07:36.630Z
+updatedAt: 2023-10-05T14:14:03.274Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:50:17.208Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/en/register-mercado-livre-integration.md b/docs/tracks/en/register-mercado-livre-integration.md
index cf9dc4a0e..2f550200b 100644
--- a/docs/tracks/en/register-mercado-livre-integration.md
+++ b/docs/tracks/en/register-mercado-livre-integration.md
@@ -3,8 +3,8 @@ title: 'Adding Mercado Livre conector'
 id: 4YvYdgICMosaEgISOYogsi
 status: PUBLISHED
 createdAt: 2018-08-13T12:33:55.818Z
-updatedAt: 2022-02-03T23:29:27.323Z
-publishedAt: 2022-02-03T23:29:27.323Z
+updatedAt: 2023-07-06T20:21:00.334Z
+publishedAt: 2023-07-06T20:21:00.334Z
 firstPublishedAt: 2018-08-13T14:28:06.574Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/registering-the-carrefour-integration.md b/docs/tracks/en/registering-the-carrefour-integration.md
index b7aec2189..3addf3217 100644
--- a/docs/tracks/en/registering-the-carrefour-integration.md
+++ b/docs/tracks/en/registering-the-carrefour-integration.md
@@ -3,8 +3,8 @@ title: 'Configuring register the Carrefour integration'
 id: 2AhqcmRN1mseCsGuGIe6GK
 status: PUBLISHED
 createdAt: 2018-10-08T23:26:55.073Z
-updatedAt: 2022-09-06T22:59:04.246Z
-publishedAt: 2022-09-06T22:59:04.246Z
+updatedAt: 2024-07-02T19:27:42.975Z
+publishedAt: 2024-07-02T19:27:42.975Z
 firstPublishedAt: 2018-10-08T23:51:59.055Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/registering-the-centauro-integration.md b/docs/tracks/en/registering-the-centauro-integration.md
index 170756c2f..eca69c198 100644
--- a/docs/tracks/en/registering-the-centauro-integration.md
+++ b/docs/tracks/en/registering-the-centauro-integration.md
@@ -3,8 +3,8 @@ title: 'Registering the Centauro integration'
 id: 4EqL0hADU1AWvP0gTr4nyq
 status: PUBLISHED
 createdAt: 2020-10-20T18:55:02.489Z
-updatedAt: 2022-01-25T15:55:01.810Z
-publishedAt: 2022-01-25T15:55:01.810Z
+updatedAt: 2024-07-02T19:28:22.448Z
+publishedAt: 2024-07-02T19:28:22.448Z
 firstPublishedAt: 2020-10-20T19:51:24.705Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/registering-the-integration.md b/docs/tracks/en/registering-the-integration.md
index bfdcd66b0..fa4c2ca78 100644
--- a/docs/tracks/en/registering-the-integration.md
+++ b/docs/tracks/en/registering-the-integration.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configuring register the Via integration'
+title: 'Configuring register the Casas Bahia Marketplace integration'
 id: 1okse2MybWk04AQoueu88O
 status: PUBLISHED
 createdAt: 2018-09-24T18:45:21.544Z
-updatedAt: 2022-02-07T21:16:28.792Z
-publishedAt: 2022-02-07T21:16:28.792Z
+updatedAt: 2024-07-02T19:20:54.448Z
+publishedAt: 2024-07-02T19:20:54.448Z
 firstPublishedAt: 2018-09-27T22:12:25.372Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/registering-the-netshoes-integration.md b/docs/tracks/en/registering-the-netshoes-integration.md
index da2aac016..fed9c5e9b 100644
--- a/docs/tracks/en/registering-the-netshoes-integration.md
+++ b/docs/tracks/en/registering-the-netshoes-integration.md
@@ -3,8 +3,8 @@ title: 'Registering the Netshoes integration'
 id: 7o8Vt25LJmAUuMmSWSmWes
 status: PUBLISHED
 createdAt: 2018-09-24T20:27:48.984Z
-updatedAt: 2023-01-05T20:12:16.965Z
-publishedAt: 2023-01-05T20:12:16.965Z
+updatedAt: 2024-07-02T19:19:00.338Z
+publishedAt: 2024-07-02T19:19:00.338Z
 firstPublishedAt: 2018-09-27T15:02:23.717Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/relevance.md b/docs/tracks/en/relevance.md
index 3effd52ea..9928aeda3 100644
--- a/docs/tracks/en/relevance.md
+++ b/docs/tracks/en/relevance.md
@@ -3,8 +3,8 @@ title: 'Relevance'
 id: 1qlObWIib6KqgrfX1FCOXS
 status: PUBLISHED
 createdAt: 2020-04-14T13:35:28.989Z
-updatedAt: 2023-01-23T13:48:19.938Z
-publishedAt: 2023-01-23T13:48:19.938Z
+updatedAt: 2024-01-12T22:16:50.165Z
+publishedAt: 2024-01-12T22:16:50.165Z
 firstPublishedAt: 2020-04-14T23:58:35.468Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,26 +14,26 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
-**Relevance settings** define the order in which products are shown in search results. The order changes according to the criteria and priorities configured for the Search Engine.
+**Relevance rules** define the order in which products are shown in search results in product listing pages (PLP). The order changes according to the criteria and priorities configured for the Search Engine.
 
 Relevance rules are applied to the search results only when the results are sorted by relevance in your store's search. For example, if a customer sorts results by price, relevance settings will not be considered when displaying search results.
 
 You can configure relevance in two ways:
 
-  - __Priority criteria__: it imposes that one or more criteria has a higher priority among the others. In this situation, there are no weights; all products that have this feature will be shown first in the search results.
-  - __Criteria composition__: it is a way to distribute weights for each option, ranging from 0 to 10. Here, there is no order between the criteria; the weights will define the relevance.
+  - __Priority Criteria__: it imposes that one or more criteria has a higher priority among the others. In this situation, there are no weights; all products that have this feature will be shown first in the search results.
+  - __Criteria Composition__: it is a way to distribute weights for each option, ranging from 0 to 10. Here, there is no order between the criteria; the weights will define the relevance.
 
-![regras-relevancia-1-EN](https://images.ctfassets.net/alneenqid6w5/pWaOZBllEtnkrAxc2kEdJ/7ed55448e3b78b749a8d6d0c7d0d803b/Captura_de_Tela_2022-03-25_a__s_15.17.28.png)
+![criterios-en](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/56c8163ed9b449419c17db066dd4506e/criterios-en.png)
 
 The information considered for the relevance is:
 
-- __Discount (from/to)__: it compares the [List Price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#list-price) and the [Base Price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definition) to determine whether the product will be classified as having a discount.
+- __Discount__: it compares the [List Price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#list-price) and the [Base Price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definition) to determine whether the product will be classified as having a discount.
 - __Release date__: this criterion assigns an automatic decreasing value (between 1 and 0) to the product, based on the date it was added to the catalog and considering a 90-day interval. Products added to the catalog today would have the value 1. This value would decrease every day until it becomes 0 after 90 days. This value will be multiplied by the weight you assign to the __Release date__ criterion to compose product relevance.
-- __Best sellers__: number of orders for the product in the last 90 days.
-- __Best sellers by revenue__: the total revenue generated by the product in the last 90 days.
+- __Best-selling__: number of orders for the product in the last 90 days.
+- __Best-selling by revenue__: the total revenue generated by the product in the last 90 days.
 - __Popularity__: the number of clicks the item received in the last 90 days.
 - __Promotion__: it checks for [Campaign Audiences](https://help.vtex.com/en/tutorial/overview-2--tutorials_326?&utm_source=autocomplete#campaign-audiences) or [Promotions](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#) linked to the item to determine whether the product will be classified as a promotion.
-- __Catalog Score__: Catalog sorting tie-breaker based on the value given to products. Learn more about the Score field [in this article](https://help.vtex.com/en/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcae).
+- __Catalog score__: Catalog sorting tie-breaker based on the value given to the **Score** field of products. For this purpose of composing relevance, the higher the score, the greater the weight, i.e. the behavior is descending: products with a higher score are prioritized. Find out more about the field and its behavior in the guide [How does the Score field work?](https://help.vtex.com/en/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcae).
 - __Available matrix variety__: Relevance is based on the percentage of SKUs available per product. In a scenario where _Product A_ has 3 SKUs and 3 of them are available, and _Product B_ has 5 SKUs and 2 of them are available, _Product A_ stands out over _Product B_ because the percentage of SKUs is higher.
 
 The set of weights and criteria distribution generates a score for the product, which determines its position in the search result ranking.
@@ -42,42 +42,54 @@ The set of weights and criteria distribution generates a score for the product,
   <p>IIf you want to use priority criteria, we recommend adding only one criterion in this field. Adding more criteria compromises the ordering or search results, since only the first criterion will be considered.</p>
 </div>
 
-So you can tailor the behavior of the search results to a specific strategy. For example: A fashion store receives new collections frequently. The retailer chooses to prioritize new products instead of products with discounts. To do that, the tool can be configured as follows:
+So you can tailor the behavior of the search results to a specific strategy.
 
-<b>Priority criteria:</b>
-<ul><li>Empty</li></ul>
-<b>Criteria composition:</b>
-<ul><li> <b>Popularity:</b> 7</li>
-    <li> <b>Release date:</b> 10 </li>
-    <li> <b>Best sellers:</b> 6</li>
-    <li> <b>Best sellers by revenue:</b> 6</li>
-    <li> <b>Promotion:</b> 0 </li>
-    <li> <b>Discount:</b> 0 </li>
-    <li> <b>Variation availability (SKU):</b> 10 </li></ul>
+## Example
+
+A fashion store receives new collections frequently. The retailer chooses to prioritize new products instead of products with discounts. To do that, the tool can be configured as follows:
+
+> __Priority criteria:__
+> 
+> - Empty
+> 
+> __Criteria composition:__
+> 
+> - Popularity: 7
+> - Release date: 10
+> - Best-selling: 6
+> - Best-selling by revenue: 6
+> - Promotion: 0
+> - Discount: 0
+> - Available matrix variety: 10
 
 If this retailer wants new products to always have the highest priority, there are two ways to configure the Relevance rules:
 
-<ol>
-    <li> <b>Priority criteria:</b> </li>
-   <ul><li> <b>Release date</b></li></ul>
-     <b>Criteria composition:</b>
-   <ul><li> <b>Popularity:</b> 7</li> 
-   <li> <b>Best sellers:</b> 6</li> 
-   <li> <b>Best sellers by revenue:</b> 6 </li> 
-   <li> <b>Promotion:</b> 0 </li>
-   <li> <b>Discount:</b> 0 </li>
-   <li> <b>Variation availability (SKU):</b> 10 </li></ul><br>
-    <li> <b>Priority criteria:</b> </li>
-    <ul><li>Empty</li></ul>
-    <b>Criteria composition</b>
-    <ul> <li> <b>Popularity:</b> 0 </li>
-    <li> <b>Release date:</b> 10 </li>
-    <li> <b>Best sellers:</b> 0 </li>
-    <li> <b>Best sellers by revenue:</b> 0 </li>
-    <li> <b>Promotion:</b> 0 </li>
-    <li> <b>Discount:</b> 0 </li>
-    <li> <b>Variation availability (SKU):</b> 0 </li></ul>
-</ol>
+> __A:__
+> 
+> __Priority criteria:__
+> - Release date
+> 
+> __Criteria composition:__
+> - Popularity: 7
+> - Best-selling: 6
+> - Best-selling by revenue: 6
+> - Promotion: 0
+> - Discount: 0
+> - Available matrix variety: 10
+
+> __B:__
+> 
+> __Priority criteria:__
+> - Empty
+> 
+> __Criteria composition__
+> - Popularity: 0
+> - Release date: 10
+> - Best-selling: 0
+> - Best-selling by revenue: 0
+> - Promotion: 0
+> - Discount: 0
+> - Available matrix variety: 0
 
 ## Configuring relevance rules
 
@@ -86,7 +98,10 @@ To change relevance settings, follow the steps below.
 1. In the Admin, go to the **Storefront** module.
 2. In **Intelligent Search**, click **Relevance Rules**.
 3. Choose the criterion whose weight you want to change.
-4. Click the <i class="fas fa-minus"></i> or <i class="fas fa-plus"></i> icons to set a number. If you want to change a criterion from **Criteria composition** to **Priority criteria**, click on the <i class="fas fa-grip-vertical"></i> icon and drag it to the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight. 
-![regras-relevancia-EN](https://images.ctfassets.net/alneenqid6w5/iZze1vchSYf9lLFJnfwiT/892c2f6f5aca868508c1a7f0c48a27d8/regras-relevancia-EN.gif)
+4. Click the arrow down <i class="fas fa-chevron-down"></i> or arrow up <i class="fas fa-chevron-up"></i> icons to set a number.
+
+   If you want to change a criterion from **Criteria Composition** to **Priority Criteria**, click on the <i class="fas fa-grip-vertical"></i> icon and drag it to the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight. 
+
+   ![criterios-prioritarios-en](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/326edf2ab5b2c2ee3050a97a98090dd9/criterios-prioritarios-en.gif)
 5. Click `Save` to finish.
 
diff --git a/docs/tracks/en/reports-vtex-intelligent-search.md b/docs/tracks/en/reports-vtex-intelligent-search.md
index 3bfd24c1d..111592978 100644
--- a/docs/tracks/en/reports-vtex-intelligent-search.md
+++ b/docs/tracks/en/reports-vtex-intelligent-search.md
@@ -79,8 +79,8 @@ To export a report in .csv format, you must follow the steps below:
 
 The report (CSV file) you have downloaded contains two tables. The first table contains information about searched terms, as illustrated below. It also shows funnel metrics (from the **ProductsClick** column to the **ProductsSold** column) if you have selected this option.
 
-![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
+![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
 
 The second table shows data for the selected period, as illustrated below. In the __Date__ column, you can see the date of the search.
 
-![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
+![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
diff --git a/docs/tracks/en/sale-confirmed.md b/docs/tracks/en/sale-confirmed.md
index adbd54f0f..f93387258 100644
--- a/docs/tracks/en/sale-confirmed.md
+++ b/docs/tracks/en/sale-confirmed.md
@@ -16,4 +16,4 @@ trackSlugEN: instore-using-the-app
 
 The sales associate can see the __Sale confirmed__ page with the order summary when they finish a sale, or by clicking on a sale in the __Latest sales__ page, which they can access through VTEX Sales App's main menu. In the __Latest sales__ page, they can search for the order by order number or customer name.
 
-![order-placed-en](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/50395e206f1f6eb47f02a8f5a271a8d9/order-placed-en.png)
+![order-placed-en](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/50395e206f1f6eb47f02a8f5a271a8d9/order-placed-en.png)
diff --git a/docs/tracks/en/sales-channel-mapping.md b/docs/tracks/en/sales-channel-mapping.md
index 2d3689318..26b3935c3 100644
--- a/docs/tracks/en/sales-channel-mapping.md
+++ b/docs/tracks/en/sales-channel-mapping.md
@@ -16,10 +16,10 @@ trackSlugEN: lengow-integration
 
 Now that your product feed is ready, it's time to create identifiers for the sales channels you will use in Lengow. These identifiers will then be mapped to the [trade policies](https://help.vtex.com/en/tutorial/configuring-a-marketplace-trade-policy--tutorials_404) that should be used to determine the catalog, pricing and shipping strategy adopted for each sales channel.
 
-To do this, go to *Marketplace > Lengow Integration > Settings* and find the **Sales Channel mapping** section. Clicking on the <img src="https:https://images.ctfassets.net/alneenqid6w5/2KymcHLipd3OUJPvxspzeM/99925b311364a3ccb2e212e66e07ddf4/Screen_Shot_2020-07-01_at_22.51.00.png" style="width: 23px;" /> button adds a new sales channel and clicking on the <img src="https:https://images.ctfassets.net/alneenqid6w5/vJZkSDRUy4etx7d4q48YX/19a559aec5a896cd5f121c4d1ec277f2/Screen_Shot_2020-07-01_at_22.50.20.png" style="width: 23px;" /> button removes it from the sales channel mapping table.
+To do this, go to *Marketplace > Lengow Integration > Settings* and find the **Sales Channel mapping** section. Clicking on the <img src="https://images.ctfassets.net/alneenqid6w5/2KymcHLipd3OUJPvxspzeM/99925b311364a3ccb2e212e66e07ddf4/Screen_Shot_2020-07-01_at_22.51.00.png" style="width: 23px;" /> button adds a new sales channel and clicking on the <img src="https://images.ctfassets.net/alneenqid6w5/vJZkSDRUy4etx7d4q48YX/19a559aec5a896cd5f121c4d1ec277f2/Screen_Shot_2020-07-01_at_22.50.20.png" style="width: 23px;" /> button removes it from the sales channel mapping table.
 
 For each sales channel, select the trade policy that should be used in the left column and fill in the sales channel identifier for Lengow in the right column. We recommend combining Marketplace names and country codes in the sales channel identifier, as this will make it easier to organize your data in Lengow. For example, *Amazon UK* would be identified as `amazon_uk`.
 
-![Lengow - Sales channel mapping](https://images.ctfassets.net/alneenqid6w5/x2fhsfCef0cWzGtVQepzK/487b1b2f601979ce6c97c5822965dd00/Screen_Shot_2020-07-01_at_22.49.58.png)
+![Lengow - Sales channel mapping](//images.ctfassets.net/alneenqid6w5/x2fhsfCef0cWzGtVQepzK/487b1b2f601979ce6c97c5822965dd00/Screen_Shot_2020-07-01_at_22.49.58.png)
 
 <div class="alert alert-warning" role="alert">All <a href="https://help.vtex.com/en/tutorial/configuring-a-marketplace-trade-policy--tutorials_404" target="_blank">trade policies</a> must be created and set up prior to this step. Their names do not need to correspond to the sales channel. If you do not need to adopt different catalog, pricing and shipping strategies for two sales channels, they may share the same trade policy.</div>
diff --git a/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md b/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md
index 8f21dbddc..c4251a74b 100644
--- a/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md
+++ b/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md
@@ -3,8 +3,8 @@ title: 'Scheduled deliveries and delivery capacity'
 id: 5TuyqHRCCwYMaDv4r8rZdo
 status: PUBLISHED
 createdAt: 2022-03-08T18:30:20.114Z
-updatedAt: 2022-03-08T18:37:54.630Z
-publishedAt: 2022-03-08T18:37:54.630Z
+updatedAt: 2024-03-25T20:07:20.150Z
+publishedAt: 2024-03-25T20:07:20.150Z
 firstPublishedAt: 2022-03-08T18:37:54.630Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -18,6 +18,10 @@ A VTEX store can offer scheduled deliveries to its customers. With this option,
 
 To offer [scheduled deliveries](https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi), you must add delivery windows to the [shipping policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140) of the [carrier](https://help.vtex.com/en/tutorial/carries-on-vtex--7u9duMD5UQa2QQwukAWMcE) in question. Once this is done, the periods and days available for this type of delivery will be displayed at your store's checkout. 
 
+<div class="alert alert-warning">
+For <a href="https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a> and <a href="https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Delivery capacity</a> to perform correctly, you must follow the rules below:<p><ul><li>The result from {<a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {shipping policy ID} cannot exceed 60 characters.</li><li>Do not use spaces in <a href="https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">shipping policy IDs</a>.</li></ul></p>
+</div>
+
 Please note that the availability of scheduled deliveries depends on the services offered by the contracted carrier to your store, as defined in the shipping policy. You can track the availability of delivery windows and the number of items/orders that can still be placed in each delivery window on the [Delivery capacity](https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) page.
 
 ### Configuration
diff --git a/docs/tracks/en/search-settings.md b/docs/tracks/en/search-settings.md
index 012c6dfaa..2c271cb56 100644
--- a/docs/tracks/en/search-settings.md
+++ b/docs/tracks/en/search-settings.md
@@ -3,8 +3,8 @@ title: 'Search configuration'
 id: 5t75L6lYNwix93l41s1Yrx
 status: PUBLISHED
 createdAt: 2020-08-17T19:50:20.729Z
-updatedAt: 2023-03-30T19:37:35.404Z
-publishedAt: 2023-03-30T19:37:35.404Z
+updatedAt: 2024-04-25T17:06:18.124Z
+publishedAt: 2024-04-25T17:06:18.124Z
 firstPublishedAt: 2020-09-28T20:51:58.291Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,25 +14,38 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
-Search configuration comprises all VTEX Intelligent Search global settings. It consists of two sections: [General Settings](#general-settings) and [Facet Settings](#facet-settings).
+The **Search Settings** page comprises the VTEX Intelligent Search general settings. To access it in the VTEX Admin, go to **Store Settings > Intelligent Search > Search Settings**. The page is divided into two sections: [General Settings](#general-settings) and [Facet Settings](#facet-settings).
 
 ## General settings
-These are the settings that handle the totality of VTEX Intelligent Search. This feature is composed by the following option:
-Use SKU specifications to display individual products in search results: defines which specifications will be used to separate SKUs in search results. 
 
-Suppose you have a product available in two different colors: blue and red. If you select the attribute "color" in this field, the search result will return two different products (one blue and one red) instead of only one product.
-To configure this field, click on the drop-down arrow and select the specifications you want to add.
+The general settings display the following options related to[ product and SKU specifications](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP):
 
-For more information, read [this article](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE#).
+* **Use SKU specifications to display individual products in search results**: Defines which specifications will sort the SKUs in the search results.
 
-![General configuration Intelligent Search V4](https://images.ctfassets.net/alneenqid6w5/41W9W07VVWur0rAxScJG9e/936118514a133901d11e4e52ef1fe7b7/general_settings_right_2.png)
+    Suppose you have a product available in two colors: blue and red. If you select the attribute "color" in this field, the search result will return two products (one blue and one red) instead of only one product.
+
+    To configure this field, click the dropdown arrow and select the specifications you want to add.
+
+    Check the guide [Detaching SKUs by specification](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE) for more details on this configuration behavior.
+
+* **Searchable specifications:** Determines which product specifications can be searched by the search engine.
+
+    For example, if a shirt doesn't have a color in the product name or SKU, by default, Intelligent Search won't identify this attribute in the search results for "blue shirt", returning shirts of different colors. However, if the color specification is set as searchable, the search can return blue shirts in the top results.
 
 ## Facet settings
-Using the intelligent search on Admin V4, you are able to edit your search’s facet. The available configurations are:
 
-- **Facet order:** order in which the filters will be displayed in the store. If you do not have any facet selected, the default order will be alphabetical. To add a facet, click on `Add`, select a filter and click on `Save`. You can change the sorting by dragging the three stacked lines icon. You can also click the trash button <i class="fa-solid fa-trash-can"></i> to delete the facet.
-- **Hide facets:** option that allows you to hide certain filters in the store. To hide a filter, click on the dropdown menu and select it.
+The facet settings have settings related to the[ filters](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) displayed to your customers during the search:
+
+![Facet configurations](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
+
+* **Facet order:** Order in which the facets will be displayed in the store. If no facet is selected, the default order is alphabetical.
+
+    To add a facet, click `Add`, select the facet, and click `Save` to confirm.
+
+    You can change the order by dragging the three-bar icon <i class="fas fa-grip-vertical"></i> on each facet to the desired position.
+
+    To delete a facet, click the trash can icon <i class="fas fa-trash-alt"></i>.
 
-![Facet configurations](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
+* **Hide facets:** Option that allows you to hide certain facets in the store. To hide a facet, click the dropdown menu and select the facet you want to hide.
 
-For more information, read [this article](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) about **Filters**.
+    To redisplay a facet, click the X next to its name. If you want to show all the previously hidden facets again, click the X on the right side of the field.
diff --git a/docs/tracks/en/seeing-order-details.md b/docs/tracks/en/seeing-order-details.md
index fdbdc2d15..6cd18d360 100644
--- a/docs/tracks/en/seeing-order-details.md
+++ b/docs/tracks/en/seeing-order-details.md
@@ -3,8 +3,8 @@ title: 'Seeing order details'
 id: 204AjAQseJe8RLUi8GAhiC
 status: PUBLISHED
 createdAt: 2019-11-14T15:12:10.952Z
-updatedAt: 2023-03-29T15:17:48.189Z
-publishedAt: 2023-03-29T15:17:48.189Z
+updatedAt: 2023-11-08T14:56:01.508Z
+publishedAt: 2023-11-08T14:56:01.508Z
 firstPublishedAt: 2019-11-18T12:20:18.851Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -20,11 +20,18 @@ In the default view of this screen, all store orders are listed starting from th
 
 In addition, the search offers a very flexible filter, which we will explain in detail in the [next article](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/3cjk655ZzDGICH4rVfgu7O).
 
-To further explore the order list, see the [Order List Overview article](https://help.vtex.com/en/tutorial/orders-list--tutorials_200)
+To further explore the order list, see the [Order List Overview article](https://help.vtex.com/en/tutorial/orders-list--tutorials_200).
+
+Besides searching for orders in **Orders > All Orders**, you can search for orders from any page in the VTEX Admin using the global search bar at the top bar. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
 
 ## Viewing the Details of an Order
 
-Clicking on an order takes you to the __order details__ screen, where you can review a range of order information and perform some actions, such as:
+Clicking on an order takes you to the [order details](https://help.vtex.com/en/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl) screen, where you can review a range of order information and perform some actions, such as:
 - Resend the last email to the customer.
 - Manually cancel the order.
 - Invoice the order items.
diff --git a/docs/tracks/en/sending-product-data-to-dafiti.md b/docs/tracks/en/sending-product-data-to-dafiti.md
index a69cc759e..e1c772f02 100644
--- a/docs/tracks/en/sending-product-data-to-dafiti.md
+++ b/docs/tracks/en/sending-product-data-to-dafiti.md
@@ -3,8 +3,8 @@ title: 'Sending product data to Dafiti'
 id: 3b8BZfB1BC8G8SCe0ao46m
 status: PUBLISHED
 createdAt: 2018-09-27T18:14:09.967Z
-updatedAt: 2022-10-14T12:56:30.575Z
-publishedAt: 2022-10-14T12:56:30.575Z
+updatedAt: 2023-08-24T20:14:58.159Z
+publishedAt: 2023-08-24T20:14:58.159Z
 firstPublishedAt: 2018-09-27T21:44:56.294Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/sending-products-to-amazon.md b/docs/tracks/en/sending-products-to-amazon.md
index ce8d16cdd..e6250cc35 100644
--- a/docs/tracks/en/sending-products-to-amazon.md
+++ b/docs/tracks/en/sending-products-to-amazon.md
@@ -1,10 +1,10 @@
 ---
-title: 'Sending products to Amazon'
+title: 'Mapping and sending product categories to Amazon'
 id: 5xklf2wSdeztQh4iy5kJvD
 status: PUBLISHED
 createdAt: 2019-02-28T23:12:40.204Z
-updatedAt: 2023-03-16T19:46:44.241Z
-publishedAt: 2023-03-16T19:46:44.241Z
+updatedAt: 2023-10-18T19:47:04.829Z
+publishedAt: 2023-10-18T19:47:04.829Z
 firstPublishedAt: 2019-02-28T23:13:35.624Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,7 +14,54 @@ trackId: 6sgd4Pagy3wNsWKBvmIFrP
 trackSlugEN: amazon-integration
 ---
 
-Once you have configured the initial integration settings, you can send products to the Amazon catalog. To speed up the process of cataloging products on Amazon and making them available for sale, you will need to map the characteristics of the products in your VTEX store to the characteristics of the same products in your Amazon store. To perform the mapping, you must:
+Once you have configured the initial integration settings, you can send the products to the Amazon catalog. To speed up the process of cataloging products on Amazon, and making them available for sale, you will need to map the characteristics of the products in your VTEX store to the characteristics of the same products in your Amazon store.  
+
+To send your products to Amazon, you need to map the product [categories](https://help.vtex.com/en/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) and [attributes](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).  
+
+<div class="alert alert-info">
+Your products need to have the <a href="https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">warehouse</a> and <a href="https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">price</a> configured before sending them to Amazon.  </div>
+
+## Mapping categories  
+
+The mapping process can be done through the [VTEX Admin](#mapping-through-the-vtex-admin), or a [spreadsheet](#mapping-via-spreadsheet). See below how to do it in each case. 
+
+<div class="alert alert-danger">
+When mapping a category using the VTEX Admin, the category mapping previously done via a spreadsheet will be overwritten and cannot be recovered.
+</div>  
+
+### Mapping through the VTEX Admin (BETA)  
+
+To access the Amazon mapping page, go to **Marketplace > Marketplaces and Integrations > Amazon > Perform Mapping.**
+
+On the Amazon mapping page, you will see a list of your VTEX store categories. The category mapping allows you to match your categories to the Amazon ones. This way, the products you send will be displayed in the equivalent category in the marketplace.  
+
+On the mapping page, use the search bar to search for the category name. In addition, the **Store Categories** section displays a list of all categories in your store.  
+
+This list includes icons to indicate the status of your mapping:
+
+| **Icon** | **Status**| **Description**|
+|:---:|:---:|:---:|
+|![mapeado mapper](//images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/94a47adb24232c9a88da68e951edfad4/mapeado_mapper.jpg)| **Mapped** |Indicates that the category mapping was completed.|
+|![mapeamentoincompleto mapper](//images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/5c707e0427e064603b127ecffba75970/mapeamentoincompleto_mapper.jpg) | **Incomplete mapping** |The category is partially mapped.The required attributes, indicated by an asterisk, need to be added for completing the mapping. |
+|![erromapeamento mapper](//images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/f84c40b49563dacdf2f96c5ac20ad65e/erromapeamento_mapper.jpg) | **Error in mapping** |The mapping error occurs when the marketplace removes or changes the product category. To solve this, simply remap the category. |
+|![incompleto mapper](//images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/5c2bb3c9fd5f5d131b9a2e153d7857d0/incompleto_mapper.jpg) | **Not mapped** | Indicates that the category was not mapped. |  
+
+To map a category, follow these steps:  
+
+1. In the Admin, go to **Marketplace > Marketplaces and Integrations > Amazon > Perform Mapping.**  
+2. Select the category you want to map.
+3. Select the corresponding category on Amazon for the product you want to send.
+4. Match the attributes in the side window, as shown in the image below: ![Amazon Mapper Attributes](//downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/da4ea7365efc744b036e55305feaea6f/mapper_amazon_atributos.gif)  
+5. Click the `Save Changes` button.  
+
+<div class="alert alert-danger">
+Fields with an * asterisks are required.
+<br>Completing an attribute can trigger new required fields that only become visible under <b>Marketplace > Connections > Products</b> after the mapping has been saved.</br>
+</div>
+
+### Mapping via spreadsheet  
+
+To carry out the mapping via spreadsheet, follow the steps below:
 
 1. [Download the Amazon general category template](#1-amazon-general-categories-template)
 2. [Download the Amazon mandatory attributes template](#2-amazon-attributes-template)
@@ -23,21 +70,21 @@ Once you have configured the initial integration settings, you can send products
 5. [Fill out the mapping template](#5-filling-in-the-mapping-spreadsheet)
 6. [Upload the completed mapping template](##6-uploading-the-mapping-template)
 
-## 1. Amazon general categories template
+#### 1. Amazon general categories template
 
 Amazon uses the [global categories](https://help.vtex.com/en/tutorial/configurando-a-categoria-global--tutorials_188) registered on the VTEX platform to map products. Therefore, it is important that the equivalence between the global categories in VTEX and the categories in Amazon is done correctly.
 
 To learn about the categories accepted by Amazon, please download the [Amazon general categories template.xlsx.](https://drive.google.com/uc?export=download&id=1GC5Guic4k_8C2ZnEGQUoDqT2cdJzp-Ti) This template will be used for consultation purposes only.
 
-## 2. Amazon attributes template
+#### 2. Amazon attributes template
 
 Amazon has reference attributes for certain product features that must be considered when mapping attributes.
 
-To know which attributes are accepted by Amazon according to each column of the mapping template, please download the [Amazon attributes template.xlsx.](https://drive.google.com/uc?export=download&id=1UkcrfPopMg-cnrSDOF0qt51NRIXgzi0r) This template will be used for consultation purposes only.
+To know which attributes are accepted by Amazon according to each column of the mapping template, please download the [Amazon required attributes template.xlsx.](https://drive.google.com/uc?export=download&id=1UkcrfPopMg-cnrSDOF0qt51NRIXgzi0r) This template will be used for consultation purposes only.
 
 In this template, each tab corresponds to a global subcategory on Amazon. When you click on a tab, the template displays the subcategories present within the selected global category.
 
-## 3. Pre-configuring the catalog
+#### 3. Pre-configuring the catalog
 
 Before mapping the products in your store, you must configure the following [fields for the product](https://help.vtex.com/es/tutorial/criando-um-campo-de-produto--tutorials_106) you want to send to Amazon:
 
@@ -56,22 +103,21 @@ When configuring a global category on the VTEX platform, please consider the Ama
 
 To configure a global category in the VTEX environment according to the global categories on Amazon, please follow the steps below:
 
-1. In the [Amazon attributes template](#1-amazon-general-categories-template) find the category that will be used for your products.
-2. In the [Amazon general categories template](#2-amazon-attributes-template) filter column I - **Cat-Amazon-General** and select the desired category.
-3. In the [Amazon general categories template](#2-amazon-attributes-template), identify which category tree will apply to VTEX by viewing columns B, C, D and/or E.
-4. In VTEX Admin, go to the *CATALOG*, module and select the **Products and SKUs** tab. 
+1. In the [Amazon required attributes template](#1-amazon-general-categories-template) find the category that will be used for your products.
+2. In the [Amazon global categories template](#2-amazon-attributes-template) filter column I - **Cat-Amazon-General** and select the desired category.
+3. In the [Amazon global categories template](#2-amazon-attributes-template), identify which category tree will apply to VTEX by viewing columns B, C, D and/or E.
+4. In VTEX Admin, go to the **Catalog**, module and select the **Products and SKU Management** tab. 
 5. Find the product by searching for the desired category in the search field.
-6. Click on `Edit`.
+6. Click on `Edit Product`.
 7. On the product page, find the `VTEX global category` field.
 8. Fill out the [VTEX global category](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global) field with the name of the category you found in step 3.
 9. Click on `Save`.
 
-#### Example of how to use the templates for consultation 
-
-In the Amazon attributes template, we will use the **Health** category as an example:
+**Example of a spreadsheet query**
+In the Amazon required attributes template, we will use the **Health** category as an example:  
 ![categoriageral01](//images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
 
-In the Amazon general categories template, filter column I (Cat-Amazon-General) by clicking on **Filter > Health > OK**.
+In the Amazon general categories template, filter column "I" Cat-Amazon-General by clicking on **Filter > Health > OK**.
 ![categoriageral02](//images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
 
 Following the previous example, filter columns B, C, and D in the **Health & Beauty > Personal care > Massage & Relaxation** tree.
@@ -85,7 +131,7 @@ Because Amazon's catalog is unique, Amazon requires that products shipped have a
 
 #### EAN exemption
 
-However, there are situations in which [Amazon exempts the retailer from entering the EAN](https://sellercentral.amazon.com.br/gp/help/200426310). In this case, the exemption must be configured in both Amazon and VTEX. 
+However, there are situations in which [Amazon exempts the merchant from sending the EAN](https://sellercentral.amazon.com.br/gp/help/200426310). In this case, the exemption must be configured in both Amazon and VTEX. 
 
 If Amazon has already granted EAN exemption for your store, please [submit a support ticket](https://support.vtex.com/hc/en-us) with the subject "Amazon - EAN exemption" to request VTEX to do the same. To obtain the EAN exemption, the integration must already be configured before you make the request via support ticket.
 
@@ -114,13 +160,13 @@ Whether you are selling a brand's products or your own branded products, Amazon
 
 If you want to sell a product that is associated with another owner (creating a new ASIN), it is important to pay attention to the [approvals](https://sellercentral.amazon.com/gp/help/help.html/?itemID=G201844590&ref_=xx_G201844590_a_r0_cont_sgsearch).
 
-## 4. Mapping spreadsheet
+#### 4. Mapping spreadsheet
 
 In this step, you will need to categorize product variations and attributes and send them to the marketplace. This information is sent using the mapping template, which establishes the equivalence between the categories, variations and attributes of your store and the standards adopted by Amazon.
 
 Download the [Amazon mapping template.xlsx](https://assets.ctfassets.net/alneenqid6w5/4mNcXF4yS3160xUGgCZVQC/caf8cfc88b316bc9878000264e16e30b/Planilha_modelo.xlsx) and fill it out. This file will be submitted to Amazon afterwards.
 
-## 5. Filling in the mapping spreadsheet
+#### 5. Filling in the mapping spreadsheet
 
 The template contains the following columns:
 
@@ -157,7 +203,7 @@ Follow the steps below for each product:
 Depending on the category, the <b>VariationTheme</b> values may be similar. There are categories in which <b>VariationTheme</b> can be: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, while there are other categories in which it can be: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. The difference is in the order. In <i>SizeColor</i>, the checkboxes on the product page will be sorted by size and color, while in <i>ColorSize</I> they will be sorted by color and size. Pay attention to the values valid for each category that will be mapped. 
 </div>
 
-### Example
+#### Example
 
 | CategoryID | VariationTheme | Type | VTEXSpecification | AmazonSpecification | VTEXValue | AmazonValue |
 | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
@@ -165,7 +211,7 @@ Depending on the category, the <b>VariationTheme</b> values may be similar. Ther
 | 212 | SizeColor | Variation | Size | Size | M | M |
 | 212 | SizeColor | Variation | Size | Size | L | L |
 
-## 6. Uploading the mapping template
+#### 6. Uploading the mapping template
 
 After filling in the spreadsheet, go to Integrations in the Admin menu:
 
@@ -178,18 +224,3 @@ After filling in the spreadsheet, go to Integrations in the Admin menu:
 
 If no error has occurred during the process, the products will be sent to Amazon with their respective attributes.  
 
-## 7. Automatic matching
-
-Whenever a [SKU](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) with a registered [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) is sent to Amazon, the marketplace performs a matching process, combining offers for the same product using its EAN.  
-
-The EAN added on VTEX is used to match the corresponding [ASIN](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (Amazon Standard Identification Number) on Amazon. This matching happens automatically; however, it may not be done correctly.  
-
-<div class= "alert alert-info">
-We recommend that the seller review all products in the `Processed with warning` status. Products that do not have a matching EAN and ASIN need to be resent.  
-</div>
-
-Follow the steps below to filter products that were not processed correctly:  
-
-1. In the VTEX Admin, go to __Marketplace > Integrations > Products__.  
-2. Filter the products with the Affiliate field filled in with Amazon and the Status field with the value Warning. You will see the products that have not been processed with the matching EAN and ASIN and will be able to resend them.  
-
diff --git a/docs/tracks/en/sending-products-to-facebook.md b/docs/tracks/en/sending-products-to-facebook.md
index 0b2d5a441..c15644f84 100644
--- a/docs/tracks/en/sending-products-to-facebook.md
+++ b/docs/tracks/en/sending-products-to-facebook.md
@@ -3,8 +3,8 @@ title: 'Sending products to Facebook'
 id: 41qzoa7TWIYTyIhABHdgzI
 status: PUBLISHED
 createdAt: 2021-02-08T19:45:07.202Z
-updatedAt: 2021-07-09T22:04:10.786Z
-publishedAt: 2021-07-09T22:04:10.786Z
+updatedAt: 2024-01-22T15:03:37.861Z
+publishedAt: 2024-01-22T15:03:37.861Z
 firstPublishedAt: 2021-02-08T20:10:14.152Z
 contentType: trackArticle
 productTeam: Channels
@@ -89,10 +89,10 @@ Here is an example of a completed spreadsheet:
 The third and final step to complete the mapping is to upload the completed spreadsheet. To do this, follow the steps below:
 
 1. Access the Admin.
-2. In the _MARKETPLACE_ module, click on `Integrations`.
-3. Click on `Settings`.
-4. In the Facebook card, click on <i class="fas fa-cog"></i>
-5. Choose the Upload Mapping option.
+2. In the Marketplace module, click Marketplace and Integrations.
+4. Search for Facebook in the search bar.
+5. Click `Edit`
+6. Choose the `Category Mapping` option.
 6. Click on `Choose a File`.
 7. Select the completed mapping spreadsheet.
 8. Click on `Upload File`.
diff --git a/docs/tracks/en/sending-products-to-via.md b/docs/tracks/en/sending-products-to-via.md
index fa41d91be..a462a1593 100644
--- a/docs/tracks/en/sending-products-to-via.md
+++ b/docs/tracks/en/sending-products-to-via.md
@@ -1,10 +1,10 @@
 ---
-title: 'Sending products to Via Marketplace'
+title: 'Sending products to Casas Bahia Marketplace'
 id: 5QVZFYNfuRIQKdq34MbTxz
 status: PUBLISHED
 createdAt: 2020-03-30T18:51:30.236Z
-updatedAt: 2022-01-24T19:39:58.658Z
-publishedAt: 2022-01-24T19:39:58.658Z
+updatedAt: 2024-07-26T19:30:35.060Z
+publishedAt: 2024-07-26T19:30:35.060Z
 firstPublishedAt: 2020-03-30T23:08:05.849Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md b/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md
index c1fb74576..888045ff1 100644
--- a/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md
+++ b/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md
@@ -26,31 +26,31 @@ You can find download links at: [http://instore.vtex.com/#download](http://insto
 
 When opening inStore for the first time, you will need to enter the VTEX account where you want to configure it and click on __Confirm__.
 
-![01 inStore selecione conta](https://images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
+![01 inStore selecione conta](//images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
 
 If inStore is not configured on this account, you will be redirected to the VTEX App Store where you will need to log in with your admin account in VTEX.
 
 After login, you will be able to install inStore in your account.
 
-![02 inStore instalar](https://images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
+![02 inStore instalar](//images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
 
 A setup form will be displayed, the first step being the address information.
 
-![03 inStore endereco](https://images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
+![03 inStore endereco](//images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
 
 Then you must set an email and password to be used as a vendor login.
 
 > __IMPORTANT__: this email __CAN'T__ be the same as the one used on VTEX platform, because your admin email has permissions that a salesperson should not have, so it's necessary to use some other email without privileges on the platform.
 
-![04 inStore registre vendedor](https://images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
+![04 inStore registre vendedor](//images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
 
 Once you've set up the seller and confirmed the activation code received via email, you can set up payment methods.
 
-![05 inStore configure pagamento](https://images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
+![05 inStore configure pagamento](//images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
 
 If you do not already have an agreement with an acquirer, you can only keep the __Cash__ option active. After clicking on __Confirm__, you should see the success screen.
 
-![06 inStore sucesso](https://images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
+![06 inStore sucesso](//images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
 
 Now just go back to the app, log in with the vendor credentials and start selling!
 
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
index 35ff11781..9a16818d3 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
@@ -20,11 +20,11 @@ One of the functions of sales policies is to make a differentiation of __catalog
 
 A single sales policy can be shared by more than one marketplace or between the main store and the marketplace. To do this, simply use the same sales policy ID in the [settings](/en/tutorial/integrating-with-marketplace). By doing so, the same catalog and the same logistics will be used for the stores or channels that are configured with the same sales policy.
 
-![carrefour.en2](https://images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/6838742905e194a219bc848592b79906/carrefour.en2.png)
+![carrefour.en2](//images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/6838742905e194a219bc848592b79906/carrefour.en2.png)
 
 In other words, if there is no need to define a specific catalog or logistics type for different sales channels, then you will not need to use separate sales policies. Simply associate your integration with the marketplace to the sales policy ID that already exists.
 
-![carrefour.en3](https://images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/bd7e0ec03f86e280299e18b83ba1ecbf/carrefour.en3.png)
+![carrefour.en3](//images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/bd7e0ec03f86e280299e18b83ba1ecbf/carrefour.en3.png)
 
 So before setting up a new sales policy in your store, make sure you need to do that. If the answer is yes, follow the guidelines in the article [How to hire a new sales policy](https://help.vtex.com/en/faq/how-to-configure-a-new-trade-policy--frequentlyAskedQuestions_700) before moving on to the next configuration step. If your sales policy already meets the conditions you need for integration with the marketplace, follow the instructions below.
 
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy-skyhub-b2w.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
index 0c7284745..ce65a1d22 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
@@ -3,8 +3,8 @@ title: 'Setting up a marketplace trade policy'
 id: 4rbhQuuWlUvOp4oOeBlbiC
 status: PUBLISHED
 createdAt: 2021-02-22T19:46:30.515Z
-updatedAt: 2022-12-08T20:34:38.911Z
-publishedAt: 2022-12-08T20:34:38.911Z
+updatedAt: 2023-10-19T14:10:13.534Z
+publishedAt: 2023-10-19T14:10:13.534Z
 firstPublishedAt: 2021-02-22T21:40:49.337Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy-viavarejo.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy-viavarejo.md
index 4f2e314f5..dc9df418c 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy-viavarejo.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy-viavarejo.md
@@ -3,8 +3,8 @@ title: 'Setting up a trade policy'
 id: D63aTOOoQXd6NYq1f5rhc
 status: PUBLISHED
 createdAt: 2021-02-22T16:52:54.100Z
-updatedAt: 2022-12-08T20:34:07.143Z
-publishedAt: 2022-12-08T20:34:07.143Z
+updatedAt: 2023-11-30T21:09:43.958Z
+publishedAt: 2023-11-30T21:09:43.958Z
 firstPublishedAt: 2021-02-22T21:38:33.617Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
index ff0878c7d..0a411cfe6 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
@@ -20,11 +20,11 @@ One of the functions of sales policies is to make a differentiation of __catalog
 
 A single sales policy can be shared by more than one marketplace or between the main store and the marketplace. To do this, simply use the same sales policy ID in the [settings](/en/tutorial/integrating-with-marketplace). By doing so, the same catalog and the same logistics will be used for the stores or channels that are configured with the same sales policy.
 
-![carrefour.en2](https://images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/ac520788fc2a7f4c7455c21fb9eb7a06/carrefour.en2.png)
+![carrefour.en2](//images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/ac520788fc2a7f4c7455c21fb9eb7a06/carrefour.en2.png)
 
 In other words, if there is no need to define a specific catalog or logistics type for different sales channels, then you will not need to use separate sales policies. Simply associate your integration with the marketplace to the sales policy ID that already exists.
 
-![carrefour.en3](https://images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/7c11964cda1bfc0eab26adec48027cc4/carrefour.en3.png)
+![carrefour.en3](//images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/7c11964cda1bfc0eab26adec48027cc4/carrefour.en3.png)
 
 So before setting up a new sales policy in your store, make sure you need to do that. If the answer is yes, follow the guidelines in the article [How to hire a new sales policy](https://help.vtex.com/en/faq/how-to-configure-a-new-trade-policy--frequentlyAskedQuestions_700) before moving on to the next configuration step. If your sales policy already meets the conditions you need for integration with the marketplace, follow the instructions below.
 
diff --git a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
index e7730f273..7e873cdde 100644
--- a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -16,7 +16,7 @@ trackSlugEN:
 
 This article aims to explain how the inStore app configures AppLinking for `payment` and `payment-reversal` actions with the acquirers' apps.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Setting fields
 
diff --git a/docs/tracks/en/setting-up-credit-direct-sale.md b/docs/tracks/en/setting-up-credit-direct-sale.md
index 29cc16ff9..6539daa1f 100644
--- a/docs/tracks/en/setting-up-credit-direct-sale.md
+++ b/docs/tracks/en/setting-up-credit-direct-sale.md
@@ -3,8 +3,8 @@ title: 'Setting up Credit Direct Sale'
 id: 5rSTgGeCqEN7c9LmFbfqA
 status: PUBLISHED
 createdAt: 2021-09-27T20:09:51.763Z
-updatedAt: 2023-05-31T14:45:21.350Z
-publishedAt: 2023-05-31T14:45:21.350Z
+updatedAt: 2023-07-19T19:35:38.275Z
+publishedAt: 2023-07-19T19:35:38.275Z
 firstPublishedAt: 2021-09-27T20:35:59.233Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,7 +14,7 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugEN: instore-payments
 ---
 
-If you wish to receive credit card payments on inStore, follow the steps below.
+If you wish to receive credit card payments on VTEX Sales App, follow the steps below.
 
 1. In the VTEX Admin, go to **Store Settings** > **Settings** > **Payment Conditions**, or type **Settings** in the search bar at the top of the page.
 2. Click the `+` button.
@@ -25,5 +25,5 @@ If you wish to receive credit card payments on inStore, follow the steps below.
 7. Click `Save`.
 
 <div class="alert-info">
-<p>In addition to the settings above, you must follow the <strong><a href="https://help.vtex.com/en/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1">Define payment methods displayed in inStore</a></strong> guide so that the payment options are displayed correctly in the app.</p>
+<p>In addition to the settings above, you must follow the <strong><a href="https://help.vtex.com/en/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1">Define payment methods displayed in VTEX Sales App</a></strong> guide so that the payment options are displayed correctly in the app.</p>
 </div>
diff --git a/docs/tracks/en/setting-up-payment-methods-for-instore.md b/docs/tracks/en/setting-up-payment-methods-for-instore.md
index 009e64b22..b43d799e7 100644
--- a/docs/tracks/en/setting-up-payment-methods-for-instore.md
+++ b/docs/tracks/en/setting-up-payment-methods-for-instore.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up payment methods for inStore'
+title: 'Setting up payment methods for VTEX Sales App'
 id: 2liigRors32hzqBNs2M1Oa
 status: PUBLISHED
 createdAt: 2020-06-28T14:54:46.020Z
-updatedAt: 2023-05-31T14:44:58.176Z
-publishedAt: 2023-05-31T14:44:58.176Z
+updatedAt: 2023-08-28T11:55:43.015Z
+publishedAt: 2023-08-28T11:55:43.015Z
 firstPublishedAt: 2020-06-28T15:17:02.889Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,6 +14,6 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugEN: instore-payments
 ---
 
-The inStore [configuration](https://help.vtex.com/en/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc) allows you to receive credit and debit card payments.
+The VTEX Sales App [configuration](https://help.vtex.com/en/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc) allows you to receive credit and debit card payments.
 
 First you must enable the acquirer in the __Payments__ settings, then you can set up the desired payment terms. Click on `NEXT` to read the articles explaining all the configuration steps.
diff --git a/docs/tracks/en/setting-up-the-app.md b/docs/tracks/en/setting-up-the-app.md
index ede8ea024..bcaead8f0 100644
--- a/docs/tracks/en/setting-up-the-app.md
+++ b/docs/tracks/en/setting-up-the-app.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up Customer Credit'
+title: 'Configuring Customer Credit'
 id: 21ok0GBwmcIeaY2IukYMOg
 status: PUBLISHED
 createdAt: 2018-11-07T17:11:22.823Z
-updatedAt: 2022-01-07T13:30:23.058Z
-publishedAt: 2022-01-07T13:30:23.058Z
+updatedAt: 2024-02-08T18:03:14.738Z
+publishedAt: 2024-02-08T18:03:14.738Z
 firstPublishedAt: 2018-11-07T17:23:16.520Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,95 +14,101 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugEN: customer-credit-getting-started
 ---
 
-## First acess settings
+After installing the Customer Credit app, you must perform the following settings:
 
-Let's configure the Customer Credit app.
+- [First access](#first-access)
+- [App](#app-settings) 
+- [Payment conditions](#payment-conditions)
 
-The first step is to access its settings page in the Admin.
+## First access
 
-You will see three commands inside the “Pending” box: 
+To perform the initial Customer Credit settings, follow the steps below:
 
-1. __Activate transactional emails in Message Center__: installs transactional email templates related to Customer Credit in Message Center. To activate it, click on the “Activate” button;
-2. __Configure checkout payment conditions__: defines rules for installments and payment terms. To activate it, click on the “Configure” button;
-3. __Undefined affiliation’s appKey and appToken__: Customer Credit as a payment method. To activate it, click on the “Authenticate” button. You will be redirected to the “Gateway Affiliations” page, where you must fill in the empty fields with your Key and Token for that store. For more details, see our [article on how to create appKeys and appTokens](https://help.vtex.com/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2 "article on how to create appKeys and appTokens.").
+1. In the VTEX Admin, go to __Apps > Customer Credit > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Pending__ section, one or more of the settings listed below may be displayed:
+<br>
+<ul>
+<br>
+    	<li><b>Enable transactional emails on Message Center</b>: click in <b>Enable</b> to install the transactional email templates related to Customer Credit in <a href="https://help.vtex.com/pt/tutorial/conhecendo-o-message-center--tutorials_84">Message Center</a>.</li>
+    	<li><b>Setting checkout payment conditions</b>: click in <b>Setting</b> to allow the definition of the store's deadline and installment rules.</li>
+  	<li><b>Affiliation not authenticated</b>: click in <b>Authenticate</b> to be redirected to the configuration screen where you must fill in the information <b>Application Key</b> and <b>Application Token</b>. This action will allow payments made through Customer Credit to be processed in your store. Find out more at <a href="https://developers.vtex.com/docs/guides/authentication">Authentication</a>.</li>
+</ul>
 
-This way, Customer Credit will be available as a payment method in your store's SmartCheckout.
+![CC Configuration 1 EN](//images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/25a43afef349f6443a55820be9f17616/CC_Configuration_1_EN.JPG)
 
 ## App settings
-There are four options to customize the consumer experience in your store.
-Check the details of each below.
+
+Then, still on the same VTEX Admin screen(__Apps > Customer Credit > Settings__), you should check the following settings options:
+
+- [Tolerance](#tolerance)
+- [Automatic account creation](#automatic-account-creation) 
+- [My Credits page](#my-credits-page)
+- [Payment instructions](#payment-instructions)
+- [Identifying Information](#identifying-information)
 
 ### Tolerance
 
-With this feature, a purchase can be concluded even if it exceeds the user's available credit. You can set a tolerance percentage to limit the surplus credit available for each account.
+Activating this option allows a purchase to be completed even if its value exceeds the customer's available credit limit. When creating an account, it is possible to register an excess credit percentage (tolerance) for each customer.
 
-For example, let's say an account has US$ 1,000 in available credit and a tolerance of 10%. Thus, the system will allow the customer to place orders of up to US$ 1,100.
+For example, for an account created with a credit limit of $1,000.00 and a tolerance of 10%, the customer will be able to place an order with a maximum value of $1,100.00 using Customer Credit as a payment method. If the customer wishes to use the credit to pay for an order worth $1,250.00, the system will not allow the purchase to be completed.
 
 <div class="alert alert-warning">
-Tolerance values are set in decimal numbers, with 0 representing 0% and 1 representing 100%. Example: for a 5% tolerance, the value to be set is 0.05.
+Tolerance values are configured in decimal numbers, with 0 representing 0% and 1 representing 100%. Example: to use a tolerance of 5%, the value to be configured is 0.05.
 </div>
 
-To set the tolerance, check out the step by step:
-
-1. Access __Admin__.
-2. Click on __Customer Credit__.
-3. Then, click on __Accounts__.
-4. Click on the customer account for which you want to set the tolerance.
-5. In __Tolerance__, click on __Edit__.
-6. Fill in the tolerance value (in decimals).
-7. Click on __Update__.
+![CC_Configuration_2_EN](//images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/42de816c9685f31074c0637dcbd6c5f1/CC_Configuration_2_EN.JPG)
 
 ### Automatic account creation
-This flag allows customers to complete purchases using Customer Credit as a payment method, even if they do not have a previous account with a defined credit limit.
 
-On the settings page, you have the option to set a default credit limit for customers whose accounts will be automatically created on SmartCheckout.
+This option allows any store customer to use Customer Credit as a payment method, even if you have not previously created an account for them in the Customer Credit app. When activating this functionality, you must also define the initial credit limit that can be used for orders placed by customers without a Customer Credit account.
+
+![CC_Configurações_3_EN](//images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/07a144ef285f845819fb1e12442b3f56/CC_Configuration_3_EN.JPG)
 
 ### My Credits page
-It is the interface through which your end-users will have access to their account information.
 
-In it, users can see their available limits, invoices and statements, and they can also add or remove dependents.
+By installing the __My Credits__ page, you will allow customers to view and manage information about the credits and titles available in their account.
 
-When the page is activated, it will be available in the customers’ MyAccount area.
+The customer can access this page on your store's website at __My account > My Credits__.
 
-### Payment instructions
-Here, the user can add payment instructions to their title documents. To do this, click on “Edit” and write the instruction. Don't forget to click on the “Update” button to save your settings.
+![CC_Configuration_4_EN](//images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/92daf3c995157e03887f1975d2cccbc8/CC_Configuration_4_EN.JPG)
 
-The same instruction will be replicated in all invoices of your store, regardless of the account to which they are linked and their status.
+### Payment Instructions 
 
-## Payment conditions
-At this point, Customer Credit is properly installed and configured in your store. You can now create payment conditions that will be displayed on SmartCheckout.
+This configuration allows you to insert instructions related to payment in the invoices issued by Customer Credit. To edit the message to be displayed in the invoice, enter the information in the test box and click `Update`.
 
-You can define different business scenarios for these payment conditions. This also implies which term and installment conditions will be available for customers.
+<div class="alert alert-warning">
+The message registered in this configuration will be replicated on all invoices issued for all Customer Credit accounts. It is not possible to configure a unique message for each specific customer or invoice.
+</div>
 
-Here are some payment terms that can be used:
+![CC_Configuration_5_EN](//images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/cdf9331ac0d8e46d6537c8f265bc621b/CC_Configuration_5_EN.JPG)
 
-- Payments within 7, 28 and 45 days;
-- Payments within 45 days;
-- Installments in 30, 60 and 90 days.
+### Identifying Information
 
-Check out the step by step:
+This option allows you to select which store identification information should be displayed at the top of issued invoices.
 
-1. Access __the Admin__;
-2. Click on __Payments__;
-3. Click on __Settings__;
-4. Make sure you are in the __Payment Conditions__ tab;
-5. On the right side of the screen, click on the __“+”__ button;
-6. Find and click on the __Customer Credit__ option;
-7. On the right side, define the criteria in the box __Configure deadline and installment rules__.
+![CC_Configuration_6_EN](//images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/94bce774843c23fa582f065689423087/CC_Configuration_6_EN.JPG)
 
-If you want to add more than one rule, click on the "Add new rule" button. Finally, click on the “Save” button.
+![CC_Configuration_8_EN](//images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/7078eccb9c08d690fb0f453456f2dcaf/CC_Configuration_8_EN.JPG)
 
-In the same way as other payment methods, Customer Credit allows you to configure [special conditions](https://help.vtex.com/en/tutorial/condicoes-especiais?locale=en "special conditions."). Users will define which purchase contexts will be applied to each payment condition configured in their stores.
+## Payment conditions
 
-### Interest
-Finally, you can also set simple interest rates for the installment rules configured in your store. Currently, these rates can be applied to orders that will be paid in two or more installments.
+Once the Customer Credit settings are completed, it is necessary to indicate which term and installment options will be available to be displayed to customers on the Checkout screen.
 
-<div class="alert alert-warning">
-<strong>Warning</strong>: Interest rates do <strong>not</strong> apply to orders paid in full.
-</div> 
+To create payment conditions for Customer Credit invoices, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. On the __Payment Conditions__ tab, click the `+` button.
+3. Select the option __Customer Credit__.
+4. Fill in the field __Condition name__ with a name of your choice for identification.
+5. Enable the condition in the __Status__ field.
+6. In __Configure Due Date and Installment Rules__, indicate the number of installments, due period (in days) and the simple interest rate to be applied to each installment. To create more than one payment condition, click `Add new condition`.
 
-However, only one interest rate will be displayed on SmartCheckout.
+![CC_Configuration_9_EN](//images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/77399f912ebbb03ac5611682eca77c06/CC_Configuration_9_EN.JPG)
 
-For example, let's say you have set up three installment options for Customer Credit, each with a different interest rate: 10%, 15% and 20%.
+<blockquote><ui>7. If you wish, you can also configure <a href="https://help.vtex.com/en/tutorial/special-conditions--tutorials_456">payment special conditions</a>.</ui>
 
-Since the 10% rate is the most advantageous for the end consumer, this will be the only payment option shown on SmartCheckout.
+<blockquote><ui>8. Click <b>Save</b>.</ui>
+
+<div class="alert alert-warning">
+It is not possible to set an interest rate for a payment condition created with just a single installment. 
+</div>
diff --git a/docs/tracks/en/setting-up-the-logistics-for-mercado-livre.md b/docs/tracks/en/setting-up-the-logistics-for-mercado-livre.md
index e29db724c..e44e89173 100644
--- a/docs/tracks/en/setting-up-the-logistics-for-mercado-livre.md
+++ b/docs/tracks/en/setting-up-the-logistics-for-mercado-livre.md
@@ -3,8 +3,8 @@ title: 'Setting up the logistics for Mercado Livre'
 id: 4551ZlEQI8qmiSWieigoKy
 status: PUBLISHED
 createdAt: 2018-08-13T12:53:57.008Z
-updatedAt: 2023-03-28T13:36:16.191Z
-publishedAt: 2023-03-28T13:36:16.191Z
+updatedAt: 2024-07-23T22:07:18.063Z
+publishedAt: 2024-07-23T22:07:18.063Z
 firstPublishedAt: 2018-08-13T14:27:58.483Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/setting-up-the-order-summary-printing.md b/docs/tracks/en/setting-up-the-order-summary-printing.md
index 19acc5790..7a0d424d4 100644
--- a/docs/tracks/en/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/en/setting-up-the-order-summary-printing.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-customizations
 
 When the salesperson completes an order with inStore, they can print a summary of that order. But, to enable this functionality, you need to make some settings.
 
-![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
+![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
 
 Two steps are required:
 
@@ -50,7 +50,7 @@ Do not remove any of the other properties present in the <code>window.INSTORE_CO
 
 This change will make the __Configure device__ option appear in the inStore main menu, as shown in the image below. It is through this option that you will configure the printer.
 
-![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
+![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
 <div class="alert alert-info">
 <strong>Note:</strong> There is an option to automatically print the order summary as soon as the order is completed. To enable it, add the <code>printPageAutomatically</code> property with the value <code>true</code> inside the <code>printingConfig</code> object. See below how the code would look like in this case.
@@ -84,11 +84,11 @@ With AppKey and AppToken in hand, follow the steps below:
 2. Open the inStore app and enter the store where you want to set up the printer.
 3. In the inStore main menu, in the Settings section, the option __Configure device__ should now appear. Click on that option.
 
-![15. Configurar impressão de resumo do pedido - 3](https://images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
+![15. Configurar impressão de resumo do pedido - 3](//images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
 
 You will find the summary of the configured device. If this is the first time you are making this configuration, the fields on this screen will be empty. If a device has been previously configured, some information about the device will be displayed (Device name and Default printer). Click the __Edit__ button.
 
-![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 A form will show containing the __AppKey__, __AppToken__ and __name__ fields with which you want to identify the device. After entering this data, click __Configure__.
 
diff --git a/docs/tracks/en/settings-on-via-marketplace.md b/docs/tracks/en/settings-on-via-marketplace.md
index 29b6547ec..b76d09d5d 100644
--- a/docs/tracks/en/settings-on-via-marketplace.md
+++ b/docs/tracks/en/settings-on-via-marketplace.md
@@ -1,10 +1,10 @@
 ---
-title: 'Settings on Via Marketplace'
+title: 'Settings on Casas Bahia Marketplace'
 id: 2oxPVeYpVgA8IrhaDqKon6
 status: PUBLISHED
 createdAt: 2022-01-18T21:39:29.664Z
-updatedAt: 2023-02-08T14:50:54.438Z
-publishedAt: 2023-02-08T14:50:54.438Z
+updatedAt: 2024-01-22T15:59:29.253Z
+publishedAt: 2024-01-22T15:59:29.253Z
 firstPublishedAt: 2022-01-18T22:32:05.415Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
index 1a167f36e..63efea955 100644
--- a/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
@@ -3,8 +3,8 @@ title: 'Sharing shopping cart using VTEX Sales App Social Selling'
 id: 6deiffo22iKkY27PkfstXy
 status: PUBLISHED
 createdAt: 2021-08-05T14:57:10.773Z
-updatedAt: 2023-05-31T15:22:18.271Z
-publishedAt: 2023-05-31T15:22:18.271Z
+updatedAt: 2023-07-26T19:00:02.450Z
+publishedAt: 2023-07-26T19:00:02.450Z
 firstPublishedAt: 2021-08-05T15:08:06.961Z
 contentType: trackArticle
 productTeam: Shopping
@@ -37,7 +37,7 @@ This option allows sales associates to share shopping carts ready for purchase w
 
 See the step-by-step instructions illustrated below.
 
-![socialselling-sugestaocarrinho-en](https://images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/66a5a405d1c213ebe66d798799e972ef/socialselling-sugestaocarrinho-en.gif)
+![socialselling-sugestaocarrinho-en](//images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/66a5a405d1c213ebe66d798799e972ef/socialselling-sugestaocarrinho-en.gif)
 
 The same link is shareable with multiple customers as many times as they like. Each time a person accesses this link, a new shopping cart is generated, exactly like the one created in VTEX Sales App. Carts accessed are also associated with the sales associate account and their code, if they have one.
 
@@ -63,4 +63,4 @@ In this case, the sales associate needs to add items to the cart, fill in the cu
 
 See the step-by-step instructions illustrated below.
 
-![socialselling-paymentlink-en](https://images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/13e08b6558e7c4b2ecd22c242d4f7247/socialselling-paymentlink-en.gif)
+![socialselling-paymentlink-en](//images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/13e08b6558e7c4b2ecd22c242d4f7247/socialselling-paymentlink-en.gif)
diff --git a/docs/tracks/en/shipping-strategies.md b/docs/tracks/en/shipping-strategies.md
index 653c327d5..edb9e6f15 100644
--- a/docs/tracks/en/shipping-strategies.md
+++ b/docs/tracks/en/shipping-strategies.md
@@ -18,7 +18,7 @@ The shipping options offered to the customer at the checkout of your store are c
 
 The shipping strategy defines how warehouses, loading docks, and shipping policies interact to meet the needs of your customers and your business. 
 
-![Estrategia EnvioEN](https://images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/f21e70736f667399bb811dea84caf5c7/Estrategia_EnvioEN.png)
+![Estrategia EnvioEN](//images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/f21e70736f667399bb811dea84caf5c7/Estrategia_EnvioEN.png)
 
 The shipping strategy is defined by three logistics entities:
 
diff --git a/docs/tracks/en/specifications-mapping.md b/docs/tracks/en/specifications-mapping.md
index e53e48857..9c52b3589 100644
--- a/docs/tracks/en/specifications-mapping.md
+++ b/docs/tracks/en/specifications-mapping.md
@@ -16,10 +16,10 @@ trackSlugEN: lengow-integration
 
 [Specification fields](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) are additional properties that can be added to your products or SKUs. They can be submitted to enrich your catalog with information that is required by different channels. 
 
-In the **Specifications mapping** section seen in *Marketplace > Lengow Integration > Settings*, you can send [product specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#product-specification) or [SKU specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#sku-specifications) to Lengow. Clicking on the <img src="https:https://images.ctfassets.net/alneenqid6w5/2KymcHLipd3OUJPvxspzeM/99925b311364a3ccb2e212e66e07ddf4/Screen_Shot_2020-07-01_at_22.51.00.png" style="width: 23px;" /> button adds a new row and clicking on the <img src="https:https://images.ctfassets.net/alneenqid6w5/vJZkSDRUy4etx7d4q48YX/19a559aec5a896cd5f121c4d1ec277f2/Screen_Shot_2020-07-01_at_22.50.20.png" style="width: 23px;" /> button removes it from mapping tables.
+In the **Specifications mapping** section seen in *Marketplace > Lengow Integration > Settings*, you can send [product specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#product-specification) or [SKU specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#sku-specifications) to Lengow. Clicking on the <img src="https://images.ctfassets.net/alneenqid6w5/2KymcHLipd3OUJPvxspzeM/99925b311364a3ccb2e212e66e07ddf4/Screen_Shot_2020-07-01_at_22.51.00.png" style="width: 23px;" /> button adds a new row and clicking on the <img src="https://images.ctfassets.net/alneenqid6w5/vJZkSDRUy4etx7d4q48YX/19a559aec5a896cd5f121c4d1ec277f2/Screen_Shot_2020-07-01_at_22.50.20.png" style="width: 23px;" /> button removes it from mapping tables.
 
 For each specification, fill in the left column with its name in VTEX and the right column with the name that should be used in Lengow. Both columns may have the same values. If needed, you may repeat a VTEX specification to map it out to multiple Lengow specifications.
 
-![Lengow - Specifications mapping](https://images.ctfassets.net/alneenqid6w5/4mcy8worOtuTEiPzSBHthD/8c7304156d13269af3eca4c1efa12eec/Screen_Shot_2020-07-01_at_23.00.21.png)
+![Lengow - Specifications mapping](//images.ctfassets.net/alneenqid6w5/4mcy8worOtuTEiPzSBHthD/8c7304156d13269af3eca4c1efa12eec/Screen_Shot_2020-07-01_at_23.00.21.png)
 
 <div class="alert alert-warning" role="alert">All <a href="https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP" target="_blank">specification fields</a> must be created and set up prior to this step. Make sure the name used in the mapping tables is exactly as seen in the Catalog, otherwise the connector will not be able to find the proper values to send to Lengow.</div>
diff --git a/docs/tracks/en/store-development.md b/docs/tracks/en/store-development.md
index 2743c71fb..5f9e72c8d 100644
--- a/docs/tracks/en/store-development.md
+++ b/docs/tracks/en/store-development.md
@@ -19,7 +19,7 @@ In an ecommerce store, both the interface that users see and interact with, and
 - **Frontend**: The frontend consists of the visual layer of an application, such as a website's or mobile app's interface. It is through it that users interact with a store. On VTEX, three different technologies can be used to build storefronts: the CMS Portal (Legacy), the Store Framework, and FastStore.
 - **Backend**: The backend is the layer responsible for computing and processing all the data needed to execute the functionalities offered by a given application. On VTEX, the integration and backend application development are done mainly through VTEX IO and VTEX APIs.
 
-![storefront mockup](https://images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/9f957800cf3b303a7887421c75fb1f74/image1.png)
+![storefront mockup](//images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/9f957800cf3b303a7887421c75fb1f74/image1.png)
 
 In the following sections, we will further explore the key aspects and technologies related to store development on VTEX.
 
diff --git a/docs/tracks/en/subject-rights.md b/docs/tracks/en/subject-rights.md
new file mode 100644
index 000000000..13c91f6bd
--- /dev/null
+++ b/docs/tracks/en/subject-rights.md
@@ -0,0 +1,31 @@
+---
+title: 'Data subject rights'
+id: 1ZWqUdeKsD8Mm3GKQ8xBI3
+status: PUBLISHED
+createdAt: 2024-05-03T20:20:18.952Z
+updatedAt: 2024-05-03T21:27:03.812Z
+publishedAt: 2024-05-03T21:27:03.812Z
+firstPublishedAt: 2024-05-03T20:25:55.041Z
+contentType: trackArticle
+productTeam: Others
+slug: subject-rights
+locale: en
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugEN: data-and-privacy
+---
+
+A data subject request is a written request that your store's customers can make to exercise their right to obtain information about the data being processed by the store and VTEX.
+
+Anyone has the right to confirm whether a store is processing their data. If so, the data subject also has the right to access the data and know the purpose of the processing, the personal data categories, and the recipients or categories of recipients with whom their personal data has been shared.
+
+To learn more, check the [Data subject rights](https://help.vtex.com/en/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM) guide.
+
+## Erasing data
+
+At any time, merchants can erase personal data upon customer request. The end customer must make the request to the merchant directly, and the merchant must forward these requests to VTEX. The right to erasure overrides the retention period.
+
+If you manage a VTEX store and need help erasing user data, see [Erasing customer data](https://help.vtex.com/en/tutorial/erasing-customer-data--1R9Fn7A06Ifj4R9YD4JTKU). 
+
+## Editing data
+
+All your customers' personal data is editable on the[ My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) page, except for their email addresses. In this case, you can delete the old profile and create a new one using a different email address.
diff --git a/docs/tracks/en/technical-and-administrative-measures.md b/docs/tracks/en/technical-and-administrative-measures.md
new file mode 100644
index 000000000..13864bbf4
--- /dev/null
+++ b/docs/tracks/en/technical-and-administrative-measures.md
@@ -0,0 +1,56 @@
+---
+title: 'Technical and administrative measures'
+id: 7ANSqBP5DgOrVVyglo3Lbh
+status: PUBLISHED
+createdAt: 2024-05-03T20:26:17.710Z
+updatedAt: 2024-05-03T21:12:11.696Z
+publishedAt: 2024-05-03T21:12:11.696Z
+firstPublishedAt: 2024-05-03T20:57:29.358Z
+contentType: trackArticle
+productTeam: Others
+slug: technical-and-administrative-measures
+locale: en
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugEN: data-and-privacy
+---
+
+VTEX operates in different countries and has the necessary tools to meet the privacy demands of each location. For this reason, VTEX always takes the necessary measures to ensure its platform is secure and complies with data protection laws.
+
+The tools we provide on the platform are designed to ensure that stores comply with privacy laws. However, merchants must also implement additional measures to comply with personal data processing laws. To understand these requirements, see [Data protection roles](https://help.vtex.com/en/tracks/data-and-privacy--4Lc0i0an0DgnEtB0AUwlcq/5f8hTEw3xOALgqzus9VXKd). Note that these are general guidelines and that specific regulations may impose other obligations.
+
+## Security
+
+VTEX maintains appropriate technical and organizational measures to protect the security, confidentiality, and integrity of personal data when providing services.
+
+See below the practices adopted by VTEX, detailed in the[ DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/):
+
+- Antivirus policy.
+- Information classification.
+- Vulnerability management.
+- Encryption of personal data at rest and in transit.
+- Data backup and redundancy. VTEX has a specific tool to provide customers with the means to obtain a full copy of all personal data stored on the platform.
+- Disaster recovery and incident recovery.
+- Segregation of clients and networks.
+- Physical security measures.
+- Guaranteed deletion of all personal data after the end of service provision.
+- Ensuring that any employee who accesses personal data is bound by confidentiality agreements with VTEX.
+- Specific incident management and notification process and informing the customer, as required by data protection laws, if they become aware of any personal data breach.
+- Support for merchants in conducting a [Data Protection Impact Assessment (DPIA)](https://commission.europa.eu/law/law-topic/data-protection/reform/rules-business-and-organisations/obligations/when-data-protection-impact-assessment-dpia-required_pt).
+
+For more information, see [Security Practices - VTEX](https://vtex.com/us-en/security/security-practices/).
+
+## Storage
+
+The [hosting provider](https://vtex.com/us-en/privacy-and-agreements/subprocessors/) used by VTEX is Amazon Web Services (AWS), which stores data in the Northern Virginia region of the United States. The AWS platform is a benchmark in the cloud hosting sector and has important certifications, such as ISO 27001, PCI DSS, CSA, NIST, etc. For a detailed list of certifications, see [AWS Compliance Programs](https://aws.amazon.com/en/compliance/programs/). Authorization for data storage on AWS can be found in our [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/).
+
+VTEX only stores personal data for as long as necessary to process the service provided.
+
+## Personal data retention
+
+Data retention limits define the duration data can be stored on VTEX. These limits are influenced by multiple factors, such as legal and compliance requirements, data privacy considerations, and costs. By setting data retention limits, we aim to ensure regulatory compliance, protect user privacy, and maintain efficient resource allocation.
+
+Responsibility for compliance with applicable laws and regulations lies with the merchants themselves. This includes defining and respecting data retention periods, which may vary according to the specific legislation each store is subject to. 
+
+VTEX makes data available based on the technical capacity of each module. However, if specific legislation needs to be complied with, merchants need to extract the relevant data from the platform. Therefore, each merchant must manage their own retention periods as required by the applicable legislation, using the resources available on the platform accordingly.
+
+VTEX must store customer personal data for the duration of the [MSA](https://vtex.com/us-en/privacy-and-agreements/agreements/). In the event of contract termination with VTEX, the merchant must ensure that the data is extracted from the Master Data within thirty (30) days before the MSA termination date, in compliance with Clause 7 of the [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/).
diff --git a/docs/tracks/en/technical-support.md b/docs/tracks/en/technical-support.md
new file mode 100644
index 000000000..41a04bf50
--- /dev/null
+++ b/docs/tracks/en/technical-support.md
@@ -0,0 +1,33 @@
+---
+title: 'Technical support'
+id: 3thRAdTB3gGwTB0e1fVL3T
+status: PUBLISHED
+createdAt: 2024-02-20T21:34:10.778Z
+updatedAt: 2024-02-22T14:08:41.465Z
+publishedAt: 2024-02-22T14:08:41.465Z
+firstPublishedAt: 2024-02-22T14:08:41.465Z
+contentType: trackArticle
+productTeam: Others
+slug: technical-support
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+During and after the development of a store, it is expected to have questions about implementations, [module settings](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), [storefront development](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), apps, and other technical matters. In this sense, technical support is available to help with questions regarding the platform, store development, applications, and implementations.
+
+The following table shows the main topics related to technical support:
+
+| Topic | Description |   Articles  |
+|-------|-------------|-------------|
+| [VTEX IO](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#development-environment)  | VTEX IO is a low-code, cloud-based development platform that allows developers to create ecommerce solutions. It's designed to provide an easy way to develop customized solutions and integrations within the VTEX ecosystem. | [What is VTEX IO?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework)                                                  |
+| [Store Framework](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) | Store Framework is a VTEX technology for building low-code storefronts focused on composability. It allows different VTEX IO applications to be combined to build a storefront. | [What is VTEX Store Framework?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework)<br><br>  [FAQ VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-frequently-asked-questions) |
+| [VTEX App](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#what-is-an-app-on-vtex) | VTEX apps extend the platform's features, helping store owners to create experiences in different areas of the store. This includes aspects such as marketing, product reviews, customer support, notifications, logistics, store customization, and more. | [What is a VTEX App?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app)  |
+| Layout          | VTEX technology for building storefronts using [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). The layout allows you to create and customize your storefront using HTML, JavaScript, and CSS via the VTEX Admin.<br><br>  Currently, the layout is available for some VTEX stores, but not for new stores joining VTEX. | [CMS - Legacy Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj)<br><br>  [Layout Overview](https://help.vtex.com/en/tutorial/what-is-cms-layout--EmO8u2WBj2W4MUQCS8262)                              |
+| [ERP integration](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#erp-integration) | Integrating an ERP with the VTEX platform is an important strategy for optimizing ecommerce operations with the possibility of integrating external software.| [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide)<br><br>  [FAQ: ERP Integration](https://developers.vtex.com/docs/guides/faq-erp-integration) |
+
+If the user needs technical support and can't find solutions on the portals and documentation mentioned, they can contact us via the [Support page](https://support.vtex.com/hc/pt-br/requests) and select the **Technical** option via the VTEX IA Support Bot, a chatbot focused on technical assistance, as shown in the image below:
+
+![Support imagem 2 -EN](//images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/bebfbb302b01ba80644d77e460136f99/support_imagem2_EN.png)
+
+If the user needs support beyond the VTEX IA Support Bot, they can open a ticket by clicking `OPEN TICKET`. For more information on how to complete a ticket for technical support, read the [Opening tickets to VTEX Support - Technical](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#technical) article.
diff --git a/docs/tracks/en/teste-1.md b/docs/tracks/en/teste-1.md
index b09a550f1..ec9b7bde2 100644
--- a/docs/tracks/en/teste-1.md
+++ b/docs/tracks/en/teste-1.md
@@ -3,7 +3,7 @@ title: 'Teste (1)'
 id: 2Oq3MriB8hJ5YmFq3QIlPD
 status: DRAFT
 createdAt: 2021-04-14T14:58:44.451Z
-updatedAt: 2023-06-01T14:02:58.525Z
+updatedAt: 2024-02-23T14:24:12.796Z
 publishedAt: 
 firstPublishedAt: 2021-04-14T15:01:28.601Z
 contentType: trackArticle
@@ -14,5 +14,65 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugEN: magazine-luiza-integration-set-up
 ---
 
-abc
+With client success in mind, VTEX offers complete solutions for different business models. This puts the flexibility of composable commerce at the service of innovation and growth in your operation.
 
+To help you easily adopt new resources, manage your business autonomously, and gain scalability, we have published the new **Onboarding guide** — content covering the complete journey for operating a VTEX store. This documentation will be available in the [Start here](https://help.vtex.com/en/tracks) section of the Help Center.
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/359WPOFfC5pE91DpoECZJe/ead8add75ce24d17af10d12a439959f0/announcement_complete_guide_EN.png" alt="Onboarding guide">
+</div>
+
+## What is the Onboarding guide?
+
+The **Onboarding guide** is a collection of three documentation tracks, which include planning the store architecture, go-live configurations, products to help evolve your business, and guidelines about our support. The guide describes and contextualizes the platform settings and resources within the VTEX store journey.
+
+The **Onboarding guide** has three tracks:
+
+- [VTEX store overview](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9)
+- [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS)
+- [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy)
+
+<div class="alert alert-info">
+The tracks include content that complement one another, but they are intended to be standalone. This means you can explore the content freely, without following any specific order.
+</div>
+
+Our aim is to allow clients, partners, and the VTEX ecosystem to take advantage of the **Onboarding guide**. We took into account a comprehensive journey to make sure the content stayed relevant for different businesses.
+
+You can find an [overview](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9) of the guide content below.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/1N4nX2r9WxhdSCqr8zOEla/08f6af21193f72196786c3675d950a0e/announcement_headings_track_1_EN.png" height="90" alt="VTEX store track">
+</div>
+
+The **VTEX store track** describes the initial context of the operation, starting by defining the [account type and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) that best suit the business needs. From there, you can complete the [initial setup](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) and configure the platform [modules](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), focusing on getting the operation going. Once the [backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) are completed and the [frontend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) technology has been implemented in order to build the storefront, it's time for the [go-live](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) and launching the new store.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6yRmvP19rt7z1mNE7vdWQz/0e09fd47f72f6177da8f318ea78d0d9f/announcement_headings_track_2_EN.png" height="90" alt="Next steps after go live">
+</div>
+
+The **Next steps after go-live** track describes how [unified commerce](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/5Qvw31yH2FPDBl14K5xXHA) is achieved with the platform resources, including [module settings](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) not mentioned before. The aim here is to focus on evolving the operation. This track also describes VTEX's [add-on products](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm), which are products that can be requested separately for implementing new strategies and diversifying the business.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6N7adQ7RxTfTyuIrCDqstZ/500c3acec9c5f6c7ddc8895df69916ac/announcement_headings_track_3_EN.png" height="90" alt="VTEX Support">
+</div>
+
+The **VTEX Support** track describes the [support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) offered by VTEX to clients, which is not restricted to a specific part of the journey. Other tracks also mention [how support works](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3), since [opening a ticket](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE) is the designated channel for certain requests. The organization of this track aims to help our clients have the best experiences with our services, providing all the necessary information for opening tickets, whether for [technical](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [billing](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl), or [commercial](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) support.
+
+## Why did we create this content?
+
+We organized the **Onboarding guide** to provide autonomy for our clients. Here are some highlights about the guide:
+
+- **Complete journey:** This is the first documentation that covers the complete operational journey of a VTEX store. The content is designed to make go-live faster and reduce the _time to revenue_ of the business.
+- **Brand-new content:** In addition to the new approach of the journey, there is brand-new content, with the following highlights in the _VTEX store track_ ([Accounts and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl), [Backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), [Frontend implementation](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)), in the _Next steps after the go-live track_ ([Add-on products](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm)), and the _VTEX Support track_ as a whole.
+- **General relevance:** The value of this guide is not restricted to new clients or stores in the phases before go-live. We envisioned a comprehensive journey to make it relevant for different business models.
+
+We hope this content contributes to the success of your business and your satisfaction with VTEX.
+
+|  | **Onboarding guide** |  |
+| :---: | :---: | :---: |
+| Part I | Part II | Part III |
+| [VTEX store overview](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9) | [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS) | [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy) |
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/4CgTVLjK3cazg4dDyVlB8m/924575a75836acd4e7b5e4a4c199b516/announcement_under_table_image_EN.png" alt="Ecommerce image">
+</div>
diff --git a/docs/tracks/en/the-reservation.md b/docs/tracks/en/the-reservation.md
index 86062a28d..95cda2559 100644
--- a/docs/tracks/en/the-reservation.md
+++ b/docs/tracks/en/the-reservation.md
@@ -34,7 +34,7 @@ This is the reservation flow at VTEX:
  
  3. Finally, once the order is being prepared for delivery, the items move to the status `Reservation Acknowledged`. This status indicates that the items no longer exist in the physical inventory.
 
-![reservation en](https://images.ctfassets.net/alneenqid6w5/7mm0YP3bcfb5fqZf5XhmZX/8798695363d5f4008f0a9c7078ebc386/reservation_en.png)
+![reservation en](//images.ctfassets.net/alneenqid6w5/7mm0YP3bcfb5fqZf5XhmZX/8798695363d5f4008f0a9c7078ebc386/reservation_en.png)
 
 <div class="alert alert-warning">
 VTEX does not automatically remove items from the inventory, even after they have moved to <code>Reservation Recognized</code> status. Purchased items will remain in this status until the ERP or the store remove them from the inventory.
diff --git a/docs/tracks/en/unified-commerce-101.md b/docs/tracks/en/unified-commerce-101.md
index 60c26a10d..cfedb3eb8 100644
--- a/docs/tracks/en/unified-commerce-101.md
+++ b/docs/tracks/en/unified-commerce-101.md
@@ -3,8 +3,8 @@ title: 'Omnichannel'
 id: 2LGAiUnHES1enjHsfi8fI3
 status: PUBLISHED
 createdAt: 2020-06-30T20:38:48.297Z
-updatedAt: 2023-05-31T14:45:20.583Z
-publishedAt: 2023-05-31T14:45:20.583Z
+updatedAt: 2023-07-26T18:50:02.780Z
+publishedAt: 2023-07-26T18:50:02.780Z
 firstPublishedAt: 2020-06-30T20:45:00.959Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,34 +16,34 @@ trackSlugEN: unified-commerce-strategies
 
 The evolution of online retail has brought a series of improvements to the customer experience, and one of the most relevant is perhaps the one that transformed the multichannel relationship between customer and store into an omnichannel relationship.
 
-![32. Unified Commerce 101 - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/YYPXpy8HRuqRE8CX2cgYC/b4c9a5a5b094d256798a3a017c4d9ce7/32._Unified_Commerce_101_-_1_-_EN.png_h_250)
+![32. Unified Commerce 101 - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/YYPXpy8HRuqRE8CX2cgYC/b4c9a5a5b094d256798a3a017c4d9ce7/32._Unified_Commerce_101_-_1_-_EN.png_h_250)
 
-In a __multichannel__ architecture, each channel communicates independently with the store, be it the e-commerce, physical stores, call centers, social media, etc. When a customer interacts with one of these channels, the store has no knowledge at all of who that customer is.
+In a __multichannel__ architecture, each channel communicates independently with the store, be it the ecommerce, physical stores, call centers, social media, etc. When a customer interacts with one of these channels, the store has no knowledge at all of who that customer is.
 
 In an __omnichannel__ architecture, customer data is shared between store channels. This means that when the customer who has already interacted with the store starts a new interaction through a different channel, the store is aware of who that customer is, what their order history is, their purchase profile, etc.
 
-In omnichannel, however, orders are still processed in isolation. Although there is data sharing, orders that take place in e-commerce live only in e-commerce, whereas those that take place in a physical store live only in that specific store, and so on. An order placed on one channel cannot be completed on another, for example.
+In omnichannel, however, orders are still processed in isolation. Although there is data sharing, orders that take place in ecommerce live only in ecommerce, whereas those that take place in a physical store live only in that specific store, and so on. An order placed on one channel cannot be completed on another, for example.
 
 The __Unified Commerce__ solves this problem.
 
-![32. Unified Commerce 101 - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6IuAQNFiyqaUgcRLA2mSDP/673202ebbfa44580a9e737269b738b9c/32._Unified_Commerce_101_-_2_-_EN.png_h_250)
+![32. Unified Commerce 101 - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6IuAQNFiyqaUgcRLA2mSDP/673202ebbfa44580a9e737269b738b9c/32._Unified_Commerce_101_-_2_-_EN.png_h_250)
 
 Unified Commerce is an evolution of omnichannel: in addition to data sharing, this strategy also involves __unifying the order processing and management system__. In practice, this means that every order placed on one store channel is not only visible by other channels but can be processed by them.
 
 Below are some of the scenarios made possible by Unified Commerce:
 - __Endless Aisle__: customer buys in a channel (in a physical store, for example) and receives from the stock of another store or the main Distribution Center.
 - __Transaction with mixed cart__: customer buys in a physical store, picks up one of the products there and receives the other at home from another stock.
-- __Pickup in store__: customer buys in the e-commerce and picks up the products in a physical store.
+- __Pickup in store__: customer buys in the ecommerce and picks up the products in a physical store.
 
 At VTEX, these and other scenarios are possible because the catalog is accessible trough all channels and the Order Management System orchestrates all orders, whether they are made online or offline.
 
-## inStore
+## VTEX Sales App
 
-InStore is a VTEX app that allows sales associates to cater customers in a personalized way and complete the entire sales process, from helping to choose products to payment and delivery.
+VTEX Sales App is a VTEX app that allows sales associates to cater customers in a personalized way and complete the entire sales process, from helping to choose products to payment and delivery.
 
-It is an important tool in your Unified Commerce strategy because it interacts with the unified database of your VTEX account and with our Order Management System. In other words, all sales made with inStore give the sales associates access to the customer's data, even if this customer has never bought at that physical store. It also allows the creation of orders in which fulfillment is carried out from other channels and stocks.
+It is an important tool in your Unified Commerce strategy because it interacts with the unified database of your VTEX account and with our Order Management System. In other words, all sales made with VTEX Sales App give the sales associates access to the customer's data, even if this customer has never bought at that physical store. It also allows the creation of orders in which fulfillment is carried out from other channels and stocks.
 
-If you want more details, see our [check out our documentation about inStore](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf).
+If you want more details, see our [check out our documentation about VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf).
 
 ## Learn more
 
diff --git a/docs/tracks/en/unified-commerce.md b/docs/tracks/en/unified-commerce.md
new file mode 100644
index 000000000..a6835c5a4
--- /dev/null
+++ b/docs/tracks/en/unified-commerce.md
@@ -0,0 +1,56 @@
+---
+title: 'Unified commerce'
+id: 5Qvw31yH2FPDBl14K5xXHA
+status: PUBLISHED
+createdAt: 2024-02-20T20:19:58.572Z
+updatedAt: 2024-04-03T12:14:19.783Z
+publishedAt: 2024-04-03T12:14:19.783Z
+firstPublishedAt: 2024-02-22T14:08:56.252Z
+contentType: trackArticle
+productTeam: Others
+slug: unified-commerce
+locale: en
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugEN: next-steps-after-the-go-live
+---
+
+[Unified commerce](https://help.vtex.com/pt/tracks/unified-commerce-strategies--3WGDRRhc3vf1MJb9zGncnv) is an evolution of omnichannel. This strategy involves data sharing and the unification of the order processing and management system. It means that every order placed in a store channel is visible to other sales channels and can also be processed within them. Operating with franchise accounts and [white label sellers](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) in an increasingly connected context can be very strategic for the business.
+
+## Franchise accounts and white label sellers
+
+[Franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) are accounts associated with a [main account](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). Companies with multiple physical stores, franchisees, or multi-brands can create franchise accounts associated with the brand's main account.
+
+![main account](//images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/aaa2c7b886fb7a050c684465fb08c8f8/next_steps_image1_EN.png)
+
+This model shares Catalog and [storefront](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) information, allowing the franchise accounts' inventory to be available for sale in the main store. It also supports different unified commerce strategies, such as [ship from store](#ship-from-store), [physical stores as pickup points](#pickup-points), and [endless aisle](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+
+Other advantages of working with franchise accounts are listed below:
+
+- Exclusive accounts for each store, allowing better management of employee access.
+
+- Better management and resource scalability by adding loading docks and warehouses for each store.
+
+- Management of specific promotions per account without requesting a new [trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV).
+
+- Payment can be made in the main or franchise account environment ([split payment](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx)/order).
+
+- [Seller regionalization](https://help.vtex.com/en/tutorial/configure-seller-regionalization--32t6wLpQCEnumoh8TjT5fw) (price and inventory).
+
+- Increased operational performance by using multiple requests at the store checkout. In a standard account, where the [shipping strategy](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistics-required-settings) is added to the main account, requests are processed separately and queued, generating a potential backlog of requests and increased timeouts. Whenever a timeout occurs, an error message appears at checkout, and the customer has to click F5 or the refresh button to proceed with the purchase. This behavior has a negative impact on the customer experience and lowers the store's conversion rate.
+
+<div class="alert alert-warning">
+  <p><a href="https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">Franchise accounts</a> act as a <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a> for the main account. When a customer adds products to the shopping cart and simulates shipping on the main account's website, the <a href="https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">white label seller selection algorithm</a> automatically determines which franchise account will <a href="https://help.vtex.com/en/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP">fulfill</a> the order. If one or more products in the cart are unavailable in the selected franchise account, the system will select another available account to ship the unavailable products, allowing more than one shipment for the same order. This process occurs internally on the platform, and the customer doesn't know the sellers involved.</p>
+</div>
+
+## Ship from store
+
+Physical stores can act as mini distribution centers by shipping products directly from their warehouse to customers. This type of operation reduces shipping costs and time, improving the company's logistics planning. Learn more in the [Ship From Store](https://help.vtex.com/en/tracks/unified-commerce-strategies--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl) article.
+
+## Pickup points
+
+Configuring physical [pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R) contributes to operations that apply [unified commerce strategies](https://help.vtex.com/en/tracks/unified-commerce-strategies--3WGDRRhc3vf1MJb9zGncnv/2LGAiUnHES1enjHsfi8fI3). This approach optimizes the customer's buying experience by centralizing sales and order management, and offering multiple shipping options. On VTEX, you can add the following pickup points:
+
+- Distribution center (DC).
+- Proprietary physical store.
+- Franchised physical store.
+- Physical store or third-party pickup point, using a secure storage system such as a locker.
diff --git a/docs/tracks/en/unified-search.md b/docs/tracks/en/unified-search.md
index 0c7b7c665..1b2d69e64 100644
--- a/docs/tracks/en/unified-search.md
+++ b/docs/tracks/en/unified-search.md
@@ -1,10 +1,10 @@
 ---
-title: 'Unified search'
+title: 'Unified search in VTEX Sales App'
 id: 9sXeVwoD60qYYgRJ11r5F
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-08-05T13:47:18.180Z
-updatedAt: 2023-05-31T14:45:09.383Z
-publishedAt: 2023-05-31T14:45:09.383Z
+updatedAt: 2024-05-03T13:22:04.096Z
+publishedAt: 2024-05-03T12:35:21.520Z
 firstPublishedAt: 2021-08-05T14:45:51.056Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,33 +14,43 @@ trackId: 4BYzQIwyOHvnmnCYQgLzdr
 trackSlugEN: instore-using-the-app
 ---
 
-On VTEX Sales App's endless aisle, the sales associate can search for the desired products and add them to the cart. To do this, they must click on the magnifier on the top bar of VTEX Sales App and enter the product name, the reference code, or the EAN.
+VTEX Sales App's [endless aisle](https://help.vtex.com/en/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn) feature allows sales associates to search for products beyond the inventory of the current store and add them to the cart. To search for a product, click the magnifying glass icon <i class="fas fa-search"></i>, and a search bar will be displayed at the top of the store's homepage.  Enter the product name, reference code, SKU ID, or EAN.
 
-![instore-search-en](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/0fe42edc9020eeb5e15859c7e6e81425/instore-search-en.png)
+<div class = "alert alert-info">
+This feature uses the browser's cache to optimize searches in scenarios with slow internet connections.
+</div>
 
-VTEX Sales App has a unified search, which means that, when a sales associate searches for a product in the application, both the local inventory (of the physical store itself) and other physical stores and distribution centers associated with the ecommerce are included in the search.
+![Barra busca - EN](//images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/31aeb140714a23b6e5d0f958e90dcea2/Tela_1_barra_busca.gif)
 
-![instore-search-plp-en](https://images.ctfassets.net/alneenqid6w5/1WEugAiPUVHRVTL1ph3zv2/3564246537e995a74ecd15c3a6cfc8c8/instore-search-plp-en.png)
+VTEX Sales App features a unified search, which means that, when searching for a product in the app, search results will include not only the local inventory (of the current physical store) but also inventories of other physical stores and distribution centers associated with the ecommerce operation.
 
-By clicking the <i class="fas fa-chevron-down"></i> arrow next to a product, you can see its variations, delivery options, the quantity to be added to the cart, and the `Add to cart` and `More details` buttons.
+Search results are organized to improve customer experience, displaying images that facilitate product identification and providing relevant information for sales associates.
 
-![instore-search-details-en](https://images.ctfassets.net/alneenqid6w5/1itzXskqYPkJ4CghrWihy8/ee15e1947451b3ed68876643efd67569/instore-search-details-en.png)
+![Busca unificada - EN](//images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/89c5c59cc9e5ce4f86f3d97966439ed7/Busca_unificada_VTEX_Sales_App.png)
+
+When you click the `Add to Cart` option, the following product information will be displayed:
+- Product variations, SKUs.
+- Available shipping options.
+- Product quantity to be added to the cart.
+
+To add a product to the cart, select the desired variation, shipping option, and quantity, then click `Add to Cart`.
+
+![Carrinho - EN](//images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/4e2090b5e30f545a65f35c7faefd67ac/Adicionar_ao_carrinho_VTEX_Sales_App.png)
 
 ## Filters
 
-To use the search filters in VTEX Sales App, it is necessary to first install and configure [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). In this context, please note that:
+Filters allow the search to be refined based on customer preferences. You can refine your search by applying multiple filters and easily remove them if needed.
 
-* It is essential to configure the filters that will be displayed, as indicated in the article [Search configuration](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx). Otherwise, all product information will be considered as filterable attributes in VTEX Sales App.
-* The **Autocomplete** option does not apply to the VTEX Sales App search, so it can be left empty.
-* Any changes made to the search settings will also apply to the ecommerce if the tool used is VTEX Intelligent Search.
+To use search filters in VTEX Sales App, you must first install and configure [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Please keep in mind that:
+- It is essential to configure the filters that will be displayed, as indicated in the article [Search configuration](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx). Otherwise, all product information will be considered as filterable attributes in VTEX Sales App.
+- Any changes made to the search settings will also apply to the ecommerce operation if it uses VTEX Intelligent Search.
 
-In addition to configuring VTEX Intelligent Search, it is necessary to [contact VTEX support](https://support.vtex.com/hc/en-us/requests) to enable the filter feature in VTEX Sales App.
+In addition to configuring VTEX Intelligent Search, to enable the filter feature in VTEX Sales App, [contact VTEX support](https://support.vtex.com/hc/pt-br/requests).
 
-Once the filters are enabled, you can use this feature by following the process below when searching for products.
+Once the filters are enabled, you can use this feature by following the process below when searching for products:
 
-1. If you are using VTEX Sales App on a mobile device, such as a smartphone, click on `Filter search`. If you are using a device with a larger screen, skip this step.
+1. If you are using VTEX Sales App on a mobile device, such as a smartphone, click `Filters`.  If you are using a device with a larger screen, skip this step.
 2. Select the desired filters.
-3. Click on `Filter Search`.
-
-The results displayed will be filtered according to your preferences.
+3. Click `Filter`.
 
+The results displayed will be filtered based on your preferences.
diff --git a/docs/tracks/en/update-and-import-product-feed.md b/docs/tracks/en/update-and-import-product-feed.md
index c485c52e6..8c15d0739 100644
--- a/docs/tracks/en/update-and-import-product-feed.md
+++ b/docs/tracks/en/update-and-import-product-feed.md
@@ -23,6 +23,6 @@ http://{accountName}.myvtex.com/integration/lengow/feed
 
 Using the Lengow product feed URL you will now be able to import your products into a new Lengow catalogue using the direct link (HTTP/HTTPS) method.
 
-![Lengow - Import products](https://images.ctfassets.net/alneenqid6w5/67HpK4zsXv2GeqZZ3U99zj/c1472e7e7b92e1a41a7ee7e8a3a38422/image4.png)
+![Lengow - Import products](//images.ctfassets.net/alneenqid6w5/67HpK4zsXv2GeqZZ3U99zj/c1472e7e7b92e1a41a7ee7e8a3a38422/image4.png)
 
 For more information on how to publish your products on the channels of your choice, please refer to the how-to articles available in the Lengow Help Center.
diff --git a/docs/tracks/en/using-custom-controls.md b/docs/tracks/en/using-custom-controls.md
index ff235bbe5..245a18cc6 100644
--- a/docs/tracks/en/using-custom-controls.md
+++ b/docs/tracks/en/using-custom-controls.md
@@ -32,7 +32,7 @@ To create a custom control, follow the walk-through below:
 3. Click on the __CMS__ folder.
 4. Click on the __Custom Elements__ folder.
 5. Click on the __Add__ button.
-![8 1](https://images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
+![8 1](//images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
 6. Fill in the __Name__ field with the custom control name.
 7. Fill in the __Tag name__ field. This is the name that will be used in the control when adding it to the template.
 8. Select the control type on __Type__.
diff --git a/docs/tracks/en/via-varejo-marketplace.md b/docs/tracks/en/via-varejo-marketplace.md
index 483090418..339e40be7 100644
--- a/docs/tracks/en/via-varejo-marketplace.md
+++ b/docs/tracks/en/via-varejo-marketplace.md
@@ -1,10 +1,10 @@
 ---
-title: 'Via Marketplace'
+title: 'Casas Bahia Marketplace'
 id: 3rymwJDuc5Z6lQtsyTINim
 status: PUBLISHED
 createdAt: 2020-03-30T17:59:31.535Z
-updatedAt: 2022-01-18T21:38:11.833Z
-publishedAt: 2022-01-18T21:38:11.833Z
+updatedAt: 2023-11-30T20:51:57.221Z
+publishedAt: 2023-11-30T20:51:57.221Z
 firstPublishedAt: 2020-03-30T18:11:59.947Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/viewing-the-email-history-of-an-order.md b/docs/tracks/en/viewing-the-email-history-of-an-order.md
index 9f84f977f..8efa1e2b2 100644
--- a/docs/tracks/en/viewing-the-email-history-of-an-order.md
+++ b/docs/tracks/en/viewing-the-email-history-of-an-order.md
@@ -3,8 +3,8 @@ title: 'Viewing the email history of an order'
 id: 13YJE9CKzeduRfVplgjC88
 status: PUBLISHED
 createdAt: 2020-01-10T14:07:26.022Z
-updatedAt: 2023-03-31T21:10:54.264Z
-publishedAt: 2023-03-31T21:10:54.264Z
+updatedAt: 2023-09-23T00:49:55.012Z
+publishedAt: 2023-09-23T00:49:55.012Z
 firstPublishedAt: 2020-01-13T14:38:41.810Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -21,3 +21,7 @@ This feature is useful for tracking all email communication with the customer th
 To see email history, go to the **Orders** module, enter the desired order and scroll down to the timeline. There you will find the records of emails sent.
 
 This record is made by a system called __Conversation Tracker__. To get a deeper understanding of how it works, see our article on [communication with the client during the order flow](https://help.vtex.com/en/tutorial/understanding-the-conversation-tracker--tutorials_195).
+
+<div class = "alert alert-info">
+Since the communication with customers is a responsibility from marketplaces, only orders with marketplace origin keep a transactional emails history. Orders with fulfilllment origin do not keep a register of transactional emails.
+</div>
diff --git a/docs/tracks/en/vtex-modules-i.md b/docs/tracks/en/vtex-modules-i.md
new file mode 100644
index 000000000..b132707b0
--- /dev/null
+++ b/docs/tracks/en/vtex-modules-i.md
@@ -0,0 +1,355 @@
+---
+title: 'VTEX modules I'
+id: 75MX4aorniD0BYAB8Nwbo7
+status: PUBLISHED
+createdAt: 2024-01-17T19:53:53.326Z
+updatedAt: 2024-02-23T00:42:01.506Z
+publishedAt: 2024-02-23T00:42:01.506Z
+firstPublishedAt: 2024-02-22T14:07:05.427Z
+contentType: trackArticle
+productTeam: Others
+slug: vtex-modules-i
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+The VTEX platform is structured in modules for each part of the store's operation. This article provides an overview and describes the main settings of the following modules:
+
+- [Catalog](#catalog)
+- [Prices](#prices)
+- [Promotions](#promotions)
+- [Logistics](#logistics)
+
+<div class="alert alert-info">
+The <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ">VTEX modules II</a> article describes the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments">Payments</a>, <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#orders">Orders</a>, and <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout">Checkout</a> modules.
+</div>
+
+## Catalog
+
+[Catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) is the VTEX module where merchants configure their products to make them available in the store. The catalog structure defines the customers' experience when navigating the product categories in the store. Check out the [Catalog](https://developers.vtex.com/docs/guides/catalog-overview) guide for an [overview](https://help.vtex.com/en/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe) of the [Catalog API](https://developers.vtex.com/docs/guides/catalog-overview) for developers.
+
+### Before you begin with Catalog
+
+There are no prior settings to make before configuring the Catalog, but the following should be noted:
+
+- __Customer navigation on the site__: You need to plan how you want to arrange your [category tree](#category-tree) and know in advance what browsing experience you want to offer to customers in the category hierarchy.
+- __Making products available to customers__: To [make a product available in the store](https://help.vtex.com/en/faq/why-is-the-product-not-visible-on-the-website--frequentlyAskedQuestions_382), after the Catalog settings, you must add a [price](#prices) and shipping [logistics](#logistics) to the SKU. Also, the store's CMS must be correctly configured.
+
+### Catalog architecture
+
+The Catalog architecture has some key concepts: category, brand, product, SKU (_Stock Keeping Unit_) and specification. The image below shows the relation between these concepts:
+
+![arquitetura-catalogo-EN](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
+
+The store catalog must be created following the steps below:
+
+1. Create a [category tree](#category-tree).
+2. Add [brands](#brands).
+3. Add [specifications](#specifications).
+4. Import [produts](#products).
+5. Import [SKUs](#skus).
+
+The following table shows the store's main Catalog settings based on their creation order:
+
+| **Topic** | **Configuration via VTEX Admin** | **Configuration via API** |
+| :--- | :--- | :--- |
+| 1. [Category tree](https://help.vtex.com/en/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categories) | [Add a category](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206) | - [Categories](https://developers.vtex.com/docs/guides/categories) <br> - [Create Category](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category) |
+| 2. [Brands](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) | [Add brands](https://help.vtex.com/en/tutorial/registering-brands--tutorials_1414) | - [Brands](https://developers.vtex.com/docs/guides/brands) <br> - [Create Brand](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand) |
+| 3.1. [Product specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#product-specification) | [Add product specifications or fields](https://help.vtex.com/en/tutorial/adding-specifications-or-product-fields--tutorials_106) | - [Product specifications](https://developers.vtex.com/docs/guides/product-specifications) <br> - [Create Specification](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/specification) |
+| 3.2. [SKU specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#sku-specifications) | [Add SKU specifications or fields](https://help.vtex.com/en/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119) | - [SKU specifications](https://help.vtex.com/en/tutorial/adding-sku-specifications-or-fields--tutorials_119) <br> - [Create Specification](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/specification) |
+| 4. [Products](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) | [Add products](https://help.vtex.com/en/tutorial/cadastrando-produtos--tutorials_2567) | - [Products](https://help.vtex.com/en/tutorial/adding-products--tutorials_2567) <br> - [Create Product with Category and Brand](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product) |
+| 5. [SKUs](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) | [Complete the SKU fields](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY) | - [SKUs](https://developers.vtex.com/docs/guides/skus) <br> - [Create SKU](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit) |
+
+<br>
+
+<div class="alert alert-warning">
+To learn how to import products from an ERP (Enterprise Resource Planning) or PIM (Product Information Manager) system to the VTEX platform, read the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
+</div>
+
+#### Category tree
+
+The [category tree](https://help.vtex.com/en/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categories) defines the Catalog's basic structure. The categories act as hierarchical levels for classifying products, which simplify the customer's search and keep the store's catalog organized.
+
+We recommend creating a three-level hierarchy, including [Departaments](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf#department), [Categories](https://help.vtex.com/en/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categories) and [Subcategorias](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf#subcategory). However, some stores may benefit from a two-level structure with Departments and Categories. This depends on the operation's complexity and the types of products offered.
+
+__Example__: Department `Women`, Category `Shirts and T-shirts`, and Sub-category `T-shirts`.
+
+Before importing the store catalog to VTEX, we recommend that you start working on the category tree by creating a table such as the one below. This allows you to better view the tree's organization and the display of specifications.
+
+![catalog_arquitecture_table_EN](//images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/f539ab283449f2aa2163be8b8ddd957e/catalog_arquitecture_table_EN.png)
+
+<div class="alert alert-info">
+For more information on how to import back-office specifications, read the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
+</div>
+
+#### Brands
+
+[Brands](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) generally refer to the company that manufactures or resells the products. On VTEX, brands must be created independently, and when creating a product, it must be associated with a brand already listed in the store.
+
+#### Specifications
+
+[Specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) are additional properties that can be added to the products and SKUs, such as size, color, voltage, or material. In other words, there are [product specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#product-specification) and [SKU specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#sku-specifications).
+
+In the VTEX __Catalog__, specifications are created as follows:
+
+1. __Specification groups__: These are specification field groups. They must be linked to categories. Usually, only one group is created at the root level, and all the specification fields are associated with this group.
+2. __Specification fields__: Fields with additional product and SKU information. They must be linked to categories and specification groups.
+3. __Specification values__: Values you can choose to add to the specification fields.
+
+The specifications follow the Catalog hierarchy, so when one of these groups is created in a Department or Category, it follows the levels below.
+
+#### Products
+
+[Products](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) is the level of catalog organization that is located in the hierarchy below Categories and above SKUs. As the product is above the SKU in the catalog hierarchy, we can understand it as a generic definition of the items sold in your store. A product must have at least one SKU associated with it.
+
+#### SKUs
+
+[SKU](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) (_Stock Keeping Unit_) is a product variation and represents the physical unit in stock that can be purchased by the customer. The SKU is the last level in the catalog organization, and in order to be active, the SKU must have an image and specifications.
+
+### Optional Catalog settings
+
+The following table shows optional Catalog settings on VTEX:
+
+| **Feature** | **Description** | **Learn more** |
+| :---: | :--- | :--- |
+| Collections | A collection is a combination of two or more products that may or may not share specific characteristics. <br> Collections can be created to associate products based on different criteria, such as commemorative dates, launches, or best-selling products. | __Help Center__ <br> - [Collections - Concept definition](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/4hN41yU8IPeb8HKmmaXoca) <br> - [Creating Collections (Beta)](https://help.vtex.com/en/tutorial/creating-collections-beta--yJBHqNMViOAnnnq4fyOye)  <br> __Developer Portal__  <br> - [Create Collection](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection/) <br> - [Get All Inactive Collections](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/collection/inactive) <br> - [Get All Collections](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/collection/search) <br> - [Get Collections by search terms](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/collection/search/-searchTerms-) <br> - [Import File Example](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/collection/stockkeepingunit/importfileexample) <br> - [Add products to Collection by imported file](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection/-collectionId-/stockkeepingunit/importinsert) |
+| Attachments | An attachment is an optional and free product customization used to add information to a SKU. | __Help Center__ <br> - [Adding an attachment](https://help.vtex.com/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU) <br> - [How to create a subscription attachment](https://help.vtex.com/en/tutorial/how-to-create-a-subscription-attachment--2bUuKyPflA8cOGLv8OvaKK) <br> - [What is an Attachment?](https://help.vtex.com/en/tutorial/what-is-an-attachment--aGICk0RVbqKg6GYmQcWUm)  <br> __Developer Portal__ <br> - [Catalog API - Attachment](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/attachment/-attachmentid-) <br> - [Catalog API - SKU attachment](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuattachment) |
+| Assembly Options | Assembly Options are a type of attachment for complex cases, such as product customization, in which you can manage different combinations of products, quantity, additional items, costs, and inventory. Then, you will be able to display these options on the product page. | __Developer Portal__ <br> - [Assembly Options](https://help.vtex.com/en/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH) <br> - [Assembly Option App](https://developers.vtex.com/docs/guides/assembly-options-app) |
+| Services | Service with extra cost, offered optionally with a product. It is used to add an additional service to an SKU, such as gift wrapping, customization, or special warranty agreements. | __Help Center__ <br> - [What is a Service?](https://help.vtex.com/en/tutorial/what-is-a-service--46Ha8CEEQoC6Y40i6akG0y) <br> - [Service Management](https://help.vtex.com/en/tutorial/service-management--3sGqSI93t878ETAWzCZ0E2) <br> - [Services Import](https://help.vtex.com/en/tutorial/services-import--2LRgMnGbX0af7krrs6tXy3) <br> - [Services Report](https://help.vtex.com/en/tutorial/services-report--7djPWfxtf9qb6hFTOgKDE8) <br> - [Services scheduling](https://help.vtex.com/en/tutorial/services-scheduling--78HPYBxDCmpCfa8i40zo7R)  <br> __Developer Portal__ <br> - [Catalog API - SKU service](https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/skuservice/-skuServiceId-) <br> - [Catalog API - SKU service attachment](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicetypeattachment) <br> - [Catalog API - SKU service type](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicetype) <br> - [Catalog API - SKU service value](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicevalue) |
+| Kits | A kit is a set of SKUs sold together, i.e., an SKU consisting of one or more SKUs. | __Help Center__ <br> - [What is a kit?](https://help.vtex.com/en/tutorial/what-is-a-kit--5ov5s3eHM4AqAAgqWwoc28) <br> - [Kit registration](https://help.vtex.com/en/tutorial/kit-registration--tutorials_215) <br> __Developer Portal__ <br> - [Catalog API - SKU Kit](https://developers.vtex.com/vtex-rest-api/reference/catalog-api-get-sku-kit) |
+
+## Prices
+
+[Prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu) is the VTEX module for creating, editing, and storing price details for the store's SKUs. For a product to be sold, the customer needs to know the price of each item displayed in the store. The pricing module has features that allow you to use different pricing strategies in your business.
+
+###  Before you begin with Prices
+
+Before configuring the store's prices, you need to create a [catalog](#catalog) with your products. The store catalog must contain [categories](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206), [brands](https://help.vtex.com/en/tutorial/registering-brands--tutorials_1414), [products](https://help.vtex.com/en/tutorial/adding-products--tutorials_2567) and [SKUs](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY) already added and active. If the catalog was created via [ntegration with an ERP system](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#erp-integration), you should check the information before proceeding.
+
+### How the Prices module works
+
+It is important to familiarize yourself with the main terms related to the module. These terms are outlined in the table below:
+
+| **Term** | **Definition** |
+| :---: | :--- |
+| Prices | Information on the sales values of the store's SKUs. |
+| [Price tables](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) | Set of SKU prices that can be applied to a given context, such as a [trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV). These tables contain the price information displayed on the store's storefront. |
+| Cost price | Price paid by the store when purchasing the SKU. |
+| Markup | The store's desired profit margin from selling the SKU. |
+| [Base price](hhttps://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) | Amount calculated by combining the __cost price__ and the __markup__. This is the SKU's reference price for all price tables. |
+| [List price](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#list-price) | Suggested selling price for an SKU. This price will be displayed on the product page as the __From__ price, while the base price will be displayed as the __To__ price. |
+| [Price rule](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/2rBirbpB7wLnei4dQ9KGMW) | Changes the SKU price on a specific price table without changing the base price on other tables. To do so, you need to create a price rule and associate it with the desired table. |
+| [Fixed price](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy) | Price that overrides all other price settings in a price table. |
+| [Price rounding](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/1tUIUvF6BUkDgMsknGaMkF) | A pricing strategy based on price rounding. This method aims to influence the consumer's purchasing decision by displaying prices in a more user-friendly and intuitive format. |
+| [Price variation limiter](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/7JZhLmI3mjBVu0RMOueoy3) | Sets the maximum and minimum price variations for an item. This feature ensures that SKU prices are not changed to undesirable values. |
+
+For more information on pricing architecture, read the [Pricing System Architecture](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) article.
+
+### Creating price tables
+
+The Pricing module's architecture is structured based on three key concepts:
+
+- Prices
+- Price tables
+- Contexts for applying price tables
+
+Prices are the sales value information for your SKUs. These prices are stored in price tables, which can be applied to different contexts.
+
+The image below illustrates the relationship between prices, the price table, and the context in which they will be applied:
+
+![Conceito de Preços-EN](//images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/c229973cb7f6f135570b309d23af10a3/Conceito_de_Pre_os-EN.png)
+
+You can create price tables for your SKUs in three ways:
+
+- [Via Admin VTEX](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/2WQ3pVYfQpXkJnHr7VTFBv#admin)
+- [Via spreadsheet](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D)
+- [Via API](https://developers.vtex.com/docs/api-reference/pricing-api)
+
+Prices can be scheduled for special events, as described in the [Scheduling prices](https://help.vtex.com/en/tutorial/agendar-preco--4vVha6TGzYkguWuMOqCcCk) article.
+
+### Relationship between price tables and trade policies
+
+There is a difference between price tables created for [trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) and price tables created for other contexts.
+
+Price tables not associated with trade policies can be used in contexts such as __promotions__ and __customer clusters__. Tables created for trade policies can only be associated with the trade policy itself. Thus, the price table associated with a trade policy shows the SKU price specific to that policy and cannot be associated with other contexts.
+
+<div class="alert alert-warning">
+The concepts of <b>price table</b> and <a href="LINK">trade policy</a> are different. Trade policy is the context with which a price list is associated.
+</div>
+
+When setting up a trade policy, you must [specify the currency that will be used in the store](https://help.vtex.com/en/tutorial/creating-a-trade-policy--563tbcL0TYKEKeOY4IAgAE). Creating different trade policies associated with a different currency allows the store to display prices in different currencies to customers. 
+
+## Promotions
+
+On VTEX, the merchant can create a set of rules to indicate if customers can have discounts applied to certain shopping contexts. [Promotions](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N) is the VTEX module for creating, editing, and applying discounts to customers' shopping carts.
+
+### Before you begin with Promotions
+
+Before configuring your store's promotions, you must create a [Catalog](https://help.vtex.com/en/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe) with your products and enter the [prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu) of the store's SKUs.
+
+### How the Promotions module works
+
+In this context, it is important to be familiar with the main terms related to the module. These terms are outlined in the table below:
+
+| **Term** | **Definition** |
+| :---: | :--- |
+| Promotion | Discount given to customers, which can be linked to one or more products in the cart, to shipping or a gift. |
+| Coupon | Promotional code consisting of a sequence of letters and numbers. Coupons are associated with promotions applied to the cart total amount. Thus, by entering a valid coupon at checkout, the customer can get discounts on the order total amount. |
+| Campaign audience | Campaign audience is a feature that allows you to define the [target audience](https://help.vtex.com/en/tutorial/audiencias-de-campanhas--3o7lhpNseXY2WmjZO0gQ6m#target-audience) or a promotion. It consists of setting up criteria to segment customers from which the VTEX platform automatically validates whether customers are eligible for a particular campaign audience and, consequently, for the associated [campaign promotions](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume). |
+| Campaign promotion | A campaign promotion is always linked to a campaign audience, i.e., a specific target audience. This type of promotion will only be applied to the target audience of the campaign. |
+
+### Creating promotions
+
+On VTEX, merchants can create rules that determine the application of discounts based on the purchase context. These rules take into account various parameters, including product lists, customer lists, postal code ranges, minimum value of items in the cart, and others.
+
+Discounts can be of two main types:
+
+- __Nominal__: Discount of the gross amount, such as $20.
+- __Percentage__: Discount of a percentage value, such as 10% of the total amount of the cart.
+
+There are six types of promotion, each related to a different scenario:
+
+| **Promotion type** | **Definition** |
+| :---: | :--- |
+| [Regular Promotion](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) | Promotion that allows the store to offer flexible discounts, combining multiple conditions, restrictions, and benefits. |
+| [Buy Together](https://help.vtex.com/en/tutorial/buy-together--tutorials_323) | Promotion used to give a discount on products added together in the cart. The discount can be applied to both products. There's also the option to only apply the discount if a specific quantity of one of the product is added to the cart. |
+| [More for Less](https://help.vtex.com/en/tutorial/creating-a-more-for-less-promotion--tutorials_325) | Promotion used to give a discount when the customer adds multiple units of the same product to the cart. |
+| [Progressive Discount](https://help.vtex.com/en/tutorial/progressive-discount--tutorials_324) | Promotion used when you want to offer a percentage discount for a specific number of products in the cart. |
+| [Buy One Get One](https://help.vtex.com/en/tutorial/buy-one-get-one--tutorials_322) | Promotion used to provide free shipping or a giveaway when a specific product is purchased. |
+| [Campaign Promotion](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume) | A campaign promotion is always linked to a campaign audience, i.e., a specific target audience. |
+
+For all promotions, you can define their duration, restrictions, and limitations on usage. Promotions can also be scheduled for special events, as described in the [Scheduling features for special events](https://help.vtex.com/en/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI#scheduling-promotions) article.
+
+For more information on how promotions can be applied, read the [Promotion examples](https://help.vtex.com/en/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD) article.
+
+### Creating coupons
+
+You can create discount coupons through the [VTEX Admin](https://help.vtex.com/en/tutorial/creating-a-coupon-beta--7lMk3MmhNp2IEccyGApxU) ou via [API](https://developers.vtex.com/docs/guides/creating-and-managing-coupons-with-promotions-api). A coupon must be linked to at least one promotion to be applicable. 
+
+<div class="alert alert-warning">
+There is a maximum number of active coupons. We strongly recommend reusing coupons, as a large number of coupons can compromise the performance of the Promotions module.
+</div>
+
+### Criar promoções de campanha
+
+Creating campaign promotions [campaign audience](https://help.vtex.com/en/tutorial/creating-a-campaign-audience--6cnuDZJzIkIeocewAQQK4K) to set the promotion's target audience. You can then choose eligible customer segments for the promotion. These segments act as a trigger based on criteria defined by the merchant.
+
+Once the campaign audience has been created, it needs to be linked to a [Regular Promotion](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), thus creating a campaign promotion. This type of promotion encompasses all the possibilities available in the [Regular Promotion](hhttps://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) and a few more options:
+
+- Specific target audience.
+- Free shipping for all available shipping options.
+- Promotional price table.
+- Giveaways delivered by sellers.
+
+### Highlighting promotions on the product page
+
+You can highlight a promotion on the product page (PDP). To do so, follow the steps below:
+
+1. [Create a promotion](https://help.vtex.com/en/tutorial/lista-de-promocoes-beta--4yB7nNdliiFxBTXE19GCIi#creating-promotions) of any type, except for the Buy Together promotion.
+2. Activate the __Promotion is highlighted__ field in the promotion form.
+3. Save the promotion.
+4. In the [Legacy CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj), enter the promotion display control in the template: `<vtex.cmc:discountHightLight/>`. 
+
+### Syncing promotion dates, banners, and digital assets
+
+Ensure that you sync your promotion timeline with the delivery dates on your banners and digital assets to ensure perfect coordination. To do so, you should check the dates on both promotions and banners. This strategic alignment ensures that promotional campaigns are supported by relevant visual materials, maximizing their impact and effectiveness.
+
+## Logistics
+
+On VTEX, the [Logistics](https://help.vtex.com/en/tracks/logistics-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a) module is responsible for the store's [logistics and order fulfillment](https://help.vtex.com/en/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP). It includes planning, transportation, storage, and shipping orders to customers.
+
+### Before you begin with Logistics
+
+To configure the logistics settings, you must have completed the following steps:
+
+- __Creating catalog__: As the order fulfillment is related to storing items, the store's products and SKUs must be listed in the [Catalog](#catalog).
+- __Configuring trade policies__: [Trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) shape the customer experience on a store's website. They encompass sales conditions for each audience, the products offered, pricing, promotions, and shipping methods.
+
+Besides, if the business model includes international stores and [cross-border](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs) sales, you should first consider the [store's architectural](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#store-architecture) model.
+
+### Logistics required settings
+
+The set of essential logistics settings for a VTEX store is called [Shipping Strategy](https://help.vtex.com/en/tutorial/shipping-strategy--58vLBDbjYVQzJ6rRc5QNz3) and consists of three main concepts: shipping policy, warehouse, and loading dock.
+
+- __[Shipping policy](#shipping-policy)__: set of rules that define the order's shipping options and conditions.
+- __[Warehouse](#warehouse)__: physical storage space for the products to be sold.
+- __[Loading dock](#loading-dock)__: distribution location for the items to be sold.
+
+The image below shows how these concepts relate to each other when selling a product:
+
+![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
+
+The following table shows the store's main logistics settings on VTEX:
+
+<div class="alert alert-INFO">
+We recommend configuring the warehouse first, followed by the loading dock, and then the shipping policy.
+</div>
+
+| **Topic** | **Configuration via VTEX Admin** | **Configuration via API** |
+| :---: | :--- | :--- |
+| [Warehouse](#warehouse) | [Managing Warehouses](https://help.vtex.com/en/tutorial/managing-warehouses--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| [Loading dock](#loading-dock) | [Managing Loading Docks](https://help.vtex.com/en/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
+| [Shipping policy](#shipping-policy) | [Shipping Policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| [Inventory](#inventory-management) | [Inventory Management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) | [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-) |
+
+#### Warehouse
+
+The logistics route starts with the [warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb). It corresponds to the physical storage space for the products the store sells. Once the items sold are picked from the warehouse, they are sent to the loading dock.
+
+#### Loading dock
+
+The [loading dock](https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj) is where items are distributed and shipped from and is the intermediate step between the warehouse and the carriers. The loading dock integrates the warehouse, trade policy, and shipping policy. Some use cases are:
+
+- Different distribution centers for a single warehouse.
+- Loading dock as a distribution center.
+- Loading dock and warehouse correspond to the same physical space.
+
+For certain products, you may not need a physical distribution center. Even so, configuring the loading dock is essential for the proper functioning of the VTEX platform's operations.
+
+#### Shipping policy
+
+[Shipping policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140) is a set of rules that define the shipping options and conditions that will be displayed to customers at checkout. These conditions include carriers, delivery times, shipping costs, etc. The shipping policy is linked to the warehouse by the loading dock.
+
+The [carrier](https://help.vtex.com/en/tutorial/carries-on-vtex--7u9duMD5UQa2QQwukAWMcE) delivering the order is defined via the shipping policy. First, carriers are added to the [shipping rate template](https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127), then the shipping rate template is associated when a shipping policy is created.
+
+### Inventory management
+
+Store [inventory](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) corresponds to the stored items available for sale. Warehouse is the identification of the physical location of storage location, while inventory is the set of SKUs in stock that are available for sale.
+
+<div class="alert alert-danger">
+On VTEX, the store must manage inventory updates after selling items. Thus, after a sale, the merchant ensures proper control of the remaining items and invoice operations with ERP. Information on inventory import via the back office can be found in the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
+</div>
+
+### Lead time
+
+In the VTEX Admin, under __Catalog > Inventory > Inventory Management__, existe you can configure the [Lead time](https://help.vtex.com/en/tutorial/lead-time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B), an optional setting that allows you to assign a shipping time at SKU level.  Configuring the lead time means adding a period of time to the order shipping [calculation](#order-shipping-calculation) which is strategic in some contexts.
+
+The [main use cases](https://help.vtex.com/en/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#main-use-cases), include products from external suppliers, _dropshipping_ scenarios, and the sale of custom items. Having the option to configure the lead time means having more flexibility to set deadlines for handling and shipping products by third parties.
+
+### Order shipping calculation
+
+The VTEX platform considers the following settings to [calculate the order shipping time](https://help.vtex.com/en/tutorial/how-shipping-calculation-works--tutorials_116):
+
+![Shipping Calculation_EN](//images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/7088aadd2ae56175b3a9b57ae0af38a8/Shipping_Calculation_EN.png)
+
+- [Lead time](https://help.vtex.com/en/tutorial/lead-time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B): Configurable amount of time for an SKU in stock. This configuration is optional and is set to zero days by default.
+- [Warehouse time](https://help.vtex.com/en/tutorial/managing-warehouses--tutorials_137): time it takes for an SKU to move from a warehouse to a [loading dock](https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj). This configuration is required, but you can set the time to zero.
+- [Loading dock time](https://help.vtex.com/en/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW): time it takes for an SKU to leave the dock and be shipped to the customer. This configuration is required, but you can set the time to zero.
+- [Shipping policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140): groups together the shipping rules and conditions displayed to customers at checkout, including carriers, shipping costs, carrier business hours, delivery windows, and delivery capacity.
+
+The [shipping simulator](https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144) allows merchants to simulate and analyze the delivery options available for an order in a given location. The simulation checks the viability and shipping conditions of the order, such as item availability, shipping methods, costs, and shipping time.
+
+### Logistics optional settings
+
+To serve different business models, the VTEX platform offers many optional settings, as shown in the table below:
+
+| **Feature** | **Description** |
+| :---: | :--- |
+| Pickup points | [Pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R) are physical locations set up by the store for customers to pick up their orders. Setting up pickup points is interesting for omnichannel operations, especially when there are many physical stores, as each can be used as a pickup option for customers, increasing the flexibility of your logistics network. |
+| Holidays | [Holidays](https://help.vtex.com/en/tutorial/registering-holidays--2ItOthSEAoyAmcwsuiO6Yk) is a feature that allows the store to set up days that are not valid for shipping, which will be considered when calculating the order's shipping time. |
+| Reservation | [Reservation](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92) is a solution that prevents the same item from being sold more than once. When the customer only adds the product to the cart, this does not generate a reservation; your priority over the item only occurs once the order has been placed. |
+| Delivery capacity | [Delivery capacity](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi#delivery-capacity) is the limit of shipments that can be made by the store in a given period. Being able to delimit the number of items or orders that can be shipped in each shipping window means having more control over order handling and increasing the chances of fulfilling the delivery agreement made with the customer at checkout. |
+| Geolocation | [Geolocation](https://help.vtex.com/en/tutorial/registering-geolocation--tutorials_138) involves adding delivery locations based on the latitude and longitude of addresses. This feature is often used for addresses in rural and industrial areas, which are divided into lots or risk areas, and when it's necessary to remove certain delivery locations within a region. |
+
+For more information on logistics concepts on VTEX, read the [Logistics Glossary](https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby) article. For developer content on the [Logistics API](https://developers.vtex.com/docs/api-reference/logistics-api#overview), read the  [Fulfillment and Logistics](https://developers.vtex.com/docs/guides/fulfillment) article.
diff --git a/docs/tracks/en/vtex-modules-ii.md b/docs/tracks/en/vtex-modules-ii.md
new file mode 100644
index 000000000..875034a38
--- /dev/null
+++ b/docs/tracks/en/vtex-modules-ii.md
@@ -0,0 +1,299 @@
+---
+title: 'VTEX Modules II'
+id: 3MYcZaojb5HSUg6ufm6GxQ
+status: CHANGED
+createdAt: 2024-02-07T13:20:33.477Z
+updatedAt: 2024-02-22T17:08:09.649Z
+publishedAt: 2024-02-22T14:07:12.569Z
+firstPublishedAt: 2024-02-22T14:07:12.569Z
+contentType: trackArticle
+productTeam: Others
+slug: vtex-modules-ii
+locale: en
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugEN: vtex-store-overview
+---
+
+In addition to the modules covered in the previous article, such as [Catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog), [Prices](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices), [Promotions](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promotions), and [Logistics](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistics), the VTEX platform has other modules that are essential for the store's operation. This article presents an overview and the main settings for the following modules:
+
+- [Payments](#payments)
+- [Orders](#orders)
+- [Checkout](#checkout)
+
+## Payments
+
+The [Payments](https://help.vtex.com/en/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB) module on VTEX is where you can manage all the financial operations of a store. It allows you to determine the payment providers, methods, and conditions that will be offered to customers at checkout and check payment transaction details for each order.
+
+### Before you begin with Payments
+
+To process and receive payments for purchases in a VTEX store, you need to have a service agreement with one or more payment providers. These agreements are established directly between the merchant and the provider, without mediation or participation from VTEX. To view available providers on VTEX in each country, check the [List of Payment Providers by Country](https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp).
+
+<div class="alert alert-warning">
+We recommend integrating multiple payment providers in your store to enhance customer experience by offering a variety of payment methods and conditions. This approach also allows operating with diverse rates and costs, thereby improving business performance.
+</div>
+
+The payment settings described in this track can be configured at any time during the onboarding process. However, for the store to be able to process any type of payment transaction, the [Catalog](https://help.vtex.com/en/tracks/track-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog), [Pricing](https://help.vtex.com/en/tracks/track-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices), and [Logistics](https://help.vtex.com/en/tracks/track-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistic) modules must have been configured beforehand.
+
+### How the Payments module works
+
+The table below shows the main agents and terms used in the Payments context:
+
+| **Term** | **Description** |
+| :---: | :--- |
+| **Gateway**  | System that processes order payment information during checkout. | 
+| **Acquirer** | Company that processes credit and debit card payments. |
+| **Subacquirer** | Company that handles payments and acts as an intermediary between acquirers, anti-fraud providers, and merchants.|
+| **Card brand** | Company that defines business rules for credit and debit cards. |
+| **Issuing bank** | Financial institution that authorizes a payment method, such as credit or debit card. |
+| **Payment provider** | Company that offers support for electronic transactions across various payment methods. |
+| **Anti-fraud provider** | Company that conducts risk analysis on credit and debit card transactions. |
+| **Payment Provider Protocol** | Protocol used by payment or anti-fraud providers to transmit payment data. Learn more about how providers integrate with VTEX in [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). |
+| **Payment method** | Methods available to customers when paying for their orders, such as credit cards, debit cards, and digital wallets. |
+| **Payment condition** | Rules established for a specific payment method, e.g., the maximum number of installments allowed and applicable interest. |
+
+### Payment and transaction flows
+
+When a purchase is completed on VTEX, a new transaction is created and the payment flow begins. In the example below, you can see the payment flow for a credit card purchase:
+
+![payments-en](//images.ctfassets.net/alneenqid6w5/6rqeRDDqm3rijRrwpG6Lb1/8df497f70d26352352a11d942887afa7/payments_image1_EN__1_.JPG)
+
+As the data is transferred among the agents responsible for data processing, the payment transaction status is updated to reflect the current stage of the resources in the flow. In the credit card payment flow, we can consider the following example of transaction statuses:
+
+![payments-flow-en](//images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/14fa9b346e6a041fa934f2cfa9d94ace/payments_image2_ALL.JPG)
+
+### Configuring payments in your store
+
+Once you have agreements in place with the payment providers, you need to configure the respective connector for each one and define the available payment methods and conditions that will be offered at the store's checkout.
+
+#### Enabling a payment provider
+
+Payment providers must be enabled in a store to transmit and receive the information required to complete a payment transaction. Follow the steps below to enable each provider:
+
+1. Access the [List of Payment Providers by Country](https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp).
+2. Select the desired provider by clicking the corresponding link in the table.
+3. Go to the VTEX Admin to configure the provider and follow the instructions listed in the specific configuration article.
+
+<div class = "alert alert-info">
+You can also find provider configuration articles by entering the name of the provider in the search bar of the <a href="https://help.vtex.com/en">Help Center</a>.
+</div>
+
+#### Defining payment methods and payment conditions
+
+After enabling the payment provider, you need to configure the payment methods and terms to be processed by the provider. To do this, follow the steps below:
+
+1. In the VTEX Admin, go to **Store Settings > Payment > Settings**, or type **Settings** in the search bar at the top of the page.
+2. On the **Payment Conditions** tab, click the **+** button.
+3. Click the desired payment method.
+4. If you want, you can change the name of the payment method in the **Condition name** field.
+5. Activate the **Status** toggle switch.
+6. In **Process with provider**, select the name of the payment provider.
+7. If you want to use an anti-fraud system, check the option **Use anti-fraud solution**. Learn more in [Configuring an anti-fraud provider (optional)](#setting-up-an-anti-fraud-provider).
+8. If the chosen payment method allows you to set up payments in installments, select the **In installments** option under **Paid in full or in installments?** and enter the desired information. Learn more in [Configuring payment terms](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455).
+9. If you want, you can also set up special payment conditions. Learn more in [Adding special payment conditions](#adding-special-payment-conditions).
+10. Click `Save`.
+
+### Optional Payments settings
+
+Depending on the store's operating profile, you can also configure the following optional payment settings:
+
+- [Add special payment conditions](#adding-special-payment-conditions)
+- [Configure custom payment methods](#configuring-custom-payment-methods)
+- [Set up an anti-fraud provider](#setting-up-an-anti-fraud-provider)
+- [Create gift cards](#creating-gift-cards)           
+- [Enable digital wallets](#enabling-digital-wallets)
+- [Customer Credit](#customer-credit)
+
+#### Adding special payment conditions
+
+Special payment conditions allow you to define specific rules for a given payment method, such as expiration date, issuing bank, trade policy, commercial condition, and account name.
+
+For more details on each type of special payment condition, check the [Configuring special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456) article.
+
+#### Configuring custom payment methods
+
+On VTEX, you can configure the following custom payment methods:
+
+- **Notes payable**: Payment commitment between the merchant and the customer for the purchase amount. Manual approval by the merchant is required to approve the purchase transaction. Learn more in [Setting up payments with Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ).
+
+- **Store cards (private label)**: Credit or debit cards issued through a partnership between a company and a card label, such as Visa or Mastercard. These cards can only be used for purchases at establishments that accept the card issuer's label. Learn more in [Setting up Private Label payments](https://help.vtex.com/en/tutorial/setting-up-private-label-payments--428FgVdSGQUeAOoogkaIw4).
+
+- **Store cards (co-branded)**: Credit or debit cards that are branded with a company's own name, issued exclusively for purchases made at the establishments of the card-issuing company. Learn more in [Setting up payments with Store Card (cobranded)](https://help.vtex.com/en/tutorial/setting-up-payments-with-store-card-cobranded--jrkLK41IjuquUmyKUi86Q).
+
+#### Setting up an anti-fraud provider
+
+Anti-fraud providers can be configured in the store to analyze credit and debit card payments, provided that an agreement has been established between the merchant and the provider. While their use is recommended, it is optional.
+
+To view the anti-fraud providers that are currently integrated with VTEX, enter the name of the provider into the [Help Center](https://help.vtex.com/en/) search bar or access the VTEX Admin, as detailed in the article [Configuring the anti-fraud](https://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud--tutorials_446).
+
+#### Creating gift cards
+
+Gift cards, also known as vouchers, can be used in VTEX stores as a payment method or in loyalty programs.
+
+VTEX has its own gift card provider, which allows creating and managing gift cards either through the VTEX Admin or via the Gift Card API. Learn more details about gift-card creation with both methods in [Gift Card API](https://developers.vtex.com/docs/api-reference/giftcard-api).
+
+You can also offer gift cards from external providers via the [GiftCard Hub API](https://developers.vtex.com/docs/api-reference/giftcard-hub-api). To use an external gift card provider, you must have an agreement with the provider and check if the provider is already integrated with VTEX. Learn more in [Setting up gift cards](https://help.vtex.com/en/tutorial/gift-card--tutorials_995) and [Gift Card system architecture](https://developers.vtex.com/docs/guides/gift-card-integration-guide-system-architecture).
+
+#### Enabling digital wallets
+
+Digital wallets provide secure environments where customers can store their bank and credit card information in an encrypted form and use it when completing a purchase. This payment method enhances security by eliminating the need to enter sensitive data for each purchase. Instead, users authenticate within the digital wallet environment once.
+
+On VTEX, you can offer native digital wallets, such as [Google Pay](https://help.vtex.com/en/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/61JMBvM5Vanqj6RaJsP8CT), or integrated digital wallets, such as [Apple Pay](https://help.vtex.com/en/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/STKWiXJSR9ImPt5EEC2aL), [Samsung Pay](https://help.vtex.com/en/tutorial/configurar-samsung-pay-como-meio-de-pagamento--5Yj9rgzOCVYuGmAumQlfpP), and [PayPal](https://help.vtex.com/en/tutorial/configurar-paypal--4p3sD9u1moq2Aya2oc684w). Learn more in [Digital wallet (ewallet)](https://help.vtex.com/en/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/7jLbdfch9Oe2yYbQa9zwE1).
+
+#### Customer Credit
+
+Customer Credit is a VTEX solution designed to offer credit to specific customers, enabling them to spread payments over time. With this app, you can access customer management, set up payment terms and installment plans, define credit limits, and monitor the status of issued invoices, among other features.
+
+Learn more in [Customer Credit - Overview](https://help.vtex.com/en/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0) and [Customer Credit - Getting Started](https://help.vtex.com/en/tracks/customer-credit-getting-started--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
+
+## Orders
+
+As soon as the customer completes a purchase, an [order](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE) is generated on VTEX. Orders can be managed through the VTEX Admin, in **Orders > [All Orders](https://help.vtex.com/en/tutorial/all-orders--2QTduKHAJMFIZ3BAsi6Pi)**, by accessing the [order details page](https://help.vtex.com/en/tutorial/order-details-page--2Y75n54Cc9VizrlG1N6ZNl), or via API. For an overview of developer content related to the [Orders API](https://developers.vtex.com/docs/api-reference/orders-api#overview), check the [Orders](https://developers.vtex.com/docs/guides/orders-overview) guide.
+
+### Before you begin with Orders
+
+The VTEX platform does not require mandatory settings for a store to manage its orders. Instead, it offers a variety of [optional settings](#optional-orders-settings) that can be strategic for different business models.
+
+However, for a customer to make a purchase and place an order, the store must have registered and priced products, offer [payment methods](https://help.vtex.com/en/tutorial/difference-between-payment-methods-and-payment-conditions--3azJenhGFyUy2gsocms42Q), and ensure that the order can be shipped. To do this, the following modules must be configured:
+
+- [Catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog)
+- [Prices](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices)
+- [Logistics](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistic)
+- [Payments](#payments)
+
+### Order integration
+
+Stores frequently want to [integrate their orders](https://developers.vtex.com/docs/guides/erp-integration-guide) with systems such as ERP (Enterprise Resource Planning) and WMS (Warehouse Management System). The [backend implementation](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) allows stores to automate some actions in order processing, such as:
+
+- Receiving notifications about order progress and status within the [order flow](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196).
+- Obtaining information on orders that need to be picked and packed.
+- Sending the [invoice](https://help.vtex.com/en/tutorial/how-to-manually-invoice-an-order--7p1h852V5t54KyscpgxE2v) to the VTEX platform, which then forwards it to the customer.
+- Making [changes](https://help.vtex.com/en/tutorial/changing-items-from-a-complete-order--tutorials_190) to order items.
+
+There are two different ways of tracking order status changes: [Feed](https://developers.vtex.com/docs/guides/orders-feed) or [Hook](https://developers.vtex.com/docs/guides/orders-feed#hook). Learn more about order integration in the [Backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) article.
+
+### Managing orders
+
+In the VTEX Admin, under **Orders > [All Orders](https://help.vtex.com/en/tutorial/all-orders--2QTduKHAJMFIZ3BAsi6Pi)**, you can perform the following actions:
+
+- View a list of all store orders.
+- Access order details on the [details page](https://help.vtex.com/en/tutorial/order-details-page--2Y75n54Cc9VizrlG1N6ZNl) by clicking the order.
+
+On the order details page, you can also track the progress of the [order flow](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196). The image below illustrates an example of this flow when the store acts as both a marketplace and a seller:
+
+![order-flow-en](//images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/3ea6fe2efb78e9b449acb2dac8b1700f/pedido_fluxo_completo_en.png)
+
+To find a purchase record in the VTEX Admin, you can either [filter orders](https://help.vtex.com/en/tutorial/filtering-all-orders--tutorials_192) on the **All Orders** page or use the global search bar, which is accessible from any page within the VTEX Admin. To search, simply select the `Orders` option in the right corner of the search bar and enter any of the following values:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer ID
+
+<div class="alert alert-warning">
+You can only access details about orders created in the last two years. This same period applies to customers accessing their orders via the <a href="">My Account</a> page.
+</div>
+
+To enable customers to track their orders, VTEX offers two important features: [transactional emails](#transactional-emails) and a dedicated customer area called [My Account](#my-account-feature).
+
+#### Transactional emails
+
+VTEX natively offers the option of sending [transactional emails](https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84), enabling stores to automatically inform customers of order updates. In essence, as the order progresses through the processing flow, customers can receive notification emails. These emails keep them updated on key stages, such as payment approval and order shipping.
+
+The platform offers a series of [transactional email templates](https://help.vtex.com/en/tutorial/order-transactional-email-templates--3g2S2kqBOoSGcCaqMYK2my), but customizing these communications is also possible. The list below describes the main aspects of these optional settings, which are independent of each other:
+
+- **Alias**: Alternative email address automatically generated by the VTEX platform to [mask](https://help.vtex.com/en/tutorial/general-configurations-on-the-oms--tutorials_194) the customer's email in store transactional emails. This [type of conversation mask](https://help.vtex.com/en/tutorial/general-configurations-on-the-oms--tutorials_194) provides enhanced protection for customer data, as the alternative email is designed to be unreadable by external systems.
+
+- **Availability - Notify Me**: Configuration of the [Notify Me](https://help.vtex.com/en/tutorial/setting-up-the-notify-me-option--2VqVifQuf6Co2KG048Yu6e) button on product pages visible on the store website. This button appears when a product is out of stock, allowing customers to enter their email to receive a notification when the product is available for purchase again.
+
+#### My Account feature
+
+[My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) is the solution that gives customers autonomy to check their orders and update their personal information. It's a unique environment for each customer and can be accessed with a username and password.
+
+One of the advantages of **My Account** is that it facilitates more direct communication between the customer and the store. Additionally, it allows customers to take actions such as ordering again or canceling their orders. More efficient communication tends to reduce the need for customer service, resulting in cost savings for the store.
+
+### Optional Orders settings
+
+The following table shows some optional settings in the Orders module:
+
+| **Feature** | **Description** |
+| :---: | :--- |
+| Subscriptions | [Subscriptions](https://help.vtex.com/en/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453) is an automatic order scheduler to simplify recurring purchases for store customers. The customer specifies the items they want to buy and how often the automatic orders should be placed.<br><br>[Setting up subscriptions](https://help.vtex.com/en/tutorial/como-configurar-assinaturas--1FA9dfE7vJqxBna9Nft5Sj) is particularly interesting for business models such as supermarkets and pet stores, where customers consume the same products on a regular basis. |
+| Telesales | The [telesales](https://help.vtex.com/en/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS) solution gives the customer service team more autonomy in assisting customers. By [configuring the telesales features](https://help.vtex.com/en/tutorial/como-configurar-as-funcionalidades-de-televendas--76FNgQP2Glc4umMJ5Yr50R), store operators can perform tasks such as:<br><br>- Making purchases on behalf of a customer.<br>- Manually adjusting item prices in a shopping cart.<br>- Editing existing orders.<br>- Managing customer profile information in [My Account](#my-account-feature).|
+| Price divergence | In store [marketplace strategies](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) in the VTEX ecosystem, the price set by the seller can differ from the price offered by the marketplace. Scenarios such as promotions in the marketplace can affect the original price set by the seller for their product.<br><br>To prevent order processing errors, VTEX sellers can [configure price divergence rules](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) and set parameters to allow the automatic authorization of orders with a price difference between the seller's set price and the marketplace offering. By implementing automatic rules for approving or rejecting orders with price discrepancies, the store can avoid the need for manual processing of each item, increasing operational efficiency. |
+
+Learn more in [Orders General Configuration](https://help.vtex.com/en/tutorial/configuracoes-gerais--tutorials_194).
+
+## Checkout
+
+Checkout is the last stage in the online shopping process, playing a significant role in achieving a good sales conversion rate. On the VTEX platform, the [Checkout](https://help.vtex.com/en/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) module is crucial for:
+
+- Providing information about the price and availability of products in the store.
+- Adding items to and processing the shopping cart.
+- Completing the purchase.
+
+### Before you begin with Checkout
+
+To ensure the checkout will work properly, the following modules must be correctly configured: [Catalog](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), [Logistics](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx), [Prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP#), [Promotions](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#), [Payments](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#), and [Orders](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE).
+
+![checkout-en](//images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/fd3e825135b5ca4f2a1c3b976bf9d9ad/checkout_image_EN.jpg)
+
+Sharing information allows processing details regarding availability, prices, applicable promotions, shipping options, and payment methods.
+
+### Customizing the store's checkout
+
+The customizations described below are optional and aim to improve the performance of the checkout process. Before configuring them, we recommend analyzing the most suitable options for your store's operation.
+
+- [Optimizing shipping options at checkout](#optimizing-shipping-options-at-checkout)
+- [Abandoned cart](#abandoned-cart)
+- [Changing the price of an item in the shopping cart](#changing-the-price-of-an-item-in-the-shopping-cart)
+- [Minimum order amount and maximum item quantity per SKU](#minimum-order-amount-and-maximum-item-quantity-per-sku)
+- [Geolocation at checkout](#geolocation-at-checkout)
+- [Checkout UI Custom app](#checkout-ui-custom-app)
+
+### Optimizing shipping options at checkout
+
+Solution that allows you to trigger a combination of existing data, showing customers the fastest and cheapest shipping options for the products selected in their cart. Other shipping options (with higher costs or longer delivery times) will not be displayed at checkout, improving the customer experience.
+
+Learn more in [Optimization of shipping options at Checkout](https://help.vtex.com/en/tutorial/otimizacao-das-opcoes-de-entrega-no-checkout--6DeGO9eBSFWe4XkoS0SxAB).
+
+### Abandoned cart 
+
+This feature allows sending emails to customers who have created a shopping cart but have not completed the purchase.
+
+<div class = "alert alert-info">
+Configuring the abandoned cart feature during the onboarding process allows forwarding all future carts for customer review, encouraging them to complete their purchases.
+</div>
+
+Learn more in [Setting up Cart Abandonment](https://help.vtex.com/en/tutorial/configurar-carrinho-abandonado--tutorials_740).
+
+### Changing the price of an item in the shopping cart
+
+On the VTEX platform, stores can manually adjust the price of an item (SKU) in the cart at checkout. This feature can be used to apply special discounts, correct pricing errors, create custom offers, address price-related complaints, or adjust shipping costs.
+
+<div class="alert alert-warning">
+Only users with the necessary <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> and permissions within the VTEX Admin can make these changes.
+</div>
+
+Learn more in [Change the price of an item in the shopping cart](https://help.vtex.com/en/tutorial/modificar-o-preco-de-um-item-no-carrinho-de-compras--7Cd37aCAmtL1qmoZJJvjNf).
+
+### Minimum order amount and maximum item quantity per SKU
+
+In ecommerce operations, the logistics cost associated with product shipping plays a crucial role in maintaining competitiveness. This cost is influenced by factors such as the total amount in the shopping cart and the number of units of the same SKU in the cart.
+
+Implementing a minimum order amount can improve efficiency for sellers who deliver in batches, avoiding orders with low total amounts or few items, which may be economically unviable.
+
+Learn more in [How to configure minimum order value and maximum quantity of items per SKU](https://help.vtex.com/en/tutorial/como-configurar-valor-minimo-de-pedido-e-quantidade-maxima-de-itens-por-sku--7JqipPUBxtKz0m4OlAyKs9).
+
+### Geolocation at checkout 
+
+The geolocation solution allows customers to use Google Maps on the store checkout screen for specifying their delivery location, as an alternative to entering the postal code. After indicating the delivery point, the shipping cost of the order will be calculated and displayed. This cost is based on the rates set by the merchant for deliveries within the selected area on the map (coordinate polygons).
+
+In addition to automatically calculating the shipping cost, if the store offers the option of in-store pickup, geolocation can help customers find the nearest store based on their current location.
+
+Learn more in [Setting up geolocation at checkout](https://help.vtex.com/en/tutorial/geolocalizacao-no-checkout--tutorials_4345).
+
+### Checkout UI Custom app
+
+This app allows different visual customizations to be applied to the store checkout screen.
+
+Learn more in [Checkout UI Custom](https://developers.vtex.com/docs/apps/vtex.checkout-ui-custom).
diff --git a/docs/tracks/en/vtex-support.md b/docs/tracks/en/vtex-support.md
new file mode 100644
index 000000000..19b3df2a0
--- /dev/null
+++ b/docs/tracks/en/vtex-support.md
@@ -0,0 +1,33 @@
+---
+title: 'VTEX Support'
+id: 7w7cUmbrdPEKpTMItjXEB8
+status: PUBLISHED
+createdAt: 2023-12-19T12:23:03.789Z
+updatedAt: 2024-05-23T17:44:36.531Z
+publishedAt: 2024-05-23T17:44:36.531Z
+firstPublishedAt: 2024-02-22T14:09:33.306Z
+contentType: trackArticle
+productTeam: Billing
+slug: vtex-support
+locale: en
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugEN: support-at-vtex
+---
+
+When clients and partners need support, they can count on VTEX assistance, which includes our documentation portals, VTEX Community, and our online support, as shown in the table below:
+
+| **Channel**  | **Artigos** |
+|--------------|-------------|
+| [Help Center](https://help.vtex.com/pt/)      | Documentation portal intended for merchants, support teams and business decision-makes who work with the platform's administrative dashboard, the VTEX Admin. |
+| [Developer Portal](https://developers.vtex.com/) | Documentation portal intended for developers and technical users working with the VTEX platform.                                                              |
+| [VTEX Community](https://community.vtex.com/)   | Official VTEX community. This is where you share questions, ideas, and create connections within the VTEX ecosystem.                         |
+| [VTEX Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe)     | Official VTEX support provided virtually by experts. If your issue needs access to data privacy, open a [technical](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#technical), [billing](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#financial), or [commercial](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#commercial) support request.
+
+This track is dedicated to describing the virtual support provided by VTEX and is structured as follows:
+
+- [How VTEX Support works](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3)
+- [Opening tickets](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE)
+- [Technical support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T)
+- [Billing support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl)
+- [Commercial support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ)
+- [Contract termination](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3TUpFItxp8L1WZAD1JuYfF)
diff --git a/docs/tracks/en/what-are-clustered-payment-conditions.md b/docs/tracks/en/what-are-clustered-payment-conditions.md
index 847604c8a..3c6995824 100644
--- a/docs/tracks/en/what-are-clustered-payment-conditions.md
+++ b/docs/tracks/en/what-are-clustered-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'What are Clustered Payment Conditions?'
 id: 4z2upCJ2om27Cs0BVJRA0U
 status: PUBLISHED
 createdAt: 2020-11-18T11:49:06.387Z
-updatedAt: 2022-02-07T13:17:58.519Z
-publishedAt: 2022-02-07T13:17:58.519Z
+updatedAt: 2024-05-07T19:41:05.528Z
+publishedAt: 2024-05-07T19:41:05.528Z
 firstPublishedAt: 2020-11-18T17:37:30.544Z
 contentType: trackArticle
 productTeam: Financial
@@ -21,6 +21,3 @@ This functionality is currently in Closed Beta (testing stage) and is not availa
 </div>  
 
 This customization is done using our [Master Data](https://help.vtex.com/en/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw "Master Data") database. 
-
-Next, you will learn how to use this feature in your store’s operation.
-
diff --git a/docs/tracks/en/what-is-a-logistics-route.md b/docs/tracks/en/what-is-a-logistics-route.md
index 851a65f91..bb1d4d026 100644
--- a/docs/tracks/en/what-is-a-logistics-route.md
+++ b/docs/tracks/en/what-is-a-logistics-route.md
@@ -33,4 +33,4 @@ To add a loading dock to a store's admin, follow the steps detailed in this [lin
 ### Carrier
 A carrier is used to distribute orders to the their respective end users and is comprised of a fleet of vehicles that will perform the actual deliveries. The distribution center sends orders out for delivery directly to the carrier that will be used to complete the process until its final destination.
 
-![EN Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
+![EN Conceitos Logística](//images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
diff --git a/docs/tracks/en/what-is-conversational-commerce-vtex.md b/docs/tracks/en/what-is-conversational-commerce-vtex.md
index 1185c2167..05bb725e5 100644
--- a/docs/tracks/en/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/en/what-is-conversational-commerce-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'What is VTEX Conversational Commerce?'
 id: 1NwwADrU70v3roPUV7dWxI
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T14:47:50.242Z
-updatedAt: 2023-04-18T15:02:45.235Z
-publishedAt: 2023-04-18T15:02:45.235Z
+updatedAt: 2024-01-05T17:13:58.076Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:46:55.444Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/en/what-is-instore.md b/docs/tracks/en/what-is-instore.md
index 917f945f7..bf669740d 100644
--- a/docs/tracks/en/what-is-instore.md
+++ b/docs/tracks/en/what-is-instore.md
@@ -3,8 +3,8 @@ title: 'What is VTEX Sales App?'
 id: 7fnnVlG3Kv1Tay9iagc5yf
 status: PUBLISHED
 createdAt: 2020-06-28T13:07:24.773Z
-updatedAt: 2023-05-31T15:45:55.825Z
-publishedAt: 2023-05-31T15:45:55.825Z
+updatedAt: 2024-05-13T18:03:19.146Z
+publishedAt: 2024-05-13T18:03:19.146Z
 firstPublishedAt: 2020-06-28T13:12:31.221Z
 contentType: trackArticle
 productTeam: Shopping
@@ -24,19 +24,12 @@ With that, you’ll be able to implement an Endless Aisle strategy, which helps
 
 - Avoid stockout and never miss a sale.
 - Have real-time visibility of your inventory.
-- Benefit from an intelligent search and items lookup.
+- Benefit from an intelligent search and items lookup, when [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) is installed on the website. .
 - Build mixed cart transactions.
 
-On the fulfillment side of your operation, VTEX Sales App will help you to:
-
-- Attract foot traffic and increase sales.
-- Have an efficient order picking workflow.
-- Guarantee your products are always available, with wiser shipping options.
-- Lower fulfillment time and cost with Smart Routing.
-
 Finally, with VTEX Sales App, the purchasing process becomes faster, both while adding products to the cart and during payment and confirmation.
 
-The checkout process no longer needs to be done at a fixed desk. Starting and finishing sales can be done anywhere in the store, which reduces queues and makes the customer experience smoother.
+The checkout process no longer needs to be done from a physical and fixed location. Starting and finishing sales can be done anywhere in the store, which reduces queues and makes the customer experience smoother.
 
 Your sales associates will have a 360º view of the consumer and will be able to create memorable and frictionless shopping experiences.
 
diff --git a/docs/tracks/en/what-is-lengow.md b/docs/tracks/en/what-is-lengow.md
index 715f9c273..e81b90f99 100644
--- a/docs/tracks/en/what-is-lengow.md
+++ b/docs/tracks/en/what-is-lengow.md
@@ -18,7 +18,7 @@ Since 2009, [Lengow](https://www.lengow.com/) has grown in the European market b
 
 The [Lengow connector](https://apps.vtex.com/vtex-lengow/p) for VTEX allows your store to use their e-commerce feed management solution to increase the visibility and profitability of your products on Amazon, Google Shopping, Facebook, eBay, Criteo and <a href="https://www.lengow.com/marketplace-finder/" target="_blank">others</a>.
 
-<div><a href="https://www.lengow.com/" target="_blank"><img src="https:https://images.ctfassets.net/alneenqid6w5/2i9dPrUQBspc11Q52km82I/a44c2f63f968b50611dc0a7d2f5c5dd1/lengow.png" alt="Lengow" style="margin-left: auto; margin-right: auto; display: block;"></a></div>
+<div><a href="https://www.lengow.com/" target="_blank"><img src="https://images.ctfassets.net/alneenqid6w5/2i9dPrUQBspc11Q52km82I/a44c2f63f968b50611dc0a7d2f5c5dd1/lengow.png" alt="Lengow" style="margin-left: auto; margin-right: auto; display: block;"></a></div>
 
 Once the connector app is set up, your catalog feed will become available in Lengow and your products will be ready to be published on the channels of your choice. As you sell across different channels, orders and product stock levels will be automatically kept in sync between VTEX and Lengow.
 
diff --git a/docs/tracks/en/what-is-the-cms.md b/docs/tracks/en/what-is-the-cms.md
index 2df70a6ce..5efa7bbe1 100644
--- a/docs/tracks/en/what-is-the-cms.md
+++ b/docs/tracks/en/what-is-the-cms.md
@@ -14,7 +14,7 @@ trackId: 2YcpgIljVaLVQYMzxQbc3z
 trackSlugEN: cms
 ---
 
-![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System) is a feature dedicated to manage content in a constant and practical manner.
 
diff --git a/docs/tracks/en/what-is-the-master-user.md b/docs/tracks/en/what-is-the-master-user.md
index 743f74187..30636e3b2 100644
--- a/docs/tracks/en/what-is-the-master-user.md
+++ b/docs/tracks/en/what-is-the-master-user.md
@@ -26,7 +26,7 @@ If your user has role to the Account management module, you can verify who is th
 
 By clicking on the desired account name, the Sponsor user's name and email are in the __Contact__ section.
 
-![usuario-master-contato en](https://images.ctfassets.net/alneenqid6w5/3ezUM1WmYEcIkGOoKm2s8e/0d14ffe3cce780a79f6111b46943db80/contato_usuario_master_en.png)
+![usuario-master-contato en](//images.ctfassets.net/alneenqid6w5/3ezUM1WmYEcIkGOoKm2s8e/0d14ffe3cce780a79f6111b46943db80/contato_usuario_master_en.png)
 
 Among the actions that only the Sponsor user can take are:
 - Reindex the catalog.
diff --git a/docs/tracks/en/what-is-vtex-payment.md b/docs/tracks/en/what-is-vtex-payment.md
index 55c5ef933..88d7f2c5f 100644
--- a/docs/tracks/en/what-is-vtex-payment.md
+++ b/docs/tracks/en/what-is-vtex-payment.md
@@ -1,10 +1,10 @@
 ---
 title: 'What is VTEX Payment?'
 id: 1lZWKCGdy7xpYjukTLfFJL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T17:29:51.035Z
-updatedAt: 2023-03-14T22:08:12.345Z
-publishedAt: 2023-03-14T22:08:12.345Z
+updatedAt: 2023-10-05T14:12:50.764Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:47:57.806Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md b/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md
index 578f55ddd..d797ddc3a 100644
--- a/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md
+++ b/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md
@@ -3,8 +3,8 @@ title: 'What to configure in Wish prior to the integration'
 id: 4mIn8NE9McE9BxKsAf9IcB
 status: PUBLISHED
 createdAt: 2019-11-13T16:43:49.316Z
-updatedAt: 2020-02-13T15:01:13.402Z
-publishedAt: 2020-02-13T15:01:13.402Z
+updatedAt: 2023-09-22T20:08:35.507Z
+publishedAt: 2023-09-22T20:08:35.507Z
 firstPublishedAt: 2019-11-19T17:27:37.060Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/en/whatsapp-integration.md b/docs/tracks/en/whatsapp-integration.md
index 87548a44d..c3c1c709a 100644
--- a/docs/tracks/en/whatsapp-integration.md
+++ b/docs/tracks/en/whatsapp-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'WhatsApp Integration'
 id: 33sM0SVrwffWhAhAgiGrZb
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T15:11:28.551Z
-updatedAt: 2023-04-25T20:26:48.598Z
-publishedAt: 2023-04-25T20:26:48.598Z
+updatedAt: 2024-01-05T17:14:09.083Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:47:05.529Z
 contentType: trackArticle
 productTeam: Shopping
@@ -45,7 +45,7 @@ In addition to sending this information, the administrator must authorize the fo
 We also recommend [checking your store with Meta](https://www.facebook.com/business/help/1095661473946872?id=180505742745347). This step is optional for integration, but is mandatory if:
 
 * You want to initiate conversations, such as product tracking warnings, for your customers through WhatsApp.
-* You want your business account to be [official](https://developers.facebook.com/micro_site/url/?click_from_context_menu=true&country=BR&destination=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation%23official-business-account&event_type=click&last_nav_impression_id=0txQ0CoZfJfxi7cez&max_percent_page_viewed=44&max_viewport_height_px=869&max_viewport_width_px=1794&orig_http_referrer=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation&orig_request_uri=https%3A%2F%2Fdevelopers.facebook.com%2Fajax%2Fdocs%2Fnav%2F%3Ftranslation%26path1%3Dwhatsapp%26path2%3Doverview%26path3%3Dbusiness-accounts&region=latam&scrolled=true&session_id=2nAsnwfEzmFrzLZoM&site=developers), which allows the display of the name of the store instead of the phone number on the list and with the seal <img src="https://images.ctfassets.net/alneenqid6w5/4DNjQiVYTI24Wjt3t9CRfG/8e1ec0ab6bb167b4ff0de2547243354f/101835379_284952909300321_643050663994982400_n.png" alt="selo oficial whatsapp" width="25"/>.
+* You want your business account to be [official](https://developers.facebook.com/micro_site/url/?click_from_context_menu=true&country=BR&destination=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation%23official-business-account&event_type=click&last_nav_impression_id=0txQ0CoZfJfxi7cez&max_percent_page_viewed=44&max_viewport_height_px=869&max_viewport_width_px=1794&orig_http_referrer=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation&orig_request_uri=https%3A%2F%2Fdevelopers.facebook.com%2Fajax%2Fdocs%2Fnav%2F%3Ftranslation%26path1%3Dwhatsapp%26path2%3Doverview%26path3%3Dbusiness-accounts&region=latam&scrolled=true&session_id=2nAsnwfEzmFrzLZoM&site=developers), which allows the display of the name of the store instead of the phone number on the list and with the seal <img src="//images.ctfassets.net/alneenqid6w5/4DNjQiVYTI24Wjt3t9CRfG/8e1ec0ab6bb167b4ff0de2547243354f/101835379_284952909300321_643050663994982400_n.png" alt="selo oficial whatsapp" width="25"/>.
 
 ## Created by the client via the VTEX Admin
 
@@ -62,17 +62,17 @@ After installing the app, VTEX will share the VTEX Conversational Commerce Admin
 Then, follow the steps below:
 
 1. Log in to the VTEX Admin using the URL provided by the support team. You will be directed to the screen below:
-![Track 101 - Conversational Commerce 1 - PT](https://images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 1 - PT](//images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
 2. Click the `Configure WhatsApp Business Account` button.
 3. A Facebook window will open for configuration. Log in with the desired Business Manager Admin profile.
 4. Select the `Create a WhatsApp Business Account` option.
 5. Enter the account name for your WhatsApp profile.
 6. Select the category and enter the account description. 
-![Track 101 - Conversational Commerce 2 - PT](https://images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 2 - PT](//images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
 7. Check the phone number you want to associate with the account via the code sent to the phone.
 8. Notify VTEX support to complete the configuration.
 
 Once the configuration is complete, the alert below will be displayed in the Admin. 
 
-![Track 101 - Conversational Commerce 3 - PT](https://images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 3 - PT](//images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
 
diff --git a/docs/tracks/es/access-to-the-customers-last-cart.md b/docs/tracks/es/access-to-the-customers-last-cart.md
index 261342adf..a9e5645ba 100644
--- a/docs/tracks/es/access-to-the-customers-last-cart.md
+++ b/docs/tracks/es/access-to-the-customers-last-cart.md
@@ -20,4 +20,4 @@ Al tener acceso a esta información, el vendedor puede intentar completar la ven
 
 Simplemente haga clic en `Acceder` para ver los productos en el carrito abandonado.
 
-![last-cart-es](https://images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/13c98f924fcee93b1a04f4bcd9f91821/last-cart-ES.png)
+![last-cart-es](//images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/13c98f924fcee93b1a04f4bcd9f91821/last-cart-ES.png)
diff --git a/docs/tracks/es/accounts-and-architecture.md b/docs/tracks/es/accounts-and-architecture.md
new file mode 100644
index 000000000..fbfd5dc64
--- /dev/null
+++ b/docs/tracks/es/accounts-and-architecture.md
@@ -0,0 +1,126 @@
+---
+title: 'Cuentas y arquitectura'
+id: 4yPqZQyj0t675QpcG7H6yl
+status: PUBLISHED
+createdAt: 2024-01-09T00:00:08.724Z
+updatedAt: 2024-02-22T17:18:14.922Z
+publishedAt: 2024-02-22T17:18:14.922Z
+firstPublishedAt: 2024-02-22T14:06:20.581Z
+contentType: trackArticle
+productTeam: Others
+slug: cuentas-y-arquitectura
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+VTEX ofrece muchas funcionalidades y productos cuya disponibilidad puede variar dependiendo del [tipo de cuenta](#tipos-de-cuenta-vtex), ya que cada tipo fue creado para escenarios específicos. Antes de empezar a planificar la [arquitectura de la tienda](#arquitectura-de-la-tienda) y definir los [partners de implementación](#partners-de-implementacion), es importante conocer las principales características de las cuentas.
+
+## Tipos de cuenta VTEX
+
+La definición de la arquitectura de una tienda VTEX depende de la cuenta VTEX. Esto se debe a que algunas funcionalidades solo se ofrecen mediante ciertos tipos de cuenta y cada una se adapta a determinados modelos de negocio. La mejor cuenta es la que mejor refleja la estructura de ese modelo de negocio.  
+
+Los tipos de cuenta VTEX son:
+
+- **Cuenta principal (estándar):** es la cuenta VTEXprimordial y permite crear el sitio web de la tienda, configurar todos los ajustes nativos y contratar todos los servicios de la plataforma.
+- [Cuenta franquicia](https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl): es una cuenta asociada a la cuenta principal. No tiene un sitio web propio y su característica más importante es que no permite configurar un catálogo propio, sino que lo recibe de la cuenta principal. Este tipo de cuenta se recomienda para operaciones que tienen tiendas físicas, franquicias y representantes de marca. No es obligatorio que la tienda tenga una red de franquicias para beneficiarse de los recursos de una cuenta franquicia VTEX.
+- [Cuenta Seller Portal](https://help.vtex.com/es/tutorial/seller-criar-conta-no-seller-portal--3gn2Q5rMhgu0jjX7AiiHcs): es una cuenta asociada a una cuenta principal. No tiene sitio web propio y su característica más importante es que convierte la tienda en un marketplace para [sellers white label](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) o sellers externos que no forman parte del ecosistema VTEXy les permite activar su propio catálogo en el marketplace VTEX. En otras palabras, es una edición de la plataforma VTEXdirigida a los sellers de la cuenta principal.  
+
+La siguiente imagen muestra una visión general para ayudarte a [elegir entre la cuenta estándar, franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78):
+
+![main_account_franchise_seller_portal_ES](//images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/befcaed2563320ca9280d44759fe4962/main_account_franchise_seller_portal_ES.png)
+
+## Recursos de las cuentas
+
+Hay varios factores que se deben considerar al [elegir entre la cuenta estándar, franquicia o Seller Portal.](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78) La tabla a continuación describe los principales recursos de cada una:  
+
+| **Tipo de cuenta** | **Características principales** |
+| :---: | :--- |
+| Cuenta principal (estándar) | <ul><li>Tiene frontend y sitio web propio.</li><li>Puede convertirse en <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multitienda">multitienda</a> y tener varios sitios web y tiendas, cada uno con su propia política comercial.</li><li>Tiene su propio entorno en el Admin VTEX para gestionar la operación.</li><li>Puede tener cuentas franquicia y Seller Portal y contratar nuevos entornos.</li><li>Permite operar como <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#como-seller-vtex">seller VTEX</a> y <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex">marketplace VTEX</a> de forma nativa y conectarse con todas las tiendas del ecosistema VTEX.</li><li>Puede configurar <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">sellers white label</a> en cuentas franquicia.</li><li>Puede vender de forma nativa el stock de sus cuentas franquicia en otros marketplaces VTEX mediante la funcionalidad <a href="https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a>.</li><li>Puede integrarse con <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">sellers externos</a> y <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-guide">marketplaces externos</a>.</li><li>Puede contratar productos add-on.</li></ul> |
+| Cuenta franquicia | <ul><li>No tiene frontend ni sito web propio.</li><li>Tiene un entorno propio en el Admin VTEX para gestionar la operación.</li><li>No tiene catálogo propio y refleja la estructura de catálogo exacta de la cuenta principal.</li><li>Puede configurar precios y promociones.</li><li>Tiene almacén y stock propios.</li><li>El stock de la cuenta franquicia puede ser vendido en otros marketplaces VTEX que estén conectados con la cuenta principal a través de <a href="https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a>.</li></ul> |
+| Cuenta Seller Portal | <ul><li>No tiene frontend ni sito web propio.</li><li>La cuenta principal tiene una página de <a href="https://help.vtex.com/es/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv">Gestión de sellers</a>. A su vez, cada seller cuenta un entorno independiente en el Admin del Seller Portal.</li><li>El seller puede configurar stock y precio, gestionar productos compartidos con el marketplace, facturar pedidos, activar promociones, procesar pagos y contar con logística propia.</li></ul> |  
+
+<div class="alert alert-info">
+<p><b>Marketplaces en VTEX</b></p><p>Además de proporcionar gran versatilidad en la arquitectura de la tienda, nuestro ecosistema permite que cada tienda cuente con una serie de <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">estrategias de marketplace</a> tales como:</p><ul><li>Convertirse en seller o marketplace para otras tiendas VTEX.</li><li>Integrarse con importantes actores del mercado como <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> y <a href="https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP">Amazon</a>.</li><li>Integrarse con los <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros">marketplaces partner</a> certificados por VTEX.</li>
+<li> Ser un marketplace para sellers que tengan una cuenta <a href="https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK">Seller Portal</a>.</li>
+<li> Ser un <a href="https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>.</li>
+<li> Crear integraciones propias con <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">marketplaces y sellers externos</a>.</li></ul>
+</div>
+
+## Arquitectura de la tienda
+
+La plataforma VTEX ofrece a diversos modelos y tamaños de negocio todas las funcionalidades y configuraciones necesarias para sus operaciones. Por ejemplo, una tienda puede tener una estrategia diferente en cada canal de venta a través de [políticas comerciales](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz#politicas-comerciales) y configurar un catálogo, precio y logística distinta para cada canal. Solo es necesario [contratar nuevas políticas comerciales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X).
+
+Sin embargo, el uso simultáneo de muchas políticas comerciales puede afectar el desempeño de la tienda y hacer que sea más lenta, ya que los cambios deben actualizarse en múltiples políticas. Dependiendo del modelo de negocio y la complejidad de la operación, se puede crear segmentación utilizando las siguientes opciones:  
+
+- [Multitiendas](#multitienda)  
+- [Entornos adicionales](#entorno-adicional)
+
+La siguiente imagen es un ejemplo de la relación entre la cuenta principal, entorno (subcuenta), multitiendas (tiendas) y políticas comerciales:  
+
+![multistore_aditional_environment_ES](//images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/a0d486cc33bba9057698b54eb2f8eaf4/multistore_aditional_environment_ES.png)
+
+### Multitienda
+
+[Multitienda o multidominio ](https://help.vtex.com/es/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL)es la funcionalidad que permite crear otras tiendas asociadas a la cuenta principal cuya gestión se llevará a cabo en el mismo entorno administrativo. Esto significa que cada tienda tendrá su propio [storefront](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) y dominio, aunque pueden compartir la configuración de módulos, como catálogo, logística, precios, entre otros.  
+
+Algunas de las principales ventajas de [crear multitiendas](https://help.vtex.com/es/tutorial/como-criar-multiloja-multidominio--tutorials_510) son la facilidad que le brinda a la empresa de comercializar productos con nichos diferentes, la practicidad al vender múltiples marcas y la agilidad al ofrecer diversos productos en tiendas y canales distintos.  
+
+Los siguientes escenarios son ejemplos de casos en los que tener múltiples tiendas asociadas a un mismo entorno es estratégico:  
+
+- **Tienda nacional e internacional:** hay una tienda para el país de origen de la operación y otra para el mercado internacional.
+- **Segmentación pornicho:** se aplica a las empresas con un amplio nicho y que tienen tiendas separadas según la oferta de diferentes tipos de productos dirigidos a públicos distintos.
+- **Operaciones distintas:** para los negocios que tienen operaciones B2C y B2B, por ejemplo, puede ser estratégico tener tiendas separadas para cada tipo de operación, pero que compartan muchas configuraciones e información y, así, mantener la gestión centralizada y ágil.  
+
+Además de la combinación de políticas comerciales y multitiendas, VTEX permite contratar un nuevo entorno, como se explica a continuación.  
+
+### Entorno adicional
+
+Una cuenta VTEX estándar puede separar por completo el espacio de gestión de las operaciones; solo hay que [contratar un nuevo entorno](https://help.vtex.com/es/tutorial/contratar-novo-ambiente--tutorials_2542). Esto significa que cada Admin VTEX estará asociado a una cuenta propia y tendrá una configuración de storefront y módulos de la plataforma independientes.  
+
+Algunos casos de uso comunes para contratar un nuevo entorno son cuando se quiere tener un [entorno exclusivo para pruebas](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH#4-pruebas-antes-del-go-live) (Quality Assurance - QA) o un entorno completamente separado para gestionar otra operación como B2C, B2B o B2E.
+
+## Elegirentre multitienda y ambiente adicional
+
+La siguiente tabla presenta los puntos importantes que se deben tomar en cuenta al decidir entre una arquitectura multitienda, entorno adicional o una combinación de ambas:
+
+| **Tema** | **Multitienda (tiendas)** | **Entorno adicional (subcuentas)** |
+| :---: | :--- | :--- |
+| Arquitectura | Un __solo entorno administrativo__ en el Admin VTEX asociado a dos o más tiendas [store names](https://help.vtex.com/es/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK). Todas las tiendas están vinculadas al **mismo [account name](https://help.vtex.com/es/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC)**. | **Múltiples entornos administrativos** en el Admin VTEX con configuraciones completamente independientes. Cada entorno tiene un **[account name](https://help.vtex.com/es/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) propio.** |
+| Mapa del sitio | Un único **[mapa del sitio](https://help.vtex.com/es/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) para la cuenta principal que se comparte** entre todas las tiendas.| Cada cuenta tiene un **[mapa del sitio](https://help.vtex.com/es/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) propio**. |
+| Segmentación de ventas | Las tiendas pueden __segmentar experiencias de compra mediante políticas comerciales__. Esto también ayuda a mantener el desempeño de cada tienda, ya que no es necesario tener múltiples políticas comerciales activas. | Muchas posibilidades para segmentar y personalizar las ventas, ya que cada entorno puede __combinar varias políticas comerciales y multitiendas__. |
+| Tipo de equipo | Un __mismo equipo gestiona__ la operación o, si hay varios equipos, la similitud en las configuraciones entre tiendas permite compartir eficientemente los ajustes de catálogo, logística y precio, entre otras. Todos los usuarios son **gestionados a través del mismo [License Manager](https://help.vtex.com/es/tutorial/visao-geral-do-modulo-license-manager)**. | __Diferentes tipos de equipos__ dentro de la empresa están encargados de distintas operaciones. __Cada entorno tiene un License Manager__ y los [usuarios](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512?&utm_source=autocomplete) de cada entorno se gestionan por separado. |
+| Costos | __No hay costo__ para crear nuevas tiendas, sin embargo, para crear storefronts diferentes se requiere contratar una política comercial adicional, lo que sí conlleva un cargo. | __Hay costo__ para [contratar un entorno adicional](https://help.vtex.com/es/tutorial/contratar-novo-ambiente--tutorials_2542?&utm_source=autocomplete), pero este ya incluye una política comercial. |
+
+Para más información, accede al artículo [Elegir entre arquitectura multitienda o entorno adicional](https://help.vtex.com/es/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL).
+
+## Cuestionario sobre tipo de arquitectura
+
+Para ayudarte a decidir qué productos y configuraciones incluir en la planificación de la arquitectura de la tienda, creamos la siguiente tabla de preguntas:
+
+| **Tema** | **Preguntas** |
+| :---: | :--- |
+| Mapeo de arquitectura existente | - ¿Hay [integraciones externas](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) que se deban considerar? Por ejemplo: <br><br> - Enterprise Resource Planning (ERP) <br><br>  - Customer Relationship Management (CRM) <br><br> - Transportation Management System (TMS) <br><br> - Warehouse Management System (WMS) <br><br> - Business Intelligence (BI) <br><br> - ¿Las integraciones externas se conectarán directamente con la plataforma utilizando las [API de VTEX](https://developers.vtex.com/docs/api-reference)? <br><br> - ¿Se requerirá contratar un [partner de integración](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion) para crear una [integración de back office](https://developers.vtex.com/docs/guides/erp-integration-guide)? |
+| Métodos de crear la tienda | - ¿La implementación se realizará utilizando las API de [API Reference de VTEX](https://developers.vtex.com/docs/api-reference)? <br><br> - ¿La implementación se realizará a través del Admin VTEX? <br><br> - ¿Es un modelo de headless commerce que utilizará tecnologías de [frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) en el escenario headless? |
+| Estructura general de [backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) y [frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) | - ¿Se requerirá un partner para implementar el [backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) de la tienda? <br><br> - ¿Se requerirá un partner para implementar el [frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) de la tienda? <br><br> - ¿Se creará el frontend de la tienda utilizando alguna de [las siguientes tecnologías VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#tecnologias-de-desarrollo-de-frontend-de-vtex)? ([Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) and [FastStore](https://www.faststore.dev)) <br><br> - ¿Se utilizará el Content Management System (CMS) [Storefront](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC) en el Admin VTEX para las operaciones de la tienda? <br><br> - ¿El modelo de [autenticación](https://developers.vtex.com/docs/guides/authentication) en VTEX podría generar fricción en las integraciones con la plataforma VTEX? |
+| Estructura general en VTEX | - ¿Se requerirá tener [cuentas franquicia](https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl)? <br><br> - ¿Es importante tener [sellers white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa)? <br><br> - ¿Valdría la pena aprovechar el uso de [Multilevel Omnichannel Inventory (MOI)](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4)? <br><br> - ¿Se requerirá tener cuentas [Seller Portal](https://help.vtex.com/es/tutorial/seller-criar-conta-no-seller-portal--3gn2Q5rMhgu0jjX7AiiHcs)? <br><br> - ¿Se requerirá contratar un [entorno adicional](https://help.vtex.com/es/tutorial/contratar-novo-ambiente--tutorials_2542)? <br><br>- ¿La operación usa [multitienda/multidominio](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitectura-de-la-tienda)? <br><br> - ¿Valdría contratar una [política comercial adicional](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#contratacion-de-politicas-comerciales-adicionales)? <br><br> - ¿Sería conveniente tener la solución nativa para crear integraciones con [sellers VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#como-seller-vtex) y [marketplaces VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex)? <br><br> - ¿Sería conveniente crear integraciones con [sellers externos](https://developers.vtex.com/docs/guides/external-seller-integration-guide) y [marketplaces externos](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide)? <br><br> - ¿Qué puntos de [optimización de rendimiento](https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance) deben tomarse en cuenta en el desarrollo en Store Framework? <br><br> - ¿Qué puntos de internacionalización deben tomarse en cuenta en el desarrollo en Store Framework? <br><br> - La operación es internacional y requiere [gestionar contenido mediante binding](https://help.vtex.com/es/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) para personalizar la apariencia de la tienda según la ubicación de los usuarios. |
+| Tipo de sector | - ¿Cuál es el sector de la operación? <br><br> - ¿Está relacionado con [moda](https://vtex.com/mx-es/moda-y-vestuario/) (ropa y vestuario)? <br><br> - ¿Está relacionado con [supermercado](https://vtex.com/mx-es/supermercado/)?  |
+| Caso de uso | - ¿El modelo de negocio incluye [comercio B2C](https://vtex.com/ar-es/digital-commerce/) o [comercio B2B](https://help.vtex.com/es/tutorial/setting-up-b2b-on-vtex--tutorials_238)? <br><br> - ¿Se requerirá una [solución omnichannel](https://vtex.com/co-es/omnichannel/)? |
+| [Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) | - ¿Cuál será la [arquitectura del catálogo](https://help.vtex.com/es/tracks/catalogo-1015AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) de productos? <br><br> - ¿La integración back office realizará la configuración del catálogo? <br><br> - ¿Se importarán los productos a través de una [integración de back office](https://developers.vtex.com/docs/guides/erp-integration-import-products)? <br><br> - ¿Hay que [internacionalizar el catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization)? |
+| [Búsquedas en el sitio web de la tienda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) | - ¿Hay que instalar y configurar [VTEX Intelligent Search](https://developers.vtex.com/docs/apps/vtex.search) para que los clientes dispongan de búsqueda inteligente y autocompletar en el sitio web de la tienda? <br><br> - ¿La operación está presente en varios países y necesita ofrecer una experiencia de [búsqueda en múltiples idiomas](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO) a los clientes? <br><br> - ¿Deseas que la tienda ordene los productos en los resultados de búsqueda siguiendo alguna [regla de merchandising específica](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW)? <br><br> - ¿Sería beneficioso configurar Region para [regionalizar a los sellers](https://help.vtex.com/es/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw)? |
+| [Precios](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precios) y [Promociones](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promociones) | - ¿Considerando la [arquitectura del sistema de precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) en VTEX, qué tipos de precios se registrarán? <br><br> - ¿Se configurarán los precios de los productos a través de una integración de back office? <br><br> - ¿La estrategia de ventas utiliza [tablas de precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8)? <br><br> - ¿Se espera [crear promociones](https://help.vtex.com/es/tutorial/lista-de-promocoes-beta--4yB7nNdliiFxBTXE19GCIi)? |
+| [Pagos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos) | - ¿Con qué gateway o grupo de gateways habrá contacto para después [registrar las afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444) en la plataforma? <br><br> - ¿Qué [configuraciones de pago](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) (crédito, efectivo, etc.) se requerirán para las [condiciones de pago](https://help.vtex.com/es/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) ofrecidas a los clientes en el checkout? <br><br> - ¿Sería conveniente configurar el [split de pagos](https://help.vtex.com/es/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) para sellers y marketplaces? |
+| [Logística y fulfillment](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) | - ¿Cómo se organizará la [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)? <br><br> - ¿Cuáles serán los [muelles](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)? <br><br> - ¿Cuáles serán los [almacenes](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)? <br><br> - ¿Cuáles serán las [políticas de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140)? <br><br> - ¿Qué [transportadoras](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) de las [plantillas de envío](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) se configurarán en las políticas de envío? <br><br> - ¿Se configurarán [puntos de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) para que los clientes puedan recoger los pedidos en tiendas físicas o centros de distribución? <br><br> - ¿En la [gestión de stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) sería conveniente configurar el [lead time](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) (ajuste opcional de tiempo de envío a nivel de SKU)?<br><br> - ¿Se importará el stock a través de una integración de back office? <br><br> - ¿Sería conveniente activar [VTEX Shipping Network Correios](https://help.vtex.com/es/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) para integrar la operación con los servicios de PAC y SEDEX de Correios a través del Admin? (Solo Brasil). <br><br> - ¿La operación tiene tiendas internacionales y ventas [cross border](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs)? |
+| [Pedidos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos) | - ¿Sería conveniente configurar [Feed o Hook](https://developers.vtex.com/docs/guides/orders-feed) para monitorear los cambios de [status de los pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196)? <br><br> - ¿Se requerirá una [integración de back office](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-integration) para enviar los datos de pedidos VTEX a sistemas externos como ERP o WMS, o para enviar datos de pedidos de sistemas externos a VTEX? |
+| [Checkout](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout) | - ¿La tienda utilizará [VTEX Checkout VTEX](https://help.vtex.com/es/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) o una solución externa? <br><br> - ¿Sería conveniente [configurar el precio y disponibilidad de SKU a nivel regional](https://help.vtex.com/es/tutorial/setting-up-price-and-availability-of-skus-by-region--12ne58BmvYsYuGsimmugoc) de modo que el cliente vea primero los ítems de la tienda con stock en su ubicación? |
+
+## Partners de implementación
+
+Es común que agencias y [partners de implementación ](https://vtex.com/mx-es/partner/)(system integration partners) participen de la creación de una tienda. VTEX se asocia con un amplio ecosistema de partners que han sido reconocidos por su excelencia y confiabilidad al crear proyectos de tiendas VTEX. Siempre que el [usuario](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) tenga permiso de acceso al Admin VTEX de una tienda, puede consultar la lista de partners a través del [Partner Portal](https://partnerportal.vtex.com/) (solamente en portugués).
+
+El [Cuadrante VTEX](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) es un programa en que VTEX evalúa internamente el rendimiento y los resultados de éxito de operación de sus partners. Es una forma de reconocer y recompensar anualmente a los partners que demuestren el máximo nivel de entrega y excelencia. [Aquí](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) puedes ver el resultado del Cuadrante VTEX 2023.
+
+<div class = "alert alert-info">
+El <a href="https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/">Cuadrante VTEX</a> es un programa exclusivo para partners de implementación en Brasil.
+</div>
+
diff --git a/docs/tracks/es/ad-types-classic-and-premium.md b/docs/tracks/es/ad-types-classic-and-premium.md
index 63325194a..30f5bd0e6 100644
--- a/docs/tracks/es/ad-types-classic-and-premium.md
+++ b/docs/tracks/es/ad-types-classic-and-premium.md
@@ -20,9 +20,9 @@ Los anuncios del tipo Clásico tienen como principal ventaja una menor tarifa po
 
 En la integración con VTEX, puede elegir anunciar sus productos en ambos formatos. Cada tipo de anuncio debe ser configurado por separado, siguiendo todos los pasos indicados en este tutorial.
 
-<img style="width:48%;" src="https:https://images.ctfassets.net/alneenqid6w5/65sXxgN6qA2i0faa1i3UqZ/db79bd4140d93a987ff0a9fa6e013aa6/mercadolivre-classic-pt.png"/>
+<img style="width:48%;" src="https://images.ctfassets.net/alneenqid6w5/65sXxgN6qA2i0faa1i3UqZ/db79bd4140d93a987ff0a9fa6e013aa6/mercadolivre-classic-pt.png"/>
 <span style="width:4%;"/>
-<img style="width:48%;" src="https:https://images.ctfassets.net/alneenqid6w5/2m56Xo8kVHJD8gQZZHTAKt/7cbfdb8a46cec1d825381c592783f053/mercadolivre-premium-pt.png"/>
+<img style="width:48%;" src="https://images.ctfassets.net/alneenqid6w5/2m56Xo8kVHJD8gQZZHTAKt/7cbfdb8a46cec1d825381c592783f053/mercadolivre-premium-pt.png"/>
 
 #### Más detalles sobre los tipos de anuncios
 
diff --git a/docs/tracks/es/add-on-products.md b/docs/tracks/es/add-on-products.md
new file mode 100644
index 000000000..990f2db66
--- /dev/null
+++ b/docs/tracks/es/add-on-products.md
@@ -0,0 +1,136 @@
+---
+title: 'Products Add-on'
+id: 1t2QBZvrOBSLgvHaAV9fYm
+status: PUBLISHED
+createdAt: 2024-02-20T20:29:42.983Z
+updatedAt: 2024-07-03T11:38:12.320Z
+publishedAt: 2024-07-03T11:38:12.320Z
+firstPublishedAt: 2024-02-22T14:09:28.506Z
+contentType: trackArticle
+productTeam: Others
+slug: products-add-on
+locale: es
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugES: proximos-pasos-tras-el-go-live
+---
+
+Los productos add-on son soluciones que VTEX ofrece para satisfacer demandas específicas de los negocios y que pueden adquirirse por separado mediante un contrato de suscripción.
+
+<div class="alert alert-warning">
+  <p>Para implementar las soluciones a continuación, debes ponerte en contacto con el equipo de<a href="https://help.vtex.com/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ"> soporte comercial de VTEX</a>.</p>
+</div>
+
+## VTEX Ad Network
+
+[VTEX Ad Network](https://help.vtex.com/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) conecta a retailers VTEX con marcas interesadas en anunciar sus productos. Con esta conexión, anunciantes y retailers VTEX pueden impulsar su negocio:
+
+- **Anunciantes:** marcas que pueden crear campañas de anuncios para promocionar productos en storefronts de tiendas VTEX que tengan esos mismos productos en sus catálogos, incrementando las ventas.
+- **Retailers:** son retailers que tienen tiendas VTEX que pueden ofrecer espacios en sus storefronts para que los anunciantes promocionen sus productos. Estos retailers recibirán una valor por cada clic recibido en anuncios de su tienda.
+
+![vtex_ad_network_sponsored_ES](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/bfec823e3960cac69bf878395437cdec/vtex_ad_network_sponsored.png)
+
+## VTEX Assisted Sales
+
+[Assisted Sales (SuiteShare)](https://help.vtex.com/es/tracks/suiteshare--khP0p8mjIYRIpvM7Cb4Zr/onWmyS8j4Thhde67UBBsB) es una solución creada por VTEX para potenciar las ventas en WhatsApp que ayuda a atraer nuevos clientes, integrar herramientas de ventas, gestionar datos de atención al usuario y métricas de resultados.
+
+![suiteshare-es](//images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/2e88a04abe0eeb3008df7f4bb0f87f49/next_steps_image11_ONLYPT.JPG)
+
+## VTEX Live Shopping
+VTEX Live Shopping permite crear transmisiones online para hacer demostraciones en vivo de las características de los productos de la tienda. Las interacciones directas e instantáneas con los clientes ayudan a mejorar el engagement del público con la marca y aumentar el rendimiento de ventas.
+
+![live-shopping-es](//images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/5db3287d499b2abdc4acfe7ef38689f7/next_steps_image5_ALL.JPG)
+
+Para programar una demostración de la aplicación con un especialista, debes acceder a la página de [VTEX Live Shopping](https://vtex.com/es-es/live-shopping/#contact).
+
+## VTEX Personal Shopper
+
+VTEX Personal Shopper permite ofrecer un servicio personalizado directo entre el cliente y el vendedor para incorporar la experiencia de la tienda física al entorno digital. Con esta aplicación el vendedor puede hacer demostraciones de productos, dar recomendaciones y aclarar las dudas de los clientes. Durante la videollamada se pueden agregar ítems al carrito.
+
+![personal-shopper-es](//images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/5ea754ef7cfe6f2f4a17db69964d8ca9/next_steps_image6_ALL.JPG)
+
+Para programar una demostración de la aplicación con un especialista, debes acceder a la página de [VTEX Personal Shopper](https://vtex.com/mx-es/vtex-personal-shopper/).
+
+## VTEX Pick and Pack
+VTEX Pick and Pack es una solución de gestión del proceso de fulfillment que proporciona visibilidad completa, desde el alistamiento y empaque de productos en las tiendas físicas o almacenes hasta la entrega en puntos de recogida o domicilio.
+
+La solución se compone de:
+
+- [Aplicación Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA): gestiona pedidos en la tienda o almacén, permitiendo personalizar el método de alistamiento de pedidos, seleccionar tipo de empaque por producto y remover o agregar productos según el stock de la tienda.
+
+- [Aplicación Last Mile](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): coordina el envío de paquetes desde los almacenes o tiendas a las direcciones de los clientes mediante la creación de rutas inteligentes de entrega, selección de conductores disponibles y seguimiento de la ubicación exacta del pedido.
+
+![pick-and-pack-es](//images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/2a0495961f4d1dd6024ab04af3af8893/next_steps_image7_ALL.JPG)
+
+Para ver una demostración de la aplicación o programar una sesión personalizada con un especialista, debes acceder a la página de [VTEX Pick and Pack](https://content.vtex.com/es/pick-and-pack/). 
+
+## VTEX Sales App
+
+Con [VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO) los vendedores de las tiendas físicas pueden aumentar su potencial de ventas mediante la integración de datos de stock entre tiendas físicas y online a la vez que ofrecen al cliente un seguimiento completo presencial sobre el proceso de compra. La aplicación puede utilizarse para:
+
+- Acceder a la información y vender productos que estén en la propia tienda o en otras ubicaciones, tales como sucursales, socios o centros de distribución ([pasillo infinito](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn)).
+- Sugerir productos según el perfil del cliente.
+
+- Ofrecer opciones de entrega instantánea, recogida programada o entrega a domicilio del cliente.
+
+- Gestionar métricas de rendimiento por vendedor.
+
+![sales-app-es](//images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/fdac94d9c5de3a71957368c552b3cecd/image3.png)
+
+Para ver una demostración de la aplicación o programar una sesión personalizada con un especialista, debes acceder a la página de [VTEX Sales App](https://assets.vtex.com/es-sales-app/).
+
+## VTEX Shipping Network
+
+Explora las opciones de envío de productos a todas las regiones de Brasil con [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) y **VTEX Shipping Network Correios**.
+
+**VTEX Shipping Network** permite conectar transportadoras para crear una red de entrega integrada, que actualmente cuenta con más de 20 socios, para ofrecer a los clientes mejores opciones de costo y plazo.
+
+![shipping-network-es](//images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/5fec34d4b9279162c37ff9efff927a49/image7.png)
+
+Para más información, debes acceder a la página de VTEX Shipping Network.
+
+<div class="alert alert-warning">
+  <p>Las soluciones <strong>VTEX Shipping Network</strong> y <strong>VTEX Shipping Network Correios</strong> son exclusivas para las operaciones en Brasil.</p>
+</div>
+
+## VTEX Shipping Network Correios (solo Brasil)
+
+[VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) es una asociación entre VTEX y Correios en la que la tienda puede contratar servicios de envío de productos a través de PAC y SEDEX directamente en el Admin VTEX, con tarifas especiales que reducen los costos operativos del envío.
+
+![image6](//images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/536e7173450c2b066da7ef539baf8e19/image6.png)
+
+Contratar la solución es simple y solo toma unos pocos minutos: basta con aceptar los Términos y condiciones y la [activación](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) directamente en el Admin de la tienda. Algunas de las funcionalidades de VTEX Shipping Network Correios son:
+
+- Sincronización de las tablas de envío entre Correios y VTEX. Las actualizaciones de datos realizadas por Correios se muestran automáticamente en el entorno VTEX.
+
+- El seguimiento de envío se añade y actualiza automáticamente en los pedidos.
+
+- Las etiquetas de envío se pueden imprimir desde el Admin VTEX (en la página [Pronto para Envio](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs)) o por [API](https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration) para las integraciones con sistemas externos (como ERP o WMS).
+
+- Canal de comunicación directa con Correios dentro del Admin a través de [Pedido de informações](https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq#solicitar-informacoes-do-pedido-aos-correios).
+
+Para más información, debes acceder a la página de [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/).
+
+## VTEX Shield
+
+[VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) ofrece capas de protección adicionales y personalizables para tiendas que priorizan la resiliencia de la plataforma, además de los estándares de seguridad garantizados por las certificaciones y [prácticas de seguridad](https://vtex.com/mx-es/security/security-practices/) existentes en VTEX.
+
+Al contratar VTEX Shield tienes la opción de elegir entre las siguientes funcionalidades:
+
+* [Security Monitor](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#security-monitor)
+* [Pruebas de penetración](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#pruebas-de-penetracion)
+* [Web Application Firewall (WAF)](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#web-application-firewall-waf)
+
+## VTEX WhatsApp AI Campaigns
+[WhatsApp AI Campaigns](https://help.vtex.com/es/tutorial/recupere-checkouts-abandonados-com-whatsapp-ai-campaigns--20i0zLQHt72LKzVEmk1CRZ?&utm_source=autocomplete) es una funcionalidad desarrollada por VTEX para recuperar checkouts abandonados. 
+
+Cuando un usuario abandona la página de checkout de la compra, la plataforma identifica esta acción. Si el usuario no regresa para completar la compra en el plazo de una hora, la funcionalidad le envía un recordatorio a través de WhatsApp.
+
+Los principales beneficios de la funcionalidad son:
+
+- **Mejora de la experiencia del cliente:** los mensajes pueden personalizarse para aumentar la relevancia y reforzar la relación con la marca.
+
+**Aumento de las tasas de conversión y ventas:** incentiva a los clientes a volver a la página de checkout para finalizar su compra, aumentando así las ventas y las tasas de conversión de los retailers.
+
+<div class = "alert alert-info">
+WhatsApp AI Campaigns solamente está disponible para tiendas que utilizan <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> y no tienen personalizaciones en Checkout.
+</div>
diff --git a/docs/tracks/es/add-pickup-points.md b/docs/tracks/es/add-pickup-points.md
index b929226e5..1a34a38fd 100644
--- a/docs/tracks/es/add-pickup-points.md
+++ b/docs/tracks/es/add-pickup-points.md
@@ -33,7 +33,7 @@ Siga el siguiente procedimiento para registrar un punto de recogida en su tienda
 4. Rellene los campos del formulario de punto de recogida. Para entender mejor el significado de cada campo, consulte la sección [Campos de registro](#campos-de-registro), abajo.
 5. Haga clic en el botón **Guardar cambios**
 
-![ES Cadastrar Ponto de Retirada GIF](https://images.ctfassets.net/alneenqid6w5/1tWiezGUaoTRohpM2m5241/f1dfb789d45d72d8054f0f4ccebe740b/ES_Cadastrar_Ponto_de_Retirada_GIF.gif)
+![ES Cadastrar Ponto de Retirada GIF](//images.ctfassets.net/alneenqid6w5/1tWiezGUaoTRohpM2m5241/f1dfb789d45d72d8054f0f4ccebe740b/ES_Cadastrar_Ponto_de_Retirada_GIF.gif)
 
 
 ### Campos de registro
diff --git a/docs/tracks/es/add-sku-specifications.md b/docs/tracks/es/add-sku-specifications.md
index ad9d4547d..860c56cbb 100644
--- a/docs/tracks/es/add-sku-specifications.md
+++ b/docs/tracks/es/add-sku-specifications.md
@@ -35,7 +35,7 @@ Para registrar las especificaciones, su tienda necesita tener departamentos, cat
  7. Rellene los campos del formulario de especificaciones. En el caso de los SKUs, el flag de campo obligatorio siempre está seleccionado por default. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre [cómo rellenar los campos de especificaciones de SKU](https://help.vtex.com/es/tutorial/criando-campo-de-sku--tutorials_119)
  8.  Haga clic en **Guardar**
 
-![ES1](https://images.ctfassets.net/alneenqid6w5/4cSrsR60RiWrSSllCFgbsQ/2d8e6ffab449e23f59c3521e67764568/ES1.gif)
+![ES1](//images.ctfassets.net/alneenqid6w5/4cSrsR60RiWrSSllCFgbsQ/2d8e6ffab449e23f59c3521e67764568/ES1.gif)
 
 Para añadir valores a la especificación de SKU, siga los siguientes pasos:
 
@@ -49,7 +49,7 @@ Para añadir valores a la especificación de SKU, siga los siguientes pasos:
  9. Haga clic en **Nuevo valor**
  10. Escriba el **Nombre** del valor deseado y haga clic en **Guardar**
 
-![ES2](https://images.ctfassets.net/alneenqid6w5/7v4nItIFqlZZP6SVOhVlcf/2e81e722d6f6c69a3e551ddc5c221bec/ES2.gif)
+![ES2](//images.ctfassets.net/alneenqid6w5/7v4nItIFqlZZP6SVOhVlcf/2e81e722d6f6c69a3e551ddc5c221bec/ES2.gif)
 
 ### Vincular las especificaciones a un SKU
 
@@ -65,7 +65,7 @@ Para incluir las especificaciones en un **SKU** siga los siguientes pasos:
  6. Haga clic en la pestaña **Especificaciones** y seleccione el valor de la especificación para ese SKU
  7. Haga clic en **Guardar**
 
-![ES3](https://images.ctfassets.net/alneenqid6w5/2r7p71kBKd70qbLDu7EJBS/c10904a508a3a2e5baf02c2a22288c8a/ES3.gif)
+![ES3](//images.ctfassets.net/alneenqid6w5/2r7p71kBKd70qbLDu7EJBS/c10904a508a3a2e5baf02c2a22288c8a/ES3.gif)
 
 ## Plantilla
 
@@ -94,7 +94,7 @@ Después de rellenar los datos de la plantilla, siga el procedimiento para impor
 5. Haga clic en **Select** para seleccionar la plantilla rellenada
 6. Haga clic en **Importar**
 
-![ES4](https://images.ctfassets.net/alneenqid6w5/7gytIVRaKu9gmvZXlIyfe2/073d2f187de623baf5bb44a89615e5e1/ES4.gif)
+![ES4](//images.ctfassets.net/alneenqid6w5/7gytIVRaKu9gmvZXlIyfe2/073d2f187de623baf5bb44a89615e5e1/ES4.gif)
 
 ## API
 
diff --git a/docs/tracks/es/adding-a-fixed-price.md b/docs/tracks/es/adding-a-fixed-price.md
index 55bd681fc..534e53581 100644
--- a/docs/tracks/es/adding-a-fixed-price.md
+++ b/docs/tracks/es/adding-a-fixed-price.md
@@ -1,10 +1,10 @@
 ---
 title: 'Registrar precio fijo'
 id: 3g39iXkQza4AW7C7L814mj
-status: CHANGED
+status: PUBLISHED
 createdAt: 2019-07-04T13:53:38.630Z
-updatedAt: 2023-03-29T21:16:34.391Z
-publishedAt: 2023-03-29T18:18:57.294Z
+updatedAt: 2024-05-15T16:01:59.100Z
+publishedAt: 2024-05-15T16:01:59.100Z
 firstPublishedAt: 2019-07-17T19:46:38.452Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -54,7 +54,7 @@ Para eliminar un precio fijo existente, sigue los pasos que se indican a continu
 5. Haz clic en el botón `Eliminar`.
 
 ## Pricing API
-Para registrar un precio fijo mediante API, utiliza el endpoint [Create or update base or fixed prices](https://developers.vtex.com/vtex-rest-api/reference/prices-and-fixed-prices#createupdatepriceorfixedprice) de la Pricing API.
+Para registrar un precio fijo mediante API, utiliza el endpoint [Create or update base or fixed prices](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-) de la Pricing API.
 
 ### Más información
 * [Programar precio](https://help.vtex.com/es/tutorial/programar-precio--4vVha6TGzYkguWuMOqCcCk)
diff --git a/docs/tracks/es/adding-a-loading-dock.md b/docs/tracks/es/adding-a-loading-dock.md
index bdc71b79b..077d04b2d 100644
--- a/docs/tracks/es/adding-a-loading-dock.md
+++ b/docs/tracks/es/adding-a-loading-dock.md
@@ -28,7 +28,7 @@ Siga el procedimiento a continuación para registrar un muelle en su tienda:
 4. Rellene los campos del formulario de registro. Para comprender mejor el significado de cada campo, consulte a continuación la sección [Campos de Registro] (#campos-de-registro).
 5. Haga clic en el botón **Guardar**.
 
-![ES Cadastrar Doca GIF](https://images.ctfassets.net/alneenqid6w5/1nWWY7VL7GvqTA3s9TuQ3Z/470d02a8d6a602066a4585fd3db15208/ES_Cadastrar_Doca_GIF.gif)
+![ES Cadastrar Doca GIF](//images.ctfassets.net/alneenqid6w5/1nWWY7VL7GvqTA3s9TuQ3Z/470d02a8d6a602066a4585fd3db15208/ES_Cadastrar_Doca_GIF.gif)
 
 ### Campos de registro
 
diff --git a/docs/tracks/es/adding-a-price-rule.md b/docs/tracks/es/adding-a-price-rule.md
index f505ff50a..f0c045198 100644
--- a/docs/tracks/es/adding-a-price-rule.md
+++ b/docs/tracks/es/adding-a-price-rule.md
@@ -3,8 +3,8 @@ title: 'Registrar Regla de Precio'
 id: 7fyZaYe1IGzL0qVC28tOBO
 status: PUBLISHED
 createdAt: 2019-07-04T13:53:15.461Z
-updatedAt: 2023-03-29T18:50:59.023Z
-publishedAt: 2023-03-29T18:50:59.023Z
+updatedAt: 2023-08-21T17:10:07.115Z
+publishedAt: 2023-08-21T17:10:07.115Z
 firstPublishedAt: 2019-07-17T19:42:10.960Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Siga el procedimiento a continuación para registrar la regla de precio de su ti
 
 ## Admin
 
-1. En el Admin VTEX, accede a *Precios > Reglas de precios* , o escribe *Reglas de precios* en la barra de búsqueda en la parte superior de la página.
+1. En el Admin VTEX, accede a **Precios > Reglas de precios** , o escribe **Reglas de precios** en la barra de búsqueda en la parte superior de la página.
 2. Haga clic en el botón verde **Nueva Regla**.
 3. En el primer paso, **¿Cuáles son los datos generales de esta regla?**, seleccione en el *dropdown* una tabla de precios. 
 4. En el segundo paso, **¿En cuáles ítems esta regla se aplicará?**, seleccione si la regla se va a *Aplicar en todos los productos* o *Apenas en categorías y marcas escogidas*. Si se selecciona la segunda opción, debe escoger las **Categorías** y/o **Marcas** deseadas. 
diff --git a/docs/tracks/es/adding-extra-text-to-the-order-print.md b/docs/tracks/es/adding-extra-text-to-the-order-print.md
index ffcc7fdaf..5e86c6feb 100644
--- a/docs/tracks/es/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/es/adding-extra-text-to-the-order-print.md
@@ -38,7 +38,7 @@ Después de volver a cargar inStore, cada vez que un vendedor imprima un pedido,
 
 Antes de agregar texto adicional, la impresión del resumen del pedido tiene el siguiente formato:
 
-![28. Adding extra text to the order print - 1](https://images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
+![28. Adding extra text to the order print - 1](//images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
 
 En nuestro ejemplo, cambiamos el archivo `checkout-instore-custom.js` insertando el siguiente texto adicional:
 
@@ -50,4 +50,4 @@ window.INSTORE_CONFIG = {
 
 Ahora, cada vez que se imprima un resumen del pedido, obtendremos el siguiente resultado:
 
-![28. Adding extra text to the order print - 2](https://images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
+![28. Adding extra text to the order print - 2](//images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
diff --git a/docs/tracks/es/adding-new-stores-to-instore.md b/docs/tracks/es/adding-new-stores-to-instore.md
index f482678d6..ad39f9e9a 100644
--- a/docs/tracks/es/adding-new-stores-to-instore.md
+++ b/docs/tracks/es/adding-new-stores-to-instore.md
@@ -3,8 +3,8 @@ title: 'Gestionar tiendas físicas en VTEX Sales App'
 id: 5PSjRstg7UU4lOm0s8aqKN
 status: PUBLISHED
 createdAt: 2020-06-29T13:30:51.354Z
-updatedAt: 2023-05-31T15:07:31.507Z
-publishedAt: 2023-05-31T15:07:31.507Z
+updatedAt: 2023-07-26T18:59:24.074Z
+publishedAt: 2023-07-26T18:59:24.074Z
 firstPublishedAt: 2020-06-29T14:22:11.121Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugES: instore-primeros-pasos-y-configuracion
 
 Después de realizar las [configuraciones básicas de inStore en el Admin](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), puede añadir otras tiendas físicas al sistema o gestionar tiendas ya registrados.
 
-**Tienda física** es una de las páginas de **Configuración de la tienda** del Admin VTEX que muestra una lista de tiendas físicas registradas en la aplicación [inStore](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). En ella, puedes gestionar la información de todas las tiendas físicas de la cuenta.
+**Tienda física** es una de las páginas de **Configuración de la tienda** del Admin VTEX que muestra una lista de tiendas físicas registradas en la aplicación [VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). En ella, puedes gestionar la información de todas las tiendas físicas de la cuenta.
 
 Esta página te permite realizar las siguientes acciones: 
 
@@ -25,7 +25,7 @@ Esta página te permite realizar las siguientes acciones:
 * [Editar](#editar-tienda-física)
 * [Inativar](#inativar-tienda-física)
 
-![loja-fisica-ES](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
+![loja-fisica-ES](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
 
 La página contiene la siguiente información:
 
@@ -50,7 +50,7 @@ Puedes crear una tienda física siguiendo los pasos a continuación:
 
 ### Campos de registro de la tienda física
 
-![loja-fisica2-es](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
+![loja-fisica2-es](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
 
 #### Identificación
 
diff --git a/docs/tracks/es/adding-product-specifications.md b/docs/tracks/es/adding-product-specifications.md
index ab207bb0d..c0f0667e0 100644
--- a/docs/tracks/es/adding-product-specifications.md
+++ b/docs/tracks/es/adding-product-specifications.md
@@ -35,7 +35,7 @@ Para registrar las especificaciones, su tienda necesita tener departamentos, cat
  7. Rellene los campos del formulario de especificaciones. Para comprender mejor el significado de cada campo, acceda a nuestro  artículo sobre [cómo rellenar los campos de especificaciones de producto](https://help.vtex.com/es/tutorial/creando-un-campo-de-producto--tutorials_106)
  8.  Haga clic en **Guardar**.
 
-![ES1](https://images.ctfassets.net/alneenqid6w5/26nmolyzhktK7RHFRIfeGn/bd9cc1425426b6f32212083f98760014/ES1.gif)
+![ES1](//images.ctfassets.net/alneenqid6w5/26nmolyzhktK7RHFRIfeGn/bd9cc1425426b6f32212083f98760014/ES1.gif)
 
 Para añadir valores a la especificación de un producto, siga los pasos a continuación:
 
@@ -49,7 +49,7 @@ Para añadir valores a la especificación de un producto, siga los pasos a conti
  9. Haga clic en **Nuevo valor**.
 10. Escriba el **Nombre** del valor deseado y haga clic en **Guardar**.
 
-![ES2](https://images.ctfassets.net/alneenqid6w5/1t2mGbtHaq6Koiz4anwOOO/79b47af516682cb283ccf2faf605af4d/ES2.gif)
+![ES2](//images.ctfassets.net/alneenqid6w5/1t2mGbtHaq6Koiz4anwOOO/79b47af516682cb283ccf2faf605af4d/ES2.gif)
 
 ### Vincular las especificaciones a un producto
 
@@ -63,7 +63,7 @@ Para incluir las especificaciones en un **Producto** siga los siguientes pasos:
  4. Haga clic en la pestaña **Especificaciones** y elija el valor de la especificación para este producto.
  5. Haga clic en la pestaña **Producto** y después haga clic en **Guardar**.
 
-![ES3](https://images.ctfassets.net/alneenqid6w5/1PVutb4VQX4Tbt8VuRzxNA/348cf9167307462767ae79b1f5887105/ES3.gif)
+![ES3](//images.ctfassets.net/alneenqid6w5/1PVutb4VQX4Tbt8VuRzxNA/348cf9167307462767ae79b1f5887105/ES3.gif)
 
 ## Plantilla
 
@@ -92,7 +92,7 @@ Después de rellenar los datos de la plantilla, siga este procedimiento para imp
 5. Haga clic en **Select** para seleccionar la plantilla de importación.
 6. Haga clic en **Importar**.
 
-![ES4](https://images.ctfassets.net/alneenqid6w5/3yZtK0w9QXrf3kBV0UfWq0/e65a0dad3840a0adee367c503b781233/ES4.gif)
+![ES4](//images.ctfassets.net/alneenqid6w5/3yZtK0w9QXrf3kBV0UfWq0/e65a0dad3840a0adee367c503b781233/ES4.gif)
 
 ## API
 
diff --git a/docs/tracks/es/adding-products.md b/docs/tracks/es/adding-products.md
index 6f3399871..046213004 100644
--- a/docs/tracks/es/adding-products.md
+++ b/docs/tracks/es/adding-products.md
@@ -30,7 +30,7 @@ En el Admin VTEX, realice los siguientes pasos:
 4. Rellene los campos del formulario de producto. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre los [campos de registro de producto](https://help.vtex.com/es/tutorial/campos-de-registro-de-producto--4dYXWIK3zyS8IceKkQseke).
 5. Haga clic en `Guardar` o `Guardar y registrar nuevo SKU`, si quiere agregar SKUs asociados a este producto.
 
-![Catalogo - Cadastrar produto ES.gif?h=250](https://images.ctfassets.net/alneenqid6w5/IaFCYaexWNcL8nMvkI1Ya/1704449927dee788756723f216072b92/Catalogo_-_Cadastrar_produto_ES.gif_h_250)
+![Catalogo - Cadastrar produto ES.gif?h=250](//images.ctfassets.net/alneenqid6w5/IaFCYaexWNcL8nMvkI1Ya/1704449927dee788756723f216072b92/Catalogo_-_Cadastrar_produto_ES.gif_h_250)
 
 ## Plantilla
 
diff --git a/docs/tracks/es/adding-skus.md b/docs/tracks/es/adding-skus.md
index 1659cdd55..2449b5b5e 100644
--- a/docs/tracks/es/adding-skus.md
+++ b/docs/tracks/es/adding-skus.md
@@ -25,7 +25,7 @@ Existen dos flujos de registro de SKU por el admin: luego de registrar un produc
 ### Registrar SKU luego del registro de un producto
 
 1. En la pantalla de registro de Producto, después de rellenar los campos, haga clic en `Guardar y Crear SKU`.
-  ![1foto.es](https://images.ctfassets.net/alneenqid6w5/5lYrKBh17OA6yUU5HHdZO7/cd48c8350405235a7526b16c0248083f/1foto.es.png)
+  ![1foto.es](//images.ctfassets.net/alneenqid6w5/5lYrKBh17OA6yUU5HHdZO7/cd48c8350405235a7526b16c0248083f/1foto.es.png)
 2. Usted será redirigido a la pantalla de registro de SKU. Rellene los campos del formulario de SKU. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre [cómo rellenar los campos de registro de SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY).
 3. Haga clic en `Guardar`.
 
@@ -43,7 +43,7 @@ Existen dos flujos de registro de SKU por el admin: luego de registrar un produc
 Después del registro de un SKU, es necesario agregar una imagen para que se active. Para esto, realice el siguiente procedimiento:
 
 1. En la página de registro de SKU, haga clic en la pestaña **Imágenes**.
-  ![6foto.es](https://images.ctfassets.net/alneenqid6w5/5AgORlEQzTGpvxSKSuGUl7/f363abad82ee975e0a0dab1448f47348/6foto.es.png)
+  ![6foto.es](//images.ctfassets.net/alneenqid6w5/5AgORlEQzTGpvxSKSuGUl7/f363abad82ee975e0a0dab1448f47348/6foto.es.png)
 2. Haga clic en `Insertar` y elija la imagen deseada.
 3. Rellene los campos **Texto** (tag alt de la imagen) y **Label** (la “etiqueta” utilizada para facilitar la organización del template de las páginas de su sitio web, a través de la referencia del valor rellenado en esta. Ej.: Frontal, lateral, superior, etc.)
 4. Haga clic en `Enviar`.
@@ -53,7 +53,7 @@ Después del registro de un SKU, es necesario agregar una imagen para que se act
 Después de registrar las imágenes, debe registrar las especificaciones del SKU. El registro de las especificaciones se detallará en el próximo paso de esta guía. 
 
 1. Haga clic en la pestaña **Especificaciones**.
-  ![7foto.es](https://images.ctfassets.net/alneenqid6w5/3OdYoTaGUSznx0PsVyrKaX/b89adf4357e466db3d9a9efcb3109b4d/7foto.es.png)
+  ![7foto.es](//images.ctfassets.net/alneenqid6w5/3OdYoTaGUSznx0PsVyrKaX/b89adf4357e466db3d9a9efcb3109b4d/7foto.es.png)
 2. Rellene los campos solicitados. Los valores de las especificaciones se configuran en el nivel de la Categoría.
 3. Haga clic en `Guardar`.
 
diff --git a/docs/tracks/es/adding-vendors.md b/docs/tracks/es/adding-vendors.md
index 2a1139735..12837bf9f 100644
--- a/docs/tracks/es/adding-vendors.md
+++ b/docs/tracks/es/adding-vendors.md
@@ -18,7 +18,7 @@ Si usted ha configurado su tienda utilizando el flujo de __Easy Setup__, tal vez
 
 Al entrar en el VTable (https://{{AccountName}}.myvtex.com/admin/vtable) usted verá dos aplicaciones, __Admin de las tiendas__ y __Admin de los vendedores__:
 
-![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Haga clic en __Admin de los vendedores__ para abrir la tabla donde incluiremos un nuevo vendedor.
 
@@ -26,7 +26,7 @@ En el caso de que ya haya registrado un vendedor a través del __Easy Setup__, s
 
 > __IMPORTANTE__: el e-mail de cada vendedor __NO__ puede ser el mismo utilizado en la plataforma VTEX, porque su e-mail de administrador tiene permisos que un vendedor no debería tener, por lo que es necesario utilizar algún otro e-mail sin privilegios en la plataforma.
 
-![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
+![inStore adicionando vendedor](//images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
 Si ha saltado el paso de creación de vendedor en el __Easy Setup__ y no tiene ningún vendedor creado, usted necesitará recoger el ID de __Tienda__ en el __Admin de las Tiendas__ en el VTable.
 
diff --git a/docs/tracks/es/adding-warehouses.md b/docs/tracks/es/adding-warehouses.md
index 0868b53ca..6556b8b70 100644
--- a/docs/tracks/es/adding-warehouses.md
+++ b/docs/tracks/es/adding-warehouses.md
@@ -29,7 +29,7 @@ Siga el siguiente procedimiento para registrar un inventario en su tienda:
 4. Rellene los campos del formulario de inventario. Para entender mejor el significado de cada campo, consulte abajo la sección [Campos de Registro](#campos-de-registro).
 5. Haga clic en el botón **Guardar**
 
-![ES Cadastrar Estoque GIF](https://images.ctfassets.net/alneenqid6w5/29hDNueQOJgRlg6rLIk8T5/ee2fba7fcb9da60690df299825e0cdef/ES_Cadastrar_Estoque_GIF.gif)
+![ES Cadastrar Estoque GIF](//images.ctfassets.net/alneenqid6w5/29hDNueQOJgRlg6rLIk8T5/ee2fba7fcb9da60690df299825e0cdef/ES_Cadastrar_Estoque_GIF.gif)
 
 ### Campos de registro
 
diff --git a/docs/tracks/es/allowing-order-replacement.md b/docs/tracks/es/allowing-order-replacement.md
index cdf91b187..b20af354e 100644
--- a/docs/tracks/es/allowing-order-replacement.md
+++ b/docs/tracks/es/allowing-order-replacement.md
@@ -3,8 +3,8 @@ title: 'Permitir sustitución de pedido'
 id: 381eYJw7lrypjGq3hmPtGV
 status: PUBLISHED
 createdAt: 2019-11-18T11:57:28.677Z
-updatedAt: 2023-03-31T22:52:53.575Z
-publishedAt: 2023-03-31T22:52:53.575Z
+updatedAt: 2024-04-01T17:58:20.948Z
+publishedAt: 2024-04-01T17:58:20.948Z
 firstPublishedAt: 2019-11-18T12:20:58.872Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -18,6 +18,10 @@ La **Sustitución de pedidos** permite a los clientes de su tienda cambiar los d
 
 El objetivo es ayudarlos a corregir errores sin tener que realizar manualmente un nuevo pedido o contactar a su soporte, lo que facilita el funcionamiento de su tienda y reduce costos.
 
+<div class = "alert alert-warning">
+No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
+</div>
+
 ## Habilitación de la sustitución de pedidos
 
 La funcionalidad está disponible para todas las tiendas. Para habilitarla, sigue los pasos a continuación:
diff --git a/docs/tracks/es/amazon-account-settings.md b/docs/tracks/es/amazon-account-settings.md
index dfc4b606b..85def77df 100644
--- a/docs/tracks/es/amazon-account-settings.md
+++ b/docs/tracks/es/amazon-account-settings.md
@@ -1,9 +1,9 @@
 ---
 title: 'Configuración de la cuenta de Amazon'
 id: 43L0dpbjLBz6tcim1BbTzf
-status: PUBLISHED
+status: CHANGED
 createdAt: 2019-02-28T23:01:18.628Z
-updatedAt: 2023-03-08T20:38:03.932Z
+updatedAt: 2023-11-09T22:36:18.079Z
 publishedAt: 2023-03-08T20:38:03.932Z
 firstPublishedAt: 2019-02-28T23:02:20.905Z
 contentType: trackArticle
diff --git a/docs/tracks/es/amazon.md b/docs/tracks/es/amazon.md
index d62172a7d..547cebd49 100644
--- a/docs/tracks/es/amazon.md
+++ b/docs/tracks/es/amazon.md
@@ -16,7 +16,7 @@ trackSlugES: integracion-de-amazon
 
 Amazon es una plataforma de ecommerce y se le considera una de las cinco mayores empresas de tecnología del mundo. Actualmente, Amazon vende una gran variedad de productos, como juguetes, productos electrónicos, ropa y accesorios, entre otros. Además, la empresa de comercio minorista online ofrece servicios de streaming, almacenamiento en la nube y asistentes virtuales.
 
-![amazon logo](https://images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
+![amazon logo](//images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
 
 La configuración con Amazon tiene como objetivo enviar el catálogo de productos de su tienda VTEX a este marketplace, permitiéndole anunciar sus productos y aumentar sus ventas. 
 
diff --git a/docs/tracks/es/apple-pay.md b/docs/tracks/es/apple-pay.md
new file mode 100644
index 000000000..1083dcbd5
--- /dev/null
+++ b/docs/tracks/es/apple-pay.md
@@ -0,0 +1,53 @@
+---
+title: 'Apple Pay'
+id: STKWiXJSR9ImPt5EEC2aL
+status: PUBLISHED
+createdAt: 2023-06-28T14:04:58.979Z
+updatedAt: 2024-06-25T21:02:43.540Z
+publishedAt: 2024-06-25T21:02:43.540Z
+firstPublishedAt: 2023-06-28T14:13:24.803Z
+contentType: trackArticle
+productTeam: Shopping
+slug: apple-pay
+locale: es
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugES: cartera-digital-e-wallet
+---
+
+Sus clientes pueden comprar con Apple Pay, la [cartera digital](https://help.vtex.com/es/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/7jLbdfch9Oe2yYbQa9zwE1) de Apple. Para ello, usted necesita cumplir algunos requisitos:
+
+- Tener cuenta en `developer.apple.com`.
+- Tener contrato con un proveedor que procese pagos con Apple Pay.
+
+<div class="alert alert-warning">
+  Actualmente, Apple Pay solo funciona en los sistemas operativos MacOs e IOS, y en el navegador Safari. Para obtener más información, vaya a <a href="https://support.apple.com/es-es/HT208531">Dispositivos compatibles con Apple Pay</a>.
+</div>
+
+## Configurar proveedor de pago
+
+En primer lugar, debes configurar un proveedor en el Admin de tu tienda que procese transacciones con Apple Pay, como [Adyen](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3--7xAz67E2Eg63LWCQNjVdwv) y [Stripe](https://help.vtex.com/es/tutorial/configurar-la-afiliacion-stripe--fwF2wk2FQKrODrWWkvSLO).
+
+Para consultar todas las opciones de proveedores disponibles para este método de pago, acceda a la lista como se describe en el Paso 5 de la sección [Configurar el pago con Apple Pay](#configurar-el-pago-con-apple-pay).
+
+<div class="alerta alerta-advertencia">
+  Antes de comenzar a configurar el proveedor, debe <a href="register your Merchant ID with Apple Pay">registrar su Merchant ID con Apple Pay</a>.
+</div>
+
+## Configurar el pago con Apple Pay
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en la pestaña __Condiciones de pago__ y, a continuación, en el botón `+`.
+3. Seleccione el medio de pago __Apple Pay__.
+4. Haga clic en el botón `Status` para activar esta condición de pago.
+5. En el campo __Procesar con proveedor__, seleccione el proveedor que se va a utilizar para procesar los pagos.
+6. Si hay un antifraude configurado en su tienda, usted puede activarlo para esta condición de pago marcando la casilla __Utilizar antifraude__.
+7. Elija si desea que los pagos se realicen en efectivo o parcelados.
+8. Si lo desea, también puede optar por una [condición especial de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+9. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Apple Pay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
+
+### Artículos relacionados
+
+- [Configurar Merchant ID en Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay)
+- [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456)
diff --git a/docs/tracks/es/associating-a-template-with-a-layout.md b/docs/tracks/es/associating-a-template-with-a-layout.md
index 111f6555d..bb6e50d01 100644
--- a/docs/tracks/es/associating-a-template-with-a-layout.md
+++ b/docs/tracks/es/associating-a-template-with-a-layout.md
@@ -29,4 +29,4 @@ Esta asociación se realiza en la configuración de las propiedades del layout.
 5. Haga clic en el menú desplegable __Template__. Ahí se listarán los templates configurados en HTML Templates.
 6. Seleccione el template que desea asociar a este layout.
 7. Digite "yes" para confirmar el cambio (este paso es necesario porque se trata de un cambio crítico para el sitio web, ya que el front-end de la página será reemplazado). 
-![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tracks/es/autocomplete-search.md b/docs/tracks/es/autocomplete-search.md
index d3cd7aaa4..a2c053bae 100644
--- a/docs/tracks/es/autocomplete-search.md
+++ b/docs/tracks/es/autocomplete-search.md
@@ -53,22 +53,22 @@ Otra ventaja para el administrador de la tienda es el aumento de conversión, qu
 
 En esta sección se muestran los términos más buscados por otros clientes dentro del sitio web.
 
-![PT - Autocomplete termos mais pesquisados](https://images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
 
 ## Últimas búsquedas realizadas
 
 En esta sección se muestran las últimas búsquedas realizadas por el cliente. Así, es posible comenzar la interacción con la búsqueda instantáneamente.
 
-![PT - Autocomplete historico](https://images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
 
 ## Sugerencia de búsquedas
 
 En esta sección se muestran los términos buscados por otros usuarios que se relacionan con la búsqueda realizada en ese momento. Además de términos, también se sugieren categorías relacionadas con la búsqueda.
 
-![PT - Autocomplete sugestao termos](https://images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
 
 ## Sugerencia de productos
 
 En esta sección se muestran los productos que coinciden con la búsqueda realizada en ese momento. Así, al mostrar productos relacionados con su búsqueda durante la escritura, se reducen las interrupciones y se le permite al usuario realizar una compra más dinámica.
 
-![PT - Autocomplete sugestao de produtos](https://images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
+![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tracks/es/availability.md b/docs/tracks/es/availability.md
index bf8f19caa..2da638c6e 100644
--- a/docs/tracks/es/availability.md
+++ b/docs/tracks/es/availability.md
@@ -3,8 +3,8 @@ title: 'Disponibilidad'
 id: 7LMQbWK5nElIkXo0NK8Kux
 status: PUBLISHED
 createdAt: 2021-10-04T18:01:24.137Z
-updatedAt: 2021-10-04T18:18:56.501Z
-publishedAt: 2021-10-04T18:18:56.501Z
+updatedAt: 2023-12-07T19:28:15.731Z
+publishedAt: 2023-12-07T19:28:15.731Z
 firstPublishedAt: 2021-10-04T18:18:56.501Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ trackSlugES: vtex-intelligent-search
 
 Al elaborar un resultado de búsqueda, VTEX Intelligent Search tiene en cuenta la disponibilidad de cada producto encontrado en la búsqueda. Los productos disponibles siempre tendrán prioridad sobre los no disponibles en los resultados de búsqueda. 
 
-Al verificar la disponibilidad del producto, VTEX Intelligent Search utiliza el campo **Mostrar producto agotado** registrado en el [Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) para saber qué productos se mostrarán aunque no estén disponibles. Si la configuración del producto define que no se mostrará si está agotado, la plataforma lo situará al final del resultado de búsqueda. VTEX Intelligent Search también verifica si:
+Al verificar la disponibilidad del producto, VTEX Intelligent Search utiliza el campo **Mostrar producto agotado** registrado en el [Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) para saber qué productos se mostrarán aunque no estén disponibles. Si la configuración del producto determina que no debe mostrarse cuando esté fuera de stock, la plataforma no presentará el producto. Sin embargo, si la configuración indica que el producto debe mostrarse incluso cuando esté sin stock, la plataforma lo colocará al final de los resultados de búsqueda. VTEX Intelligent Search también verifica si:
 
 - El producto en cuestión está activo.
 - Al menos un SKU del producto está activo.
diff --git a/docs/tracks/es/b2b-form.md b/docs/tracks/es/b2b-form.md
index 409d03121..32172e74d 100644
--- a/docs/tracks/es/b2b-form.md
+++ b/docs/tracks/es/b2b-form.md
@@ -46,12 +46,12 @@ Ejemplos de cómo queda en el inStore el formulario con persona jurídica:
 
 __Formulario B2B__ - opcional y cerrado:
 
-![b2b-opcional-fechado](https://images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
+![b2b-opcional-fechado](//images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
 
 __Formulario B2B__ - opcional y abierto:
 
-![b2b-opcional-aberto](https://images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
+![b2b-opcional-aberto](//images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
 
 __Formulario B2B__ - obligatorio (ya vienen todos los campos abiertos):
 
-![b2b-obrigatorio](https://images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
+![b2b-obrigatorio](//images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
diff --git a/docs/tracks/es/backend-integrations.md b/docs/tracks/es/backend-integrations.md
new file mode 100644
index 000000000..f4320f53f
--- /dev/null
+++ b/docs/tracks/es/backend-integrations.md
@@ -0,0 +1,406 @@
+---
+title: 'Integraciones de backend '
+id: 7euXDZR5CCnVFSrXyczIhu
+status: PUBLISHED
+createdAt: 2024-02-05T13:23:32.848Z
+updatedAt: 2024-02-23T02:06:48.878Z
+publishedAt: 2024-02-23T02:06:48.878Z
+firstPublishedAt: 2024-02-22T14:06:58.203Z
+contentType: trackArticle
+productTeam: Others
+slug: integraciones-de-backend
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+Normalmente, las integraciones comienzan con los softwares de back office y permiten gestionar las partes esenciales de la operación relacionadas con [Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) y [Pedidos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos). Los principales tipos de software presentes en el back office son:
+
+- ERP (Enterprise Resource Planning)
+- WMS (Warehouse Management System)
+- PIM (Product Information Manager)
+- CRM (Customer Relationship Management)
+
+Además del back office, la plataforma de ecommerce puede integrarse a otros sistemas que suman nuevos recursos. Un ejemplo son los [provedores de pago](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos), que permiten la comunicación para procesar pagos e incluir medios de pago adicionales en el [checkout](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout).
+
+## Integración con ERP
+
+La configuración de integración de back office de una tienda comienza por el software ERP. Otros tipos de software pueden ser utilizados en el back office para propósitos específicos, como un PIM para los datos de productos y un WMS para el stock.
+
+Los ERP y otros tipos de software pueden tener integraciones nativas con VTEX. En caso contrario, debes implementar un middleware propio utilizando las [API de VTEX](https://developers.vtex.com/docs/api-reference) para integrar el software con la cuenta VTEX.
+
+La configuración consta de dos fases: la **configuración inicial** y la **configuración del middleware**. Después de realizar la configuración, podrás ver el flujo activo que se utiliza para la operación cotidiana de la tienda. Para más información sobre la configuración, consulta [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide).
+
+### Configuración inicial
+
+En esta fase se llevan a cabo los pasos para que la [cuenta VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-cuenta-vtex) reciba todos los datos de los productos. En este momento, se integran el catálogo, productos, precios y stock de la tienda. En general, la configuración de esta fase puede realizarse de tres maneras:
+
+- Integración con herramientas externas.
+- Integración de plantillas.
+- Importación manual a través del Admin VTEX.
+
+Los pasos de configuración de esta fase se deben seguir en el orden indicado a continuación. Los detalles de cada paso se describen en las respectivas subsecciones de la sección [Integraciones](#integraciones) de este artículo.
+
+1. [Arquitectura del catálogo](#arquitectura-del-catalogo)
+
+    a. Árbol de categorías
+
+    b. Marcas
+
+    c. Especificaciones (grupos y campos)
+
+2. [Importación de productos](#importar-productos)
+
+    a. Importar productos
+
+    b. Importar especificaciones de los productos
+
+    c. Agregar los productos a la política comercial
+
+    d. Importar SKU
+
+    e. Importar especificaciones de los SKU
+
+    f. Importar imágenes de los SKU
+
+3. [Importación de precios](#precios)
+
+    a. Establecer precio base
+
+    b. Definir precios fijos para contextos específicos
+
+4. [Importación de stock](#stock)
+
+    a. Crear almacenes
+
+    b. Actualizar stock de SKU
+
+### Configuración de middleware
+
+En esta fase se llevan a cabo los pasos para permitir que la tienda procese los pedidos. Además, se integrarán las notificaciones sobre cambios a los pedidos y las acciones para ejecutar el procesamiento de pedidos. La integración puede realizarse de dos maneras:
+
+- **Integración de plataformas:** esta opción utiliza una plataforma externa, conocida como PaaS (Platform-as-a-service), que ya ofrece una solución lista para integrarse con VTEX y requiere un esfuerzo de desarrollo mínimo.
+- **Desarrollo interno:** esta opción requiere la creación y mantenimientos de software de integración propio. El middleware debe ser capaz de funcionar con variaciones de escalabilidad que pueden surgir en picos de ventas, como los que se observan a menudo durante eventos de ventas como Black Friday.
+
+Los pasos para la configuración se deben seguir en el orden indicado a continuación. Los detalles de cada paso se describen en las respectivas subsecciones de la sección [Integraciones](#integraciones) de este artículo.
+
+1. [Integración/notificación de pedidos](#integracion-de-pedidos)
+
+    a. Configurar el feed o hook
+
+2. [Procesamiento de pedidos](#procesamiento-de-pedidos)
+
+    a. Modificar pedido
+
+    b. Cancelación
+
+    c. Facturación
+
+    d. Seguimiento
+
+### Comportamiento de la integración con ERP
+
+Después de configurar la tienda y completar la integración con el middleware, el flujo general de información seguirá el formato que se muestra en la imagen:
+
+![ERP-integrations-es](//images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/fc870c6a2aedf5a3bebd4d0c33058794/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_3.jpg)
+
+Cada una de las solicitudes o procesos representados por las flechas en el diagrama anterior es accionado por un tipo diferente de evento en la operación cotidiana de una tienda online. Para más información sobre este flujo, consulta[ Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide#ongoing-middleware-flow).
+
+## Integraciones
+
+En esta sección, se abordan las principales integraciones para el funcionamiento de una tienda VTEX. Las integraciones abarcan una amplia gama de aspectos, desde la integración de catálogo y datos de clientes hasta la gestión de pedidos e inicio de sesión único (SSO). Cada una de las integraciones se describe a continuación.
+
+### Arquitectura del catálogo
+
+En VTEX,[Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) es el módulo donde se configuran las características de los productos de la tienda para ponerlos a disposición de los clientes. El catálogo se debe crear siguiendo el orden de pasos descritos a continuación:
+
+1. Creación del [árbol de categorías](#arbol-de-categorias).
+2. Registro de [marcas](#marcas).
+3. Registro de [especificaciones](#especificaciones) (opcional).
+4. Importación de [productos](#importacion-de-productos).
+5. Importación de [SKU](#importar-productos).
+6. [Asociación de especificaciones de productos y SKU](#importar-productos)
+
+Consulta más información sobre la configuración del catálogo con el back office en los artículos [Catalog](https://developers.vtex.com/docs/guides/catalog-overview) y [Set up catalog](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog).
+
+#### Árbol de categorías
+
+Después de definir y planificar la [arquitectura del catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#arquitectura-de-catalogo) de la tienda, puedes crear las categorías de las siguientes maneras:
+
+1. **Admin VTEX:** crear cada categoría a través de la interfaz de usuario. Consulta los detalles en [Registrar categorías](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1).
+2. **API de Catálogo:** crear cada categoría mediante llamadas de API. Consulta los detalles en [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category).
+3. **Integración con back office:** importar categorías a partir de un software de back office externo (ERP o PIM) integrado a VTEX. El software puede ofrecer una integración nativa con VTEX o requerir el desarrollo de middleware que utilice la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Consulta los detalles en [Category migration from ERPs](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#category-migration-from-erps).
+
+<div class="alert alert-warning">
+Al importar las categorías de un software externo, la estructura de categorías en el software puede diferir de la de VTEX. En este caso, recomendamos crear una categoría simulada inactiva que no será visible en el storefront y que se puede utilizar para recibir todos los productos y SKU durante la importación. Una vez finalizada la importación, los productos pueden organizarse manualmente en el Admin VTEX para ajustarse al árbol de categorías deseado.
+</div>
+
+Las categorías tienen algunas limitaciones:
+
+- **Mover categorías:** aunque sí es posible mover una categoría a otro nivel (superior o inferior) y/u otro departamento, es una acción arriesgada debido a las especificaciones asociadas a la categoría. Esta acción puede impactar la información de los productos, ya que los productos heredan las especificaciones nuevas además de las anteriores.
+- **Agregar categorías:** no es posible eliminar una categoría a menos que se haga una [limpieza completa](https://help.vtex.com/es/tutorial/database-maintenance-full-cleanup--34P9LGs7BCIQK6acQom802) del catálogo de la tienda.
+
+Para más información sobre la importación de categorías al back office, consulta [Categories](https://developers.vtex.com/docs/guides/categories).
+
+#### Marcas
+
+Las [marcas](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) son atributos de productos que ayudan a los clientes a identificar el producto y la empresa de origen. Un producto debe estar asociado a una sola marca. Por ende, crear marcas es un paso obligatorio en la configuración del catálogo. Se pueden crear marcas de las siguientes formas:
+
+1. **Admin VTEX:** crear cada marca a través de la interfaz de usuario. Consulta los detalles en [Registrar marcas](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7lEGOSpAlQJCs5eUc5XFmR).
+2. **API de Catálogo:** crear cada marca mediante llamadas de API. Consulta los detalles en [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand).
+3. **Integración con back office:** importar marcas a partir de un software de back office externo (ERP o PIM) integrado a VTEX. El software puede ofrecer una integración nativa con VTEX o requerir el desarrollo de middleware que utilice la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Consulta los detalles en la sección [Create Brands](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-brands) de la guía de configuración de Catálogo para back office.
+
+<div class="alert alert-warning">
+Si el sistema de back office no tiene la información sobre marcas, se puede aplicar el mismo procedimiento mencionado anteriormente para categorías en el que se crea una marca simulada inactiva que solo se usa para la migración. Luego, la información de los productos puede ingresarse manualmente.
+</div>
+
+Para más información sobre la importación de marcas al back office, consulta [Brands](https://developers.vtex.com/docs/guides/brands).
+
+#### Especificaciones
+
+Las [especificaciones](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) son propiedades adicionales que se pueden atribuir a productos y SKU de la tienda y se utilizan para crear filtros de búsqueda y diferenciar SKU y productos en la página del producto. La creación de especificaciones puede llevarse a cabo mediante [integraciones de back office](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-specifications-groups) utilizando las [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview).
+
+Hay tres tipos de especificaciones que se deben crear en el siguiente orden:
+
+1. Grupos de especificaciones
+2. Campos de especificación
+3. Valores de especificación
+
+El diagrama a continuación ilustra el procedimiento.
+
+![catalog_specification_diagram_ES](//images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/8614400d84e83d97dcc00ae1029161e4/catalog_specification_diagram_ES.png)
+
+Las especificaciones siguen la jerarquía de Catálogo. Cuando se crea un grupo en un departamento o categoría, el mismo se heredará en los niveles inferiores.
+Una vez creados los grupos, campos y valores, hay que asociar las especificaciones a productos y SKU. Estos procedimientos se describen en la próxima sección: [Importar productos](#importar-productos).
+
+Para más información sobre la importación de especificaciones al back office, consulta [Specifications](https://developers.vtex.com/docs/guides/specifications).
+
+### Importar productos
+
+Importar productos es el acto de transferir todos los datos relevantes de un producto de un sistema ERP o PIM a la plataforma VTEX. Este paso mantiene el catálogo de productos actualizado y sincronizado con la tienda. Tanto si se trata de una amplia variedad de productos, SKU o distintas variaciones, la importación eficaz de productos es esencial para la experiencia del cliente.
+
+En VTEX, es importante entender la distinción entre productos y SKU:
+
+- [Producto](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru): unidad abstracta del catálogo, visible en los estantes de la tienda.
+- [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA): unidad concreta del catálogo en el stock que representa las variaciones específicas de un producto, como color, tamaño y otros atributos. Los SKU se muestran como ítems individuales en las páginas de los productos.
+
+<div class = "alert alert-info">
+La manera en que se estructuran los productos y SKU afectan directamente la experiencia de compra de los clientes.
+</div>
+
+La importación de productos debe seguir el orden descrito en la tabla a continuación:
+
+| **Acción** | **Descripción** | **Métodos** |
+| :--- | :--- | :--- |
+| [1. Importar productos](https://developers.vtex.com/docs/guides/products) | Registrar los productos en el catálogo. | - Integración mediante la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product). <br><br>- Importación de plantillas ([método clásico](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#spreadsheet) y [aplicación google-drive-import](https://developers.vtex.com/docs/apps/vtex.google-drive-import@0.x)). <br><br>- Entrada manual en el Admin VTEX. |
+| [2. Importar especificaciones de los productos](https://developers.vtex.com/docs/guides/product-specifications) | Rellenar las especificaciones de los productos en el catálogo. | - Integración mediante la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/specification). <br><br>- Entrada manual en el [Admin VTEX](https://help.vtex.com/es/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106#preencher-especificacoes-de-produto). |
+| [3. Agregar los productos a la política comercial](https://developers.vtex.com/docs/guides/erp-integration-import-products#add-product-to-trade-policy) | Asociar los productos a las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) correspondientes y definir las reglas específicas (precios, pagos, estrategia de envío, etc.) según el canal de venta o público. Como mínimo, se deben agregar todos los productos a la política comercial principal. | - Integración mediante la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/salespolicy/-tradepolicyId-). <br><br>- Entrada manual en el [Admin VTEX](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL) al registrar un producto.  |
+| [4. Importar SKU](https://developers.vtex.com/docs/guides/skus) | Agregar SKU a los productos del catálogo. | - Integración mediante la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit). <br><br>- Entrada manual en el [Admin VTEX](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#adicionar-novo-sku-a-um-produto-ja-cadastrado). |
+| [5. Importar especificaciones de los SKUs](https://developers.vtex.com/docs/guides/sku-specifications) | Rellenar las especificaciones de los SKU en el catálogo. | <br><br>- Integración mediante la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/specification). <br><br>- Entrada manual en el [Admin VTEX](https://help.vtex.com/es/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119#preencher-especificacoes-de-sku). |
+| [6. Importar imágenes de los SKUs](https://developers.vtex.com/docs/guides/images) | Agregar imágenes a los SKU. | - Integración mediante la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file). <br><br>- Entrada manual en el [Admin VTEX](https://help.vtex.com/es/tutorial/como-atualizar-a-imagem-de-um-sku--5PMb54FnvUuWOq2qGyAosu). |
+
+<br>
+
+<div class="alert alert-warning">
+Es común que los datos de productos en el ERP no sean adecuados para uso y visualización en una tienda online. Por esta razón, debe llevarse a cabo un proceso de enriquecimiento, que puede incluir reestructuración de categorías y la creación de descripciones de productos más detalladas y atractivas.
+</div>
+
+Después de la importación, también es importante garantizar que los datos de los productos y SKU se mantengan actualizados. Consulta las instrucciones en el artículo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information).
+
+Para más información sobre la importación de productos al back office, consulta [Import products](https://developers.vtex.com/docs/guides/erp-integration-import-products).
+
+ ### Precios
+
+Los [precios](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precios) son la información de los valores de venta de los SKU, que se almacenan en las [tablas de precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8). Para garantizar que los productos de la tienda tengan precios competitivos y adaptados a los distintos canales de venta, es necesario entender cómo los precios se integran en VTEX.
+
+En operaciones de venta, es común delegar el cálculo de precios al ERP, desde donde se puede importar la información. Los precios tienen un valor base definido para cada SKU y pueden variar según el contexto. Los pasos para importar precios son:
+
+1. **Definir precio base:** el precio base sirve como referencia para determinar el precio de un producto en el sistema de precios de VTEX. El precio base de un SKU puede importarse a través de una integración mediante la [API de Precios](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-) o [crearse en el Admin VTEX](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29#admin).
+2. **Definir precios fijos para contextos específicos:** el precio base puede ser ajustado o modificado mediante reglas específicas, cálculos o precios fijos para llegar al precio final de retail del SKU en diferentes contextos, dependiendo de la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV), [grupo de clientes](https://help.vtex.com/es/tutorial/como-criar-um-cluster-de-clientes--frequentlyAskedQuestions_1724), [promoción](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR), entre otros factores. Los precios fijos para contextos específicos pueden importarse mediante una integración que use la [API de Precios](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-), [mediante una plantilla](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#importacao-de-precos) o [crearse en el Admin VTEX](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj#admin).
+
+Después de la importación, también es importante garantizar que los datos de los precios se mantengan actualizados. Consulta las instrucciones en el artículo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information#pricing-updates).
+
+Para más información sobre la importación de precios al back office, consulta [Import prices](https://developers.vtex.com/docs/guides/erp-integration-import-prices).
+
+### Stock
+
+En el módulo [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) de VTEX, el [stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) es la relación entre los ítems de venta en una tienda (SKU) y las ubicaciones donde se guardan dichos ítems, denominados [almacenes](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb). La gestión eficiente del stock de una tienda es fundamental para importar el stock a VTEX y garantizar que los clientes puedan acceder a información precisa sobre la disponibilidad de los productos, lo que agiliza el proceso de [logística y envío](https://help.vtex.com/es/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP).
+
+Los pasos para importar el stock son:
+
+1. **Crear almacenes:** registrar las ubicaciones físicas o virtuales donde se almacenarán los SKU. Los almacenes pueden importarse mediante una integración que utilice la [API de Logística](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) o [crearse en el Admin VTEX](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137#cadastrar-estoque%5D).
+2. **Actualizar el stock de SKU:** ingresar la cantidad disponible de cada ítem en los almacenes. El stock puede importarse mediante una integración que utilice la [API de Logística](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-), mediante una [plantilla de stock](https://help.vtex.com/es/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034) o [actualizarse en el Admin VTEX](https://help.vtex.com/es/tutorial/como-atualizar-estoque--2MDwYV1COA6YuoiY22AyGo).
+
+Después de la importación, también es importante garantizar que los datos de los precios se mantengan actualizados. Puedes consultar las instrucciones en [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information#pricing-updates).
+
+Para más información sobre la importación de stock al back office, consulta [Import inventory](https://developers.vtex.com/docs/guides/erp-integration-import-inventory).
+
+ ### Datos de clientes
+
+La importación de datos de clientes permite integrar los datos de los clientes de otros sistemas, como aplicaciones de CRM, con VTEX. De forma predeterminada, VTEX almacena los datos de los clientes en [Master Data V1](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw).
+
+Los datos de Master Data se organizan en [entidades de datos](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-dados) análogas a tablas en otros sistemas de bases de datos, cuyos [documentos](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#documentos) son el equivalente de filas o registros. Los datos de perfil de los clientes se almacenan en la entidad `CL` y sus direcciones en la entidad `AD`.
+
+Los pasos para importar los datos de clientes son:
+
+1. **Crear nuevos perfiles de clientes:** crear documentos en la entidad `CL` con la información de perfil de los clientes, como nombre, email, teléfono, entre otros. Los datos pueden importarse a través de integración utilizando la [API de Master Data](https://developers.vtex.com/docs/api-reference/masterdata-api#post-/api/dataentities/-acronym-/documents).
+2. **Crear direcciones:** crear documentos en la entidad `AD` con las direcciones de los clientes, incluyendo información como calle, ciudad, código postal, entre otros. Cada dirección se asocia a un cliente y un cliente puede tener más de una dirección asociada. Los datos pueden importarse a través de integración utilizando la [API de Master Data](https://developers.vtex.com/docs/api-reference/masterdata-api#post-/api/dataentities/-acronym-/documents).
+
+Para más información sobre la importación de datos de clientes para back office, consulta el artículo [Import customer data](https://developers.vtex.com/docs/guides/import-customer-data).
+
+### Integración de pedidos
+
+En la plataforma VTEX se genera un [pedido](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos) en el momento en que el cliente hace clic en el botón de finalizar compra. Cada pedido contiene varios datos, como los ítems del carrito, el valor de la compra, el medio de pago, entre otros.
+
+La integración de pedidos permite la comunicación entre la aplicación de back office, ya sea ERP o WMS, y el OMS (Order Management System) de VTEX. Dicha integración desempeña un papel fundamental al:
+
+- Manejar los eventos de cambios de [status del pedido](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
+- Obtener [detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl).
+- Transmitir la información de [procesamiento del pedido](#).
+
+#### Recibir actualizaciones de pedidos
+
+Las actualizaciones de los pedidos en el back office permite agilizar y automatizar las acciones realizadas durante el [procesamiento de los pedidos](#procesamiento-de-pedidos), tales como facturación y cancelación.
+Existen dos formas dar seguimiento a los cambios de status de los pedidos en VTEX:
+
+- [Feed v3](https://developers.vtex.com/docs/guides/orders-feed): una lista de eventos sobre las actualizaciones de los pedidos. Para este tipo de integración, VTEX proporciona un [endpoint](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/orders/feed/config?endpoint=get-/api/orders/feed/config) que el back office puede utilizar para consultar los ítems de la lista, procesar los pedidos, así como también remover los ítems de la lista.
+- [Hook](https://developers.vtex.com/docs/guides/orders-feed#hook): un canal para el envío automático de notificaciones sobre las actualizaciones de los pedidos. Para este tipo de integración, la aplicación de back office proporciona un [endpoint](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/orders/hook/config?endpoint=get-/api/orders/hook/config) al que VTEX notificará sobre las actualizaciones de los pedidos. Tras recibir una notificación, el sistema de back office continúa el procesamiento del pedido.
+
+Los dos tipos de integración permiten aplicar [filtros](https://developers.vtex.com/docs/guides/orders-feed#filter) para seleccionar los tipos de eventos que el sistema de back office debe procesar.
+
+<div class = "alert alert-info">
+En la mayoría de los casos, VTEX recomienda integrar los pedidos con <a href="https://developers.vtex.com/docs/guides/orders-feed">Feed v3</a> porque es un método más robusto.
+</div>
+
+#### Obtener detalles del pedido
+
+Además de los cambios de status, la operación puede necesitar información adicional sobre un pedido. Los detalles de un pedido se pueden obtener mediante la [API de Pedidos](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-), que se puede utilizar para integrar el sistema de back office deseado.
+
+Los detalles del pedido se utilizan en diferentes etapas del procesamiento, como los ítems que requieren preparación y el valor de la compra que se debe facturar.
+
+#### Iniciar preparación
+
+Después de que se envían los detalles del pedido al sistema de back office, el paso final antes de iniciar el procesamiento es cambiar el status del pedido a `Iniciar preparación`. Este proceso puede integrarse con el sistema de back office mediante la [API de Pedidos](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
+
+Para más información sobre la integración de pedidos con el sistema de back office, consulta los artículos [Set up order integration](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-integration) y [Feed v3](https://developers.vtex.com/docs/guides/orders-feed).
+
+### Procesamiento de pedidos
+
+En esta etapa, se configura la integración para enviar actualizaciones de pedidos del sistema de back office, ya sea ERP o WMS, a VTEX. Durante la preparación de un pedido se pueden aplicar diversas acciones, incluyendo cambio, cancelación y facturación.
+
+A continuación se listan los eventos que el sistema de back office puede transmitir a VTEX. La integración entre VTEX y el sistema de back office para la transmisión de estos eventos se completa mediante la [API de Pedidos](https://developers.vtex.com/docs/api-reference/orders-api).
+
+- **Modificar pedido:** cambiar ítems o valores del pedido.
+- **Cancelar pedido:** finalizar el pedido y cancelar el pago.
+- **Facturar pedido:** [agregar la factura al pedido](https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT). Esto es lo que indica que el pedido se finalizó con éxito y esta listo para envío.
+- **Seguir pedido:** enviar la información de seguimiento. Puede enviarse el código o la URL de seguimiento de la transportadora o las notificaciones de actualización de seguimiento. 
+
+Para más información sobre la configuración del procesamiento de pedidos en el sistema de back office, consulta los artículos [Set up order processing](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-processing) y [Change order](https://developers.vtex.com/docs/guides/change-order).
+
+### Inicio de sesión único (SSO)
+
+El inicio de sesión único es un método que permite autenticar usuarios en la plataforma utilizando un único conjunto de credenciales de inicio de sesión, eliminando la necesidad de iniciar sesión en cada aplicación por separado. VTEX admite la integración de proveedores de identidad externos. Además de la integración nativa con servicios como [Google](https://help.vtex.com/es/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google--1lBgDmetUM4goie6mYEOK6), se pueden crear nuevas integraciones con otros proveedores.
+
+**VTEX ID** es el servicio que identifica los usuarios en la plataforma. Este servicio opera de acuerdo con la audiencia, las reglas de negocios y el tipo de user persona que puede interactuar con cada módulo de VTEX. Las audiencias disponibles son:
+
+| **Audiencia** | **Contexto** | **Tecnología** |
+| :---: | :--- | :--- |
+| [Admin VTEX](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) | Identificación en el dashboard administrativo de VTEX, también conocido como [Admin VTEX](https://help.vtex.com/es/tutorial/vtex-admin-start-here--531cHtUCUi3puRXNDmKziw), destinado a administradores y operadores de la tienda. | SAML 2.0 (Security Assertion Markup Language). |
+| [Webstore](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) | Identificación en el storefront VTEX, destinado a los clientes de la tienda. | OAuth 2.0 (Open Authorization). |
+
+Para más información, consulta el artículo [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide).
+
+### Pagos
+
+Los sistemas de [Pago](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos) de VTEX ofrecen amplios recursos para incorporar varios [medios de pago](https://developers.vtex.com/docs/guides/payments-integration-payment-methods), [condiciones](https://help.vtex.com/es/tutorial/condicoes-de-pagamento) e integraciones. En VTEX los pagos tienen las siguientes opciones de [flujo de compra](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows):
+
+- **Transparente:** el pago ocurre directamente en el checkout y el comprador escoge el medio de pago.
+- **Redirección:** abre una nueva ventana en el navegador del comprador donde un servicio externo procesa el pago. Después de finalizado el pago, el comprador vuelve al checkout para concluir la compra.
+- **Payment App:** abre una ventana modal en la página de checkout. Después de finalizado el pago, la ventana se cierra y el flujo de compra continúa en el checkout. Este flujo también puede utilizarse para el método de autenticación [3D Secure 2 (3DS2)](https://developers.vtex.com/docs/guides/payments-integration-payment-app#scenario-2-payment-app-and-3d-secure-2).
+
+Se pueden agregar medios de pago en una tienda VTEX de dos maneras:
+
+- **Proveedor de pago con soporte nativo:** si VTEX ofrece integración con el proveedor de pago deseado, es necesario tener un contrato con el mismo y configurar las opciones de pago a través del Admin VTEX. Consulta los detalles de configuración en [Pagos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos) y los proveedores de pago que tienen soporte en VTEX en la [Lista de proveedores de pago por país](https://help.vtex.com/es/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).
+- **Proveedor de pago personalizado:** Si el proveedor de pago deseado no tiene una integración con VTEX, es necesario implementar un proveedor de pago independiente utilizando el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) con los [endpoints de la API](https://developers.vtex.com/docs/api-reference/payment-provider-protocol) para conectarse con nuestro [gateway de pagos](https://help.vtex.com/es/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk). El proveedor puede implementarlo una [agencia partner de VTEX](https://partnerportal.vtex.com/) (el Partner Portal está disponible solamente en portugués). Para disponibilizar el proveedor en VTEX, es necesario probarlo y pasar el [proceso de homologación](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
+
+Para más información sobre cómo integrar un nuevo proveedor de pago, consulta el artículo [Integrating a new payment provider on VTEX](https://developers.vtex.com/docs/guides/integrating-a-new-payment-provider-on-vtex).
+
+### Tarjeta de regalo
+
+En VTEX, las tarjetas de regalo pueden utilizarse como opción de pago en el **checkout** y como parte de programas de fidelización. VTEX proporciona una solución nativa de tarjetas de regalo y también permite incorporar integraciones con proveedores de tarjeta de regalo externos. 
+
+Se pueden agregar tarjetas de regalo en una tienda VTEX de dos maneras:
+
+- **Solución nativa de tarjetas de regalo:** si deseas utilizar la solución nativa de VTEX para tarjetas de regalo o una integración existente, debes configurar las tarjetas de regalo a través del Admin VTEX siguiendo los pasos presentes en [Configurar tarjeta de regalo](https://help.vtex.com/es/tutorial/gift-card--tutorials_995).
+- **Proveedor de tarjetas de regalo personalizado:** si el proveedor de tarjetas de regalo deseado no tiene una integración con VTEX, es necesario implementar una integración independiente utilizando el [Gift Card Provider Protocol](https://help.vtex.com/es/tutorial/integrando-com-gift-card). Este protocolo les permite a los proveedores desarrollar una integración con los endpoints descritos en nuestra [Gift Card Provider Protocol API](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol#overview) y conectarse co nuestro [Gift Card Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api#overview).
+
+### Antifraude
+
+Un antifraude es un sistema especializado en analizar las compras realizadas en los sitios web con el fin de identificar transacciones fraudulentas. En VTEX, el operador de pagos primero aprueba la compra y, luego, el antifraude evalúa el pedido. 
+
+Se puede agregar un sistema antifraude a los pagos de una tienda VTEX de dos maneras:
+
+- **Sistema antifraude con soporte nativo:** si el sistema antifraude deseado ya tiene una integración con VTEX, es necesario tener un contrato con una de las empresas partner y realizar la configuración en el Admin VTEX. Para más información, consulta los artículos [Configurar el antifraude](https://help.vtex.com/es/tutorial/como-configurar-antifraude--tutorials_446) y [¿Qué es antifraude?](https://help.vtex.com/es/tutorial/o-que-e-antifraude--69SjFCc4rC6Ii0OMAeYAsG).
+- **Sistema antifraude personalizado:** si el sistema antifraude deseado no tiene una integración con VTEX, es necesario implementar una integración independiente utilizando el [Antifraud Provider Protocol](https://developers.vtex.com/docs/guides/how-the-integration-protocol-between-vtex-and-antifraud-companies-works) con los endpoints de la [Antifraud Provider API](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol).
+
+## Extensiones y aplicaciones
+
+Además de los servicios esenciales que VTEX ofrece, las funcionalidades de las tiendas VTEX se pueden optimizar mediante la incorporación de extensiones. Las extensiones son herramientas que amplían la capacidad de la plataforma VTEX y proporcionan diversas posibilidades, tales como agregar proveedores de pago y marketplace, personalizar el storefront, construir servicios de backend personalizados y crear nuevas aplicaciones para el Admin VTEX.
+
+Una de las formas de incorporar nuevas funcionalidades a VTEX es crear aplicaciones utilizando [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io), nuestra plataforma de desarrollo que proporciona gestión de alto rendimiento, escalabilidad y seguridad robusta. VTEX IO permite a los desarrolladores centrarse en construir soluciones de negocio sin tener que preocuparse de la infraestructura.
+
+### Qué es una aplicación en VTEX
+
+Una [app](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app) en VTEX es una aplicación construida con VTEX IO. Las aplicaciones son un tipo de extensión, es decir, también amplían las funcionalidades de la plataforma VTEX. Las aplicaciones pueden [desarrollarse](https://developers.vtex.com/docs/app-development) localmente, con código personalizado, y posteriormente integrarse a las tiendas que operan en nuestra infraestructura. Las aplicaciones también pueden agregarse y adquirirse a través de [VTEX App Store](https://developers.vtex.com/docs/guides/vtex-app-store).
+
+Los tipos de aplicaciones disponibles en VTEX son:
+
+- [Storefront](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ): temas de tienda desarrollados con [Store Framework](https://help.vtex.com/es/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework).
+- [Frontend](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io): componentes [React](https://react.dev/) que conforman los temas de tienda desarrollados con Store Framework.
+- [Admin VTEX](https://learn.vtex.com/docs/course-admin-lang-en): módulos y funcionalidades para el [Admin VTEX](https://help.vtex.com/es/tutorial/vtex-admin-start-here--531cHtUCUi3puRXNDmKziw).
+- [Servicios (backend)](https://developers.vtex.com/docs/guides/vtex-io-documentation-service): servicios [Node](https://nodejs.org/en) o [.NET Core](https://dotnet.microsoft.com/en-us/) capaces de manejar eventos y triggers, exportar rutas HTTP y mostrar solucinadores GraphQL.
+- [Pixel](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developnativeintegrationswithpixelapps): scripts de servicios externos que se ejecutan en el frontend y proporcionan soluciones como monitoreo de ventas, soporte al usuario, recopilación de datos y servicios de marketing.
+- [Edition](https://developers.vtex.com/docs/guides/vtex-io-documentation-edition-app): conjunto de configuraciones, políticas, aplicaciones de backend y frontend encapsulado y exportado por una [sponsor account](https://developers.vtex.com/docs/guides/vtex-io-documentation-sponsor-account).
+
+Para ver las opciones de implementación de aplicaciones, consulta la [lista de builders](https://developers.vtex.com/docs/guides/vtex-io-documentation-builders#list-of-builders).
+
+Para más información, consulta el artículo [What is a VTEX App](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app).
+
+### Consideraciones antes de instalar una aplicación en tu tienda
+
+Antes de empezar el proceso de desarrollo de una nueva aplicación, recomendamos explorar las soluciones disponibles para instalación en tu tienda. Puedes encontrar estas soluciones en el [Hub de extensiones](https://help.vtex.com/es/tracks/extensions-hub--AW7klkYMh557y5IUOgzco), la sección del Admin VTEX que centraliza la gestión de extensiones. El Hub de extensiones tiene las siguientes páginas:
+
+- **App Store:** marketplace donde se encuentran las aplicaciones desarrolladas por VTEX y terceros. En esta página puedes ver, comprar e instalar aplicaciones para una cuenta VTEX. Hay aplicaciones gratis y de pago, que tienen diferentes métodos de facturación.
+- **Gestión de aplicaciones:** página que permite instalar, desinstalar, remover y configurar aplicaciones en la tienda.
+
+Algunos ejemplos de soluciones disponibles en la App Store son:
+
+- [Assembly Options](https://developers.vtex.com/docs/guides/assembly-options-app): agrega opciones de [anexos](https://help.vtex.com/es/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm) para personalizar SKU. Por ejemplo, agregar una frase a una camiseta o ingredientes para un sándwich.
+- [Gift List](https://developers.vtex.com/docs/apps/vtex.list): permite crear listas de regalos que se pueden compartir para que otras personas compren los ítems que se van a regalar. Son útiles para eventos como cumpleaños, bodas y baby showers. Los ítems comprados se transforman en crédito que puede utilizarse para comprar cualquier ítem disponible en la tienda.
+- [Live Shopping](https://developers.vtex.com/docs/apps/vtexventures.livestreaming): permite transmitir en vivo desde el sitio web de la tienda para interactuar con los clientes en tiempo real. Crea oportunidades para promocionar productos y tiene varios componentes que van más allá de la reproducción de video como número de espectadores, botón de me gusta, chat en tiempo real y barra lateral para presentar productos.
+- **Aplicaciones de chat para clientes:** agregan un componente de chat para interactuar con los clientes. Pueden disponer de un chatbot para interacción automática, además de proporcionar servicio al cliente humano. Algunos ejemplos de aplicaciones son [JivoChat](https://developers.vtex.com/docs/apps/vtex.jivochat), [Tawk.to](https://developers.vtex.com/docs/apps/vtex.tawk-to) y [Zendesk Chat](https://developers.vtex.com/docs/apps/vtex.zendesk-chat).
+- **Aplicaciones de análisis y evaluación:** agregan componentes para que los clientes evalúen los productos de la tienda, generalmente mediante una calificación numérica o un comentario. Algunos ejemplos de aplicaciones son[ Reviews and Ratings by VTEX](https://developers.vtex.com/docs/apps/vtex.reviews-and-ratings), [Bazaarvoice](https://developers.vtex.com/docs/apps/vtex.bazaarvoice) y [PowerReviews](https://developers.vtex.com/docs/apps/vtex.powerreviews).
+- **Aplicaciones de redes sociales:** permite interactuar con redes sociales, como por ejemplo para divulgar productos de la tienda a través de anuncios en la plataforma de la red. Algunos ejemplos de aplicaciones son [TikTok for Business](https://developers.vtex.com/docs/apps/vtexbr.tiktok-tbp) y [Facebook Business Extension](https://developers.vtex.com/docs/apps/vtex.facebook-fbe).
+
+### Consideraciones al crear una aplicación para tu tienda
+
+Si no encuentras una aplicación que satisfaga las necesidades de tu tienda VTEX, tienes la opción de desarrollar una solución independiente. Hay varios aspectos que se deben tener en cuenta al desarrollar aplicaciones en VTEX:
+
+- **¿Quién será el responsable del desarrollo y mantenimiento?** Las aplicaciones pueden ser desarrolladas y mantenidas por el equipo de desarrollo interno de la empresa o por una agencia certificada por VTEX. Puedes encontrar los [partners de implementación de VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion) en nuestro [Partner Portal](https://partnerportal.vtex.com/) (solamente en portugués). Además del desarrollo, el responsable de la aplicación está encargado de mantenerla y actualizarla.
+- **¿Qué tipo de aplicación se debe desarrollar?** Es importante saber el contexto en que la solución deseada debe operar. Los tipos de aplicaciones disponibles se describen en la sección anterior [Qué es una aplicación en VTEX](#que-es-una-aplicacion-en-vtex). Tenemos guías de desarrollo para algunos tipos de aplicaciones como [storefront](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io), [servicio](https://developers.vtex.com/docs/guides/vtex-io-documentation-developing-service-configuration-apps) y [Pixel](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developnativeintegrationswithpixelapps).
+- **¿Cuál es el proceso de desarrollo de una aplicación?** Las aplicaciones se desarrollan en varias etapas. En general, el proceso de desarrollo sigue los pasos a continuación:
+
+  a. **Preparar el entorno de desarrollo:** los requisitos principales antes de empezar el desarrollo de una aplicación son [instalar VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install) (la interfaz de comando de VTEX IO) y [crear un workspace de desarrollo](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace) en la cuenta de la tienda.
+
+  b. **Interactuar con el código:** normalmente, el desarrollo parte de un template inicial seguido de la implementación local en el código. Se debe elegir un template que corresponda al tipo de aplicación deseada. Puedes consultar los templates disponibles ejecutando el [comando](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-command-reference) `vtex init` en la CLI. Además, se debe configurar el archivo [manifest.json](https://developers.vtex.com/docs/guides/vtex-io-documentation-manifest), donde se definen varios parámetros como el nombre de la aplicación, el nombre del desarrollador (vendor) y los [permisos](https://developers.vtex.com/docs/guides/vtex-io-documentation-policies). Después de editar el código, se agrega la aplicación al workspace de desarrollo para probarla utilizando el [comando vtex link](https://developers.vtex.com/docs/guides/vtex-io-documentation-linking-an-app) en la CLI.
+
+  c. **Empaquetar el código en una nueva versión:** después de las pruebas, se deben seguir los pasos para [lanzar una nueva versión de la aplicación](https://developers.vtex.com/docs/guides/vtex-io-documentation-releasing-a-new-app-version) y [publicar la aplicación](https://developers.vtex.com/docs/guides/vtex-io-documentation-publishing-an-app). Esto permite que el código se guarde en la infraestructura VTEX y se pueda instalar en [workspaces de producción](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace).
+
+  d. **(Opcional) Validar que la aplicación satisfaga la necesidad de negocio:** después de tener la versión publicada, podría ser beneficioso instalar la aplicación en un [workspace de producción](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace) y realizar una [prueba A/B](https://developers.vtex.com/docs/guides/ab-tests) para comparar la tasa de conversión de las ventas con la nueva aplicación. 
+
+<div class = "alert alert-info">
+Si deseas saber más sobre el desarrollo de aplicaciones, accede a nuestro <a href="https://learn.vtex.com/">Learning Center</a>.
+</div>
+
+- **¿Deseas que la aplicación sea pública?** Puedes [disponibilizar](https://developers.vtex.com/docs/guides/vtex-io-documentation-making-your-new-app-version-publicly-available) la aplicación en la App Store para permitir que otras cuentas puedan aprovechar la solución desarrollada.
+- **¿Deseas que la aplicación esté disponible en la App Store?** Disponibilizar la aplicación en la App Store tiene varias ventajas, como aumentar la visibilidad de la aplicación y la posibilidad de [monetizarla](https://developers.vtex.com/docs/guides/vtex-io-documentation-setting-your-apps-billing-model) siguiendo algunos pasos y reglas. En resumen, debes ser un [desarrollador registrado](https://developers.vtex.com/docs/guides/vtex-io-documentation-becoming-a-registered-vtex-app-store-developer), tener el código de la aplicación almacenado en un repositorio de [GitHub](https://github.com/), desarrollar la aplicación siguiendo las [mejores prácticas de la App Store](https://developers.vtex.com/docs/guides/vtex-io-documentation-homologation-requirements-for-vtex-app-store) y [enviarla](https://developers.vtex.com/docs/guides/vtex-io-documentation-submitting-your-app-in-the-vtex-app-store) al proceso de homologación. Tras el proceso de homologación, la aplicación estará disponible en la App Store.
diff --git a/docs/tracks/es/banners-en.md b/docs/tracks/es/banners-en.md
index 4878efd00..c8660f801 100644
--- a/docs/tracks/es/banners-en.md
+++ b/docs/tracks/es/banners-en.md
@@ -33,7 +33,7 @@ En VTEX Admin, la página **Storefront** > **Banners** muestra la lista completa
 * [Editar banner](#editar-banner)
 * [Eliminar banner](#eliminar-banner) 
 
-![banners-intro-es](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
+![banners-intro-es](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
 
 La página contiene la siguiente información:
 
diff --git a/docs/tracks/es/barcode-reading.md b/docs/tracks/es/barcode-reading.md
index b82237be4..f44c959bb 100644
--- a/docs/tracks/es/barcode-reading.md
+++ b/docs/tracks/es/barcode-reading.md
@@ -18,6 +18,6 @@ Después de identificar al cliente, el vendedor es llevado directamente al carri
 
 Si el vendedor está usando un tablet o smartphone, verá un botón de código de barras <i class="fas fa-barcode"></i> en la barra superior de la aplicación.
 
-![31. VTEX Sales App - Product Overview - 6 - EN](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/faddd95042b7890f597f30c00d933222/barcode.png)
+![31. VTEX Sales App - Product Overview - 6 - EN](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/faddd95042b7890f597f30c00d933222/barcode.png)
 
 Al hacer clic en él, el vendedor puede usar la cámara para emitir leer un producto y, con eso, pasar automáticamente a la pantalla de detalles de ese producto.
diff --git a/docs/tracks/es/basic-vtex-io-developer-setup.md b/docs/tracks/es/basic-vtex-io-developer-setup.md
index d14e2ff88..722a923f8 100644
--- a/docs/tracks/es/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/es/basic-vtex-io-developer-setup.md
@@ -38,7 +38,7 @@ Esto abrirá una ventana del navegador que solicitará sus credenciales.
 
 Cuando esté conectado, usted puede utilizar el comando `vtex whoami` para descubrir qué *cuenta* y *workspace* está utilizando actualmente.
 
-![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
+![Command Line](//images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
 <div class="alert alert-info">
 Sugerencia: Usted puede configurar su terminal para mostrar automáticamente su cuenta y workspace. La manera más fácil de hacer esto es usar nuestros <a href="https://github.com/vtex/dotfiles">dotfiles</a>, que configuran automáticamente la <a href="https://fishshell.com/">Fish Shell</a> y añaden una <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">función de prompt</a> para usted.
@@ -54,7 +54,7 @@ De forma predeterminada, cuando inicie sesión en una tienda, usted está en el
 $ vtex ls
 ```
 
-![Command Line vtex ls](https://images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
+![Command Line vtex ls](//images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
 
 ## Creando su propio workspace
 
@@ -72,6 +72,6 @@ Sugerencia: Usted puede cambiar a (<em>y restablecer</em>) un workspace master c
 
 Los workspaces pueden ser nombrados arbitrariamente, pero generalmente es conveniente asignar su propio nombre cuando usted desea desarrollar en su ambiente.
 
-![command line workspace](https://images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
+![command line workspace](//images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
 
 Ahora usted tiene su propio workspace. Usted puede ejecutar `vtex list` nuevamente y observar que las apps instaladas reflejan aquellas en `master`. Ahora, vamos a "linkar" una versión local del tema de la tienda para que usted pueda comenzar a editarla.
diff --git a/docs/tracks/es/best-practices-for-testing-instore.md b/docs/tracks/es/best-practices-for-testing-instore.md
index 3844b7061..8b202c678 100644
--- a/docs/tracks/es/best-practices-for-testing-instore.md
+++ b/docs/tracks/es/best-practices-for-testing-instore.md
@@ -16,7 +16,7 @@ trackSlugES: instore-usando-el-app
 
 Tras completar la configuración básica y la instalación de la aplicación de VTEX Sales App en un dispositivo, es importante realizar pruebas antes de empezar a utilizar VTEX Sales App en tus tiendas físicas. En este artículo, conocerás las mejores prácticas para probar el uso de VTEX Sales App.
 
-![testes-instore-es](https://images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/9e729d91cf79c227665adeeb099b79ac/Group_6.png)
+![testes-instore-es](//images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/9e729d91cf79c227665adeeb099b79ac/Group_6.png)
 
 ## Pruebas técnicas
 
diff --git a/docs/tracks/es/billing-support.md b/docs/tracks/es/billing-support.md
new file mode 100644
index 000000000..74adce2ec
--- /dev/null
+++ b/docs/tracks/es/billing-support.md
@@ -0,0 +1,53 @@
+---
+title: 'Soporte financiero'
+id: 3g2mhmPDx5GszNgLDICzsl
+status: PUBLISHED
+createdAt: 2024-02-20T21:41:41.795Z
+updatedAt: 2024-02-22T14:08:36.105Z
+publishedAt: 2024-02-22T14:08:36.105Z
+firstPublishedAt: 2024-02-22T14:08:36.105Z
+contentType: trackArticle
+productTeam: Others
+slug: soporte-financiero
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+Después de que [el cliente llega a VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz), pueden surgir dudas relacionadas con cambios en los datos de registro, información de cobros, facturas y otros aspectos financieros de la cuenta. En este sentido, el soporte financiero está disponible para ayudar en cuestiones contractuales y financieras relacionadas con las tiendas y VTEX.
+
+Puedes empezar consultando los artículos del Help Center y las secciones presentadas a continuación:
+
+## Cuentas por pagar
+
+VTEX tiene como objetivo garantizar el cumplimiento de los procedimientos y políticas de pago a los proveedores de sus sucursales; para hacerlo, implementó prácticas específicas que los proveedores deben seguir, dependiendo de su ubicación:
+
+- [Cuentas por pagar - Brasil](https://help.vtex.com/pt/tutorial/contas-a-pagar-brasil--tutorials_660): prácticas a seguir para todos los pagos a proveedores relacionados con los procedimientos de cuentas por pagar de las sucursales de VTEX en Brasil.
+- [Cuentas por pagar - Internacional](https://help.vtex.com/es/tutorial/cuentas-por-pagar-internacional--3yea9sIlsA0KgUC28ASCGs): prácticas a seguir para todos los pagos a proveedores relacionados con los procedimientos de cuentas por pagar de las sucursales de VTEX a excepción de Brasil.
+
+<div class = "alert alert-info">
+Para consultar la lista de sucursales VTEX en todo el mundo y saber en qué país se emiten facturas, consulta el artículo <a href="https://help.vtex.com/es/tutorial/nombres-de-las-sucursales-vtex-en-el-mundo--zg05n6OIOZOEmLW7dcq9z"> País de facturación de la tienda. </a>
+</div>
+
+## Cálculo de los ingresos por facturación por VTEX
+
+Los ingresos se refieren a los pedidos marcados como `Pedidos aprobados` en [la página detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl). Una vez aprobado financieramente un pedido, en la facturación se tiene en cuenta el valor total del mismo, incluyendo el envío y los impuestos finales. Esto ocurre independientemente de las cancelaciones posteriores, debido al propio uso de la infraestructura de la plataforma.
+
+A través del módulo **Pedidos** también puedes descargar el informe financiero, ver el desglose de facturas y cuáles son los valores de los ingresos aprobados.
+
+Para más información, consulta los artículos [¿Qué considera VTEX como ingresos en el cálculo de la factura? y Entiende los valores de los ingresos aprobados](https://help.vtex.com/es/tutorial/que-considera-vtex-como-ingresos-en-el-calculo-de-facturacion--58j4cfoXfisWyemASACwSq).
+
+## Modificar los datos registrados de la tienda
+
+Tras el primer acceso, es posible modificar los datos registrados de la tienda, como:
+
+- Correcciones e inclusión de contactos.
+- Transferencia de responsabilidad.
+- Modificar el documento de identificación de la cuenta.
+
+Para realizar estas modificaciones es necesario [abrir un ticket de soporte financiero](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#financiero), especificando el tipo de modificación requerida.
+
+<div class = "alert alert-info">
+Para obtener más información sobre cómo solicitar una evaluación de SLA y los descuentos concedidos por infracciones de SLA, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-solicitar-la-verificacion-de-sla--3L99VeoLhYEwMqqkWKu86i"> Cómo solicitar la verificación de SLA de operación de la plataforma. </a>
+</div>
+
diff --git a/docs/tracks/es/canceling-an-order.md b/docs/tracks/es/canceling-an-order.md
index 18f0e9569..0b6f641bc 100644
--- a/docs/tracks/es/canceling-an-order.md
+++ b/docs/tracks/es/canceling-an-order.md
@@ -3,8 +3,8 @@ title: 'Cancelar pedido'
 id: 4ts2ItvjYo8wm5gg76miS3
 status: PUBLISHED
 createdAt: 2019-11-18T11:50:32.691Z
-updatedAt: 2023-03-22T23:28:21.211Z
-publishedAt: 2023-03-22T23:28:21.211Z
+updatedAt: 2024-04-01T18:04:36.603Z
+publishedAt: 2024-04-01T18:04:36.603Z
 firstPublishedAt: 2019-11-18T12:20:50.741Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -23,6 +23,10 @@ Usted puede cancelar un pedido con VTEX de tres maneras diferentes:
 Una vez cancelado el pedido, no se puede cambiar su status. Es posible cancelar el pedido hasta antes de <b>Facturado</b>, después el pedido no puede ser modificado.
 </div>
 
+<div class = "alert alert-info">
+No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
+</div>
+
 ## Cancelación por el módulo Pedidos
 
 1. En el Admin VTEX, accede a **Pedidos > Todos los pedidos**, o escribe **Todos los pedidos** en la barra de búsqueda en la parte superior de la página.
diff --git a/docs/tracks/es/cart-transfer-and-capture.md b/docs/tracks/es/cart-transfer-and-capture.md
index 996390b5f..4b51be5e0 100644
--- a/docs/tracks/es/cart-transfer-and-capture.md
+++ b/docs/tracks/es/cart-transfer-and-capture.md
@@ -20,11 +20,11 @@ VTEX Sales App permite [habilitar una funcionalidad de transferencia de carrito]
 
 Para compartir un carrito, el vendedor puede generar un código numérico o un código QR. Para hacer esto, mientras está en la pantalla del carrito, haga clic en el botón __Transferir__. Vea un ejemplo en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
 
 Al hacer clic en este botón, la aplicación muestra un código QR y un código numérico de cuatro dígitos.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Otro vendedor vinculado a la misma tienda puede capturar ese carrito y continuar la venta desde su dispositivo.
 
@@ -34,7 +34,7 @@ Para capturar un carrito, ingrese al menú principal de VTEX Sales App y haga cl
 
 Alternativamente, en la pantalla de inicio de la aplicación, el vendedor simplemente puede arrastrar la pantalla hacia la derecha. Cuando arrastre la pantalla hacia la derecha, verá la pantalla para __Capturar Carrito__, como se muestra en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
 
 En esta pantalla, el vendedor puede capturar un carrito utilizando uno de estos tres métodos:
 - Código del carrito
diff --git a/docs/tracks/es/cart-transfer.md b/docs/tracks/es/cart-transfer.md
index 16e19d391..3d8363054 100644
--- a/docs/tracks/es/cart-transfer.md
+++ b/docs/tracks/es/cart-transfer.md
@@ -31,14 +31,14 @@ window.INSTORE_CONFIG = {
 
 Al realizar este cambio, debe darse cuenta de que aparecerán dos bolitas al final de la página de identificación del inStore:
 
-![01 inStore slider transferencia](https://images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
+![01 inStore slider transferencia](//images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
 
 Al arrastrar la pantalla hacia el lateral verá la pantalla para __ "Capturar carrito" __:
 
-![02 inStore capturar carrinho](https://images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
+![02 inStore capturar carrinho](//images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
 
 En ella es posible capturar un carrito por el código del carrito, QR code o incluso por vendedor.
 
 Para generar un código o código QR de un carro usted debe usar la opción __ "Transferir" __ presente en el carrito del inStore:
 
-![03 inStore transferir](https://images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
+![03 inStore transferir](//images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
diff --git a/docs/tracks/es/catalog-architecture.md b/docs/tracks/es/catalog-architecture.md
index f231aabbe..544f721a2 100644
--- a/docs/tracks/es/catalog-architecture.md
+++ b/docs/tracks/es/catalog-architecture.md
@@ -35,4 +35,4 @@ Estas especificaciones son, por ejemplo, la composición de un producto, o el ta
 
 A continuación, vea un esquema de la arquitectura del Catálogo en VTEX:
 
-![arquitetura-catalogo-ES](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
+![arquitetura-catalogo-ES](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
diff --git a/docs/tracks/es/catalog-concept-definition.md b/docs/tracks/es/catalog-concept-definition.md
index 8976c160d..0523d5c40 100644
--- a/docs/tracks/es/catalog-concept-definition.md
+++ b/docs/tracks/es/catalog-concept-definition.md
@@ -18,7 +18,7 @@ El menú **Catálogo** contiene las funcionalidades relativas al surtido de prod
 
 El menú **Catálogo** de tu Admin actualizado reúne las páginas donde gestionas tu catálogo, los precios y el stock de tu *ecommerce*.
 
-![visao-geral-produto-ES](https://images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/ad397a99b3db19ea9187ef5667577a26/image.png)
+![visao-geral-produto-ES](//images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/ad397a99b3db19ea9187ef5667577a26/image.png)
 
 El **Catálogo** permite la configuración de funcionalidades relacionadas con el surtido de productos del *ecommerce*, como sus categorías, marcas y colecciones, por ejemplo. Para vender tus productos, debes registrarlos en esta sección.
 
diff --git a/docs/tracks/es/centauro-marketplace.md b/docs/tracks/es/centauro-marketplace.md
index 3ec4f9226..2c23a6462 100644
--- a/docs/tracks/es/centauro-marketplace.md
+++ b/docs/tracks/es/centauro-marketplace.md
@@ -3,8 +3,8 @@ title: 'Centauro Marketplace'
 id: 5HXEYuDGxv7hNVUma3PKPC
 status: PUBLISHED
 createdAt: 2020-10-20T14:22:13.423Z
-updatedAt: 2021-03-22T15:41:41.809Z
-publishedAt: 2021-03-22T15:41:41.809Z
+updatedAt: 2023-09-22T20:08:49.350Z
+publishedAt: 2023-09-22T20:08:49.350Z
 firstPublishedAt: 2020-10-20T14:23:14.172Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/changing-the-instore-language.md b/docs/tracks/es/changing-the-instore-language.md
index 6d84012b9..8008f09d1 100644
--- a/docs/tracks/es/changing-the-instore-language.md
+++ b/docs/tracks/es/changing-the-instore-language.md
@@ -80,4 +80,4 @@ Después de hacer el cambio de código, guarde el archivo `checkout-instore-cust
 
 Luego, en la aplicación inStore, para ver los cambios reflejados, ingrese al menú y haga clic en el botón __Restaurar datos__, como se muestra en la imagen a continuación.
 
-![22. Change the inStore language - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6kyOLVTDlyawsehMQwORid/589ff63de4574dc8cf1d9cc3ed84024a/22._Change_the_inStore_language_-_1_-_ES.png_h_250)
+![22. Change the inStore language - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6kyOLVTDlyawsehMQwORid/589ff63de4574dc8cf1d9cc3ed84024a/22._Change_the_inStore_language_-_1_-_ES.png_h_250)
diff --git a/docs/tracks/es/cms-folder-structure.md b/docs/tracks/es/cms-folder-structure.md
index d9b799e6a..aaef10e49 100644
--- a/docs/tracks/es/cms-folder-structure.md
+++ b/docs/tracks/es/cms-folder-structure.md
@@ -34,7 +34,7 @@ Toda tienda debe tener, sin excepción, las siguientes carpetas en el CMS para a
 
 Vea abajo estas carpetas básicas en el CMS:
 
-![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas carpetas vienen de forma predeterminada en el ambiente de todas las tiendas VTEX.
 
diff --git a/docs/tracks/es/cms-vtex-io.md b/docs/tracks/es/cms-vtex-io.md
index 4a1f9aae7..32c7e0921 100644
--- a/docs/tracks/es/cms-vtex-io.md
+++ b/docs/tracks/es/cms-vtex-io.md
@@ -28,19 +28,19 @@ Configura el [binding de la tienda](https://help.vtex.com/en/tutorial/what-is-cm
 
 Binding es el proceso para vincular tu sitio web a una tienda. Para más detalles, consulta el artículo [Vincular una tienda a una estructura de carpetas en CMS (binding)](https://help.vtex.com/en/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![CMS - Layout ES](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
+![CMS - Layout ES](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
 
 ## Páginas
 En **[Páginas](https://help.vtex.com/es/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc)**, crea una nueva URL y enlázala a una plantilla ya definida en el [código del tema de la tienda](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-4-configuringtemplates).
 
-![CMS - Páginas](https://images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/b6c227e2c39991747ae1c60b826269e7/cms-pages-es.png)
+![CMS - Páginas](//images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/b6c227e2c39991747ae1c60b826269e7/cms-pages-es.png)
 
 Además, esta sección contiene la página **Redirecciones**, que redirige a los usuarios y a los motores de búsqueda de una URL a otra más relevante o similar. 
 
 ## Site Editor
 El **[Site Editor](https://help.vtex.com/es/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1)** es una interfaz gráfica para gestionar el contenido de tu storefront. Te permite crear, editar, publicar y programar cambios en los componentes y el comportamiento de tu storefront.
 
-![CMS - Site Editor ES](https://images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/e44ac6d9f16a0523d476ccf15cf55fec/cms-siteeditor-es.png)
+![CMS - Site Editor ES](//images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/e44ac6d9f16a0523d476ccf15cf55fec/cms-siteeditor-es.png)
 
 ## Estilos
 
@@ -50,12 +50,12 @@ La sección **[Estilos](https://help.vtex.com/pt/tutorial/styles-overview--v0Db5
   Este recurso solo funciona en production workspaces <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-creating-a-production-workspace">espacios de trabajo de producción</a>.
 </div>
 
-![CMS - Estilos](https://images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/b6562343e0c7cfd98210964a5dfd30e8/cms-styles-es.png)
+![CMS - Estilos](//images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/b6562343e0c7cfd98210964a5dfd30e8/cms-styles-es.png)
 
 ## Tienda
 La sección **[Tienda](https://help.vtex.com/es/tutorial/cms-loja-visao-geral--3Eat287G6wUi6Mly5rW5Fs)** es donde se configuran los ajustes de SEO, de las flags de optimización de rendimiento y se habilitan las notificaciones push de PWA en tu tienda.
 
-![CMS - Tienda](https://images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/02496bd9a4cdcb3ebbf6baeb51a50044/cms-store-es.png)
+![CMS - Tienda](//images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/02496bd9a4cdcb3ebbf6baeb51a50044/cms-store-es.png)
 
 ## Referencias
 - [Layout - Sites and channels](https://help.vtex.com/es/tutorial/what-is-cms-layout--EmO8u2WBj2W4MUQCS8262?&utm_source=autocomplete#sites-and-channels)
diff --git a/docs/tracks/es/commercial-support.md b/docs/tracks/es/commercial-support.md
new file mode 100644
index 000000000..34f6c4da5
--- /dev/null
+++ b/docs/tracks/es/commercial-support.md
@@ -0,0 +1,35 @@
+---
+title: 'Soporte comercial'
+id: 3KQWGgkPOwbFTPfBxL7YwZ
+status: PUBLISHED
+createdAt: 2024-02-20T21:44:41.944Z
+updatedAt: 2024-02-22T14:08:28.702Z
+publishedAt: 2024-02-22T14:08:28.702Z
+firstPublishedAt: 2024-02-22T14:08:28.702Z
+contentType: trackArticle
+productTeam: Others
+slug: soporte-comercial
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+Además de los recursos ya previstos en el contrato inicial con VTEX, es posible adquirir soluciones y activar otras funcionalidades para ampliar la operación del negocio. Para hacerlo, el soporte comercial brinda orientación sobre:
+
+- Contratar [política comercial adicional](#contratacion-de-políticas-comerciales-adicionales), [entorno adicional](#contratacion-de nuevo entorno) y cuenta franquicia.
+- Modificar [usuario titular](https://help.vtex.com/es/tutorial/que-es-el-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy).
+- Adquirir [productos add-on](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+
+Puedes [abrir un ticket con el soporte comercial](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM) si necesitas ayuda con otros temas o para adquirir un producto add-on. Para un primer contacto, consulta los artículos del [Help Center](https://help.vtex.com/es/) y las secciones presentadas a continuación.
+
+## Contratación de políticas comerciales adicionales
+
+La [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) es un recurso de las tiendas VTEX que define las condiciones y estrategias de venta en un canal de ventas, ya sea en la propia tienda, marketplaces, tiendas físicas o modelos B2B. Una operación puede tener una sola política comercial y ser suficiente; es el modelo de negocio el que definirá cuántas políticas comerciales se asociarán a la cuenta.
+
+Para decidir si [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacion-de-politicas-comerciales-adicionales--61vuFOw4yGh6nwSmkLJL1X), hay que entender si la cuenta necesita un entorno adicional o multitienda. El artículo [Cuentas y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) presenta estos conceptos en detalle.
+
+## Contratación de nuevo entorno
+
+Solamente la cuenta principal puede contratar nuevos entornos, que pueden utilizarse para pruebas (QA), B2C, B2B, etc. Esta contratación se solicita a través del [soporte VTEX](https://help.vtex.com/es/support).
+
+Dependiendo del modelo de negocio y de la estrategia empresarial, puede ser recomendable contratar un nuevo entorno. Para ello, es necesario tener nociones sobre multitienda y entorno adicional, tal como se explica en el artículo [Cuentas y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl).
diff --git a/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md b/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md
index c1ca4cbdf..43c48dd7d 100644
--- a/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md
+++ b/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuración de la estructura para Servicio al cliente humano'
 id: SxhYiiqUJYiQX4CIWxmVE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T15:25:37.553Z
-updatedAt: 2023-04-27T15:32:38.909Z
-publishedAt: 2023-04-27T15:32:38.909Z
+updatedAt: 2024-01-05T17:14:19.560Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:47:18.082Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/es/configure-customer-identification.md b/docs/tracks/es/configure-customer-identification.md
index 10b2d85c0..a9054e679 100644
--- a/docs/tracks/es/configure-customer-identification.md
+++ b/docs/tracks/es/configure-customer-identification.md
@@ -26,11 +26,11 @@ Para elegir qué métodos de identificación desea habilitar, acceda al panel ad
 
 En el cuadro __Inicio de sesión del cliente__, usted debe seleccionar los métodos de identificación que desea habilitar.
 
-![21. Configure client identification - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/4efcT1xJ2naRxi5pUykS1M/4f9e6cd6f793a6126e956cbd023863e4/21._Configure_client_identification_-_1_-_ES.png_h_250)
+![21. Configure client identification - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/4efcT1xJ2naRxi5pUykS1M/4f9e6cd6f793a6126e956cbd023863e4/21._Configure_client_identification_-_1_-_ES.png_h_250)
 
 También puede cambiar el orden de estos métodos. Para hacer esto, arrástrelos como se muestra en la imagen a continuación. El orden de los métodos definidos en esta pantalla determina el orden en que aparecerán para el vendedor en la aplicación. Por lo tanto, el primer método será el predeterminado.
 
-![21. Configure client identification - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/1oZXmjWc7ii8yirafQiiEQ/50cc598d8e315665968919c04bdd1164/21._Configure_client_identification_-_2_-_ES.png_h_250)
+![21. Configure client identification - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/1oZXmjWc7ii8yirafQiiEQ/50cc598d8e315665968919c04bdd1164/21._Configure_client_identification_-_2_-_ES.png_h_250)
 
 ## Habilitar usuario anónimo
 
@@ -38,7 +38,7 @@ Es posible utilizar inStore para atender a los clientes de forma anónima, es de
 
 Para esto, aún en la pantalla de Identificación del Cliente, es necesario habilitar la flag __Usuario anónimo__.
 
-![21. Configure client identification - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/5rkF0v7jr91rGCQsbIgAGV/73dd9f1c038c42bef465e4507152f05f/21._Configure_client_identification_-_3_-_ES.png_h_250)
+![21. Configure client identification - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/5rkF0v7jr91rGCQsbIgAGV/73dd9f1c038c42bef465e4507152f05f/21._Configure_client_identification_-_3_-_ES.png_h_250)
 
 ## Registro de entidad legal para ventas B2B
 
@@ -50,10 +50,10 @@ A continuación, puede elegir si estos campos deben completarse necesariamente o
 
 En el siguiente ejemplo, el registro de la entidad legal se activa y configura como opcional.
 
-![21. Configure client identification - 4 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6AidakHNTZAZxB9ygG14aF/310070d0cf327cd90c1915dbb05b7e4f/21._Configure_client_identification_-_4_-_ES.png_h_250)
+![21. Configure client identification - 4 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6AidakHNTZAZxB9ygG14aF/310070d0cf327cd90c1915dbb05b7e4f/21._Configure_client_identification_-_4_-_ES.png_h_250)
 
 En este caso, la aplicación le mostrará al vendedor un formulario como el siguiente:
 
-![21. Configure client identification - 5.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/aa10e2401c309494320033a556b323f4/21._Configure_client_identification_-_5.png_h_250_h_250)
+![21. Configure client identification - 5.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/aa10e2401c309494320033a556b323f4/21._Configure_client_identification_-_5.png_h_250_h_250)
 
 Tenga en cuenta que se muestra una flag que le permite al vendedor decidir si mostrar estos campos adicionales o no. Esto se debe a que, en la configuración, marcamos los campos de registro de la entidad legal como opcionales. Si están marcados como obligatorios, esta flag no se mostrará en la aplicación.
diff --git a/docs/tracks/es/configure-integration-of-pick-up-points.md b/docs/tracks/es/configure-integration-of-pick-up-points.md
index ffeccf83c..0db7955b5 100644
--- a/docs/tracks/es/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/es/configure-integration-of-pick-up-points.md
@@ -1,16 +1,16 @@
 ---
 title: 'Configurar la integración de los puntos de recogida '
 id: 52C1lm8gMovN8v68s6v89d
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-08-12T18:12:20.076Z
-updatedAt: 2021-09-08T17:52:30.570Z
-publishedAt: 2021-09-08T17:52:30.570Z
+updatedAt: 2024-03-11T22:19:05.610Z
+publishedAt: 
 firstPublishedAt: 2021-08-19T15:16:01.224Z
 contentType: trackArticle
 productTeam: Channels
 slug: configurar-la-integracion-de-los-puntos-de-recogida
 locale: es
-trackId: 2YfvI3Jxe0CGIKoWIGQEIq
+trackId: 
 trackSlugES: configurar-integracion-con-mercado-libre
 ---
 
@@ -58,7 +58,7 @@ Para ativar os pontos de retirada nas contas franquias:
 1. Acceda al Admin VTEX.
 2. En el módulo MARKETPLACE, seleccione **Integraciones**.
 3. Luego, haga clic en `Configuración`.
-4. En la integración de Mercado Libre, haga clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+4. En la integración de Mercado Libre, haga clic en el ícono de engranaje <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 5. Elija la opción `Editar configuración`.
 6. En el campo **Activar integración de los puntos de recogida de las cuentas franquicia**, haga clic en la opción `Sí`.
 7. Haga clic en `Guardar configuración`.
diff --git a/docs/tracks/es/configure-integration.md b/docs/tracks/es/configure-integration.md
index e13189581..5b8d6c900 100644
--- a/docs/tracks/es/configure-integration.md
+++ b/docs/tracks/es/configure-integration.md
@@ -3,8 +3,8 @@ title: 'Configurar integración'
 id: 3tZ4qVuMDDsC2jx2DCmjdA
 status: PUBLISHED
 createdAt: 2021-03-16T20:17:00.970Z
-updatedAt: 2022-09-06T22:49:30.916Z
-publishedAt: 2022-09-06T22:49:30.916Z
+updatedAt: 2024-07-26T19:06:41.787Z
+publishedAt: 2024-07-26T19:06:41.787Z
 firstPublishedAt: 2021-03-18T20:12:33.299Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,5 +14,5 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugES: configurar-la-integracion-de-magazine-luiza
 ---
 
-<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+<div class="alert alert-warning">Este contenido es exclusivamente regional; 
 por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/configure-warranty-in-via-varejo.md b/docs/tracks/es/configure-warranty-in-via-varejo.md
index a3d6c6569..614028a34 100644
--- a/docs/tracks/es/configure-warranty-in-via-varejo.md
+++ b/docs/tracks/es/configure-warranty-in-via-varejo.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar la garantía de Via Varejo'
+title: 'Configurar la garantía de Casas Bahia Marketplace'
 id: 3FFcVmL5Aod6tkFIz9vJmX
 status: PUBLISHED
 createdAt: 2020-10-01T19:13:10.864Z
-updatedAt: 2022-01-24T20:11:25.306Z
-publishedAt: 2022-01-24T20:11:25.306Z
+updatedAt: 2023-11-30T21:39:33.028Z
+publishedAt: 2023-11-30T21:39:33.028Z
 firstPublishedAt: 2020-10-01T20:32:16.599Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/configuring-a-payment-condition.md b/docs/tracks/es/configuring-a-payment-condition.md
index 2641cf383..e9e07c9fc 100644
--- a/docs/tracks/es/configuring-a-payment-condition.md
+++ b/docs/tracks/es/configuring-a-payment-condition.md
@@ -3,8 +3,8 @@ title: 'Configurar una condición de pago '
 id: 6bzGxlz4inf8sKmvZ1c7i3
 status: PUBLISHED
 createdAt: 2019-11-26T17:47:27.426Z
-updatedAt: 2023-03-21T20:02:36.184Z
-publishedAt: 2023-03-21T20:02:36.184Z
+updatedAt: 2024-03-13T21:42:43.233Z
+publishedAt: 2024-03-13T21:42:43.233Z
 firstPublishedAt: 2019-11-26T20:43:48.321Z
 contentType: trackArticle
 productTeam: Financial
@@ -27,17 +27,18 @@ Las condiciones de pago son las reglas que debe seguir una persona que desee com
 Dicho esto, podemos pasar a configurar el medio de pago en sí.
 
 ## Configuraciones generales
-Para configurar una condición de pago, primero debe registrar una afiliación, como se explica en el documento [Afiliaciones de Gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway/).
 
-Sin embargo, lo que no cambia de una forma de pago a otra es la necesidad de:
-- Definir el nombre de la regla, que se puede identificar de acuerdo con lo que esta representa.
-- Activarla.
-- Definir por cuál afiliación de gateway se procesará esa condición.
-- Definir si usted va o no utilizar [antifraude](https://help.vtex.com/es/tutorial/como-configurar-antifraude?locale=pt).
+Para configurar una condición de pago, primero debe registrar un proveedor de pago, como se describe en [Registrar proveedores de pago y antifraude](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
 
-Además, es posible definir si el pago será al contado o en cuotas, con o sin intereses y [condiciones especiales](https://help.vtex.com/es/tutorial/condicoes-especiais--tutorials_456?locale=es "condiciones especiales").
+Independientemente de la condición de pago a elegir, siempre se deberán realizar las siguientes acciones:
+- Definir el nombre de la regla según lo que representa, para ayudar a identificarla;
+- Actívalo;
+- Definir qué proveedor de pago procesará esta condición;
+- Defina si utilizará o no [antifraude](https://help.vtex.com/es/tutorial/como-configurar-antifraude--tutorials_446).
 
-Dado que la condición de pago que permite todas estas configuraciones es "Tarjeta de Crédito", siga las etapas a continuación para cada una de estas configuraciones.
+Además, para algunas condiciones de pago puede ser necesario definir si el pago se realizará en efectivo o a plazos, con o sin intereses y [condiciones especiales](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+
+Como la __Tarjeta de Crédito__ es un método de pago que te permite aplicar todas estas características, mira a continuación cómo configurarla:
 
 ## Al contado 
 Aquí, antes de activar la condición de pago, debe verificar con el gateway o el adquirente si la bandera o el medio de pago está disponible en su sistema.
@@ -50,9 +51,9 @@ Hecho esto, siga las instrucciones:
 4. Escoja el medio de pago tarjeta de crédito.
 5. Denomine la regla en el campo **Nombre de la Regla**.
 6. Active la condición en el campo **Status**.
-7. En el campo **Proceso con la Afiliación**, elija la afiliación que configuró.
+7. En el campo **Procesar con proveedor**, elija el proveedor previamente configurado.
 8. En el campo **¿Al Contado o En Cuotas?**, seleccione la opción **Al Contado**.
-9. Haga clic en el botón **Guardar**.
+9. Haga clic en **Guardar**.
 
 ## En cuotas 
 
@@ -68,7 +69,7 @@ Cabe mencionar que el campo "Facturación" solo se tendrá en cuenta para cuotas
 4. Escoja el medio de pago tarjeta de crédito.
 5. Denomine la regla en el campo **Nombre de la Regla**.
 6. Active la condición en el campo **Status**.
-7. En el campo **Proceso con la Afiliación**, elija la afiliación que configuró.
+7. En el campo **Procesar con proveedor**, elija el proveedor previamente configurado.
 8. En el campo **¿Al Contado o En Cuotas?**, seleccione la opción **En Cuotas**.
 9. Configure el número de cuotas secuenciales o individuales en el campo Total de Cuotas.
 10. Defina una cuota mínima que se aplicará de acuerdo con el valor de cada producto.
@@ -83,7 +84,7 @@ Si decide configurar un medio de pago que acepte cuotas con intereses, este camp
 4. Escoja el medio de pago tarjeta de crédito.
 5. Denomine la regla en el campo **Nombre de la Regla**.
 6. Active la condición en el campo **Status**.
-7. En el campo **Proceso con la Afiliación**, elija la afiliación que configuró.
+7. En el campo **Procesar con proveedor**, elija el proveedor previamente configurado.
 8. En el campo **¿Al Contado o En Cuotas?**, seleccione la opción **En Cuotas**.
 9. Configure el número de cuotas secuenciales o individuales en el campo **Total de Cuotas**.
 10. Defina una cuota mínima que se aplicará de acuerdo con el valor de cada producto.
@@ -91,19 +92,15 @@ Si decide configurar un medio de pago que acepte cuotas con intereses, este camp
 12. Haga clic en el botón **Agregar Intereses**.
 13. Digite el valor de los intereses que desea aplicar a cada una de las cuotas. 
 14. Haga clic en **Interés compuesto aplicado. Cambiar** para escoger entre intereses compuestos o simples.
-15. Haga clic en el botón **Guardar**.  
+15. Haga clic en **Guardar**.  
 
 ### Cuota Automática
 La opción Cuota Automática le permite configurar los detalles de las cuotas directamente en el proveedor de pago (fuera del entorno VTEX).
-Para habilitar esta opción, seleccione "Sí" en el campo **Utilizar pago en cuotas externo** durante el paso de [configuración de afiliación](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444).
-
-![cuotaautomatica](https://images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/5e3f569ad3db6cb29111199467b34892/parcelamentoautomaticoes.JPG)
+Para habilitar esta opción, seleccione "Sí" en el campo **Utilizar pago en cuotas externo** durante el paso de [configuración de proveedor](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444).
 
-<div class="alert alert-warning">
-  Actualmente, solo la afiliación MercadoPagoV1 permite la función de cuota automática.
-</div>
+![cuotaautomatica](//images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/5e3f569ad3db6cb29111199467b34892/parcelamentoautomaticoes.JPG)
 
-Después de habilitar la cuota automática en la afiliación, siga estos pasos:
+Después de habilitar la cuota automática en el proveedor, siga estos pasos:
 
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
 2. Haga clic en **Condiciones de Pago**.
@@ -111,9 +108,9 @@ Después de habilitar la cuota automática en la afiliación, siga estos pasos:
 4. Escoja el medio de pago tarjeta de crédito.
 5. Denomine la regla en el campo **Nombre de la Regla**.
 6. Active la condición en el campo **Status**.
-7. En el campo **Proceso con la Afiliación**, elija la afiliación que configuró.
+7. En el campo **Procesar con proveedor**, elija el proveedor previamente configurado.
 8. Si desea utilizar un sistema antifraude, seleccione la opción **Usar antifraude**.
 9. Seleccione una opción antifraude.
 10. En el campo **¿Al Contado o En Cuotas?**, seleccione la opción **Automático**.
-11. Clique no botão **Salvar**.
+11. Haga clic en **Guardar**.
 
diff --git a/docs/tracks/es/configuring-banners.md b/docs/tracks/es/configuring-banners.md
index d51e0c50f..a10af26c8 100644
--- a/docs/tracks/es/configuring-banners.md
+++ b/docs/tracks/es/configuring-banners.md
@@ -3,8 +3,8 @@ title: 'Configurar Banners'
 id: 4ViKEivLJtJsvpaW0aqIQ5
 status: PUBLISHED
 createdAt: 2019-11-27T16:34:24.404Z
-updatedAt: 2023-03-30T21:35:08.898Z
-publishedAt: 2023-03-30T21:35:08.898Z
+updatedAt: 2024-01-30T21:59:49.330Z
+publishedAt: 2024-01-30T21:59:49.330Z
 firstPublishedAt: 2020-03-05T19:58:30.009Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -28,7 +28,7 @@ Después de configurar el banner, debes agregarlo a una página de tu tienda. Pa
 <p> Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configuración Multidioma (Beta)</a>para saber más.</p>
 </div>
 
-![banner-form-es](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
+![banner-form-es](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
 
 ## Campos de registro del banner
 
@@ -51,6 +51,7 @@ Para registrar el banner, debes rellenar los siguientes campos:
 * **Hora de inicio:** hora en la que el banner comenzará a estar disponible.
 * **Fecha de fin:** fecha en la que el banner dejará de estar disponible. Esto permite al administrador programar futuras campañas, lo que facilita su control.
 * **Hora de fin:** hora en la que el banner dejará de estar disponible.
+* **Idiomas:** idiomas en los que se aplicará el banner. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 
 ### Reglas de activación
 
@@ -58,7 +59,7 @@ Para registrar el banner, debes rellenar los siguientes campos:
 
 Haz clic en <i class="fa-solid fa-link"></i> `Autocompletar desde URL` para agregar la URL de la página de búsqueda donde se aplicarán las reglas de activación.
 
-![banner-url-es](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
+![banner-url-es](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
 
 Haz clic en <i class="fas fa-plus"></i> `Agregar condición` para crear una regla. Pueden ser de los siguientes tipos:
 
diff --git a/docs/tracks/es/configuring-cash-payments-through-instore.md b/docs/tracks/es/configuring-cash-payments-through-instore.md
index 64c9d15b6..7e2666145 100644
--- a/docs/tracks/es/configuring-cash-payments-through-instore.md
+++ b/docs/tracks/es/configuring-cash-payments-through-instore.md
@@ -34,7 +34,7 @@ Ahora vamos a crear la condición de pago.
 1. Aún en la página de **Configuración **del módulo de **Pagos**, haz clic en la pestaña **Planes de Pago**.
 2. Haz clic en el botón verde con el ícono `+` para añadir una nueva condición de pago, como se muestra a continuación.
 
-![es-add-payment-condition](https://images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/7aa38306086b2bb26b9b789b63baeeb0/es-add-payment-condition.png)
+![es-add-payment-condition](//images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/7aa38306086b2bb26b9b789b63baeeb0/es-add-payment-condition.png)
 
 3. En la sección __Pagos Personalizados__, haz clic en la opción __Efectivo__ que ha creado.
 4. Introduce un nombre para esta condición de pago, cambia el status a __Activo__, y en el campo __Procesar con la afiliación__, selecciona el pago personalizado que creaste en el paso anterior.
diff --git a/docs/tracks/es/configuring-dafiti-connector.md b/docs/tracks/es/configuring-dafiti-connector.md
index 94563552b..568897adb 100644
--- a/docs/tracks/es/configuring-dafiti-connector.md
+++ b/docs/tracks/es/configuring-dafiti-connector.md
@@ -3,8 +3,8 @@ title: 'Configuración del conector Dafiti'
 id: 3PV2OACP2E4O4uOKKW2sMg
 status: PUBLISHED
 createdAt: 2018-09-27T17:57:53.647Z
-updatedAt: 2022-01-25T15:51:13.004Z
-publishedAt: 2022-01-25T15:51:13.004Z
+updatedAt: 2024-07-02T19:17:57.983Z
+publishedAt: 2024-07-02T19:17:57.983Z
 firstPublishedAt: 2018-09-27T20:41:13.133Z
 contentType: trackArticle
 productTeam: Channels
@@ -50,6 +50,27 @@ Si se activa la opción <i>No</i>, los intentos de enviar SKU registrados como k
 
 - **Nombre de SKU*:** determina cuál será la regla para nombrar los SKU en el portal de Dafiti. Debe seleccionar una de las combinaciones disponibles de los siguientes atributos: _Marca_, _Nombre del Producto_ y _Nombre del SKU._
 
-  ![print tela nome exibição produto](https://drive.google.com/uc?export=download&id=1LZby5znJvD8J1ul7WagR70OWhr7J25Qp)
+![print nome exibicao produto es](//images.ctfassets.net/alneenqid6w5/3MiGbDbIXFGiawLcXjji5w/35e795635bba7aa025facd31d63d76d7/print_nome_exibicao_produto_es.png)
 
 > Ejemplo: mi producto es una zapatilla deportiva negra de Nike. El _Nombre de SKU_ que seleccioné fue _Marca - Nombre del Producto - Nombre del SKU_. Así, el nombre que aparecerá en el portal de Dafiti será Nike zapatilla deportiva negra.
+
+- **NCM:** es la Nomenclatura Común del Mercosur (NCM), que define la tasa impositiva común para el bloque. Para determinados productos, es necesario informar en este campo el nombre único de la especificación del producto o SKU responsable, que contiene la información de NCM en el catálogo.
+- **Id. de cliente:** código único asignado a un vendedor para acceder a la integración.
+- **Client Secret:** código único utilizado para autenticar la integración.
+- **Mapeo de campos personalizados (Nombre y descripción):** Para utilizar este mapeo es necesario crear un campo personalizado. Para saber cómo crear campos personalizados accede a la documentación de [Registrar especificaciones o campos de producto](https://help.vtex.com/es/tutorial/criando-um-campo-de-produto--tutorials_106).
+
+Para que el mapeo funcione, el seller debe seguir los siguientes pasos:
+
+1. Crea un campo de tipo `Texto grande`.  
+2. Deshabilite la opción `Mostrar especificación`.  
+3. Complete los campos creados en cada producto registrado.  
+
+Este campo debe completarse de la siguiente manera:
+
+1. Complete el campo **DESDE** con el nombre del campo de origen.  
+2. Complete el campo **PARA** con el nombre del nuevo campo.  
+3. Haga clic en el botón <i class="fas fa-plus" aria-hidden="true"></i> y se agregará una regla de mapeo a tu integración.  
+
+<div class = "alert alert-info">
+Cada regla registrada asigna solo un campo.
+
diff --git a/docs/tracks/es/configuring-livelo-price-divergence-rule.md b/docs/tracks/es/configuring-livelo-price-divergence-rule.md
new file mode 100644
index 000000000..c61e7cadd
--- /dev/null
+++ b/docs/tracks/es/configuring-livelo-price-divergence-rule.md
@@ -0,0 +1,18 @@
+---
+title: 'Configurar Livelo regla de Divergencia de precios'
+id: 4kocvdsHiLcLLcX6eQIVmD
+status: PUBLISHED
+createdAt: 2023-08-10T22:45:01.497Z
+updatedAt: 2024-02-19T19:09:00.244Z
+publishedAt: 2024-02-19T19:09:00.244Z
+firstPublishedAt: 2023-08-11T01:56:55.359Z
+contentType: trackArticle
+productTeam: Channels
+slug: configurar-livelo-regla-de-divergencia-de-precios
+locale: es
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugES: integracion-de-livelo
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/configuring-login-with-facebook.md b/docs/tracks/es/configuring-login-with-facebook.md
index a4aa08eed..671724c0a 100644
--- a/docs/tracks/es/configuring-login-with-facebook.md
+++ b/docs/tracks/es/configuring-login-with-facebook.md
@@ -28,7 +28,7 @@ Después de la configuración en Facebook, es necesario configurar esta opción
 1.  En el módulo de **Configuración de la cuenta**, acceda a la pestaña de **Autenticación**.
 2.  Haga clic en el botón **Editar** correspondiente a Facebook.
 3.  Rellene los campos con el _Client Id_ y _Client Secret_ registrados en **Facebook**.
-    ![Facebook OAuth ES](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/ffc13a1eb81a285feea15e78a72342b9/facebook_ES.png)
+    ![Facebook OAuth ES](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/ffc13a1eb81a285feea15e78a72342b9/facebook_ES.png)
 4.  Haga clic en el botón **Salvar**. 
 5.  Para validar si el inicio de sesión se hizo correctamente, acceda al  front-end de su tienda y haga clic en **Login**.
 6. Aparecerán las opciones de inicio de sesión configuradas. Haga clic en la opción **Facebook** y compruebe si se muestra el nombre de su tienda.
diff --git a/docs/tracks/es/configuring-login-with-google.md b/docs/tracks/es/configuring-login-with-google.md
index 9c996f7d9..083b471c1 100644
--- a/docs/tracks/es/configuring-login-with-google.md
+++ b/docs/tracks/es/configuring-login-with-google.md
@@ -29,7 +29,7 @@ Después de hacer la configuración en Google, puede configurar el inicio de ses
 1.  En el módulo **Configuración de la cuenta**, acceda a la pestaña **Autenticación**.  
 2.  Haga clic en el botón **Editar** correspondiente a Google.
 3.  Complete los campos ingresando el _Client Id_ y _Client Secret_ registrados en **Google**.
-    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
+    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
 5.  Haga clic en el botón **Salvar**. 
 6. Para validar si el inicio de sesión se hizo correctamente, acceda al front-end de su tienda y haga clic en **Login**.
 7. Las opciones de inicio de sesión aparecerán configuradas. Haga clic en la opción **Google** y verifique si se muestra el nombre de su tienda.    
diff --git a/docs/tracks/es/configuring-merchandising-rules.md b/docs/tracks/es/configuring-merchandising-rules.md
index 3b190bb91..198d7f896 100644
--- a/docs/tracks/es/configuring-merchandising-rules.md
+++ b/docs/tracks/es/configuring-merchandising-rules.md
@@ -3,8 +3,8 @@ title: 'Crear regla de merchandising - Editor manual'
 id: 2FpbarYzsnbg7aZZn3TGF8
 status: PUBLISHED
 createdAt: 2020-04-14T14:10:24.518Z
-updatedAt: 2023-04-03T22:07:36.546Z
-publishedAt: 2023-04-03T22:07:36.546Z
+updatedAt: 2024-01-29T16:58:41.850Z
+publishedAt: 2024-01-29T16:58:41.850Z
 firstPublishedAt: 2020-04-15T00:39:30.807Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -23,8 +23,8 @@ Si deseas configurar una [regla de merchandising](https://help.vtex.com/es/track
     * **Nombre de la regla**: nombre de la regla de _merchandising_. Ejemplo: promover el producto A cuando se busca «galletas de chocolate».
     * **Fecha de inicio (opcional)**: define la fecha a partir de la cual se aplicará la regla de _merchandising_. La fecha considera la zona horaria UTC-0.
     * **Fecha de fin (opcional)**: define la fecha en que la regla de _merchandising_ dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
-    * **Regiones:** idiomas en los que se aplicará la regla de _merchandising_.
-5. Haz clic en **Editor manual**. Para más información sobre cada editor, consulta [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicion).
+    * **Aplicar a los idiomas:** idiomas en los que se aplicará la regla de merchandising. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Haga clic en **Editor Manual**. Para más información sobre cada editor, consulte [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicion).
 6. Haz clic en `Siguiente`.
 7. Si lo necesitas, modifica la información básica ya definida sobre la nueva regla de _merchandising_ en la sección [Información general](#informacion-general).
 8. Define las [Reglas de activación](#reglas-de-activacion),  es decir, el conjunto de condiciones que determinan cuándo se aplicará la regla de merchandising.
@@ -36,6 +36,8 @@ Si deseas configurar una [regla de merchandising](https://help.vtex.com/es/track
   <p>Una vez guardados, la actualización de los cambios en las reglas de merchandising demoran un promedio de dos minutos.</p>
 </div>
 
+## Ejemplo
+
 Considera el siguiente ejemplo: deseas promover productos de la marca Beautyx durante la semana de un carnaval de modo que cuando el cliente busque «jabón» o «champú», la búsqueda promueva los productos de la marca Beautyx. Para esto, debes configurar la regla de _merchandising_ del siguiente modo:
 
 * **Nombre**: Promoción de carnaval
diff --git a/docs/tracks/es/configuring-payment-connectors.md b/docs/tracks/es/configuring-payment-connectors.md
index d313f1c2c..6c8ea99bb 100644
--- a/docs/tracks/es/configuring-payment-connectors.md
+++ b/docs/tracks/es/configuring-payment-connectors.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar un conector de pagos'
+title: 'Configurar un provedor de pagos'
 id: 7pAEMAo4iqNHwYOarZ3zgm
 status: PUBLISHED
 createdAt: 2019-11-12T17:29:10.501Z
-updatedAt: 2023-03-21T20:10:49.512Z
-publishedAt: 2023-03-21T20:10:49.512Z
+updatedAt: 2024-07-29T14:50:02.445Z
+publishedAt: 2024-07-29T14:50:02.445Z
 firstPublishedAt: 2019-11-24T21:05:50.533Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,32 +14,19 @@ trackId: 6GAS7ZzGAm7AGoEAwDbwJG
 trackSlugES: pagos
 ---
 
-El módulo de **Pagos** permite la configuración de una serie de **conectores**, que son protocolos de comunicación que su tienda necesita usar para permitir la transmisión de datos entre esta y adquirentes, subadquirentes o gateways. 
+El módulo __Pagos__ permite configurar varios proveedores de pagos (pasarelas, adquirentes, subadquirentes, [orquestadores](https://www.y.uno/en), [PSP](https://en.wikipedia.org/wiki/Payment_service_provider), entre otros) en tu tienda. De esta forma, podrás ofrecer diferentes métodos y condiciones de pago a tus clientes.
 
-Por ejemplo, para que su sitio web ofrezca un determinado medio de pago particular a sus clientes, usted debe activar el **conector** que se comunicará con el gateway responsable del procesamiento.
+Cuando se realiza una compra en su tienda y el cliente realiza el pago, la transmisión de datos entre VTEX y el proveedor elegido se produce a través de protocolos de comunicación configurados en el VTEX Admin.
 
-Otra característica importante es la igualdad de conexiones. Así como un medio de pago puede comunicarse con varios  conectores, un conector puede establecer comunicación con varios medios de pago. Debido a esta posibilidad, debe configurar el conector a través de **afiliaciones de gateway**.
+<div class="alerta alerta-info">
+  Para comprobar qué proveedores de pago están disponibles en su región y los respectivos artículos de configuración, visite <a href="https://help.vtex.com/es/tutorial/lista-de-proveedores-de-pago-por-pais--2im3BEGXxSAcRuxEaIHPvp">Lista de proveedores de pago por país</a>.</p>
+</div>
 
-**Afiliaciones de Gateway** es un conjunto de configuraciones que representa su contrato con un gateway de pago de su elección. 
+A continuación se muestra un ejemplo de cómo configurar un proveedor de pagos:
 
-Además de los gateways de pago, otras afiliaciones incluyen, por ejemplo, pagarés, adquirentes y adquirentes. Con esto es posible decidir por cuál gateway de pago se procesarán  los diferentes tipos de transacciones de su tienda VTEX.
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Proveedores__, o escriba __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón "Nuevo proveedor".
+3. Escriba el proveedor de pago deseado en la barra de búsqueda y haga clic en su nombre.
+4. Complete los campos disponibles según la información del proveedor de pago con el que tiene contrato.
+5. Haga clic en "Guardar".
 
-El Módulo de Pagos VTEX soporta múltiples afiliaciones con una o más gateways de su elecciónn para procesar diferentes formas de pago.
-
-Hay dos formas para comenzar a aceptar pagos con tarjeta de crédito:
-- Afiliarse a un gateway de pago por el admin.
-- Utilizar las [integraciones de VTEX](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-guide) para medios de pago.
-
-## Cómo registrar afiliaciones de gateway por el Admin
-1.  En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.   
-2.  Haga clic en la opción **Afiliaciones de Gateway**.   
-3.  Haga clic en el botón de **+**  para agregar una nueva afiliación.   
-4.  Escoja cuál es su Gateway de Pago.   
-5.  Dele un nombre a su afiliación.
-6.  Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón **Instalar aplicación** y siga las instrucciones de instalación. Este mensaje solo se muestra para algunos tipos de afiliaciones de pgateway.   
-7.  Complete los campos disponibles con los datos del contrato enviados por el Gateway escogido.   
-8.  Haga clic en el botón **Guardar**.
-
-Este conector debe estar asociado a una condición de pago. Para más informaciones y ejemplos de cómo recibir pagos en cuotas o al contado con diferentes afiliaciones, vea el artículo sobre  [Condiciones de Pago](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
-
-Si desea consultar el procedimiento de un conector específico, visite nuestros artículos de [Tutoriales y Soluciones](https://help.vtex.com/es/tutorial/--531cHtUCUi3puRXNDmKziw "Tutoriales y Soluciones"), y busque la palabra clave deseada. 
diff --git a/docs/tracks/es/configuring-physical-stores-as-pickup-points.md b/docs/tracks/es/configuring-physical-stores-as-pickup-points.md
index 12794781e..e41f67cb8 100644
--- a/docs/tracks/es/configuring-physical-stores-as-pickup-points.md
+++ b/docs/tracks/es/configuring-physical-stores-as-pickup-points.md
@@ -3,8 +3,8 @@ title: 'Tiendas físicas como puntos de recogida'
 id: 4hXfgqXxS1lwAfnxgja3xW
 status: PUBLISHED
 createdAt: 2021-08-23T17:04:37.282Z
-updatedAt: 2023-05-31T14:45:23.483Z
-publishedAt: 2023-05-31T14:45:23.483Z
+updatedAt: 2023-07-26T18:51:23.201Z
+publishedAt: 2023-07-26T18:51:23.201Z
 firstPublishedAt: 2021-08-23T17:12:50.884Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/es/configuring-price-divergence-rule-dafiti.md b/docs/tracks/es/configuring-price-divergence-rule-dafiti.md
index 550a09f74..41fee498e 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-dafiti.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-dafiti.md
@@ -3,8 +3,8 @@ title: 'Configurar regla de Divergencia de precios'
 id: 4rGMP9mEVOKCZCM71yzxnj
 status: PUBLISHED
 createdAt: 2022-01-05T16:09:05.484Z
-updatedAt: 2022-01-05T16:18:18.655Z
-publishedAt: 2022-01-05T16:18:18.655Z
+updatedAt: 2023-08-11T18:26:09.918Z
+publishedAt: 2023-08-11T18:26:09.918Z
 firstPublishedAt: 2022-01-05T16:11:57.454Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md b/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md
index 2bea1ed14..0f9d5585f 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Configurar regla de Divergencia de precios'
 id: 1ivH7sJoS771wZFMkaFdpt
 status: PUBLISHED
 createdAt: 2022-01-05T16:18:22.558Z
-updatedAt: 2022-01-05T16:22:48.459Z
-publishedAt: 2022-01-05T16:22:48.459Z
+updatedAt: 2024-03-27T20:43:18.424Z
+publishedAt: 2024-03-27T20:43:18.424Z
 firstPublishedAt: 2022-01-05T16:22:48.459Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,7 +16,7 @@ trackSlugES: configurar-integracion-con-mercado-libre
 
 Cuando se utiliza una integración con _marketplaces_ como Mercado Libre, a veces se produce una variación entre el precio fijado por el vendedor y el ofrecido por el _marketplace_, lo que resulta en pedidos con valores diferentes a los esperados. Esto puede resultar en pedidos con errores de divergencia de precios.
 
-En el Admin VTEX, en **PEDIDOS > Gestión de pedidos > Autorización de pedidos**, la [regla de Divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite controlar los pedidos con divergencia de valores. Solo usuarios con los [roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) o OMS Full pueden configurar esta funcionalidad, siguiendo las instrucciones descritas en [Configuración de regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
+En el Admin VTEX, en **Configuración de la tienda > Pedidos > Autorización de pedidos**, la [regla de Divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite controlar los pedidos con divergencia de valores. Solo usuarios con los [roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) o OMS Full pueden configurar esta funcionalidad, siguiendo las instrucciones descritas en [Configuración de regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
 La regla de Divergencia de precios se compone de una o varias reglas de autorización de pedidos, cada una de las cuales corresponde a un intervalo porcentual del precio del pedido. Las reglas de autorización se pueden configurar para negar automáticamente, autorizar automáticamente o exigir la autorización manual del pedido.
 
@@ -24,4 +24,4 @@ La regla de Divergencia de precios se compone de una o varias reglas de autoriza
 Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Mercado Libre.
 </div> 
 
-Se recomienda configurar la regla de Divergencia de precios antes de avanzar al siguiente paso de configuración de la integración con Mercado Libre. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios. Puedes seguirlos en tu Admin VTEX, en **MARKETPLACE > Integraciones > Pedidos**.
+Se recomienda configurar la regla de Divergencia de precios antes de avanzar al siguiente paso de configuración de la integración con Mercado Libre. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios. Puedes seguirlos en tu Admin VTEX, en **Marketplace > Conexiones > Pedidos**.
diff --git a/docs/tracks/es/configuring-price-divergence-rule-via.md b/docs/tracks/es/configuring-price-divergence-rule-via.md
index 297eb59dd..cbe9f2fb5 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-via.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-via.md
@@ -3,8 +3,8 @@ title: 'Configurar regla de Divergencia de precios'
 id: 6MeJhODLMCnYwUCe18QjzP
 status: PUBLISHED
 createdAt: 2022-01-05T16:01:03.231Z
-updatedAt: 2022-01-05T16:04:18.518Z
-publishedAt: 2022-01-05T16:04:18.518Z
+updatedAt: 2023-11-30T21:12:36.109Z
+publishedAt: 2023-11-30T21:12:36.109Z
 firstPublishedAt: 2022-01-05T16:04:18.518Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/configuring-rappi-price-divergence-rule.md b/docs/tracks/es/configuring-rappi-price-divergence-rule.md
new file mode 100644
index 000000000..86dcf41b9
--- /dev/null
+++ b/docs/tracks/es/configuring-rappi-price-divergence-rule.md
@@ -0,0 +1,18 @@
+---
+title: 'Configurar rappi regla de Divergencia de precios '
+id: VoIvBSldeT2A4MuRVMMi1
+status: PUBLISHED
+createdAt: 2024-05-31T20:36:17.323Z
+updatedAt: 2024-05-31T20:51:50.382Z
+publishedAt: 2024-05-31T20:51:50.382Z
+firstPublishedAt: 2024-05-31T20:51:50.382Z
+contentType: trackArticle
+productTeam: Channels
+slug: configurar-rappi-regla-de-divergencia-de-precios
+locale: es
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugES: integracion-de-rappi
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/configuring-redirect.md b/docs/tracks/es/configuring-redirect.md
index 49cdf3ca6..e5f363e84 100644
--- a/docs/tracks/es/configuring-redirect.md
+++ b/docs/tracks/es/configuring-redirect.md
@@ -3,8 +3,8 @@ title: 'Configurar Redireccionamientos'
 id: 4Gd2wLQFbCwTsh8RUDwSoL
 status: PUBLISHED
 createdAt: 2019-11-22T23:40:25.940Z
-updatedAt: 2023-03-30T19:34:08.021Z
-publishedAt: 2023-03-30T19:34:08.021Z
+updatedAt: 2024-06-17T12:20:22.176Z
+publishedAt: 2024-06-17T12:20:22.176Z
 firstPublishedAt: 2019-11-25T17:36:44.905Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -26,7 +26,7 @@ Para configurar un redireccionamiento, es necesario seguir los siguientes pasos:
 
 Debes rellenar los siguientes campos:
 
-![redirecionamentos-adminv4-ES](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
+![redirecionamentos-adminv4-ES](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
 
 ### Informaciones generales
 
@@ -34,6 +34,7 @@ Esta sección proporciona las siguientes informaciones generales sobre el redire
 
 - **Nombre**: nombre del conjunto de reglas del redireccionamiento creado.
 - **URL de redireccionamiento**: URL de destino al cual el cliente será dirigido. Debe ser registrado de forma absoluta - dirección completa - y no relativa. Ejemplo: `https://www.tienda.com/_secure/account/#/orders` en vez de `_secure/account/#/orders`.
+- **Idiomas:** idiomas en los que se aplicará el redireccionamiento. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 
 ### Reglas de activación
 
diff --git a/docs/tracks/es/configuring-ship-from-store.md b/docs/tracks/es/configuring-ship-from-store.md
index 462f3b277..599416280 100644
--- a/docs/tracks/es/configuring-ship-from-store.md
+++ b/docs/tracks/es/configuring-ship-from-store.md
@@ -3,8 +3,8 @@ title: 'Ship From Store'
 id: 50GAmxxFsJoLWqcnMysWdl
 status: PUBLISHED
 createdAt: 2020-06-30T21:36:43.926Z
-updatedAt: 2023-05-31T14:45:10.189Z
-publishedAt: 2023-05-31T14:45:10.189Z
+updatedAt: 2023-07-26T18:44:48.356Z
+publishedAt: 2023-07-26T18:44:48.356Z
 firstPublishedAt: 2020-06-30T21:45:36.187Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugES: estrategias-de-comercio-unificado
 
 La estrategia de **Ship From Store** se produce cuando el cliente desea recibir los productos en su casa y estos productos provienen del almacén de una tienda física. En otras palabras, en este escenario, la tienda funciona como un mini centro de distribución.
 
-![35. Setting up Shipping From Store - 1](https://images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
+![35. Setting up Shipping From Store - 1](//images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
 
 Este tipo de logística ayuda a su operación a reducir costos y tiempo de envío. Esto se debe a que, en lugar de tener solo los almacenes principales, generalmente lejos de las áreas centrales de las ciudades, ahora usted tiene una red de entrega más capilar.
 
@@ -24,7 +24,7 @@ Considere este ejemplo: un cliente que se encuentra en su casa hace un pedido en
 
 ## Prerrequisitos
 
-En primer lugar, consideremos los requisitos previos que su tienda necesita para asegurarse de comenzar a implementar una estrategia de Ship From Store. Consulte nuestro artículo sobre [Requisitos previos para utilizar inStore](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/1wtAanSRA3g2316dw7bw8u "Requisitos previos para utilizar inStore").
+En primer lugar, consideremos los requisitos previos que su tienda necesita para asegurarse de comenzar a implementar una estrategia de Ship From Store. Consulte nuestro artículo sobre [Requisitos previos para utilizar VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/1wtAanSRA3g2316dw7bw8u "Requisitos previos para utilizar VTEX Sales App").
 
 ## Cómo implementar el Ship From Store
 
diff --git a/docs/tracks/es/configuring-synonyms.md b/docs/tracks/es/configuring-synonyms.md
index 021e7f6b2..f598acc96 100644
--- a/docs/tracks/es/configuring-synonyms.md
+++ b/docs/tracks/es/configuring-synonyms.md
@@ -3,8 +3,8 @@ title: 'Configurar Sinónimos'
 id: 3ExbC3QKNF4zH7Gs8jD1cL
 status: PUBLISHED
 createdAt: 2019-11-29T12:04:33.557Z
-updatedAt: 2023-03-30T19:19:37.658Z
-publishedAt: 2023-03-30T19:19:37.658Z
+updatedAt: 2024-01-30T22:46:15.605Z
+publishedAt: 2024-01-30T22:46:15.605Z
 firstPublishedAt: 2020-03-05T19:56:02.826Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,8 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
+<div class = "alert alert-info"> Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ">Sinónimos</a> en lugar de <a href="https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palabras sustitutas</a> para asociar palabras con productos, ya que los sinónimos permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>. </div>
+
 Hay dos formas de configurar sinónimos en VTEX Admin: [individualmente](#crear-sinonimos-individualmente) o [importando una hoja de cálculo en formato CSV](#). Si necesita registrar sinónimos en bloque, le recomendamos que utilice la hoja de cálculo. Consulte las instrucciones para cada método de configuración en las secciones siguientes.
 
 La configuración de sinónimos funciona de forma recursiva. Esto significa que cuando agrega un segundo sinónimo a uno existente, también se convertirá en sinónimo del primero.
@@ -33,6 +35,7 @@ Siga el proceso paso a paso para configurar sinónimos individualmente en VTEX A
 3. Rellene los campos referentes al sinónimo:
    - __Tipo:__ define el tipo de sinónimo. Consulte [Tipos de sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) para obtener más información.
    - __Términos:__ palabras o expresiones que se definirán como sinónimos. Debe pulsar `Enter` después de cada término para insertar otro término.
+   - **Idiomas:** idiomas en los que se aplicará el sinónimo. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
    - __Status:__ define si el sinónimo estará activo o inactivo.
 4. Para terminar, haga clic en `Publicar`.
 
@@ -44,9 +47,22 @@ La alteración puede tardar hasta dos horas en aplicarse.
 
 ## Importar CSV
 
-Si existen muchos sinónimos para registrar, puedes hacer un archivo .csv y luego importarlo en el Admin. El fichero debe contener el siguiente formato, según los [tipos de sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) elegidos:
+Si existen muchos sinónimos para registrar, puedes hacer un archivo .csv y luego importarlo en el Admin.
+
+Para importar la hoja de cálculo, siga los pasos que se indican a continuación:
+
+1. Cree un archivo CSV en el formato indicado en [Plantilla de sinónimos](#plantilla-de-sinonimos).
+2. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
+3. En **Intelligent Search**, haga clic en __Sinónimos__. 
+4. Haga clic en <i class="fas fa-download"></i> `Importar`.
+5. Arrastre el archivo CSV al área delimitada o haga clic en `selecciona un archivo` para seleccionar el archivo de su dispositivo.
+6. Haga clic en `Importar`.
 
-- __Unidireccional:__ `{términos separados por una coma};{términos expandidos separados por una coma};{status}`
+## Plantilla de sinónimos
+
+El fichero debe contener el siguiente formato, según los [tipos de sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) elegidos:
+
+- __Unidireccional:__ `{términos separados por una coma};{término equivalente};{status}`
 
    __Ejemplos:__
 
@@ -60,8 +76,21 @@ Si existen muchos sinónimos para registrar, puedes hacer un archivo .csv y lueg
     - `tv,televisión,televisor;true`: al buscar por cualquiera de los términos, el producto que contenga uno de estos será devuelto.
     - `monitor,pantalla,display;true`: al buscar por cualquiera de los términos, el producto que contenga uno de estos será devuelto.
 
-Para importar la hoja de cálculo, siga los pasos que se indican a continuación:
+#### Tiendas multidioma (Beta)
+
+Tiendas que utilizan configuración multidioma (beta) deben seguir la siguiente plantilla para importar Sinónimos para idiomas específicos.
+
+- __Unidireccional__: `{términos separados por una coma};{término equivalente};{status};{locales separados por coma}`.
+
+   __Ejemplo:__
+   - `smartphone;iphone;true;en-GB`: al buscar smartphone en la tienda en el idioma inglés (`locale en-GB`), se mostrará los resultados de iphone.  Sin embargo, al buscar iphone, no aparecerán los resultados de smartphone.
+
+- __Bidireccional__: `{términos separados por una coma};{status};{locales separados por coma}`.
+
+   __Ejemplo:__
+   - `tv,smart tv;true;en-GB`: al buscar cualquiera de estos términos en la tienda en el idioma inglés (`locale en-GB`), se mostrará cualquier producto que contenga uno de esos términos en los resultados de búsqueda.
+
+<div class="alert alert-warning">
+  <p> Si el archivo .csv importado no contiene el <code>locale</code>, el sinónimo será válido para todos los idiomas disponibles en la tienda. </p>
+</div>
 
-1. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
-2. En **Intelligent Search**, haga clic en __Sinónimos__. 
-3. Haga clic en "Importar".
diff --git a/docs/tracks/es/configuring-the-amazon-integration.md b/docs/tracks/es/configuring-the-amazon-integration.md
index c9d3fd016..212ab029a 100644
--- a/docs/tracks/es/configuring-the-amazon-integration.md
+++ b/docs/tracks/es/configuring-the-amazon-integration.md
@@ -3,8 +3,8 @@ title: 'Configurar la integración de Amazon'
 id: 5J9CWPIbYQdAegJJWGsxan
 status: PUBLISHED
 createdAt: 2019-02-28T23:11:28.346Z
-updatedAt: 2022-02-03T23:25:36.883Z
-publishedAt: 2022-02-03T23:25:36.883Z
+updatedAt: 2023-09-22T20:17:01.064Z
+publishedAt: 2023-09-22T20:17:01.064Z
 firstPublishedAt: 2019-02-28T23:12:37.347Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/configuring-the-connector-b2w.md b/docs/tracks/es/configuring-the-connector-b2w.md
index 0af49f3ae..9cb1d490e 100644
--- a/docs/tracks/es/configuring-the-connector-b2w.md
+++ b/docs/tracks/es/configuring-the-connector-b2w.md
@@ -3,8 +3,8 @@ title: 'Configuración del conector'
 id: 40eYElt1qwIqGeIeum2W4M
 status: PUBLISHED
 createdAt: 2018-09-27T22:25:49.315Z
-updatedAt: 2022-09-06T22:53:13.914Z
-publishedAt: 2022-09-06T22:53:13.914Z
+updatedAt: 2024-07-02T19:23:01.065Z
+publishedAt: 2024-07-02T19:23:01.065Z
 firstPublishedAt: 2018-09-27T22:41:30.135Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/configuring-the-connector.md b/docs/tracks/es/configuring-the-connector.md
index 523bcca42..5f9b0a974 100644
--- a/docs/tracks/es/configuring-the-connector.md
+++ b/docs/tracks/es/configuring-the-connector.md
@@ -3,8 +3,8 @@ title: 'Configuración del conector'
 id: wWyl0Njxgs5KfXvxYZJrl
 status: PUBLISHED
 createdAt: 2021-04-14T21:01:49.270Z
-updatedAt: 2021-04-15T21:19:06.543Z
-publishedAt: 2021-04-15T21:19:06.543Z
+updatedAt: 2023-10-13T19:52:02.877Z
+publishedAt: 2023-10-13T19:52:02.877Z
 firstPublishedAt: 2021-04-15T17:41:17.442Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,17 +16,17 @@ trackSlugES: integracion-con-google-shopping
 
 La configuración de la integración con Google Shopping se realiza en el Admin. Para completarla, siga las instrucciones a continuación:
 
-1. Acceda al Admin.
-2. En el módulo _Marketplace_, haga clic en `Integraciones`. 
-3. Haga clic en `Configuración`.
-4. En la card de Google Shopping, haga clic en `Integrar`.
-5. Rellene los campos que aparecen en la pantalla según se describe a continuación y después haga clic en `Guardar configuración` (los campos marcados con el símbolo * son obligatorios).
+1. Accede al Admin VTEX.
+2. En el módulo Marketplace, haz clic en __Marketplace e integraciones__.
+3.  Ingresa __Google Shopping__ en el campo Buscar marketplace por nombre o nombre de cuenta y haz clic en `Conectar`.
+4. Lee la información contenida en la ventana emergente, rellena los campos que aparecen en la pantalla según se describe a continuación y después, en la parte superior derecha de la pantalla, haz clic en `Conectar`. (Los campos marcados con el símbolo * son obligatorios).
 
 - **Integración*:** solamente se habilitará la integración si marca _sí_.
 - **Ignorar el envío de EAN (GTIN):** la opción _sí_ significa que se enviarán los SKU sin código de barras. Si su producto tiene un código de barras, se recomienda marcar _no_ para así incluir esta información en la integración. Puede consultar el artículo [Registrar el campo EAN](https://help.vtex.com/es/tutorial/cadastrar-o-codigo-de-barra-dos-skus-para-o-instore--2jkOdRB4XSMG2ke0uUQIKS#registrar-el-campo-ean).
 - **Merchant Id*:** código atribuido a su perfil de Google Merchant Center (secuencia numérica que aparece en la parte superior derecha de la pantalla cuando accede a su cuenta).
 - **Políticas comerciales*:** número de la política comercial que definirá el surtido del catálogo y los valores de los ítems utilizados en la integración.
 - **Email de Google Merchant*:** _email_ utilizado para crear la cuenta de Google Merchant Center.
+- **Aplicar descuento en el precio enviado*:** aquí el seller debe elegir qué tipo de descuento desea enviar a Google Shopping. Puede seleccionar __No aplicar__ (envía el precio registrado en la plataforma VTEX), __Para medio de pago configurado en la API de Checkout__ (debe seleccionarse si el seller tiene el descuento configurado) o __Mayor descuento configurado__.  
 - **Eliminar SKU sin stock*:** al hacer clic en _no_, cuando un producto no esté disponible, no desaparecerá de su _feed_ de Google Shopping, solo aparecerá con el estado _indisponible_. Si hace clic en _sí_, el SKU que haya sido retirado temporalmente por falta de _stock_ volverá a aparecer en el _feed_ cuando se reabastezca el _stock_.
 - **Merchant Id (Multi-Client):** solo debe utilizarse este campo cuando se configure una cuenta avanzada en Google Merchant Center. El propósito de crear una cuenta avanzada es gestionar varios vendedores y dominios a gran escala. En estos casos, debe rellenar el campo con el código atribuido a su cuenta avanzada en Google Merchant Center, que se puede identificar de la misma forma que el Merchant Id (secuencia numérica localizada en la parte superior derecha de la pantalla). Puede ver más detalles en el artículo de Google [Convertir una cuenta de varios clientes](https://support.google.com/merchants/answer/188487).
 - **Enviar precio*:** hay dos opciones: _Sin multiplicador de unidades_, con la cual el producto aparecerá con el valor unitario, y _Con multiplicador de unidades_, cuando el cobro de su producto tiene algún tipo de medidor.
diff --git a/docs/tracks/es/configuring-the-integration-rappi.md b/docs/tracks/es/configuring-the-integration-rappi.md
new file mode 100644
index 000000000..323038e9c
--- /dev/null
+++ b/docs/tracks/es/configuring-the-integration-rappi.md
@@ -0,0 +1,18 @@
+---
+title: 'Configuración de la integración'
+id: 1SowuK4iQngOHebFMfizYY
+status: PUBLISHED
+createdAt: 2024-05-31T20:32:15.901Z
+updatedAt: 2024-05-31T20:51:41.392Z
+publishedAt: 2024-05-31T20:51:41.392Z
+firstPublishedAt: 2024-05-31T20:51:41.392Z
+contentType: trackArticle
+productTeam: Channels
+slug: configuracion-de-la-integracion-rappi
+locale: es
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugES: integracion-de-rappi
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index c12c92162..e8025111b 100644
--- a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -3,8 +3,8 @@ title: 'Configurar la integración con FBE en el Admin VTEX'
 id: jUtgjBDumr5oGWIU7mVLC
 status: PUBLISHED
 createdAt: 2021-09-30T16:07:29.101Z
-updatedAt: 2021-10-05T21:36:44.675Z
-publishedAt: 2021-10-05T21:36:44.675Z
+updatedAt: 2024-04-17T14:57:04.600Z
+publishedAt: 2024-04-17T14:57:04.600Z
 firstPublishedAt: 2021-09-30T18:49:18.739Z
 contentType: trackArticle
 productTeam: Channels
@@ -40,7 +40,7 @@ Para que la integración funcione correctamente, se recomienda conceder todos lo
 10. Haz clic en `Siguiente`.
 11. En la ventana abierta, aparecerá una confirmación de que la integración se ha realizado. Haz clic en `Listo`.
 
-![gif_es_v1](https://drive.google.com/uc?export=download&id=1KvwcMkIeX3_UzsnN5lIZzWysbyo8djLS)
+![gif es v1](//images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/aad4d60cb7baecae018ef1d38d25acef/gif_es_v1.gif)
 
 ## Envío de datos de productos a Facebook Business Extension
 
diff --git a/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index ea164dcf9..497c7a1b5 100644
--- a/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -80,7 +80,7 @@ Después de rellenar el formulario de configuración de la integración, debes c
 
 En la página **Set up TikTok for Business** (Configurar TikTok for Business), que se muestra abajo, debes seguir las instrucciones de configuración que se describen a continuación.
 
-![set-up-tiktok-for-business](https://images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
+![set-up-tiktok-for-business](//images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
 
 1. Haz clic en la sección **TikTok for Business Account** y verifica que tu cuenta esté en la lista.
     * Si quieres conectar otra cuenta, haz clic en `Disconnect` y repite el paso de inicio de sesión que se describe en [Conectar con la cuenta de TikTok](#2-conectar-con-la-cuenta-de-tiktok).
diff --git a/docs/tracks/es/configuring-the-integration.md b/docs/tracks/es/configuring-the-integration.md
new file mode 100644
index 000000000..327053601
--- /dev/null
+++ b/docs/tracks/es/configuring-the-integration.md
@@ -0,0 +1,18 @@
+---
+title: 'Configuración de la integración'
+id: HgIbZEzbPr8FQid5MXURQ
+status: PUBLISHED
+createdAt: 2023-08-10T22:33:03.150Z
+updatedAt: 2024-07-26T18:36:22.560Z
+publishedAt: 2024-07-26T18:36:22.560Z
+firstPublishedAt: 2023-08-11T01:56:55.389Z
+contentType: trackArticle
+productTeam: Channels
+slug: configuracion-de-la-integracion
+locale: es
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugES: integracion-de-livelo
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/configuring-the-relevance-feature.md b/docs/tracks/es/configuring-the-relevance-feature.md
index 68dd4ba5e..425921182 100644
--- a/docs/tracks/es/configuring-the-relevance-feature.md
+++ b/docs/tracks/es/configuring-the-relevance-feature.md
@@ -34,7 +34,7 @@ Hay dos áreas para configurar esta funcionalidad: __Criterios de prioridad__ y
   <li><b>Score del catálogo:</b> 3</li>
 </ul>
 
-![default priority criteria ES](https://images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/a87d76864944720f3e33c55d0275ada1/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_33.png)
+![default priority criteria ES](//images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/a87d76864944720f3e33c55d0275ada1/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_33.png)
 
 Para cambiar la configuración de relevancia, realice los siguientes pasos.
 
@@ -42,7 +42,7 @@ Para cambiar la configuración de relevancia, realice los siguientes pasos.
 2. Haga clic en __Configuración de relevancia__.
 3. Elija el criterio cuyo peso desea cambiar.
 4. Arrastre el control deslizante hasta el número deseado utilizando el cursor como se muestra en la imagen siguiente.
-  ![composicao-criterios-es](https://images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/1753fa46745b8fb9468f1c8adeb47aba/composicao-criterios-es.gif)
+  ![composicao-criterios-es](//images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/1753fa46745b8fb9468f1c8adeb47aba/composicao-criterios-es.gif)
   Si quiere cambiar la posición de un criterio de __Composición de criterios__ a __Criterios de prioridad__, simplemente arrástrelo por el ícono <i class="fas fa-bars"></i> a la zona superior, como se muestra a continuación. Tenga en cuenta que cuando el criterio se convierte en prioritario, ya no es posible cambiar su peso.
-  ![criterios-prioridad-es](https://images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/59e0ec635987e5d8a11aa1e45f296f68/criterios-prioridad-es.gif)
+  ![criterios-prioridad-es](//images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/59e0ec635987e5d8a11aa1e45f296f68/criterios-prioridad-es.gif)
 5. Para terminar, haga clic en __Guardar__.
diff --git a/docs/tracks/es/contract-termination.md b/docs/tracks/es/contract-termination.md
new file mode 100644
index 000000000..683d05818
--- /dev/null
+++ b/docs/tracks/es/contract-termination.md
@@ -0,0 +1,22 @@
+---
+title: 'Rescisión de contrato'
+id: 3TUpFItxp8L1WZAD1JuYfF
+status: PUBLISHED
+createdAt: 2024-02-20T21:47:12.450Z
+updatedAt: 2024-02-22T14:08:21.680Z
+publishedAt: 2024-02-22T14:08:21.680Z
+firstPublishedAt: 2024-02-22T14:08:21.680Z
+contentType: trackArticle
+productTeam: Others
+slug: rescision-de-contrato
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+VTEX lamenta la marcha de un cliente y comprende que las necesidades y circunstancias de los partners comerciales pueden cambiar. A pesar de sentir la decisión de rescindir el contrato, VTEX se compromete a que este proceso sea lo más sencillo y transparente posible para garantizar una transición fluida.
+
+Para rescindir tu contrato con VTEX debes ponerte en contacto con el [soporte financiero](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#financiero). Para Brasil, Argentina y Colombia, sigue las directrices de los artículos a continuación:
+
+- [Solicitar rescisión contractual en Brasil](https://help.vtex.com/pt/tutorial/como-solicitar-sua-rescisao-contratual-no-brasil--frequentlyAskedQuestions_1834)
+- [Solicitar rescisión contractual en Argentina y Colombia](https://help.vtex.com/es/tutorial/solicitar-rescisao-contratual-na-argentina-e-colombia--33g6mUoYB9Mf04C06gSU0a)
diff --git a/docs/tracks/es/corporate-digital-account.md b/docs/tracks/es/corporate-digital-account.md
index a4124b588..0f7fa17bf 100644
--- a/docs/tracks/es/corporate-digital-account.md
+++ b/docs/tracks/es/corporate-digital-account.md
@@ -1,10 +1,10 @@
 ---
 title: 'Cuenta digital corporativa '
 id: 3MVAuZJenHAEt8jsgX99GD
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T17:37:52.588Z
-updatedAt: 2023-03-14T22:07:22.796Z
-publishedAt: 2023-03-14T22:07:22.796Z
+updatedAt: 2023-10-05T14:13:52.213Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:48:20.683Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/es/create-brands.md b/docs/tracks/es/create-brands.md
index 222a5eeba..a80b3edda 100644
--- a/docs/tracks/es/create-brands.md
+++ b/docs/tracks/es/create-brands.md
@@ -39,7 +39,7 @@ Las informaciones rellenadas en el registro se pueden actualizar en cualquier mo
 
 Para eliminar el registro de alguna marca, debe hacer clic en la flecha al lado de `Editar` y seleccionar la opción `Eliminar`.
 
-![editar-marca es](https://images.ctfassets.net/alneenqid6w5/1klwWT7dVmC63Az7KqX4hI/5fb442a9f0f4c3b566b61899ad17eb3c/editar-marca_ES.png)
+![editar-marca es](//images.ctfassets.net/alneenqid6w5/1klwWT7dVmC63Az7KqX4hI/5fb442a9f0f4c3b566b61899ad17eb3c/editar-marca_ES.png)
 
 ## API
 
diff --git a/docs/tracks/es/creating-accounts.md b/docs/tracks/es/creating-accounts.md
index d9f546c92..1a43f9380 100644
--- a/docs/tracks/es/creating-accounts.md
+++ b/docs/tracks/es/creating-accounts.md
@@ -1,10 +1,10 @@
 ---
-title: 'Crear cuentas en Customer Credit'
+title: ' Creación de cuentas en Customer Credit'
 id: 7FHLd0cmxqqGeEUuc8uioU
 status: PUBLISHED
 createdAt: 2018-11-06T20:24:28.924Z
-updatedAt: 2023-05-12T12:20:09.076Z
-publishedAt: 2023-05-12T12:20:09.076Z
+updatedAt: 2024-02-08T19:08:32.443Z
+publishedAt: 2024-02-08T19:08:32.443Z
 firstPublishedAt: 2018-11-06T21:15:02.053Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,106 +14,82 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugES: customer-credit-como-empezar
 ---
 
-El siguiente paso es crear las cuentas de los clientes a los que desea ofrecer crédito en su tienda. 
+El siguiente paso es crear cuentas para los clientes a los que desea ofrecer crédito en su tienda. Las cuentas se pueden crear de tres maneras diferentes:
 
-Hay tres formas de crearlas:
-
-- Vía Admin.
-- Por el recurso de importación masiva.  
-- Vía API.
+- [Cuenta individual (Admin VTEX)](#crear-cuentas-individualmente)
+- [Múltiples cuentas masivas (Admin VTEX)](#crear-varias-cuentas-importacion-masiva)
+- [Cuenta individual (Customer Credit API)](#crear-cuenta-a-traves-de-api)
 
 <div class="alert alert-info">
-<strong>Atención</strong>: Las cuentas de Customer Credit no están integradas con la base de clientes registrada en las entidades del Master Data. Las cuentas deben crearse en la propia aplicación antes o después de que el usuario haya cerrado las compras en la tienda.
+Las cuentas creadas en la aplicación Customer Credit no tienen relación ni comparten datos con la base de clientes registrada en <a href="https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-datos">entidades de Master Data</a> de la tienda. Para que un cliente pueda utilizar Customer Credit como método de pago, el comerciante debe registrar su cuenta en la aplicación, incluso si el cliente ya tiene una cuenta en la tienda. 
 </div>
 
-Además, en todos los casos en que el usuario opte por actualizar datos mediante la importación de una plantilla en el sistema, es necesario asegurarse de que todos los valores estén separados por una coma. De lo contrario, la operación no se completará correctamente.
-
-Dicho esto, verifique los detalles de cómo crear una cuenta por medio de cada una de las formas.
-
-## Creación de cuentas individualmente
-Si lo prefiere, puede crear varias cuentas manualmente a través del Admin.
-
-Verifique el procedimiento:
+## Crear cuentas individualmente
 
-1. Accede al __Admin__.
-2. Haga clic en el módulo __Customer Credit__.
-3. Luego, haga clic en __Cuentas__.
-4. En el lado derecho de la pantalla, haga clic en el botón azul __"Nuevo"__.
-5. Seleccione el __tipo de documento__ que identificará la cuenta.
-6. Introduzca el número de documento en el campo __Documento__.
-7. Rellene el campo __E-mail__.
-8. Establezca el __límite de crédito__ disponible para la cuenta.
-9. Haga clic en el botón azul __Confirmar__.
+Para registrar un nuevo cliente en Customer Credit, siga los pasos a continuación:
 
-El llenado del campo de email en el formulario es obligatorio, ya que a través del email (clave de acceso al sistema VTEX), es posible autenticar el acceso del cliente a los límites de crédito de una cuenta. Para obtener más información sobre la protección de datos, visite [Seguridad de SmartCheckout](https://help.vtex.com/es/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB#).
+1. En el Admin VTEX, accede a __Apps > Customer Credit > Cuentas__, o escribe __Cuentas__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla __Cuentas__, haga clic en el botón "NUEVA".
+3. En __Identificación__, seleccione el __Tipo de documento__ y complete los campos __Documento__ y __Email__ con la información del cliente que desea registrar.
+4. En __Crédito__, ingrese los valores de __Límite de crédito (BRL)__ y __Tolerancia__ que desea poner a disposición del cliente.
+5. Haga clic en `Confirmar`.
 
-De esta manera, la nueva cuenta se mostrará en la página de inicio de la sección "Cuentas".
-
-## Crear cuentas a través de la importación masiva
-
-Para la creación de cuentas de forma masiva, puede utilizar el recurso de importación de archivo CSV (Comma Separated Value) - un formato de plantilla. 
-
-Esta funcionalidad es muy útil ya que permite importar miles de cuentas al sistema a la vez.
+<div class="alert alert-warning">
+El llenado del campo <b>Email</b> es obligatorio, ya que la plataforma VTEX utiliza esta información para autentificar el acceso del cliente a los límites de crédito de su cuenta. Para obtener más información sobre protección de datos, visite <a href="https://help.vtex.com/es/tutorial/seguridad-de-smartcheckout--3SrJuuhrqwePUg1rp1exfB">Seguridad de SmartCheckout</a>.
+</div>
 
-1. Acceda al __Admin__.
-2. Haga clic en el módulo __Customer Credit__.
-3. Luego, haga clic en __Cuentas__.
-4. Junto al botón "Nuevo", haga clic en la opción __Importar__.
-5. En el box que aparece en la pantalla, seleccione la opción __Crear__.
-6. Haga clic en el botón azul __"Continuar"__.
-7. Luego, haga clic en la opción __Descargar plantilla__.
+A partir de este momento, la nueva cuenta creada se mostrará en la pantalla __Cuentas__.
 
-De este modo, en su computadora se guardará un modelo de plantilla en formato CSV. Puede encontrarlo en la carpeta de Descargas.
+![CC_nueva_cuenta_1_ES](//images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/137feed49de06cbae706252e4d6ef813/CC_nueva_cuenta_1_ES.JPG)
 
-El siguiente paso es rellenar las columnas del documento con la información de cada una de las cuentas que desea crear.
+## Crear varias cuentas (importación masiva)
 
-En total, la tabla tiene 13 columnas que pueden rellenarse. Sin embargo, la única  obligatoria es la del correo electrónico, información utilizada por el sistema VTEX para identificar al usuario en SmartCheckout.
+Para crear varias cuentas al mismo tiempo (en masa) en Customer Credit, puede utilizar una plantilla en formato CSV (Comma Separated Value) que contiene la información de cada cliente. Siga los pasos a continuación para crear varias cuentas:
 
-Cuando haya terminado de rellenar la tabla y de guardar todas las modificaciones que haya hecho, proceda a realizar los siguientes pasos:
+1. En el Admin VTEX, accede a __Apps > Customer Credit > Cuentas__, o escribe __Cuentas__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla __Cuentas__, haga clic en el botón `IMPORTAR`.
+3. En __¿Quieres crear o actualizar cuentas?__, selecciona la opción __Crear__ y haz clic en `CONTINUAR`.
+4. Haga clic en `DESCARGAR PLANTILLA`. Se enviará una plantilla en formato .csv a su dispositivo (computadora, teléfono celular o tableta).
+5. Complete cada línea:
+<br>
+<ul>
+  <li>Columnas <b>Email</b>, <b>Document</b> y <b>Document Type</b>: información al cliente.</li>
+  <li>Columnas <b>Credit limit</b> y <b>Tolerance rate</b>: valores disponibles para cada cliente. La <b>tasa de tolerancia</b> debe ingresarse en formato decimal, por ejemplo, una tolerancia del 5% debe indicarse como 0,05.</li>
+</ul>
 
-1. Vuelva a la sección de __Cuentas__ en el Admin.
-2. De nuevo, haga clic en la opción __Importar__.
-3. Esta vez, seleccione la opción __Actualizar__ en el box.
-4. Haga clic en el botón azul __"Continuar"__
-5. Cargue la plantilla en el espacio __"Suelte aquí su CSV o elija un archivo"__.
-6. Haga clic en el botón __Importar archivo__.
+![CC_criar_conta_2_ALL](//images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
 
-¡Listo! Sus cuentas se crearán y se mostrarán en la página de inicio de la sección Cuentas.
+<blockquote><ui>6. Guardar la plantilla .csv.</ui>
 
-En el contexto de la creación de nuevas cuentas, puede consultar todo su historial de importación. Para esto, simplemente haga clic en "Historial de importación" en la página principal de la sección Cuentas. 
+<blockquote><ui>7. Regrese a la pantalla <b>Cuentas</b> y haga clic en el botón <b>IMPORTAR</b> nuevamente.</ui>
 
-De esta manera, también se puede comprobar si las importaciones se hicieron de la manera correcta. De lo contrario, se indicará en la interfaz las correcciones necesarias.
+<blockquote><ui>8. En <b>¿Quieres crear o actualizar cuentas?</b>, selecciona la opción <b>Actualizar</b> y haz clic en <b>CONTINUAR</b>.</ui>
 
-### Actualizar cuentas a través de la importación masiva
+<blockquote><ui>9. Inserta o selecciona la plantilla .csv en el espacio <b>Suelta áqui tu archivo CSV o elige uno</b>.</ui>
 
-Además, también puede actualizar los datos  - correo electrónico, límite de crédito, documento, tipo de documento, status y tolerancia - de todas sus cuentas a la vez mediante la función de importación masiva.
+<blockquote><ui>10. Haga clic en el botón <b>IMPORTAR ARCHIVO</b>.</ui>
 
-El proceso es similar a la creación de cuentas. Sin embargo, aquí se considera que ya tiene el modelo del archivo CSV descargado en su máquina.
+A partir de este momento, las nuevas cuentas creadas mediante la plantilla .csv estarán disponibles en la pantalla __Cuentas__.
 
-Verifique el procedimiento:
+<div class="alert alert-warning">
+También es posible rastrear procesos anteriores de creación de múltiples cuentas, identificando si las cuentas se crearon correctamente. Para comprobar esta información, haga clic en <b>Historial de importación</b> en la pantalla <b>Cuentas</b>.
+</div>  
 
-1. Acceda al __Admin__.
-2. Haga clic en el módulo __Customer Credit__.
-3. Luego, haga clic en __Cuentas__.
-4. Junto al botón "Nuevo", haga clic en la opción __Importar__.
-5. En el box que aparece en la pantalla, seleccione la opción __Actualizar__.
-6. Haga clic en el botón azul __Continuar__.
-7. Luego, cargue el archivo __CSV actualizado__ en el área de *Drop Zone*.
-8. Haga clic en el botón __"Importar archivo"__.
+### Actualizar varias cuentas (importación masiva)
 
-Finalmente, espera a la carga completa de la plantilla.
+Para actualizar información, como documento, tipo de documento, correo electrónico, límite de crédito y tolerancia, en varias cuentas al mismo tiempo, también puede utilizar la función de importación masiva.  
 
-## Crear cuentas a través de API
+El procedimiento es similar a [crear múltiples cuentas](#crear-varias-cuentas-importacion- masiva). Sin embargo, ya debes tener descargada y completada la hoja de cálculo .csv en tu dispositivo (computadora, celular o tableta). Siga los pasos a continuación para actualizar la información del cliente:  
 
-Otra alternativa es crear cuentas a través de APIs por medio de [endpoint](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-accountId- "endpoint") `POST Open or Change Account`.
+1. En el Admin VTEX, accede a __Apps > Customer Credit > Cuentas__, o escribe __Cuentas__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla __Cuentas__, haga clic en el botón `IMPORTAR`.
+3. En __¿Quieres crear o actualizar cuentas?__, selecciona la opción __Actualizar__ y haz clic en `CONTINUAR`.
+4. Inserta o selecciona la plantilla .csv en el espacio __Suelta áqui tu archivo CSV o elige uno__.
+5. Haga clic en el botón __IMPORTAR ARCHIVO__.
+6. Después de cargar la plantilla en Admin, verifique en la pantalla __Cuentas__ si la información se actualizó correctamente en las cuentas de cada cliente.   
 
-Rellene el body con la siguiente información:
+## Crear cuenta a través de API
 
-     {
-      "id": "id",
-      "creditLimit": "number",
-      "document": "CPF or CNPJ or Other",
-      "email": "email"
-    }
+También puede crear cuentas para sus clientes en Customer Credit a través  endpoint [POST - Open an account](https://developers.vtex.com/docs/api-reference/customer-credit-api#post-/api/creditcontrol/accounts).
 
-Para más detalles, consulte nuestra [documentación técnica sobre las APIs de Customer Credit](https://developers.vtex.com/docs/guides/customer-credit-api-overview "documentación técnica sobre las APIs de Customer Credit"). 
+Para obtener más información sobre los endpoints de la API de Customer Credit, acesse [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api#overview).
diff --git a/docs/tracks/es/creating-and-editing-users.md b/docs/tracks/es/creating-and-editing-users.md
index df5a0645b..8dbf81a8f 100644
--- a/docs/tracks/es/creating-and-editing-users.md
+++ b/docs/tracks/es/creating-and-editing-users.md
@@ -3,8 +3,8 @@ title: 'Crear y editar usuario '
 id: 5enE0a0glnI0coEj7rRHBA
 status: PUBLISHED
 createdAt: 2019-11-22T15:16:38.307Z
-updatedAt: 2022-08-24T14:23:48.018Z
-publishedAt: 2022-08-24T14:23:48.018Z
+updatedAt: 2024-06-17T15:10:57.072Z
+publishedAt: 2024-06-17T15:10:57.072Z
 firstPublishedAt: 2020-01-13T14:33:11.563Z
 contentType: trackArticle
 productTeam: Identity
@@ -23,7 +23,7 @@ Es en esta sección donde registramos quién puede acceder al ambiente administr
 1. En el módulo Gestión de la Cuenta, haga clic en la pestaña **Usuarios**.
 2. Haga clic en el botón **Nuevo usuario**.
 3. Complete el **Correo electrónico** y el **Nombre completo**.
-4. Agregue o cree los [roles](https://help.vtex.com/es/tutorial/guia-para-crear-perfiles-de-usuario/) deseados.
+4. Agregue o cree los [roles](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) deseados.
 5. Haga clic en el botón **Guardar**.
 
 El usuario recibirá un correo electrónico confirmando el registro, con un enlace para registrar la contraseña de acceso.
diff --git a/docs/tracks/es/creating-merchandising-rules-visual-editor.md b/docs/tracks/es/creating-merchandising-rules-visual-editor.md
new file mode 100644
index 000000000..8c825d540
--- /dev/null
+++ b/docs/tracks/es/creating-merchandising-rules-visual-editor.md
@@ -0,0 +1,99 @@
+---
+title: 'Crear regla de merchandising - Editor visual'
+id: 2ejly01m1w28RsZlCKowEr
+status: PUBLISHED
+createdAt: 2024-01-29T17:01:20.082Z
+updatedAt: 2024-02-01T13:22:55.562Z
+publishedAt: 2024-02-01T13:22:55.562Z
+firstPublishedAt: 2024-01-29T17:04:11.061Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: crear-regla-de-merchandising-editor-visual
+locale: es
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugES: vtex-intelligent-search
+---
+
+Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) de VTEX Intelligent Search utilizando el [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), sigue los pasos a continuación.
+
+1. En el Admin VTEX, accede a **Storefront**, o ingresa **Storefront **en la barra de búsqueda.
+2. En **Intelligent Search**, haz clic en **Reglas de merchandising**.
+3. Haz clic en el botón `+ Agregar`.
+4. Rellena los siguientes campos:
+
+    * **Nombre de la regla**: nombre de la regla de merchandising. Ejemplo: promocionar el producto A cuando el cliente busque "galletas de chocolate".
+    * **Fecha de inicio (opcional)**: define la fecha a partir de la cual se aplicará la regla de merchandising. La fecha considera la zona horaria UTC-0.
+    * **Fecha de fin (opcional)**: define la fecha en que la regla de merchandising dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
+    * **Aplicar a los idiomas:** idiomas en los que se aplicará la regla de merchandising. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Haz clic en **Editor visual**. Para más información sobre cada editor, consulta [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
+6. Haz clic en `Siguiente`.
+7. Define al menos un término de búsqueda o filtro para aplicar la regla de merchandising:
+
+    * Para definir un término de búsqueda, ingresa el término en la barra de búsqueda (ítem **II** de la sección [Acciones disponibles en el Editor visual](https://docs.google.com/document/d/1zUZ_FhSGgJ8b3E0oF-q04sfcaDw6_btr/edit#bookmark=id.2et92p0)).
+    * Si deseas crear un filtro para aplicar la regla de merchandising (ítem **III** de la sección [Acciones disponibles en el Editor visual](https://docs.google.com/document/d/1zUZ_FhSGgJ8b3E0oF-q04sfcaDw6_btr/edit#bookmark=id.2et92p0)), sigue las instrucciones descritas en la sección [Agregar filtros y condiciones](https://help.vtex.com/es/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes).
+8. Si lo deseas, realiza las acciones opcionales que se indican a continuación para personalizar los resultados de la búsqueda.
+    * Definir cantidad de ítems por fila en los resultados de búsqueda.
+    * Definir cantidad de ítems por página en los resultados de búsqueda.
+    * Ocultar producto en los resultados de búsqueda.
+    * Fijar producto, es decir, anclarlo en las primeras posiciones de los resultados de búsqueda.
+    * Arrastrar el producto fijado a la posición deseada en los resultados de búsqueda.
+    * Editar la configuración inicial de la regla de merchandising, que incluye el nombre de la regla, las fechas de inicio y fin y, si la tienda utiliza la [Configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO), los idiomas a los que se aplicará.
+
+      Más información sobre estas acciones en los puntos **4, 5, 6, 8, 9** y **11** de la sección [Acciones disponibles en el Editor visual](#acciones-disponibles-en-el-editor-visual).
+9. Haz clic en `Guardar`.
+
+ <div class="alert alert-info">
+  <p>Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.</p>
+</div>
+
+## Acciones disponibles en el Editor visual
+
+El Editor visual de reglas de merchandising de VTEX Intelligent Search permite realizar las acciones que se ilustran en la imagen siguiente:
+
+![visual-merch-rules-ES-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Editar nombre de la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir los términos de búsqueda para aplicar la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#agregar-filtros-y-condiciones" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a> para aplicar la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir cantidad de ítems por fila en los resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir cantidad de ítems por página en los resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ocultar producto en los resultados de búsqueda. En el Editor visual, los productos ocultos aparecen en gris con el ícono del ojo tachado <i class="far fa-eye-slash"></i>. Para volver a mostrar un producto oculto, pasa el mouse sobre él y haz clic en el ícono del ojo <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ver detalles del producto. La información mostrada es:<br /><br />
+	   <ul>
+		  <li class="t-body c-on-base mb5 lh-copy"><strong>Disponible:</strong> indica si el producto está o no disponible en la tienda.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Clics:</strong> número de clics durante los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Pedidos:</strong> número de pedidos realizados que incluyen el producto en los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Ingresos:</strong> ingresos que generó el producto en los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Fecha de lanzamiento:</strong> fecha de lanzamiento del producto.</li> 
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Promoción:</strong> indica si el producto forma parte o no de una promoción.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Descuento:</strong> descuento aplicado sobre el producto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Variedad de matriz disponible: </strong>representa el porcentaje de SKU disponibles del producto. Por ejemplo, si un producto tiene cinco SKU y solo hay tres disponibles, la variedad de matriz disponible será del 60 %, representada como 0.6 en este campo. Si todos los SKU están disponibles, el valor del campo será 1.</li>
+	   </ul>
+    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Arrastrar producto anclado a la posición deseada en los resultados de búsqueda. Solo pueden arrastrarse productos que hayan sido anclados (acción <strong>IX</strong> de esta lista).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Anclar producto, es decir, situarlo en las primeras posiciones de los resultados de búsqueda. Al anclar el producto A y, a continuación, el producto B, aparecerán en ese orden en los resultados de búsqueda, antes que los demás. Para desanclar un producto, pasa el cursor sobre él y haz clic en el ícono de la tachuela tachada <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar la configuración inicial de la regla de merchandising, que incluye el nombre de la regla, las fechas de inicio y fin y, si la tienda utiliza la <a rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO">Configuración multidioma (beta)</a>, los idiomas a los que se aplicará.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Cancelar edición.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Guardar configuración.</li>
+</ol>
+
+### Agregar filtros y condiciones
+
+El filtro es un atributo seleccionable predefinido que restringe los resultados de la búsqueda, por ejemplo, permite filtrar por todos los productos de una categoría o marca, entre otras condiciones. Puedes agregar una o más condiciones a un filtro, tal como se muestra a continuación.
+
+![filtros-merchrules-es](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
+
+Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
+
+1. Haz clic en `Filtro`.
+2. Haz clic en `Agregar condición`.
+3. Rellena las condiciones que deseas crear. Las opciones disponibles se describen en [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+4. Haz clic en `Guardar`.
+
+Las condiciones definidas pueden funcionar en forma conjunta (`y`) o alternativamente (`o`).
+
+En el menú de cada una de las condiciones existentes, puedes `Duplicar` o `Eliminar` la condición. Si deseas desactivar todas las condiciones creadas, haz clic en `Borrar filtros`.
diff --git a/docs/tracks/es/creating-or-editing-a-page-template.md b/docs/tracks/es/creating-or-editing-a-page-template.md
index 53186a073..2ddd43236 100644
--- a/docs/tracks/es/creating-or-editing-a-page-template.md
+++ b/docs/tracks/es/creating-or-editing-a-page-template.md
@@ -41,8 +41,8 @@ Vea a continuación el procedimiento:
 <li><code>admin</code></li>
 </ul></p>
 </div>
-7. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
-8. En la esquina superior derecha, haga clic en el botón  __Save Template__.![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
+7. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+8. En la esquina superior derecha, haga clic en el botón  __Save Template__.![4 2](//images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
 Para editar un template ya existente, el proceso es casi idéntico.
 
diff --git a/docs/tracks/es/creating-regular-promotions.md b/docs/tracks/es/creating-regular-promotions.md
index 7f35fbb63..c534ccfdf 100644
--- a/docs/tracks/es/creating-regular-promotions.md
+++ b/docs/tracks/es/creating-regular-promotions.md
@@ -3,8 +3,8 @@ title: 'Crear Promoción Regular '
 id: 7FjbeZdE2KMwk5L1t98pZI
 status: PUBLISHED
 createdAt: 2020-01-14T13:11:35.010Z
-updatedAt: 2022-12-08T19:33:56.600Z
-publishedAt: 2022-12-08T19:33:56.600Z
+updatedAt: 2024-04-22T13:23:15.737Z
+publishedAt: 2024-04-22T13:23:15.737Z
 firstPublishedAt: 2020-01-22T13:55:43.369Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,153 +14,157 @@ trackId: 6asfF1vFYiZgTQtOzwJchR
 trackSlugES: promociones
 ---
 
-En VTEX, se pueden [crear varios tipos de promociones](https://help.vtex.com/es/tutorial/como-criar-promocoes--tutorials_320#) para escenarios diferentes. Sin embargo, el más utilizado es la Promoción Regular. Este tipo de promoción permite que su tienda ofrezca descuentos de forma dinámica y flexible al combinar diferentes condiciones, restricciones y beneficios.
+En VTEX, se pueden crear varios tipos de promociones que se ajustan a diferentes escenarios. De entre ellos, el más utilizado es la promoción regular, ya que permite a la tienda ofrecer descuentos flexibles, combinando múltiples condiciones, restricciones y beneficios.
 
-En este artículo, detallamos cómo funciona cada campo durante los pasos de configuración de una promoción regular según se describen a continuación.
+Este artículo describe los pasos para configurar una promoción regular.
 
-1. [¿Cuáles son los datos generales de la promoción?](#1-cuales-son-los-datos-generales-de-la-promocion)
-    - [Restringir esta promoción a productos dos sellers](#restringir-esta-promocion-a-productos-dos-sellers)
-    - [Política Comercial](#politica-comercial)
-2. [¿A qué ítems se aplicará esta promoción?](#2-a-que-items-se-aplicara-esta-promocion)
-3. [¿Qué condiciones para la promoción sea válida?](#3-que-condiciones-para-la-promocion-sea-valida)
-4. [Restricciones y limitaciones de uso](#4-restricciones-y-limitaciones-de-uso)
+1. [Resumen de la promoción](#Resumen-de-la-promoción)
 
-Para entender la implementación de las promociones, lea nuestro artículo sobre [Ejemplos de Promociones](https://help.vtex.com/es/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD?&utm_source=autocomplete#).
+    ○  	[Restringir la promoción a los productos de los sellers](#restringir-la-promoción-a-los-productos-de-los-sellers)
 
-## 1. ¿Cuáles son los datos generales de la promoción? 
+    ○  	[Política comercial](#política-comercial)
 
-En esta sección, debe configurar los datos generales de la promoción. Los campos **Nombre**, **Validez** y **Cuál es el tipo y valor del descuento** son obligatorios.
+2. [¿A qué ítems se aplicará esta promoción?](#¿a-qué-ítems-se-aplicará-esta-promoción?)
 
-- **Nombre**: es el nombre de la promoción.
-- **Status**: define si la promoción está activa o inactiva.
-- **Descripción**: es la descripción interna de la promoción. El objetivo de este campo es que se utilice para comunicación interna en su tienda, a fin de dejar en claro si la promoción se debe a alguna campaña, liquidación de stock, etc.
-- **Validez**: es la fecha y hora de inicio y fin de la promoción. Se puede usar una fecha y hora futura para iniciar la promoción en el sitio web. Si se configura de esta forma, la promoción tendrá el status de programada hasta que se llegue a la fecha y hora definida. Mientras esté válida, la promoción tendrá el status de activa y al término de la fecha y hora definidas, su status cambiará a inactiva de forma automática.
-- **Utilizar configuraciones de recurrencia**: esta opción es del tipo de casilla de selección, que al ser activada pone a disposición otras siete casillas, de modo que se pueda seleccionar los días de la semana y las horas del día en que se aplicará la promoción. Si desea que la promoción se aplique en cualquier día de la semana, no seleccione esta opción.
-- **¿Cuál es el tipo y el valor del descuento?**: elección que define el tipo y valor del descuento que se aplicará a la promoción. Estas son las opciones de descuento:
+3. [Condiciones de la promoción](#condiciones-de-la-promoción)
 
-  - **Nominal**: es el descuento que se concederá al total del carrito. 
-  - **Carga nominal**: es el descuento que se concederá al valor del flete.
-  - **Porcentual**: porcentaje de descuento que se concederá al valor del producto.
-  - **Precio máximo por artículo**: el precio máximo para cada artículo de la compra será el precio registrado aquí.
-  - **Carga porcentual**: porcentaje de descuento que se concederá al valor del flete.
-  - **Envío máximo**: es el valor máximo establecido para el flete. 
-  - **Flete gratis**: es el descuento total sobre el valor del flete.
-  - **Regalo**: es el descuento total sobre el valor del producto definido como regalo. Puede seleccionar uno o más SKU como regalos, o más de una unidad para el mismo SKU. Para definir más de un regalo, escoja la opción **Activar multiplicador de regalo** y defina la cantidad deseada. Lea más sobre esta opción en este [artículo](https://help.vtex.com/es/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK#).
+4. [Restricciones y limitaciones de uso](#restricciones-y-limitaciones-de-uso)
+
+Para entender cómo funciona la implementación de promociones, consulta nuestro artículo [Ejemplos de promociones](https://help.vtex.com/es/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD?&utm_source=autocomplete).
+
+## Para crear una promoción regular, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Promociones > Promociones** o escribe **Promociones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el botón **Crear promoción**.
+3. Selecciona la opción **Regular**.
+4. Rellena los campos de la promoción.
+5. Haz clic en **Guardar**.
+
+# 1. Resumen de la promoción
+
+En esta sección, debes configurar la información general de la promoción. Los campos Nombre, Fecha de vencimiento y Cuál es el tipo y valor del descuento son obligatorios.
+
+- **Nombre:** nombre de la promoción. Campo obligatorio.
+- **Status:** activa o desactiva la promoción.
+- **Descripción:** descripción interna de la promoción. Este campo se utiliza para la comunicación interna de la tienda. Por ejemplo, se puede utilizar para indicar si la promoción se debe a alguna campaña o liquidación de stock.
+- **Fecha de vencimiento:** fecha y hora de inicio y fin de la promoción. Se pueden seleccionar una fecha y hora futuras para que la promoción comience a aplicarse en el sitio web. Si se configura de esta forma, el status de la promoción se mostrará de las siguientes maneras:
+    - **Programada:** antes de la fecha y hora de inicio seleccionadas.
+    - **Activa:** durante el periodo previsto para la promoción.
+    - **Inactiva:** después de la fecha y hora de fin seleccionadas.
+- **Utilizar configuración de recurrencia:** seleccionando esta opción, puedes realizar ajustes de recurrencia, por ejemplo, día de la semana y horario.
+- **Cuál es el tipo y valor del descuento:** permite seleccionar una de las opciones a continuación:
+    - **Nominal:** el descuento que se concederá al total del carrito.
+    - **Envío nominal:** el descuento que se concederá al valor del envío.
+    - **Porcentual:** porcentaje de descuento que se concederá al valor del producto.
+    - **Precio máximo por ítem:** el precio máximo para cada ítem de la compra será el precio registrado aquí.
+    - **Envío porcentual:** el porcentaje de descuento que se concederá al valor del envío.
+    - **Envío máximo:** el valor máximo del envío.
+    - **Envío gratis:** el descuento total sobre el valor del envío.
+    - **Regalo:** el descuento total sobre el valor del producto definido como regalo. Seleccionando esta opción podrás indicar el SKU (por nombre o ID) que se considerará como regalo, elegir si debe activarse el [multiplicador de regalo](https://help.vtex.com/es/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK) y la cantidad máxima de productos que se pueden utilizar como regalos en la promoción.
 <div class = "alert alert-info">
-  <p>El producto de regalo también debe tener un precio registrado aunque se dé al cliente de forma gratuita.</p>
+El producto de regalo también debe tener un precio registrado aunque se ofrezca gratuitamente al cliente.
 </div>
-  - **Descuento nominal basado en la fórmula**: el descuento se calcula en base a la fórmula que puede crear utilizando como variables la suma de los precios de los productos (`total`), el flete (`freight`) y la cantidad de artículos (`quantity`). Tenga en cuenta que el flete considerado por la fórmula será el más bajo disponible para el pedido, independientemente de la selección del cliente. El separador decimal debe ser siempre un punto. Ejemplo: si el descuento es del 30% del valor total del producto + el valor del flete, la fórmula debe ser `(total + flete) * 0,3`. Para más información sobre la fórmula, lea nuestra [documentación](https://help.vtex.com/es/tutorial/promocion-regular-con-descuento-nominal-basado-en-la-formula--2Pwrq6THyGViNedQG381jV).
-  - **Valor de fidelidad nominal:** es el crédito que será añadido al programa de fidelidad de la tienda. Lea [Promoción regular con valor de fidelidad](https://help.vtex.com/es/tutorial/promocion-regular-con-valor-de-fidelidad--3FCip23ZtvG0sDt0rVGVmR) para más información.
-  - **Valor de fidelidad porcentual**: es el porcentaje de crédito que se añadirá al programa de fidelidad de la tienda. Lea [Promoción regular con valor de fidelidad](https://help.vtex.com/es/tutorial/promocion-regular-con-valor-de-fidelidad--3FCip23ZtvG0sDt0rVGVmR) para más información.
-  - **Tabla de precios promocionales**: se puede utilizar una lista de precios como promoción. El precio promocional de cada SKU será el correspondiente a la lista de precios seleccionada.
 
-- **Destaque en los productos**: inserta una flag con el nombre de la promoción, usada en la vitrina y en la página del producto. Esta flag solo se insertará si se utiliza el control correcto de exhibición de promoción en el formato: `<vtex.cmc:discountHightLight/>`
+   - **Descuento nominal basado en fórmula:** el descuento se calcula con base en una fórmula que se puede crear utilizando como variables la suma de los precios de los productos, el envío y la cantidad de ítems. Ten en cuenta que el envío considerado por la fórmula será el envío de menor costo disponible para el pedido, independientemente de la selección del cliente. El separador decimal debe ser siempre el punto. Ejemplo: si el descuento es 30 % del valor total del producto + el valor del envío, la fórmula debe ser (total + freight) * 0.3. Para más información, consulta la [documentación de la fórmula](https://help.vtex.com/es/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
+   - **Valor de recompensa nominal:** el crédito que será añadido al programa de fidelidad de la tienda. Para más información, consulta [Promoción regular con valor de fidelidad](https://help.vtex.com/es/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR).
+   - **Valor de fidelidad porcentual:** el porcentaje de crédito que se añadirá al programa de fidelidad de la tienda. Para más información, consulta [Promoción regular](https://help.vtex.com/es/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) con valor de fidelidad.
+   - **Tabla de precios promocionales:** se puede utilizar una tabla de precios como promoción. El precio promocional de cada SKU será el correspondiente en la tabla de precios seleccionada.
+ - **Información adicional (opcional):** permite incluir en la promoción información adicional compuesta de un nombre y un valor.
+ - **Promoción resaltada:** inserta un flag con el nombre de la promoción utilizada en la vitrina y en la página del producto. El flag solo se inserta si se utiliza el control de visualización de promociones correcto en la plantilla: `<vtex.cmc:discountHightLight/>`.
 
 <div class = "alert alert-info">
-  <p>Las promociones del tipo <b>Nominal</b> solo se presentarán en el carrito, no en la vitrina o en la página de producto.</p>
+Las promociones nominales solo se muestran en el carrito, no en la vitrina o la página del producto.
 </div>
 
-### Restringir esta promoción a productos dos sellers
+## Restringir esta promoción a los productos de los sellers
 
-En esta sección, se puede definir a qué *sellers* se aplicará la promoción. Puede determinar cuáles de ellos serán incluidos o excluidos del descuento.  
+En esta sección se pueden definir los sellers a los que se aplicará la promoción. Es decir, tienes la opción de decidir los sellers que se incluirán o excluirán del descuento.
 
-- **Es igual a:** seleccione los nombres de los *sellers* deseados para incluirlos.
-- **Diferente de:** seleccione los nombres de los *sellers* deseados para excluirlos.
+- **Igual a:** selecciona los nombres de los sellers deseados para incluirlos.
+- **Diferentes de:** selecciona los nombres de los sellers deseados para excluirlos.
 
-Para que la promoción sea válida para todos los *sellers*, deje la selección sin marcar.
+Para que la promoción sea válida para todos los sellers, deja la selección sin marcar.
 
 <div class = "alert alert-warning">
   <p>No es posible seleccionar directamente un <em>seller white label</em>. Para incluir a un <em>seller white label</em> en la promoción, tiene dos opciones:</p><ol>1. Restringir a los <em>sellers</em> a la tienda principal. Esta restricción agrega a todos los <em>sellers white label</em> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <em>sellers</em>. Aquí, todos los tipos de <em>sellers</em>, <em>white label</em> o no, se agregarán a la promoción.</ol>
 </div>
 
-### Política Comercial
-
-Esta sección establece las políticas comerciales válidas para la promoción. Puede incluir o excluir las políticas comerciales del descuento.
-
-- **Es igual a:** seleccione las políticas comerciales deseadas para incluirlas.
-- **Diferente de:** seleccione las políticas comerciales deseadas para excluirlas.
-- **Proporcionado por mí (Mi tienda):** selección de las políticas comerciales para los productos de su tienda. Se puede seleccionar más de una política comercial.
-- **Entregado por mí (Tienda de otros):** selección de las políticas comerciales para sus productos que están en las tiendas de otros. Puede seleccionar más de una política comercial.
-
-Para que la promoción sea válida para todas las políticas comerciales, deje la selección sin marcar.
+## Política comercial
 
-## 2. ¿A qué ítems se aplicará esta promoción?
+Esta sección establece las políticas comerciales válidas para la promoción. Puedes incluir o excluir políticas comerciales del descuento.
 
-En esta sección, debe elegir si la promoción se aplicará a todos los productos registrados en su tienda o solo a productos específicos, como se ilustra a continuación.
+- **Igual a:** selecciona las políticas comerciales que deseas incluir.
+- **Diferentes de:** selecciona las políticas comerciales que deseas excluir.
+- **Proporcionado por mí (Mi tienda):** selección de las políticas comerciales con productos de tu tienda. Puedes seleccionar más de una política comercial.
+- **Entregado por mí (Otras tiendas):** selección de políticas comerciales bajo que rigen la presencia de tus productos tiendas de terceros. Puedes seleccionar más de una política comercial.
 
-![promocoes-restricao-es](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/83e378ce4788febd839ee10395e02f9f/image.png)
+Para que la promoción sea válida en todas las políticas comerciales, deja la selección sin marcar.
 
-Si desea aplicar la promoción a todo su catálogo, seleccione la opción **Aplicar a todos los productos.**
+# 2. ¿A qué ítems se aplicará esta promoción?
 
-Para limitar la promoción a productos específicos, seleccione **Aplicar a los siguientes productos** y luego rellene los criterios de selección para **Categorías, Marcas, Colecciones**, **Productos** y **SKUs**.
+En esta sección, debes seleccionar si la promoción se aplicará a todos los productos registrados en tu tienda o solo a productos específicos, como se ilustra a continuación:
 
-Puede incluir o excluir **categorías, marcas, colecciones**, **productos** y **SKUs** de la promoción utilizando los criterios **Es igual a** o **Diferente de**.
+- **Aplicar a todos los productos:** te permite aplicar la promoción a todo el catálogo.
+- **Aplicar a los productos que cumplen todas las restricciones siguientes:** permite limitar la promoción a productos específicos que deben cumplir los criterios de selección relativos a categorías, marcas, colecciones, productos y SKU.
+- **Productos:** permite elegir los productos a los que se aplicará la promoción. Puedes cargar un archivo .txt con los ID de los productos.
+- **SKUs:** permite escoger los SKU de los productos a los que se aplicará la promoción. Puedes cargar un archivo .txt con los ID de los productos.
 
-Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en la promoción todos los productos de la categoría **Vestido **cuya marca es **Farm**, con la excepción del producto **Vestido Rosas**.
+Puedes incluir o excluir **categorías**, **marcas**, **colecciones**, **productos** y **SKU** de la promoción utilizando los criterios **Igual a** o **Diferentes de**.
+Los productos deben cumplir todas las condiciones para ser válidos en la promoción.
 
-![exemplo-es](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/89c3e52e137f7856cb49628954217ff9/image.png)
+![A quais itens esta promoção será aplicada - ES](//images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/7ad5d4c49596dad8d2e81e0f1ef28d66/A_quais_itens_-_ES.png)
 
-En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
+# 3. Condiciones de la promoción
+El pedido del cliente debe cumplir las condiciones registradas en esta sección para ser válido en la promoción.
 
-<div class = "alert alert-warning">
-<p>Si selecciona<strong> Aplicar a los siguientes productos</strong> y no rellena ninguno de los criterios de selección, la promoción no se creará y aparecerá el mensaje <strong>Defina los productos elegibles o aplique a todos los productos</strong>. En este caso, debe volver y rellenar los criterios de selección o elegir <strong>Aplicar a todos los productos.</strong></p>
+- **Valor mínimo y máximo del pedido:** la promoción se aplicará teniendo en cuenta el valor bruto del carrito, sin considerar otras promociones o costos de envío.
+- **Valor acumulado en compras:** el descuento se concederá si el total de todas las compras realizadas por el cliente hasta este punto alcanzan el valor indicado.
+- **Precio del ítem entre:** el descuento se concederá si el valor del ítem está dentro del intervalo de valores indicados.
+- **Precio "de" y "por" son iguales o Precio "de" y "por" son diferentes:** corresponde a los valores de registro del producto. Solo se puede seleccionar una opción.
+- **Usar BINs de restricción:** permite activar o desactivar la restricción de BIN, limitando las tarjetas de crédito que se pueden utilizar en la promoción creada. También puedes importar una lista de BIN, que debe guardarse en un archivo de texto (.txt) con cada BIN descrito en una fila diferente.
+- **Tags de marketing:** campo utilizado para restringir la activación de la promoción si la compra se realiza a través del módulo [Suscripciones de VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453).
+- **Afiliados:** identificador de pedidos del marketplace. El descuento se aplicará a los afiliados seleccionados. Para más información, consulta el artículo [Qué es afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0?locale=pt).
+- **Clúster de clientes:** el descuento se concederá si el cliente está registrado en el clúster seleccionado. Es importante resaltar que el nombre del clúster debe coincidir exactamente con el nombre registrado. Cualquier error ortográfico impedirá que la configuración funcione correctamente. Para más información, consulta [Crear clúster de clientes](https://help.vtex.com/pt/tutorial/como-criar-um-cluster-de-clientes).
+- **Países de envío:** el descuento se concederá a los países seleccionados en este campo.
+- **El código postal de envío debe:** el descuento se concederá si el código postal cumple con la regla configurada. Es importante resaltar que los códigos postales que no estén registrados no son elegibles para activar la promoción.
+- **Método de envío:** el descuento se concederá si el tipo de envío seleccionado por el cliente es el mismo que el registrado en la promoción. Este criterio solamente se considerará si el efecto de la promoción está relacionado con el valor de envío, es decir, si el tipo de la promoción es Envío porcentual, Envío nominal, Envío máximo o Envío gratis. Ten en cuenta que esta configuración no se puede combinar con la opción "Aplicar el descuento solo a la opción de envío más barata".
+- **Aplicar el descuento solo cuando el cliente seleccione una de las transportadoras anteriores:** la promoción se aplicará solo después de que el cliente seleccione la forma de entrega en cuestión. Mientras no se seleccione, no tendrá descuento. Este criterio solo se tendrá en cuenta si el tipo de promoción está relacionado con el valor del envío, es decir, solo si el tipo es Envío porcentual, Envío nominal, Envío máximo o Envío gratis.
+- **Medio de pago:** permite elegir si la promoción se aplicará a uno o varios de los medios de pago seleccionados.
+<div class = "alert alert-info">
+El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con nuestro equipo de soporte <a href="https://support.vtex.com/hc/pt-br/requests">.
+técnica</a>.</p>.
 </div>
 
-Para ser válidos en la promoción, los productos deben cumplir todas las condiciones registradas en esta sección.
-
-## 3. ¿Qué condiciones para la promoción sea válida?
+- **Número de cuotas:** el descuento se concederá si la cantidad de cuotas seleccionada por el cliente está en el intervalo registrado. Este campo no se aplica a la selección de boleto.
 
-El pedido del cliente debe cumplir las condiciones registradas en esta sección para ser válido en la promoción.
-
-- **Valor mínimo y máximo del pedido:** la promoción se aplicará teniendo en cuenta el valor "bruto" del carrito, sin considerar otras promociones o el flete.
-- **Valor acumulado de las compras:** se concederá el descuento si el total de todas las compras ya realizadas por el cliente alcanza el valor ingresado.
-- **Valor del ítem entre:** se concederá el descuento si el valor del ítem cumple el intervalo de valores ingresados.
-- **Precio "de" y "a" son iguales** o **Precio "de" y "a" son diferentes:** se refiere al precio del producto. Solo se puede seleccionar una opción.
-- **Restricción de promoción por BIN:** se concederá el descuento si el BIN de la tarjeta está entre los ingresados.
-- **Marketing Tags:** campo utilizado para restringir la activación de la promoción si la compra es realizada por el [módulo de Suscripciones de VTEX](https://help.vtex.com/es/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#)
-- **Afiliados:** identificador de pedidos del Marketplace. Se aplicará el descuento a los afiliados seleccionados. Vea el artículo [Qué es afiliado](https://help.vtex.com/es/tutorial/que-es-afiliado--4bN3e1YarSEammk2yOeMc0?locale=es) para más información.
-- **Clúster de clientes:** se concederá el descuento si el cliente está registrado en el clúster seleccionado. Es importante destacar que el nombre del clúster debe ser exactamente como se ha registrado, cualquier error ortográfico impedirá el correcto funcionamiento de la configuración.
-- **Países de entrega:** se concederá el descuento a los países seleccionados en este campo. 
-- **El código postal de entrega debe:** se concederá el descuento si el código postal está de acuerdo con la regla configurada.
-- **Tipo de carga:** se concederá el descuento si el tipo de flete es igual al registrado. Este criterio solo se considerará si la promoción está relacionada con el Valor de Flete, es decir, en alguno de los siguientes casos: Carga porcentual», «Carga nominal», «Envío máximo» o «Flete gratis».
-- **Aplicar el descuento solamente con el flete más barato:** si habilita esta opción, el descuento del flete se aplicará solamente al valor menor calculado por el flete. Esta opción está habilitada de forma predeterminada, pero puede inhabilitarla si desea aplicar el descuento a otros tipos de flete. Lea el artículo [Registrar promociones de envío](https://help.vtex.com/es/tutorial/configurar-promocoes-de-frete--6Lo5BR61KMiUFAAHGCdgfW) para más información. Este criterio solo se considerará si la promoción está relacionada con el Valor de Flete, es decir, en alguno de los siguientes casos: Carga porcentual», «Carga nominal», «Envío máximo» o «Flete gratis».
-- **Aplicar el descuento solamente cuando el cliente seleccione uno de los transportistas anteriores:** la promoción se aplicará solo después de que el cliente seleccione la forma de entrega en cuestión. Mientras no se seleccione, no tendrá descuento. Este criterio solo se considerará si la promoción está relacionada con el Valor de Flete, es decir, en alguno de los siguientes casos: Carga porcentual», «Carga nominal», «Envío máximo» o «Flete gratis».
-- **Medio de pago:** se concederá el descuento si el medio de pago seleccionado por el cliente es igual al registrado. Este descuento solo se aplica al finalizar la compra, cuando el cliente seleccione el mismo medio de pago registrado aquí.
-
- <div class = "alert alert-info">
-  <p> Por estándar, puede registrar hasta 20 medios de pago por promoción. Además, existe la posibilidad de personalización para incluir hasta 100 medios de pago. Si necesita utilizar más de 20, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro servicio de asistencia
-técnica</a>.</p>
- </div>
-
-- **Número de cuotas:** se concederá el descuento si el número de cuotas seleccionado por el cliente está dentro del intervalo registrado. Este campo no se aplica para la selección de boleto bancario.
-
-<div class = "alert alert-warning">
-  <p><b>Atención</b>: las promociones por medio de pago y/o número de cuotas no se aplican a pedidos pagados con dos tarjetas o vales de compra.</p>
+<div class="alert alert-warning">
+Las promociones por medio de pago y número de cuotas no se aplican a pedidos pagados con dos tarjetas o tarjetas de regalo.
 </div>
 
-- **Utm\_source:** se concederá el descuento si la navegación se realiza con la **utm_source** correspondiente a alguno de los valores registrados. Es importante resaltar que el cliente solo puede ingresar una **utm_source** en el checkout.
-- **Utm\_campaign:** se concederá el descuento si la navegación se realiza con la **utm\_campaign** con el valor registrado.
-- **Generar cupón con las UTM arriba:** crea un cupón con las UTM registradas para darle al cliente acceso a esta promoción sin necesidad de las UTM, tan solo con el código del cupón.
-- **Utmi\_cp:** se concederá el descuento si la navegación se realiza con la utmi\_cp con el valor registrado (case sensitive).
+- **utm_source:** el descuento se concederá si la navegación utiliza un parámetro utm_source correspondiente a cualquiera de los valores registrados. Es importante resaltar que el cliente solo puede ingresar un **utm_source** en el checkout.
+- **utm_campaign:** el descuento se concederá si la navegación utiliza un parámetro utm_campaign con el valor registrado.
+- **Crear un nuevo cupón con los UTM anteriores:** crea un cupón a partir de los UTM registrados para que el cliente tenga acceso a esta promoción solo con el código del cupón.
+- **utmi_cp:** el descuento se concederá si la navegación se realiza con el utmi_cp con el valor registrado (distingue entre mayúsculas y minúsculas).
 
 <div class = "alert alert-info">
-  <p>En el campo de las UTM, ingrese solo el valor que tendrán las UTM para activar la promoción. No es necesario ingresar <i>?utm_source=</i> dentro del campo.</p>
+En el campo de UTM, ingresa únicamente el valor que deberán asumir los UTM para activar la promoción. No es necesario ingresar ?utm_source= dentro del campo.
 </div>
 
-- **Solo en la primera compra:** solo se concederá el descuento en la primera compra del cliente.
-- **Es un pedido de suscripción**: opción que define que la promoción se aplicará a los pedidos de suscripción. Estas son las condiciones:
-  - **Pedido original**: los pedidos que generan las suscripciones, pero que aún no forman parte de los ciclos de suscripción.
-  - **Pedidos recurrentes**: los pedidos que forman parte de los ciclos de suscripción.
-  - **Filtrar por**: es la selección que filtra qué pedidos de suscripción serán válidos para la promoción.
-      - **Frecuencia**: es la selección de la frecuencia de los pedidos por suscripción, que puede ser semanal, mensual y anual.
-      - **Número del ciclo**: es la selección de los ciclos de la suscripción que se incluirán en la promoción. Esta opción se desbloquea solamente si la de **Pedidos recurrentes** ha sido seleccionada anteriormente.
+- **Solo en la primera compra:** el descuento solo se concederá en la primera compra del cliente.
+- **¿Se debe aplicar el descuento incluso si el usuario no tiene sesión iniciada?:** este campo se muestra cuando se selecciona la opción Solo en la primera compra. Si se marca esta opción, la promoción se aplicará aun cuando el cliente no ingrese su email y contraseña. Por otro lado, si no se selecciona, la promoción solo se aplicará si el consumidor ingresó con su email y contraseña previamente registrados.
+  - **Es un pedido de suscripción:** permite seleccionar una de las siguientes dos opciones:
+  - **Primeros pedidos:** pedidos que generan suscripciones, pero que aún no forman parte de los ciclos de suscripción.
+  - **Pedidos recurrentes:** pedidos que forman parte de los ciclos de suscripción.
+  - **Filtrar por:** permite filtrar los pedidos de suscripción que serán válidos para la promoción.
+  - **Frecuencia:** permite seleccionar la frecuencia de los pedidos de suscripción: semanal, mensual y anual. Para más información, consulta [Configurar la frecuencia y la fecha del ciclo de suscripción](https://help.vtex.com/pt/tutorial/como-criar-um-anexo-de-assinatura--2bUuKyPflA8cOGLv8OvaKK#configurar-frequencia-e-data-do-ciclo-de-assinatura).
+  - **Número del ciclo:** permite seleccionar los ciclos de suscripción que se incluirán en la promoción. Esta opción solo se habilita si se selecciona la opción Pedidos recurrentes.
 
-- **Aplicar el descuento, incluso si el usuario no está conectado:** este campo se habilita cuando se selecciona el campo **solo en la primera compra**. Si se marca este campo, la promoción se aplicará incluso si el consumidor no ingresó su *email* y contraseña. Cuando no está marcado, la promoción solo se aplicará si el consumidor ha accedido con su *email* y contraseña previamente registrados.
+# 4. Restricciones y limitaciones de uso
+En esta sección se proporciona información importante sobre las condiciones y restricciones aplicables a la promoción.
 
-## 4. Restricciones y limitaciones de uso
+- **Cuántas veces se aplicará esta promoción en tu tienda:** limita la cantidad de veces que se aplicará la promoción. Al deseleccionar la opción ilimitado, se habilita un campo para registrar la cantidad de veces que se puede aplicar la promoción. Si la promoción ya ha sido creada, esta condición solo se aplicará a partir del día en que se configure, sin afectar los pedidos realizados anteriormente.
+- **Cuántas veces por cliente se aplicará esta promoción:** el valor de este campo determina la cantidad máxima de veces que cada cliente puede beneficiarse de la promoción. Por ejemplo, si se establece un límite de tres usos y la promoción se aplica tres veces en un mismo pedido, se considerará como un único uso en relación con el límite total. Esto significa que el cliente aún podrá utilizar la promoción en otros dos pedidos diferentes. Es importante resaltar que este cálculo es independiente de la cantidad de veces que se utilice la promoción en cada pedido individual.
+- **Establecer el número máximo de ítems elegibles para cada carrito:** define la cantidad de ítems del carrito sobre los que la promoción surtirá efecto. Consulta [Límite de ítems con promoción en el carrito](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para más información.
+- **Aplicar con otras promociones:** permite que se conceda más de una promoción al mismo tiempo sin importar el tipo de descuento. Aprende más sobre cómo [funciona la competencia de promociones](https://help.vtex.com/es/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270).
+- **Aplicar con precios manuales:** permite aplicar la promoción a productos cuyos precios hayan sido ingresados manualmente por el agente de televentas. Para activar la funcionalidad de precios manuales, utiliza el endpoint [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration).
 
-- **Cuántas veces esta promoción se aplicará en su tienda:** limita la cantidad de veces que se aplicará la promoción. Cuando no está marcada la opción **ilimitada**, se habilita un campo para registrar la cantidad de veces a la que estará limitada. Dado que la promoción ya ha sido creada, esta condición solo se aplicará a partir del día en que se establezca, sin que afecte a los pedidos realizados con anterioridad.
--  **Cuántas veces se aplicará la promoción a su tienda por cliente:** habilita la cantidad registrada arriba, no para la cantidad de uso total de la promoción, sino para la cantidad de veces que cada cliente podrá recibir la promoción. Si se selecciona también el campo anterior, tendrá una prioridad de aplicación superior a este límite.
-- **Definir la cantidad máxima de ítems afectados por carrito:** define a cuántos ítems del carrito se aplicará la promoción. Lea [este artículo](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para saber cómo configurar el campo.
-- **Permite que las promociones se acumulen:** permite que se conceda de forma simultánea más de una promoción, independiente del tipo de descuento. Sepa más sobre [cómo funciona la competencia de promociones](https://help.vtex.com/es/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270#)
-- **Permite que se acumule con precios manuales:** permite que la promoción se aplique a productos cuyos precios fueron introducidos manualmente por un usuario de televentas. Para habilitar la funcionalidad de precios manuales, utilice el *endpoint* [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration).
diff --git a/docs/tracks/es/credit-card-payment-flow.md b/docs/tracks/es/credit-card-payment-flow.md
index 6b96bdd16..54a69fa5d 100644
--- a/docs/tracks/es/credit-card-payment-flow.md
+++ b/docs/tracks/es/credit-card-payment-flow.md
@@ -1,10 +1,10 @@
 ---
 title: 'Flujo de pago por tarjeta de crédito  '
 id: TEYVv2fcVkH7et9n3OnBS
-status: CHANGED
+status: PUBLISHED
 createdAt: 2019-11-12T15:51:05.024Z
-updatedAt: 2020-11-27T19:39:59.301Z
-publishedAt: 2020-02-13T15:38:53.526Z
+updatedAt: 2023-11-01T12:40:40.235Z
+publishedAt: 2023-11-01T12:40:40.235Z
 firstPublishedAt: 2019-11-22T19:30:16.374Z
 contentType: trackArticle
 productTeam: Financial
@@ -31,9 +31,7 @@ Para saber más sobre los agentes financieros involucrados en el flujo de pago d
 
 El flujo completo para pago por tarjeta de crédito en VTEX puede ser descrito por la siguiente imagen.  
 
-<br/>
-![Cartão de crédito - Fluxo básico de um pagamento](https://images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/424c414ed06f81c4edcc676773fd00d9/Fluxo_Cart__o_de_Cr__dito.jpg)
-<br/>
+![Tarjeta de crédito - Flujo básico de un pago](//images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/354650e116ee61e05196dd1b592b6f6c/payments_image1_ES.JPG)
 
 1. En la pantalla de Checkout de su tienda, el cliente elige el **Medio de pago** _tarjeta de crédito_ para realizar el pago de su compra.
 2. La información de este pago se pasa al **Gateway de Pagos**, que es el player responsable de garantizar que este pago se realice con éxito.
diff --git a/docs/tracks/es/customer-identification.md b/docs/tracks/es/customer-identification.md
index 4a3d025f5..4feaf1459 100644
--- a/docs/tracks/es/customer-identification.md
+++ b/docs/tracks/es/customer-identification.md
@@ -27,7 +27,7 @@ Usted puede [configurar qué métodos de identificación desea habilitar](https:
 
 En el ejemplo de la imagen a continuación, Email y CPF están habilitados.
 
-![31. inStore - Product Overview - 2 - ES](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99fe77f7a5c0a43318ffa841e67d20cb/identify-customer-es.PNG)
+![31. inStore - Product Overview - 2 - ES](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99fe77f7a5c0a43318ffa841e67d20cb/identify-customer-es.PNG)
 
 Ingrese uno de estos datos en el campo y haga clic en el botón `Confirmar`.
 
diff --git a/docs/tracks/es/customizing-instore.md b/docs/tracks/es/customizing-instore.md
index 8ce4d47bb..2921e4a60 100644
--- a/docs/tracks/es/customizing-instore.md
+++ b/docs/tracks/es/customizing-instore.md
@@ -3,8 +3,8 @@ title: 'Personalización de VTEX Sales App'
 id: Rby973h1l9tEM4C1YrzwZ
 status: PUBLISHED
 createdAt: 2021-09-16T00:55:10.885Z
-updatedAt: 2023-05-31T16:08:29.389Z
-publishedAt: 2023-05-31T16:08:29.389Z
+updatedAt: 2023-07-24T23:04:49.692Z
+publishedAt: 2023-07-24T23:04:49.692Z
 firstPublishedAt: 2021-09-16T01:00:39.153Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugES: instore-primeros-pasos-y-configuracion
 
 La experiencia VTEX Sales App es personalizable. Puede aplicar funcionalidades y configuraciones específicas según las necesidades de su negocio, así como adaptar el _layout_ de la aplicación para que se ajuste a la identidad de su marca.
 
-Para ello, es necesario editar archivos JavaScript y CSS, tal y como se describe en la guía para desarrolladores[ How to customize VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/how-to-customize-instore).
+Para ello, es necesario editar archivos JavaScript y CSS, tal y como se describe en la guía para desarrolladores[ How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app).
 
 <div class="alert alert-warning">
 <p>La personalización de VTEX Sales App debe ser realizada por personas con experiencia en programación, ya que modificaciones incorrectas en estos archivos pueden provocar errores críticos.</p>
@@ -24,16 +24,16 @@ Para ello, es necesario editar archivos JavaScript y CSS, tal y como se describe
 
 Vea a continuación las personalizaciones disponibles en VTEX Sales App. Puede hacer clic en el nombre de cada una para acceder a su respectiva guía de implementación.
 
-* [Personalizar opciones de inicio de sesión en VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/customize-instore-login-options): permitir a los usuarios iniciar sesión en VTEX Sales App con su cuenta de Google o Facebook. 
-* [Cambiar el idioma de VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/change-instore-language): cambiar el idioma de VTEX Sales App a inglés o español. El idioma estándar de la aplicación es el portugués.
+* [Personalizar opciones de inicio de sesión en VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app#list-of-customizations): permitir a los usuarios iniciar sesión en VTEX Sales App con su cuenta de Google o Facebook. 
+* [Cambiar el idioma de VTEX Sales App](https://developers.vtex.com/docs/guides/change-vtex-sales-app-language): cambiar el idioma de VTEX Sales App a inglés o español. El idioma estándar de la aplicación es el portugués.
 * [Habilitar el campo Observación en la página del pedido](https://developers.vtex.com/vtex-rest-api/docs/enable-the-remarks-field-in-the-order-screen): activar un campo para registrar información adicional sobre el pedido. Los datos introducidos en este campo se envían al módulo **Gestión de pedidos**.
     * [Habilitar el código del vendedor](https://developers.vtex.com/vtex-rest-api/docs/sales-associate-code): activar el código del vendedor, es decir, una personalización adicional del campo **Observación** para convertirlo en un campo obligatorio en el que los vendedores deben introducir sus códigos personales durante el flujo de compra.
 * [Habilitar transferencia y captura del carrito entre dispositivos:](https://developers.vtex.com/vtex-rest-api/docs/enable-cart-transfer-between-devices) permitir que una compra iniciada en un dispositivo se finalice en cualquier otro dispositivo presente en el flujo de compra, sin necesidad de volver a añadir productos al carrito. Para más información, consulte [este artículo](https://help.vtex.com/pt/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/2hlBqxHlxgFo2o4R52pbsk).
 * [Habilitar el filtro de pedidos por vendedor: ](https://developers.vtex.com/vtex-rest-api/docs/enable-order-filter-by-sales-associate)definir que cada vendedor solo pueda ver los pedidos realizados por él, en lugar de mostrar todos los pedidos de la tienda por defecto.
 * [Forzar disponibilidad de stock: ](https://developers.vtex.com/vtex-rest-api/docs/force-stock-availability)permitir la venta de ítems que no están disponibles en el stock del ecommerce. Por defecto, si un ítem no tiene stock en el catálogo de la tienda, no puede venderse en VTEX Sales App. Sin embargo, hay casos en los que el ítem está disponible en la tienda física. Esta personalización permite la venta en estos casos.
-* [Configurar la impresión del resumen del pedido](https://developers.vtex.com/vtex-rest-api/docs/set-up-the-order-summary-printing): habilitar la impresión de un resumen del pedido al finalizarlo utilizando VTEX Sales App.
+* [Configurar la impresión del resumen del pedido](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app#list-of-customizations): habilitar la impresión de un resumen del pedido al finalizarlo utilizando VTEX Sales App.
     * [Añadir texto adicional a la impresión del pedido](https://developers.vtex.com/vtex-rest-api/docs/add-extra-text-to-the-order-print): añadir un texto personalizado a la impresión del resumen del pedido.
 
 ## Sepa más
 
-* [How to customize VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/how-to-customize-instore)
+* [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app)
diff --git a/docs/tracks/es/customizing-styles.md b/docs/tracks/es/customizing-styles.md
index 0e529f00b..87dfb4ef3 100644
--- a/docs/tracks/es/customizing-styles.md
+++ b/docs/tracks/es/customizing-styles.md
@@ -48,7 +48,7 @@ Vamos a hacer algunos cambios en nuestro archivo `style.json`. Podemos cambiar u
 
 Ahora, vamos a ver los resultados al "linkar" nuestra aplicación:
 
-![style-json](https://images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
+![style-json](//images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
 
 Muy bien! Ahora usted sabe cómo personalizar los estilos de su tienda.
 
@@ -98,4 +98,4 @@ Vamos a escribir un poco de CSS, para añadir una línea roja sólida:
 ```
 Nuestro nuevo menú de categoría tendrá ahora una línea roja sólida a lo largo de la parte inferior del menú.
 
-![red-line](https://images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
+![red-line](//images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
diff --git a/docs/tracks/es/customizing-templates.md b/docs/tracks/es/customizing-templates.md
index 8db7d9d97..d4c93077b 100644
--- a/docs/tracks/es/customizing-templates.md
+++ b/docs/tracks/es/customizing-templates.md
@@ -119,6 +119,6 @@ Para añadir un componente a esa página, basta con declarar un nuevo bloque de
 
 Si guarda esto en `store/blocks.json` y ejecuta `vtex link` en su tienda, usted deberá ver un nuevo estante renderizado al visitar la página principal.
 
-![shelf](https://images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
+![shelf](//images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
 
 Usted puede personalizar los bloques declarados por la app `store-theme` libremente y también declarar nuevos. Por ahora, usted puede encontrar la documentación para cada componente en sus [repositorios de GitHub](https://github.com/vtex-apps?q=store-components). Aquí encontrará las propiedades disponibles para cada componente.
diff --git a/docs/tracks/es/dafiti-marketplace.md b/docs/tracks/es/dafiti-marketplace.md
index 80ae019ac..6718c6966 100644
--- a/docs/tracks/es/dafiti-marketplace.md
+++ b/docs/tracks/es/dafiti-marketplace.md
@@ -3,8 +3,8 @@ title: 'Dafiti marketplace'
 id: 5lAIj7OCqizD5EisLJvatx
 status: PUBLISHED
 createdAt: 2021-05-26T15:09:29.538Z
-updatedAt: 2021-05-26T15:51:04.313Z
-publishedAt: 2021-05-26T15:51:04.313Z
+updatedAt: 2024-06-26T15:28:29.564Z
+publishedAt: 2024-06-26T15:28:29.564Z
 firstPublishedAt: 2021-05-26T15:28:12.852Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/dashboard.md b/docs/tracks/es/dashboard.md
index e758776e1..42d18d920 100644
--- a/docs/tracks/es/dashboard.md
+++ b/docs/tracks/es/dashboard.md
@@ -1,10 +1,10 @@
 ---
 title: 'Dashboard'
 id: 7vg42kAdhUQeWBzncsSymN
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-01-24T15:01:36.426Z
-updatedAt: 2023-01-26T12:57:04.230Z
-publishedAt: 2023-01-26T12:57:04.230Z
+updatedAt: 2024-01-05T17:14:37.506Z
+publishedAt: 
 firstPublishedAt: 2023-01-25T14:42:22.919Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugES: conversational-commerce
 
 En la página Dashboard, los dueños de tiendas VTEX pueden ver las métricas del canal [VTEX Conversational Commerce](https://help.vtex.com/es/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/1NwwADrU70v3roPUV7dWxI). En este panel, puedes ver el rendimiento de las ventas y los indicadores de las sesiones, que también puedes filtrar por periodo y exportar a un archivo CSV.
 
-![Conversational Commerce Analytics Panel](https://images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/5493bb92bc05b4ab33eb295551783a96/Conversational_Commerce_Analytics_Panel_ES.png)
+![Conversational Commerce Analytics Panel](//images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/5493bb92bc05b4ab33eb295551783a96/Conversational_Commerce_Analytics_Panel_ES.png)
 
 ## Datos
 
diff --git a/docs/tracks/es/data-protection-roles.md b/docs/tracks/es/data-protection-roles.md
new file mode 100644
index 000000000..a901e0d90
--- /dev/null
+++ b/docs/tracks/es/data-protection-roles.md
@@ -0,0 +1,86 @@
+---
+title: 'Roles en la protección de datos'
+id: 5f8hTEw3xOALgqzus9VXKd
+status: PUBLISHED
+createdAt: 2024-05-03T16:42:23.883Z
+updatedAt: 2024-05-03T21:10:00.990Z
+publishedAt: 2024-05-03T21:10:00.990Z
+firstPublishedAt: 2024-05-03T16:58:44.285Z
+contentType: trackArticle
+productTeam: Others
+slug: roles-en-la-proteccion-de-datos
+locale: es
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugES: datos-y-privacidad
+---
+
+Para garantizar la seguridad y privacidad de la información, existen roles distintos para la posesión, control y procesamiento de datos personales. En la tabla siguiente presentamos cada uno de los roles del ecosistema de protección de datos:
+
+| Rol | Descripción |
+|---|---|
+| Titular de los dados | El titular es el propietario de sus propios datos personales. <br><br> Por ejemplo, un cliente en una tienda es el propietario de sus datos personales, y los utiliza para realizar una compra. |
+| Responsable del tratamiento | El responsable del tratamiento es la persona que decide los fines y criterios, de conformidad con las leyes sobre protección de datos, para utilizar datos personales. El responsable del tratamiento también determina la forma en que los encargados del tratamiento utilizarán los datos.  <br><br> Por ejemplo, el responsable del tratamiento de datos es el retailer, ya que decide los datos del cliente que son necesarios para realizar una compra. |
+| Encargado del tratamiento de datos | El encargado del tratamiento de datos es la persona que trata los datos personales por orden del responsable del tratamiento. <br><br> Por ejemplo, VTEX es el encargado que realiza el tratamiento de datos de los clientes finales en nombre de la tienda. VTEX no trata los datos sensibles de los clientes finales por decisión propia, sino únicamente por instrucciones directas de los gestores de la tienda. <br><br> Los términos de este tratamiento que realiza VTEX se definen en el [Data Processing Addendum (DPA)](#data-processing-addendum-dpa). |
+| Encargado secundario del tratamiento de datos | El encargado secundario del tratamiento de datos es una empresa tercera que procesa datos personales en nombre del encargado. El responsable del tratamiento de los datos debe tener visibilidad y estar de acuerdo con la contratación de un encargado secundario.  <br><br> Los encargados secundarios son los proveedores de infraestructuras y las sucursales de VTEX. Consulta la [lista completa de encargados secundarios VTEX](https://vtex.com/co-es/privacy-and-agreements/subprocessors/). |
+
+## Data Processing Addendum (DPA)
+
+El Data Processing Addendum (DPA) es el contrato entre el responsable del tratamiento (retailer) y el encargado del tratamiento de los datos (VTEX), que tiene como objetivo regular la forma en que VTEX procesa los datos personales en nombre del retailer.
+
+Este documento es un anexo al [Master Services Agreement (MSA)](https://vtex.com/co-es/privacy-and-agreements/agreements/), el contrato que regula la relación entre VTEX y retailers y establece las reglas de uso de la plataforma VTEX y de cualesquiera otros servicios o productos contratados.
+
+El DPA sigue el estándar establecido por el [Reglamento General de Protección de Datos (RGPD)](https://gdpr-info.eu/), la legislación más restrictiva en materia de privacidad de datos.
+
+En dicho documento podrás consultar la siguiente información:
+
+* Roles del encargado y responsable del tratamiento de los datos.
+* Cumplimiento de los derechos de los titulares de los datos.
+* [Encargados secundarios](https://vtex.com/co-es/privacy-and-agreements/subprocessors/).
+* Nuestras [medidas técnicas y administrativas](https://help.vtex.com/es/tracks/datos-y-privacidad--4Lc0i0an0DgnEtB0AUwlcq/7ANSqBP5DgOrVVyglo3Lbh) de seguridad de los datos.
+* Gestión de incidentes de seguridad.
+* Limitaciones de responsabilidad:
+    * Solicitudes de auditoría.
+    * Transferencia internacional de datos.
+    * Responsabilidad de VTEX en caso de indemnización por incidentes de seguridad.
+* Integridad y confidencialidad de los datos personales en VTEX.
+
+VTEX no utiliza los datos de los clientes finales para ningún otro fin que no sea llevar a cabo las operaciones de ecommerce siguiendo las instrucciones de los retailers.
+
+El DPA utilizado debe corresponder a la región específica del titular de los datos (cliente de la tienda).
+
+<div class="alert alert-warning">
+  <p>Accede a <a href="https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/">Data Processing Addendum - VTEX</a> para ver el DPA predeterminado de VTEX para cada región.</p>
+</div>
+
+## Responsabilidades compartidas
+
+Tanto VTEX como los retailers deben garantizar la seguridad de los datos personales, cada uno dentro de su ámbito definido. El ámbito de VTEX incluye la infraestructura de la plataforma y sus funcionalidades, mientras que el del retailer abarca el storefront, configuraciones en el Admin, credenciales de acceso y el reglamento local sobre privacidad. Aprende más en las secciones siguientes.
+
+## Responsabilidades de VTEX
+
+VTEX, como encargada del tratamiento de los datos, podrá asistir al retailer en el cumplimiento de los derechos de los titulares, en la realización de informes de impacto sobre la privacidad y en la notificación de cualquier incidencia sobre datos personales de la que tenga conocimiento. Además, VTEX se compromete a cumplir las [medidas de seguridad técnicas y administrativas](https://help.vtex.com/es/tracks/datos-y-privacidad--4Lc0i0an0DgnEtB0AUwlcq/7ANSqBP5DgOrVVyglo3Lbh) establecidas en el [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/).
+
+## Responsabilidades de retailers
+
+Los retailers, como responsables del tratamiento, son quienes deben determinar los fines y medios del tratamiento de datos personales. Por lo tanto, los retailers deben instruir a VTEX, en los términos contenidos en el [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/), para que los datos personales puedan ser utilizados en la plataforma con el fin de llevar a cabo operaciones de ecommerce.
+
+En el contexto comercial, corresponde al retailer definir la base jurídica para utilizar los datos personales de los clientes (titulares de los datos). Las bases jurídicas son los casos en los que la ley permite el uso de datos personales, por ejemplo, el consentimiento. Dichas bases jurídicas no son aplicables a VTEX, ya que solo actúa como encargada del tratamiento de los datos, en los términos del [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/), y no decide los fines para los que se utilizan los datos personales.
+
+### Reglamentos de privacidad
+
+Cada retailer debe realizar su propia evaluación de riesgos de privacidad, [informes de impacto a la privacidad (Privacy Impact Assessments)](https://gdpr-info.eu/issues/privacy-impact-assessment/), políticas de privacidad y medidas técnicas y organizacionales, así como el cumplimiento de los derechos de los titulares de datos personales que estén registrados en su tienda. Corresponde al retailer elegir los términos de su política de privacidad y hacerla pública en el sitio web, de conformidad con los reglamentos locales sobre privacidad.
+
+Los retailers deben aplicar sus propias medidas de seguridad y, en caso de incidentes relacionados con datos personales, deben notificarlo a las autoridades de protección de datos y a los titulares de los datos en conformidad con la legislación aplicable. Si tienes dudas específicas sobre las leyes de privacidad que se aplican a tu tienda, tus clientes finales, o necesitas asesoramiento sobre aspectos legales relacionados con tu negocio, te recomendamos consultar a un profesional especializado en protección de datos personales. 
+
+VTEX prestará asistencia al retailer en algunas de estas obligaciones, como las respuestas a los derechos de los titulares y la notificación de incidentes de seguridad, en virtud del [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/).
+
+### Acceso a la plataforma
+
+Los retailers desempeñan un papel crucial en la seguridad de los datos, ya que sus decisiones repercuten directamente en la protección de la información. Por ejemplo, al conceder acceso a la plataforma a determinados usuarios o equipos, o al compartir [claves de aplicación](https://help.vtex.com/es/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) (appKeys), el retailer influye en la seguridad de los datos almacenados en ese entorno.
+
+Para saber cómo gestionar correctamente las credenciales de acceso y garantizar la integridad de los datos, consulta los siguientes artículos:
+
+* [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [Recursos de License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3)
+* [Claves de aplicación](https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet)
+
diff --git a/docs/tracks/es/define-payment-methods-displayed-on-instore.md b/docs/tracks/es/define-payment-methods-displayed-on-instore.md
index be56621c5..76863634e 100644
--- a/docs/tracks/es/define-payment-methods-displayed-on-instore.md
+++ b/docs/tracks/es/define-payment-methods-displayed-on-instore.md
@@ -3,8 +3,8 @@ title: 'Definir los métodos de pago mostrados en VTEX Sales App'
 id: jHQQcyX3WKeUFidwSjmY1
 status: PUBLISHED
 createdAt: 2021-09-27T20:54:02.947Z
-updatedAt: 2023-05-31T16:13:49.825Z
-publishedAt: 2023-05-31T16:13:49.825Z
+updatedAt: 2023-07-05T17:16:01.041Z
+publishedAt: 2023-07-05T17:16:01.041Z
 firstPublishedAt: 2021-09-27T20:57:59.730Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugES: instore-pagos
 
 Ahora que la condición de pago ha sido creada, necesitas crear los filtros que definen los medios de pago que aparecerán en el _checkout_ de VTEX Sales App.
 
-Para ello, los desarrolladores de tu tienda deben personalizar un archivo JavaScript. Para más información, consulta la guía [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/define-payment-methods-displayed-on-instore).
+Para ello, los desarrolladores de tu tienda deben personalizar un archivo JavaScript. Para más información, consulta la guía [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/docs/guides/define-payment-methods-displayed-on-vtex-sales-app).
 
 <div class="alert alert-danger">
 <p>Para habilitar los pagos a través de la aplicación VTEX Sales App, como se explica en este artículo, es necesario realizar cambios en un archivo JavaScript. Esta operación debe ser realizada por personas con experiencia en programación. Modificaciones incorrectas en este archivo pueden causar errores críticos.</p>
diff --git a/docs/tracks/es/defining-centauro-trade-policy.md b/docs/tracks/es/defining-centauro-trade-policy.md
index b81495789..15b3d9f11 100644
--- a/docs/tracks/es/defining-centauro-trade-policy.md
+++ b/docs/tracks/es/defining-centauro-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definir la política comercial para Centauro'
 id: 2wFjrUoLI3q85r3QZA0Tp
 status: PUBLISHED
 createdAt: 2020-10-20T18:17:56.907Z
-updatedAt: 2022-12-08T20:35:41.540Z
-publishedAt: 2022-12-08T20:35:41.540Z
+updatedAt: 2023-10-19T14:10:07.750Z
+publishedAt: 2023-10-19T14:10:07.750Z
 firstPublishedAt: 2020-10-20T19:51:02.327Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/defining-dafiti-trade-policy.md b/docs/tracks/es/defining-dafiti-trade-policy.md
index 2f8bf8ae6..eb6a16167 100644
--- a/docs/tracks/es/defining-dafiti-trade-policy.md
+++ b/docs/tracks/es/defining-dafiti-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definición de la política comercial de Dafiti'
 id: 54cBCKrJgqdrm61vxihY1g
 status: PUBLISHED
 createdAt: 2021-02-23T21:32:12.282Z
-updatedAt: 2022-12-08T20:36:49.783Z
-publishedAt: 2022-12-08T20:36:49.783Z
+updatedAt: 2023-08-11T18:10:58.039Z
+publishedAt: 2023-08-11T18:10:58.039Z
 firstPublishedAt: 2021-02-23T21:41:19.622Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/defining-netshoes-trade-policy.md b/docs/tracks/es/defining-netshoes-trade-policy.md
index d3983d6c2..acb5d8bed 100644
--- a/docs/tracks/es/defining-netshoes-trade-policy.md
+++ b/docs/tracks/es/defining-netshoes-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definir la política comercial para Netshoes'
 id: 6ESk5Zk32baNfluXbL3Xmz
 status: PUBLISHED
 createdAt: 2021-02-23T20:04:34.470Z
-updatedAt: 2022-12-08T20:35:12.874Z
-publishedAt: 2022-12-08T20:35:12.874Z
+updatedAt: 2023-10-19T14:10:00.314Z
+publishedAt: 2023-10-19T14:10:00.314Z
 firstPublishedAt: 2021-02-23T20:20:32.953Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/defining-the-google-shopping-trade-policy.md b/docs/tracks/es/defining-the-google-shopping-trade-policy.md
index 259af26b8..4064e0315 100644
--- a/docs/tracks/es/defining-the-google-shopping-trade-policy.md
+++ b/docs/tracks/es/defining-the-google-shopping-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definir la política comercial'
 id: 3AqbcsWrge8zLt0BC5CtGd
 status: PUBLISHED
 createdAt: 2021-04-14T17:58:41.545Z
-updatedAt: 2022-12-08T21:04:01.815Z
-publishedAt: 2022-12-08T21:04:01.815Z
+updatedAt: 2023-10-23T20:22:26.830Z
+publishedAt: 2023-10-23T20:22:26.830Z
 firstPublishedAt: 2021-04-15T17:41:14.352Z
 contentType: trackArticle
 productTeam: Channels
@@ -23,13 +23,39 @@ Tendrá que solicitar la creación de una nueva política comercial solo si:
 - Necesita enviar diferentes precios a Google Shopping.
 
 Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), solo tiene que rellenar el [formulario de política comercial adicional](https://docs.google.com/forms/d/e/1FAIpQLSe9qCGB_KM_xsV5e9uNe06JE8tMZrWcv6EuHUOmqTiM8oRW7w/viewform). Si tiene alguna duda, póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)* seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`.
-
 La contratación de políticas comerciales adicionales para integración con un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), un [conector certificado (partner)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX está exenta de la cuota mensual.
 
 ## Envío de precios de productos
 
 El [precio](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu) de su producto en Google Shopping es determinado por la selección de la política comercial. Es importante prestar atención a algunos puntos.
 
-Si su política comercial tiene precios de/por (lo que VTEX llama [precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#precio-de-lista) y [precio calculado](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx#precio-calculado)), se enviará a Google Shopping el precio calculado, es decir, el precio «por».
+Si su política comercial tiene precios de/por (lo que VTEX llama [precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#precio-de-lista) y [precio calculado](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx#precio-calculado)), se enviará a Google Shopping el precio calculado, es decir, el precio «por». Para que estas promociones figuren en Google Shopping los productos deben cumplir los siguientes requisitos en Google Merchant Center:  
+
+- Se debe haber cobrado el precio base, o un precio superior, durante un periodo de 30 días (consecutivos o no) en los últimos 200 días.  
+- El precio base debe ser válido.  
+- El precio de oferta debe ser inferior al de base.  
+- El descuento de la oferta debe ser superior al 5 % e inferior al 90 %.  
+
+Si tus productos cumplen todos los requisitos anteriores, la herramienta aplica el valor promocional previamente configurado en VTEX en las vistas de Google Shopping.  
+
+## Descuento vinculado a medio de pago
+
+La activación del descuento vinculado a un medio de pago se lleva a cabo en dos etapas: la [configuración del descuento y el medio de pago]((#configurar-descuento) y posteriormente la activación de descuentos en la [configuración del conector](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).  
+
+### Configurar descuento  
+
+Para configurar un descuento vinculado a un medio de pago debes considerar la información contenida en los artículos a continuación:
+
+1. [Set a discount using the checkout API](https://developers.vtex.com/docs/guides/set-a-discount-using-the-checkout-api) para ingresar el medio de pago deseado en la variable `paymentSystemToCheckFirstInstallment` y simular un carrito de compras para comprobar si el medio de pago se ha actualizado.  
+2.  [Configurar descuento de precio al contado](https://help.vtex.com/es/tutorial/configurar-desconto-de-preco-a-vista--7Lfcj9Wb5dpYfA2gKkACIt) para vincular el SKU al método de pago.  
+3. [Configurar descuento del precio al contado para Google Shopping](https://help.vtex.com/es/tutorial/configurar-desconto-de-preco-a-vista-para-google-shopping--40K3R5d4NogMvCzIWdWt3e).  
+
+Una vez realizados los pasos anteriormente descritos, la activación deberá realizarse a través de la [configuración del conector](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
+
+<div class="alert alert-warning">
+En caso de que haya varios sellers vinculados a un producto de tu tienda, Google Shopping aplicará la regla de anunciar la mejor oferta disponible.
+  </div>
 
-Cuando hay varios _[sellers](https://help.vtex.com/es/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w)_ vinculados a un producto de su tienda, la regla para Google Shopping es anunciar la mejor oferta disponible.
+  <div class="alert alert-danger">
+Para que el descuento se envíe a Google Shopping, cada promoción creada solo puede tener vinculado un medio de pago.
+  </div>
diff --git a/docs/tracks/es/defining-the-shipping-strategy-via.md b/docs/tracks/es/defining-the-shipping-strategy-via.md
index 8254f5d79..a0b2bef4f 100644
--- a/docs/tracks/es/defining-the-shipping-strategy-via.md
+++ b/docs/tracks/es/defining-the-shipping-strategy-via.md
@@ -3,8 +3,8 @@ title: 'Definir la Estrategia de Envío'
 id: 69cLhDK7PGOqgSs2EyqMke
 status: PUBLISHED
 createdAt: 2018-09-24T19:51:55.267Z
-updatedAt: 2022-01-18T22:08:54.766Z
-publishedAt: 2022-01-18T22:08:54.766Z
+updatedAt: 2023-11-30T21:11:02.106Z
+publishedAt: 2023-11-30T21:11:02.106Z
 firstPublishedAt: 2018-09-27T22:13:49.998Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/delivery.md b/docs/tracks/es/delivery.md
index e5ced40e6..9973ab0d2 100644
--- a/docs/tracks/es/delivery.md
+++ b/docs/tracks/es/delivery.md
@@ -27,19 +27,19 @@ Puedes elegir entre:
 - Recoger en una tienda física.
 - Personalizar por ítem.
 
-![entrega-2-es](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/338f5137a3c8c920f612657fd7290f3d/entrega-2-es.png)
+![entrega-2-es](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/338f5137a3c8c920f612657fd7290f3d/entrega-2-es.png)
 
 ### Puntos de recogida
 
 Para los puntos de recogida, el sistema selecciona las tiendas que tienen los SKUs en stock y muestra la tienda más cercana al código postal del cliente, como sugerencia. Si el vendedor quiere cambiar la tienda donde el cliente recogerá los productos, solo hay que hacer clic en el botón `Editar punto de recogida`.
 
-![entrega-retirada-es](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/6cdbea15076e2d11b6bcdb4bb72108ab/entrega-retirada-es.png)
+![entrega-retirada-es](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/6cdbea15076e2d11b6bcdb4bb72108ab/entrega-retirada-es.png)
 
 Al hacer clic en ese botón, el vendedor primero tiene acceso al punto de recogida sugerido por el sistema. Para ver todos los puntos de recogida disponibles, hay que hacer clic en `Ver todos los puntos de recogida`.
 
-![31. VTEX Sales App - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
+![31. VTEX Sales App - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
 
 La aplicación mostrará la lista de puntos de recogida ordenados por la distancia más corta desde el código postal del cliente. También es posible elegir el punto de recogida en el mapa.
 
-![31. VTEX Sales App - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
+![31. VTEX Sales App - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
 
diff --git a/docs/tracks/es/detaching-skus-by-specification.md b/docs/tracks/es/detaching-skus-by-specification.md
index 98f52f322..9dc8872b0 100644
--- a/docs/tracks/es/detaching-skus-by-specification.md
+++ b/docs/tracks/es/detaching-skus-by-specification.md
@@ -24,7 +24,7 @@ Esta herramienta se recomienda, principalmente, para las tiendas de ropa, porque
 
 A continuación, vea un ejemplo de separación de SKUs por color. La sandalia que se destaca en la siguiente imagen se exhibe en dos colores en el resultado de la búsqueda:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.</p></div>
diff --git a/docs/tracks/es/digital-wallet-e-wallet.md b/docs/tracks/es/digital-wallet-e-wallet.md
new file mode 100644
index 000000000..048f1909c
--- /dev/null
+++ b/docs/tracks/es/digital-wallet-e-wallet.md
@@ -0,0 +1,23 @@
+---
+title: 'Cartera digital (ewallet)'
+id: 7jLbdfch9Oe2yYbQa9zwE1
+status: PUBLISHED
+createdAt: 2023-06-27T21:10:04.185Z
+updatedAt: 2023-09-26T15:11:41.781Z
+publishedAt: 2023-09-26T15:11:41.781Z
+firstPublishedAt: 2023-06-27T21:47:02.764Z
+contentType: trackArticle
+productTeam: Shopping
+slug: cartera-digital-e-wallet
+locale: es
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugES: cartera-digital-e-wallet
+---
+
+Una cartera digital (también llamada ewallet) es un entorno seguro en el que se pueden almacenar datos bancarios y de tarjetas de crédito. Esta información se encripta en el sistema y, cuando su propietario accede a ella, puede utilizarla para realizar compras por internet.
+
+Comprar con una cartera digital ofrece más seguridad al usuario, ya que no necesita introducir sus datos de pago en el checkout de la tienda. En su lugar, el usuario es redirigido al entorno de la cartera digital, donde debe pasar por las etapas de autenticación.
+
+Con la identidad confirmada y el medio de pago elegido, la compra vuelve al flujo normal y se completa el pedido. Algunas carteras digitales también cumplen la función de subadquirentes, posibilitando que incluso una persona que no esté registrada pueda hacer una compra a través de su entorno.
+
+A continuación, algunos ejemplos de carteras digitales que pueden configurarse para realizar pagos en tu tienda VTEX: Cartera **Google**, **[Apple Pay](https://help.vtex.com/es/tutorial/configurar-pagamentos-com-apple-pay--5L3NWMgvdKswWQa6eIc008)**, **Samsung Pay, Paypal**, **Mercado** **Pago**, **PagSeguro**, **Stelo**, entre otros.
diff --git a/docs/tracks/es/enabling-2-factor-authentication-login.md b/docs/tracks/es/enabling-2-factor-authentication-login.md
index 78c13db36..5251c5e7f 100644
--- a/docs/tracks/es/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/es/enabling-2-factor-authentication-login.md
@@ -31,7 +31,7 @@ Hay dos opciones de autenticación:
 - __App Google__ (clave generada por aplicación de autenticación)
 - __Mensaje SMS__ (clave enviada por mensaje de texto)
 
-![2FA - Select - ES](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
+![2FA - Select - ES](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
 
 <div class="alert alert-warning">
 Recomendamos el uso de la <a href="#habilitar-o-2fa-por-aplicativo">aplicación de autenticación</a> para que las fallas del servicio de su operador de telefonía no impidan su inicio de sesión. A través de la aplicación, la clave de acceso siempre estará disponible para que la utilice.
@@ -47,17 +47,17 @@ Debido a que algunas empresas restringen el uso de celulares a los operadores de
 Para utilizar una clave generada a través de la aplicación de autenticación:
 1. Descargue la aplicación **Google Autenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)). 
 
-![2FA - App Download - ES](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
+![2FA - App Download - ES](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
 
 2. Utilice la aplicación para leer el código QR a través de la cámara del celular.
 
-![2FA - App QR Code - ES](https://images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/fde55b590db79ef108e5f1d508e18d3a/2FA_-_App_QR_Code_-_ES.png)
+![2FA - App QR Code - ES](//images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/fde55b590db79ef108e5f1d508e18d3a/2FA_-_App_QR_Code_-_ES.png)
 
 3. Su cuenta VTEX se agregará a la aplicación, que generará un código de 6 dígitos. Ingrese ese código para finalizar su inicio de sesión.
 
   *El código de la app se actualiza periódicamente. No es necesario que lo memorice, solo debe consultar la aplicación cuando lo necesite.*
 
-![2FA - App Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
+![2FA - App Insert Code - ES](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
 
 <div class="alert alert-info">
 Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso <strong> cada 3 días</strong>. Cuando eso suceda, basta con consultar el código en la aplicación.
@@ -69,11 +69,11 @@ Para utilizar una clave enviada a través de mensaje de texto:
 
 1. Ingrese su número de celular para que le enviemos el código por SMS, no olvide colocar el código de país y área. 
 
-![2FA - SMS Insert Phone - ES](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
+![2FA - SMS Insert Phone - ES](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
 
 2. Usted recibirá un mensaje de texto de VTEX en el celular indicado. Ingrese la clave de 6 dígitos para finalizar su inicio de sesión.
 
-![2FA - SMS Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
+![2FA - SMS Insert Code - ES](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
 
 <div class="alert alert-warning">
 No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o <a href="#habilitar-o-2fa-por-aplicativo">habilitar 2FA a través de la aplicación</a>.
@@ -85,11 +85,11 @@ Para modificar la configuración de la verificación en dos etapas:
 
 1. Acceda a su configuración de usuario, haciendo clic en el círculo con sus iniciales en el lado superior derecho del Admin. 
 
-![2FA - User Initials - ES](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
+![2FA - User Initials - ES](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
 
 2. Haga clic en **Verificación en 2 pasos** para ver su configuración.
 
-![2FA - My User - ES](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
+![2FA - My User - ES](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
 
 3. Usted también puede modificar su configuración siguiendo pasos similares a los anteriores para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) y por [aplicación](#habilitar-o-2fa-por-aplicativo).
 
diff --git a/docs/tracks/es/enabling-a-sales-rep-code.md b/docs/tracks/es/enabling-a-sales-rep-code.md
index 16afe7087..2ff62450e 100644
--- a/docs/tracks/es/enabling-a-sales-rep-code.md
+++ b/docs/tracks/es/enabling-a-sales-rep-code.md
@@ -42,7 +42,7 @@ Después de seguir estas recomendaciones, acceda al módulo __Configuración de
 
 Al lado derecho de la pantalla, encontrará el archivo `checkout-custom-instore.js`.
 
-![codevendorES.png?h=250](https://images.ctfassets.net/alneenqid6w5/4hITwpBXNEoN359J96d2oy/0bb39f0f4085e4daf2bc3d6b4fca1d97/codevendorES.png)
+![codevendorES.png?h=250](//images.ctfassets.net/alneenqid6w5/4hITwpBXNEoN359J96d2oy/0bb39f0f4085e4daf2bc3d6b4fca1d97/codevendorES.png)
 
 Acceda a este archivo y agregue el siguiente código al objeto `window.INSTORE_CONFIG`:
 
@@ -66,7 +66,7 @@ Cada responsable debe completar las propiedades del objeto `window.INSTORE_CONFI
 
 Por último, finalice haciendo clic en el botón azul __Guardar__ que se encuentra en la parte superior de la página.
 
-![codevendor2ES](https://images.ctfassets.net/alneenqid6w5/zkFzm3m0NvekTQZQRznzZ/8a65b58374a71cd91b3ce972844fc762/codevendor2ES.png)
+![codevendor2ES](//images.ctfassets.net/alneenqid6w5/zkFzm3m0NvekTQZQRznzZ/8a65b58374a71cd91b3ce972844fc762/codevendor2ES.png)
 
 ## Entendiendo las propiedades
 
diff --git a/docs/tracks/es/enabling-cart-transfer-between-devices.md b/docs/tracks/es/enabling-cart-transfer-between-devices.md
index 12f212d3b..bc0daf875 100644
--- a/docs/tracks/es/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/es/enabling-cart-transfer-between-devices.md
@@ -34,11 +34,11 @@ window.INSTORE_CONFIG = {
 
 Después de realizar este cambio, abra el menú inStore y actualice los datos haciendo clic en el botón __Restaurar Datos__. Una vez hecho esto, aparecerá un slider en la parte inferior de la página de identificación de inStore:
 
-![24. Enable cart transfer between devices - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/62BOCXeTPeE0Qa4dJQvAWV/01364823bc0b73dd1b8f383215f6602e/24._Enable_cart_transfer_between_devices_-_1_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/62BOCXeTPeE0Qa4dJQvAWV/01364823bc0b73dd1b8f383215f6602e/24._Enable_cart_transfer_between_devices_-_1_-_ES.png_h_250)
 
 Cuando arrastre la pantalla hacia la derecha, verá la pantalla para __Capturar Carrito__, como se muestra en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
 
 En esta pantalla, el vendedor puede capturar un carrito utilizando uno de estos tres métodos:
 - Código del carrito
@@ -49,4 +49,4 @@ En esta pantalla, el vendedor puede capturar un carrito utilizando uno de estos
 
 Para compartir un carrito, el vendedor puede generar un código numérico o un código QR. Para hacer esto, mientras está en la pantalla del carrito, haga clic en el botón __Transferir__. Vea un ejemplo en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
diff --git a/docs/tracks/es/enabling-product-recommendations.md b/docs/tracks/es/enabling-product-recommendations.md
index 2c3f6c96a..4b734665c 100644
--- a/docs/tracks/es/enabling-product-recommendations.md
+++ b/docs/tracks/es/enabling-product-recommendations.md
@@ -28,7 +28,7 @@ Si desea ocultar estas recomendaciones, debe editar los archivos `checkout-insto
 
 Al igual que el archivo JavaScript de personalización inStore, se debe acceder a `checkout-instore-custom.css` a través del panel administrativo de VTEX (como se explica en el artículo sobre [personalizaciones en el inStore](https://help.tex.com/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/4mwdBrFsmE2EPE0FzgX28b)).
 
-![25. Enable product recommendations - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/nEA1Zz5EeltimlFEFSMzy/8f489dd051c79453fd858d5376699c79/25._Enable_product_recommendations_-_1_-_ES.png_h_250)
+![25. Enable product recommendations - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/nEA1Zz5EeltimlFEFSMzy/8f489dd051c79453fd858d5376699c79/25._Enable_product_recommendations_-_1_-_ES.png_h_250)
 
 En el archivo `checkout-instore-custom.css`, incluya la siguiente regla CSS:
 
diff --git a/docs/tracks/es/endless-aisle.md b/docs/tracks/es/endless-aisle.md
index cb33d5fb9..c7d4f8d37 100644
--- a/docs/tracks/es/endless-aisle.md
+++ b/docs/tracks/es/endless-aisle.md
@@ -3,8 +3,8 @@ title: 'Pasillo Infinito'
 id: 40KMlmGI5tN0r0KPCDWgGn
 status: PUBLISHED
 createdAt: 2020-06-30T21:32:21.143Z
-updatedAt: 2023-05-31T15:34:48.839Z
-publishedAt: 2023-05-31T15:34:48.839Z
+updatedAt: 2023-07-26T18:46:19.274Z
+publishedAt: 2023-07-26T18:46:19.274Z
 firstPublishedAt: 2020-06-30T21:36:39.077Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/es/explained-search.md b/docs/tracks/es/explained-search.md
index 5bef7462a..7381a59ee 100644
--- a/docs/tracks/es/explained-search.md
+++ b/docs/tracks/es/explained-search.md
@@ -26,5 +26,5 @@ Siga las instrucciones a continuación para acceder a la página:
 1. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
 2. En **Intelligent Search**, haga clic en **Explicación de la búsqueda**. 
 
-![Explicación de Búsqueda](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
+![Explicación de Búsqueda](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
 
diff --git a/docs/tracks/es/extensions-hub-1.md b/docs/tracks/es/extensions-hub-1.md
index aa0218d96..4b04faa62 100644
--- a/docs/tracks/es/extensions-hub-1.md
+++ b/docs/tracks/es/extensions-hub-1.md
@@ -18,6 +18,6 @@ El Hub de extensiones es una sección del Admin VTEX que agrupa toda la informac
 
 Para acceder al Hub de extensiones ve al panel lateral izquierdo del Admin, haz clic en el ícono **Extensiones** y verás la sección en la parte superior del menú.
 
-![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
+![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
 
 La sección del Hub de extensiones tiene tres páginas: **App Store**, **Partners** y **Gestión de aplicaciones**. La documentación sobre cada una de ellas puede consultarse en los artículos a continuación.
diff --git a/docs/tracks/es/extensions-hub-app-store.md b/docs/tracks/es/extensions-hub-app-store.md
index 63a0620e7..b8b0814af 100644
--- a/docs/tracks/es/extensions-hub-app-store.md
+++ b/docs/tracks/es/extensions-hub-app-store.md
@@ -20,7 +20,7 @@ App Store es la página del Admin VTEX donde puedes buscar, visualizar y obtener
 
 Al entrar en la tienda estarás en la página de inicio,  con las siguientes opciones disponibles: 
 
-![Extensions Hub App Store página de inicio](https://images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/03756392e94a93e19546acc1f9e1bc75/Extensions_Hub_App_Store_home_page_ES.png)
+![Extensions Hub App Store página de inicio](//images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/03756392e94a93e19546acc1f9e1bc75/Extensions_Hub_App_Store_home_page_ES.png)
 
 * **Buscar:** cuadro de texto donde puedes buscar aplicaciones en la tienda. Al escribir en el cuadro de texto y pulsar la tecla `Intro`, accederás a la [página de búsqueda](#buscar).
 * **Destacados:** aplicaciones y partners destacados. Los destacados aparecen en formato de tarjetas rectangulares, en las que se puede ver el título y el subtítulo. Al hacer clic en un elemento destacado, accederás a la página de una aplicación o a la de un partner.
@@ -28,13 +28,13 @@ Al entrar en la tienda estarás en la página de inicio,  con las siguientes opc
 
 ## Buscar
 
-![Extensions Hub App Store busca](https://images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/59564b2103a79a2e5b4ebd9dfbad5fa5/Extensions_Hub_App_Store_search_ES.png)
+![Extensions Hub App Store busca](//images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/59564b2103a79a2e5b4ebd9dfbad5fa5/Extensions_Hub_App_Store_search_ES.png)
 
 El cuadro de búsqueda te permite buscar aplicaciones por su nombre. Al escribir lo que deseas encontrar y pulsar `Intro`, se te dirigirá a la página de resultados de la búsqueda. Los resultados serán las aplicaciones cuyos nombres coincidan con el texto introducido en la búsqueda. Las aplicaciones aparecen en formato de tarjetas cuadradas, donde puedes ver el nombre, el subtítulo y el costo de la misma. Al hacer clic en una tarjeta, accederás a la [página de la aplicación](#pagina-de-la-aplicacion).
 
 ## Página de la aplicación
 
-![Extensions Hub App Store app page](https://images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/a08b32f1a0af455d68c111c42cf4dd75/Extensions_Hub_App_Store_app_page_ES.png)
+![Extensions Hub App Store app page](//images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/a08b32f1a0af455d68c111c42cf4dd75/Extensions_Hub_App_Store_app_page_ES.png)
 
 Al hacer clic en una tarjeta en la página de inicio o en la búsqueda, se te dirigirá a la página de inicio de la aplicación. En esta página encontrarás toda la información sobre la aplicación, incluido el precio, y la opción de comprarla.
 
diff --git a/docs/tracks/es/extensions-hub-partners.md b/docs/tracks/es/extensions-hub-partners.md
new file mode 100644
index 000000000..5b82db8d7
--- /dev/null
+++ b/docs/tracks/es/extensions-hub-partners.md
@@ -0,0 +1,19 @@
+---
+title: 'Partners'
+id: 3XkOpOSbeCJIcBL5dhuPq1
+status: PUBLISHED
+createdAt: 2023-08-02T13:04:06.286Z
+updatedAt: 2023-08-02T14:33:05.047Z
+publishedAt: 2023-08-02T14:33:05.047Z
+firstPublishedAt: 2023-08-02T14:33:05.047Z
+contentType: trackArticle
+productTeam: VTEX IO
+slug: hub-de-extensiones-partners
+locale: es
+trackId: AW7klkYMh557y5IUOgzco
+trackSlugES: hub-de-extensiones
+---
+
+<div class="alert alert-warning">
+Contenido aún no disponible.
+</div>
diff --git a/docs/tracks/es/filter-orders-by-vendor.md b/docs/tracks/es/filter-orders-by-vendor.md
index 1a1d3ea0f..a0ab8e782 100644
--- a/docs/tracks/es/filter-orders-by-vendor.md
+++ b/docs/tracks/es/filter-orders-by-vendor.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 En inStore es posible ver el listado de todos los pedidos finalizados en una tienda:
 
-![pedidos finalizados](https://images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
+![pedidos finalizados](//images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
 
 Sin embargo, a veces tiene sentido que un vendedor vea sólo los pedidos finalizados por él. Para habilitar esta opción es necesario editar el archivo `checkout-instore-custom.js` presente en el Admin del Portal. Por tratarse de un JavaScript presente en diversos flujos de uso de la aplicación, es importante que usted tenga conocimientos de programación antes de cambiarlo, para evitar la ruptura de otras funcionalidades.
 
@@ -37,4 +37,4 @@ __IMPORTANTE__: No quite ninguna de las otras propiedades presentes en el objeto
 
 Después de recargar el inStore el resultado debe ser el siguiente:
 
-![pedidos finalizados filtrados por vendedor](https://images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
+![pedidos finalizados filtrados por vendedor](//images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
diff --git a/docs/tracks/es/filters.md b/docs/tracks/es/filters.md
index 807d18afe..dac085270 100644
--- a/docs/tracks/es/filters.md
+++ b/docs/tracks/es/filters.md
@@ -3,8 +3,8 @@ title: 'Filtros'
 id: 50Dh4mpv0Sax0XpbvsjAtP
 status: PUBLISHED
 createdAt: 2020-03-05T17:44:58.362Z
-updatedAt: 2023-05-05T19:32:35.780Z
-publishedAt: 2023-05-05T19:32:35.780Z
+updatedAt: 2024-06-04T15:34:47.299Z
+publishedAt: 2024-06-04T15:34:47.299Z
 firstPublishedAt: 2020-03-05T19:54:44.962Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -37,13 +37,13 @@ La funcionalidad Filtros tiene las siguientes funciones:
 - Búsqueda que permite al cliente buscar un término dentro de un filtro.
 - Configurar y definir la cantidad máxima de opciones en un filtro antes de generar un desplazamiento.
 - Configurar en cuál *layout* se mostrará un filtro. Puede elegir entre los siguientes formatos:
- - Lista vertical (formato estándar).
- - Lista horizontal: se utiliza para mostrar filtros como «Tamaño» y «Color».
- - Barra deslizante: normalmente utilizada en los filtros numéricos, alterna del valor mínimo al valor máximo.
- - Conjunto con intervalos: división de productos en grupos de valores a partir de la cantidad de ítems.
- - Entrada de valores: permite al cliente introducir el valor «De» y «Hasta» que se utilizará para filtrar.
 
-Esta herramienta permite al cliente explorar las características relevantes de un producto durante la experiencia de búsqueda, así como proporcionar escenarios que facilitan la toma de decisiones del usuario.
+   - Lista vertical (formato estándar).
+   - Lista horizontal: se utiliza para mostrar filtros como «Tamaño» y «Color».
+   - Barra deslizante: utilizada para alternar del precio mínimo al precio máximo.
+   - Entrada de valores: permite al cliente indicar el precio “De” y “Hasta” que se utilizará en el filtro.
+
+Consulte la guía [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) en el Developer Portal para obtener más detalles técnicos sobre el uso de filtros.
 
 <div class="alert alert-warning">
   <p>Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.</p>
diff --git a/docs/tracks/es/frontend-implementation.md b/docs/tracks/es/frontend-implementation.md
new file mode 100644
index 000000000..b306a5c30
--- /dev/null
+++ b/docs/tracks/es/frontend-implementation.md
@@ -0,0 +1,320 @@
+---
+title: 'Implementación del frontend'
+id: 67SCtUreXxKYWhZh8n0zvZ
+status: PUBLISHED
+createdAt: 2024-01-31T22:25:47.689Z
+updatedAt: 2024-03-07T17:10:29.946Z
+publishedAt: 2024-03-07T17:10:29.946Z
+firstPublishedAt: 2024-02-22T14:07:19.178Z
+contentType: trackArticle
+productTeam: Others
+slug: implementacion-del-frontend
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+El frontend de una tienda online, también conocido como storefront, es la interfaz visual e interactiva de la tienda a través de la cual los clientes interactúan con los productos y realizan acciones, como navegar por las categorías, buscar y agregar productos al carrito.
+
+El propósito de este artículo es brindar orientación en la elección de la tecnología para construir el storefront, detallando los ajustes necesarios para cada opción, considerando los siguientes puntos:
+
+- Tecnologías de desarrollo de storefront de VTEX.
+- Principales funcionalidades de cada tecnología.
+- Etapas de desarrollo.
+
+La implementación del frontend es una etapa centrada en la definición de las tecnologías a implementar, en función de las necesidades del negocio relacionadas con el storefront.
+
+<div class = "alert alert-info">
+El frontend puede ser implementado tanto por el equipo de desarrollo interno de la empresa como por nuestros <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">partners de implementación</a>. <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512">Los usuarios</a> con acceso al Admin VTEX pueden consultar la lista de nuestros partners a través del <a href="https://partnerportal.vtex.com/">Partner Portal</a> (exclusivo Brasil).
+</div>
+
+## Antes de empezar
+
+Antes de empezar a implementar el frontend, se recomienda que la tienda complete las siguientes fases de configuración:
+
+| Fase | Descripción |
+|---|---|
+| Definición de la arquitectura de la tienda y la estrategia de ventas | El equipo define la arquitectura de la tienda VTEX en función de las estrategias y necesidades de tu modelo de negocio.<br><br>Más información en el artículo [Cuentas y arquitectura](https://help.vtex.com/en/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). |
+| Configuración de roles | El equipo configura los roles de acceso necesarios de cada [usuario](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512) para la utilización de la plataforma VTEX. <br><br>Más información en el artículo [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). |
+| Configuración del catálogo | El equipo configura el [catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) con los productos, el árbol de categorías y la información relacionada, como descripciones, imágenes y precios, para completar y probar la tienda, incluyendo recursos como las páginas de lista de productos (PLP), funcionalidad de búsqueda, las páginas de detalles de producto (PDP) y checkout.<br><br>La falta de catálogo puede resultar en pruebas incompletas y problemas en la integración de datos, lo que retrasa la implementación.<br><br>Más información en el artículo [Módulos de VTEX I](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7). |
+| Definición de las aplicaciones necesarias para la operación de la tienda | El equipo define las aplicaciones, tanto nativas como de terceros, necesarias para la operación de la tienda.<br><br>Hay una lista de aplicaciones nativas y de terceros para tiendas que se construyan usando [Store Framework](#store-framework).<br><br>Más información en el artículo [VTEX IO Apps](https://developers.vtex.com/docs/vtex-io-apps). |
+
+<div class = "alert alert-info">
+La <a href="#fases-de-desarrollo">fase de desarrollo</a> puede llevarse a cabo simultáneamente con otras fases de las <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">integraciones de backend</a> y <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7">configuración de módulos</a>, como por ejemplo, la configuración de medios de pago y ajustes logísticos. Esto va a depender del tipo de <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitectura y planificación</a> elegida para la tienda VTEX y deberá ir acompañado de la <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6ylpartners-de-implementacion">agencia implementadora</a> o del <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">soporte VTEX</a>.
+</div>
+
+## Tecnologías de desarrollo de frontend de VTEX
+
+VTEX cuenta con tres diferentes tecnologías para el desarrollo del storefront: [FastStore](#faststore), [Store Framework](#store-framework) y [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). CMS Portal Legado fue la primera tecnología de VTEX para la construcción de storefronts. Este sistema, basado en HTML, CSS y JavaScript, centraliza todo el proceso de desarrollo y edición de código a través del Admin VTEX.
+
+<div class="alert alert-warning">
+Aunque algunas tiendas aún lo utilizan, <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> es una tecnología heredada y ya no está disponible para tiendas que inician su trayectoria con VTEX.
+</div>
+
+Las siguientes secciones tratan sobre las principales características y funcionalidades de FastStore y Store Framework.
+
+## FastStore
+
+FastStore es una innovación tecnológica diseñada para permitir a los equipos de desarrollo crear tiendas enfocadas en el desempeño y la estabilidad. Además, destaca por su facilidad de mantenimiento, incluso para editar páginas del sitio web de la tienda. 
+
+Esta tecnología es un toolkit open-source basado en [React](https://react.dev/) y en la arquitectura [Jamstack](https://jamstack.org/). Para más información, consulta el portal de documentación de [FastStore](https://www.faststore.dev/docs).
+
+### Principales funcionalidades de FastStore
+
+La siguiente tabla muestra algunas de las principales funcionalidades de FastStore:
+
+| Funcionalidad | Descripción |
+|---|---|
+| [Starter](https://starter.vtex.app/) | Plantilla funcional diseñada para el desarrollo rápido de la tienda, que ya integra los componentes de [FastStore UI](https://www.faststore.dev/components). Incluye páginas como páginas de inicio, páginas de lista de productos (PLP), páginas de detalles de productos (PDP) y también la funcionalidad minicart. |
+| [FastStore UI](https://www.faststore.dev/components) | Biblioteca de componentes para ecommerce que ofrece recursos y estilos básicos para agilizar la implementación y personalización de storefronts. |
+| Tecnologia headless | Proceso de personalización que separa el código de la tienda, creado por el equipo de desarrollo, del código base suministrado por VTEX. Esto simplifica las actualizaciones del frontend de la tienda, haciendo que no impacten al código personalizado. |
+| Integración con [GitHub](https://github.com/) | Los equipos de desarrollo pueden gestionar todo el código del storefront mediante [GitHub](https://github.com/). |
+| [Headless CMS](https://www.faststore.dev/docs/headless-cms-overview) | Sistema de gestión de contenido (CMS) que permite editar y crear nuevas páginas y previsualizar los cambios en el contenido. |
+| Verificaciones automáticas | Se llevan a cabo de forma continua y automática pruebas funcionales y evaluación del desempeño de la tienda y de la calidad del código para detectar impactos de velocidad y bugs durante toda la fase de desarrollo del storefront. |
+| Integración con [Intelligent Search](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account) | Funcionalidad de autocompletar en la barra de búsqueda, junto con sugerencias de búsqueda y productos basados en preferencias configurables. |
+| Integraciones con [Checkout](https://www.faststore.dev/docs/go-live/4-integrating-the-vtex-checkout), [My Account](https://www.faststore.dev/docs/go-live/5-integrating-the-vtex-order-placed-and-my-account) y [Login](https://www.faststore.dev/docs/go-live/3-integrating-the-the-vtex-login) | Integración con otras fases de la jornada de compra del cliente. Las tiendas VTEX previamente desarrolladas con Store Framework pueden mantener los ajustes relacionados con Checkout, My Account y Login al migrar a FastStore, ya que ambas se benefician de la misma infraestructura. |
+
+## Store Framework
+
+Store Framework es una solución tecnológica establecida de framework para implementar storefronts low-code con un enfoque en el modelo composable commerce, es decir, el framework permite combinar diferentes apps de [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) para crear un storefront.
+
+En esta tecnología, la implementación y el lanzamiento de la tienda se centra en componentes preconstruidos, también conocidos como bloques, y en la posibilidad de personalizar estos componentes en función de las necesidades del modelo de negocio. Este framework se basa en:
+
+- React
+- TypeScript
+- Node.js
+- GraphQL
+
+Para más información, consulta el artículo [What is VTEX Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework).
+
+### Entorno de desarrollo
+
+Cuando se habla de implementación frontend, cabe recordar que [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) no es una tecnología de construcción de storefront, sino una plataforma de desarrollo. Store Framework es una tecnología de construcción de storefront ejecutada por VTEX IO, que a su vez es una solución de desarrollo y ejecución basada en la nube para aplicaciones personalizadas y storefronts.
+
+Esto significa que cuando trabajas con VTEX IO, desarrollas tu código localmente. Sin embargo, en lo que respecta a implementar y ejecutar la tienda, además de encargarse del proceso de deploy, VTEX IO gestiona la infraestructura, CI/CD y la seguridad. La siguiente imagen muestra cómo se relacionan estos conceptos entre sí:
+
+![Arquitectura de desarrollo frontend](//images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/b86208e7447890ebd62183059c0b22f6/frontend_image3_ES.png)
+
+### Principales funcionalidades de Store Framework
+
+La siguiente tabla muestra algunas de las principales funcionalidades de Store Framework:
+
+| Funcionalidad | Descripción |
+|---|---|
+| [Starter](https://github.com/vtex-apps/store-theme) | Plantilla funcional diseñada para el desarrollo rápido de la tienda, que ya integra los componentes preconstruidos. |
+| [Componentes preconstruidos](https://developers.vtex.com/docs/vtex-io-apps) | Componentes nativos basados en React. |
+| Arquitectura modular | Personalización y reutilización del código de elementos de la interfaz para lanzar y replicar tiendas rápidamente. |
+| [Workspaces y entornos de prueba](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace) | Permite crear distintas versiones de la tienda y probarlas antes para hacer cambios con seguridad. |
+| [Site Editor](https://help.vtex.com/es/tutorial/site-editor-vision-general--299Dbeb9mFczUTyNQ9xPe1) | Sistema de gestión de contenido (CMS) para editar plantillas y crear nuevas páginas en el sitio web de la tienda. |
+| [Pruebas A/B nativas](https://developers.vtex.com/docs/guides/ab-tests) | Permite probar y validar la versión de la tienda que tiene las tasas de conversión más altas. |
+| Integración con [Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) | Funcionalidad de autocompletar en la barra de búsqueda, junto con sugerencias de búsqueda y productos basados en tus preferencias. |
+| [Progressive Web App (PWA)](https://help.vtex.com/es/tutorial/habilitar-las-notificaciones-pwa-de-la-tienda--1be3ZPhbsgZSbE7h5H46pG) | Permite experiencias similares a las de una aplicación nativa en cualquier dispositivo con tecnología preparada para PWA. |
+| [Cross-border](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs) | Posibilita que una [multitienda](http://link-warm-up-multiloja) VTEX opere en diferentes países, adaptando su estrategia de manera individualizada para cada uno de ellos. |
+| Integración con Checkout, [My Account](https://help.vtex.com/es/tutorial/como-funciona-mi-cuenta--2BQ3GiqhqGJTXsWVuio3Xh) y Login | Integración con otras fases de la jornada de compra del cliente. |
+
+## Elegir la tecnología frontend
+
+A la hora de elegir entre Store Framework y FastStore, el equipo debe evaluar las necesidades específicas del proyecto y considerar la experiencia del equipo con ambas tecnologías.
+
+Store Framework es una opción más madura, que ofrece una estructura flexible adecuada para casos de uso complejos, así como soporte para tiendas que operan a escala internacional y con varios idiomas. Para las tiendas B2B, Store Framework es una excelente opción, ya que ofrece el [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite), una aplicación que permite el manejo de organizaciones, permisos de la tienda virtual y configuraciones de pago para relaciones comerciales B2B.
+
+FastStore es una alternativa más reciente en proceso de evolución, enfocada en el desempeño de la tienda. Esta solución ofrece una experiencia de carga rápida, que es esencial para mantener el interés de los visitantes de la tienda y reducir las tasas de abandono de carrito. FastStore es la tecnología más recomendada para casos de uso más simples enfocados en desempeño.
+
+<div class = "alert alert-info">
+El equipo de <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">soporte de VTEX</a> puede ayudarte a elegir una de las tecnologías de storefront disponibles.
+</div>
+
+En la siguiente tabla se comparan las dos tecnologías según sus principales funcionalidades:
+
+<table>
+    <tr>
+        <td><strong>Funcionalidad</strong></td>
+        <td><strong>Store Framework</strong></td>
+        <td><strong>FastStore</strong></td>
+    </tr>
+    <tr>
+        <td>Starter (plantilla inicial)</td>
+        <td><a href="https://github.com/vtex-apps/store-theme">Store Theme</a> es la plantilla inicial que el equipo puede utilizar como base para iniciar el proyecto de tienda o comenzar desde cero.</td>
+        <td><a href="https://starter.vtex.app/">FastStore Starter</a> se disponibiliza al finalizar el <a href="https://www.faststore.dev/docs/getting-started/1-faststore-onboarding/overview">Onboarding de FastStore</a>, lo que permite al equipo comenzar el proyecto con una plantilla base centrada en desempeño.</td>
+    </tr>
+    <tr>
+        <td>Desempeño</td>
+        <td>Los recursos SSR (Server Side Rendering) generan todo el HTML de una página en el servidor en respuesta a un request de la página, mientras que la SPA (Single Page Application) carga elementos como el header solamente cuando la página se ha cargado.</td>
+        <td>Posibilidad de máximo desempeño, ya que utiliza la arquitectura <a href="https://jamstack.org/">Jamstack</a> para crear las páginas del sitio web de la tienda con antelación, lo que hace que la entrega del sitio web sea más rápida y eficiente en términos de recursos.</td>
+    </tr>
+    <tr>
+        <td>Tech Stack</td>
+        <td>
+            <ul>
+                <li>TypeScript
+                <li>React
+                <li>GraphQL
+                <li>Node.js
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li>TypeScript
+                <li>React
+                <li>Next.js
+                <li>GraphQL
+                <li>Node.js
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Personalización de componentes</td>
+        <td>Flexible y fácil de personalizar.</td>
+        <td>Permite personalizar los componentes nativos y garantiza el desempeño de la tienda basándose en las mejores prácticas.</td>
+    </tr>
+    <tr>
+        <td>Gestión del código</td>
+        <td>Utiliza <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace">workspaces</a> y la arquitectura VTEX IO para distintas versiones, actualización y rollback (reversión) de componentes y aplicaciones.</td>
+        <td>Utiliza GitHub y el concepto de <a href="https://docs.github.com/pt/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches">branch</a> para colaboración. Los usuarios con autorización para acceder al repositorio del storefront en GitHub pueden ver y trabajar en el código.</td>
+    </tr>
+    <tr>
+        <td>Comunidad de soporte</td>
+        <td>
+            <ul>
+                <li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework">Documentación oficial</a>
+                <li><a href="https://community.vtex.com/c/store-development/store-framework/17">VTEX Community</a>
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li><a href="https://www.faststore.dev/docs">Documentación oficial</a>
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Monitoreo del desempeño y Analytics</td>
+        <td>
+            <ul>
+                <li>Posibilidad de configurar <a href="https://developers.vtex.com/docs/guides/google-tag-manager">VTEX Google Tag Manager</a> para analizar los datos de navegación de la tienda.
+                <li>Posibilidad de aumentar el desempeño del sitio web de la tienda utilizando herramientas de <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance">optimización de desempeño</a>.
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li>Posibilidad de configurar el módulo de Analytics nativo.
+                <li>Posibilidad de aumentar el desempeño del sitio web de la tienda utilizando herramientas tecnológicas.
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Sistema de gestión de contenido (CMS)</td>
+        <td>Compatible con <a href="https://help.vtex.com/es/tutorial/site-editor-vision-general--299Dbeb9mFczUTyNQ9xPe1">Site Editor</a>.</td>
+        <td>Compatible con <a href="https://www.faststore.dev/docs/headless-cms-overview">Headless CMS</a>.</td>
+    </tr>
+</table>
+
+## Fases de desarrollo
+
+Antes de lanzar la tienda en producción, y antes del [go-live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), enumera los ajustes esenciales y las características que deben incluirse en el storefront. Estas definiciones ayudan a establecer el Producto Mínimo Viable (PMV) para el storefront. En los siguientes temas se describen:
+
+- [Requisitos para un PMV de FastStore](#requisitos-para-un-pmv-de-faststore)
+- [Requisitos para un PMV de Store Framework](#requisitos-para-un-pmv-de-store-framework).
+
+<div class = "alert alert-info">
+Las recomendaciones a continuación abordan configuraciones básicas de storefront. Dependiendo de la <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitectura elegida</a> para la operación de la tienda, pueden ser necesarias otras configuraciones.
+</div>
+
+### Desarrollo con FastStore
+
+El equipo de desarrollo debe iniciar un nuevo proyecto con FastStore a través del proceso de [Onboarding](https://www.faststore.dev/docs/getting-started/1-faststore-onboarding/overview). Al final de este proceso, el equipo tendrá una tienda básica y funcional basada en [FastStore Starter](https://starter.vtex.app/). Una vez hecho esto, ya se habrán implementado los requisitos básicos de la página:
+
+- Página de inicio
+- Página de lista de productos (PLP)
+- Página de detalles de producto (PDP)
+- Minicart
+
+![FastStore template](//images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
+
+#### Requisitos para un PMV de FastStore
+
+A continuación se presentan los requisitos de cada tema:
+
+- Catálogo
+  - [Registrar productos y SKU](https://help.vtex.com/es/tutorial/registrar-productos--tutorials_2567)
+  - [Construir un árbol de categorías](https://help.vtex.com/es/tutorial/registrar-categoria--tutorials_206) ([departamentos](https://help.vtex.com/es/tutorial/que-es-un-departamento--22rKjmYWVmmKAK8CWa8yKw), [categorías](https://help.vtex.com/es/tutorial/que-es-una-categoria--6HV4Q3E2FauUoOQoiCCgCg) y [subcategorías](https://help.vtex.com/es/tutorial/que-es-una-subcategoria--2cb0aRkG3i6AeiAMM24iwY))
+  - [Definir filtros y tipos de especificaciones por categoría](https://help.vtex.com/es/tutorial/crear-grupo-de-especificaciones-en-una-categoria--tutorials_246)
+  - [Registrar imágenes de los SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY#imagenes)
+  - [Registrar precios de los SKU](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29)
+  - [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139)
+- VTEX Intelligent Search
+  - [Integrar la aplicación de Intelligent Search con la cuenta](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account)
+- Integración con Headless CMS
+  - [Configurar Headless CMS en la cuenta](https://www.faststore.dev/docs/headless-cms-integration/1-configuring-the-vtex-account)
+  - [Definir content types y las secciones que estarán disponibles](https://www.faststore.dev/docs/headless-cms-integration/2-setting-up-the-headless-cms)
+  - Crear y editar páginas utilizando Headless CMS en el Admin VTEX
+- Página de inicio
+  - Editar los componentes y estilos ya presentados en [Starter](https://starter.vtex.app/)
+- Página de inicio de sesión
+  - [Integrar con VTEX Login](https://www.faststore.dev/docs/go-live/3-integrating-the-the-vtex-login)
+  - Editar los componentes y estilos ya presentados en [Starter](https://starter.vtex.app/)
+- Página de lista de producto (PLP)
+  - Editar los componentes y estilos ya presentados en [Starter](https://starter.vtex.app/office)
+- Página de detalles de producto (PDP)
+  - Editar los componentes y estilos ya presentados en [Starter](https://starter.vtex.app/4k-philips-monitor-99988213/p)
+- Configuración de minicart
+  - Editar los componentes y estilos ya presentados en [Starter](https://starter.vtex.app/)
+- Checkout
+  - Integrar con [VTEX Checkout](https://www.faststore.dev/docs/go-live/4-integrating-the-vtex-checkout)
+  - Integrar con [VTEX Order Placed y My Account](https://www.faststore.dev/docs/go-live/5-integrating-the-vtex-order-placed-and-my-account)
+- Logística
+  - [Registrar muelle](https://help.vtex.com/es/tutorial/gestionar-el-muelle--7K3FultD8I2cuuA6iyGEiW)
+  - [Registrar estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
+  - [Relacionar la estrategia de envío y almacén con el muelle](https://help.vtex.com/es/tutorial/gestionar-el-muelle--7K3FultD8I2cuuA6iyGEiW)
+- Pagos
+  - [Configurar el proveedor Pagarés](https://help.vtex.com/es/tutorial/configurar-conector-pagares--7Gy0SJRVS0Qi2CuWMAqQc0)
+  - [Registrar proveedores de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444)
+- Desempeño y SEO
+  - Optimizar el desempeño del sitio web de la tienda utilizando herramientas [tecnológicas](https://v1.faststore.dev/how-to-guides/performance)
+- Métricas
+  - Configurar o módulo [Analytics](https://v1.faststore.dev/reference/sdk/analytics)
+
+### Desarrollo con Store Framework
+
+El equipo de desarrollo debe iniciar un nuevo proyecto con Store Framework clonando y [asociando](https://developers.vtex.com/docs/guides/vtex-io-documentation-linking-an-app) el [Store Theme](https://github.com/vtex-apps/store-theme) en un [workspace de desarrollo](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace). Store Theme es una plantilla funcional básica para iniciar una tienda con componentes esenciales y páginas como:
+
+- Página de inicio
+- Página de lista de productos (PLP)
+- Página de detalles de producto (PDP)
+
+![Store Framework template](//images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
+
+#### Requisitos para un PMV de Store Framework
+
+A continuación se presentan los requisitos para cada tema:
+
+- Catálogo
+  - [Registrar productos y SKU](https://help.vtex.com/es/tutorial/registrar-productos--tutorials_2567)
+  - [Construir un árbol de categorías](https://help.vtex.com/es/tutorial/registrar-categoria--tutorials_206) ([departamentos](https://help.vtex.com/es/tutorial/que-es-un-departamento--22rKjmYWVmmKAK8CWa8yKw), [categorías](https://help.vtex.com/es/tutorial/que-es-una-categoria--6HV4Q3E2FauUoOQoiCCgCg) y [subcategorías](https://help.vtex.com/es/tutorial/que-es-una-subcategoria--2cb0aRkG3i6AeiAMM24iwY))
+  - [Definir filtros y tipos de especificaciones por categoría](https://help.vtex.com/es/tutorial/crear-grupo-de-especificaciones-en-una-categoria--tutorials_246)
+  - [Registrar imágenes de los SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY#imagenes)
+  - [Registrar precios de los SKU](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29)
+  - [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139)
+- VTEX Intelligent Search
+  - [Integrar la aplicación de Intelligent Search con la cuenta](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account)
+- Página de inicio
+  - Editar los componentes y estilos ya presentados en [Starter](https://storetheme.vtex.com/)
+- Página de inicio de sesión
+  - Integrar con VTEX Login
+  - Editar los componentes y estilos ya presentados en [Starter](https://storetheme.vtex.com/)
+- Página de lista de producto (PLP)
+  - Editar los componentes y estilos ya presentados en [Starter](https://storetheme.vtex.com/clothing?_q=clothing&map=ft)
+- Página de detalles de producto (PDP)
+  - Editar los componentes y estilos ya presentados en [Starter](https://storetheme.vtex.com/ten-top-shirts/p)
+- Configuración de minicart
+  - Editar los componentes y estilos ya presentados en [Starter](https://storetheme.vtex.com/)
+- Logística
+  - [Registrar muelle](https://help.vtex.com/es/tutorial/gestionar-el-muelle--7K3FultD8I2cuuA6iyGEiW)
+  - [Registrar estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
+  - [Relacionar la estrategia de envío y almacén con el muelle](https://help.vtex.com/es/tutorial/gestionar-el-muelle--7K3FultD8I2cuuA6iyGEiW)
+- Pagos
+  - [Configurar el proveedor Pagarés](https://help.vtex.com/es/tutorial/configurar-conector-pagares--7Gy0SJRVS0Qi2CuWMAqQc0)
+  - [Registrar proveedores de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444)
+- Desempeño y SEO
+  - Optimizar el desempeño del sitio web de la tienda utilizando herramientas [tecnológicas](https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance)
+- Métricas
+  - Configurar [Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager)
diff --git a/docs/tracks/es/frontend.md b/docs/tracks/es/frontend.md
index d6a9ce07c..c99033826 100644
--- a/docs/tracks/es/frontend.md
+++ b/docs/tracks/es/frontend.md
@@ -26,7 +26,7 @@ La ampliación de funcionalidades se produce a través de aplicaciones VTEX disp
 
 Store Framework es una solución para construir storefronts aprovechando VTEX IO. Esta solución permite utilizar la interfaz intuitiva de [Site Editor](https://help.vtex.com/es/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) y simplificar la gestión de contenido de la tienda.
 
-![vtex io](https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5c359c6ec0fd106a7f7783669485c64e/image3.png)
+![vtex io](//images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5c359c6ec0fd106a7f7783669485c64e/image3.png)
 
 Las tiendas creadas con Store Framework también tienen las siguientes funcionalidades:
 - **[Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)**: herramienta de búsqueda que corrige errores ortográficos y permite usar reglas condicionales para mostrar los resultados de búsqueda.
diff --git a/docs/tracks/es/getting-started-with-logistics.md b/docs/tracks/es/getting-started-with-logistics.md
index 9dd93b2ea..ce9be5d6f 100644
--- a/docs/tracks/es/getting-started-with-logistics.md
+++ b/docs/tracks/es/getting-started-with-logistics.md
@@ -55,7 +55,7 @@ El módulo de **Inventario y envío** se divide en las siguientes secciones:
 * **Configuración**: configuraciones logísticas generales, como la activación de la notificación de stock crítico.
 * **[Puntos de recogida](https://help.vtex.com/es/tutorial/puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R)**: sección para registrar los puntos físicos donde los clientes pueden recoger sus pedidos.
 
-![estoque e entregaES](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/a66b016481c796b9170823b1c111d3d9/estoque_e_entregaES.png)
+![estoque e entregaES](//images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/a66b016481c796b9170823b1c111d3d9/estoque_e_entregaES.png)
 
 <div class = "alert alert-info">
 Los clientes que utilizan <a href="https://vtex.com/ar-es/">VTEX Shipping Network</a> acceden a la funcionalidad a través del módulo Inventario y envío.
diff --git a/docs/tracks/es/go-live-process.md b/docs/tracks/es/go-live-process.md
index 362bd1f3f..48a052b79 100644
--- a/docs/tracks/es/go-live-process.md
+++ b/docs/tracks/es/go-live-process.md
@@ -1,10 +1,10 @@
 ---
 title: 'Cómo realizar el go live de tu tienda'
 id: 1iP90RcJvlrfQhnlxM54wo
-status: PUBLISHED
+status: CHANGED
 createdAt: 2022-12-09T19:12:28.218Z
-updatedAt: 2023-03-27T14:51:55.484Z
-publishedAt: 2023-03-27T14:51:55.484Z
+updatedAt: 2024-05-24T14:32:56.445Z
+publishedAt: 2024-01-31T13:30:12.446Z
 firstPublishedAt: 2022-12-09T22:09:43.345Z
 contentType: trackArticle
 productTeam: Reliability
@@ -18,7 +18,7 @@ Si has [configurado el funcionamiento de tu tienda](https://help.vtex.com/pt/tra
 
 En este tutorial, encontrarás una guía detallada paso a paso sobre cómo realizar el _go live_ de tu tienda.
 
-![Go live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/d2dcbd2093cd822624d8ed29642eae4e/go_live_es.jpg)
+![Go live](//images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/d2dcbd2093cd822624d8ed29642eae4e/go_live_es.jpg)
 
 <div class = "alert alert-info">
 Ten en cuenta que una tienda en producción es diferente de una cuenta en producción. En general, se puede decir que para que una tienda esté en producción, es necesario poner la cuenta en producción y realizar el apuntamiento de DNS. Consulta todos los pasos de este proceso a continuación.
@@ -27,7 +27,7 @@ Ten en cuenta que una tienda en producción es diferente de una cuenta en produc
 ## Antes de comenzar
 Antes de realizar el go live de tu tienda, es importante garantizar que hayas completado todas las configuraciones necesarias para el buen funcionamiento de la tienda.
 
-Copia esta [Lista de verificación de tienda](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/c12e77226bfd0168252e98877b0459d4/Lista_de_verificaci__n_de_tienda.xlsx) y comprueba, para cada ítem, si realizaste la configuración de acuerdo con el funcionamiento deseado de la tienda.
+Copia esta [Lista de verificación de tienda](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f254ea28c42f4fe323bb5ad29fd0da36/Lista_verificacion_tienda.xlsx) y comprueba, para cada ítem, si realizaste la configuración de acuerdo con el funcionamiento deseado de la tienda.
 
 <div class="alert alert-warning">
 La lista de verificación que se presenta aquí muestra las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. Tu equipo debe definir qué funcionalidades implementará en la tienda y cómo se deben configurar para crear la experiencia de tienda deseada. Esto significa que la lista no necesariamente incluye todas las funcionalidades que tu tienda utiliza. Sin embargo, es importante verificar todos los aspectos del funcionamiento de tu tienda aunque no estén en la lista sugerida.
diff --git a/docs/tracks/es/google-pay.md b/docs/tracks/es/google-pay.md
new file mode 100644
index 000000000..3df083e66
--- /dev/null
+++ b/docs/tracks/es/google-pay.md
@@ -0,0 +1,111 @@
+---
+title: 'Google Pay'
+id: 61JMBvM5Vanqj6RaJsP8CT
+status: PUBLISHED
+createdAt: 2023-06-27T21:28:37.755Z
+updatedAt: 2024-08-01T17:59:31.657Z
+publishedAt: 2024-08-01T17:59:31.657Z
+firstPublishedAt: 2023-06-27T21:46:39.537Z
+contentType: trackArticle
+productTeam: Shopping
+slug: google-pay
+locale: es
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugES: cartera-digital-e-wallet
+---
+
+Google Pay™ es un servicio de pagos digitales que permite a los usuarios no compartir los datos reales de su tarjeta con la tienda, aportando más seguridad y agilizando la fase de checkout. Con Google Pay, el usuario puede realizar pagos utilizando tarjetas de crédito o débito, sin necesidad de rellenar ningún dato manualmente, y Google Pay también está disponible en muchas aplicaciones, sitios web y Catera Google. 
+
+Los términos de la API de Google Pay se aplican siempre que el administrador de la tienda ofrezca Google Pay como medio de pago. Para leer los términos, accede a [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
+
+<div class="alert alert-warning">
+<p>Google Pay no está disponible para Checkout V5 o versiones anteriores de Checkout.h</p>
+</div>
+
+## Activar Google Pay
+
+Para activar Google Pay, sigue los pasos a continuación. 
+
+1. En el Admin VTEX, haz clic en el ícono del engranaje **Configuración de la tienda > Pago > Carteras** o ingresa. **Carteras** en la barra de búsqueda de la parte superior de la página.
+2. Selecciona la opción **Activar** para modificar el checkout e incluir la extensión de Google Pay.
+
+<div class = "alert alert-info">
+<p>Las redes admitidas en Google Pay son las mismas configuradas en las condiciones de pago.</p>
+</div>
+
+Una vez hecho esto, Google Pay estará disponible en el checkout de tu tienda VTEX como nuevo medio de pago. La configuración puede demorarse alrededor de 10 minutos en aparecer en el checkout.
+
+![google-pay-checkout-es](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b131b38fa81affd857db8c107278f3e9/Screenshot_2024-08-01_at_14.22.06.png)
+
+<div class = "alert alert-warning">
+<p>Google Pay, por el momento, no admite suscripciones.</p>
+</div>
+
+Para utilizar Google Pay deben cumplirse los siguientes requisitos:
+
+* Tener al menos una [condición de pago](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) activa configurada para tarjetas de crédito o débito con un adquirente, definiendo qué [adquirente](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente) procesará el pago.
+* Utilizar el [Checkout VTEX](https://help.vtex.com/es/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) en tu tienda.
+
+<div class = "alert alert-warning">
+  <p>En las tiendas que tengan el flujo de autenticación <a href="https://help.vtex.com/es/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado y admitido por el adquirente, el pago con Google Pay seguirá el flujo nativo de la tarjeta y también utilizará 3DS. Para más información sobre este tema, accede a <a href="https://help.vtex.com/es/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar flujo de autenticación 3DS 2</a>.</p>
+</div>
+
+<div class="alert alert-info">
+<p>También puedes configurar Google Pay para que se procese con Adyen o Stripe. Para hacer esto, acceda a la pantalla <b>Condiciones de pago</b> en Admin, haga clic en <b>Google Pay</b> y seleccione la opción deseada.</p>
+</div>
+
+## Consultar transacciones finalizadas con Google Pay
+
+Para consultar y verificar las transacciones finalizadas con Google Pay, sigue los pasos indicados en el artículo [Ver detalles de la transacción](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy). En la barra de búsqueda de la página de transacciones, escriba **Google Pay** para filtrar las transacciones realizadas con este tipo de pago.
+
+![Google Pay Transaction_1](//images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/77ec267f3567f8d3988adf07c3a5d06a/Google_Pay_Transaction1_ES.png)
+
+Después de acceder a la transacción deseada, haga clic en "+ Información" para verificar la información de **Google Pay** descrita en el campo `paymentOrigin`.
+
+![Google Pay Transaction_2](//images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/394481aab2e3d50703ab836080f1e1c9/Google_Pay_Transaction2_ES.png)
+
+<div class="alert alert-warning">
+  <p>También es posible identificar las transacciones realizadas con Google Pay a través de la página <b>Todos los pedidos</b> en Admin. Sólo necesitas seleccionar el periodo de búsqueda deseado, <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">exportar los pedidos</a> en un informe en formato . csv y localizar la información de Google Pay en el campo "payment origin".</p>
+</div>
+
+## Agregar información de Google Pay en la plantilla de compra
+
+Para agregar en la plantilla de email que se le enviará al comprador la información de que el pedido se realizó con una tarjeta vinculada a Google Pay, sigue los pasos a continuación:
+
+1. En el Admin VTEX, haz clic en el ícono del engranaje **Configuración de la tienda > Plantillas de email > Plantillas** o ingresa el término **Plantillasen** la barra de búsqueda de la parte superior de la página.
+2. Accede a las plantillas de finalización de compra y aprobación del pago.
+3. Después de todas las menciones donde figura a `{{#if lastDigits}}` last digits `{{lastDigits}}`, agrega la siguiente línea:
+`{{/if}} {{#if paymentOrigin}} ({{paymentOrigin}}` 
+
+Así, siempre que haya cualquier mención de los últimos cuatro dígitos de la tarjeta en estas plantillas de email, se añadirá la información «(Google Pay)» si el pago se realizó con cartera digital.
+
+<div class = "alert alert-info">
+  <p>Para tiendas aprovisionadas a partir de marzo de 2023, las plantillas ya estarán actualizadas con la información del pago del pedido realizado con Google Pay.</p>
+</div>
+
+## Preguntas frecuentes
+
+### Problemas de activación
+
+* No ha sido posible habilitar la cartera, ya que el botón de alternancia está desactivado
+
+Ante el mensaje «Tu tienda todavía no tiene redes habilitadas para Google Pay.», accede a las condiciones de pago y comprueba que haya reglas asociadas para realizar transacciones con tarjeta con adquirentes.
+
+* El botón de alternancia está activado, pero no es posible finalizar el proceso
+
+Si al activar el botón de alternancia no aparece el mensaje «Google Pay activado con éxito», significa que puede haber ocurrido algún tipo de inestabilidad en el sistema. Si el problema persiste, el usuario recibirá un aviso para ponerse en contacto con [el soporte de VTEX](https://help.vtex.com/es/support).
+
+### Problemas que pueden ocurrir durante la compra
+
+* El dispositivo utilizado para finalizar la compra no es compatible con Google Pay
+
+Ante el mensaje "Forma de pago no disponible en tu navegador", el usuario debe intentar concluir la compra en otro navegador o dispositivo.
+
+* En la tienda no hay reglas configuradas para pago con tarjeta 
+
+Si el administrador de la tienda no ha configurado reglas de pago con tarjeta, el usuario verá un error al seleccionar Google Pay, señalando que este medio de pago no está disponible.
+
+### Más información 
+
+* [DPAN y FPAN: comprender la seguridad en el flujo de pagos tokenizados online](https://help.vtex.com/es/tutorial/dpan-e-fpan-entendendo-a-seguranca-no-fluxo-de-pagamentos-tokenizados-online--3RM7RvhKZ057wja5xVEOqb)
+
diff --git a/docs/tracks/es/google-shopping-marketplace.md b/docs/tracks/es/google-shopping-marketplace.md
index 9fea2cd40..93a24dbd8 100644
--- a/docs/tracks/es/google-shopping-marketplace.md
+++ b/docs/tracks/es/google-shopping-marketplace.md
@@ -3,8 +3,8 @@ title: 'Google Shopping'
 id: 2kGKxwD9HKJvTLDTikQ4zG
 status: PUBLISHED
 createdAt: 2021-04-14T14:19:25.417Z
-updatedAt: 2021-04-16T22:47:55.190Z
-publishedAt: 2021-04-16T22:47:55.190Z
+updatedAt: 2024-02-29T19:00:16.087Z
+publishedAt: 2024-02-29T19:00:16.087Z
 firstPublishedAt: 2021-04-15T17:41:07.946Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,7 +16,7 @@ trackSlugES: integracion-con-google-shopping
 
 [Google Shopping](https://shopping.google.com/) es una plataforma en la que el producto aparece en listas gratis que son clasificadas orgánicamente en las búsquedas de Google. Es decir, es un servicio de comparación y seguimiento de precios que incluye sus productos de forma gratuita en los resultados de búsqueda de productos locales.
 
-![google-shopping](https://drive.google.com/uc?export=download&id=1htNbqBqTs4HSdnPnp4Q6__wDzMTYPl6-)
+![Google Shopping](//images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/1cd372670bd55e0dbf359984e058d81e/logo_Google_shopping.png)
 
 A través de Google Shopping, puede mostrar al consumidor algunos de los atributos de su producto, tales como imagen, título, precio y nombre de su tienda.
 
diff --git a/docs/tracks/es/hide-product-suggestions-recommendation.md b/docs/tracks/es/hide-product-suggestions-recommendation.md
index 3f1a9add1..33882651d 100644
--- a/docs/tracks/es/hide-product-suggestions-recommendation.md
+++ b/docs/tracks/es/hide-product-suggestions-recommendation.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 De forma predeterminada, inStore incluye una lista de productos sugeridos en el carrito y en la página de producto.
 
-![inStore recommendation](https://images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
+![inStore recommendation](//images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
 
 Si desea ocultar las recomendaciones, es necesario editar los archivos `checkout-instore-custom.css` y `checkout-instore-custom.js` presentes en el administrador del Portal. Por tratarse de archivos utilizados en diversos flujos de uso de la aplicación, es importante que usted tenga conocimientos de programación antes de cambiarlos, para evitar la ruptura de otras funcionalidades.
 
diff --git a/docs/tracks/es/how-a-split-payment-transaction-works.md b/docs/tracks/es/how-a-split-payment-transaction-works.md
index f7e5a41ce..4c0861e29 100644
--- a/docs/tracks/es/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/es/how-a-split-payment-transaction-works.md
@@ -60,4 +60,4 @@ Aquellos USD 6,50 serían divididos entre el *marketplace* y adquirente. Como la
 
 Vea el siguiente gráfico: 
 
-![Split de pagos](https://images.ctfassets.net/alneenqid6w5/1VXR6E7dDgMTTSBM0D6qyL/2900b47ba92432068e940c185088399b/Split-ES.png)
+![Split de pagos](//images.ctfassets.net/alneenqid6w5/1VXR6E7dDgMTTSBM0D6qyL/2900b47ba92432068e940c185088399b/Split-ES.png)
diff --git a/docs/tracks/es/how-clustered-conditions-work.md b/docs/tracks/es/how-clustered-conditions-work.md
index ff903a858..b5fe5c0e4 100644
--- a/docs/tracks/es/how-clustered-conditions-work.md
+++ b/docs/tracks/es/how-clustered-conditions-work.md
@@ -26,7 +26,7 @@ De esta manera, las reglas de plazo y de pago en cuotas se aplicarán al consumi
 
 Para configurarlas, escoja una propiedad y, luego, seleccione los parámetros para crear un clúster.
 
-![Pagamentos Clusterizados_ES](https://images.ctfassets.net/alneenqid6w5/9VBsI8vnkYsrpnKIQLE6C/9c4af9336f284033455bc20a66ad9225/image.png)
+![Pagamentos Clusterizados_ES](//images.ctfassets.net/alneenqid6w5/9VBsI8vnkYsrpnKIQLE6C/9c4af9336f284033455bc20a66ad9225/image.png)
 
 ## Propiedad
 
diff --git a/docs/tracks/es/how-does-vtex-intelligent-search-work.md b/docs/tracks/es/how-does-vtex-intelligent-search-work.md
index ed419fc4d..0f7396f1a 100644
--- a/docs/tracks/es/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/es/how-does-vtex-intelligent-search-work.md
@@ -3,8 +3,8 @@ title: '¿Cómo funciona VTEX Intelligent Search?'
 id: 23mytRDsEduqLO0Lo7yufy
 status: PUBLISHED
 createdAt: 2020-03-05T14:57:22.014Z
-updatedAt: 2023-04-13T23:00:35.423Z
-publishedAt: 2023-04-13T23:00:35.423Z
+updatedAt: 2024-04-25T16:53:08.559Z
+publishedAt: 2024-04-25T16:53:08.559Z
 firstPublishedAt: 2020-03-05T19:54:00.932Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,95 +14,133 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
-El Motor de búsqueda es el centro de la inteligencia de VTEX Intelligent Search. Interpreta el término buscado y muestra la lista de productos filtrada y ordenada. Esta herramienta permite una búsqueda más objetiva, a través de la indexación y el tratamiento de los datos del catálogo.
+El motor de búsqueda es el centro de la inteligencia de VTEX Intelligent Search. Interpreta el término buscado y muestra la lista de productos filtrada y ordenada. Esta herramienta permite una búsqueda más objetiva, a través de la indexación y el tratamiento de los datos del catálogo.
 
-Esta funcionalidad es estándar de VTEX Intelligent Search y atiende a la mayoría de los escenarios. Sin embargo, el Motor de búsqueda también presenta algunos ajustes para perfeccionar el resultado de la búsqueda.
+Esta es una funcionalidad predeterminada de VTEX Intelligent Search y cubre a la mayoría de los escenarios. Sin embargo, el motor de búsqueda también presenta algunos ajustes para perfeccionar el resultado de la búsqueda. En esta guía describimos:
 
-Por lo tanto, hay un conjunto de configuraciones que alteran la lista y el orden de los productos mostrados en el resultado de la búsqueda. Estas son:
+* [Comportamiento predeterminado de la búsqueda](#comportamiento-predeterminado-de-la-busqueda)
+* [Configuración del comportamiento de la búsqueda](#configuracion-del-comportamiento-de-la-busqueda)
+* [Formas de búsqueda alternativas](#formas-de-busqueda-alternativas)
+* [Indexación](#indexacion)
 
-- __Definición de los campos de búsqueda__: define determinada información de producto como susceptible de búsqueda. A partir de la configuración, toda búsqueda realizada verifica el contenido de este campo para relacionarlo con los productos. Los campos __nombre del producto__, __marca__, __ProductID__, __ProductRefID__, __SKUID__, __SKURefID__ y __EAN__ están definidos de forma predeterminada y no pueden ser modificados. 
+## Comportamiento predeterminado de la búsqueda
 
-  Se puede encontrar un producto haciendo una búsqueda por caracteres especiales (`-` y `/`). 
+A continuación se describe el comportamiento predeterminado de Intelligent Search.
 
-  _Ejemplo_: se configuró que el campo «color» es configurable y el producto está registrado con el nombre «Zapatilla Nike Total 90» y con el color «negro». Si un cliente busca «Zapatilla Negra», la herramienta devolverá productos que tengan el término «zapatilla» y el color «negra» en la parte superior del resultado de búsqueda.
+### Autocorrección
 
-- __Definición y orden de los campos de filtro__: en todos los resultados de búsqueda se muestran filtros que el usuario puede seleccionar. Por estándar, algunos filtros ya están predeterminados, pero es posible crearlos según la necesidad de la tienda. Otro aspecto personalizable es el orden de visualización.
+El usuario puede cometer errores ortográficos al realizar una búsqueda. La herramienta interpreta los errores y muestra como resultados productos que se aproximen a la búsqueda realizada.
 
-  _Ejemplos_: Precio, Categorías y Marca.
+Para lograrlo, el motor de búsqueda intenta corregir las palabras ingresadas por el usuario de acuerdo con los ítems registrados en el catálogo. Para cada término de búsqueda se permite una cantidad específica de caracteres erróneos. Esta cantidad de errores aceptados se denomina _fuzzy_.
 
-- __Configuración de autocorrección__: el usuario puede cometer errores ortográficos al realizar una búsqueda. Es función de la herramienta interpretar estos errores y devolver como resultados los productos que se parezcan a la búsqueda realizada.
+El _fuzzy_ varía según el tamaño del término buscado. De forma predeterminada, si el término tiene de 3 a 5 caracteres, se aplica un _fuzzy_ de 1, es decir, se permite 1 carácter erróneo. A los términos de 6 caracteres o más, se aplica un _fuzzy_ de 2.
 
- Para esto, el Motor de búsqueda intenta corregir lo que el usuario digitó de acuerdo con los ítems registrados en el catálogo. Para cada término de búsqueda, se permite un número específico de caracteres incorrectos. Esta cantidad de errores aceptados se denomina *fuzzy*.
+Los errores previstos para los que se considera *fuzzy* = 1 son:
 
- El *fuzzy* varía dependiendo del tamaño del término de búsqueda. De forma predeterminada, si el término tiene de 3 a 5 caracteres, el *fuzzy* aplicado es 1, es decir, 1 carácter puede estar equivocado. Para términos de 6 caracteres o más, el *fuzzy* aplicado es 2.
+* Insertar 1 carácter demás.
+* Remover 1 carácter.
+* Cambiar 1 carácter.
+* Intercambiar 2 caracteres que estén una al lado del otro.
 
- Los errores previstos considerando ```*fuzzy* = 1``` son:
-   - Introducir 1 carácter extra.
-   - Eliminar 1 carácter.
-   - Intercambiar 1 carácter.
-   - Intercambiar 2 caracteres que estén uno al lado del otro.
+Ejemplo: un cliente desea buscar el término `bola`. Siguiendo la configuración predeterminada (*fuzzy* = 1 para términos de 3 a 5 caracteres), el motor de búsqueda muestra los resultados de `bola` para cualquier búsqueda que contenga los errores aceptados según se muestra a continuación:
 
- _Ejemplo_:
- Supongamos que un cliente quiere buscar el término «bola». Siguiendo la configuración predeterminada (```*fuzzy* = 1``` para términos de 3 a 5 caracteres), el Motor de búsqueda mostrará el resultado «bola» para cualquier búsqueda que contenga los errores aceptados, como:
-   - bolla (introducir 1 carácter extra)
-   - boa (eliminar 1 carácter)
-   - bora (cambiar 1 carácter)
-   - obla (intercambiar 2 caracteres que están uno al lado del otro entre ellos)
+* `bolla` (insertar 1 carácter de más)
+* `boa` (remover 1 carácter)
+* `bora` (cambiar 1 carácter)
+* `obla` (intercambiar 2 caracteres que estén uno al lado del otro)
 
- <div class="alert alert-info" role="alert">
-<p> Los espacios en blanco no se consideran en fuzzy, por lo que "base ball" no se corregirá a "baseball". Recomendamos utilizar sinónimos para estos casos.</p>
+<div class ="alert alert-info">
+	<p>El <em>fuzzy</em> no considera los espacios en blanco. Esto quiere decir que, por ejemplo, <code>base ball</code> no se corregiría a <code>baseball</code>. Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinónimos</a> en estos casos.</p>
 </div>
 
-- __Configuración de relevancia__: funcionalidad que define el orden de los productos en el resultado de búsqueda. Esta configuración permite asignar pesos y priorizar determinados criterios utilizados por el Motor de búsqueda, como popularidad, fecha de lanzamiento del producto y participación en promociones, por ejemplo. La relevancia de un producto está conformada por la combinación de los pesos y prioridades definidos por cada administrador de tienda. 
+### Resultado mínimo
 
- _Ejemplo_: un administrador de tienda configuró que el criterio «promoción» tiene una mayor relevancia que otros criterios. Así, cuando un cliente busca «camiseta» en la búsqueda interna de la tienda, las camisetas incluidas en las promociones tienden a aparecer en primer lugar en los resultados, dependiendo del peso asignado a los demás criterios.
+La cantidad mínima de resultados mostrados para cualquier búsqueda realizada es 1. Si no se encuentra el número mínimo de resultados, se aplica [autocorrección](#autocorreccion).
 
- Para obtener más información sobre como personalizar el orden de los resultados de acuerdo con las necesidades de su tienda, lea el artículo [Configuración de relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+En las búsquedas que contienen varios términos, se aplica la siguiente lógica:
 
-- __Configuración de resultado mínimo__: permite configurar la cantidad mínima de productos para la consulta de múltiples términos. Si no se alcanza este número, la búsqueda presenta resultados más amplios, que respetan solo uno de los términos buscados.
+Si no se devuelve la cantidad mínima de resultados con la autocorrección inicial, la búsqueda comienza a incluir resultados más amplios que contengan cualquiera de los términos buscados. Por ejemplo, cuando un usuario busca “zapatilla nike” pero el catálogo no tiene ningún producto con ese nombre, la búsqueda puede mostrar como resultado un producto que contenga solo “zapatilla” en el nombre.
+Si la búsqueda más amplia no devuelve la cantidad de resultados mínima, se repetirá la autocorrección nuevamente en cada uno de los términos.
 
-  _Ejemplo_: se configuró que el resultado mínimo para consultas con múltiples términos es __tres__.  El usuario realizó la búsqueda de «zapatilla nike», pero el catálogo solo tiene __cuatro__ productos con ese nombre. La plataforma presentará primero productos que tengan el término «zapatilla nike», luego productos con el término «zapatilla» y, por último, aquellos que tengan el término «nike».
+<div class= "alert alert-warning">
+<p>Las búsquedas que contienen varios términos son más eficientes cuando el cliente ordena los resultados por relevancia, ya que pueden devolver un número mayor de resultados más allá del contexto de búsqueda inicial. En el orden por relevancia también pueden priorizarse ítems relacionados con cada término. Por otro lado, cuando se aplican otros criterios, como precio o más vendidos, el orden de los resultados depende de los valores numéricos y no necesariamente prioriza ítems que contienen más palabras.</p>
+</div>
+
+### Límite de paginación
+
+VTEX Intelligent Search limita los resultados de búsqueda a 50 páginas. Este límite incentiva el uso de filtros para hacer que la navegación sea más relevante y enfocada para el usuario.
+
+## Configuración del comportamiento de la búsqueda
+
+Hay un conjunto de ajustes que alteran la lista y el orden de los productos mostrados en el resultado de la búsqueda. En las siguientes secciones se presentan las principales definiciones que afectan el comportamiento de la búsqueda.
+
+### Definición de los campos de búsqueda
 
-- __Límite de páginas__: limita el resultado de la búsqueda a 50 páginas. Este límite fomenta el uso de filtros, lo que permite una navegación más relevante y centrada para el usuario.
+Determina la información de producto que se puede buscar. A partir de la configuración, toda búsqueda realizada en la barra de búsqueda verifica el contenido de este campo para generar resultados de búsqueda. Consulta la tabla a continuación para saber qué información permite la realización de búsquedas de forma predeterminada y ver las otras opciones de configuración:
+
+| Información | Configuración |
+| - | - |
+| Nombre del producto, marca, ID de producto (`ProductID`), código de referencia del producto (`ProductRefID`), ID del SKU (`SKUID`), código de referencia del SKU (`SKURefID`) y EAN | Se pueden realizar búsquedas en estos datos de forma predeterminada en VTEX Intelligent Search. Para remover alguno de ellos, ponte en contacto con nuestro [Soporte](https://help.vtex.com/es/support). |
+| Especificaciones de producto y SKU | Para incluir las especificaciones deseadas como campos que se pueden buscar, debes configurar la opción __Especificaciones buscables__ en el Admin VTEX a través de __Configuración de la tienda__ > __Intelligent Search__ > __Configuración de la búsqueda__. <br /><br /> Por ejemplo, si una camisa no tiene el color en el nombre del producto o del SKU, de forma predeterminada, Intelligent Search no identifica ese atributo cuando se busque “camisa azul” y devolverá como resultado camisas de diferentes colores. Sin embargo, si la especificación de color se configura de manera que se pueden realizar búsquedas sobre la especificación de color, la búsqueda podrá devolver camisas azules en las primeras posiciones. <br /><br /> Para más detalles sobre la definición de especificaciones buscables, accede a la guía [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#configuracion-general). Puedes ver más información sobre especificaciones en [Especificaciones de producto y SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP). |
+| Código del fabricante (`ManufactureID`) | Ponte en contacto con nuestro [Soporte](https://help.vtex.com/es/support) para configurar la realización de búsquedas en este campo. |
+
+Ejemplo: se configuró que la especificación “color” se puede buscar y el producto está registrado con el nombre “Zapatilla Nike Total 90” y con el color “negro”. Si un cliente busca “Zapatilla Negra”, la herramienta devolverá productos que tengan el término “zapatilla” y el color “negra” en la parte superior del resultado de búsqueda.
+
+Se puede encontrar un producto realizando una búsqueda por caracteres especiales (`-` y `/`).
 
 <div class="alert alert-warning">
-  <p>VTEX Intelligent Search no ofrece la funcionalidad de sustitución de palabras de forma nativa. Para habilitar el uso de palabras sustitutivas por parte de VTEX Intelligent Search, póngase en contacto con <a href="https://support.vtex.com/hc/es-419/requests">nuestro equipo de soporte</a>.</p>
+	<p>La selección de los campos de búsqueda afecta las posibilidades de las <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">reglas de merchandising</a>, ya que solo se pueden utilizar los campos que permiten búsquedas para configurar reglas. Por ejemplo, al definir solo el campo <code>SKUID</code> para búsquedas, no se podrá promover un <code>ProductID</code> o un <code>ProductRefID</code> utilizando reglas de merchandising.</p>
+</div>
+
+### Definición y orden de los campos de filtro
+
+En todos los resultados de búsqueda se muestran filtros que el usuario puede seleccionar. De forma predeterminada, algunos filtros ya están predefinidos, pero es posible crearlos según la necesidad de la tienda. Otro aspecto personalizable es el orden de visualización. Ejemplo: en una lista de resultados de búsqueda puede incluir filtros como Precio, Categorías y Marca.
+
+### Configuración de relevancia
+
+La relevancia es la funcionalidad que define el orden de los productos en el resultado de búsqueda. Esta configuración permite asignar pesos y priorizar determinados criterios utilizados por el motor de búsqueda, como popularidad, fecha de lanzamiento del producto y participación en promociones. La relevancia de un producto está compuesta por la combinación de los pesos y prioridades definidos por cada administrador de la tienda.
+
+Ejemplo: un administrador de la tienda configuró que el criterio “promoción” tiene una mayor relevancia que otros criterios. Así, cuando un cliente busca “camiseta” en la búsqueda interna de la tienda, las camisetas incluidas en las promociones tienden a aparecer en primer lugar en los resultados, dependiendo del peso asignado a los demás criterios.
+
+Para obtener más información sobre cómo personalizar el orden de los resultados de acuerdo con las necesidades de tu tienda, consulta el artículo [Configuración de relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+<div class="alert alert-info">
+	<p>Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Si utilizas el comando <code>map=productClusterIds</code>, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con su propio criterio de relevancia. Si eliges utilizar <code>productClusterNames</code>, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search.</p>
 </div>
 
 ## Formas alternativas de búsqueda
 
-Es posible buscar ID en la URL de la tienda o directo en la barra de búsqueda. En dicha búsqueda, puedes buscar un solo ítem o una lista de ítems.
+Es posible buscar el ID de uno o varios artículos en la barra de búsqueda o añadiendo parámetros de consulta (*query*) a la URL de la tienda.
 
-Para buscar en la URL de tu tienda, sigue el formato a continuación:
+### Coincidencia parcial
 
-- Ejemplo de búsqueda de un ítem: `[dirección de la cuenta]/[tipo de id]:[id_1]?q=[tipo de id]&map=ft`
-- Ejemplo de búsqueda de lista: `[dirección de la cuenta]/[tipo de id]:[id_1];[id_2];[id_3]?q=[tipo de id]:[id_1];[id_2];[id_3]&map=ft`
+Al ingresar únicamente los primeros dígitos exactos del ID del producto (`ProductID`), código de referencia del producto (`ProductRefID`), ID del SKU (`SKUID`), código de referencia del SKU (`SKURefID`) o EAN en la barra de búsqueda, Intelligent Search hará un match parcial con productos y SKU activos en la tienda, incluyéndolos en los resultados de la búsqueda.
 
-Los posibles tipos de valores para el campo tipo de ID son `product.id`, `sku.id`,`sku.ean`, `sku.reference` o `id` (ProductID, ProductRefID, SKUID, SKURefID y EAN). Cabe resaltar que todos los ID deben ser del mismo tipo.
+Por ejemplo, si el ID del producto es `123456789` y la búsqueda realizada es `123`, ese producto se mostrará entre los resultados; sin embargo, si la búsqueda es `234`, sin alguno de los primeros dígitos del ID, este producto no se mostrará.
 
-Puedes buscar IDs en la barra de búsqueda de las siguientes maneras:
+### URL
 
-1. Introduciendo solo los primeros dígitos del ID en la barra de búsqueda. Es importante tener en cuenta que la busca debe ser exacta, por ejemplo, si el ID es `0123-456-789` y buscas `123`, el producto no será mostrado.
-2. Por consultas, siguiendo el formato a continuación:
-  - **Búsqueda por ID de SKU:** `?q=sku.id:<id>` o `?q=sku:<id>`
-  - **Búsqueda por EAN:** `?q=sku.ean:<id>`
-  - **Búsqueda por ID de referencia:** `?q=sku.reference:<id>`
-  - **Búsqueda por slug:** `?q=product.link:<link>`
-  - **Búsqueda por ID de producto:** `?q=product:<id>` o `?q=product.id:<id>`
+Para buscar desde la URL de tu tienda, añade parámetros de búsqueda (_query_) al final de la URL de la tienda, respetando una de las siguientes estructuras:
 
-## Indexación
+* Ejemplo de búsqueda de un ítem: `[dirección de la cuenta]/[tipo de id]:[id_1]?q=[tipo de id]&map=ft`
+* Ejemplo de búsqueda de lista: `[dirección de la cuenta]/[tipo de id]:[id_1];[id_2];[id_3]?q=[tipo de id]:[id_1];[id_2];[id_3]&map=ft`
 
-La indexación es un proceso de sincronía entre los catálogos de la tienda y la búsqueda. Esta funcionalidad permite una actualización continua del índice de productos. Además, ejecuta un tratamiento de datos para utilizarlos en la búsqueda.
+Los posibles tipos de valores para el campo “tipo de ID” son `product.id`, `sku.id`, `sku.ean`, `sku.reference` o `id` (ProductID, ProductRefID, SKUID, SKURefID y EAN). Cabe resaltar que todos los ID deben ser del mismo tipo.
 
-Inicialmente, se realiza una sincronización con todos los productos del catálogo VTEX del cliente. Después, el indexador de búsqueda recibirá en tiempo real las futuras actualizaciones de datos, como el nombre y el status del producto. 
+* **Búsqueda por ID de SKU:** `?q=sku.id:<id>` o `?q=sku:<id>`
+* **Búsqueda por EAN:** `?q=sku.ean:<id>`
+* **Búsqueda por ID de referencia:** `?q=sku.reference:<id>`
+* **Búsqueda por slug:** `?q=product.link:<link>`
+* **Búsqueda por ID de producto:** `?q=product:<id>` o `?q=product.id:<id>`
 
-En este proceso de sincronía, el sistema forma una fila de la información que se ha actualizado para indexarlas en el catálogo de búsqueda. Una vez que se hayan indexado todos los cambios, estarán disponibles en el sitio web. 
+## Indexación
 
-El proceso de indexación es seguro y cuenta con reglas de recuperación: si un ítem no se indexa en el primer intento, el sistema realiza más intentos.
+La indexación es un proceso de sincronía entre los catálogos de la tienda y la búsqueda. Esta funcionalidad permite una actualización continua del índice de productos. Además, ejecuta un tratamiento de datos para utilizarlos en la búsqueda.
 
-La indexación es muy importante para analizar, tratar y organizar los datos de la mejor manera para que se muestren en los resultados.
+Inicialmente, se realiza una sincronización con todos los productos del catálogo VTEX del cliente. Después, el indexador de búsqueda recibirá en tiempo real las futuras actualizaciones de datos, como el nombre y el status del producto.
 
-<div class="alert alert-info" role="alert">
-<p>Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Al utilizar el comando `map=productClusterIds`, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con sus propios criterios de relevancia. Si eliges utilizar `productClusterNames`, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search. </p>
-</div>
+En este proceso de sincronía, el sistema forma una fila con la información que se ha actualizado para indexarlas en el catálogo de búsqueda. Una vez que se hayan indexado todos los cambios, estarán disponibles en el sitio web.
+
+El proceso de indexación es seguro y cuenta con reglas de recuperación: si un ítem no se indexa en el primer intento, el sistema realiza más intentos. La indexación también es muy importante para analizar, tratar y organizar los datos de la mejor manera para que se muestren en los resultados.
 
+Consulta [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) para ver más información sobre cómo monitorear el proceso de indexación.
diff --git a/docs/tracks/es/how-message-center-works.md b/docs/tracks/es/how-message-center-works.md
index 276edd55f..8557a9009 100644
--- a/docs/tracks/es/how-message-center-works.md
+++ b/docs/tracks/es/how-message-center-works.md
@@ -43,7 +43,7 @@ Al entrar en el Message Center y hacer clic en __Templates__, encontrará una li
 
 Comprendamos la información presente en estos cards.
 
-![Emails 1 1](https://images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
+![Emails 1 1](//images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
 
 - Nombre del template para identificación interna. Este *no* es el asunto del correo electrónico.  
 - Aplicación o módulo al que pertenece el template, indicado en verde.  
@@ -53,7 +53,7 @@ Comprendamos la información presente en estos cards.
   
 Para buscar templates, puede utilizar filtros por aplicación (módulo) y tipo (mensaje estándar o personalizado).
 
-![Emails 1 2](https://images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
+![Emails 1 2](//images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
 
 ### Remitentes
 
@@ -61,7 +61,7 @@ Aquí, el usuario verifica y edita la información - nombre, correo electrónico
 
 Esta es la información que se muestra en los cards de los remitentes:
 
-![Emails 1 3](https://images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
+![Emails 1 3](//images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
 
 - Nombre del remitente, para identificación interna.  
 - Tipo de servidor SMTP, que puede ser de VTEX o de la propia tienda.  
diff --git a/docs/tracks/es/how-the-payments-module-works.md b/docs/tracks/es/how-the-payments-module-works.md
index 8a4b0acf5..1010e5493 100644
--- a/docs/tracks/es/how-the-payments-module-works.md
+++ b/docs/tracks/es/how-the-payments-module-works.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona el módulo de pagos '
 id: kdPbEIWf8Xq8tESQvViMB
 status: PUBLISHED
 createdAt: 2019-11-13T18:30:00.279Z
-updatedAt: 2021-09-21T14:41:47.003Z
-publishedAt: 2021-09-21T14:41:47.003Z
+updatedAt: 2024-07-24T18:38:45.637Z
+publishedAt: 2024-07-24T18:38:45.637Z
 firstPublishedAt: 2019-11-21T22:49:51.417Z
 contentType: trackArticle
 productTeam: Financial
@@ -24,39 +24,39 @@ Es importante recordar que cada tienda tiene sus particularidades y su propio fu
 
 ## Gateway 
 
-Un gateway (también llamado gateway de pago) es un _sistema que efectúa la transmisión de los datos de las compras realizadas en su tienda en el momento del checkout_. 
+Un gateway (también llamado gateway de pago) es un sistema que efectúa la transmisión de los datos de las compras realizadas en su tienda en el momento del checkout. 
 
 Como primer player del flujo, es responsable de enviar la información de pago recibida en el checkout a los actores financieros que integran la secuencia del flujo de pago (como adquirentes, banderas y bancos emisores). 
 
 En seguida, obtiene una respuesta sobre la aprobación del pago y continuación del flujo de compra, o su cancelación.  
 
-Como agentes intermediarios entre un e-commerce y sus medios de pago, los **gateways** _actúan como un terminal_, integrando en un solo lugar todos los movimientos realizados entre los players del flujo de pago.  
+Como agentes intermediarios entre un e-commerce y sus medios de pago, los **gateways** actúan como un terminal, integrando en un solo lugar todos los movimientos realizados entre los players del flujo de pago.  
 
-> Ejemplos de gateway: Braspag y Mundipagg.
+Ejemplos de gateway: Pagar.me y Stripe.
 
 ## Adquirente 
-Un adquirente (también llamado de acreditador) es una _empresa especializada en procesar pagos_; es decir, hacer la liquidación financiera de las transacciones de una tienda por medio de tarjetas de crédito y débito. 
+Un adquirente (también llamado de acreditador) es una empresa especializada en procesar pagos; es decir, hacer la liquidación financiera de las transacciones de una tienda por medio de tarjetas de crédito y débito. 
 
 A través de su red de socios acreditados (o red de adquirencia), permite que una tienda ofrezca diversas condiciones de pago a sus clientes. En la práctica, el **adquirente** recibe la información del pago, la procesa y la transmite a la bandera y al banco emisor. 
 
 Cuando todo está en orden y una compra es autorizada por los otros players del flujo de compra, el adquirente es responsable de transferir los valores (cobrados del cliente por el banco emisor) a la cuenta de su tienda.
 
-> Ejemplos de adquirente: Rede, Cielo, GetNet y Stone.  
+Ejemplos de adquirente: Rede, Cielo, GetNet y Stone.  
 
 ## Subadquirente  
 
-Un subadquirente es una _empresa que procesa pagos y transmite su información a los otros players involucrados en el flujo de pago_. 
+Un subadquirente es una empresa que procesa pagos y transmite su información a los otros players involucrados en el flujo de pago. 
 
 Como facilitador, su papel es semejante al de un adquirente, pero no lo sustituye por completo por su falta de autonomía para desempeñar todas las funcionalidades de un adquirente.
 
 Así, el **subadquirente** puede ser entendido como una especie de intermediario entre adquirente y tienda. 
 
-> Ejemplos de subadquirente: Paypal y PagSeguro.
+Ejemplos de subadquirente: Paypal y PagSeguro.
 
 Para saber más sobre las [ventajas y desventajas de incluir a un subadquirente en su flujo](https://help.vtex.com/es/tutorial/diferenca-entre-adquirentes-subadquirentes-e-gateways-no-brasil?locale=pt "Atores financeiros"), consulte nuestro artículo.   
 
 ## Bandera de la Tarjeta 
-Banderas son _empresas responsables de definir las reglas de negocio para compras realizadas con tarjeta de crédito_, como la cantidad de cuotas en que puede dividir el pago y el número de establecimientos en que se acepta, nacional e internacionalmente. 
+Banderas son empresas responsables de definir las reglas de negocio para compras realizadas con tarjeta de crédito, como la cantidad de cuotas en que puede dividir el pago y el número de establecimientos en que se acepta, nacional e internacionalmente. 
 
 Son estas las que definen los estándares por los que los adquirentes deben procesar las transacciones realizadas por ese medio de pago. 
 
@@ -64,27 +64,27 @@ En el flujo de pago por tarjeta de crédito, la **bandera** recibe del adquirent
 
 De esta forma, la bandera sirve tanto para regular el uso de la tarjeta, así como un puente entre adquirente y banco.
 
-> Ejemplos de banderas de  tarjeta: Mastercard, American Express y Visa.
+Ejemplos de banderas de  tarjeta: Mastercard, American Express y Visa.
 
 ## Banco Emisor
-El Banco Emisor es la _institución financiera responsable de los medios de pago, ya sean boletos bancarios, tarjetas de débito o de crédito_. 
+El Banco Emisor es la institución financiera responsable de los medios de pago, ya sean boletos bancarios, tarjetas de débito o de crédito. 
 
 Es este quien, al recibir los datos de una compra hecha en su tienda, va a autorizar o no la venta (dependiendo del límite de crédito o del dinero disponible en la cuenta del usuario). 
 
 En VTEX, es posible configurar las condiciones especiales para pagos realizados a través de **bancos** específicos, funcionalidad que exploraremos más adelante. 
 
-> Ejemplos de bancos emisores:  Itaú, Santander, Bradesco y Citibank.  
+Ejemplos de bancos emisores:  Itaú, Santander, Bradesco y Citibank.  
 
 ## Antifraude  
-El antifraude es un _sistema especializado en analizar las compras realizadas en los sitios web, con el objetivo de identificar operaciones fraudulentas_. 
+El antifraude es un sistema especializado en analizar las compras realizadas en los sitios web, con el objetivo de identificar operaciones fraudulentas. 
 
 Recolecta datos sobre el comportamiento de los usuarios y los compara con patrones sospechosos para, entonces,  aprobar o no el pedido. Así, el **antifraude** añade una capa más de seguridad para su tienda.
 
-> Ejemplos de antifraudes:  ClearSale y Konduto.  
+Ejemplos de antifraudes:  ClearSale y Konduto.  
 
 ## Certificación PCI SSC
-El PCI Security Standards Council es un _foro mundial abierto para el continuo desarrollo, mejora, almacenamiento, difusión e implementación de normas de seguridad para la protección de datos_. 
+El PCI Security Standards Council es un foro mundial abierto para el continuo desarrollo, mejora, almacenamiento, difusión e implementación de normas de seguridad para la protección de datos. 
 
 [La plataforma VTEX posee un gateway propio con **certificación PCI**](https://help.vtex.com/es/tutorial/que-es-el-pci-ssc--4jo3Vkox3amSO2w4qIWa0E "PCI SSC"), que  significa que los datos de todos los pagos realizados en su tienda están protegidos de acuerdo con los más altos estándares de seguridad. 
 
-> Si desea profundizar los conceptos de gateway, adquirente, subadquirente, bandera, banco emisor y antifraude, consulte nuestro [artículo sobre agentes financieros en Brasil](https://help.vtex.com/es/tutorial/diferenca-entre-adquirentes-subadquirentes-e-gateways-no-brasil?locale=pt "Agentes financeiros ").
+Si desea profundizar los conceptos de gateway, adquirente, subadquirente, bandera, banco emisor y antifraude, consulte nuestro [artículo sobre agentes financieros en Brasil](https://help.vtex.com/es/tutorial/diferenca-entre-adquirentes-subadquirentes-e-gateways-no-brasil?locale=pt "Agentes financeiros ").
diff --git a/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md b/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md
index 77b680b94..3849fe664 100644
--- a/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md
+++ b/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 Si usted ha configurado su tienda utilizando el flujo de __Easy Setup__ ya se ha creado una tienda en el __Admin de tiendas__ dentro del VTable de VTEX (https://{{AccountName}}.myvtex.com/admin/vtable).
 
-![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Haga clic en __Admin de tiendas__ para abrir la tabla donde usted verá las tiendas físicas.
 
@@ -24,7 +24,7 @@ Si no ha utilizado el __Easy Setup__ y así no ve ninguna tienda registrada, cre
 
 Si ya ha registrado una tienda a través de __Easy Setup__, verá el registro de esta tienda creada como en la siguiente imagen.
 
-![vtable-admin-das-lojas-2](https://images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
+![vtable-admin-das-lojas-2](//images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
 
 Para cambiar cualquier dato, incluso la política comercial de la tienda, basta con cambiar la celda relacionada y luego hacer clic en el botón __Guardar__.
 
diff --git a/docs/tracks/es/how-to-configure-a-custom-payment.md b/docs/tracks/es/how-to-configure-a-custom-payment.md
index 91317afcf..fc3b0f0b4 100644
--- a/docs/tracks/es/how-to-configure-a-custom-payment.md
+++ b/docs/tracks/es/how-to-configure-a-custom-payment.md
@@ -3,8 +3,8 @@ title: 'Configurar pagos personalizados '
 id: 1wWt35dRwEboRs1nrSx7G0
 status: PUBLISHED
 createdAt: 2019-11-12T14:02:06.237Z
-updatedAt: 2023-03-21T19:57:00.742Z
-publishedAt: 2023-03-21T19:57:00.742Z
+updatedAt: 2023-10-18T14:41:42.080Z
+publishedAt: 2023-10-18T14:41:42.080Z
 firstPublishedAt: 2019-11-25T15:33:37.696Z
 contentType: trackArticle
 productTeam: Financial
@@ -36,7 +36,7 @@ Le permite usar una tarjeta de crédito de la tienda con una de las siguientes b
 3. Seleccione una de las opciones de pago personalizado.
 4. Complete los campos del formulario y haga clic en **Guardar**.
 
-![PT Pagamento Customizado](https://images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
+![PT Pagamento Customizado](//images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
 
 Después de esta configuración, deberá crear la [Condición de pago](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento/).  
 
diff --git a/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
index 50b4c0492..a3b6d4f11 100644
--- a/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 Dentro de las opciones que ofrece **inStore** al momento de completar una venta, se encuentra una que permite imprimir el resumen del pedido.
 
-![ES-Venda confirmada](https://images.ctfassets.net/alneenqid6w5/54Z1ETTtBXkSxJsWu16UKV/fe90bb4197cce83777fd9f4fee75bbd7/ES-Venda_confirmada.png)
+![ES-Venda confirmada](//images.ctfassets.net/alneenqid6w5/54Z1ETTtBXkSxJsWu16UKV/fe90bb4197cce83777fd9f4fee75bbd7/ES-Venda_confirmada.png)
 
 Para configurar esta opción, serán necesarios dos pequeños pasos:
   1. Por el Admin VTEX, active la opción de configuración del dispositivo en el menú inStore.
@@ -29,7 +29,7 @@ Hoy, esta configuración está presente en el administrador del portal, más esp
 Para habilitar la opción _“Configurar dispositivo”_, debe encontrar el objeto **_window.INSTORE_CONFIG_** presente en este archivo y agregar la propiedad **_configureDeviceEnabled_** con el valor **_true_** y también agregar el objeto **_printingConfig_** a la propiedad **_printByBroker_** con el valor true, para que inStore permita utilizar la propiedad opción dentro del menú, como se muestra en la imagen de ejemplo a continuación:
 
 
-![ES-Configurar dispositivo](https://images.ctfassets.net/alneenqid6w5/5alZn4GuAJkvZkEW7PkQE/5aef5e117ba6a20ae8ba6438e23e0f91/ES-Configurar_dispositivo.png)
+![ES-Configurar dispositivo](//images.ctfassets.net/alneenqid6w5/5alZn4GuAJkvZkEW7PkQE/5aef5e117ba6a20ae8ba6438e23e0f91/ES-Configurar_dispositivo.png)
 
 No elimine ninguna de las otras propiedades presentes en este objeto, pero el resultado debería ser algo como:
 
@@ -64,11 +64,11 @@ printPageAutomatically: true
   2. Abra la aplicación inStore y entre a la tienda donde desea configurar la impresora.
   3. En el menú de inStore, en el bloque de “Configuraciones”, deberá aparecer la opción “Configurar dispositivo”. Haga clic allí.
 
-![ES-Barra inStore](https://images.ctfassets.net/alneenqid6w5/1sluYEwdo4f01KnUyyEsoa/19344feb059bd03b316c37e2caed9ae0/ES-Barra_inStore.png)
+![ES-Barra inStore](//images.ctfassets.net/alneenqid6w5/1sluYEwdo4f01KnUyyEsoa/19344feb059bd03b316c37e2caed9ae0/ES-Barra_inStore.png)
 
   4. Va a encontrar el resumen del dispositivo configurado. En caso de que sea la primera vez, las informaciones estarán vacías o, si ya se ha configurado un dispositivo previamente, van a aparecer algunas informaciones sobre el dispositivo _(Nombre del dispositivo e Impresora estándar)_. Haga clic en la opción “Editar”.
 
-![ES-Dispositivo via Broadcast](https://images.ctfassets.net/alneenqid6w5/4KoNSOz0DB2KvXEyYcBiCd/668bc635360f6934f604ad1e53defddd/ES-Dispositivo_via_Broadcast.png)
+![ES-Dispositivo via Broadcast](//images.ctfassets.net/alneenqid6w5/4KoNSOz0DB2KvXEyYcBiCd/668bc635360f6934f604ad1e53defddd/ES-Dispositivo_via_Broadcast.png)
 
   5. Aparecerá un formulario indicando los datos de _AppKey_,  _AppToken_ y el nombre con el que desee identificar el dispositivo. Luego de ingresar estos datos, haga clic en “Configurar”.
   6. Por último, al incluir los datos anteriores, será posible seleccionar la impresora en la lista de opciones. La idea es que sea seleccionada una de esas opciones y haga clic en “Configurar” nuevamente.
diff --git a/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
index f29ebd872..2c7967eb0 100644
--- a/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
@@ -3,8 +3,8 @@ title: 'Crear o editar template de correo electrónico transaccional'
 id: 335JZKUYgvYlGOJgvJYxRO
 status: PUBLISHED
 createdAt: 2020-01-10T13:13:48.069Z
-updatedAt: 2021-02-11T13:19:34.511Z
-publishedAt: 2021-02-11T13:19:34.511Z
+updatedAt: 2024-06-11T19:54:28.554Z
+publishedAt: 2024-06-11T19:54:28.554Z
 firstPublishedAt: 2020-01-13T14:38:32.506Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -23,6 +23,10 @@ Para editar un template de correo electrónico transaccional, siga los pasos a c
 3. Altere el título del correo electrónico y el destinatario (los valores entre llaves dobles son variables; en el próximo artículo aprenderemos cómo manejarlas). Usted puede incluir destinatarios en copia (`CC`) y copia oculta (`CCO`).
 4. Deje el flag __Utilizar remitente estándar__ para hacer uso de la dirección de correo electrónico registrado como estándar, como se explica en el artículo anterior de esta guía.
 
+<div class = "alert alert-info">
+La lista de plantillas está disponible en el artículo <a href="https://help.vtex.com/es/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">Plantillas de correo electrónico transaccional relacionadas con el pedido</a>.
+</div>
+
 Es en el campo __HTML__ donde encuentra el código HTML del template. Puede editar el código en el propio campo o copiarlo en el editor de su preferencia, editarlo y luego pegarlo nuevamente en el campo del template.
 
 El __preview__ renderizado por este código se muestra en el box justo debajo. Puede seleccionar tres tamaños de pantalla diferentes para probar la responsividad del código.
diff --git a/docs/tracks/es/how-vtex-support-works.md b/docs/tracks/es/how-vtex-support-works.md
new file mode 100644
index 000000000..2ac57d2b0
--- /dev/null
+++ b/docs/tracks/es/how-vtex-support-works.md
@@ -0,0 +1,42 @@
+---
+title: 'Funcionamiento del soporte VTEX'
+id: 2Ik9CGbPeZIHHaYFsuyId3
+status: PUBLISHED
+createdAt: 2024-02-20T21:27:52.565Z
+updatedAt: 2024-02-22T14:09:20.551Z
+publishedAt: 2024-02-22T14:09:20.551Z
+firstPublishedAt: 2024-02-22T14:09:20.551Z
+contentType: trackArticle
+productTeam: Others
+slug: funcionamiento-del-soporte-vtex
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+El soporte VTEX se presta online y permite abrir tickets con distintos niveles de prioridad, en función de la región de operación de la tienda. La apertura de tickets se realiza a través de la [página de soporte](https://help.vtex.com/es/support) y requiere [autenticación de la cuenta del usuario](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz#definir-roles-y-permisos-para-los-usuarios). Hay tres métodos de autenticación disponibles:
+
+- Token recibido en el email registrado en la tienda.
+- Inicio de sesión usando la cuenta de Google.
+- Email y contraseña con autenticación de dos factores mediante aplicación o SMS.
+
+<div class = "alert alert-warning">
+Para obtener la autorización de autenticación, el <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512">usuario </a> <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol </a> asociado con <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos de License Manager. </a>
+</div>
+
+El soporte VTEX está dividido en regiones, y cada región tiene su propio acuerdo de nivel de servicio (SLA), prioridad y disponibilidad del equipo de Customer Excellence (CX) para aquella determinada región. Las regiones donde hay servicio de soporte son las siguientes:
+
+- Brasil
+- América Latina (LATAM, excepto Brasil)
+- Asia-Pacífico (APAC)
+- Estados Unidos (EE. UU.)
+- Europa, Oriente Medio y África (EMEA)
+
+La tabla a continuación ofrece una visión general de los principales artículos del Help Center por región:
+
+| **Región**     | **Artículo del Help Center**    |
+|----------------|---------------------------------|
+| Global         | **Artículo:** [¿Cómo funciona el soporte de VTEX?](https://help.vtex.com/es/faq/como-funciona-el-soporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe)<br.<br>Presenta cómo funciona el soporte a nivel global, incluyendo la gestión de tickets, planes regionales, encuesta de satisfacción y servicios como monitoreo y recursos disponibles como Help Center, Developer Portal y anuncios de actualizaciones de la plataforma. |
+| Solo Brasil    | **Articulo:** [Soporte VTEX - Brasil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)<br><br>  Presenta la disponibilidad, el SLA y los recursos disponibles para clientes en Brasil. |
+| Solo Estados Unidos  | **Artículo:** [Soporte VTEX - Estados unidos](https://help.vtex.com/en/faq/vtex-support-united-states--Bm45YFp68QRe1Z5r2oa07)<br><br> Presenta la disponibilidad, el SLA y los recursos disponibles para clientes en Estados Unidos. Disponible solamente en inglés. |
+| Solo Europa, Oriente Medio y África (EMEA) | **Artículo:** [Soporte VTEX - EMEA](https://help.vtex.com/en/faq/vtex-support-emea--5ePu2qkCfmE0IEKDFKg53F)<br><br> Presenta la disponibilidad, el SLA y los recursos disponibles para clientes en la región de EMEA. Disponible solamente en inglés. |
diff --git a/docs/tracks/es/including-order-variables-in-email-template.md b/docs/tracks/es/including-order-variables-in-email-template.md
index 88578d278..aaf183022 100644
--- a/docs/tracks/es/including-order-variables-in-email-template.md
+++ b/docs/tracks/es/including-order-variables-in-email-template.md
@@ -30,7 +30,7 @@ Supongamos que desea ingresar el nombre de la transportadora en el correo electr
 
 Para hacer esto, entre en el template de pedido enviado y, en el campo __JSON Data__, busque la propiedad `courier`.
 
-![EN Incluir variáveis do pedido no template de e-mail - 1](https://images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/a8060a2a2c8dca9887178af7d6c97812/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)  
+![EN Incluir variáveis do pedido no template de e-mail - 1](//images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/a8060a2a2c8dca9887178af7d6c97812/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)  
 
 El valor ingresado para esta propiedad es apenas un ejemplo, pero puede usarlo en el campo __HTML__ para que, cuando se envíe el correo electrónico, el cliente vea la transportadora de hecho responsable de entregar el pedido.
 
@@ -39,7 +39,7 @@ Tenga en cuenta que la propiedad `courier` está dentro del objeto `package`. Po
 `{{package.courier}}`
 
 
-![EN Incluir variáveis do pedido no template de e-mail - 2](https://images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/f3e8ee4de1d2a5d5a46c0385660a9c67/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)  
+![EN Incluir variáveis do pedido no template de e-mail - 2](//images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/f3e8ee4de1d2a5d5a46c0385660a9c67/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)  
 
 
 Vea que el valor de ejemplo  ("Transportadora Teste Courier S.A.") fue ingresado en la pantalla de preview, debajo de los campos __HTML__ y __JSON Data__. 
diff --git a/docs/tracks/es/indexing-history.md b/docs/tracks/es/indexing-history.md
new file mode 100644
index 000000000..2781b2d91
--- /dev/null
+++ b/docs/tracks/es/indexing-history.md
@@ -0,0 +1,66 @@
+---
+title: 'Historial de indexación'
+id: 4flMwTaQL8FRKl1YT58ezH
+status: PUBLISHED
+createdAt: 2020-04-14T13:33:20.167Z
+updatedAt: 2023-07-13T19:35:40.455Z
+publishedAt: 2023-07-13T19:35:40.455Z
+firstPublishedAt: 2020-04-14T23:55:09.210Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: historial-de-indexacion
+locale: es
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugES: vtex-intelligent-search
+---
+
+El **Historial de indexación** es la página que monitorea el estado de sincronización de todos los productos del catálogo que se envían a Intelligent Search. Allí se puede ver ampliamente el progreso de la indexación de tu tienda.
+
+![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+
+La sección **Status de la indexación** muestra la siguiente información:
+
+* **Tiempo promedio de indexación:** tiempo promedio para la indexación de los productos, desde el momento en que el sistema recibió la notificación de un cambio, hasta la actualización en la tienda. El desempeño del tiempo de indexación se mide por un punto verde (saludable) o rojo (no saludable). 
+![Historico Indexação 2 - ES](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
+* **Productos en tienda:** cantidad de productos con información actualizada que se muestran actualmente en la tienda.
+* **División de status de indexación:** porcentaje de productos en cada etapa de indexación. El desempeño de los estados compartidos se mide por un punto verde (saludable) o rojo (no saludable). Las etapas que se muestran son:
+    * **Actualizado:** la actualización más reciente del producto que se introdujo en la tienda.
+    * **Actualizando:** se está preparando e introduciendo en la tienda la nueva información del producto.
+    * **Error**: indica que hubo un error en la indexación. El producto presenta un problema en el registro, por eso no puede indexarse. Si se trata de un nuevo producto registrado, no estará disponible en la tienda.
+
+Puedes filtrar la lista de productos indexados para tener una vista personalizada. Cabe destacar que el tiempo medio de indexación y el desglose de los estados se recalcularán en base a los productos filtrados. 
+
+Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
+
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
+
+Si filtras por `Status`, puedes seleccionar el estado por el que deseas filtrar: `Actualizado`, `Actualizando`, `Error`.
+
+![Historico indexação 4 - ES](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
+
+Si filtras por `Tiempo de indexación`, puedes seleccionar si el intervalo de tiempo `Es mayor que`, `Es igual o mayor que`, `Es menor que` o `Es igual o menor que` un horario definido.
+
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
+
+Luego de definir el filtro, haz clic en `Aplicar` para activarlo. 
+
+Para agregar un nuevo filtro, haz clic en <i class="fa-solid fa-plus"></i> `Agregar filtro`. Para remover los filtros configurados, haz clic en `Limpiar filtros`.
+
+También puedes filtrar los productos exhibidos en la lista por **ID**, **Última actualización** y **Status**, haciendo clic en la columna deseada. Para encontrar un producto específico en la lista, puedes buscarlo por su ID en la barra de búsqueda.
+
+Si deseas obtener más información sobre la indexación de un producto específico, puedes hacer clic en la línea del producto en la lista para acceder a una ventana con más detalles, tal como se muestra a continuación.
+
+![Historico indexação 6 - ES](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
+
+Además de los datos que se muestran en la lista de productos, también puedes ver:
+
+* **Tiempo de indexación:** registro de cuánto tiempo duró la última actualización del producto, en el formato `hh:mm:ss`.
+* **Cronología de indexación:** registro de cada cambio de estado con fecha y hora. Puedes ver más detalles de cada etapa haciendo clic en el ícono <i class="fa-solid fa-chevron-down"></i>.
+
+![Historico indexação 7 - ES](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
+
+Puedes reindexar un producto manualmente sin tener que ingresar una actualización en su registro. Para reindexar un producto, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Reintentar la indexación`. Solo se pueden reindexar los productos en el estado **Actualizado**.
+
+Puedes acceder al **Historial de indexación** del producto, una lista con los datos y la hora de cada actualización realizada. De esta manera, puedes llevar un registro de todas las modificaciones que se le hicieron al producto. Para acceder al historial, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Historial`. 
+
+![Histórico da Indexação 8 - ES](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
diff --git a/docs/tracks/es/initializing-your-store-theme.md b/docs/tracks/es/initializing-your-store-theme.md
index 8369c048d..feb01ab9d 100644
--- a/docs/tracks/es/initializing-your-store-theme.md
+++ b/docs/tracks/es/initializing-your-store-theme.md
@@ -28,7 +28,7 @@ Seleccione `store-theme` y confirme que desea descargar el proyecto template en
 
 Usted recibirá información importante sobre la aplicación, como el vendor, el nombre, el título y la descripción de la app. Utilice el __account name__ de la tienda que está desarrollando como el __vendor__. Esto es importante para que posteriormente pueda publicar correctamente esta aplicación en esta cuenta. Para utilizar los valores predeterminados, simplemente presione Enter.
 
-![store-theme](https://images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
+![store-theme](//images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
 
 ## Entendiendo la estructura de la app
 
@@ -88,7 +88,7 @@ Durante un "link", todos los cambios realizados en su código se envían automá
 
 Ejecute `vtex link` y vea que su aplicación de ejemplo se compila y se publica en la cuenta y en el workspace que acaba de crear.
 
-![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
+![vtex-link](//images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
 <div class="alerta alerta-info">
 Recuerde: ejecute <code>vtex whoami</code> para asegurarse de que está en la cuenta correcta y en un workspace de prueba. De lo contrario, el <code>VTEX Toolbelt</code> se queja del link directo con master.
@@ -106,4 +106,4 @@ El `{{account}}.myvtex.com` es su dominio privado destinado a probar nuevos work
 
 Felicitaciones por hacer el link de su primera app en VTEX IO!
 
-![dreamstore](https://images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
+![dreamstore](//images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
diff --git a/docs/tracks/es/inserting-and-configuring-placeholders.md b/docs/tracks/es/inserting-and-configuring-placeholders.md
index c78788087..7e501b40c 100644
--- a/docs/tracks/es/inserting-and-configuring-placeholders.md
+++ b/docs/tracks/es/inserting-and-configuring-placeholders.md
@@ -34,7 +34,7 @@ Lo que hace es crear un elemento configurable en el lugar del código donde se i
 
 Es importante ingresar un valor de `id`. Este será el identificador para este placeholder en el sistema.
 
-![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando el placeholder
 
@@ -42,7 +42,7 @@ Ahora que el control de placeholder se ha ingresado en el template, vamos a conf
 
 Esto se hace en las configuraciones del layout que utiliza este template.
 
-1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para ingresar un objeto, haga clic en **add object**. 
 3. A continuación, seleccione el tipo de objeto y haga clic en **Añadir**.
 4. Finalmente, haga clic en el botón  **Save Settings**, en la parte superior de la página.
@@ -51,7 +51,7 @@ Ahora puede editar el objeto que ha ingresado en el placeholder.
 
 Para esto, haga clic en el lápiz que se encuentra dentro del objeto y, a continuación, haga clic en **add content**.
 
-![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Ahora puede definir el nombre de este objeto, subir imágenes y configurar las condiciones en las que se renderizará, tales como el período. 
 
diff --git a/docs/tracks/es/installing-customer-credit.md b/docs/tracks/es/installing-customer-credit.md
index 1833546af..dda9b4c3d 100644
--- a/docs/tracks/es/installing-customer-credit.md
+++ b/docs/tracks/es/installing-customer-credit.md
@@ -1,10 +1,10 @@
 ---
-title: 'Instalar Customer Credit'
+title: ' Instalación de Customer Credit'
 id: 36grlQ69NK6OCuioeekyCs
 status: PUBLISHED
 createdAt: 2018-11-06T19:45:12.804Z
-updatedAt: 2020-08-17T22:17:50.649Z
-publishedAt: 2020-08-17T22:17:50.649Z
+updatedAt: 2024-02-08T11:31:30.622Z
+publishedAt: 2024-02-08T11:31:30.622Z
 firstPublishedAt: 2018-11-06T20:24:15.191Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,20 +14,14 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugES: customer-credit-como-empezar
 ---
 
-En esta guía, explicaremos el procedimiento para instalar y configurar Customer Credit. 
+En esta guía encontrará instrucciones paso a paso para instalar y configurar la aplicación Customer Credit. Para obtener más información sobre esta aplicación, visite [Customer Credit - Visión General](https://help.vtex.com/es/tutorial/customer-credit-vision-general--1uIqTjWxIIIEW0COMg4uE0).
 
-Ahora, antes que nada, en caso de que los conceptos de esta app sean nuevos para usted, le recomendamos que lea antes el artículo sobre las [nociones generales de Customer Credit](https://help.vtex.com/es/tutorial/customer-credit-vision-general--1uIqTjWxIIIEW0COMg4uE0).
+Para instalar Customer Credit en su tienda, siga los pasos a continuación:
 
-Al final de la lectura, será capaz de hacer compras en las tiendas VTEX usando Customer Credit  como forma de pago. 
+1. En el Admin VTEX, accede a __Apps > Hub de Extensiones > App Store__, o escribe __App Store__ en la barra de búsqueda en la parte superior de la página.
+2. Escriba el nombre __Customer Credit__ en la barra de búsqueda de la página de la App Store y haga clic en el icono de la aplicación.
+3. Haga clic en el botón `Obtener App`.
+4. Luego haga clic en `Instalar app` y `INSTALAR`.
+5. Actualice la página (pulsando la tecla `F5` o el botón de actualización de su navegador).
 
-De esta manera, podemos proceder con el primer paso que es la instalación de la app. Para esto, usted debe:
-
-1. Acceder a la página [App Store](https://apps.vtex.com/ "App Store") de VTEX. 
-2. Localizar el ícono de __Customer Credit__.
-3. Hacer clic en el botón gris __“Get”__.
-4. Rellenar el campo __Account__ info con el __"Account Name"__ de su tienda.
-5. Hacer clic en el botón rosa __“Confirm order and begin installation”__.
-
-En seguida, será dirigido para el Admin de su tienda. Inicie sesión y complete la instalación haciendo clic en el botón azul "Instalar", situado en la esquina superior derecha de la pantalla. 
-
-Con la app instalada, la nueva sección Customer Credit, dentro del módulo de Transacciones, aparecerá en el Admin.
+Después de cargar la página, se puede acceder a la nueva sección Customer Credit en el Admin VTEX en __Apps > Customer Credit__.
diff --git a/docs/tracks/es/instore-basic-settings.md b/docs/tracks/es/instore-basic-settings.md
index a61aac847..d0c0437ae 100644
--- a/docs/tracks/es/instore-basic-settings.md
+++ b/docs/tracks/es/instore-basic-settings.md
@@ -3,8 +3,8 @@ title: 'VTEX Sales App - Configuración básica'
 id: 4L5SoLxE8O3YkxF7FKymrO
 status: PUBLISHED
 createdAt: 2020-06-28T13:51:53.895Z
-updatedAt: 2023-05-31T15:55:29.064Z
-publishedAt: 2023-05-31T15:55:29.064Z
+updatedAt: 2023-07-26T18:42:22.814Z
+publishedAt: 2023-07-26T18:42:22.814Z
 firstPublishedAt: 2020-06-28T14:01:36.462Z
 contentType: trackArticle
 productTeam: Shopping
@@ -17,7 +17,7 @@ trackSlugES: instore-primeros-pasos-y-configuracion
 VTEX Sales App es uno de los principales productos de VTEX para las operaciones de [comercio unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv). Es una aplicación que permite a tu tienda ofrecer una verdadera experiencia <i>omnichannel</i>, integrando perfectamente tus canales <i>online</i> y físicos y poniendo a tus clientes en el centro del negocio.
 
 <div class="alert alert-info">
-<p>Comprueba que tu tienda cumple todos los <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">requisitos para utilizar inStore</a> antes de empezar a configurarla.</p>
+<p>Comprueba que tu tienda cumple todos los <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">requisitos para utilizar VTEX Sales App</a> antes de empezar a configurarla.</p>
 </div>
 
 Para utilizar VTEX Sales App, debes seguir los pasos descritos a continuación en tu cuenta principal.
@@ -78,7 +78,7 @@ Si decides `Saltar este paso`, se creará un vendedor ficticio con el email `ins
 
 ### Configurar métodos de pago
 
-El siguiente paso es configurar los métodos de pago que aceptarás en inStore. Activa las opciones deseadas utilizando el botón <i class="fas fa-toggle-on"></i> como se ilustra a continuación.
+El siguiente paso es configurar los métodos de pago que aceptarás en VTEX Sales App. Activa las opciones deseadas utilizando el botón <i class="fas fa-toggle-on"></i> como se ilustra a continuación.
 
 ![configurar-meios-de-pagamento-pt](//images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
 
@@ -93,7 +93,7 @@ Después de seleccionar las opciones deseadas, haz clic en `Confirmar`. Verás e
 
 ## Configurar condiciones de pago
 
-Después de realizar la configuración básica, debes configurar las condiciones de pago para inStore en el módulo de **Pagos**. Para ello, lee la guía [Configurar métodos de pago para inStore](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy).
+Después de realizar la configuración básica, debes configurar las condiciones de pago para VTEX Sales App en el módulo de **Pagos**. Para ello, lee la guía [Configurar métodos de pago para inStore](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy).
 
 ## Configurar logística
 
diff --git a/docs/tracks/es/instore-customizations.md b/docs/tracks/es/instore-customizations.md
index 4c15746b3..9fa24db18 100644
--- a/docs/tracks/es/instore-customizations.md
+++ b/docs/tracks/es/instore-customizations.md
@@ -36,11 +36,11 @@ Alternativamente, puede buscar el archivo de configuración desde la página de
 
 En el menú principal, haga clic en __Checkout__ y luego haga clic en el símbolo de engranaje de la tienda, como se muestra en la imagen a continuación.
 
-![20. inStore Customizations - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/4EDg8NKDGXRYEG6C8t6TjM/5e7c8c88e79ad04b7c6b0a31795a0b20/20._inStore_Customizations_-_1_-_ES.png_h_250)
+![20. inStore Customizations - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/4EDg8NKDGXRYEG6C8t6TjM/5e7c8c88e79ad04b7c6b0a31795a0b20/20._inStore_Customizations_-_1_-_ES.png_h_250)
 
 Haga clic en la pestaña __Código__ y luego en el archivo `checkout-instore-custom.js`, que se encuentra en la lista de archivos a la derecha.
 
-![20. inStore Customizations - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6mGe02KwVH7z0HGy6UpgKQ/6d4d983a3aa4bf7e3ec98540b3bc23f0/20._inStore_Customizations_-_2_-_ES.png_h_250)
+![20. inStore Customizations - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6mGe02KwVH7z0HGy6UpgKQ/6d4d983a3aa4bf7e3ec98540b3bc23f0/20._inStore_Customizations_-_2_-_ES.png_h_250)
 
 ## Cambiar el archivo de personalización del inStore
 
@@ -48,7 +48,7 @@ Haga clic en la pestaña __Código__ y luego en el archivo `checkout-instore-cus
 
 Para realizar cualquier cambio, simplemente agregue o modifique las líneas de código directamente en el cuadro de edición de archivos, en el Admin de VTEX, y finalmente haga clic en el botón __Guardar__, como se muestra en la imagen a continuación.
 
-![20. inStore Customizations - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7xWS4qln2lhLN1CgM9VwOy/69495b399f32730531e0b8eb553d6d94/20._inStore_Customizations_-_3_-_ES.png_h_250)
+![20. inStore Customizations - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/7xWS4qln2lhLN1CgM9VwOy/69495b399f32730531e0b8eb553d6d94/20._inStore_Customizations_-_3_-_ES.png_h_250)
 
 <div class="alert alert-warning">
 Siga siempre las instrucciones de personalización en esta documentación y realice solo los cambios como se indica aquí.
diff --git a/docs/tracks/es/instore-login.md b/docs/tracks/es/instore-login.md
index bd95a70cc..3f2e62335 100644
--- a/docs/tracks/es/instore-login.md
+++ b/docs/tracks/es/instore-login.md
@@ -18,7 +18,7 @@ El primer contacto entre el vendedor de la tienda física y el VTEX Sales App se
 
 Aquí, se debe utilizar el correo electrónico y la contraseña creados para el vendedor en el paso de [Configuración Básica](https://help.vtex.com/es/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO#adding-a-sales-associates-email-and-name). Recuerde que no está permitido usar correos electrónicos que ya tengan acceso al panel administrativo de las tiendas VTEX.
 
-![instore-login-PT](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/1e7ad4161b3afa2b048b4166e26a240a/instore-login-PT.png)
+![instore-login-PT](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/1e7ad4161b3afa2b048b4166e26a240a/instore-login-PT.png)
 
 Al iniciar sesión, el vendedor accede al VTEX Sales App específico de una cuenta VTEX. Aunque no es un escenario común, el mismo vendedor puede estar vinculado a más de una cuenta. Si necesita cambiar de cuenta, simplemente cierre sesión y, en la pantalla de inicio de sesión, haga clic en `Cambiar tienda`.
 
diff --git a/docs/tracks/es/instore.md b/docs/tracks/es/instore.md
index d723dff92..93d801a57 100644
--- a/docs/tracks/es/instore.md
+++ b/docs/tracks/es/instore.md
@@ -24,7 +24,7 @@ El primer contacto entre el vendedor de la tienda física y el inStore se produc
 
 Aquí, se debe utilizar el correo electrónico y la contraseña creados para el vendedor en el paso de [Configuración Básica](https://help.vtex.com/es/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO). Recuerde que no está permitido usar correos electrónicos que ya tengan acceso al panel administrativo de las tiendas VTEX.
 
-![31. inStore - Product Overview - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
+![31. inStore - Product Overview - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
 
 Al iniciar sesión, el vendedor accede al inStore específico de una cuenta VTEX. Aunque no es un escenario común, el mismo vendedor puede estar vinculado a más de una cuenta. Si necesita cambiar de cuenta, simplemente cierre sesión y, en la pantalla de inicio de sesión, haga clic en __Cambiar tienda__.
 
@@ -46,7 +46,7 @@ Usted puede [configurar qué métodos de identificación desea habilitar](https:
 
 En el ejemplo de la imagen a continuación, E-mail y CPF están habilitados.
 
-![31. inStore - Product Overview - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
+![31. inStore - Product Overview - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
 
 Ingrese uno de estos datos en el campo y haga clic en el botón __Confirmar__.
 
@@ -60,11 +60,11 @@ Aunque es posible atender a los clientes sin identificarlos, siempre recomendamo
 
 La barra superior de la aplicación de inStore ofrece algunas opciones utilizadas frecuentemente por el vendedor. Una de ellas es la búsqueda de SKU, disponible en la esquina superior derecha.
 
-![31. inStore - Product Overview - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
+![31. inStore - Product Overview - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
 
 La búsqueda de inStore es omnicanal. Es decir, cuando realiza una búsqueda en la aplicación, el vendedor busca tanto en el stock local (de la tienda física en sí) como en el catálogo de otras tiendas físicas y del e-commerce.
 
-![31. inStore - Product Overview - 4 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
+![31. inStore - Product Overview - 4 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
 
 Las opciones de disponibilidad de entrega y recogida se mostrarán más adelante, en la etapa de entrega.
 
@@ -72,11 +72,11 @@ Las opciones de disponibilidad de entrega y recogida se mostrarán más adelante
 
 Después de identificar al cliente, el vendedor es llevado directamente al carrito. Allí, si está utilizando la versión para computadora de inStore, conectada a un lector de código de barras, simplemente lea los productos para que aparezcan en el carrito.
 
-![31. inStore - Product Overview - 5 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
+![31. inStore - Product Overview - 5 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
 
 Si el vendedor está usando un tablet o smartphone, verá un botón de lectura de código de barras en la barra superior de la aplicación.
 
-![31. inStore - Product Overview - 6 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
+![31. inStore - Product Overview - 6 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
 
 Al hacer clic en él, el vendedor puede usar la cámara para emitir leer un producto y, con eso, pasar automáticamente a la pantalla de detalles de ese producto.
 
@@ -119,7 +119,7 @@ Es bueno recordar que toda esta información se refiere no solo a la experiencia
 
 Al hacer clic en los detalles de un producto que aparece en los resultados de búsqueda de inStore, o al leer el código de un producto, el vendedor se dirige a la pantalla de detalles del producto.
 
-![31. inStore - Product Overview - 7 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
+![31. inStore - Product Overview - 7 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
 
 Esta pantalla muestra el nombre del producto, su galería de fotos, variaciones, descripción y disponibilidad. El vendedor puede, en esta pantalla, agregar el producto al carrito.
 
@@ -137,7 +137,7 @@ InStore permite [habilitar una funcionalidad de transferencia de carrito](https:
 
 Una vez en un carrito, el vendedor tiene acceso al botón __Transferir__. Al hacer clic en este botón, la aplicación muestra un código QR y un código numérico de cuatro dígitos.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Otro vendedor vinculado a la misma tienda puede capturar ese carrito y continuar la venta desde su dispositivo.
 
@@ -155,21 +155,21 @@ La siguiente pantalla muestra las opciones de entrega. Como inStore tiene acceso
 
 El siguiente ejemplo muestra dos opciones: recibir todos los artículos en casa a través de una entrega económica o recogerlos en otra tienda física dentro de 5 días hábiles.
 
-![31. inStore - Product Overview - 10](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
+![31. inStore - Product Overview - 10](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
 
 ### Puntos de recogida
 
 Para los puntos de recogida, el sistema selecciona las tiendas que tienen los SKUs en stock y muestra la tienda más cercana al código postal del cliente, como sugerencia. Si el vendedor quiere cambiar la tienda donde el cliente recogerá los productos, solo hay que hacer clic en el botón __Cambiar punto de recogida__.
 
-![31. inStore - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
+![31. inStore - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
 
 Al hacer clic en ese botón, el vendedor primero tiene acceso al punto de recogida sugerido por el sistema. Para ver todos los puntos de recogida disponibles, hay que hacer clic en __Ver todos los puntos de recogida__.
 
-![31. inStore - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
+![31. inStore - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
 
 La aplicación mostrará la lista de puntos de recogida ordenados por la distancia más corta desde el código postal del cliente. También es posible elegir el punto de recogida en el mapa.
 
-![31. inStore - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
+![31. inStore - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
 
 ## 12. Pago
 
@@ -177,17 +177,17 @@ En el paso de pago, las [opciones de pago que se han configurado](https://help.v
 
 Una feature importante permitida por inStore son los pagos múltiples. Por ejemplo, al elegir Efectivo y luego hacer clic en __Agregar otro pago__, el vendedor puede cobrar parte del importe en efectivo y parte con tarjeta de crédito.
 
-![31. inStore - Product Overview - 14](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
+![31. inStore - Product Overview - 14](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
 
 La barra superior de la pantalla de pago le permite agregar cupones y gift cards. También permite cambiar el número de identificación del cliente que aparecerá en la factura.
 
-![31. inStore - Product Overview - 15](https://images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
+![31. inStore - Product Overview - 15](//images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
 
 ## 13. Pedido completado
 
 El vendedor puede ver esta misma pantalla haciendo clic en __Pedidos completos__ en el menú principal de inStore, y buscando el pedido por número de pedido o cliente.
 
-![31. inStore - Product Overview - 16](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
+![31. inStore - Product Overview - 16](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
 
 ## 14. Impresión de factura
 
diff --git a/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
index 1f338c15f..d75aefb8a 100644
--- a/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
@@ -16,7 +16,7 @@ trackSlugES: integrar-el-instore-a-un-nuevo-adquirente-de-pago
 
 Este artículo tiene como objetivo explicar cómo la aplicación de inStore configura el AppLinking para las acciones de `payment` y `payment-reversal` con las apps de los adquirentes.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuración
 
diff --git a/docs/tracks/es/integration-configurations.md b/docs/tracks/es/integration-configurations.md
index 04e4d65f5..39318f1f5 100644
--- a/docs/tracks/es/integration-configurations.md
+++ b/docs/tracks/es/integration-configurations.md
@@ -21,7 +21,7 @@ Los siguientes pasos deben realizarse dentro de la app.
 1. En el selector, escoja la política comercial que se utilizará en Wish ([predefinida en el paso 2](https://help.vtex.com/es/tracks/configurar-integracao-da-wish--50hbG4bzhSIhjz1lzqI1g43OHGQIQmt1dKw9RwKruE7H#definindo-politica-comercial))
 2. Después de seleccionar la política comercial, haga clic en "Continuar".
 
-![PT - Configurar Wish](https://images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
+![PT - Configurar Wish](//images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
 
 ## Configuraciones de envío 
 
diff --git a/docs/tracks/es/integration-settings.md b/docs/tracks/es/integration-settings.md
index 7ae77a961..bd2319929 100644
--- a/docs/tracks/es/integration-settings.md
+++ b/docs/tracks/es/integration-settings.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configuraciones de integración'
+title: 'Integraciónes'
 id: 6wKQgKmu2FT6084BJT7z5V
 status: PUBLISHED
 createdAt: 2020-04-14T13:28:52.687Z
-updatedAt: 2020-04-20T20:15:39.952Z
-publishedAt: 2020-04-20T20:15:39.952Z
+updatedAt: 2024-01-24T19:12:30.626Z
+publishedAt: 2024-01-24T19:12:30.626Z
 firstPublishedAt: 2020-04-14T23:53:14.582Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,9 +14,16 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
-Configuración de integración es la funcionalidad responsable de la indexación inicial del Catálogo con VTEX Intelligent Search. Después de instalar la aplicación, este será el primer paso para integrarla con el Catálogo.
+ En el Admin VTEX, la página **Configuración de la tienda** > **Intelligent Search** > **Integraciones** es responsable de la indexación inicial del catálogo con VTEX Intelligent Search. Luego de instalar la aplicación, la indexación constituye el primer paso para realizar la integración con el catálogo.
 
-La herramienta consiste en un texto que informa sobre el proceso de indexación y un botón de inicio. Al pulsar el botón, se inicia la indexación y se muestra un enlace para la pantalla __Status de indexación__.
+Sigue las instrucciones a continuación para iniciar el proceso de integración:
 
+1. En el Admin de VTEX, accede a **Configuración de la tienda**, o ingresa **Configuración de la tienda** en la barra de búsqueda en la parte superior de la página.
+2. En **Intelligent Search**, haz clic en **Integraciones**.
+4. Haz clic en `Iniciar la integración`.
 
-![config-int-ES](https://images.ctfassets.net/alneenqid6w5/4vmQOeaMNzZVr4gxFmwRZ0/94a0f0244cf92adc18845db15ed09be1/config-int-ES.png)
+Se dará inicio al proceso de indexación. Una vez completado, se mostrará la siguiente pantalla:
+
+![integracoes-es](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/0e53cf7952ac60b089bbcb5f6441640e/integracoes-es.PNG)
+
+No es necesario repetir este proceso. Una vez iniciada la integración, puedes realizar un seguimiento del status de indexación en la página [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tracks/es/intelligent-synonyms.md b/docs/tracks/es/intelligent-synonyms.md
new file mode 100644
index 000000000..222d22031
--- /dev/null
+++ b/docs/tracks/es/intelligent-synonyms.md
@@ -0,0 +1,67 @@
+---
+title: 'Sinónimos Inteligentes'
+id: 36w9XnpEkoVWl46tAwlyIV
+status: DRAFT
+createdAt: 2024-04-02T12:59:23.678Z
+updatedAt: 2024-06-17T13:46:32.394Z
+publishedAt: 
+firstPublishedAt: 2024-04-02T13:04:21.646Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: sinonimos-inteligentes
+locale: es
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugES: vtex-intelligent-search
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad está disponible para cuentas que tengan una cantidad mínima de sesiones y pedidos para que el modelo de inteligencia artificial sea entrenado. Si estás interesado en implementarla, por favor, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>. Es posible que se apliquen tarifas adicionales en el futuro.</p>
+</div>
+
+La funcionalidad [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) te permite registrar palabras o expresiones con el mismo significado para los términos de búsqueda utilizados por los clientes al realizar búsquedas en tu tienda, lo que aumenta las posibilidades de que obtengan resultados de búsqueda relevantes.
+
+Con la funcionalidad Sinónimos Inteligentes, la página **Sinónimos** en el Admin VTEX, además de permitir la configuración manual de sinónimos, te ofrece sugerencias inteligentes de términos para que los registres. La plataforma sugiere sinónimos a partir de inteligencia artificial, basándose en el comportamiento de búsqueda de los clientes en tu tienda.
+
+Para hacerlo, VTEX Intelligent Search contabiliza cuántas veces los clientes, durante los últimos 30 días, buscaron un término que devolvió pocos o ningún resultado de búsqueda, y tuvieron que sustituir el término original por otro. 
+
+Ejemplo: cinco clientes escribieron `jabón para la cara` y luego cambiaron la búsqueda a `jabón facial`. El sistema registra este comportamiento y los términos más reescritos aparecerán como sinónimos sugeridos.
+
+Las sugerencias se muestran en dos categorías en la lista de sinónimos, como se ilustra a continuación:
+
+* **Nuevas sugerencias:** son aquellas generadas por la plataforma que aún no se han revisado.
+* **Sugerencias guardadas:** son aquellas que se guardaron para su posterior revisión, tal como se describe en el paso 5 de la sección [Revisar sugerencias](#revisar-sugestoes).
+
+![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
+
+Puedes revisar las sugerencias generadas y elegir guardar para más tarde, rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
+
+## Revisar sugerencias
+
+Sigue las instrucciones para visualizar las sugerencias de sinónimos y definir si deseas rechazarlas, editarlas o aprobarlas:
+
+1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda de la parte superior de la página.
+2. En **Intelligent Search**, haz clic en **Sinónimos**.
+3. Al acceder a la página **Sinónimos**, si hay sugerencias todavía no revisadas, aparecerá un modal indicando el número de sugerencias generadas. Haz clic en `Revisar` para analizarlas.
+
+    Si optas por hacer clic en `Ahora no`, esas sugerencias se mantendrán en la sección **Nuevas sugerencias**, indicando la cantidad de sugerencias generadas. Para revisarlas, haz clic en `Revisar`.
+
+4. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
+
+   ![synonym-suggestion-es](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
+
+4. Para revisar cada sugerencia, elige una de las siguientes opciones:
+    * <i class="fas fa-bookmark"></i> **Guardar para más tarde:** remueve la sugerencia del recuento **Nuevas sugerencias** y la almacena en **Sugerencias guardadas**. Para analizarla posteriormente, haz clic en `Revisar`.
+    * <i class="fas fa-times-circle"></i> **Rechazar**: descarta la sugerencia propuesta.
+    * <i class="fas fa-pencil-alt"></i> **Editar**: modifica los campos de la configuración de sinónimos sugeridos. Después de editar, debes hacer clic en <i class="fas fa-check-circle"></i> para guardar los cambios. Para más información sobre los campos disponibles, consulta [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
+    * <i class="fas fa-check-circle"></i> **Aprobar**: aplica y guarda la sugerencia propuesta.
+5. Después de revisar todas las sugerencias, cierra el modal para acceder a la lista de sinónimos configurada en tu tienda.
+
+<div class="alert alert-error">
+  <p>Cuando se realiza una acción no es posible deshacerla, ya que se muestra inmediatamente la siguiente sugerencia disponible.</p>
+</div>
+
+## Más información
+
+* [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV)
+* [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL)
+* [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
diff --git a/docs/tracks/es/intro-to-vtex-io-builders.md b/docs/tracks/es/intro-to-vtex-io-builders.md
index 86ff2b8f4..9a9f543d7 100644
--- a/docs/tracks/es/intro-to-vtex-io-builders.md
+++ b/docs/tracks/es/intro-to-vtex-io-builders.md
@@ -19,6 +19,6 @@ Las apps de VTEX IO exportan código o configuración para proporcionar features
 Estos pedazos de código y configuración generalmente requieren alguna preparación o validación para servir a su propósito. Por ejemplo, los componentes React deben tener sus dependencias extraídas y compiladas en paquetes JavaScript.
 
 El VTEX IO se encarga automáticamente de todos estos pasos, implementándolos como builders. Una vez que su app declara que utiliza un builder, la carpeta correspondiente y su contenido son procesados por él cuando se realiza el link.
-![builders](https://images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
+![builders](//images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
 
 El proyecto store theme utiliza dos builders principales (`store` y `styles`), pero a medida que cree apps con funciones más avanzadas, usted comenzará a usar otros builders de nivel más bajo, como `react`, `messages`, `graphql` y `node`.
diff --git a/docs/tracks/es/introduction-to-vtex-io.md b/docs/tracks/es/introduction-to-vtex-io.md
index 694c8bbd3..7d5c57d32 100644
--- a/docs/tracks/es/introduction-to-vtex-io.md
+++ b/docs/tracks/es/introduction-to-vtex-io.md
@@ -22,7 +22,7 @@ En esta track, vamos a enseñar paso a paso cómo desarrollar una aplicación ut
 
 En la siguiente imagen se muestra la estructura jerárquica del VTEX IO:
 
-![VTEX IO Hierarchy](https://images.ctfassets.net/alneenqid6w5/41yNT81ioog0yMeq0wMKM4/86005dd6b0cee4548e16133acfb8b6fe/VTEX_IO_Hierarchy.jpg)
+![VTEX IO Hierarchy](//images.ctfassets.net/alneenqid6w5/41yNT81ioog0yMeq0wMKM4/86005dd6b0cee4548e16133acfb8b6fe/VTEX_IO_Hierarchy.jpg)
 
 - __Account__: para desarrollar una aplicación, es necesario tener una cuenta en VTEX.
 - __Workspaces__: son los ambientes donde las aplicaciones serán desarrolladas. Estos ambientes están vinculados a la cuenta. Es posible que haya varios workspaces para una sola cuenta.
diff --git a/docs/tracks/es/introduction-to-vtex.md b/docs/tracks/es/introduction-to-vtex.md
new file mode 100644
index 000000000..37325723f
--- /dev/null
+++ b/docs/tracks/es/introduction-to-vtex.md
@@ -0,0 +1,45 @@
+---
+title: 'Introducción a VTEX'
+id: 3QfoDZWg9YWl8lwS9MVrnU
+status: PUBLISHED
+createdAt: 2024-01-22T14:29:24.584Z
+updatedAt: 2024-02-22T14:58:02.855Z
+publishedAt: 2024-02-22T14:58:02.855Z
+firstPublishedAt: 2024-02-22T13:59:50.803Z
+contentType: trackArticle
+productTeam: Others
+slug: introduccion-a-vtex
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+[VTEX](https://vtex.com/co-es/) es una solución de comercio global, totalmente integrada y basada en microservicios; ofrece marketplace de punta a punta, recursos nativos de gestión de pedidos (OMS) y un modelo composable commerce, lo que permite a tiendas de diferentes segmentos gestionar operaciones con eficiencia y escalabilidad, brindando a sus clientes excelentes experiencias de compra.
+
+La imagen a continuación muestra las soluciones y posibilidades de VTEX, que se tratarán a lo largo de esta serie de artículos:
+
+![vtex_composable_complete_ES](//images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/80e21dd3aebbe2c74c752b8d61d7a2f9/vtex_composable_complete_ES.png)
+
+<div class="alert alert-info">
+Además de los portales Help Center y <a href="https://developers.vtex.com/">Developer Portal</a> y <a href="https://community.vtex.com/">VTEX Community</a>, en nuestro <a href="https://vtex.com/co-es/">sitio web</a>ofrecemos más información sobre la plataforma a través de <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">videos explicativos</a> (solo en inglés) y <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> creados por nuestros <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">partners</a>. También ponemos a disposición una serie de <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">videos de onboarding</a> (solamente en portugués).
+</div>
+
+## Visión general de esta serie
+
+Esta serie de artículos muestra la jornada de una tienda VTEX, desde la [configuración inicial](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) hasta el [go live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH). Antes de configurar los [módulos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) de la plataforma, planificar las [integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) y elegir una tecnología de [frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para la construcción del storefront, hay un paso previo: definir el [tipo de cuenta y la arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) que mejor se ajuste a las necesidades específicas del negocio.
+
+<div class="alert alert-warning">
+Cada operación de ecommerce tiene sus propias particularidades y este contenido no busca abarcar todas las situaciones existentes. El objetivo es ofrecer un modelo general y presentar de forma contextualizada los recursos y posibilidades de la plataforma VTEX.
+</div>
+
+La organización secuencial del contenido tiene un propósito didáctico y no implica necesariamente que las etapas deban llevarse a cabo en orden lineal o que la conclusión de una etapa sea un requisito para iniciar la siguiente. En algunos casos, las etapas pueden llevarse a cabo en paralelo, o al menos parcialmente. Es el caso de las integraciones del backend, las configuraciones de determinados módulos y la implementación del frontend.
+
+## Visión general de la Guía de onboarding
+
+La **Serie de la tienda VTEX** es la primera de las que componen la **Guía de onboarding**. Tras el go live, existen otras [soluciones](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) y [configuraciones](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) en la plataforma cuyo objetivo es diversificar las estrategias de venta de la tienda y expandir sus operaciones comerciales. De eso trata la segunda serie, llamada [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/7bORBaAr4rIG3JgRi68jIK).
+
+La tercera y última ruta de la **Guía de onboarding** se denomina [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) y tiene como objetivo proporcionar a nuestros clientes la mejor experiencia con la plataforma y nuestro soporte, abordando el [funcionamiento del Soporte VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) y explicando cómo abrir tickets para obtener ayuda con problemas [técnicos](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [financieros](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) o [comerciales](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
+
+Una vez hecha esta presentación, podemos empezar nuestra jornada.<br>
+Te damos la bienvenida a VTEX.
+
diff --git a/docs/tracks/es/inventory-and-shipping-module-overview.md b/docs/tracks/es/inventory-and-shipping-module-overview.md
index 1fee9e258..e81371a47 100644
--- a/docs/tracks/es/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/es/inventory-and-shipping-module-overview.md
@@ -23,7 +23,7 @@ El módulo __Inventario y Envío__ es el servicio responsable de la *logística*
 El sistema de logística tiene diversas funcionalidades útiles. Estas *features* le permiten crear una estrategia de inventario y envío que se adecue mejor a su negocio. En los próximos pasos de esta guía, veremos cómo utilizar cada una de las funcionalidades que se muestran a continuación. En el Admin de su tienda, encontrará las siguientes secciones:
 
 
-![inventory-shipping-admin-es](https://images.ctfassets.net/alneenqid6w5/jUIsT8CjbAP2O637yW3Mu/d68d30481a1e37d708a92881a227fb52/inventory-shipping-admin-es.png)
+![inventory-shipping-admin-es](//images.ctfassets.net/alneenqid6w5/jUIsT8CjbAP2O637yW3Mu/d68d30481a1e37d708a92881a227fb52/inventory-shipping-admin-es.png)
 
 __Estrategia de Envío__ (Paneles) - En esta sección, debe registrar las rutas logísticas que realizan la entrega de sus pedidos. Una ruta básica se compone de un __stock__, un __muelle__ y una __política de envío__ (transportadora).
 
diff --git a/docs/tracks/es/legacy-cms-portal.md b/docs/tracks/es/legacy-cms-portal.md
index 571567874..81346c920 100644
--- a/docs/tracks/es/legacy-cms-portal.md
+++ b/docs/tracks/es/legacy-cms-portal.md
@@ -18,7 +18,7 @@ trackSlugES: cms
 
 La sección [Layout](https://help.vtex.com/es/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW) te permite crear tu storefront con HTML y CSS. Se organiza en carpetas y archivos con fines específicos:
 
-![CMS - Layout ES](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
+![CMS - Layout ES](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
 
 - **HTML Templates:** construye el código HTML y los archivos JavaScript y CSS de referencia que se utilizarán en las páginas del sitio web.
 
@@ -38,7 +38,7 @@ La sección [Layout](https://help.vtex.com/es/subcategory/layout--2g6LxtasS4iSeG
 
 La sección [Configuración](https://help.vtex.com/es/subcategory/configuracion-de-cms--6kovkwzMRyeOOc2iEC4suM) te permite configurar los ajustes relacionados con el sitio web de tu tienda, como sus metadatos, las etiquetas SEO, los tipos de archivo, etc. 
 
-![CMS - Settings ES](https://images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/68fd8114fc801d74c45f115716d2a73e/cms-settings-es.png)
+![CMS - Settings ES](//images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/68fd8114fc801d74c45f115716d2a73e/cms-settings-es.png)
 
 La sección **Configuración** está estructurada de la siguiente manera:
 
@@ -69,7 +69,7 @@ Toda tienda debe tener, sin excepción, las siguientes carpetas en el CMS para a
 
 Vea abajo estas carpetas básicas en el CMS:
 
-![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas carpetas vienen de forma predeterminada en el ambiente de todas las tiendas VTEX.
 
diff --git a/docs/tracks/es/live-support.md b/docs/tracks/es/live-support.md
index 40da73ae4..43c85f430 100644
--- a/docs/tracks/es/live-support.md
+++ b/docs/tracks/es/live-support.md
@@ -1,10 +1,10 @@
 ---
 title: 'Servicio al cliente humano'
 id: 1woBo299K5gvDG7MSa8HYL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-18T15:27:09.214Z
-updatedAt: 2023-04-27T15:25:57.212Z
-publishedAt: 2023-04-27T15:25:57.212Z
+updatedAt: 2024-01-05T17:14:29.070Z
+publishedAt: 
 firstPublishedAt: 2023-04-18T19:58:12.540Z
 contentType: trackArticle
 productTeam: Shopping
@@ -29,18 +29,18 @@ Para configurar los horarios en los que el servicio estará disponible, sigue lo
 
 1. Define si quieres activar el Servicio al cliente humano en tu tienda.
 
-![Live Support es](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/3b266be75366e3db076799ba968028ca/configuracion_general.png)
+![Live Support es](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/3b266be75366e3db076799ba968028ca/configuracion_general.png)
 Si eliges no utilizarlo, debes incluir un mensaje de indisponibilidad que indique el canal de atención al cliente.
-![Mensagem de indisponibilidade](https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png)
+![Mensagem de indisponibilidade](//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png)
 2. Define la zona horaria. 
 3. Selecciona los días y establece el horario en el que tu tienda estará disponible para atender a los clientes vía WhatsApp. Es posible definir más de un período de servicio por día de la semana.
-![fuso horário es](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/ee9b18b394f724ea9b8c6e31eb79fcb0/horarios_funcionamento_es.png)
+![fuso horário es](//images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/ee9b18b394f724ea9b8c6e31eb79fcb0/horarios_funcionamento_es.png)
 <div class="alert alert-info">
 Para los feriados nacionales, regionales u otras fechas en las que no vayas a prestar servicio: informa la fecha y hora en que el servicio no estará disponible. Si los periodos se repiten anualmente, es posible seleccionar “Recurrencia anual”, predefiniendo la configuración de los periodos seleccionados.
 </div>
 <ol start="4">
-  <li>En caso de existir alguna excepción, informa los periodos de indisponibilidad.<br><img src="https://images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/ec040b052be986620bc101c9d56ce0f4/excecoes_ou_feriados_es.png"></li>
-  <li>Establece un mensaje de indisponibilidad. Este mensaje se enviará cuando los clientes contacten por WhatsApp fuera de las ventanas de servicio previamente configuradas.<br><img src="https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png" alt="Mensage de indisponibilidad"></li>
+  <li>En caso de existir alguna excepción, informa los periodos de indisponibilidad.<br><img src="//images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/ec040b052be986620bc101c9d56ce0f4/excecoes_ou_feriados_es.png"></li>
+  <li>Establece un mensaje de indisponibilidad. Este mensaje se enviará cuando los clientes contacten por WhatsApp fuera de las ventanas de servicio previamente configuradas.<br><img src="//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png" alt="Mensage de indisponibilidad"></li>
   <li>Haz clic en <code>Guardar</code>.</li>
 </ol> 
 
diff --git a/docs/tracks/es/livelo-integration-overview.md b/docs/tracks/es/livelo-integration-overview.md
new file mode 100644
index 000000000..36aa952d0
--- /dev/null
+++ b/docs/tracks/es/livelo-integration-overview.md
@@ -0,0 +1,18 @@
+---
+title: 'Visión general  de la Livelo integración'
+id: 5rhGcaM0SedoK7lDMBkVFD
+status: PUBLISHED
+createdAt: 2023-08-10T22:18:36.772Z
+updatedAt: 2023-08-11T02:18:04.456Z
+publishedAt: 2023-08-11T02:18:04.456Z
+firstPublishedAt: 2023-08-11T01:56:55.424Z
+contentType: trackArticle
+productTeam: Channels
+slug: vision-general-de-la-livelo-integracion
+locale: es
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugES: integracion-de-livelo
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/livelo-integration-registration.md b/docs/tracks/es/livelo-integration-registration.md
new file mode 100644
index 000000000..461e973c0
--- /dev/null
+++ b/docs/tracks/es/livelo-integration-registration.md
@@ -0,0 +1,18 @@
+---
+title: 'Registro de integración de Livelo'
+id: 2h9cAUiAZONxc5xbqeRjvu
+status: PUBLISHED
+createdAt: 2023-08-11T00:50:23.667Z
+updatedAt: 2024-07-26T18:49:35.608Z
+publishedAt: 2024-07-26T18:49:35.608Z
+firstPublishedAt: 2023-08-11T01:56:55.329Z
+contentType: trackArticle
+productTeam: Channels
+slug: registro-de-integracion-de-livelo
+locale: es
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugES: integracion-de-livelo
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/magazine-luiza-marketplace.md b/docs/tracks/es/magazine-luiza-marketplace.md
index bfb1271b8..1245d0314 100644
--- a/docs/tracks/es/magazine-luiza-marketplace.md
+++ b/docs/tracks/es/magazine-luiza-marketplace.md
@@ -3,8 +3,8 @@ title: 'Marketplace Magazine Luiza'
 id: 5CEVGKgtrMuifbjNoo8jKX
 status: PUBLISHED
 createdAt: 2021-03-16T19:41:45.000Z
-updatedAt: 2021-03-19T16:23:48.653Z
-publishedAt: 2021-03-19T16:23:48.653Z
+updatedAt: 2024-07-26T18:58:37.335Z
+publishedAt: 2024-07-26T18:58:37.335Z
 firstPublishedAt: 2021-03-18T14:15:52.422Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/managing-accounts.md b/docs/tracks/es/managing-accounts.md
index bb9d02ce6..f9649798c 100644
--- a/docs/tracks/es/managing-accounts.md
+++ b/docs/tracks/es/managing-accounts.md
@@ -3,8 +3,8 @@ title: 'Gestionar cuentas en Customer Credit'
 id: 4eknoeqaj6EGC20amsm6Gc
 status: PUBLISHED
 createdAt: 2018-11-06T21:15:25.330Z
-updatedAt: 2023-05-12T12:21:21.583Z
-publishedAt: 2023-05-12T12:21:21.583Z
+updatedAt: 2024-02-27T19:44:55.522Z
+publishedAt: 2024-02-27T19:44:55.522Z
 firstPublishedAt: 2018-11-07T17:10:45.883Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,104 +14,66 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugES: customer-credit-como-empezar
 ---
 
-La pantalla de Detalles de la Cuenta trae todo lo que usted necesita saber sobre una cuenta y su configuración.
+A través de la pantalla de cuentas en el Admin de VTEX (__Apps > Customer Credit > Cuentas__), puede acceder a la información de todas las cuentas registradas en la aplicación Customer Credit de su tienda. 
 
-## Límite de crédito 
+Al hacer clic en el nombre de una cuenta específica, la pantalla __Detalles de la cuenta__ mostrará los siguientes datos:
 
-El límite de crédito indica el valor máximo de títulos abiertos que un cliente puede tener en un momento dado. Establecerlo es obligatorio y el super Admin de la cuenta puede cambiar ese valor tantas veces como desee.
+- [Información del titular](#titular)
+- [Status de crédito](#status)
+- [Facturas emitidas](#facturas)
+- [Extractos de utilización](#extractos)
+- [Dependientes adicionales](#dependientes-adicionales)
+- [Cierre de cuenta](#cierre-de-cuenta)
+<br>
+<br>
+![Cuenta_ES](//images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/4ee2770f072e2cbd60d80045423ad427/Contas_ES.png)
 
-Además, recuerde que los cambios en el límite de crédito se actualizan en pocos minutos en el sistema.
+## Titular
 
-## Títulos
+Presenta información sobre el estado de la cuenta (activa, inactiva), código de identificación, documento registrado y correo electrónico del titular, fechas de apertura de la cuenta y última actualización de datos.
 
-El título es el documento que se genera cuando un cliente cierra una compra utilizando Customer Credit como medio de pago. 
+## Status
 
-Cuando se trata de compras en cuotas, los títulos se refieren al número de cuotas. Es decir, si el cliente escogió hacer un pago en 10 cuotas, el sistema calculará 10 títulos relacionados con el mismo pedido.
+Muestra el monto de crédito disponible para que el cliente lo utilice en compras y el monto total a pagar (en facturas) por compras ya realizadas utilizando Customer Credit como medio de pago.
 
-Independientemente del medio de pago, todos los títulos del sistema pueden ser visualizados y gestionados por el Admin y, al igual que las cuentas, también pueden exportarse y editarse de forma masiva. 
+<div class="alert alert-warning">
+Cuando el cliente realiza una compra utilizando Customer Credit, pero aún no hay factura para el pedido, el campo <b>Crédito reservado</b> también se muestra en esta pantalla que contiene información sobre el valor del pedido.
+</div>
 
-### Status de un título
-Hay cuatro posibles status para los títulos.
+## Gestionar
 
-Estos son:
+Indica el monto máximo de crédito otorgado al cliente y la tolerancia a utilizar en las compras. Estos valores se pueden editar en cualquier momento.
 
-- Abierto.
-- Pagado. 
-- Vencido.
-- Cancelado. 
+## Facturas
 
-Cabe mencionar que un título siempre se crea con el status de abierto y, dependiendo de  acciones realizadas en el Admin o de llamadas de API, puede pasar al status de Pagado o Cancelado.
+Listado que contiene la siguiente información sobre todos los valores emitidos en compras realizadas por el cliente:
 
-### Liquidación de títulos
-La forma en que los títulos serán liquidados debe ser controlada por la tienda.
+- Fecha de vencimento
+- Observación (mensaje específico para una factura)
+- Id del pedido
+- Valor de la factura
+- Status de la factura (Abierto, Pagado, Cancelado, Vencido)
 
-Una de las opciones para la liquidación de títulos es generar un enlace de pago. En este caso, una vez configurado, el cliente verá un botón "Pagar" junto al título en la pantalla Mis Créditos, que lo llevará al enlace indicado. 
+## Extractos
 
-Además, se pueden añadir enlaces de pago mediante un archivo CSV por el Admin o vía  API. 
+Muestra un informe de todas las transacciones de pago y factura realizadas para el cliente durante un período seleccionado.
 
-De esta manera, después de recibir el pago por un título, solo hay que marcarlo como pagado en nuestro sistema. Esto puede hacerse de tres maneras: individualmente, de forma masiva o por API. 
-
-#### Liquidación individual
-
-Liquidar un título por el Admin es bastante simple. 
-
-Los pasos son:
-
-1. Acceda al __Admin__.
-2. Haga clic en el módulo __Customer Credit__.
-3. Luego, haga clic en la sección __Títulos__.
-4. Seleccione el __título__ que desea editar.
-5. Haga clic en el botón azul __"Marcar"__ como pagado.
-
-De esta manera, el título cambiará su status a "Pagado".
-
-#### Liquidación masiva 
-Si su cuenta tiene muchos títulos como abiertos, no es factible cambiar el status de cada uno individualmente. 
-
-De esta manera, se puede utilizar el recurso de liquidación masiva, un proceso muy similar al de actualización masiva de cuentas. El principio es el mismo: importar un archivo CSV con los nuevos datos en el Admin. 
-
-En este caso, debe cambiar los valores de la columna status de "Abierto" a "Pagado" y guardar los cambios.
-
-A continuación, realice el procedimiento:
-
-1. Acceda al __Admin__.
-2. Haga clic en el módulo __Customer Credit__.
-3. Haga clic en la sección __Títulos__.
-4. Luego, haga clic en el botón __“Actualización masiva”__.
-5. Haga clic en el botón __“Escoger archivo”__.
-6. Seleccione el archivo __CSV deseado__.
-
-Espere que se cargue la plantilla y los todos títulos serán liquidados al mismo tiempo.
-
-#### Liquidación por API
-
-Para liquidar un título por medio de una API, puede utilizar el [endpoint](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId- "endpoint") `PUT Change Invoice`. Esta API sirve para cambiar el status de un título, no solo para liquidarlo.
-
-Rellene el body con la siguiente información:
-
-```json
-{
-"status": "string [Opened | Cancelled | Paid] (optional)", "observation": "string (optional)",
-"paymentLink": "string (URL) (optional)"
-}
-```
+## Dependientes adicionales
 
-Para más detalles, consulte nuestra [documentación técnica sobre Customer Credit](https://developers.vtex.com/docs/guides/customer-credit-api-overview "documentación ténica sobre Customer Credit.").
+La funcionalidad __Dependientes adicionales__ permite al cliente compartir créditos disponibles para compras con otras personas registradas en la cuenta.
 
-## Dependientes adicionales
+Para registrar un nuevo dependiente, siga los pasos a continuación:
 
-De acuerdo con las reglas de su negocio, puede compartir el límite de crédito de sus cuentas con otros usuarios.
+1. Dentro de la cuenta del cliente, en __Dependientes adicionales__, haga clic en "NUEVO".
+2. Ingrese el correo electrónico de la persona que se agregará como dependiente en la cuenta del cliente.
+3. Haga clic en "CONFIRMAR".
 
-Esta funcionalidad le permite registrar nuevos dependientes para una cuenta. Estos a su vez podrán compartir el mismo crédito disponible para pagar las compras en el  SmartCheckout.
+A partir de este momento, el cliente y su dependiente podrán compartir el monto en __Crédito disponible__ para realizar sus compras a través de Customer Credit.
 
-Para registrar nuevos dependientes en una cuenta, siga el procedimiento:
+## Cierre de cuenta
 
-1. Acceda al __Admin__.
-2. Haga clic en el módulo __Customer Credit__.
-3. Luego haga clic en la sección __Cuentas__.
-4. Seleccione la __cuenta__ que desea editar.
-5. En la parte final de la página, haga clic en el botón azul __"Nuevo"__.
-6. Rellene el campo en blanco con el __Email__ del nuevo dependiente.
-7. Haga clic en el botón azul __"Confirmar"__.
+Si desea cerrar la cuenta del cliente, en la sección __Otro__, haga clic en `CERRAR CUENTA`.
 
-Esto hará que el dependiente recién agregado se muestre en el box de dependientes adicionales de esa cuenta.
+<div class="alert alert-warning">
+Una cuenta de Customer Credit cerrada no se puede volver a abrir y se eliminarán la factura, el status de cuenta y los datos adicionales de los dependientes. Sin embargo, luego de completar el cierre de cuenta, si lo desea, puede <a href="https://help.vtex.com/es/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#crear-cuentas-individualmente">abrir una nueva cuenta</a> para el cliente utilizando el mismo correo electrónico que la cuenta cerrada.
+</div>
diff --git a/docs/tracks/es/managing-customer-credit-invoices.md b/docs/tracks/es/managing-customer-credit-invoices.md
new file mode 100644
index 000000000..641e97f86
--- /dev/null
+++ b/docs/tracks/es/managing-customer-credit-invoices.md
@@ -0,0 +1,73 @@
+---
+title: 'Gestionar títulos en Customer Credit'
+id: vtf5UVQcmlb0kHBZYYmM3
+status: PUBLISHED
+createdAt: 2024-02-07T21:31:46.690Z
+updatedAt: 2024-02-09T12:30:53.684Z
+publishedAt: 2024-02-09T12:30:53.684Z
+firstPublishedAt: 2024-02-07T21:44:30.527Z
+contentType: trackArticle
+productTeam: Financial
+slug: gestionar-titulos-en-customer-credit
+locale: es
+trackId: 1hCRg21lXYy2seOKgqQ2CC
+trackSlugES: customer-credit-como-empezar
+---
+
+La pantalla __Facturas__ en el Admin de VTEX (__Aplicaciones > Customer Credit > Facturas__), le permite acceder a información de todos las facturas emitidas por clientes registrados con Customer Credit en su tienda. A través de esta funcionalidad podrás realizar las siguientes acciones:
+
+- [Filtrar vista de facturas](#filtro-de-facturas) 
+- [Consulta los detalles de cada factura](#detalhes-de-la-factura)
+- [Liquidar facturas](#liquidar-facturas)
+<br>
+<br>
+![Invoices_ES](//images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/ef748599f8033d5bdac2d320a5cb2be3/Invoices_ES.JPG)
+
+## Filtro de facturas
+
+Para seleccionar la lista de invoices que se mostrarán, puede hacer clic en uno de los cuatro estados (Abierto, Pagado, Cancelado o Vencido), o ingresar el número de identificación del pedido para el cual se emitió la invoice.
+
+<div class="alert alert-warning">
+En Customer Credit, todos los títulos se crean con el estado <b>Abierto</b>.
+</div>
+
+## Detalhes de la factura
+
+Al hacer clic en una factura específica, la página __Detalles de la factura__ muestra la siguiente información: valor de la factura emitida, fecha de vencimiento, link de pago (si existe), identificación de la cuenta donde fue emitida, identificación de la orden y observaciones (mensajes específicos sobre la factura).
+
+## Liquidar facturas
+
+Para facilitar el proceso de pago de una factura, es posible proporcionar un link de pago directamente al cliente. Este link se puede añadir a la factura de dos formas:
+
+- Utilice la función `IMPORTAR` para insertar datos desde una plantilla .csv.
+- Via endpoint [PUT Change Invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-) da API Customer Credit.
+
+<div class="alert alert-info">
+Luego de realizar uno de los trámites anteriores, el cliente tendrá acceso al botón <b>PAGAR</b> que estará disponible en su área de cliente en la web de la tienda (<b>Mi Cuenta > Mis Créditos</b >).
+</div>
+
+### Liquidación individual
+
+Después de confirmar el pago de una factura, puede liquidarla de la siguiente manera:
+
+1. En el Admin VTEX, accede a __Apps > Customer Credit > Facturas__, o escribe __Facturas__ en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en la factura deseada.
+3. En la página __Detalles de la factura__, haga clic en __Marcar como pagada__.
+4. En la página __Facturas__, confirme que el estado de la factura esté se indique como __Pagado__.
+
+### Liquidación masiva
+
+Si deseas confirmar el pago de varias facturas al mismo tiempo, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Apps > Customer Credit > Facturas__, o escribe __Facturas__ en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en el botón "EXPORTAR".
+3. Accede a la plantilla .csv descargada y cambia la información del campo `Status` a `Paid` en las líneas correspondientes a los valores que deseas liquidar. Guarde la plantilla. 
+4. Haga clic en el botón `IMPORTAR`.
+5. Seleccione o inserte la plantilla .csv en el espacio __Suelta aquí tu archivo CSV o elige uno__.
+6. Haga clic en el botón `IMPORTAR ARCHIVO`.
+7. Después de cargar la plantilla en Admin, verifique en la pantalla __Facturas__ si las facturas actualizadas se describen como __Pagado__. 
+
+### Liquidación de API
+
+También puede liquidar un valor a través del endpoint [PUT - Change invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-). Para obtener más información sobre los endpoints de la API de Customer Credit , visite [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api#overview).
+
diff --git a/docs/tracks/es/managing-sales-associates-in-instore.md b/docs/tracks/es/managing-sales-associates-in-instore.md
index 16e2c1248..8d7f8f6be 100644
--- a/docs/tracks/es/managing-sales-associates-in-instore.md
+++ b/docs/tracks/es/managing-sales-associates-in-instore.md
@@ -3,8 +3,8 @@ title: 'Gestionar vendedores en VTEX Sales App'
 id: 5pqtuvi97FFZiGf7MlSe8q
 status: PUBLISHED
 createdAt: 2023-04-17T21:01:21.431Z
-updatedAt: 2023-05-31T16:15:21.153Z
-publishedAt: 2023-05-31T16:15:21.153Z
+updatedAt: 2024-01-05T19:59:15.811Z
+publishedAt: 2024-01-05T19:59:15.811Z
 firstPublishedAt: 2023-04-25T20:13:04.431Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,44 +14,31 @@ trackId: zav76TFEZlAjnyBVL5tRc
 trackSlugES: instore-primeros-pasos-y-configuracion
 ---
 
-Después de realizar las [configuraciones básicas de VTEX Sales App en el Admin](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), puede añadir vendedores al sistema o gestionar vendedores ya registrados.
+Una vez realizadas las [configuraciones básicas de VTEX Sales App en el Admin](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), es posible agregar nuevos vendedores al sistema o administrar vendedores ya registrados.
+La categoría **Vendedores** representa una sección dentro del módulo **Configuración de la tienda** del Admin VTEX, mostrando la lista completa de vendedores registrados en la aplicación [VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). Dentro de esta página, es posible gestionar la información de los vendedores en todas las [cuentas franquicia]() de tu tienda, mediante operaciones de [crear](#crear-vendedor), [buscar](#buscar-vendedor), [filtrar](#filtrar-vendedore), [editar](Editar) y [eliminar](#eliminar-vendedor).
 
-**Vendedores** es una de las páginas de **Configuración de la tienda** del Admin VTEX que muestra la lista de vendedores registrados en la aplicación VTEX Sales App de la tienda. Desde aquí, puedes gestionar la información de los vendedores en todas las cuentas franquicias de tu tienda.
-
-**Vendedores** é uma página das **Configurações da loja** del Admin VTEX que muestra la lista de vendedores registrados en la aplicación [VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) de la tienda. Desde aquí, puedes gestionar la información de los vendedores en todas las [cuentas franquicias](https://help.vtex.com/es/tutorial/que-es-una-cuenta-franquicia--kWQC6RkFSCUFGgY5gSjdl) de tu tienda.
-
-Esta página te permite gestionar tus vendedores a través de las siguientes acciones:
-
-* [Crear](#crear-vendedor)
-* [Buscar](#buscar-vendedor)
-* [Filtrar](#filtrar-vendedores)
-* [Editar](#editar-vendedor)
-* [Eliminar](#eliminar-vendedor)
-
-![vendedores-es](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
+![vendedores-es](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
 
 La página contiene la siguiente información:
 
-  | Columna | Descripción                                                                                                                                                                            |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Nombre             | Nombre que identifica el vendedor, definido en la etapa [Crear vendedor](#crear-vendedor). |
-| Código           | Código identificador de cada vendedor, el mismo registrado en el sistema de la tienda física.                                                                                                 |
-| Tienda             | Nombre identificador de la [cuenta franquicia](https://help.vtex.com/es/tutorial/que-es-una-cuenta-franquicia--kWQC6RkFSCUFGgY5gSjdl) en la que el vendedor está registrado.                              |
-| Email            | Email de acceso de cada vendedor.                                                                                                                                           |
+| Columna | Descripción                                                                                                                                                              |
+| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Nombre  | Nombre que identifica el vendedor, definido en la etapa[Crear vendedor](#crear-vendedor).                                                                                    |
+| Código | Código identificador de cada vendedor, el mismo registrado en el sistema de la tienda física.                                                                           |
+| Tienda  | Nombre identificador de la[cuenta franquicia](https://help.vtex.com/es/tutorial/que-es-una-cuenta-franquicia--kWQC6RkFSCUFGgY5gSjdl) en la que el vendedor está registrado. |
+| Email   | Email de acceso de cada vendedor.                                                                                                                                         |
 
-## Crear vendedor
+## Registrar vendedor
 
-Puedes crear un vendedor siguiendo los pasos a continuación:
+Puedes realizar el registro de un vendedor siguiendo los pasos a continuación:
 
 1. En el Admin VTEX, accede a **Configuración de la tienda > VTEX Sales App > Vendedores**, o escribe **Vendedores** en la barra de búsqueda en la parte superior de la página
-2. Haz clic en el botón `+ Agregar vendedor`.
+2. Haz clic en el botón `+ Registrar vendedor`.
 3. Rellena los [campos de registro del vendedor](#campos-de-registro-del-vendedor).
-4. Haz clic en `Agregar`.
-5. Haz clic en `Guardar` para confirmar el registro del vendedor.  
-
-Después de registrado, el vendedor recibirá un email de confirmación y se le redirigirá a la opción de inicio de sesión del vendedor en la aplicación VTEX Sales App.
+4. Haz clic en `Registrar`.
+5. Haz clic en `Guardar` para confirmar el registro del vendedor.
 
-![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+Una vez registrado, el vendedor recibirá un email de confirmación de registro y será redirigido a la aplicación VTEX Sales App para iniciar sesión como vendedor.
 
 <div class ="alert alert-warning">
 <p>Los vendedores registrados en VTEX Sales App no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.</p> 
@@ -64,6 +51,7 @@ Después de registrado, el vendedor recibirá un email de confirmación y se le
 * **Nombre del vendedor:** nombre del vendedor que se creará. Campo obligatorio.
 * **Código del vendedor:** código que identifica al vendedor, el mismo que el registrado en el sistema de la tienda física.
 * **Email:** email de acceso del vendedor para VTEX Sales App. Campo obligatorio.
+* **Permitir acceso al desempeño de ventas de otros vendedores:** casilla de verificación que permite ver el desempeño de ventas de otros vendedores (cuando está marcada) o acceder a información sobre su propio desempeño de ventas (cuando no está marcada).
 
 #### Tienda física
 
@@ -75,7 +63,7 @@ Después de registrado, el vendedor recibirá un email de confirmación y se le
 
 ## Buscar vendedor
 
-Puedes buscar un vendedor utilizando la barra de búsqueda. Tienes la opción de buscar por nombre del vendedor, nombre de la tienda y email del vendedor.
+Puedes buscar información sobre un vendedor utilizando la barra de búsqueda, que te permite acceder al nombre y al email del vendedor, así como al nombre de la tienda en la que se encuentra registrado.
 
 ## Filtrar vendedores
 
@@ -92,10 +80,10 @@ Si es necesario actualizar la tienda de un vendedor, debes editarla en el regist
 
 ## Inativar vendedor
 
-Puedes inativar un vendedor siguiendo los pasos a continuación:
+Puedes inactivar un vendedor siguiendo los pasos a continuación:
 
 1. En la fila del vendedor que deseas editar, haz clic en <i class="fas fa-ellipsis-v"></i>.
-2. Haz clic en <i class="fa-solid fa-box-archive"></i> `Inativar`.
-3. Haz clic en `Inativar` para confirmar y finalizar.
+2. Haz clic en <i class="fa-solid fa-box-archive"></i> `Inactivar`.
+3. Haz clic en `Inactivar` para confirmar y finalizar.
 
-Después de inativado, el vendedor perderá el acceso a la aplicación VTEX Sales App y no podrá iniciar sesión. Para eliminar definitivamente a un vendedor, póngase en contacto con nuestro [soporte](https://support.vtex.com/hc/es-419/requests).
+Una vez inactivado, el vendedor perderá el acceso a la aplicación VTEX Sales App y no podrá iniciar sesión. Para eliminar definitivamente a un vendedor, contacta con nuestro [soporte](https://support.vtex.com/hc/es-419/requests).
diff --git a/docs/tracks/es/managing-shipping-rates.md b/docs/tracks/es/managing-shipping-rates.md
index 5b267fabf..613e2738c 100644
--- a/docs/tracks/es/managing-shipping-rates.md
+++ b/docs/tracks/es/managing-shipping-rates.md
@@ -18,7 +18,7 @@ Para la correcta configuración de una nueva transportadora, es importante detal
 
 Esta se utiliza para registrar los códigos postales atendidos, los valores cobrados, los rangos de peso considerados y los valores adicionales de cada transportadora.
 
-![planilha-frete-pt](https://images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
+![planilha-frete-pt](//images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
 
 ## Cómo crear la plantilla 
 
diff --git a/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index e69500108..8e5e3c038 100644
--- a/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -19,7 +19,7 @@ Después de instalar y configurar TikTok for Business, podrás gestionar la inte
 
 Cualquier usuario conectado al Admin VTEX podrá acceder a esta área para gestionar TikTok. Sin embargo, al interactuar con los botones de esta zona, el usuario será redireccionado a los entornos de TikTok – TikTok Business Center, TikTok Ads Manager y TikTok Catalog Manager, donde necesitará los permisos necesarios para ver el contenido y realizar cambios.
 
-![manage-tiktok-integration](https://images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
+![manage-tiktok-integration](//images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
 
 Desde esta página, puedes:
 
diff --git a/docs/tracks/es/mapping-colors-and-sizes.md b/docs/tracks/es/mapping-colors-and-sizes.md
index b73da5bd2..15a6177af 100644
--- a/docs/tracks/es/mapping-colors-and-sizes.md
+++ b/docs/tracks/es/mapping-colors-and-sizes.md
@@ -65,7 +65,7 @@ Debe escogerse el color disponible más cercano que, en el caso de Wish, "Hielo"
   OBS: la cabecera de la tabla debe rellenarse exactamente como está en el siguiente ejemplo. Recuerde no agregar caracteres especiales como enter o espacio al rellenar esta tabla. 
   </div>
 
-![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
+![PT - Tabela Wish](//images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
 ## Cargando el archivo
 
diff --git a/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
index 33f9b3eb0..c4120c874 100644
--- a/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Mapear categorías y atributos de los productos para Mercado Libre'
 id: 5XNeiye4rS4oao2MueSUeA
 status: PUBLISHED
 createdAt: 2018-08-13T12:58:18.100Z
-updatedAt: 2022-09-05T19:01:28.441Z
-publishedAt: 2022-09-05T19:01:28.441Z
+updatedAt: 2024-07-23T21:39:55.195Z
+publishedAt: 2024-07-23T21:39:55.195Z
 firstPublishedAt: 2018-08-13T14:27:50.859Z
 contentType: trackArticle
 productTeam: Channels
@@ -27,7 +27,7 @@ Tus productos deben tener el <a href="https://help.vtex.com/es/tutorial/estoque-
 
 ## Mapear categorías
 
-Para acceder a la página de mapeo, debes ir a Admin *MARKETPLACE > Integraciones > Configuración* y en la tarjeta de integración con Mercado Libre seleccionar el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" /> y hacer clic en la opción `Realizar mapeo`.
+Para acceder a la página de mapeo, debes ir a Admin **Marketplace > Marketplace e Integrações** y en la integración con Mercado Libre selecciona la opción `Realizar mapeo`.
 
 Se te redirigirá a la página de mapeo de Mercado Libre que mostrará una lista con las categorías de tu tienda VTEX. El mapeo de categorías permite que haya una correspondencia entre las categorías de tu tienda y las categorías de Mercado Libre. Así, los productos enviados se mostrarán en la categoría equivalente en Mercado Libre.
 
@@ -37,18 +37,18 @@ La lista de categorías de tu tienda VTEX incluye el status del mapeo a través
 
 | Icono | Status | Descripción |
 | ---------- | ---------- | ---------- | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado**| Indica que se completó el mapeo de la categoría. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6v4eFsWHVy8F5VIqTVLQD9/e63d945d60a958a37246f57d919eede8/mapeamentoincompleto_mapper.JPG" /> | **Mapeo incompleto** | La categoría está parcialmente mapeada y requiere que se rellenen los atributos obligatorios, indicados con un asterisco, para mapearla. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Error en el mapeo** | Se produce un error en el mapeo cuando el marketplace elimina o cambia la categoría del producto.  Para resolver este problema, solo hay que rehacer el mapeo de categorías. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **No mapeada** | Indica que la categoría no fue mapeada. |
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado**| Indica que se completó el mapeo de la categoría. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6v4eFsWHVy8F5VIqTVLQD9/e63d945d60a958a37246f57d919eede8/mapeamentoincompleto_mapper.JPG" /> | **Mapeo incompleto** | La categoría está parcialmente mapeada y requiere que se rellenen los atributos obligatorios, indicados con un asterisco, para mapearla. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Error en el mapeo** | Se produce un error en el mapeo cuando el marketplace elimina o cambia la categoría del producto.  Para resolver este problema, solo hay que rehacer el mapeo de categorías. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **No mapeada** | Indica que la categoría no fue mapeada. |
 
 La página de mapeo también contiene las secciones **Categoría del marketplace** y **Mapeo de atributos**. Ambas aparecen como una opción de menú de selección en el que si se hace clic sobre la flecha, se muestran nuevos campos e información.
 
 Para realizar el mapeo de categorías:
 
 1. Accede al Admin.
-2. En el módulo Marketplace, seleccione **Integraciones** y haz clic en `Configuración`.
-3. En la tarjeta de Mercado Libre, haz clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+2. Haz clic en **Marketplace > Marketplace e Integraciones.**
+3. Haz clic en la integracion con Mercado Libre.
 4. Selecciona la opción `Realizar mapeo`. Se abrirá una nueva ventana con la página de mapeo.
 5. En la sección **Categorías de la tienda**, elige la categoría que deseas mapear.
 6. En la sección **Categoría del marketplace**, selecciona la categoría correspondiente en el marketplace del producto que deseas enviar.  
@@ -57,95 +57,21 @@ Para finalizar el mapeo de la categoría, debes seguir las instrucciones a conti
 
 ## Mapear atributos
 
-![Home (8)](https://images.ctfassets.net/alneenqid6w5/1WVspX796PMYQcgOycbhVC/5de9a1c9a262f8556b2eb82b9fd6cf20/Home__8_.gif)
+![Home (8)](//images.ctfassets.net/alneenqid6w5/1WVspX796PMYQcgOycbhVC/5de9a1c9a262f8556b2eb82b9fd6cf20/Home__8_.gif)
 
 El mapeo de los atributos permite que haya una correspondencia entre el patrón de tu tienda VTEX y el patrón utilizado por Mercado Libre. Cada categoría tiene atributos obligatorios en Mercado Libre y es necesario rellenarlos para que el mapeo pueda completarse. Los campos no mapeados no impiden que se realice el mapeo, sin embargo, mientras más atributos de tu producto se envíen a Mercado Libre, mejor clasificado estará en ese marketplace.
 
 Para mapear los atributos, sigue los pasos a continuación:
 
 1. Accede al Admin.
-2. En el módulo Marketplace, seleccione **Integraciones** y haz clic en `Configuración`.
-3. En la tarjeta de Mercado Libre, haz clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+2. Haz clic en **Marketplace > Marketplace e Integraciones.**
+3. Haz clic en la integracion con Mercado Libre.
 4. Selecciona la opción `Realizar mapeo`. Se abrirá una nueva ventana con la página de mapeo.
 5. En la sección **Mapeo de atributos**, rellena los campos con los atributos que deseas mapear (el asterisco indica que es obligatorio).
 6. Si has rellenado los atributos *Color* o *Tamaño*, en la columna Valores de atributo, haz clic en el "`Color/Tamaño`" equivalente y selecciona la opción de valor correspondiente.
 7. Si deseas personalizar un atributo, haz clic en el botón `Agregar valor personalizado` y crea un nombre para el valor del atributo personalizado.
 8. Haz clic en `Guardar cambios`.
 
-Al finalizar el mapeo de categorías y atributos correctamente, el status de la categoría cambiará a **Mapeado** <img class="shadow-4" src="https://images.contentful.com/alneenqid6w5/6Zu9VaGjbucOthXQsFwTD1/8681ab7d7e4fd12b41daae3c69afd552/mapper_correto.JPG" /> y tus productos se anunciarán en el sitio web de Mercado Libre.
+Al finalizar el mapeo de categorías y atributos correctamente, el status de la categoría cambiará a **Mapeado** <img class="shadow-4" src="https://images.contentful.com/alneenqid6w5/6Zu9VaGjbucOthXQsFwTD1/8681ab7d7e4fd12b41daae3c69afd552/mapper_correto.JPG" /> y tus productos se anunciarán en el sitio web de Mercado Libre.  
 
-### Tabla de medidas 
-
-La tabla de medidas permite a los clientes saber el tamaño aproximado del producto que desean comprar, brindándoles así una mejor experiencia al momento de seleccionar el tamaño de un producto. Al informar detalladamente las medidas del producto, te evitas devoluciones y reclamos por tamaño incorrecto.
-
-Al recibir menos devoluciones, tu reputación en Mercado Libre mejora junto con la exposición de tus productos. La tabla de medidas está disponible para los productos de la categoría `Calzado`. Las medidas aparecen en centímetros (cm).
-
-La tabla de medidas no solo es personalizable, lo cual posibilita la elección de diferentes opciones según las necesidades de cada uno, sino que también incluye las medidas aproximadas del tamaño de cada producto disponible.  
-
-#### Agregar tabla personalizada
-
-Para agregar una tabla de medidas personalizada, debes seguir los pasos a continuación: 
-
-1. Accede al Admin VTEX.
-2. En el *MARKETPLACE*, selecciona la opción **Integraciones** y haz clic en `Configuración`.
-3. En el recuadro de Mercado Libre, haz clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
-4. Selecciona la opción `Realizar mapeo`. Se abrirá una nueva ventana con la interfaz de mapeo.
-5. En la sección **Tabla de medidas**, haz clic en el ícono `+`.
-6. Selecciona la opción *Tabla personalizada*.
-7. Ingresa un nombre válido para tu tabla en el campo **Nombre de la tabla**.
-8. En el campo **Dominio**, selecciona la opción para tu tabla personalizada.
-9. En el campo **Género**, selecciona la opción correspondiente al género del producto. Existen cinco tipos de géneros:
-   * **Mujeres**
-   * **Hombres**
-   * **Niñas**
-   * **Niños**
-   * **Sin género**
-10. En el campo **Tamaño principal**, escoge la opción de modelo de tabla. Hay cinco modelos diferentes:
-    * **BR:** usa los tamaños estándar en Brasil.
-    * **Tamaño de la marca:** usa los tamaños estándar de la marca del producto seleccionado.
-    * **US:** usa las medidas estándar de los tamaños en Estados Unidos. Las medidas pueden variar según el género.
-    * **EU:** usa las medidas estándar de los tamaños en la Unión Europea.
-    * **UK:** usa las medidas estándar de los tamaños en el Reino Unido.
-11. En el campo **Template**, haz clic en `CSV`. Se descargará una plantilla de la tabla que deberás completar según las instrucciones de la sección Completar la plantilla de la Tabla de medidas.
-
-#### Completar la plantilla de la Tabla de medidas
-
-Cuando la completes, debes rellenar todas las columnas. Si optas por no completarla o usar algunas medidas estándar, rellena la plantilla con un `-`.
-
-En esa plantilla, deberás configurar las columnas y completarlas con los valores de los tamaños y medidas en centímetros de los respectivos tamaños.
-
-Para configurar la plantilla automáticamente, accede a *Datos > Texto para columnas*, selecciona la opción **Delimitado** y haz clic en `Avanzar`. En el campo **Delimitadores**, selecciona la opción **Coma**, haz clic en `Avanzar`, y termina haciendo clic en `Finalizar`.
-
-La plantilla de la tabla de medidas contiene las siguientes columnas:
-
-| **Columna** | **Descripción** | **Contenido** |
-| ---------- | ---------- | ---------- |
-| **Foot Length** | Medida en centímetros del tamaño | Completa cada línea con la medida en centímetros de los tamaños que completarás en las siguientes columnas |
-| **Foot Length to** | Medida en centímetros del tamaño máximo que debe tener el pie para acomodar el tamaño respectivo | Completa cada línea con las medidas máximas en centímetros de los tamanõs que completarás en las seguintes columnas |
-| **Manufacturer Size** | Número de la medida estándar del tamaño de la marca del producto seleccionado | Completa cada línea con la medida estándar de la marca del producto |
-| **BR Size** | Número de la medida estándar del tamaño en Brasil | Completa cada línea con el tamaño correspondiente seguido de BR. Por ejemplo, 38 BR |
-| **US Size** | Número de la medida estándar del tamaño en Estados Unidos. Las medidas pueden variar según el género | PCompleta cada línea con el tamaño correspondiente seguido de US. Por ejemplo, 24 US |
-| **EU Size** | Número de la medida estándar del tamaño en la Unión Europea | Completa cada línea con el tamaño correspondiente seguido de EU. Por ejemplo, 38 EU |
-| **UK Size** | Número de la medida estándar del tamaño en el Reino Unido | Completa cada línea con el tamaño correspondiente seguido de UK. Por ejemplo, 12 UK |
-
-<div class = "alert alert-info">
-Es importante reforzar la necesidad de usar “espacio” entre el número y la medida (cm), separar los números con puntos (.), llenar todas las columnas y verificar si los campos <b>Género</b> y <b>Tamaño</b> fueron seleccionados correctamente
-</div>
-
-#### Cargar la tabla de medidas
-
-Luego de completar la plantilla de mapeo, cárgala:
-
-1. Accede al Admin VTEX.
-2. En el *MARKETPLACE*, selecciona la opción **Integraciones** y haz clic en `Configuración`.
-3. En el recuadro de Mercado Libre, haz clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
-4. Selecciona la opción `Realizar mapeo`. Se abrirá una nueva ventana con la interfaz de mapeo.
-5. En la sección **Tabla de medidas**, haz clic en el ícono `+`.
-6. Selecciona la opción *Tabla personalizada*.
-7. Haz clic en `Elegir un archivo`.
-8. Selecciona el archivo de la plantilla.
-9. Haz clic en `Agregar`.
-
-Al terminar, habrás creado con éxito tu tabla de medidas personalizada.
-
-<div class = "alert alert-info">Si ocurre un error en la tabla, se indicará el problema para ser resuelto y se deberá realizar la carga nuevamente.</div>
+Después del mapeo de productos de moda, como ropa y calzado, es necesario enviar la tabla de medidas del producto a Mercado Livre. Para saber cómo llenar y enviar la tabla de medidas, sigue el tutorial [Tabla de medidas de Mercado Livre](https://help.vtex.com/pt/tutorial/tabela-de-medidas-do-mercado-livre--5dCc9IJ83SjllG75BVCWnr)
diff --git a/docs/tracks/es/mapping-product-categories-and-attributes.md b/docs/tracks/es/mapping-product-categories-and-attributes.md
new file mode 100644
index 000000000..52414a567
--- /dev/null
+++ b/docs/tracks/es/mapping-product-categories-and-attributes.md
@@ -0,0 +1,18 @@
+---
+title: 'Mapeo de categorías y atributos de productos'
+id: 1Ue3UIHrelsvjYpkLL4IRx
+status: PUBLISHED
+createdAt: 2023-08-11T01:20:24.164Z
+updatedAt: 2023-08-11T02:32:16.459Z
+publishedAt: 2023-08-11T02:32:16.459Z
+firstPublishedAt: 2023-08-11T01:56:55.281Z
+contentType: trackArticle
+productTeam: Channels
+slug: mapeo-de-categorias-y-atributos-de-productos
+locale: es
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugES: integracion-de-livelo
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/mapping-rappi-product-categories-and-attributes.md b/docs/tracks/es/mapping-rappi-product-categories-and-attributes.md
new file mode 100644
index 000000000..e5dfd846f
--- /dev/null
+++ b/docs/tracks/es/mapping-rappi-product-categories-and-attributes.md
@@ -0,0 +1,18 @@
+---
+title: 'Mapeo de categorías y atributos de productos Rappi'
+id: 6iVRkhA3WHvynIlwgQhjPc
+status: PUBLISHED
+createdAt: 2024-05-31T20:42:26.540Z
+updatedAt: 2024-05-31T20:52:02.358Z
+publishedAt: 2024-05-31T20:52:02.358Z
+firstPublishedAt: 2024-05-31T20:52:02.358Z
+contentType: trackArticle
+productTeam: Channels
+slug: mapeo-de-categorias-y-atributos-de-productos-rappi
+locale: es
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugES: integracion-de-rappi
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/mercado-libre-marketplace.md b/docs/tracks/es/mercado-libre-marketplace.md
index e79aa134a..443cef00c 100644
--- a/docs/tracks/es/mercado-libre-marketplace.md
+++ b/docs/tracks/es/mercado-libre-marketplace.md
@@ -1,10 +1,10 @@
 ---
 title: 'Mercado Libre '
 id: 51oWBHvVxSs8eAwLQhSbSd
-status: CHANGED
+status: PUBLISHED
 createdAt: 2020-09-23T20:16:36.804Z
-updatedAt: 2023-03-28T21:46:05.528Z
-publishedAt: 2021-09-04T11:14:45.743Z
+updatedAt: 2024-03-11T22:19:17.941Z
+publishedAt: 2024-03-11T22:19:17.941Z
 firstPublishedAt: 2020-09-23T20:31:42.798Z
 contentType: trackArticle
 productTeam: Channels
@@ -18,7 +18,7 @@ trackSlugES: configurar-integracion-con-mercado-libre
 
 Su operación está presente en países: Argentina, Brasil, Chile, Colombia, México, Uruguay y Venezuela.
 
-![image3](https://images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/c459fc424669363e045e5a6bca90c82d/image3.png)
+![image3](//images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/c459fc424669363e045e5a6bca90c82d/image3.png)
 
 El marketplace de Mercado Libre ofrece un entorno de comercio en línea totalmente automatizado, organizado por temas y fácil de usar. Este servicio ofrece a los compradores una amplia variedad de artículos nuevos y usados, permitiendo a empresas y particulares publicitar artículos y realizar sus ventas y compras en el mercado más grande de América Latina.
 
diff --git a/docs/tracks/es/merchandising-rules.md b/docs/tracks/es/merchandising-rules.md
index 2ccb20273..f309c9ce1 100644
--- a/docs/tracks/es/merchandising-rules.md
+++ b/docs/tracks/es/merchandising-rules.md
@@ -3,8 +3,8 @@ title: 'Reglas de merchandising'
 id: 5tBSYXb9EIdePa0MWTnFd0
 status: PUBLISHED
 createdAt: 2020-03-05T18:53:37.305Z
-updatedAt: 2023-04-03T22:01:51.692Z
-publishedAt: 2023-04-03T22:01:51.692Z
+updatedAt: 2024-01-29T17:07:18.414Z
+publishedAt: 2024-01-29T17:07:18.414Z
 firstPublishedAt: 2020-03-05T19:58:55.021Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -21,9 +21,7 @@ Las reglas de merchandising son un criterio prioritario. Así, si se configura u
 Puedes determinar reglas de merchandising para:
 
 *	**Marcas:** puedes configurar qué productos de una marca tienen mayor relevancia que los demás. Cuando el cliente busque «smartphone», por ejemplo, los productos de la marca aparecerán en el inicio de la lista y los productos de otras marcas aparecerán debajo de ellos.
-* **Producto:** otra posibilidad es promocionar un producto específico. Por ejemplo, puedes definir que cuando el cliente busque «camiseta para correr», el producto «Camiseta Running» sea el primer resultado presentado en la lista.
-
-## Lista de Reglas de Merchandising
+* **Productos:** otra posibilidad es promocionar un producto específico. Por ejemplo, puedes definir que cuando el cliente busque «camiseta para correr», el producto «Camiseta Running» sea el primer resultado presentado en la lista.
 
 En el Admin VTEX, la página **Storefront** > **Intelligent Search** > **Reglas de merchandising** permite realizar las siguientes acciones:
 
@@ -32,25 +30,36 @@ En el Admin VTEX, la página **Storefront** > **Intelligent Search** > **Reglas
 * [Editar](#editar-reglas-de-merchandising)
 * [Eliminar](#eliminar-reglas-de-merchandising)
 
-![configurar las reglas de merchandising-es](https://images.ctfassets.net/alneenqid6w5/4RIkVevSJArI3LhEHjELHu/1370d2d2a0a79dd02f01514452fc938d/image.png)
+![reglas-merch-es](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/4624acb4cd7dbe4e2a4d858e570f1f92/reglas-merch-es.PNG)
 
 La página contiene la siguiente información: 
 
-| Campos de la columna | Descripción         |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Nombre               | Nombre que identifica la regla de merchandising definida en la etapa [Crear reglas de merchandising](#crear-reglas-de-merchandising). |
-| Fecha de inicio      | Fecha en la que la regla de merchandising comenzará a estar disponible.                                                                                                                                            |
-| Fecha de fin         | Fecha en la que la regla de merchandising dejará de estar disponible.                                                                                                                                              |
-| Activa               | Opción para activar o desactivar una regla de merchandising.                                                                                                                                                       |
-| Acciones             | Opción para eliminar o editar una regla de merchandising.                                                                                                                                                          |
+| Campos de la columna | Descripción |
+| - | - |
+| __Nombre__ | Nombre que identifica la regla de merchandising definida en la etapa [Crear reglas de merchandising](#crear-reglas-de-merchandising). |
+| __Fecha de inicio__ | Fecha en la que la regla de merchandising comenzará a estar disponible. |
+| __Fecha de fin__ | Fecha en la que la regla de merchandising dejará de estar disponible. |
+| __Tipo__ | Indica el [tipo de edición](#tipos-de-edicion) utilizado en la regla de merchandising. |
+| __Activa__ | Opción para activar o desactivar una regla de merchandising. |
+| __Acciones__ <i class="fas fa-ellipsis-v"></i> | Menú con acciones para `Editar` o `Eliminar` una regla de merchandising. |
 
 ### Crear reglas de merchandising
 
-Para configurar una regla de merchandising, haga clic en `Agregar`. Más información sobre toda la información necesaria para crear un Banner en las siguientes secciones.
+Para configurar una regla de merchandising, haga clic en `+ Agregar`. Más información sobre toda la información necesaria para crear una regla de merchandising en las siguientes secciones.
 
 ### Tipos de edición
 
-Al crear o editar Reglas de merchandising, puedes elegir entre dos tipos de edición disponibles: el [Editor manual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) y el [Editor visual (Beta)](https://help.vtex.com/es/tutorial/crear-regla-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3). A continuación, te mostramos cuáles son las funcionalidades disponibles en cada una de estas opciones para que puedas decidir cuál es la más adecuada para usar en tu caso en particular:
+Existen dos tipos de editor para Reglas de merchandising: el [Editor manual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) y el [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr).
+
+A continuación, te mostramos cuáles son las funcionalidades en cada una de estas opciones:
+
+| Funcionalidad | Descripción | Editor manual | Editor visual |
+|---|---|---|---|---|
+| Reglas de activación  | Define las condiciones para la activación de la regla de merchandising. | Sí | Sí |
+| Reglas de personalización | Controla los resultados de la búsqueda a partir de condiciones específicas. | Sí | No |
+| Vista previa | Ofrece una vista previa de cómo los clientes verán los resultados de la búsqueda mientras navegan por la tienda. | No | Sí |
+| Reordenar los resultados de búsqueda | Modifica el orden de los artículos incluidos en la lista de los resultados de la búsqueda. | No | Sí |
+| Fijar productos en las primeras posiciones | Determina que un determinado elemento de un resultado de búsqueda se muestre siempre en la primera posición entre los resultados de búsqueda. | No | Sí |
 
 ## Buscar reglas de merchandising
 
@@ -60,10 +69,10 @@ Para buscar una regla de merchandising, escribe el nombre de la regla de comerci
 
 Puedes editar la información de una regla de merchandising siguiendo los pasos a continuación.
 
-1. Haz clic en el botón del lápiz <i class="fa-solid fa-pencil"></i>.
+1. Haz clic en el menú <i class="fas fa-ellipsis-v"></i> de la línea de la regla de merchandising y, a continuación, en el botón <i class="fas fa-pencil-alt"></i> `Editar`.
 2. Edita la información deseada en la regla de merchandising.
 3. Haz clic en `Guardar`.
 
 ## Eliminar reglas de merchandising
 
-Puedes eliminar una regla haciendo clic en el botón de la papelera <i class="fa-solid fa-trash-can"></i>.
+Puedes eliminar una regla haciendo clic en el menú <i class="fas fa-ellipsis-v"></i> de la línea de la regla de merchandising y, a continuación, en el botón <i class="fas fa-trash"></i> `Eliminar`.
diff --git a/docs/tracks/es/next-steps.md b/docs/tracks/es/next-steps.md
new file mode 100644
index 000000000..054eaa344
--- /dev/null
+++ b/docs/tracks/es/next-steps.md
@@ -0,0 +1,28 @@
+---
+title: 'Próximos pasos'
+id: 7bORBaAr4rIG3JgRi68jIK
+status: PUBLISHED
+createdAt: 2024-02-07T16:51:41.686Z
+updatedAt: 2024-04-03T12:10:02.808Z
+publishedAt: 2024-04-03T12:10:02.808Z
+firstPublishedAt: 2024-02-22T13:58:08.369Z
+contentType: trackArticle
+productTeam: Others
+slug: proximos-pasos
+locale: es
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugES: proximos-pasos-tras-el-go-live
+---
+
+Ahora que la tienda está configurada en el entorno VTEX y el [go-live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) se completó con éxito, presentaremos las funcionalidades y [soluciones adicionales](https://help.vtex.com/en/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) disponibles que ayudan a optimizar el rendimiento de las ventas y la expansión de la operación con el objetivo de contribuir al desarrollo continuo del negocio.
+
+<div class="alert alert-warning">
+  <p>Puedes contratar <a href="https://partnerportal.vtex.com/">partners</a> para ayudar con el desarrollo de la tienda y la gestión de las soluciones descritas en este artículo a través de <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">VTEX Partner Portal</a> (solamente en portugués). Para acceder al portal, el usuario debe tener <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz">acceso al Admin VTEX</a> de una tienda.</p>
+</div>
+
+## Lanzamientos en VTEX
+
+Los comunicados y actualizaciones más recientes de las soluciones VTEX están disponibles en nuestros portales de documentación:
+
+- **Help Center:** [comunicados](https://help.vtex.com/es/announcements) dirigidos al público operativo de la tienda.
+- **Developer Portal:** [notas de la versión](https://developers.vtex.com/updates/release-notes) dirigidas a los desarrolladores del entorno VTEX.
diff --git a/docs/tracks/es/opening-tickets.md b/docs/tracks/es/opening-tickets.md
new file mode 100644
index 000000000..94935bdda
--- /dev/null
+++ b/docs/tracks/es/opening-tickets.md
@@ -0,0 +1,35 @@
+---
+title: 'Apertura de tickets'
+id: 6EboD7Y1BOLlWdT8JM15EE
+status: PUBLISHED
+createdAt: 2024-02-20T21:30:49.633Z
+updatedAt: 2024-02-22T14:09:13.418Z
+publishedAt: 2024-02-22T14:09:13.418Z
+firstPublishedAt: 2024-02-22T14:09:13.418Z
+contentType: trackArticle
+productTeam: Others
+slug: apertura-de-tickets
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+El acceso a una cuenta VTEX te permite entrar al [dashboard de soporte](https://support.vtex.com/hc/es/requests), desde donde puedes dar seguimiento a los tickets que tengas abiertos. Abrir un ticket puede hacerse de tres maneras:
+
+- Accediendo a la [página de soporte](https://support.vtex.com/hc/es/requests).
+- Accediendo a cualquier página del [Help Center](https://help.vtex.com/es/) y haciendo clic en `Soporte` en la parte superior de la página o en `Entrar en contacto`, en la parte inferior.
+- Accediendo al Admin VTEX, haciendo clic en el ícono de la interrogación `?` del **Centro de información** y eligiendo la opción **Habla con nuestros expertos**.
+
+![Support imagem 1 - ES](//images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/0ac7e761404016450b146bfc8fabfa67/support__imagem1_ES.gif)
+
+<div class = "alert alert-info">
+Para obtener más información sobre cómo abrir un ticket y sobre los tipos existentes, consulta el artículo <a href="https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM"> Abrir tickets para el soporte VTEX. </a>
+</div>
+
+## Tipos de soporte
+
+Al abrir un ticket debes seleccionar el tipo de soporte deseado:
+
+- [Soporte técnico](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T): problemas o preguntas técnicas relacionadas con la plataforma o soluciones VTEX como [productos add-on](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+- [Soporte financiero](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl): cuestiones contractuales o financieras relacionadas con la tienda y VTEX.
+- [Soporte comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ): contratación de [política comercial adicional](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#contratacion-de-politicas-comerciales-adicionales), de [entorno adicional](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#contratacion-de-nuevo-entorno), cuenta franquicia o cambio de [usuario titular](https://help.vtex.com/es/tutorial/que-es-el-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy).
diff --git a/docs/tracks/es/order-delivery.md b/docs/tracks/es/order-delivery.md
index ab6d9b7a3..e93b63ef7 100644
--- a/docs/tracks/es/order-delivery.md
+++ b/docs/tracks/es/order-delivery.md
@@ -23,7 +23,7 @@ Vea a continuación dos ejemplos de este escenario:
 
 En este caso, es habitual que los ítems salgan del almacén de un Centro de Distribución, como se ilustra a continuación.
 
-![ES Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
+![ES Conceitos Logística](//images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
 
 Otra posibilidad de entrega que puede optimizar la operación y reducir los costes es implementar la estrategia de [envío desde la tienda](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl), de modo que los ítems también puedan enviarse desde el <i>*stock*</i> de las tiendas físicas.
 
diff --git a/docs/tracks/es/order-flow.md b/docs/tracks/es/order-flow.md
index 86d56012c..90b82b077 100644
--- a/docs/tracks/es/order-flow.md
+++ b/docs/tracks/es/order-flow.md
@@ -3,8 +3,8 @@ title: 'Flujo del pedido'
 id: 4811ExCe3WrEiRMV3sy9n8
 status: PUBLISHED
 createdAt: 2019-11-14T13:46:22.682Z
-updatedAt: 2022-08-08T22:25:52.457Z
-publishedAt: 2022-08-08T22:25:52.457Z
+updatedAt: 2023-10-24T15:32:07.852Z
+publishedAt: 2023-10-24T15:32:07.852Z
 firstPublishedAt: 2019-11-14T15:38:27.680Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -14,13 +14,13 @@ trackId: 2xkTisx4SXOWXQel8Jg8sa
 trackSlugES: pedidos
 ---
 
-El __flujo del pedido__ es la ruta que sigue un pedido en la plataforma VTEX, desde el momento en que el cliente hace clic en el botón Pagar hasta que se factura o cancela el pedido.
+El [flujo del pedido](https://help.vtex.com/es/tutorial/order-flow-and-status--tutorials_196) es la ruta que sigue un pedido en la plataforma VTEX, desde el momento en que el cliente hace clic en el botón Pagar hasta que se factura o cancela el pedido.
 
 Los cambios en el pedido - ya sean causados por el cliente, la tienda o los sistemas externos - generan cambios en el __status del pedido__. Y con eso, el pedido se mueve dentro del flujo.
 
 ## Marketplaces y Sellers
 
-Los conceptos de marketplace y seller son fundamentales para comprender el flujo de un pedido en VTEX. Vamos a entender por qué:
+Los conceptos de [marketplace y seller](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) son fundamentales para comprender el flujo de un pedido en VTEX. Vamos a entender por qué:
 
 - __Marketplace__ es el ambiente donde se cierra el pedido, es decir, donde el cliente realiza el proceso de pago.
 - __Seller__ es el propietario del SKU. Por lo tanto, es responsable del fulfillment, es decir, de entregar el producto al cliente.
@@ -33,7 +33,7 @@ Es importante comprender estos conceptos porque el flujo de pedidos en el Market
 
 ## Flujo del pedido en el Marketplace
 
-![screenshoot fluxo marketplace ES](https://images.ctfassets.net/alneenqid6w5/2ehRbL33XqtPTTF8DoHtvT/49e8aad025ddba81b5f3d169a040d9f2/screenshoot_fluxo_marketplace_ES.JPG)
+![screenshoot fluxo marketplace ES](//images.ctfassets.net/alneenqid6w5/2ehRbL33XqtPTTF8DoHtvT/49e8aad025ddba81b5f3d169a040d9f2/screenshoot_fluxo_marketplace_ES.JPG)
 
 Se produce cuando la tienda actúa solamente como Marketplace en el pedido. O sea, es cuando la tienda vende productos de otra tienda: su Seller.
 
@@ -47,7 +47,7 @@ El envío se autoriza y luego el pedido ingresa el status `Carencia para la canc
 
 ## Flujo del pedido en el Seller
 
-![screenshoot fluxo seller ES](https://images.ctfassets.net/alneenqid6w5/eEAFKk01PalVIOQFHrPUr/e10848ee747ff9c9334489d871fde01e/screenshoot_fluxo_seller_ES.JPG)
+![screenshoot fluxo seller ES](//images.ctfassets.net/alneenqid6w5/eEAFKk01PalVIOQFHrPUr/e10848ee747ff9c9334489d871fde01e/screenshoot_fluxo_seller_ES.JPG)
 
 Se produce cuando la tienda actúa como Seller. O sea, es entonces cuando ella posee el producto.
 
@@ -61,7 +61,7 @@ El siguiente status es `Preparando entrega`, cuando el Seller prepara la factura
 
 ## Flujo completo del pedido
 
-![screenshoot fluxo completo ES](https://images.ctfassets.net/alneenqid6w5/35UAHChmiqzGYFTsKDEnRI/ae60c51044ef99dab1c262fb73afc5ad/screenshoot_fluxo_completo_ES.JPG)
+![screenshoot fluxo completo ES](//images.ctfassets.net/alneenqid6w5/35UAHChmiqzGYFTsKDEnRI/ae60c51044ef99dab1c262fb73afc5ad/screenshoot_fluxo_completo_ES.JPG)
 
 Ocurre cuando la tienda es tanto Marketplace como Seller. Es decir, es cuando el pedido se cerró en la tienda y la tienda en sí es el propietario del producto, siendo responsable del fulfillment.
 
diff --git a/docs/tracks/es/other-vtex-module-settings.md b/docs/tracks/es/other-vtex-module-settings.md
new file mode 100644
index 000000000..d9f953ff3
--- /dev/null
+++ b/docs/tracks/es/other-vtex-module-settings.md
@@ -0,0 +1,106 @@
+---
+title: 'Otros ajustes de los módulos de VTEX'
+id: V1fs7IkfYMfn91ZVHTLu4
+status: PUBLISHED
+createdAt: 2024-02-20T20:25:49.450Z
+updatedAt: 2024-07-30T16:23:50.641Z
+publishedAt: 2024-07-30T16:23:50.641Z
+firstPublishedAt: 2024-02-22T14:09:20.283Z
+contentType: trackArticle
+productTeam: Others
+slug: otros-ajustes-de-los-modulos-de-vtex
+locale: es
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugES: proximos-pasos-tras-el-go-live
+---
+
+En la **Serie general de la tienda VTEX**, los artículos [Módulos de VTEX I](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) y [Módulos de VTEX II](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ) detallan los ajustes principales de cada módulo. El presente artículo explica otros ajustes de los módulos que no son requisito para el [go-live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH).
+
+## Promociones
+
+Luego de configurar los ajustes obligatorios de [Promociones](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promocoes), también es importante familiarizarse con los [clústeres de clientes](#clusteres-de-clientes), la [competencia de promociones](#competencia-de-promociones) y las [promociones para marketplaces](#promociones-para-marketplaces) según describe a continuación.
+
+### Clústeres de clientes
+
+Para proporcionarles ventajas de compra exclusivas a un grupo específico de personas o empresas, puedes [crear promociones personalizadas](https://help.vtex.com/es/tutorial/creando-promociones-cluster-clientes--tutorials_342) para un clúster de clientes registrados en la tienda. En este contexto, la información de la promoción solo se mostrará en el carrito después de que los clientes inicien sesión en el sitio web. 
+
+### Competencia de promociones
+
+Cuando la tienda tiene promociones activas registradas que comparten características similares y que pueden aplicarse simultáneamente a un producto, las promociones pueden competir entre sí. En estos casos, es importante entender el orden de prioridad en que se aplicarán las promociones al producto para garantizar que se esté utilizando la estrategia de ventas correctamente.
+
+Para más información, consulta [Cómo funciona la competencia de promociones](https://help.vtex.com/es/tutorial/como-funciona-la-competencia-de-promociones--tutorials_2270).
+
+### Promociones para marketplace
+
+Las tiendas que operan como marketplace VTEX solo pueden configurar [promociones regulares](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) para sus productos, tales como:
+
+- Envío gratis
+- Envío porcentual
+- Porcentaje de precio
+- Tablas de precios
+
+Para más información, consulta [Configurar promoción para marketplace](https://help.vtex.com/es/tutorial/configurar-promocion-para-marketplace--tutorials_406).
+
+## Logística
+
+Después de configurar los ajustes obligatorios de [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistc), las cuentas VTEX que tienen una arquitectura [multitienda o multidominio](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multiloja) pueden iniciar una estrategia de ventas para otros países para convertirse en una [tienda internacional (cross-border)](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs). Algunas de las principales ventajas de este tipo de operación son:
+
+- **Optimización de la capacidad logística total:** la acumulación de experiencia sobre procesos logísticos complejos (importación y exportación) permite la gestión más eficiente de toda la cadena logística (nacional e internacional).
+- **Expansión del negocio:** apertura de nuevos públicos que aumentan el potencial de ventas de las tiendas.
+- **Ventajas fiscales:** puede haber incentivos fiscales internacionales, como la exención de impuestos, que disminuyan el costo de la venta del producto.
+- **Internacionalización de la marca:** consolidación de la imagen de la empresa en varios mercados, lo que aumenta la confianza de los consumidores y, en consecuencia, aumenta las ventas a nivel nacional e internacional.
+
+Las operaciones cross-border deben planificarse tomando en cuenta las siguientes consideraciones:
+- **Tipo de exportación:** la exportación puede ser directa o indirecta.
+  - **Directa:** la empresa es la única encargada de las actividades de distribución y envío de los productos a los clientes.
+  -   **Indirecta:** los productos son adquiridos por terceros (socios de negocio o intermediarios ubicados en el país de destino) que asumen toda la responsabilidad de la gestión de la operación.
+
+- **Aceptación de productos:** comprobar estrategias de venta y preferencias del público en el mercado en el que se quiere operar.
+
+- **Precios inteligentes:** definir la estrategia de precios con base en los costos locales (transporte, cargos, impuestos).
+
+- **Asociaciones:** establecer asociaciones con transportadoras y proveedores locales.
+
+- **Diferenciales competitivos:** definir la forma en que la empresa podrá ofrecer beneficios a los clientes del nuevo mercado en comparación con los competidores actuales.
+
+Para más información sobre cómo empezar una operación cross-border, ponte en contacto con el CX encargado de la cuenta VTEX o con el [equipo de soporte VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8).
+
+## Pedidos
+
+Después de configurar los ajustes obligatorios de [Pedidos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex-eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos), la tienda puede expandir las ventas por medio de [suscripciones](#suscripciones) de pedidos recurrentes y optimizar la gestión de los pedidos en el Admin VTEX con [VTEX DO](#vtex-do).
+
+### Suscripciones
+
+Se puede configurar la programación de compras recurrentes en el [sistema de Suscripciones](https://help.vtex.com/es/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453) de la plataforma, posibilitando que los clientes vuelvan a adquirir automáticamente sus productos preferidos con la frecuencia que deseen.
+
+### VTEX DO
+
+[VTEX DO](https://help.vtex.com/es/tutorial/vtex-do-interface--7KMbRL4OslN8DTX9oiuCiu) es el sistema de gestión de tareas de procesamiento de pedidos en la tienda que permite a los operadores de la tienda ejecutar manualmente las tareas creadas automáticamente por el Admin VTEX. VTEX DO tiene las siguientes funcionalidades:
+
+- Búsqueda y filtro por status (abiertas y sin asignar) o por tema (catálogo, comercial, infraestructura).
+
+- Acceso a detalles e información para completar cada tarea.
+
+- Asignación de [usuario](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512) encargado de la tarea.
+
+![vtex-do-es](//images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/68b05218448ed87c58001b235024bb46/next_steps_image12_ES.JPG)
+
+### VTEX Social Selling
+
+[VTEX Social Selling](https://help.vtex.com/es/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg) les permite a los vendedores seleccionar productos y compartirlos con los clientes a través de canales de comunicación como WhatsApp, Facebook Messenger e email. Esta funcionalidad se puede utilizar tanto en la tienda online como en operaciones de tiendas físicas ([VTEX Sales App](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm#vtex-sales-app).
+
+## B2B Suite 
+[B2B Suite](https://help.vtex.com/es/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3) es un conjunto de [aplicaciones VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) que permite a las tiendas gestionar organizaciones, permisos de acceso y configuraciones de checkout para relaciones comerciales B2B, entre otras funciones. Estos recursos son importantes para simplificar el flujo de compra, reducir costos y ofrecer una experiencia de compra personalizada.
+
+### Conjunto de aplicaciones B2B Suite
+Las aplicaciones que componen B2B Suite se desarrollaron para impulsar las operaciones de negocios B2B. Son las siguientes:
+
+- **Storefront Permissions:** almacena un conjunto predefinido de roles y permisos que determina lo que los usuarios B2B pueden acceder y realizar en el storefront.
+- **Storefront Permissions UI:** permite a los usuarios de VTEX Admin gestionar funciones B2B y permisos de aplicaciones asociadas a través del propio Admin.
+- **B2B Organizations:** permite agrupar a los usuarios B2B en organizaciones a las que pueden asignarse medios de pago específicos, tablas de precios y colecciones de productos.
+- **B2B Quotes & Carts:** permite a los usuarios B2B crear cotizaciones y guardar carritos, que pueden compartirse con otros miembros de la organización.
+- **B2B Checkout Settings:** agrupa a los usuarios B2B en organizaciones, a las cuales se les pueden asignar métodos de pago específicos, tablas de precios y colecciones de productos.
+- **B2B Orders History:** permite a los usuarios B2B ver todos los pedidos anteriores realizados por su organización o centro de costos.
+- **B2B Admin Customers:** proporciona funciones adicionales de gestión de información de clientes en el Admin VTEX, permitiendo a los administradores de la tienda crear, editar y buscar clientes.
+
+Para más información sobre las aplicaciones, accede a [Conjunto de aplicaciones B2B Suite](https://help.vtex.com/es/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#conjunto-de-aplicaciones-b2b-suite).
diff --git a/docs/tracks/es/overview-intelligent-search.md b/docs/tracks/es/overview-intelligent-search.md
index 900b71b64..11a1cd6ce 100644
--- a/docs/tracks/es/overview-intelligent-search.md
+++ b/docs/tracks/es/overview-intelligent-search.md
@@ -1,10 +1,10 @@
 ---
 title: 'Intelligent Search'
 id: 3qgT47zY08biLP3d5os3DG
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-03-05T14:47:05.068Z
-updatedAt: 2023-04-13T22:52:19.619Z
-publishedAt: 2023-04-13T22:52:19.619Z
+updatedAt: 2023-08-22T17:03:02.484Z
+publishedAt: 2023-08-22T17:01:21.074Z
 firstPublishedAt: 2020-03-05T19:53:38.701Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,10 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
+<div class="alert alert-info" role="alert"><p>
+Esta aplicación solo está disponible para tiendas desarrolladas con VTEX IO. Antes de continuar, debes instalar y configurar Intelligent Search en tu tienda.</p>
+</div>
+
 Intelligent Search es una plataforma de búsqueda inteligente para el comercio digital. Es una solución de búsqueda nativa de la plataforma VTEX que ayuda al cliente en toda la jornada de compra, independientemente del canal (sitio web, aplicación móvil, conversacional, etc.).
 
 De forma sencilla e intuitiva, presenta resultados relevantes basados en el catálogo desde la primera interacción del usuario con la tienda, ya sea a través de la barra de búsqueda, al navegar por las categorías o incluso a través de las vitrinas de productos.
@@ -22,9 +26,7 @@ La herramienta también cuenta con funcionalidades como autocompletar, que muest
 
 Además, Intelligent Search utiliza datos históricos de clics y pedidos para mejorar la búsqueda dinámicamente y tiene la capacidad de manejar errores ortográficos, plurales y singulares y género. Asimismo, la configuración permite tanto mejorar la experiencia del cliente como satisfacer las necesidades de negocio del comerciante.
 
-<div class="alert alert-info" role="alert"><p>
-Esta aplicación solo está disponible para tiendas desarrolladas con VTEX IO. Antes de continuar, debes instalar y configurar Intelligent Search en tu tienda.</p>
-</div>
+VTEX Intelligent Search es compatible con los siguientes idiomas: Alemán, Árabe, Armenio, Bengalí, Búlgaro, Catalán, Checo, Chino, Danés, Español, Estonio, Euskera, Finés, Francés, Gallego, Griego, Hindi, Húngaro, Indonesio, Irlandés, Italiano, Japonés, Letón, Lituano, Neerlandés, Noruego, Persa, Polaco, Portugués, Portugués Brasileño, Rumano, Ruso, Soran, Sueco, Tailandés, Turco y Urdu.
 
 En los artículos que se mencionan a continuación, encontrarás una descripción general de cada funcionalidad de Intelligent Search.
 
@@ -34,6 +36,6 @@ En los artículos que se mencionan a continuación, encontrarás una descripció
 - **Filtros**: es la funcionalidad que muestra las especificaciones de los resultados de una búsqueda de forma agrupada.
 - **Indexación**: es un proceso que prepara los datos generales del SKU, como los datos de catálogo, precio y stock, y actualiza la información para que sirva de base a las búsquedas y montajes de estantes del sitio web. Al acceder a Intelligent Search en tu tienda, puedes comprobar el status e historial de la indexación.
 - **Relevancia**: la relevancia es una funcionalidad que define el orden de los productos en los resultados de la búsqueda.
-- **Informes**: Organiza los datos relativos a las búsquedas realizadas en la tienda y permite exportar estos datos en un archivo CSV.
+- **Analytics**: Organiza los datos relativos a las búsquedas realizadas en la tienda y permite exportar estos datos en un archivo CSV.
 - **Redirecciones**: las redirecciones son una funcionalidad que dirige al cliente a cualquier otra página, ya sea interna o externa a tu sitio web. La redirección se realiza en el área de búsqueda utilizando términos o filtros seleccionados. En el Admin, la redirección se conoce como Redirecciones.
 - **Sinónimos**: permite registrar sinónimos (palabras con el mismo significado) de un término de búsqueda concreto, lo que aumenta las posibilidades de éxito de la búsqueda.
diff --git a/docs/tracks/es/partial-invoices.md b/docs/tracks/es/partial-invoices.md
index 2dc4c6bc6..ffec5ed72 100644
--- a/docs/tracks/es/partial-invoices.md
+++ b/docs/tracks/es/partial-invoices.md
@@ -3,8 +3,8 @@ title: 'Facturas parciales'
 id: q9GPspTb9cHlMeAZfdEUe
 status: PUBLISHED
 createdAt: 2022-06-20T20:13:46.342Z
-updatedAt: 2023-03-31T22:36:12.880Z
-publishedAt: 2023-03-31T22:36:12.880Z
+updatedAt: 2024-04-01T17:51:08.329Z
+publishedAt: 2024-04-01T17:51:08.329Z
 firstPublishedAt: 2022-06-20T20:21:34.641Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -29,7 +29,8 @@ Las facturas parciales generan las siguientes acciones en el módulo **Pedidos**
 * Las facturas parciales emitidas en los pedidos también generan liquidaciones parciales en la transacción. El valor total del pedido se actualizará después de emitir la factura por el valor que se facturó a través del _gateway_ de pagos de VTEX.  
 * Si hay una diferencia en los valores, el consumidor recibe un reembolso de modo automático.  
 * Luego, si el _retailer_ identifica que se deben eliminar un ítem y su valor, se podrá modificar el pedido y descontar ese importe, ya que las facturas anteriores solo incluían los valores correspondientes y el saldo del valor facturado estaba pendiente.  
-* Como en la factura parcial solo se liquida el valor correspondiente a la factura, se pueden realizar cambios en los importes del pedido. Con la factura parcial, la transacción queda pendiente y a la espera de que el valor restante se facture o cancele, tal como sucede cuando hay un cambio en un pedido por un descuento en el valor.   
+* Como en la factura parcial solo se liquida el valor correspondiente a la factura, se pueden realizar cambios en los importes del pedido. Con la factura parcial, la transacción queda pendiente.
+* No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos parcialmente facturados. Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 <div class = "alert alert-info">
 La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el <a href="https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Los conectores legados no admiten la funcionalidad.
diff --git a/docs/tracks/es/payment.md b/docs/tracks/es/payment.md
index 7fb6da073..d638625ba 100644
--- a/docs/tracks/es/payment.md
+++ b/docs/tracks/es/payment.md
@@ -16,7 +16,7 @@ trackSlugES: instore-usando-el-app
 
 En el paso de pago de VTEX Sales App, las [opciones de pago que se han configurado](https://help.vtex.com/es/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy) aparecerán en su tienda.
 
-![instore-payment-es](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/b91142c0f767502f5e68f91830032fcb/Screenshot_2022-10-21_at_15-02-51_VTEX_VTEX Sales App_Checkout.png)
+![instore-payment-es](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/b91142c0f767502f5e68f91830032fcb/Screenshot_2022-10-21_at_15-02-51_VTEX_VTEX Sales App_Checkout.png)
 
 La barra superior de la pantalla de pago muestra las siguientes opciones:
 
@@ -45,7 +45,7 @@ Para configurar un medio de pago, sigue las instrucciones de la guía[ VTEX Sale
 
 El cliente debe seleccionar la opción **Efectivo** y hacer clic en `Finalizar venta`.
 
-![instore-dinheiro-es](https://images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/12ee090451235610a53ec937f8af2b69/Screenshot_2022-10-21_at_15-03-02_VTEX_VTEX Sales App_Checkout.png)
+![instore-dinheiro-es](//images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/12ee090451235610a53ec937f8af2b69/Screenshot_2022-10-21_at_15-03-02_VTEX_VTEX Sales App_Checkout.png)
 
 Luego, el cliente debe realizar la transacción con el vendedor. La aprobación de la venta puede ser [manual o automática](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), dependiendo de la configuración de la tienda.
 
@@ -53,21 +53,21 @@ Luego, el cliente debe realizar la transacción con el vendedor. La aprobación
 
 El cliente debe seleccionar la opción **Pix** y hacer clic en `Finalizar venta`.
 
-![instore-pix-es](https://images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/2f9ad65f84c36686f1e9f06ed94a69ed/Screenshot_2022-10-21_at_15-03-27_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix-es](//images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/2f9ad65f84c36686f1e9f06ed94a69ed/Screenshot_2022-10-21_at_15-03-27_VTEX_VTEX Sales App_Checkout.png)
 
 Después de finalizar la venta, se mostrará el código QR en la pantalla de VTEX Sales App. El cliente debe escanear el código QR con el celular para realizar el pago.
 
-![instore-pix2-es](https://images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/ebdb109d680d504c71b41318c3dcfa24/image.png) 
+![instore-pix2-es](//images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/ebdb109d680d504c71b41318c3dcfa24/image.png) 
 
 Después de que el cliente realice el pago, la venta será procesada y finalmente confirmada en la página del pedido, como se muestra en la imagen a continuación.
 
-![instore-pix3-es](https://images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/3d4621cb3e131300d783dae3b5531f73/Screenshot_2022-10-21_at_15-03-58_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix3-es](//images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/3d4621cb3e131300d783dae3b5531f73/Screenshot_2022-10-21_at_15-03-58_VTEX_VTEX Sales App_Checkout.png)
 
 ### Boleto (Brasil)
 
 El cliente debe seleccionar la opción **Boleto** y hacer clic en `Finalizar venta`.
 
-![instore-boleto-es](https://images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/e0800b0dc8dec484040eb5980a888adc/Screenshot_2022-10-21_at_15-02-56_VTEX_VTEX Sales App_Checkout.png)
+![instore-boleto-es](//images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/e0800b0dc8dec484040eb5980a888adc/Screenshot_2022-10-21_at_15-02-56_VTEX_VTEX Sales App_Checkout.png)
 
 El boleto se enviará al email del cliente. Después de que se confirme el pago del boleto, la venta será confirmada.
 
@@ -75,7 +75,7 @@ El boleto se enviará al email del cliente. Después de que se confirme el pago
 
 El cliente debe seleccionar la opción **Tarjeta de crédito**, seleccionar el número de cuotas de la compra y hacer clic en `Finalizar venta`.
 
- ![instore-credito-es](https://images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ede072361e0b860a57134816109a34e7/Screenshot_2022-10-21_at_15-03-20_VTEX_VTEX Sales App_Checkout.png)
+ ![instore-credito-es](//images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ede072361e0b860a57134816109a34e7/Screenshot_2022-10-21_at_15-03-20_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App mostrará una pantalla de espera mientras se realiza el pago en la máquina de tarjetas de la tienda. Una vez que el sistema reconozca el pago, la venta será confirmada.
 
@@ -83,7 +83,7 @@ VTEX Sales App mostrará una pantalla de espera mientras se realiza el pago en l
 
 El cliente debe seleccionar la opción **Tarjeta de débito** y hacer clic en `Finalizar venta`.
 
-![instore-debito-es](https://images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4574ff7ac0657f38ccc46ecfcb7200e7/Screenshot_2022-10-21_at_15-03-13_VTEX_VTEX Sales App_Checkout.png)
+![instore-debito-es](//images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4574ff7ac0657f38ccc46ecfcb7200e7/Screenshot_2022-10-21_at_15-03-13_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App mostrará una pantalla de espera mientras se realiza el pago en la máquina de tarjetas de la tienda. Una vez que el sistema reconozca el pago, la venta será confirmada.
 
diff --git a/docs/tracks/es/personal-data.md b/docs/tracks/es/personal-data.md
new file mode 100644
index 000000000..cc31a69af
--- /dev/null
+++ b/docs/tracks/es/personal-data.md
@@ -0,0 +1,48 @@
+---
+title: 'Datos personales'
+id: 65ZqZlNWcmFSOqZQxr8gha
+status: PUBLISHED
+createdAt: 2024-05-03T14:39:14.904Z
+updatedAt: 2024-05-03T21:13:09.925Z
+publishedAt: 2024-05-03T21:13:09.925Z
+firstPublishedAt: 2024-05-03T16:42:08.464Z
+contentType: trackArticle
+productTeam: Others
+slug: datos-personales
+locale: es
+trackId: 65ZqZlNWcmFSOqZQxr8gha
+trackSlugES: datos-y-privacidad
+---
+
+Los datos personales o Personally Identifiable Information (PII) son cualquier información relativa a una persona física que sea capaz de identificarla de forma directa (como nombre, nro. de identificación fiscal y dirección de email personal) o indirecta (como direcciones IP, direcciones físicas y [cookies](https://vtex.com/co-es/privacy-and-agreements/vtex-platform-cookies-information/)).
+
+Los datos personales sensibles comprenden aquellos relacionados con la raza, creencias religiosas, opiniones políticas, afiliación sindical, salud, vida sexual, información genética o biométrica. El uso indebido de estos tipos de datos puede ocasionar graves perjuicios o tratamiento discriminatorio al titular.
+
+## Datos personales tratados por VTEX
+
+VTEX procesa los datos personales de los compradores solo cuando es necesario, de acuerdo con los requisitos de cada módulo de la plataforma para llevar a cabo las operaciones de ecommerce. Consulta a continuación la lista de los datos personales que pueden ser tratados por VTEX:
+
+* Nombre
+* Email
+* Dirección IP
+* Información de navegación ([cookies](https://vtex.com/co-es/privacy-and-agreements/vtex-platform-cookies-information/))
+* Información del carrito
+* Información e historial de pedidos
+* Dirección de envío
+* Número de documento de identidad (cuando lo exija el país en el que opera la tienda)
+* Historial de tarjeta de regalo
+* Carrito abandonado
+* Conversaciones de [Conversation Tracker](https://help.vtex.com/es/tutorial/comprendiendo-el-conversation-tracker--tutorials_195)
+* Contraseñas de sesión (cifradas)
+* Tokens generados
+
+La lista de datos anterior se encuentra detallada en el contrato [Data Processing Addendum (DPA)](#data-processing-addendum-dpa).
+
+VTEX no vende, monetiza, enriquece ni transfiere ningún dato personal de compradores a otras empresas.
+
+## Minimización de datos
+
+El principio de minimización de datos se refiere a la práctica de recopilar, procesar y almacenar solo la información estrictamente necesaria para alcanzar un propósito específico. Este principio permite limitar la cantidad de datos personales que se recopilan y mantienen, reduciendo así el riesgo asociado con el procesamiento excesivo de información.
+
+En este sentido, VTEX solamente recopila la cantidad mínima de datos necesarios para procesar los pedidos recibidos, es decir, únicamente los datos personales estrictamente necesarios para las operaciones de ecommerce.
+
diff --git a/docs/tracks/es/planning-the-go-live.md b/docs/tracks/es/planning-the-go-live.md
new file mode 100644
index 000000000..1eb7212d8
--- /dev/null
+++ b/docs/tracks/es/planning-the-go-live.md
@@ -0,0 +1,195 @@
+---
+title: 'Planificación del go live'
+id: 6xYnNxDHUcY6FyChgziCoH
+status: PUBLISHED
+createdAt: 2024-01-08T13:11:05.385Z
+updatedAt: 2024-06-27T00:28:49.687Z
+publishedAt: 2024-06-27T00:28:49.687Z
+firstPublishedAt: 2024-02-22T14:07:27.548Z
+contentType: trackArticle
+productTeam: Others
+slug: planificacion-del-go-live
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+El go live es el momento en que la tienda empieza a estar disponible para que los clientes accedan a ella y realicen compras. Este artículo explica cómo planificar todas las etapas necesarias para el go live de una tienda VTEX, que son las siguientes:
+
+1. [Preparación para el go live](#1-preparacion-para-el-go-live)
+2. [Configuración de la tienda](#2-configuracion-de-la-tienda)
+3. [Configuración del dominio y la cuenta](#3-configuracion-del-dominio-y-la-cuenta)
+4. [Pruebas antes del go live](#4-pruebas-antes-del-go-live)
+5. [Registro del dominio y solicitud de apuntamiento](#5-registro-del-dominio-y-solicitud-de-apuntamiento)
+6. [Go live](#6-go-live)
+7. [Acciones después del go live](#7-acciones-despues-del-go-live)
+
+## Antes de comenzar
+
+Para preparar una tienda para el go live, es importante definir previamente el equipo o [agencia partner](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion) que se encargará de la implementación, escoger los [tipos de cuenta VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-cuenta-en-vtex) según el tipo de operación y planificar la arquitectura de la tienda. Para más información sobre las etapas, consulta el artículo [Cuentas y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl).
+
+## 1. Preparación para el go live
+
+El proceso de go live de una tienda, incluyendo las configuraciones y pruebas necesarias, puede variar según el nivel de complejidad operativa de la misma. Por este motivo, recomendamos planificar todas las etapas necesarias del go live con un mínimo de 15 días de antelación.
+
+En la siguiente imagen puedes ver las etapas de planificación del go live de una tienda VTEX:
+
+![go-live-es](//images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/41e4c49c159b2a1d22c863808f3e382c/golive_1_ES.png)
+
+### Definir MVP
+
+El primer paso es determinar los elementos fundamentales del Minimum Viable Product (MVP), incluyendo las funcionalidades, páginas y datos necesarios para el lanzamiento oficial de la tienda.
+
+Es importante hacer una lista de todos los requisitos que se deben implementar antes del go live. Los recursos deseables (pero no esenciales) se deben anotar por separado y se deben implementar como cambios graduales después del lanzamiento.
+
+### Planificar prueba de penetración (opcional)
+
+Los retailers que deseen realizar una prueba de penetración antes del go live deben solicitar autorización previa, siguiendo las pautas de la guía [Pruebas de penetración y avisos de vulnerabilidad](https://help.vtex.com/es/tutorial/pruebas-de-penetracion-y-advertencia-de-vulnerabilidad--6jodF6s1I50Fg84ZwutOCb).
+
+Es obligatorio enviar el informe con los resultados al [soporte VTEX](https://help.vtex.com/es/support) por lo menos **45 días** antes de la fecha prevista para el go live. Durante este período, VTEX analizará el resultado y abordará cualquier vulnerabilidad detectada en el proceso.
+
+Por lo tanto, todo el proceso de planificación debe comenzar con al menos 45 días de antelación, más el tiempo transcurrido entre la solicitud y la prueba.
+
+### Definir roadmap
+
+Para organizar los equipos participantes y realizar el go live en la fecha deseada, es importante crear un roadmap, es decir, un documento que recoja las acciones requeridas y que indique los responsables de cada etapa y los plazos acordados. La siguiente imagen muestra un ejemplo de roadmap:
+
+![golive 2 ES](//images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/135bae2dca13c1881fb5d7c02a5f0b60/golive_2_ES.png)
+
+Recomendamos planificar reuniones periódicas con los [equipos de implementación](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion) para mantener una alineación frecuente y, de ser necesario, crear un war room para resolver asuntos pendientes la semana antes del go live.
+
+### Planificar lanzamiento piloto
+
+Además de las pruebas durante el desarrollo del proyecto, recomendamos incluir un lanzamiento piloto en el roadmap, o sea, un lanzamiento restringido a un público o mercado antes del lanzamiento oficial. Esta etapa puede ayudar a refinar y corregir detalles no observados durante el proyecto de implementación.
+
+Después de la fecha del lanzamiento oficial, con la tienda plenamente operativa, los desarrolladores pueden seguir iterando el MVP y añadiendo mejoras sin interrumpir las ventas.
+
+## 2. Configuración de la tienda
+
+Antes del go live, es muy importante comprobar las configuraciones esenciales para el buen funcionamiento de la tienda. Para esto recomendamos verificar la [Lista de configuración de la tienda](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx). En cada punto se debe confirmar que las configuraciones se completaron de acuerdo con las características de operación de la tienda.
+
+<div class="alert alert-warning">
+ <p>La lista de comprobación indicada anteriormente enumera las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. El <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">equipo de implementación</a> de cada tienda es responsable de definir las funcionalidades y configuraciones que se deben aplicar para producir la experiencia de compra deseada para los clientes. Recomendamos comprobar todos los aspectos operativos de la tienda y añadirlos a la lista en caso de que no estén incluidos.</p>
+</div>
+
+## 3. Configuración del dominio y la cuenta
+
+Después de completar las configuraciones internas de la tienda se deben realizar algunos pasos para la configuración del dominio y la cuenta VTEX. Estos ajustes no dependen de la fecha prevista para el go live, pero deben realizarse antes de la etapa de pruebas.
+
+1. [Comprobar dominio en las redes CDN](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#conferir-dominio-nos-cdns): confirmar que el dominio no esté registrado previamente en [Cloudfront](https://aws.amazon.com/es/cloudfront/?nc1=h_ls) o [Azion](https://www.azion.com/es/).
+2. [Configurar registro CAA](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#configurar-registro-caa): indicar que la autoridad de certificación (CA) **Let's Encrypt** está autorizada para generar y renovar certificados que acrediten la identidad del dominio. Este paso es necesario si hay un registro CAA en el servidor DNS.
+3. [Añadir cuenta en producción](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#colocar-conta-em-producao): activar la cuenta VTEX en producción. Aun después de la activación, la tienda sigue sin estar disponible para clientes externos. Solo se podrán ver y comprar productos en la tienda después de la finalización del go live, según los pasos que se describen en las próximas secciones de este artículo.
+
+<div class="alert alert-warning">
+ <p>Desde el momento en que la cuenta se active en producción, todos los pedidos se cobrarán automáticamente y el <a href="https://help.vtex.com/es/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322#valores-da-receita-aprovada">take rate</a> se aplicará según el plan acordado con VTEX. Esto incluye los pedidos realizados en `{nombredelatienda}.myvtex.com`, incuso si fueron realizados como prueba.</p>
+</div>
+
+Para más información, consulta el artículo [Configuración](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX), que forma parte de la serie [Go live](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/1iP90RcJvlrfQhnlxM54wo).
+
+## 4. Pruebas antes del go live
+
+Recomendamos llevar a cabo pruebas antes del go live para observar el comportamiento de la tienda y evitar errores o problemas en el lanzamiento oficial. En las siguientes secciones, explicamos los dos tipos de prueba más comunes: [Quality Assurance (QA)](#quality-assurance-qa) y [User Acceptance Testing (UAT)](#user-acceptance-testing-uat).
+
+VTEX permite crear entornos independientes para estas pruebas. Cuando se crea un entorno de pruebas, se deben replicar las configuraciones del entorno principal que se van a probar. Por ejemplo, si se desea probar el funcionamiento de una promoción, se deben configurar todos los elementos requeridos para simular un escenario en el que se aplicaría una promoción, tales como productos, precios, logística, checkout, medios de pago.
+
+Para planificar una fase de pruebas ponte en contacto con [nuestro equipo de soporte](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy), que es el canal para [contratar un entorno de pruebas](https://help.vtex.com/es/tutorial/contratar-ambiente-de-testes--2nmZAHlfQoGsCWmEWGIoGy).
+
+<div class="alert alert-info">
+ <p>Si la tienda fue<a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#entorno-de-desarrollo"> creada utilizando VTEX IO</a>, puedes realizar pruebas A/B entre workspaces, es decir, comparar el rendimiento de entornos de desarrollo de storefront. Para más información, consulta la guía de desarrolladores<a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing"> Running A/B tests</a>.</p>
+</div>
+
+### Quality Assurance (QA)
+
+La fase de pruebas de QA es la garantía de calidad mediante el proceso de verificación y validación de todos los aspectos de la tienda y de sus funcionalidades antes de que se pongan a disposición del público general. Esto conlleva probar a fondo todos los elementos, desde la facilidad de navegación y el rendimiento del sitio web hasta los distintos escenarios de flujo de compra, procesamiento de pagos e integraciones de sistemas.
+
+El objetivo es identificar y corregir cualquier problema, error o falla para garantizar que la tienda esté lista y cumpla con el alcance previsto para el MVP del lanzamiento. En esta etapa es importante documentar bugs y errores y planificar su corrección antes de la fecha del go live.
+
+### User Acceptance Testing (UAT)
+
+Las pruebas UAT (User Acceptance Testing), o pruebas de aceptación de usuario, representan la última fase de las pruebas en que usuarios finales validan y verifican si la tienda cumple con las expectativas y funcionalidades requeridas para el MVP. Generalmente, este tipo de prueba incluye al equipo de la tienda y, en algunos casos, un grupo seleccionado de clientes.
+
+Durante las pruebas UAT, los probadores exploran el sitio web, realizan pedidos de prueba y evalúan la experiencia general del usuario. Esta fase es otra oportunidad para informar, documentar y corregir cualquier problema o comportamiento indeseado en la experiencia antes del lanzamiento oficial, lo que aumenta la probabilidad de éxito después del go live.
+
+## 5. Registro del dominio y solicitud de apuntamiento
+
+Después de concluidas las pruebas y ajustes correspondientes, se debe preparar la tienda para el go live. Siete a tres días antes de la fecha prevista para el lanzamiento oficial, se deben completar las siguientes acciones:
+
+1. [Registrar el dominio en VTEX](https://help.vtex.com/es/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450): hay que acceder a **Configuración de la cuenta** en el Admin VTEX para conectar la dirección de la tienda.
+
+   <div class="alert alert-warning">
+     <p>Después del registro, hay un plazo de siete días para completar el go live. Si la tienda no completa los procedimientos requeridos para el go live en ese periodo, habrá que acceder al registro y guardarlo nuevamente.</p>
+   </div>
+
+2. **Solicitar apuntamiento interno:** hay que abrir un ticket con el [soporte VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy) para solicitar el apuntamiento de DNS interno. El plazo para completar esta solicitud es de hasta tres días laborables.
+
+    El tipo de solicitud enviada debe corresponder a la [tecnología escogida](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para el storefront:
+
+  <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tecnología</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Solicitud</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Store Framework o FastStore (VTEX IO)</td>
+      <td class="t-body pa5" style="min-width: 10rem;">Solicitar el <a href="https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#solicitar-apontamento-io" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">apuntamiento de DNS interno para VTEX IO</a> mediante un ticket con el <a href="https://help.vtex.com/es/support" target="_blank" rel="noopener noreferrer"  class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">soporte VTEX</a>.<br> <br>Para más información, consulta los artículos:<ul><li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-go-live" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Going live with a new store</a> (Store Framework)</li><li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-migrating-storefront-from-legacy-to-io" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Migrating your storefront from Legacy CMS Portal to Store Framework</a></li><li><a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Configuring external DNS for a custom domain</a> (FastStore)</li></ul></td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">CMS Portal Legado</td>
+      <td class="t-body pa5" style="min-width: 10rem;">Si el acceso a la tienda está restringido por una <a href="https://help.vtex.com/es/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">política comercial</a> con una regla condicional y tu storefront fue creado con<a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">CMS Portal Legado</a>, debes solicitar un <a href="https://help.vtex.com/es/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#solicitar-apontamento-especial" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">apuntamiento interno especial</a>. Un ejemplo común son las tiendas B2B que restringen el acceso a empresas preaprobadas. La solicitud de apuntamiento especial se envía a través del <a href="https://help.vtex.com/es/support" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">soporte VTEX</a>, que debe incluir la política comercial y la regla condicional configurada.</td>
+    </tr>
+  </tbody>
+  </table>
+
+Independientemente del tipo de solicitud que se necesite, el ticket para el soporte VTEX debe contener la siguiente información:
+
+- Título que indique la intención de realizar el go live.
+- Si la [tecnología de storefront](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) fue desarrollada en VTEX IO o CMS Portal Legado.
+- URL que se debe apuntar.
+- Horario en que se realizará el apuntamiento interno, entre 9:00 y 17:00 UTC-3.
+- Indicar si la tienda tiene reglas condicionales de [políticas comerciales](https://help.vtex.com/es/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE).
+- Si ya hay un sitio web activo que se esté migrando a VTEX, indicar si se utiliza la red CDN de Azion o Cloudfront.
+
+<div class="alert alert-warning">
+ <p>Después de recibir la confirmación de apuntamiento interno, hay que realizar el apuntamiento común de DNS en hasta cinco días. De lo contrario, el apuntamiento interno se eliminará y habrá que enviar una nueva solicitud.</p>
+</div>
+
+## 6. Go live
+
+Durante el go live, después de la confirmación del apuntamiento interno realizado en la etapa anterior, será necesario llevar a cabo el apuntamiento de DNS y notificar a VTEX:
+
+1. [Realizar el apuntamiento DNS:](https://help.vtex.com/es/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dnshttps://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dns) en la zona DNS del dominio, crear una entrada de tipo CNAME en el subdominio deseado para el destino ``{dominio}.cdn.vtex.com``. El ``{dominio}`` debe ser el mismo que está registrado en VTEX.
+
+   <div class="alert alert-warning">
+    <p>La propagación del apuntamiento DNS puede tomar de 24 a 48 horas para completarse. Esto significa que la dirección configurada puede no estar accesible a todo el mundo justo después de la configuración.</p>
+   </div>
+
+2. [Notificar el apuntamiento:](https://help.vtex.com/es/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#notificar-apontamento) para que la tienda esté disponible al público general, se debe notificar a la plataforma VTEX que el apuntamiento fue realizado. Para esto, hay que guardar nuevamente la **Configuración de la cuenta** en el Admin VTEX.
+
+   <div class="alert alert-info">
+    <p>Si la tienda fue creada con<a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#faststore"> FastStore</a>, también se deben seguir los pasos descritos en el artículo<a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns"> Configuring external DNS for a custom domain</a>.</p>
+   </div>
+
+Luego de completar las etapas anteriores, la tienda estará disponible en el dominio registrado para que los clientes puedan entrar y hacer compras.
+
+## 7. Acciones después del go live
+
+Después del lanzamiento oficial de la tienda, hay varias acciones importantes que se deben tomar para garantizar que los clientes tengan acceso a la dirección correcta y para monitorear el rendimiento de ventas y navegación del sitio web.
+
+### Configurar redirecciones
+
+Después del go live, se puede acceder a la tienda en el [dominio registrado](https://help.vtex.com/es/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#cadastrar-dominio-na-vtex). Sin embargo, puede que sea necesario redirigir direcciones antiguas o una dirección sin subdominio `www` para garantizar el acceso a la dirección de la tienda nueva. Recomendamos seguir los tutoriales de los siguientes artículos:
+
+- [Redirección de otras direcciones](https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ)
+- [Configurar acceso sin www](https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278)
+
+### Monitorear el rendimiento de la tienda
+
+Recomendamos monitorear el rendimiento de la tienda después del lanzamiento desde el menú de [Dashboards](https://help.vtex.com/es/tutorial/visao-geral-dashboards--1yn2nZUoXtDO3teTEJsCNl) en el Admin VTEX, que incluye las siguientes páginas:
+
+- [Vista general:](https://help.vtex.com/es/tutorial/vista-general-de-la-tienda--P8ahguoRs0U3PzmXg2wuQ) métricas principales que afectan los ingresos de las tiendas. Este dashboard monitorea los principales indicadores de la evolución de ventas mediante los recursos de análisis de tendencias de pedidos, tasa de conversión y gráficos del embudo de ventas.
+- [Desempeño de ventas:](https://help.vtex.com/es/tutorial/desempeno-de-ventas--3DMube0sEsK9vPcRYGas72) dashboard que control para el comercio unificado, que ayuda a las tiendas a ampliar su negocio y tomar decisiones con mayor precisión.
+
+Además de las herramientas disponibles en el Admin VTEX, puedes monitorear el rendimiento de la tienda a través de [Google Analytics](https://analytics.google.com/analytics/web/) si fue previamente configurado. Para más información, accede a la guía [Configurar Google Analytics 4 en una tienda VTEX](https://help.vtex.com/es/tutorial/como-configurar-google-analytics-em-loja-vtex--G2P0rmSrEiqCcmUMyUUwG).
diff --git a/docs/tracks/es/preco-base-definicao-de-conceito.md b/docs/tracks/es/preco-base-definicao-de-conceito.md
index a785494bb..9478731e8 100644
--- a/docs/tracks/es/preco-base-definicao-de-conceito.md
+++ b/docs/tracks/es/preco-base-definicao-de-conceito.md
@@ -18,7 +18,7 @@ trackSlugES: precios-101
 
 El Precio Base de un SKU es el valor calculado a través de la combinación entre el **Precio de Costo** y el **Markup**, el margen de ganancia deseado con la venta del SKU. Es el __precio de referencia__ de un SKU para todas las tablas de precio. 
 
-![base-price-es](https://images.ctfassets.net/alneenqid6w5/14OYPLF5k6gNJhSUZ5OE53/9b59c8c88d39347707be5054d948ad91/base-price-es.png)
+![base-price-es](//images.ctfassets.net/alneenqid6w5/14OYPLF5k6gNJhSUZ5OE53/9b59c8c88d39347707be5054d948ad91/base-price-es.png)
 
 Este **precio base** puede combinarse con una **regla de precio** aplicada a la tabla de precios. Si no existe regla de precio registrada, el precio de venta en una tabla será el propio precio base.
 
diff --git a/docs/tracks/es/preco-fixo-definicao-de-conceito.md b/docs/tracks/es/preco-fixo-definicao-de-conceito.md
index 63dbaebd5..3828042db 100644
--- a/docs/tracks/es/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/es/preco-fixo-definicao-de-conceito.md
@@ -74,7 +74,7 @@ Digamos que se registren dos precios fijos para el mismo SKU. Además, ambos tie
 
 Por ejemplo: el primer precio fijo es __$ 50.00__ y ​​su programación va de __10h a 16h__. Ya el segundo es __$ 25.00__, solo que está programado de __12h a 20h del mismo día__. En este caso, *entre las 12h y las 16h*, los dos precios fijos compiten entre sí. Por lo tanto, el valor de __$ 25.00__ será el precio de venta del SKU en este horario en común.
 
-![fixed price - example2](https://images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
+![fixed price - example2](//images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
 
 ### Competencia por el Criterio de Ítems Mínimos en el Carrito 
 
@@ -84,7 +84,7 @@ Imagine que registramos un precio fijo de $ 200.00 para __dos o más ítems en e
 
 ¿Cuál sería el precio aplicado para 5 o más ítems? El precio de venta será de $ 100.00, visto que el sistema prioriza el valor más bajo.
 
-![fixed price - example1](https://images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
+![fixed price - example1](//images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
 
 ## Ejemplos
 
diff --git a/docs/tracks/es/prerequisites-for-using-instore.md b/docs/tracks/es/prerequisites-for-using-instore.md
index f22c83012..ff3610e11 100644
--- a/docs/tracks/es/prerequisites-for-using-instore.md
+++ b/docs/tracks/es/prerequisites-for-using-instore.md
@@ -3,8 +3,8 @@ title: 'Requisitos previos para usar VTEX Sales App'
 id: 1wtAanSRA3g2316dw7bw8u
 status: PUBLISHED
 createdAt: 2020-06-28T13:28:33.600Z
-updatedAt: 2023-05-31T15:30:38.223Z
-publishedAt: 2023-05-31T15:30:38.223Z
+updatedAt: 2024-06-27T16:50:09.189Z
+publishedAt: 2024-06-27T16:50:09.189Z
 firstPublishedAt: 2020-06-28T13:41:36.817Z
 contentType: trackArticle
 productTeam: Shopping
@@ -29,15 +29,12 @@ Para mantener el equipo y el buen funcionamiento de tu operación, es importante
 
 ### _Tablets, smartphones_ y computadores
 
-La aplicación VTEX Sales App funciona en _tablets_ y _smartphones_ con sistemas operativos **Android 6.0** (o superior) e **iOS 9** (o superior).
+Se recomienda que los dispositivos estén actualizados a la última versión del sistema operativo o, como mínimo, utilizar una de las:
 
-Algunos ejemplos de dispositivos que se pueden utilizar:
+* Tres versiones más recientes de iOS, o
+* Cuatro últimas versiones de Android.
 
-* Tablet Samsung Galaxy Tab A Note
-* Motorola G4
-* Samsung S8
-
-Recomendamos que los dispositivos utilizados para acceder a VTEX Sales App tengan chips 4G para el acceso a Internet. De este modo, tu tienda seguirá funcionando con normalidad aunque la red Wi-Fi tenga problemas.
+Al acceder a VTEX Sales App, los dispositivos utilizados deben contar con chips 4G para conexión a internet. De esta forma, tu tienda seguirá funcionando con normalidad, incluso en situaciones en las que la red wifi presente problemas.
 
 VTEX Sales App también funciona en computadores con sistema operativo **Windows**, siempre que se cumplan los siguientes requisitos mínimos:
 
@@ -85,6 +82,15 @@ Para imprimir la factura electrónica y los recibos de tarjeta, necesitarás una
 ## Partners
 
 VTEX tiene una serie de _partners_ que hacen posible la operación de las tiendas físicas. Cada _partner_ tiene un papel específico que desempeñar para que todo el proceso de venta se desarrolle sin problemas.
+Entre estos partners se encuentran:
+
+- Integración con PDV:
+    - Jitterbit
+    - Neomode
+- Integración de pagos:
+    - Pagarme
+    - Adyen
+    - Cielo
 
 VTEX tiene un contrato estándar con estos _partners_ para facilitar la implementación de sus productos, pero depende de ti negociar mejores condiciones directamente con ellos.
 
diff --git a/docs/tracks/es/prices-module-overview.md b/docs/tracks/es/prices-module-overview.md
index 8690b1fa0..e1e11ac17 100644
--- a/docs/tracks/es/prices-module-overview.md
+++ b/docs/tracks/es/prices-module-overview.md
@@ -3,8 +3,8 @@ title: 'Precios - Visión General'
 id: 3N9xYhnampRQOrfaTAOxNu
 status: PUBLISHED
 createdAt: 2019-07-09T19:26:54.473Z
-updatedAt: 2023-03-29T19:18:12.146Z
-publishedAt: 2023-03-29T19:18:12.146Z
+updatedAt: 2023-08-21T17:16:35.856Z
+publishedAt: 2023-08-21T17:16:35.856Z
 firstPublishedAt: 2019-07-11T21:35:16.813Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -20,4 +20,4 @@ Pricing posee diversas funcionalidades que permiten usar diferentes estrategias
 
 **Lista de precios** - En esta sección, debe registrar los precios de sus productos. Es en esta área que puede consultar e ingresar los precios de los SKUs para cada **tabla de precio** existente en su tienda.
 
-**Reglas de precio** - Esta sección permite crear reglas para las tablas de precio de su tienda. Las reglas de precio son como funciones que modifican los precios base que se registran en el área Lista de Precios.
+**Reglas de precios** - Esta sección permite crear reglas para las tablas de precio de su tienda. Las reglas de precio son como funciones que modifican los precios base que se registran en el área Lista de Precios.
diff --git a/docs/tracks/es/pricing-system-architecture.md b/docs/tracks/es/pricing-system-architecture.md
index a10c07a0a..0ab02e1b6 100644
--- a/docs/tracks/es/pricing-system-architecture.md
+++ b/docs/tracks/es/pricing-system-architecture.md
@@ -3,8 +3,8 @@ title: 'Arquitectura del sistema de Precios'
 id: 7GptzvlPDVM11ojEjywIQx
 status: PUBLISHED
 createdAt: 2019-07-04T13:51:00.418Z
-updatedAt: 2022-07-27T20:39:31.113Z
-publishedAt: 2022-07-27T20:39:31.113Z
+updatedAt: 2024-04-22T19:20:30.485Z
+publishedAt: 2024-04-22T19:20:30.485Z
 firstPublishedAt: 2019-07-17T19:40:40.258Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -33,7 +33,7 @@ Estos pueden ser:
 
 A continuación, vemos un esquema de cómo se relacionan los conceptos de *precios*, *tabla de precios* y *contextos*:
 
-![Architecture-ES](https://images.ctfassets.net/alneenqid6w5/6bnxEox2mBlC6eFRoXv2B2/c8275d94ff8ec1867467a22eeed50464/Architecture__3_.svg)
+![Architecture-ES](//images.ctfassets.net/alneenqid6w5/6bnxEox2mBlC6eFRoXv2B2/c8275d94ff8ec1867467a22eeed50464/Architecture__3_.svg)
 
 ## Precio calculado
 
@@ -47,24 +47,24 @@ El módulo de precios considera 4 criterios para calcular el precio calculado pa
 - Precio Fijo
 
 1. Si el SKU tiene apenas registrado el *precio base*, el precio calculado para una determinada tabla de precios será igual al **precio base**.
-![rule1-ES](https://images.ctfassets.net/alneenqid6w5/4R46AGzDiANh7Qvki4aAFb/585544b840165564ed86a740ae90850d/rule1__2_.svg) 
+![rule1-ES](//images.ctfassets.net/alneenqid6w5/4R46AGzDiANh7Qvki4aAFb/585544b840165564ed86a740ae90850d/rule1__2_.svg) 
 
 2. Si el SKU tiene el *precio base* y una *regla de precio* configurada para una determinada tabla de precios, el precio calculado será igual al **precio base modificado por la regla de precio**.
-![rule2-ES](https://images.ctfassets.net/alneenqid6w5/6G50mQEFbvLdoS0GshmqrZ/45c8762d46b0cca57ec96505db2b708f/rule2__2_.svg) 
+![rule2-ES](//images.ctfassets.net/alneenqid6w5/6G50mQEFbvLdoS0GshmqrZ/45c8762d46b0cca57ec96505db2b708f/rule2__2_.svg) 
 
 3. En otro escenario, vamos a considerar un SKU con *precio base*, *regla de precio* y *redondeo de precios*. **El precio calculado para una determinada tabla de precio se calculará mediante una combinación de estos tres factores**. Primero, el precio base se modificará por la regla de precio. Después de esto, se producirá el redondeo por la regla de precio psicológico.
-![rule3-ES](https://images.ctfassets.net/alneenqid6w5/3FEUQbPoblkpqqQpBrzUjC/cb730b634996a8f57356b794353f63d2/rule3__2_.svg)
+![rule3-ES](//images.ctfassets.net/alneenqid6w5/3FEUQbPoblkpqqQpBrzUjC/cb730b634996a8f57356b794353f63d2/rule3__2_.svg)
 
 4. Finalmente, si un SKU tiene un *precio fijo* registrado, **el precio calculado para una determinada tabla de precios será igual al precio fijo**. Este precio tiene un peso superior a los otros precios. De esta manera, el módulo de precios *ignora los otros precios* si encuentra un precio fijo asociado a un SKU.
-![rule4-ES](https://images.ctfassets.net/alneenqid6w5/1IO167lvTydJX8UqYSgdWi/58103cb411586d9bbe924ecc11680155/rule4__3_.svg)
+![rule4-ES](//images.ctfassets.net/alneenqid6w5/1IO167lvTydJX8UqYSgdWi/58103cb411586d9bbe924ecc11680155/rule4__3_.svg)
 
 ## Validar precio calculado
 
 Para verificar el precio de venta de un SKU en una determinada tabla de precios, puede consultar el **valor del precio computado** en la sección de **Lista de precios** del admin de VTEX. En el siguiente ejemplo, vemos que el precio computado del **SKU 14** para la **tabla de la política comercial 1** es igual a **334.62**:
 
-![computed-price-es](https://images.ctfassets.net/alneenqid6w5/4bUfMSdT0nD8ySiMZ5QztD/6e34043f53fbb6296a3d82c9d6892aa4/computed-price-es.png)
+![computed-price-es](//images.ctfassets.net/alneenqid6w5/4bUfMSdT0nD8ySiMZ5QztD/6e34043f53fbb6296a3d82c9d6892aa4/computed-price-es.png)
 
-También puede verificar cuál es el precio computado de un SKU en una tabla de precios **haciendo una llamada por API**. Para esto, debe hacer un **GET** en el endpoint [Get Computed Price by price table or trade policy](https://developers.vtex.com/vtex-rest-api/reference/getcomputedpricebypricetable).
+También puede verificar cuál es el precio computado de un SKU en una tabla de precios **haciendo una llamada por API**. Para esto, debe hacer un **GET** en el endpoint [Get Computed Price by price table or trade policy](https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-).
 
 Esta llamada devuelve el `sellingPrice` de un SKU en la tabla de precio `1`. **Esta es la información que *Pricing* entrega como *precio de venta* del SKU**.
 
diff --git a/docs/tracks/es/printing-an-order-summary.md b/docs/tracks/es/printing-an-order-summary.md
index 9ffef6d25..15bf09e60 100644
--- a/docs/tracks/es/printing-an-order-summary.md
+++ b/docs/tracks/es/printing-an-order-summary.md
@@ -3,8 +3,8 @@ title: 'Impresión del resumen del pedido'
 id: 5UeqJA3sHp5goJacvHwPoS
 status: PUBLISHED
 createdAt: 2021-08-05T14:40:53.752Z
-updatedAt: 2023-05-31T15:23:48.750Z
-publishedAt: 2023-05-31T15:23:48.750Z
+updatedAt: 2023-07-26T19:01:33.402Z
+publishedAt: 2023-07-26T19:01:33.402Z
 firstPublishedAt: 2021-08-05T14:47:18.680Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,9 +16,9 @@ trackSlugES: instore-utilizando-la-aplicación
 
 Al finalizar un pedido utilizando VTEX Sales App, es posible imprimir un resumen del mismo si esta personalización está habilitada y si hay un dispositivo de impresión correctamente configurado.
 
-Para ello, el vendedor puede hacer clic en el botón `Imprimir pedido` en la pantalla del pedido finalizado, como se ilustra a continuación. Otra opción es configurar inStore para que imprima el resumen del pedido automáticamente en cuanto se finalice el pedido.
+Para ello, el vendedor puede hacer clic en el botón `Imprimir pedido` en la pantalla del pedido finalizado, como se ilustra a continuación. Otra opción es configurar VTEX Sales App para que imprima el resumen del pedido automáticamente en cuanto se finalice el pedido.
 
-![15. Configurar impressão de resumo do pedido - 1 - ES](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/5a3aabdd6ad7b66958a744955fbfa979/print-order-es.png)
+![15. Configurar impressão de resumo do pedido - 1 - ES](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/5a3aabdd6ad7b66958a744955fbfa979/print-order-es.png)
 
 Para habilitar la impresión del resumen del pedido, sigue los pasos descritos a continuación.
 
@@ -32,7 +32,7 @@ A continuación, debes configurar una impresora conectada a VTEX Sales App para
 
 ### Requisitos previos
 
-Para emparejar inStore con una impresora, deben cumplirse los siguientes requisitos previos:
+Para emparejar VTEX Sales App con una impresora, deben cumplirse los siguientes requisitos previos:
 
 * Utilizar un computador con sistema operativo Windows 7 o superior.
 * Si no tienes VTEX Sales App en tu computador, instala la aplicación siguiendo nuestra guía de [Instalación](https://help.vtex.com/es/tracks/instore-usando-el-app--4BYzQIwyOHvnmnCYQgLzdr/2rPSJ8519UCCZo5uEBkqxh).
@@ -50,13 +50,13 @@ Después de obtener el AppKey y el AppToken, sigue los pasos a continuación.
 2. Abre la aplicación VTEX Sales App e introduce el nombre de la tienda en la que quieres configurar la impresora.
 3. En el menú principal de inStore, en la sección **Configuración**, haz clic en la opción <i class="fas fa-cog"></i> **Configurar el dispositivo**, ilustrada a continuación.
 
-![15. Configurar impressão de resumo do pedido - 2 - ES](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/901224ec3c5342310a3ad2c54274caf8/configuracion-es.png)
+![15. Configurar impressão de resumo do pedido - 2 - ES](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/901224ec3c5342310a3ad2c54274caf8/configuracion-es.png)
 
 <ol start="4">
   <li>A continuación, verás el resumen del dispositivo configurado. Si es la primera vez que se realiza esta configuración, los campos en la pantalla estarán vacíos, como se muestra en la siguiente imagen. Si un dispositivo ha sido configurado anteriormente, verás el <b>Nombre del dispositivo</b> y la <b>Impresora estándar</b>. Haz clic en el botón <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">Editar</span>.</li>
 </ol>
 
-![15. Configurar impressão de resumo do pedido - 4 - ES](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/f8ad79cb1907905f230318c0c25ad964/image_4__1_.png)
+![15. Configurar impressão de resumo do pedido - 4 - ES](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/f8ad79cb1907905f230318c0c25ad964/image_4__1_.png)
 
 <ol start="5">
   <li>Rellena el formulario con los campos descritos a continuación.
diff --git a/docs/tracks/es/product-details.md b/docs/tracks/es/product-details.md
index 5936dd110..0a5b456e4 100644
--- a/docs/tracks/es/product-details.md
+++ b/docs/tracks/es/product-details.md
@@ -16,7 +16,7 @@ trackSlugES: instore-usando-el-app
 
 Al hacer clic en los detalles de un producto que aparece en los resultados de búsqueda de VTEX Sales App, o al leer el código de un producto, el vendedor se dirige a la pantalla de detalles del producto.
 
-![instore-pdp-es](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/89db3673ca4d66e8c5af7e18dcb4c296/pdp-es.png)
+![instore-pdp-es](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/89db3673ca4d66e8c5af7e18dcb4c296/pdp-es.png)
 
 Esta pantalla muestra el nombre del producto, su galería de fotos, variaciones, descripción y disponibilidad. El vendedor puede, en esta pantalla, agregar el producto al carrito.
 
diff --git a/docs/tracks/es/product-integration-errors-with-amazon.md b/docs/tracks/es/product-integration-errors-with-amazon.md
new file mode 100644
index 000000000..dd0ef19c6
--- /dev/null
+++ b/docs/tracks/es/product-integration-errors-with-amazon.md
@@ -0,0 +1,148 @@
+---
+title: 'Errores de integración de productos Amazon'
+id: 4HsdzgoYxgQNtCBCRttKDA
+status: PUBLISHED
+createdAt: 2023-06-29T19:08:38.476Z
+updatedAt: 2023-09-26T15:02:03.011Z
+publishedAt: 2023-09-26T15:02:03.011Z
+firstPublishedAt: 2023-06-29T22:27:35.313Z
+contentType: trackArticle
+productTeam: Channels
+slug: errores-de-integracion-de-productos-amazon
+locale: es
+trackId: 6sgd4Pagy3wNsWKBvmIFrP
+trackSlugES: errores-de-integracion-de-productos-amazon
+---
+
+Hay varias razones por las que un producto entre Amazon y una tienda VTEX puede no integrarse, y para cada una de ellas hay una notificación que indica la naturaleza del error. Puedes ver el mensaje de error en el Admin VTEX en el módulo **Marketplace > Conexiones > Productos**, o también puedes acceder a él mediante la barra de búsqueda. Al acceder a la página, filtra por el marketplace Amazon y haz clic en el producto para ver el mensaje.
+
+Después de resolver un error, debes volver a procesar manualmente la integración del stock del SKU en cuestión. Puedes hacerlo en el mismo lugar donde accediste al error al hacer clic en **Acciones > Reprocesar**.
+
+En este artículo, describimos los siguientes errores:
+
+- [Errores en la plantilla de mapeo de categorías y atributos de Amazon](#Errores-en-la-plantilla-de-mapeo-de-categorias-y-atributos-de-Amazon)
+- [Errores de falta de atributos obligatorios en Amazon](#Errores-de-falta-de-atributos-obligatorios-en-Amazon)
+- [Errores de divergencia entre los catálogos de VTEX y Amazon (match de anuncios)](#Errores-de-divergencia-entre-los-catálogos-de-VTEX-y-Amazon (match-de-anuncios))
+- [Errores de token y permisos de Amazon](#Errores-de-token-y-permisos-de-Amazon)
+- [Errores de configuración en la integración de Amazon](#Errores-de-configuracion-en-la-integracion-de-Amazon)
+- [Errores de envío de la categoría global VTEX](#Errores-de-envio-de-la-categoria-global-VTEX)
+- [Aviso de SKU inactivo](#Aviso-de-SKU-inactivo)
+
+## Errores en la plantilla de mapeo de categorías y atributos de Amazon
+
+- **La categoría global VTEX del SKU no se rellenó en la plantilla de mapeo o se rellenó incorrectamente**
+
+  Este error se produce cuando la [categoría global](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) no está configurada o está configurada incorrectamente. Amazon utiliza la categoría global registrada en VTEX para realizar el mapeo de los productos. Por lo tanto, es importante que la equivalencia entre la categoría global de VTEX y las categorías generales de Amazon se realice correctamente.
+
+  Para resolver este error, [configura la categoría global](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#configuracao-da-categoria-global) de tu producto.
+
+- **No se encontró la especificación (X) rellenada en la plantilla de mapeo en la especificación del producto o del SKU en tu catálogo VTEX**
+
+  Este error se produce cuando se rellena la plantilla con una especificación que no existe en el catálogo VTEX. Para resolver este error, debes registrar una[ especificación de producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) o [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr). Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) y consulta la pestaña VALORES VÁLIDOS.
+
+- **El valor (X) en la plantilla de mapeo no es un valor de atributo/especificación aceptado por Amazon**
+
+  Este error se produce cuando la especificación X no es aceptada por Amazon. Debes[ registrar una especificación](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) aceptada por Amazon. Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) y consulta la pestaña VALORES VÁLIDOS.
+
+- **El ID de categoría global VTEX del producto no se encontró en la plantilla de mapeo**
+
+  Este error se produce cuando la[ categoría global](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) no está configurada o está configurada incorrectamente. Para resolver este error,[ configura la categoría global](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#configuracao-da-categoria-global) de tu producto.
+
+- **El valor en la plantilla de mapeo para la especificación "Material" o "Department" no es un valor de atributo/especificación aceptado por Amazon**
+
+  En ambos errores, la [categoría global VTEX](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) del producto seleccionado por el seller requiere el registro obligatorio de los atributos **Department** o **Material** en el producto y que se rellenen en la [plantilla de mapeo](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento). [Registra](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) el atributo en el producto y rellena la plantilla según el ejemplo a continuación:
+
+|**CategoryID**|**VariationTheme**|**Type**|**VTEXSpecification**|**AmazonSpecification**|**VTEXValue**|**AmazonValue**|
+| :- | :- | :- | :- | :- | :- | :- |
+|3||Information|Género|Department|Femenino|Female|
+
+- **No se cargó la plantilla de mapeo de categorías y atributos**
+
+  Este error se produce porque no se cargó la [plantilla de mapeo de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento). Debes[ rellenar](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#5-preenchimento-da-planilha-de-mapeamento) la plantilla de mapeo de Amazon y [cargar](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#6-upload-da-planilha-de-mapeamento) la plantilla después que esté rellenada.
+
+- **El valor de la especificación (X) en la plantilla no existe en la especificación del producto en VTEX**
+
+  En el error anterior, el atributo mencionado no está registrado en el SKU del catálogo VTEX. Debes [registrar el atributo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) y volver a realizar el [mapeo](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) del producto enviado.
+
+- **La unidad de edad mínima en la plantilla de mapeo no concuerda con la esperada por Amazon**
+
+  La unidad de edad mínima no concuerda con la solicitada por Amazon. Amazon acepta valores en años o meses. Vuelve a realizar el [mapeo](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) con los valores aceptados por el marketplace.
+
+- **Amazon no acepta las variaciones de SKU de la plantilla de mapeo**
+
+  Este error se produce cuando se rellena la columna **VariationTheme** de la plantilla de mapeo de Amazon con un valor que Amazon no acepta. [Verifica los valores aceptados](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#5-preenchimento-da-planilha-de-mapeamento) e ingresa un valor válido en la plantilla de mapeo.
+
+- **El valor en la plantilla de mapeo del atributo "SizeMap" no es un atributo/especificación aceptado por Amazon**
+
+  Rellenaste un valor incorrecto en el atributo SizeMap. Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) y consulta la pestaña VALORES VÁLIDOS.
+
+- **El valor en la plantilla de mapeo para "TargetGender" no es un atributo/especificación aceptado por Amazon**
+
+  Rellenaste un valor incorrecto en la especificación TargetGender. Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) y consulta la pestaña VALORES VÁLIDOS.
+
+- **Los atributos de color y tamaño en este SKU no se encontraron en la plantilla de mapeo**
+
+  No rellenaste el valor de las especificaciones Color y Tamaño, que son obligatorias para la categoría del producto que deseas enviar. Consulta la [plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) para ver los valores aceptados por Amazon y rellena un valor válido en la plantilla de mapeo.
+
+- **El atributo "author" no está registrado en el SKU o no consta en la plantilla de mapeo**
+
+  No registraste el atributo obligatorio Author para el producto que deseas enviar. Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon), consulta la pestaña VALORES VÁLIDOS y [registra una especificación de producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) para ese atributo.
+
+- **El valor en la plantilla de mapeo del atributo "Size" no es un atributo/especificación aceptado por Amazon**
+
+  No rellenaste el valor de la especificación Size correctamente. Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) y consulta la pestaña VALORES VÁLIDOS.
+
+- **El valor en la plantilla de mapeo del atributo "Color" no es un atributo/especificación aceptado por Amazon**
+
+  No rellenaste el valor de la especificación Color correctamente. Para ver los valores aceptados por Amazon, abre la [Plantilla de atributos obligatorios de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) y consulta la pestaña VALORES VÁLIDOS.
+
+## Errores de falta de atributos obligatorios en Amazon
+
+- **El atributo Color no está registrado en el SKU o no consta en la plantilla de mapeo**
+
+  El atributo Color es obligatorio para la categoría del producto que estás enviando a Amazon y no está registrado en el SKU o no fue mapeado en la plantilla de mapeo.
+Debes registrar una [especificación de SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) para el atributo Color y/o volver a realizar el [mapeo](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) del producto enviado.
+
+- **La especificación de producto "TargetGender" es obligatoria para integrar el producto con Amazon**
+
+  La especificación de producto TargetGender es obligatoria para la categoría del producto que estás enviando. Dependiendo de la categoría, Amazon puede llamarla Department o TargetGender. [Registra la especificación de producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) TargetGender y vuelve a realizar el [mapeo](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).
+
+## Errores de divergencia entre los catálogos de VTEX y Amazon (match de anuncios)
+
+- **El SKU ya existe en el catálogo de Amazon y se podría realizar el proceso de matching del mismo entre VTEX y Amazon. Sin embargo, el valor del atributo (X) de este SKU en VTEX es distinto del valor que tiene registrado en Amazon. En VTEX es (X) y en Amazon es (Y).**
+
+  Este error se produce cuando hay divergencias de valores del atributo (datos de las características del SKU) entre el catálogo de Amazon y el de VTEX. Para resolver este error, debes [modificar el valor del atributo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) en la plataforma VTEX para que sea equivalente al [valor del atributo en la plataforma Amazon](https://drive.google.com/uc?export=download&id=1UkcrfPopMg-cnrSDOF0qt51NRIXgzi0r).
+
+## Errores de token y permisos de Amazon
+
+- **El token rellenado en el formulario de configuración de Amazon en VTEX está expirado o no tiene permiso de acceso en este flujo**
+
+  Este error se produce porque el número de serie del **token de autorización de MWS** expiró. Ponte en contacto con Amazon para resolver este problema y vuelve a realizar la [configuración de la integración de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan).
+
+- **Tu cuenta no tiene permiso de Amazon MWS**
+
+  Te falta permiso en Amazon MWS. Para resolver este error, debes ponerte en contacto con Amazon a través de [Amazon Seller Central](https://sellercentral.amazon.com/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fsellercentral.amazon.com%2Fhome&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=sc_na_amazon_v2&openid.mode=checkid_setup&language=en_US&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&pageId=sc_na_amazon_v2&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&ssoResponse=eyJ6aXAiOiJERUYiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiQTI1NktXIn0.Tu8_jE6QC2G-_ocUOfrmbQ5Yzla8DIU8mDM1MWECzOdygOPMJaQPUQ.j9BRXu7ZWuDPBs9t.yNk43-MFTIkvgWYkVs9Oef8u2lDFWlUflCequoOgISLz9wNQ9nCwrQuwuUXxK77ev5JB_00vp8K4iwOGijHX26VL9xaXilgIT8oZOBuq_DCSFLcSvFyne_WjZsRmU2UeE4bKXSYuQphH4Z50b7Q09jYpP5XuN73UUwv8I70m10qNv_GFRCs71bbqTxfteEeNQZ-ot9PZ8Q.oTZEuYQOUvTkfnLq8JaAFQ). Puedes ver más información sobre cuentas en la documentación de Amazon [Administrar la cuenta de AWS](https://docs.aws.amazon.com/es_es/accounts/latest/reference/managing-accounts.html). Para ver más información sobre la política de seguridad en las cuentas de sellers de Amazon, consulta [Seguridad en AWS - Administración de cuentas](https://docs.aws.amazon.com/es_es/accounts/latest/reference/security.html).
+
+## Errores de configuración en la integración de Amazon
+
+- **El valor que aparece en el campo "Nombre para el tipo de envío" en la configuración de la integración de Amazon en VTEX no es igual al que aparece en Amazon Seller Central**
+
+  Este error se produce cuando el valor registrado en el campo **Nombre para el tipo de envío** en la etapa [Configurar la integración de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan) en VTEX difiere del valor registrado en Amazon Seller Central. Consulta la documentación de Amazon Seller Central para aclarar dudas y corregir el problema.
+
+- **El valor que aparece en el campo "SELLER ID" en la configuración de la integración de Amazon en VTEX no es el mismo que aparece en Amazon Seller Central**
+
+  Este error se produce cuando el valor registrado en el campo **Seller ID** en la etapa[ Configurar la integración de Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan) en VTEX difiere del valor registrado en Amazon Seller Central. En efecto, el valor de **Seller ID** que se solicita en la configuración de la integración es el que aparece en Amazon. [Consulta la documentación de Amazon Seller Portal](https://sellercentral.amazon.com/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https%3A%2F%2Fsellercentral.amazon.com%2Fhome&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=sc_na_amazon_v2&openid.mode=checkid_setup&language=en_US&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&pageId=sc_na_amazon_v2&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&ssoResponse=eyJ6aXAiOiJERUYiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiQTI1NktXIn0.jk7RCgyM4a8-ticE3kjb7XXngMJKpyjxxbhlZjiNAG7CbVI5ei2sIQ.IEq--_YXM1lwf15N.c4ZcixdNfbrDYajjTiYzTsIanK5hS2nSY8tVRiAbP9S7o6nmfzHm6QDkOlQ0JVbRMf3qohVVI7tmQWoIwyegOGADsdg5TQbHeAbrhP4mQ3mTofsFSqmf63LwJ4tYq4g_Fu86FOGH-zZAcsDTqZIE8wgQwXfua3zwGvVFFCN_Z_ME1JWimOiwGDqd_ZjKbVICSkhufmAq.kKdpxcDBuoYRqKymaONbwA) para aclarar dudas y corregir el problema.
+
+## Errores de envío de la categoría global VTEX
+
+- **La categoría global VTEX (X) de este SKU no está configurada correctamente en la integración**
+
+  Este error se produce cuando la [categoría global](https://help.vtex.com/es/tutorial/configurando-a-categoria-global--tutorials_188) seleccionada en el mapeo no existe en Amazon. Comprueba el [mapeo de categoría global](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) del producto para asegurarte de que la categoría seleccionada está asociada a Amazon.
+
+## Aviso de SKU inactivo
+
+- **El SKU que intentaste enviar está inactivo en VTEX**
+
+El [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) no está activo en VTEX. Solo se pueden integrar SKU activos. En algunos caos, este error se genera por [colecciones](https://help.vtex.com/es/tutorial/como-deletar-colecao--6C620yHzwsGoS8iaCocAM2) antiguas asociadas a la política comercial de Amazon que contiene SKU inactivos.
+Verifica el status del SKU en el Admin desde el módulo *PRODUCTOS > Catálogo > Productos y SKUs* y, de ser necesario, [activa el SKU](https://help.vtex.com/es/tutorial/ativar-skus-em-massa--4uMZATlSc0kEYiewWKSwEY).
+
diff --git a/docs/tracks/es/promotions-for-specific-scenarios.md b/docs/tracks/es/promotions-for-specific-scenarios.md
index b3a757350..67aad83d1 100644
--- a/docs/tracks/es/promotions-for-specific-scenarios.md
+++ b/docs/tracks/es/promotions-for-specific-scenarios.md
@@ -1,10 +1,10 @@
 ---
 title: 'Promociones para escenarios específicos'
 id: jOu9b69mKbrTDfSJYAawy
-status: CHANGED
+status: PUBLISHED
 createdAt: 2020-01-22T13:55:51.326Z
-updatedAt: 2020-11-27T19:40:32.581Z
-publishedAt: 2020-07-29T22:53:59.120Z
+updatedAt: 2023-10-23T17:08:04.859Z
+publishedAt: 2023-10-23T17:08:04.859Z
 firstPublishedAt: 2020-01-22T15:01:20.187Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -38,7 +38,7 @@ La pantalla de configuración de la promoción ofrece dos listas de SKUs, que pu
 
 Puede, entonces, definir un valor de descuento para cada una de estas listas. Si, por ejemplo, la lista 1 tiene un 10% de descuento y la lista 2 un 5% de descuento, cuando el carrito tenga al menos un producto de cada una de estas listas, se concederá un descuento total del 10% sobre el valor de los ítems de la lista 1 y un descuento del 5% sobre el valor de los ítems de la lista 2.
 
-![Compre Junto - ES](https://images.ctfassets.net/alneenqid6w5/6Heut08iWTOC9Ph1CpVjJ0/255d0f4409b49327640aebba743afe6b/Screenshot_2020-06-24_https_lojadobreno_myvtex_com.png)
+![Compre Junto - ES](//images.ctfassets.net/alneenqid6w5/6Heut08iWTOC9Ph1CpVjJ0/255d0f4409b49327640aebba743afe6b/Screenshot_2020-06-24_https_lojadobreno_myvtex_com.png)
 
 Dos ejemplos de este tipo de promoción serían "Compre un pantalón y gane 10% de descuento en la compra de un cinturón" y "Compre un par de zapatos + un par de calcetines y gane 15% de descuento".
 
@@ -50,7 +50,7 @@ La promoción Más por Menos se utiliza para otorgar un descuento cuando el clie
 
 En la configuración de la promoción Más por Menos, la tienda debe definir a qué colecciones o SKUs se aplicará. Luego, elija el número de ítems en el carrito para que funcione y el número de ítems con descuento.
 
-![Leve mais por menos - ES](https://images.ctfassets.net/alneenqid6w5/2oKj9TshOn5AWpgPHP2UT4/27f982cc7854eccb0ff656f3e6f70606/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_1_.png)
+![Más por menos](//images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/2f8e02eef7f52bdaccf728ff9406ece7/Mas_por_menos.png)
 
 Por ejemplo:
 
@@ -69,7 +69,7 @@ Al configurar la promoción de Descuento Progresivo, la tienda debe definir a qu
 
 Para continuar la progresión del descuento, haga clic en el botón "+". Se agregará una nueva línea y, entonces, podrá agregar un nuevo descuento. Por ejemplo: para los siguientes 2 productos, el cliente recibirá un descuento adicional del 5%. Y así sucesivamente.
 
-![Desconto progressivo - ES](https://images.ctfassets.net/alneenqid6w5/2JgsOt6rikmlj5SeXNEjvo/f245c7434417c86f0d8cccd977d68907/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_2_.png)
+![Desconto progressivo - ES](//images.ctfassets.net/alneenqid6w5/2JgsOt6rikmlj5SeXNEjvo/f245c7434417c86f0d8cccd977d68907/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_2_.png)
 
 Para entender la promoción del Descuento Progresivo con más detalle, vea el artículo <a href="https://help.vtex.com/es/tutorial/descuento-progresivo--tutorials_324">Cómo el Descuento Progresivo funciona</a>.
 
@@ -79,7 +79,7 @@ La promoción Compre y Gane se utiliza para ofrecer flete gratis o un regalo si
 
 El descuento aplicado (flete gratis o regalo) debe definirse en los datos generales de la promoción. Luego, la tienda debe elegir las colecciones o SKUs a los que se aplicará. Finalmente, debe definir la cantidad mínima de ítems en el carrito para que la promoción funcione.
 
-![Compre e Ganhe - ES](https://images.ctfassets.net/alneenqid6w5/3VixYm5a1Yj3Qb30ZSWVWp/054fe69fe18da0a1636309d621adcc59/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_3_.png)
+![Compre e Ganhe - ES](//images.ctfassets.net/alneenqid6w5/3VixYm5a1Yj3Qb30ZSWVWp/054fe69fe18da0a1636309d621adcc59/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_3_.png)
 
 Para entender la promoción Compre y Gane con más detalle, vea el artículo  <a href="https://help.vtex.com/es/tutorial/compre-y-gane--tutorials_322">Cómo funciona la promoción Compre y Gane</a>.
 
@@ -93,22 +93,22 @@ Es importante señalar que esta posibilidad es <strong>válida apenas para una p
 
 Después de rellenar todos [los campos de una promoción regular](https://help.vtex.com/es/tutorial/regular-promotion--tutorials_327) con descuento porcentual, puede seleccionar la opción __Definir la cantidad máxima de ítems afectados por carrito__ en la sección __Restricciones y limitaciones de uso__.
 
-![Limites de itens - ES](https://images.ctfassets.net/alneenqid6w5/4Z5PxhDSo3baaPwtNOuCnM/3ff74fed7b7652368f70fc1dab936000/image__14_.png)
+![Limite itens - ES](//images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/b2df8c53d0e4cb8d144db320ddb983ae/Limite_itens_-_ES.png)
 
 Por defecto, la opción __ilimitado__ está activa, aplicando la promoción a todos los ítems del carrito, como se ilustra en el siguiente diagrama:
 
-![Caso ilimitado ES](https://images.ctfassets.net/alneenqid6w5/7LMJMOT1k3hs8lHbe1BmtJ/811dc4e9f2210817bee4dcaf319443a4/Caso_ilimitado_ES.png)
+![Caso ilimitado ES](//images.ctfassets.net/alneenqid6w5/7LMJMOT1k3hs8lHbe1BmtJ/811dc4e9f2210817bee4dcaf319443a4/Caso_ilimitado_ES.png)
 
 Para restringir el número de ítems del carrito que recibirán el descuento, puede elegir una de las siguientes opciones:
 
 - __Ítems por carrito__: esta configuración limita la aplicación de la promoción a un número de ítems del carrito. Una vez alcanzado el límite, la promoción no se aplicará al resto del carrito. El sistema utiliza el precio como criterio de elección, por lo que los ítems con el precio más bajo serán los primeros en ser afectados.
 
-![Caso por itens ES](https://images.ctfassets.net/alneenqid6w5/4ZE8Sc1reAjgnSzJHlEaar/6891a83f39caa6f6d4e4fc8fc8034dfd/Caso_por_itens_ES.png)
+![Caso por itens ES](//images.ctfassets.net/alneenqid6w5/4ZE8Sc1reAjgnSzJHlEaar/6891a83f39caa6f6d4e4fc8fc8034dfd/Caso_por_itens_ES.png)
 
 - __Ítems por producto__: esta configuración limita la promoción a un número de unidades de cada producto. Como en el siguiente ejemplo, apenas dos unidades por producto serán elegibles para la promoción. El precio más bajo define qué ítems de cada producto son elegibles para la promoción.
 
-![Caso por produto ES](https://images.ctfassets.net/alneenqid6w5/X34R3R6KpYR3xCJdF2AcI/596e61129705dc40d677f5356796c5b2/Caso_por_produto_ES.png)
+![Caso por produto ES](//images.ctfassets.net/alneenqid6w5/X34R3R6KpYR3xCJdF2AcI/596e61129705dc40d677f5356796c5b2/Caso_por_produto_ES.png)
 
 - __Ítems por SKU__: esta configuración limita la promoción a un número de unidades por cada SKU en el carrito. Como en el siguiente ejemplo, apenas dos unidades de cada SKU serán elegibles para la promoción. Como en el caso anterior, será el precio más bajo el que defina los ítems elegibles para la promoción.
 
-![Caso por SKU ES](https://images.ctfassets.net/alneenqid6w5/2l071JBnZtESSnbM2MPAQ1/1b22d7143f3ce6ed219ec6817acfd489/Caso_por_SKU_ES.png)
+![Caso por SKU ES](//images.ctfassets.net/alneenqid6w5/2l071JBnZtESSnbM2MPAQ1/1b22d7143f3ce6ed219ec6817acfd489/Caso_por_SKU_ES.png)
diff --git a/docs/tracks/es/rappi-integration-overview.md b/docs/tracks/es/rappi-integration-overview.md
new file mode 100644
index 000000000..88e14337f
--- /dev/null
+++ b/docs/tracks/es/rappi-integration-overview.md
@@ -0,0 +1,20 @@
+---
+title: 'Visión general  de la Rappi integración'
+id: 7y40IL3ajiukMRHrX3XmC8
+status: PUBLISHED
+createdAt: 2024-05-31T20:24:26.112Z
+updatedAt: 2024-05-31T20:51:33.604Z
+publishedAt: 2024-05-31T20:51:33.604Z
+firstPublishedAt: 2024-05-31T20:51:33.604Z
+contentType: trackArticle
+productTeam: Channels
+slug: vision-general-de-la-rappi-integracion
+locale: es
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugES: integracion-rappi
+---
+
+<div class="alert alert-warning" role="alert">
+  Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.
+</div>
diff --git a/docs/tracks/es/rappi-integration-registration.md b/docs/tracks/es/rappi-integration-registration.md
new file mode 100644
index 000000000..871b872e0
--- /dev/null
+++ b/docs/tracks/es/rappi-integration-registration.md
@@ -0,0 +1,18 @@
+---
+title: 'Registro de integración de Rappi'
+id: 4Wu9gyd5xCRC0MOb5zG9BK
+status: PUBLISHED
+createdAt: 2024-05-31T20:39:08.338Z
+updatedAt: 2024-05-31T20:51:55.857Z
+publishedAt: 2024-05-31T20:51:55.857Z
+firstPublishedAt: 2024-05-31T20:51:55.857Z
+contentType: trackArticle
+productTeam: Channels
+slug: registro-de-integracion-de-rappi
+locale: es
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugES: integracion-de-rappi
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tracks/es/receivables-management.md b/docs/tracks/es/receivables-management.md
index 355d4a3f4..8626ed85a 100644
--- a/docs/tracks/es/receivables-management.md
+++ b/docs/tracks/es/receivables-management.md
@@ -1,10 +1,10 @@
 ---
 title: 'Gestión de cuentas por cobrar'
 id: 4zO5DEg07BSqHsmlBrCgvr
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T18:01:47.594Z
-updatedAt: 2023-03-14T22:07:36.630Z
-publishedAt: 2023-03-14T22:07:36.630Z
+updatedAt: 2023-10-05T14:14:03.274Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:50:17.208Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/es/register-mercado-livre-integration.md b/docs/tracks/es/register-mercado-livre-integration.md
index 4a242d95a..b0db9fa86 100644
--- a/docs/tracks/es/register-mercado-livre-integration.md
+++ b/docs/tracks/es/register-mercado-livre-integration.md
@@ -3,8 +3,8 @@ title: 'Registro del conector de Mercado Libre'
 id: 4YvYdgICMosaEgISOYogsi
 status: PUBLISHED
 createdAt: 2018-08-13T12:33:55.818Z
-updatedAt: 2022-02-03T23:29:27.323Z
-publishedAt: 2022-02-03T23:29:27.323Z
+updatedAt: 2023-07-06T20:21:00.334Z
+publishedAt: 2023-07-06T20:21:00.334Z
 firstPublishedAt: 2018-08-13T14:28:06.574Z
 contentType: trackArticle
 productTeam: Channels
@@ -29,16 +29,7 @@ Cada cuenta VTEX debe estar vinculada a una sola cuenta en Mercado Libre, aunque
 - **ID de la política comercial*:**  ID de la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que se utilizará para la integración con Mercado Libre. Los productos de esta política comercial se enviarán al marketplace.
 - **Formato del título del anuncio*:** regla para el formato del título del anuncio que se publicará en Mercado Libre. Este título puede combinar diferentes atributos del Catálogo, como la *Marca*, el *Nombre del Producto* y el *Nombre del SKU*. Los títulos de los anuncios en Mercado Libre pueden tener un máximo de 60 caracteres. Para personalizar el *Formato del título del anuncio* de un producto, puede [crear un campo](https://help.vtex.com/es/tutorial/criando-um-campo-de-produto--tutorials_106) de producto con el nombre `meli_title`, del tipo `Texto Grande` y la opción `Mostrar Especificación` desactivada.
 - **Actualizar la descripción del anuncio*:** cuando está activado, actualiza automáticamente la descripción del anuncio en Mercado Libre cada vez que se realiza un cambio en la descripción del producto en VTEX. En caso contrario, se mantendrá la descripción original.
-- **Activar la integración de los puntos de recogida*:** cuando está activado, habilita el recurso de recoger los productos en los [puntos de recogida](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/52C1lm8gMovN8v68s6v89d) registrados en VTEX para la tienda principal.
-- **Activar la integración de los puntos de recogida para las cuentas franquicia*:** cuando está activado, habilita el recurso de recoger los productos en los puntos de recogida registrados en VTEX para las cuentas franquicia.
-- **Activar stock para entrega y cotización de flete para cuentas franquicia*:** cuando está activado, habilita el recurso de utilizar el [stock de las cuentas franquicia](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/52C1lm8gMovN8v68s6v89d).
-- **Estrategia de envío de stock (solo es válida si la configuración de stock y cotización para cuentas franquicia está activa):** si tiene una cuenta franquicia, seleccione una de las siguientes opciones:
-   * **Total de los stocks:** utiliza la suma de los stocks de las cuentas franquicia más el stock de la tienda principal.
-   * **Stock máximo:** utiliza solo el mayor stock disponible de la cuenta franquicia.
-- **Estrategia de envío para cotización de flete (solo es válida si la configuración de stock y cotización para cuentas franquicia está activa):** si tiene una cuenta franquicia, seleccione una de las siguientes opciones:
-   * **Más barato:** al optar por un flete más barato, el plazo de entrega es más largo.
-   * **Más rápido:** al optar por un flete más rápido, el precio es más alto.
-- **ID de la tienda oficial en Mercado Libre:** identificador numérico de tres o cuatro dígitos que proporciona Mercado Libre en su contrato comercial cuando un usuario alcanza el status de [Tienda Oficial](https://www.mercadolibre.com.ar/tiendas-oficiales). Debe rellenarse si su tienda tiene este status para que la integración funcione correctamente.
+- **ID de la tienda oficial en Mercado Libre:** identificador numérico que proporciona Mercado Libre en su contrato comercial cuando un usuario alcanza el status de [Tienda Oficial](https://www.mercadolibre.com.ar/tiendas-oficiales). Debe rellenarse si su tienda tiene este status para que la integración funcione correctamente.
 - **Stock mínimo*:** Si la cantidad de ítems de un producto en stock está por debajo del valor introducido, su anuncio se pone en pausa para evitar que se realicen ventas sin stock durante el tiempo de actualización de Mercado Libre por parte de VTEX.
 - **Formato de archivo de las etiquetas de envío*:** elija entre los formatos PDF o JSON (que es compatible con las impresoras Zebra) para imprimir las etiquetas de los productos.
 - **Atributos omitidos en la plantilla del producto:** rellene el campo con los atributos del producto que están registrados en VTEX pero que no desea incluir en Mercado Libre.
diff --git a/docs/tracks/es/registering-the-carrefour-integration.md b/docs/tracks/es/registering-the-carrefour-integration.md
index 08e375f8d..38544e662 100644
--- a/docs/tracks/es/registering-the-carrefour-integration.md
+++ b/docs/tracks/es/registering-the-carrefour-integration.md
@@ -3,8 +3,8 @@ title: 'Configurar registro de la integración del Carrefour'
 id: 2AhqcmRN1mseCsGuGIe6GK
 status: PUBLISHED
 createdAt: 2018-10-08T23:26:55.073Z
-updatedAt: 2022-09-06T22:59:04.246Z
-publishedAt: 2022-09-06T22:59:04.246Z
+updatedAt: 2024-07-02T19:27:42.975Z
+publishedAt: 2024-07-02T19:27:42.975Z
 firstPublishedAt: 2018-10-08T23:51:59.055Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/registering-the-centauro-integration.md b/docs/tracks/es/registering-the-centauro-integration.md
index 1ac0f6c1d..66ff2a0d9 100644
--- a/docs/tracks/es/registering-the-centauro-integration.md
+++ b/docs/tracks/es/registering-the-centauro-integration.md
@@ -3,8 +3,8 @@ title: 'Registro de la integración de Centauro'
 id: 4EqL0hADU1AWvP0gTr4nyq
 status: PUBLISHED
 createdAt: 2020-10-20T18:55:02.489Z
-updatedAt: 2022-01-25T15:55:01.810Z
-publishedAt: 2022-01-25T15:55:01.810Z
+updatedAt: 2024-07-02T19:28:22.448Z
+publishedAt: 2024-07-02T19:28:22.448Z
 firstPublishedAt: 2020-10-20T19:51:24.705Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/registering-the-integration.md b/docs/tracks/es/registering-the-integration.md
index 82ff69b63..167c892bc 100644
--- a/docs/tracks/es/registering-the-integration.md
+++ b/docs/tracks/es/registering-the-integration.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar registro de la integración de la Via'
+title: 'Configurar registro de la integración de la Casas Bahia Marketplace'
 id: 1okse2MybWk04AQoueu88O
 status: PUBLISHED
 createdAt: 2018-09-24T18:45:21.544Z
-updatedAt: 2022-02-07T21:16:28.792Z
-publishedAt: 2022-02-07T21:16:28.792Z
+updatedAt: 2024-07-02T19:20:54.448Z
+publishedAt: 2024-07-02T19:20:54.448Z
 firstPublishedAt: 2018-09-27T22:12:25.372Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/registering-the-netshoes-integration.md b/docs/tracks/es/registering-the-netshoes-integration.md
index 76f6e7a79..71595f904 100644
--- a/docs/tracks/es/registering-the-netshoes-integration.md
+++ b/docs/tracks/es/registering-the-netshoes-integration.md
@@ -3,8 +3,8 @@ title: 'Registro de la integración de Netshoes'
 id: 7o8Vt25LJmAUuMmSWSmWes
 status: PUBLISHED
 createdAt: 2018-09-24T20:27:48.984Z
-updatedAt: 2023-01-05T20:12:16.965Z
-publishedAt: 2023-01-05T20:12:16.965Z
+updatedAt: 2024-07-02T19:19:00.338Z
+publishedAt: 2024-07-02T19:19:00.338Z
 firstPublishedAt: 2018-09-27T15:02:23.717Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/relevance.md b/docs/tracks/es/relevance.md
index 2b5f7e64a..d0d887926 100644
--- a/docs/tracks/es/relevance.md
+++ b/docs/tracks/es/relevance.md
@@ -3,8 +3,8 @@ title: 'Relevancia'
 id: 1qlObWIib6KqgrfX1FCOXS
 status: PUBLISHED
 createdAt: 2020-04-14T13:35:28.989Z
-updatedAt: 2023-01-23T13:48:19.938Z
-publishedAt: 2023-01-23T13:48:19.938Z
+updatedAt: 2024-01-12T22:16:50.165Z
+publishedAt: 2024-01-12T22:16:50.165Z
 firstPublishedAt: 2020-04-14T23:58:35.468Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,7 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
-Las **Reglas de Relevancia** definen el orden de los productos en los resultados de la búsqueda. La disposición de los productos es alterada por la configuración de criterios y prioridades con datos predeterminados utilizados por el Motor de Búsqueda.
+Las **Reglas de relevancia** definen el orden de los productos en los resultados de la búsqueda en las páginas de listado de productos (PLP). La disposición de los productos es alterada por la configuración de criterios y prioridades con datos predeterminados utilizados por el Motor de Búsqueda.
 
 Las Reglas de relevancia solo se aplican en los resultados de búsqueda cuando el orden de los se define por relevancia al realizar una búsqueda en la tienda. Por ejemplo, si un cliente selecciona ordenar los resultados por precio, los ajustes de relevancia no tienen efecto en el orden de los resultados.
 
@@ -23,17 +23,17 @@ Hay dos posibles escenarios de configuración de relevancia:
 - **Criterios de prioridad:** es la forma de forzar que uno o más criterios tengan mayor prioridad entre los demás. En esta situación no hay pesos, porque todos los productos que tienen esta característica se presentarán primero en el resultado de la búsqueda.
 - **Composición de criterios:** es la forma de distribuir los pesos de cada opción, que van de 0 a 10. Aquí no hay un orden entre los criterios, serán los pesos los que definan la relevancia.
 
-![regras-relevancia-1-ES](https://images.ctfassets.net/alneenqid6w5/pWaOZBllEtnkrAxc2kEdJ/cb3cb591c460e22adfcfdcb210443d39/Captura_de_Tela_2022-03-25_a__s_15.24.26.png)
+![criterios-es](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/0b54c302ffac20ed831392a3c7d5135d/criterios-es.png)
 
 La información aplicada para establecer la relevancia es:
 
-- **Descuento (de / por):** criterio que compara el [Precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#precio-de-lista) y el [Precio base](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicion) registrados para determinar si el producto califica para un descuento.
-- **Lanzamiento:** este criterio asigna un valor decreciente automático (entre 1 y 0) a partir de la fecha de registro del producto en la tienda, considerando un intervalo de 90 días. Los productos registrados hoy tendrían un valor de 1 y ese valor disminuiría cada día, hasta convertirse en 0 a partir del día 90. Este valor se multiplica por el peso que introduzca para el criterio **Lanzamiento** para establecer la relevancia.
+- **Descuento:** criterio que compara el [Precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#precio-de-lista) y el [Precio base](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicion) registrados para determinar si el producto califica para un descuento.
+- **Fecha de release:** este criterio asigna un valor decreciente automático (entre 1 y 0) a partir de la fecha de registro del producto en la tienda, considerando un intervalo de 90 días. Los productos registrados hoy tendrían un valor de 1 y ese valor disminuiría cada día, hasta convertirse en 0 a partir del día 90. Este valor se multiplica por el peso que introduzca para el criterio **Fecha de release** para establecer la relevancia.
 - **Más vendidos:** número de pedidos del producto en los últimos 90 días.
 - **Más vendidos por ingresos:** total de ganancia adquirida por el producto en los últimos 90 días.
 - **Popularidad:** número de clics de un producto en los últimos 90 días.
 - **Promoción:** criterio que comprueba si existen [Audiencias de las campañas](https://help.vtex.com/es/tutorial/overview-2--tutorials_326#audiencia-de-campanas) o [Promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N) vinculadas al artículo para determinar si el producto clasifica como promoción.
-- **Score del catálogo:** criterio de desempate del orden basado en el valor registrado en el producto. Lea más sobre el campo en el artículo [Cómo funciona el campo Score](https://help.vtex.com/es/tutorial/como-funciona-el-campo-score--1BUZC0mBYEEIUgeQYAKcae).
+- **Puntuación del catálogo:** criterio de desempate del orden basado en el valor del campo **Puntuación** registrado en el producto. A efectos de la composición de la relevancia, cuanto mayor sea la puntuación, mayor será el peso, es decir, el comportamiento es descendente: se da prioridad a los productos con una puntuación más alta. Más información sobre el campo y su comportamiento en la guía [¿Cómo funciona el campo Puntuación?](https://help.vtex.com/es/tutorial/como-funciona-el-campo-puntuacion--1BUZC0mBYEEIUgeQYAKcae).
 - **Variedad de matriz disponible:** la relevancia se basa en el porcentaje de SKU disponibles por producto. En un escenario donde el _Producto A_ tiene 3 SKU y 3 de ellos están disponibles, y el _Producto B_ tiene 5 SKU y 2 de ellos están disponibles, el _Producto A_ se destaca sobre _Producto B_ porque el porcentaje de SKU es mayor.
 
 El conjunto de distribución de pesos y criterios genera una puntuación para el producto, lo que ayuda a su posicionamiento en el orden del resultado de la búsqueda.
@@ -42,53 +42,61 @@ El conjunto de distribución de pesos y criterios genera una puntuación para el
   <p>Si deseas utilizar los criterios de prioridad, recomendamos agregar solo un criterio en este campo. Agregar más criterios compromete la ordenación de los resultados de búsqueda, ya que solo se considerará el primer criterio.</p>
 </div>
 
-De esta manera, es posible adaptar el comportamiento del resultado de búsqueda a una estrategia específica. Ejemplo: una tienda de moda a menudo recibe nuevas colecciones. El administrador de la tienda opta por priorizar artículos de lanzamiento a productos promocionales. Configura la herramienta de la siguiente manera:
+De esta manera, es posible adaptar el comportamiento del resultado de búsqueda a una estrategia específica.
 
-**Criterios de prioridad:**
+## Ejemplo
 
-- Vacío
+Una tienda de moda a menudo recibe nuevas colecciones. El administrador de la tienda opta por priorizar artículos de lanzamiento a productos promocionales. Configura la herramienta de la siguiente manera:
 
-**Composición de criterios:**
-
-- Popularidad: 7
-- Lanzamiento: 10
-- Más vendidos: 6
-- Más vendidos por ingresos: 6
-- Promoción: 0
-- Descuento (de / por): 0
-- Variedad de matriz disponible: 10
-- Score del catálogo: 0 
+> **Criterios de prioridad:**
+> 
+> - Vacío
+> 
+> **Composición de criterios:**
+> 
+> - Popularidad: 7
+> - Fecha de release: 10
+> - Más vendidos: 6
+> - Más vendidos por ingresos: 6
+> - Promoción: 0
+> - Descuento: 0
+> - Variedad de matriz disponible: 10
+> - Puntuación del catálogo: 0 
 
 Si el administrador de la tienda quiere que el lanzamiento sea siempre la prioridad, puede ajustar la Reglas de relevancia de dos maneras:
 
-**Criterios de prioridad:**
-
-- Lanzamiento
-
-**Composición de criterios:**
-
-- Popularidad: 7
-- Más vendidos: 6
-- Más vendidos por ingresos: 6
-- Promoción: 0
-- Descuento (de / por): 0
-- Variedad de matriz disponible: 10
-- Score del catálogo: 0
-
-**Criterios de prioridad:**
-
-- Vacío
-
-**Composición de criterios:**
-
-- Popularidad: 0
-- Lanzamiento: 10
-- Más vendidos: 0
-- Más vendidos por ingresos: 0
-- Promoción: 0
-- Descuento (de / por): 0
-- Variedad de matriz disponible: 0
-- Score del catálogo: 0
+> **Manera A**:
+> 
+> **Criterios de prioridad:**
+> 
+> - Fecha de release
+> 
+> **Composición de criterios:**
+> 
+> - Popularidad: 7
+> - Más vendidos: 6
+> - Más vendidos por ingresos: 6
+> - Promoción: 0
+> - Descuento: 0
+> - Variedad de matriz disponible: 10
+> - Puntuación del catálogo: 0
+
+> **Manera B**:
+> 
+> **Criterios de prioridad:**
+> 
+> - Vacío
+> 
+> **Composición de criterios:**
+> 
+> - Popularidad: 0
+> - Fecha de release: 10
+> - Más vendidos: 0
+> - Más vendidos por ingresos: 0
+> - Promoción: 0
+> - Descuento: 0
+> - Variedad de matriz disponible: 0
+> - Puntuación del catálogo: 0
 
 ## Configurar Reglas de relevancia
 
@@ -97,6 +105,9 @@ Para cambiar la configuración de Reglas de relevancia, sigue los pasos a contin
 1. En el Admin, haz clic en el módulo **Storefront**.
 2. En **Intelligent Search**, haz clic en **Reglas de relevancia**.
 3. Escoge el criterio cuyo peso deseas cambiar.
-4. Haz clic en los íconos <i class="fas fa-minus"></i> o <i class="fas fa-plus"></i> para definir el número deseado. Si deseas cambiar la posición de un criterio de **Composición de criterios** a **Criterios de prioridad**, solo tienes que arrastrarlo por el ícono <i class="fas fa-grip-vertical"></i> a la parte superior según se muestra aquí. Ten en cuenta que cuando el criterio cambia a criterio de prioridad, no se le puede cambiar el peso.
-![regras-relevancia-ES](https://images.ctfassets.net/alneenqid6w5/iZze1vchSYf9lLFJnfwiT/1c19ad405d3fe291a14626849c805309/regras-relevancia-ES.gif)
+4. Haz clic en los íconos flecha abajo <i class="fas fa-chevron-down"></i> o flecha arriba <i class="fas fa-chevron-up"></i> para definir el número deseado.
+
+   Si deseas cambiar la posición de un criterio de **Composición de criterios** a **Criterios de prioridad**, solo tienes que arrastrarlo por el ícono <i class="fas fa-grip-vertical"></i> a la parte superior según se muestra aquí. Ten en cuenta que cuando el criterio cambia a criterio de prioridad, no se le puede cambiar el peso.
+
+   ![criterios-prioritarios-es](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/1bdaef8e82e1e1801a439a45acb2e4e3/criterios-prioritarios-es.gif)
 5. Para terminar, haz clic en  `Guardar`.
diff --git a/docs/tracks/es/reports-vtex-intelligent-search.md b/docs/tracks/es/reports-vtex-intelligent-search.md
index d447c7833..81da2576d 100644
--- a/docs/tracks/es/reports-vtex-intelligent-search.md
+++ b/docs/tracks/es/reports-vtex-intelligent-search.md
@@ -79,8 +79,8 @@ Para exportar un informe en formato CSV, debe seguir los pasos que se indican a
 
 El informe CSV descargado tiene dos tablas. La primera tabla, que se muestra a continuación, contiene información sobre los términos de búsqueda y las métricas de embudo (desde la columna **ProductsClick** hasta la columna **ProductsSold**), si se ha seleccionado esa opción.
 
-![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
+![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
 
 La segunda tabla, que se muestra a continuación, muestra los datos del periodo seleccionado, mostrando la columna **Date**, que indica la fecha de la búsqueda.
 
-![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
+![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
diff --git a/docs/tracks/es/sale-confirmed.md b/docs/tracks/es/sale-confirmed.md
index 4e858848e..4583072c7 100644
--- a/docs/tracks/es/sale-confirmed.md
+++ b/docs/tracks/es/sale-confirmed.md
@@ -16,4 +16,4 @@ trackSlugES: instore-usando-el-app
 
 El vendedor puede ver la pantalla __Venta confirmada__ con el resumen del pedido cuando termina una venta, o haciendo clic en una venta en la página __Últimas ventas__, a la que puede acceder a través del menú principal de VTEX Sales App. En la página __Últimas ventas__, pueden buscar el pedido por número de pedido o nombre del cliente.
 
-![order-placed-es](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/11ccd0884f76f8407d439678a338b3b3/order-placed-es.png)
+![order-placed-es](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/11ccd0884f76f8407d439678a338b3b3/order-placed-es.png)
diff --git a/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md b/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md
index 85d79b8d6..b0c7b353f 100644
--- a/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md
+++ b/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md
@@ -3,8 +3,8 @@ title: 'Entregas programadas y capacidad de entrega'
 id: 5TuyqHRCCwYMaDv4r8rZdo
 status: PUBLISHED
 createdAt: 2022-03-08T18:30:20.114Z
-updatedAt: 2022-03-08T18:37:54.630Z
-publishedAt: 2022-03-08T18:37:54.630Z
+updatedAt: 2024-03-25T20:07:20.150Z
+publishedAt: 2024-03-25T20:07:20.150Z
 firstPublishedAt: 2022-03-08T18:37:54.630Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -16,7 +16,11 @@ trackSlugES: logistica-101
 
 Una tienda VTEX puede ofrecer entregas programadas a sus clientes. De esta forma, el cliente elige un día de entrega específico para que la tienda y la transportadora le entreguen el pedido en su domicilio. 
 
-Para poner a disposición de los clientes la [entrega programada](https://help.vtex.com/es/tutorial/entrega-programada--22g3HAVCGLFiU7xugShOBi), es necesario incluir ventanas de entrega en la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) de la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-en-vtex--7u9duMD5UQa2QQwukAWMcE) correspondiente. Una vez hecho esto, los períodos y los días disponibles para la entrega programada aparecerán en el checkout de tu tienda. 
+Para poner a disposición de los clientes la [entrega programada](https://help.vtex.com/es/tutorial/entrega-programada--22g3HAVCGLFiU7xugShOBi), es necesario incluir ventanas de entrega en la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) de la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-en-vtex--7u9duMD5UQa2QQwukAWMcE) correspondiente. Una vez hecho esto, los períodos y los días disponibles para la entrega programada aparecerán en el checkout de tu tienda.
+
+<div class="alert alert-warning">
+Para que la <a href="https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> y la <a href="https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidad de entrega</a> funcionen correctamente, debes tener en cuenta que:<p><ul><li>La suma de {<a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID de la política de envío} no puede exceder los 60 caracteres.</li><li>No se debe utilizar espacio en el ID de la <a href="https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">política de envío</a>.</li></ul></p>
+</div>
 
 Es importante tener en cuenta que la disponibilidad de las entregas programadas está en función del servicio que la transportadora contratada (registrada en la política de envío) ofrece a tu tienda. Para conocer la disponibilidad de las ventanas de entrega (o de los periodos de envío) y de la cantidad de ítems/pedidos que aún pueden atenderse en cada ventana de entrega, consulta la página [Capacidad de entrega](https://help.vtex.com/es/tutorial/gestionar-capacidad-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
diff --git a/docs/tracks/es/search-settings.md b/docs/tracks/es/search-settings.md
index 5dba92aa6..c7d82c091 100644
--- a/docs/tracks/es/search-settings.md
+++ b/docs/tracks/es/search-settings.md
@@ -3,8 +3,8 @@ title: 'Configuración de la búsqueda'
 id: 5t75L6lYNwix93l41s1Yrx
 status: PUBLISHED
 createdAt: 2020-08-17T19:50:20.729Z
-updatedAt: 2023-03-30T19:37:35.404Z
-publishedAt: 2023-03-30T19:37:35.404Z
+updatedAt: 2024-04-25T17:06:18.124Z
+publishedAt: 2024-04-25T17:06:18.124Z
 firstPublishedAt: 2020-09-28T20:51:58.291Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,24 +14,38 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
-La configuración de la búsqueda comprende todos los ajustes globales de VTEX Intelligent Search. Esta consta de dos secciones: [Configuración general](#configuracion-general) y [Configuración de filtros](#configuracion-de-filtros).
+La página **Configuración de la búsqueda** comprende la configuración global de VTEX Intelligent Search. Para acceder, en el VTEX Admin ve a **Configuración de la tienda > Intelligent Search > Configuración de la búsqueda**. Esta consta de dos secciones: [Configuración general](#configuracion-general) y [Configuración de filtros](#configuracion-de-filtros).
 
 ## Configuración general
-Son las configuraciones que se ocupan de VTEX Intelligent Search como un todo. Esta funcionalidad está conformada por la opcione:
 
-Utilice las especificaciones de SKU para mostrar productos individuales en los resultados de búsqueda: define las especificaciones que separarán los SKUs en los resultados de búsqueda.
+La configuración general presenta las siguientes opciones relativas a [las especificaciones de productos y SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP):
 
-Supongamos que tiene un producto en los colores rojo y azul como SKUs. Si selecciona el atributo "color" en este campo, el resultado de la búsqueda devolverá dos productos (uno azul y otro rojo) en lugar de uno solo.
-Para agregar una especificación, haga clic en la barra de la funcionalidad y seleccione la especificación que desea. 
+* **Utiliza las especificaciones de SKU para mostrar productos individuales en los resultados de búsqueda**: establece las características que determinarán el orden de los SKU en los resultados de búsqueda.
 
-Para saber más detalles de esta configuración, acceda a [este artículo](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE#).
-![Configuracion geral Intelligent search v4](https://images.ctfassets.net/alneenqid6w5/41W9W07VVWur0rAxScJG9e/74ad0906e2f9c703b3a9ed349e9c9341/configuracion_general_es.png)
+    Supongamos que tienes un producto con los colores rojo y azul como SKU. Si seleccionas el atributo "color" en este campo, el resultado de la búsqueda devolverá dos productos (uno azul y otro rojo) en lugar de uno solo.
+
+    Para agregar una especificación, haz clic en la barra del menú desplegable y selecciona la especificación deseada.
+
+    Consulta la guía [Separar SKUs por especificación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE) para obtener más detalles sobre esta configuración. 
+
+* **Especificaciones buscables:** determina las especificaciones de producto que pueden ser buscadas por el motor de búsqueda.
+
+    Por ejemplo, si una camisa no contiene un color en el nombre del producto o en el SKU, de manera predeterminada, Intelligent Search no identificará este atributo en una búsqueda de "camisa azul", lo que dará como resultado camisas de diferentes colores. Sin embargo, si la especificación de color está configurada como buscable, la búsqueda puede hacer que aparezcan camisas azules en las primeras posiciones.
 
 ## Configuración de filtros
-Esta configuración abarca todos los aspectos de los filtros. Estos son:
 
-- **Orden de filtro:** orden en que los filtros se exhibirán en la tienda. Si no tiene ningún filtro seleccionado en esta área, el orden por  fecto es alfabético. Para agregar un filtro, haga clic en «Agregar», seleccione el filtro y haga clic en «Guardar» para finalizar. Usted puede alterar el orden arrastrando el ícono  a la posición deseada. Para eliminar un filtro, solo debe hacer clic en el ícono <i class="fa-solid fa-trash-can"></i>.
-- **Ocultar filtros:** selección que permite que algunos filtros no se muestren en la tienda. Para ocultar un filtro, solo seleccione el nombre del mismo.
-![Configuracion del filtro](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
-Para más información, acceda a [este artículo](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) más detallado sobre la funcionalidad **Filtros**.
+La configuración de facetas presenta ajustes relacionados con las [facetas](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) mostradas a los clientes de tu tienda durante la búsqueda:
+
+![Configuracion del filtro](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
+
+* **Orden de las facetas:** orden en el que se mostrarán las facetas en la tienda. Si no hay ninguna faceta seleccionada en la sección, el orden predeterminado es alfabético.
+
+    Para agregar una faceta, haz clic en `Agregar`, selecciona la faceta deseada y haz clic en `Guardar`.
+
+    Puedes cambiar la clasificación arrastrando el ícono de puntos <i class="fas fa-grip-vertical"></i> de cada faceta a la posición deseada.
+
+    Para eliminar una faceta, haz clic en el ícono de la papelera <i class="fas fa-trash-alt"></i>.
+
+* **Ocultar facetas:** selección que permite que determinadas facetas no se muestren en la tienda. Para ocultar una faceta, haz clic en el menú desplegable, y a continuación en el nombre de la faceta. 
 
+    Para volver a mostrar una faceta, haz clic en la X situada junto a su nombre. Si deseas volver a mostrar todas las facetas anteriormente ocultas, haz clic en la X situada a la derecha del campo.
diff --git a/docs/tracks/es/seeing-order-details.md b/docs/tracks/es/seeing-order-details.md
index 467175618..69e66a8ca 100644
--- a/docs/tracks/es/seeing-order-details.md
+++ b/docs/tracks/es/seeing-order-details.md
@@ -3,8 +3,8 @@ title: 'Ver detalles del pedido'
 id: 204AjAQseJe8RLUi8GAhiC
 status: PUBLISHED
 createdAt: 2019-11-14T15:12:10.952Z
-updatedAt: 2023-03-29T15:17:48.189Z
-publishedAt: 2023-03-29T15:17:48.189Z
+updatedAt: 2023-11-08T14:56:01.508Z
+publishedAt: 2023-11-08T14:56:01.508Z
 firstPublishedAt: 2019-11-18T12:20:18.851Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -22,9 +22,16 @@ Además, la búsqueda ofrece un filtro muy flexible, que explicaremos en detalle
 
 Para comprender la lista de pedidos en detalle, consulte el artículo [Visión general de la lista de pedidos](https://help.vtex.com/es/tutorial/listado-de-pedidos--tutorials_200)
 
+Además de buscar pedidos en **Pedidos > Todos los pedidos**, puede buscar pedidos desde cualquier página del Admin VTEX utilizando la barra de búsqueda global en la parte superior de la página. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
 ## Ver los detalles de un pedido
 
-Hacer clic en un pedido lleva a la pantalla __detalles del pedido__, donde puede revisar un rango de información del pedido y realizar algunas acciones, tales como:
+Hacer clic en un pedido lleva a la pantalla [detalles del pedido](https://help.vtex.com/es/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl), donde puede revisar un rango de información del pedido y realizar algunas acciones, tales como:
 - Volver a enviar el último correo electrónico al cliente.
 - Cancelar manualmente el pedido.
 - Facturar los artículos del pedido.
diff --git a/docs/tracks/es/sending-product-data-to-dafiti.md b/docs/tracks/es/sending-product-data-to-dafiti.md
index 38950df22..356fe5ba1 100644
--- a/docs/tracks/es/sending-product-data-to-dafiti.md
+++ b/docs/tracks/es/sending-product-data-to-dafiti.md
@@ -3,8 +3,8 @@ title: 'Envío de los productos a Dafiti'
 id: 3b8BZfB1BC8G8SCe0ao46m
 status: PUBLISHED
 createdAt: 2018-09-27T18:14:09.967Z
-updatedAt: 2022-10-14T12:56:30.575Z
-publishedAt: 2022-10-14T12:56:30.575Z
+updatedAt: 2023-08-24T20:14:58.159Z
+publishedAt: 2023-08-24T20:14:58.159Z
 firstPublishedAt: 2018-09-27T21:44:56.294Z
 contentType: trackArticle
 productTeam: Channels
@@ -138,3 +138,7 @@ Después de rellenar la plantilla de mapeo de Dafiti, debes cargarla en el Admin
 8. Haz clic en `Enviar archivo`.
 
 Si no se ha producido ningún error en el envío, los productos se enviarán a Dafiti con sus respectivos atributos.
+
+<div class="alert alert-info">
+  La integración entre VTEX y Dafiti redimensiona automáticamente las fotos de los productos si son mayores que el tamaño solicitado por Dafiti (1000x1000).
+  </div>
diff --git a/docs/tracks/es/sending-products-to-amazon.md b/docs/tracks/es/sending-products-to-amazon.md
index 15d7d5faf..b2b211725 100644
--- a/docs/tracks/es/sending-products-to-amazon.md
+++ b/docs/tracks/es/sending-products-to-amazon.md
@@ -1,10 +1,10 @@
 ---
-title: 'Envío de productos a Amazon'
+title: 'Envío y mapeo de categorías de productos a Amazon'
 id: 5xklf2wSdeztQh4iy5kJvD
 status: PUBLISHED
 createdAt: 2019-02-28T23:12:40.204Z
-updatedAt: 2023-03-16T19:46:44.241Z
-publishedAt: 2023-03-16T19:46:44.241Z
+updatedAt: 2023-10-18T19:47:04.829Z
+publishedAt: 2023-10-18T19:47:04.829Z
 firstPublishedAt: 2019-02-28T23:13:35.624Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,7 +14,57 @@ trackId: 6sgd4Pagy3wNsWKBvmIFrP
 trackSlugES: integracion-de-amazon
 ---
 
-Una vez que haya realizado las configuraciones descritas en los pasos anteriores, podrá enviar sus productos al catálogo de Amazon. Para agilizar el proceso de catalogación de sus productos en Amazon y permitir que puedan estar disponibles para la venta en menos tiempo, tendrá que realizar el mapeo entre las características de los productos de su tienda VTEX y las características de los mismos productos en su tienda Amazon. Para realizar el mapeo, necesitarás:  
+Una vez realizada la configuración inicial de integración, ya puedes enviar los productos al catálogo de Amazon. Para habilitar el proceso de catalogación de los productos en Amazon y permitir que estén disponibles para la venta en menos tiempo, el seller debe realizar el mapeo entre las características de los productos de su tienda VTEX y las características de esos mismos productos en su tienda Amazon.  
+
+Para enviar sus productos a Amazon, el seller debe mapear las [categorías](https://help.vtex.com/es/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) y los [atributos del producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).
+
+<div class="alert alert-info">
+Los productos deben tener el <a href="https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">stock</a> y los <a href="https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">precios</a> configurados antes de enviarlos a Amazon.
+</div>
+
+## Mapear categorías  
+
+El proceso de mapeo se puede realizar a través del [Admin VTEX](#mapeo-via-admin-vtex-(beta)), o mediante una [plantilla](#mapeo-mediante-plantilla). Consulta a continuación los detalles de cada caso.  
+
+<div class="alert alert-danger">
+Atención: si realizas el mapeo de una categoría a través del Admin VTEX, y anteriormente habías realizado el mapeo de esa misma categoría mediante una plantilla, se sobreescribirá el mapeo de la plantilla y no podrá recuperarse.
+</div>
+
+### Mapeo vía Admin VTEX (beta)  
+
+Para acceder a la página de mapeo de Amazon, ve a **Marketplace > Marketplaces e integraciones > Amazon > Realizar mapeo.**  
+Se mostrará una lista de categorías disponibles para tu tienda VTEX. El mapeo de categorías permite una correspondencia entre las categorías de tu tienda y las de Amazon. De esta forma, los productos enviados figurarán en la categoría equivalente en el marketplace.  
+
+En la página de mapeo, puedes utilizar la barra de búsqueda para buscar la categoría por nombre o también puedes encontrarla en la sección **Categorías** de la tienda que muestra una lista de las categorías de tu tienda VTEX.  
+
+La lista de categorías de tu tienda VTEX incluye el status del mapeo a través de los íconos:  
+
+| **Ícono** | **Status** | **Descripción** |
+|:---:|:---:|:---:|
+| ![mapeado mapper](//images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/069480d9eeb7b6108d5f6ec3d7ad1d78/mapeado_mapper.jpg) | **Mapeada** | Indica que el mapeo de categorías está completo. |
+| ![mapeamentoincompleto mapper](//images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/695f33c0eba4012f7e585ca1785ec17f/mapeamentoincompleto_mapper.jpg) | **Mapeo incompleto** | La categoría está parcialmente mapeada, por lo que es necesario ingresar sus atributos obligatorios (señalados con un asterisco) para realizar el mapeo. |
+| ![erromapeamento mapper](//images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/7036253cccb4415d9759867b28ff1695/erromapeamento_mapper.jpg) | **Error al realizar el mapeo** | El error de mapeo ocurre cuando el marketplace elimina o cambia la categoría del producto. Para resolver este problema, solo hay que rehacer el mapeo de categorías. |
+|![incompleto mapper](//images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/3eaea439ecfdbb54eaa8fefec12247ae/incompleto_mapper.jpg) | **No mapeada** | Indica que no se realizó el mapeo de la categoría. |  
+
+Para realizar el mapeo de categorías:  
+
+1. En el Admin VTEX, accede al módulo **Marketplace > Marketplaces e integraciones > Amazon > Realizar mapeo.**
+2. Selecciona la categoría que deseas mapear.
+3. Selecciona la categoría de Amazon correspondiente al producto que deseas enviar.
+4. Haz la correspondencia de los atributos en la ventana lateral, como se muestra en la imagen a continuación:
+
+![Atributos del mapeador de Amazon](//downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/9dbef07f676b7bf29ef81bfda39d9bda/mapper_amazon_atributos.gif)
+
+5. Haz clic en el botón `Guardar cambios`.
+
+<div class="alert alert-danger">
+Los campos marcados con un asterisco * son obligatorios.
+<br>Al ingresar un atributo pueden activarse nuevos campos obligatorios que solo serán visibles en la página <b>Marketplace > Conexiones > Productos,</b> después de guardar el mapeo.</br>
+</div>
+
+### Mapeo mediante plantilla 
+
+El seller deberá seguir los pasos a continuación para realizar el mapeo a partir de una plantilla:
 
 1. [Descargar el modelo de la plantilla de categorías generales de Amazon](#1-plantilla-de-categorias-generales-de-amazon)
 2. [Descargar el modelo de la plantilla de atributos de Amazon](#2-plantilla-de-atributos-de-amazon)
@@ -23,13 +73,13 @@ Una vez que haya realizado las configuraciones descritas en los pasos anteriores
 5. [Rellenar la plantilla de mapeo](#5-como-rellenar-la-plantilla-de-mapeo)
 6. [Cargar la plantilla de mapeo](#6-cargar-la-plantilla-de-mapeo)
 
-## 1. Plantilla de categorías generales de Amazon
+#### 1. Plantilla de categorías generales de Amazon
 
 Amazon utiliza la [categoría global](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188) registrada en VTEX para mapear los productos, por lo que es importante que la equivalencia entre la categoría global de VTEX y las categorías generales en Amazon se haga correctamente.
 
 Para conocer las categorías aceptadas por Amazon es necesario descargar la [Plantilla de categorías generales de Amazon](https://drive.google.com/uc?export=download&id=1GC5Guic4k_8C2ZnEGQUoDqT2cdJzp-Ti). Esta plantilla se utilizará solo para consulta.
 
-## 2. Plantilla de atributos de Amazon
+#### 2. Plantilla de atributos de Amazon
 
 Amazon tiene valores de referencia para determinadas características de productos que se deben tomar en cuenta en el mapeo de los productos.
 
@@ -37,14 +87,14 @@ Para saber qué atributos acepta Amazon según cada columna de la plantilla de m
 
 En esta plantilla, cada pestaña corresponde a una subcategoría global en Amazon. Al hacer clic en una pestaña, la plantilla muestra en cada columna las subcategorías presentes dentro de la categoría global seleccionada.
 
-## 3. Preconfiguraciones en el Catálogo
+#### 3. Preconfiguraciones en el Catálogo
 
 Antes de mapear los productos en su tienda, debe configurar los siguientes [campos del producto](https://help.vtex.com/es/tutorial/criando-um-campo-de-produto--tutorials_106) que desea enviar a Amazon:
 
 - [Categoría Global](#categoria-global)
 - [EAN](#ean)
 
-### Categoría global
+###### Categoría global
 
 Para identificar sus productos y relacionarlos con el catálogo de Amazon, la integración utiliza las [categorías globales](https://help.vtex.com/es/tutorial/configurando-a-categoria-global--tutorials_188) de VTEX. Durante el proceso de mapeo, el sistema hace la correspondencia de cada categoría global de VTEX con las [categorías generales](#plantilla-de-categorías-generales-de-amazon) de Amazon. De este modo, dirigimos los productos a las categorías correctas y con los atributos de producto necesarios.
 
@@ -52,7 +102,7 @@ Por lo tanto, es obligatorio tener todos los productos de su catálogo clasifica
 
 Cuando configure la categoría global en VTEX, tenga en cuenta las categorías globales de Amazon, ya que esta información se utilizará al [rellenar la plantilla de mapeo de Amazon](#5-como-rellenar-la-plantilla-de-mapeo).
 
-#### Configuración de la Categoría global 
+##### Configuración de la Categoría global 
 
 Para configurar la categoría global en su entorno VTEX según las categorías globales en Amazon, siga los pasos a continuación:
 
@@ -66,7 +116,7 @@ Para configurar la categoría global en su entorno VTEX según las categorías g
 8. Rellene el campo [Categoria Global](https://help.vtex.com/es/tutorial/configurando-a-categoria-global) con el nombre de la categoría encontrada en el paso 3.
 9. Haga clic en `Guardar cambios`.
 
-#### Ejemplo de cómo consultar las plantillas 
+##### Ejemplo de cómo consultar las plantillas 
 
 En la Plantilla de atributos de Amazon, utilizaremos la categoría **Health**, centrada en los productos de salud:
 ![categoriageral01](//images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
@@ -79,11 +129,11 @@ Siguiendo el ejemplo anterior, filtre las columnas B, C y D, haciendo clic en **
 
 Ahora que ha encontrado la categoría general de Amazon, vuelva al Admin para [configurar la categoría global de VTEX](https://help.vtex.com/es/tutorial/configurando-a-categoria-global--tutorials_188) según la categoría general de Amazon.
 
-### EAN
+#### EAN
 
 Como el catálogo de Amazon es único, se requiere que los productos enviados tengan [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube), para poder mostrar los productos de todos los sellers en la vitrina y en el checkout. Por lo tanto, asegúrese de que sus productos tienen EAN válidos registrados antes de configurar la integración.
 
-#### Exención del EAN
+##### Exención del EAN
 
 Sin embargo, hay situaciones en las que [Amazon exime al administrador de la tienda de enviar el EAN](https://sellercentral.amazon.com.br/gp/help/200426310). En este caso, la exención debe configurarse tanto en Amazon como en VTEX. 
 
@@ -113,13 +163,13 @@ Si vende productos de una marca o de fabricación propia, Amazon debe aprobarla
 
 Si quiere vender un producto que está asociado a otro propietario (creación de un nuevo ASIN, el código creado por Amazon para identificar sus productos), es importante estar atento al proceso de [Liberación del producto a la marca](https://sellercentral.amazon.com/gp/help/help.html/?itemID=G201844590&ref_=xx_G201844590_a_r0_cont_sgsearch).
 
-## 4. Plantilla de mapeo
+#### 4. Plantilla de mapeo
 
 En este paso tendrá que categorizar las variaciones y atributos de los productos y enviarlos al marketplace. Esta información se envía mediante la plantilla de mapeo, que establece la equivalencia entre las categorías, las variaciones y los atributos de su tienda y los estándares adoptados por Amazon.
 
 Descargue la [Plantilla de mapeo de Amazon.xlsx](https://assets.ctfassets.net/alneenqid6w5/4mNcXF4yS3160xUGgCZVQC/caf8cfc88b316bc9878000264e16e30b/Planilha_modelo.xlsx) y utilice el archivo descargado como modelo para rellenar. Esta es la plantilla que se rellenará y posteriormente se enviará a Amazon.
 
-## 5. Cómo rellenar la plantilla de mapeo
+#### 5. Cómo rellenar la plantilla de mapeo
 
 La plantilla contiene las siguientes columnas:
 
@@ -156,7 +206,7 @@ Para cada producto, siga los pasos a continuación.
 En algunos casos, los valores de <b>VariationTheme</b> pueden ser similares. Hay categorías en las que el <b>VariationTheme</b> puede ser: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, mientras en otras categorías puede ser: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. La diferencia está en el orden. En <i>SizeColor</i>, as casillas en la página del producto se ordenarán por tamaño y color, mientras que en <i>ColorSize</i> se ordenarán por color y tamaño. Tenga en cuenta los valores válidos de cada categoría que se va a mapear. 
 </div>
 
-### Ejemplo de cómo rellenar la plantilla
+##### Ejemplo de cómo rellenar la plantilla
 
 | CategoryID | VariationTheme | Type | VTEXSpecification | AmazonSpecification | VTEXValue | AmazonValue |
 | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
@@ -164,7 +214,7 @@ En algunos casos, los valores de <b>VariationTheme</b> pueden ser similares. Hay
 | 212 | SizeColor | Variation | Tamaño | Size | M | M |
 | 212 | SizeColor | Variation | Tamaño | Size | G | L |
 
-## 6. Cargar la plantilla de mapeo
+#### 6. Cargar la plantilla de mapeo
 
 Después de rellenar la plantilla, accede a Integraciones en el menú del Admin:  
 
@@ -177,17 +227,3 @@ Después de rellenar la plantilla, accede a Integraciones en el menú del Admin:
 
 Si no se ha producido ningún error en el envío, los productos se enviarán a Amazon con sus respectivos atributos.  
 
-## 7. Correspondencia automática  
-
-Cada vez que un [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) que tiene un [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) registrado se envía a Amazon, el marketplace realiza un proceso de correspondencia, que unifica los anuncios de un mismo producto utilizando el EAN.  
-
-El EAN registrado en VTEX se utiliza para establecer la equivalencia con los [ASIN](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (Amazon Standard Identification Number) correspondientes de Amazon. La correspondencia se realiza automáticamente, sin embargo, pueden ocurrir errores.  
-<div class="alert alert-info">
-Se recomienda que el seller revise todos los productos que tengan el status Procesado con advertencia. Los productos que no tengan el EAN y ASIN correspondientes, se tendrán que enviar de nuevo.  
-</div>
-
-Para filtrar los productos que no se hayan procesado correctamente, sigue los pasos a continuación:
-
-1. En el Admin VTEX, accede a __Marketplace > Integraciones > Productos.__  
-2. Filtra los productos que tienen el valor Amazon en el campo Afiliado y Aviso en el campo __Status__. Verás los productos que no se procesaron con EAN y ASIN equivalentes y podrás enviarlos de nuevo.
-
diff --git a/docs/tracks/es/sending-products-to-facebook.md b/docs/tracks/es/sending-products-to-facebook.md
index 8517407bd..dfc8ea931 100644
--- a/docs/tracks/es/sending-products-to-facebook.md
+++ b/docs/tracks/es/sending-products-to-facebook.md
@@ -3,8 +3,8 @@ title: 'Envío de productos a Facebook'
 id: 41qzoa7TWIYTyIhABHdgzI
 status: PUBLISHED
 createdAt: 2021-02-08T19:45:07.202Z
-updatedAt: 2021-07-09T22:04:10.786Z
-publishedAt: 2021-07-09T22:04:10.786Z
+updatedAt: 2024-01-22T15:03:37.861Z
+publishedAt: 2024-01-22T15:03:37.861Z
 firstPublishedAt: 2021-02-08T20:10:14.152Z
 contentType: trackArticle
 productTeam: Channels
@@ -89,10 +89,10 @@ Vea un ejemplo de plantilla llenada:
 El tercer y último paso para finalizar el mapeo es cargar la plantilla llenada.  Esta acción se realiza en el Admin, a través de los siguientes pasos:
 
 1. Acceda al Admin.
-2. En el módulo _MARKETPLACE_, haga clic en `Integracione`.
-3. Seleccione la opción `Configuración`.
-4. En la tarjeta de Facebook, haga clic en <i class="fas fa-cog"></i>
-5. Elija la opción `Carga de mapeo`.
+2. En el módulo Marketplace, haga clic en Marketplace e integraciones.
+4. Busque Facebook en la barra de búsqueda.
+5. Haga clic en `Editar`
+6. Elija la opción `Mapeo de categorías`.
 6. Haga clic en `Elegir un archivo`.
 7. Seleccione la plantilla de mapeo llenada.
 8. Haga clic en `Subir archivo`.
diff --git a/docs/tracks/es/sending-products-to-via.md b/docs/tracks/es/sending-products-to-via.md
index 0e7fb6eee..b6250cd67 100644
--- a/docs/tracks/es/sending-products-to-via.md
+++ b/docs/tracks/es/sending-products-to-via.md
@@ -1,10 +1,10 @@
 ---
-title: 'Envío de los productos a Via Marketplace'
+title: 'Envío de los productos a Casas Bahia Marketplace'
 id: 5QVZFYNfuRIQKdq34MbTxz
 status: PUBLISHED
 createdAt: 2020-03-30T18:51:30.236Z
-updatedAt: 2022-01-24T19:39:58.658Z
-publishedAt: 2022-01-24T19:39:58.658Z
+updatedAt: 2024-07-26T19:30:35.060Z
+publishedAt: 2024-07-26T19:30:35.060Z
 firstPublishedAt: 2020-03-30T23:08:05.849Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md b/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md
index 352b7dae6..7e4928354 100644
--- a/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md
+++ b/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md
@@ -26,31 +26,31 @@ Puede encontrar enlaces para descargar en: [http://instore.vtex.com/#download](h
 
 Al abrir inStore por primera vez, tendrá que introducir la cuenta VTEX donde desea configurar el inStore y hacer clic en __Confirmar__.
 
-![01 inStore selecione conta](https://images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
+![01 inStore selecione conta](//images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
 
 Al identificar que el inStore no está configurado en esta cuenta, se redirirá a la VTEX App Store en la que tendrá que iniciar sesión con su cuenta de administrador en VTEX.
 
 Después de iniciar sesión, usted podrá instalar el inStore en su cuenta.
 
-![02 inStore instalar](https://images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
+![02 inStore instalar](//images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
 
 Se mostrará un formulario de configuración, siendo el primer paso la información de dirección.
 
-![03 inStore endereco](https://images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
+![03 inStore endereco](//images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
 
 A continuación, usted debe definir un correo electrónico y una contraseña que se utilizarán como login de vendedor.
 
 > __IMPORTANTE__: ese e-mail __NO__ puede ser el mismo utilizado en la plataforma VTEX, porque su e-mail de administrador tiene permisos que un vendedor no debería tener, por lo que es necesario utilizar algún otro e-mail sin privilegios en la plataforma.
 
-![04 inStore registre vendedor](https://images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
+![04 inStore registre vendedor](//images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
 
 Después de configurar el vendedor y confirmar el código de activación recibido por correo electrónico, usted puede definir las formas de pago.
 
-![05 inStore configure pagamento](https://images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
+![05 inStore configure pagamento](//images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
 
 Si aún no tiene contrato con un adquirente, sólo puede mantener la opción __Efectivo__ activa. Al hacer clic en __Confirmar__, usted verá la pantalla de éxito.
 
-![06 inStore sucesso](https://images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
+![06 inStore sucesso](//images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
 
 Ahora basta con volver a la aplicación, iniciar sesión con las credenciales de vendedor y empezar a vender!
 
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md
index 5fca041d1..d9018f226 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md
@@ -18,7 +18,7 @@ El primer paso de cualquier integración es definir la política comercial que s
 
 Una de las funciones de la política comercial es hacer una diferenciación de __catálogo__ y/o __logística__ entre los diferentes canales de venta de la tienda. Es decir, una nueva política comercial solo es necesaria cuando uno de estos factores es diferente entre los canales de venta.
 
-![carrefour.1es](https://images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/9f0435400496cfcfeb6201edb5c9837f/carrefour.1es.png)
+![carrefour.1es](//images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/9f0435400496cfcfeb6201edb5c9837f/carrefour.1es.png)
 
 La misma política comercial puede ser utilizada por más de un marketplace o entre tienda principal y marketplace. Para esto, basta con utilizar el mismo ID de política comercial en la [configuración](es/tutorial/integrando-con-marketplace). Al hacer esto, se utilizará el mismo catálogo y la misma logística para las tiendas o canales que están configurados con la misma política comercial.
 
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy-skyhub-b2w.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
index b3161f8ed..45c7c513a 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
@@ -3,8 +3,8 @@ title: 'Configurar la política comercial para marketplace'
 id: 4rbhQuuWlUvOp4oOeBlbiC
 status: PUBLISHED
 createdAt: 2021-02-22T19:46:30.515Z
-updatedAt: 2022-12-08T20:34:38.911Z
-publishedAt: 2022-12-08T20:34:38.911Z
+updatedAt: 2023-10-19T14:10:13.534Z
+publishedAt: 2023-10-19T14:10:13.534Z
 firstPublishedAt: 2021-02-22T21:40:49.337Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy-viavarejo.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy-viavarejo.md
index d72de1a87..e39df82dd 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy-viavarejo.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy-viavarejo.md
@@ -3,8 +3,8 @@ title: 'Configurar la política comercial'
 id: D63aTOOoQXd6NYq1f5rhc
 status: PUBLISHED
 createdAt: 2021-02-22T16:52:54.100Z
-updatedAt: 2022-12-08T20:34:07.143Z
-publishedAt: 2022-12-08T20:34:07.143Z
+updatedAt: 2023-11-30T21:09:43.958Z
+publishedAt: 2023-11-30T21:09:43.958Z
 firstPublishedAt: 2021-02-22T21:38:33.617Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
index b2b790b96..9390225de 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
@@ -18,15 +18,15 @@ El primer paso de cualquier integración es definir la política comercial que s
 
 Una de las funciones de la política comercial es hacer una diferenciación de __catálogo__ y/o __logística__ entre los diferentes canales de venta de la tienda. Es decir, una nueva política comercial solo es necesaria cuando uno de estos factores es diferente entre los canales de venta.
 
-![carrefour.1es](https://images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/51afdc673afc6959b447a7c28a81f170/carrefour.1es.png)
+![carrefour.1es](//images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/51afdc673afc6959b447a7c28a81f170/carrefour.1es.png)
 
 La misma política comercial puede ser utilizada por más de un marketplace o entre tienda principal y marketplace. Para esto, basta con utilizar el mismo ID de política comercial en la [configuración](es/tutorial/integrando-con-marketplace). Al hacer esto, se utilizará el mismo catálogo y la misma logística para las tiendas o canales que están configurados con la misma política comercial.
 
-![carrefour.2es](https://images.ctfassets.net/alneenqid6w5/2F7jSO1EjBamKdt5ArgPjm/8a0835cd3f38702fe82c2fb187af3a11/carrefour.2es.png)
+![carrefour.2es](//images.ctfassets.net/alneenqid6w5/2F7jSO1EjBamKdt5ArgPjm/8a0835cd3f38702fe82c2fb187af3a11/carrefour.2es.png)
 
 En otras palabras, si no es necesario definir un catálogo o un tipo de logística específicos para diferentes canales de ventas, usted tampoco necesitará utilizar políticas comerciales separadas. Basta asociar el ID de la política comercial que ya existe a su integración con el marketplace. 
 
-![carrefour.3es](https://images.ctfassets.net/alneenqid6w5/3SW2dNax736jMp5eZ54gpj/646492b31b365d60cbfebde8356a9018/carrefour.3es.png)
+![carrefour.3es](//images.ctfassets.net/alneenqid6w5/3SW2dNax736jMp5eZ54gpj/646492b31b365d60cbfebde8356a9018/carrefour.3es.png)
 
 Luego de entender esto, evalúe si es necesario configurar una nueva política comercial en su tienda. Si la respuesta es sí, siga las instrucciones de [este artículo](https://help.vtex.com/es/faq/como-contratar-nueva-politica-comercial--frequentlyAskedQuestions_700) antes de pasar a la siguiente etapa de configuración. Si su política comercial ya cumple las condiciones que necesita para la integración con el marketplace, siga las próximas instrucciones.
 
diff --git a/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
index 757d20372..18546b8fe 100644
--- a/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
@@ -16,7 +16,7 @@ trackSlugES:
 
 Este artículo tiene como objetivo explicar cómo la aplicación de inStore configura el AppLinking para las acciones de `payment` y `payment-reversal` con las apps de los adquirentes.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuración
 
diff --git a/docs/tracks/es/setting-up-credit-direct-sale.md b/docs/tracks/es/setting-up-credit-direct-sale.md
index 31be842a7..e2e73dce5 100644
--- a/docs/tracks/es/setting-up-credit-direct-sale.md
+++ b/docs/tracks/es/setting-up-credit-direct-sale.md
@@ -3,8 +3,8 @@ title: 'Configuración de venta directa - Crédito'
 id: 5rSTgGeCqEN7c9LmFbfqA
 status: PUBLISHED
 createdAt: 2021-09-27T20:09:51.763Z
-updatedAt: 2023-05-31T14:45:21.350Z
-publishedAt: 2023-05-31T14:45:21.350Z
+updatedAt: 2023-07-19T19:35:38.275Z
+publishedAt: 2023-07-19T19:35:38.275Z
 firstPublishedAt: 2021-09-27T20:35:59.233Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/es/setting-up-payment-methods-for-instore.md b/docs/tracks/es/setting-up-payment-methods-for-instore.md
index 8a3aa188c..492e65944 100644
--- a/docs/tracks/es/setting-up-payment-methods-for-instore.md
+++ b/docs/tracks/es/setting-up-payment-methods-for-instore.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configuración de métodos de pago para inStore'
+title: 'Configuración de métodos de pago VTEX Sales App'
 id: 2liigRors32hzqBNs2M1Oa
 status: PUBLISHED
 createdAt: 2020-06-28T14:54:46.020Z
-updatedAt: 2023-05-31T14:44:58.176Z
-publishedAt: 2023-05-31T14:44:58.176Z
+updatedAt: 2023-08-28T11:55:43.015Z
+publishedAt: 2023-08-28T11:55:43.015Z
 firstPublishedAt: 2020-06-28T15:17:02.889Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/es/setting-up-the-app.md b/docs/tracks/es/setting-up-the-app.md
index 47b718ed7..696671e9c 100644
--- a/docs/tracks/es/setting-up-the-app.md
+++ b/docs/tracks/es/setting-up-the-app.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar Customer Credit'
+title: ' Configurar el Customer Credit'
 id: 21ok0GBwmcIeaY2IukYMOg
 status: PUBLISHED
 createdAt: 2018-11-07T17:11:22.823Z
-updatedAt: 2022-01-07T13:30:23.058Z
-publishedAt: 2022-01-07T13:30:23.058Z
+updatedAt: 2024-02-08T18:03:14.738Z
+publishedAt: 2024-02-08T18:03:14.738Z
 firstPublishedAt: 2018-11-07T17:23:16.520Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,100 +14,101 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugES: customer-credit-como-empezar
 ---
 
-## Configuración de primero acceso
+Después de instalar la aplicación del Customer Credit, debe realizar las siguientes configuraciones:
 
-Ahora vamos a configurar Customer Credit. 
+- [Primer acceso](#configuracion-de-primer-acceso)
+- [App](#configuracion-de-app) 
+- [Condiciones de pago](#condiciones-de-pago)
 
-El primer paso es acceder a la página de configuración de la aplicación en el Admin. 
+## Configuración de primer acceso
 
-Luego de hacer esto, justo al inicio de la pantalla, verá tres comandos dentro del box "Pendiente".
+Para realizar la configuración inicial del Customer Credit, siga los pasos a continuación:
 
-Estos son: 
+1. En el Admin VTEX, accede a __Apps > Customer Credit > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la sección __Pendiente__, es posible que se muestren una o más de las configuraciones enumeradas a continuación:
+<br>
+<ul>
+<br>
+    	<li><b>Habilitar emails transaccionales en el Centro de mensajes</b>: haga clic en <b>Habilitar</b> para instalar las plantillas de correo electrónico transaccional relacionadas con el Customer Credit en <a href="https://help.vtex.com/pt/tutorial/conhecendo-o-message-center--tutorials_84">Message Center</a>.</li>
+    	<li><b>Configurar las condiciones de pago del checkout</b>: haga clic en <b>Configurar</b> para permitirle definir la fecha límite y las reglas de pago de la tienda.</li>
+  	<li><b>Afiliación no autenticada todavía</b>: haga clic en <b>Autenticar</b> para ser redirigido a la pantalla de configuración donde deberás completar la información <b>Application Key</b> y <b>Application Token</b>. Esta acción permitirá que los pagos realizados a través de Customer Credit se procesen en su tienda. Obtenga más información en <a href="https://developers.vtex.com/docs/guides/authentication">Autenticación</a>.</li>
+</ul>
 
-1. __Activar correos electrónicos transaccionales en el Message Center__: instala los templates de correos electrónicos transaccionales relativos al Customer Credit en el Message Center. Para activarlo, haga clic en el botón "Activar".
-2. __Configurar las condiciones de pago del checkout__: define las reglas de plazo y de pago en cuotas de la tienda. Para activarlo, haga clic en el botón "Configurar".
-3. __AppKey y AppToken de la afiliación no definidos__: Customer Credit como forma de pago. Para activarlo, haga clic en el botón “Autenticar”. A continuación, usted será redirigido a la página “Afiliaciones de Gateway”, donde deberá rellenar los campos vacíos con su Key y Token para aquella tienda. Para saber más detalles, consulte nuestro [artículo sobre cómo crear appKey y appToken](https://help.vtex.com/es/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2 "artículo sobre cómo crear appKey y appToken"). 
+![CC Configuracion 1 ES](//images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/7e7102273c6ef79723ff3124d3aab727/CC_Configuracion_1_ES.JPG)
 
-De esta manera, Customer Credit estará disponible como forma de pago en el SmartCheckout de su tienda.
+## Configuración de app
 
-## Configuración de la aplicación 
+Luego, aún en la misma pantalla de VTEX Admin (__Apps > Customer Credit > Configuración__), debes verificar las siguientes opciones de configuración:
 
-A continuación, tendrá cuatro opciones de personalización de la experiencia que su consumidor tendrá en la tienda. 
-
-Revise los detalles de cada uno de estos.
+- [Tolerancia](#tolerancia)
+- [Creación automática de cuenta](#creacion-automática-de-cuenta) 
+- [Página Mis créditos](#pagina-mis-creditos)
+- [Instrucciones de pago](#instrucciones-de-pago)
+- [Información de identificación](#informacion-de-identificacion)
 
 ### Tolerancia
 
-Esta opción permite cerrar una compra aunque exceda el crédito disponible del usuario. Cabe mencionar que es posible registrar un porcentaje excedente de crédito disponible para cada cuenta registrada.
+Activar esta opción permite completar una compra incluso si su valor excede el límite de crédito disponible del cliente. Al crear una cuenta, es posible registrar un porcentaje de exceso de crédito (tolerancia) para cada cliente.
 
-Por ejemplo, digamos que una cuenta tiene R$ 1.000,00 de crédito disponible y una tolerancia del 10%. De esta manera, el sistema permitirá que se hagan pedidos de hasta R$ 1.100,00.
+Por ejemplo, para una cuenta creada con un límite de crédito de $1.000,00 y una tolerancia del 10%, el cliente podrá realizar un pedido con un valor máximo de $1.100,00 utilizando Customer Credit como método de pago. Si el cliente desea utilizar el crédito para pagar un pedido por valor de $1.250,00, el sistema no permitirá completar la compra.
 
 <div class="alert alert-warning">
-Los valores de tolerancia se establecen en números decimales, donde 0 representa el 0% y 1 representa el 100%. Ejemplo: para una tolerancia del 5%, el valor a configurar es 0.05.
+Los valores de tolerancia se configuran en números decimales, donde 0 representa el 0% y 1 representa el 100%. Ejemplo: para utilizar una tolerancia del 5%, el valor a configurar es 0,05.
 </div>
 
-Para establecer la tolerancia, consulte el procedimiento: 
+![CC_Configuracion_2_ES](//images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/c87641a0ebdb835abfb632fcc2ebff90/CC_Configuracion_2_ES.JPG)
 
-1. Acceda al __Admin__.
-2. Haga clic en __Customer Credit__.
-3. Luego, haga clic en __Cuentas__.
-4. Haga clic en la cuenta de cliente para la que desea establecer la tolerancia.
-5. En __Tolerancia__, haga clic en __Editar__.
-6. Complete el valor de tolerancia (en decimales).
-7. Haga clic en __Actualizar__.
+### Creación automática de cuenta
 
-### Creación automática de cuenta  
-Este flag permite a los clientes finalizar una compra utilizando Customer Credit como forma de pago, aunque no tengan una cuenta previa con un límite de crédito definido. 
+Esta opción permite que cualquier cliente de la tienda utilice Customer Credit como método de pago, incluso si no ha creado previamente una cuenta para ellos en la aplicación Customer Credit . Al activar esta funcionalidad, también deberás definir el límite de crédito inicial que se puede utilizar para los pedidos realizados por clientes sin una cuenta de Customer Credit .
 
-En la página de configuración, tiene la opción de establecer un límite de crédito predeterminado para los clientes cuyas cuentas se crearán automáticamente en el SmartCheckout
+![CC_Configurações_3_ES](//images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/7ff9a5cbdb0e164891c5da0931add045/CC_Configuracion_3_ES.JPG)
 
-### Mi página de créditos
-Es la interfaz a través de la cual el usuario final tendrá acceso a la información de su cuenta.
+### Página Mis créditos
 
-En esta, el usuario ve sus límites disponibles, los títulos abiertos y pagados, el extracto de cuenta y la posibilidad de añadir o eliminar dependientes. 
+Al instalar la página __Mis créditos__, permitirá a los clientes ver y administrar información sobre los créditos y facturas disponibles en su cuenta.
 
-Cuando la página esté habilitada, estará disponible en el área de acceso del cliente - MyAccount.
+El cliente puede acceder a esta página en el sitio web de su tienda en __Mi Cuenta > Mis Créditos__.
 
-### Instrucciones de pago  
+![CC_Configuracion_4_ES](//images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/72cff75048d2ac6bb609169f73bb9c49/CC_Configuracion_4_ES.JPG)
 
-Aquí, el usuario puede ingresar instrucciones de pago en los documentos de sus títulos. Para esto, simplemente haga clic en "Editar" y escriba la orientación que prefiera. No olvide hacer clic en el botón azul "Actualizar" para guardar la configuración.
+### Instrucciones de pago 
 
-Además, destacamos que la misma instrucción se reproducirá en todas las facturas de la tienda, independientemente de la cuenta a la que esté vinculado el título y de su status.
+Esta configuración permite insertar instrucciones relacionadas con el pago en las facturas emitidas por Customer Credit. Para editar el mensaje que se mostrará en la factura, ingrese la información en el cuadro de texto y haga clic en `Actualizar`.
 
-## Condiciones de pago  
-En ese momento, Customer Credit está correctamente instalado y configurado en su tienda. Ahora puede crear condiciones de pago que se mostrarán en el  SmartCheckout.
+<div class="alert alert-warning">
+El mensaje registrado en esta configuración se replicará en todos las facturas emitidas para todas las cuentas de clientes de Customer Credit. No es posible configurar un mensaje único para cada cliente o factura específica.
+</div>
 
-Puede definir diferentes escenarios de negocio para estas condiciones de pago. Esto también implica los plazos y el número de cuotas disponibles para sus clientes. 
+![CC_Configuracion_5_ES](//images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/791355858bde3d7fa86eaa8b142b56e9/CC_Configuracion_5_ES.JPG)
 
-Algunos de los plazos utilizados son:
+### Información de identificación
 
-- Pagos realizados en 7, 28 y 45 días.
-- Pagos hechos en 45 días. 
-- Plazos de 30, 60 y 90 días. 
+Esta opción le permite seleccionar qué información de identificación de la tienda debe mostrarse en la parte superior de las facturas emitidas.
 
-A continuación, consulte el procedimiento: 
+![CC_Configuracion_6_ES](//images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/cda6ab4a6232705bfb4323be12fc93bb/CC_Configuracion_6_ES.JPG)
 
-1. Acceda al __Admin__.
-2. Haga clic en __Pagos__.
-3. Luego, haga clic en __Configuración__.
-4. Asegúrese de que está en la pestaña __Planes de Pago__.
-5. En el lado derecho de la pantalla, haga clic en el botón verde __“+”__.
-6. Localice y haga clic en la opción __Customer Credit__.
-7. En el lado derecho, establezca el criterio en el box __Configure las reglas de plazo y parcelación__.
+![CC_Configuration_8_ES](//images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/708d343130c21d3c308ea058e4414c5c/CC_Configuration_8_ES.JPG)
 
-Si desea establecer más de una regla, solo tiene que hacer clic en el botón azul "Agregar nueva regla". Por último, haga clic en el botón "Guardar" para actualizar la configuración.
+## Condiciones de pago 
 
-Además, como en otras formas de pago, Customer Credit también permite la configuración de [condiciones especiales](https://help.vtex.com/es/tutorial/condicoes-especiais?locale=es "condiciones especiales"). Esto hace que el usuario defina los contextos de compra que se aplicarán para cada plan de pago configurado en la tienda.
+Una vez que se completa la configuración del Customer Credit, es necesario indicar qué opciones de plazo y cuotas estarán disponibles para mostrarse a los clientes en la pantalla de Checkout.
 
-### Intereses 
-Por último, también puede establecer tasas de interés simples para las reglas de pago en cuotas establecidas en su tienda. Actualmente, puede aplicar estas tasas a los pedidos que se pagarán en dos o más cuotas.
+Para crear condiciones de pago para títulos de Customer Credit, siga los pasos a continuación:
 
-<div class="alert alert-warning">
-<strong>Atención</strong>: las tasas de interés <strong>no</strong> se aplican a los pedidos que se pagarán en solo una cuota.
-</div> 
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Seleccione la opción __Customer Credit__.
+4. Complete el campo __Nombre de la condición__ con un nombre de su elección para identificación.
+5. Active la condición en el campo __Status__.
+6. En __Configura las condiciones de plazo y de pago en cuotas__, indique el número de cuotas, el plazo de vencimiento (en días) y la tasa de interés simple a aplicar a cada cuota. Para crear más de una condición de pago, haga clic en `Agregar nueva regla`.
 
-Sin embargo, apenas un valor de intereses aplicado a las cuotas aparecerá en el SmartCheckout.
+![CC_Configuration_9_ES](//images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/35c2d14c21c1e10aba4ac95f49fc3354/CC_Configuration_9_ES.JPG)
 
-Por ejemplo, digamos que ha configurado tres cuotas para Customer Credit, cada una con un tipo de interés diferente: la primera con el 10%, la segunda con el 15% y la tercera con el 20%.
+<blockquote><ui>7. Si lo deseas también puedes <a href="https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456">Configurar condiciones especiales de pago</a>.</ui>
 
-Como la configuración de 10 % es la más ventajosa para el consumidor final, esta será la única opción de pago que se mostrará en el SmartCheckout.
+<blockquote><ui>8. Clic en <b>Guardar</b>.</ui>
+
+<div class="alert alert-warning">
+No es posible establecer una tasa de interés para una condición de pago creada con una sola cuota. 
+</div>
diff --git a/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md b/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md
index 2c043a781..1d0d15085 100644
--- a/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md
+++ b/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md
@@ -3,8 +3,8 @@ title: 'Configurar logística para Mercado Libre'
 id: 4551ZlEQI8qmiSWieigoKy
 status: PUBLISHED
 createdAt: 2018-08-13T12:53:57.008Z
-updatedAt: 2023-03-28T13:36:16.191Z
-publishedAt: 2023-03-28T13:36:16.191Z
+updatedAt: 2024-07-23T22:07:18.063Z
+publishedAt: 2024-07-23T22:07:18.063Z
 firstPublishedAt: 2018-08-13T14:27:58.483Z
 contentType: trackArticle
 productTeam: Channels
@@ -23,7 +23,11 @@ Las modalidades de envío son dos:
 - [Mercado Envíos 1 (ME1)](#mercado-envios-1-me1)
 - [Mercado Envíos (ME2)](#mercado-envios-2-me2)
 
-## Mercado Envios 1 (ME1)
+<div class="alert alert-warning">
+Debes tener un SLA configurado en VTEX independientemente de la modalidad de envío que utilizas en tu tienda. Si no se configura la modalidad, los pedidos realizados en Mercado Libre no se integrará a la plataforma VTEX.
+</div>
+
+## Mercado Envíos 1 (ME1)
 
 La modalidad de envío ME1 está pensada para productos que pesen más de 30 kg o midan más de 200 cm en total, sumando altura, anchura y longitud, o cuando uno de los lados del producto supere los 70 cm.
 
@@ -67,12 +71,12 @@ Algunos tipos de logística tienen la obligación de enviar una factura o config
 - [Flex](#flex)
 - [Mercado Envíos Full](#mercado-envios-full)
 
-### Drop Off
-
 <div class="alert alert-info">
-La modalidad Drop Off es la única que no ofrece la posibilidad de que el cliente recoja el pedido en los puntos de recogida.
+Para segmentar qué tipo de envío utiliza la tienda, es necesario crear un <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106"><i>atributo de producto</i></a> con el nombre <code>meli_shipping_mode</code>, donde estará completado si es ME1 o ME2.
 </div>
 
+### Drop Off
+
 Siempre que usted se inicia como vendedor en Mercado Libre, comienza con el *Drop Off*, este tipo de logística es utilizado por todos los clientes que están comenzando a vender en Mercado Libre.
 
 Cuando se cierra el pedido en Mercado Libre, se envía una etiqueta al seller, que contendrá la dirección de entrega del pedido. El seller tiene que imprimir esta etiqueta, pegarla en el paquete del pedido y enviarlo a una oficina de correos. 
@@ -113,6 +117,10 @@ Todos los ajustes se realizan dentro de la plataforma de Mercado Libre.
 
 Puede integrar este servicio a su tienda a través del [registro de un stock](https://help.vtex.com/es/tutorial/gerenciar-estoque) destinado exclusivamente para Mercado Envíos Full. Esa integración permite hacer seguimiento al nivel del stock, ya que la cantidad de productos se actualiza automáticamente a medida que se realizan las ventas mediante Mercado Libre Full.
 
+<div class="alert alert-danger">
+Si el vendedor elige el modelo logístico <b>Mercado Envíos Full</b>, es necesario seguir el siguiente orden de configuración: <p><ol><a href="#configurando-el-modelo-de-envio">Configurar modelo de envío</a> <br><a href="#configurar-mercado-envios-full">Configurar Mercado Envíos Full</a></br></ol></p>
+</div>
+
 #### Configurando Mercado Envíos Full
 
 Para configurar, realice los siguientes pasos: 
@@ -120,12 +128,21 @@ Para configurar, realice los siguientes pasos:
 1. En el Admin VTEX, accede a **Envío > Estrategia de Envío > Almacenes**, o escribe *Estrategia de Envío* en la barra de búsqueda en la parte superior de la página, y haz clic en *Almacenes*.  
 2. [Registra](https://help.vtex.com/es/tutorial/gerenciar-estoque) un stock.   
 3. Seleccione la pestaña **Almacenes** y copie el ID del stock que desea utilizar.  
-4. Accede a **Marketplace > Conexiones > Integraciones**, o escribe *Integraciones* en la barra de búsqueda en la parte superior de la página.  
-5. En la integración de Mercado Libre, haga clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />  y seleccione la opción `Editar configuración`.  
+4. Accede en **Marketplace > Marketplace e Integraciones.**
+3. Haz clic en la integracion con Mercado Libre y seleccione la opción `Editar configuración`.  
 6. Ingrese el ID del stock seleccionado en el campo **Almacén Mercado Full**.  
 7. Para finalizar, haga clic en `Guardar Configuración`.  
 
-#### Cómo consultar las facturas de Mercado Libre mediante API
+## Configurando el modelo de envío
+Después de definir qué modelo de envío se utilizará para la integración de tu tienda con Mercado Libre, es necesario configurar en la integración si se utilizará el ME1 o el ME2. Para esto, debes seguir los siguientes pasos, **crear un campo personalizable de producto** y **llenarlo**.  
+
+Para crear un campo de producto, sigue las instrucciones del tutorial [Registrar especificaciones o campos de producto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
+
+<div class="alert alert-warning">
+ El nombre del campo creado debe ser "meli_shipping_mode" y el valor del campo debe ser completado como "me1" o "me2". Si el nombre del campo o el valor es diferente, la integración no reconocerá el atributo. 
+</div>
+
+## Cómo consultar las facturas de Mercado Libre mediante API
 
 Las facturas de los pedidos de [Mercado Envíos Full](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy#mercado-envios-full) emitidas por Mercado Libre pueden consultarse mediante nuestras llamadas de API. Para consultar la factura emitida por Mercado Libre para el pedido, debes utilizar la llamada de API [Get Order](https://developers.vtex.com/vtex-rest-api/reference/orders#getorder). 
 
diff --git a/docs/tracks/es/setting-up-the-order-summary-printing.md b/docs/tracks/es/setting-up-the-order-summary-printing.md
index c77b748a9..f3c1b4bd5 100644
--- a/docs/tracks/es/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/es/setting-up-the-order-summary-printing.md
@@ -16,7 +16,7 @@ trackSlugES: instore-personalizaciones
 
 Cuando el vendedor completa un pedido con inStore, puede imprimir un resumen de ese pedido. Pero, para habilitar esta funcionalidad, usted debe realizar algunas configuraciones.
 
-![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
+![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
 
 Se requieren dos pasos:
 
@@ -50,7 +50,7 @@ No elimine ninguna de las otras propiedades presentes en el objeto <code>window.
 
 Este cambio hará que la opción __Configurar dispositivo__ aparezca en el menú principal de inStore, como se muestra en la imagen a continuación. Es a través de esta opción que configuraremos la impresora.
 
-![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
+![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> hay una opción para imprimir automáticamente el resumen del pedido tan pronto como se complete el pedido. Para habilitarla, agregue la propiedad <code>printPageAutomatically</code> con el valor <code>true</code> dentro del objeto <code>printingConfig</code>. Vea a continuación cómo se vería el código en este caso.
@@ -84,11 +84,11 @@ Con AppKey y AppToken en mano, siga los pasos a continuación:
 2. Abra la aplicación inStore e ingrese a la tienda donde desea configurar la impresora.
 3. En el menú principal de inStore, en la sección Configuración, ahora debería aparecer la opción __Configurar dispositivo__. Haga clic en esa opción.
 
-![15. Configurar impressão de resumo do pedido - 3](https://images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
+![15. Configurar impressão de resumo do pedido - 3](//images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
 
 Usted encontrará el resumen del dispositivo configurado. Si es la primera vez que realiza esta configuración, los campos en esta pantalla estarán vacíos. Si un dispositivo se ha configurado previamente, mostrarán algumas informaciones sobre el dispositivo (nombre del dispositivo e impresora predeterminada). Haga clic en el botón __Editar__.
 
-![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 Aparecerá un formulario que contiene los campos __AppKey__, __AppToken__ y __Nome__ con los que desea identificar el dispositivo. Después de ingresar estos datos, haga clic en __Configurar__.
 
diff --git a/docs/tracks/es/settings-on-via-marketplace.md b/docs/tracks/es/settings-on-via-marketplace.md
index 7175f6e6f..b71a4b26f 100644
--- a/docs/tracks/es/settings-on-via-marketplace.md
+++ b/docs/tracks/es/settings-on-via-marketplace.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configuración en Via Marketplace'
+title: 'Configuración en Casas Bahia Marketplace'
 id: 2oxPVeYpVgA8IrhaDqKon6
 status: PUBLISHED
 createdAt: 2022-01-18T21:39:29.664Z
-updatedAt: 2023-02-08T14:50:54.438Z
-publishedAt: 2023-02-08T14:50:54.438Z
+updatedAt: 2024-01-22T15:59:29.253Z
+publishedAt: 2024-01-22T15:59:29.253Z
 firstPublishedAt: 2022-01-18T22:32:05.415Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
index f83f26748..e8154e440 100644
--- a/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
@@ -3,8 +3,8 @@ title: 'Compartir el carrito utilizando VTEX Sales App Social Selling'
 id: 6deiffo22iKkY27PkfstXy
 status: PUBLISHED
 createdAt: 2021-08-05T14:57:10.773Z
-updatedAt: 2023-05-31T15:22:18.271Z
-publishedAt: 2023-05-31T15:22:18.271Z
+updatedAt: 2023-07-26T19:00:02.450Z
+publishedAt: 2023-07-26T19:00:02.450Z
 firstPublishedAt: 2021-08-05T15:08:06.961Z
 contentType: trackArticle
 productTeam: Shopping
@@ -37,7 +37,7 @@ Esta opción permite compartir un carrito lleno de ítems con uno o más cliente
 
 Vea el paso a paso que se muestra a continuación.
 
-![socialselling-sugestaocarrinho-es](https://images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/dccf53fd6fdac19cd750717c4dd4a0be/socialselling-sugestaocarrinho-es.gif)
+![socialselling-sugestaocarrinho-es](//images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/dccf53fd6fdac19cd750717c4dd4a0be/socialselling-sugestaocarrinho-es.gif)
 
 El vendedor puede enviar el mismo enlace a varios clientes, tantas veces como lo desee. Cada vez que una persona acceda a este enlace, se generará un nuevo carrito de compra, exactamente igual al creado en VTEX Sales App. Cada carrito al que se accede también está asociado a la cuenta del vendedor y, si existe, al código del vendedor.
 
@@ -63,4 +63,4 @@ En este caso, el vendedor tiene que poner los ítems en el carrito, rellenar los
 
 Vea el paso a paso que se muestra a continuación.
 
-![socialselling-paymentlink-es](https://images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/3690f99dd3ac16dd3ae0f90c2bf85cc1/socialselling-paymentlink-es.gif)
+![socialselling-paymentlink-es](//images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/3690f99dd3ac16dd3ae0f90c2bf85cc1/socialselling-paymentlink-es.gif)
diff --git a/docs/tracks/es/shipping-strategies.md b/docs/tracks/es/shipping-strategies.md
index 7829b1c6c..512d753e7 100644
--- a/docs/tracks/es/shipping-strategies.md
+++ b/docs/tracks/es/shipping-strategies.md
@@ -18,7 +18,7 @@ Las opciones de envío a disposición del cliente en el _checkout_ de tu tienda
 
 La estrategia de envío define cómo los almacenes, muelles y políticas de envío interactúan para atender las necesidades de tus clientes y de tu empresa. 
 
-![Estrategia EnvioES](https://images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/d0349a827fc24a4c5a3e1782289fd8c0/Estrategia_EnvioES.png)
+![Estrategia EnvioES](//images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/d0349a827fc24a4c5a3e1782289fd8c0/Estrategia_EnvioES.png)
 
 La estrategia de envío está definida por tres entidades logísticas:
 
diff --git a/docs/tracks/es/size-chart.md b/docs/tracks/es/size-chart.md
index 83879909c..3f9383182 100644
--- a/docs/tracks/es/size-chart.md
+++ b/docs/tracks/es/size-chart.md
@@ -18,7 +18,7 @@ Al comprar ropa o calzados en línea, muchos usuarios suelen tener preguntas sob
 
 La guía de tallas de Mercado Libre es una tabla de medidas o equivalencias que permite que los usuarios vean las medidas exactas para que puedan elegir el producto ideal para ellos. 
 
-![MLB tamanosARG](https://images.ctfassets.net/alneenqid6w5/4xmAfYyY7z2sVGNKAaR2XM/404d040e8a9bae57b462da40b78e2321/MLB_tamanosARG.gif)
+![MLB tamanosARG](//images.ctfassets.net/alneenqid6w5/4xmAfYyY7z2sVGNKAaR2XM/404d040e8a9bae57b462da40b78e2321/MLB_tamanosARG.gif)
 
 ## Entendiendo la guía de tallas
 
@@ -159,7 +159,7 @@ Después de completar la segunda pestaña, se necesita reenviar la plantilla de
 1. Acceda al Admin.
 2. En el módulo Marketplace, seleccione Integraciones.
 3. Seleccione la opción Configuración.
-4. En la integración Mercado Libre, haga clic en el ícono de engranaje<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+4. En la integración Mercado Libre, haga clic en el ícono de engranaje<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 5. Elija la opción **Carga de mapeo**.
 6. Seleccione **Elegir un archivo**.
 7. Ahora, seleccione la plantilla de mapeo de categorías, atributos y variaciones de Mercado Libre.
@@ -172,7 +172,7 @@ Necesita acceder a su cuenta de Mercado Libre para activar la guía de tallas. D
 1. Acceda a su cuenta en Mercado Libre.
 2. Haga clic en la opción **Ventas**.
 3. En el menú del lado izquierdo, seleccione la opción **Publicaciones**.
-4. Haga clic en los 3 puntos <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/5h4riyTF3EAYAM2e04up4O/73040d1e9e6892c6feea96a9bcc6560e/3_pontos.JPG" /> ubicados en el lado derecho de su anuncio. 
+4. Haga clic en los 3 puntos <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/5h4riyTF3EAYAM2e04up4O/73040d1e9e6892c6feea96a9bcc6560e/3_pontos.JPG" /> ubicados en el lado derecho de su anuncio. 
 5. Seleccione **Alterar**.
 6. En la opción Guía de tallas, seleccione la tabla que creó.
 7. Haga clic en **Confirmar**.
diff --git a/docs/tracks/es/store-development.md b/docs/tracks/es/store-development.md
index 4c6a194ef..5abbd1c48 100644
--- a/docs/tracks/es/store-development.md
+++ b/docs/tracks/es/store-development.md
@@ -19,7 +19,7 @@ En una tienda de ecommerce, tanto la interfaz que los usuarios ven y con la que
 - **Frontend**: el frontend comprende la capa visual de una aplicación, como la interfaz de un sitio web o de una aplicación móvil. A través del frontend, los usuarios interactúan con la tienda. En VTEX, hay tres tecnologías diferentes que pueden utilizarse para el desarrollo del storefront de la tienda: CMS Portal (Legado), Store Framework y FastStore.
 - **Backend**: el backend es la capa que computa y procesa todos los datos necesarios para ejecutar las funcionalidades ofrecidas por una determinada aplicación. En VTEX, el desarrollo de integraciones y aplicaciones backend mayormente se realiza a través de VTEX IO y de las API de VTEX.
 
-![storefront mockup](https://images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/f7db8614b227a93b636b593870dab50c/image1.png)
+![storefront mockup](//images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/f7db8614b227a93b636b593870dab50c/image1.png)
 
 En las siguientes secciones, profundizaremos en los principales aspectos y tecnologías relacionados con el desarrollo de la tienda en VTEX.
 
diff --git a/docs/tracks/es/subject-rights.md b/docs/tracks/es/subject-rights.md
new file mode 100644
index 000000000..e8dbe3671
--- /dev/null
+++ b/docs/tracks/es/subject-rights.md
@@ -0,0 +1,32 @@
+---
+title: 'Derechos de los titulares'
+id: 1ZWqUdeKsD8Mm3GKQ8xBI3
+status: PUBLISHED
+createdAt: 2024-05-03T20:20:18.952Z
+updatedAt: 2024-05-03T21:27:03.812Z
+publishedAt: 2024-05-03T21:27:03.812Z
+firstPublishedAt: 2024-05-03T20:25:55.041Z
+contentType: trackArticle
+productTeam: Others
+slug: derechos-de-los-titulares
+locale: es
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugES: datos-y-privacidad
+---
+
+Una solicitud de titular de datos es una petición por escrito que tus clientes pueden hacer para ejercer su derecho a obtener información sobre los datos que están siendo tratados por tu tienda y VTEX.
+
+Cualquier persona tiene derecho a confirmar si una tienda está tratando sus datos o no. Si es así, el titular también tiene derecho a acceder a los datos y a conocer la finalidad del tratamiento, las categorías de datos personales y los destinatarios o categorías de destinatarios con los que se han compartido sus datos personales.
+
+Para más información, consulta la guía [Derechos de los titulares de datos personales](https://help.vtex.com/es/tutorial/derechos-de-los-titulares-de-datos-personales--6imchxTx09icupKMbzHVIM).
+
+## Supresión de datos
+
+Los retailers pueden eliminar datos personales en cualquier momento a petición de sus clientes. El cliente final debe dirigir su solicitud directamente al retailer, quien a su vez deberá transmitirla a VTEX. El derecho de supresión de los datos personales tiene prioridad sobre el periodo de retención.
+
+Si gestionas una tienda VTEX y necesitas ayuda para eliminar datos de usuarios, consulta [Eliminación de los datos de los clientes](https://help.vtex.com/es/tutorial/eliminacion-de-los-datos-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU). 
+
+## Rectificación de datos
+
+Todos los datos personales de clientes de tu tienda pueden editarse en la página [Mi cuenta](https://help.vtex.com/es/tutorial/como-funciona-mi-cuenta--2BQ3GiqhqGJTXsWVuio3Xh), excepto el email. En este caso, se puede eliminar el perfil anterior y crear uno nuevo con un email diferente.
+
diff --git a/docs/tracks/es/technical-and-administrative-measures.md b/docs/tracks/es/technical-and-administrative-measures.md
new file mode 100644
index 000000000..bd56dca21
--- /dev/null
+++ b/docs/tracks/es/technical-and-administrative-measures.md
@@ -0,0 +1,56 @@
+---
+title: 'Medidas técnicas y administrativas'
+id: 7ANSqBP5DgOrVVyglo3Lbh
+status: PUBLISHED
+createdAt: 2024-05-03T20:26:17.710Z
+updatedAt: 2024-05-03T21:12:11.696Z
+publishedAt: 2024-05-03T21:12:11.696Z
+firstPublishedAt: 2024-05-03T20:57:29.358Z
+contentType: trackArticle
+productTeam: Others
+slug: medidas-tecnicas-y-administrativas
+locale: es
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugES: datos-y-privacidad
+---
+
+VTEX opera en varias regiones del mundo y dispone de las herramientas necesarias para satisfacer las exigencias de privacidad de cada país. Por eso, VTEX siempre toma las medidas necesarias para garantizar que su plataforma sea segura y cumpla con las leyes de protección de datos.
+
+Las herramientas que ofrecemos en la plataforma están diseñadas para garantizar que las tiendas cumplan la normativa sobre privacidad. Sin embargo, los retailers también deben adoptar medidas adicionales para cumplir la ley relativa al tratamiento de datos personales. Para comprender estos requisitos, consulta [Roles en la protección de datos](https://help.vtex.com/es/tracks/datos-y-privacidad--4Lc0i0an0DgnEtB0AUwlcq/5f8hTEw3xOALgqzus9VXKd).  Es importante señalar que se trata de directrices generales y que la normativa específica puede contener otras obligaciones.
+
+## Seguridad
+
+VTEX mantiene medidas técnicas y organizativas apropiadas para proteger la seguridad, confidencialidad e integridad de los datos personales en el contexto de la prestación de servicios.
+
+Consulta a continuación las prácticas adoptadas por VTEX, detalladas en el [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/):
+
+* Política antivirus.
+* Clasificación de la información.
+* Gestión de vulnerabilidades.
+* Cifrado de datos personales en reposo y en tránsito.
+* Copia de seguridad y redundancia de datos. VTEX dispone de una herramienta específica que proporciona al cliente los medios para extraer una copia completa de todos los datos personales almacenados en la plataforma. 
+* Recuperación ante desastres y recuperación de incidentes en datos personales.
+* Segregación de clientes y redes.
+* Medidas físicas de seguridad.
+* Supresión garantizada de todos los datos personales una vez finalizada la prestación de servicios.
+* Garantía de que cualquier empleado con acceso a datos personales esté vinculado a acuerdos de confidencialidad con VTEX.
+* Proceso específico de gestión y notificación de incidentes que garantiza que el cliente sea informado, tal como lo exige la legislación de protección de datos, en caso de que se detecte cualquier violación de datos personales.
+* Apoyo a retailers para realizar la [Evaluación de impacto relativa a la protección de datos (EIPD)](https://commission.europa.eu/law/law-topic/data-protection/reform/rules-business-and-organisations/obligations/when-data-protection-impact-assessment-dpia-required_es).
+
+Para obtener más información, consulta [Prácticas de seguridad - VTEX](https://vtex.com/co-es/security/security-practices/).
+
+## Almacenamiento
+
+El [proveedor de hosting](https://vtex.com/co-es/privacy-and-agreements/subprocessors/) utilizado por VTEX es Amazon Web Services (AWS), que almacena datos en la región de Virginia del Norte, en EE. UU. La plataforma AWS es un referente en el sector del hosting en la nube y cuenta con importantes certificaciones como ISO 27001, PCI DSS, CSA, NIST, entre otras. Puedes consultar una lista de certificaciones detallada accediendo a [Programas de conformidad de AWS](https://aws.amazon.com/en/compliance/programs/). La autorización para almacenar datos en AWS se encuentra en nuestro [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/).
+
+VTEX solo almacena los datos personales durante el tiempo necesario para el procesamiento del servicio prestado.
+
+## Conservación de datos personales
+
+Los límites de conservación de datos definen la duración durante la cual los datos pueden almacenarse en VTEX. En estos límites influyen varios factores, como requisitos jurídicos y de cumplimiento, consideraciones sobre la privacidad de datos y los costos. Al establecer límites de conservación de datos pretendemos garantizar el cumplimiento del reglamento, proteger la privacidad de los usuarios y mantener una asignación eficiente de los recursos.
+
+La responsabilidad del cumplimiento de las leyes y reglamentos aplicables recae sobre el propio retailer. Esto incluye definir y respetar los periodos de conservación de datos, que pueden variar en función de la legislación específica a la que esté sujeta cada tienda.
+
+VTEX facilita los datos en función de la capacidad técnica de cada módulo, pero si es necesario cumplir una legislación específica, los retailers deben extraer los datos relevantes de la plataforma. Por lo tanto, corresponde a cada retailer gestionar sus propios periodos de conservación, tal como exige la legislación aplicable, utilizando adecuadamente los recursos disponibles en la plataforma.
+
+VTEX tiene la obligación de conservar los datos personales del comprador durante la vigencia del [MSA](https://vtex.com/co-es/privacy-and-agreements/agreements/). En caso de rescisión del contrato con VTEX, el retailer deberá garantizar la extracción de los datos de Master Data en un plazo de 30 (treinta) días antes de la fecha de rescisión del MSA, de conformidad con la cláusula 7 del [DPA](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/).
diff --git a/docs/tracks/es/technical-support.md b/docs/tracks/es/technical-support.md
new file mode 100644
index 000000000..05cc04710
--- /dev/null
+++ b/docs/tracks/es/technical-support.md
@@ -0,0 +1,34 @@
+---
+title: 'Soporte técnico'
+id: 3thRAdTB3gGwTB0e1fVL3T
+status: PUBLISHED
+createdAt: 2024-02-20T21:34:10.778Z
+updatedAt: 2024-02-22T14:08:41.465Z
+publishedAt: 2024-02-22T14:08:41.465Z
+firstPublishedAt: 2024-02-22T14:08:41.465Z
+contentType: trackArticle
+productTeam: Others
+slug: suporte-tecnico
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+
+Durante y después del desarrollo de una tienda es habitual que surjan dudas sobre implementaciones, [configuraciones de módulos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), [desarrollo de storefronts](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), aplicaciones y otros aspectos técnicos. En este sentido, el soporte técnico está disponible para ayudar en cuestiones relacionadas con la plataforma, el desarrollo de la tienda, aplicaciones e implementaciones. 
+
+La siguiente tabla muestra los principales temas relacionados con el soporte técnico:
+
+| **Tema** | **Descripción**  | **Artículos** |
+|----------|------------------|---------------|
+| [VTEX IO](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#entorno-de-desarrollo)             | VTEX IO es una plataforma de desarrollo en la nube con enfoque low-code, que posibilita a los desarrolladores crear soluciones de ecommerce. El objetivo es ofrecer una forma más económica y eficiente de desarrollar soluciones e integraciones personalizadas dentro del ecosistema VTEX. | [What is VTEX IO?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework)                                                 |
+| [Store Framework](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework)     | Store Framework es una tecnología VTEX para la construcción de storefronts low-code y centrada en la componibilidad. Permite combinar distintas aplicaciones de VTEX IO para montar un storefront. | [What is VTEX Store Framework?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework)<br><br>  [VTEX IO FAQ](https://developers.vtex.com/docs/guides/vtex-io-documentation-frequently-asked-questions)  |
+| [Aplicaciones VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#que-es-una-aplicación-en-VTEX)   | Las aplicaciones VTEX amplían las funcionalidades de la plataforma, ayudando a los retailers a crear experiencias en diversas áreas de la tienda, como marketing, evaluaciones de productos, soporte al cliente, notificaciones, logística, personalización de la tienda y mucho más. | [What is a VTEX App?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app)  |
+| Layout | Tecnología VTEX para la construcción de STOREFRONTS utilizando el CMS Portal Legado. Layout te permite crear y personalizar tu storefront utilizando HTML, JavaScript y CSS a través del Admin VTEX.  Layout está disponible actualmente para algunas tiendas VTEX, pero no para aquellas tiendas que están empezando en la plataforma. | [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj)<br><br>  [Visión general de Layout](https://help.vtex.com/es/tutorial/que-es-el-cms-layout--EmO8u2WBj2W4MUQCS8262)                     |
+| [Integración con ERP](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#integracion-con-erp) | La integración de un ERP con la plataforma VTEX se presenta como una estrategia clave para optimizar las operaciones de una cuenta en una tienda online, brindando la flexibilidad de integrar software externo. | [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide)<br><br>  [FAQ: ERP Integration](https://developers.vtex.com/docs/guides/faq-erp-integration) |
+
+Si el usuario necesita soporte técnico y no encuentra respuesta en los portales y documentación mencionados, puede contactarnos a través de la página de soporte  y elegir la opción **Técnico** a través del VTEX AI Support Bot, un chatbot dedicado a la asistencia técnica, como se muestra en la imagen a continuación:
+
+![Support imagem 2 -ES](//images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/889524bdd11a69c86f075412447b03e2/suppot_imagem2_ES.png)
+
+Si el usuario necesita soporte más allá del VTEX AI Support Bot, puede abrir un ticket haciendo clic en `ABRIR TICKET`. Para más información sobre cómo rellenar un ticket para el soporte técnico, consulta el artículo [Abrir ticket para soporte VTEX - Técnico](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#tecnico).
diff --git a/docs/tracks/es/teste-1.md b/docs/tracks/es/teste-1.md
index 963624555..e33dfee01 100644
--- a/docs/tracks/es/teste-1.md
+++ b/docs/tracks/es/teste-1.md
@@ -3,7 +3,7 @@ title: 'Teste (1)'
 id: 2Oq3MriB8hJ5YmFq3QIlPD
 status: DRAFT
 createdAt: 2021-04-14T14:58:44.451Z
-updatedAt: 2023-06-01T14:02:58.525Z
+updatedAt: 2024-02-23T14:24:12.796Z
 publishedAt: 
 firstPublishedAt: 2021-04-14T15:01:28.601Z
 contentType: trackArticle
@@ -14,4 +14,65 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugES: configurar-la-integracion-de-magazine-luiza
 ---
 
-![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+Enfocados en el éxito de nuestros clientes, en VTEX brindamos soluciones completas para diversos modelos de negocio. La versatilidad del comercio composable se pone al servicio de la innovación y el crecimiento de tu operación.
+
+Y para facilitar la adopción de nuevos recursos, la gestión autónoma de tu negocio y la mejora en la escalabilidad, hemos lanzado la nueva **Guía de onboarding**, un contenido que abarca íntegramente la jornada de operar una tienda VTEX. Accede desde la sección [Comienza aquí](https://help.vtex.com/es/tracks) del Help Center.
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/359WPOFfC5pE91DpoECZJe/7fadfccaa642f496b82cdd09d93a5647/announcement_complete_guide_ES.png" alt="Guia de onboarding">
+</div>
+
+## ¿Qué es la Guía de onboarding?
+
+La **Guía de onboarding** está compuesta por una serie de artículos que incluyen la planificación de la arquitectura de la tienda, configuración del go live, productos para evolucionar el negocio y orientaciones sobre nuestro soporte. La guía presenta ajustes y recursos de la plataforma contextualizados en la jornada de operación de una tienda VTEX.
+
+La **Guía de onboarding** se compone de 3 series:
+
+* [Serie de la tienda VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU)
+* [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS)
+* [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy)
+
+<div class="alert alert-info"> 
+Las series presentan contenidos complementarios, pero son independientes entre sí, lo que significa que se puede explorar el contenido libremente y sin necesidad de seguir una secuencia.
+</div>
+
+Nuestra meta es asegurarnos de que tanto clientes como partners, así como todo el ecosistema de VTEX, puedan sacarle el máximo partido a la **Guía de onboarding**. Con este objetivo de garantizar la pertinencia del material para una amplia gama de negocios, hemos cubierto una jornada completa y abarcadora. 
+
+A continuación, te presentamos una [introducción](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) a lo que encontrarás en la guía.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/1N4nX2r9WxhdSCqr8zOEla/0c63bf21015b75c89c8dc1e75b283662/announcement_headings_track_1_ES.png" height="90" alt="Serie de la tienda VTEX">
+</div>
+
+La **Serie de la tienda VTEX** presenta el contexto inaugural de la operación, comenzando por la definición del [tipo de cuenta y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) que mejor se adaptan a las necesidades de tu negocio. A partir de ese punto, puedes llevar a cabo la [configuración inicial](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) y la configuración de los [módulos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) de la plataforma, enfocándote en acelerar la inauguración de la tienda. Una vez finalizadas las [integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) y la implementación de la [tecnología de frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para la construcción del storefront, es el momento del [go live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) y de la inauguración de la nueva tienda.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6yRmvP19rt7z1mNE7vdWQz/24410786064e27a396dd068b5c37418a/announcement_headings_track_2_ES.png" height="90" alt="Proximos pasos tras el go live">
+</div>
+
+La serie **Próximos pasos tras el go live** presenta la manera en que se realiza el [comercio unificado](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/5Qvw31yH2FPDBl14K5xXHA) con los recursos de la plataforma, abordando [configuración de módulos](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) no mencionada anteriormente, ya que en este punto el enfoque está en la evolución de la operación. Esta serie también presenta los [productos add-on](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) de VTEX, una variedad de productos que pueden adquirirse por separado para posibilitar nuevas estrategias y la diversificación del negocio.
+
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6N7adQ7RxTfTyuIrCDqstZ/e7a5437f1d39e69bfe53047c68c22821/announcement_headings_track_3_ES.png" height="90" alt="VTEX Support">
+</div>
+
+**Soporte en VTEX** presenta el [soporte](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) que proporcionamos a los clientes, que no se limita a una parte específica de la jornada. El [funcionamiento del soporte](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) se aborda también en otras series, ya que la [apertura de tickets](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE) es la vía para determinadas contrataciones y solicitudes. Esta serie ha sido diseñada para que nuestros clientes tengan la mejor experiencia con nuestros servicios y dispongan de la información necesaria para abrir tickets, ya sea en el ámbito del soporte [técnico](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [financiero](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) o [comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
+
+## ¿Por qué creamos este material?
+
+Con el propósito de promover la autonomía de nuestros clientes, hemos estructurado la **Guía de onboarding** enfocándonos en los siguientes aspectos clave:
+
+* **Jornada completa:** se trata de la primera documentación de la jornada completa de la operación de una tienda VTEX, y el contenido está diseñado para acelerar el go live y reducir el time-to-revenue del negocio.
+* * **Contenido inédito:** además del novedoso planteamiento de la jornada, hay contenido inédito, donde podemos destacar: _Serie de la tienda VTEX_ ([Cuentas y arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl), [Integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), [Implementación de frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)), _Acciones después del go live_, ([Productos add-on](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm)) y Soporte VTEX como un todo.
+* **Relevancia general:** el valor de esta guía no se limita a nuevos clientes o a tiendas que se encuentran en las fases previas al go live, ya que consideramos una jornada lo suficientemente abarcadora como para ser relevante para una gran variedad de modelos de negocio.
+
+Esperamos que este material contribuya al éxito de tu negocio y a tu satisfacción con VTEX.
+
+|  | **Guía de onboarding** |  |
+| :---: | :---: | :---: |
+| Parte I | Parte II | Parte III |
+| [Serie de la tienda VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS) | [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy) |
+
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/4CgTVLjK3cazg4dDyVlB8m/eaf5ae6c543344566898cd810a9753a1/announcement_under_table_image_ES.png" alt="Imagen ecommerce">
+</div>
diff --git a/docs/tracks/es/the-reservation.md b/docs/tracks/es/the-reservation.md
index 17d4f653c..4e2584fa7 100644
--- a/docs/tracks/es/the-reservation.md
+++ b/docs/tracks/es/the-reservation.md
@@ -34,7 +34,7 @@ Este es el flujo de reserva en VTEX:
 
  3. Finalmente, una vez que el pedido se encuentra en la etapa de preparación para la entrega, los artículos pasan al estado `Reserva Reconocida`. Este estado indica que el artículo ya no existe en el inventario físico.  
 
-![reservation es](https://images.ctfassets.net/alneenqid6w5/3qiFEUNLlkbc403lzwFCdS/31eaafb108b2e75685cc33441f127407/reservation_es.png)
+![reservation es](//images.ctfassets.net/alneenqid6w5/3qiFEUNLlkbc403lzwFCdS/31eaafb108b2e75685cc33441f127407/reservation_es.png)
 
 <div class="alert alert-warning">
 VTEX no quita automáticamente los artículos del inventario, incluso después de que hayan pasado al estado <code>Reserva Reconocida</code>. Los artículos comprados permanecerán en este estado hasta que el ERP o la tienda los quiten del inventario.
diff --git a/docs/tracks/es/unified-commerce-101.md b/docs/tracks/es/unified-commerce-101.md
index 3868265a4..bd3ce12d1 100644
--- a/docs/tracks/es/unified-commerce-101.md
+++ b/docs/tracks/es/unified-commerce-101.md
@@ -3,8 +3,8 @@ title: 'Omnichannel'
 id: 2LGAiUnHES1enjHsfi8fI3
 status: PUBLISHED
 createdAt: 2020-06-30T20:38:48.297Z
-updatedAt: 2023-05-31T14:45:20.583Z
-publishedAt: 2023-05-31T14:45:20.583Z
+updatedAt: 2023-07-26T18:50:02.780Z
+publishedAt: 2023-07-26T18:50:02.780Z
 firstPublishedAt: 2020-06-30T20:45:00.959Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,24 +16,24 @@ trackSlugES: estrategias-de-comercio-unificado
 
 La evolución del comercio en línea ha traído una serie de mejoras a la experiencia del cliente, y una de las más relevantes es quizás la que transformó la relación multicanal entre el cliente y la tienda en una relación omnicanal.
 
-![32. Unified Commerce 101 - 1 - ES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/3WXokD0CaXdjQIp78KVZ9K/91a5153042717c725708d7a4e289fde4/32._Unified_Commerce_101_-_1_-_ES.png_h_250_h_250)
+![32. Unified Commerce 101 - 1 - ES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/3WXokD0CaXdjQIp78KVZ9K/91a5153042717c725708d7a4e289fde4/32._Unified_Commerce_101_-_1_-_ES.png_h_250_h_250)
 
 En una arquitectura __multicanal__, cada canal se comunica independientemente con la tienda, ya sea comercio electrónico, tiendas físicas, call center, redes sociales, etc. Cuando un cliente interactúa con uno de estos canales, la tienda no tiene conocimiento de quién es ese cliente.
 
 En una arquitectura __omnichannel__, los datos del cliente se comparten entre los canales de la tienda. Esto significa que cuando el cliente que ya ha interactuado con la tienda interactúa a través de un nuevo canal, la tienda sabe quién es ese cliente, cuál es su historial de pedidos, su perfil de compra, etc.
 
-En el omnichannel, sin embargo, los pedidos aún se procesan de forma aislada. Aunque hay intercambio de datos, los pedidos que tienen lugar en el e-commerce viven solamente en el e-commerce, los que tienen lugar en la tienda física viven solamente en la tienda física, y así sucesivamente. Un pedido realizado en un canal no se puede completar en otro, por ejemplo.
+En el omnichannel, sin embargo, los pedidos aún se procesan de forma aislada. Aunque hay intercambio de datos, los pedidos que tienen lugar en el ecommerce viven solamente en el ecommerce, los que tienen lugar en la tienda física viven solamente en la tienda física, y así sucesivamente. Un pedido realizado en un canal no se puede completar en otro, por ejemplo.
 
 El __Comercio Unificado__ resuleve ese problema.
 
-![32. Unified Commerce 101 - 2 - ES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/6nzjDTPhDPePrbcG2lYuV9/39f8bc1548b7c31d13d11bb491540d55/32._Unified_Commerce_101_-_2_-_ES.png_h_250_h_250)
+![32. Unified Commerce 101 - 2 - ES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/6nzjDTPhDPePrbcG2lYuV9/39f8bc1548b7c31d13d11bb491540d55/32._Unified_Commerce_101_-_2_-_ES.png_h_250_h_250)
 
 El Comercio Unificado es una evolución del omnichannel: además del intercambio de datos, esta estrategia también implica __unificar el sistema de procesamiento y gestión de pedidos__. En la práctica, esto significa que todos los pedidos realizados en un canal de la tienda no solo son visibles por otros canales, sino que también pueden ser procesados por ellos.
 
 A continuación se presentan algunos de los escenarios posibles gracias al Comercio Unificado:
 - __Pasillo Infinito__: el cliente compra en un canal (en una tienda física, por ejemplo) y recibe del stock de otra tienda o del Centro de Distribución principal.
 - __Transacción con carrito mixto__: el cliente compra en una tienda física, retira uno de los productos en el acto y recibe el otro en casa desde otro stock.
-- __Retirada en tienda__: el cliente compra en el e-commerce y retira los productos en una tienda física.
+- __Retirada en tienda__: el cliente compra en el ecommerce y retira los productos en una tienda física.
 
 En VTEX, estos y varios otros escenarios son posibles porque el catálogo es accesible para todos los canales y el Sistema de Gestión de Pedidos organiza todos los pedidos, ya sea online o offline.
 
diff --git a/docs/tracks/es/unified-commerce.md b/docs/tracks/es/unified-commerce.md
new file mode 100644
index 000000000..9f585e76b
--- /dev/null
+++ b/docs/tracks/es/unified-commerce.md
@@ -0,0 +1,57 @@
+---
+title: 'Comercio unificado'
+id: 5Qvw31yH2FPDBl14K5xXHA
+status: PUBLISHED
+createdAt: 2024-02-20T20:19:58.572Z
+updatedAt: 2024-04-03T12:14:19.783Z
+publishedAt: 2024-04-03T12:14:19.783Z
+firstPublishedAt: 2024-02-22T14:08:56.252Z
+contentType: trackArticle
+productTeam: Others
+slug: comercio-unificado
+locale: es
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugES: proximos-pasos-tras-el-go-live
+---
+
+# Comercio unificado
+
+El [comercio unificado](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/2LGAiUnHES1enjHsfi8fI3) es una evolución del omnichannel. Además de compartir datos, en esta estrategia también se unifica el sistema de procesamiento y gestión de pedidos. Esto significa que los canales de la tienda no solo pueden ver cualquier pedido realizado en otro canal de ventas, sino también procesarlo. A medida que la interconectividad aumenta, puede ser muy estratégico para el negocio operar con cuentas franquicia y [sellers white label](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
+
+## Cuentas franquicia y sellers white label
+
+Las [cuentas franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) son cuentas asociadas a una [cuenta principal](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). Las empresas que tienen varias tiendas físicas, franquicia o multimarca pueden crear cuentas franquicia vinculadas a la cuenta principal de la marca.
+
+![cuenta principal](//images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/4cc2eed8bca448fa38b8eb39a8428e52/next_steps_image1_ES.png)
+
+Este modelo comparte la información del catálogo y [storefront](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), permitiendo que el stock de las cuentas franquicia esté disponible para la venta en la cuenta principal y que se puedan utilizar varias estrategias de comercio unificado, tales como [envío desde la tienda](#envio-desde-la-tienda), [tiendas físicas como puntos de recogida](#punto-de-recogida) y [pasillo infinito](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+
+Otras ventajas de operar utilizando cuentas franquicia son:
+- Cuentas exclusivas para cada tienda para una mejor gestión del acceso de los colaboradores.
+
+- Mejor gestión y escalabilidad de recursos gracias al registro de muelles y stocks para cada tienda.
+
+- Gestión de promociones específicas para cada cuenta sin la obligación de contratar una nueva [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV).
+
+- Posibilidad de pago en el entorno de la cuenta principal o de la cuenta franquicia ([split de pago](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx)/pedido).
+
+- [Regionalización de sellers](https://help.vtex.com/es/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw) (precio y stock).
+
+- Mejor rendimiento operativo gracias al uso de requests simultáneos en el checkout de la tienda. En una cuenta estándar, en la que se registra la [estrategia de envío](https://help.vtex.com/es/tracks/serie-general-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#ajustes-obligatorios-en-logistica) en la cuenta principal, los requests se procesan en fila, lo que puede resultar en una posible acumulación de requests y un aumento de interrupciones (timeouts). Cada vez que se produce una interrupción, se muestra un mensaje de error en el checkout y el cliente debe presionar F5 o hacer clic en el botón de actualizar para continuar con la compra. Este comportamiento afecta negativamente la experiencia del cliente y disminuye la tasa de conversión de la tienda.
+
+<div class="alert alert-warning">
+  <p>Las <a href="https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a> actúan como un <a href="https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a> de la cuenta principal. Cuando un cliente agrega productos al carrito y simula el envío en el sitio web de la cuenta principal, el <a href="https://help.vtex.com/es/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo de selección de sellers white label</a> asigna automáticamente la cuenta franquicia que se encargará del <a href="https://help.vtex.com/es/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP">fulfillment</a> del pedido. Si uno o más productos del carrito no están disponibles en la cuenta franquicia seleccionada, el sistema asignará otra cuenta disponible para realizar el envío de los productos faltantes, lo que permite que haya más de una entrega para el mismo pedido. Este proceso se lleva a cabo internamente, sin que el cliente vea los sellers.</p>
+</div>
+
+## Envío desde la tienda
+
+Las tiendas físicas pueden funcionar como minicentros de distribución para permitir el envío directo del stock a la dirección del cliente. Este tipo de operación reduce el costo y tiempo de envío y optimiza la planificación logística de la empresa. Para más información, consulta [Ship From Store](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl).
+
+ ## Punto de recogida
+
+Configurar [puntos de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) en persona es beneficioso para las operaciones que implementan [estrategias de comercio unificado](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/2LGAiUnHES1enjHsfi8fI3), donde se optimiza la experiencia de compra del cliente mediante la venta y gestión de pedidos centralizados y la disponibilidad de varias opciones de envío. En VTEX, pueden registrarse los siguientes puntos de recogida:
+
+- Centro de distribución (CD).
+- Tienda física propia.
+- Tienda física franquicia.
+- Tienda física o punto de retirada de terceros utilizando un sistema de almacenamiento seguro, como por ejemplo, un casillero (locker).
diff --git a/docs/tracks/es/unified-search.md b/docs/tracks/es/unified-search.md
index db859abe9..da4fa0b22 100644
--- a/docs/tracks/es/unified-search.md
+++ b/docs/tracks/es/unified-search.md
@@ -1,10 +1,10 @@
 ---
-title: 'Búsqueda unificada'
+title: 'Búsqueda unificada en VTEX Sales App'
 id: 9sXeVwoD60qYYgRJ11r5F
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-08-05T13:47:18.180Z
-updatedAt: 2023-05-31T14:45:09.383Z
-publishedAt: 2023-05-31T14:45:09.383Z
+updatedAt: 2024-05-03T13:22:04.096Z
+publishedAt: 2024-05-03T12:35:21.520Z
 firstPublishedAt: 2021-08-05T14:45:51.056Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,33 +14,45 @@ trackId: 4BYzQIwyOHvnmnCYQgLzdr
 trackSlugES: instore-usando-el-app
 ---
 
-En el pasillo infinito de VTEX Sales App, el vendedor puede buscar los productos deseados y añadirlos al carrito. Para ello, es necesario hacer clic en la lupa de la barra superior de VTEX Sales App e introducir el nombre del producto, el código de referencia o el EAN.
 
-![instore-search-es](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/d3d9724e70f6f8b96242f3c960cb02c0/instore-search-es.png)
+El [pasillo infinito](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn) de VTEX Sales App le permite al vendedor buscar y agregar al carrito productos más allá del stock de su tienda. Para buscar un producto, haz clic en el ícono de lupa <i class="fas fa-search"></i>. Se mostrará la barra de búsqueda en la parte superior de la página de inicio de la tienda.  Ingresa el nombre del producto, código de referencia, ID de SKU o EAN para buscar.
 
-VTEX Sales App tiene una búsqueda unificada, es decir, al buscar un producto en la aplicación, el vendedor lo busca tanto en el almacén local (de la propia tienda física) como en el de otras tiendas físicas y centros de distribución asociados al ecommerce.
+<div class = "alert alert-info">
+Para mejorar la experiencia en situaciones en que la conexión de internet esté lenta, esta funcionalidad tiene recursos de optimización que utilizan la caché del navegador para agilizar la búsqueda.
+</div>
 
-![instore-search-plp-es](//images.contentful.com/alneenqid6w5/1WEugAiPUVHRVTL1ph3zv2/73d2c4adf21592089ad7ed0c08c73f12/instore-search-plp-es.png)
+![Barra busca - ES](//images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/1ad8c720186c675630364918f1d9e0f1/Tela_1_barra_busca.gif)
 
-Al hacer clic en la flecha <i class="fas fa-chevron-down"></i> junto a un producto, podrás ver sus variaciones, las opciones de entrega, la cantidad a agregar al carrito y los botones `Agregar al carrito` y `Más detalles`.
+La búsqueda de VTEX Sales App es unificada, lo que significa que al realizar una búsqueda los resultados se obtienen tanto del stock local (de la tienda física) como de otras tiendas físicas y centros de distribución asociados a la tienda de ecommerce.
 
-![instore-search-details-es](https://images.ctfassets.net/alneenqid6w5/1itzXskqYPkJ4CghrWihy8/463d49a83d0f421f2f62f4a1cf0368a6/Group_1__1_.png)
+Los resultados de búsqueda muestran los productos organizados para mejorar la experiencia del cliente, incluyendo imágenes que facilitan la identificación de los productos e información relevante para el vendedor.
 
-## Filtros
+![Busca unificada - ES](//images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/a94fdd1ace89c89f2081c9fb43174216/Busca_unificada_VTEX_Sales_App.png)
+
+Al hacer clic en la opción `Agregar al carrito`, se mostrará la siguiente información del producto:
+
+- Variación del producto, SKU.
+- Disponibilidad de las opciones de envío
+- Cantidad del producto que se agregará al carrito.
 
-Para utilizar los filtros de búsqueda en VTEX Sales App, primero debes instalar y configurar [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). En este contexto, ten en cuenta algunos puntos de atención:
+Para agregar el producto al carrito, selecciona la variación, envío y cantidad deseada y haz clic en `Agregar al carrito`.
+
+![Carrinho - ES](//images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/defe694e7ce4805172e3879c78411c3c/Adicionar_ao_carrinho_VTEX_Sales_App.png)
+
+## Filtros
 
-* Es imprescindible configurar los filtros que se mostrarán, como se indica en el artículo [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx). De lo contrario, toda la información del producto constará como atributos filtrables en VTEX Sales App.
-* La opción **Autocomplete** no se aplica a la búsqueda en VTEX Sales App, por lo que puede dejarse vacía.
-* Cualquier cambio realizado en la configuración de la búsqueda se aplicará también al ecommerce si la herramienta utilizada es VTEX Intelligent Search.
+Los filtros permiten definir la búsqueda según las preferencias del cliente. Los filtros se pueden combinar para crear criterios de búsqueda precisos. De ser necesario, también es fácil remover cualquier filtro.
 
-Además de la configuración de VTEX Intelligent Search, es necesario [contactar con el equipo de soporte de VTEX](https://support.vtex.com/hc/es-es/requests) para habilitar la funcionalidad de filtros en VTEX Sales App.
+Antes de utilizar los filtros de búsqueda en VTEX Sales App, debes haber instalado y configurado [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Ten en cuenta algunos puntos de atención:
+- Es importante configurar los filtros que se mostrarán según se describe en el artículo Configuración de la búsqueda. De lo contrario, toda la información del producto constará de atributos filtrables en VTEX Sales App.
+- Cualquier cambio realizado en la configuración de la búsqueda se aplicará también a la tienda de ecommerce si la herramienta utilizada es VTEX Intelligent Search.
 
-Una vez activados los filtros, es posible utilizar este recurso siguiendo el procedimiento que se indica a continuación durante la búsqueda de productos.
+Además de la configuración de VTEX Intelligent Search, también es necesario [ponerse en contacto con el equipo de soporte de VTEX](https://help.vtex.com/es/support) para activar la funcionalidad de filtros en VTEX Sales App.
 
-1. Si utilizas VTEX Sales App en un dispositivo móvil, como un smartphone, haz clic en `Filtrar búsqueda`. Si utilizas otro dispositivo con una pantalla más grande, omite este paso.
+Una vez activados los filtros, puedes utilizar este recurso siguiendo el procedimiento a continuación al buscar productos:
+1. Si estás utilizando VTEX Sales App en un dispositivo móvil, como un teléfono inteligente, haz clic en `Filtros`.  Si estás utilizando un dispositivo con una pantalla más grande, omite este paso.
 2. Selecciona los filtros deseados.
-3. Haz clic en `Filtrar búsqueda`.
+3. Haz clic en `Filtrar`.
 
 Los resultados mostrados se filtrarán según tus preferencias.
 
diff --git a/docs/tracks/es/using-custom-controls.md b/docs/tracks/es/using-custom-controls.md
index c58c5fd14..cac3e5e6b 100644
--- a/docs/tracks/es/using-custom-controls.md
+++ b/docs/tracks/es/using-custom-controls.md
@@ -30,7 +30,7 @@ Para crear un control personalizado, siga el procedimiento a continuación:
 2. Haga clic en __Layout__
 3. Haga clic en la carpeta __CMS__
 4. A continuación, haga clic en la carpeta __Custom Elements__
-5. Haga clic en el botón __Add__![8 1](https://images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
+5. Haga clic en el botón __Add__![8 1](//images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
 6. Complete el campo __Name__ con el nombre del control personalizado
 7. Complete el campo __Tag name__. Este es el nombre que se usará en el control al agregarlo al template
 8. Seleccione el tipo de control en __Type__
diff --git a/docs/tracks/es/via-varejo-marketplace.md b/docs/tracks/es/via-varejo-marketplace.md
index 79cdf3e53..fa7803963 100644
--- a/docs/tracks/es/via-varejo-marketplace.md
+++ b/docs/tracks/es/via-varejo-marketplace.md
@@ -1,10 +1,10 @@
 ---
-title: 'Via Marketplace'
+title: 'Casas Bahia Marketplace'
 id: 3rymwJDuc5Z6lQtsyTINim
 status: PUBLISHED
 createdAt: 2020-03-30T17:59:31.535Z
-updatedAt: 2022-01-18T21:38:11.833Z
-publishedAt: 2022-01-18T21:38:11.833Z
+updatedAt: 2023-11-30T20:51:57.221Z
+publishedAt: 2023-11-30T20:51:57.221Z
 firstPublishedAt: 2020-03-30T18:11:59.947Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/viewing-the-email-history-of-an-order.md b/docs/tracks/es/viewing-the-email-history-of-an-order.md
index acfe55f67..d4872e952 100644
--- a/docs/tracks/es/viewing-the-email-history-of-an-order.md
+++ b/docs/tracks/es/viewing-the-email-history-of-an-order.md
@@ -3,8 +3,8 @@ title: 'Ver historial de correos electrónicos de un pedido '
 id: 13YJE9CKzeduRfVplgjC88
 status: PUBLISHED
 createdAt: 2020-01-10T14:07:26.022Z
-updatedAt: 2023-03-31T21:10:54.264Z
-publishedAt: 2023-03-31T21:10:54.264Z
+updatedAt: 2023-09-23T00:49:55.012Z
+publishedAt: 2023-09-23T00:49:55.012Z
 firstPublishedAt: 2020-01-13T14:38:41.810Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -22,3 +22,6 @@ Para ver el historial de correos electrónicos, vaya al módulo **Pedidos**, ent
 
 El sistema que hace este registro se llama __Conversation Tracker__. Para entender más a fondo cómo funciona, consulte el artículo [Cómo se realiza la comunicación con el cliente durante el flujo del pedido](https://help.vtex.com/es/tutorial/comprendiendo-el-conversation-tracker--tutorials_195).
 
+<div class = "alert alert-info">
+Como la comunicación con el cliente es responsabilidad del marketplace, solamente los pedidos con origen marketplace tienen un historial de emails transaccionales. Los pedidos con origen fulfillment no mantienen tal historial.
+</div>
diff --git a/docs/tracks/es/vtex-modules-i.md b/docs/tracks/es/vtex-modules-i.md
new file mode 100644
index 000000000..6895ef93a
--- /dev/null
+++ b/docs/tracks/es/vtex-modules-i.md
@@ -0,0 +1,355 @@
+---
+title: 'Módulos de VTEX I'
+id: 75MX4aorniD0BYAB8Nwbo7
+status: PUBLISHED
+createdAt: 2024-01-17T19:53:53.326Z
+updatedAt: 2024-02-23T00:42:01.506Z
+publishedAt: 2024-02-23T00:42:01.506Z
+firstPublishedAt: 2024-02-22T14:07:05.427Z
+contentType: trackArticle
+productTeam: Others
+slug: modulos-de-vtex-i
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+La plataforma VTEX se compone de diferentes módulos, cada uno responsable de una faceta específica de la operación de la tienda. Este artículo presenta una visión general y las principales configuraciones de los siguientes módulos:
+
+- [Catálogo](#catalogo)
+- [Precios](#precios)
+- [Promociones](#promociones)
+- [Logística](#logistica)
+
+<div class="alert alert-info">
+El artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ">Módulos de VTEX II</a> presenta los módulos <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos">Pagos</a>, <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos">Pedidos</a>, y <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout">Checkout</a>.
+</div>
+
+## Catálogo
+
+[Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) es el módulo de VTEX mediante el cual los retailers configuran sus productos, poniéndolos a disposición en el sitio web de la tienda. La estructura del catálogo define la experiencia de compra del cliente en la tienda online, cuando este navega por las categorías de clasificación de los productos. En la guía [Catalog](https://developers.vtex.com/docs/guides/catalog-overview), los desarrolladores pueden consultar una [visión general del módulo Catálogo](https://help.vtex.com/es/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe) que abarca la [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api).
+
+### Antes de comenzar en Catálogo
+
+No se requieren ajustes preliminares antes de realizar configuraciones en Catálogo, no obstante, los siguientes puntos deben tenerse en cuenta:
+
+- __Navegación del cliente en el sitio web__: es importante que la tienda planifique cómo quiere organizar su [árbol de categorías](#arbol-de-categorias) y saber de antemano la experiencia de navegación que quiere proporcionar a los clientes en la jerarquía de categorías.
+- __Disponibilizar productos para clientes__: para [que un producto esté disponible en la tienda](https://help.vtex.com/es/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382), después de realizar la configuración de Catálogo, el SKU debe tener un [precio](#precios) registrado y [logística](#logistica) para envío. Además, el CMS de la tienda debe estar correctamente configurado.
+
+### Arquitectura de Catálogo
+
+La arquitectura de Catálogo presenta algunos conceptos fundamentales: categoría, marca, producto, SKU (_Stock Keeping Unit_) y especificación. La siguiente imagen ilustra la relación entre estos conceptos:
+
+![arquitetura-catalogo-ES](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
+
+El catálogo de la tienda debe crearse siguiendo el orden de los pasos que se indican a continuación:
+
+1. Creación del [árbol de categorías](#arbol-de-categorias).
+2. Registro de [Marcas](#marcas).
+3. Registro de [Especificaciones](#especificaciones).
+4. Importación de [Productos](#productos).
+5. Importación de [SKUs](#skus).
+
+La siguiente tabla muestra los principales ajustes de Catálogo para la tienda, según el orden de creación:
+
+| **Tema** | **Configuración en el Admin VTEX** | **Configuración por API** |
+| :--- | :--- | :--- |
+| 1. [Árbol de categorias](https://help.vtex.com/es/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categorias) | [Registrar categoría](https://help.vtex.com/es/tutorial/cadastrando-categoria--tutorials_206) | - [Categories](https://developers.vtex.com/docs/guides/categories) <br> - [Create Category](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category) |
+| 2. [Marcas](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) | [Registrar marcas](https://help.vtex.com/es/tutorial/cadastrando-marcas--tutorials_1414) | - [Brands](https://developers.vtex.com/docs/guides/brands) <br> - [Create Brand](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand) |
+| 3.1. [Especificaciones de producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacion-de-producto) | [Registrar especificaciones o campos de producto](https://help.vtex.com/es/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106) | - [Product specifications](https://developers.vtex.com/docs/guides/product-specifications) <br> - [Create Specification](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/specification) |
+| 3.2. [Especificaciones de SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacion-de-sku) | [Registrar especificaciones o campos de SKU](https://help.vtex.com/es/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119) | - [SKU specifications](https://developers.vtex.com/docs/guides/sku-specifications) <br> - [Create Specification](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/specification) |
+| 4. [Productos](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) | [Registrar productos](https://help.vtex.com/es/tutorial/cadastrando-produtos--tutorials_2567) | - [Products](https://developers.vtex.com/docs/guides/products) <br> - [Create Product with Category and Brand](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product) |
+| 5. [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) | [Rellenar campos de registro de SKU](https://help.vtex.com/es/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) | - [SKUs](https://developers.vtex.com/docs/guides/skus) <br> - [Create SKU](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit) |
+
+<br>
+
+<div class="alert alert-warning">
+Puedes obtener información detallada sobre la importación de productos a la plataforma VTEX desde un sistema ERP (Enterprise Resource Planning) o PIM (Product Information Manager) consultando el artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a>.
+</div>
+
+#### Árbol de categorías
+
+El [árbol de categorías](https://help.vtex.com/es/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categorias) define la estructura básica del catálogo. Las categorías actúan como niveles jerárquicos de clasificación de productos, simplificando la búsqueda del cliente y manteniendo el catálogo de la tienda organizado.
+
+Recomendamos crear una jerarquía de hasta tres niveles, incluyendo [Departamentos](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf#departamento), [Categorías](https://help.vtex.com/es/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categorias) y [Subcategorias](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf#subcategoria). Sin embargo, algunas tiendas pueden beneficiarse de una estructura de solamente dos niveles, con departamentos y categorías. Esto depende de la complejidad de la operación y de los tipos de productos ofrecidos.
+
+__Ejemplo__: Departamento `Femenino`, Categoría `Blusas y camisas` y Subcategoría `Camisetas`.
+
+Antes de importar el catálogo de la tienda a VTEX, recomendamos empezar a trabajar en el árbol de categorías creando una tabla como la que se ilustra a continuación. Esto facilita la visualización de la estructura del árbol y la presentación de las especificaciones.
+
+![catalog_arquitecture_table_ES](//images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/60756721b1e21b27b981dee2f2a5e9ad/catalog_arquitecture_table_ES.png)
+
+<div class="alert alert-info">
+En el artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a> puedes consultar más información sobre cómo importar especificaciones para back office.
+</div>
+
+#### Marcas
+
+Las [Marcas](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) identifican a la empresa que crea o revende productos. En VTEX, las marcas deben registrarse de forma independiente, y al crear un producto, es obligatorio asociarlo a una marca ya registrada en la tienda.
+
+#### Especificaciones
+
+Las [especificaciones](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) son propiedades adicionales que se pueden asignar a los productos y SKU de la tienda, como tamaño, color, voltaje o material. Es decir, existen [especificações de producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacion-de-producto) y [especificaciones de SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacion-de-sku).
+
+En el __Catálogo__ de VTEX, las especificaciones se crean en el siguiente orden:
+
+1. __Grupos de especificaciones__: son agregadores de campos de especificación. Deben estar asociados a categorías. Es habitual que solo se cree un grupo a nivel raíz y que todos los campos de especificación se asocien a este grupo.
+2. __Campos de especificación__: son los campos que contendrán información adicional del producto y SKU. Deben estar asociados a categorías y grupos de especificaciones.
+3. __Valores de especificación__: son valores que puedes agregar a campos de especificación.
+
+Las especificaciones siguen la jerarquía del catálogo, por lo que cuando se crea uno de estos grupos en un departamento o categoría, se reproduce en los niveles inferiores.
+
+#### Productos
+
+El [Producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) es el nivel de organización del catálogo que se encuentra en la jerarquía por debajo de las categorías y por encima de los SKU. Como el producto está por encima del SKU en la jerarquía del catálogo, podemos entenderlo como una definición genérica de los ítems que se venden en tu tienda. Un producto debe tener obligatoriamente al menos un SKU asociado.
+
+#### SKUs
+
+El [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) (_Stock Keeping Unit_) es una variación del producto y representa la unidad física en stock que adquiere el cliente. Además, representa el último nivel en la organización de un catálogo, y para que esté activo requiere contar con una imagen y que sus especificaciones estén completas.
+
+### Ajustes opcionales de Catálogo
+
+La siguiente tabla muestra los ajustes opcionales de Catálogo en VTEX:
+
+| **Funcionalidad** | **Descripción** | **Más información** |
+| :---: | :--- | :--- |
+| Colecciones | Una colección es la agrupación de dos o más productos que pueden compartir o no características específicas. <br> Se pueden crear colecciones para asociar productos en función de diversos criterios, como fechas conmemorativas, lanzamientos o productos más vendidos. | __Help Center__ <br> - [Colecciones - Definición del concepto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4hN41yU8IPeb8HKmmaXoca) <br> - [Registrar colecciones (beta)](https://help.vtex.com/es/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye)  <br> __Developer Portal__  <br> - [Create Collection](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection/) <br> - [Get All Inactive Collections](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/collection/inactive) <br> - [Get All Collections](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/collection/search) <br> - [Get Collections by search terms](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/collection/search/-searchTerms-) <br> - [Import File Example](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/collection/stockkeepingunit/importfileexample) <br> - [Add products to Collection by imported file](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection/-collectionId-/stockkeepingunit/importinsert) |
+| Anexos | Un anexo es una personalización opcional y gratuita del producto que se utiliza para añadir información a un SKU. | __Help Center__ <br> - [Registrar un anexo](https://help.vtex.com/es/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU) <br> - [Cómo crear un anexo de suscripción](https://help.vtex.com/es/tutorial/como-criar-um-anexo-de-assinatura--2bUuKyPflA8cOGLv8OvaKK) <br> - [¿Qué es un anexo?](https://help.vtex.com/es/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm)  <br> __Developer Portal__ <br> - [Catalog API - Attachment](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/attachment/-attachmentid-) <br> - [Catalog API - SKU attachment](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuattachment) |
+| Assembly Options | Assembly Options es un tipo de anexo para casos complejos, como la personalización de productos, en los que es necesario gestionar diferentes combinaciones de productos, cantidad, ítems adicionales, costos y stock, y mostrar estas opciones en la página de producto. | __Developer Portal__ <br> - [Assembly Options](https://help.vtex.com/en/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH) <br> - [Assembly Option App](https://developers.vtex.com/docs/guides/assembly-options-app) |
+| Servicios | Servicio con costo adicional que puede ofrecerse con un producto como opcional. Se utiliza para agregar un servicio adicional a un SKU, como embalaje para regalo, personalización o acuerdos de garantía especial. | __Help Center__ <br> - [¿Qué es un servicio?](https://help.vtex.com/es/tutorial/o-que-e-um-servico--46Ha8CEEQoC6Y40i6akG0y) <br> - [Gestión de servicios](https://help.vtex.com/es/tutorial/gerenciamento-de-servicos--3sGqSI93t878ETAWzCZ0E2) <br> - [Importación de servicios](https://help.vtex.com/es/tutorial/importacao-de-servicos--2LRgMnGbX0af7krrs6tXy3) <br> - [Informe de servicios](https://help.vtex.com/es/tutorial/relatorio-de-servicos--7djPWfxtf9qb6hFTOgKDE8) <br> - [Programación de servicios](https://help.vtex.com/es/tutorial/agendamento-de-servicos--78HPYBxDCmpCfa8i40zo7R)  <br> __Developer Portal__ <br> - [Catalog API - SKU service](https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/skuservice/-skuServiceId-) <br> - [Catalog API - SKU service attachment](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicetypeattachment) <br> - [Catalog API - SKU service type](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicetype) <br> - [Catalog API - SKU service value](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicevalue) |
+| Kits | Un kit es un conjunto de SKU que se venden juntos, es decir, un SKU compuesto por uno o más SKU. | __Help Center__ <br> - [¿Qué es un kit?](https://help.vtex.com/es/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28) <br> - [Registrar kit](https://help.vtex.com/es/tutorial/cadastrando-kit--tutorials_215) <br> __Developer Portal__ <br> - [Catalog API - SKU Kit](https://developers.vtex.com/vtex-rest-api/reference/catalog-api-get-sku-kit) |
+
+## Precios
+
+[Precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) es el módulo de VTEX responsable de crear, editar y almacenar los datos de precios de los SKU de la tienda. Para que un producto se venda, el cliente necesita saber cuánto cuesta cada ítem mostrado en la tienda. El módulo Precios tiene funcionalidades que permiten el uso de diferentes estrategias de precios en tu negocio.
+
+### Antes de comenzar en Precios
+
+Antes de configurar los precios de la tienda, hay que registrar en [Catálogo](#catalogo) los productos que se venderán. El catálogo de la tienda debe contener [categorias](https://help.vtex.com/es/tutorial/cadastrando-categoria--tutorials_206), [marcas](https://help.vtex.com/es/tutorial/cadastrando-marcas--tutorials_1414), [productos](https://help.vtex.com/es/tutorial/cadastrando-produtos--tutorials_2567) y [SKUs](https://help.vtex.com/es/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) activos. Si el registro del catálogo se realizó mediante una [integración con un sistema ERP](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#integracion-con-erp), es muy importante confirmar que la información esté correcta antes de continuar. 
+
+### Cómo funciona el módulo Precios
+
+En la siguiente tabla se presentan los principales términos relacionados con el módulo:
+
+| **Término** | **Definición** |
+| :---: | :--- |
+| Precios | Información de los valores de venta de los SKU de la tienda. |
+| [Tablas de precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) | Conjunto de precios de los SKU que se pueden aplicar en un determinado contexto, como una [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Las tablas almacenan la información de los precios que se muestran en el storefront de la tienda. |
+| Precio de costo | Precio pagado por la tienda para adquirir el SKU. |
+| Markup | Margen de beneficio que la tienda desea obtener con la venta del SKU. |
+| [Precio base](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicion) | Valor calculado al combinar el __precio de costo__ y el __markup__. Este es el precio de referencia de un SKU en todas las tablas de precios. |
+| [Precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) | Precio de venta sugerido para un SKU. Este precio se mostrará en la página de producto como el precio __De__, mientras que el precio base será el precio __Por__. |
+| [Regla de precio](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) | Modifica el precio de un SKU en una sola tabla de precios sin cambiar el precio base en las demás. Para que funcione, se debe registrar una regla de precio asociada a la tabla deseada. |
+| [Precio fijo](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy#definiciones) | Precio con prioridad sobre todas las demás configuraciones de precios presentes en una tabla de precios.  |
+| [Redondeo de precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1tUIUvF6BUkDgMsknGaMkF#definiciones) | Estrategia de precios que se basa en el redondeo de precios. El objetivo de este método es influenciar la decisión de compra del consumidor al mostrar precios en un formato más fácil e intuitivo. |
+| [Bloqueo de precio](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7JZhLmI3mjBVu0RMOueoy3#definicion) | Determina las variaciones máximas y mínimas del precio de un ítem. Esta funcionalidad garantiza que los precios de los SKU no cambien a valores indeseados. |
+
+Puedes consultar más información sobre la arquitectura de precios en el artículo [Arquitectura del sistema de precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx).
+
+### Registrar tabla de precios
+
+La arquitectura del módulo Precios se basa en tres conceptos fundamentales:
+
+- Precios
+- Tablas de precios
+- Contextos de aplicación de las tablas de precios
+
+Los precios son la información del valor de venta de tus SKU. Estos precios se almacenan en tablas de precios. A su vez, estas tablas de precios pueden aplicarse a distintos contextos.
+
+La relación entre los precios, la tabla de precios y el contexto que se aplicará se muestra en la siguiente imagen:
+
+![Conceito de Precios-ES](//images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/2a14232018aea8b88b70c21d5a9b6618/Conceito_de_Precios-ES.png)
+
+Puedes registrar tablas de precios para los SKU de la tienda de tres maneras:
+
+- [Admin VTEX](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/2WQ3pVYfQpXkJnHr7VTFBv#admin)
+- [Plantilla](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D)
+- [API](https://developers.vtex.com/docs/api-reference/pricing-api)
+
+Los precios se pueden programar para eventos especiales, como se describe en el artículo [Programación de precios](https://help.vtex.com/es/tutorial/agendar-preco--4vVha6TGzYkguWuMOqCcCk).
+
+### Relación entre tablas de precios y políticas comerciales
+
+Existe una diferencia entre las tablas de precios creadas para [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y las creadas para otros contextos.
+
+Las listas de precios no asociadas a políticas comerciales pueden utilizarse en contextos como __promociones__ y __clústeres de clientes__. Las tablas creadas para políticas comerciales solo pueden asociarse a la propia política comercial. Así, la tabla de precios asociada a una política comercial informa el precio de los SKU de esa política y no puede asociarse a otros contextos.
+
+<div class="alert alert-warning">
+Los conceptos de <b>tabla de precios</b> y <a href="LINK">política comercial</a> son diferentes. La política comercial es el contexto al que se asocia una tabla de precios.
+</div>
+
+A la hora de configurar una política comercial, es imprescindible [especificar la moneda que se utilizará en la tienda](https://help.vtex.com/es/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE). La creación de diferentes políticas comerciales, cada una asociada a una moneda distinta, permite a la tienda mostrar a los clientes los precios en diferentes monedas. 
+
+## Promociones
+
+En VTEX, el retailer puede crear un conjunto de reglas para indicar si los clientes pueden recibir descuentos aplicados en ciertos contextos de compra. [Promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR) es el módulo de VTEX responsable de crear, editar y aplicar descuentos en el carrito de compra del cliente.
+
+### Antes de comenzar en Promociones
+
+Antes de configurar las promociones de tu tienda, es necesario registrar el [Catálogo](https://help.vtex.com/es/tutorial/catalogo-visao-geral--77M8ItLhDXs6aBdQTqToVe) con los productos que se venderán y establecer lo [precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu) de los SKU.
+
+### Cómo funciona el módulo Promociones
+
+Consulta en la tabla a continuación los principales términos utilizados en este contexto:
+
+| **Término** | **Definición** |
+| :---: | :--- |
+| Promoción | Descuento concedido al cliente, que puede estar asociado a uno o varios productos del carrito, a un envío o a un regalo. |
+| Cupón | Código promocional, formado por una secuencia de letras y números. Los cupones están asociados a promociones aplicadas al valor total del carrito. Así, al ingresar un código de cupón válido en el momento de la compra, el cliente puede obtener descuentos sobre el valor del pedido. |
+| Audiencia de campañas | La Audiencia de campañas es una funcionalidad que permite definir el [público objetivo](https://help.vtex.com/es/tutorial/audiencias-de-campanhas--3o7lhpNseXY2WmjZO0gQ6m#publico-objetivo) para una promoción. La funcionalidad consiste en crear criterios de segmentación de clientes. A partir de estos criterios, la plataforma VTEX comprueba automáticamente si los clientes son elegibles para una determinada audiencia de campañas, y en consecuencia, para las [promociones de campaña](https://help.vtex.com/es/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) asociadas. |
+| Promoción de campaña | La promoción de campaña siempre está vinculada a una audiencia de campaña, es decir, a un público objetivo específico. Este tipo de promoción solo se aplicará al público objetivo definido en la campaña. |
+
+### Crear promociones
+
+En VTEX, el retailer puede crear una serie de reglas que, según el contexto de la compra, determinan si se aplicará el descuento y cómo. Entre los parámetros considerados en estas reglas se encuentran: listas de productos, listas de clientes, rangos de códigos postales, valor mínimo de los ítems en el carrito, entre otros.
+
+Los descuentos son, principalmente, de dos tipos:
+
+- __Nominal__: descuento de un valor bruto, como $20.
+- __Porcentual__: descuento de un valor porcentual, como el 10 % del valor total del carrito.
+
+Hay seis tipos diferentes de promociones, cada una relacionada con un escenario distinto:
+
+| **Tipo de promoción** | **Definición** |
+| :---: | :--- |
+| [Regular](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) | Promoción que permite a la tienda ofrecer descuentos de forma flexible, combinando múltiples condiciones, restricciones y beneficios.  |
+| [Comprar Juntos](https://help.vtex.com/es/tutorial/compre-junto--tutorials_323) | Promoción utilizada para conceder descuentos en productos cuando se agregan juntos al carrito. El descuento puede aplicarse a ambos productos. También existe la opción de que el descuento solo se aplique si se añade al carrito una determinada cantidad de uno de los productos. |
+| [Más Por Menos](https://help.vtex.com/es/tutorial/leve-mais-por-menos--tutorials_325) | Promoción utilizada para conceder un descuento cuando el cliente añade al carrito varias unidades del mismo producto. |
+| [Descuento Progresivo](https://help.vtex.com/es/tutorial/desconto-progressivo--tutorials_324) | Promoción utilizada cuando se desea ofrecer un descuento porcentual a un determinado número de productos del carrito. |
+| [Compra uno y lleva uno gratis](https://help.vtex.com/es/tutorial/compre-e-ganhe--tutorials_322) | Promoción utilizada para ofrecer envío gratis o un regalo si se compra un determinado producto. |
+| [Promoción de campaña](https://help.vtex.com/es/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) | Promoción que está siempre vinculada a una audiencia de campaña, es decir, a un público objetivo específico. |
+
+Para todas las promociones puede establecerse un periodo de validez, así como restricciones y limitaciones de uso. Las promociones también pueden programarse para eventos especiales, como se describe en el artículo [Programación de funcionalidades para eventos especiales](https://help.vtex.com/es/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI#programar-promociones).
+
+Consulta más información sobre las posibilidades de aplicar promociones en el artículo [Ejemplos de promociones](https://help.vtex.com/es/tutorial/exemplos-de-promocao--5A8UTc7knvAscxo7e7rMFD).
+
+###  Crear cupones
+
+Puedes crear cupones de descuento en el [Admin VTEX](https://help.vtex.com/es/tutorial/criar-cupom-beta--7lMk3MmhNp2IEccyGApxU) o a través de [API](https://developers.vtex.com/docs/guides/creating-and-managing-coupons-with-promotions-api). Para utilizarlo, el cupón debe estar vinculado al menos a una promoción.
+
+<div class="alert alert-warning">
+Hay una cantidad limitada de cupones activos. Se recomienda encarecidamente la reutilización de los cupones, ya que un exceso de estos podría afectar el desempeño del módulo Promociones.
+</div>
+
+### Crear promociones de campaña
+
+Antes de crear una promoción de campaña se debe crear una [audiencia de campaña](https://help.vtex.com/es/tutorial/criar-audiencia-de-campanha--6cnuDZJzIkIeocewAQQK4K) para definir el público objetivo de la promoción. A partir de los criterios definidos por el retailer pueden seleccionarse segmentos de clientes elegibles para la promoción, los cuales actúan como activadores.
+
+Una vez creada la audiencia de campaña, es necesario asociarla a una [Promoción Regular](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), ccreando así una promoción de campaña. Este tipo de promoción engloba todas las posibilidades presentes en la [Promoción Regular](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) y las siguientes opciones adicionales:
+
+- Público objetivo específico.
+- Envío gratis para todos los envíos disponibles.
+- Tabla de precios promocionales.
+- Regalo entregado por sellers.
+
+### Destacar promociones en la página del producto
+
+Para destacar una promoción en la página del producto (PDP) sigue los pasos que se indican a continuación:
+
+1. [Crea una promoción](https://help.vtex.com/es/tutorial/lista-de-promocoes-beta--4yB7nNdliiFxBTXE19GCIi) de cualquier tipo, a excepción de Comprar juntos.
+2. Activa el campo __Promoción resaltada__ en el formulario de promoción.
+3. Guarda la promoción.
+4. En el [CMS Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj), ingresa el control de visualización de la promoción en el template: `<vtex.cmc:discountHightLight/>`. 
+
+### Sincronización de fechas de promoción, banners y activos digitales
+
+Es importante garantizar una coordinación perfecta al sincronizar la línea de tiempo de las promociones con las fechas de entrega de banners y activos digitales. Para hacerlo, debes comprobar las fechas de las promociones y los banners. Esta alineación estratégica garantiza que las campañas promocionales se apoyen en material visual relevante, maximizando su impacto y eficacia.
+
+## Logística
+
+En VTEX, el módulo [Logística](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx) es el responsable de la [logística y fulfillment](https://help.vtex.com/es/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP) de los pedidos de la tienda, incluyendo la planificación, el transporte, el almacenamiento de los productos y el envío de los pedidos a los clientes.
+
+### Antes de comenzar en Logística
+
+Para realizar los ajustes de logística, deben haberse completado los siguientes pasos:
+
+- __Registrar catálogo__: como la realización de pedidos está relacionada con el almacenamiento de ítems, los productos y SKU de la tienda deben estar registrados en el [Catálogo](#catalogo).
+- __Configurar política comercial__: las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) moldean la experiencia del cliente en el sitio web de una tienda, segmentando desde las condiciones de venta para cada público, hasta los productos ofrecidos, precios, promociones y métodos de envío.
+
+Además, si el modelo de negocio incluye tiendas internacionales y ventas [cross-border](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs), es importante determinar previamente cuál sería el modelo de [arquitetura de la tienda](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitectura-de-la-tienda).
+
+### Ajustes obligatorios en Logística
+
+El conjunto de configuraciones esenciales de logística para una tienda VTEX se denomina [Estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), y se compone de tres conceptos principales: política de envío, almacén y muelle.
+
+- __[Política de envío](#politica-de-envio)__: conjunto de reglas que definen las opciones y condiciones de envío del pedido.
+- __[Almacén](#almacen)__: espacio físico donde se almacenan los productos a la venta.
+- __[Muelle](#muelle)__: local de distribución de los ítems vendidos.
+
+La imagen siguiente muestra cómo se relacionan estos conceptos en la venta de un producto:
+
+![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
+
+La siguiente tabla muestra los principales ajustes de logística de la tienda VTEX:
+
+<div class="alert alert-INFO">
+Recomendamos en primer lugar configurar el almacén, en segundo lugar el muelle y, finalmente, la política de envío.
+</div>
+
+| **Tema** | **Configuración en el Admin VTEX** | **Configuración por API** |
+| :---: | :--- | :--- |
+| [Almacén](#almacen) | [Gestionar almacenes](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| [Muelle](#muelle) | [Gestionar el muelle](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
+| [Políticas de envío](#politica-de-envio) | [Política de Envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| [Stock](#gestion-del-stock) | [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) | [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-) |
+
+####  Almacén
+
+La ruta logística se inicia en el [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb), que es el espacio físico de almacenamiento para los productos que vende la tienda. Cuando los ítems vendidos se alistan en el almacén, se envían al muelle de carga.
+
+#### Muelle
+
+El [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) es el lugar desde el que se distribuyen y envían los ítems, el punto intermedio entre el almacén y las transportadoras. El muelle integra el almacén, la política comercial y la política de envío. Algunos de los casos de uso son:
+
+- Centros de distribución diferentes para un único almacén.
+- Muelle como centro de distribución.
+- Muelle y stock corresponden al mismo espacio físico.
+
+Para determinados productos, puede no ser necesario un espacio físico de distribución. Aun así, para el correcto funcionamiento de las operaciones de la plataforma VTEX hay que configurar el muelle obligatoriamente.
+
+#### Política de envío  
+
+La [Política de envio](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) es un conjunto de reglas que definen las opciones y condiciones de envío que se presentarán a los clientes en el checkout. Las condiciones de envío incluyen transportadora, plazos y valor del envío. La política de envío se vincula al almacén a través del muelle.
+
+La [transportadora](https://help.vtex.com/es/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE) responsable del envío del pedido viene determinada por la política de envío. En primer lugar, deben registrarse las transportadoras en la [plantilla de envío](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127), después, esta plantilla de envío se asocia cuando se crea una política de envío.
+
+### Gestión del stock
+
+El [stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) de la tienda corresponde a los ítems almacenados que están disponibles para la venta. El almacén es la identificación de la ubicación física de almacenamiento, mientras que el stock es el conjunto de SKU disponibles para la venta.
+
+<div class="alert alert-danger">
+En VTEX, la actualización del stock una vez vendidos los ítems debe ser controlada por la propia tienda. De esta forma, tras la venta, el retailer garantiza un control de la cantidad de ítems restantes y de las operaciones de facturación con ERP. En el artículo  <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a> puedes consultar más información sobre cómo importar stock a través del back office.
+</div>
+
+### Lead time
+
+En el Admin VTEX, en __Catálogo > Stock > Gestión de stock__, hay una configuración opcional denominada [Lead time](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B), que permite asignar un plazo de envío a nivel de SKU. Configurar el lead time significa añadir un periodo de tiempo al [cálculo](#calculo-de-envio-de-pedidos) de envío del pedido, lo que resulta estratégico en algunos contextos.
+
+Entre los [principales casos de uso](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#principales-casos-de-uso), podemos mencionar productos de proveedores externos, escenarios de _dropshipping_ y venta de ítems personalizables. Configurar el lead time brinda mayor flexibilidad para definir los plazos de procesamiento y envío del producto por terceros.
+
+### Cálculo de envío de pedidos
+
+Para realizar el [cálculo de envio](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) de los pedidos, la plataforma VTEX considera las siguientes configuraciones:
+
+![Envío de Pedidos_ES](//images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/19fd25987e328aeb22f03f48764b2479/Env_o_de_Pedidos_ES.png)
+
+- [Lead time](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B): cantidad de tiempo configurable para el SKU de un almacén. Esta configuración es opcional y se establece en cero días de forma predeterminada.
+- [Tiempo de almacén](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137): tiempo que tarda el SKU en pasar del almacén al [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Esta configuración es obligatoria, pero el tiempo puede establecerse en cero.
+- [Tiempo de muelle](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW): tiempo que tarda el SKU en salir del muelle para ser enviado al cliente. Esta configuración es obligatoria, pero el tiempo puede establecerse en cero.
+- [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140): agrupa las reglas y condiciones de envío que se presentan a los clientes en el checkout, incluyendo transportadoras, valor del envío, horarios de funcionamiento de las transportadoras, las ventanas de entrega y la capacidad de entrega.
+
+El [simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144) permite al retailer simular y analizar las opciones de entrega disponibles para un pedido en una ubicación. La simulación comprueba la viabilidad y las condiciones de envío del pedido, como disponibilidad de los ítems, métodos de envío, costos y plazos.
+
+### Ajustes opcionales de Logística
+
+Para adaptarse a los distintos modelos de negocio, la plataforma VTEX ofrece una serie de ajustes opcionales, como se muestra en la tabla a continuación:
+
+| **Funcionalidad** | **Descripción** |
+| :---: | :--- |
+| Puntos de recogida | Los [puntos de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) son ubicaciones físicas que la tienda ha establecido para que los clientes recojan sus pedidos. Configurar puntos de recogida es una buena opción para las operaciones omnichannel, especialmente cuando hay un gran número de tiendas físicas, ya que cada tienda física puede convertirse en una opción para que el cliente recoja su pedido, aumentando la versatilidad de su red logística. |
+| Feriados | La funcionalidad [Feriados](https://help.vtex.com/es/tutorial/cadastrar-feriados--2ItOthSEAoyAmcwsuiO6Yk) permite a la tienda establecer días en los que no se procesan envíos, y esto se tiene en cuenta al calcular el tiempo de envío del pedido. |
+| Reserva | La [reserva](https://help.vtex.com/es/tutorial/como-a-reserva-funciona--tutorials_92) es una solución VTEX que impide que un mismo ítem se venda más de una vez. Cuando el cliente simplemente añade un producto al carrito, no se genera una reserva; su prioridad sobre el ítem solo se activa al finalizar la compra.|
+| Capacidad de entrega | La [Capacidad de entrega](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi#capacidade-de-entrega) es el límite de envíos que puede realizar la tienda en un periodo determinado. Poder delimitar el número de ítems o pedidos que se pueden enviar en cada ventana de envío significa tener más control sobre la preparación de los pedidos y aumentar las posibilidades de cumplir la promesa de entrega establecida con el cliente en el checkout. |
+| Geolocalización | La [Geolocalización](https://help.vtex.com/es/tutorial/gerenciar-geolocalizacao--tutorials_138) es el registro de las ubicaciones de entrega a partir de la latitud y la longitud de las direcciones. Esta funcionalidad es muy utilizada en direcciones de zonas rurales e industriales (donde hay división por terrenos) o en zonas de riesgo, cuando es necesario eliminar ciertos lugares de entrega dentro de una región. |
+
+Consulta más información sobre conceptos logísticos en VTEX en el artículo [Glosario de logística](https://help.vtex.com/es/tutorial/glossario-de-logistica--16DSSiXn548rsidi0A8Hby), también ponemos a disposición contenido específico para desarrolladores sobre la [Logistics API](https://developers.vtex.com/docs/api-reference/logistics-api#overview) en el artículo [Fulfillment and Logistics](https://developers.vtex.com/docs/guides/fulfillment).
diff --git a/docs/tracks/es/vtex-modules-ii.md b/docs/tracks/es/vtex-modules-ii.md
new file mode 100644
index 000000000..52ceb26f6
--- /dev/null
+++ b/docs/tracks/es/vtex-modules-ii.md
@@ -0,0 +1,300 @@
+---
+title: 'Módulos de VTEX II'
+id: 3MYcZaojb5HSUg6ufm6GxQ
+status: CHANGED
+createdAt: 2024-02-07T13:20:33.477Z
+updatedAt: 2024-02-22T17:08:09.649Z
+publishedAt: 2024-02-22T14:07:12.569Z
+firstPublishedAt: 2024-02-22T14:07:12.569Z
+contentType: trackArticle
+productTeam: Others
+slug: modulos-de-vtex-ii
+locale: es
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugES: serie-de-la-tienda-vtex
+---
+
+Además de los módulos abordados en el artículo anterior, como [Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Precios](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precios), [Promociones](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promociones) y [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica), la plataforma VTEX cuenta con otros módulos necesarios para el funcionamiento de la tienda. Este artículo presenta una visión general y las principales configuraciones de los siguientes módulos:
+
+- [Pagos](#pagos)
+- [Pedidos](#pedidos)
+- [Checkout](#checkout)
+
+## Pagos
+
+El módulo [Pagos](https://help.vtex.com/es/tracks/pagos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB) de VTEX se encarga de coordinar todas las operaciones financieras que se realizan en una tienda. Configurándolo, puedes especificar qué proveedores, medios y condiciones de pago se ofrecerán a los clientes en el checkout, además de revisar la información sobre las transacciones de pago realizadas para cada pedido.
+
+### Antes de comenzar en Pagos
+
+Para procesar y recibir los pagos de las compras realizadas en una tienda VTEX, es necesario contratar los servicios de uno o más proveedores de pago. Este contrato se realiza directamente entre el retailer y el proveedor respectivo, sin intervención ni participación de VTEX. Accede a la [Lista de proveedores de pago](https://help.vtex.com/es/tutorial/lista-de-proveedores-de-pago-por-pais--2im3BEGXxSAcRuxEaIHPvp) para consultar la disponibilidad de proveedores en VTEX en cada país.
+
+<div class="alert alert-warning">
+Recomendamos integrar más de un proveedor de pago en tu tienda para proporcionar una experiencia óptima al cliente al ofrecer diversos medios y condiciones de pago. Esto permite operar con diferentes tarifas y costos, mejorando el desempeño del negocio.
+</div>
+
+Los ajustes de pago descritos en esta serie pueden realizarse en cualquier momento durante el proceso de onboarding. No obstante, para que la tienda pueda realizar cualquier tipo de transacción relacionada con pagos, es necesario que previamente se hayan configurado los módulos [Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Precios](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precios) y [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica).
+
+### Cómo funciona Pagos
+
+La siguiente tabla muestra los principales agentes y términos utilizados en el contexto de este módulo:
+
+| **Término** | **Descripción** |
+| :---: | :--- |
+| **Gateway** | Sistema responsable de procesar la información de pago de una compra en el checkout. |
+| **Adquirente** | Empresa que procesa pagos con tarjeta de crédito y débito. |
+| **Subadquirente** | Empresa que procesa pagos y actúa como intermediaria entre adquirentes, proveedores antifraude y retailers. |
+| **Red de la tarjeta** | Empresa responsable de definir las reglas de negocio aplicadas a las tarjetas de crédito y débito. |
+| **Emisor de la tarjeta** | Institución financiera responsable de autorizar un medio de pago, como tarjeta de crédito o débito. |
+| **Proveedor de pago** | Empresa que ofrece soporte para transacciones electrónicas en distintos medios de pago. |
+| **Proveedor de antifraude** | Empresa responsable de realizar análisis de riesgos en las operaciones con tarjetas de crédito y débito. |
+| **Payment Provider Protocol** | Protocolo de comunicación de un proveedor de pago empleado para la transmisión de datos relacionados con el pago. Para más información sobre la integración de proveedores de pago en VTEX, consulta [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). |
+| **Medios de pago** | Métodos utilizados por el cliente para pagar una compra, como tarjetas de crédito, débito o carteras digitales. |
+| **Condiciones de pago** | Reglas establecidas para un determinado medio de pago, por ejemplo, número máximo de cuotas permitidas e intereses aplicados. |
+
+### Flujos de pago y transacciones
+
+Cuando se finaliza una compra en VTEX, se crea una nueva transacción y se inicia el flujo de pago. El siguiente ejemplo muestra el flujo de pago para una compra realizada con tarjeta de crédito:
+
+![payments-es](//images.ctfassets.net/alneenqid6w5/5QPFkvZhpZzRWuq15zlMoz/1a6dd2fc04096a775c1208ff0e20088a/payments_image1_ES.JPG)
+
+A medida que la información se transmite entre los agentes encargados de procesar los datos, el status de la transacción del pago se actualiza para indicar en qué etapa del flujo se encuentran los recursos. Para ilustrar el flujo de pago con tarjeta de crédito, tenemos el siguiente ejemplo de status de la transacción:
+
+![payments-flow-es](//images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/4d17ee553dfe4fadfdc59a502339159e/payments_image2_ALL.JPG)
+
+Consulta más información sobre cada paso en el artículo [Flujo de la transacción en Pagos](https://help.vtex.com/es/tutorial/flujo-de-la-transaccion-en-pagos--Er2oWmqPIWWyeIy4IoEoQ). Para acceder a más información sobre transacciones en el Admin VTEX, consulta el artículo [Ver detalles de la transacción](https://help.vtex.com/es/tracks/pagos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
+
+### Configurar pagos en la tienda
+
+Tras establecer el contrato con un proveedor de pago, debes configurarlo y definir los medios y condiciones de pago que estarán disponibles en el checkout de la tienda.
+
+#### Activar un proveedor de pago
+
+Es necesario activar los proveedores de pago en la tienda a fin de permitir la transmisión y recepción de la información esencial para completar las transacciones de pago. Para activar cada proveedor deben seguirse los pasos a continuación:
+
+1. Accede a la [Lista de proveedores de pago por país](https://help.vtex.com/es/tutorial/lista-de-proveedores-de-pago-por-pais--2im3BEGXxSAcRuxEaIHPvp).
+2. Selecciona el proveedor deseado haciendo clic en el respectivo link en la tabla.
+3. En el Admin VTEX, configura el proveedor según las instrucciones descritas en el artículo de configuración.
+
+<div class = "alert alert-info">
+También se puede acceder a los artículos de configuración de proveedores escribiendo el nombre del proveedor deseado en la barra de búsqueda del <a href="https://help.vtex.com/es/">Help Center</a>.
+</div>
+
+#### Definir medios y condiciones de pago
+
+Tras habilitar el proveedor de pago, debes configurar los medios y condiciones de pago que dicho proveedor procesará. Sigue los pasos a continuación para realizar este procedimiento:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Pagos > Configuración**, o ingresa **Configuración** en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña **Condiciones de pago**, haz clic en el botón **+**.
+3. Haz clic en el nombre del medio de pago que desees.
+4. Si lo deseas, puedes cambiar el nombre del medio de pago en el campo **Nombre de la condición**.
+5. Activa la opción **Status**.
+6. En **Procesar con proveedor** selecciona el nombre del proveedor de pago.
+7. Si deseas utilizar un sistema antifraude, selecciona la opción **Utilizar antifraude**. Más información en [Configurar un proveedor antifraude (opcional)](#configurar-proveedor-antifraude).
+8. Si el medio de pago elegido permite definir pagos en cuotas, selecciona la opción **En cuotas** en **¿Al contado o en cuotas?**, e ingresa la información deseada. Más información en [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455).
+9. Si lo deseas, también puedes configurar condiciones de pago especiales. Más información en [Agregar condiciones especiales de pago](#agregar-condiciones-especiales-de-pago).
+10. Haz clic en `Guardar`.
+
+### Ajustes opcionales en Pagos
+
+También puedes realizar los siguientes ajustes de pago opcionales según el perfil operacional de la tienda:
+
+- [Agregar condiciones especiales de pago](#agregar-condiciones-especiales-de-pago)
+- [Configurar medios de pago personalizados](#configurar-medios-de-pago-personalizados)
+- [Configurar proveedor antifraude](#configurar-proveedor-antifraude)
+- [Crear tarjetas de regalo](#crear-tarjetas-de-regalo)           
+- [Activar carteras digitales](#activar-carteras-digitales)
+- [Customer Credit.](#customer-credit)
+
+#### Agregar condiciones especiales de pago
+
+Las condiciones especiales de pago permiten definir reglas específicas para un determinado medio de pago, como fecha de vencimiento, emisor de la tarjeta, política comercial, condición comercial y el nombre de la cuenta. 
+
+Para obtener más detalles sobre cada tipo de condición especial de pago, consulta el artículo [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+
+#### Configurar medios de pago personalizados
+
+En VTEX se pueden configurar los siguientes medios de pago personalizados:
+
+- **Pagarés**: compromiso de pago entre el retailer y el cliente sobre el valor de una compra. Para autorizar la transacción de compra se requiere la aprobación manual del retailer. Más información en [Configurar pagos con pagarés](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ).
+
+- **Tarjetas de tienda (red propia)**: tarjeta de crédito o débito emitida en asociación entre una empresa y una red de tarjetas (Visa, Mastercard, entre otras). Solo puede utilizarse para compras en establecimientos que formen parte de la red del emisor de la tarjeta. Más información en [Configurar pagos con private label (red propia)](https://help.vtex.com/es/tutorial/configurar-pagos-con-private-label--428FgVdSGQUeAOoogkaIw4).
+
+- **Tarjetas de tienda (cobranded)**: tarjeta de crédito o débito de marca propia, emitida para uso exclusivo en compras realizadas en la empresa emisora de la tarjeta. Más información en [Configurar pagos con tarjeta de tienda (cobranded)](https://help.vtex.com/es/tutorial/configurar-pagos-con-tarjeta-de-tienda-cobranded--jrkLK41IjuquUmyKUi86Q).
+
+#### Configurar proveedor antifraude
+
+También pueden configurarse proveedores antifraude en la tienda para analizar los pagos con tarjeta de crédito y débito, siempre que exista un contrato entre el retailer y el proveedor. Su uso es recomendable, pero opcional.
+
+Para consultar los proveedores antifraude actualmente integrados en VTEX, escribe el nombre del proveedor deseado en la barra de búsqueda del [Help Center](https://help.vtex.com/es/) o accede al Admin VTEX, tal y como se describe en el artículo [Configurar el antifraude](https://help.vtex.com/es/tutorial/como-configurar-antifraude--tutorials_446).
+
+#### Crear tarjetas de regalo
+
+Las tarjetas de regalo, también conocidas como gift cards o vouchers, pueden utilizarse en las tiendas VTEX como medio de pago o programa de fidelidad.
+
+VTEX cuenta con su propio proveedor de tarjetas de regalo, lo que posibilita la creación y gestión de estas tarjetas mediante el Admin VTEX o la API de Gift Card. Consulta más información sobre las características de creación de los dos métodos en [GiftCard API](https://developers.vtex.com/docs/api-reference/giftcard-api).
+
+Además, también es posible ofrecer tarjetas de regalo de proveedores externos a través de la [API de GiftCard Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api). Para utilizar un proveedor externo de tarjetas de regalo es necesario contar con un contrato establecido con dicho proveedor y verificar que ya esté integrado en VTEX. Más información en los artículos [Configurar tarjeta de regalo](https://help.vtex.com/es/tutorial/gift-card--tutorials_995) y [Gift Card system architecture](https://developers.vtex.com/docs/guides/gift-card-integration-guide-system-architecture).
+
+#### Activar carteras digitales
+
+Las carteras digitales proporcionan entornos seguros para almacenar de manera encriptada los datos bancarios y de tarjetas de crédito, a los cuales los clientes pueden acceder al realizar una compra. La seguridad de este medio de pago reside en la eliminación de la necesidad de completar todos los datos en el checkout en cada compra. Solo se requiere la autenticación en el propio entorno de la cartera digital.
+
+En VTEX, se pueden ofrecer carteras digitales nativas, como [Google Pay](https://help.vtex.com/es/tracks/cartera-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/61JMBvM5Vanqj6RaJsP8CT), o integradas, como [Apple Pay](https://help.vtex.com/es/tracks/cartera-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/STKWiXJSR9ImPt5EEC2aL), [Samsung Pay](https://help.vtex.com/es/tutorial/configurar-samsung-pay-como-meio-de-pagamento--5Yj9rgzOCVYuGmAumQlfpP) y [PayPal](https://help.vtex.com/es/tutorial/configurar-paypal--4p3sD9u1moq2Aya2oc684w). Más información en [Cartera digital (ewallet)](https://help.vtex.com/es/tracks/cartera-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/7jLbdfch9Oe2yYbQa9zwE1).
+
+#### Customer Credit
+
+Customer Credit es la solución de VTEX que posibilita la oferta de crédito a clientes específicos, brindándoles la opción de pagar sus compras en un periodo de tiempo más extenso. Esta aplicación proporciona acceso a la gestión de clientes, la configuración de plazos y cuotas, definición de crédito y seguimiento del status de las facturas emitidas, entre otras funcionalidades.
+
+Para más información, consulta [Customer Credit - Visión general](https://help.vtex.com/es/tutorial/customer-credit-vision-general--1uIqTjWxIIIEW0COMg4uE0) y [Customer Credit - Cómo empezar](https://help.vtex.com/es/tracks/customer-credit-como-empezar--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
+
+## Pedidos
+
+Cuando el cliente finaliza la compra se genera un [pedido](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE) en VTEX. Los pedidos pueden gestionarse a través del Admin VTEX, en **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-los-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**, accediendo a una [página de detalles](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl) de la compra, o a través de API. En la guía [Orders](https://developers.vtex.com/docs/guides/orders-overview) los desarrolladores pueden consultar una visión general de contenido sobre [Orders API](https://developers.vtex.com/docs/api-reference/orders-api#overview).
+
+### Antes de comenzar en Pedidos
+
+Para que la tienda pueda gestionar los pedidos recibidos la plataforma VTEX no requiere configuraciones obligatorias, y ofrece varias [configuraciones opcionales](#ajustes-opcionales-en-pedidos) que pueden resultar estratégicas para diferentes modelos de negocio.
+
+Sin embargo, para que el cliente pueda realizar una compra y generar un pedido, la tienda necesita tener productos registrados y con precio, ofrecer [medios de pago](https://help.vtex.com/es/tutorial/diferencia-entre-medios-de-pago-y-condiciones-de-pago--3azJenhGFyUy2gsocms42Q) y garantizar el envío del pedido. Esto implica que deben realizarse ajustes en los siguientes módulos:
+
+- [Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo)
+- [Precios](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precios)
+- [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica)
+- [Pagos](#pagos)
+
+### Integración de pedidos
+
+Es habitual que las tiendas deseen [integrar sus pedidos](https://developers.vtex.com/docs/guides/erp-integration-guide) a sistemas como ERP (Enterprise Resource Planning) y WMS (Warehouse Management System). La [implementación del backend](https://help.vtex.com/en/tracks/serie-general-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) permite a la tienda automatizar algunas acciones en el procesamiento de pedidos, como:
+
+- Recibir notificaciones del progreso de los pedidos y su status en el [flujo de pedidos](https://help.vtex.com/es/tutorial/flujo-y-status-de-pedidos--tutorials_196).
+- Obtener información sobre los pedidos que deben ser alistados y empacados.
+- Enviar la [factura](https://help.vtex.com/es/tutorial/como-facturar-manualmente-un-pedido--7p1h852V5t54KyscpgxE2v) a la plataforma VTEX, que la remitirá al cliente.
+- Realizar [cambios de ítems](https://help.vtex.com/es/tutorial/cambiar-items-de-un-pedido-finalizado--tutorials_190) en el pedido.
+
+Existen dos formas diferentes de monitorear los cambios de status de los pedidos, el [feed](https://developers.vtex.com/docs/guides/orders-feed) o el [hook](https://developers.vtex.com/docs/guides/orders-feed#hook). Consulta más información sobre integración de pedidos en el artículo [Integraciones de backend](https://help.vtex.com/en/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu).
+
+### Gestionar pedidos
+
+En el Admin VTEX, en **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-los-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**, pueden realizarse las siguientes acciones:
+
+- Ver una lista de todos los pedidos de la tienda.
+- Acceder a la información de compra en la [página de detalles](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) haciendo clic en el pedido.
+
+En la página de detalles del pedido, también puede monitorearse la información del [flujo del pedido](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196). La imagen siguiente ilustra un ejemplo del flujo cuando la tienda actúa simultáneamente como marketplace y seller:
+
+![order-flow-es](//images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/7cb86712ed404f7ae9a8d804820ae673/pedido_fluxo_completo_es.png)
+
+Para ubicar el registro de una compra en el Admin VTEX, además de poder [filtrar pedidos](https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192) en la página **Todos los pedidos**, existe la opción de buscar a través de la barra de búsqueda global, presente en todas las páginas del Admin VTEX. Para realizar la búsqueda solo hay que seleccionar la opción `Pedidos` en la esquina derecha de la barra de búsqueda y utilizar cualquiera de los siguientes valores:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
+<div class="alert alert-warning">
+Solo se puede acceder a la información de los pedidos creados en los dos últimos años. Este mismo periodo es aplicable para que los clientes accedan a sus pedidos a través de <a href="">Mi cuenta</a>.
+</div>
+
+VTEX proporciona dos funcionalidades importantes para que los clientes de la tienda puedan hacer un seguimiento de sus pedidos: [emails transaccionales](#emails-transaccionales) y el espacio de los clientes denominado [Mi Cuenta](#funcionalidad-mi-cuenta).
+
+#### Emails transaccionales
+
+VTEX ofrece de forma nativa el envío de [emails transaccionales](https://help.vtex.com/es/tutorial/understanding-the-message-center--tutorials_84), para que la tienda pueda enviar emails automáticos al cliente informándole de las actualizaciones del pedido. En resumen, a medida que el pedido avanza en el flujo de procesamiento, el cliente puede recibir notificaciones por email, lo que le permite realizar un seguimiento de eventos como la aprobación del pago y el envío del pedido.
+
+La plataforma ofrece una serie de [plantillas de emails transaccionales](https://help.vtex.com/es/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my), pero también se puede personalizar la comunicación. La siguiente lista ofrece la información principal sobre estas configuraciones opcionales, que son independientes entre sí:
+
+- **Alias:** email alternativo generado automáticamente por la plataforma VTEX para [enmascarar](https://help.vtex.com/es/tutorial/configuracoes-gerais--tutorials_194#tipo-de-mascara-de-conversa) el email del cliente en los emails transaccionales de la tienda. Este [tipo de máscara de la conversación](https://help.vtex.com/es/tutorial/configuracoes-gerais--tutorials_194#tipo-de-mascara-de-conversa) representa una mayor protección para los datos del cliente, ya que el email alternativo se crea de forma que no sea legible por sistemas externos.
+- **Availability Notify o Avísame**: configuración del botón [Avísame](https://help.vtex.com/es/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e) en la página de producto visto por el cliente en el sitio web de la tienda. El botón se hace visible cuando un producto no está disponible, permitiendo al cliente ingresar su email en el campo correspondiente para recibir una notificación cuando el producto vuelva a estar disponible para su compra.
+
+#### Funcionalidad Mi cuenta
+
+[Mi cuenta](https://help.vtex.com/es/tutorial/como-funciona-mi-cuenta--2BQ3GiqhqGJTXsWVuio3Xh) es la solución que garantiza a los clientes de la tienda autonomía en el seguimiento de sus pedidos y en la actualización de sus datos personales. Es un entorno exclusivo para cada cliente, al que se accede mediante nombre de usuario y contraseña.
+
+Una de las ventajas de **Mi cuenta** es que la funcionalidad hace que la comunicación entre el cliente y la tienda sea más directa, además de permitir al cliente realizar acciones como pedir nuevamente o cancelar el pedido. Una comunicación más eficaz tiende a reducir la necesidad de atención al cliente, lo que a su vez supone un ahorro de costos para la tienda.
+
+### Ajustes opcionales en Pedidos
+
+La siguiente tabla muestra algunos ajustes adicionales para el módulo Pedidos:
+
+| **Funcionalidad** | **Descripción** |
+| :---: | :--- |
+| Suscripciones | [Suscripciones](https://help.vtex.com/es/tutorial/como-funciona-suscripciones--frequentlyAskedQuestions_4453) es un programador automático de pedidos para facilitar a los clientes de la tienda la realización de compras recurrentes. El cliente indica los ítems que desea comprar y la frecuencia con que deben realizarse pedidos automáticos.<br><br>[Configurar Suscripciones](https://help.vtex.com/es/tutorial/como-configurar-suscripciones--1FA9dfE7vJqxBna9Nft5Sj) es especialmente interesante para modelos de negocio como supermercados y tiendas de productos para mascotas, donde los clientes consumen los mismos productos de forma habitual. |
+| Televentas | La solución de [televentas](https://help.vtex.com/es/tutorial/funcionalidades-de-televentas--UqhiccIRIK2KD0OqkzJaS) permite al equipo de atención al cliente de la tienda una mayor autonomía para prestar servicio a los clientes. Al [configurar las funcionalidades de televentas](https://help.vtex.com/es/tutorial/como-configurar-las-funcionalidades-de-televentas--76FNgQP2Glc4umMJ5Yr50R) se habilita a los operadores de la tienda para realizar tareas como:<br><br>- Comprar en nombre de un cliente.<br>- Ajustar manualmente el precio de los ítems de un carrito.<br>- Modificar pedidos existentes.<br>- Gestionar la información del perfil de un cliente en [Mi cuenta](#funcionalidad-mi-cuenta). |
+| Divergencia de precios | En las [estrategias de marketplace](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-en-vtex--tutorials_402) de la tienda en el ecosistema VTEX, puede darse el caso de que el precio fijado por el seller sea diferente del precio ofrecido por el marketplace. Las promociones existentes en el marketplace, por ejemplo, pueden tener un impacto en el precio que el seller fijó para la venta de su producto.<br><br>Para evitar errores en el procesamiento de los pedidos, el seller VTEX puede [configurar reglas de divergencia de precios](https://help.vtex.com/es/tutorial/configuracion-de-regla-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) y establecer parámetros para autorizar automáticamente los pedidos con esta diferencia de precio entre seller y marketplace. Al crear reglas automáticas para aprobar o rechazar pedidos con divergencias de precios, la tienda evita tener que procesar manualmente cada ítem, logrando así una operación más eficiente. |
+
+Más información en [Configuraciones generales de los pedidos](https://help.vtex.com/es/tutorial/configuraciones-generales--tutorials_194).
+
+## Checkout
+
+El checkout es la etapa final en el proceso de compras online y contribuye de manera significativa para una buena tasa de conversión de ventas. En el contexto de la plataforma VTEX, el módulo [Checkout](https://help.vtex.com/es/tutorial/checkout-vtex-vista-general--7wcprkM7yZUflOqbzAN5SI) desempeña algunas funciones esenciales:
+
+* Informar sobre el precio y la disponibilidad de los productos en la vitrina.
+* Agregar ítems y procesar el carrito.
+* Completar el proceso de finalización de compra. 
+
+### Antes de comenzar en Checkout
+
+Para garantizar el correcto funcionamiento del checkout, los siguientes módulos deben ser debidamente configurados en la tienda: [Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), [Logística](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx), [Precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP#), [Promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#), [Pagos](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#) y [Pedidos](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE).
+
+![checkout-es](//images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/2c7ccff2d662fb9bff20c549819f1576/checkout_image_ES.jpg)
+
+Este intercambio de información permite procesar datos sobre disponibilidad, precios, promociones aplicables, métodos de envío y medios de pago.
+
+### Personalizar el checkout de la tienda
+
+Las personalizaciones que se describen a continuación son opcionales y tienen por objeto mejorar el desempeño del checkout. Antes de proceder con la configuración, se sugiere realizar un análisis para identificar los módulos aplicables al perfil operacional de la tienda.
+
+- [Optimización de opciones de entrega en el checkout](#optimizacion-de-opciones-de-entrega-en-el-checkout)
+- [Carrito abandonado](#carrito-abandonado)
+- [Modificar el precio de un ítem en el carrito](#modificar-el-precio-de-un-item-en-el-carrito)
+- [Valor mínimo por pedido y cantidad máxima de ítems por SKU](#valor-minimo-por-pedido-y-cantidad-maxima-de-items-por-sku)
+- [Geolocalización en el checkout](#geolocalizacion-en-el-checkout )
+- [Checkout UI Custom app](#checkout-ui-custom-app)
+
+### Optimización de opciones de entrega en el checkout
+
+Una solución que permite activar una combinación de información registrada para mostrar al cliente la opción más rápida y barata del envío de los productos seleccionados en el carrito. Las opciones alternativas (aquellas de mayor costo o con un tiempo de envío más prolongado) no se visualizan en el checkout, proporcionando así una mejor experiencia para el cliente.
+
+Más información en [Optimización de opciones de entrega en el checkout](https://help.vtex.com/es/tutorial/optimizacion-de-opciones-de-entrega-en-checkout--6DeGO9eBSFWe4XkoS0SxAB).
+
+### Carrito abandonado 
+
+Funcionalidad que permite enviar emails a los clientes como recordatorio de un carrito que crearon previamente, pero no se completó la compra.
+
+<div class="alert alert-warning">
+Configurar el carrito abandonado durante el onboarding permite que todos los carritos que se creen se envíen nuevamente al cliente, brindándole la oportunidad de evaluarlos y completar la compra.
+</div>
+
+Más información en [Configurar carrito abandonado](https://help.vtex.com/es/tutorial/configurar-carrito-abandonado--tutorials_740).
+
+### Modificar el precio de un ítem en el carrito
+
+En la plataforma VTEX, las tiendas tienen la opción de ajustar manualmente el precio de un ítem (SKU) en el carrito de checkout. Esta funcionalidad puede utilizarse para aplicar descuentos especiales, corregir errores de precios, crear ofertas personalizadas, resolver reclamaciones relacionadas con precios o ajustar el costo de envío.
+
+<div class="alert alert-warning">
+Solo usuarios con <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> y permisos debidamente registrados en el VTEX Admin pueden realizar este cambio.
+</div>
+
+Más información en [Cambiar el precio de un ítem en el carrito de compras](https://help.vtex.com/es/tutorial/cambiar-el-precio-de-un-item-en-el-carrito-de-compras--7Cd37aCAmtL1qmoZJJvjNf).
+
+### Valor mínimo por pedido y cantidad máxima de ítems por SKU
+
+En las operaciones de ecommerce, los costos logísticos asociados al envío de los productos desempeñan un papel importante en el mantenimiento de la competitividad. Estos costes se ven afectados por el valor total del carrito y la cantidad de unidades del mismo SKU que dicho carrito contiene.
+
+La implementación de un valor mínimo del pedido puede mejorar la eficiencia de los sellers que realizan entregas por lotes, evitando pedidos de poco valor o con pocos ítems, que pueden resultar económicamente inviables.
+
+Más información en [Cómo configurar el valor mínimo por pedido y la cantidad máxima de ítems por SKU](https://help.vtex.com/es/tutorial/como-configurar-el-valor-minimo-por-pedido-y-la-cantidad-maxima-de-items-por--7JqipPUBxtKz0m4OlAyKs9).
+
+### Geolocalización en el checkout 
+
+La solución de geolocalización permite a los clientes utilizar Google Maps en la pantalla del checkout de la tienda para definir una ubicación de entrega, en lugar de utilizar el código postal de la dirección. Una vez indicado el punto de entrega, se mostrará el valor del envío del pedido según el valor introducido por el retailer para entregas en la región seleccionada en el mapa (polígonos de coordenadas).
+
+Además de calcular automáticamente el costo del envío, si la tienda ofrece la opción de recogida en tienda, la geolocalización puede ayudar a los clientes a encontrar la tienda más cercana en función de su ubicación actual.
+
+Más información en [Configurar geolocalización en el checkout](https://help.vtex.com/es/tutorial/geolocalizacion-en-el-checkout--tutorials_4345).
+
+### Checkout UI Custom app
+
+Esta aplicación permite aplicar diferentes personalizaciones visuales a la pantalla del checkout de la tienda. 
+
+Más información en [Checkout UI Custom](https://developers.vtex.com/docs/apps/vtex.checkout-ui-custom).
diff --git a/docs/tracks/es/vtex-support.md b/docs/tracks/es/vtex-support.md
new file mode 100644
index 000000000..defb3e8be
--- /dev/null
+++ b/docs/tracks/es/vtex-support.md
@@ -0,0 +1,33 @@
+---
+title: 'Soporte VTEX'
+id: 7w7cUmbrdPEKpTMItjXEB8
+status: PUBLISHED
+createdAt: 2023-12-19T12:23:03.789Z
+updatedAt: 2024-05-23T17:44:36.531Z
+publishedAt: 2024-05-23T17:44:36.531Z
+firstPublishedAt: 2024-02-22T14:09:33.306Z
+contentType: trackArticle
+productTeam: Billing
+slug: soporte-vtex
+locale: es
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugES: soporte-en-vtex
+---
+
+Cuando clientes y partners necesitan soporte, pueden contar con la asistencia de VTEX, que incluye nuestros portales de documentación, VTEX Community y nuestro soporte online, como se muestra en la siguiente tabla:
+
+| **Canal**  | **Descripción**   |
+|------------|-------------------|
+| [Help Center](https://help.vtex.com/es/)      | Portal de documentación dirigido a retailers, equipos de soporte y responsables de toma de decisiones de negocios que trabajan con el Admin VTEX, el dashboard administrativo de la plataforma. |
+| [Developer Portal](https://developers.vtex.com/) | Portal de documentación dirigido a desarrolladores y usuarios técnicos que trabajan con la plataforma VTEX.                                                                                     |
+| [VTEX Community](https://community.vtex.com/)   | La comunidad oficial de VTEX. Donde podrás encontrar soluciones a tus dudas, compartir ideas y crear conexiones en el ecosistema VTEX.                                                          |
+| [Soporte VTEX](https://help.vtex.com/es/faq/como-funciona-el-soporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe?&utm_source=autocomplete)     | Soporte oficial de VTEX, donde actúan virtualmente especialistas dispuestos a ayudar a resolver problemas de soporte que necesitan el uso de datos privados. [técnico](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#tecnico), [financiero](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#financiero) o [comercial](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#comercial).                                           |
+
+Esta serie está dedicada a la presentación del soporte virtual proporcionado por VTEX y se estructura de la siguiente manera:
+
+- [Funcionamiento del soporte VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3)
+- [Apertura de tickets](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE)
+- [Soporte técnico](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T)
+- [Soporte financiero](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl)
+- [Soporte comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ)
+- [Rescisión de contrato](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3TUpFItxp8L1WZAD1JuYfF)
diff --git a/docs/tracks/es/what-are-clustered-payment-conditions.md b/docs/tracks/es/what-are-clustered-payment-conditions.md
index b15c6277c..218ce8960 100644
--- a/docs/tracks/es/what-are-clustered-payment-conditions.md
+++ b/docs/tracks/es/what-are-clustered-payment-conditions.md
@@ -3,8 +3,8 @@ title: '¿Qué son las Condiciones de Pago Clusterizadas?'
 id: 4z2upCJ2om27Cs0BVJRA0U
 status: PUBLISHED
 createdAt: 2020-11-18T11:49:06.387Z
-updatedAt: 2022-02-07T13:17:58.519Z
-publishedAt: 2022-02-07T13:17:58.519Z
+updatedAt: 2024-05-07T19:41:05.528Z
+publishedAt: 2024-05-07T19:41:05.528Z
 firstPublishedAt: 2020-11-18T17:37:30.544Z
 contentType: trackArticle
 productTeam: Financial
@@ -21,5 +21,3 @@ Esta funcionalidad se encuentra actualmente en Beta Cerrada (etapa de prueba) y
 </div>
 
 Esta personalización ocurre por medio de nuestro banco de datos, el [Master Data](https://help.vtex.com/es/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw "Master Data").
-
-A continuación, explicaremos todas las etapas necesarias para que usted pueda usar esta funcionalidad en la operación de su tienda.
diff --git a/docs/tracks/es/what-is-a-logistics-route.md b/docs/tracks/es/what-is-a-logistics-route.md
index b125fed47..391c714dd 100644
--- a/docs/tracks/es/what-is-a-logistics-route.md
+++ b/docs/tracks/es/what-is-a-logistics-route.md
@@ -33,5 +33,5 @@ Para registrar un muelle en el admin de la tienda, siga los pasos indicados en e
 ### Transportadora
 Es a partir de aquí que los pedidos se distribuyen a sus destinos finales. Una transportadora está compuesta por la flota de vehículos que realizarán las entregas. Por lo tanto, los pedidos salen  del centro de distribución directo a la transportadora que completa el proceso hasta el cliente final.
 
-![ES Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
+![ES Conceitos Logística](//images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
 
diff --git a/docs/tracks/es/what-is-conversational-commerce-vtex.md b/docs/tracks/es/what-is-conversational-commerce-vtex.md
index 9230878e9..8f91a3650 100644
--- a/docs/tracks/es/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/es/what-is-conversational-commerce-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Qué es el comercio conversacional de VTEX?'
 id: 1NwwADrU70v3roPUV7dWxI
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T14:47:50.242Z
-updatedAt: 2023-04-18T15:02:45.235Z
-publishedAt: 2023-04-18T15:02:45.235Z
+updatedAt: 2024-01-05T17:13:58.076Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:46:55.444Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/es/what-is-instore.md b/docs/tracks/es/what-is-instore.md
index fc0ad73a6..34d32093f 100644
--- a/docs/tracks/es/what-is-instore.md
+++ b/docs/tracks/es/what-is-instore.md
@@ -3,8 +3,8 @@ title: '¿Qué es VTEX Sales App?'
 id: 7fnnVlG3Kv1Tay9iagc5yf
 status: PUBLISHED
 createdAt: 2020-06-28T13:07:24.773Z
-updatedAt: 2023-05-31T15:45:55.825Z
-publishedAt: 2023-05-31T15:45:55.825Z
+updatedAt: 2024-05-13T18:03:19.146Z
+publishedAt: 2024-05-13T18:03:19.146Z
 firstPublishedAt: 2020-06-28T13:12:31.221Z
 contentType: trackArticle
 productTeam: Shopping
@@ -24,19 +24,12 @@ Con esto, usted será capaz de implementar una estrategia de pasillo infinito, q
 
 - Evitar la falta de stock y nunca perder una venta.
 - Tener visibilidad en tiempo real de su stock.
-- Beneficiarse de una búsqueda inteligente y consulta de ítems.
+- Beneficiarse de una búsqueda inteligente y consulta de ítems, cuando se instala la Búsqueda [Inteligente Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)en el sitio web.
 - Crear transacciones de carrito mixto.
 
-En cuanto al fulfillment de su operación, VTEX Sales App lo ayudará a:
-
-- Atraer mayor tráfico de clientes y aumentar sus ventas.
-- Tener un flujo eficiente en la preparación de pedidos.
-- Garantizar que sus productos estén siempre disponibles, con opciones de envío más inteligentes.
-- Reducir el tiempo de fulfillment y el costo con Smart Routing.
-
 Por último, con VTEX Sales App, el proceso de compra se hace más rápido, tanto al añadir productos al carrito como durante el pago y la confirmación.
 
-El proceso de checkout ya no necesita hacerse en un mostrador fijo. Se puede comenzar y terminar la venta en cualquier lugar de la tienda, lo que reduce las colas y hace que la experiencia del cliente sea más ágil.
+El proceso de pago ya no necesita realizarse desde un lugar físico y fijo. Se puede comenzar y terminar la venta en cualquier lugar de la tienda, lo que reduce las colas y hace que la experiencia del cliente sea más ágil.
 
 Sus vendedores tendrán una visión de 360º del consumidor y podrán crear experiencias de compra memorables y sin fricciones.
 
diff --git a/docs/tracks/es/what-is-the-master-user.md b/docs/tracks/es/what-is-the-master-user.md
index a9a4d59e6..460ee9021 100644
--- a/docs/tracks/es/what-is-the-master-user.md
+++ b/docs/tracks/es/what-is-the-master-user.md
@@ -26,7 +26,7 @@ Si su usuario tiene perfil de acceso al módulo Gestión de la cuenta, usted pue
 
 Al hacer clic en el nombre de la cuenta deseada, el nombre y el correo electrónico del usuario Titular se encuentran en la sección __Contacto__.
 
-![usuario-master-contato es](https://images.ctfassets.net/alneenqid6w5/2lYlZR55HqYSk4aoGMCCI6/eea8b18ab53d475f046820db05eb717c/contato_usuario_master_es.png)
+![usuario-master-contato es](//images.ctfassets.net/alneenqid6w5/2lYlZR55HqYSk4aoGMCCI6/eea8b18ab53d475f046820db05eb717c/contato_usuario_master_es.png)
 
 Entre las acciones que sólo el usuario Titular puede tomar, están:
 - Reindexar el catálogo.
diff --git a/docs/tracks/es/what-is-vtex-payment.md b/docs/tracks/es/what-is-vtex-payment.md
index 4caf76c79..264cf30e6 100644
--- a/docs/tracks/es/what-is-vtex-payment.md
+++ b/docs/tracks/es/what-is-vtex-payment.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Que és VTEX Payment?'
 id: 1lZWKCGdy7xpYjukTLfFJL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T17:29:51.035Z
-updatedAt: 2023-03-14T22:08:12.345Z
-publishedAt: 2023-03-14T22:08:12.345Z
+updatedAt: 2023-10-05T14:12:50.764Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:47:57.806Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md b/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md
index 1d767de7e..6102e00b3 100644
--- a/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md
+++ b/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md
@@ -3,8 +3,8 @@ title: ' Qué configurar en Wish antes de iniciar la integración'
 id: 4mIn8NE9McE9BxKsAf9IcB
 status: PUBLISHED
 createdAt: 2019-11-13T16:43:49.316Z
-updatedAt: 2020-02-13T15:01:13.402Z
-publishedAt: 2020-02-13T15:01:13.402Z
+updatedAt: 2023-09-22T20:08:35.507Z
+publishedAt: 2023-09-22T20:08:35.507Z
 firstPublishedAt: 2019-11-19T17:27:37.060Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/es/whatsapp-integration.md b/docs/tracks/es/whatsapp-integration.md
index 0d15c516a..7d8b4994c 100644
--- a/docs/tracks/es/whatsapp-integration.md
+++ b/docs/tracks/es/whatsapp-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integración con WhatsApp'
 id: 33sM0SVrwffWhAhAgiGrZb
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T15:11:28.551Z
-updatedAt: 2023-04-25T20:26:48.598Z
-publishedAt: 2023-04-25T20:26:48.598Z
+updatedAt: 2024-01-05T17:14:09.083Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:47:05.529Z
 contentType: trackArticle
 productTeam: Shopping
@@ -45,7 +45,7 @@ Además de enviar esta información, el administrador debe autorizar los siguien
 También recomendamos [verificar tu tienda con Meta](https://www.facebook.com/business/help/1095661473946872?id=180505742745347). Esta etapa es opcional para la integración, pero es obligatoria si:
 
 * Deseas iniciar conversaciones, como avisar a los clientes del seguimiento de sus productos a través de WhatsApp.
-* Deseas que tu cuenta comercial sea [oficial](https://developers.facebook.com/micro_site/url/?click_from_context_menu=true&country=BR&destination=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation%23official-business-account&event_type=click&last_nav_impression_id=0txQ0CoZfJfxi7cez&max_percent_page_viewed=44&max_viewport_height_px=869&max_viewport_width_px=1794&orig_http_referrer=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation&orig_request_uri=https%3A%2F%2Fdevelopers.facebook.com%2Fajax%2Fdocs%2Fnav%2F%3Ftranslation%26path1%3Dwhatsapp%26path2%3Doverview%26path3%3Dbusiness-accounts&region=latam&scrolled=true&session_id=2nAsnwfEzmFrzLZoM&site=developers), es decir, que permita mostrar el nombre de tu tienda en vez del número de teléfono en la lista junto con el sello <img src="https://images.ctfassets.net/alneenqid6w5/4DNjQiVYTI24Wjt3t9CRfG/8e1ec0ab6bb167b4ff0de2547243354f/101835379_284952909300321_643050663994982400_n.png" alt="selo oficial whatsapp" width="25"/>.
+* Deseas que tu cuenta comercial sea [oficial](https://developers.facebook.com/micro_site/url/?click_from_context_menu=true&country=BR&destination=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation%23official-business-account&event_type=click&last_nav_impression_id=0txQ0CoZfJfxi7cez&max_percent_page_viewed=44&max_viewport_height_px=869&max_viewport_width_px=1794&orig_http_referrer=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation&orig_request_uri=https%3A%2F%2Fdevelopers.facebook.com%2Fajax%2Fdocs%2Fnav%2F%3Ftranslation%26path1%3Dwhatsapp%26path2%3Doverview%26path3%3Dbusiness-accounts&region=latam&scrolled=true&session_id=2nAsnwfEzmFrzLZoM&site=developers), es decir, que permita mostrar el nombre de tu tienda en vez del número de teléfono en la lista junto con el sello <img src="//images.ctfassets.net/alneenqid6w5/4DNjQiVYTI24Wjt3t9CRfG/8e1ec0ab6bb167b4ff0de2547243354f/101835379_284952909300321_643050663994982400_n.png" alt="selo oficial whatsapp" width="25"/>.
 
 ## Creación por parte del cliente en el Admin VTEX
 
@@ -62,17 +62,17 @@ Una vez instalada la aplicación, VTEX compartirá la URL del Admin de VTEX Conv
 Con esta información, sigue los pasos a continuación.
 
 1. Accede al VTEX Admin a través de la URL que te ha enviado el equipo de soporte. Verás la siguiente pantalla:
-![Track 101 - Conversational Commerce 1 - PT](https://images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 1 - PT](//images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
 2. Haz clic en el botón `Configurar la cuenta de WhatsApp Business`.
 3. Se abrirá una ventana de Facebook para la configuración. Inicia sesión con el perfil de administrador deseado de Business Manager.
 4. Selecciona la opción `Crear una cuenta de WhatsApp Business`.
 5. Introduce el nombre de la cuenta que se mostrará como nombre de perfil en WhatsApp.
 6. Selecciona la categoría y introduce la descripción de la cuenta. 
-![Track 101 - Conversational Commerce 2 - PT](https://images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 2 - PT](//images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
 7. Verifica el número de teléfono que se asociará a la cuenta mediante el código enviado al teléfono.
 8. Comunica al equipo de soporte de VTEX para que finalice la configuración.
 
 Una vez completada la configuración, se mostrará la alerta de abajo en el Admin. 
 
-![Track 101 - Conversational Commerce 3 - PT](https://images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 3 - PT](//images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
 
diff --git a/docs/tracks/pt/access-to-the-customers-last-cart.md b/docs/tracks/pt/access-to-the-customers-last-cart.md
index 94892caa5..ccc545504 100644
--- a/docs/tracks/pt/access-to-the-customers-last-cart.md
+++ b/docs/tracks/pt/access-to-the-customers-last-cart.md
@@ -20,4 +20,4 @@ Ao ter acesso a essa informação, o vendedor pode tentar concluir a venda dos i
 
 Basta clicar em `Acessar` para ver os produtos do carrinho abandonado.
 
-![last-cart-pt](https://images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/2cccf8f174d42a76d25c0811782dc79e/last-cart-PT.png)
+![last-cart-pt](//images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/2cccf8f174d42a76d25c0811782dc79e/last-cart-PT.png)
diff --git a/docs/tracks/pt/accounts-and-architecture.md b/docs/tracks/pt/accounts-and-architecture.md
new file mode 100644
index 000000000..0b6e31d66
--- /dev/null
+++ b/docs/tracks/pt/accounts-and-architecture.md
@@ -0,0 +1,122 @@
+---
+title: 'Contas e arquitetura'
+id: 4yPqZQyj0t675QpcG7H6yl
+status: PUBLISHED
+createdAt: 2024-01-09T00:00:08.724Z
+updatedAt: 2024-02-22T17:18:14.922Z
+publishedAt: 2024-02-22T17:18:14.922Z
+firstPublishedAt: 2024-02-22T14:06:20.581Z
+contentType: trackArticle
+productTeam: Others
+slug: contas-e-arquitetura
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+A VTEX oferece inúmeras funcionalidades e produtos, mas sua disponibilidade pode variar dependendo do [tipo de conta](#tipos-de-conta-na-vtex), pois cada uma delas foi criada para determinados cenários. Antes de começar a planejar a [arquitetura da loja](#arquitetura-da-loja) e definir [parceiros de implementação](#parceiros-de-implementacao), é preciso conhecer as principais características das contas.
+
+## Tipos de conta na VTEX
+
+A definição da arquitetura de uma loja VTEX está atrelada ao tipo de conta na VTEX, pois algumas funcionalidades são exclusivas ao alguns tipos de conta, sendo que cada conta se adequa a determinados modelos de negócio. A melhor conta será a que melhor reflete a estrutura desse modelo de negócio.
+Os tipos de conta que existem na VTEX são:
+
+- **Conta principal (ou padrão):** é a conta central na VTEX, que permite montar o site da loja, dispor de todas as configurações nativas e contratar tudo o que a plataforma tem a oferecer.
+- [Conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl): é uma conta vinculada à conta principal, não possui site próprio e sua característica mais marcante é não configurar catálogo próprio, e sim recebê-lo da conta principal. Esse tipo de conta é recomendada para operações com lojas físicas, franqueados e representantes da marca, mas a loja não precisa necessariamente ter uma rede de franqueados para se beneficiar dos recursos de uma conta franquia na VTEX.
+- [Conta Seller Portal](https://help.vtex.com/pt/tutorial/seller-criar-conta-no-seller-portal--3gn2Q5rMhgu0jjX7AiiHcs): é uma conta vinculada a uma conta principal, não possui site próprio e sua característica principal é tornar a loja um marketplace para [sellers white label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) ou sellers fora do ecossistema VTEX, que podem rapidamente ativar o próprio catálogo no marketplace VTEX. Ou seja, é uma edição da plataforma VTEX direcionada aos sellers da conta principal.  
+
+A imagem a seguir é uma visão geral para auxiliar a [escolher entre contas padrão, franquia ou Seller Portal](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78):
+
+![main_account_franchise_seller_portal_PT](//images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/dc7b2ca283b2613838a840589bf3b9d3/main_account_franchise_seller_portal_PT.png)
+
+## Recursos das contas
+
+Existem vários fatores para [escolher entre conta padrão, conta franquia ou Seller Portal](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78), a tabela a seguir apresenta os principais recursos de cada uma:
+
+| **Tipo de conta** | **Principais características** |
+| :---: | :--- |
+| Conta principal (ou padrão) | <ul><li>Tem frontend e site próprio.</li><li>Pode se tornar <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multiloja">multiloja</a> e possuir múltiplos sites e lojas, cada um com política comercial própria.</li><li>Tem ambiente próprio no Admin VTEX para gerir sua operação.</li><li>Pode ter contas franquia e Seller Portal, e <a href="https://help.vtex.com/pt/tutorial/contratar-novo-ambiente--tutorials_2542">contratar novos ambientes</a>.</li><li>Permite se tornar um <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex">seller VTEX</a> e um <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex">marketplace VTEX</a> de forma nativa e se conectar com todas as lojas do ecossistema VTEX.</li><li>Pode configurar <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">sellers white label</a> em contas franquias.</li><li>Pode, de forma nativa, vender o inventário de suas contas franquia em outros marketplaces VTEX por meio da funcionalidade <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a>.</li><li>Pode integrar com <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">sellers externos</a> e marketplaces externos.</li><li>Pode contratar produtos add on.</li></ul> |
+| Conta franquia | <ul><li>Não tem frontend e site próprio.</li><li>Possui ambiente próprio no Admin VTEX para gerir a operação.</li><li>Não possui <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo">catálogo</a> próprio, e sim reflete a exata estrutura de catálogo da conta principal.</li><li>Pode configurar <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos">preços e promoções</a>.</li><li>Tem estoque e inventário próprios.</li><li>O inventário da conta franquia pode ser vendido em outros marketplaces VTEX conectados à conta principal, por meio da <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a>.</li></ul> |
+| Conta Seller Portal | <ul><li>Não tem frontend e site próprio.</li><li>A conta principal tem uma área para <a href="https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv">gerenciar os sellers</a> e cada seller tem um ambiente próprio separado no Admin do Seller Portal.</li><li>O seller pode configurar estoque e preço, gerenciar produtos compartilhados com o marketplace, faturar pedidos, ativar promoções, processar pagamentos e ter logística própria.</li></ul> |
+
+<div class="alert alert-info">
+<b>Marketplace na VTEX</b><p>Além de oferecer grande versatilidade na arquitetura da loja, nosso ecossistema possibilita a cada loja ter uma série de <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">estratégias de marketplace</a>, tais como:</p><p><ul><li>Tornar-se seller ou marketplace de outras lojas VTEX.</li><li>Integrar com os grandes players do mercado, como o <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre</a> e a <a href="https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP">Amazon</a>.</li><li>Integrar com os <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros">marketplaces parceiros</a> certificados pela VTEX.</li><li>Ser marketplace para sellers com conta <a href="https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK">Seller Portal</a>.</li><li>Ser <a href="https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>.</li><li>Criar integrações próprias com <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">marketplaces e sellers externos</a>.</li></ul></p>
+</div>
+
+## Arquitetura da loja
+
+A plataforma VTEX oferece a diversos modelos e tamanhos de negócio todas as funcionalidades e configurações necessárias para suas operações. Uma loja pode, por exemplo, ter uma estratégia diferente em cada canal de venda por meio de [políticas comerciais](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz#politica-comercial), configurando catálogo, preço e logística diferente para cada canal. Para isso, basta [contratar novas políticas comerciais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X).
+
+No entanto, o uso simultâneo de muitas políticas comerciais pode comprometer a performance da loja e torná-la lenta, pois alterações precisam ser atualizadas em múltiplas políticas. Portanto, a depender do modelo de negócio e complexidade da operação, é possível segmentar usando as seguintes opções:  
+
+- [Multilojas](#multiloja)
+- [Ambientes adicionais](#ambiente-adicional)
+
+A imagem a seguir é um exemplo de como conta principal, ambiente (subconta), multilojas (lojas) e políticas comerciais estão relacionados:
+
+![multistore_aditional_environment_PT](//images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/c91d697c801dd5fb42e7186e697b2abb/multistore_aditional_environment_PT.png)
+
+### Multiloja
+
+[Multiloja ou multidomínio](https://help.vtex.com/pt/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL) é a funcionalidade que permite criar outras lojas associadas à conta principal, sendo que todas são gerenciadas no mesmo ambiente administrativo. Isso significa que cada loja vai ter seu próprio [storefront](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) e domínio, mas elas podem compartilhar configurações de módulos, como catálogo, logística, preços, entre outros.  
+
+Entre as principais vantagens de [criar multilojas](https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510) estão a facilidade para a empresa comercializar produtos com nichos diferentes, a praticidade na venda de múltiplas marcas e a agilidade em disponibilizar diversos produtos em diferentes lojas e canais.  
+
+Os cenários a seguir são exemplos de quando ter múltiplas lojas associadas ao mesmo ambiente é estratégico:  
+
+- **Loja nacional e internacional:** existe uma loja voltada para o país de origem da operação e outra para mercado internacional.
+- **Segmentação por nicho:** empresas com amplo nicho de atuação, com lojas distintas segmentadas pela oferta de produtos de tipos diferentes focados em públicos distintos.
+- **Operações distintas:** quando um negócio tem tanto atuação B2C quanto B2B, por exemplo, pode ser estratégico ter lojas separadas para cada tipo de operação, mas compartilhando muitas configurações e informações, portanto manter uma administração central é oportuno.  
+
+Além da combinação entre políticas comerciais e multilojas, na VTEX, é possível contratar um novo ambiente, como será visto a seguir.  
+
+### Ambiente adicional
+
+Uma conta padrão na VTEX pode separar inteiramente o espaço de gestão de suas operações, bastando para isso [contratar um novo ambiente](https://help.vtex.com/pt/tutorial/contratar-novo-ambiente--tutorials_2542). Isso significa que cada Admin VTEX estará associado a uma conta própria e vai dispor de forma independente das configurações de storefront e módulos da plataforma.
+
+Alguns casos de uso comuns para contratar um novo ambiente são quando se deseja ter um [ambiente exclusivo para testes](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH#4-testes-antes-do-go-live) (_Quality Assurance_ - QA), ou se deseja um ambiente inteiramente separado para gerir uma outra operação, como B2C, B2B ou B2E.
+
+## Escolhendo entre multiloja e ambiente adicional
+
+A tabela a seguir apresenta aspectos importantes para considerar na hora de decidir sobre ter uma arquitetura multiloja, ambiente adicional ou uma combinação de ambos:  
+
+| **Aspecto** | **Multiloja (lojas)** | **Ambiente adicional (subcontas)** |
+| :---: | :--- | :--- |
+| Arquitetura | Um **único ambiente administrativo** no Admin VTEX associado a duas ou mais lojas ([store names](https://help.vtex.com/pt/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)). Todas as lojas estão vinculadas ao **mesmo [account name](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC)**. | **Múltiplos ambientes administrativos** no Admin VTEX com configurações inteiramente independentes. Cada ambiente possui **[account name](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) próprio**. |
+| Sitemap | Tem um único **[sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) da conta principal compartilhado** entre todas as lojas. | Cada conta tem **[sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) próprio**. |
+| Segmentação nas vendas | As lojas podem **segmentar experiências de compra usando políticas comerciais**. Isso também ajuda a manter a performance de cada loja, pois não é necessário estar com múltiplas políticas comerciais ativas. | As possibilidades de segmentação e personalização de vendas são imensas, pois cada ambiente pode **combinar várias políticas comerciais e multilojas**. |
+| Tipo de equipe | Uma **mesma equipe gerencia** a operação ou, apesar de equipes diferentes, a similaridade de configurações entre lojas torna mais eficiente que elas compartilhem configurações de catálogo, logística e preço, por exemplo. Todos os usuários são **gerenciados pelo mesmo [License Manager](https://help.vtex.com/pt/tutorial/visao-geral-do-modulo-license-manager)**. | Tipos de **equipes distintas** na mesma empresa são responsáveis por operações diferentes. **Cada ambiente tem o seu License Manager**, então os [usuários](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) de cada ambiente são gerenciados separadamente. |
+| Custos | **Não existe um custo** na criação de novas lojas, mas para criar storefronts diferentes, é necessário [contratar uma política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), o que tem um custo. | **Existe um custo** para [contratar um ambiente adicional](https://help.vtex.com/pt/tutorial/contratar-novo-ambiente--tutorials_2542), mas isso já inclui uma política comercial. |
+
+Para obter mais informações, basta acessar o artigo [Escolhendo entre arquitetura multiloja ou ambiente adicional](https://help.vtex.com/pt/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL).  
+
+## Questionário sobre arquitetura
+
+Para auxiliar decisões sobre quais produtos e configurações incluir no planejamento da arquitetura da loja, criamos uma série de perguntas, como pode ser visto na tabela a seguir:
+
+| **Tema** | **Perguntas** |
+| :---: | :--- |
+| Mapeamento de arquitetura existente | - Já existem [integrações externas](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) que devam ser consideradas? Por exemplo: <br><br>- Enterprise Resource Planning (ERP) <br><br>- Customer Relationship Management (CRM) <br><br>- Transportation Management System (TMS) <br><br>- Warehouse Management System (WMS) <br><br>- Business Intelligence (BI) <br><br>- Integrações externas vão se conectar diretamente com a plataforma usando as [APIs da VTEX](https://developers.vtex.com/docs/api-reference)? <br><br>- Será necessário contratar um [parceiro integrador](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao) para fazer uma integração de back office? |
+| Formas de montar a loja | - A implementação será feita usando APIs da [API Reference da VTEX](https://developers.vtex.com/docs/api-reference)? <br><br>- A implementação será feita via Admin VTEX? <br><br>- O modelo é do tipo Headless commerce que vai usar tecnologias de [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) no cenário headless? |
+| Estrutura geral de [backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) e [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) | - Será necessário um parceiro para implementar o [backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) da loja? <br><br>- Será necessário um parceiro para implementar o [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) da loja? <br><br>- O frontend da loja será criado com alguma das [tecnologias da VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#tecnologias-de-desenvolvimento-de-frontend-na-vtex)? ([Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) e [FastStore](https://vtex.com/br-pt/resources/faststore-acelerando-a-cultura-composable-commerce-de-desenvolvimento-headless-avanti/)) <br><br>- O Content Management System (CMS) [Storefront](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC) no Admin VTEX será utilizado nas operações da loja? <br><br>- O modelo de [autenticação na VTEX](https://developers.vtex.com/docs/guides/authentication) poderia gerar algum atrito nas integrações com a plataforma VTEX? |
+| Estrutura geral na VTEX | - Será necessário ter [contas franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl)? <br><br>- Será importante ter [sellers white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa)? <br><br>- Vale se alavancar usando [Multilevel Omnichannel Inventory (MOI)](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4)? <br><br>- Será necessário ter contas [Seller Portal](https://help.vtex.com/pt/tutorial/seller-criar-conta-no-seller-portal--3gn2Q5rMhgu0jjX7AiiHcs)? <br><br>- Será necessário contratar um [ambiente adicional](https://help.vtex.com/pt/tutorial/contratar-novo-ambiente--tutorials_2542)? <br><br>- A operação envolve [multiloja/multidomínio](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitetura-da-loja)? <br><br>- Se sim, vale contratar uma [política comercial adicional](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#contratar-politica-comercial-adicional)? <br><br>- É desejável dispor da solução nativa para integrar com [sellers VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) e [marketplaces VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex)? <br><br>- É desejável integrar com [sellers externos](https://developers.vtex.com/docs/guides/external-seller-integration-guide) e [marketplaces externos](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide)? <br><br>- Quais questões de [otimização de performance](https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance) devem ser consideradas em desenvolvimento em [Store Framework](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework)? <br><br>- Quais questões de internacionalização devem ser consideradas em desenvolvimento em Store Framework? <br><br>- A operação é internacional e precisa [gerenciar conteúdo por binding](https://help.vtex.com/pt/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) para personalizar a aparência da sua loja de acordo com a localização dos usuários? |
+| Tipo de indústria  | - Qual é o tipo de indústria da operação? <br><br>- Está relacionado à [moda](https://vtex.com/br-pt/moda-e-vestuario/) (roupas e vestuário)? <br><br>- Está relacionado a [supermercado](https://vtex.com/br-pt/supermercado/)? |
+| Caso de uso | - O modelo de negócio envolve [comércio B2C](https://vtex.com/br-pt/digital-commerce/) ou [comércio B2B](https://help.vtex.com/pt/tutorial/setting-up-b2b-on-vtex--tutorials_238)? <br><br>- É necessário ter uma [solução omnichannel](https://vtex.com/br-pt/omnichannel/)? |
+| [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) |  - Como será a [arquitetura do catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) de produtos? <br><br>- A configuração de catálogo será feita por [integração backoffice](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#arquitetura-do-catalogo)? <br><br>- A importação de produtos será feita por [integração backoffice](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#importar-produtos)? <br><br>- Será necessário [internacionalizar o catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization)? |
+| [Buscas no site da loja](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) | - É necessário instalar e configurar o [VTEX Intelligent Search](https://developers.vtex.com/docs/apps/vtex.search), para os clientes terem busca inteligente e função autocomplete no site da loja? <br><br>- A operação funciona em diversos países e precisa oferecer aos clientes experiências de [pesquisa em múltiplos idiomas](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO)? <br><br>- A loja deseja que os resultados das buscas ordenem os produtos de acordo com alguma [regra de merchandising específica](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW)? <br><br>- É desejável configurar o Region para ter a [regionalização de sellers](https://help.vtex.com/pt/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw)? |
+| [Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos) e [Promoções](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promocoes) | - Considerando a [arquitetura do sistema de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) na VTEX, quais serão os tipos de preço cadastrados? <br><br>- A configuração de preços dos produtos será feita por [integração backoffice](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu)? <br><br>- A estratégia de venda envolve o uso de [tabelas de preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8)? <br><br>- Será desejável [criar promoções](https://help.vtex.com/pt/tutorial/lista-de-promocoes-beta--4yB7nNdliiFxBTXE19GCIi)? |
+| [Pagamentos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagamentos) | - Qual gateway ou grupo de gateways serão contatados para, em seguida, [cadastrar as afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444) na plataforma? <br><br>- Quais [configurações de pagamento](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) (crédito, dinheiro, etc.) serão necessárias para as [condições de pagamento](https://help.vtex.com/pt/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) oferecidas aos clientes no checkout? <br><br>- É desejável configurar [split de pagamentos](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) para sellers e marketplaces? |
+| [Logística e fulfillment](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) | - Como será organizada a [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)? <br><br>- Quais serão as [docas](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)? Quais serão os [estoques](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)? <br><br>- Quais serão as [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)? <br><br>- Quais serão as [transportadoras](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) nas [planilhas de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) configuradas nas políticas de envio? <br><br>- Será necessário configurar [pontos de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) para os clientes poderem retirar pedidos em lojas físicas ou centros de distribuição? <br><br>- No [gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139), seria interessante usar o [lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B), uma configuração opcional de tempo de envio a nível de SKU? <br><br>- A importação de inventário será feita por [integração backoffice](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#inventario)? <br><br>- É desejável ativar o [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) para a operação se integrar pelo Admin VTEX com os serviços PAC e SEDEX dos Correios? (Somente Brasil) <br><br>- A operação envolve lojas internacionais e venda [cross-border](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs)? |
+| [Pedidos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos) | - É desejável configurar [Feed ou Hook](https://developers.vtex.com/docs/guides/orders-feed) para acompanhar mudanças de [status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196)? <br><br>- Será necessária uma [integração backoffice](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-integration) para enviar informações de pedidos da VTEX para sistemas externos como ERP ou WMS, ou para enviar informações de pedidos de sistemas externos para a VTEX? |
+| [Checkout](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout) | - A loja vai utilizar o [Checkout da VTEX](https://help.vtex.com/pt/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) ou uma solução de terceiros? <br><br>- É desejável [configurar preço e disponibilidade de SKUs regionalmente](https://help.vtex.com/pt/tutorial/setting-up-price-and-availability-of-skus-by-region--12ne58BmvYsYuGsimmugoc), de forma que o cliente, em sua experiência de compra, veja primeiro os itens da loja que estão disponíveis em estoque e que podem ser entregues na sua localização? |
+
+## Parceiros de implementação
+
+É comum a criação de uma loja contar com a participação de agências e [parceiros de implementação](https://vtex.com/br-pt/partner/) (System Integration Partners). A VTEX está associada a um vasto ecossistema de parceiros que foram reconhecidos por sua excelência e confiabilidade na criação de projetos de lojas VTEX. Desde que o [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) tenha uma permissão de acesso ao Admin VTEX de uma loja, é possível consultar a lista desses parceiros pelo [Partner Portal](https://partnerportal.vtex.com/) (somente português).
+
+O [Quadrante VTEX](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) é um programa em que a VTEX avalia internamente a performance e os resultados de sucesso da operação dos seus parceiros. Esta é uma forma de reconhecer e premiar anualmente aqueles que apresentam o maior nível de entrega e excelência. Veja [aqui](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) o resultado do Quadrante de 2023.
+
+<div class="alert alert-info">
+O <a href="https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/">Quadrante VTEX</a> é um programa exclusivo para parceiros de implementação do Brasil.
+</div>
+
diff --git a/docs/tracks/pt/ad-types-classic-and-premium.md b/docs/tracks/pt/ad-types-classic-and-premium.md
index 2d16d983b..1bb63dd20 100644
--- a/docs/tracks/pt/ad-types-classic-and-premium.md
+++ b/docs/tracks/pt/ad-types-classic-and-premium.md
@@ -20,9 +20,9 @@ Anúncios do tipo Clássico têm como principal vantagem uma menor tarifa por ve
 
 Na integração com a VTEX, você pode optar por anunciar seus produtos em ambos formatos. Cada tipo de anúncio deve ser configurado separadamente, seguindo todos os passos indicados neste tutorial.
 
-<img style="width:48%;" src="https:https://images.ctfassets.net/alneenqid6w5/65sXxgN6qA2i0faa1i3UqZ/db79bd4140d93a987ff0a9fa6e013aa6/mercadolivre-classic-pt.png"/>
+<img style="width:48%;" src="https://images.ctfassets.net/alneenqid6w5/65sXxgN6qA2i0faa1i3UqZ/db79bd4140d93a987ff0a9fa6e013aa6/mercadolivre-classic-pt.png"/>
 <span style="width:4%;"/>
-<img style="width:48%;" src="https:https://images.ctfassets.net/alneenqid6w5/2m56Xo8kVHJD8gQZZHTAKt/7cbfdb8a46cec1d825381c592783f053/mercadolivre-premium-pt.png"/>
+<img style="width:48%;" src="https://images.ctfassets.net/alneenqid6w5/2m56Xo8kVHJD8gQZZHTAKt/7cbfdb8a46cec1d825381c592783f053/mercadolivre-premium-pt.png"/>
 
 #### Mais detalhes sobre os tipos de anúncios
 
diff --git a/docs/tracks/pt/add-on-products.md b/docs/tracks/pt/add-on-products.md
new file mode 100644
index 000000000..7f7fd11b4
--- /dev/null
+++ b/docs/tracks/pt/add-on-products.md
@@ -0,0 +1,128 @@
+---
+title: 'Produtos Add-on'
+id: 1t2QBZvrOBSLgvHaAV9fYm
+status: PUBLISHED
+createdAt: 2024-02-20T20:29:42.983Z
+updatedAt: 2024-07-03T11:38:12.320Z
+publishedAt: 2024-07-03T11:38:12.320Z
+firstPublishedAt: 2024-02-22T14:09:28.506Z
+contentType: trackArticle
+productTeam: Others
+slug: produtos-add-on
+locale: pt
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugPT: proximos-passos-apos-o-go-live
+---
+
+Produtos Add-on são soluções oferecidas pela VTEX para atender demandas específicas de um negócio e que podem ser adquiridas separadamente por meio de um contrato de assinatura.
+
+<div class="alert alert-warning">
+  <p>Para implementar as soluções abaixo, é necessário entrar em contato com o nosso <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial VTEX</a>.</p> 
+</div>
+
+## VTEX Ad Network
+
+O [VTEX Ad Network](https://help.vtex.com/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) conecta lojas VTEX a marcas interessadas em anunciar seus produtos. Com esta conexão, anunciantes e lojas VTEX podem potencializar seu negócio:
+
+- **Anunciantes:** marcas, que podem criar campanhas de anúncios para promover seus produtos nas frentes de lojas VTEX que possuem aqueles produtos em seus catálogos, aumentando suas vendas.
+- **Lojas VTEX:** podem disponibilizar espaço publicitário para que marcas promovam seus produtos na sua frente de loja. Estas lojas receberão um valor por cada clique recebido em anúncios na sua loja.
+
+![vtex_ad_network_sponsored_PT](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
+
+## VTEX Assisted Sales
+
+[Assisted Sales (SuiteShare)](https://help.vtex.com/pt/tracks/suiteshare--khP0p8mjIYRIpvM7Cb4Zr/onWmyS8j4Thhde67UBBsB) é a solução criada pela VTEX para impulsionamento de vendas no WhatsApp. Por meio dela, é possível atrair novos clientes, integrar ferramentas de vendas, gerenciar dados de atendimento do usuário e métricas de resultados.
+
+![suitshare-pt](//images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/23ef16a09a1c9b86b743059ba4c364ef/next_steps_image11_ONLYPT.JPG)
+
+## VTEX Live Shopping
+Solução que permite a criação de transmissões online para a realização de demonstrações ao vivo das características dos produtos na loja. Interações diretas e instantâneas com os clientes permitem melhorar o engajamento do público com a marca e contribuem para aumentar a performance de venda.
+
+![live-shopping-pt](//images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/aa4276798ea8f4a5edc2b61cab366154/next_steps_image5_ALL.JPG)
+
+Para agendar uma demonstração do aplicativo com um especialista, é preciso acessar a página sobre [VTEX Live Shopping](https://vtex.com/br-pt/live-shopping/#contact).
+
+## VTEX Personal Shopper
+
+Solução que permite o atendimento personalizado direto entre o cliente e o vendedor, trazendo a experiência de compra da loja física para o ambiente digital. Por meio deste aplicativo, o vendedor tem a possibilidade demonstrar produtos, fazer recomendações e esclarecer dúvidas dos clientes. Durante a videochamada, também é possível adicionar itens no carrinho de compras.
+
+![personal-shopper-pt](//images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/0853e4731a4f6b688fe214bde2f88d70/next_steps_image6_ALL.JPG)
+
+## VTEX Pick and Pack
+
+Solução para gestão e visibilidade completa do processo de fulfillment, desde a separação e embalagem dos produtos nas lojas físicas ou depósitos, até a entrega em pontos de retirada ou local do cliente.
+
+O **VTEX Pick and Pack** é composto por: 
+
+- [Pick and Pack app](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA): gerencia pedidos na loja ou depósito, permitindo personalizar o método de separação de pedidos, selecionar tipos de embalagens por produto, remover ou adicionar produtos de acordo com o estoque da loja.
+- [Last Mile app](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): coordena o envio de pacotes a partir de depósitos ou lojas até os endereços, criando rotas inteligentes de entrega, selecionando motoristas disponíveis, e rastreando a localização exata do pedido.
+
+![pick-and-pack-pt](//images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/61b013dcf10e9427d68f42b909ba0c23/next_steps_image7_ALL.JPG)
+
+Para assistir uma demonstração do aplicativo ou agendar o atendimento personalizado com um especialista, é preciso acessar a página sobre [VTEX Pick and Pack](https://content.vtex.com/pt-br/pick-and-pack/). 
+
+## VTEX Sales App
+
+Com o [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), os vendedores de lojas físicas podem expandir suas possibilidades de vendas por meio da integração de dados de estoque entre lojas físicas e virtuais, enquanto oferecem um acompanhamento completo presencial do processo de compra ao cliente. Por meio deste app, é possível:
+
+- Acessar informações e realizar vendas de produtos que estejam presentes em sua própria loja e em diferentes locais, tais como, lojas filiais, parceiras ou centros de distribuição ([prateleira infinita](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn)).
+- Sugerir produtos de acordo com o perfil do cliente.
+- Oferecer opções de entrega instantânea, retirada agendada ou no local do cliente.
+- Gerenciar métricas de performance para cada vendedor.
+
+![sales-app-pt](//images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/e5e9b59e94c59f05ffb9cead6d2f7d93/image3.png)
+
+Para assistir uma demonstração do aplicativo ou agendar o atendimento personalizado com um especialista, é preciso acessar a página sobre [VTEX Sales App](https://assets.vtex.com/sales-app/).
+
+## VTEX Shipping Network
+
+Explore opções de envio de produtos para todas as regiões do Brasil com o [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) e **VTEX Shipping Network Correios**.
+
+O **VTEX Shipping Network** proporciona a possibilidade de conectar transportadoras para criar uma rede integrada de entrega, atualmente com mais de 20 parceiros, para oferecer as melhores opções de custo e prazo aos clientes. 
+
+![shipping-network-pt](//images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/573663b07a3ec62b235be4037b75b93e/image7.png)
+
+Para mais informações, é preciso acessar a página sobre [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/).
+
+<div class="alert alert-warning">
+  <p>As soluções <strong>VTEX Shipping Network</strong> e <strong>VTEX Shipping Network Correios</strong> são exclusivas para operações no Brasil.</p>
+</div>
+
+## VTEX Shipping Network Correios
+
+O [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) é uma parceria entre a VTEX e os Correios na qual a loja pode contratar serviços de envio de produtos via PAC e SEDEX diretamente no Admin VTEX, com taxas diferenciadas que reduzem os custos operacionais de frete.
+
+![image6](//images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/4a83e3f251f45e5bae81f44cc35d6d4d/image6.png)
+
+A contratação dessa solução pode ser realizada de maneira simples e em poucos minutos, por meio da aceitação dos Termos e Condições e a [ativação](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) no próprio Admin da loja. As seguintes funcionalidades estão presentes no VTEX Shipping Network Correios: 
+
+- Sincronia de Tabelas de fretes entre os Correios e a VTEX. Cada informação atualizada pelos Correios é mostrada automaticamente no ambiente VTEX
+- Rastreios de entregas inseridos e atualizados de forma automática nos pedidos
+- Etiquetas de envio disponíveis para serem impressas direto no Admin VTEX (módulo [Pronto para Envio](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs)) ou via [API](https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration), para integração com sistemas externos (ex. ERP, WMS)
+- Canal de comunicação direta com os Correios dentro do Admin por meio do [Pedido de informações](https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq#solicitar-informacoes-do-pedido-aos-correios)
+
+Para mais informações, é preciso acessar a página sobre [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/#).
+
+## VTEX Shield
+
+O [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) oferece camadas adicionais e personalizáveis de proteção para lojas que priorizam a resiliência da plataforma, além dos padrões de segurança garantidos pelas [certificações e práticas de segurança](https://vtex.com/br-pt/security/security-practices/) existentes na VTEX.
+
+Ao contratar o VTEX Shield, é possível optar pelas funcionalidades a seguir:
+
+* [Security Monitor](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#security-monitor)
+* [Testes de penetração](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#testes-de-penetracao)
+* [Web Application Firewall (WAF)](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh#web-application-firewall-waf)
+
+## VTEX WhatsApp AI Campaigns
+
+O [WhatsApp AI Campaigns](https://help.vtex.com/pt/tutorial/recupere-checkouts-abandonados-com-whatsapp-ai-campaigns--20i0zLQHt72LKzVEmk1CRZ?&utm_source=autocomplete), é uma funcionalidade desenvolvida pela VTEX, para recuperar checkouts abandonados.
+
+Quando um usuário abandona a página de pagamento de compras, a plataforma identifica essa ação. Se o usuário não retornar para concluir a compra no período de 1 hora, a funcionalidade envia uma mensagem de lembrete ao usuário por meio do WhatsApp.
+
+Os principais benefícios dessa funcionalidade são:
+- **Melhoria na experiência do cliente:** É possível personalizar mensagens para aumentar a relevância e fortalecer a relação com a marca.
+- **Aumento nas taxas de conversão e vendas:** incentiva que os clientes retornem à página de pagamento para finalizar sua compra, aumentando desta forma as vendas e taxas de conversão para lojistas.
+
+<div class = "alert alert-info">
+O WhatsApp AI Campaigns está disponível  apenas para lojas que utilizam <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> que não tenham customizações no Checkout.
+</div>
diff --git a/docs/tracks/pt/add-pickup-points.md b/docs/tracks/pt/add-pickup-points.md
index 988336237..44fd45005 100644
--- a/docs/tracks/pt/add-pickup-points.md
+++ b/docs/tracks/pt/add-pickup-points.md
@@ -29,7 +29,7 @@ Siga o passo a passo abaixo para cadastrar um ponto de retirada na sua loja:
 4. Preencha os campos do formulário de ponto de retirada. Para entender melhor o significado de cada campo, consulte a seção [Campos de cadastro](#campos-de-cadastro), abaixo.
 5. Clique no botão **Save Changes** 
 
-![PT Cadastrar Pontos de Retirada GIF](https://images.ctfassets.net/alneenqid6w5/7m2LOZGJLly2gdprwvU7Gt/06d1113db5efc6d6fc35c26daa9fabf4/PT_Cadastrar_Pontos_de_Retirada_GIF.gif)
+![PT Cadastrar Pontos de Retirada GIF](//images.ctfassets.net/alneenqid6w5/7m2LOZGJLly2gdprwvU7Gt/06d1113db5efc6d6fc35c26daa9fabf4/PT_Cadastrar_Pontos_de_Retirada_GIF.gif)
 
 ### Campos de cadastro
 
diff --git a/docs/tracks/pt/add-sku-specifications.md b/docs/tracks/pt/add-sku-specifications.md
index 1edd1dda6..ac0a56c09 100644
--- a/docs/tracks/pt/add-sku-specifications.md
+++ b/docs/tracks/pt/add-sku-specifications.md
@@ -35,7 +35,7 @@ Para cadastrar as especificações sua loja precisa ter departamentos, categoria
  7. Preencha os campos do formulário de especificações. No caso dos SKUs,  a flag de campo obrigatório sempre está selecionada por default. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher campos de especificações de SKU](https://help.vtex.com/pt/tutorial/criando-campo-de-sku--tutorials_119)
  8.  Clique em **Salvar**
 
-![1.PT](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/fa7b4836240b18cd3d941f6260b512b8/1.PT.gif)
+![1.PT](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/fa7b4836240b18cd3d941f6260b512b8/1.PT.gif)
 
 Para adicionar valores à especificação de SKU, siga os passos abaixo:
 
@@ -49,7 +49,7 @@ Para adicionar valores à especificação de SKU, siga os passos abaixo:
  8. Clique em **Novo Valor**
  9. Escreva o **Nome** do valor desejado e clique em **Salvar**
 
-![2.PT](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/8f8ee16b8a59dd7be5e5b77f358fba0c/2.PT.gif)
+![2.PT](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/8f8ee16b8a59dd7be5e5b77f358fba0c/2.PT.gif)
 
 ### Vincular as especificações a um SKU
 
@@ -65,7 +65,7 @@ Para incluir as especificações em um **SKU** siga os seguintes passos:
  6. Clique na aba **Especificações** e escolha o valor da especificação para esse SKU
  7. Clique em **Salvar**
 
-![3.PT](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/f1a986c79116835f7abb23853b51278e/3.PT.gif)
+![3.PT](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/f1a986c79116835f7abb23853b51278e/3.PT.gif)
 
 ## Planilha 
 
@@ -94,7 +94,7 @@ Depois de preencher os dados da planilha, siga o passo a passo para Importar sua
 5. Clique em **Select** para selecionar a planilha preenchida
 6.  Clique em **Importar**
 
-![4.PT](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/39b16e05c0e7f952fed25892902da30e/4.PT.gif)
+![4.PT](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/39b16e05c0e7f952fed25892902da30e/4.PT.gif)
 
 ## API 
 
diff --git a/docs/tracks/pt/adding-a-fixed-price.md b/docs/tracks/pt/adding-a-fixed-price.md
index 4c97b4ccd..10ea0eaba 100644
--- a/docs/tracks/pt/adding-a-fixed-price.md
+++ b/docs/tracks/pt/adding-a-fixed-price.md
@@ -1,10 +1,10 @@
 ---
 title: 'Cadastrar preço fixo'
 id: 3g39iXkQza4AW7C7L814mj
-status: CHANGED
+status: PUBLISHED
 createdAt: 2019-07-04T13:53:38.630Z
-updatedAt: 2023-03-29T21:16:34.391Z
-publishedAt: 2023-03-29T18:18:57.294Z
+updatedAt: 2024-05-15T16:01:59.100Z
+publishedAt: 2024-05-15T16:01:59.100Z
 firstPublishedAt: 2019-07-17T19:46:38.452Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -54,7 +54,7 @@ Para excluir um preço fixo existente, siga os passos abaixo.
 
 ## Pricing API
 
-Para cadastrar um preço fixo por API, use o endpoint [Create or update base or fixed prices](https://developers.vtex.com/vtex-rest-api/reference/prices-and-fixed-prices#createupdatepriceorfixedprice) da Pricing API.
+Para cadastrar um preço fixo por API, use o endpoint [Create or update base or fixed prices](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-) da Pricing API.
 
 ### Saiba mais
 
diff --git a/docs/tracks/pt/adding-a-loading-dock.md b/docs/tracks/pt/adding-a-loading-dock.md
index f7a07823d..009cd1e3a 100644
--- a/docs/tracks/pt/adding-a-loading-dock.md
+++ b/docs/tracks/pt/adding-a-loading-dock.md
@@ -28,7 +28,7 @@ Siga o passo a passo abaixo para cadastrar uma Doca na sua loja:
 4.  Preencha os campos do formulário de cadastro. Para entender melhor o significado de cada campo, veja abaixo a seção [Campos de Cadastro](#campos-de-cadastro).
 5.  Clique no botão  **Salvar**.
 
-![PT Cadastrar Doca GIF](https://images.ctfassets.net/alneenqid6w5/4GWA3i4x5LSitJRR2nPSF/518140a1c67b5382bcd2042148f2b05c/PT_Cadastrar_Doca.gif)
+![PT Cadastrar Doca GIF](//images.ctfassets.net/alneenqid6w5/4GWA3i4x5LSitJRR2nPSF/518140a1c67b5382bcd2042148f2b05c/PT_Cadastrar_Doca.gif)
 
 ### Campos de cadastro
 
diff --git a/docs/tracks/pt/adding-a-price-rule.md b/docs/tracks/pt/adding-a-price-rule.md
index a0571df94..4193667a3 100644
--- a/docs/tracks/pt/adding-a-price-rule.md
+++ b/docs/tracks/pt/adding-a-price-rule.md
@@ -3,8 +3,8 @@ title: 'Cadastrar regra de preço'
 id: 7fyZaYe1IGzL0qVC28tOBO
 status: PUBLISHED
 createdAt: 2019-07-04T13:53:15.461Z
-updatedAt: 2023-03-29T18:50:59.023Z
-publishedAt: 2023-03-29T18:50:59.023Z
+updatedAt: 2023-08-21T17:10:07.115Z
+publishedAt: 2023-08-21T17:10:07.115Z
 firstPublishedAt: 2019-07-17T19:42:10.960Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Siga o passo a passo abaixo para cadastrar a regra de preço da sua loja:
 
 ## Admin
 
-1.  No Admin VTEX, acesse *Preços > Regras de preços*, ou digite *Regras de preços* na barra de busca no topo da página.
+1.  No Admin VTEX, acesse **Preços > Regras de preços**, ou digite **Regras de preços** na barra de busca no topo da página.
 2.  Clique no botão verde **Nova Regra**.
 3.  No primeiro passo, **Quais os dados gerais dessa regra?**, selecione no *dropdown* uma tabela de preços.
 4.  No segundo passo, **Em quais itens esta regra será aplicada?**, selecione se a regra irá se *Aplicar em todos os produtos* ou *Apenas em categorias e marcas escolhidas*. Se selecionada a segunda opção, você deve escolher as **Categorias** e/ou **Marcas** desejadas. 
diff --git a/docs/tracks/pt/adding-extra-text-to-the-order-print.md b/docs/tracks/pt/adding-extra-text-to-the-order-print.md
index 1c4e32f99..77a43ac08 100644
--- a/docs/tracks/pt/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/pt/adding-extra-text-to-the-order-print.md
@@ -38,7 +38,7 @@ Após recarregar o inStore, sempre que um vendedor imprimir um pedido, esse text
 
 Antes de adicionar texto extra, a impressão do resumo do pedido tem o seguinte formato:
 
-![28. Adding extra text to the order print - 1](https://images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
+![28. Adding extra text to the order print - 1](//images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
 
 Em nosso exemplo, alteramos o arquivo `checkout-instore-custom.js` inserindo o seguinte texto extra:
 
@@ -50,4 +50,4 @@ window.INSTORE_CONFIG = {
 
 Agora, quando sempre que um resumo de pedido for impresso, teremos o seguinte resultado:
 
-![28. Adding extra text to the order print - 2](https://images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
+![28. Adding extra text to the order print - 2](//images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
diff --git a/docs/tracks/pt/adding-new-stores-to-instore.md b/docs/tracks/pt/adding-new-stores-to-instore.md
index 3b5525ae9..cb502f869 100644
--- a/docs/tracks/pt/adding-new-stores-to-instore.md
+++ b/docs/tracks/pt/adding-new-stores-to-instore.md
@@ -3,8 +3,8 @@ title: 'Gerenciar lojas físicas no VTEX Sales App'
 id: 5PSjRstg7UU4lOm0s8aqKN
 status: PUBLISHED
 createdAt: 2020-06-29T13:30:51.354Z
-updatedAt: 2023-05-31T15:07:31.507Z
-publishedAt: 2023-05-31T15:07:31.507Z
+updatedAt: 2023-07-26T18:59:24.074Z
+publishedAt: 2023-07-26T18:59:24.074Z
 firstPublishedAt: 2020-06-29T14:22:11.121Z
 contentType: trackArticle
 productTeam: Shopping
@@ -25,7 +25,7 @@ Esta página permite que você realize as seguintes ações:
 * [Editar](#editar-loja-fisica)
 * [Inativar](#inativar-loja-fisica)
 
-![loja-fisica-PT](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
+![loja-fisica-PT](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
 
 A página apresenta as seguintes informações: 
 
@@ -51,7 +51,7 @@ Você pode cadastrar uma loja física seguindo os passos a seguir:
 
 ### Campos de cadastro da loja física
 
-![loja-fisica2-pt](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
+![loja-fisica2-pt](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
 
 #### Identificação
 
diff --git a/docs/tracks/pt/adding-product-specifications.md b/docs/tracks/pt/adding-product-specifications.md
index c8c74d624..5948914e6 100644
--- a/docs/tracks/pt/adding-product-specifications.md
+++ b/docs/tracks/pt/adding-product-specifications.md
@@ -35,7 +35,7 @@ Para cadastrar as especificações sua loja precisa ter departamentos, categoria
  7. Preencha os campos do formulário de especificações. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher campos de especificações de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).
  8.  Clique em **Salvar**.
 
-![1.PT](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/309fc619d5f3fa5dfc472ea31336b646/1.PT.gif)
+![1.PT](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/309fc619d5f3fa5dfc472ea31336b646/1.PT.gif)
 
 Para adicionar valores à especificação de um produto, siga os passos abaixo:
 
@@ -49,7 +49,7 @@ Para adicionar valores à especificação de um produto, siga os passos abaixo:
  9. Clique em **Novo Valor**.
  10. Escreva o **Nome** do valor desejado e clique em **Salvar**.
 
-![2.PT](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/38de1f08c0bab9de62b6003688e678e5/2.PT.gif)
+![2.PT](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/38de1f08c0bab9de62b6003688e678e5/2.PT.gif)
 
 ### Vincular as especificações a um produto
 
@@ -63,7 +63,7 @@ Para incluir as especificações em um **Produto** siga os seguintes passos:
  4. Clique na aba **Especificações** e escolha o valor da especificação para esse produto.
  5. Clique na aba **Produto** e depois clique em **Salvar**.
 
-![3.PT](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/e884dd25a34b8dc9ffeade1e8dc9b9bd/3.PT.gif)
+![3.PT](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/e884dd25a34b8dc9ffeade1e8dc9b9bd/3.PT.gif)
 
 ## Planilha 
 
@@ -92,7 +92,7 @@ Depois de preencher os dados da planilha, siga o passo a passo para Importar sua
 5. Clique em **Select** para selecionar a planilha de Importação.
 6.  Clique em **Importar**.
 
-![4.PT](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/33cb6da8c5fc3f57f84e9559e4a9867a/4.PT.gif)
+![4.PT](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/33cb6da8c5fc3f57f84e9559e4a9867a/4.PT.gif)
 
 ## API 
 
diff --git a/docs/tracks/pt/adding-products.md b/docs/tracks/pt/adding-products.md
index 6c66f941a..5bc77e9f3 100644
--- a/docs/tracks/pt/adding-products.md
+++ b/docs/tracks/pt/adding-products.md
@@ -30,7 +30,7 @@ No Admin VTEX, siga os passos abaixo.
 4. Preencha os campos do formulário de produto. Para entender melhor o significado de cada campo, acesse nosso artigo sobre os [campos de cadastro de produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke).
 5. Clique em `Salvar` ou `Salvar e Cadastrar novo SKU`, caso queira adicionar SKUs associados a esse produto.
 
-![Catalogo - Cadastrar produto PT](https://images.ctfassets.net/alneenqid6w5/bdIAqfM86PlhwB3and8rX/48c5f7c1aa60306d9bdc114e1464c0aa/Catalogo_-_Cadastrar_produto_PT.gif)
+![Catalogo - Cadastrar produto PT](//images.ctfassets.net/alneenqid6w5/bdIAqfM86PlhwB3and8rX/48c5f7c1aa60306d9bdc114e1464c0aa/Catalogo_-_Cadastrar_produto_PT.gif)
 
 ## Planilha
 
diff --git a/docs/tracks/pt/adding-skus.md b/docs/tracks/pt/adding-skus.md
index 7ca83fac7..62b25577e 100644
--- a/docs/tracks/pt/adding-skus.md
+++ b/docs/tracks/pt/adding-skus.md
@@ -25,7 +25,7 @@ Existem dois fluxos de cadastro de SKU pelo Admin VTEX: criar um SKU logo após
 ### Cadastrar SKU logo após o cadastro de um produto
 
 1. Na tela de cadastro de Produto, após preencher os campos, clique em `Salvar e Cadastrar novo SKU`.
-  ![foto1.pt](https://images.ctfassets.net/alneenqid6w5/4hbOFLl4i0ItEagHpb0SQD/49b2bd614f938aef01f48444c07843f3/foto1.pt.png)
+  ![foto1.pt](//images.ctfassets.net/alneenqid6w5/4hbOFLl4i0ItEagHpb0SQD/49b2bd614f938aef01f48444c07843f3/foto1.pt.png)
 2. Você será redirecionado(a) para a tela de cadastro de SKU. Preencha os campos do formulário de SKU. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher os campos de cadastro de SKU](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) 
 3. Clique em `Salvar`.
 
@@ -43,7 +43,7 @@ Existem dois fluxos de cadastro de SKU pelo Admin VTEX: criar um SKU logo após
 Após o cadastro de um SKU é necessário adicionar uma imagem para torná-lo ativo. Para fazer isso, siga o passo a passo abaixo: 
 
 1. Na página de cadastro do SKU, clique na aba **Imagens**.
-![foto6.pt](https://images.ctfassets.net/alneenqid6w5/78tvoRLdoSO4dI8QtDPfuH/f1ba5b1a2cd4b917c4d46df95f44cc1c/foto6.pt.png)
+![foto6.pt](//images.ctfassets.net/alneenqid6w5/78tvoRLdoSO4dI8QtDPfuH/f1ba5b1a2cd4b917c4d46df95f44cc1c/foto6.pt.png)
 2. Clique em `Inserir` e escolha a imagem desejada.
 3. Preencha os campos **Texto** (tag alt da imagem) e **Label** (a “etiqueta” usada para facilitar na organização do template das páginas do seu site, através do referenciamento do valor preenchido nesta. Ex.: Frontal, lateral, superior etc).
 4. Clique em `Enviar`.
@@ -53,7 +53,7 @@ Após o cadastro de um SKU é necessário adicionar uma imagem para torná-lo at
 Após cadastrar as imagens, você deve cadastrar as especificações do SKU. O cadastro das especificações será detalhado no próximo passo dessa trilha.  
 
 1. Clique na aba **Especificações**.
-![foto7.pt](https://images.ctfassets.net/alneenqid6w5/TCWsuTxF97y0yZNLfggIX/f316524c44ec171e226d454d58da321c/foto7.pt.png)
+![foto7.pt](//images.ctfassets.net/alneenqid6w5/TCWsuTxF97y0yZNLfggIX/f316524c44ec171e226d454d58da321c/foto7.pt.png)
 2. Preencha os campos solicitados. Os valores das especificações são configurados no nível da Categoria.
 3. Clique em `Salvar`.
 
diff --git a/docs/tracks/pt/adding-vendors.md b/docs/tracks/pt/adding-vendors.md
index 1ebfb06c5..2902c8c9a 100644
--- a/docs/tracks/pt/adding-vendors.md
+++ b/docs/tracks/pt/adding-vendors.md
@@ -18,7 +18,7 @@ Se você configurou sua loja utilizando o fluxo de __Easy Setup__ talvez já ten
 
 Ao entrar no VTable (https://{{AccountName}}.myvtex.com/admin/vtable) você verá duas aplicações, __Admin das lojas__ e __Admin dos vendedores__:
 
-![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Clique em __Admin dos vendedores__ para abrir a tabela onde incluiremos um novo vendedor.
 
@@ -28,7 +28,7 @@ Caso você já tenha cadastrado um vendedor através do __Easy Setup__, basta cl
 <strong>IMPORTANTE</strong>: o e-mail de cada vendedor <strong>NÃO</strong> pode ser o mesmo utilizado na plataforma VTEX, isso porque o seu e-mail de admin possui permissões que um vendedor não deveria ter, por isso é necessário utilizar algum outro e-mail sem privilégios na plataforma.
 </div>
 
-![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
+![inStore adicionando vendedor](//images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
 Se você pulou a etapa de criação de vendedor no __Easy Setup__ e não tem nenhum vendedor criado, precisará pegar o id da __Loja__ no __Admin das Lojas__ no VTable.
 
diff --git a/docs/tracks/pt/adding-warehouses.md b/docs/tracks/pt/adding-warehouses.md
index c3d27e08b..2c459b057 100644
--- a/docs/tracks/pt/adding-warehouses.md
+++ b/docs/tracks/pt/adding-warehouses.md
@@ -29,7 +29,7 @@ Siga o passo a passo abaixo para cadastrar um estoque na sua loja:
 4. Preencha os campos do formulário de estoque. Para entender melhor o significado de cada campo, veja abaixo a seção [Campos de Cadastro](#campos-de-cadastro).
 5. Clique no botão **Salvar**
 
-![PT Cadastrar Estoque GIF](https://images.ctfassets.net/alneenqid6w5/2z4bJ7wuzd6vePDariRnX8/90c3c2e7fa6e7f00ae360a7fd77f2dbd/PT_Cadastrar_Estoque.gif)
+![PT Cadastrar Estoque GIF](//images.ctfassets.net/alneenqid6w5/2z4bJ7wuzd6vePDariRnX8/90c3c2e7fa6e7f00ae360a7fd77f2dbd/PT_Cadastrar_Estoque.gif)
 
 ### Campos de cadastro
 
diff --git a/docs/tracks/pt/allowing-order-replacement.md b/docs/tracks/pt/allowing-order-replacement.md
index 19cacd31a..6e8451113 100644
--- a/docs/tracks/pt/allowing-order-replacement.md
+++ b/docs/tracks/pt/allowing-order-replacement.md
@@ -3,8 +3,8 @@ title: 'Permitir substituição de pedidos'
 id: 381eYJw7lrypjGq3hmPtGV
 status: PUBLISHED
 createdAt: 2019-11-18T11:57:28.677Z
-updatedAt: 2023-03-31T22:52:53.575Z
-publishedAt: 2023-03-31T22:52:53.575Z
+updatedAt: 2024-04-01T17:58:20.948Z
+publishedAt: 2024-04-01T17:58:20.948Z
 firstPublishedAt: 2019-11-18T12:20:58.872Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -18,6 +18,10 @@ A **Substituição de pedidos** permite aos clientes da sua loja alterar dados d
 
 O objetivo é ajudá-los a corrigir erros sem a necessidade de realizar um novo pedido manualmente ou de entrar em contato com seu suporte, o que facilita a operação da sua loja e reduz custos.
 
+<div class = "alert alert-warning">
+Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
+</div>
+
 ## Como ativar a Substituição de pedidos
 
 A funcionalidade está disponível para todos as lojas. Para ativá-la, siga os passos abaixo:
diff --git a/docs/tracks/pt/amazon-account-settings.md b/docs/tracks/pt/amazon-account-settings.md
index f641b8d51..337225cde 100644
--- a/docs/tracks/pt/amazon-account-settings.md
+++ b/docs/tracks/pt/amazon-account-settings.md
@@ -1,9 +1,9 @@
 ---
 title: 'Configurações de conta na Amazon '
 id: 43L0dpbjLBz6tcim1BbTzf
-status: PUBLISHED
+status: CHANGED
 createdAt: 2019-02-28T23:01:18.628Z
-updatedAt: 2023-03-08T20:38:03.932Z
+updatedAt: 2023-11-09T22:36:18.079Z
 publishedAt: 2023-03-08T20:38:03.932Z
 firstPublishedAt: 2019-02-28T23:02:20.905Z
 contentType: trackArticle
diff --git a/docs/tracks/pt/apple-pay.md b/docs/tracks/pt/apple-pay.md
new file mode 100644
index 000000000..2b8dd8960
--- /dev/null
+++ b/docs/tracks/pt/apple-pay.md
@@ -0,0 +1,53 @@
+---
+title: 'Apple Pay'
+id: STKWiXJSR9ImPt5EEC2aL
+status: PUBLISHED
+createdAt: 2023-06-28T14:04:58.979Z
+updatedAt: 2024-06-25T21:02:43.540Z
+publishedAt: 2024-06-25T21:02:43.540Z
+firstPublishedAt: 2023-06-28T14:13:24.803Z
+contentType: trackArticle
+productTeam: Shopping
+slug: apple-pay
+locale: pt
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugPT: carteira-digital-e-wallet
+---
+
+Seus clientes podem fazer compras usando o Apple Pay, a [carteira digital](https://help.vtex.com/pt/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/7jLbdfch9Oe2yYbQa9zwE1) da Apple. Para isso, você precisa cumprir alguns requisitos:
+
+- Ter uma conta em `developer.apple.com`.
+- Ter contrato com um provedor que processe pagamentos com Apple Pay.
+
+<div class="alert alert-warning">
+  O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse <a href="https://support.apple.com/pt-br/HT208531">Dispositivos compatíveis com o Apple Pay</a>.
+</div>
+
+## Configurar provedor de pagamento
+
+Primeiramente é necessário configurar no Admin de sua loja um provedor que processe transações com o Apple Pay, tais como, [Adyen](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3) e [Stripe](https://help.vtex.com/pt/tutorial/configurar-a-afiliacao-de-gateway-stripe--fwF2wk2FQKrODrWWkvSLO).
+
+Para conferir todas as opções de provedores disponíveis para este meio de pagamento, acesse a lista conforme descrito no Passo 5 da seção [Configurar pagamento com Apple Pay](#configurar-pagamento-com-apple-pay).
+
+<div class="alert alert-warning">
+  Antes de iniciar a configuração do provedor é necessário <a href="registrar o Merchant ID no Apple Pay">registrar o Merchant ID no Apple Pay</a>.
+</div>
+
+## Configurar pagamento com Apple Pay
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
+2. Clique na aba __Condições de pagamento__ e, em seguida, no botão `+`.
+3. Selecione o meio de pagamento __Apple Pay__.
+4. Clique no botão `Status` para ativar essa condição de pagamento.
+5. No campo __Processar com o provedor__, selecione o provedor que será utilizado para processar os pagamentos.
+6. Se houver um antifraude configurado na sua loja, você pode ativá-lo para essa condição de pagamento marcando a caixa __Usar solução antifraude__.
+7. Escolha se deseja que os pagamentos sejam feitos à vista ou parcelados.
+8. Se desejar, você também pode optar por uma [condição especial de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+9. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, Apple Pay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
+
+### Artigos relacionados
+
+- [Configurando Merchant ID no Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay)
+- [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456)
diff --git a/docs/tracks/pt/associating-a-template-with-a-layout.md b/docs/tracks/pt/associating-a-template-with-a-layout.md
index c2beafcfe..00bc88447 100644
--- a/docs/tracks/pt/associating-a-template-with-a-layout.md
+++ b/docs/tracks/pt/associating-a-template-with-a-layout.md
@@ -30,4 +30,4 @@ Essa associação é feita na configuração de propriedades do layout. Para che
 6. Selecione o template que você deseja associar a esse layout.
 7. Digite "yes" para confirmar a mudança. (Este passo é necessário porque esta é uma alteração crítica para o site, já que o front-end da página será substituído.) 
 
-![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tracks/pt/autocomplete-search.md b/docs/tracks/pt/autocomplete-search.md
index f78c35fd9..1a2bbeda9 100644
--- a/docs/tracks/pt/autocomplete-search.md
+++ b/docs/tracks/pt/autocomplete-search.md
@@ -52,22 +52,22 @@ Outra vantagem para o gestor da loja é o aumento de conversão, resultado dessa
 
 Essa seção exibe os termos mais buscados por outros clientes dentro do site.
 
-![PT - Autocomplete termos mais pesquisados](https://images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
 
 ## Últimas buscas efetuadas
 
 Essa seção exibe as últimas buscas efetuadas pelo cliente. Assim, é possível  iniciar a interação com a busca instantaneamente.
 
-![PT - Autocomplete historico](https://images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
 
 ## Sugestão de buscas
 
 Essa seção apresenta os termos pesquisados por outros usuários que se relacionam com a busca efetuada naquele momento. Além de termos, também são sugeridas categorias que estejam relacionadas com a busca.
 
-![PT - Autocomplete sugestao termos](https://images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
 
 ## Sugestão de produtos
 
 Essa seção apresenta os produtos que correspondem a busca efetuada naquele momento. Dessa forma, ao mostrar produtos relacionados a sua busca durante a sua digitação, diminui as desistências e dá a possibilidade do usuário efetuar uma compra mais dinâmica.
 
-![PT - Autocomplete sugestao de produtos](https://images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
+![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tracks/pt/availability.md b/docs/tracks/pt/availability.md
index 7b7aa871d..f97c03af3 100644
--- a/docs/tracks/pt/availability.md
+++ b/docs/tracks/pt/availability.md
@@ -3,8 +3,8 @@ title: 'Disponibilidade'
 id: 7LMQbWK5nElIkXo0NK8Kux
 status: PUBLISHED
 createdAt: 2021-10-04T18:01:24.137Z
-updatedAt: 2021-10-04T18:18:56.501Z
-publishedAt: 2021-10-04T18:18:56.501Z
+updatedAt: 2023-12-07T19:28:15.731Z
+publishedAt: 2023-12-07T19:28:15.731Z
 firstPublishedAt: 2021-10-04T18:18:56.501Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -16,7 +16,8 @@ trackSlugPT: vtex-intelligent-search
 
 Para montar um resultado de busca, o VTEX Intelligent Search considera a disponibilidade de cada produto encontrado na pesquisa. Produtos disponíveis serão sempre priorizados em relação a produtos sem disponibilidade nos resultados de busca. 
 
-Ao verificar a disponibilidade do produto, o VTEX Intelligent Search utiliza o campo **Mostrar produto esgotado** cadastrado no [Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ) para verificar quais produtos serão exibidos mesmo quando indisponíveis. Caso a configuração do produto defina que ele não será exibido se estiver sem estoque, a plataforma o posicionará no final do resultado de busca.  Além da exibição do produto sem estoque, o VTEX Intelligent Search também verifica se:
+Ao verificar a disponibilidade do produto, o VTEX Intelligent Search utiliza o campo **Mostrar produto esgotado** cadastrado no [Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ) para verificar quais produtos serão exibidos mesmo quando indisponíveis. Se a configuração do produto determinar que ele não deve ser exibido quando estiver fora de estoque, a plataforma não apresentará o produto. No entanto, se a configuração indicar que o produto deve ser exibido mesmo quando estiver sem estoque, a plataforma o colocará no final dos resultados de busca.
+Além da exibição do produto sem estoque, o VTEX Intelligent Search também verifica se:
 
 - O produto em questão está ativo.
 - Pelo menos um SKU do produto está ativo.
diff --git a/docs/tracks/pt/b2b-form.md b/docs/tracks/pt/b2b-form.md
index effdfda22..eda7258df 100644
--- a/docs/tracks/pt/b2b-form.md
+++ b/docs/tracks/pt/b2b-form.md
@@ -46,12 +46,12 @@ Exemplos de como fica no inStore o formulário com pessoa jurídica:
 
 __Formulário B2B__ opcional fechado:
 
-![b2b-opcional-fechado](https://images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
+![b2b-opcional-fechado](//images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
 
 __Formulário B2B__ opcional aberto:
 
-![b2b-opcional-aberto](https://images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
+![b2b-opcional-aberto](//images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
 
 __Formulário B2B__ obrigatório (já vem todos os campos abertos):
 
-![b2b-obrigatorio](https://images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
+![b2b-obrigatorio](//images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
diff --git a/docs/tracks/pt/backend-integrations.md b/docs/tracks/pt/backend-integrations.md
new file mode 100644
index 000000000..1c5316108
--- /dev/null
+++ b/docs/tracks/pt/backend-integrations.md
@@ -0,0 +1,406 @@
+---
+title: 'Integrações de backend'
+id: 7euXDZR5CCnVFSrXyczIhu
+status: PUBLISHED
+createdAt: 2024-02-05T13:23:32.848Z
+updatedAt: 2024-02-23T02:06:48.878Z
+publishedAt: 2024-02-23T02:06:48.878Z
+firstPublishedAt: 2024-02-22T14:06:58.203Z
+contentType: trackArticle
+productTeam: Others
+slug: integracoes-de-backend
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+Normalmente, as integrações começam com os softwares de back-office, permitindo o gerenciamento de partes essenciais da operação relacionadas a [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos), [Logística](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica), [Pedidos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#pedidos). Os principais tipos de software presentes no back-office são:
+
+- ERP (Enterprise Resource Planning)
+- WMS (Warehouse Management System)
+- PIM (Product Information Manager)
+- CRM (Customer Relationship Management)
+
+Além do back-office, pode-se integrar a plataforma de comércio eletrônico a outros sistemas que adicionam novos recursos. Um exemplo são os [provedores de pagamento](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagamentos), que permitem a comunicação entre a plataforma VTEX e os provedores para realizar o processamento dos pagamentos e incluir métodos de pagamento adicionais no [Checkout](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout).
+
+## Integração com ERP
+
+A configuração de integração do back-office de uma loja começa pelo software ERP (Enterprise Resource Planning). É possível que outros tipos de software sejam utilizados no back-office para finalidades específicas, como o PIM (Product Information Manager) lidando com dados de produtos, e o WMS (Warehouse Management System) lidando com inventário.
+
+ERPs e outros tipos de softwares podem possuir integrações nativas com a VTEX. Caso não possua, será necessário implementar um middleware próprio utilizando as [APIs da VTEX](https://developers.vtex.com/docs/api-reference) para integrar o software com a conta VTEX.
+
+A configuração tem duas fases: a **configuração inicial** e a **configuração de middleware**. Após esta configuração, estará visível o fluxo em andamento, utilizado para a operação do dia a dia da loja. Veja mais detalhes sobre a configuração no [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide).
+
+### Configuração inicial
+
+Nesta fase são feitos os procedimentos para que a [conta VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-conta-na-vtex) receba todas as informações relacionadas aos produtos. Aqui serão integrados o catálogo, os produtos, os preços e o inventário da loja. Em geral, as configurações desta fase podem ser feita de três formas: 
+
+- Integração com ferramentas externas.
+- Importação de planilhas.
+- Inserção manual pelo Admin VTEX.
+
+Os passos de configuração desta fase devem ser seguidos na ordem apresentada abaixo. Os detalhes sobre cada passo estão descritos nas respectivas subseções da seção [Integrações](#integracoes) deste artigo.
+
+1. [Arquitetura do Catálogo](#arquitetura-do-catalogo)
+
+  a. Árvore de categorias
+
+  b. Marcas
+
+  c. Especificações (grupos e campos)
+
+2. [Importação dos produtos](#importar-produtos)
+
+  a. Importar produtos
+
+  b. Importar especificações dos produtos
+
+  c. Adicionar os produtos à política comercial
+
+  d. Importar SKUs
+
+  e. Importar especificações dos SKUs
+
+  f. Importar imagens dos SKUs
+
+3. [Importação dos preços](#precos)
+
+  a. Definir preço-base
+
+  b. Definir preços fixos para contextos específicos
+
+4. [Importação do inventário](#inventario)
+
+  a. Criar estoques
+
+  b. Atualizar inventário de SKUs
+
+### Configuração de middleware
+
+Nesta fase são feitos os procedimentos para permitir que a loja processe os pedidos. Aqui serão integradas as notificações sobre alterações dos pedidos e as ações para executar o processamento dos pedidos. A integração pode ser realizada de duas formas:
+
+- **Integração de plataformas:** esta opção envolve a utilização de uma plataforma de terceiros, conhecida como Platform-as-a-Service (PaaS), que já oferece uma solução pronta para integrar-se à VTEX, demandando um esforço mínimo de desenvolvimento.
+- **Desenvolvimento interno:** esta opção envolve a construção e manutenção do próprio software de integração. O middleware deve ser capaz de lidar com questões de escalabilidade que podem surgir com picos de vendas, como os que costumam acontecer em eventos de vendas como a Black Friday.
+
+Os passos para esta configuração devem ser seguidos na ordem apresentada abaixo. Os detalhes sobre cada passo estão descritos nas respectivas subseções da seção [Integrações](#integracoes).
+
+1. [Configuração de integração/notificação de pedidos](#integracao-de-pedidos)
+
+  a. Configurar feed ou hook
+
+2. [Configuração de processamento de pedidos](#processamento-de-pedidos)
+
+  a. Alterar pedido
+
+  b. Cancelamento
+
+  c. Faturamento
+
+  d. Rastreamento
+
+### Comportamento da integração com ERP
+
+Após configurar a loja e fazer a integração com middleware, o fluxo geral de informações terá o seguinte formato:
+
+![ERP-integrations-pt](//images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/cfbbd0b541595fd3788d895bbeeef071/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_1.jpg)
+
+Cada uma das requisições ou processos representados pelas setas no diagrama acima é acionada por um tipo diferente de evento na operação do dia a dia de um ecommerce. Para saber mais detalhes sobre esse fluxo, veja o [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide#ongoing-middleware-flow).
+
+## Integrações
+
+Nesta seção, serão abordadas as principais integrações para o funcionamento de uma loja VTEX. Essas integrações abrangem uma ampla gama de aspectos, desde a integração de catálogo e dados de clientes até a gestão de pedidos e autenticação única (SSO). Cada uma dessas integrações será examinada a seguir.
+
+### Arquitetura do Catálogo
+
+Na VTEX, o [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) é o módulo para configurar as características dos produtos da loja de forma a tornar estes produtos disponíveis para os clientes. O Catálogo deve ser criado seguindo a ordem dos passos abaixo:
+
+1. Criação da [árvore de categorias](#arvore-de-categorias).
+2. Cadastro de [Marcas](#marcas).
+3. Cadastro de [Especificações (opcional)](#especificacoes).
+4. Importação de [Produtos](#importar-produtos).
+5. Importação de [SKUs](#importar-produtos).
+6. [Associação de especificações a produtos e SKUs](#importar-produtos).
+
+Mais informações sobre configuração do Catálogo com back-office nos artigos [Catalog](https://developers.vtex.com/docs/guides/catalog-overview) e [Set up catalog](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog).
+
+#### Árvore de categorias
+
+Após compreender e planejar a [Arquitetura do Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#arquitetura-do-catalogo) da loja, a criação das categorias pode ser realizada pelas seguintes formas:
+
+1. __Admin VTEX:__ criar cada categoria usando a interface de usuário. Veja os detalhes em [Cadastrar Categorias](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1).
+2. __API do Catálogo:__ criar cada categoria fazendo chamadas de API. Veja os detalhes na [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category).
+3. __Integração com back-office:__ importar as categorias a partir de um software externo de back-office (ERP ou PIM) integrado à VTEX. O software pode já oferecer integração nativa com a VTEX ou requerer o desenvolvimento de um middleware que utiliza a [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Veja os detalhes em [Migração de Categorias a partir do ERP](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#category-migration-from-erps).
+
+<div class="alert alert-warning">
+Ao importar as categorias de um software externo, a estrutura de categorias no software pode ser diferente da VTEX. Nesse caso, é recomendado criar uma categoria simulada inativa que não será visível no storefront e que pode ser usada para receber todos os produtos e SKUs durante a importação. Após a conclusão da importação, os produtos podem ser arranjados manualmente no Admin VTEX para se adequarem à árvore de categorias desejada.
+</div>
+
+Existem algumas limitações para lidar com categorias, são elas:
+
+- __Mover categorias:__ embora seja possível mover categorias para diferentes níveis (mais alto/mais baixo) e/ou diferentes departamentos, isto é muito arriscado devido às especificações anexadas à categoria. Esta ação pode negativamente afetar informações sobre o produto, já que produtos herdam não apenas as especificações anteriores, mas também as novas.
+- __Apagar categorias:__ não é possível apagar uma categoria a menos que se faça uma [limpeza completa](https://help.vtex.com/pt/tutorial/database-maintenance-full-cleanup--34P9LGs7BCIQK6acQom802) do catálogo da loja.
+
+Mais informações sobre importação para back-office de categorias no artigo [Categories](https://developers.vtex.com/docs/guides/categories).
+
+#### Marcas
+
+[Marcas](https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) são atributos de produtos que ajudam os clientes a identificar o produto e a empresa responsável por ele. Um produto deve estar associado a uma única marca, o que significa que criar marcas é um passo obrigatório na configuração do Catálogo. É possível criar marcas das seguintes formas:
+
+1. __Admin VTEX:__ criar cada marca usando a interface de usuário. Veja os detalhes em [Cadastrar Marcas](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7lEGOSpAlQJCs5eUc5XFmR).
+2. __API do Catálogo:__ criar cada marca fazendo chamadas de API. Veja os detalhes na [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand).
+3. __Integração com back-office:__ importar as marcas a partir de um software externo de back-office (ERP ou PIM) integrado à VTEX. O software pode já oferecer a integração nativa com a VTEX ou pode requerer o desenvolvimento de um middleware que utiliza a [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Veja os detalhes em [Criar Marcas no guia de configuração do Catálogo para back-office](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-brands).
+
+<div class="alert alert-warning">
+Caso o sistema de back-office não possua informação sobre marcas, pode ser feito o mesmo procedimento mencionado acima para migração de categorias, criando uma marca simulada inativa, exclusivamente para fins de migração. Posteriormente, as informações dos produtos podem ser inseridas manualmente.
+</div>
+
+Mais informações sobre importação para back-office de marcas para no artigo [Brands](https://developers.vtex.com/docs/guides/brands).
+
+#### Especificações
+
+[Especificações](https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) são propriedades adicionais que podem ser atribuídas a produtos e SKUs da loja para serem usadas na criação de filtros de busca e para diferenciar SKUs e produtos na página do produto. A criação de especificações pode ser realizada por meio de [integrações de back-office](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-specifications-groups) utilizando a [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview).
+
+Existem três tipos de especificações e elas devem ser criadas na seguinte ordem:
+
+1. Grupos de especificações
+2. Campos de especificação
+3. Valores de especificação
+
+O diagrama abaixo ilustra este procedimento:
+
+![catalog_specification_diagram_PT](//images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/1880753cbe1e9b79f0dae39125a76cb8/catalog_specification_diagram_PT.png)
+
+As especificações seguem a hierarquia do Catálogo. Quando um grupo é criado em um departamento ou categoria, ele será herdado nos níveis abaixo. 
+
+Após criar grupos, campos e valores, deve ser feita a associação de especificações a produtos e SKUs. Estes procedimentos estão descritos na próxima seção, [Importar produtos](#importar-produtos).
+
+Mais informações sobre importação para back-office de especificações no artigo [Specifications](https://developers.vtex.com/docs/guides/specifications).
+
+### Importar produtos
+
+Importar produtos refere-se ao ato de transferir todas as informações relevantes do produto de um sistema ERP ou PIM para a plataforma VTEX. Esta etapa mantém o catálogo de produtos atualizado e sincronizado com a loja. Seja lidando com uma ampla variedade de produtos, SKUs ou variações diferentes, a importação eficaz de produtos é essencial para a experiência do cliente.
+
+Na VTEX, é importante compreender a distinção entre Produtos e SKUs:
+
+- [Produto](https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru): unidade abstrata do catálogo, visível nas prateleiras da loja. 
+- [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA): unidade concreta do catálogo no estoque, representando as variações específicas de um produto, como cor, tamanho e outros atributos. Os SKUs são exibidos como itens individuais em páginas de produtos.
+
+<div class = "alert alert-info">
+A maneira como produtos e SKUs são estruturados tem impacto direto na experiência de compra dos clientes.
+</div>
+
+A importação de produtos segue os passos na ordem da tabela abaixo:
+
+| **Ação** | **Descrição** | **Métodos** |
+| :--- | :--- | :--- |
+| <a href="https://developers.vtex.com/docs/guides/products">1. Importar produtos</a> | Registrar os produtos no catálogo. | <ul><li>Integração pela <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product">API do Catálogo</a></li><li>Importação de planilhas (<a href="https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#spreadsheet">método clássico</a> e <a href="https://developers.vtex.com/docs/apps/vtex.google-drive-import@0.x">app google-drive-import</a>).</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL">Admin VTEX</a>.</li></ul>|
+| <a href="https://developers.vtex.com/docs/guides/product-specifications">2. Importar especificações dos produtos</a> | Preencher as especificações dos produtos no catálogo. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/specification">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106#preencher-especificacoes-de-produto">Admin VTEX</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/erp-integration-import-products#add-product-to-trade-polic">3. Adicionar os produtos à política comercial</a> | Associar os produtos às devidas <a href="https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">políticas comerciais</a>, definindo regras específicas (Preços, Pagamentos, estratégia de envio, etc.) de acordo com o canal de venda ou público. No mínimo, deve-se adicionar todos os produtos à política comercial principal. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/salespolicy/-tradepolicyId-">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL">Admin VTEX ao cadastrar um produto</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/skus">4. Importar SKUs</a> | Adicionar SKUs aos produtos no Catálogo. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#adicionar-novo-sku-a-um-produto-ja-cadastrado">Admin VTEX</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/sku-specifications">5. Importar especificações dos SKUs</a> | Preencher as especificações dos SKUs no Catálogo. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/specification">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119#preencher-especificacoes-de-sku">Admin VTEX</a>.</li></ul> |
+| <a href="https://developers.vtex.com/docs/guides/images">6. Importar imagens dos SKUs</a> | Adicionar imagens aos SKUs. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tutorial/como-atualizar-a-imagem-de-um-sku--5PMb54FnvUuWOq2qGyAosu">Admin VTEX</a>.</li></ul> |
+
+<div class="alert alert-warning">
+É comum que as informações de produtos no ERP não sejam adequadas para uso e exibição em um ecommerce. Por isso, deve ser feito um processo de enriquecimento, que pode incluir a reestruturação de categorias, e a criação de descrições de produtos mais descritivas e cativantes.
+</div>
+
+Após a importação, também é importante garantir que as informações sobre produtos e SKUs se mantenham atualizadas. Veja as instruções no artigo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information).
+
+Mais informações sobre importação para back-office de produtos no artigo [Import products](https://developers.vtex.com/docs/guides/erp-integration-import-products).
+
+### Preços
+
+[Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos) são as informações dos valores de venda dos SKUs, os quais são armazenados em [tabelas de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8). Para garantir que os produtos da loja tenham preços competitivos e adaptados aos diferentes canais de vendas, é necessário compreender como as informações de preços são integradas à VTEX. 
+
+Em operações de venda, é comum delegar o cálculo do preço para o ERP, de onde esses dados podem ser importados. Os preços têm um valor base definido para cada SKU e podem variar de acordo com o contexto. Os passos para realizar a importação de preços são:
+
+1. **Definir preço-base:** o preço-base serve como referência para determinar o preço de um produto no sistema de precificação da VTEX. O preço-base de um SKU pode ser importado por integração utilizando a [API de Preços](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-) ou [criado pelo Admin VTEX](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29#admin).
+2. **Definir preços fixos para contextos específicos:** o preço-base pode ser ajustado ou modificado com base em regras específicas, cálculos ou preços fixos para chegar ao preço final de varejo do SKU em diferentes contextos, a depender da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV), [grupo de clientes](https://help.vtex.com/pt/tutorial/como-criar-um-cluster-de-clientes--frequentlyAskedQuestions_1724), [promoção](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR), entre outros fatores. Os preços fixos para contextos específicos podem ser importados por integração utilizando a [API de Preços](https://developers.vtex.com/docs/api-reference/pricing-api#put-/pricing/prices/-itemId-), [importados por planilha](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#importacao-de-precos) ou [criados pelo Admin VTEX](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj#admin).
+
+Após a importação, também é importante garantir que as informações sobre preços se mantenham atualizadas. Veja as instruções no artigo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information#pricing-updates).
+
+Mais informações sobre importação para back-office de preços no artigo [Import prices](https://developers.vtex.com/docs/guides/erp-integration-import-prices).
+
+### Inventário
+
+No módulo [Logística](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) da VTEX, o [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) é a relação entre os itens de venda de uma loja (SKUs) e os locais onde estes itens estão armazenados, conhecidos como [estoques](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb). Gerenciar com eficiência o inventário de uma loja é uma etapa essencial para importar o inventário para a VTEX e garantir que os clientes possam acessar informações precisas de disponibilidade de produtos, agilizando o processo de [logística e envio](https://help.vtex.com/pt/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP).
+
+Os passos para realizar a importação de inventário são:
+
+1. **Criar estoques:** cadastrar os locais físicos ou virtuais onde os SKUs serão armazenados. Os estoques podem ser importados por integração utilizando a [API de Logística](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) ou [criados pelo Admin VTEX](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#cadastrar-estoque).
+2. **Atualizar inventário de SKUs:** inserir a quantidade disponível de cada item nos estoques. O inventário pode ser importado por integração utilizando a [API de Logística](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-), por [planilha de estoque](https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034) ou [atualizado pelo Admin VTEX](https://help.vtex.com/pt/tutorial/como-atualizar-estoque--2MDwYV1COA6YuoiY22AyGo).
+
+Após a importação, também é importante garantir que as informações sobre preços se mantenham atualizadas. Para conferir as instruções, basta acessar o artigo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information#pricing-updates).
+
+Mais informações sobre importação para back-office de inventário no artigo [Import inventory](https://developers.vtex.com/docs/guides/erp-integration-import-inventory).
+
+### Dados de clientes
+
+A importação de dados de clientes permite integrar informações de clientes de outros sistemas, como aplicações de CRM (Customer Relationship Management), com a VTEX. Por padrão, a VTEX armazena os dados dos clientes no [Master Data V1](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). 
+
+Os dados no Master Data são organizados em [entidades de dados](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-dados), que podem ser comparadas a tabelas em outros sistemas de bancos de dados, contendo [documentos](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#documentos) que se assemelham a linhas ou registros. Os dados de perfil dos clientes são armazenados na entidade `CL` e os endereços dos clientes na entidade `AD`.
+
+Os passos para realizar a importação de dados de clientes são:
+
+1. **Criar novos perfis de clientes:** criar documentos na entidade `CL` contendo os dados de perfil dos clientes, como nome, email, telefone, entre outros. Estes dados podem ser importados por integração utilizando a [API do Master Data](https://developers.vtex.com/docs/api-reference/masterdata-api#post-/api/dataentities/-acronym-/documents).
+2. **Criar endereços:** criar documentos na entidade `AD` contendo os endereços dos clientes, incluindo informações como rua, cidade, código postal, etc. Cada endereço é associado a um cliente, e um cliente pode ter vários endereços associados. Estes dados podem ser importados por integração utilizando a [API do Master Data](https://developers.vtex.com/docs/api-reference/masterdata-api#post-/api/dataentities/-acronym-/documents).
+
+Mais informações sobre importação para back-office de dados de clientes no artigo [Import customer data](https://developers.vtex.com/docs/guides/import-customer-data).
+
+## Integração de pedidos
+
+[Pedidos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos) são gerados na plataforma VTEX assim que um cliente clica no botão de finalizar a compra no checkout. Cada pedido carrega várias informações, incluindo os itens do carrinho, o valor da compra, o método de pagamento, entre outros.
+
+A integração de pedidos permite a comunicação entre a aplicação de back-office, ERP ou WMS, e o OMS (_Order Management System_) da VTEX. Tal integração desempenha um papel fundamental para:
+
+- Lidar com os eventos relacionados às mudanças de [status do pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
+- Obter [detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl).
+- Transmitir as informações relacionadas ao [processamento de pedidos](#processamento-de-pedidos).
+
+#### Receber atualizações de pedidos
+
+Com o back-office recebendo as atualizações dos pedidos, é possível agilizar e automatizar os procedimentos realizados no [processamento de pedidos](#processamento-de-pedidos), como faturamento e cancelamento.
+
+Existem duas formas de rastrear mudanças de status de pedidos na VTEX:
+
+- [Feed v3](https://developers.vtex.com/docs/guides/orders-feed): é uma lista de eventos sobre atualizações de pedidos. Para este tipo de integração, a VTEX fornece um [endpoint](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/orders/feed/config?endpoint=get-/api/orders/feed/config) para que o back-office possa realizar consultas aos itens da lista, processar os pedidos, e em seguida, remover os itens da lista.
+- [Hook](https://developers.vtex.com/docs/guides/orders-feed#hook): é um canal para envio automático de notificações sobre atualizações de pedidos. Para este tipo de integração, a aplicação de back-office fornece um [endpoint](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/orders/hook/config?endpoint=get-/api/orders/hook/config) para que a VTEX o notifique sobre atualizações dos pedidos. Após receber uma notificação, o back-office procede com o processamento do pedido.
+
+Para os dois tipos de integração, é possível aplicar [filtros](https://developers.vtex.com/docs/guides/orders-feed#filter) para selecionar os tipos de evento que devem ser processados pelo back-office.
+
+<div class = "alert alert-info">
+Para a maioria dos casos, a VTEX recomenda a integração de pedidos pelo <a href="https://developers.vtex.com/docs/guides/orders-feed">Feed v3</a> devido à sua resiliência.
+</div>
+
+#### Obter detalhes do pedido
+
+Além das mudanças de status, a operação pode precisar obter informações adicionais sobre um pedido. As informações detalhadas de um pedido podem ser obtidas através da [API de Pedidos](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-), a qual pode ser utilizada em uma integração com o sistema de back-office desejado.
+
+Os detalhes do pedido são utilizados em vários procedimentos no processamento de pedidos, como os itens do pedido para fazer o manuseio e o valor da compra para fins de faturamento.
+
+#### Iniciar manuseio
+
+Após os detalhes do pedido serem submetidos ao back-office, o passo final antes de iniciar o processamento de pedidos é alterar o status do pedido para `Iniciar manuseio`. Este procedimento pode ser integrado com o back-office pela [API de Pedidos](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
+
+Mais informações sobre integração para back-office de pedidos nos artigos [Set up order integration](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-integration) e [Feed v3](https://developers.vtex.com/docs/guides/orders-feed).
+
+### Processamento de pedidos
+
+Nesta etapa, é configurada a integração para enviar atualização de pedidos do back-office, ERP ou WMS, para a VTEX. Durante o manuseio de um pedido, várias ações podem ser aplicadas, incluindo alteração, cancelamento e faturamento.
+
+Abaixo se encontram os eventos que o back-office pode transmitir para a VTEX. A integração entre a VTEX e o back-office para a transmissão desses eventos é realizada por meio da [API de Pedidos](https://developers.vtex.com/docs/api-reference/orders-api).
+
+- **Alterar pedido:** alterar itens ou valores do pedido.
+- **Cancelar pedido:** finalizar o pedido e cancelar o pagamento.
+- **Faturar pedido:** [inserir a nota fiscal ao pedido](https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT). Essa é a indicação de que o pedido foi concluído com sucesso e está pronto para ser enviado.
+- **Rastrear pedido:** enviar as informações de rastreamento. Pode ser o código ou URL de rastreamento da transportadora, ou as notificações sobre atualizações no rastreamento.
+
+Mais informações sobre configurar processamento de pedidos para back-office nos artigos [Set up order processing](https://developers.vtex.com/docs/guides/erp-integration-set-up-order-processing) e [Change order](https://developers.vtex.com/docs/guides/change-order).
+
+### SSO (Single Sign-On)
+
+Single Sign-On é um sistema que permite a autenticação de usuários na plataforma utilizando um único conjunto de credenciais de login, eliminando a necessidade de fazer login separadamente em cada aplicativo. A VTEX oferece suporte à integração de provedores de identidade externos. Além das integrações nativas com serviços, como o [Google](https://help.vtex.com/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google--1lBgDmetUM4goie6mYEOK6), é possível criar novas integrações com outros provedores.
+
+O **VTEX ID** é o serviço responsável por identificar os usuários na plataforma. Este serviço opera de acordo com a audiência, as regras de negócios, e o tipo de persona que pode interagir com cada módulo VTEX. As audiências disponíveis são:
+
+| **Audiência** | **Contexto** | **Tecnologia** |
+| :---: | :--- | :--- |
+| [Admin VTEX](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) | Identificação no painel administrativo VTEX, também conhecido como [Admin VTEX](https://help.vtex.com/pt/tutorial/vtex-admin-start-here--531cHtUCUi3puRXNDmKziw), destinado a administradores e operadores da loja. | SAML 2.0 (Security Assertion Markup Language). |
+| [Webstore](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) | Identificação no storefront VTEX, destinado a clientes da loja. | OAuth 2.0 (Open Authorization). |
+
+Mais informações no artigo [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide).
+
+### Pagamentos
+
+Os sistemas de [Pagamento]() da VTEX oferecem recursos extensivos para dar suporte a vários [métodos de pagamento](https://developers.vtex.com/docs/guides/payments-integration-payment-methods), [condições](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento) e integrações. Os pagamentos na VTEX possuem as seguintes opções de [fluxo de compra](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows):
+
+- **Transparente:** o pagamento acontece diretamente no checkout, e o comprador escolhe o método de pagamento.
+- **Redirecionamento:** abre uma nova janela no navegador do comprador, onde o pagamento é processado por um serviço externo. Após finalizar o pagamento, o comprador retorna ao checkout para finalizar a compra.
+- **Payment App:** abre uma janela modal na página do checkout. Ao finalizar o pagamento, a janela se fecha e o fluxo da compra continua no checkout. Este fluxo também pode ser utilizado para o método de autenticação [3D Secure 2 (3DS2)](https://developers.vtex.com/docs/guides/payments-integration-payment-app#scenario-2-payment-app-and-3d-secure-2).
+
+Para adicionar pagamentos em uma loja VTEX, existem as seguintes opções:
+
+- **Provedor de pagamentos suportado nativamente:** caso a VTEX ofereça a integração com o provedor de pagamentos desejado, é necessário possuir um contrato com o provedor e configurar as opções de pagamento através do Admin VTEX. Veja os detalhes sobre configurações no artigo [Pagamentos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagamentos) e os provedores de pagamentos suportados pela VTEX na [Lista de Provedores de Pagamentos por País](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).
+- **Provedor de pagamentos personalizado:** Caso o provedor de pagamentos desejado não possua uma integração com a VTEX, é necessário criar uma integração de pagamento utilizando o [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m) contendo os [endpoints da API](https://developers.vtex.com/docs/api-reference/payment-provider-protocol) para se conectar com o nosso [gateway de pagamentos](https://help.vtex.com/pt/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk). O conector pode ser implementado por uma [agência parceira da VTEX](https://partnerportal.vtex.com/). Para que o provedor seja disponibilizado na VTEX, é necessário testar a integração criada e passar pelo [processo de homologação](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation). 
+
+Mais informações sobre integrar um novo provedor de pagamentos no artigo [Integrating a new payment provider on VTEX](https://developers.vtex.com/docs/guides/integrating-a-new-payment-provider-on-vtex).
+
+### Vales-presente
+
+Na VTEX, vales-presente, também conhecidos como gift cards, podem ser usados como uma opção de pagamento no **Checkout**, e como parte de programas de fidelidade. A VTEX fornece uma solução nativa de vales-presente e também suporta integrações com provedores de vale-presente externos.
+
+Para adicionar vales-presente em uma loja VTEX, existem as seguintes opções:
+
+- **Solução nativa de vales-presente:** caso deseje utilizar a solução nativa de vales-presente da VTEX ou alguma integração já existente, deve-se configurar os vales-presente pelo Admin VTEX seguindo os passos do artigo [Configurar Vale-presente](https://help.vtex.com/pt/tutorial/gift-card--tutorials_995).
+- **Provedor de vales-presente personalizado:** caso o provedor de vales-presente desejado não possua uma integração com a VTEX, é necessário implementar a própria integração utilizando o [Gift Card Provider Protocol](https://help.vtex.com/pt/tutorial/integrando-com-gift-card). Através deste protocolo, provedores podem desenvolver uma integração contendo os endpoints descritos na nossa [Gift Card Provider Protocol API](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol#overview) e conectar com o nosso [Gift Card Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api#overview).
+
+### Antifraude
+
+O antifraude é um sistema especializado em analisar as compras realizadas nos sites, com o intuito de identificar operações fraudulentas. Na VTEX, primeiro a operadora do pagamento aprova a compra e, em seguida, o antifraude avalia o pedido. 
+
+Para adicionar um sistema de antifraude aos pagamentos de uma loja VTEX, existem as seguintes opções:
+
+- **Sistema de antifraude suportado nativamente:** caso já exista uma integração com o sistema de antifraude desejado na VTEX, é necessário possuir um contrato com uma das empresas parceiras e fazer a configuração no Admin VTEX. Mais informações nos artigos [Configurar o antifraude](https://help.vtex.com/pt/tutorial/como-configurar-antifraude--tutorials_446) e [O que é antifraude?](https://help.vtex.com/pt/tutorial/o-que-e-antifraude--69SjFCc4rC6Ii0OMAeYAsG).
+- **Sistema de antifraude personalizado:** caso o sistema de antifraude desejado não possua uma integração com a VTEX, é necessário implementar a própria integração de antifraude utilizando o [Antifraud Provider Protocol](https://developers.vtex.com/docs/guides/how-the-integration-protocol-between-vtex-and-antifraud-companies-works) contendo os endpoints da [Anti-fraud Provider API](https://developers.vtex.com/docs/api-reference/antifraud-provider-protocol).
+
+## Extensões e apps
+
+Além dos serviços essenciais oferecidos pela VTEX, é possível aprimorar as funcionalidades das lojas VTEX com a incorporação de extensões. Essas extensões são ferramentas que ampliam as capacidades da plataforma VTEX e oferecem diversas possibilidades, como adicionar provedores de pagamento e marketplace, personalizar o storefront, construir serviços de backend personalizados e criar novas aplicações para o Admin VTEX.
+
+Uma das formas de inserir novas funcionalidades à plataforma VTEX é criando apps utilizando o [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io), nossa plataforma de desenvolvimento responsável por proporcionar um gerenciamento de alto desempenho, escalabilidade e segurança robusta. Com o VTEX IO, desenvolvedores focam em construir soluções de negócio sem se preocupar com questões de infraestrutura.
+
+### O que é um app na VTEX
+
+Um [app](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app) na VTEX é uma aplicação construída utilizando o VTEX IO. Apps são um tipo de extensão, ou seja, também são responsáveis por estender as funcionalidades da plataforma VTEX. Apps podem ser [desenvolvidos](https://developers.vtex.com/docs/app-development) localmente, com código personalizado, e posteriormente integrados às lojas que operam na nossa infraestrutura. Apps também podem ser disponibilizados e adquiridos através da [VTEX App Store](https://developers.vtex.com/docs/guides/vtex-app-store).
+
+Os tipos de apps disponíveis na VTEX são:
+
+- [Storefront](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ): temas de loja desenvolvidos com o [Store Framework](https://help.vtex.com/pt/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework).
+- [Frontend](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io): componentes [React](https://react.dev/) que compõem temas de loja desenvolvidos com Store Framework.
+- [Admin VTEX](https://learn.vtex.com/docs/course-admin-lang-en): módulos e funcionalidades para o [Admin VTEX](https://help.vtex.com/pt/tutorial/vtex-admin-start-here--531cHtUCUi3puRXNDmKziw).
+- [Serviços (backend)](https://developers.vtex.com/docs/guides/vtex-io-documentation-service): serviços [Node](https://nodejs.org/en) ou [.NET Core](https://dotnet.microsoft.com/en-us/) capazes de lidar com eventos e gatilhos, exportar rotas HTTP, e expor resolvedores GraphQL.
+- [Pixel](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developnativeintegrationswithpixelapps): scripts de serviços terceiros que são executados na frente de loja (frontend), provendo soluções como monitoramento de vendas, suporte ao usuário, coleta de dados e serviços de marketing.
+- [Edition](https://developers.vtex.com/docs/guides/vtex-io-documentation-edition-app): conjunto de configurações, políticas, apps backend e frontend encapsulados e exportados por uma [Sponsor Account](https://developers.vtex.com/docs/guides/vtex-io-documentation-sponsor-account).
+
+Para conhecer as opções de implementação de apps, basta conferir a [lista de builders](https://developers.vtex.com/docs/guides/vtex-io-documentation-builders#list-of-builders).
+
+Mais informações no artigo [O que é um App VTEX](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app). 
+
+### O que levar em consideração ao escolher um app para ser instalado na sua loja?
+
+Antes de iniciar o processo de desenvolvimento de um novo app, é recomendável explorar as soluções prontas para instalação na sua loja. Essas soluções podem ser encontradas no [Hub de Extensões](https://help.vtex.com/pt/tracks/extensions-hub--AW7klkYMh557y5IUOgzco), o painel do Admin VTEX que centraliza o gerenciamento de extensões. No Hub de Extensões estão disponíveis os seguintes painéis:
+
+- **App Store:** marketplace onde estão disponíveis apps desenvolvidos pela VTEX e por terceiros. Neste painel é possível visualizar, adquirir e instalar apps para uma conta VTEX. Existem apps gratuitos e pagos, que possuem diversas formas de cobrança.
+- **Gerenciamento de Aplicativos:** página que permite instalar, desinstalar, remover e configurar apps na loja.
+
+Veja alguns exemplos de soluções disponíveis na App Store:
+
+- [Assembly Options](https://developers.vtex.com/docs/guides/assembly-options-app): adiciona opções de [anexos](https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm) para personalização de SKUs. Por exemplo, adicionar uma frase em uma camiseta ou ingredientes em um sanduíche.
+- [Gift List](https://developers.vtex.com/docs/apps/vtex.list): permite criar listas de presente, que podem ser compartilhadas para que outras pessoas comprem os itens a serem presenteados. São úteis para eventos como aniversário, casamento e chá de bebê. Os itens comprados são transformados em créditos na loja, que podem ser utilizados para comprar quaisquer itens disponíveis na loja.
+- [Live Shopping](https://developers.vtex.com/docs/apps/vtexventures.livestreaming): permite a transmissão ao vivo no site da loja para engajar os clientes em tempo real. Cria oportunidades para promover produtos e possui vários componentes além do reprodutor de vídeo como número de espectadores, botão de curtir, chat em tempo real e barra lateral para apresentar produtos.
+- **Apps de chat com clientes**: adicionam um componente de chat para interagir com clientes. Podem possuir chatbot para interação automática, além de fornecer suporte humano. Alguns exemplos de apps são [JivoChat](https://developers.vtex.com/docs/apps/vtex.jivochat), [Tawk.to](https://developers.vtex.com/docs/apps/vtex.tawk-to) e [Zendesk Chat](https://developers.vtex.com/docs/apps/vtex.zendesk-chat).
+- **Apps de análise e avaliação:** adicionam componentes para que clientes avaliem os produtos da loja, geralmente por uma nota numérica ou um texto. Alguns exemplos de apps são [Reviews and Ratings by VTEX](https://developers.vtex.com/docs/apps/vtex.reviews-and-ratings), [Bazaarvoice](https://developers.vtex.com/docs/apps/vtex.bazaarvoice) e [PowerReviews](https://developers.vtex.com/docs/apps/vtex.powerreviews).
+- **Apps de mídias sociais:** permite a interação com mídias sociais, por exemplo para divulgar os produtos da loja por anúncios na plataforma de mídia. Alguns exemplos de apps são [TikTok for Business](https://developers.vtex.com/docs/apps/vtexbr.tiktok-tbp) e [Facebook Business Extension](https://developers.vtex.com/docs/apps/vtex.facebook-fbe).
+
+### O que levar em consideração ao criar um app para a sua loja
+
+Se a loja VTEX não encontrar um app que atenda às necessidades do seu modelo de negócio, existe a alternativa de desenvolver uma solução própria. Neste sentido, existem vários aspectos a serem considerados para desenvolver apps na VTEX:
+
+- **Quem será responsável pelo desenvolvimento e manutenção?** Os apps podem ser desenvolvidos e mantidos pelo time de desenvolvimento interno da empresa ou por uma agência certificada VTEX. Os [parceiros de implementação da VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao) podem ser encontrados no nosso [Partner Portal](https://partnerportal.vtex.com/) (somente português). Além do desenvolvimento, o responsável pelo app é encarregado da sua manutenção e atualizações.
+- **Que tipo de app deve ser desenvolvido?** É importante saber o contexto em que a solução desejada irá atuar. Os tipos de apps disponíveis estão descritos [acima](#o-que-e-um-app-na-vtex). Nós temos guias de “desenvolvimento para alguns tipos de apps como [storefront](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developing-storefront-apps-using-react-and-vtex-io), [serviço](https://developers.vtex.com/docs/guides/vtex-io-documentation-developing-service-configuration-apps) e [Pixel](https://developers.vtex.com/docs/guides/vtex-io-documentation-1-developnativeintegrationswithpixelapps).
+- **Como desenvolver um app?** O desenvolvimento de um app é feito em várias etapas. Em geral, o processo de desenvolvimento segue os seguintes passos:
+
+    a. **Preparar o ambiente de desenvolvimento:** os principais requisitos antes de começar a desenvolver um app são [instalar](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install) a [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) (command-line interface) e [criar um workspace de desenvolvimento](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace) na conta da loja.
+
+    b. **Interagir com o código**: normalmente, o desenvolvimento se inicia a partir de um template inicial, seguido da implementação local no código. O template deve ser escolhido de acordo com o tipo de app desejado. É possível verificar os templates disponíveis rodando o [comando da CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-command-reference) `vtex init`. Além disso, é necessário configurar do arquivo [manifest.json](https://developers.vtex.com/docs/guides/vtex-io-documentation-manifest), onde são definidos vários parâmetros como o nome do app, o nome do desenvolvedor (vendor) e as [permissões](https://developers.vtex.com/docs/guides/vtex-io-documentation-policies). Após a edição do código, o app é inserido no workspace de desenvolvimento pelo [comando da CLI vtex link](https://developers.vtex.com/docs/guides/vtex-io-documentation-linking-an-app) para realização de testes.
+
+    c. **Empacotar o código em uma nova versão:** após os testes, deve-se seguir os passos para [lançar uma nova versão do app](https://developers.vtex.com/docs/guides/vtex-io-documentation-releasing-a-new-app-version) e [publicar um app](https://developers.vtex.com/docs/guides/vtex-io-documentation-publishing-an-app). Isso permite que o código fique salvo na infraestrutura da VTEX e possa ser instalado em [workspaces de produção](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace).
+
+    d. **(Opcional) Validar se o meu app atende a minha necessidade de negócio:** após ter a versão publicada, pode ser interessante instalar o app em um [workspace de produção](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace) e realizar um [teste A/B](https://developers.vtex.com/docs/guides/ab-tests) a fim de comparar a taxa de conversão das vendas considerando o seu novo app.
+
+<div class = "alert alert-info">
+Caso queira aprender mais sobre o desenvolvimento de apps, recomendamos acessar o nosso <a href="https://learn.vtex.com/">Learning Center</a>.
+</div>
+
+- **Deseja tornar o app disponível publicamente?** É possível [disponibilizar](https://developers.vtex.com/docs/guides/vtex-io-documentation-making-your-new-app-version-publicly-available) o app na App Store, permitindo que outras contas possam se alavancar da solução desenvolvida.
+- **Deseja tornar o app disponível na App Store?** Existem algumas vantagens em tornar o app disponível na App Store, como aumentar a visibilidade do seu app e a possibilidade de [monetizá-lo](https://developers.vtex.com/docs/guides/vtex-io-documentation-setting-your-apps-billing-model). Para isso, é necessário seguir alguns passos e regras. Em resumo, deve-se tornar um [desenvolvedor registrado](https://developers.vtex.com/docs/guides/vtex-io-documentation-becoming-a-registered-vtex-app-store-developer), ter o código do app armazenado em um repositório do [GitHub](https://github.com), desenvolver o app obedecendo as [melhores práticas da App Store](https://developers.vtex.com/docs/guides/vtex-io-documentation-homologation-requirements-for-vtex-app-store) e [submetê-lo](https://developers.vtex.com/docs/guides/vtex-io-documentation-submitting-your-app-in-the-vtex-app-store) ao processo de homologação. Após homologado, o app estará disponível na App Store.
diff --git a/docs/tracks/pt/banners-en.md b/docs/tracks/pt/banners-en.md
index 4585769a6..814c6a284 100644
--- a/docs/tracks/pt/banners-en.md
+++ b/docs/tracks/pt/banners-en.md
@@ -33,7 +33,7 @@ No Admin VTEX, a página **Storefront** > **Banners** exibe a listagem dos banne
 * [Editar um banner](#editar-banner)
 * [Deletar um banner](#deletar-banner) 
 
-![banners-intro-pt](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
+![banners-intro-pt](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
 
 A página apresenta as seguintes informações: 
 
diff --git a/docs/tracks/pt/barcode-reading.md b/docs/tracks/pt/barcode-reading.md
index cae9667f4..f379fe9c9 100644
--- a/docs/tracks/pt/barcode-reading.md
+++ b/docs/tracks/pt/barcode-reading.md
@@ -18,6 +18,6 @@ Após fazer a identificação do cliente, o vendedor é levado já diretamente p
 
 Se o vendedor estiver usando um tablet ou smartphone, ele verá, na barra superior do aplicativo, um botão de código de barras <i class="fas fa-barcode"></i>.
 
-![31. VTEX Sales App - Product Overview - 6 - EN](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/543f300da71b929ff7e6d57581040128/barcode.png)
+![31. VTEX Sales App - Product Overview - 6 - EN](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/543f300da71b929ff7e6d57581040128/barcode.png)
 
 Ao clicar nele, o vendedor pode usar a câmera para bipar um produto e, com isso, ser levado automaticamente à tela de detalhes deste produto.
diff --git a/docs/tracks/pt/basic-vtex-io-developer-setup.md b/docs/tracks/pt/basic-vtex-io-developer-setup.md
index ad4f0dbe4..36f63761b 100644
--- a/docs/tracks/pt/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/pt/basic-vtex-io-developer-setup.md
@@ -38,7 +38,7 @@ Isso abrirá uma janela do navegador que solicitará suas credenciais.
 
 Quando estiver logado, você pode usar o comando `vtex whoami` para descobrir qual *conta* e *workspace* está usando atualmente.
 
-![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
+![Command Line](//images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
 <div class="alert alert-info">
 Dica: Você pode configurar seu terminal para exibir sua conta e workspace atuais automaticamente. A maneira mais fácil de fazer isso é usar nossos <a href="https://github.com/vtex/dotfiles">dotfiles</a>, que configuram automaticamente  a <a href="https://fishshell.com/">Fish Shell</a> e adicionam uma <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">função de prompt</a> para você.
@@ -54,7 +54,7 @@ Por padrão, quando efetua login em uma loja, você está no workspace `master`.
 $ vtex ls
 ```
 
-![Command Line vtex ls](https://images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
+![Command Line vtex ls](//images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
 
 ## Criando seu próprio workspace
 
@@ -72,6 +72,6 @@ Dica: Você pode alternar para (<em>e redefinir</em>) um workspace master em um
 
 Os workspaces podem ser nomeados arbitrariamente, mas geralmente é conveniente atribuir o seu próprio nome quando você deseja desenvolver em seu ambiente.
 
-![command line workspace](https://images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
+![command line workspace](//images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
 
 Agora você tem seu próprio workspace. Você pode rodar `vtex list` novamente e observar que as apps instaladas espelham aquelas em `master`. Agora, vamos "linkar" uma versão local do tema da loja para que você possa começar a editá-la.
diff --git a/docs/tracks/pt/best-practices-for-testing-instore.md b/docs/tracks/pt/best-practices-for-testing-instore.md
index 86d198f5e..34b61ac8e 100644
--- a/docs/tracks/pt/best-practices-for-testing-instore.md
+++ b/docs/tracks/pt/best-practices-for-testing-instore.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Após finalizar as configurações básicas e a instalação do aplicativo do VTEX Sales App em um dispositivo, é importante realizar testes antes de começar a utilizar o VTEX Sales App em suas lojas físicas. Neste artigo, você vai conhecer as boas práticas para testes de uso do VTEX Sales App.
 
-![testes-instore-pt](https://images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/090c0fa4f420c4d875181819c200360b/Group_4__2_.png)
+![testes-instore-pt](//images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/090c0fa4f420c4d875181819c200360b/Group_4__2_.png)
 
 ## Testes de retaguarda
 
diff --git a/docs/tracks/pt/billing-support.md b/docs/tracks/pt/billing-support.md
new file mode 100644
index 000000000..191bb1510
--- /dev/null
+++ b/docs/tracks/pt/billing-support.md
@@ -0,0 +1,52 @@
+---
+title: 'Suporte financeiro'
+id: 3g2mhmPDx5GszNgLDICzsl
+status: PUBLISHED
+createdAt: 2024-02-20T21:41:41.795Z
+updatedAt: 2024-02-22T14:08:36.105Z
+publishedAt: 2024-02-22T14:08:36.105Z
+firstPublishedAt: 2024-02-22T14:08:36.105Z
+contentType: trackArticle
+productTeam: Others
+slug: suporte-financeiro
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+Após o [cliente chegar à VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz), podem surgir dúvidas relacionadas a alterações de dados cadastrais, informações de cobrança, faturas e outros aspectos financeiros da conta. Nesse sentido, o suporte financeiro está disponível para ajudar com questões contratuais e financeiras relacionadas às lojas e à VTEX.
+
+O primeiro contato pode ser feito através dos artigos do [Help Center](https://help.vtex.com/pt/) e conferindo os tópicos apresentados a seguir.
+
+## Contas a pagar
+
+A VTEX busca garantir a conformidade com os procedimentos e políticas de pagamentos a fornecedores das filiais e, para isso, implementou práticas específicas que os fornecedores precisam seguir, dependendo da localização:
+
+- [Contas a Pagar - Brasil](https://help.vtex.com/pt/tutorial/contas-a-pagar-brasil--tutorials_660): práticas a serem seguidas em todos os pagamentos a fornecedores relacionados aos procedimentos de contas a pagar das filiais VTEX no Brasil.
+- [Contas a pagar - Internacional](https://help.vtex.com/pt/tutorial/contas-a-pagar-internacional--3yea9sIlsA0KgUC28ASCGs): práticas a serem seguidas em todos os pagamentos a fornecedores relacionados aos procedimentos de contas a pagar das filiais VTEX fora do Brasil.
+
+<div class = "alert alert-info">
+  <p>Para conferir a lista de filiais VTEX pelo mundo e saber em qual país é emitida a fatura, basta consultar o artigo <a href="https://help.vtex.com/pt/tutorial/nomes-das-filiais-vtex-pelo-mundo--zg05n6OIOZOEmLW7dcq9z">País de faturamento da loja</a>.</p>
+</div>
+
+## Cálculo da receita da fatura pela VTEX
+
+A receita refere-se a pedidos marcados como `Pedidos aprovados` na [página de detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). Uma vez que um pedido seja aprovado financeiramente, o valor total do pedido, incluindo frete e impostos finais, é considerado na fatura. Isso ocorre independentemente de cancelamentos posteriores, devido à utilização da infraestrutura da plataforma.
+
+Através do módulo **Pedidos**, também é possível baixar o relatório financeiro, visualizar o detalhamento de faturas e o que são os valores da receita aprovada.
+
+Para mais informações, basta consultar os artigos [O que a VTEX considera como receita no cálculo da fatura?](https://help.vtex.com/pt/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq) e [Compreendendo o valor da receita](https://help.vtex.com/pt/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322).
+
+## Alteração dos dados cadastrais da loja
+
+Após o [primeiro acesso](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz), é possível alterar os dados cadastrais da loja como:
+
+- Correções e inclusão de contatos.
+- Transferência de responsabilidade.
+- Alteração de documento de identificação da conta.
+
+Para fazer essas alterações, é necessário [abrir um chamado para o suporte financeiro](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM#financeiro), especificando o tipo de alteração necessária.
+
+<div class = "alert alert-info">
+  <p>Para obter mais informações sobre como solicitar a avaliação de SLA e descontos concedidos devido a violações do SLA, basta consultar o artigo <a href="https://help.vtex.com/pt/tutorial/como-solicitar-a-apuracao-de-sla--3L99VeoLhYEwMqqkWKu86i>">Solicitar apuração de SLA do suporte VTEX</a>.</p>
+</div>
diff --git a/docs/tracks/pt/canceling-an-order.md b/docs/tracks/pt/canceling-an-order.md
index 160228d85..021466251 100644
--- a/docs/tracks/pt/canceling-an-order.md
+++ b/docs/tracks/pt/canceling-an-order.md
@@ -3,8 +3,8 @@ title: 'Cancelar pedido'
 id: 4ts2ItvjYo8wm5gg76miS3
 status: PUBLISHED
 createdAt: 2019-11-18T11:50:32.691Z
-updatedAt: 2023-03-22T23:28:21.211Z
-publishedAt: 2023-03-22T23:28:21.211Z
+updatedAt: 2024-04-01T18:04:36.603Z
+publishedAt: 2024-04-01T18:04:36.603Z
 firstPublishedAt: 2019-11-18T12:20:50.741Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -23,6 +23,10 @@ trackSlugPT: pedidos
 Uma vez que o pedido seja cancelado, não é possível alterar o seu status. Pedidos com status <b>Faturado</b> não podem ser cancelados.
 </div>
 
+<div class = "alert alert-info">
+Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
+</div>
+
 ## Cancelamento pelo módulo Pedidos
 
 1. No Admin VTEX, acesse **Pedidos > Todos os pedidos**, ou digite **Todos os pedidos** na barra de busca no topo da página.
diff --git a/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md b/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
index 9acd65d85..ae67aacf3 100644
--- a/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
+++ b/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
@@ -20,25 +20,25 @@ Após o seu cliente clicar no chat, ele será direcionado a um formulário, onde
 
 Depois de preencher o  as informações ele será direcionado para o WhatsApp.
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 1](https://images.ctfassets.net/alneenqid6w5/3XFOXC4aO8kqu550uXLsCG/d957132af5ff3ac5b48f6a340625fb06/Screenshot_2022-08-25_at_14-57-08_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 1](//images.ctfassets.net/alneenqid6w5/3XFOXC4aO8kqu550uXLsCG/d957132af5ff3ac5b48f6a340625fb06/Screenshot_2022-08-25_at_14-57-08_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
 
 Para começar, você precisa criar um **link** para cada número que irá atender na sua empresa. Se você ainda não criou ou não sabe como criar, [leia mais sobre links.](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB) Mas, se você já possui todos os links criados, vamos começar a organizar o nosso processo de [**captura**.](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo)  
 
 1. Defina em qual etapa você deseja capturar as informações (ela pode ser diretamente no link distribuído nas redes sociais, no chat antes de selecionar o setor ou até mesmo na hora do redirecionamento [sequencial](https://help.vtex.com/pt/tutorial/seletivo--7zjQVFhGbwYZ7NW8yKRSKX) ou [geolocalizado](https://help.vtex.com/pt/tutorial/geolocalizado--6XIfgaqXaPe5exQa9oVp6D)).
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 2](https://images.ctfassets.net/alneenqid6w5/7Lc7JSpcU6lSIK0vEZZkzu/2e0b8536fb814f1f7bcf9a4e401942b1/Screenshot_2022-08-25_at_15-01-46_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 2](//images.ctfassets.net/alneenqid6w5/7Lc7JSpcU6lSIK0vEZZkzu/2e0b8536fb814f1f7bcf9a4e401942b1/Screenshot_2022-08-25_at_15-01-46_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
 
 2. Selecione o link que será o link âncora**.
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 3](https://images.ctfassets.net/alneenqid6w5/2QKQTKLBwpZSfcMNoOfijk/3d1d0c8b42fcd2cb4d6215cbed713a15/Screenshot_2022-08-25_at_15-02-27_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 3](//images.ctfassets.net/alneenqid6w5/2QKQTKLBwpZSfcMNoOfijk/3d1d0c8b42fcd2cb4d6215cbed713a15/Screenshot_2022-08-25_at_15-02-27_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
 
 3. Recomendamos sempre o mesmo link que será o de destino.
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 4](https://images.ctfassets.net/alneenqid6w5/2ZJjdfc2ICq5Zh6UR9x8JZ/c0c7c33d49a9de249f5e953af397c93c/Screenshot_2022-08-25_at_15-03-19_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 4](//images.ctfassets.net/alneenqid6w5/2ZJjdfc2ICq5Zh6UR9x8JZ/c0c7c33d49a9de249f5e953af397c93c/Screenshot_2022-08-25_at_15-03-19_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
 
 4. Defina os campos que deseja capturar de seus Leads 
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 5](https://images.ctfassets.net/alneenqid6w5/79O7HBEFJpTbDxJt2XkahA/50e889ee13894faac97e5bd1b582f6e8/Screenshot_2022-08-25_at_15-05-18_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 5](//images.ctfassets.net/alneenqid6w5/79O7HBEFJpTbDxJt2XkahA/50e889ee13894faac97e5bd1b582f6e8/Screenshot_2022-08-25_at_15-05-18_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
 
 5. Para definir, basta clicar e selecionar o campo desejado. Além disso, você ainda pode ativar o modo robô. Acesse [https://whts.co/bot](\"https://whts.co/bot\") e faça um teste da experiência que seu cliente terá.
 
diff --git a/docs/tracks/pt/carrefour-marketplace.md b/docs/tracks/pt/carrefour-marketplace.md
index 10ef4af8d..661f16b09 100644
--- a/docs/tracks/pt/carrefour-marketplace.md
+++ b/docs/tracks/pt/carrefour-marketplace.md
@@ -16,6 +16,6 @@ trackSlugPT: configurar-integracao-do-carrefour
 
 O [Carrefour](https://www.carrefour.com.br/) é uma das principais empresas do ramo varejista físico e online do país, operando no Brasil há mais de 40 anos e uma das suas linhas de negócio é o [Carrefour Marketplace](https://www.carrefour.com.br/marketplace), onde sellers se beneficiam da visibilidade nacional e credibilidade da marca para vender seus produtos para mais de 6 milhões de clientes cadastrados na sua plataforma.
 
-![carrefourmkt](https://images.ctfassets.net/alneenqid6w5/3vjhZetYnWLNUAZWZXCBiI/dc1d6f0d919a1ec5784a31c1d0ce1ea7/carrefourmkt.jpg)
+![carrefourmkt](//images.ctfassets.net/alneenqid6w5/3vjhZetYnWLNUAZWZXCBiI/dc1d6f0d919a1ec5784a31c1d0ce1ea7/carrefourmkt.jpg)
 
 A configuração com o Carrefour tem como objetivo enviar o catálogo de produtos da sua loja VTEX para esse marketplace, permitindo que você anuncie seus produtos e expanda seus canais de venda.
diff --git a/docs/tracks/pt/cart-transfer-and-capture.md b/docs/tracks/pt/cart-transfer-and-capture.md
index ee3474d19..0f9642c16 100644
--- a/docs/tracks/pt/cart-transfer-and-capture.md
+++ b/docs/tracks/pt/cart-transfer-and-capture.md
@@ -20,11 +20,11 @@ O VTEX Sales App permite [habilitar uma funcionalidade de transferência de carr
 
 Para o vendedor compartilhar um carrinho, ele pode gerar um código numérico ou um QR Code. Para isso, estando na tela do carrinho, basta clicar no botão __Transferir__. Veja um exemplo na imagem abaixo.
 
-![24. Enable cart transfer between devices - 3](https://images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
+![24. Enable cart transfer between devices - 3](//images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
 
 Ao clicar nesse botão, o aplicativo mostra um QR Code e um código numérico de quatro dígitos.
 
-![31. VTEX Sales App - Product Overview - 9](https://images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._VTEX Sales App_-_Product_Overview_-_9.png)
+![31. VTEX Sales App - Product Overview - 9](//images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._VTEX Sales App_-_Product_Overview_-_9.png)
 
 Um outro vendedor logado na mesma loja pode, então, capturar esse carrinho e continuar a venda a partir do seu dispositivo.
 
@@ -34,7 +34,7 @@ Para capturar um carrinho, basta entrar no menu principal do VTEX Sales App e cl
 
 Alternativamente, na tela inicial do aplicativo, o vendedor pode simplesmente arrastar a tela para a direita. Ao arrastar a tela para a direita, você verá a tela para __Capturar Carrinho__, conforme mostra a imagem abaixo.
 
-![24. Enable cart transfer between devices - 2](https://images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
+![24. Enable cart transfer between devices - 2](//images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
 
 Nessa tela, é possível capturar um carrinho por um desses três métodos:
 - Código do carrinho
diff --git a/docs/tracks/pt/cart-transfer.md b/docs/tracks/pt/cart-transfer.md
index 046aeeb44..d83277759 100644
--- a/docs/tracks/pt/cart-transfer.md
+++ b/docs/tracks/pt/cart-transfer.md
@@ -31,14 +31,14 @@ window.INSTORE_CONFIG = {
 
 Ao realizar essa alteração, você deve perceber que aparecerão duas bolinhas no fim da página de identificação do inStore:
 
-![01 inStore slider transferencia](https://images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
+![01 inStore slider transferencia](//images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
 
 Ao arrastar a tela para a lateral você verá a tela para __“Capturar carrinho”__:
 
-![02 inStore capturar carrinho](https://images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
+![02 inStore capturar carrinho](//images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
 
 Nela é possível capturar um carrinho pelo código do carrinho, QR code ou até por vendedor.
 
 Para gerar um código ou QR code de um carrinho você deve usar a opção __“Transferir”__ presente no carrinho do inStore:
 
-![03 inStore transferir](https://images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
+![03 inStore transferir](//images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
diff --git a/docs/tracks/pt/catalog-architecture.md b/docs/tracks/pt/catalog-architecture.md
index 3a6d413ce..36a0a7413 100644
--- a/docs/tracks/pt/catalog-architecture.md
+++ b/docs/tracks/pt/catalog-architecture.md
@@ -35,4 +35,4 @@ Essas especificações são, por exemplo, a composição de um produto, ou o tam
 
 Abaixo, vemos um esquema da arquitetura do Catálogo na VTEX.
 
-![arquitetura-catalogo-PT](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
+![arquitetura-catalogo-PT](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
diff --git a/docs/tracks/pt/centauro-marketplace.md b/docs/tracks/pt/centauro-marketplace.md
index 9d764d99d..5b92c448b 100644
--- a/docs/tracks/pt/centauro-marketplace.md
+++ b/docs/tracks/pt/centauro-marketplace.md
@@ -3,8 +3,8 @@ title: 'Centauro Marketplace'
 id: 5HXEYuDGxv7hNVUma3PKPC
 status: PUBLISHED
 createdAt: 2020-10-20T14:22:13.423Z
-updatedAt: 2021-03-22T15:41:41.809Z
-publishedAt: 2021-03-22T15:41:41.809Z
+updatedAt: 2023-09-22T20:08:49.350Z
+publishedAt: 2023-09-22T20:08:49.350Z
 firstPublishedAt: 2020-10-20T14:23:14.172Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,9 +14,9 @@ trackId: D8Qnjbr5lfLkUfMRhsfbj
 trackSlugPT: integracao-com-a-centauro
 ---
 
-A Centauro é maior rede de lojas esportivas da América Latina, presente em mais de 22 estados e com mais de 190 lojas. Seu site possui 15 milhões de visitantes únicos por mês, 5 milhões de usuários conectados por mês via redes sociais. 
+A Centauro é maior rede de lojas esportivas da América Latina, presente em mais de 22 estados e com mais de 190 lojas. Seu site possui 15 milhões de visitantes únicos por mês, 5 milhões de usuários conectados por mês via redes sociais.  
 
-![logo centauro](https://images.ctfassets.net/alneenqid6w5/4GJN1Dn7SBPMN0CzP2nIqg/f48e6b057a585abcd3eb5cf8b0b0e75c/logo_centauro.jpg)
+![logo centauro](//images.ctfassets.net/alneenqid6w5/4GJN1Dn7SBPMN0CzP2nIqg/f48e6b057a585abcd3eb5cf8b0b0e75c/logo_centauro.jpg)
 
 Usando a integração nativa com o Marketplace da Centauro, você poderá expor e vender seus produtos na loja online.
 
diff --git a/docs/tracks/pt/changing-the-instore-language.md b/docs/tracks/pt/changing-the-instore-language.md
index 50ed7102b..7a909b103 100644
--- a/docs/tracks/pt/changing-the-instore-language.md
+++ b/docs/tracks/pt/changing-the-instore-language.md
@@ -80,4 +80,4 @@ Após fazer a alteração no código, salve o arquivo `checkout-instore-custom.j
 
 Em seguida, no aplicativo inStore, para ver as alterações refletidas, entre no menu e clique no botão __Restaurar dados__, como mostra a reprodução abaixo.
 
-![22. Change the inStore language - 1](https://images.ctfassets.net/alneenqid6w5/6kMdyIyQkEUJ9HYKSLSFj4/55748d5b159dc83944dc211e95833669/22._Change_the_inStore_language_-_1.png)
+![22. Change the inStore language - 1](//images.ctfassets.net/alneenqid6w5/6kMdyIyQkEUJ9HYKSLSFj4/55748d5b159dc83944dc211e95833669/22._Change_the_inStore_language_-_1.png)
diff --git a/docs/tracks/pt/cms-folder-structure.md b/docs/tracks/pt/cms-folder-structure.md
index b72091abd..45b01c5c4 100644
--- a/docs/tracks/pt/cms-folder-structure.md
+++ b/docs/tracks/pt/cms-folder-structure.md
@@ -33,7 +33,7 @@ Toda loja precisa ter, sem exceção, as seguintes pastas no CMS para garantir o
 
 Veja abaixo estas pastas básicas no CMS:
 
-![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas pastas vêm por padrão no ambiente de todas as lojas VTEX.
 
diff --git a/docs/tracks/pt/cms-vtex-io.md b/docs/tracks/pt/cms-vtex-io.md
index d10b3e9a7..587a83d98 100644
--- a/docs/tracks/pt/cms-vtex-io.md
+++ b/docs/tracks/pt/cms-vtex-io.md
@@ -27,19 +27,19 @@ Configure o [binding da loja](https://help.vtex.com/en/tutorial/what-is-cms-layo
 
 Binding é o processo utilizado para vincular o seu site a uma loja. Para mais detalhes, consulte o artigo [Vincular uma loja a uma estrutura de pastas do CMS (binding)](https://help.vtex.com/en/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![CMS - Sites and channels PT](https://images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/0c3d2414ac7931cc88b8e11264927765/cms-sites-and-channels-pt.png)
+![CMS - Sites and channels PT](//images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/0c3d2414ac7931cc88b8e11264927765/cms-sites-and-channels-pt.png)
 
 ## Páginas
 Em **[Páginas](https://help.vtex.com/pt/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc)**, crie uma nova URL e vincule-a a uma template já definido no [código do tema da loja](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-4-configuringtemplates).
 
 Essa seção também contém a página **Redirecionamentos**, que redireciona usuários e mecanismos de pesquisa de uma URL para outra mais relevante ou similar. 
 
-![CMS - Páginas](https://images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/43932eacc38cd05af0f1a913cd2eb488/cms-pages-pt.png)
+![CMS - Páginas](//images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/43932eacc38cd05af0f1a913cd2eb488/cms-pages-pt.png)
 
 ## Site Editor
 O **[Site Editor](https://help.vtex.com/pt/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1)** é uma interface gráfica para o gerenciamento do conteúdo do storefront (frente de loja). Ele permite criar, editar, publicar e agendar mudanças nos seus componentes e no comportamento do storefront.
 
-![CMS - Site Editor PT](https://images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/4258f07e4ba21f1d2c0ade81579207e1/cms-siteeditor-pt.png)
+![CMS - Site Editor PT](//images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/4258f07e4ba21f1d2c0ade81579207e1/cms-siteeditor-pt.png)
 
 ## Estilos
 
@@ -49,12 +49,12 @@ A seção **[Estilos](https://help.vtex.com/pt/tutorial/styles-overview--v0Db5oh
   Esse recurso só funciona em <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-creating-a-production-workspace">workspaces de produção</a>.
 </div>
 
-![CMS - Estilos](https://images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/a58296966e9b912d16546bbd232d0800/cms-styles-pt.png)
+![CMS - Estilos](//images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/a58296966e9b912d16546bbd232d0800/cms-styles-pt.png)
 
 ## Loja
 A seção **[Loja](https://help.vtex.com/pt/tutorial/cms-loja-visao-geral--3Eat287G6wUi6Mly5rW5Fs)** é responsável pelas configurações de SEO, marcadores de otimização de desempenho e notificações PWA na sua loja.
 
-![CMS - Loja](https://images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/f5c8cf60d396197462842c2152d70e3b/cms-store-pt.png)
+![CMS - Loja](//images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/f5c8cf60d396197462842c2152d70e3b/cms-store-pt.png)
 
 ## Referências
 - [Conceitos - VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6loFGF4nXvgIVIzsyyJA5c#concepts)
diff --git a/docs/tracks/pt/commercial-support.md b/docs/tracks/pt/commercial-support.md
new file mode 100644
index 000000000..8787f5011
--- /dev/null
+++ b/docs/tracks/pt/commercial-support.md
@@ -0,0 +1,34 @@
+---
+title: 'Suporte comercial'
+id: 3KQWGgkPOwbFTPfBxL7YwZ
+status: PUBLISHED
+createdAt: 2024-02-20T21:44:41.944Z
+updatedAt: 2024-02-22T14:08:28.702Z
+publishedAt: 2024-02-22T14:08:28.702Z
+firstPublishedAt: 2024-02-22T14:08:28.702Z
+contentType: trackArticle
+productTeam: Others
+slug: suporte-comercial
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+Além dos recursos já previstos no contrato inicial com a VTEX, é possível adquirir soluções e ativar outras funcionalidades, para expandir a operação do negócio. Para isso, o suporte comercial orienta sobre:
+
+- Contratar [política comercial adicional](#contratar-politica-comercial-adicional), [ambiente adicional](#contratar-novo-ambiente) e conta franquia.
+- Alterar [usuário titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy).
+- Adquirir [Produtos add-on](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+
+Caso o usuário precise de suporte além dos tópicos a seguir ou adquirir um Produto Add-on, é possível [abrir chamados para o suporte comercial](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM#financeiro). O primeiro contato pode ser feito através dos artigos do [Help Center](https://help.vtex.com/pt/) e conferindo os as seções apresentadas a seguir.
+
+## Contratar política comercial adicional
+
+A [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o recurso das lojas VTEX que define condições e estratégias de vendas em um canal de venda, seja na própria loja, marketplaces, lojas físicas ou modelos B2B, por exemplo. Uma operação pode ter uma única política comercial e ser suficiente, é o modelo de negócio que vai definir quantas políticas comerciais serão associadas a conta.
+
+Para decidir sobre a [contratação de políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), é preciso entender se a conta precisa de ambiente adicional ou multiloja. O artigo [Contas e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) apresenta estes conceitos em detalhes.
+
+## Contratar novo ambiente
+
+Somente a conta principal pode contratar novos ambientes, que podem ser destinados a testes (QA), B2C, B2B dentre outros. Essa contratação é solicitada pelo [suporte VTEX](https://help.vtex.com/pt/support).
+Dependendo do modelo de negócio e estratégia do negócio, pode ser recomendado a contratação de um novo ambiente. Para isso é preciso entender sobre multiloja e ambiente adicional, conforme explicado no artigo [Contas e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl).
diff --git a/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md b/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
index ac9b3c764..6bc629081 100644
--- a/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
+++ b/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
@@ -16,7 +16,7 @@ trackSlugPT: suiteshare
 
 Você já conseguiu o mais difícil, fazer com que seus clientes entrem em contato com a sua empresa pelo WhatsApp. Agora, basta configurar com quem eles irão falar, definir os setores ou se serão direcionados para o atendente mais próximo a ele. 
 
-![Como distribuir o atendimento no WhatsApp para mais de um número 1](https://images.ctfassets.net/alneenqid6w5/7wLfyYNfAzOf7tn6xIBOWm/c899205e4a03b341c5ece68646d8f17e/Screenshot_2022-08-25_at_14-51-20_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
+![Como distribuir o atendimento no WhatsApp para mais de um número 1](//images.ctfassets.net/alneenqid6w5/7wLfyYNfAzOf7tn6xIBOWm/c899205e4a03b341c5ece68646d8f17e/Screenshot_2022-08-25_at_14-51-20_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
 
 Para começar, você precisa criar um link para cada número que irá atender na sua empresa. Se você ainda não criou ou não sabe como criar, [leia mais sobre links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB). Mas, se você já possui todos os links criados vamos começar a organizar o nosso time. 
 
@@ -24,7 +24,7 @@ Para começar, você precisa criar um link para cada número que irá atender na
 
 Acesse “_**Organizar**_” e escolha como será distribuído o atendimento, você pode escolher entre **Sequencial, Geolocalizado** (Apenas para o plano Enterprise) e **Seletivo**.
 
-![Como distribuir o atendimento no WhatsApp para mais de um número 2](https://images.ctfassets.net/alneenqid6w5/6ODYG6o8SZUk9dQvx0Lps/e73c6dca3304220e27815eef943928bc/Screenshot_2022-08-25_at_14-55-02_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
+![Como distribuir o atendimento no WhatsApp para mais de um número 2](//images.ctfassets.net/alneenqid6w5/6ODYG6o8SZUk9dQvx0Lps/e73c6dca3304220e27815eef943928bc/Screenshot_2022-08-25_at_14-55-02_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
 
 No modo **sequencial**, cada cliente que clica nesse link cairá para um atendente diferente, a distribuição é feita de forma sequencial, onde cada atendente terá a sua vez de forma igualitária.  Como se fosse uma fila de espera, cada cliente será direcionado para um atendente, numa espécie de central de atendimento (ou como alguns gostam de chamar), em um call-center de WhatsApp.
 
diff --git a/docs/tracks/pt/como-funciona-o-adaptador-vtex.md b/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
index c8329f425..5b4316e20 100644
--- a/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
+++ b/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
@@ -33,7 +33,7 @@ Para facilitar o entendimento, organizamos o documento em tópicos:
 
 Por meio da tabela abaixo, você pode verificar o que a integração do adaptador contempla:
 
-![image-adaptador-2](https://images.ctfassets.net/alneenqid6w5/4TsEw3tXkfK0IEAZlcRzwR/b9dc7e117331beacf34577442c69da0c/Group_1_9_.png)
+![image-adaptador-2](//images.ctfassets.net/alneenqid6w5/4TsEw3tXkfK0IEAZlcRzwR/b9dc7e117331beacf34577442c69da0c/Group_1_9_.png)
 
 <div class="alert alert-warning">
   <p>Para integração via WEBSERVICE, os pedidos na VTEX serão coletados quando estiverem com pagamento aprovado, no status <b>Pronto-para-manuseio</b>.</p>
diff --git a/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md b/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md
index 8ebd6ed5a..bf8c87248 100644
--- a/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md
+++ b/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuração da estrutura para Atendimento Humano'
 id: SxhYiiqUJYiQX4CIWxmVE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T15:25:37.553Z
-updatedAt: 2023-04-27T15:32:38.909Z
-publishedAt: 2023-04-27T15:32:38.909Z
+updatedAt: 2024-01-05T17:14:19.560Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:47:18.082Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/pt/configurar-erps.md b/docs/tracks/pt/configurar-erps.md
index f3ed0df0a..94891c948 100644
--- a/docs/tracks/pt/configurar-erps.md
+++ b/docs/tracks/pt/configurar-erps.md
@@ -40,7 +40,7 @@ Tudo o que você precisa fazer no ambiente Protheus é alterar os valores  de tr
 3. Clique em **Parâmetros**. A seguinte tela será exibida:
 ![protheusParametros-adaptador](//images.contentful.com/alneenqid6w5/3aqBRHAGIDIeEuSJUTwPjm/c442a2efa4ea45d6040db8a9e6eeaa62/protheusParametros-adaptador.png)
 4. Na barra de ferramentas superior, clique no botão `FILTRO`. Abrirá a tela **Expressão de Filtro**:
-![protheusParametros2-adaptador](https://images.ctfassets.net/alneenqid6w5/5RJ5621Oog3oUS5kzl1Siq/91d3daf359cb35448132f1c68191869d/protheusParametros2-adaptador.png)
+![protheusParametros2-adaptador](//images.ctfassets.net/alneenqid6w5/5RJ5621Oog3oUS5kzl1Siq/91d3daf359cb35448132f1c68191869d/protheusParametros2-adaptador.png)
 5. Na caixa **campos**, informe `X6_VAR`.
 6. Na caixa **Operadores**, escolha **Contém a expressão**.
 7. Na caixa **expressão** informe `MV_LJEC`.
diff --git a/docs/tracks/pt/configure-customer-identification.md b/docs/tracks/pt/configure-customer-identification.md
index aa1c0eb86..5f63b4ce1 100644
--- a/docs/tracks/pt/configure-customer-identification.md
+++ b/docs/tracks/pt/configure-customer-identification.md
@@ -26,11 +26,11 @@ Para escolher quais métodos de identificação você deseja habilitar, acesse o
 
 Na caixa __Login do cliente__, você deve selecionar os métodos de identificação que deseja habilitar.
 
-![21. Configure client identification - 1](https://images.ctfassets.net/alneenqid6w5/30Kb57zS5TKV5rHY851Xl2/d15329ea3a76733869ecefd3c861e150/21._Configure_client_identification_-_1.png)
+![21. Configure client identification - 1](//images.ctfassets.net/alneenqid6w5/30Kb57zS5TKV5rHY851Xl2/d15329ea3a76733869ecefd3c861e150/21._Configure_client_identification_-_1.png)
 
 Você também pode alterar a ordem desses métodos. Para isso, basta arrastá-los, como mostra a imagem abaixo. A ordem dos métodos definida nessa tela determina a ordem em que eles aparecerão para o vendedor no aplicativo. Portanto, o primeiro método será o default.
 
-![21. Configure client identification - 2](https://images.ctfassets.net/alneenqid6w5/6C2oVlDbGtNMJfllED6pcO/9b62fb9778af207ba77320b67ddab653/21._Configure_client_identification_-_2.png)
+![21. Configure client identification - 2](//images.ctfassets.net/alneenqid6w5/6C2oVlDbGtNMJfllED6pcO/9b62fb9778af207ba77320b67ddab653/21._Configure_client_identification_-_2.png)
 
 ## Habilitar Usuário Anônimo
 
@@ -38,7 +38,7 @@ Você também pode alterar a ordem desses métodos. Para isso, basta arrastá-lo
 
 Para isso, ainda na tela de Identificação do Cliente, é necessário habilitar a flag __Usuário anônimo__.
 
-![21. Configure client identification - 3](https://images.ctfassets.net/alneenqid6w5/62h8jghzR0LhqmnhzXYcws/02869cc40d8244aad5985c4f5483a4e6/21._Configure_client_identification_-_3.png)
+![21. Configure client identification - 3](//images.ctfassets.net/alneenqid6w5/62h8jghzR0LhqmnhzXYcws/02869cc40d8244aad5985c4f5483a4e6/21._Configure_client_identification_-_3.png)
 
 ## Cadastro de Pessoa Jurídica para vendas B2B
 
@@ -50,10 +50,10 @@ Você poderá, então, escolher se esses campos devem necessariamente ser preenc
 
 No exemplo abaixo, o cadastro de Pessoa Jurídica está ativado e configurado como opcional.
 
-![21. Configure client identification - 4](https://images.ctfassets.net/alneenqid6w5/i5hr6RRXlNC0aNHKUvg2C/b309608994fe85592c01abf35f643e84/21._Configure_client_identification_-_4.png)
+![21. Configure client identification - 4](//images.ctfassets.net/alneenqid6w5/i5hr6RRXlNC0aNHKUvg2C/b309608994fe85592c01abf35f643e84/21._Configure_client_identification_-_4.png)
 
 Neste caso, o aplicativo mostrará para o vendedor um formulário como este abaixo:
 
-![21. Configure client identification - 5](https://images.ctfassets.net/alneenqid6w5/4bvM9B3FeukRQaHXXMqLhL/7695d831d0f93a7669f054179467ace2/21._Configure_client_identification_-_5.png)
+![21. Configure client identification - 5](//images.ctfassets.net/alneenqid6w5/4bvM9B3FeukRQaHXXMqLhL/7695d831d0f93a7669f054179467ace2/21._Configure_client_identification_-_5.png)
 
 Note que é exibida uma flag que permite ao vendedor decidir entre mostrar ou não esses campos adicionais. Isto é porque, nas configurações, marcamos os campos de cadastro de pessoa jurídica como opcionais. Caso sejam marcados como obrigatórios, essa flag não será exibida no aplicativo.
diff --git a/docs/tracks/pt/configure-integration-of-pick-up-points.md b/docs/tracks/pt/configure-integration-of-pick-up-points.md
index 91449ccb5..ce18e4526 100644
--- a/docs/tracks/pt/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/pt/configure-integration-of-pick-up-points.md
@@ -1,16 +1,16 @@
 ---
 title: 'Configurar integração de pontos de retirada '
 id: 52C1lm8gMovN8v68s6v89d
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-08-12T18:12:20.076Z
-updatedAt: 2021-09-08T17:52:30.570Z
-publishedAt: 2021-09-08T17:52:30.570Z
+updatedAt: 2024-03-11T22:19:05.610Z
+publishedAt: 
 firstPublishedAt: 2021-08-19T15:16:01.224Z
 contentType: trackArticle
 productTeam: Channels
 slug: configurar-integracao-de-pontos-de-retirada
 locale: pt
-trackId: 2YfvI3Jxe0CGIKoWIGQEIq
+trackId: 
 trackSlugPT: configurar-integracao-do-mercado-livre
 ---
 
@@ -57,7 +57,7 @@ Para ativar os pontos de retirada nas contas franquias:
 
 1. Acesse o Admin. 
 2. No módulo MARKETPLACE, selecione a opção **Integrações** e clique em `Configurações`.
-3. Na integração Mercado Livre, clique na engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+3. Na integração Mercado Livre, clique na engrenagem <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 4. Escolha a opção `Editar Configurações`.
 5. No campo **Ativar integração de pontos de retirada para contas franquias**, clique na opção `Sim`.
 6. Clique em `Salvar Configurações`.
diff --git a/docs/tracks/pt/configure-integration.md b/docs/tracks/pt/configure-integration.md
index d48c1266d..114968f6b 100644
--- a/docs/tracks/pt/configure-integration.md
+++ b/docs/tracks/pt/configure-integration.md
@@ -3,8 +3,8 @@ title: 'Configurar integração'
 id: 3tZ4qVuMDDsC2jx2DCmjdA
 status: PUBLISHED
 createdAt: 2021-03-16T20:17:00.970Z
-updatedAt: 2022-09-06T22:49:30.916Z
-publishedAt: 2022-09-06T22:49:30.916Z
+updatedAt: 2024-07-26T19:06:41.787Z
+publishedAt: 2024-07-26T19:06:41.787Z
 firstPublishedAt: 2021-03-18T20:12:33.299Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,49 +14,59 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugPT: configurar-integracao-com-o-magazine-luiza
 ---
 
-A configuração da integração com o Magazine Luiza é feita no Admin. Para realizá-la, siga as instruções abaixo:
-
-1. Acesse o Admin.
-2. No módulo Marketplace, clique em `Integrações`.
-3. Clique em `Configurações`.
-4. No card do Magazine Luiza, clique em `Integrar`.
-5. Preencha os campos da tela descritos logo abaixo e em seguida, clique no botão `Salvar configuração` (campos marcados com o símbolo * são obrigatórios).
-
-- **Integração (se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos)*:** marque _Ativada_ para que a integração comece a operar.
-
-- **Id do afiliado*:** código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestão: MGZ. A configuração do conector cria automaticamente o afiliado.
-
-- **Política Comercial*:** ID da política comercial que será utilizada para a integração com o Magazine Luiza. Todos os produtos vinculados a esta política comercial serão enviados para o marketplace
-
-- **Série da Nota Fiscal*:** numeração que identifica a série a que pertencem um grupo de notas fiscais. Caso nenhum valor seja preenchido, o sistema automaticamente vai atribuir o número 1.
-
-- **Estoque Mínimo (se o saldo do SKU estiver igual ou abaixo do valor configurado, será enviado saldo 0 para o marketplace)*:** valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização do Magalu pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
-
-- **Mapeamento de SLA Customizável (Tipo de Entrega Magalu/Tipo de Entrega VTEX):** no caso do seu Tipo de Entrega Magalu ter um nome diferente da sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), é necessário fazer uma convergência de denominação (de > para) entre ambos.
-  > Exemplo: os Correios (PAC) são usados como transportadoras, seu Tipo de Entrega no Magalu se chama _NORMAL_, e sua política de envio (nome dado ao seu método de envio) na VTEX é _Comum_. Portanto, você deve preencher o primeiro campo com _NORMAL_ e o segundo com _Comum_.
-
-  É possível associar vários Tipos de Entrega Magalu a uma mesma política de envio na VTEX, e não há um número limite de tipos de entrega que podem ser cadastrados no Magazine Luiza. Você também pode alterar os valores padrões do Tipo de entrega Magalu (de até 50 caracteres) para que tenham os mesmos nomes das suas políticas de envio. Neste caso, o mapeamento da correspondência não será necessário, pois os valores serão idênticos.
-
-  <div class="alert alert-danger">
-O pedido só será integrado na VTEX se estiver relacionado a uma estratégia de envio. Mesmo quando a entrega é feita pelo Magazine Luiza, é necessário haver uma correspondência entre a sua política de envio e o seu tipo de entrega Magalu, seja por meio do mapeamento entre valores diferentes ou utilizando valores idênticos. Esteja atento para letras maiúsculas, minúsculas e espaçamentos.
+A configuração da integração com o Magalu é feita em duas etapas, primeiro a  configuração no Admin VTEX e logo após a autenticação no [portal do Magalu Marketplace](https://marketplace-vendamais.magazineluiza.com.br/). Antes de iniciar a configuração, certifique-se de estar [cadastrado](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y) no portal do Magalu Marketplace e siga as instruções abaixo para realizar as etapas de configuração:
+
+1. No Admin VTEX, acesse o módulo **Marketplace > Conexões > Marketplaces e integrações.**
+2. Clique no marketplace `Magazine Luiza`
+3. No modal que aparecerá, clique em `Conectar`.
+4. Preencha os campos da tela, descritos na tabela abaixo. Os campos marcados com o símbolo * são obrigatórios.
+5. Após preencher os campos, clique no botão `Autenticar` no topo da página e você será redirecionado para fazer o login no [portal do Magalu Marketplace](https://marketplace-vendamais.magazineluiza.com.br/).
+6. Para [autorizar a integradora](https://marketplacemagalu.zendesk.com/hc/pt-br/articles/15666930590605) VTEX, no portal do Magalu Marketplace, acesse **MENU > Integradoras.**
+7. Na barra de busca, digite `VTEX` e clique no botão `Autorizar`.
+8. No modal que aparecerá, selecione as seguintes opções de [consentimento de integração](https://marketplacemagalu.zendesk.com/hc/pt-br/articles/15666930590605):
+
+   - OpenId
+   - Permissão acesso marketplace
+
+9. Clique no botão `Continuar`.
+
+Feito isso, a integração da sua loja VTEX com o Magalu Marketplace estará concluída.
+
+| **Campo** | **Descrição** | **Exemplo**|
+|---|---|---|
+| **Integração*** | Marque como *Ativada* para que a integração comece a operar. Se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos. | ![Integração Magalu](//images.ctfassets.net/alneenqid6w5/3h6E673Nx6xsCpjbqGAjYd/d8b34130a2a85301b469a5f5fea55f45/integra____o_magalu.png) |
+| **CNPJ*** | CNPJ utilizado no cadastrado no portal Magalu Marketplace. Inserir apenas números, sem caracteres especiais. | **45121594000127** |
+| **Id do afiliado*** | Código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não. Vogais não são aceitas. A configuração do conector cria automaticamente o afiliado. | **MGZ** |
+| **Política Comercial*** | ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será utilizada para a integração com o Magalu Marketplace. Todos os produtos vinculados a esta política comercial serão enviados para o marketplace. | **1** |
+| **Série da Nota Fiscal*** | Numeração da série de um grupo de notas fiscais. Caso nenhum valor seja preenchido, o sistema automaticamente vai atribuir o número 1. |**123**|
+| **Estoque Mínimo*** | Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização do Magalu pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial. Se o saldo do SKU estiver igual ou abaixo do valor configurado, será enviado saldo 0 para o marketplace. | **3** |
+| **Mapeamento de SLA Customizável** | Tipo de Entrega Magalu x Tipo de Entrega VTEX. No caso do seu Tipo de Entrega Magalu ter um nome diferente da sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), é necessário fazer uma convergência de denominação **(de > para)** entre ambos.É possível associar vários Tipos de Entrega Magalu a uma mesma política de envio na VTEX, e não há um número limite de tipos de entrega que podem ser cadastrados no Magalu Marketplace. Você também pode alterar os valores padrões do Tipo de entrega Magalu (de até 50 caracteres) para que tenham os mesmos nomes das suas políticas de envio. Neste caso, o mapeamento da correspondência não será necessário, pois os valores serão idênticos. O pedido só será integrado na VTEX se estiver relacionado a uma [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3). Mesmo quando a entrega é feita pelo Magalu Marketplace, é necessário haver uma correspondência entre a sua política de envio e o seu Tipo de Entrega Magalu, seja por meio do mapeamento entre valores diferentes ou utilizando valores idênticos. Os Correios (PAC) são usados como transportadoras, seu Tipo de Entrega no Magalu se chama NORMAL, e sua política de envio (nome dado ao seu método de envio) na VTEX é Comum. Portanto, você deve preencher o primeiro campo com NORMAL e o segundo com Comum. Esteja atento para letras maiúsculas, minúsculas e espaçamentos. | <p><b>NORMAL > Comum</b></p>|
+| **Enviar Kit*** | Ao escolher Não, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para o Magalu Marketplace. Ao habilitar Sim, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudar sua configuração de *Sim* para *Não*, SKUs enviados anteriormente para o Magalu não são removidos ou alterados. Com a opção Não ativada, tentativas de envio para o Magalu Marketplace de SKUs cadastrados como kit resultam no seguinte aviso: `O conector está configurado para não enviar SKUs do tipo Kit.`  Esta mensagem pode ser visualizada no Admin VTEX, em **Marketplace > Conexões > Produtos**, clicando no SKU. | ![Enviar kit Magalu](//images.ctfassets.net/alneenqid6w5/27gXQYqGSyzJlJPIcOkFKh/fefbd13c07f92ce502972d47bfe7d18e/enviar_kit_magalu.png) |
+| **Ativar estoque para entrega de cotação de frete para contas franquias*** | Com a opção *Sim* selecionada, a funcionalidade [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) permite que você venda na Magalu produtos dos estoques das suas contas franquias. Ou seja, o estoque de contas franquias é disponibilizado para *fullfilment* de pedidos na Magalu. | ![Ativar estoque Magalu](//images.ctfassets.net/alneenqid6w5/4AfIZTX6Oe5KPRUOlmoBug/4d7f29cc1480552f6a2897b409599403/ativar_estoque_magalu.png) |
+| **Estratégia de envio para cotação de frete (Válida apenas caso a configuração de estoque e cotação para contas franquias estiver ativa)** | É possível escolher entre duas opções de frete. <p><b>Mais barato:</b> a escolha de estoque para fulfillment do pedido é feita com base no menor preço, mas o envio do produto leva mais tempo.</p> <p><b>Mais rápido:</b> a escolha de estoque para fulfillment do pedido é feita com base no menor tempo, mas o envio do produto custa mais caro.</p>| |
+|**Etiqueta de entrega**| Qual o tipo do arquivo da etiqueta de entrega deve ser disponibilizada. | PDF ou ZPL |
+| <b>Mapeamento de Certificados de Homologação (ANATEL, INMETRO, ANVISA e MAPA)</b> | Devido à <a href="https://www.gov.br/anatel/pt-br/assuntos/noticias/marketplaces-adotam-medidas-para-coibir-venda-de-produtos-nao-homologados">determinação da Anatel</a>, produtos da categoria Smartphones e Celulares deverão possuir obrigatoriamente uma <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin">especificação de produto</a> cadastrada com o código de homologação da Anatel para serem comercializados no Magalu Marketplace. Por isso, é necessário preencher este campo com o nome da especificação de produto criada e o código de homologação do produto disponibilizado pela Anatel. Você poderá cadastrar a especificação com o nome que quiser. <p>Se o certificado de homologação não for mapeado, os produtos apresentarão erros de integração. Para cadastrar a especificação, você irá preencher os campos <b>DE e PARA</b> e clicar no botão <b>+</b>.</p>Você pode cadastrar quantas especificações forem necessárias.| <b> CERTIFICADO_1 > ANATEL </b>|
+
+**Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+  <p><b>Exemplo de nome para o novo campo:</b> <code>MGZ_ProductName</code> para nome do produto e <code>MGZ_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+2. Preencha o campo PARA com o nome do novo campo.   `MGZ_ProductName` para nome do produto e `MGZ_ProductDescription` para descrição do produto.    
+3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
 </div>
-
-- **Mapeamento de Certificados de Homologação (Ex: ANATEL, INMETRO, ANVISA e MAPA):** devida à [determinação da Anatel](https://www.gov.br/anatel/pt-br/assuntos/noticias/marketplaces-adotam-medidas-para-coibir-venda-de-produtos-nao-homologados), produtos da categoria Smartphones e Celulares deverão possuir obrigatoriamente uma [especificação de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) cadastrada com o código de homologação da Anatel para serem comercializados no Magazine Luiza. Por isso, é necessário preencher este campo com o nome da especificação de produto criada e o código de homologação do produto disponibilizado pela Anatel.
-
-  Você poderá cadastrar a especificação com o nome que quiser. Se o certificado de homologação não for mapeado, os produtos apresentarão erros de integração.
-
-  Exemplo: `CERTIFICADO_1 > ANATEL`
-
-- **Enviar Kit*:** ao escolher _Não_, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para o Magazine Luiza. Ao habilitar _Sim_, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de _Sim_ para _Não_, SKUs enviados anteriormente para o Magalu não seriam removidos ou sofreriam qualquer alteração.
-
-  <div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para o Magazine Luiza de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos,</b> ao se clicar sobre o SKU.
-</div>
-
-- **Estratégia de envio para cotação de frete (válida apenas caso a configuração de estoque e cotação para contas franquias estiver ativa):** é possível escolher entre duas opções de priorização de frete.
-  - **Mais barato:** a escolha de estoque para fulfillment do pedido é feita com base no menor preço, mas a entrega do produto leva mais tempo.
-  - **Mais rápido:** a escolha de estoque para fulfillment do pedido é feita com base no menor tempo, mas a entrega do produto é mais cara.
-
-- **Usuário API*:** login enviado por email pelo Magalu após a realização do [cadastro no portal da Magazine Luiza](https://marketplace-vendamais.magazineluiza.com.br/).
-
-- **Senha API*:** senha fornecida por email pelo Magalu depois da configuração do [cadastro no portal da Magazine Luiza](https://marketplace-vendamais.magazineluiza.com.br/).
diff --git a/docs/tracks/pt/configure-warranty-in-via-varejo.md b/docs/tracks/pt/configure-warranty-in-via-varejo.md
index fe71d9941..87d85e6f3 100644
--- a/docs/tracks/pt/configure-warranty-in-via-varejo.md
+++ b/docs/tracks/pt/configure-warranty-in-via-varejo.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar garantia da Via Varejo'
+title: 'Configurar garantia da Casas Bahia Marketplace'
 id: 3FFcVmL5Aod6tkFIz9vJmX
 status: PUBLISHED
 createdAt: 2020-10-01T19:13:10.864Z
-updatedAt: 2022-01-24T20:11:25.306Z
-publishedAt: 2022-01-24T20:11:25.306Z
+updatedAt: 2023-11-30T21:39:33.028Z
+publishedAt: 2023-11-30T21:39:33.028Z
 firstPublishedAt: 2020-10-01T20:32:16.599Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,9 +14,9 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-garantia-da-via-varejo
 ---
 
-O cadastro da garantia da Via é obrigatório para algumas [categorias do produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf) na plataforma VTEX. Estas categorias de produto são identificáveis na planilha de referência da Via pela presença do atributo `Garantia` na coluna **Nome do atributo**.
+O cadastro da garantia da Casas Bahia Marketplace é obrigatório para algumas [categorias do produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf) na plataforma VTEX. Estas categorias de produto são identificáveis na planilha de referência da Casas Bahia Marketplace pela presença do atributo `Garantia` na coluna **Nome do atributo**.
 
-O cadastro da garantia é feito através de uma [especificação de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacao-de-produto) com o nome específico: `viavarejogarantia`. Não é necessário incluir o atributo Garantia na planilha de mapeamento da Via - a especificação `viavarejogarantia` é enviada diretamente para o marketplace.
+O cadastro da garantia é feito através de uma [especificação de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacao-de-produto) com o nome específico: `viavarejogarantia`. Não é necessário incluir o atributo Garantia na planilha de mapeamento da Casas Bahia Marketplace - a especificação `viavarejogarantia` é enviada diretamente para o marketplace.
 
 Para cadastrar a garantia, siga os passos a seguir:
 
@@ -28,9 +28,9 @@ Para cadastrar a garantia, siga os passos a seguir:
    * **Nome:** preencha com `viavarejogarantia`.
    * **Texto:** preencha com `Garantia Via Marketplace`.
    * **Tipo:** escolha a opção `Número`.
-   * **Grupo:** sugerimos selecionar o grupo que foi criado chamado `Via Marketplace`.
+   * **Grupo:** sugerimos selecionar o grupo que foi criado chamado `Casas Bahia Marketplace`.
    * **Ativo:** Marque a caixinha.
 
-Com a especificação `viavarejogarantia` disponível para todos os produtos da categoria selecionada, será possível [vincular valores a essa especificação](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin#vincular-as-especificacoes-a-um-produto). Esse valor será o tempo de garantia em meses que serão oferecidos na Via Marketplace, digite um valor numérico entre 1 e 60.
+Com a especificação `viavarejogarantia` disponível para todos os produtos da categoria selecionada, será possível [vincular valores a essa especificação](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin#vincular-as-especificacoes-a-um-produto). Esse valor será o tempo de garantia em meses que serão oferecidos na Casas Bahia Marketplace, digite um valor numérico entre 1 e 60.
 
 Feito isso, a garantia estará configurada em seus produtos e eles estarão disponíveis para venda no marketplace.
diff --git a/docs/tracks/pt/configuring-a-payment-condition.md b/docs/tracks/pt/configuring-a-payment-condition.md
index 65b443299..acc6dd961 100644
--- a/docs/tracks/pt/configuring-a-payment-condition.md
+++ b/docs/tracks/pt/configuring-a-payment-condition.md
@@ -3,8 +3,8 @@ title: 'Configurar uma condição de pagamento'
 id: 6bzGxlz4inf8sKmvZ1c7i3
 status: PUBLISHED
 createdAt: 2019-11-26T17:47:27.426Z
-updatedAt: 2023-03-21T20:02:36.184Z
-publishedAt: 2023-03-21T20:02:36.184Z
+updatedAt: 2024-03-13T21:42:43.233Z
+publishedAt: 2024-03-13T21:42:43.233Z
 firstPublishedAt: 2019-11-26T20:43:48.321Z
 contentType: trackArticle
 productTeam: Financial
@@ -27,17 +27,18 @@ Já as condições de pagamentos são as regras que deverão ser seguidas por um
 Dito isso, podemos partir para a configuração das condições de pagamento em si.
 
 ## Configurações gerais
-Para configurar uma condição de pagamento, primeiro você precisa cadastrar uma afiliação, conforme explicado no documento [Afiliações de Gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway/).
 
-O que não muda de uma condição de pagamento para outra é a necessidade de:
+Para configurar uma condição de pagamento, primeiramente você precisa cadastrar um provedor de pagamento, conforme descrito em [Cadastrar provedores de pagamento e antifraude](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
+
+Independente da condição de pagamento a ser escolhida, as ações abaixo sempre devem ser efetuadas:
 - Definir o nome da regra de acordo com o que ela representa, para ajudar a identificá-la;
 - Ativá-la;
-- Definir por qual afiliação de gateway essa condição será processada;
-- Definir se você vai ou não usar [antifraude](https://help.vtex.com/pt/tutorial/como-configurar-antifraude?locale=pt).
+- Definir por qual provedor de pagamento essa condição será processada;
+- Definir se você vai ou não usar [antifraude](https://help.vtex.com/pt/tutorial/como-configurar-antifraude--tutorials_446).
 
-Além disso, existe a possibilidade de definir se o pagamento será à vista ou em parcelas, com ou sem juros e [condições especiais](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456?locale=pt "condições especiais").
+Além disso, para algumas condições de pagamento pode ser necessário definir se o pagamento será à vista ou em parcelas, com ou sem juros e [condições especiais](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
 
-Como o meio de pagamento que permite todas essas configurações é o **Cartão de Crédito**, siga as etapas abaixo para cada uma dessas configurações.
+Como o __Cartão de Crédito__ é um meio de pagamento que permite aplicar todas essas características, veja abaixo como configurá-lo:
 
 ## À vista
 Aqui, antes de ativar a condição de pagamento, você deve verificar com o gateway ou adquirente se a bandeira ou o meio de pagamento estão disponíveis no sistema deles.
@@ -50,9 +51,9 @@ Feito isso, siga as instruções:
 4. Escolha um dos cartões de crédito como meio de pagamento.
 5. Nomeie a regra no campo **Nome da regra**.
 6. Ative a condição no campo **Status**.
-7. No campo **Processar com a afiliação**, escolha a afiliação que configurou.
+7. No campo **Processar com o provedor**, escolha o provedor configurado anteriormente.
 8. No campo **À vista ou parcelado?**, selecione a opção **À vista**.
-9. Clique no botão **Salvar**.
+9. Clique em **Salvar**.
 
 ## Parcelado
 
@@ -68,11 +69,11 @@ Vale ressaltar que o campo **Cobrança** só será levado em consideração para
 4. Escolha um dos cartões de crédito como meio de pagamento.
 5. Nomeie a regra no campo **Nome da regra**.
 6. Ative a condição no campo **Status**.
-7. No campo **Processar com a afiliação**, escolha a afiliação que configurou. 
+7. No campo **Processar com o provedor**, escolha o provedor configurado anteriormente.
 8. No campo **À vista ou parcelado?**, selecione **parcelado**.
 9. Configure o número de parcelas sequenciais ou individuais no campo **Total de parcelas**.
 10. Defina uma parcela mínima para ser aplicada conforme o valor de cada produto.
-11. Clique no botão **Salvar**.
+11. Clique em **Salvar**.
 
 ### Com juros
 Caso você decida configurar um meio de pagamento que aceite parcelas com juros, esse campo aceita valores com até duas casas decimais. Por exemplo, 1,25 ou 10,89 são valores possíveis.
@@ -83,7 +84,7 @@ Caso você decida configurar um meio de pagamento que aceite parcelas com juros,
 4. Escolha um dos cartões de crédito como meio de pagamento.
 5. Nomeie a regra no campo **Nome da regra**.
 6. Ative a condição no campo **Status**.
-7. No campo **Processar com a afiliação**, escolha a afiliação que configurou.
+7. No campo **Processar com o provedor**, escolha o provedor configurado anteriormente.
 8. No campo **À vista ou parcelado?**, selecione **parcelado**.
 9. Configure o número de parcelas sequenciais ou individuais no campo **Total de parcelas**.
 10. Defina uma parcela mínima para ser aplicada conforme o valor de cada produto.
@@ -91,19 +92,15 @@ Caso você decida configurar um meio de pagamento que aceite parcelas com juros,
 12. Clique no botão **Adicionar juros**.
 13. Digite o valor do juros que deseja aplicar a cada uma das parcelas.
 14. Clique em **Juros composto aplicado. Alterar** para escolher entre juros composto ou simples.
-15. Clique no botão **Salvar**.
+15. Clique em **Salvar**.
 
 ### Parcelamento Automático
 A opção de Parcelamento Automático permite que você configure os detalhes dos parcelamentos diretamente no provedor de pagamento (externamente ao ambiente VTEX).
-Para habilitar esta opção, selecione “Sim” no campo **Usar parcelamento externo** durante a etapa de [configuração de afiliação](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
-
-![parcelamentoautomatico](https://images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/f05aa9a6c8ed312d82a5aa2e51b5fa03/parcelamentoautomaticobr.JPG)
+Para habilitar esta opção, selecione “Sim” no campo **Usar parcelamento externo** durante a etapa de [configuração de provedores](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
 
-<div class="alert alert-warning">
-  Atualmente, somente a afiliação do MercadoPagoV1 permite a função de parcelamento automático.
-</div>
+![parcelamentoautomatico](//images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/f05aa9a6c8ed312d82a5aa2e51b5fa03/parcelamentoautomaticobr.JPG)
 
-Após habilitar o parcelamento automático na afiliação, siga os seguintes passos:
+Após habilitar o parcelamento automático no provedor, siga os seguintes passos:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Clique em **Condições de pagamento**.
@@ -111,9 +108,9 @@ Após habilitar o parcelamento automático na afiliação, siga os seguintes pas
 4. Escolha um dos cartões de crédito como meio de pagamento.
 5. Nomeie a regra no campo **Nome da regra**.
 6. Ative a condição no campo **Status**.
-7. No campo **Processar com a afiliação**, escolha a afiliação que configurou.
+7. No campo **Processar com o provedor**, escolha o provedor configurado anteriormente.
 8. Se desejar utilizar um sistema antifraude, selecione a opção **Usar antifraude**.
 9. Selecione uma opção de antifraude. 
 10. No campo **À vista ou parcelado?**, selecione **Automático**.
-11. Clique no botão **Salvar**.
+11. Clique em **Salvar**.
 
diff --git a/docs/tracks/pt/configuring-banners.md b/docs/tracks/pt/configuring-banners.md
index 1bd934e74..20ed85781 100644
--- a/docs/tracks/pt/configuring-banners.md
+++ b/docs/tracks/pt/configuring-banners.md
@@ -3,8 +3,8 @@ title: 'Configurar Banners'
 id: 4ViKEivLJtJsvpaW0aqIQ5
 status: PUBLISHED
 createdAt: 2019-11-27T16:34:24.404Z
-updatedAt: 2023-03-30T21:35:08.898Z
-publishedAt: 2023-03-30T21:35:08.898Z
+updatedAt: 2024-01-30T21:59:49.330Z
+publishedAt: 2024-01-30T21:59:49.330Z
 firstPublishedAt: 2020-03-05T19:58:30.009Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -28,7 +28,7 @@ Depois de realizar as configurações do banner, você deve adicioná-lo a uma p
   <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
 </div>
 
-![banner-form-pt](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
+![banner-form-pt](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
 
 ## Campos de cadastro do banner
 
@@ -51,6 +51,7 @@ Para cadastrar o banner, é necessário preencher os seguintes campos:
 * **Horário de início**: horário que define o início da disponibilidade do banner.
 * **Data de término**: data que define o término da disponibilidade do banner - o que permite o gestor agendar campanhas futuras, facilitando o seu controle.
 * **Horário de término**: horário que define o término da disponibilidade do banner.
+* **Idiomas:** idiomas aos quais o banner será aplicado. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 
 ### Regras de ativação 
 
@@ -58,7 +59,7 @@ Para cadastrar o banner, é necessário preencher os seguintes campos:
 
 Clique em <i class="fa-solid fa-link"></i> `Preencher a partir de uma URL` para adicionar a URL da página de busca em as regras de ativação serão aplicadas. 
 
-![banner-url-pt](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
+![banner-url-pt](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
 
 Clique em <i class="fas fa-plus"></i> `Adicionar condição` para criar uma regra. Elas podem ser dos seguintes tipos:
 
diff --git a/docs/tracks/pt/configuring-dafiti-connector.md b/docs/tracks/pt/configuring-dafiti-connector.md
index 945df056d..5b06f897e 100644
--- a/docs/tracks/pt/configuring-dafiti-connector.md
+++ b/docs/tracks/pt/configuring-dafiti-connector.md
@@ -3,8 +3,8 @@ title: 'Configuração do conector Dafiti'
 id: 3PV2OACP2E4O4uOKKW2sMg
 status: PUBLISHED
 createdAt: 2018-09-27T17:57:53.647Z
-updatedAt: 2022-01-25T15:51:13.004Z
-publishedAt: 2022-01-25T15:51:13.004Z
+updatedAt: 2024-07-02T19:17:57.983Z
+publishedAt: 2024-07-02T19:17:57.983Z
 firstPublishedAt: 2018-09-27T20:41:13.133Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,11 +16,9 @@ trackSlugPT: configurar-integracao-da-dafiti
 
 A configuração do conector é feita no Admin. Para realizá-la, siga as instruções abaixo:
 
-1. Acesse o Admin.
-2. No módulo _MARKETPLACE_, clique em `Integrações`.
-3. Clique em `Configurações`.
-4. No _card_ da Dafiti, clique em `Integrar`.
-5. Preencha os campos da tela descritos logo abaixo e em seguida, clique no botão `Salvar configuração` (campos marcados com o símbolo * são obrigatórios).
+1. Acesse no Admin **Marketplace > Conexões > Marketplaces e Integrações** ou digite **Marketplaces e Integrações**.
+3. Selecione o marketplace **Dafiti** e clique em `Conectar`.
+4. Preencha os campos da tela descritos logo abaixo e em seguida, clique no botão `Salvar configuração` (campos marcados com o símbolo * são obrigatórios).
 
 - **Integração (se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos)*:** marque _Ativada_ para que a integração comece a operar.
 
@@ -45,11 +43,39 @@ A configuração do conector é feita no Admin. Para realizá-la, siga as instru
 - **Enviar KIT*:** ao escolher _Não_, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Dafiti. Ao habilitar _Sim_, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de _Sim_ para _Não_, SKUs enviados anteriormente para a Dafiti não seriam removidos ou sofreriam qualquer alteração.
 
   <div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a Dafiti de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos,</b> ao se clicar sobre o SKU.
+Com a opção <i>Não</i> ativada, tentativas de envio para a Dafiti de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>Marketplace> Conexões> Produtos,</b> ao se clicar sobre o SKU.
 </div>
 
 - **Nome do SKU*:** determina qual será a regra para nomeação de SKUs no portal da Dafiti. Você deve selecionar uma das combinações disponíveis dos seguintes atributos: _Marca_, _Nome do Produto_ e _Nome do SKU_.
 
-  ![print tela nome exibição produto](https://drive.google.com/uc?export=download&id=1KqEfKd5RCUJve3IZrAd50Ke0nlL2pL4l)
+![print nome exibicao produto es](//images.ctfassets.net/alneenqid6w5/3MiGbDbIXFGiawLcXjji5w/62b3d417ca2cfc58e13f8602c482ff23/print_nome_exibicao_produto.png)
 
 > Exemplo: meu produto é um tênis preto da marca Nike. O _Nome do SKU_ que eu selecionei foi _Marca - Nome do Produto - Nome do SKU_. Assim, o nome que aparecerá no portal da Dafiti será _Nike tênis preto_.
+
+- **NCM:** é a Nomenclatura Comum do Mercosul (NCM), que define a alíquota de impostos comum ao bloco. Para determinados produtos, é necessário informar neste campo o nome único da especificação do produto ou SKU responsável, que contém a informação do NCM no catálogo.
+- **Client Id:** código único atribuído a um seller para acessar a integração.
+- **Client Secret:** código único utilizado para autenticação da integração.
+- **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+  <p><b>Exemplo de nome para o novo campo:</b> <code>DFT_ProductName</code> para nome do produto e <code>DFT_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+2. Preencha o campo PARA com o nome do novo campo. `DFT_ProductName` para nome do produto e `DFT_ProductDescription` para descrição do produto.  
+3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
+</div>
+
diff --git a/docs/tracks/pt/configuring-livelo-price-divergence-rule.md b/docs/tracks/pt/configuring-livelo-price-divergence-rule.md
new file mode 100644
index 000000000..d721220a9
--- /dev/null
+++ b/docs/tracks/pt/configuring-livelo-price-divergence-rule.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar regra de Divergência de valores Livelo'
+id: 4kocvdsHiLcLLcX6eQIVmD
+status: PUBLISHED
+createdAt: 2023-08-10T22:45:01.497Z
+updatedAt: 2024-02-19T19:09:00.244Z
+publishedAt: 2024-02-19T19:09:00.244Z
+firstPublishedAt: 2023-08-11T01:56:55.359Z
+contentType: trackArticle
+productTeam: Channels
+slug: con-gurar-regra-de-divergencia-de-valores-livelo
+locale: pt
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugPT: integracao-livelo
+---
+
+Na integração com marketplaces como a Livelo, por vezes há uma variação entre o preço definido pelo seller e aquele oferecido pelo marketplace, resultando em pedidos fechados com valores diferentes do esperado. Isso pode ocasionar pedidos com erro de divergência de preço.  
+
+No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos**, ou digite **Autorização de pedidos** na barra de busca. A [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (*Owner*) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).  
+
+A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar 
+automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido.    
+
+<div class="alert alert-warning">
+Para que a regra de Divergência de valores seja válida, após a configuração é
+necessário enviar o campo `isCreatedAsync` na API <a href="https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders">Place fulfillment order</a>, independente do tipo de conector utilizado, seja ele, marketplace externo, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outros <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Livelo.  
+</div>  
+
+É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Livelo. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores e o envio do campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders). Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos,** ou digite **Pedidos** na barra de busca.  
+
+<div class="alert alert-warning">
+Incrementos de preço superiores a 20% do valor atual do produto só serão atualizados no sistema se realizados de forma gradual.
+</div>  
diff --git a/docs/tracks/pt/configuring-login-with-facebook.md b/docs/tracks/pt/configuring-login-with-facebook.md
index d5266c453..af490978d 100644
--- a/docs/tracks/pt/configuring-login-with-facebook.md
+++ b/docs/tracks/pt/configuring-login-with-facebook.md
@@ -28,7 +28,7 @@ Após a configuração no Facebook, é preciso configurar essa opção de login
 1.  No módulo de **Configurações da Conta**, acesse a aba de **Autenticação**.
 2.  Clique no botão **Editar** correspondente ao Facebook.
 3.  Preencha os campos com o _Client Id_ e o _Client Secret_ cadastrados no **Facebook**.
-    ![Facebook OAuth PT](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/c07c9d4160e7273a0f5ad2a0cabd1bec/facebook_PT.png)
+    ![Facebook OAuth PT](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/c07c9d4160e7273a0f5ad2a0cabd1bec/facebook_PT.png)
 4.  Clique no botão **Salvar**. 
 5.  Para validar se o login foi feito corretamente, acesse o front-end da sua loja e clique em **Login**.
 6. Aparecerão as opções de login configuradas. Clique na opção **Facebook** e confira se o nome da sua loja é exibido.
diff --git a/docs/tracks/pt/configuring-login-with-google.md b/docs/tracks/pt/configuring-login-with-google.md
index c2afd5735..db80158fc 100644
--- a/docs/tracks/pt/configuring-login-with-google.md
+++ b/docs/tracks/pt/configuring-login-with-google.md
@@ -29,7 +29,7 @@ Após a configuração no Google, é preciso configurar o login na VTEX.
 1.  No módulo de **Configurações da Conta**, acesse a aba de **Autenticações**.
 2.  Clique no botão **Editar** correspondente ao Google.
 3.  Preencha os campos com o _Client Id_ e o _Client Secret_ cadastrados no **Google**.
-    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
+    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
 4.  Clique no botão **Salvar**.
 5.  Para validar se o login foi feito corretamente, acesse o front-end da sua loja e clique em **Login**.
 6. Aparecerão as opções de login configuradas. Clique na opção **Google** e veja se o nome da sua loja é exibido.
diff --git a/docs/tracks/pt/configuring-merchandising-rules.md b/docs/tracks/pt/configuring-merchandising-rules.md
index b27814e2c..544cb91ac 100644
--- a/docs/tracks/pt/configuring-merchandising-rules.md
+++ b/docs/tracks/pt/configuring-merchandising-rules.md
@@ -3,8 +3,8 @@ title: 'Criar Regra de merchandising - Editor manual'
 id: 2FpbarYzsnbg7aZZn3TGF8
 status: PUBLISHED
 createdAt: 2020-04-14T14:10:24.518Z
-updatedAt: 2023-04-03T22:07:36.546Z
-publishedAt: 2023-04-03T22:07:36.546Z
+updatedAt: 2024-01-29T16:58:41.850Z
+publishedAt: 2024-01-29T16:58:41.850Z
 firstPublishedAt: 2020-04-15T00:39:30.807Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
     * **Nome**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
     * **Data de início (opcional)**: agendamento da data a partir da qual a regra de merchandising será aplicada. A data segue o fuso horário UTC-0.
     * **Data de término (opcional)**: agendamento da data em que a regra de merchandising não será mais aplicada às buscas na loja. A data segue o fuso horário UTC-0.
-    * **Idiomas:** idiomas aos quais a regra de merchandising será aplicada.
+    * **Aplicar aos idiomas:** idiomas aos quais a regra de merchandising será aplicada. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 5. Clique em **Editor manual**. Para mais informações sobre cada editor, confira [Tipos de edição](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
 6. Clique em `Próximo`.
 7. Se necessário, altere as informações básicas já definidas sobre a nova regra de merchandising na seção [Informação Geral](#informacao-geral).
@@ -36,6 +36,8 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
 <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
 </div>
 
+## Exemplo
+
 Considere o seguinte exemplo: você quer promover produtos da marca Beautyx durante a semana de Carnaval, ou seja, quando o cliente pesquisar por "sabonete" ou "shampoo", a busca precisa promover produtos da marca. Para isso, a configuração precisa ser feita da seguinte forma:
 
 * **Nome**: Promoção Carnaval
diff --git a/docs/tracks/pt/configuring-payment-connectors.md b/docs/tracks/pt/configuring-payment-connectors.md
index e2923150d..1e9810885 100644
--- a/docs/tracks/pt/configuring-payment-connectors.md
+++ b/docs/tracks/pt/configuring-payment-connectors.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar um conector de pagamentos'
+title: 'Configurar um provedor de pagamentos'
 id: 7pAEMAo4iqNHwYOarZ3zgm
 status: PUBLISHED
 createdAt: 2019-11-12T17:29:10.501Z
-updatedAt: 2023-03-21T20:10:49.512Z
-publishedAt: 2023-03-21T20:10:49.512Z
+updatedAt: 2024-07-29T14:50:02.445Z
+publishedAt: 2024-07-29T14:50:02.445Z
 firstPublishedAt: 2019-11-24T21:05:50.533Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,32 +14,19 @@ trackId: 6GAS7ZzGAm7AGoEAwDbwJG
 trackSlugPT: pagamentos
 ---
 
-O módulo de  **Pagamentos**  permite a configuração de uma série de **conectores**, que  são protocolos de comunicação que sua loja precisa usar para habilitar a transmissão de dados entre ela e adquirentes, subadquirentes ou gateways. 
+O módulo de __Pagamentos__ permite que diversos provedores de pagamento (gateways, adquirentes, subadquirentes, [orquestradores](https://www.y.uno/br), [PSPs](https://en.wikipedia.org/wiki/Payment_service_provider), entre outros) sejam configurados em sua loja. Desta forma, você pode oferecer diferentes métodos e condições de pagamentos aos seus clientes. 
 
-Por exemplo, para que seu web site ofereça um determinado meio de pagamento aos seus clientes, você precisa ativar o **conector** que vai se comunicar com o gateway responsável pelo processamento.
+Quando uma compra é realizada em sua loja e o cliente efetua o pagamento, a transmissão de dados entre a VTEX e o provedor escolhido ocorre por meio de protocolos de comunicação configurados no Admin VTEX.
 
-Outra característica importante é a paridade de conexões. Assim como um meio de pagamento pode se comunicar com vários conectores, um conector pode estabelecer comunicação com vários meios de pagamento. Por conta dessa possibilidade, é necessário que você configure o conector, por meio das **afiliações de gateway**.
+<div class = "alert alert-info">
+  Para verificar quais provedores de pagamento estão disponíveis em sua região e os respectivos artigos de configurações, acesse a <a href="https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp">Lista de provedores de pagamento por país</a>.</p>
+</div>
 
-Uma **afiliações de gateway** é um conjunto de configurações que representa seu contrato com um gateway de pagamento de sua escolha. 
+Veja abaixo um exemplo de como configurar um provedor de pagamento:
 
-Além dos gateways de pagamento, outras afiliações incluem promissórias, adquirentes, e subadquirentes, por exemplo. Com isso é possível decidir por qual gateway de pagamento serão processados os diferentes tipos de transações da sua loja VTEX.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`. 
+3. Digite o provedor de pagamento desejado na barra de busca e clique sobre o seu nome.
+4. Preencha os campos disponíveis conforme informações do provedor de pagamento com o qual você possui contrato.
+5. Clique em `Salvar`.   
 
-O módulo de pagamentos da VTEX dá suporte diversas afiliações com um ou mais Gateways de Pagamento de sua escolha, para processar diferentes formas de pagamento.
-
-Há duas formas para começar a aceitar pagamentos com cartão de crédito: 
-- Afiliar-se a um gateway de pagamento pelo Admin; 
-- Usar as [integrações da VTEX](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-guide) a meios de pagamento.
-
-## Como cadastrar afiliações de gateway pelo Admin
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Clique na opção  **Afiliações de Gateway**.   
-3. Clique no botão de  **+**  para adicionar uma nova afiliação.   
-4. Escolha qual é o seu Gateway de Pagamento.   
-5. Dê um nome à sua afiliação.
-6. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão **Instalar app** e siga as instruções de instalação. Esta mensagem é exibida somente para alguns tipos de afiliações de gateway.   
-7. Preencha os campos disponíveis com os dados do contrato enviados pelo Gateway escolhido.   
-8. Clique no botão  **Salvar**.   
-
-Esse conector deve estar associado a uma condição de pagamento. Para mais informações e exemplos de como receber pagamentos parcelados ou à vista com diferentes afiliações, veja o artigo sobre  [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
-
-Se deseja conferir o passo-a-passo de um conector específico, acesse nossos artigos de [Tutoriais e Soluções](https://help.vtex.com/pt/tutorial/--531cHtUCUi3puRXNDmKziw "Tutoriais e Soluções"), e busque pela palavra-chave desejada. 
diff --git a/docs/tracks/pt/configuring-physical-stores-as-pickup-points.md b/docs/tracks/pt/configuring-physical-stores-as-pickup-points.md
index 5bea7351c..e4309ce7d 100644
--- a/docs/tracks/pt/configuring-physical-stores-as-pickup-points.md
+++ b/docs/tracks/pt/configuring-physical-stores-as-pickup-points.md
@@ -3,8 +3,8 @@ title: 'Lojas físicas como pontos de retirada'
 id: 4hXfgqXxS1lwAfnxgja3xW
 status: PUBLISHED
 createdAt: 2021-08-23T17:04:37.282Z
-updatedAt: 2023-05-31T14:45:23.483Z
-publishedAt: 2023-05-31T14:45:23.483Z
+updatedAt: 2023-07-26T18:51:23.201Z
+publishedAt: 2023-07-26T18:51:23.201Z
 firstPublishedAt: 2021-08-23T17:12:50.884Z
 contentType: trackArticle
 productTeam: Shopping
@@ -20,9 +20,9 @@ Você pode utilizar as lojas físicas da sua marca como pontos de retirada, para
 
 Fica a critério do cliente decidir se deseja que o pedido seja entregue em casa ou se prefere buscá-lo em um ponto de retirada, e qual dos pontos de retirada disponíveis é a melhor opção.
 
-## Pré-requisitos - inStore
+## Pré-requisitos - VTEX Sales App
 
-Verifique os requisitos que sua loja precisa garantir para iniciar a implementação de lojas físicas como pontos de retirada para pedidos realizados no [inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). Para isso, confira o artigo [Pré-requisitos para usar o inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/1wtAanSRA3g2316dw7bw8u "Pré-requisitos para usar o inStore").
+Verifique os requisitos que sua loja precisa garantir para iniciar a implementação de lojas físicas como pontos de retirada para pedidos realizados no [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). Para isso, confira o artigo [Pré-requisitos para usar o VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/1wtAanSRA3g2316dw7bw8u "Pré-requisitos para usar o VTEX Sales App").
 
 ## Configurar lojas físicas como pontos de retirada
 
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md b/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md
index 650048a02..d8fffeb3d 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md
@@ -3,8 +3,8 @@ title: 'Configurar regra de Divergência de valores'
 id: 4rGMP9mEVOKCZCM71yzxnj
 status: PUBLISHED
 createdAt: 2022-01-05T16:09:05.484Z
-updatedAt: 2022-01-05T16:18:18.655Z
-publishedAt: 2022-01-05T16:18:18.655Z
+updatedAt: 2023-08-11T18:26:09.918Z
+publishedAt: 2023-08-11T18:26:09.918Z
 firstPublishedAt: 2022-01-05T16:11:57.454Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,12 +16,13 @@ trackSlugPT: configurar-integracao-da-dafiti
 
 Na integração com marketplaces como a Dafiti, por vezes há uma variação entre o preço definido pelo seller e aquele oferecido pelo marketplace, resultando em pedidos fechados com valores diferentes do esperado. Isso pode ocasionar pedidos com erro de divergência de preço.
 
-No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedidos**, a [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
+No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos**, a [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
 <div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Dafiti.
-</div>
+Para que a regra de Divergência de valores seja válida, após a configuração é
+necessário enviar o campo `isCreatedAsync` na API <a href="https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders">Place fulfillment order</a>, independente do tipo de conector utilizado, seja ele, marketplace externo, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outros <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Dafiti.  
+</div>  
 
-É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Dafiti. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
+É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Dafiti. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos,** ou digite **Pedidos** na barra de busca.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md b/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md
index d5fca6d31..2a2ddb761 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Configurar regra de Divergência de valores'
 id: 1ivH7sJoS771wZFMkaFdpt
 status: PUBLISHED
 createdAt: 2022-01-05T16:18:22.558Z
-updatedAt: 2022-01-05T16:22:48.459Z
-publishedAt: 2022-01-05T16:22:48.459Z
+updatedAt: 2024-03-27T20:43:18.424Z
+publishedAt: 2024-03-27T20:43:18.424Z
 firstPublishedAt: 2022-01-05T16:22:48.459Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,7 +16,7 @@ trackSlugPT: configurar-integracao-do-mercado-livre
 
 Na integração com marketplaces como o Mercado Livre, por vezes há uma variação entre o preço definido pelo seller e aquele oferecido pelo marketplace, resultando em pedidos fechados com valores diferentes do esperado. Isso pode ocasionar pedidos com erro de divergência de preço.
 
-No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedidos**, a [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
+No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos**, a [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
@@ -24,4 +24,4 @@ A regra de Divergência de valores é composta de uma ou mais regras de autoriza
 Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Mercado Livre.
 </div>
 
-É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com o Mercado Livre. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
+É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com o Mercado Livre. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-via.md b/docs/tracks/pt/configuring-price-divergence-rule-via.md
index 6cd26df6c..353028d76 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-via.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-via.md
@@ -3,8 +3,8 @@ title: 'Configurar regra de Divergência de valores'
 id: 6MeJhODLMCnYwUCe18QjzP
 status: PUBLISHED
 createdAt: 2022-01-05T16:01:03.231Z
-updatedAt: 2022-01-05T16:04:18.518Z
-publishedAt: 2022-01-05T16:04:18.518Z
+updatedAt: 2023-11-30T21:12:36.109Z
+publishedAt: 2023-11-30T21:12:36.109Z
 firstPublishedAt: 2022-01-05T16:04:18.518Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,14 +14,14 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-integracao-da-via-varejo
 ---
 
-Na integração com marketplaces como a Via, por vezes há uma variação entre o preço definido pelo seller e aquele oferecido pelo marketplace, resultando em pedidos fechados com valores diferentes do esperado. Isso pode ocasionar pedidos com erro de divergência de preço.
+Na integração com marketplaces como a Casas Bahia Marketplace, por vezes há uma variação entre o preço definido pelo seller e aquele oferecido pelo marketplace, resultando em pedidos fechados com valores diferentes do esperado. Isso pode ocasionar pedidos com erro de divergência de preço.
 
 No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedidos**, a [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
 <div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Via.
+Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Casas Bahia Marketplace.
 </div>
 
-É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Via. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
+É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Casas Bahia Marketplace. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-rappi-price-divergence-rule.md b/docs/tracks/pt/configuring-rappi-price-divergence-rule.md
new file mode 100644
index 000000000..c81057a70
--- /dev/null
+++ b/docs/tracks/pt/configuring-rappi-price-divergence-rule.md
@@ -0,0 +1,29 @@
+---
+title: 'Configurar regra de Divergência de valores rappi'
+id: VoIvBSldeT2A4MuRVMMi1
+status: PUBLISHED
+createdAt: 2024-05-31T20:36:17.323Z
+updatedAt: 2024-05-31T20:51:50.382Z
+publishedAt: 2024-05-31T20:51:50.382Z
+firstPublishedAt: 2024-05-31T20:51:50.382Z
+contentType: trackArticle
+productTeam: Channels
+slug: configurar-regra-de-divergencia-de-valores-rappi
+locale: pt
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugPT: integracao-rappi
+---
+
+Na integração com marketplaces como a Rappi, por vezes há uma variação entre o preço definido pelo seller e aquele oferecido pelo marketplace, resultando em pedidos fechados com valores diferentes do esperado. Isso pode ocasionar pedidos com erro de divergência de preço.  
+
+No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos**, ou digite **Autorização de pedidos** na barra de busca. A [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) permite o controle de pedidos com divergência de preço. Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (*Owner*) ou OMS Full podem configurar essa funcionalidade, conforme o passo a passo descrito em [Configuração da regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).  
+
+A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar 
+automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido.    
+
+<div class="alert alert-warning">
+Para que a regra de Divergência de valores seja válida, após a configuração é
+necessário enviar o campo `isCreatedAsync` na API <a href="https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders">Place fulfillment order</a>, independente do tipo de conector utilizado, seja ele, marketplace externo, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outros <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Rappi.  
+</div>  
+
+É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Rappi. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores e o envio do campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders). Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos,** ou digite **Pedidos** na barra de busca.  
diff --git a/docs/tracks/pt/configuring-redirect.md b/docs/tracks/pt/configuring-redirect.md
index 0c6007160..ce3edea52 100644
--- a/docs/tracks/pt/configuring-redirect.md
+++ b/docs/tracks/pt/configuring-redirect.md
@@ -3,8 +3,8 @@ title: 'Configurar Redirecionamentos'
 id: 4Gd2wLQFbCwTsh8RUDwSoL
 status: PUBLISHED
 createdAt: 2019-11-22T23:40:25.940Z
-updatedAt: 2023-03-30T19:34:08.021Z
-publishedAt: 2023-03-30T19:34:08.021Z
+updatedAt: 2024-06-17T12:20:22.176Z
+publishedAt: 2024-06-17T12:20:22.176Z
 firstPublishedAt: 2019-11-25T17:36:44.905Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -26,7 +26,7 @@ Para configurar um redirecionamento, você precisa seguir os passos a seguir:
 
 Você deve preencher os seguintes campos:
 
-![redirecionamentos-adminv4-PT](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
+![redirecionamentos-adminv4-PT](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
 
 ### Informações gerais
 
@@ -34,6 +34,7 @@ Esta seção apresenta as seguintes informações gerais sobre o redirecionament
 
 - **Nome**: nome do conjunto de regras do redirecionamento criado.
 - **URL de redirecionamento**: endereço de destino que o cliente será encaminhado. Precisa ser cadastrado de forma absoluta - endereço completo - e não relativo. Exemplo: `https://www.loja.com.br/_secure/account/#/orders` ao invés de `_secure/account/#/orders`.
+- **Idiomas:** idiomas aos quais o redirecionamento será aplicado. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 
 ### Regras de ativação
 
diff --git a/docs/tracks/pt/configuring-ship-from-store.md b/docs/tracks/pt/configuring-ship-from-store.md
index c5941ecd0..ce24a4593 100644
--- a/docs/tracks/pt/configuring-ship-from-store.md
+++ b/docs/tracks/pt/configuring-ship-from-store.md
@@ -3,8 +3,8 @@ title: 'Ship From Store'
 id: 50GAmxxFsJoLWqcnMysWdl
 status: PUBLISHED
 createdAt: 2020-06-30T21:36:43.926Z
-updatedAt: 2023-05-31T14:45:10.189Z
-publishedAt: 2023-05-31T14:45:10.189Z
+updatedAt: 2023-07-26T18:44:48.356Z
+publishedAt: 2023-07-26T18:44:48.356Z
 firstPublishedAt: 2020-06-30T21:45:36.187Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugPT: estrategias-de-comercio-unificado
 
 A estratégia de **Ship From Store** se dá quando o cliente deseja receber os produtos em casa e esses produtos partem do estoque de uma loja física. Ou seja, neste cenário, a loja funciona como um mini centro de distribuição.
 
-![35. Setting up Shipping From Store - 1](https://images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
+![35. Setting up Shipping From Store - 1](//images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
 
 Esse tipo de logística ajuda sua operação a reduzir custos e tempo de envio. Isto porque, em vez de contar apenas com os estoques principais - geralmente afastados da zonas centrais das cidades - você passa a ter uma rede mais capilarizada de entrega. 
 
diff --git a/docs/tracks/pt/configuring-synonyms.md b/docs/tracks/pt/configuring-synonyms.md
index a53baeefe..0294d7ecd 100644
--- a/docs/tracks/pt/configuring-synonyms.md
+++ b/docs/tracks/pt/configuring-synonyms.md
@@ -3,8 +3,8 @@ title: 'Configurar Sinônimos'
 id: 3ExbC3QKNF4zH7Gs8jD1cL
 status: PUBLISHED
 createdAt: 2019-11-29T12:04:33.557Z
-updatedAt: 2023-03-30T19:19:37.658Z
-publishedAt: 2023-03-30T19:19:37.658Z
+updatedAt: 2024-01-30T22:46:15.605Z
+publishedAt: 2024-01-30T22:46:15.605Z
 firstPublishedAt: 2020-03-05T19:56:02.826Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,8 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
+<div class = "alert alert-info"> Para relacionar palavras ao produto, é recomendada a utilização da configuração de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV?&utm_source=autocomplete">Sinônimos</a> ao invés das <a href="https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palavras Substitutas</a>, uma vez que os sinônimos possibilitam uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.</div>
+
 Existem duas formas de configurar sinônimos no Admin VTEX: [individualmente](#criar-sinonimos-individualmente) ou por [importação de uma planilha em formato CSV](#importar-csv). Se você precisa cadastrar sinônimos em massa, recomendamos utilizar a planilha. Confira as instruções para cada forma de configuração nas seções a seguir.
 
 A configuração de sinônimos funciona de maneira recursiva. Isso significa que, ao adicionar um segundo sinônimo a outro já existente, ele também se tornará sinônimo do primeiro. 
@@ -32,6 +34,7 @@ Siga o passo a passo para configurar sinônimos individualmente no Admin VTEX:
 4. Preencha os campos referentes ao sinônimo:
    - __Tipo:__ define o tipo de sinônimo. Confira [Tipos de sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) para mais informações.
    - __Termos:__ palavras ou expressões a serem definidas como sinônimos. É necessário teclar `Enter` após cada termo para inserir um outro termo.
+   - **Idiomas:** idiomas aos quais o sinônimo será aplicado. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
    - __Status:__ define se o sinônimo estará ativo ou inativo.
 5. Para finalizar, clique em `Salvar`.
 
@@ -43,9 +46,22 @@ A alteração pode demorar até duas horas para ser aplicada.
 
 ## Importar CSV
 
-Caso existam muitos sinônimos a serem cadastrados, você pode fazer um arquivo .csv e depois importá-lo no Admin VTEX. O arquivo deve conter o seguinte formato, de acordo com os [tipos de sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) escolhidos:
+Caso existam muitos sinônimos a serem cadastrados, você pode fazer um arquivo .csv e depois importá-lo no Admin VTEX. 
+
+Para importar sinônimos por planilha, siga os passos abaixo:
+
+1. Crie um arquivo CSV no formato indicado em [Template da planilha de sinônimos](#template-da-planilha-de-sinonimos).
+2. No Admin VTEX, acesse __Storefront__, ou digite __Storefront__ na barra de busca no topo da página.
+3. Em **Intelligent Search**, clique em **Sinônimos**.
+4. Clique em <i class="fas fa-download"></i> `Importar`.
+5. Arraste o arquivo CSV para a área delimitada ou clique em `escolha um arquivo` para selecionar o arquivo no seu dispositivo.
+6. Clique em `Importar`.
+
+### Template da planilha de sinônimos
 
- - **Unidirecional**: `{termos separados por vírgula};{termos expandidos separados por vírgula};{status}`
+O arquivo deve conter o seguinte formato, de acordo com os [tipos de sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) escolhidos:
+
+ - **Unidirecional**: `{termos separados por vírgula};{termo equivalente};{status}`
 
    __Exemplos:__
 
@@ -56,11 +72,23 @@ Caso existam muitos sinônimos a serem cadastrados, você pode fazer um arquivo
 
    __Exemplos:__
 
-    - `tv,televisão,televisor;true`: ao pesquisar por qualquer um dos ternos, qual produto que contenha um deles será exibido.
-    - `monitor,tela,display;true`: ao pesquisar por qualquer um dos ternos, qualquer produto que contenha um deles será exibido.
+    - `tv,televisão,televisor;true`: ao pesquisar por qualquer um dos termos, qualquer produto que contenha um deles será exibido.
+    - `monitor,tela,display;true`: ao pesquisar por qualquer um dos termos, qualquer produto que contenha um deles será exibido.
 
-Para importar a planilha, siga os passos abaixo:
+#### Lojas Multi-idioma (Beta)
 
-1. No Admin VTEX, acesse __Storefront__, ou digite __Storefront__ na barra de busca no topo da página.
-2. Em **Intelligent Search**, clique em **Sinônimos**.
-3. Clique em `Importar`.
+Lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO) devem seguir o template abaixo para fazer a importação de Sinônimos para idiomas específicos.
+
+- __Unidirecional__: `{termos separados por vírgula};{termo equivalente};{status};{locales separados por vírgula}`
+
+   __Exemplo:__
+   - `smartphone;iphone;true;en-GB`: ao pesquisar por `smartphone` na loja no idioma inglês (`locale = en-GB`), os resultados para `iphone` irão aparecer. Contudo, ao pesquisar por `iphone`, os resultados para `smartphone` não irão aparecer.
+
+- __Bidirecional__: `{termos separados por vírgula};{status};{locales separados por vírgula}`
+
+     __Exemplo:__
+     - `tv,smart tv;true;en-GB`: ao pesquisar por qualquer um dos termos na loja no idioma inglês (`locale = en-GB`), qualquer produto que contenha um desses termos irá aparecer nos resultados da busca.
+
+<div class="alert alert-warning">
+<p> Se o arquivo CSV importado não apresentar o <code>locale</code>, o sinônimo será válido para todos os idiomas disponíveis na loja.</p>
+</div>
diff --git a/docs/tracks/pt/configuring-the-amazon-integration.md b/docs/tracks/pt/configuring-the-amazon-integration.md
index d632fd616..e270fd20d 100644
--- a/docs/tracks/pt/configuring-the-amazon-integration.md
+++ b/docs/tracks/pt/configuring-the-amazon-integration.md
@@ -3,8 +3,8 @@ title: 'Configurar a integração da Amazon'
 id: 5J9CWPIbYQdAegJJWGsxan
 status: PUBLISHED
 createdAt: 2019-02-28T23:11:28.346Z
-updatedAt: 2022-02-03T23:25:36.883Z
-publishedAt: 2022-02-03T23:25:36.883Z
+updatedAt: 2023-09-22T20:17:01.064Z
+publishedAt: 2023-09-22T20:17:01.064Z
 firstPublishedAt: 2019-02-28T23:12:37.347Z
 contentType: trackArticle
 productTeam: Channels
@@ -17,9 +17,8 @@ trackSlugPT: integracao-com-a-amazon
 Uma vez terminadas as etapas de preparo da sua loja na VTEX e na Amazon, é necessário configurar de fato a integração entre ambas. A configuração da integração é feita no Admin da VTEX. Para configurar, siga as instruções abaixo.
 
 1.	Acesse o Admin da VTEX. 
-2.	No módulo *MARKETPLACE*, Clique em **Integrações**.
-3.	Acesse o item **Configurações**.
-4.	No box da Amazon, clique em `Integrar`.
+2.	Clique em __Marketplace > Conexões > Marketplaces e Integrações__.
+4.	No box da Amazon, clique em `Conectar`.
 5.	Preencha os campos da tela descritos logo abaixo e, em seguida, clique no botão `Salvar Configuração` (campos marcados com o símbolo * são obrigatórios).
 
 - **Id do Afiliado*:**  código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestão: MZN. A configuração do conector cria automaticamente o afiliado.
diff --git a/docs/tracks/pt/configuring-the-connector-b2w.md b/docs/tracks/pt/configuring-the-connector-b2w.md
index e46095053..a3f59d84a 100644
--- a/docs/tracks/pt/configuring-the-connector-b2w.md
+++ b/docs/tracks/pt/configuring-the-connector-b2w.md
@@ -3,8 +3,8 @@ title: 'Configurar conector'
 id: 40eYElt1qwIqGeIeum2W4M
 status: PUBLISHED
 createdAt: 2018-09-27T22:25:49.315Z
-updatedAt: 2022-09-06T22:53:13.914Z
-publishedAt: 2022-09-06T22:53:13.914Z
+updatedAt: 2024-07-02T19:23:01.065Z
+publishedAt: 2024-07-02T19:23:01.065Z
 firstPublishedAt: 2018-09-27T22:41:30.135Z
 contentType: trackArticle
 productTeam: Channels
@@ -50,6 +50,31 @@ Com a opção <i>Não</i> ativada, tentativas de envio para a B2W de SKUs cadast
 </div>
 
 - **E-mails Para Notificação de Pedidos Não Integrados*:** digite o endereço eletrônico desejado e, em seguida, clique em `+` sinal de adição. Você pode inserir vários emails para receberem a notificação de [pedidos da B2W que não foram integrados](https://help.vtex.com/pt/tutorial/erros-de-integracao-de-pedidos-da-b2w--2iQqCJIfySN0JsCJkOG2h8).
-- **Etiqueta dos pedidos de B2W Entrega*:** selecione o formato que você deseja para a emissão de etiquetas, se em JSON (JavaScript Object Notation) ou em PDF (Portable Document Format).
+- **Etiqueta dos pedidos de B2W Entrega*:** selecione o formato que você deseja para a emissão de etiquetas, se em JSON (JavaScript Object Notation) ou em PDF (Portable Document Format).  
+- **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação Cadastrar especificações ou campos de produto.  
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+  <p><b>Exemplo de nome para o novo campo:</b> <code>B2W_ProductName</code> para nome do produto e <code>B2W_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   
+Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+2. Preencha o campo PARA com o nome do novo campo.   
+`B2W_ProductName` para nome do produto e `B2W_ProductDescription` para descrição do produto.    
+3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
+</div>
 
 Após salvar a configuração, a integração envia automaticamente todos os produtos associados à política comercial determinada para a SkyHub, a integradora com a B2W.
diff --git a/docs/tracks/pt/configuring-the-connector.md b/docs/tracks/pt/configuring-the-connector.md
index aa212889a..cf014624a 100644
--- a/docs/tracks/pt/configuring-the-connector.md
+++ b/docs/tracks/pt/configuring-the-connector.md
@@ -3,8 +3,8 @@ title: 'Configuração do conector'
 id: wWyl0Njxgs5KfXvxYZJrl
 status: PUBLISHED
 createdAt: 2021-04-14T21:01:49.270Z
-updatedAt: 2021-04-15T21:19:06.543Z
-publishedAt: 2021-04-15T21:19:06.543Z
+updatedAt: 2023-10-13T19:52:02.877Z
+publishedAt: 2023-10-13T19:52:02.877Z
 firstPublishedAt: 2021-04-15T17:41:17.442Z
 contentType: trackArticle
 productTeam: Channels
@@ -17,22 +17,16 @@ trackSlugPT: configurar-integracao-com-o-google-shopping
 A configuração da integração com o Google Shopping é feita no Admin. Para realizá-la, siga as instruções abaixo:
 
 1. Acesse o Admin.
-2. No módulo _Marketplace_, clique em `Integrações`. 
-3. Clique em `Configurações`.
-4. No card do Google Shopping, clique em `Integrar`.
-5. Preencha os campos da tela descritos logo abaixo e em seguida, clique no botão `Salvar configuração` (campos marcados com o símbolo * são obrigatórios).
+2. No módulo Marketplace, clique em __Marketplaces e Integrações.__
+3. Busque __Google Shopping__ na barra de busca e clique no botão `Conectar`.
+4. Preencha os campos da tela descritos logo abaixo e em seguida, clique no botão `Salvar configuração` (campos marcados com o símbolo * são obrigatórios).
 
 - **Integração*:** a integração somente será habilitada se você clicar em _sim._
 - **Ignorar envio do EAN (GTIN):** a opção _sim_ significa que os SKUs serão enviados sem o código de barras. Se o seu produto possuir código de barras, a recomendação é marcar _não, _de forma a incluir essa informação na integração. Caso necessário, veja o artigo [Cadastrar o campo EAN](https://help.vtex.com/pt/tutorial/cadastrar-o-codigo-de-barra-dos-skus-para-o-instore--2jkOdRB4XSMG2ke0uUQIKS#cadastrar-o-campo-ean).
 - **Merchant Id*:** código atribuído ao seu perfil no Google Merchant Center (sequência numérica que aparece no canto superior direito da sua tela quando você acessa sua conta).
 - **Política comercial*:** número da política comercial que definirá o sortimento de catálogo e valores dos itens utilizados na integração.
 - **E-mail da conta Google Merchant*:** email utilizado na criação da conta no Google Merchant Center.
-- **Considerar desconto para pagamento com boleto no preço enviado (Desconto à vista)*:** ao clicar em _sim_, você habilita a modalidade de pagamento por [boleto bancário](https://help.vtex.com/pt/tutorial/como-configurar-boleto-bancario--tutorials_447), ou seja, o preço do produto enviado para o Google Shopping será o valor com esse desconto. Para isso, é necessário que a condição de pagamento com boleto esteja previamente cadastrada.
-<br/>
-<div class="alert alert-warning">
-Esse campo não está disponível nas configurações em inglês e espanhol, portanto recomendamos atenção caso a integração esteja sendo realizada em outros idiomas. Isso se deve ao fato de o boleto ser uma modalidade de pagamento exclusiva do Brasil.
-</div>
-
+- **Aplicar desconto no preço enviado*:** aqui o seller deve escolher qual tipo de desconto deseja enviar ao Google Shopping, __Não aplicar__ (envia o preço cadastrado na plataforma VTEX), __Para meio de pagamento configurado na API de Checkout__ (deve ser selecionado caso o seller tenha configurado o desconto), ou __Maior desconto configurado__.
 - **Remover SKU’s sem estoque*:** ao clicar em _não_, quando um produto não estiver disponível ele não será removido do seu feed do Google Shopping, apenas aparecerá com o status _indisponível_. Caso você clique em _sim_, o SKU removido temporariamente por falta de estoque voltará a aparecer no feed assim que o estoque for reposto.
 - **Merchant Id (Multi-Client):** este campo deve ser usado apenas quando uma conta avançada for configurada no Google Merchant Center. As contas avançadas são criadas para gerenciar vários vendedores e domínios em grande escala. Nestes casos, o preenchimento do campo deverá ser feito com o código atribuído à sua conta avançada no Google Merchant Center, que poderá ser identificado da mesma forma que o Merchant Id (sequência numérica localizada no canto superior direito da tela). Se for do seu interesse, veja mais detalhes no artigo do Google [Mudar para uma conta avançada](https://support.google.com/merchants/answer/188487).
 - **Enviar preço*:** há duas opções, _sem multiplicador de unidade_, no qual seu produto aparece com o valor unitário, e _com multiplicador de unidade,_ quando a cobrança do seu produto for por algum tipo de metragem.
diff --git a/docs/tracks/pt/configuring-the-integration-rappi.md b/docs/tracks/pt/configuring-the-integration-rappi.md
new file mode 100644
index 000000000..065145bc6
--- /dev/null
+++ b/docs/tracks/pt/configuring-the-integration-rappi.md
@@ -0,0 +1,41 @@
+---
+title: 'Configurando a integração'
+id: 1SowuK4iQngOHebFMfizYY
+status: PUBLISHED
+createdAt: 2024-05-31T20:32:15.901Z
+updatedAt: 2024-05-31T20:51:41.392Z
+publishedAt: 2024-05-31T20:51:41.392Z
+firstPublishedAt: 2024-05-31T20:51:41.392Z
+contentType: trackArticle
+productTeam: Channels
+slug: configurando-a-integracao-rappi
+locale: pt
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugPT: integracao-rappi
+---
+
+## Credenciais Livelo Rappi
+
+O primeiro passo para integrar sua loja VTEX à Rappi é ter as credenciais Client Id e Secret, ambas são utilizadas para validar sua integração com o Marketplace. Para obter as suas credenciais, entre em contato através do suporte VTEX.
+
+## Configurações na plataforma VTEX  
+Durante o processo de configuração na plataforma VTEX, tenha sempre em mãos as credenciais fornecidas pela Livelo. O [*AppKey* e *AppToken*](https://developers.vtex.com/docs/guides/authentication), são imprescindíveis para a integração.
+
+### Definição da política comercial na Livelo
+
+Na VTEX, uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio em um canal de venda. Ou seja, é por meio da política comercial que você define as configurações que serão aplicadas aos seus produtos na Livelo.  
+
+Se as mesmas configurações de catálogo, preço e estratégia de envio da sua loja VTEX forem utilizadas no Livelo, não é preciso [criar uma política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) nova, porque uma mesma política comercial pode ser usada para diferentes canais de venda.  
+
+Só será necessário [configurar uma política comercial para Marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404) específica, se você tiver algum dos seguintes objetivos: 
+
+- Oferecer na Rappi uma seleção diferente de produtos.  
+- Disponibilizar uma quantidade de estoque diferente.  
+- Enviar preços diferentes para a Rappi.  
+- Enviar promoções diferentes para a Rappi.  
+- Configurar outras condições de pagamento.  
+- Definir uma [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) diferente.    
+
+Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta preencher o [Formulário de liberação de Política Comercial](https://docs.google.com/forms/d/e/1FAIpQLSe9qCGB_KM_xsV5e9uNe06JE8tMZrWcv6EuHUOmqTiM8oRW7w/viewform). Em caso de dúvidas, entre em contato com o nosso time de Growth Operations em [*Suporte*](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.  
+
+A contratação de política comercial adicional para integrar com [conector nativo, conector certificado(parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex) ou outras lojas VTEX é isenta de taxas.  
diff --git a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index da8eae4ab..03e32466c 100644
--- a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -3,8 +3,8 @@ title: 'Configurar a integração com o FBE no Admin VTEX'
 id: jUtgjBDumr5oGWIU7mVLC
 status: PUBLISHED
 createdAt: 2021-09-30T16:07:29.101Z
-updatedAt: 2021-10-05T21:36:44.675Z
-publishedAt: 2021-10-05T21:36:44.675Z
+updatedAt: 2024-04-17T14:57:04.600Z
+publishedAt: 2024-04-17T14:57:04.600Z
 firstPublishedAt: 2021-09-30T18:49:18.739Z
 contentType: trackArticle
 productTeam: Channels
@@ -40,7 +40,7 @@ Para que a integração funcione corretamente, o recomendável é conceder todas
 10. Clique em `Avançar`.
 11. Na janela aberta, aparecerá uma confirmação de que a integração foi realizada. Clique em `Concluir`.
 
-![gif_pt_v1](https://drive.google.com/uc?export=download&id=1QwtFUWSBxeq1MMSsBnVyzVcWnsS6oeee)
+![gif pt v1](//images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/a677146be91000f363e02c81cd5e6e25/gif_pt_v1.gif)
 
 ## Envio de dados dos produtos para o Facebook Business Extension
 
diff --git a/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 17712ddb9..ea3b50d5b 100644
--- a/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -84,7 +84,7 @@ Depois de preencher o formulário de configuração da integração, você preci
 
 Na página **Set up TikTok For Business** (Configurar o TikTok For Business), ilustrada abaixo, é necessário cumprir as instruções de configuração descritas a seguir.
 
-![set-up-tiktok-for-business](https://images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
+![set-up-tiktok-for-business](//images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
 
 1. Clique na seção **TikTok For Business Account** e verifique se a sua conta está listada.
     * Caso queira conectar outra conta, clique em `Disconnect` e repita a etapa de login descrita em [Conectar a conta do TikTok](#conectar-a-conta-do-tiktok).
diff --git a/docs/tracks/pt/configuring-the-integration.md b/docs/tracks/pt/configuring-the-integration.md
new file mode 100644
index 000000000..841e35504
--- /dev/null
+++ b/docs/tracks/pt/configuring-the-integration.md
@@ -0,0 +1,47 @@
+---
+title: 'Configurando a integração'
+id: HgIbZEzbPr8FQid5MXURQ
+status: PUBLISHED
+createdAt: 2023-08-10T22:33:03.150Z
+updatedAt: 2024-07-26T18:36:22.560Z
+publishedAt: 2024-07-26T18:36:22.560Z
+firstPublishedAt: 2023-08-11T01:56:55.389Z
+contentType: trackArticle
+productTeam: Channels
+slug: configurando-a-integracao
+locale: pt
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugPT: integracao-livelo
+---
+
+## Credenciais Livelo  
+
+O primeiro passo para integrar sua loja VTEX à Livelo é ter as credenciais **AppKey** e **AppToken**, ambas são utilizadas para validar sua integração com o Marketplace.
+
+<div class="alert alert-danger">
+Para obter as suas credenciais e iniciar a integração, entre em contato através com o time de <a href="https://help.vtex.com/pt/support">suporte da VTEX</a>. 
+</div>
+
+Após solicitar as credenciais, o seller pode seguir com as [Configurações da plataforma VTEX](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/HgIbZEzbPr8FQid5MXURQ#conguracoes-na-plataforma-vtex) e configuração da [Regra de divergência.](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/4kocvdsHiLcLLcX6eQIVmD)
+
+## Configurações na plataforma VTEX  
+Durante o processo de configuração na plataforma VTEX, tenha sempre em mãos as credenciais fornecidas pela Livelo. O [*AppKey* e *AppToken*](https://developers.vtex.com/docs/guides/authentication), são imprescindíveis para a integração.
+
+### Definição da política comercial na Livelo
+
+Na VTEX, uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio em um canal de venda. Ou seja, é por meio da política comercial que você define as configurações que serão aplicadas aos seus produtos na Livelo.  
+
+Se as mesmas configurações de catálogo, preço e estratégia de envio da sua loja VTEX forem utilizadas no Livelo, não é preciso [criar uma política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) nova, porque uma mesma política comercial pode ser usada para diferentes canais de venda.  
+
+Só será necessário [configurar uma política comercial para Marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404) específica, se você tiver algum dos seguintes objetivos: 
+
+- Oferecer na Livelo uma seleção diferente de produtos.  
+- Disponibilizar uma quantidade de estoque diferente.  
+- Enviar preços diferentes para a Livelo.  
+- Enviar promoções diferentes para a Livelo.  
+- Configurar outras condições de pagamento.  
+- Definir uma [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) diferente.    
+
+Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta preencher o [Formulário de liberação de Política Comercial](https://docs.google.com/forms/d/e/1FAIpQLSe9qCGB_KM_xsV5e9uNe06JE8tMZrWcv6EuHUOmqTiM8oRW7w/viewform). Em caso de dúvidas, entre em contato com o nosso time de Growth Operations em [*Suporte*](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.  
+
+A contratação de política comercial adicional para integrar com [conector nativo, conector certificado(parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex) ou outras lojas VTEX é isenta de taxas.  
diff --git a/docs/tracks/pt/configuring-the-relevance-feature.md b/docs/tracks/pt/configuring-the-relevance-feature.md
index 8c89d6b39..378e42a38 100644
--- a/docs/tracks/pt/configuring-the-relevance-feature.md
+++ b/docs/tracks/pt/configuring-the-relevance-feature.md
@@ -34,7 +34,7 @@ Há duas áreas de configuração dessa funcionalidade: __Critérios prioritári
   <li><b>Score do Catálogo:</b> 3</li>
 </ul>
 
-![default priority criteria PT](https://images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/092139dbd13f66e3b061fba36704450a/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_19_41.png)
+![default priority criteria PT](//images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/092139dbd13f66e3b061fba36704450a/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_19_41.png)
 
 Para alterar a configuração de Relevância, siga os passos abaixo.
 
@@ -42,7 +42,7 @@ Para alterar a configuração de Relevância, siga os passos abaixo.
 2. Clique em __Configuração de relevância__.
 3. Escolha o critério cujo peso você deseja alterar.
 4. Arraste o indicador para o número desejado, utilizando o cursor, conforme demonstrado na imagem abaixo.
-  ![composicao-criterios-pt](https://images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/008effff0981f64be5a28b8b4cc53063/composicao-criterios-pt.gif)
+  ![composicao-criterios-pt](//images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/008effff0981f64be5a28b8b4cc53063/composicao-criterios-pt.gif)
   Caso você queira mudar a posição de um critério de __Composição de critérios__ para __Critérios prioritários__, basta arrastá-lo pelo ícone <i class="fas fa-bars"></i> para a área superior, conforme demonstrado abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso.
-  ![criterios-prioritarios-pt](https://images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/4cf717f0197e391b10d723dc13bfb57b/criterios-prioritarios-pt.gif)
+  ![criterios-prioritarios-pt](//images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/4cf717f0197e391b10d723dc13bfb57b/criterios-prioritarios-pt.gif)
 5. Para finalizar, clique em __Salvar__.
diff --git a/docs/tracks/pt/contract-termination.md b/docs/tracks/pt/contract-termination.md
new file mode 100644
index 000000000..a0f04cacb
--- /dev/null
+++ b/docs/tracks/pt/contract-termination.md
@@ -0,0 +1,22 @@
+---
+title: 'Rescisão de contrato'
+id: 3TUpFItxp8L1WZAD1JuYfF
+status: PUBLISHED
+createdAt: 2024-02-20T21:47:12.450Z
+updatedAt: 2024-02-22T14:08:21.680Z
+publishedAt: 2024-02-22T14:08:21.680Z
+firstPublishedAt: 2024-02-22T14:08:21.680Z
+contentType: trackArticle
+productTeam: Others
+slug: rescisao-de-contrato
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+A VTEX lamenta a saída de um cliente e compreende que as necessidades e circunstâncias de parceiros de negócios podem mudar. Apesar de lamentar a decisão de rescindir o contrato, a VTEX está comprometida em tornar esse processo o mais simples e transparente possível, para garantir uma transição tranquila.
+
+Para rescindir o contrato com a VTEX, é preciso entrar em contato com o [suporte financeiro](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM#financeiro). Para Brasil, Argentina e Colômbia é preciso seguir as orientações nos seguintes artigos:
+
+- [Solicitar rescisão contratual no Brasil](https://help.vtex.com/pt/tutorial/como-solicitar-sua-rescisao-contratual-no-brasil--frequentlyAskedQuestions_1834)
+- [Solicitar rescisão contratual na Argentina e Colômbia](https://help.vtex.com/pt/tutorial/solicitar-rescisao-contratual-na-argentina-e-colombia--33g6mUoYB9Mf04C06gSU0a)
diff --git a/docs/tracks/pt/corporate-digital-account.md b/docs/tracks/pt/corporate-digital-account.md
index d09c9d8a0..4fa05c674 100644
--- a/docs/tracks/pt/corporate-digital-account.md
+++ b/docs/tracks/pt/corporate-digital-account.md
@@ -1,10 +1,10 @@
 ---
 title: 'Conta digital corporativa'
 id: 3MVAuZJenHAEt8jsgX99GD
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T17:37:52.588Z
-updatedAt: 2023-03-14T22:07:22.796Z
-publishedAt: 2023-03-14T22:07:22.796Z
+updatedAt: 2023-10-05T14:13:52.213Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:48:20.683Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/pt/create-brands.md b/docs/tracks/pt/create-brands.md
index 2e61974c8..84355b65b 100644
--- a/docs/tracks/pt/create-brands.md
+++ b/docs/tracks/pt/create-brands.md
@@ -39,7 +39,7 @@ As informações preenchidas no cadastro podem ser atualizadas a qualquer moment
 
 Para excluir o cadastro de alguma marca, você deve clicar na seta ao lado de  `Alterar ` e selecionar a opção `Excluir`. 
 
-![editar-marca pt](https://images.ctfassets.net/alneenqid6w5/3lz8nIX88GLSISJCiFk1h7/c45e2225e20611d450e91f3e97bc24c9/editar-marca_PT.png)
+![editar-marca pt](//images.ctfassets.net/alneenqid6w5/3lz8nIX88GLSISJCiFk1h7/c45e2225e20611d450e91f3e97bc24c9/editar-marca_PT.png)
 
 ## API
 
diff --git a/docs/tracks/pt/creating-accounts.md b/docs/tracks/pt/creating-accounts.md
index c64ec8d31..de0386c2a 100644
--- a/docs/tracks/pt/creating-accounts.md
+++ b/docs/tracks/pt/creating-accounts.md
@@ -1,10 +1,10 @@
 ---
-title: 'Criar contas no Customer Credit'
+title: 'Criando contas no Customer Credit'
 id: 7FHLd0cmxqqGeEUuc8uioU
 status: PUBLISHED
 createdAt: 2018-11-06T20:24:28.924Z
-updatedAt: 2023-05-12T12:20:09.076Z
-publishedAt: 2023-05-12T12:20:09.076Z
+updatedAt: 2024-02-08T19:08:32.443Z
+publishedAt: 2024-02-08T19:08:32.443Z
 firstPublishedAt: 2018-11-06T21:15:02.053Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,103 +14,82 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugPT: customer-credit-como-comecar
 ---
 
-O próximo passo é criar as contas dos clientes que você deseja oferecer crédito na sua loja. 
+O próximo passo é criar contas para os clientes que você deseja oferecer crédito em sua loja. As contas podem ser criadas de três diferentes formas:
 
-Há três formas de criá-las:
-
-- Via Admin; 
-- Pelo recurso importação em massa;  
-- Via API.
+- [Conta individual (Admin VTEX)](#criar-contas-individualmente)
+- [Múltiplas contas em massa (Admin VTEX)](#criar-multiplas-contas-importacao-em-massa)
+- [Conta individual (Customer Credit API)](#criar-conta-via-api)
 
 <div class="alert alert-info">
-<strong>Atenção</strong>: as contas do Customer Credit não são integradas à base de clientes cadastradas nas entidades do Master Data. As contas devem ser criadas na própria app antes ou depois do usuário ter fechado compras na loja.
+As contas criadas na app do Customer Credit não tem relação ou compartilham dados com a base de clientes cadastrada nas <a href="https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-dados">entidades do Master Data</a> da loja. Para que um cliente possa utilizar o Customer Credit como meio de pagamento, a sua conta deve ser cadastrada pelo lojista na app mesmo que o cliente já possua uma conta na loja. 
 </div>
 
 ## Criar contas individualmente
 
-Caso o usuário prefira, é possível criar várias contas manualmente por meio do Admin.
-
-Confira o passo a passo:
-
-1. Acesse o __Admin__;
-2. Clique no módulo __Customer Credit__;
-3. Em seguida, clique em __Contas__;
-4. Do lado direito da tela, clique no botão azul __“Novo”__;
-5. Selecione o __tipo de documento__ que identificará a conta;
-6. Digite o número do documento no campo __Documento__;
-7. Preencha o campo __Email__;
-8. Defina o __limite crédito__ disponível para a conta;
-9. Clique no botão azul __“Confirmar”__.
-
-O preenchimento do campo email no formulário é obrigatório, pois por meio do email (chave de acesso único ao sistema da VTEX), é possível autenticar o acesso do cliente aos limites de crédito de uma conta. Para saber mais sobre proteção de dados, acesse [Segurança do SmartCheckout](https://help.vtex.com/pt/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB). 
+Para cadastrar um novo cliente no Customer Credit, siga os passos abaixo:
 
-Desse modo, a nova conta será exibida na página inicial da seção “Contas”.
+1. No Admin VTEX, acesse __Aplicativos > Customer Credit > Contas__, ou digite __Contas__ na barra de busca no topo da página.
+2. Na tela de __Contas__, clique no botão `NOVO`.
+3. Em __Identificação__, selecione o __Tipo de documento__ e preencha os campos __Documento__ e __Email__ com as informações do cliente que deseja cadastrar.
+4. Em __Crédito__, insira em os valores de __Limite de crédito (BRL)__ e da __Tolerância__ que deseja disponibilizar ao cliente.
+5. Clique em `Confirmar`.
 
-## Criar contas com a importação em massa
-
-Para criação de contas em massa, o usuário pode usar o recurso importação de arquivo CSV (Comma Separated Value) - um formato de planilha. 
-
-Essa funcionalidade é muito útil visto que possibilita a importação de milhares de contas para o sistema de uma só vez.
+<div class="alert alert-warning">
+  O preenchimento do campo <b>Email</b> é obrigatório, pois a plataforma VTEX utiliza essa informação apra realizar a autenticação de acesso do cliente aos limites de crédito da sua conta. Para mais informações sobre proteção de dados, acesse <a href="https://help.vtex.com/pt/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB">Segurança do SmartCheckout</a>.
+</div>
 
-1. Acesse o __Admin__;
-2. Clique no módulo __Customer Credit__;
-3. Em seguida, clique em __Contas__;
-4. Do lado do botão __“Novo”__, clique na opção __Importar__;
-5. No box que aparecer na tela, selecione a opção __Criar__;
-6. Clique no botão azul __"Continuar"__;
-7. Em seguida, clique na opção __Baixar modelo__.
+A partir deste momento, a nova conta criada será exibida na tela de __Contas__.
 
-Desse modo, você receberá seu computador um modelo de planilha em formato CSV. Você pode encontrá-lo na pasta *Downloads*.
+![CC_criar_conta_1_PT](//images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/d260357ee6bb9151e7dfc99d8fc72e90/CC_criar_conta_1_PT.JPG)
 
-O próximo passo é preencher as colunas listadas no documento com as informações referentes a cada uma das contas que você deseja criar.
+## Criar múltiplas contas (importação em massa)
 
-Ao todo, a tabela conta com 13 colunas que podem ser preenchidas. Entretanto, a única obrigatória é a de e-mail, informação utilizada pelo sistema VTEX para identificar o usuário no SmartCheckout.
+Para criar múltiplas contas ao mesmo tempo (em massa) no Customer Credit, você pode utilizar uma planilha modelo no formato CSV (Comma Separated Value) contendo as informações de cada cliente. Siga os passos abaixo para criar múltiplas contas:
 
-Quando você terminar de preencher a tabela e salvar todas as edições feitas, prossiga com o passo a passo:
+1. No Admin VTEX, acesse __Aplicativos > Customer Credit > Contas__, ou digite __Contas__ na barra de busca no topo da página.
+2. Na tela de __Contas__, clique no botão `IMPORTAR`.
+3. Em __Deseja criar ou atualizar contas?__, selecione a opção __Criar__ e clique em `CONTINUAR`.
+4. Clique em `BAIXAR MODELO`. Um modelo de planilha no formato .csv será enviado para o seu dispositivo (computador, celular ou tablet).
+5. Preencha em cada linha:
+<br>
+<ul>
+  <li>Colunas <b>Email</b>, <b>Document</b> e <b>Document Type</b>:  informações dos clientes.</li>
+  <li>Colunas <b>Credit limit</b> e <b>Tolerance rate</b>: valores disponibilizados para cada cliente. O <b>Tolerance rate</b> deve ser inserido em formato decimal, por exemplo, uma tolerância de 5% deve ser indicada como 0.05.</li>
+</ul>
 
-1. Retorne a seção __Contas__ no Admin;
-2. Novamente, clique na opção __Importar__;
-3. Dessa vez, selecione a opção __Atualizar__ no box;
-4. Clique no botão azul __"Continuar"__;
-5. Insira a planilha no espaço __“Solte aqui seu CSV ou escolha ou arquivo”__;
-6. Clique no botão __“Importar arquivo”__.
+![CC_criar_conta_2_ALL](//images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
 
-Pronto! Assim, suas contas serão criadas e apresentadas na página inicial da seção Contas.
+<blockquote><ui>6. Salve a planilha .csv.</ui>
 
-Em contexto de criar novas contas, você pode conferir todo o histórico de importação. Para isso, basta clicar em “Histórico de importação” na página principal da seção Contas. 
+<blockquote><ui>7. Retorne à tela de <b>Contas</b> e clique novamente no botão <b>IMPORTAR</b>.</ui>
 
-Desse modo, também é possível checar se as importações foram feitas da forma correta. Caso contrário, as correções necessárias serão indicadas na interface. 
+<blockquote><ui>8. Em <b>Deseja criar ou atualizar contas?</b>, selecione a opção <b>Atualizar</b> e clique em <b>CONTINUAR</b>.</ui>
 
-### Atualizar Contas por meio da importação em massa
+<blockquote><ui>9. Insira ou selecione a planilha .csv no espaço <b>Solte aqui seu CSV ou escolha ou arquivo</b>.</ui>
 
-Além disso, você também pode atualizar os dados - e-mail, limite de crédito, documento, document type, status e tolerância - de todas as suas contas de uma só vez por meio do recurso de importação em massa.
+<blockquote><ui>10. Clique no botão <b>IMPORTAR ARQUIVO</b>.</ui>
 
-O processo é semelhante ao de criar contas. Entretanto, aqui considera-se que você já tem o modelo do arquivo CSV baixado na sua máquina.
+A partir deste momento, as novas contas criadas via a planilha .csv estarão disponíveis na tela de __Contas__.
 
-Confira o passo a passo:
+<div class="alert alert-warning">
+  Também é possível rastrear processos anteriores de criação de múltiplas contas, identificando se as contas foram criadas de forma correta. Para verificar estas informações, clique em <b>Histórico de Importação</b> na tela de <b>Contas</b>.
+</div>  
 
-1. Acesse o __Admin__;
-2. Clique no módulo __Customer Credit__;
-3. Em seguida, clique em __Contas__;
-4. Do lado do botão “Novo”, clique na opção __Importar__;
-5. No box que aparecer na tela, selecione a opção __Atualizar__;
-6. Clique no botão azul __"Continuar"__;
-7. Em seguida, insira o arquivo CSV atualizado na *Drop Zone*;
-8. Clique no botão __“Importar Arquivo”__.
+### Atualizar múltiplas contas (importação em massa)
 
-Por fim, espere o *upload* completo da planilha. 
+Para atualizar informações, tais como, documento, tipo de documento, email, limite de crédito e tolerância, em múltiplas contas ao mesmo tempo,você pode também pode utilizar a funcionalidade de importação em massa.  
 
-## Criar contas por API
+O procedimento é semelhante ao de [criar múltiplas contas](#criar-multiplas-contas-importacao-em-massa). Entretanto, você já deve ter a planilha .csv baixada e preenchida em seu dispositivo (computador, celular ou tablet). Siga os passos abaixo para atualizar as informações dos clientes:  
 
-Outra alternativa é criar contas por meio de APIs com o [endpoint](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-accountId- "endpoint") `POST Open or Change Account`.
+1. No Admin VTEX, acesse __Aplicativos > Customer Credit > Contas__, ou digite __Contas__ na barra de busca no topo da página.
+2. Na tela de __Contas__, clique no botão `IMPORTAR`.
+3. Em __Deseja criar ou atualizar contas?__, selecione a opção __Atualizar__ e clique em `CONTINUAR`.
+4. Insira ou selecione a planilha .csv no espaço __Solte aqui seu CSV ou escolha ou arquivo__.
+5. Clique no botão __IMPORTAR ARQUIVO__.
+6. Após a planilha ser carregada no Admin, verifique na tela de __Contas__ se as informações foram atualizadas corretamente nas contas de cada cliente.   
 
-Preencha o body com as seguintes informações:
+## Criar conta via API
 
-    {
-      "id": "id",
-      "creditLimit": "number",
-      "document": "CPF or CNPJ or Other",
-      "email": "email"
-    }
+Você também pode criar contas para seus clientes no Customer Credit por meio do endpoint [POST - Open an account](https://developers.vtex.com/docs/api-reference/customer-credit-api#post-/api/creditcontrol/accounts).
 
-Para mais detalhes, veja a nossa [documentação técnica sobre as APIs de Customer Credit](https://developers.vtex.com/docs/guides/customer-credit-api-overview "documentação técnica sobre as APIs de Customer Credit.").
+Para mais informações sobre os endpoints da API de Customer Credit , acesse [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api#overview).  
diff --git a/docs/tracks/pt/creating-and-editing-users.md b/docs/tracks/pt/creating-and-editing-users.md
index 8c65db722..400ce477d 100644
--- a/docs/tracks/pt/creating-and-editing-users.md
+++ b/docs/tracks/pt/creating-and-editing-users.md
@@ -3,8 +3,8 @@ title: 'Criar e editar usuário'
 id: 5enE0a0glnI0coEj7rRHBA
 status: PUBLISHED
 createdAt: 2019-11-22T15:16:38.307Z
-updatedAt: 2022-08-24T14:23:48.018Z
-publishedAt: 2022-08-24T14:23:48.018Z
+updatedAt: 2024-06-17T15:10:57.072Z
+publishedAt: 2024-06-17T15:10:57.072Z
 firstPublishedAt: 2020-01-13T14:33:11.563Z
 contentType: trackArticle
 productTeam: Identity
@@ -23,7 +23,7 @@ Também é possível cadastrar e gerenciar __usuários__ por meio do módulo Ger
 1.  No módulo Gerenciamento da conta, clique na aba **Usuários**.  
 2.  Clique no botão **Novo usuário**.  
 3.  Preencha o **Email** e o **Nome Completo**.  
-4.  Adicione ou crie os [perfis de acesso](https://help.vtex.com/pt/tutorial/como-criar-perfil-de-acesso/) desejados.  
+4.  Adicione ou crie os [perfis de acesso](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) desejados.  
 5.  Clique no botão **Salvar**.
 
 O usuário irá receber um e-mail confirmando o cadastro, com um link para cadastrar a senha de acesso.
diff --git a/docs/tracks/pt/creating-merchandising-rules-visual-editor.md b/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
new file mode 100644
index 000000000..2593d0593
--- /dev/null
+++ b/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
@@ -0,0 +1,98 @@
+---
+title: 'Criar Regra de merchandising - Editor visual'
+id: 2ejly01m1w28RsZlCKowEr
+status: PUBLISHED
+createdAt: 2024-01-29T17:01:20.082Z
+updatedAt: 2024-02-01T13:22:55.562Z
+publishedAt: 2024-02-01T13:22:55.562Z
+firstPublishedAt: 2024-01-29T17:04:11.061Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: criar-regra-de-merchandising-editor-visual
+locale: pt
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugPT: vtex-intelligent-search
+---
+
+Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) do VTEX Intelligent Search utilizando o [Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), siga os passos abaixo.
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca.
+2. Em **Intelligent Search**, clique em **Regras de merchandising**.
+3. Clique no botão `+ Adicionar`.
+4. Preencha os seguintes campos:
+    * **Nome da regra**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
+    * **Data de início (opcional)**: agendamento da data a partir da qual a regra de merchandising será aplicada. A data segue o fuso horário UTC-0.
+    * **Data de término (opcional)**: agendamento da data em que a regra de merchandising não será mais aplicada às buscas na loja. A data segue o fuso horário UTC-0.
+    * **Aplicar aos idiomas:** idiomas aos quais a regra de merchandising será aplicada. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Clique em **Editor visual**. Para mais informações sobre cada editor, confira [Tipos de edição](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
+6. Clique em `Próximo`.
+7. Defina ao menos um termo de busca ou um filtro para a aplicação da regra de merchandising:
+    * Para definir um termo de busca, digite o termo na barra de busca (item **II** na seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual])).
+    * Para criar um filtro para aplicação da regra de merchandising (item **III** na seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual])), siga o passo a passo descrito na seção [Adicionar filtros e condições](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes).
+8. Se desejar, realize as ações opcionais citadas a seguir para customizar os resultados de busca:
+    * Definir quantidade de itens por linha nos resultados de busca.
+    * Definir quantidade de itens por página nos resultados de busca.
+    * Ocultar produto nos resultados de busca.
+    * Pinar produto, ou seja, fixá-lo nas primeiras posições dos resultados de busca.
+    * Arrastar produto pinado para a posição desejada nos resultados de busca.
+    * Editar configurações iniciais da regra de merchandising, que incluem o nome da regra, as datas de início e de término e, caso a loja utilize o [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO), os idiomas aos quais ela será aplicada.
+
+    Saiba mais sobre essas ações nos itens **IV, V, VI, VIII, IX** e **XI** da seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual]).
+9. Clique em `Salvar`.
+
+<div class="alert alert-info">
+  <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
+</div>
+
+## Ações disponíveis no Editor visual
+
+O Editor visual de regras de merchandising do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
+
+![visual-merch-rules-PT-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir termos de busca para aplicação da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#adicionar-filtros-e-condicoes" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a>
+        para aplicação da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por linha nos resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por página nos resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ocultar produto nos resultados de busca. Produtos ocultos aparecem em cinza com o ícone de olho riscado <i class="far fa-eye-slash"></i> no Editor visual. Para voltar a exibir um produto oculto, passe o cursor sobre ele e clique no ícone de olho <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy"> Ver detalhes do produto. As informações exibidas são:<br /><br />
+	   <ul>
+		  <li class="t-body c-on-base mb5 lh-copy"><strong>Disponível:</strong> indica se o produto está disponível ou não na loja.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Cliques:</strong> quantidade de cliques nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Pedidos:</strong> quantidade de pedidos realizados que incluem o produto nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Receita:</strong> receita que o produto representou nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Data de lançamento:</strong> data de lançamento do produto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Promoção:</strong> indica se o produto faz parte ou não de uma promoção.</li> 
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Desconto:</strong> desconto aplicado sobre o produto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Variedade de matriz disponível: </strong>representa o percentual de SKUs disponíveis do produto. Por exemplo, se um produto tem cinco SKUs e somente três estão disponíveis, a variedade de matriz disponível será 60%, representada como 0.6 neste campo. Se todos os SKUs estiverem disponíveis, o valor do campo será 1.</li>
+	   </ul>
+    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Arrastar produto pinado para a posição desejada nos resultados de busca. É possível apenas arrastar produtos que foram pinados (ação <strong>IX</strong> nesta lista).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Pinar produto, ou seja, fixá-lo nas primeiras posições dos resultados de busca. Ao fixar o produto A e, em seguida, fixar o produto B, eles aparecerão nesta ordem nos resultados de busca, antes dos demais. Para despinar um produto, passe o cursor sobre ele e clique no ícone de alfinete riscado <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar configurações iniciais da regra de merchandising, que incluem o nome da regra, as datas de início e de término e, caso a loja utilize o <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Configurações Multi-idioma (Beta)</a>, os idiomas aos quais ela será aplicada.</li>
+     <li class="t-body c-on-base mb5 lh-copy">Cancelar edição.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Salvar configurações.</li>
+</ol>
+
+### Adicionar filtros e condições
+
+O filtro é um atributo selecionável pré-definido que restringe os resultados da busca, por exemplo, possibilitando filtrar por todos os produtos de uma categoria ou marca, entre outras condições. Você pode adicionar uma ou mais condições a um filtro, conforme ilustrado a seguir.
+
+![filtros-merchrules-pt](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
+
+Para adicionar uma condição no Editor visual, siga o passo a passo abaixo. 
+
+1. Clique em `Filtro`.
+2. Clique em `Adicionar condição`.
+3. Preencha as condições desejadas. As opções disponíveis estão descritas em [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+4. Clique em `Salvar`.
+
+As condições definidas podem funcionar de forma conjunta (`e`) ou de forma alternativa (`ou`).
+
+No menu <i class="far fa-ellipsis-v"></i> de cada condição existente, é possível `Duplicar` ou `Excluir` a condição. Para desativar todas as condições criadas, clique em `Limpar filtros`.
diff --git a/docs/tracks/pt/creating-or-editing-a-page-template.md b/docs/tracks/pt/creating-or-editing-a-page-template.md
index c047e70ec..883d21549 100644
--- a/docs/tracks/pt/creating-or-editing-a-page-template.md
+++ b/docs/tracks/pt/creating-or-editing-a-page-template.md
@@ -41,8 +41,8 @@ Confira o passo a passo a seguir:
 <li><code>admin</code></li>
 </ul></p>
 </div>
-7. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
-8. No canto superior direito, clique no botão __Save Template__.![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
+7. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+8. No canto superior direito, clique no botão __Save Template__.![4 2](//images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
 Para editar um template já existente, o processo é quase idêntico.
 
diff --git a/docs/tracks/pt/creating-regular-promotions.md b/docs/tracks/pt/creating-regular-promotions.md
index 6a086dda3..34b54e045 100644
--- a/docs/tracks/pt/creating-regular-promotions.md
+++ b/docs/tracks/pt/creating-regular-promotions.md
@@ -3,8 +3,8 @@ title: 'Criar Promoção Regular'
 id: 7FjbeZdE2KMwk5L1t98pZI
 status: PUBLISHED
 createdAt: 2020-01-14T13:11:35.010Z
-updatedAt: 2022-12-08T19:33:56.600Z
-publishedAt: 2022-12-08T19:33:56.600Z
+updatedAt: 2024-04-22T13:23:15.737Z
+publishedAt: 2024-04-22T13:23:15.737Z
 firstPublishedAt: 2020-01-22T13:55:43.369Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,7 @@ trackId: 6asfF1vFYiZgTQtOzwJchR
 trackSlugPT: promocoes
 ---
 
+
 Na VTEX, é possível [criar vários tipos de promoção](https://help.vtex.com/pt/tutorial/como-criar-promocoes--tutorials_320#como-criar-promocoes) para cenários diferentes, porém o mais utilizado é a Promoção Regular. Esse tipo de promoção permite que sua loja ofereça descontos de forma poderosa e flexível, combinando múltiplas condições, restrições e benefícios. 
 
 Neste artigo, detalhamos o funcionamento de cada campo durante as etapas de configuração de uma Promoção Regular listadas abaixo.
@@ -27,43 +28,55 @@ Neste artigo, detalhamos o funcionamento de cada campo durante as etapas de conf
 
 Para entender como funciona a implementação das promoções, leia nosso artigo de [Exemplos de Promoção](https://help.vtex.com/pt/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD?&utm_source=autocomplete#).
 
-## 1. Quais os dados gerais desta promoção?
-
-Nesta seção, você deve configurar as informações gerais da sua promoção. Os campos **Nome**, **Validade** e **Qual o tipo e valor do desconto** são de preenchimento obrigatório.
-
-- **Nome**: nome da promoção.
-- **Status**: opção que define se a promoção está ativa ou inativa.
-- **Descrição**: descrição interna da promoção. O objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a promoção é devido à alguma campanha, queima de estoque, etc.
-- **Validade**: data e hora de início e de fim da promoção. Pode ser usada uma data e horário futuros, para que a promoção comece a ser aplicada no site. Caso seja configurada dessa forma, a promoção terá o status de agendada até que a data e horário sejam atingidos. Enquanto a promoção estiver válida, esta terá o status de ativa, e ao término da data e hora definidos o status será alterado para inativo automaticamente.
-- **Usar configurações de recorrência**: essa opção é do tipo caixa de seleção, que quando marcada disponibiliza sete outras caixas de seleção, para que sejam selecionados os dias da semana e as horas do dia em que a promoção será aplicada. Se deseja que a promoção seja aplicada em qualquer dia da semana, não selecione essa opção.
-- **Qual o tipo e valor do desconto?**: seleção que define o tipo e valor do desconto que será aplicado na promoção. Veja as opções de desconto a seguir:
-
-  - **Nominal**: desconto que será concedido ao total do carrinho.
-  - **Frete nominal**: desconto que será concedido ao valor do frete.
-  - **Percentual**: percentual de desconto que será concedido ao valor do produto.
-  - **Preço Máximo por Item**: o preço máximo para cada item da compra será o preço configurado acima.
-  - **Frete percentual**: percentual de desconto que será concedido ao valor do frete. 
-  - **Frete máximo**: valor máximo que o frete poderá assumir. 
-  - **Frete grátis**: desconto total sobre o valor do frete.
-  - **Brinde**: desconto total sobre o valor do produto definido como brinde. Você pode selecionar um ou mais SKUs como brinde ou mais de uma unidade do mesmo SKU. Para definir mais de um brinde, selecione a opção **Ativar multiplicador de brindes** e defina a quantidade desejada. Saiba mais sobre essa opção neste [artigo](https://help.vtex.com/pt/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK#).
-  <div class = "alert alert-info">
-  <p>O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido gratuitamente ao cliente.</p>
- </div>
-
-  - **Desconto nominal baseado em fórmula**: o desconto é calculado com base na fórmula que você pode criar usando como variáveis a soma dos preços de produtos, o frete e a quantidade de itens. Observe que o frete considerado pela fórmula será o menor disponível para o pedido, independentemente da seleção do cliente. O separador decimal deve ser sempre o ponto. Exemplo: se o desconto for 30% do valor total do produto + valor do frete, a fórmula deve ser `(total + freight) * 0.3`. Para obter mais informações sobre a fórmula, leia nossa [documentação](https://help.vtex.com/pt/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
-  - **Valor fidelidade nominal**: crédito que será adicionado no programa de fidelidade da loja. Leia [Promoção regular com valor fidelidade](https://help.vtex.com/pt/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) para mais informações.
-  - **Valor fidelidade percentual**: crédito percentual que será adicionado no programa de fidelidade da loja. Leia [Promoção regular com valor fidelidade](https://help.vtex.com/pt/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) para mais informações.
-  - **Tabela de preços promocionais**: uma tabela de preços pode ser utilizada como promoção. O preço promocional de cada SKU será o preço correspondente na tabela de preços selecionada.
+## **Criar a promoção**
+
+Para criar uma Promoção Regular, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Promoções > Promoções**, ou digite **Promoções** na barra de busca no topo da página.
+2. Clique no botão **Criar promoção**.
+3. Selecione a opção **Regular**.
+4. Preencha os campos da promoção.
+5. Clique em **Salvar**.
+
+# 1. Quais os dados gerais desta promoção?
+
+Nesta seção, você deve configurar as informações gerais da sua promoção. Os campos **Nome**, **Data de expiração** e **Qual o tipo e valor do desconto** são de preenchimento obrigatório.
+
+- **Nome:** nome da promoção. Campo obrigatório.
+- **Status:** opção que define se a promoção está ativa ou inativa.
+- **Descrição:** descrição interna da promoção. O objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a promoção é devido à alguma campanha, queima de estoque, etc.
+- **Data de expiração:** data e hora de início e de fim da promoção. Pode ser usada uma data e/ou horário futuros, para que a promoção comece a ser aplicada no site. Caso seja configurada desta forma, o status da promoção será exibido das seguintes formas:
+    - **Agendada:** antes da data e horário de início selecionados.
+    - **Ativa:** durante o período programado para a promoção.
+    - **Inativa:** após a data e horário de término selecionados.
+- **Usar configurações de recorrência:** ao selecionar esta opção, é permitido realizar configurações de recorrência, por exemplo, dia da semana e horário.
+- **Qual o tipo e valor do desconto?:** permite selecionar uma das opções abaixo:
+     - **Nominal:** desconto que será concedido ao total do carrinho.
+     - **Frete nominal:** desconto que será concedido ao valor do frete.
+     - **Percentual:** percentual de desconto que será concedido ao valor do produto.
+     - **Preço Máximo por Item:** o preço máximo para cada item da compra será o preço configurado acima.
+     - **Frete percentual:** percentual de desconto que será concedido ao valor do frete.
+     - **Frete máximo:** valor máximo que o frete poderá assumir.
+     - **Frete grátis:** desconto total sobre o valor do frete.
+     - **Brinde:** desconto total sobre o valor do produto definido como brinde. Ao selecionar essa opção  é possível indicar o SKU por nome ou ID que será considerado como brinde, escolher se o [multiplicador de brindes](https://help.vtex.com/pt/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK) deve ser ativado e a quantidade máxima de produtos que poderão ser utilizados como brindes na promoção.
+<div class = "alert alert-info">
+O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido gratuitamente ao cliente.
+</div>
 
-- **Destaque nos produtos**: insere uma flag com o nome da promoção, utilizada na vitrine e na página de produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template: `<vtex.cmc:discountHightLight/>`
+   - **Desconto nominal baseado em fórmula:** o desconto é calculado com base na fórmula que você pode criar usando como variáveis a soma dos preços de produtos, o frete e a quantidade de itens. Observe que o frete considerado pela fórmula será o menor disponível para o pedido, independentemente da seleção do cliente. O separador decimal deve ser sempre o ponto. Exemplo: se o desconto for 30% do valor total do produto + valor do frete, a fórmula deve ser (total + freight) * 0.3. Para obter mais informações sobre a fórmula, leia nossa [documentação](https://help.vtex.com/pt/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
+   - **Valor fidelidade nominal:** crédito que será adicionado no programa de fidelidade da loja. Leia [Promoção regular com valor fidelidade](https://help.vtex.com/pt/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) para mais informações.
+   - **Valor fidelidade percentual:** crédito percentual que será adicionado no programa de fidelidade da loja. Leia [Promoção regular com valor fidelidade](https://help.vtex.com/pt/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) para mais informações.
+   - **Tabela de preços promocionais:** uma tabela de preços pode ser utilizada como promoção. O preço promocional de cada SKU será o preço correspondente na tabela de preços escolhida.
+- **Informações adicionais (opcional):** permite  incluir informações adicionais a promoção composto de um nome e valor.
+- **Destaque nos produtos:** insere uma flag com o nome da promoção, utilizada na vitrine e na página do produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template `vtex.cmc:discountHightLight/>`.
 
 <div class = "alert alert-info">
-  <p><b>OBS:</b> Promoções do tipo <b>Nominal</b> só serão apresentadas no carrinho, e não na vitrine ou na página de produto.</p>
+Promoções do tipo Nominal só serão apresentadas no carrinho, e não na vitrine ou na página de produto.
 </div>
 
-### Restringir esta promoção a produtos dos sellers
+## Restringir esta promoção a produtos dos sellers
 
-Nesta seção, é possível definir para quais sellers a promoção será aplicada. Você pode determinar quais sellers serão incluídos ou excluídos do desconto. 
+Nesta seção, é possível definir para quais sellers a promoção será aplicada. Você pode determinar quais sellers serão incluídos ou excluídos do desconto.
 
 - **Iguais a:** selecione os nomes dos sellers desejados para inclui-los.
 - **Diferentes de:** selecione os nomes dos sellers desejados para exclui-los.
@@ -74,93 +87,79 @@ Para que a promoção seja válida para todos os sellers, deixe a seleção vazi
   <p><b>Atenção:</b> não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
 </div>
 
-### Política Comercial
+## Política comercial
 
 Esta seção estabelece as políticas comerciais válidas para a promoção. Você pode incluir ou excluir políticas comerciais do desconto.
 
-- **Iguais a:** selecione as políticas comerciais desejadas inclui-las.
-- **Diferentes de:** selecione as políticas comerciais desejadas exclui-las.
+- **Iguais a:** selecione as políticas comerciais desejadas incluí-las.
+- **Diferentes de:** selecione as políticas comerciais desejadas excluí-las.
 - **Fornecido por mim (Minha loja):** seleção de políticas comerciais com produtos da sua loja. Pode ser selecionada mais de uma política comercial.
 - **Entregue por mim (Lojas de terceiros):** seleção de políticas comerciais em que seus produtos estão de lojas de terceiros. Pode ser selecionada mais de uma política comercial.
 
 Para que a promoção seja válida para todas as políticas comerciais, deixe a seleção vazia.
 
-## 2. Em quais itens esta promoção será aplicada?
+# 2. A quais itens esta promoção será aplicada?
 
-Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
+Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme detalharemos abaixo:
 
-![promocoes-restricao-pt](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
-
-Caso deseje aplicar a promoção a todo o seu catálogo, selecione a opção **Aplicar a todos os produtos**.
-
-Para limitar a sua promoção a produtos específicos, selecione **Aplicar aos seguintes produtos **e, em seguida, preencha os critérios de seleção referentes a **Categorias**, **Marcas**, **Coleções **, **Produtos** e **SKUs**.
+- **Aplicar a todos os produtos:** permite aplicar a promoção a todo o seu catálogo.
+- **Aplicar aos produtos que atendem a todas as restrições a seguir:** permite limitar a sua promoção a produtos específicos, e é necessário preencher os critérios de seleção referentes a **Categorias**, **Marcas**, **Coleções**, **Produtos **e **SKUs**.
+- **Produtos:** permite escolher os produtos no qual a promoção será aplicada. É possível fazer o upload de um arquivo **(.txt)** com os IDs dos produtos.
+- **SKUs:** permite escolher os SKUs dos produtos no qual a promoção será aplicada. É possível fazer o upload de um arquivo **(.txt)** com os SKUs dos produtos.
 
 Você pode incluir ou excluir **Categorias**, **Marcas**, **Coleções**, **Produtos** e **SKUs** da promoção, utilizando os critérios **Iguais a** ou **Diferentes de**.
 
-Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção todos os produtos da categoria **Vestido** cuja marca é **Farm**, com a exceção do produto **Vestido Rosas**.
-
-![exemplo-pt](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/6c40e996aece6e87b82b0bc71a50f3e5/image.png)
-
-Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
-
-<div class = "alert alert-warning">
-<p>Se você selecionar <strong>Aplicar aos seguintes produtos</strong> e não preencher nenhum dos critérios de seleção, a promoção não será cadastrada e a mensagem <strong>Defina os produtos elegíveis ou aplique a todos os produtos</strong> será exibida. Nesse caso, você deve retornar e preencher os critérios de seleção ou optar por <strong>Aplicar a todos os produtos</strong>.</p>
-</div>
-
 Para serem válidos na promoção, os produtos precisam atender a todas as condições cadastradas nesta seção.
 
-## 3. Quais as condições para a promoção ser válida?
+![A quais itens esta promoção será aplicada - PT](//images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/811aa40a0ac7caaf32b2e04e9dd438f6/A_quais_itens.png)
+
+# 3. Quais as condições para a promoção ser válida?
 
 O pedido do cliente deve atender às condições cadastradas nesta seção para ser válido na promoção.
 
-- **Valor mínimo e máximo do pedido:** a promoção será aplicada levando em conta o valor "bruto" do carrinho, sem considerar demais promoções ou frete.
-- **Valor acumulado em compras:** o desconto será concedido caso o total de todas as compras já realizadas pelo cliente, esteja atendendo ao valor preenchido.
-- **Valor do item entre:** o desconto será concedido caso o valor do item estiver atendendo ao intervalo de valores preenchidos.
-- **Preço "de" e "por" são iguais** ou **Preço "de" e "por" são diferentes:**  se refere aos valores do cadastro do produto. Somente uma opção pode ser selecionada.
-- **Restrição de Promoção por BIN:** o desconto será concedido caso o BIN do cartão esteja entre os número preenchidos preenchidos.
-- **Marketing Tags:** campo utilizado para restringir a ativação da promoção caso a compra seja realizada pelo [módulo de Assinaturas da VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#). 
+- **Valor mínimo e máximo do pedido:** a promoção será aplicada levando em conta o valor “bruto” do carrinho, sem considerar demais promoções ou frete.
+* **Valor acumulado em compras:** o desconto será concedido caso o total de todas as compras já realizadas pelo cliente, esteja atendendo ao valor preenchido.
+- **Preço do item entre:** o desconto será concedido caso o valor do item esteja atendendo ao intervalo de valores preenchidos.
+- **Preço "de" e "por" são iguais** ou **Preço "de" e "por" são diferentes:** se refere aos valores do cadastro do produto. Somente uma opção pode ser selecionada.
+- **Usar BIN de restrição:** permite ativar ou desativar a restrição do BIN, limitando quais cartões de créditos poderão ser utilizados na promoção criada. É possível realizar a importação de uma lista de BINs, que deve estar salvo em um arquivo de texto (.txt) com cada BIN descrito em uma linha diferente.
+- **Tags Marketing:** campo utilizado para restringir a ativação da promoção caso a compra seja realizada pelo [módulo de Assinaturas da VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#).
 - **Afiliados:** identificador de pedidos do marketplace. O desconto será aplicado nos afiliados selecionados. Veja o artigo [O que é afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0?locale=pt) para mais informações.
-- **Cluster de clientes:** o desconto será concedido caso o cliente esteja cadastrado no cluster selecionado. É importante destacar que o nome do cluster deve ser exatamente como cadastrado, qualquer erro de grafia impedirá o funcionamento correto da configuração.
-- **Países de entrega**: o desconto será concedido aos países selecionados neste campo.
-- **O CEP de entrega deve:** o desconto será concedido caso o CEP esteja atendendo à regra configurada.
-- **Tipo de frete:** o desconto será concedido caso o tipo de frete escolhido pelo cliente seja o mesmo que o cadastrado na promoção. Esse critério somente será considerado se o efeito da promoção for relativo ao Valor de Frete, ou seja, somente se for um dos seguintes efeitos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis.
-- **Aplicar o desconto somente no frete mais barato:** caso você habilite esta opção, o desconto do frete será aplicado somente no menor valor estimado para o frete. Esta opção já aparece habilitada por padrão, mas você pode desabilitá-la se desejar aplicar o desconto a outros tipos de frete. Leia o artigo [Configurar promoções de frete](https://help.vtex.com/pt/tutorial/configurar-promocoes-de-frete--6Lo5BR61KMiUFAAHGCdgfW) para mais informações. Esse critério somente será considerado se o tipo da promoção for relativo ao valor de frete, ou seja, somente se for um dos seguintes tipos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis.
-- **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente**: a promoção será aplicada somente após o cliente efetivamente selecionar a forma de entrega em questão. Enquanto não for selecionada, ela ficará sem o desconto. Esse critério somente será considerado se o tipo da promoção for relativo ao valor de frete, ou seja, somente se for um dos seguintes tipos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis.
-- **Meio de pagamento:** o desconto será concedido caso a forma de pagamento selecionada pelo cliente seja a mesma cadastrada na promoção. Esse desconto somente será aplicado na finalização da compra, quando o cliente selecionar a mesma forma de pagamento cadastrada.
-
-  <div class = "alert alert-info">
-  <p> Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
- </div>
-
-- **Número de parcelas**: o desconto será concedido caso o número de parcelas selecionadas pelo cliente estiver no intervalo cadastrado. Esse campo não se aplica para a seleção de boleto. 
-
-<div class = "alert alert-warning">
-  <p><b>Atenção</b>: promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.</p>
+- **Cluster de clientes:** o desconto será concedido caso o cliente esteja cadastrado no cluster selecionado. É importante destacar que o nome do cluster deve ser exatamente como cadastrado, qualquer erro de grafia impedirá o funcionamento correto da configuração. Para mais informações, acesse [Criar cluster de clientes](https://help.vtex.com/pt/tutorial/como-criar-um-cluster-de-clientes).
+- **Países de entrega:** o desconto será concedido aos países selecionados neste campo.
+- **O CEP de entrega deve:** o desconto será concedido caso o CEP esteja atendendo à regra configurada. É importante ressaltar que os CEPs que não constam no cadastro não serão elegíveis para ativar a promoção. 
+- **Tipo de frete:** o desconto será concedido caso o tipo de frete escolhido pelo cliente seja o mesmo que o cadastrado na promoção. Esse critério somente será considerado se o efeito da promoção for relativo ao Valor de Frete, ou seja, somente se for um dos seguintes efeitos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis. Importante observar que esta configuração não pode ser combinada com a opção “Aplicar desconto ao frete mais barato”, já que uma opção invalida a outra.
+- **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente:** a promoção será aplicada somente após o cliente efetivamente selecionar a forma de entrega em questão. Enquanto não for selecionada, ela ficará sem o desconto. Esse critério somente será considerado se o tipo da promoção for relativo ao valor de frete, ou seja, somente se for um dos seguintes tipos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis.
+- **Meio de pagamento:** permite escolher se a promoção será aplicada em um ou mais tipos de meios de pagamento selecionados.
+<div class = "alert alert-info">
+Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o [nosso Suporte.](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue)
 </div>
-
-- **Utm_source:** o desconto será concedido caso a navegação seja realizada com as **utm_source** correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas um **utm_source** no checkout.
-- **Utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
+- **Número de parcelas:** o desconto será concedido caso o número de parcelas selecionadas pelo cliente estiver no intervalo cadastrado. Esse campo não se aplica para a seleção de boleto.
+ <div class="alert alert-warning">
+Promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.
+</div>
+- **utm_source:** o desconto será concedido caso a navegação seja realizada com as **utm_source** correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas um **utm_source** no checkout.
+- **utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
 - **Criar cupom a partir das UTMs acima:** cria um cupom a partir das UTMs cadastradas para dar ao cliente acesso à essa promoção sem a necessidade das utms, apenas com o código do cupom.
-- **Utmi_cp:** o desconto será concedido caso a navegação seja realizada com a utmi_cp com o valor cadastrado (case sensitive).
-
-<div class = "alert alert-info">
-     <p>No campo das UTMs coloque somente o valor que as UTMs terão que assumir para ativar a promoção. Não é necessário colocar <i>?utm_source=</i> dentro do campo.</p>
-  </div>
-
+- **utmi_cp:** o desconto será concedido caso a navegação seja realizada com a utmi_cp com o valor cadastrado (case sensitive).
+ <div class = "alert alert-info">
+No campo das UTMs coloque somente o valor que as UTMs terão que assumir para ativar a promoção. Não é necessário colocar ?utm_source= dentro do campo.
+</div>
 - **Apenas na primeira compra:** o desconto só será concedido na primeira compra do cliente.
-- **É um pedido de assinatura**: opção que define que a promoção será aplicada para pedidos de assinatura. Veja as condições a seguir:
-  - **Pedido original**: pedidos que geram as assinaturas, mas ainda não fazem parte dos ciclos de assinatura.
-  - **Pedidos recorrentes**: pedidos que fazem parte dos ciclos de assinatura.
-  - **Filtrar por**: seleção que filtra quais pedidos de assinatura que serão válidos para a promoção.
-      - **Frequência**: seleção da frequência dos pedidos por assinatura - semanal, mensal e anual.
-      - **Número do ciclo**: seleção dos ciclos da assinatura que serão incluídos à promoção. Essa opção é desbloqueada apenas se **Pedidos recorrentes** for selecionado anteriormente.
+- **Aplicar o desconto mesmo se o cliente não estiver logado:** este campo é disponibilizado quando o campo **Apenas na primeira compra** é selecionado. Se este campo é marcado, a promoção será aplicada mesmo que o consumidor não tenha inserido e-mail e senha. Quando desmarcado, a promoção somente será aplicada se o consumidor tiver acessado com e-mail e senha previamente cadastrados.
+- **Pedido de assinatura:** permite selecionar uma das opções abaixo:
+    - **Pedido original:** são pedidos que geram as assinaturas, mas ainda não fazem parte dos ciclos de assinatura.
+    - **Pedidos recorrentes:** são pedidos que fazem parte dos ciclos de assinatura.
+    - **Filtrar por**: permite filtrar quais pedidos de assinatura são válidos para a promoção.
+    - **Frequência:** seleção da frequência dos pedidos por assinatura - semanal, mensal e anual.  Para saber mais informações, acesse [Configurar frequência e data do ciclo de assinatura](https://help.vtex.com/pt/tutorial/como-criar-um-anexo-de-assinatura--2bUuKyPflA8cOGLv8OvaKK#configurar-frequencia-e-data-do-ciclo-de-assinatura).
+   - **Número do ciclo:** permite selecionar os ciclos da assinatura que serão incluídos à promoção. Essa opção é desbloqueada apenas se **Pedidos recorrentes** forem selecionados anteriormente. 
 
-- **Aplicar o desconto mesmo se o cliente não estiver logado:** este campo é disponibilizado quando o campo **Apenas na primeira compra** é selecionado. Se este campo é marcado, a promoção será aplicada mesmo que o consumidor não tenha inserido e-mail e senha. Quando desmarcado, a promoção somente será aplicada se o consumidor tiver acessado com e-mail e senha, previamente cadastrados.
+# 4. Restrições e limitações de uso
 
-## 4. Restrições e limitações de uso
+Nesta seção você encontrará informações importantes sobre quais condições e restrições se aplicam à promoção.
 
-- **Quantas vezes essa promoção será aplicada em sua loja:** limita a quantidade de vezes  em que a promoção será aplicada. Quando a opção **ilimitada** é desmarcada, é disponibilizado um campo para cadastrar a quantidade de vezes que deseja limitar. Uma vez que a promoção já foi criada, essa condição só será aplicada a partir do dia em que foi configurada, não afetando os pedidos realizados anteriormente.
-- **Quantas vezes essa promoção será aplicada em sua loja por cliente:** habilita a quantidade cadastrada acima não mais para quantidade de uso total da promoção, e sim para a quantidade de vezes que cada cliente poderá receber a promoção. Caso o campo acima também esteja selecionado, ele terá uma prioridade maior de atuação que este limite.
-- **Definir quantidade máxima de itens afetados por carrinho**: define quantos itens do carrinho serão afetados pela promoção. Leia [esse artigo](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para saber como configurar o campo.
+- **Quantas vezes essa promoção será aplicada em sua loja:** limita a quantidade de vezes  em que a promoção será aplicada. Quando a opção **ilimitada** é desmarcada, é disponibilizado um campo para cadastrar a quantidade de vezes que deseja limitar. Uma vez que a promoção já foi criada, essa condição só será aplicada a partir do dia em que foi configurada, não afetando os pedidos realizados anteriormente.
+- **Quantas vezes essa promoção será aplicada em sua loja por cliente:** O valor incluído neste campo determina o número máximo de vezes que cada cliente pode se beneficiar da promoção. Consideremos, por exemplo, um limite estabelecido de três utilizações. Caso a promoção seja aplicada três vezes em um único pedido, isso será considerado como uma única utilização em relação ao limite total. Assim, o cliente ainda terá a oportunidade de utilizar a promoção em mais dois pedidos diferentes. É importante destacar que este cálculo é independente da quantidade de vezes que a promoção é utilizada em cada pedido individualmente.
+- **Definir o número máximo de itens elegíveis por carrinho:** define quantos itens do carrinho serão afetados pela promoção. Leia [esse artigo](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para saber como configurar o campo.
 - **Permitir acumular promoções:** permite que mais de uma promoção, independente do tipo de desconto, seja concedida ao mesmo tempo. Saiba mais sobre [como funciona a concorrência de promoções](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270#).
-- **Permitir acumular com preços manuais:**  permite que a promoção seja aplicada a produtos cujos preços foram manualmente inseridos pelo televendas. Para habilitar a funcionalidade de preços manuais, use o endpoint [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration).
+- **Permitir acumular com preços manuais:** permite que a promoção seja aplicada a produtos cujos preços foram manualmente inseridos pelo televendas. Para habilitar a funcionalidade de preços manuais, use o endpoint [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
+
diff --git a/docs/tracks/pt/credit-card-payment-flow.md b/docs/tracks/pt/credit-card-payment-flow.md
index da53eaeb3..df6921564 100644
--- a/docs/tracks/pt/credit-card-payment-flow.md
+++ b/docs/tracks/pt/credit-card-payment-flow.md
@@ -1,10 +1,10 @@
 ---
 title: 'Fluxo de um pagamento por cartão de crédito'
 id: TEYVv2fcVkH7et9n3OnBS
-status: CHANGED
+status: PUBLISHED
 createdAt: 2019-11-12T15:51:05.024Z
-updatedAt: 2020-11-27T19:39:59.301Z
-publishedAt: 2020-02-13T15:38:53.526Z
+updatedAt: 2023-11-01T12:40:40.235Z
+publishedAt: 2023-11-01T12:40:40.235Z
 firstPublishedAt: 2019-11-22T19:30:16.374Z
 contentType: trackArticle
 productTeam: Financial
@@ -28,7 +28,7 @@ Para saber mais sobre os agentes financeiros envolvidos no fluxo de pagamento de
 
 O fluxo completo para pagamento por cartão de crédito na VTEX pode ser descrito pela imagem abaixo. 
 
-![Cartão de crédito - Fluxo básico de um pagamento](https://images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/424c414ed06f81c4edcc676773fd00d9/Fluxo_Cart__o_de_Cr__dito.jpg)
+![Cartão de crédito - Fluxo básico de um pagamento](//images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/424c414ed06f81c4edcc676773fd00d9/Fluxo_Cart__o_de_Cr__dito.jpg)
 
 1. Na tela de Checkout da sua loja, o cliente escolhe o  **Meio de Pagamento**  _cartão de crédito_ para realizar o pagamento de sua compra.  
 
@@ -37,7 +37,7 @@ O fluxo completo para pagamento por cartão de crédito na VTEX pode ser descrit
 3. Com as informações em mãos, o _gateway de pagamentos_ repassa as informações necessárias para o  **Adquirente**, que é responsável pelas liquidações das transações financeiras com os varejistas.  
 
 4. Em posse das informações, o adquirente envia os dados do pagamento para a  **Bandeira**. A bandeira, que conecta o sistema de adquirentes com os bancos emissores. 
-   
+
 5. Por fim, a bandeira envia as informações do pagamento para o **Banco Emissor**. O banco emissor faz a análise de crédito, verifica o limite disponível e então autoriza ou nega o pagamento.
 
 Com a resposta do banco emissor, é realizado o fluxo inverso e o  **Gateway de Pagamentos**  recebe a informação se o pagamento foi aprovado ou negado.
diff --git a/docs/tracks/pt/customer-identification.md b/docs/tracks/pt/customer-identification.md
index 1f6adf697..43db8e9de 100644
--- a/docs/tracks/pt/customer-identification.md
+++ b/docs/tracks/pt/customer-identification.md
@@ -27,7 +27,7 @@ Você pode [configurar quais métodos de identificação deseja habilitar](https
 
 No exemplo da imagem abaixo, estão habilitados Email e CPF.
 
-![31. VTEX Sales App - Product Overview - 2 - PT](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/8923621c44984ce4d58ff7a9ac97a77f/identify-customer-pt.PNG)
+![31. VTEX Sales App - Product Overview - 2 - PT](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/8923621c44984ce4d58ff7a9ac97a77f/identify-customer-pt.PNG)
 
 Basta inserir um desses dados no campo e clicar em `Confirmar`.
 
diff --git a/docs/tracks/pt/customizing-instore.md b/docs/tracks/pt/customizing-instore.md
index 767f9a846..2608c4a7f 100644
--- a/docs/tracks/pt/customizing-instore.md
+++ b/docs/tracks/pt/customizing-instore.md
@@ -3,8 +3,8 @@ title: 'Customizar o VTEX Sales App'
 id: Rby973h1l9tEM4C1YrzwZ
 status: PUBLISHED
 createdAt: 2021-09-16T00:55:10.885Z
-updatedAt: 2023-05-31T16:08:29.389Z
-publishedAt: 2023-05-31T16:08:29.389Z
+updatedAt: 2023-07-24T23:04:49.692Z
+publishedAt: 2023-07-24T23:04:49.692Z
 firstPublishedAt: 2021-09-16T01:00:39.153Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugPT: instore-primeiros-passos-e-configuracoes
 
 A experiência do VTEX Sales App é customizável: você pode aplicar funcionalidades e configurações específicas de acordo com as necessidades do seu negócio, além de adaptar o layout do aplicativo de acordo com a identidade da sua marca.
 
-Para isso, é necessário editar arquivos JavaScript e CSS, conforme descrito no guia para desenvolvedores [How to customize VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/how-to-customize-instore).
+Para isso, é necessário editar arquivos JavaScript e CSS, conforme descrito no guia para desenvolvedores [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app).
 
 <div class="alert alert-warning">
 <p>Somente pessoas com experiência em programação devem customizar o VTEX Sales App, pois alterações incorretas nestes arquivos podem causar erros críticos.</p>
@@ -24,16 +24,16 @@ Para isso, é necessário editar arquivos JavaScript e CSS, conforme descrito no
 
 Veja abaixo as customizações disponíveis para uso no VTEX Sales App. Você pode clicar no nome de cada uma para acessar seu respectivo guia de implementação.
 
-* [Customizar opções de login no VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/customize-instore-login-options): permitir que usuários façam login no VTEX Sales App utilizando a conta do Google ou do Facebook. 
-* [Alterar o idioma do VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/change-instore-language): mudar o idioma do VTEX Sales App para inglês ou espanhol. O idioma padrão é português.
+* [Customizar opções de login no VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app#list-of-customizations): permitir que usuários façam login no VTEX Sales App utilizando a conta do Google ou do Facebook. 
+* [Alterar o idioma do VTEX Sales App](https://developers.vtex.com/docs/guides/change-vtex-sales-app-language): mudar o idioma do VTEX Sales App para inglês ou espanhol. O idioma padrão é português.
 * [Habilitar o campo Observação na tela do pedido](https://developers.vtex.com/vtex-rest-api/docs/enable-the-remarks-field-in-the-order-screen): ativar um campo para armazenar uma informação adicional sobre o pedido. Os dados inseridos neste campo são enviados para o **Gerenciamento de pedidos**.
     * [Habilitar o código do vendedor](https://developers.vtex.com/vtex-rest-api/docs/sales-associate-code): ativar o código do vendedor, ou seja, uma customização adicional do campo **Observação** para transformá-lo em um campo obrigatório onde vendedores precisam inserir seus códigos pessoais durante o fluxo de compra.
 * [Habilitar transferência e captura do carrinho entre dispositivos:](https://developers.vtex.com/vtex-rest-api/docs/enable-cart-transfer-between-devices) permitir que uma compra iniciada em um dispositivo possa ser finalizada em qualquer outro dispositivo presente no fluxo da compra, sem a necessidade de reinserir os produtos no carrinho. Para mais informações, acesse [este artigo](https://help.vtex.com/pt/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/2hlBqxHlxgFo2o4R52pbsk).
 * [Habilitar filtro de pedidos por vendedor:](https://developers.vtex.com/vtex-rest-api/docs/enable-order-filter-by-sales-associate) definir que cada vendedor(a) só pode visualizar os pedidos finalizados por ele(a), em vez de exibir todos os pedidos da loja por padrão.
 * [Forçar disponibilidade de estoque](https://developers.vtex.com/vtex-rest-api/docs/force-stock-availability): permitir a venda de itens que estão indisponíveis no estoque do ecommerce. Por padrão, se um item tem estoque zerado no catálogo da loja, não é possível vendê-lo no VTEX Sales App. Porém, existem casos em que o item está disponível na loja física. Esta customização permite a venda nesses casos.
-* [Configurar impressão de resumo do pedido](https://developers.vtex.com/vtex-rest-api/docs/set-up-the-order-summary-printing): habilitar a impressão de um resumo do pedido ao finalizar o pedido utilizando o VTEX Sales App.
+* [Configurar impressão de resumo do pedido](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app#list-of-customizations): habilitar a impressão de um resumo do pedido ao finalizar o pedido utilizando o VTEX Sales App.
     * [Adicionar texto extra à impressão do pedido](https://developers.vtex.com/vtex-rest-api/docs/add-extra-text-to-the-order-print): adicionar um texto personalizado à impressão do resumo do pedido.
 
 ## Saiba mais
 
-* [How to customize VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/how-to-customize-instore)
+* [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app)
diff --git a/docs/tracks/pt/customizing-styles.md b/docs/tracks/pt/customizing-styles.md
index 9910c9bf4..33698af4b 100644
--- a/docs/tracks/pt/customizing-styles.md
+++ b/docs/tracks/pt/customizing-styles.md
@@ -48,7 +48,7 @@ Vamos fazer algumas alterações no nosso arquivo `style.json`. Podemos mudar um
 
 Agora, vamos ver os resultados "linkando" nossa app:
 
-![style-json](https://images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
+![style-json](//images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
 
 Sucesso! Agora você sabe como personalizar os estilos da sua loja.
 
@@ -98,4 +98,4 @@ Vamos escrever um pouco de CSS, para acrescentar uma linha vermelha sólida:
 ```
 Nosso novo menu de categoria terá agora uma linha vermelha sólida ao longo da parte inferior do nosso menu.
 
-![red-line](https://images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
+![red-line](//images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
diff --git a/docs/tracks/pt/customizing-templates.md b/docs/tracks/pt/customizing-templates.md
index b1407ceaa..22e76abe7 100644
--- a/docs/tracks/pt/customizing-templates.md
+++ b/docs/tracks/pt/customizing-templates.md
@@ -119,6 +119,6 @@ Para adicionar um componente a essa página, basta declarar um novo bloco de pra
 
 Se salvar isso em `store/blocks.json` e rodar `vtex link` em sua loja, você deverá ver uma nova prateleira renderizada ao visitar a home page.
 
-![shelf](https://images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
+![shelf](//images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
 
 Você pode personalizar os blocos declarados pela aplicativo `store-theme` livremente e também declarar novos. Por enquanto, você pode encontrar a documentação para cada componente em seus [repositórios do GitHub](https://github.com/vtex-apps?q=store-components). Lá você encontra as propriedades disponíveis para cada componente.
diff --git a/docs/tracks/pt/dafiti-marketplace.md b/docs/tracks/pt/dafiti-marketplace.md
index d8485105d..6807121e1 100644
--- a/docs/tracks/pt/dafiti-marketplace.md
+++ b/docs/tracks/pt/dafiti-marketplace.md
@@ -3,8 +3,8 @@ title: 'Dafiti marketplace'
 id: 5lAIj7OCqizD5EisLJvatx
 status: PUBLISHED
 createdAt: 2021-05-26T15:09:29.538Z
-updatedAt: 2021-05-26T15:51:04.313Z
-publishedAt: 2021-05-26T15:51:04.313Z
+updatedAt: 2024-06-26T15:28:29.564Z
+publishedAt: 2024-06-26T15:28:29.564Z
 firstPublishedAt: 2021-05-26T15:28:12.852Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,11 +16,11 @@ trackSlugPT: configurar-integracao-da-dafiti
 
 A Dafiti é o maior marketplace de moda e _lifestyle_ da América Latina. Fundada em 2011, já são mais de 10 anos influenciando o varejo online. Em 2020, foram estimados mais de 7,7 milhões de clientes ativos, e o faturamento para o ano ultrapassou 3 bilhões de reais.
 
-![dafiti_marca](https://drive.google.com/uc?export=download&id=1YlSc_8OvOZSAmnvTdRlqMleNkceEh7ok)
+![Dafiti Logo](//images.ctfassets.net/alneenqid6w5/47bytXO1eU2uoKkomqWQaS/c06477ee90fb10a4a6ad1168c5bf9c7a/Dafiti_new_logo.png)
 
 Na Dafiti você pode vender produtos de diversas categorias, tais como roupas, esporte, beleza, decoração, dentre outros. O marketplace concentra cerca de 6 mil marcas e um portifólio de mais de 400 mil produtos.
 
-Por meio do conector nativo da VTEX, você pode anunciar seus produtos na Dafiti de forma simples e eficiente, garantindo mais visibilidade para seus produtos e aumentando suas chances de conversão.
+Por meio do conector nativo da VTEX, você pode anunciar seus produtos na Dafiti de forma simples e eficiente, garantindo mais visibilidade para seus produtos e aumentando suas chances de conversão. 
 
 Atualmente, a Dafiti opera no Brasil, Argentina, Chile e Colômbia. Entretanto, **o conector nativo da VTEX só está disponível para integração com Brasil e Colômbia. **É necessário definir um desses países para configurar a integração, assim a venda dos seus produtos será feita exclusivamente no país escolhido.
 
diff --git a/docs/tracks/pt/dashboard.md b/docs/tracks/pt/dashboard.md
index 744bf4e80..cea29ff01 100644
--- a/docs/tracks/pt/dashboard.md
+++ b/docs/tracks/pt/dashboard.md
@@ -1,10 +1,10 @@
 ---
 title: 'Dashboard'
 id: 7vg42kAdhUQeWBzncsSymN
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-01-24T15:01:36.426Z
-updatedAt: 2023-01-26T12:57:04.230Z
-publishedAt: 2023-01-26T12:57:04.230Z
+updatedAt: 2024-01-05T17:14:37.506Z
+publishedAt: 
 firstPublishedAt: 2023-01-25T14:42:22.919Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugPT: conversational-commerce
 
 Na página Dashboard, os proprietários de lojas VTEX têm acesso às métricas do canal de [Conversational Commerce VTEX](https://help.vtex.com/pt/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/1NwwADrU70v3roPUV7dWxI#). Neste painel, você pode visualizar o desempenho das vendas e os indicadores das sessões, além de filtrá-los pelo período e exportá-los para um arquivo CSV.
 
-![Conversational Commerce Analytics Panel](https://images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/0317999b94d984da418d5126851085d1/Conversational_Commerce_Analytics_Panel_PT.png)
+![Conversational Commerce Analytics Panel](//images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/0317999b94d984da418d5126851085d1/Conversational_Commerce_Analytics_Panel_PT.png)
 
 ## Dados
 
diff --git a/docs/tracks/pt/data-protection-roles.md b/docs/tracks/pt/data-protection-roles.md
new file mode 100644
index 000000000..482237686
--- /dev/null
+++ b/docs/tracks/pt/data-protection-roles.md
@@ -0,0 +1,85 @@
+---
+title: 'Papéis na proteção de dados'
+id: 5f8hTEw3xOALgqzus9VXKd
+status: PUBLISHED
+createdAt: 2024-05-03T16:42:23.883Z
+updatedAt: 2024-05-03T21:10:00.990Z
+publishedAt: 2024-05-03T21:10:00.990Z
+firstPublishedAt: 2024-05-03T16:58:44.285Z
+contentType: trackArticle
+productTeam: Others
+slug: papeis-na-protecao-de-dados
+locale: pt
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugPT: dados-e-privacidade
+---
+
+Para garantir a segurança e a privacidade das informações, existem papéis distintos para a posse, o controle e o tratamento de dados pessoais. Na tabela a seguir, apresentamos cada papel no ecossistema de proteção de dados:
+
+| Papel | Descrição |
+| - | - |
+| Titular de dados | O titular é o dono dos próprios dados pessoais. Por exemplo, o cliente de uma loja é o titular dos seus próprios dados pessoais, os quais ele utiliza para fechar uma compra. |
+| Controlador de dados | Controlador de dados é aquele que decide as finalidades e critérios, conforme as leis de proteção de dados, para utilizar dados pessoais. O controlador também determina de que forma os dados serão utilizados pelos operadores. <br><br> Por exemplo, o controlador de dados é o lojista, já que ele decide quais dados de seus clientes são necessários para fechar uma compra. |
+| Operador de dados | Operador é aquele que trata os dados pessoais conforme instruções do controlador. <br><br> Por exemplo, a VTEX é a operadora que trata os dados dos clientes finais em nome da loja. A VTEX não realiza o tratamento de dados sensíveis de clientes finais por decisão própria, apenas mediante instruções diretas dos responsáveis pela loja. <br><br> Os termos desse tratamento que a VTEX realiza estão definidos no [Data Processing Addendum (DPA)](#data-processing-addendum-dpa). |
+| Suboperador de dados | O suboperador é uma empresa terceira que trata dados pessoais a serviço do operador. O controlador deve ter visibilidade e estar de acordo com a contratação de um suboperador. <br><br> Os provedores de infraestrutura e as afiliadas da VTEX são os suboperadores. Consulte a [lista completa de suboperadores VTEX](https://vtex.com/br-pt/privacy-and-agreements/subprocessors/). |
+
+## Data Processing Addendum (DPA)
+
+O _Data Processing Addendum_ (DPA) é o contrato entre o controlador de dados (lojista) e o operador (VTEX), com o objetivo de regular como a VTEX trata dados pessoais em nome do lojista.
+
+Esse documento é um anexo ao [Master Services Agreement (MSA)](https://vtex.com/br-pt/privacy-and-agreements/agreements/), contrato que regula a relação entre a VTEX e os lojistas e que estabelece as regras para uso da plataforma VTEX e de quaisquer outros serviços ou produtos contratados.
+
+O DPA segue o padrão da [General Data Protection Regulation (GDPR)](https://gdpr-info.eu/), a legislação mais restritiva sobre privacidade de dados.
+
+Nele, você encontrará informações sobre:
+
+* Papéis de operador e controlador.
+* Atendimento a direitos dos titulares de dados.
+* [Suboperadores](https://vtex.com/br-pt/privacy-and-agreements/subprocessors/).
+* Nossas [medidas técnicas e administrativas](https://help.vtex.com/pt/tracks/dados-e-privacidade--4Lc0i0an0DgnEtB0AUwlcq/7ANSqBP5DgOrVVyglo3Lbh) de segurança de dados.
+* Gerenciamento de incidentes de segurança.
+* Limitações de responsabilidades:
+    * Pedidos de auditoria.
+    * Transferência internacional de dados.
+    * Responsabilidade da VTEX em caso de indenizações por incidentes de segurança.
+* Integridade e confidencialidade dos dados pessoais na VTEX.
+
+A VTEX não utiliza dados de clientes finais para nenhuma outra finalidade que não seja realizar operações de ecommerce seguindo as instruções dos lojistas.
+
+O DPA utilizado deve ser o da região específica do titular dos dados (cliente da loja).
+
+<div class="alert alert-warning">
+  <p>Acesse <a href="https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/">Data Processing Addendum - VTEX</a> para visualizar o DPA padrão da VTEX para cada região.</p>
+</div>
+
+## Responsabilidades compartilhadas
+
+Tanto a VTEX quanto os lojistas devem assegurar a segurança dos dados pessoais, cada um em escopo definido. O escopo da VTEX inclui a infraestrutura da plataforma e suas funcionalidades, enquanto o do lojista abrange a frente de loja, configurações no Admin, credenciais de acesso e regulamentos de privacidade locais. Saiba mais nas seções a seguir.
+
+## Responsabilidades da VTEX
+
+A VTEX, como operadora, poderá auxiliar o lojista no atendimento aos direitos de titulares, na realização de relatórios de impacto à privacidade e no aviso de qualquer incidente envolvendo dados pessoais de que tenha conhecimento. Ademais, nos comprometemos com as [medidas técnicas e administrativas](https://help.vtex.com/pt/tracks/dados-e-privacidade--4Lc0i0an0DgnEtB0AUwlcq/7ANSqBP5DgOrVVyglo3Lbh) de segurança previstas no [DPA](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/).
+
+## Responsabilidades de lojistas
+
+Os lojistas, na posição de controladores, são responsáveis por determinar as finalidades e meios de tratamento de dados pessoais. Portanto, lojistas devem instruir a VTEX, nos termos do [DPA](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/), para que os dados pessoais possam ser utilizados na plataforma com a finalidade de realizar operações de ecommerce.
+
+No contexto comercial, cabe ao lojista definir a base legal para utilizar os dados pessoais de clientes (titulares de dados). Bases legais são os casos em que a lei permite o uso de dados pessoais, por exemplo, o consentimento. As bases legais não são aplicáveis à VTEX, pois ela atua apenas como operadora, nos termos do [DPA](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/), e não decide as finalidades de uso dos dados pessoais.
+
+### Regulamentos de privacidade
+
+Cada lojista precisa realizar sua própria avaliação de riscos de privacidade, [relatórios de impacto à privacidade (Privacy Impact Assessments)](https://gdpr-info.eu/issues/privacy-impact-assessment/), políticas de privacidade e medidas técnicas e organizacionais, além de cumprir os direitos dos titulares de dados que estão cadastrados em sua loja. Cabe ao lojista escolher os termos da sua política de privacidade e disponibilizá-la no site, em conformidade com as regulamentações de privacidade locais.
+
+Os lojistas devem implementar suas próprias medidas de segurança e, no caso de incidentes envolvendo dados pessoais, devem notificar as autoridades de proteção de dados e os titulares na forma das leis aplicáveis. Em caso de dúvidas específicas sobre quais leis se aplicam à sua loja, aos seus consumidores finais, ou dúvidas específicas sobre seus negócios, procure orientação de um profissional especializado em proteção de dados pessoais. 
+
+A VTEX prestará assistência ao lojista em algumas dessas obrigações, tais como respostas a direito de titular e notificação de incidentes de segurança, nos termos do [DPA](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/).
+
+### Acesso à plataforma
+
+O lojista desempenha um papel crucial na segurança dos dados, pois suas decisões têm um impacto direto na proteção das informações. Por exemplo, ao conceder acesso à plataforma a determinados usuários ou equipes, ou compartilhar [chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) (appKeys), o lojista influencia a segurança dos dados armazenados nesse ambiente.
+
+Para entender como gerenciar adequadamente credenciais de acesso e garantir a integridade dos dados, consulte os artigos a seguir:
+
+* [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc)
+* [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3)
+* [Chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet)
diff --git a/docs/tracks/pt/define-payment-methods-displayed-on-instore.md b/docs/tracks/pt/define-payment-methods-displayed-on-instore.md
index 89c0cc2b8..cb189b995 100644
--- a/docs/tracks/pt/define-payment-methods-displayed-on-instore.md
+++ b/docs/tracks/pt/define-payment-methods-displayed-on-instore.md
@@ -3,8 +3,8 @@ title: 'Definir meios de pagamento exibidos no VTEX Sales App'
 id: jHQQcyX3WKeUFidwSjmY1
 status: PUBLISHED
 createdAt: 2021-09-27T20:54:02.947Z
-updatedAt: 2023-05-31T16:13:49.825Z
-publishedAt: 2023-05-31T16:13:49.825Z
+updatedAt: 2023-07-05T17:16:01.041Z
+publishedAt: 2023-07-05T17:16:01.041Z
 firstPublishedAt: 2021-09-27T20:57:59.730Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,7 +16,7 @@ trackSlugPT: instore-pagamentos
 
 Agora que a condição de pagamento está criada, é preciso criar os filtros que definem quais meios de pagamento aparecerão no checkout do VTEX Sales App.
 
-Para isso, os desenvolvedores da sua loja precisam customizar um arquivo JavaScript. Leia o guia [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/vtex-rest-api/docs/define-payment-methods-displayed-on-instore) para mais informações.
+Para isso, os desenvolvedores da sua loja precisam customizar um arquivo JavaScript. Leia o guia [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/docs/guides/define-payment-methods-displayed-on-vtex-sales-app) para mais informações.
 
 <div class="alert alert-danger">
 <p>Para habilitar pagamentos via aplicativo do VTEX Sales App, é necessário fazer alterações em um arquivo JavaScript. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas neste arquivo podem causar erros críticos.</p>
diff --git a/docs/tracks/pt/defining-centauro-trade-policy.md b/docs/tracks/pt/defining-centauro-trade-policy.md
index fec2f663c..c8c4a0eee 100644
--- a/docs/tracks/pt/defining-centauro-trade-policy.md
+++ b/docs/tracks/pt/defining-centauro-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definição da política comercial para Centauro'
 id: 2wFjrUoLI3q85r3QZA0Tp
 status: PUBLISHED
 createdAt: 2020-10-20T18:17:56.907Z
-updatedAt: 2022-12-08T20:35:41.540Z
-publishedAt: 2022-12-08T20:35:41.540Z
+updatedAt: 2023-10-19T14:10:07.750Z
+publishedAt: 2023-10-19T14:10:07.750Z
 firstPublishedAt: 2020-10-20T19:51:02.327Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/pt/defining-dafiti-trade-policy.md b/docs/tracks/pt/defining-dafiti-trade-policy.md
index dbda406f7..b5f4b9d3c 100644
--- a/docs/tracks/pt/defining-dafiti-trade-policy.md
+++ b/docs/tracks/pt/defining-dafiti-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definição da política comercial para Dafiti'
 id: 54cBCKrJgqdrm61vxihY1g
 status: PUBLISHED
 createdAt: 2021-02-23T21:32:12.282Z
-updatedAt: 2022-12-08T20:36:49.783Z
-publishedAt: 2022-12-08T20:36:49.783Z
+updatedAt: 2023-08-11T18:10:58.039Z
+publishedAt: 2023-08-11T18:10:58.039Z
 firstPublishedAt: 2021-02-23T21:41:19.622Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,7 +14,7 @@ trackId: 4wF4RBx9ygEkimW6SsKw8i
 trackSlugPT: configurar-integracao-da-dafiti
 ---
 
-Na VTEX, uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio em um canal de venda. Ou seja, é por meio da política comercial que você define as configurações que serão aplicadas aos seus produtos na Netshoes.
+Na VTEX, uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio em um canal de venda. Ou seja, é por meio da política comercial que você define as configurações que serão aplicadas aos seus produtos na Dafiti.
 
 Se as mesmas configurações de catálogo, preço e estratégia de envio da sua loja VTEX forem utilizadas na Dafiti, não é preciso [criar uma política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) nova, pois uma mesma política comercial pode ser usada para diferentes canais de venda.
 
diff --git a/docs/tracks/pt/defining-netshoes-trade-policy.md b/docs/tracks/pt/defining-netshoes-trade-policy.md
index eb582984d..2969e5ab0 100644
--- a/docs/tracks/pt/defining-netshoes-trade-policy.md
+++ b/docs/tracks/pt/defining-netshoes-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definição da política comercial para Netshoes'
 id: 6ESk5Zk32baNfluXbL3Xmz
 status: PUBLISHED
 createdAt: 2021-02-23T20:04:34.470Z
-updatedAt: 2022-12-08T20:35:12.874Z
-publishedAt: 2022-12-08T20:35:12.874Z
+updatedAt: 2023-10-19T14:10:00.314Z
+publishedAt: 2023-10-19T14:10:00.314Z
 firstPublishedAt: 2021-02-23T20:20:32.953Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/pt/defining-the-google-shopping-trade-policy.md b/docs/tracks/pt/defining-the-google-shopping-trade-policy.md
index 9e3213c46..1e65a1f21 100644
--- a/docs/tracks/pt/defining-the-google-shopping-trade-policy.md
+++ b/docs/tracks/pt/defining-the-google-shopping-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Definição da política comercial'
 id: 3AqbcsWrge8zLt0BC5CtGd
 status: PUBLISHED
 createdAt: 2021-04-14T17:58:41.545Z
-updatedAt: 2022-12-08T21:04:01.815Z
-publishedAt: 2022-12-08T21:04:01.815Z
+updatedAt: 2023-10-23T20:22:26.830Z
+publishedAt: 2023-10-23T20:22:26.830Z
 firstPublishedAt: 2021-04-15T17:41:14.352Z
 contentType: trackArticle
 productTeam: Channels
@@ -22,7 +22,7 @@ Será necessário solicitar a criação de uma nova política comercial apenas s
 - Quiser oferecer uma seleção de produtos diferente no Google Shopping.
 - Precisar enviar preços diferentes para o Google Shopping.
 
-Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via ticket em nosso [Suporte](https://help.vtex.com/pt/support) selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
+Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via ticket em nosso [Suporte](https://help.vtex.com/pt/support) selecionando a ção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
 
 A contratação de política comercial adicional para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
 
@@ -30,12 +30,38 @@ A contratação de política comercial adicional para integrar com [conector nat
 
 O [preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu) do seu produto no Google Shopping é determinado na escolha da política comercial. É importante ter atenção a alguns pontos.
 
-Se na sua política comercial existirem preços de/por (que na VTEX chamamos de [preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) e [preço computado](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx#preco-computado)), será enviado para o Google Shopping o preço computado, ou seja, o preço “por”.
+Se na sua política comercial existirem preços de/por (que na VTEX chamamos de [preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) e [preço computado](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx#preco-computado)), o preço computado só será enviado para o Google Shopping caso seja habilitado no campo **“Enviar preços com e sem desconto (De/Por)”.**  
 
-Caso exista uma promoção de desconto à vista (condicionada ao método de pagamento [boleto](https://help.vtex.com/pt/tutorial/como-configurar-boleto-bancario--tutorials_447)), esse benefício será aplicado ao valor do produto antes do envio.
+Para que essas promoções apareçam no Google Shopping, é preciso que os produtos atendam aos seguintes requisitos no Merchant Center:  
+- O preço base ou um valor mais alto precisa ter sido cobrado por 30 dias, consecutivos ou não, nos últimos 200 dias.  
+- O preço base precisa ser válido.  
+- O preço promocional precisa ser inferior ao preço base.  
+- O desconto da promoção precisa ser superior a 5% e inferior a 90% em relação ao preço base.  
+
+Com seus produtos seguindo todos os requisitos acima, a ferramenta aplica o valor promocional previamente configurado na VTEX, nas visualizações do Google Shopping.  
+
+<div class="alert alert-warning">
+  Caso exista uma promoção de desconto à vista (condicionada ao método de pagamento boleto ou pix), esse benefício será aplicado ao valor do produto antes do envio.
+  </div>
+
+## Desconto vinculado ao método de pagamento  
+
+A ativação de desconto atrelado a um método de pagamento é realizada em duas etapas: a [configuração do desconto](#configurar-desconto), do método de pagamento e, posteriormente, a ativação dos descontos na [configuração do conector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl). 
+
+### Configurar desconto
+
+Para configurar um desconto vinculado a um método de pagamento, é necessário seguir as seguintes documentações:  
+
+1. [Set a discount using the checkout API](https://developers.vtex.com/docs/guides/set-a-discount-using-the-checkout-api) para inserir qual o método de pagamento desejado na variável `paymentSystemToCheckFirstInstallment` e simular uma carrinho de comprar para verificar se a forma de pagamento foi atualizada.  
+2.  [Configurar desconto de preço à vista](https://help.vtex.com/pt/tutorial/configurar-desconto-de-preco-a-vista--7Lfcj9Wb5dpYfA2gKkACIt) para atrelar o SKU ao meio de pagamento.  
+3. [Configurar desconto de preço à vista para Google Shooping](https://help.vtex.com/pt/tutorial/configurar-desconto-de-preco-a-vista-para-google-shopping--40K3R5d4NogMvCzIWdWt3e)  
+
+Após seguir essas documentações, a ativação deverá ser realizada através da [Configuração do conector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
 
 <div class="alert alert-warning">
-A ativação de pagamento por boleto é determinada na <a href="https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl">configuração do conector</a>, no campo de preenchimento obrigatório <i/>Considerar desconto para pagamento com boleto no preço enviado (Desconto à vista)</i>.
-</div>
+  Quando há vários sellers vinculados a um produto na sua loja, para o Google Shopping a regra é anunciar a melhor oferta disponível.
+  </div>
 
-Além disso, quando há vários [sellers](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) vinculados a um produto na sua loja, para o Google Shopping a regra é anunciar a melhor oferta disponível.
+  <div class="alert alert-danger">
+  Cada promoção criada só pode ter um método de pagamento atrelado para que o desconto seja enviado ao Google Shooping.
+  </div>
diff --git a/docs/tracks/pt/defining-the-shipping-strategy-via.md b/docs/tracks/pt/defining-the-shipping-strategy-via.md
index b2d63ac0e..62e38776f 100644
--- a/docs/tracks/pt/defining-the-shipping-strategy-via.md
+++ b/docs/tracks/pt/defining-the-shipping-strategy-via.md
@@ -3,8 +3,8 @@ title: 'Definir a Estratégia de Envio'
 id: 69cLhDK7PGOqgSs2EyqMke
 status: PUBLISHED
 createdAt: 2018-09-24T19:51:55.267Z
-updatedAt: 2022-01-18T22:08:54.766Z
-publishedAt: 2022-01-18T22:08:54.766Z
+updatedAt: 2023-11-30T21:11:02.106Z
+publishedAt: 2023-11-30T21:11:02.106Z
 firstPublishedAt: 2018-09-27T22:13:49.998Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,15 +14,15 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-integracao-da-via-varejo
 ---
 
-Para vender seus produtos na Via é preciso determinar uma [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), ou seja, informar qual será a operação de entrega dos seus produtos. A Estratégia de Envio é composta de três etapas logísticas: [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), [Estoque](https://help.vtex.com/pt/tutorial/o-que-e-um-estoque--23kq5gUdY0QOymOu8QSGcA) e [Doca](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj).
+Para vender seus produtos na Casas Bahia Marketplace é preciso determinar uma [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), ou seja, informar qual será a operação de entrega dos seus produtos. A Estratégia de Envio é composta de três etapas logísticas: [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), [Estoque](https://help.vtex.com/pt/tutorial/o-que-e-um-estoque--23kq5gUdY0QOymOu8QSGcA) e [Doca](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj).
 
 É por meio da Doca que a Política de envio (transportadora) é associada ao Estoque da sua loja. A doca é o ponto intermediário entre a transportadora e o armazenamento da sua loja, e através da doca as condições entre transportadora e armazenagem são feitas.
 
-Se for do seu interesse utilizar a mesma Estratégia de Envio definida para sua loja VTEX na integração com a Via, não é necessário criar novas configurações de logística. Se, no entanto, você deseja criar uma Estratégia de Envio específica para o marketplace, é necessário realizar os seguintes passos:
+Se for do seu interesse utilizar a mesma Estratégia de Envio definida para sua loja VTEX na integração com a Casas Bahia Marketplace, não é necessário criar novas configurações de logística. Se, no entanto, você deseja criar uma Estratégia de Envio específica para o marketplace, é necessário realizar os seguintes passos:
 
 1. [Cadastrar Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio), associada à política comercial usada na integração.
 2. [Cadastrar Doca](https://help.vtex.com/pt/tutorial/como-cadastrar-doca--7K3FultD8I2cuuA6iyGEiW), associada à política comercial usada na integração.
 3. [Cadastrar Estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137), associado à Doca criada no passo anterior.
-4. [Associar a política comercial](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404#estrategia-de-envio) da Via à doca.
+4. [Associar a política comercial](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404#estrategia-de-envio) da Casas Bahia Marketplace à doca.
 
 Caso você queira conferir se as configurações foram realizadas corretamente, você pode fazer uma [simulação de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144). O Simulador de envio é uma ferramenta que possibilita checar as condições de entrega do produto sem de fato abrir um pedido.
diff --git a/docs/tracks/pt/delivery.md b/docs/tracks/pt/delivery.md
index 6e0e6987f..20fd31821 100644
--- a/docs/tracks/pt/delivery.md
+++ b/docs/tracks/pt/delivery.md
@@ -18,7 +18,7 @@ Ao clicar em `Ir para a entrega`, o VTEX Sales App mostra os endereços disponí
 
 Alternativamente, o vendedor pode inserir um outro CEP no campo __Informe o CEP para ver as opções de entrega__ e, em seguida, clicar em `Confirmar`.
 
-![instore-entrega-1](https://images.ctfassets.net/alneenqid6w5/6gysul2FyDXGWJRUC0nwJT/2b1d1f617824ddbac290d8ee0c98ead3/entrega-1.png)
+![instore-entrega-1](//images.ctfassets.net/alneenqid6w5/6gysul2FyDXGWJRUC0nwJT/2b1d1f617824ddbac290d8ee0c98ead3/entrega-1.png)
 
 A tela seguinte permite definir escolhas de entrega. Como o VTEX Sales App lida com o estoque de múltiplas lojas, há diversas possibilidades de organização da entrega, dependendo de onde se encontram os produtos do carrinho.
 
@@ -29,19 +29,19 @@ A tela seguinte permite definir escolhas de entrega. Como o VTEX Sales App lida
 - Retirar em uma loja física.
 - Personalizar por item.
 
-![instore-definir-escolhas-de-entrega](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/697cb506db0466fd5f137629ec57458a/entrega-2.png)
+![instore-definir-escolhas-de-entrega](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/697cb506db0466fd5f137629ec57458a/entrega-2.png)
 
 ### Pontos de retirada
 
 Para opções de retirada em loja (pickup point), o sistema seleciona as lojas que têm os itens em estoque e mostra a loja mais próxima ao CEP do cliente, como sugestão. Se o vendedor quiser trocar a loja onde o cliente fará a coleta, basta clicar no botão `Alterar ponto de retirada`.
 
-![31. VTEX Sales App - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/667f6c141be1ad04b2588fc6e28526be/entrega-retirada.png)
+![31. VTEX Sales App - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/667f6c141be1ad04b2588fc6e28526be/entrega-retirada.png)
 
 Ao clicar em `Alterar ponto de retirada`, o vendedor primeiro visualiza o ponto de retirada sugerido pelo sistema. Para ver os demais pontos de retirada disponíveis, é necessário clicar em `Ver todos os pontos de retirada`.
 
-![31. VTEX Sales App - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
+![31. VTEX Sales App - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
 
 O VTEX Sales App mostrará, então, a lista de pontos de retirada, ordenada por menor distância do CEP do cliente. Também é possível escolher o ponto de retirada a partir da visualização no mapa, clicando na aba __Mapa__.
 
-![31. VTEX Sales App - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
+![31. VTEX Sales App - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
 
diff --git a/docs/tracks/pt/detaching-skus-by-specification.md b/docs/tracks/pt/detaching-skus-by-specification.md
index 1803808cd..1c2bd4347 100644
--- a/docs/tracks/pt/detaching-skus-by-specification.md
+++ b/docs/tracks/pt/detaching-skus-by-specification.md
@@ -24,7 +24,7 @@ Essa ferramenta é indicada, principalmente, para lojas de vestuários, pois é
 
 A seguir, confira um exemplo de separação de SKUs por cor. Na imagem abaixo, a sandália em destaque apresenta duas cores diferentes no resultado da pesquisa:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.</p></div>
diff --git a/docs/tracks/pt/digital-wallet-e-wallet.md b/docs/tracks/pt/digital-wallet-e-wallet.md
new file mode 100644
index 000000000..c7678f45b
--- /dev/null
+++ b/docs/tracks/pt/digital-wallet-e-wallet.md
@@ -0,0 +1,24 @@
+---
+title: 'Carteira digital (ewallet)'
+id: 7jLbdfch9Oe2yYbQa9zwE1
+status: PUBLISHED
+createdAt: 2023-06-27T21:10:04.185Z
+updatedAt: 2023-09-26T15:11:41.781Z
+publishedAt: 2023-09-26T15:11:41.781Z
+firstPublishedAt: 2023-06-27T21:47:02.764Z
+contentType: trackArticle
+productTeam: Shopping
+slug: carteira-digital-e-wallet
+locale: pt
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugPT: carteira-digital-e-wallet
+---
+
+Uma carteira digital (também chamada de ewallet) é um ambiente seguro onde podem ser armazenados dados bancários e de cartão de crédito. Essas informações ficam criptografadas no sistema e, quando acessadas pelo seu dono, podem ser usadas para realizar compras na internet.
+
+Comprar com uma carteira digital oferece mais segurança para o usuário, uma vez que ele não precisa informar seus dados de pagamento no checkout da loja. Ao invés disso, o usuário é redirecionado para o ambiente da carteira digital, onde deverá passar por etapas de autenticação.
+
+Com identidade confirmada e meio de pagamento escolhido, a compra volta ao fluxo normal e o pedido é concluído. Algumas carteiras digitais funcionam ainda como subadquirentes, permitindo que mesmo uma pessoa que não tenha cadastro seja capaz de realizar a compra por meio do seu ambiente.
+
+São exemplos de carteiras digitais que podem ser configuradas para a realização de pagamentos na sua loja VTEX: **Carteira Google**, **[Apple Pay](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-apple-pay--5L3NWMgvdKswWQa6eIc008),** **Samsung Pay, Paypal**, **Mercado** **Pago**, **PagSeguro**, **Stelo**, entre outras.
+
diff --git a/docs/tracks/pt/enabling-2-factor-authentication-login.md b/docs/tracks/pt/enabling-2-factor-authentication-login.md
index c23e34f79..369f07051 100644
--- a/docs/tracks/pt/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/pt/enabling-2-factor-authentication-login.md
@@ -32,7 +32,7 @@ Há duas opções de autenticação:
 - __App Google__ (chave gerada por aplicativo de autenticação)
 - __Mensagem SMS__ (chave enviada por mensagem de texto)
 
-![2FA - Select - PT](https:https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
+![2FA - Select - PT](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
 
 <div class="alert alert-warning">
   Recomendamos o uso de <a href="#habilitar-o-2fa-por-aplicativo">aplicativo de autenticação</a>, para que falhas na sua operadora de telefonia não inviabilizem seu login. Pelo aplicativo, a chave de acesso estará sempre disponível para uso.
@@ -48,17 +48,17 @@ Para usar uma chave gerada por aplicativo de autenticação:
 
 1. Baixe o aplicativo **Google Autenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)). 
 
-  ![2FA - App Download - PT](https:https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/c0bc298cb4c870e271da368bb765e146/2FA_-_App_Download_-_PT.png)
+  ![2FA - App Download - PT](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/c0bc298cb4c870e271da368bb765e146/2FA_-_App_Download_-_PT.png)
 
 2. Use o aplicativo para ler o QR Code com a câmera do seu celular.
 
-  ![2FA - App QR Code - PT](https:https://images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/48d5047d5959b95f938efe35d7fa0983/2FA_-_App_QR_Code_-_PT.png)
+  ![2FA - App QR Code - PT](https://images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/48d5047d5959b95f938efe35d7fa0983/2FA_-_App_QR_Code_-_PT.png)
 
 3. Sua conta da VTEX será adicionada ao aplicativo, com um código de 6 dígitos. Insira o código para concluir seu login.
 
   *O código do app é atualizado periodicamente. Não será necessário memorizá-lo, basta consultar o aplicativo sempre que precisar.*
 
-  ![2FA - App Insert Code - PT](https:https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/58da9e3065ebec81f1528554808eee56/2FA_-_App_Insert_Code_-_PT.png)
+  ![2FA - App Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/58da9e3065ebec81f1528554808eee56/2FA_-_App_Insert_Code_-_PT.png)
 
 <div class="alert alert-info">
 Se você fizer login usando e-mail e senha no mesmo computador, a chave de acesso será solicitada <strong>a cada 3 dias</strong>. Quando isso acontecer, basta consultar o código no aplicativo.
@@ -70,11 +70,11 @@ Para usar uma chave enviada por mensagem de texto:
 
 1. Insira seu número de celular para enviarmos o código por SMS - não se esqueça de colocar o código de país e área.
 
-  ![2FA - SMS Insert Phone - PT](https:https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/d57d2ea05bb88182ab5b9df700fdadb2/2FA_-_SMS_Insert_Phone_-_PT.png)
+  ![2FA - SMS Insert Phone - PT](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/d57d2ea05bb88182ab5b9df700fdadb2/2FA_-_SMS_Insert_Phone_-_PT.png)
 
 2. Você receberá uma mensagem de texto da VTEX no celular indicado. Insira a chave de 6 dígitos para concluir seu login.
 
-   ![2FA - SMS Insert Code - PT](https:https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/bf998e866456c232965f4bd845b65db1/2FA_-_SMS_Insert_Code_-_PT.png)
+   ![2FA - SMS Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/bf998e866456c232965f4bd845b65db1/2FA_-_SMS_Insert_Code_-_PT.png)
 
 <div class="alert alert-warning">
 Não podemos garantir que sua operadora de telefonia conseguirá entregar a chave de acesso sempre que necessário. Caso a mensagem de texto da VTEX não chegue, tente reenviar o código ou <a href="#habilitar-o-2fa-por-aplicativo">habilitar o 2FA por aplicativo</a>.
@@ -86,10 +86,10 @@ Para modificar as configurações de verificação em duas etapas:
 
 1. Acesse suas configurações de usuário, clicando no círculo com suas iniciais no canto superior-direito do Admin.
 
-  ![2FA - User Initials - PT](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
+  ![2FA - User Initials - PT](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
 
 2. Clique em **Verificação em 2 passos** para visualizar suas configurações.
 
-  ![2FA - My User - PT](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
+  ![2FA - My User - PT](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
 
 3. Você poderá então alterar suas configurações seguindo passos similares aos apresentados nas seções acima para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) e [aplicativo](#habilitar-o-2fa-por-aplicativo). 
diff --git a/docs/tracks/pt/enabling-a-sales-rep-code.md b/docs/tracks/pt/enabling-a-sales-rep-code.md
index bf29478c7..aa36cb730 100644
--- a/docs/tracks/pt/enabling-a-sales-rep-code.md
+++ b/docs/tracks/pt/enabling-a-sales-rep-code.md
@@ -42,7 +42,7 @@ Depois de seguir essas recomendações, acesse o módulo __Configurações da lo
 
 Do lado direito da tela, você verá o arquivo `checkout-instore-custom.js`. 
 
-![vendorcode](https://images.ctfassets.net/alneenqid6w5/ZvQVCvlacD2AYf9eHKcxl/53885297fc0e0882178a6230815b2b6e/vendorcode.PNG)
+![vendorcode](//images.ctfassets.net/alneenqid6w5/ZvQVCvlacD2AYf9eHKcxl/53885297fc0e0882178a6230815b2b6e/vendorcode.PNG)
 
 Acesse-o e adicione o seguinte trecho ao objeto `window.INSTORE_CONFIG`:
 
@@ -64,7 +64,7 @@ Cada responsável deve preencher as propriedades do objeto `window.INSTORE_CONFI
 
 Por fim, finalize clicando no botão azul __Salvar__ localizado no topo da página.
 
-![vendorcode2](https://images.ctfassets.net/alneenqid6w5/59lZVji41rXxNjVXhwC6Ae/76513fc455650813e5740e68882421dd/vendorcode2.PNG) 
+![vendorcode2](//images.ctfassets.net/alneenqid6w5/59lZVji41rXxNjVXhwC6Ae/76513fc455650813e5740e68882421dd/vendorcode2.PNG) 
 
 ## Entendendo as propriedades
 
diff --git a/docs/tracks/pt/enabling-cart-transfer-between-devices.md b/docs/tracks/pt/enabling-cart-transfer-between-devices.md
index 17d86be15..7cdd8a408 100644
--- a/docs/tracks/pt/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/pt/enabling-cart-transfer-between-devices.md
@@ -34,11 +34,11 @@ window.INSTORE_CONFIG = {
 
 Após realizar essa alteração, abra o menu do inStore e atualize os dados, clicando no botão __Restaurar dados__. Feito isso, aparecerão duas bolinhas ao fim da página de identificação do inStore:
 
-![24. Enable cart transfer between devices - 1](https://images.ctfassets.net/alneenqid6w5/4HXR0QuEd2wa6GiRFL9gsm/4515dcc3ca2bb5a7d6d2304886724704/24._Enable_cart_transfer_between_devices_-_1.png)
+![24. Enable cart transfer between devices - 1](//images.ctfassets.net/alneenqid6w5/4HXR0QuEd2wa6GiRFL9gsm/4515dcc3ca2bb5a7d6d2304886724704/24._Enable_cart_transfer_between_devices_-_1.png)
 
 Ao arrastar a tela para a direita, você verá a tela para __Capturar Carrinho__, conforme mostra a imagem abaixo.
 
-![24. Enable cart transfer between devices - 2](https://images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
+![24. Enable cart transfer between devices - 2](//images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
 
 Nessa tela, é possível capturar um carrinho por um desses três métodos:
 - Código do carrinho
@@ -49,4 +49,4 @@ Nessa tela, é possível capturar um carrinho por um desses três métodos:
 
 Para o vendedor compartilhar um carrinho, ele pode gerar um código numérico ou um QR Code. Para isso, estando na tela do carrinho, basta clicar no botão __Transferir__. Veja um exemplo na imagem abaixo.
 
-![24. Enable cart transfer between devices - 3](https://images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
+![24. Enable cart transfer between devices - 3](//images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
diff --git a/docs/tracks/pt/enabling-order-filter-by-salesperson.md b/docs/tracks/pt/enabling-order-filter-by-salesperson.md
index a393f8983..49a57d796 100644
--- a/docs/tracks/pt/enabling-order-filter-by-salesperson.md
+++ b/docs/tracks/pt/enabling-order-filter-by-salesperson.md
@@ -20,7 +20,7 @@ A mudança das configurações de filtro por vendedor, explicada neste artigo, e
 
 No inStore, é possível ver a listagem de todos os pedidos finalizados em uma loja:
 
-![26. Enable order filter by salesperson - 1](https://images.ctfassets.net/alneenqid6w5/4pI7zxSaInuVvjIqWUK3Uv/ef9c2555f36f9bed41970a85727c2059/26._Enable_order_filter_by_salesperson_-_1.png)
+![26. Enable order filter by salesperson - 1](//images.ctfassets.net/alneenqid6w5/4pI7zxSaInuVvjIqWUK3Uv/ef9c2555f36f9bed41970a85727c2059/26._Enable_order_filter_by_salesperson_-_1.png)
 
 Porém, algumas vezes faz sentido que um vendedor veja apenas os pedidos finalizados por ele. Para habilitar essa opção é necessário editar o arquivo `checkout-instore-custom.js`.
 
@@ -43,4 +43,4 @@ Não remova nenhuma das outras propriedades presentes no objeto <code>window.INS
 
 Após recarregar os dados do inStore, clicando no botão __Restaurar dados__, o vendedor verá apenas os pedidos fechados por ele, como no seguinte exemplo:
 
-![26. Enable order filter by salesperson - 2](https://images.ctfassets.net/alneenqid6w5/4vi7YeUa3706ls0bQ2p0eE/343cfe8b50ae2956522bc5c79de8ec58/26._Enable_order_filter_by_salesperson_-_2.png)
+![26. Enable order filter by salesperson - 2](//images.ctfassets.net/alneenqid6w5/4vi7YeUa3706ls0bQ2p0eE/343cfe8b50ae2956522bc5c79de8ec58/26._Enable_order_filter_by_salesperson_-_2.png)
diff --git a/docs/tracks/pt/enabling-product-recommendations.md b/docs/tracks/pt/enabling-product-recommendations.md
index bea6eeacf..9a604098b 100644
--- a/docs/tracks/pt/enabling-product-recommendations.md
+++ b/docs/tracks/pt/enabling-product-recommendations.md
@@ -22,7 +22,7 @@ Por padrão, o inStore mostra uma lista de produtos sugeridos ao vendedor em dua
 - No carrinho
 - Na página de produto
 
-![25. Enable product recommendations - 1](https://images.ctfassets.net/alneenqid6w5/4j8YWYRuwENptnipUat6Wj/44401abb84a8aba3c3c89282afafc511/25._Enable_product_recommendations_-_1.png)
+![25. Enable product recommendations - 1](//images.ctfassets.net/alneenqid6w5/4j8YWYRuwENptnipUat6Wj/44401abb84a8aba3c3c89282afafc511/25._Enable_product_recommendations_-_1.png)
 
 Caso deseje ocultar essas recomendações, é necessário editar os arquivos `checkout-instore-custom.css` e `checkout-instore-custom.js`.
 
@@ -30,7 +30,7 @@ Caso deseje ocultar essas recomendações, é necessário editar os arquivos `ch
 
 Assim como o arquivo JavaScript de customização do inStore, o `checkout-instore-custom.css` deve ser acessado pelo painel administrativo da VTEX (conforme explicado no artigo [inStore Customizations](https://help.tex.com/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/4mwdBrFsmE2EPE0FzgX28b)).
 
-![25. Enable product recommendations - 2](https://images.ctfassets.net/alneenqid6w5/4jRvpkXNEW0k5kwXXxkRnG/fe7e30eef89ad19ad4d4bfc0ca9579a5/25._Enable_product_recommendations_-_2.png)
+![25. Enable product recommendations - 2](//images.ctfassets.net/alneenqid6w5/4jRvpkXNEW0k5kwXXxkRnG/fe7e30eef89ad19ad4d4bfc0ca9579a5/25._Enable_product_recommendations_-_2.png)
 
 No arquivo `checkout-instore-custom.css`, inclua a seguinte regra de CSS:
 
diff --git a/docs/tracks/pt/endless-aisle.md b/docs/tracks/pt/endless-aisle.md
index e01bfe8e2..c3057284d 100644
--- a/docs/tracks/pt/endless-aisle.md
+++ b/docs/tracks/pt/endless-aisle.md
@@ -3,8 +3,8 @@ title: 'Prateleira Infinita'
 id: 40KMlmGI5tN0r0KPCDWgGn
 status: PUBLISHED
 createdAt: 2020-06-30T21:32:21.143Z
-updatedAt: 2023-05-31T15:34:48.839Z
-publishedAt: 2023-05-31T15:34:48.839Z
+updatedAt: 2023-07-26T18:46:19.274Z
+publishedAt: 2023-07-26T18:46:19.274Z
 firstPublishedAt: 2020-06-30T21:36:39.077Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md b/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
index 9ceb9ef0d..9a8b66da2 100644
--- a/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
+++ b/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
@@ -16,11 +16,11 @@ trackSlugPT: suiteshare
 
 Você já criou o [chat](https://help.vtex.com/pt/tutorial/chat--2HdGrTcSYL1ZIXy7QTWE5), criou os [links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB), a [captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) está funcionando perfeitamente, agora só precisamos entender de onde vieram esses clientes. Para fazer isso é super tranquilo, acesse o seu painel admin e clique em “_**Analisar**_” 
 
-![Entenda como os clientes chegam até o seu WhatsApp 1](https://images.ctfassets.net/alneenqid6w5/5wsUGreWmGzlbgMNYFiKmg/996bf462e45d3274236d3d70246dca78/Screenshot_2022-08-25_at_15-24-42_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 1](//images.ctfassets.net/alneenqid6w5/5wsUGreWmGzlbgMNYFiKmg/996bf462e45d3274236d3d70246dca78/Screenshot_2022-08-25_at_15-24-42_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Acessando o painel, você terá as seguintes opções: 
 
-![Entenda como os clientes chegam até o seu WhatsApp 2](https://images.ctfassets.net/alneenqid6w5/rERjlfyQ0Ck7UZTukK1nX/54d8ca1cdbb8216136dd9f19af636144/Screenshot_2022-08-25_at_15-25-53_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 2](//images.ctfassets.net/alneenqid6w5/rERjlfyQ0Ck7UZTukK1nX/54d8ca1cdbb8216136dd9f19af636144/Screenshot_2022-08-25_at_15-25-53_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 **1 Geral:** Uma análise geral de todos os links criados na sua conta
 
@@ -34,27 +34,27 @@ Acessando o painel, você terá as seguintes opções: 
 
 No analisar você consegue entender o número total de cliques no seu link, o relatório do mês, semana e diário. 
 
-![Entenda como os clientes chegam até o seu WhatsApp 3](https://images.ctfassets.net/alneenqid6w5/1ks9WLyhVQ3X0jNrvOSVeT/9f0f3450ebe47a4fbe777d5052b52a5a/Screenshot_2022-08-25_at_15-32-26_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 3](//images.ctfassets.net/alneenqid6w5/1ks9WLyhVQ3X0jNrvOSVeT/9f0f3450ebe47a4fbe777d5052b52a5a/Screenshot_2022-08-25_at_15-32-26_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Além disso é possível filtrar períodos específicos 
 
-![Entenda como os clientes chegam até o seu WhatsApp 4](https://images.ctfassets.net/alneenqid6w5/6SLlRKkWTRV7KdKYWVl8zs/3fb77230a60ed93026c8122a1be89711/Screenshot_2022-08-25_at_15-39-59_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 4](//images.ctfassets.net/alneenqid6w5/6SLlRKkWTRV7KdKYWVl8zs/3fb77230a60ed93026c8122a1be89711/Screenshot_2022-08-25_at_15-39-59_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Além disso é possível filtrar períodos específicos
 
-![Entenda como os clientes chegam até o seu WhatsApp 5](https://images.ctfassets.net/alneenqid6w5/6EmQOv4uPAdhAxT2Mo8Nur/bb80d00d59f31098c0a90c49e94103b7/Screenshot_2022-08-25_at_15-42-13_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 5](//images.ctfassets.net/alneenqid6w5/6EmQOv4uPAdhAxT2Mo8Nur/bb80d00d59f31098c0a90c49e94103b7/Screenshot_2022-08-25_at_15-42-13_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Analisar também a região de onde o seu cliente está vindo
 
-![Entenda como os clientes chegam até o seu WhatsApp 6](https://images.ctfassets.net/alneenqid6w5/5iYtWzO8XFn2oHCCe1GqZR/271dec5624608a53f1adff8e31347321/Screenshot_2022-08-25_at_15-43-10_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 6](//images.ctfassets.net/alneenqid6w5/5iYtWzO8XFn2oHCCe1GqZR/271dec5624608a53f1adff8e31347321/Screenshot_2022-08-25_at_15-43-10_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 E a referência de domínio, de onde originou esse acesso 
 
-![Entenda como os clientes chegam até o seu WhatsApp 7](https://images.ctfassets.net/alneenqid6w5/2mOHLwD91XCdPVFLplkdTb/01e92096688aa4cad6a2f2552c02bb2a/Screenshot_2022-08-25_at_15-47-17_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 7](//images.ctfassets.net/alneenqid6w5/2mOHLwD91XCdPVFLplkdTb/01e92096688aa4cad6a2f2552c02bb2a/Screenshot_2022-08-25_at_15-47-17_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Além de uma visão geral sobre dispositivos e navegadores
 
-![Entenda como os clientes chegam até o seu WhatsApp 8](https://images.ctfassets.net/alneenqid6w5/7Ak1oh5FTardmnq18olO0U/3e2ac6b3487ee8a15c5ee369d999bf50/Screenshot_2022-08-25_at_15-48-00_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 8](//images.ctfassets.net/alneenqid6w5/7Ak1oh5FTardmnq18olO0U/3e2ac6b3487ee8a15c5ee369d999bf50/Screenshot_2022-08-25_at_15-48-00_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Gostou? 
 
diff --git a/docs/tracks/pt/explained-search.md b/docs/tracks/pt/explained-search.md
index 6f0a388ac..a0e68f773 100644
--- a/docs/tracks/pt/explained-search.md
+++ b/docs/tracks/pt/explained-search.md
@@ -26,5 +26,5 @@ Para utilizá-la, siga o passo a passo abaixo:
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
 2. Em **Intelligent Search**, clique em **Explicação da busca**. 
 
-![Explicação da Busca](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
+![Explicação da Busca](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
 
diff --git a/docs/tracks/pt/extensions-hub-1.md b/docs/tracks/pt/extensions-hub-1.md
index 804f3e9a4..b70c9243c 100644
--- a/docs/tracks/pt/extensions-hub-1.md
+++ b/docs/tracks/pt/extensions-hub-1.md
@@ -18,6 +18,6 @@ O Hub de Extensões é uma seção do Admin que agrupa todas as informações e
 
 Para acessar o Hub de Extensões, vá ao painel lateral esquerdo do Admin, clique no ícone **Extensões** e ele estará visível na parte superior do menu.
 
-![Extensions Hub painel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
+![Extensions Hub painel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
 
 No Hub de Extensões podem ser encontradas três páginas: **Loja de aplicativos**, **Parceiros** e **Gerenciamento de aplicativos**. A documentação sobre cada um deles pode ser vista nos artigos logo em seguida.
diff --git a/docs/tracks/pt/extensions-hub-app-store.md b/docs/tracks/pt/extensions-hub-app-store.md
index 7cb1ecbff..f0ea6a195 100644
--- a/docs/tracks/pt/extensions-hub-app-store.md
+++ b/docs/tracks/pt/extensions-hub-app-store.md
@@ -18,7 +18,7 @@ A App Store é a página do Admin onde você pode buscar, visualizar e obter app
 
 ## Página inicial
 
-![Extensions Hub App Store página inicial](https://images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/ba56f15ab8cc4041dd0d8cf3d10afa1d/Extensions_Hub_App_Store_home_page_PT.png)
+![Extensions Hub App Store página inicial](//images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/ba56f15ab8cc4041dd0d8cf3d10afa1d/Extensions_Hub_App_Store_home_page_PT.png)
 
 Ao entrar na loja, você estará na página inicial. Nesta página estão disponíveis as seguintes opções:
 
@@ -28,13 +28,13 @@ Ao entrar na loja, você estará na página inicial. Nesta página estão dispon
 
 ## Busca
 
-![Extensions Hub App Store busca](https://images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/1cca7f3ff65a4568f6327cae2e4e6de0/Extensions_Hub_App_Store_search_PT.png)
+![Extensions Hub App Store busca](//images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/1cca7f3ff65a4568f6327cae2e4e6de0/Extensions_Hub_App_Store_search_PT.png)
 
 A busca permite que você pesquise por apps através do nome. Ao digitar na caixa de texto da busca e pressionar a tecla `Enter`, você será direcionado para a página de resultados da busca. Os resultados serão os apps cujos nomes correspondam ao texto inserido na busca. Os apps aparecem no formato de cartões quadrados, onde é possível ver o nome, o subtítulo e o custo do app. Ao clicar em um app, você será levado para a [página do app](#pagina-do-app).
 
 ## Página do app
 
-![Extensions Hub App Store app page](https://images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/c0e06d0a250b05fa32b97b4161fae294/Extensions_Hub_App_Store_app_page_PT.png)
+![Extensions Hub App Store app page](//images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/c0e06d0a250b05fa32b97b4161fae294/Extensions_Hub_App_Store_app_page_PT.png)
 
 Ao clicar em um app na página inicial ou na busca, você será direcionado para a página do respectivo app. Nesta página você encontrará todas as informações sobre o app, incluindo os custos, e a opção para baixá-lo.
 
diff --git a/docs/tracks/pt/extensions-hub-partners.md b/docs/tracks/pt/extensions-hub-partners.md
new file mode 100644
index 000000000..658cfbbe7
--- /dev/null
+++ b/docs/tracks/pt/extensions-hub-partners.md
@@ -0,0 +1,19 @@
+---
+title: 'Parceiros'
+id: 3XkOpOSbeCJIcBL5dhuPq1
+status: PUBLISHED
+createdAt: 2023-08-02T13:04:06.286Z
+updatedAt: 2023-08-02T14:33:05.047Z
+publishedAt: 2023-08-02T14:33:05.047Z
+firstPublishedAt: 2023-08-02T14:33:05.047Z
+contentType: trackArticle
+productTeam: VTEX IO
+slug: hub-de-extensoes-parceiros
+locale: pt
+trackId: AW7klkYMh557y5IUOgzco
+trackSlugPT: hub-de-extensoes
+---
+
+<div class="alert alert-warning">
+Conteúdo ainda não disponível.
+</div>
diff --git a/docs/tracks/pt/filter-orders-by-vendor.md b/docs/tracks/pt/filter-orders-by-vendor.md
index f171a4929..ed6389331 100644
--- a/docs/tracks/pt/filter-orders-by-vendor.md
+++ b/docs/tracks/pt/filter-orders-by-vendor.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 No inStore é possível ver a listagem de todos os pedidos finalizados em uma loja:
 
-![pedidos finalizados](https://images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
+![pedidos finalizados](//images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
 
 Porém, algumas vezes faz sentido que um vendedor veja apenas os pedidos finalizados por ele. Para habilitar essa opção é necessário editar o arquivo `checkout-instore-custom.js` presente no admin do Portal. Por se tratar de um JavaScript presente em diversos fluxos de uso da aplicação, é importante que você tenha conhecimentos de programação antes de alterá-lo, para evitar a quebra de outras funcionalidades.
 
@@ -37,4 +37,4 @@ __IMPORTANTE__: Não remova nenhuma das outras propriedades presentes no objeto
 
 Após recarregar o inStore o resultado deve ser o seguinte:
 
-![pedidos finalizados filtrados por vendedor](https://images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
+![pedidos finalizados filtrados por vendedor](//images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
diff --git a/docs/tracks/pt/filters.md b/docs/tracks/pt/filters.md
index b428b8a9d..c9edb0a97 100644
--- a/docs/tracks/pt/filters.md
+++ b/docs/tracks/pt/filters.md
@@ -3,8 +3,8 @@ title: 'Filtros'
 id: 50Dh4mpv0Sax0XpbvsjAtP
 status: PUBLISHED
 createdAt: 2020-03-05T17:44:58.362Z
-updatedAt: 2023-05-05T19:32:35.780Z
-publishedAt: 2023-05-05T19:32:35.780Z
+updatedAt: 2024-06-04T15:34:47.299Z
+publishedAt: 2024-06-04T15:34:47.299Z
 firstPublishedAt: 2020-03-05T19:54:44.962Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -37,11 +37,13 @@ A funcionalidade de Filtros apresenta as seguintes funções:
 - Pesquisa que possibilita ao cliente buscar um termo dentro de um filtro.
 - Configurar e definir a quantidade máxima de opções em um filtro antes de gerar rolagem.
 - Configurar qual o layout em que um filtro será exibido. É possível escolher entre os seguintes formatos:
- - Listagem vertical (formato padrão).
- - Listagem horizontal: utilizada para exibir filtros como Tamanho e Cor.
- - Barra deslizante: normalmente utilizada em filtros numéricos, alternando do valor mínimo para o máximo.
- - Conjunto de intervalados: divisão de produtos em agrupamentos de valores a partir da quantidade de itens.
- - Entrada de valores: permite ao cliente informar o valor “De” e “Até” que será usado para filtragem.
+
+   - Listagem vertical (formato padrão).
+   - Listagem horizontal: utilizada para exibir filtros como Tamanho e Cor.
+   - Barra deslizante: utilizada para alternar do preço mínimo para o máximo.
+   - Entrada de valores: permite ao cliente informar o preço “De” e “Até” que será usado para filtragem.
+
+Confira o guia [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) no Developer Portal para mais detalhes técnicos sobre a utilização de filtros.
 
 <div class="alert alert-warning">
   <p>Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.</p>
diff --git a/docs/tracks/pt/frontend-implementation.md b/docs/tracks/pt/frontend-implementation.md
new file mode 100644
index 000000000..8a57f1d79
--- /dev/null
+++ b/docs/tracks/pt/frontend-implementation.md
@@ -0,0 +1,321 @@
+---
+title: 'Implementação de frontend'
+id: 67SCtUreXxKYWhZh8n0zvZ
+status: PUBLISHED
+createdAt: 2024-01-31T22:25:47.689Z
+updatedAt: 2024-03-07T17:10:29.946Z
+publishedAt: 2024-03-07T17:10:29.946Z
+firstPublishedAt: 2024-02-22T14:07:19.178Z
+contentType: trackArticle
+productTeam: Others
+slug: implementacao-de-frontend
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+O frontend de uma loja online, também conhecido como frente de loja, é a interface visual e interativa da loja através da qual os clientes da loja interagem com produtos e executam ações, como navegar por categorias, pesquisar, e adicionar produtos ao carrinho.
+
+Este artigo tem como objetivo auxiliar na escolha de qual tecnologia usar para construir a frente de loja e quais configurações são necessárias para cada uma, considerando os seguintes pontos:
+
+- Tecnologias de desenvolvimento de frente de loja da VTEX.
+- Principais funcionalidades de cada tecnologia.
+- Etapas de desenvolvimento.
+
+O foco da implementação de frontend é uma etapa com foco em definir as tecnologias a serem implementadas, de acordo com as necessidades do negócio relacionadas à frente de loja.
+
+<div class = "alert alert-info">
+O frontend pode ser implementado pelo time de desenvolvimento interno da empresa ou pelos nossos <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros de implementação</a>. <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512">Usuários</a> com acesso ao Admin VTEX podem consultar a lista dos nossos parceiros pelo <a href="https://partnerportal.vtex.com/">Partner Portal</a>.
+</div>
+
+## Antes de começar
+
+Antes de começar a implementação do frontend, é recomendado que a loja tenha as seguintes etapas configuradas:
+
+| Etapa | Descrição |
+| ----- | --------- |
+| Definição da arquitetura da loja e sua estratégia de vendas | O time definiu a arquitetura da sua loja VTEX de acordo com as estratégias e necessidades do seu modelo de negócio.<br><br>Mais informações no artigo [Contas e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). |
+| Configuração dos perfis de acesso | O time configurou os acessos necessários para usar a plataforma VTEX para cada [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512).<br><br>Mais informações no artigo [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc). |
+| Configuração do catálogo | O time configurou o [catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) com os produtos, a árvore de categoria e informações relacionadas, como descrições, imagens e preços, a fim de preencher e testar a loja, incluindo recursos como páginas de listagem de produtos (PLP), funcionalidade de pesquisa, páginas de detalhes de produtos (PDP) e checkout.<br><br>A ausência de um catálogo pode resultar em testes incompletos e problemas de integração de dados, atrasando a implementação.<br><br>Mais informações no artigo [Módulos da VTEX I](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7). |
+| Definição dos aplicativos necessários à operação da loja | O time definiu os aplicativos, nativos ou de terceiros, necessários para a operação da loja.<br><br>Para lojas que serão construídas usando [Store Framework](#store-framework), existe uma lista de apps nativos e de terceiros.<br><br>Mais informações no artigo [VTEX IO apps](https://developers.vtex.com/docs/vtex-io-apps). |
+
+<div class = "alert alert-info">
+A <a href="#etapas-de-desenvolvimento">etapa de desenvolvimento</a> pode acontecer em paralelo com outras etapas da <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a> e <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7">configuração de módulos</a>, como por exemplo as configurações de meios de pagamentos e logística. Isso vai depender do tipo de <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitetura e planejamento</a> escolhidos para a loja VTEX e deve ser acompanhado pela <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">agência implementadora</a> ou <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">Suporte VTEX</a>.
+</div>
+
+## Tecnologias de desenvolvimento de frontend na VTEX
+
+A VTEX possui três tecnologias distintas para o desenvolvimento de frente de loja: a [FastStore](#FastStore), o [Store Framework](#store-framework) e o [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). O CMS Portal Legado foi a primeira tecnologia da VTEX para construção de frente de loja, baseada em HTML, CSS e JavaScript, e todo o desenvolvimento e a edição do código dessa tecnologia são feitos via Admin VTEX.
+
+<div class="alert alert-warning">
+Apesar de ainda ser usado por algumas lojas, o <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> é uma tecnologia legada e não está mais disponível para lojas que estão iniciando com a VTEX.
+</div>
+
+As próximas seções são sobre as principais características e funcionalidades da FastStore e do Store Framework.
+
+## FastStore
+
+FastStore é uma inovação em tecnologia de frente de loja para times de desenvolvimento criarem lojas com foco em performance e estabilidade, além de ser uma tecnologia de fácil manutenção, inclusive na edição de páginas do site da loja. 
+
+Esta tecnologia é um _toolkit open-source_ baseado em _React_ e na arquitetura [Jamstack](https://jamstack.org/). Para obter mais informações, basta consultar o portal de documentação da [FastStore](https://www.faststore.dev/docs).
+
+### Principais funcionalidades da FastStore
+
+A tabela a seguir apresenta algumas das principais funcionalidades da FastStore:
+
+| Funcionalidade | Descrição |
+| -------------- | --------- |
+| [Starter](https://starter.vtex.app/) | Template funcional projetado para o desenvolvimento rápido da loja, e que já integra os componentes da [FastStore UI](https://www.faststore.dev/components). Inclui páginas como Home, páginas de lista de produtos (PLPs), páginas de detalhes do produto (PDPs) e também a funcionalidade minicart. |
+| [FastStore UI](https://www.faststore.dev/components) | Biblioteca de componentes para ecommerce que fornece recursos e estilo básico, tornando mais rápida a implementação e personalização de frentes de loja. |
+| Tecnologia *headless* | Processo de customização que separa o código da loja desenvolvido pelo time de desenvolvimento do código base fornecido pela VTEX. Isso simplifica as atualizações do frontend da loja, permitindo atualizações sem impactar o código customizado. |
+| Integração com o [GitHub](https://github.com/) | Os times de desenvolvimento podem gerenciar todo o código da frente de loja utilizando o [GitHub](https://github.com/). |
+| [Headless CMS](https://www.faststore.dev/docs/headless-cms-overview) | Sistema de gerenciamento de conteúdo (CMS) que permite a edição e criação de novas páginas e a pré-visualização de mudanças no conteúdo. |
+| Verificações automatizadas | Testes funcionais e a avaliação da performance da loja e da qualidade do código são executados continuamente de forma automatizada para detectar lentidão e bugs durante todo o estágio de desenvolvimento da frente de loja. |
+| Integração com [Intelligent Search](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account) | Funcionalidade de preenchimento automático na barra de pesquisa, juntamente com sugestões de pesquisa e produtos com base em preferências configuráveis. |
+| Integrações com [Checkout](https://www.faststore.dev/docs/go-live/4-integrating-the-vtex-checkout), [Minha Conta](https://www.faststore.dev/docs/go-live/5-integrating-the-vtex-order-placed-and-my-account) e [Login](https://www.faststore.dev/docs/go-live/3-integrating-the-the-vtex-login) | Integração com outras etapas da jornada de compra dos clientes. Lojas VTEX previamente desenvolvidas com o Store Framework podem manter configurações relacionadas ao Checkout, Minha Conta e Login quando migradas para a FastStore, pois ambas se beneficiam da mesma infraestrutura. |
+
+## Store Framework
+
+Store Framework é uma solução já estabelecida de tecnologia *framework* de implementação de frentes de loja *low-code* com foco no modelo composable commerce, ou seja, o framework possibilita a combinação de diferentes apps do [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) para formar a frente de loja.
+
+Nesta tecnologia, a implementação e o lançamento da loja são focados em componentes pré-construídos, também conhecidos como blocos, e na possibilidade de customização desses componentes, conforme a necessidade do modelo de negócio. Este *framework* é baseado em:
+
+- React
+- TypeScript
+- Node.js
+- GraphQL
+
+Para obter mais informações, basta acessar o artigo [What is VTEX Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework).
+
+### Ambiente de desenvolvimento
+
+Ao falar de implementação de frontend, é preciso lembrar que o [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) não é uma tecnologia de construção de frente de loja, mas sim uma plataforma de desenvolvimento. O Store Framework é uma tecnologia de construção de frente de loja que é executada pelo VTEX IO, que por sua vez é uma solução de desenvolvimento e execução em nuvem de aplicativos personalizados e frentes de loja.
+
+Isso significa que ao trabalhar com VTEX IO, a pessoa desenvolve seu código localmente. Porém, quando se trata de implantar e executar a loja, o VTEX IO gerencia a infraestrutura, CI/CD e segurança, além de cuidar do processo de implantação. A imagem abaixo apresenta como estes conceitos se relacionam entre si:
+
+![Arquitetura de desenvolvimento frontend](//images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/a552a6ae6c50ef92304ff8f11e651cbf/frontend_image2_PT.png)
+
+### Principais funcionalidades do Store Framework
+
+A tabela a seguir apresenta algumas das principais funcionalidades do Store Framework:
+
+| Funcionalidade | Descrição |
+| -------------- | --------- |
+| [Starter](https://github.com/vtex-apps/store-theme) | Template funcional projetado para o desenvolvimento rápido da loja, e que já integra os componentes pré-construídos. |
+| [Componentes pré-construídos](https://developers.vtex.com/docs/vtex-io-apps) | Componentes nativos baseados em *React*. |
+| Arquitetura modular | Personalização e reutilização do código de elementos da interface para lançar e replicar lojas rapidamente. |
+| [Workspaces e ambientes de testes](https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace) | Permite criar diferentes versões da loja e testá-las previamente para realizar alterações com segurança. |
+| [Site Editor](https://help.vtex.com/pt/tutorial/site-editor-visao-geral--299Dbeb9mFczUTyNQ9xPe1) | Sistema de gerenciamento de conteúdo (CMS) para edição de templates e construção de novas páginas no site da loja. |
+| [Testes A/B nativos](https://developers.vtex.com/docs/guides/ab-tests) | Permite testar e validar qual a versão da loja com as maiores taxas de conversão. |
+| Integração com [Intelligent Search](https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) | Funcionalidade de preenchimento automático na barra de pesquisa, juntamente com sugestões de pesquisa e produtos com base em suas preferências. |
+| [Progressive Web App (PWA)](https://help.vtex.com/pt/tutorial/habilitando-notificacoes-pwa-da-loja--1be3ZPhbsgZSbE7h5H46pG) | Permite experiências nativas semelhantes a aplicativos em qualquer dispositivo com tecnologia pronta para PWA. |
+| [Cross-border](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs?&utm_source) | Permite que uma loja [multiloja](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multiloja) VTEX opere em diferentes países com uma abordagem própria para cada um deles. |
+| Integração com Checkout, [Minha Conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh) e Login | Integração com outras etapas da jornada de compra do cliente. |
+
+## Escolhendo a tecnologia de frontend
+
+Ao escolher entre Store Framework e FastStore, o time deve avaliar as necessidades específicas do projeto e considerar a experiência da equipe com ambas as tecnologias.
+
+O Store Framework é uma opção mais madura, oferecendo uma estrutura flexível adequada para casos de uso complexos, bem como suporte para lojas que operam internacionalmente e com vários idiomas. 
+Para lojas B2B, o Store Framework é uma ótima opção, uma vez que disponibiliza o [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite), um aplicativo que permite o gerenciamento de organizações, permissões de frente de loja, e configurações de checkout para relacionamentos comerciais B2B.
+
+A FastStore é uma alternativa em evolução mais recente focada na performance da loja. Esta solução oferece uma experiência de carregamento rápido, o que é essencial para manter os visitantes da loja engajados e reduzir as taxas de abandono de carrinho. Para casos de uso mais simples e com foco em performance, a FastStore pode ser a tecnologia mais recomendada. 
+
+<div class = "alert alert-info">
+A equipe de <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">suporte da VTEX</a> pode auxiliar no momento de escolher entre uma das tecnologias de storefront disponíveis.
+</div>
+
+A tabela abaixo compara as duas tecnologias de acordo com suas principais funcionalidades:
+
+<table>
+    <tr>
+        <td><strong>Funcionalidade</strong></td>
+        <td><strong>Store Framework</strong></td>
+        <td><strong>FastStore</strong></td>
+    </tr>
+    <tr>
+      <td><i>Starter</i> (template inicial)</td>
+        <td>O <a href="https://github.com/vtex-apps/store-theme">Store Theme</a> é o template inicial no qual o time pode usar de base para iniciar o projeto da loja ou iniciar do zero.</td>
+        <td>O <a href="https://starter.vtex.app/">Starter FastStore</a> já é disponibilizado ao finalizar o <a href="https://www.faststore.dev/docs/getting-started/1-faststore-onboarding/overview">Onboarding da FastStore</a>. Isso permite que o time comece o projeto com um template base focado em performance.</td>
+    </tr>
+    <tr>
+        <td>Desempenho</td>
+        <td>Os recursos de SSR (<em>Server Side Rendering</em>) geram todo o HTML de uma página no servidor em resposta a uma solicitação de página, enquanto o SPA (<em>Single Page Application</em>) carrega elementos como o cabeçalho apenas uma vez que a página é carregada.</td>
+        <td>Possibilidade de máxima performance, já que utiliza a arquitetura <a href="https://jamstack.org/">Jamstack</a> para criar as páginas do site da loja com antecedência, tornando a entrega do site mais rápida e eficiente em termos de recursos.</td>
+    </tr>
+    <tr>
+        <td>Tech Stack</td>
+        <td>
+            <ul>
+                <li>TypeScript
+                <li>React
+                <li>GraphQL
+                <li>Node.js
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li>TypeScript
+                <li>React
+                <li>Next.js
+                <li>GraphQL
+                <li>Node.js
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Customizações de componentes</td>
+        <td>Flexível e de fácil personalização.</td>
+        <td>Permite a customização de componentes nativos e garante a performance da loja a partir de boas práticas.</td>
+    </tr>
+    <tr>
+        <td>Gerenciamento do código</td>
+        <td>Utiliza <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-workspace">Workspaces</a> e a arquitetura do VTEX IO para o versionamento, atualização e rollback dos componentes e aplicativos.</td>
+        <td>Utiliza o GitHub e o conceito de <a href="https://docs.github.com/pt/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches">branches</a> para a colaboração. Os usuários autorizados no repositório da frente de loja no GitHub podem visualizar e colaborar com o código.</td>
+    </tr>
+    <tr>
+        <td><em>Community and Support</em></td>
+        <td>
+            <ul>
+                <li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework">Documentação oficial</a>
+                <li><a href="https://community.vtex.com/c/store-development/store-framework/17">VTEX community</a>
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li><a href="https://www.faststore.dev/docs">Documentação oficial</a>
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td><em>Performance Monitoring and Analytics</em></td>
+        <td>
+            <ul>
+                <li>Possibilidade de configurar o <a href="https://developers.vtex.com/docs/guides/google-tag-manager">VTEX Google Tag Manager</a> para analisar dados de navegação da loja.
+                <li>Possibilidade de aumentar o desempenho do site da loja usando ferramentas de <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance">otimização de desempenho</a>.
+            </ul>
+        </td>
+        <td>
+            <ul>
+                <li>Possibilidade de configurar o módulo de Analytics nativo.
+                <li>Possibilidade de aumentar o desempenho do site da loja usando ferramentas indicadas para tecnologia.
+            </ul>
+        </td>
+    </tr>
+    <tr>
+        <td>Sistema de Gerenciamento de Conteúdo (CMS)</td>
+        <td>Compatível com o <a href="https://help.vtex.com/pt/tutorial/site-editor-visao-geral--299Dbeb9mFczUTyNQ9xPe1">Site Editor</a>.</td>
+        <td>Compatível com o <a href="https://www.faststore.dev/docs/headless-cms-overview">Headless CMS</a>.</td>
+    </tr>
+</table>
+
+## Etapas de desenvolvimento
+
+Antes de lançar a loja em produção e do [go-live](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), é importante listar as configurações e funcionalidades essenciais a serem incluídas na frente de loja. Essas definições auxiliam na definição do Mínimo Produto Viável (MVP) para a frente de loja. Por isso, os próximos tópicos indicam:
+
+- [Requisitos para um MVP da FastStore](#requisitos-para-um-mvp-da-faststore)
+- [Requisitos para um MVP do Store Framework](#requisitos-para-um-mvp-do-store-framework)
+
+<div class = "alert alert-info">
+As recomendações a seguir são para configurações básicas de frente de loja. Dependendo da <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitetura escolhida</a> para a operação da loja, outras configurações podem ser necessárias.
+</div>
+
+### Desenvolvendo com a FastStore
+
+O time de desenvolvimento deve iniciar um novo projeto com a FastStore através do processo de [Onboarding](https://www.faststore.dev/docs/getting-started/1-faststore-onboarding). Ao final desse processo, o time estará com uma loja básica e funcional baseada no [Starter da FastStore](https://starter.vtex.app/). Feito isso, os requisitos básicos da página já estarão implementados, são eles:
+
+- Home
+- *Product Listing Page* (PLP)
+- *Product Details Page* (PDP)
+- *Minicart*
+
+![FastStore template](//images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
+
+#### Requisitos para um MVP da FastStore
+
+São apresentados a seguir os requisitos para cada tema:
+
+- Catálogo
+  - [Cadastrar produtos e SKUs](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567)
+  - [Construir a árvore de categorias](https://help.vtex.com/pt/tutorial/cadastrar-uma-categoria--tutorials_206) ([departamentos](https://help.vtex.com/pt/tutorial/o-que-e-um-departamento--22rKjmYWVmmKAK8CWa8yKw), [categorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) e [subcategorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-subcategoria--2cb0aRkG3i6AeiAMM24iwY))
+  - [Definir filtros e tipos de especificações por categoria](https://help.vtex.com/pt/tutorial/criando-grupo-de-especificacoes-em-uma-categoria--tutorials_246)
+  - [Cadastrar imagens dos SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY#imagens)
+  - [Cadastrar preços dos SKUs](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29)
+  - [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139)
+- VTEX Intelligent Search
+  - [Integrar a app de Intelligent Search na conta](https://www.faststore.dev/docs/getting-started-requirements#enable-the-vtex-intelligent-search-app-in-your-account)
+- Integração com Headless CMS
+  - [Configurar o Headless CMS na conta](https://www.faststore.dev/docs/headless-cms-integration/1-configuring-the-vtex-account)
+  - [Definir content types e seções que estarão disponíveis](https://www.faststore.dev/docs/headless-cms-integration/2-setting-up-the-headless-cms)
+  - Criar e editar páginas usando o Headless CMS no Admin VTEX
+- Página Home
+  - Editar os componentes e estilos já apresentados no [Starter](https://starter.vtex.app/)
+- Página de Login
+  - [Integrar com o VTEX Login](https://www.faststore.dev/docs/go-live/3-integrating-the-the-vtex-login)
+  - Editar os componentes e estilos já apresentados no [Starter](https://starter.vtex.app/)
+- Product Listing Page (PLP)
+  - Editar os componentes e estilos já apresentados no [Starter](https://starter.vtex.app/office)
+- Product Details Page (PDP)
+  - Editar os componentes e estilos já apresentados no [Starter](https://starter.vtex.app/4k-philips-monitor-99988213/p)
+- Minicart configuration
+  - Editar os componentes e estilos já apresentados no [Starter](https://starter.vtex.app/)
+- Checkout
+  - Integrar com o [VTEX Checkout](https://www.faststore.dev/docs/go-live/4-integrating-the-vtex-checkout)
+  - Integrar com [VTEX Order Placed e My Account](https://www.faststore.dev/docs/go-live/5-integrating-the-vtex-order-placed-and-my-account)
+- Logística
+  - [Cadastrar doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+  - [Cadastrar estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
+  - [Relacionar estratégia de envio e estoque com a doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+- Payments
+  - [Configurar o conector Promissórias](https://help.vtex.com/pt/tutorial/configurar-o-conector-promissorias--7Gy0SJRVS0Qi2CuWMAqQc0)
+  - [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444)
+- Performance e SEO
+  - Aumentar o desempenho do site da loja usando ferramentas indicadas [para tecnologia](https://v1.faststore.dev/how-to-guides/performance)
+- Métricas
+  - Configurar o módulo de [Analytics](https://v1.faststore.dev/reference/sdk/analytics)
+
+### Desenvolvendo com o Store Framework
+
+O time de desenvolvimento deve iniciar um novo projeto com o Store Framework clonando e [linkando](https://developers.vtex.com/docs/guides/vtex-io-documentation-linking-an-app) o [Store Theme](https://github.com/vtex-apps/store-theme) em um [workspace de desenvolvimento](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-development-workspace). O Store Theme é um template funcional básico para iniciar a loja com componentes e páginas essenciais, tais como:
+
+- *Home*
+- *Product Listing Page* (PLP)
+- *Product Details Page* (PDP)
+
+![Store Framework template](//images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
+
+#### Requisitos para um MVP do Store Framework
+
+São apresentados a seguir os requisitos para cada tema:
+
+- Catálogo
+  - [Cadastrar produtos e SKUs](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567)
+  - [Construir a árvore de categorias](https://help.vtex.com/pt/tutorial/cadastrar-uma-categoria--tutorials_206) ([departamentos](https://help.vtex.com/pt/tutorial/o-que-e-um-departamento--22rKjmYWVmmKAK8CWa8yKw), [categorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) e [subcategorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-subcategoria--2cb0aRkG3i6AeiAMM24iwY))
+  - [Definir filtros e tipos de especificações por categoria](https://help.vtex.com/pt/tutorial/criando-grupo-de-especificacoes-em-uma-categoria--tutorials_246)
+  - [Cadastrar imagens dos SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY#imagens)
+  - [Cadastrar preços dos SKUs](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/P99EjtrlRHk92Q8qDPq29)
+  - [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139)
+- VTEX Inteligent Search
+  - [Integrar a app de Intelligent Search na conta](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
+- Página Home
+  - Editar os componentes e estilos já apresentados no [Starter](https://storetheme.vtex.com/)
+- Página de Login
+  - Integrar com o VTEX Login
+  - Editar os componentes e estilos já apresentados no [Starter](https://storetheme.vtex.com/)
+- Product Listing Page (PLP)
+  - Editar os componentes e estilos já apresentados no [Starter](https://storetheme.vtex.com/clothing?_q=clothing&map=ft)
+- Product Details Page (PDP)
+  - Editar os componentes e estilos já apresentados no [Starter](https://storetheme.vtex.com/ten-top-shirts/p)
+- Minicart configuration
+  - Editar os componentes e estilos já apresentados no [Starter](https://storetheme.vtex.com/)
+- Logística
+  - [Cadastrar doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+  - [Cadastrar estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
+  - [Relacionar estratégia de envio e estoque com doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+- Pagamentos
+  - [Configurar o conector Promissórias](https://help.vtex.com/pt/tutorial/configurar-o-conector-promissorias--7Gy0SJRVS0Qi2CuWMAqQc0)
+  - [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/registering-gateway-affiliations/)
+- Performance
+  - Aumentar o desempenho do site da loja usando ferramentas de [otimização de desempenho](https://developers.vtex.com/docs/guides/vtex-io-documentation-best-practices-for-optimizing-performance)
+- Métricas
+  - Configurar o [Google Tag Manager](https://developers.vtex.com/docs/guides/google-tag-manager)
diff --git a/docs/tracks/pt/frontend.md b/docs/tracks/pt/frontend.md
index 5f1bb936f..baad22859 100644
--- a/docs/tracks/pt/frontend.md
+++ b/docs/tracks/pt/frontend.md
@@ -26,7 +26,7 @@ A maneira como essa extensão de funcionalidades ocorre é através de apps VTEX
 
 O Store Framework é uma solução para construção de frente de loja que se alavanca do VTEX IO. Através dela podemos contar com a interface amigável do [Site Editor](https://help.vtex.com/pt/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) e tornar o gerenciamento de conteúdo da loja mais simples.
 
-![vtex io](https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/51d67a21e5ab6bf0517fee83f9455337/image3.png)
+![vtex io](//images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/51d67a21e5ab6bf0517fee83f9455337/image3.png)
 
 Lojas criadas com o Store Framework também contam com as features de: 
 - **[Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)**: ferramenta de busca, que corrige erros ortográficos e possibilita regras condicionais para exibição do resultado de busca.
diff --git a/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md b/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
index 96b2f6b5b..fcd6069ce 100644
--- a/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
+++ b/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
@@ -22,7 +22,7 @@ Primeiro, você já deve ter criado os links, caso não tenha criado clique aqui
 
 Agora é só criar seus anúncios no Facebook, Instagram e outras redes que utilizar, e inserir seu link no campo de texto. Seu cliente irá diretamente para a conversa no WhatsApp com a sua empresa.
 
-![Levar os visitantes do meu site e redes sociais para o WhatsApp 1](https://images.ctfassets.net/alneenqid6w5/44eCSKO1yJcy816ZA4wKlR/2f95d30387906b9d67ee953c6d484e31/Screenshot_2022-08-25_at_15-09-21_Levar_os_visitantes_do_meu_site_e_redes_sociais_para_o_WhatsApp.png)
+![Levar os visitantes do meu site e redes sociais para o WhatsApp 1](//images.ctfassets.net/alneenqid6w5/44eCSKO1yJcy816ZA4wKlR/2f95d30387906b9d67ee953c6d484e31/Screenshot_2022-08-25_at_15-09-21_Levar_os_visitantes_do_meu_site_e_redes_sociais_para_o_WhatsApp.png)
 
 Além de levar o seu cliente diretamente para o WhatsApp de forma rápida e fácil, você ainda pode capturar informações diretamente para o seu CRM, analisar quais redes estão lhe trazendo mais clientes, além do Remarketing no seu link. 
 
diff --git a/docs/tracks/pt/getting-started-with-logistics.md b/docs/tracks/pt/getting-started-with-logistics.md
index f7137509d..23745b7ab 100644
--- a/docs/tracks/pt/getting-started-with-logistics.md
+++ b/docs/tracks/pt/getting-started-with-logistics.md
@@ -56,7 +56,7 @@ De forma resumida, o módulo **Estoque & entrega** divide-se nas seguintes seç
 * **Configurações**: configurações gerais de logística, como habilitar a notificação de estoque crítico.
 * **[Pontos de retirada](https://help.vtex.com/pt/tutorial/como-funcionam-pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R)**: seção para cadastro de pontos físicos onde os clientes podem retirar seus pedidos.
 
-    ![estoque e entregaPT](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/4dff7a2616eb80d8ec89344ec2d2363c/estoque_e_entregaPT.png)
+    ![estoque e entregaPT](//images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/4dff7a2616eb80d8ec89344ec2d2363c/estoque_e_entregaPT.png)
 
 <div class = "alert alert-info">
   Clientes que utilizam o <a href="https://vtex.com/br-pt/log/"><b>VTEX Shipping Network</a></b> acessam a funcionalidade pelo módulo <b>Estoque & Entrega</b>.
diff --git a/docs/tracks/pt/go-live-process.md b/docs/tracks/pt/go-live-process.md
index 694d9ef21..c9f8884fa 100644
--- a/docs/tracks/pt/go-live-process.md
+++ b/docs/tracks/pt/go-live-process.md
@@ -1,10 +1,10 @@
 ---
 title: 'Realizando o go-live da sua loja'
 id: 1iP90RcJvlrfQhnlxM54wo
-status: PUBLISHED
+status: CHANGED
 createdAt: 2022-12-09T19:12:28.218Z
-updatedAt: 2023-03-27T14:51:55.484Z
-publishedAt: 2023-03-27T14:51:55.484Z
+updatedAt: 2024-05-24T14:32:56.445Z
+publishedAt: 2024-01-31T13:30:12.446Z
 firstPublishedAt: 2022-12-09T22:09:43.345Z
 contentType: trackArticle
 productTeam: Reliability
@@ -18,7 +18,7 @@ Se você já [configurou o funcionamento da sua loja](https://help.vtex.com/pt/t
 
 Neste tutorial você encontra o passo a passo detalhado de como realizar o go-live da sua loja.
 
-![Go-live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/032594f36e1fe4fda13252502060b753/go_live_pt.jpg)
+![Go-live](//images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/032594f36e1fe4fda13252502060b753/go_live_pt.jpg)
 
 <div class = "alert alert-info">
 Note que uma loja em produção é diferente de uma conta em produção. De modo geral, pode-se dizer que para ter uma loja em produção é necessário colocar a conta em produção e realizar o apontamento de DNS. Confira abaixo todos os passos envolvidos nesse processo.
@@ -28,7 +28,7 @@ Note que uma loja em produção é diferente de uma conta em produção. De modo
 
 Antes de realizar o go-live da sua loja, é essencial garantir que você tenha realizado todas as configurações necessárias para o bom funcionamento da sua loja.
 
-Copie esta [Checklist de configuração de loja](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx) e verifique, para cada item, se realizou as configurações de acordo com o funcionamento desejado da loja.
+Copie esta [Checklist de configuração de loja](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f504033fb6e8bf38b639547c5fd8790a/Checklist_de_configura__o_de_loja.xlsx) e verifique, para cada item, se realizou as configurações de acordo com o funcionamento desejado da loja.
 
 <div class="alert alert-warning">
 A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. Cabe à sua equipe definir quais funcionalidades implementar na sua loja e como deverão ser configuradas de maneira a produzir a experiência de loja desejada. Isso significa que a lista pode não contemplar todas as funcionalidades usadas pela sua loja. Ainda assim, é importante verificar todos os aspectos do funcionamento da sua loja, mesmo que não estejam na lista sugerida.
@@ -39,7 +39,7 @@ A checklist indicada acima lista funcionalidades e configurações básicas para
 O processo de go-live da sua loja pode ter variações dependendo de algumas características da sua operação. Além disso, alguns passos são sensíveis ao tempo. Por esses motivos recomendamos que planeje o processo completo do seu go-live com no mínimo 15 dias de antecedência.
 
 <div class = "alert alert-info">
-Se você usa o CMS Legado Portal e deseja migrar para uma frente de loja construída com [CMS IO](https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), siga as instruções no guia [Migrando sua frente de loja do CMS Legado Portal para Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
+  <p>Se você usa o CMS Legado Portal e deseja migrar para uma frente de loja construída com <a href="https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, siga as instruções no guia <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migrando sua frente de loja do CMS Legado Portal para Store Framework</a>.</p>
 </div>
 
 Por motivo de organização e conveniência, este guia divide os passos envolvidos no go-live em quatro estágios:
diff --git a/docs/tracks/pt/google-pay.md b/docs/tracks/pt/google-pay.md
new file mode 100644
index 000000000..f496b1e09
--- /dev/null
+++ b/docs/tracks/pt/google-pay.md
@@ -0,0 +1,111 @@
+---
+title: 'Google Pay'
+id: 61JMBvM5Vanqj6RaJsP8CT
+status: PUBLISHED
+createdAt: 2023-06-27T21:28:37.755Z
+updatedAt: 2024-08-01T17:59:31.657Z
+publishedAt: 2024-08-01T17:59:31.657Z
+firstPublishedAt: 2023-06-27T21:46:39.537Z
+contentType: trackArticle
+productTeam: Shopping
+slug: google-pay
+locale: pt
+trackId: 6X8YyZBoVJpz5R8oXciTyu
+trackSlugPT: carteira-digital-e-wallet
+---
+
+O Google Pay™ é um serviço de pagamentos digitais que possibilita ao usuário não compartilhar os dados reais do seu cartão com a loja, trazendo mais segurança e acelerando a etapa de checkout. Com Google Pay o usuário pode realizar pagamentos por meio de cartões de crédito ou de débito, sem a necessidade de preencher qualquer dado manualmente, e o Google Pay também está disponível em diversos apps, sites e na Carteira do Google.
+
+Os termos de serviço da API do Google Pay se aplicam sempre que o serviço Google Pay for oferecido por um lojista. Para ler os termos, acesse [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
+
+<div class="alert alert-warning">
+<p>O Google Pay não está disponível para Checkout V5 ou versões anteriores do Checkout.</p>
+</div>
+
+## Ativar Google Pay
+
+Para ativar o Google Pay, siga o passo a passo abaixo. 
+
+1. No Admin VTEX, acesse **Configurações da loja > Pagamentos > Carteiras** ou digite **Carteiras **na barra de busca no topo da página.
+2. Selecione a opção **Ativar** para modificar o checkout para incluir a extensão do Google Pay.
+
+<div class="alert alert-info">
+<p>As bandeiras suportadas no Google Pay são as mesmas bandeiras configuradas nas condições de pagamento.</p>
+</div>
+
+Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como nova forma de pagamento. É possível que demore em torno de 10 minutos para que a configuração apareça no Checkout.
+
+![google-pay-checkout-pt](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/6ba2af94c811c8cb76d553f68c5578d6/Screenshot_2024-08-01_at_14.21.25.png)
+
+<div class="alert alert-warning">
+<p>Google Pay, neste momento, não vai suportar assinatura.</p>
+</div>
+
+É necessário ter os seguintes requisitos para utilizar o Google Pay:
+
+* Ter pelo menos uma [condição de pagamento](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) ativa configurada para cartões de crédito ou débito com um [adquirente](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente), definindo qual adquirente irá processar o pagamento da carteira.
+* Utilizar o [Checkout VTEX](https://help.vtex.com/pt/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) na sua loja.
+
+<div class="alert alert-warning">
+  <p>Nas lojas que têm o fluxo de autenticação <a href="https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado e suportado pelo adquirente, o pagamento com o Google Pay seguirá o fluxo nativo de cartão, sendo submetido também ao 3DS. Para mais informações sobre como configurar o fluxo de autenticação, consulte <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar fluxo de autenticação 3DS 2</a>.</p>
+</div>
+
+<div class="alert alert-info">
+<p>Você também pode configurar o Google Pay para ser processado com a Adyen ou Stripe. Para isso, acesse a tela <b>Condições de Pagamento</b> no Admin, clique em <b>Google Pay</b> e selecione a opção desejada.</p>
+</div>
+
+## Consultar transações finalizadas com o Google Pay
+
+Para consultar e verificar transações que foram finalizadas com o Google Pay no pagamento, siga os passos descritos no artigo [Ver detalhes da transação](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy). Na barra de busca da página de transações, digite **Google Pay** para filtrar as transações realizadas com este tipo de pagamento.
+
+![Google Pay Transaction_1](//images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/7529f5dce8a104bc97e546cb31a47843/Google_Pay_Transaction1_PT.png)
+
+Após acessar a transação desejada, clique em `+ Informações` para verificar a informação **Google Pay** descrita no campo `paymentOrigin`.
+
+![Google Pay Transaction_2](//images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/904607c6df63c9168c35435b9bb5068e/Google_Pay_Transaction2_PT.png)
+
+<div class="alert alert-warning">
+  <p>Também é possível identificar transações realizadas com o Google Pay por meio da página <b>Todos os pedidos</b> no Admin. Você precisa somente selecionar o período desejado de busca, <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">exportar os pedidos</a> em um relatório no formato .csv e localizar a informação Google Pay no campo "payment origin".</p>
+</div>
+
+## Adicionar informação do Google Pay no template de compra
+
+Para adicionar a informação que o pedido foi realizado com um cartão advindo do Google Pay no template de email para o comprador, siga as etapas a seguir:
+
+1. No Admin VTEX, acesse **Configurações da loja > Templates de email > Templates** ou digite **Templates **na barra de busca no topo da página.
+2. Acesse os templates de fechamento de compra e aprovação de pagamento.
+3. Após** **todas as menções** **a** `**{{#if lastDigits}} last digits {{lastDigits}}**`**, adicionar a seguinte linha:
+
+`{{/if}} {{#if paymentOrigin}} ({{paymentOrigin}}` 
+
+Com isso, após qualquer menção aos últimos quatro dígitos do cartão desses templates de email, será adicionada a informação "(Google Pay)" caso o pagamento tenha sido feito com a carteira.
+
+<div class="alert alert-info">
+<p>Para lojas provisionadas a partir de Março de 2023, os templates já estarão atualizados com a informação do pagamento do pedido feito com o Google Pay.</p>
+</div>
+
+## FAQ
+
+### Problemas de ativação
+
+* Não é possível ligar a carteira, pois o toggle está desabilitado
+
+Ao se deparar com a mensagem "Você ainda não tem bandeiras habilitadas para Google Pay na sua loja.",** **é preciso acessar as condições de pagamento e garantir que há regras associadas para transacionar cartão com adquirentes.
+
+* O toggle está habilitado, mas não é possível finalizar o processo**
+
+Caso não se depare com a mensagem de sucesso "Google Pay ativado com sucesso." ao ligar o toggle, significa que pode ter havido instabilidade no sistema. Se o problema persistir, o usuário receberá um aviso para contatar o [suporte da VTEX](https://support.vtex.com/hc/pt-br/requests).
+
+### Problemas que podem acontecer na compra
+
+* Aparelho utilizado para finalizar a compra não suporta Google Pay
+
+Ao se deparar com a mensagem "Forma de pagamento indisponível no seu navegador", o usuário deverá tentar fechar a compra em outro navegador ou aparelho.
+
+* Não há regras configuradas para cartão na loja
+
+Caso o lojista não tenha configurado regras de pagamento para cartão, o usuário verá um erro ao selecionar o meio Google Pay de que este método não está disponível.
+
+### Saiba mais
+
+* [DPAN e FPAN: entendendo a segurança no fluxo de pagamentos tokenizados online](https://help.vtex.com/pt/tutorial/dpan-e-fpan-entendendo-a-seguranca-no-fluxo-de-pagamentos-tokenizados-online--3RM7RvhKZ057wja5xVEOqb)
diff --git a/docs/tracks/pt/google-shopping-marketplace.md b/docs/tracks/pt/google-shopping-marketplace.md
index cd6f058d6..01b7c6a5a 100644
--- a/docs/tracks/pt/google-shopping-marketplace.md
+++ b/docs/tracks/pt/google-shopping-marketplace.md
@@ -3,8 +3,8 @@ title: 'Google Shopping'
 id: 2kGKxwD9HKJvTLDTikQ4zG
 status: PUBLISHED
 createdAt: 2021-04-14T14:19:25.417Z
-updatedAt: 2021-04-16T22:47:55.190Z
-publishedAt: 2021-04-16T22:47:55.190Z
+updatedAt: 2024-02-29T19:00:16.087Z
+publishedAt: 2024-02-29T19:00:16.087Z
 firstPublishedAt: 2021-04-15T17:41:07.946Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,7 +16,7 @@ trackSlugPT: configurar-integracao-com-o-google-shopping
 
 O [Google Shopping](https://shopping.google.com/) é uma plataforma na qual um produto é apresentado em listagens gratuitas classificadas de forma orgânica em pesquisas do Google. Ou seja, é um serviço de comparação e rastreamento de preços, que apresenta seus produtos gratuitamente nos resultados de pesquisa de produtos locais.
 
-![google-shopping](https://drive.google.com/uc?export=download&id=1htNbqBqTs4HSdnPnp4Q6__wDzMTYPl6-)
+![Google Shopping](//images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/d9e89361ff7eec1ad054348e16d15432/logo_Google_shopping.png)
 
 Através do Google Shopping, é possível exibir ao consumidor alguns dos atributos do seu produto, tais como imagem, título, preço e nome da sua loja.
 
diff --git a/docs/tracks/pt/hide-product-suggestions-recommendation.md b/docs/tracks/pt/hide-product-suggestions-recommendation.md
index e512ad180..d1d96f6be 100644
--- a/docs/tracks/pt/hide-product-suggestions-recommendation.md
+++ b/docs/tracks/pt/hide-product-suggestions-recommendation.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 Por padrão o inStore inclui uma lista de produtos sugeridos no carrinho e na página de produto.
 
-![inStore recommendation](https://images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
+![inStore recommendation](//images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
 
 Caso deseje ocultar as recomendações, é necessário editar os arquivos `checkout-instore-custom.css` e `checkout-instore-custom.js` presentes no admin do Portal. Por se tratarem de arquivos utilizados em diversos fluxos de uso da aplicação, é importante que você tenha conhecimentos de programação antes de alterá-los, para evitar a quebra de outras funcionalidades.
 
diff --git a/docs/tracks/pt/how-a-split-payment-transaction-works.md b/docs/tracks/pt/how-a-split-payment-transaction-works.md
index 3f79ed1b4..1f0c17dc5 100644
--- a/docs/tracks/pt/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/pt/how-a-split-payment-transaction-works.md
@@ -62,4 +62,4 @@ Esses mesmos R$ 6,50 serão divididos entre marketplace e adquirente. Como o MDR
 
 Confira o diagrama abaixo:
 
-![Split de pagamento](https://images.ctfassets.net/alneenqid6w5/3D3Lso54Ho1lXbelILxaZO/ed7b92307403f708227bb85f492d0984/Split.png)
+![Split de pagamento](//images.ctfassets.net/alneenqid6w5/3D3Lso54Ho1lXbelILxaZO/ed7b92307403f708227bb85f492d0984/Split.png)
diff --git a/docs/tracks/pt/how-clustered-conditions-work.md b/docs/tracks/pt/how-clustered-conditions-work.md
index f6746f729..adc1bd80e 100644
--- a/docs/tracks/pt/how-clustered-conditions-work.md
+++ b/docs/tracks/pt/how-clustered-conditions-work.md
@@ -26,7 +26,7 @@ Desse modo, as regras de prazo e parcelamento serão aplicadas ao(s) consumidor(
 
 Para configurá-las, escolha uma propriedade e, em seguida, selecione os parâmetros para criar um cluster.
 
-![UI - Pagamentos Clusterizados](https://images.ctfassets.net/alneenqid6w5/5CqjpJpWRzVAPpTSUAIt8C/91425fe2c9d9d49b66655419b89abf9a/image.png)
+![UI - Pagamentos Clusterizados](//images.ctfassets.net/alneenqid6w5/5CqjpJpWRzVAPpTSUAIt8C/91425fe2c9d9d49b66655419b89abf9a/image.png)
 
 ## Propriedade
 
@@ -40,7 +40,7 @@ Consequentemente, ele pode criar as propriedades - que podem ser de texto, numé
 
 Sigamos com o exemplo. Na imagem abaixo, a propriedade usada é “Localização Padrão”. Mas outros campos que poderiam ser usados são “E-mail” e “Telefone”, por exemplo.
 
-![Propriedade - PC](https://images.ctfassets.net/alneenqid6w5/3acMvJIDlyTfdbIWKcuweT/80c035726574476b316c91b054d3c741/PC1.png)
+![Propriedade - PC](//images.ctfassets.net/alneenqid6w5/3acMvJIDlyTfdbIWKcuweT/80c035726574476b316c91b054d3c741/PC1.png)
 
 ## Operador 
 
@@ -50,7 +50,7 @@ Na imagem abaixo, a regra será aplicada a todos os clientes que correspondem a
 
 Caso o lojista determinasse a condição “Localização diferente São Paulo” - “diferente” como operador - a regra de pagamento seria aplicada a todos os consumidores da base que não moram em São Paulo.
 
-![Operador](https://images.ctfassets.net/alneenqid6w5/4KHYbVD6ubXXFSW01ZuS9q/8ed89399d9f88f2285cbaefc236b4507/PC2.png)
+![Operador](//images.ctfassets.net/alneenqid6w5/4KHYbVD6ubXXFSW01ZuS9q/8ed89399d9f88f2285cbaefc236b4507/PC2.png)
 
 ## Valor
 Por fim, o último campo é preenchido com um valor relacionado à propriedade escolhida. Sigamos com o exemplo da condição “Localização Igual São Paulo”. 
@@ -61,4 +61,4 @@ Nesse caso, o sistema segmenta os consumidores que correspondam à localização
 
 Caso exista apenas um consumidor que corresponda ao cluster “Localização é São Paulo”, essa regra será aplicadas apenas para ele.
 
-![PC3](https://images.ctfassets.net/alneenqid6w5/3oQrXen2cJCOsLpwRAqT74/3600f14168835dcbeabec367e512805e/PC3.png)
+![PC3](//images.ctfassets.net/alneenqid6w5/3oQrXen2cJCOsLpwRAqT74/3600f14168835dcbeabec367e512805e/PC3.png)
diff --git a/docs/tracks/pt/how-does-vtex-intelligent-search-work.md b/docs/tracks/pt/how-does-vtex-intelligent-search-work.md
index 484af781c..5db51f9b1 100644
--- a/docs/tracks/pt/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/pt/how-does-vtex-intelligent-search-work.md
@@ -3,8 +3,8 @@ title: 'Como o VTEX Intelligent Search funciona?'
 id: 23mytRDsEduqLO0Lo7yufy
 status: PUBLISHED
 createdAt: 2020-03-05T14:57:22.014Z
-updatedAt: 2023-04-13T23:00:35.423Z
-publishedAt: 2023-04-13T23:00:35.423Z
+updatedAt: 2024-04-25T16:53:08.559Z
+publishedAt: 2024-04-25T16:53:08.559Z
 firstPublishedAt: 2020-03-05T19:54:00.932Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -16,74 +16,116 @@ trackSlugPT: vtex-intelligent-search
 
 O Motor de Busca é o centro da inteligência do VTEX Intelligent Search. Ele interpreta o termo buscado e apresenta a listagem filtrada e ordenada de produtos. Essa ferramenta possibilita uma pesquisa mais objetiva, por meio de indexação e tratamento dos dados do catálogo.
 
-Essa funcionalidade é padrão do VTEX Intelligent Search e atende a maioria dos cenários. Contudo, o Motor de Busca também apresenta alguns ajustes para que o resultado da busca seja aperfeiçoado.
+Essa funcionalidade é padrão do VTEX Intelligent Search e atende a maioria dos cenários. Contudo, o Motor de Busca também apresenta alguns ajustes para que o resultado da busca seja aperfeiçoado. Neste guia, apresentamos:
 
-Assim, há um conjunto de configurações que alteram a listagem e a ordenação de produtos exibidos no resultado de busca. São elas:
+* [Comportamento padrão da busca](#comportamento-padrão-da-busca)
+* [Configurações para o comportamento da busca](#configuracoes-para-o-comportamento-da-busca)
+* [Formas alternativas de busca](#formas-alternativas-de-busca)
+* [Indexação](#indexacao)
 
-- __Definição de campos de busca__: define determinadas informações de produto como pesquisáveis. A partir da configuração, toda pesquisa realizada verifica o conteúdo desse campo para assimilar a produtos. Os campos __Nome do produto__, __marca__, __ProductID__, __ProductRefID__, __SKUID__, __SKURefID__ e __EAN__ são definidos por padrão e não podem ser alterados. 
+## Comportamento padrão da busca
 
-É possível buscar por caracteres especiais (`-` e `/`) para encontrar um produto.
+A seguir, apresentamos características do comportamento padrão do Intelligent Search.
+
+### Autocorreção
+
+O usuário pode cometer erros ortográficos ao realizar uma busca. É função da ferramenta interpretar esses erros e apresentar como resultados produtos que se aproximem da pesquisa realizada.
+
+Para isso, o Motor de Busca tenta corrigir o que o usuário digitou de acordo com os itens registrados no Catálogo. Para cada termo pesquisado, uma quantidade específica de caracteres errados é permitida. Essa quantidade de erros aceitos é chamada de _fuzzy_.
 
-_Exemplo_: foi configurado que o campo "cor" é configurável e o produto está cadastrado com o nome  "Tênis Nike Total 90" e com a cor "preta". Se um cliente pesquisar por "Tenis Preto", a ferramenta retornará produtos que possuem o termo "tenis" e cor "preta" no topo do resultado de busca. 
+O _fuzzy_ varia de acordo com o tamanho do termo pesquisado. Por padrão, caso o termo tenha de 3 a 5 caracteres, o _fuzzy_ aplicado será 1, ou seja, é permitido errar 1 caractere. Para termos de 6 caracteres ou mais, o _fuzzy_ aplicado será 2.
 
-- __Definição e ordenação de campos de filtro__: em todos os resultados de busca são apresentados filtros que podem ser selecionados pelo usuário. Por padrão, alguns filtros já são pré-definidos, mas é possível criar de acordo com a necessidade da loja. Outro ponto customizável é a ordem de visualização.
+Os erros previstos considerando *fuzzy* = 1 são:
 
- _Exemplos_: Preço, Categorias e Marca.
+* Inserir 1 caractere a mais.
+* Remover 1 caractere.
+* Trocar 1 caractere.
+* Trocar 2 caracteres que estiverem lado a lado.
 
-- __Configuração da autocorreção__: o usuário pode cometer erros ortográficos ao realizar uma busca. É função da ferramenta interpretar esses erros e apresentar como resultados produtos que se aproximem da pesquisa realizada.
+Exemplo: suponha que um cliente queira pesquisar pelo termo `bola`. Seguindo a configuração padrão (*fuzzy* = 1 para termos de 3 a 5 caracteres), o Motor de Busca vai apresentar o resultado `bola` para qualquer busca que contenha os erros aceitos, como:
+
+* `bolha` (inserir 1 caractere a mais)
+* `boa` (remover 1 caractere)
+* `bora` (trocar 1 caractere)
+* `obla` (trocar 2 caracteres que ficam um do lado do outro entre eles)
+
+<div class ="alert alert-info">
+	<p>Espaços em branco não são considerados no <em>fuzzy</em>, então <code>base ball</code> não será corrigido para <code>baseball</code>, por exemplo. Recomendamos o uso de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinônimos</a> para esses casos.</p>
+</div>
 
- Para isso, o Motor de Busca tenta corrigir o que o usuário digitou de acordo com os itens registrados no catálogo. Para cada termo pesquisado, uma quantidade específica de caracteres errados é permitida. Essa quantidade de erros aceitos é chamada de fuzzy.
+### Resultado mínimo
 
- O fuzzy varia de acordo com o tamanho do termo pesquisado. Por padrão, caso o termo tenha de 3 a 5 caracteres, o fuzzy aplicado será 1, ou seja, é permitido errar 1 caractere. Para termos de 6 caracteres ou mais, o fuzzy aplicado será 2.
+A quantidade mínima de resultados exibidos a partir de qualquer busca realizada é 1. Em qualquer busca, se o número mínimo de resultados não for atingido, a [autocorreção](#autocorrecao) é aplicada.
 
- Os erros previstos considerando ```fuzzy = 1``` são:
-   - Inserir 1 caractere a mais.
-   - Remover 1 caractere.
-   - Trocar 1 caractere.
-   - Trocar 2 caracteres que estiverem lado a lado.
+Em uma busca com múltiplos termos, ocorre a lógica a seguir:
 
- _Exemplo_:
- Suponha que um cliente queira pesquisar pelo termo “bola”. Seguindo a configuração padrão (```fuzzy = 1``` para termos de 3 a 5 caracteres), o Motor de Busca vai apresentar o resultado “bola” para qualquer busca que contenha os erros aceitos, como:
-   - bolha (inserir 1 caractere a mais)
-   - boa (remover 1 caractere)
-   - bora (trocar 1 caractere)
-   - obla (trocar 2 caracteres que ficam um do lado do outro entre eles)
+1. Se o resultado mínimo não for atingido mesmo com a autocorreção inicial, a busca passa a incluir resultados mais abrangentes, que apresentam qualquer um dos termos pesquisados. Por exemplo, quando um usuário pesquisa por "tenis nike", mas o catálogo não possui nenhum produto com esse nome, a busca pode apresentar como resultado um produto com apenas o termo "tenis" no nome.
+2. Se a busca abrangente não apresentar o resultado mínimo, ela será repetida aplicando a autocorreção novamente a cada um dos termos.
 
-<div class="alert alert-info" role="alert">
-<p> Espaços em branco não são considerados no fuzzy, então “base ball” não será corrigido para “baseball”. Recomendamos o uso de sinônimos para esses casos.</p>
+<div class= "alert alert-warning">
+<p>Buscas com múltiplos termos são mais eficientes quando o cliente ordena os resultados por relevância, já que elas podem ter um número maior de resultados além do contexto que foi buscado. Na ordenação por relevância, ainda priorizam-se os itens relacionados aos múltiplos termos. Porém, ao aplicar outras ordenações, como preço ou mais vendidos, a ordem dos resultados depende desses valores numéricos e não necessariamente prioriza itens que contêm mais palavras dos termos de busca.</p>
 </div>
 
-- __Configuração de relevância__: funcionalidade que define a ordem dos produtos no resultado de busca. Essa configuração permite atribuir pesos e priorizar determinados critérios utilizados pelo Motor de Busca, como popularidade, data de lançamento do produto e participação em promoções, por exemplo. A relevância de um produto é composta pela combinação dos pesos e prioridades definidos por cada lojista.
+### Limite de paginação
 
- _Exemplo_: um lojista configurou que o critério Promoção possui uma relevância maior que outros critérios. Dessa forma, quando o cliente pesquisa pelo termo “camiseta” na busca interna da loja, as camisetas incluídas em promoções tendem a aparecer primeiro nos resultados, dependendo dos pesos atribuídos aos outros critérios.
+O VTEX Intelligent Search limita o resultado de busca a 50 páginas. Esse limite incentiva o uso de filtros, permitindo uma navegação mais relevante e focada para o usuário.
 
- Para mais informações sobre como personalizar a ordenação dos resultados de acordo com as necessidades da sua loja, leia o artigo [Configuração de relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+## Configurações para o comportamento da busca
 
-- __Configuração de resultado mínimo__: permite configurar a quantidade mínima de produtos para a consulta de múltiplos termos. Caso esse número não seja atingido, a busca apresenta resultados mais abrangentes, que respeitam somente um dos termos pesquisados.
+Há um conjunto de configurações que alteram a listagem e a ordenação de produtos exibidos no resultado de busca. Nas seções a seguir, você verá as principais definições que afetam o comportamento da busca.
 
- _Exemplo_: foi configurado que o resultado mínimo para consultas com múltiplos termos é __três__. O usuário realizou a pesquisa por "tenis nike", mas o catálogo possui apenas __quatro__ produtos com esse nome. A plataforma vai apresentar primeiro produtos que possuem os termos “tenis nike”, depois produtos com o termo “tenis” e, em seguida, os que possuem o termo “nike”.
+### Definição de campos pesquisáveis
 
-- __Limite de paginação__: limita o resultado de busca a 50 páginas. Esse limite incentiva o uso de filtros, permitindo uma navegação mais relevante e focada para o usuário.
+Determina quais informações de produto são pesquisáveis. A partir da configuração, toda pesquisa realizada na barra de busca verifica o conteúdo desses campos para gerar resultados de busca. Confira a tabela a seguir para entender quais são as informações pesquisáveis por padrão e as demais opções de configuração:
 
-<div class="alert alert-warning">
-  <p>O VTEX Intelligent Search não oferece a funcionalidade de palavras substitutas nativamente. Para ativar o uso de palavras substitutas pelo VTEX Intelligent Search, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso suporte</a>.</p>
+| Informações | Configuração |
+| - | - |
+| Nome do produto, marca, ID do produto (`ProductID`), código de referência do produto (`ProductRefID`), ID do SKU (`SKUID`), código de referência do SKU (`SKURefID`) e EAN | Essas informações são pesquisáveis por **padrão** no VTEX Intelligent Search. Para remover alguma delas, entre em contato com o nosso [Suporte](https://help.vtex.com/support?/cultureInfo=en-us). |
+| Especificações de produto e de SKU | Para incluir as especificações desejadas como campos pesquisáveis, é preciso configurar a opção **Especificações pesquisáveis** no Admin VTEX, em **Intelligent Search** > **Configurações da busca**.<br /><br /> Por exemplo, se uma camisa não tiver a cor no nome do produto ou do SKU, por padrão, o Intelligent Search não identifica esse atributo em uma pesquisa por "camisa azul", trazendo como resultado camisas de diversas cores. Contudo, se a especificação de cor estiver configurada como pesquisável, a busca consegue trazer camisas azuis nas primeiras posições.<br /><br /> Para mais detalhes sobre a definição de especificações pesquisáveis, acesse o guia [Configurações da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#configuracoes-gerais). Saiba mais sobre especificações em [Especificações de produto e de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP). |
+| Código do fabricante (`ManufactureID`) | Entre em contato com o nosso [Suporte](https://help.vtex.com/support?/cultureInfo=en-us) para definir esse campo como pesquisável. | 
+
+_Exemplo_: foi configurado que a especificação "cor" é pesquisável e o produto está cadastrado com o nome "Tênis Nike Total 90" e com a cor "preta". Se um cliente pesquisar por "Tenis Preto", a ferramenta retornará produtos que possuem o termo "tenis" e cor "preta" no topo do resultado de busca.
+
+É possível buscar por caracteres especiais (`-` e `/`) para encontrar um produto.
+
+<div class ="alert alert-warning">
+	<p>A escolha dos campos de busca afeta as possibilidades das <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">Regras de merchandising</a>, pois apenas campos pesquisáveis podem ser utilizados para configurar as regras. Por exemplo, ao definir somente o campo <strong><code>SKUID</code> </strong>como pesquisável, não será possível promover um <strong><code>ProductID</code> </strong>ou um <strong><code>ProductRefID</code> </strong>utilizando Regras de merchandising.</p>
+</div>
+
+### Definição e ordenação de campos de filtro
+
+Em todos os resultados de busca são apresentados filtros que podem ser selecionados pelo usuário. Por padrão, alguns filtros são pré-definidos, mas é possível criar outros de acordo com a necessidade da loja. Outro ponto customizável é a ordem de visualização. Exemplo: em uma lista de resultados de busca, podem existir os filtros de Preço, Categorias e Marca.
+
+### Configuração de relevância
+
+A relevância é a funcionalidade que define a ordem dos produtos no resultado de busca. Essa configuração permite atribuir pesos e priorizar determinados critérios utilizados pelo Motor de Busca, como popularidade, data de lançamento do produto e participação em promoções, por exemplo. A relevância de um produto é composta pela combinação dos pesos e prioridades definidos por cada lojista.
+
+_Exemplo_: um lojista configurou que o critério Promoção possui uma relevância maior que outros critérios. Dessa forma, quando o cliente pesquisa pelo termo “camiseta” na busca interna da loja, as camisetas incluídas em promoções tendem a aparecer primeiro nos resultados, dependendo dos pesos atribuídos aos outros critérios.
+
+Para mais informações sobre como personalizar a ordenação dos resultados de acordo com as necessidades da sua loja, leia o artigo [Configuração de relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+<div class ="alert alert-info">
+	<p>Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções. Usando o comando <code>map=productClusterIds</code>, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar <code>productClusterNames</code>, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search.</p>
 </div>
 
 ## Formas alternativas de busca
 
-É possível buscar IDs na URL da loja ou na própria barra de busca. Nesta busca, você pode procurar por apenas um item ou por uma lista de itens. 
+É possível buscar pelo ID de um ou mais itens na barra de busca ou adicionando parâmetros de busca (*query*) na URL da loja.
 
-Para buscar na URL da sua loja, siga o formato a seguir:
+### Match parcial
 
-- Exemplo para pesquisa de um item: `[endereço da conta]/[tipo do id]:[id_1]?q=[tipo do id]&map=ft`
-- Exemplo para pesquisa de lista: `[endereço da conta]/[tipo do id]:[id_1];[id_2];[id_3]?q=[tipo do id]:[id_1];[id_2];[id_3]&map=ft`
+Ao digitar somente os primeiros dígitos exatos do ID do produto (`ProductID`), código de referência do produto (`ProductRefID`), ID do SKU (`SKUID`), código de referência do SKU (`SKURefID`) ou EAN na barra de busca, o Intelligent Search fará o match parcial com produtos e SKUs ativos na loja, incluindo-os nos resultados da busca.
+
+Por exemplo, se o ID do produto for `123456789` e a busca for `123`, esse produto aparecerá entre os resultados. Porém, se a busca for `234`, sem algum dos primeiros dígitos do ID, esse produto não aparecerá.
+
+### URL
 
-Os possíveis tipos de valores para o campo tipo do ID são `product.id`, `sku.id`,`sku.ean`, `sku.reference` ou `id` (ProductID, ProductRefID, SKUID, SKURefID e EAN). Importante destacar que todos os IDs devem pertencer ao mesmo tipo. 
+Para buscar a partir da URL da sua loja, adicione parâmetros de busca (*query*) no final da URL da loja, respeitando uma das estruturas a seguir:
 
-Você pode buscar IDs na barra de busca das seguintes formas:
+- Exemplo para pesquisa de um item: `[endereço da conta]/[tipo do id]:[id_1]?q=[tipo do id]&map=ft`
+- Exemplo para pesquisa de lista de itens: `[endereço da conta]/[tipo do id]:[id_1];[id_2];[id_3]?q=[tipo do id]:[id_1];[id_2];[id_3]&map=ft`
 
-1. Digitando apenas os primeiros dígitos do ID na barra de busca. É importante destacar os digítos devem que ser exatos, por exemplo caso o ID seja `0123-456-789` e for buscado por `123`, o produto não retornará. 
-2. Por queries, seguindo o formato a seguir:
+Os possíveis tipos de valores para o campo tipo do ID são `product.id`, `sku.id`,`sku.ean`, `sku.reference` ou `id` (ProductID, ProductRefID, SKUID, SKURefID e EAN). Importante destacar que todos os IDs buscados devem pertencer ao mesmo tipo. 
 
   - **Busca por SKU ID:** `?q=sku.id:<id>` ou `?q=sku:<id>`
   - **Busca por EAN:** `?q=sku.ean:<id> `
@@ -103,7 +145,4 @@ O processo de indexação é seguro e conta com regras de repescagem – caso um
 
 A indexação também é muito importante para analisar, tratar e organizar os dados da melhor forma para serem exibidos nos resultados.
 
-<div class="alert alert-info" role="alert">
-<p>Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções.  Usando o comando `map=productClusterIds`, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar `productClusterNames`, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search. </p>
-</div>
-
+Confira [Histórico da indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) para mais informações sobre como monitorar o processo de indexação.
diff --git a/docs/tracks/pt/how-message-center-works.md b/docs/tracks/pt/how-message-center-works.md
index 3e9d5eef6..d3b7fd1ce 100644
--- a/docs/tracks/pt/how-message-center-works.md
+++ b/docs/tracks/pt/how-message-center-works.md
@@ -43,7 +43,7 @@ Ao entrar no Message Center e clicar em __Templates__, você encontra a lista de
 
 Vamos entender as informações presentes nesses cards.
 
-![Emails 1 1](https://images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
+![Emails 1 1](//images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
 
 - Nome do template para identificação interna. Este *não* é o assunto do e-mail.
 - Aplicação ou módulo ao qual o template pertence, sinalizado em verde.
@@ -53,7 +53,7 @@ Vamos entender as informações presentes nesses cards.
 
 Para buscar templates, você pode usar filtros por aplicação (módulo) e tipo (mensagem padrão ou personalizada).
 
-![Emails 1 2](https://images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
+![Emails 1 2](//images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
 
 ### Remetentes
 
@@ -61,7 +61,7 @@ Aqui, o usuário confere e edita as informações - nome, e-mail e dados do serv
 
 Estas são as informações apresentadas nos cards dos remetentes:
 
-![Emails 1 3](https://images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
+![Emails 1 3](//images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
 
 - Nome do remetente, para identificação interna.
 - Tipo de servidor SMTP, que pode ser da VTEX ou da própria loja.
diff --git a/docs/tracks/pt/how-the-payments-module-works.md b/docs/tracks/pt/how-the-payments-module-works.md
index 58c3d5ef4..3d9e2c38d 100644
--- a/docs/tracks/pt/how-the-payments-module-works.md
+++ b/docs/tracks/pt/how-the-payments-module-works.md
@@ -3,8 +3,8 @@ title: 'Como funciona o módulo de Pagamentos'
 id: kdPbEIWf8Xq8tESQvViMB
 status: PUBLISHED
 createdAt: 2019-11-13T18:30:00.279Z
-updatedAt: 2021-09-21T14:41:47.003Z
-publishedAt: 2021-09-21T14:41:47.003Z
+updatedAt: 2024-07-24T18:38:45.637Z
+publishedAt: 2024-07-24T18:38:45.637Z
 firstPublishedAt: 2019-11-21T22:49:51.417Z
 contentType: trackArticle
 productTeam: Financial
@@ -23,15 +23,15 @@ Antes de explorarmos as funcionalidades dentro de *Pagamentos* no Admin da VTEX,
 </div>
 
 ## Gateway 
-Um gateway (também chamado de gateway de pagamento) é um _sistema que efetua a transmissão dos dados das compras realizadas na sua loja no momento do checkout_.
+Um gateway (também chamado de gateway de pagamento) é um sistema que efetua a transmissão dos dados das compras realizadas na sua loja no momento do checkout.
 
 Como primeiro player do fluxo, ele é responsável por enviar as informações do pagamento, recebidas no checkout, aos atores financeiros que integram a sequência do fluxo de pagamento (como adquirentes, bandeiras e bancos emissores). 
 
 Em seguida, obtém um retorno sobre a aprovação do pagamento e continuação do fluxo de compra, ou seu cancelamento. 
 
-Como agentes intermediários entre um e-commerce e seus meios de pagamento, os **gateways** _atuam como um terminal_, integrando em um só lugar todas as movimentações realizadas entre os players do fluxo de pagamento.  
+Como agentes intermediários entre um e-commerce e seus meios de pagamento, os **gateways** atuam como um terminal, integrando em um só lugar todas as movimentações realizadas entre os players do fluxo de pagamento.  
 
-> Exemplos de gateway: Braspag e Mundipagg.
+Exemplos de gateway: Pagar.me e Stripe.
 
 ## Adquirente 
 Um adquirente (também chamado de credenciador) é uma _empresa especializada em processar pagamentos_, isto é, fazer a liquidação financeira das transações de uma loja por meio de cartões de crédito e débito. 
@@ -40,7 +40,7 @@ Por meio de sua rede de parceiros credenciados (ou rede de adquirência), ele po
 
 Quando tudo está em ordem e uma compra é autorizada pelos outros players do fluxo de compra, o adquirente fica responsável por repassar os valores (cobrados do cliente pelo banco emissor) para a conta da sua loja.
 
-> Exemplos de aquirente: Rede, Cielo, GetNet e Stone.
+Exemplos de aquirente: Rede, Cielo, GetNet e Stone.
 
 ## Subadquirente  
 Um subdadquirente é uma _empresa que processa pagamentos e transmite suas informações para os outros players envolvidos no fluxo de pagamento_. 
@@ -49,11 +49,12 @@ Como facilitador, o seu papel é semelhante ao de um adquirente, mas não o subs
 
 Portanto, o **subadquirente** pode ser entendido como uma espécie de intermediador entre adquirente e loja.
 
-> Exemplos de subadquirente: Paypal e PagSeguro.
+Exemplos de subadquirente: Paypal e PagSeguro.
+
 Para saber mais sobre as [vantagens e desvantagens de se incluir um subadquirente no seu fluxo](https://help.vtex.com/pt/tutorial/diferenca-entre-adquirentes-subadquirentes-e-gateways-no-brasil?locale=pt "Atores financeiros"), confira nosso artigo.   
 
 ## Bandeira de Cartão
-Bandeiras são _empresas responsáveis por definir as regras de negócio para compras realizadas com cartão de crédito_, como a quantidade de parcelas em que você pode dividir o pagamento e o número de estabelecimentos em que ele é aceito, nacional e internacionalmente.
+Bandeiras são empresas responsáveis por definir as regras de negócio para compras realizadas com cartão de crédito, como a quantidade de parcelas em que você pode dividir o pagamento e o número de estabelecimentos em que ele é aceito, nacional e internacionalmente.
 
 São elas que definem os padrões pelos quais os adquirentes devem processar as transações realizadas por esse meio de pagamento.
 
@@ -61,27 +62,27 @@ No fluxo de pagamento por cartão de crédito, a **bandeira** recebe do adquiren
 
 Dessa forma, a bandeira serve tanto para regular o uso do cartão quanto como ponte entre a adquirente e o banco.
 
-> Exemplos de bandeiras de cartão: Mastercard, American Express e Visa.   
+Exemplos de bandeiras de cartão: Mastercard, American Express e Visa.   
 
 ## Banco Emissor
-Banco Emissor é a _instituição financeira responsável pelos meios de pagamento, sejam eles boletos bancários, cartões de débito ou de crédito_.
+Banco Emissor é a instituição financeira responsável pelos meios de pagamento, sejam eles boletos bancários, cartões de débito ou de crédito.
 
 É ele que, ao receber os dados de uma compra feita na sua loja, vai autorizar ou não a venda (dependendo do limite de crédito ou do dinheiro disponível na conta do usuário). 
 
 Na VTEX, é possível configurar as condições especiais para pagamentos realizados através de **bancos** específicos, funcionalidade que exploraremos mais adiante. 
 
-> Exemplos de bancos emissores:  Itaú, Santander, Bradesco e Citibank.  
+Exemplos de bancos emissores:  Itaú, Santander, Bradesco e Citibank.  
 
 ## Antifraude  
 O antifraude é um _sistema especializado em analisar as compras realizadas nos sites, com o intuito de identificar operações fraudulentas_. 
 
 Ele coleta dados sobre o comportamento dos usuários e os comparam com padrões suspeitos para, então, aprovar ou não o pedido. Assim, o **antifraude** adiciona uma camada a mais de segurança para sua loja.
 
-> Exemplos de antifraudes:  ClearSale e a Konduto.  
+Exemplos de antifraudes:  ClearSale e a Konduto.  
 
 ## Certificação PCI SSC
-O PCI Security Standards Council é um _fórum global aberto para o contínuo desenvolvimento, aprimoramento, armazenamento, disseminação e implementação de padrões de segurança para a proteção de dados_. 
+O PCI Security Standards Council é um fórum global aberto para o contínuo desenvolvimento, aprimoramento, armazenamento, disseminação e implementação de padrões de segurança para a proteção de dados. 
 
 [A plataforma VTEX possui um gateway próprio com **certificação PCI**](https://help.vtex.com/pt/tutorial/o-que-e-o-pci-ssc--4jo3Vkox3amSO2w4qIWa0E "PCI SSC"), o que significa que os dados de todos os pagamentos realizados na sua loja estão protegidos de acordo com os mais altos padrões de segurança. 
 
-> __Se quiser aprofundar os conceitos de gateway, adquirente, subadquirente, bandeira, banco emissor e antifraude, confira nosso [artigo sobre agentes financeiros no Brasil](https://help.vtex.com/pt/tutorial/diferenca-entre-adquirentes-subadquirentes-e-gateways-no-brasil?locale=pt "Agentes financeiros ").
+Se quiser aprofundar os conceitos de gateway, adquirente, subadquirente, bandeira, banco emissor e antifraude, confira nosso [artigo sobre agentes financeiros no Brasil](https://help.vtex.com/pt/tutorial/diferenca-entre-adquirentes-subadquirentes-e-gateways-no-brasil?locale=pt "Agentes financeiros ").
diff --git a/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md b/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md
index fc66acb00..553f905f3 100644
--- a/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md
+++ b/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md
@@ -33,7 +33,7 @@ Após recarregar o inStore, quando for imprimir um pedido verá esse texto extra
 Exemplo rápido:
 
 Antes de adicionar o texto extra teriamos uma impressão da seguinte forma:
-![inStore recommended text before](https://images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
+![inStore recommended text before](//images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
 
 Ao alterar o arquivo `checkout-instore-custom.js` colocando o seguinte texto extra:
 
@@ -44,6 +44,6 @@ window.INSTORE_CONFIG = {
 ```
 
 Agora quando for impresso o pedido, teremos:
-![inStore recommended text after](https://images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
+![inStore recommended text after](//images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
 
 
diff --git a/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md b/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md
index 7be3da08f..a685c5bfe 100644
--- a/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md
+++ b/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 Se você configurou sua loja utilizando o fluxo de __Easy Setup__ já foi criada uma loja para você no __Admin das lojas__ dentro do VTable da VTEX (https://{{AccountName}}.myvtex.com/admin/vtable).
 
-![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Clique em __Admin dos lojas__ para abrir a tabela onde você verá as lojas físicas.
 
@@ -24,7 +24,7 @@ Se você não usou o __Easy Setup__ e assim não ver nenhuma loja cadastrada, cr
 
 Caso você já tenha cadastrado uma loja por meio do __Easy Setup__, você verá o registro dessa loja criada como na imagem a seguir.
 
-![vtable-admin-das-lojas-2](https://images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
+![vtable-admin-das-lojas-2](//images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
 
 Para alterar qualquer dado, incluindo a política comercial da loja, basta alterar a celula relacionada e depois clicar no botão de __Salvar__.
 
diff --git a/docs/tracks/pt/how-to-configure-a-custom-payment.md b/docs/tracks/pt/how-to-configure-a-custom-payment.md
index c19a1b2fd..a8ba38c59 100644
--- a/docs/tracks/pt/how-to-configure-a-custom-payment.md
+++ b/docs/tracks/pt/how-to-configure-a-custom-payment.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamentos customizados'
 id: 1wWt35dRwEboRs1nrSx7G0
 status: PUBLISHED
 createdAt: 2019-11-12T14:02:06.237Z
-updatedAt: 2023-03-21T19:57:00.742Z
-publishedAt: 2023-03-21T19:57:00.742Z
+updatedAt: 2023-10-18T14:41:42.080Z
+publishedAt: 2023-10-18T14:41:42.080Z
 firstPublishedAt: 2019-11-25T15:33:37.696Z
 contentType: trackArticle
 productTeam: Financial
@@ -36,7 +36,7 @@ Permite que você utilize um cartão de crédito da loja com uma das seguintes b
 3.  Selecione uma das opções de pagamento customizado.  
 4.  Preencha os campos do formulário e clique em  **Salvar**.
 
-![PT Pagamento Customizado](https://images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
+![PT Pagamento Customizado](//images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
 
 Após essa configuração, será necessária a criação da [Condição de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento/).  
 
diff --git a/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
index 6f0832a2e..be4b2a005 100644
--- a/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 Entre as opções oferecidas pela **inStore** ao concluir uma venda, existe uma que permite imprimir o resumo do pedido.
 
-![PT-Venda corfimada](https://images.ctfassets.net/alneenqid6w5/4S51lvnSiCJIyH2IiG49Uy/2b3a3dfd3a7248080339e9e4a16efd93/PT-Venda_confirmada.png)
+![PT-Venda corfimada](//images.ctfassets.net/alneenqid6w5/4S51lvnSiCJIyH2IiG49Uy/2b3a3dfd3a7248080339e9e4a16efd93/PT-Venda_confirmada.png)
 
 Para configurar esta opção, serão necessárias duas pequenas etapas:
   1. Pelo Admin VTEX, ative a opção de configuração do dispositivo no menu inStore
@@ -28,7 +28,7 @@ Hoje, essa configuração está presente no administrador do portal, mais especi
 
 Para habilitar a opção _"Configurar dispositivo"_, você deve encontrar o objeto **_window.INSTORE_CONFIG_** presente neste arquivo e adicionar a propriedade **_configureDeviceEnabled_** com o valor **_true_**, e também adicionar o objeto **_printingConfig_** à propriedade **_printByBroker_** com o valor true, para que o inStore permita o uso da propriedade opção dentro do menu, como mostra a imagem de exemplo abaixo:
 
-![PT-Configurar dispositivo](https://images.ctfassets.net/alneenqid6w5/FNNbs1nFbkwbQHD4LfMx5/639002d286b1c502cc8079a2b6b64aad/PT-Configurar_dispositivo.png)
+![PT-Configurar dispositivo](//images.ctfassets.net/alneenqid6w5/FNNbs1nFbkwbQHD4LfMx5/639002d286b1c502cc8079a2b6b64aad/PT-Configurar_dispositivo.png)
 
 Não exclua nenhuma das outras propriedades presentes neste objeto. O resultado deve ser algo como:
 
@@ -62,11 +62,11 @@ printPageAutomatically: true
   2. Abra o aplicativo inStore e entre na loja onde deseja configurar a impressora.
   3. No menu do inStore, no bloco "Configurações", a opção "Configurar o dispositivo" deve aparecer. Clique ali.
 
-![PT-Barra inStore](https://images.ctfassets.net/alneenqid6w5/3D4dG6jMeBrKYFzdatmWID/4a0c6e1daa1c7f324174dc87d0119ca7/PT-Barra_inStore.png)
+![PT-Barra inStore](//images.ctfassets.net/alneenqid6w5/3D4dG6jMeBrKYFzdatmWID/4a0c6e1daa1c7f324174dc87d0119ca7/PT-Barra_inStore.png)
 
   4. Você encontrará o resumo do dispositivo configurado. Se for a primeira vez, as informações estarão vazias. Se um dispositivo já tiver sido configurado anteriormente, algumas informações sobre o dispositivo serão exibidas _(Nome do dispositivo e Impressora padrão)_. Clique na opção "Editar".
   
-  ![PT-Dispositivo via Broadcast](https://images.ctfassets.net/alneenqid6w5/5EqfgcZGdhiLtJcZmYkqGb/66c7deeb361ad97d98cf649458f09758/PT-Dispositivo_via_Broadcast.png)
+  ![PT-Dispositivo via Broadcast](//images.ctfassets.net/alneenqid6w5/5EqfgcZGdhiLtJcZmYkqGb/66c7deeb361ad97d98cf649458f09758/PT-Dispositivo_via_Broadcast.png)
   
   5. Um formulário aparecerá indicando os dados do _AppKey_, _AppToken_ e o nome com o qual você deseja identificar o dispositivo. Após inserir esses dados, clique em "Configurar".
   6. Por fim, incluindo os dados acima, será possível selecionar a impressora na lista de opções. A ideia é selecionar uma dessas opções e clicar em “Configurar” novamente.
diff --git a/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
index c207f9966..c9235e07a 100644
--- a/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
@@ -3,8 +3,8 @@ title: 'Criar ou editar template de e-mail transacional'
 id: 335JZKUYgvYlGOJgvJYxRO
 status: PUBLISHED
 createdAt: 2020-01-10T13:13:48.069Z
-updatedAt: 2021-02-11T13:19:34.511Z
-publishedAt: 2021-02-11T13:19:34.511Z
+updatedAt: 2024-06-11T19:54:28.554Z
+publishedAt: 2024-06-11T19:54:28.554Z
 firstPublishedAt: 2020-01-13T14:38:32.506Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -23,6 +23,10 @@ Para editar um template de e-mail transacional, siga os passos abaixo.
 3. Altere o título do e-mail e o destinatário (os valores entre chaves duplas são variáveis; vamos aprender no próximo artigo como lidar com elas). Você pode incluir destinatários em cópia (`CC`) e cópia oculta (`CCO`).
 4. Deixe a flag __Usar o remetente padrão__ para usar o endereço de e-mail cadastrado como padrão, conforme explicado no artigo anterior desta trilha.
 
+<div class = "alert alert-info">
+A lista de templates está disponível no artigo <a href="https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">Templates de emails transacionais referentes ao pedido</a>.
+</div>
+
 É no campo __HTML__ que você encontra o código HTML do template. Você pode editar o código no próprio campo ou copiá-lo para o editor de sua preferência, editar e depois colar novamente no campo do template.
 
 O __preview__ renderizado por esse código é mostrado no box logo abaixo. Você pode selecionar três tamanhos de tela diferentes para testar a responsividade do código.
diff --git a/docs/tracks/pt/how-to-get-started.md b/docs/tracks/pt/how-to-get-started.md
index 997a27d04..4416e19e3 100644
--- a/docs/tracks/pt/how-to-get-started.md
+++ b/docs/tracks/pt/how-to-get-started.md
@@ -16,17 +16,17 @@ trackSlugPT: suiteshare
 
 Após realizar o seu cadastro na **VTEX Assisted Sales (SuiteShare)**, você pode estar em uma dessas duas situações: No trial de 7 dias do plano Enterprise ou no plano que você já contratou conosco. 
 
-![Suitshare-Como começar](https://images.ctfassets.net/alneenqid6w5/8fSuhGRJ2V9P3SJUz2lgB/211f16f93cc9b6b056171968f45db640/Screenshot_2022-08-24_at_17-39-46_Como_come__ar.png)
+![Suitshare-Como começar](//images.ctfassets.net/alneenqid6w5/8fSuhGRJ2V9P3SJUz2lgB/211f16f93cc9b6b056171968f45db640/Screenshot_2022-08-24_at_17-39-46_Como_come__ar.png)
 
 Caso você não não saiba em que situação está o seu plano, você pode consultar em **Minha conta**: 
 
-![Suitshare-Como começar2](https://images.ctfassets.net/alneenqid6w5/3NmGx5TTBsOZlrFSIqIwNR/bb96395f146e9ea661acccd1615fd652/Screenshot_2022-08-24_at_17-39-52_Como_come__ar.png)
+![Suitshare-Como começar2](//images.ctfassets.net/alneenqid6w5/3NmGx5TTBsOZlrFSIqIwNR/bb96395f146e9ea661acccd1615fd652/Screenshot_2022-08-24_at_17-39-52_Como_come__ar.png)
 
 O primeiro passo dentro da **VTEX Assisted Sales (SuiteShare)** é [criar os links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB) de Whatsapp que serão utilizados. Os links são a maneira mais fácil para que o seu cliente entre em contato com você via Whatsapp em apenas um clique. Para facilitar o processo de criação, você pode [acessar o nosso tutorial](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB) que irá lhe auxiliar na criação dos links.
 
 Após finalizar a criação dos seus links, você pode gerenciá-los através da aba de links, gerar um [QRCode](https://help.vtex.com/pt/tutorial/qr-code-suiteshare--t7faoKDUUr4ZZlrfS0sXV) para utilizar em materiais impressos, descobrir o número de cliques e data de criação.
 
-![Suitshare-Como começar3](https://images.ctfassets.net/alneenqid6w5/2fQZjEXKihad8NTPxkfHgB/a10e14d441d00734cfa72d68221a53c8/Screenshot_2022-08-24_at_17-39-56_Como_come__ar.png)
+![Suitshare-Como começar3](//images.ctfassets.net/alneenqid6w5/2fQZjEXKihad8NTPxkfHgB/a10e14d441d00734cfa72d68221a53c8/Screenshot_2022-08-24_at_17-39-56_Como_come__ar.png)
 
 Com os links criados, podemos passar para os próximos passos da nossa jornada. Defina o maior desafio da sua empresa para começar: 
 
diff --git a/docs/tracks/pt/how-vtex-support-works.md b/docs/tracks/pt/how-vtex-support-works.md
new file mode 100644
index 000000000..e5d05f019
--- /dev/null
+++ b/docs/tracks/pt/how-vtex-support-works.md
@@ -0,0 +1,43 @@
+---
+title: 'Funcionamento do Suporte VTEX'
+id: 2Ik9CGbPeZIHHaYFsuyId3
+status: PUBLISHED
+createdAt: 2024-02-20T21:27:52.565Z
+updatedAt: 2024-02-22T14:09:20.551Z
+publishedAt: 2024-02-22T14:09:20.551Z
+firstPublishedAt: 2024-02-22T14:09:20.551Z
+contentType: trackArticle
+productTeam: Others
+slug: funcionamento-do-suporte-vtex
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+O Suporte VTEX é prestado de forma online e permite a abertura de tickets com diferentes níveis de prioridade, dependendo da região da operação da loja. A abertura de tickets ocorre na [página de suporte](https://help.vtex.com/pt/support) e requer [autenticação da conta do usuário](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz#autenticacao-para-plataforma-e-frente de loja). Existem três métodos de autenticação disponíveis:
+
+- Token recebido por email registrado na loja.
+- Login usando a conta do Google.
+- Email e senha com autenticação de dois fatores via aplicativo ou SMS.
+
+<div class="alert alert-warning">
+Para obter a autorização de autenticação, é necessário que o <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512">usuário</a> tenha acesso ao Admin VTEX e um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete">perfil de acesso</a> associado a <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos do License Manager</a>.
+</div>
+
+O Suporte VTEX é dividido por regiões, e cada região possui sua própria definição de nível de serviço (SLA de atendimento), prioridade e disponibilidade da equipe de Customer Excellence (CX) daquela região. As regiões onde o suporte atua são as seguintes:
+
+- Brasil
+- América Latina (LATAM, exceto Brasil)
+- Ásia-Pacífico (APAC)
+- Estados Unidos (EUA)
+- Europa, Oriente Médio e África (EMEA)
+
+A tabela a seguir apresenta uma visão geral dos principais artigos do Help Center relacionados à região:
+
+| **Região**     | **Artigo no Help Center** |
+| -------------- | ------------------------- |
+| Global         | **Artigo:** [Como funciona o suporte da VTEX?](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe)<br><br>Apresenta como funciona o suporte em nível global, abordando tickets, planos regionais, pesquisa de satisfação e serviços, como monitoramento e recursos como [Help Center](https://help.vtex.com/), [Developer Portal](https://developers.vtex.com/) e comunicados de atualizações na plataforma. |
+| Somente Brasil | **Artigo:** [Suporte VTEX - Brasil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)<br><br>Apresenta a disponibilidade, SLA e recursos disponíveis para clientes no Brasil. |
+| Somente Estados Unidos  | **Artigo:** [Suporte VTEX - Estados Unidos](https://help.vtex.com/en/faq/vtex-support-united-states--Bm45YFp68QRe1Z5r2oa07)<br><br>Apresenta a disponibilidade, SLA e recursos disponíveis para clientes nos Estados Unidos. Disponível somente em inglês. |
+| Somente Europa, Oriente Médio e África (EMEA) | **Artigo:** [Suporte VTEX - EMEA](https://help.vtex.com/en/faq/suporte-vtex-emea--5ePu2qkCfmE0IEKDFKg53F)<br><br>Apresenta a disponibilidade, SLA e recursos disponíveis para clientes da região EMEA. Disponível somente em inglês. |
+
diff --git a/docs/tracks/pt/indexing-history.md b/docs/tracks/pt/indexing-history.md
new file mode 100644
index 000000000..3457629f0
--- /dev/null
+++ b/docs/tracks/pt/indexing-history.md
@@ -0,0 +1,67 @@
+---
+title: 'Histórico da indexação'
+id: 4flMwTaQL8FRKl1YT58ezH
+status: PUBLISHED
+createdAt: 2020-04-14T13:33:20.167Z
+updatedAt: 2023-07-13T19:35:40.455Z
+publishedAt: 2023-07-13T19:35:40.455Z
+firstPublishedAt: 2020-04-14T23:55:09.210Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: historico-da-indexacao
+locale: pt
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugPT: vtex-intelligent-search
+---
+
+**Histórico da Indexação** é a página que monitora a situação de sincronização de todos os produtos do Catálogo enviados para o Intelligent Search. Ele permite visualizar de forma ampla o progresso da indexação da sua loja.
+
+![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+
+A seção **Status da indexação** exibe as seguintes informações:
+
+* **Tempo médio de indexação:** tempo médio para a indexação dos produtos, a partir do momento em que o sistema recebeu a notificação de uma mudança até a atualização na loja. O desempenho do tempo de indexação é medido por um ponto verde (saudável) ou vermelho (ruim). 
+![Historico Indexação 2 - PT](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
+* **Produtos na loja:** quantidade de produtos com informações atualizadas exibidos atualmente na loja.
+* **Divisão dos status:** porcentagem de produtos em cada etapa de indexação. O desempenho da divisão dos status é medido por um ponto verde (saudável) ou vermelho (ruim). As etapas exibidas são:
+    * **Atualizado:** a atualização mais recente do produto foi inserida na loja.
+    * **Atualizando:** as novas informações do produto estão sendo preparadas e inseridas na loja.
+    * **Erro**: indica que houve um erro na indexação. O produto apresenta um problema no cadastro e, por isso, não pode ser indexado. Caso seja um produto novo cadastrado, ele não estará disponível na loja.
+
+Você pode filtrar a lista de produtos indexados para uma visualização customizada. Importante destacar que o tempo médio de indexação e a divisão dos status serão recalculados a partir dos produtos filtrados. 
+
+Para filtrar a lista de produtos indexados clique em `Filtro` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
+
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+Caso filtre por `Status` você pode selecionar por qual status deseja filtrar, podendo ser `Atualizado`, `Atualizando`, `Erro`.
+
+ ![Historico indexação 4 - PT](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+Caso filtre por `Tempo de indexação` você pode selecionar se o intervelo de tempo `É maior que`, `É igual ou maior que`, `É menor que` ou `É igual ou menor que` um horário definido.
+
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
+
+Depois de definir o filtro, clique em `Aplicar` para ativá-lo. 
+
+Para adicionar um novo filtro, clique em <i class="fa-solid fa-plus"></i> `Adicionar filtro`. Para remover os filtros configurados, clique em `Limpar filtros`.
+
+Você também pode filtrar os produtos exibidos na listagem por **ID**, **Última atualização** e **Status**, clicando na coluna desejada. Para encontrar um produto específico na listagem, é possível pesquisar pelo ID na barra de busca.
+
+Caso deseje obter mais informações sobre a indexação de um produto específico, você pode clicar na linha do produto na lista para acessar a janela com mais detalhes, ilustrada abaixo.
+
+![Historico indexação 6 - PT](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+Além dos dados exibidos na lista de produtos, também é possível visualizar:
+
+* **Tempo de Indexação:** registro de quanto tempo durou a última atualização do produto, no formato `hh:mm:ss`.
+* **Linha do tempo da indexação:** registro de cada mudança de status com data e horário. Você pode vizualizar mais detalhes de cada etapa clicando no ícone <i class="fa-solid fa-chevron-down"></i>.
+
+![Historico indexação 7 - PT](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+É possível reindexar um produto manualmente sem a necessidade de realizar alguma atualização no seu cadastro. Para reidexar um produto, clique em <i class="fa-solid fa-arrows-rotate"></i> `Reindexar`. Apenas produtos no status **Atualizado** podem ser reindexados.
+
+Você pode acessar o **Histórico de indexação** do produto, uma lista com data e horário de cada atualização realizada. Dessa forma, é possível ter registro de toda alteração que foi realizada no produto. Para acessá-lo, clique em <i class="fa-solid fa-arrow-rotate-left"></i> `Histórico`. 
+
+![Histórico da Indexação 8 - PT](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
+
diff --git a/docs/tracks/pt/initializing-your-store-theme.md b/docs/tracks/pt/initializing-your-store-theme.md
index 598ef7349..3cbdde0aa 100644
--- a/docs/tracks/pt/initializing-your-store-theme.md
+++ b/docs/tracks/pt/initializing-your-store-theme.md
@@ -27,7 +27,7 @@ Selecione `store-theme` e confirme que você gostaria de fazer o download do pro
 
 Você receberá informações importantes sobre o aplicativo, como o vendor, o nome, o título e a descrição do aplicativo. Use o __account name__ da loja que você está desenvolvendo como o __vendor__. Isso é importante para que posteriormente você consiga publicar corretamente essa app nesta conta. Para usar os valores padrão, basta pressionar Enter.
 
-![store-theme](https://images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
+![store-theme](//images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
 
 ## Entendendo a estrutura da app
 
@@ -87,7 +87,7 @@ Durante um "link", todas as alterações feitas no seu código são automaticame
 
 Execute o `vtex link` e veja seu aplicativo de exemplo ser compilado e publicado na conta e no workspace que você acabou de criar.
 
-![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
+![vtex-link](//images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
 <div class="alerta alerta-info">
 Lembre-se: execute <code>vtex whoami</code> para ter certeza de que você está na conta certa e em um workspace de teste. Caso contrário, o <code>VTEX Toolbelt</code> irá reclamar do link direto com o master.
@@ -105,4 +105,4 @@ O `{{account}}.myvtex.com` é o seu domínio privado destinado a testar novos wo
 
 Parabéns por linkar sua primeira app no VTEX IO!
 
-![dreamstore](https://images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
+![dreamstore](//images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
diff --git a/docs/tracks/pt/inserting-and-configuring-placeholders.md b/docs/tracks/pt/inserting-and-configuring-placeholders.md
index 4a15e52c6..f00a5f3c6 100644
--- a/docs/tracks/pt/inserting-and-configuring-placeholders.md
+++ b/docs/tracks/pt/inserting-and-configuring-placeholders.md
@@ -34,7 +34,7 @@ O que ele faz é criar um elemento configurável no local do código onde for in
 
 É importante inserir um valor de `id`. Este será o identificador desse placeholder no sistema.
 
-![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando o placeholder
 
@@ -42,7 +42,7 @@ Agora que o controle de placeholder foi inserido no template, vamos configurá-l
 
 Isso é feito nas configurações do layout que usa esse template.
 
-1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para inserir um objeto, clique em **add object**. 
 3. Em seguida, escolha o tipo de objeto e clique em **Adicionar**.
 4. Por fim, clique no botão **Save Settings**, no alto da página.
@@ -51,7 +51,7 @@ Agora você já pode editar o objeto inserido no placeholder.
 
 Para isso, clique no lápis dentro do objeto e, em seguida, clique em **add content**.
 
-![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Agora você pode definir o nome desse objeto, subir imagens para ele e configurar as condições em que ele vai ser renderizado, tais como o período. 
 
diff --git a/docs/tracks/pt/installing-customer-credit.md b/docs/tracks/pt/installing-customer-credit.md
index ba3d1e688..88491da2a 100644
--- a/docs/tracks/pt/installing-customer-credit.md
+++ b/docs/tracks/pt/installing-customer-credit.md
@@ -1,10 +1,10 @@
 ---
-title: 'Instalar Customer Credit'
+title: 'Instalando o Customer Credit'
 id: 36grlQ69NK6OCuioeekyCs
 status: PUBLISHED
 createdAt: 2018-11-06T19:45:12.804Z
-updatedAt: 2020-08-17T22:17:50.649Z
-publishedAt: 2020-08-17T22:17:50.649Z
+updatedAt: 2024-02-08T11:31:30.622Z
+publishedAt: 2024-02-08T11:31:30.622Z
 firstPublishedAt: 2018-11-06T20:24:15.191Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,20 +14,14 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugPT: customer-credit-como-comecar
 ---
 
-Nessa track, explicaremos o passo a passo para instalar e configurar o Customer Credit. 
+Nesta track você encontra o passo a passo para instalar e configurar a app Customer Credit. Para mais informações sobre esta app, acesse [Customer Credit - Visão geral](https://help.vtex.com/pt/tutorial/customer-credit-visao-geral--1uIqTjWxIIIEW0COMg4uE0).
 
-Agora, antes de tudo, caso os conceitos dessa app sejam novos para você, recomendamos a leitura prévia do artigo sobre [noções gerais do Customer Credit](https://help.vtex.com/pt/tutorial/customer-credit-visao-geral--1uIqTjWxIIIEW0COMg4uE0).
+Para instalar o Customer Credit em sua loja, siga os passos abaixo:
 
-Ao final da leitura, você será capaz de efetuar compras nas lojas VTEX usando o Customer Credit como forma de pagamento. 
+1. No Admin VTEX, acesse __Aplicativos > Hub de Extensões > App Store__, ou digite App Store na barra de busca no topo da página.
+2. Digite o nome __Customer Credit__ na barra de busca da página da App Store e clique sobre o ícone da app.
+3. Clique no botão `Baixar App`.
+4. Em seguida, clique em `Instalar App` e `INSTALAR`.
+5. Atualize a página, pressionando a tecla __F5__ ou o botão de atualizar do seu navegador.
 
-Desse modo, podemos seguir para o primeiro passo que é a instalação da app. Para isso, você deve:
-
-1. Acesse a página da [App Store](https://apps.vtex.com/ "App Store") da VTEX;
-2. Localize o ícone do __Customer Credit__;
-3. Clique no botão cinza __“Get”__; 
-4. Preencha o campo __Account info__ com o __"Account Name"__ da sua loja;
-5. Clique no botão rosa __“Confirm order and begin installation”__.
-
-Em seguida, você será direcionado para o Admin da sua loja. Faça o respectivo login e finalize a instalação clicando no botão azul “Instalar”, localizado no canto superior direito da tela. 
-
-Com a app instalada, a nova seção Customer Credit, dentro do módulo Transações,  aparecerá no Admin.
+Após o carregamento da página, a nova seção do Customer Credit poderá ser acessada no Admin VTEX em __Aplicativos > Customer Credit__.
diff --git a/docs/tracks/pt/instore-basic-settings.md b/docs/tracks/pt/instore-basic-settings.md
index 92b0e1284..add0f54a3 100644
--- a/docs/tracks/pt/instore-basic-settings.md
+++ b/docs/tracks/pt/instore-basic-settings.md
@@ -3,8 +3,8 @@ title: 'VTEX Sales App - Configurações Básicas'
 id: 4L5SoLxE8O3YkxF7FKymrO
 status: PUBLISHED
 createdAt: 2020-06-28T13:51:53.895Z
-updatedAt: 2023-05-31T15:55:29.064Z
-publishedAt: 2023-05-31T15:55:29.064Z
+updatedAt: 2023-07-26T18:42:22.814Z
+publishedAt: 2023-07-26T18:42:22.814Z
 firstPublishedAt: 2020-06-28T14:01:36.462Z
 contentType: trackArticle
 productTeam: Shopping
@@ -17,7 +17,7 @@ trackSlugPT: instore-primeiros-passos-e-configuracoes
 O VTEX Sales App é um dos principais produtos da VTEX para operações de [Comércio Unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv). Ele é um aplicativo que permite à sua loja oferecer uma experiência omnichannel real, integrando seus canais online e físicos e colocando seus clientes no centro do negócio.
 
 <div class="alert alert-info">
-<p>Verifique se a sua loja cumpre todos os <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">pré-requisitos para usar o inStore</a> antes de começar a utilizá-lo.</p>
+<p>Verifique se a sua loja cumpre todos os <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">pré-requisitos para usar o VTEX Sales App</a> antes de começar a utilizá-lo.</p>
 </div>
 
 Para utilizar o VTEX Sales App, você precisa seguir os passos descritos a seguir na sua conta principal.
diff --git a/docs/tracks/pt/instore-customizations.md b/docs/tracks/pt/instore-customizations.md
index b66809881..52447f98d 100644
--- a/docs/tracks/pt/instore-customizations.md
+++ b/docs/tracks/pt/instore-customizations.md
@@ -36,11 +36,11 @@ Alternativamente, você pode navegar até o arquivo de configuração a partir d
 
 No menu principal, clique em __Checkout__ e, em seguida, clique no símbolo de engrenagem da loja, como indica a imagem abaixo.
 
-![20. inStore Customizations (intro) - 1](https://images.ctfassets.net/alneenqid6w5/4LKGRGjbprogSqW8fZfFDS/2a0919796851d030aa6dd86d93942620/20._inStore_Customizations__intro__-_1.png)
+![20. inStore Customizations (intro) - 1](//images.ctfassets.net/alneenqid6w5/4LKGRGjbprogSqW8fZfFDS/2a0919796851d030aa6dd86d93942620/20._inStore_Customizations__intro__-_1.png)
 
 Clique, então, na aba __Código__ e depois no arquivo checkout-instore-custom.js, que se encontra na lista de arquivos à direita.
 
-![20. inStore Customizations (intro) - 2](https://images.ctfassets.net/alneenqid6w5/6YhI3qfwXzJEn4jnkWHPKC/e64eb7aa7ae72a71deb0308bffa65592/20._inStore_Customizations__intro__-_2.png)
+![20. inStore Customizations (intro) - 2](//images.ctfassets.net/alneenqid6w5/6YhI3qfwXzJEn4jnkWHPKC/e64eb7aa7ae72a71deb0308bffa65592/20._inStore_Customizations__intro__-_2.png)
 
 ## Alterando o arquivo de customização do inStore
 
@@ -48,7 +48,7 @@ O `checkout-instore-custom.js` é um arquivo JavaScript que aceita uma série de
 
 Para fazer qualquer alteração, basta incluir ou modificar as linhas de código diretamente na caixa de edição do arquivo, no Admin da VTEX, e finalmente clicar no botão de __Salvar__, como indica a imagem abaixo.
 
-![20. inStore Customizations (intro) - 3](https://images.ctfassets.net/alneenqid6w5/4MRxgu5pLvZYTa8hGObbH1/96489ddb7665b702da05e72fd6d7e1bf/20._inStore_Customizations__intro__-_3.png)
+![20. inStore Customizations (intro) - 3](//images.ctfassets.net/alneenqid6w5/4MRxgu5pLvZYTa8hGObbH1/96489ddb7665b702da05e72fd6d7e1bf/20._inStore_Customizations__intro__-_3.png)
 
 <div class="alert alert-warning">
 Siga sempre as instruções de customização desta documentação e faça apenas as alterações conforme indicadas aqui.
diff --git a/docs/tracks/pt/instore-login.md b/docs/tracks/pt/instore-login.md
index ae7d1611a..445d694e4 100644
--- a/docs/tracks/pt/instore-login.md
+++ b/docs/tracks/pt/instore-login.md
@@ -18,7 +18,7 @@ O primeiro contato do vendedor da loja física com o VTEX Sales App acontece no
 
 Aqui devem ser usados o email e a senha criados para o vendedor na etapa de [Configurações Básicas](https://help.vtex.com/pt/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO#adding-a-sales-associates-email-and-name). Lembre-se que não é permitido usar emails que já tenham acesso ao Admin de lojas VTEX.
 
-![31. inStore - Product Overview - 1](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/6043e4d8fe06f651f2740286a89e323c/instore-login-PT.png)
+![31. inStore - Product Overview - 1](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/6043e4d8fe06f651f2740286a89e323c/instore-login-PT.png)
 
 Ao fazer o login, o vendedor acessa o VTEX Sales App específico de uma conta VTEX. Embora não seja um cenário comum, um mesmo vendedor pode estar atrelado a mais de uma conta. Se precisar trocar de conta, basta fazer logout e, na tela de login, clicar em `Alterar Loja`.
 
diff --git a/docs/tracks/pt/instore.md b/docs/tracks/pt/instore.md
index 8fe2fd311..4cc6abfdc 100644
--- a/docs/tracks/pt/instore.md
+++ b/docs/tracks/pt/instore.md
@@ -24,7 +24,7 @@ O primeiro contato do vendedor da loja física com o inStore acontece no momento
 
 Aqui devem ser usados o e-mail e a senha criados para o vendedor na etapa de [Basic Setup](https://help.vtex.com/pt/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO). Lembre-se que não é permitido usar e-mails que já tenham acesso ao painel administrativo de lojas VTEX.
 
-![31. inStore - Product Overview - 1](https://images.ctfassets.net/alneenqid6w5/3PLZFDcKUMOzX4oDtPg1D9/de1b8f3d8b6d4fd6503bc9775892d0ee/31._inStore_-_Product_Overview_-_1.jpg)
+![31. inStore - Product Overview - 1](//images.ctfassets.net/alneenqid6w5/3PLZFDcKUMOzX4oDtPg1D9/de1b8f3d8b6d4fd6503bc9775892d0ee/31._inStore_-_Product_Overview_-_1.jpg)
 
 Ao fazer o login, o vendedor acessa o inStore específico de uma conta VTEX. Embora não seja um cenário comum, um mesmo vendedor pode estar atrelado a mais de uma conta. Se precisar trocar de conta, basta fazer logout e, na tela de login, clicar em __Alterar Loja__.
 
@@ -46,7 +46,7 @@ Você pode [configurar quais métodos de identificação deseja habilitar](https
 
 No exemplo da imagem abaixo, estão habilitados E-mail e CPF.
 
-![31. inStore - Product Overview - 2](https://images.ctfassets.net/alneenqid6w5/3PXA3jRSgYOX4YABRCNe22/d032f9ee41ace4b964a0900cbc58a3af/31._inStore_-_Product_Overview_-_2.jpg)
+![31. inStore - Product Overview - 2](//images.ctfassets.net/alneenqid6w5/3PXA3jRSgYOX4YABRCNe22/d032f9ee41ace4b964a0900cbc58a3af/31._inStore_-_Product_Overview_-_2.jpg)
 
 Basta inserir um desses dados no campo e clicar no botão __Confirmar__.
 
@@ -60,11 +60,11 @@ Embora seja possível atender clientes sem identificá-los, recomendamos sempre
 
 A barra superior do aplicativo do inStore oferece algumas opções frequentemente usadas pelo vendedor. Uma delas é a da busca por SKUs, disponível no canto superior direito.
 
-![31. inStore - Product Overview - 3](https://images.ctfassets.net/alneenqid6w5/6LJqD76EflPnW1ntKJ05Tt/098471e730845c8a31801e3750a28c97/31._inStore_-_Product_Overview_-_3.png)
+![31. inStore - Product Overview - 3](//images.ctfassets.net/alneenqid6w5/6LJqD76EflPnW1ntKJ05Tt/098471e730845c8a31801e3750a28c97/31._inStore_-_Product_Overview_-_3.png)
 
 A busca do inStore é omnichannel. Ou seja, ao fazer uma busca no aplicativo, o vendedor está buscando tanto no estoque local (da loja física em si) quanto no catálogo de outras lojas físicas e do e-commerce.
 
-![31. inStore - Product Overview - 4](https://images.ctfassets.net/alneenqid6w5/1m7tJFo3VHdqNZbbw9SDMG/b5a0dc2efb81521f8317ec6f0edd86db/31._inStore_-_Product_Overview_-_4.png)
+![31. inStore - Product Overview - 4](//images.ctfassets.net/alneenqid6w5/1m7tJFo3VHdqNZbbw9SDMG/b5a0dc2efb81521f8317ec6f0edd86db/31._inStore_-_Product_Overview_-_4.png)
 
 As opções de disponibilidade de entrega e retirada serão mostradas depois, na etapa de entrega.
 
@@ -72,11 +72,11 @@ As opções de disponibilidade de entrega e retirada serão mostradas depois, na
 
 Após fazer a identificação do cliente, o vendedor é levado já diretamente para o carrinho. Lá, se estiver usando a versão para desktop do inStore, conectada a um leitor de código de barras, basta bipar os produtos para que eles apareçam no carrinho.
 
-![31. inStore - Product Overview - 5](https://images.ctfassets.net/alneenqid6w5/zYrBMK3ZD8nLWSlWJ0k1C/ffead039b599a608e2767e642290a396/31._inStore_-_Product_Overview_-_5.png)
+![31. inStore - Product Overview - 5](//images.ctfassets.net/alneenqid6w5/zYrBMK3ZD8nLWSlWJ0k1C/ffead039b599a608e2767e642290a396/31._inStore_-_Product_Overview_-_5.png)
 
 Se o vendedor estiver usando um tablet ou smartphone, ele verá, na barra superior do aplicativo, um botão de leitura de código de barras.
 
-![31. inStore - Product Overview - 6](https://images.ctfassets.net/alneenqid6w5/6AIhwNFp2qUA74hhScWN76/5a46203e12b175a4f8beebe26b4d7bc3/31._inStore_-_Product_Overview_-_6.png)
+![31. inStore - Product Overview - 6](//images.ctfassets.net/alneenqid6w5/6AIhwNFp2qUA74hhScWN76/5a46203e12b175a4f8beebe26b4d7bc3/31._inStore_-_Product_Overview_-_6.png)
 
 Ao clicar nele, o vendedor pode usar a câmera para bipar um produto e, com isso, ser levado automaticamente à tela de detalhes deste produto.
 
@@ -119,11 +119,11 @@ Todas essas informações, é bom lembrar, se referem não apenas à experiênci
 
 Ao clicar nos detalhes de um produto que aparece nos resultados da busca do inStore, ou ao bipar um produto, o vendedor é direcionado à tela de detalhes do produto.
 
-![31. inStore - Product Overview - 7](https://images.ctfassets.net/alneenqid6w5/6xjT1krpqTtSVhDEh4i3vk/ad365df3960022885ed0e279b08d2848/31._inStore_-_Product_Overview_-_7.png)
+![31. inStore - Product Overview - 7](//images.ctfassets.net/alneenqid6w5/6xjT1krpqTtSVhDEh4i3vk/ad365df3960022885ed0e279b08d2848/31._inStore_-_Product_Overview_-_7.png)
 
 Essa tela mostra o nome do produto, sua galeria de fotos, variações, descrição e disponibilidade. O vendedor pode, nessa tela, adicionar o produto ao carrinho.
 
-![31. inStore - Product Overview - 8](https://images.ctfassets.net/alneenqid6w5/1CEnHyRjNNX1GvMd8hKjLg/2f765e5a9959a5c0114651e4283baf71/31._inStore_-_Product_Overview_-_8.png)
+![31. inStore - Product Overview - 8](//images.ctfassets.net/alneenqid6w5/1CEnHyRjNNX1GvMd8hKjLg/2f765e5a9959a5c0114651e4283baf71/31._inStore_-_Product_Overview_-_8.png)
 
 Note que, se você configurou sua loja para [forçar disponibilidade de estoque](https://help.vtex.com/pt/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/2SgRUekV8FO4lg2aO6YTmh), mesmo que o produto esteja indisponível em todos os canais, o vendedor poderá adicioná-lo ao carrinho.
 
@@ -139,7 +139,7 @@ O inStore permite [habilitar uma funcionalidade de transferência de carrinho](h
 
 Uma vez no carrinho de um pedido, o vendedor tem acesso ao botão __Transferir__. Ao clicar nesse botão, o aplicativo mostra um QR Code e um código numérico de quatro dígitos.
 
-![31. inStore - Product Overview - 9](https://images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._inStore_-_Product_Overview_-_9.png)
+![31. inStore - Product Overview - 9](//images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._inStore_-_Product_Overview_-_9.png)
 
 Um outro vendedor logado na mesma loja pode, então, capturar esse carrinho e continuar a venda a partir do seu dispositivo.
 
@@ -158,21 +158,21 @@ A tela seguinte mostra as opções de entrega. Como o inStore lida com o catálo
 
 O exemplo abaixo mostra duas opções: receber todos os itens em casa via entrega econômica ou retirar em outra loja física no prazo de 5 dias úteis.
 
-![31. inStore - Product Overview - 10](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
+![31. inStore - Product Overview - 10](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
 
 ### Pontos de Retirada
 
 Para opções de retirada em loja (pickup point), o sistema seleciona as lojas que têm os SKUs em estoque e mostra a loja mais próxima ao CEP do cliente, como sugestão. Se o vendedor quiser trocar a loja onde o cliente fará a coleta, basta clicar no botão __Alterar ponto de retirada__.
 
-![31. inStore - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
+![31. inStore - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
 
 Ao clicar em Alterar ponto de retirada, o vendedor primeiro tem acesso ao ponto de retirada sugerido pelo sistema. Para ver todos os pontos de retirada disponíveis, basta clicar em __Ver todos os pontos de retirada__.
 
-![31. inStore - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
+![31. inStore - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
 
 O aplicativo mostrará, então, a lista de pontos de retirada, ordenada por menor distância do CEP do cliente. Também é possível escolher o ponto de retirada pelo mapa.
 
-![31. inStore - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
+![31. inStore - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
 
 ## 12. Pagamento
 
@@ -180,17 +180,17 @@ Na etapa de pagamento, aparecerão as [opções de pagamento que foram configura
 
 Uma funcionalidade importante permitida pelo inStore são os múltiplos pagamentos. Por exemplo: escolhendo Dinheiro e depois clicando em __Adicionar outro pagamento__, o vendedor pode fazer parte da cobrança em dinheiro e outra parte em cartão de crédito ou débito.
 
-![31. inStore - Product Overview - 14](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
+![31. inStore - Product Overview - 14](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
 
 A barra superior da tela de pagamento permite adicionar cupom e vale-presente. Permite, ainda, alterar o número do CPF que constará na Nota Fiscal do pedido.
 
-![31. inStore - Product Overview - 15](https://images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
+![31. inStore - Product Overview - 15](//images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
 
 ## 13. Pedido finalizado
 
 O vendedor pode ver essa mesma tela clicando em __Pedidos finalizados__, no menu principal do inStore, e buscando o pedido por número do pedido ou cliente.
 
-![31. inStore - Product Overview - 16](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
+![31. inStore - Product Overview - 16](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
 
 ## 14. Impressão de NFC-e
 
diff --git a/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
index 3c76e97cc..8dbd54e38 100644
--- a/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
@@ -16,7 +16,7 @@ trackSlugPT: integrar-o-instore-a-um-novo-adquirente-de-pagamento
 
 Este artigo tem como objetivo explicar como a app do inStore configura o AppLinking para as ações de `payment` e `payment-reversal` com as apps dos adquirentes.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuração
 
diff --git a/docs/tracks/pt/integration-configurations.md b/docs/tracks/pt/integration-configurations.md
index a7a99f5f6..2b085ba58 100644
--- a/docs/tracks/pt/integration-configurations.md
+++ b/docs/tracks/pt/integration-configurations.md
@@ -21,7 +21,7 @@ Os passos a seguir deverão ser feitos dentro do app.
 1. No seletor, escolha a política comercial que será usada na Wish ([pré definida no passo 2](https://help.vtex.com/pt/tracks/configurar-integracao-da-wish--50hbG4bzhSIhjz1lzqI1g43OHGQIQmt1dKw9RwKruE7H#definindo-politica-comercial))
 2. Após selecionar a política comercial, clique em "Continuar".
 
-![PT - Configurar Wish](https://images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
+![PT - Configurar Wish](//images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
 
 ## Configurações de envio
 
diff --git a/docs/tracks/pt/integration-settings.md b/docs/tracks/pt/integration-settings.md
index 76bbbdcf9..6e00980d4 100644
--- a/docs/tracks/pt/integration-settings.md
+++ b/docs/tracks/pt/integration-settings.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurações de Integração'
+title: 'Integrações'
 id: 6wKQgKmu2FT6084BJT7z5V
 status: PUBLISHED
 createdAt: 2020-04-14T13:28:52.687Z
-updatedAt: 2020-04-20T20:15:39.952Z
-publishedAt: 2020-04-20T20:15:39.952Z
+updatedAt: 2024-01-24T19:12:30.626Z
+publishedAt: 2024-01-24T19:12:30.626Z
 firstPublishedAt: 2020-04-14T23:53:14.582Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,9 +14,16 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
-Configurações de integração é a funcionalidade responsável pela indexação inicial do Catálogo com o VTEX Intelligent Search. Após instalar o aplicativo, esse será o primeiro passo para integrá-lo com o Catálogo.
+A página **Configurações da loja** > **Intelligent Search** > **Integrações** no Admin VTEX é responsável pela indexação inicial do Catálogo com o VTEX Intelligent Search. Após instalar o aplicativo, esse será o primeiro passo para integrá-lo com o Catálogo.
 
-A ferramenta consiste em um texto informando sobre o processo de indexação e um botão Iniciar. Ao apertar o botão, a indexação é iniciada e um link para a tela de __Status da indexação__ é exibido.
+Siga as instruções para iniciar o processo de integração:
 
+1. No Admin VTEX, acesse **Configurações da loja**, ou digite **Configurações da loja** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Integrações**.
+4. Clique em `Iniciar`.
 
-![config-int-PT](https://images.ctfassets.net/alneenqid6w5/3V6THUbFmXULk1LhelGcTK/f6c35665bb7e8fc77de782a86cdb5426/config-int-PT.png)
+O processo de indexação será iniciado. Uma vez concluído, a tela ilustrada a seguir será exibida.
+
+![integracoes-is](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/43b9e3474b8f3046405278e34266e0fc/integracoes-is.PNG)
+
+Não é necessário repetir esse processo. Depois de iniciar a integração, é possível acompanhar o status da indexação na página [Histórico da indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tracks/pt/intelligent-synonyms.md b/docs/tracks/pt/intelligent-synonyms.md
new file mode 100644
index 000000000..85d4faf55
--- /dev/null
+++ b/docs/tracks/pt/intelligent-synonyms.md
@@ -0,0 +1,68 @@
+---
+title: 'Sinônimos Inteligentes'
+id: 36w9XnpEkoVWl46tAwlyIV
+status: DRAFT
+createdAt: 2024-04-02T12:59:23.678Z
+updatedAt: 2024-06-17T13:46:32.394Z
+publishedAt: 
+firstPublishedAt: 2024-04-02T13:04:21.646Z
+contentType: trackArticle
+productTeam: Marketing & Merchandising
+slug: sinonimos-inteligentes
+locale: pt
+trackId: 19wrbB7nEQcmwzDPl1l4Cb
+trackSlugPT: vtex-intelligent-search
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidade está  disponível para contas que tenham um número mínimo de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. É possível que taxas extras se apliquem futuramente.</p>
+</div>
+
+A funcionalidade de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) permite cadastrar palavras, ou expressões de mesmo sentido, para termos de busca utilizados pelos clientes ao realizar pesquisas na sua loja, aumentando a chance deles obterem resultados relevantes nas buscas.
+
+Com a funcionalidade de Sinônimos Inteligentes, a página de **Sinônimos** no Admin VTEX apresenta recomendações inteligentes de termos para cadastro, além da configuração manual de sinônimos. A plataforma sugere sinônimos a partir de Inteligência Artificial, com base no comportamento de busca de clientes na sua loja.
+
+Para isso, o VTEX Intelligent Search contabiliza quantas vezes nos últimos 30 dias os clientes pesquisaram por um termo que resultou em poucos ou nenhum resultado de busca e substituíram o termo original por outro. 
+
+Por exemplo, imagine que cinco clientes escreveram `sabonete rosto` e, em seguida, alteraram a pesquisa para `sabão rosto`. O sistema registra esse comportamento e os termos mais reescritos vão aparecer como sugestão de sinônimos.
+
+As sugestões são exibidas em duas categorias na listagem de sinônimos, conforme a ilustração abaixo:
+
+* **Novas sugestões:** sugestões geradas pela plataforma que ainda não foram visualizadas.
+* **Sugestões salvas:** sugestões salvas para depois, como descrito no passo 5 da seção [Revisar sugestões](#revisar-sugestoes).
+
+![synonym-suggestion-list-pt](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
+
+Você pode revisar as sugestões geradas e optar por salvar para depois, recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
+
+## Revisar sugestões
+
+Siga as instruções para visualizar as sugestões de sinônimos e definir se elas serão recusadas, editadas ou aprovadas:
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Sinônimos**.
+3. Ao acessar a página de **Sinônimos**, se existirem sugestões ainda não revisadas, um modal vai surgir, indicando a quantidade de sugestões geradas. Nesse caso, clique em `Revisar` para analisá-las.
+
+    Se optar por clicar em `Agora não`, essas sugestões são mantidas na caixa **Novas sugestões**, indicando a quantidade de sugestões geradas. Para revisá-las, clique em `Revisar`.
+
+4. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
+
+   ![synonym-suggestion-pt](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
+
+5. Para revisar cada sugestão, escolha uma das ações a seguir:
+
+    * <i class="fas fa-bookmark"></i> **Salvar para depois:** remove a sugestão da contagem de **Novas sugestões** e passa a armazená-la na caixa **Sugestões salvas**. Para analisar as sugestões salvas posteriormente, clique em `Revisar`.
+    * <i class="fas fa-times-circle"></i> **Recusar**: descarta a sugestão proposta.
+    * <i class="fas fa-pencil-alt"></i> **Editar**: altera campos da configuração dos sinônimos sugeridos. Depois de editar, é preciso clicar em <i class="fas fa-check-circle"></i> para salvar. Para mais informações sobre os campos disponíveis, leia [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
+    * <i class="fas fa-check-circle"></i> **Aprovar**: aplica e salva a sugestão proposta.
+6. Após revisar todas as sugestões, feche o modal para acessar a listagem de sinônimos configurados na sua loja.
+
+<div class="alert alert-error">
+  <p>Uma vez que uma ação é realizada, não é possível desfazê-la, pois a próxima sugestão disponível é exibida imediatamente.</p>
+</div>
+
+## Saiba mais
+
+* [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV)
+* [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL)
+* [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
diff --git a/docs/tracks/pt/intro-to-vtex-io-builders.md b/docs/tracks/pt/intro-to-vtex-io-builders.md
index 9ec3e1dad..2ce458286 100644
--- a/docs/tracks/pt/intro-to-vtex-io-builders.md
+++ b/docs/tracks/pt/intro-to-vtex-io-builders.md
@@ -19,6 +19,6 @@ Apps do VTEX IO exportam código ou configuração para fornecer features ou alt
 Esses pedaços de código e configuração geralmente requerem alguma preparação ou validação para servirem à sua finalidade. Por exemplo, os componentes React precisam ter suas dependências extraídas e compiladas em pacotes JavaScript.
 
 O VTEX IO cuida automaticamente de todas essas etapas, implementando-as como Builders. Uma vez que sua app declara que ela usa um builder, a pasta correspondente e seu conteúdo são processados ​​por ele quando é realizado o link.
-![builders](https://images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
+![builders](//images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
 
 O projeto store theme usa dois builders principais (`store` e `styles`), mas à medida que criar apps com funcionalidades mais avançadas, você começará a usar outros builders de nível mais baixo, como `react`, `messages`, `graphql` e `node`.
diff --git a/docs/tracks/pt/introduction-to-vtex-io.md b/docs/tracks/pt/introduction-to-vtex-io.md
index be841fd18..291e44348 100644
--- a/docs/tracks/pt/introduction-to-vtex-io.md
+++ b/docs/tracks/pt/introduction-to-vtex-io.md
@@ -22,7 +22,7 @@ Nesta track, vamos ensinar passo a passo como desenvolver uma app utilizando o V
 
 Veja na imagem abaixo a estrutura de hierarquia do VTEX IO:
 
-![VTEX IO Hierarchy](https://images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
+![VTEX IO Hierarchy](//images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
 
 - __Account__: Para desenvolver uma app, é necessário ter uma conta na VTEX.
 - __Workspaces__: São os ambientes onde as apps serão desenvolvidas. Esses ambientes estão vinculados ao account. É possível ter diversos workspaces para um único account.
diff --git a/docs/tracks/pt/introduction-to-vtex.md b/docs/tracks/pt/introduction-to-vtex.md
new file mode 100644
index 000000000..bae9aca47
--- /dev/null
+++ b/docs/tracks/pt/introduction-to-vtex.md
@@ -0,0 +1,45 @@
+---
+title: 'Introdução à VTEX'
+id: 3QfoDZWg9YWl8lwS9MVrnU
+status: PUBLISHED
+createdAt: 2024-01-22T14:29:24.584Z
+updatedAt: 2024-02-22T14:58:02.855Z
+publishedAt: 2024-02-22T14:58:02.855Z
+firstPublishedAt: 2024-02-22T13:59:50.803Z
+contentType: trackArticle
+productTeam: Others
+slug: introducao-a-vtex
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+A [VTEX](https://vtex.com/br-pt/) é uma solução integrada de comércio global baseada em microsserviços, oferece marketplace de ponta a ponta, recursos nativos de gestão de pedidos (OMS) e tem um modelo composable commerce. Isso possibilita a lojas de diversos segmentos gerir operações com eficiência e escalabilidade, oferecendo aos seus clientes excelentes experiências de compra.
+
+A imagem a seguir apresenta as soluções e possibilidades da VTEX, que serão abordadas ao longo desta trilha:
+
+![vtex_composable_complete_PT](//images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/c5b053eec0632543c254624f13bf6dbf/vtex_composable_complete_PT.png)
+
+<div class="alert alert-info">
+Além dos portais de documentação Help Center e <a href="https://developers.vtex.com/">Developer Portal</a> e da <a href="https://community.vtex.com/">VTEX Community</a>, em nosso <a href="https://vtex.com/br-pt/">site</a> disponibilizamos mais informações sobre a plataforma por meio de <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">demo videos</a> (somente inglês) e <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> criados por <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros</a>. Também é possível conferir uma série de <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">vídeos de onboarding</a> (somente português).
+</div>
+
+## Visão geral desta trilha
+
+Esta trilha apresenta a jornada de uma loja VTEX desde as [configurações iniciais](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) até o [go-live](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH). Mas antes de configurar os [módulos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) da plataforma, planejar as [integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) e escolher uma tecnologia de [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para a construção da frente de loja, existe um passo anterior: definir o [tipo de conta e a arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) que melhor atende às necessidades do negócio.
+
+<div class="alert alert-warning">
+Cada operação de ecommerce possui suas particularidades e este conteúdo não busca traduzir todas as situações existentes. O objetivo é fornecer um modelo geral e apresentar de forma contextualizada os recursos e as possibilidades da plataforma VTEX.
+</div>
+
+A organização sequencial do conteúdo existe para fins didáticos e não significa que as etapas devam ser realizadas de forma sequencial, ou que a etapa anterior seja um bloqueio para a seguinte, pois algumas etapas podem ser executadas em paralelo, ao menos parcialmente. É o caso das integrações de backend, as configurações de alguns módulos e a implementação de frontend.
+
+## Visão geral do Guia de onboarding
+
+A **Trilha da loja VTEX** é a primeira das trilhas que compõem o **Guia de onboarding**. Após o go-live, existem diversas outras [soluções](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) e [configurações](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) na plataforma para diversificar as estratégias de venda da loja e expandir as operações do negócio. É sobre isso que se trata a segunda trilha, chamada [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/7bORBaAr4rIG3JgRi68jIK).
+
+A terceira e última trilha do **Guia de onboarding** é chamada [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) e visa proporcionar aos nossos clientes a melhor experiência com a plataforma e nosso suporte. A trilha aborda o [funcionamento do Suporte](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) e explica como abrir chamados para obter auxílio em questões [técnicas](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [financeiras](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) ou [comerciais](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
+
+Feita esta apresentação, podemos começar a jornada.<br>
+Desejamos as boas-vindas à VTEX.
+
diff --git a/docs/tracks/pt/inventory-and-shipping-module-overview.md b/docs/tracks/pt/inventory-and-shipping-module-overview.md
index 409b4917e..25be04966 100644
--- a/docs/tracks/pt/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/pt/inventory-and-shipping-module-overview.md
@@ -18,7 +18,7 @@ O módulo de __Estoque e entrega__ é o serviço responsável pela *logística*
 
 O sistema de logística possui diversas funcionalidades úteis. Estas *features* permitem que você monte uma estratégia de estoque e entrega da maneira mais adequada ao seu negócio. Nos próximos passos desta trilha, veremos como utilizar cada uma das funcionalidades exibidas abaixo. No admin da sua loja, você vai encontrar as seguintes seções:
 
-![inventory-shipping-admin-pt](https://images.ctfassets.net/alneenqid6w5/6S8H6GEZ58BQc9V6YfTT6Y/242d97ee4ba2809fcb9dd2c209e7fa9b/inventory-shipping-admin-pt.png)
+![inventory-shipping-admin-pt](//images.ctfassets.net/alneenqid6w5/6S8H6GEZ58BQc9V6YfTT6Y/242d97ee4ba2809fcb9dd2c209e7fa9b/inventory-shipping-admin-pt.png)
 
 __Estratégia de envio__ (Painéis) - Nesta seção, você deve cadastrar as rotas logísticas que realizam a entrega dos seus pedidos. Um rota básica é composta por um __estoque__, uma __doca__ e uma __política de envio__ (transportadora).
 
diff --git a/docs/tracks/pt/legacy-cms-portal.md b/docs/tracks/pt/legacy-cms-portal.md
index 536cda3b3..b46b0e8f1 100644
--- a/docs/tracks/pt/legacy-cms-portal.md
+++ b/docs/tracks/pt/legacy-cms-portal.md
@@ -18,7 +18,7 @@ trackSlugPT: cms
 
 A seção [Layout](https://help.vtex.com/pt/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW) permite que você crie seu storefront usando HTML e CSS. Ela é organizada em pastas e arquivos com as funções descritas abaixo.
 
-![CMS - Layout PT](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/ce15ae6de766c7856a26d9c2f7e21cbc/cms-layout-pt.png)
+![CMS - Layout PT](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/ce15ae6de766c7856a26d9c2f7e21cbc/cms-layout-pt.png)
 
 - **HTML Templates:** criar o código HTML e os arquivos JavaScript e CSS de referência que serão usados nas páginas do site.
 
@@ -38,7 +38,7 @@ A seção [Layout](https://help.vtex.com/pt/subcategory/layout--2g6LxtasS4iSeGEq
 
 A seção [Configurações](https://help.vtex.com/pt/subcategory/configuracoes-de-cms--6kovkwzMRyeOOc2iEC4suM) permite que você defina configurações relacionadas ao site da sua loja, como metadados, tags de SEO, tipos de arquivos, etc. 
 
-![CMS - Settings PT](https://images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/77031b9bdbae01c422147d00c9f9a2cb/cms-settings-pt.png)
+![CMS - Settings PT](//images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/77031b9bdbae01c422147d00c9f9a2cb/cms-settings-pt.png)
 
 A seção **Configurações*** contém as seguintes abas:
 
@@ -67,7 +67,7 @@ Toda loja precisa ter, sem exceção, as seguintes pastas no CMS para garantir o
 
 Veja abaixo estas pastas básicas no CMS:
 
-![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas pastas vêm por padrão no ambiente de todas as lojas VTEX.
 
diff --git a/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md b/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md
index 94153abc3..99d64037f 100644
--- a/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md
+++ b/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md
@@ -26,9 +26,9 @@ Você provavelmente já definiu quais [links](https://help.vtex.com/pt/tutorial/
 
 1. No menu principal do seu painel admin na VTEX Assisted Sales (SuiteShare), clique em **Configurações**.
 2. Selecione a opção **Integrações**. 
-![Levar os contatos do WhatsApp para um CRM 1](https://images.ctfassets.net/alneenqid6w5/1eVxgg7WRTzIhymKuIKHui/f03e6023c83e6bd24ac65f00e987ef5b/Screenshot_2022-08-24_at_17-59-46_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 1](//images.ctfassets.net/alneenqid6w5/1eVxgg7WRTzIhymKuIKHui/f03e6023c83e6bd24ac65f00e987ef5b/Screenshot_2022-08-24_at_17-59-46_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 3. Localize o seu CRM dentro das opções de integrações
-![Levar os contatos do WhatsApp para um CRM 2](https://images.ctfassets.net/alneenqid6w5/4owv76x3alggHV7HJsHgt8/f9ba71dcd084bdc03d6d7c4e160f2176/Screenshot_2022-08-24_at_17-59-37_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 2](//images.ctfassets.net/alneenqid6w5/4owv76x3alggHV7HJsHgt8/f9ba71dcd084bdc03d6d7c4e160f2176/Screenshot_2022-08-24_at_17-59-37_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 
 Para realizar as configurações com a ajuda dos nossos tutoriais, escolha na lista abaixo o CRM que deseja configurar.  
 
@@ -49,13 +49,13 @@ Não encontrou o seu CRM na lista?
 Não se preocupe, você pode avisar nossa equipe qual o CRM deseja integrar para avaliarmos a possibilidade de incluí-lo na nossa lista de integração automática. Por enquanto você pode exportar todos os leads para um arquivo CSV e inserir manualmente no seu CRM. 
 
 1. Para fazer isso basta acessar **Capturar**.
-![Levar os contatos do WhatsApp para um CRM 3](https://images.ctfassets.net/alneenqid6w5/1iOqIAZHaz9d52kE8HCoct/4ad9945d7f72a7638b316b4661d0d90c/Screenshot_2022-08-25_at_14-44-55_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 3](//images.ctfassets.net/alneenqid6w5/1iOqIAZHaz9d52kE8HCoct/4ad9945d7f72a7638b316b4661d0d90c/Screenshot_2022-08-25_at_14-44-55_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 2. Clique na opção _**“Leads”**_ 
-![Levar os contatos do WhatsApp para um CRM 4](https://images.ctfassets.net/alneenqid6w5/5WBulBLvIz16GiZj2JDzig/ea13b87c7ba52c9e36979a41abff368c/Screenshot_2022-08-24_at_17-59-58_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 4](//images.ctfassets.net/alneenqid6w5/5WBulBLvIz16GiZj2JDzig/ea13b87c7ba52c9e36979a41abff368c/Screenshot_2022-08-24_at_17-59-58_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 
 Nesta tela você terá as seguintes informações: 
 
-![Levar os contatos do WhatsApp para um CRM 5](https://images.ctfassets.net/alneenqid6w5/2i2zwDDmuYMaMA37SjRnd7/754db443e0b63af943c32959c0dfa0f7/Screenshot_2022-08-25_at_14-46-39_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 5](//images.ctfassets.net/alneenqid6w5/2i2zwDDmuYMaMA37SjRnd7/754db443e0b63af943c32959c0dfa0f7/Screenshot_2022-08-25_at_14-46-39_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 
 **1 Exportar** : Você exporta em CSV toda a lista de leads cadastrados na captura. 
 
diff --git a/docs/tracks/pt/live-support.md b/docs/tracks/pt/live-support.md
index 7f185e23e..b616c29a3 100644
--- a/docs/tracks/pt/live-support.md
+++ b/docs/tracks/pt/live-support.md
@@ -1,10 +1,10 @@
 ---
 title: 'Atendimento Humano'
 id: 1woBo299K5gvDG7MSa8HYL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-18T15:27:09.214Z
-updatedAt: 2023-04-27T15:25:57.212Z
-publishedAt: 2023-04-27T15:25:57.212Z
+updatedAt: 2024-01-05T17:14:29.070Z
+publishedAt: 
 firstPublishedAt: 2023-04-18T19:58:12.540Z
 contentType: trackArticle
 productTeam: Shopping
@@ -19,7 +19,7 @@ Atendimento Humano é a configuração que auxiliará sua loja no suporte ao cli
 Para a ativação do Atendimento Humano, é necessário seguir os passos de integração descritos em [Configuração da estrutura para atendimento humano](https://help.vtex.com/pt/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/SxhYiiqUJYiQX4CIWxmVE).
 
 Para configurar os horários de funcionamento do Atendimento Humano na sua loja, siga os passos abaixo.
-![Live Support pt](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
+![Live Support pt](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
 
 1. Visite seu Admin > Apps > Conversational Commerce > Configurações> Atendimento Humano.
 2. Ative o Atendimento Humano em sua loja.
@@ -29,11 +29,11 @@ Para configurar os horários de funcionamento do Atendimento Humano na sua loja,
 # Configurações Gerais
 
 1. Defina se deseja ativar o Atendimento Humano em sua loja. 
-![Live Support pt](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
+![Live Support pt](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
 Se optar por não utilizar, é necessário definir uma mensagem de indisponibilidade indicando o melhor canal de atendimento para seu cliente. 
-![Mensagem de indisponibilidade](https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/893fc8739cf19e9160a37c650614af2b/Mensagem_de_indisponibilidade.png)
+![Mensagem de indisponibilidade](//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/893fc8739cf19e9160a37c650614af2b/Mensagem_de_indisponibilidade.png)
 2. Defina o fuso horário que será utilizado em seu atendimento. 
-![Fuso horário](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/70da2f837c8ace1dcf4f03196d03eeb6/Hor__rios_de_funcionamento.png)
+![Fuso horário](//images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/70da2f837c8ace1dcf4f03196d03eeb6/Hor__rios_de_funcionamento.png)
 3. Selecione os dias e defina os horários de funcionamento do seu Atendimento Humano. É possível definir mais de um período de atendimento por dia de semana. 
 
 <div class="alert alert-info">
@@ -41,8 +41,8 @@ Em caso de feriados fixos, regionais ou outras datas em que não possua atendime
 </div>
 
 <ol start="4">
-  <li>Se houver alguma exceção de atendimento, informe os períodos de indisponibilidade.<br><img src="https://images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/b9e85eff01bcd5f86a685720b7b9a1f0/image4.png" alt="Exceções ou feriados"></li>
-  <li>Defina uma mensagem de indisponibilidade. Esta mensagem será enviada nos momentos em que clientes entrarem em contato via Whatsapp em períodos fora das janelas de atendimento configuradas.<br><img src="https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/893fc8739cf19e9160a37c650614af2b/Mensagem_de_indisponibilidade.png" alt="Mensagem de indisponibilidade"></li>
+  <li>Se houver alguma exceção de atendimento, informe os períodos de indisponibilidade.<br><img src="//images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/b9e85eff01bcd5f86a685720b7b9a1f0/image4.png" alt="Exceções ou feriados"></li>
+  <li>Defina uma mensagem de indisponibilidade. Esta mensagem será enviada nos momentos em que clientes entrarem em contato via Whatsapp em períodos fora das janelas de atendimento configuradas.<br><img src="//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/893fc8739cf19e9160a37c650614af2b/Mensagem_de_indisponibilidade.png" alt="Mensagem de indisponibilidade"></li>
   <li>Clique em <code>Salvar</code>.</li>
 </ol> 
 
diff --git a/docs/tracks/pt/livelo-integration-overview.md b/docs/tracks/pt/livelo-integration-overview.md
new file mode 100644
index 000000000..0f06f56b1
--- /dev/null
+++ b/docs/tracks/pt/livelo-integration-overview.md
@@ -0,0 +1,32 @@
+---
+title: 'Visão geral da integração com a Livelo'
+id: 5rhGcaM0SedoK7lDMBkVFD
+status: PUBLISHED
+createdAt: 2023-08-10T22:18:36.772Z
+updatedAt: 2023-08-11T02:18:04.456Z
+publishedAt: 2023-08-11T02:18:04.456Z
+firstPublishedAt: 2023-08-11T01:56:55.424Z
+contentType: trackArticle
+productTeam: Channels
+slug: visao-geral-da-integracao-com-a-livelo
+locale: pt
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugPT: integracao-livelo
+---
+
+A Livelo é a plataforma de marketplace com o maior programa de recompensas do Brasil. Atualmente, a Livelo comercializa produtos diversos, com destaque para as categorias de eletrônicos, eletrodomésticos, eletroportáteis e utilidades domésticas.
+
+![Logo Livelo](//images.ctfassets.net/alneenqid6w5/3pndHEvgehYKfuzlg2Zk7Y/ad11bd007d297906f52fc650fcbe197d/logo-livelo.jpg)  
+
+A configuração com a Livelo tem como objetivo conectar sua loja VTEX com o marketplace, permitindo que você anuncie seus produtos, aumente suas vendas e atingindo novos clientes a partir deste novo canal.   
+
+<div class="alert alert-info"> A funcionalidade <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> (MOI) não está disponível na integração com a Livelo.
+</div>  
+
+A configuração da integração está disponível somente para lojas VTEX do Brasil integrarem produtos de todas as categorias.  
+Para realizar a configuração entre VTEX e Livelo, é necessário concluir as etapas:  
+
+- [Credenciais Livelo  ](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/HgIbZEzbPr8FQid5MXURQ#credenciais-livelo)
+- [Configurações na plataforma VTEX](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/HgIbZEzbPr8FQid5MXURQ#conguracoes-na-plataforma-vtex)  
+- [Cadastro da integração Livelo](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/2h9cAUiAZONxc5xbqeRjvu)  
+
diff --git a/docs/tracks/pt/livelo-integration-registration.md b/docs/tracks/pt/livelo-integration-registration.md
new file mode 100644
index 000000000..5bff26699
--- /dev/null
+++ b/docs/tracks/pt/livelo-integration-registration.md
@@ -0,0 +1,37 @@
+---
+title: 'Cadastro da integração Livelo'
+id: 2h9cAUiAZONxc5xbqeRjvu
+status: PUBLISHED
+createdAt: 2023-08-11T00:50:23.667Z
+updatedAt: 2024-07-26T18:49:35.608Z
+publishedAt: 2024-07-26T18:49:35.608Z
+firstPublishedAt: 2023-08-11T01:56:55.329Z
+contentType: trackArticle
+productTeam: Channels
+slug: cadastro-da-integracao-livelo
+locale: pt
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugPT: integracao-livelo
+---
+
+Terminadas as etapas de configuração da sua conta na Livelo e da sua conta na VTEX, a configuração do conector é feita no Admin VTEX. Para configurar, siga as instruções abaixo:  
+
+1. No Admin VTEX vá em *Marketplace* > Conexões > **Marketplaces e** **Integrações** ou digite **Marketplaces e Integrações** na barra de busca.  
+2. Digite **Livelo** na barra de busca da página, clique no card da integração.
+3. Clique no botão **`Conectar`**, você será redirecionado para a App Store (a moeda da página precisa estar em BRL).  
+4. Clique no botão **`GET APP`**.
+5. Retorne para a página **Marketplaces e Integrações** e preencha os campos da tela descritos logo abaixo e, em seguida, clique no botão `Salvar`.  
+
+<div class="alert alert-danger">
+Nesta etapa as credenciaisda Livelo são necessárias. <br>Todos os campos da tela de configuração da Livelo são obrigatórios.</br>
+</div>  
+
+| **Campo** | **Descrição** | **Exemplo** |
+|---|---|---|
+| **Status da integração** | Botão que define se a integração estará ligada ou desligada. | <i class="fas fa-toggle-on"></i>  ou <i class="fas fa-toggle-off"></i> |
+| **ID do Afiliado** | Código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não. Vogais não são aceitas.  A configuração do conector cria automaticamente o afiliado. | LVL |
+| **Email** | Email do responsável pela loja. | email@integracao.com |
+| **Canal de vendas** | Identificador da [política comercial](https://help.vtex.com/pt/tutorial/configuring-a-marketplace-trade-policy--tutorials_404) que definirá o sortimento de catálogo e os valores dos itens que serão enviados para a Livelo. | 1 |
+| **Client Id** | Identificador fornecido pela Livelo. | lvlteste |
+| **Secret** | Chave alfanumérica  fornecida pela Livelo. | xx61x016-xx41-423x-xx42-xx781x6x14xx5 |
+
diff --git a/docs/tracks/pt/login-e-senha.md b/docs/tracks/pt/login-e-senha.md
index 4f990033c..943845d48 100644
--- a/docs/tracks/pt/login-e-senha.md
+++ b/docs/tracks/pt/login-e-senha.md
@@ -20,7 +20,7 @@ Para conseguir o login e senha para acessar o adaptador, você deve abrir um cha
 
 Em seu navegador preferido, digite `https://adapterstaging.ciashop.com.br/`. Sugerimos adicionar este link na pasta favoritos do seu navegador preferido.
 
-![login-adaptador](https://images.ctfassets.net/alneenqid6w5/4toFGLYSg26MGGWMf3kHDc/4fbb56d3ebf3f7dca51ea3aa9bd623c0/login-adaptador.png)
+![login-adaptador](//images.ctfassets.net/alneenqid6w5/4toFGLYSg26MGGWMf3kHDc/4fbb56d3ebf3f7dca51ea3aa9bd623c0/login-adaptador.png)
 
 ## Efetuando login (ambiente de homologação) com os dados enviados pela equipe de atendimento
 
diff --git a/docs/tracks/pt/magazine-luiza-marketplace.md b/docs/tracks/pt/magazine-luiza-marketplace.md
index 542cc66bf..5b6489d41 100644
--- a/docs/tracks/pt/magazine-luiza-marketplace.md
+++ b/docs/tracks/pt/magazine-luiza-marketplace.md
@@ -3,8 +3,8 @@ title: 'Magazine Luiza Marketplace'
 id: 5CEVGKgtrMuifbjNoo8jKX
 status: PUBLISHED
 createdAt: 2021-03-16T19:41:45.000Z
-updatedAt: 2021-03-19T16:23:48.653Z
-publishedAt: 2021-03-19T16:23:48.653Z
+updatedAt: 2024-07-26T18:58:37.335Z
+publishedAt: 2024-07-26T18:58:37.335Z
 firstPublishedAt: 2021-03-18T14:15:52.422Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,6 +16,6 @@ trackSlugPT: configurar-integracao-com-o-magazine-luiza
 
 O [Magazine Luiza](https://www.magazineluiza.com.br/) foi criado há mais de 60 anos, e se consolidou como uma das maiores empresas varejistas do Brasil. Atualmente são mais de 900 lojas físicas distribuídas por todo o país e desde 2019, o Magalu vem se posicionando como uma plataforma digital de varejo.
 
-![magazine-luiza](https://drive.google.com/uc?export=download&id=14dU0rn3SBfCZZPPMGYdru1YPZalxwz6J)
+![Logo Magazine Luiza](//images.ctfassets.net/alneenqid6w5/2gWxg3UR4Hxf0XeLIx3QA0/d8a0ed0314ab90c39acff73fef5f8ea9/magazine-luiza-redimensionado-2.jpg)
 
 Por meio da integração da Plataforma VTEX com o Magalu, você pode aumentar a visibilidade dos seus produtos e alavancar suas vendas. O primeiro passo para isso é fazer seu [cadastro no portal Magazine Luiza Marketplace](https://marketplace-vendamais.magazineluiza.com.br/).
diff --git a/docs/tracks/pt/managing-accounts.md b/docs/tracks/pt/managing-accounts.md
index 3ed0d12e2..731b94384 100644
--- a/docs/tracks/pt/managing-accounts.md
+++ b/docs/tracks/pt/managing-accounts.md
@@ -1,10 +1,10 @@
 ---
-title: 'Gerenciar contas no Customer Credit'
+title: 'Gerenciando contas no Customer Credit'
 id: 4eknoeqaj6EGC20amsm6Gc
 status: PUBLISHED
 createdAt: 2018-11-06T21:15:25.330Z
-updatedAt: 2023-05-12T12:21:21.583Z
-publishedAt: 2023-05-12T12:21:21.583Z
+updatedAt: 2024-02-27T19:44:55.522Z
+publishedAt: 2024-02-27T19:44:55.522Z
 firstPublishedAt: 2018-11-07T17:10:45.883Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,100 +14,66 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugPT: customer-credit-como-comecar
 ---
 
-A tela de Detalhes da Conta traz tudo o que você precisa saber sobre uma conta e suas configurações.
+Por meio da tela de contas no Admin VTEX (__Aplicativos > Customer Credit > Contas__), você pode ter acesso a informações de todas contas cadastradas no app do Customer Credit em sua loja. 
 
-## Limite de crédito
-O limite de crédito e indica o valor máximo de títulos em aberto que um cliente pode ter em um dado momento. Estabelecê-lo é obrigatório e o super Admin da conta pode alterar esse valor quantas vezes quiser.
+Ao clicar sobre o nome de uma conta específica, a tela __Detalhes da conta__ exibirá os seguintes de dados:
 
-Além disso, lembre-se que as alterações no limite de crédito são atualizadas em poucos minutos no sistema.
+- [Informações do Titular](#titular)
+- [Status de crédito](#status)
+- [Títulos emitidos](#titulos)
+- [Extrato de utilização](#extrato)
+- [Dependentes adicionais](#dependentes-adicionais)
+- [Encerramento de conta](#encerramento-da-conta)
+<br>
+<br>
+![Conta_PT](//images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/7a4da3fc9797c2256f03e5811b06475d/Contas_PT.png)
 
-## Títulos
-O título é o documento gerado quando um cliente fecha uma compra utilizando o Customer Credit como meio de pagamento. 
-
-Em casos de compras parceladas, os títulos são referentes ao número de parcelas. Ou seja, se o cliente optou por fazer um pagamento em 10 parcelas, o sistema computará 10 títulos relacionados ao mesmo pedido. 
-
-Independente do meio de pagamento, todos os títulos no sistema podem ser visualizados e gerenciados pelo Admin e,  assim como as contas, também podem ser exportados e editados em massa. 
-
-### Estados de um título
-Há quatro status possíveis para os títulos.
-
-São eles:
-
-- Aberto; 
-- Pago; 
-- Vencido;
-- Cancelado. 
-
-Vale ressaltar que um título é sempre criado com o status de aberto e, dependendo de ações feitas no Admin ou de chamadas de API, pode transitar para o estado de Pago ou Cancelado.
-
-### Liquidação dos títulos
+## Titular
 
-A forma como os títulos serão liquidados precisa ser controlada pela loja.
+Apresenta informações sobre o status da conta (ativa, inativa), código de identificação, documento e email cadastrados do titular, datas de abertura da conta e da última atualização de dados. 
 
-Uma das opções de liquidação de títulos é gerar um link de pagamento. Nesse caso, uma vez que o esteja configurado, o cliente verá um botão "Pagar" junto do título na tela de Meus Créditos, que o levará para o link indicado. 
+## Status
 
-Além disso, os links de pagamento podem ser adicionados via arquivo CSV pelo Admin ou via API. 
+Exibe o valor do crédito disponível para o cliente utilizar em compras e o valor total a ser pago (em títulos), por compras já realizadas utilizando o Customer Credit como meio de pagamento.
 
-Desse modo, após ter recebido o pagamento referente a um título, basta marcá-lo como pago no nosso sitema. Isto pode ser feito de três maneiras: individualmente, em massa ou pela API.
+<div class="alert alert-warning">
+Quando o cliente realiza uma compra utilizando o Customer Credit, mas o pedido ainda não foi faturado (título emitido), o campo <b>Crédito reservado</b> também é exibido nesta tela contendo a informação do valor do pedido.
+</div>
 
-#### Liquidação individual
-Liquidar um título pelo Admin é bem simples. 
+## Gerenciar
 
-Os passos são:
+Indica o valor máximo de crédito concedido ao cliente e a tolerância a ser utilizada em compras. Estes valores podem ser editados a qualquer momento.
 
-1. Acesse o __Admin__;
-2. Clique no módulo __Customer Credit__;
-3. Em seguida, clique na seção __Títulos__;
-4. Selecione o __título__ que deseja editar;
-5. Clique no botão azul claro __“Marcar como pago”__.
-
-Assim, o título terá o estado alterado para “Pago”.
-
-#### Liquidação em massa
-Caso sua conta tenha muito títulos em aberto, não é viável alterar o status de cada um individualmente. 
-
-Desse modo, você pode utilizar o recurso de liquidação em massa, processo muito semelhante ao de atualização de contas em massa. O princípio é o mesmo: importar um arquivo CSV com os novos dados para o Admin. 
-
-Nesse caso, você deve alterar os valores da coluna status de “Aberto” para “Pago” e salvar as edições.
+## Títulos
 
-Em seguida, basta seguir o passo a passo:
+Lista contendo as seguintes informações sobre todos os títulos emitidos em compras realizadas pelo cliente:
 
-1. Acesse o __Admin__;
-2. Clique no módulo __Customer Credit__;
-3. Em seguida, clique na seção __Títulos__;
-4. Depois, clique no botão __“Atualizar em massa”__;
-5. Clique no botão cinza __“Escolher arquivo”__;
-6. Selecione o __arquivo CSV__ desejado.
+- Data de vencimento
+- Observação (mensagem específica para um título)
+- Id do pedido
+- Valor do título
+- Status do título (Aberto, Pago, Cancelado, Vencido)
 
-Aguarde o upload da planilha e os títulos serão liquidados todos de uma vez.
+## Extrato
 
-#### Liquidação por API
-Para liquidar um título por meio de uma API, você pode utilizar o [endpoint](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId- "endpoint") `PUT Change Invoice`. Essa API serve para alterar o estado de um título, não apenas para liquidá-lo.
+Exibe um relatório de todas as movimentações de pagamento e títulos realizadas para o cliente durante um período selecionado.
 
-Preencha o body com as seguintes informações:
+## Dependentes adicionais
 
-```json
-{
-"status": "string [Opened | Cancelled | Paid] (optional)", "observation": "string (optional)",
-"paymentLink": "string (URL) (optional)"
-}
-```
+A funcionalidade __Dependentes adicionais__ permite que o cliente possa compartilhar os créditos disponíveis para compras com outras pessoas cadastradas na conta.
 
-Para mais detalhes, confira nossa [documentação técnica sobre o Customer Credit](https://developers.vtex.com/docs/guides/customer-credit-api-overview "documentação técnica sobre o Customer Credit").
+Para cadastrar um novo dependente, siga os passos abaixo:
 
-## Dependentes adicionais
-Conforme suas regras de negócio, você pode compartilhar o limite de crédito das contas com demais usuários. 
+1. Dentro da conta do cliente, em __Dependentes adicionais__, clique em `NOVO`.
+2. Insira o email da pessoa a ser adicionada como dependente na conta do cliente.
+3. Clique em `CONFIRMAR`.
 
-A funcionalidade permite você cadastre novos dependentes para uma conta. Estes, por sua vez, poderão compartilhar o mesmo crédito disponível para pagar compras no SmartCheckout.
+A partir deste momento, o cliente e seu dependente poderão utilizar de forma compartilhada o valor em __Crédito disponível__ para realizar suas compras por meio do Customer Credit.
 
-Para cadastrar novos dependentes para uma conta, siga o passo a passo:
+## Encerramento da conta
 
-1. Acesse o __Admin__;
-2. Clique no módulo __Customer Credit__;
-3. Em seguida, clique na seção __Contas__;
-4. Selecione a __conta__ que deseja editar;
-5. No final da página, clique no botão azul __"Novo"__;
-6. Preencha o campo em branco com o __e-mail__ do novo dependente;
-7. Clique no botão azul __"Confirmar"__.
+Caso deseje encerrar a conta do cliente, na seção __Outros__, clique em `FECHAR CONTA`.
 
-Isso fará com que o dependente recém-adicionado seja  exibido no box de dependentes adicionais daquela conta.
+<div class="alert alert-warning">
+Uma conta do Customer Credit fechada não poderá ser reaberta novamente e os dados de títulos, extrato e dependentes adicionais serão apagados. Entretanto, após concluir o encerramento da conta, caso deseje, você poderá <a href="https://help.vtex.com/pt/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#criar-contas-individualmente">abrir uma nova conta</a> para o cliente utilizando o mesmo email da conta encerrada.
+</div>
diff --git a/docs/tracks/pt/managing-customer-credit-invoices.md b/docs/tracks/pt/managing-customer-credit-invoices.md
new file mode 100644
index 000000000..4d86e031a
--- /dev/null
+++ b/docs/tracks/pt/managing-customer-credit-invoices.md
@@ -0,0 +1,73 @@
+---
+title: 'Gerenciando títulos no Customer Credit'
+id: vtf5UVQcmlb0kHBZYYmM3
+status: PUBLISHED
+createdAt: 2024-02-07T21:31:46.690Z
+updatedAt: 2024-02-09T12:30:53.684Z
+publishedAt: 2024-02-09T12:30:53.684Z
+firstPublishedAt: 2024-02-07T21:44:30.527Z
+contentType: trackArticle
+productTeam: Financial
+slug: gerenciando-titulos-no-customer-credit
+locale: pt
+trackId: 1hCRg21lXYy2seOKgqQ2CC
+trackSlugPT: customer-credit-como-comecar
+---
+
+A tela de __Títulos__ no Admin VTEX (__Aplicativos > Customer Credit > Títulos__), permite que você tenha acesso as informações de todos títulos emitidos por clientes cadastrados no Customer Credit em sua loja. Por meio desta funcionalidade, você pode executar as seguintes ações:
+
+- [Filtrar visualização de títulos](#filtro-de-titulos) 
+- [Verificar detalhes de cada título](#detalhes-do-titulo)
+- [Liquidar títulos](#liquidar-titulos)
+<br>
+<br>
+![Invoices_PT](//images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/3ac50b7bdade789abccccda8abe14352/Invoices_PT.JPG)
+
+## Filtro de títulos
+
+Para selecionar a lista de títulos a ser exibida é possível clicar em um dos quatro status (Aberto, Pago, Cancelado ou Vencido), ou inserir o número de identificação do pedido para qual o título foi emitido.
+
+<div class="alert alert-warning">
+No Customer Credit, todos os títulos são criados com o status <b>Aberto</b>.
+</div>
+
+## Detalhes do título
+
+Ao clicar sobre um título específico, a página __Detalhes do título__ apresenta as seguintes informações: valor do título emitido, data de vencimento, link de pagamento (caso exista), identificação da conta onde foi emitido, identificação do pedido e observações (mensagens específicas sobre o título).
+
+## Liquidar títulos
+
+Para facilitar o processo de pagamento de um título, é possível fornecer um link de pagamento diretamente ao cliente. Este link pode ser adicionado no título de duas formas:
+
+- Utilizar a função `IMPORTAR` para inserir dados de uma planilha .csv.
+- Via endpoint [PUT Change Invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-) do Customer Credit API.
+
+<div class="alert alert-info">
+  Após você realizar um dos procedimentos acima, o cliente terá acesso ao botão <b>PAGAR</b> que ficará disponível na sua área do cliente no site da loja (<b>Minha Conta > Meus Créditos</b>).
+</div>
+
+### Liquidação individual
+
+Após confirmar o pagamento de um título, você pode liquidá-lo da seguinte forma:
+
+1. No Admin VTEX, acesse __Aplicativos > Customer Credit > Títulos__, ou digite __Títulos__ na barra de busca no topo da página.
+2. Clique sobre o título desejado.
+3. Na página __Detalhes do título__, clique sobre __Marcar como pago__.
+4. Na página de __Títulos__, confirme que o status do título está indicado como __Pago__.
+
+### Liquidação em massa
+
+Caso você deseje confirmar o pagamento de vários títulos ao mesmo tempo, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Aplicativos > Customer Credit > Títulos__, ou digite __Títulos__ na barra de busca no topo da página.
+2. Clique no botão `EXPORTAR`.
+3. Acesse a planilha .csv baixada e modifique a informação do campo `Status` para `Paid` nas linhas correspondentes ao títulos que deseja liquidar. Salve a planilha. 
+4. Clique no botão `IMPORTAR`.
+5. Selecione ou insira a planilha .csv no espaço __Solte aqui seu CSV ou escolha ou arquivo__.
+6. Clique no botão `IMPORTAR ARQUIVO`.
+7. Após a planilha ser carregada no Admin, verifique na tela de __Títulos__ se os títulos atualizados estão descritos como __Pago__. 
+
+### Liquidação por API
+
+Você também pode liquidar um título por meio do endpoint [PUT - Change invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-). Para mais informações sobre os endpoints da API de Customer Credit , acesse [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api#overview).
+
diff --git a/docs/tracks/pt/managing-sales-associates-in-instore.md b/docs/tracks/pt/managing-sales-associates-in-instore.md
index b7348ff1f..30020b774 100644
--- a/docs/tracks/pt/managing-sales-associates-in-instore.md
+++ b/docs/tracks/pt/managing-sales-associates-in-instore.md
@@ -3,8 +3,8 @@ title: 'Gerenciar vendedores no VTEX Sales App'
 id: 5pqtuvi97FFZiGf7MlSe8q
 status: PUBLISHED
 createdAt: 2023-04-17T21:01:21.431Z
-updatedAt: 2023-05-31T16:15:21.153Z
-publishedAt: 2023-05-31T16:15:21.153Z
+updatedAt: 2024-01-05T19:59:15.811Z
+publishedAt: 2024-01-05T19:59:15.811Z
 firstPublishedAt: 2023-04-25T20:13:04.431Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,19 +14,10 @@ trackId: zav76TFEZlAjnyBVL5tRc
 trackSlugPT: instore-primeiros-passos-e-configuracoes
 ---
 
-Depois de fazer as [configurações básicas do VTEX Sales App no Admin](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), você pode adicionar outras vendedores ao sistema ou gerenciar vendedores já cadastrados.
+Após realizar as [configurações básicas do VTEX Sales App no Admin](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), é possível adicionar novos vendedores ao sistema ou gerenciar os vendedores já cadastrados. 
+A categoria Vendedores representa uma seção dentro das Configurações da loja do Admin VTEX, exibindo a lista completa dos vendedores registrados no aplicativo [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) da loja. Dentro dessa página, é possível administrar as informações dos vendedores em todas as [contas franquias](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) da sua loja, realizando operações de [cadastrar](#cadastrar-vendedor), [buscar](#buscar-vendedor), [filtrar](#filtrar-vendedores), [editar](#editar-vendedor) e [excluir](#excluir-vendedor)].
 
-**Vendedores** é uma página das **Configurações da loja** do Admin VTEX que apresenta a listagem de vendedores cadastrados no aplicativo [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) da loja. Nela, você pode gerenciar informações dos vendedores em todas as [contas franquias](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) da sua loja.
-
-Esta página permite que você gerencia seus vendedores a partir das seguintes ações:
-
-* [Cadastrar](#cadastrar-vendedor)
-* [Buscar](#buscar-vendedor)
-* [Filtrar](#filtrar-vendedores)
-* [Editar](#editar-vendedor)
-* [Excluir](#excluir-vendedor)
-
-![vendedores-pt](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/fbd82da71cf7d2e4a8936b2fd2aac877/PT.png)
+![vendedores-pt](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/fbd82da71cf7d2e4a8936b2fd2aac877/PT.png)
 
 A página apresenta as seguintes informações: 
 
@@ -34,25 +25,23 @@ A página apresenta as seguintes informações:
 | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Nome             | Nome que identifica o vendedor, definido na etapa [Cadastrar vendedor](#cadastrar-vendedor). |
 | Código           | Código identificador de cada vendedor, o mesmo cadastrado no sistema da loja física.                                                                                                 |
-| Loja             | Nome identificador da [conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) que o vendedor está cadastrado.                              |
+| Loja             | Nome identificador da [conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) em que o vendedor está cadastrado.                              |
 | Email            | Email de acesso referente a cada vendedor.                                                                                                                                           |
 
 ## Cadastrar vendedor
 
 Você pode cadastrar um vendedor seguindo os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** **> inStore > Vendedores**, ou digite **Vendedores** na barra de busca no topo da página.
+1. No Admin VTEX, acesse **Configurações da loja** **> Sales App > Vendedores**, ou digite **Vendedores** na barra de busca no topo da página.
 2. Clique no botão `+ Cadastrar vendedor`.
 3. Preencha os [campos de cadastro do vendedor](#campos-de-cadastro-do-vendedor).
 4. Clique em `Cadastrar`.
 5. Clique em `Salvar` para confirmar o cadastro do vendedor.  
 
-Após o cadastro, o vendedor irá receber um email confirmando o cadastro e redirecionando para a opção de login do vendedor ao aplicativo inStore.
-
-![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+Após o cadastro, o vendedor irá receber um email de confirmação do cadastramento, e com redirecionamento para a opção de login do vendedor ao aplicativo Sales App.
 
 <div class ="alert alert-warning">
-<p>Os vendedores cadastrados no inStore não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin seu cadastro será excluído.</p> 
+<p>Os vendedores cadastrados no Sales App não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin, seu cadastro será excluído.</p> 
 </div>
 
 ### Campos de cadastro do vendedor
@@ -61,19 +50,20 @@ Após o cadastro, o vendedor irá receber um email confirmando o cadastro e redi
 
 * **Nome do vendedor:** nome do vendedor que será cadastrado. Campo obrigatório.
 * **Código do vendedor:** código que identifica o vendedor, igual ao cadastrado no sistema da loja física.
-* **Email:** email de acesso do vendedor ao inStore. Campo obrigatório.
+* **Email:** email de acesso do vendedor ao Sales App. Campo obrigatório.
+* **Permitir acesso à performance de vendas de outros vendedores:** caixa de seleção que permite a visualização da performance de vendas de outros vendedores (quando marcada) ou apenas o acesso à informações da sua própria performance de vendas (quando não marcada).
 
 #### Loja física
 
 * **Loja:** [conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) em que o vendedor será cadastrado. Campo obrigatório.
 
 <div class ="alert alert-info">
-<p>As alterações podem levar até 15 minutos para serem processadas e aplicadas no inStore.</p> 
+<p>As alterações podem levar até 15 minutos para serem processadas e aplicadas no Sales App.</p> 
 </div>
 
 ## Buscar vendedor
 
-Você pode buscar um vendedor utilizando a barra de busca. É possível pesquisar pelo nome do vededor, nome da loja e email do vendedor.
+Você pode buscar informações sobre um vendedor utilizando a barra de busca. Por meio dela, você tem acesso ao nome e email do vendedor, e nome da loja na qual ele está cadastrado.
 
 ## Filtrar vendedores
 
@@ -90,10 +80,10 @@ Clique no filtro `Loja` para filtrar os vendedores pelo nome de uma loja física
 
 ## Inativar vendedor
 
-Você pode inativar um vendedor seguindo os passos a seguir.
+Você pode inativar um vendedor seguindo os passos a seguir:
 
 1. Na linha do vendedor que deseja editar, clique em <i class="fas fa-ellipsis-v"></i>.
 2. Clique em <i class="fa-solid fa-box-archive"></i> `Inativar`.
 3. Clique em `Inativar` para confirmar e finalizar.
 
-Uma vez que o vendedor foi inativado, ele perderá o acesso ao aplicativo do inStore e não conseguirá mais realizar o login. Para excluir definitivamente um vendedor, entre em contato com nosso [suporte](https://support.vtex.com/hc/pt-br/requests).
+Uma vez que o vendedor foi inativado, ele perderá o acesso ao aplicativo do Sales App e não conseguirá mais realizar o login. Para excluir definitivamente um vendedor, entre em contato com nosso [suporte](https://support.vtex.com/hc/pt-br/requests).
diff --git a/docs/tracks/pt/managing-shipping-rates.md b/docs/tracks/pt/managing-shipping-rates.md
index 4856d5852..223cf5401 100644
--- a/docs/tracks/pt/managing-shipping-rates.md
+++ b/docs/tracks/pt/managing-shipping-rates.md
@@ -18,7 +18,7 @@ Para a correta configuração de uma nova transportadora, é importante detalhar
 
 Ela é usada para registrar os CEPs atendidos, os valores cobrados, as faixas de peso consideradas e os valores adicionais de cada transportadora.
 
-![planilha-frete-pt](https://images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
+![planilha-frete-pt](//images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
 
 ## Como montar a planilha
 
diff --git a/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 91401ca71..ba09d36ad 100644
--- a/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -18,7 +18,7 @@ Após instalar e configurar o TikTok for Business, você poderá gerenciar a int
 
 Qualquer usuário logado no Admin VTEX poderá acessar essa área de gerenciamento do TikTok. Porém, ao interagir com os botões dessa área, o usuário será redirecionado para ambientes do TikTok – TikTok Business Center, TikTok Ads Manager e TikTok Catalog Manager – onde precisam das permissões necessárias para visualizar o conteúdo e realizar alterações.
 
-![manage-tiktok-integration](https://images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
+![manage-tiktok-integration](//images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
 
 A partir dessa página, é possível:
 
diff --git a/docs/tracks/pt/mapping-colors-and-sizes.md b/docs/tracks/pt/mapping-colors-and-sizes.md
index b3b706bf7..e7d34dba5 100644
--- a/docs/tracks/pt/mapping-colors-and-sizes.md
+++ b/docs/tracks/pt/mapping-colors-and-sizes.md
@@ -65,7 +65,7 @@ Deve-se escolher a cor disponível mais próxima que, no caso da Wish, "Gelo" po
   OBS: o cabeçalho da tabela deve ser preenchida exatamente como está no exemplo abaixo. Lembre-se de não adicionar caracteres especiais como enter ou espaço no preenchimento dessa tabela. 
   </div>
 
-![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
+![PT - Tabela Wish](//images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
 ## Fazendo o upload
 
diff --git a/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
index 0c7942638..9ffa447c9 100644
--- a/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Mapear categorias e atributos dos produtos para o Mercado Livre'
 id: 5XNeiye4rS4oao2MueSUeA
 status: PUBLISHED
 createdAt: 2018-08-13T12:58:18.100Z
-updatedAt: 2022-09-05T19:01:28.441Z
-publishedAt: 2022-09-05T19:01:28.441Z
+updatedAt: 2024-07-23T21:39:55.195Z
+publishedAt: 2024-07-23T21:39:55.195Z
 firstPublishedAt: 2018-08-13T14:27:50.859Z
 contentType: trackArticle
 productTeam: Channels
@@ -27,7 +27,7 @@ Seus produtos precisam ter o <a href="https://help.vtex.com/pt/tutorial/estoque-
 
 ## Mapear categorias
 
-Para acessar a página de mapeamento, você deverá acessar no Admin *MARKETPLACE > Integrações > Configurações*, dentro do card da integração com o Mercado Livre selecionar o ícone de engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" /> e clicar na opção `Realizar mapeamento`.
+Para acessar a página de mapeamento, você deverá acessar no Admin **Marketplace > Marketplaces e Integrações**, na integração com o Mercado Livre selecione a opção `Realizar mapeamento`.
 
 Você será direcionado à página de mapeamento do Mercado Livre e a página apresentará uma lista com as categorias da sua loja VTEX. O mapeamento das categorias permite que exista uma correspondência entre as categorias da sua loja e as categorias do Mercado Livre. Dessa forma, os produtos enviados serão exibidos na categoria equivalente no Mercado Livre.
 
@@ -37,18 +37,18 @@ A lista de categorias da sua loja VTEX inclui o status de seu  mapeamento  por m
 
 | Ícone | Status | Descrição |
 | ---------- | ---------- | ---------- | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado**| Indica que o mapeamento da categoria foi concluído. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6v4eFsWHVy8F5VIqTVLQD9/e63d945d60a958a37246f57d919eede8/mapeamentoincompleto_mapper.JPG" /> | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto.  Para solucionar esse problema basta refazer o mapeamento da categoria. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado** | Indica que a categoria não foi mapeada. |
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado**| Indica que o mapeamento da categoria foi concluído. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6v4eFsWHVy8F5VIqTVLQD9/e63d945d60a958a37246f57d919eede8/mapeamentoincompleto_mapper.JPG" /> | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto.  Para solucionar esse problema basta refazer o mapeamento da categoria. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado** | Indica que a categoria não foi mapeada. |
 
 Ainda na página de mapeamento, existem as seções **Categoria do marketplace** e **Mapeamento de Atributos**, ambos com uma opção de menu de seleção, onde ao clicar sobre a seta, aparecem novos campos e informações.
 
 Para realizar o mapeamento de categorias:
 
-1. Acesse o Admin.
-2. No módulo MARKETPLACE, selecione **Integrações** e clique em `Configurações`.
-3. No cartão do Mercado Livre, clique na engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+1. Acesse o Admin VTEX vá em **Marketplace > Marketplaces e Integrações.**  
+2. Selecione a integração com o Mercado Livre.  
+3. Clique na integração do Mercado Livre.
 4. Clique em `Realizar mapeamento`. Uma nova janela será aberta com a página de mapeamento.
 5. Na seção **Categorias da loja**, escolha a categoria que deseja mapear.
 6. Selecione na seção **Categoria do marketplace** a categoria correspondente no marketplace do produto que você deseja enviar.
@@ -57,15 +57,15 @@ Para finalizar o mapeamento da categoria, você deve seguir o passo a passo abai
 
 ## Mapear atributos
 
-![Início (13)](https://images.ctfassets.net/alneenqid6w5/owf1A0SnYfOkoNCGDlTFj/ca731b95328853d12ee9872ef14b8aaf/In__cio__13_.gif)
+![Início (13)](//images.ctfassets.net/alneenqid6w5/owf1A0SnYfOkoNCGDlTFj/ca731b95328853d12ee9872ef14b8aaf/In__cio__13_.gif)
 
 O mapeamento dos atributos permite que exista uma correspondência entre o padrão da sua loja VTEX e o padrão utilizado pelo Mercado Livre. Cada categoria possui seus atributos obrigatórios pelo Mercado Livre e é necessário preenchê-los para que o mapeamento seja concluído. Os campos não mapeados não impedem que o mapeamento ocorra, porém quanto mais atributos enviados para o Mercado Livre seu produto tiver, melhor rankeado ele será no marketplace.
 
 Para mapear os atributos, siga os passos abaixo:
 
-1. Acesse o Admin.
-2. No módulo MARKETPLACE, selecione **Integrações** e clique em `Configurações`.
-3. No cartão do Mercado Livre, clique na engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+1. Acesse o Admin VTEX vá em **Marketplace > Marketplaces e Integrações.**  
+2. Selecione a integração com o Mercado Livre.  
+3. Clique na integração do Mercado Livre.
 4. Clique em `Realizar mapeamento`. Uma nova janela será aberta com a página de mapeamento.
 5. Na seção **Mapeamento de Atributos**, preencha os campos com os atributos que deseja mapear (o asterisco indica preenchimento obrigatório).
 6. Caso tenha preenchido os atributos *Cor* ou *Tamanho*, na coluna **Valores de Atributo** clique na `Cor equivalente` ou `Tamanho equivalente` e selecione a opção de valor correspondente.
@@ -74,78 +74,4 @@ Para mapear os atributos, siga os passos abaixo:
 
 Ao finalizar o mapeamento de categorias e atributos corretamente, o status da categoria mudará para **Mapeado** <img class="shadow-4" src="https://images.contentful.com/alneenqid6w5/6Zu9VaGjbucOthXQsFwTD1/8681ab7d7e4fd12b41daae3c69afd552/mapper_correto.JPG" /> e seus produtos serão anunciados no site do Mercado Livre.
 
-### Tabela de medidas 
-
-A Tabela de medidas permite que os clientes saibam o tamanho aproximado do seu produto, proporcionando uma melhor experiência no momento de selecionar o tamanho de um produto. Ao informar detalhadamente as medidas do seu produto, você evita devoluções e reclamações por tamanho errado.
-
-Ao receber menos devoluções de seus produtos, sua reputação no Mercado Livre melhora e exposição dos seus produtos. A tabela de medidas está disponível para produtos da categoria `Calçados` e as medidas são feitas em centímetros (cm).
-
-A tabela de medidas é personalizável, ou seja, é possível selecionar opções de tabelas de acordo com a sua necessidade, com as medidas aproximadas de cada tamanho do produto disponível. 
-
-#### Adicionar tabela personalizada
-
-Para adicionar a tabela de medidas personalizada, você deve seguir os passos abaixo:
-
-1. Acesse o Admin VTEX.
-2. Em *MARKETPLACE*, selecione a opção **Integrações** e clique em `Configurações`.
-3. No cartão do Mercado Livre, clique na engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
-4. Selecione a opção `Realizar mapeamento`. Uma nova janela será aberta com a interface de mapeamento.
-5. Na seção Tabela de medida, clique no ícone `+`.
-6. Selecione a opção *Tabela personalizada*.
-7. Preencha um nome válido para sua tabela no campo **Nome da tabela**.
-8. No campo **Domínio** selecione a opção para sua tabela personalizada.
-9. No campo **Gênero**, selecione a opção correspondente ao gênero do produto.Existem cinco tipos de gêneros diferentes:
-   * **Mulheres**
-   * **Homens**
-   * **Meninas**
-   * **Meninos**
-   * **Sem gênero**
-10. No campo **Tamanho principal**, escolha uma opção de modelo de tabela. Existem cinco modelos diferentes:
-    * **BR:** utiliza os tamanhos padrões de tamanho no Brasil.
-    * **Tamanho da marca:** utiliza os tamanhos padrões da marca do produto selecionado.
-    * **US:** utiliza as medidas padrões de tamanho nos Estados Unidos. As medidas podem variar de acordo com o gênero.
-    * **EU:** utiliza as medidas padrões de tamanho na União Europeia.
-    * **UK:** utiliza as medidas padrões de tamanho no Reino Unido.
-11. No campo **Template**, clique em `CSV`. Você realizará o download de um template de tabela que precisa ser preenchido conforme as instruções da seção Preencher o template da Tabela de Medidas.
-
-#### Preencher o template da Tabela de Medidas
-
-Durante o preenchimento, todas as colunas devem ser preenchidas. Caso você opte por não informar ou utilizar algumas das medidas padrões, preencha com um `-`.
-
-Nesse template, você deverá configurar as colunas e preencher com os valores dos tamanhos e medidas em centímetros dos respectivos tamanhos.
-
-Para configurar automaticamente a planilha acesse *Dados > Texto* para colunas, selecione a opção **Delimitado**, clique em Avançar. No campo **Delimitadores**, selecione a opção *Vírgula*, clique em `Avançar`, e finalize clicando em `Concluir`.
-
-O template da tabela de medidas possui as seguintes colunas:
-
-| **Colunas** | **Descrição** | **Preenchimento** |
-| ---------- | ---------- | ---------- |
-| **Foot Length** | Medida em centímetros do tamanho | Preencha cada linha com a medida em centímetros dos tamanhos que serão preenchidos nas próximas colunas |
-| **Manufacturer Size** | Número da medida padrão de tamanho da marca do produto selecionado | Preencha cada linha com a medida padrão da marca do produto |
-| **Foot Length to** | Medida em centímetros do tamanho máximo que o pé deve ter para se acomodar no respectivo tamanho | Preencha cada linha com a medida em centímetros dos tamanhos máximos que serão preenchidos nas próximas colunas |
-| **BR Size** | Número da medida padrão de tamanho no Brasil | Preencha cada linha com o tamanho correspondente seguido de BR. Por exemplo, 38 BR |
-| **X-US Size** | Número da medida padrão de tamanho nos Estados Unidos. As medidas podem variar de acordo com o gênero | Preencha cada linha com o tamanho correspondente seguido de US. Por exemplo, 24 US |
-| **EU Size** | Número da medida padrão de tamanho na União Europeia | Preencha cada linha com o tamanho correspondente seguido de EU. Por exemplo, 38 EU |
-| **UK Size** | Número da medida padrão de tamanho no Reino Unido | Preencha cada linha com o tamanho correspondente seguido de UK. Por exemplo, 12 UK |
-
-<div class = "alert alert-info">
-Importante reforçar a necessidade de utilizar “espaço” entre o número e a medida (cm), separar os números utilizando pontos (.), preencher todas as colunas e conferir se os campos <b>Gênero</b> e <b>Tamanho</b> foram selecionados corretamente.
-</div>
-
-#### Fazer upload da tabela de medidas
-
-Depois de preencher a planilha de mapeamento, faça o seu upload:
-
-1. Acesse o Admin VTEX.
-2. Em *MARKETPLACE*, selecione a opção **Integrações** e clique em `Configurações`.
-3. No cartão do Mercado Livre, clique na engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
-4. Selecione a opção `Realizar mapeamento`. Uma nova janela será aberta com a interface de mapeamento.
-5. Na seção Tabela de medida, clique no ícone `+`.
-6. Selecione a opção *Tabela personalizada*.
-7. Clique em `Escolha um arquivo`.
-8. Selecione o arquivo do template da planilha.
-9. Clique em `Adicionar`.
-
-Ao finalizar, sua tabela de medida personalizada terá sido criada com sucesso.
-
-<div class = "alert alert-info"> Caso ocorra algum erro, o problema será indicado para que seja resolvido e o upload deverá ser realizado novamente.</div>
+Após realizar o mapeamento de produtos de moda como, roupas e calçados, é necessário enviar a tabela de medidas dos produtos ao Mercado Livre. Para saber como preencher e enviar a tabela de medidas, siga o tutorial [Tabela de medidas do Mercado Livre](https://help.vtex.com/pt/tutorial/tabela-de-medidas-do-mercado-livre--5dCc9IJ83SjllG75BVCWnr)
diff --git a/docs/tracks/pt/mapping-product-categories-and-attributes.md b/docs/tracks/pt/mapping-product-categories-and-attributes.md
new file mode 100644
index 000000000..5baff52d4
--- /dev/null
+++ b/docs/tracks/pt/mapping-product-categories-and-attributes.md
@@ -0,0 +1,32 @@
+---
+title: 'Mapeamento de categorias e atributos de produtos'
+id: 1Ue3UIHrelsvjYpkLL4IRx
+status: PUBLISHED
+createdAt: 2023-08-11T01:20:24.164Z
+updatedAt: 2023-08-11T02:32:16.459Z
+publishedAt: 2023-08-11T02:32:16.459Z
+firstPublishedAt: 2023-08-11T01:56:55.281Z
+contentType: trackArticle
+productTeam: Channels
+slug: mapeamento-de-categorias-e-atributos-de-produtos
+locale: pt
+trackId: 4ZSHEiuTkh8HR9ubJQj8BP
+trackSlugPT: integracao-livelo
+---
+
+Após fazer as configurações de conta na Livelo na VTEX e integrar o conector, é necessário categorizar e enviar as variações e [especificações de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) para o marketplace. O envio dessas informações é feito por meio do menu **Mapeamento de categorias**.  
+
+Esta funcionalidade fará a correspondência entre as categorias, variações e atributos da sua loja e os padrões adotados pela Livelo, agilizando o processo de catalogação dos seus produtos no Marketplace, permitindo que estes fiquem disponíveis para venda em menos tempo.  
+
+Para realizar o mapeamento de categorias, siga as instruções abaixo.  
+
+1. No Admin VTEX, acesse ***Hub de Extensões* > Livelo > Mapeamento de categorias** ou digite **Mapeamento de categorias na barra de busca.**  
+2. Clique na categoria que deseja mapear, isso abrirá uma barra lateral para realizar a correspondência no marketplace.  
+3. Na barra lateral, clique em **Categoria do marketplace.**  
+4. Clique no ícone  <i class="fas fa-angle-down"></i>  e, em seguida, selecione a categoria correspondente no marketplace.  
+5. Clique em **Mapeamento de Atributos** e faça as correspondências dos campos que aparecerão na tela.  
+6. Clique no botão `Salvar Alterações` 
+
+<div class="alert alert-info">
+  Os campos de <b>Mapeamento de Atributos</b> com asterisco <b>(*)</b> são obrigatórios.  
+</div>
diff --git a/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md b/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md
new file mode 100644
index 000000000..ac86fb3bf
--- /dev/null
+++ b/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md
@@ -0,0 +1,32 @@
+---
+title: 'Mapeamento de categorias e atributos de produtos Rappi'
+id: 6iVRkhA3WHvynIlwgQhjPc
+status: PUBLISHED
+createdAt: 2024-05-31T20:42:26.540Z
+updatedAt: 2024-05-31T20:52:02.358Z
+publishedAt: 2024-05-31T20:52:02.358Z
+firstPublishedAt: 2024-05-31T20:52:02.358Z
+contentType: trackArticle
+productTeam: Channels
+slug: mapeamento-de-categorias-e-atributos-de-produtos-rappi
+locale: pt
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugPT: integracao-rappi
+---
+
+Após fazer as configurações de conta na Rappi na VTEX e integrar o conector, é necessário categorizar e enviar as variações e [especificações de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) para o marketplace. O envio dessas informações é feito por meio do menu **Mapeamento de categorias**.  
+
+Esta funcionalidade fará a correspondência entre as categorias, variações e atributos da sua loja e os padrões adotados pela Rappi, agilizando o processo de catalogação dos seus produtos no Marketplace, permitindo que estes fiquem disponíveis para venda em menos tempo.  
+
+Para realizar o mapeamento de categorias, siga as instruções abaixo.  
+
+1. No Admin VTEX, acesse ***Hub de Extensões* > Rappi > Mapeamento de categorias** ou digite **Mapeamento de categorias na barra de busca.**  
+2. Clique na categoria que deseja mapear, isso abrirá uma barra lateral para realizar a correspondência no marketplace.  
+3. Na barra lateral, clique em **Categoria do marketplace.**  
+4. Clique no ícone  <i class="fas fa-angle-down"></i>  e, em seguida, selecione a categoria correspondente no marketplace.  
+5. Clique em **Mapeamento de Atributos** e faça as correspondências dos campos que aparecerão na tela.  
+6. Clique no botão `Salvar Alterações` 
+
+<div class="alert alert-info">
+  Os campos de <b>Mapeamento de Atributos</b> com asterisco <b>(*)</b> são obrigatórios.  
+</div>
diff --git a/docs/tracks/pt/mercado-libre-marketplace.md b/docs/tracks/pt/mercado-libre-marketplace.md
index c3ca29545..1c17507bc 100644
--- a/docs/tracks/pt/mercado-libre-marketplace.md
+++ b/docs/tracks/pt/mercado-libre-marketplace.md
@@ -1,10 +1,10 @@
 ---
 title: 'Mercado Livre '
 id: 51oWBHvVxSs8eAwLQhSbSd
-status: CHANGED
+status: PUBLISHED
 createdAt: 2020-09-23T20:16:36.804Z
-updatedAt: 2023-03-28T21:46:05.528Z
-publishedAt: 2021-09-04T11:14:45.743Z
+updatedAt: 2024-03-11T22:19:17.941Z
+publishedAt: 2024-03-11T22:19:17.941Z
 firstPublishedAt: 2020-09-23T20:31:42.798Z
 contentType: trackArticle
 productTeam: Channels
@@ -18,7 +18,7 @@ O [Mercado Livre](https://www.mercadolivre.com.br/) é um dos líderes do e-comm
 
 Sua operação está presente nos países: Argentina, Brasil, Chile, Colômbia,  México, Uruguai e Venezuela.
 
-![mercado-livre-reproducao-w-970x550](https://images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/9f13547ee20c96383f18e8151f98177e/mercado-livre-reproducao-w-970x550.jpg)
+![mercado-livre-reproducao-w-970x550](//images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/9f13547ee20c96383f18e8151f98177e/mercado-livre-reproducao-w-970x550.jpg)
 
 O marketplace do Mercado Livre oferece um ambiente de negociação on-line totalmente automatizado, organizado por tópicos e fácil de usar. Esse serviço oferece aos compradores uma grande variedade de itens novos e usados, permitindo que empresas e indivíduos anunciem itens e realizem suas vendas e compras no maior mercado da América Latina.
 
diff --git a/docs/tracks/pt/merchandising-rules.md b/docs/tracks/pt/merchandising-rules.md
index a7f21b629..3e3cceb25 100644
--- a/docs/tracks/pt/merchandising-rules.md
+++ b/docs/tracks/pt/merchandising-rules.md
@@ -3,8 +3,8 @@ title: 'Regras de merchandising'
 id: 5tBSYXb9EIdePa0MWTnFd0
 status: PUBLISHED
 createdAt: 2020-03-05T18:53:37.305Z
-updatedAt: 2023-04-03T22:01:51.692Z
-publishedAt: 2023-04-03T22:01:51.692Z
+updatedAt: 2024-01-29T17:07:18.414Z
+publishedAt: 2024-01-29T17:07:18.414Z
 firstPublishedAt: 2020-03-05T19:58:55.021Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -21,44 +21,45 @@ As Regras de merchandising são uma configuração prioritária. Portanto, se vo
 É possível determinar regras de merchandising para:
 
 * **Marcas:** é possível configurar que produtos de uma marca apresentam maior relevância que as demais. Quando o cliente pesquisar por “smartphone”, por exemplo, os produtos da marca vão aparecer no início da listagem e os produtos de outras marcas abaixo deles.
-* **Produto:** Outra possibilidade é promover um produto específico. Por exemplo: definir que quando pesquisar “camiseta de corrida”, o produto “Camiseta Running” seja o primeiro resultado apresentado na listagem.
+* **Produtos:** Outra possibilidade é promover um produto específico. Por exemplo: definir que quando pesquisar “camiseta de corrida”, o produto “Camiseta Running” seja o primeiro resultado apresentado na listagem.
 
 O que define em quais casos aplicar uma regra de merchandising são as Regras de ativação, definidas durante a criação da regra de merchandising. Elas permitem criar condições para identificar os cenários em que o efeito será ativado.
 
-## Listagem de Regras de Merchandising
-
 No Admin VTEX, a página **Storefront** > **Intelligent Search** > **Regras de merchandising** permite que você realize as seguintes ações: 
 
 * [Criar regra de merchandising](#criar-regras-de-merchandising)
 * [Buscar regra de merchandising](#buscar-regras-de-merchandising)
 * [Editar regra de merchandising](#editar-regras-de-merchandising)
-* [Deletar regra de merchandising](#deletar-regras-de-merchandising)
+* [Excluir regra de merchandising](#excluir-regras-de-merchandising)
 
-![configurar regras de merchandising-pt](https://images.ctfassets.net/alneenqid6w5/4RIkVevSJArI3LhEHjELHu/cb0f5d067d0e668c84a6cec1dd1fdbf5/image.png)
+![regras-merch-pt](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/725d7d991d98ca633d7efd56ec14a254/regras-merch-pt.PNG)
 
 | Coluna | Descrição |
 | - | - |
-| Nome | Nome que identifica a regra de merchandising, definido na etapa [Criar regras de merchandising](#criar-regras-de-merchandising). |
-| Data de início | Data que define o início da disponibilidade da regra de merchandising. |
-| Data de término | Data que define o término da disponibilidade da regra de merchandising. |
-| Ativo | Opção que ativa ou desativa uma regra de merchandising. |
-| Ações | Ação de deletar ou editar uma regra de merchandising. |
+| __Nome__ | Nome que identifica a regra de merchandising, definido na etapa [Criar regras de merchandising](#criar-regras-de-merchandising). |
+| __Data de início__ | Data que define o início da disponibilidade da regra de merchandising. |
+| __Data de término__ | Data que define o término da disponibilidade da regra de merchandising. |
+| __Tipo__ | Indica o [tipo de edição](#tipos-de-edicao) utilizado na regra de merchandising. |
+| __Ativo__ | Opção que ativa ou desativa uma regra de merchandising. |
+| __Ações__  <i class="fas fa-ellipsis-v"></i> | Menu com ações de `Editar` ou `Excluir` uma regra de merchandising. |
 
 ### Criar regras de merchandising
 
-Para configurar uma regra de merchandising, clique em `Adicionar`. Saiba mais sobre todas as informações necessárias para criar uma regra de merchandising nas seções a seguir.
+Para configurar uma regra de merchandising, clique em `+ Adicionar`. Saiba mais sobre todas as informações necessárias para criar uma regra de merchandising nas seções a seguir.
 
 #### Tipos de edição
 
-Ao criar Regras de merchandising, você pode escolher entre dois tipos de edição disponíveis: o [Editor manual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) e o [Editor visual (Beta)](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3). Veja a seguir as funcionalidades disponíveis em cada um para decidir qual é o mais adaptado ao seu caso de uso:
+Existem dois tipos de edição para criar Regras de merchandising: o [Editor manual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) e o [Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr).
+
+Veja a seguir as funcionalidades de cada editor:
 
-| Funcionalidade | Descrição | Editor manual | Editor visual (Beta) |
+| Funcionalidade | Descrição | Editor manual | Editor visual |
 |---|---|---|---|
 | Regras de ativação  | Definir condições para a Regra de merchandising ser ativada. | Sim | Sim |
 | Regras de customização | Controlar os resultados de busca a partir de condições específicas. | Sim | Não |
 | Pré-visualização | Visualizar uma prévia de como os resultados de busca aparecerão para os clientes durante a navegação na loja. | Não | Sim |
 | Reordenar resultados de busca | Alterar a ordem dos itens listados como resultados de busca. | Não | Sim |
-| Fixar resultado em determinada posição | Definir uma posição fixa para determinado item de um resultado de busca. | Não | Sim |
+| Fixar produto nas primeiras posições | Definir que o produto sempre aparecerá nas primeiras posições dos resultados de busca. | Não | Sim |
 
 ### Buscar regra de merchandising
 
@@ -68,11 +69,11 @@ Para pesquisar uma regra de merchandising, digite o nome da regra de merchandisi
 
 Você pode editar as informações uma regra de merchandising seguindo os passos abaixo.
 
-1. Clique no botão lápis <i class="fa-solid fa-pencil"></i>.
+1. Clique no menu <i class="fas fa-ellipsis-v"></i> na linha da regra de merchandising e, em seguida, no botão <i class="fas fa-pencil-alt"></i> `Editar`.
 2. Altere a informação desejada da regra de merchandising.
 3. Clique em `Salvar`.
 
-### Deletar regra de merchandising
+### Excluir regra de merchandising
 
-Você pode deletar uma regra de merchandising clicando no botão lixeira <i class="fa-solid fa-trash-can"></i>.
+Você pode deletar uma regra de merchandising clicando no menu <i class="fas fa-ellipsis-v"></i> na linha da regra der merchandising e, em seguida, no botão <i class="fas fa-trash"></i> `Excluir`.
 
diff --git a/docs/tracks/pt/netshoes-marketplace.md b/docs/tracks/pt/netshoes-marketplace.md
index f98a66016..f9b290425 100644
--- a/docs/tracks/pt/netshoes-marketplace.md
+++ b/docs/tracks/pt/netshoes-marketplace.md
@@ -16,10 +16,10 @@ trackSlugPT: configurar-integracao-da-netshoes
 
 A [Netshoes](https://www.netshoes.com.br/) é o maior e-commerce de lifestyle esportivo da América Latina com a estrutura já consolidada de uma das 100 marcas de maior prestígio do Brasil, com 54 milhões de visitantes únicos por mês.
 
-<div><a href="https://www.netshoes.com.br/" target="_blank"><img src="https:https://images.ctfassets.net/alneenqid6w5/5vFWUEsP9R4MCsP7bcdD6Q/4baeea7382538fadc5de05acd62fce44/image2.png" alt="Netshoes" style="margin-left: auto; margin-right: auto; display: block;"></a></div>
+<div><a href="https://www.netshoes.com.br/" target="_blank"><img src="https://images.ctfassets.net/alneenqid6w5/5vFWUEsP9R4MCsP7bcdD6Q/4baeea7382538fadc5de05acd62fce44/image2.png" alt="Netshoes" style="margin-left: auto; margin-right: auto; display: block;"></a></div>
 
 Lojas que operam no Brasil podem usar a integração nativa com o Marketplace da Netshoes para expor e vender produtos de categorias como Calçados, Roupas, Acessórios, Equipamentos, Suplementos, Beleza e Eletrônicos. 
 
-![Netshoes Marketplace - Passo a Passo](https://images.ctfassets.net/alneenqid6w5/4l5uEyMSlfB55VHEmbm1sD/0bb6d4d15b6b7f586de32c899e208e2e/Screen_Shot_2020-06-04_at_23.24.51.png)
+![Netshoes Marketplace - Passo a Passo](//images.ctfassets.net/alneenqid6w5/4l5uEyMSlfB55VHEmbm1sD/0bb6d4d15b6b7f586de32c899e208e2e/Screen_Shot_2020-06-04_at_23.24.51.png)
 
 Antes de começar, é importante que você cadastre sua loja no [Netshoes Marketplace](https://www.netshoes.com.br/marketplace), aguarde a aprovação e prepare os documentos solicitados para preparação do seu contrato. Uma vez cadastrado, você poderá seguir os passos deste tutorial para montar seu catálogo e começar a vender.
diff --git a/docs/tracks/pt/next-steps.md b/docs/tracks/pt/next-steps.md
new file mode 100644
index 000000000..77a9306cf
--- /dev/null
+++ b/docs/tracks/pt/next-steps.md
@@ -0,0 +1,28 @@
+---
+title: 'Próximos passos'
+id: 7bORBaAr4rIG3JgRi68jIK
+status: PUBLISHED
+createdAt: 2024-02-07T16:51:41.686Z
+updatedAt: 2024-04-03T12:10:02.808Z
+publishedAt: 2024-04-03T12:10:02.808Z
+firstPublishedAt: 2024-02-22T13:58:08.369Z
+contentType: trackArticle
+productTeam: Others
+slug: proximos-passos
+locale: pt
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugPT: proximos-passos-apos-o-go-live
+---
+
+Agora que a loja está configurada no ambiente VTEX e realizou o [go-live](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), é o momento de conhecer as funcionalidades e [soluções adicionais](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) disponíveis que auxiliam no aumento da performance de vendas e expansão das operações, contribuindo para o desenvolvimento contínuo do negócio.
+
+<div class="alert alert-warning">
+  <p>Através do <a href="https://partnerportal.vtex.com/">VTEX Partner Portal</a>, é possível contratar <a href="https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros</a> para auxiliar no desenvolvimento da loja e gestão das soluções apresentadas neste artigo. Para acessar o portal, o usuário precisa ter <a href="https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz">acesso ao Admin VTEX</a> de uma loja.</p>
+</div>
+
+## Lançamentos na VTEX
+
+Nos nossos portais de documentação, é possível conhecer as últimas novidades e atualizações das soluções da VTEX:
+
+- **Help Center:** [novidades](https://help.vtex.com/pt/announcements) voltadas para o público operacional da loja.
+- **Developer Portal:** [release notes](https://developers.vtex.com/updates/release-notes) direcionados para os desenvolvedores do ambiente VTEX.
diff --git a/docs/tracks/pt/opening-tickets.md b/docs/tracks/pt/opening-tickets.md
new file mode 100644
index 000000000..5255027f6
--- /dev/null
+++ b/docs/tracks/pt/opening-tickets.md
@@ -0,0 +1,35 @@
+---
+title: 'Abertura de chamados'
+id: 6EboD7Y1BOLlWdT8JM15EE
+status: PUBLISHED
+createdAt: 2024-02-20T21:30:49.633Z
+updatedAt: 2024-02-22T14:09:13.418Z
+publishedAt: 2024-02-22T14:09:13.418Z
+firstPublishedAt: 2024-02-22T14:09:13.418Z
+contentType: trackArticle
+productTeam: Others
+slug: abertura-de-chamados
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+O acesso a uma conta VTEX possibilita acessar o [painel de suporte](https://support.vtex.com/hc/pt-br/requests), pelo qual solicitações abertas podem ser acompanhadas. A abertura de um chamado pode ser feita de três formas:
+
+- Acessando a [página de suporte](https://support.vtex.com/hc/pt-br/requests).
+- Acessando qualquer página do [Help Center](https://help.vtex.com/) e clicando em `Suporte`, no topo, ou em `Entrar em contato` no canto inferior da página.
+- Acessando o Admin VTEX, clicando no ícone interrogação `?` de **Central de Informações** e escolhendo a opção **Fale com nossos especialistas**.
+
+![Support imagem 1 - PT](//images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/8b56af5455d0c5ce1879a98aaa6b6768/support_imagem1_PT.gif)
+
+<div class = "alert alert-info">
+Para obter mais informações sobre como abrir um chamado e sobre tipos de chamado, basta acessar o artigo <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex">Abrir chamados para o suporte VTEX</a>.
+</div>
+
+## Tipos de suporte
+
+Durante a abertura de chamado, é preciso selecionar o tipo de suporte, que podem:
+
+- [Suporte técnico](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T): problemas ou perguntas técnicas em relação à plataforma ou a produtos VTEX como [Produtos Add-on](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+- [Suporte financeiro](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl): contrato ou questões financeiras relativas à loja e à VTEX.
+- [Suporte comercial](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ): contratação de [política comercial](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#contratar-politica-comercial-adicional) adicional, de [ambiente adicional](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ#contratar-politica-comercial-adicional#contratar-novo-ambiente), conta franquia ou alteração de [usuário titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy).
diff --git a/docs/tracks/pt/order-delivery.md b/docs/tracks/pt/order-delivery.md
index fa0ec4adf..dbef57750 100644
--- a/docs/tracks/pt/order-delivery.md
+++ b/docs/tracks/pt/order-delivery.md
@@ -23,7 +23,7 @@ Veja dois exemplos desse cenário:
 
 Nesse caso, é comum que os itens partam do estoque de um Centro de Distribuição, conforme ilustrado abaixo.
 
-![PT Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
+![PT Conceitos Logística](//images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
 
 Outra possibilidade de entrega que pode otimizar a operação e reduzir custos é implementar a estratégia [Ship From Store](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl), para que os itens também possam ser enviados a partir do estoque das lojas físicas.
 
diff --git a/docs/tracks/pt/order-flow.md b/docs/tracks/pt/order-flow.md
index f4f12b8b7..391579689 100644
--- a/docs/tracks/pt/order-flow.md
+++ b/docs/tracks/pt/order-flow.md
@@ -3,8 +3,8 @@ title: 'Fluxo do pedido'
 id: 4811ExCe3WrEiRMV3sy9n8
 status: PUBLISHED
 createdAt: 2019-11-14T13:46:22.682Z
-updatedAt: 2022-08-08T22:25:52.457Z
-publishedAt: 2022-08-08T22:25:52.457Z
+updatedAt: 2023-10-24T15:32:07.852Z
+publishedAt: 2023-10-24T15:32:07.852Z
 firstPublishedAt: 2019-11-14T15:38:27.680Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -14,13 +14,13 @@ trackId: 2xkTisx4SXOWXQel8Jg8sa
 trackSlugPT: pedidos
 ---
 
-O __fluxo do pedido__ é o caminho percorrido por um pedido na plataforma VTEX, desde o momento em que o cliente clica no botão de Finalizar Compra até o momento em que o pedido é faturado ou cancelado.
+O [fluxo do pedido](https://help.vtex.com/pt/tutorial/order-flow-and-status--tutorials_196) é o caminho percorrido por um pedido na plataforma VTEX, desde o momento em que o cliente clica no botão de Finalizar Compra até o momento em que o pedido é faturado ou cancelado.
 
 Alterações no pedido - sejam elas causadas pelo cliente, pela loja ou por sistemas externos - geram mudanças no __status do pedido__. E com, isso, o pedido se movimenta dentro do fluxo.
 
 ## Marketplaces e Sellers
 
-Os conceitos de Marketplace e Seller são fundamentais para o entendimento do fluxo de um pedido na VTEX. Vamos entender por quê:
+Os conceitos de [Marketplace e Seller](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) são fundamentais para o entendimento do fluxo de um pedido na VTEX. Vamos entender por quê:
 
 - __Marketplace__ é o ambiente onde é realizado o fechamento do pedido, ou seja, onde o cliente realiza o processo de checkout. 
 - __Seller__ é o dono do SKU. É, portanto, o responsável pelo fulfilment - ou seja, por fazer a entrega do produto ao cliente. 
@@ -33,7 +33,7 @@ Toda loja que vende produtos em seu próprio ambiente e realiza suas próprias e
 
 ## Fluxo do pedido no Marketplace
 
-![Screen Shot Fluxo de Marketplace](https://images.ctfassets.net/alneenqid6w5/51d58fXMpuxCTqFCyLkdaV/21d945a4e3d519e1500a8b73f7c24c02/Screen_Shot_Fluxo_de_Marketplace.png)
+![Screen Shot Fluxo de Marketplace](//images.ctfassets.net/alneenqid6w5/51d58fXMpuxCTqFCyLkdaV/21d945a4e3d519e1500a8b73f7c24c02/Screen_Shot_Fluxo_de_Marketplace.png)
 
 Ocorre quando a loja atua apenas como Marketplace no pedido. Ou seja, quando a loja vende produtos de outra loja - seu Seller.
 
@@ -47,7 +47,7 @@ Então, o despacho é autorizado e logo em seguida entra-se no status `Carência
 
 ## Fluxo do pedido no Seller
 
-![screenshoot fluxo seller PT](https://images.ctfassets.net/alneenqid6w5/19xYHIDMJf3wClpHAnTwuf/8adf145a324fdbc36db70785f55675c0/screenshoot_fluxo_seller_PT.JPG)
+![screenshoot fluxo seller PT](//images.ctfassets.net/alneenqid6w5/19xYHIDMJf3wClpHAnTwuf/8adf145a324fdbc36db70785f55675c0/screenshoot_fluxo_seller_PT.JPG)
 
 Ocorre quando a loja atua como Seller. Ou seja, quando ela é a dona do produto.
 
@@ -61,7 +61,7 @@ O próximo status é então o de `Preparando entrega`, quando o Seller prepara a
 
 ## Fluxo completo do pedido
 
-![Screen Shot Fluxo completo](https://images.ctfassets.net/alneenqid6w5/7A1IWqoCQw4INm34u6lOWF/f21882fb0c337fbaf2ebb462ebb197f7/Screen_Shot_Fluxo_completo.png)
+![Screen Shot Fluxo completo](//images.ctfassets.net/alneenqid6w5/7A1IWqoCQw4INm34u6lOWF/f21882fb0c337fbaf2ebb462ebb197f7/Screen_Shot_Fluxo_completo.png)
 
 Ocorre quando a loja é ao mesmo tempo Marketplace e Seller. Ou seja, é quando o pedido foi fechado na loja e a própria loja é a dona do produto, sendo responsável pelo fulfillment.
 
diff --git a/docs/tracks/pt/other-vtex-module-settings.md b/docs/tracks/pt/other-vtex-module-settings.md
new file mode 100644
index 000000000..61490fa10
--- /dev/null
+++ b/docs/tracks/pt/other-vtex-module-settings.md
@@ -0,0 +1,102 @@
+---
+title: 'Outras configurações de módulos VTEX'
+id: V1fs7IkfYMfn91ZVHTLu4
+status: PUBLISHED
+createdAt: 2024-02-20T20:25:49.450Z
+updatedAt: 2024-07-30T16:23:50.641Z
+publishedAt: 2024-07-30T16:23:50.641Z
+firstPublishedAt: 2024-02-22T14:09:20.283Z
+contentType: trackArticle
+productTeam: Others
+slug: outras-configuracoes-de-modulos-vtex
+locale: pt
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugPT: proximos-passos-apos-o-go-live
+---
+
+Na **Trilha geral da loja VTEX**, os artigos [Módulos VTEX I](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) e [Módulos VTEX II](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ) abordam as principais configurações de cada assunto. O artigo atual apresenta outras configurações de módulos que não são obrigatórias para o [go-live](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH).
+
+## Promoções
+
+Feitas as configurações obrigatórias de [Promoções](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promocoes), também é importante conhecer mais sobre [cluster de clientes](#cluster-de-clientes), [concorrência de promoções](#concorrencia-de-promocoes) e [promoções para marketplace](#promocoes-para-marketplace), conforme apresentado a seguir.
+
+### Cluster de clientes
+
+Para disponibilizar vantagens exclusivas de compra para um grupo determinado de pessoas ou empresas, é possível [criar promoções personalizadas](https://help.vtex.com/pt/tutorial/criando-promocao-para-um-cluster-de-clientes--tutorials_342) para um cluster de clientes cadastrados na loja. Neste contexto, as informações da promoção serão exibidas no carrinho de compras somente após os clientes selecionados realizarem o login no site. 
+
+### Concorrência de promoções
+
+Quando a loja possui promoções ativas cadastradas, com características similares e que possam ser aplicadas ao mesmo tempo em um produto, temos um cenário de concorrência de promoções. Nesta situação, é necessário entender em qual ordem de prioridade as promoções serão aplicadas no produto, de modo a garantir que a estratégia de venda está sendo utilizada de forma correta. 
+
+Mais informações em [Como funciona a concorrência de promoções](https://help.vtex.com/pt/tutorial/como-funciona-a-concorrencia-de-promocoes--tutorials_2270).
+
+### Promoções para marketplace
+
+Lojas operando como marketplace VTEX podem configurar apenas [promoções regulares](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) para seus produtos, como por exemplo:
+
+- Frete grátis
+- Frete percentual
+- Preço percentual
+- Tabela de preços
+
+Mais informações em [Configurar promoção para marketplace](https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406).
+
+## Logística
+
+Feitas as configurações obrigatórias de [Logística](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica), as contas VTEX que possuem a arquitetura [multiloja ou multidomínio](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#multiloja) tem a possibilidade de iniciar uma estratégia de vendas para outros países, tornando-se uma [loja internacional (cross-border)](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs). Dentre as principais vantagens desse tipo de operação, podemos destacar:
+
+- **Melhoria da capacidade logística total:** o acúmulo de experiência adquirido em processos logísticos complexos (importação e exportação) permite que toda a cadeia logística (nacional e internacional) possa ser gerenciada de forma mais eficiente.
+- **Expansão do negócio:** novos públicos são atingidos, aumentando o potencial de vendas das lojas.
+- **Vantagens fiscais:** incentivos fiscais internacionais, como isenção de impostos, podem ser oferecidos, diminuindo o custo total de venda do produto.
+- **Internacionalização da marca:** consolidação da imagem da empresa em diversos mercados, contribuindo para o aumento da confiança do consumidor e consequente aumento de vendas a nível nacional e internacional.
+
+Operações cross-border devem ser planejadas levando em consideração os seguintes aspectos: 
+
+- **Tipo de exportação:** pode ser de dois tipos:
+    - **Direta:** a empresa é a única responsável pelas atividades de distribuição e entrega dos produtos ao clientes.
+    - **Indireta:** os produtos são adquiridos por terceiros (parceiros de negócios ou intermediários localizados no país de destino), assumindo a total responsabilidade pelo gerenciamento da operação.
+- **Aceitação de produtos:** verificar estratégias de venda e preferências do público no mercado onde deseja atuar.
+- **Precificação inteligente:** definir estratégia de preço baseado nos custos locais (transporte, taxas, impostos).
+- **Parcerias:** estabelecer parcerias com transportadoras e fornecedores locais.
+- **Diferenciais competitivos:** definir como o negócio poderá oferecer benefícios aos clientes do novo mercado em relação aos atuais concorrentes.
+
+Para mais informações sobre como iniciar uma operação cross-border, é necessário contatar o responsável CX da conta VTEX ou o [Suporte VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8).
+
+## Pedidos
+
+Feitas as configurações obrigatórias de [Pedidos](https://help.vtex.com/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos), a loja pode expandir suas vendas disponibilizando [assinaturas](#assinaturas) de pedidos recorrentes e otimizar o gerenciamento de pedidos no Admin VTEX usando o [VTEX DO](#vtex-do).
+
+### Assinaturas
+
+Para permitir que clientes realizem compras recorrentes de seus produtos preferidos, de forma automática e indicando a frequência desejada, é possível configurar um agendamento de recompra no [sistema de Assinaturas](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453) da plataforma.
+
+### VTEX DO
+
+O [VTEX DO](https://help.vtex.com/pt/tutorial/vtex-do-interface--7KMbRL4OslN8DTX9oiuCiu) é o sistema de gerenciamento de tarefas relacionadas ao processamento de pedidos na loja. Por meio dele, tarefas criadas de forma automática pelo Admin VTEX podem ser executadas manualmente pelos operadores da loja. As seguintes funcionalidades estão disponíveis no VTEX DO:
+
+- Busca e filtragem por status (abertas, não atribuídas) ou por assunto (catálogo, comercial, infraestrutura).
+- Acesso a detalhes e informações para conclusão de cada tarefa.
+- Atribuição de [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) responsável pela tarefa.
+
+![vtex-do-pt](//images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/61ec58213dff43bd94d98b757087249d/next_steps_image12_PT.JPG)
+
+### VTEX Social Selling
+
+O [VTEX Social Selling](https://help.vtex.com/pt/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg) proporciona a possibilidade de vendedores selecionarem produtos e compartilharem com os clientes por meio de canais de comunicação como WhatsApp, Facebook Messenger e email. Esta funcionalidade pode ser utilizada tanto na loja virtual quanto em operações de lojas físicas ([VTEX Sales App](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm#vtex-sales-app)).
+
+## B2B Suite
+O [B2B Suite](https://help.vtex.com/pt/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3) é uma coleção de aplicativos [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) que permite às lojas gerenciarem organizações, permissões de acesso e configurações de checkout para relações comerciais B2B, entre outras funções. Esses recursos são importantes para simplificar o fluxo de compra, reduzir custos e fornecer uma experiência de compra personalizada.
+
+### Conjunto de Aplicativos do B2B Suite
+Os aplicativos essenciais do B2B Suite impulsionam as operações de negócios B2B. A seguir, apresentamos os principais aplicativos:
+
+- **Permissões da Loja:** gerencia as permissões de acesso para diferentes usuários e grupos dentro da loja.
+- **Interface de Permissões da Loja:** permite que os usuários do Admin VTEX gerenciem funções B2B e permissões de aplicativos associadas por meio do próprio Admin.
+- **Organizações B2B:** agrupa usuários B2B em organizações às quais é possível atribuir métodos de pagamento específicos, tabelas de preços e coleções de produtos.
+- **Cotações e Carrinhos B2B:** permite a criação de cotações e o gerenciamento de carrinhos de compras para empresas.
+- **Configurações de Checkout B2B:** configura métodos de pagamento específicos, endereços pré-preenchidos, número de ordem de compra e cotações de pedido.
+- **Histórico de Pedidos B2B:** permite que usuários B2B visualizem todos os pedidos anteriores feitos por sua organização ou centro de custos.
+- **B2B Clientes:** gerencia as informações e as relações com os clientes B2B.
+
+Para mais informações sobre os aplicativos, acesse [Conjunto de aplicativos do B2B Suite](https://help.vtex.com/pt/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#conjunto-de-aplicativos-do-b2b-suite).
+
diff --git a/docs/tracks/pt/overview-intelligent-search.md b/docs/tracks/pt/overview-intelligent-search.md
index d5afb4f8d..3c6368a7f 100644
--- a/docs/tracks/pt/overview-intelligent-search.md
+++ b/docs/tracks/pt/overview-intelligent-search.md
@@ -1,10 +1,10 @@
 ---
 title: 'Intelligent Search'
 id: 3qgT47zY08biLP3d5os3DG
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-03-05T14:47:05.068Z
-updatedAt: 2023-04-13T22:52:19.619Z
-publishedAt: 2023-04-13T22:52:19.619Z
+updatedAt: 2023-08-22T17:03:02.484Z
+publishedAt: 2023-08-22T17:01:21.074Z
 firstPublishedAt: 2020-03-05T19:53:38.701Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,6 +14,10 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
+<div class="alert alert-info" role="alert"><p>
+Este app só está disponível para lojas desenvolvidas usando VTEX IO. Antes de prosseguir, é preciso instalar e configurar o Intelligent Search na sua loja.</p>
+</div>
+
 O Intelligent Search é uma plataforma de busca inteligente para o comércio digital. Ele é uma solução de busca nativa da plataforma VTEX, auxiliando o cliente em toda sua jornada de compra, independente do canal (website, mobile app, conversational, etc). 
 
 De forma simples e intuitiva, ele apresenta resultados relevantes com base no catálogo desde a primeira interação do usuário com a loja, seja através da barra de busca, navegando pelas categorias, ou mesmo através das vitrines de produtos.
@@ -22,9 +26,7 @@ A ferramenta ainda conta com funcionalidades como o autocomplete, exibindo suges
 
 Além disso, o Intelligent Search utiliza dados históricos de cliques e pedidos para melhorar a busca dinamicamente, bem como possui a capacidade de lidar com erros ortográficos, plural/singular, gênero (radical). Por fim, conta com configurações que possibilitam tanto melhorar a experiência do cliente, quanto atender as necessidades de negócio do comerciante.
 
-<div class="alert alert-info" role="alert"><p>
-Esta app só está disponível para lojas desenvolvidas usando VTEX IO. Antes de prosseguir, é preciso instalar e configurar o Intelligent Search na sua loja.</p>
-</div>
+O VTEX Intelligent Search suporta os seguintes idiomas: Alemão, Árabe, Armênio, Basco, Bengali, Búlgaro, Catalão, Chinês, Coreano, Dinamarquês, Espanhol, Estoniano, Finlandês, Francês, Galego, Grego, Hindi, Holandês, Húngaro, Indonésio, Inglês, Irlandês, Italiano, Japonês, Letão, Lituano, Norueguês, Persa, Polonês, Português, Português do Brasil, Romeno, Russo, Sorani, Sueco, Tailandês, Tcheco, Turco e Urdu.
 
 Nos artigos mencionados abaixo, você encontrará uma visão geral sobre cada funcionalidade do Intelligent Search.
 
@@ -36,4 +38,4 @@ Nos artigos mencionados abaixo, você encontrará uma visão geral sobre cada fu
 - **Relevância**: Relevância é uma funcionalidade que define a ordem dos produtos no resultado de busca. 
 - **Redirecionamentos**: Redirecionamentos é uma funcionalidade que direciona o cliente para qualquer outra página, seja interna, seja externa ao seu site. Esse redirecionamento é feito na área de busca, utilizando termos ou filtros selecionados. Dentro do Admin, o redirecionamento é chamado de Redirecionamento.
 - **Sinônimos**: permite o cadastro de sinônimos - palavras de mesmo sentido - a um termo de busca específico, aumentando a chance de uma busca com sucesso.
-- **Relatórios**: Organiza os dados relacionados às pesquisas realizadas na loja e possibilita exportar esses dados em um arquivo CSV.
+- **Analytics**: Organiza os dados relacionados às pesquisas realizadas na loja e possibilita exportar esses dados em um arquivo CSV.
diff --git a/docs/tracks/pt/partial-invoices.md b/docs/tracks/pt/partial-invoices.md
index d9c11e34d..bd8b533ed 100644
--- a/docs/tracks/pt/partial-invoices.md
+++ b/docs/tracks/pt/partial-invoices.md
@@ -3,8 +3,8 @@ title: 'Faturas parciais'
 id: q9GPspTb9cHlMeAZfdEUe
 status: PUBLISHED
 createdAt: 2022-06-20T20:13:46.342Z
-updatedAt: 2023-03-31T22:36:12.880Z
-publishedAt: 2023-03-31T22:36:12.880Z
+updatedAt: 2024-04-01T17:51:08.329Z
+publishedAt: 2024-04-01T17:51:08.329Z
 firstPublishedAt: 2022-06-20T20:21:34.641Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -29,8 +29,9 @@ As faturas parciais causam as seguintes ações no OMS, e demais sistemas da VTE
 
 * As faturas parciais inseridas nos pedidos também disparam liquidações parciais na transação. O valor total do pedido será atualizado após a inserção da nota fiscal, e corresponde ao que é liquidado pelo gateway de pagamentos da VTEX.   
 * É feito o reembolso automático ao consumidor, caso haja estorno de valores.  
-* Se eventualmente o lojista identificar que um item precisa ser removido juntamente com seu valor, a alteração do pedido, com o valor descontado, poderá ser feita - dado que as notas fiscais anteriores só liquidam seus valores correspondentes e mantiveram o resto do valor liquidado em aberto.  
-* Como a fatura parcial só liquida o valor correspondente à fatura, é possível solicitar alterações de valores no pedido. Com a fatura parcial, a transação ainda fica em aberto, esperando o resto do valor ser liquidado ou cancelado - como é o caso de uma alteração do pedido com desconto de valor.   
+* Se eventualmente o lojista identificar que um item precisa ser removido juntamente com seu valor, a alteração do pedido com o valor descontado poderá ser feita, dado que as notas fiscais anteriores só liquidam seus valores correspondentes e mantiveram o resto do valor liquidado em aberto.  
+* Como a fatura parcial só liquida o valor correspondente à fatura, é possível solicitar alterações de valores no pedido. Com a fatura parcial, a transação ainda fica em aberto.
+* Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido faturados parcialmente. Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 * Valores maiores ou iguais ao total do pedido seguem o fluxo para faturado. Qualquer nota inserida além desses valores entrará como Nota Fiscal Avulsa que não receberá atualização de tracking.  
 
 <div class = "alert alert-info">
diff --git a/docs/tracks/pt/payment.md b/docs/tracks/pt/payment.md
index 028e312cf..e73683d23 100644
--- a/docs/tracks/pt/payment.md
+++ b/docs/tracks/pt/payment.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Na etapa de pagamento do VTEX Sales App, aparecerão as [opções de pagamento que foram configuradas](https://help.vtex.com/pt/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy) na sua loja.
 
-![instore-payment-pt](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/fd64b98d229c0079b017f9e926306b13/original_31f07de6-319b-454b-8c64-62dcc8ccc736_Screenshot_20220926-142455_instore.jpg)
+![instore-payment-pt](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/fd64b98d229c0079b017f9e926306b13/original_31f07de6-319b-454b-8c64-62dcc8ccc736_Screenshot_20220926-142455_instore.jpg)
 
 A barra superior da tela de pagamento exibe as opções a seguir:
 
@@ -45,7 +45,7 @@ Para configurar um método de pagamento, siga as instruções da track [VTEX Sal
 
 O cliente deve selecionar a opção **Dinheiro** e clicar em `Finalizar venda`. 
 
-![instore-dinheiro-pt](https://images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/1baf8b97937e9f9b627f0122598c382b/original_f0a5c2c8-72da-4961-b146-380416922fb4_Screenshot_20220926-142511_instore.jpg)
+![instore-dinheiro-pt](//images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/1baf8b97937e9f9b627f0122598c382b/original_f0a5c2c8-72da-4961-b146-380416922fb4_Screenshot_20220926-142511_instore.jpg)
 
 Após isso, o cliente deve realizar a transação com o vendedor. A aprovação da venda pode ser [manual ou automática](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), dependendo da configuração da loja.
 
@@ -53,21 +53,21 @@ Após isso, o cliente deve realizar a transação com o vendedor. A aprovação
 
 O cliente deve selecionar a opção **Pix** e clicar em `Finalizar venda`. 
 
-![instore-pix-pt](https://images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/caf7224236509a0d185a680af077cfb6/image.png)
+![instore-pix-pt](//images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/caf7224236509a0d185a680af077cfb6/image.png)
 
 Após finalizar a venda, será exibido o QR Code na tela do VTEX Sales App. O cliente deve escanear esse QR Code com o celular para realizar o pagamento. 
 
-![instore-pix2-pt](https://images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/cc329d7a9d6c46f61292fe5255a1cc0b/image.png)
+![instore-pix2-pt](//images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/cc329d7a9d6c46f61292fe5255a1cc0b/image.png)
 
 Depois que o cliente realizar o pagamento, a venda será processada e, por fim, confirmada na página do pedido, conforme a imagem abaixo.
 
-![instore-pix3-pt](https://images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/31173482d2636ba795335dd542e97818/image.png)
+![instore-pix3-pt](//images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/31173482d2636ba795335dd542e97818/image.png)
 
 ### Boleto bancário
 
 O cliente deve selecionar a opção **Boleto Bancário** e clicar em `Finalizar venda`. 
 
-![instore-boleto-pt](https://images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/ebcafe3b1d49b11780d1587e9ff2d2d6/Screenshot_20220926-142519_instore__1_.jpg)
+![instore-boleto-pt](//images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/ebcafe3b1d49b11780d1587e9ff2d2d6/Screenshot_20220926-142519_instore__1_.jpg)
 
 O boleto será enviado para o email do cliente. Uma vez que o pagamento do boleto for confirmado, a venda será confirmada. 
 
@@ -75,7 +75,7 @@ O boleto será enviado para o email do cliente. Uma vez que o pagamento do bolet
 
 O cliente deve selecionar a opção **Cartão de crédito**, selecionar a quantidade de parcelas da compra e clicar em `Finalizar venda`. 
 
-![instore-credito-pt](https://images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/21a3fa6635db72c129ba08e7f7ceb56f/Screenshot_20220926-143755_instore.jpg)
+![instore-credito-pt](//images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/21a3fa6635db72c129ba08e7f7ceb56f/Screenshot_20220926-143755_instore.jpg)
 
 O VTEX Sales App exibirá uma tela de espera enquanto o pagamento é realizado na máquina de cartão da loja. Uma vez que o pagamento é reconhecido pelo sistema, a venda será confirmada.
 
@@ -83,7 +83,7 @@ O VTEX Sales App exibirá uma tela de espera enquanto o pagamento é realizado n
 
 O cliente deve selecionar a opção **Cartão de débito** e clicar em `Finalizar venda`. 
 
-![instore-debito-pt](https://images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4ac0e0e71fe105df9c93d5d068d5cd98/Screenshot_20220926-142524_instore__1_.jpg)
+![instore-debito-pt](//images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4ac0e0e71fe105df9c93d5d068d5cd98/Screenshot_20220926-142524_instore__1_.jpg)
 
 O VTEX Sales App exibirá uma tela de espera enquanto o pagamento é realizado na máquina de cartão da loja. Uma vez que o pagamento é reconhecido pelo sistema, a venda será confirmada.
 
diff --git a/docs/tracks/pt/personal-data.md b/docs/tracks/pt/personal-data.md
new file mode 100644
index 000000000..6b3ce59c4
--- /dev/null
+++ b/docs/tracks/pt/personal-data.md
@@ -0,0 +1,47 @@
+---
+title: 'Dados pessoais'
+id: 65ZqZlNWcmFSOqZQxr8gha
+status: PUBLISHED
+createdAt: 2024-05-03T14:39:14.904Z
+updatedAt: 2024-05-03T21:13:09.925Z
+publishedAt: 2024-05-03T21:13:09.925Z
+firstPublishedAt: 2024-05-03T16:42:08.464Z
+contentType: trackArticle
+productTeam: Others
+slug: dados-pessoais
+locale: pt
+trackId: 65ZqZlNWcmFSOqZQxr8gha
+trackSlugPT: dados-e-privacidade
+---
+
+Um dado pessoal ou _Personally Identifiable Information_ (PII) é qualquer informação relativa a uma pessoa física, que seja capaz de identificá-la de maneira direta (como nome, CPF e e-mails pessoais) ou indireta (como endereços de IP, endereços físicos e [cookies](https://vtex.com/br-pt/privacy-and-agreements/vtex-platform-cookies-information/)).
+
+Dados pessoais sensíveis são informações relacionadas a etnia, crenças religiosas, opinião política, filiação sindical, saúde ou dados de vida sexual, genéticos ou biométricos. O uso indevido desses tipos de dados pode trazer graves prejuízos ou tratamento discriminatório ao titular.
+
+## Dados pessoais tratados pela VTEX
+
+A VTEX trata dados pessoais de compradores somente quando necessário, em conformidade com os requisitos de cada módulo da plataforma para realizar operações de ecommerce. Confira a seguir a lista de dados pessoais que podem ser tratados pela VTEX:
+
+* Nome
+* Email
+* Endereço IP
+* Informações de navegação ([cookies](https://vtex.com/br-pt/privacy-and-agreements/vtex-platform-cookies-information/))
+* Informações do carrinho
+* Informações e histórico do pedido
+* Endereço de entrega
+* Número de identidade (quando exigido pelo país em que a loja opera)
+* Histórico do cartão-presente
+* Carrinho não utilizado
+* Conversas do [Conversation Tracker](https://help.vtex.com/pt/tutorial/conversation-tracker--tutorials_195)
+* Senhas de sessões (criptografadas)
+* Tokens gerados
+
+A lista de dados acima está descrita no [Data Processing Addendum (DPA)](#data-processing-addendum-dpa).
+
+A VTEX não vende, monetiza, enriquece ou transfere quaisquer dados pessoais de compradores para outras empresas.
+
+## Minimização de dados
+
+O princípio da minimização de dados refere-se à prática de coletar, processar e armazenar apenas as informações estritamente necessárias para alcançar um propósito específico. Esse princípio possibilita limitar a quantidade de dados pessoais que coletam e mantêm, reduzindo assim o risco associado ao processamento excessivo de informações.
+
+Nesse sentido, a VTEX coleta apenas a quantidade mínima de dados necessária para processar os pedidos recebidos, ou seja, somente os dados pessoais estritamente necessários às operações de ecommerce.
diff --git a/docs/tracks/pt/planning-the-go-live.md b/docs/tracks/pt/planning-the-go-live.md
new file mode 100644
index 000000000..93b72d860
--- /dev/null
+++ b/docs/tracks/pt/planning-the-go-live.md
@@ -0,0 +1,195 @@
+---
+title: 'Planejamento do go-live'
+id: 6xYnNxDHUcY6FyChgziCoH
+status: PUBLISHED
+createdAt: 2024-01-08T13:11:05.385Z
+updatedAt: 2024-06-27T00:28:49.687Z
+publishedAt: 2024-06-27T00:28:49.687Z
+firstPublishedAt: 2024-02-22T14:07:27.548Z
+contentType: trackArticle
+productTeam: Others
+slug: planejamento-do-go-live
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+Go-live é o momento a partir do qual a loja encontra-se disponível para que clientes a acessem e façam compras. Este artigo explica como planejar todas as etapas necessárias para o go-live de uma loja VTEX e está organizado nas seguintes etapas:
+
+1. [Preparação para o go-live](#1-preparacao-para-o-go-live)
+2. [Configurações da loja](#2-configuracoes-da-loja)
+3. [Configurações de domínio e conta](#3-configuracoes-de-dominio-e-conta)
+4. [Testes antes do go-live](#4-testes-antes-do-go-live)
+5. [Cadastro de domínio e solicitação de apontamento](#5-cadastro-de-dominio-e-solicitacao-de-apontamento)
+6. [Go-live](#6-go-live)
+7. [Ações após o go-live](#7-acoes-apos-o-go-live)
+
+## Antes de começar
+
+Para preparar uma loja para o go-live, é importante já ter definido a equipe ou [agência parceira](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao) responsável pela implementação, ter escolhido os [tipos de conta VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-conta-na-vtex) de acordo com o tipo de operação e ter planejado a arquitetura da loja. Mais informações sobre essas etapas podem ser encontradas no artigo [Contas e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl).
+
+## 1. Preparação para o go-live
+
+O processo para realizar o go-live de uma loja, incluindo as configurações e testes necessários, pode variar de acordo com o grau de complexidade operacional da loja. Por esse motivo, recomendamos planejar todas as etapas necessárias para o go-live com no mínimo 15 dias de antecedência.
+
+A imagem a seguir apresenta as etapas de planejamento envolvidas no go-live de uma loja VTEX:
+
+![go-live-pt](//images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/a758f107911697856c856d70192d2912/go-live-pt.png)
+
+### Definir MVP
+
+O primeiro passo consiste em determinar o que é fundamental para o _Minimum Viable Product_ (MVP), incluindo as funcionalidades, páginas e informações necessárias para o lançamento oficial da loja.
+
+É importante listar tudo que será preciso implementar antes do go-live. Recursos desejáveis, mas não essenciais, devem ser listados separadamente e implementados como mudanças incrementais após o lançamento.
+
+### Planejar teste de penetração (opcional)
+
+Lojistas que desejam realizar um teste de penetração antes do go-live precisam solicitar autorização prévia, seguindo as orientações do guia [Testes de penetração e avisos de vulnerabilidade](https://help.vtex.com/pt/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb).
+
+É obrigatório enviar o relatório com os resultados para o [Suporte VTEX](https://help.vtex.com/pt/support) pelo menos **45 dias** antes da data planejada para o go-live. Neste período, a VTEX vai analisar o resultado e endereçar qualquer vulnerabilidade identificada no processo.
+
+Nesse caso, portanto, todo o processo de planejamento precisa iniciar no mínimo 45 dias antes, mais o tempo decorrido entre a solicitação e a realização do teste.
+
+### Definir cronograma
+
+Para organizar as equipes envolvidas e realizar o go-live na data desejada, é importante criar um _roadmap_, ou seja, um documento com o roteiro de ações necessárias para o go-live, indicando os responsáveis por cada etapa e os prazos acordados. A imagem a seguir mostra um exemplo de cronograma:
+
+![golive 2 PT](//images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/a15338a9461674d2069c56d02388f742/golive_2_PT.png)
+
+Recomendamos planejar reuniões periódicas com as [equipes de implementação](warm-up-heading-parceiros-de-implementacao) para manter um alinhamento frequente e, se necessário, criar uma _war room_ para resolver assuntos pendentes na semana que antecede o go-live.
+
+### Planejar soft launch
+
+Além de testes durante o desenvolvimento do projeto, recomendamos incluir um _soft launch_ no cronograma, ou seja, um lançamento restrito a um público ou mercado antes do lançamento oficial. Essa etapa pode contribuir para o refinamento e correção de detalhes não observados ao longo do projeto de implementação.
+
+Após a data do lançamento oficial, com a loja operando plenamente, os desenvolvedores podem continuar iterando o MVP e adicionando melhorias sem interromper as vendas.
+
+## 2. Configurações da loja
+
+Antes de realizar o go-live, é essencial garantir todas as configurações essenciais para o bom funcionamento da loja. Para isso, recomendamos verificar a [Checklist de configuração de loja](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx). É preciso confirmar em cada item se as configurações foram concluídas de acordo com as características de operação da loja.
+
+<div class="alert alert-warning">
+  <p>A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. É de responsabilidade da <a href="https://help.vtex.com/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">equipe de implementação</a> de cada loja definir quais funcionalidades e configurações devem ser aplicadas de maneira a produzir a experiência de compra desejada para os clientes. Recomendamos verificar todos os aspectos operacionais da loja e acrescentá-los à lista, caso não estejam presentes.</p>
+</div>
+
+## 3. Configurações de domínio e conta
+
+Assim que as configurações internas da lojas forem concluídas, será preciso fazer algumas configurações referentes ao domínio e à conta VTEX. Esses ajustes não dependem da data prevista para o go-live, mas precisam ser realizados antes da etapa de testes.
+
+1. [Conferir domínio nos CDNs](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#conferir-dominio-nos-cdns): garantir que o domínio não está registrado previamente na [Cloudfront](https://aws.amazon.com/pt/cloudfront/) ou na [Azion](https://www.azion.com/pt-br/).
+2. [Configurar registro CAA](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#configurar-registro-caa): indicar que a autoridade certificadora (CA) **Let’s Encrypt** está autorizada a gerar e renovar certificados que atestam a identidade do domínio. Passo necessário apenas se há registro de CAA no servidor DNS.
+3. [Colocar conta em produção](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#colocar-conta-em-producao): ativar a conta VTEX em produção. Mesmo após essa ativação, a loja permanece indisponível para acesso de clientes externos. A visualização e compra de produtos na loja só poderão ser efetuadas após a conclusão do go-live, conforme os passos descritos nas próximas seções deste artigo.
+
+<div class="alert alert-warning">
+  <p>A partir do momento em que a conta entra em produção, todos os pedidos serão cobrados automaticamente e o <a href="https://help.vtex.com/pt/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322#valores-da-receita-aprovada">Take Rate</a> será aplicado de acordo com o plano contratado com a VTEX. Isso inclui pedidos realizados no domínio <code>{nomedaloja}.myvtex.com</code>, mesmo que tenham sido realizados para testes.</p>
+</div>
+
+Para obter mais informações, basta consultar o artigo [Configurações](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX), parte da trilha detalhada sobre [Go-live](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/1iP90RcJvlrfQhnlxM54wo).
+
+## 4. Testes antes do go-live
+
+Recomendamos realizar testes antes do go-live para observar o comportamento da loja e evitar erros ou pendências no momento do lançamento oficial. Nas seções seguintes, explicamos os dois tipos mais comuns de testes: [Quality Assurance (QA)](#quality-assurance-qa) e [User Acceptance Testing (UAT)](#user-acceptance-testing-uat).
+
+Na VTEX, é possível criar ambientes separados para esses testes. Nesse caso, é preciso replicar as configurações do ambiente principal que serão testadas. Por exemplo, se o objetivo é testar o funcionamento de uma promoção, é preciso fazer todas as configurações necessárias para simular um cenário em que ela seria aplicada, incluindo produtos, preços, logística, checkout, meios de pagamento, entre outros.
+
+Para planejar a fase de testes, vale entrar em contato com o [nosso suporte](https://help.vtex.com/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy), que é por onde é feita a [contratação de um ambiente de teste](https://help.vtex.com/pt/tutorial/contratar-ambiente-de-testes--2nmZAHlfQoGsCWmEWGIoGy).
+
+<div class="alert alert-info">
+  <p>Se a loja for <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#ambiente-de-desenvolvimento">construída com VTEX IO</a>, é possível realizar testes A/B entre workspaces, ou seja, comparar a performance de ambientes de desenvolvimento de frente de loja. Para mais detalhes, basta acessar o guia para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing">Running A/B tests</a>.</p>
+</div>
+
+### _Quality Assurance_ (QA)
+
+A fase de testes de QA é a garantia de qualidade, ou seja, o processo de verificação e validação de todos os aspectos da loja e de suas funcionalidades antes de serem disponibilizadas ao público em geral. Isso envolve testar minuciosamente todos os elementos, desde a navegabilidade e desempenho do site até diversos cenários de fluxo de compra, processamento de pagamentos e integrações de sistemas.
+
+O objetivo é identificar e corrigir quaisquer problemas, erros ou falhas para garantir que a loja esteja pronta e de acordo com o escopo previsto para o MVP no momento do lançamento. Nessa etapa, é importante documentar bugs e erros e planejar como corrigi-los antes da data do go-live.
+
+### _User Acceptance Testing_ (UAT)
+
+O UAT, ou Teste de Aceitação do Usuário (_User Acceptance Testing_), representa a fase final de testes em que usuários finais validam e verificam se a loja atende às expectativas e funcionalidades necessárias para o MVP. Geralmente, esse tipo de teste inclui a equipe da loja e, em alguns casos, um grupo selecionado de clientes.
+
+Durante o UAT, os responsáveis pelos testes exploram o site, realizam pedidos-teste e avaliam a experiência geral do usuário. Essa fase oferece mais uma oportunidade de relatar, documentar e corrigir qualquer problema ou comportamento indesejado na experiência antes do lançamento oficial, aumentando assim a probabilidade de sucesso após o go-live.
+
+## 5. Cadastro de domínio e solicitação de apontamento
+
+Após a conclusão dos testes e ajustes necessários, é preciso preparar a loja para o go-live. Em um período entre três e sete dias antes da data prevista para o lançamento oficial, é necessário realizar as seguintes ações:
+
+1. [Cadastrar domínio na VTEX](https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450): acessar as **Configurações da conta** no Admin VTEX para conectar o endereço à loja.
+
+   <div class="alert alert-warning">
+    <p>Após realizar o cadastro, existe um prazo de sete dias para concluir o go-live. Caso a loja não conclua os procedimentos necessários para go-live neste período, será preciso acessar o cadastro realizado e salvá-lo novamente.</p>
+   </div>
+
+2. **Solicitar apontamento interno:** abrir um ticket para o [Suporte VTEX](https://help.vtex.com/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy) para solicitar o apontamento interno de DNS. O tempo para a conclusão desta solicitação pode ser de até três dias úteis.
+
+    O tipo da solicitação encaminhada deve ser de acordo com a [tecnologia escolhida](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#escolhendo-a-tecnologia) para a frente de loja:
+
+  <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tecnologia</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Solicitação</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">Store Framework ou FastStore (VTEX IO)</td>
+      <td class="t-body pa5" style="min-width: 10rem;">Solicitar o <a href="https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#solicitar-apontamento-io" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">apontamento interno de DNS para VTEX IO</a> por meio de um ticket para o <a href="https://help.vtex.com/pt/support" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Suporte VTEX</a>.<br>Mais informações nos artigos:<ul><li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-go-live" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Going live with a new store</a> (Store Framework)</li><li><a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-migrating-storefront-from-legacy-to-io" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Migrating your storefront from Legacy CMS Portal to Store Framework</a></li><li><a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns" target="_blank" rel="noopener noreferrer" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Configuring external DNS for a custom domain</a> (FastStore)</li></ul></td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 10rem;">CMS Portal Legado</td>
+      <td class="t-body pa5" style="min-width: 10rem;">Se o acesso à loja é restrito por <a href="https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">política comercial</a> com regra condicional e sua frente de loja foi construída com <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">CMS Portal Legado</a>, é preciso solicitar um <a href="https://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#solicitar-apontamento-especial" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">apontamento interno especial</a>. Um exemplo comum são as lojas B2B, que restringem o acesso a empresas pré-aprovadas. A solicitação de apontamento especial é feita pelo <a href="https://help.vtex.com/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Suporte VTEX</a>, indicando a política comercial e a regra condicional configurada.</td>
+    </tr>
+  </tbody>
+  </table>
+
+Independente do tipo de solicitação a ser encaminhada, o ticket para o Suporte VTEX deve conter as seguintes informações:
+
+- Título informando a intenção de realizar o go-live.
+- Se a [tecnologia de frente de loja](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) foi desenvolvida em VTEX IO ou CMS Portal Legado.
+- URL a ser apontada.
+- Horário para o apontamento interno ocorrer, entre 9 e 17 BRT (UTC-3).
+- Informar se a loja tem regras condicionais de [políticas comerciais](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE).
+- Caso já exista um site no ar que esteja sendo migrado para a VTEX, informar se utiliza a CDN da Azion ou Cloudfront.
+
+<div class="alert alert-warning">
+ <p>Após receber a confirmação do apontamento interno, é necessário realizar o apontamento comum de DNS em até cinco dias. Caso contrário, o apontamento interno será excluído e uma nova solicitação será necessária.</p>
+</div>
+
+## 6. Go-live
+
+No momento do go-live, após a confirmação do apontamento interno realizado na etapa anterior, será preciso realizar o apontamento de DNS e notificar a VTEX:
+
+1. [Realizar apontamento de DNS](https://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dnshttps://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dns): na zona de DNS do domínio, criar uma entrada do tipo CNAME no subdomínio desejado para o destino ``{domínio}.cdn.vtex.com``. O ``{domínio}`` deve ser o mesmo cadastrado na VTEX.
+
+   <div class="alert alert-warning">
+    <p>A propagação do apontamento de DNS pode levar entre 24 a 48 horas para ser concluída, o que significa que o endereço configurado pode não estar acessível a todas as pessoas logo após a configuração.</p>
+   </div>
+
+2. [Notificar apontamento](https://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#notificar-apontamento): para que a loja fique disponível ao público em geral, é preciso notificar a plataforma VTEX que o apontamento foi realizado. Para isso, é necessário salvar novamente as **Configurações da conta** no Admin VTEX.
+
+   <div class="alert alert-info">
+    <p>Se a loja tiver sido construída com <a href="link-implement-frontend-faststore">FastStore</a>, também será necessário seguir os passos descritos no artigo <a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns">Configuring external DNS for a custom domain</a>.</p>
+   </div>
+
+Uma vez que as etapas acima forem concluídas, a loja estará disponível no domínio cadastrado para que clientes a acessem e realizem compras.
+
+## 7. Ações após o go-live
+
+Depois do lançamento oficial da loja, existem algumas ações importantes para garantir que os clientes tenham acesso ao endereço correto e acompanhar o desempenho das vendas e da navegação no site.
+
+### Configurar redirecionamentos
+
+Após o go-live, é possível acessar a loja no [domínio cadastrado](https://help.vtex.com/pt/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#cadastrar-dominio-na-vtex). Porém, pode ser preciso redirecionar endereços antigos ou um endereço sem o subdomínio `www` para garantir o acesso ao endereço da nova loja. Para isso, recomendamos seguir os tutoriais dos seguintes artigos:
+
+- [Redirecionamento de outros endereços](https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ)
+- [Configurar acesso sem www](https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278)
+
+### Monitorar performance da loja
+
+Recomendamos acompanhar o desempenho da loja após o lançamento a partir do menu de [Dashboards](https://help.vtex.com/pt/tutorial/visao-geral-dashboards--1yn2nZUoXtDO3teTEJsCNl) no Admin VTEX, que inclui as seguintes páginas:
+
+- [Visão Geral](https://help.vtex.com/pt/tutorial/store-overview--P8ahguoRs0U3PzmXg2wuQ): principais métricas que impactam a receita das lojas. Nesse painel, é possível acompanhar os principais indicadores da evolução das vendas através dos recursos de análise de tendências de pedidos, taxa de conversão e gráficos de funil de vendas.
+- [Performance de Vendas](https://help.vtex.com/pt/tutorial/sales-performance--3DMube0sEsK9vPcRYGas72): painel de controle para comércio unificado, que auxilia lojas a ampliarem seu negócio e tomarem decisões com mais precisão.
+
+Além das ferramentas disponíveis no Admin VTEX, é possível acompanhar a performance da loja pelo [Google Analytics](https://analytics.google.com/analytics/web/), caso tenha sido configurado anteriormente. Para obter mais informações, basta acessar o guia [Configurar Google Analytics 4 em loja VTEX](https://help.vtex.com/pt/tutorial/como-configurar-google-analytics-em-loja-vtex--G2P0rmSrEiqCcmUMyUUwG).
diff --git a/docs/tracks/pt/preco-base-definicao-de-conceito.md b/docs/tracks/pt/preco-base-definicao-de-conceito.md
index 47804b0ea..c850f30c1 100644
--- a/docs/tracks/pt/preco-base-definicao-de-conceito.md
+++ b/docs/tracks/pt/preco-base-definicao-de-conceito.md
@@ -18,7 +18,7 @@ trackSlugPT: precos-101
 
 Preço Base de um SKU é o valor calculado através da combinação entre o **Preço de Custo** e o **Markup**, a margem de lucro desejada com a venda do SKU. É o __preço de referência__ de um SKU para todas as tabelas de preço. 
 
-![base-price-pt](https://images.ctfassets.net/alneenqid6w5/5tamTR4dro1URUdIvMkp93/f5103d68e1230e853496b49a9211852e/base-price-pt.png)
+![base-price-pt](//images.ctfassets.net/alneenqid6w5/5tamTR4dro1URUdIvMkp93/f5103d68e1230e853496b49a9211852e/base-price-pt.png)
 
 Esse **preço base** pode ser combinado com uma **regra de preço** aplicada à tabela de preços. Caso não exista regra de preço cadastrada, o preço de venda em uma tabela será o próprio preço base.
 
diff --git a/docs/tracks/pt/preco-fixo-definicao-de-conceito.md b/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
index a60b9918d..f55ece39a 100644
--- a/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
@@ -73,7 +73,7 @@ Digamos que dois preços fixos sejam cadastrados para o mesmo SKU. Além disso,
 
 Por exemplo: o primeiro preço fixo é de __R$ 50,00__ e seu agendamento vai das __10h às 16h__. Já o segundo é de __R$ 25,00__, só que está programado das __12h às 20h do mesmo dia__. Neste caso, *entre 12h e 16h*, os dois preços fixos competem entre si. Desse modo, o valor de __R$ 25,00__ será o preço de venda do SKU neste horário em comum.
 
-![fixed price - example2](https://images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
+![fixed price - example2](//images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
 
 ### Concorrência pelo critério de Itens mínimos no carrinho
 
@@ -83,7 +83,7 @@ Imagine que cadastramos um preço fixo de R$ 200,00 para __dois ou mais itens no
 
 Qual seria o preço aplicado para 5 ou mais itens? O preço de venda será de R$ 100,00, visto que o sistema prioriza o menor valor.
 
-![fixed price - example1](https://images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
+![fixed price - example1](//images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
 
 ## Exemplos
 
diff --git a/docs/tracks/pt/prerequisites-for-using-instore.md b/docs/tracks/pt/prerequisites-for-using-instore.md
index c9a043e65..65149ac7a 100644
--- a/docs/tracks/pt/prerequisites-for-using-instore.md
+++ b/docs/tracks/pt/prerequisites-for-using-instore.md
@@ -3,8 +3,8 @@ title: 'Pré-requisitos para usar o VTEX Sales App'
 id: 1wtAanSRA3g2316dw7bw8u
 status: PUBLISHED
 createdAt: 2020-06-28T13:28:33.600Z
-updatedAt: 2023-05-31T15:30:38.223Z
-publishedAt: 2023-05-31T15:30:38.223Z
+updatedAt: 2024-06-27T16:50:09.189Z
+publishedAt: 2024-06-27T16:50:09.189Z
 firstPublishedAt: 2020-06-28T13:41:36.817Z
 contentType: trackArticle
 productTeam: Shopping
@@ -30,15 +30,12 @@ Para manter o equipamento e o bom funcionamento de sua operação, é importante
 
 ### Tablets, smartphones e computadores
 
-O aplicativo do VTEX Sales App funciona em tablets e smartphones que utilizam os sistemas operacionais **Android 6.0** (ou superior) e **iOS 9** (ou superior).
+É recomendado que os dispositivos estejam atualizados com a versão mais recente do sistema operacional, ou, no mínimo, utilize alguma das:
 
-Alguns exemplos de dispositivos que podem ser utilizados:
+* Três versões mais recentes do IOS, ou
+* Quatro versões mais recentes do Android.
 
-* Tablet Samsung Galaxy Tab A Note
-* Motorola G4
-* Samsung S8
-
-Recomendamos que os dispositivos usados para acessar o VTEX Sales App tenham chips 4G para acesso à internet. Dessa forma, sua loja continuará funcionando normalmente mesmo se a rede Wi-Fi tiver problemas.
+Ao acessar o VTEX Sales App, é necessário que os dispositivos utilizados possuam chips 4G para conexão à internet. Dessa forma, sua loja continuará funcionando normalmente, mesmo em situações em que a rede Wi-Fi apresente problemas.
 
 O VTEX Sales App também funciona em computadores que utilizam o sistema operacional **Windows**, desde que os seguintes requisitos mínimos sejam atendidos:
 
@@ -86,6 +83,16 @@ Para imprimir a fatura eletrônica (NFC-e) e os recibos de cartão, você precis
 ## Parceiros
 
 A VTEX possui uma série de parceiros que viabilizam a operação de lojas físicas. Cada parceiro tem uma função específica para que todo o processo de venda possa funcionar com segurança.
+Entre esses parceiros estão:
+
+- Integração com PDVs
+    - Jitterbit
+    - Neomode
+
+- Integração com pagamentos
+    - Pagarme
+    - Adyen
+    - Cielo
 
 A VTEX conta com um contrato padrão com esses parceiros para facilitar a implantação de seus produtos, mas cabe a você negociar melhores termos diretamente com eles.
 
diff --git a/docs/tracks/pt/prices-module-overview.md b/docs/tracks/pt/prices-module-overview.md
index 991139cb1..9094de005 100644
--- a/docs/tracks/pt/prices-module-overview.md
+++ b/docs/tracks/pt/prices-module-overview.md
@@ -3,8 +3,8 @@ title: 'Preços - Visão Geral'
 id: 3N9xYhnampRQOrfaTAOxNu
 status: PUBLISHED
 createdAt: 2019-07-09T19:26:54.473Z
-updatedAt: 2023-03-29T19:18:12.146Z
-publishedAt: 2023-03-29T19:18:12.146Z
+updatedAt: 2023-08-21T17:16:35.856Z
+publishedAt: 2023-08-21T17:16:35.856Z
 firstPublishedAt: 2019-07-11T21:35:16.813Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -20,4 +20,4 @@ O Pricing possui diversas funcionalidades que permitem o uso de diferentes estra
 
 **Lista de preços** - Nesta seção, você deve cadastrar os preços dos seus produtos. É nesta área que você pode consultar e inserir os preços dos SKUs para cada **tabela de preço** existente em sua loja.
 
-**Regras de preço** - Esta seção permite a criação de regras para as tabelas de preço da sua loja. As regras de preço são como funções que modificam os preços base cadastrados na área de Lista de preços.
+**Regras de preços** - Esta seção permite a criação de regras para as tabelas de preço da sua loja. As regras de preço são como funções que modificam os preços base cadastrados na área de Lista de preços.
diff --git a/docs/tracks/pt/pricing-system-architecture.md b/docs/tracks/pt/pricing-system-architecture.md
index a4567a6ae..34ead7a2d 100644
--- a/docs/tracks/pt/pricing-system-architecture.md
+++ b/docs/tracks/pt/pricing-system-architecture.md
@@ -3,8 +3,8 @@ title: 'Arquitetura do sistema de Preços'
 id: 7GptzvlPDVM11ojEjywIQx
 status: PUBLISHED
 createdAt: 2019-07-04T13:51:00.418Z
-updatedAt: 2022-07-27T20:39:31.113Z
-publishedAt: 2022-07-27T20:39:31.113Z
+updatedAt: 2024-04-22T19:20:30.485Z
+publishedAt: 2024-04-22T19:20:30.485Z
 firstPublishedAt: 2019-07-17T19:40:40.258Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -33,7 +33,7 @@ Estes podem ser:
 
 Abaixo, vemos um esquema de como os conceitos de *preços*, *tabela de preços* e *contextos* se relacionam:
 
-![enter image description here](https:https://images.ctfassets.net/alneenqid6w5/33vrmmMkAg9H4hSgQh0quO/c0f00cbaffb141a66874e2e5c636c099/architecture.svg)
+![enter image description here](https://images.ctfassets.net/alneenqid6w5/33vrmmMkAg9H4hSgQh0quO/c0f00cbaffb141a66874e2e5c636c099/architecture.svg)
 
 ## Preço computado
 
@@ -46,21 +46,21 @@ O módulo de preços considera 4 critérios para calcular o preço computado par
 - Arredondamento de Preços
 - Preço Fixo
 
-1. Caso o SKU tenha apenas o *preço-base* cadastrado, o preço computado para uma determinada tabela de preços será igual ao **preço-base**. ![enter image description here](https:https://images.ctfassets.net/alneenqid6w5/4TkDZzN4kJXKNXj9Ft6hWs/31d7ebdbd4b555e4edc6e8acba64709b/rule1.svg)
+1. Caso o SKU tenha apenas o *preço-base* cadastrado, o preço computado para uma determinada tabela de preços será igual ao **preço-base**. ![enter image description here](https://images.ctfassets.net/alneenqid6w5/4TkDZzN4kJXKNXj9Ft6hWs/31d7ebdbd4b555e4edc6e8acba64709b/rule1.svg)
 
-2. Se o SKU tiver uma *regra de preço* configurada para uma determinada tabela de preços, o preço computado será igual ao **preço-base modificado pela regra de preço**.![enter image description here](https:https://images.ctfassets.net/alneenqid6w5/7k9mOk5hOngCaAvzn0c7Wt/89fedbfc75f32e977bf75509f4c7d1fa/rule2.svg)
+2. Se o SKU tiver uma *regra de preço* configurada para uma determinada tabela de preços, o preço computado será igual ao **preço-base modificado pela regra de preço**.![enter image description here](https://images.ctfassets.net/alneenqid6w5/7k9mOk5hOngCaAvzn0c7Wt/89fedbfc75f32e977bf75509f4c7d1fa/rule2.svg)
 
-3. Em um outro cenário, vamos considerar um SKU com *preço-base*, *regra de preço* e *arredondamento de preços*. **O preço computado para uma determinada tabela de preço será calculado por uma combinação entre esses três fatores**. Primeiro, o preço base será modificado pela regra de preço. Depois disso, ocorrerá o arredondamento pela regra de preço psicológico.![rule3-pt](https://images.ctfassets.net/alneenqid6w5/3hpO858nn2Ln3rWizXP5uS/7b66e899d6ac3bbac7e5f1d53b814652/rule3.svg)
+3. Em um outro cenário, vamos considerar um SKU com *preço-base*, *regra de preço* e *arredondamento de preços*. **O preço computado para uma determinada tabela de preço será calculado por uma combinação entre esses três fatores**. Primeiro, o preço base será modificado pela regra de preço. Depois disso, ocorrerá o arredondamento pela regra de preço psicológico.![rule3-pt](//images.ctfassets.net/alneenqid6w5/3hpO858nn2Ln3rWizXP5uS/7b66e899d6ac3bbac7e5f1d53b814652/rule3.svg)
 
-4. Por fim, se um SKU tiver um *preço fixo* cadastrado, **o preço computado para uma determinada tabela de preços será igual ao preço fixo**. Este preço tem um peso superior aos outros preços. Desta maneira, o módulo de preços *ignora os outros preços* caso encontre um preço fixo associado a um SKU.![enter image description here](https:https://images.ctfassets.net/alneenqid6w5/1ztpeUQ5BDqR5ZTLtVAEia/e7472b2be59efd63dbd04faf90e312b3/rule4.svg)
+4. Por fim, se um SKU tiver um *preço fixo* cadastrado, **o preço computado para uma determinada tabela de preços será igual ao preço fixo**. Este preço tem um peso superior aos outros preços. Desta maneira, o módulo de preços *ignora os outros preços* caso encontre um preço fixo associado a um SKU.![enter image description here](https://images.ctfassets.net/alneenqid6w5/1ztpeUQ5BDqR5ZTLtVAEia/e7472b2be59efd63dbd04faf90e312b3/rule4.svg)
 
 ## Validar preço computado
 
 Para verificar o preço de venda de um SKU em uma determinada tabela de preços, você pode consultar o **valor do preço computado** na seção **Lista de preços** do Admin da VTEX. No exemplo abaixo, vemos que o preço computado do **SKU 14** para a **tabela da política comercial 1** é igual a **334,62**:
 
-![enter image description here](https:https://images.ctfassets.net/alneenqid6w5/TsRcmSsJ1J0E4ydLVdC09/37ee0472055e92fae51a5003ff4c24b7/computed-price-pt.png)
+![enter image description here](https://images.ctfassets.net/alneenqid6w5/TsRcmSsJ1J0E4ydLVdC09/37ee0472055e92fae51a5003ff4c24b7/computed-price-pt.png)
 
-Você também pode verificar qual o preço computado de um SKU em uma tabela de preços **fazendo uma chamada por API**. Para isso, você deve fazer um **GET** no endpoint [Get Computed Price by price table or trade policy](https://developers.vtex.com/vtex-rest-api/reference/getcomputedpricebypricetable).
+Você também pode verificar qual o preço computado de um SKU em uma tabela de preços **fazendo uma chamada por API**. Para isso, você deve fazer um **GET** no endpoint [Get Computed Price by price table or trade policy](https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-).
 
 Esta chamada retorna o `sellingPrice` de um SKU na tabela de preço `1`. **Esta é a informação que o módulo de preços entrega como *preço de venda* do SKU**.
 
diff --git a/docs/tracks/pt/printing-an-order-summary.md b/docs/tracks/pt/printing-an-order-summary.md
index b3eb24019..b80199e36 100644
--- a/docs/tracks/pt/printing-an-order-summary.md
+++ b/docs/tracks/pt/printing-an-order-summary.md
@@ -3,8 +3,8 @@ title: 'Impressão de resumo do pedido'
 id: 5UeqJA3sHp5goJacvHwPoS
 status: PUBLISHED
 createdAt: 2021-08-05T14:40:53.752Z
-updatedAt: 2023-05-31T15:23:48.750Z
-publishedAt: 2023-05-31T15:23:48.750Z
+updatedAt: 2023-07-26T19:01:33.402Z
+publishedAt: 2023-07-26T19:01:33.402Z
 firstPublishedAt: 2021-08-05T14:47:18.680Z
 contentType: trackArticle
 productTeam: Shopping
@@ -18,7 +18,7 @@ Ao concluir um pedido pelo VTEX Sales App, é possível imprimir um resumo do pe
 
 Para isso, o vendedor pode clicar no botão `Imprimir Pedido`, na tela de pedido finalizado, conforme ilustrado abaixo. Outra opção é configurar o VTEX Sales App para imprimir o resumo do pedido automaticamente, assim que o pedido for finalizado.
 
-![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/30253b60272652b911a9dfd03c9fe8ae/Group_1.png)
+![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/30253b60272652b911a9dfd03c9fe8ae/Group_1.png)
 
 Para habilitar a impressão do resumo do pedido, é necessário seguir as etapas descritas abaixo.
 
@@ -50,13 +50,13 @@ Com o AppKey e o AppToken em mãos, siga os passos abaixo.
 2. Abra o aplicativo do VTEX Sales App e informe o nome da loja onde você deseja configurar a impressora.
 3. No menu principal do VTEX Sales App, na seção **Configurações**, clique na opção <i class="fas fa-cog"></i> **Configurar o dispositivo**, ilustrada abaixo.
 
-![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/8a5a3ec9f8a845292f549bbaf3831756/Group_2.png)
+![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/8a5a3ec9f8a845292f549bbaf3831756/Group_2.png)
 
 <ol start="4">
   <li>Em seguida, você verá o resumo do dispositivo configurado. Se essa for a primeira vez em que essa configuração é realizada, os campos da tela estarão vazios, conforme a imagem abaixo. Se um dispositivo já tiver sido configurado anteriormente, você verá o <b>Nome do dispositivo</b> e <b>Impressora padrão</b>. Clique no botão <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">Editar</span>.</li>
 </ol>
 
-![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 <ol start="5">
   <li>Preencha o formulário contendo os campos descritos abaixo.
diff --git a/docs/tracks/pt/product-details.md b/docs/tracks/pt/product-details.md
index 7051411d6..b9477961b 100644
--- a/docs/tracks/pt/product-details.md
+++ b/docs/tracks/pt/product-details.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Ao clicar nos detalhes de um produto que aparece nos resultados da busca do VTEX Sales App, ou ao bipar um produto, o vendedor é direcionado à tela de detalhes do produto.
 
-![instore-pdp-pt](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/91062ff9c3840a3095bb96b36dc73136/pdp-pt.png)
+![instore-pdp-pt](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/91062ff9c3840a3095bb96b36dc73136/pdp-pt.png)
 
 Essa tela mostra o nome do produto, sua galeria de fotos, variações, descrição e disponibilidade. O vendedor pode, nessa tela, adicionar o produto ao carrinho.
 
diff --git a/docs/tracks/pt/product-group-registration-in-netshoes.md b/docs/tracks/pt/product-group-registration-in-netshoes.md
index 33c965a47..79d190f4c 100644
--- a/docs/tracks/pt/product-group-registration-in-netshoes.md
+++ b/docs/tracks/pt/product-group-registration-in-netshoes.md
@@ -19,7 +19,7 @@ Caso a [arquitetura do seu catálogo](https://help.vtex.com/pt/tracks/catalogo-1
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/3z63XIelT1rFWgyx336yWV/118d83ee093fae1e58a86fbf45c7292c/image6.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Variações de produto na Netshoes" title="Variações de produto na Netshoes">
+    <img src="https://images.ctfassets.net/alneenqid6w5/3z63XIelT1rFWgyx336yWV/118d83ee093fae1e58a86fbf45c7292c/image6.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Variações de produto na Netshoes" title="Variações de produto na Netshoes">
    </td>
   </tr>
   <tr>
@@ -38,7 +38,7 @@ O que faz com que seja preciso agrupar produtos é a criação de produtos difer
 <table width="100%">
   <tr>
    <td width="24px">
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/5CFfntd5BUumDCmdeGxwMo/0c838aa06775580b4e1ed0acf892ff52/image2.png" alt="Icon - Action required" title="Icon - Action required"/>
+    <img src="https://images.ctfassets.net/alneenqid6w5/5CFfntd5BUumDCmdeGxwMo/0c838aa06775580b4e1ed0acf892ff52/image2.png" alt="Icon - Action required" title="Icon - Action required"/>
    </td>
    <td style="padding-left: 12px;">
      <strong>
@@ -53,10 +53,10 @@ O que faz com que seja preciso agrupar produtos é a criação de produtos difer
 <table width="100%">
   <tr>
    <td width="50%">
-     <img src="https:https://images.ctfassets.net/alneenqid6w5/3ILf3V4cYT8yxlANjrR5lC/5db464128b49304b544334c60187866d/image4.png" alt="Tênis Infantil Asics Buzz 3 Gs - Cinza e Rosa" title="Tênis Infantil Asics Buzz 3 Gs - Cinza e Rosa" style="display: block; margin-left: auto; margin-right: auto;">
+     <img src="https://images.ctfassets.net/alneenqid6w5/3ILf3V4cYT8yxlANjrR5lC/5db464128b49304b544334c60187866d/image4.png" alt="Tênis Infantil Asics Buzz 3 Gs - Cinza e Rosa" title="Tênis Infantil Asics Buzz 3 Gs - Cinza e Rosa" style="display: block; margin-left: auto; margin-right: auto;">
    </td>
    <td width="50%">
-     <img src="https:https://images.ctfassets.net/alneenqid6w5/3Z4Bu3DFAGP2s2L8Ib5BkD/b759e3fdfba59130a493a324dd5b87ed/image8.png" alt="Tênis Infantil Asics Buzz 3 Gs - Cinza e Verde" title="Tênis Infantil Asics Buzz 3 Gs - Cinza e Verde" style="display: block; margin-left: auto; margin-right: auto;">
+     <img src="https://images.ctfassets.net/alneenqid6w5/3Z4Bu3DFAGP2s2L8Ib5BkD/b759e3fdfba59130a493a324dd5b87ed/image8.png" alt="Tênis Infantil Asics Buzz 3 Gs - Cinza e Verde" title="Tênis Infantil Asics Buzz 3 Gs - Cinza e Verde" style="display: block; margin-left: auto; margin-right: auto;">
    </td>
   </tr>
   <tr>
@@ -74,7 +74,7 @@ O que faz com que seja preciso agrupar produtos é a criação de produtos difer
 <table width="100%">
   <tr>
    <td width="24px">
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/7LUDORO5lzJLTAOnP6pHi9/162b4e9a129442d9d5df7713ee549725/image10.png" alt="Icon - No action needed" title="Icon - No action needed"/>
+    <img src="https://images.ctfassets.net/alneenqid6w5/7LUDORO5lzJLTAOnP6pHi9/162b4e9a129442d9d5df7713ee549725/image10.png" alt="Icon - No action needed" title="Icon - No action needed"/>
    </td>
    <td style="padding-left: 12px;">
      <strong>
@@ -89,10 +89,10 @@ O que faz com que seja preciso agrupar produtos é a criação de produtos difer
 <table width="100%">
   <tr>
    <td>
-     <img src="https:https://images.ctfassets.net/alneenqid6w5/33OYoWuZlolHt1pM9TrIcd/8f6f93b1dcccc7227414ef9dbb84c67e/image7.png" alt="Tênis Adidas Vs Advantage Clean Masculino - Preto" title="Tênis Adidas Vs Advantage Clean Masculino - Preto" style="display: block; margin-left: auto; margin-right: auto;">
+     <img src="https://images.ctfassets.net/alneenqid6w5/33OYoWuZlolHt1pM9TrIcd/8f6f93b1dcccc7227414ef9dbb84c67e/image7.png" alt="Tênis Adidas Vs Advantage Clean Masculino - Preto" title="Tênis Adidas Vs Advantage Clean Masculino - Preto" style="display: block; margin-left: auto; margin-right: auto;">
    </td>
    <td>
-     <img src="https:https://images.ctfassets.net/alneenqid6w5/6dDXm1LodPmv1ErSK5trEl/086f885406fa52ceab0387eed7a6701f/image5.png" alt="Tênis Adidas Vs Advantage Clean Masculino - Branco" title="Tênis Adidas Vs Advantage Clean Masculino - Branco" style="display: block; margin-left: auto; margin-right: auto;">
+     <img src="https://images.ctfassets.net/alneenqid6w5/6dDXm1LodPmv1ErSK5trEl/086f885406fa52ceab0387eed7a6701f/image5.png" alt="Tênis Adidas Vs Advantage Clean Masculino - Branco" title="Tênis Adidas Vs Advantage Clean Masculino - Branco" style="display: block; margin-left: auto; margin-right: auto;">
    </td>
   </tr>
   <tr>
@@ -112,8 +112,8 @@ Para verificar como está estruturado seu catálogo, você pode acessar a seçã
 <table width="100%">
   <tr>
    <td>
-    <a href="https:https://images.ctfassets.net/alneenqid6w5/2m665obeMjCkD6eGbOC5nm/9046ad832d38159fc576c33187778ec3/image9.png" target="_blank">
-      <img src="https:https://images.ctfassets.net/alneenqid6w5/2m665obeMjCkD6eGbOC5nm/9046ad832d38159fc576c33187778ec3/image9.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Mesmo modelo apresenta variações de cor separadas em produtos diferentes" title="Mesmo modelo apresenta variações de cor separadas em produtos diferentes">
+    <a href="https://images.ctfassets.net/alneenqid6w5/2m665obeMjCkD6eGbOC5nm/9046ad832d38159fc576c33187778ec3/image9.png" target="_blank">
+      <img src="https://images.ctfassets.net/alneenqid6w5/2m665obeMjCkD6eGbOC5nm/9046ad832d38159fc576c33187778ec3/image9.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Mesmo modelo apresenta variações de cor separadas em produtos diferentes" title="Mesmo modelo apresenta variações de cor separadas em produtos diferentes">
      </a>
    </td>
   </tr>
diff --git a/docs/tracks/pt/product-integration-errors-with-amazon.md b/docs/tracks/pt/product-integration-errors-with-amazon.md
new file mode 100644
index 000000000..42d773fe2
--- /dev/null
+++ b/docs/tracks/pt/product-integration-errors-with-amazon.md
@@ -0,0 +1,155 @@
+---
+title: 'Erros de integração de produtos Amazon'
+id: 4HsdzgoYxgQNtCBCRttKDA
+status: PUBLISHED
+createdAt: 2023-06-29T19:08:38.476Z
+updatedAt: 2023-09-26T15:02:03.011Z
+publishedAt: 2023-09-26T15:02:03.011Z
+firstPublishedAt: 2023-06-29T22:27:35.313Z
+contentType: trackArticle
+productTeam: Channels
+slug: erros-de-integracao-de-produtos-amazon
+locale: pt
+trackId: 6sgd4Pagy3wNsWKBvmIFrP
+trackSlugPT: erros-de-integracao-de-produtos-amazon
+---
+
+Há diversas razões pelas quais um produto entre a Amazon e sua loja VTEX pode não integrar, e para cada uma delas existe uma notificação que indica a natureza do erro. Você encontra a mensagem de erro no Admin VTEX, no módulo **Marketplace > Conexões > Produtos** ou na barra de busca. Ao acessar a página, filtre pelo marketplace Amazon e clique no produto para visualizar a mensagem.  
+
+Após solucionar um erro, é necessário reprocessar manualmente a integração do estoque daquele SKU. Isso é feito no mesmo local onde o erro é visualizado, clicando em **Ações > Reprocessar.**  
+
+Nesse artigo, listamos os seguintes erros:  
+
+- [Erros na planilha de mapeamento de categorias e atributos da Amazon](#Erros-na-planilha-de-mapeamento-de-categorias-e-atributos-da-Amazon)
+- [Erros de ausência de atributos obrigatórios na Amazon](#Erros-de-ausencia-de-atributos-obrigatorios-na-Amazon)
+- [Erros de divergência entre catálogos VTEX e Amazon (match de anúncios)](#Erros-de-divergencia-entre-catalogos-VTEX-e-Amazon-(match-de-anuncios))
+- [Erros de Token/Permissão da Amazon](#Erros-de-Token/Permissao-da-Amazon)
+- [Erros de configuração na integração da Amazon](#Erros-de-configuracao-na-integracao-da-Amazon)
+- [Erros no envio da categoria global VTEX](#Erros-no-envio-da-categoria-global-VTEX)
+- [Aviso de SKU Inativo](#Aviso-de-SKU-Inativo)
+
+## Erros na planilha de mapeamento de categorias e atributos da Amazon  
+
+- **A categoria global VTEX desse SKU não foi preenchida na planilha de mapeamento ou está preenchida incorretamente**  
+
+  Esse erro ocorre quando a Categoria global não está configurada ou configurada incorretamente. A Amazon utiliza a categoria global cadastrada na VTEX para fazer o mapeamento dos produtos, por isso, é importante que seja feita de maneira correta a equivalência entre a categoria global da VTEX e as categorias gerais na Amazon. 
+Para resolver esse erro, [configure a Categoria global](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#configuracao-da-categoria-global) do seu produto.
+
+- **A especificação (X) preenchida na planilha de mapeamento não foi encontrada na especificação do produto ou do SKU no seu catálogo da VTEX**
+
+  Esse erro ocorre quando a planilha foi preenchida com uma especificação que não existe no catálogo VTEX. Para resolver esse erro, você deverá cadastrar uma [especificação de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) ou [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr). Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`.
+
+- **O valor (X) preenchido na planilha de mapeamento não é um valor de atributo/especificação aceito pela Amazon**
+
+  O erro ocorre quando a especificação X não é aceita pela Amazon. Você deverá [cadastrar uma especificação](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) que seja aceita pela Amazon. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`.
+
+- **O ID da categoria global VTEX desse produto não foi encontrado na planilha de mapeamento**
+
+  Esse erro ocorre quando a Categoria global não está configurada ou configurada incorretamente. Para resolver esse erro, [configure a Categoria global](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#configuracao-da-categoria-global) do seu produto.
+
+- **O valor preenchido na planilha de mapeamento para a especificação "Material" ou “Departament” não é um valor de atributo/especificação aceito pela Amazon**
+
+  Em ambos os erros, a [Categoria Global VTEX](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) do produto selecionado pelo seller exige o cadastro obrigatório dos atributos Department ou Material no produto, e o  preenchimento da [planilha de mapeamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento). [Cadastre](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) o atributo no produto e preencha a planilha conforme o exemplo abaixo:  
+
+| **CategoryID** | **VariationTheme** | **Type** | **VTEXSpecification** | **AmazonSpecification** | **VTEXValue** | **AmazonValue** |
+|-----|-----|-----|-----|-----|-----|-----|
+| 3 |  | Information | Gênero | Department | Feminino | Female |
+
+- **Não foi feito o upload da planilha de mapeamento de categorias e atributos**
+
+  Esse erro ocorreu porque não foi feito o upload da [planilha de mapeamento da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento). Você deverá [preencher](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#5-preenchimento-da-planilha-de-mapeamento) a planilha de mapeamento da Amazon e fazer o [upload](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#6-upload-da-planilha-de-mapeamento) da planilha após o preenchimento. 
+
+- **O valor da especificação (X) preenchido na planilha não existe na especificação desse produto na VTEX**
+
+  No erro acima, o atributo citado não está cadastrado no SKU do catálogo VTEX. Você deverá [cadastrar o atributo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) e refazer o [mapeamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) do produto enviado.
+
+- **A unidade da idade mínima preenchida na planilha de mapeamento não está de acordo com o que a Amazon espera receber**
+
+- A unidade da idade mínima não está de acordo com o que a Amazon solicita. A Amazon aceita valores em anos ou meses, refaça o [mapeament](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD)o com valores aceitos pelo marketplace.
+
+- **A Amazon não aceita a(s) variação do SKU preenchida na planilha de mapeamento**
+
+  O erro ocorre quando a coluna **VariationTheme** da planilha de mapeamento da Amazon é preenchida com um valor que não é aceito pela Amazon. [Verifique os valores aceitos](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#5-preenchimento-da-planilha-de-mapeamento) e preencha um valor válido na planilha de mapeamento.
+
+- **O valor preenchido na planilha de mapeamento para o atributo "SizeMap" não é um valor de atributo/especificação aceito pela Amazon**
+
+  Você preencheu o valor do atributo `SizeMap` com um valor incorreto. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`.
+
+- **O valor preenchido na planilha de mapeamento para a especificação "TargetGender" não é um valor de atributo/especificação aceito pela Amazon**
+
+  Você preencheu o valor da especificação `TargetGender` com um valor incorreto. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`.
+
+- **Os atributos de cor e de tamanho que constam nesse SKU não foram encontrados na planilha de mapeamento**
+
+  Você não preencheu o valor das especificações Cor e Tamanho, obrigatórios para a categoria do produto que você quer enviar. Confira na [planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) para conferir os valores aceitos pela Amazon e preencha um valor válido na planilha de mapeamento.
+
+- **O atributo "author" não está cadastrado no SKU ou não consta na planilha de mapeamento**
+
+  Você não cadastrou o atributo obrigatório `Author` para o produto que você deseja enviar. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon), busque pela aba `VALORES VÁLIDOS` e [cadastre uma especificação de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) para esse atributo.
+
+- **O valor preenchido na planilha de mapeamento para o atributo "Size" não é um valor de atributo/especificação aceito pela Amazon**
+
+Você não preencheu o valor da especificação `Size` de maneira correta. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`.
+
+- **O valor preenchido na planilha de mapeamento para o atributo "Color" não é um valor de atributo/especificação aceito pela Amazon**
+
+  Você não preencheu o valor da especificação `Color` de maneira correta. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`.
+
+## Erros de ausência de atributos obrigatórios na Amazon
+
+- **O atributo Cor não está cadastrado no SKU ou não consta na planilha de mapeamento**
+
+  O atributo `Cor` é obrigatório para a categoria do produto que você está enviando para a Amazon e não está cadastrado no SKU ou não foi mapeado na planilha de mapeamento. 
+Você deverá cadastrar uma [especificação de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) para o atributo `Cor` e/ou refazer o [mapeamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) do produto enviado.
+
+- **A especificação do produto TargetGender é obrigatória para integrar esse produto com a Amazon**
+
+  A especificação do produto `TargetGender` é obrigatória para a categoria do produto que você está enviando. Dependendo da categoria, a Amazon pode chamar de Departamento ou TargetGender.
+Faça o [cadastro da especificação do produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) `TargetGender` e refaça o [mapeamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).
+
+## Erros de divergência entre catálogos VTEX e Amazon (Match de anúncios)
+
+- **SKU já existe no catálogo da Amazon e poderia ser feito o processo de matching dele entre VTEX e Amazon. Porém, o valor do atributo (x) deste SKU que consta na VTEX é diferente do valor que está cadastrado na Amazon para ele. Na VTEX ele é (x) e na Amazon, é (y).** 
+
+  Esse erro ocorre quando há divergências de valores do atributo (informações das características do SKU) entre o catálogo da Amazon e da VTEX. Para corrigir esse erro, você deverá [ajustar o valor do atributo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/6UjLHdAT5YLuflki10SXLr) na plataforma da VTEX para ficar equivalente ao [valor do atributo na plataforma da Amazon](https://drive.google.com/uc?export=download&id=1UkcrfPopMg-cnrSDOF0qt51NRIXgzi0r).  
+
+## Erro de Atributos Ausentes  
+
+- **`SKU XXXXX, Atributos Ausentes`. O SKU XXXXX não corresponde a nenhum ASIN. Certifique-se de que todos os identificadores de produtos padrão (como códigos UPC, ISBN, EAN ou JAN) estejam corretos.**  
+
+Esse erro ocorre quando um SKU em seu feed não corresponde a nenhum ASIN no catálogo da Amazon e que os dados de atributos do produto não são suficientes para criação de um ASIN. Para solucioná-lo, certifique-se de que está enviando as informações corretamente, conforme os valores exigidos pela Amazon na [planilha de atributos obrigatórios](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#2-planilha-de-atributos-obrigatorios-da-amazon).  
+
+## Erros de Token e Permissão da Amazon
+
+- **O token preenchido no formulário de configuração da Amazon na VTEX está expirado ou não tem permissão para acessar esse fluxo**
+
+  Esse erro ocorreu porque o número de série do **Token de autorização do MWS** expirou. Entre em contato com a Amazon para resolver esse problema, e depois refaça a [configuração da integração da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan).
+
+- **Sua conta não possui permissão na Amazon MWS**  
+
+  Falta de permissão na Amazon MWS. Para solucionar o erro é necessário entrar em contato com a Amazon pelo [Amazon Seller Central](https://sellercentral.amazon.com.br/). Mais informações sobre contas podem ser encontradas na documentação da Amazon [Gerenciar Conta da AWS](https://docs.aws.amazon.com/pt_br/accounts/latest/reference/managing-accounts.html). Para saber mais sobre política de segurança em contas de sellers na Amazon, consulte [Segurança em AWSGerenciamento de contas](https://docs.aws.amazon.com/pt_br/accounts/latest/reference/security.html).
+
+## Erros de configuração na integração da Amazon
+
+- **O valor que consta no campo "Nome para o tipo de frete" na configuração da integração da Amazon na VTEX não é igual ao que consta no Seller Central da Amazon**
+
+  Esse erro ocorre quando não há equivalência no valor cadastrado no campo **Nome para o tipo de frete** na etapa [Configurar a integração da Amazo](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan)n na VTEX e o valor cadastrado no Seller Central da Amazon. Acesse a documentação do Seller Central da Amazon para tirar suas dúvidas e corrigir o problema.
+
+- **O valor que consta no campo "SELLER ID" na configuração da integração da Amazon na VTEX não é igual ao que consta no Seller Central da Amazon**  
+
+  Esse erro ocorre quando não há equivalência no valor cadastrado no campo **Seller ID** na etapa [Configurar a integração da Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5J9CWPIbYQdAegJJWGsxan) na VTEX e o valor cadastrado no Seller Central da Amazon, lembrando que na configuração da integração, o valor de **Seller ID** solicitado é o que consta na Amazon.
+[Acesse a documentação do Seller Central da Amazon](https://sellercentral.amazon.com.br/sw/AccountInfo/MerchantToken/step/MerchantToken?ref_=macs_aimertok_cont_acinfohm&) para tirar suas dúvidas e corrigir o problema.  
+
+## Erro no envio da categoria global VTEX na Amazon
+
+- **A categoria global VTEX (X) desse SKU não está configurada corretamente na integração**
+
+  O erro ocorre quando a [categoria global](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188) selecionada no mapeamento não existe na Amazon. Confira o [mapeamento da Categoria Global](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#categoria-global) do produto, garantindo que a categoria selecionada está vinculada com a Amazon.
+
+## Aviso de SKU Inativo
+
+- **O SKU que você tentou enviar se encontra inativo na VTEX**
+
+O [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) não está ativo na VTEX, e somente SKUs ativos são integrados. Em alguns casos, este erro é gerado por [coleções](https://help.vtex.com/pt/tutorial/como-deletar-colecao--6C620yHzwsGoS8iaCocAM2) antigas vinculadas à política comercial da Amazon que contém SKUs inativos.
+
+Verifique o status do SKU no seu Admin, no módulo _PRODUTOS > Catálogo > Produtos e SKUs_ e, se necessário, [ative o SKU](https://help.vtex.com/pt/tutorial/ativar-skus-em-massa--4uMZATlSc0kEYiewWKSwEY).
diff --git a/docs/tracks/pt/promotions-for-specific-scenarios.md b/docs/tracks/pt/promotions-for-specific-scenarios.md
index 683da406e..93df9d5f0 100644
--- a/docs/tracks/pt/promotions-for-specific-scenarios.md
+++ b/docs/tracks/pt/promotions-for-specific-scenarios.md
@@ -1,10 +1,10 @@
 ---
 title: 'Promoções para cenários específicos'
 id: jOu9b69mKbrTDfSJYAawy
-status: CHANGED
+status: PUBLISHED
 createdAt: 2020-01-22T13:55:51.326Z
-updatedAt: 2020-11-27T19:40:32.581Z
-publishedAt: 2020-07-29T22:53:59.120Z
+updatedAt: 2023-10-23T17:08:04.859Z
+publishedAt: 2023-10-23T17:08:04.859Z
 firstPublishedAt: 2020-01-22T15:01:20.187Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -38,20 +38,19 @@ A tela de configuração da promoção oferece duas listas de SKUs, que podem se
 
 Você pode, então, definir um valor de desconto para a cada uma dessas listas. Se, por exemplo, a lista 1 tem 10% de desconto e a lista 2 tem 5% de desconto, quando o carrinho tiver pelo menos um produto de cada uma dessas listas, será concedido um total de 10% sobre o valor dos itens da lista 1 e um desconto de 5% sobre o valor dos itens da lista 2.
 
-![5 1](https://images.ctfassets.net/alneenqid6w5/365uWey6OG9w1jMlIbi11L/108d507cd3957a5e9c6b128cd920d543/5_1.png)
+![5 1](//images.ctfassets.net/alneenqid6w5/365uWey6OG9w1jMlIbi11L/108d507cd3957a5e9c6b128cd920d543/5_1.png)
 
 Dois exemplos desse tipo de promoção seriam "Compre uma calça e ganhe 10% na compra de um cinto" e "Compre um par de tênis + um par de meias e ganhe 15% de desconto".
 
 Para entender a promoção Compre Junto em mais detalhes, veja o artigo [Criar promoção Compre Junto](https://help.vtex.com/pt/tutorial/compre-junto--tutorials_323).
 
-
 ### Leve Mais por Menos
 
 A promoção do tipo Leve Mais por Menos é usada para conceder desconto quando o cliente adiciona várias unidades do mesmo produto ao carrinho. Um exemplo clássico dessa promoção seria "Leve 4 e pague 3".
 
 Na configuração da promoção Leve Mais por Menos, a loja deve definir a quais coleções ou SKUs ela será aplicada. Em seguida, escolha o número de itens no carrinho para ela funcionar e o número de itens com desconto.
 
-![5 2](https://images.ctfassets.net/alneenqid6w5/5wvLzNJIbEEzXFkH4Yf5lV/0da926307c9b2c31fcc6f7a63ad0c6c2/5_2.png)
+![Leve mais por menos](//images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/88a65536af3f8ee11f7fb7881056176b/Promo__es.png)
 
 Por exemplo:
 - A cada `3` produtos, o cliente levará `1` produto `grátis`.
@@ -69,7 +68,7 @@ Na configuração da promoção de Desconto Progressivo, a loja deve definir a q
 
 Para continuar a progressão do desconto, clique no botão de "+". Uma nova linha será adicionada, e então você poderá adicionar um novo desconto. Por exemplo: para os próximos 2 produtos, o cliente receberá mais 5% de desconto. E assim por diante.
 
-![5 3](https://images.ctfassets.net/alneenqid6w5/28KPsHCVKBF9ZgRUzwHudZ/81dcb7a88df530c81a8468e572aec43c/5_3.png)
+![5 3](//images.ctfassets.net/alneenqid6w5/28KPsHCVKBF9ZgRUzwHudZ/81dcb7a88df530c81a8468e572aec43c/5_3.png)
 
 Para entender a promoção de Desconto Progressivo em mais detalhes, veja o artigo [Como funciona o desconto progressivo](https://help.vtex.com/pt/tutorial/desconto-progressivo--tutorials_324).
 
@@ -79,7 +78,7 @@ A promoção do tipo Compre e Ganhe é usada para oferecer frete grátis ou um b
 
 O desconto aplicado (frete grátis ou brinde) deve ser definido nos dados gerais da promoção. Depois, a loja deve escolher as coleções ou SKUs aos quais ela será aplicada. E, por fim, deve definir a quantidade mínima de itens no carrinho para a promoção funcionar.
 
-![5 4](https://images.ctfassets.net/alneenqid6w5/59ir5nkFky3fqbvr6fh4ht/156bd36222aaf26eeae18644e8ef2075/5_4.png)
+![5 4](//images.ctfassets.net/alneenqid6w5/59ir5nkFky3fqbvr6fh4ht/156bd36222aaf26eeae18644e8ef2075/5_4.png)
 
 Para entender a promoção do tipo Compre e Ganhe em mais detalhes, veja o artigo [Como funciona a promoção Compre e Ganhe](https://help.vtex.com/pt/tutorial/compre-e-ganhe--tutorials_322).
 
@@ -93,22 +92,22 @@ Esta configuração define quantos itens do carrinho serão afetados pela promo
 
 Depois de preencher todos [os campos de uma promoção regular](https://help.vtex.com/pt/tutorial/regular-promotion--tutorials_327) com desconto percentual, você pode selecionar a opção __Definir quantidade máxima de itens afetados por carrinho__ na seção __Restrições e limites de uso__.
 
-![Limite itens - PT](https://images.ctfassets.net/alneenqid6w5/6X3fH4UtV36JojrWyVXfqj/57d55acfe5510ac9b9bdfe1c54ae0123/Limite_itens_-_PT.png)
+![Limite itens - PT](//images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/efa4913d768b6c60a738ade38b36250c/Limite_itens_-_PT.png)
 
 Por default, a seleção __ilimitado__ está ativa, aplicando a promoção em todos os itens do carrinho, como ilustrado no diagrama abaixo:
 
-![Caso ilimitado - PT](https://images.ctfassets.net/alneenqid6w5/ryqePV18B6yVGLoUnqHdg/406ea14fc3a931027876309e46cb6afa/Caso_ilimitado.png)
+![Caso ilimitado - PT](//images.ctfassets.net/alneenqid6w5/ryqePV18B6yVGLoUnqHdg/406ea14fc3a931027876309e46cb6afa/Caso_ilimitado.png)
 
 Para restringir o número de itens do carrinho que receberão o desconto, você pode escolher entre uma das seguintes opções:
 
 - __Itens por carrinho__: essa configuração limita a aplicação da promoção a um número de itens do carrinho. Assim que o limite for atingido, a promoção não será aplicada para o restante do carrinho. O sistema utiliza o preço como critério de escolha, dessa forma, os itens com preço menor serão os primeiros a serem afetados.
 
-![Caso por item - PT](https://images.ctfassets.net/alneenqid6w5/7yXbUrBWdqkcWyvXaLa7Hc/5de06c1250b310850722f31a63c36418/Caso_por_item.png)
+![Caso por item - PT](//images.ctfassets.net/alneenqid6w5/7yXbUrBWdqkcWyvXaLa7Hc/5de06c1250b310850722f31a63c36418/Caso_por_item.png)
 
 - __Itens por produto__: essa configuração limita a promoção a um número de unidades de cada produto. Como no exemplo abaixo, apenas duas unidades por produto serão elegíveis para a promoção. O preço mais baixo define os itens de cada produto elegíveis para a promoção.
 
-![Caso por produto - PT](https://images.ctfassets.net/alneenqid6w5/55wWvZwHyjvrfk01vA9PRX/972beb813354aafcfa65c25ae5d37135/Caso_por_produto.png)
+![Caso por produto - PT](//images.ctfassets.net/alneenqid6w5/55wWvZwHyjvrfk01vA9PRX/972beb813354aafcfa65c25ae5d37135/Caso_por_produto.png)
 
 - __Itens por SKU__: essa configuração limita a promoção a um número de unidades para cada SKU no carrinho. Como no exemplo abaixo, apenas duas unidades de cada SKU serão elegíveis para a promoção. Assim como no caso anterior, será o preço mais baixo que definirá os itens elegíveis para a promoção.
 
-![Caso por SKU - PT](https://images.ctfassets.net/alneenqid6w5/2UCLkXZNHNKJtecRIeoYuF/c73bd02637a38ed2693ba5d2f74a8efa/Caso_por_SKU.png)
+![Caso por SKU - PT](//images.ctfassets.net/alneenqid6w5/2UCLkXZNHNKJtecRIeoYuF/c73bd02637a38ed2693ba5d2f74a8efa/Caso_por_SKU.png)
diff --git a/docs/tracks/pt/rappi-integration-overview.md b/docs/tracks/pt/rappi-integration-overview.md
new file mode 100644
index 000000000..87d399920
--- /dev/null
+++ b/docs/tracks/pt/rappi-integration-overview.md
@@ -0,0 +1,35 @@
+---
+title: 'Visão geral da integração com a Rappi'
+id: 7y40IL3ajiukMRHrX3XmC8
+status: PUBLISHED
+createdAt: 2024-05-31T20:24:26.112Z
+updatedAt: 2024-05-31T20:51:33.604Z
+publishedAt: 2024-05-31T20:51:33.604Z
+firstPublishedAt: 2024-05-31T20:51:33.604Z
+contentType: trackArticle
+productTeam: Channels
+slug: visao-geral-da-integracao-com-a-rappi
+locale: pt
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugPT: integracao-rappi
+---
+
+A Rappi é uma plataforma que funciona como marketplace conectando compradores a produtos dos mais diversos segmentos. Acompanhando a experiência do cliente da compra à entrega.
+
+![Logo Rappi](//images.ctfassets.net/alneenqid6w5/INsIz4tJzR7MR8JsKPKjt/4264529e186ed1aa18d6e75352719dfe/logo-rappi.jpg)
+
+A configuração com a Rappi tem o objetivo conectar sua loja VTEX com a plataforma, permitindo que você anuncie seus produtos, aumente suas vendas e alcance novos clientes a partir deste canal.
+
+<div class="alert alert-warning">
+A integração com a Rappi está disponível apenas para lojas VTEX do Brasil, que possuam loja física.
+</div>
+
+<div class="alert alert-info">
+A funcionalidade <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> (MOI) não está disponível na integração com a Rappi.
+</div>
+
+Para realizar a configuração entre VTEX e Rappi, é necessário concluir algumas etapas:
+
+[Credenciais Rappi](#credenciais-rappi)  
+[Configurações na plataforma VTEX](#configuracoes-na-plataforma)  
+[Cadastro da integração da Rappi](#cadastro-da-integracao-da-rappi)  
diff --git a/docs/tracks/pt/rappi-integration-registration.md b/docs/tracks/pt/rappi-integration-registration.md
new file mode 100644
index 000000000..dd15485e1
--- /dev/null
+++ b/docs/tracks/pt/rappi-integration-registration.md
@@ -0,0 +1,35 @@
+---
+title: 'Cadastro da integração Rappi'
+id: 4Wu9gyd5xCRC0MOb5zG9BK
+status: PUBLISHED
+createdAt: 2024-05-31T20:39:08.338Z
+updatedAt: 2024-05-31T20:51:55.857Z
+publishedAt: 2024-05-31T20:51:55.857Z
+firstPublishedAt: 2024-05-31T20:51:55.857Z
+contentType: trackArticle
+productTeam: Channels
+slug: cadastro-da-integracao-rappi
+locale: pt
+trackId: 2AeYfJRnQ0I91dvSzRcpKh
+trackSlugPT: integracao-rappi
+---
+
+Terminadas as etapas de configuração da sua conta na Rappi e da sua conta na VTEX, a configuração do conector é feita no Admin VTEX. Para configurar, siga as instruções abaixo:  
+
+1. No Admin VTEX vá em *Marketplace* > Conexões > **Marketplaces e** **Integrações** ou digite **Marketplaces e Integrações** na barra de busca.  
+2. Digite **Rappi** na barra de busca da página, clique no card da integração.  
+3. Clique no botão **`Conectar`**.    
+
+<div class="alert alert-info">
+Todos os campos da tela de configuração da Rappi são obrigatórios.
+</div>  
+
+| **Campo** | **Descrição** | **Exemplo** |
+|---|---|---|
+| **Status da integração** | Botão que define se a integração estará ligada ou desligada. | <i class="fas fa-toggle-on"></i>  ou <i class="fas fa-toggle-off"></i> |
+| **ID do Afiliado** | Código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não. Vogais não são aceitas.  A configuração do conector cria automaticamente o afiliado. | RPP |
+| **Email** | Email do representante comercial da Livelo para o afiliado que está sendo criado. | email@integracao.com |
+| **Canal de vendas** | Identificador da [política comercial](https://help.vtex.com/pt/tutorial/configuring-a-marketplace-trade-policy--tutorials_404) que definirá o sortimento de catálogo e os valores dos itens que serão enviados para a Livelo. | 1 |
+| **Client Id** | Identificador fornecido pela Rappi. | rppteste |
+| **Secret** | Chave alfanumérica  fornecida pela Livelo. | xx61x016-xx41-423x-xx42-xx781x6x14xx5 |
+
diff --git a/docs/tracks/pt/receivables-management.md b/docs/tracks/pt/receivables-management.md
index b832bffb4..953194610 100644
--- a/docs/tracks/pt/receivables-management.md
+++ b/docs/tracks/pt/receivables-management.md
@@ -1,10 +1,10 @@
 ---
 title: 'Gestão de recebíveis'
 id: 4zO5DEg07BSqHsmlBrCgvr
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T18:01:47.594Z
-updatedAt: 2023-03-14T22:07:36.630Z
-publishedAt: 2023-03-14T22:07:36.630Z
+updatedAt: 2023-10-05T14:14:03.274Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:50:17.208Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/pt/register-mercado-livre-integration.md b/docs/tracks/pt/register-mercado-livre-integration.md
index fe3eace7d..e90821d59 100644
--- a/docs/tracks/pt/register-mercado-livre-integration.md
+++ b/docs/tracks/pt/register-mercado-livre-integration.md
@@ -3,8 +3,8 @@ title: 'Cadastro do conector Mercado Livre'
 id: 4YvYdgICMosaEgISOYogsi
 status: PUBLISHED
 createdAt: 2018-08-13T12:33:55.818Z
-updatedAt: 2022-02-03T23:29:27.323Z
-publishedAt: 2022-02-03T23:29:27.323Z
+updatedAt: 2023-07-06T20:21:00.334Z
+publishedAt: 2023-07-06T20:21:00.334Z
 firstPublishedAt: 2018-08-13T14:28:06.574Z
 contentType: trackArticle
 productTeam: Channels
@@ -25,20 +25,11 @@ Cada conta VTEX deve estar vinculada a apenas uma conta no Mercado Livre, mesmo
 </div>
 
 - **Integração (se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos)* :** selecione *Ativada* para que a integração comece a operar.
-- **ID do afiliado*:** código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado)que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestões: `MLC` (Classic) ou `MLP` (Premium). A configuração do conector cria automaticamente o afiliado.
+- **ID do afiliado*:** código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestões: `MLC` (Classic) ou `MLP` (Premium). A configuração do conector cria automaticamente o afiliado.
 - **ID da política comercial*:** ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será utilizada para a integração com o Mercado Livre. São os produtos dessa política comercial que serão enviados para o marketplace.
 - **Formato do título do anúncio*:** regra para formação do título do anúncio que será publicado no Mercado Livre. Esse título pode combinar diferentes atributos do Catálogo, como *Marca*, *Nome do Produto* e *Nome do SKU*. Os títulos de anúncios no Mercado Livre podem ter no máximo 60 caracteres. Para customizar o *Formato do título do anúncio* de um produto, você pode [criar um campo de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106) com o nome `meli_title`, do tipo `Texto Grande` e a opção `Exibe Especificação` desativada.
 - **Atualizar descrição do anúncio*:** quando ativado, atualiza automaticamente a descrição do anúncio no Mercado Livre sempre que for feita uma alteração na descrição do produto na VTEX. Caso contrário, a descrição original será mantida.
-- **Ativar integração de pontos de retirada*:** quando ativada, viabiliza o recurso de retirada de produtos nos pontos de retirada cadastrados na VTEX da loja principal.
-- **Ativar integração de pontos de retirada para contas franquias*:** quando ativada, viabiliza o recurso de retirada de produtos nos [pontos de retirada](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/52C1lm8gMovN8v68s6v89d) cadastrados na VTEX das contas franquias.
-- **Ativar estoque para entrega e cotação de frete para contas franquias*:** quando ativada, viabiliza o recurso de utilizar o [estoque das contas franquias](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/52C1lm8gMovN8v68s6v89d).
-- **Estratégia de envio de estoque (válida apenas caso a configuração de estoque e cotação para contas franquias estiver ativa):** caso tenha ativado a opção anterior, selecione as seguintes opções:
-   * **Total dos estoques:** utiliza a soma dos estoques das contas franquias mais estoque da loja principal.
-   * **Estoque máximo:** utiliza apenas o maior estoque disponível da conta franquia.
-- **Estratégia de envio para cotação de frete (válida apenas caso a configuração de estoque e cotação para contas franquias estiver ativa):** caso você tenha uma conta franquia, selecione as seguintes opções:
-   * **Mais barato:** optando por um frete mais barato, o tempo de entrega é maior.
-   * **Mais rápido:** optando por um frete mais rápido, o preço é mais alto.
-- **ID da Loja Oficial no Mercado Livre:**  identificador numérico de três ou quatro dígitos fornecido pelo Mercado Livre no seu contrato comercial quando um usuário atinge o status de [Loja Oficial](https://www.mercadolivre.com.br/lojas-oficiais/catalogo). Deve ser preenchido caso sua loja tenha este status, para que a integração funcione corretamente.
+- **ID da Loja Oficial no Mercado Livre:**  identificador numérico fornecido pelo Mercado Livre no seu contrato comercial quando um usuário atinge o status de [Loja Oficial](https://www.mercadolivre.com.br/lojas-oficiais/catalogo). Deve ser preenchido caso sua loja tenha este status, para que a integração funcione corretamente.
 - **Estoque limite para pausa de anúncio*:** valor mínimo de estoque de segurança. Se a quantidade de itens em estoque de um produto estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização do Mercado Livre pela VTEX.
 - **Formato do arquivo da etiqueta de remessas*:** escolha entre os formatos PDF ou JSON (que é compatível com impressoras zebra), para impressão das etiquetas dos produtos.
 - **Atributos omitidos no template do produto:** preencha o campo com atributos do produto que estão cadastrados na VTEX, mas que  você não deseja incluir no Mercado Livre.
diff --git a/docs/tracks/pt/registering-the-carrefour-integration.md b/docs/tracks/pt/registering-the-carrefour-integration.md
index db3b8f80b..c3ba68a1a 100644
--- a/docs/tracks/pt/registering-the-carrefour-integration.md
+++ b/docs/tracks/pt/registering-the-carrefour-integration.md
@@ -3,8 +3,8 @@ title: 'Configurar cadastro do conector Carrefour'
 id: 2AhqcmRN1mseCsGuGIe6GK
 status: PUBLISHED
 createdAt: 2018-10-08T23:26:55.073Z
-updatedAt: 2022-09-06T22:59:04.246Z
-publishedAt: 2022-09-06T22:59:04.246Z
+updatedAt: 2024-07-02T19:27:42.975Z
+publishedAt: 2024-07-02T19:27:42.975Z
 firstPublishedAt: 2018-10-08T23:51:59.055Z
 contentType: trackArticle
 productTeam: Channels
@@ -54,6 +54,31 @@ Caso a categoria de produtos não exija o mapeamento de certificados, o campo de
 - __Mapeamento de SLA de tipo Expressa*:__ preencha com o nome do [Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126) cadastrado na [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_1400). Por exemplo, se você cadastrou como `Expressa`, então, deve preencher esse campo o nome exatamente igual.
 - __Mapeamento de SLA de tipo Econômica*:__ preencha com o nome do [Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126) cadastrado na [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_1400). Por exemplo, se você cadastrou como `Entrega econômica`, então, deve preencher esse campo o nome exatamente igual.
 - __Mapeamento de SLA de tipo Agendada*:__ preencha com o nome do [Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126) cadastrado na [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_1400). Por exemplo, se você cadastrou como `Agendada`, então, deve preencher esse campo o nome exatamente igual.
+- **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+  <p><b>Exemplo de nome para o novo campo:</b> <code>CRF_ProductName</code> para nome do produto e <code>CRF_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   
+Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+2. Preencha o campo PARA com o nome do novo campo.   
+`CRF_ProductName` para nome do produto e `CRF_ProductDescription` para descrição do produto.    
+3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
+</div>  
 
 ### Categorias elegíveis
 
diff --git a/docs/tracks/pt/registering-the-centauro-integration.md b/docs/tracks/pt/registering-the-centauro-integration.md
index 9f542add1..5307823bf 100644
--- a/docs/tracks/pt/registering-the-centauro-integration.md
+++ b/docs/tracks/pt/registering-the-centauro-integration.md
@@ -3,8 +3,8 @@ title: 'Cadastro da integração da Centauro'
 id: 4EqL0hADU1AWvP0gTr4nyq
 status: PUBLISHED
 createdAt: 2020-10-20T18:55:02.489Z
-updatedAt: 2022-01-25T15:55:01.810Z
-publishedAt: 2022-01-25T15:55:01.810Z
+updatedAt: 2024-07-02T19:28:22.448Z
+publishedAt: 2024-07-02T19:28:22.448Z
 firstPublishedAt: 2020-10-20T19:51:24.705Z
 contentType: trackArticle
 productTeam: Channels
@@ -32,3 +32,30 @@ Nessa etapa, você realizará o cadastro da sua loja na integração da Centauro
 | Token da Centauro * | Chave de acesso para comunicação entre VTEX e Centauro. Este token deve ser solicitado diretamente para Centauro e preenchido neste campo.|
 | Estoque mínimo | Valor mínimo de estoque de segurança. Se a quantidade de itens em estoque de um produto estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização da Centauro pela VTEX. Escolha com cuidado: essa configuração é aplicada a todos produtos. Verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.|
 | Account da Centauro | Nome da loja no ambiente da Centauro. |
+
+**Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+  <p><b>Exemplo de nome para o novo campo:</b> <code>CTR_ProductName</code> para nome do produto e <code>CTR_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   
+Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+2. Preencha o campo PARA com o nome do novo campo.   
+`CTR_ProductName` para nome do produto e `CTR_ProductDescription` para descrição do produto.    
+3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.   
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
+</div>
+
diff --git a/docs/tracks/pt/registering-the-integration.md b/docs/tracks/pt/registering-the-integration.md
index aa79c4a3b..bd81521ea 100644
--- a/docs/tracks/pt/registering-the-integration.md
+++ b/docs/tracks/pt/registering-the-integration.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar cadastro do conector da Via'
+title: 'Configurar cadastro do conector da Casas Bahia Marketplace'
 id: 1okse2MybWk04AQoueu88O
 status: PUBLISHED
 createdAt: 2018-09-24T18:45:21.544Z
-updatedAt: 2022-02-07T21:16:28.792Z
-publishedAt: 2022-02-07T21:16:28.792Z
+updatedAt: 2024-07-02T19:20:54.448Z
+publishedAt: 2024-07-02T19:20:54.448Z
 firstPublishedAt: 2018-09-27T22:12:25.372Z
 contentType: trackArticle
 productTeam: Channels
@@ -16,23 +16,50 @@ trackSlugPT: configurar-integracao-da-via-varejo
 
 O cadastro do conector é feito no Admin da VTEX. Para realizá-lo, siga as instruções abaixo.
 
-1. No Admin VTEX, acesse **MARKETPLACE > Integrações**.
-2. Selecione a opção `Configuração`.
-3. Busque pelo box da Via e clique em `Integrar`.
-4. Preencha os campos da tela descritos logo abaixo e, em seguida, clique no botão `Salvar Configuração` (campos marcados com o símbolo * são obrigatórios).
+1. No Admin VTEX, acesse **Marketplace > Conexões >Marketplace e integrações** ou digite **Marketplace e integrações** na barra de busca.  
+2. Busque pelo conector da **Casas Bahia Marketplace**.  
+3. Clique em `Conectar`.
+5. Preencha os campos da tela descritos logo abaixo e, em seguida, clique no botão `Salvar Configuração` (campos marcados com o símbolo * são obrigatórios).
 
 - **Id do afiliado*:** código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) qque ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestão: `VVJ`. A configuração do conector cria automaticamente o afiliado.
-- **Afiliate Email*:** preencha com o e-mail cadastrado na etapa [**Criar conta de seller na Via**](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/2oxPVeYpVgA8IrhaDqKon6#criar-conta-de-seller-na-via).
-- **Política comercial*:** ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será utilizada para a integração com a Via. São os produtos dessa política comercial que serão enviados para o marketplace.
-- **Chave de acesso:** preencha com o Token enviado pela Via na etapa [Solicitar token na Via](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/2oxPVeYpVgA8IrhaDqKon6#solicitar-token-na-via).
-- **CNPJ*:** preencha esse campo com o CNPJ da sua loja. Essa informação é obrigatória para que seja possível faturar os pedidos. Leia o artigo [Fluxo de configuração](https://help.vtex.com/pt/tutorial/como-funciona-a-integracao-da-cnova-via-varejo) da Via para saber mais.
+- **Afiliate Email*:** preencha com o e-mail cadastrado na etapa [**Criar conta de seller na Casas Bahia Marketplace**](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/2oxPVeYpVgA8IrhaDqKon6#criar-conta-de-seller-na-via).
+- **Política comercial*:** ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será utilizada para a integração com a Casas Bahia Marketplace. São os produtos dessa política comercial que serão enviados para o marketplace.
+- **Chave de acesso:** preencha com o Token enviado pela Casas Bahia Marketplace na etapa [Solicitar token na Via](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/2oxPVeYpVgA8IrhaDqKon6#solicitar-token-na-via).
+- **CNPJ*:** preencha esse campo com o CNPJ da sua loja. Essa informação é obrigatória para que seja possível faturar os pedidos. Leia o artigo [Fluxo de configuração](https://help.vtex.com/pt/tutorial/como-funciona-a-integracao-da-cnova-via-varejo) da Casas Bahia Marketplace para saber mais.
 - **Nome do campo de Especificação de Produto que contém sua Descrição:** preencha esse campo para utilizar uma descrição diferente da que já está cadastrada no catálogo VTEX. Ao preencher esse campo, você deverá [criar um campo de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106) do tipo `Texto Grande`. O conector priorizará o envio da descrição contida no campo criado.
-- **Estoque mínimo*:** determina o valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização da Via pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
-- **Enviar KIT*:** ao escolher `Não`, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Via. Ao habilitar `Sim`, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de `Sim` para `Não`, SKUs enviados anteriormente para a Via não seriam removidos ou sofreriam qualquer alteração. Se você mudar sua configuração de `Não` para `Sim`, você precisará [reindexar a base](https://help.vtex.com/pt/tutorial/manutencao-de-base-full-cleanup--34P9LGs7BCIQK6acQom802) para que a configuração seja aplicada.
+- **Estoque mínimo*:** determina o valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização da Casas Bahia Marketplace pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
+- **Enviar KIT*:** ao escolher `Não`, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Casas Bahia Marketplace. Ao habilitar `Sim`, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de `Sim` para `Não`, SKUs enviados anteriormente para a Casas Bahia Marketplace não seriam removidos ou sofreriam qualquer alteração. Se você mudar sua configuração de `Não` para `Sim`, você precisará [reindexar a base](https://help.vtex.com/pt/tutorial/manutencao-de-base-full-cleanup--34P9LGs7BCIQK6acQom802) para que a configuração seja aplicada.
 
 <div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a Via de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos</b>, ao se clicar sobre o SKU.</div>
+Com a opção <i>Não</i> ativada, tentativas de envio para a Casas Bahia Marketplace de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos</b>, ao se clicar sobre o SKU.</div>
 
 - **E-mails Para Notificação de Pedidos Não Integrados*:** preencher com o e-mail do responsável técnico. Caso ocorra algum erro na integração do pedido, será enviada uma mensagem para o e-mail cadastrado.
 
-<div class="alert alert-warning">Caso você não aperte no botão <code>+</code> para inserir o E-MAIL PARA NOTIFICAÇÃO DE PEDIDOS NÃO INTEGRADOS, aparecerá um alerta de erro ao salvar a configuração.</div>
+<div class="alert alert-warning">Caso você não aperte no botão <code>+</code> para inserir o E-MAIL PARA NOTIFICAÇÃO DE PEDIDOS NÃO INTEGRADOS, aparecerá um alerta de erro ao salvar a configuração.</div>  
+
+**Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+<p><b>Exemplo de nome para o novo campo:</b> <code>CBH_ProductName</code> para nome do produto e <code>CBH_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   
+Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+3. Preencha o campo PARA com o nome do novo campo.   
+`CBH_ProductName` para nome do produto e `CBH_ProductDescription` para descrição do produto.    
+4. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
+</div>
+
diff --git a/docs/tracks/pt/registering-the-netshoes-integration.md b/docs/tracks/pt/registering-the-netshoes-integration.md
index f045805c7..ed38f2dd6 100644
--- a/docs/tracks/pt/registering-the-netshoes-integration.md
+++ b/docs/tracks/pt/registering-the-netshoes-integration.md
@@ -3,8 +3,8 @@ title: 'Cadastro da integração da Netshoes'
 id: 7o8Vt25LJmAUuMmSWSmWes
 status: PUBLISHED
 createdAt: 2018-09-24T20:27:48.984Z
-updatedAt: 2023-01-05T20:12:16.965Z
-publishedAt: 2023-01-05T20:12:16.965Z
+updatedAt: 2024-07-02T19:19:00.338Z
+publishedAt: 2024-07-02T19:19:00.338Z
 firstPublishedAt: 2018-09-27T15:02:23.717Z
 contentType: trackArticle
 productTeam: Channels
@@ -54,3 +54,29 @@ Com a opção <i>Não</i> ativada, tentativas de envio para a Netshoes de SKUs c
 </div> 
 
    * **Emails de notificação de erro de pedido:** adicione os endereços eletrônicos por meio dos quais você gostaria de ser notificado em caso de erro de integração de um pedido. Não há um número limite para esses emails.
+   * **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+<div class = "alert alert-info">
+  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
+  <p><b>Exemplo de nome para o novo campo:</b> <code>NTS_ProductName</code> para nome do produto e <code>NTS_ProductDescription</code> para descrição do produto.</p>
+</div>  
+
+Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
+
+1. Criar um campo do tipo `Texto grande`.  
+2. Desativar a opção  `Exibe especificação`.  
+3. Preencher os campos criados em cada produto cadastrado.  
+
+O preenchimento desse campo deve ser realizado da seguinte maneira:
+
+1. Preencha o campo DE com o nome do campo de origem.   Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `ProductDescription` para descrição do produto.  
+2. Preencha o campo PARA com o nome do novo campo.   `NTS_ProductName` para nome do produto e `NTS_ProductDescription` para descrição do produto.  
+3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
+
+<div class="alert alert-info">
+Cada regra cadastrada mapeia apenas um campo.
+<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.<p>
+</div>
+
diff --git a/docs/tracks/pt/relevance.md b/docs/tracks/pt/relevance.md
index d87a1a561..c5828b81e 100644
--- a/docs/tracks/pt/relevance.md
+++ b/docs/tracks/pt/relevance.md
@@ -3,8 +3,8 @@ title: 'Relevância'
 id: 1qlObWIib6KqgrfX1FCOXS
 status: PUBLISHED
 createdAt: 2020-04-14T13:35:28.989Z
-updatedAt: 2023-01-23T13:48:19.938Z
-publishedAt: 2023-01-23T13:48:19.938Z
+updatedAt: 2024-01-12T22:16:50.165Z
+publishedAt: 2024-01-12T22:16:50.165Z
 firstPublishedAt: 2020-04-14T23:58:35.468Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,25 +14,27 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
-As Regras de Relevância são aplicadas nos resultados de busca apenas quando a ordenação dos resultados é feita por relevância na busca da sua loja. Por exemplo, se um cliente selecionar a ordenação dos resultados por preço, as configurações de relevância não terão efeito na ordem dos resultados.
+As **Regras de relevância** definem a ordem em que os produtos são exibidos nos resultados de busca nas páginas de listagem de produtos (PLP). A ordem muda de acordo com os critérios e prioridades configurados.
+
+As Regras de relevância são aplicadas nos resultados de busca apenas quando a ordenação dos resultados é feita por relevância na busca da sua loja. Por exemplo, se um cliente selecionar a ordenação dos resultados por preço, as configurações de relevância não terão efeito na ordem dos resultados.
 
 Existem dois cenários possíveis de configurações de relevância:
 
 - **Critérios prioritários:** é a forma de forçar que um ou mais critérios terão prioridade maior entre os demais. Nessa situação não existem pesos, pois todos os produtos que possuírem essa característica serão apresentados primeiro no resultado de busca.
 - **Composição de critérios:** é a forma de distribuir pesos para cada opção, variando de 0 a 10. Aqui, não existe uma ordem entre os critérios, serão os pesos que vão definir a relevância.
 
-![regras-relevancia-1-PT](https://images.ctfassets.net/alneenqid6w5/pWaOZBllEtnkrAxc2kEdJ/f6c856ddd8d6f49ed08bdaa921f214ae/Captura_de_Tela_2022-03-25_a__s_15.14.17.png)
+![criterios-pt](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/faefb674583084511a114faf0c39cdbd/criterios-pt.png)
 
-As informações aplicadas para compôr a relevância são:
+As informações aplicadas para compor a relevância são:
 
-- **Desconto (de / por):** critério que compara o [Preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) e o [Preço base](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicao) cadastrados para determinar se o produto será classificado com desconto.
-- **Lançamento:** esse critério atribui um valor automático decrescente (entre 1 e 0) a partir da data de cadastro do produto na loja, considerando um intervalo de 90 dias. Produtos cadastrados hoje teriam o valor 1 e esse valor vai reduzindo a cada dia, até que, do dia 90 em diante, passa a ser 0. Esse valor é multiplicado pelo peso que você cadastrar para o critério **Lançamento** para compor a relevância.
+- **Desconto:** critério que compara o [Preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) e o [Preço base](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicao) cadastrados para determinar se o produto será classificado com desconto.
+- **Data de lançamento:** esse critério atribui um valor automático decrescente (entre 1 e 0) a partir da data de cadastro do produto na loja, considerando um intervalo de 90 dias. Produtos cadastrados hoje teriam o valor 1 e esse valor vai reduzindo a cada dia, até que, do dia 90 em diante, passa a ser 0. Esse valor é multiplicado pelo peso que você cadastrar para o critério **Data de lançamento** para compor a relevância.
 - **Mais vendidos:** números de pedidos do produto nos últimos 90 dias.
 - **Mais vendidos por receita:** lucro total adquirido pelo produto nos últimos 90 dias.
 - **Popularidade:** número de cliques de um produto nos últimos 90 dias.
 - **Promoção:** critério que verifica se há [Audiências de campanhas](https://help.vtex.com/pt/tutorial/overview-2--tutorials_326#audiencia-de-campanhas) ou [Promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N) vinculadas ao item para determinar se o produto será classificado como promoção.
-- **Score do Catálogo:** critério de desempate de ordenações baseado no valor cadastrado no produto. Leia mais sobre o campo no artigo [Como funciona o campo Score?](https://help.vtex.com/pt/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae).
-- **Variedade de grade disponível:** A relevância se dá a partir da porcentagem de SKUs disponíveis por produto. Exemplo: Num cenário em que _Produto A_ tem 3 SKus e 3 deles estão disponíveis, e _Produto B_ tem 5 SKUs 2 dele está disponível, o _Produto A_ se sobressai ao _Produto B_ pois a porcentagem de SKUs é maior.
+- **Pontuação do catálogo:** critério de desempate de ordenações baseado no valor do campo __Score__ cadastrado no __Catálogo__. Para essa finalidade de compor relevância, quanto maior o score, maior o peso, ou seja, o comportamento é decrescente: produtos com score mais alto são priorizados. Saiba mais sobre o campo e seu comportamento no guia [Como funciona o campo Score?](https://help.vtex.com/pt/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae).
+- **Variedade de matriz disponível:** A relevância se dá a partir da porcentagem de SKUs disponíveis por produto. Exemplo: Num cenário em que _Produto A_ tem 3 SKus e 3 deles estão disponíveis, e _Produto B_ tem 5 SKUs 2 dele está disponível, o _Produto A_ se sobressai ao _Produto B_ pois a porcentagem de SKUs é maior.
 
 O conjunto de distribuição de pesos e critérios gera uma pontuação para o produto, o que auxilia no seu posicionamento na ordenação do resultado da pesquisa.
 
@@ -40,62 +42,72 @@ O conjunto de distribuição de pesos e critérios gera uma pontuação para o p
   <p>Caso deseje utilizar critérios prioritários, recomendamos adicionar apenas um critério neste campo. Adicionar mais critérios compromete a ordenação do resultado de busca, visto que apenas o primeiro critério será considerado.</p>
 </div>
 
-Dessa forma, é possível adequar o comportamento do resultado de busca a uma estratégia específica. Por exemplo: uma loja de moda recebe novas coleções com frequência. O lojista opta por priorizar peças de lançamento a produtos promocionais. Ele configura a ferramenta da seguinte forma:
-
-**Critérios prioritários:**
-
-- Vazio
-
-**Composição de critérios:**
-
-- Popularidade: 7
-- Lançamento: 10
-- Mais vendidos: 6
-- Mais vendidos por receita: 6
-- Promoção: 0
-- Desconto (de / por): 0
-- Variedade de grade disponível: 10
-- Score do Catálogo: 0
-
-Caso esse lojista queira que o lançamento seja sempre a prioridade máxima, ele pode fazer a Regras de Relevância de duas formas:
-
-**Critérios prioritários:**
-
-- Lançamento
-
-**Composição de critérios:**
-
-- Popularidade: 7
-- Mais vendidos: 6
-- Mais vendidos por receita: 6
-- Promoção: 0
-- Desconto (de / por): 0
-- Variedade de grade disponível: 10
-- Score do Catálogo: 0
-
-**Critérios prioritários:**
-
-- Vazio
-
-**Composição de critérios:**
-
-- Popularidade: 0
-- Lançamento: 10
-- Mais vendidos: 0
-- Mais vendidos por receita: 0
-- Promoção: 0
-- Desconto (de / por): 0
-- Variedade de grade disponível: 0
-- Score do Catálogo: 0
-
-## Configurar Regra de Relevância
+Dessa forma, é possível adequar o comportamento do resultado de busca a uma estratégia específica.
+
+## Exemplo
+
+Uma loja de moda recebe novas coleções com frequência. O lojista opta por priorizar peças de lançamento a produtos promocionais. Ele configura a ferramenta da seguinte forma:
+
+> **Critérios prioritários:**
+> 
+> - Vazio
+> 
+> **Composição de critérios:**
+> 
+> - Popularidade: 7
+> - Data de lançamento: 10
+> - Mais vendidos: 6
+> - Mais vendidos por receita: 6
+> - Promoção: 0
+> - Desconto: 0
+> - Variedade de matriz disponível: 10
+> - Pontuação do catálogo: 0
+
+Caso esse lojista queira que o lançamento seja sempre a prioridade máxima, ele pode fazer as Regras de relevância de duas formas:
+
+> __Forma A:__
+> 
+> **Critérios prioritários:**
+> 
+> - Data de lançamento
+> 
+> **Composição de critérios:**
+> 
+> - Popularidade: 7
+> - Mais vendidos: 6
+> - Mais vendidos por receita: 6
+> - Promoção: 0
+> - Desconto: 0
+> - Variedade de matriz disponível: 10
+> - Pontuação do catálogo: 0
+
+> __Forma B:__
+> 
+> **Critérios prioritários:**
+> 
+> - Vazio
+> 
+> **Composição de critérios:**
+> 
+> - Popularidade: 0
+> - Data de lançamento: 10
+> - Mais vendidos: 0
+> - Mais vendidos por receita: 0
+> - Promoção: 0
+> - Desconto: 0
+> - Variedade de matriz disponível: 0
+> - Pontuação do catálogo: 0
+
+## Configurar Regra de relevância
+
+Para alterar a configuração de relevância, siga os passos abaixo.
+
+1. No Admin VTEX, clique no módulo de **Storefront** ou digite **Storefront** na barra de busca.
+2. Em **Intelligent Search**, clique em **Regras de relevância**.
+3. Escolha o critério cujo peso você deseja alterar.
+4. Clique nos ícones de seta para baixo <i class="fas fa-chevron-down"></i> ou seta para cima <i class="fas fa-chevron-up"></i> para definir o número desejado.
 
-Para alterar a configuração de Relevância, siga os passos abaixo.
+   Caso você queira mudar a posição de um critério de **Composição de critérios** para **Critérios prioritários**, arraste-o pelo ícone <i class="fas fa-grip-vertical"></i> para a área superior, conforme ilustrado na imagem abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso. 
 
-1. No Admin, clique no módulo de **Storefront**.
-2. Em **Intelligent Search**, clique em **Regras de Relevância**.
-3. Escolha o critério cujo peso você deseja alterar.
-4. Clique nos ícones <i class="fas fa-minus"></i> ou <i class="fas fa-plus"></i> para definir o número desejado. Caso você queira mudar a posição de um critério de **Composição de critérios** para **Critérios prioritários**, basta arrastá-lo pelo ícone <i class="fas fa-grip-vertical"></i> para a área superior, conforme demonstrado abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso. 
-![regras-relevancia-PT](https://images.ctfassets.net/alneenqid6w5/iZze1vchSYf9lLFJnfwiT/8a533cf40db35b72852fc2c3e1f2b5ec/regras-relevancia-PT.gif)
+    ![criterios-prioritarios-pt](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/43155e1e110f6ec8eaff5debf9d8a2df/criterios-prioritarios-pt.gif)
 5. Para finalizar, clique em `Salvar`.
-
diff --git a/docs/tracks/pt/reports-vtex-intelligent-search.md b/docs/tracks/pt/reports-vtex-intelligent-search.md
index 0a4f0a70e..c9e9d6742 100644
--- a/docs/tracks/pt/reports-vtex-intelligent-search.md
+++ b/docs/tracks/pt/reports-vtex-intelligent-search.md
@@ -79,8 +79,8 @@ Para exportar um relatório no formato CSV, você deve seguir os passos abaixo.
 
 O relatório CSV baixado apresenta duas tabelas. A primeira tabela, ilustrada abaixo, contém informações sobre termos pesquisados e as métricas de funil (da coluna **ProductsClick** até a coluna **ProductsSold**), caso essa opção tenha sido selecionada.
 
-![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
+![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
 
 A segunda tabela, ilustrada abaixo, mostra dados referentes ao período selecionado, exibindo a coluna Date, que informa a data da busca.
 
-![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
+![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
diff --git a/docs/tracks/pt/sale-confirmed.md b/docs/tracks/pt/sale-confirmed.md
index 863a8512f..019a4f94b 100644
--- a/docs/tracks/pt/sale-confirmed.md
+++ b/docs/tracks/pt/sale-confirmed.md
@@ -16,4 +16,4 @@ trackSlugPT: instore-usando-o-app
 
 O vendedor pode ver a tela __Venda confirmada__ com o resumo do pedido quando terminar uma venda, ou clicando em uma venda na página __Últimas vendas__, que pode ser acessada através do menu principal do VTEX Sales App. Na página __Últimas vendas__, é possível procurar a venda pelo número do pedido ou pelo nome do cliente.
 
-![order-placed-pt](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/8c3cc031c6f1b86c2f6cfbc31c53c1ec/order-placed-pt.png)
+![order-placed-pt](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/8c3cc031c6f1b86c2f6cfbc31c53c1ec/order-placed-pt.png)
diff --git a/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md b/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md
index 24416cb06..f0d924aa2 100644
--- a/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md
+++ b/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md
@@ -3,8 +3,8 @@ title: 'Entregas agendadas e capacidade de entrega'
 id: 5TuyqHRCCwYMaDv4r8rZdo
 status: PUBLISHED
 createdAt: 2022-03-08T18:30:20.114Z
-updatedAt: 2022-03-08T18:37:54.630Z
-publishedAt: 2022-03-08T18:37:54.630Z
+updatedAt: 2024-03-25T20:07:20.150Z
+publishedAt: 2024-03-25T20:07:20.150Z
 firstPublishedAt: 2022-03-08T18:37:54.630Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -16,7 +16,11 @@ trackSlugPT: logistica-101
 
 Uma loja VTEX pode oferecer entregas agendadas para seus clientes. Dessa forma, o cliente escolhe um dia de entrega específico para que a loja e a transportadora realizem a entrega do pedido no seu endereço. 
 
-Para disponibilizar a [entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) para os clientes, é preciso incluir janelas de entrega na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) da [transportadora ](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE)relacionada. Feito isso, os períodos e dias para entrega agendada ficarão disponíveis no checkout da sua loja. 
+Para disponibilizar a [entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) para os clientes, é preciso incluir janelas de entrega na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) da [transportadora ](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE)relacionada. Feito isso, os períodos e dias para entrega agendada ficarão disponíveis no checkout da sua loja.
+
+<div class="alert alert-warning">
+Para que a <a href="https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> e a <a href="https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidade de entrega</a> funcionem corretamente, você deve observar que:<p><ul><li>A soma {<a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID da política de envio} não pode exceder 60 caracteres.</li><li>Não se deve utilizar espaçamento no ID de <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">políticas de envio</a>.</li></ul></p>
+</div>
 
 É importante ressaltar que a disponibilidade das entregas agendadas está de acordo com o serviço que a transportadora contratada (cadastrada pela política de envio) oferece para sua loja. Para acompanhar a disponibilidade de janelas de entrega (ou períodos de envio) e a quantidade de itens/pedidos que ainda pode ser realizada em cada janela de entrega, confira a página de [Capacidade de entrega](https://help.vtex.com/pt/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
diff --git a/docs/tracks/pt/search-settings.md b/docs/tracks/pt/search-settings.md
index 98e63b5e0..9ea44356b 100644
--- a/docs/tracks/pt/search-settings.md
+++ b/docs/tracks/pt/search-settings.md
@@ -3,8 +3,8 @@ title: 'Configuração da busca'
 id: 5t75L6lYNwix93l41s1Yrx
 status: PUBLISHED
 createdAt: 2020-08-17T19:50:20.729Z
-updatedAt: 2023-03-30T19:37:35.404Z
-publishedAt: 2023-03-30T19:37:35.404Z
+updatedAt: 2024-04-25T17:06:18.124Z
+publishedAt: 2024-04-25T17:06:18.124Z
 firstPublishedAt: 2020-09-28T20:51:58.291Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -14,28 +14,39 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
-A Configuração da busca compreende todos os ajustes globais do VTEX Intelligent Search. 
-Ela consiste em duas seções: [Configurações gerais](#configuracoes-gerais) e [Configurações de filtros](#configuracoes-de-filtros).
+A página **Configuração da busca** compreende os ajustes globais do VTEX Intelligent Search. Para acessá-la no Admin VTEX, entre em **Configurações da loja > Intelligent Search > Configuração da busca**. Ela consiste em duas seções: [Configurações gerais](#configuracoes-gerais) e [Configurações de filtros](#configuracoes-de-filtros).
 
 ## Configurações gerais
-Configurações que lidam com o todo do VTEX Intelligent Search. Essa funcionalidade é composta pela opção:
-Use as especificações de SKU para exibir produtos individuais nos resultados da pesquisa. Esta opção define quais especificações vão separar os SKUs no resultado de busca.
 
-Digamos que você tenha um produto com as cores vermelho e azul como SKUs. 
-Se você selecionar o atributo "cor" neste campo, o resultado da pesquisa retornará dois produtos (um azul e outro vermelho) em vez de apenas um. Para adicionar uma especificação, clique na barra da funcionalidade e selecione a especificação desejada.
+As configurações gerais apresentam as opções a seguir, relacionadas a [especificações de produtos e de SKUs](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP):
 
-![Configurações gerais intelligent search v4](https://images.ctfassets.net/alneenqid6w5/41W9W07VVWur0rAxScJG9e/fd0509ae1632ea466789b374baca5030/configuracoes_gerais_pt.png)
+* **Use as especificações de SKU para exibir produtos individuais nos resultados da pesquisa**: define quais especificações vão separar os SKUs no resultado de busca.
 
-Para mais detalhes sobre essa configuração, acesse [este artigo](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE#).
+    Digamos que você tenha um produto com as cores vermelho e azul como SKUs. Se você selecionar o atributo "cor" neste campo, o resultado da pesquisa retornará dois produtos (um azul e outro vermelho) em vez de apenas um.
+
+    Para adicionar uma especificação, clique na barra da funcionalidade e selecione a especificação desejada.
+
+    Confira o guia [Separar SKUs por especificação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE) para mais detalhes sobre o comportamento dessa configuração. 
+
+* **Especificações pesquisáveis:** determina quais especificações terão valores pesquisáveis na busca.
+
+    Por exemplo, se uma camisa não tiver a cor no nome do produto ou do SKU, por padrão, o Intelligent Search não identifica esse atributo em uma pesquisa por "camisa azul", trazendo como resultado camisas de diversas cores. Contudo, se a especificação de cor estiver configurada como pesquisável, a busca consegue trazer camisas azuis nas primeiras posições.
 
 ## Configurações de filtros
-Configurações que englobam todos os aspectos de filtros. São eles:
 
-- **Ordenação dos filtros:** ordem em que os filtros serão exibidos na loja. Caso não tenha nenhum filtro selecionado na área, a ordem padrão é alfabética. Para adicionar um filtro, clique em Adicionar, selecione o filtro e clique em Salvar para concluir. Você pode alterar a ordenação arrastando o ícone de três barras em cada filtro para a posição desejada. Para deletar um filtro, basta clicar na lixeira <i class="fa-solid fa-trash-can"></i>.
+As configurações de filtros apresentam ajustes relacionados aos filtros exibidos para os clientes da sua loja durante a busca:
+
+![Configurações de filtros](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
+
+* **Ordenação dos filtros:** ordem em que os filtros serão exibidos na loja. Caso não tenha nenhum filtro selecionado na área, a ordem padrão é alfabética.
+
+    Para adicionar um filtro, clique em `Adicionar`, selecione o filtro e clique em `Salvar` para concluir.
+
+    Você pode alterar a ordenação arrastando o ícone de três barras <i class="fas fa-grip-vertical"></i> em cada filtro para a posição desejada.
 
-- **Ocultar filtros:** seleção que permite que certos filtros não sejam exibidos na loja. Para ocultar um filtro, basta selecionar seu nome.
+    Para deletar um filtro, clique no ícone de lixeira <i class="fas fa-trash-alt"></i>.
 
-![Configurações de filtros](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
+* **Ocultar filtros:** seleção que permite que determinados filtros não sejam exibidos na loja. Para ocultar um filtro, clique no campo e, em seguida, clique no nome do filtro. 
 
-Para mais informações, acesse [este artigo](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) mais detalhado sobre a funcionalidade de Filtros.
+    Para voltar a exibir um filtro, clique no X ao lado do nome dele. Se deseja voltar a exibir todos os filtros anteriormente ocultos, clique no X do lado direito do campo.
 
diff --git a/docs/tracks/pt/seeing-order-details.md b/docs/tracks/pt/seeing-order-details.md
index f8e219dbc..cc1979e51 100644
--- a/docs/tracks/pt/seeing-order-details.md
+++ b/docs/tracks/pt/seeing-order-details.md
@@ -3,8 +3,8 @@ title: 'Ver detalhes do pedido'
 id: 204AjAQseJe8RLUi8GAhiC
 status: PUBLISHED
 createdAt: 2019-11-14T15:12:10.952Z
-updatedAt: 2023-03-29T15:17:48.189Z
-publishedAt: 2023-03-29T15:17:48.189Z
+updatedAt: 2023-11-08T14:56:01.508Z
+publishedAt: 2023-11-08T14:56:01.508Z
 firstPublishedAt: 2019-11-18T12:20:18.851Z
 contentType: trackArticle
 productTeam: Post-purchase
@@ -22,9 +22,16 @@ Além disso, a busca oferece um filtro bastante flexível, que explicaremos em d
 
 Para entender a lista de pedidos em detalhes, consulte o artigo [Visão geral da lista de pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos--tutorials_200)
 
+Além de pesquisar pedidos em **Pedidos > Todos os pedidos**, você pode buscar pedidos a partir de qualquer página no Admin VTEX usando a barra de busca global no topo da página. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
+
 ## Vendo os detalhes de um pedido
 
-Ao clicar em um pedido, você é direcionado para a tela de __detalhes do pedido__, onde é possível consultar uma série de informações sobre o pedido e ainda executar algumas ações, tais como:
+Ao clicar em um pedido, você é direcionado para a tela de [detalhes do pedido](https://help.vtex.com/pt/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl), onde é possível consultar uma série de informações sobre o pedido e ainda executar algumas ações, tais como:
 - Reenviar o último e-mail para o cliente.
 - Cancelar manualmente o pedido.
 - Faturar os itens do pedido.
diff --git a/docs/tracks/pt/sending-product-data-to-dafiti.md b/docs/tracks/pt/sending-product-data-to-dafiti.md
index f2c915ec4..6a6c1e9f1 100644
--- a/docs/tracks/pt/sending-product-data-to-dafiti.md
+++ b/docs/tracks/pt/sending-product-data-to-dafiti.md
@@ -3,8 +3,8 @@ title: 'Envio dos produtos para a Dafiti'
 id: 3b8BZfB1BC8G8SCe0ao46m
 status: PUBLISHED
 createdAt: 2018-09-27T18:14:09.967Z
-updatedAt: 2022-10-14T12:56:30.575Z
-publishedAt: 2022-10-14T12:56:30.575Z
+updatedAt: 2023-08-24T20:14:58.159Z
+publishedAt: 2023-08-24T20:14:58.159Z
 firstPublishedAt: 2018-09-27T21:44:56.294Z
 contentType: trackArticle
 productTeam: Channels
@@ -31,7 +31,7 @@ Para cadastrar um produto na VTEX, é obrigatório que você vincule o produto a
 
 A Dafiti tem valores de referência para determinados atributos de produtos que devem ser levados em consideração durante o mapeamento de produtos.
 
-Para conhecer os valores aceitos pela Dafiti de acordo com cada coluna da planilha de mapeamento, é necessário fazer download da planilha de consulta da Dafiti para a categoria correspondente. Essa planilha será utilizada somente para fins de consulta.
+Para conhecer os valores aceitos pela Dafiti de acordo com cada coluna da planilha de mapeamento, é necessário fazer [download da planilha de consulta da Dafiti](https://drive.google.com/uc?export=download&id=1b2LOpNWDKtA-GCj8U_vHp3htlHAe-LI9) para a categoria correspondente. Essa planilha será utilizada somente para fins de consulta.
 
 - [Acessórios](https://drive.google.com/uc?export=download&id=19g-ycAnPDIefna0mU1IPMIO_cCwEIc_n)
 - [Beleza](https://drive.google.com/uc?export=download&id=17rH-YBklL8ut8ldkLs1ZaAib9ck7xN5c)
@@ -77,7 +77,7 @@ A aba __attributenames__ da planilha de mapeamento possui três colunas para ser
 - **VTEXAttributeName:** nome do campo de especificação na VTEX.
 - **DafitiAttributeName:** nome da variação / atributo na Dafiti.
     Para obter essas informações, verifique a planilha de consulta da Dafiti. Os atributos *Variation*, *Gender*, *Origin*, *ColorFamily*, *Color* e *Origincountry* são obrigatórios, considerando que:
-    - Clientes do Brasil precisam [cadastrar](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) em *Admin > Catálogo > Categorias* a especificação **País de origem** nos produtos que serão mapeados, para posteriormente preencher nas planilhas de mapeamento o novo atributo obrigatório **Origincountry**.
+    - Clientes do Brasil precisam [cadastrar](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) em *Admin > Catálogo > Categorias*, a especificação **País de origem** nos produtos que serão mapeados, para posteriormente preencher nas planilhas de mapeamento o novo atributo obrigatório **Origincountry**.
     - Quando preencher o atributo **ColorFamily** para um produto que possua mais de uma cor, recomendamos utilizar a cor predominante.
     - Os atributos **Color** e **ColorFamily** são distintos, sendo necessário o [cadastro de duas especificações](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) de produto *Cor* diferentes para o mapeamento correto dos produtos. Exemplo: Cor e Cor2.
 - **HasValueMapping:** indica se é necessário fazer uma conversão dos valores do atributo na aba *VTEXAttributeValue*. Quando os valores das especificações do seu produto na VTEX forem diferentes dos utilizados pela Dafiti, será preciso informar ao sistema que será feita uma conversão entre eles. Preencha essa coluna com `Y` (Yes), caso queira indicar que há uma conversão de valores para ser feita, ou com `N` (No) caso não tenha conversão.
@@ -139,3 +139,7 @@ Depois de mapear todos os atributos dos SKUs da sua loja, você deverá fazer up
 8. Clique em `Enviar arquivo`.
 
 Não tendo ocorrido nenhum erro com o envio, os produtos serão enviados para a Dafiti com seus respectivos atributos.
+
+<div class="alert alert-info">
+ A integração entre VTEX e Dafiti realiza automaticamente o redimensionamento das fotos dos produtos caso elas sejam superiores ao tamanho solicitado pela Dafiti(1000x1000).
+</div>
diff --git a/docs/tracks/pt/sending-products-to-amazon.md b/docs/tracks/pt/sending-products-to-amazon.md
index 1773504c5..d0f873eb4 100644
--- a/docs/tracks/pt/sending-products-to-amazon.md
+++ b/docs/tracks/pt/sending-products-to-amazon.md
@@ -1,10 +1,10 @@
 ---
-title: 'Envio de produtos para a Amazon'
+title: 'Envio e mapeamento de categorias dos produtos para a Amazon'
 id: 5xklf2wSdeztQh4iy5kJvD
 status: PUBLISHED
 createdAt: 2019-02-28T23:12:40.204Z
-updatedAt: 2023-03-16T19:46:44.241Z
-publishedAt: 2023-03-16T19:46:44.241Z
+updatedAt: 2023-10-18T19:47:04.829Z
+publishedAt: 2023-10-18T19:47:04.829Z
 firstPublishedAt: 2019-02-28T23:13:35.624Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,7 +14,58 @@ trackId: 6sgd4Pagy3wNsWKBvmIFrP
 trackSlugPT: integracao-com-a-amazon
 ---
 
-Feitas as configurações iniciais da integração, é possível enviar os produtos para o catálogo da Amazon. Para agilizar o processo de catalogação dos seus produtos na Amazon, permitindo que eles fiquem disponíveis para venda em menos tempo, você precisará realizar o mapeamento entre as características dos produtos na sua loja VTEX e as características dos mesmos produtos na sua loja Amazon. Para realizar o mapeamento, você precisará:
+Feitas as configurações iniciais da integração, é possível enviar os produtos para o catálogo da Amazon. Para habilitar o processo de catalogação dos produtos na Amazon, permitindo que eles fiquem disponíveis para venda em menos tempo, o seller precisará realizar o mapeamento entre as características dos produtos na sua loja VTEX e as características dos mesmos produtos na sua loja Amazon.  
+
+Para enviar os seus produtos para a Amazon, o seller deverá mapear as [categorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) e os [atributos dos produtos](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).  
+
+<div class="alert alert-info">
+Seus produtos precisam ter o <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a> e <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">Preço</a> configurados antes de enviá-los à Amazon.
+</div>  
+
+## Mapear Categorias  
+
+O processo de mapeamento pode ser realizado via Admin VTEX, ou via planilha, veja abaixo como executar em cada caso.  
+
+<div class="alert alert-danger">
+Ao realizar o mapeamento de uma categoria via Admin VTEX, o mapeamento daquela categoria realizado via planilha anteriormente, será sobrescrito e não poderá ser recuperado.
+</div>
+
+### Mapeamento via Admin VTEX (BETA)  
+
+Para acessar a página de mapeamento da Amazon, acesse __Marketplace > Marketplaces e Integrações > Amazon > Realizar Mapeamento.__  
+
+Na página de mapeamento da Amazon, será apresentado uma lista com as categorias da sua loja VTEX. O mapeamento das categorias permite que exista uma correspondência entre as categorias da sua loja e as categorias da Amazon. Dessa forma, os produtos enviados serão exibidos na categoria equivalente no marketplace.  
+
+Na página de mapeamento, use a barra de busca para pesquisar a categoria por nome. Além disso, a seção __Categorias da loja__ exibe lista das categorias da sua loja VTEX.  
+
+A lista de categorias da sua loja VTEX inclui o status de seu mapeamento por meio dos ícones:  
+
+| **Ícone** | **Status** | **Descrição** |
+|:---:|:---:|:---:|
+| ![mapeado mapper](//images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/43ace44c1e31c69157dc8ad5ec12529d/mapeado_mapper.jpg) | **Mapeado** | Indica que o mapeamento da categoria foi concluído. |
+| ![mapeamentoincompleto mapper](//images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/3cc09ec0f77d42f3277dd90e2f3167f9/mapeamentoincompleto_mapper.jpg) | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. |
+| ![erromapeamento mapper](//images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/136543f594ca05eec7be6bfc545cd10f/erromapeamento_mapper.jpg) | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto. Para solucionar esse problema basta refazer o mapeamento da categoria. |
+| ![não mapeado mapper](//images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/79bf968ab2d73471ee6e96b41b6a75d9/incompleto_mapper.jpg) | **Não mapeado** | Indica que a categoria não foi mapeada. |  
+
+Para realizar o mapeamento de categorias:  
+
+1. No Admin, acesse o módulo __Marketplace > Marketplaces e Integrações > Amazon > Realizar Mapeamento.__  
+2. Selecione a categoria que deseja mapear.  
+3. Selecione a categoria correspondente na Amazon do produto que deseja enviar.  
+4. Faça a correspondência dos atributos na janela lateral, conforme imagem abaixo:  
+
+![Mapper Amazon Atributos](//downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/7724063f4b499153958aadf44ee0a704/mapper_amazon_atributos.gif)
+
+5. Clique no botão __`Salvar Alterações`__.  
+
+<div class="alert alert-danger">
+Os campos sinalizados com o asterisco <strong>*</strong> são obrigatórios.  
+O preenchimento de um atributo pode desencadear novos campos obrigatórios que só ficarão visíveis na página <strong> Marketplace> Conexões> Produtos, </strong> após salvar o mapeamento.
+</div>  
+
+### Mapeamento via Planilha  
+
+Para realizar o mapeamento via planilha o seller deve seguir os passos abaixo:  
 
 1. [Realizar download do modelo de planilha de categorias gerais da Amazon.](#1-planilha-de-categorias-gerais-da-amazon) 
 2. [Realizar download do modelo de planilha de atributos obrigatórios da Amazon.](#2-planilha-de-atributos-obrigatorios-da-amazon)
@@ -23,13 +74,13 @@ Feitas as configurações iniciais da integração, é possível enviar os produ
 5. [Preencher a planilha de mapeamento.](#5-preenchimento-da-planilha-de-mapeamento)
 6. [Fazer o upload da planilha de mapeamento](#6-upload-da-planilha-de-mapeamento)
 
-## 1. Planilha de categorias gerais da Amazon
+#### 1. Planilha de categorias gerais da Amazon
 
 A Amazon utiliza a [categoria global](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188) cadastrada na VTEX para fazer o mapeamento dos produtos, por isso, é importante que seja feita de maneira correta a equivalência entre a categoria global da VTEX e as categorias gerais na Amazon.
 
 Para conhecer as categorias aceitas pela Amazon é necessário fazer o download da [Planilha de categorias gerais da Amazon.xlsx](https://drive.google.com/uc?export=download&id=1GC5Guic4k_8C2ZnEGQUoDqT2cdJzp-Ti), essa planilha será utilizada somente para fins de consulta.
 
-## 2. Planilha de atributos obrigatórios da Amazon
+#### 2. Planilha de atributos obrigatórios da Amazon
 
 A Amazon tem valores de referência para determinadas características de produtos que devem ser considerads no mapeamento dos produtos. 
 
@@ -37,14 +88,14 @@ Para conhecer os valores aceitos pela Amazon de acordo com cada coluna da planil
 
 Nesta planilha, cada aba corresponde a uma categoria global na Amazon. Ao clicar em uma aba, a planilha apresenta as subcategorias presentes dentro da categoria global selecionada.
 
-## 3. Pré-configurações no Catálogo
+#### 3. Pré-configurações no Catálogo
 
 Antes de mapear os produtos da sua loja, é necessário configurar os seguintes [campos do produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) que você deseja enviar para a Amazon: 
 
 - [Categoria global](#categoria-global)
 - [EAN](#ean)
 
-### Categoria global
+#### Categoria global
 
 Para identificar os seus produtos e relacioná-los com o catálogo da Amazon, a integração utiliza as [categorias globais](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188) da VTEX. Durante o processo de mapeamento, o sistema faz equivalência de cada categoria global da VTEX com as [categorias gerais](#planilha-de-categorias-gerais-da-amazon) da Amazon e, através disso, encaminhamos os produtos para as categorias corretas e com os atributos de produto necessários. 
 
@@ -79,7 +130,7 @@ Seguindo o exemplo anterior, filtre as colunas B, C e D da árvore de **Saúde e
 
 Agora que você encontrou a categoria geral da Amazon, volte ao Admin para [configurar a categoria global](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188) da VTEX de acordo com a categoria geral da Amazon.
 
-### EAN
+#### EAN
 
 Como o catálogo da Amazon exige que os produtos enviados tenham o [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube), para que eles possam juntar os produtos de todos os sellers. Portanto, certifique-se que seus produtos estão com EANs válidos cadastrados antes de configurar a integração.
 
@@ -95,7 +146,7 @@ Para estar  elegível para solicitar isenção de EAN, você deve estar dentro d
 - Vendas de produtos que não tem EAN. Exemplo: Acessórios para celular.
 - Kits/combos de produtos. Exemplo: Camisas + Cinto.
 
-##### Dicas para envio de produtos com isenção de EAN
+#### Dicas para envio de produtos com isenção de EAN
 
 Após a solicitação e aprovação da isenção de EAN, com a definição de [Categoria](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1?&utm_source=autocomplete) e [Marca](https://help.vtex.com/pt/tutorial/cadastrando-marcas--tutorials_1414),  o produto passa a ter a necessidade de ser enviado via integração exatamente com as mesmas informações aprovadas na Amazon, são elas: 
 - Nome da marca
@@ -112,13 +163,13 @@ Se você está vendendo produtos de uma marca ou fabricação própria a Amazon
 
 Caso você queira vender um produto que está associado a outro proprietário (criação de um novo ASIN), é importante se atentar ao processo de [Liberação do Produto para a Marca](https://sellercentral.amazon.com/gp/help/help.html/?itemID=G201844590&ref_=xx_G201844590_a_r0_cont_sgsearch).
 
-## 4. Planilha de mapeamento
+#### 4. Planilha de mapeamento
 
 Nessa etapa você precisará categorizar as variações e os atributos dos produtos e enviá-los para o marketplace. O envio dessas informações é feito por meio da planilha de mapeamento, que faz a equivalência entre as categorias, as variações e os atributos da sua loja e os padrões adotados pela Amazon.
 
 Faça o download do arquivo da [Planilha de Mapeamento da Amazon.xlsx](https://assets.ctfassets.net/alneenqid6w5/4mNcXF4yS3160xUGgCZVQC/caf8cfc88b316bc9878000264e16e30b/Planilha_modelo.xlsx) e utilize o arquivo baixado como modelo para preenchimento. Esta é a planilha que será preenchida e enviada posteriormente para a Amazon.
 
-## 5. Preenchimento da planilha de mapeamento
+#### 5. Preenchimento da planilha de mapeamento
 
 A planilha possui as seguintes colunas:
 
@@ -152,10 +203,10 @@ Para cada produto, siga os passos a seguir:
 7. Preencha a coluna **AmazonValue** com os valores aceitos pela Amazon. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`
 
 <div class="alert alert-warning">
-Em alguns casos, os valores de <b>VariationTheme</b> podem ser parecidos. Há categorias em que o <b>VariationTheme</b> pode ser: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, enquanto há outras categorias em que pode ser: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. A diferença está na ordem, em <i>SizeColor</i>, as caixas de seleção na página do produto estarão ordenadas por tamanho e cor, enquanto em <i>ColorSize</I> estarão ordenadas por cor e tamanho. Esteja atento aos valores válidos de cada categoria que será mapeada. 
+Em alguns casos, os valores de <strong>VariationTheme</strong> podem ser parecidos. Há categorias em que o <strong>VariationTheme</strong> pode ser: <em>SizeColor</em>, <em>Color</em> e <em>Size</em>, enquanto há outras categorias em que pode ser: <em>ColorSize</em>, <em>Color</em> e <em>Size</em>. A diferença está na ordem, em <em>SizeColor</em>, as caixas de seleção na página do produto estarão ordenadas por tamanho e cor, enquanto em <em>ColorSize</em> estarão ordenadas por cor e tamanho. Esteja atento aos valores válidos de cada categoria que será mapeada. 
 </div>
 
-### Exemplo de preenchimento 
+##### Exemplo de preenchimento 
 
 | CategoryID | VariationTheme | Type | VTEXSpecification | AmazonSpecification | VTEXValue | AmazonValue |
 | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
@@ -163,7 +214,7 @@ Em alguns casos, os valores de <b>VariationTheme</b> podem ser parecidos. Há ca
 | 212 | SizeColor | Variation | Tamanho | Size | M | M |
 | 212 | SizeColor | Variation | Tamanho | Size | G | L |
 
-## 6. Upload da planilha de mapeamento
+#### 6. Upload da planilha de mapeamento
 
 Após de preencher a planilha, acesse Integrações no menu do Admin:
 
@@ -178,17 +229,3 @@ Após de preencher a planilha, acesse Integrações no menu do Admin:
 
 Não tendo ocorrido nenhum erro com o envio, os produtos serão enviados para a Amazon com seus respectivos atributos.  
 
-## 7. Matching automático
-
-Toda vez que um [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) com [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) cadastrado é enviado para a Amazon, o marketplace realiza um processo chamado *matching*, que consiste em unificar anúncios de um mesmo produto através do seu EAN. 
-
-O EAN cadastrado na VTEX é utilizado para fazer a equivalência com os [ASINs](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (Amazon Standard Identification Number) correspondentes na Amazon. Esse *matching* acontece automaticamente, entretanto, ele pode não ocorrer corretamente.  
-
-<div class= "alert alert-info">
-É recomendado que o seller revise todos os produtos que estiverem com status `Processado com aviso`, aqueles produtos que não tiverem EAN e ASIN correspondentes, precisarão de um novo envio.  
-</div>
-
-Para filtrar os produtos que não foram processados corretamente, siga os passos abaixo:
-
-1. No Admin VTEX, acesse __Marketplace > Integrações > Produtos__.
-2. Filtre os produtos com o campo Afiliado preenchido com Amazon e o campo __Status__ com o valor Aviso. Você visualizará os produtos que não foram processados com EAN e ASIN equivalentes e poderá efetuar um novo envio.
diff --git a/docs/tracks/pt/sending-products-to-facebook.md b/docs/tracks/pt/sending-products-to-facebook.md
index b81a98d29..f1b86d4a9 100644
--- a/docs/tracks/pt/sending-products-to-facebook.md
+++ b/docs/tracks/pt/sending-products-to-facebook.md
@@ -3,8 +3,8 @@ title: 'Envio de produtos para o Facebook'
 id: 41qzoa7TWIYTyIhABHdgzI
 status: PUBLISHED
 createdAt: 2021-02-08T19:45:07.202Z
-updatedAt: 2021-07-09T22:04:10.786Z
-publishedAt: 2021-07-09T22:04:10.786Z
+updatedAt: 2024-01-22T15:03:37.861Z
+publishedAt: 2024-01-22T15:03:37.861Z
 firstPublishedAt: 2021-02-08T20:10:14.152Z
 contentType: trackArticle
 productTeam: Channels
@@ -89,12 +89,12 @@ Veja um exemplo de planilha preenchida:
 O terceiro e último passo para concluir o mapeamento é fazer o upload da planilha preenchida. Esta ação é realizada no Admin, através dos seguintes passos:
 
 1. Acesse o Admin.
-2. No módulo _MARKETPLACE_, clique em `Integrações`.
-3. Selecione a opção `Configurações`.
-4. No card do Facebook, clique na <i class="fas fa-cog"></i>
-5. Escolha a opção `Upload de mapeamento`.
-6. Clique em `Escolher um arquivo`.
-7. Selecione a planilha de mapeamento preenchida.
-8. Clique em `Enviar arquivo`.
+2. No módulo Marketplace, clique em Marketplace e integrações.
+4. Procure Facebook na barra de busca.
+5. Clique em `Editar`
+6. Escolha a opção `Mapeamento de categorias`.
+7. Clique em `Escolher um arquivo`.
+8. Selecione a planilha de mapeamento preenchida.
+9. Clique em `Enviar arquivo`.
 
 Feito isso, você terá concluído o mapeamento de categorias e atributos dos seus produtos. O tempo para isso se refletir no Facebook vai depender da extensão do seu catálogo.
diff --git a/docs/tracks/pt/sending-products-to-via.md b/docs/tracks/pt/sending-products-to-via.md
index 3f9f54481..3f0c8a38f 100644
--- a/docs/tracks/pt/sending-products-to-via.md
+++ b/docs/tracks/pt/sending-products-to-via.md
@@ -1,10 +1,10 @@
 ---
-title: 'Envio de produtos para a Via Marketplace'
+title: 'Envio de produtos para a Casas Bahia Marketplace'
 id: 5QVZFYNfuRIQKdq34MbTxz
 status: PUBLISHED
 createdAt: 2020-03-30T18:51:30.236Z
-updatedAt: 2022-01-24T19:39:58.658Z
-publishedAt: 2022-01-24T19:39:58.658Z
+updatedAt: 2024-07-26T19:30:35.060Z
+publishedAt: 2024-07-26T19:30:35.060Z
 firstPublishedAt: 2020-03-30T23:08:05.849Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,50 +14,50 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-integracao-da-via-varejo
 ---
 
-Após cadastrar sua loja ao conector da Via, será possível enviar os produtos para o catálogo da Via. Para enviar seus produtos, você precisará realizar o mapeamento entre as características dos produtos na sua loja VTEX e as características dos mesmos produtos na sua loja Via. 
+Após cadastrar sua loja ao conector da Casas Bahia Marketplace, será possível enviar os produtos para o catálogo da Casas Bahia Marketplace. Para enviar seus produtos, você precisará realizar o mapeamento entre as características dos produtos na sua loja VTEX e as características dos mesmos produtos na sua loja Casas Bahia Marketplace. 
 
 Para fazer o mapeamento, você seguir os seguintes passos:
 
-1. [Fazer download do modelo de planilha de referência da Via](#1-planilha-de-referencia-da-via)
+1. [Fazer download do modelo de planilha de referência da Casas Bahia Marketplace](#1-planilha-de-referencia-da-casas-bahia-marketplace)
 2. [Fazer download do modelo de planilha de mapeamento](#2-planilha-de-mapeamento)
 3. [Preencher a planilha de mapeamento](#3-preenchimento-da-planilha-de-mapeamento)
 4. [Fazer upload da planilha de mapeamento](#4-upload-da-planilha-de-mapeamento)
 
-## 1. Planilha de referência da Via
+## 1. Planilha de referência da Casas Bahia Marketplace
 
-A Via Marketplace tem valores de referência para determinados atributos de produtos que devem ser levados em consideração durante o mapeamento de produtos. 
+A Casas Bahia Marketplace tem valores de referência para determinados atributos de produtos que devem ser levados em consideração durante o mapeamento de produtos. 
 
-Para conhecer os valores aceitos pela Via é necessário fazer download da [Planilha de Referência da Via.csv](https://s3.amazonaws.com/vtex-channels/viavarejointegration/categories/viavarejo-categories.csv). Essa planilha será utilizada somente para fins de consulta.
+Para conhecer os valores aceitos pela Casas Bahia Marketplace é necessário fazer download da [Planilha de Referência da Casas Bahia Marketplace.csv](https://s3.amazonaws.com/vtex-channels/viavarejointegration/categories/viavarejo-categories.csv). Essa planilha será utilizada somente para fins de consulta.
 
 ## 2. Planilha de mapeamento
 
-Nessa etapa você precisará mapear os atributos dos produtos e enviá-los para o marketplace. O envio dessas informações é feito por meio da planilha de mapeamento, ela tem o objetivo de indicar à Via Marketplace a correspondência entre os valores cadastrados na sua loja e os valores aceitos na Via.
+Nessa etapa você precisará mapear os atributos dos produtos e enviá-los para o marketplace. O envio dessas informações é feito por meio da planilha de mapeamento, ela tem o objetivo de indicar à Casas Bahia Marketplace a correspondência entre os valores cadastrados na sua loja e os valores aceitos na Casas Bahia Marketplace.
 
-Faça o download do arquivo da [Planilha de Mapeamento da Via.xlsx](https://drive.google.com/uc?export=download&id=1x1xwYIM40kx5J-Km_lYixJUJ5w445AEi) e utilize o arquivo baixado como modelo para preenchimento. Esta é a planilha que será preenchida e enviada posteriormente para a Via.
+Faça o download do arquivo da [Planilha de Mapeamento da Casas Bahia Marketplace.xlsx](https://vtex-channels.s3.amazonaws.com/viavarejointegration/categories/vvj_map.xlsx) e utilize o arquivo baixado como modelo para preenchimento. Esta é a planilha que será preenchida e enviada posteriormente para a Casas Bahia Marketplace.
 
 ## 3. Preenchimento da planilha de mapeamento
 
-A planilha de mapeamento da Via Varejo contém as seguintes colunas:
+A planilha de mapeamento da Casas Bahia Marketplace Varejo contém as seguintes colunas:
 
-| Nome da coluna           | Descrição                                  |
-| ----------               | ----------                                 |
-| VTEX Category Id         | ID da Categoria na VTEX                    |
-| VV Category Id           | ID da Categoria na Via Marketplace              |
-| Is Variation             | Indica se especificação é variação (`true`) ou atributo (`false`)                                                        |
-| VTEX Specification Name  | Nome do campo de especificação na VTEX     |
-| VV Specification Name    | Nome da variação / atributo na Via Marketplace  |
-| VTEX Specification Value | Valor do campo de especificação na VTEX    |
-| VV Specification Value   | Nome da variação / atributo na Via Marketplace  |
+| Nome da coluna | Descrição  |
+| :-------:| :--------:|
+| VTEX Category Id| ID da Categoria na VTEX |
+| VV Category Id | ID da Categoria na Casas Bahia Marketplace  |
+| Is Variation | Indica se especificação é variação (`true`) ou atributo (`false`) |
+| VTEX Specification Name  | Nome do campo de especificação na VTEX |
+| VV Specification Name  | Nome da variação / atributo na Casas Bahia Marketplace  |
+| VTEX Specification Value | Valor do campo de especificação na VTEX |
+| VV Specification Value | Nome da variação / atributo na Casas Bahia Marketplace |
 
 Para cada produto, siga os passos a seguir: 
 
 1. Preencha a coluna **VTEX Category Id** com o ID da Categoria na VTEX. Você consegue encontrá-lo ao lado do nome da Categoria, ao navegar pela árvore de categorias disponível em **Produtos > Catálogo > Categorias**.
-2. Preencha a coluna **VV Category Id** com o ID da Categoria na Via. Você deve procurar a melhor correspondência possível na [Planilha de Referência da Via](#1-planilha-de-referencia-da-via).
+2. Preencha a coluna **VV Category Id** com o ID da Categoria na Casas Bahia Marketplace. Você deve procurar a melhor correspondência possível na [Planilha de Referência da Casas Bahia Marketplace](#1-planilha-de-referencia-da-casas-bahia-marketplace).
 3. Preencha a coluna **Is variation** com o valor `true`, quando se tratar da variação do produto, ou o valor `false`, quando se tratar da especificação do produto.
 4. Preencha a coluna **VTEX Specification Name** com o nome das especificações do produto na VTEX.
-5. Preencha a coluna **VV Specification Name** com o nome dos atributos do produto na Via.
+5. Preencha a coluna **VV Specification Name** com o nome dos atributos do produto na Casas Bahia Marketplace.
 6. Preencha a coluna **VTEX Specification Value** com o valor das especificações do produto na VTEX.
-7. Preencha a coluna **VV Specification Value** com o valor do atributo do produto na Via.
+7. Preencha a coluna **VV Specification Value** com o valor do atributo do produto naCasas Bahia Marketplace.
 8. Repita os passos acima.
 9. Salve a planilha em seu computador.
 
@@ -68,18 +68,18 @@ Para cada produto, siga os passos a seguir:
 Neste exemplo, faremos o mapeamento de uma categoria de Freezer.
 
 **VTEX:** Eletrodomésticos > Freezer > Vertical (157)
-**Via:** Eletrodomésticos > Freezer > Freezer Vertical (3391)
+**Casas Bahia Marketplace:** Eletrodomésticos > Freezer > Freezer Vertical (3391)
 
-Na planilha de referência da Via, busque por `Freezer` na coluna **Nome da categoria**, você encontrará o ID da categoria de *Freezer Vertical* na Via.
+Na planilha de referência da Casas Bahia Marketplace, busque por `Freezer` na coluna **Nome da categoria**, você encontrará o ID da categoria de *Freezer Vertical* na Via.
 
 | VTEX Category Id | VV Category Id | Is Variation | VTEX Specification Name | VV Specification Name | VTEX Specification Value | VV Specification Value |
-| ---------- | ---------- | ---------- | ----------| ----------| ---------- | ---------- |
-| 157 | 3391 |                  |                         |                       |                          |                        |
+| ---- | ---- | ----| -----| ----|----|----|
+| 157 | 3391 |    |    |     |     |     |
 
-Ainda na planilha de referência da Via, busque pelos atributos obrigatórios da categoria `Freezer Vertical` observando a coluna **É Obrigatório**. Você encontrará o atributo `Voltagem` como atributo obrigatório. 
+Ainda na planilha de referência da Casas Bahia Marketplace, busque pelos atributos obrigatórios da categoria `Freezer Vertical` observando a coluna **É Obrigatório**. Você encontrará o atributo `Voltagem` como atributo obrigatório. 
 
 | VTEX Category Id | VV Category Id | Is Variation | VTEX Specification Name | VV Specification Name | VTEX Specification Value | VV Specification Value |
-| ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
+| ---- | ----- | ----- | ----- | ---- | ---- | ---- |
 | 157| 3391 | true | Voltagem | Voltagem | 127 volts | 110V |
 | 157 | 3391 | true | Voltagem | Voltagem | 220 volts | 220V |
 
@@ -88,7 +88,7 @@ Ainda é possível mapear atributos não obrigatórios para serem usados no enri
 As especificações `Cor` e `Capacidade total` serão mapeadas duas vezes, porque o mapeamento como variação é o que habilita a seleção de cor e capacidade total do produto na página do anúncio. Já o mapeamento como atributo é o que faz com que a cor e a capacidade total sejam listados nas características e especificações técnicas.
 
 | VTEX Category Id | VV Category Id | Is Variation | VTEX Specification Name | VV Specification Name | VTEX Specification Value | VV Specification Value |
-| ---------- | ---------- | ---------- | ---------- | ---------- | ---------- | ---------- |
+| ----- | ----- | ----- | -----| ---- | ----- | ----- |
 | 157| 3391 | true | Voltagem | Voltagem | 127 volts | 110V |
 | 157 | 3391 | true | Voltagem | Voltagem | 220 volts | 220V |
 | 157| 3391 | true | Capacidade total | Capacidade (Litros)| 246l | 246L |
@@ -111,4 +111,4 @@ Depois de preencher a planilha de mapeamento, faça o seu upload:
 7. Selecione a planilha de mapeamento preenchida.
 8. Clique no botão `Enviar arquivo`
 
-Não tendo ocorrido nenhum erro com o envio, os produtos serão enviados para a Via com seus respectivos atributos.
+Não tendo ocorrido nenhum erro com o envio, os produtos serão enviados para a Casas Bahia Marketplace com seus respectivos atributos.
diff --git a/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md b/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md
index cfc748593..f2226b64c 100644
--- a/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md
+++ b/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md
@@ -26,31 +26,31 @@ Você pode encontrar links para download em: [http://instore.vtex.com/#download]
 
 Ao abrir o inStore pela primeira vez, você precisará digitar a conta VTEX onde deseja configurar o inStore e clicar em __Confirmar__.
 
-![01 inStore selecione conta](https://images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
+![01 inStore selecione conta](//images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
 
 Ao identificar que o inStore não está configurado nessa conta, você será redirecionado para a VTEX App Store onde precisará efetuar o login com sua conta de admin na VTEX.
 
 Após o login, você conseguirá instalar o inStore na sua conta.
 
-![02 inStore instalar](https://images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
+![02 inStore instalar](//images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
 
 Um formulário de configuração será exibido, sendo a primeira etapa a informação de endereço.
 
-![03 inStore endereco](https://images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
+![03 inStore endereco](//images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
 
 Depois você deve definir um email e senha a serem utilizados como login de vendedor.
 
 > __IMPORTANTE__: esse e-mail __NÃO__ pode ser o mesmo utilizado na plataforma VTEX, isso porque o seu e-mail de admin possui permissões que um vendedor não deveria ter, por isso é necessário utilizar algum outro e-mail sem privilégios na plataforma.
 
-![04 inStore registre vendedor](https://images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
+![04 inStore registre vendedor](//images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
 
 Depois de configurar o vendedor e confirmar o código de ativação recebido por e-mail, você poderá definir as formas de pagamento.
 
-![05 inStore configure pagamento](https://images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
+![05 inStore configure pagamento](//images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
 
 Caso ainda não tenha contrato com uma adquirente, você pode manter apenas a opção __Dinheiro__ ativa. Ao clicar em __Confirmar__ verá a tela de sucesso.
 
-![06 inStore sucesso](https://images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
+![06 inStore sucesso](//images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
 
 Agora basta voltar para o aplicativo, logar com as credenciais de vendedor e começar a vender!
 
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
index 7f5068ca0..b9a03dfb5 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
@@ -18,11 +18,11 @@ O primeiro passo de qualquer integração é definir a política comercial que s
 
 Uma das funções da política comercial é fazer uma diferenciação de __catálogo__ e/ou __logística__ entre os diferentes canais de venda da loja. Ou seja, uma nova política comercial só é necessária quando um desses fatores for diferente entre os canais de venda.
 
-![marketplace-v2](https://images.ctfassets.net/alneenqid6w5/6wy87Eq81O6ksOoq4EsAyG/29f6801d23163b8bef6d6fa30a68b4f1/marketplace-v2.png)
+![marketplace-v2](//images.ctfassets.net/alneenqid6w5/6wy87Eq81O6ksOoq4EsAyG/29f6801d23163b8bef6d6fa30a68b4f1/marketplace-v2.png)
 
 Uma única política comercial pode ser compartilhada por mais de um marketplace ou entre loja principal e marketplace. Para isso, basta que se use o mesmo ID de política comercial nas [configurações](/pt/tutorial/integrando-com-marketplace). Fazendo isso, o mesmo catálogo e a mesma logística vão ser usados para as lojas ou canais que estão configurados com a mesma política comercial.
 
-![marketplace-politica-compartilhada](https://images.ctfassets.net/alneenqid6w5/6ur6jWd8hG4wew4GO4YWS6/60624ed33a2b4765c4f8de3d064526f3/marketplace-politica-compartilhada.png)
+![marketplace-politica-compartilhada](//images.ctfassets.net/alneenqid6w5/6ur6jWd8hG4wew4GO4YWS6/60624ed33a2b4765c4f8de3d064526f3/marketplace-politica-compartilhada.png)
 
 A partir desse entendimento, avalie se é necessário configurar uma nova política comercial na sua loja. Se a resposta for sim, siga as orientações [deste artigo](https://help.vtex.com/pt/faq/como-contratar-nova-politica-comercial--frequentlyAskedQuestions_700) antes de passar para a próxima etapa de configuração. Caso sua política comercial já atenda às condições que precisa para a integração com o marketplace, siga as próximas instruções.
 
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-skyhub-b2w.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
index d1acdbcb0..cb08e54ef 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-skyhub-b2w.md
@@ -3,8 +3,8 @@ title: 'Configurar política comercial para marketplace'
 id: 4rbhQuuWlUvOp4oOeBlbiC
 status: PUBLISHED
 createdAt: 2021-02-22T19:46:30.515Z
-updatedAt: 2022-12-08T20:34:38.911Z
-publishedAt: 2022-12-08T20:34:38.911Z
+updatedAt: 2023-10-19T14:10:13.534Z
+publishedAt: 2023-10-19T14:10:13.534Z
 firstPublishedAt: 2021-02-22T21:40:49.337Z
 contentType: trackArticle
 productTeam: Channels
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-viavarejo.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-viavarejo.md
index 2906490f1..ee0a0d6c2 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-viavarejo.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-viavarejo.md
@@ -3,8 +3,8 @@ title: 'Configurar política comercial '
 id: D63aTOOoQXd6NYq1f5rhc
 status: PUBLISHED
 createdAt: 2021-02-22T16:52:54.100Z
-updatedAt: 2022-12-08T20:34:07.143Z
-publishedAt: 2022-12-08T20:34:07.143Z
+updatedAt: 2023-11-30T21:09:43.958Z
+publishedAt: 2023-11-30T21:09:43.958Z
 firstPublishedAt: 2021-02-22T21:38:33.617Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,16 +14,16 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-integracao-da-viavarejo
 ---
 
-Na VTEX, uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio em um canal de venda. Ou seja, é por meio da política comercial que você define as configurações que serão aplicadas aos seus produtos na Via.
+Na VTEX, uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio em um canal de venda. Ou seja, é por meio da política comercial que você define as configurações que serão aplicadas aos seus produtos na Casas Bahia Marketplace.
 
-Se as mesmas configurações de catálogo, preço e estratégia de envio da sua loja VTEX forem utilizadas na Via, não é preciso [criar uma política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) nova, porque uma mesma política comercial pode ser usada para diferentes canais de venda.
+Se as mesmas configurações de catálogo, preço e estratégia de envio da sua loja VTEX forem utilizadas na Casas Bahia Marketplace, não é preciso [criar uma política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) nova, porque uma mesma política comercial pode ser usada para diferentes canais de venda.
 
 Só será necessário [configurar uma política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404) específica, se você tiver algum dos seguintes objetivos:
 
-- Oferecer na Via uma seleção diferente de produtos.
+- Oferecer na Casas Bahia Marketplace uma seleção diferente de produtos.
 - Disponibilizar uma quantidade de estoque diferente.
-- Enviar preços diferentes para a Via.
-- Enviar promoções diferentes para a Via.
+- Enviar preços diferentes para a Casas Bahia Marketplace.
+- Enviar promoções diferentes para a Casas Bahia Marketplace.
 - Configurar outras condições de pagamento.
 - Definir uma estratégia de envio diferente.
 
diff --git a/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
index 16ce79347..65774ff45 100644
--- a/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
@@ -16,7 +16,7 @@ trackSlugPT:
 
 Este artigo tem como objetivo explicar como a app do inStore configura o AppLinking para as ações de `payment` e `payment-reversal` com as apps dos adquirentes.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuração
 
diff --git a/docs/tracks/pt/setting-up-credit-direct-sale.md b/docs/tracks/pt/setting-up-credit-direct-sale.md
index adcfaa7b3..ca66d1e19 100644
--- a/docs/tracks/pt/setting-up-credit-direct-sale.md
+++ b/docs/tracks/pt/setting-up-credit-direct-sale.md
@@ -3,8 +3,8 @@ title: 'Configurar Venda Direta - Crédito'
 id: 5rSTgGeCqEN7c9LmFbfqA
 status: PUBLISHED
 createdAt: 2021-09-27T20:09:51.763Z
-updatedAt: 2023-05-31T14:45:21.350Z
-publishedAt: 2023-05-31T14:45:21.350Z
+updatedAt: 2023-07-19T19:35:38.275Z
+publishedAt: 2023-07-19T19:35:38.275Z
 firstPublishedAt: 2021-09-27T20:35:59.233Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/pt/setting-up-payment-methods-for-instore.md b/docs/tracks/pt/setting-up-payment-methods-for-instore.md
index 304702128..14698e1d0 100644
--- a/docs/tracks/pt/setting-up-payment-methods-for-instore.md
+++ b/docs/tracks/pt/setting-up-payment-methods-for-instore.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar métodos de pagamento para o inStore'
+title: 'Configurar métodos de pagamento para o VTEX Sales App'
 id: 2liigRors32hzqBNs2M1Oa
 status: PUBLISHED
 createdAt: 2020-06-28T14:54:46.020Z
-updatedAt: 2023-05-31T14:44:58.176Z
-publishedAt: 2023-05-31T14:44:58.176Z
+updatedAt: 2023-08-28T11:55:43.015Z
+publishedAt: 2023-08-28T11:55:43.015Z
 firstPublishedAt: 2020-06-28T15:17:02.889Z
 contentType: trackArticle
 productTeam: Shopping
diff --git a/docs/tracks/pt/setting-up-the-app.md b/docs/tracks/pt/setting-up-the-app.md
index 663fbfef8..6c9cfbe46 100644
--- a/docs/tracks/pt/setting-up-the-app.md
+++ b/docs/tracks/pt/setting-up-the-app.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar Customer Credit '
+title: 'Configurando o Customer Credit '
 id: 21ok0GBwmcIeaY2IukYMOg
 status: PUBLISHED
 createdAt: 2018-11-07T17:11:22.823Z
-updatedAt: 2022-01-07T13:30:23.058Z
-publishedAt: 2022-01-07T13:30:23.058Z
+updatedAt: 2024-02-08T18:03:14.738Z
+publishedAt: 2024-02-08T18:03:14.738Z
 firstPublishedAt: 2018-11-07T17:23:16.520Z
 contentType: trackArticle
 productTeam: Financial
@@ -14,102 +14,101 @@ trackId: 1hCRg21lXYy2seOKgqQ2CC
 trackSlugPT: customer-credit-como-comecar
 ---
 
-## Configurações do primeiro acesso
+Após instalar a app do Customer Credit, você deve realizar as seguintes configurações:
 
-Agora vamos configurar o Customer Credit. 
+- [Primeiro acesso](#configuracoes-do-primeiro-acesso)
+- [App](#configuracoes-da-app) 
+- [Condições de pagamento](#condicoes-de-pagamento)
 
-O primeiro passo é acessar a página de configurações do aplicativo no Admin. 
+## Configurações do primeiro acesso
 
-Feito isso, logo no início da tela, você verá três comandos dentro do box “Pendente”.
+Para realizar as configurações iniciais do Customer Credit, siga os passos abaixo:
 
-1. __“Ativar emails transacionais no Message Center”__: instala os templates de e-mails transacionais relativos ao Customer Credit no Message Center. Para acioná-lo, clique no botão “Ativar”;
-2. __“Configurar condições de pagamento do checkout”__: define as regras de prazo e parcelamento da loja. Para acioná-lo, clique no botão “Configurar”;
-3. __“AppKey e appToken da afiliação não definidos”__:  o Customer Credit com uma forma de pagamento. Para acioná-lo, clique no botão “Autenticar”. Logo em seguida, você será direcionado para a página de “Afiliações de Gateways” em que você deve preencher os campos vazios com os seus Key e Token para aquela loja. Para saber mais detalhes, consulte nosso artigo de como gerar [o appKey e o appToken](https://help.vtex.com/pt/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2 "o appKey e o appToken"). 
+1. No Admin VTEX, acesse __Aplicativos > Customer Credit > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na seção __Pendente__, uma ou mais das configurações listadas abaixo podem ser exibidas:
+<br>
+<ul>
+<br>
+    	<li><b>Ativar emails transacionais no Message Center</b>: clique em <b>Ativar</b> para instalar os templates de emails transacionais relativos ao Customer Credit no <a href="https://help.vtex.com/pt/tutorial/conhecendo-o-message-center--tutorials_84">Message Center</a>.</li>
+    	<li><b>Configurar condições de pagamento do checkout</b>: clique em <b>Configurar</b> para permitir a definição as regras de prazo e parcelamento da loja.</li>
+  	<li><b>Appkey e appToken da afiliação não definidos</b>: clique em <b>Autenticar</b> para ser redirecionado a tela de configuração onde você deverá preencher as informações <b>Application Key</b> e <b>Application Token</b>. Esta ação permitirá que pagamentos realizados por meio de Customer Credit possam ser processados em sua loja. Saiba mais em <a href="https://developers.vtex.com/docs/guides/authentication">Authentication</a>.</li>
+</ul>
 
-Desse modo, o Customer Credit estará disponível como forma de pagamento no SmartCheckout da sua loja.
+![CC_Configurações_1_PT](//images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/b1505293c33db8cd9f7d8cf1d7802496/CC_Configura__es_1_PT.JPG)
 
-## Configurações da app 
+## Configurações da app
 
-Em seguida, você terá quatro opções de customização da experiência que o seu consumidor terá na loja. 
+Em seguida, ainda na mesma tela do Admin VTEX (__Aplicativos > Customer Credit > Configurações__), você deve verificar as seguintes opções de configurações:
 
-Confira detalhes de cada uma delas a seguir.
+- [Tolerância](#tolerancia)
+- [Criação automática de conta](#criacao-automatica-de-conta) 
+- [Página Meus Créditos](#pagina-meus-creditos)
+- [Instruções de pagamento](#instrucoes-de-pagamento)
+- [Informações de identificação](#informacoes-de-identificacao)
 
 ### Tolerância
 
-Esta opção permite que uma compra seja fechada mesmo que ela ultrapasse o crédito disponível do usuário. Vale ressaltar que é possível cadastrar um percentual excedente do crédito disponível para cada conta cadastrada.
+Ativar esta opção permite que uma compra seja concluída mesmo que o seu valor ultrapasse o limite de crédito disponível do cliente. No momento da criação da conta é possível cadastrar um percentual excedente de crédito (tolerância) para cada cliente.
 
-Por exemplo, digamos que uma conta tenha R$ 1.000,00 de crédito disponível e uma tolerância de 10%. Desse modo, o sistema permitirá que pedidos sejam feitos em até R$ 1.100,00.
+Por exemplo, para uma conta criada com o limite de crédito de R$ 1.000,00 e tolerância de 10%, o cliente poderá realizar um pedido no valor máximo de R$ 1.100,00 utilizando o Customer Credit como meio de pagamento. Caso o cliente deseje utilizar o crédito para pagar um pedido no valor de R$ 1.250,00, o sistema não permitirá a conclusão da compra.
 
 <div class="alert alert-warning">
-Os valores de tolerância são configurados em números decimais, sendo 0 a representação de 0% e 1, a representação de 100%. Exemplo: para uma tolerância de 5%, o valor a ser configurado é de 0.05.
+Os valores de tolerância são configurados em números decimais, sendo 0 a representação de 0% e 1, a representação de 100%. Exemplo: para utilizar uma tolerância de 5%, o valor a ser configurado é de 0.05.
 </div>
 
-Para configurar a tolerância, confira o passo a passo:
-
-1. Acesse o __Admin__.
-2. Clique em __Customer Credit__.
-3. Em seguida, clique em __Contas__.
-4. Clique sobre a conta do cliente na qual deseja configurar a tolerância.
-5. Em __Tolerância__, clique em __Editar__.
-6. Preencha o valor da tolerância (em decimais).
-7. Clique em __Atualizar__.
+![CC_Configurações_2_PT](//images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/1fde698cc193dda7e6ed82de51f7c19e/CC_Configura__es_2_PT.JPG)
 
 ### Criação automática de conta 
 
-Essa flag permite que clientes finalizem uma compra utilizando o Customer Credit como forma de pagamento, mesmo que eles não tenham uma conta prévia com limite de crédito definido. 
+Esta opção permite que qualquer cliente da loja possa utilizar o Customer Credit como meio de pagamento, mesmo que o você não tenha previamente criado uma conta para ele no app do Customer Credit. Ao ativar esta funcionalidade, você também deve definir qual o limite de crédito inicial poderá ser utilizado para pedidos realizados por clientes sem conta no Customer Credit.
 
-Na página de Configurações, você tem a opção de definir um limite de crédito padrão para os clientes que terão suas contas criadas automaticamente no SmartCheckout.
+![CC_Configurações_3_PT](//images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/692229716909844ecc30b605e629301e/CC_Configura__es_3_PT.JPG)
 
 ### Página Meus Créditos
 
-É a interface pela qual seu usuário final terá acesso às informações de sua conta.
+Ao realizar a instalação da página __Meus Créditos__, você permitirá que os clientes possam visualizar e gerenciar informações sobre os créditos e títulos disponíveis em sua conta.
 
-Nela, o usuário visualiza seus limites disponíveis, títulos em aberto e pagos, extrato da conta e a possibilidade de adicionar ou remover dependentes. 
+O cliente poderá acessar esta página no site da sua loja em __Minha Conta > Meus Créditos__.
 
-Quando a página for habilitada, ficará disponível na área logada - MyAccount - do cliente.
+![CC_Configurações_4_PT](//images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/8bf45b5c1708a3861ea92a729c2b9d22/CC_Configura__es_4_PT.JPG)
 
 ### Instruções de pagamento  
 
-Aqui, o usuário pode inserir instruções de pagamento nos documentos dos seus títulos. Para isso, basta clicar em “Editar” e escrever a orientação que preferir. Não esqueça de clicar no botão azul “Atualizar” para salvar as configurações.
-
-Além disso, ressaltamos que a mesma instrução será replicada em todas as faturas da loja, independente da conta a qual o título está vinculado e o seu status.
-
-## Condições de pagamento 
+Esta configuração permite você possa inserir instruções relacionadas ao pagamento nos títulos que forem emitidos pelo Customer Credit. Para editar a mensagem a ser exibida no título, insira as informações na caixa de texto e clique em `Atualizar`.
 
-Nesse momento, o Customer Credit está devidamente instalado e configurado na sua loja. Agora, você pode criar condições de pagamento que serão apresentadas no SmartCheckout.
+<div class="alert alert-warning">
+A mensagem cadastrada nessa configuração será replicada em todos os títulos emitidos para todas as contas de clientes do Customer Credit. Não é possível configurar uma mensagem única para cada cliente ou título específico.
+</div>
 
-É possível definir diferentes cenários de negócio para essas condições de pagamento. Isso implica, também, em quais serão os prazos e os parcelamentos disponibilizados para seus clientes. 
+![CC_Configurações_5_PT](//images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/b2c97be162320e8ed8ef2da3729ecedd/CC_Configura__es_5_PT.JPG)
 
-Alguns prazos utilizados são:
+### Informações de identificação
 
-- Pagamentos realizados em 7, 28 e 45 dias;
-- Pagamento feitos em 45 dias; 
-- Parcelamentos de 30, 60 e 90 dias. 
+Esta opção permite selecionar quais informações de identificação da loja devem ser exibidas na parte superior dos títulos emitidos.
 
-Desse modo, confira o passo a passo:
+![CC_Configurações_6_PT](//images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/d85d0bf4bf69a520f923844d36f304bb/CC_Configura__es_6_PT.JPG)
 
-1. Acesse o __Admin__;
-2. Clique em __Pagamentos__;
-3. Em seguida, clique em __Configurações__;
-4. Certifique-se que você está na aba __Condições de Pagamento__;
-5. Do lado direito da tela, clique no botão verde __“+”__;
-6. Localize e clique na opção __Customer Credit__;
-7. Do lado direito, defina os critérios no box __Configure as regras de prazo e parcelamento__.
+![CC_Configuration_8_PT](//images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/ec7b597cdf26bc9aeb17012047849f44/CC_Configuration_8_PT.JPG)
 
-Caso você queira estabelecer mais de uma regra, basta clicar no botão azul “Adicionar nova regra”. Clique no botão “Salvar” para atualizar as configurações.
+## Condições de pagamento 
 
-Além disso, da mesma forma que outras formas de pagamento, o Customer Credit também permite a configuração de [condições especiais](https://help.vtex.com/pt/tutorial/condicoes-especiais?locale=pt "condições especiais"). Isso faz o usuário defina os contextos de compra serão aplicados para cada condição de pagamento configuradas na loja.
+Assim que as configurações do Customer Credit estiverem concluídas, é necessário indicar quais serão as opções de prazo e parcelamentos disponíveis a serem exibidos aos clientes na tela do Checkout.
 
-### Juros
+Para criar as condições de pagamento de títulos do Customer Credit, siga os passos abaixo:
 
-Por fim, você também pode definir taxas de juros simples para as regras de parcelamento configuradas na sua loja. Atualmente, é possível aplicar essas taxas para pedidos que serão pagos em duas ou mais parcelas.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Selecione a opção __Customer Credit__.
+4. Preencha o campo __Nome da condição__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Em __Configure as condições de prazo e parcelamento__, indique o número de parcelas, período de vencimento (em dias) e a taxa de juros simples a ser aplicada em cada parcela. Para criar mais de uma condição de pagamento, clique em `Adicionar nova condição`.
 
-<div class="alert alert-warning">
-<strong>Atenção</strong>: as taxas de juros <strong>não</strong> são aplicáveis para pedidos que serão pagos em apenas uma parcela.
-</div>  
+![CC_Configuration_9_PT](//images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/337edcc2678c80f6e1504def51efceaf/CC_Configuration_9_PT.JPG)
 
-Entretanto, apenas um valor de juros aplicado aos parcelamentos será exibido no SmartCheckout.
+<blockquote><ui>7. Se desejar, você também pode <a href="https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456">configurar condições especiais de pagamento</a>.</ui>
 
-Por exemplo, digamos que você tenha configurado três parcelamentos para o Customer Credit, cada um deles com uma taxa de juros diferente: a primeira com 10%, a segunda com 15% e a terceira com 20%.
+<blockquote><ui>8. Clique em <b>Salvar</b>.</ui>
 
-Como a configuração de 10% é a mais vantajosa para o consumidor final, essa será a única opção de pagamento exibida no SmartCheckout.
+<div class="alert alert-warning">
+Não é possível configurar taxa de juros para uma condição de pagamento criada com apenas uma única parcela. 
+</div>
diff --git a/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md b/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md
index 6062e4f59..45a73f455 100644
--- a/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md
+++ b/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md
@@ -3,8 +3,8 @@ title: 'Configurar logística para o Mercado Livre'
 id: 4551ZlEQI8qmiSWieigoKy
 status: PUBLISHED
 createdAt: 2018-08-13T12:53:57.008Z
-updatedAt: 2023-03-28T13:36:16.191Z
-publishedAt: 2023-03-28T13:36:16.191Z
+updatedAt: 2024-07-23T22:07:18.063Z
+publishedAt: 2024-07-23T22:07:18.063Z
 firstPublishedAt: 2018-08-13T14:27:58.483Z
 contentType: trackArticle
 productTeam: Channels
@@ -23,6 +23,10 @@ Os modos de envio podem ser de dois tipos:
 - [Mercado Envios 1 (ME1)](#mercado-envios-1-me1)
 - [Mercado Envios (ME2)](#mercado-envios-2-me2)
 
+<div class="alert alert-warning">
+  Independente do modo de envio que sua loja utiliza, é necessário ter um SLA configurado na VTEX, caso contrário os pedidos realizados no Mercado Livre não serão integrados na plataforma da VTEX.
+  </div>
+
 ## Mercado Envios 1 (ME1)
 
 O modo de envios ME1 é destinado a produtos que possuem mais de 30 kg ou tem mais 200 cm no total, somando altura, largura e comprimento, ou em que um dos lados do produto exceda 70 cm.
@@ -67,12 +71,12 @@ Alguns tipos logísticos possuem a obrigatoriedade de envio de nota fiscal ou co
 - [Flex](#flex)
 - [Mercado Envios Full](#mercado-envios-full)
 
-### Drop Off
-
 <div class="alert alert-info">
-A modalidade Drop Off é a única que não oferece possibilidade do cliente retirar o pedido em pontos de retirada.
+Para Segmentar qual tipo de frete utilizado pela loja, é necessário criar um <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106"><i>atributo de produto</i></a> com o nome <code>meli_shipping_mode</code>, onde estará preenchido se é ME1 ou ME2. 
 </div>
 
+### Drop Off
+
 Sempre que você inicia como vendedor no Mercado Livre, você começa obrigatoriamente pelo *Drop Off*, esse tipo logístico é utilizado por todos os clientes que estão começando a vender no Mercado Livre.
 
 Quando o pedido é fechado no Mercado Livre, uma etiqueta é enviada para o seller, constando endereço de entrega do pedido. O seller precisa imprimir essa etiqueta, colar no pacote do pedido e despachá-lo em alguma agência dos Correios. 
@@ -119,6 +123,10 @@ Essa modalidade só está disponível para pedidos feitos na mesma cidade do sel
 
 É possível configurar esse serviço na sua loja através do [cadastro de um estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque) exclusivo para o  Mercado Envios Full. Essa configuração permite acompanhar o nível do estoque uma vez que a quantidade dos produtos dos pedidos feitos através do Mercado Envios Full é atualizada automaticamente conforme a venda é realizada.
 
+<div class="alert alert-danger">
+  Caso o seller escolha o modelo logístico <b>Mercado Envios Full</b>, é necessário seguir a seguinte ordem de configuração: <p><ol><a href="#configurando-modelo-de-envio">Configurar modelo de envio</a> <br><a href="#configurar-o-mercado-envios-full">Configurar o Mercado Envios Full</a></br></ol></p>
+  </div>
+
 #### Configurar o Mercado Envios Full
 
 Para configurar, siga os passos a seguir: 
@@ -126,12 +134,22 @@ Para configurar, siga os passos a seguir:
 1. No Admin VTEX, acesse **Envio > Estratégia de Envio > Estoques**, ou digite *Estratégia de Envio* na barra de busca no topo da página e selecione a aba *Estoques*.     
 2. [Cadastre](https://help.vtex.com/pt/tutorial/gerenciar-estoque) um estoque.    
 3. Na aba **Estoques**, copie o ID do estoque que você criou.    
-4. Acesse **Marketplace > Conexões > Integrações**, ou digite *Integrações* na barra de busca no topo da página.     
-5. Na integração do Mercado Livre, clique na engrenagem <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />  e selecione a opção `Editar configuração`.    
+4. Acesse **Marketplace > Marketplaces e Integrações**, ou digite *Marketplaces e Integrações* na barra de busca no topo da página.      
+5. Clique na integração do Mercado Livre e selecione a opção `Editar configuração`.    
 6. Insira o ID do estoque selecionado no campo **Armazém Mercado Full**.  
 7. Clique em `Salvar Configuração`.    
 
-#### Consultar as notas fiscais do Mercado Livre por API
+## Configurando o modelo de envio
+
+Após definir qual modelo de envio será utilizado para a integração da sua loja com o Mercado Livre, é necessário configurar na integração se será utilizado o ME1 ou ME2. Para isso, você deve seguir os seguintes passos, **criar um campo customizável de produto** e **preenchê-lo**.
+
+Para criar um campo de produto, siga as instruções do tutorial [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106). 
+
+<div class="alert alert-warning">
+O nome do campo criado deve ser "meli_shipping_mode" e o valor do campo deve ser preenchido como "me1" ou "me2". Caso o nome do campo ou o preenchimento seja diferente, a integração não reconhecerá o atributo.
+</div>
+
+## Consultar as notas fiscais do Mercado Livre por API
 
 As notas fiscais dos pedidos [Mercado Envios Full](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy#mercado-envios-full) emitidas pelo Mercado Livre podem ser consultadas por meio de nossas chamadas de API. Para consultar a nota fiscal faturada pelo Mercado Livre para o pedido, você deverá utilizar a chamada de API [Get Order](https://developers.vtex.com/vtex-rest-api/reference/orders#getorder). 
 
diff --git a/docs/tracks/pt/setting-up-the-order-summary-printing.md b/docs/tracks/pt/setting-up-the-order-summary-printing.md
index 5faf6eac9..a679e89ec 100644
--- a/docs/tracks/pt/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/pt/setting-up-the-order-summary-printing.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-customizacoes
 
 Quando o vendedor conclui um pedido com o inStore, ele pode imprimir um resumo desse pedido. Mas, para habilitar essa funcionalidade, você precisa fazer algumas configurações.
 
-![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
+![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
 
 São necessárias duas etapas:
 
@@ -50,7 +50,7 @@ window.INSTORE_CONFIG = {
 
 Essa alteração fará aparecer no menu principal do inStore a opção __Configurar o dispositivo__, como mostra a imagem abaixo. É por meio dessa opção que vamos configurar a impressora.
 
-![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
+![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> Há uma opção para imprimir automaticamente o resumo do pedido, assim que o pedido for concluído. Para habilitar, basta adicionar a propriedade <code>printPageAutomatically</code> com o valor <code>true</code> dentro do objeto printingConfig. Veja abaixo como ficaria o trecho de código neste caso.
@@ -84,11 +84,11 @@ Tendo o AppKey e o AppToken em mãos, siga os passos abaixo:
 2. Abra o aplicativo do inStore e entre na loja onde deseja configurar a impressora.
 3. No menu principal do inStore, na seção Configurações, agora deve constar a opção __Configurar o dispositivo__. Clique nessa opção.
 
-![15. Configurar impressão de resumo do pedido - 3](https://images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
+![15. Configurar impressão de resumo do pedido - 3](//images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
 
 Você encontrará o resumo do dispositivo configurado. Se essa for a primeira vez em que você realiza essa configuração, os campos dessa tela estarão vazios. Se um dispositivo já tiver sido configurado anteriormente, algumas informações sobre o dispositivo serão exibidas (Nome do dispositivo e Impressora padrão). Clique no botão __Editar__.
 
-![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 Será exibido um formulário contendo os campos __AppKey__, __AppToken__ e o __nome__ com o qual você deseja identificar o dispositivo. Após inserir esses dados, clique em __Configurar__.
 
diff --git a/docs/tracks/pt/settings-on-via-marketplace.md b/docs/tracks/pt/settings-on-via-marketplace.md
index 76cea9c91..93c3972b4 100644
--- a/docs/tracks/pt/settings-on-via-marketplace.md
+++ b/docs/tracks/pt/settings-on-via-marketplace.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurações no Via Marketplace'
+title: 'Configurações na Casas Bahia Marketplace'
 id: 2oxPVeYpVgA8IrhaDqKon6
 status: PUBLISHED
 createdAt: 2022-01-18T21:39:29.664Z
-updatedAt: 2023-02-08T14:50:54.438Z
-publishedAt: 2023-02-08T14:50:54.438Z
+updatedAt: 2024-01-22T15:59:29.253Z
+publishedAt: 2024-01-22T15:59:29.253Z
 firstPublishedAt: 2022-01-18T22:32:05.415Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,47 +14,47 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-integracao-da-via-varejo
 ---
 
-Os primeiros passos para integrar sua loja VTEX com o Via Marketplace são:
+Os primeiros passos para integrar sua loja VTEX com a Casas Bahia Marketplace  são:
 
-1. [Criar conta de seller no Via Marketplace](#criar-conta-de-seller-no-via-marketplace)
-2. [Solicitar token no Via Marketplace](#solicitar-token-no-via-marketplace)
+1. [Criar conta de seller na Casas Bahia Marketplace](#criar-conta-de-seller-na-casas-bahia-marketplace)
+2. [Solicitar token na Casas Bahia Marketplace](#solicitar-token-na-casas-bahia-marketplace)
 3. [Cadastrar Integradora de Frete](#cadastrar-integradora-de-frete)
 4. [Cadastrar Integradora de Pedidos](#cadastrar-integradora-de-pedidos)
 
-## Criar conta de seller no Via Marketplace
+## Criar conta de seller na Casas Bahia Marketplace
 
-O primeiro passo para configurar sua loja é [criar uma conta de seller no Via Marketplace](https://so.via.com.br/). Depois de  realizar o cadastro e criar a conta, você deverá aguardar o contato da Via para orientá-lo sobre os próximos passos para cadastro da sua conta de seller.
+O primeiro passo para configurar sua loja é [criar uma conta de seller na Casas Bahia Marketplace](https://so.via.com.br/). Depois de  realizar o cadastro e criar a conta, você deverá aguardar o contato da Casas Bahia Marketplace para orientá-lo sobre os próximos passos para cadastro da sua conta de seller.
 
-## Solicitar token no Via Marketplace
+## Solicitar token na Casas Bahia Marketplace
 
-Depois que receber o contato do Via Marketplace, você deverá solicitar ao marketplace a chave de acesso (token) para começar a configurar a integração VTEX. Essa chave dá permissão para a VTEX alterar ou atualizar informações relacionadas à sua loja diretamente no marketplace.
+Depois que receber o contato da Casas Bahia Marketplace, você deverá solicitar ao marketplace a chave de acesso (token) para começar a configurar a integração VTEX. Essa chave dá permissão para a VTEX alterar ou atualizar informações relacionadas à sua loja diretamente no marketplace.
 
-A chave de acesso será utilizada na etapa de [Cadastro do conector do Via](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/1okse2MybWk04AQoueu88O). Sem esse token não será possível concluir a integração com o Via Marketplace.
+A chave de acesso será utilizada na etapa de [Cadastro do conector da Casas Bahia Marketplace](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/1okse2MybWk04AQoueu88O). Sem esse token não será possível concluir a integração com a Casas Bahia Marketplace.
 
-Existem três fluxos diferentes para configurar sua conta no Via. Veja abaixo em qual deles você se encaixa e faça download da documentação do Via Marketplace:
+Existem três fluxos diferentes para configurar sua conta na Casas Bahia Marketplace. Veja abaixo em qual deles você se encaixa e faça download da documentação da Casas Bahia Marketplace:
 
-- [Onboarding](https://drive.google.com/uc?export=download&id=1g6Swi8HoSkIRyZGeab4AYoQh4GMxC1wy): a solicitação do token do Via Marketplace é feita no Onboarding para lojistas que estão integrando pela primeira vez.
-- [Chamado para lojistas não integrados](https://drive.google.com/uc?export=download&id=1Ty_KwFH5k0QI5pAyzt_bBdy7OfjMODY5): para lojistas que estavam cadastrados anteriormente no Via e não integraram suas lojas. A solicitação do token é feita por uma abertura de chamado no [Portal do lojista do Via Marketplace](https://pas.viavarejo.com.br/login?returnUrl=%2F).
-- [Chamado para lojistas integrados](https://drive.google.com/uc?export=download&id=1KK0z5CFlA1pPH0QoFq2trrZWcVbkjqQC): o lojista deverá se enquadrar em uma das circunstâncias abaixo:
+- [Onboarding](https://marketplace.via.com.br/): a solicitação do token da Casas Bahia Marketplace é feita no Onboarding para lojistas que estão integrando pela primeira vez.
+- [Chamado para lojistas não integrados](https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01835): para lojistas que estavam cadastrados anteriormente na Casas Bahia Marketplace e não integraram suas lojas. A solicitação do token é feita por uma abertura de chamado no [Portal do lojista da Casas Bahia Marketplace](https://pas.viavarejo.com.br/login?returnUrl=%2F).
+- [Chamado para lojistas integrados](https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01974): o lojista deverá se enquadrar em uma das circunstâncias abaixo:
    * Utilizava uma outra integração antes de utilizar a integração da VTEX.
    * Quando o lojista deseja modificar de integrador para integração própria.
 
 ## Cadastrar Integradora de Frete
 
-O Via Marketplace exige que você informe uma rota de API para a consulta de valores de frete, preço e prazo em tempo real, de acordo com o CEP. Você precisa cadastrar essa URL pelo [Portal do lojista do Via Marketplace](https://orbviavarejo.nccserver.com.br/ViaVarejoWeb), na seção **Configurações > Integradora de frete**.
+A Casas Bahia Marketplace exige que você informe uma rota de API para a consulta de valores de frete, preço e prazo em tempo real, de acordo com o CEP. Você precisa cadastrar essa URL pelo [Portal do lojista da Casas Bahia Marketplace](https://plataformamarketplaceprd.b2clogin.com/plataformamarketplaceprd.onmicrosoft.com/b2c_1a_signup_signin_pas/oauth2/v2.0/authorize?client_id=07d16b2e-55be-4c02-93c3-6d859ed6ff12&scope=openid%20profile%20offline_access&redirect_uri=https%3A%2F%2Fpas.viavarejo.com.br&client-request-id=bc66a8e0-a543-478b-bd97-3b6d0373156f&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=2.30.0&client_info=1&code_challenge=DxEQ1KVtlEA0IVlteU9fNjmV9GdMHXB_aSIDJq-bLKk&code_challenge_method=S256&nonce=fe1482bd-316e-4973-844c-7992ef741abc&state=eyJpZCI6IjlmMDQ1ZTIyLWY2ZDgtNGY3MS1iNzU3LWQ0OWVlN2NkZWY3OSIsIm1ldGEiOnsiaW50ZXJhY3Rpb25UeXBlIjoicmVkaXJlY3QifX0%3D&_ga=2.230922463.1371461897.1701380473-1690674604.1698180870), na seção **Configurações > Integradora de frete**.
 
 No campo Endereço URL, informe a seguinte rota de API, substituindo `{AccountName}` pelo [nome da sua loja](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) na plataforma VTEX:
 
 `http://cnovaintegration.vtexcommercestable.com.br/api/viavarejointegration/pub/{{AccountName}}/freight?skuId={{skuId}},{{quantidade}}&zipcode={{cep}}`
 
 <div class="alert alert-info">
-Se o seller utiliza a solução logística <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01543&title=O%20que%20%C3%A9%20Envvias?#:~:text=O%20Envvias%20%C3%A9%20a%20plataforma,ele%20passa%20a%20ser%20automatizado!">Envvias</a>, deverá <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01538&title=Como%20cadastro%20minha%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">cadastrar</a> a URL de frete como <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01071&title=O%20que%20%C3%A9%20uma%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">tabela de contingência</a> ou abrir um chamado no Via Marketplace para remover o Envvias e cadastrar a URL de Frete.
+Se o seller utiliza a solução logística <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01543&title=O%20que%20%C3%A9%20Envvias?#:~:text=O%20Envvias%20%C3%A9%20a%20plataforma,ele%20passa%20a%20ser%20automatizado!">Envvias</a>, deverá <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01538&title=Como%20cadastro%20minha%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">cadastrar</a> a URL de frete como <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01071&title=O%20que%20%C3%A9%20uma%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">tabela de contingência</a> ou abrir um chamado na Casas Bahia Marketplace para remover o Envvias e cadastrar a URL de Frete.
 </div>
 
 ## Cadastrar Integradora de Pedidos
 
-Para ativar a importação de pedidos do Via Marketplace para a VTEX, é recomendável informar a rota de API abaixo, substituindo `{accountName}` pelo nome da sua conta na VTEX. Você precisa cadastrar essa URL pelo [Portal do Lojista da Via Marketplace](https://pas.viavarejo.com.br/), na seção **Configurações > Integradora de pedidos**.
+Para ativar a importação de pedidos da Casas Bahia Marketplace para a VTEX, é recomendável informar a rota de API abaixo, substituindo `{accountName}` pelo nome da sua conta na VTEX. Você precisa cadastrar essa URL pelo [Portal do Lojista da Casas Bahia Marketplace](https://pas.viavarejo.com.br/), na seção **Configurações > Integradora de pedidos**.
 
 `https://{accountName}.vtexcommercestable.com.br/api/viavarejointegration/pub/order/notification`
 
-Para mais informações sobre esse processo, leia a documentação do Via Marketplace [Integradora de pedidos - Como cadastrar URL de pedidos?](https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01735&title=Integradora%20de%20pedidos%20-%20Como%20cadastrar%20URL%20de%20pedidos?&cat=Configura%C3%A7%C3%B5es).
+Para mais informações sobre esse processo, leia a documentação da Casas Bahia Marketplace [Integradora de pedidos - Como cadastrar URL de pedidos?](https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01735&title=Integradora%20de%20pedidos%20-%20Como%20cadastrar%20URL%20de%20pedidos?&cat=Configura%C3%A7%C3%B5es).
diff --git a/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
index 9b7f10243..32e573ce5 100644
--- a/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
@@ -3,8 +3,8 @@ title: 'Compartilhar carrinho utilizando o VTEX Sales App Social Selling'
 id: 6deiffo22iKkY27PkfstXy
 status: PUBLISHED
 createdAt: 2021-08-05T14:57:10.773Z
-updatedAt: 2023-05-31T15:22:18.271Z
-publishedAt: 2023-05-31T15:22:18.271Z
+updatedAt: 2023-07-26T19:00:02.450Z
+publishedAt: 2023-07-26T19:00:02.450Z
 firstPublishedAt: 2021-08-05T15:08:06.961Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,8 +14,7 @@ trackId: 4BYzQIwyOHvnmnCYQgLzdr
 trackSlugPT: instore-usando-o-app
 ---
 
-
-A funcionalidade Social Selling no inStore permite que vendedores selecionem produtos e compartilhem o carrinho preenchido utilizando um QR code ou enviando um link por canais como o WhatsApp ou outras redes sociais. Dessa forma, seus clientes podem realizar o pagamento e concluir a compra em seu próprio celular, tablet ou computador.
+A funcionalidade Social Selling no VTEX Sales App permite que vendedores selecionem produtos e compartilhem o carrinho preenchido utilizando um QR code ou enviando um link por canais como o WhatsApp ou outras redes sociais. Dessa forma, seus clientes podem realizar o pagamento e concluir a compra em seu próprio celular, tablet ou computador.
 
 Existem duas formas de utilizar essa funcionalidade:
 
@@ -24,7 +23,7 @@ Existem duas formas de utilizar essa funcionalidade:
 
 ## Sugestão de carrinho
 
-Essa opção possibilita compartilhar um carrinho preenchido com um ou mais clientes. Após adicionar produtos ao carrinho no inStore, o vendedor pode seguir os passos abaixo para compartilhar o link.
+Essa opção possibilita compartilhar um carrinho preenchido com um ou mais clientes. Após adicionar produtos ao carrinho no VTEX Sales App, o vendedor pode seguir os passos abaixo para compartilhar o link.
 
 1. Clique no botão `Compartilhar`.
 2. Clique na opção `Sugestão de carrinho`.
@@ -38,7 +37,7 @@ Essa opção possibilita compartilhar um carrinho preenchido com um ou mais clie
 
 Veja o passo a passo ilustrado a seguir.
 
-![socialselling-sugestaocarrinho-pt](https://images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/e0ce46b332549816ac9ff81a99d39879/socialselling-sugestaocarrinho-pt.gif)
+![socialselling-sugestaocarrinho-pt](//images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/e0ce46b332549816ac9ff81a99d39879/socialselling-sugestaocarrinho-pt.gif)
 
 O vendedor pode enviar o mesmo link para vários clientes, quantas vezes desejar. Cada vez que uma pessoa acessar esse link, um novo carrinho será gerado, exatamente igual ao criado no inStore. Cada carrinho acessado também fica associado à conta do vendedor e, se houver, ao código do vendedor.
 
@@ -64,4 +63,4 @@ Nesse caso, o vendedor precisa colocar itens no carrinho, preencher as informaç
 
 Veja o passo a passo ilustrado abaixo.
 
-![socialselling-paymentlink-pt](https://images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/c00c97d9a8eec83b259d30793879d019/socialselling-paymentlink-pt.gif)
+![socialselling-paymentlink-pt](//images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/c00c97d9a8eec83b259d30793879d019/socialselling-paymentlink-pt.gif)
diff --git a/docs/tracks/pt/shipping-strategies.md b/docs/tracks/pt/shipping-strategies.md
index ae91a4909..1e3064b43 100644
--- a/docs/tracks/pt/shipping-strategies.md
+++ b/docs/tracks/pt/shipping-strategies.md
@@ -18,7 +18,7 @@ As opções de envio que ficam disponíveis para o cliente no checkout da sua lo
 
 A estratégia de envio define como os estoques, as docas e as políticas de envio interagem para atender às necessidades dos seus clientes e do seu negócio. 
 
-![Estrategia Envio](https://images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/3b4eb756f2c833f5b3fa7726c3cbdce7/Estrategia_Envio.png)
+![Estrategia Envio](//images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/3b4eb756f2c833f5b3fa7726c3cbdce7/Estrategia_Envio.png)
 
 A estratégia de envio é definida por três entidades logísticas:
 
diff --git a/docs/tracks/pt/size-chart.md b/docs/tracks/pt/size-chart.md
index 5c9ba60c5..908261505 100644
--- a/docs/tracks/pt/size-chart.md
+++ b/docs/tracks/pt/size-chart.md
@@ -18,7 +18,7 @@ Ao comprar roupas ou calçados on-line, muitos usuários costumam ter dúvidas s
 
 O guia de tamanhos do Mercado Livre é uma tabela de medidas ou equivalências que permite aos usuários visualizar as medidas exatas para que possam escolher o produto que melhor se adaptem. 
 
-![MLB tamanos1](https://images.ctfassets.net/alneenqid6w5/3kHkmPhrh50s9QhJQurtcD/f4ca7decdd70609953dbd842b55c24f7/MLB_tamanos1.gif)
+![MLB tamanos1](//images.ctfassets.net/alneenqid6w5/3kHkmPhrh50s9QhJQurtcD/f4ca7decdd70609953dbd842b55c24f7/MLB_tamanos1.gif)
 
 ## Entendendo o guia de tamanhos
 
@@ -46,7 +46,7 @@ Feita a escolha das categorias, preencha a coluna `CategoryID` com o ID da Categ
 
 Na segunda etapa do preenchimento escolha os nomes que deseja dar para as suas tabelas. Você deve definir um nome para cada tabela que será criada. É possível vincular a mesma tabela a várias categorias. A imagem abaixo ilustra como este nome aparece na criação manual no Mercado Livre - neste caso, a tabela seria Camisetas esportivas.
 
-![Screen Shot 2020-10-06 at 12.07.57](https://images.ctfassets.net/alneenqid6w5/1gGCEZMpgye7A26vQF2faX/61530c84cd32534c8ec26f92a19bde52/Screen_Shot_2020-10-06_at_12.07.57.png)
+![Screen Shot 2020-10-06 at 12.07.57](//images.ctfassets.net/alneenqid6w5/1gGCEZMpgye7A26vQF2faX/61530c84cd32534c8ec26f92a19bde52/Screen_Shot_2020-10-06_at_12.07.57.png)
 
 Feita a escolha das tabelas, preencha a coluna `TableName` com o nome do guia de tamanhos que será usado para cada categoria.
 
@@ -54,7 +54,7 @@ Feita a escolha das tabelas, preencha a coluna `TableName` com o nome do guia de
 
 Na terceira etapa do preenchimento escolha o nome que desejar dar para os tamanhos da sua tabela. A imagem abaixo ilustra como estes tamanhos aparecem na criação manual no Mercado Livre - neste caso, os tamanhos seriam P e M.
 
-![Screen Shot 2020-10-06 at 12.08.39](https://images.ctfassets.net/alneenqid6w5/6KvJFDknNoKqgL32Rs9R58/9f29afbc7690b6e67bde3201e88112b0/Screen_Shot_2020-10-06_at_12.08.39.png)
+![Screen Shot 2020-10-06 at 12.08.39](//images.ctfassets.net/alneenqid6w5/6KvJFDknNoKqgL32Rs9R58/9f29afbc7690b6e67bde3201e88112b0/Screen_Shot_2020-10-06_at_12.08.39.png)
 
 Feita a escolha das tabelas, preencha a coluna `SizeName` com o nome dos tamanhos que serão usados para cada guia de tamanhos. 
 
@@ -62,7 +62,7 @@ Feita a escolha das tabelas, preencha a coluna `SizeName` com o nome dos tamanho
 
 Na quarta etapa do preenchimento é definir as colunas que gostaria de incluir no guia de tamanhos.  A imagem abaixo ilustra como estes tamanhos aparecem na criação manual no Mercado Livre - note que é possível vincular até 5 colunas por tabela.
 
-![Screen Shot 2020-10-06 at 12.07.49](https://images.ctfassets.net/alneenqid6w5/190jdCD4Tgmp6xGfLm0nlT/c387fda654105b81532fcc79e64087da/Screen_Shot_2020-10-06_at_12.07.49.png)
+![Screen Shot 2020-10-06 at 12.07.49](//images.ctfassets.net/alneenqid6w5/190jdCD4Tgmp6xGfLm0nlT/c387fda654105b81532fcc79e64087da/Screen_Shot_2020-10-06_at_12.07.49.png)
 
 Na planilha de mapeamento, é necessário utilizar códigos específicos para indicar as colunas que devem ser incluídas no Guia de Tamanhos:
 
@@ -167,7 +167,7 @@ Ao concluir as etapas de preenchimento da planilha de mapeamento, você deve seg
 1. Acesse o Admin.
 2. No módulo Marketplace, clique em Integrações.
 3. Selecione a opção Configurações.
-4. Na integração Mercado Livre, clique na engrenagem<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+4. Na integração Mercado Livre, clique na engrenagem<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 5. Escolha a opção **Upload do mapeamento**.
 6. Selecione a opção **Escolher um arquivo**.
 7. Agora, selecione a planilha de mapeamento de categorias, atributos e variações do Mercado Livre.
@@ -180,9 +180,9 @@ Agora, é necessário acessar sua conta do Mercado Livre para ativar o guia de t
 1. Acessar sua conta no Mercado Livre.
 2. Clique na opção **Vendas**.
 3. No menu no canto esquerdo, selecione a opção **Anúncios**.
-4. Clique nos 3 pontos <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/5h4riyTF3EAYAM2e04up4O/73040d1e9e6892c6feea96a9bcc6560e/3_pontos.JPG" />
+4. Clique nos 3 pontos <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/5h4riyTF3EAYAM2e04up4O/73040d1e9e6892c6feea96a9bcc6560e/3_pontos.JPG" />
 5. Selecione a opção **Alterar**.
 6. Na opção Guia de Tamanhos, selecione a tabela que você criou.
 7. Clique em **Confirmar**.
 
-![Início (2)](https://images.ctfassets.net/alneenqid6w5/4hTDDEGYuZscACtdLiYNhW/d8781adfeab2a6c7326fba9aed7aa52b/Mercado_Livre_Brasil.gif)
+![Início (2)](//images.ctfassets.net/alneenqid6w5/4hTDDEGYuZscACtdLiYNhW/d8781adfeab2a6c7326fba9aed7aa52b/Mercado_Livre_Brasil.gif)
diff --git a/docs/tracks/pt/store-development.md b/docs/tracks/pt/store-development.md
index 3a95f659e..6812283f3 100644
--- a/docs/tracks/pt/store-development.md
+++ b/docs/tracks/pt/store-development.md
@@ -19,7 +19,7 @@ Em uma loja de ecommerce, tanto a interface que os usuários veem e interagem qu
 - **Frontend**: O frontend compreende a camada visual de uma aplicação, como por exemplo, a interface de um website ou de um aplicativo mobile. É através dela que os usuários interagem com uma loja. Na VTEX, existem três tecnologias diferentes que podem ser utilizadas para o desenvolvimento de fronts de loja. São elas: o CMS Portal (Legado), o Store Framework e a FastStore.
 - **Backend**: O backend é a camada responsável por computar e processar todos os dados nescessários para executar as funcionalidades oferecidas por uma determinada aplicação. Na VTEX, o desenvolvimento de integrações e aplicações de backend se dá principalmente através do VTEX IO e das APIs da VTEX.
 
-![storefront mockup](https://images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/89990fd9837da63e881a4fee92ce9787/image1.png)
+![storefront mockup](//images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/89990fd9837da63e881a4fee92ce9787/image1.png)
 
 Nas seções a seguir, exploraremos melhor os principais aspectos e tecnologias relacionadas ao desenvolvimento de loja na VTEX.
 
diff --git a/docs/tracks/pt/subject-rights.md b/docs/tracks/pt/subject-rights.md
new file mode 100644
index 000000000..7cb1530d6
--- /dev/null
+++ b/docs/tracks/pt/subject-rights.md
@@ -0,0 +1,31 @@
+---
+title: 'Direitos dos titulares'
+id: 1ZWqUdeKsD8Mm3GKQ8xBI3
+status: PUBLISHED
+createdAt: 2024-05-03T20:20:18.952Z
+updatedAt: 2024-05-03T21:27:03.812Z
+publishedAt: 2024-05-03T21:27:03.812Z
+firstPublishedAt: 2024-05-03T20:25:55.041Z
+contentType: trackArticle
+productTeam: Others
+slug: direitos-dos-titulares
+locale: pt
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugPT: dados-e-privacidade
+---
+
+Uma solicitação de titular de dados é um pedido escrito que clientes da sua loja podem fazer para exercer seu direito de obter informações sobre os dados que estão sendo tratados pela loja e pela VTEX.
+
+Qualquer pessoa tem o direito de confirmar se uma loja está tratando seus dados ou não. Se estiver, o titular também tem o direito de acessar os dados e saber a finalidade do tratamento, as categorias de dados pessoais e os destinatários ou categorias de destinatários com os quais seus dados pessoais foram compartilhados.
+
+Para mais informações, confira o guia [Direitos dos titulares de dados pessoais](https://help.vtex.com/pt/tutorial/direitos-dos-titulares-de-dados-pessoais--6imchxTx09icupKMbzHVIM).
+
+## Exclusão de dados
+
+A qualquer momento, lojistas podem excluir dados pessoais a pedido dos clientes da sua loja. O cliente final deve fazer a solicitação diretamente ao lojista e essas solicitações devem ser encaminhadas pelo lojista à VTEX. O direito de exclusão se sobrepõe ao período de retenção previsto.
+
+Se você gerencia uma loja VTEX e precisa de ajuda para excluir os dados dos usuários, leia [Exclusão de dados de clientes](https://help.vtex.com/pt/tutorial/exclusao-de-dados-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU).
+
+## Alteração de dados
+
+Todos os dados pessoais de clientes da sua loja são editáveis na página [Minha Conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh), exceto o email. Nesse caso, é possível excluir o perfil anterior e criar um novo perfil com outro email.
diff --git a/docs/tracks/pt/technical-and-administrative-measures.md b/docs/tracks/pt/technical-and-administrative-measures.md
new file mode 100644
index 000000000..5f27bc494
--- /dev/null
+++ b/docs/tracks/pt/technical-and-administrative-measures.md
@@ -0,0 +1,56 @@
+---
+title: 'Medidas técnicas e administrativas'
+id: 7ANSqBP5DgOrVVyglo3Lbh
+status: PUBLISHED
+createdAt: 2024-05-03T20:26:17.710Z
+updatedAt: 2024-05-03T21:12:11.696Z
+publishedAt: 2024-05-03T21:12:11.696Z
+firstPublishedAt: 2024-05-03T20:57:29.358Z
+contentType: trackArticle
+productTeam: Others
+slug: medidas-tecnicas-e-administrativas
+locale: pt
+trackId: 4Lc0i0an0DgnEtB0AUwlcq
+trackSlugPT: dados-e-privacidade
+---
+
+A VTEX atua em várias regiões do mundo e possui as ferramentas necessárias para atender as demandas de privacidade de cada local. Por isso, a VTEX sempre toma as medidas necessárias para garantir que sua plataforma seja segura e esteja em conformidade com as leis de proteção de dados.
+
+As ferramentas que oferecemos na plataforma são projetadas para garantir a adequação das lojas a regulamentos de privacidade. No entanto, lojistas também precisam adotar medidas adicionais para cumprir as leis relacionadas ao tratamento de dados pessoais. Para entender esses requisitos, consulte [Papéis na proteção de dados](https://help.vtex.com/pt/tracks/dados-e-privacidade--4Lc0i0an0DgnEtB0AUwlcq/5f8hTEw3xOALgqzus9VXKd).  É importante lembrar que estas são orientações gerais e que os regulamentos específicos podem conter outras obrigações.
+
+## Segurança
+
+A VTEX mantém as medidas técnicas e organizacionais adequadas para proteção da segurança, confidencialidade e integridade dos dados pessoais no contexto da prestação dos serviços.
+
+Confira a seguir as práticas adotadas pela VTEX, detalhadas no [DPA](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/):
+
+* Política antivírus.
+* Classificação de Informações.
+* Gerenciamento de vulnerabilidades.
+* Criptografia de dados pessoais em repouso e em trânsito.
+* Backup e redundância de dados. A VTEX possui uma ferramenta específica para fornecer meios para que o cliente extraia uma cópia completa de todos os dados pessoais armazenados na plataforma. 
+* Recuperação de desastres e recuperação de incidentes.
+* Segregação de clientes e redes.
+* Medidas físicas de segurança.
+* Garantia de exclusão de todos os dados pessoais após o término da prestação de serviços.
+* Garantia de que todo funcionário que acessar dados pessoais esteja vinculado a acordos de confidencialidade com a VTEX.
+* Processo específico de gerenciamento e notificação de incidentes e informará o cliente, conforme exigido pelas leis de proteção de dados, caso tome conhecimento de qualquer violação de dados pessoais.
+* Auxílio a lojistas para realizar a [Avaliação de Impacto de Proteção de Dados (AIPD)](https://commission.europa.eu/law/law-topic/data-protection/reform/rules-business-and-organisations/obligations/when-data-protection-impact-assessment-dpia-required_pt).
+
+Para mais informações, consulte [Práticas de Segurança - VTEX](https://vtex.com/br-pt/security/security-practices/).
+
+## Armazenamento
+
+O [provedor de hospedagem](https://vtex.com/br-pt/privacy-and-agreements/subprocessors/) utilizado pela VTEX é a Amazon Web Services (AWS), que armazena dados na região da Virgínia do Norte, nos Estados Unidos. A plataforma AWS é uma referência no setor de hospedagem em nuvem e possui certificações importantes, como ISO 27001, PCI DSS, CSA, NIST, entre outras. Para ver uma lista de certificações detalhadas, acesse [Programas de conformidade da AWS](https://aws.amazon.com/pt/compliance/programs/?nc1=h_ls). A autorização para o armazenamento de dados na AWS pode ser encontrada em nosso [DPA](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/).
+
+A VTEX somente armazena os dados pessoais enquanto forem necessários para o processamento do serviço prestado.
+
+## Retenção de dados pessoais
+
+Os limites de retenção de dados definem a duração pela qual os dados podem ser armazenados na VTEX. Esses limites são influenciados por vários fatores, como requisitos legais e de conformidade, considerações de privacidade de dados e considerações de custo. Ao estabelecer limites de retenção de dados, pretendemos garantir a conformidade com os regulamentos, proteger a privacidade do usuário e manter a alocação eficiente de recursos.
+
+A responsabilidade pelo cumprimento das leis e regulamentos aplicáveis recai sobre o próprio lojista. Isso inclui a definição e o respeito aos períodos de retenção de dados, os quais podem variar de acordo com a legislação específica a que cada loja está sujeita.
+
+A VTEX disponibiliza os dados de acordo com a capacidade técnica de cada módulo, mas caso seja necessário cumprir legislações específicas, os lojistas precisam extrair os dados relevantes da plataforma. Assim, cabe a cada lojista gerenciar seus próprios períodos de retenção conforme exigido pela legislação aplicável, utilizando os recursos disponíveis na plataforma de forma adequada.
+
+A VTEX tem o dever de armazenar os dados pessoais do comprador durante a vigência do [MSA](https://vtex.com/br-pt/privacy-and-agreements/agreements/). Em caso de cancelamento do contrato com a VTEX, o lojista deve garantir a extração dos dados do Master Data no prazo de 30 (trinta) dias antes da data de rescisão do MSA, de acordo com a Cláusula 7 do [DPA](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/).
diff --git a/docs/tracks/pt/technical-support.md b/docs/tracks/pt/technical-support.md
new file mode 100644
index 000000000..570451a09
--- /dev/null
+++ b/docs/tracks/pt/technical-support.md
@@ -0,0 +1,33 @@
+---
+title: 'Suporte técnico'
+id: 3thRAdTB3gGwTB0e1fVL3T
+status: PUBLISHED
+createdAt: 2024-02-20T21:34:10.778Z
+updatedAt: 2024-02-22T14:08:41.465Z
+publishedAt: 2024-02-22T14:08:41.465Z
+firstPublishedAt: 2024-02-22T14:08:41.465Z
+contentType: trackArticle
+productTeam: Others
+slug: suporte-tecnico
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+Durante e após o desenvolvimento de uma loja, é comum surgirem dúvidas sobre implementações, [configurações de módulos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), [desenvolvimento da frente de loja](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), apps e outros aspectos técnicos. Nesse sentido, o suporte técnico está disponível para auxiliar com questões relacionadas à plataforma, desenvolvimento da loja, aplicativos e implementações.
+
+A tabela a seguir apresenta os principais tópicos relacionados a suporte técnico:
+
+| **Tópico** | **Descrição** | **Artigos** |
+| ---------- | ------------- | ----------- |
+| [VTEX IO](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#ambiente-de-desenvolvimento)         | O VTEX IO é uma Plataforma de desenvolvimento _low-code_ e em nuvem, que permite que desenvolvedores criem soluções para ecommerce. Seu objetivo é fornecer uma forma eficiente de desenvolver soluções e integrações personalizadas dentro do ecossistema VTEX. |   [What is VTEX IO?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) |
+| [Store Framework](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) | Store Framework é uma tecnologia da VTEX para construção de frentes de loja _low-code_ e com foco em compossibilidade. Ele possibilita a combinação de diferentes aplicativos do VTEX IO para formar a frente de loja. |   [What is VTEX Store Framework?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework)<br><br>   [FAQ VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-frequently-asked-questions) |
+| [App VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#o-que-e-um-app-na-vtex)      | Os aplicativos VTEX estendem as funcionalidades da plataforma, auxiliando os lojistas na criação de experiências em várias áreas da loja, incluindo marketing, avaliações de produtos, suporte ao cliente, notificações, logística, customização da loja e muito mais. |    [What is a VTEX App?](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-a-vtex-app)  |
+| Layout            | Tecnologia VTEX para construção de frente de loja utilizando o [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). O Layout permite a criação e customização da frente de loja usando HTML, JavaScript e CSS através do Admin VTEX.<br><br>Atualmente, o Layout está disponível para algumas lojas VTEX, mas não para novas lojas iniciando na VTEX. |    [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj)<br><br>   [Visão geral do Layout](https://help.vtex.com/pt/tutorial/o-que-e-o-cms-layout--EmO8u2WBj2W4MUQCS8262)                    |
+[Integração com ERP](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#integracao-com-erp) | A integração de um ERP com a plataforma VTEX é uma estratégia importante para otimizar as operações de uma conta em um ecommerce com a possibilidade de integrar softwares externos.    |   [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide)<br><br>   [FAQ: ERP Integration](https://developers.vtex.com/docs/guides/faq-erp-integration). |
+
+Se o usuário precisar de um suporte técnico e não encontrar respostas nos portais e documentações mencionados, é possível fazer o contato através da [página de suporte](https://support.vtex.com/hc/pt-br/requests) e escolher **Técnico** como opção através do VTEX IA Suporte Bot, chatbot com foco em assistência técnica, como na imagem abaixo:
+
+![Support imagem 2 -PT](//images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/63300c9dbb7480b31b24085eb5ed7181/support_imagem2_PT.png)
+
+Caso o usuário necessite de suporte além do VTEX IA Suporte Bot, ela pode abrir um ticket clicando em `ABRIR TICKET`. Para mais informações de como preencher o ticket para suporte técnico, basta acessar o artigo [Abrir chamados para o suporte VTEX - Técnico](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt#tecnico).
diff --git a/docs/tracks/pt/teste-1.md b/docs/tracks/pt/teste-1.md
index 88d04561f..dc3a4dc0c 100644
--- a/docs/tracks/pt/teste-1.md
+++ b/docs/tracks/pt/teste-1.md
@@ -3,7 +3,7 @@ title: 'Teste (1)'
 id: 2Oq3MriB8hJ5YmFq3QIlPD
 status: DRAFT
 createdAt: 2021-04-14T14:58:44.451Z
-updatedAt: 2023-06-01T14:02:58.525Z
+updatedAt: 2024-02-23T14:24:12.796Z
 publishedAt: 
 firstPublishedAt: 2021-04-14T15:01:28.601Z
 contentType: trackArticle
@@ -14,82 +14,64 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugPT: configurar-integracao-com-o-magazine-luiza
 ---
 
-Texto [1. continua](#1.o-que-e-o-vtex-shipping-network-correios-?)
+Com foco no sucesso dos nossos clientes, a VTEX oferece soluções completas para diversos modelos de negócio. É a versatilidade do composable commerce a serviço da inovação e do crescimento da sua operação.
 
-Texto [1. continua](#1.o-que-e-o-vtex-shipping-network-correios)
+E para que você adote facilmente novos recursos, gerencie seu negócio com autonomia e ganhe em escalabilidade, disponibilizamos o novo Guia de onboarding, um conteúdo da jornada completa de operar uma loja VTEX. O material está disponível na seção [Comece aqui](https://help.vtex.com/pt/tracks) do Help Center.
 
-Texto [1. continua](#1-.-o-que-e-o-vtex-shipping-network-correios-?)
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/359WPOFfC5pE91DpoECZJe/4ec1ed1efbb3b2bc052974136a8759ce/announcement_complete_guide_PT.png" alt="Guia de onboarding">
+</div>
 
-Texto [1. continua](#1-.-o-que-e-o-vtex-shipping-network-correios)
+## O que é o Guia de onboarding?
 
-Texto [1. continua](#1-o-que-e-o-vtex-shipping-network-correios-?)
+O **Guia de onboarding** é um conjunto de trilhas de documentação que incluem o planejamento de arquitetura da loja, as configurações para o go-live, os produtos para evoluir o negócio e as orientações sobre o nosso suporte. O guia apresenta configurações e recursos da plataforma contextualizados na jornada de operação da loja VTEX.
 
-Texto [1. continua](#1.o-que-e-o-vtex-shipping-network-correios?)
+O **Guia de onboarding** é composto por três trilhas, são elas:
 
-Texto [1. continua](#1-.-o-que-e-o-vtex-shipping-network-correios?)
+- [Trilha da loja VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9)
+- [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS)
+- [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-Texto [1. continua](#1-o-que-e-o-vtex-shipping-network-correios?)
+<div class="alert alert-info">
+As trilhas tem conteúdos complementares, mas são independentes entre si. Isso significa que você pode explorar o conteúdo com liberdade, sem precisar seguir uma sequência.
+</div>
 
-Texto [1. continua](#1-o-que-e-o-vtex-shipping-network-correios?)
+Nosso objetivo é que clientes, parceiros e todo o ecossistema VTEX se beneficiem do **Guia de onboarding**. E para manter a relevância do material para diferentes negócios, consideramos uma jornada bastante abrangente. 
+Veja a seguir uma [introdução](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) do que você encontrará no guia.
 
-Texto [1. continua](#1-o-que-e-o-vtex-shipping-network-correios-?)
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/1N4nX2r9WxhdSCqr8zOEla/dc8a923eb652753491a1501284d17e00/announcement_headings_track_1_PT.png" height="90" alt="Trilha da loja VTEX">
+</div>
 
-Texto [1. continua](#1.o-que-e-o-vtex-shipping-network-correios)
+A **Trilha da loja VTEX** apresenta o contexto inaugural da operação, começando pela definição de qual [tipo de conta e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) são adequados às necessidades do negócio. A partir disso, é possível realizar as [configurações iniciais](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) e as configurações dos [módulos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) da plataforma, focando em acelerar a inauguração da loja. Uma vez que as [integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) estejam concluídas e a implementação da tecnologia de [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para a construção da frente de loja tenha sido finalizada, é chegado o momento do [go-live](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) e da inauguração da nova loja.
 
-Texto [1. continua](#1o-que-e-o-vtex-shipping-network-correios-?)
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6yRmvP19rt7z1mNE7vdWQz/4f45499ead8fd1b91442d51e9e3c50a6/announcement_headings_track_2_PT.png" height="90" alt="Proximos passos apos o go live">
+</div>
 
-Texto [1 - continua](#1o-que-e-o-vtex-shipping-network-correios-?)
+A trilha **Próximos passos após o go-live** apresenta como o [comércio unificado](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/5Qvw31yH2FPDBl14K5xXHA) é realizado com os recursos da plataforma, incluindo [configurações de módulos](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/V1fs7IkfYMfn91ZVHTLu4) não mencionadas anteriormente, pois aqui o foco é na evolução da operação. Esta trilha apresenta também os [produtos Add on](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) da VTEX, uma série de produtos que podem ser adquiridos à parte para permitir novas estratégias e diversificação do negócio.
 
-________________
+<div>
+    <img src="//images.ctfassets.net/alneenqid6w5/6N7adQ7RxTfTyuIrCDqstZ/ee6aea639c26136d7f9ff6b9e560c9cb/announcement_headings_track_3_PT.png" height="90" alt="Suporte na VTEX">
+</div>
 
-Texto [1. continua](#1-o-que-e-o-vtex-shipping-network-correios)
+O **Suporte na VTEX** apresenta o [suporte](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) que prestamos aos clientes, o que não se restringe a uma parte específica da jornada. O [funcionamento do suporte](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3) é inclusive referenciado nas outras trilhas, pois a [abertura de chamados](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE) é a via para determinadas contratações e solicitações. Esta trilha foi organizada para que os nossos clientes tenham a melhor experiência com nossos serviços e que disponham das informações necessárias à abertura de chamados, seja no contexto de suporte [técnico](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T), [financeiro](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl) ou [comercial](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
-_______________________
+## Por que criamos este material?
 
-Etapa 1: Configurações básicas
-Para realizar a primeira etapa de Configurações básicas, siga os passos abaixo:
+Pensando em promover a autonomia dos nossos clientes, organizamos o **Guia de onboarding** e vale ressaltar os seguintes aspectos:
 
-No Admin VTEX, acesse Envio > Localidades, ou digite Localidades na barra de busca no topo da página.
-Clique em Criar localidade.
-Em Status, acione o toggle  para criar a localidade como Ativa, ou deixe-o desativado  para que a nova localidade esteja Pausada. Somente localidades ativas recebem novos pedidos.
-Em Identificação, determine o nome da localidade sendo criada. Este nome é visível somente no seu Admin VTEX.
-Em Seller, selecione um seller para associar à localidade. O seller é quem possui os produtos sendo vendidos.
+* **Jornada completa:** esta é a primeira documentação da jornada completa da operação de uma loja VTEX, sendo que o conteúdo foi planejado para acelerar o go-live e diminuir o _time-to-revenue_ do negócio.
+* **Conteúdo inédito:** além da novidade da abordagem da jornada, existem conteúdos inéditos, com destaques na _Trilha da loja VTEX_ ([Contas e arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl), [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), [Implementação de frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ)), na _Próximos passos após o go-live_ ([Produtos Add-on](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm)) e na _Suporte na VTEX_ como um todo.
+* **Relevância geral:** o valor deste guia não se restringe a novos clientes ou lojas em fases anteriores ao go-live, pois consideramos uma jornada suficientemente abrangente para ser relevante a diversos modelos de negócio.
 
-Cada localidade pode ser associada a um único seller.
-Em Endereço, defina o local físico onde se situa a localidade.
+Desejamos que este material contribua para o sucesso do seu negócio e sua satisfação com a VTEX.
 
-Clique no botão Próximo.
-Feito isso, você terá concluído a Etapa 1 será redirecionado para a segunda e última etapa de criação, a Capacidade operacional.
-
-Etapa 2: Capacidade operacional
-Para realizar esta etapa, siga os passos abaixo:
-
-Em Gostaria de configurar uma capacidade?, clique em umas das alternativas:
-Configurar: a localidade tem um limite na capacidade de receber pedidos e, caso este limite seja atingido, novos pedidos podem ser alocados em outras localidades. Isso aumenta a eficiência da sua operação e aumenta as chances de cumprir as promessas de envio feitas aos clientes.
-Manter ilimitada: a localidade mantém a capacidade irrestrita de receber novos pedidos. Como não é possível determinar um limite máximo, a localidade pode receber mais pedidos do que é capaz de dar vazão no tempo de envio prometido, o que pode causar um atraso nos envios e consequente frustração de clientes.
-
-## 1. O que é o VTEX Shipping Network Correios?
-
-No Admin VTEX, acesse Envio > Localidades, ou digite Localidades na barra de busca no topo da página.
-Clique em Criar localidade.
-Em Status, acione o toggle  para criar a localidade como Ativa, ou deixe-o desativado  para que a nova localidade esteja Pausada. Somente localidades ativas recebem novos pedidos.
-Em Identificação, determine o nome da localidade sendo criada. Este nome é visível somente no seu Admin VTEX.
-Em Seller, selecione um seller para associar à localidade. O seller é quem possui os produtos sendo vendidos.
-
-Cada localidade pode ser associada a um único seller.
-Em Endereço, defina o local físico onde se situa a localidade.
-
-Clique no botão Próximo.
-Feito isso, você terá concluído a Etapa 1 será redirecionado para a segunda e última etapa de criação, a Capacidade operacional.
-
-Etapa 2: Capacidade operacional
-Para realizar esta etapa, siga os passos abaixo:
-
-Em Gostaria de configurar uma capacidade?, clique em umas das alternativas:
-Configurar: a localidade tem um limite na capacidade de receber pedidos e, caso este limite seja atingido, novos pedidos podem ser alocados em outras localidades. Isso aumenta a eficiência da sua operação e aumenta as chances de cumprir as promessas de envio feitas aos clientes.
-Manter ilimitada: a localidade mantém a capacidade irrestrita de receber novos pedidos. Como não é possível determinar um limite máximo, a localidade pode receber mais pedidos do que é capaz de dar vazão no tempo de envio prometido, o que pode causar um atraso nos envios e consequente frustração de clientes.
-
-## 1. O que é o VTEX Shipping Network Correios?
-
-## 1. O que é o VTEX Shipping Network Correios
+|  | **Guia de onboarding** |  |
+| :---: | :---: | :---: |
+| Parte I | Parte II | Parte III |
+| [Trilha da loja VTEX](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/7bORBaAr4rIG3JgRi68jIK) | [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) |
 
+<div>
+  <img src="//images.ctfassets.net/alneenqid6w5/4CgTVLjK3cazg4dDyVlB8m/92967dbc04e132e4901ba7080d76f2e5/announcement_under_table_image_PT.png" alt="Imagem de ecommerce">
+</div>
diff --git a/docs/tracks/pt/the-reservation.md b/docs/tracks/pt/the-reservation.md
index defb5ed73..01f18ebde 100644
--- a/docs/tracks/pt/the-reservation.md
+++ b/docs/tracks/pt/the-reservation.md
@@ -35,7 +35,7 @@ Este é o fluxo da reserva na VTEX:
  
  3. Finalmente, uma vez que o pedido está na etapa de preparo para a entrega, os itens passam para o status `Reserva reconhecida`. Esse status indica que o item já não existe mais no estoque físico.      
 
-![reservation pt](https://images.ctfassets.net/alneenqid6w5/7nDqT6kSvWTESRqZLzZutZ/9009856b729712a613d4d6c36612fd9a/reservation_pt.png)
+![reservation pt](//images.ctfassets.net/alneenqid6w5/7nDqT6kSvWTESRqZLzZutZ/9009856b729712a613d4d6c36612fd9a/reservation_pt.png)
 
 <div class="alert alert-warning">
 A VTEX não desconta automaticamente os itens dos estoques, mesmo depois que eles passam para o status <code>Reserva reconhecida</code>. Os itens comprados continuarão nesse status até que o ERP ou o lojista realizem a baixa no estoque.
diff --git a/docs/tracks/pt/unified-commerce-101.md b/docs/tracks/pt/unified-commerce-101.md
index 3149bb2ce..6772bc85c 100644
--- a/docs/tracks/pt/unified-commerce-101.md
+++ b/docs/tracks/pt/unified-commerce-101.md
@@ -3,8 +3,8 @@ title: 'Omnichannel'
 id: 2LGAiUnHES1enjHsfi8fI3
 status: PUBLISHED
 createdAt: 2020-06-30T20:38:48.297Z
-updatedAt: 2023-05-31T14:45:20.583Z
-publishedAt: 2023-05-31T14:45:20.583Z
+updatedAt: 2023-07-26T18:50:02.780Z
+publishedAt: 2023-07-26T18:50:02.780Z
 firstPublishedAt: 2020-06-30T20:45:00.959Z
 contentType: trackArticle
 productTeam: Shopping
@@ -16,24 +16,24 @@ trackSlugPT: estrategias-de-comercio-unificado
 
 A evolução do varejo online trouxe uma série de melhorias à experiência do cliente, e uma das mais relevantes talvez seja a que transformou a relação multicanal entre cliente e loja em uma relação de omnicanalidade.
 
-![32. Unified Commerce 101 - 2](https://images.ctfassets.net/alneenqid6w5/hZLcXdCI6EXa4lR4cNShc/1bb91baac796afbdedb890b1c6362e90/32._Unified_Commerce_101_-_2.png)
+![32. Unified Commerce 101 - 2](//images.ctfassets.net/alneenqid6w5/hZLcXdCI6EXa4lR4cNShc/1bb91baac796afbdedb890b1c6362e90/32._Unified_Commerce_101_-_2.png)
 
-Em uma arquitetura __multicanal__, cada canal se comunica de forma independente com a loja, seja o e-comerce, as lojas físicas, o SAC, as mídias sociais etc. Quando um cliente interage com um desses canais, a loja não tem conhecimento algum sobre quem é esse cliente.
+Em uma arquitetura __multicanal__, cada canal se comunica de forma independente com a loja, seja o ecomerce, as lojas físicas, o SAC, as mídias sociais etc. Quando um cliente interage com um desses canais, a loja não tem conhecimento algum sobre quem é esse cliente.
 
 Já em uma arquitetura __omnichannel__, os dados do cliente são compartilhados entre os canais da loja. Isso significa que, quando o cliente que já interagiu com a loja interage por um novo canal, a loja tem conhecimento sobre quem é esse cliente, qual é o histórico de pedidos dele, o perfil de compras etc.
 
-No omnichannel, entretanto, os pedidos ainda são processados de forma isolada. Embora haja compartilhamento de dados, os pedidos que acontecem no e-commerce vivem apenas no e-commerce, os que acontecem na loja física vivem apenas na loja física e assim por diante. Um pedido feito em um canal não pode ser concluído em outro, por exemplo.
+No omnichannel, entretanto, os pedidos ainda são processados de forma isolada. Embora haja compartilhamento de dados, os pedidos que acontecem no ecommerce vivem apenas no ecommerce, os que acontecem na loja física vivem apenas na loja física e assim por diante. Um pedido feito em um canal não pode ser concluído em outro, por exemplo.
 
 O __Comércio Unificado__ resolve esse problema.
 
-![32. Unified Commerce 101 - 1](https://images.ctfassets.net/alneenqid6w5/4JVV00Jk5F0P5S27c9BLCo/71bbbb249454b39188d08a87d2de0761/32._Unified_Commerce_101_-_1.png)
+![32. Unified Commerce 101 - 1](//images.ctfassets.net/alneenqid6w5/4JVV00Jk5F0P5S27c9BLCo/71bbbb249454b39188d08a87d2de0761/32._Unified_Commerce_101_-_1.png)
 
 O Comércio Unificado é uma evolução do omnichannel: além do compartilhamento de dados, nessa estratégia acontece também a __unificação do sistema de processamento e gerenciamento dos pedidos__. Na prática, isso significa que todo pedido realizado em um canal da loja fica não apenas visível por outros canais como pode ser processado por eles.
 
 Veja abaixo alguns dos cenários possibilitados pelo Comércio Unificado:
 - __Prateleira Infinita__: cliente compra em um canal (em uma loja física, por exemplo) e recebe a partir do estoque de outra loja ou do Centro de Distribuição principal.
 - __Transação com carrinho misto__: cliente compra em uma loja física, retira um dos produtos na hora e recebe o outro em casa a partir de outro estoque.
-- __Retirada em loja__: cliente compra no e-commerce e retira os produtos em uma loja física.
+- __Retirada em loja__: cliente compra no ecommerce e retira os produtos em uma loja física.
 
 Na VTEX, estes e diversos outros cenários são possíveis porque o catálogo da marca fica acessível a todos os canais e o Sistema de Gestão de Pedidos faz a orquestração de todos os pedidos, sejam eles feitos online ou offline.
 
diff --git a/docs/tracks/pt/unified-commerce.md b/docs/tracks/pt/unified-commerce.md
new file mode 100644
index 000000000..7a2853642
--- /dev/null
+++ b/docs/tracks/pt/unified-commerce.md
@@ -0,0 +1,51 @@
+---
+title: 'Comércio unificado'
+id: 5Qvw31yH2FPDBl14K5xXHA
+status: PUBLISHED
+createdAt: 2024-02-20T20:19:58.572Z
+updatedAt: 2024-04-03T12:14:19.783Z
+publishedAt: 2024-04-03T12:14:19.783Z
+firstPublishedAt: 2024-02-22T14:08:56.252Z
+contentType: trackArticle
+productTeam: Others
+slug: comercio-unificado
+locale: pt
+trackId: 3J7WFZyvTcoiwkcIVFVhIS
+trackSlugPT: proximos-passos-apos-o-go-live
+---
+
+[Comércio unificado](https://help.vtex.com/pt/tracks/unified-commerce-strategies--3WGDRRhc3vf1MJb9zGncnv) é uma evolução do omnichannel. Além do compartilhamento de dados, nessa estratégia acontece também a unificação do sistema de processamento e gerenciamento dos pedidos. Isso significa que todo pedido realizado em um canal da loja fica não apenas visível por outros canais de venda como o pedido pode ser processado neles. E em um contexto cada vez mais conectado, operar com contas franquia e [sellers white labels](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) pode ser muito estratégico para o negócio.
+
+## Contas franquia e seller white label
+
+[Contas franquias](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) são contas associadas a uma [conta principal](https://help.vtex.com/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). Para empresas que possuam múltiplas lojas físicas, franqueados ou multimarcas, é possível criar contas-franquia vinculadas à conta principal da marca.
+
+![Conta principal](//images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/f6dc3d52f41b4acbf54704f177df49f4/next_steps_image1_PT.png)
+
+Esse modelo compartilha as informações do Catálogo e [frente de loja](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), permitindo que o inventário das contas franquia seja disponibilizado para venda na loja principal e que diversas estratégias de comércio unificado possam ser utilizadas, tais como, [Ship from store](#ship-from-store), [lojas físicas como pontos de retirada](#pontos-de-retirada) e [prateleira infinita](https://help.vtex.com/en/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
+
+Outras vantagens em operar com contas franquia estão listadas a seguir:
+
+- Contas exclusivas para cada loja, permitindo melhor gestão do acesso de colaboradores.
+- Melhor gerenciamento e escalabilidade de recursos devido ao cadastro de docas e estoques para cada loja.
+- Gestão de promoções específicas para cada conta, sem a obrigatoriedade de contratar uma nova [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).
+- Possibilidade de pagamento no ambiente da conta principal ou da franquia ([split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx)/pedido).
+- [Regionalização de sellers](https://help.vtex.com/pt/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw) (preço e inventário).
+- Aumento na performance operacional por meio da utilização de requisições simultâneas no checkout de cada loja. Em uma conta padrão, onde a [estratégia de envio](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#configuracoes-obrigatorias-em-logistica) é cadastrada na conta principal, as requisições são processadas em fila, gerando um possível acúmulo de requisições e aumento de interrupções (timeout). Sempre que a interrupção ocorre, uma mensagem de erro aparece no checkout e o cliente precisa clicar em F5 ou no botão de atualizar para prosseguir com a compra. Este comportamento gera impacto negativo na experiência do cliente e diminui a taxa de conversão da loja.
+
+<div class="alert alert-warning">
+  <p>As <a href="https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">contas franquias</a> atuam como um <a href="https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a> da conta principal. Quando um cliente adiciona produtos no carrinho de compras e simula o frete no site da conta principal, o <a href="https://help.vtex.com/pt/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo de seleção de sellers white label</a> define automaticamente qual conta franquia será responsável pelo <a href="https://help.vtex.com/pt/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP">fulfillment</a> do pedido. Caso ocorra o cenário onde um ou mais produtos do carrinho não estejam disponíveis na conta franquia selecionada, o sistema definirá um outra conta disponível para realizar o envio dos produtos faltantes, permitindo que ocorra mais de uma entrega para o mesmo pedido. Este processo acontece de forma interna na plataforma, sem que o cliente tenha conhecimento dos sellers envolvidos.</p>
+</div>
+
+## Ship from store
+
+Lojas físicas podem funcionar como mini centros de distribuição, possibilitando o envio de produtos direto do seu estoque para o endereço do cliente. Este tipo de operação reduz custos e tempo de envio, melhorando o planejamento logístico da empresa. Saiba mais em [Ship From Store](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl).
+
+## Pontos de retirada
+
+Configurar [pontos de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) física de produtos contribui para operações que aplicam [estratégias de comércio unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/2LGAiUnHES1enjHsfi8fI3), onde a experiência de compra do cliente é otimizada por meio da venda e gerenciamento de pedidos centralizados e disponibilidade de múltiplas opções de entrega. Na VTEX, os seguintes pontos de retirada podem ser cadastrados:
+
+- Centro de distribuição (CD).
+- Loja física própria.
+- Loja física franqueada.
+- Loja física ou ponto de retirada de terceiro, utilizando um sistema de armazenamento seguro, como por exemplo, um armário (_locker_).
diff --git a/docs/tracks/pt/unified-search.md b/docs/tracks/pt/unified-search.md
index a140c9d62..672d79e0c 100644
--- a/docs/tracks/pt/unified-search.md
+++ b/docs/tracks/pt/unified-search.md
@@ -1,10 +1,10 @@
 ---
-title: 'Busca unificada'
+title: 'Busca unificada no VTEX Sales App'
 id: 9sXeVwoD60qYYgRJ11r5F
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-08-05T13:47:18.180Z
-updatedAt: 2023-05-31T14:45:09.383Z
-publishedAt: 2023-05-31T14:45:09.383Z
+updatedAt: 2024-05-03T13:22:04.096Z
+publishedAt: 2024-05-03T12:35:21.520Z
 firstPublishedAt: 2021-08-05T14:45:51.056Z
 contentType: trackArticle
 productTeam: Shopping
@@ -14,33 +14,42 @@ trackId: 4BYzQIwyOHvnmnCYQgLzdr
 trackSlugPT: instore-usando-o-app
 ---
 
-Na Prateleira Infinita do VTEX Sales App, o vendedor pode buscar pelos produtos desejados e adicioná-los ao carrinho. Para isso, é necessário clicar na lupa na barra superior do VTEX Sales App e digitar o nome do produto, o código de referência ou o EAN.
+Com a [prateleira infinita](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn) do VTEX Sales App, o vendedor pode buscar por produtos que não estão limitados ao estoque da loja e adicioná-los ao carrinho. Para buscar um produto, clique no ícone de lupa <i class="fas fa-search"></i> e a barra de busca será exibida no topo da página inicial da loja.  Digite o nome do produto, código referência, SKU ID  ou EAN para encontrar o que precisa.
 
-![instore-search-pt](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/a7145393acb3d5517f53c0925a9d45b2/instore-search-pt.png)
+<div class = "alert alert-info">
+Para melhorar a experiência em cenários em que a conexão com a internet esteja em baixa velocidade, esta funcionalidade conta com recursos otimizados que fazem uso do cache do navegador para otimizar a busca.
+</div>
 
-A busca do VTEX Sales App é unificada, ou seja, ao fazer uma busca no aplicativo, o vendedor pesquisa tanto no estoque local (da loja física em si) quanto no de outras lojas físicas e dos centros de distribuição associados ao ecommerce.
+![Barra busca - PT](//images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/3c7031056980ae911e2436933bee89fa/Tela_1_barra_busca.gif)
 
-![instore-search-plp-pt](https://images.ctfassets.net/alneenqid6w5/1WEugAiPUVHRVTL1ph3zv2/dbe2ac9add28b4576a4a6e7b3d5c227e/instore-search-plp-pt.png)
+A busca do VTEX Sales App é unificada, o que significa que ao fazer uma busca no aplicativo a pesquisa é feita tanto no estoque local (da sua loja física) quanto no de outras lojas físicas e nos centros de distribuição associados ao ecommerce.
 
-Ao clicar na seta <i class="fas fa-chevron-down"></i> ao lado de um produto, você poderá ver suas variações, as opções de entrega, a quantidade a ser adicionada ao carrinho e os botões `Adicionar ao carrinho` e `Mais detalhes`.
+Os resultados da busca mostram os produtos organizados para melhorar a experiência do cliente, com imagens que facilitam a identificação dos produtos e informações relevantes para o vendedor.
 
-![instore-search-details-pt](https://images.ctfassets.net/alneenqid6w5/1itzXskqYPkJ4CghrWihy8/c792832bed73d6e28782c35ab8b6fb55/Group_2__1_.png)
+![Busca unificada - PT](//images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/c918c2a6179fc8899f9bc3d899b60121/Busca_unificada_VTEX_Sales_App.png)
+
+Ao clicar na opção `Adicionar ao carrinho`, as seguintes informações do produto serão exibidas:
+
+- Variação do produto, SKUs.
+- Disponibilidade das opções de entrega.
+- Quantidade do produto que será adicionada no carrinho.
+
+Para adicionar o produto ao carrinho, selecione a variação, entrega e quantidade desejada e clique em `Adicionar ao carrinho`.
+
+![Carrinho - PT](//images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/f4a3612b1e625a03b446831229bbf605/Adicionar_ao_carrinho_VTEX_Sales_App.png)
 
 ## Filtros
 
+Os filtros permitem que a busca seja refinada de acordo com as preferências do cliente. Com a possibilidade de associar diferentes filtros, é possível realizar uma combinação precisa de critérios de pesquisa e, se necessário, remover qualquer filtro de forma simples.
 Para utilizar os filtros de busca no VTEX Sales App, é necessário antes instalar e configurar o [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG). Nesse contexto, observe alguns pontos de atenção:
-
-* É fundamental configurar os filtros que serão exibidos, conforme o artigo [Configuração da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx), caso contrário todas as informações do produto serão atributos filtráveis no VTEX Sales App.
-* A opção **Autocomplete** não se aplica à busca no VTEX Sales App, portanto pode ser deixada vazia.
-* Qualquer alteração realizada na configuração de busca também vai se aplicar ao ecommerce caso a ferramenta utilizada seja o VTEX Intelligent Search.
+- É fundamental configurar os filtros que serão exibidos, conforme o artigo [Configuração da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx), caso contrário todas as informações do produto serão atributos filtráveis no VTEX Sales App.
+- Qualquer alteração realizada na configuração de busca também será aplicada ao ecommerce caso a ferramenta de busca utilizada seja o VTEX Intelligent Search.
 
 Além das configurações do VTEX Intelligent Search, é preciso [entrar em contato com o time de suporte da VTEX](https://support.vtex.com/hc/pt-br/requests) para habilitar a funcionalidade de filtros no VTEX Sales App.
 
-Uma vez que os filtros estiverem habilitados, é possível utilizar esse recurso seguindo o procedimento abaixo durante a busca por produtos.
-
-1. Se estiver utilizando o VTEX Sales App em um dispositivo móvel, como um smartphone, clique em `Filtrar busca`. Se estiver usando outro dispositivo com uma tela maior, pule este passo.
+Uma vez que os filtros estejam habilitados, é possível utilizar esse recurso seguindo o procedimento abaixo durante a busca por produtos:
+1. Se estiver utilizando o VTEX Sales App em um dispositivo móvel, como um smartphone, clique em `Filtros`.  Se estiver usando outro dispositivo com uma tela maior, pule este passo.
 2. Selecione os filtros desejados.
-3. Clique em `Filtrar busca`.
+3. Clique em `Filtrar`.
 
 Os resultados exibidos serão filtrados de acordo com as suas preferências.
-
diff --git a/docs/tracks/pt/using-custom-controls.md b/docs/tracks/pt/using-custom-controls.md
index 0f0426983..a426f132c 100644
--- a/docs/tracks/pt/using-custom-controls.md
+++ b/docs/tracks/pt/using-custom-controls.md
@@ -31,7 +31,7 @@ Para criar um controle customizado, siga o passo a passo abaixo:
 2. Clique em __Layout__
 3. Clique na pasta __CMS__
 4. Logo abaixo, clique na pasta __Custom Elements__
-5. Clique no botão __Add__![8 1](https://images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
+5. Clique no botão __Add__![8 1](//images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
 6. Preencha o campo __Name__ com o nome do controle customizado
 7. Preencha o campo __Tag name__. É este nome que será usado no controle no momento de adicioná-lo ao template.
 8. Selecione o tipo do controle em __Type__
diff --git a/docs/tracks/pt/via-varejo-marketplace.md b/docs/tracks/pt/via-varejo-marketplace.md
index f1fac0717..01b608211 100644
--- a/docs/tracks/pt/via-varejo-marketplace.md
+++ b/docs/tracks/pt/via-varejo-marketplace.md
@@ -1,10 +1,10 @@
 ---
-title: 'Via Marketplace'
+title: 'Casas Bahia Marketplace'
 id: 3rymwJDuc5Z6lQtsyTINim
 status: PUBLISHED
 createdAt: 2020-03-30T17:59:31.535Z
-updatedAt: 2022-01-18T21:38:11.833Z
-publishedAt: 2022-01-18T21:38:11.833Z
+updatedAt: 2023-11-30T20:51:57.221Z
+publishedAt: 2023-11-30T20:51:57.221Z
 firstPublishedAt: 2020-03-30T18:11:59.947Z
 contentType: trackArticle
 productTeam: Channels
@@ -14,10 +14,10 @@ trackId: 3E9XylGaJ2wqwISGyw4GuY
 trackSlugPT: configurar-integracao-da-via-varejo
 ---
 
-A [Via Marketplace](https://www.viavarejo.com.br/) é uma das líderes do e-commerce brasileiro, com mais de 280 milhões de visitas mensais e 15 milhões de usuários ativos.
+A [Casas Bahia Marketplace](https://marketplace.via.com.br/) é uma das líderes do e-commerce brasileiro, com mais de 280 milhões de visitas mensais e 15 milhões de usuários ativos.
 
-Usando a integração nativa com o Marketplace da Via Varejo, você poderá expor e vender seus produtos nas lojas online das [Casas Bahia](https://www.casasbahia.com.br/), [Ponto Frio](http://pontofrio.com.br/) e [Extra](http://extra.com.br/).
+Usando a integração nativa com a Casas Bahia Marketplace, você poderá expor e vender seus produtos nas lojas online das [Casas Bahia](https://www.casasbahia.com.br/), [Ponto](http://pontofrio.com.br/) e [Extra](http://extra.com.br/).
 
-![via marketplace](https://images.ctfassets.net/alneenqid6w5/1h9W5eT3dKZAKcyTdt5oc0/cca5587318be15d4a3284cf735942986/via_marketplace.JPG)
+![Casas Bahia Marketplace](//images.ctfassets.net/alneenqid6w5/nBFPh57qyKQcaPmseMIcj/9fd735f8bd3a713d26e3655aa0419601/Casas_Bahia_Marketplace.jpg)  
 
-A configuração com a Via tem como objetivo enviar o catálogo de produtos da sua loja VTEX para os 3 marketplaces que fazem parte do grupo Via, permitindo que você anuncie seus produtos para milhões de clientes e aumente suas vendas.
+A configuração com a Casas Bahia Marketplace tem como objetivo enviar o catálogo de produtos da sua loja VTEX para os 3 marketplaces que fazem parte do Grupo Casas Bahia, permitindo que você anuncie seus produtos para milhões de clientes e aumente suas vendas.  
diff --git a/docs/tracks/pt/viewing-the-email-history-of-an-order.md b/docs/tracks/pt/viewing-the-email-history-of-an-order.md
index afc65647c..b7a6c2cdb 100644
--- a/docs/tracks/pt/viewing-the-email-history-of-an-order.md
+++ b/docs/tracks/pt/viewing-the-email-history-of-an-order.md
@@ -3,8 +3,8 @@ title: 'Ver histórico de e-mails de um pedido'
 id: 13YJE9CKzeduRfVplgjC88
 status: PUBLISHED
 createdAt: 2020-01-10T14:07:26.022Z
-updatedAt: 2023-03-31T21:10:54.264Z
-publishedAt: 2023-03-31T21:10:54.264Z
+updatedAt: 2023-09-23T00:49:55.012Z
+publishedAt: 2023-09-23T00:49:55.012Z
 firstPublishedAt: 2020-01-13T14:38:41.810Z
 contentType: trackArticle
 productTeam: Marketing & Merchandising
@@ -21,3 +21,7 @@ Esse recurso é útil para acompanhar toda a comunicação por email com o clien
 Para ver o histórico de emails, acesse o módulo **Pedidos**, entre no pedido desejado e desça a tela até a linha do tempo. Lá você encontra os registros de e-mails enviados.
 
 O sistema que faz esse registro chama-se __Conversation Tracker__. Para entender mais a fundo como ele funciona, veja o artigo [Como é feita a comunicação com o cliente durante o fluxo pedido](https://help.vtex.com/pt/tutorial/conversation-tracker--tutorials_195).
+
+<div class = "alert alert-info">
+Como a comunicação com o cliente é uma responsabilidade do marketplace, apenas pedidos com origem marketplace tem o histórico de email transacionais. Pedidos com origem fulfillment não mantêm tal histórico.
+</div>
diff --git a/docs/tracks/pt/vtex-modules-i.md b/docs/tracks/pt/vtex-modules-i.md
new file mode 100644
index 000000000..25bb7eb78
--- /dev/null
+++ b/docs/tracks/pt/vtex-modules-i.md
@@ -0,0 +1,354 @@
+---
+title: 'Módulos da VTEX I'
+id: 75MX4aorniD0BYAB8Nwbo7
+status: PUBLISHED
+createdAt: 2024-01-17T19:53:53.326Z
+updatedAt: 2024-02-23T00:42:01.506Z
+publishedAt: 2024-02-23T00:42:01.506Z
+firstPublishedAt: 2024-02-22T14:07:05.427Z
+contentType: trackArticle
+productTeam: Others
+slug: modulos-da-vtex-i
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+A plataforma VTEX se organiza em diferentes módulos, cada um deles responsável por uma parte da operação da loja. Este artigo apresenta uma visão geral e principais configurações dos seguintes módulos:
+
+- [Catálogo](#catalogo)
+- [Preços](#precos)
+- [Promoções](#promocoes)
+- [Logística](#logistica)
+
+<div class="alert alert-info">
+O artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ">Módulos da VTEX II</a> apresenta os módulos <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagamentos">Pagamentos</a>, <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos">Pedidos</a>, e <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout">Checkout</a>.
+</div>
+
+## Catálogo
+
+[Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) é o módulo da VTEX onde lojistas configuram produtos para torná-los disponíveis no site da loja. É a estrutura do catálogo que define a experiência de compra dos clientes no ecommerce ao navegar nas categorias de classificação dos produtos. Uma [visão geral de Catálogo](https://help.vtex.com/pt/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe) para desenvolvedores sobre a [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api) pode ser encontrada no guia [Catalog](https://developers.vtex.com/docs/guides/catalog-overview).
+
+### Antes de começar em Catálogo
+
+Não existem configurações prévias que devam ser realizadas antes das configurações no Catálogo, mas vale ressaltar os seguintes pontos de atenção:
+
+- __Navegação do cliente no site:__ é importante que a loja planeje como deseja organizar sua [árvore de categorias](#arvore-de-categorias) e saber de antemão qual experiência de navegação deseja promover aos clientes na hierarquia de categorias.
+- __Tornar produtos disponíveis para clientes:__ para [disponibilizar um produto na loja](https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382), após as configurações de Catálogo, é preciso que o SKU tenha [preço](#precos) cadastrado e [logística](#logistica) para envio. Além disso, o CMS da loja precisa estar configurado corretamente.
+
+### Arquitetura do Catálogo
+
+A arquitetura do Catálogo apresenta alguns conceitos fundamentais: categoria, marca, produto, SKU (_Stock Keeping Unit_) e especificação. A imagem abaixo ilustra a relação entre esses conceitos:
+
+![arquitetura-catalogo-PT](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
+
+O catálogo da loja deve ser criado seguindo a ordem dos passos abaixo:
+
+1. Criação da [árvore de categorias](#arvore-de-categorias).
+2. Cadastro de [Marcas](#marcas).
+3. Cadastro de [Especificações](#especificacoes).
+4. Importação de [Produtos](#produtos).
+5. Importação de [SKUs](#skus).
+
+A tabela a seguir apresenta as principais configurações de Catálogo da loja, conforme a ordem de criação:
+
+| **Assunto** | **Configuração via Admin VTEX** | **Configuração via API++ |
+| :--- | --- | :--- |
+| 1. [Árvore de categorias](https://help.vtex.com/pt/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categorias) | [Cadastrar uma Categoria](https://help.vtex.com/pt/tutorial/cadastrando-categoria--tutorials_206) | - [Categories](https://developers.vtex.com/docs/guides/categories) <br> - [Create Category](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category) |
+| 2. [Marcas](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) | [Cadastrar marcas](https://help.vtex.com/pt/tutorial/cadastrando-marcas--tutorials_1414) | - [Brands](https://developers.vtex.com/docs/guides/brands) <br> - [Create Brand](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand) |
+| 3.1. [Especificações de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacao-de-produto) | [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106) | - [Product specifications](https://developers.vtex.com/docs/guides/product-specifications) <br> - [Create Specification](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/specification) |
+| 3.2. [Especificações de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacao-de-sku) | [Cadastrar especificações ou campos de SKU](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119) | - [SKU specifications](https://developers.vtex.com/docs/guides/sku-specifications) <br> - [Create Specification](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/specification) |
+| 4. [Produtos](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) | [Cadastrar produtos](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567) | - [Products](https://developers.vtex.com/docs/guides/products) <br> - [Create Product with Category and Brand](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product) |
+| 5. [SKUs](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) | [Preencher campos de cadastro de SKU](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY?&utm_source=autocomplete) | - [SKUs](https://developers.vtex.com/docs/guides/skus) <br> - [Create SKU](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit) |
+
+<br>
+
+<div class="alert alert-warning">
+Para saber como importar produtos de um sistema ERP (Enterprise Resource Planning) ou PIM (Product Information Manager) para a plataforma VTEX, veja o artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
+</div>
+
+#### Árvore de categorias
+
+A [árvore de categorias](https://help.vtex.com/pt/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categorias) é a definição da estrutura base do Catálogo. As categorias atuam como níveis hierárquicos de classificação de produtos, simplificando a busca do cliente e mantendo o catálogo da loja organizado. 
+
+Recomendamos a criação de uma hierarquia de até três níveis, incluindo [Departamento](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf#departamento), [Categorias](https://help.vtex.com/pt/tutorial/catalog-overview--77M8ItLhDXs6aBdQTqToVe#categorias) e [Subcategorias](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf#subcategoria). No entanto, algumas lojas podem se beneficiar de uma estrutura mais simples de dois níveis, com Departamentos e Categorias. Isso depende da complexidade da operação e tipos de produtos oferecidos.
+
+**Exemplo:** Departamento `Feminino`, Categoria `Blusas e camisas` e Subcategoria `Camisetas`.
+
+Antes de importar o catálogo da loja para a VTEX, recomendamos começar a trabalhar na árvore de categorias criando uma tabela como a ilustrada abaixo. Isto permite uma melhor visualização de como a árvore está organizada e como as especificações serão apresentadas.
+
+![catalog_arquitecture_table_PT](//images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/d28bf46e6d7b444f994f986068a3b49f/catalog_arquitecture_table_PT.png)
+
+<div class="alert alert-info">
+Informações sobre como importar especificações para back-office podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
+</div>
+
+#### Marcas
+
+[Marcas](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7i3sB8fgkqUp5NoH5yJtfh) geralmente identificam a empresa que cria ou revende um ou mais produtos. Na VTEX, é necessário cadastrar as marcas de maneira independente e, ao criar um produto, é obrigatório associá-lo a uma marca já cadastrada na loja.
+
+#### Especificações
+
+[Especificações](https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) são propriedades adicionais que podem ser atribuídas a produtos e SKUs da loja, como por exemplo, tamanho, cor, voltagem ou material. Ou seja, existem [especificações de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacao-de-produto) e [especificações de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#especificacao-de-sku).
+
+No __Catálogo__ da VTEX, as especificações são criadas na seguinte ordem:
+
+1. __Grupos de especificações__: são agregadores de campos de especificação. Devem ser atribuídos a categorias. É comum apenas um grupo ser criado no nível raiz e todos os campos de especificação serem associados a este grupo.
+2. __Campos de especificação__: são os campos que irão possuir as informações adicionais de produtos e SKUs. Devem ser atribuídos a categorias e grupos de especificações.
+3. __Valores de especificação__: são valores de escolha atribuídos aos campos de especificação.
+
+As especificações seguem a hierarquia do Catálogo, então quando um desses grupos é criado em um Departamento ou Categoria, ele é herdado nos níveis abaixo.
+
+#### Produtos
+
+O [Produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) é o nível da organização do catálogo que se localiza na hierarquia abaixo das Categorias e acima dos SKUs. Como o produto está acima do SKU na hierarquia do catálogo, podemos entendê-lo como uma definição genérica dos itens que são vendidos em sua loja. É obrigatório que um produto tenha pelo menos um SKU associado a ele.
+
+#### SKUs
+
+[SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) (_Stock Keeping Unit_) é uma variação do produto e representa a unidade física em estoque que é adquirida pelo cliente. O SKU é o último nível na organização de um catálogo e, para ficar ativo, é necessário que o SKU tenha uma imagem e especificações preenchidas.
+
+### Configurações opcionais do Catálogo
+
+A tabela a seguir apresenta outras configurações opcionais de Catálogo na VTEX:
+
+| **Funcionalidade** | **Descrição** | **Saiba mais** |
+| :---: | :--- | :--- |
+| Coleções | Uma coleção representa o agrupamento de dois ou mais produtos que podem ou não compartilhar características específicas. <br> As coleções podem ser criadas com o propósito de associar produtos com base em critérios diversos, como datas comemorativas, lançamentos ou produtos mais vendidos. | __Help Center__ <br> - [Coleções - Definição de conceito](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4hN41yU8IPeb8HKmmaXoca) <br> - [Cadastrar Coleções (Beta)](https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye)  <br> __Developer Portal__  <br> - [Create Collection](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection/) <br> - [Get All Inactive Collections](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/collection/inactive) <br> - [Get All Collections](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/collection/search) <br> - [Get Collections by search terms](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/collection/search/-searchTerms-) <br> - [Import File Example](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/collection/stockkeepingunit/importfileexample) <br> - [Add products to Collection by imported file](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/collection/-collectionId-/stockkeepingunit/importinsert) |
+| Anexos | Um anexo é uma customização opcional e gratuita do produto, usada para adicionar informações a um SKU. | __Help Center__ <br> - [Cadastrar um anexo](https://help.vtex.com/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU) <br> - [Como criar um anexo de assinatura](https://help.vtex.com/pt/tutorial/como-criar-um-anexo-de-assinatura--2bUuKyPflA8cOGLv8OvaKK?&utm_source=autocomplete) <br> - [O que é um Anexo?](https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete)  <br> __Developer Portal__ <br> - [Catalog API - Attachment](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog/pvt/attachment/-attachmentid-) <br> - [Catalog API - SKU attachment](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuattachment) |
+| Assembly Options | Assembly Options é um tipo de anexo para casos complexos, como personalização de produtos, no qual você precisa gerenciar diferentes combinações de produtos, quantidade, itens adicionais, custos e estoque, e exibir essas opções na página do produto. | __Developer Portal__ <br> - [Assembly Options](https://help.vtex.com/en/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH) <br> - [Assembly Option App](https://developers.vtex.com/docs/guides/assembly-options-app) |
+| Serviços | Serviço com custo extra que pode ser oferecido com um produto de forma opcional. Ele é usado para atribuir um serviço adicional a um SKU, como embalagem de presente, personalização ou acordos de garantia especial. | __Help Center__ <br> - [O que é um Serviço?](https://help.vtex.com/pt/tutorial/o-que-e-um-servico--46Ha8CEEQoC6Y40i6akG0y) <br> - [Gerenciamento de Serviços](https://help.vtex.com/pt/tutorial/gerenciamento-de-servicos--3sGqSI93t878ETAWzCZ0E2) <br> - [Importação de Serviços](https://help.vtex.com/pt/tutorial/importacao-de-servicos--2LRgMnGbX0af7krrs6tXy3) <br> - [Relatório de Serviços](https://help.vtex.com/pt/tutorial/relatorio-de-servicos--7djPWfxtf9qb6hFTOgKDE8) <br> - [Agendamento de Serviços](https://help.vtex.com/pt/tutorial/agendamento-de-servicos--78HPYBxDCmpCfa8i40zo7R)  <br> __Developer Portal__ <br> - [Catalog API - SKU service](https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog/pvt/skuservice/-skuServiceId-) <br> - [Catalog API - SKU service attachment](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicetypeattachment) <br> - [Catalog API - SKU service type](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicetype) <br> - [Catalog API - SKU service value](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuservicevalue) |
+| Kits | Um kit é um conjunto de SKUs que são vendidos juntos, ou seja, um SKU composto por um ou mais SKUs. | __Help Center__ <br> - [O que é um kit?](https://help.vtex.com/pt/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28) <br> - [Cadastrar kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) <br> __Developer Portal__ <br> - [Catalog API - SKU Kit](https://developers.vtex.com/vtex-rest-api/reference/catalog-api-get-sku-kit) |
+
+## Preços
+
+[Preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) é o módulo da VTEX responsável pela criação, edição e armazenamento dos dados de preços dos SKUs da loja. Para que um produto seja vendido, o cliente precisa saber quanto custa cada item exibido na loja. O módulo de preços possui funcionalidades que permitem o uso de diferentes estratégias de precificação no seu negócio.
+
+### Antes de começar em Preços
+
+Antes de configurar os preços da loja, é necessário cadastrar o [Catálogo](#catalogo) com os produtos que serão vendidos. O catálogo da loja deve conter [categorias](https://help.vtex.com/pt/tutorial/cadastrando-categoria--tutorials_206), [marcas](https://help.vtex.com/pt/tutorial/cadastrando-marcas--tutorials_1414), [produtos](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567) e [SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) já cadastrados e ativos. Caso o cadastro do catálogo tenha sido realizado pela [integração com um sistema ERP](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu#integracao-com-erp), é essencial checar se as informações estão corretas antes de prosseguir. 
+
+### Como funciona o módulo Preços
+
+É importante conhecer os principais termos relacionado ao módulo, eles são apresentados na tabela a seguir:
+
+| **Termo** | **Definição** |
+| :---: | :--- |
+| Preços | Informações dos valores de venda dos SKUs da loja. |
+| [Tabelas de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) | Conjunto de preços de SKUs que pode ser aplicado a um determinado contexto, como a uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Essas tabelas guardam as informações dos preços que são exibidos no storefront da loja. |
+| Preço de custo | Preço que foi pago pela loja para adquirir o SKU. |
+| Markup | Margem de lucro desejada pela loja com a venda do SKU. |
+| [Preço base](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicao) | Valor calculado através da combinação entre o __preço de custo__ e o __markup__. É o preço de referência do SKU para todas as tabelas de preço. |
+| [Preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) | Preço de venda sugerido para um SKU. Este preço será exibido na página de produto como o preço __De__ e o preço base funciona como o preço __Por__. |
+| [Regra de preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/2rBirbpB7wLnei4dQ9KGMW) | Altera o preço de um SKU para apenas uma tabela de preço sem alterar o preço base das demais. Para isso, é necessário cadastrar uma regra de preço associada à tabela desejada. |
+| [Preço fixo](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy#definicoes) | Preço que se sobrepõe a todas as outras configurações de preços existentes numa tabela de preços. |
+| [Arredondamento de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1tUIUvF6BUkDgMsknGaMkF#definicoes) | Estratégia de precificação que se baseia no arredondamento de preços. Este método tem como objetivo influenciar a decisão de compra do consumidor ao exibir preços com um formato mais amigável e intuitivo. |
+| [Trava de preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7JZhLmI3mjBVu0RMOueoy3#definicao) | Configura as variações máximas e mínimas do preço de um item. Esta funcionalidade garante que os preços dos SKUs não sejam alterados para valores indesejados. |
+
+Mais informações sobre a arquitetura de preços podem ser encontradas no artigo [Arquitetura do sistema de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx).
+
+### Cadastrar tabela de preços
+
+A arquitetura do módulo Preços é organizada a partir de três conceitos fundamentais:
+
+- Preços
+- Tabelas de preços
+- Contextos de aplicação das tabelas de preços
+
+Os preços são as informações dos valores de venda dos seus SKUs. Estes preços são armazenados em tabelas de preços. Por sua vez, estas tabelas de preços podem ser aplicadas a diferentes contextos.
+
+O relacionamento entre preços, tabela de preço e o contexto que será aplicado está representado na imagem abaixo:
+
+![Conceito de Preços-PT](//images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/19ea7c2075d1a752b4001e652dff58c3/Conceito_de_Pre_os-PT.png)
+
+É possível cadastrar tabelas de preços para os SKUs da loja de três maneiras:
+
+- [Via Admin VTEX](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/2WQ3pVYfQpXkJnHr7VTFBv#admin)
+- [Via planilha](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#)
+- [Via API](https://developers.vtex.com/docs/api-reference/pricing-api)
+
+Preços podem ser agendados para eventos especiais, como descrito no artigo [Agendar preço](https://help.vtex.com/pt/tutorial/agendar-preco--4vVha6TGzYkguWuMOqCcCk).
+
+### Relação entre tabelas de preços e políticas comerciais
+
+Há uma diferença entre as tabelas de preços criadas para [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) e tabelas de preços criadas para outros contextos.
+
+As tabelas de preços não associadas a políticas comerciais podem ser usadas em contextos como __promoções__ e __clusters de clientes__. As tabelas criadas para políticas comerciais só podem ser associadas à própria política comercial. Assim, a tabela de preço associada a uma política comercial informa o preço dos SKUs para esta política e não pode ser associada a outros contextos.
+
+<div class="alert alert-warning">
+Os conceitos de <b>tabela de preços</b> e <a href="LINK">política comercial</a> são diferentes. A política comercial é o contexto ao qual uma tabela de preços é associada.
+</div>
+
+Ao configurar uma política comercial, é essencial [especificar a moeda que será utilizada na loja](https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE). A criação de políticas comerciais distintas, cada uma associada a uma moeda diferente, possibilita à loja exibir preços em diversas moedas para os clientes. 
+
+## Promoções
+
+Na VTEX, o lojista pode criar uma série de regras para determinar se os clientes podem ter descontos em certos contextos de compra e esses descontos devem ser aplicados. [Promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR) é o módulo VTEX responsável pela criação, edição e aplicação de descontos no carrinho de compras de clientes.
+
+### Antes de começar em Promoções
+
+Antes de configurar as promoções da loja, é necessário cadastrar o [Catálogo](https://help.vtex.com/pt/tutorial/catalogo-visao-geral--77M8ItLhDXs6aBdQTqToVe#) com os produtos que serão vendidos e estabelecer os [preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu#) dos SKUs na loja.
+
+### Como funciona o módulo Promoções
+
+Neste contexto, é importante conhecer os principais termos utilizados, conforme apresentado na tabela abaixo:
+
+| **Termo** | **Definição** |
+| :---: | :--- |
+| Promoção | Desconto concedido ao cliente, podendo estar associado a um ou mais produtos do carrinho, ou ainda ao frete ou a um brinde. |
+| Cupom | Código promocional, composto de uma sequência de letras e números. Os cupons são associados a promoções sobre o valor do carrinho. Assim, ao informar o código de um cupom válido no momento da compra, o cliente pode obter descontos sobre o valor do pedido. |
+| Audiência de campanha | Audiência de campanha é uma funcionalidade que permite definir o [público-alvo](https://help.vtex.com/pt/tutorial/audiencias-de-campanhas--3o7lhpNseXY2WmjZO0gQ6m#publico-alvo) para uma promoção. A funcionalidade consiste em criar critérios para segmentar clientes. A partir desses critérios, a plataforma VTEX valida automaticamente se os clientes são elegíveis a uma determinada audiência de campanha e, consequentemente, às [promoções de campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) associadas. |
+| Promoção de campanha | A promoção de campanha é sempre atrelada a uma audiência de campanha, ou seja, um público alvo específico. Uma promoção desse tipo será aplicada somente para o público-alvo definido na campanha. |
+
+### Criar promoções
+
+Na VTEX, o lojista pode criar uma série de regras que, de acordo com o contexto da compra, determinam se e como o desconto será aplicado. Entre os parâmetros considerados por essas regras, estão: listas de produtos, listas de clientes, intervalos de CEP, valor mínimo de itens no carrinho, entre outros.
+
+Os descontos podem ser de dois tipos principais:
+
+- __Nominal__: desconto de um valor bruto, como R$ 20.
+- __Percentual__: desconto de um valor percentual, como 10% do valor total do carrinho.
+
+Há seis tipos diferentes de promoções, cada uma relacionada a um cenário diferente:
+
+| **Tipo de promoção** | **Definição** |
+| :---: | :--- |
+| [Promoção Regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) | Promoção que permite à loja oferecer descontos de forma flexível, combinando múltiplas condições, restrições e benefícios. |
+| [Compre Junto](https://help.vtex.com/pt/tutorial/compre-junto--tutorials_323) | Promoção utilizada para conceder desconto para produtos quando colocados ao mesmo tempo no carrinho. O desconto pode ser aplicado em ambos os produtos. Ainda há a opção de o desconto ser aplicado apenas se for inserida no carrinho uma determinada quantidade de um dos produtos. |
+| [Leve Mais Por Menos](https://help.vtex.com/pt/tutorial/leve-mais-por-menos--tutorials_325) | Promoção usada para conceder desconto quando o cliente adiciona várias unidades do mesmo produto ao carrinho. |
+| [Desconto Progressivo](https://help.vtex.com/pt/tutorial/desconto-progressivo--tutorials_324) | Promoção utilizada quando se deseja oferecer um percentual de desconto para determinada quantidade de produtos inseridos no carrinho. |
+| [Compre e Ganhe](https://help.vtex.com/pt/tutorial/compre-e-ganhe--tutorials_322) | Promoção utilizada para oferecer frete grátis ou um brinde caso determinado produto seja comprado. |
+| [Promoção de Campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) | Promoção que é sempre atrelada a uma audiência de campanha, ou seja, a um público alvo específico. |
+
+Para todas as promoções, é possível definir um período de validade, além de restrições e limitações de uso. Promoções também podem ser agendadas para eventos especiais, como descrito no artigo [Agendamento para eventos especiais](https://help.vtex.com/pt/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI#agendar-promocoes).
+
+Mais informações sobre possibilidades de aplicação de promoções podem ser conferidas no artigo [Exemplos de promoção](https://help.vtex.com/pt/tutorial/exemplos-de-promocao--5A8UTc7knvAscxo7e7rMFD).
+
+### Criar cupons
+
+É possível criar cupons de desconto pelo [Admin VTEX](https://help.vtex.com/pt/tutorial/criar-cupom-beta--7lMk3MmhNp2IEccyGApxU) ou por [API](https://developers.vtex.com/docs/guides/creating-and-managing-coupons-with-promotions-api). Para ser utilizado, um cupom precisa estar vinculado a pelo menos uma promoção. 
+
+<div class="alert alert-warning">
+Há uma quantidade limitada de cupons ativos. A reutilização de cupons é altamente recomendada, uma vez que um grande número de cupons pode comprometer o desempenho do módulo de Promoções.
+</div>
+
+### Criar promoções de campanha
+
+Antes de criar uma promoção de campanha, é necessário criar uma [audiência de campanha](https://help.vtex.com/pt/tutorial/criar-audiencia-de-campanha--6cnuDZJzIkIeocewAQQK4K) para definir o público alvo da promoção. Assim, é possível selecionar segmentos de clientes elegíveis na promoção, que funcionam como gatilho, a partir dos critérios definidos pelo lojista.
+
+Uma vez que a audiência de campanha foi criada, é preciso associá-la a uma [Promoção Regular](https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327), criando assim uma promoção de campanha. Esse tipo de promoção engloba todas as possibilidades presentes na [Promoção Regular](https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327) e algumas opções a mais, que são:
+
+- Público-alvo específico.
+- Frete grátis para todos os fretes disponíveis.
+- Tabela de preços promocionais.
+- Brinde entregue por sellers.
+
+### Destaque de promoções na página de produto
+
+É possível dar destaque a uma promoção na página do produto (PDP). Para isso, basta seguir as passos abaixo:
+
+1. [Crie uma promoção](https://help.vtex.com/pt/tutorial/criar-promocoes--tutorials_320) de qualquer tipo, com exceção da promoção Compre Junto.
+2. Ative o campo __Destaque nos produtos__ no formulário da promoção.
+3. Salve a promoção.
+4. No [CMS Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj), insira o controle de exibição de promoção no template: `<vtex.cmc:discountHightLight/>`. 
+
+### Sincronização de datas de promoção, banners e ativos digitais
+
+É importante se certificar de uma coordenação perfeita ao sincronizar a linha do tempo das promoções com as datas de entrega dos banners e ativos digitais. Para isso, as datas das promoções e dos banners devem ser verificados. Esse alinhamento estratégico garante que as campanhas promocionais sejam apoiadas por materiais visuais oportunos e relevantes, maximizando seu impacto e eficácia.
+
+## Logística
+
+Na VTEX, o módulo [Logística](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx) é o responsável pela [logística e o fulfillment](https://help.vtex.com/pt/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP) de pedidos da loja, incluindo planejamento, transporte, armazenamento de produtos e envio de pedidos a clientes.
+
+### Antes de começar em Logística
+
+Para realizar as configurações de logística, é necessário ter concluído as seguintes etapas:
+
+- __Cadastrar catálogo__: como o fulfillment de pedidos está relacionado ao armazenamento de itens, os produtos e SKUs da loja precisam estar cadastrados no [Catálogo](#catalogo).
+- __Configurar política comercial__: as [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) moldam a experiência do cliente no site de uma loja, segmentando desde condições de venda para cada público, até produtos ofertados, preços, promoções e formas de envio.
+
+Além disso, caso o modelo de negócio envolva lojas internacionais e vendas [cross-border](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/5qgXy9Erm7FDP3UB5Ox8Bs), é importante primeiro considerar qual seria o modelo de [arquitetura da loja](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitetura-da-loja).
+
+### Configurações obrigatórias em Logística
+
+O conjunto de configurações essenciais de logística de uma loja VTEX é chamado de [Estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), composta de três conceitos principais: política de envio, estoque e doca.
+
+- __[Política de envio](#politica-de-envio)__: conjunto de regras que definem as opções de envio do pedido e condições de frete.
+- __[Estoque](#estoque)__: espaço físico de armazenamento das mercadorias vendidas.
+- __[Doca](#doca)__: local de distribuição dos itens vendidos.
+
+A imagem abaixo mostra como esses conceitos se relacionam entre si na venda de um produto:
+
+![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
+
+A tabela a seguir apresenta as principais configurações de logística da loja na VTEX:
+
+<div class="alert alert-INFO">
+A ordem de configuração inicial sugerida é a seguinte: primeiro estoque, segundo doca e terceiro política de envio.
+</div>
+
+| **Assunto** | **Configuração via Admin VTEX** | **Configuração via API** |
+| :---: | :--- | :--- |
+| [Estoque](#estoque) | [Gerenciar Estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| [Doca](#doca) | [Gerenciar Doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
+| [Política de envio](#politica-de-envio) | [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| [Inventário](#gerenciamento-de-inventario) | [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) | [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-) |
+
+#### Estoque
+
+É a partir do [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) que se inicia a rota logística. Ele corresponde ao espaço físico de armazenamento das mercadorias vendidas pela loja. Uma vez que os itens vendidos são separados do estoque, eles são encaminhados para a doca.
+
+#### Doca
+A [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) é o local a partir dos quais os itens são distribuídos e escoados para envio, o ponto intermediário entre estoques e transportadoras. Pela doca, ocorre a integração entre estoque, política comercial e política de envio. Alguns dos casos de uso são:
+
+- Diferentes pontos de escoamento para um único estoque.
+- Doca como centro de distribuição.
+- Doca e estoque correspondem ao mesmo espaço físico.
+
+Para determinados produtos, é possível que não exista necessidade de um espaço físico de distribuição. Ainda assim, a doca é uma configuração obrigatória para o funcionamento correto das operações da plataforma VTEX.
+
+#### Política de envio 
+
+[Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) é um conjunto de regras que definem as opções e condições de envio que serão apresentadas aos clientes no checkout. As condições de envio incluem transportadora, prazos de entrega, custo de frete, entre outros. A política de envio é vinculada ao estoque pela doca.
+
+A [transportadora](https://help.vtex.com/pt/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE) que será responsável pelo envio do pedido é determinada por meio da política de envio. Primeiro, o cadastro de transportadoras é feito na [planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127), em seguida, a planilha de frete é associada quando se cria uma política de envio.
+
+### Gerenciamento de inventário
+
+O [inventário](https://help.vtex.com/pt/tutorial/gerenciar-inventario--tutorials_139) da loja corresponde aos itens armazenados que estão disponíveis para a venda. O estoque é a identificação do local físico de armazenamento, enquanto o inventário é o conjunto de SKUs em estoque que estão prontos para serem vendidos.
+
+<div class="alert alert-danger">
+Na VTEX, a atualização de inventário após a venda dos itens precisa ser controlada pela própria loja. Desta forma, após a venda, o lojista garante o devido controle da quantidade de itens restantes e de operações de fatura com ERP. Informações sobre importação de inventário via back-office podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
+</div>
+
+### Lead time
+
+No Admin VTEX, em __Catálogo > Estoque > Gerenciamento de inventário__, existe uma configuração opcional chamada [Lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B), que permite atribuir um tempo de envio a nível de SKU. Configurar o lead time significa adicionar um período de tempo ao [cálculo](#calculo-de-envio-de-pedidos) de envio de pedido, o que é estratégico em alguns contextos.
+
+Dentre os [principais casos de uso](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#principais-casos-de-uso), podemos citar produtos de fornecedores externos, cenários de _dropshipping_ e venda de itens personalizáveis. Poder configurar o lead time significa ter mais flexibilidade para definir prazos de manipulação e envio do produto por terceiros.
+
+### Cálculo de envio de pedidos
+
+Para [calcular o prazo de envio](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) de pedidos, a plataforma VTEX considera as seguintes configurações:
+
+![Envio de Pedidos_PT](//images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/a9d7b3e4fcaf73e11e3d3d4d9e2a3e28/Envio_de_Pedidos_PT.png)
+
+- [Lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B): quantidade de tempo configurável para o SKU de um estoque. A configuração é opcional e, por padrão, está definida como zero dias.
+- [Tempo de estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137): tempo que o SKU leva para sair de um estoque para uma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Essa configuração é obrigatória, mas o tempo pode ser definido igual a zero.
+- [Tempo de doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW): tempo que o SKU leva para sair da doca para ser enviado para o cliente. Essa configuração é obrigatória, mas o tempo pode ser definido igual a zero.
+- [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140): agrupa as regras e condições de envio apresentadas aos clientes no checkout, incluindo transportadoras, custo de envio, horário de funcionamento da transportadora, janelas de entrega e capacidade de entrega.
+
+O [simulador de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144) permite ao lojista simular e analisar as opções de entrega disponíveis para um pedido em uma localidade. A simulação verifica a viabilidade e as condições de envio do pedido, tais como disponibilidade de itens, formas de envio, custos e prazos.
+
+### Configurações opcionais de Logística
+
+Para atender a diversos modelos de negócio, a plataforma VTEX disponibiliza uma série de configurações opcionais, conforme apresentado na tabela abaixo:
+
+| **Funcionalidade** | **Descrição** |
+| :---: | :--- |
+| Pontos de retirada | [Pontos de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) são locais físicos que a loja configura para que os clientes possam retirar seus pedidos. Configurar pontos de retirada é interessante para operações omnichannel, especialmente quando há um grande número de lojas físicas, pois cada loja física pode se tornar uma opção para o cliente retirar seu pedido, aumentando a versatilidade da sua malha logística. |
+| Feriados | A funcionalidade [Feriados](https://help.vtex.com/pt/tutorial/cadastrar-feriados--2ItOthSEAoyAmcwsuiO6Yk) permite que a loja configure dias que não são válidos para o envio, e isso será considerado ao calcular o prazo de envio do pedido. |
+| Reserva | A [reserva](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92) é uma solução que impede que um mesmo item seja vendido mais de uma vez. Quando o cliente apenas insere o produto no carrinho, isso não gera reserva, sua prioridade sobre o item só ocorre após a finalização do pedido. |
+| Capacidade de entrega | A [Capacidade de entrega](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi#capacidade-de-entrega) é o limite de envios que podem ser realizados pela loja em determinado período. Poder delimitar uma quantidade de itens ou pedidos que podem ser enviados em cada janela de envio significa ter mais controle sobre o preparo de pedidos e aumentar as chances de cumprir o acordo de entrega feito ao cliente no checkout. |
+| Geolocalização | [Geolocalização](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138) é o cadastro dos locais de envio a partir da latitude e longitude dos endereços. Essa funcionalidade é muito utilizada em endereços de zonas rurais e industriais, onde há divisão por lotes, ou áreas de risco, quando é preciso excluir determinados locais de entrega dentro de uma região. |
+
+Outras informações sobre conceitos logísticos na VTEX podem ser encontradas no artigo [Glossário de logística](https://help.vtex.com/pt/tutorial/glossario-de-logistica--16DSSiXn548rsidi0A8Hby), e conteúdo para desenvolvedores sobre a [Logistics API](https://developers.vtex.com/docs/api-reference/logistics-api#overview), no artigo [Fulfillment and Logistics](https://developers.vtex.com/docs/guides/fulfillment).
diff --git a/docs/tracks/pt/vtex-modules-ii.md b/docs/tracks/pt/vtex-modules-ii.md
new file mode 100644
index 000000000..70f12cbd2
--- /dev/null
+++ b/docs/tracks/pt/vtex-modules-ii.md
@@ -0,0 +1,299 @@
+---
+title: 'Módulos da VTEX II'
+id: 3MYcZaojb5HSUg6ufm6GxQ
+status: CHANGED
+createdAt: 2024-02-07T13:20:33.477Z
+updatedAt: 2024-02-22T17:08:09.649Z
+publishedAt: 2024-02-22T14:07:12.569Z
+firstPublishedAt: 2024-02-22T14:07:12.569Z
+contentType: trackArticle
+productTeam: Others
+slug: modulos-da-vtex-ii
+locale: pt
+trackId: eSDNk26pdvemF3XKM0nK9
+trackSlugPT: trilha-da-loja-vtex
+---
+
+Além dos módulos abordados no artigo anterior, como [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos), [Promoções](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#promocoes) e [Logística](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica), a plataforma VTEX possui outros módulos necessários à operação da loja. Este artigo apresenta uma visão geral e as principais configurações dos seguintes módulos:
+
+- [Pagamentos](#pagamentos)
+- [Pedidos](#pedidos)
+- [Checkout](#checkout)
+
+## Pagamentos
+
+O módulo de [Pagamentos](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB) na VTEX é responsável por coordenar todas as operações financeiras realizadas em uma loja. Por meio dele, é possível determinar quais provedores, meios e condições de pagamento serão oferecidos aos clientes no checkout, bem como verificar informações a respeito das transações de pagamento efetuadas em cada pedido.
+
+### Antes de começar em Pagamentos
+
+Para processar e receber os pagamentos das compras realizadas em uma loja VTEX, é preciso contratar os serviços de um ou mais provedores de pagamento. Este contrato é realizado diretamente entre o lojista e o respectivo provedor, não havendo mediação ou participação da VTEX. Para verificar quais provedores estão disponíveis na VTEX em cada país, basta acessar a [Lista de provedores de pagamento](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).
+
+<div class="alert alert-warning">
+É recomendável utilizar mais de um provedor de pagamento na loja para prover uma boa experiência ao cliente por meio diversos tipos de meios e condições de pagamento, e ao mesmo tempo, operar com diferentes taxas e custos, melhorando o desempenho do negócio.
+</div>
+
+As configurações de pagamento descritas nesta trilha podem ser realizadas a qualquer momento durante o processo de onboarding. Entretanto, para que a loja possa realizar qualquer tipo de transação de pagamento, é necessário que os módulos de [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos) e [Logística](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) tenham sido previamente configurados.
+
+### Como funciona o módulo Pagamentos
+
+A tabela a seguir apresenta os principais agentes e termos utilizados no contexto de Pagamentos:
+
+| **Termo** | **Descrição** |
+| --- | --- |
+| **Gateway** | Sistema responsável por processar informações de pagamento de uma compra no checkout. |
+| **Adquirente** | Empresa que realiza o processamento de pagamentos realizados por cartões de crédito e débito. |
+| **Subadquirente** | Empresa intermediadora de pagamentos entre os adquirentes, provedores de antifraude e lojistas. |
+| **Bandeira de cartão** | Empresa responsável por definir regras de negócios aplicadas a cartão de crédito e débito. |
+| **Banco emissor** | Instituição financeira responsável por realizar a autorização de um meio de pagamento, como boleto bancário, cartão de crédito ou débito. |
+| **Provedor de pagamento** | Empresa que oferece suporte para transações eletrônicas em diversos meios de pagamento. |
+| **Provedor de antifraude** | Empresa responsável por realizar análises de risco em transações de cartão de crédito e débito. |
+| **Payment Provider Protocol** | Protocolo de comunicação de um provedor de pagamento utilizado para transmissão de dados de pagamento. Saiba mais sobre como provedores de pagamento são integrados na VTEX em [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). |
+| **Anti-fraud Provider Protocol** | Protocolo de comunicação de um provedor de antifraude utilizado para transmissão de dados de análises de pagamento. Saiba mais sobre como provedores de antifraude são integrados na VTEX em [Anti-fraud Provider Protocol](https://developers.vtex.com/docs/guides/how-the-integration-protocol-between-vtex-and-antifraud-companies-works). |
+| **Meio de pagamento** | Métodos disponibilizados pelo cliente para realizar o pagamento de uma compra, tais como, cartões de crédito, débito, carteiras digitais. |
+| **Condição de pagamento** | Regras estabelecidas para um determinado meio de pagamento, por exemplo, número máximo de parcelas permitidas e juros aplicados. |
+
+### Fluxos de pagamento e transação
+
+Quando uma compra é finalizada na VTEX, uma nova transação é criada e o fluxo de pagamento é iniciado. No exemplo abaixo, é possível verificar um fluxo de pagamento para uma compra realizada por cartão de crédito:
+
+![payments-pt](//images.ctfassets.net/alneenqid6w5/5QPFkvZhpZzRWuq15zlMoz/c40d02d7dd6be8f01dc8b9ed03c4741e/payments_image1_PT.jpg)
+
+Conforme as informações vão sendo transmitidas entre os agentes responsáveis pelo processamento dos dados, o status da transação de pagamento é atualizado para indicar em qual momento do fluxo os recursos se encontram. Para o fluxo de pagamento por cartão de crédito, temos o seguinte exemplo de status da transação:
+
+![payments-flow-pt](//images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/9419c03573e34455c5a97f08982be8fd/payments_image2_ALL.JPG)
+
+Mais informações sobre cada etapa podem ser encontradas no artigo [Fluxo da transação no Pagamentos](https://help.vtex.com/pt/tutorial/transaction-flow-in-payments--Er2oWmqPIWWyeIy4IoEoQ). Para saber como acessar mais informações sobre as transações no Admin VTEX, bas conferir o artigo [Ver detalhes da transação](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
+
+### Configurando pagamentos na loja
+
+Após estabelecer contrato com um provedor de pagamento, é necessário configurá-lo e definir quais meios e condições de pagamento serão disponibilizados no checkout da loja.
+
+#### Habilitando o conector de pagamento
+
+Os provedores de pagamento precisam ser habilitados em uma loja de modo que transmitam e recebam as informações necessárias para a conclusão de uma transação de pagamento. Os passos abaixo devem ser seguidos para cada provedores a ser habilitado:
+
+1. Acessar a [Lista de provedores de pagamento](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).
+2. Selecionar o provedor desejado, clicando no respectivo link da tabela.
+3. Acessar o Admin VTEX para configurar o provedor conforme as instruções descritas no respectivo artigo de configuração.
+
+<div class = "alert alert-info">
+Os artigos de configuração de provedores também podem ser acessados ao digitar o nome do provedor desejado na barra de busca do <a href="https://help.vtex.com/pt/">Help Center</a>.
+</div>
+
+#### Definindo meios e condições de pagamento
+
+Para configurar os meios e condições de pagamento, os passos abaixo devem ser seguidos:
+
+1. No Admin VTEX, acessar **Configurações da loja > Pagamentos > Configurações**, ou digitar **Configurações** na barra de busca no topo da página.
+2. Na aba **Condições de pagamento**, clicar no botão **+**.
+3. Clicar no nome do meio de pagamento desejado.
+4. Se desejar, o nome do meio de pagamento pode ser modificado na coluna **Nome da condição**.
+5. Ativar a opção **Status**.
+6. Em **Processar com a afiliação:** o nome do provedor de pagamento deve ser selecionado.
+7. Se desejar utilizar um sistema antifraude, a opção **Usar solução antifraude** deve ser selecionada. Saiba mais em [Configurando provedor de antifraude (opcional)](#configurando-provedor-de-antifraude).
+8. Caso o meio de pagamento escolhido permita a configuração de pagamentos parcelados, selecionar a opção **Parcelado** em **A vista ou parcelado?** e inserir as informações desejadas. Saiba mais em [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455).
+9. Se desejar, também é possível configurar condições especiais de pagamento. Saiba mais em [Adicionando condições especiais de pagamento](#adicionando-condicoes-especiais-de-pagamento).
+10. Clicar em `Salvar`.
+
+### Configurações opcionais em Pagamentos
+
+De acordo com o perfil de operação da loja, também é possível realizar as seguintes configurações opcionais de pagamentos:
+
+- [Adicionar condições especiais de pagamento](#adicionando-condicoes-especiais-de-pagamento)
+- [Configurar meios de pagamento customizados](#configurando-meios-de-pagamento-customizados)
+- [Configurar provedor de antifraude](#configurando-provedor-de-antifraude)
+- [Criar vales-presente](#criando-vales-presente)       
+- [Habilitar carteiras digitais](#habilitando-carteiras-digitais)
+- [Customer Credit](#costumer-credit)
+
+#### Adicionando condições especiais de pagamento
+
+Condições especiais de pagamento permitem que sejam definidas regras específicas para um determinado meio de pagamento, tais como data de vencimento, banco emissor, política comercial, condição comercial e nome da conta. 
+
+Para conhecer mais detalhes sobre cada tipo de condição especial de pagamento, basta consultar o artigo [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+
+#### Configurando meios de pagamento customizados
+
+Na VTEX, é possível configurar os seguintes de meios de pagamento customizados:
+
+- **Promissórias**: compromisso de pagamento entre o lojista e o cliente referente ao valor de uma compra. É necessária a aprovação manual do lojista para aprovar a transação de compra. Mais informações em [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ).
+
+- **Cartões de loja (bandeira própria)**: cartão de crédito ou débito, emitido em parceria entre uma empresa e uma bandeira de cartões (Visa, Mastercard, entre outros). Pode ser utilizado somente para compras em estabelecimentos que operem com a marca da bandeira emissora do cartão. Mais informações em [Configurar pagamentos com Cartões de Loja (bandeira própria)](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4).
+
+- **Cartões de loja (co-branded)**: cartão de crédito ou débito de marca própria, emitido para uso exclusivo em compras realizadas na empresa emissora do cartão. Mais informações em [Configurar pagamentos com Cartões de Loja (co-branded)](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-cobranded--jrkLK41IjuquUmyKUi86Q).
+
+#### Configurando provedor de antifraude
+
+Provedores de antifraude também podem ser configurados na loja para realizar análises de pagamentos de cartão de crédito e débito, desde que haja um contrato entre o lojista e o provedor. A sua utilização é recomendada, porém, opcional.
+
+Para verificar os provedores de antifraude atualmente integrados na VTEX, é necessário digitar na barra de busca do [Help Center](https://help.vtex.com/pt/) o nome do provedor desejado ou acessar o Admin VTEX, conforme o artigo [Configurar o antifraude](https://help.vtex.com/pt/tutorial/como-configurar-antifraude--tutorials_446).
+
+#### Criando vales-presente
+
+Os vales-presente, também conhecidos como, gift cards ou vouchers, podem ser utilizados em lojas VTEX como meio de pagamento ou programa de fidelidade.
+
+A VTEX possui o seu próprio provedor de vales-presente, permitindo que vales sejam criados e gerenciados por meio do Admin VTEX ou da API do Gift Card. Saiba mais sobre as características de criação pelos dois métodos em [GiftCard API](https://developers.vtex.com/docs/api-reference/giftcard-api).
+
+Além disso, também é possível oferecer gift cards de provedores externos por meio da [GiftCard Hub API](https://developers.vtex.com/docs/api-reference/giftcard-hub-api). Para utilizar um provedor externo de gift card, é necessário possuir um contrato com o provedor e verificar se já está integrado na VTEX. Mais informações nos artigos [Configurar Vale-presente](https://help.vtex.com/pt/tutorial/gift-card--tutorials_995) e [Gift Card system architecture](https://developers.vtex.com/docs/guides/gift-card-integration-guide-system-architecture).
+
+#### Habilitando carteiras digitais
+
+Carteiras digitais são ambientes seguros onde dados bancários e de cartão de crédito podem ser armazenados de forma criptografada e que podem ser acessadas pelo cliente no momento de realizar uma compra. A segurança deste meio de pagamento consiste em não ser necessário preencher todos os dados no checkout a cada compra, sendo somente solicitado ao realizar a autenticação dentro do próprio ambiente de carteira digital.
+
+Na VTEX, é possível oferecer carteiras digitais nativas, como o [Google Pay](https://help.vtex.com/pt/tracks/carteira-digital-e-wallet--6X8YyZBoVJpz5R8oXciTyu/61JMBvM5Vanqj6RaJsP8CT), ou carteiras digitais integradas, tais como [Apple Pay](https://help.vtex.com/en/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/STKWiXJSR9ImPt5EEC2aL), [Samsung Pay](https://help.vtex.com/pt/tutorial/configurar-samsung-pay-como-meio-de-pagamento--5Yj9rgzOCVYuGmAumQlfpP) e [PayPal](https://help.vtex.com/pt/tutorial/configurar-paypal--4p3sD9u1moq2Aya2oc684w). Mais informações em [Carteira digital (ewallet)](https://help.vtex.com/pt/tracks/digital-wallet-e-wallet--6X8YyZBoVJpz5R8oXciTyu/7jLbdfch9Oe2yYbQa9zwE1).
+
+#### Customer Credit
+
+Customer credit é a solução da VTEX para permitir que crédito seja oferecido a clientes específicos, possibilitando um prazo maior para o pagamento de suas compras. Por meio deste app, é possível ter acesso a gerenciamento de clientes, configuração de prazos e parcelamentos, definição de crédito e acompanhamento de status de títulos de cobrança emitidos, entre outras funcionalidades.
+
+Para mais informações, acesse [Customer Credit - Visão Geral](https://help.vtex.com/pt/tutorial/customer-credit-visao-geral--1uIqTjWxIIIEW0COMg4uE0) e [Customer Credit - Como Começar](https://help.vtex.com/pt/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
+
+## Pedidos
+
+A partir do momento em que o cliente conclui a compra, é gerado um [pedido](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa) na VTEX. O gerenciamento de pedidos pode ser feito pelo Admin VTEX, em **Pedidos > [Todos os pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi)**, acessando-se uma [página de detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) da compra, ou via API. Uma visão geral de conteúdo para desenvolvedor sobre a [Orders API](https://developers.vtex.com/docs/api-reference/orders-api#overview) pode ser encontrada no guia [Orders](https://developers.vtex.com/docs/guides/orders-overview).
+
+### Antes de começar em Pedidos
+
+Para a loja ser capaz de gerenciar seus pedidos, a plataforma VTEX não exige configurações obrigatórias, e oferece diversas [configurações opcionais](#configuracoes-opcionais-em-pedidos) que podem ser estratégicas para diferentes modelos de negócio.
+
+No entanto, para o cliente ser capaz de realizar a compra e gerar um pedido, a loja precisa ter produtos cadastrados e precificados, oferecer [meios de pagamento](https://help.vtex.com/pt/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento--3azJenhGFyUy2gsocms42Q) e garantir o envio do pedido. Para isso, é necessário realizar as configurações obrigatórias dos seguintes módulos:
+
+- [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo)
+- [Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos)
+- [Logística](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica)
+- [Pagamentos](#pagamentos)
+
+### Integração de pedidos
+
+Com grande frequência, as lojas desejam [integrar seus pedidos](https://developers.vtex.com/docs/guides/erp-integration-guide) a sistemas como ERP (_Enterprise Resource Planning_) e WMS (_Warehouse Management System_). A [implementação de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) permite à loja automatizar algumas ações no processamento do pedido, tais como:
+
+- Receber notificações do andamento de pedidos e do seu status no [fluxo do pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
+- Obter informações de pedidos que precisam ser separados e embalados.
+- Enviar a [fatura](https://help.vtex.com/pt/tutorial/como-faturar-um-pedido--7p1h852V5t54KyscpgxE2v) para a plataforma VTEX, que vai encaminhá-la ao cliente.
+- Realizar a [alteração de itens](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) do pedido.
+
+Existem duas maneiras diferentes de acompanhar a mudança de status de pedido, o [Feed](https://developers.vtex.com/docs/guides/orders-feed) ou [Hook](https://developers.vtex.com/docs/guides/orders-feed#hook). Mais informações sobre integração de pedidos podem ser encontradas no artigo [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu).
+
+### Gerenciar pedidos
+
+No Admin VTEX, em **Pedidos > [Todos os pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi)**, é possível realizar as seguintes ações:
+
+- Visualizar uma listagem com todos os pedidos da loja.
+- Acessar informações da compra na [página de  detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), clicando sobre o pedido.
+
+Na página de detalhes do pedido, também é possível acompanhar a evolução do [fluxo do pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196). A imagem a seguir é um exemplo de fluxo quando a loja atua simultaneamente como marketplace e seller:
+
+![order-flow-pt](//images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/65a4533c0b089dd2792a21383f913393/pedido_fluxo_completo_pt.png)
+
+Para localizar o registro de uma compra no Admin VTEX, além de poder [filtrar pedidos](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192) na página **Todos os pedidos**, existe a opção de pesquisar pela barra de busca global, que aparece em todas as páginas do Admin VTEX. Para realizar a pesquisa, basta selecionar a opção `Pedidos`, no canto direito da barra de busca, e utilizar algum dos seguintes valores:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
+
+<div class="alert alert-warning">
+Só é possível acessar informações de pedidos criados nos últimos dois anos, sendo o mesmo período válido para os clientes acessarem seus pedidos pelo <a href="">Minha Conta</a>.
+</div>
+
+#### Emails transacionais
+
+A VTEX oferece de forma nativa o envio de [emails transacionais](https://help.vtex.com/pt/tutorial/understanding-the-message-center--tutorials_84), para a loja ser capaz de disparar emails automáticos para o cliente informando sobre as atualizações do pedido. Ou seja, conforme o pedido avança no fluxo de processamento, o cliente pode receber um email de notificação para acompanhar, por exemplo, a aprovação do pagamento da compra e o envio do pedido.
+
+A plataforma oferece uma série de [templates de emails transacionais](https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my), mas também é possível personalizar a comunicação. A lista abaixo apresenta as principais informações sobre essas configurações opcionais, que são independentes entre si:
+
+- **Alias:** email alternativo gerado automaticamente pela plataforma VTEX para [mascarar](https://help.vtex.com/pt/tutorial/configuracoes-gerais--tutorials_194#tipo-de-mascara-de-conversa) o email do cliente nos emails transacionais da loja. Esse [tipo de máscara de conversa](https://help.vtex.com/pt/tutorial/configuracoes-gerais--tutorials_194#tipo-de-mascara-de-conversa) representa mais proteção para os dados dos clientes, pois o email alternativo é criado de forma não legível para sistemas externos.
+- **Availability Notify ou Avise-me**: configuração do botão [Avise-me](https://help.vtex.com/pt/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e) na página do produto que o cliente visualizou no site da loja. O botão se torna visível quando aquele produto está indisponível e o cliente pode escolher inserir o seu email no campo informado para ser notificado quando o produto estiver novamente disponível para compra.
+
+#### Funcionalidade Minha conta
+
+[Minha Conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh) é a solução que garante aos clientes da loja terem autonomia no acompanhamento dos seus pedidos e na atualização de seus dados pessoais. Trata-se de ambiente único para cada cliente, que o acessa com senha e usuário.
+
+Uma das vantagens da **Minha Conta** é que a funcionalidade torna mais direta a comunicação entre o cliente e a loja, além de permitir ao cliente ações como pedir novamente ou cancelar o pedido. A comunicação mais eficiente tende a diminuir a necessidade de serviços de atendimento ao cliente o que, por sua vez, representa uma redução de custos para a loja.
+
+### Configurações opcionais em Pedidos
+
+A tabela a seguir apresenta algumas configurações opcionais do módulo Pedidos:
+
+| **Funcionalidade** | **Descrição** |
+| :---: | :--- |
+| Assinaturas | [Assinaturas](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453) é um agendador automático de pedidos para facilitar aos clientes da loja fazerem compras recorrentes. O cliente indica quais itens deseja comprar e a frequência com que os pedidos automáticos devem ser feitos.<br><br>[Configurar Assinaturas](https://help.vtex.com/pt/tutorial/como-configurar-assinaturas--1FA9dfE7vJqxBna9Nft5Sj) é especialmente interessante para modelos de negócio como supermercados e vendas para pets, nos quais os clientes consomem os mesmo produtos com certa periodicidade. |
+| Televendas | A solução [televendas](https://help.vtex.com/pt/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS) permite mais autonomia para a equipe de serviço de atendimento da loja no apoio aos clientes. Ao [configurar as funcionalidades de televendas](https://help.vtex.com/pt/tutorial/como-configurar-as-funcionalidades-de-televendas--76FNgQP2Glc4umMJ5Yr50R), os operadores da loja se tornam habilitados a realizar tarefas como:<br><br>- Comprar em nome de um cliente.<br>- Ajustar manualmente o preço de itens de um carrinho de compras.<br>- Alterar pedidos existentes.<br>- Gerenciar informações de perfil de um cliente no [Minha Conta](#funcionalidade-minha-conta). |
+| Divergência de valores | Nas [estratégias de marketplace](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) da loja no ecossistema VTEX, pode acontecer do preço definido pelo seller ser diferente do preço oferecido pelo marketplace. Cenários com promoções no marketplace, por exemplo, podem interferir no preço que o seller definiu para a venda do seu produto.<br><br>Para evitar erros de processamento de pedidos, o seller VTEX pode [configurar regras de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) e estabelecer parâmetros para autorização automática de pedidos com essa diferença de preço entre seller e marketplace. Ao criar regras automáticas para aprovar ou recusar pedidos com diferença de preço, a loja evita ter que fazer o processamento manual de cada item e a operação ganha em eficiência. |
+
+Mais informações em [Configurações Gerais dos pedidos](https://help.vtex.com/pt/tutorial/configuracoes-gerais--tutorials_194).
+
+## Checkout
+
+O checkout é a etapa final no processo de compras online e contribui de maneira expressiva para uma boa taxa de conversão de vendas. No contexto da plataforma VTEX, o módulo [Checkout](https://help.vtex.com/pt/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) desempenha algumas funções essenciais:
+
+- Fornecimento de informações sobre o preço e a disponibilidade dos produtos na vitrine da loja.
+- Adiciona itens e processa o carrinho de compras.
+- Realiza o processo de conclusão da compra. 
+
+### Antes de começar no Checkout
+
+Para assegurar o correto funcionamento do checkout, é necessário que os seguintes módulos estejam devidamente configurados pela loja: [Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), [Logística](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx), [Preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP#), [Promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#), [Pagamentos](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#) e [Pedidos](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE).
+
+![checkout-pt](//images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/df639ea0697ca3e01b99963acd509b4f/checkout_image_PT.jpg)
+
+Este compartilhamento de informações permite que sejam processadas informações de disponibilidade, preços, promoções aplicáveis, métodos de envio e de pagamento.
+
+### Customizando o Checkout da loja
+
+As customizações descritas abaixo são opcionais e tem o objetivo de produzir melhorias na performance da Checkout. Antes de configurá-las, é recomendável realizar uma análise para identificar quais são aplicáveis ao perfil operacional da loja.
+
+- [Otimização das opções de entregas do checkout](#otimizacao-das-opcoes-de-entregas-no-checkout)
+- [Carrinho abandonado](#carrinho-abandonado)
+- [Modificar o preço de um item no carrinho de compras](#modificar-o-preco-de-um-item-no-carrinho-de-compras)
+- [Valor mínimo de pedido e quantidade máxima de itens por SKU](#valor-minimo-de-pedido-e-quantidade-maxima-de-itens-por-sku)
+- [Geolocalização no Checkout](#geolocalizacao-no-checkout)
+- [Checkout UI Custom app](#checkout-ui-custom-app)
+
+### Otimização das opções de entregas no Checkout
+
+Solução que permite acionar uma combinação de informações cadastradas para exibir ao cliente qual é a opção mais rápida e a mais barata para realizar a entrega dos produtos selecionados no carrinho. As outras opções (de maior custo ou maior prazo), não são exibidas no Checkout, melhorando a experiência do cliente.
+
+Mais informações em [Otimização das opções de entrega no Checkout](https://help.vtex.com/pt/tutorial/otimizacao-das-opcoes-de-entrega-no-checkout--6DeGO9eBSFWe4XkoS0SxAB).
+
+### Carrinho abandonado 
+
+Funcionalidade que permite envio de e-mails aos clientes para recordá-los sobre a conclusão da compra de um carrinho que tenha sido criado anteriormente, mas não finalizado.
+
+<div class = "alert alert-info">
+Configurar o carrinho abandonado durante o Onboarding, permitirá que todos os carrinhos que ainda serão criados, possam ser encaminhados para avaliação do cliente ou finalizados.
+</div>
+
+Mais informações em [Configurar carrinho abandonado](https://help.vtex.com/pt/tutorial/configurar-carrinho-abandonado--tutorials_740).
+
+### Modificar o preço de um item no carrinho de compras
+
+Na plataforma VTEX, as lojas têm a possibilidade de ajustar manualmente o preço de um item (SKU) presente no carrinho do Checkout. Esta funcionalidade pode ser usada para aplicar descontos especiais, corrigir erros de preço, criar ofertas personalizadas, resolver reclamações relacionadas a preços ou ajustar custos de envio.
+
+<div class="alert alert-warning">
+Apenas usuários com <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfis de acesso</a> e permissões devidamente registrados no Admin VTEX podem realizar esta modificação.
+</div>
+
+Mais informações em [Modificar o preço de um item no carrinho de compras](https://help.vtex.com/pt/tutorial/modificar-o-preco-de-um-item-no-carrinho-de-compras--7Cd37aCAmtL1qmoZJJvjNf).
+
+### Valor mínimo de pedido e quantidade máxima de itens por SKU
+
+Nas operações de ecommerce, o custo logístico associado à entrega dos produtos desempenha um papel importante na manutenção da competitividade. Esse custo é impactado pelo valor total do carrinho de compras e quantidade de unidades do mesmo SKU contidas no carrinho.
+
+A implementação de um valor mínimo de pedido pode melhorar a eficiência para sellers que realizam entregas em lotes, evitando pedidos com valor baixo ou poucos itens, que podem ser economicamente inviáveis.
+
+Mais informações em [Como configurar valor mínimo de pedido e quantidade máxima de itens por SKU](https://help.vtex.com/pt/tutorial/como-configurar-valor-minimo-de-pedido-e-quantidade-maxima-de-itens-por-sku--7JqipPUBxtKz0m4OlAyKs9).
+
+### Geolocalização no Checkout 
+
+A solução de geolocalização possibilita ao cliente utilizar o Google Maps na tela do checkout da loja para definir um local de entrega, ao invés de utilizar o CEP do endereço. Após indicar o ponto de entrega, o valor do frete do pedido será exibido de acordo com o valor cadastrado pelo lojista entregas na região selecionada do mapa (polígonos de coordenadas).
+
+Além de calcular automaticamente o custo do frete, se a loja oferece a opção de retirada na loja física, a geolocalização pode ajudar os clientes a encontrar a loja mais próxima com base em sua localização atual.
+
+Mais informações em [Configurar geolocalização no checkout](https://help.vtex.com/pt/tutorial/geolocalizacao-no-checkout--tutorials_4345).
+
+### Checkout UI Custom app
+
+Este aplicativo permite que diferentes customizações visuais possam ser aplicadas na tela do Checkout da loja. 
+
+Mais informações em [Checkout UI Custom](https://developers.vtex.com/docs/apps/vtex.checkout-ui-custom).
diff --git a/docs/tracks/pt/vtex-support.md b/docs/tracks/pt/vtex-support.md
new file mode 100644
index 000000000..da83d34d7
--- /dev/null
+++ b/docs/tracks/pt/vtex-support.md
@@ -0,0 +1,33 @@
+---
+title: 'Suporte na VTEX'
+id: 7w7cUmbrdPEKpTMItjXEB8
+status: PUBLISHED
+createdAt: 2023-12-19T12:23:03.789Z
+updatedAt: 2024-05-23T17:44:36.531Z
+publishedAt: 2024-05-23T17:44:36.531Z
+firstPublishedAt: 2024-02-22T14:09:33.306Z
+contentType: trackArticle
+productTeam: Billing
+slug: suporte-na-vtex
+locale: pt
+trackId: 4AXsGdGHqExp9ZkiNq9eMy
+trackSlugPT: suporte-na-vtex
+---
+
+Quando surge a necessidade de apoio, os clientes e parceiros podem contar com a assistência VTEX, que inclui nossos portais de documentação, o VTEX Community e o nosso suporte online, conforme apresentado na tabela abaixo:
+
+| **Canal**     | **Descrição**     |
+| ---------- | ---------- |
+| [Help Center](https://help.vtex.com/pt/) | Portal de documentação voltado para lojistas, equipes de suporte e tomadores de decisão de negócios que trabalham com o painel administrativo da plataforma, o Admin VTEX.   |
+| [Developer Portal](https://developers.vtex.com/)  | Portal de documentação voltado para desenvolvedores e usuários técnicos que trabalham com a plataforma VTEX.  |
+| [VTEX Community](https://community.vtex.com/)  | Comunidade oficial da VTEX. Na VTEX Community é possível encontrar soluções para dúvidas, compartilhar ideias e fazer conexões no ecossistema VTEX. |
+| [Suporte VTEX](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe) | Suporte oficial da VTEX, prestado de maneira virtual por especialistas prontos para ajudar na resolução de problemas de suporte que necessitam de acesso a dados privados. [técnico](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt#tecnico), [financeiro](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt#financeiro) ou [comercial](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt#comercial). |
+
+Esta trilha é dedicada à apresentação do suporte virtual prestado pela VTEX e está organizada da seguinte forma:
+
+- [Funcionamento do Suporte VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/2Ik9CGbPeZIHHaYFsuyId3)
+- [Abertura de chamados](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/6EboD7Y1BOLlWdT8JM15EE)
+- [Suporte técnico](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3thRAdTB3gGwTB0e1fVL3T)
+- [Suporte financeiro](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3g2mhmPDx5GszNgLDICzsl)
+- [Suporte comercial](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ)
+- [Rescisão de contrato](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3TUpFItxp8L1WZAD1JuYfF)
diff --git a/docs/tracks/pt/what-are-clustered-payment-conditions.md b/docs/tracks/pt/what-are-clustered-payment-conditions.md
index 0e0b87022..fde9a6630 100644
--- a/docs/tracks/pt/what-are-clustered-payment-conditions.md
+++ b/docs/tracks/pt/what-are-clustered-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'O que é o Condições de Pagamento Clusterizadas?'
 id: 4z2upCJ2om27Cs0BVJRA0U
 status: PUBLISHED
 createdAt: 2020-11-18T11:49:06.387Z
-updatedAt: 2022-02-07T13:17:58.519Z
-publishedAt: 2022-02-07T13:17:58.519Z
+updatedAt: 2024-05-07T19:41:05.528Z
+publishedAt: 2024-05-07T19:41:05.528Z
 firstPublishedAt: 2020-11-18T17:37:30.544Z
 contentType: trackArticle
 productTeam: Financial
@@ -21,5 +21,3 @@ Atualmente, esta funcionalidade encontra-se em Closed Beta (estágio de testes)
 </div>            
 
 A personalização das regras de prazo e parcelamento acontece por meio de nosso banco de dados - o [Master Data](https://help.vtex.com/pt/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw "Master Data"). 
-
-A seguir, explicaremos todas as etapas para que você use essa funcionalidade na operação da sua loja.
diff --git a/docs/tracks/pt/what-is-a-logistics-route.md b/docs/tracks/pt/what-is-a-logistics-route.md
index 8d3bbc1d7..a5432e8c3 100644
--- a/docs/tracks/pt/what-is-a-logistics-route.md
+++ b/docs/tracks/pt/what-is-a-logistics-route.md
@@ -33,4 +33,4 @@ Para cadastrar uma doca no admin da loja, siga os passos indicados neste [link](
 ### Transportadora
 É a partir daqui que os pedidos são distribuídos para seus destinos finais. Uma transportadora se compõe pela frota de veículos que farão as entregas. Assim, os pedidos saem do centro de distribuição direto para a transportadora que finaliza o processo até o cliente final. 
 
-![PT Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
+![PT Conceitos Logística](//images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
diff --git a/docs/tracks/pt/what-is-conversational-commerce-vtex.md b/docs/tracks/pt/what-is-conversational-commerce-vtex.md
index 18ceb024b..808916649 100644
--- a/docs/tracks/pt/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/pt/what-is-conversational-commerce-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'O que é Conversational Commerce VTEX?'
 id: 1NwwADrU70v3roPUV7dWxI
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T14:47:50.242Z
-updatedAt: 2023-04-18T15:02:45.235Z
-publishedAt: 2023-04-18T15:02:45.235Z
+updatedAt: 2024-01-05T17:13:58.076Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:46:55.444Z
 contentType: trackArticle
 productTeam: Shopping
@@ -20,7 +20,7 @@ Com ele, é possível realizar compras utilizando uma lista de compras, ideal pa
 
 Para utilização do suporte humano, o Message-to-Order já está pré integrado com as plataformas de mercado Zenvia (produto Zenvia Chat) e Zendesk. Para clientes que não tenham essas plataformas ou não desejem atendimento humano, também é possível redirecionar o cliente aos canais de atendimento padrões da marca através de mensagem personalizada. 
 
-![chatbot-PT](https://images.ctfassets.net/alneenqid6w5/5w2PKYYmrGDYuiP0t4jQXU/2e05dae6dd79cd1352cade3533624f68/Captura_de_Tela_2022-07-28_a__s_11.13.08.png)
+![chatbot-PT](//images.ctfassets.net/alneenqid6w5/5w2PKYYmrGDYuiP0t4jQXU/2e05dae6dd79cd1352cade3533624f68/Captura_de_Tela_2022-07-28_a__s_11.13.08.png)
 
 <div class="alert alert-info">
 O Message-to-Order é um produto em fase de início de operação com escopo reduzido (Alpha). Portanto o perfil de cliente e mercados que abrange ainda é limitado a BR e LATAM e às capacidades disponibilizadas pelo cliente nesse estágio.
diff --git a/docs/tracks/pt/what-is-instore.md b/docs/tracks/pt/what-is-instore.md
index 4edb52890..81cc9a2f1 100644
--- a/docs/tracks/pt/what-is-instore.md
+++ b/docs/tracks/pt/what-is-instore.md
@@ -3,8 +3,8 @@ title: 'O que é o VTEX Sales App?'
 id: 7fnnVlG3Kv1Tay9iagc5yf
 status: PUBLISHED
 createdAt: 2020-06-28T13:07:24.773Z
-updatedAt: 2023-05-31T15:45:55.825Z
-publishedAt: 2023-05-31T15:45:55.825Z
+updatedAt: 2024-05-13T18:03:19.146Z
+publishedAt: 2024-05-13T18:03:19.146Z
 firstPublishedAt: 2020-06-28T13:12:31.221Z
 contentType: trackArticle
 productTeam: Shopping
@@ -24,19 +24,12 @@ Você poderá implementar uma estratégia de Prateleira Infinita, que te ajudar
 
 - Evitar falta de estoque e nunca perder vendas.
 - Ter visibilidade em tempo real do seu estoque. 
-- Beneficiar-se de busca inteligente.
+- Beneficiar-se de busca inteligente, quando instalado o [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) no site. 
 - Estruturar transações de carrinho misto.
 
-Em relação ao fullfilment, o VTEX Sales App vai te ajudar a:
-
-- Atrair movimento e aumentar as vendas.
-- Ter um fluxo de trabalho eficiente para separação de pedidos (picking).
-- Garantir a disponibilidade dos seus produtos por meio de opções de entrega inteligentes.
-- Diminuir custos e tempo de fullfilment com o Smart Routing.
-
 Assim, o processo de compra se torna mais rápido, tanto ao adicionar produtos ao carrinho quanto o pagamento e a confirmação. 
 
-O processo de checkout não precisa mais ser feito de uma mesa. É possível iniciar e finalizar vendas em qualquer lugar da loja, o que reduz filas e torna a experiência do cliente mais agradável. 
+O processo de checkout não precisa mais ser feito de um local físico e fixo. É possível iniciar e finalizar vendas em qualquer lugar da loja, o que reduz filas e torna a experiência do cliente mais agradável. 
 
 Seus vendedores terão uma visão 360º do cliente e poderão criar experiências de compra memoráveis e sem atritos.
 
diff --git a/docs/tracks/pt/what-is-the-cms.md b/docs/tracks/pt/what-is-the-cms.md
index 9cdc17885..81689101f 100644
--- a/docs/tracks/pt/what-is-the-cms.md
+++ b/docs/tracks/pt/what-is-the-cms.md
@@ -14,7 +14,7 @@ trackId: 2YcpgIljVaLVQYMzxQbc3z
 trackSlugPT: cms
 ---
 
-![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System, em Português, Sistema de Gerenciamento de Conteúdo) é uma funcionalidade voltada para o gerenciamento de conteúdo de forma prática e constante.
 
diff --git a/docs/tracks/pt/what-is-the-master-user.md b/docs/tracks/pt/what-is-the-master-user.md
index e4f953539..f16be61e1 100644
--- a/docs/tracks/pt/what-is-the-master-user.md
+++ b/docs/tracks/pt/what-is-the-master-user.md
@@ -26,7 +26,7 @@ Se seu usuário tem perfil de acesso ao módulo Gerenciamento da conta, você po
 
 Ao clicar na loja desejada, o nome e o e-mail do usuário Titular encontram-se na seção __Contato__.
 
-![usuario-master-contato pt](https://images.ctfassets.net/alneenqid6w5/HuUChkUJYyg2wi0gqua6c/015b91c77fd19f159117db66298c79aa/contato_usuario_master.png)
+![usuario-master-contato pt](//images.ctfassets.net/alneenqid6w5/HuUChkUJYyg2wi0gqua6c/015b91c77fd19f159117db66298c79aa/contato_usuario_master.png)
 
 Entre as ações que somente o usuário Titular pode tomar, estão:
 - Reindexar o catálogo.
diff --git a/docs/tracks/pt/what-is-vtex-payment.md b/docs/tracks/pt/what-is-vtex-payment.md
index ed446609c..5b076f701 100644
--- a/docs/tracks/pt/what-is-vtex-payment.md
+++ b/docs/tracks/pt/what-is-vtex-payment.md
@@ -1,10 +1,10 @@
 ---
 title: 'O que é o VTEX Payment?'
 id: 1lZWKCGdy7xpYjukTLfFJL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-05-28T17:29:51.035Z
-updatedAt: 2023-03-14T22:08:12.345Z
-publishedAt: 2023-03-14T22:08:12.345Z
+updatedAt: 2023-10-05T14:12:50.764Z
+publishedAt: 
 firstPublishedAt: 2020-05-29T17:47:57.806Z
 contentType: trackArticle
 productTeam: Financial
diff --git a/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md b/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md
index 8e05edbcc..109f6fa1c 100644
--- a/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md
+++ b/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md
@@ -3,8 +3,8 @@ title: ' O que configurar na Wish antes de iniciar a integração'
 id: 4mIn8NE9McE9BxKsAf9IcB
 status: PUBLISHED
 createdAt: 2019-11-13T16:43:49.316Z
-updatedAt: 2020-02-13T15:01:13.402Z
-publishedAt: 2020-02-13T15:01:13.402Z
+updatedAt: 2023-09-22T20:08:35.507Z
+publishedAt: 2023-09-22T20:08:35.507Z
 firstPublishedAt: 2019-11-19T17:27:37.060Z
 contentType: trackArticle
 productTeam: Channels
@@ -19,14 +19,14 @@ trackSlugPT: integracao-com-a-wish
 É necessário preparar o seu ambiente na Wish antes de iniciar a integração na VTEX. Os principais passos são:
 
   1. [Crie sua conta na Wish](https://merchant.wish.com/open?referral_id=5dbf5f2839622963f0da94ff) - ([vídeo com os passos detalhados](https://www.youtube.com/watch?v=uEl0AnJAaPY))
-  
+
   2. Configure o Brasil como país de envio
 
   3. Escolha sua forma de frete. Existem duas opções na Wish:
     - **Modo Standard ou padrão**: nesta modalidade existe 1 preço de frete para todo o Brasil e não há prazo de entrega definido.
 
-    - **Wish Express**: programa de entrega rápida que permite que os _sellers_ (lojistas) habilitem um preço por produto para 12 sub-regiões no país. O prazo de entrega é **10** dias úteis.
-  
+    - **Wish Express**: programa de entrega rápida que permite que os _sellers_ (lojistas) habilitem um preço por produto para 12 sub-regiões no país. O prazo de entrega é **10** dias úteis. 
+
   4. Caso queira trabalhar com [Wish Express](https://merchantfaq.wish.com/hc/pt/articles/360018939394-Como-enviar-usando-o-Wish-Express-Brasil-):
     - Configure a modalidade ([saiba como aqui](https://merchantfaq.wish.com/hc/pt/articles/232047747-Wish-Express-Fluxo-de-Inscri%C3%A7%C3%A3o))
     - Crie um armazém express ([veja o vídeo com os passos detalhados](https://www.youtube.com/watch?v=adTseSEdeLI&feature=youtu.be))
diff --git a/docs/tracks/pt/whatsapp-integration.md b/docs/tracks/pt/whatsapp-integration.md
index 9e48014f9..85d518bf3 100644
--- a/docs/tracks/pt/whatsapp-integration.md
+++ b/docs/tracks/pt/whatsapp-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integração com o WhatsApp'
 id: 33sM0SVrwffWhAhAgiGrZb
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-08-23T15:11:28.551Z
-updatedAt: 2023-04-25T20:26:48.598Z
-publishedAt: 2023-04-25T20:26:48.598Z
+updatedAt: 2024-01-05T17:14:09.083Z
+publishedAt: 
 firstPublishedAt: 2022-08-23T17:47:05.529Z
 contentType: trackArticle
 productTeam: Shopping
@@ -45,7 +45,7 @@ Além de enviar essas informações, o administrador deve autorizar via [Gerenci
 Recomendamos também [verificar a sua loja junto à Meta](https://www.facebook.com/business/help/1095661473946872?id=180505742745347). Essa etapa é opcional para a integração, mas é obrigatória caso:
 
 * Você deseje iniciar conversas, como aviso de rastreio de produtos, para seus clientes pelo WhatsApp.
-* Você deseje que sua conta comercial seja [oficial](https://developers.facebook.com/micro_site/url/?click_from_context_menu=true&country=BR&destination=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation%23official-business-account&event_type=click&last_nav_impression_id=0txQ0CoZfJfxi7cez&max_percent_page_viewed=44&max_viewport_height_px=869&max_viewport_width_px=1794&orig_http_referrer=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation&orig_request_uri=https%3A%2F%2Fdevelopers.facebook.com%2Fajax%2Fdocs%2Fnav%2F%3Ftranslation%26path1%3Dwhatsapp%26path2%3Doverview%26path3%3Dbusiness-accounts&region=latam&scrolled=true&session_id=2nAsnwfEzmFrzLZoM&site=developers), que permite exibir o nome da loja em vez do número de telefone na lista e com o selo <img src="https://images.ctfassets.net/alneenqid6w5/4DNjQiVYTI24Wjt3t9CRfG/8e1ec0ab6bb167b4ff0de2547243354f/101835379_284952909300321_643050663994982400_n.png" alt="selo oficial whatsapp" width="25"/>.
+* Você deseje que sua conta comercial seja [oficial](https://developers.facebook.com/micro_site/url/?click_from_context_menu=true&country=BR&destination=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation%23official-business-account&event_type=click&last_nav_impression_id=0txQ0CoZfJfxi7cez&max_percent_page_viewed=44&max_viewport_height_px=869&max_viewport_width_px=1794&orig_http_referrer=https%3A%2F%2Fdevelopers.facebook.com%2Fdocs%2Fwhatsapp%2Foverview%2Fbusiness-accounts%2F%3Ftranslation&orig_request_uri=https%3A%2F%2Fdevelopers.facebook.com%2Fajax%2Fdocs%2Fnav%2F%3Ftranslation%26path1%3Dwhatsapp%26path2%3Doverview%26path3%3Dbusiness-accounts&region=latam&scrolled=true&session_id=2nAsnwfEzmFrzLZoM&site=developers), que permite exibir o nome da loja em vez do número de telefone na lista e com o selo <img src="//images.ctfassets.net/alneenqid6w5/4DNjQiVYTI24Wjt3t9CRfG/8e1ec0ab6bb167b4ff0de2547243354f/101835379_284952909300321_643050663994982400_n.png" alt="selo oficial whatsapp" width="25"/>.
 
 ## Criação pelo cliente via Admin VTEX
 
@@ -62,16 +62,16 @@ Após a instalação do aplicativo, a VTEX compartilhará a URL do Admin do Conv
 Com essas informações, siga os passos abaixo:
 
 1. Acesse o Admin VTEX via URL enviada pelo time de suporte. Você será encaminhado para a tela abaixo:
-![Track 101 - Conversational Commerce 1 - PT](https://images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 1 - PT](//images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
 2. Clique no botão `Configurar conta WhatsApp Business`.
 3. Uma janela do Facebook será aberta para configuração. Efetue o login com o perfil de Administração do Business Manager desejado.
 4. Selecione a opção `Criar uma conta WhatsApp Business`.
 5. Insira o nome da conta que será exibido como nome do perfil no WhatsApp.
 6. Selecione a categoria e cadastre a descrição da conta. 
-![Track 101 - Conversational Commerce 2 - PT](https://images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 2 - PT](//images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
 7. Verifique o número de telefone a ser associado à conta por meio do código enviado para o telefone.
 8. Notifique o suporte da VTEX para finalizar a configuração.
 
 Uma vez que a configuração seja concluída, o alerta abaixo será exibido no Admin. 
 
-![Track 101 - Conversational Commerce 3 - PT](https://images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 3 - PT](//images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
diff --git a/docs/tutorials/en/ab-testing-how-where-when-and-why.md b/docs/tutorials/en/ab-testing-how-where-when-and-why.md
index 78b486184..32be6d931 100644
--- a/docs/tutorials/en/ab-testing-how-where-when-and-why.md
+++ b/docs/tutorials/en/ab-testing-how-where-when-and-why.md
@@ -1,10 +1,10 @@
 ---
-title: 'AB Testing: how, where, when and why'
+title: 'A/B Testing for stores on Legacy CMS Portal'
 id: tutorials_581
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:39.133Z
-updatedAt: 2019-12-31T17:00:44.367Z
-publishedAt: 2019-12-31T17:00:44.367Z
+updatedAt: 2024-04-04T17:00:10.270Z
+publishedAt: 2024-04-04T17:00:10.270Z
 firstPublishedAt: 2017-04-27T23:03:41.601Z
 contentType: tutorial
 productTeam: Others
@@ -15,63 +15,24 @@ legacySlug: ab-testing-how-where-when-and-why
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-Recently, there has been a large increase in the search for information about the AB test. The subject is being widely discussed by specialists at all meetings relating to the e-commerce market. Why are people so interested in learning more about this subject? The answer is simple: the interest is a result of the evolution of e-commerce in Brazil. 
+A/B testing is a method used to compare two versions of a website to determine which one performs better in terms of user engagement, conversions, and other relevant metrics. The purpose of A/B testing is to identify which version (A or B) has higher success rates and better results.
 
-First, I would like to clarify the difference between AB Testing and Multivariate Testing.
+Native A/B testing tools are not available for Legacy CMS Portal stores. However, you can still leverage third-party solutions such as [Optimizely's](https://docs.developers.optimizely.com/full-stack-experimentation/docs/welcome) [A/B testing solution](https://docs.developers.optimizely.com/full-stack-experimentation/docs/run-a-b-tests). This tool enables you to create and manage A/B tests, allowing you to analyze the performance of different website versions in a controlled environment.
 
-**AB Test:** this is just two (or more) versions of one single page that are developed with a different element in order to test which version will have the best results. These tests are conducted simultaneously, that is, the two versions are run at the same time in order to reach the same audience profile within the same timeframe: 
+## Use cases for A/B testing
+On VTEX, A/B testing can be conducted using the following store development technologies:
 
-![ab_teste_modelo1 eng](https://images.ctfassets.net/alneenqid6w5/7uNulbMKrYIUGGEME0cGcI/259554cf1b6e8649a1a981021487e036/modelo_1_ingles.png)
+| Technology | Is native A/B testing possible?   | Reference    |
+| ---------- | ---------- | ---------- |
+| CMS Portal Legado - VTEX IO (Store Framework) | Yes     | [A/B testing Legacy and IO store versions](https://developers.vtex.com/docs/guides/vtex-io-documentation-performing-ab-testing-between-legacy-and-io)     |
+| CMS Portal Legado - FastStore | No | - |
+| VTEX IO (Store Framework) - VTEX IO (Store Framework)   | No | - |
+| VTEX IO (Store Framework) - FastStore     | No | - |
+| FastStore - FastStore  | No | - |
 
-_In this example, we are testing the “button color” element_
+## A/B testing between Legacy CMS Portal and VTEX IO store versions
 
-**Multivariate Testing:** similarly to AB Testing, is also intended for testing different versions of one single screen. However, several changes are tested for each version developed. 
+If you are considering migrating your store to VTEX IO and want to compare the performance of your current store against a VTEX IO version through A/B testing, see the [A/B testing Legacy and IO store versions guide](https://developers.vtex.com/docs/guides/vtex-io-documentation-performing-ab-testing-between-legacy-and-io). This guide provides instructions on how to conduct A/B tests between store workspaces from the Legacy CMS Portal and VTEX IO.
 
-![ab_teste_modelo2 eng](https://images.ctfassets.net/alneenqid6w5/1atmZWk1ysSQwAo0UqI4Ak/32f32d90f55a3df1a12a5bdbaaa184e9/MODELO_2_ingles.png)
+By running an A/B test between these two store versions, you can analyze the impact of transitioning to VTEX IO on user engagement, conversions, and overall performance.
 
-_In the example above, we are testing the “button color” element, the “text” element, and the “font size” element_ 
-
-Considering these differences, let’s discuss why conversion specialists would much rather use AB Testing than Multivariate Testing. 
-
-It’s obvious! Using AB Testing, you know exactly what generated the variation in results and can learn from it. On the other hand, when you use Multivariate Testing, it is impossible to say if the variation was due to the color of the button or the change in the text. 
-
-There are specific sites for disclosure of AB Testing results. In spite of being very useful, they must be analyzed carefully, since not everything that works for audience A will work for audience B. Also, the profile of Brazilian consumers is quite different from the profile of foreign consumers. 
-
-Check out sites whichtestwon.com and abtests.com to learn more about what other store owners are testing. 
-
-With that in mind, some common doubts arise:
-
-- How to conduct these tests?
-- Where can I apply them? In which part of the page?
-- When can I start testing?
-- Why should I spend resources testing my store?
-
-### How?
-
-Currently, there are several tools on the market (paid or cost-free) for making an AB Test. I recommend using Google Analytics, which received resources from the former Google Optimizer to make AB Tests in a simple and fast manner. Just access your account in Analytics and find the tab **Content > Experiments**. The step-by-step can be easily followed, and you will not have much difficulty in running a test.
-
-I also recommend the Visual Website Optimizer tool. Despite being paid, this tool offers more advanced resources for making tests, and it also enables you to make changes on the page without the need to contact your front-end developer. It is worthwhile checking the test version of this tool to learn more about it. 
-
-All tests should be applied for a minimum period of one week, since weekend users have a browsing profile that differs from that of weekday users. When conducting a test, you must consider at least 1,000 prints for each version developed, that is, if you created two versions of one single page, do not draw any conclusion before the test is displayed at least 2,000 times. 
-
-### Where?
-
-Anywhere. All pages of your site can be included in AB Testing. The tests will enable you to have a better understanding of how users think, what works and what does not work on the internet.
-
-Tests can be applied in all page elements, such as button colors, texts, text color, font size, location of an element, page design, insertion of icons, size and type of images etc.
-The more you test, the greater will be your knowledge about the profile of users. 
-
-Even if tests do not help to increase your conversion rates, or even if they represent a significant decrease in results, they can be used for improving all other pages and boosting your conversion rates. 
-
-### When?
-
-A great advantage of AB Testing is that end users have no idea that they have participated in a test, since they will see only one version and be sure that that is their original page, regardless of the page presented. 
-There is thus no limit regarding the number of tests to be created and applied. So, just keep testing. 
-
-### Why?
-
-I could justify this question in many ways, but I will focus on the most important points:
-
-1. Only through AB Testing will you be able to make the best decisions for your store based on measurable data about your specific audience. Not everything that works for your competitors will work for you;
-2. Putting all your chips in a layout that is purely based on the designer’s feeling is dangerous and may result in losses. Personal taste is dangerous;
-3. It’s no good investing all your money in attracting traffic to your store, if it is not prepared to receive your visitors and convert them into buyers. Only applying these tests will you be able to know what must be done INSIDE your store to increase your conversion rates and take more advantage of the investment made in advertising, boosting your income, ROI, revenues etc.
diff --git a/docs/tutorials/en/access-control.md b/docs/tutorials/en/access-control.md
new file mode 100644
index 000000000..349044d08
--- /dev/null
+++ b/docs/tutorials/en/access-control.md
@@ -0,0 +1,61 @@
+---
+title: 'Access control'
+id: 4rM3gyiWqtkim4Q8hOvLTC
+status: DRAFT
+createdAt: 2023-11-30T16:29:30.077Z
+updatedAt: 2023-11-30T21:42:00.250Z
+publishedAt: 
+firstPublishedAt: 2023-11-30T21:40:59.550Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: access-control
+locale: en
+legacySlug: access-control
+subcategory: 1HSqkejwuYcQSMC400uY84
+---
+
+Every action on VTEX, such as accessing a page in the Admin or making an API call, requires a request to our infrastructure. To guarantee the security of these operations, there is **License Manager**, a system that verifies whether a user has the right permissions to perform an action on the platform.
+
+To make it easier to manage these permissions, License Manager uses a system based on [resources](#resources) and [roles](#roles). See below for more details on these concepts.
+
+## Resources
+
+A **resource** is an entity associated with an action or information within our infrastructure. For example, the _Product management_ resource allows a user to access and edit product information in the Catalog. To learn more about each available resource, read the [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) article.
+
+Each request undergoes a security analysis to check if the user has the necessary resources, i.e., the necessary permission to perform the action. Without the necessary resources, a request will not be successful.
+
+## Roles
+
+A **role** determines the set of resources accessible to a group of users on VTEX. Each admin user can be associated with one or more roles.
+
+As several employees often access the Admin, it is important to limit access to critical actions within an account. This minimizes disruptions in the store operation and ensures that each user has access only to the actions necessary for their role.
+
+For example, a team of telesales operators only needs access to order details, so they shouldn't have access to other platform settings. In this case, their role would only contain resources related to reading order details.
+
+To manage your store roles and their associated users, go to the [Roles list](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+Check below the different types of roles you can add to the store.
+
+### Role types
+
+When [creating a new role](https://help.vtex.com/en/tutorial/creating-roles--qGtNQpKSSAduX94l2WZBW), you can use one of the predefined roles provided by VTEX or create a customized one, selecting each required resource.
+
+The admin must have a role with the _Save access profile_ [resource](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) in order to create a role in License Manager.
+
+#### Predefined
+
+Predefined roles are sets of resources predetermined by VTEX that cover the most common use cases. Check the complete list of [predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy) and their permissions.
+
+#### Custom
+
+Besides using predefined roles, you can [create custom roles](https://help.vtex.com/en/tutorial/creating-roles--qGtNQpKSSAduX94l2WZBW#creating-custom-roles), combining the necessary resources for a group of admin users from your store.
+
+For example, a team responsible for keeping the store catalog up to date usually performs a well-defined set of tasks, such as adding and editing products, categories, and brands. In this case, an admin can create a customized role with all the necessary resources for these employees.
+
+Check the complete list of available [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
+
+## Learn more
+
+* [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [Creating roles](https://help.vtex.com/en/tutorial/creating-roles--qGtNQpKSSAduX94l2WZBW)
diff --git a/docs/tutorials/en/accessing-a-client-abandoned-cart.md b/docs/tutorials/en/accessing-a-client-abandoned-cart.md
index 2d46a5eab..115127076 100644
--- a/docs/tutorials/en/accessing-a-client-abandoned-cart.md
+++ b/docs/tutorials/en/accessing-a-client-abandoned-cart.md
@@ -29,26 +29,26 @@ Viewing these fields is very simple. Once logged in to your store Admin, just fo
 
 1. In the Admin sidebar, click __Master Data__;
 
-  ![Carrinho Abandonado - 1 - EN](https://images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/4e22ff4da9abc1b692ee236082a1c85d/4GdZSkwtm9f76BIVFnC65D_Masterdata_EN.jpg)
+  ![Carrinho Abandonado - 1 - EN](//images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/4e22ff4da9abc1b692ee236082a1c85d/4GdZSkwtm9f76BIVFnC65D_Masterdata_EN.jpg)
 
 2. Click the __Profile System__ Settings icon (gear);
 
-  ![Carrinho Abandonado - 2 - EN](https://images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/b22ea9f10722d249dd6bbda4ab6f43ac/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
+  ![Carrinho Abandonado - 2 - EN](//images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/b22ea9f10722d249dd6bbda4ab6f43ac/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
 
 3. Make sure you are in the __Applications__ tab;
 
-  ![Carrinho Abandonado - 3 - EN](https://images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/2cba845e608d8d2c577542351afebe1f/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
+  ![Carrinho Abandonado - 3 - EN](//images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/2cba845e608d8d2c577542351afebe1f/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
 
 4. Click Edit (Pencil icon) in the __Customers__ category;
 
-  ![Carrinho Abandonado - 4 - EN](https://images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/e2ec5bfae66b41f7b882a30510d08c51/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
+  ![Carrinho Abandonado - 4 - EN](//images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/e2ec5bfae66b41f7b882a30510d08c51/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
 
 5. Select __"Last Cart"__ and __"Cart"__ from the __Listing Options__;
 
-  ![Carrinho Abandonado - 5 - EN](https://images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/e74e93b98db80fd40db53d38efd7436a/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 5 - EN](//images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/e74e93b98db80fd40db53d38efd7436a/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
 
 6. Click __Save__.
 
-  ![Carrinho Abandonado - 6 - EN](https://images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/75c67997d3547b16653b09030778d91e/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
+  ![Carrinho Abandonado - 6 - EN](//images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/75c67997d3547b16653b09030778d91e/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
 
 With this, you can see the parameters of your customers' abandoned carts.
diff --git a/docs/tutorials/en/accessing-the-beta-environment.md b/docs/tutorials/en/accessing-the-beta-environment.md
index 8bcfb4b81..d87454f0d 100644
--- a/docs/tutorials/en/accessing-the-beta-environment.md
+++ b/docs/tutorials/en/accessing-the-beta-environment.md
@@ -1,10 +1,10 @@
 ---
-title: 'Accessing the beta environment through myvtex.com domain'
+title: 'Accessing the beta environment through the myvtex.com domain'
 id: 3BHM289568gcSwk2O80Asu
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-07-26T18:09:29.968Z
-updatedAt: 2019-12-31T15:26:39.674Z
-publishedAt: 2019-12-31T15:26:39.674Z
+updatedAt: 2024-03-13T12:00:57.622Z
+publishedAt: 2024-03-12T19:18:51.136Z
 firstPublishedAt: 2018-07-26T18:43:10.906Z
 contentType: tutorial
 productTeam: Reliability
@@ -15,26 +15,34 @@ legacySlug: accessing-the-beta-environment
 subcategory: Se4oi5LroIII2Ei0uGAoE
 ---
 
-In VTEX, all stores have a beta environment.
+On VTEX, all stores have a beta environment, where platform users (sales associates, developers, or other authorized users) can run tests to validate new settings or versions of applications/services before making changes to the stable environment.
 
-This environment is a testing site so the platform user can validate changes to a store before promoting the changes to the main environment.
-
-## How the beta environment works
+<div class = "alert alert-info">
+The beta environment is an exact replica of the stable environment, including store data and configurations.
+</div>
 
-The beta environment works as a testing environment for different versions of VTEX applications/services in your store. It is an environment that reproduces all the information of the main one (`stable`). So the store data is the same, both in beta and stable. Because of that, __changing data in the beta environment affects data in the stable environment__.
+In this way, **changing data in the beta environment will also affect data in the stable environment**.
 
 ## Accessing the beta environment
-
-The button that gives you access to the beta environment is located at the end of the Admin side menu. Just click `Use beta` to gain access to the testing environment.
-
-![usar-beta-en](https://images.ctfassets.net/alneenqid6w5/1k3Qb8gAGOsqQwMSK4Y6mG/579c06f9af8be8142bdd617ae2fdc502/usar-beta-en.png)
-
-<div class="alert alert-info">
-To return to the main environment, click <code>Use stable</code>, also located at the end of the Admin side menu.
+To access the beta environment in your store, enable the <code>vtex-commerce-env</code> cookie as follows: 
+
+<ol start="1">
+  <li>In the VTEX Admin, access the Dev. Tools in your browser by pressing the <code>F12</code> key or right-clicking and choosing the <b>Inspect</b> option.
+.</li>
+  <li>In the top bar of the screen, go to the <b>Application</b> tab, and in the left sidebar, under Cookies, click your store's URL.
+</li>
+  <li>In the table, enter the information below in the cells of the last row:
+</li>
+  <ul>
+<li>Name: <code>vtex-commerce-env</code></li>
+<li>Value: <code>beta</code>
+</li>
+</ul>
+<img src="https://images.ctfassets.net/alneenqid6w5/3g8wintA1heJbzdV8J0s45/8eb6f5917e2d9d8a134b81231dc42728/Ambiente_beta_.png" alt="beta">
+<li>Refresh the page by pressing <code>F5</code> or clicking the refresh button in your browser. Once the page has loaded, the store's Admin will already be in beta. 
+</li>
+</ol>
+
+<div class = "alert alert-info">
+To go back to the main store environment, return to the Dev. Tools panel in your browser and remove the vtex-commerce-env cookie. Refresh the page again to switch back to the <b>stable</b> environment.
 </div>
-
-## Checking for changes in the beta environment
- 
-To access your store in beta mode and see how changes have affected your store front, click on the `VISIT THE STORE` button once you have accessed the beta environment described in the previous step.
-
-![visite-a-loja-beta-en](https://images.ctfassets.net/alneenqid6w5/23HFLXk6I8OMSG8oGY4Wsw/cf4ef21978d3c1a2bb720d52b1468a0f/visite-a-loja-beta-en.png)
diff --git a/docs/tutorials/en/account-management.md b/docs/tutorials/en/account-management.md
index 1592a6c48..2ca076027 100644
--- a/docs/tutorials/en/account-management.md
+++ b/docs/tutorials/en/account-management.md
@@ -85,86 +85,10 @@ After a user has filled in and saved the **Name** and **E-mail** in the contacts
 The template for this automatic email can be changed in the <a href="https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84">Message Center</a> by modifying the <i>account registration</i> template.
 </div>
 
-![account registration](https://images.ctfassets.net/alneenqid6w5/I0CttFz6ayQW2Q8uOkKmc/19184a55a9a8de5cb3e04088251a9c93/account_registration.jpg)
+![account registration](//images.ctfassets.net/alneenqid6w5/I0CttFz6ayQW2Q8uOkKmc/19184a55a9a8de5cb3e04088251a9c93/account_registration.jpg)
 
 ## Security
 
 The [appKeys and appTokens](https://help.vtex.com/en/tutorial/chaves-de-aplicacao) used to authenticate integrations with your store are created here.
 
 Only the Sponsor user is allowed to create appKeys and appTokens, since they give access to your store via API, which can be critical if not used by skilled professionals.
-s tab, you can:
-
-- View [store list](#stores).
-- [Add new store](#creating-a-store).
-- [Edit store](#editing-a-store).
-- [Delete store](#deleting-a-store).
-
-By clicking the **Stores** tab at the top of the screen, you will see a list with all the information of all the stores created in your VTEX account.
-
-![Account details page - Stores](https://images.ctfassets.net/alneenqid6w5/rAFyEsEDLBDqj3UBGufrb/19d4e782db194e0482398ffa382a9565/2en.png)
-
-For each store, you can view the following details:
-
-- **Store name:** Name that will identify your store.
-- **Trading name:** Business name of your store.
-- **Hosts:** Domains related to the store.
-
-You can use the search box to filter the stores displayed in the list by any of the attributes.
-
-You can also [create a new store](#create-store), [edit a store](#edit-store), or [delete](# delete-store) existing stores.
-
-### Creating a store
-
-Follow the steps below to create a store:
-
-1. Go to the **Account** page by clicking your **profile avatar** that has the first letter of your email, and then go to **Account Settings** > **Account**.
-2. Click the **Stores** tab at the top of the screen.
-3. Click the `+ New Store` button.
-4. Fill in the basic store information:
-	- **Store name:** Name that will identify your store.
-	- **Trading name:** Business name of your store.
-	- **Locale:** Preset language associated with this store.
-	- **Trade policy:** [Trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#) you want to associate with the new store.
-5. If you wish to start the [go-live](https://help.vtex.com/en/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM) process for your store, fill in the **Hosts** field with your store's domain. Otherwise, leave it blank.
-6. Click the `Create` button.
-
-<div class = "alert alert-info">
-  To learn more about configuring your store's <b>Hosts</b>, read the article  <a href="https://help.vtex.com/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450">Configure your store domain</a>.
-</div>
-
-<div class="alert alert-warning">
-Do not use a ".com" domain in the Store Name field. This type of entry can only exist in the Hosts field.
-</div>
-
-### Editing a store
-
-Follow the steps below to edit information from an existing store:
-
-1. Go to the **Account** page by clicking your **profile avatar** that has the first letter of your email, and then go to **Account Settings** > **Account**.
-2. Click the **Stores** tab at the top of the screen.
-3. Click the action button<i class="fas fa-ellipsis-v"></i> corresponding to the store you want to edit.
-4. Click `Edit`.
-5. You will see the account edit page. Edit the information you want.
-6. Click `Save`.
-
-### Deleting a store
-
-Follow the steps below to delete a store:
-
-1. Go to the **Account** page by clicking your **profile avatar** that has the first letter of your email, and then on **Account Settings** > **Account**.
-2. Click the **Stores** tab at the top of the screen.
-3. Click the action button <i class="fas fa-ellipsis-v"></i> corresponding to the store you want to delete.
-4. Click `Delete`.
-5. You will see a confirmation modal. Click `Delete`.
-
-<div class="alert alert-warning">
-Note that the main store, indicated with a star next to its name in the store list, cannot be deleted.
-</div>
-
-Learn more:
-- [What is an account name?](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)
-- [Sponsor user](https://help.vtex.com/en/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy)
-- [Transferring store ownership](https://help.vtex.com/en/tutorial/transferencia-de-propriedade-da-loja)
-- [Configure your store's domain](https://help.vtex.com/en/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450)
-- [Go-live](https://help.vtex.com/en/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM)
-
diff --git a/docs/tutorials/en/account-settings-overview.md b/docs/tutorials/en/account-settings-overview.md
index 781d2e4df..11cf14d43 100644
--- a/docs/tutorials/en/account-settings-overview.md
+++ b/docs/tutorials/en/account-settings-overview.md
@@ -21,7 +21,7 @@ In the **Account Settings** section, you can control access to the Admin and cha
 
 To access the _Account Settings_ page, click on your **profile avatar**, which can be identified by the first letter of your email address, and click on **Account Settings**.
 
-![Admin v4 account settings menu EN](https://images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/c9f9e17c63ce76c40d01a650920ce5ff/Admin_v4_account_settings_menu_EN.jpg)
+![Admin v4 account settings menu EN](//images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/c9f9e17c63ce76c40d01a650920ce5ff/Admin_v4_account_settings_menu_EN.jpg)
 
 This section includes the following pages, soon to be included in Admin v4.
 
diff --git a/docs/tutorials/en/accounts-payable-brazil.md b/docs/tutorials/en/accounts-payable-brazil.md
index b7ec6d645..76635c7ac 100644
--- a/docs/tutorials/en/accounts-payable-brazil.md
+++ b/docs/tutorials/en/accounts-payable-brazil.md
@@ -3,8 +3,8 @@ title: 'Accounts Payable - Brazil'
 id: tutorials_660
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:25.003Z
-updatedAt: 2023-01-24T21:41:37.901Z
-publishedAt: 2023-01-24T21:41:37.901Z
+updatedAt: 2024-02-23T15:08:20.685Z
+publishedAt: 2024-02-23T15:08:20.685Z
 firstPublishedAt: 2017-04-27T23:03:40.609Z
 contentType: tutorial
 productTeam: Billing
@@ -15,4 +15,4 @@ legacySlug: accounts-payable-procedures
 subcategory: 22TaEgFhwE6a6CG2KASYkC
 ---
 
-<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to English speaking countries.</div>
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to English speaking countries. The English speaking countries version version is available at <a href="https://help.vtex.com/en/tutorial/accounts-payable-international--3yea9sIlsA0KgUC28ASCGs">Accounts Payable - International.</a> </div>
diff --git a/docs/tutorials/en/activating-new-vtex-cdn.md b/docs/tutorials/en/activating-new-vtex-cdn.md
index ed31cfc28..c71a2d289 100644
--- a/docs/tutorials/en/activating-new-vtex-cdn.md
+++ b/docs/tutorials/en/activating-new-vtex-cdn.md
@@ -1,10 +1,10 @@
 ---
 title: 'Activating the new VTEX CDN'
 id: 400JfRm4VGgsKgqgOw4WWA
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-10-02T23:12:05.096Z
-updatedAt: 2019-12-31T15:25:39.216Z
-publishedAt: 2019-12-31T15:25:39.216Z
+updatedAt: 2023-08-09T20:43:20.267Z
+publishedAt: 
 firstPublishedAt: 2017-10-03T02:09:58.361Z
 contentType: tutorial
 productTeam: Reliability
diff --git a/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md b/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md
index 6d38247f3..b922ed3c6 100644
--- a/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md
+++ b/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md
@@ -20,7 +20,7 @@ The **Lista Completa** link on the Categorias menu is frequently used in stores
 
 Look at the following example, for "Departamento 2":
 
-![categoria.en](https://images.ctfassets.net/alneenqid6w5/2GfnTZfCAPr9Baxn4dy1s/a6c97388bf36b6adc233112586d3e012/categoria.en.png)
+![categoria.en](//images.ctfassets.net/alneenqid6w5/2GfnTZfCAPr9Baxn4dy1s/a6c97388bf36b6adc233112586d3e012/categoria.en.png)
 
 The store has preferred to show only a few of its many categories in the menu.
 
@@ -29,6 +29,6 @@ You can configure this when registering the category, selecting **Menu with acti
 - If it is checked, the category appears in the menu.
 - If it is not checked, the category does not appear and the Lista Completa option will appear on the site.
 
-![categoria2.en](https://images.ctfassets.net/alneenqid6w5/3KtFDmEUqs71YobX8VOibJ/6b3709cb7741069a6ead068b9eb40a4c/categoria2.en.png)
+![categoria2.en](//images.ctfassets.net/alneenqid6w5/3KtFDmEUqs71YobX8VOibJ/6b3709cb7741069a6ead068b9eb40a4c/categoria2.en.png)
 
 
diff --git a/docs/tutorials/en/adapting-your-integration-for-change-order-beta.md b/docs/tutorials/en/adapting-your-integration-for-change-order-beta.md
new file mode 100644
index 000000000..91259be34
--- /dev/null
+++ b/docs/tutorials/en/adapting-your-integration-for-change-order-beta.md
@@ -0,0 +1,305 @@
+---
+title: 'Adapting your integration for Change order (Beta)'
+id: 6kGQWs0IvpwIZoyeoLMjlp
+status: PUBLISHED
+createdAt: 2024-06-03T18:54:30.094Z
+updatedAt: 2024-07-09T17:18:19.900Z
+publishedAt: 2024-07-09T17:18:19.900Z
+firstPublishedAt: 2024-06-03T20:02:10.248Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: adapting-your-integration-for-change-order-beta
+locale: en
+legacySlug: adapting-your-integration-for-change-order-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+To evolve the VTEX platform for order changes, we are launching [Change order (Beta)](https://help.vtex.com/en/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ), a more complete and flexible solution that provides a [new experience in the VTEX Admin](https://help.vtex.com/en/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw).
+
+After interactions between our engineering team, clients, and partners who have joined the beta version, we created this content with the best implementation practices and frequently asked questions. The goal is for future clients and partners to have this support material when they start using **Change order (Beta)**.
+
+The content is organized as follows:
+
+- [Adapting to different use cases](#adapting-to-different-use-cases)
+- [Changes in the request body](#changes-in-the-request-body)
+- [Requests with errors and failures](#requests-with-errors-and-failures)
+- [Frequently Asked Questions (FAQ)](#frequently-asked-questions-faq)
+
+## Adapting to different use cases
+
+The following sections outline the main use cases for **Change order (Beta)** and their recommendations.
+
+### Communication with customers via transactional email
+
+**Change order (Beta)** uses new templates for [transactional emails](https://help.vtex.com/en/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my) (Message Center) to cover the solution's innovative features.
+
+To customize an email template in the VTEX Admin, copy and paste the link below into your browser, replacing `{accountName}` with your store's [account name](https://help.vtex.com/en/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC), and then click `Enter`:
+
+`https://{accountName}.myvtex.com/admin/message-center/#/templates/vtexcommerce-order-changed-v2`
+
+### Managing order changes through the VTEX Admin
+
+For stores using the current version to change orders through the VTEX Admin, the updated interfaces will be immediately available for you to use **Change order (Beta)** once the VTEX team has installed the new solution. This includes new management features and communication tools for [My Account](https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#pedidos) and [transactional email templates](https://help.vtex.com/en/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my).
+
+### Managing order changes via API
+
+For stores that use our APIs, the implementation in the integration must comply with the new feature architecture.
+
+In **Change order (Beta),** the [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) endpoint works asynchronously, and the [user](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) or integration that makes the request receives a `requestId` from the platform, which is a unique identifier to track the order change operation. This identifier will later be used in some of the endpoints. All the **Change order (Beta)** endpoints are:
+
+* [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes)
+* [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview)
+* [Get order change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-)
+* [Get order change history](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes)
+* [Retry order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry)
+* [Cancel order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel)
+
+After changing the order using the [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) endpoint, for new requests to the **Change order (Beta)** endpoints, you have the following options for the integrator:
+
+* **Polling:** Low complexity.
+* **Preview:** Medium complexity.
+
+The table below describes each one:
+
+| **Flow type** | **How it works** |
+| :---: | :--- |
+| **Polling**<p>Low complexity</p> | <p>After the change order operation, a unique code, the `requestId`, is generated to identify the order change. You can use it to follow the details of the request through the <a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get change details</a> endpoint. In this endpoint, once the request has been changed, the response body property `finished` is set to `true`.</p><p>In addition, <a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get change details</a> can also be used to obtain information about failures and errors that resulted in the eventual cancellation of the change order operation, as will be described in the section <a href="#requests-with-errors-and-failures">Requests with errors and failures</a>.</p> |
+| **Preview**<p>Medium complexity</p> | <p>Before making a request to <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a>, the integration can make a preview that will result in a response body identical to the change request. To do so, use the same request body in the request to the <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a> endpoint.</p><p>This preview is a simulated change and does not generate any real changes to the order. Using <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a> is useful for obtaining the total values associated with the order change being made and for validating the request details with a valid request body.</p><p>After receiving a successful `200 OK` response for a preview of the change, the integration can proceed with the request to <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> to change the order.</p><p>Then, the integration can be adapted to scenarios such as:<ul><li><b>Optimistic scenario:</b> The validation data obtained by simulating the change covers most of the `200 OK` success scenarios.</li><li><b>Polling implementation:</b> Mentioned above.</li></ul></p> |
+
+## Changes in the request body
+
+**Change order (Beta)** maintains some attributes of the previous solution, but others have been created or modified in terms of nomenclature and functioning. The main changes have been organized as follows:
+
+* [Manual values](#manual-values)
+* [Adding and removing items](#adding-and-removing-items)
+* [Attributes of mandatory and optional items](#attributes-of-mandatory-and-optional-items)
+* [User responsibility in system automation](#user-responsibility-in-system-automation)
+
+### Manual values
+
+* **Previously:** The `discountValue` and `incrementValue` fields defined the value of the change being made to the order by decreasing or increasing a value, respectively. The user calculated the change value, and the result was added to or subtracted from the order total amount using these fields.
+  > **Example:** When adding a $50 item to a $100 order, the user would send the `incrementValue` as $50, and the system would update the order total to $150. To apply a $30 discount for the customer, the user had to send the `discountValue` of $30, resulting in a revised order total of $120.
+* **Now:** The new `manualDiscountValue` and `manualIncrementValue` fields set additional manual values to be added to or subtracted from the total order amount regardless of the changes made. As the system automatically calculates the changes (considering the price and conditions when the order was placed), the user can add or subtract values using the fields mentioned.
+  > **Example:** When adding a $50 item to a $100 order, the system automatically adjusts the total to $150. Users are not required to update the amount manually. If a discount of $30 is needed, users can simply send the `manualDiscountValue` field as $30, resulting in a new total of $120.
+
+### Adding and removing items
+
+* **Previously:** The attributes used to add and remove items from the order were the `itemsAdded` and `itemsRemoved` arrays, which contained item objects with the `id`, `price`, and `quantity` fields.
+* **Now:** The attributes for adding and removing items from the order are the `add` and  `remove` objects. They contain a new level that defines an object for each item via the `items` array.
+
+Example of removing items in **Change order (Beta)**:
+
+```
+{
+    "remove": {
+         items": [
+            {
+             "id": "1",
+             "quantity": 1
+            }
+        ]
+    }
+}
+```
+
+<br>
+
+### Attributes of mandatory and optional items
+
+The items in the request body need fewer mandatory attributes than before: `id` and `quantity`. The other attributes are obtained from the request or the Catalog system.
+
+If you need to add or change existing items, you can change other fields to override the information for an item being changed. The optional fields are `price`, `unitMultiplier`, and `measurementUnit`. The system disregards any other fields sent in the request.
+
+### User responsibility in system automation
+
+* **Previously:** Users had to calculate the value to be changed in the order. They used to send this value via the `discountValue` or `incrementValue` attributes, depending on whether the change was an increase or decrease in price.
+* **Now:** The system provides item information and automatically calculates the final order amount after the change. Users only need to enter the minimum information required and no longer calculates the final order amount, which reduces potential errors.
+
+## Requests with errors and failures
+
+When an error or failure occurs in **Change order (Beta)**, information about the processing can be obtained from the [Get change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-) endpoint via the `logs` attribute.
+
+Example of `logs` with a processing error:
+
+```
+{
+    "requestId": "de88ad2b-a927-47ad-b5af-a6fab4d2a22f",
+    "workflowId": "418827ee-0efd-4127-87c0-6d881358b750",
+    "status": "preparing",
+    "finished": false,
+    "reason": "test",
+    "manualDiscountValue": 1000,
+    "manualIncrementValue": 0,
+    "totalChangeValue": 0,
+    "totals": [],
+    "add": {
+        ...
+    },
+    "logs": [
+       {
+            "date": "2024-05-13T21:35:00.1952066Z",
+            "message": "Automatic transition failed. Current retry counter is 1. Failed with message: Failure to run the action 'preparing'. Content: '{\"error\":{\"code\":\"001\",\"message\":\"An error has occurred\"},\"operationId\":\"f69e8934-5f93-4ba2-9ebe-408080c6733b\",\"fields\":{}}'",
+            "source": "Workflow Engine",
+            "status": "preparing"
+        },
+        {
+            "date": "2024-05-13T21:35:00.1481754Z",
+            "message": "OperationId:f69e8934-5f93-4ba2-9ebe-408080c6733b\nSystem.NullReferenceException: Object reference not set to an instance of an object.\n   at VTEX.SOS.Services.OrderService.OrderServiceCapabilities.ChangeOrderV2.ChangeOrderMerger.MergeWithEnrichedItemMetadata(Seller seller, OrderItem itemToEnrich, OrderItem enrichedItem)\n   at VTEX.SOS.Services.OrderService.OrderService.FillAddedItemMetadataAsync(IContext context, IEnumerable`1 enrichedOrderItems, Seller seller, OrderItem addedItem, String salesChannel, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 284\n   at VTEX.SOS.Services.OrderService.OrderService.FillAddedItemInfoAsync(IContext context, OrderSource orderOrigin, IEnumerable`1 enrichedOrderItems, Seller seller, OrderItem addedItem, String salesChannel, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 273\n   at VTEX.SOS.Services.OrderService.OrderService.EnrichItemsOnlyAsync(IContext context, Order order, ChangeOrderInput changeOrderInput, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 238\n   at VTEX.SOS.Services.OrderService.OrderService.PrepareChangeOrderAsync(IContext context, Order order, ChangeOrderInput changeOrderInput, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 38\n   at VTEX.SOS.Services.OrderService.ChangeOrderService.PrepareChangeInternalAsync(String orderId, String changeRequestId, IContext context, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Service/ChangeOrderService.cs:line 288\n   at VTEX.SOS.Services.OrderService.ChangeOrderService.PrepareChangeInternalAsync(String orderId, String changeRequestId, IContext context, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Service/ChangeOrderService.cs:line 288",
+            "source": "ChangeOrderService:PrepareChangeInternalAsync",
+            "status": "preparing"
+        }
+    ]
+}
+```
+
+<br>
+
+For each system failure (untreated errors), the system automatically makes new processing attempts. If the new attempts don't work, the change request is canceled, and the reason for the error can be found using the [Get change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-) endpoint via the `cancellationData` attribute.
+
+If the source of the error is the user's non-compliance with the request validation rules, the operation will be canceled automatically, and no further processing attempts will be made. In this case, the reason for the error is also communicated via `cancellationData`.
+
+Example of the `cancellationData` object: The price change requested exceeds the limit value set for canceling orders.
+
+```
+{
+    "requestId": "29004325-e2b8-4b7e-a82c-f588e6d3c07f",
+    "workflowId": "ea392ae2-1db5-432c-97d3-adc4436ca4aa",
+    "status": "canceled",
+    "finished": false,
+    "reason": "test",
+    "manualDiscountValue": 37500,
+    "manualIncrementValue": 0,
+    "totalChangeValue": 0,
+    "totals": [],
+    "remove": {
+        ...
+    },
+    "cancellationData": {
+        "requestedByUser": false,
+        "reason": "The value of the change exceed the order's price",
+        "cancellationDate": "2024-05-13T21:31:38.8596Z"
+    }
+}
+```
+
+<br>
+
+## Frequently Asked Questions (FAQ)
+
+This section gathers commonly asked questions from clients and partners who use **Change order (Beta)**:
+
+[1 - How do I overwrite the price of a specific item?](#1-how-do-i-overwrite-the-price-of-a-specific-item)
+
+[2 - How do I know and change the total amount of the order before it is changed?](#2-how-do-i-know-and-change-the-total-amount-of-the-order-before-it-is-changed)
+
+[3 - Do I need to indicate the shipping cost, or is it automatically recalculated?](#3-do-i-need-to-indicate-the-shipping-cost-or-is-it-automatically-recalculated)
+
+[4 - How do promotions work in Change orders (Beta)?](#4-how-do-promotions-work-in-change-orders-beta)
+
+[5 - What should I do when the request leads to a canceling or canceled status?](#5-what-should-i-do-when-the-request-leads-to-a-canceling-or-canceled-status)
+
+### 1 - How do I overwrite the price of a specific item?
+
+You can apply a manual value to a specific item's price while changing its quantity to overwrite its price.
+
+In the [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) endpoint, the `price` attribute has the same function as for the order placing flow and refers to the nominal price of the item. For example, in an order with a weighable item, such as an apple, the `price` refers to the kilo price of apples.
+
+Example of price overwriting on a weighable item:
+
+```
+{
+    "reason": "the client wanted to change",
+    "add": {
+        "items": [
+            {
+                "id": "1",
+                "quantity": 1,
+                "price": 150,
+            }
+        ]
+}
+```
+
+<br>
+
+### 2 - How do I know and change the total amount of the order before it is changed?
+
+The [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) endpoint allows the user to simulate the order change to be made with [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), as it uses the same request body and provides the same response body but without changing the order. The `totalChangeValue` attribute indicates the total value being changed in the order, either to a higher value (e.g., tax or adding items) or a lower value (e.g., manually reducing the price or removing items).
+
+If you want the integration to handle variations in the order amount, you can use the same request body as in the [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) and use it in a request to [Create an order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), adjusting the values of the `manualIncrementValue` and `manualDiscountValue` fields up or down respectively.
+
+### 3 - Do I need to indicate the shipping cost, or is it automatically recalculated?
+
+When item quantity, size, or weight changes, the shipping cost is automatically recalculated and added to the new order total.
+
+The rule for calculating the new shipping cost follows the same conditions applied when the order was placed.
+
+### 4 - How do promotions work in Change orders (Beta)?
+
+Changing the order automatically applies the same promotions and taxes that were valid for the items when the order was placed, but only replicates the conditions that were valid then. New promotions and taxes are not recalculated under the changed order conditions.
+
+**Example:** In one store, there was a 'Get 3 for the price of 2' promotion. However, the customer only purchased 2 items initially and did not qualify for the discount. If the customer then decides to add one more item to the order, making it a total of 3 items purchased, they still wouldn't receive the promotion because it wasn't part of the original order.
+
+You can inform the promotion of an item when you change the order manually with[ Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) using the `priceTags` attribute. This is already the platform's default behavior.
+
+Example of an item with promotions applied to the original order:
+
+```
+{
+    "reason": "teste",
+    "replace": [
+        {
+            "from": {
+                "items": [
+                    {
+                        "id": "16",
+                        "quantity": 1,
+                        "measurementUnit": "kg",
+                        "unitMultiplier": 0.5
+                    }
+                ]
+            },
+            "to": {
+                "items": [
+                    {
+                        "id": "16",
+                        "quantity": 1,
+                        "measurementUnit": "kg",
+                        "unitMultiplier": 0.750,
+                        "price": 530,
+                        "priceTags": [
+                            {
+                                "name": "DISCOUNT@MANUALPRICE",
+                                "value": -50,
+                                "isPercentual": false
+                            }
+                        ]
+                    }
+                ]
+            }
+        }
+    ]
+}
+```
+
+<br>
+
+In this example, the manual discount tag used was `DISCOUNT@MANUALPRICE`. The equivalent for manual rates would be `TAX@MANUALPRICE`. The [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) endpoint also allows you to use the `priceTag` attribute of an existing promotion and change its value when changing the order.
+
+### 5 - What should I do when the request leads to a canceling or canceled status?
+
+The statuses `canceling` and `canceled` mean that the order change was not processed correctly and not applied to the order, so the user can disregard the request. Failures and errors can occur due to:
+
+* User non-compliance with the request validation rules.
+* Exceeded number of automatic reprocessing attempts by the system.
+* Other system processing failures.
+
+The general recommendation is to investigate the error source and check the request body being sent from the [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) or [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) endpoints. Learn more in the section [Requests with errors and failures](#requests-with-errors-and-failures).
+
+## Learn more
+
+| **Help Center** | **Developer Portal** |
+| :--- | :--- |
+| <p>Changing orders in the VTEX Admin:<ul><li><a href="https://help.vtex.com/en/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">How Change order works (Beta)</a></li><li><a href="https://help.vtex.com/en/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw">How to change orders (Beta)</a></li></ul></p> | <p>Changing orders via API:<ul><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change details</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes">Get order change history</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry">Retry order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel">Cancel order change</a></li></ul></p> |
+
diff --git a/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md b/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md
index 0c07238e0..2c7323d11 100644
--- a/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md
+++ b/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md
@@ -3,8 +3,8 @@ title: 'Add 3DS support to the integration with Adyen'
 id: 3DNZeC9qJaC2GMIw4mawYk
 status: PUBLISHED
 createdAt: 2017-07-25T18:20:05.681Z
-updatedAt: 2023-03-26T22:04:52.559Z
-publishedAt: 2023-03-26T22:04:52.559Z
+updatedAt: 2024-06-13T21:44:14.602Z
+publishedAt: 2024-06-13T21:44:14.602Z
 firstPublishedAt: 2017-08-01T16:58:04.306Z
 contentType: tutorial
 productTeam: Financial
@@ -20,10 +20,10 @@ To add support for [3DS](https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1e
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. Access the __Gateways Affiliations__ tab.
 3. Click on the Adyen affiliation card.
-4. Go to __Live Endpoint URL Prefix__ and follow [this Adyen tutorial](https://www.adyen.help/hc/en-us/articles/360014322079-How-can-I-find-the-endpoint-URL-for-my-LIVE-account-) to get the necessary information.
+4. Go to __Live Endpoint URL Prefix__ and follow [this Adyen tutorial](https://help.adyen.com/en_US/knowledge/ecommerce-integrations/integrations-basics/how-can-i-find-the-endpoint-url-for-my-live-account) to get the necessary information.
 5. In the field __Enable 3D Secure?__, select __Yes__.
 6. Choose the 3DS mode — 3DS, 3DS2, or 3DS2 Data only — defined in the agreed-upon business partnership with Adyen.
-7. Fill in the remaining fields according to [this tutorial](https://help.vtex.com/en/tutorial/como-configurar-o-gateway-adyen-na-vtex--tutorials_2337).
+7. Fill in the remaining fields according to [this tutorial](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv).
 8. Click on __Save__.
 
 ### Enable 3DS Responses
diff --git a/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md b/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md
index 67b949282..e75e021b8 100644
--- a/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md
+++ b/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md
@@ -26,4 +26,4 @@ The file structure must be as follows:
 - Column D: Data Inicial (DD/MM /YYYY format)
 - Column E: Data Final (DD/MM /YYYY format)
 
-![urlbuilder en](https://images.ctfassets.net/alneenqid6w5/4rLD4jAM0oaq6CqQam6U4y/895ec67d0ac775529a71b8536e4b03bd/urlbuilder_en.png)
+![urlbuilder en](//images.ctfassets.net/alneenqid6w5/4rLD4jAM0oaq6CqQam6U4y/895ec67d0ac775529a71b8536e4b03bd/urlbuilder_en.png)
diff --git a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
index 17277e0d4..b34697e78 100644
--- a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
+++ b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
@@ -1,10 +1,10 @@
 ---
-title: 'Adding a Client Id and a Client Secret to log in with Facebook'
+title: 'Adding Client ID and Client Secret for Facebook Login'
 id: 3R7rzXWG1GswWOIkYyy8SO
 status: PUBLISHED
 createdAt: 2017-08-29T17:46:04.080Z
-updatedAt: 2023-02-08T14:33:31.750Z
-publishedAt: 2023-02-08T14:33:31.750Z
+updatedAt: 2023-10-20T21:29:11.632Z
+publishedAt: 2023-10-20T21:29:11.632Z
 firstPublishedAt: 2017-08-29T17:51:41.650Z
 contentType: tutorial
 productTeam: Identity
@@ -15,53 +15,73 @@ legacySlug: registering-a-client-id-and-a-client-secret-for-login-with-facebook
 subcategory: 14V5ezEX0cewOMg0o0cYM6
 ---
 
-To activate Facebook login with OAuth2, you must access the VTEX ID in your admin and fill in the `Client ID` and `Client Secret` fields, as described [in this article](/en/tutorial/configuring-user-id-with-facebook-and-google).
-
-![Facebook OAuth EN](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/06b29f9c839316df31c736a315ba1786/facebook_EN.png)
-
-To get these values, follow the steps below:
-
-1. Access the link [`https://developers.facebook.com/`](https://developers.facebook.com/);
-2. Create a Facebook developer account;
-3. Create a Facebook login application;
-4. At the top right, click on __My apps__;
-    ![Meus Aplicativos Facebook EN](https://images.ctfassets.net/alneenqid6w5/2XUFbJ20Z1Op022DLzNru7/4ffc7fddf5e06de99b4901bc6a940fe2/Meus_Aplicativos_Facebook_EN.png)  
-5. Click on Create App;
-6. Choose the __Manage Business Integrations__ option;
-    ![Criar ID Aplicativo Facebook EN](https://images.ctfassets.net/alneenqid6w5/4nEHH7m3rzaIjNyXCS7jwQ/ef467a17654f0eccc57811bbfcd79e7c/Facebook_Login_App_Type_EN.png)
-7. Fill in the __App Display Name__ field with your store's name;
-8. In __App Purpose__, choose the option that best meets the needs of your store;
-9. Click on __Create App ID__;  
-    ![Configurar Criação ID Aplicativo Facebook EN](https://images.ctfassets.net/alneenqid6w5/aJ4qEYEBdQXp3IkQwcwBe/6dfdb4e775e1c317d707796192577558/App_details_EN.png)
-10. Select __Set up__ in the __Facebook Login__ option;
-    ![Adicionar Configuração Login Facebook EN](https://images.ctfassets.net/alneenqid6w5/4Kz42ev7FSm0uEYIYwQ8C8/189d96e7550b9334931049e6e4ec41e2/add_products_EN.png)
-
-11. In __Products__, on the left side dashboard, click __Facebook Login > Settings__.
-    ![Login Configurações Menu Facebook EN](https://images.ctfassets.net/alneenqid6w5/7CosZB53qkywCS1NG3Cj0r/6a0236dc8c74df2661ad5faff74e6e23/menu_configura____es_EN.png)
-    Set the options as in the image below:
-    ![Configuração URI OAuth Facebook EN](https://images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/ef5ad727b07d41fdd907cef762788dd6/configuracoes_Oauth_EN.png)
-    Insert the following URLs in __Valid OAuth Redirect URIs__, replacing `{{HOST_URL}}` with your store's base URL and `{{accountName}}` with your account name as described in the store's administration menu:
-    - `https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
-    - `https://{{HOST_URL}}/api/vtexid/pub/authentication/oauth/authorizationcode`
-    - `https://{{accountName}}.myvtex.com/api/vtexid/pub/authentication/oauth/authorizationcode`
-
-12. At the bottom of the page, click on the __Save Changes__ button.
-    ![Salvar Alterações EN](https://images.ctfassets.net/alneenqid6w5/6xrSjyVnjTdpMwK6mmg7qQ/73dc3e3471df55544d445dba41ebe32f/Salvar_Altera____es_EN.png)
-
-13. Access __Settings > Basic__ on the left side dashboard.
-    ![Menu Configurações Aplicativo Facebook EN](https://images.ctfassets.net/alneenqid6w5/2hW7fOAt85ErH30RUI9KLA/49da02c39bac5ba28817f7fdfb8fb24d/menu_configura____es_b__sica_EN.png)
-
-14. In __App Secret__, click on the __Show__ button.
-    - Copy the __App ID__ field and paste it in the `Client Id` field on the VTEX ID admin.
-    - Copy the __App Secret__ field of the Facebook App and paste it in the `Client Secret` field in the VTEX ID admin.
-    ![ID Chave Facebook EN](https://images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/c54a397045c8f5585e76b0b9de7c0a74/ID_Chave_Facebook_EN.png)
-
-15. Upload an icon for your application of exactly 1024x1024 pixels and with a transparent background.
-16. Add the __URL of the Privacy Policy__ of your store;
-    ![Configuração Básica Facebook EN](https://images.ctfassets.net/alneenqid6w5/66rxFKyvG7eCptwC7BdSWT/3b13d29d6ef24ada8e777062b2deede2/Configura____o_B__sica_Facebook_EN.png)
-17. Select a __Category__. For stores, we suggest __Shopping__;
-    ![Categoria Facebook EN](https://images.ctfassets.net/alneenqid6w5/20X5DqI7WEuGwksOO6cMS2/48f596d2da1d4d2395424bdd2db14029/Categoria_Facebook_EN.png)
-18. Below in this form, fill in the __Data Protection Officer Contact Information__ field with the data of the company responsible for the store;
-    ![Endereço Facebook EN](https://images.ctfassets.net/alneenqid6w5/3TenJ8YunJ6gFRs0aZQkp7/79e44d0029bb492e1a5383334f4a8f6c/Endere__o_Facebook_EN.png)
-19. At the bottom of the page, click on __Save Changes__;
-    ![Salvar Alterações EN](https://images.ctfassets.net/alneenqid6w5/6xrSjyVnjTdpMwK6mmg7qQ/73dc3e3471df55544d445dba41ebe32f/Salvar_Altera____es_EN.png)
+To enable login via Facebook, in your VTEX Admin, go to **Account Settings > Authentication** and complete the **Client ID** and **Client Secret** fields, as described in the [Configuring login with Facebook and Google](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513) article.
+
+![Facebook OAuth EN](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/7daac156505a588b95fc0e90fbc08e2d/1-login-fb-en.PNG)
+
+To get these credentials, follow the instructions below:
+
+1. [Create an app](#1-creating-an-app)
+2. [Configure Facebook Login in the app](#2-configuring-facebook-login-in-the-app)
+3. [Configure the app's basic settings](#3-configuring-the-apps-basic-settings)
+
+## 1. Creating an app
+
+To begin, you need to create a Facebook application by following the steps below:
+
+1. Access the [Meta for Developers](https://developers.facebook.com/) website.
+2. Create a Facebook developer account.
+3. Once logged in, click **My Apps** in the top bar.
+4. Click `Create App`.
+5. Click **Allow people to log in with their Facebook** account from the options shown below.
+
+   ![2-login-fb-en](//images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/18115fc2fab3b2efa194681f5f46d1cc/2-login-fb-en.png)
+
+6. Click `Next`.
+7. Enter the app name and the email address of the person in charge of the app in the fields illustrated below.
+
+   ![3-login-fb-en](//images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/6a66ed67c5576d710573f0ab9642b9eb/3-login-fb-en.png)
+
+8. Click `Create app`.
+
+## 2. Configuring Facebook Login in the app
+
+The next step is to set up the Facebook Login product in the app you created. To do this, follow the instructions below:
+
+1.	Click **Products** in the side menu or the Meta for Developers **Dashboard**, as in the image below.
+
+   ![4-login-fb-en](//images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/ee51c9db1b9c5d6c8f9298a901b74d5c/4-login-fb-en.png)
+
+2. Click `Configure` and select `Settings`.
+
+   ![5-login-fb-en](//images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/0c913b1d202594789f0986427c404a7e/5-login-fb-en.png)
+
+3. Set the options as in the image below:
+
+   ![Configuração URI OAuth Facebook EN](//images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/ef5ad727b07d41fdd907cef762788dd6/configuracoes_Oauth_EN.png)
+
+   Insert the following URLs in **Valid OAuth Redirect URIs**, replacing `{{HOST_URL}}`  with your store's base URL and e `{{accountName}}` with your VTEX account name as described in the store's Admin:
+
+      * `https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
+      * `https://{{HOST_URL}}/api/vtexid/pub/authentication/oauth/authorizationcode`
+      * `https://{{accountName}}.myvtex.com/api/vtexid/pub/authentication/oauth/authorizationcode`
+
+4. At the bottom of the page, click the `Save Changes` button.
+
+## 3. Configuring the app's basic settings
+
+Finally, you must complete specific information about the app to finish the registration process. In this step, you will obtain the **Client ID** and **Client Secret**. These will be used when configuring the Facebook login settings in the VTEX Admin. Please follow the steps below:
+
+1.	In the Meta for Developers side menu, go to **App settings** and click **Basic:**
+
+   ![7-login-fb-en](//images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/a572a3a7fea37cbec1cded5f5bd95ca4/7-login-fb-en.png)
+
+2. Copy the value from the **App ID** field. You must enter this value in the **Client ID** field when[ configuring Facebook Login in the VTEX Admin](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513).
+3. Under **App Secret**, click the **Show** button, and then copy the value from the field. You must enter this value in the **Client Secret** field when [configuring Facebook Login in the VTEX Admin](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513).
+4. Add the link to your store's terms of service in the **Terms of Service URL** field.
+5. Under **App Icon (1024 x 1024)**, add an icon of exactly 1024x1024 pixels and a transparent background for your app.
+6. **Choose a Category**. For stores, we recommend using **Shopping**.
+7. Below in this form, complete the **Data Protection Officer Contact Information** with the details of the company running the store.
+8. At the bottom of the page, click `Save Changes`.
+
+Once you have completed all these steps, you can use the **Client ID** and **Client Secret** you obtained to configure Facebook Login in your store, as detailed in the [Configuring login with Facebook and Google](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513) article.
diff --git a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
index 7e475d2a5..e2fa73315 100644
--- a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
+++ b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 To activate Google login with OAuth2, you must access the VTEX ID in your admin and fill in the `Client ID` and `Client Secret` fields, as described [in this article](/en/tutorial/configuring-user-id-with-facebook-and-google).
 
-![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
+![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
 
 These values are derived from a project that needs to be created in the Google Cloud Platform API service.
 
@@ -30,17 +30,17 @@ The steps mentioned below describe a third-party platform and may therefore be o
 1. Access the link [`https://console.developers.google.com/`](https://console.developers.google.com/);
 2. In the side tab, click on __Credentials__;
 3. Click on __Create Project__;
-    ![Criar Projeto Google EN](https://images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/6aa68d7e981fd534a35ef3046b8d4cc2/Criar_Projeto_Google_EN.png)
+    ![Criar Projeto Google EN](//images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/6aa68d7e981fd534a35ef3046b8d4cc2/Criar_Projeto_Google_EN.png)
 4. Name the project and click on __Create__;
-    ![Novo Projeto Google EN](https://images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/aba1e15eee652b262a3932ffa87cdf02/Novo_Projeto_Google_EN.png)
+    ![Novo Projeto Google EN](//images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/aba1e15eee652b262a3932ffa87cdf02/Novo_Projeto_Google_EN.png)
 5. Click on __Create credentials__;
-    ![Criar Credenciais Google EN](https://images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/b5916fc567067ef1c3dcb464d392be4f/Criar_Credenciais_Google_EN.png)
+    ![Criar Credenciais Google EN](//images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/b5916fc567067ef1c3dcb464d392be4f/Criar_Credenciais_Google_EN.png)
 6. Select the __OAuth client ID__ option;
-    ![ID cliente OAuth Google EN](https://images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/66104a80f14e2ea12cd894435ddf0843/ID_cliente_OAuth_Google_EN.png)
+    ![ID cliente OAuth Google EN](//images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/66104a80f14e2ea12cd894435ddf0843/ID_cliente_OAuth_Google_EN.png)
 7. Click on __Configure consent screen__;
-    ![Configurar Tela Consentimento Google EN](https://images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/5b057c3ce55c3207415d1b37117b5ac1/Configurar_Tela_Consentimento_Google_EN.png)
+    ![Configurar Tela Consentimento Google EN](//images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/5b057c3ce55c3207415d1b37117b5ac1/Configurar_Tela_Consentimento_Google_EN.png)
 8. Choose the type of user for your store(__Internal__ or __External__) and click on __Create__;
-    ![Tipo usuário Google EN](https://images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/2f15aac33884886b494137342ebadaf6/Tipo_usu__rio_EN.png)
+    ![Tipo usuário Google EN](//images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/2f15aac33884886b494137342ebadaf6/Tipo_usu__rio_EN.png)
 9. __Application name__: will be shown to clients when logging in;
 10. __User support email__: for users to contact you with question about their consent;
 11. __App logo__: corresponds to your store logo;
@@ -49,19 +49,19 @@ The steps mentioned below describe a third-party platform and may therefore be o
     - `vtex.com.br`, regarding our backend servers
 13. __Developer contact information__: these email addresses are for Google to notify you about any changes to your project;
 14. Click on __Save and continue__;
-    ![Configurações Tela Consentimento EN](https://images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4d3a9c16d4a83dfc8559f8ddab04cd6f/Configura____es_Tela_Consentimento_EN.png)
+    ![Configurações Tela Consentimento EN](//images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4d3a9c16d4a83dfc8559f8ddab04cd6f/Configura____es_Tela_Consentimento_EN.png)
 13. In the left side menu, click on __Credentials__;
 14. In Type of application, click on __Web Application__;
-    ![Credenciais Aplicativo Web Google EN](https://images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/68c4968faa050c891f7501420d7fc6c8/Credenciais_Aplicativo_Web_Google_EN.png)
+    ![Credenciais Aplicativo Web Google EN](//images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/68c4968faa050c891f7501420d7fc6c8/Credenciais_Aplicativo_Web_Google_EN.png)
 15. __Name__: for internal identification;
 16.  __Authorized JavaScript origins__: add the exact addresses that can use this authentication method, corresponding to your site; for example `https://www.mystore.com`. We also recommended that you add the address `https://{{accountName}}}.myvtex.com` of your account, where `{{accountName}}` is your account name as described in the store's admin menu;
 17. __Authorized redirect URIs__: add the VTEX service URL:
     -`https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
-    ![Configurações Aplicativo Web Google EN](https://images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/9e9b216146ef6285903e647722080234/Configura____es_Aplicativo_Web_EN.png)
+    ![Configurações Aplicativo Web Google EN](//images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/9e9b216146ef6285903e647722080234/Configura____es_Aplicativo_Web_EN.png)
 
 18. After you complete these steps, your credentials will be displayed:
-    ![Cliente OAuth criado Google EN](https://images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/b2db65f7598baba9de8f6ecd7d3aa70e/Cliente_OAuth_criado_Google_EN.png)
+    ![Cliente OAuth criado Google EN](//images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/b2db65f7598baba9de8f6ecd7d3aa70e/Cliente_OAuth_criado_Google_EN.png)
     - Copy the __Client ID__ from Google and paste it into the `Client Id' field in the VTEX ID admin.
     - Copy the __client secret key__ from Google and paste it into the `Client Secret` field in the VTEX ID admin.
-    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)    
+    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)    
     Then, save the changes.
diff --git a/docs/tutorials/en/adding-a-record-on-a-master-data-form.md b/docs/tutorials/en/adding-a-record-on-a-master-data-form.md
new file mode 100644
index 000000000..033d6bb6f
--- /dev/null
+++ b/docs/tutorials/en/adding-a-record-on-a-master-data-form.md
@@ -0,0 +1,56 @@
+---
+title: 'Adding a record on a Master Data form'
+id: tutorials_6264
+status: PUBLISHED
+createdAt: 2017-04-27T21:48:37.277Z
+updatedAt: 2024-07-17T21:25:51.382Z
+publishedAt: 2024-07-17T21:25:51.382Z
+firstPublishedAt: 2017-04-27T23:11:18.994Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: adding-a-record-on-a-master-data-form
+locale: en
+legacySlug: how-to-include-a-registration-on-a-master-data-form
+subcategory: 42hDtnYXHw5ExG6l19RP1l
+---
+
+To add a record in a Master Data form, you need to access Master Data and choose the application you want to view. To do this, follow the instructions in the sections below.
+
+Fields can be configured as editable or not directly in the data entity. Learn more in [Data entity](https://help.vtex.com/en/tutorial/entidade-de-dados--tutorials_1265).
+
+<div class="alert alert-warning">
+This article covers Master Data v1. It is important to evaluate which version of Master Data meets your needs or is used in your operation. Learn more:
+<ul>
+<li>
+<a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+Master Data version features
+</a>
+</li>
+<li>
+<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+Master Data v2
+</a>
+</li>
+</ul>
+</div>
+
+## Adding a record
+
+To save a new record, such as a new customer profile, follow the steps below:
+
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. In the application, find the form row to which you want to add a record and click the add icon <i class="fas fa-plus-circle"></i>.
+3. Complete the form fields.
+4. Click `Save`.
+
+## Editing a record
+
+To edit an existing record, such as the information of a customer in your store, follow the steps below:
+
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. In the application, find the form row with the record you want to edit and click the menu icon <i class="fas fa-bars"></i>.
+3. You can search for the record by any field defined in the data entity as searchable.
+4. Click the edit icon <i class="fas fa-edit"></i> on the record row you want to edit.
+5. Make the desired changes.
+6. Click `Save`.
diff --git a/docs/tutorials/en/adding-an-attachment.md b/docs/tutorials/en/adding-an-attachment.md
index f105f54f1..946485328 100644
--- a/docs/tutorials/en/adding-an-attachment.md
+++ b/docs/tutorials/en/adding-an-attachment.md
@@ -3,15 +3,15 @@ title: 'Adding an attachment'
 id: 7zHMUpuoQE4cAskqEUWScU
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:42.901Z
-updatedAt: 2023-03-29T15:07:58.328Z
-publishedAt: 2023-03-29T15:07:58.328Z
+updatedAt: 2023-11-16T17:23:31.034Z
+publishedAt: 2023-11-16T17:23:31.034Z
 firstPublishedAt: 2019-01-24T22:06:25.639Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
 author: 1malnhMX0vPThsaJaZMYm2
 slug: adding-an-attachment
 locale: en
-legacySlug: adding-an-attachment
+legacySlug: registering-an-attachment
 subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 ---
 
@@ -31,7 +31,7 @@ Attachments can be used to [complement a product with custom information](https:
 After adding the attachment, you need to add the keys and **permitted values** related to it. You can add as many keys as you wish. To add the keys and **permitted values**, follow the steps below.
 
 1. On the **Custom product attributes** page, find the row of the attachment you have created and click `Modify`, as illustrated in the image below.
-  ![anexos.pt](https://images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/0088408090cd1bec84c4826676af8cb8/custom-product-attributes-en.PNG)
+  ![anexos.pt](//images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/0088408090cd1bec84c4826676af8cb8/custom-product-attributes-en.PNG)
 2. Fill in the fields listed below.
     * **Key Name:** name of the custom information. This field is required and must contain only letters, numbers, or periods. For example, if the customizable product is a U.S. soccer jersey, its key names can be `Name` and `Number`.
     * **Maximum Number of Characters:** the maximum number of characters the customer can type to add custom information to the product. For example, in this field you could set the character limit for the name that will be printed on a shirt. This field is required. If you do not fill it in, the attachment will not be displayed to your customer as a selection option in the cart.
diff --git a/docs/tutorials/en/adding-bin-information.md b/docs/tutorials/en/adding-bin-information.md
new file mode 100644
index 000000000..20b23411b
--- /dev/null
+++ b/docs/tutorials/en/adding-bin-information.md
@@ -0,0 +1,42 @@
+---
+title: 'Adding BIN information'
+id: 7xvo4JJ53WM7aLzufdC4au
+status: PUBLISHED
+createdAt: 2024-05-02T19:11:00.734Z
+updatedAt: 2024-05-03T13:40:32.363Z
+publishedAt: 2024-05-03T13:40:32.363Z
+firstPublishedAt: 2024-05-02T19:44:35.388Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: adding-bin-information
+locale: en
+legacySlug: adding-bin-information
+subcategory: 2Xay1NOZKE2CSqKMwckOm8
+---
+
+The Bank Identification Number (BIN) consists of the first six or eight digits of a credit or debit card and identifies the card's issuing institution.
+
+![BIN_image_digits_EN_2](//images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/1e44ba9fd9c075edcc4042470c40af1a/BIN_image_digits_EN_2.png)
+
+When a banking institution wants to create new card profiles or issue new cards for an existing model, new BINs are required. This also applies when a card [brand](https://help.vtex.com/en/tutorial/what-is-a-credit-card-brand--4bNba5QYuIwKEmac88KwyI) is acquired by another.
+
+In such cases, VTEX must be notified to ensure that the new cards are correctly validated during the payment process for purchases made on the platform.
+
+## Submitting an add BIN request
+
+To add a new BIN or update an existing one on VTEX, please open a ticket with [VTEX Support](https://help.vtex.com/en/support).
+
+In the ticket, you should attach a spreadsheet with the following information:
+
+- __code__: New BIN to be added or existing BIN to be updated.
+- __cardBrand__: Card brand of the BIN.
+- __cardType__: Type of card (credit or debit).
+- __country__: Country where the card will be used.
+- __bank__: Issuing bank of the card.
+- __cvvSize__: Number of characters in the CVV (Card Verification Value).
+- __cardLevel__: Card category (e.g., Gold, Platinum, Black, among others).
+
+Template example:
+
+![Bin_spreadsheet](//images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/3c5b160ad784b2fdf80b57f99a375050/Bin_spreadsheet.PNG)
diff --git a/docs/tutorials/en/adding-collections-cms.md b/docs/tutorials/en/adding-collections-cms.md
index 3d044614a..cdbf2bbf1 100644
--- a/docs/tutorials/en/adding-collections-cms.md
+++ b/docs/tutorials/en/adding-collections-cms.md
@@ -33,7 +33,7 @@ When the number of created collections surpasses twenty, those exceeding that nu
 
 Choosing the products that will make up a collection is done by clicking on __New Group__ in the desired collection, creating a __group__.
 
-![new-group-collection en](https://images.ctfassets.net/alneenqid6w5/7tJUzscKOqsDSLv64f71KJ/49434a9c33f677cf4632f2145d4064b4/new-group-collection_en.png)
+![new-group-collection en](//images.ctfassets.net/alneenqid6w5/7tJUzscKOqsDSLv64f71KJ/49434a9c33f677cf4632f2145d4064b4/new-group-collection_en.png)
 
 Before choosing which products to add to a group, you will need to give it a name and specify which type the created group falls under.
 
@@ -75,17 +75,17 @@ For example: When selecting a category `A` and a brand `B`, only products pertai
 
 To add the products of a specific department to a group, select the desired department and click on __Save Group__, as shown in the image below.
 
-![seleção-departamento EN](https://images.ctfassets.net/alneenqid6w5/2CWCcsikNQciGdeJrN4ffV/3419aae384eec69319a0fd199decc16a/sele____o-departamento_EN.png)
+![seleção-departamento EN](//images.ctfassets.net/alneenqid6w5/2CWCcsikNQciGdeJrN4ffV/3419aae384eec69319a0fd199decc16a/sele____o-departamento_EN.png)
 
 The same applies for products of a specific Category or Subcategory.
 
-![seleção-categoria-subcategoria EN](https://images.ctfassets.net/alneenqid6w5/2Z3mfoWo65F6fJM22sZEqi/c5dc354968d5bb690fadff1da9316e96/sele____o-categoria-subcategoria_EN.png)
+![seleção-categoria-subcategoria EN](//images.ctfassets.net/alneenqid6w5/2Z3mfoWo65F6fJM22sZEqi/c5dc354968d5bb690fadff1da9316e96/sele____o-categoria-subcategoria_EN.png)
 
 ## Product by Brand
 
 To create a group containing products from one or more brands, select the desired brand from the corresponding list.
 
-![seleção-marca-coleção en](https://images.ctfassets.net/alneenqid6w5/1wjrZ0Oa0n2ZwdB8QXAWAS/8386ab974309a4ffe652011ab1a312f4/sele____o-marca-cole____o_en.png)
+![seleção-marca-coleção en](//images.ctfassets.net/alneenqid6w5/1wjrZ0Oa0n2ZwdB8QXAWAS/8386ab974309a4ffe652011ab1a312f4/sele____o-marca-cole____o_en.png)
 
 Brands are displayed in alphabetical order. When clicking on the first letter corresponding to the desired brand, the list expands and displays the existing brands.
 
@@ -95,7 +95,7 @@ Brands are displayed in alphabetical order. When clicking on the first letter co
 
 When adding a SKU to a group, the product to which it is linked is also added. If the product is linked to more than one SKU, adding one SKU would also add all other SKUs to the group.
 
-![selecao-sku-manual en & es](https://images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
+![selecao-sku-manual en & es](//images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
 
 In the __find SKUs__ field, you can type in as many SKU IDs as needed, separating each one by a comma. 
 
@@ -117,21 +117,21 @@ Get the file template for adding SKUs to or removing them from a collection <a h
 
 You can __Bulk insert SKUs__ by importing an `.xls` format spreadsheet to list SKUs that will be part of a group.
 
-![selecao-sku-planilha-insert en & es](https://images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
+![selecao-sku-planilha-insert en & es](//images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
 
 In the imported spreadsheet, all SKU IDs must be listed in the first column, with a header, as shown in the example below:
 
-![exemplo-planilha-seleção-sku-coleção](https://images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png) 
+![exemplo-planilha-seleção-sku-coleção](//images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png) 
 
 After selecting the desired spreadsheet, click on the __Import SKUs__ option to sent the information.
 
-![Import SKUs](https://images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
+![Import SKUs](//images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
 
 #### Bulk remove
 
 To avoid having to remove SKUs one at a time, you can use the import function of a spreadsheet to bulk remove them.
 
-![exclusao-skus-manualmente-planilha-coleção-cms en & es](https://images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
+![exclusao-skus-manualmente-planilha-coleção-cms en & es](//images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
 
 In this specific case, the SKUs listed in the imported spreadsheet will be excluded from the group. Do this by clicking on __remove SKUs__ after the file has been loaded. 
 
@@ -147,7 +147,7 @@ In the <strong>Other options</strong> section, the <strong>Pre-sales</strong> an
 
 Note that you can only select one of the two options. Should you want both add-ons, create two groups and configure each one with the respective option.
 
-![other-options-cms-coleções EN](https://images.ctfassets.net/alneenqid6w5/4kHHhPDUSBSdjkYaApxayp/ef552cf4e72bb119f0b080605927a2b9/other-options-cms-cole____es_EN.png)
+![other-options-cms-coleções EN](//images.ctfassets.net/alneenqid6w5/4kHHhPDUSBSdjkYaApxayp/ef552cf4e72bb119f0b080605927a2b9/other-options-cms-cole____es_EN.png)
 
 ### Pre-sales
 
diff --git a/docs/tutorials/en/adding-sku-specifications-or-fields.md b/docs/tutorials/en/adding-sku-specifications-or-fields.md
index e8dbdd6d7..4c8d2d1e1 100644
--- a/docs/tutorials/en/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/en/adding-sku-specifications-or-fields.md
@@ -3,8 +3,8 @@ title: 'Adding SKU specifications or fields'
 id: tutorials_119
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:08.662Z
-updatedAt: 2023-03-29T17:31:34.699Z
-publishedAt: 2023-03-29T17:31:34.699Z
+updatedAt: 2023-11-30T12:05:25.945Z
+publishedAt: 2023-11-30T12:05:25.945Z
 firstPublishedAt: 2017-04-27T23:00:44.181Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: creating-sku-fields
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-An SKU specification is a field in the SKU form where you can insert specific characteristics for every product variation.
+An SKU specification is a mandatory field in the SKU form where you can insert specific characteristics for every product variation.
 
 At VTEX, a specification is always included in a [specification group](https://help.vtex.com/en/tutorial/creating-category-groups--tutorials_246), associated with a [category](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf). Therefore, to create an SKU specification (field), you must first create at least one category and one specification group.
 
@@ -43,7 +43,7 @@ Before creating any specifications, it's important to understand that they follo
 
 Example: consider a **Men's shirt** product. In __Catalog > Products and SKUs > SKU > Specifications__, as illustrated in the page below, we can see that the specification group called **Characteristics** is associated with the Shirt category. This group includes a field named **Color** and a field named **Size**.
 
-![heranca-especificacoes-sku-en](https://images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/1dd8ca5d13bf8f288cac031795bf85ea/sku-specifications-inheritance-en.PNG)
+![heranca-especificacoes-sku-en](//images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/1dd8ca5d13bf8f288cac031795bf85ea/sku-specifications-inheritance-en.PNG)
 
 Since this is an SKU specification, the information selected on that page will apply only to the **Men's Shirt** product variations. All SKUs added to the **Men's Shirt** category and all product SKUs of the same category must also have these specifications filled out.
 
@@ -85,7 +85,7 @@ To create an SKU field, follow the instructions below:
     * **Active**: Inserts or removes this field when adding an SKU.
 7. Click `Save`.
 
-![sku-spec-1](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/3c508d340371923bcc233d8737197b66/en-sku-spec-2.gif)
+![sku-spec-1](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/3c508d340371923bcc233d8737197b66/en-sku-spec-2.gif)
 
 #### SKU Field types
 
@@ -130,13 +130,13 @@ The **Values** of the SKU fields will vary according to the selected field type:
 
     Insert one value per row and press `Enter` after each value, as illustrated in the image below.
 
-    ![valores-campo-sku-en](https://images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/f7aa05de7fb5964660b912f2aa2f0b24/valores-especificacoes-sku-en.PNG)
+    ![valores-campo-sku-en](//images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/f7aa05de7fb5964660b912f2aa2f0b24/valores-especificacoes-sku-en.PNG)
 
 8. Click `Save`.
 
     The added values will be displayed in the [SKU registration interface](#sku-registration).
 
-![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/a6da423b96ac0edb46837b590e7a030f/en-sku-spec-2.gif)
+![sku-spec-2](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/a6da423b96ac0edb46837b590e7a030f/en-sku-spec-2.gif)
 
 <div class = "alert alert-info">
   <p>If you are adding values for the first time in a field, you must return to the form of that specific field and check the <strong>Active</strong> option.</p>
@@ -180,7 +180,7 @@ To fill in the specifications for each SKU individually, follow the instructions
 
 8. Click `Save`.
 
-![sku-spec-3](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/caa7782074d6311b0ac3b7182258464d/en-sku-spec-3.gif)
+![sku-spec-3](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/caa7782074d6311b0ac3b7182258464d/en-sku-spec-3.gif)
 
 #### Spreadsheet
 
@@ -203,7 +203,7 @@ To fill in SKU specifications in bulk using a spreadsheet, first you must export
 9. Click **Select** to select the file with the filled out spreadsheet from your computer.
 10. Click `Import`.
 
-![sku-spec-4](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/9fb7eb05a187b6cd90ad963067ca1223/en-sku-spec-4.gif)
+![sku-spec-4](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/9fb7eb05a187b6cd90ad963067ca1223/en-sku-spec-4.gif)
 
 ## Learn more
 - [Adding product specifications or fields](https://help.vtex.com/en/tutorial/adding-specifications-or-product-fields--tutorials_106)
diff --git a/docs/tutorials/en/adding-specifications-or-product-fields.md b/docs/tutorials/en/adding-specifications-or-product-fields.md
index bc27f7264..3419c3771 100644
--- a/docs/tutorials/en/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/en/adding-specifications-or-product-fields.md
@@ -43,7 +43,7 @@ Before creating any specifications, it's important to understand that they follo
 
 Consider the **TV** product for example. In __Catalog > All products > Edit > Specifications__, as illustrated in the page below, we can see that the specification group called **Characteristics** is associated with the TV's category. This group includes a field named **Inches** and a field named **Age group**, which are mandatory.
 
-![specifications-en](https://images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/abd1962c5063aa7f66d4ca8c743216c9/specifications-en.PNG)
+![specifications-en](//images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/abd1962c5063aa7f66d4ca8c743216c9/specifications-en.PNG)
 
 Since this is a product specification, the information selected on that page will apply to all **TV** product variations. All products added to the TV's category must have these specifications filled out, since they are required fields.
 
@@ -80,7 +80,7 @@ To create a product field, follow the steps below:
     * **Active**: Inserts or removes this field when adding the product (**Specifications** tab).
 7. Click `Save`. 
 
-![product-spec-1](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/d63d7b135d47717c567f77769ded7998/EN_ProdutoGif_1_Alterado.gif)
+![product-spec-1](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/d63d7b135d47717c567f77769ded7998/EN_ProdutoGif_1_Alterado.gif)
 
 #### Product field types
 
@@ -146,7 +146,7 @@ For the **Combo**, **Radio** and **CheckBox** field types, you must add preset v
 
     The created values will be displayed in the Product **Specifications** tab.
 
-![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/c8c76e2f734ee038be20a6c273fdf987/EN_ProdutoGif_2_Alterado.gif)
+![product-spec-2](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/c8c76e2f734ee038be20a6c273fdf987/EN_ProdutoGif_2_Alterado.gif)
 
 <div class = "alert alert-info">
   <p>If you are adding values for the first time in a field, you must return to the form of that specific field and check the <strong>Active</strong> option.</p>
@@ -188,7 +188,7 @@ To fill in the specifications for each product individually, follow the instruct
 
 6. Click `Save`.
 
-![product-spec-3](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/80503bcee1eddc3c30cc9b6eee05a4f5/EN_ProdutoGif_3_Alterado.gif)
+![product-spec-3](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/80503bcee1eddc3c30cc9b6eee05a4f5/EN_ProdutoGif_3_Alterado.gif)
 
 #### Spreadsheet
 
@@ -211,7 +211,7 @@ To fill in product specifications in bulk by spreadsheet, you need to export the
 9. Click **Select** to select the file with the completed spreadsheet on your computer.
 10. Click `Import`.
 
-![product-spec-4](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/0bc27b7b0d9e41dc649b057c20aaf90f/EN_ProdutoGif_4_Alterado.gif)
+![product-spec-4](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/0bc27b7b0d9e41dc649b057c20aaf90f/EN_ProdutoGif_4_Alterado.gif)
 
 ## Learn more
 - [Adding SKU specifications or fields](https://help.vtex.com/en/tutorial/adding-sku-specifications-or-fields--tutorials_119)
diff --git a/docs/tutorials/en/additional-shipping-costs.md b/docs/tutorials/en/additional-shipping-costs.md
index 451d5e381..59ce37a98 100644
--- a/docs/tutorials/en/additional-shipping-costs.md
+++ b/docs/tutorials/en/additional-shipping-costs.md
@@ -17,7 +17,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Additional shipping costs are extra charges added to the shipping rate as established in [shipping policies](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140). So, when configuring costs for shipping items, you can set a fixed rate and include additional charges. Together, these values will compose the [shipping rate](https://help.vtex.com/en/tutorial/gerenciar-valores-de-frete--tutorials_141). 
 
-![Tarifa envio EN](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
+![Tarifa envio EN](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
 
 You can configure the following additional costs:
 
@@ -26,7 +26,7 @@ You can configure the following additional costs:
 * [Insurance charge](https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV#additional-insurance-charge);
 * [Extra shipping charge](https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV#additional-shipping-charge).
 
-![adicionais frete EN](https://images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/eee27446335556a96fece61f8d2f0e8f/adicionais_frete_EN.svg)
+![adicionais frete EN](//images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/eee27446335556a96fece61f8d2f0e8f/adicionais_frete_EN.svg)
 
 <div class="alert alert-danger">
 Note that all of them can be simultaneously considered for composing the shipping rate. The final calculation of the <a href="https://help.vtex.com/en/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">shipping rate</a> is the sum of all additional charges plus the flat rate. 
@@ -69,7 +69,7 @@ There are two ways to configure the weight-based additional charge:
 
 To learn more, access their tutorials.
 
-![faixa-peso EN](https://images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/df911253923073437cf3708e1d2b753b/faixa-peso_EN.png)
+![faixa-peso EN](//images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/df911253923073437cf3708e1d2b753b/faixa-peso_EN.png)
 
 ## Price-based additional charge
 
@@ -163,4 +163,4 @@ To configure the additional shipping charge, go to the left-side menu in the VTE
     If you want to include a 10% fee, fill in the field with 10. Use a period to indicate the decimal place, such as 1.67.
 3. Click on `Save`.
 
-![adicional configuracoes EN](https://images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/2a2708eaac81731568792959f167bdd9/adicional_configuracoes_EN.png)
+![adicional configuracoes EN](//images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/2a2708eaac81731568792959f167bdd9/adicional_configuracoes_EN.png)
diff --git a/docs/tutorials/en/admin-redirect-search-returns-no-results.md b/docs/tutorials/en/admin-redirect-search-returns-no-results.md
new file mode 100644
index 000000000..73fce401d
--- /dev/null
+++ b/docs/tutorials/en/admin-redirect-search-returns-no-results.md
@@ -0,0 +1,111 @@
+---
+title: 'Admin redirect search returns no results'
+id: 2u5cJhUSVM6bbEAFkgUww7
+status: PUBLISHED
+createdAt: 2024-07-24T13:41:02.016Z
+updatedAt: 2024-07-24T14:33:50.131Z
+publishedAt: 2024-07-24T14:33:50.131Z
+firstPublishedAt: 2024-07-24T14:13:11.586Z
+contentType: tutorial
+productTeam: Others
+author: 4ubliktPJIsvyl1hq91RdK
+slug: admin-redirect-search-returns-no-results
+locale: en
+legacySlug: admin-redirect-search-returns-no-results
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Keywords:** redirect
+
+When the number of redirects is too high, the Redirects page in the Admin can't process the search. This results in no returned results when the search is run. For more details on the Redirects page, see [Managing URL redirects by binding](https://help.vtex.com/en/tutorial/managing-redirects-per-binding--67GAK2TCQgjvmtPXxAqREb).
+
+## Solution
+
+Follow these steps to get the redirects:
+
+1. Access **GraphQL IDE** through the page `{account_name}.myvtex.com/admin/graphql-ide`. Replace `{account_name}` with the name of your VTEX account.
+2. Select the `vtex.rewriter@x` app, where `x` is the app version. For example: `vtex.rewriter@1.62.0`.
+3. Use the following GraphQL query to list the store's redirects:
+
+  ```
+  query {
+    redirect{
+      listRedirects{
+        routes{
+          from
+          to
+          endDate
+          type
+          binding
+        }
+      }
+    }
+  }
+  ```
+
+  The expected result will be displayed in the following format:
+
+  ```json
+  {
+    "data": {
+      "redirect": {
+        "listRedirects": {
+          "routes": [
+            {
+              "from": "/hello",
+              "to": "hola",
+              "endDate": null,
+              "type": "PERMANENT",
+              "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+            },
+            {
+              "from": "/v/*",
+              "to": "https://masrefacciones.backend.verbolia.com",
+              "endDate": null,
+              "type": "PERMANENT",
+              "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+            }
+          ]
+        }
+      }
+    }
+  }
+  ```
+
+4. Alternatively, if the redirect path you want to find is known, use the following GraphQL query replacing `/hello` with the path of the desired redirect:
+
+  ```
+  query {
+    redirect{
+      get(path:"/hello"){
+        from
+        to
+        endDate
+        type
+        binding
+      }
+    }
+  }
+  ```
+
+  The expected result will be displayed in the following format:
+
+  ```json
+  {
+    "data": {
+      "redirect": {
+        "get": {
+          "from": "/hello",
+          "to": "hola",
+          "endDate": null,
+          "type": "PERMANENT",
+          "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+        }
+      }
+    }
+  }
+  ```
+
+If the current redirects are not what's expected, the Rewriter app allows you to perform other operations with redirects, such as deleting existing ones and creating new ones. For details on these operations, see the [Rewriter GraphQL API](https://developers.vtex.com/docs/apps/vtex.rewriter/rewriter-graphql-api) guide.
+
+You can also export and import redirects with `.csv files` using the Redirects page or the VTEX IO CLI `redirects` [plugin](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-plugins). For details on importing and exporting redirects, see [Managing URL redirects by binding](https://help.vtex.com/en/tutorial/managing-redirects-per-binding--67GAK2TCQgjvmtPXxAqREb#importing-and-exporting-redirects) and the [VTEX IO CLI command reference](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-command-reference#redirects-delete).
diff --git a/docs/tutorials/en/admin-v4-getting-started.md b/docs/tutorials/en/admin-v4-getting-started.md
index aa365a462..b11d3090d 100644
--- a/docs/tutorials/en/admin-v4-getting-started.md
+++ b/docs/tutorials/en/admin-v4-getting-started.md
@@ -24,22 +24,22 @@ To achieve this, we are redesigning multiple parts of the experience and making
 ## Improved navigation 
 Everything you need to manage your VTEX store is still available in Admin v4, only now with a more straightforward organization. Our left and top navigation menu were rebuilt from scratch, grouping similar categories in a clearer way to reduce distractions and help your team find what they need faster. It is also possible to use the search bar to find specific sections on the menu.
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Information Center
 This is where we group all useful links from our VTEX ecosystem, to help you get the best out of our VTEX platform. By clicking on the `?` button on the top bar, you can access our Help Center, blog, Developer Portal, Platform Status and support pages.    
 
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Store Settings
 For this new experience, we have grouped all settings, from all sections under a specific tab: Store Settings. Through this improvement, you can easily access all settings that affect every service in your account.
 
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Profile Settings
 Your profile avatar, on the upper right corner now hosts all the settings related to your user and account. Through the avatar you can access user settings, account settings, billing information, change your Admin’s locale,  switch to the Admin’s previous version and logout of your account and logout. Through this improvement, we separated your profile settings from the configurations that affect your actual store. Now you have more control and visibility over actions that affect your business, and those that affect your profile. 
 
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 ## Refreshed home page
 
@@ -47,7 +47,7 @@ Our admin home page was redesigned to give you a high level overview of your sto
 
 As soon as you log in to Admin v4, you will see useful metrics and charts to monitor your store's performance, such as revenue and number of orders, sales funnel and conversion rates, and your top 10 highest grossing products. Check out all components on the new Dashboard, and learn how they work, looking through the list below.
 
-![Dashboard v4](https://images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
+![Dashboard v4](//images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
 
 - **Orders:**  number of orders placed.  All data about orders and revenue comes from VTEX’s Order Management System.  
 - **Sessions:** Number of visits to store  
diff --git a/docs/tutorials/en/ads-from-vtex-sales-app.md b/docs/tutorials/en/ads-from-vtex-sales-app.md
index c36711503..d69f2ddd0 100644
--- a/docs/tutorials/en/ads-from-vtex-sales-app.md
+++ b/docs/tutorials/en/ads-from-vtex-sales-app.md
@@ -1,10 +1,10 @@
 ---
-title: 'Ads from VTEX Sales App'
+title: 'VTEX Sales App Offers'
 id: 3UtOFwbwD4muz3p72RBPmC
 status: PUBLISHED
 createdAt: 2023-05-25T17:16:06.902Z
-updatedAt: 2023-05-30T15:53:49.413Z
-publishedAt: 2023-05-30T15:53:49.413Z
+updatedAt: 2024-06-26T18:31:53.389Z
+publishedAt: 2024-06-26T18:31:53.389Z
 firstPublishedAt: 2023-05-26T22:11:51.769Z
 contentType: tutorial
 productTeam: Shopping
@@ -15,90 +15,94 @@ legacySlug: ads-from-vtex-sales-app
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-The new ad area in the VTEX Sales App features two main types of ads: specific products or search results. This flexibility allows merchants to adapt their marketing strategies according to their specific needs and goals, promoting individual products or groups of related products.
+The new offer area in VTEX Sales App features two main types of offers: specific products or search results. This flexibility allows merchants to adapt their marketing strategies based on their specific needs and goals, promoting individual products or groups of related products.
 
-In this document, we will provide detailed instructions on how to install, configure, and use the new ad area. Follow the steps below to set up this tool and boost your online sales.
+To customize a store's window display, merchants can add an `Offers by store` page by specifying the store ID in the [Master Data](https://developers.vtex.com/docs/guides/master-data-introduction) to which the offer will be linked, allowing them to create personalized offers for each store.
+
+In this document, we will provide detailed instructions on how to install, configure, and use the new offer area. Follow the steps below to set up this tool and boost your online sales.
 
 * [Install VTEX dependencies](#install-vtex-dependencies)
 * [Configure the Headless CMS app](#configure-the-headless-cms-app)
-* [Create an ad page](#create-an-ad-page)
-* [Activate the ad menu in the VTEX Sales App](#activate-the-ad-menu-in-the-vtex-sales-app)
+* [Create an offer page](#create-an-offer-page)
+* [Activate the offer menu in VTEX Sales App](#activate-the-offer-menu-in-VTEX-Sales-App)
 * [Access ads in the VTEX Sales App](#access-ads–in-the-vtex-sales-app)
 
-## Install VTEX dependencies
+## Installing VTEX dependencies
 
 Before installing the dependencies, you must have VTEX IO CLI installed. With VTEX IO CLI installed, execute the following commands in your computer's command prompt to install the necessary dependencies:
 
-```
-vtex login {account}
-
-vtex install vtex.admin-cms@1.x vtex.admin-cms-graphql@0.x 
-vtex.admin-cms-graphql-rc@1.x vtex.admin-releases@0.x 
-vtex.cms-builder-sf-jamstack@1.x
-```
-
-## Configure the Headless CMS app
-
-1. In the VTEX Admin, go to **Applications > My Apps**, or type **My Apps** in the search bar at the top of the page.
-2. Click on the **CMS (alpha)** item's `Settings`.
-3. Click on `Add More`.
-4. In the **Project ID** field, type `instore`.
+1.
+    ```
+    vtex login {account}  
+    ```
+2.
+    ```
+    vtex install vtex.admin-cms@1.x vtex.admin-cms-graphql@0.x vtex.admin-cms-graphql-rc@1.x vtex.admin-releases@0.x vtex.cms-builder-sf-jamstack@1.x
+    ```
+## Configuring the Headless CMS app
+To create an offer page for VTEX Sales App, follow the steps below:
+1. In the VTEX Admin, go to **Apps > App Management**, or type **App Management** in the search bar at the top of the page.
+2. Click the **CMS (alpha)** item's `Settings`.
+3. Click `Add More`.
+4. In the **Project ID** field, type `assisted-sales-app`.
 5. In the **Sections URL** field, type `https://instore--instore.vtex.app/assisted-sales/cms/sections.json`.
 6. In the **Content types URL** field, type `https://instore--instore.vtex.app/assisted-sales/cms/content-types.json`.
-7. In the **Translation keys URL** field, type `https://instore--instore.vtex.app/assisted-sales/cms/translation-keys.json.
-8. Click on `Save`.
-
-## Create an ad page
-
-To create an ad page for the VTEX Sales App, follow the steps below:
-
-1. Access the VTEX Admin URL: `https://{main_account}.myvtex.com/admin/new-cms/instore`
-2. Click on **Create New** and select **Ads**.
-3. Click on **Untitled** to edit and include the desired name. We recommend the name **Ads**.
-4. In the **Sections** tab, click on the `+` button to add a new section. Each section is a collection of products or search terms. Each section will be displayed as a carousel showcase. You can reorder the showcases by clicking on the `Move down` or `Move up` buttons.
-5. Select an ad type, either products or search results.
-  - **Product Showcase:** It will display each product and SKU (optional) that you specify. Add the following information:
-    - **Showcase title:** name of the showcase that will be displayed on the page.
-    - **Product ID:** identifier number of the product you want to display. Mandatory field.
-    - **Product SKU ID:** identifier number of the product's SKU you want to display. Optional field.
-![vitrine-produto-en](https://images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/055391c146dbfe153d0161eb1f9af701/image.png)
-After filling in the fields, the product image will be displayed with the "starting at" price. If you include the SKU, the price and promotion of the indicated SKU will be displayed. You can add more products by clicking on + NEW PRODUCT. You can add up to 10 products in each showcase.
-The result of the product showcase will be displayed as shown in the image below.
-![vitrine-produto-2-en](https://images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/f288b81bbd6f3f9e788afdccead5286e/image.png)
-  - **Search Results Showcase:** it will display products from a search result that you define. Add the following information:
-Showcase title: The name of the showcase that will be displayed on the page.
+7. Click `Save`.
+
+## Creating an offer page
+
+To create an offer page for VTEX Sales App, follow the steps below:
+
+1. Access the VTEX Admin URL: `https://{main_account}.myvtex.com/admin/new-cms/assisted-sales-app`
+2. Click **Create New** and select **Ads**.
+3. Click **Untitled** to edit and include the desired name. We recommend using the name **Offers**.
+4. In the **Sections** tab, click the + button to add a new section. Each section is a collection of products or search terms. Each section will be displayed as a carousel. You can reorder custom displays by clicking the Move down or Move up buttons.
+5. Select an offer type, either products or search results.
+  - **Product custom display:** It will display each product and SKU (optional) that you specify. Add the following information: - **Custom display title:** Name of the custom display that will be displayed on the page. - **Product ID:** Identifier number of the product you want to display. Required field. - **Product SKU ID:** Iidentifier number of the product's SKU you want to display. Optional field.
+![vitrine-produto-en](//images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/055391c146dbfe153d0161eb1f9af701/image.png)
+After completing the fields, the product image will be displayed with the "starting at" price. If you include the SKU, the price and promotion of the indicated SKU will be displayed. You can add more products by clicking + NEW PRODUCT. You can add up to 10 products in each custom display. The result of the product custom display will be displayed as shown in the image below.
+![vitrine-produto-2-en](//images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/f288b81bbd6f3f9e788afdccead5286e/image.png)
+  - **Search results custom display:** It will display products from a search result that you define. Add the following information: 
+Custom display title: Name of the custom display that will be displayed on the page.
     - **Search image:** image that will represent the selection of products in the showcase.
-    - **Search name:** name of the search that will be displayed on the page.
-    - **Search term:** search term that will be used as a reference for the products.
-![vitrine-busca-en](https://images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/79a8cc3b08dd79d76d402456e47a62ac/image.png)
-When the seller clicks on the search term, they will be directed to the search result determined in the Search term. You can also include up to 10 searches in each showcase. See the result in the image below:
-![vitrine-busca-2-en](https://images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/58073fd76945673090d787622ebcc09a/image.png)
+    - **Search name:** Name of the search that will be displayed on the page.
+    - **Search term:** Search term: Search term that will be used as a reference for the products.
+![vitrine-busca-en](//images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/79a8cc3b08dd79d76d402456e47a62ac/image.png)
+When the seller clicks the search term, they will be directed to the search result determined in the Search term. You can also include up to 10 searches in each custom display. See the result in the image below:
+![vitrine-busca-2-en](//images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/58073fd76945673090d787622ebcc09a/image.png)
 <ol start="6">
-  <li>After creating the sections, click on <code>Save</code>, then click on <code>Publish</code> and <code>Publish Now</code> to finalize.</li>
+  <li>After creating the sections, click <code>Save</code>, then click <code>Publish</code> and <code>Publish Now</code> to finalize.</li>
 </ol> 
 
-The publication of the showcase will enter the indexing queue and will be published within a few seconds.
+The publication of the custom display will enter the indexing queue and will be published within a few seconds.
 
-## Activate the ad menu in the VTEX Sales App
+- **Collection custom display:** It will display products from a specified collection. Please add the following details:
+    - **Custom display title:** Name of the custom display as it will appear on the page.
+    - **Collection ID:** The collection identifier number that will be displayed on the page.
 
-Access the technical settings of the VTEX Sales App at:
+![Vitrine - EN](//images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/c3f21920a6ac94d53a3097b8a7b3ad72/Vitrine_-_EN.png)
+
+## Activate the offer menu in VTEX Sales App
+
+Access the technical settings of VTEX Sales App at: 
 ```https://{main_account}.myvtex.com/admin/portal/#/sites```
 
-1. Click on the <i class="fas fa-cog"></i> button.
+1. Click the <i class="fas fa-cog"></i> button.
 2. Select the **Code** tab.
 3. Select the `checkout-instore-custom-js` file in the side tab.
-![checkout-instore-custom-js-file](https://images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/8f4cdc9e643abd06f8b3ef4ecc906040/image.png)
-5. In the `window.INSTORE_CONFIG` object, add the flag `enableExplore: true`.
-![window.INSTORE_CONFIG](https://images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/e2984ba814f55a81a0b4263ff9d1a694/image.png)
-6. Click on <i class="fas fa-save"></i> `Save`.
-7. Optionally, you can set the ad page as the seller's homepage. To do this, add the flag `initialPage: advertisements` to the `window.INSTORE_CONFIG` object.
-![initialPage : advertisements](https://images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/57c885204ca51226610e97e88f2e85e4/image.png)
+![checkout-instore-custom-js-file](//images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/8f4cdc9e643abd06f8b3ef4ecc906040/image.png)
+5. In the `window.INSTORE_CONFIG` object, add the flag `enableExplore: true,`.
+![window.INSTORE_CONFIG](//images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/e2984ba814f55a81a0b4263ff9d1a694/image.png)
+6. Click <i class="fas fa-save"></i> `Save`.
+7. Optionally, you can set the offer page as the seller's homepage. To do this, add the flag `initialPage: 'advertisements',` to the `window.INSTORE_CONFIG` object.
+![initialPage : advertisements](//images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/57c885204ca51226610e97e88f2e85e4/image.png)
+
+## Accessing offers in VTEX Sales App
 
-## Access ads in the VTEX Sales App
+In VTEX Sales App, the seller will can access the offer page in two different ways:
 
-In the VTEX Sales App, the seller will have the ability to access the ad page in two different ways:
+* **Homepage:** If the store administrator previously set the offer page as the seller's homepage, upon logging into the platform, the seller will be directed straight to the offer page. This configuration ensures that sellers are always up-to-date with relevant offers and promotions as soon as they access the system.
 
-* **Homepage:** If the store administrator previously registered the ad page as the seller's homepage, upon logging into the platform, the seller will be directed straight to the ad page. This configuration ensures that sellers are always up-to-date with relevant ads and promotions as soon as they access the system.
-* **Explore Menu:** If the ad page is not set as the seller's homepage, it can still be easily accessed through the **Explore** menu. To access the ad page, the seller should click on the **Explore** menu. This will directly take the seller to the ad page, where they can view and interact with the available products and promotions.
+* **Explore Menu:** If the offer page is not set as the seller's homepage, it can still be easily accessed through the Explore menu. To access the offer page, the seller should click the Explore menu. This will directly take the seller to the offer page, where they can view and interact with the available products and promotions.
 
-![vitrine-sale-app-en](https://images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/b1924f30b51e02d7c4fa4ca057b162bb/image.png)
+![vitrine-sale-app-en](//images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/b1924f30b51e02d7c4fa4ca057b162bb/image.png)
diff --git a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
new file mode 100644
index 000000000..7b30c5db1
--- /dev/null
+++ b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
@@ -0,0 +1,163 @@
+---
+title: 'Advertising with VTEX Ad Network (Beta)'
+id: 5WoXcJzHc7EQElpPjziqse
+status: PUBLISHED
+createdAt: 2024-04-23T18:57:14.559Z
+updatedAt: 2024-07-30T15:01:46.734Z
+publishedAt: 2024-07-30T15:01:46.734Z
+firstPublishedAt: 2024-04-23T19:16:43.333Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: advertising-with-vtex-ad-network-beta
+locale: en
+legacySlug: advertising-with-vtex-ad-network-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>VTEX Ad Network is in beta, which means that we are working to improve. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
+</div>
+
+[VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) allows you to advertise your products on VTEX stores that have them listed in their catalog.
+
+To start advertising on VTEX Ad Network, you must contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) to request that the __VTEX Ad Network__ app be installed on your VTEX account.
+
+If you're already a **VTEX Ad Network** advertiser, check this article to learn how you can manage and track your campaigns.
+
+- [Creating campaigns](#creating-campaigns)
+- [Editing campaigns](#editing-campaigns)
+- [Pausing campaigns](#pausing-campaigns)
+- [Tracking your campaigns](#tracking-your-campaigns)
+- [Viewing more details by campaign and product](#viewing-more-details-by-campaign-and-product)
+
+## Creating campaigns
+
+Follow the steps below to create a [VTEX Ad Network campaign](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campaigns):
+
+<div class = "alert alert-info">
+VTEX currently offers a single ad format: search results. Learn more about this <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ad-format">ad format</a>.
+</div>
+
+1. On VTEX Admin, go to **Storefront > Ad Network > Campaigns**.
+2. Click `Create campaign`.
+3. In the *Campaign name* section, click the edit button <i class="fas fa-pencil-alt"></i>.
+4. Enter your campaign name and click `Save`.
+5. In the *Products* section, click the edit button <i class="fas fa-pencil-alt"></i>.
+6. Select the products you want to advertise using one of the following options:
+
+   * __Search products by EAN:__ Search for products in your catalog by EAN.
+   * __Upload File:__ Upload a CSV file with a list of EAN codes, as in [this example](//assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/75958f41bc4628e283ab1d8e060a01ab/teste-ads.csv). EANs are mandatory and bids are optional in the file.
+
+7. In the *Budget, bid, and schedule* section, click the edit button <i class="fas fa-pencil-alt"></i>.
+8. Set the bid amount for each product. You can set each value individually.
+
+  <div class="alert alert-info">
+The bid for a product is the cost per click (CPC), i.e., the amount spent when a user clicks an ad. Learn more about <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campaigns">campaigns</a> and how an <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ad-priority">auction</a> works.
+</div>
+
+9. Click `Save`.
+10. Set the campaign's total budget and end date.
+11. Click `Save`.
+12. In the *Ads Coverage* section, click the edit button <i class="fas fa-pencil-alt"></i>.
+13. Select the stores where you want this campaign to be displayed.
+
+   By default, VTEX displays your ads in all stores that joined VTEX Ad Network and sell the products featured in your campaign.
+
+   If you prefer not to display your ads in all stores, select the *Or choose your publishers* option and specify the stores where you want to display the campaign's ads.
+
+15. Click `Save`. 
+16. Click `Publish`.
+
+Within a few minutes, the chosen products will begin to be advertised in highlighted places in VTEX stores.
+
+## Editing campaigns
+
+Once you've created a campaign, you can edit all its details. To do so, follow the steps below:
+
+1. On VTEX Admin, go to **Storefront > Ad Network > Campaigns**.
+2. Click the table row corresponding to the campaign you want to edit.
+3. Click the <i class="fas fa-pencil-alt"></i> icon.
+4. Edit the information you want.
+5. Click the <i class="fa-solid fa-check"></i> icon.
+
+## Pausing campaigns
+
+You can pause campaigns and stop displaying the corresponding ads. If you want to pause one of your campaigns, follow the steps below:
+
+1. On VTEX Admin, go to **Storefront > Ad Network > Campaigns**.
+2. In the row of the campaign you want to pause, click <i class="fas fa-ellipsis-v"></i>.
+3. Click `Pause`.
+
+## Pausing products
+
+You can pause a specific product in your campaign,  which will stop the corresponding ad from being displayed. If you want to pause a product in one of your campaigns, follow the steps below:
+
+1. On VTEX Admin, go to **Storefront > Ad Network > Campaigns**.
+2. Click the row of the campaign containing the product you want to pause.
+3. In the row of the product you want to pause, click <i class="fas fa-ellipsis-v"></i>.
+4. Click `Pause`.
+
+## Tracking your campaigns
+
+On the [VTEX Ad Network](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) app's home screen, you'll also find details about ongoing campaigns.
+
+![vtex_ad_network_create_campaign_EN](//images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/353d1cb7a0d73b40594ec358a5ecbffa/vtex_ad_network_create_campaign.png)
+
+At the top of the page, you'll find aggregated data:
+
+- **Total Budget:** The total budget assigned to your campaigns.
+- **Budget Spent:** Amount spent so far.
+- **Average ROAS:** Average return on advertising spend.
+- **Ad Sales:** Total sales revenue generated from ads.
+
+Below you will find a table with details about each campaign:
+
+- **Duration:** Duration of the campaign so far.
+- **Impressions:** Number of times ads were displayed on the page.
+- **Views:** Number of times ads were viewed. VTEX Ad Network considers it a view when there is an ad impression and, if necessary, the user scrolls down the page to view at least 50% of the ad area for one second.
+- **Clicks:** Number of clicks on ads. VTEX Ad Network discards clicks on the same product if they occur less than a minute apart.
+- **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views. 
+- **Orders:** Number of orders resulting from clicks on ads.
+- **Units Sold:** Number of product units sold from ads in this campaign.
+- **Ad Sales:** Total sales revenue.
+- **ROAS:** Return on advertising spend. 
+- **Budget:** Total budget.
+- **Remaining:** Budget still available at the moment.
+
+<div class = "alert alert-info">
+Learn more about <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#attribution-window">sales attribution to ads</a>.
+</div>
+
+You can filter the table data using the following options:
+
+- **Search campaign:** Filter campaigns by name.
+- **Status:** Select whether you want to see active or inactive campaigns.
+
+### Viewing more details by campaign and product
+
+In the table on the initial screen of the [VTEX Ad Network](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) app, you can click the row of one of your campaigns to see more details.
+
+- **Views/Clicks:** Ad views and clicks.
+- **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views.
+- **Budget Spent:** Amount spent so far.
+- **ROAS:** Return on advertising spend.
+- **Revenue:** Sales revenue generated from ads.
+
+You'll find a table below the aggregated data detailing each product's performance in that campaign:
+
+- **CPC:** Amount spent when a user clicks an ad.
+- **Impressions:** Number of times ads were displayed on the page.
+- **Views:** Number of times ads were viewed. VTEX Ad Network considers it a view when there is an ad impression and, if necessary, the user scrolls down the page to view the ad.
+- **Clicks:** Number of clicks on ads.
+- **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views. 
+- **Orders:** Number of orders resulting from clicks on ads.
+- **Units Sold:** Number of product units sold from ads in this campaign.
+- **Ad Sales:** Total sales revenue.
+- **ROAS:** Return on advertising spend.
+- **Remaining:** Budget still available at the moment.
+
+<div class = "alert alert-info">
+Learn more about <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#attribution-window">sales attribution to ads</a>.
+</div>
+
diff --git a/docs/tutorials/en/affiliates-program-app.md b/docs/tutorials/en/affiliates-program-app.md
index 9db445376..11bdae5da 100644
--- a/docs/tutorials/en/affiliates-program-app.md
+++ b/docs/tutorials/en/affiliates-program-app.md
@@ -40,11 +40,11 @@ The app creates three types of affiliate pages, available to them without any ac
 
 The **affiliate page** is the VTEX store URL that they will share with the customers. The following image shows an example:
 
-![print_affiliates_url_en](https://images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/6d0e53ff26c4f9c7f3d9fbd3cebf4db9/print_affiliates_url_en.png)
+![print_affiliates_url_en](//images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/6d0e53ff26c4f9c7f3d9fbd3cebf4db9/print_affiliates_url_en.png)
 
 The **affiliate profile page** is an interface where the affiliate can track and manage their orders and commissions. The image below shows an example:
 
-![affiliate_profile_page_en](https://images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/9f11c3ffaa7aac74fe70ab6268679b74/print_profile_en.png)
+![affiliate_profile_page_en](//images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/9f11c3ffaa7aac74fe70ab6268679b74/print_profile_en.png)
 
 The **registration page** allows those who are interested in becoming affiliates to fill in their information to apply for VTEX store registration. 
 
@@ -74,7 +74,7 @@ The **Affiliate Management** page allows you to do the following:
 - [View affiliate details](#viewing-affiliate-details)
 - [Edit an affiliate](#editing-an-affiliate)
 
-![affiliates_management_page_en](https://images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6ea891b6bd27373375fb3d808b26d97c/affiliates_management_page_en.png)
+![affiliates_management_page_en](//images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6ea891b6bd27373375fb3d808b26d97c/affiliates_management_page_en.png)
 
 ### Adding an affiliate
 
@@ -121,7 +121,7 @@ The **Order Management** page allows you to do the following:
 - [Export order spreadsheet](#exporting-the-order-list)
 - [View order details](#viewing-order-details)
 
-![orders_management_page_en](https://images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/9f63b76106915d023708574ad68f3d18/orders_management_page_en.jpg)
+![orders_management_page_en](//images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/9f63b76106915d023708574ad68f3d18/orders_management_page_en.jpg)
 
 ### Monitoring data
 
@@ -174,7 +174,7 @@ The **Commission Management** page allows you to do the following:
 - [Import commissions](#importing-commissions)
 - [Download last import](#downloading-the-last-import)
 
-![commissions_ management_page_en](https://images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/73d8406a30e628474923dfb098dc53da/commissions__management_page_en.png)
+![commissions_ management_page_en](//images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/73d8406a30e628474923dfb098dc53da/commissions__management_page_en.png)
 
 ### Searching for commissions
 
diff --git a/docs/tutorials/en/all-orders.md b/docs/tutorials/en/all-orders.md
index 46a6c2dba..a6c1f46b8 100644
--- a/docs/tutorials/en/all-orders.md
+++ b/docs/tutorials/en/all-orders.md
@@ -3,8 +3,8 @@ title: 'All Orders'
 id: 2QTduKHAJMFIZ3BAsi6Pi
 status: PUBLISHED
 createdAt: 2022-04-04T21:50:53.330Z
-updatedAt: 2023-03-23T16:27:45.086Z
-publishedAt: 2023-03-23T16:27:45.086Z
+updatedAt: 2023-12-21T14:05:13.862Z
+publishedAt: 2023-12-21T14:05:13.862Z
 firstPublishedAt: 2022-04-04T22:39:11.450Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: order-listing-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
+<div class = "alert alert-info">
+You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
+</div>
+
 The **All Orders** page allows retailers to track their store's orders and extract information for intelligent business management. To access the page, go to your VTEX Admin menu and click **Orders > All Orders**. On this page, you can:
 
 - Check order and sales metrics.
@@ -24,7 +28,14 @@ The **All Orders** page allows retailers to track their store's orders and extra
 
 The following sections provide more details about each page component and its actions.
 
-![Order Listing EN](https://images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/e39aa9ff8eab7e0a031c2d7464dc2e87/Order_Listing_EN.gif)
+![Order Listing EN](//images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/e39aa9ff8eab7e0a031c2d7464dc2e87/Order_Listing_EN.gif)
+
+Besides searching for orders in **Orders > All Orders**, you can search for orders from any page in the VTEX Admin using the global search bar at the top bar. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
 
 ## Top bar
 
@@ -155,7 +166,7 @@ Learn more about each column.
 
 ## VTEX DO
 
-![VTEX Do overview EN](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
+![VTEX Do overview EN](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
 
 [VTEX DO](https://help.vtex.com/en/tutorial/vtex-do-beta--7KMbRL4OslN8DTX9oiuCiu) manages tasks automatically created by the VTEX Admin that require manual action by the ecommerce team. 
 
diff --git a/docs/tutorials/en/amaro-integration.md b/docs/tutorials/en/amaro-integration.md
new file mode 100644
index 000000000..a9cdcf279
--- /dev/null
+++ b/docs/tutorials/en/amaro-integration.md
@@ -0,0 +1,19 @@
+---
+title: 'AMARO Integration'
+id: 7615C3U8EHbxbVw82D9pH8
+status: PUBLISHED
+createdAt: 2023-09-20T21:43:42.533Z
+updatedAt: 2024-01-05T19:46:36.030Z
+publishedAt: 2024-01-05T19:46:36.030Z
+firstPublishedAt: 2023-09-20T22:13:13.268Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: amaro-integration
+locale: en
+legacySlug: amaro-integration
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tutorials/en/amazon-offer-matching.md b/docs/tutorials/en/amazon-offer-matching.md
index 99da00c5c..4a627d3af 100644
--- a/docs/tutorials/en/amazon-offer-matching.md
+++ b/docs/tutorials/en/amazon-offer-matching.md
@@ -3,8 +3,8 @@ title: 'Amazon Offer Matching'
 id: 7fRfoP69kYgg8znImMhyQ0
 status: PUBLISHED
 createdAt: 2023-05-29T15:07:38.220Z
-updatedAt: 2023-05-29T16:59:25.926Z
-publishedAt: 2023-05-29T16:59:25.926Z
+updatedAt: 2023-07-27T21:32:07.360Z
+publishedAt: 2023-07-27T21:32:07.360Z
 firstPublishedAt: 2023-05-29T16:38:11.840Z
 contentType: tutorial
 productTeam: Channels
@@ -12,14 +12,14 @@ author: 2p7evLfTcDrhc5qtrzbLWD
 slug: amazon-offer-matching
 locale: en
 legacySlug: amazon-offer-matching
-subcategory: 4YvjazdRUhQzjHJ53FCYJM
+subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
 Every time a [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) with an [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) from VTEX is sent to Amazon, the marketplace performs a process called matching, which consists of grouping offers for the same product based on their EAN.  
 
 On VTEX, the EAN is used to map the products with the corresponding [ASINs](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (*Amazon Standard Identification Number*) on Amazon. To map the equivalence between the EAN and the ASIN, manual matching is required. EAN and ASIN matches need to be exact for the offers to be linked correctly.  
 
-![Match Amazon EN](https://images.ctfassets.net/alneenqid6w5/2w6NrOhlTwsknC27Soe0pr/e8a1195e73d228f5d8b87bec9494474b/Amazon_Ad_Match.gif)
+![Offer match overview](//images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/263c3f6248e2b8d2cc07807c4800fd97/Match-an__ncios-Amazon.gif)
 
 ## Opportunity tab  
 
@@ -61,18 +61,38 @@ See the tab structure below.
 
 Once you have [sent](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD) the products, they will be available on the __Amazon Offer Matching page__. To view the unapproved offers, go to the VTEX Admin and click *Marketplace >* __Amazon Offer Matching__ or use the search bar at the top of the page.  
 
+### Single Offer Match  
+
+In the `Opportunities` tab, each listed product has the icon <i class="fas fa-ellipsis-v"></i>. Clicking on it will display two buttons: `View Details` and `View Suggested Offer`, which will redirect users to new pages. The first shows the single product match, while the second displays the suggested offer published on Amazon.
+See the buttons available on each page and their actions.
+- **`Reject` button:** It deletes the suggested match, and the seller will have to submit the product again, following the [product submission guide](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).
+- **`Reject and request review` button:** If the seller disagrees with the matching suggestion and wants to request a review from Amazon, they should choose this option. Clicking this button will take the seller to the Amazon ticket page and remove the matching suggestion from the **opportunities** list.
+This review can be tracked via the Amazon ticket dashboard.
+- **`Publish` button:** If the seller agrees with the Amazon suggestion, they should click `Publish`.
+
+To approve the match, the seller must follow the steps below.
+
+1. 	In the `Opportunities` tab, click the icon <i class="fas fa-ellipsis-v"></i>.
+2. 	Click `View Details`.
+3. 	Check out the information displayed on the page.
+![Single Offer Match](//images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/11d1054047295a3b8b03a687bb1201be/Match_individual_AMZ.png)  
+
+4. 	Then, click one of the available buttons: `Publish`, `Reject and request review`, or `Reject`.  
+
+### Bulk matching of offers  
+
 On the `Opportunity` tab, all listed products matching Your Offer and Amazon Suggestion need to be approved manually. To approve SKU and ASIN matches, follow the steps below.  
 
 1. On the `Opportunity` tab, select the checkbox next to the offer title that has a matching SKU <> ASIN.
 As you select the products, the following pop-up will appear on the screen showing the number of selected products.  
 
-![popupEN](https://images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/41058f81c65b88b1b8d48c9018e6e1ee/MATCH_AMZ_EN.png)
+![popupEN](//images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/41058f81c65b88b1b8d48c9018e6e1ee/MATCH_AMZ_EN.png)
 
 2. When you have finished selecting the products, click `Publish Selected Offers`.  
 
 3. In the match confirmation pop-up, check the selected offers and click `Confirm Publish`.  
 
-![Matching confirmation](https://images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4ebd22582c42cb2f5cd1a53f2311c2d4/MATCH_CONFIRMATION.png)
+![Matching confirmation](//images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4ebd22582c42cb2f5cd1a53f2311c2d4/MATCH_CONFIRMATION.png)
 
 Once confirmed, your offers will be sent and queued for processing. After approval, they will appear in the __Offers tab__, where you can __"View details of your offer"__, __"View offer suggested by Amazon"__, and __search for__ offers using the search bar.  
 
diff --git a/docs/tutorials/en/analytics.md b/docs/tutorials/en/analytics.md
new file mode 100644
index 000000000..b126954d2
--- /dev/null
+++ b/docs/tutorials/en/analytics.md
@@ -0,0 +1,87 @@
+---
+title: 'Analytics'
+id: 6qRMAHDL9hvv3oE0bh8mA1
+status: PUBLISHED
+createdAt: 2024-06-27T16:53:32.304Z
+updatedAt: 2024-06-27T16:54:23.587Z
+publishedAt: 2024-06-27T16:54:23.587Z
+firstPublishedAt: 2024-06-27T16:54:23.587Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: analytics
+locale: en
+legacySlug: analytics
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+**Analytics** is a page in VTEX Intelligent Search that organizes the data related to the searches carried out in the store and allows you to export this data in a CSV file.
+
+It provides insights into the performance of search results and [Autocomplete](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4gXFsEWjF7QF7UtI2GAvhL?&utm_source=autocomplete) search terms. This way, you can take actions to improve performance, such as creating redirects or adding synonyms.
+
+Follow the steps below to access the page:
+
+1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2. Under __Intelligent Search__, click __Analytics__. 
+
+<div class = "alert alert-info">
+  <p>The <b>Analytics</b> page is native to VTEX Intelligent Search. You cannot disable it in the Admin.</p>
+</div>
+
+## Data
+
+The report data is updated every four hours and contains the following information:
+
+* **Terms**: the content that users searched for.
+* **Searches**: number of searches performed for a specific term. If the customer searches for a term in the store but clicks on a different page or refreshes the current page, it will also be counted as a new search.
+* **Clicks**: total number of clicks on search results for a term.
+* **Unique clicks**: the number of unique users that have clicked on search results for a term. Indicates the number of people who clicked on a particular search result.
+* **CTR**: stands for click-through rate. It is the ratio of clicks to the total number of searches. This rate is calculated as follows: `(Clicks/Searches) * 100`.
+* **Conversion**: conversion rate of the searched terms. The conversion rate is calculated based on the formula: `(Orders/Unique clicks) * 100`. The conversion rate can be over 100%, because it takes into account the number of orders placed between clicks. For example, it is possible that the user places more than one order using the term _t-shirt_, so the conversion would be greater than 100%.
+* **Orders**: number of orders placed from the search results. To calculate this metric, we consider all orders placed after the customer clicked on a search result, even if they ended up buying a different product than the one they clicked on.
+* **Sales**: the total revenue generated by orders placed from the search results. The calculation follows the same logic as the **Orders** metric, the difference being that the result reflects the revenue instead of the number of orders.
+
+<div class="alert alert-info">
+  <p>The data displayed in the report is limited to the top 10,000 search terms. If you want the complete search data for your store, you must <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exporting-reports">export the report</a>.</p>
+</div>
+
+When you opt to [export a report](#exporting-reports), you can generate it **With funnel metrics**. If this option is selected, four new columns will be added to the file:
+
+* **ProductClicks**: for a given search term, this column shows the IDs of the products that have been clicked on and the number of clicks they received. For example, `3378|1`; `3659|2`; `4038|3` means that the product with the ID 3378 has been clicked on one time, the product with the ID 3659 has been clicked on two times and the product with the ID 4038 has been clicked on three times.
+* **PositionClickAverage**: for a given search term, this column shows the IDs of the products that have been clicked on and their average position in search results. For example, `4321|1` means that, on average, product 4321 is the first item in search results.
+* **ProductsAddToCart**: for a given search term, this column shows the IDs of the products that have been added to the shopping cart and their quantity. For example, `3380|1`; `3910|2` means that one unit of the product with the ID 3380 has been added to the cart and that two units of the product with the ID 3910 have been added to the cart.
+* **ProductsSold**: for a given search term, this column shows the IDs of the products that have been sold and their quantity. For example, `3500|1` means that 1 unit of the product with the ID 3500 has been sold.
+
+## Filters
+
+The **Analytics** page allows you to combine different filters to limit the data displayed. See below the filter options available:
+
+*   **Search** or **Autocomplete**.
+*   **With results** or **With empty results**: choose between searches that returned results or searches that returned empty results.
+*   **All**, **Mobile **or **Desktop**: limit the devices on which the searches have been performed.
+*   **Today**, **Yesterday**, **Last 7 days**, **Last 30 days**, and **Custom:** select the period you want to analyze. The **Custom** option allows you to set the start and end dates.
+
+The **Analytics** page only displays information for a maximum period of one month. To access data for a period of up to 6 months, please [export a CSV file](#exporting-reports).
+
+## Exporting reports
+
+To export a report in .csv format, you must follow the steps below:
+
+1. On the **Storefront** > **Intelligent Search** > **Analytics** page, click on the `Export` button.
+2. Set the filters for the report you want to generate.
+3. Choose whether to check the option **With funnel metrics**. If you check this option, the [columns ProductsClick, PositionClickAverage, ProductsAddToCart, and ProductsSold](#data) will be added to the file — showing the correlation between number of clicks, sales, and searched for products.
+4. Then click on `Export`.
+5. Wait until the file is available for download. Leaving this page will not interrupt the process.
+6. Click on `Download`.
+
+<div class = "alert alert-info">
+  <p>The file will be available for download for 48 hours.</p>
+</div>
+
+The report (CSV file) you have downloaded contains two tables. The first table contains information about searched terms, as illustrated below. It also shows funnel metrics (from the **ProductsClick** column to the **ProductsSold** column) if you have selected this option.
+
+![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
+
+The second table shows data for the selected period, as illustrated below. In the __Date__ column, you can see the date of the search.
+
+![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
diff --git a/docs/tutorials/en/antifraud-provider.md b/docs/tutorials/en/antifraud-provider.md
index 26844ca04..d9cd807bf 100644
--- a/docs/tutorials/en/antifraud-provider.md
+++ b/docs/tutorials/en/antifraud-provider.md
@@ -46,14 +46,14 @@ Before setting up the VTEX environment, the provider must implement the back-end
 ### 3. Antifraud Provider Administration Panel
 After receiving the access data and deploying the backend, the provider can access the approval tool through VTEX Admin. To do this, you must install the Anti-Fraud Provider App from the Apps menu:
 
-![print5](https://images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
+![print5](//images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
 
 Click on the installed app or access `https://{{AccountName}}.myvtex.com/admin/antifraud-provider`, replacing `{{AccountName}}` with the name of your account on the platform. In this environment, you can register the provider back-end configuration data and perform integration tests.
 
-![print6](https://images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
+![print6](//images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
 
 ### 4. Initial settings
-![print1](https://images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
+![print1](//images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
 
 When you access the environment through the link described in the previous item, you will see a form. Fill in the fields as indicated below:
 
@@ -77,7 +77,7 @@ After completing the fields correctly, the system will check the approved transa
 
 The tests that should be done in your integration before sending it to VTEX evaluation are displayed in the next module. You can select which tests you want to run, but for your integration to go through the analysis of our team, __all tests need to be done__. Therefore, we recommend that all of them remain selected.
 
-![print2](https://images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
+![print2](//images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
 
 ### 5. Testing
 When you click the __Execute tests__ button, the Antifraud Provider will apply the tests in your integration to the different possible scenarios. It's important to remember that __all of them are required__. To run them your service must be in HTTPS. The tests are:
@@ -107,11 +107,11 @@ For each Antifraud Provider Protocol test, we send a specific ID end to return t
 ### 6. Results
 After running the tests, the system returns the results, both positive and negative. The system also provides information on the expected results for each test. Thus, you have more visibility of what should be corrected in case of error.
 
-![print3](https://images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
+![print3](//images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
 
 To visualize in detail each action performed by the integration (and thus to identify possible errors), just click on the __Show logs__ link. A list of the complete information about the events that happened during the test will be displayed below the results.
 
-![print4](https://images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
+![print4](//images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
 
 When your integration has successfully passed all tests, please open a ticket in our [VTEX support](https://help.vtex.com/pt/support "VTEX Help"). However, before opening the ticket, make sure you have the following information:
 
@@ -135,7 +135,7 @@ Use the `https://{{AccountName}}.myvtex.com/admin/license-manager/#/home` URL, r
 Once the integration with your anti-fraud is approved, a connector will be made available for VTEX merchants to configure it on their respective websites. To do this, in addition to the contract with your company, the store will need two keys in hand: "X-PROVIDER-API-AppKey" and "X-PROVIDER-API-AppToken".
 
 An example of how the antifraud settings screen will look for the VTEX store:
-![print8](https://images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
+![print8](//images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
 
 These keys should be made available by you and will serve to identify the store that hired and is using your anti-fraud service.
 
diff --git a/docs/tutorials/en/application-keys.md b/docs/tutorials/en/application-keys.md
index 348170346..1de2490c0 100644
--- a/docs/tutorials/en/application-keys.md
+++ b/docs/tutorials/en/application-keys.md
@@ -3,134 +3,169 @@ title: 'Application Keys'
 id: 2iffYzlvvz4BDMr6WGUtet
 status: PUBLISHED
 createdAt: 2021-08-19T17:45:31.084Z
-updatedAt: 2022-11-25T18:39:48.683Z
-publishedAt: 2022-11-25T18:39:48.683Z
+updatedAt: 2023-10-17T20:17:39.441Z
+publishedAt: 2023-10-17T20:17:39.441Z
 firstPublishedAt: 2021-08-19T18:08:07.096Z
 contentType: tutorial
 productTeam: Identity
-author: 56yU9Wz6mLwmzo82TjgAHy
+author: 1malnhMX0vPThsaJaZMYm2
 slug: application-keys
 locale: en
 legacySlug: application-keys
 subcategory: 5GYFjiMQg0qIKpnnQY2qjh
 ---
 
-Each API integration used to connect your VTEX account with external systems will require the creation of an application key (or app key). These [authentication](https://developers.vtex.com/vtex-rest-api/docs/getting-started-authentication) credentials are used to give secure access to the data you wish to share with these integrations, without exposing your account to unauthorized users or applications.
+Each API integration used to connect your VTEX account with external systems will require the creation of an application key, also known as an _app key_.
 
-The **Application Keys** screen is where you can manage the [internal](#internal-app-keys) and [external](#external-app-keys) app keys that have access to your account, including:
+These [authentication](https://developers.vtex.com/docs/guides/authentication) credentials are used to ensure secure access to the data you want to share with these integrations, without exposing your account to unauthorized users or applications.
 
-- [Generating app keys in your account](#generating-app-keys-in-your-account)
-- [Managing app key permissions](#managing-app-key-permissions)
-- [Enabling or disabling app keys](#enabling-and-disabling-app-keys)
-- [Exporting app keys with access to your account](#exporting-app-keys-with-access-to-your-account)
+## Types of application keys
 
-You can find it by navigating to _Account settings > Account management > Application Keys_.
+There are two types of application keys: [internal](#internal-app-keys) or [external](#external-app-keys). This definition depends on which account creates, manages, and uses the credential.
 
-<div class = "alert alert-info">
-  Learn more about <a href="https://help.vtex.com/en/tutorial/best-practices-application-keys--7b6nD1VMHa49aI5brlOvJm">Best practices for using application keys</a>.
+### Internal app keys
+
+Internal application keys are credentials generated in and managed by your VTEX account. This means you should have access to all pairs of application keys and tokens, which is akin to usernames and passwords for API integrations.
+
+### External app keys
+
+External application keys are credentials generated in and managed by other VTEX accounts. By adding [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) to application keys — which are equivalent to usernames — provided by third parties, you can allow them to access specific resources in your account.
+
+## Managing application keys
+
+<div class="alert alert-warning">
+  <p>A <a href="https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">role</a> with the <strong>Save User</strong> <a href="https://help.vtex.com/en/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">resource</a> is required to manage users and application keys. The default role for this purpose is <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, but it is also possible to <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role">create a custom role</a> with this resource.</p>
 </div>
 
-## Types of application keys
+On the **Application Keys** page, you can manage the [internal](#internal-app-keys) and [external](#external-app-keys) app keys that have access to your account, including:
 
-### Internal app keys
+- [Generate internal application keys](#generating-internal-application-keys)
+- [Add external application keys](#adding-external-application-keys)
+- [Manage application key permissions](#managing-application-key-permissions)
+- [Activate or deactivate application keys](#activating-or-deactivating-application-keys)
+- [Export application keys with access to your account](#exporting-application-keys-with-access-to-your-account)
 
-Internal application keys are credentials generated in and managed by your VTEX account. This means you should have access to all app key and app token pairs – the equivalent of usernames and passwords for API integrations.
+To view this page, at the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
 
-### External app keys
+<div class = "alert alert-info">
+<p>Learn more about <a href="https://help.vtex.com/en/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm">best practices for using application keys</a>.</p>
+</div>
+
+## Generating internal application keys
 
-External application keys are credentials generated in and managed by other VTEX accounts. By adding [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) to application keys – the equivalent of usernames – provided by third parties, you can allow them to access specific resources in your account.
+As application keys allow external systems to access your account, they can only be created by users who have the `License Manager / Services access control / Save user` feature in their [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
 
-## Generating app keys in your account
+To create internal app keys in your account, follow the steps below:
 
-To create application keys in your account, navigate to _Account settings > Account management > Application Keys_ and click on the **Manage my keys** button. This will take you to the **My Keys** page, which lists all [internal app keys](#internal-app-keys).
+1. At the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
+2. Click the `Manage My Keys` button.
 
-![My Keys](//images.contentful.com/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/1c98224b6f50673c4567f21e22de4978/image3.png)
+	You will be redirected to the **My Keys** page, as shown below. This page lists all [internal app keys](#internal-application-keys).
 
-These are the visible fields in the **My Keys** page:
+    ![My Keys](//images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/1c98224b6f50673c4567f21e22de4978/image3.png)
 
-- **Label:** text field describing the purpose of the app key.
-- **Key:** text field containing the unique identifier for the app key.
-- **Status:** boolean field indicating whether the app key is active or inactive.
+    These are the visible fields on the **My Keys** page:
 
-Since application keys allow external systems to gain access to your account, their creation is restricted to users with the `License Manager / Services access control / Save user` resource included in their [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+	- **Label:** Text field describing the purpose of the app key.
+	- **Key:** Unique identifier for the app key.
+	- **Status:** Current status of the app key, which can be active or inactive.
+
+3. Click the `+ Generate New` button.
+4. (Optional) Complete the **Label** with a description of the purpose of the app key. This field is set only when creating the app key and cannot be changed afterward. If left blank, it will default to the **Key** value of the generated app key.
+5. (Optional) Click `+ Add Roles` to [manage application key permissions](#managing-application-key-permissions).
+6. Click the `Generate` button.
+7. Click <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> to copy the **Application token**. _This secret will only be displayed once. Save it in a safe place._
+
+<div class="alert alert-warning">
+  <p>Secure your application keys and token pairs as you would with other credentials, such as usernames and passwords. If you suspect an application key is compromised, immediately deactivate the key in your account. To learn more, read the <a href="#activating-or-deactivating-application-keys">Activating or deactivating application keys</a> section of this article.</p>
+</div>
 
-To generate a new application key:
+## Adding external application keys
 
-1. Click on the **⊕ Generate new** button.
-2. (Optional) Fill in the **Label** with a description of the purpose of the app key. This field is immutable and can only be set when the app key is being generated. If left blank, the field will be set to the **Key** value of the generated app key.
-3. (Optional) Click on the **+ Add roles** to [manage app key permissions](#managing-app-key-permissions).
-4. Click on the **Generate** button.
-5. Click on the <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> button to copy the Application Token. _This secret will only be displayed once. Save it in a safe place._
+To add third-party application keys, follow the steps below:
 
-<div class="alert alert-warning">Secure your app key and app token pairs as you would with other credentials, such as usernames and passwords. If you suspect an application key is compromised, immediately disable the key in your account. See <a href="#enabling-and-disabling-app-keys">Enabling and disabling app keys</a> for details.</div>
+1. At the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
+2. Click the `+ Add 3rd Party Key` button.
+3. Complete the **Key** field with the app key provided by the third party.
+4. Click `+ Add Roles` to [manage application key permissions](#managing-application-key-permissions). Add roles to allow them to access the resources you desire.
+5. Click `Save`.
 
-## Managing app key permissions
+## Managing application key permissions
 
-For an application key to successfully make API requests to your account, it must both be active and have [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) specifying the account resources it is allowed to access. 
+For an application key to successfully make API requests to your account, it must both be active and have [roles](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) specifying the account resources it is allowed to access.
 
 <div class="alert alert-danger">
-<b>Warning!</b> Unrestricted use of very permissive roles increases the risk of attacks on stores by login credentials leakage.
+<p>Unrestricted use of overly permissive roles increases the risk of store attacks through leaked login credentials.</p>
 </div>
 
 Application keys are created, by default, with no permission to access any account resources.
 
 There are three different paths to the page where you can edit the roles for an app key:
 
-- **+ Add roles** button when [generating app keys](#generating-app-keys-in-your-account) in your account.
-- **⊕ Add button** in the **Application Keys** page.
-- **፧** button and selecting the **Edit** option in the **Application Keys** or **My Keys** pages.
+- Use the `+ Add Roles` button to [generate application keys](#generating-application-keys-in-your-account) in your account.
+- Use the `+ Add 3rd Party Key` button on the **Application keys** page.
+- Use the `፧` button and select the **Edit** option on the **Application Keys** or **My Keys** pages.
 
-When editing an app key you can: 
+When editing an application key, you can:
 
-- Add roles by clicking on the **+ Add roles** button, selecting one or more roles and clicking on the **Add roles** button. 
-- Remove roles by using the checkboxes to select and clicking on the **Remove roles** button.
-- Save by clicking on the **Save** button.
+- Add roles by clicking the `+ Add Roles` button, selecting one or more roles, and clicking the `Add Roles` button.
+- Remove roles by selecting them using the checkboxes and then clicking the `Remove Roles` button.
+- Save the changes by clicking the `Save` button.
 
-Once you have added roles to an application key, it will show up in the **Application Keys** page.
+Once you have added roles to an application key, it will be displayed on the **Application Keys** page.
 
-![Application Keys](//images.contentful.com/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/da66ebc249dd18cbc709d872ce78719c/image2.png)
+![Application Keys](//images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/4ca25e35b379a4a71370c1e07221cf1a/appkeys-en.png)
 
-These are the visible fields in the **Application Keys** page:
+These are the visible fields on the **Application Keys** page:
 
-- **Key:** text field containing the unique identifier for the app key.
-- **Account:** text field indicating the VTEX account that manages the app key.
-- **Status:** boolean field indicating whether the app key is active or inactive.
+- **Key:** Unique identifier for the app key.
+- **Account:** VTEX account managing the app key.
+- **Status:** Current status of the app key, which can be active or inactive.
+
+<div class="alert alert-info">
+  <p>Note that the <strong>Label</strong> field is not displayed on the <strong>Application Keys</strong>page. To see a description of the purpose of an internal app key, you will have to use the<strong>Key</strong> value to find it on the <strong>My Keys</strong> page. It is not possible to add labels to external app keys.</p>
+</div>
+
+## Activating or deactivating application keys
+
+If an application key that has access to your account is compromised, you should immediately revoke its access to your account. If you make a mistake, you can reactivate it to reestablish the impacted integration. This can be done in various ways depending on the [type of application key](#types-of-application-keys).
+
+<div class="alert alert-warning">
+  <p>You should only reactivate an app key if you are certain it has not been compromised. Anyone with the associated app token will regain privileged access to your account.</p>
+</div>
 
-<div class="alert alert-info">Note that the <strong>Label</strong> field is not shown in the <strong>Application Keys</strong> page. To see a description of the purpose of an internal app key, you will have to use the <strong>Key</strong> value to find it in the <strong>My Keys</strong> page. It is not possible to add labels to external app keys.</div>
+### Deactivating internal application keys
 
-## Enabling and disabling app keys
+To deactivate an internal app key, follow the steps below:
 
-If an application key that has access to your account is compromised, you should immediately revoke its access to your account. If you make a mistake, you can re-enable it to reestablish the impacted integration. The way to do this depends on the [type of application key](#types-of-application-keys).
+1. At the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
+2. Click the `Manage My Keys` button.
+3. Find the app key you want to deactivate in the list and click the `፧` button.
+4. Click the **Deactivate** option.
 
-<div class="alert alert-warning">You should only re-enable an app key if you are certain it has not been compromised. Anyone with the associated app token will regain privileged access to your account.</div>
+### Deactivating external application keys
 
-To disable an internal app key: 
+To deactivate an external application key, follow the steps below:
 
-1. Navigate to _Account settings > Account management > Application Keys_.
-2. Click on the **Manage my keys** button.
-3. Find the app key you want to disable in the list and click on the ፧ button.
-4. Select the **Deactivate** option.
+1. At the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
+2. Find the app key you want to deactivate in the list and click the `፧` button.
+3. Click the **Remove** option.
 
-To disable an external app key: 
+### Activating internal application keys
 
-1. Navigate to _Account settings > Account management > Application Keys_.
-2. Find the app key you want to disable in the list and click on the **፧** button.
-3. Select the **Remove** option.
+To reactivate internal application keys that have previously been deactivated, follow the steps below:
 
-To re-enable internal app keys that have been previously deactivated:
+1. At the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
+2. Click the `Manage My Keys` button.
+3. Find the app key you want to reactivate in the list and click the `፧` button.
+4. Click the **Activate** option.
 
-1. Navigate to _Account settings > Account management > Application Keys_.
-2. Click on the **Manage my keys** button.
-3. Find the app key you want to re-enable in the list and click on the **፧** button.
-4. Select the **Activate** option.
+### Activating external application keys
 
-To re-enable external app keys that have been previously deactivated:
+To reactivate external application keys that have previously been deactivated, you will need to follow the instructions again as described in the [Adding external application keys](#adding-external-application-keys) section.
 
-1. Navigate to _Account settings > Account management > Application Keys_.
-2. Click on the **⊕ Add button**.
-3. Fill in the **Key** field with the app key provided by the third party.
-4. Add roles to allow them to access the resources you desire.
+## Exporting application keys with access to your account
 
-## Exporting app keys with access to your account
+If necessary for a security audit, you can export a CSV file containing the **Key** values for all internal and external app keys that currently have access to your account — that is, that have roles associated with them.
 
-If necessary for a security audit, you can export a CSV file containing the **Key** values for all internal and external app keys that currently have access to your account – that is, that have roles associated with them. This can be done by navigating to _Account settings > Account management > Application Keys_ and clicking on the <span style="display: inline-block;"><img src="//images.contentful.com/alneenqid6w5/25JqGWNUZPZattDX6ORXX6/742e99e17042024b9cae641564909171/image4.png" alt="export-button"/> <strong>Export</strong></span> button.
+To export the keys, go to _Account settings > Application keys_ and click the <span style="display: inline-block;"><img src="//images.contentful.com/alneenqid6w5/25JqGWNUZPZattDX6ORXX6/742e99e17042024b9cae641564909171/image4.png" alt="export-button"/> <strong>Export</strong></span> button.
diff --git a/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
index 6641ad1f6..02e8f9701 100644
--- a/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
@@ -3,8 +3,8 @@ title: 'Approving payment of the bank payment slip'
 id: tutorials_184
 status: PUBLISHED
 createdAt: 2017-04-27T22:16:19.919Z
-updatedAt: 2023-03-26T21:44:48.077Z
-publishedAt: 2023-03-26T21:44:48.077Z
+updatedAt: 2024-06-03T20:36:09.927Z
+publishedAt: 2024-06-03T20:36:09.927Z
 firstPublishedAt: 2017-04-27T23:00:46.699Z
 contentType: tutorial
 productTeam: Financial
@@ -25,7 +25,7 @@ This approval can be done manually through the Orders Management module as shown
 2. Click on the transaction.
 3. Click on **Notify Payment** button.
 
-![NotificarEN](https://images.ctfassets.net/alneenqid6w5/19t11NnJzs40wGQqkaeKIu/1d7fee23772ca875bccb59286859c415/NotificarEN.png)
+![NotificarEN](//images.ctfassets.net/alneenqid6w5/19t11NnJzs40wGQqkaeKIu/1d7fee23772ca875bccb59286859c415/NotificarEN.png)
 
 **After approval of the payment, the order will go through the normal purchase flow.**
 
@@ -33,7 +33,7 @@ This approval can be done manually through the Orders Management module as shown
 In the Account management module, the user must have a role that includes the <code>Notify payment</code> permission to be able to approve payments.
 </div>
 
-To approve payments through API, check the [documentation about the payment notification request](https://developers.vtex.com/reference/payment#getorder).
+To approve payments through API, check the [documentation about the payment notification request](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/payments/-paymentId-/payment-notification).
 
 <div class="alert alert-warning">
 Since <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">ERP integrations</a> are governed by the <a href="https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#">orders flow</a>, manually approving a payment will continue the integration of this order with the store’s back office as usual. Therefore, caution is recommended when approving payments manually, in order to ensure that every order that is processed and shipped is received.
diff --git a/docs/tutorials/en/apps-overview.md b/docs/tutorials/en/apps-overview.md
index f18886afe..df2bff066 100644
--- a/docs/tutorials/en/apps-overview.md
+++ b/docs/tutorials/en/apps-overview.md
@@ -36,7 +36,7 @@ The Apps menu allows merchants to download new apps directly from the App Store
 
 These operations can be found in the Apps menu of your redesigned Admin.
 
-![Apps Overview menu EN](https://images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/76a9830a08af07c0cdd5ebecfb7a5ca9/Apps_Overview_menu_EN.jpg)
+![Apps Overview menu EN](//images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/76a9830a08af07c0cdd5ebecfb7a5ca9/Apps_Overview_menu_EN.jpg)
 
 See below for more details on the different sections and pages of this feature, which will soon be available in the redesigned Admin. 
 
diff --git a/docs/tutorials/en/assembly-options-app.md b/docs/tutorials/en/assembly-options-app.md
index 0a596bef5..eaeac0b8d 100644
--- a/docs/tutorials/en/assembly-options-app.md
+++ b/docs/tutorials/en/assembly-options-app.md
@@ -37,7 +37,7 @@ After installation, the **Catalog > Assembly Options** page will become availabl
 
 In the VTEX Admin, go to **Catalog > Assembly Options** to access a list with all the assembly options available in your store.
 
-![assembly-options-app-en](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
+![assembly-options-app-en](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
 
 Below, you will find the information displayed in the list:
 
diff --git a/docs/tutorials/en/assembly-options-in-vtex-sales-app.md b/docs/tutorials/en/assembly-options-in-vtex-sales-app.md
new file mode 100644
index 000000000..d64ee4521
--- /dev/null
+++ b/docs/tutorials/en/assembly-options-in-vtex-sales-app.md
@@ -0,0 +1,60 @@
+---
+title: 'Assembly Options in VTEX Sales App'
+id: 4fTfqOMcXyhAhWXkl935lr
+status: PUBLISHED
+createdAt: 2024-04-30T11:16:48.636Z
+updatedAt: 2024-04-30T17:04:30.041Z
+publishedAt: 2024-04-30T17:04:30.041Z
+firstPublishedAt: 2024-04-30T14:58:57.024Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: assembly-options-in-vtex-sales-app
+locale: en
+legacySlug: assembly-options-in-vtex-sales-app
+subcategory: 4T6qfa6gNO6g4sAUIa6s2G
+---
+
+[VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) is an app that allows integration between online and physical sales channels. It enables sales associates to offer customized, in-person service to customers while handling an end-to-end sales process — from choosing products to finding the best payment method and shipping option.
+
+For more information on installing VTEX Sales App, check out the article [VTEX Sales App - Basic Settings](https://help.vtex.com/en/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO).
+
+[Assembly Options](https://help.vtex.com/en/tutorial/assembly-options-app) is available in the VTEX App Store and allows sellers to offer additional services during the sale process, such as extended warranties and protection plans. It also makes it possible to assemble sets of multiple SKUs, such as Christmas or breakfast baskets, makeup sets, etc.
+
+## Installing Assembly Options
+
+To use Assembly Options, you need to have the [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) and the Assembly Options App installed in your store. The [Assembly Options App](https://help.vtex.com/en/tutorial/assembly-options-app--54mWg37mojrqOgCA79iqqk) is only available for [VTEX IO](https://developers.vtex.com/docs/guides/welcome) stores.
+
+## Assembly options app scenarios in VTEX Sales App
+
+There are two scenarios for adding services to products in a single cart:
+
+**Scenario 1:** Selecting a single service
+
+1. Add to the cart a product that has an Assembly Options service associated with it.
+2. Select the service option you want and click the **Continue to Cart** button.
+3. After completing the process, you can view the selected services in your cart, along with the total order amount.
+
+![Garantia estendida - EN](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/f81df1f138065b8954e3120a7fc0b4b7/Cen_rio_1__T1__-_EN.png)
+
+![Carrinho - EN](//images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/cec8bd9e2deaac996bf5dbe8af8ab620/Cen_rio_1__T2__-_EN.png)
+
+**Scenario 2:** Selecting multiple services
+
+1.	Add to the cart a product that has an Assembly Options service associated with it.
+
+2.	You can choose more than one service by selecting the service you want and clicking the Next button.
+
+3.	Select the other service you want to add and click the **Continue to Cart** button.
+
+4.	After completing the process, you can view the selected services in your cart, along with the total order amount.
+
+5.	Click the **Continue** button. If any services require additional information, complete the necessary fields to link this information to the purchased service.
+
+6.	Click the **Apply** button.
+
+![Garantia estendida - EN](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/f81df1f138065b8954e3120a7fc0b4b7/Cen_rio_1__T1__-_EN.png)
+
+![Seguro - EN](//images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/09bc8e283906d9472ddc71e79ac3e492/Cen_rio_2__T2__-_EN.png)
+
+![Ordem pedido - EN](//images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/92e7055b292e8e3385e0ee3b1814c38b/Cen_rio_2__T3__-_EN.png)
diff --git a/docs/tutorials/en/assembly-options.md b/docs/tutorials/en/assembly-options.md
index 07948c72c..9c39b6162 100644
--- a/docs/tutorials/en/assembly-options.md
+++ b/docs/tutorials/en/assembly-options.md
@@ -3,8 +3,8 @@ title: 'Assembly Options'
 id: 5x5FhNr4f5RUGDEGWzV1nH
 status: PUBLISHED
 createdAt: 2021-10-25T20:22:43.094Z
-updatedAt: 2023-03-29T17:55:49.763Z
-publishedAt: 2023-03-29T17:55:49.763Z
+updatedAt: 2024-06-06T19:38:13.881Z
+publishedAt: 2024-06-06T19:38:13.881Z
 firstPublishedAt: 2021-10-25T21:39:46.746Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ An assembly option is an [attachment](https://help.vtex.com/en/tutorial/what-is-
 
 In the example below, a store offers multiple assembly options for the Custom Bell product. These options are shown on the product page, where the customer can select the desired options. Depending on the choices, there may be an additional cost for the SKU.
 
-![assembly-option-EN](https://images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/585aace6b147a8107f0f5d03faa5db5f/image.png)
+![assembly-option-EN](//images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/585aace6b147a8107f0f5d03faa5db5f/image.png)
 
 You can combine [SKUs](https://help.vtex.com/en/tutorial/what-is-an-sku--1K75s4RXAQyOuGUYKMM68u) to provide assembly options, such as the Bells add-ons Roman or the Bells add-ons 1-3 lines in the example above. If an item is out of stock, it will be shown as unavailable.
 
@@ -61,7 +61,7 @@ The first elements `[x-y]` are group rules, and between each `#` and `;` are SKU
 | \[0-3\]#10000\[1-2\]**\[1\]**pricetable1;#20000\[0-2\]**\[0\]**pricetable2;#30000\[0-2\]**\[0\]**pricetable3 | This segment defines the default selected quantity for each SKU.  |
 | \[0-3\]#10000\[1-2\]\[1\]**pricetable1**;#20000\[0-2\]\[0\]**pricetable2**;#30000\[0-2\]\[0\]**pricetable3** | The final segment indicates the price table for each item.  | 
 
-![assembly-option-exemplo-EN](https://images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/939c084743ddf02d3903af57104f0b39/image.png)
+![assembly-option-exemplo-EN](//images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/939c084743ddf02d3903af57104f0b39/image.png)
 
 #### Attachment Settings
 
diff --git a/docs/tutorials/en/associate-a-sku-to-a-trade-policy.md b/docs/tutorials/en/associate-a-sku-to-a-trade-policy.md
index 28366bc92..5191d7a43 100644
--- a/docs/tutorials/en/associate-a-sku-to-a-trade-policy.md
+++ b/docs/tutorials/en/associate-a-sku-to-a-trade-policy.md
@@ -1,10 +1,10 @@
 ---
 title: 'Associate a SKU to a trade policy'
 id: 1qFAiybogHCStRO65sy4vb
-status: CHANGED
+status: PUBLISHED
 createdAt: 2021-03-30T17:18:09.088Z
-updatedAt: 2023-03-29T18:27:48.036Z
-publishedAt: 2021-08-04T18:13:54.928Z
+updatedAt: 2024-05-31T22:32:04.940Z
+publishedAt: 2024-05-31T22:32:04.940Z
 firstPublishedAt: 2021-03-30T17:34:49.644Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -29,4 +29,8 @@ You can associate an SKU with one or more trade policies on the configuration pa
 6. Mark the checkbox of the trade policy for B2B.
 7. At the bottom of the page, click on the `Save` button to save changes.
 
+<div class="alert alert-warning" role="alert">
+  <p>If no specific trade policy is selected on the SKU configuration, all trade policies will have access to the SKU.</p>
+</div>
+
 Every change made to an SKU takes time to be processed, including associating it with trade policies. This period is called re-indexing. Learn more in the article [How indexing works](https://help.vtex.com/en/tutorial/understanding-how-indexation-works--tutorials_256).
diff --git a/docs/tutorials/en/associating-a-template-with-a-layout.md b/docs/tutorials/en/associating-a-template-with-a-layout.md
index fddaa01c7..472f8b351 100644
--- a/docs/tutorials/en/associating-a-template-with-a-layout.md
+++ b/docs/tutorials/en/associating-a-template-with-a-layout.md
@@ -35,4 +35,4 @@ This association is made in the layout properties setting. To get there, follow
 6. Select the template you want to associate with this layout.
 7. Type `yes` to confirm the change (this step is necessary because this is a critical change for the site, as the page's front-end will be replaced).
 
-![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tutorials/en/audit.md b/docs/tutorials/en/audit.md
new file mode 100644
index 000000000..fe2dc95bc
--- /dev/null
+++ b/docs/tutorials/en/audit.md
@@ -0,0 +1,136 @@
+---
+title: 'Audit'
+id: 5RXf9WJ5YLFBcS8q8KcxTA
+status: PUBLISHED
+createdAt: 2021-10-21T16:51:06.108Z
+updatedAt: 2024-04-18T14:03:48.943Z
+publishedAt: 2024-04-18T14:03:48.943Z
+firstPublishedAt: 2021-10-21T21:55:42.939Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: audit
+locale: en
+legacySlug: searching-for-events-on-audit
+subcategory: 2TNXiKzLZOPxjMTyGiEeJu
+---
+
+To increase transparency and trust among your store admin users, VTEX records different operations, their authors and timestamps in **Audit**, a module used to query and investigate this history through filters.
+
+To access the Audit page in the VTEX Admin, go to **Apps > Installed Apps > Audit**, or type **Audit** in the search bar. On this page, you can do the following:
+
+* [Query events in Audit](#querying-events-in-audit)
+* [View the last queries in Audit](#viewing-the-last-queries-in-audit)
+
+<div class="alert alert-info">
+  <p>To view Audit events, you must have a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> associated with the <em>Insights Metrics</em>  <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">resource</a>.</p>
+</div>
+
+![audit-ui-en (1)](//images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/9e040c47cb3220175bf368155f438813/audit-ui-en__1_.png)
+
+## Querying events in Audit
+
+Audit allows you to query events using filters related to the following information: application, date, action, author, and event details. Below, we explain how to use Audit [filters](#filters) and how the [results](#results) are displayed. We also use practical [examples](#query-examples) to demonstrate the use of filters.
+
+### Filters
+
+Follow the instructions to search for an event using the filters available in Audit:
+
+1. In the VTEX Admin, go to **Apps > Installed Apps > Audit**, or type _Audit_ in the search bar. You will be redirected to the **Audit Events** tab.
+2. In the **Application** menu under **Filters**, select the application related to the query.
+3. In the **Date** menu, choose a predefined date for the query. If you prefer to set the exact date range for the query, select the **Custom** option and choose the **Start** and **End** dates for the query.
+
+   <div class= "alert alert-info">
+     <p>Only records from the last 3 months are stored.</p>
+   </div>
+
+4. If you wish, add a filter by Action. To do this, in the field next to `Action` **must be**, type the name of the action and press `Enter`. You can enter more than one value by pressing `Enter` after each selection. Check the name of each action in [Events available in Audit](https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
+5. If necessary, you can add specific filters to search for events more accurately. To do this, click the `Add Filter` button.
+5. Select the filter parameter (_Author_ or _Event Details_) and enter the value to which the parameter should be compared.
+
+    When adding filters with the same parameter (for example: `Action = Change Promotion Configuration` or `Change Coupon Configuration`), the results include events that match any of the values entered. When adding filters with different parameters (for example: `Action = Change Coupon Configuration` and `Author = email@mail.com`), the criteria are combined. Note that you can repeat steps 4 and 5 to add more filters.
+
+    For example, the query in the image below returns results for `Change Promotion Configuration` or `Change Coupon Configuration` actions whose author is `email@mail.com`.
+
+    ![filtros-en (1)](//images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/266db3f0a88fe7e35268d8e2410c0052/filtros-en__1_.png)
+
+7. Click the `Apply` button to obtain the events found.
+
+    Check the [Results](#results) section to see how the events are displayed.
+
+<div class= "alert alert-warning">
+  <p>The query results correspond exactly to the content entered in the filter field. To avoid unexpected results, make sure you haven't typed extra spaces in the query terms.</p>
+</div>
+
+If you wish, you can share a query with another user. To do this, click `Share Query` in the top right-hand corner of the page. The link to the Audit search will be copied to your clipboard.
+
+### Results
+
+The **Results** section lists all events found in the query and displays information about each event, as shown in the table below.
+
+| Column | Description |
+|---|---|
+| __Copy__ | Button to copy the event information displayed in the table to the clipboard. |
+| __Event Time__ | Date and time of the event, displayed in the browser or operating system timezone. |
+| __Action__ | Action performed in the selected application for the query. Check the possible actions in the [list of events available in Audit](https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ). |
+| __Event Details__ | Additional information about the event. Check the details displayed for each event in the [list of events available in Audit](https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ). |
+| __Author__ | Email, ID, or token of the user who performed the event. |
+| __More Details__ | Button that opens a modal with more information about the event, when applicable. The details displayed may include: <ul><li class="t-body mb5 lh-copy"><strong>Entity name:</strong> The ID of the entity that was changed.</li><li class="t-body mb5 lh-copy"><strong>Entity before action:</strong> dInformation about the entity before the event, in <a href="http://www.json.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" rel="noopener noreferrer" target="_blank">JSON</a> format.</li><li class="t-body mb5 lh-copy"><strong>Entity after action:</strong> Information about the entity after the event, in <a href="http://www.json.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" rel="noopener noreferrer" target="_blank">JSON</a> format.</li></ul>Depending on the event, not all the information above is displayed. For example, an event that deleted information only displays the entity before the action. In contrast, an event that added information only displays the entity after the action. <br /><br /> Some events have no additional information. In such cases, the modal is left blank. |
+
+### Query examples
+
+Below, we've listed some common query scenarios to illustrate how filters should be arranged depending on what you want to query.
+
+#### Product activation
+
+To query if a product was activated in the Catalog on a given date:
+
+1. Select the desired date.
+2. In the **Application** menu, select _Catalog (Admin)_.
+3. Add a filter whose **Action** must be `Product Activation`.
+4. Add a filter whose **Event Details** must be equal to `activated product ID "X"`, where `X` must be replaced by the ID of the product queried.
+
+#### Price change
+
+To query whether the price of an SKU changed on a given date:
+
+1. Select the desired date.
+2. In the **Application** menu, select _Prices_.
+3. Add a filter whose **Action** must be `Put Price`.
+4. Add a filter whose **Event Details** must be the SKU ID of the item queried.
+
+#### Warehouse deletion
+
+To query whether a warehouse was deleted on a given date:
+
+1. Select the desired date.
+2. In the **Application** menu, select _Inventory & Shipping_.
+3. Add a filter whose **Action** must be `Warehouse Delete`.
+4. Add a filter whose **Event Details** must be the ID of the item queried.
+
+#### Carrier deletion
+
+To query whether a carrier was deleted on a given date:
+
+1. Select the desired date.
+2. In the **Application** menu, select _Inventory & Shipping_.
+3. Add a filter whose **Action** must be `Carrier Delete`.
+4. Add a filter whose **Event Details** must be the ID of the carrier queried.
+
+## Viewing the last queries in Audit
+
+Every query made in Audit is saved in the **Last queries** tab. To redo a query in this tab, click the  button corresponding to the query you want to redo.
+
+See below the information available in this tab:
+
+| Column | Description |
+|---|---|
+| Queried on | Date and time the query was made in Audit. |
+| Application | VTEX application in which the events were queried. |
+| Terms | Filters applied to the query. |
+| Period | Start and end date of the period selected for the query. |
+| Redo Query | Button to redo the query. |
+
+<div class= "alert alert-warning">
+  <p>The <strong>Last queries</strong> tab only saves up to 50 queries. If you want to save a query beyond this limit, add it to your browser favorites.</p>
+</div>
diff --git a/docs/tutorials/en/authentication.md b/docs/tutorials/en/authentication.md
new file mode 100644
index 000000000..15363d0a5
--- /dev/null
+++ b/docs/tutorials/en/authentication.md
@@ -0,0 +1,86 @@
+---
+title: 'Authentication'
+id: 21CkKHLKP1o41lUpGhuRUs
+status: PUBLISHED
+createdAt: 2021-10-25T19:06:37.982Z
+updatedAt: 2024-02-26T20:32:47.823Z
+publishedAt: 2024-02-26T20:32:47.823Z
+firstPublishedAt: 2021-11-08T18:39:50.432Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: authentication
+locale: en
+legacySlug: authentication-page
+subcategory: 14V5ezEX0cewOMg0o0cYM6
+---
+
+Authentication is the process of validating a user's identity, which, on VTEX, can be done in three different ways:
+
+* [Login](#login): Verifies and validates the user's identity when accessing an online store or the VTEX Admin.
+* [Developing integrations](#developing-integrations): Authenticates requests made to VTEX APIs from integrations with external services. This validation is usually through API keys or user tokens.
+* [Developing apps](#developing-apps): Ensures the legitimacy of communication between applications developed with VTEX IO and VTEX APIs. This validation is usually through authentication tokens.
+
+## Login
+
+On VTEX, login authentication occurs in two contexts: in the webstore, when customers log in to access their profile or place an order, and in the Admin, when admin users log in to manage the store's administrative environment.
+
+You need to configure which authentication method will be available in each context. See the available options in the table below:
+
+| Login method | Description | Webstore | Admin |
+|---|---|---|---|
+| Access code | A random numeric code is sent to the user's email, and they use this code to log in. | Can be enabled | Always enabled |
+| Password | The user creates a password and logs in using their email and password. Merchants can choose to [enforce password expiration](#enforcing-password-expiration) after a specific period for Admin users. | Can be enabled | Always enabled. Password expiration can be enabled. |
+| Facebook | The user logs in using their Facebook account. Check out the [Configuring login with Facebook and Google](https://help.vtex.com/en/tutorial/configurar-login-com-facebook-e-google--tutorials_513) guide for more information. | Can be enabled | Not available |
+| Google | The user logs in using their Google account. Check out the [Configuring login with Facebook and Google](https://help.vtex.com/en/tutorial/configurar-login-com-facebook-e-google--tutorials_513) guide for more information. | Can be enabled | Can be enabled |
+| Integration with other ID providers | The user logs in using their account from other external ID providers through an integration. Read the [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) developer guide to learn more. | Can be enabled using the OAuth protocol.  Read the [Webstore (OAuth 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) developer guide to learn more. | Can be enabled using the SAML protocol. Read the [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) developer guide to learn more. |
+
+<div class="alert alert-info">
+  <p>At least one of the login methods in the table above must be enabled for the webstore.</p>
+</div>
+
+<div class="alert alert-warning">
+  <p>You must have a valid admin <a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512">user</a> to log in to the VTEX Admin. The <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> and permissions assigned to the user specify which<a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3"> resources</a> they can use in the Admin.</p>
+</div>
+
+### Enabling login methods
+
+On the **Authentication** page, you can choose which login methods you want to offer for your store's customers and administrative users accessing the Admin.
+
+![Authentication page](//images.ctfassets.net/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/06ed0a952614213a04bc68fc8fa5fa4e/Tela_de_Autentica____o_EN.png)
+
+Follow the steps below to enable the desired login methods:
+
+1. In the top bar of the VTEX Admin, click your profile avatar, indicated by the initial letter of your email address.
+2. Click **Account settings > Authentication**.
+
+    You will be redirected to the **Webstore** tab listing the login methods available in your store. In this tab, you can enable the desired customer login methods.
+
+    To configure the login methods in the Admin for administrative users, click the **Admin** tab.
+
+    See the table in the [Login](#login) section to learn about the available login methods and access the documentation explaining how to configure them.
+
+### Enforcing password expiration for Admin users
+
+If the password login option is enabled, you can set Admin user passwords to expire after a specified number of days. To do this, follow the instructions below:
+
+1. In the top bar of the VTEX Admin, click your profile avatar, indicated by the initial letter of your email address.
+2. Click **Account settings > Authentication**.
+3. Click the **Admin** tab.
+4. In the **Password** row, click` Edit`. 
+5. Check the **Enforce password expiration** option.
+6. Select a period after which user passwords will become invalid. You can choose **15**, **30**, or **90** days.
+7. Click `Save`.
+
+Once the expiration period is reached, Admin users will be required to reset their password when attempting to log in.
+
+## Developing integrations
+
+When developing integrations using VTEX [APIs](https://developers.vtex.com/docs/guides/getting-started), you must provide authentication parameters for the desired operations. See the available methods below:
+
+- **Application keys (appKeys):** [Application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) authenticate requests made to VTEX APIs. Store admins can create keys and associate them with [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc), allowing them to use certain platform[ resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3). Learn more in the [API authentication using application keys](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys) developer guide.
+-	**User tokens:** User tokens authenticate API requests, especially for[ frontend](https://help.vtex.com/en/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl) applications developed with VTEX IO. Learn how to use them in the [API authentication using user tokens](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) developer guide.
+
+## Developing apps
+
+Authentication tokens (auth tokens) are required for authentication when developing apps on VTEX IO. Learn more in the [App authentication using auth tokens](https://developers.vtex.com/docs/guides/app-authentication-using-auth-tokens) developer guide.
diff --git a/docs/tutorials/en/autocomplete.md b/docs/tutorials/en/autocomplete.md
new file mode 100644
index 000000000..e4cac2866
--- /dev/null
+++ b/docs/tutorials/en/autocomplete.md
@@ -0,0 +1,77 @@
+---
+title: 'Autocomplete'
+id: 6qhP0ZQ4JqUBdgFnbnxS4a
+status: PUBLISHED
+createdAt: 2024-06-27T16:42:03.645Z
+updatedAt: 2024-06-27T16:42:56.071Z
+publishedAt: 2024-06-27T16:42:56.071Z
+firstPublishedAt: 2024-06-27T16:42:56.071Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: autocomplete
+locale: en
+legacySlug: autocomplete
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+<div class = "alert alert-warning">
+The Autocomplete tool is enabled by default in VTEX Intelligent Search. It is not possible to disable it in the Admin.
+</div>
+
+Autocomplete is the functionality that displays previous search results based on current and previous searches. These results are presented in four different lists, which can be together or separated, depending on the customer's interaction. The existing sections are:
+
+- Last searches performed;
+
+- Search suggestion;
+
+- Product suggestion;
+
+- Most searched terms.
+
+<div class="alert alert-warning" role="alert">
+<p>When searching for a term not listed, Autocomplete will not find products with that specification and will not display any suggestions.
+</p>
+</div>
+
+During the interaction with the search bar, VTEX Intelligent Search immediately displays the set of _Most searched terms_ and _Last searches_ (if the customer has done searches before).
+
+When the user starts typing, the system displays the _Search suggestions_ and the _Product suggestions_ and removes the previous lists.
+
+<div class = "alert alert-info">
+  <p>Section information <i>Most searched terms</i> and <i>Search suggestions</i> are updated daily using the data from the last 14 days of the customers' interaction with the search.</p>
+  </div>
+
+This way, it is possible to provide the customer with a more fluid and personalized search experience. They can view the result quickly and receive suggestions based on their search.
+
+Another advantage for the store's manager is the increase in conversion due to this dynamic of usability and experience.
+
+<div class = "alert alert-info">
+  <p>Autocomplete offers search keyword suggestions even for completely new stores that do not yet have data on customer interaction such as clicks and searches.
+    In this case, the feature suggests search options based on an algorithm that extracts keywords from the store's catalog, products, brands, and categories.
+    </p>
+  </div>
+
+ ## Most searched terms
+
+This section displays the most searched terms on the website by other customers.
+
+![top-busca-EN](//images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
+
+## Last searches
+
+This section displays the last searches performed by the customer. This way, it is possible to start the interaction with the search instantly.
+
+![historico-EN](//images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
+
+## Search suggestions
+
+This section displays the terms and categories other users searched related to the search performed at that time. 
+
+![sugest-EN](//images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
+
+## Product suggestion
+
+This section shows the products that correspond to the search carried out at that moment. By displaying products related to your search while you are typing, it reduces dropouts and gives the user the possibility to make a more dynamic purchase.
+
+![produtos-EN](//images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
diff --git a/docs/tutorials/en/availability.md b/docs/tutorials/en/availability.md
new file mode 100644
index 000000000..406d77a2b
--- /dev/null
+++ b/docs/tutorials/en/availability.md
@@ -0,0 +1,32 @@
+---
+title: '​​Availability'
+id: 3ZcZOzTSr2RdauUbn7qTa9
+status: PUBLISHED
+createdAt: 2024-06-24T17:51:07.903Z
+updatedAt: 2024-06-24T18:00:08.767Z
+publishedAt: 2024-06-24T18:00:08.767Z
+firstPublishedAt: 2024-06-24T18:00:08.767Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: availability
+locale: en
+legacySlug: availability
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+To generate a search result, VTEX Intelligent Search takes into account the availability of each product found in the search. Available products will always have priority over unavailable products in the search results.
+
+When checking the availability of a product, VTEX Intelligent Search uses the **Show out of stock** field in the [Catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) to verify which products will be displayed even if they are unavailable. If the product configuration specifies that it should not be displayed when out of stock, the platform will not showcase the product. However, if the configuration indicates that the product should be displayed even when out of stock, the platform will position it at the end of the search results.
+
+VTEX Intelligent Search also checks if:
+
+- The product in question is active.
+- At least one product SKU is active.
+- The product category is active.
+- The product brand is active.
+- The **Show on website** field of the product is set to active.
+
+After checking the availability, the system combines items from your store, the [sellers](https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w)' catalog and the registered [trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) settings to determine the final price and stock. If any of these items have price and stock, the product is available. Whenever the stock and price of the product change, a new [indexing](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) is scheduled and this information is updated.
+
+Other factors, such as [Relevance](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) and [Merchandising rules](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), can be added to influence the result. However, availability will still be the most important criterion for the search result.
diff --git a/docs/tutorials/en/b2b-checkout-settings.md b/docs/tutorials/en/b2b-checkout-settings.md
new file mode 100644
index 000000000..66ece1b1b
--- /dev/null
+++ b/docs/tutorials/en/b2b-checkout-settings.md
@@ -0,0 +1,71 @@
+---
+title: 'B2B Checkout Settings'
+id: u7wG1SjmeCqXCSF2UsVok
+status: PUBLISHED
+createdAt: 2024-07-26T14:09:31.973Z
+updatedAt: 2024-07-26T19:06:26.485Z
+publishedAt: 2024-07-26T19:06:26.485Z
+firstPublishedAt: 2024-07-26T18:46:07.935Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-checkout-settings
+locale: en
+legacySlug: b2b-checkout-settings
+subcategory: 6sgdAY3pCuZ7qNws6gnzDX
+---
+
+The **B2B Checkout Settings** app is part of the VTEX solution [B2B Suite](https://help.vtex.com/en/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3), a group of apps that helps stores manage organizations, roles, and storefront permissions, in addition to checkout settings for B2B business relationships.
+
+B2B (business-to-business) transactions are more complex than B2C (business-to-consumer) transactions. B2B companies often deal with:
+
+- Large volume orders.
+- Customized contracts.
+- Specific payment conditions.
+- A diverse range of clients.
+
+In B2B commerce, you need to provide custom options at checkout, which may include:
+
+- Specific payment methods for each organization or cost center.
+- Preset addresses.
+- A field for entering the purchase order number.
+- Option for creating an order quote before actually completing the purchase.
+
+The **B2B Checkout Settings** app works together with other [B2B Suite](https://help.vtex.com/en/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3#aplicativo-configuracoes-de-checkout-b2b) apps to extend the checkout experience for users that belong to an organization.
+
+## Checkout user roles
+This app automatically checks the role of users that belong to an organization and communicates with the [B2B Organizations](https://help.vtex.com/en/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#aplicativo-organizacoes-b2b) app. It also confirms if the user has the required [permissions](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) to access the checkout by interacting with the [*Storefront Permissions*](https://help.vtex.com/en/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA) app.
+
+By default, any user with a role that allows storefront access can access the checkout, except those who have an organization buyer role. If a user tries to go to checkout without the required permission, they will see a "You don't have access to the checkout" notification message.
+
+## Cost center addresses
+The **B2B Checkout Settings** app communicates with the [B2B Organizations](https://help.vtex.com/en/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3#aplicativo-organizacoes-b2b) app and automatically lists the cost center addresses that are linked to the user at checkout.
+
+## Purchase order number field
+A purchase order (PO) is a business agreement between a buyer company and a B2B store that authorizes payment for products or services that will be delivered in the future within a specific period.
+
+Having a purchase order number allows B2B customers to pay for authorized purchases using that number. A purchase order is authorized and issued in advance by the company that is buying.
+
+**B2B Checkout Settings** allows you to enable an optional field — reference or purchase order number — where customers can enter that information during checkout.
+
+## Custom checkout settings for B2B
+B2B stores require specific checkout customizations. **B2B Checkout Settings** provides a custom checkout page that is ideal for this use case. This feature allows you to customize your checkout page to meet store needs.
+
+The section below describes how to configure the B2B Checkout Settings app.
+
+### Configuring the B2B Checkout Settings app
+Follow the steps below to customize your store checkout:
+
+<ol start="1">
+<li>In the VTEX Admin, go to <strong>Store Settings > Storefront > B2B Checkout Settings</strong>, or type <strong>B2B Checkout Settings</strong>  in the search bar at the top of the page.</li>
+<li>When you enable <code>Show purchase order (PO) number field</code>, the checkout page will include a field for entering the purchase order number during the purchase process.</li>
+<li>When you enable <code>Show Create a Quote button</code>, the checkout page will include a <code>Create Quote</code> button that allows creating a budget using the current cart items.</li>
+</ol>
+
+<div class = "alert alert-info">
+You should only enable the <code>Create Quote</code> button if the Order Quote app is installed in your store. For more information, check <a href="https://developers.vtex.com/docs/apps/vtex.b2b-quotes">B2B Quotes & Carts</a>.
+</div>
+
+<ol start="4">
+<li>Click <code>Save</code>.</li>
+</ol>
diff --git a/docs/tutorials/en/b2b-cost-center-management.md b/docs/tutorials/en/b2b-cost-center-management.md
new file mode 100644
index 000000000..12672e3b7
--- /dev/null
+++ b/docs/tutorials/en/b2b-cost-center-management.md
@@ -0,0 +1,101 @@
+---
+title: 'B2B cost center management'
+id: 2fjt1Layng8iKdvEEzRhuk
+status: PUBLISHED
+createdAt: 2024-07-25T10:55:43.882Z
+updatedAt: 2024-07-25T16:15:44.248Z
+publishedAt: 2024-07-25T16:15:44.248Z
+firstPublishedAt: 2024-07-25T13:38:42.344Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-cost-center-management
+locale: en
+legacySlug: b2b-cost-center-management
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+In the context of B2B organizations, cost centers represent business units or departments linked to a specific organization. This feature allows you to manage and associate relevant cost centers to your organization, making it easy to allocate and analyze financial expenses.
+
+## Adding a cost center
+To add a cost center through the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+To add a new cost center, follow these steps:
+
+<ol>
+  <li>Click the organization name.</li>
+  <li>Click the <strong>Cost Centers</strong> tab.</li>
+  <li>Click <code>New</code>.</li>
+  <li>
+    Complete the necessary fields about the cost center based on the information below:
+    <ul>
+      <li><strong>Cost center name</strong>: Name of the cost center associated with the organization.</li>
+      <li><strong>Phone number</strong>: Phone number for contacting the organization.</li>
+      <li><strong>Business document</strong>: Company registration number, tax identification number, VAT number, or other document.</li>
+      <li><strong>State registration</strong>: Company state registration number.</li>
+      <li><strong>Country</strong>: Country where the cost center is located.</li>
+      <li><strong>Postal code</strong>: Postal code of the cost center's address.</li>
+      <li><strong>Street</strong>: Name of the street where the cost center is located.</li>
+      <li><strong>Number</strong>: Number of the address where the cost center is located.</li>
+      <li><strong>Additional information</strong>: Extra details about the cost center's address.</li>
+      <li><strong>Neighborhood</strong>: Name of the neighborhood where the cost center is located.</li>
+      <li><strong>City</strong>: City where the cost center is located. This field is populated automatically based on the postal code entered.</li>
+      <li><strong>State</strong>: State where the cost center is located. This field is populated automatically based on the postal code entered.</li>
+      <li><strong>Recipient</strong>: Name of the person who will receive the orders at the address provided.</li>
+    </ul>
+  </li>
+  <li>Click the <code>Add</code> button.</li>
+  <li>Click <code>Save</code> at the top right of the page after making any changes.</li>
+</ol>
+
+## Cost center details
+To view, add or edit the details of a cost center in the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers >Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+To add a cost center, follow the steps below:
+
+1. Click the organization name.
+2. Click the **Cost Center** tab.
+3. Click `New` and complete the form fields.
+4. To add information, click on the cost center and fill in the fields.
+5. Click `Add`. 
+
+### Cost center form
+The form for viewing or editing the cost center is divided into the following sections:
+- [Information fields](#information-fields)
+- [Addresses](#addresses)
+- [Custom fields](#custom-fields)
+
+#### Information fields
+On this details page, you can view or edit the following fields:
+- **Cost center name:** Name of the cost center associated with the organization.
+- **Phone number:** Phone number for contacting the organization.
+- **Business document:** Company registration number, tax identification number, VAT number, or other document.
+- **State registration:** Company state registration number.
+
+#### Addresses
+To edit or delete an existing address, click<i class="fas fa-ellipsis-v" aria-hidden="true"></i> and select `Edit` or `Delete`.
+
+If you want to add a new delivery address associated with this cost center, follow these instructions:
+
+<ol>
+  <li>Click the <code>Add New Address</code> button.</li>
+  <li>
+    Complete the address details:
+    <ul>
+      <li><strong>Country</strong>: Country where the cost center is located.</li>
+      <li><strong>Postal code</strong>: Postal code of the cost center's address.</li>
+      <li><strong>Street</strong>: Name of the street where the cost center is located.</li>
+      <li><strong>Additional information</strong>: Extra details about the cost center's address.</li>
+      <li><strong>City</strong>: City where the cost center is located. This field is populated automatically based on the postal code entered.</li>
+      <li><strong>State</strong>: State where the cost center is located. This field is populated automatically based on the postal code entered.</li>
+      <li><strong>Recipient</strong>: Name of the person who will receive the orders at the address provided.</li>
+    </ul>
+  </li>
+  <li>Click the <code>Add</code> button.</li>
+  <li>Click <code>Save</code> at the top right of the page after making any changes.</li>
+  <li>Click <code>Delete</code> to remove the cost center.</li>
+</ol>
+
+#### Custom fields
+Custom fields allow users to add information relevant to the company. For more information, go to [Custom fields when adding an organization](https://help.vtex.com/en/tutorial/campos-personalizados-no-cadastro-de-organizacao--2MqEVusOvcbqagNwOuHA7f).
+
diff --git a/docs/tutorials/en/b2b-organization-general-settings.md b/docs/tutorials/en/b2b-organization-general-settings.md
new file mode 100644
index 000000000..3cbbbdea2
--- /dev/null
+++ b/docs/tutorials/en/b2b-organization-general-settings.md
@@ -0,0 +1,34 @@
+---
+title: 'B2B organization general settings'
+id: 6OSJHuiJJ7beRZaflNtzx5
+status: PUBLISHED
+createdAt: 2024-06-07T11:34:25.125Z
+updatedAt: 2024-06-07T11:45:51.047Z
+publishedAt: 2024-06-07T11:45:51.047Z
+firstPublishedAt: 2024-06-07T11:44:14.228Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-organization-general-settings
+locale: en
+legacySlug: b2b-organization-general-settings
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+The general settings page allows users to enter basic information for each B2B organization integrated with VTEX.
+
+In the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+1.	Click the organization name.
+
+2.	Click the General tab.
+
+3.	Complete the required information:
+    - Organization name: Name of the organization created.
+    - Trade name: Trade name used by the company.
+    - Status: Indicates whether the buyer organization is active.
+    - Custom fields: Contains additional fields for an organization.
+
+![Configurações gerais organizações - EN](//images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/c2c35b3eb340e1aa5603eafd55c0568a/Configura__es_gerais_organiza__es_-_EN.gif)
+
+Make sure you click the `Save` button at the top right corner to apply the changes.
diff --git a/docs/tutorials/en/b2b-overview.md b/docs/tutorials/en/b2b-overview.md
index 30397073d..6d40e90f5 100644
--- a/docs/tutorials/en/b2b-overview.md
+++ b/docs/tutorials/en/b2b-overview.md
@@ -3,8 +3,8 @@ title: 'B2B – Overview'
 id: 5vb9SNXhX2bZnkpAh7ADdC
 status: PUBLISHED
 createdAt: 2021-03-30T12:31:10.644Z
-updatedAt: 2021-05-11T17:43:13.209Z
-publishedAt: 2021-05-11T17:43:13.209Z
+updatedAt: 2024-05-10T13:56:48.012Z
+publishedAt: 2024-05-10T13:56:48.012Z
 firstPublishedAt: 2021-03-30T18:43:45.812Z
 contentType: tutorial
 productTeam: B2B
@@ -12,7 +12,7 @@ author: 7qy2DBsUp8U5P9lqV0JHfR
 slug: b2b-overview
 locale: en
 legacySlug: overview
-subcategory: 5N5GjDrKSycIQMeoS7CLtj
+subcategory: 1PSq4adEARlFaK5Mdv74Y7
 ---
 
 In ecommerce, business models are commonly divided into two groups: B2C (Business to Consumer) and B2B (Business to Business).
diff --git a/docs/tutorials/en/b2b-store-settings.md b/docs/tutorials/en/b2b-store-settings.md
new file mode 100644
index 000000000..97ef5ca54
--- /dev/null
+++ b/docs/tutorials/en/b2b-store-settings.md
@@ -0,0 +1,42 @@
+---
+title: 'B2B Store Settings'
+id: 7riBcnrOv4Cz7qMeACyVLm
+status: PUBLISHED
+createdAt: 2023-10-11T15:17:39.003Z
+updatedAt: 2024-06-06T16:33:44.798Z
+publishedAt: 2024-06-06T16:33:44.798Z
+firstPublishedAt: 2023-10-19T13:27:04.087Z
+contentType: tutorial
+productTeam: B2B
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: b2b-store-settings
+locale: en
+legacySlug: b2b-store-settings
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+On this page, you will see the instructions on how to configure the general settings for your B2B store.
+
+1. 	In your Admin, go to Apps > B2B Organizations & Cost Centers > Organization and click the Settings tab, or search for Settings under B2B Organizations & Cost Centers
+2. 	Configure the General Settings.
+
+- **Auto approve new organizations:** Select if you want to approve new organizations automatically.
+- **Make business document ready only:** By selecting this option, the customer will not be able to edit the business document field.
+- **Make state registration ready only:** By selecting this option, the customer will not be able to edit the state registration field.
+- **Use modal to switch company:** This option improves the user experience and simplifies store maintenance.
+- **Clear cart when switching company or logging in:** By selecting this setting, the cart will automatically empty when you switch stores or log into other accounts.
+## Payment Terms
+You can add payment methods by selecting them based on your business needs.  
+Example: debit card, credit card, promissory.
+![ B2B Store Settings - General Settings + Payment Terms](//images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/4efe4d1a37c7b2858fb8f528388e45e5/image1.jpg)
+
+## Price Tables
+You can add default prices for the stores you add. Learn more about Price Tables on [Pricing](https://developers.vtex.com/docs/guides/pricing-overview).
+
+## Trade Policies
+ ![ B2B - Políticas comerciais EN](//images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/7d93cbc41f2011d2ca1f1f3090458b2d/image2.jpg)
+You can directly link your store to trade policies and sales channels.
+
+1. In the **Available trade policies** list, click the trade policy you want to add to your store and then click `Add to Trade Policy`, which will then be displayed in the **Selected trade policies** list.
+2. After configuration, click `Save`.
+
diff --git a/docs/tutorials/en/b2b-suite-overview.md b/docs/tutorials/en/b2b-suite-overview.md
new file mode 100644
index 000000000..52646340c
--- /dev/null
+++ b/docs/tutorials/en/b2b-suite-overview.md
@@ -0,0 +1,93 @@
+---
+title: 'B2B Suite - Overview'
+id: 5eG6UfveWrai7looK0kVG3
+status: PUBLISHED
+createdAt: 2024-05-09T10:31:51.517Z
+updatedAt: 2024-05-10T18:37:56.917Z
+publishedAt: 2024-05-10T18:37:56.917Z
+firstPublishedAt: 2024-05-10T11:07:09.230Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-suite-overview
+locale: en
+legacySlug: b2b-suite-overview
+subcategory: 1PSq4adEARlFaK5Mdv74Y7
+---
+
+
+B2B Suite is a collection of [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) apps that helps stores manage organizations, permissions, and checkout settings in B2B scenarios, among other benefits. This is very important for streamlining the purchase flow, reducing costs, and providing a personalized shopping experience.
+
+B2B customers have different roles within your organization. They may be buyers, managers, or supervisors. Each role is associated with a different set of store permissions, depending on the actions that the user will need to perform.
+
+B2B Suite offers some key features:
+
+- **User groups:** Centralization of different users from the same company in a single organization allows unified management.
+
+- **Custom payment methods:** Set up customer-specific payment methods to meet individual needs.
+
+- **Product selection and specification:** Adapt product selection and price structure to tailor them to each customer, an essential element of B2B transactions.
+
+Offering custom options at checkout is key for meeting specific needs of B2B customers. B2B Suite allows the following customizations:
+
+- **Payment method selection:** Allow selecting specific payment methods by organization or cost center.
+
+- **Address autocomplete:** Automate address input to streamline checkout.
+
+- **Purchase order numbers:** Make it easier to include purchase order numbers, which are key for tracking and control.
+
+- **Order quotes:** Allow requesting order quotes at checkout.
+
+## Installing B2B Suite in your store
+
+To install B2B Suite, follow the steps below:
+
+1. On the VTEX Admin, go to **Apps > Extensions Hub > App Store**, or type **App Store** in the search bar at the top of the page.
+
+2. On the App Store page, find **B2B Suite** in the app gallery, or type **B2B Suite** in the search bar at the top of the page.
+
+3. Click Get App to install.
+
+![Instalação B2B Suite - EN](//images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/fbf0baa072a40dfdf9f89f5130eb82bf/Instala__o_B2B_Suite_-_EN.gif)
+
+## B2B Suite apps
+
+**B2B Suite** apps were developed to drive B2B operations. The main apps are described below.
+
+### Storefront Permissions
+
+Stores a predefined set of roles and permissions related to the pages and actions B2B users can view and take on the storefront. This is useful for stores that want to set specific permissions for users with different organizational roles.
+
+### Storefront Permissions UI
+
+This app provides an interface for the Storefront Permissions app, which allows VTEX Admin users to manage B2B features and the permissions of related apps directly on the Admin.
+
+### B2B Organizations
+
+Allows grouping B2B users into organizations that can be assigned specific payment methods, price tables, and product collections. This ensures that all organization users share the same commercial conditions.
+Each organization can be segmented into one or more cost centers that will have their own delivery addresses, which cost center users will be able to see at checkout.
+
+#### **Organization structure**
+
+- **Buyer organization:** A company or organization that makes purchases through the platform. It can have several users and access to specific pages related to its business needs.
+
+- **Users:** Members or employees of a B2B organization that are authorized to access and operate the B2B Suite platform on behalf of the organization. They have specific responsibilities related to the purchase process, such as placing orders, managing product catalogs, and approving transactions. Every user has restricted access to the platform resources based on their specific roles and permissions.
+
+- **Cost center:** A category or area within a B2B organization that tracks and attributes costs derived from specific company activities or departments. The company can use it to track costs from different business areas in more detail and with greater precision, which provides an efficient way for managing corporate expenses.
+
+### B2B Quotes & Carts
+
+Enables B2B users to create quotes and save carts, which can be shared with other organization members. Users with the appropriate store permissions can edit quotes to apply discounts or change item quantities, making the quotes ready for order placement.
+
+### B2B Checkout Settings
+
+Extends the checkout experience to users that are not members of B2B organizations. This app allows you to provide specific payment methods for the user's organization, autocompleted address based on the user's cost center, and add a purchase order number to the order. Customers can also create an order quote before placing an order.
+
+### B2B Orders History
+
+Provides a new Orders page under [My Account](https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh) that allows B2B users to view all previous orders placed by users from their organization or cost center, depending on their role.
+
+### B2B Admin Customers
+
+Provides additional customer information management capabilities on the VTEX Admin, allowing store administrators to create, edit, and search for customers.
+
diff --git a/docs/tutorials/en/b2b-trade-policies-overview.md b/docs/tutorials/en/b2b-trade-policies-overview.md
new file mode 100644
index 000000000..f64a5526d
--- /dev/null
+++ b/docs/tutorials/en/b2b-trade-policies-overview.md
@@ -0,0 +1,32 @@
+---
+title: 'B2B trade policies overview'
+id: sKrYjDJPBChgIxzYFpUvu
+status: PUBLISHED
+createdAt: 2024-07-05T11:20:38.780Z
+updatedAt: 2024-07-05T11:34:04.566Z
+publishedAt: 2024-07-05T11:34:04.566Z
+firstPublishedAt: 2024-07-05T11:34:04.566Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-trade-policies-overview
+locale: en
+legacySlug: b2b-trade-policies-overview
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Associating a [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) with the organization is key to a B2B operation. It allows you to apply specific rules on prices, discounts, and payment conditions, providing customized management of commercial relationships.
+
+The main objective of trade policies in B2B is to ensure that all transactions follow the trade policies the company has set, providing a consistent shopping experience aligned with business strategies. This includes:
+- Setting specific prices for products or groups of products, adapting them for different customers or market segments.
+- Configuring custom conditions, deadlines, and payment methods.
+- Implementing specific rules for calculating shipping costs and applying taxes based on the customer's location and profile.
+
+Implementing and managing these policies is important to ensure an efficient B2B operation aligned with the company's strategic objectives.
+
+## Associating trade policies
+1. In the VTEX Admin, go to **Apps > Organizations > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access its details page.
+3. Click the **Trade Policy** tab.
+4. Select the trade policy you want to associate with the organization.
+5. Click `Save`.
diff --git a/docs/tutorials/en/bank-reconciliations.md b/docs/tutorials/en/bank-reconciliations.md
index d541f52e1..eebe6d25d 100644
--- a/docs/tutorials/en/bank-reconciliations.md
+++ b/docs/tutorials/en/bank-reconciliations.md
@@ -36,7 +36,7 @@ After receiving the bank file and saving it on your machine, as mentioned above
 
 Once you select the file, the platform will begin to process it, and record in the history how many payments were reconciled, with success or error. Payments that have been successfully reconciled will update the status of the orders to Approved Payment.
 
-![upload-file-ret](https://images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7dd94c343503e88caa9430ba9319e39/uploadret_EN.JPG)
+![upload-file-ret](//images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7dd94c343503e88caa9430ba9319e39/uploadret_EN.JPG)
 
 ## View history
 
@@ -48,7 +48,7 @@ Among the details, it is possible to know the bank to which the slip belongs, th
 3. In **History**, click on one of the dates of the bank reconciliation operations performed.
 4. In **More Details**, click **Successfully Reconciled** or **Not Able to Reconcile** to check the details of the transactions carried out in a particular bank. 
 
-![historic-conciliation](https://images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/2e2ebac6f5612baa7935e99758612f66/historico_conciliacao_EN.jpg)
+![historic-conciliation](//images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/2e2ebac6f5612baa7935e99758612f66/historico_conciliacao_EN.jpg)
 
 ## Payclub
 
@@ -59,4 +59,4 @@ Here you can download the payments on the day they were made through redirection
 4. Select the date you want from the calendar.
 5. Click on **Download file**.
 
-![donwload-file-conciliation](https://images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/fa25f9754480cf2e41b72b70f95d5740/Download_Concilia____o_EN.JPG)
+![donwload-file-conciliation](//images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/fa25f9754480cf2e41b72b70f95d5740/Download_Concilia____o_EN.JPG)
diff --git a/docs/tutorials/en/banners.md b/docs/tutorials/en/banners.md
new file mode 100644
index 000000000..b128c9f86
--- /dev/null
+++ b/docs/tutorials/en/banners.md
@@ -0,0 +1,69 @@
+---
+title: 'Banners'
+id: 72XytEoeqOAOiH05oVF0pH
+status: PUBLISHED
+createdAt: 2024-06-27T16:30:55.610Z
+updatedAt: 2024-06-27T16:31:52.889Z
+publishedAt: 2024-06-27T16:31:52.889Z
+firstPublishedAt: 2024-06-27T16:31:52.889Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: banners
+locale: en
+legacySlug: banners
+subcategory: z6qcw06Z38YDu1fOcu9Jn
+---
+
+Banners is the Intelligent Search feature that displays banners, like promotional activities, on the search results page of the customer. The banner display is based on an analysis of the search context, including selected terms and filters, in the buyer’s journey. Banners can also be configured for each existing category in your catalog, as well as for departments and subcategories.
+
+Each customer group in your store, having its own profile, has its own interest. Your marketing campaigns need to take this into account in order to be effective and increase the sales conversion rate. The flexible settings of banners allow you to create marketing campaigns that are more creative, working your brand’s relationship with the public on an individual level.
+
+It is worth noting that these settings can be configured by terms as well as by filters used during the search. If a customer searches for “running shoes,” they can filter by different attributes (“size,” “type,” and “brand”) in the search results. When the “nike” filter is selected, if there is a banner of that brand in the store, it can be displayed to the customer (filter).
+
+Based upon the context captured by Intelligent Search, the system chooses the content, previously added, that is most relevant in that situation.
+
+For example, consider that the customer searches for "running shoes", and in the search results they can filter by several attributes ("size", "type" and "brand"). When selecting the “nike” filter, in case there is a campaign of this brand in the store, it can be displayed to the customer (filter). The customer can also be directed to a more specific promotion of Nike running shoes (term and filter), if you've created a campaign and linked it to the banner.
+
+## Banners listing page
+
+On VTEX Admin, the page **Storefront** > **Banners** shows the full list of registered banners and allows you to perform the following actions:
+
+* [Create a banner](#creating-a-banner)
+* [Search for banners](#searching-a-banner)
+* [Edit a banner](#editing-a-banner)
+* [Delete a banner](#deleting-a-banner) 
+
+![banners-intro-en](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
+
+The page shows the following information:
+
+| Column     | Description                      |
+| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Name       | Name that identifies the banner, defined when [Creating a banner](#creating-a-banner). |
+| Position   | Position of the banner on the search results page.                                                                                                                              |
+| Start Date | Date when the banner will start being available.                                                                                                                                |
+| End Date   | Date when the banner will stop being available.                                                                                                                                 |
+| Active     | Option that activates or deactivates the banner.                                                                                                                                |
+| Actions    | Ability to delete or edit the banner.                                                                                                                                           |
+
+## Creating a banner
+
+To add a new banner, click `New`. Learn more about all the information needed to create a Banner in [Configure Banners](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
+
+## Searching for banners
+
+To search for a banner, enter the name of the banner in the search bar.
+
+## Editing a banner
+
+You can edit the banner details by following the steps below.
+
+1. Click the pencil <i class="fas-solid fa-pencil"></i> button.
+2. Change the desired banner details.
+3. Click `Save`.
+
+## Deleting a banner
+
+You can delete a banner by clicking the trash <i class="fas-solid fa-trash-can"></i> button.
+
diff --git a/docs/tutorials/en/best-practices-against-virtual-attacks.md b/docs/tutorials/en/best-practices-against-virtual-attacks.md
index d6332623f..b2ab72f92 100644
--- a/docs/tutorials/en/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/en/best-practices-against-virtual-attacks.md
@@ -3,8 +3,8 @@ title: 'Best practices against virtual attacks'
 id: 191rpbF7UgrKapVCi1PCDE
 status: PUBLISHED
 createdAt: 2022-04-06T19:04:13.387Z
-updatedAt: 2022-06-10T14:24:42.121Z
-publishedAt: 2022-06-10T14:24:42.121Z
+updatedAt: 2024-06-18T20:41:01.987Z
+publishedAt: 2024-06-18T20:41:01.987Z
 firstPublishedAt: 2022-04-06T19:23:22.326Z
 contentType: tutorial
 productTeam: Reliability
@@ -19,21 +19,22 @@ VTEX offers different protections against possible attacks on stores. Still, the
 
 - [Anti-fraud solution](#anti-fraud-solution)
 - [Protection against transaction attacks](#protection-against-transaction-attacks)
-- [Using reCAPTCHA at Checkout](#using-recaptcha-at-checkout)
+- [reCAPTCHA v3 at Checkout](#recaptcha-v3-at-checkout)
+- [orderForm settings](#orderform-settings)
 - [Disabling password login](#disabling-password-login)
 
- <div class = "alert alert-info">
-These measures do not entirely eliminate the possibility of an attack, but may considerably reduce the likelihood, if properly employed.
+<div class = "alert alert-info">
+  <p>The measures in this guide do not entirely eliminate the possibility of an attack but may considerably reduce the likelihood of them happening if properly employed.</p>
 </div>
 
 ## Anti-fraud solution
 
-An anti-fraud solution is a system that specializes in online purchase analysis with the aim of identifying fraudulent operations. This system analyzes buyer behavioral data in ecommerce operations and prevents suspicious purchases from being made.
+Anti-fraud systems specialize in analyzing ecommerce purchases to identify fraudulent transactions. They analyze customers' behavioral data and prevent suspicious purchases from being made.
 
-Learn more about [anti-fraud systems](https://help.vtex.com/en/tutorial/what-is-anti-fraud#) and how to integrate them with the VTEX platform.
+Learn more about [anti-fraud systems](https://help.vtex.com/en/tutorial/what-is-anti-fraud--69SjFCc4rC6Ii0OMAeYAsG) and how to use them on VTEX.
 
 <div class="alert alert-warning">
-To increase security, set up your anti-fraud solution for all the payment methods available in your store.
+  <p>To increase security, set up your anti-fraud solution for all the payment methods available in your store.</p>
 </div>
 
 ## Protection against transaction attacks
@@ -41,23 +42,32 @@ To increase security, set up your anti-fraud solution for all the payment method
 To access the documentation on this topic, insert your VTEX [account name](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) below, click the button and login into the Admin panel.
 <iframe src="https://help.vtex.com/insertaccountname?id=62oQBmi7UZlYlgb0Ha1hZ3" title="Insert your account name and click the button." frameBorder="0" width="400" height="50"></iframe>
 
-## Using reCAPTCHA at checkout
+## reCAPTCHA v3 at Checkout
 
 reCAPTCHA is a user verification solution for orders paid by credit or debit card. It prevents the use of malware for fraudulent purposes.
 
-Learn more about how to set up this verification at your store's checkout in the article [Using reCAPTCHA at checkout](https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#).
+We recommend using [reCAPTCHA v3](https://help.vtex.com/en/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-v3), which uses a quality score instead of pop-up validation and is, therefore, harder to circumvent in such scenarios.
+
+Learn more about how to set up this verification at your store's checkout in the article [reCAPTCHA at checkout](https://help.vtex.com/en/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-v3). To implement reCAPTCHA V3 in a VTEX store, see the [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score) developer's guide.
 
 <div class = "alert alert-info">
-reCAPTCHA verification is enabled by default when store customers go through the steps of <a href=tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes>adding credit cards</a>, without having to be configured by the store.
+reCAPTCHA verification is enabled by default when store customers go through the steps of <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#credit-cards">adding credit cards</a>, without having to be configured by the store.
 </div>
 
+## orderForm settings
+
+To access the documentation on this topic, insert your VTEX [account name](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) below, click the button and login into the Admin panel.
+
+<iframe src="https://help.vtex.com/insertaccountname?id=7EAqNk48KP2QHnCxu856jT" title="Insert your account name and click the button." frameBorder="0" width="400" height="50"></iframe>
+
 ## Disabling password login
 
 If your store is still being attacked even with the mentioned resources enabled, we recommend disabling password login. This measure can be temporarily or permanently enabled, aiming to break the attack automation flow.
 
 To perform this configuration:
+
 1. Go to **Account settings** > **Authentication**.
 2. Disable the **password** field.
 
-Learn more about how to [manage authentication methods](https://help.vtex.com/en/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs#) for your store.
+Learn more about how to [manage authentication methods](https://help.vtex.com/en/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) for your store.
 
diff --git a/docs/tutorials/en/best-practices-application-keys.md b/docs/tutorials/en/best-practices-application-keys.md
index 99c7fa32a..d11d0ba0e 100644
--- a/docs/tutorials/en/best-practices-application-keys.md
+++ b/docs/tutorials/en/best-practices-application-keys.md
@@ -1,9 +1,9 @@
 ---
 title: 'Best practices for using application keys'
 id: 7b6nD1VMHa49aI5brlOvJm
-status: PUBLISHED
+status: CHANGED
 createdAt: 2022-10-04T21:36:57.185Z
-updatedAt: 2022-10-04T21:41:08.638Z
+updatedAt: 2024-03-19T14:22:43.610Z
 publishedAt: 2022-10-04T21:41:08.638Z
 firstPublishedAt: 2022-10-04T21:41:08.638Z
 contentType: tutorial
@@ -22,6 +22,7 @@ This type of credential is used to authenticate identities via API.
 </div>
 
 Improper handling of [application keys](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) can generate leaks, consequently leading to improper access scenarios. Below, you can see the best practices we recommend to manage the credentials you can implement to increase the security of your store.
+
 ## Rotate keys periodically
 
 It is recommended that you disable old keys and create new ones over time. By doing so, you make sure your [application keys](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) will have a certain duration.
diff --git a/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md b/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md
new file mode 100644
index 000000000..ceaf498f9
--- /dev/null
+++ b/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md
@@ -0,0 +1,74 @@
+---
+title: 'Best practices for accessing the store without www'
+id: tutorials_4278
+status: PUBLISHED
+createdAt: 2017-04-27T21:51:11.002Z
+updatedAt: 2024-01-23T17:50:54.783Z
+publishedAt: 2024-01-23T17:50:54.783Z
+firstPublishedAt: 2017-04-27T23:11:15.960Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: best-practices-for-accessing-the-store-without-www
+locale: en
+legacySlug: configuring-access-without-www
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+
+A store's main domain must have a subdomain, such as `www` or other. To access the store using a pure domain, such as `mystore.com`, which lacks a subdomain, a redirect is necessary.  This guide explains why you need a redirect and how to do it. Check out the following sections:
+
+* [Before you begin](#before-you-begin)
+* [Challenges of domains without subdomains](#challenges-of-domains-without-subdomains)
+* [Recommended solution: Redirect](#recommended-solution-redirect)
+* [Alternative solution: CNAME Flattening](#alternative-solution-cname-flattening)
+
+## Before you begin
+
+We recommend reading the following guides to understand how domains and DNS configuration work on VTEX:
+
+* [Configuring the store domain](https://help.vtex.com/en/tutorial/configuring-the-store-domain--tutorials_2450)
+* [How DNS configuration works on VTEX](https://help.vtex.com/en/tutorial/how-dns-configuration-works-on-vtex--2P5k3oMYOj7TgSK4Mrxmgy)
+
+## Limitations on DNS configuration for pure domains
+
+This section explores the complexity and challenges of configuring the DNS system for pure domains. Managing domains without subdomains requires special attention, mainly to preserve the function and integrity of the website without affecting crucial elements such as emails, security, and certificates.
+
+### Type A redirects for pure domains
+
+DNS configuration on VTEX must be done for the store's main domain; using pure domains is not recommended. A pure domain without a subdomain, also known as a _naked domain_ (for example, `mystore.com`, without `www`), implies creating a type A configuration (Address Record) in the DNS. The A record points the domain directly to a specific IP address.
+
+However, this type of configuration is not recommended. You cannot use a type A configuration pointing directly to an IP address due to the following reasons:
+
+* **Risk of unreachable site:** If a pure domain is configured with an A record pointing to a specific IP address and that IP address changes, the site may become inaccessible once the new IP is updated in the A record.
+*	**Poor performance:** If the pure domain points directly to a single IP address, site visitors worldwide are required to connect to that single server, regardless of their location. This could lead to a downgrade in performance, as long-distance visitors would have a slower experience.
+
+### CNAME redirects for pure domains
+
+CNAME redirects for pure domains should be avoided. A CNAME behaves similarly to a redirect in the DNS context: when someone accesses `www.mystore.com`, DNS automatically redirects them to `www.mystore.com.cdn.vtex.com`. However, according to the DNS protocol rules, a CNAME cannot coexist with any other type of DNS configuration for the same domain. This means that if we use a CNAME to redirect a website, all settings of the website must follow that redirect. You cannot redirect only some settings.
+
+This behavior conflicts with pure domains, as merchants often need to configure other features, such as MX records for emails, TXT records for security, CAA records for certificates, and NS and SOA records to demonstrate they control the pure domain.
+
+## Pure domains
+
+Given the DNS configuration limitations for pure domains, this section outlines the best practices to ensure your store is accessible without the www prefix.
+
+### Recommended solution: Redirects
+
+VTEX recommends always using the `www` or another subdomain when[ configuring the store's main domain](https://help.vtex.com/en/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450), to combine the use of CNAMEs and other settings. In this scenario, we recommend using redirects to access the address without `www` or other subdomains. Read the [Redirection from other addresses](https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ) article to learn how to configure redirects.
+
+Some DNS providers support CNAMEs for the pure domain (DNS Flattening). However, this option may not be offered by all providers. Therefore, we recommend the mandatory use of the subdomain to ensure that all the necessary features can coexist.
+
+### Alternative solution: CNAME Flattening
+
+By default, VTEX recommends using a `www` subdomain to avoid issues related to dynamic IPs in the CDN. However, some hosting companies and DNS services offer an alternative solution to get around this problem, called [CNAME Flattening](https://developers.cloudflare.com/dns/cname-flattening/).
+
+CNAME Flattening is a technique that allows you to associate a pure domain directly with a CNAME instead of an A record. This allows you to configure a pure domain (without a subdomain) to work with a CDN, even when the IPs change. However, this feature is not supported by all DNS providers.
+
+Some DNS providers, such as [Cloudflare](https://www.cloudflare.com/pt-br/), provide CNAME Flattening support. In this case, you can configure the pure domain with a CNAME pointing to the VTEX CDN service. This allows the pure domain to work similarly to the `www` subdomain and still benefit from the CDN.
+
+So, if you want to use a pure domain with a CDN in a specific configuration, the first step is to check whether your DNS provider supports CNAME Flattening. If so, you can configure the pure domain accordingly.
+
+<div class="alert alert-warning">
+  <p>When the DNS Flattening solution is used, it will have the same behavior as a<a href="https://help.vtex.com/en/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir"> reverse-proxy</a>. In this case, a TXT verification entry must be configured.</p>
+</div>
diff --git a/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md b/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md
new file mode 100644
index 000000000..2e40a95b6
--- /dev/null
+++ b/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md
@@ -0,0 +1,171 @@
+---
+title: 'Best practices for the success of your VTEX store'
+id: ItKyLqcRl9wNADMhYH8O4
+status: PUBLISHED
+createdAt: 2024-05-24T21:33:12.690Z
+updatedAt: 2024-05-24T22:42:51.899Z
+publishedAt: 2024-05-24T22:42:51.899Z
+firstPublishedAt: 2024-05-24T22:42:51.899Z
+contentType: tutorial
+productTeam: Others
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: best-practices-for-the-success-of-your-vtex-store
+locale: en
+legacySlug: best-practices-for-the-success-of-your-vtex-store
+subcategory: 4PeX73EGpmULh9Ip5F4XER
+---
+
+This article presents key practices to help you manage your VTEX store efficiently and enhance the scalability of your operation. The content is organized as follows:
+
+* **[Performance and security](#performance-and-security)**
+    * [Document your store architecture](#document-your-store-architecture)
+    * [Follow security guidelines](#follow-security-guidelines)
+    * [Manage access permission levels](#manage-access-permission-levels)
+    * [Explore our certified marketplaces and partners](#explore-our-certified-marketplaces-and-partners)
+* **[Updates and news](#updates-and-news)**
+    * [Stay updated with our latest launches and news](#stay-updated-with-our-latest-launches-and-news)
+    * [Receive platform status notifications](#receive-platform-status-notifications)
+    * [Explore our onboarding content](#explore-our-onboarding-content)
+* **[Community and support](#community-and-support)**
+    * [Join the VTEX Community](#join-the-vtex-community)
+    * [Learn best practices for VTEX Support requests](#learn-best-practices-for-vtex-support-requests)
+
+<div class = "alert alert-info">
+<b>Partner agencies</b><p>Several agencies and implementation partners have been certified by VTEX for demonstrating excellence and reliability in platform projects. Whether you need efficient implementation, customized store architecture, or ongoing infrastructure support, we recommend working with our partner agencies. To explore our partners, visit <a href="http://vtex.com">vtex.com</a> or the <a href="https://partnerportal.vtex.com/parceiros">Partner Portal</a> (available in Portuguese only).</p>
+</div>
+
+## Performance and security
+
+In this section, you will learn about best practices to enhance the performance efficiency and security of your operation.
+
+### Document your store architecture
+
+Ecommerce operations often involve integrating different systems and technologies. Keeping the [store architecture](https://help.vtex.com/en/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitetura-da-loja) documentation up-to-date is strategic for ensuring optimal performance from both the structure and the professionals involved.
+
+The main benefits of creating and maintaining updated documentation of the operation architecture include:
+
+* **Efficient implementation and maintenance:** It makes the initial phase of store development faster and future maintenance easier. Maintaining architecture documentation reduces reliance on experienced professionals and enhances collaboration between involved parties.
+* **Easier evolution:** Documenting the store architecture minimizes the friction associated with changes, which contributes to the capacity of the business for innovation.
+* **Well-informed decisions:** Understanding how the store works allows executive leaders to make informed decisions about infrastructure.
+* **Quick action on security issues:** Addressing security issues or vulnerabilities is more efficient when architecture documentation is available.
+* **Support optimization:** When support from our team or third parties is needed, sharing the architecture documentation streamlines communication between parties and increases the effectiveness of their efforts.
+
+<div class = "alert alert-info">
+For guidelines on documenting your store architecture, see the <a href="https://developers.vtex.com/docs/guides">Get started</a> page on our Developer Portal and learn about the <a href="https://assets.vtex.com/4524045/">interactive framework</a> of the VTEX platform.
+</div>
+
+### Follow security guidelines
+
+There are strategies to prevent and reduce store exposure to the risk of malicious attacks. Some of the main ones are:
+
+* **Anti-fraud systems:** Configure an [anti-fraud system](https://help.vtex.com/en/tutorial/what-is-anti-fraud) for all store payment methods.
+* **reCAPTCHA:** Use [reCAPTCHA](https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#) to prevent fraud involving fake user accounts created by malicious software.
+* **Authentication:** If your store has been experiencing recurrent attacks, consider disabling password login and opting for alternative [authentication](https://help.vtex.com/en/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) methods for your customers.
+
+<div class = "alert alert-info">
+For more information about preventive actions, see the article <a href="https://help.vtex.com/en/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE">Best practices against virtual attacks</a> and this <a href="https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470">post</a> on VTEX Community (available in Portuguese).
+</div>
+
+### Manage access permission levels
+
+[VTEX store security](https://help.vtex.com/en/subcategory/seguranca-para-lojistas--6uJgdHqWf1Mo0rUfgxseTn) offers several preventive measures and [best practices](https://help.vtex.com/en/tutorial/boas-praticas-para-evitar-golpes-que-utilizam-a-marca-da-vtex--6uPwUr2Fnj2m3TM4hAj2Ec) that can significantly enhance the security of your business. One of the main ones is managing access roles in your VTEX Admin.
+
+Some key recommendations for VTEX [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) are:
+
+* **Grant minimal permissions:** Create roles considering the minimum level of permissions necessary for users to perform their tasks. Beyond the [predefined roles](https://help.vtex.com/en/tutorial/perfis-de-acesso), you can create [customized roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso). Limiting third-party access to critical content minimizes the risk of unwanted access, data leakage, or other harmful scenarios. 
+* **Re-evaluate roles:** [Manage users](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) periodically and ensure that each has an appropriate level of permission. It is crucial to delete roles from employees or vendors who are no longer in your business. Proactively and regularly reviewing users help prevent security breaches caused by improper access.
+* **Control app key permissions:** [App keys](https://help.vtex.com/en/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) used in integrations can also access your VTEX store. Please follow our [Best practices for using application keys](https://help.vtex.com/en/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm).
+* **Restrict VTEX Admin access to corporate domains:** Using corporate domains adds a layer of security, preventing unauthorized access to your store. Limiting access to only use corporate email addresses mitigates the risk of data leaks (intentional or accidental), enhances protection against phishing, and improves the traceability of audit activities.
+* **Enable two-factor authentication (2FA):** [2FA](https://help.vtex.com/en/tutorial/habilitar-login-por-autenticacao-de-2-fatores--4Ae1fcQi12g8u4SkQKCqWQ) adds an additional layer of security, protecting access to the store even if the secrecy of your password is compromised. This feature is particularly important for users with access to sensitive information and settings.
+
+### Explore our certified marketplaces and partners
+
+The VTEX platform architecture allows stores to act both as [marketplaces and sellers](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402), and on [Marketplaces and Integrations](https://help.vtex.com/en/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V) they can discover and communicate with each other. In addition, VTEX offers native integrations with several [certified marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-marketplace) and [partners](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-marketplaces-partners) (such as Amazon and Mercado Libre).
+
+If you want to develop an integration with an external marketplace, see the article [External Marketplace](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide).
+
+## Updates and news
+
+In this section, you can find best practices for monitoring platform status and VTEX product innovations.
+
+### Stay updated with our latest launches and news
+
+The VTEX platform is constantly evolving, and a great way for you and your team to stay up to date with new launches is by following our documentation portals:
+
+| **Documentation Portal** | **Location** |
+| :---: | :---: |
+| Help Center | Page: [News](https://help.vtex.com/en/announcements) |
+| Developer Portal | Page: [Release Notes](https://developers.vtex.com/updates/release-notes) |
+
+Some of the main advantages of staying up to date are:
+
+* Keep your operation aligned with the latest launches to use the platform to its full potential and maintain your competitive advantage in the market.
+* Understand how new features work to ensure a faster and seamless implementation.
+* Configure updates to increase store security, as we continually innovate to protect your business operation.
+* If you need to contact support, familiarity with new features allows you to interact more efficiently with our support team, resulting in quicker solutions.
+
+<div class = "alert alert-info">
+The announcements from the Help Center <b>News</b> page are also accessible through your VTEX Admin. To view this content, click the bell icon at the top of the page.
+</div>
+
+### Receive platform status notifications
+
+When an incident occurs on the platform, VTEX is committed to acting in the most transparent and informative way possible.
+
+For this purpose, VTEX provides a [platform status page](https://status.vtex.com/). On this page, you can monitor the platform's stability in real time, as well as view scheduled maintenance. You can subscribe to the page to receive notifications via:
+
+* Email
+* [RSS feed](https://rss.com/blog/how-do-rss-feeds-work/)
+* [Slack](https://slack.com/)
+
+<div class = "alert alert-info">
+For moreninformation about the platform status page, see the article <a href="https://</a>help.vtex.com/en/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ">VTEX Status Page</a>.
+</div>
+
+### Explore our onboarding content
+
+VTEX offers a wide range of features and products, and it's important to familiarize yourself with them to determine which resources are best suited to your business needs.
+
+For this reason, we provide different types of onboarding material about the platform:
+
+| **Format** | **Location** | **Language** |
+| :---: | :--- | :--- |
+| Documentation | Help Center: [Onboarding guide](https://help.vtex.com/en/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | English, Spanish, and Portuguese. |
+| Videos | Site: [Onboarding VTEX](https://sites.google.com/vtex.com.br/onboardingvtex/trilha) | Portuguese only. |
+| Demos and ebooks | Site: [vtex.com](http://vtex.com) | Each piece of content is available in English, Spanish, or Portuguese, depending on your location. |
+
+## Community and support
+
+In this section, you will learn about best practices for optimizing your support network in the VTEX ecosystem.
+
+### Join the VTEX Community
+
+The [VTEX Community](https://community.vtex.com/) is a publicly accessible space where our specialists, customers, implementation partners, and the entire VTEX ecosystem collaborate, share knowledge, and support each other.
+
+The collaborative nature of our community is an important source of support at VTEX, and some of its main advantages are:
+
+* **Fast responses:** The VTEX Community operates 24/7, with members from different countries. Your questions can be answered at any time, not only by VTEX professionals, but also by others who may have experienced similar situations and can offer insights.
+* **Diverse perspectives:** Interacting with various members of the community provides access to different perspectives and problem-solving approaches. This diversity often results in innovative solutions.
+* **Knowledge sharing:** Our community has become a sort of virtual library, where you can find tips, best practices, and a variety of practical content to help you manage your VTEX store effectively.
+* **Professional and business networking:** Being active in the community contributes to developing your professional network.
+
+### Learn best practices for VTEX support requests
+
+In some cases, submitting a ticket to VTEX Support is necessary, such as those involving sensitive information or urgent needs. 
+
+Our specialists are prepared to address your questions and provide a positive experience throughout the process. However, you can help ensure that support is as quick and effective as possible.
+
+These are the [best practices for opening a ticket with VTEX Support](https://help.vtex.com/en/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX), in order to achieve a faster and more objective service:
+
+* Provide detailed information about the reason for opening the ticket.
+* Describe the situation or issue clearly, precisely, and objectively (especially for urgent matters).
+* Maintain clear and proactive communication throughout the interaction.
+* When possible, attach screenshots and relevant logs.
+* When possible, explain how to reproduce the error or issue.
+
+These are some of the most important recommendations. For more information, see the article [Best practices for opening a ticket with VTEX Support](https://help.vtex.com/en/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX).
+
+<div class = "alert alert-info">
+For an overview of our ticket support system, check the <a href="https://help.vtex.com/en/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">VTEX Support</a> track in the <b>Onboarding guide</b>.
+</div>
+
diff --git a/docs/tutorials/en/best-practices-for-using-images-in-the-catalog.md b/docs/tutorials/en/best-practices-for-using-images-in-the-catalog.md
index c7362d312..318553889 100644
--- a/docs/tutorials/en/best-practices-for-using-images-in-the-catalog.md
+++ b/docs/tutorials/en/best-practices-for-using-images-in-the-catalog.md
@@ -3,8 +3,8 @@ title: 'Best practices for using images in the Catalog'
 id: 738K2yfq5U86kUI2k4AQIk
 status: PUBLISHED
 createdAt: 2018-01-30T14:45:53.934Z
-updatedAt: 2022-07-07T15:32:57.069Z
-publishedAt: 2022-07-07T15:32:57.069Z
+updatedAt: 2024-01-23T15:54:22.159Z
+publishedAt: 2024-01-23T15:54:22.159Z
 firstPublishedAt: 2018-01-31T18:36:10.087Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/en/best-practices-on-spf.md b/docs/tutorials/en/best-practices-on-spf.md
index 617771d53..e8c0d63a3 100644
--- a/docs/tutorials/en/best-practices-on-spf.md
+++ b/docs/tutorials/en/best-practices-on-spf.md
@@ -3,8 +3,8 @@ title: 'Best Practices on Sender Policy Framework (SPF)'
 id: 42t0lkl2VyC6Yewc4wA6wI
 status: PUBLISHED
 createdAt: 2017-08-09T16:58:00.716Z
-updatedAt: 2023-03-10T18:49:18.935Z
-publishedAt: 2023-03-10T18:49:18.935Z
+updatedAt: 2024-02-22T18:11:49.023Z
+publishedAt: 2024-02-22T18:11:49.023Z
 firstPublishedAt: 2017-08-10T00:04:19.239Z
 contentType: tutorial
 productTeam: Reliability
@@ -25,13 +25,13 @@ For syntax details, we recommend that you read the documentation [Sender Policy
 
 In the DNS manager, the SPF will be a TXT entry in the domain root (ex.: site.com) with the following format:
 
-`site.com. IN TXT “v=spf1 a mx ip4:192.0.2.32/27 include:provedor.com -all”`
+`site.com. IN TXT “v=spf1 a mx ip4:192.0.2.32/27 include:provedor.com ~all”`
 
 We can divide the policy above into the following sections:
 
 - `v=spf1`: required prefix.
 - `a mx ip4:192.0.2.32/27 include:provedor.com`: authorized senders.
-- `-all`: condition for including or excluding senders except the ones previously declared.
+- `~all`: condition for including or excluding senders except the ones previously declared.
 
 When applied for authorized senders, the above rules mean a server can send messages on behalf of the given domain (site.com) if:
 
@@ -44,10 +44,10 @@ The inclusion or exclusion condition can have the following values:
 
 - `+all`: any sender will be authorized.
 - `-all`: any sender (except the declared ones) will be rejected.
-- `~all`: another verification step will be required to reject unauthorized senders.
+- `~all`: another verification step will be required to reject unauthorized senders. (Recommended)
 - `?all`: the verification of unauthorized senders will be disregarded.
 
-We recommend using -all, which has a better deliverability rate. Make sure all domains sending messages on your behalf are properly configured. Otherwise, messages will not be delivered.
+We recommend using `~all`, which has a better deliverability rate. If there is an unauthorized sender, this option does not stop the sending of the email, but informs that the SPF validation failed.
 
 ## SPF in the VTEX context
 VTEX uses the `include:amazonses.com` SPF. This is Amazon's transactional email sending service, used in the default sender (VTEX type) of Message Center.
diff --git a/docs/tutorials/en/best-practices-to-avoid-scams-using-the-vtex-brand.md b/docs/tutorials/en/best-practices-to-avoid-scams-using-the-vtex-brand.md
new file mode 100644
index 000000000..816c45144
--- /dev/null
+++ b/docs/tutorials/en/best-practices-to-avoid-scams-using-the-vtex-brand.md
@@ -0,0 +1,53 @@
+---
+title: 'Best practices to avoid scams using the VTEX brand'
+id: 6uPwUr2Fnj2m3TM4hAj2Ec
+status: PUBLISHED
+createdAt: 2024-03-19T14:09:14.448Z
+updatedAt: 2024-03-19T14:21:08.209Z
+publishedAt: 2024-03-19T14:21:08.209Z
+firstPublishedAt: 2024-03-19T14:21:08.209Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: best-practices-to-avoid-scams-using-the-vtex-brand
+locale: en
+legacySlug: best-practices-to-avoid-scams-using-the-vtex-brand
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+As a merchant, it's crucial to be aware of scams that might misuse the VTEX brand in fraudulent ways. In this article, we'll share some recommendations to help you identify and avoid these scams.
+
+Protecting your online store from scams using the VTEX brand requires constant vigilance and caution. By following the guidelines in this guide and staying alert to potential threats, you will be contributing to the security and integrity of your online business.
+
+## Verify the authenticity of the communication
+
+VTEX generally communicates with its clients through official channels:
+
+- Pop-up messages in the VTEX Admin
+- Business emails
+- Announcements in the [Help Center](https://help.vtex.com/) or[ Developer Portal](https://developers.vtex.com/)
+- Posts on the official VTEX [website](https://vtex.com/us-en/) or social networks
+
+Be wary of any communication requesting confidential information or suspicious actions, especially from unverified sources.
+
+Scammers often try to convince you to act immediately, giving you a short deadline or suggesting there's a risk involved. So stay calm and always think before clicking or providing any information.
+
+## Protect login credentials
+
+Keep [application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet), [user tokens](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens), and VTEX [login](https://help.vtex.com/en/tutorial/authentication--21CkKHLKP1o41lUpGhuRUs#login) credentials such as email, password, and access codes safe. Never share personal and confidential information, store data, codes, or any other sensitive information with third parties.
+
+Scammers may try to get access to your account to perform fraudulent activities on behalf of your company. Before taking action or providing any information, ensure that the communication is indeed from VTEX.
+
+## Identify misleading offers
+
+If you receive offers claiming to be part of an incentive program in VTEX's name, do not follow the sender's instructions. VTEX does not offer incentive programs or request payments from individuals or companies outside the platform's service agreement terms.
+
+Always check the URL before clicking a link or accessing a page to make sure it is one of VTEX's [official communication channels](#verify-the-authenticity-of-the-communication). If you have any questions, contact our [Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe) team.
+
+## Check VTEX's security resources
+
+VTEX offers security resources and guidelines to help its clients protect their online stores from fraud and scams. Familiarize yourself with these resources and use them to strengthen your store's security. Learn more about our security practices in [Security - VTEX](https://vtex.com/us-en/security/).
+
+## Report suspicious activities
+
+If you suspect fraudulent activity using the VTEX brand, report it immediately to [VTEX Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe). The VTEX Security team will then investigate the matter and take the necessary actions to prevent and combat potential fraud.
diff --git a/docs/tutorials/en/beta-price-configuration.md b/docs/tutorials/en/beta-price-configuration.md
index 7ecbe2899..48616b423 100644
--- a/docs/tutorials/en/beta-price-configuration.md
+++ b/docs/tutorials/en/beta-price-configuration.md
@@ -73,11 +73,11 @@ To create a new rule, follow the steps below:
 
   b. **Activate in specific conditions:** the price table will be activated according to the conditions set in the rule. See the configuration possibilities on the following images:
 
-  ![config-preco-EN](https://images.ctfassets.net/alneenqid6w5/2sDqS10pMIv7tmDTgP96si/10028ff45ae241863445061a871e98dd/config-preco-EN.png)
+  ![config-preco-EN](//images.ctfassets.net/alneenqid6w5/2sDqS10pMIv7tmDTgP96si/10028ff45ae241863445061a871e98dd/config-preco-EN.png)
 
-  ![config-preco2-EN](https://images.ctfassets.net/alneenqid6w5/13jaqi9EY1SZ7CdShElb7r/e9ce4f8ca7b2322aacd556fbf5f7cd50/config-preco2-EN.png)
+  ![config-preco2-EN](//images.ctfassets.net/alneenqid6w5/13jaqi9EY1SZ7CdShElb7r/e9ce4f8ca7b2322aacd556fbf5f7cd50/config-preco2-EN.png)
 
-![config-preco3-EN](https://images.ctfassets.net/alneenqid6w5/3EC7hLAQO43LoPlijbXFKM/42d35e6f525408f2920da790b08bd88d/config-preco3-EN.png)
+![config-preco3-EN](//images.ctfassets.net/alneenqid6w5/3EC7hLAQO43LoPlijbXFKM/42d35e6f525408f2920da790b08bd88d/config-preco3-EN.png)
 
   7. Click on **Confirm**.
 
diff --git a/docs/tutorials/en/billing-module-overview.md b/docs/tutorials/en/billing-module-overview.md
index 5fbdf33b8..7b932a39b 100644
--- a/docs/tutorials/en/billing-module-overview.md
+++ b/docs/tutorials/en/billing-module-overview.md
@@ -23,7 +23,7 @@ To access this section, click on your **profile avatar**, which can be identifie
 Only users with the access profiles of <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> or with <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> resources linked to their access profile can view this section of the VTEX Admin.
   </div>     
 
-![Admin v4 Faturas menu EN](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/efc4c8a58bed888f975fa5aa2b0f2fad/Admin_v4_Faturas_menu_EN.jpg)
+![Admin v4 Faturas menu EN](//images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/efc4c8a58bed888f975fa5aa2b0f2fad/Admin_v4_Faturas_menu_EN.jpg)
 
 See below for more details on the different sections and pages of this feature.
 
diff --git a/docs/tutorials/en/brands.md b/docs/tutorials/en/brands.md
index 64cc2c792..6dafd3dfa 100644
--- a/docs/tutorials/en/brands.md
+++ b/docs/tutorials/en/brands.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Brands** page allows you to view, manage and add brands on Seller Portal. To access the page on VTEX Admin, go to **Catalog** > **Brands**.
 
-![brands-en](https://images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/a5d64115e686cda5ebe5e11a8c8b7aa8/brands-en.PNG)
+![brands-en](//images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/a5d64115e686cda5ebe5e11a8c8b7aa8/brands-en.PNG)
 
 ## Creating a Brand
 To create a new brand, click on the `Create brand` button. Fill in the fields on the __New brand__ modal according to the information below.
diff --git a/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md b/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md
index 234590622..91e953659 100644
--- a/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md
+++ b/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md
@@ -25,7 +25,7 @@ Open up your favorite text editor and navigate to your project’s folder.
 
 Adding a simple `“admin/“` to the beginning of the page name as well as to the route path should make it look like this:
 
-![2 pages](https://images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
+![2 pages](//images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
 
 ## Fixing dependencies
 
@@ -33,7 +33,7 @@ We must now navigate to the manifest.json file where we list all of our dependan
 
 Let’s add `vtex.admin: “1.x”` to out dependencies. VTEX IO is strict about requiring explicit version.
 
-![3 manifest](https://images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
+![3 manifest](//images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
 
 ## The final touches
 
@@ -47,5 +47,5 @@ Navigate to index.js and add the `componentDidMount()` lifecycle method above th
 
 Your React application should now have the proper URL path, the correct dependencies and an index.js that makes use of React’s lifecycle method to communicate with VTEX (through `window.postmessage`) to terminate the loading process.
 
-![4 final touches](https://images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
-![5 completo](https://images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
+![4 final touches](//images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
+![5 completo](//images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
diff --git a/docs/tutorials/en/buy-one-get-one.md b/docs/tutorials/en/buy-one-get-one.md
index b0e0f8d0f..8e2ea500d 100644
--- a/docs/tutorials/en/buy-one-get-one.md
+++ b/docs/tutorials/en/buy-one-get-one.md
@@ -3,8 +3,8 @@ title: 'How the Buy One Get One (BoGo) promotion works'
 id: tutorials_322
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:41.148Z
-updatedAt: 2021-12-13T17:23:17.182Z
-publishedAt: 2021-12-13T17:23:17.182Z
+updatedAt: 2024-02-19T11:48:37.254Z
+publishedAt: 2024-02-19T11:48:37.254Z
 firstPublishedAt: 2017-04-27T23:03:14.992Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,46 +15,111 @@ legacySlug: buy-win
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-This kind of promotion is used to offer free shipping or a free gift if a determined product is purchased. For example, "buy a TV and get free shipping" or "buy a video game and win a game."
 
-## What is the general data of this promotion?
+Buy One Get One promotions are used to offer free shipping or a gift for buying a specific product. For example, "Buy a TV and get free shipping" or "Buy a video game and get a game for free".
 
-- __Name__
-- __Name of the promotion__
-- __Status__
-- __Enable or disable the promotion__
-- __Internal description of the promotion__: This field is used for your store's internal communication, in order to explain if the promotion is the result of a campaign, stock clearance, etc.
-- __Expiration Date__: Promotion start and end date. A future date and/or time can be used to launch the promotion on the website, where it will have a scheduled status until the set date and time arrive. As long as the promotion is valid, it will have the enabled status and, at the end of the set date and time, the status will automatically change to disabled.
-- __Specify days of the week for the enabling__: This option is displayed as a check box. When selected, it provides seven other check boxes, that represent the days of the week when the promotion can be offered. If you want the promotion to be offered on every day of the week, don't select this option.
-- __What is the type and value of the discount?__; 
-  1. __Maximum Price per Item__: Sets the maximum price for each item.
-  2. __Free Shipping__: Total discount on shipping fees.
-  3. __Gift__: Total discount on the value of a product defined as gift. Selecting this option will open other fields to enter a SKU, a box to activate the gift multiplier and the amount of product defined as gifts. The SKU can be entered by name or ID, being also possible to enter more than one. 
-To learn how to set up this type of discount, have a look at the article on [Setup Buy and Win promotion gift for a Specific SKU](/en/tutorial/how-to-set-a-buy-and-win-promotion-gift-for-a-specific-sku).
-- __Discount highlight__: Inserts a flag with the name of the promotion. Used on the product's window and page. This flag will only be inserted if you use the correct promotion display control on the template. <vtex.cmc:discountHightLight>;
-- __Seller__: Selects the seller that will offer the discount. Having a multistore will make all the sellers registered to your account appear. This option allows you to assign a different discount for each seller.
-- __Commercial Policy__: Selects the Commercial Policies that will offer the discount. All the policies registered in `E-Commerce > Marketplace > Commercial Policy` will be listed. This option allows you to offer a different discount for each policy.
+In this article, we'll explain the steps required to set up a Buy One Get One promotion:
 
-## Buy One Get One
+1. [Promotion overview](#1-promotion-overview)
+    - [Restrict this promotion to seller products](#restrict-this-promotion-to-seller-products)
+    - [Trade policy](#trade-policy)
+2. [Buy One, Get One](#2-buy-one-get-one)
+3. [Conditions for the promotion to be valid](#3-conditions-for-the-promotions-to-be-valid)
+4. [Restrictions and limitations of use](#4-restrictions-and-limitations-of-use)
 
-- __Collections__: enter the name of the product collection you wish to relate to this type of discount. It is possible to enter more than one name. The promotion will only be applied to products that are in the collections registered in this field.
-- __SKUs__: enter the name or Id of the SKUs to which you want to apply the discount. You can import a list of SKUs, which must be saved as a text file (.txt), with each Id on a different line. 
+# Creating a promotion
+In the VTEX Admin, go to Promotions > Promotions, or type Promotions in the search bar at the top of the page.
 
-__Notice__: if products are not limited by collection or SKU, the platform will not allow the creation of the promotion.
+1. Click the `Create Promotion` button.
+2. Select the **Buy One Get One** option.
+3. Complete the promotion fields.
+4. Click `Save`.
 
-__Notice__: the maximum number of registered SKUs for this promotion is 100.
+# 1. Promotion overview
+In this section, we provide information on the promotion overview.
+- **Name:** Promotion name. Required field.
+- **Status:** Activates or deactivates the promotion.
+- **Description:** This field is for internal communication in your store to indicate the purpose of the promotion, such as a campaign, a clearance sale, etc.
+- **Expiration date:** Start and end date and time of the promotion. You can use a future date and/or time for the promotion to start on your website. If configured this way, the promotion status will be displayed as follows:
+    - Scheduled: Before the selected start date and time.
+    - Active: During the scheduled promotion period.
+    - Inactive: After the selected end date and time.
+- **Use recurrence settings:** By selecting this option, you can configure the recurrence, such as the weekday and time.
+- **Type and amount of discount:** Allows you to select one of the options below:
+    1. **Maximum price per item:** Sets the maximum price for each item in the order.
+    2. **Free shipping:** Full discount on shipping costs.
+    3. **Gift:** Full discount on the product amount set as a gift. By selecting this option, you can indicate the SKU (by name or ID) that will be considered a gift, choose if you want to activate the [gift multiplier](https://help.vtex.com/en/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK), and the maximum number of products that can be used as gifts in the promotion. For more information on this type of discount, check [How to set a Buy One Get One promotion (gift) for a specific SKU](https://help.vtex.com/en/tutorial/configurar-promocao-compre-e-ganhe-para-um-sku-especifico).
+- **Additional information (optional):** Allows you to add name and value details to the promotion.
+- **Promotion is highlighted:** Adds a tag with the promotion name,  which is displayed in the window display and on the product page. This tag will only be added if you use the right promotion display control in the template. `<vtex.cmc:discountHightLight>`.
 
-- __Product Threshold__: sets the number of products required in the cart in order to grant the discount. This field is mandatory.
+![Promotion Overview](//images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/fb5019d7359026929f45631e94e2f454/Promotion_Overview.png)
 
-## What are the conditions for the promotion to be valid?
+## Restrict this promotion to seller products
 
-- __BIN Restriction__: defines which credit cards can benefit from this promotion.
-- __Customer Cluster__: you can use an existing field in the __CL__ Data Entity to create a threshold. Example: `age = 25`
-- __Type of Shipping__: the discount will be granted if the type of shipping is the same as the one registered.
-- __Utm\_source__: the discount will be granted if browsing is performed with the utm\_source that contains the registered value.
-- __Utm\_campaign__: The discount will be granted if browsing is performed with the utm\_campaign that contains the registered value.
+In this section, you can determine to which sellers the promotion will apply. You can specify the sellers you want to include or exclude from the discount.
 
-## Restrictions and limitations of use
+- Equal to: Select the sellers you want to include.
+- Different from: Select the sellers you want to exclude.
 
-- __Only for the same items__: The discount will only be applied per SKU, once each one has a minimum registered amount. If you don't check this option, the discount will be applied to products from the collection or from the list of SKUs, without the need of having the minimum registered amount in the cart for each of them. The sum of these products will be considered instead.
-- __Allow promotion stockpiling__: Allows that more than one promotion with the same type of discount be granted at the same time.
+For the promotion to be valid for all sellers, leave the field blank.
+
+<div class = "alert alert-warning">
+  <p>It is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:</p><ol>1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.</ol><ol>2. Leave the field blank.  In this way, all sellers will be included in the promotion.</ol>
+</div>
+
+![Restrict this promotion to seller products](//images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/32b26e784595d4551700c022fc539598/Restrict_this_promotion_to_seller_products.png)
+
+## Trade policy
+
+In this section, you can set the trade policies valid for the promotion. You can include or exclude trade policies from the discount.
+
+- **Equal to:**  Select the trade policies you want to include.
+- **Different from:** Select the trade policies you want to exclude.
+- **Provided by me (my store):** Select trade policies with products from your store. You can select more than one trade policy.
+- **Delivered by me (other stores):** Select trade policies in which your products are available in third-party stores. You can select more than one trade policy.
+
+For the promotion to be valid for all trade policies, leave the selection empty.
+
+![Trade Policy](//images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/2d378d9c081945a7128525036ed1f9e4/Trade_policy.png)
+
+# 2. Buy One Get One
+
+In this section, you can define the collections, SKUs, and minimum quantity for the promotion to apply.
+
+- **Collections:** Select one or more product collections you want to give this type of discount. The promotion will only be applied to products in the collections listed in this field.
+- **SKUs:** Allows you to enter the SKU name or ID to which the discount will apply. You can import a list of SKUs that must be saved in a text file (**.txt**), with each ID listed on a different row.
+- **Minimum quantity:** Allows you to define the minimum quantity of products that must be added to the cart for the discount to be applied. This is a required field.
+
+<div class = "alert alert-warning">
+<p>The promotion will not be created if the Collections or SKUs fields are not completed.<p>
+</div>
+
+<div class = "alert alert-warning">
+<p>A Buy One Get One promotion can be created with a maximum of 100 different SKUs at the same time.<p>
+</div>
+
+![Buy One Get One](//images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c521b34d5694bf3712f5450f32839a91/Buy_One_Get_One.png)
+
+# 3. Conditions for the promotion to be valid
+
+In this section, we will detail the conditions you must apply for a promotion to be valid.
+
+- **Use restriction BINs:** Allows you to activate or deactivate the BIN restriction, limiting the credit cards used in the promotion. You can import a list of BINs, which must be saved in a text file (.txt) with each BIN listed on a different row.
+- **Customer cluster:** Allows you to activate or deactivate the customer cluster. When activated, you can choose a customer cluster created via [Master Data](https://help.vtex.com/en/tutorial/como-criar-um-cluster-de-clientes).
+- **Shipping method:** Allows you to choose if the promotion will be applied to one or more shipping methods. When activated, choose a shipping method; when deactivated, you can apply the discount to the cheapest shipping method.
+- **Payment method:** Allows you to choose if the promotion will be applied to one or more of the selected payment methods.
+- **Utm_source:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion.
+- **Utm_campaign:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion.
+
+![What are the conditions for the promotion to be valid?](//images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/935d35fb86b2e6931c238d60e14f2872/What_are_the_conditions_for_the_promotion_to_be_valid.png)
+
+# 4. Restrictions and limitations of use
+
+In this section, you will find important information about the promotion conditions and restrictions.
+
+- How many times will this promotion be applied in your store: Allows you to restrict the promotion in your store to a specific limit or use it unlimitedly.
+- How many times per customer will this promotion be applied in your store: Allows you to restrict the promotion in your store to each customer for a specific limit or to use it unlimitedly.
+- Only for the same items: If this option is activated, the promotion is only applied if the minimum quantity of items (previously added) is reached using the same SKU in the cart. If this option is deactivated, the promotion will be applied even when the minimum quantity of items is added to the cart, regardless of whether the SKUs are different or the same.
+- Apply with other promotions: Allows this promotion to be applied to the cart in combination with other promotions that give the same discount type.
+
+![Restrictions and limitations of use](//images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/3786a7a5b6067de6410cabfe402325b4/Restrictions_and_limitations_of_use.png)
diff --git a/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md b/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
index 05aa9acd4..d0adcf697 100644
--- a/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
+++ b/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
@@ -25,4 +25,4 @@ To do this, follow the steps below:
 For White Label Sellers there is a limit of 50 items with the same SKU in the shopping cart. You can change this limit upon request to customer
  [support](https://help.vtex.com/en/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe).
 
-![Carrinho Max EN](https://images.ctfassets.net/alneenqid6w5/2NKRULRqqck8QmGg8oOSCs/d7b5c44cca5cc1e4ca19abcb80dfd379/Carrinho_Max_EN.png)
+![Carrinho Max EN](//images.ctfassets.net/alneenqid6w5/2NKRULRqqck8QmGg8oOSCs/d7b5c44cca5cc1e4ca19abcb80dfd379/Carrinho_Max_EN.png)
diff --git a/docs/tutorials/en/campaign-audiences-list.md b/docs/tutorials/en/campaign-audiences-list.md
index 3e3d8cb92..d39e43ad8 100644
--- a/docs/tutorials/en/campaign-audiences-list.md
+++ b/docs/tutorials/en/campaign-audiences-list.md
@@ -17,7 +17,7 @@ subcategory: 2cI57eZ3ZiWSeaQs26Gwys
 
 Your store's campaign audience list is available in the VTEX Admin, on the *Promotions > Campaign audience* page, illustrated below.
 
-![lista-audiencias-campanha-en](https://images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/cec59b7c69282287586b1db574aedfe7/lista-audiencias-campanha-en.png)
+![lista-audiencias-campanha-en](//images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/cec59b7c69282287586b1db574aedfe7/lista-audiencias-campanha-en.png)
 
 On this page, you can perform the following actions:
 
@@ -50,7 +50,7 @@ The campaign audiences are displayed in _cards_ containing the following informa
 
 To view the [archived](#archiving-a-campaign-audience) campaign audiences, next to the **Show** option, click **Archived**, as illustrated below:
 
-![toggle-audiencias-campanha-arquivadas-en](https://images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/853066310add51cccf742dc10ea0283b/toggle-audiencias-campanha-arquivadas-en.png)
+![toggle-audiencias-campanha-arquivadas-en](//images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/853066310add51cccf742dc10ea0283b/toggle-audiencias-campanha-arquivadas-en.png)
 
 To return to the campaign audiences which have not been archived, click **Not Archived**.
 
diff --git a/docs/tutorials/en/campaign-audiences.md b/docs/tutorials/en/campaign-audiences.md
index e3bf0698c..2475bf9a0 100644
--- a/docs/tutorials/en/campaign-audiences.md
+++ b/docs/tutorials/en/campaign-audiences.md
@@ -27,7 +27,7 @@ For example: When creating a campaign audience for the fashion segment, you can
 
 The target audience segments the campaign audience's eligible users and conditions. If the campaign audience is active, the promotions associated with the campaign audience will be activated by meeting all the criteria defined for the target audience.
 
-![campanha-en](https://images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/5f7c4bb9f35c674f4959d136943b6808/campanha-en.png)
+![campanha-en](//images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/5f7c4bb9f35c674f4959d136943b6808/campanha-en.png)
 
 When the campaign is activated, eligible for the purchase context and all its restrictions are met, it does not necessarily mean that all the campaign audience promotions associated with it will be applied. The restrictions defined in the[ campaign promotion](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume) must also be met.
 
diff --git a/docs/tutorials/en/campaign-promotion.md b/docs/tutorials/en/campaign-promotion.md
index a08e0c890..b1c66924d 100644
--- a/docs/tutorials/en/campaign-promotion.md
+++ b/docs/tutorials/en/campaign-promotion.md
@@ -122,7 +122,7 @@ For the promotion to be valid for all trade policies, leave it blank.
 
 In this section, you need to choose whether this promotion will apply to all products in your store or only to specific products, as illustrated below.
 
-![promocoes-restricao-en](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
+![promocoes-restricao-en](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
 
 If you want the promotion to apply to your entire catalog, select the **Apply to all products** option.
 
@@ -132,7 +132,7 @@ You can add or remove **Categories**, **Brands**, **Collections**, **Products**
 
 See an example below. In this case, the promotion includes all products from the category **Home Appliances** whose brand is **Brastemp**, except the product **Refrigerator 100**.
 
-![exemplo-en](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
+![exemplo-en](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
 
 In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
 
diff --git a/docs/tutorials/en/canceling-orders.md b/docs/tutorials/en/canceling-orders.md
index 78e5c49b9..d8a38f470 100644
--- a/docs/tutorials/en/canceling-orders.md
+++ b/docs/tutorials/en/canceling-orders.md
@@ -3,8 +3,8 @@ title: 'How to cancel orders'
 id: tutorials_186
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:47.296Z
-updatedAt: 2023-03-31T00:26:08.605Z
-publishedAt: 2023-03-31T00:26:08.605Z
+updatedAt: 2024-04-01T17:34:46.564Z
+publishedAt: 2024-04-01T17:34:46.564Z
 firstPublishedAt: 2017-04-27T23:00:46.851Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,24 +17,29 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Orders on VTEX can be canceled at practically any status during their evolution. It must be stressed that once canceled, the order status cannot be altered.
 
+<div class = "alert alert-warning">
+Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be canceled. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
+</div>
+
 There are two ways of doing this, through the VTEX Admin or API.
 
-## Cancelation through Orders module
+## Cancellation through Orders module
 
 1. In the VTEX Admin, go to **Orders > All Orders**, or type *All orders* in the search bar at the top of the page.  
-2. In **All orders**, access the desired order;
-3. Click on the button **Confirm cancelation** beside the main status card;
-4. You will be asked if you want to proceed with this action.
+2. In **All orders**, access the desired order.
+3. In the top pf the page, click `Cancel order`.
+4. Fill in the fields.
+5. Click `Confirm`.
 
 When the status of the order is **Ready for Handling** or **Handling Shipping**, cancellation must be done twice. This is because when you click on the button for the first time the status is changed to **Cancellation requested**.
 When the status of the order is **Cancellation requested**, just click again on **Confirm cancellation** to change the order to **Canceled**. If you want to continue with this order, just enter the tax receipt.
 
-**Remember!** It is impossible to change an order when its status already shows **Invoiced**.
+It is not possible to change an order when its status already shows `Invoiced`.
 
-## Cancelation using the ERP
+## Cancellation using the ERP
 
-Using the ERP, this action can take place through our REST API, according to our [ERP Integration Guide](https://developers.vtex.com/docs/erp-integration-set-up-order-processing).
+Using the ERP, this action can take place through our REST API, according to our [ERP Integration Guide](https://developers.vtex.com/docs/erp-integration-set-up-order-processing). You can use the [Cancel order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/cancel) endpoint.
 
-## Cancelation requested by the customer
+## Cancellation requested by the customer
 
-When the order cancelation is requested by the customer, the flow is different. Refer to [this article](https://help.vtex.com/en/tutorial/como-funciona-o-cancelamento-de-pedido-por-parte-do-cliente--3wEI6DUNtecooG2Ki4Akqo) to unserstand how cancelation happens in such case.
+When the order cancellation is requested by the customer, the flow is different. Refer to [this article](https://help.vtex.com/en/tutorial/como-funciona-o-cancelamento-de-pedido-por-parte-do-cliente--3wEI6DUNtecooG2Ki4Akqo) to unserstand how cancellation happens in such case.
diff --git a/docs/tutorials/en/carrefour-inventory-integration-errors.md b/docs/tutorials/en/carrefour-inventory-integration-errors.md
index b7fce4aed..619789fb8 100644
--- a/docs/tutorials/en/carrefour-inventory-integration-errors.md
+++ b/docs/tutorials/en/carrefour-inventory-integration-errors.md
@@ -3,8 +3,8 @@ title: 'Carrefour inventory integration errors'
 id: 4oDrYCkrIvWETCW34I2CKF
 status: PUBLISHED
 createdAt: 2021-10-25T22:15:47.447Z
-updatedAt: 2023-03-29T14:40:33.949Z
-publishedAt: 2023-03-29T14:40:33.949Z
+updatedAt: 2024-06-17T15:05:00.226Z
+publishedAt: 2024-06-17T15:05:00.226Z
 firstPublishedAt: 2021-10-25T22:30:07.082Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/carrier-working-hours.md b/docs/tutorials/en/carrier-working-hours.md
index 4f2b8fcbf..90aa2fe39 100644
--- a/docs/tutorials/en/carrier-working-hours.md
+++ b/docs/tutorials/en/carrier-working-hours.md
@@ -3,8 +3,8 @@ title: 'Carrier working hours'
 id: 2oGpbInIgdxSWUi3TZjdCS
 status: PUBLISHED
 createdAt: 2019-02-06T16:21:24.412Z
-updatedAt: 2021-08-11T17:43:41.414Z
-publishedAt: 2021-08-11T17:43:41.414Z
+updatedAt: 2024-04-11T00:33:50.619Z
+publishedAt: 2024-04-11T00:33:50.619Z
 firstPublishedAt: 2019-02-06T18:25:37.545Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,32 +15,39 @@ legacySlug: setting-up-business-hours-for-carriers, configuring-carriers-cut-off
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-On the VTEX platform, you can determine working hours for your store’s carriers. To do that, you have to configure pickup times and shipping windows available in your store.
+On VTEX, you can determine business hours for your store’s [carriers](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) in the [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140). You can configure pickup time and shipping window periods available for the carrier.
 
-To configure a carrier’s working hours in your store, go to `Inventory & shipping` and click on `Shipping strategy`. Then, you can create a [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) or edit an existing one. 
+To configure a carrier’s business hours in your store, in your VTEX Admin go to **Shipping > Shipping strategy**. You can [create a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) or [edit](https://help.vtex.com/en/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE) an existing one.
 
 The way you configure working hours will influence the delivery time calculation. These configurations can be made on the shipping policy’s details page, in the following options:
 
-* **[Shipping window](#shipping-window)**: periods in which the carrier ships items to customers.
-* **[Pickup time](#pickup-time)**: timetables in which the carrier picks up items for delivery.
+* **[Shipping Window](#shipping-window)**: periods in which the carrier ships items to customers.
+* **[Pickup Time](#pickup-time)**: timetables in which the carrier picks up items for delivery.
 
-## Shipping window
+## Shipping Window
 
-1. Click on the `Shipping window` card.
-2. Click the toggle button to enable or disable the option `Accept purchases outside working hours`.
+1. In the [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140), in the **Business Hours** section, click the `Shipping Window` card.
+2. If you wish to activate the option `Accept purchases outside working hours`, enable the toggle switch. Otherwise, leave it deactivated.
 
-    Enable it if the carrier agrees to receive orders outside working hours. By setting this option to `Active`, the delivery time will be calculated differently. For example, if an order is placed after the pickup time, the time until the next available pickup time will be added to the total delivery time.
+  <div class="alert alert-danger">
+To authorize the carrier to receive orders on weekends, this toggle must be marked as <code>Active</code>. Even if Saturdays and Sundays are configured as valid windows, activating the toggle is mandatory to authorize the carrier to receive orders outside business hours.
+</div>
+
+  <div class = "alert alert-info">
+When this option is enabled, the order <a href="https://help.vtex.com/en/tutorial/how-shipping-calculation-works--tutorials_116">shipping calculation</a> is influenced, and the period from order placement to the carrier's business time is added to the total shipping time.
+</div>
 
 3. Select the `Day of the week`, as well as the `Start time` and `End time` for shipping items to customers.
     * **Day of the week**: days on which carriers make deliveries.
     * **Start time**: the time the shipping window starts.
     * **End time**: the time the shipping window ends.
-4. Click on `Add shipping window` if you want to add a new window.
-5. Click on `Save changes`.
+4. If you want to add a new window period, click `Add shipping window`.
+5. Click `Save changes`.
 
-## Pickup time
+## Pickup Time
 
-1. Click on the `Pickup time` card.
-2. Select the `Day of the week` and `Pickup time`. 
-3. Click on `Add pickup time` if you want to add a new time for pickup.
-4. Click on `Save changes`.
+1. In the [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140), in the **Business Hours** section, click the `Pickup Time` card.
+2. Select the `Day of the week`.
+3. Select the `Pickup time`. 
+4. If you want to add a new pickup period, click `Add pickup time`.
+5. Click `Save changes`.
diff --git a/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md
index afa76347c..593ed70d3 100644
--- a/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -21,7 +21,7 @@ In the tab *Shipping strategy* you can register your logistics route, including
 The new features on the **Shipping policy** registration page give you more flexibility when setting up your delivery strategy. In the previous version, there was the section *Time setup*, in which you could select the *Working hours*, *Cut-off times* or *Scheduled Delivery* for a carrier. 
 
 **Previous version**
-![EN Configurações de tempo versão antiga](https://images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/5c6dfcad4a2511c33c6f2a5a0f0d358a/EN_Configura____es_de_tempo_vers__o_antiga.jpg)
+![EN Configurações de tempo versão antiga](//images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/5c6dfcad4a2511c33c6f2a5a0f0d358a/EN_Configura____es_de_tempo_vers__o_antiga.jpg)
 
 In the new version, we’ve:  
 - Changed option names to make it more clear to users.  
@@ -29,7 +29,7 @@ In the new version, we’ve:
 - Added an option to define your delivery capacity, in order to schedule deliveries based on your operation reality.   
 
 **Beta version**
-![EN Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/f4883976b951e19591b4b75b228f9a10/EN_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![EN Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/f4883976b951e19591b4b75b228f9a10/EN_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 ## Pickup time
 
@@ -46,7 +46,7 @@ Just like in the previous version, you can't set up the “Shipping time window
 Previously, you could only choose the *Scheduled Delivery* function deprived of the *Business hours*. You can now set up the *Scheduled Delivery* option together with *Business hours* for your client to choose the most suitable shipping method during the order checkout. Please check the fields to fill-in when setting up this option.
 
 **Beta version**
-![EN entrega agendada](https://images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/7165d0778182cb771f137637ef8e2a2b/EN_entrega_agendada.jpg)
+![EN entrega agendada](//images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/7165d0778182cb771f137637ef8e2a2b/EN_entrega_agendada.jpg)
 
 - **Max. range of delivery**: this field must be filled according to your logistics operation. Please define the time period that the carrier takes to do a scheduled delivery, from the order to the delivery confirmation.  
 - **Set operational capacity**: depending on the characteristics of your operation, and on how the carrier sends its products, you might prefer to define a delivery capacity in the number of items or number of orders. For example, if your store is in the supermarket sector, and the means of transportation for the scheduled delivery is by motorcycle, only a limited number of items will fit into the motorcycle storage. For this reason, we recommend that you select “items” as units. However, if your operation already has a few items per order, you might prefer to define `orders` as units, for example.  
diff --git a/docs/tutorials/en/carries-on-vtex.md b/docs/tutorials/en/carries-on-vtex.md
index 789ae4a1c..64dd4e671 100644
--- a/docs/tutorials/en/carries-on-vtex.md
+++ b/docs/tutorials/en/carries-on-vtex.md
@@ -3,8 +3,8 @@ title: '​​Carriers on VTEX'
 id: 7u9duMD5UQa2QQwukAWMcE
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:39.775Z
-updatedAt: 2023-03-31T01:00:22.710Z
-publishedAt: 2023-03-31T01:00:22.710Z
+updatedAt: 2023-07-31T22:14:54.618Z
+publishedAt: 2023-07-31T22:14:54.618Z
 firstPublishedAt: 2019-01-24T22:14:26.579Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/en/catalog-overview-2.md b/docs/tutorials/en/catalog-overview-2.md
index 989b08080..8a6c0c323 100644
--- a/docs/tutorials/en/catalog-overview-2.md
+++ b/docs/tutorials/en/catalog-overview-2.md
@@ -1,10 +1,10 @@
 ---
 title: 'Catalog Overview'
 id: FFrumKPYFpvIWKRXfhQYp
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-28T17:25:52.296Z
-updatedAt: 2023-03-28T17:31:02.205Z
-publishedAt: 2023-03-28T17:31:02.205Z
+updatedAt: 2024-03-14T16:38:37.477Z
+publishedAt: 
 firstPublishedAt: 2023-03-28T17:31:02.205Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -24,8 +24,6 @@ The **Catalog** menu contains the features related to the product assortment of
 
 The **Catalog** menu in your redesigned Admin brings together the pages where you manage your ecommerce catalog, pricing, and inventory.
 
-![visao-geral-produto-EN](https://images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/be0aec115746ca9494e44e3f120983ed/image.png)
-
 Check out the menu’s different sections and pages below.
 
 ## Catalog
diff --git a/docs/tutorials/en/catalog-overview.md b/docs/tutorials/en/catalog-overview.md
index 4b842b009..bd3b27cce 100644
--- a/docs/tutorials/en/catalog-overview.md
+++ b/docs/tutorials/en/catalog-overview.md
@@ -15,18 +15,17 @@ legacySlug: catalog-overview
 subcategory: 
 ---
 
-![Catalog overview (header)](https://raw.githubusercontent.com/vtexdocs/help-center-content/main/images/en/catalog-overview-0.jpg)
-Catalog is your store's administration module for configuring the features related to your ecommerce products. To make products available for customers on your website, you need to add them to this module.
+![Catalog overview (header)](//images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/ecec695214ce50acf65453efb6668247/image1.jpg)
+Catalog is your store's administration module for configuring the features related to your ecommerce products. To make products available for customers on your website, you need to add them to this module. 
 
 In this article, you will find an overview of the catalog items and its features.
 
 ## Categories
-
 Category is the second categorization level of your store, under [Departments](https://help.vtex.com/en/tutorial/what-is-a-department--22rKjmYWVmmKAK8CWa8yKw) — sections or sectors that categorize the areas of your business. Categories are essential for classifying your products.
 
 The **Categories** page allows you to view and manage your store's category trees, as illustrated below.
 
-![Catalog structure](https://raw.githubusercontent.com/vtexdocs/help-center-content/main/images/en/catalog-overview-1.png)
+![Catalog structure](//images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/1716c9232b7a09d5477021ac875fe690/image4.png)
 
 Learn how to add a category in the tutorial [Registering a category](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206). If you want to change or disable a category, follow the steps in the tutorial [Disabling and reorganizing categories](https://help.vtex.com/en/tutorial/disabling-and-reorganizing-categories--tutorials_264).
 
@@ -35,7 +34,6 @@ In the Categories module, there are [Subcategories](https://help.vtex.com/en/tut
 [Similar categories](https://help.vtex.com/en/tutorial/setting-up-similar-categories--tutorials_204) allow a product to be in more than one category, and [Global categories](https://help.vtex.com/en/tutorial/setting-up-similar-categories--tutorials_204) are used for external integrations, for example, with marketplaces or other sales channels.  
 
 ## Brands
-
 Brand is a required field when adding a product, so you cannot save a product without defining it. On the VTEX platform, there is a specific section to add the brands of the products available in your store.
 
 Once a product is associated with a brand, customers will use this attribute as a filter in your store. It is quite common for customers to search for products using the brand as a keyword.
@@ -45,10 +43,9 @@ You have to add brands independently. When adding a product, you must associate
 Learn how to add a brand in the tutorial [How to register brands](https://help.vtex.com/en/tutorial/registering-brands--tutorials_1414).
 
 ## Products and SKUs
+A product is the most generic definition of something available for sale in your store, such as "shirt". SKUs are variations of this product, such as colors and sizes. It is possible to have the same shirt (product) in sizes S, M, or L, i.e., with different specifications. 
 
-A product is the most generic definition of something available for sale in your store, such as "shirt". SKUs are variations of this product, such as colors and sizes. It is possible to have the same shirt (product) in sizes S, M, or L, i.e., with different specifications.
-
-The combination of product specifications composes a SKU, for example, a shirt in size S. A product must have at least one SKU.
+The combination of product specifications composes a SKU, for example, a shirt in size S. A product must have at least one SKU. 
 
 The Products and SKUs section in the VTEX Admin allows you to manage products and SKUs. Check out the tutorial on [How to add products](https://help.vtex.com/en/tutorial/adding-products--tutorials_2567). Once you have added a product, create its SKUs following the steps in the tutorial [SKU registration fields](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY).
 
@@ -63,19 +60,16 @@ The SKU specification determines the website navigation filters and differentiat
 To add a specification, check out the tutorials [How to create a product field](https://help.vtex.com/en/tutorial/creating-a-product-field--tutorials_106), [Setting up the specification type](https://help.vtex.com/en/tutorial/setting-up-the-category-field-type--tutorials_286), and [How to create category groups](https://help.vtex.com/en/tutorial/creating-category-groups--tutorials_246).
 
 ## Import and export
-
 This feature allows the Admin to import [Images](https://help.vtex.com/en/tutorial/importing-images-via-a-worksheet--tutorials_262), [Products](https://help.vtex.com/en/tutorial/how-to-export-a-product-spreadsheet--2sIroGeqZqaN3NAvaSGwWV), [SKUs](https://help.vtex.com/en/tutorial/importing-and-exporting-product-and-sku-specifications--tutorials_274), Brands, and [Inventory spreadsheets](https://help.vtex.com/en/tutorial/importing-and-exporting-an-inventory-spreadsheet--tutorials_2034) into your store, making it easy to populate fields in bulk.
 
 To understand how to use this feature, check out the article  [Filling in the product and SKU import spreadsheet](https://help.vtex.com/en/tutorial/filling-in-fields-in-the-import-spreadsheet--4nYhx63Q5yokQWaMguaIgI).
 
 ## List types
-
-Lists are groups of products you can offer your customers in your store. It is possible to create various types of lists, especially related to events, such as weddings, baby showers, birthdays, or any other occasion that addresses your customer needs.
+Lists are groups of products you can offer your customers in your store. It is possible to create various types of lists, especially related to events, such as weddings, baby showers, birthdays, or any other occasion that addresses your customer needs. 
 
 In this section, you can configure the lists available on your website. Learn how to create a list in the tutorial [Creating a list type](https://help.vtex.com/en/tutorial/creating-a-type-of-list--tutorials_254).
 
 ## Attachments
-
 Attachments are optional customizations for complementing products with a particular specification. They can be purchased with a service or item, and may or may not have an additional cost.
 
 To add an attachment, follow the steps in the tutorial [Registering an attachment](https://help.vtex.com/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU). For complex scenarios, you can set up an [Assembly Option](https://help.vtex.com/en/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH).
@@ -89,38 +83,34 @@ On the VTEX platform, the XML configuration feature combines different standards
 To configure XML files, follow the steps in the tutorial [Configuring XML](https://help.vtex.com/en/tutorial/configuring-xml--tutorials_242).
 
 ## Reports
-
 You can get reports about transactions and changes in your store. These are the types of reports available:
 
-- [Security](https://help.vtex.com/en/tutorial/understanding-the-security-report--tutorials_282)
-- [Index](https://help.vtex.com/en/tutorial/how-to-use-the-index-report--4ikVpMhwByyS8sysaeOIm4)
-- Gift list
-- Inventory shortage
-- Newsletter
-- [Reviews](https://help.vtex.com/en/tutorial/accessing-product-reviews--139sIVny6fyXK0Nk60L1NF)
-- Downloads
+ - [Security](https://help.vtex.com/en/tutorial/understanding-the-security-report--tutorials_282)
+ - [Index](https://help.vtex.com/en/tutorial/how-to-use-the-index-report--4ikVpMhwByyS8sysaeOIm4)
+ - Gift list
+ - Inventory shortage
+ - Newsletter
+ - [Reviews](https://help.vtex.com/en/tutorial/accessing-product-reviews--139sIVny6fyXK0Nk60L1NF)
+ - Downloads
 
 ## Commercial conditions
-
 Commercial conditions are used to group SKUs and, based on that, offer different payment conditions. Example: allowing your customers to pay in 12 installments with credit card, but only for electronics.
 To define a commercial condition, follow the tutorial [Registering a commercial condition](https://help.vtex.com/en/tutorial/registering-a-commercial-condition--tutorials_445).
 
 ## Suppliers
-
 This feature allows you to add suppliers to your store or marketplace. To add a supplier, please follow the steps below:
 In the Admin, click **Catalog** > **Suppliers**.
 Click the button `New Provider`.
 Fill in the following fields.
 
 1. **Name:** Name of the supplier. This is a required field.
-2. **Company name:** Enter the supplier's company name.
+2. **Company name:** Enter the supplier's company name. 
 3. **State Registration:** Enter the supplier's registration ID in a given state.
 4. **FEIN:** Enter the supplier's Tax Identification Number.
 5. Fill in the supplier's contact data.
 6. Click `Save`.
 
 ## Collections
-
 A collection is composed of two or more SKUs that may or may not have common features to be displayed on your store's product pages.
 
 You can create collections using grouping criteria such as commemorative dates, launches, or best-selling products.
@@ -128,3 +118,4 @@ You can create collections using grouping criteria such as commemorative dates,
 For example, you can create a page for Valentine's Day with recommended gifts for the occasion, creating a "gift" collection.
 
 To create a collection, follow the steps in [this tutorial](https://help.vtex.com/en/tutorial/creating-collections-beta--yJBHqNMViOAnnnq4fyOye).
+
diff --git a/docs/tutorials/en/categories.md b/docs/tutorials/en/categories.md
index 766528d62..ba5108b37 100644
--- a/docs/tutorials/en/categories.md
+++ b/docs/tutorials/en/categories.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Categories** page allows you to view and manage the category trees registered on Seller Portal. To access the page on VTEX Admin, go to **Catalog** > **Categories**.
 
-![categorias-en](https://images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/d9d795232e14fe8300461c0d32dfb10e/categorias-en.PNG)
+![categorias-en](//images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/d9d795232e14fe8300461c0d32dfb10e/categorias-en.PNG)
 
 From the category tree, you can:
 
@@ -51,7 +51,7 @@ To find a category, you must type the name of the category in the search bar abo
 ## Browsing the category tree
 The categories page displays the outermost levels of the categories. Click on the <i class="fas fa-angle-right"></i> icon to access the subcategories, as shown below.
 
-![arvore-categoria-EN](https://images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/362b5e61773ad44d2e00d7f0813339d0/arvore-categoria-EN.gif)
+![arvore-categoria-EN](//images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/362b5e61773ad44d2e00d7f0813339d0/arvore-categoria-EN.gif)
 
 To view the information for a category, click on its name. 
 
diff --git a/docs/tutorials/en/category-registration-fields.md b/docs/tutorials/en/category-registration-fields.md
index cd7453cee..d9e5ba82c 100644
--- a/docs/tutorials/en/category-registration-fields.md
+++ b/docs/tutorials/en/category-registration-fields.md
@@ -3,8 +3,8 @@ title: 'Filling in the category registration fields'
 id: 5Z7RrvW41yumyQCmk2iqoG
 status: PUBLISHED
 createdAt: 2017-09-20T14:44:06.897Z
-updatedAt: 2022-08-01T18:47:26.486Z
-publishedAt: 2022-08-01T18:47:26.486Z
+updatedAt: 2024-01-04T14:40:33.174Z
+publishedAt: 2024-01-04T14:40:33.174Z
 firstPublishedAt: 2017-09-20T14:58:27.420Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -40,11 +40,11 @@ To better understand the meaning of each category registration field, see the fu
 - __Active:__ When selecting this item, the category or department is activated or deactivated in your store.
 - __Menu with active link:__ When selecting this item, the category or department is active and clickable on the site for the client to navigate through it.
 - __Brand Filter:__ When selecting this item, the category or department will have a brand filter on the page.
-- __Score (used for search ordering):__ value used to set the priority on the search result page. To understand more about Score, access our article: [How does the score field work?](https://help.vtex.com/en/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcaee).
+- __Score (used for search ordering):__ value used to set the priority on the search result page. To understand more about Score, access our article: [How does the score field work?](https://help.vtex.com/en/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcae).
 - __Product display mode:__ defines how SKUs will be displayed on the product page. See below the options for this field:
   - __List of SKUs:__ All SKUs in the department or category in question will be displayed in list format. Each one with its Buy button on the side.
-  ![1Lista.en](https://images.ctfassets.net/alneenqid6w5/52RUiCTYT5JeL6Huo53nSh/1b3c9713709f10be3e88ae5925128de5/Lista.en.png)
+  ![1Lista.en](//images.ctfassets.net/alneenqid6w5/52RUiCTYT5JeL6Huo53nSh/1b3c9713709f10be3e88ae5925128de5/Lista.en.png)
   - __Icons with radio selection (radio box)__ All SKUs in this department/category will need to be selected through radio selection.
-  ![RadioBox.en](https://images.ctfassets.net/alneenqid6w5/bbx5D8m5cXuac0w1LZGc2/9c91af75ed6af97eebf70207880e7708/RadioBox.en.png)
+  ![RadioBox.en](//images.ctfassets.net/alneenqid6w5/bbx5D8m5cXuac0w1LZGc2/9c91af75ed6af97eebf70207880e7708/RadioBox.en.png)
   - __Following definition of the SKU specification:__ all SKUs in this department/category will be selected according to the specification tab on the SKU registration form. The preconfigured options are Combo or Radio.
-  ![Campos.en](https://images.ctfassets.net/alneenqid6w5/4opYmeQPk3r8uux4ldosbh/d14bec6c5bdb9d6b0e6b4ab87bd20ef6/Campos.en.png)
+  ![Campos.en](//images.ctfassets.net/alneenqid6w5/4opYmeQPk3r8uux4ldosbh/d14bec6c5bdb9d6b0e6b4ab87bd20ef6/Campos.en.png)
diff --git a/docs/tutorials/en/change-a-placeholder-title.md b/docs/tutorials/en/change-a-placeholder-title.md
index af1b6e194..16e91821c 100644
--- a/docs/tutorials/en/change-a-placeholder-title.md
+++ b/docs/tutorials/en/change-a-placeholder-title.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 The title of a placeholder is what appears in the right corner of the object, as the image below indicates.
 
-![cms-placeholder en](https://images.ctfassets.net/alneenqid6w5/7kCsbNAZZ6kGiGe6IMGGye/02545dd609ed095ee074d85134668028/placeholder_destaque_EN.png)
+![cms-placeholder en](//images.ctfassets.net/alneenqid6w5/7kCsbNAZZ6kGiGe6IMGGye/02545dd609ed095ee074d85134668028/placeholder_destaque_EN.png)
 
 The text that is entered in this field is what will be displayed as a placeholder title on the store's website.
 
@@ -26,7 +26,7 @@ To change the title of a placeholder, just follow the steps below:
 1. Click the title.
 
 2. Insert the new title.
-![placeholder-change-name en](https://images.ctfassets.net/alneenqid6w5/2T3rBaF3RYIukMyeWOacI/e17ee1fd57027e899f409194f9bfe99e/change_name_E.png)
+![placeholder-change-name en](//images.ctfassets.net/alneenqid6w5/2T3rBaF3RYIukMyeWOacI/e17ee1fd57027e899f409194f9bfe99e/change_name_E.png)
 
 3. Click __Rename__.
 
diff --git a/docs/tutorials/en/change-seller.md b/docs/tutorials/en/change-seller.md
index 316ce5216..68c37628c 100644
--- a/docs/tutorials/en/change-seller.md
+++ b/docs/tutorials/en/change-seller.md
@@ -26,13 +26,13 @@ Sellers can be changed in two situations:
 - Seller cancels the order.
 - Marketplace decides to change the seller.
 
-![seller_cancela_pedido_EN](https://images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/de157152dd35da3598e6345114c7e90e/seller_cancela_pedido_EN.png)
+![seller_cancela_pedido_EN](//images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/de157152dd35da3598e6345114c7e90e/seller_cancela_pedido_EN.png)
 
 You can [set the time window to change seller from 0 to 30 days](https://developers.vtex.com/vtex-rest-api/reference/updatewindowtochangeseller); by default, it is two days. When the window to change seller is set to 0 days, there is not an actual period for switching sellers, so even though the feature is configured, it does not work in practice, and the order proceeds to cancellation.
 
 Upon being notified by the seller about the order cancellation, the marketplace can configure how many days they have to decide whether to cancel the purchase or change the seller. But pay attention: if the marketplace chooses to change sellers, the decision to inform customers of such changes is the marketplace’s responsibility.
 
-![mkt_cancela_seller_EN](https://images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/7a5c5687cb444e4ddf4a41a64dec6ff4/mkt_cancela_seller_EN.png)
+![mkt_cancela_seller_EN](//images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/7a5c5687cb444e4ddf4a41a64dec6ff4/mkt_cancela_seller_EN.png)
 
 ## Limitations
 
diff --git a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
index b44617708..dec01d3a2 100644
--- a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -34,7 +34,7 @@ After [enabling the functionality](https://developers.vtex.com/vtex-rest-api/doc
 3. Change the price to the desired value and press `ENTER`.
 4. Click `Close order`.
 
-![manualprice](https://images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/56a551927294fedcaf127cfdb3a8f2a1/manualprice.gif)
+![manualprice](//images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/56a551927294fedcaf127cfdb3a8f2a1/manualprice.gif)
 
 In addition to the configuration on the Checkout screen, the price of a product can also be modified through the [Change Price](https://developers.vtex.com/vtex-rest-api/reference/pricechange) API, learn more in [Setting the price of an item manually](https://developers.vtex.com/vtex-rest-api/docs/enable-the-manual-price#setting-the-price-of-an-item-manually).
 
diff --git a/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
index 1a9a60afb..225ef50ab 100644
--- a/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
@@ -51,8 +51,8 @@ That is, I'm using the variables `preposicaonomeloja2` and `nomeloja`.
 When using variables to compose a text, replace the <code>#</code> symbol with <code>@</code>. That is, <b>#variable#</b> becomes <b>@variable@</b>.
 </div>
 
-![textos-importantes en](https://images.ctfassets.net/alneenqid6w5/3ck7V4j6wgygm0qE2ia2m8/ec2d596e8fbee37f53d38568d797a401/textos_importantes_en.png)
-![exemplos-textos-importantes en](https://images.ctfassets.net/alneenqid6w5/3qJmU7aPIcUowc6SkaYoSS/4c7d666cf29ef651c19ee837c9f42a75/3_en.png)
+![textos-importantes en](//images.ctfassets.net/alneenqid6w5/3ck7V4j6wgygm0qE2ia2m8/ec2d596e8fbee37f53d38568d797a401/textos_importantes_en.png)
+![exemplos-textos-importantes en](//images.ctfassets.net/alneenqid6w5/3qJmU7aPIcUowc6SkaYoSS/4c7d666cf29ef651c19ee837c9f42a75/3_en.png)
 
 As I defined the content of the first variable to be "to" and the second one is "World Shopping", the final text rendered on the site will be "Welcome to World Shopping".
 
diff --git a/docs/tutorials/en/changing-items-from-a-complete-order.md b/docs/tutorials/en/changing-items-from-a-complete-order.md
index bdf194ef6..e144a15b5 100644
--- a/docs/tutorials/en/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/en/changing-items-from-a-complete-order.md
@@ -3,8 +3,8 @@ title: 'Changing items from a completed order'
 id: tutorials_190
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:22.411Z
-updatedAt: 2023-05-03T14:22:00.584Z
-publishedAt: 2023-05-03T14:22:00.584Z
+updatedAt: 2024-04-01T17:40:33.284Z
+publishedAt: 2024-04-01T17:40:33.284Z
 firstPublishedAt: 2017-04-27T23:00:47.264Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -37,8 +37,9 @@ Before making changes to the order, be aware of the restrictions of this feature
 * The request for change only occurs if there are changes in the number of items or replacement of at least one SKU in the order.
 * Changing items that are not from the marketplace itself or a franchise account is not allowed.
 * The [acquirer](https://help.vtex.com/pt/tutorial/o-que-e-um-adquirente--7N1oRTG8dGmOiIugC0cs4E) must accept the new transaction value for the change to occur.
-* Additional amounts are only allowed if the order was paid by [credit card promissory](https://help.vtex.com/tutorial/setting-up-payments-with-promissory--5pW7avTwtyQcMu4uiW8quQ), [cash](https://help.vtex.com/tutorial/how-to-configure-a-custom-payment--tutorials_451) or [credit control](https://help.vtex.com/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0). In addition, the [acquirer](https://help.vtex.com/pt/tutorial/what-is-an-acquirer--7N1oRTG8dGmOiIugC0cs4E) must allow transactions without the CVV code and two charging transactions in the same order.
+* Additional amounts are only allowed if the order was paid by [Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ), [cash](https://help.vtex.com/tutorial/how-to-configure-a-custom-payment--tutorials_451) or [credit control](https://help.vtex.com/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0). In addition, the [acquirer](https://help.vtex.com/pt/tutorial/what-is-an-acquirer--7N1oRTG8dGmOiIugC0cs4E) must allow transactions without the CVV code and two charging transactions in the same order.
 * The [reservation](https://help.vtex.com/pt/tutorial/how-does-reservation-work--tutorials_92) of the items in the inventory is not automatic. You must manually update the number of items that are still available in the [inventory](https://help.vtex.com/pt/tutorial/managing-stock-items--tutorials_139).
+* Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to change the order.
 * It is not possible to change an order when its transaction is finalized. For changes to the discounted order value, for example, the OMS considers that you can still change the transaction value if the status in Transaction Details is other than `Finished`, even if the value has already been settled.  
 * You cannot make changes to orders coming from [marketplaces integrated with VTEX](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402) (either by native connectors or partner connectors).
 * You can only change orders that are being prepared for delivery.
diff --git a/docs/tutorials/en/changing-the-total-cost-of-the-order.md b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
index c5de941a9..35290d784 100644
--- a/docs/tutorials/en/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
@@ -28,13 +28,13 @@ To make the change, follow the steps below:
 3. Click the order to access the **Order details page**.        
 4. Go to the **Total cost of the order** section on the right side of the Order Details page.    
 5. Click `Change final cost`.    
-![valorfinalEN](https://images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/22a8836f14fd64c2f17257c60e711a8a/valorfinalEN__1_.png)  
+![valorfinalEN](//images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/22a8836f14fd64c2f17257c60e711a8a/valorfinalEN__1_.png)  
 6. On the **Change value** page, fill in the required fields.  
 7. Fill in the required fields:  
     * **Value:** Select Discount or Increase and enter the amount corresponding to what you want to change.    
     * **Reason:** indicate why you are making this change.  
 8. On the right side of the page click `Submit`.  
-![Alterar valorEN](https://images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/91ea6db5cdf47879f616f2a17e31c542/Alterar_valorEN.png)
+![Alterar valorEN](//images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/91ea6db5cdf47879f616f2a17e31c542/Alterar_valorEN.png)
 
 Changes to the order cost will be updated in the "Items to invoice" and "Order History" sections. Note that the order total will also change.
 
diff --git a/docs/tutorials/en/changing-tracking-data.md b/docs/tutorials/en/changing-tracking-data.md
index 91fd2a88e..717657ba0 100644
--- a/docs/tutorials/en/changing-tracking-data.md
+++ b/docs/tutorials/en/changing-tracking-data.md
@@ -38,4 +38,4 @@ To manually change an order's data, follow the steps below:
     * **Select carrier:** select which carrier will deliver the order.
 7. Click `Save`.
 
-![FaturaEN](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
+![FaturaEN](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
diff --git a/docs/tutorials/en/check-order-delivery-details.md b/docs/tutorials/en/check-order-delivery-details.md
index 91e0d1835..67688bd1f 100644
--- a/docs/tutorials/en/check-order-delivery-details.md
+++ b/docs/tutorials/en/check-order-delivery-details.md
@@ -45,7 +45,7 @@ To see these details, do a [shipping simulation](/en/tutorial/freight-simulation
 6. Enter the zip code of the order.
 7. Click on __Shipping Simulation__.
 
-![gerenciamento-pedidos-filtro-hoje en](https://images.ctfassets.net/alneenqid6w5/9qtBlqEOicqQMqqGmuOWU/86e3bb19ce13e8880561f715f1d4b0d8/simular-frete_en.png)
+![gerenciamento-pedidos-filtro-hoje en](//images.ctfassets.net/alneenqid6w5/9qtBlqEOicqQMqqGmuOWU/86e3bb19ce13e8880561f715f1d4b0d8/simular-frete_en.png)
 
 For each carrier considered in the simulation, you can see the details of the corresponding order. To do this, click __show details__. 
 
diff --git a/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md b/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md
index c6e62b3a3..0431a1f81 100644
--- a/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md
+++ b/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md
@@ -23,7 +23,7 @@ Let's say you want to know what criteria the platform used to calculate the deli
 
 First, let's enter the __All Orders__ module to see the order.
 
-![1](https://images.ctfassets.net/alneenqid6w5/2tlBnsKXyuMxuCI2U2Ekyi/35c860bb303a575b221fd1662e749867/1.png)
+![1](//images.ctfassets.net/alneenqid6w5/2tlBnsKXyuMxuCI2U2Ekyi/35c860bb303a575b221fd1662e749867/1.png)
 
 >In the upper right corner, you see the __date in which the order was made__ (MAY 6 2019).
 >And in the bottom of the screen, you see the __order delivery deadline__ (MAY 22 2019).
@@ -33,25 +33,25 @@ Now let's enter the __Inventory & shipping__ module and simulate the freight of
 To do this, follow the steps below:
 
 1. In the VTEX Admin, go to **Shipping > Shipping Simulator**, or type *Shipping Simulator* in the search bar at the top of the page.  
-2. Enter the name or ID of each SKU that was in the shopping cart of the order that you want to investigate, including the quantity of each of them.![2](https://images.ctfassets.net/alneenqid6w5/SCHsOOepDsyafXnm2pWJW/58cb84906928bb1295fad1d807bd737d/2.png)
+2. Enter the name or ID of each SKU that was in the shopping cart of the order that you want to investigate, including the quantity of each of them.![2](//images.ctfassets.net/alneenqid6w5/SCHsOOepDsyafXnm2pWJW/58cb84906928bb1295fad1d807bd737d/2.png)
 3. Enter the purchase order's zip code.
 4. Click __Shipping simulation__.
 
 In the example below, note that 4 carriers were considered, and 12 were disregarded.
 
-![3](https://images.ctfassets.net/alneenqid6w5/1iMnSymiQdjkdd8uC2RRGN/be814f59861f03bea128f4307151c457/3.png)
+![3](//images.ctfassets.net/alneenqid6w5/1iMnSymiQdjkdd8uC2RRGN/be814f59861f03bea128f4307151c457/3.png)
 
 Checking again the order details page, we see that the type of delivery chosen by the customer for this order was __Expressa__, and that the carrier chosen by the platform to make the delivery was __Expressa & CO__.
 
-![4](https://images.ctfassets.net/alneenqid6w5/5CnczmPwairE2lypuLgeUM/64ee3a9cffba79370182c935e5d44073/4.png)
+![4](//images.ctfassets.net/alneenqid6w5/5CnczmPwairE2lypuLgeUM/64ee3a9cffba79370182c935e5d44073/4.png)
 
 Therefore, returning to the freight simulation, in the Shipping menu, we conclude that the first option was chosen for this delivery - and that therefore the total delivery time for the order was 12 days.
 
-![5](https://images.ctfassets.net/alneenqid6w5/euQuUd8FDcK5NE9wsLbp7/498df87eb1a5eaa10d1c32f63c63e7f6/5.png)
+![5](//images.ctfassets.net/alneenqid6w5/euQuUd8FDcK5NE9wsLbp7/498df87eb1a5eaa10d1c32f63c63e7f6/5.png)
 
 Now just click __show details__ to see the cost times that were used to calculate this deadline.
 
-![2019-06-05 17 52 13-Shipping simulator](https://images.ctfassets.net/alneenqid6w5/3nsjSgTBJEhVTGZr90nFXa/bd883156e87ede57fae70c3d05d516f5/2019-06-05_17_52_13-Shipping_simulator.png)
+![2019-06-05 17 52 13-Shipping simulator](//images.ctfassets.net/alneenqid6w5/3nsjSgTBJEhVTGZr90nFXa/bd883156e87ede57fae70c3d05d516f5/2019-06-05_17_52_13-Shipping_simulator.png)
 
 Each of the three cost times corresponds to what was defined for the three steps of the logistics route: stock, dock and carrier.
 
diff --git a/docs/tutorials/en/checkout-vtex-overview.md b/docs/tutorials/en/checkout-vtex-overview.md
index dd6bf5758..da54d3d79 100644
--- a/docs/tutorials/en/checkout-vtex-overview.md
+++ b/docs/tutorials/en/checkout-vtex-overview.md
@@ -35,7 +35,7 @@ The steps below describe the customer's purchase experience and the way that Che
 
 Every time a customer changes something in the cart (adds or removes items), or every time the Checkout screen is updated, the following Checkout internal process chain is performed.
 
-![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/1c2b515127000db8b88c3a2cfa5996d0/Checkout_Overview_EN.png)
+![Checkout overview](//images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/1c2b515127000db8b88c3a2cfa5996d0/Checkout_Overview_EN.png)
 
 <div class="alert alert-info">
 If one or more items selected by the customer are eligible for delivery by a <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#">Seller white label</a>, the seller responsible for delivering the items will be chosen based on shipping simulations, as shown in the right side of the picture. Learn more in <a href="https://help.vtex.com/en/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Selecting white label sellers</a>.
diff --git a/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md b/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
index 86b020f3b..8b7ada43e 100644
--- a/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
+++ b/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
@@ -3,8 +3,8 @@ title: 'Choosing between a multi-store architecture or an additional environment
 id: 4HRNpa1OCKZ5YzP8yiilBL
 status: PUBLISHED
 createdAt: 2023-05-25T16:33:11.450Z
-updatedAt: 2023-05-25T19:39:40.359Z
-publishedAt: 2023-05-25T19:39:40.359Z
+updatedAt: 2023-10-02T16:57:08.371Z
+publishedAt: 2023-10-02T16:57:08.371Z
 firstPublishedAt: 2023-05-25T19:35:27.925Z
 contentType: tutorial
 productTeam: Management
@@ -36,23 +36,23 @@ For marketplace architectures, you can also  <a href="https://help.vtex.com/en/t
 
 The following table shows how the different architectures are related to the components and features of the VTEX platform.
 
-| Property                         | Multistore architecture (store names)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Additional environment architecture                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Architecture                     | A single VTEX Admin ([account](https://help.vtex.com/en/tutorial/o-que-e-account-name)) with multiple subaccounts ([store names](https://help.vtex.com/pt/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)).                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Two separate VTEX Admin environments ([accounts](https://help.vtex.com/en/tutorial/o-que-e-account-name)).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| Segmentation of sales conditions | You can segment applications such as catalog, prices, payments, promotions, and other components through [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) and [bindings](https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W).                                                                                                                                                                                                                                                                                                                                                                                                        | Because there are two separate environments, with independent configurations, the merchant has more control over segmentation options for sales conditions in different scenarios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| Type of team                     | This is recommended when the same company and the same team manage two or more ecommerce stores with similar catalogs and some of the same items, but want to have separate storefronts for the customers to see each experience with a different brand.<br> <br>                                                                                                                                                                                                                                                                            | Recommended when different teams within the same company manage different online stores.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| Storefront                       | Each store has a different storefront, but all stores are managed through the same VTEX Admin. If you only want to change the website language, without changing the operation of the store, you can use [multibinding](https://help.vtex.com/en/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) and [catalog internationalization](https://developers.vtex.com/docs/guides/catalog-internationalization) to set that up within the same VTEX environment.<br> <br>Note that this architecture is different from a [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl); this account doesn't have its own website. Consumers browse directly on the website of the main account, which acts as a marketplace in this case.<br>     | Each account manages its own storefronts in separate VTEX Admins and can use all available options for segmenting storefronts.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| VTEX Admin performance           | Linking additional [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) to the same main account can affect the performance of the VTEX Admin. Platform features can be slowed down because information needs to be updated in each trade policy.<br> <br>Impact on Admin performance is also to be expected if the product catalog is very extensive (more than 2 million products), which increases indexing time.                                                                                                                                                               | You can create multiple [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) for each environment separately.<br> <br>Linking more trade policies to the same main account can affect the performance of the VTEX Admin, which can slow down some platform features.<br> <br>However, since separate environments are used, there is less need to add multiple trade policies.                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| Costs                            | Even though adding a store name has no extra cost, you still need to [request an additional trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X?) if you want to differentiate the website storefronts.Learn more about trade policies and segmentation of available settings in [How trade policies work](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).                                                                                                                                                                                                                                                                              | You need to [request an additional environment](https://help.vtex.com/en/tutorial/contratar-novo-ambiente--tutorials_2542) at the additional cost specified in the VTEX agreement.<br> <br>You may also [request a trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X?) if you want to segment the settings of each environment for different conditions. Learn more about trade policies and segmentation of available settings in [How trade policies work](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| Operation                        | When using this type of architecture, you should assess the complexity of managing catalog, promotions, prices, inventory, orders, and payments taking into account the different store names since all the information will be in the same Admin. You can set up [catalog internationalization](https://developers.vtex.com/docs/guides/catalog-internationalization) to sell in different countries.                                                                                                                                                                                                               | We recommend this architecture when you have operations in two different countries, and you need to separate the languages in the catalog itself to facilitate the operation of teams that also use different languages to communicate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| Master Data                      | When a subaccount is created, [Master Data](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) is created separately by default; in other words, each account has its own. However, it's possible to unify them by [submitting a ticket to our Support team](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).                                                                                                                                                                                                                                                                                                                                       | Each account will have its own independent [Master Data](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| Information security             | All components are shared between the store names, such as catalog, promotions, prices, and payment settings.<br> <br>It's important to take this into account when different teams in the same company have access to the VTEX Admin. For example, Brand A and Brand B are different store names. Employees of Brand B will be able to view the catalog, prices, and orders of Brand A.                                                                                                                                                     | The separate environments prevent access by employees from different teams to the information and settings of components such as catalog, promotions, prices, and payments.<br> <br>For example, Brand A and Brand B are different VTEX environments. Employees of Brand B can't view the catalog, prices, and orders of Brand A.<br>                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| License Manager                  | The same [License Manager](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager) manages all users.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Each Admin will have its own [License Manager](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager), and user management will be separate.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| Gift card                        | Subaccounts will have access to the same gift card management, and it will be possible to use the gift cards in different storefronts.                                                                                                                                                                                                                                                                                                                                                                                                       | Each Admin will have its own gift card management, and it won't be possible to use a gift card generated in one environment in the other.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| Marketplace structure            | The marketplace structure doesn't apply between different store names since they share catalog, prices, and inventory.<br> <br>                                                                                                                                                                                                                                                                                                                                                                                                              | An environment can be a seller in the other environment and vice versa. Products sold on both websites are based on the seller-marketplace relationship. Learn more in [Configuring a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) and[ Configuring a seller on a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP).<br> <br>You can also create franchise accounts to operate as white label sellers since they have different prices, inventories, and logistics. <br> <br>This can be done by requesting an additional environment (if they have some, but not all, items in common in the catalog) or through a franchise account (when the catalogs are completely the same). Learn more in [Choosing between standard account, franchise account, and Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).  |
-| Sitemap                          | There will be a single [sitemap](https://help.vtex.com/en/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) for the main account, which will be shared between the store names.                                                                                                                                                                                                                                                                                                                                                                                                                                           | Each account has its own independent [sitemap](https://help.vtex.com/en/tutorial/rastreamento-google-search-console-sitemap--tutorials_575).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| B2B: Catalog                     | You can't change the unit of measure configured in the catalog for each [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#catalog). Example: B2B stores sell wholesale, while B2Cs sell in small quantities.<br> <br>The B2B storefront with a centralized catalog will have only one unit in the product page. Depending on your business, you will need to customize the storefront to allow a minimum of units for a given SKU.<br> <br>You can expand the catalog by creating kits, but kits would be created for most products, which basically generates a duplicate of the catalog. | Since the catalogs in each environment are independent, the current multistore environment restrictions don't apply.One of the catalogs can be dedicated to only handle B2B sales.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| B2B: orderForm settings          | When using a multistore architecture, all store names will share the same [orderForm settings](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) for Checkout.<br> <br>There are systems that can be integrated to the VTEX Admin and depend on this type of configuration to integrate, such as tax providers.<br> <br>In practice, in a tax provider integration, the orderForm will be called by both B2C and B2B within a multistore environment, which is detrimental for the operation.                                                                                                    | You can create a separate [orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) for each environment, and meet the needs of external checkout integrations of a B2B store.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| Property | Multistore architecture (store names) | Additional environment architecture |
+| - | - | - |
+| Architecture | A single VTEX Admin ([account](https://help.vtex.com/en/tutorial/o-que-e-account-name)) with multiple subaccounts ([store names](https://help.vtex.com/pt/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)). | Two separate VTEX Admin environments ([accounts](https://help.vtex.com/en/tutorial/o-que-e-account-name)). |
+| Segmentation of sales conditions | You can segment applications such as catalog, prices, payments, promotions, and other components through [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) and [bindings](https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W). | Because there are two separate environments, with independent configurations, the merchant has more control over segmentation options for sales conditions in different scenarios. |
+| Type of team | This is recommended when the same company and the same team manage two or more ecommerce stores with similar catalogs and some of the same items, but want to have separate storefronts for the customers to see each experience with a different brand. | Recommended when different teams within the same company manage different online stores. |
+| Storefront | Each store has a different storefront, but all stores are managed through the same VTEX Admin. If you only want to change the website language, without changing the operation of the store, you can use [multibinding](https://help.vtex.com/en/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) and [catalog internationalization](https://developers.vtex.com/docs/guides/catalog-internationalization) to set that up within the same VTEX environment.<br> <br>Note that this architecture is different from a [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl); this account doesn't have its own website. Consumers browse directly on the website of the main account, which acts as a marketplace in this case. | Each account manages its own storefronts in separate VTEX Admins and can use all available options for segmenting storefronts. |
+| VTEX Admin performance | Linking additional [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) to the same main account can affect the performance of the VTEX Admin. Platform features can be slowed down because information needs to be updated in each trade policy.<br> <br>Impact on Admin performance is also to be expected if the product catalog is very extensive (more than 2 million products), which increases indexing time. | You can create multiple [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) for each environment separately.<br> <br>Linking more trade policies to the same main account can affect the performance of the VTEX Admin, which can slow down some platform features.<br> <br>However, since separate environments are used, there is less need to add multiple trade policies. |
+| Costs | Even though adding a store name has no extra cost, you still need to [request an additional trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X?) if you want to differentiate the website storefronts.Learn more about trade policies and segmentation of available settings in [How trade policies work](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). | You need to [request an additional environment](https://help.vtex.com/en/tutorial/contratar-novo-ambiente--tutorials_2542) at the additional cost specified in the VTEX agreement.<br> <br>You may also [request a trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X?) if you want to segment the settings of each environment for different conditions. Learn more about trade policies and segmentation of available settings in [How trade policies work](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). |
+| Operation | When using this type of architecture, you should assess the complexity of managing catalog, promotions, prices, inventory, orders, and payments taking into account the different store names since all the information will be in the same Admin. You can set up [catalog internationalization](https://developers.vtex.com/docs/guides/catalog-internationalization) to sell in different countries. | We recommend this architecture when you have operations in two different countries, and you need to separate the languages in the catalog itself to facilitate the operation of teams that also use different languages to communicate. |
+| Master Data | When a subaccount is created, [Master Data](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) is created separately by default, i.e. each account has its own Master Data. It is possible to replicate the data from one account to another to populate the standard entities (CL, AD and OD) by requesting it via [ticket to our Support team](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). However, customized entities exist only in the account in which they were created and cannot be replicated to other accounts. | Each account will have its own independent [Master Data](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). |
+| Information security | All components are shared between the store names, such as catalog, promotions, prices, and payment settings.<br> <br>It's important to take this into account when different teams in the same company have access to the VTEX Admin. For example, Brand A and Brand B are different store names. Employees of Brand B will be able to view the catalog, prices, and orders of Brand A. | The separate environments prevent access by employees from different teams to the information and settings of components such as catalog, promotions, prices, and payments.<br> <br>For example, Brand A and Brand B are different VTEX environments. Employees of Brand B can't view the catalog, prices, and orders of Brand A.<br> |
+| License Manager | The same [License Manager](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager) manages all users. | Each Admin will have its own [License Manager](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager), and user management will be separate. |
+| Gift card | Subaccounts will have access to the same gift card management, and it will be possible to use the gift cards in different storefronts. | Each Admin will have its own gift card management, and it won't be possible to use a gift card generated in one environment in the other. |
+| Marketplace structure | The marketplace structure doesn't apply between different store names since they share catalog, prices, and inventory.<br> <br> | An environment can be a seller in the other environment and vice versa. Products sold on both websites are based on the seller-marketplace relationship. Learn more in [Configuring a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) and [Configuring a seller on a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP).<br> <br>You can also create franchise accounts to operate as white label sellers since they have different prices, inventories, and logistics. <br> <br>This can be done by requesting an additional environment (if they have some, but not all, items in common in the catalog) or through a franchise account (when the catalogs are completely the same). Learn more in [Choosing between standard account, franchise account, and Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78). |
+| Sitemap | There will be a single [sitemap](https://help.vtex.com/en/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) for the main account, which will be shared between the store names. | Each account has its own independent [sitemap](https://help.vtex.com/en/tutorial/rastreamento-google-search-console-sitemap--tutorials_575). |
+| B2B: Catalog | You can't change the unit of measure configured in the catalog for each [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#catalog). Example: B2B stores sell wholesale, while B2Cs sell in small quantities.<br> <br>The B2B storefront with a centralized catalog will have only one unit in the product page. Depending on your business, you will need to customize the storefront to allow a minimum of units for a given SKU.<br> <br>You can expand the catalog by creating kits, but kits would be created for most products, which basically generates a duplicate of the catalog. | Since the catalogs in each environment are independent, the current multistore environment restrictions don't apply.One of the catalogs can be dedicated to only handle B2B sales. |
+| B2B: orderForm settings | When using a multistore architecture, all store names will share the same [orderForm settings](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) for Checkout.<br> <br>There are systems that can be integrated to the VTEX Admin and depend on this type of configuration to integrate, such as tax providers.<br> <br>In practice, in a tax provider integration, the orderForm will be called by both B2C and B2B within a multistore environment, which is detrimental for the operation. | You can create a separate [orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) for each environment, and meet the needs of external checkout integrations of a B2B store. |
 
 ## Learn more
 
diff --git a/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
index 9ff302bd2..6e4f94144 100644
--- a/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -3,8 +3,8 @@ title: 'Choosing between standard account, franchise account or Seller Portal'
 id: 4S90HzzhMyZESsHqrnUs78
 status: PUBLISHED
 createdAt: 2022-04-20T14:15:50.164Z
-updatedAt: 2022-06-22T21:39:18.954Z
-publishedAt: 2022-06-22T21:39:18.954Z
+updatedAt: 2023-11-22T14:09:05.122Z
+publishedAt: 2023-11-22T14:09:05.122Z
 firstPublishedAt: 2022-04-27T21:42:35.010Z
 contentType: tutorial
 productTeam: Channels
@@ -23,6 +23,8 @@ There are three types of accounts on the VTEX platform and each one allows you t
 - **Franchise account:** It is associated with a standard account, inheriting its catalog. [Franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) can configure their own logistics, payment and prices, and use the VTEX platform modules partially. This type of seller is called a [white label seller](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 - **Seller Portal:** The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) is a feature of the VTEX platform that allows sellers to connect and sell their products on marketplaces of the VTEX ecosystem, regardless of whether the seller already has a VTEX account. The Seller Portal allows partial access to the platform modules, and the seller type can be standard or [white label seller](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 
+<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+
 The table below presents the main use cases for each account type:
 
 | **Seller Portal** | **Standard account** | **Franchise account** |
@@ -61,7 +63,7 @@ See below for comparisons explaining how the Seller Portal, standard accounts an
 | **Aspect** | **Seller Portal** | **Standard account** | **Franchise account** |
 |---------- | ---------- | ---------- | ---------- |
 | Inheriting prices from  another account | When the VTEX marketplace [invites](https://help.vtex.com/en/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A) a seller to the Seller Portal selecting the [White Label Seller](https://help.vtex.com/en/tutorial/white-label-seller--5orlGHyDHGAYciQ64oEgKa) option, the seller products inherit the marketplace prices. However, the seller can edit those prices. | Standard accounts do not inherit prices from another account. Prices must be added in the standard account environment. | Franchise accounts can inherit prices from the main account. |
-| VTEX marketplaces can overwrite seller prices | No. The VTEX marketplace can only set trade rules for sellers. | Yes. | No. The VTEX marketplace can only set trade rules for franchise accounts. |
+| VTEX marketplaces can overwrite seller prices | When the seller created via invitation is a regular seller, its price can be overwritten, but not if it is a white label seller. | Yes. | No. The VTEX marketplace can only set trade rules for franchise accounts. |
 | Possibility of using [Manual Pricing](https://help.vtex.com/en/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS#manual-pricing) | Yes. | Yes. | Yes. |
 
 ## Promotions
diff --git a/docs/tutorials/en/cms-overview.md b/docs/tutorials/en/cms-overview.md
index e224adc30..c040def75 100644
--- a/docs/tutorials/en/cms-overview.md
+++ b/docs/tutorials/en/cms-overview.md
@@ -1,10 +1,10 @@
 ---
 title: 'CMS - Overview'
 id: 2X1xWJi9WmtNylxmggn3ts
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-29T18:36:32.910Z
-updatedAt: 2023-03-29T19:34:13.250Z
-publishedAt: 2023-03-29T19:34:13.250Z
+updatedAt: 2023-07-18T18:36:27.273Z
+publishedAt: 
 firstPublishedAt: 2023-03-29T18:38:26.442Z
 contentType: tutorial
 productTeam: Others
@@ -15,7 +15,7 @@ legacySlug: cms-overview
 subcategory: 3PNmhq67KMmGTBSfIWJdcQ
 ---
 
-![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System) is a feature dedicated to manage content in a constant and practical manner.
 
diff --git a/docs/tutorials/en/cms-store-overview.md b/docs/tutorials/en/cms-store-overview.md
index d7cde92f6..43e21848d 100644
--- a/docs/tutorials/en/cms-store-overview.md
+++ b/docs/tutorials/en/cms-store-overview.md
@@ -19,7 +19,7 @@ The **Store** page allows you to set up your SEO configurations, enable performa
 
 In the VTEX Admin, access **Store Settings > Storefront > Store**, and take a look at the main tools available on the interface.
 
-![CMS Store](https://images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/19924b9aeffed7d9cba408245a46d365/store-en-overview.png)
+![CMS Store](//images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/19924b9aeffed7d9cba408245a46d365/store-en-overview.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Before making changes in the <b>Advanced</b> tab, please contact your developer team and read our documentation <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-best-practices-for-optimizing-performance#enabling-store-settings">Optimizing performance</a> para mais informações.
diff --git a/docs/tutorials/en/collection-highlight-control.md b/docs/tutorials/en/collection-highlight-control.md
index d0ed5801a..2647bee69 100644
--- a/docs/tutorials/en/collection-highlight-control.md
+++ b/docs/tutorials/en/collection-highlight-control.md
@@ -3,8 +3,8 @@ title: 'Collection highlight control'
 id: 1tGdb2ndjqy6yWsk2YwKMu
 status: PUBLISHED
 createdAt: 2018-02-21T19:12:49.216Z
-updatedAt: 2023-03-29T18:01:46.386Z
-publishedAt: 2023-03-29T18:01:46.386Z
+updatedAt: 2023-06-22T17:42:41.479Z
+publishedAt: 2023-06-22T17:42:41.479Z
 firstPublishedAt: 2018-02-21T20:51:49.939Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
 <div class = "alert alert-warning" >
-  <p><b>Warning:</b> there are two ways to configure collections, through the CMS or the Collection module (Beta). This article is about how to <a href = "https://help.vtex.com/en/tutorial/adding-collections-cms--2YBy6P6X0NFRpkD2ZBxF6L">configure collections through the CMS</a>.</p>
+  <p> there are two ways to configure collections, through the CMS or the Collection module (Beta). This article is about how to <a href = "https://help.vtex.com/en/tutorial/adding-collections-cms--2YBy6P6X0NFRpkD2ZBxF6L">configure collections through the Legacy CMS Portal</a>.</p>
 </div>
 
 The `<vtex.cmc:HightLight/>` control (for product pages) or `$product.HightLight` control (for shelves) renders an HTML element with a specific class in the context of products that are part of a collection marked with the __Highlight__ flag.
diff --git a/docs/tutorials/en/conditions-builder-usage-examples.md b/docs/tutorials/en/conditions-builder-usage-examples.md
index aa910f214..d0a04ee9c 100644
--- a/docs/tutorials/en/conditions-builder-usage-examples.md
+++ b/docs/tutorials/en/conditions-builder-usage-examples.md
@@ -25,7 +25,7 @@ To understand __what__ to create the conditions for, see the article [Create Con
 
 UTM (Marketing tag) is an information that relates to the origin of the customer's traffic. Therefore, the app has a block that checks for this type of information. 
 
-![utm_source_english](https://images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
+![utm_source_english](//images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
 
 <div class="alert alert-warning"><strong>Note: </strong>
 It is possible that your store employs customizations and thereby the UTM information contained in the URL is not being passed on to our system. If you use JavaScript customization, read the article <a href="https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho">Por que as utms não estão sendo aplicadas ao carrinho</a>
@@ -43,7 +43,7 @@ __utm_campaign__ informs in __which campaign__ your customer specifically clicke
 
 __utm_medium__ informs which __advertising channel__ , that can be E-mail or a Banner on a site, reached your customer. In the case of images, the block checks if the channel was *email*.  
 
-![utmenglish](https://images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
+![utmenglish](//images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
   
 For each one of these blocks, you can check to see if: 
 
@@ -88,7 +88,7 @@ This block analyzes the total value which exists in the cart.
 Let’s assume that your wanted to put a cheaper price on a shampoo if your customer would buy __exactly 3 units__, but apart from this would also buy __at least 150 reais__ worth of goods.
 The condition to be created will be: 
 
-![Exemplo2](https://images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
+![Exemplo2](//images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
 
 *quantity of this item in the cart is **exactly** 3 
 **and** 
diff --git a/docs/tutorials/en/conecta-la-integration.md b/docs/tutorials/en/conecta-la-integration.md
index 339c0c3c9..070ed6892 100644
--- a/docs/tutorials/en/conecta-la-integration.md
+++ b/docs/tutorials/en/conecta-la-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Conecta Lá integration'
 id: 403fvPYdv2f6VeP0na3awP
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-06-08T17:54:34.361Z
-updatedAt: 2023-03-29T15:27:11.094Z
-publishedAt: 2023-03-29T15:27:11.094Z
+updatedAt: 2024-02-19T20:16:43.888Z
+publishedAt: 
 firstPublishedAt: 2021-06-08T18:36:46.591Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/configure-cartman.md b/docs/tutorials/en/configure-cartman.md
index 13bb0eabf..cf0e62dbc 100644
--- a/docs/tutorials/en/configure-cartman.md
+++ b/docs/tutorials/en/configure-cartman.md
@@ -3,8 +3,8 @@ title: 'Configure Cartman'
 id: 1ACMTStZYkMqB0lTgwg451
 status: PUBLISHED
 createdAt: 2019-09-03T15:02:48.303Z
-updatedAt: 2022-06-15T23:16:07.805Z
-publishedAt: 2022-06-15T23:16:07.805Z
+updatedAt: 2024-03-13T18:18:17.017Z
+publishedAt: 2024-03-13T18:18:17.017Z
 firstPublishedAt: 2019-09-09T18:28:20.208Z
 contentType: tutorial
 productTeam: Shopping
@@ -25,13 +25,14 @@ For official store domains (`www.{yourstore}.com`), you need to [manually activa
 
 This article will cover the following topics:
 
-- [Manually activate Cartman](configure-cartman#activate-cartman-manually)
-- [Cartman features](configure-cartman#cartman-features)
-  - [Get information about items in cart](configure-cartman#get-information-about-items-in-cart)
-  - [Add specific items to cart](configure-cartman#add-specific-items-to-cart)
-  - [Add random items to cart](configure-cartman#add-random-items-to-cart)
-  - [Define marketing data](configure-cartman#define-marketing-data)
-- [Disable Cartman](configure-cartman#disable-cartman) 
+- [Manually activate Cartman](#activate-cartman-manually)
+- [Cartman features](#cartman-features)
+  - [Promotion Simulator](#promotion-simulator) 
+  - [Get information about items in cart](#get-information-about-items-in-cart)
+  - [Add specific items to cart](#add-specific-items-to-cart)
+  - [Add random items to cart](#add-random-items-to-cart)
+  - [Define marketing data](#define-marketing-data)
+- [Disable Cartman](#disable-cartman) 
 
 <div class="alert alert-warning">
   Only the merchant has access to <b>Cartman</b>. Its features are not available for use by users in a store.
@@ -43,15 +44,21 @@ To activate Cartman manually, follow the steps below:
 
 1. Access any of your store's Checkout pages (`https://{accountname}.myvtex.com/checkout/`).
 2. Insira a query string `?cartman=on` no final da URL  (`https://accountname.myvtex.com/checkout?cartman=on`).
-3. In the lower right corner of the screen, click the button <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> to access Cartman.
+3. In the lower right corner of the screen, click the button <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> to access Cartman.
 
 ## Cartman features
 
+### Promotion Simulator
+
+Under **Promotion Simulator**, you can view any promotions created in your store that were applied to the cart, as well as what triggered those promotions. You can also test applying promotions before activating them, including scheduled and inactive promotions.
+
+To learn more about this tool, check the [Promotion Simulator](https://help.vtex.com/en/tutorial/promotion-simulator-beta--4zc8SNqjqeIJ0ZRMhjlnvy) guide.
+
 ### Get information about items in cart
 
 By accessing the **View cart details** menu, it is possible to check the specific information of each of the selected products in the cart.
 
-![Item detail](https://images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/82b5f6305c4ea397b5aaaed9168e6d74/Item_detail.PNG)
+![Item detail](//images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/82b5f6305c4ea397b5aaaed9168e6d74/Item_detail.PNG)
 
 ### Add specific items to cart
 
@@ -61,7 +68,7 @@ In **Add items by SKU ID**, new items can be added to the cart according to thei
 - **Quantity of each item**: indication of how many SKU units will be added to the cart.
 - **Seller ID**: identification number of the seller who will deliver the item.
 
-![Add items by SKU ID](https://images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/969209879fc26ab3ea769e75c8730bda/Add_items_by_SKU_ID.PNG)
+![Add items by SKU ID](//images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/969209879fc26ab3ea769e75c8730bda/Add_items_by_SKU_ID.PNG)
 
 ### Add random items to cart
 
@@ -75,7 +82,7 @@ In **Add random items**, new items from the store catalog can be added to the ca
 - Seller ID
 - Price range (Price from / Price up to)
 
-![Add random items](https://images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/66f12cfd13a5abb0e4e50251a719ccee/Add_random_items.PNG)
+![Add random items](//images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/66f12cfd13a5abb0e4e50251a719ccee/Add_random_items.PNG)
 
 ### Define marketing data
 
@@ -87,7 +94,7 @@ In the **Set marketing data option**, you can apply discount coupons to specific
 - **utmi_cp**: internal utm used to define when a certain promotion will be applied, according to the utm described in the order URL. 
 - **Cupom**: discount coupon code to be added to cart.
 
-![Set marketing data](https://images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/03ea65c5ca723df8a38ab99dc78301c5/Set_marketing_data.PNG)
+![Set marketing data](//images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/03ea65c5ca723df8a38ab99dc78301c5/Set_marketing_data.PNG)
 
 To learn more about UTMs and UTMIs, go to [What are utm_source, utm_campaign, and utm_medium](https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii#) and [What are the internal UTMs utmi_cp, utmi_pc and utmi_p](https://help.vtex.com/en/tutorial/o-que-sao-as-utms-internas-utmi_cp-utmi_pc-e-utmi_p#).
 
@@ -96,7 +103,7 @@ To learn more about UTMs and UTMIs, go to [What are utm_source, utm_campaign, an
 Cartman can be deactivated at any time as required by the merchant. To disable it, follow the steps below:
 
 1. Access any of your store's Checkout pages (`https://{accountname}.myvtex.com/checkout/`).
-2. In the lower right corner of the screen, click the button  <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
+2. In the lower right corner of the screen, click the button  <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
 3. At the bottom of Cartman's menu, click  `Disable Cartman`.
 
 <div class="alert alert-info">
diff --git a/docs/tutorials/en/configure-direct-consumer-credit-cdc-by-losango.md b/docs/tutorials/en/configure-direct-consumer-credit-cdc-by-losango.md
index 1527a92b5..62158b2b7 100644
--- a/docs/tutorials/en/configure-direct-consumer-credit-cdc-by-losango.md
+++ b/docs/tutorials/en/configure-direct-consumer-credit-cdc-by-losango.md
@@ -3,8 +3,8 @@ title: 'Configure direct consumer credit (CDC) by Losango'
 id: 4vfoIULHTs8S9t3WDyldCE
 status: PUBLISHED
 createdAt: 2020-11-23T20:29:21.353Z
-updatedAt: 2023-03-30T15:42:27.683Z
-publishedAt: 2023-03-30T15:42:27.683Z
+updatedAt: 2024-01-23T18:47:11.153Z
+publishedAt: 2024-01-23T18:47:11.153Z
 firstPublishedAt: 2020-11-23T21:04:18.389Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
index 1e8b26a32..d10d9e14e 100644
--- a/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
@@ -45,7 +45,7 @@ Here, the common property of the clients will be that they are also employees of
 This article assumes that the employees are properly registered with a boolean field `isEmployee` set to true in their respective documents for the CL data entity, as shown in the figure below. 
 
 If they are not, check the article [Creating a field in Master Data](https://help.vtex.com/en/tutorial/how-can-i-create-field-in-master-data) to create a field that identifies the employees and properly configure it for each document corresponding to the employees.
-![Employee field](https://images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
+![Employee field](//images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
 
 <div class="alert alert-info" role="alert">There are many details to completely configure a benefit. If you need additional information on this matter, check out the article <a href="https://help.vtex.com/en/tutorial/creating-promotions-2">Creating promotions</a>.</div>
 
@@ -60,4 +60,4 @@ With the field configured, the benefit can be created by following the steps bel
 7. In the end of the page, click on the **Save** button.
 
 After that, the benefit should already be working as configured. The discount is shown only in the shopping cart. The image below shows an example with 99% off.
-![Shopping cart with discount](https://images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
+![Shopping cart with discount](//images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
diff --git a/docs/tutorials/en/configure-payment-with-pix-at-nubank.md b/docs/tutorials/en/configure-payment-with-pix-at-nubank.md
index c9c52f1f0..fe6a39b48 100644
--- a/docs/tutorials/en/configure-payment-with-pix-at-nubank.md
+++ b/docs/tutorials/en/configure-payment-with-pix-at-nubank.md
@@ -3,8 +3,8 @@ title: 'Configure payment with Pix at Nubank'
 id: 2pJBJdtkvyn645rL2sxyJy
 status: PUBLISHED
 createdAt: 2022-07-19T16:38:08.465Z
-updatedAt: 2023-03-24T15:03:05.135Z
-publishedAt: 2023-03-24T15:03:05.135Z
+updatedAt: 2024-01-23T19:11:23.258Z
+publishedAt: 2024-01-23T19:11:23.258Z
 firstPublishedAt: 2022-07-19T16:56:30.888Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/configure-payment-with-shopfacil.md b/docs/tutorials/en/configure-payment-with-shopfacil.md
new file mode 100644
index 000000000..9f71cbe41
--- /dev/null
+++ b/docs/tutorials/en/configure-payment-with-shopfacil.md
@@ -0,0 +1,18 @@
+---
+title: 'Configure payment with ShopFácil'
+id: 4v3z3CLrgZ2bByMx7uoMeG
+status: PUBLISHED
+createdAt: 2023-07-14T16:49:07.504Z
+updatedAt: 2024-01-23T21:31:46.325Z
+publishedAt: 2024-01-23T21:31:46.325Z
+firstPublishedAt: 2023-07-14T16:57:55.320Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configure-payment-with-shopfacil
+locale: en
+legacySlug: configure-payment-with-shopfacil
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to English speaking countries.</div>
diff --git a/docs/tutorials/en/configure-seller-regionalization.md b/docs/tutorials/en/configure-seller-regionalization.md
index e515860f1..a3d97ef69 100644
--- a/docs/tutorials/en/configure-seller-regionalization.md
+++ b/docs/tutorials/en/configure-seller-regionalization.md
@@ -3,8 +3,8 @@ title: 'Configure seller regionalization'
 id: 32t6wLpQCEnumoh8TjT5fw
 status: PUBLISHED
 createdAt: 2022-08-26T13:58:10.648Z
-updatedAt: 2022-08-26T18:34:14.924Z
-publishedAt: 2022-08-26T18:34:14.924Z
+updatedAt: 2023-07-17T12:11:40.614Z
+publishedAt: 2023-07-17T12:11:40.614Z
 firstPublishedAt: 2022-08-26T18:34:14.924Z
 contentType: tutorial
 productTeam: Shopping
@@ -41,7 +41,7 @@ With the use of **Region**, if the customer logs in to the store during the sele
 To activate **Region** in your store, you need to perform the following steps:
 
 1. [Setting up price and availability of SKUs by Region](https://help.vtex.com/en/tutorial/setting-up-price-and-availability-of-skus-by-region--12ne58BmvYsYuGsimmugoc#)
-2. [Enable Region functionality](https://developers.vtex.com/vtex-rest-api/docs/how-to-configure-region-feature-sku)
+2. [Enable Region functionality](https://developers.vtex.com/docs/guides/enable-the-region-for-skus)
 
 <div class="alert alert-info">
   <b>Region</b> is currently available for use in all VTEX stores in v2. Learn more in <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
diff --git a/docs/tutorials/en/configure-template-in-smartcheckout-update.md b/docs/tutorials/en/configure-template-in-smartcheckout-update.md
index e4df3c2a3..eb70119e8 100644
--- a/docs/tutorials/en/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/en/configure-template-in-smartcheckout-update.md
@@ -37,11 +37,11 @@ Each registered site corresponds to a multidomain (if the account has contracted
 
 Creation of the new website:
 
-![en.smartcheckout1](https://images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png)
+![en.smartcheckout1](//images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png)
 
 Account Name Access:
 
- ![en.smartcheckout2](https://images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
+ ![en.smartcheckout2](//images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
 
 ## Editing and configuring website 
 
@@ -56,14 +56,14 @@ Account Name Access:
    - __Pages__: display existing pages for the website.
 
 Example of existing sites in the same account:
-![EN Cards Portal](https://images.ctfassets.net/alneenqid6w5/3PYf4oomjW0HmBznIBYi2N/2e81a23b6f03bcb847fd7407baf58c1a/EN_Cards_Portal.png)
+![EN Cards Portal](//images.ctfassets.net/alneenqid6w5/3PYf4oomjW0HmBznIBYi2N/2e81a23b6f03bcb847fd7407baf58c1a/EN_Cards_Portal.png)
 
 Example of available pages for a website:
-![en.smartcheckout3](https://images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
+![en.smartcheckout3](//images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
 
 If you want to __delete__ a site, click on the delete button for the desired site, as in the example below:
 
-![en.smartcheckout5](https://images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/020a02fc80da75fbf27794714b6d7c2c/en.smartcheckout5.png)
+![en.smartcheckout5](//images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/020a02fc80da75fbf27794714b6d7c2c/en.smartcheckout5.png)
 
 We'll now have a more in-depth look at the following options menu settings: __Code__ and __Checkout__, being responsible for configuring the pages *checkout* and *order placed* pages.
 
@@ -80,7 +80,7 @@ We'll now have a more in-depth look at the following options menu settings: __Co
   <li><b>Calculation of Delivery Options (Beta and Stable)</b>: select whether the freight calculation will be done from the spreadsheet or by geolocation.</li>
   </ul>
 
-![en.smartcheckout6](https://images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
+![en.smartcheckout6](//images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
 
 ## Configure code
 
@@ -90,7 +90,7 @@ We'll now have a more in-depth look at the following options menu settings: __Co
 
 Example:
 
-![en.smartcheckout7](https://images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
+![en.smartcheckout7](//images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
 
 ### Configuring templates from the "Code" menu
 
@@ -110,27 +110,27 @@ Below are examples of how the codes present in the __checkout-header__, __checko
 
 - Template __checkout-header__ and website page header:
 
-![en.smartcheckout10](https://images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) 
+![en.smartcheckout10](//images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) 
 
-![en.smartcheckout11](https://images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
+![en.smartcheckout11](//images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
 
 - Template __checkout-footer__ and website page footer:
 
-![en.smartcheckout8](https://images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png)
+![en.smartcheckout8](//images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png)
 
- ![en.smartcheckout9](https://images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
+ ![en.smartcheckout9](//images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
 
 - Template __vtex-checkout__ and cart page at Checkout:
 
-![en.smartcheckout12](https://images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) 
+![en.smartcheckout12](//images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) 
 
-![en.smartcheckout13](https://images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
+![en.smartcheckout13](//images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
 
 - Template __vtex-orderPlaced__ and confirmed order page:
 
-![en.smartcheckout18](https://images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png)
+![en.smartcheckout18](//images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png)
 
-![en.smartcheckout19](https://images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
+![en.smartcheckout19](//images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
 
 ### Multi-domain accounts
 
diff --git a/docs/tutorials/en/configure-template-in-the-smartcheckout.md b/docs/tutorials/en/configure-template-in-the-smartcheckout.md
index f97421165..68032186a 100644
--- a/docs/tutorials/en/configure-template-in-the-smartcheckout.md
+++ b/docs/tutorials/en/configure-template-in-the-smartcheckout.md
@@ -32,7 +32,7 @@ Now fill out the following fields according to the instructions:
 
 See picture below:
 
-![en.smartcheckout1](https://images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png) ![en.smartcheckout2](https://images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
+![en.smartcheckout1](//images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png) ![en.smartcheckout2](//images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
 
 Click on Save to conclude the registration of the new site.
 
@@ -47,17 +47,17 @@ As shown in the next picture, on clicking the Site name the system displays all
 - Code: Site-related templates
 - Pages: Displays the pages that exist for the site. By default, two pages are created, **checkout **and **checkout/orderPlaced**. As already mentioned at the beginning of this post, the **checkout **page represents the shopping basket, personal data, address and payment method pages. The **checkout/orderPlaced **page represents the Purchase Confirmation page**
 
-![en.smartcheckout3](https://images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
+![en.smartcheckout3](//images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
 
 In **Pages**, it is possible to** Create **new pages, **Edit** and **Exclude **existing pages. See the following two pictures illustrating **Editing **and **Exclusion**. Creation follows the same rules as editing.
 
 Editing pages:
 
-![en.smartcheckout4](https://images.ctfassets.net/alneenqid6w5/7to0u1evDi9wENUr7bObaq/17162c0dc68db11895017d4d75d273f9/en.smartcheckout4.png)
+![en.smartcheckout4](//images.ctfassets.net/alneenqid6w5/7to0u1evDi9wENUr7bObaq/17162c0dc68db11895017d4d75d273f9/en.smartcheckout4.png)
 
 Excluding pages:
 
-![en.smartcheckout5](https://images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/e10b9a0784b5061594b3690ed6a43ca3/en.smartcheckout5.png)
+![en.smartcheckout5](//images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/e10b9a0784b5061594b3690ed6a43ca3/en.smartcheckout5.png)
 
 In **Checkout**, we can edit the fields below:
 
@@ -68,39 +68,39 @@ In **Checkout**, we can edit the fields below:
 
 Below is a picture illustrating how to fill out this form:
 
-![en.smartcheckout6](https://images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
+![en.smartcheckout6](//images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
 
 In **Code**, on the right, all the Site-related templates will be displayed. By default, the system configures the templates exemplified in the picture below:
 
-![en.smartcheckout7](https://images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
+![en.smartcheckout7](//images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
 
 Of these templates, the only ones that cannot be changed are **vtex-checkout **and **vtex-orderPlaced**. These templates correspond to the native operation of the platform, that is, they render the main content of these pages, both the checkout and the orderPlaced.
 
 In the next picture, we show the area affected at the checkout by the setting of the **checkout-footer **template. This is merely an example of an empty template.
 
-![en.smartcheckout8](https://images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png) ![en.smartcheckout9](https://images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
+![en.smartcheckout8](//images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png) ![en.smartcheckout9](//images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
 
 In the next picture, we have an equivalent example to the previous one; however, this time with the HTML code filled out. Note that the code filled out on the left corresponds to the upper right-hand area. This is the **checkout-header **template.
 
-![en.smartcheckout10](https://images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) ![en.smartcheckout11](https://images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
+![en.smartcheckout10](//images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) ![en.smartcheckout11](//images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
 
 As we can see in the next picture, all templates with the **checkout** prefix will be used on all Checkout pages. In this example, we are on the Forma de Pagamento page. Note that the header loaded is the same as in the previous example.
 
-![en.smartcheckout12](https://images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) ![en.smartcheckout13](https://images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
+![en.smartcheckout12](//images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) ![en.smartcheckout13](//images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
 
 Just as in the **checkout **templates, the same happens with the orderPlaced templates. In other words, templates with the **orderPlaced** prefix only correspond to the OrderPlaced (Purchase Confirmation) page.
 
-![en.smartcheckout14](https://images.ctfassets.net/alneenqid6w5/3R5BgiNGjgvwGord10U26t/567703d54d381bd197a5e674b035802b/en.smartcheckout14.png) ![en.smartcheckout15](https://images.ctfassets.net/alneenqid6w5/pzZig7wTU8YNCBG9wqFYe/d6c1c563cc7ebad9df6cfa1878cd8730/en.smartcheckout15.png)
+![en.smartcheckout14](//images.ctfassets.net/alneenqid6w5/3R5BgiNGjgvwGord10U26t/567703d54d381bd197a5e674b035802b/en.smartcheckout14.png) ![en.smartcheckout15](//images.ctfassets.net/alneenqid6w5/pzZig7wTU8YNCBG9wqFYe/d6c1c563cc7ebad9df6cfa1878cd8730/en.smartcheckout15.png)
 
 As explained above, the only templates where alterations are not permitted are **vtex-checkout** and **vtex-orderPlaced**. These templates render the basic content of the Checkout and OrderPlaced pages. Below are examples of the content rendered by the templates.
 
 **vtex-checkout **template:
 
-![en.smartcheckout16](https://images.ctfassets.net/alneenqid6w5/57XEgJ13YRpGLREovFUyNU/8a842c82fb418f9df729202bc52c7548/en.smartcheckout16.png) ![en.smartcheckout17](https://images.ctfassets.net/alneenqid6w5/4XmnSmdoN3DugDECxgbeOD/0082a842c288dad52d577bb52722822b/en.smartcheckout17.png)
+![en.smartcheckout16](//images.ctfassets.net/alneenqid6w5/57XEgJ13YRpGLREovFUyNU/8a842c82fb418f9df729202bc52c7548/en.smartcheckout16.png) ![en.smartcheckout17](//images.ctfassets.net/alneenqid6w5/4XmnSmdoN3DugDECxgbeOD/0082a842c288dad52d577bb52722822b/en.smartcheckout17.png)
 
 **vtex-orderPlaced **template:
 
-![en.smartcheckout18](https://images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png) ![en.smartcheckout19](https://images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
+![en.smartcheckout18](//images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png) ![en.smartcheckout19](//images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
 
 Multi-domain accounts can only use one site, if the need arises for specific configurations. This is because, although only one Site exists, the platform includes a class in the tag &lt;body&gt; according to the domain accessed. This makes it simple to apply different layouts to the same site.
 
diff --git a/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md b/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md
index 684629e6f..1f368c1e4 100644
--- a/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md
+++ b/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md
@@ -34,7 +34,7 @@ After you determine the discount at Checkout, you need to link the SKU to the pa
 3. Select the template of your product page.
 4. In the `skuPrice` property, add the `paymentSystemId` variable with the ID of the chosen payment method.
 
-![Screenshot 2020-12-18 Criar preço à vista](https://images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
+![Screenshot 2020-12-18 Criar preço à vista](//images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
 
 6. Click on __Save Template__ in the upper right corner.
 
diff --git a/docs/tutorials/en/configuring-a-marketplace-trade-policy.md b/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
index 59c9a26f4..c9c338c91 100644
--- a/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring a marketplace trade policy'
 id: tutorials_404
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T22:06:38.350Z
-updatedAt: 2022-12-08T17:30:09.288Z
-publishedAt: 2022-12-08T17:30:09.288Z
+updatedAt: 2024-06-14T14:19:35.130Z
+publishedAt: 2024-05-15T00:18:56.253Z
 firstPublishedAt: 2017-04-27T23:03:23.796Z
 contentType: tutorial
 productTeam: Channels
@@ -30,21 +30,23 @@ Learn how you can configure trade policies in the following modules when your st
 
 To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `Create a trade policy`.
 
-Requesting additional trade policies to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores is free of charge.
+Requesting additional trade policies to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), [certified connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores is free of charge.
+
+<div class=alert alert-warning> If the same trade policy is applied to a certified connector and a partner connector, there is no fee exemption.</div>
 
 ## Store setup
 Creating a new trade policy is the first step in defining the conditions that apply to each marketplace in which a seller operates. Sellers can create multiple trade policies, or apply the same policy to more than one marketplace.
 
 This configuration can be done in the *Store setup* module, on the *Trade policies* page. You must [create a new trade policy](https://help.vtex.com/en/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) when the settings for catalog, price, promotions, logistics and payments are different between the marketplaces in which sellers sell their products. 
 
-![EN Add Politica comercial](https://images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e74c92388925fad7a099da236e616122/EN_Add_Politica_comercial.jpg)
+![EN Add Politica comercial](//images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e74c92388925fad7a099da236e616122/EN_Add_Politica_comercial.jpg)
 
 ## Orders management
 After creating a trade policy, you must associate it with each marketplace in which the seller sells products by adding them as [affiliates](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). This is how sellers identify which trade policy operates in each marketplace. If your store sells products in three different marketplaces, you must create three affiliates: one for each marketplace.
 
 This can be configured in the *Settings* page of the *Order management* module, where you can add affiliates. Even if you create several, it is important to note that only one trade policy will operate in the marketplace at a time. 
 
-![EN Afiliado](https://images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/9f59fda62a85e1df3ac2c14737853493/EN_Afiliado.jpg)
+![EN Afiliado](//images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/9f59fda62a85e1df3ac2c14737853493/EN_Afiliado.jpg)
 *In the example above, the affiliate "Amazon" is associated with trade policy "1".* 
 
 ## Promotions
@@ -57,7 +59,7 @@ This configuration can be done in the *Promotions* module in all [promotions](ht
 
 If no trade policy is selected, the promotion will be available in all sales channels.
 
-![EN Promoções Politica Comercial](https://images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/e0e31dc018a61402bbacd629a4632275/EN_Promo____es_Politica_Comercial.jpg)
+![EN Promoções Politica Comercial](//images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/e0e31dc018a61402bbacd629a4632275/EN_Promo____es_Politica_Comercial.jpg)
 
 *In the example above, the promotion will only apply to orders from the "Marketplace-BRL" and "Argentina-ARS" trade policies, where the store operates as a seller. The promotion will not be available on the VTEX storefront.* 
 
@@ -66,7 +68,7 @@ Sellers who process payment for their product sales in a marketplace can create
 
 This configuration can be done in the *Payments* module by [creating a special condition](https://help.vtex.com/en/tutorial/condicoes-especiais--tutorials_456) and associating it with the trade policies of your choice.
 
-![EN Pagamento Politica comercial](https://images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/f7ca24768f12e60df2f86469dd380fe4/EN_Pagamento_Politica_comercial.jpg)
+![EN Pagamento Politica comercial](//images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/f7ca24768f12e60df2f86469dd380fe4/EN_Pagamento_Politica_comercial.jpg)
 
 *In the example above, the payment condition is associated with the "Marketplace" trade policy. This makes the payment condition available only to sales channels associated with this commercial policy.*
 
@@ -79,7 +81,7 @@ This configuration can be done in the VTEX *Catalog*, when [adding products](htt
 We do not recommend attaching trade policies to collections, when determining the product assortment, especially for external marketplaces. When a product is withdrawn from the collection associated to a trade policy, the VTEX system does not warn the marketplace of that update, making the product still available in the marketplace.
   </div>
 
-![EN Catálogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/43607a48ab2590d2f58a50c8281f4879/EN_Cat__logo_Politica.jpg)
+![EN Catálogo Politica](//images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/43607a48ab2590d2f58a50c8281f4879/EN_Cat__logo_Politica.jpg)
 
 *In the example above, the product will only be available to sales channels using the "Carrefour" and "Marketplace" trade policies.*
 
@@ -91,7 +93,7 @@ This configuration can be done in the *Prices* module by means of trade policies
 - [Price rules](https://help.vtex.com/en/tutorial/configurar-regra-de-preco-para-politica-comercial--5LQMLwcUcEGCWK6SMI6cEM): to determine a markup for specific categories and brands.
 - [Fixed prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy): to differentiate prices for specific products.
 
-![EN Regra de preço](https://images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/1e299eba8c5e102543d8db27175a9086/EN_Regra_de_pre__o.jpg)
+![EN Regra de preço](//images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/1e299eba8c5e102543d8db27175a9086/EN_Regra_de_pre__o.jpg)
 
 *In the example above, the price rule applied a markup to the "Marketplace" trade policy for products in the "Fera-Fashion category".*
 
@@ -101,11 +103,11 @@ Sellers can set up specific [logistics routes](https://help.vtex.com/en/tracks/l
 
 Both settings can be configured on the *Shipping strategy* page. When creating a [loading dock](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj), you must indicate which trade policies will be associated with it. This makes the shipping policies associated with this loading dock available to the linked trade policies. Then, you must link the desired [inventory](https://help.vtex.com/en/tutorial/gerenciar-estoque) to a loading dock to make the inventory available to the trade policies associated with the loading dock.
 
-![EN Doca politica](https://images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/55d339d25b6d5e94095f237f87fe0246/EN_Doca_politica.jpg)
+![EN Doca politica](//images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/55d339d25b6d5e94095f237f87fe0246/EN_Doca_politica.jpg)
 
 *In the example above, the loading dock is associated with the commercial policy "Marketplace", which will be linked to the carrier "Carrier A".*
 
-![EN Estoque Politica](https://images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/ad0a2568d1f7be56399c798d274d526a/EN_Estoque_Politica.jpg)
+![EN Estoque Politica](//images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/ad0a2568d1f7be56399c798d274d526a/EN_Estoque_Politica.jpg)
 *In the example above, the inventory is associated with "Dock A", so this will be the inventory used by the trade policies linked to "Dock A".* 
 
 ## Integrations
@@ -113,7 +115,7 @@ Trade policies also apply to all integrations in which your store sells products
 
 [Integrations](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#vender-em-marketplace) can be configured in the *Settings* page of the *Integrations* module. Usually, each channel requires specific commercial conditions, but it is possible that different channels share the same trade policy.
 
-![EN Integracao Politica](https://images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/dd3b2b730cfd16c4a9bbcca8b253c473/EN_Integracao_Politica.jpg)
+![EN Integracao Politica](//images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/dd3b2b730cfd16c4a9bbcca8b253c473/EN_Integracao_Politica.jpg)
 *In the example above, the "Marketplace" trade policy applies to the Google Shopping integration.*
 
 ## Learn more
diff --git a/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md b/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md
index f894544f3..3bcc8b0b5 100644
--- a/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md
+++ b/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md
@@ -3,8 +3,8 @@ title: 'Configuring a pricing rule for a sales policy'
 id: 5LQMLwcUcEGCWK6SMI6cEM
 status: PUBLISHED
 createdAt: 2018-03-19T17:49:25.791Z
-updatedAt: 2023-03-29T20:00:47.266Z
-publishedAt: 2023-03-29T20:00:47.266Z
+updatedAt: 2023-08-21T17:23:00.178Z
+publishedAt: 2023-08-21T17:23:00.178Z
 firstPublishedAt: 2018-03-19T18:26:04.279Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,7 +25,7 @@ By default, the __base price__ registered for a product is applied to all sales
 
 To create a pricing rule specific to a sales policy, follow the steps below:
 
-1. In the VTEX Admin, go to *Prices > Price rules*, or type *Price rules* in the search bar at the top of the page.
+1. In the VTEX Admin, go to **Prices > Price rules**, or type **Price rules** in the search bar at the top of the page.
 2. Click on `New rule`.
 3. In the __Trade policy__ field, choose the desired trade policy.
 4. Choose whether the rule will be applied to __all products__ of this policy or __only in categories and brands chosen__.
diff --git a/docs/tutorials/en/configuring-a-registered-boleto.md b/docs/tutorials/en/configuring-a-registered-boleto.md
index 5c236ceed..586688ece 100644
--- a/docs/tutorials/en/configuring-a-registered-boleto.md
+++ b/docs/tutorials/en/configuring-a-registered-boleto.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring a registered "boleto" (Brazilian off-line payment method)'
 id: frequentlyAskedQuestions_2867
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:46:00.197Z
-updatedAt: 2020-11-24T13:14:10.947Z
-publishedAt: 2020-11-24T13:14:10.947Z
+updatedAt: 2024-03-18T18:09:27.673Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:08:27.705Z
 contentType: tutorial
 productTeam: Financial
@@ -26,22 +26,13 @@ VTEX has adapted to this measure and there are now several ways of making this p
 - [Boleto Santander](https://help.vtex.com/en/tutorial/configurar-boleto-registrado-santander--67siNqkC7mcgy2GWUYimaa)
 - [Boleto Itaú](https://help.vtex.com/en/tutorial/configurar-boleto-registrado-itau-itau-registrado--6MEHf1oDTOkuWM2CaYi4gu)
 - [Itaú Shopline](https://help.vtex.com/en/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq)
-- [Bradesco Registrado](https://help.vtex.com/en/tutorial/configurar-boleto-registrado-bradesco--bbnXBjvKOkWYiOosmASiA)
+- [Boleto Bradesco Registrado](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-bradesco--bbnXBjvKOkWYiOosmASiA)
 
 In addition, VTEX has an automatic integration for Bradesco and Itaú Shopline registered "boletos". However, for "boletos" created without an acquisition, the reconciliation is done through a .RET file.
 
-Every client should get this file from their respective bank. In this specific example, we use Itaú Registrado and Santander. We emphasize that these files must necessarily follow the standard established by Febraran.
+Every client should get this file from their respective bank. In this specific example, we use Itaú Registrado and Santander. We emphasize that these files must necessarily follow the standard established by Febraban.
 
-For other banks you have to use one of the following gateways:
-
-- Braspag
-- PagSeguro Transparente
-- Mundipagg
-- Moip
-- MercadoPago Transparente
-- Pagar.Me
-- CieloV3
-- Adyen
+For other banks, you must use one of the gateways available in your store's Admin (eg Braspag, PagSeguro Transparente, CieloV3, among others).
 
 The cost of a registered "boleto" is different from that of the traditional "boleto" and varies according to your agreement with the bank. Make sure you plan this properly and control your margin.
 
@@ -54,6 +45,4 @@ The creation of this number by VTEX guarantees that each "boleto" is unique and
 ## Related articles
 
 - [How to configure gateway affiliation](/en/tutorial/registering-gateway-affiliations/)
-- [How to configure PagSeguro transparente](/en/tutorial/how-to-configure-the-pagseguro-without-redirect-option-transparent)
-- [Configuring Itaú registered ticket](/en/tutorial/setting-up-itau-registered-ticket)
 
diff --git a/docs/tutorials/en/configuring-a-santander-registered-boleto.md b/docs/tutorials/en/configuring-a-santander-registered-boleto.md
index e123f1885..bfc7d0d20 100644
--- a/docs/tutorials/en/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/en/configuring-a-santander-registered-boleto.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring a Santander registered "boleto"'
 id: 67siNqkC7mcgy2GWUYimaa
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-12-04T19:04:02.215Z
-updatedAt: 2023-03-30T16:12:20.970Z
-publishedAt: 2023-03-30T16:12:20.970Z
+updatedAt: 2024-03-18T18:03:25.298Z
+publishedAt: 
 firstPublishedAt: 2019-01-25T17:15:35.225Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/configuring-affiliates.md b/docs/tutorials/en/configuring-affiliates.md
index 3c2e4d4a4..0ab5925dc 100644
--- a/docs/tutorials/en/configuring-affiliates.md
+++ b/docs/tutorials/en/configuring-affiliates.md
@@ -3,8 +3,8 @@ title: 'Configuring affiliates'
 id: tutorials_187
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:31.422Z
-updatedAt: 2023-03-29T18:05:11.905Z
-publishedAt: 2023-03-29T18:05:11.905Z
+updatedAt: 2024-01-08T18:13:15.897Z
+publishedAt: 2024-01-08T18:13:15.897Z
 firstPublishedAt: 2017-04-27T23:00:46.992Z
 contentType: tutorial
 productTeam: Channels
@@ -15,9 +15,9 @@ legacySlug: configuring-affiliates
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-It will only be necessary to register [affiliates](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) in the conditions where the store acts as a seller in a marketplace, because the seller creates an affiliate code to identify each marketplace.
+At VTEX, the [affiliate](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) is an identification code of the marketplace for the seller. The [VTEX seller](https://help.vtex.com/en/tutorial/integrating-with-marketplace/#being-a-vtex-seller) needs to configure an affiliate code in order to integrate with a [VTEX marketplace](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace), and this configuration is only necessary when both marketplace and seller are VTEX stores.
 
-This configuration is only required in the case of integrations where the marketplace and the seller are VTEX stores or [when the marketplace is not a VTEX store and has no configuration using the Integrations module.](/en/tutorial/integrating-with-marketplace/) In these cases, the affiliate is created automatically.
+When the marketplace is not a VTEX store (as in [external integrations](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-an-external-marketplace)), or when the store integrates with a [certified marketplace](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-marketplace) (such as Amazon or Mercado Livre), the affiliate code is automatically created by the platform.
 
 ## How to set it up
 
diff --git a/docs/tutorials/en/configuring-banners.md b/docs/tutorials/en/configuring-banners.md
new file mode 100644
index 000000000..e2e60f986
--- /dev/null
+++ b/docs/tutorials/en/configuring-banners.md
@@ -0,0 +1,70 @@
+---
+title: 'Configuring Banners'
+id: 3AdnZhxAhgmlxJjpa02Svc
+status: PUBLISHED
+createdAt: 2024-06-27T16:32:24.435Z
+updatedAt: 2024-06-27T16:33:49.674Z
+publishedAt: 2024-06-27T16:33:49.674Z
+firstPublishedAt: 2024-06-27T16:33:39.573Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configuring-banners
+locale: en
+legacySlug: configuring-banners
+subcategory: z6qcw06Z38YDu1fOcu9Jn
+---
+
+To set up a banner, follow the steps below:
+
+1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2. Click **Banners**.
+3. Click <i class="fas fa-plus"></i> `New`.
+4. Complete the banner fields.
+5. To finish, click `Save`.
+
+After configuring the banner, you have to add it to a page on your store. To do that, follow the steps described in the [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner) guide.
+
+<div class="alert alert-info">
+<p> This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: Multilanguage settings (Beta)</a>.</p>
+</div>
+
+![banner-form-en](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
+
+## Banner fields
+
+To add a banner, the following fields need to be completed:
+
+### General Information
+
+* **Name**: Name of the banner.
+* **Position**: Position where the banner will be displayed on the search results page. Banners can be positioned in four different areas of the site page. The placing is up to the retailer and will be determined by the option selected in this field or defined through [store-theme blocks](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner#props).
+
+### Type
+
+* **Banner type**: Banner content that will be created. The banner can be  HTML code or an image URL:
+    * **HTML**: The administrator can add media, YouTube videos, images, or code lines, such as JavaScript, to the HTML field.
+    * **Image**: The system requests the image URL that will be used and the banner destination link.
+        * Image URL
+        * Destination link
+* **Time zone**: Time zone for the times configured in the banner.
+* **Start date**: Date when the banner will start being available.
+* **Start time**: Time when the banner will start being available.
+* **End date**: Date when the banner will stop being available. This allows the administrator to schedule future campaigns, which makes them easier to control.
+* **End time**: Time when the banner will stop being available.
+* **Locales:** Languages to which the banner will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+### Trigger Rules
+
+**Trigger rules** are a group of conditional terms or filters that are applied to every search. You need to have at least one condition, whether by term or by filter.
+
+Click <i class="fas-solid fa-link"></i> `Autofill from URL` to add the URL of the search page to the trigger rules that will be applied.
+
+![banner-url-en](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
+
+Click <i class="fas fa-plus"></i> `Add condition` to create a rule. Rules can be of two types:
+
+* **Term**: The word searched by the customer that will be associated with the rule.
+* **Filter**: Predefined attribute that can be selected which restricts the search results. You can select categories, departments, and subcategories.
+
+Click `Clear Rules` to delete all the rules.
diff --git a/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
new file mode 100644
index 000000000..6ddcc365e
--- /dev/null
+++ b/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -0,0 +1,67 @@
+---
+title: 'Configuring bulk data import for organizations and cost centers'
+id: 41FwcZHF3GctzKcgyKGaoF
+status: PUBLISHED
+createdAt: 2024-04-25T11:45:15.945Z
+updatedAt: 2024-05-21T14:04:56.238Z
+publishedAt: 2024-05-21T14:04:56.238Z
+firstPublishedAt: 2024-04-29T18:38:46.485Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configuring-bulk-data-import-for-organizations-and-cost-centers
+locale: en
+legacySlug: configuring-bulk-data-import-for-organizations-and-cost-centers
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+Bulk data import simplifies the process of updating and maintaining information for buyer organizations, their users (members), and cost centers.
+
+<div class = "alert alert-info">
+Before configuring the bulk import feature, you should have the <a href="https://developers.vtex.com/docs/apps/vtex.b2b-suite">B2B Suite</a> installed in your store.
+</div>
+
+Here's how to import data in bulk into the VTEX platform:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations & Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+2. In the Organizations tab, click **New**, and then Bulk Import. Click the Upload button and select your **XLSX file**, or drag and drop the file into the dashed area. The imported file must be smaller than 50 MB.
+
+<div class = "alert alert-info">
+If necessary, download a template file by clicking VTEX File Template at the bottom of the import window and enter the import data.
+</div>
+
+<ol start="3">
+	<li>Once the platform has verified the imported file and found no errors, click Import.</li>
+</ol>
+
+<div class = "alert alert-info">
+If the platform detects any errors, check the section <b>Import errors</b>.
+</div>
+
+<ol start="4">
+	<li>Once the import process is complete, you can click View Import Details to access the import report.</li>
+</ol>
+
+![Importação em massa - EN](//images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/255b9bf809653b7f66bdeff7e22c0c49/Bulk_import_vers_o_original-gif-EN.gif)
+
+# Import errors
+
+During the import process, the system will check the file for errors. If errors are detected, you will be notified by email and receive a notification on your screen.
+
+To get a detailed overview of the detected problems, follow the steps below:
+
+1. Click View Import Details to access the corresponding error report.
+2. Download the spreadsheet by clicking **Download Reviewed XLSX**. This spreadsheet shows the error details.
+3. After fixing the errors, you can restart the import process by uploading the corrected file again.
+
+<div class = "alert alert-info">
+Make sure you only upload the file with corrections to the previously detected errors to ensure a successful import.
+</div>
+
+![Bulk import - EN](//images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/f15af7d4180b8949ef33c25c761122a8/Bulk_import_vers_o_error-gif-EN.gif)
+
+# Bulk Import via API
+
+You can also import information using the [Bulk Import API](https://developers.vtex.com/docs/api-reference/buyer-organizations?endpoint=overview), which allows you to validate and import files, as well as monitor the import progress and result.
+
diff --git a/docs/tutorials/en/configuring-cargo-splitting.md b/docs/tutorials/en/configuring-cargo-splitting.md
index c8e96cd04..79c81c6ce 100644
--- a/docs/tutorials/en/configuring-cargo-splitting.md
+++ b/docs/tutorials/en/configuring-cargo-splitting.md
@@ -3,8 +3,8 @@ title: 'Configuring Cargo Splitting'
 id: tutorials_109
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:24.631Z
-updatedAt: 2023-03-28T14:07:28.837Z
-publishedAt: 2023-03-28T14:07:28.837Z
+updatedAt: 2024-04-30T14:30:11.052Z
+publishedAt: 2024-04-30T14:30:11.052Z
 firstPublishedAt: 2017-04-27T23:00:42.951Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,16 +15,15 @@ legacySlug: configuring-cargo-splitting
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
+Cargo splitting is the configuration that allows a purchase to be divided into multiple deliveries, when the calculation of total weight exceeds the limit defined in the shipping policy.
 
-Cargo splitting is the configuration that allows a purchase to be divided into multiple deliveries, when the calculation of total weight exceeds the carrier limit.
+This configuration is very important because, if cargo splitting is not allowed, the closing of a purchase may preclude. So, use it if the total weight of all products in the shopping cart is bigger than the maximum weight registered in shipping policies.
 
-This configuration is very important because, if cargo splitting is not allowed, the closing of a purchase may preclude. So, use it if the sum of the weight of all products in the cart is bigger than the maximum weight registered for carriers.
-
-![divisao-carga-desenho en](https://images.ctfassets.net/alneenqid6w5/6wSYatCGzeEq2o68IIMIkc/1b86e66b1882c4f41815f642b152446b/divisao-carga_en.png)
+![divisao-carga-desenho en](//images.ctfassets.net/alneenqid6w5/6wSYatCGzeEq2o68IIMIkc/1b86e66b1882c4f41815f642b152446b/divisao-carga_en.png)
 
 ### How to configure
 
 1. In the VTEX Admin, go to **Store settings > Shipping > Settings**, or type *Shipping* in the search bar at the top of the page and select *Store settings / Shipping*.  
-2. On the **Load sharing when carrier limit is reached** area, select the option *Allow the order and split deliveries.*.   
+2. On the **Load sharing when carrier limit is reached** area, select the option *Allow the order and split deliveries*.   
 3. Click on **Save**.  
 
diff --git a/docs/tutorials/en/configuring-cielo-acquirer.md b/docs/tutorials/en/configuring-cielo-acquirer.md
index a2d661bf2..acda49c53 100644
--- a/docs/tutorials/en/configuring-cielo-acquirer.md
+++ b/docs/tutorials/en/configuring-cielo-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring Cielo acquirer'
 id: 3avjZ7q65WcM02K8K0eeWu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-05-02T19:02:05.427Z
-updatedAt: 2023-03-21T18:55:28.551Z
-publishedAt: 2023-03-21T18:55:28.551Z
+updatedAt: 2023-09-19T14:27:20.410Z
+publishedAt: 
 firstPublishedAt: 2018-05-02T19:49:35.201Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
index 16e5c6773..9c91f6dfd 100644
--- a/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
@@ -79,7 +79,7 @@ To configure ClearSale Global, you will need to:
 <br>  
   <ui>11. In the top right corner, click on <b>Publish</b>.</ui>
 
-![Fingerprint ClearSalve_Screen](https://images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/030e58c5ff8495926031bead9fd13b0e/Fingerprint_ClearSalve_Screen.png)
+![Fingerprint ClearSalve_Screen](//images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/030e58c5ff8495926031bead9fd13b0e/Fingerprint_ClearSalve_Screen.png)
 
 For more details about the code entered in Google Tag Manager, we recommend reading [this documentation](https://api.clearsale.com.br/docs/behavior-analytics) from ClearSale.
 
diff --git a/docs/tutorials/en/configuring-clearsale-v3-antifraud.md b/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
index 8dbeb28bd..b860ff26f 100644
--- a/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring ClearSale v3 antifraud'
 id: 2pPORygesIqQOa6cIG6agg
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-10-30T14:10:20.822Z
-updatedAt: 2021-12-15T21:23:21.984Z
-publishedAt: 2021-12-15T21:23:21.984Z
+updatedAt: 2024-04-24T18:52:20.944Z
+publishedAt: 2024-04-24T18:49:44.223Z
 firstPublishedAt: 2017-10-30T14:26:53.089Z
 contentType: tutorial
 productTeam: Financial
@@ -15,22 +15,33 @@ legacySlug: configuring-clearsale-v3-antifraud
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-To enable ClearSale v3 anti-fraud solution, you must [add the gateway affiliation](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444) in the Payments section by choosing the **ClearSaleV3** option. The ClearSale v3 affiliation configuration contains the following fields:
+At VTEX, it is possible to integrate with ClearSaleV3 [anti-fraud](https://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud--tutorials_446). Through this system, it is possible to increase the level of security in payment transactions carried out in your store using risk analyzes that identify possible fraud.
+Para configurar o ClearSaleV3, siga os passos abaixo:
+
+To configure ClearSaleV3, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __ClearSaleV3__ in the search bar and click on the name of the provider.
+4. If you wish to modify the identification name to be displayed for the PagoEfectivoV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+5. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+6. Fill in the information below according to your ClearSale settings:
+<br>
+<ul>
+<br>
+  <li><b>Login</b>: Login.</li>
+  <li><b>Password</b>: Password.</li>
+  <li><b>Custom SLA in minutes (optional)</b>: Period in which ClearSale will have to process the fraud analysis.</li>
+  <li><b>Product (optional)</b>: Numeric value. Corresponds to the product ID contracted on ClearSale.</li>
+  <li><b>Transaction currency</b>: Currency in which the transaction is carried out.</li>
+  <li><b>Observation (optional)</b>: Text that will be sent to ClearSale as a remark.</li>
+  <li><b>Send authenticated transactions?</b>: Indicates whether payment transactions must be authenticated with a password in the 3DSecure program.</li>
+</ul>
+7. Click `Save`.
 
-- **Login**: Login.
-- **Password**: Password.
-- **Custom SLA in minutes (optional):** The time ClearSale will have to process the fraud analysis.
-- **Product (optional):** Numeric value corresponding to the ID of the product purchased from ClearSale.
-- **Transaction currency:** The currency used in the transaction.
-- **Observation (optional):** Text that will be sent to ClearSale as a remark.
-- **Send authenticated transactions?** Has the options **Yes** and **No**. Authenticated transactions are those where all payments have been password authenticated in the 3DSecure program.
-
-<div class = "alert alert-info">
-The ClearSale documentation on <a href="https://api.clearsale.com.br/docs/finger-print" target="_blank">FingerPrint</a> explains the script below in greater detail.
-</div>
-
-<div class="alert alert-warning">
-If you want to set up the <strong>ClearSale T</strong> anti-fraud, just follow <a href="http://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud">these instructions</a>.
+<div class="alert alert-info">
+<p>If you have a mobile application that uses VTEX APIs at checkout, it is necessary to implement fingerprint data collection to be sent to Clearsale, according to the platform used by the application. Find out more at <a href="https://api.clearsale.com.br/docs/behavior-analytics" target="_blank">Clearsale Behavior Analytics</a>.</p>
+  <p>With the SDK implementation, it is necessary to collect the <span class="bg-muted-4">sessionId</span> value and send it in the <span class="bg-muted-4">deviceFingerprint</span> via <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">API when creating the payment</a>.</p>
 </div>
 
 ## Creating a Google Tag Manager tag
diff --git a/docs/tutorials/en/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md b/docs/tutorials/en/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
index 3eb4803b2..7d3f1800d 100644
--- a/docs/tutorials/en/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
+++ b/docs/tutorials/en/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
@@ -3,8 +3,8 @@ title: 'Configuring discounts for orders prepaid in full on Google Shopping'
 id: 40K3R5d4NogMvCzIWdWt3e
 status: PUBLISHED
 createdAt: 2020-12-18T19:17:16.033Z
-updatedAt: 2023-03-30T16:56:23.457Z
-publishedAt: 2023-03-30T16:56:23.457Z
+updatedAt: 2024-01-19T16:37:47.493Z
+publishedAt: 2024-01-19T16:37:47.493Z
 firstPublishedAt: 2021-05-04T20:06:46.945Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,7 +25,12 @@ To set up the discount for orders prepaid in full on Google Shopping, you must a
 4. Select the template of your product page.
 5. In the `richSnippets` component, add the `paymentSystemId` parameter with the value of the desired payment method.
 
-![Screenshot 2020-12-18 Criar preço à vista para Google Shopping](https://images.ctfassets.net/alneenqid6w5/3cZKIpG2uAhDmFTJDslHZk/1bd7628049b5c5b7326df8044ac673f2/Screenshot_2020-12-18_Criar_pre__o____vista_para_Google_Shopping.png)
+```
+<body id="product-page">
+    <!--  Component: richSnippets -->
+    <vtex.cmc:productRichSnippets showGoogle="1" paymentSystemId="6"/>
+    <!-- /Component: richSnippets -->
+```
 
 6. Click on __Save Template__ in the upper right corner.
 
diff --git a/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md b/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md
index be623f357..5782a4a78 100644
--- a/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md
+++ b/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md
@@ -35,7 +35,7 @@ _classe.atributo_ are obtained using the JSON Data field. E.g.:
 **Template HTML**
 `<strong>{{_accountInfo.HostName}}</strong> => lojavirtual`
 
-![exemplohtml](https://images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
+![exemplohtml](//images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
 
 The above example can have different values when comparing Sellers and Marketplaces.
 
diff --git a/docs/tutorials/en/configuring-kushki-gateway.md b/docs/tutorials/en/configuring-kushki-gateway.md
index 542f153bf..8c6db8b6e 100644
--- a/docs/tutorials/en/configuring-kushki-gateway.md
+++ b/docs/tutorials/en/configuring-kushki-gateway.md
@@ -3,8 +3,8 @@ title: 'Configuring Kushki gateway'
 id: 69VC8nQMkEE0yu8oIyG2wG
 status: PUBLISHED
 createdAt: 2018-04-24T15:50:00.468Z
-updatedAt: 2023-03-29T00:41:16.269Z
-publishedAt: 2023-03-29T00:41:16.269Z
+updatedAt: 2024-01-23T17:48:58.465Z
+publishedAt: 2024-01-23T17:48:58.465Z
 firstPublishedAt: 2018-04-24T19:47:19.057Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,20 @@ legacySlug: setting-up-kushki-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Kushki is a [gateway](/en/tutorial/what-is-a-payment-gateway) with [PCI certification](/en/faq/what-is-the-pci-ssc) focused on Latin America.
+Kushki is a [gateway](https://help.vtex.com/en/tutorial/what-is-a-payment-gateway--2KH9Wdi7F6swOU4amECSOk) with [PCI certification](https://help.vtex.com/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E) focused on Latin America.
 
 To set up Kushki, follow the steps below:
 
-## Configuring Kushki gateway affiliation
-1.	In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2.	In the __Gateway Affiliations__ tab, click on the __"+"__ button.
-3.	Click on the __Kushkiv2__ connector.
-4.	Fill in the fields with the __data__ provided by Kushki. 
-5.	The __Application Key__ field must be filled with Kushki’s Private Key. 
-6.	The __Application Token__ field must be filled with Kushki’s Public Key. 
-7.	Click on __Save__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Kushkiv2__ in the search bar and click on the name of the provider.
+4.	In the __App key__ and __App token__ fields, enter the information provided by Kushki.
+5.	If you wish to modify the identification name to be displayed for the iugu provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__. 
+6.	In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7.	Click `Save`.
 
-After completing these steps, you must generate VTEX's Credentials to configure the Kushki affiliation in your store. Follow the instructions provided in the [Authentication section](https://developers.vtex.com/docs/getting-started-authentication "Authentication section") of our Developer Portal.
+To configure the payment methods to be processed by Kushki, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-## Configuring payment condition
-After following the steps indicated above, Kushki will be configured in your store. Thus, when entering a payment condition, it will be available in the __Process with affiliation__ field (as long as the payment method is compatible with Kushki). To learn how to set up payment conditions, read [this article](/en/tutorial/how-to-configure-payment-conditions).
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Kushki connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/configuring-login-with-facebook-and-google.md b/docs/tutorials/en/configuring-login-with-facebook-and-google.md
index 4805d3e84..57d4f018a 100644
--- a/docs/tutorials/en/configuring-login-with-facebook-and-google.md
+++ b/docs/tutorials/en/configuring-login-with-facebook-and-google.md
@@ -3,8 +3,8 @@ title: 'Configuring login with Facebook and Google'
 id: tutorials_513
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:01.743Z
-updatedAt: 2023-02-08T14:32:57.255Z
-publishedAt: 2023-02-08T14:32:57.255Z
+updatedAt: 2023-10-20T19:35:59.221Z
+publishedAt: 2023-10-20T19:35:59.221Z
 firstPublishedAt: 2017-04-27T23:03:27.844Z
 contentType: tutorial
 productTeam: Identity
@@ -15,29 +15,37 @@ legacySlug: configuring-user-id-with-facebook-and-google
 subcategory: 14V5ezEX0cewOMg0o0cYM6
 ---
 
-On VTEX, it is not necessary to create an account or log in to make a purchase. However, if customers wish to make changes to the information provided on their first purchase, they have to confirm that they own the email account in question.
+On VTEX, it is not necessary to create an account or log in to make a purchase. However, if customers want to change the information provided during their first purchase, they must validate their email address.
 
-The VTEX platform natively offers login options with Email & Password and with an Access Code that is sent to the customer's email. We also offer optional native integrations with Google and Facebook, which need to be configured.
+1. [Obtain credentials from providers](#obtaining-credentials-from-providers)
+2. [Configure login with providers](#configuring-login-with-providers)
+3. [Validate the configuration](#validating-the-configuration)
 
-## Obtain OAuth 2.0 credentials
+## Obtaining credentials from providers
 
-Before configuring our login integration with Google and Facebook, you need to create OAuth 2.0 (protocol used for integration) credentials on these services. To do this, follow the instructions provided in the articles below:
+Before setting up our Google and Facebook login integrations, you need to create OAuth 2.0 credentials (the protocol used for integration) in these services. To do this, follow the instructions in the articles below:
 
-- [Facebook](https://help.vtex.com/en/tutorial/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook).
-- [Google](https://help.vtex.com/en/tutorial/registering-a-client-id-and-a-client-secret-for-login-with-google).
+- [Facebook](https://help.vtex.com/en/tutorial/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook)
+- [Google](https://help.vtex.com/en/tutorial/registering-a-client-id-and-a-client-secret-for-login-with-google)
 
-## Configure these login options in your store
+## Configuring login with providers
 
-Once you have completed the previous step on Facebook and/or Google, you must configure the login options for these two providers in your store. In both cases, you will need to have in hands your `Client ID` and `Client Secret`.
+After completing the configuration on Facebook and/or Google, you must configure the login option for the desired provider in the VTEX Admin.  In both cases, you will need the `Client ID` and `Client Secret` from your providers.
 
-1. Access the VTEX ID module from the store administration dashboard in the Account Settings > Authentication menu;
-  ![List Authentication](https://images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/7c232ba07cbf687813319f27328468f7/autenticacao_EN.png)
-2. Select the provider and click on **EDIT**;
-3. Fill out the form with the `Client ID` and the `Client Secret`;
-  ![Facebook OAuth EN](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/06b29f9c839316df31c736a315ba1786/facebook_EN.png)
-4. Activate providers using theirs toggle switches.
-  ![List Authentication Switch On Highlight](https://images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/02ec0a744eb98636917b144e09cc9b3c/switch_On_highlight_EN.png)
+1. In the top bar of the VTEX Admin, click your **profile avatar**, indicated by the initial letter of your email address.
+2. Click **Account settings > Authentication**.
 
-## Validate the configuration
+  You will be redirected to the **Webstore** tab of the **Authentication** page, which lists the login methods available in your store.
 
-Once everything has been set up, you can test this configuration. We recommend that you do this through the final URL that your users will use to access your store. When trying to log in, the options regarding the active providers should be available, and the process should be completed without any problems.
+  ![List Authentication](//images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/fdb1252e98fd1284278e4c83100ec111/autenticacao-en.png)
+3. In the row of the desired login provider, click `Configure`.
+4. Complete the form with the `Client ID` and `Client Secret` from the [previous step](#obtaining-credentials-from-providers) and click `Save`.
+
+  ![Facebook OAuth EN](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/7daac156505a588b95fc0e90fbc08e2d/1-login-fb-en.PNG)
+6. On the **Authentication** page, enable the provider by clicking the toggle switch.
+
+  ![List Authentication Switch On Highlight](//images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/02ec0a744eb98636917b144e09cc9b3c/switch_On_highlight_EN.png)
+
+## Validating the configuration
+
+After the configuration in the VTEX Admin, we recommend testing the login with the chosen provider through the end URL your users will access to visit your store. When trying to log in, the options for active providers will be displayed.
diff --git a/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
index 1700c1c1a..e9374f296 100644
--- a/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -59,7 +59,7 @@ To configure the automatic settlement feature, follow the step-by-step instructi
 8. In the __Payment with anticipated capture authorization__ field, select one of the available time options.
 9. Fill in the __Change maximum time for automatic payment capture__ field with the period agreed with the acquirer. __If you leave this field blank, the default time of 4 days will be considered. __
 
-![captura_automatica_EN](https://images.ctfassets.net/alneenqid6w5/4OXaQvc9dAoPs1lsPXmigk/3351cf6cd959943406edcf967ad4492c/image.png)
+![captura_automatica_EN](//images.ctfassets.net/alneenqid6w5/4OXaQvc9dAoPs1lsPXmigk/3351cf6cd959943406edcf967ad4492c/image.png)
 10. Click on __Save__ 
 
 The new payment settlement feature will then be implemented in your store.
diff --git a/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
index 8811a448b..369910507 100644
--- a/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
@@ -63,13 +63,13 @@ To ensure the Device Fingerprint feature is operating properly, you must analyze
 4. Click on __+ Information__.
 5. Search for the __deviceFingerprint__ field and check if the code starts with the word armor, as illustrated below.
 
-![Device Fingerprint Armor](https://images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/e4183659ac15c29fec5611d96b0b1b52/DEVICEFINGERPRINTARMOR.png)
+![Device Fingerprint Armor](//images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/e4183659ac15c29fec5611d96b0b1b52/DEVICEFINGERPRINTARMOR.png)
 
 <ui>
 6. Then, send the transaction ID to the Mercado Pago support team. You can find this ID in the <b>authorizationConnectorResponse</b> field.
   </ui>
 
-![Authorization](https://images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/1d84e9df5bb987aa4b3acf9a0f1904e1/AUTHORIZATION.png)
+![Authorization](//images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/1d84e9df5bb987aa4b3acf9a0f1904e1/AUTHORIZATION.png)
 
 <ui>
 7. Copy the ID and <a href=https://www.mercadopago.com.br/developers/en/support>send an email</a> with this information to Mercado Pago requesting them to validate the transaction. 
diff --git a/docs/tutorials/en/configuring-my-account-conversational-commerce.md b/docs/tutorials/en/configuring-my-account-conversational-commerce.md
index a711cc563..78af32f90 100644
--- a/docs/tutorials/en/configuring-my-account-conversational-commerce.md
+++ b/docs/tutorials/en/configuring-my-account-conversational-commerce.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring My Account (Conversational Commerce)'
 id: 42bnIdyC2c5dwz9KKT0UKc
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-07T19:10:12.107Z
-updatedAt: 2023-03-07T20:00:20.806Z
-publishedAt: 2023-03-07T20:00:20.806Z
+updatedAt: 2024-01-05T16:28:41.167Z
+publishedAt: 
 firstPublishedAt: 2023-03-07T19:58:45.529Z
 contentType: tutorial
 productTeam: Shopping
@@ -24,7 +24,7 @@ subcategory: 5bBAgUbHdh6ovdZ4kGsN7O
 
 ## Conversational Settings Fields
 
-![my account - conversational commerce - EN](https://images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/2329e5c54977ddb95a7fd6fd4ad01b47/image.png)
+![my account - conversational commerce - EN](//images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/2329e5c54977ddb95a7fd6fd4ad01b47/image.png)
 
 * **Language:** The default language for bot messages to customers in VTEX Conversational Commerce. Required field.
 * **Welcome message:** The first message that VTEX Conversational Commerce will send in its initial interaction with the customer. This message is followed by explanatory messages about the purchase process and human support from your customer service team. Required field. Our default suggestion is: 
diff --git a/docs/tutorials/en/configuring-openpay-payment-gateway.md b/docs/tutorials/en/configuring-openpay-payment-gateway.md
index 65796c802..f5f6a3900 100644
--- a/docs/tutorials/en/configuring-openpay-payment-gateway.md
+++ b/docs/tutorials/en/configuring-openpay-payment-gateway.md
@@ -3,8 +3,8 @@ title: 'Configuring Openpay payment gateway'
 id: 5vGj3UIFCU4GFFqVBlYKW2
 status: PUBLISHED
 createdAt: 2021-07-06T17:31:51.598Z
-updatedAt: 2021-07-06T18:01:16.234Z
-publishedAt: 2021-07-06T18:01:16.234Z
+updatedAt: 2024-01-25T18:44:58.747Z
+publishedAt: 2024-01-25T18:44:58.747Z
 firstPublishedAt: 2021-07-06T17:54:12.638Z
 contentType: tutorial
 productTeam: Financial
@@ -21,11 +21,11 @@ subcategory:
   To configure it in your store, you need to have a verified Openpay account. If you do not have it yet, <a href="https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false">click here</a> to create your account.
   </div>
 
-To configure Openpay gateway in your VTEX environment, you will need to:
+To configure Openpay in your VTEX environment, you will need to:
 
 1. [Configure Google Tag Manager](#configuring-google-tag-manager)
 2. [Configure Openpay gateway](#configuring-openpay-gateway)
-3. [Associate Openpay’s solution with a payment condition](#associating-openpays-solution-with-a-payment-condition)
+3. [Configuring payment conditions](#configuring-payment-conditions)
 
 ## Configuring Google Tag Manager
 
@@ -33,21 +33,22 @@ To configure Google Tag Manager, follow the instructions in __step two__ of this
 
 Once you have finished it, proceed to the next step of this article.
 
-## Configuring Openpay gateway
+## Configuring Openpay
 
-Now you just have to install the Openpay connector in your store. Follow the steps below:
+Now you just have to install the Openpay provider in your store. Follow the steps below:
 
-1. Go to the VTEX __Admin__.
-2. In the __Payments__ module, click on __Settings__.
-3. In __Gateway Affiliations__, click on the green “__+__” button.
-4. Search for __Open Pay__ and select its card.
-5. In __Affiliation name__, enter __Open Pay__.
-6. Fill in the __Application Key__ and __Application Token__ fields. [Click here](https://www.openpay.mx/en/docs/vtex.html) to access Openpay documentation and see the instructions on how to obtain this information.
-7. Click on __Save__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Openpay__ in the search bar and click on the name of the provider.
+4. In __Affiliation name__, enter __Openpay__.
+5. Fill in the __Application Key__ and __Application Token__ fields. [Click here](https://www.openpay.mx/en/docs/vtex.html) to access Openpay documentation and see the instructions on how to obtain this information.
+6. Click `Save`.
 
-## Associating Openpay’s solution with a payment condition
+## Configuring payment conditions
 
-Once you have completed the steps above, Openpay will be ready to be used in your store.
+To configure the payment methods to be processed by Openpay, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-If you want to associate it with a compatible payment condition, check out our article [Configuring payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Openpay may take up to 10 minutes to appear at your store's checkout as a payment option.
 
diff --git a/docs/tutorials/en/configuring-payment-conditions-for-b2b.md b/docs/tutorials/en/configuring-payment-conditions-for-b2b.md
new file mode 100644
index 000000000..5cdacf407
--- /dev/null
+++ b/docs/tutorials/en/configuring-payment-conditions-for-b2b.md
@@ -0,0 +1,43 @@
+---
+title: 'Configuring payment conditions for B2B'
+id: 6NMeukzx5H7n1YaePPS7pr
+status: PUBLISHED
+createdAt: 2024-07-25T16:31:16.186Z
+updatedAt: 2024-07-25T17:07:27.442Z
+publishedAt: 2024-07-25T17:07:27.442Z
+firstPublishedAt: 2024-07-25T17:07:27.442Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configuring-payment-conditions-for-b2b
+locale: en
+legacySlug: configuring-payment-conditions-for-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+In a B2B operation, [payment conditions](https://help.vtex.com/es/tutorial/how-to-configure-payment-conditions--tutorials_455?&utm_source=autocomplete) are assigned to the buying organization. You determine the payment options that the organization users see at checkout.
+
+An organization administrator user can customize the available payment options by cost center.
+
+<div class = "alert alert-info">
+When you configure a payment condition in the Payments module, it will display as a payment method in the <b>Available</b> list in the <b>Payment Conditions</b> tab. To view the list, click the name of the organization. The payment methods listed are the ones that are already assigned to the organization.
+</div>
+
+## Linking payment conditions to the organization
+To link a payment condition to a buyer organization, follow the instructions below:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations & Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access the details page.
+3. On the organization details page, click the **Payment Conditions** tab.
+4. Select the desired payment options from the **Available** list and click `Add to Org`.
+5. Click `Save` at the top right of the page.
+
+## Removing a linked payment condition
+To unlink payment conditions from a buyer organization, follow the instructions below:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations & Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access the details page.
+3. On the organization details page, click the **Payment Conditions** tab.
+4. Select the desired options from the **Assigned to organization** list and click `Remove From Org`.
+5. Click `Save` at the top right of the page.
+
diff --git a/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index fca6db8d1..8a025d1e8 100644
--- a/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Configuring payment with AdyenV3 in VTEX Sales App'
 id: 24yO6KloBn6DN6CbprHtgt
 status: PUBLISHED
 createdAt: 2023-05-09T14:12:03.567Z
-updatedAt: 2023-06-01T11:38:18.504Z
-publishedAt: 2023-06-01T11:38:18.504Z
+updatedAt: 2024-07-26T16:55:23.474Z
+publishedAt: 2024-07-26T16:55:23.474Z
 firstPublishedAt: 2023-05-11T20:30:50.460Z
 contentType: tutorial
 productTeam: Financial
@@ -51,12 +51,16 @@ To enable VTEX access to the Adyen environment, follow the instructions below:
 2. In the left sidebar, copy and save the information shown above **Company**. This is your Company account.
 3. In the list below Company, search for the Merchant Account that will be used (highlighted in white). Copy and save this information.
 
-![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Getting the POS Live URL
 
+This information is related to the endpoints used by Adyen's endpoint APIs in a production environment. For more information, visit the [Adyen docs](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api#cloud).
+
+### Getting the Live URL prefix
+
 1. In the sidebar, go to **Developers > API URLs**.
-2. Click `Copy` in the **Point of Sale** field, and store the information in a safe place.
+2. Click `Copy` in the **Prefix** field, and store the information in a safe place. This prefix controls your endpoint on the Adyen platform.
 
 ### Getting the API Key
 
@@ -66,7 +70,7 @@ The steps below assume that the API Key has been previously generated in the Ady
 2. Select your API credential.
 3. In **Server Settings > Authentication**, select **API key**. 
 
-![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Click <b>Generate key</b> and store the generated key in a safe location.</ui>
 
@@ -82,7 +86,7 @@ Follow the steps below to configure a webhook:
 4. In **General > Description**, add a description for the new webhook. Example: "Webhook Adyen Connector Provider v3".
 5. In **General > Server configuration > URL**, enter the URL of your VTEX account. Example: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Click <b>Apply</b>.</ui>
 
@@ -90,11 +94,11 @@ Follow the steps below to configure a webhook:
 
 <blockquote><ui>8. Click <b>Save changes</b>.</ui>
 
-![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 If you have several stores, you need to configure a webhook for each of them.
@@ -102,22 +106,19 @@ If you have several stores, you need to configure a webhook for each of them.
 
 ## Configuring AdyenV3 Connector (VTEX Sales App) on VTEX
 
-1. In the VTEX Admin, go to **Store Settings > Payments > Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the **Afiliações de Gateways** tab, click the `+` button.
-3. Select the **AdyenV3** connector.
-4. Complete the following fields with the information provided by Adyen:
-    - **Application Key**: name of your Merchant account (step 3 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
-    - **Application Token**: API Key (step 4 in the [Getting the API Key](#getting-the-api-key) section).
-    - **Live URL prefix**: it is not necessary to fill in this field (only applicable to other online sales channels).
-    - **Company account**: the name of your Company account (step 2 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
-    - **Live POS URL**: URL prefix (step 2 in the [Getting the POS Live URL](#getting-the-pos-live-url) section). 
-    - **Client key**: it is not necessary to fill in this field (only applicable to other online sales channels).
-
-<blockquote><ui>  5. If a warning message is displayed indicating that the app needs to be installed, click the <b>Install app</b> button and follow the installation instructions.</ui>
-
-<blockquote><ui>  6. Click <b>Save</b>.</ui>
-
-![Adyenv3_9](https://images.ctfassets.net/alneenqid6w5/SCflCIOFcwFro09YTxEZy/27b941b772a6afb021d0fa2fe25c9fa9/Adyenv3_9.PNG)
+1. In the VTEX Admin, go to __Store Settings > Payments > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __AdyenV3__ in the search bar and click on the name of the provider.
+4. In __Application Key__, fill in the name of your Merchant account (step 3 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
+5. In __Application Token__, fill in the API Key (step 4 in the [Getting the API Key](#getting-the-api-key) section).
+6. If you wish to modify the identification name to be displayed for the AdyenV3 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+7. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+8. In __Live URL prefix__, fill in the prefix available in Adyen customer area (step 2 in the [Getting the Live URL prefix](#getting-the-live-url-prefix) section).
+9. In __Company account__, enter the name of your Company account (step 2 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
+10. In __Live POS URL__, fill in endpoints used to access Adyen terminal APIs. Learn more at [Adyen documentation](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api#cloud).
+11. The __Client Key__ field is not necessary to fill in, as it is only applicable to other types of online sales channels.
+12. In __Auto Capture Settings__, select when you want to capture the payment.
+13. Click `Save`.  
 
 ## Configuring payment condition
 
diff --git a/docs/tutorials/en/configuring-payment-with-adyenv3.md b/docs/tutorials/en/configuring-payment-with-adyenv3.md
index 8924a3b63..3d5a4107d 100644
--- a/docs/tutorials/en/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/en/configuring-payment-with-adyenv3.md
@@ -3,8 +3,8 @@ title: 'Configuring payment with AdyenV3'
 id: 7xAz67E2Eg63LWCQNjVdwv
 status: PUBLISHED
 createdAt: 2023-05-08T20:00:38.610Z
-updatedAt: 2023-05-31T19:42:52.614Z
-publishedAt: 2023-05-31T19:42:52.614Z
+updatedAt: 2024-06-25T21:10:30.984Z
+publishedAt: 2024-06-25T21:10:30.984Z
 firstPublishedAt: 2023-05-11T20:32:21.638Z
 contentType: tutorial
 productTeam: Financial
@@ -39,15 +39,15 @@ To enable VTEX access to the Adyen environment, follow the instructions below:
 ### Getting the Company and Merchant account credentials 
 
 1. Log in to your [Customer Area](https://ca-test.adyen.com/) on Adyen.
-2. In the left sidebar, copy and save the information shown above **Company**. This is your Company account.
+2. In the left sidebar, copy and save the information shown above __Company__. This is your Company account.
 3. In the list below Company, search for the Merchant Account that will be used (highlighted in white). Copy and save this information.
 
-![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Getting the Live URL
 
-1. In the sidebar, go to **Developers > API URLs**.
-2. Click Copy in the **Prefix** field, and store the information in a safe place.
+1. In the sidebar, go to __Developers > API URLs__.
+2. Click Copy in the __Prefix__ field, and store the information in a safe place.
 
 ### Getting the API Key and Client Key
 
@@ -55,11 +55,11 @@ To enable VTEX access to the Adyen environment, follow the instructions below:
 The steps below assume that the API Key and Client Key have been previously generated in the Adyen environment. If you need to create them, see the <a href="https://docs.adyen.com/">Adyen</a> documentation.
 </div>
 
-1. In the sidebar, click **Developers** and, then, click **API credentials**.
+1. In the sidebar, click __Developers__ and, then, click __API credentials__.
 2. Select your API credential.
-3. In **Server Settings > Authentication**, select **API key**. 
+3. In __Server Settings > Authentication__, select __API key__. 
 
-![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Click <b>Generate Key</b> and store the created key in a safe location.</ui>
 
@@ -67,7 +67,7 @@ The steps below assume that the API Key and Client Key have been previously gene
 
 <blockquote><ui>6. Click <b>Generate Client Key</b> and store the generated key in a safe location.
 
-![Adyenv3_3](https://images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
+![Adyenv3_3](//images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
 
 ### Configuring a webhook
 
@@ -81,7 +81,7 @@ Follow the steps below to configure a webhook:
 4. In **General > Description**, add a description for the new webhook. Example "Webhook Adyen Connector Provider v3".
 5. Em **General > Server configuration > URL**, enter the URL of your VTEX account. Example: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Click <b>Apply</b>.</ui>
 
@@ -89,11 +89,11 @@ Follow the steps below to configure a webhook:
 
 <blockquote><ui>8. Click <b>Save changes</b>.</ui>
 
-![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 If you have several stores, you need to configure a webhook for each of them.
@@ -101,25 +101,35 @@ If you have several stores, you need to configure a webhook for each of them.
 
 ## Configuring the AdyenV3 connector on VTEX
 
-1. In the VTEX Admin, go to **Store Settings > Payments > Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the **Gateways Affiliations** tab, click the `+` button.
-3. Select the **AdyenV3** connector.
-4. Complete the following fields with the information provided by Adyen:
-    - **Application Key**: name of your Merchant account (step 3 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
-    - **Application Token**: API Key (step 4 in the [Getting the API Key and Client Key](#getting-the-api-key-and-client-key) section).
-    - **Live URL prefix**: URL prefix (step 2 in the [Getting the Live URL](#getting-the-live-url) section).
-    - **Company account**: the name of your Company account (step 2 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
-    - **Live POS URL**: you do not need to complete this field (it only applies to Sales App). 
-    - **Client key**: Client key (step 6 in the [Getting the API Key and Client Key](#getting-the-api-key-and-client-key) section).
+1. In the VTEX Admin, go to __Store Settings > Payments > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __AdyenV3__ in the search bar and click on the name of the provider.
+4. In __App key__, fill in the name of your Merchant account (step 3 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
+5. In __App token__, fill in the API Key (step 4 in the [Getting the API Key and Client Key](#getting-the-api-key-and-client-key) section).
+6. If you wish to modify the identification name to be displayed for the AdyenV3 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+7. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+8. In __Live URL prefix__, fill in the URL prefix (step 2 in the [Getting the Live URL](#getting-the-live-url) section).
+9. In __Company account__, enter the name of you Company account (step 2 in the [Getting the Company and Merchant account credentials](#getting-the-company-and-merchant-account-credentials) section).
+10. In __Live POS URL__, you do not need to complete this field (it only applies to Sales App).
+11. In __Client key__, fill in the Client key (step 6 in the [Getting the API Key and Client Key](#getting-the-api-key-and-client-key) section).
+12. Click `Save`.
 
-<blockquote><ui>  5. If a warning message is displayed indicating that the app needs to be installed, click the <b>Install app</b> button and follow the installation instructions.</ui>
+To configure the payment methods to be processed by AdyenV3, see [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455). If you want to use the Sales App for completing purchases, see [Configuring payments with AdyenV3 on Sales App](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3-in-instore--24yO6KloBn6DN6CbprHtgt).
 
-<blockquote><ui>  6. Click <b>Save</b>.</ui>
+To define special conditions for payment methods, see [Configuring special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
 
-![Adyenv3_8](https://images.ctfassets.net/alneenqid6w5/6VHaDn8IejGCUoatLIyUtk/bb93a701e80a942064818a54ac401714/Adyenv3_8.PNG)
+## Configuring credit card  
 
-To configure the payment methods to be processed by AdyenV3, see [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455). If you want to use the Sales App for completing purchases, see [Configuring payments with AdyenV3 on Sales App](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3-in-instore--24yO6KloBn6DN6CbprHtgt).
+If you wish to process credit card payments in your store using AdyenV3, in addition to performing the previous configurations described in this article, you must open a ticket at [VTEX support](https://help.vtex.com/en/support), with the following request "Provider review - Add Endpoint SecureProxy - AdyenV3".
 
-To define special conditions for payment methods, see [Configuring special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+In the ticket you must also send the URL that will be authorized by Adyen to carry out the credit card transaction in your store. The URL format must be `https://{live URL prefix}-checkout-live.adyenpayments.com`, where the information "{live URL prefix}" must be the same as that entered by you in the Adyen settings in the VTEX Admin.  
+
+<div class="alert alert-warning">
+The full URL address must be written in lowercase letters only, even if the "Live URL prefix" configured in the VTEX Admin has some capital letters.
+</div>    
+
+## Configure payment with Apple Pay on Adyen (optional) 
+
+To process payments with Apple Pay on Adyen, you must first perform configurations to enable your store in the Apple Pay environment. Learn more at [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/docs/guides/setting-up-merchant-id-in-apple-pay).   
 
 After completing these steps, it can take up to 10 minutes for the AdyenV3 connector to appear as a payment option in your store's checkout.
diff --git a/docs/tutorials/en/configuring-price-divergence-rule.md b/docs/tutorials/en/configuring-price-divergence-rule.md
index 7e2f3fcc6..a5609b196 100644
--- a/docs/tutorials/en/configuring-price-divergence-rule.md
+++ b/docs/tutorials/en/configuring-price-divergence-rule.md
@@ -3,8 +3,8 @@ title: 'Configuring Price Divergence rule'
 id: awAKP0sS5J8jgLs2g7pPe
 status: PUBLISHED
 createdAt: 2021-12-03T01:24:41.194Z
-updatedAt: 2023-03-29T19:19:25.326Z
-publishedAt: 2023-03-29T19:19:25.326Z
+updatedAt: 2024-03-27T21:10:37.241Z
+publishedAt: 2024-03-27T21:10:37.241Z
 firstPublishedAt: 2021-12-03T01:31:08.666Z
 contentType: tutorial
 productTeam: Channels
@@ -17,7 +17,13 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 When the price defined by the seller is different from the price offered by the marketplace, orders may not be processed correctly. On VTEX, the order authorization flow allows you to control and automatically approve these orders by configuring [Price Divergence rule](https://help.vtex.com/en/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW). This article explains how sellers can create and edit Price Divergence rule and manually approve orders.
 
-When no Price Divergence rule is configured, orders with price divergence are automatically approved by default. This applies to VTEX marketplaces, external marketplaces, and [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), but not to [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex). 
+When no Price Divergence rule is created, the VTEX platform will behave differently for each scenario below:
+
+- **Orders created through the Marketplace interface:** Will be automatically denied.
+- **Orders created via API:** Will be automatically denied if the `isCreatedAsync` field is not sent.
+- **Orders with Price Divergence related to manual discounts:** Will be automatically authorized.
+
+To use the Order Authorization flow, in cases of price divergence, you need to send the `isCreatedAsync` field in the [Place Fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders) API, regardless of the type of connector used. This scenario is valid for VTEX marketplaces, external marketplaces, [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro), or [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex).
 
 When a seller is integrated with a native connector, such as Amazon, but has not configured a Price Divergence rule, orders with price difference errors remain pending until the rule is created. You can track them in your VTEX Admin by clicking on **Marketplace > Connections > Orders**.
 
@@ -35,17 +41,17 @@ To create a price divergence rule, follow the steps below:
 
 1. In the VTEX Admin, go to **Store Settings > Orders > Order Authorization**, or type *Order Authorization* in the search bar at the top of the page.
 2. In the _Price Divergence_ section, click `CREATE RULES`.
-3. On the new page, click `CREATE RULES`. 
+3. On the new page, click `CREATE RULES`.
 
 You will see the following screen:
 
-![print_01_EN](https://drive.google.com/uc?export=download&id=1erJY5_lSLftv75zdHWHnM-45SBgHUy6H)
+![print_01_EN](//images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/fa9641527537c42b23341371afd4952c/print_01_EN.png)
 
-The **All** tab displays all configured authorization rules. 
+The **All** tab displays all configured authorization rules.
 
 To create the first authorization rule, click on **CREATE RULES**. A new tab named **1st rule** will be displayed. Clicking on this tab will display the configuration options.
 
-![print_02_EN](https://drive.google.com/uc?export=download&id=171O7kqbffgVhC_2gMPyKAzypkLWsDw9c)
+![print_02_EN](//images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/624e56c9b13d8208d9415b0645b4745a/print_02_EN.png)
 
 To configure the **1st rule**, you can increase or decrease the divergence percentage by dragging the ends of the bar. The > sign determines the start of the range, and the < sign determines its end. The range can be from 0% to 100%.
 
@@ -59,9 +65,9 @@ Once you have defined the authorization rule range, select one of the following
 
 To configure a hierarchy of users responsible for approving orders, you must enter more than one email address and sort the registered users. You can change these users at any time by editing the order authorization rule. Please note that only users with the Super Admin (Owner) or OMS Full [roles](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) can edit the rule.
 
-To create the **2nd rule**, click on the <img class="shadow-4" src="https://https://images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> plus sign. The same applies to creating a third or fourth rule, and so on. Once you click on the icon, the following interface is displayed:
+To create the **2nd rule**, click on the `<img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" />` plus sign. The same applies to creating a third or fourth rule, and so on. Once you click on the icon, the following interface is displayed:
 
-![print_03_EN](https://drive.google.com/uc?export=download&id=1Gjrhs52gbSfoLDPn_eTJSMrznoq98vbn)
+![print_03_EN](//images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/9c85616fd03154cf6130dc5addc22cc4/print_03_EN.png)
 
 Configure the new authorization rule and, once you have configured all the rules you want, click on the **SAVE RULES** button. You will see the following message: _After saving, you can still edit or delete them at any time_. Click **OK** to confirm. Once this is done, the Price Divergence rule will be created.
 
@@ -123,3 +129,4 @@ To approve an order with price divergence via VTEX DO, follow the steps below.
 - [Price Divergence rule](https://help.vtex.com/en/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW)
 - [All Orders](https://help.vtex.com/en/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi)
 - [Marketplace strategies on VTEX](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402)
+
diff --git a/docs/tutorials/en/configuring-product-visited.md b/docs/tutorials/en/configuring-product-visited.md
index cd49c57db..cb84f99bc 100644
--- a/docs/tutorials/en/configuring-product-visited.md
+++ b/docs/tutorials/en/configuring-product-visited.md
@@ -1,10 +1,10 @@
 ---
 title: 'How to configure visited product'
 id: tutorials_3136
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T21:52:11.184Z
-updatedAt: 2023-03-28T23:34:22.351Z
-publishedAt: 2023-03-28T23:34:22.351Z
+updatedAt: 2024-06-18T21:19:01.080Z
+publishedAt: 2024-06-18T21:15:58.589Z
 firstPublishedAt: 2017-04-27T23:03:54.918Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,6 +15,10 @@ legacySlug: configuring-product-visited
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
+<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Tutorial valid only for Legacy CMS Stores.
+</div>
+
 Product visited is a function that sends emails to customers who viewed a product on your site but did not complete a purchase. The purpose of this email is to recover the sale, by sending details of the product abandoned and suggestions for others. You can do all this through your Master Data.
 
 [![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
diff --git a/docs/tutorials/en/configuring-promotions-for-marketplaces.md b/docs/tutorials/en/configuring-promotions-for-marketplaces.md
index a87ecc2bb..86b889f07 100644
--- a/docs/tutorials/en/configuring-promotions-for-marketplaces.md
+++ b/docs/tutorials/en/configuring-promotions-for-marketplaces.md
@@ -3,8 +3,8 @@ title: 'Configuring promotions for marketplaces'
 id: tutorials_406
 status: PUBLISHED
 createdAt: 2017-04-27T22:06:28.854Z
-updatedAt: 2023-01-26T18:41:34.664Z
-publishedAt: 2023-01-26T18:41:34.664Z
+updatedAt: 2024-01-18T17:21:44.418Z
+publishedAt: 2024-01-18T17:21:44.418Z
 firstPublishedAt: 2017-04-27T23:03:23.902Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -24,6 +24,7 @@ Only the following [regular promotions](https://help.vtex.com/en/tracks/promotio
 - Free shipping
 - Percentage shipping
 - Percentage price
+- Price tables
 
 The settings available for VTEX marketplaces are different from the ones of external marketplaces. Therefore, promotions in other marketplace environments are slightly different.
 
@@ -41,7 +42,7 @@ For this type of promotion, it is important to keep the following information in
 
 For this type of promotion, it is important to keep the following information in mind:
 
-- The marketplace does not receive the promotion but rather a notification via API informing that the price has changed. It is up to the marketplace to check the promotional price.
+- Once the seller has created and activated the promotion, it does not send any notifications to the marketplace. It is up to the marketplace to check the promotional price.
 - For the promotion to be applied to the product price, the marketplace must simulate the SKU price using the [Do OrderForm Simulation](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pub/orderForms/simulation) endpoint of the Checkout API.
 - The promotion will not apply to the product price if the marketplace uses the [Get Price](https://developers.vtex.com/docs/api-reference/pricing-api#get-/prices/-itemId-) endpoint of the Pricing API for checking prices. This endpoint shows only the prices listed on VTEX without considering promotions.
 - Sellers determine the discount limits that the marketplace can apply to the total order value. If the discount is greater than the established limit, the order will not be placed. You can change your store’s settings in the [Order authorization](https://help.vtex.com/en/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn#price-divergence) section.
@@ -51,13 +52,13 @@ For this type of promotion, it is important to keep the following information in
 There are differences between the settings available for VTEX marketplaces and external marketplaces. See in the table below the features applicable in each case.
 
 <div class = "alert alert-warning">
-  <p><b>Warning:</b>In the case of external integrations, configurations are unique to each marketplace, and it’s up to them to decide which features they will use.</p>
+  <p>In the case of external integrations, configurations are unique to each marketplace, and it’s up to them to decide which features they will use.</p>
 </div>
 
 | Settings  | Description      | Available for VTEX marketplaces? | Available for external marketplaces? |
 | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | ------------------------------------ |
 | Name| Promotion name | Yes| Yes|
-| Status| Option that defines if the promotion is active or inactive.| Yes| Yes|
+| Status| Option that defines if the promotion is active or inactive.| Yes| Yes| 
 | Description| The internal description of the promotion| Yes| Yes|
 | Allow cumulative promotions   | More than one promotion can be applied simultaneously, regardless of the discount type.| Yes| Yes|
 | Nominal Discount| Discount granted to the total cart price.| Yes| Yes|
@@ -74,7 +75,47 @@ There are differences between the settings available for VTEX marketplaces and e
 | Sales channels| The discount applies to a sales channel list.| Yes| Yes|
 | Item price between| Sets the trade policies applicable to the promotion.| Yes| Yes|
 
-## Determining where promotions will be applied
+## Promotions unavailable for marketplaces
+
+Check the promotions that are not available for marketplaces:
+
+* Nominal discount
+* Maximum price per item
+* Nominal shipping
+* Maximum shipping
+* Gift
+* Nominal reward amount
+* Buy Together - Bundle
+* More for Less
+* Progressive Discount
+* Buy One Get One
+* Campaign Promotion
+
+### Unavailable settings
+
+See below the settings that are not available for marketplaces:
+
+| Name                                                                      | Description                                                                                                                                                                                               |
+| ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Customer cluster                                                          | Discount given if the customer is part of the selected [cluster](https://help.vtex.com/en/tutorial/como-criar-um-cluster-de-clientes--frequentlyAskedQuestions_1724).                                     |
+| Marketing tags                                                            | Used to limit the promotion's activation if the order is placed through [the VTEX Subscriptions module](https://help.vtex.com/en/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453).     |
+| UTMs                                                                      | Discount given depending on the value of a given [UTM parameter](https://help.vtex.com/en/tutorial/o-que-sao-utm-source-utm-campaign-e-utm-medium--2wTz7QJ8KUG6skGAoAQuii).                               |
+| Campaign audience                                                         | Allows you to segment your store's promotions by defining [target audiences](https://help.vtex.com/en/tutorial/audiencias-de-campanhas--3o7lhpNseXY2WmjZO0gQ6m#publico-alvo) that meet specific criteria. |
+| Coupons                                                                   | Code that allows promotions to be applied to the total cart amount.                                                                                                                                       |
+| Cart maximum or minimum total amount                                      | Applied based on the total cart amount, regardless of other promotions or shipping.                                                                                                                       |
+| Number of installments                                                    | Discount given if the number of installments selected by the customer is within the specified range.                                                                                                      |
+| Restriction BIN                                                           | Discount given if the card's BIN is among the specified numbers.                                                                                                                                          |
+| Payment method                                                            | Discount given if the customer selects the same payment method as the one in the promotion.                                                                                                               |
+| First purchase                                                            | Discount given on the customer's first purchase.                                                                                                                                                          |
+| Aggregate purchase value                                                  | Discount given if the customer's total purchase amount reaches the specified amount.                                                                                                                      |
+| Apply with manual prices                                                  | Allows the promotion to be applied to products with prices manually added by telesales.                                                                                                                   |
+| Price "from" and "to" are the same or Price "from" and "to" are different | Refers to the prices saved for that product.                                                                                                                                                              |
+| Seller filter                                                             | Defines which sellers the promotion will be applied to.                                                                                                                                                   |
+| Maximum use of promotion per customer                                     | Limits the number of times each customer can receive the promotion.                                                                                                                                       |
+| Maximum use of promotion per store                                        | Limits the number of times the promotion can be applied.                                                                                                                                                  |
+| Maximum use of coupon per product                                         | Limits the number of times a coupon can be applied to a product.                                                                                                                                          |
+
+## Determining the context in which promotions will be applied
 
 If necessary, you can segment promotions for specific marketplaces. You can obtain these results by using two selectors:
 
@@ -96,5 +137,5 @@ If necessary, you can segment promotions for specific marketplaces. You can obta
 4. Click on `Save`.
 
 <div class = "alert alert-warning">
-  <p> Please remember to <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindex all products included in the promotion</a> after you’ve created it. This will ensure that the prices of your products are up to date.</p>
+  <p> Please remember to <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindex all products included in the promotion</a> after you’ve created it and at the beginning and end of the promotions. This will ensure that the prices of your products are up to date.</p>
 </div>
diff --git a/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md b/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md
index 9d5b5cb68..ecf51b933 100644
--- a/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md
+++ b/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md
@@ -3,8 +3,8 @@ title: 'Configuring promotions with highlights / flags'
 id: tutorials_2295
 status: PUBLISHED
 createdAt: 2017-04-27T21:55:19.949Z
-updatedAt: 2023-03-31T19:22:08.848Z
-publishedAt: 2023-03-31T19:22:08.848Z
+updatedAt: 2024-07-29T18:59:29.549Z
+publishedAt: 2024-07-29T18:59:29.549Z
 firstPublishedAt: 2017-04-27T23:03:51.539Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,6 +15,10 @@ legacySlug: configuring-promotions-with-a-highlightflag
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
+<div class="alert alert-warning" role="alert">
+Tutorial valid only for Legacy CMS Stores.
+</div>
+
 The promotion highlight is a notice that can be placed on shelves and product pages stating that the product is eligible for a promotion. A common example is an image below a product picture indicating free shipping.
 
 ![ExemploPromocaoDestaque2](//images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
@@ -63,7 +67,7 @@ This configuration consists of editing the page template used for the product pa
 9. On the right side of the screen, click on **New Layout**.
 10. In the side menu, click on the layout with a red check mark, and in the __Template__ field check the name of the template used.
 
-![Layout com check - PT](https://images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
+![Layout com check - PT](//images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
 
 ![Template](//images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
 
diff --git a/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md b/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md
new file mode 100644
index 000000000..c4c24f134
--- /dev/null
+++ b/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md
@@ -0,0 +1,73 @@
+---
+title: 'Configuring PWA in your Store Framework store'
+id: 1xWVQTONeROlSOXG8lSyKV
+status: PUBLISHED
+createdAt: 2024-06-18T14:58:53.804Z
+updatedAt: 2024-06-20T12:15:54.742Z
+publishedAt: 2024-06-20T12:15:54.742Z
+firstPublishedAt: 2024-06-18T15:49:26.862Z
+contentType: tutorial
+productTeam: Others
+author: YRJ73j8mt38D5TUleocQB
+slug: configuring-pwa-in-your-store-framework-store
+locale: en
+legacySlug: configuring-pwa-in-your-store-framework-store
+subcategory: 7ogirQ8NClawO2X6xdgCKc
+---
+
+Stores developed with VTEX IO Store Framework natively have a *Progressive Web App* (PWA), a type of web app that offers a user experience similar to a native app but runs directly in a web browser.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+For Legacy Portal CMS stores, see the guide <a href="https://help.vtex.com/en/tutorial/how-to-turn-my-store-website-into-a-pwa--3i8VmYeToAUGKgo2kKK6I2">How to turn my store's website into a PWA</a>.
+</div>
+
+To configure a PWA in your store, go to **Store Settings > Storefront > Store** in the VTEX Admin and follow the steps below:
+
+1. Click the **PWA** tab.
+2. Set the **Theme color**, **Background color** and add the **Android logo icon (512x512, PNG)** and **iOS logo icon (512x512, PNG)**. The colors must be specified in hexadecimal code (e.g., #F71963), and the icons must have a size of 512x512 px and a `.png` extension.
+
+  ![pwa-settings-1-en](//images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/8b7909e47d4ebe3906f12fc997dec948/pwa-settings-1-en.png)
+
+3. Scroll down and go to the **Other PWA settings** field. Click the arrow to show the other settings.
+
+  ![pwa-settings-2-en](//images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/7e6e92b83cdc7af103e35f19d740343d/pwa-settings-2-en.png)
+
+4. In **Other PWA settings**, complete the fields as indicated below:
+
+    - **Start URL**: URL of the PWA homepage.
+    - **Screen orientation**: Format in which the content is displayed in the PWA. One of the following values can be assigned: Any, Natural, Landscape, Landscape (primary), Landscape (secondary), Portrait, Portrait (primary), Portrait (secondary).
+
+    | **Screen Orientation**  | **Description** |
+    |--------------------------|-----------------|
+    | Any                      | The page can be viewed in any orientation, and the content automatically adjusts to fit the device's current orientation. |
+    | Natural                  | Factory default configuration of the device. |
+    | Landscape                | The content is only displayed in landscape orientation. This is useful for apps or games optimized for a wider view. |
+    | Landscape (primary)      | Horizontal orientation with the top of the device aligned to the left. |
+    | Landscape (secondary)    | Horizontal orientation with the top of the device aligned to the right. |
+    | Portrait                 | The content is only displayed in vertical orientation. This is the default setting for most mobile apps. |
+    | Portrait (primary)       | Portrait orientation with the `home` button or the bottom of the device pointing downwards. |
+    | Portrait (secondary)     | Inverted portrait orientation, with the `home` button or the bottom of the device pointing upwards. This is useful when devices are used upside down. |
+
+    - **Display**: PWA content display modes. One of the following values can be assigned: Full screen, Standalone (Add to Home Screen), Minimal-UI (not supported by Chrome), and Browser.
+
+    | **Display**              | **Description** |
+    |--------------------------|-----------------|
+    | Full Screen              | PWA fills the entire screen of the device, hiding all elements of the browser's user interface, such as the address bar and other system notifications. It is ideal for games or apps that require a deep immersion, maximizing the available screen space. |
+    | Standalone (Add to Home Screen) | The PWA behaves like a native app, running in a separate browser window and not displaying common browser elements such as the address bar. When added to the device's home screen, you can hardly tell the difference between a PWA and a native app. |
+    | Minimal-UI (not supported by Chrome) | The PWA displays a minimum of browser user interface elements, such as the address bar and some additional controls. It is a middle ground between Standalone mode and Browser mode. |
+    | Browser                  | The PWA opens like a regular browser page, with all the usual browser features visible, such as the address bar, tabs, and other interface controls. It doesn't change the standard way the user interacts with web content and is less immersive than the other display modes. |
+
+    - **Add to home screen**: When activated, it allows the user to install the PWA.
+    - **"Add to home screen" prompt**: Defines the moment when the PWA installation will be recommended to the user. One of the following values can be assigned: On the first visit, On the first item added to the cart, or On the first order. This option only applies when **Add to Home Screen** is activated.
+
+   ![pwa-settings-3-en](//images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/8496511fdfbe7d9bdd30915bd0d4e3b9/pwa-settings-3-en.png)
+
+5. Save changes by clicking `SAVE`.
+
+## Using a custom service worker
+
+Our service worker supports native push prompts to install the app on the first visit, the first item added to the cart, or the first order. You can customize the notifications in your store's PWA using your own service worker, which will work alongside ours.
+
+To learn how to create your own service worker, see [How to install a service worker](https://help.vtex.com/en/tutorial/como-instalar-um-service-worker--2H057iW0mQGguKAciwAuMe).
+
+To learn how to leverage the service worker builder to group different service workers in your store, see [Using several service workers in your store](https://developers.vtex.com/docs/guides/vtex-io-documentation-using-several-service-workers-in-your-store).
diff --git a/docs/tutorials/en/configuring-redirects.md b/docs/tutorials/en/configuring-redirects.md
new file mode 100644
index 000000000..754999136
--- /dev/null
+++ b/docs/tutorials/en/configuring-redirects.md
@@ -0,0 +1,81 @@
+---
+title: 'Configuring redirects'
+id: 35JPufOvunMHnAAVJA6azu
+status: PUBLISHED
+createdAt: 2024-06-27T17:05:37.927Z
+updatedAt: 2024-06-27T17:06:40.835Z
+publishedAt: 2024-06-27T17:06:40.835Z
+firstPublishedAt: 2024-06-27T17:06:40.835Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configuring-redirects
+locale: en
+legacySlug: configuring-redirects
+subcategory: 
+---
+
+To configure a redirect, follow the steps below.
+
+1. In the VTEX Admin, go to  **Storefront**, or type  **Storefront** in the search bar at the top of the page.
+2. In **Intelligent Search**, click **Redirects**.
+3. Click the <i class="fas fa-plus"></i> `New`.
+4. Fill in the [general information](#general-information) fields detailed in the section below.
+5. Click <i class="fa-solid fa-plus"></i> `Add condition`.
+6. Fill in the [Trigger rules](#trigger-rules) fields.
+7. To finish, click `Apply`.
+
+You must fill in the fields below.
+
+![redirecionamentos-adminv4-EN](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
+
+### General information
+
+This section provides the following general information:
+
+- **Name:** name of the rule set for the redirect you created.
+- **Redirect URL**: URL to which the client will be forwarded. You must enter the full URL. Example: `https://www.store.com/_secure/account/#/orders` instead of `_secure/account/#/orders`.
+- **Locales:** Languages to which the redirect will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+### Trigger rules
+
+Trigger rules are a set of conditions related to terms or filters that will be applied to each search performed. At least one condition must be configured, either by term or by filter.
+
+Select the type of rule, either by term or by filter.
+
+- **Term:** word searched by the customer that will be related to the rule. You can choose between two options:
+    - `is`: the search must be an exact word search. Example: if you enter "Black Friday" and the customer searches for "Black Friday", the redirect will be triggered. If they search for "Black Friday promotion", the redirect will not be triggered.
+    - `contains`: the search does not have to be an exact word search. Example: if you enter "Black Friday" and the customer searches for "Black Friday", the redirect will be triggered. If the customer searches for "Black Friday promotion", it will also be activated.
+- **Filter:** searchable attribute already defined that restricts the search results. Selecting a registered filter enables the redirection created. Customers can choose from two filter options:
+    - `is`: this option allows the customer to select not only the filter for the rule. Example: if the rule is ``is``: Filter _brand_, value _Nike_. The redirect is triggered even if the customer also selects adidas.
+    - `only`: this option allows only the configured filter to be selected. Example: if the rule is ``only``: Filter _brand_, value _Nike_. If the customer selects adidas, the redirect will not be triggered. It will only work if the first brand filter is Nike.
+
+If you want to create more than one rule, you must add an interaction between the rules. They can be:
+
+- ``or``: any of the registered rules enable the redirection.
+- ``and``: to enable the redirection, all rules must be met.
+
+By clicking on <i class="fas fa-ellipsis-v"></i>, you will see the following options:
+
+- <i class="fas fa-clone"></i> **Duplicate:** creates a copy of the selected rule.
+- <i class="far fa-trash-alt"></i> **Delete:** deletes the selected rule.
+
+To clear all configured rules, click `Clear rules`.
+
+### Importing CSV files
+
+If you need to add several redirects, you can create a CSV file and import it into the Admin. The file must follow this format for each redirect created: `<Name>;<URL>;<Type>;<Active>;<Topic>;<Verb>;<Value>`.
+
+- **Name:** the title of the redirect. The possible values are `term` or `filter`.
+- **URL:** the redirect URL.
+- **Type:** trigger rule. The possible values are `and` or `or`.
+- **Active:** redirect activation condition. The possible values are `true` or `false`.
+- **Topic:** searchable attribute. Possible values are `term` for term redirection or `brand`, `category`, `department`, `sellername` and `subcategory` for filter redirection.
+- **Verb:** option to include the **Topic**. The possible values are `is` or `contains`.
+- **Value:** value of the term or filter.
+
+To import the file, follow the instructions below.
+
+1. In the VTEX Admin, go to  **Storefront**, or type  **Storefront** in the search bar at the top of the page.
+2. In **Intelligent Search**, click **Redirects**.
+3. Click `Import From CSV`.
diff --git a/docs/tutorials/en/configuring-samsung-pay-as-a-payment-method.md b/docs/tutorials/en/configuring-samsung-pay-as-a-payment-method.md
index fcf43143c..9020c9eac 100644
--- a/docs/tutorials/en/configuring-samsung-pay-as-a-payment-method.md
+++ b/docs/tutorials/en/configuring-samsung-pay-as-a-payment-method.md
@@ -3,8 +3,8 @@ title: 'Configuring Samsung Pay as a payment method'
 id: 5Yj9rgzOCVYuGmAumQlfpP
 status: PUBLISHED
 createdAt: 2020-08-26T13:40:16.356Z
-updatedAt: 2023-03-29T01:17:07.597Z
-publishedAt: 2023-03-29T01:17:07.597Z
+updatedAt: 2024-07-24T13:36:58.723Z
+publishedAt: 2024-07-24T13:36:58.723Z
 firstPublishedAt: 2020-08-26T16:30:52.180Z
 contentType: tutorial
 productTeam: Financial
@@ -15,27 +15,21 @@ legacySlug: configuring-samsung-pay-as-a-payment-method
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-This tutorial aims to show you how to configure the Samsung Pay digital wallet as a payment method.
+At VTEX, you can use the Samsung Pay digital wallet as a payment method in your store.
 
-The first step is to configure the Adyen connector in your store, Adyen being a gateway affiliation that processes payments made with Samsung Pay. You can check the complete step by step [here](https://help.vtex.com/en/tutorial/como-configurar-o-gateway-adyen-na-vtex--tutorials_2337?locale=en "here").
+Firstly, you need to configure the [Adyen](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv) payment provider in your store, as it will be responsible for processing payments received via Samsung Pay.
 
-Thereafter, you should configure the payment method itself.
+Then you need to configure Samsung Pay according to the steps below:
 
-Follow these instructions:
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on the __Samsung Pay__ option.
+4. Activate the condition in the __Status__ field.
+5. Under __Process with Provider__, select the __Adyen__ option.
+6. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+7. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456).
+8. Click on `Save`.
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Ensure that you are in the __Payment Conditions__ tab.
-3. Next to the search bar, click on the __green button “+”__.
-4. In the “Other” section, click on the __Samsung Pay__ option.
-5. On the top of the page, set a __name__ in the __Rule Name__ field.
-6. Below, click on the __Status__ button to activate the rule.
-7. In Process with affiliation, select the __Adyen__ option.
-8. If necessary, select the __Anti-fraud__ service that will be used. 
+To set special conditions for Samsung Pay, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-Thus, you will have carried out the most basic configuration of the payment method.
-
-However, there is still the option to __set special payment conditions__ - specific rules for Samsung Pay that apply only in certain contexts determined by expiration date, country, trade policy (Sales Channel), trade condition, or account name.
-
-Simply click on the white __"Add special condition"__ button and select which context the rule should apply to. Remember that you can set multiple special conditions for each payment method. For more details, check out the [tutorial on how to configure each of the special conditions](https://help.vtex.com/en/tutorial/condicoes-especiais--tutorials_456?locale=en "tutorial on how to configure each of the special conditions"). 
-
-If this does not apply to you, simply complete the configuration by clicking on the __"Save"__ button.
+After following the indicated steps, Samsung Pay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
new file mode 100644
index 000000000..db6c61f7b
--- /dev/null
+++ b/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
@@ -0,0 +1,51 @@
+---
+title: 'Configuring seller allocation for buying'
+id: 3VJtKNbLpVAl71uVdaOqpE
+status: PUBLISHED
+createdAt: 2023-12-21T18:05:34.497Z
+updatedAt: 2024-06-06T16:46:09.065Z
+publishedAt: 2024-06-06T16:46:09.065Z
+firstPublishedAt: 2023-12-21T18:07:21.012Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configuring-seller-allocation-for-buying-xky
+locale: en
+legacySlug: configuring-seller-allocation-for-buying-xky
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Manufacturers and distributors play a crucial role in the business-to-business (B2B) purchasing process. In certain scenarios, such as in marketplaces, their operational characteristics can lead to sales channel conflicts. Here are some examples:
+
+* Manufacturers: Have vast knowledge of their products and portfolio management but need to create online stores to better manage the 'sell-in' (selling products from the manufacturer to the distributor) and 'sell-out' (selling from the distributor to the end consumer) processes.
+
+* Distributors: Work directly with buying organizations and have complementary capabilities such as providing credit, large-scale training, and a large distribution network, but choose to develop their own selling portals.
+
+In this context, the buying organization needs to visit different channels, and the purchasing process becomes fragmented and inefficient.
+
+On VTEX, buying organizations (B2B) can create an allocation rule that allows them to purchase products directly from sellers that meet their operational or logistics needs.
+
+To assign sellers to a particular buying organization, follow the steps below:
+<ol>
+<li>In the VTEX Admin, go to <b>Apps > B2B Organizations & Cost Centers > Organizations</b>, or type <b>Organizations</b> in the search bar at the top of the page.</li>
+<li>In the <b>Organizations</b> tab, click the name of the desired buying organization.</li>
+
+![Organization](//images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/c127c65c00d63077e2a61463b8fcc2d7/ORGANIZACOES_-_EN.jpg)
+
+<li>In the <b>Sellers</b> tab, under <b>Disponible</b>, select the desired sellers.</li>
+
+![Details Organization](//images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/860e494a5cb6ed7c25ed7f7423ae082e/ORGANIZACOES-DETALHES2_-_EN__com_clique_.jpg)
+
+<li>Click the <b>ADD TO ORG</b> button.</li>
+
+![Details Organizations 2](//images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/ba7c7629dda12d95e114ecb0570e4927/ORGANIZACOES-DETALHES2_-_EN.jpg)
+
+<li>Click <b>Save</b>.</li>
+
+From now on, whenever the organization searches on the VTEX platform, only the products from the sellers assigned to it will be displayed.
+</ol>
+
+<div class="alert alert-warning">
+Buying organizations that do not assign sellers will be able to access information and purchase from all the sellers available on the marketplace.</div>
+
+For more information on how to integrate a new seller, read the[ Adding a seller](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392) article.
diff --git a/docs/tutorials/en/configuring-seo-in-your-store.md b/docs/tutorials/en/configuring-seo-in-your-store.md
new file mode 100644
index 000000000..84b86c211
--- /dev/null
+++ b/docs/tutorials/en/configuring-seo-in-your-store.md
@@ -0,0 +1,63 @@
+---
+title: 'Configuring SEO in your store'
+id: 1sKskEsjUSvgHyqM8oknVR
+status: PUBLISHED
+createdAt: 2024-04-29T19:07:56.533Z
+updatedAt: 2024-05-03T18:39:56.071Z
+publishedAt: 2024-05-03T18:39:56.071Z
+firstPublishedAt: 2024-04-29T19:26:31.511Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: YRJ73j8mt38D5TUleocQB
+slug: configuring-seo-in-your-store
+locale: en
+legacySlug: configuring-seo-in-your-store
+subcategory: 7ogirQ8NClawO2X6xdgCKc
+---
+
+SEO (Search Engine Optimization) is one of the most important strategies to better position your site on organic search engine results pages. Configuring tags, metatags, and favicons is part of this set of strategies to optimize your site's performance. 
+
+The title tag helps define the subject of the page for search engines and directly influences whether users click the search results. The description tag gives users an idea of what they can find on the site. The robots meta tag controls the crawling and indexing behavior of search engines.
+
+In all VTEX IO stores, you can configure these parameters natively by following the steps below.
+
+### Instructions
+
+#### Title tag, description tag, and robots meta tag
+
+1. In the VTEX Admin, go to **Store Settings > Storefront > Store**.
+2. Click the **General** tab.
+3. Complete the fields based on the guidelines below:
+
+  - **Store name**: Enter the name of your store.
+  - **Enable configuration by binding**: This option is only valid for stores with multiple bindings. By enabling it, you can configure specific settings for tags and meta tags for each store's bindings. For stores with a single binding, leave this option unchecked.
+  - **Default title tag**: Provide a concise description with relevant keywords. The value assigned to this tag is displayed at the top of the browser's title bar when someone visits your website.
+  - **Meta description tag**: Provide a brief description of the page's content. It should be informative and contain relevant keywords.
+  - **Meta robots tag**: Specify how search engines should crawl and index a specific page. The default values are `index, follow`. For additional values compatible with Google, see the [list of valid rules](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag#directives). 
+
+  ![seo-en](//images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/b545a83de82a94a5551a222f9b15b5a5/seo-en.png)
+
+### Favicons
+
+1. In the VTEX Admin, go to **Store Settings > Storefront > Store**.
+2. Click the **General** tab.
+3. Click **Add**.
+
+  ![favicon-en](//images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/bba39b30bedfe404b3111a06853a42de/favicons-en.png)
+
+4. A new screen will open for completion based on the following guidelines:
+
+   - **Favicon relationship**: Define the relationship between the URL configured in the **Favicon href** field and the site's favicon. For example, assigning the `icon` value indicates that the configured URL is related to the site's icon. 
+    - **Favicon media type** (optional): Specify the favicon type, following HTML and W3C standards. Learn more in [HTML Favicon](https://www.w3schools.com/html/html_favicon.asp).
+    - **Favicon size** (optional): Enter the favicon dimensions in the {width}x{height} format, e.g., 180x180.
+    - **Favicon href**: Enter the full URL pointing to where the favicon file is stored. 
+
+    See the example below:
+
+    ![relacao-favicon-en](//images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/9d4f662c2be71d1d33ec68495b594049/relacao-favicon-en.png)
+
+5. Click **Apply** to reflect the settings in your store. This process may take a few minutes.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+The <strong>Search term path</strong> field is a legacy setting that was compatible with <code>vtex.search-resolver@0.x</code>.
+</div>
diff --git a/docs/tutorials/en/configuring-shipping-promotions.md b/docs/tutorials/en/configuring-shipping-promotions.md
index e2fb90f13..49fb76aca 100644
--- a/docs/tutorials/en/configuring-shipping-promotions.md
+++ b/docs/tutorials/en/configuring-shipping-promotions.md
@@ -40,10 +40,10 @@ Below you will find some of the scenarios you can configure on the VTEX platform
 If you enable the option **Apply discount only to the cheapest shipping rate**, the discount will be applied only to the lowest estimated shipping rate. This option is enabled by default, but you can disable it if you prefer to configure the promotion according to [Scenario 3](#scenario-3) or [Scenario 4](#scenario-4). 
 
 #### Configuration
-![Apply the discount only to the cheapest shipping option - EN](https://images.ctfassets.net/alneenqid6w5/7MjVSslJUZjkcKepNjene6/630faf430976850a15d833f09919e515/image.png)
+![Apply the discount only to the cheapest shipping option - EN](//images.ctfassets.net/alneenqid6w5/7MjVSslJUZjkcKepNjene6/630faf430976850a15d833f09919e515/image.png)
 
 #### Result
-![saggin frete ingles.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
+![saggin frete ingles.PNG?h=250](//images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
 
 ### Scenario 2
 
@@ -53,27 +53,27 @@ If you disable the option **Apply discount only to the cheapest shipping rate**,
 ![Nenhum frete selecionado - EN](//images.contentful.com/alneenqid6w5/3hN4Ed2L4VP3us5NBQpEfV/ff352c5a835e77ed19dc2d5c33cddc73/image.png)
 
 #### Result
-![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Scenario 3
 
 If you enable only the **Shipping Method** option and select the shipping types you want, the shipping discount will be applied to all selected shipping types.
 
 #### Configuration
-![Shipping Method - EN](https://images.ctfassets.net/alneenqid6w5/3dR7FNv3WNUMeX6o97RywQ/8711094472ac78e3843290d769ad9c26/image.png)
+![Shipping Method - EN](//images.ctfassets.net/alneenqid6w5/3dR7FNv3WNUMeX6o97RywQ/8711094472ac78e3843290d769ad9c26/image.png)
 
 #### Result
-![saggin frete ingles.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
+![saggin frete ingles.PNG?h=250](//images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
 
 ### Scenario 4
 
 If you enable the options **Shipping Method** and **Apply discount only when one of the above carriers is selected by the customer** and select the shipping types you want, the shipping discount will be applied to all selected shipping types only when the customer chooses the shipping type at checkout.
 
 #### Configuration
-![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - EN](https://images.ctfassets.net/alneenqid6w5/3hxzt9qlLT4oWzBiAUUUrr/f64db376da1db7005848382bd2d2d532/image.png)
+![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - EN](//images.ctfassets.net/alneenqid6w5/3hxzt9qlLT4oWzBiAUUUrr/f64db376da1db7005848382bd2d2d532/image.png)
 
 #### Result
-![saggin frete ingles.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
+![saggin frete ingles.PNG?h=250](//images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
 
 In summary, the purpose of the option **Apply discount only when one of the above carriers is selected by the customer** is to apply the discount only when the carrier is selected.
 
diff --git a/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
new file mode 100644
index 000000000..1f2e9a958
--- /dev/null
+++ b/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
@@ -0,0 +1,88 @@
+---
+title: 'Configuring Sign in with Apple ID (Beta)'
+id: 5qprgEmHYfPTghnYwm0KrV
+status: PUBLISHED
+createdAt: 2023-09-05T17:38:23.553Z
+updatedAt: 2023-09-05T18:22:20.252Z
+publishedAt: 2023-09-05T18:22:20.252Z
+firstPublishedAt: 2023-09-05T18:22:20.252Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configuring-sign-in-with-apple-id-beta
+locale: en
+legacySlug: configuring-sign-in-with-apple-id-beta
+subcategory: 5uXA9a0laSLMkfbv6jQRDS
+---
+
+<div class="alert alert-info">
+  <p>This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/en-us/">our support</a>.</p>
+</div>
+
+On VTEX, customers don't need to create an account or log in to make a purchase. However, if they want to change the information provided during their first purchase, they must prove the email belongs to them.
+
+The platform natively allows logging in with email and password or using an access code sent to the customer's email. We also offer optional native integrations with Apple ID, [Google, and Facebook](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513), which need to be configured. This guide explains the required configuration to enable Sign in with [Apple ID](https://support.apple.com/apple-id) in your store:
+
+- [Prerequisites](#prerequisites)
+- [Registering on Apple](#registering-on-apple)
+- [Completing the authentication information](#completing-the-authentication-information)
+- [Testing Sign in with Apple ID](#testing-sign-in-with-apple-id)
+- [Limitations](#limitations)
+
+## Prerequisites
+
+Before configuring Sign in with Apple ID for your store, you need to have an[ Apple ID](https://support.apple.com/apple-id) and be enrolled in the [Apple Developer Program](https://developer.apple.com/programs/).
+
+## Registering on Apple
+
+To configure the login integration with Apple, you must create OAuth 2.0 credentials (the protocol used for integration) in this service. To do so, follow the instructions in our [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login) developer guide.
+
+## Completing the authentication information
+
+Once you have registered with Apple, enable the option of logging in to your store using this provider by following the instructions below. Make sure you have the credentials provided in the registration step.
+
+1. In the top bar of the VTEX Admin, click **your profile avatar**, indicated by the initial letter of your email address.
+2. Click **Account settings > Authentication**.
+
+    You will be redirected to the **Webstore** tab of the **Authentication** page, which lists the login methods available in your store.
+
+1. In the **Apple** row, click `Set Up`.
+2. Complete the configuration fields with the [credentials previously registered on Apple](#registering-on-apple):
+
+    - **Key ID:** Identifier of the private key generated by Apple that VTEX will use to generate the [OAuth client secret](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/).
+    - **Team ID:** Identifier of your team on the [Apple Developer Portal](https://developer.apple.com/).
+    - **Service ID:** Identifier of your Apple service, which will be used as the [OAuth `client_id`](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/).
+    - **P8 Certificate:** Private key saved as a text file with a `.p8` file extension generated only once by Apple when creating the key.
+
+    Check out the [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login) developer guide to learn how to get these credentials.
+
+    ![apple-id-setup-en](//images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/aa8a24c6942c41dc122db4172e6730f6/apple-id-setup-en.png)
+
+5. Click `Save`.
+6. Click `Webstore Providers` to go back to the previous page.
+7. Click the _switch_ <i class="fas fa-toggle-on"></i> to enable Apple as the login provider.
+
+## Testing Sign in with Apple ID
+
+Once everything is configured, you can test it. We recommend that you test the configuration with the final URL through which users will access your store. The Apple ID option should be available when you try to log in.
+
+1. Go to your store's website and click `Sign In`.
+2. Click `Sign in with Apple`. You will be taken to the Apple login window.
+3. Enter your Apple ID and password.
+4. Complete the two-factor authentication if requested.
+5. Choose whether to share your email with the app or [hide it](https://support.apple.com/en-us/HT210425) and click `Continue`. We recommend sharing the email, as there are [limitations](#limitations) with hidden email on VTEX.
+
+<div class="alert alert-info">
+  <p>The option of whether to share your email appears only when you first access the store with your Apple ID. After that, you only need to click <code>Continue</code>. To reset the email sharing option, visit <a href="https://appleid.apple.com/us/">Apple ID management</a>, revoke your store authorization, and log in again.</p>
+</div>
+
+By doing so, you will be logged in to the store.
+
+## Limitations
+
+Please consider the current limitations on logging in with Apple ID in VTEX stores:
+
+- Message Center is not compatible with Apple emails, so emails configured in the tool will not be sent to users who log in with an Apple ID.
+- If the user chooses to use Apple's [Hide My Email](https://support.apple.com/en-us/HT210425) feature, VTEX will generate a new account every time the user logs in.
+
+   This means that if someone initially logs in with an email and password, places an order, and later logs in using Apple ID with the hidden email feature enabled, VTEX will create a separate account. This new account will not be associated with the original account and will not allow access to order history or other user information. This action cannot be undone.
diff --git a/docs/tutorials/en/configuring-stripe-gateway-affiliation.md b/docs/tutorials/en/configuring-stripe-gateway-affiliation.md
index fcc063786..ed8e951cc 100644
--- a/docs/tutorials/en/configuring-stripe-gateway-affiliation.md
+++ b/docs/tutorials/en/configuring-stripe-gateway-affiliation.md
@@ -3,8 +3,8 @@ title: 'Configuring Stripe gateway affiliation'
 id: fwF2wk2FQKrODrWWkvSLO
 status: PUBLISHED
 createdAt: 2021-10-25T16:01:40.789Z
-updatedAt: 2023-03-22T19:17:05.286Z
-publishedAt: 2023-03-22T19:17:05.286Z
+updatedAt: 2024-04-25T12:58:35.923Z
+publishedAt: 2024-04-25T12:58:35.923Z
 firstPublishedAt: 2021-10-25T17:34:52.274Z
 contentType: tutorial
 productTeam: Financial
@@ -32,30 +32,40 @@ To process your payments with Stripe, you must:
 
 After installing the Stripe connector, follow the steps below to configure it on the VTEX platform.
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In **Gateway Affiliations**, click on the green "**+**" button.
-3. Search for the **StripeConnector** connector, and click on it.
-4. Then fill in the fields below with the following information:
-<ol><br/>
-  <li><strong>Application Key:</strong> Publishable key available in your <a href="https://dashboard.stripe.com/">Stripe dashboard</a>.
-  <li><strong>Application Token:</strong> Secret Key available in your <a href="https://dashboard.stripe.com/">Stripe dashboard</a>.
-</ol>
-5. Click on **Save**.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __StripeConnector__ in the search bar and click on the name of the provider.
+4. Fill in the fields below with the following information:
+<br>
+<ul>
+<br>
+    	<li><b>App key</b>: Publishable key available in your <a href="https://dashboard.stripe.com">Stripe dashboard</a>.</li>
+    	<li><b>App token</b>: Secret Key available in your <a href="https://dashboard.stripe.com">Stripe dashboard</a>.</li>
+</ul>
+5. Click on __Save__.
 
 After configuration in the VTEX environment, you also need to configure Webhook in your Stripe account.
 
 1. Go to your [Stripe account dashboard](https://dashboard.stripe.com/).
-2. Click on the **Developers** button.
-3. Click on the **Webhooks** tab.
-4. Click on **Add an endpoint**.
-5. In the **Endpoint URL** field, add your VTEX store’s endpoint URL in the format `https://{account-name}.myvtex.com/_v/notifications` replacing `{account-name}` with your VTEX account name.
-6. Click on **+ Select events**.
-7. Add the events that must be listened to.
-8. Click on **Add endpoint**.
+2. Click on the __Developers__ button.
+3. Click on the __Webhooks__ tab.
+4. Click on __Add an endpoint__.
+5. In the __Endpoint URL__ field, add your VTEX store’s endpoint URL in the format `https://{account-name}.myvtex.com/_v/notifications` replacing `{account-name}` with your VTEX account name.
+6. Click on __+ Select events__.
+7. Click on the categories and select the desired events. If you are not sure which events to add, please contact Stripe support and they can help you with this type of configuration.
+8. Click on __Add events__.
+9. Click on __Add endpoint__.
+
+<div class="alert alert-info">
+  <p>If you wish to carry out credit card transactions on Stripe, you must open a ticket on Stripe as follows:</p>
+  <p>- Request the release of the "raw card data" function, indicating that VTEX and Stripe are payment partners.</p>
+  <p>- Please attach the VTEX AOC (Attestation of Compliance for Onsite Assessments – Service Providers). To check the latest version of AOC VTEX, access the <a href="https://vtex.com/us-en/compliance/certifications">VTEX certifications</a> page and download the file available in the PCI section.</p>
+  <p>The above actions will prevent errors related to the transmission of sensitive data from occurring in the integration between Stripe and VTEX.</p>
+</div>
 
 ## Configuring a payment condition
 
-Once you have completed the steps above, Stripe will be ready to be used in your store. It will be available in the **Process with affiliation** field — provided that the payment method is compatible with Stripe — when creating a payment condition. 
+Once you have completed the steps above, Stripe will be ready to be used in your store. It will be available in the __Process with affiliation__ field — provided that the payment method is compatible with Stripe — when creating a payment condition. 
 
 Learn more in the article [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455).
 
@@ -63,11 +73,12 @@ Learn more in the article [Configuring payment conditions](https://help.vtex.com
 
 The Stripe connector allows you to add Google Pay as a payment method in your store's checkout. Once the Stripe connector is configured, you can add Google Pay by following the steps below.
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the **Payment conditions** tab, click on “**+**”.
-3. Search for the **Google Pay** condition and click on it.
-4. Toggle the status button to activate this payment condition.
-5. Click on **Save**.
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment conditions__ tab, click on `+`.
+3. Click on the __Google Pay__ option.
+4. Activate the condition in the __Status__ field.
+5. In __Process with affiliation__, select the __StripeConnector__ option.
+6. Click on __Save__.
 
 After this configuration, Google Pay will be displayed as one of the available payment methods in your store’s checkout.
 
@@ -82,24 +93,24 @@ Apple Pay currently only works on MacOs and IOS operating systems, and with  Saf
 Once the Stripe connector is configured, you can add Apple Pay by following the steps below.
 
 1. Go to [your Stripe account dashboard](https://dashboard.stripe.com/settings/payments) in the payments setup section.
-2. In **Settings**, click on **Payment Methods**.
-3. Click on **Apple Pay > Configure** and then **Add to new domain**.
+2. In __Settings__, click on __Payment Methods__.
+3. Click on __Apple Pay > Configure__ and then __Add to new domain__.
 4. Enter the public domain of your store's website.
-5. Click on **Donwload verification file** to save it to your device.
+5. Click on __Donwload verification file__ to save it to your device.
 6. Create the credentials [appkey and apptoken](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet).
 7. Make a call to the endpoint to send the previously downloaded verification file, adding the created credentials and your public domain address in the header (https://{{dominioPublicodoSite}}/well-known/raw/apple-developer-merchantid-domain-association).
-8. Click on **Add**.
-9. Access the **Admin** VTEX.
-10. Click on **Payments**.
-11. Then, click on **Settings**.
-12. In the **Payment conditions**, click on the **+** button.
-13. Click on **Apple Pay**.
-14. Fill the **Rule Name** field with a name of your choice for identification.
-15. Activate the condition in the **Status** field.
-16. In the **Process with affiliation** field, select the Stripe option.
-17. If you have an anti-fraud set up in your store, you can enable it for that payment condition by checking the **Use anti-fraud solution** box.
+8. Click on __Add__.
+9. Access the __Admin VTEX__.
+10. Click on __Payments__.
+11. Then, click on __Settings__.
+12. In the __Payment conditions__, click on the `+` button.
+13. Click on __Apple Pay__.
+14. Fill the __Rule Name__ field with a name of your choice for identification.
+15. Activate the condition in the __Status__ field.
+16. In the __Process with affiliation__ field, select the Stripe option.
+17. If you have an anti-fraud set up in your store, you can enable it for that payment condition by checking the __Use anti-fraud solution__ box.
 18. Choose whether payments will be with or without installments.
 19. It you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-especiais).
-20. Click on **Save**.
+20. Click on __Save__.
 
 After this configuration, Apple Pay will be displayed as one of the available payment methods in your store’s checkout.
diff --git a/docs/tutorials/en/configuring-the-scheduled-delivery.md b/docs/tutorials/en/configuring-the-scheduled-delivery.md
index 0c21f2256..0b1198e17 100644
--- a/docs/tutorials/en/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/en/configuring-the-scheduled-delivery.md
@@ -31,7 +31,7 @@ On **Inventory & shipping**, access **Dashboard** and select the desired **Carri
 Then on **Shipping method**, click on **Scheduled Delivery**.
 
 
-![entrega-agendada en](https://images.ctfassets.net/alneenqid6w5/5o3hYPSCha8IuYs2QOIgIc/09756c4259fc66808dafd6ce07e39eb8/entrega-agendada_en.png)
+![entrega-agendada en](//images.ctfassets.net/alneenqid6w5/5o3hYPSCha8IuYs2QOIgIc/09756c4259fc66808dafd6ce07e39eb8/entrega-agendada_en.png)
 For a better understandment about this sectin fields fulfillments, check out our document on how to [register a carrier](http://help.vtex.com/en/tutorial/registering-a-carrier).
 
 In this area, we have the following data:
@@ -45,7 +45,7 @@ In this area, we have the following data:
 Using the same situation of the store mentioned above, this would be the carrier configuration suitable to their demand:
 
 
-![entrega-agendada-exemplo en](https://images.ctfassets.net/alneenqid6w5/1VBGSFNpZ6KcM6wU0y62k0/956e0301532b9d2d615572e215d47e81/entrega-agendada-exemplo_en.png)
+![entrega-agendada-exemplo en](//images.ctfassets.net/alneenqid6w5/1VBGSFNpZ6KcM6wU0y62k0/956e0301532b9d2d615572e215d47e81/entrega-agendada-exemplo_en.png)
 
 Assuming that Inventory time is 2 days, Dock time is 1 day, and Freight Timetable previews 5 days, the first day available for delivery will be **8** days after the date the request was made and, since the maximum delivery time is 10 days, the last day available for customer's choice will be the **18th** day after the date the request was made.
 
diff --git a/docs/tutorials/en/configuring-the-store-domain.md b/docs/tutorials/en/configuring-the-store-domain.md
new file mode 100644
index 000000000..c9aca438f
--- /dev/null
+++ b/docs/tutorials/en/configuring-the-store-domain.md
@@ -0,0 +1,104 @@
+---
+title: 'Configuring the store domain'
+id: tutorials_2450
+status: PUBLISHED
+createdAt: 2017-04-27T21:55:00.603Z
+updatedAt: 2024-03-12T19:53:14.012Z
+publishedAt: 2024-03-12T19:53:14.012Z
+firstPublishedAt: 2017-04-27T23:03:51.625Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configuring-the-store-domain
+locale: en
+legacySlug: configuring-domains-in-license-manager
+subcategory: yMp6sKDiJEi66CGAIQ4ma
+---
+
+Domain-related settings are necessary for a web address to be correctly routed to a VTEX store. This guide covers the following topics:
+
+* [Store address structure](#store-address-structure)
+* [Rules for main hosts](#rules-for-main-hosts)
+* [How to register a new host](#registering-a-new-host)
+* [How to change the host from an active store](#changing-host)
+
+## Store address structure
+
+The store's address is composed of the following elements:
+
+![url-diagram-en](//images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/ad84010eef6bab7fae5123f18ab0887d/url-diagram-en.png)
+
+| Element | Description | Example |
+|---|---|---|
+| Protocol | Communication protocol used on the internet. | `https://` |
+| Subdomain | Prefix added to the domain name. | `www` |
+| Domain | Exclusive name used to locate and identify your store on the internet. | `mystore` |
+| Top Level Domain (TLD) | Suffix after the period of a domain name. | `com` |
+| Domain name / Pure domain / Root domain | Domain + top level domain. | `mystore.com` |
+| Host | Subdomain + domain + top level domain. | `www.mystore.com` |
+
+Once you have defined your store's domain, you need to configure the main host in the VTEX Admin to communicate between the address and the store's content.
+
+## Rules for main hosts
+
+Before proceeding with your store's address configuration, consider the following guidelines to ensure a successful implementation:
+
+* **CDN providers:** VTEX uses two CDN providers for the stores: **Cloudfront** and **Azion**. Make sure that your store's domain is not registered with these services during the pointing process. Otherwise, the CDN provisioning for your store and, consequently, the go-live will fail. Therefore, if your store's domain is registered on the Cloudfront or Azion platform, remove this registration before pointing the DNS to VTEX.
+* **Main address:** The store must have a single main host, which will point to the VTEX servers. This host **must contain a subdomain**, which can be `www` or others.
+* **Additional addresses:** Any additional addresses, whether with a different domain or a version without subdomains, must be redirected to the single main host, as described in the Redirects section.
+
+### Host examples
+
+Check out the host examples below and see which ones can be used as the main host:
+
+| Host example | Can be used as a host: yes (✔️) or not (❌) | Description |
+|---|---|---|
+| `www.mystore.com` | ✔️ | Contains the www subdomain. |
+| `mystore.com` | ❌ | Does not contain a subdomain. To configure access via this address, you must set up a host with a subdomain such as `www.mystore.com` and then create a redirect. Read [Best practices for accessing the store without www](https://help.vtex.com/en/tutorial/configuring-access-without-www--tutorials_4278) for more details. |
+| `store.mybrand.com` | ✔️ | Contains the store subdomain. |
+| `www.store.mybrand.com` | ✔️ | Contains two subdomains: `www` and `store`. |
+
+### Redirects
+
+To ensure your store is accessible via different URLs, such as `www.mystore.com` and `mystore.com`, you should register a single main host and redirect the additional addresses to the main one. Learn more about redirects:
+
+* [Redirection from other addresses](https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ)
+* [Best practices for accessing the store without www](https://help.vtex.com/en/tutorial/configuring-access-without-www--tutorials_4278)
+
+We recommend implementing a single host in your store.
+
+## Registering a new host
+
+To register a new host, they must comply with the guidelines specified in the [Rules for main hosts](#rules-for-main-hosts) section. Follow the instructions below:
+
+1. In the top bar of the VTEX Admin, click your profile avatar, indicated by the initial letter of your email address.
+2. Click the **Account settings** button.
+3. Click **Account**.
+4. Click the **Store** tab.
+5. Click the actions button corresponding to the store where you want to register the host and click `Edit`.
+6. Enter the host in the **Hosts** field. For example: `www.mystore.com`.
+7. Click `Add`.
+8. Click `Save`.
+
+After completing these steps, you can [configure DNS pointing to VTEX](https://help.vtex.com/en/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
+
+<div class="alert alert-warning">
+  <p><a href="https://www.faststore.dev/">FastStore</a> stores also need to configure an address with the <code>secure</code> subdomain. Refer to the<a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns"> Configuring external DNS for a custom domain</a> guide for more details.</p>
+</div>
+
+<div class="alert alert-danger">
+  <p>If your operation has more than one VTEX account or <a href="https://help.vtex.com/en/tutorial/como-criar-multiloja-multidominio--tutorials_510">sub-account</a>, don't change hosts from one account to another. This will cause failures in many aspects of your store.</p>
+</div>
+
+## Changing host
+
+The VTEX platform is designed to support host changes without adverse impacts. If you need to change your store's host, follow the steps below:
+
+1. Create new host entries for the store you want by following the instructions in [Registering a new host](#registering-a-new-host). At this stage, the DNS of the new domain must not yet be pointed to VTEX.
+2. In the VTEX Admin, check the Checkout settings in **Store Settings > Storefront > Checkout**, as described in the [Configure template in SmartCheckout](https://help.vtex.com/en/faq/configurar-template-no-smartcheckout/) article. Completing this step is crucial to ensure the Checkout will continue working after the change.
+
+    You need to check if the sites configured are associated with the account registered in **Account settings > Accounts**. See the [Account management](https://help.vtex.com/pt/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq) article for more details.
+
+3. Point the new domain's DNS to VTEX. Learn more about [DNS pointing](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex/).
+4. If your store uses [VTEX IO - Store Framework](https://developers.vtex.com/docs/guides/storefront-implementation) or [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), contact [VTEX support](https://help.vtex.com/en/support) and submit a request for internal pointing, specifying the new domain. Once the ticket has been opened, the support team has up to three business days to analyze the settings and complete the pointing process.
+5. After confirming the new host's DNS propagation and internal pointing, delete the old hosts and keep only the new one.
diff --git a/docs/tutorials/en/configuring-tuna-gateway-affiliation.md b/docs/tutorials/en/configuring-tuna-gateway-affiliation.md
index e8dc48772..da2ca40a7 100644
--- a/docs/tutorials/en/configuring-tuna-gateway-affiliation.md
+++ b/docs/tutorials/en/configuring-tuna-gateway-affiliation.md
@@ -3,8 +3,8 @@ title: 'Configuring Tuna gateway affiliation'
 id: 5Db0j4pE76ma9pUvYuAhfF
 status: PUBLISHED
 createdAt: 2021-07-07T14:47:34.162Z
-updatedAt: 2023-03-26T21:51:52.610Z
-publishedAt: 2023-03-26T21:51:52.610Z
+updatedAt: 2024-01-23T21:47:01.684Z
+publishedAt: 2024-01-23T21:47:01.684Z
 firstPublishedAt: 2021-07-07T14:57:45.358Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: configuring-tuna-gateway-affiliation
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, you can configure your store with the Tuna gateway affiliation to receive payments through: bank invoice, debit and credit cards, PIX and Bitcoin.
+At VTEX, you can configure your store with the Tuna gateway to receive payments through: bank invoice, debit and credit cards, PIX and Bitcoin.
 
 <div class="alert alert-warning">
   You can integrate your store with Tuna via <b>Application Key</b> and <b>Application Token.</b> To receive this information, you need to create your account first. To do so, please fill out <a href="https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform">this form</a> and wait to be contacted by Tuna with more details.
@@ -23,9 +23,9 @@ At VTEX, you can configure your store with the Tuna gateway affiliation to recei
 
 Once you have created your account and obtained the __Application Key__ and __Application Token__, follow the steps below to configure Tuna in your store:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __+__ button.
-3. Click on the __Tuna__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Tuna__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Tuna.
 5. In __Payment capture__, select one of the following options:
 
diff --git a/docs/tutorials/en/configuring-vtex-marketplace.md b/docs/tutorials/en/configuring-vtex-marketplace.md
index 8ced9e944..4048b3f36 100644
--- a/docs/tutorials/en/configuring-vtex-marketplace.md
+++ b/docs/tutorials/en/configuring-vtex-marketplace.md
@@ -3,12 +3,12 @@ title: 'Configuring a VTEX marketplace'
 id: 7splyp5MqIyt2Iyz5jsNzb
 status: PUBLISHED
 createdAt: 2022-01-26T21:27:16.808Z
-updatedAt: 2023-04-17T22:04:41.917Z
-publishedAt: 2023-04-17T22:04:41.917Z
+updatedAt: 2024-05-23T15:18:17.648Z
+publishedAt: 2024-05-23T15:18:17.648Z
 firstPublishedAt: 2022-01-26T23:06:58.565Z
 contentType: tutorial
 productTeam: Channels
-author: 0QBQws7rk0t5Mnu8fgfUv
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: configuring-vtex-marketplace
 locale: en
 legacySlug: setting-up-vtex-marketplace
@@ -73,7 +73,7 @@ You can define whether the seller’s store will be visible in your marketplace
 - **Identifiable seller:** the seller is visible on your marketplace storefront and the consumer can choose them from the buy box during the shopping experience.  
 - **Unidentifiable seller (white label):** [white label sellers](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label) are franchise accounts on VTEX. They are not displayed in the storefront during the shopping experience and are automatically selected by the checkout system to fulfill the order.  
 
-If you would like to add a white label seller, this model must be covered by your contract with VTEX. If you need to make changes to your contract, please contact our Support. Every franchise account is created as a white label seller. It is not possible to change the seller type after its creation. Learn more in [Adding sellers](https://help.vtex.com/en/tutorial/adding-a-seller--tutorials_392). 
+If you would like to add a white label seller, this model must be covered by your contract with VTEX. Once the VTEX business representative assigned to your marketplace has adjusted the contract, submit a request to add a franchise account by following the instructions in [Requesting the creation of a franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl#request-the-creation-of-a-franchise-account). Every franchise account is created as a white label seller. It is not possible to change the seller type after its creation. Learn more in [Adding sellers](https://help.vtex.com/en/tutorial/adding-a-seller--tutorials_392). 
 
 ### Location
 
diff --git a/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md b/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md
index 0931de76b..f2fab78b2 100644
--- a/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md
+++ b/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md
@@ -25,7 +25,7 @@ To do this, in the VTEX Admin, access **Storefront > Layout > CMS** and click on
 
 The button is in the upper right corner, as shown in the image below.
 
-!![copiar layout](https://images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
+!![copiar layout](//images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
 The system will ask you which web site you want to copy the layout to.
 
 Select the web site and click __Copy Layout__.
diff --git a/docs/tutorials/en/coupons-list-beta.md b/docs/tutorials/en/coupons-list-beta.md
index 3dc72ef1f..0ce3a6460 100644
--- a/docs/tutorials/en/coupons-list-beta.md
+++ b/docs/tutorials/en/coupons-list-beta.md
@@ -31,7 +31,7 @@ On this page, you can:
 
 To access this page in the VTEX Admin, click **Promotions > Coupons**.
 
-![lista-cupons](https://images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/d525a4dd9ed00d8895cd6be9fc96b538/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_15_22_1.png)
+![lista-cupons](//images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/d525a4dd9ed00d8895cd6be9fc96b538/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_15_22_1.png)
 
 Below you will find a description of the page components and the actions you can perform.
 
@@ -83,7 +83,7 @@ The generated file contains the information described below.
 
 Here is an example of an exported CSV file:
 
-![cupons-exportados](https://images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
+![cupons-exportados](//images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
 
 #### Exporting coupon batch codes
 
@@ -100,13 +100,13 @@ To view or export all the codes within a coupon batch, you must follow the steps
     * <i class="far fa-clone"></i> **Copy all:** Allows you to copy the generated codes to your clipboard. You can also copy each code individually by clicking it.
     * **Export:** Allows exporting the generated coupons to a CSV file. The exported file contains a single column, with one code per row.
 
-![export-coupons](https://images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/92c61578ca7684d4f9a80dbcf0b5f690/image_7.png)
+![export-coupons](//images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/92c61578ca7684d4f9a80dbcf0b5f690/image_7.png)
 
 ### View coupon usage
 
 To view the total number of active coupons and the remaining available space for new coupons, click <i class="fas fa-chart-line"></i> `Coupon usage`.
 
-![coupon-usage](https://images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7773a8f9dc9f68d349183cad1dcc082a/image_8.png)
+![coupon-usage](//images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7773a8f9dc9f68d349183cad1dcc082a/image_8.png)
 
 You are allowed a maximum of five thousand active coupons. To free up space, you can archive coupons in the [Coupon list](#coupon-list). If you need to increase the limit of active coupons, please contact our [Support team](https://support.vtex.com/hc/en-us/requests).
 
@@ -155,13 +155,13 @@ The **View usage details** modal presents information on how each coupon was use
 
     This section presents the list of orders in which a coupon has been used and allows you to search by order number. When you click on the order number, you will be redirected to the order details page in **Orders management**.
 
-![view-usage-details](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
+![view-usage-details](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
 
 * **General usage of the coupon codes** (coupon batches): Displays the total amount of times of the codes in a coupon batch have been used and the amount of remaining uses, if you have set a usage limit.
 
    This section also displays the list of codes in the coupon batch and allows you to search for a specific code. When you click on a code, you have access to the list of orders where the code has been used and you can search by an order number. Clicking on an order number will take you to the order details page in **Orders management**.
 
-![select-the-code-coupon-batch](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
+![select-the-code-coupon-batch](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
 
 ## Learn more
 * [Coupons](https://help.vtex.com/en/tutorial/coupons-beta--1aAEN3ADpz19ss5JCIEBdL)
diff --git a/docs/tutorials/en/creating-a-campaign-audience.md b/docs/tutorials/en/creating-a-campaign-audience.md
index 437b9332e..0a28bd351 100644
--- a/docs/tutorials/en/creating-a-campaign-audience.md
+++ b/docs/tutorials/en/creating-a-campaign-audience.md
@@ -3,8 +3,8 @@ title: 'Creating a campaign audience'
 id: 6cnuDZJzIkIeocewAQQK4K
 status: PUBLISHED
 createdAt: 2018-12-02T18:34:21.663Z
-updatedAt: 2023-03-31T13:38:38.613Z
-publishedAt: 2023-03-31T13:38:38.613Z
+updatedAt: 2023-10-31T19:23:55.713Z
+publishedAt: 2023-10-31T19:23:55.713Z
 firstPublishedAt: 2018-12-03T16:51:36.457Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -69,7 +69,7 @@ After clicking `Create New Target Audience`, you must follow the instructions be
     * **or:** The campaign audience will consist of customers fitting any target audience.
     * **and:** The campaign audience will consist of customers fitting all the target audiences, summing up all their criteria.
 
-![publico-alvo-e-ou-en](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
+![publico-alvo-e-ou-en](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
 
 ### Define your target audience
 
@@ -85,13 +85,12 @@ After clicking `Create New Target Audience`, you must follow the instructions be
 
 For example: The target audience includes items whose brand is **Nike**, as illustrated below. The configuration also indicates that at least 3 items must meet the criteria. Therefore, a customer must have at least **3** items in the shopping cart to be included in the target audience.
 
-![exemplo-marca-publico-alvo-en](https://images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7aeb73bd45e025ca84337c37d6800991/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_10_40_1.png)
+![exemplo-marca-publico-alvo-en](//images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7aeb73bd45e025ca84337c37d6800991/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_10_40_1.png)
 
 ### Conditions for your target audience to be applied
 
 * **Minimum order value:** Minimum value the items in the cart must have in total. The total considers the sum of the prices of cart items that meet all the campaign audience criteria.
 * **Maximum order value:** Maximum value the items in the cart must have in total. This total considers the sum of the prices of cart items that meet all the campaign audience criteria.
-* **Use history in promotion:** Allows the customer purchase history to be taken into consideration when evaluating whether they fit in the target audience. When checked, this option requires you to set a time frame for considering the purchase history. You can add specific dates or count the days from the submission date.
 * **Item price between __ and __:** Minimum and maximum price for each item in the cart. The campaign audience will be activated if the item value is within the range of the set values.
 * **Use restriction BINs:** The campaign audience will be activated if the credit card _Bank Identification Number_ (BIN) corresponds to the filled-in characters. The BIN refers to the first 6 or 8 digits on a credit card and is used to identify the bank and the card label.
 * **Marketing Tags:**: this field prevents activating the campaign audience if the purchase is made using the [VTEX Subscriptions module](https://help.vtex.com/en/tutorial/how-subscriptions-work--frequentlyAskedQuestions_4453).
diff --git a/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md b/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
index 095ae5117..4cd412223 100644
--- a/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
+++ b/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'Creating a contingency pickup point to guarantee it as an option at checkout'
 id: 3mowqWEfjyM2g6WoWgE0Ao
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-04-01T16:02:02.437Z
-updatedAt: 2020-06-20T04:56:48.306Z
-publishedAt: 2020-06-14T22:20:33.622Z
+updatedAt: 2023-08-01T21:35:48.449Z
+publishedAt: 2023-08-01T21:35:48.449Z
 firstPublishedAt: 2019-01-25T17:26:19.150Z
 contentType: tutorial
 productTeam: Shopping
@@ -21,15 +21,19 @@ If your end customer buys a product on any of your channels (online or physical
 
 However, you may prefer this store to work as a pickup point __even in a stockout scenario__. For this, your logistics must make sure that the product will reach that store from another stock - for example, from the e-commerce one. In this case, you need to have an e-commerce shipping policy in which the pickup point of the physical store is configured.
 
-![contingency pickup](https://images.ctfassets.net/alneenqid6w5/7sxWH5eDPpCmNlEPfHiZF1/7a10b60e1273d58d9c2ca7610a9ba888/contingency_pickup.png)
+![Creating a contingency pickup point to guarantee it as an option at checkout](//images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/962f5bd2fb48459656477102f81644c2/diagrama-como-criar-um-ponto-de_contigencia-en.jpg)
 
 ## How to set up a contingency pickup point
 
-Follow these steps to implement a contingency stock:
-- In the administrative panel of the e-commerce or the store that you want to use as a fallback - that is, the store from which the products will leave the stock to supply the pickup point -, set up a new pickup point with the information from the physical store.
-- In the e-commerce or fallback store, create a new shipping policy. This shipping policy must have exactly the __same SLA type__ already configured in the pickup logistics you use in the physical store where the products will be picked up.
-- Link the newly created pickup point with this shipping policy.
+To implement a contingency pickup point, you need to configure the following steps:
 
-<div class="alert alert-info">
-With this, you will have two logistics routes with the same pickup point: one, coming from the local stock of the physical store; the other coming from the stock from another channel (e-commerce or another physical store). When a customer chooses this pick-up point at checkout, the two routes will compete. Whenever there is local inventory, its SLA will be better and therefore will prevail. When there is stockout in the local stock, the order will fall on the route you set up according to this article.
-</div>
+1. In the VTEX Admin, [add a new pickup point](https://help.vtex.com/en/tutorial/cadastro-de-pontos-de-retirada--2R5ClQiwe4KoSQgsuiOw4E) in the store with available inventory to serve this pickup point.
+2. [Create a new shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) with the same name as the shipping method already configured in the policy used in the physical store, where the products will be picked up.
+3. Link this new policy with the new pickup point you created.
+
+Thus, you will have two logistic routes: one using the physical store inventory and the other using the inventory of a different store.
+
+When the customer selects this pickup point at checkout, the system will proceed as follows:
+
+- If there is local inventory, the delivery time will be shorter. In this case, the main pickup point will be selected.
+- If there is no local inventory, the logistic route configured as contingency will be selected.
diff --git a/docs/tutorials/en/creating-a-coupon-beta.md b/docs/tutorials/en/creating-a-coupon-beta.md
index 338b2c9da..2f373532a 100644
--- a/docs/tutorials/en/creating-a-coupon-beta.md
+++ b/docs/tutorials/en/creating-a-coupon-beta.md
@@ -42,7 +42,7 @@ The form for creating or editing a coupon has the following fields:
 
 The top dashboard of the form for creating and editing coupons indicates the number of times a coupon has been used, the number of remaining uses of that coupon, and the number of promotions associated with the coupon, as illustrated below.
 
-![create-coupon-1](https://images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/12a3cfbee85e20584d8f110a419c6cfe/create-coupon-1.png)
+![create-coupon-1](//images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/12a3cfbee85e20584d8f110a419c6cfe/create-coupon-1.png)
 
 By clicking on the information on the dashboard, you may access the modal **View usage details**, which displays the following details.
 
@@ -54,11 +54,11 @@ By clicking on the information on the dashboard, you may access the modal **View
 
     If the coupon is a single coupon, this section presents the list of orders in which a coupon has been used and allows you to search by order number. When you click on the order number, you will be redirected to the order details page in **Orders management**.
 
-    ![view-usage-details](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
+    ![view-usage-details](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
 
     If it is a coupon batch, this section displays the list of codes from the batch and allows you to search for a specific code. If you click on a code,  you will see the list of orders where the code has been used and allows you to search for an order number. Clicking on the order number will then take you to the order details page in __Orders management__.
 
-![select-the-code-coupon-batch](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
+![select-the-code-coupon-batch](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
 
 ### General
 
@@ -94,7 +94,7 @@ If you have created a [coupon batch](https://help.vtex.com/en/tutorial/coupons-b
 * <i class="far fa-clone"></i> **Copy all:** Allows you to copy the generated codes to your clipboard. After that, you can paste them in a spreadsheet editor, such as Excel or Google Sheets. You can also copy each code individually by clicking it.
 * **Export:** Allows exporting the generated coupons to a CSV file. The exported file contains a single column, with one code per row.
 
-![cupons-gerados-en](https://images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/640d534c61c09cae6bb345bbbca25173/cupons-gerados-en.gif)
+![cupons-gerados-en](//images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/640d534c61c09cae6bb345bbbca25173/cupons-gerados-en.gif)
 
 ## Associating a coupon with a promotion 
 
diff --git a/docs/tutorials/en/creating-a-more-for-less-promotion.md b/docs/tutorials/en/creating-a-more-for-less-promotion.md
index 4126ec74d..f5b5ca82e 100644
--- a/docs/tutorials/en/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/en/creating-a-more-for-less-promotion.md
@@ -3,8 +3,8 @@ title: 'Creating a More for Less promotion'
 id: tutorials_325
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:17.186Z
-updatedAt: 2023-03-31T19:57:42.646Z
-publishedAt: 2023-03-31T19:57:42.646Z
+updatedAt: 2024-03-28T15:36:24.222Z
+publishedAt: 2024-03-28T15:36:24.222Z
 firstPublishedAt: 2017-04-27T23:03:15.551Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -20,34 +20,42 @@ The More for Less sales promotion gives customers a discount when they buy sever
 In this article, we explain the purpose of each field when configuring a **More for Less** promotion. Check out the configuration steps below.
 
 1. [Promotion overview](#1-promotion-overview)
-    - [Restrict this promotion to products from sellers](#restrict-this-promotion-to-products-from-sellers)
+    - [Restrict this promotion to sellers products](#restrict-this-promotion-to-products-from-sellers)
     - [Trade Policy](#trade-policy)
 2. [More for Less](#2-more-for-less)
-3. [What are the conditions for the promotion to be valid?](#3-what-are-the-conditions-for-the-promotion-to-be-valid)
+3. [Conditions for the promotion to be valid?](#3-what-are-the-conditions-for-the-promotion-to-be-valid)
 4. [Restrictions and limitations of use](#4-restrictions-and-limitations-of-use)
 
-Read our article [Promotion examples](https://help.vtex.com/en/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD) for more information.
+Read our article [Promotion examples](https://help.vtex.com/pt/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD) for more information.
 
 ## Creating a More for Less promotion
 
 1. In the VTEX Admin, go to *Promotions > Promotions*, or type *Promotions* in the search bar at the top of the page.
 2. Click on the `Create Promotion` button.
 3. Select the **More for Less** option.
-4. Fill in the promotion fields.
+4. Complete the promotion fields.
 5. Click on `Save`.
 
 ## 1. Promotion overview
 
+In this section, we provide information on the promotion overview.
+
 -**Name**: name of the promotion. Required field.
-- **Status**: option that defines if the promotion is active or inactive. Required field.
-- **Description**: internal description of the promotion. This field will be used for internal communication in your store to explain the sales promotion reason, for example, if it is part of a campaign or a clearance sale.
-- **Expiration date**: the promotion’s start and end date and time. You can choose a future date and time for the promotion to start on your website. If that is the case, the promotion will be in the scheduled status until the start date and time are reached. During the period the promotion is valid, its status will be active. When the end date is reached, the promotion status will automatically change to inactive. Required field.
-- **Use recurrence settings**: if you check this box, other checkboxes will be displayed to select the day of the week and the time of the day that the promotion will be in effect. Do not select this option if you want the promotion to be in effect every day of the week.
-- **Promotion is highlighted**: adds a banner with the promotion name to the window display and the product page. This banner will only be added if you use the correct promotion display control in the template: `<vtex.cmc:discountHightLight/>`. Required field.
+- **Status**: Activates or deactivates the promotion.
+- **Description**: An internal description of the promotion. The purpose of this field is to be used as internal communication in your store to indicate whether the promotion comes from a campaign, clearance sale, etc.
+- **Expiration date**: Start and end date and time of the promotion. You can use a future date and/or time for the promotion to start on your website. If configured this way, the promotion status will be displayed as follows:
+    - **Scheduled:** Before the selected start date and time.
+    - **Active:** During the scheduled promotion period.
+    - **Inactive:** After the selected end date and time.
+- **Use recurrence settings**:By selecting this option, you can configure the recurrence, such as the weekday and time.
+- **Additional information (optional):**: Allows you to add a name and value to the promotion.
+- **Promotion is highlighted:** Adds a tag with the promotion name to the window display and the product page. This tag will only be added if you use the right promotion display control in the template.<vtex.cmc:discountHightLight/>. Required field.
+
+![Dados gerais 1 - EN](//images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/244f3cfaeed58c7d6b5ae309ca815089/Dados_gerais_1_-_EN.png)
 
 ### Restrict this promotion to products from sellers
 
-In this section, you can define to which sellers the promotion will apply. You can determine which sellers will be included or excluded from the discount. 
+In this section, you can define to which sellers the promotion will apply. You can specify the sellers you want to include or exclude from the discount.
 
 - **Equal to**: select the name of the sellers you want to include.
 - **Different from**: select the name of the sellers you want to exclude.
@@ -55,81 +63,89 @@ In this section, you can define to which sellers the promotion will apply. You c
 For the promotion to be valid for all sellers, leave the field blank.
 
 <div class = "alert alert-warning">
-  <p>It is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:</p><ol>1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.</ol><ol>2. Leave the field blank.  In this way, all sellers will be included in the promotion.</ol>
+  <p>You cannot select a white label seller directly. To include a white label seller in the promotion, you have two options:</p><ol>1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.
+</ol><ol>2. Leave the selection empty, including all sellers. Here, all types of sellers — white label or not — will be added to the promotion.
+</ol>
 </div>
 
+![Restringir - EN](//images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/8dba06aef0da8ce4d546c0e2fea91917/Restringir_-_EN.png)
+
 ### Trade Policy
 
-In this section, you can set the trade policies that are valid for the promotion. You can include or exclude trade policies from the discount.
+In this section, you can set the trade policies valid for the promotion. You can include or exclude trade policies from the discount.
 
 - **Equal to**: select the trade policies you want to include.
 - **Different from**: select the trade policies you want to exclude.
-- **Provided by me (my store)**: trade policies with products from your store. You can select more than one trade policy.
-- **Delivered by me (other stores)**: trade policies in which your products are from third-party stores. You can select more than one trade policy.
+- **Provided by me (my store)**: Select trade policies with products from your store. You can select more than one trade policy.
+- **Delivered by me (other stores)**: Select trade policies in which your products are available in third-party stores. You can select more than one trade policy.
 
-For the promotion to be valid for all trade policies, leave it blank.
+For the promotion to be valid for all trade policies, leave the selection empty.
+
+![Politica - ES](//images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/50371b6897f37bce42ac8e70110ca90b/Politica_-_EN.png)
 
 ## 2. More for Less
 
 In this section, you can define the products, number of items, and discounts included in the promotion.
 
 - **The customer purchases** `quantity` **of the following products**: number of units of the same product that must be added to the cart for the promotion to apply. Required field.
-- **SKUs**: names or IDs of the SKUs to which the discount will apply. You can import a list of SKUs by clicking on the `Select a .txt file` button. The text file (.txt) must contain each SKU ID in a different row. You can also download the list of SKUs added to the field by clicking on the `Download SKU list` button.
-- **Collections**: selection of collections to which the promotion will apply. Note that the promotion will only apply to products in the collections you include in this field. You can add a collection by entering its name, and it is possible to select more than one collection.
+    - **SKUs**: names or IDs of the SKUs to which the discount will apply. You can import a list of SKUs by clicking on the `Select a .txt file` button. The text file (.txt) must contain each SKU ID in a different row. You can also download the list of SKUs added to the field by clicking on the `Download SKU list` button.
+    - **Collections**: Collections to which the promotion will apply. The promotion will only be applied to products in the collections listed in this field. You can add a collection by entering its name. You can also select more than one collection.
 
 <div class = "alert alert-info">
   <p>If you do not inform any product collection or SKU, the platform will not allow the creation of the promotion.</p> <p>
 </div>
 
 - **And gets** `number` **of these products**: the number of items defined to receive the discount. Required field.
-   - **With a discount of**: the percentage discount the customer will receive if they buy the number of items defined in the promotion. 
-   - **With a maximum price per item of**: the maximum price per item the customer will pay if they buy the number of items defined in the promotion. 
+   - **With a discount of**: the percentage discount the customer will receive if they buy the number of items defined in the promotion.
+   - **With a maximum price per item of**: the maximum price per item the customer will pay if they buy the number of items defined in the promotion.
 
-|![Leve mais por menos 1 - EN](https://images.ctfassets.net/alneenqid6w5/1csaRIYXrmWFwoxNttIBYg/c97d6de41f3b8d4bea23978ec305c57e/image.png)|
-|:--:| 
-| _Example of a “Buy 3, get 1 free” promotion_|
+![Leve Mais - EN](//images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/8e4b955432b5d2d10ab57e8de7a79b9d/Leve_mais_-_EN.png)
 
 ### Advanced settings
 In this section, you can specify how the discount will be applied.
+The discount must be applied:
 
-#### The discount must be applied
-
-- **Considering**: 
-  - **Any product**: the discount will be applied to different products in the collection or SKU list, even if the number of items per product is less than the number defined in the promotion. In this case, the system considers the sum of the eligible products in the shopping cart.
-  - **Only identical products and variations**: the discount will only be applied to a SKU. To use this option, you must have added a minimum number of items for the promotion. 
-
+- **Considering**:
+  - **Any product**: The discount will be applied to different products in the collection or SKU list, even if the number of items per product is less than the number defined in the promotion. In this case, the system considers the sum of the eligible products in the shopping cart.
+  - **Only identical products and variations**: The discount will only be applied to a SKU. To use this option, you must have added the minimum number of items for the promotion.
 - **To**:
   - **The lowest-priced products**: the discount will be applied to the cheapest items in the promotion.
   - **The highest-priced products**: the discount will be applied to the most expensive items in the promotion.
 
-![Leve mais por menos 2 - EN](https://images.ctfassets.net/alneenqid6w5/57U5OIjbYtvOcd2qoFe45/c137ac839cc4803e42f0ba245e6a9a7a/image.png)
+![Leve Mais por menos - EN](//images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/09d9ff06ee5085c52862aa85e5f8baa5/Leve_Mais_por_menos_-_EN.png)
 
 #### How must the discount be distributed?
 
 - **Only among the** `number` **products receiving the discount**: the discount will be applied in full to the selected number of products.
 - **Proportionally among the** `number` **products**: the discount will be equally distributed among the selected number of products.
 
-## 3. What are the conditions for the promotion to be valid?
+## 3. Conditions for the promotion to be valid
+
+In this section, we will detail the conditions you must apply for a promotion to be valid.
 
-- **Order’s minimum and maximum value**: the promotion will be applied to the gross price of the shopping cart without considering other promotions or the shipping rate.
-- **Price "from" and "to" are the same or Price "from" and "to" are different**: You can select only one option. Refers to the prices saved for that product.
+- **Order’s minimum and maximum amount**: The promotion will be applied based on the gross amount of the cart, not considering other promotions or shipping.
+- **Full price and discounted price are the same or Full price and discounted price are different:**: Refers to the added product prices. You can only select one option.
 - **Use restriction BINs**: the discount will be granted to users paying with cards whose BINs are among the numbers entered in this field.
 - **Customer cluster**: the discount applies if the customer is included in the cluster you select in this field. It is important to highlight that the cluster name must be written exactly as in the Master Data. Spelling errors will prevent the configuration from working correctly.
-- **utm_source**: the discount will be granted if the customer navigation uses a utm_source parameter corresponding to a listed one in this promotion. It is important to note that customers can only enter one utm_source at checkout.
+- **utm_source**: The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion. It is important to note that customers can only enter one utm_source at checkout.
 - **utm_campaign**: the discount will be granted if the customer navigation uses a utm_campaign parameter corresponding to a listed one in this promotion.
-- **Create a new coupon with the UTMs above**: create a coupon based on the UTM values selected above to give customers access to this promotion using only the coupon code.
-- **Payment system**: the discount will be granted if the payment method selected by the customer is the same as the one included in this field. This discount will only be applied at checkout when customers select the same payment method as determined in the promotion.
+- **Create a new coupon with the UTMs above**: Create a coupon based on the UTM values selected above to give customers access to this promotion using only the coupon code.
+- **Payment system**: Allows you to choose if the promotion will be applied to one or more of the selected payment methods.
 
   <div class = "alert alert-info">
-  <p> By default, you can add up to 20 payment methods per promotion. In addition, there is the possibility of customization to include up to 100 payment methods. If you need to use more than 20 payment methods, please contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
+  <p> By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
  </div>
 
+![Condições de promoção - EN](//images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/8efc11e8c289f9777a22e3b7d29362d5/Condi__es_de_promo__o_-_EN.png)
+
 ## 4. Restrictions and limitations of use
 
-- **How many times will this promotion be applied in your store**: limits the number of times the promotion can be applied. If you deselect the **unlimited** field, the **times** field becomes available to enter the maximum number of times the promotion can be applied. Since the promotion has already been created, this condition will only apply from the day it was configured, not affecting previous orders.
-- **How many times per customer will this promotion be applied**: the number entered in this field determines the maximum number of times each customer can use the promotion. If the above field is also selected, it will have a higher priority for action than this limit.
-- **Set maximum number of eligible items for each cart**: determines the maximum number of items in the cart to which the promotion can apply. Read [this article](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#restricting-promotional-products-in-cart) to learn how to configure this field.
-  If you do not select this option, the discount will be applied to the products of the collection or SKU list, even if the number of items per product is less than the number defined in the promotion. So the system will consider the sum of the eligible products in the shopping cart.
-- **Apply with other promotions**: if selected, more than one promotion can be applied simultaneously, regardless of the discount type. Learn more about [concurrent promotions](https://help.vtex.com/en/tutorial/understanding-competition-of-promotions--tutorials_2270).
-- **Apply with manual prices**: allows the promotion to apply to products whose prices were manually added via telesales. To enable the manual pricing feature, use the [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration) endpoint.
+In this section, you will find important information about the promotion conditions and restrictions.
+
+- **How many times will this promotion be applied in your store**: Limits the number of times the promotion will be applied. If you uncheck the **unlimited** field, the times field becomes available to enter the maximum number of times the promotion can be used. This only applies for orders created after the condition has been set up. It will not affect orders placed previously.
+- **How many times per customer will this promotion be applied in your store**:This field's value determines the maximum number of times each customer can benefit from the promotion. For example, if you set a limit of three uses and the promotion is applied three times on a single order, this will be considered a single use in relation to the total limit. This way, the customer can still use the promotion on two different orders. Note that this calculation is done regardless of how many times the promotion has been used on each individual order.
+- **Set maximum number of eligible items for each cart**: Defines the maximum number of items in the cart that will be affected by the promotion. Check out [this article](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy) to learn how to configure this field.
+- **Apply with other promotions**: if selected, more than one promotion can be applied simultaneously, regardless of the discount type. Learn more in the [How promotion competition works](https://help.vtex.com/en/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270) article.
+- **Apply with manual prices**: allows the promotion to apply to products whose prices were manually added via telesales. To enable the manual pricing feature, use the [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) endpoint.
 
+![Restrições e limitações - EN](//images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/4c779dc8723b31d77e1c36871d1bb051/Restri__es_e_limita__es_-_EN.png)
diff --git a/docs/tutorials/en/creating-a-product-collection.md b/docs/tutorials/en/creating-a-product-collection.md
index f414d87d0..007f1f36b 100644
--- a/docs/tutorials/en/creating-a-product-collection.md
+++ b/docs/tutorials/en/creating-a-product-collection.md
@@ -25,7 +25,7 @@ To create a collection, follow the instructions below.
 2. Click **Layout**.
 3. Click the folder **Product Clusters (Collections)**.
 4. Click `new collection`, illustrated below.
-	![Layout 4](https://images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
+	![Layout 4](//images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
 5. Fill in the required information:
 	- **Product Cluster Id:** collection identifier code. This field should not be filled in as it is automatically generated by the system when saving.
 	- **Name:** name of the collection.
@@ -49,17 +49,17 @@ Each group can be of one of the following types: __Inclusion__ or __Exclusion__.
 
 To create the Group, just click on the _new group_ button, as shown in the following picture.
 
-![Layout 5](https://images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
+![Layout 5](//images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
 
 To add all the products of a given Department to a Group, just select the Department in question as shown in item 1 of the following figure. This also applies to the products of a given Category (item 2) or sub-category (item 3).
 
-![Filtro_por_categoria](https://images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
+![Filtro_por_categoria](//images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
 
 ### Creating groups by brand
 
 To create a product group with one of more brands, just select the brand desired on the corresponding list. The brands are available in alphabetical order, and by clicking on the letter corresponding to the initial of the brand, the list expands to show the existing brands.
 
-![FIltro_por_marca](https://images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
+![FIltro_por_marca](//images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
 
 ### Creating groups by products in the pre-sale or launch period
 
@@ -73,7 +73,7 @@ These flags are a <em>complement</em> to the choice of products. It is important
 
 Unlike the previous version, where specific products were included using the Product ID, in the new module the manual inclusions are done using the SKU of a product. In the corresponding field, it is possible to type in the ID of one or several SKUs, separating the values with commas. E.g.: `2000004,2000009,2000005`. In spite of the difference in the manner of registration, in practice the effect will be the same, since by associating an SKU with a group, the "father" product of that SKU will also be added to the collection. Where a product has more than one SKU, just add one of the SKUs to the group, and all associated SKUs will be included in it. The field for including the IDs does not permit the typing of alphanumerical characters or the use of combinations of the keys `Control + C` and `Control + V`. Also, when the number of SKUs on the list exceeds 10 items, a pagination control will become available. To exclude an SKU from the list, just click on the red button beside the corresponding SKU.
 
-![Inserir_sku_espec_fico](https://images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
+![Inserir_sku_espec_fico](//images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
 
 ### Importing an SKU list to the group
 
@@ -83,7 +83,7 @@ Although group filters are very practical for automatically creating product gro
 
 After the spreadsheet has been imported by the system, the SKUs are displayed in the following manner:
 
-![Importar_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
+![Importar_lista_de_skus](//images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
 
 The IDs of inactive SKUs will not be imported, even if they are included in the spreadsheet.
 
@@ -93,7 +93,7 @@ _Remember that when one or more groups are selected, only the products in the in
 
 So the Administrator won't have to manually exclude several SKUs one by one, it is possible to also use the SKU importation resource in the same manner as exemplified above. In this case, after the file has been loaded, click on the option _excluir skus_ (item 1 in the picture).
 
-![Excluir_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
+![Excluir_lista_de_skus](//images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
 
 Obtain a model of a file for importation, both for including and excluding items from the collection [here](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "here").
 
@@ -101,4 +101,4 @@ Obtain a model of a file for importation, both for including and excluding items
 
 When the quantity of collections exceeds the display limit, which is twenty items, the collections may be found using the search field. The search must be done using the name of the collection.
 
-![Pesquisar_cole__o](https://images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
+![Pesquisar_cole__o](//images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
diff --git a/docs/tutorials/en/creating-a-shipping-policy.md b/docs/tutorials/en/creating-a-shipping-policy.md
new file mode 100644
index 000000000..b8ae29045
--- /dev/null
+++ b/docs/tutorials/en/creating-a-shipping-policy.md
@@ -0,0 +1,73 @@
+---
+title: 'Creating a shipping policy'
+id: 66rJO4LKBdyMJOH6Z3dsaT
+status: PUBLISHED
+createdAt: 2024-01-30T21:08:12.106Z
+updatedAt: 2024-06-11T19:05:19.723Z
+publishedAt: 2024-06-11T19:05:19.723Z
+firstPublishedAt: 2024-01-31T01:09:33.011Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: creating-a-shipping-policy
+locale: en
+legacySlug: creating-a-shipping-policy
+subcategory: 7fTH6bP0C4IaM8qWi0kkQC
+---
+
+[Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) is a set of rules and settings that define the shipping options displayed to customers at checkout. The relationship between shipping policy,[warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb), and [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) makes up your [shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) on VTEX.
+
+This article explains how to create a shipping policy via VTEX Admin. If you wish to manage your shipping policies, see the article [Managing shipping policies](https://help.vtex.com/en/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE).
+
+To create a shipping policy, follow the steps below:
+
+1. In the VTEX Admin, go to **Shipping > Shipping Strategy > Shipping Policies**, or type **Shipping Strategy** in the search bar at the top of the page. 
+2. Click the `Create shipping policy` button.
+3. Fill in the fields on the screen as described below, and click `Save changes`.
+
+*   **Active/Inactive**: enables or disables the shipping policy.
+*   **Name**: the internal name of the shipping policy.
+*   **ID**: the internal identifier also used for integrators. You must fill in this field only with letters and numbers, do not use spaces. If it is not filled in, an ID will be created automatically.
+*   **[Shipping method](https://help.vtex.com/en/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126)**: the delivery type,  which is used to differentiate delivery services. It will be displayed for customers at checkout. For example, express vs. standard shipping.
+*   **[Upload shipping rates](https://help.vtex.com/en/tutorial/como-montar-a-planilha-de-frete--tutorials_127)**: this is where you upload the spreadsheet with the shipping rates and delivery time frames based on the shipping policy.
+*   **[Package dimensions](https://help.vtex.com/en/tutorial/como-funciona-o-empilhamento--tutorials_124):**
+    *   **Sum of all dimensions:** size limit of the package. It considers the sum of the lengths of all edges of the box. If this limit is exceeded, the order will be split into two or more packages or the delivery will not be made. This information is given by the carrier when the contract is signed.
+    *   **Largest edge:** size limit of the largest edge of the package. If this limit is exceeded, the order will be split into two or more packages or the delivery will not be made.
+    *   **[Cubic weight factor](https://help.vtex.com/en/tutorial/como-o-peso-cubado-e-calculado--tutorials_128)**: the factor that will be used to calculate the dimensional weight of the package. The sum of measures divided by the cubic factor.
+    *   **Minimum weight factor:** use the cubic weight only if it exceeds this value. If this is the case, the cubic weight will be considered for calculating the shipping rate.
+*   **Weekends and holidays:** days on which deliveries can be made. Click the toggles to enable or disable delivery in the following scenarios: `Saturday Delivery`, `Sunday Delivery`, `Holiday Delivery`.
+*   **[Active modals](https://help.vtex.com/en/tutorial/como-funciona-o-modal--tutorials_125):** specifications for products that require special delivery. They indicate product shipping limitations covered by the shipping policy. Check the boxes to enable delivery in the following scenarios: `chemicals`, `electronics`, `furniture`, `glass`, `liquids`, `mattresses`, `refrigerated products`, `tires`,`appliances`, and `firearms`.
+*   **Package items:** specification of the price and number of items in the package.
+    *    **Minimum value:** minimum shipment price accepted by the shipping policy to make the delivery.
+    *   **Minimum of Items:** minimum multiple of the quantity of items accepted by the carrier. For example, if the value is **3**, it means that the carrier only ships items with quantities multiple of three (3, 6, 9, 21...).
+    *   **Maximum value:** the maximum shipment price accepted by the shipping policy to make the delivery.
+*   **Link pickup points:** Click the toggle to view the pickup point options. Choose one of the options and fill it in by clicking on its dropdown menu. You can select between `Pickup points tags`, `Pickup points names`, or `Import sellers' pickup point` that have been previously configured in your store.
+*   **[Business Hours:](https://help.vtex.com/en/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS)** the time frames in which the carrier ships items to customers and the times at which it picks up items for delivery, as specified in the shipping policy. These settings influence the calculation of delivery time.
+    *    **Shipping Window:** here you can add the time frames in which the carrier ships items to customers. To configure it, select the `Shipping Window` card.
+        *    `Accept purchases outside working hours`: click the toggle button to enable or disable the option to receive orders outside working hours. When this option is enabled and an order is placed outside working hours, the time until the next available shipping window will be added to the total delivery time.
+        *   Select the `Day of the week`, the `Start time`, and the `End time`.
+        *   To add more days of the week, click on `Add shipping window`.
+    *    **Pickup Time:** here you can add the times at which the carrier will pick up packages from your warehouse or distribution center to send them to end customers. If an order is placed after the pickup time, the time until the next available pickup time will be added to the total delivery time.
+        *   Select the `Day of the week` and the `Pickup time`.
+        *   To add more days of the week, click on `Add pickup time`.
+
+<div class="alert alert-warning">
+The <b>Shipping Window</b> and <b>Pickup Time</b> are options that exclude each other since a period cannot simultaneously be allocated to different actions.
+</div> 
+
+*   **[Scheduled delivery](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)**: this feature can be enabled if this service is included in your shipping policy. Here you must add the delivery windows that will be displayed to customers at checkout. To use this feature, click the toggle and fill in the following fields:
+    *    **Maximum delivery time:** the maximum number of days to deliver a product.
+    *   **Delivery windows:** the time frames during which the carrier delivers packages to customers. Set the days of the week, the `Start` and `End` times, and any additional rates. Click `Add delivery window` to set more time frames.
+    *   **Delivery capacity:** allows you to limit how many items/orders can be delivered in each delivery window. This feature is optional.   To learn more about these features, check out the articles[Scheduled delivery](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) and [Managing delivery capacity](https://help.vtex.com/en/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz). If you enable this feature, you must:
+        *   Choose a delivery capacity unit (`items` or `orders`).
+        *   Check the delivery windows.
+        *   Define the `delivery capacity`. We recommend choosing the delivery capacity unit and the maximum number of items carefully because the system does not consider the number of items in the cart to calculate the delivery window availability. So if a delivery window has a remaining capacity of 2 items and your customer is buying 4 items, they will be able to select this delivery window.
+
+            Once the delivery window has reached its full `delivery capacity` it will no longer be available to customers. To make a delivery window available to customers again, you must increase the number of items/orders in its `delivery capacity`.
+
+ ### Learn more
+
+ * [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+ * [Managing shipping policies](https://help.vtex.com/en/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE)
+ * [Shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
+
diff --git a/docs/tutorials/en/creating-a-subscription-plan.md b/docs/tutorials/en/creating-a-subscription-plan.md
index f202df03a..63bb7afbf 100644
--- a/docs/tutorials/en/creating-a-subscription-plan.md
+++ b/docs/tutorials/en/creating-a-subscription-plan.md
@@ -91,7 +91,7 @@ On this page, you can perform the following actions:
 
 * **Select**: by clicking on the <i class="far fa-square"></i> in the row of each product, you can select products or SKUs individually. Another option is to click on the first <i class="far fa-square"></i> and select all the products and SKUs displayed on the page to add them to the subscription plan, as illustrated in the example below.
 
-![selecionarskus EN](https://images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/f833322d9519810cbdd0d1b7e17e4551/selecionarskus_EN.gif)
+![selecionarskus EN](//images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/f833322d9519810cbdd0d1b7e17e4551/selecionarskus_EN.gif)
 
 * <i class="fas fa-chevron-down"></i> __button__: displays the SKUs, i.e., product variations.
 * **Add**: click on this button to add products or SKUs to the subscription plan.
diff --git a/docs/tutorials/en/creating-a-subscription-promotion.md b/docs/tutorials/en/creating-a-subscription-promotion.md
index c1c042b04..2c0fa9393 100644
--- a/docs/tutorials/en/creating-a-subscription-promotion.md
+++ b/docs/tutorials/en/creating-a-subscription-promotion.md
@@ -23,7 +23,7 @@ In this article, you will find the step-by-step instructions to create subscript
 4. Select the `Regular` option.
 5. In the **What are the conditions for the promotion to be valid?** section, select the **Is a subscription order** field. This option specifies that the promotion will apply to subscription orders. Only products with a subscription in the cart will receive the discount. To understand configuration possibilities, see the following conditions:
 
-![frequenciaenglish](https://images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/a13420f2bd7a22e963097a6e9d415e46/image2__2_.png)
+![frequenciaenglish](//images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/a13420f2bd7a22e963097a6e9d415e46/image2__2_.png)
 
 - **First orders**: orders that generate subscriptions but are not part of subscription cycles yet.
 - **Recurring orders**: orders from subscription cycles.
diff --git a/docs/tutorials/en/creating-a-trade-policy.md b/docs/tutorials/en/creating-a-trade-policy.md
index 6aecb3ae9..c35690bd9 100644
--- a/docs/tutorials/en/creating-a-trade-policy.md
+++ b/docs/tutorials/en/creating-a-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Creating a trade policy'
 id: 563tbcL0TYKEKeOY4IAgAE
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:49.369Z
-updatedAt: 2022-12-08T14:40:14.268Z
-publishedAt: 2022-12-08T14:40:14.268Z
+updatedAt: 2024-04-15T21:21:00.376Z
+publishedAt: 2024-04-15T21:21:00.376Z
 firstPublishedAt: 2019-01-24T22:14:00.848Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,38 +17,31 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 On VTEX, you can use [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) to group catalog, price, promotion, inventory, shipping logistics, and payment settings for different sales channels. Sales channels include marketplaces, ecommerce websites, physical stores, or B2B stores, for example.  
 
-The **Trade policies** section of the Admin features a list of all the trade policies added to your store. You can filter the results, search by keyword, and sort your store’s trade policies. The trade policy ID is automatically determined by the system based on the chronological order of creation. 
+<div class="alert alert-danger">
+By default, new trade policies are applied to all active sellers. If you wish to apply them only to a specific group of sellers, please specify that in the ticket.
+</div>
+
+## Manage trade policies
+
+The **Trade policies** section of the Admin features a list of all the trade policies added to your store. You can filter the results, search by keyword, and sort your store’s trade policies. The trade policy ID is automatically determined by the system based on the chronological order of creation.
 
-To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `Create a trade policy`.
+To define the logistics settings applied to this trade policy, you must [create or edit a loading dock](https://help.vtex.com/en/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW), related to the carriers of your choice, by entering the ID of the trade policy on the page for adding/editing loading docks.
 
-Requesting additional trade policies to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores is free of charge.
+To use the same catalog in more than one trade policy, access the
+[Associate Product with Trade Policy](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/salespolicy/-tradepolicyId-) documentation.
 
-1. In the Store Setup section, click on __Trade policies__.  
-2. Click on __New Trade Policy__.  
-3. Fill in the fields.  
-4. Click on __Save__.  
+## Request a trade policy
+
+To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), contact our Growth Operations team through [VTEX Support](https://help.vtex.com/en/support) by selecting **Commercial** and `Create a trade policy`. When requesting the creation of a trade policy via ticket, consider a response time of up to three business days.
 
 <div class="alert alert-info">
-To define the logistics settings applied to this trade policy, you must <a href="https://help.vtex.com/en/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW">create or edit a loading dock</a>, related to the carriers of your choice, by entering the ID of the trade policy on the page for adding/editing loading docks.
+For the use of additional trade policy to integrate with <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a>, <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner">certified connectors (partners)</a>, or other VTEX stores to be exempt from fees, orders must be associated with it.
 </div>
 
-## Filling in the fields
-- __Name__: the name that identifies your trade policy in other modules of the VTEX Admin.  
-- __Collection__: collection of products from the catalog that is valid for the trade policy.  
-- __Sellers__: checkbox that associates sellers with the trade policy rules.   
-- __Currency Code__: the currency that will be applied to the sales channel that uses this trade policy.  
-- __Currency Symbol:__ the symbol of the currency you have selected, which will be displayed with product prices in the sales channel that uses this trade policy. This field is optional. If you leave it blank, the system will fill it in with the default symbol of the selected currency.  
-- __Currency Decimal Places__: number of decimal places that product prices can have. This field is optional. If you leave it blank, the system will fill it in with the default value of the selected currency.  
-- __Country Code:__ the code of the country where the sales channel is located.   
-- __Culture Info:__ the language chosen for the trade policy, among the options available for the selected country.  
-- __Time Zone:__ the time zone determined for the trade policy in Universal Time Coordinated (UTC).  
-- __Active?:__ checkbox to activate or deactivate the trade policy in your VTEX environment.  
-- __Conditional Rule:__ customizable field where you can define an additional criterion for the trade policy. An example of a conditional rule is to limit access to the store through a [customer cluster](https://help.vtex.com/tutorial/como-criar-um-cluster-de-clientes).  
-- __Inherit trade policy catalog:__ indicates whether the trade policy you are creating will "inherit" the catalog of an existing trade policy. If the policies are different but share the same catalog, we recommend filling in this field to optimize system performance.  
-
 ## Learn more
 
 - [How trade policies work](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)  
 - [Trade policy for marketplaces](https://help.vtex.com/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)
+- [Requesting an additional trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X)
 - [Adding a loading dock](https://help.vtex.com/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW)
 
diff --git a/docs/tutorials/en/creating-a-type-of-list.md b/docs/tutorials/en/creating-a-type-of-list.md
index 676847439..ac593c77b 100644
--- a/docs/tutorials/en/creating-a-type-of-list.md
+++ b/docs/tutorials/en/creating-a-type-of-list.md
@@ -61,7 +61,7 @@ The store owner decides if a list will be related to an event. Once the type of
 
 When **Have an event** is selected, the form offers other configuration options for the event, including all the deadlines for creating this type of list, as shown below.
 
-![eventos.en](https://images.ctfassets.net/alneenqid6w5/2ThHmo4PQitWv6EJAoVIdF/7eb8e5c05fee152945b70b3844f63ac0/eventos.en.png)
+![eventos.en](//images.ctfassets.net/alneenqid6w5/2ThHmo4PQitWv6EJAoVIdF/7eb8e5c05fee152945b70b3844f63ac0/eventos.en.png)
 
 The events area must determine whether a list has a fixed date for the event. Wish lists and purchases lists do not require a fixed date. On the other hand, wedding lists or baby showers must take the date of the event into account, with all the products purchased being delivered in advance.
 
@@ -79,7 +79,7 @@ The following options are available:
 
 After creating the type of list, you will be directed to the screen showing the types of list already registered in the store. This screen provides the following information and functions:
 
-![listagem.en](https://images.ctfassets.net/alneenqid6w5/4vHN91gXTrDhXKKa5hEc42/2f28b377bbfcb2cc548b3ce80155037f/listagem.en.png)
+![listagem.en](//images.ctfassets.net/alneenqid6w5/4vHN91gXTrDhXKKa5hEc42/2f28b377bbfcb2cc548b3ce80155037f/listagem.en.png)
 
 - **Export to Excel**: Allows data for list types to be exported to Excel;
 - **Version**: Identifies lists created in a previous version, with limited functions. The latest version is the “V2”;
diff --git a/docs/tutorials/en/creating-an-application-in-master-data.md b/docs/tutorials/en/creating-an-application-in-master-data.md
index 819cbf1a6..cb62bce51 100644
--- a/docs/tutorials/en/creating-an-application-in-master-data.md
+++ b/docs/tutorials/en/creating-an-application-in-master-data.md
@@ -3,8 +3,8 @@ title: 'How to create an application in Master Data'
 id: tutorials_1115
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:27.067Z
-updatedAt: 2023-03-28T23:26:06.249Z
-publishedAt: 2023-03-28T23:26:06.249Z
+updatedAt: 2024-06-25T20:45:29.002Z
+publishedAt: 2024-06-25T20:45:29.002Z
 firstPublishedAt: 2017-04-27T23:03:43.159Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,32 +15,33 @@ legacySlug: creating-an-application-in-master-data
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-“Application” is a grouper of forms. Its function is to organize, divide and establish refined accesses by area. In other words, you must create an application and the forms within this application, in order to facilitate the organization of data as required. For example: Atendimento Application; Cliente and Ticket forms.
+An application is a grouping of forms that organizes, divides, and establishes refined access by topic in Master Data. When you create an application, you can include several forms within it, making it easier to organize data as needed. For example, in the Support application, you can have Customer and Ticket forms.
 
-## How to create the application
+## Creating applications
 
-1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. Click on the tab **Aplicações**.
-3. Click on the button **Criar Aplicação**.
-4. Enter the name of the **Aplicação**.
-5. Fill out the field **Criar Cópia De** if you intend to copy the forms from another application.
-6. Click on the **Salvar** button.
-7. When uploading the applications page, click on the button **Recarregar Aplicações**.
+Follow the instructions below to create a new application:
 
-<video class="wp-video-shortcode" id="video-1115-2" width="840" height="411" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4?_=2" />[//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4](//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4 "//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4")</video>
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data**.
+2. Click the `Create applications` button.
+3. Enter the **Name** of the application.
+4. Select an option on the **Create copy of** field if you want to copy the forms from another application.
+5. Click the `Save` button.
 
-## How to edit the application
+## Editing applications
 
-1. Access the **Master Data** module;
-2. Click on the tab **Aplicações**;
-3. In the Application intended, click on the gear icon;
-4. Edit the application;
-5. Click on **Salvar**.
+Follow the instructions below to edit an application:
 
-## How to delete the application
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data**.
+2. In the desired application, click the gear icon <i class="fas fa-cog"></i>.
+3. Edit the application.
+4. Click `Save`.
 
-1. Access the **Master Data** module;
-2. Click on the **Aplicações **tab;
-3. In the desiredApplication intended, click on the gear icon;
-4. Click on the **Aplicações **option;
-5. In the desired Application, click on the **Excluir **button, in red.
+## Deleting applications
+
+Follow the instructions below to delete an application:
+
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data**.
+2. In the desired application, click the gear icon <i class="fas fa-cog"></i>.
+3. Click **Applications**.
+4. In the row of the application you want to delete, click the delete button ⛔.
+5. Click `OK`.
diff --git a/docs/tutorials/en/creating-an-oauth2-authentication.md b/docs/tutorials/en/creating-an-oauth2-authentication.md
index 7f8e4739e..190fa016f 100644
--- a/docs/tutorials/en/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/en/creating-an-oauth2-authentication.md
@@ -38,7 +38,7 @@ Have a look at the OAuth2 protocol official guide on https://tools.ietf.org/html
 ### Integrating OAuth2 with VTEX ID
 
 Based on the official documentation, have a look at the illustration below explaining how to integrate OAuth2 with VTEX ID:
-![Fluxo OAuth2 VTEX ID (EN)](https://images.ctfassets.net/alneenqid6w5/3qrMFrsucwq2eWSmSAe6yY/ee05f4dafad5d0e2005293274d8f30f8/Fluxo_OAuth2_VTEX_ID__EN_.png)
+![Fluxo OAuth2 VTEX ID (EN)](//images.ctfassets.net/alneenqid6w5/3qrMFrsucwq2eWSmSAe6yY/ee05f4dafad5d0e2005293274d8f30f8/Fluxo_OAuth2_VTEX_ID__EN_.png)
 
 Keeping the illustration in mind, let's have a closer look at some of the things you'll need to know.
 
diff --git a/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
index afaf02dbb..e6972b926 100644
--- a/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -22,7 +22,7 @@ To apply different prices to products via XML, you must associate a SKU price ta
   2. Find the XML file you want to edit and click on `Modify`. If you want to create a new file, please read our article [Configuring XML](https://help.vtex.com/en/tutorial/configuring-xml--tutorials_242).
   3. Here, you must check if the fields related to SKU price (lowest product price, highest product price, original SKU price, current SKU price and current SKU price + taxes) are filled in. For the operation to work correctly, at least one of these fields must contain information.
   4. Fill in the **Price tables ** field with the name of the desired price table. Then, click on the check box corresponding to the tag in the column **Show content**. The selected price table must have fixed prices registered. Otherwise, the configuration will not be performed.
-![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
+![PT-tabela de precos](//images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
 <div class="alert alert-warning">
   <p>Once the price table is included in the XML, all price fields will be overwritten.</p>
 </div>
@@ -35,4 +35,4 @@ After finishing the XML registration and saving the changes, you can check the i
 
 Example of updated XML:
 
-![XML-exemplo](https://images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
+![XML-exemplo](//images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
diff --git a/docs/tutorials/en/creating-collections-beta.md b/docs/tutorials/en/creating-collections-beta.md
index dddd00fc6..042ec4ae8 100644
--- a/docs/tutorials/en/creating-collections-beta.md
+++ b/docs/tutorials/en/creating-collections-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Creating Collections (Beta)'
 id: yJBHqNMViOAnnnq4fyOye
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-08-17T20:29:25.500Z
-updatedAt: 2023-03-29T14:50:46.438Z
-publishedAt: 2023-03-29T14:50:46.438Z
+updatedAt: 2024-03-04T20:48:30.215Z
+publishedAt: 2024-02-22T12:15:26.041Z
 firstPublishedAt: 2020-08-27T15:16:59.673Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -88,23 +88,23 @@ Selecting products through the VTEX Admin can be made using the product list, se
 
 There are many filters that can be selected to reduce the number of products displayed on the list.
 
-![Collections-EN](https://images.ctfassets.net/alneenqid6w5/7j4kfkpKZfrc6QwVNjrV6Z/5d19956173c19af3e823eec2b24869f3/Screenshot_2020-08-28_Collections.png)
+![Collections-EN](//images.ctfassets.net/alneenqid6w5/7j4kfkpKZfrc6QwVNjrV6Z/5d19956173c19af3e823eec2b24869f3/Screenshot_2020-08-28_Collections.png)
 
 You can create new filters based on other criteria not covered by the predetermined filters. The images below show a few examples of these options:
 
-![Novo filtro - EN](https://images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/4b679fbc6cfd2242327c9d6df77e555c/novo_filtro_-en.PNG)
+![Novo filtro - EN](//images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/4b679fbc6cfd2242327c9d6df77e555c/novo_filtro_-en.PNG)
 
-![Filtro Colecao detalhes - EN](https://images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/ce198baa55d995431c3cc77efb799920/Filtro_Colecao_detalhes_-_EN.png)
+![Filtro Colecao detalhes - EN](//images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/ce198baa55d995431c3cc77efb799920/Filtro_Colecao_detalhes_-_EN.png)
 
 To add a product to a collection, click on the icon <i class="fas fa-plus-circle" title = "check circle"></i> related to the product, thereby saving it in the collection automatically.
 
 For more information about the item, click on the icon <i class="fas fa-external-link-alt" title = "external link"></i> to open the product page or click on the image to enlarge it.
 
-![EN-colecao-adicionar](https://images.ctfassets.net/alneenqid6w5/4pb2cOOWDwe4g5ToGz0kvp/fbc71e22012ce56237470c4edfc7975e/EN-colecao-adicionar.gif)
+![EN-colecao-adicionar](//images.ctfassets.net/alneenqid6w5/4pb2cOOWDwe4g5ToGz0kvp/fbc71e22012ce56237470c4edfc7975e/EN-colecao-adicionar.gif)
 
 If you want to add in bulk, apply one of the filters and click on the `Add All` button. It is worth noting that the product must have at least one existing SKU to be included in a collection.
 
-![EN-colecao-adicionar-todos](https://images.ctfassets.net/alneenqid6w5/3Ftzj2gJy9qIskElyIE6u/f638b1ae74f9d545fe74ea8c15cec9f8/EN-colecao-adicionar-todos.png)
+![EN-colecao-adicionar-todos](//images.ctfassets.net/alneenqid6w5/3Ftzj2gJy9qIskElyIE6u/f638b1ae74f9d545fe74ea8c15cec9f8/EN-colecao-adicionar-todos.png)
 
 <div class = "alert alert-danger" >
   <p> Do not bulk add more than 150,000 products. This may affect the indexing of the Catalog and the operation of your store.
@@ -112,12 +112,14 @@ If you want to add in bulk, apply one of the filters and click on the `Add All`
 
 #### By spreadsheet
 
+<div class = "alert alert-info">The maximum limit for import and export is 10,000 SKUs per operation.</div>
+
 You can also add items to a collection using a spreadsheet by following the steps below:
 
   1. In your collection's dashboard, click on the `Import` button.
   2. Click on the **Include products in collection** option.
   3. Click on the `Import` button.
-  4. Click on `Download Template` to have the correct spreadsheet template as the example below: ![colecao-planilha-EN](https://images.ctfassets.net/alneenqid6w5/6liweo59r1TKnt8wWyELwN/8416f5bccd00dd42b5d326ba7cafca70/colecao-planilha.png)
+  4. Click on `Download Template` to have the correct spreadsheet template as the example below: ![colecao-planilha-EN](//images.ctfassets.net/alneenqid6w5/6liweo59r1TKnt8wWyELwN/8416f5bccd00dd42b5d326ba7cafca70/colecao-planilha.png)
   5. Fill in the spreadsheet with the Product IDs, RefIDs, or SKUs. Add a single ID on each line. Regardless of which ID you fill in, all SKUs for the selected product will be added to the collection after import.
   6. After filling out the spreadsheet, save the changes, and import the document into the VTEX Admin. You can drop the file in the indicated area or click on **Choose a file**. Files in CSV or XML format are accepted.
   7. To finish, click on `Import`.
@@ -134,11 +136,11 @@ Products can be removed either by selecting items from the __Collections__ modul
 
 To remove an item from the collection, simply click on the product's <i class="fas fa-check-circle" title="check circle"></i>.
 
-![EN-coleao-remover](https://images.ctfassets.net/alneenqid6w5/58uEn8gQKd7lr6KVqz0TTq/eb982d2665fc13dccb9e2beb08bebc0b/EN-colecao-remover.gif)
+![EN-coleao-remover](//images.ctfassets.net/alneenqid6w5/58uEn8gQKd7lr6KVqz0TTq/eb982d2665fc13dccb9e2beb08bebc0b/EN-colecao-remover.gif)
 
 If you wish to remove in bulk, apply one of the filters and click on the `Remove All` button.
 
-![EN-colecao-remover-todos](https://images.ctfassets.net/alneenqid6w5/5KE4KYqKWTAT2S5kqwpiKv/28e9b2b7a12e0a51d676a6af810c194a/EN-colecao-remover-todos.png)
+![EN-colecao-remover-todos](//images.ctfassets.net/alneenqid6w5/5KE4KYqKWTAT2S5kqwpiKv/28e9b2b7a12e0a51d676a6af810c194a/EN-colecao-remover-todos.png)
 
 You can also click on the button <i class="far fa-check-circle" title = "check in circle"></i> (**Products in this collection**) in the top bar and then click `Remove All`.
 
@@ -171,7 +173,7 @@ To change your collection's order, follow the steps below:
 
   b. Select the box of products you wish to change and click on `Move to Position`. Enter the number of the new position and click on `Move` to complete the change. These options allows you to rearrange items in bulk.
 
-![EN-mover-colecao](https://images.ctfassets.net/alneenqid6w5/4YOgWuUHzotJ2MOcFkQYFr/92212011dad70b167ae2d2d7c4a0baf6/EN-mover-colecao.png)
+![EN-mover-colecao](//images.ctfassets.net/alneenqid6w5/4YOgWuUHzotJ2MOcFkQYFr/92212011dad70b167ae2d2d7c4a0baf6/EN-mover-colecao.png)
 
 ### Export collection spreadsheet
 
diff --git a/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md b/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md
new file mode 100644
index 000000000..a9aeb638e
--- /dev/null
+++ b/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md
@@ -0,0 +1,60 @@
+---
+title: 'Creating custom queries in Master Data v1'
+id: tutorials_799
+status: PUBLISHED
+createdAt: 2017-04-27T21:57:44.496Z
+updatedAt: 2024-07-17T13:34:47.245Z
+publishedAt: 2024-07-17T13:34:47.245Z
+firstPublishedAt: 2017-04-27T23:03:43.119Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: creating-custom-queries-in-master-data-v1
+locale: en
+legacySlug: creating-a-personalized-master-data-query
+subcategory: 2AThnkEZAYbk4G4EIs53rL
+---
+
+A custom query in Master Data is a filter or combination of filters that can be saved and accessed directly in a form's record list.
+
+## Prerequisites
+
+Before creating a query, follow the steps described in[ How to filter data in Master Data](https://help.vtex.com/en/tutorial/filtrando-dados-no-master-data--tutorials_778) to set up a filter in the data entity and the form.
+
+## Saving a query
+
+Follow the steps below to filter the form records and save a custom query.
+
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data**.
+2. Make sure you are in the **Applications** tab.
+3. In the desired application, find the form you want to view and click the list icon <i class="fas fa-bars"></i>.
+
+    You will be redirected to the list of records for this form. On the side, you will see the configured filters.
+4. To filter, select the filter name and value, then click `Filter`.
+
+    You can filter by multiple fields at once, and use multiple values for a single field. To remove a filter, click the `X` next to its value.
+5. Click the `Save Query` button.
+6. Add a name to the custom query.
+7. Click `OK`.
+8. Click `OK` again.
+9. Click the **Applications** tab.
+10. Click the `Reload Applications` button.
+
+After following the instructions above, the query will appear as a display option in the form list.
+
+![queries-2-en](//images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/adb4b03eeb9c6060ac18eece60b2fff8/queries-2-en__1_.png)
+
+You can also access the saved queries by clicking the __Queries__ button in the form list:
+
+![queries-en](//images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/5f6ac592a3157c4285e4f818a20f349b/queries-en__1_.png)
+
+## Configuring a default query
+
+To set a form to always open the list with a custom query instead of displaying all the records, you can configure a default query. To do this, follow the steps below:
+
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data**.
+2. Make sure you are in the **Applications** tab.
+3. In the application where you want to change the form, click the gear symbol <i class="fas fa-cog"></i>.
+4. Click the edit icon <i class="fas fa-edit"></i> on the form row where you want to add the default query.
+5. In the **Default query** option, select the custom query you want to display whenever you open the form's record list.
+6. Click `Save`.
diff --git a/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md b/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md
index 2d924bbdf..ada0394d0 100644
--- a/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md
+++ b/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md
@@ -3,8 +3,8 @@ title: 'Creating Customer and Address forms in new stores'
 id: 46ETfuaGogKwaMau4ESAAM
 status: PUBLISHED
 createdAt: 2017-08-16T16:57:24.708Z
-updatedAt: 2023-03-28T22:59:22.957Z
-publishedAt: 2023-03-28T22:59:22.957Z
+updatedAt: 2024-06-11T17:38:43.775Z
+publishedAt: 2024-06-11T17:38:43.775Z
 firstPublishedAt: 2017-08-16T17:21:19.815Z
 contentType: tutorial
 productTeam: Master Data
@@ -36,13 +36,12 @@ Master Data v2
 You can produce these forms automatically, following the instructions below for each store.
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. After authentication, access the following URL, to make a requisition (GET) from the API: `meusegundosite.vtexcrm.com.br/api/crm/pvt/provisioning`.
-3. The result will be a blank screen on the browser, but this corresponds to a status "200" response.
-4. Wait a few minutes and then click on **Advanced area** in Master Data.
-6. Under **Do you want to clear the cache?** click on **Yes**.
-7. Go back to the Master Data home page.
-8. Click on **Reload Applications**.
+2. After authentication, access the following URL, to make a requisition (GET) from the API: `{storename}.vtexcrm.com.br/api/crm/pvt/provisioning`. Replace `{storename}` with your store's name.
 
-After this the **Profile System** application forms should be available in your Master Data.
+  The result will be a blank screen on the browser, but this corresponds to a status __200 OK__ response.
+3. Wait a few minutes and then click on **Advanced Settings** in Master Data.
+4. Under **Do you want to clear the cache?** click on **Yes**.
+5. Click on the **Applications** tab to go back to the Master Data home page.
+6. Click on **Reload Applications**.
 
-![3 - EN](https://images.ctfassets.net/alneenqid6w5/1bosLHh7Q0SiACOAqMCuco/1c0dad3f3d233e4635e32deaca0f1297/3_-_EN.png)
+After this, the **Profile System** application forms should be available in your Master Data.
diff --git a/docs/tutorials/en/creating-form-in-master-data.md b/docs/tutorials/en/creating-form-in-master-data.md
index 5a7d47692..b375c71a6 100644
--- a/docs/tutorials/en/creating-form-in-master-data.md
+++ b/docs/tutorials/en/creating-form-in-master-data.md
@@ -3,8 +3,8 @@ title: 'Creating a form in Master Data'
 id: tutorials_1047
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:35.614Z
-updatedAt: 2023-03-28T23:49:11.948Z
-publishedAt: 2023-03-28T23:49:11.948Z
+updatedAt: 2024-06-19T15:04:30.932Z
+publishedAt: 2024-06-19T15:04:30.932Z
 firstPublishedAt: 2017-04-27T23:03:43.083Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,37 +15,45 @@ legacySlug: creating-form-in-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-“Form” is the way a data entity is displayed and handled. Therefore, a form is a grouper of fields. Despite being always connected to an entity, the form does not necessarily need to have all the fields of the entity, and it can be adjusted according to your needs, that is, one single entity may include several forms. E.g.: Purchase form with Id, customer and date.
+A form serves as an interface for the visualization and manipulation of a data entity. Essentially, it acts as a field aggregator.
 
-## How to create a form
+Although always associated with a data entity, it is not mandatory for it to contain all the fields related to it; it can be customized according to demand. This way, it is possible to create different forms for the same entity, adapting to various needs. For example, a purchase form may include fields such as ID, customer, and date.
 
-1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data.**
-2. Click on the **Aplicações** tab.
-3. In the application in which you want to create the form, click on the gear icon.
-4. After opening the list of forms, click on the **Novo** button.
-5. Fill in the fields as below (fields are divided by section).
-6. Click on the **Salvar** button.
+To create a form, follow the steps below:
 
-## Understand the fields
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. Make sure that you are in the __Applications__ tab.
+3. In the application in which you want to create the form, click on the gear icon <i class="fas fa-cog"></i>.
+4. After opening the list of forms, click `New`.
+5. Fill in the fields as described in [Fields for the new form](#fields-for-the-new-form).
+6. Click `Save`.
 
-- **Nome: **Form name
-- **Filtros: **Fields marked as entity filters; these fields will make up the side filters of the form. The internal name of the field must be entered. If there is more than one field, separate them with comas. For example: campo1,campo2.
-- **Entidade de Dados: **this is the data entity in which the form will save and display the data.
-- **Destaques de busca: **fields that will be listed in the search results. The internal name of the field must be entered. If there is more than one field, separate them with comas. For example: when searching for a customer, the list of results must include the customer’s CPF and name; so, the field must be filled out with “cpf,nome.”
-- **Consultas na visualização: **enables a new section in the display form with the records of an entity related to the form’s entity. The information displayed will relate to the record that is being viewed. For example: The Atendimento entity includes a field related to the Cliente entity. So, in the “Consultas na visualização” field of the “Cliente” form, you must enter the “atendimento” field that refers to the Cliente. if the acronym of the Atendimento entity is AT, and the name of the field is “cliente,” you must enter: “AT.Cliente” to upload the customer service that is being viewed in the form. ![registrosRelacionados2](//images.contentful.com/alneenqid6w5/2NrlYdzzR66Og4waCIekGe/e4d47ef3e257c749c09c0c9151383c45/registrosRelacionados2.png)![registrosRelacionados](//images.contentful.com/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/d80177bdf01586c97f1321c74c881ac3/registrosRelacionados-1.png)
+## Fields for the new form
+
+- **Nome:** Form name.
+- **Filters:** Fields marked as entity filters; these fields will make up the side filters of the form. The internal name of the field must be entered. If there is more than one field, separate them with comas. For example: campo1,campo2.
+- **Data entity:** This is the data entity in which the form will save and display the data.
+- **Search highlights:** Fields that will be listed in the search results. The internal name of the field must be entered. If there is more than one field, separate them with comas. For example: when searching for a customer, the list of results must include the customer’s ID and name; so, the field must be filled out with `id,nome`.
+- **View queries:** Enables a new section in the display form with the records of an entity related to the form’s entity. The information displayed will relate to the record that is being viewed.   
+
+   For example, the __Shopping List__ entity includes a field whose type is __Relationship__, which is related to the __Customer__ entity. So, in the __View queries__ field of the __Customer__ form, you must enter the __Shopping List__ field that refers to the __Customer__.
+
+   If the acronym of the __Shopping List__ entity is __SL__, and the name of the field is __Customer__, you must enter: `SL.Customer` to upload the customer service that is being viewed in the form.
+
+   ![relatedRecords-en](//images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/b63c13d0278c701cce402b77c567f843/image_2.png)
 
 After filling out the mandatory fields, the tabs available for configuration will be displayed. See below the fields of these tabs.
 
-- **Campos da Listagem: **Select the fields included in the records list when clicking to view the form. To this end, just select the check boxes appearing at the side of the fields that you want to appear on the list. It is also possible to set up the width of the field on the list (column width), the display order and the ordering. The order of the fields on the list will follow the order viewed in this screen, that is, for a field to appear in the first column, click on the up arrow until it becomes the first field. Ordering is defined by one field. Select one field and choose between ascending (Asc) or descending (Desc) order.
-- **Schemas de Layout: **definition of how the fields will be displayed in the form, both for viewing, and for editing and creating the fields. That is, the position of each field in the form will be set up in this phase, and they also be divided by sections.
+- **List Fields:** Select the fields included in the records list when clicking to view the form. To this end, just select the check boxes appearing at the side of the fields that you want to appear on the list. It is also possible to set up the width of the field on the list (column width), the display order and the ordering.
 
-1. Click on the **Incluir nova seção **button;
-2. Fill out the **Nome** field;
-3. Drag one field from the **Campos disponíveis** list to the **Campos da coluna 1 **column. The same can be made regarding the **Campos da coluna 2 **column. 
+   The order of the fields on the list will follow the order viewed in this screen, that is, for a field to appear in the first column, click on the up arrow until it becomes the first field. Ordering is defined by one field. Select one field and choose between ascending (Asc) or descending (Desc) order.
+- **Layout Schemas:** definition of how the fields will be displayed in the form, both for viewing, and for editing and creating the fields. That is, the position of each field in the form will be set up in this phase, and they also be divided by sections.
 
-Repeat these 3 steps until you reach the format desired for the form. You can include several fields in a single column, as well as create several sections.
+   1. Click on the `Add New Section` button.
+   2. Fill out the __Name__ field to name the section.
+   3. Drag one field from the **Available Fields** list to the **Fields of Column 1** column. The same can be made regarding the **Fields of Column 2** column.
 
-- **Consultas: **this tab is only intended to show the [queries created on the list](/en/tutorial/creating-a-personalized-master-data-query/).
-- **Folha de Estilo: **place to enter the CSS for editing the front-end of the form.
+   Repeat these three steps until you reach the format desired for the form. You can include several fields in a single column, as well as create several sections.
 
-<video class="wp-video-shortcode" id="video-1047-3" width="840" height="411" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/7oRARnBsVamuk8iQ0mogQa/438e55214f38f7f16634da4fbc238d68/CriandoFormulario-1.mp4?_=3" /></video>
+- **Queries:** This tab is only intended to show the [queries created on the list](https://help.vtex.com/en/tutorial/creating-a-personalized-master-data-query--tutorials_799).
+- **Style Sheet:** Tab to enter the CSS to edit the frontend of the form.
diff --git a/docs/tutorials/en/creating-landing-pages-per-binding.md b/docs/tutorials/en/creating-landing-pages-per-binding.md
index 66598b267..2c4a3e32d 100644
--- a/docs/tutorials/en/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/en/creating-landing-pages-per-binding.md
@@ -23,7 +23,7 @@ In the Admin, you can create customized landing pages by [binding](https://help.
 2. Select the desired binding in which the new landing page should be created using the dropdown menu on the page.
 3. Click on the `Create New` button.
 
-  ![en-landing-page-binding](https://images.ctfassets.net/alneenqid6w5/5c1IxR9QguR726Urdu0du8/afe633c2ca2758a3af1191c269219aed/en-landing-page-binding.png)
+  ![en-landing-page-binding](//images.ctfassets.net/alneenqid6w5/5c1IxR9QguR726Urdu0du8/afe633c2ca2758a3af1191c269219aed/en-landing-page-binding.png)
 
 4. In the `Page` details section, fill out the fields to define your new landing page's metadata, according to the expected values:
 
diff --git a/docs/tutorials/en/creating-landing-pages.md b/docs/tutorials/en/creating-landing-pages.md
index c87d8b4e5..2d7ecb611 100644
--- a/docs/tutorials/en/creating-landing-pages.md
+++ b/docs/tutorials/en/creating-landing-pages.md
@@ -3,8 +3,8 @@ title: 'Creating landing pages'
 id: 2DqFleXKz0Vsg3KhHLuUEB
 status: PUBLISHED
 createdAt: 2022-02-02T13:57:03.484Z
-updatedAt: 2023-03-24T22:24:37.311Z
-publishedAt: 2023-03-24T22:24:37.311Z
+updatedAt: 2024-08-01T13:10:40.896Z
+publishedAt: 2024-08-01T13:10:40.896Z
 firstPublishedAt: 2022-02-02T14:41:53.952Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -28,7 +28,7 @@ In the Admin, you can create customized landing pages, such as pages for special
 
 2.Click **CREATE NEW**.
 
-![Creating Landing pages](https://images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/5b59a487ca74b9d420f754ec5ab9fa18/cms-pages-en.png)
+![Creating Landing pages](//images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/5b59a487ca74b9d420f754ec5ab9fa18/cms-pages-en.png)
 
 3.In the Page details section, fill in the fields below to define the page metadata:
 
@@ -40,6 +40,11 @@ In the Admin, you can create customized landing pages, such as pages for special
 | Description | Summary of the new web page to be displayed in search engine result pages. |
 | Keywords | Topics that define the page content and  help deliver the page to interested users in search engine results. |
 
+<div class="alert alert-warning">
+<p>To avoid conflicts and protect the integrity of the system, changing an existing URL route is not allowed. If you need to change a URL, we recommend creating a new page with the desired path and deactivating the old one if necessary.
+</p>
+</div>
+
 <div class = "alert alert-info">
 <p>The five fields above have a direct impact on store hits and search engine results rankings. Before filling in the page metadata, keep SEO best practices in mind.
 </p>
diff --git a/docs/tutorials/en/creating-merchandising-rules-manual-editor.md b/docs/tutorials/en/creating-merchandising-rules-manual-editor.md
new file mode 100644
index 000000000..c930cff02
--- /dev/null
+++ b/docs/tutorials/en/creating-merchandising-rules-manual-editor.md
@@ -0,0 +1,92 @@
+---
+title: 'Creating merchandising rules - Manual Editor'
+id: 3jrXB1MSvi14ezvKancorc
+status: PUBLISHED
+createdAt: 2024-06-27T17:14:53.957Z
+updatedAt: 2024-06-27T17:15:56.346Z
+publishedAt: 2024-06-27T17:15:56.346Z
+firstPublishedAt: 2024-06-27T17:15:56.346Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: creating-merchandising-rules-manual-editor
+locale: en
+legacySlug: creating-merchandising-rules-manual-editor
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Follow the steps below to configure a [merchandising rule](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) in the VTEX Intelligent Search Manual Editor.
+
+1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2. Under **Intelligent Search**, click **Merchandising Rules**.
+3. Click the <i class="fas fa-plus"></i> `New` button.
+4. Complete the fields (detailed below).
+   * **Rule name**: Name of the merchandising rule. Example: Promote product A when searching for a chocolate cookie.
+   * **Start date (optional)**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
+   * **End date (optional)**: Set a date on which the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
+   * **Apply to locales:** Languages to which the merchandising rule will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Click on **Manual editor**. For more information on each editor, see [Types of editing](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#types-of-editing).
+6. Click `Next`.
+7. If necessary, you can change what you have already filled in about the new merchandising rule in the [General Information](#general-information) section.
+8. Define the [Trigger rules](#trigger-rules), the set of conditions that determine when the merchandising rule will be applied.
+9. Define the [Customization rules](#customization-rules), the set of conditions that control the search results that meet the trigger rules set in step 8.
+   Add one or more conditions to apply the desired customization effect in this step. To learn how to add a condition, see [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+10. Click `Save`.
+
+<div class="alert alert-info">
+  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
+</div>
+
+## Example
+
+Imagine the following example: You want to promote Beautyx products during the 4th of July week. When the customer searches for "soap" or "shampoo", the search should promote the brand's products, so the configuration should be:
+
+* **Rule name**: 4th of July promotion
+* **Start date**: Select the first day of the 4th of July week.
+* **End date**: Select the last day of the 4th of July week.
+* **Trigger Rules:**
+   * `Term is soap`
+   `or`
+   * `Term is shampoo`
+* **Customization Rules**:
+   * **Promote**
+       * `Brand is beautyx`
+
+## Manual Editor fields
+
+### General information
+
+   * **Name**: Name of the merchandising rule. Example: Promote product A when searching for a chocolate cookie.
+   * **Start date**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
+   * **End date**: Set a date on which the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
+   * **Locales:** Languages to which the merchandising rule will apply.
+
+### Trigger rules
+
+* **Global trigger**: If you activate this option, the merchandising rule will always be active and cover all search terms and filters, and you won't need to set conditions for trigger rules. This allows you to add, remove, promote, and demote products from all searches in the store.
+   However, if you choose to keep the Global trigger disabled, you need to add at least one condition to build the trigger rules. See [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW) to learn more about adding a condition.
+* <i class="fa-solid fa-link"></i> `Autofill from a URL`: Add the search page URL where the trigger rules will be applied. The URL must include `map` and `query` to work, using the following format: `https://{accountName}.myvtex.com/busca/{term}?map=ft&query={term}`. You need to replace `{accountName}` with the VTEX account name and `{term}` with the search term.
+* `Add Condition`: When creating a condition, the merchandising rule only applies to cases that meet the established set of conditions. To learn how to create conditions, see [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+
+### Customization rules
+
+* **Add**: Includes the selected conditions in the result, which means it adds products that would not be displayed in the search results. The sorting of the added products is not considered in the search results.
+   Added products are also ranked in the first positions; however, they have a lower weight than the **Promoted** ones. Therefore, if you have one product being added and another promoted, the promoted one would display first and then the added one.
+
+* **Remove**: Deletes the selected conditions from the result, so it removes products that would be displayed in the search results.
+
+  <div class="alert alert-info">
+  <p><strong>Add</strong> and <strong>Remove</strong> are compatible with other sorting types, not based on the configured relevance. So, suppose you add or remove a product using a merchandising rule, and the customer sorts the search results by price. In that case, the products will be sorted by price, and the products displayed will follow the merchandising rule.</p>
+  </div>
+
+* **Promote**: Highlights selected conditions in the result, giving more relevance to a product normally displayed in the search results. The order of the conditions affects the priority in which they are displayed. Besides, a product added to this field is only promoted in one result.
+
+* **Demote**: Hides the selected conditions in the result. This allows you to deprioritize a product normally displayed in the search results.
+
+  <div class="alert alert-info">
+  <p><strong>Promote</strong> and <strong>Demote</strong> only work when your customers sort the search results by relevance. If they sort it by price, the products will be sorted strictly by price, and the merchandising rule will not be applied.</p>
+  </div>
+
+  <div class="alert alert-warning">
+  <p>Do not set conditions that will affect the same products in the <strong>Promote</strong> and <strong>Demote</strong> sections, since these are opposite effects. This misconfiguration negatively influences the feature's behavior and does not produce the desired results.</p>
+  </div>
diff --git a/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
index 4726b752c..cf613d67d 100644
--- a/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Creating merchandising rules - Visual Editor (Beta)'
 id: 6xteumx9MsDt0uEppbChu3
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-03T21:05:14.304Z
-updatedAt: 2023-04-11T22:34:40.303Z
-publishedAt: 2023-04-11T22:34:40.303Z
+updatedAt: 2024-01-29T17:17:03.584Z
+publishedAt: 
 firstPublishedAt: 2023-04-03T21:30:34.359Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,55 +19,74 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
   <p>This feature is in closed beta, which means that only selected customers can access it for now. If you are interested in implementing it for your business in the future, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a>.</p>
 </div>
 
-The Visual Editor (beta) for[ merchandising rules](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) in VTEX Intelligent Search allows you to:
+To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) using[ Visual Editor](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), follow the steps below.
 
-![visual-merch-rules-EN](https://images.ctfassets.net/alneenqid6w5/5Pah0D3Y9CfUyczqFR99bd/4d8ea287aaed825eb017a0c6325b6e05/visual-merch-rules-EN.png)
+1.	In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2.	Under **Intelligent Search**, click **Merchandising Rules**.
+3.	Click the `+ New` button.
+4.	Complete the following fields:
+
+	* **Rule name**: Merchandising rule name. Example: Promote product A when searching for a chocolate cookie.
+	* **Start date (optional)**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
+	* **End date (optional)**: Set a date when the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
+	* **Apply to locales:** Languages to which the merchandising rule will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5.	Click **Visual Editor**. Read the [Types of editing](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao) section for more information about each editor.
+6.	Click `Next`.
+7.	Define at least one search term or filter for applying the merchandising rule:
+
+	* To define a search term, type the term in the search bar (item **II** in the  [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section).
+	* To create a filter for applying the merchandising rule (item **III** in the  [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section), follow the steps described in the[ Adding filters and conditions](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes) section.
+8.	You can also perform the following additional actions to customize the search results.
+
+	* Define the number of items per row in the search results.
+	* Define the number of items per page in the search results.
+	* Hide products in the search results.
+	* Pin products to the top positions of the search results.
+	* Drag the pinned product to the desired position in the search results.
+	* Edit the initial settings of the merchandising rule, including the rule name, start and end dates, and the locales to which it will be applied if the store uses the[ Multilanguage settings (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+      Learn more about these actions in items **IV, V, VI, VIII, IX**, and **XI** of the [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section.
+9.	Click `Save`.
+
+<div class="alert alert-info">
+  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
+</div>
+
+## Actions available in the Visual Editor
+
+The Visual Editor for merchandising rules in VTEX Intelligent Search allows you to perform the actions shown in the image below:
+
+![visual-merch-rules-EN-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Edit the name of the merchandising rule.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Set search terms to apply the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define search terms to apply the merchandising rule.</li>
     <li class="t-body c-on-base mb5 lh-copy">Set <a href="#adding-filters-and-conditions" rel="noopener noreferrer"
             target="_self"
             class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filters</a>
-        to apply the
-        merchandising rule.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Specify the number of items per row.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Specify the number of items per page.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Navigate between search results pages.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Drag and drop products to the desired position in the search results.
-        You can only drag products that have been pinned (action IX).</li>
-    <li class="t-body c-on-base mb5 lh-copy">Hide products from the search results. This action cannot be undone,
-        so to make a product display in the results again, you need to create another merchandising rule.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Pin products to the top positions of the search results. By pinning
-        product A and then product B, they will appear in this order in the search results, just before the others.</li>
-    <li class="t-body c-on-base mb5 lh-copy">See product details.</li>
+        to apply the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define the number of items per row in the search results.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define the number of items per page in the search results.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Hide products in the search results. Hidden products appear in gray with the crossed-out eye icon <i class="far fa-eye-slash"></i> in the Visual Editor. To display a hidden product again, hover over it and click the eye icon <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">View product details. The information displayed is:<br /><br />
+    	 <ul>
+			   <li class="t-body c-on-base mb5 lh-copy"><strong>Available:</strong> Indicates whether the product is available in the store.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Clicks:</strong> Number of clicks over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Orders:</strong> Number of orders containing the product that were placed over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Revenue:</strong> Revenue the product represented over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Launch date:</strong> Date on which the product was launched.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Promotion:</strong> Indicates whether the product participates in a promotion.</li> 
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Discount:</strong> Discount applied to the product.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Available matrix variety:</strong> Represents the percentage of SKUs available for a product. For example, if a product has five SKUs and only three are available, the available matrix variety will be 60%, represented as 0.6 in this field. If all the SKUs are available, the field value will be 1.</li>
+		    </ul>
+	    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Drag the pinned product to the desired position in the search results. You can only drag pinned products (action <strong>IX</strong> in this list).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Pin products to the top positions of the search results. By pinning product A and then product B, they will appear in this order in the search results, just before the others. To pin a product, hover over it and click the pin-crossed icon <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navigate between search result pages.</li>
     <li class="t-body c-on-base mb5 lh-copy">Cancel editing.</li>
     <li class="t-body c-on-base mb5 lh-copy">Save settings.</li>
 </ol>
 
-## Setting up a merchandising rule
-
-To configure a merchandising rule in the Visual Editor, follow the steps below.
-
-1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
-2. Under **Intelligent Search**, click **Merchandising Rules**.
-3. Click the `+ New` button.
-4. Fill in the following fields:
-   * **Name**: Name of the merchandising rule. Example: Promote product A when searching for a chocolate cookie.
-   * **Start date (optional)**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
-   * **End date (optional)**: Set a date on which the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
-   * **Locales:** Languages to which the merchandising rule will apply.
-5. Click **Visual Editor**. See [Types of editing](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#types-of-editing) for more information about each editor.
-6. Click `Next`.
-7. To define a search term that determines when the merchandising rule applies, enter the term in the search bar (item II in the previous image). You need to define at least one term or a filter (step 8) to apply the rule.
-8. To create a filter to apply the merchandising rule (item III in the previous image), follow the steps described in the [Adding filters and conditions](#adding-filters-and-conditions) section. You need to define at least one filter or term (step 7) for the rule to apply.
-9. You can also perform additional actions to customize the search results (items IV, V, VII, VIII, IX in the previous image).
-10. Click `Save`.
-
-<div class="alert alert-info">
-  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
-</div>
-
 ### Adding filters and conditions
 
 Filters are predefined selectable attributes that narrow the search results, such as filtering for all products in a category or brand, among other conditions. You can add one or more conditions to a filter.
diff --git a/docs/tutorials/en/creating-merchandising-rules-visual-editor.md b/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
new file mode 100644
index 000000000..1380e6d30
--- /dev/null
+++ b/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
@@ -0,0 +1,99 @@
+---
+title: 'Creating merchandising rules - Visual Editor'
+id: 3gPO5CMJ3Off0OtA3EPzow
+status: PUBLISHED
+createdAt: 2024-06-27T17:16:02.371Z
+updatedAt: 2024-06-27T17:16:43.289Z
+publishedAt: 2024-06-27T17:16:43.289Z
+firstPublishedAt: 2024-06-27T17:16:43.289Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: creating-merchandising-rules-visual-editor
+locale: en
+legacySlug: creating-merchandising-rules-visual-editor
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) using [Visual Editor](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), follow the steps below.
+
+1.	In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2.	Under **Intelligent Search**, click **Merchandising Rules**.
+3.	Click the `+ New` button.
+4.	Complete the following fields:
+
+	* **Rule name**: Merchandising rule name. Example: Promote product A when searching for a chocolate cookie.
+	* **Start date (optional)**: Set a date from which the merchandising rule will apply. The date follows the UTC-0 time zone.
+	* **End date (optional)**: Set a date when the merchandising rule will no longer apply to store searches. The date follows the UTC-0 time zone.
+	* **Apply to locales:** Languages to which the merchandising rule will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5.	Click **Visual Editor**. Read the [Types of editing](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao) section for more information about each editor.
+6.	Click `Next`.
+7.	Define at least one search term or filter for applying the merchandising rule:
+
+	* To define a search term, type the term in the search bar (item **II** in the  [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section).
+	* To create a filter for applying the merchandising rule (item **III** in the  [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section), follow the steps described in the[ Adding filters and conditions](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes) section.
+8.	You can also perform the following additional actions to customize the search results.
+
+	* Define the number of items per row in the search results.
+	* Define the number of items per page in the search results.
+	* Hide products in the search results.
+	* Pin products to the top positions of the search results.
+	* Drag the pinned product to the desired position in the search results.
+	* Edit the initial settings of the merchandising rule, including the rule name, start and end dates, and the locales to which it will be applied if the store uses the[ Multilanguage settings (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+      Learn more about these actions in items **IV, V, VI, VIII, IX**, and **XI** of the [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section.
+9.	Click `Save`.
+
+<div class="alert alert-info">
+  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
+</div>
+
+## Actions available in the Visual Editor
+
+The Visual Editor for merchandising rules in VTEX Intelligent Search allows you to perform the actions shown in the image below:
+
+![visual-merch-rules-EN-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Edit the name of the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define search terms to apply the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Set <a href="#adding-filters-and-conditions" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filters</a>
+        to apply the merchandising rule.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define the number of items per row in the search results.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Define the number of items per page in the search results.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Hide products in the search results. Hidden products appear in gray with the crossed-out eye icon <i class="far fa-eye-slash"></i> in the Visual Editor. To display a hidden product again, hover over it and click the eye icon <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">View product details. The information displayed is:<br /><br />
+    	 <ul>
+			   <li class="t-body c-on-base mb5 lh-copy"><strong>Available:</strong> Indicates whether the product is available in the store.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Clicks:</strong> Number of clicks over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Orders:</strong> Number of orders containing the product that were placed over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Revenue:</strong> Revenue the product represented over the last 90 days.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Launch date:</strong> Date on which the product was launched.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Promotion:</strong> Indicates whether the product participates in a promotion.</li> 
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Discount:</strong> Discount applied to the product.</li>
+				<li class="t-body c-on-base mb5 lh-copy"><strong>Available matrix variety:</strong> Represents the percentage of SKUs available for a product. For example, if a product has five SKUs and only three are available, the available matrix variety will be 60%, represented as 0.6 in this field. If all the SKUs are available, the field value will be 1.</li>
+		    </ul>
+	    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Drag the pinned product to the desired position in the search results. You can only drag pinned products (action <strong>IX</strong> in this list).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Pin products to the top positions of the search results. By pinning product A and then product B, they will appear in this order in the search results, just before the others. To pin a product, hover over it and click the pin-crossed icon <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navigate between search result pages.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Cancel editing.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Save settings.</li>
+</ol>
+
+### Adding filters and conditions
+
+Filters are predefined selectable attributes that narrow the search results, such as filtering for all products in a category or brand, among other conditions. You can add one or more conditions to a filter.
+
+To add a condition using the Visual Editor, follow the steps below.
+
+1. Click `Filter`.
+2. Click `+ Add condition`.
+3. Fill in the desired conditions. The available options are detailed in [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+4. Click `Save`.
+
+The defined conditions can work together (`and`) or alternatively (`or`).
+
+In the <i class="far fa-ellipsis-v"></i> menu of each existing condition, you can `Duplicate` or `Delete` the condition. To deactivate all created conditions, click `Clear filters`.
diff --git a/docs/tutorials/en/creating-price-tables.md b/docs/tutorials/en/creating-price-tables.md
index 0ab0c904d..d08ff4225 100644
--- a/docs/tutorials/en/creating-price-tables.md
+++ b/docs/tutorials/en/creating-price-tables.md
@@ -1,10 +1,10 @@
 ---
 title: 'Creating Price Tables'
 id: 58YmY2Iwggyw4WeSCGg24S
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-12-02T21:35:14.220Z
-updatedAt: 2020-11-27T19:39:45.134Z
-publishedAt: 2019-12-31T15:26:59.677Z
+updatedAt: 2023-11-30T16:46:22.924Z
+publishedAt: 2023-11-30T16:46:22.924Z
 firstPublishedAt: 2018-12-02T21:36:28.350Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,13 +17,13 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 To create a new Price Table, follow the steps below:
 
-1. Click on **Prices**
-2. Click on **Price list**
-3. Click on **Price Table**
-4. Select **Create new Price Table**
-5. Choose the name of the Price Table that you wish to create and clique on the bluw button **Create Price Table**
+1. In the VTEX Admin, go to **Catalog > Prices > Prices List >**, or type **Price List** in the search bar at the top of the page.
+2. Click on button **Price list**.
+3. Select the **Create new price table**.
+4. Choose the name of the pricing table you want to create.
+5. Click on button **Create price table**.
 
-![TutorialPriceTableEN 2806](https://images.ctfassets.net/alneenqid6w5/2PC1RQzMYmgjAbu5P1wqu6/5f020fb39ec193cd90b20756a7460294/TutorialPriceTableEN_2806.gif)
+![creating-price-tables](//images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/5fabe5c47940372d29b45d2718c34b68/criar-tabela-precos-en.gif)
 
 To find a Price Table: 
 
diff --git a/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
index 1690ae7f6..1250d1ae6 100644
--- a/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
@@ -54,9 +54,9 @@ In the configuration below, for example, only `employee` entries with the value
 
 You could also configure `employee=false`, where only `employee` entries with the value `false` in the field would receive the promotion.
 
-![Campo funcionário Master Data EN](https://images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/929dce6e74118345a2c9f17a9605e572/Campo_funcion__rio_Master_Data_EN.png)
+![Campo funcionário Master Data EN](//images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/929dce6e74118345a2c9f17a9605e572/Campo_funcion__rio_Master_Data_EN.png)
 
-![Cluster de clientes EN](https://images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/653b3bf0087c0b78268a1231ebfcbf5f/Cluster_de_clientes_EN.png)
+![Cluster de clientes EN](//images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/653b3bf0087c0b78268a1231ebfcbf5f/Cluster_de_clientes_EN.png)
 
 Given a field of type **[Varchar](https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265)**, we could configure `employee="yes"` so that only customers with the value `"yes"` in the field receive the promotion.
 
@@ -72,8 +72,8 @@ The expression `{propertyname} contains {value}` must be used when the informati
 
 For example, if you want to create a cluster with only customers whose emails contain `@test.com`, the configuration will follow the example below.
 
-![Campo Email Master Data](https://images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4d8feac02a228d44de71cb2fa28e954f/Campo_Email_Master_Data.png)
+![Campo Email Master Data](//images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4d8feac02a228d44de71cb2fa28e954f/Campo_Email_Master_Data.png)
 
-![cluster email EN](https://images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/85c04dff4d5ebf184cd9bd1f82f1bdfb/cluster_email.png)
+![cluster email EN](//images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/85c04dff4d5ebf184cd9bd1f82f1bdfb/cluster_email.png)
 
 In this case, `email contains test.com` will be `true`, for example, when the value is `john@test.com`, and `false` when the value is `john@test.org`.
diff --git a/docs/tutorials/en/creating-promotions.md b/docs/tutorials/en/creating-promotions.md
index 654197d75..7e218651f 100644
--- a/docs/tutorials/en/creating-promotions.md
+++ b/docs/tutorials/en/creating-promotions.md
@@ -86,7 +86,7 @@ A promotion is scheduled when it is created (or modified) with a valid date and
 
 These promotions can be easily identified on the main Promotions page: they have an orange stripe with the word scheduled in the upper right corner of the card, as shown below.
 
-![scheduleded](https://images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/eb514999e99bff1bb64c9b21ca93fd9c/scheduled.png)
+![scheduleded](//images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/eb514999e99bff1bb64c9b21ca93fd9c/scheduled.png)
 
 To schedule a promotion, follow the steps described in the [Scheduling promotions](https://help.vtex.com/en/tutorial/scheduling-features-for-special-events--2nd50tPWdKK4waXRZLg0JI#scheduling-promotions) section of the article [Scheduling features for special events](https://help.vtex.com/en/tutorial/scheduling-features-for-special-events--2nd50tPWdKK4waXRZLg0JI).
 
diff --git a/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md
index 83c6b1e44..2109b210c 100644
--- a/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md
@@ -1,9 +1,9 @@
 ---
 title: 'Creating relationships between Master Data entities using Admin'
 id: 1qzbCit8SYXbKwrT5x2FfA
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-08-11T13:48:26.272Z
-updatedAt: 2022-10-17T19:11:39.513Z
+updatedAt: 2024-06-06T19:36:29.525Z
 publishedAt: 2022-10-17T19:11:39.513Z
 firstPublishedAt: 2020-08-18T19:47:29.772Z
 contentType: tutorial
@@ -33,23 +33,23 @@ In the example below, there is an entity called `Lista de compras` (Shopping lis
 
 1. In the Master Data, click on the **Aplicações** (Applications) tab.
 2. Then click on the **Advanced settings** button.  
-![Configurações Avançadas](https://images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
+![Configurações Avançadas](//images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
 3. Select the option **Estrutura de dados** (Data structure). You will be redirected to the Dynamic Storage (DS).  
-![Estrutura de dados](https://images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
+![Estrutura de dados](//images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
 4. In the Dynamic Storage, click on the **Data Entities** tab.
 5. If you want to create a relationship in a new entity, click on **Add new** to create a new data entity. _If you want to create a relationship in an existing entity, locate it and click on the **Edit** button next to it. Go to step 7_.  
-![Adicionar nova entidade de dados](https://images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
-![Editar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
+![Adicionar nova entidade de dados](//images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
+![Editar entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
 6. Configure the new entity by filling in the fields **Acronym** and **Name**, and add the fields of your choice. In this example, the entity will receive the name `Lista de compras`, the acronym `LC` and the `compras` field of `Varchar 750` type.
 7. Add a `Relationship` type field and name it. In this example, it will be called `Cliente`.
 8. Then click on the button **Edit** (gear icon) to configure it in the relationship field. 
 9. In **Custom field type settings**, select the entity you want to refer to and the field that will be displayed in the relationship. In this example, the relationship will be established with the “Cliente” entity and shown in the “email” field.  
-![Relacionamento entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
+![Relacionamento entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
 10. Click on the **Save** button.
-![Salvar entidade de dados](https://images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
+![Salvar entidade de dados](//images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
 11. Go back to the entity list. Remember that you must publish the entity with the relationship by clicking on the **Publish** button (floppy disk icon). You may also need to update the applications for the changes to be implemented. For that, go to **Aplicações** (Applications) and click on the **Reload applications** button.  
-![Publicar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
-![Master Data Reload applications](https://images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
+![Publicar entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
+![Master Data Reload applications](//images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
 
 ## How to create a relationship between documents?
 
@@ -58,44 +58,44 @@ You can also apply relationships to specific documents of the data entity. The `
 1. To relate the documents, add the relationship field to the form of the entity that contains the reference. You can set the field as a combo box to show all the available values. For more details, read our article [Creating a field in Master Data](https://help.vtex.com/en/tutorial/how-can-i-create-a-field-in-master-data--frequentlyAskedQuestions_1829#crm).
 
 2. Select a value (in this case, the client to be related to this shopping list).
-![Selecionar relacionamento de documento Master Data](https://images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
+![Selecionar relacionamento de documento Master Data](//images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
 3. Click on **Salvar** (Save).
 
 After adding the field to the table, check out the values that were defined. 
-![Tabela de relacionamento de documentos Master Data](https://images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/5658949f4c0a72a5ed7bdd9af7819896/Tabela_de_relacionamento_de_documentos_Master_Data.png)
+![Tabela de relacionamento de documentos Master Data](//images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/5658949f4c0a72a5ed7bdd9af7819896/Tabela_de_relacionamento_de_documentos_Master_Data.png)
 
 ## How to add filters to relationship fields?
 
 Relationships are stored in the system as document IDs. So, suppose you enter the value of the relationship field as a filter in the form. In that case, the result will return only the ID values of the referred documents—instead of the values of the field selected for each document. You can see this result in the pictures below. For more information, read our article on [How to filter data in Master Data](https://help.vtex.com/en/tutorial/filtering-data-on-master-data--tutorials_778).
 
-![Selecionar filtro relacionamento](https://images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
+![Selecionar filtro relacionamento](//images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
 
-![Filtro relacionamento ID](https://images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
+![Filtro relacionamento ID](//images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
 
 If you want to see the field values instead of their IDs, you can filter using an automatic field. See the instructions below:
 
 1. In the Master Data, go to **Aplicações** (Applications) > **Advanced settings** > **Estrutura de dados** (Data structure) to access the Dynamic Storage.
 2. Access **Data Entities**.
 3. Click on the **Edit** button next to the entity that contains the relationship (in this case, `Lista de Compras`). 
-![Editar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/01edd05338b039279672d9cfc4a49164/Editar_entidade_Lista_de_Compras.png)
+![Editar entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/01edd05338b039279672d9cfc4a49164/Editar_entidade_Lista_de_Compras.png)
 4. Select the **Automatic fields** tab.
 5. Click on **New field**.    
-![Relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
+![Relacionamento automatic fields](//images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
 6.  Fill in the **Name**, **Display Name**, and **Type** fields. In this example, they are `emailCliente`, `E-mail cliente`, and Varchar 50.
 7. Select the gear icon to adjust additional settings.   
-![Name automatic field](https://images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/9aed2f322c02ab0c3991f1d28c199676/Nome_automatic_field.png)
+![Name automatic field](//images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/9aed2f322c02ab0c3991f1d28c199676/Nome_automatic_field.png)
 8. Enter additional settings to the formula, and select the field value, as in the picture below. 
-![Configurar relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/8605aa25dbc22ba6d28674472fc80232/Configurar_relacionamento_automatic_fields.png)
+![Configurar relacionamento automatic fields](//images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/8605aa25dbc22ba6d28674472fc80232/Configurar_relacionamento_automatic_fields.png)
 9. Click on **Validate**.
 10. A new window will open and you’ll be asked to add an email address. Enter a generic email address and click **Ok**.   
-![Validar automatic field](https://images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
+![Validar automatic field](//images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
 11. Subsequently, a warning will be displayed indicating that the formula is valid, as in the image below. Then click **Ok**. 
-![Fórmula válida automatic field](https://images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
+![Fórmula válida automatic field](//images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
 12. Click on **Save**.
 
 After following the steps above, the filter will be applied to the relationship. In the entity form (`Lista de Compras`), add the new field to the filter after updating the records.
-![Selecionar filtro relacionamento valor](https://images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/731c3fa19a7a8c3d9cf91a3733d86c7c/Selecionar_filtro_relacionamento_valor.png)
+![Selecionar filtro relacionamento valor](//images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/731c3fa19a7a8c3d9cf91a3733d86c7c/Selecionar_filtro_relacionamento_valor.png)
 
 Now the filters are named with values instead of their IDs.
-![Filtro relacionamento valor](https://images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/5c63307856159af60995094fa6e99f42/Filtro_relacionamento_valor.png)
+![Filtro relacionamento valor](//images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/5c63307856159af60995094fa6e99f42/Filtro_relacionamento_valor.png)
 
diff --git a/docs/tutorials/en/creating-roles.md b/docs/tutorials/en/creating-roles.md
new file mode 100644
index 000000000..c133e40f9
--- /dev/null
+++ b/docs/tutorials/en/creating-roles.md
@@ -0,0 +1,95 @@
+---
+title: 'Creating roles'
+id: qGtNQpKSSAduX94l2WZBW
+status: DRAFT
+createdAt: 2023-11-30T16:42:01.373Z
+updatedAt: 2023-11-30T21:59:23.416Z
+publishedAt: 
+firstPublishedAt: 2023-11-30T17:12:45.125Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: creating-roles
+locale: en
+legacySlug: creating-roles
+subcategory: 1HSqkejwuYcQSMC400uY84
+---
+
+A role determines the set of resources that a group of users can access on VTEX. You can manage roles via the VTEX Admin, where you can define the[ resources](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) and users associated with each role.
+
+When creating a role, you can either use a [predefined role](https://help.vtex.com/en/tutorial/access-control--4rM3gyiWqtkim4Q8hOvLTC#predefined) created by the VTEX team to meet common operational scenarios or create a [custom role](https://help.vtex.com/en/tutorial/access-control--4rM3gyiWqtkim4Q8hOvLTC#custom), selecting specific resources that users with this role need access to.
+
+Check the steps for each of these options below:
+
+* [Using predefined roles](#using-predefined-roles)
+* [Creating custom roles](#creating-custom-roles)
+
+We recommend creating roles that are analogous to the store's hierarchical structures. This approach ensures that all employees are accountable for the information they have access to. Best practices for managing roles not only increase operational security but also heighten the awareness of those handling sensitive store data and customer information.
+
+<div class="alert alert-warning">
+  <p>Unrestricted use of overly permissive roles increases the risk of store attacks through leaked login credentials.</p>
+</div>
+
+## Using predefined roles
+
+To start using a predefined role, follow the instructions below:
+
+1. In the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **User roles**.
+
+    You will see a list of all the roles added to the account. For more information on this page, read the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) article.
+2. Click `+ Create Role`.
+3. Click the `Choose role` field and select one of the predefined roles displayed in the dropdown menu. Do not choose the **Custom** option, as it is dedicated to custom roles.
+
+    You will see which resources are included in this role, sorted by product.
+
+    For example, the **Call center operator** profile has a _Catalog_ product resource that allows operations to be carried out in a store on behalf of a customer and an _OMS_ resource that allows verifying an order status:
+
+    ![New role saved](//images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/a4452a13454d847c991800db970f0a7e/New_role_saved.png)
+
+    Learn more about the available predefined roles and their associated resources in [Predefined roles](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy).
+4. Add admin users to the role by entering the user email address in **Add users to this role** and click `Add`.
+
+    ![Role users](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
+
+    If the user does not exist, a new user will be created using the email as the name, i.e., the name and email will be the same.
+5. Click `Save`.
+
+## Creating custom roles
+
+To create a custom role that meets the access needs of a group of users, follow the instructions below:
+
+1. In the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **User roles**.
+
+    You will see a list of all the roles added to the account. For more information on this page, read the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) article.
+2. Click `+ Create Role`.
+3. To create a custom role, click the `Choose role` field and select the **Custom** option from the dropdown menu.
+4. Click the dropdown menu under **Choose a product** and select a product from the list.
+
+    You will see a list of all the resources available for the product:
+
+    ![Configuring product](//images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/956aa2dfc15f9e2adedd6efc90af039f/configurar-produto-en.png)
+
+5. Check the resources to which the role should grant access. Check the complete [License Manager resources](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) list for more information on each one.
+6. If you want to add resources from another product, click the **Configure Another Product** button at the bottom of the product and resource list and repeat steps 4 and 5.
+
+    You can add resources from as many products as you need to the role.
+7. Type a name for the custom role in the **Role name** field.
+
+  <div class="alert alert-warning">
+    <p>Choose descriptive names for the roles, clearly indicating the type of user who should have access. We recommend indicating the position in the company or the activity to be carried out on the platform.</p>
+  </div>
+8. Add admin users to the role by entering the user email address in **Add users to this role** and then click `Add`.
+
+    ![Role users](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
+
+    If the user does not exist, a new user will be created using the email as the name, i.e., the name and email will be the same.
+
+9. Click `Save`.
+
+    Once created, the new role will be listed on the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) page.
+
+## Learn more
+
+* [Access control](https://help.vtex.com/en/tutorial/access-control--4rM3gyiWqtkim4Q8hOvLTC)
+* [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [License Manager resources](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3)
diff --git a/docs/tutorials/en/creating-service-for-a-sku.md b/docs/tutorials/en/creating-service-for-a-sku.md
index 4d97734c7..306854a9c 100644
--- a/docs/tutorials/en/creating-service-for-a-sku.md
+++ b/docs/tutorials/en/creating-service-for-a-sku.md
@@ -3,8 +3,8 @@ title: 'Creating service for a SKU'
 id: tutorials_252
 status: PUBLISHED
 createdAt: 2017-04-27T22:12:00.282Z
-updatedAt: 2023-05-04T13:15:14.224Z
-publishedAt: 2023-05-04T13:15:14.224Z
+updatedAt: 2024-03-04T22:36:04.117Z
+publishedAt: 2024-03-04T22:36:04.117Z
 firstPublishedAt: 2017-04-27T23:03:11.914Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -40,17 +40,10 @@ To register a service type, please follow the steps below:
 In this section you must enter a name for your service type and configure its behavior according to the options below.
 
 - **Name:** name of the service type.
-- **Displays on product:** option to display the service type on the product page.
-- **Displays in cart:** option to display the service type in the cart.
-- **Displays on service:** option to display the service type on the service page.
 - **Gift card:** option to display the service type on the gift card.
 - **Mandatory service:** option to make the service type mandatory.
 - **Status** option to enable or disable the service type.
-- **Attachments:** selected attachments that will be added to the service type. The attachment is used to add customized information to the service. To learn more, read our article What is an Attachment?.
-
-<div class = "alert alert-warning">
-  <p>To display the service on the product page, you must enable the option <b>Displays on product</b> and add the control <code><vtex.cmc:stockKeepingUnitService/></code> to the product page in the CMS. For more information, read our article <a href ="https://help.vtex.com/en/tutorial/what-are-controls--6e2qsk9zu8IQuyEysKweag" >What are controls?</a>.</p> 
-</div>
+- **Attachments:** selected attachments that will be added to the service type. The attachment is used to add customized information to the service. To learn more, read our article [What is an Attachment?](https://help.vtex.com/en/tutorial/what-is-an-attachment--aGICk0RVbqKg6GYmQcWUm).
 
 ## Creating a service value and associating it with a service type
 After registering the service type, you must assign a value to it. To register the value of a service type, please follow the steps below:
@@ -86,7 +79,7 @@ To link a service to a SKU, please follow the steps below:
   <p>The size of the template file cannot exceed 4Mb (4096KB).</p>
 </div>
 8. Click on the bar next to the `Select` button, as shown below.
-  ![Anexos - EN](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/6d834bfa0595150d8c6a5b69c6088e23/sku-services.png)
+  ![Anexos - EN](//images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/6d834bfa0595150d8c6a5b69c6088e23/sku-services.png)
 9. Select the updated CSV template.
 10. Click on the button `Link service values to SKU`.
 
diff --git a/docs/tutorials/en/creating-subaccount-multi-store-multi-domain.md b/docs/tutorials/en/creating-subaccount-multi-store-multi-domain.md
new file mode 100644
index 000000000..c82c729bc
--- /dev/null
+++ b/docs/tutorials/en/creating-subaccount-multi-store-multi-domain.md
@@ -0,0 +1,65 @@
+---
+title: 'How to create a subaccount / multistore / multidomain'
+id: tutorials_510
+status: PUBLISHED
+createdAt: 2017-04-27T22:03:17.733Z
+updatedAt: 2024-01-18T17:56:47.931Z
+publishedAt: 2024-01-18T17:56:47.931Z
+firstPublishedAt: 2017-04-27T23:03:27.832Z
+contentType: tutorial
+productTeam: Others
+author: authors_84
+slug: creating-subaccount-multi-store-multi-domain
+locale: en
+legacySlug: creating-multi-store-multi-domain
+subcategory: yMp6sKDiJEi66CGAIQ4ma
+---
+
+A subaccount, multistore or multidomain is a second store administered within the same VTEX administrative panel. This feature is usually used when the store has other brands but there's a similarity of logistics and payment methods or when the store needs another environment, for example for B2B sales.
+
+The creation of a multistore is free of charge for merchants. However, if you need to [request an additional commercial policy](https://help.vtex.com/en/tutorial/requesting-an-additional-trade-policy--61vuFOw4yGh6nwSmkLJL1X), additional costs will apply.
+
+In a multidomain environment it's possible to define distinct layouts (in addition to products and/or prices) for each store, varying according to the domain. Example: `accountname.com` and `b2baccountname.com`.
+
+## Creating a new store in the Account management
+
+The first step in setting up multistore is to configure a new store on the account details page. Learn how to do this with the [Account Management](https://help.vtex.com/en/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq) guide.
+
+Note that you also need to specify the domain of your new store. Learn more with the [Configuring your store's domain](https://help.vtex.com/tutorial/configuring-domains-in-account-management--tutorials_2450) guide.
+
+## Setting up a new website in Legacy CMS Portal
+
+The configuration in the Legacy CMS Portal will actually create the environment that can be accessed by the clients. The walkthrough below demonstrates how to create a website by copying the folder structure of your main website to make it easier to create your layout. However, this setting can also be done by creating a new website.
+
+1. Access the **Storefront > Layout** module.
+2. Click **CMS**.
+3. Click **Sites and channels**.
+4. Click on your main website.
+5. Click the `Copy Website` button.
+6. Click **Sites and channels** again in the side column.
+7. Click on the created website.
+8. Change its name.
+9. Click the `Save Website` button.
+10. On the same screen, click the `Add` button.
+11. Fill in the **Store name from License Manager** with the store value created in the previous step in the __Account management__.
+12. Fill in **Available sales policies** by selecting the sales policies you will associate with this store.
+13. Click the `Save Binding` button.
+14. Click the `Save Website` button.
+
+Pay attention to the ordering of your sales policies. They should always be ordered according to their use on websites, i.e. first the commercial policies that are used by websites (main website, b2b, etc.) and then the sales policies that are not associated with any website (marketplace sales policies, for example). 
+
+This is because if there's a sales policy that is not associated with any website, it's available to all of them. And should it come before the sales policy associated with the website, this website will be assigned to the wrong sales policy.
+
+To learn more about the relationship between websites and sales policies, check the article [How the relationship between websites and sales policies works](https://help.vtex.com/en/tutorial/how-the-relationship-between-websites-and-business-policies-works--1VuakBcyNOgg4AM4cUeeQg).
+
+### Editing the dictionary
+
+You can also define specific variables for each website using the dictionary. To do so, within the website, click **dictionary**.
+
+## Deleting a subaccount / multistore / multidomain
+
+To delete an existing multistore, follow the steps described in the [Deleting a store section of the Account management guide](https://help.vtex.com/en/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq#deleting-a-store). The name of the removed subaccount cannot be used again.
+
+## Learn more
+
+- [Choosing between a multi-store architecture or an additional environment](https://help.vtex.com/en/tutorial/choosing-between-a-multi-store-architecture-or-an-additional-environment--4HRNpa1OCKZ5YzP8yiilBL)
diff --git a/docs/tutorials/en/creating-surchargestaxes.md b/docs/tutorials/en/creating-surchargestaxes.md
index f22cdc86a..ada9e8ad5 100644
--- a/docs/tutorials/en/creating-surchargestaxes.md
+++ b/docs/tutorials/en/creating-surchargestaxes.md
@@ -3,8 +3,8 @@ title: 'How to create surcharges/taxes'
 id: tutorials_321
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:49.745Z
-updatedAt: 2023-03-31T16:53:05.461Z
-publishedAt: 2023-03-31T16:53:05.461Z
+updatedAt: 2023-10-26T13:20:22.531Z
+publishedAt: 2023-10-26T13:20:22.531Z
 firstPublishedAt: 2017-04-27T23:03:14.603Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -30,31 +30,32 @@ The surcharge is applied in accordance with the registration done on the seller.
 
 ### What is the general information of this tax?
 
-- **Name**: Name of the surcharge.
-- **Status**: Activates or deactivates the surcharge.
-- **Description**: Internal description of the surcharge This field is intended for communication within your store, to make it clear whether the surcharge is based on some special rule, for example.
-- **Expiration Date**: Date and time of the start and finish of the surcharge. Future dates and times can be used to schedule the application of the surcharge on the site. If it is configured in this manner, the surcharge will be shown as scheduled, until the date and time indicated are reached. While the surcharge is in effect, it will have active status and, when the defined date and time run out, the status will automatically change to inactive.
+- **Name**: name of the surcharge.
+- **Status**: activates or deactivates the surcharge.
+- **Description**: internal description of the surcharge This field is intended for communication within your store, to make it clear whether the surcharge is based on some special rule, for example.
+- **Expiration Date**: date and time of the start and finish of the surcharge. Future dates and times can be used to schedule the application of the surcharge on the site. If it is configured in this manner, the surcharge will be shown as scheduled, until the date and time indicated are reached. While the surcharge is in effect, it will have active status and, when the defined date and time run out, the status will automatically change to inactive.
 - **What kind and amount of Tax?**:
-  - **Percentage Tax**: A percentage of the value of the product to be added to the amount.
-  - **Formula-based Tax Value**: The surcharge will apply the calculation entered in the field.
-  - **Shipping percentual tax**: Percentage increase over freight value.
-- **Sales Policy**: Select the sales policies to which the surcharge will apply.
+  - **Percentage Tax**: a percentage of the value of the product to be added to the amount.
+  - **Formula-based Tax Value**: the surcharge will apply the calculation entered in the field.
+  - **Shipping percentual tax**: percentage increase over freight value.
+  - **Nominal tax**: additional tax with a predefined value.
+- **Sales Policy**: select the sales policies to which the surcharge will apply.
 
 ### To what items will this tax apply?
 
-- **Categories, Brands, Collections and Products:** It must meet all the conditions registered. E.g.: if a category and a brand are registered, the product must meet both conditions.
+- **Categories, Brands, Collections and Products:** it must meet all the conditions registered. E.g.: if a category and a brand are registered, the product must meet both conditions.
 
 ### What are the conditions for the tax to be valid?
 
-- **Aggregate value of purchases**: The surcharge will be applied if the total of all purchases previously made by the customer meets this minimum.
-- **Marketing Tags**: Field used to restrict the activation of the campaign if the purchase is made by the VTEX Recurrence System.
-- **Affiliates**: Marketplace order identifier
-- **Customer cluster**: The surcharge will be applied if the customer is registered in the selected cluster.
-- **Shipping to postal code should**: The surcharge will be applied where the postal code meets the rule configured.
-- **Shipping Method**: The surcharge will be applied if the type of shipping is as registered.
+- **Aggregate value of purchases**: the surcharge will be applied if the total of all purchases previously made by the customer meets this minimum.
+- **Marketing Tags**: field used to restrict the activation of the campaign if the purchase is made by the VTEX recurrence system.
+- **Affiliates**: marketplace order identifier
+- **Customer cluster**: the surcharge will be applied if the customer is registered in the selected cluster.
+- **Shipping to postal code should**: the surcharge will be applied where the postal code meets the rule configured.
+- **Shipping Method**: the surcharge will be applied if the type of shipping is as registered.
 
 ## Scheduling
 
 Scheduling of a surcharge occurs when it is created with an expiration date and time, beginning after the current one. Visually, it is possible to identify these surcharges on the home page of the Promotions & Taxes module by an orange strip in the upper right-hand corner of the surcharge card with the word ‘scheduled’. See below an example of how the surcharge card looks when scheduled.
 
-![agendamento.en](https://images.ctfassets.net/alneenqid6w5/6XrW3s1vW86EPSvcMufVcg/3b64aad76af6a36adc278405163fc7aa/agendamento.en.png)
+![agendamento.en](//images.ctfassets.net/alneenqid6w5/6XrW3s1vW86EPSvcMufVcg/3b64aad76af6a36adc278405163fc7aa/agendamento.en.png)
diff --git a/docs/tutorials/en/creating-synonyms.md b/docs/tutorials/en/creating-synonyms.md
new file mode 100644
index 000000000..204c01fd8
--- /dev/null
+++ b/docs/tutorials/en/creating-synonyms.md
@@ -0,0 +1,96 @@
+---
+title: 'Creating synonyms'
+id: 5IfjhvjxNAvJGEWNn0AhOA
+status: PUBLISHED
+createdAt: 2024-06-27T16:36:30.904Z
+updatedAt: 2024-06-27T16:39:00.981Z
+publishedAt: 2024-06-27T16:39:00.981Z
+firstPublishedAt: 2024-06-27T16:37:25.800Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: creating-synonyms
+locale: en
+legacySlug: configuring-synonyms
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+<div class = "alert alert-info"> We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Synonyms</a> instead of <a href="https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Substitute Words</a> to associate words with products, as synonyms allow you to manage terms per product in a more scalable way. Contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a> for more information.</div>
+
+There are two ways to set up synonyms in VTEX Admin: [individually](#creating-synonyms-individually) or by [importing a spreadsheet in CSV format](#importing-csv-spreadsheet). If you need to register synonyms in bulk, we recommend using the spreadsheet. See the instructions for each configuration form in the following sections.
+
+The configuration of synonyms works recursively. This means that when you add a second synonym to an existing one, it will also become a synonym for the first one.
+
+<div class="alert alert-info" role="alert">
+<p>Synonyms should not be used to resolve misspellings, plural and singular errors, or even pronouns, articles, and propositions in the search terms. On all these points, VTEX Intelligent Search is able to interpret, learn and solve them automatically through algorithms.</p>
+</div>
+
+## Creating synonyms individually
+
+Follow the step-by-step procedure to configure synonyms individually in the VTEX Admin:
+
+1. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
+2. Under **Intelligent Search**, click **Synonyms**. 
+3. Click on `Create Synonym`.
+4. Fill in the fields that correspond to the synonym:
+   - __Type:__ defines the type of synonym. Check [Types of synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#types-of-synonyms) for more information.
+   - __Terms:__ words or expressions to be defined as synonyms. You must press `Enter` after each term to insert another term.
+   - **Locales:** Languages to which the synonym will apply. The field is only available for stores using [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+   - __Status:__ defines whether the synonym will be active or inactive.
+5. To finish, click on `Save`.
+
+Changes can take up to two hours to take effect.
+
+<div class="alert alert-info">
+<p> This feature is available on VTEX Intelligent Search Multilanguage. Read our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#synonyms">VTEX Intelligent Search: Multilanguage settings (Beta)</a>to learn more.</p>
+</div>
+
+## Importing CSV spreadsheet
+
+In case there are many synonyms to be added, you can make a .csv file and import it in the Admin.
+
+To import the file, follow the steps below:
+
+1. Create a CSV file in the format described on [Synonyms spreadsheet template](#synonyms-spreadsheet-template).
+2. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
+3. Under **Intelligent Search**, click **Synonyms**. 
+4. Click on <i class="fas fa-download"></i> `Import`.
+5. Drag the CSV file into the bounded area or click on `choose a file` to select the file on your device.
+6. Click on `Import`.
+
+### Synonyms spreadsheet template
+
+The file must contain the following format, according to the [types of synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#types-of-synonyms) chosen:
+
+ - __Unidirectional:__ `{terms separated by comma};{equivalent term};{status}`
+
+   __Examples:__
+
+    - `smartphone;iphone;true`: When searching for `smartphone`, `iphone` results will be returned. However, when searching for `iphone`, `smartphone` results will not be returned.
+    - `tablet;ipad;true`: When searching for `tablet`, `ipad` results will be returned. However, when searching for `ipad`, `tablet` results will not be returned.
+
+ - __Bidirectional:__ `{terms separated by comma};{status}`
+
+   __Examples:__
+
+    - `tv,television,television set;true`: When searching for any of these terms, the products containing any of them will be returned.
+    - `monitor,screen,display;true`: When searching for any of these terms, the products containing any of them will be returned.
+
+#### Multilanguage stores (Beta)
+
+Stores using  [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO) must follow the template below to import synonyms for specific locales.
+
+- __Unidirectional__: `{terms separated by comma};{equivalent term};{status};{locales separated by comma}`
+
+   __Example:__
+   - `smartphone;iPhone;true;en-GB`: When searching for smartphone in the English language store (`locale en-GB`), the website will return results for `iphone`. However, when searching for `iphone`, the website will not return results for `smartphone`.
+
+- __Bidirectional__: `{terms separated by comma};{status};{locales separated by comma}`
+
+    __Example:__
+    - `tv,smart tv;true;en-GB`: When searching for one of these terms in the store in English (`locale en-GB`), the search results will return any product that contains one of these terms.
+
+<div class="alert alert-warning">
+  <p>If the imported .csv file does not have the <code>locale</code>, the synonym will be valid for all languages available in the store.</p>
+</div>
+
diff --git a/docs/tutorials/en/creating-trigger-in-master-data.md b/docs/tutorials/en/creating-trigger-in-master-data.md
index b36788f65..f297df314 100644
--- a/docs/tutorials/en/creating-trigger-in-master-data.md
+++ b/docs/tutorials/en/creating-trigger-in-master-data.md
@@ -3,8 +3,8 @@ title: 'How to create a trigger in Master Data v1'
 id: tutorials_1270
 status: PUBLISHED
 createdAt: 2017-04-27T21:56:49.666Z
-updatedAt: 2022-12-14T18:27:30.828Z
-publishedAt: 2022-12-14T18:27:30.828Z
+updatedAt: 2024-06-27T13:01:58.637Z
+publishedAt: 2024-06-27T13:01:58.637Z
 firstPublishedAt: 2017-04-27T23:03:50.015Z
 contentType: tutorial
 productTeam: Master Data
@@ -16,147 +16,156 @@ subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
 <div class="alert alert-info">
-This article talks about Master Data v1. If you want to use Master Data v2, check out the steps explained in <a href="https://help.vtex.com/en/tutorial/setting-up-triggers--54eVOFGhS0EWyAUieoqKWo">this article</a>.
+<p>This article is about Master Data v1. If you want to use Master Data v2, see the steps in the guide <a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2">Setting up triggers in Master Data v2</a>.</p>
 </div>
 
-Conceptually, the “Trigger” is a programming feature that is executed whenever its linked event takes place. In Master Data, the trigger is the setup of one or more events when a given situation takes place. This situation is set up based on several variables.
+Conceptually, a trigger is a programming resource that performs a specific action whenever an associated event occurs. In Master Data, a trigger consists of configuring one or more events that activate when a particular situation occurs based on different variables.
 
-This enables the use of certain data automation and controls, increasing the efficiency of your data management. In other words, simply speaking, triggers are functionalities that enable the scheduling of actions if an event takes place.
+This enables diverse automations and data control, increasing the efficiency of your data management. A trigger is a feature that allows you to schedule actions to be executed when a triggering event occurs.
 
-1. A data entity contains data from all stores
-2. A new registry is added to this entity
-3. A configured trigger sends an email providing all customers with this update
+For example:
 
-Suppose that certain actions are scheduled to take place when a given condition is met. Accordingly, any information recorded in MasterData may trigger innumerable actions, as required. Triggers have some important characteristics, as described below:
+1. A data entity contains the data of all your physical stores.
+2. A new record is added to this entity.
+3. A configured trigger sends an email to all customers with the updates.
 
-- They relate to a data entity;
-- They are called automatically;
-- They cannot be called directly;
-- They set off several actions;
-- They enable the creation of recursion scenarios;
-- They may impact the handling of data by the entity, due to the previous characteristic.
+Triggers allow you to schedule actions to be executed when certain conditions are met. Any information registered in Master Data can trigger many other actions as desired.
 
-Triggers are set up through a 4-step process. Each step is detailed below:
+Below are the main characteristics of triggers:
 
-1. Settings of the action that will activate the trigger. You have to determine which action must be followed by another action. This setting is divided in two parts: **condição** and **filtros adicionais**. Condição (condition) is the action that sets off the trigger (for example, a registration), while filtros (filters) are the specifications that must be met so that the return action can be executed, such as a registration that is carried out through a newsletter form, rather than upon the completion of a purchase. In this case, the condition of the trigger would be as follows: “Whenever a record is included”, and the additional filters include an “origin” field filtering by “newsletter.” So, whenever a new registration is made, the trigger checks whether the customer registered through the newsletter and, only in this case, it would carry out the action that was set up for this purpose.
-2. Trigger timing. It is possible to set up several sending actions separated by time intervals. You may also schedule the trigger according to the date of another field. For example: the field “Maturity Date” is included in the registration of a “Product” entity; it is required that, 1 month before this date, a notice is sent by API to another system. In this case, the trigger timing will be the “Maturity Date” less 1 month.
+- They are associated with a data entity.
+- They activate automatically.
+- They cannot be called directly.
+- They trigger several actions.
+- They allow creating recursion scenarios.
+- They can impact the manipulation of the entity's data due to the previous aspect.
 
-Actions that will be performed when a record meets the condition of the trigger and the filters. Here, you must set up all actions that will be executed when the record that met the conditions has also met the filters and reached the date established in the schedule. These actions may include the sending of e-mails, comments, changing other fields and other possibilities, which are detailed below: Real example:
+## Trigger structure
 
-- **Condition – **The Checkout attribute is changed.
-- **Additional filter – **Checkout is equal to Completed
-- **Actions in positive case – **Change the Bonus field (score type) by including a bonus tag with value 10 and valid for 30 days.
+Before [creating a trigger](#configuring-triggers), it's important to understand that configuring a trigger has four parts, which are explained below.
 
-In this case, this is a situation that seeks to score a field at each new purchase made by the customer. That is, at each order made by the customer, 10 points are added to the Bonus field. Supposing that the bonus is granted when this field reaches 40 points, another trigger is required to check this bonus and grant the promotion. For this purpose, a second trigger will associate the customer with a cluster that is already set up in a promotion. See below the settings of the second trigger:
+![trigger](//images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/7c3bad97c814b7cb52393616ef58fa47/trigger-en.png)
 
-- **Condition** - The Checkout attribute is changed**.**
-- **Additional filter ** - The bonus is equal to or greater than 40.
-- **Actions in positive case** – Change the ClusterBônus field to “true.”
+### Action that fires the trigger
 
-Actions that will be performed when a record meets the condition of the trigger but not the filters. This option is exactly the opposite of the option above. It will be performed only when the record that met the condition of the trigger **does not** meet the additional filters. Real example:
+To configure this, you need to decide which action should trigger another action. This configuration is separated into two parts:
 
-**Condition** – Addition of a new record in the Extended Registration
-**Additional filter** – The sex is equal to “female”.
-**Actions in positive case** – Sending of e-mail with offers from the women’s department.
-**Actions in negative case** - Sending of e-mail with offers from the men’s department.
+- **Rule**: Action that fires the trigger. Example: A new registration in the store.
+- **Additional filters**: Conditions the action must meet for the response action to be executed, such as registration through a newsletter form and not through the checkout. Example: To trigger the action, registration must be done through the newsletter form, not checkout.
 
-## How to set it up
+In this example, the trigger condition would be **Every time a record is created**, and in the additional filters, there should be a "source" field filtered by "newsletter". So, whenever a new registration is made, the trigger checks whether the customer registered via the newsletter. Only if this condition is met will the configured action be executed.
 
-1. Go to the DynamicStorage (https://*YOURSTORE*.ds.vtexcrm.com.br);
-2. Click on the **Trigger **tab;
-3. Click on the **Novo **button;
-4. Enter the trigger Name;
-5. Give an e-mail address to receive a notice in case the execution fails;
-6. Select the [data entity](/tutorial/criando-entidade-de-dados/ "data entity") that will activate the trigger;
-7. After selecting the data entity, the other fields of the settings will be displayed;
-8. Select a status for the trigger;
-9. Continue to set up the tabs as below:
+### Trigger time
 
-### Conditions
+You can set multiple triggers separated by a time intervals. Or, even better, schedule the trigger based on the date of another field. For example, there is a **Due date** field in a **Product** entity record, and you want an API notification to be sent to another system 1 month before the due date. In this case, the trigger time will be the **Due date** minus 1 month.
 
-Here, you will define the conditions that will activate the event(s) set up in the trigger. These settings are described below:
+### Actions that will be executed if a record meets the trigger rule and filters
 
-#### Condition of the trigger
+You must configure all the actions that will be executed when the record meets the conditions and filters. These actions can include sending an email or scoring a field of Score2 type, among other options, as detailed below.
 
-- **The value of an attribute was changed** – this means that, should there be any change in the value of the field given, regarding any record, this trigger will be activated.
-The field to be filtered must be given. E.g.: When the “E-mail” field is changed, the trigger should be set off – give the “E-mail” field in the “Give the attribute” field.
-- **An event was raised** – This type was discontinued.
-- **A record was changed **– this means that when a record is changed in any field, this trigger will be activated.
-- **A record was commented **– this means that, when a record is commented, this trigger will be set off.
-- **A record was entered** – this means that, when a record is entered, this trigger will be set off.
-- **A record was removed **– this means that, when a record is removed, this trigger will be set off.
+Example: A scenario in which you want to score a field with every new order. Every time the customer places an order, 10 points are added to the current value of the **Bonus** field.
 
-#### Additional filter
+- **Rule**: When the Checkout attribute is changed.
+- **Additional filter**: Checkout equal to Completed.
+- **If positive actions**: Change the Bonus field (Score2 type), setting the bonus tag to 10 and valid for 30 days.
 
-**Add group** – creates groups that contain filters. Each of these groups may relate to other groups in order to create more complex filter layers.
-![relacaoGrupos](//images.contentful.com/alneenqid6w5/6n2ipjsapUYyG8quIucIke/1b789ceed1f6ea993096f0d3c857b114/relacaoGrupos.png)
+### Actions that will be executed if a record meets the trigger rule but does not meet the filters
 
-**Enter filter** – this can be created inside the most recently created group, or without the need for a group. In the set model, a filter always interacts with other filters through the “AND” and “OR” options for each one of them.
-The fields and values accepted must be selected in order to activate the trigger.
-![filtroTrigger](//images.contentful.com/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/cf6c5ef321a8d39e16a09d30c2ca1245/filtroTrigger.png)
+In this configuration, you must define actions that will only be executed if the record that meets the trigger condition **does not** meet the additional filters. Example:
 
-<div class="alert alert-info">
-Master Data v1 does not allow retries configuration, unlike Master Data v2.
-</div>
+- **Rule**: When a new record is created.
+- **Additional filter**: Gender is equal to female.
+- **Actions if positive**: Sends an email with deals from the female department.
+- **Actions if negative**: Sends an email with deals from the male department.
+
+## Configuring triggers
+
+Follow the instructions below to create a trigger in Master Data v1:
 
-#### Scheduling
+1. Access Master Data at `https://{accountname}.ds.vtexcrm.com.br/`, replacing `{accountname}` with your VTEX account name.
+2. Click the **Trigger** tab.
+3. Click the `Add` button.
+4. Enter the **Name** of the trigger.
+5. Select the [data entity](https://help.vtex.com/en/tutorial/data-entity--tutorials_1265 "data entity") that will fire the trigger.
+6. After selecting the data entity, the other configuration fields will be displayed.
+7. Select a status for the trigger, which can be **Enabled** or **Disabled**.
+8. Configure each of the tabs based on the sections:
 
-This defines when the trigger should be activated. It can be immediately, through the option “Execute as soon as possible;” scheduling for a calendar date through “Schedule for a specific date;” or a future value, starting from the current date or the date of some date field, using minutes, hours, days, month and years through the option “Schedule the execution for a dynamic date.”
+	- [Rules](#rules)
+	- [Schedule](#schedule)
+	- [If Positive](#if-positive)
+	- [If Negative](#if-negative)
 
-### Actions in positive case
+9. Click `Save`.  
 
-The events to be triggered in case the record that triggered the event meets the conditions of all additional filters, will be set up.
+### Rules
 
-#### Changing an attribute
+In this section, you must set the conditions that will fire the event(s) configured in the trigger.
 
-This action changes the record field that activated the trigger. The field (attribute) that must be changed and the formula to be used must be given. The field “Expressões dinâmica” displays the values that should be used in the formula in case you intend to use the values given in the record fields or fields of related records (if any). “Formula” is a C# code that returns a value of the same type defined in the data entity for the field.
-![fórmula](//images.contentful.com/alneenqid6w5/F3qRfRkScKWAYoCas4GCe/36f27cb6e71425b80340e1221251d3d2/f_C3_B3rmula-1.png)
+#### Trigger rules
 
-The Validar button will compile the code in the formula field to check whether or not it is valid, showing the value that will be returned to the field.
-![validacaoFormula](//images.contentful.com/alneenqid6w5/3Fjh4Q1hVCqkY0yAmMSmOM/67564a371055792fd5c0f40efed7670b/validacaoFormula.png)
+- **An attribute value is changed**: When the value of the field below is changed in any record, the trigger will be enabled.
 
-#### Entering a comment
+   In the **Field** option, select the field that will be used. For example: If the trigger should be fired when the **Email** field is changed, select the **Email** field.
 
-Includes a comment in the record that activated the trigger. Type in the comment that will be entered.
+- **A filter attribute is changed**: The trigger will be fired when a filter attribute is changed.
+- **A record is changed**: The trigger will be fired when a record is changed in any field.
+- **A record is created**: The trigger will be fired when a record is created.
+- **A record is deleted**: The trigger will be fired when a record is deleted.
 
-#### Sending an email
+#### Additional filters
 
-Sends an e-mail for fixed or dynamic (included in the record) addressees. The e-mail to be sent is fully customized, and it may be a text, HTML, or even the contents of an URL. Attachments can also be included, and the “tag válidas” field shows how to enter values in record fields.
-![email](//images.contentful.com/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/89d9d75e4cfdb2fd539dece5a542f8ce/email.png)
+- **Add Group**: Creates groups with filters. Each group can be related to the others, creating more complex filter layers.
+- **Add Filter**: You can create a filter within the last group created or independently of groups. A filter always interacts with other filters based on the set arrangement, with the "and" and "or" options for each.
 
-#### Assigning points to the Score field
+   Select which fields and values are accepted or not for the trigger to be fired.
 
-A score field includes a special type of data about 3 information: Key, Points and Effectiveness. You may establish a value for each of these points and save it in a Score-type field. 
+   ![filters-en](//images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/c0d93fda52ba199ee2101c62028d1c33/filters-en.png)
 
-#### Generating a QRCode
+<div class="alert alert-info">
+  <p>Master Data v1 does not allow the configuration of trigger reattempts, unlike Master Data v2.</p>
+</div>
 
-generates a QRCode with the content entered. This QRCode must be entered in some file-type field of the record.
+### Schedule
 
-More than one action can be set up, but we recommend including up to 3 actions per trigger. The actions have to be set up according to a priority, or, in case of failure in the settings of an event, the subsequent events will not be triggered.
+This tab allows you to configure when the trigger should be fired:
 
-#### Sending an HTTP request
+- **Run ASAP**: Immediately.
+- **Schedule on specific date**: Schedule for a specific date and time in the calendar.
+- **Schedule on dynamic date:** Set a future date, starting from the current date or the date of a date field. You can use minutes, hours, days, months, and years.
 
-Send an HTTP request and save the response information in the Master Data.
+### If Positive
 
-Fill in the **Request data** section with the information of the request to be sent. In the **Response action** section, you can indicate how the response information should be saved in the Master Data.
+In this tab, you must configure the events to be triggered if the record that triggered the event meets all the additional filters.
 
-![Master Data v1 send http request screenshot](https://images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/74bc888f1f8b2a901e642d9809207fd5/mdv1_trigger_http_request.PNG)
+#### Send an email
 
-To configure the **Response action**, select the desired data entity and set the corresponding JSON path in the response for each field to be saved.
+Sends an email to dynamic (specified in the record) or static recipients. The email content can be customized to include text, HTML, or even URL content. You can also add attachments, and the **Valid tags** field shows how to enter field values in the record.
+
+![send-email-en](//images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/ed63e14a042e2e8b9ec80cc7303b7f00/send-email-en.png)
 
-### Actions in negative case
+#### Send an email using a VTEX Message Center template
 
-Some events are set off when a record does not go through the additional filters of the trigger. The same events of the “Actions in positive case” can be set up.
+Sends an email using an existing Message Center template.
 
-<!--
-## For example:
+#### Add scores to the Score2 field
+
+A Score2 field is a special type of data that stores three pieces of information: key, points, and validity. You can define a value for each score and save it in a field of this type.
+
+#### Send an HTTP request
+
+Sends an HTTP request, allowing you to save the response details in Master Data.
+
+Complete the **Request information** section with the request details you want to send. In the **Response action** section, you can indicate how the response details should be saved in Master Data.
+
+![http-request-en](//images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/63d495ea6217ad26f62c5d1f26b4d299/http-request-en.png)
+
+To configure the **Response action**, select the desired data entity and set the corresponding JSON path in the response for each field to be saved.
 
-Watch the video indicated below, which shows the settings for the following scenario: Sending of an e-mail welcoming the new customers of the store. Except if the customer is included in a cluster. In this case, the initial approach to customers will be made by phone. So, “Cluster 1” customers should not receive a welcome e-mail.
+### If Negative
 
-<iframe width="840" height="473" src="https://www.youtube.com/embed/A6UrxcYIq5E?feature=oembed" frameborder="0" allowfullscreen></iframe>
--->
+Events will be triggered when the record does not meet the trigger additional filters. The same events can be configured for [actions if positive](#if-positive).
 
 ## Examples
 
-- [Setting up Cart Abandonment (Trigger)
-](https://help.vtex.com/en/tutorial/configurando-carrinho-abandonado--tutorials_740)
+- [Configuring abandoned carts](https://help.vtex.com/en/tutorial/configuring-abandoned-carts--tutorials_740)
diff --git a/docs/tutorials/en/credit-card-basic-payment-flow.md b/docs/tutorials/en/credit-card-basic-payment-flow.md
index bf3128afc..2680ff15b 100644
--- a/docs/tutorials/en/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/en/credit-card-basic-payment-flow.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 This article aims to explain how the basic flow of a __credit card__ payment works:
 
-![EN Credit Card Flow](https://images.ctfassets.net/alneenqid6w5/5uiKlzNdkvbaN0u8pYltiv/6fadc7c928fd8974e8398c410b6716c7/EN_Credit_Card_Flow.svg)
+![EN Credit Card Flow](//images.ctfassets.net/alneenqid6w5/5uiKlzNdkvbaN0u8pYltiv/6fadc7c928fd8974e8398c410b6716c7/EN_Credit_Card_Flow.svg)
 
 1. On the Checkout screen, the customer chooses the credit card __Payment Method__ to pay for their purchase.
 2. Payment information is passed to the __Payment Gateway__. The [gateway](/en/tutorial/what-is-a-payment-gateway) is the player responsible for ensuring that this payment is successful.
diff --git a/docs/tutorials/en/criar-um-produto-beta.md b/docs/tutorials/en/criar-um-produto-beta.md
new file mode 100644
index 000000000..0d862642e
--- /dev/null
+++ b/docs/tutorials/en/criar-um-produto-beta.md
@@ -0,0 +1,194 @@
+---
+title: 'Adding products (Beta)'
+id: 2nkoy6RakJEVF7ug4ZP0bP
+status: PUBLISHED
+createdAt: 2023-10-31T13:43:19.226Z
+updatedAt: 2023-11-05T15:00:16.505Z
+publishedAt: 2023-11-05T15:00:16.505Z
+firstPublishedAt: 2023-11-05T14:13:41.744Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: criar-um-produto-beta
+locale: en
+legacySlug: criar-um-produto-beta
+subcategory: 
+---
+
+<div class="alert alert-info">This feature is currently in beta, which means we are working on improving it. If you have any questions, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a>.</div>
+
+The **Add Product (Beta)** page allows you to create and edit[ products](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) and their corresponding [SKUs](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) in the VTEX Admin. To add a new product, follow the steps below.
+
+1. In the VTEX Admin, go to **Catalog > Products & SKUs**, or type **Products & SKUs** in the search bar at the top of the page.
+2. Click `+ Add Product`.
+3. Determine if the product being created will be active in the store. To create the product as active in the store, select the **Active** &lt;i class="fas fa-toggle-on">&lt;/i> option in the top right corner of the page.
+If you want to create a product as inactive, click the <i class="fas fa-toggle-on"></i> button and note that the option will change to **Inactive**. You can activate it later from the product edit page or the product list.
+4. Complete the information in each tab as detailed below.  
+
+○  	[Product](https://docs.google.com/document/d/186UuyKqeTz8CNGGm8UTcw81kp18RoApX5zuXccZHylc/edit#produtos) 
+
+○  	[Attributes](https://docs.google.com/document/d/186UuyKqeTz8CNGGm8UTcw81kp18RoApX5zuXccZHylc/edit#atributos)
+
+○  	[SKUs](https://docs.google.com/document/d/186UuyKqeTz8CNGGm8UTcw81kp18RoApX5zuXccZHylc/edit#skus)
+
+5. Select the **Active**&lt;i class="fas fa-toggle-on">&lt;/i> option at the top right of the page to activate the SKU.
+6. Click `Save`.
+
+After that, the product will be activated and available in your store.
+
+<div class="alert alert-info">If the product is not visible on your store after creating it, read the <a href="https://Why is the product not visible on the website?">Why is the product not visible on the website?</a> article to find out how to solve this problem.</div>
+
+## Product
+
+In this tab, complete the fields described below to create the product.
+
+### General information
+![image9](//images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
+- **Name:** Enter the product name. Use simple words, avoiding other languages or complex writing. This field is crucial for SEO and must respect the 150-character limit. Required field. **Example**: Ultralight Running Shoes.
+- **Substitute words:** Enter synonyms of terms related to the product name, separated by commas (`,`). This field is essential for a more comprehensive search and must respect the 8,000-character limit. **Example**: for the product `Ultralight Running Shoes`, synonyms could include `Light Running Shoes,Ultra Running Shoes`. If your store uses VTEX Intelligent Search, do not complete this field and read the[Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) article.
+
+- **Brand**: Select a brand already available in the store to associate with the product. Required field. Example: SportXtreme.
+
+- **Category:** Select the category or subcategory associated with the product. Required field. **Example**: Running shoes.
+
+- **Reference code:** Enter the product's unique reference code to improve your store management. **Example**: TXU1234.
+
+### Description
+
+In this step, you must write a description with the main information about the product. The text must contain a clear and simple product description.
+
+Example: "The Ultralight Running Shoes are the perfect choice for athletes looking for high performance and comfort. Their innovative design and high-tech materials provide the utmost lightness and resistance during physical activity."
+
+The text editor for the description is a _rich text_ editor, which means you can use different formatting tools in its toolbar, as shown in the image below.
+![image10](//images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
+
+See the tools available in the toolbar:
+
+- **Styles**: Define the style of the selected text. You can choose from **Normal**, and **Heading 1** to **Heading 6**.
+
+- **Font size:** Changes the font size of the selected text. You can choose from 10 to 36 pts.
+
+- **Bold:** Formats the selected text in bold.
+
+- **Italic:** Formats the selected text in italics.
+
+- **Underline:** Underlines the selected text.
+
+- **Align text left:** Aligns the selected text to the left.
+
+- **Center text:** Centers the selected text.
+
+- **Align text right:** Aligns the selected text to the right.
+
+- **Bulleted list:** Converts the selected text into an unordered list with bullets.
+
+- **Numbered list:** Converts the selected text into an ordered list item.
+
+- **Add link:** Adds a link to the selected text. After clicking this button, complete the required fields and then click `Save`.
+
+     - **Link title:** Enter the text with the link.
+     - **URL:** Enter the link to which the text will redirect the user.
+     - **Open in new tab:** Select this option if you want the user to open the page in a new tab when they click the link. Do not select it if you want the user to open the link in the same tab.
+
+- **Source code:** Displays the source code of the HTML description. You can edit the description directly from the source code if you want. To go back to the previous view, click the source button again.
+
+### SEO 
+![image11](//images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
+
+- **Product URL:** Enter the URL to access the product page in the store. You cannot use spaces or special characters in this field. If the URL consists of more than one word, you must separate them with a hyphen (-). Required field. **Example**: ultralight-running-shoes.
+
+-  **Page title:** Enter the title of the product page. To optimize the ranking of your product in the search results, do not exceed 60 characters. Required field. **Example**: Ultralight Running Shoes
+
+- **Meta description:** Enter the title of the product page. To optimize the ranking of your product in the search results, do not exceed 60 characters. Required field. **Example**: Meet the SportXtreme Ultralight Running Shoes, perfect for athletes looking for lightness and maximum performance in sports activities.
+
+### Operation and Logistics
+
+- **Trade policies:** Select one or more[ trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) for the product to determine the marketplaces in which the product will be available. If no trade policy is selected, the product will be applied to all of them. Example: B2C.
+- **Supplier: **Select a supplier already added to the store to link to the product.
+- **Tax code:** Enter the fiscal identification number of the product.
+
+### Visibility 
+![image4](//images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)
+
+- **Display on website:** Enable or disable the product visibility in your store. For example, if the product is a gift that cannot be purchased, you should disable this option.
+
+- **Show when out of stock:** Enable or disable the option to show the product in the store even when it is out of stock. If enabled, the out-of-stock product will be displayed in your store with a [Notify me](https://help.vtex.com/en/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e) field, in which the customer can enter their email to be notified when the product is back in stock. If this option is disabled, the product will not be displayed in the store when it is out of stock.
+- **Priority in search order:** Enter a numerical value to set the priority on the search results page. For more details on this field, read the[How does the Score field work?](https://help.vtex.com/en/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae) article. 
+
+If your store uses VTEX Intelligent Search, read the[How does VTEX Intelligent Search work?](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/23mytRDsEduqLO0Lo7yufy) article.
+
+## Attributes
+
+Depending on the product category you create, you may have to complete some fields in the **Attributes** tab. These fields are [specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) you can add to your SKUs to give them characteristics.
+
+If you have created any required product fields, the product will only be activated once this specification has been completed.
+
+Under **Attributes**, the [specification groups](https://help.vtex.com/en/tutorial/criando-grupo-de-especificacoes-em-uma-categoria--tutorials_246) will be displayed with the specifications you entered. In the image below, the specification group is **Characteristics**, and the specifications are **Video** and **See More**.
+![image3](//images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
+
+## SKUs
+
+In this tab, you will add the [SKUs](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) that will be linked to the product you created earlier.
+
+<div class="alert alert-info"> A product must have at least one active SKU to be available in your store. The SKU must have an image attached to it for it to be activated. </div>
+
+### Specifications
+This is where the previously created [specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) for the SKUs will be displayed. If you have created any required SKU fields, the SKU will only be activated once this specification has been completed.
+
+### Basic Information
+![image2](//images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
+- **Name:** The SKU name, which will be displayed in the store. Required field.
+- **Reference code:** Code that the store will use internally to identify the SKU. Required field if the **EAN/UPC** is empty.
+- **EAN/UPC**: Field that must have the barcode information. Required field if the **Reference code** field is empty.
+- **Manufacturer code:** Provided by the manufacturer to identify their product. If a product has a specific code, this field must be completed.
+- **Commercial condition:** Used to define specific promotions or installment rules for SKUs. If there is no specific condition, use the default value. Learn more in the[Registering a commercial condition](https://help.vtex.com/en/tutorial/como-cadastrar-condicao-comercial--tutorials_445) article. 
+- **Modal:** Field that links an unusual product (e.g., meat, glass, mattress) to a carrier specialized in delivering this product. Learn more in the[How the modal works](https://help.vtex.com/en/tutorial/como-funciona-o-modal--tutorials_125) article.
+
+### Images
+
+<div class="alert alert-warning">
+SKUs must have at least one image to be active.</div>
+
+To add an image to your SKU, follow the steps below:
+
+1. Click the `+` button.![image8](//images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
+2. Add the link to your image in the 🔗 field. You can add more than one image to your SKU. To do this, click `+ Add Image` and add the new link. ![image6](//images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
+3. Click `Save`.
+
+<div class="alert alert-info">The first image added will be the main image of the SKU and will be displayed in the store and search results.
+</div>
+
+You can edit an image's metadata by clicking the &lt;i class="fas fa-ellipsis-v">&lt;/i> button and selecting <i class="fas fa-pencil-alt"></i>` Edit Metadata`.
+
+You can also delete an image by clicking the <i class="fas fa-ellipsis-v"></i> button and selecting <i class="fas fa-trash-alt"></i>`Remove`
+
+### Weight and Dimensions
+![image1](//images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
+#### Shipping weight and dimensions
+
+- **Package weight:** Weight of the empty package in kilos. Required field.
+
+- **Package width:** Width of the package in centimeters. Required field.
+
+- **Package height:** Height of the package in centimeters. Required field.
+
+- **Package length:** Length of the package in centimeters. Required field.
+
+#### Actual weight and dimensions
+
+- **Actual weight:** Weight of the SKU in kilos.
+- **Actual width:** Width of the SKU in centimeters.
+- **Actual height:** Height of the SKU in centimeters.
+- **Actual length:** Length of the SKU in centimeters.
+
+#### Unit system
+- **Unit of measure:** Used when the unit of measure needs to be converted for sales purposes. For example, if a product is sold by the box but customers want to buy it by m². Usually used as "ea." (abbreviation for each).
+
+- **Unit multiplier:** Numerical unit that multiplies the selected quantity of the product when it is added to the cart. If the multiplier is 5, the product will be added in multiple quantities of 5, such as 5, 10, 15, 20, and so on.
+
+### Advanced Settings 
+![image5](//images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
+
+- **Activate bundle:** Determines if SKUs within a bundle can only be sold together. You can make the SKU part of a bundle &lt;i class="fas fa-toggle-on">&lt;/i> or not &lt;i class="fas fa-toggle-off">&lt;/i>.
+
+- **Generate credit with gift card**: Determines if the customer receives [credit](https://help.vtex.com/en/tutorial/gift-card--tutorials_995) when buying an SKU. You can activate <i class="fas fa-toggle-on"></i> or deactivate <i class="fas fa-toggle-off"></i> this option.
diff --git a/docs/tutorials/en/custom-fields-when-adding-an-organization.md b/docs/tutorials/en/custom-fields-when-adding-an-organization.md
new file mode 100644
index 000000000..800ea876a
--- /dev/null
+++ b/docs/tutorials/en/custom-fields-when-adding-an-organization.md
@@ -0,0 +1,46 @@
+---
+title: 'Custom fields when adding an organization'
+id: 2MqEVusOvcbqagNwOuHA7f
+status: PUBLISHED
+createdAt: 2024-06-06T12:19:51.817Z
+updatedAt: 2024-07-03T17:35:29.850Z
+publishedAt: 2024-07-03T17:35:29.850Z
+firstPublishedAt: 2024-06-06T12:40:11.507Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: custom-fields-when-adding-an-organization
+locale: en
+legacySlug: custom-fields-when-adding-an-organization
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+The VTEX platform allows users with an admin role to create and manage custom fields when adding new organizations or cost centers. This feature simplifies the inclusion of specific and relevant information for the company.
+
+## Defining and managing fields
+
+Users with an admin role can define additional fields in the VTEX Admin, which will be displayed when adding new organizations or cost centers. These custom fields are designed to capture specific and useful information that is not available on the registration form.
+
+## Adding a custom field
+
+Custom fields enable users to add specific and personalized information for organizations or cost centers. These fields can be tailored to the company's needs to obtain relevant information.
+
+To add a custom field, follow these steps:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+2. Click the **Custom Fields** tab.
+
+3. Choose between the Organizations or Cost centers options in the selection box.
+
+4. Click the **Add Field** button. An empty row will be added to the list of custom fields.
+
+5. Under the empty row, click <i class="fas fa-ellipsis-v" aria-hidden="true"></i> to edit.
+
+6. Complete the required information:
+    - **Use on Registration:** Indicates whether the field should be displayed in the registration form.
+    - **Field Type:** Determines whether the field will be text or a list with selectable values.
+    - **Custom Field Name:** Name of the field you want to customize.
+7. Click `Update`.
+
+Make sure you click `Save Settings` in the top right corner to apply the changes.
diff --git a/docs/tutorials/en/custom-payment-information-for-argentina.md b/docs/tutorials/en/custom-payment-information-for-argentina.md
index b61b97d2b..2c27d01e3 100644
--- a/docs/tutorials/en/custom-payment-information-for-argentina.md
+++ b/docs/tutorials/en/custom-payment-information-for-argentina.md
@@ -1,10 +1,10 @@
 ---
 title: 'Custom payments information for Argentina'
 id: jvDroisg0wu0sQMAW4qAs
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.320Z
-updatedAt: 2019-12-31T15:27:50.416Z
-publishedAt: 2019-12-31T15:27:50.416Z
+updatedAt: 2024-03-19T12:11:44.590Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:14:28.069Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/custom-product-fields.md b/docs/tutorials/en/custom-product-fields.md
new file mode 100644
index 000000000..4611ab85f
--- /dev/null
+++ b/docs/tutorials/en/custom-product-fields.md
@@ -0,0 +1,20 @@
+---
+title: 'Custom product fields'
+id: 6tJOSJ2o9phVIb8XXG6QSk
+status: PUBLISHED
+createdAt: 2024-07-23T19:44:34.554Z
+updatedAt: 2024-07-23T20:25:32.123Z
+publishedAt: 2024-07-23T20:25:32.123Z
+firstPublishedAt: 2024-07-23T20:17:01.358Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: custom-product-fields
+locale: en
+legacySlug: custom-product-fields
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning">
+This is a regional exclusive content not applicable to English speaking countries.
+</div>
diff --git a/docs/tutorials/en/customer-approval.md b/docs/tutorials/en/customer-approval.md
index 2204318d7..e8a65f5e0 100644
--- a/docs/tutorials/en/customer-approval.md
+++ b/docs/tutorials/en/customer-approval.md
@@ -3,8 +3,8 @@ title: 'Customer approval'
 id: 2fDHMMLJl00Pm6imiACU72
 status: PUBLISHED
 createdAt: 2021-03-30T16:54:48.752Z
-updatedAt: 2023-03-29T00:06:00.612Z
-publishedAt: 2023-03-29T00:06:00.612Z
+updatedAt: 2024-06-18T22:16:38.698Z
+publishedAt: 2024-06-18T22:16:38.698Z
 firstPublishedAt: 2021-03-30T17:14:26.769Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,25 +15,25 @@ legacySlug: customer-approval
 subcategory: 42hDtnYXHw5ExG6l19RP1l
 ---
 
-You can approve customers in the Master Data via Admin or API.
+Customer approval is carried out in Master Data and can be done via the Admin or via API. See below for instructions on each of the two forms of approval.
 
 ## Approving customers via Admin
 
-To approve customers in the Admin:
+To approve customers in the Admin, follow the steps below:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data.**
-2. Inside the box __Profile System__, click on the  <i class="fas fa-bars"></i>   icon next to __Clientes__ (Customers).
-3. Select the row of the customer you want to approve.
-4. At the bottom of the page, click on the __Editar__ (Edit) button.
-5. Select the __checkbox__ next to the __Aprovado__ (Approved) field.
-6. At the bottom of the page, click on __Salvar__ (Save).
+2. Inside the box __Profile System__, click on the  <i class="fas fa-bars"></i>   icon next to __Customers__.
+3. Click the row of the customer you want to approve.
+4. At the bottom of the page, click on the `Edit` button.
+5. Select the checkbox next to the __Approved__ field.
+6. At the bottom of the page, click on`Save`.
 
 After that, the store content will be displayed to the selected customers. 
 
 ## Approving customers via API
 
-You can approve multiple customers at once via a [Master Data API](https://developers.vtex.com/vtex-developer-docs/reference/master-data-api-v2-overview "API do Master Data") route.
+You can approve multiple customers at once via a [Master Data API](https://developers.vtex.com/docs/api-reference/masterdata-api) route.
 
-All information related to a customer can be interpreted as a document in [“Customer” data entity](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265 "entidade de dados "Cliente""). Therefore, the [PATCH Create or Update partial document](https://developers.vtex.com/vtex-developer-docs/reference/documents#createorupdatepartialdocument "PATCH Create or Update partial document") route must be used to change the "Approved" field value in bulk.
+All information related to a customer can be interpreted as a document in the __Customer__ [data entity](https://help.vtex.com/en/tutorial/data-entity--tutorials_1265). Therefore, the [PATCH Update partial document](https://developers.vtex.com/docs/api-reference/masterdata-api#patch-/api/dataentities/-acronym-/documents/-id-) route must be used to change the __Approved__ field value in bulk.
 
-Check the article [Import customer data](https://help.vtex.com/pt/tutorial/importar-datos-de-clientes-brasil?locale=pt "Importar dados de clientes") to learn which fields are required for a specific individual document.
+Check the [Import customer data](https://developers.vtex.com/docs/guides/import-customer-data) guide to learn which fields are required for a specific individual document.
diff --git a/docs/tutorials/en/customer-credit-overview.md b/docs/tutorials/en/customer-credit-overview.md
index a89fd8de3..886d32614 100644
--- a/docs/tutorials/en/customer-credit-overview.md
+++ b/docs/tutorials/en/customer-credit-overview.md
@@ -3,8 +3,8 @@ title: 'Customer Credit - Overview'
 id: 1uIqTjWxIIIEW0COMg4uE0
 status: PUBLISHED
 createdAt: 2018-11-08T17:11:28.486Z
-updatedAt: 2023-03-29T14:46:02.462Z
-publishedAt: 2023-03-29T14:46:02.462Z
+updatedAt: 2024-02-09T21:37:56.199Z
+publishedAt: 2024-02-09T21:37:56.199Z
 firstPublishedAt: 2018-11-08T19:14:39.491Z
 contentType: tutorial
 productTeam: Financial
@@ -15,94 +15,77 @@ legacySlug: credit-control-overview
 subcategory: 7EWKfPIGfmI0G8iMYK8Aiy
 ---
 
-
-Customer Credit is the VTEX app that allows the store to offer credit to trusted customers. Having more time to pay, the customer has greater purchasing power.
-
-Through the platform, it’s possible to set deadlines and installments, as well as manage accounts, define credit limits and follow the issued invoices. Your customers have visibility of available credit and payables directly on your store's website.
+Customer Credit is the VTEX app that allows a store to offer exclusive credit to its trusted customers, increasing purchasing power by allowing a longer period for payment of orders.
 
 ## When to use it
 
-Business models that have a commercial relationship with their customers often need a credit management system in order to be able to issue billed bank slips without jeopardizing the company's cash flow.
+Business models that have a consolidated commercial relationship with their customers generally require a credit management system that allows the issuance of invoices without compromising the company's cash flow.
 
-Approval of these payments on e-commerce platforms often requires a manual effort of approving each order individually, even for customers who have available credit.
+Approving these types of payments on ecommerce platforms usually requires manual approval effort on an order-by-order basis, even for those customers who already have credit available.
 
-Stores with B2B relationships such as distributors of retail chains, direct sales to resellers, office supplies for companies or industrial supplies can use Customer Credit to offer an experience of purchase and deferred payment integrated to VTEX platform.
+Stores that carry out B2B commercial transactions, such as distributors of retail chains, direct sales to resellers, office supplies for companies or industrial inputs, can use Customer Credit to offer a purchasing and installment payment experience integrated with the VTEX platform.
 
 ## How it works
 
-**Basic flow of how Customer Credit works.**
+Using the VTEX Admin or [Customer Credit API](https://developers.vtex.com/docs/api-reference/customer-credit-api), you can perform the following actions in the Customer Credit app:
 
-1. Store connects the Customer Credit connector and makes the initial settings.
-2. Store sets credit limit for a user's current account.
-3. User places an order using store credit in SmartCheckout.
-4. Order debits its value of the user's credit limit and generates an invoice.
-5. Then, the user pays the generated invoice.  
-6. The invoice's payment recharges the credit limit of the user's current account.
+- Create and manage accounts for chosen customers
+- Set credit limits and tolerances for each account
+- Configure deadlines and installments for invoices documents
+- Monitor and modify the status of issued invoices
 
-Because it was developed in VTEX, Customer Credit is fully integrated with SmartCheckout, which means your customers' buying experience remains the same.
-You can choose the users who will receive credit, set the credit limit for each of them, and individually manage each invoice.
+<div class="alert alert-info">
+When installed, Customer Credit appears as a payment option at Checkout only for customers selected by the retailer, displaying the amount of credit available to be used for the purchase.
+</div>
 
-Customer Credit can be used through both the Admin web interface and the API. 
+See below the basic flow of how Customer Credit works in VTEX stores:
 
-## Concepts
+![GIF_CC_EN](//images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/28fd6b4db8e48a99115fd02e00273b54/GIF_CC_EN.gif)
 
-### Checking account
+## Customer Credit definitions
 
-In order to be able to access the deferred payment, the user must have access to an account registered in the Customer Credit. 
+### Account (Customer Credit account)
 
-This account is made up of identifiers such as email and document, as well as the defined credit limit.
+To use Customer Credit as a payment method for a purchase, the customer must have an account registered by the retailer in the Customer Credit app. This account has information such as the holder's document type and number, email, credit limit and tolerance.
 
 ### Credit limit
 
-For each account you must set a credit limit. This limit indicates the maximum amount that the account can have in open invoices at the same time. 
-When invoices are paid or canceled, their values reset the credit limit. The limit can be reset at any time by the user with the required permissions.
+Each account has a credit limit registered at the time of opening. This limit indicates the maximum amount that the customer can use to make one or more purchases at the same time via Customer Credit.
 
-At the time of purchase, the customer has visibility of how much credit he or she has available. When it’s not enough for the full amount, they can not use their credit.
+<div class="alert alert-warning">
+An account's credit limit can be changed by the retailer at any time.
+</div>
 
-The credit limit set on an account can also be used by more than one dependent.
+### Available credit
 
-### Invoices
+Amount that the customer still has available in their account to make purchases through Customer Credit.
 
-Invoice are references to future payments. They are automatically created when an order paid with Customer Credit is billed. It consists of expiration date, value and description. An external payment link can be added to each invoice in order to facilitate settlement.
+Every time the customer completes a purchase and the order is billed, the amount of available credit decreases. However, after the customer makes payment for the issued invoice, the available credit value returns to the pre-purchase value.
 
-There are 3 possible states for the invoices: **Open**, **Paid** and **Canceled**. In the interface there will be a forth state, the **Overdue**, but which is actually an Open invoice which is expired.
+<div class="alert alert-warning">
+At the time of a purchase, the customer has visibility of how much credit can be used via Customer Credit. If the purchase value is greater than the available credit, payment cannot be made through Customer Credit.
+</div>
 
-An invoice is always created with the Open status, and depending on Admin actions or API calls it can transition to Paid or Canceled.
+### Invoice
 
-### Tolerance
+Invoice is the document generated after the customer makes a purchase using Customer Credit as a payment method and the order is billed.
 
-It allows a purchase to be approved even if it exceeds the user's available credit. 
-If the feature is turned on, a percentage can be configured individually for each registered account.
+In cases of purchases in installments, invoices are generated according to the number of installments. For example, a purchase made with payment in 10 installments on Customer Credit will generate 10 invoices related to the same order number.
 
 ### Deadlines and installments
 
-Customer Credit allows you to set up the installment terms that will be available to your customers as you wish. Some common examples of deadlines used are 7 days, 28, 45, 30/60, 30/60/90, etc.
+Customer Credit allows retailers to configure different payment deadlines and installment scenarios to offer greater payment flexibility to registered customers.
 
 ### Pre-authorization and settlement
 
-Once the payment with credit has been approved, the system pre-authorizes the amount, reserving it automatically after 5 business days or until the order is billed. The value is then settled in the account and the invoices are created.
-
-The flow follows the same pattern as the one for credit cards: alterations made to the order during the pre-authorization period change the amount of reserved credit. 
-
-Changes made after settlement, i.e. after invoice has been issued, update the invoice already issued if the value decreases and issue a new invoice if the order value increases.
-
-## Contact Points
-
-### Admin
-
-The Customer Credit interface in VTEX Admin provides complete visibility of the system: invoices, accounts and general settings. 
-The interface also allows you to fetch, filter and sort data, as well as import and export data.
-
-### Checkout
-
-Through VTEX Checkout users can close purchases using Customer Credit. The system will automatically check if the user already has an account with credit and, if so, will allow the user to authenticate to see the available credit as well as options for closing the purchase, in addition to terms and installments.
+After the customer makes the purchase using Customer Credit, the payment is approved as a credit and the platform pre-authorizes the amount, automatically reserving it after 5 business days or until the order is billed. At this point, the amount in the account is settled and payment invoices are generated.
 
-### My Credits
+The flow in Customer Credit is similar to that of credit cards in regarding order modifications. When an order value change occurs during the pre-authorization period, the credit amount changes.
 
-The interface through which your customer will have access to their account information. 
-It’s very similar to the VTEX Admin Accounts page. In it, users see their available limit, paid and due invoices, and the account history.
+<div class="alert alert-warning">
+If it is necessary to change an order to reduce its value after the settlement period (issuance of invoices), the system will update the invoices to the new value. If the order value is increased, the system will create new invoices.
+</div>
 
-## Installing and setting up
-We've prepared a detailed guide for you to [start using Customer Credit in your store](/en/tracks/customer-credit-getting-started).  Go on and offer exclusive credit to your best customers right now.
+## Installation and configuration
 
-For more information about Customer Credit APIs, visit [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api).
+To install and configure Customer Credit in your store, access Track [Customer Credit - How to get started](https://help.vtex.com/en/tracks/customer-credit-getting-started--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
diff --git a/docs/tutorials/en/customizing-your-stores-typography.md b/docs/tutorials/en/customizing-your-stores-typography.md
index 7b717cf84..e3d52537b 100644
--- a/docs/tutorials/en/customizing-your-stores-typography.md
+++ b/docs/tutorials/en/customizing-your-stores-typography.md
@@ -27,7 +27,7 @@ In the Admin, you have the flexibility to customize your store’s typography to
 1. In the VTEX Admin, access **Storefront > Styles**.
 2. Select the kebab menu icon (three dots).
 
-![Styles - More Options](https://images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/3bc40e3e3a439475b4f0998a3af56854/styles-two-en.png)
+![Styles - More Options](//images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/3bc40e3e3a439475b4f0998a3af56854/styles-two-en.png)
 
 3. Click **Edit > Typography > Font Family**.
 
@@ -51,7 +51,7 @@ Refer to the section [Type tokens](#type-tokens) for more information about them
 2. Select the kebab menu icon (three dots).
 3. Click on **Edit > Typography > Type Tokens**.
 
-![Styles - Type tokens EN](https://images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/dbb378f7b8e11fa1217276626dd6f008/styles-three-en.gif)
+![Styles - Type tokens EN](//images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/dbb378f7b8e11fa1217276626dd6f008/styles-three-en.gif)
 
 4. Choose the type token you want to customize, for example, **Heading 1**, and click it.
 
diff --git a/docs/tutorials/en/dashboards-overview.md b/docs/tutorials/en/dashboards-overview.md
index 1d89c91cb..1e1b21f5a 100644
--- a/docs/tutorials/en/dashboards-overview.md
+++ b/docs/tutorials/en/dashboards-overview.md
@@ -3,8 +3,8 @@ title: 'Dashboards Overview'
 id: 1yn2nZUoXtDO3teTEJsCNl
 status: PUBLISHED
 createdAt: 2023-03-29T21:16:46.179Z
-updatedAt: 2023-03-29T21:18:04.195Z
-publishedAt: 2023-03-29T21:18:04.195Z
+updatedAt: 2024-06-19T15:30:06.441Z
+publishedAt: 2024-06-19T15:30:06.441Z
 firstPublishedAt: 2023-03-29T21:18:04.195Z
 contentType: tutorial
 productTeam: Others
@@ -23,5 +23,4 @@ This section includes the following pages, which are already available in your A
 
 - [Overview](https://help.vtex.com/en/v4/docs/store-overview--6mcM4LPUqQxSiXY6uFtXZy): where store owners have access to key metrics that impact their store revenue. In this dashboard, you can track the evolution of your sales through order trend analysis, conversion rate, and sales funnel charts.  
 - [Sales Performance](https://help.vtex.com/en/v4/docs/sales-performance--6gx46RGRzWO8qgaVck7PRp): a dashboard for unified commerce that helps stores grow their business and make more accurate decisions.  
-- [Web Page Performance](https://help.vtex.com/en/v4/docs/web-page-performance--7DeyhX8cGtG9PtAGkL8zvc):  brings Google's PageSpeed Insights tool to your VTEX Admin, allowing you to track the performance of your ecommerce's URLs. 
 
diff --git a/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md b/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md
new file mode 100644
index 000000000..36d4cd326
--- /dev/null
+++ b/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md
@@ -0,0 +1,54 @@
+---
+title: 'Data dictionary: VTEX Data Pipeline (Beta)'
+id: 69hMoE2woVw14nWR3ujVto
+status: PUBLISHED
+createdAt: 2024-02-01T18:51:29.281Z
+updatedAt: 2024-06-25T14:23:40.720Z
+publishedAt: 2024-06-25T14:23:40.720Z
+firstPublishedAt: 2024-05-27T19:26:59.681Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: data-dictionary-vtex-data-pipeline-beta
+locale: en
+legacySlug: vtex-data-pipeline-catalog-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+<div class= "alert alert-info">
+This feature is currently in beta, which means we are working on improving it. If you have any questions, please contact <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">our support</a>.
+</div>  
+
+**VTEX Data Pipeline** is a tool that only VTEX clients can leverage, which allows exploring and analyzing the ecommerce data that is currently available on our servers. **Data Pipeline** is a VTEX add-on product that integrates the data from your ecommerce website to the data warehouse and BI tools of your choice cleanly and securely.  
+
+## Security and privacy  
+
+**VTEX Data Pipeline** improves security for your ecommerce website data by establishing a direct and secure connection from our data warehouse to your data infrastructure tool. This approach eliminates the need to rely on ETL (Extract, Transform, and Load) processes that run on third-party tools, providing direct and secure control over the flow of data. In addition, a key aspect of our solution is the proactive removal of all personally identifiable information (PII) of the users listed in the tables, thus meeting the best data protection practices.  
+
+## What is a data dictionary?  
+
+This dictionary contains all the datasets that **VTEX Data Pipeline** has available, described in a dedicated section that includes details of their characteristics.  
+
+Each section contains information such as the following:  
+
+- Data characteristics  
+  - Data source  
+  - Availability to client  
+  - History  
+  - Minimum update interval  
+- Dataset tables  
+- Analyses with the dataset  
+- Correlations with other data
+
+## Dataset  
+
+The following sections will help you understand how the data relates to your business and how relevant it is to your project.  
+The available datasets are:  
+
+- [Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navigation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Payments](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs) 
+- [Orders](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Prices](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promotions](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)  
+
diff --git a/docs/tutorials/en/data-entity.md b/docs/tutorials/en/data-entity.md
new file mode 100644
index 000000000..696e815d1
--- /dev/null
+++ b/docs/tutorials/en/data-entity.md
@@ -0,0 +1,109 @@
+---
+title: 'Data entity'
+id: tutorials_1265
+status: PUBLISHED
+createdAt: 2017-04-27T21:56:57.118Z
+updatedAt: 2024-06-21T21:12:23.798Z
+publishedAt: 2024-06-21T21:12:23.798Z
+firstPublishedAt: 2017-04-27T23:03:49.803Z
+contentType: tutorial
+productTeam: Master Data
+author: authors_3
+slug: data-entity
+locale: en
+legacySlug: creating-data-entity
+subcategory: 1l3IVVYwrrG5YOtdt7R2SN
+---
+
+A data entity is a representation of a set of information about a given concept. Each entity includes fields with information that makes up the entity.
+
+For example, imagine a system that controls a library. This system controls books that customers can borrow. Thus, we can notice that these three concepts (book, customer, borrowing) are entities that contain information about each one. 
+
+![data-entity-en](//images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/1b24a20995e073f17e492e8d80ae4031/data-entity-en.png)
+
+With these concepts in mind, you can set up several data control scenarios in Master Data. By default, the following data entities are considered: customer, address, stores, etc. You can create as many data entities as you want to develop a customized environment tailored to your store's needs.
+
+<div class="alert alert-warning">
+<p>This article outlines the Master Data v1 operation. You should evaluate which Master Data version meets your needs or is in use in your operation. Learn more:</p>
+	<ul>
+    	<li><a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#available-versions">Master Data version features</a></li>
+    	<li><a href="https://developers.vtex.com/docs/guides/master-data-v2-basics">Master Data v2</a></li>
+	</ul>
+</div>
+
+## Data types
+
+The data entity consists of fields that have a type. This type identifies the information characteristics stored in the field and enables validations, filters, and calculations based on the selected value.
+
+When creating a field, the following types are displayed:
+
+| Field type | Description
+| - | - |
+| **Auto Increment** | Stores integers and is automatically incremented, which means that for each new record, this field receives the value of the previous record + 1. |
+| **Boolean** | Stores true or false information, which means it will always be completed as `true` or `false`. |
+| **CEP** | Stores a CEP (postal code in Brazil). |
+| **CPF / CNPJ** | Stores the CPF and CNPJ information (taxpayer registration number and company registration number in Brazil, respectively). |
+| **Currency** | Stores information in currency format. |
+| **Date** | Stores date information. |
+| **Date and Time** |  Stores date and time. |
+| **Decimal** |  Stores numbers with the fractional part always set to 2. This field will always store 2 digits as decimal places of the value entered. |
+| **Email** |  Stores an email. |
+| **File** | Stores a file. The maximum size accepted must be set up in the field’s options via the gear icon button<i class="fas fa-cog"></i>. |
+| **Integer** | Stores integers, i.e., numbers without the fractional part. It stores whole numbers between `-2147483648` and `2147483647`. |
+| **Long** | Similar to **Integer** but can store more numbers. Stores from `-2⁶³` to `2⁶³-1`. |
+| **Percent** | Stores information in a percentage format. |
+| **Phone** |  Stores information in a phone number format. |
+| **Relationship** | Creates a relationship with another entity. The term relationship refers to displaying an entity’s information in another entity. For example, in the library example, the **Customer** may also appear in the **Borrowing** record.<br><br>To do so, you just have to establish a relationship between **Borrowing** and **Customer** by using the **Name** field under **Borrowing** and selecting the **Relationship** type in the settings. The **Customer** field to be displayed must also be selected for the **Name** field to be selected. |
+| **Score2** | Field consisting of key, value, and expiration date. For example: This can be used to control purchases made by each customer, storing the amount and quantity of purchases. This field needs to be completed through the [Update scores](https://developers.vtex.com/docs/api-reference/masterdata-api#put-/api/dataentities/-acronym-/documents/-id-/score) or the [Update score by field](https://developers.vtex.com/docs/api-reference/masterdata-api#put-/api/dataentities/-acronym-/documents/-id-/score/-field-name-) endpoint from [Master Data API v1](https://developers.vtex.com/docs/api-reference/masterdata-api). |
+| **Text** | Stores numbers, letters, and special characters, without a character limit. |
+| **Time** |  Stores time information. |
+| **URL** |  Stores a URL. |
+| **User Login** | Automatically selects the user logged in. This is used to record the email of the user who performs an action on an entity record.  |
+| **Varchar 10** | Stores numbers, letters, and special characters, limited to 10 characters. |
+| **Varchar 100** | Stores numbers, letters, and special characters, limited to 100 characters. |
+| **Varchar 50** | Stores numbers, letters, and special characters, limited to 50 characters. |
+| **Varchar 750** | Stores numbers, letters, and special characters, limited to 750 characters. |
+
+## Creating data entities
+
+Follow the steps below to configure a new data entity.
+
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data.**
+2. In Master Data, click **Applications** > **Advanced Settings** > **Data structure.**
+3. Click the **Data Entities** tab.
+4. Click the `Add` button.
+5. Complete the **Acronym** field with 2 letters that identify the data entity. These letters will be the initials of the field that identifies the record. For example: use the acronym SP for identifier SP-0001.
+6. Complete the **Name** of the data entity you want to create.
+7. Select the type of primary key, which can be:
+
+   - **GUID**: A unique sequence of numbers and characters that identifies a record.
+   - **Primary key must be given using the 'ID' property**: This key does not automatically create an identifier field, which must be created manually and named **ID**.
+8. If you need to consult records without a filter and without authentication, check the option **Allow all document query without filter**. Note: This setting is critical because it allows all the records in the database to be listed via the API.
+9.  Complete the **Fields** tab with the fields you want to include in the new data entity, indicated as follows.
+10. Complete the **Name** column with the field's identification value. Do not insert spaces or special characters. Example: CustomerName.
+11. Complete the **Display Name** column with the name that will be displayed on the form. Example: Customer name.
+12. Select the field type based on the options described in the [Data types](#data-typed) section.
+13. Click the <i class="fas fa-cog"></i> gear icon to open the field configuration options.
+14. Complete the **General settings**:
+
+ 	- **Is nullable?:** Check this option to create or edit a record with a blank (void) field. If this option is unchecked, you cannot create a record without a value in this field.
+ 	- **Make readable without credentials:** Check this option to allow the field data to be read without authentication, using the Master Data API.
+ 	- **Allow editing without credentials:** Check this option to allow data to be entered into the field without the need for authentication, using the Master Data API.
+ 	- **Allow filtering without credentials:** Check this option to filter field data without the need for authentication, using the Master Data API.
+
+15. Complete the **Search and filter settings**:
+
+	- **Is searchable?**: If this field is used for searching in the form and via API.
+	- **Is filterable?:** If this field is used to filter the form and via API.
+16. Add a field description.
+17. To add more fields, click the `New Field` button and repeat steps 10 to 16.
+18. At the end of the field definition, click the `Save` button to complete or `Save and New` to create a new data entity.
+
+	You will be redirected back to the **Data Entity** tab.
+
+19. In the row of the newly created entity, click the <i class="fas fa-save"></i> diskette button to publish the created data entity.
+20. Click `OK`.
+
+<div class="alert alert-info">
+	<p>After creating the data entity, <a href="https://help.vtex.com/en/tutorial/creating-form-in-master-data--tutorials_1047">create the form for adding, changing, and displaying data in Master Data</a>.</p>
+</div>
diff --git a/docs/tutorials/en/data-subject-rights.md b/docs/tutorials/en/data-subject-rights.md
index 04f3eeb4f..3190c4672 100644
--- a/docs/tutorials/en/data-subject-rights.md
+++ b/docs/tutorials/en/data-subject-rights.md
@@ -3,8 +3,8 @@ title: 'Data subject rights'
 id: 6imchxTx09icupKMbzHVIM
 status: PUBLISHED
 createdAt: 2023-04-26T18:56:45.938Z
-updatedAt: 2023-04-27T12:43:48.560Z
-publishedAt: 2023-04-27T12:43:48.560Z
+updatedAt: 2023-06-22T21:47:26.569Z
+publishedAt: 2023-06-22T21:47:26.569Z
 firstPublishedAt: 2023-04-26T19:50:54.254Z
 contentType: tutorial
 productTeam: Others
@@ -50,7 +50,7 @@ To export data from the Master Data v1 through the Admin dashboard, follow these
 1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data.**
 2. Click the **Applications** tab.
 3. Click the view icon (on the right) of the desired data entity.
-![Master Data view button](https://images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/601df52aab81d94c5ad3afc75103fde3/visualizar_bot__o_master_data_EN.png)
+![Master Data view button](//images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/601df52aab81d94c5ad3afc75103fde3/visualizar_bot__o_master_data_EN.png)
 4. Use the [Master Data v1 filter](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) to filter only the data for the desired user. Use the `email` or `user ID` as the filter field.
 5. Click `Export XLS`.
 6. Select the `Select all fields` option.
@@ -133,7 +133,7 @@ Learn more about <a href="https://help.vtex.com/en/tutorial/configurar-carrinho-
 
 ## Erasure
 
-The right to erasure allows customers to request that their personal data be deleted from the platform.
+The right to erasure allows customers to request that their personal data be erased from the platform.
 
-If any customer requests to delete their data from your store, you can comply by following the [Deleting customer data](https://help.vtex.com/en/tutorial/exclusao-de-dados-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU) guide.
+If any customer requests to erase their data from your store, you can comply by following the [Erasing customer data](https://help.vtex.com/en/tutorial/exclusao-de-dados-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU) guide.
 
diff --git a/docs/tutorials/en/database-maintenance-full-cleanup.md b/docs/tutorials/en/database-maintenance-full-cleanup.md
index b6e53d05f..123ebc1d9 100644
--- a/docs/tutorials/en/database-maintenance-full-cleanup.md
+++ b/docs/tutorials/en/database-maintenance-full-cleanup.md
@@ -3,8 +3,8 @@ title: 'Database Maintenance (Full Cleanup)'
 id: 34P9LGs7BCIQK6acQom802
 status: PUBLISHED
 createdAt: 2018-02-07T14:32:22.879Z
-updatedAt: 2022-12-08T22:26:21.443Z
-publishedAt: 2022-12-08T22:26:21.443Z
+updatedAt: 2023-08-02T16:15:41.168Z
+publishedAt: 2023-08-02T16:15:41.168Z
 firstPublishedAt: 2018-02-07T16:44:48.971Z
 contentType: tutorial
 productTeam: Others
@@ -42,10 +42,6 @@ These are the operations available:
 
 - __Delete categories, brands, fields, and related items__: By deleting Categories, Brands, Fields, and related items, they will be permanently removed from your store. Before performing this operation, you must delete your Products and SKUs.
 
-<div class="alert alert-info">
-  <p>For cases where the <b>Delete Products/SKUs and related items</b> or <b>Delete categories, brands, fields, and related items</b> operation is performed and the store uses <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a>, please contact our <a href="https://support.vtex.com/hc/en-us/requests">Support team</a> to perform full database maintenance.</p>
-</div>
-
 - __Delete sellers and related items__: By deleting Sellers and related items, they will be permanently removed from your store.
 
 - __Schedule full reindexing__: When you reindex the database, your products enter an indexing queue. __The store’s products remain available for sale during the indexing process__. They enter a queue for data updates and remain available for purchase on the website. Warning: After clicking on __Reindex Database__, the process starts automatically.
diff --git a/docs/tutorials/en/declining-order-cancelation.md b/docs/tutorials/en/declining-order-cancelation.md
new file mode 100644
index 000000000..620bbd3d6
--- /dev/null
+++ b/docs/tutorials/en/declining-order-cancelation.md
@@ -0,0 +1,89 @@
+---
+title: 'Declining order cancelation'
+id: F2n0h1TeQ5td540Gjyff4
+status: PUBLISHED
+createdAt: 2023-09-21T02:29:56.663Z
+updatedAt: 2024-04-01T15:47:27.833Z
+publishedAt: 2024-04-01T15:47:27.833Z
+firstPublishedAt: 2023-09-21T16:08:07.567Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: declining-order-cancelation
+locale: en
+legacySlug: order-cancellation-denial
+subcategory: 2t00bBkcAwIkgSCGKsMOwY
+---
+
+There are many scenarios where canceling an order is necessary, whether on behalf of sellers, marketplaces, or customers. However, there are situations where canceling an order would bring significant financial loss to a seller so that the seller can decline an order cancellation request.
+
+The order flow has a [cancellation window](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) – or grace period – in which the customer can automatically cancel an order. Except for that period, the seller can decline an order cancellation request, regardless of whether the customer or the marketplace initiated it.
+
+> **Example:** A seller sells customizable products in a marketplace and a customer contacts the marketplace to cancel an order after the cancellation window. If the marketplace cancels the order, the seller would incur a financial loss since it would be hard to sell the customized product to another customer. Therefore, the seller chooses to decline the cancellation request.
+
+For developer’s content, see [Order canceling improvements](https://developers.vtex.com/docs/guides/order-canceling-improvements).
+
+<div class = "alert alert-info">
+In this article, the terms marketplace and seller refer to <a href="https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplace</a> and <a href="https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace">VTEX seller</a>. The decline cancellation request feature is not available for external sellers and marketplaces.
+</div>
+
+<div class = "alert alert-warning">
+Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
+</div>
+
+## Order cancellation declined diagram
+
+The following image shows the flow of declining an order’s cancellation request outside the cancellation window:
+
+![cancel_api_improvements_help_center_EN](//images.ctfassets.net/alneenqid6w5/6qU0tP4gQxa2qh6JLjleoK/abdfe44471ce04c695bc0b1c50463afb/cancel_api_improvements_help_center_EN.png)
+
+The description of each step is the following:
+
+1. The customer contacts the marketplace to cancel an order or does it via [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
+2. The marketplace sends a cancellation request to the seller. At this point, the [order status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) for the marketplace is `waiting for seller decision`.
+3. If the order is within the cancellation window, the order is automatically canceled, which is the platform’s default behavior. The next steps apply after the cancellation window is over.
+4. The seller receives the cancel order request and decides whether to accept it. The next steps apply when the seller decides not to cancel the order.
+
+  <div class="alert alert-danger">
+To decline an order cancellation request, the order status in the marketplace and seller must be the following:
+<ul>
+<li><b>Marketplace status:</b> waiting for seller decision.</li>
+<li><b>Seller status:</b> cancellation requested.</li>
+</ul>
+</div>
+
+5. The seller declines the order cancellation and notifies the marketplace.
+6. After the marketplace receives the declined request, the order moves on in the order workflow.
+
+## Declining an order cancellation request
+
+The request to cancel an order can be made by the marketplace, or by the customer via **My Account.** When made directly through [My account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), the customer receives a confirmation message that the request was successfully submitted.
+
+After that, the order will remain in the [order status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) `cancellation requested` for the marketplace and `waiting for seller decision` for the seller until the seller takes action, and accepts or declines the request.
+
+<div class="alert alert-warning">
+If within 30 days the seller takes no action regarding a cancellation order request, the order is automatically canceled by the VTEX platform.
+</div>
+
+To decline an order cancellation request via the VTEX Admin, follow the steps below:
+
+1. In the VTEX Admin, go to **Orders > All Orders**, or type [All Orders](https://help.vtex.com/en/tutorial/all-orders--2QTduKHAJMFIZ3BAsi6Pi) in the search bar at the top of the page.
+2. Select the desired order to access the [Order Details page](https://help.vtex.com/en/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl).
+3. At the top of the page, click `Decline`.
+
+  ![deny_cancel_request_EN](//images.ctfassets.net/alneenqid6w5/3TpCmA2PEdtVb5ru8Ed2va/253a91677769d1b3617f6a8714fc3603/deny_cancel_request_EN.png)
+
+4. Complete the **Cancellation Request** box with the reason why the cancel order request has been declined.
+
+  ![deny_cancel_request_reason_EN](//images.ctfassets.net/alneenqid6w5/5UUueX5kuj7OkBCHVhe0oL/022f068cefdd1e6588560d5bcba94ea3/deny_cancel_request_reason_EN.png)
+
+  <div class="alert alert-warning">
+Keep in mind that the message written in this field can be displayed to the customer via <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, or sent by the marketplace.
+</div>
+
+5. Click `Decline Request`.
+
+After that, the request to cancel order is declined, and the order moves on in the order workflow to the following status:
+
+- **For the marketplace:** `payment approved`.
+- **For the seller:** `ready for handling` or `handling`, depending on which was the status before the cancel request.
diff --git a/docs/tutorials/en/defining-mandatory-fields-in-master-data-v1-forms.md b/docs/tutorials/en/defining-mandatory-fields-in-master-data-v1-forms.md
new file mode 100644
index 000000000..de2a7b6d7
--- /dev/null
+++ b/docs/tutorials/en/defining-mandatory-fields-in-master-data-v1-forms.md
@@ -0,0 +1,30 @@
+---
+title: 'Defining mandatory fields in Master Data v1 forms'
+id: 3ufvQPc02Aybg7K1r1HADV
+status: PUBLISHED
+createdAt: 2022-10-17T19:47:22.675Z
+updatedAt: 2024-07-04T13:15:32.435Z
+publishedAt: 2024-07-04T13:15:32.435Z
+firstPublishedAt: 2022-10-17T19:50:55.489Z
+contentType: tutorial
+productTeam: Master Data
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: defining-mandatory-fields-in-master-data-v1-forms
+locale: en
+legacySlug: i-can-not-edit-a-required-field-on-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+To change the fields that appear as mandatory in the __Profile System__ of Master Data v1, follow the steps below:
+
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. Make sure that you are in the __Applications__ tab.
+3. Click on the gear <i class="fas fa-cog"></i> in __Profile System__.
+4. Click on the edit icon <i class="far fa-edit"></i> next to the form you want to configure.
+5. Click on __Layout Schemas__.
+6. Click on the edit icon <i class="far fa-edit"></i> in the line of the field you want to configure.
+7. In __Advanced Field Settings__, select __Required form field__.
+8. Click `OK`.
+9. Click `Save`.
+
+The option can be changed whenever necessary.
diff --git a/docs/tutorials/en/defining-window-displays.md b/docs/tutorials/en/defining-window-displays.md
index cd9ea4d9b..c94be10bb 100644
--- a/docs/tutorials/en/defining-window-displays.md
+++ b/docs/tutorials/en/defining-window-displays.md
@@ -27,25 +27,25 @@ After defining this, link the collection to the window display in **Storefront >
 
 In the example below, we will define a window display on the home page, and to do so the following layout has to be changed:
 
-![cms_layout_home ](https://images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
+![cms_layout_home ](//images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
 
 In the selected layout, add the control for the window display where you want to display the collection by clicking on **Add Object**
 After selecting the type of control you want, set its name and click **Adicionar** (Add)
 
 __Do not forget to click on the "Save Settings" button so that you can later edit the created control.__
 
-![ed](https://images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
+![ed](//images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
 
 ### Editing created control
 
 To edit your controls, click on the **pencil symbol**, as shown in the example image below:
 
-![banner_edit_cms](https://images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
+![banner_edit_cms](//images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
 
 When you editing the control you must add its contents by clicking **Add content**, which represent each set of items to be displayed.
 
-![cadastro_conteudo_cms ](https://images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
-![cadastro_conteudo_cms 2](https://images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
+![cadastro_conteudo_cms ](//images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
+![cadastro_conteudo_cms 2](//images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
 
 - **"Adicionar arquivo" (add file):** to select the collection that will be displayed in this content.
 - **Partner / Campaign / Source:** defines the display of this content if the visitor has a corresponding UTM in its source URL.
@@ -61,7 +61,7 @@ Check **Active Content** box and click on **Add content list**. Do not forget to
 
 If it is necessary to update the created content after saving it, just click on the second pencil symbol as shown below:
 
-![edit_content_cms](https://images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
+![edit_content_cms](//images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
 
 Click **Update Content List** after all changes were made and clicking on **Save Settings** afterwards.
 
diff --git a/docs/tutorials/en/deleting-a-category.md b/docs/tutorials/en/deleting-a-category.md
index 648c7d194..3f983c1dc 100644
--- a/docs/tutorials/en/deleting-a-category.md
+++ b/docs/tutorials/en/deleting-a-category.md
@@ -26,7 +26,7 @@ If you do not want to display a specific category to your customers, you can dea
 3. Select the category you want to deactivate.
 4. Click on the `Actions` button.
 5. Click on `Edit`.
-6. Uncheck the box that says __Active | Category is active on site__, as illustrated in the image below: ![img inativarcategoria EN](https://images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/b1056e64bedc8a7f495dde49b87b735e/img_inativarcategoria_EN.png)
+6. Uncheck the box that says __Active | Category is active on site__, as illustrated in the image below: ![img inativarcategoria EN](//images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/b1056e64bedc8a7f495dde49b87b735e/img_inativarcategoria_EN.png)
 7. Click on `Save`.
 
 ## Deleting all categories
diff --git a/docs/tutorials/en/deliveries-progress-vtex-shipping-network.md b/docs/tutorials/en/deliveries-progress-vtex-shipping-network.md
index 9b829ea0c..76eaadfe3 100644
--- a/docs/tutorials/en/deliveries-progress-vtex-shipping-network.md
+++ b/docs/tutorials/en/deliveries-progress-vtex-shipping-network.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Deliveries progress'
 id: 5CZRA0lq60EecmwZpsjvfq
 status: PUBLISHED
 createdAt: 2022-03-04T13:12:38.617Z
-updatedAt: 2023-06-09T12:56:36.259Z
-publishedAt: 2023-06-09T12:56:36.259Z
+updatedAt: 2024-03-04T21:51:37.046Z
+publishedAt: 2024-03-04T21:51:37.046Z
 firstPublishedAt: 2022-03-04T13:17:13.380Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/detaching-skus-by-specification.md b/docs/tutorials/en/detaching-skus-by-specification.md
new file mode 100644
index 000000000..ab84cc537
--- /dev/null
+++ b/docs/tutorials/en/detaching-skus-by-specification.md
@@ -0,0 +1,34 @@
+---
+title: 'Detaching SKUs by specification'
+id: 2q34xCKFuob941cOmz9Fx
+status: PUBLISHED
+createdAt: 2024-06-27T16:45:42.418Z
+updatedAt: 2024-06-27T16:47:01.429Z
+publishedAt: 2024-06-27T16:47:01.429Z
+firstPublishedAt: 2024-06-27T16:47:01.429Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: detaching-skus-by-specification
+locale: en
+legacySlug: detaching-skus-by-specification
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+On VTEX Intelligent Search, you can **Detach SKUs by specification**. This feature allows the store to determine the SKUs that will be displayed in search results.
+
+Previously, products were displayed in the search result without any distinction between them. So it was necessary to add each SKU as a single product for them to be displayed separately in the search result.
+
+Now this kind of workaround in the Catalog is no longer necessary. You can [configure the SKU specifications](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx) you want to display in the search directly in the Admin.
+
+This tool is useful for clothing stores as it allows you to display the products by color or material.
+
+See the following example of detaching SKUs by color. In the image below, the featured sandals are available in two different colors in the search results:
+
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+
+<div class="alert alert-info"><p>
+If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.</p></div>
+
+## Configuration
+To configure which attributes will be used to detach SKUs, see our [Search Settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#) article.
diff --git a/docs/tutorials/en/determine-the-minimum-number-of-items-in-a-cart.md b/docs/tutorials/en/determine-the-minimum-number-of-items-in-a-cart.md
index 1c19489c9..3f2aee8e9 100644
--- a/docs/tutorials/en/determine-the-minimum-number-of-items-in-a-cart.md
+++ b/docs/tutorials/en/determine-the-minimum-number-of-items-in-a-cart.md
@@ -1,10 +1,10 @@
 ---
 title: 'Is it possible to determine the minimum number of items in a cart?'
 id: 3rhoZXYon6aaGqusgOwukQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:41.366Z
-updatedAt: 2023-03-30T15:55:10.926Z
-publishedAt: 2023-03-30T15:55:10.926Z
+updatedAt: 2024-02-05T18:20:53.788Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:19.953Z
 contentType: tutorial
 productTeam: Shopping
@@ -12,16 +12,15 @@ author: 7FpKZ0rc6k4WqeymES80cw
 slug: determine-the-minimum-number-of-items-in-a-cart
 locale: en
 legacySlug: determine-the-minimum-number-of-items-in-a-cart
-subcategory: 3tDGibM2tqMyqIyukqmmMw
+subcategory: 
 ---
 
-Yes. By default, the minimum quantity of items in the cart is 1 item. However, you can change this value and specify the number that the store understands to be right for your business.
+By default, the minimum quantity of items in the cart is 1 item. However, it is possible to change this value and specify the number that the store believes is ideal for your business.
 
-If you change the number from 1 *(default)* to 2, this will prevent the customer from closing the purchase without having at least 2 items in the cart.
+For example, if you change the number from 1 *(default)* to 2, this will prevent the customer from completing the purchase without having added at least 2 items to the cart.
 
-__To change this number, follow the steps below: __
+To change the minimum quantity of items in the cart, follow the steps below:
 
-1. In the VTEX Admin, go to **Apps** > **Affiliates** > **Orders Management**, or type **Orders Management** in the search bar at the top of the page.
-2. Click on __Settings__.
-3. Set the value of the __Minimum number of items in cart__.
-4. Click the __Update__ button.
+1. In the VTEX Admin, access __Store Settings > Orders > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. On the __General__ tab, __Cart__ section, adjust the value of the __Minimum number of items in cart__ field as desired.
+3. Click `Save`.
diff --git a/docs/tutorials/en/direct-migration-magazine-luiza.md b/docs/tutorials/en/direct-migration-magazine-luiza.md
new file mode 100644
index 000000000..d565b3d5b
--- /dev/null
+++ b/docs/tutorials/en/direct-migration-magazine-luiza.md
@@ -0,0 +1,20 @@
+---
+title: 'Direct Migration Magazine Luiza'
+id: 6QRyRfi16YMVdPesThw3AA
+status: PUBLISHED
+createdAt: 2024-05-31T19:52:31.191Z
+updatedAt: 2024-05-31T21:02:13.878Z
+publishedAt: 2024-05-31T21:02:13.878Z
+firstPublishedAt: 2024-05-31T20:07:32.221Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: direct-migration-magazine-luiza
+locale: en
+legacySlug: direct-migration-magazine-luiza
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning">
+This content is exclusively regional; therefore, it does not apply to Spanish-speaking countries.
+  </div>
diff --git a/docs/tutorials/en/disable-cloudflare-proxy.md b/docs/tutorials/en/disable-cloudflare-proxy.md
index 2211ede9b..c20d5618b 100644
--- a/docs/tutorials/en/disable-cloudflare-proxy.md
+++ b/docs/tutorials/en/disable-cloudflare-proxy.md
@@ -23,7 +23,7 @@ To disable the CloudFlare proxy (and therefore disable CloudFlare's CDN and WAF
 
 If the proxy is enabled, the icon will be orange with the text **Proxied**. If it is disabled, the icon will be gray with the text **DNS Only**.
 
-![Cloudflare proxy configuration](https://images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/80ac72636596307b289d75cf6ca6c2fd/DNS_Management.png)
+![Cloudflare proxy configuration](//images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/80ac72636596307b289d75cf6ca6c2fd/DNS_Management.png)
 
 Please note that it may take a while to see the result of disabling the CloudFlare proxy, as it requires the cache to be refreshed.
 
diff --git a/docs/tutorials/en/displaying-the-store-in-another-language.md b/docs/tutorials/en/displaying-the-store-in-another-language.md
index d2f8dc56c..fac270534 100644
--- a/docs/tutorials/en/displaying-the-store-in-another-language.md
+++ b/docs/tutorials/en/displaying-the-store-in-another-language.md
@@ -17,7 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 In order to display your website in another language, a [new sales policy](/en/tutorial/configuring-a-marketplace-sales-policy/) must be created and assigned to the intended language through the __Culture Info__ field. 
 
-![exibição-loja-idioma-diferente en](https://images.ctfassets.net/alneenqid6w5/38da6HQyM0Sq2KaeoQUemC/0a14f342af87aaf865431e95a2ebad36/exibi____o-loja-outra-l__ngua_en.png)
+![exibição-loja-idioma-diferente en](//images.ctfassets.net/alneenqid6w5/38da6HQyM0Sq2KaeoQUemC/0a14f342af87aaf865431e95a2ebad36/exibi____o-loja-outra-l__ngua_en.png)
 
 With the sales policy already created, you will need to adjust the front-end of the store to enable changing the language and, consequently, the trade policies. 
 To do so, you must define that for each language the URL must include the parameter `?sc=salespolicyid`, changing the __salespolicyid__ value for the sales policy Id that was set up and assigned to the desired language. 
diff --git a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
new file mode 100644
index 000000000..ebe8f97ac
--- /dev/null
+++ b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -0,0 +1,85 @@
+---
+title: 'Displaying VTEX Ad Network ads in your store (Beta)'
+id: 6gWgZrMLcS5FDFFdl5LETA
+status: CHANGED
+createdAt: 2024-04-23T18:51:12.785Z
+updatedAt: 2024-07-05T13:10:03.749Z
+publishedAt: 2024-07-05T13:05:44.686Z
+firstPublishedAt: 2024-04-23T19:13:52.053Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: displaying-vtex-ad-network-ads-in-your-store-beta
+locale: en
+legacySlug: displaying-vtex-ad-network-ads-in-your-store-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>VTEX Ad Network is in beta, which means that we are working to improve. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
+</div>
+
+With [VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), VTEX stores can offer ad space in their stores for brands to promote products. VTEX will select ads for products already in your catalog, and your store will receive a fee for each ad click in your store.
+
+To become a part of the VTEX Ad Network and start displaying ads in your store, install the VTEX Ad Network for stores app.
+
+<div class="alert alert-warning">
+Currently, VTEX stores can only offer ad space on stores using <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
+</div>
+
+## Monitoring results
+
+On the initial screen of the [VTEX Ad Network for stores app](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#merchants), you can monitor the results of ads in your store.
+
+![vtex_ad_network_admin_EN](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/434685bba26278166e6b5192a7b198d1/vtex_ad_network_admin.png)
+
+At the top of the page, you'll find aggregated data:
+
+- **Total Budget Spend:** Amount spent by brands on ads displayed in your store.
+- **Ad Sales:** Total sales revenue from ads displayed in your store.
+- **Revenue:** Total amount received by your store from ads.
+
+Below, there's a table with details on each campaign that has been or can be displayed in your store:
+
+- **Duration:** Duration of the campaign so far.
+- **Impressions:** Number of times ads were displayed on the page.
+- **Views:** Number of times ads were viewed. VTEX Ad Network considers it a view when there is an ad impression and, if necessary, the user scrolls down the page to view the ad.
+- **Clicks:** Number of clicks on ads.
+- **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views.
+- **Orders:** Number of orders resulting from clicks on ads.
+- **Units Sold:** Number of product units sold from ads in this campaign.
+- **Ad Sales:** Total sales revenue from ads displayed in your store.
+- **ROAS:** Return on investment for advertising that campaign in your store.
+- **Budget Spent:** Campaign budget spent in your store.
+
+You can also use the filters available at the top of the table:
+
+- **Search campaign:** Filter campaigns by name.
+- **Status:** Select whether you want to see active or inactive campaigns.
+- **Advertisers:** View data related to the campaigns of a specific advertiser.
+
+### Viewing more details by campaign and product
+
+In the table on the initial screen of the [VTEX Ad Network for stores app](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#merchants), you can click the campaign row to see more details:
+
+![vtex_ad_network_details_EN](//images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/b81424e85fc704593e7f5bb86bf55409/vtex_ad_network_details.png)
+
+- **Views/Clicks:** Ad views and clicks.
+- **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views.
+- **Budget Spent:** Amount spent so far.
+- **ROAS:** Return on advertising spend.
+- **Revenue:** Sales revenue generated from ads.
+
+You'll find a table below the aggregated data detailing each product's performance in that campaign:
+
+- **CPC:** Cost per click. This is the amount paid by the advertiser for each ad click.
+- **Impressions:** Number of times ads were displayed on the page.
+- **Views:** Number of times ads were viewed. VTEX Ad Network considers it a view when there is an ad impression and, if necessary, the user scrolls down the page to view the ad.
+- **Clicks:** Number of clicks on ads.
+- **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views.
+- **Orders:** Number of orders resulting from clicks on ads.
+- **Units Sold:** Number of product units sold from ads in this campaign.
+- **Ad Sales:** Total sales revenue for that product generated from ads.
+- **ROAS:** Return on advertising spend.
+- **Budget Spent:** Campaign budget spent on that product in your store.
+
diff --git a/docs/tutorials/en/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md b/docs/tutorials/en/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
new file mode 100644
index 000000000..738bcc99e
--- /dev/null
+++ b/docs/tutorials/en/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
@@ -0,0 +1,41 @@
+---
+title: 'DPAN and FPAN: Understanding security in the online tokenized payment flow'
+id: 3RM7RvhKZ057wja5xVEOqb
+status: PUBLISHED
+createdAt: 2023-06-19T16:55:51.107Z
+updatedAt: 2023-06-26T13:27:44.965Z
+publishedAt: 2023-06-26T13:27:44.965Z
+firstPublishedAt: 2023-06-19T17:10:43.124Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow
+locale: en
+legacySlug: dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow
+subcategory: 
+---
+
+A token is a digital representation of a physical asset with commercial value. In the payment context, tokenization is a security procedure that allows you to protect sensitive customer data when processing credit cards, debit cards, or digital wallet transactions, such as Apple Pay, Google Pay, and Samsung Pay.
+
+First, you need to understand the following information related to a card:
+
+- **PAN (Primary Account Number)**: The number printed on the front or back of a debit or credit card used to identify an account holder and their issuing financial institution. It consists of 14 to 19 digits.
+
+- **DPAN (Device Primary Account Number)**: Tokenized version of the PAN used in mobile payments or digital wallets. This number is linked to the user's mobile device (smartphone, smartwatch, tablet) and the cardholder account.
+
+- **FPAN (Funding Primary Account Number)**: Account ID to which the amount paid in a payment transaction will be charged, used exclusively when the purchase is made through digital wallets or services that allow more than one payment method at the same time, such as different credit or debit cards or bank accounts.
+
+Below is an example of a payment flow using tokens:
+
+1. The customer enters the card information on a website, app, or machine or uses a digital wallet to pay for an order.
+
+2. The payment provider or digital wallet system sends a request to the financial institution that issued the card, asking them to create a token to represent the PAN.
+
+3. The bank generates the token (DPAN) and forwards it to the payment provider or digital wallet system. The PAN remains recorded only in the bank system.
+
+4. During transaction processing, the payment provider sends the DPAN to the bank, requesting authorization for the transaction. When applicable, the FPAN is also generated and forwarded for transaction authorization.
+
+5. The bank checks the relationship between the DPAN and PAN and authorizes the payment. If the FPAN is used, the bank will verify that the FPAN is valid and that the funding source (account) has enough funds before authorizing the payment.
+
+6. The transaction is completed, and the merchant receives the payment confirmation. The physical card data (PAN) is not shared with the merchant or any third party, reducing the risk of fraud.
+
diff --git a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
new file mode 100644
index 000000000..cd88db022
--- /dev/null
+++ b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
@@ -0,0 +1,76 @@
+---
+title: '​​Dynamic relevance in Intelligent Search (Beta)'
+id: rFaW7JPnBKNDBFzMxpBn8
+status: PUBLISHED
+createdAt: 2023-09-01T17:14:43.241Z
+updatedAt: 2024-01-05T17:24:55.378Z
+publishedAt: 2024-01-05T17:24:55.378Z
+firstPublishedAt: 2023-09-01T18:59:54.853Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: dynamic-relevance-in-intelligent-search-beta
+locale: en
+legacySlug: dynamic-relevance-in-intelligent-search-beta
+subcategory: 23WdCYqmn2V2Z7SDlc14DF
+---
+
+<div class="alert alert-info">
+  <p>This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>.</p>
+  <p>For selected customers, the functionality is available for free use in the VTEX Admin during its Beta period, or until decided by VTEX. Extra fees may apply in the future.</p>
+</div>
+
+Relevance is the feature that defines the ranking of products in search results. This configuration allows you to set weights and prioritize certain criteria, such as popularity, release date, and participation in promotions. Intelligent Search determines the relevance of each product by combining weights and priorities defined by each merchant.
+
+In Intelligent Search, you can configure your search relevance in two ways:
+
+* [Manually](#manual-relevance)
+* [Dynamically](#dynamic-relevance)
+
+Only one of these is applied to your store at a time, and you can [change the relevance type configured](#changing-relevance-type). If you change the relevance from manual to dynamic, all the manual rules you have set will remain saved.
+
+<div class = "alert alert-info">
+Manual relevance is the store default setting.
+</div>
+
+## Manual relevance
+
+Manual relevance is configured by distributing the weights on the **Relevance Rules** page. To enable manual relevance, follow the steps below:
+
+1. In the VTEX Admin, go to **Storefront > Intelligent Search >** **Relevance Rules** or type **Relevance Rules** in the search bar at the top of the page.
+2. Select the **Manual Relevance** option.
+![relevancia-manual-en](//images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/c66c5e883e20fd0711400e63d9a18423/image.png)
+3. Click `Save`.
+
+To configure manual relevance, see the [Relevance](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) article.
+
+## Dynamic relevance
+
+Dynamic relevance is a VTEX feature that uses artificial intelligence to find patterns in customer behavior based on their searches and the result rankings they click or buy. It can improve search results by increasing the relevance of products that are growing in popularity.
+
+For example, dynamic relevance can identify which products increase conversion on a new arrivals page, without any configuration by the merchant.
+
+It can also reposition results that are not relevant to your customers within a specific search.
+
+To enable dynamic relevance, follow these steps:
+
+1. In the VTEX Admin, go to **Storefront > Intelligent Search > Relevance Rules** or type **Relevance Rules** in the search bar at the top of the page.
+2. Read the information about dynamic relevance and click `Next`.
+3. Select the **Dynamic Relevance** option.
+![relevancia-dinamica-en](//images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/75b719ed30b77a99b0f9c9a5d7a62371/image.png)
+4. Click `Save`.
+5. Wait for the loading bar to reach 100%. This process may take a few hours. You will receive an email when the loading is complete.
+6. Click `Enable`.
+
+## Changing relevance type
+
+To change the relevance type, follow the steps below:
+
+<div class = "alert alert-warning">
+We do not recommend constantly changing the relevance type used by your store. The system needs a week to settle.
+</div>
+
+1. In the VTEX Admin, go to **Storefront > Intelligent Search > Relevance Rules** or type **Relevance Rules** in the search bar at the top of the page.
+2. Click `Change`.
+3. Choose the type of relevance you want to apply.
+4. Click `Save`.
diff --git a/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md b/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md
index 6374b90d8..a6ea37e99 100644
--- a/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md
+++ b/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md
@@ -1,10 +1,10 @@
 ---
-title: 'Edit a required field on Profile System of Master Data'
+title: 'Editing a required field on Profile System of Master Data'
 id: 3Kat18isG7ZQptlLusUKnj
 status: PUBLISHED
 createdAt: 2019-03-29T14:18:37.284Z
-updatedAt: 2023-03-28T23:00:24.414Z
-publishedAt: 2023-03-28T23:00:24.414Z
+updatedAt: 2024-06-19T14:27:27.495Z
+publishedAt: 2024-06-19T14:27:27.495Z
 firstPublishedAt: 2019-03-29T15:48:22.604Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: edit-a-required-field-on-profile-system-of-master-data
 subcategory: 42hDtnYXHw5ExG6l19RP1l
 ---
 
-Master Data is a module within VTEX's platform used for safeguarding and organizing client data. Find out how to edit a field, making it mandatory or not, by using the Profile System feature. 
+Master Data is a module of the VTEX platform used to store and organize documents. Find out how to make a form field mandatory in Master Data in the instructions below.
 
 <div class="alert alert-warning">
 This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
@@ -36,12 +36,13 @@ Master Data v2
 The following steps will allow you to select a field and make it mandatory:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. Make certain that you're in the Applications tab, in __Quick Links__.
-3. Select the __gears__ icon in __Profile System__. ![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
-4. Click on the __pencil__ next to the item you wish to configure. ![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
-5. Click on __Layout Outlines__.
-6. In __Section 1__, choose the item of the field you wish to configure.
-7. In __Advanced field settings, select __Mandatory Field__ on the form. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
-8. Click on __ok__.
+2. Make sure that you are in the __Applications__ tab.
+3. Click the gear icon <i class="fas fa-cog"></i> in __Profile System__.
+4. Click on the pencil icon <i class="fas fa-edit"></i> next to the form you wish to configure.
+5. Click on __Layout Schemas__.
+6. Within one of the form sections, find the field you wish to configure and click <i class="fas fa-edit"></i> next to it to open the __Advanced Field Settings__.
+7. In __Advanced Field Settings__, select __Required form field__.
+8. Click `OK`.
+9. Click `Save`.
 
-You're done. From now on, the selected options will need to be, without fail, filled out on the store page. The above may be changed whenever it may be necessary. 
+From now on, the selected options will be mandatory in the form. The settings above can be changed if necessary. 
diff --git a/docs/tutorials/en/enable-checkout-v6.md b/docs/tutorials/en/enable-checkout-v6.md
index acd779806..f59086000 100644
--- a/docs/tutorials/en/enable-checkout-v6.md
+++ b/docs/tutorials/en/enable-checkout-v6.md
@@ -28,7 +28,7 @@ To update your store's checkout to the latest version (Checkout v6), you must en
 5. Click `Save`.
 6. [Access your store in beta/test environment](/tutorial/access-beta-environment-through-myvtex-com-domain--3BHM289568gcSwk2O80Asu) and implement the necessary style adjustments. Checkout v6 has new _CSS_ classes that you need to be mindful of when performing style customizations.
 
-![Checkoutv6_box](https://images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/f185469ae22029d00f5d19f3b6a8cf1b/CheckoutV6_box_EN.png)
+![Checkoutv6_box](//images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/f185469ae22029d00f5d19f3b6a8cf1b/CheckoutV6_box_EN.png)
 
 ## Activate Checkout v6 in Production Environment
 
@@ -42,7 +42,7 @@ After the necessary adjustments are completed, you can activate Checkout v6 in t
 
 After this step, Checkout v6 would be installed in your store.
 
-![checkoutv6_box_2](https://images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/f38745c904dfcb233ec0b09d3c01b2a2/CheckoutV6_box2_EN.png)
+![checkoutv6_box_2](//images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/f38745c904dfcb233ec0b09d3c01b2a2/CheckoutV6_box2_EN.png)
 
 ## How to ascertain whether Checkout v6 was properly installed?
 
diff --git a/docs/tutorials/en/enabling-2-factor-authentication-login.md b/docs/tutorials/en/enabling-2-factor-authentication-login.md
index d3e8b141e..0afd79c66 100644
--- a/docs/tutorials/en/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/en/enabling-2-factor-authentication-login.md
@@ -3,8 +3,8 @@ title: 'Enabling two-factor authentication login'
 id: 4Ae1fcQi12g8u4SkQKCqWQ
 status: PUBLISHED
 createdAt: 2017-11-09T00:46:29.023Z
-updatedAt: 2023-02-08T14:28:53.895Z
-publishedAt: 2023-02-08T14:28:53.895Z
+updatedAt: 2024-03-12T17:52:28.500Z
+publishedAt: 2024-03-12T17:52:28.500Z
 firstPublishedAt: 2017-11-09T13:09:54.237Z
 contentType: tutorial
 productTeam: Identity
@@ -17,8 +17,6 @@ subcategory: 4sY1T2qdFehvVmC0tL5xW3
 
 Two-Factor Authentication (2FA) is an authentication method that dramatically increases the security of your store's login.
 
-![EN- LoginAdmin](https://images.ctfassets.net/alneenqid6w5/2POUjooORqKWz4aeLhLtFa/4eaa5520fd10ef3a172cd592756e7698/EN-_LoginAdmin.png)
-
 During the login process, in addition to email and password, the system asks for an extra key (which, in VTEX's case, can be either an SMS or an app generated code).
 
 Since this key is generated at login and quickly expires, it becomes almost impossible for someone to access your store using your credentials without authorization. Without 2FA, someone would only need your email and password to have full access to your store's account.
@@ -36,7 +34,7 @@ There are two authentication options:
 - Using a key that's generated by an authentication app.
 - Using a key sent by __SMS__.
 
-![2FA - Select - EN](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
+![2FA - Select - EN](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
 
 <div class="alert alert-danger">
 We strongly recommend that you <strong>choose the app authentication option</strong>, since, with SMS authentication, you will depend on your network provider. By using an app, you can generate an access key whenever you need it.
@@ -49,14 +47,15 @@ If you chose 2FA through SMS, and the SMS code doesn't appear, your network oper
 ### Enabling 2FA through an app
 
 To use the key generated by the authentication app:
+
 1. Download the __Google Authenticator__ app ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)).
-  ![2FA - App Download - EN](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
+  ![2FA - App Download - EN](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
 2. Use the application to scan the QR Code with your cell phone's camera.
-   ![mfa qr code](https://images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/ec1e00707e20e7f6ab295123c71f9c0d/mfa_qr_code_correction_en.jpg)
+   ![mfa qr code](//images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/ec1e00707e20e7f6ab295123c71f9c0d/mfa_qr_code_correction_en.jpg)
 3. Your VTEX account will be added to the application, and a 6-digit code will be displayed. Enter the code to complete your login.
 
   *The app code is updated periodically. No need to memorize it; access the app whenever you need an access code.*
-  ![2FA - App Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
+  ![2FA - App Insert Code - EN](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
 
 <div class="alert alert-info">
 If you log in with your email and password on the same computer, the access key will be requested <strong> every three days</strong>. When this happens, check the code in the application.
@@ -68,11 +67,11 @@ To use a key sent by SMS:
 
 1. Enter your cell phone number to receive the code by SMS - do not forget to enter the country and area code.
 
-  ![2FA - SMS Insert Phone - EN](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
+  ![2FA - SMS Insert Phone - EN](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
 
 2. You will receive a text message from VTEX on the given cell phone. Enter the 6-digit key to finish your login.
 
-   ![2FA - SMS Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
+   ![2FA - SMS Insert Code - EN](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
 
 <div class="alert alert-warning">
 We cannot guarantee that your network operator will be able to deliver the access key whenever necessary. If the text message does not arrive, try resending the code or <a href="#habilitate-o-2fa-per-application" >enable 2FA through the application</a>.
@@ -88,10 +87,10 @@ To change the verification settings, follow these two steps:
 
 1. Access your user settings by clicking on the circle with your initials on the top-right corner of the Admin.
 
-  ![2FA - User Initials - EN](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
+  ![2FA - User Initials - EN](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
 
 2. Click on **2-step verification** to see the settings.
 
-  ![2FA - My User - EN](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
+  ![2FA - My User - EN](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
 
 3. You can then change the settings by following similar steps, as shown in the sections above, to enable 2FA through [SMS](#enable-o-2fa-by-sms) and [application](#enable-o-2fa-by-application). 
diff --git a/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
index 19790a613..90782d150 100644
--- a/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Enabling 3DS2 for Redsýs V2 integration'
 id: 1ixji2XORg9p0UoW8gBtUG
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-08T14:53:08.780Z
-updatedAt: 2023-03-23T15:42:17.139Z
-publishedAt: 2023-03-23T15:42:17.139Z
+updatedAt: 2024-03-18T19:54:47.084Z
+publishedAt: 
 firstPublishedAt: 2021-03-08T16:29:32.443Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: enabling-3ds2-for-redsys-v2-integration
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 The 3DS2 feature is now available for payments made with credit cards and processed by the [Redsýs](https://help.vtex.com/en/tutorial/configurar-gateway-redsys--7xRnMyzZS0kQoIG2ISagY8) payment gateway.
 
 3DS2 is a security solution that requires cardholder authentication in the issuing bank, ensuring greater security for your online transactions. 
@@ -33,7 +35,7 @@ In this tutorial, you will learn how to add the 3DS2 authentication to the Reds
 4. Scroll down the screen and select __Yes__ for the __3DS Enabled__ option.
 5. Click on __Save__.
 
-![RedsysV2 EN](https://images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/d1671b87629fbc5d59dd8c0298f9a90f/Redsys_3DS2_-_EN.png)
+![RedsysV2 EN](//images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/d1671b87629fbc5d59dd8c0298f9a90f/Redsys_3DS2_-_EN.png)
 
 It’s done! Now the solution is enabled for Redsýs’s transactions with credit cards.
 
diff --git a/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
index dbedf9b2f..0ef0f67ad 100644
--- a/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -77,7 +77,7 @@ You will need to select a sales associate from the store where you want to test
 1. With a [sales associate selected](https://help.vtex.com/en/tutorial/vendedores-instore-beta--4rzit1pzp28km4HSDEdrEC), open Sales App and log in.
 2. Search for an item that exists in the franchise account warehouse. The item should display the available quantity that corresponds to the seller inventory.
 
-![instore-pdp-en](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/064cb3f0b499da4533cacdbea0fee4eb/image.png)
+![instore-pdp-en](//images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/064cb3f0b499da4533cacdbea0fee4eb/image.png)
 
 <div class="alert alert-info">
 <p>If you enabled Infinite inventory, the item quantity will display as a number greater than one million, which can't be changed when a sale is completed.</p>
@@ -92,9 +92,9 @@ You can also enable On Hands to ignore stock quantity and force item availabilit
 2. Click the gear <i class="fas fa-cog"></i> button to edit.
 3. Select the **Code** tab.
 4. In the side tab, select the `checkout-instore-custom-js` file.
-![instore-custom-js-en](https://images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/45e6d1e73997a0ff4a4872fdc502a17c/image.png)
+![instore-custom-js-en](//images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/45e6d1e73997a0ff4a4872fdc502a17c/image.png)
 5. In the `window.INSTORE_CONFIG` key, add the `sellWithoutStockInHands: true` flag.
-![sellWithoutStockInHands-en](https://images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/642bf1e6d79d00ce46275ac1924d03c0/image.png)
+![sellWithoutStockInHands-en](//images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/642bf1e6d79d00ce46275ac1924d03c0/image.png)
 6. Click <i class="fas fa-save"></i> `Save`.
 
 ## Enabling mixed cart sales (optional)
diff --git a/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md b/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md
index 05909ca23..5baec9caf 100644
--- a/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md
+++ b/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md
@@ -16,7 +16,7 @@ subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
 All VTEX IO stores natively have a Progressive Web App (PWA) at their disposal. A PWA is a web app used to natively promote beneficial features to users, such as offline functionalities or a home screen icon.
-![pwa-noticeen](https://images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/f47f6817eb995c32b186be1ebd320300/Screenshot_162.png)
+![pwa-noticeen](//images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/f47f6817eb995c32b186be1ebd320300/Screenshot_162.png)
 The PWA can be made available for installation in three distinct moments of users’ browsing experience: during their first visit to your store's website, when adding the first item to the shopping cart, or when completing their first purchase.
 To configure the prompt in your store, follow the steps below.
 
diff --git a/docs/tutorials/en/entering-tax-receipts-in-the-order.md b/docs/tutorials/en/entering-tax-receipts-in-the-order.md
index a0c630e73..a4aa3847e 100644
--- a/docs/tutorials/en/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/en/entering-tax-receipts-in-the-order.md
@@ -19,7 +19,7 @@ Entering the tax receipt in the order is a mandatory step so that the status bec
 
 To do this manually using the **Orders management**,  click on the `Invoice package` button, as shown in the image below.
 
-![faturar-pedido-ex en](https://images.ctfassets.net/alneenqid6w5/3xGII9E1x6Iogai8qYyWYw/d50b5a145891ac1766882dabdf35a371/ex_1_en.png)
+![faturar-pedido-ex en](//images.ctfassets.net/alneenqid6w5/3xGII9E1x6Iogai8qYyWYw/d50b5a145891ac1766882dabdf35a371/ex_1_en.png)
 
 Once the tax receipt is entered with the total amount of the order, the status changes to **Invoiced**.
 
diff --git a/docs/tutorials/en/erasing-customer-data.md b/docs/tutorials/en/erasing-customer-data.md
new file mode 100644
index 000000000..555c4e4a9
--- /dev/null
+++ b/docs/tutorials/en/erasing-customer-data.md
@@ -0,0 +1,65 @@
+---
+title: 'Erasing customer data'
+id: 1R9Fn7A06Ifj4R9YD4JTKU
+status: PUBLISHED
+createdAt: 2022-04-14T13:28:53.209Z
+updatedAt: 2023-06-23T15:06:52.315Z
+publishedAt: 2023-06-23T15:06:52.315Z
+firstPublishedAt: 2022-04-14T13:50:08.688Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: erasing-customer-data
+locale: en
+legacySlug: deleting-customer-data
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+According to data protection policies, such as [GDPR and LGPD](https://vtex.com/us-en/privacy-and-agreements/vtex-commitment/), companies using customer personal data are required to delete collected information upon the customer's request. This means that VTEX allows you to request the erasure of data collected from your store's customers. 
+
+## Before submitting a data erase request
+
+Before [submitting a data erase request via Support](#request-erasure-via-support), you need to check which Master Data entities store customer data in your operation.
+
+You must be careful not to erase any data from the [native Master Data entities](#native-master-data-entities). However, you must manually erase customer information stored in [other Master Data entities](#other-data-entities), in case your store keeps any of it. You can find more details about this below.
+
+### Native Master Data entities
+
+Upon your [request via Support](#request-erasure-via-support), VTEX will delete the data from the native **CL** and **AD** data entities. You should not delete data from these entities.
+
+### Other data entities
+
+If your store keeps customer information in other data entities, you need to manually delete this data before requesting the data erasure via Support. Use the Master Data API:
+
+1. Search for the document with the [Search Document](https://developers.vtex.com/vtex-rest-api/reference/searchdocuments-1) endpoint
+
+2. Use a [Delete Document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1) request
+
+<div class="alert alert-danger"> 
+  Do not do this for the <b>CL</b> and <b>AD</b> entities.
+</div> 
+
+## Request erasure via support
+
+You must request the erasure of your customers' personal data from VTEX platform by opening a ticket with the [VTEX Support](https://help.vtex.com/en/support).
+
+To request the deletion of customer personal data, follow the steps below.
+
+1. Access the [VTEX Support](https://help.vtex.com/en/support).
+2. Fill in your full name in the **Name** field and in the **Store** field select the name of the store you want to open the ticket for.
+3. Click the `Continue` option.
+4. Select the `Technical` option.
+5. In the **Problem type** field, select `I would like to request a setup`.
+6. In the **Subject of the request** field, fill in the following information:
+   * Data Subject Request
+   * VTEX accounts
+   * Email linked to VTEX accounts whose data must be erased
+7. In the field **Your experience with the platform**, select the option that corresponds to your experience as a user of the VTEX platform.
+8. Fill in the **Describe what happened in detail** field with details of your request.
+9. Click `Submit`.
+
+<div class="alert alert-warning">
+Please request the erasure of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
+</div>
+
+Your request will be sent to our support team. Upon completion of the ticket, a certificate will be issued to the email where the ticket was opened confirming the completion of the erasure of the data.
diff --git a/docs/tutorials/en/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md b/docs/tutorials/en/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
new file mode 100644
index 000000000..daffc97f4
--- /dev/null
+++ b/docs/tutorials/en/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
@@ -0,0 +1,44 @@
+---
+title: 'Error when trying to import SKUs via spreadsheet in the VTEX Admin'
+id: 1TDF87s7P1UJT1hNDGZsuk
+status: PUBLISHED
+createdAt: 2024-07-01T15:07:50.982Z
+updatedAt: 2024-07-22T18:56:05.856Z
+publishedAt: 2024-07-22T18:56:05.856Z
+firstPublishedAt: 2024-07-01T18:24:23.096Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin
+locale: en
+legacySlug: error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+
+**Product tags:** *Catalog*, *SKU*
+
+**Keywords:** *catalog, sku, spreadsheet, import*
+
+After setting the category tree and adding [product specifications and SKUs](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP#product-specification) to your store, you must complete the values for the specifications you created. In the VTEX Admin, you can do this process manually or using a spreadsheet when [adding products and SKUs](https://help.vtex.com/en/tutorial/adding-sku-specifications-or-fields--tutorials_119).
+If you get the message `"An error occurred in the data writing process. Make sure your worksheet data is consistent with the instructions and try again."` when importing SKUs via spreadsheet, this may be due to:
+
+- [Incomplete mandatory SKU specifications.](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
+
+- Incorrect file formatting.
+
+## Solution 
+You can solve this problem by:
+
+- [Changing the file](#solution-changing-the-file): The file must follow specific formatting rules and be saved as an XML spreadsheet in .xls format.
+
+### Solution  - Changing the file
+
+1. In the VTEX Admin, go to **Catalog > Import and Export > All Products > Export / Import** and click the **Import** tab.
+2. Click `Click Here` to download the spreadsheet template.
+3. Edit the spreadsheet template with the SKUs you want, following all the recommendations on the [Import and Export](https://cosmetics2.myvtex.com/admin/Site/Relatorio_Skus.aspx) page.
+4. Save the spreadsheet in `.xls` format.
+5. On the same page, under `Upload Import File`, select the file and click `Import`.
+
+If the error persists after changing the file, please contact our [Support](https://support.vtex.com/hc/pt-br/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests) team.
+
diff --git a/docs/tutorials/en/events-available-in-audit.md b/docs/tutorials/en/events-available-in-audit.md
index 1ac1a0826..fec04100d 100644
--- a/docs/tutorials/en/events-available-in-audit.md
+++ b/docs/tutorials/en/events-available-in-audit.md
@@ -3,12 +3,12 @@ title: 'Events available in Audit'
 id: 6r1Mzcu5NmkmmDLJlz9CCZ
 status: PUBLISHED
 createdAt: 2022-06-22T16:05:16.214Z
-updatedAt: 2023-04-25T14:51:35.871Z
-publishedAt: 2023-04-25T14:51:35.871Z
+updatedAt: 2024-06-28T18:16:11.762Z
+publishedAt: 2024-06-28T18:16:11.762Z
 firstPublishedAt: 2022-06-22T16:28:52.801Z
 contentType: tutorial
 productTeam: Master Data
-author: 2Gy429C47ie3tL9XUEjeFL
+author: 1malnhMX0vPThsaJaZMYm2
 slug: events-available-in-audit
 locale: en
 legacySlug: events-available-in-audit
@@ -17,659 +17,228 @@ subcategory: 2TNXiKzLZOPxjMTyGiEeJu
 
 Below, you will find a list of the potential events available in [Audit](https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA#) for each app.
 
+* [OMS](#oms)
+* [Orders](#orders)
+* [Order Authorization](#order-authorization)
+* [Inventory & Shipping](#inventory-shipping)
+* [Catalog (Admin)](#catalog-admin)
+* [Catalog (API)](#catalog-api)
+* [Prices](#prices)
+* [Promotions](#promotions)
+* [Subscriptions](#subscriptions)
+* [Wallets](#wallets)
+* [Gift Card](#gift-card)
+* [Checkout](#checkout)
+* [Portal CMS](#portal-cms)
+* [License Manager](#license-manager)
+* [VTEX ID](#vtex-id)
+* [Headless CMS](#headless-cms)
+* [Seller Management](#seller-management)
+
 <div class = "alert alert-info">
-In case you encounter an event in Audit which has not been included in this list, please contact us through the <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">documentation feedback page</a>.
+In case you encounter an event in Audit which has not been included in this list, please inform us through the <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">documentation feedback page</a>.
 </div>
 
 <div class="alert alert-warning">
-In the Audit filter options, you can find the <code>Profile System</code> option and the applications mentioned below. As this option refers to features in closed beta, most accounts will not have events associated with them.
+<p>In the Audit filter options, you can find <strong>Shipping Options</strong>, <strong>Profile System</strong>, and <strong>Billing</strong> options besides the applications listed in this guide. Since these options refer to internal resources or features in closed beta, most accounts will not have events associated with them.</p>
 </div>
 
-## Catalog admin
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Product Activation
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Product activation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Product ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Product Commercial Condition Change
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in product commercial condition.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Product ID and changed list of conditions.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Attachment Association    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Attachment Association.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">SKU ID, name and attachment ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Archive Upload    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File delivery.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File name.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Field Activation    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Catalog field activation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Field name, ID and status.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Binding    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">SKU and seller binding.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Seller’s ID, SKU ID in seller’s catalog and SKU ID in the marketplace catalog.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Unbinding
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Removal of SKU and seller binding.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Seller’s ID, SKU ID in seller’s catalog and SKU ID in the marketplace catalog.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Removal
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Removal of seller SKU.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">SKU ID in seller’s catalog.
-   </td>
-  </tr>
-</table>
-
-## Pricing
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Put Price
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation or change of a SKU price.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">SKU ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Price Table
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation or change of a price table.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identifies the created or changed table.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Price Tables
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation or change of multiple price tables.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identifies the created or changed tables.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Price Deleted
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Deletion of a SKU price.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">SKU ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Config
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation or change of price settings.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identifies the created or changed configuration.
-   </td>
-  </tr>
-
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Fixed Price Modified
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change of fixed price.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identification of the fixed price changed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Put Catalog Step
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation or change of a price rule.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Price rule created or changed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Deleted Fixed Prices From Table
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Deletion of fixed price from the related price table.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identification of the table and the deleted price.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Compatibility Post Prices
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change of price using the compatibility API with the PricingV1 contract
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identification of the changed price.
-   </td>
-  </tr>
-</table>
-
-## Logistics
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier creation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier update.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier deletion.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Loading dock creation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Loading dock ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Loading dock update.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Loading dock ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Loading dock deletion.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Loading dock ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse creation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse update.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse deletion.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Pickup Point Save
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Pickup point creation or change.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Pickup point ID.
-   </td>
-  </tr>
-</table>
-
 ## OMS
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Start Handling
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Informs VTEX that the store has started handling an order. This helps order workflow.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Order ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Status
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Changes order status.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Order ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Payment Notification
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sends payment notification of certain orders.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Order ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Changes price module settings.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Short description of the change.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resend Last Email
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Resends the last email related to the order in the Message Center.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Order ID.
-   </td>
-  </tr>
-</table>
+| Action | Event description | Event details |
+|---|---|---|
+| Start Handling | Informs VTEX that the store has started handling an order. This helps order workflow. | Order ID. |
+| Change Status | Change in order status. | Order ID. |
+| Shipping Notification  | Shipping notification of a certain order.  | Order ID.  |
+| Payment Notification | Payment notification of a certain order. | Order ID. |
+| Save Configuration | Change in price module settings. | Short description of the change. |
+| Resend Last Email | Resending the last email related to the order in the Message Center. | Order ID. |
+
+## Orders
+
+| Action | Event description | Event details |
+|---|---|---|
+| Change State | Change in order status. | Order ID. |
+| Order Cancellation | Cancellation of an order. | Order ID. |
+| Start Handling  | Action that signals to VTEX that the store has started handling a given order. This triggers the continuation of the flow of this order.  | Order ID.  |
+| Notify Payment | Payment notification for a given order. | Order ID. |
+
+## Order Authorization
+
+| Action | Event description  | Event details  |
+|---|---|---|
+| Create Rule | Creation of a price divergence rule.  | Rule ID. |
+| New Dimension | Creation of dimensions for order approvals, such as order value range, list of emails authorized to carry out order approval, among others.  | Dimension ID. |
+| Delete Dimension | Exclusion of dimensions for order approvals, such as order value range, list of emails authorized to carry out order approval, among others.  | Dimension ID. |
+| Update Dimension | Update in dimensions for order approvals, such as order value range, list of emails authorized to carry out order approval, among others.  | Dimension ID. |
+| Update Rule | Edition of a price divergence rule.  | Rule ID. |
+| Delete Rule | Exclusion of a price divergence rule.  | Rule ID. |
+
+## Inventory & Shipping
+
+| Action | Event description | Event details |
+|---|---|---|
+| Carrier Create | Carrier creation. | Carrier ID. |
+| Carrier Update | Carrier update. | Carrier ID. |
+| Carrier Delete | Carrier deletion. | Carrier ID. |
+| Dock Create | Loading dock creation. | Loading dock ID. |
+| Dock Update | Loading dock update. | Loading dock ID. |
+| Dock Delete | Loading dock deletion. | Loading dock ID. |
+| Warehouse Create | Warehouse creation. | Warehouse ID. |
+| Warehouse Update | Warehouse update. | Warehouse ID. |
+| Warehouse Delete | Warehouse deletion. | Warehouse ID. |
+| Pickup Point Save | Pickup point creation or change. | Pickup point ID. |
+
+## Catalog (Admin)
+
+| Action | Event description | Event details |
+|---|---|---|
+| Product Activation | Product activation. This event is recorded only when changes are made in the Admin. Changes made via spreadsheet are not recorded in this event. | Product ID. |
+| Product Commercial Condition Change | Change in product commercial condition. | Product ID and changed list of conditions. |
+| SKU Attachment Association | SKU Attachment Association. | SKU ID, name and attachment ID. |
+| Archive Upload | File delivery. | File name. |
+| Field Activation | Catalog field activation. | Field name, ID and status. |
+| SKU Seller Binding | SKU and seller binding. | Seller’s ID, SKU ID in seller’s catalog and SKU ID in the marketplace catalog. |
+| SKU Seller Unbinding | Removal of SKU and seller binding. | Seller’s ID, SKU ID in seller’s catalog and SKU ID in the marketplace catalog. |
+| SKU Seller Removal | Removal of seller SKU. | SKU ID in seller’s catalog. |
+
+## Catalog (API)
+
+| Action | Description | Event details |
+|---|---|---|
+| SKU Seller Binding Removal | SKU Binding Removal. | SKU ID in seller and seller ID. |
+| Seller Update | Seller update. | Seller ID. |
+| Seller Creation | Seller creation. | Seller ID. |
+| SKU Seller Binding Activation | SKU binding activation. | SKU ID in seller and seller ID. |
+| SKU Seller Binding Inactivation | SKU binding inactivation. | SKU ID in seller and seller ID. |
+
+## Prices
+
+| Action | Description | Event details |
+|---|---|---|
+| Put Price | Creation or change of a SKU price. | SKU ID. |
+| Save Price Table | Creation or change of a price table. | Identifies the created or changed table. |
+| Save Price Tables | Creation or change of multiple price tables. | Identifies the created or changed tables. |
+| Price Deleted | Deletion of a SKU price. | SKU ID. |
+| Save Config | Creation or change of price settings. | Identifies the created or changed configuration. |
+| Fixed Price Modified | Change of fixed price. | Identification of the fixed price changed. |
+| Put Catalog Step | Creation or change of a price rule. | Price rule created or changed. |
+| Deleted Fixed Prices From Table | Deletion of fixed price from the related price table. | Identification of the table and the deleted price. |
+| Compatibility Post Prices | Change of price using the compatibility API with the PricingV1 contract | Identification of the changed price. |
+| Change Rnb Config  | Change in price settings for new accounts.  | Name of the account that made the change.  |
 
 ## Promotions
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Rate Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in fee settings.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Fee configuration ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Promotion Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in promotion settings.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Promotion configuration ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Coupon Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Coupon change.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Coupon code.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Unarchived Calculator
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Unarchived promotion or fee.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Promotion or fee configuration ID.
-   </td>
-  </tr>
-</table>
+| Action | Event description | Event details |
+|---|---|---|
+| Archive Coupon | Archived a coupon. | Coupon code. |
+| Unarchive Coupon | Unarchived a coupon. | Coupon code. |
+| Change Rate Configuration | Change in fee settings. | Fee configuration ID. |
+| Change Promotion Configuration | Change in promotion settings. | Promotion configuration ID. |
+| Change Coupon Configuration | Coupon change. | Coupon code. |
+| Unarchived Calculator | Unarchived promotion or fee. | Promotion or fee configuration ID. |
+| Archived Calculator | Archived promotion or fee. | Promotion or fee configuration ID. |
+
+## Subscriptions
+
+| Action | Event description | Event details |
+|---|---|---|
+| SubscriptionGroup Update | Update of a subscription group. | Subscription group ID. |
+| Subscription Create | Creation of a subscription. | Subscription ID. |
+| SubscriptionGroup Place Order | Creation of a subscription order within a subscription group. | Subscription group ID. |
+| SubscriptionGroup Retry | Execution of an attempt to generate a subscription cycle. | Subscription group ID. |
+| Subscription Delete | Deletion of a subscription. | Subscription ID. |
+| Plan Create | Creation of a subscription plan, where stores can associate different items and SKUs. | Subscription plan ID. |
+| Plan Update | Update of a subscription plan, where stores can associate different items and SKUs. | Subscription plan ID. |
+| Subscriber Fetch By Email | Audit of who has searched the profile data of a store customer who has subscriptions, based on the customer's email. | ID of the user who carried out the search. |
+| SubscriptionGroup Create For Order | Creation of a subscription group for an existing order. | Subscription group ID. |
+| Plan Delete | Deletion of a subscription plan. | Subscription plan ID. |
+| Store Payments Update | Update in the payment methods that the store accepts for subscriptions. | Account name. |
+
+## Wallets
+
+| Action | Event description | Event details |
+|---|---|---|
+| TOGGLE_WALLET | Activate or deactivate a digital wallet. | toggle-wallet-action |
+
+## Gift Card
+
+| Action | Event description	 | Event details |
+|:---:|:---:|:---:|
+| LIST_GIFT_CARD | Visualization of the gift card list. | list-gift-card |
+| EXPORT_GIFT_CARD | Export of gift cards. | export-gift-card |
+| EDIT_GIFT_CARD | Change in gift card value. | add-gift-card-value |
+| CREATE_GIFT_CARD | Creation of gift cards. | create-multiple-gift-cards |
 
 ## Checkout
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Configured OrderForm
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in OrderForm settings, which is in charge of running the store checkout.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Action description (“configurated OrderForm”)
-   </td>
-  </tr>
-</table>
-
-## Portalv2
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Configuration Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in portal settings.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">“*”
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Saved
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in portal file.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File name changed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Site Created
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Website creation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Name of the created website.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Template Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Changes in portal template.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Template name changed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Page Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Page changes.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Page name.
-   </td>
-  </tr>
-</table>
+| Action | Event description | Event details |
+|---|---|---|
+| SaveOrderFormConfiguration | Change in OrderForm settings, which is in charge of running the store checkout. | Action description (“configurated OrderForm”) |
 
 ## Portal CMS
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change in portal file.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File name and ID changed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Upload
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Portal file upload.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File name changed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Deleted
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File removal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">File name and ID changed.
-   </td>
-  </tr>
-</table>
-
-## Conditions
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PutCondition
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Condition creation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identification of the condition created.
-   </td>
-  </tr>
-</table>
+| Action | Event description | Event details |
+|---|---|---|
+| File Update | Change in portal file. | File name and ID changed. |
+| File Upload | Portal file upload. | File name changed. |
+| File Deleted | File removal. | File name and ID changed. |
+
+## License Manager
+
+| Action | Event description | Event details |
+|---|---|---|
+| Block AppToken | Application key blocking. | Application key blocked. |
+| Accept Sponsor Invite | Accept the invitation to become the sponsor user. | ID of the user who accepted the invitation. |
+| Save User | Create a user or change user information. | User ID. |
+| Save Account | Create an account or edit account information. | Created or changed account. |
+| Change Role | Access role editing. | Role edited. |
+| Delete Role | Deletion of a role. | Role deleted. |
+| Unblock AppToken | Application key unlocking. | Unblocked application key. |
+| Resource Access Allowed | Resource access allowed. | Resource key and user ID to which access has been allowed. |
+| Cancel Sponsor Invite | Cancellation of sponsor user invitation. | ID of invited user. |
+| Delete User | Deletion of a user. | ID of deleted user. |
+| Update Binding | Binding update. | Binding updated. |
+| Resource Access Denied | Resource access denied. | Resource key and user ID to which access was denied. |
+| Create New AppToken | Creation of application key. | Application key created. |
+| Create Sponsor Invite | Creation of a sponsor user invitation. | ID of invited user. |
 
 ## VTEX ID
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PasswordCreated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation of a first-time password in the store or the VTEX Admin
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">User ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PasswordUpdated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Change of store or VTEX Admin password by the user.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">User ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">IdentityProviderChanged
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identity provider configuration change. For example: Creating a customized OAuth integration and changing information in an existing OAuth configuration.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identity provider.
-   </td>
-  </tr>
-</table>
+| Action | Event description | Event details |
+|---|---|---|
+| PasswordCreated | Creation of a first-time password in the store or the VTEX Admin | User ID. |
+| PasswordUpdated | Change of store or VTEX Admin password by the user. | User ID. |
+| IdentityProviderChanged | Identity provider configuration change. For example: Creating a customized OAuth integration and changing information in an existing OAuth configuration. | Identity provider. |
 
-## License Manager
+## Master Data
+
+| Action | Event description | Event details |
+|---|---|---|
+| DeleteDocument | Deleted document. | Document ID. |
+
+## Headless CMS
+
+| Action | Event description | Event details |
+|---|---|---|
+| TRY_PUBLISHING | Attempt to publish a page. | Event ID. |
+| TRY_PUBLISH_IN_RELEASE | Attempt to publish a release. | Event ID. |
+| TRY_UNPUBLISHING | Attempt to unpublish a page. | Event ID. |
+| RESTORE_CONTENT | Content restore. | Event ID. |
+| TRY_UPDATING_DRAFT | Attempt to update a draft. | Event ID. |
+| TRY_UNPUBLISHING_AND_OVERWRITING | Attempt to unpublish and overwrite a page. | Event ID. |
+| done.invoke.deleteContent | Delete content. | Event ID. |
+| done.invoke.deleteContentVariant | Delete content version. | Event ID. |
+
+In the **Action** column, all Headless CMS events also display the following information:
+
+* **CONTENT_ID:** unique identifier of the content.
+* **VARIANT_ID:** unique identifier of the content version.
+* **WORKSPACE**: workspace where the action occurred.
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Action</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event description</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Event details</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Block AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Application key blocking.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Application key blocked.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Accept Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Accept the invitation to become the sponsor user.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID of the user who accepted the invitation.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save User
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Create a user or change user information.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">User ID.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Account
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Create an account or edit account information.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Created or changed account.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Role
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Access role editing.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Role edited.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Delete Role
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Deletion of a role.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Role deleted.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Unblock AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Application key unlocking.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Unblocked application key.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resource Access Allowed
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Resource access allowed.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Resource key and user ID to which access has been allowed.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Cancel Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cancellation of sponsor user invitation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID of invited user.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Delete User
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Deletion of a user.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID of deleted user.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Update Binding
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Binding update.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Binding updated.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resource Access Denied
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Resource access denied.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Resource key and user ID to which access was denied.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Create New AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation of application key.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Application key created.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Create Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creation of a sponsor user invitation.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID of invited user.
-   </td>
-  </tr>
-</table>
+## Seller Management
 
+| Action | Event details | Event description |
+|---|---|---|
+| Update Seller | Change in a seller. | Seller ID. |
+| Save Seller | Seller creation. | Seller ID. |
diff --git a/docs/tutorials/en/explained-search.md b/docs/tutorials/en/explained-search.md
new file mode 100644
index 000000000..dfc93dfb1
--- /dev/null
+++ b/docs/tutorials/en/explained-search.md
@@ -0,0 +1,31 @@
+---
+title: 'Explained Search'
+id: F2yxrRvTNt4aEZGC7HV65
+status: PUBLISHED
+createdAt: 2024-06-27T16:54:49.509Z
+updatedAt: 2024-06-27T16:55:37.629Z
+publishedAt: 2024-06-27T16:55:37.629Z
+firstPublishedAt: 2024-06-27T16:55:37.629Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: explained-search
+locale: en
+legacySlug: explained-search
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+Explained Search is a feature that interprets a search term and displays the product list as a search result. It also displays all the references used to determine the product order, which are:
+
+- Search settings and rules (configured in VTEX Intelligent Search).
+- Product information.
+
+With this tool it is possible to view which data impacts the final ordering. Thus, when exposing this information, modifications can be made to achieve the search goal.
+
+Follow the steps below to access it:
+
+1. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
+2. Under **Intelligent Search**, click __Explained Search__. 
+
+![Explained Search](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
+
diff --git a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
index 5751d3407..f497bcf59 100644
--- a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
@@ -3,8 +3,8 @@ title: 'Exporting and importing product and SKU specifications'
 id: tutorials_274
 status: PUBLISHED
 createdAt: 2017-04-27T22:10:43.787Z
-updatedAt: 2023-03-29T15:30:59.932Z
-publishedAt: 2023-03-29T15:30:59.932Z
+updatedAt: 2024-02-21T20:34:56.013Z
+publishedAt: 2024-02-21T20:34:56.013Z
 firstPublishedAt: 2017-04-27T23:03:12.428Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -28,14 +28,18 @@ In this article, we explain how to export and import spreadsheets with product a
 1. In the VTEX Admin, go to **Catalog**, or type **Catalog** in the search bar at the top of the page.
 2. Click **Import and export**.
 3. Click the **Product Specifications** or the **SKU Specifications** tab, according to your need.
-    ![skuexport1.en](https://images.ctfassets.net/alneenqid6w5/2bM5OviaFXKxXxM8ggXEr3/8f45b5a59425898d0a66697480526899/skuexport1.en.png)
+    ![skuexport1.en](//images.ctfassets.net/alneenqid6w5/2bM5OviaFXKxXxM8ggXEr3/8f45b5a59425898d0a66697480526899/skuexport1.en.png)
 4. Right-click on the desired category.
     You cannot export specifications from all categories at once. You must choose only one category whose specifications you want to export. 
-7. Click on `Export...`.
+5. Click on `Export...`.
     A green rectangle will appear on the screen.
-8. Click `Click here to download the file` to export the spreadsheet.
+6. Click `Click here to download the file` to export the spreadsheet.
 
-![skuexport2.en](https://images.ctfassets.net/alneenqid6w5/6oBhxWWjktsofR8XGRzl3E/87e1859f2f3ece16f3c0e1c527a392ee/skuexport2.en.png)
+![skuexport2.en](//images.ctfassets.net/alneenqid6w5/6oBhxWWjktsofR8XGRzl3E/87e1859f2f3ece16f3c0e1c527a392ee/skuexport2.en.png)
+
+<div class = "alert alert-info">
+  <p>The exported spreadsheet will be available in your email for one week. If you exceed this period, follow the export step-by-step again to generate a new spreadsheet.</p>
+</div>
 
 ## Importing product or SKU specifications
 
@@ -55,7 +59,7 @@ Follow the steps below to import the spreadsheet:
 2. Click **Select** to select the file with the completed spreadsheet on your computer.
 3. Click `Import`.
 
-![skuexport3.en](https://images.ctfassets.net/alneenqid6w5/3xrInPyr70kdXCGgVfj4q1/8b4ff4d98df714f62d97d765edee8600/skuexport3.en.png)
+![skuexport3.en](//images.ctfassets.net/alneenqid6w5/3xrInPyr70kdXCGgVfj4q1/8b4ff4d98df714f62d97d765edee8600/skuexport3.en.png)
 
 ## Learn more
 - [Product and SKU Specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
diff --git a/docs/tutorials/en/exporting-data.md b/docs/tutorials/en/exporting-data.md
index 26a49c70d..b7391791d 100644
--- a/docs/tutorials/en/exporting-data.md
+++ b/docs/tutorials/en/exporting-data.md
@@ -3,8 +3,8 @@ title: 'Exporting data from Master Data v1'
 id: tutorials_1125
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:19.601Z
-updatedAt: 2023-03-28T23:31:33.420Z
-publishedAt: 2023-03-28T23:31:33.420Z
+updatedAt: 2024-06-20T15:09:14.414Z
+publishedAt: 2024-06-20T15:09:14.414Z
 firstPublishedAt: 2017-04-27T23:03:43.216Z
 contentType: tutorial
 productTeam: Master Data
@@ -21,21 +21,21 @@ The mass export of data records in Master Data v1 can be made through the API or
 Exporting data from Master Data is not an immediate operation, and its execution time depends on the amount of data in Master Data. Therefore, in stores with a very large amount of data and a high update frequency, the exported file may become outdated in relation to the new data. If this occurs, the solution may be to export the data again, preferably when there are not many updates taking place (for example, outside of business hours or on weekends).
 </div>
 
-## How to export
+## Export report with data from Master Data v1
 
-1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data.**
-2. Click on the **Aplicações** tab.
-3. Click on **visualizar** in the intended form.
-![visualizar button master data](https://images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
-4. The list of the form selected will be uploaded.
-5. Click on the **Exportar XLS** button.
+Follow the instructions below to export a report with data from documents of a form in Master Data v1.
+
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. Make sure you are in the **Applications** tab.
+3. Click the list icon <i class="fas fa-bars"></i> next to the desired form.
+4. Click on the `Export XLS` button.
 6. Select the fields that you want to see in the report.
-7. Give the e-mail to which the report will be sent (by default, the system will show the e-mail of the user who logged in, but this can be changed).
-8. Click on **Exportar.**
+7. Inform the email to which the report will be sent (by default, the system will show the email of the user who is logged in, but this can be changed).
+8. Click on `Export`.
 
 ## Exported customer data
 
-Below you can see all fields exported from the **Clientes** tab in the Profile System (CRM) in Master Data v1.
+Below you can see all fields exported from the **Customers** tab in the Profile System (CRM) in Master Data v1.
 
 | Field     | Description     | Origin     |
 | ---------- | ---------- | ---------- |
@@ -72,5 +72,5 @@ Below you can see all fields exported from the **Clientes** tab in the Profile S
 | rclastcartvalue       | Value of last cart	       | Browsing script       |
 | carttag       | List of IDs of last SKUs in the cart	       | Browsing script       |
 
-Remember that these fields are the ones shown by default in the Customer form. If the store has customized this company (Customer), other fields may have been created.
+These fields are the ones shown by default in the __Customer__ form. If the store has customized this entity (__Customer__), other fields may have been created.
 
diff --git a/docs/tutorials/en/facebook-faq.md b/docs/tutorials/en/facebook-faq.md
index c4d1f1067..268c20bbe 100644
--- a/docs/tutorials/en/facebook-faq.md
+++ b/docs/tutorials/en/facebook-faq.md
@@ -36,7 +36,7 @@ The first step in this scenario is to investigate whether the SKU in fact does n
 
 If the SKU does have a price, check its status, as the error may also be related to its active/inactive status. The best way to do this is by performing a checkout simulation:
 
-![face faq01](https://images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
+![face faq01](//images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
 
 In this simulation, it is important to analyze the following fields:
 
@@ -53,7 +53,7 @@ This process is recommended for authentication issues concerning the Facebook in
 
 #### Deleting VTEX integration app on Facebook 
 1. Deleting VTEX integration app on Facebook 
-2. In the upper right corner of the screen, **click the button** <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/7bplP3pn7Pu5gpfYKGHUjQ/688fda65e48070afcf18f57e396c2b22/sua_conta_fb.JPG" />
+2. In the upper right corner of the screen, **click the button** <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/7bplP3pn7Pu5gpfYKGHUjQ/688fda65e48070afcf18f57e396c2b22/sua_conta_fb.JPG" />
 3.  Select **Settings and Privacy**, then click on **Settings**.
 4.  Click on **Business integrations**.
 5.  Select VTEX Integration and click **Remove**.
@@ -62,7 +62,7 @@ This process is recommended for authentication issues concerning the Facebook in
 1. Go to [Facebook Business Manager](https://business.facebook.com/).
 2. Click on **Settings**.
 3. Click on **Business Settings**.
-4. Select the VTEX catalog you would like to delete and click on the trash can icon <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6zFRTeiTa9xkTlafUVBIcK/d2c5a40219dbee8084d22f76d0b88109/excluir_fb.JPG" />
+4. Select the VTEX catalog you would like to delete and click on the trash can icon <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6zFRTeiTa9xkTlafUVBIcK/d2c5a40219dbee8084d22f76d0b88109/excluir_fb.JPG" />
 5. Click **Confirm**.
 
 #### Deleting Facebook integration on VTEX
diff --git a/docs/tutorials/en/facilitating-b2b-store-operation.md b/docs/tutorials/en/facilitating-b2b-store-operation.md
index 8ed2a7317..15273e385 100644
--- a/docs/tutorials/en/facilitating-b2b-store-operation.md
+++ b/docs/tutorials/en/facilitating-b2b-store-operation.md
@@ -1,9 +1,9 @@
 ---
 title: 'Facilitating B2B store operation'
 id: 8t1f9FYBsSCopHHVujKWR
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-03-30T14:29:12.548Z
-updatedAt: 2021-05-20T18:17:16.108Z
+updatedAt: 2024-05-10T10:59:55.549Z
 publishedAt: 2021-05-20T18:17:16.108Z
 firstPublishedAt: 2021-03-30T19:54:13.259Z
 contentType: tutorial
@@ -12,7 +12,7 @@ author: 7qy2DBsUp8U5P9lqV0JHfR
 slug: facilitating-b2b-store-operation
 locale: en
 legacySlug: facilitating-b2b-store-operation
-subcategory: 5N5GjDrKSycIQMeoS7CLtj
+subcategory: 2LrbEY7MFeKqmdfYLBCnfi
 ---
 
 You can facilitate the operation of your store by installing applications to solve business issues related to store usability, sales, and after-sales.
@@ -91,7 +91,7 @@ All VTEX stores have the [My account](https://help.vtex.com/en/tutorial/como-fun
 
 This tool allows you to monitor the order status in the after-sales flow and carry out operations such as: “Order again”, which allows placing the same order again.  
 
-![Order again](https://images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
+![Order again](//images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
 
 For more details on “My Account,” check out the tutorial on [how to configure this feature](https://help.vtex.com/en/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1 "").
 
diff --git a/docs/tutorials/en/faq-security-2.md b/docs/tutorials/en/faq-security-2.md
index c86e47329..4a53bfaba 100644
--- a/docs/tutorials/en/faq-security-2.md
+++ b/docs/tutorials/en/faq-security-2.md
@@ -3,7 +3,7 @@ title: 'FAQ - Security 2'
 id: 1ayXEtqawI9yuxFXutiITh
 status: DRAFT
 createdAt: 2022-05-26T13:33:48.633Z
-updatedAt: 2022-08-22T12:33:50.220Z
+updatedAt: 2024-05-28T16:48:10.138Z
 publishedAt: 
 firstPublishedAt: 2022-06-09T22:09:20.893Z
 contentType: tutorial
diff --git a/docs/tutorials/en/faq-security-restricted-content.md b/docs/tutorials/en/faq-security-restricted-content.md
new file mode 100644
index 000000000..bccad63e3
--- /dev/null
+++ b/docs/tutorials/en/faq-security-restricted-content.md
@@ -0,0 +1,187 @@
+---
+title: 'FAQ - Security (restricted content)'
+id: 7AmPOGXykmE9SYyYDzdAZ4
+status: DRAFT
+createdAt: 2022-05-26T00:09:53.997Z
+updatedAt: 2024-05-28T16:45:09.328Z
+publishedAt: 
+firstPublishedAt: 2022-06-02T18:56:44.116Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: faq-security-restricted-content
+locale: en
+legacySlug: faq-security-restricted-content
+subcategory: 
+---
+
+# FAQ - Security (restricted content)
+
+<div class="alert alert-danger">
+  <p>Please do not share the information in this FAQ with users who do not have access to the VTEX Admin.</p>
+</div>
+
+VTEX provides FAQ pages that address the main questions and answers concerning the platform's structure and security to assist in customer risk assessments. This content is restricted to users with access to the VTEX Admin. Public questions and answers are available in the Security FAQ in the VTEX Help Center.
+
+Click the following topics to see the related questions and answers:
+
+* [Risk management](#risk-management)
+* [Access control, identification, and authentication](#access-control-identification-and-authentication)
+* [Platform security](#platform-security)
+* [Data security](#data-security)
+* [Network security](#network-security)
+* [Vulnerability management](#vulnerability-management)
+* [Security monitoring](#security-monitoring)
+* [Incident response and mitigation](#incident-response-and-mitigation)
+* [Disaster recovery and business continuity](#disaster-recovery-and-business-continuity)
+
+## Risk management
+
+### How does VTEX manage cybersecurity risks on its platform and internal infrastructure?
+
+VTEX conducts regular threat and vulnerability analyses of the platform and its operational processes and business. Identifying risks allows us to improve our monitoring and notification systems to deal with their eventual materialization. This can be done by notifying the people in charge of handling risks or triggering automated actions to mitigate or eliminate these risks.
+
+### Does VTEX have a vendor risk management program?
+
+VTEX has a robust third-party risk management process. This involves a thorough and ongoing evaluation of partners and providers to identify, analyze, and mitigate potential risks related to the activities performed by these external parties. This process aims to ensure security and compliance in all third-party interactions, thereby strengthening our organizational risk management posture.
+
+To integrate into our ecosystem, we require third parties to implement appropriate security measures. This condition aims to ensure that all involved parties maintain high standards of information security, contributing to the integrity and reliability of our operational environment.
+
+Learn more about our partners who act as subprocessors in our operational processes on the [Subprocessors](https://vtex.com/us-en/privacy-and-agreements/subprocessors) page.
+
+## Access control, identification, and authentication
+
+### Does VTEX have a password policy for employees? If so, what criteria are considered?
+
+We have secure configurations and a robust password policy to access our internal systems, such as a minimum number of characters and special characters, password expiration, not using previous passwords, session control, inactivity, and more. See examples below:
+
+* Passwords must be at least 16 characters long.
+* Passwords must contain at least 1 uppercase, lowercase, numeric, and special character (`%`, `#`, `$`, `@`, `&`, among others).
+* It's not recommended to use repeated numbers or letters, either in sequence or an obvious series, e.g., `aaaabbbb`, `12345678`, `asdfghjk`.
+* Strong encryption must be used to render all authentication credentials unreadable during transmission and storage in all system components.
+* The option to change password at first login must be enabled.
+* Previous passwords should not be reused.
+
+### Does the platform end the session due to inactivity?
+
+The VTEX platform has an inactivity timeout mechanism. After 15 minutes of inactivity, customers are automatically logged out of the checkout environment.
+
+## Platform security
+
+### How does the platform store and maintain the user base? How are user credentials stored and protected?
+
+VTEX platform passwords use a combination of hash and salt. We currently support SHA1 and PBKDF2 hash algorithms and add a salt at the beginning or the end for an additional layer of security. User emails are stored and logically separated based on specific store accounts and cannot be cross-accessed, even by VTEX employees. The databases containing the emails and hashes are fully encrypted using AES-256.
+
+### How does the hardening process work?
+
+VTEX consistently deploys its environments using the latest Amazon Machine Image (AMI) provided by AWS for each deployment service, including Elastic Beanstalk, OpsWorks, and CloudFormation. This allows us to leverage our security using the protection AWS has in place for instances deployed through its services. Additionally, we increase security configurations with our specific hardening processes tailored for each type of asset.
+
+### What are the security capabilities of the infrastructure that hosts the platform?
+
+The VTEX platform is a SaaS (Software as a Service) solution hosted in a highly controlled environment with numerous security measures. These measures include network protection, which involves filtering and protecting incoming and outgoing traffic, along with a Web Application Firewall (WAF) to protect internal assets, automated real-time monitoring, and environment alerts.
+
+In addition, we implement baselines and asset hardening and establish both physical and logical access controls, among other necessary procedures. These measures aim to ensure continuous protection of the platform and compliance with the highest industry security standards.
+
+## Data security
+
+### How does VTEX prevent data leaking?
+
+VTEX is committed to enhancing the security of our platform and supporting infrastructure through preventive measures and procedures. In addition, we constantly reinforce the control of access to systems, particularly those containing sensitive data, by adhering to the principle of least privilege. We strictly follow applicable guidelines in regulated environments, such as those involving payment card data (PCI-DSS) and mandated by data protection laws.
+
+We analyze how information is transferred between environments, whether internal or external, ensuring that it is not shared unnecessarily, thus minimizing the security perimeter. Other actions to prevent data leakage are: we continuously educate our professionals on best information security practices through regular training and qualification; we automate process controls, as computers help us maintain control uniformity effectively; we constantly evolve our data leakage prevention process, regularly updating it to meet emerging risks and adapt to technological or strategic company changes.
+
+## Network security
+
+### Are internal production networks segregated in any way, for example, by restricting and/or filtering traffic between networks?
+
+VTEX's production networks are completely isolated from external networks, creating a highly secure environment. Employees who manage these production environments may occasionally require a VPN (Virtual Private Network) connection to access them.
+
+Externally, load balancers are the only components accessed via the DMZ (Demilitarized Zone). Meanwhile, the platform and database layers are housed in separate subnets distinct from the DMZ. These critical layers are fortified with additional security measures to ensure that only authorized personnel can access them. This network architecture provides an extra layer of protection, safeguarding VTEX’s sensitive data and systems from external threats.
+
+### Does VTEX use network access protection through firewalls?
+
+VTEX uses network access protection through firewalls. In addition to the local firewalls installed on the operating systems of the servers, VTEX has multiple layers of security in the AWS infrastructure.
+
+We use AWS security groups, ELB (Elastic Load Balancing) configurations, and VPC (Virtual Private Cloud) routing to replicate firewall features across our systems. These measures are designed to ensure that only authorized traffic is permitted on our network, reinforcing the security of our data and services.
+
+Since the deployment of our applications is automated and all logs are centralized, our team does not require daily direct access to the servers. Access to the production environment is typically managed via the AWS console or through our own web applications and APIs.
+
+For an additional layer of security, our security groups and ELBs are configured to only allow HTTP and HTTPS access to ELBs that expose resources publicly. If a specific task requires additional access, it can be requested and temporarily granted in a controlled and secure manner. These practices guarantee the integrity and security of our network infrastructure.
+
+### What controls does VTEX use to mitigate DDoS (Distributed Denial of Service) attacks?
+
+VTEX employs a two-layer approach to defending against DDoS attacks. The first defense layer is at the CDN (Content Delivery Network) level, where security measures filter and block malicious traffic before it reaches our core infrastructure.
+
+Additionally, we implement an adaptive limitation rule in the front proxy in each of VTEX's microservices.  This rule is crucial for detecting and limiting malicious or excessive traffic, which mitigates the impact of potential DDoS attacks.
+
+VTEX also leverages [AWS Shield](https://aws.amazon.com/shield/), an Amazon Web Services service that offers additional protection against DDoS attacks. This multi-layered strategy significantly enhances VTEX’s ability to mitigate and respond to DDoS attacks, ensuring the continued availability and integrity of our services.
+
+Beyond standard protective measures implemented by VTEX, customers can enhance the security of their stores by opting for a Web Application Firewall (WAF) through the VTEX Shield add-on product. The WAF provides an extra layer of protection, filtering and blocking malicious traffic before it can reach the stores. This customizable solution allows customers to adapt security measures to their specific needs, offering enhanced protection against cyberattacks. By choosing VTEX Shield, merchants ensure a comprehensive and proactive defense for their online stores and have peace of mind and confidence in their digital operations.
+
+### Does VTEX have an IDS (Intrusion Detection System) and an IPS (Intrusion Prevention System)? If so, how often are the rules reviewed?
+
+Yes, our solution includes both an IDS and an IPS.  These systems are crucial for detecting and preventing malicious activities within our network infrastructure and other systems.
+
+We regularly review the IDS and IPS rules to align them with the latest recognized threats and vulnerabilities. This review occurs with considerable frequency and is an integral part of our security process. Our objective is to maintain the most current protection against new attack techniques and emerging vulnerabilities.
+
+This ongoing practice of reviewing IDS and IPS rules reflects our commitment to the security and protection of our client data, ensuring that we stay one step ahead of the continually evolving cyber threats.
+
+## Vulnerability management
+
+### What is the timeframe for patching vulnerabilities?
+
+Our vulnerability management procedure is carefully designed to ensure an effective approach to patching potential security flaws. We have established internal policies that determine the timeframe for patching, which varies according to the criticality and complexity of each identified vulnerability. This timeframe varies to ensure that the most critical and urgent vulnerabilities are addressed with priority, while less severe ones are managed appropriately without compromising system security. This approach allows us to efficiently manage security risks and maintain our systems protected against potential threats.
+
+### Does VTEX allow customers to perform vulnerability checks through independent scans and penetration tests organized by an independent consultant?
+
+VTEX instances are hosted on AWS infrastructure, which prevents personal audits of the systems. AWS adheres to rigorous [compliance programs](https://aws.amazon.com/compliance/programs/) to secure the hosted instances.
+
+VTEX does not allow access to its facilities or files for auditing internal systems and procedures. Instead, VTEX obtains reports from a specialized, independent auditing company. To demonstrate commitment to privacy, security, compliance, and governance, VTEX shares relevant documents, policies, and certifications through a [security portal](https://vtex.com/us-en/trust/). As part of its ongoing commitment to security, VTEX is continuously pursuing new certifications.
+
+Customers can conduct [vulnerability scans](https://help.vtex.com/pt/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb#reportar-vulnerabilidade) within their own environments under two conditions: the tests must not include actual attacks that could disrupt production systems, nor should they attempt to access data that does not belong to them.
+
+### How is vulnerability management carried out? Is the process documented? To what extent are the identified vulnerabilities managed and patched?
+
+Vulnerability scans are performed continuously, restricted to an authorized group of individuals using approved and dedicated systems. When vulnerabilities are detected in our systems or software, we initiate a patch management process to implement the necessary corrections. Our team coordinates all involved developers to reproduce the issues and, when necessary, develop the required security patches. After implementing the patches, we conduct further tests to verify their effectiveness. If the testing returns positive results, we close the case. If necessary, we conduct a detailed analysis similar to the problem management phase.
+
+## Security monitoring
+
+### Are system logs protected against modification, falsification, or improper access?
+
+Our applications are equipped with audit logging systems that capture and store relevant logs to ensure compliance with both our internal standards and applicable regulations. Logs cover various events, including authentication details like login failures, successes, and account blocks, all in compliance with regulatory, security, and privacy requirements. They are fundamental to our internal analysis,  providing a complete and detailed record of all relevant activities on the platform. This ensures transparency, security, and compliance in our operations.
+
+### Does VTEX log security events?
+
+Our organization uses a tool to centralize activity logs and implement SIEM (Security Information and Event Management) features. Logs are generally kept for 18 months. We use both in-house and AWS-provided tools for continuous security analysis and vulnerability scanning in the cloud. These tools are used at least quarterly.
+
+The VTEX team makes the solution available, keeps it updated with new features, and fully monitors its operation. In addition, we have a specialized team dedicated to scaling the solution during peak seasons or in response to surges in demand. This team also continuously monitors store performance using proprietary heuristics.
+
+### Does VTEX protect its mail server against spoofing?
+
+VTEX uses Google Workspace as its primary communication tool. To enhance the security of our email server against spoofing, we have implemented SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). SPF allows us to specify a list of servers and domains authorized to send emails on behalf of our organization, while DKIM adds a unique digital signature to each message sent. These measures ensure that destination servers can authenticate the origin of the messages, offering an additional layer of protection against possible fraudulent activity. The VTEX Security team is the only one that manages these configurations.
+
+### Are the endpoints protected with antivirus?
+
+We have integrated robust antivirus technology across all our endpoints and servers. This measure is crucial for enhancing the security of our infrastructure and for protecting our clients' sensitive data and information. By making the installation of antivirus software on all devices and servers mandatory, we proactively mitigate potential cyber threats, ensuring a secure and reliable experience for everyone involved in our operations.
+
+## Incident response and mitigation
+
+### Does the incident response plan establish criteria for notification?
+
+Yes, our operational protocols include our commitment to notify affected customers within a maximum of 24 hours after confirming any security incident. This measure is essential to ensure transparency and provide our customers with the information they need to take appropriate actions to protect their data and systems. In addition, by acting quickly to disclose information about security incidents, we demonstrate our ongoing commitment to cybersecurity and the trust of our clients.
+
+## Disaster recovery and business continuity
+
+### What are the set RPO (Recovery Point Objective) and RTO (Recovery Time Objective) for disaster recovery?
+
+The RPO is the maximum age of backup data before it becomes obsolete, which directly correlates with the backup retention policy. At VTEX, the standard RPO is 24 hours. However, this timeframe specifically refers to the frequency of backups for Catalog. For transactional systems like Checkout, we implement strategies that can reduce the RPO to the last saved transaction.
+
+The RTO is the maximum time allowed to restore services. Service downtime may result from application interruption, data corruption or loss, server failure, or interruption in the AWS availability zone or region. Check the standard RTO based on the type of downtime below:
+
+| Downtime | Standard RTO |
+|---|---|
+| Application interruption | 10 minutes |
+| Data corruption or loss | 30 minutes |
+| Data server failure | 1 hour |
+| Interruption in the AWS availability zone | 4 hours |
+| Interruption in the AWS region | 24 hours |
diff --git a/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 0f4ac127f..be207fb35 100644
--- a/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -17,7 +17,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 For a better understanding of what each fixed price spreadsheet field means, read the full description below.
 
-![tabela.preço.fixo](https://images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
+![tabela.preço.fixo](//images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
 
 - **SKU ID:** the ID of the SKU to which you want to add the fixed price.
 - **Trade policy:** the name or ID of the trade policy to which the fixed price will be applied.
diff --git a/docs/tutorials/en/filtering-all-orders.md b/docs/tutorials/en/filtering-all-orders.md
index 911847a67..d6f3c742d 100644
--- a/docs/tutorials/en/filtering-all-orders.md
+++ b/docs/tutorials/en/filtering-all-orders.md
@@ -3,8 +3,8 @@ title: 'Filtering orders on All Orders'
 id: tutorials_192
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:05.494Z
-updatedAt: 2023-05-31T14:45:05.491Z
-publishedAt: 2023-05-31T14:45:05.491Z
+updatedAt: 2023-12-21T14:06:54.896Z
+publishedAt: 2023-12-21T14:06:54.896Z
 firstPublishedAt: 2017-04-27T23:00:47.449Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,13 @@ legacySlug: filtering-orders-in-oms, filtering-orders-on-the-oms
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
+<div class = "alert alert-info">
+You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
+</div>
+
 In the **Orders** module, the **All Orders** page allows you to access your store's orders, search and filter them, as shown in the image below:
 
-![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 This article explains how to use these resources, and it is divided into:
 
@@ -26,6 +30,13 @@ This article explains how to use these resources, and it is divided into:
 - [Filter by Status](#filter-by-status)
 - [Created](#created)
 
+Besides searching for orders in **Orders > All Orders**, you can search for orders from any page in the VTEX Admin using the global search bar at the top bar. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
+
 ## Search bar
 
 To search using the search bar, type in the desired term and press the `enter` key. You can search by:
@@ -52,7 +63,7 @@ Searching on All orders returns all orders related to the criteria used, regardl
 
 Enter the desired term in the search bar to search on All orders. This will make <i class="fas fa-toggle-on"></i> `Remove date limit` option visible. Then, activate it to search.
 
-![search_bar_without_time_limit_EN](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c861b2b825068d861850bce56660aa30/search_bar_without_time_limit_EN.png)
+![search_bar_without_time_limit_EN](//images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c861b2b825068d861850bce56660aa30/search_bar_without_time_limit_EN.png)
 
 <div class="alert alert-danger">
 The search on All orders cannot be combined with other filters. So, once you remove the date limit from the search, any active filters become inactive. If the search term is removed or the <i class="fas fa-toggle-off"></i> <b>Remove date limit</b> is disabled, the previously configured filters become active again.
@@ -70,7 +81,7 @@ Searching by associated filters allows you to combine different filters, which a
 
 On the **Orders > All Orders** page, there is `Filters` option, as shown in the image below: 
 
-![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 When you click `Filters`, a modal is displayed with the following options:
 
@@ -186,7 +197,7 @@ Click `Filters` to use these filters and select **Other**. You can find the opti
 
 On the **Orders > All Orders** page, there is the `Filter by Status` <i class="fas fa-angle-down"></i> option, as shown in the image below:
 
-![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 When clicking `Filter by Status` <i class="fas fa-angle-down"></i>, your store's [order status](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196) options are displayed. For example, if among all your orders, there are no canceled ones, this option will not be visible. 
 
@@ -198,7 +209,7 @@ For more status filter options, go to the section <a href="https://help.vtex.com
 
 On the **Orders > All Orders** page, there is the option `Created: Today` <i class="fas fa-angle-down"></i>, as shown in the image below:
 
-![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 This filter has the **Today** date enabled by default, but by clicking it, the following options are displayed:
 
diff --git a/docs/tutorials/en/filtering-data-on-master-data.md b/docs/tutorials/en/filtering-data-on-master-data.md
index 99dcd0111..a8fa3e64f 100644
--- a/docs/tutorials/en/filtering-data-on-master-data.md
+++ b/docs/tutorials/en/filtering-data-on-master-data.md
@@ -3,8 +3,8 @@ title: 'How to filter data in Master Data'
 id: tutorials_778
 status: PUBLISHED
 createdAt: 2017-04-27T21:58:11.041Z
-updatedAt: 2023-03-28T23:42:30.477Z
-publishedAt: 2023-03-28T23:42:30.477Z
+updatedAt: 2024-06-27T00:07:07.554Z
+publishedAt: 2024-06-27T00:07:07.554Z
 firstPublishedAt: 2017-04-27T23:03:42.905Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,40 +15,54 @@ legacySlug: filtering-data-on-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-In Master Data, you can create filters for accesses through API, or for viewing the forms. Creating filters facilitates the search and query of data, enabling a greater control on your data. Filters must be set up first in the data entity, and subsequently, in the form desired. To be set up as a filter, a field should not be of the CEP, Text and File types. Also, a good practice is to set up filters with fields that contain just a few options for completion, such as “Categoria,” for example.
+In Master Data, you can create filters for API access and viewing forms. Filters simplify data search and query, giving you more control over your data.
 
-## How to set up a Data Entity filter
+To create a filter, you must first configure it on the data entity and then on the desired form, following the steps described in the following sections.
 
-1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data.**
-2. In Master Data, click **Aplications** > **Data structure.**
-2. Access the **Entidade de Dados** tab.
-3. Click on the **editar** button in the entity in which you intend to set up a filter.
-4. The list of fields will be shown.
-5. Click on the gear icon of the field that you intend to set up.
-6. Check the **É filtro **option.**
-7. Click on the **Salvar** button.
-8. In the list of entities, click on the **Publicar** button, with the disk icon.
-9. Wait for the publication and re-indexation of data to view the filter.
+## Filter requirements
 
-## How to set up the filter in the form
+Follow the recommendations below when setting fields as filters:
 
-1. Access the **Master Data** module;
-2. Click on the **Aplicações** tab;
-3. In the application containing the form in which you want to create the filter, click on the gear icon;
-4. The list of forms will be displayed; click on the pencil icon of the form that you intend to edit;
-5. Fill out the **Filtros** field with the internal name of the field that was marked as filter. “Internal name” is the first column when creating and editing a data entity; this name cannot be changed. To enter more than one value, just separate them by comas, without spaces;
-6. Click on the **Salvar **button.
+- Do not use fields of the **CEP** (Brazilian postal code system), **Text** and **File** types as filters.
+- Add a field containing a few options as a filter, such as "Category".
 
-## How to use filters
+## Configuring filters in the data entity
 
-After creating the filter, you will be able to use it in the form. To do so, follow the steps below:
+Follow the instructions below to set an existing field as a filter in the data entity:
 
-1. Access the **Master Data** module;
-2. Click on the **Aplicações** tab;
-3. In the desired application, identify the form that you intend to view;
-4. In the desired form, click on the list icon;
-5. The page with the list of records of this form will be shown. On one side, you will see the filters set up.
-6. To use the filters, just click on the name of the filter, and on its value.
-7. To check the results of the filter, scroll down the page and click on the **Filtrar **button.
-8. You can use several fields simultaneously as filters, as well as several values in the same field. To remove a filter, just click on the **x** icon next to the value.
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. In Master Data, click the gear icon <i class="fas fa-cog"></i> next to an application.
+3. Click **Data structure**.
+4. Go to the **Data Entities** tab.
+5. Click the edit button <i class="fas fa-edit"></i> on the entity you want to set the filter.
 
+   You will be redirected to the list of the entity's fields.
+6. Click the gear <i class="fas fa-cog"></i> button in the field you want to set as a filter.
+7. Check the **Is filterable?** option.
+8. Click the `Save` button.
+9. In the list of entities, click the diskette button <i class="fas fa-save"></i> to publish the entity.
+10. Click the reindex button <i class="fas fa-expand-arrows-alt"></i> to index the entity.
+
+## Configuring filters in the form
+
+Follow the instructions below to configure filters in the form:
+
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
+2. In the application containing the form where you want to create the filter, click the gear icon <i class="fas fa-cog"></i>.
+
+   You will be redirected to the list of forms in the app.
+3. Click the edit <i class="fas fa-edit"></i> button on the row of the form you want to edit.
+4. Complete the **Filters** field with the internal name of the designated filter field. The internal name corresponds to the initial field value when creating and editing the data entity, and it cannot be changed. To input multiple values, separate them with commas, without spaces.
+5. Click the `Save` button.
+
+## Filtering form records
+
+After creating the filter, you can use it in the form. To do this, follow the steps below:
+
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data**.
+2. In the desired application, find the form you want to view and click the list icon <i class="fas fa-bars"></i>.
+
+   You will be redirected to the list of records for this form. On the side, you will see the configured filters. 
+3. To filter, select the filter's name and value, then click `Filter`.
+
+   You can filter by multiple fields at once, and use multiple values for a single field. To remove a filter, click the `X` next to its value.
diff --git a/docs/tutorials/en/filtering-transactions-on-pci-gateway.md b/docs/tutorials/en/filtering-transactions-on-pci-gateway.md
index 20d2bd7ba..e9517841f 100644
--- a/docs/tutorials/en/filtering-transactions-on-pci-gateway.md
+++ b/docs/tutorials/en/filtering-transactions-on-pci-gateway.md
@@ -3,8 +3,8 @@ title: 'Filtering transactions on Orders section'
 id: 6LUq65FqUgIKkKEeWa4IwC
 status: PUBLISHED
 createdAt: 2019-01-24T21:38:42.313Z
-updatedAt: 2023-03-26T21:29:36.950Z
-publishedAt: 2023-03-26T21:29:36.950Z
+updatedAt: 2023-10-18T16:58:56.709Z
+publishedAt: 2023-10-18T16:58:56.709Z
 firstPublishedAt: 2019-01-24T21:38:42.695Z
 contentType: tutorial
 productTeam: Financial
@@ -87,7 +87,7 @@ Some examples of payment methods are:
 
 - Visa
 - Bank slip
-- Promissory
+- Notes Payable
 - Mercado Pago
 - Pay Pal
 
diff --git a/docs/tutorials/en/filters.md b/docs/tutorials/en/filters.md
new file mode 100644
index 000000000..a5bab03d0
--- /dev/null
+++ b/docs/tutorials/en/filters.md
@@ -0,0 +1,50 @@
+---
+title: 'Filters'
+id: k24mQQa9SjmhNWSwdqIMB
+status: PUBLISHED
+createdAt: 2024-06-27T16:43:43.811Z
+updatedAt: 2024-06-27T16:44:34.723Z
+publishedAt: 2024-06-27T16:44:34.723Z
+firstPublishedAt: 2024-06-27T16:44:34.723Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: filters
+locale: en
+legacySlug: filters
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Filters is a feature that displays in groups the specifications of search results. It allows the customer to explore relevant features of a product during their search experience, and provides scenarios that facilitate user decision-making.
+
+By selecting a filter (price, color, size, or brand), customers can narrow search results and other existing filters available for this search context.
+
+**VTEX Intelligent Search** uses the context of products returned in search results to know exactly which filters should be displayed to the customer, according to the Catalog configuration.
+
+<div class="alert alert-info">
+  <p>The brand, department, category, and subcategory filters are sorted by the number of products registered for each filter.</p>
+</div>
+
+For example, consider that the *Size* filter has been configured in the store's catalog, and only the *sneakers* product has the *Size* specification filled in. So when the user searches for the term *sneakers*, the *Size* filter will be available. If they search for any other term, such as *hat*, this specification won’t be displayed as a filter.
+
+The search result will not display a specification when it the only existing filter or when the customer accesses it through the store menu. For example, if a customer selects the Electrical Appliances filter directly from the menu, it will not display Departments as a side filter.
+
+<div class="alert alert-info">
+  <p>If the search results returns more than 30,000 products, some filter values will be omitted, since only the specifications of some of these products will be considered.</p>
+</div>
+
+The Filters feature allows you to:
+
+- Search for a term within a filter.
+- Configure and define the maximum number of options in a filter before scrolling.
+- Configure the filter layout. You can choose between the following formats:
+   - Vertical list (standard format).
+   - Horizontal list (used to display filters such as Size and Color).
+   - Slider: Used to adjust the price range from a minimum to a maximum value.
+   - Price field: Allows entering the full price and discounted price for filtering results.
+
+Check out the [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) guide on the Developer Portal for more technical details on using filters.
+
+<div class="alert alert-warning">
+  <p>While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.</p>
+</div>
diff --git a/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
index dd6637e90..e2cdcf9ef 100644
--- a/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -1,10 +1,10 @@
 ---
 title: 'Marketplace Network: find marketplaces and sellers in the VTEX network'
 id: 2bzC7tXlVgLEEjxo4ixcAM
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-09-14T22:21:50.677Z
-updatedAt: 2022-04-07T14:44:29.576Z
-publishedAt: 2022-04-07T14:44:29.576Z
+updatedAt: 2023-07-19T21:34:02.498Z
+publishedAt: 
 firstPublishedAt: 2020-09-14T23:03:21.356Z
 contentType: tutorial
 productTeam: Apps
@@ -21,7 +21,7 @@ Note that Marketplace Network is a tool that promotes interaction between potent
 
 ## Finding Sellers and Marketplaces
 
-![Marketplace network tour EN](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
+![Marketplace network tour EN](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
 To see the list of available marketplaces and sellers, go to *Marketplace > Marketplace Network > Find Sellers / Find Marketplaces*. On both pages, you can search by keyword and filter the list for more exact results, as well as contact potential partners.
 
 ## Contact
@@ -43,7 +43,7 @@ The potential business partner will receive an email with the information you en
 </div>
 
 ## Store Profile
-![Network profile EN](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/17a2b46b39a8fc853755fc91e974b904/Marketplace_store_profile_EN.gif)
+![Network profile EN](//images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/17a2b46b39a8fc853755fc91e974b904/Marketplace_store_profile_EN.gif)
 
 1. In the *Marketplace* section of your store, click __Marketplace Network__.      
 2. Click the __Store Profile__ page.      
diff --git a/docs/tutorials/en/find-sellers.md b/docs/tutorials/en/find-sellers.md
new file mode 100644
index 000000000..03c06c9bc
--- /dev/null
+++ b/docs/tutorials/en/find-sellers.md
@@ -0,0 +1,57 @@
+---
+title: 'Find Sellers'
+id: 6kkZaxIgfDyvN5trgIuwBl
+status: PUBLISHED
+createdAt: 2023-07-19T20:18:59.741Z
+updatedAt: 2023-07-19T20:46:01.656Z
+publishedAt: 2023-07-19T20:46:01.656Z
+firstPublishedAt: 2023-07-19T20:41:17.099Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: find-sellers
+locale: en
+legacySlug: find-sellers
+subcategory: 6riYYNZCpO8wyksi8Ksgyq
+---
+
+The **Find Sellers** page enables contact with sellers operating in the VTEXecosystem, creating opportunities for new business and mutual growth for all involved. The page works as a catalog of parties interested in partnerships,allowing registration,search,and contact between marketplaces and sellers to sign commercial agreements.
+
+To leverage the page,you need to create a **Store Profile**. Learn how by reading the documentation.
+
+<div class="alert alert-info">
+Note that <b>Find Sellers</b> is a tool that fosters contact between potential partners,but it is not a mandatory step to be a marketplace and seller on VTEX.
+If you want to be both,a marketplace and seller,please read the <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace">Marketplace Strategies at VTEX</a> documentation.
+</div>  
+
+To access the list of sellers, go to **Marketplace > Find Sellers** or type **Find Sellers** in the search bar.
+
+## Searching and filtering
+
+You can use the page search bar to search by seller name or VTEX account name and filter the list in a combined or separate way to get more accurate results and contact potential partners.
+
+**Static filters**
+
+- Country
+- Industry
+
+**Conditional filter**
+
+- Region
+
+## Contact
+
+The **Find Sellers** page enables direct contact with potential partners. You can access the seller details by clicking the profiles in the list. Note that you can only send a message after activating your **Store Profile**.
+
+When sending a message, provide all the information the seller needs to connect to your business. We also suggest anticipating questions or topics that might arise in a future meeting.
+
+To contact a member:
+
+1. In the Marketplace section of your VTEX Admin, click **Find Sellers** or type **Find Sellers** in the search bar.
+1. In the list, click the **profile** of a potential partner.
+1. Complete the **Contact Seller** field.
+1. Click the **Send** button.
+
+<div class="alert alert-info">
+The potential business partner will receive an email with your message. If the interest is mutual,the seller or marketplace administrator can contact you and negotiate the marketplace and seller agreement terms.
+</div>
diff --git a/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
index 7f34eef22..28f0cef96 100644
--- a/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
@@ -26,7 +26,7 @@ From February 1st, 2023, the new interface will be the default for all VTEX stor
 
 You can see the sections and fields correspondence between the old version of the **Order Details** page and the new version in the image below:
 
-![board_comparativo_interface_pedido_v2_en](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
+![board_comparativo_interface_pedido_v2_en](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
 
 ## What happened to the six-month search filter?
 
@@ -38,17 +38,17 @@ The search in All Orders cannot be combined with other filters. So, once you rem
 
 Enter the desired term in the search bar to search all orders. This will make the <i class="fas fa-toggle-off"></i> `Remove date limit` option visible. Then, activate it to search.
 
-![busca_sem_limite_data_all_en](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
+![busca_sem_limite_data_all_en](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
 
 ## How to view the order flow diagram?
 
 By default, in the new interface, a timeline with the **Order status** events is displayed, as in the image below:
 
-![timeline_pedido_en](https://images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/4ed7055d4dd820fcb5d2ff9d70e7c3c4/timeline_pedido_en.png)
+![timeline_pedido_en](//images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/4ed7055d4dd820fcb5d2ff9d70e7c3c4/timeline_pedido_en.png)
 
 If you want to see the **Order diagram** as in the old interface, click `View diagram` and a modal like the one in the image below will display: 
 
-![diagrama_pedido_en](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
+![diagrama_pedido_en](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
 
 ## How do I invoice an order?
 
@@ -56,7 +56,7 @@ In the **Items to invoice** section of the new interface, you can access all inv
 
 * **Submit invoice referencing items: **This option is exclusive to the new interface. It allows you to issue the invoice for all or specific items identified by SKU, inventory, and price. The following image shows an example:
 
-![faturar_referenciar_pedidos_final_en](https://images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/bf24faab5137854a28d9c2e7dd972c54/faturar_referenciar_pedidos_final_en.png)
+![faturar_referenciar_pedidos_final_en](//images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/bf24faab5137854a28d9c2e7dd972c54/faturar_referenciar_pedidos_final_en.png)
 
 * **Submit single invoice:** This option corresponds to the old _Submit invoice_ and allows you to invoice the full or partial order amount. The page layout is different, but the fields remain the same.
 
@@ -75,6 +75,6 @@ In the new interface, in the **Order history** section, there is a timeline with
 
 To resend an email to the client, click the sent email event or the arrow icon <i class="fas fa-angle-right"></i> to see the event details, which will display as in the following image:
 
-![enviar_email_en](https://images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/b5b4d755b4b1cab066217b2ce58d6218/enviar_email_en.png)
+![enviar_email_en](//images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/b5b4d755b4b1cab066217b2ce58d6218/enviar_email_en.png)
 
 Click the `Resend Email` button, and it will be immediately sent to the customer, and the following confirmation message should be displayed: _Email was successfully resent to the customer_. 
diff --git a/docs/tutorials/en/fulfillment-logistics-vtex.md b/docs/tutorials/en/fulfillment-logistics-vtex.md
index e6a94b2b0..371db3f12 100644
--- a/docs/tutorials/en/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/en/fulfillment-logistics-vtex.md
@@ -48,7 +48,7 @@ Once the order is placed, the [reservation of the products is authorized](https:
 Please note that the shipping process depends on the configuration made on the platform. Here, we present the scenarios for each type of shipping (delivery and pickup), but there are other possible flows in the shipping process. For example, when the customer chooses pickup and the selected pickup point is the warehouse, there is no need to transport the packages.
 </div>
 
-![Envio EN](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/2cf59529b64fd641f61b1afdb807d136/Envio_EN.svg)
+![Envio EN](//images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/2cf59529b64fd641f61b1afdb807d136/Envio_EN.svg)
 
 ## Configuring the logistics process
 
diff --git a/docs/tutorials/en/fulfillment-magalu.md b/docs/tutorials/en/fulfillment-magalu.md
new file mode 100644
index 000000000..f0b0ba82f
--- /dev/null
+++ b/docs/tutorials/en/fulfillment-magalu.md
@@ -0,0 +1,18 @@
+---
+title: 'Fulfillment Magalu'
+id: 7ckyEv4Z8HmiCRydo0a9P6
+status: PUBLISHED
+createdAt: 2023-12-19T19:09:47.849Z
+updatedAt: 2024-01-05T11:58:20.772Z
+publishedAt: 2024-01-05T11:58:20.772Z
+firstPublishedAt: 2023-12-19T19:44:22.896Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: fulfillment-magalu
+locale: en
+legacySlug: fulfillment-magalu
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to English speaking countries.</div>
diff --git a/docs/tutorials/en/general-configurations-on-the-oms.md b/docs/tutorials/en/general-configurations-on-the-oms.md
index c559371ff..813d06bd6 100644
--- a/docs/tutorials/en/general-configurations-on-the-oms.md
+++ b/docs/tutorials/en/general-configurations-on-the-oms.md
@@ -3,8 +3,8 @@ title: 'Orders General Configuration'
 id: tutorials_194
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:49.644Z
-updatedAt: 2023-03-29T16:11:56.900Z
-publishedAt: 2023-03-29T16:11:56.900Z
+updatedAt: 2024-07-02T19:07:22.178Z
+publishedAt: 2024-07-02T19:07:22.178Z
 firstPublishedAt: 2017-04-27T23:00:47.468Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -19,7 +19,7 @@ It is possible to execute configurations directly related to the conditions of t
 
 In the VTEX Admin, go to **Store Settings > Orders > Settings**, or type *Orders* in the search bar at the top of the page and select *Store Settings / Orders*.
 
-![configuracoes_pedidos_en](https://images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/5f485e4f43fa2df4305a1f4ad9b7dd40/configuracoes_pedidos_en.png)
+![configuracoes_pedidos_en](//images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/5f485e4f43fa2df4305a1f4ad9b7dd40/configuracoes_pedidos_en.png)
 
 ## Cart
 
@@ -33,7 +33,7 @@ This configuration is a flag that enables or disables the requirement for a user
 
 - **Minimum number of items in cart**. Default: 1 item – this will prevent the customer from closing the purchase without having at least the same value in quantity of items as that defined in this field.
 - **Number of decimal digits to be considered**. Default: 2 decimal places – this means that the product prices are illustrated according to the number of decimal places defined. There will be no rounding of amounts. At the checkout, the value of the decimal places – if they have been cut off – will be included for closing the purchase.
-- **Minimum total value in cart**. Default: R$0.10 – as with the minimum quantity of items in the cart, this will prevent the customer from closing the purchase without having at least the same amount in products as that defined in this field.
+- **Minimum total value in cart**. Default: R$0.10 – as with the minimum quantity of items in the cart, this will prevent the customer from closing the purchase without having at least the same amount in products as that defined in this field. The minimum cart value also includes taxes and shipping costs. It is the final value of the order that is being calculated.
 
 ## Orders
 
diff --git a/docs/tutorials/en/geolocation-at-checkout.md b/docs/tutorials/en/geolocation-at-checkout.md
index d96ced230..874eb1ed0 100644
--- a/docs/tutorials/en/geolocation-at-checkout.md
+++ b/docs/tutorials/en/geolocation-at-checkout.md
@@ -42,7 +42,7 @@ Once you have an API Key, proceed as follows:
 1. In the VTEX Admin, go to __Store Settings > Shipping > Geolocation Shipping__, or type __Geolocation Shipping__ in the search bar at the top of the page.
 2. Enter the API Key in the field indicated and click on __Register Key__.
 
-![Geolocalizacao 1 EN](https://images.ctfassets.net/alneenqid6w5/6pPXB9VKz6aQIA8YUWyyKk/ae4f7acd4ed20feac7edf6d27960c902/Geolocalizacao_1_EN.png)
+![Geolocalizacao 1 EN](//images.ctfassets.net/alneenqid6w5/6pPXB9VKz6aQIA8YUWyyKk/ae4f7acd4ed20feac7edf6d27960c902/Geolocalizacao_1_EN.png)
 
 <div class="alert alert-info">
 In some countries, Google Maps does not provide high quality mapping. Therefore it is possible that some addresses will be written wrongly, or Google may indicate an incorrect address. In these cases, you must correct the address on the map itself.
@@ -61,7 +61,7 @@ Once you've created the polygon and entered your ID in the shipping worksheet, y
 3. In the blue options menu located at the top of the page, click on __Checkout__.
 4. In the __Google Maps API Key__ field insert the API Key given in the logistics step.
 
-![Google map keys](https://images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/a0449abd0a356e5afa7cbb87a7101fc5/google_maps_api_key_en.PNG)
+![Google map keys](//images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/a0449abd0a356e5afa7cbb87a7101fc5/google_maps_api_key_en.PNG)
 
 Once the API Key has been included in the Checkout configuration, the geolocation will be visible in your store checkout.
 
diff --git a/docs/tutorials/en/gift-card.md b/docs/tutorials/en/gift-card.md
index 7b66abd09..3ba3220ad 100644
--- a/docs/tutorials/en/gift-card.md
+++ b/docs/tutorials/en/gift-card.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Gift cards'
 id: tutorials_995
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T21:57:54.816Z
-updatedAt: 2023-04-27T17:11:31.494Z
-publishedAt: 2023-04-27T17:11:31.494Z
+updatedAt: 2024-01-19T19:16:50.349Z
+publishedAt: 2024-01-12T12:46:20.978Z
 firstPublishedAt: 2017-04-27T23:03:42.674Z
 contentType: tutorial
 productTeam: Financial
@@ -24,22 +24,23 @@ For more details on the second option, check our technical documentation on [int
 
 ## How to create the GiftCard (manual)
 
-By a VTEX standard, the voucher is considered a payment method. This product has a nominal value that can be used at the moment of the purchase to reduce the order price.
+By a VTEX standard, the gift card is considered a payment method. This product has a nominal value that can be used at the moment of the purchase to reduce the order price.
 
-To create a new voucher, follow the step by step:
+To create a new gift card, follow the step by step:
 <ol>
   <li>In the VTEX Admin, go to <b>Promotions > Gift Cards</b>, or type <b>Gift Cards</b> in the search bar at the top of the page.</li>  
   <br>
   <li>Click on the <b>New Gift Card</b> button.</li> 
   <br>
   <div class = "alert alert-info">
-  <p>On the data filling page, the <b>Voucher</b> field corresponds to the voucher's ID. This is automatically generated by the VTEX system and will be displayed in SmartCheckout for vouchers that are not associated with a unique CPF (individual taxpayer registration number) or CNPJ (company registration number).</p>
+  <p>On the gift card creation screen, the <b>Gift card</b> field is automatically filled in by the VTEX system with the ID code of the new gift card. This is the code to be entered by the customer on the checkout screen to apply the gift card to the cart and reduce the payment value of the order.</p>
 </div>
 <br>
   <li>Fill in the fields that will be displayed as explained below:</li>
   <br>
 <ul>  
   <li><b>Value</b>: the nominal value that will be granted for the voucher use.</li>
+  <li><b>Currency code</b>: currency in which the voucher will be created. The options available for selection are presented in accordance with the commercial policies of each store.</li>
   <li><b>Expiration Date</b>: this is the effective date for using the voucher.</li>
   <li><b>Customer ID</b>: data that identifies and defines the voucher for a specific client.</li>
   <li><b>Collection</b>: identifies the product collection that defines the items to which the voucher can be applied.</li>
@@ -79,8 +80,9 @@ To create more than one new voucher at the same time (a batch), follow the step
   <li>Fill in the fields that will be displayed as explained below:</li>  
 <br>
 <ul>
-  <li><b>Number of gift cards</b>: this is the number of vouchers that you want to create as a batch. A maximum of 500 (five hundred) vouchers can be created per batch;</li>
+  <li><b>Number of gift cards</b>: this is the number of vouchers that you want to create as a batch. A maximum of 500 (five hundred) vouchers can be created per batch.</li>
   <li><b>Value</b>: the nominal value that will be granted for all vouchers in this batch.</li>
+  <li><b>Currency code</b>: currency in which vouchers will be batched. The options available for selection are customized according to the commercial policies of each store.</li>
   <li><b>Expiration Date</b>: this is the effective date for using all vouchers of this batch.</li>
   <li><b>Collection</b>: identifies the product collection that defines the items to which the vouchers can be applied.</li>
 <br>
@@ -107,9 +109,9 @@ There is no limit to the creation of gift cards, however only 8000 gift cards ca
 
 ## How to set a Gift Card as a payment method
 
-Perfect! Now that you created the Gift Card, you need to set it as a payment method. It allows your Gift Card to be displayed in the Checkout and your customers will be able to complete their order using the amount available in it.
+After creating the Gift Card, it must be configured as a payment method. This way, your customers will be able to use it at Checkout.
 
-Follow the instructions below: 
+Follow the steps below to set up the Gift card:
 
 1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type Settings in the search bar at the top of the page.
 2. In the __Payment Conditions__ tab, click on the `+` button.
diff --git a/docs/tutorials/en/google-analytics-faq.md b/docs/tutorials/en/google-analytics-faq.md
index 3a6edfc0e..215b8c238 100644
--- a/docs/tutorials/en/google-analytics-faq.md
+++ b/docs/tutorials/en/google-analytics-faq.md
@@ -3,8 +3,8 @@ title: 'Google Analytics: FAQ'
 id: 2VRtB07muo3vwO6KEmMVn0
 status: PUBLISHED
 createdAt: 2021-12-17T18:41:26.175Z
-updatedAt: 2023-03-31T15:22:28.277Z
-publishedAt: 2023-03-31T15:22:28.277Z
+updatedAt: 2023-07-31T18:35:26.120Z
+publishedAt: 2023-07-31T18:35:26.120Z
 firstPublishedAt: 2021-12-17T18:53:43.536Z
 contentType: tutorial
 productTeam: Others
@@ -15,6 +15,7 @@ legacySlug: google-analytics-faq
 subcategory: 1luKrYptdi8WoMYckakUaM
 ---
 
+Check below some of the most frequently asked questions about Google Analytics for VTEX stores.
 ## How to install Google Analytics in your store
 
 The installation is done via [Google Tag Manager](https://help.vtex.com/tutorial/integracao-com-o-google-tag-manager#), as described in the article [Setting up Google Analytics in VTEX stores](https://help.vtex.com/pt/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG#).
@@ -31,26 +32,37 @@ The information available on the Google platform comes from the triggers of thes
 
 Attribution models dictate the methodology used by a platform to attribute a cause to a given event. When it comes to Google Analytics, this means defining whether a given sale occurred as a result of an ad on a social network or an email marketing campaign, for example.
 
-Learn more about [attribution models in Google Analytics.](https://support.google.com/analytics/answer/1662518?hl=en)
+Learn more about [attribution models in Google Analytics.](https://support.google.com/analytics/answer/1662518?hl=en).
 
-## Why is there divergence in the metrics displayed on VTEX and Google Analytics?
+## Why are the metrics displayed on VTEX and Google Analytics different?
 
 There are differences in how each platform gets data from your store, and this can result in different numbers in analytics. Below, we indicate some of the most common cases and explain how to interpret these differences.
 
 ### Transactions
 
-Divergences in the recording of transactions are usually due to some irregularity in the triggering of the [Google Analytics tag](https://help.vtex.com/en/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG#). In this case, there may be duplicate or missed triggers.
+As VTEX is responsible for processing transactions from your store, all of them are recorded on the platform. However, in Google Analytics, some cases may generate anomalies or failures triggering the corresponding tag. These cases include:
+
+- Browsers with strict privacy settings.
+- Browsers with JavaScript blocking.
+- Ad blockers.
+- Google Analytics data layer configuration error. See the official Google documentation to learn more about how your development team can [configure Google Analytics 4 data layer](https://developers.google.com/tag-manager/ecommerce-ga4).
+- Transaction tag triggers even with transactions that were not successfully completed.
+- Failed or duplicated display of the order confirmation page if the transaction tag is linked to the page display.
+
+<div class = "alert alert-info">
+Consider that there is also a delay of up to 48 hours in recording transaction data on Google Analytics.
+</div>
 
 Also, integrations can be built in such a way that they end up not triggering certain tags on your storefront. For example, there are integrations that use a [payment app](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-app) and complete the purchase without redirecting the customer to the order confirmation page, such as the integration developed by AME Digital. Transactions will always be recorded in VTEX, but in this case, it is likely that they are not recorded in Google Analytics, generating divergence.
 
 ### Sales attribution
 
-It is normal that there are differences between the attribution in the VTEX **Orders** module and Google Analytics, as they are different tools with different attribution models and that capture information through different cookies.
+It is normal that there are differences between attribution data as seen in VTEX modules and Google Analytics, as they are different tools with different [attribution models](#what-are-attribution-models) and that capture information through different cookies.
 
-The UTM information recognized by VTEX can be verified in the developer tools panel of your browser, in the `marketingData` object of the [OrderForm.](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview#orderform-fields) For more information, read the article [Marketing UTMs at checkout.](https://help.vtex.com/en/tutorial/identificar-se-utms-de-marketing-estao-sendo-passadas-para-o-checkout--6kjHHfOWIgeI26qcQSU4Wg#)
+The UTM information recognized by VTEX can be verified in the developer tools panel of your browser, in the `marketingData` object of the [OrderForm](https://developers.vtex.com/docs/guides/orderform-fields). For more information, read the article [Marketing UTMs at checkout](https://help.vtex.com/en/tutorial/identificar-se-utms-de-marketing-estao-sendo-passadas-para-o-checkout--6kjHHfOWIgeI26qcQSU4Wg#).
 
 Google Analytics uses the Last Interaction model by default.
-You can choose between different models, which are described in [Google’s documentation on attribution models.](https://support.google.com/analytics/answer/1662518?hl=en)
+You can choose between different models, which are described in [Google’s documentation on attribution models](https://support.google.com/analytics/answer/1662518?hl=en).
 
 If you also analyze Facebook ads data, you may find other divergences. For example, Facebook takes into account customers who saw the ad and purchased the product at some later point, even if they came to the store via another route at the time of purchase.
 
@@ -68,9 +80,11 @@ Despite the differences, it is worth noting that both platforms consider that a
 
 ### Sales funnel
 
-Just as sessions are recorded by VTEX, there is an interpretation of navigation data between product pages and shopping cart flow. With this, VTEX generates the sales funnel.
+VTEX generates a view of your store sales funnel based on the navigation records that the platform generates, from product pages to shopping cart flow and checkout.
+
+Whereas Google Analytics provides an automatically generated sales funnel based on Google tags set up in your storefront. Learn more about [how Google generates this funnel view](https://support.google.com/analytics/answer/6014872#zippy=%2Cin-this-article%2Cneste-artigo).
 
-[Google Analytics, on the other hand, has an automatically generated sales funnel](https://support.google.com/analytics/answer/6014872#zippy=%2Cin-this-article%2Cneste-artigo), based on Google tags set up on your storefront.
+As the funnel views are based on different information, they may differ.
 
-In addition, you can set up another sales funnel in Google Analytics, which allows for a personalized view and better control of the buying journey. For more information, read the article [Setting up the sales funnel in Google Analytics](https://help.vtex.com/en/tutorial/configurar-funil-de-vendas-no-google-analytics#).
+You can configure another sales funnel on Google Analytics, which enables a customized view and better control of the buying journey. Check out this article on how to [set up the sales funnel on Google Analytics] (https://help.vtex.com/en/tutorial/configurar-funil-de-vendas-no-google-analytics#).
 
diff --git a/docs/tutorials/en/google-integration-warnings.md b/docs/tutorials/en/google-integration-warnings.md
new file mode 100644
index 000000000..05d3d3d59
--- /dev/null
+++ b/docs/tutorials/en/google-integration-warnings.md
@@ -0,0 +1,20 @@
+---
+title: 'Google integration warnings'
+id: 4BC0Epit2hACKbkBSqDR2A
+status: PUBLISHED
+createdAt: 2024-07-01T15:16:46.324Z
+updatedAt: 2024-07-01T20:42:52.728Z
+publishedAt: 2024-07-01T20:42:52.728Z
+firstPublishedAt: 2024-07-01T16:13:33.089Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: google-integration-warnings
+locale: en
+legacySlug: google-integration-warnings
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning">
+Content in translation.
+</div>
diff --git a/docs/tutorials/en/google-pay-beta.md b/docs/tutorials/en/google-pay-beta.md
index 0608817a7..85ce94aaa 100644
--- a/docs/tutorials/en/google-pay-beta.md
+++ b/docs/tutorials/en/google-pay-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Google Pay (Beta)'
 id: 653pNFOw6L5CvGupLosJSq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-26T15:34:40.825Z
-updatedAt: 2023-06-14T19:34:39.943Z
-publishedAt: 2023-06-14T19:34:39.943Z
+updatedAt: 2023-06-27T21:56:34.229Z
+publishedAt: 
 firstPublishedAt: 2023-04-26T20:03:44.992Z
 contentType: tutorial
 productTeam: Shopping
@@ -38,7 +38,7 @@ To enable Google Pay, follow the steps below.
 <p>The issuing banks supported by the Google Pay extension are the ones configured in the payment conditions.</p>
 </div>
 
-![google pay - EN](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/c1848f1deba2af0d837f96f21eae86a5/image.png)
+![google pay - EN](//images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/c1848f1deba2af0d837f96f21eae86a5/image.png)
 
 Google Pay will then be available in your VTEX store's checkout as a new payment method. It may take around 10 minutes to be implemented.
 
diff --git a/docs/tutorials/en/google-search-console-tracking-sitemap.md b/docs/tutorials/en/google-search-console-tracking-sitemap.md
index e3ab2184d..0bda05148 100644
--- a/docs/tutorials/en/google-search-console-tracking-sitemap.md
+++ b/docs/tutorials/en/google-search-console-tracking-sitemap.md
@@ -34,11 +34,11 @@ Follow the steps below to register your Sitemap:
 Go to your store’s Search Console panel: 
 [https://search.google.com/search-console/sitemaps?resource_id=sc-domain%YOURDOMAIN.com&hl=en**]
 
-![Sitemaps](https://images.ctfassets.net/alneenqid6w5/5VQWkkJc0TvsouCQ1Pts4e/646f489829a2854caad27ac326de0e2e/Screen_Shot_2019-08-08_at_15.25.23.png_h_250)
+![Sitemaps](//images.ctfassets.net/alneenqid6w5/5VQWkkJc0TvsouCQ1Pts4e/646f489829a2854caad27ac326de0e2e/Screen_Shot_2019-08-08_at_15.25.23.png_h_250)
 
 Add your new sitemap and click on submit. The Search Console will access the XML and verify it.
  
-After successfully adding the sitemap to Search Console, the tool will show you a list of all the URLs:![Sitemap URL List](https://images.ctfassets.net/alneenqid6w5/6CHMG0wWwSoEmGJSrYhxua/79d8edd09363539cd5cf196e2e35d61e/Screen_Shot_2019-08-08_at_15.46.59.png_h_250)
+After successfully adding the sitemap to Search Console, the tool will show you a list of all the URLs:![Sitemap URL List](//images.ctfassets.net/alneenqid6w5/6CHMG0wWwSoEmGJSrYhxua/79d8edd09363539cd5cf196e2e35d61e/Screen_Shot_2019-08-08_at_15.46.59.png_h_250)
 
 
 
diff --git a/docs/tutorials/en/headless-cms-overview.md b/docs/tutorials/en/headless-cms-overview.md
new file mode 100644
index 000000000..58521d55a
--- /dev/null
+++ b/docs/tutorials/en/headless-cms-overview.md
@@ -0,0 +1,54 @@
+---
+title: 'Headless CMS - Overview'
+id: 3U5gvhHdQL0jczYH8gjX09
+status: PUBLISHED
+createdAt: 2023-12-15T20:27:39.404Z
+updatedAt: 2024-02-16T01:12:18.561Z
+publishedAt: 2024-02-16T01:12:18.561Z
+firstPublishedAt: 2023-12-18T13:33:50.044Z
+contentType: tutorial
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-overview
+locale: en
+legacySlug: headless-cms-overview
+subcategory: 27t6x0lngvjI3bnUg5AgEO
+---
+
+The Headless CMS is a content management system designed by VTEX to empower businesses with the flexibility to create and deliver content across various channels, such as websites and mobile apps.
+
+The term *Headless* refers to the separation between the interface that displays content to the user, the frontend, and the system responsible for managing and storing that content, the backend. This approach allows content management to occur independently of the user interface, providing flexibility and scalability. For example, a merchant can update a product page through Headless CMS without affecting the user experience on the website. This simplifies content maintenance and enables the reuse of data.
+
+To access the Headless CMS, log in to the VTEX Admin and navigate to **Storefront > Headless CMS**. 
+
+<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+  For the the Headless CMS management, make sure the <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">resources</a> <i>See CMS menu on the top-bar</i>, <i>Settings</i>, and <i>CMS GraphQL API</i> are associated with your <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">user role</a>. Otherwise, <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role">create a custom user role </a> and add these resources to it or add these resources to an existing user role.
+</div>
+
+The headless CMS allows you to:
+
+- [Manage Projects](#managing-projects)
+- [Manage pages](#managing-pages)
+- [Manage singleton content types](#managing-singleton-content-types)
+
+## Managing Projects
+
+[Projects](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) is a feature in Headless CMS that allows you to create and manage multiple frontend projects like mobile apps, websites, and email marketing from a single control panel.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
+
+For more information, refer to [Managing Projects](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM). 
+
+## Managing pages
+Within each project, you can also manage all the URL routes and page templates for your store's website, including the home page, product page (PDP), and others. For more information, refer to [Managing Pages in the Headless CMS](https://help.vtex.com/en/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt).
+
+## Managing Singleton content types
+Singleton is a content type that simplifies content management by creating and managing a single page, guaranteeing the existence of only one version of this content type in the Headless CMS. This approach enhances content reliability and simplifies the creation and maintenance of content within a Headless CMS environment.  For more information, refer to [Managing Singleton content types](https://help.vtex.com/en/tutorial/managing-singleton-content-types--VBibMN1BqV2OFmavUFCdo).
+
+## Next steps
+Check out the following tutorials to start managing your storefront content:
+
+- [Managing Projects](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) 
+- [Managing Pages in the Headless CMS](https://help.vtex.com/en/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt)
+- [Managing Singleton content types](https://help.vtex.com/en/tutorial/managing-singleton-content-types--VBibMN1BqV2OFmavUFCdo)
+
diff --git a/docs/tutorials/en/how-and-when-do-i-receive-my-invoice.md b/docs/tutorials/en/how-and-when-do-i-receive-my-invoice.md
index 2ddce1f81..fc0753e5c 100644
--- a/docs/tutorials/en/how-and-when-do-i-receive-my-invoice.md
+++ b/docs/tutorials/en/how-and-when-do-i-receive-my-invoice.md
@@ -3,8 +3,8 @@ title: 'How and when do I receive my invoice?'
 id: 4kRivWUH68iQ6AwI2QU6gm
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:47.627Z
-updatedAt: 2020-05-12T18:36:27.081Z
-publishedAt: 2020-05-12T18:36:27.081Z
+updatedAt: 2023-10-11T20:31:33.338Z
+publishedAt: 2023-10-11T20:31:33.338Z
 firstPublishedAt: 2019-01-24T22:08:59.617Z
 contentType: tutorial
 productTeam: Billing
@@ -15,15 +15,14 @@ legacySlug: how-and-when-do-i-receive-my-invoice
 subcategory: 5ZfsNR4ioEsIyu6wkyce0M
 ---
 
-<div class="alert alert-info" role="alert"><strong>WARNING: This procedure is only for customers billed in Brazil.</strong></div>
+<div class="alert alert-warning" role="alert"><p>This procedure only applies to customers billed in <strong>Brazil.</strong></div>
 
+The billing is triggered until the 5th business day of the month. Invoice and *boleto* (Brazilian offline payment method) are available on the __Billing__ module in the Admin of your store.
 
-The billing is triggered until the 5th business day of the month. Invoice and *"boleto"* (Brazilian off-line payment method) are available on the __Billing__ module in the Admin of your store.
+When a charge is made, we send an email to the registered contacts advising that the invoice and the *boleto* are already available for payment or consultation.
 
-When a charge is made, we send an email to the registered contacts advising that the invoice and the *"boleto"* are already available for payment or consultation.
-
-If you have not received the notice by the 5th business day of the month, [check your administrative panel](/en/tutorial/how-to-download-vtex-payment-slips-and-tax-invoices). If you identify any divergence, [contact our](https://support.vtex.com/hc/en/requests) financial team.
+If you have not received the notice by the 5th business day of the month, [check your administrative panel](https://help.vtex.com/en/tutorial/how-to-download-the-vtex-invoices--tutorials_653). If you identify any divergence, [contact our](https://support.vtex.com/hc/en/requests) financial team.
 
 If you are unable to download your *"boleto"*, you may not have a financial profile configured in your store account. In this case, ask the account's Super Admin to add it.
 
-If you are not receiving the emails that inform that the *"boleto"* is available for download on the platform, the email address may not be registered as a financial contact. In this case, open a [ticket](https://help-tickets.vtex.com/smartlink/sso/login/zendesk) to request the inclusion of the email address in the account's financial contacts. 
+If you are not receiving the emails that inform that the *"boleto"* is available for download on the platform, the email address may not be registered as a financial contact. In this case, open a [ticket](https://support.vtex.com/hc/en/requests) to request the inclusion of the email address in the account's financial contacts. 
diff --git a/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
index 734a76e40..66af3431c 100644
--- a/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
@@ -26,7 +26,7 @@ The VTEX platform is prepared to support domain changes without adverse impacts.
 ### 1. Create new HOST entries in the License Manager
 In the License Manager, under “Contas,” enter the new domain as the HOST of your store. At this moment, the DNS of the new domain should not be pointed to VTEX yet. 
 See below an image illustrating and giving examples of the inclusion of new HOSTs to be applied:
-![Change Domain](https://images.ctfassets.net/alneenqid6w5/4FfqogdPy0UokEe2G2CICk/d044f0e997870688f9fec8163c508f73/626-en.png)
+![Change Domain](//images.ctfassets.net/alneenqid6w5/4FfqogdPy0UokEe2G2CICk/d044f0e997870688f9fec8163c508f73/626-en.png)
 
 ### 2. Check the settings of the new Portal
 This step is crucial for the Checkout to continue operating after the change. You must check whether the Sites set up are connected to some inexisting Account Name created in License Manager. [Learn more about the portal settings here](/en/faq/configure-template-in-the-smartcheckout).
diff --git a/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
index 861716ecc..db5265430 100644
--- a/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
@@ -44,7 +44,7 @@ Follow the step-by-step below:
 
 <div class="alert alert-info">More information about <strong>General Settings</strong> and <strong>Search and Filter Configurations</strong> can be found in our article on <a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Creating a data entity</a>, subsection <strong>How to set up</strong>.</div>
 
-![criar campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
+![criar campo master data ds](//images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
 You will then return to the main Data Entity page. To complete the process, you need to publish the field. Locate the entity line in which the field was added and click on the disk icon.
 
@@ -69,6 +69,6 @@ To achieve this, follow the instructions below:
 7. Drag the field from the list entitled "available fields" to the columns entitled "column Fields 1" or "column Fields 2";
 8. In the lower part of the screen, click on the blue Save button.
 
-![criar campo master data CRM](https://images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
+![criar campo master data CRM](//images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
 
 Done! The fields will be displayed on the form.
diff --git a/docs/tutorials/en/how-can-i-create-callcenter-user.md b/docs/tutorials/en/how-can-i-create-callcenter-user.md
index 2e31c31a1..32b63dce8 100644
--- a/docs/tutorials/en/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/en/how-can-i-create-callcenter-user.md
@@ -41,7 +41,7 @@ To create a user with the telesales role, follow the steps below.
 
 7. Click on **Save**.
 
-![Animated GIF showing how to create call center operator ](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/c41d49badebeb869d2e9d4cef73c74b0/Adicionar_perfil_EN.gif)
+![Animated GIF showing how to create call center operator ](//images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/c41d49badebeb869d2e9d4cef73c74b0/Adicionar_perfil_EN.gif)
 
 <div class="alert alert-warning">
 When creating a  <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">role</a>, avoid including call center <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">resources</a> with other resources. Otherwise, the role might not work as expected.
diff --git a/docs/tutorials/en/how-can-i-create-cluster-of-customers.md b/docs/tutorials/en/how-can-i-create-cluster-of-customers.md
index 24f789605..4dcf3b440 100644
--- a/docs/tutorials/en/how-can-i-create-cluster-of-customers.md
+++ b/docs/tutorials/en/how-can-i-create-cluster-of-customers.md
@@ -3,8 +3,8 @@ title: 'Create a cluster of customers'
 id: frequentlyAskedQuestions_1724
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:58.065Z
-updatedAt: 2022-10-17T21:24:38.123Z
-publishedAt: 2022-10-17T21:24:38.123Z
+updatedAt: 2024-05-24T19:15:04.156Z
+publishedAt: 2024-05-24T19:15:04.156Z
 firstPublishedAt: 2019-01-24T22:05:41.666Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -44,6 +44,6 @@ So technically, a cluster in CRM is nothing more than a field.
 
 To populate this field you can use an [import worksheet](https://help.vtex.com/en/tutorial/importing-data-into-master-data--tutorials_1135 "How to import data into Master Data") or an API, or you can do it manually using the Customer form in CRM. Everything depends on the store’s strategy for clusterizing its customers.
 
-## Go further
+## Learn more
 
-[Learn how to create a promotion for a cluster](/en/tutorial/creating-promotions-for-a-cluster-of-customers)
+- [Learn how to create a promotion for a cluster](/en/tutorial/creating-promotions-for-a-cluster-of-customers)
diff --git a/docs/tutorials/en/how-can-i-direct-a-financial-doubt-to-vtex.md b/docs/tutorials/en/how-can-i-direct-a-financial-doubt-to-vtex.md
index 84bf11254..0390c7e48 100644
--- a/docs/tutorials/en/how-can-i-direct-a-financial-doubt-to-vtex.md
+++ b/docs/tutorials/en/how-can-i-direct-a-financial-doubt-to-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'How can I direct a financial doubt to VTEX?'
 id: 5h8wQ6AqIEKYcU2mASqGEU
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:46.689Z
-updatedAt: 2020-03-09T17:25:45.988Z
-publishedAt: 2020-03-09T17:25:45.988Z
+updatedAt: 2024-07-29T22:06:40.466Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T21:58:53.151Z
 contentType: tutorial
 productTeam: Billing
diff --git a/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md b/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md
index ef37226c4..663f9ed62 100644
--- a/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md
+++ b/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md
@@ -3,8 +3,8 @@ title: 'Exporting the newsletter database using Master Data'
 id: frequentlyAskedQuestions_1825
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:58.818Z
-updatedAt: 2023-03-28T23:50:45.779Z
-publishedAt: 2023-03-28T23:50:45.779Z
+updatedAt: 2024-05-24T18:56:12.924Z
+publishedAt: 2024-05-24T18:56:12.924Z
 firstPublishedAt: 2019-01-24T22:00:56.109Z
 contentType: tutorial
 productTeam: Master Data
@@ -19,10 +19,13 @@ To export your customer base that have chosen to receive newsletter, follow the
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data.**
 2. Click on the **Clientes** tab.
-3. Click **Export XLS.**
+3. Click `Export XLS`.
 4. Select the `Receive Newsletter?` filter, as well as others you like (`Name` and `email`, for example).
-5. Click on **Export.**
-6. A window will appear informing you that the export has been successfully programmed. Click **OK** to close it.
-7. In the spreadsheet that has been sent to your email there will be a column titled `isNewsletterOptIn`, which assigns the value **true** to customers who receive newsletter and **false** to those who do not.
+5. Click on `Export`.
+6. A window will appear informing you that the export has been successfully programmed. Click `OK` to close it.
 
-_This option is only valid for stores with their Newsletter registered in the CRM. If your store is not yet configured in this way, and still uses the page control, read the article [Configuring the inclusion of a newsletter in Master Data](/en/tutorial/how-do-i-configure-the-inclusion-of-newsletter-in-master-data--frequentlyAskedQuestions_1816) to find out how to do it._
+  In the spreadsheet that has been sent to your email there will be a column titled `isNewsletterOptIn`, which assigns the value **true** to customers who receive newsletter and **false** to those who do not.
+
+<div class="alert alert-warning">
+  <p>This option is only valid for stores with their Newsletter registered in the CRM. If your store is not yet configured in this way, and still uses the page control, read the article <a href="https://help.vtex.com/en/tutorial/how-do-i-configure-the-inclusion-of-newsletter-in-master-data--frequentlyAskedQuestions_1816">Configuring the inclusion of a newsletter in Master Data</a> to find out how to do it.</p>
+</div>
diff --git a/docs/tutorials/en/how-can-my-customer-login-to-my-store.md b/docs/tutorials/en/how-can-my-customer-login-to-my-store.md
index 192e1af72..352cbb63d 100644
--- a/docs/tutorials/en/how-can-my-customer-login-to-my-store.md
+++ b/docs/tutorials/en/how-can-my-customer-login-to-my-store.md
@@ -28,7 +28,7 @@ The purpose of this article is to show you how your customers should log in to a
 
 When clicking on a link to authenticate, the client will see the login screen.
 
-![vtex-id-pt](https://images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/cfeadc0b744855b307b02718f7d4493f/vtex-id-en.png)
+![vtex-id-pt](//images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/cfeadc0b744855b307b02718f7d4493f/vtex-id-en.png)
 
 There are three standard ways to log in to a VTEX store:
 
@@ -42,9 +42,9 @@ This login type __sends an access token to the user’s email__ so he or she can
 
 For the client to sign in using this method, they must follow the steps below:
 1. On the login screen, the user should click on __Receive quick access key by email__;
-2. On the next screen, the user must fill out their email and click on the button __Confirm__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-3. __An access token will be sent to the email they entered in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should to check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-4. Return to the login screen and __enter the access key__ received in the previous step and click __Enter__ ![fill-access-token-pt](https://images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
+2. On the next screen, the user must fill out their email and click on the button __Confirm__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+3. __An access token will be sent to the email they entered in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should to check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+4. Return to the login screen and __enter the access key__ received in the previous step and click __Enter__ ![fill-access-token-pt](//images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
 
 ### Login with email and password
 
@@ -54,11 +54,11 @@ This type of login __ requests email and password__ so that the client can authe
 
 - If the client needs to __register a password__, they must follow the steps below:
 1. On the login screen, the user must click on __Login with email and password__;
-2. On the next screen, the user should click on __Don’t you have a password? Register now!__ ![register-password-pt](https://images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
-3. The user must fill in their email and click on the button __Confirm__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-4. On the next screen, the user must enter their new password in the fields __New password__ and __Confirm new password__ and then click on the button __Create new password__  ![register-new-password-pt](https://images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
-5. __An access token will be sent to the email informed in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-6. Return to the login screen and __enter the access key__ received in the previous step and then click __Change Password__ ![change-password-pt](https://images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)
+2. On the next screen, the user should click on __Don’t you have a password? Register now!__ ![register-password-pt](//images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
+3. The user must fill in their email and click on the button __Confirm__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+4. On the next screen, the user must enter their new password in the fields __New password__ and __Confirm new password__ and then click on the button __Create new password__  ![register-new-password-pt](//images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
+5. __An access token will be sent to the email informed in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+6. Return to the login screen and __enter the access key__ received in the previous step and then click __Change Password__ ![change-password-pt](//images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)
 
 ### Social media login
 
diff --git a/docs/tutorials/en/how-change-order-works-beta.md b/docs/tutorials/en/how-change-order-works-beta.md
new file mode 100644
index 000000000..a0748b4da
--- /dev/null
+++ b/docs/tutorials/en/how-change-order-works-beta.md
@@ -0,0 +1,77 @@
+---
+title: 'How Change order works (Beta)'
+id: 56TO0bOFXsfmpc7YZ3wIUZ
+status: PUBLISHED
+createdAt: 2023-11-27T14:51:09.723Z
+updatedAt: 2024-04-09T17:58:34.469Z
+publishedAt: 2024-04-09T17:58:34.469Z
+firstPublishedAt: 2023-11-27T22:39:50.675Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: how-change-order-works-beta
+locale: en
+legacySlug: how-change-order-works-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+<div class="alert alert-info">
+This feature is in beta, which means that we are working to improve it. If you wish to use <b>Change order (Beta)</b>, please contact <a href="https://help.vtex.com/en/support">our Support</a> and provide the <a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> in which to activate it.
+</div>
+
+The **Change order (beta)** feature allows you to edit an order in different ways, either due to customer requests, product unavailability, or other reasons. These are the main order changes that can be made:
+
+- **Add:** Increase the number of items or add new products.
+- **Remove:** Remove the partial or total number of items.
+- **Weight change:** Adjust the weight assigned to items.
+- **Replace items:** Replace items, including those priced by weight.
+- **Price change:** Change the order total amount.
+
+For detailed instructions on each action, read the [How to change orders (Beta)](https://help.vtex.com/en/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw) documentation. This article covers other aspects of **Change order (beta)** and is structured as follows:
+
+- [Changes through the VTEX Admin and API](#changes-through-the-vtex-admin-and-api)
+- [General characteristics](#general-characteristics)
+- [Price changes](#price-changes)
+
+## Changes through the VTEX Admin and API
+
+You can change an order in two ways; see details in the table below:
+
+| **How to change** | **Description** | **Changeable status** |
+|:---:|:--- |:--- |
+| Via the VTEX Admin | <p>Changes are made from the <a href="https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl">order details page</a>, which can be accessed under <b>Orders > All orders</b>, by selecting the desired order.</p><p>You can also access the order using the search bar at the top of the VTEX Admin. To do this, click the bar, select the <b>Orders</b> option, and use any of the following criteria:</p><p><ul><li>Order ID</li><li>Customer name</li><li>Customer email</li><li>Customer document</li></ul></p><p><b>Help Center article:</b> <a href="https://help.vtex.com/en/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw">How to change orders (beta)</a></p> | <p><ul><li><code>handling</code></li></ul></p> |
+| Via API | <p>Changes using the endpoints:</p><p><ul><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change detail</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes">Get order change history</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry">Retry order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel">Cancel order change</a></li></ul></p> | <p><ul><li><code>ready-for-handling</code></li><li><code>handling</code></li><li><code>waiting-for-fulfillment</code></li><li><code>ready for invoicing</code></li></ul></p> |
+
+The order's change history is recorded on its [details page](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) in the **History of changed items section**. To view this information via API, use the [Get order change history](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes) endpoint.
+
+## General characteristics
+
+**Change order (beta)** has specific characteristics, as shown in the table below:
+
+| **Characteristic** | **Description** |
+|:---:|:--- |
+| Number of order changes | There is no limit to how many times an order can be changed. |
+| Incomplete orders | You cannot change <a href="https://help.vtex.com/en/tutorial/entendendo-os-pedidos-incompletos--tutorials_294">incomplete orders</a> — those lacking necessary information to be processed by the VTEX platform. |
+| Franchise accounts | You can change orders where the seller is a franchise account. |
+| VTEX marketplace, certified, partner and external marketplaces | <p>Changing orders works differently across various marketplace scenarios on VTEX:</p><p><ul><li>You can change orders from stores that act as both a <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller">VTEX seller</a> and a <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplace</a>.</li><li>You can change <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a> orders placed on <a href="https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces">external marketplaces</a>.</li><li>You cannot change orders placed on <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-marketplace">certified marketplaces</a> and <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-marketplaces-partners">marketplaces partners</a>.</li></ul></p> |
+| Reservation | In change order scenarios, item <a href="https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92">reservation</a> is automatic. |
+| Inventory update | When you change an order, the store's <a href="https://help.vtex.com/en/tutorial/inventory-management--tutorials_139">inventory</a> is not updated automatically. The store must update the inventory in the VTEX Admin under <b>Catalog > Inventory > Inventory Management</b> or via API, using the <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a> endpoint. |
+| License Manager permission | <p>For a user to be able to change orders, their <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> must be associated with at least one of the following <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">Licence Manager resources</a>:</p><p><ul><li><code>Orders Full Access</code></li><li><code>Change order</code></li></ul></p> |
+
+## Price changes
+
+When a change to an order item increases or decreases the original amount of the purchase, the **Orders** module automatically communicates with **Payments** as follows:
+
+- **Lower price after a change:** A notification is sent to the payment [gateway](https://help.vtex.com/en/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#gateway) to refund the customer.
+- **Higher price after a change:** A notification is sent to the payment gateway to request the customer to pay the additional amount.
+
+See the table below for more information on payment and invoicing when changing orders:
+
+| **Characteristic** | **Description** |
+|:---:|:--- |
+| Conditions for increasing the order amount | <p>You can only increase the amount of an order when it meets the following criteria:</p><p><ul><li>The order was placed using credit card, <a href="https://help.vtex.com/en/tutorial/setting-up-payments-notes--5pW7avTwtyQcMu4uiW8quQ">notes payable</a> or <a href="https://help.vtex.com/en/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0">customer credit</a>.</li><li>The order <a href="https://help.vtex.com/en/tutorial/what-is-an-acquirer--7N1oRTG8dGmOiIugC0cs4E">acquirer</a> allows transactions without the CVV code.</li><li>The order acquirer allows two billing transactions for the same order.</li></ul></p><p>If the <a href="https://help.vtex.com/en/tutorial/o-que-e-conector--3lze0Cu0bmyC6u2o2iaeEA">connector</a> does not allow changes for higher amounts, a new transaction will be processed for the excess value, and the transaction will not be linked to the original order.</p> |
+| Change of settled order | <p>In the <a href="https://help.vtex.com/en/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/1xjzgJZvqwaI1rfxLMCC3Y">transaction flow</a>, the order can be changed to <code>settled</code>, provided it meets the following conditions:</p><p><ul><li>The order was placed using a credit card.</li><li>Payment is settled before the order is <a href="https://help.vtex.com/en/tutorial/como-faturar-um-pedido--7p1h852V5t54KyscpgxE2v">invoiced</a>.</li><li>The payment connector is configured to allow partial refunds. <a href="https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv">Adyen</a> is currently the only payment connector that supports this operation.</li></ul></p><p>Orders with the transaction status <code>finished</code> cannot be changed.</p> |
+| Shared transaction betweensellers and marketplace | You can change orders with more than one seller and payment in marketplaces, i. e., in <a href="https://help.vtex.com/en/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx">split payment</a> scenarios. |
+| Discounts | You cannot change an order by applying discounts greater than or equal to the total amount of the original order. |
+| Invoice | <p>For <a href="https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT">invoices</a>, order changes behave as follows:</p><p><ul><li>If the order has already been <a href="https://help.vtex.com/en/tutorial/como-faturar-um-pedido--7p1h852V5t54KyscpgxE2v">invoiced</a> in full, it can no longer be changed.</li><li>Orders not yet invoiced or only <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partially invoiced</a> can be changed.</li><li>The amount of partial invoices for the changed order must be equal to or greater than the amount of an invoice already issued.</li><li>If the total amount of the changed order is lower than the amount of an invoice that has already been issued, it cannot be changed.</li></ul></p><p>In general, it is the invoicing of the order that triggers payment settlement. However, this behavior is different for stores with <a href="https://help.vtex.com/en/tutorial/configuring-maximum-automatic-payment-settlement-time-frame--7dwcaxrcgcFJUk7umqPBw2">automatic settlement</a> configured.</p> |
+
diff --git a/docs/tutorials/en/how-dns-configuration-works-on-vtex.md b/docs/tutorials/en/how-dns-configuration-works-on-vtex.md
new file mode 100644
index 000000000..da570cba9
--- /dev/null
+++ b/docs/tutorials/en/how-dns-configuration-works-on-vtex.md
@@ -0,0 +1,36 @@
+---
+title: '​​How DNS configuration works on VTEX'
+id: 2P5k3oMYOj7TgSK4Mrxmgy
+status: PUBLISHED
+createdAt: 2024-01-23T16:53:52.076Z
+updatedAt: 2024-01-23T17:00:29.714Z
+publishedAt: 2024-01-23T17:00:29.714Z
+firstPublishedAt: 2024-01-23T16:58:57.454Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: how-dns-configuration-works-on-vtex
+locale: en
+legacySlug: how-dns-configuration-works-on-vtex
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+DNS configuration is an essential step for your store's go-live. On VTEX, a specific configuration of the DNS system (_Domain Name System_) is required for the store to operate properly. DNS is the system that translates domain names (such as `mystore.com`) into IP addresses of servers that store the files needed to display a web page.
+
+To configure DNS, you must create a [CNAME](https://www.cloudflare.com/pt-br/learning/dns/dns-records/dns-cname-record/) for your store's main domain, directing it to `{mainDomain}.cdn.vtex.com`. For example, for a store with the main domain `www.mystore.com`, you should create a CNAME pointing to `www.mystore.com.cdn.vtex.com`.
+
+Redirects work in stages:
+
+1. The CNAME created by your team routes the store traffic to a specific location within the VTEX infrastructure.
+
+   `www.mystore.com` 🠖 `CNAME `🠖 `www.mystore.com.cdn.vtex.com`
+2. Internally, VTEX configures a second CNAME that directs to the Azion or CloudFront service.
+
+   `www.mystore.com.cdn.vtex.com` 🠖 `CNAME` 🠖 `uug412qft7.map.azionedge.net`
+3. Finally, a type A redirect routes the Azion/CloudFront service to a specific IP address.
+
+   `uug412qft7.map.azionedge.net` 🠖 `A` (record type containing an IP address) 🠖 `185.76.11.52`
+
+These settings ensure the resolved IP address is dynamic and can change anytime. This is because this IP address adapts to match the CDN (Content Delivery Network) server closest to the visitor's location. This adaptation improves the site's performance, as files are delivered from servers geographically closer to the visitor.
+
+Learn more about DNS configuration on VTEX by reading the [Go-live](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj) article.
diff --git a/docs/tutorials/en/how-do-i-terminate-my-contract-with-vtex.md b/docs/tutorials/en/how-do-i-terminate-my-contract-with-vtex.md
index a7cdbba94..21364fc6f 100644
--- a/docs/tutorials/en/how-do-i-terminate-my-contract-with-vtex.md
+++ b/docs/tutorials/en/how-do-i-terminate-my-contract-with-vtex.md
@@ -3,19 +3,19 @@ title: 'How do I terminate my contract with VTEX?'
 id: HhPeg8EOismMSImoWwaI8
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:36.822Z
-updatedAt: 2019-12-31T15:22:44.073Z
-publishedAt: 2019-12-31T15:22:44.073Z
+updatedAt: 2024-01-18T16:03:47.790Z
+publishedAt: 2024-01-18T16:03:47.790Z
 firstPublishedAt: 2019-01-24T22:00:07.201Z
 contentType: tutorial
 productTeam: Financial
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: how-do-i-terminate-my-contract-with-vtex
 locale: en
 legacySlug: how-do-i-terminate-my-contract-with-vtex
 subcategory: 6SJnrkKDjGwSqKkMuQMOmm
 ---
 
-In order to terminate your agreement and to stop using VTEX platform, you must open a [ticket](https://support.vtex.com/hc/en-us/requests) communicating your decision to the financial team.
+In order to terminate your agreement and to stop using VTEX platform, you must open a [ticket](https://help.vtex.com/en/support) communicating your decision to the financial team.
 
 ## Make sure that your ticket contains the following information:
 
@@ -25,4 +25,4 @@ In order to terminate your agreement and to stop using VTEX platform, you must o
 
 Once this is done, the internal process will be started and then a distraction for electronic signature will be sent via __Clicksign__.
 
-If the client's desire for termination is confirmed, __no fine will be charged.__ The last charge made will correspond to the month of the request for termination. Your administrative panel will be __removed within the first 5 days of the month following the request__.
+If the customer's desire for termination is confirmed, the __prior notice and fine clauses will be verified and charged on the customer's billing.__ Your administrative panel will be __removed within the first 5 days of the month following the request__.
diff --git a/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index f358a847f..788dc3916 100644
--- a/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -32,16 +32,16 @@ You can change the protocol in all folders at once by using our API, documented
 2. Access **Sites and channels**.
 3. Access the desired website.
 4. Open the root folder of the website.
-![CMS instrução - EN](https://images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
+![CMS instrução - EN](//images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
 5. The screen that was opened displays all the folders that are on the first level of the site. For each pertinent folder, click **Edit** - for home, consider the top button;
-![edit cms - EN](https://images.ctfassets.net/alneenqid6w5/6ijmcqCYCIOmi2oeSSEaiy/c6f229d2a4727d5fbeb368e6b8282b2f/edit_CMS_EN.png)
+![edit cms - EN](//images.ctfassets.net/alneenqid6w5/6ijmcqCYCIOmi2oeSSEaiy/c6f229d2a4727d5fbeb368e6b8282b2f/edit_CMS_EN.png)
 6. In the checkbox **Protocol**, select the option **HTTPS**;
-![cms-protocol-https EN](https://images.ctfassets.net/alneenqid6w5/6QfX3kETJeqI2Iu0wKECys/2296b1dff11262501fbc20b2ff70afe2/cms_protocol_HTTPS_EN.png)
+![cms-protocol-https EN](//images.ctfassets.net/alneenqid6w5/6QfX3kETJeqI2Iu0wKECys/2296b1dff11262501fbc20b2ff70afe2/cms_protocol_HTTPS_EN.png)
 7. Click in **Save Folder**.
 
 Attention to folders that have subfolders, such as Departamento, Categoria, Produto, and other folders, including also those created for store customization. 
 
 In the following example, the folder **Orders**, contained in **Account**, which also must be edited: 
-![cms-subcategoria-edit EN](https://images.ctfassets.net/alneenqid6w5/6ugtIHxBSgMMeMgCeA040c/51521187a54845179835e410d76294d4/subcategoria_edit_EN.png)
+![cms-subcategoria-edit EN](//images.ctfassets.net/alneenqid6w5/6ugtIHxBSgMMeMgCeA040c/51521187a54845179835e410d76294d4/subcategoria_edit_EN.png)
 
 After a cache of up to 10 minutes the changes will take effect.
diff --git a/docs/tutorials/en/how-do-reversals-work-when-an-item-is-returned.md b/docs/tutorials/en/how-do-reversals-work-when-an-item-is-returned.md
index bc6e309ee..9a4e138dd 100644
--- a/docs/tutorials/en/how-do-reversals-work-when-an-item-is-returned.md
+++ b/docs/tutorials/en/how-do-reversals-work-when-an-item-is-returned.md
@@ -3,8 +3,8 @@ title: 'Refund function when item is returned'
 id: frequentlyAskedQuestions_298
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.904Z
-updatedAt: 2021-08-12T18:29:59.905Z
-publishedAt: 2021-08-12T18:29:59.905Z
+updatedAt: 2024-02-28T17:25:13.906Z
+publishedAt: 2024-02-28T17:25:13.906Z
 firstPublishedAt: 2019-01-24T21:55:16.859Z
 contentType: tutorial
 productTeam: Financial
@@ -17,7 +17,7 @@ subcategory: 3Gdgj9qfu8mO0c0S4Ukmsu
 
 When a request is made for the [partial or total return of items](/en/tutorial/returning-order-items) in orders paid using a credit card or other payments **except "boleto"** (popular Brazilian off-line payment method), the Orders Management contacts Payments requesting the chargeback for the items to be returned.
 
-In such cases, VTEX sends the refund to the acquirer when the value has already been billed (`Billed` status). It works in the following way: VTEX gets in touch with the acquirer and tries to solve the refund online as soon as possible.
+In such cases, VTEX sends the refund to the acquirer when the value has already been billed (`Invoiced` status). It works in the following way: VTEX gets in touch with the acquirer and tries to solve the refund online as soon as possible.
 
 However, if this operation is not successful, an [e-mail notification](/en/tutorial/how-to-configure-notifications/) will be sent, informing the retailer to get in touch with the acquirer in order to make the automatic refund.
 
diff --git a/docs/tutorials/en/how-does-promotion-proration-work.md b/docs/tutorials/en/how-does-promotion-proration-work.md
index 1253dbd01..22006422b 100644
--- a/docs/tutorials/en/how-does-promotion-proration-work.md
+++ b/docs/tutorials/en/how-does-promotion-proration-work.md
@@ -38,7 +38,7 @@ Let's say a nominal discount promotion of US$ 156.00 will be applied to a cart w
 
 Considering the calculation logic above, the proration would be like this:
 
-![tabelaex.en](https://images.ctfassets.net/alneenqid6w5/2mLv3HI7hgSRXkGyNwQRtT/1e529a7d90cc02e13cfdf07f488f56e8/tabelaex.en.png)
+![tabelaex.en](//images.ctfassets.net/alneenqid6w5/2mLv3HI7hgSRXkGyNwQRtT/1e529a7d90cc02e13cfdf07f488f56e8/tabelaex.en.png)
 
 
 This calculation is applied to unitary products, such as a blouse or a table, but some products have a configuration called multiplier unit, such as a floor box with 2.5 m², for example.
diff --git a/docs/tutorials/en/how-does-reservation-work.md b/docs/tutorials/en/how-does-reservation-work.md
index 8888f7563..1aa9e74dd 100644
--- a/docs/tutorials/en/how-does-reservation-work.md
+++ b/docs/tutorials/en/how-does-reservation-work.md
@@ -3,8 +3,8 @@ title: 'How the reservation works'
 id: tutorials_92
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:56.753Z
-updatedAt: 2023-04-28T22:58:58.294Z
-publishedAt: 2023-04-28T22:58:58.294Z
+updatedAt: 2023-10-18T17:20:21.911Z
+publishedAt: 2023-10-18T17:20:21.911Z
 firstPublishedAt: 2017-04-27T23:00:42.751Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -43,7 +43,7 @@ The item remains with this status for a certain time, and if payment is not conf
 
 _Payment expiration period + inventory reservation period_
 
-- **Payment expiration period:** the time period (in days) in which the payment must be made. You can configure this period in the **[Payments](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB)** module for payments with boleto (Brazilian offline payment method) or [notes payable](https://help.vtex.com/en/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ#promissory-setup). For other payment methods, such as credit card and wallet, no time limit for payment expiration can be specified. The payment flow starts right after checkout, and the payment can be approved or denied in different time periods, depending on the selected payment method.
+- **Payment expiration period:** the time period (in days) in which the payment must be made. You can configure this period in the **[Payments](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB)** module for payments with boleto (Brazilian offline payment method) or [notes payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ#notes-payable-setup). For other payment methods, such as credit card and wallet, no time limit for payment expiration can be specified. The payment flow starts right after checkout, and the payment can be approved or denied in different time periods, depending on the selected payment method.
 - **Inventory reservation period:** is set automatically, following the rules below.
     - **four calendar days:** when the payment is due on a Sunday, Monday or Tuesday.
     - **five calendar days:** when the payment is due on a Wednesday, Thursday or Friday.
diff --git a/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index 5c51a4d60..7e26f4ac0 100644
--- a/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -29,7 +29,7 @@ Instead of using the IDs of each item (which would generate separate orders in o
 
 You can find both IDs through the report generated on the integration's panel on VTEX Admin.
 
-![mercalo-livre-pedido-id-en](https://images.ctfassets.net/alneenqid6w5/5CZg21BumbrNw5QjimjuGt/67fefe0993b7ca80eb365428f389fd4d/mercalo-livre-pedido-id.png)
+![mercalo-livre-pedido-id-en](//images.ctfassets.net/alneenqid6w5/5CZg21BumbrNw5QjimjuGt/67fefe0993b7ca80eb365428f389fd4d/mercalo-livre-pedido-id.png)
 
 
 <div class="alert alert-warning">
diff --git a/docs/tutorials/en/how-does-the-delivery-flow-work.md b/docs/tutorials/en/how-does-the-delivery-flow-work.md
index a733d1a9a..8959e64ac 100644
--- a/docs/tutorials/en/how-does-the-delivery-flow-work.md
+++ b/docs/tutorials/en/how-does-the-delivery-flow-work.md
@@ -27,4 +27,4 @@ VTEX platform gives you the freedom to use these settings in a variety of ways,
 
 But for now, let's stick to the most basic scenario, illustrated by the image below:
 
-![Logistics Concept English](https://images.ctfassets.net/alneenqid6w5/4dxX4SvwV2SuCekgeM480w/2a69059d4efd30c0610ef04df02cc49c/Component__19_.png)
+![Logistics Concept English](//images.ctfassets.net/alneenqid6w5/4dxX4SvwV2SuCekgeM480w/2a69059d4efd30c0610ef04df02cc49c/Component__19_.png)
diff --git a/docs/tutorials/en/how-does-the-score-field-work.md b/docs/tutorials/en/how-does-the-score-field-work.md
index 8b0a99b9b..d5ac8b31e 100644
--- a/docs/tutorials/en/how-does-the-score-field-work.md
+++ b/docs/tutorials/en/how-does-the-score-field-work.md
@@ -3,36 +3,54 @@ title: 'How does the Score field work?'
 id: 1BUZC0mBYEEIUgeQYAKcae
 status: PUBLISHED
 createdAt: 2018-02-16T16:17:51.610Z
-updatedAt: 2023-03-27T13:32:27.264Z
-publishedAt: 2023-03-27T13:32:27.264Z
+updatedAt: 2024-01-05T20:42:03.525Z
+publishedAt: 2024-01-05T20:42:03.525Z
 firstPublishedAt: 2018-02-16T18:09:11.291Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 1malnhMX0vPThsaJaZMYm2
 slug: how-does-the-score-field-work
 locale: en
 legacySlug: how-does-the-score-field-work
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-The __Score__ field, available for __Product__, __Category__ and __Brand__, is the value used to ensure the ordering of products in your store, and is also used as a tie-breaking criterion for other ordering options, such as lower price, better discount etc. By filling in this field, you can define the priority of some products over others, both on the storefront and on the search results page.
+The **Score** field, available in the **Product**, **Category**, and **Brand** forms, is the value used to sort your store products. This score works as a tie-breaking criterion for other sorting options, such as lower price, best discount, and others. By completing the **Score** field, you can define the priority of some products over others, both in the window display and in the search results page.
 
-The field enumeration criterion follows a simple ordering (1, 2, 3, 4...), and it only needs to be followed in order to display the sequence in the storefront or on the search results page. 
+The criterion for listing the field follows a numerical order to display the sequence in the window display or on the search results page. By default, products without a score will behave as if they had a 0 score.
 
-However, when it comes to product score, it is important to know that it is the __sum of your own score plus those of category and brand__. That is: `Product score + category score + brand score`.
+A product's total score is the sum of its own score plus the scores defined for the category and brand: `total product score = product score + category score + brand score`.
 
-You can use the following parameters to implement the ordering:
+We recommend defining the score at the product level, as your window display constantly changes.
 
-- __Ascending order:__ `?O=OrderByScoreASC`
-- __Descending order:__ `?O=OrderByScoreDESC`
+For example, you could use the score for specific events, such as when your store needs to display some products rather than others to ensure their visibility.
 
-It is best to enter the product score one by one, as your storefront probably changes constantly.
+## Score in the VTEX search
 
-A good example for the use of the score field is in specific events, like when your store needs to position certain products before others to ensure they are seen.
+If your store uses the [VTEX search](https://help.vtex.com/en/tutorial/como-funciona-a-busca-da-vtex--tutorials_542), you can use the parameters below to implement sorting by score:
+
+- **Ascending order **(products with lower scores are displayed at the top)**:** `?O=OrderByScoreASC`
+- **Descending order **(products with the highest score are displayed at the top)**:** `?O=OrderByScoreDESC`
+
+## Score in VTEX Intelligent Search
+
+The `OrderByScoreASC` and `OrderByScoreDESC` parameters are not supported by[ VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb), only by the [VTEX search](https://help.vtex.com/en/tutorial/como-funciona-a-busca-da-vtex--tutorials_542).
+
+[VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb) does not allow direct sorting of products by the score defined in the **Score** field. When using one of these parameters in VTEX Intelligent Search, the default sorting will be by[ relevance](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+However, the Catalog score composes Intelligent Search's [relevance](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) among the other criteria, allowing it to be given greater weight or even prioritized. Thus, the higher the score, the greater the weight, i.e., the behavior is descending: products with a higher score are prioritized.
+
+Disregarding other criteria or even considering priority sorting, in VTEX Intelligent Search, products with no score are displayed after products with a score in the search results.
+
+You need to consider whether this would be appropriate for your use case compared to other criteria calculated automatically by the system, such as popularity and sales. Making one criterion a priority overrides all the others, even meeting the same objective as `OrderByScore`, bypassing the other relevance settings.
+
+To sort items manually one by one, we recommend using[ Merchandising Rules](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) to avoid undesirable effects and respect the relevance settings.
+
+## Editing a product score
 
 To add or change a score related to a product, please follow these steps:
 
-1. In VTEX Admin, go to **Catalog > Products & Skus**.
-2. Click on `Add Product` to create a new product or click on `Update` on the product you want to edit.
-3. Enter the desired score value in the **Score field**.
+1. In the VTEX Admin, go to **Catalog > Products & SKUs**.
+2. Click Add Product to create a new product, or click Edit product in the options of the product you want to edit.
+3. Enter the desired score value in the **Score field (used for sorting the search)**.
 
diff --git a/docs/tutorials/en/how-does-the-type-of-delivery-work.md b/docs/tutorials/en/how-does-the-type-of-delivery-work.md
index 6e5476fa3..c700ca12a 100644
--- a/docs/tutorials/en/how-does-the-type-of-delivery-work.md
+++ b/docs/tutorials/en/how-does-the-type-of-delivery-work.md
@@ -3,8 +3,8 @@ title: 'How does the type of delivery work?'
 id: tutorials_126
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:17.250Z
-updatedAt: 2023-05-31T14:45:20.914Z
-publishedAt: 2023-05-31T14:45:20.914Z
+updatedAt: 2023-11-13T15:00:10.346Z
+publishedAt: 2023-11-13T15:00:10.346Z
 firstPublishedAt: 2017-04-27T23:00:44.173Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -29,7 +29,7 @@ On the cart area, the delivery options are separated by shipping type, not by ca
 
 The following picture shows how the shipping options would be displayed on the checkout according to the example mentioned before: 
 
-![Transportadoras Checkout EN](https://images.ctfassets.net/alneenqid6w5/4cCgmqCPRS8ou84UOuQege/53fdf91f37084eedf58eb9b0def2c355/Transportadoras_Checkout_EN.png)
+![Transportadoras Checkout EN](//images.ctfassets.net/alneenqid6w5/4cCgmqCPRS8ou84UOuQege/53fdf91f37084eedf58eb9b0def2c355/Transportadoras_Checkout_EN.png)
 
 Notice that, even though five carriers are registered (in the **Regular** and **Express** categories), only two freight options are displayed to the customer. This is not because the other carriers do not fulfill the cart requirement, but because, within the same type of freight, only the carrier with the lowest price or the shortest delivery time will be displayed.
 
diff --git a/docs/tutorials/en/how-does-vtex-search-work.md b/docs/tutorials/en/how-does-vtex-search-work.md
index 986c807dd..b5cb98574 100644
--- a/docs/tutorials/en/how-does-vtex-search-work.md
+++ b/docs/tutorials/en/how-does-vtex-search-work.md
@@ -73,7 +73,7 @@ To understand VTEX search, we must first become familiar with the indexer and it
 
 The catalog indexer is a quick access scalable database, with configurable algorithms for result prioritization. It is positioned between conventional database and user. See the outline below:
 
-![database](https://images.ctfassets.net/alneenqid6w5/5ACXw5iwhZP4iT1DwuEVOi/3c3b66551bf05d00042ed3babdfc004f/database.JPG)
+![database](//images.ctfassets.net/alneenqid6w5/5ACXw5iwhZP4iT1DwuEVOi/3c3b66551bf05d00042ed3babdfc004f/database.JPG)
 
 The indexer contains all the information referring to the product catalog (products, SKUs, brands, departments, categories). The search engine uses this information to locate products and to display these in shop windows and search results. However, __only already indexed products can be found by the search__.
 
diff --git a/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md b/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md
index 36819908d..711dcfa4b 100644
--- a/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md
+++ b/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md
@@ -21,6 +21,6 @@ The discount calculation goes like this: `monthly fee divided by the number of d
 
 So if your monthly payment had a value of $ 750 in May - 31 days - and you hired VTEX on May 6, you would be deducted $ 145.16 on your next bill.
 
-![prorata PT](https://images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
+![prorata PT](//images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
 
 The calculation was: `$ 750/31 = $ 24,19 x 3 (days) = $ 145,16`
diff --git a/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md b/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md
index a8b6ff556..d522a9e0e 100644
--- a/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md
+++ b/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md
@@ -3,8 +3,8 @@ title: 'How is the order delivery deadline calculated?'
 id: 1TOuKCIjGQmqOqQkEqCg82
 status: PUBLISHED
 createdAt: 2018-01-12T12:56:52.805Z
-updatedAt: 2023-03-29T14:09:06.429Z
-publishedAt: 2023-03-29T14:09:06.429Z
+updatedAt: 2023-09-23T00:34:19.034Z
+publishedAt: 2023-09-23T00:34:19.034Z
 firstPublishedAt: 2018-01-12T14:42:26.502Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,27 +15,22 @@ legacySlug: how-is-the-order-delivery-deadline-calculated
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-The deadline for delivering an order takes into account the "cost periods" defined for the five stages of the logistics route:
-- Stock.
-- Dock.
-- Carrier.
-- Holidays.
-- Cut-off times.
+The shipping time calculation for an order takes into account the following aspects:
 
-That is, for each of these steps you can define a detention time - and the delivery time that your customer will see at the checkout is the sum of these cost times.
+- [Lead time](https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B)
+- [Warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+- [Dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
+- [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
 
-![deliveryCostTimes](//images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
+![lead_time_image_total_time_EN](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
 
-The detention time for the __stock__ and __dock__ are defined in the setting screens of each of these steps, in **Shipping > Shipping Strategy.**
+You configure e time frame for each one of them and what your customer sees at checkout is a shipping time calculated adding those configurationn.
 
-![entrega1.en](https://images.ctfassets.net/alneenqid6w5/39bRRLzf4nv4V0EpDe71cQ/ae7546c90db3697294b9fc499a80dd81/entrega1.en.png) 
+The __carriers__ shipping time is defined in the [freight table](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127), which has to be associated to your shipping strategy through a [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140).
 
-![entrega2.en](https://images.ctfassets.net/alneenqid6w5/23DgHkimiBcH2alWZEQyYI/b9b78b5cbddaa2efa0a218122ab818ad/entrega2.en.png)
+To configure shipping policies, warehouses an docks, go to your VTEX Admin, in **Shipping > Shipping Strategy**. In this page, there a tab for each. If you want to configure lead time, go to **Catalog > Inventory Management**.
 
-The detention cost of the __carrier__ is defined in the freight table, sent to VTEX through the carrier configuration screen, also in the **Shipping Strategy > Shipping policy** tab.
+### Know more
 
-![entrega3.en](https://images.ctfassets.net/alneenqid6w5/lFStGX80SPEuAWnVwt2eK/ca241929a087956172dedc1097559871/entrega3.en.png)
-
-### Go further
-
-Through freight simulation, you can check how the delivery time for a specific order has been calculated. Understand how in the article [Checking how an order delivery deadline was calculated](/en/tutorial/checking-how-an-order-delivery-deadline-was-calculated).
+- [Shipping Simulator](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+- [Checking how an order delivery deadline was calculated](https://help.vtex.com/en/tutorial/verificar-como-o-prazo-de-entrega-de-um-pedido-foi-calculado).
diff --git a/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md b/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md
index c541ba467..808eb80d4 100644
--- a/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md
+++ b/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md
@@ -3,8 +3,8 @@ title: 'How is the platform’s operation SLA determined?'
 id: frequentlyAskedQuestions_662
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:57.436Z
-updatedAt: 2019-12-31T17:00:45.718Z
-publishedAt: 2019-12-31T17:00:45.718Z
+updatedAt: 2024-03-11T22:38:31.694Z
+publishedAt: 2024-03-11T22:38:31.694Z
 firstPublishedAt: 2019-01-24T22:11:03.028Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,26 +15,26 @@ legacySlug: how-is-the-platforms-operation-sla-determined
 subcategory: 5PYkoNDZyo2G80yiiqG2YW
 ---
 
-In addition to the deadlines, you must identify what we consider to be a violation of the SLA. That is, what will really be considered as unavailability time.
+Any minute of interruption can be costly, both for the stores and for VTEX. Therefore, we try to be as transparent as possible regarding the health of our platform. We provide the [VTEX Status] page (http://status.vtex.com), where we record all incidents that have impacted our SLA.
 
-Since our trade model is based on store returns, it is quite clear for the VTEX team that an interruption of 1 minute costs a lot for both the stores and VTEX itself. Accordingly, we try to be as transparent as possible regarding the health of our platform. See the [status page](http://status.vtex.com "status page") for a description of all incidents that impacted our SLA. Such events are accounted for as follows:
+To determine SLA violations, i.e. to account for platform downtime, we consider the following events:
 
-### Events accounted for
+- Interruptions in the online store that significantly affect the number of orders placed, for example: store outage, slow access, checkout failure.
+- Interruptions lasting at least 10 minutes.
 
-- Interruptions in the virtual stores that may significantly impact the number of orders made. E.g.: store outage, slow access, checkout failure.
-- We account for interruptions with duration of no less than 10 minutes.
+<div class="alert alert-warning">
+  <p>We do not count scheduled maintenance as downtime.</p>
+</div>
 
-### Events not accounted for
+### Checking VTEX status
 
-- Scheduled maintenance.
-- Interruption of administrative module services.
+To identify unstable scenarios, we recommend checking the [VTEX Status](https://status.vtex.com) page if you suspect that the platform is unavailable. The status is updated when the incident has passed the 10-minute mark, with the following information:
 
-### Checking the status
+- __Investigating/Identified__: The team is investigating the incident and carrying out the necessary actions to restore the service.
+- __Monitoring__: The incident has been resolved and the service stabilized. The environment is being monitored.
+- __Resolved__: Case closed, with total SLA interruption time recorded. In most cases, the total interruption time is the sum of the incident's downtime.
 
-To facilitate the identification of such scenarios, we always recommend checking the status when there is a suspicion that the tool is not available. When the incident surpasses 10 minutes, the status is updated with the following information:
+## Learn more
 
-- __Investigating/Identifying__: the incident is being investigated by the team. The team is taking the actions required to restore services.
-- __Monitoring__: The incident was resolved, and the service was restored. The environment is being monitored.
-- __Resolved__: Case closed. Total outage time has been recorded. In most cases, the SLA is the sum of the unavailability time for all incidents.
+- [VTEX status page](https://help.vtex.com/en/tutorial/vtex-status-page--gPhqDn9IQ3c67wbJEX3JJ)
 
-![](//images.contentful.com/alneenqid6w5/2Le8koNu7YUoICaquSSuuY/134a3f2ca7cee4614a09c96397573dd9/Screen_Shot_2016-04-22_at_16.28.39.png)
diff --git a/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md b/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
index 486050881..39a1bebb2 100644
--- a/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
+++ b/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
@@ -3,8 +3,8 @@ title: 'How long does it take to cancel an order with an unpaid "boleto"?'
 id: frequentlyAskedQuestions_300
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.983Z
-updatedAt: 2021-10-28T11:55:41.026Z
-publishedAt: 2021-10-28T11:55:41.026Z
+updatedAt: 2024-06-11T21:26:30.893Z
+publishedAt: 2024-06-11T21:26:30.893Z
 firstPublishedAt: 2019-01-24T22:03:31.971Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/how-my-account-works.md b/docs/tutorials/en/how-my-account-works.md
index f8f2497f9..8292cb5b3 100644
--- a/docs/tutorials/en/how-my-account-works.md
+++ b/docs/tutorials/en/how-my-account-works.md
@@ -3,8 +3,8 @@ title: 'How My Account works'
 id: 2BQ3GiqhqGJTXsWVuio3Xh
 status: PUBLISHED
 createdAt: 2019-04-11T21:14:26.117Z
-updatedAt: 2023-04-24T23:39:56.581Z
-publishedAt: 2023-04-24T23:39:56.581Z
+updatedAt: 2023-12-21T14:09:42.863Z
+publishedAt: 2023-12-21T14:09:42.863Z
 firstPublishedAt: 2019-05-21T19:48:15.019Z
 contentType: tutorial
 productTeam: Identity
@@ -34,7 +34,7 @@ To learn about <b>My Account</b> customization, see our developer documentation
 
 In this section, customers can manage their personal data saved in the store. They can [edit their profile information](#edit),[ set a new password](#password), and [choose whether to receive emails with promotions](#newsletter).
 
-![profile EN](https://images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/a9f2ca072b2a08cb6cb1bc196b9c9f1e/profile_EN.png)
+![profile EN](//images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/a9f2ca072b2a08cb6cb1bc196b9c9f1e/profile_EN.png)
 
 ### Edit
 
@@ -77,9 +77,13 @@ The `Add address` button allows customers to include new addresses besides the o
 
 ## Orders
 
+<div class = "alert alert-info">
+In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
+</div>
+
 This section displays a list of all orders placed by the customer in your store. The list is sorted by creation date and displays details such as order date, total price of the order, order ID, status, and items purchased.
 
-![orders EN](https://images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/29e797af3e99000a06d906bf5e3ae0d1/orders_EN.png)
+![orders EN](//images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/29e797af3e99000a06d906bf5e3ae0d1/orders_EN.png)
 
 The **Orders** section allows customers to track the progress of their orders and offers options such as cancel or change orders. See below all available options.
 
@@ -103,7 +107,7 @@ By clicking on an order in the list, the customer will be able to view the detai
 
 Customers can also use the option [Order again](#order-again) in this page. By clicking on [More options](#more-options), the [Change order](#change-order) and [Request cancellation](#request-cancellation) features will be displayed (if enabled in your store and the order is in the `Handling shipping` status).
 
-![order details EN](https://images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/ee071c1cc75a884c9daecb85072d3453/order_details_EN.png)
+![order details EN](//images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/ee071c1cc75a884c9daecb85072d3453/order_details_EN.png)
 
 #### Change order
 
@@ -115,7 +119,12 @@ The `More options` button allows customers to change their order information, su
 
 ## Credit cards
 
-In the **Credit cards** section, the customer has autonomy to manage credit cards in their account. They can include and edit the credit card data saved at checkout. To add new cards, follow the steps below:
+In the **Credit cards** section, the customer has autonomy to manage the credit cards related to his account through the following actions:
+
+- Add new cards
+- Remove cards with an expired expiration date
+
+To add new cards, follow the steps below:
 
 1. Open **My Account** in the store.
 2. Click the **Credit cards** tab.
@@ -125,7 +134,7 @@ In the **Credit cards** section, the customer has autonomy to manage credit card
 6. Solve the reCaptcha challenge.
 7. The card validation process will happen automatically. If there is no problem, you will be redirected to the card list and the new card will appear on the list.
 
-![Card ReCaptcha](https://images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/ab1e37db8b01f154e80f8d2f4f562d7d/Card_ReCaptcha_EN.gif)
+![Card ReCaptcha](//images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/ab1e37db8b01f154e80f8d2f4f562d7d/Card_ReCaptcha_EN.gif)
 
 However, there are limitations for stores using [3DS](https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) authentication (V1 or V2) in their acquirers:
 
@@ -147,7 +156,7 @@ In this section, customers can manage all their subscriptions, as well as modify
 
 This section can be accessed on the left side menu by clicking on **Authentication** in the user profile settings. It offers options for password and session management.
 
-![My Authentication app EN](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
+![My Authentication app EN](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
 
 ### Password management
 
@@ -157,7 +166,7 @@ The **Password** component allows users to create their passwords, if they do no
 2. In the **Code** field, enter the verification code received by email.
 3. In the **New password** field, enter a new password. Below those fields, you will see the requirements for setting a valid password. As the user types the password meeting those requirements, their symbols will change from red to green. The password will be valid only if all symbols are green.
 4. Once you have entered a valid password, click on the `SAVE PASSWORD` button.  
-![My Authentication create password EN](https://images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/fb226bc32cfc48422cec830332d10762/My_Authentication_create_password_EN.png)
+![My Authentication create password EN](//images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/fb226bc32cfc48422cec830332d10762/My_Authentication_create_password_EN.png)
 
 To change an existing password, follow the instructions below:
 
@@ -165,7 +174,7 @@ To change an existing password, follow the instructions below:
 2. Enter the current password in the corresponding field.
 3. Enter the new password in the corresponding field, following all the requirements.
 4. Click on `SAVE PASSWORD`.
-![My Authentication change password EN](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/4a055c06066c293502ffb9652d220c93/My_Authentication_change_password_EN.png)
+![My Authentication change password EN](//images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/4a055c06066c293502ffb9652d220c93/My_Authentication_change_password_EN.png)
 
 <div class="alert alert-info">
 If you have forgotten your password, you cannot recover it using the option for resetting passwords. To recover your password, you must log out of your current session, try to log in using your email address and password, and click on <strong>I forgot my password</strong>.
@@ -179,7 +188,7 @@ To view active sessions, click on the `VIEW SESSIONS` button, and you will be re
 
 To revoke access from other sessions, click on the `LOG OUT` button of that session.
 
-![My Authentication Session Management EN](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
+![My Authentication Session Management EN](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
 
 ## Basic settings 
 
@@ -190,7 +199,7 @@ In **My Orders**, you determine which sections will be visible to the customer i
 * In **ORDERS**, the <a class="far fa-check-square"></a> _Visible_ option determines whether the customer has the [Orders](#orders) section to track their orders. 
 * In **ADDRESSES**, the <a class="far fa-check-square"></a> _Visible_ option defines whether the customer will have the [Addresses](#addresses) section with their address’ details.
 
-![vtex-my-account_EN](https://images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/9605097215fa1591bfc7e49de4b48735/vtex-my-account_EN.png)
+![vtex-my-account_EN](//images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/9605097215fa1591bfc7e49de4b48735/vtex-my-account_EN.png)
 
 By default, the **CARDS** and **ORDERS** options are configured as visible. To change these settings or enable others, follow the steps below: 
 
diff --git a/docs/tutorials/en/how-order-authorization-works.md b/docs/tutorials/en/how-order-authorization-works.md
index 0e4e311bc..31263e9b2 100644
--- a/docs/tutorials/en/how-order-authorization-works.md
+++ b/docs/tutorials/en/how-order-authorization-works.md
@@ -3,8 +3,8 @@ title: 'How Order authorization works'
 id: 3MBK6CmKHAuUjMBieDU0pn
 status: PUBLISHED
 createdAt: 2019-03-25T17:18:05.295Z
-updatedAt: 2023-03-29T22:05:18.017Z
-publishedAt: 2023-03-29T22:05:18.017Z
+updatedAt: 2024-07-08T17:06:56.254Z
+publishedAt: 2024-07-08T17:06:56.254Z
 firstPublishedAt: 2019-03-25T17:24:44.319Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,7 +17,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 In the VTEX Admin, in **Store Settings > Orders > Order Authorization**, you can control and approve orders that have a price divergence in your store.
 
-![print_autorizacao_pedidos_EN](https://drive.google.com/uc?export=download&id=1lM96qEzJ1dAg-8gMy9x7Jn_4nC1QgrKc)
+![print_autorizacao_pedidos_EN](//images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/4fc80cda8d50acff5ed646a00dc5f01f/print_autorizacao_pedidos_EN.png)
 
 Price divergence errors may occur in two main scenarios:
 
diff --git a/docs/tutorials/en/how-order-authorization-workss.md b/docs/tutorials/en/how-order-authorization-workss.md
index 5bb84e9a9..c4527672b 100644
--- a/docs/tutorials/en/how-order-authorization-workss.md
+++ b/docs/tutorials/en/how-order-authorization-workss.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 In the Order Management module, __Order Authorization__ allows you to control approvals for orders in your store that have a price divergence.
 
-![autorização-de-pedidos EN](https://images.ctfassets.net/alneenqid6w5/2lbMgKkD1d4Bm7jJwPECqg/a8959ca6d3690c3a53d2e6a34fbc4fa6/autoriza____o-de-pedidos__EN.png)
+![autorização-de-pedidos EN](//images.ctfassets.net/alneenqid6w5/2lbMgKkD1d4Bm7jJwPECqg/a8959ca6d3690c3a53d2e6a34fbc4fa6/autoriza____o-de-pedidos__EN.png)
 
 This divergence in price between orders may occur in two main scenarios:
 
diff --git a/docs/tutorials/en/how-promotion-competition-works.md b/docs/tutorials/en/how-promotion-competition-works.md
new file mode 100644
index 000000000..00a840a85
--- /dev/null
+++ b/docs/tutorials/en/how-promotion-competition-works.md
@@ -0,0 +1,215 @@
+---
+title: 'How promotion competition works'
+id: tutorials_2270
+status: PUBLISHED
+createdAt: 2017-04-27T21:55:27.997Z
+updatedAt: 2023-11-14T16:52:38.320Z
+publishedAt: 2023-11-14T16:52:38.320Z
+firstPublishedAt: 2017-04-27T23:03:50.791Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 46G4yHIZerH7B9Jo0Iw5KI
+slug: how-promotion-competition-works
+locale: en
+legacySlug: understanding-competition-of-promotions
+subcategory: 1yTYB5p4b6iwMsUg8uieyq
+---
+
+The Promotions module uses a specific logic to determine which promotion should be applied to a purchase, similar to how the [Checkout](https://help.vtex.com/en/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) selects a seller to fulfill the order. This logic is called promotion competition.
+
+Promotion competition occurs in the following situations:
+
+- Promotions with the same type of discount.
+- More than one promotion applied to the same item.
+- Promotions not [configured](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restrictions-and-limitations-of-use) to allow cumulative promotions.
+
+To understand how the selection of the promotion that will be applied works, it's important to understand some concepts used in the Promotions module.
+
+- [Promotion effects](#promotion-effects)
+- [Promotion sorting rule](#promotion-sorting-rule)
+- [Cumulative promotions](#cumulative-promotions)
+- [Promotion competition strategies](#promotion-competition-strategies)
+
+## Promotion effects
+
+The promotion effects are related to the benefit the promotion offers. There are four types of benefits:
+
+- **Price discount:** Promotions that apply a percentage or nominal discount to the product price. This includes various discounts such as [regular promotions](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), [progressive discounts](https://help.vtex.com/en/tutorial/desconto-progressivo--tutorials_324), and any other mechanisms that affect the price of an item.
+- **Shipping discount:** [Promotions with a discount applied to the shipping cost.](https://help.vtex.com/en/tutorial/configurar-promocoes-de-frete--6Lo5BR61KMiUFAAHGCdgfW)
+- **Giveaway:** Promotions that offer one or more giveaways to the customer.
+- **Formula:** Promotions with nominal discount based on [formula](https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV), which is one of the options of a regular promotion.
+
+## Promotion sorting rule
+
+Sorting is the process that defines in which order promotions will be applied to the cart. This is important to understand the final price of the items in the shopping cart. The sorting rule is based on two criteria:
+
+- [Sorting by promotion and discount type](#sorting-by-promotion-and-discount-type)
+- [Sorting by discount amount](#sorting-by-discount-amount)
+
+### Sorting by promotion and discount type
+
+The promotions applied to the cart respect the following order:
+
+1. Percentage
+2. Nominal
+3. Maximum price
+4. Buy Together (not a regular promotion)
+5. Percentage shipping
+6. Nominal shipping
+7. Giveaway
+8. Formula
+
+### Sorting by discount amount
+
+Promotions of the same type applied to the cart are compared by their discount amount. At this point, the Promotions module always tries to apply the most advantageous promotion for the buyer.
+
+For giveaway promotions, the sorting is by the highest number of giveaways granted by the promotion.
+
+Example:
+
+- Promotion 1: 30% discount on the product price.
+- Promotion 2: 50% discount.
+
+Priority is given to the promotion that grants the highest discount, i.e., the cart will apply **Promotion 2** and then **Promotion 1**.
+
+The **Promotion 1** will be applied to the product price already discounted by **Promotion 2**.
+
+## Cumulative promotions
+
+Promotions that are [configured](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restrictions-and-limitations-of-use) to Apply with other promotions in this field will always be applied if their conditions are met, regardless of their type.
+
+However, they will be applied to the amount that has already been discounted by the promotion that won over non-cumulative promotions. The order of selected promotions will follow the sorting by type and value, as described in item 1. 
+
+Therefore, promotions will be applied in the following order:
+
+![promocao3 EN](//images.ctfassets.net/alneenqid6w5/6nz2KJuFk4aS0eU0OGg0sM/7cf285654ec80894e0a346c90918cd33/promocao3_EN.png)
+
+<div class="alert alert-warning">
+Orders originating from the <a href="https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> (provided by the store) or Fulfillment (delivered by the store) do not support cumulative promotions. This is because the use of promotions is restricted to specific types on both VTEX and external marketplaces.</div>
+
+## Promotion competition strategies
+
+After understanding how promotions are sorted and applied, you will be able to comprehend how non-cumulative promotions compete with each other.
+
+The selection of each promotion only considers promotions of the same discount type (as described in [Promotion effects](#promotion-effects)) that apply to at least one common product.
+
+Promotions that have different discount types, or that apply to different products, do not compete with each other. So they are automatically applied together.
+
+Here are the two strategies for promotion competition: 
+
+- [Competition by scenario](#competition-by-scenario)
+- [Competition by item](#competition-by-item)
+
+<div class="alert alert-info">
+By default, all accounts follow the competition by scenariostrategy. In case the competition by item strategy is better suited for your business needs, please <a href="https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">open a ticket</a> with our support team and request the change.</div>
+
+### Competition by scenario
+
+The competition by scenario follows the logic of grouping promotions that do not compete with each other on the same products. With each group created, a comparison is made to determine whether the group or an individual promotion offers a greater advantage to the customer. 
+
+The one that gives the best discount will be applied to the cart. See the examples below:
+
+#### Example 1
+
+James is planning to purchase a t-shirt priced at $10, with an additional $4 for shipping. Up to five promotions can be applied to the order. All applicable promotions were [configured](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restrictions-and-limitations-of-use) in the `Apply with other promotions` field as non-cumulative, except for the first one.
+
+| Cumulative promotions | Non-cumulative promotions |
+| ----------- | ----------- |
+| 10% off | Maximum shipping cost of $20 |
+| X | 80% off on the shipping cost |
+| X | Nominal discount of $5 |
+| X | Buy the shirt and get a giveaway |
+
+The cart will show a final price of $4.50 for the t-shirt and $0.80 for shipping. The promotion system starts by applying the promotion competition logic:
+
+- T-shirt: **$10**.
+   - Receives a nominal discount of *$5*. New price: **$5**. 
+
+- Shipping cost: **$4**.
+   - Receives a discount of *80%*. New price: **$0.80**.
+   - The maximum shipping cost of **$20** is applied but is not valid as the shipping cost is already below that.
+
+Then, cumulative promotions are applied:
+
+- T-shirt from ~~$10~~ now for **$5**.
+   - Receives a percentage discount of **10%**. New price: **$4.50**.
+
+Therefore, the final amounts for James' purchase are: 
+
+- T-shirt: **$4.50**.
+- Shipping cost: **$0.80**.
+- Giveaway for buying the t-shirt.
+
+#### Example 2
+
+Linda created a cart with 1 t-shirt and 1 pair of shoes. These items are part of collections:
+
+| Collection | Items | Prices |
+| ----------- | ----------- |  ----------- |
+| 1 | T-shirt | $ 10 |
+| 1 | Shoes | $ 50 |
+| 2 | T-shirt | $ 10 |
+
+- Promotions:
+   1. **10%** off on the first collection. Configured as non-cumulative in the `Apply with other promotions field`.
+   2. **25%** off on the second collection. Configured as non-cumulative in the `Apply with other promotions field`.
+   3. **5%** off on the product price. Configured as cumulative in the `Apply with other promotions field`. Applies to all the products in the shopping cart.
+
+As the first two promotions apply to the t-shirt and are not marked as cumulative, they compete with each other.
+
+When promotions compete, the Promotions module will choose the promotion that provides the best discount for the customer. See below for an example of competition by scenario.
+
+##### Scenario 1: Applying Promotion 1 of 10% 
+
+| Items | Promotions applied | Amounts |
+| ----------- | ----------- |  ----------- |
+| T-shirt | Promotion 1 and Promotion 3 | $8.55 |
+| Shoes | Promotion 1 and Promotion 3 | $42.75 |
+
+The t-shirt would be priced at **$8.55** with a *discount of 10% from Promotion 1* and 5% on the product price. The pair of shoes would be priced at **$42.75** with a *discount of 10% from Promotion 1* and a *discount of 5% on the product price*.
+
+The order total would be **$51.30**.
+
+##### Scenario 2: Applying Promotion 2 of 25%
+
+| Items | Promotions applied | Amounts |
+| ----------- | ----------- |  ----------- |
+| T-shirt | Promotion 2 and Promotion 3 | $7.12 |
+| Shoes | Promotion 2 and Promotion 3 | $47.50 |
+
+The t-shirt would be priced at **$7.12** with a *discount of 25% from Promotion 2 and 5% on the product price*. The pair of shoes would be priced at **$47.50**, considering only the *5% discount on the product price*, as it is not in the Promotion 2 collection.
+
+In this scenario, the order total would be **$54.62**.
+
+In short, since in scenario 1 the order total is cheaper for the customer, it fits the premise of offering the best possible discount. So VTEX chooses to apply Promotion 1 of 10% for both items. This is because promotions 1 and 2 could not be applied together since they are non-cumulative. 
+
+### Competition by item
+
+The Promotions module can also consider the highest discount for the customer on each item in the cart. To do this, the system considers the promotions that can be applied to an item and selects the best among them, rather than considering a combination of promotions at the cart level.
+
+In the competition by item, this is what would happen following the data from the previous example:
+
+| Collection | Items | Amounts |
+| ----------- | ----------- |  ----------- |
+| 1 | T-shirt | $ 10 |
+| 1 | Shoes | $ 50 |
+
+- Promotions:
+   1. **10%** off on the first collection. Configured as non-cumulative in the `Apply with other promotions field`.
+   2. **25%** off on the second collection. Configured as non-cumulative in the `Apply with other promotions field`.
+   3. **5%** off on the product price. Configured as cumulative in the `Apply with other promotions field`. Applies to all the products in the shopping cart.
+
+Applying the promotion, the amounts would be:
+
+| Items | Promotions applied | Amounts |
+| ----------- | ----------- |  ----------- |
+| T-shirt | Promotion 2| $7.50 |
+| Shoes | Promotion 1 | $45 |
+
+The t-shirt would be priced at **$7.50** with a *discount of 25% from Promotion 2*. The pair of shoes would be priced at **$45** with a *discount of 10% from Promotion 1*.
+
+In this scenario, the order total would be **$52.50**.
+
+This option would offer a smaller discount to the customer than the selection from the [competition by scenario](#competition-by-scenario). Therefore, this configuration depends on the business goals set by the store. 
+
+In case the competition by item strategy is better suited for your business needs, please [open a ticket](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) with our support team and request the change.
diff --git a/docs/tutorials/en/how-recursive-marketplace-works.md b/docs/tutorials/en/how-recursive-marketplace-works.md
index 3b9b38900..09b112d2e 100644
--- a/docs/tutorials/en/how-recursive-marketplace-works.md
+++ b/docs/tutorials/en/how-recursive-marketplace-works.md
@@ -33,7 +33,7 @@ Thus:
 
 - __When a VTEX store is intermediate in the order flow__: chain order with __Chain Workflow__:
 
-![marketplace-recursivo-chain-order-workflow](https://images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
+![marketplace-recursivo-chain-order-workflow](//images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
 
 
 ## Setup
diff --git a/docs/tutorials/en/how-shipping-calculation-works.md b/docs/tutorials/en/how-shipping-calculation-works.md
index a488201e0..9cc4ed5bf 100644
--- a/docs/tutorials/en/how-shipping-calculation-works.md
+++ b/docs/tutorials/en/how-shipping-calculation-works.md
@@ -3,8 +3,8 @@ title: 'How shipping calculation works'
 id: tutorials_116
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:59.694Z
-updatedAt: 2022-06-21T14:55:49.737Z
-publishedAt: 2022-06-21T14:55:49.737Z
+updatedAt: 2023-07-25T19:55:42.137Z
+publishedAt: 2023-07-25T19:55:42.137Z
 firstPublishedAt: 2017-04-27T23:00:43.230Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -84,7 +84,6 @@ You can configure different priorities and criteria for [logistics](https://help
 - **Shipping rates:** The shipping rate prices are configured in the [shipping rates](https://help.vtex.com/en/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM), except for the [loading dock rate](https://help.vtex.com/en/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV), which is an optional value, configured when adding a new loading dock to a warehouse.
 - **Delivery time:** The shipping time is configured in the [SLA estimate](#shipping-time-estimate).
 - **Package splitting:** The adopted criteria are configured in the Checkout module. Learn more in [package splitting](https://help.vtex.com/en/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV).
-- **Warehouse prioritization:** You can only configure a different criterion for warehouse prioritization via API, adding the `priority` property in [Create/update warehouse](https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse). 
 
 ## Shipping time estimate
 
diff --git a/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md b/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
index 5dffead41..413c745ad 100644
--- a/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
+++ b/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
@@ -3,8 +3,8 @@ title: ' How shipping works when delivery is done by the marketplace (FOB)'
 id: EY1l6tYW3IUquwwwcQqwQ
 status: PUBLISHED
 createdAt: 2017-08-28T23:17:57.225Z
-updatedAt: 2021-08-11T17:11:00.299Z
-publishedAt: 2021-08-11T17:11:00.299Z
+updatedAt: 2024-02-05T15:48:24.006Z
+publishedAt: 2024-02-05T15:48:24.006Z
 firstPublishedAt: 2017-08-29T20:09:40.790Z
 contentType: tutorial
 productTeam: Channels
@@ -23,7 +23,8 @@ This procedure avoids the order being unnecessarily validated, simplifies the in
 
 The following rules must always be applied when selecting the inventories to serve an SKU:
 
-1. Largest available SKU amount.
+1. Fewest available SKU amount.
+    > _So inventories with small item quantities are not blocked out._ 
 2. Shortest travel time between warehouse and loading dock.
 3. Lowest travel price between warehouse and loading dock.
 
@@ -35,7 +36,7 @@ If an order has several units of an SKU, one of the warehouses must have the ful
 
 Since delivery will be made by the marketplace, the OMS does not indicate delivery time or cost, since this is agreed between upon between the marketplace and the buyer of the product, at no cost to the store. The information pertaining to the deadline, found in the order, is a shipping simulation done when integrating the order, rather than what the marketplace had informed VTEX about.
 
-Instead of carrier identification and the type of delivery, `vtex:fob_1111` is shown, with `1111` being the ID of the warehouse where the SKU has been reserved.
+Instead of carrier identification and the type of delivery, `vtex:fob_1111` is shown, with `1111` being the ID of the loading dock.
 
 ## API
 
@@ -43,7 +44,7 @@ As with the OMS interface, the API shows `vtex:fob_1111` in the selectedSla, del
 
 It is important that the ERP is able to accept data in this format.
 
-![](https://images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
+![](//images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
 
 ## Label
 
@@ -51,6 +52,6 @@ The order is mailed under an agreement between Correios (national postal service
 
 The label can be accessed directly through OMS, under the order list. Just click on the link and a new window will open with the label in PDF format.
 
-![Delivery label by Correios (BR) - Marketplace](https://images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/4b1c70652ae5dc8248c829527d733c65/Screen_Shot_2020-03-25_at_11.43.43.png)
+![Delivery label by Correios (BR) - Marketplace](//images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/4b1c70652ae5dc8248c829527d733c65/Screen_Shot_2020-03-25_at_11.43.43.png)
 
-If you want to make use of the label in your ERP, it is also available in the [Orders API](https://developers.vtex.com/reference/orders#getorder), in the `trackingHints` array of the `shippingData` object.
+If you want to make use of the label in your ERP, it is also available in the [Marketplace Protocol API](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/order-integration/orders), more information in [New Order Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-collect-orders#scenario-12-order-with-tracking-hints).
diff --git a/docs/tutorials/en/how-subscriptions-work.md b/docs/tutorials/en/how-subscriptions-work.md
index b5a5f7547..dab08ea72 100644
--- a/docs/tutorials/en/how-subscriptions-work.md
+++ b/docs/tutorials/en/how-subscriptions-work.md
@@ -3,8 +3,8 @@ title: 'How subscriptions work'
 id: frequentlyAskedQuestions_4453
 status: PUBLISHED
 createdAt: 2019-01-24T20:46:00.886Z
-updatedAt: 2023-02-15T23:42:14.386Z
-publishedAt: 2023-02-15T23:42:14.386Z
+updatedAt: 2024-07-24T17:36:44.989Z
+publishedAt: 2024-07-24T17:36:44.989Z
 firstPublishedAt: 2019-01-24T22:14:56.290Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,13 +17,15 @@ subcategory: 1rA9wuuskW3PpjvMrhatAM
 
 The **Subscription System** is an app developed by VTEX to facilitate recurring sales. It works as an automatic scheduler, making a purchase at the frequency requested by the customer. 
 
-Your customers indicate how often they want to repeat the purchase of a specific SKU, and the system resubmits the order. This purchase is made automatically every scheduled period, with the same configuration as the original order.
+Your customers indicate how often they want to repeat the purchase of a specific SKU, and the system resubmits the order. This purchase is made automatically every scheduled period, with the same configuration as the original order. Subscription is a simple solution to save your customer's time and to add a scheduled sales flow to your store.
 
-For VTEX, a subscription consists of an SKU list that is linked to a specific purchase configuration. All management operations are based on the Subscription entity, which contains all the necessary information to generate a recurring order. The diagram below illustrates the subscription concept:
+For VTEX, a subscription consists of an SKU list that is linked to a specific purchase configuration. All management operations are based on the Subscription entity, which contains all the necessary information to generate a recurring order, such as:
 
-![img8 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/33a97511d0c48f954b9de33bcad8fa40/img8_subscriptions_EN.png)
-
-Subscription is a simple solution to save your customer's time and to add a scheduled sales flow to your store.
+- User profile
+- Address
+- Payment method
+- Frequency
+- Subscription order start date
 
 ## How your customer generates an order with a subscription
 
@@ -43,9 +45,13 @@ To do that, go to the **My Account** page on your store's website, access the **
 
 ## How your customers view and manage their subscriptions
 
+<div class = "alert alert-info">
+In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
+</div>
+
 A list of all the customer’s subscriptions, containing their details and statuses, will be displayed in the **Subscriptions** section, on the **My Account** page. Your customer will also receive a confirmation of the subscription and the generated order by email.  
 
-You will communicate with your customers about their subscriptions through the **Message Center** module. Please read our article about **[Transactional emails for subscription orders](https://help.vtex.com/en/tutorial/e-mails-transacionais-para-pedidos-de-assinatura--2NYHqHMRqZ43Cn6s84ZCB5). 
+You will communicate with your customers about their subscriptions through the **Message Center** module. Please read our article about [Transactional emails for subscription orders](https://help.vtex.com/en/tutorial/e-mails-transacionais-para-pedidos-de-assinatura--2NYHqHMRqZ43Cn6s84ZCB5). 
 
 ### Subscription details
 
@@ -105,3 +111,5 @@ Yes, the price charged for the subscription is based on the price configured for
 
 12. **What time are subscription orders generated?**
 Subscription orders are created between 6:00 and 7:00 am in Brazil zone (GMT-3).
+
+13. **Does the functionality Subscriptions work with Seller Portal?** No, Subscriptions does not work with [Seller Portal](https://help.vtex.com/en/tutorial/how-to-set-up-your-store-on-seller-portal).
diff --git a/docs/tutorials/en/how-the-carrefour-integration-works.md b/docs/tutorials/en/how-the-carrefour-integration-works.md
index 1c44734df..994248b86 100644
--- a/docs/tutorials/en/how-the-carrefour-integration-works.md
+++ b/docs/tutorials/en/how-the-carrefour-integration-works.md
@@ -3,8 +3,8 @@ title: 'How the integration with Carrefour works'
 id: UbtveAQnoQGKOkQIYG0uQ
 status: PUBLISHED
 createdAt: 2018-09-26T13:35:41.191Z
-updatedAt: 2021-07-09T19:05:35.482Z
-publishedAt: 2021-07-09T19:05:35.482Z
+updatedAt: 2023-09-22T20:09:43.231Z
+publishedAt: 2023-09-22T20:09:43.231Z
 firstPublishedAt: 2018-10-11T20:58:12.080Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/how-the-order-replacement-works.md b/docs/tutorials/en/how-the-order-replacement-works.md
index e8dd58e96..567ebaac1 100644
--- a/docs/tutorials/en/how-the-order-replacement-works.md
+++ b/docs/tutorials/en/how-the-order-replacement-works.md
@@ -63,7 +63,7 @@ With this feature, your store users get a redesigned My Orders page with change
 
 ![meus pedidos1 EN](//images.contentful.com/alneenqid6w5/6qCTCcaC2WSE8AgcGuI2YM/c435205525f59c10f5c04c664229044b/meus_pedidos1_EN.png)
 
-![meus pedidos3 EN](https://images.ctfassets.net/alneenqid6w5/r8wqLRzyGOEmGcMuWQYMg/3fa6aaad6bd888246457d9e96e704516/meus_pedidos3_EN.png)
+![meus pedidos3 EN](//images.ctfassets.net/alneenqid6w5/r8wqLRzyGOEmGcMuWQYMg/3fa6aaad6bd888246457d9e96e704516/meus_pedidos3_EN.png)
 
 When you select **Change order**, the customers are taken to a screen where they choose which information they would like to replace:
 
diff --git a/docs/tutorials/en/how-the-seller-portal-catalog-works.md b/docs/tutorials/en/how-the-seller-portal-catalog-works.md
index 80d0172d6..0ed56b524 100644
--- a/docs/tutorials/en/how-the-seller-portal-catalog-works.md
+++ b/docs/tutorials/en/how-the-seller-portal-catalog-works.md
@@ -21,7 +21,7 @@ The Seller Portal Catalog is the module where you configure your store's product
 
 The Seller Portal Catalogue architecture is based on fundamental concepts distributed throughout the following hierarchy:
 
-![ilustra-catalogoEN](https://images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/0b0ac21f576210cc1acc7acac5391a93/ilustra-catalogoEN.png)
+![ilustra-catalogoEN](//images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/0b0ac21f576210cc1acc7acac5391a93/ilustra-catalogoEN.png)
 
 - **Categories:** ways in which your products can be organized. You cannot add your own categories; the marketplace defines the categories that are available to classify your products under. Each product will necessarily be linked to an already existing category.  
 - **Brands:** part of the attributes that characterize your store's products, allowing your customers to also find what they are looking for in a more specific way. You cannot add your own brands, the ones shown in the *Brands* tab have already been imported from the marketplace.    
diff --git a/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md b/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md
index e0ab0bd52..669d0d2e4 100644
--- a/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md
+++ b/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 The [Shareable Cart](https://apps.vtex.com/vtex-social-selling/p) app allows sales assistants to select products for their customers and share the cart through channels such as WhatsApp, Facebook Messenger and email.
 
-![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 This article explains how to install the app and configure this functionality in your store. After completing the activation steps, your sales assistants will be able to [follow the instructions](https://help.vtex.com/en/tutorial/como-usar-o-app-carrinho-compartilhavel--3ePPpkmeZ96GXbeIoGZbTN) to start your Social Selling strategies.
 
@@ -84,7 +84,7 @@ You can change the button colors on your store's cart sharing interface through
 
 In the image below, option A shows the original colors and option B shows one possible customization.
 
-![shareable-cart-ui-customization](https://images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
+![shareable-cart-ui-customization](//images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
 
 The code below must be added at the end of the `checkout5-custom.css` or `checkout6-custom.css` file, available for customization in *Store Settings > Checkout > Code*. The file that should be edited depends on the version of the Checkout used by your store.
 
diff --git a/docs/tutorials/en/how-to-alter-a-banner.md b/docs/tutorials/en/how-to-alter-a-banner.md
index c35735d5e..683c39540 100644
--- a/docs/tutorials/en/how-to-alter-a-banner.md
+++ b/docs/tutorials/en/how-to-alter-a-banner.md
@@ -22,14 +22,14 @@ We will use a banner on the Home Page as an example, but these step-by-step inst
 3. Click the **Sites and Channels** folder.
 4. Click the **name of your store**.
 5. Click the **"/" folder**.
-![CMS instrução - EN](https://images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
+![CMS instrução - EN](//images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
 6. Click on the **Home** file.
 7. Click on the **Settings** tab.
 8. Click on the “pencil” for editing.
-![cms-home-settings EN](https://images.ctfassets.net/alneenqid6w5/1Gs6bDdZs4eqaiQmK6qScC/272aa7943884746f32c66b75bb86b58d/banner_home_settings_-_EN.png)
+![cms-home-settings EN](//images.ctfassets.net/alneenqid6w5/1Gs6bDdZs4eqaiQmK6qScC/272aa7943884746f32c66b75bb86b58d/banner_home_settings_-_EN.png)
 9. The banner window will open.
 10. Click on the pencil that appears on the screen.
-![cms_home_settings_lapis EN](https://images.ctfassets.net/alneenqid6w5/5Js48igaXuycwYaMEkSG2k/80d3bcf1f1fa41134cd65bacfd9cda6d/cms_settings_lapis_EN.png)
+![cms_home_settings_lapis EN](//images.ctfassets.net/alneenqid6w5/5Js48igaXuycwYaMEkSG2k/80d3bcf1f1fa41134cd65bacfd9cda6d/cms_settings_lapis_EN.png)
 11. This will open the banner form.
 
 **Change the content of the form:**
diff --git a/docs/tutorials/en/how-to-archive-ratestaxes.md b/docs/tutorials/en/how-to-archive-ratestaxes.md
index 023af18cf..f599f2d4a 100644
--- a/docs/tutorials/en/how-to-archive-ratestaxes.md
+++ b/docs/tutorials/en/how-to-archive-ratestaxes.md
@@ -18,7 +18,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 If you want to remove a rate created from the main list, for example, because it is not being used, you can move it to the list of archived taxes. By doing this, the status of the rate will be automatically changed to inactive. To do so, follow the steps below:
 
-![example 1](https://images.ctfassets.net/alneenqid6w5/14f4EpASB8c2m2kMEcES0c/7e83ef6235c1d6bb8071fb4a2ae0dea4/example_1.png)
+![example 1](//images.ctfassets.net/alneenqid6w5/14f4EpASB8c2m2kMEcES0c/7e83ef6235c1d6bb8071fb4a2ae0dea4/example_1.png)
 
 1. In the VTEX Admin, go to *Promotions > Taxes*, or type *Taxes* in the search bar at the top of the page.
 2. Search the rate that you intend to archive.
diff --git a/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
index 08edfdd16..3843d4751 100644
--- a/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
@@ -21,11 +21,11 @@ To retrieve the IP of a customer that placed an order at your store, you can ana
 
 When you open an order, click "See transaction details" in the payment box:
 
-![ip pedido1 EN](https://images.ctfassets.net/alneenqid6w5/23018S94Qgws4swwoUUmSW/37a40268c64fb2306cdb236f552d3e20/ip_pedido1_EN.png)
+![ip pedido1 EN](//images.ctfassets.net/alneenqid6w5/23018S94Qgws4swwoUUmSW/37a40268c64fb2306cdb236f552d3e20/ip_pedido1_EN.png)
 
 Finally, the IP is visualized on the top right corner:
 
-![ip pedido2 EN](https://images.ctfassets.net/alneenqid6w5/5TFz9FxDAQiwcuGCmcYoCu/315612e531df7562d33b80398bc80ef9/ip_pedido2_EN.png)
+![ip pedido2 EN](//images.ctfassets.net/alneenqid6w5/5TFz9FxDAQiwcuGCmcYoCu/315612e531df7562d33b80398bc80ef9/ip_pedido2_EN.png)
 
 See more details on [How to visualize the order detail](/en/tutorial/how-to-view-the-orders-details)
 
diff --git a/docs/tutorials/en/how-to-change-orders-beta.md b/docs/tutorials/en/how-to-change-orders-beta.md
new file mode 100644
index 000000000..d12c4ac50
--- /dev/null
+++ b/docs/tutorials/en/how-to-change-orders-beta.md
@@ -0,0 +1,217 @@
+---
+title: 'How to change orders (Beta)'
+id: 7btlG91rb6sHpW1dkd2kBw
+status: PUBLISHED
+createdAt: 2023-11-27T22:40:33.769Z
+updatedAt: 2024-04-09T18:03:22.045Z
+publishedAt: 2024-04-09T18:03:22.045Z
+firstPublishedAt: 2023-11-28T15:16:50.272Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: how-to-change-orders-beta
+locale: en
+legacySlug: how-to-change-orders-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+<div class="alert alert-info">
+This feature is in beta, which means that we are working to improve it. If you wish to use <b>Change order (Beta)</b>, please contact <a href="https://help.vtex.com/en/support">our Support</a> and provide the <a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> in which to activate it.
+</div>
+
+The [Change order (beta)](https://help.vtex.com/en/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ) feature allows you to edit an order in different ways, either due to customer requests, product unavailability, or other reasons.
+
+This article explains how an order can be changed and how to do so. It comprises the following sections:
+
+- [Conditions](#conditions)
+- [Types of order changes](#types-of-order-changes)
+- [Common aspects](#common-aspects)
+- [Processing errors](#processing-errors)
+
+<div class="alert alert-warning">
+To learn about the <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#general-characteristics">general characteristics</a> of order change scenarios, including aspects like reservation, inventory update, and franchise accounts, or to understand details related to <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#price-changes">pricing, payment, and invoicing</a>, read the <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ">How Change order works (Beta)</a> article.
+</div>
+
+## Conditions
+
+There are some conditions for changing orders related to the order status. See the details below.
+
+### Status of the order to be changed
+
+In the [order flow](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196), `Handling shipping` is the only status valid for **Change order (beta)** in the VTEX Admin. Read the [How Change order works (Beta)](https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ) article to learn more about API changes.
+
+### License Manager permission
+
+For a user to be able to change orders, their [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) must be associated with at least one of the following [Licence Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3):
+
+- `Orders Full Access`
+- `Change order`
+
+## Types of order changes
+
+These are the main order changes that can be made through the VTEX Admin:
+
+- **Add:** Increase the number of items or add new products.
+- **Remove:** Remove the partial or total number of items.
+- **Weight change:** Adjust the weight assigned to items.
+- **Replace items:** Replace items, including those priced by weight.
+- **Price change:** [Change the order total amount](https://help.vtex.com/en/tutorial/alterar-valor-total-do-pedido--2asq4BmxvSD8Tw9xpfZuMo).
+
+All these actions are done on the [order details](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) page, which you can access in two ways, as described below.
+
+### Viewing orders on the All orders page
+
+In the VTEX Admin, go to **Orders >** [All Orders](https://help.vtex.com/en/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi) and click the desired order, or type **All Orders** in the search bar at the top of the page. Then click the order you want to view. If necessary, you can use [filters](https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192) to narrow your search.
+
+### Viewing orders using the global search bar
+
+From any VTEX Admin page, search for the order using the search bar at the top of the page. Select the `Orders` option in the right corner of the bar and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
+
+On the order details page, you can do the following:
+
+- [Add items](#adding-items)
+- [Add a new product](#adding-a-new-product)
+- [Remove items](#removing-items)
+- [Remove a product](#removing-a-product)
+- [Replace items](#replacing-items)
+- [Change weight](#changing-weight)
+
+<div class = "alert alert-info">
+You can make a single change to the order or combine several at once. There is no limit to how many times an order can be changed. Read the <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ">How Change order works (Beta)</a> article to learn more.
+</div>
+
+### Adding items
+
+To add one or more items to the order, follow these steps:
+
+1. In the VTEX Admin, go to the order details page through **Orders >** [All Orders](#viewing-orders-on-the-all-orders-page) or by using the [global search bar](#viewing-orders-using-the-global-search-bar).
+2. In the **Pending invoicing** section, click `Change Items`.
+3. On the **Manage order items** page, click the up arrow <i class="fas fa-angle-up"></i> to the number you want, or enter the number in the field. Then, the page will display the price and the previous number with a strikethrough, followed by the message: _"Item edited"_.
+
+    ![change_order_adding_items_EN](//images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/d1f2ff7078f9a72db8ab25b8dda60e7c/change_order_adding_items_EN.png)
+
+4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
+5. Click `Review and Apply`.
+6. In the **Reason for Changes** field, briefly explain why the order is being changed. If you wish, review the changes again.
+7. Click `Apply`. The following confirmation message will be displayed: _"Change request completed"._
+
+After doing so, you will be redirected back to the order details page. In the **Pending invoicing** section, you will see the updated number of items.
+
+### Adding a new product
+
+To add one or more products to an order, follow these steps:
+
+1. In the VTEX Admin, go to the order details page through **Orders >** [All Orders](#viewing-orders-on-the-all-orders-page) or by using the [global search bar](#viewing-orders-using-the-global-search-bar).
+2. In the **Pending invoicing** section, click `Change Items`.
+3. On the **Manage order items** page, click `+ Add Item`.
+4. On the **Add items** page, use the <i class="fas fa-search"></i> search bar to enter the name of the desired product.
+5. Click <i class="fas fa-plus"></i> `Select`. You can add as many products as you like by repeating the procedure. For each new addition, the following message will be displayed: _"Item selected"_.
+  > If you click the product name, you will be redirected to the product page on the store's website.
+6. Then click `Add Selected Items`, and the following message will be displayed: _"Items added"_.
+
+    ![change_order_adding_product_EN](//images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/30f4bc58081e982190d44bb730a9ca25/change_order_adding_product_EN.png)
+
+4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
+5. Click `Review and Apply`.
+6. In the **Reason for Changes** field, briefly explain why the order is being changed. If you wish, review the changes again.
+7. Click `Apply`. The following confirmation message will be displayed: _"Change request completed"_.
+
+After doing so, you will be redirected back to the order details page. In the **Pending invoicing** section, you will see the recently added products.
+
+### Removing items
+
+To remove one or more items from an order, follow these steps:
+
+1. In the VTEX Admin, go to the order details page through **Orders >** [All Orders](#viewing-orders-on-the-all-orders-page) or by using the [global search bar](#viewing-orders-using-the-global-search-bar).
+2. In the **Pending invoicing** section, click `Change Items`.
+3. On the **Manage order items** page, click the down arrow <i class="fas fa-angle-down"></i> to the number you want, or enter the number in the field. Then, the page will display the price and the previous number with a strikethrough, followed by the message: _"Item edited"_.
+
+    ![change_order_removing_items_EN](//images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/d2ebd588be0ed9b83aec51767bd263e3/change_order_removing_items_EN.png)
+
+4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
+5. Then click `Review and Apply`.
+6. In the **Reason for Changes** field, briefly explain why the order is being changed. If you wish, review the changes again.
+7. Click `Apply`. The following confirmation message will be displayed: _"Change request completed"._
+
+After doing so, you will be redirected back to the order details page. In the **Pending invoicing** section, the number of items will reflect the recent removal.
+
+### Removing a product
+
+To remove a product from an order, follow these steps:
+
+1. In the VTEX Admin, go to the order details page through **Orders >** [All Orders](#viewing-orders-on-the-all-orders-page) or by using the [global search bar](#viewing-orders-using-the-global-search-bar).
+2. In the **Pending invoicing** section, click `Change Items`.
+3. On the **Manage order items** page, click the trash can icon <i class="far fa-trash-alt"></i> and `Remove Item`. The following confirmation message will appear: _"Item removed"_.
+
+    ![change_order_removing_product_EN](//images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/7d5515c38ca48467dbaabe0123d8b14d/change_order_removing_product_EN.png)
+
+4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
+5. Then click `Review and Apply`.
+6. In the **Reason for Changes** field, briefly explain why the order is being changed. If you wish, review the changes again.
+7. Click `Apply`. The following confirmation message will be displayed: _"Change request completed"_.
+
+After doing so, you will be redirected back to the order details page. In the **Pending invoicing** section, you will see the order without the recently removed product.
+
+### Replacing items
+
+To replace items in the order, follow these steps:
+
+1. In the VTEX Admin, go to the order details page through **Orders >** [All Orders](#viewing-orders-on-the-all-orders-page) or by using the [global search bar](#viewing-orders-using-the-global-search-bar).
+2. In the **Pending invoicing** section, click `Change Items`.
+3. On the **Manage order items** page, in the row of the product you want to replace, click the menu <i class="fas fa-ellipsis-v"></i> and select <i class="fas fa-pencil-alt"></i> `Replace Item`.
+4. On the **Order replacement** page, use the &lt;i class="fas fa-search">&lt;/i> search bar to enter the name of the product you want to replace it with.
+5. Click `+ Select`. The following message will be displayed: _"Item selected"_. If you click the product name, you will be redirected to the product page on the store's website.
+6. Then click `Apply`. The following message will appear: _"Changes applied"_.
+7. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
+8. Click `Review and Apply`.
+9. In the **Reason for Changes** field, briefly explain why the order is being changed. If you wish, review the changes again.
+10. Click `Apply`. The following confirmation message will be displayed: _"Change request completed"_.
+
+After doing so, you will be redirected back to the order details page. In the **Pending invoicing** section, you will see the item that replaced the previous product.
+
+### Changing weight
+
+To change the weight of an item, follow these steps:
+
+1. In the VTEX Admin, go to the order details page through **Orders >** [All Orders](#viewing-orders-on-the-all-orders-page) or by using the [global search bar](#viewing-orders-using-the-global-search-bar).
+2. In the **Pending invoicing** section, click `Change Items`.
+3. On the **Manage order items** page, enter the new weight in the row of the desired product. The unit of measure will be specified based on the Catalog settings.
+4. Then, the page will display the previous price and weight number with a strikethrough, followed by the message _"Item edited"_.
+
+    ![change_order_changing_weight_EN](//images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/c57d6801d560764df71a72e0593358f9/change_order_changing_weight_EN.png)
+
+5. Review the [details of the amount change](##viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
+6. Click `Review and Apply`.
+7. In the **Reason for Changes** field, briefly explain why the order is being changed. If you wish, review the changes again.
+8. Click `Apply`. The following confirmation message will be displayed: _"Change request completed"._
+
+After doing so, you will be redirected back to the order details page. In the **Pending invoicing** section, you will see the updated item weight.
+
+## Common aspects
+
+When making any [type of change](#types-of-order-changes) to an order, some steps are the same, and you can check them in this section.
+
+### Viewing details of the amount change
+
+On the **Manage order items** page, as you change the order, the **Total amount** is automatically updated at the bottom of the page. In addition, you can view the price variation resulting from each operation. To view price details, click the arrow icon <i class="fas fa-angle-up"></i> next to the total amount.
+
+### Undoing actions
+
+On the **Manage order items** page, you can undo a change if you want. To do this, click the curved arrow icon `Undo Action`. After this, a confirmation message will be displayed: _"Change undone"_, indicating that the action has been successfully reversed.
+
+![change_order_undoing_actions_EN](//images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/ceee7cdae26eddb1da3588d1e5af4d0e/change_order_undoing_actions_EN.png)
+
+## Processing errors
+
+In any [type of order change](#types-of-order-changes) on the **Manage order items** page, when you click `Review and Apply,` the change may not be approved, which redirects you back to the order details page. Some of the reasons for changes being rejected are:
+
+- **Unavailable item:** The SKU may [not be displayed on the store's website](https://help.vtex.com/en/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382) or may be unavailable due to an error or missing catalog, price, or logistics settings.
+- **Insufficient inventory:** The number of items added or replaced in the change may be greater than the number of items available for sale in your [inventory](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+
+If the Catalog and inventory settings are correct and changes to orders return errors, this might indicate a problem with the platform's processing. In this case, we recommend contacting our [support team](https://help.vtex.com/en/support).
+
diff --git a/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md b/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md
index 7aa823e16..47fe89bc1 100644
--- a/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md
+++ b/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md
@@ -3,8 +3,8 @@ title: 'Changing the order of payment methods at checkout'
 id: frequentlyAskedQuestions_490
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:54.205Z
-updatedAt: 2022-04-25T15:09:37.985Z
-publishedAt: 2022-04-25T15:09:37.985Z
+updatedAt: 2023-10-31T17:27:08.660Z
+publishedAt: 2023-10-31T17:27:08.660Z
 firstPublishedAt: 2019-01-24T22:12:00.925Z
 contentType: tutorial
 productTeam: Shopping
diff --git a/docs/tutorials/en/how-to-check-your-balance.md b/docs/tutorials/en/how-to-check-your-balance.md
index 7740b6e1e..b959831d7 100644
--- a/docs/tutorials/en/how-to-check-your-balance.md
+++ b/docs/tutorials/en/how-to-check-your-balance.md
@@ -28,7 +28,7 @@ To check your account balance, follow the step by step:
 - Click on __Account Overview__;
 - On the left side of the screen, find the __Balance__ box.
 
-![saldodisponivelEN](https://images.ctfassets.net/alneenqid6w5/1nnABtiycAQhExwdQcbbHD/fe145d3e68fcab0ab97b53713244df1c/image.png_h_250)
+![saldodisponivelEN](//images.ctfassets.net/alneenqid6w5/1nnABtiycAQhExwdQcbbHD/fe145d3e68fcab0ab97b53713244df1c/image.png_h_250)
 
 Two different values are shown in the box. The first, __Available__, shows the account balance that is available for transactions. The second, __Balance due__, refers to future payments that will be deposited into your corporate digital account.
 
diff --git a/docs/tutorials/en/how-to-configure-a-bank-slip.md b/docs/tutorials/en/how-to-configure-a-bank-slip.md
index 705c500aa..668538e66 100644
--- a/docs/tutorials/en/how-to-configure-a-bank-slip.md
+++ b/docs/tutorials/en/how-to-configure-a-bank-slip.md
@@ -3,8 +3,8 @@ title: 'Configuring bank slips'
 id: tutorials_447
 status: PUBLISHED
 createdAt: 2017-04-27T22:04:55.249Z
-updatedAt: 2023-03-21T20:14:57.262Z
-publishedAt: 2023-03-21T20:14:57.262Z
+updatedAt: 2024-04-16T14:44:36.023Z
+publishedAt: 2024-04-16T14:44:36.023Z
 firstPublishedAt: 2017-04-27T23:03:25.766Z
 contentType: tutorial
 productTeam: Financial
@@ -15,41 +15,22 @@ legacySlug: how-to-configure-a-bank-slip
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-The bank slip is a payment instrument where, for the recovery, you just need to have a bank account, and to contract a collection portfolio with the bank. After that, it is possible to send and receive slips directly through your bank account.
+At VTEX, your store can sell via [bank slips](https://help.vtex.com/en/tutorial/registered-ticket-flow--1WlPkeueWQiykUwW8mcM4S). To configure the bank slip, follow the steps below:
 
-There are two ways of configuration:
-- Straight through VTEX, without an external payment gateway.
-- Through a payment gateway, such as PagSeguro.
+1. In the VTEX Admin, access __Store Settings > Payments > Providers__, or type __Provedores__ in the search bar at the top of the page.
+2. On the providers screen, click the `New provider` button.
+3. Type in the search bar the name of the provider that will process the bank slip.
+4. Fill in the form fields according to the data provided by the provider/bank.
+5. Click `Save`.
 
-The two ways of configuration are described below.
+## Setting up the payment condition
 
-## Setting it up without an external payment gateway
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. In __Boleto__, select the option __Boleto Bancário__.
+4. Activate the condition in the __Status__ field.
+5. Under __Process with provider__, select the previously configured provider.
+6. If you want, you can also [Set up special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+7. Click `Save`.
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Access the **Gateway Affiliations** tab.
-3. Click on **+**.
-4. Select one of the **Bank Slip** options.
-5. Fill out the form fields according to the data provided by your bank - each bank requires different information. So, always check with the bank which are the mandatory information.
-6. Click on **Save**.
-
-## Setting it up with an external payment gateway
-
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Access the **Gateway Affiliations** tab.
-3. Click on **+**.
-4. Select one of the options in **Other** (to configure payment through PagSeguro, select the "PagSeguro without redirect" option).
-5. Fill out the form fields according to the data provided by your payment gateway - each gateway requires different information. So, always check with the payment gateway which are the mandatory information.
-6. Click on **Save**.
-
-After the configuration at Gateway Affiliations, both for external gateway or direct configuration options, you need to configure the payment condition.
-
-## How to set up the payment condition
-
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Access the **Payment Conditions** tab.
-3. Click on **+**.
-4. In **Slip**, select the **Bank Slip** option.
-5. Fill out the name, select the gateway affiliation configured above, and decide wheter you would like to use the [special condition](/en/tutorial/special-conditions) configuration.
-6. Click on **Save**.
-
-After this last configuration, this form of payment will be available at the checkout of the store.
+After following the steps indicated, Boleto Bancário may take up to 10 minutes to appear at your store checkout as a payment option.
diff --git a/docs/tutorials/en/how-to-configure-a-custom-payment.md b/docs/tutorials/en/how-to-configure-a-custom-payment.md
index b158d7473..c38c4563d 100644
--- a/docs/tutorials/en/how-to-configure-a-custom-payment.md
+++ b/docs/tutorials/en/how-to-configure-a-custom-payment.md
@@ -3,8 +3,8 @@ title: 'How to configure a custom payment'
 id: tutorials_451
 status: PUBLISHED
 createdAt: 2017-04-27T22:04:32.144Z
-updatedAt: 2021-07-08T19:02:18.536Z
-publishedAt: 2021-07-08T19:02:18.536Z
+updatedAt: 2023-10-18T14:42:25.244Z
+publishedAt: 2023-10-18T14:42:25.244Z
 firstPublishedAt: 2017-04-27T23:03:25.828Z
 contentType: tutorial
 productTeam: Financial
@@ -19,19 +19,19 @@ The custom payment is an alternative to the standard options offered by Payments
 
 These payment methods are separated into three categories, and each category allows five configurations.
 
-## Promissory notes
+## Notes Payable
 
-A promissory note is a promise of payment that needs manual approval of the seller to perform the transaction. It is often used to provide payment through money. To configure Promissory notes, access the documentation [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ?&utm_source=autocomplete).
+A Note Payable is a promise of payment that needs manual approval of the seller to perform the transaction. It is often used to provide payment through money. To configure Notes Payable, access the documentation [Setting up payments with Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable).
 
 ## Store Cards (Own Brand)
 
-It allows the use of a store's credit card with its own brand. To configure this payment method, access the documentation [Setting up Private Label payments](https://help.vtex.com/en/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4?&utm_source=autocomplete).
+It allows the use of a store's credit card with its own brand. To configure this payment method, access the documentation [Setting up Private Label payments](https://help.vtex.com/en/tutorial/setting-up-private-label-payments).
 
 ## Store Cards (Co-Branded)
 
-It allows the use of a store's credit card in partnership with one of the following networks: MasterCard, Visa, Amex and Diners. To configure this payment method, access the documentation [Setting up payments with Store Card (cobranded)](https://help.vtex.com/en/tutorial/configurar-pagamentos-com-cartoes-de-loja-cobranded--jrkLK41IjuquUmyKUi86Q?&utm_source=autocomplete).
+It allows the use of a store's credit card in partnership with one of the following networks: MasterCard, Visa, Amex and Diners. To configure this payment method, access the documentation [Setting up payments with Store Card (cobranded)](https://help.vtex.com/en/tutorial/setting-up-payments-with-store-card-cobranded).
 
-After this configuration, the creation of a [Payment Condition](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455) is required.
+After this configuration, the creation of a [Payment Condition](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions) is required.
 
 <div class="alert alert-warning">
 We recommend using the automatic approval only in cases where the payment will be made upon delivery or pickup at the store. This option releases the payment of the order, meaning that the order automatically switches to the Preparing Delivery status, without payment verification.
diff --git a/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index c82847ed5..4cdcd958b 100644
--- a/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -30,7 +30,7 @@ In B2B operations, there is a need to maintain relationships with buyers who req
 2. On the tab __General__, fill in the desired value in the field __Minimum total amount in cart__.
 3. Click `Save`.
 
-![Minimum Order Value - EN](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/871fa991d270c1e64c12f0cdf3c5a4ab/Minimum_Order_Value_-_EN.png)
+![Minimum Order Value - EN](//images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/871fa991d270c1e64c12f0cdf3c5a4ab/Minimum_Order_Value_-_EN.png)
 
 <div class="alert alert-warning">
 The customer is allowed to assemble a cart with a value less than that specified in the "Minimum total amount in cart" rule. However, at the time of closing the purchase, only orders that are equal to or greater than the specified amount will be completed.
@@ -42,7 +42,7 @@ The customer is allowed to assemble a cart with a value less than that specified
 2. On the tab __General__, fill in the desired value in the field __Max quantity of the same SKU in cart__.
 3. Click `Save`.
 
-![Max quantity of the same SKU in cart](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/0a8cf8d7955ae90cea6332cafb6990ed/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_EN.png)
+![Max quantity of the same SKU in cart](//images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/0a8cf8d7955ae90cea6332cafb6990ed/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_EN.png)
 
 <div class="alert alert-warning">
 There are no limits on the maximum number of <b>same SKU</b> items per cart. The only restriction refers to the maximum number of items from <b>different SKUs</b>, which must be a maximum of 300 items per cart.
diff --git a/docs/tutorials/en/how-to-configure-payment-conditions.md b/docs/tutorials/en/how-to-configure-payment-conditions.md
index 9653b8fe8..fe683f862 100644
--- a/docs/tutorials/en/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/en/how-to-configure-payment-conditions.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configuring payment conditions'
 id: tutorials_455
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-04-27T22:04:07.105Z
-updatedAt: 2023-03-21T21:01:23.792Z
-publishedAt: 2023-03-21T21:01:12.557Z
+updatedAt: 2023-10-18T17:17:55.702Z
+publishedAt: 2023-10-18T17:17:55.702Z
 firstPublishedAt: 2017-04-27T23:03:26.687Z
 contentType: tutorial
 productTeam: Financial
@@ -49,7 +49,7 @@ In the steps below, we will use the credit card as an example of a payment condi
 9. Click on __Save__.
 
 <div class="alert alert-info">
-In Step 5. you can choose other payment methods such as debit cards, cobranded, private, promissories, bank invoices, PIX, among others.
+In Step 5. you can choose other payment methods such as debit cards, cobranded, private, notes payable, bank invoices, PIX, among others.
 </div>
 
 ### Installments without interest
@@ -85,7 +85,7 @@ In Step 5. you can choose other payment methods such as debit cards, cobranded,
 14. To choose between compound interest and simple interest, select __Compound Interest applied. Change__. A selection box will appear allowing you to choose between the two options. 
 15. Click on __Save*__.
 
-![Juros - en](https://images.ctfassets.net/alneenqid6w5/7IPLydgcKCsQUItYhn4LgD/efa95228eb34354425a0064491122b46/Juros_-_en.png)
+![Juros - en](//images.ctfassets.net/alneenqid6w5/7IPLydgcKCsQUItYhn4LgD/efa95228eb34354425a0064491122b46/Juros_-_en.png)
 
 #### External Interest
 
@@ -101,4 +101,4 @@ In some countries, interest on installment purchases is charged directly by the
 2. In the __Payment Conditions__ tab, click on the payment term you wish to remove.
 3. Click on the trash can icon.
 
-![Remove payment condition](https://images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/8fc094a085a51f3b24d705956c14e052/remove_payment_condition.png)
+![Remove payment condition](//images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/8fc094a085a51f3b24d705956c14e052/remove_payment_condition.png)
diff --git a/docs/tutorials/en/how-to-configure-rating-and-review-controls.md b/docs/tutorials/en/how-to-configure-rating-and-review-controls.md
index 4422dad2a..4bcc50553 100644
--- a/docs/tutorials/en/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/en/how-to-configure-rating-and-review-controls.md
@@ -41,10 +41,10 @@ These controls, unlike the others, will only work if specifically configured, as
 
 In registering the Category, there is the option to configure the Rating feature, and this is normally done in the root category:
 
-![avaliação-categoria EN](https://images.ctfassets.net/alneenqid6w5/QRc6IqC0gMkGMGyuces2S/91d41a3275a79250d08d375ba86add28/avalia____o_en.png)
+![avaliação-categoria EN](//images.ctfassets.net/alneenqid6w5/QRc6IqC0gMkGMGyuces2S/91d41a3275a79250d08d375ba86add28/avalia____o_en.png)
 
 Click on **new rating** and fill in the Name and Text fields, then save.
 
-![new-rating-categorias EN](https://images.ctfassets.net/alneenqid6w5/k7zFwGh3bM8C6io8yicYU/7568bf49b49455acbf564e33146b2396/new_rating.png)
+![new-rating-categorias EN](//images.ctfassets.net/alneenqid6w5/k7zFwGh3bM8C6io8yicYU/7568bf49b49455acbf564e33146b2396/new_rating.png)
 
 Now your Review and Rating controls are ready to be used.
diff --git a/docs/tutorials/en/how-to-configure-subscriptions.md b/docs/tutorials/en/how-to-configure-subscriptions.md
index 75b482133..5810b056a 100644
--- a/docs/tutorials/en/how-to-configure-subscriptions.md
+++ b/docs/tutorials/en/how-to-configure-subscriptions.md
@@ -3,8 +3,8 @@ title: 'How to configure Subscriptions in your store'
 id: 1FA9dfE7vJqxBna9Nft5Sj
 status: PUBLISHED
 createdAt: 2019-01-31T16:00:03.228Z
-updatedAt: 2023-04-11T00:33:27.310Z
-publishedAt: 2023-04-11T00:33:27.310Z
+updatedAt: 2024-07-09T14:27:30.778Z
+publishedAt: 2024-07-09T14:27:30.778Z
 firstPublishedAt: 2019-01-31T16:01:57.927Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -67,7 +67,7 @@ Currently, the following payment methods are enabled for subscription orders:
   <p>To make the <strong>Credit card</strong> payment option available, contact your store's acquirer and make sure they accept recurring purchase transactions coming from tokenized cards (no CVV). The <strong>Subscriptions</strong> system will use the same card data from the first purchase to place subsequent subscription orders, ensuring the security of the entire process.</p>
 </div>
 
-To enable this type of transaction in the connector, the store manager must ask the acquirer for permission to process recurring payments. Check out our article on [how to set up a payment gateway in your store](https://help.vtex.com/en/tutorial/pci-gateway-visao-geral/).
+To enable this type of transaction in the connector, the store manager must ask the acquirer for permission to process recurring payments. Check out our article [Registering gateway affiliations](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
 
 ## 3. Create a subscription plan
 
@@ -94,12 +94,12 @@ See the table below for features related to the Subscriptions module.
 
 To configure Subscription roles, please follow the instructions below.
 
-1. Under **Account settings**, click on **Account management** and then on **Roles**.
-2. Click on the `New role` button. 
+1. Under **Account Settings**, click **User Roles**.
+2. Click `New Role`.
 3. Fill in the **Role name**.
-4. Under **Products and resources** select **OMS**.
-5. Check the **Subscription resources** you would like to add.
-6. Click on `Save`.
+4. Under **Products and Resources** select `Subscriptions`.
+5. Check the resources you would like to add.
+6. Click `Save`.
 
 Once Subscriptions are configured in your store, please read our article on how to [manage subscriptions](https://help.vtex.com/en/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x).
 
diff --git a/docs/tutorials/en/how-to-configure-the-anti-fraud.md b/docs/tutorials/en/how-to-configure-the-anti-fraud.md
index 86bfef6b0..4fca69bc6 100644
--- a/docs/tutorials/en/how-to-configure-the-anti-fraud.md
+++ b/docs/tutorials/en/how-to-configure-the-anti-fraud.md
@@ -3,8 +3,8 @@ title: 'Configuring the anti-fraud'
 id: tutorials_446
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:02.912Z
-updatedAt: 2023-03-29T00:57:28.767Z
-publishedAt: 2023-03-29T00:57:28.767Z
+updatedAt: 2024-03-13T12:04:32.047Z
+publishedAt: 2024-03-13T12:04:32.047Z
 firstPublishedAt: 2017-04-27T23:03:25.730Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,23 @@ legacySlug: how-to-configure-the-anti-fraud
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-The anti-fraud is an external system that identifies frauds, increasing the security of all purchases. On VTEX, you can choose between some anti-fraud options. And setting them up is very simple.
+Anti-fraud is an external system that identifies fraud and allows you to increase security in payment transactions carried out during online purchases. At VTEX, you can choose some anti-fraud provider options to use in your store.
 
-## How to configure
+To configure an anti-fraud provider, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Access the **Gateway Affiliations** tab.
-3. Click on **+**.
-4. Click on the anti-fraud you want to configure.
-5. Fill out the form fields with the data provided by the anti-fraud (EntityCode).
-6. Click on **Save**.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the desired anti-fraud provider in the search bar and click on its name.
+4. Fill in the form fields with the data indicated by the anti-fraud provider.
+5. Click `Save`.
 
-After the configuration at Gateway Affiliations, you need to access the Payment Conditions, and associate the anti-fraud to each one of them.
+After enabling the anti-fraud provider, you need to associate it with one or more payment methods. To perform this operation, follow the steps below:
 
-1. Access the **Payment Conditions** tab.
-2. Click on the desired condition or [create the payment condition](/en/tutorial/how-to-configure-payment-conditions).
-3. Select the **Use anti-fraud** option.
-4. Select which anti-fraud you want to use.
-7. Click on **Save**.
+1. In the VTEX Admin, access __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click the `+` button.
+3. Click on the desired payment method.
+4. Fill in the __Condition name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. In __Process with provider__ select the desired payment provider.
+7. In __Use anti-fraud solution__, select the previously enabled anti-fraud provider, if available for use with this payment method.
+8. Click `Save`.
diff --git a/docs/tutorials/en/how-to-configure-the-pagseguro-without-redirect-option-transparent.md b/docs/tutorials/en/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
index f438e6836..aa9bceea9 100644
--- a/docs/tutorials/en/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
+++ b/docs/tutorials/en/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
@@ -1,10 +1,10 @@
 ---
 title: 'How to configure the PagSeguro without redirect option (transparent)'
 id: tutorials_449
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T22:04:37.656Z
-updatedAt: 2023-03-29T01:24:00.848Z
-publishedAt: 2023-03-29T01:24:00.848Z
+updatedAt: 2024-07-24T12:05:55.438Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:25.912Z
 contentType: tutorial
 productTeam: Financial
@@ -19,24 +19,19 @@ _The settings documented in this article are performed in a non-VTEX environment
 
 If you have a PagSeguro account and already use the redirect option in your store, you can enable the "without redirect" option in Payments. This means that at checkout, the customer will no longer leave your site to make the payment, even when transacting through PagSeguro. This occurs in a transparent way.
 
-This option is available as a new connector in the **Gateway Affiliations** option.
-
 Notice: If the retailer has chargeback insurance, PagSeguro's antifraud needs to be configured. This process warrants a configuration in Google Tag Manager. For more details on how to this, be sure to check out this [article on PagSeguro's page](https://dev.pagseguro.uol.com.br/v2/docs/configurando-device-fingerprint) (only available in Portuguese).
 
-To enable the affiliation without redirect, follow the steps below:
-1. 
-2. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-3. Click on __Gateway Affiliations__ and thereafter on __"+"__.
-4. Select the __PagSeguroV2__ affiliation.
-5. Save the __affiliation__.
-6. Go back to the affiliations __panel__.
-7. Select the recently created __PagSeguroV2__ affiliation.
-8. Click on __authorize__.
-9. Select and send the __desired rule__.
-10. Click on __login with email and password__.
-11. Login to your __account__ using your PagSeguro associated email and password.
-12. Authorize the __app_.
-13. Click on __save__.
+To enable it, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagSeguroV2__ in the search bar and click on the name of the provider.
+4. Click on __Authorize via OAuth__.
+5. Select and send the __desired rule__.
+6. Click on __login with email and password__.
+7. Login to your __account__ using your PagSeguro associated email and password.
+8. Authorize the __app_.
+9. Click `Save`.
 
 ## Set Payment Condition
 
diff --git a/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md b/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md
index ecc29a212..b384584ef 100644
--- a/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md
+++ b/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md
@@ -38,7 +38,7 @@ To develop a mobile version for a new website, you must proceed as follows:
 
 Storefront > Layout > CMS folder > Sites and Channels > New Website
 
-![cms-new-website](https://images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
+![cms-new-website](//images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
 
 3. Create a folder structure for the Mobile website: at this stage, you will have to create the default system folders to be used in the mobile version (search, department, category, brand, product etc.)
 
diff --git a/docs/tutorials/en/how-to-create-a-financial-access-profile.md b/docs/tutorials/en/how-to-create-a-financial-access-profile.md
index c114e3e59..65584dd68 100644
--- a/docs/tutorials/en/how-to-create-a-financial-access-profile.md
+++ b/docs/tutorials/en/how-to-create-a-financial-access-profile.md
@@ -31,7 +31,7 @@ To create a financial role, follow the walkthrough below:
 6. (Optional) Before saving, you can **add users to this role**.
 7. Click on **Save**.
 
-![gif perfildeacessoEN](https://images.ctfassets.net/alneenqid6w5/6s1lN2aC88o56Ps2OSD9jy/1c0fbd165d803a9a6c0fddac7ce8d477/gif_perfildeacessoEN.gif)
+![gif perfildeacessoEN](//images.ctfassets.net/alneenqid6w5/6s1lN2aC88o56Ps2OSD9jy/1c0fbd165d803a9a6c0fddac7ce8d477/gif_perfildeacessoEN.gif)
 
 After you’ve created the financial role, you can associate it with your existing users.
 
@@ -44,10 +44,10 @@ To associate a user with the Finance role you’ve created, follow the steps bel
 3. Click on the **Users** tab.
 4. Select the user you want to associate with the role.
 5. Choose the **Financial role**.
-6. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> button, next to the role, to add it.
+6. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> button, next to the role, to add it.
 7. Click on **Save**.
 
-![gif usuárioEN](https://images.ctfassets.net/alneenqid6w5/4UkPeH2Sfsp2KiSvozclnk/ef5a0fe13d88461cc9057e75cce09151/gif_usu__rioEN.gif)
+![gif usuárioEN](//images.ctfassets.net/alneenqid6w5/4UkPeH2Sfsp2KiSvozclnk/ef5a0fe13d88461cc9057e75cce09151/gif_usu__rioEN.gif)
 
 The selected user is now associated with the Financial role and will be able to access invoices, contract information, charges and other financial information.
 
diff --git a/docs/tutorials/en/how-to-create-a-page-template.md b/docs/tutorials/en/how-to-create-a-page-template.md
index 905dd8d13..7f1cadbc9 100644
--- a/docs/tutorials/en/how-to-create-a-page-template.md
+++ b/docs/tutorials/en/how-to-create-a-page-template.md
@@ -3,8 +3,8 @@ title: 'Creating and editing a page template'
 id: frequentlyAskedQuestions_1850
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:59.664Z
-updatedAt: 2023-03-27T14:56:34.174Z
-publishedAt: 2023-03-27T14:56:34.174Z
+updatedAt: 2023-11-01T20:27:09.646Z
+publishedAt: 2023-11-01T20:27:09.646Z
 firstPublishedAt: 2019-01-24T22:03:09.865Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Tutorial valid only for CMS Portal Legado stores.
+Tutorial valid only for Legacy CMS Portal stores.
 </div>
 
 The page template is a model designed to define an HTML structure for displaying page content.
@@ -47,7 +47,7 @@ Check out the walk-through:
 </ul></p>
 </div>
 6. Then fill in the __Template XHTML__ box with your template code. 
-![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. Click on the __Save Template__ button.
 
 To edit an existing template, the process is almost identical.
diff --git a/docs/tutorials/en/how-to-create-a-product.md b/docs/tutorials/en/how-to-create-a-product.md
index b5fa301a1..513370858 100644
--- a/docs/tutorials/en/how-to-create-a-product.md
+++ b/docs/tutorials/en/how-to-create-a-product.md
@@ -167,7 +167,7 @@ The specifications you’ve created and their respective options will be listed
 
 By combining these different options, the system automatically generates a list of SKUs and displays it in the **[Variations](#variations)** section.
 
-![variations EN](https://images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/c37697e3259b102f8292be8378cf6e2b/variations_EN.png)
+![variations EN](//images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/c37697e3259b102f8292be8378cf6e2b/variations_EN.png)
 
 ## Specifications
 
@@ -222,7 +222,7 @@ To edit a large number of variations at once, you can use the Bulk edit feature
 
 1. Click on the `Bulk editing` button to open the variation editing spreadsheet.
 2. To edit information, double-click on the field you want to change.
-![edicao-massa-SKU-EN](https://images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/279480fdf223ea60584f27ba4b8c2e05/image.png)
+![edicao-massa-SKU-EN](//images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/279480fdf223ea60584f27ba4b8c2e05/image.png)
 
 You can edit the following information:
 - **Active:** whether the variation is active or not.
@@ -238,7 +238,7 @@ You can edit the following information:
 To filter the columns displayed in the spreadsheet, click on `Filter columns` and select the columns you want to hide.
 
 You can replicate information from one cell to other rows and columns. To do this, click on the blue square in the lower right corner of the cell and drag to the cells where you want to automatically replicate the value, as shown in the image below.
-![Formatacao-celula-EN](https://images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/b0171c41044f0a8653d13a696a33534f/Formatacao-celula-EN.gif)
+![Formatacao-celula-EN](//images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/b0171c41044f0a8653d13a696a33534f/Formatacao-celula-EN.gif)
 3.  After editing, click on `Apply` to save the changes.
 
 ## SEO
diff --git a/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
index 5462dd46d..523162475 100644
--- a/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
@@ -21,7 +21,7 @@ If you want regular promotion to be applied only for a limited number of times,
 <p>Orders with status <code>Canceling</code> or <code>Canceled</code> do not count in the defined limit.</p>
 </div>
 
-![promotion-with-restriction-en](https://images.ctfassets.net/alneenqid6w5/5yz4Gzh3nao86gISu8OsCu/d7a18088185d781c140916bc1bf2299e/Promotion_with_restriction_-_EN.png)
+![promotion-with-restriction-en](//images.ctfassets.net/alneenqid6w5/5yz4Gzh3nao86gISu8OsCu/d7a18088185d781c140916bc1bf2299e/Promotion_with_restriction_-_EN.png)
 
 You can also set the limit per customer, rather than a general usage limit. To do so, simply perform the configuration above, then click on **Enable usage limit per customer**.
 
diff --git a/docs/tutorials/en/how-to-create-a-store-name.md b/docs/tutorials/en/how-to-create-a-store-name.md
index 5e86e505d..9cfd3d261 100644
--- a/docs/tutorials/en/how-to-create-a-store-name.md
+++ b/docs/tutorials/en/how-to-create-a-store-name.md
@@ -23,7 +23,7 @@ To create or edit a [store name](https://help.vtex.com/pt/tutorial/o-que-e-store
 4. Access [Account management](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager) > **Account**.
 5. In the Store section, you will see the store names that already exist in your account. You can edit the information for each store or create a new store name by clicking the **Configure this store** button.
 
-![Store name configuration](https://images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/fd371329c163b0611c188cd6816e8ccf/EN.PNG)
+![Store name configuration](//images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/fd371329c163b0611c188cd6816e8ccf/EN.PNG)
 
 Learn how to set up your stores' domain in the article [Changing the domain of the store](https://help.vtex.com/en/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
diff --git a/docs/tutorials/en/how-to-create-a-subscription-attachment.md b/docs/tutorials/en/how-to-create-a-subscription-attachment.md
index 3377d8f8d..a9a389211 100644
--- a/docs/tutorials/en/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/en/how-to-create-a-subscription-attachment.md
@@ -71,11 +71,11 @@ Follow the step-by-step instructions below to configure available frequencies an
 
         * **Weekly**: possible values for this field are `0`, `1`, `2`, `3`, `4`, `5`, and `6`, representing the days of the week. Consider `0` = Sunday, `1` = Monday, `2` = Tuesday, and so on until `6` = Saturday. Separate the values by `,`, as illustrated below.
 
-        ![EN Assinatura Exemplo Valores week](https://images.ctfassets.net/alneenqid6w5/3pNwE8MSIe9GevIiLZxBOf/ecba3debced2525d6cd3ab3cbbdf4a5f/EN_Assinatura_Exemplo_Valores_week.png) 
+        ![EN Assinatura Exemplo Valores week](//images.ctfassets.net/alneenqid6w5/3pNwE8MSIe9GevIiLZxBOf/ecba3debced2525d6cd3ab3cbbdf4a5f/EN_Assinatura_Exemplo_Valores_week.png) 
 
         * **Monthly**: possible values for filling in this field at checkout are = `1`, `2`, `3`, (...) until `28`, representing the days of the month. Consider `1` = the first day of the month, `2` = the second day of the month, and so on until `28` = the twenty-eighth day of the month. Separate the values by `,`, as illustrated below.
 
-        ![EN Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/15AueDNpKyx3yBVjP0q7tY/415def684e81619e96155a1fb390a4f4/EN_Assinatura_Exemplo_Valores_month.png)
+        ![EN Assinatura Exemplo Valores month](//images.ctfassets.net/alneenqid6w5/15AueDNpKyx3yBVjP0q7tY/415def684e81619e96155a1fb390a4f4/EN_Assinatura_Exemplo_Valores_month.png)
 
 <div class="alert alert-info">
   <p>If the <strong>Permitted Values</strong> field is left blank, the date of the subscription cycle will be the same day of the week (if the frequency is weekly) or the same day of the month (if the frequency is monthly) as the original order.</p>
diff --git a/docs/tutorials/en/how-to-create-conditional-prices.md b/docs/tutorials/en/how-to-create-conditional-prices.md
index 69ead8238..dfbd362d3 100644
--- a/docs/tutorials/en/how-to-create-conditional-prices.md
+++ b/docs/tutorials/en/how-to-create-conditional-prices.md
@@ -34,4 +34,4 @@ So here is a step by step showing how you can use this feature :
 6. You can define a short message, called *Teaser*, to promote this condition to your customers. (To learn more, see [Teasers - Coming Soon])
 7. Save it
 
-![conditionalPrice](https://images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
+![conditionalPrice](//images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
diff --git a/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md b/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md
new file mode 100644
index 000000000..a5a2df870
--- /dev/null
+++ b/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md
@@ -0,0 +1,86 @@
+---
+title: 'How to customize the Checkout UI Custom in the Admin'
+id: 548aDBJciQu97Vh0BhEiWx
+status: PUBLISHED
+createdAt: 2024-01-04T13:27:04.734Z
+updatedAt: 2024-01-04T18:28:45.989Z
+publishedAt: 2024-01-04T18:28:45.989Z
+firstPublishedAt: 2024-01-04T18:28:45.989Z
+contentType: tutorial
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: how-to-customize-the-checkout-ui-custom-in-the-admin
+locale: en
+legacySlug: how-to-customize-the-checkout-ui-custom-in-the-admin
+subcategory: 6XAvmMxp7yyY06ewYMuggs
+---
+
+The Checkout customizations covered in this article are made using the Checkout UI Custom app. Before configuring it in your app, check if the app is installed in your store or install it as explained in the[ Checkout UI Custom](https://developers.vtex.com/docs/apps/vtex.checkout-ui-custom) article.
+
+## Customizing the Checkout
+
+In the VTEX Admin, go to **Store Settings > Storefront > Checkout UI Custom** or type **Checkout UI Custom** in the search bar at the top of the page.
+
+The app's customizing features can be found in the following Admin tabs:
+
+* [Layout](#layout)
+* [Colors](#colors)
+* [JavaScript](#javascript)
+* [CSS](#css)
+* [History](#history)
+
+## Layout
+
+In this tab, you can configure the following:
+
+1. **Payment option as accordion:** by enabling this button, the payment methods are displayed in a cascade (accordion) if up to five payment methods are available. When disabled, the payment methods will be displayed in side tabs.
+
+2. **Simplified shipping date:** by enabling this button, the user can view the delivery estimate in date format (e.g., "Monday, 09/18/23").  When disabled, the data provided will be limited to an estimate of the delivery time in days (e.g., "up to 5 working days").
+
+3. **Show item unit price:** by enabling this button, the user will see both the unit price of each product and the total amount for that product based on the product's quantity. When disabled, only the product's unit price will be displayed.
+
+4. **Show Notes field:** by enabling this button, a box will be displayed for the user to add additional comments to the order, such as a birthday message if the product is a gift or a comment about the delivery. When disabled, this box will not be displayed.
+
+5. **Hide email step:** by enabling this button, the option to automatically enter information via email is disabled. When disabled, the contact information must be entered manually.
+
+6. **Google address form:** this is an address form integration with Google (beta). By enabling this button, when the user enters the address, autocomplete suggestions will be offered. Selecting one of these suggestions will automatically complete the address fields.
+
+7. **Text size:** it allows you to change the font size (in pixels) in the Checkout.
+
+8. **Border radius:** it allows you to customize the rounding format of the outer border (in pixels) in the Checkout.
+
+9. **Button border radius:** it allows you to customize the rounding format of the button border (in pixels) in the Checkout.
+
+10. **Text field height:** it allows you to customize the width (in pixels) of the text fields in the Checkout.
+
+11. **Max. wrapper width:** it allows you to set the maximum width (in pixels) of the information displayed in the Checkout.
+
+12. **Container border:** it allows you to configure the [type of border](https://www.w3schools.com/css/css_border.asp) for Checkout sections.
+
+13. **Font family:** it allows you to configure the font types used in the Checkout.
+
+## Colors
+
+The Colors tab allows you to customize the checkout colors in your store, including backgrounds, buttons, text, and more. This standardization ensures consistent design.
+
+![Colors](//images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/82c33725eabb61f10ba13b8d2406e4d8/Colors_-_EN.png)
+
+## JavaScript
+
+The JavaScript tab adds an additional layer of customization to the interface by allowing you to add scripts.
+
+![Java - EN](//images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/045facf9e300f701eb07395dbfbb1570/Java_-_EN.png)
+
+## CSS
+
+The CSS tab allows the store layout customization by adding CSS code.
+
+![CSS - EN](//images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/6911348bbacbba2fee4c7bc0bfd8a1df/CSS_-_EN.png)
+
+## History
+
+It allows you to view and restore previously created and published customizations.
+
+![Histórico - EN](//images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/85741110e6bd7c7ad0914adce2124bcb/Hist_rico_-_EN.png)
+
+To ensure that your configuration is successfully applied, complete the necessary settings and click `Publish`.
diff --git a/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
index d5cf9adb3..1694aead9 100644
--- a/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
@@ -23,7 +23,7 @@ You can change the **textLink** of existing products anytime in the VTEX Admin,
 
 Check out the [Filling rules](#filling-rules) section to understand the restrictions on this field.
 
-![textlink.en](https://images.ctfassets.net/alneenqid6w5/2FDLvlMqvZNRCAiCoFNbfB/3485de69b69d5245045063e617177c70/textlink.en.png)
+![textlink.en](//images.ctfassets.net/alneenqid6w5/2FDLvlMqvZNRCAiCoFNbfB/3485de69b69d5245045063e617177c70/textlink.en.png)
 
 <div class="alert alert-info">
   <p>You can also change a product's page URL using the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview">Catalog API</a>. In this case, you must change the field <code>LinkId</code>. See <a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product">Update Product</a> for more information.</p>
diff --git a/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md b/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md
index a6d914239..7cafe8dac 100644
--- a/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md
+++ b/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md
@@ -19,4 +19,4 @@ In the unfortunate event that you need to rollback your app to the previous vers
 
 If you realize that the deprecation was unecessary and need to republish highest version of your app, you can run `vtex undeprecate`.
 
-![image (2)](https://images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
+![image (2)](//images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
diff --git a/docs/tutorials/en/how-to-disable-a-transactional-email.md b/docs/tutorials/en/how-to-disable-a-transactional-email.md
index 6909688ee..abb4f3f0b 100644
--- a/docs/tutorials/en/how-to-disable-a-transactional-email.md
+++ b/docs/tutorials/en/how-to-disable-a-transactional-email.md
@@ -28,7 +28,7 @@ Proceed with the following steps:
 3. Type in __Payment Pending__ in the search box.
 4. Uncheck the __Enable email sending__ option.
 
-  ![Message Center - Desativar - EN](https://images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d09c9060f369f1f0dbe90706047d8bc3/dlSCQPRLKf46SnYGl7X9a_EN_Payment_Pending.jpg)
+  ![Message Center - Desativar - EN](//images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d09c9060f369f1f0dbe90706047d8bc3/dlSCQPRLKf46SnYGl7X9a_EN_Payment_Pending.jpg)
 
 5. Click on __Save__.
 
diff --git a/docs/tutorials/en/how-to-download-the-vtex-invoices.md b/docs/tutorials/en/how-to-download-the-vtex-invoices.md
index 5590cdd81..6bce905d5 100644
--- a/docs/tutorials/en/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/en/how-to-download-the-vtex-invoices.md
@@ -46,7 +46,7 @@ To download your invoice, follow the steps below:
 
 The invoice will then be appear in another tab.
 
-![baixar faturas en](https://images.ctfassets.net/alneenqid6w5/4kge4ovIXcBv8EYizjg2ro/cd75e5882e47da9114a87979c13c1f9b/baixar_faturas_en.gif)
+![baixar faturas en](//images.ctfassets.net/alneenqid6w5/4kge4ovIXcBv8EYizjg2ro/cd75e5882e47da9114a87979c13c1f9b/baixar_faturas_en.gif)
 
 ## Brazil 
 
@@ -66,7 +66,7 @@ To download your "boleto", follow the steps below:
 
 <div class="alert alert-info">In Brazil, a purple invoice can indicate that it is overdue but that a new "boleto" with an upcoming due date has already been issued. In such cases, the invoice will continue as overdue until it's paid. If no payment is made, the invoice color will switch to red again.</div>
 
-![baixar boletos en](https://images.ctfassets.net/alneenqid6w5/4NxkYNfPImdKOMzCkuUAmp/4e545d21ada8b602c02ea337ff209d40/baixar_boletos_en.gif)
+![baixar boletos en](//images.ctfassets.net/alneenqid6w5/4NxkYNfPImdKOMzCkuUAmp/4e545d21ada8b602c02ea337ff209d40/baixar_boletos_en.gif)
 
 ### Download "Nota Fiscal"
 
@@ -83,7 +83,7 @@ The Nota Fiscal will be opened in another tab on your browser. Click on **Print
 1. In the Save as option, select **Save as PDF**.
 2. To conclude, click on **Save**.
 
-![baixar notafiscal en](https://images.ctfassets.net/alneenqid6w5/2LhJUKdHjNziL9OXoqvWQg/cbe309a9e1695dc74b7345e74c80882b/baixar_notafiscal_en.gif)
+![baixar notafiscal en](//images.ctfassets.net/alneenqid6w5/2LhJUKdHjNziL9OXoqvWQg/cbe309a9e1695dc74b7345e74c80882b/baixar_notafiscal_en.gif)
 
 If you have questions about the amount charged on the invoice, read the article on [understanding the value of approved revenues](https://help.vtex.com/tutorial/understanding-the-value-of-approved-revenues--tutorials_4322).
 
diff --git a/docs/tutorials/en/how-to-identify-a-page-template.md b/docs/tutorials/en/how-to-identify-a-page-template.md
index 51901207e..4ca1cdeb3 100644
--- a/docs/tutorials/en/how-to-identify-a-page-template.md
+++ b/docs/tutorials/en/how-to-identify-a-page-template.md
@@ -27,7 +27,7 @@ VTEX uses the same principle. The directory (folder) is where all the informatio
 
 We can create any number of templates but we have to specify in the directory which template is to be exhibited. Using the __Account__ page as an example:
 
-![cms-template-pagina EN](https://images.ctfassets.net/alneenqid6w5/4Zu301bdyU2EsSIK0aGycG/1118a06dfeed0f9e11f6669c1bdef337/Produto_CMS_EN.png)
+![cms-template-pagina EN](//images.ctfassets.net/alneenqid6w5/4Zu301bdyU2EsSIK0aGycG/1118a06dfeed0f9e11f6669c1bdef337/Produto_CMS_EN.png)
 
 Storefront > Layout > CMS Foulder > Sites and channels > Account Name > (/) Foulder > Account *(following the example)* > Click on the link with the red "ok" arrow.
 
@@ -39,13 +39,13 @@ To make this more flexible, it is also possible to include subtemplates and any
 
 Now a real example: I want to know what page I am browsing on right now:
 
-![página-loja EN](https://images.ctfassets.net/alneenqid6w5/8rd8A3NxvOeaSYqqa2Wyy/75863ff3536180f32ed8388435175940/exemplo_loja_em_ingles.png)
+![página-loja EN](//images.ctfassets.net/alneenqid6w5/8rd8A3NxvOeaSYqqa2Wyy/75863ff3536180f32ed8388435175940/exemplo_loja_em_ingles.png)
 
 The domain itself often helps me identify it, but some stores may customize this, making this identification more difficult. If I am unsure if I am on a __Departament__ or __Category__ page, this may well be that the shelf has been customized. 
 
 The best way is checking the Source Code for the page (Ctrl + U). VTEX stores will have an indication of the directory to which the page belongs.
 
-![template-cms-exemplo en](https://images.ctfassets.net/alneenqid6w5/emC1qyMArCYWKcKg0M2UM/3cb37ecc2ae2f01f265d8b4dd25cbfff/exemplo_loja_em_ingles_PRODUCT.png)
+![template-cms-exemplo en](//images.ctfassets.net/alneenqid6w5/emC1qyMArCYWKcKg0M2UM/3cb37ecc2ae2f01f265d8b4dd25cbfff/exemplo_loja_em_ingles_PRODUCT.png)
 
 In the example above: `<!-- CommerceContext.Current.VirtualFolder.Name: @Produto@ -->`
 Now that we know that it is a category page, we have to find out which template is active for Categoria. To this, you need only repeat the process described in the previous example.
diff --git a/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md b/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md
index f7418b7fb..0e57909d6 100644
--- a/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md
+++ b/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md
@@ -26,7 +26,7 @@ To do so, follow the steps below:
 1. To disable the JS of the page, just add `/tools.html` at the end of the URL. E.g.: {AccountName}.myvtex.com/tools.html
 2. Click on __Disable__ in the __Client JavaScript is__ tab. 
 
-![javascript-disable ](https://images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
+![javascript-disable ](//images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
 
 3. Next, remove `/tools.html` from the URL and update the page.
 
diff --git a/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
index 1ce7d771e..f873ef416 100644
--- a/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
@@ -28,10 +28,10 @@ You can place a test order in the store and then check in **Orders Management**
 
 Example: Imagine an order in which free shipping has been applied, but you don't know the reason. By clicking on an order in **Orders Management**, you would find the name of the promotion registered in the **Sales and Marketing** or **Promotions and Partnerships** section.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/708046486a825d2d2ec3c40ec20a9da2/detalhes-oms-en.png" alt="order-details" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/708046486a825d2d2ec3c40ec20a9da2/detalhes-oms-en.png" alt="order-details" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
 </em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/6acf4788ee8432dbfb24d7d790197022/detalhes-neworders-en.png" alt="order-details-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/6acf4788ee8432dbfb24d7d790197022/detalhes-neworders-en.png" alt="order-details-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
  (Beta)</em></figcaption></figure>
 
 If no promotion is listed, it indicates that the free shipping is not caused by a promotion, i.e. the shipping calculation in the **Inventory & shipping** module has resulted in zero. In this case, you have to use the **Shipping Simulator** to understand why shipping had zero value.
@@ -42,7 +42,7 @@ In the cart, you can move your mouse over the question mark icon below the price
 
 However, if more than one promotion is applied, what appears will be the sum of the discounts, making it difficult to analyze the scenario.
 
-![example-cart](https://images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/324846b73794d9a19305cfb4d9486ab1/image6.png)
+![example-cart](//images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/324846b73794d9a19305cfb4d9486ab1/image6.png)
 
 ## orderForm
 
diff --git a/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
index 0e2d7f692..45ec9c276 100644
--- a/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
@@ -28,8 +28,8 @@ A <strong>10 MB</strong> XLS file allows you to register an average <strong>50.0
 ## How to upload the spreadsheet
 1. Click on __Inventory & shipping__, on the __Orders__ section of the sidebar.
 2. On the options that open up, click on __Pickup points__.
-3. Click on the __Upload an XLS__ link, located on the top-right corner of the page. ![Upload XLS](https://images.ctfassets.net/alneenqid6w5/4rUkTvzcqso46aGcsOYwMc/e8cf57f6c1ee560062dc8c1bfd7767ba/Upload_XLS.png)
-4. A modal window will appear, allowing you to upload your `.xls` extension file or to download the [example spreadsheet](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Remember that it comes with lines filled with example values, so you must replace them with your pickup points' actual data. ![modal (EN)](https://images.ctfassets.net/alneenqid6w5/52EN8SmteU0kQK4U0YKy8a/1129dc87228d86800e06b455d5ccddf2/modal__EN_.png)
+3. Click on the __Upload an XLS__ link, located on the top-right corner of the page. ![Upload XLS](//images.ctfassets.net/alneenqid6w5/4rUkTvzcqso46aGcsOYwMc/e8cf57f6c1ee560062dc8c1bfd7767ba/Upload_XLS.png)
+4. A modal window will appear, allowing you to upload your `.xls` extension file or to download the [example spreadsheet](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Remember that it comes with lines filled with example values, so you must replace them with your pickup points' actual data. ![modal (EN)](//images.ctfassets.net/alneenqid6w5/52EN8SmteU0kQK4U0YKy8a/1129dc87228d86800e06b455d5ccddf2/modal__EN_.png)
 5. With all set, your new pickup points will be available to your clients.
 
 
diff --git a/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md
index ceeb40150..67ce0c68e 100644
--- a/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -27,30 +27,30 @@ After the proper definitions, the collection is linked to the shop window at **S
 
 In the example below, we will define a shop window shown on the Home page. Therefore, select **Settings**, then **add object**, as in the following image.
 
-![coleção2](https://images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
+![coleção2](//images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
 
 This command will open the **Visual Controls**, that correspond to the showcase where you want to display the collection. Add a _Collection_, but be sure to set a name for it.
 
-![coleção3](https://images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
+![coleção3](//images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
 
-![coleção4](https://images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
+![coleção4](//images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
 
 Remember to save the settings so that you can edit the control created.
 
-![coleção5](https://images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
+![coleção5](//images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
 
-![coleção6](https://images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
+![coleção6](//images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
 
 To edit the control, it is necessary to add its contents, which represent each set of items to be displayed.
 Are they:
 _Layout_: Select the shelf template used in the showcase.
 _Number of Columns, Number of Items, Show Unavailable_ and _Ramdom ad Paged_: Define the layout, quantity, and the criteria for displaying the items.
 
-![coleção7](https://images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
+![coleção7](//images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
 
 Remember to save your changes before you search or change pages.
 The next step is to add the content by selecting **Add Content**.
-![coleção8](https://images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
+![coleção8](//images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
 
 It is possible to define each content by using collections or search results, by using search parameters (further details [here](/en/tutorial/search-parameters "here"))
 
@@ -60,7 +60,7 @@ _QueryString_: The parameters entered in this field define the search result tha
 
 In the **Product Cluster (Collection)** field, you must select the collection that will be displayed by completing the following step:
 
-![coleção10](https://images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
+![coleção10](//images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
 
 The contents to be filled in the **Display Condition** part:
 _Partner, Campaign_ and _Source_: Define the display of this content if the visitor has a corresponding UTM in its source URL.
@@ -72,7 +72,7 @@ After the settings, check **Active Content** and add to the content list, saving
 
 The example below shows a standard shop window, with no display conditions, and another one exclusive for visits arising from Google sponsored campaign audiences (utm_source=**google**/utm_medium=**cpc**): 
 
-![coleção9](https://images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
+![coleção9](//images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
 
 In the scenario above, if the customer came from the sponsored campaign audience, the products corresponding to the result of a search for ID 200000 Brand will be displayed on the **Lançamentos** shop window, located on Home; otherwise, the products corresponding to ID 8 collection will be displayed.
 
diff --git a/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md b/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
index 4afcf80b1..c517655fe 100644
--- a/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
+++ b/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
@@ -18,12 +18,12 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 To include metadata when exporting a SKU prices spreadsheet, follow the steps below:
 
 1. Click on **Prices**, in the menu on the left side of the page
-![2019 05 27 18 56 22 Price list.jpg?h=250](https://images.ctfassets.net/alneenqid6w5/084YLwZ0JF1ptBlurtbNQ/15c9ed54e664eac0eebd3af720494acb/2019_05_27_18_56_22_Price_list.jpg_h_250)
+![2019 05 27 18 56 22 Price list.jpg?h=250](//images.ctfassets.net/alneenqid6w5/084YLwZ0JF1ptBlurtbNQ/15c9ed54e664eac0eebd3af720494acb/2019_05_27_18_56_22_Price_list.jpg_h_250)
 2. Click on **Price List**
 3. In the  upper left side of the page, select the **arrow down** button
 4. In the newly opened tab, on the left side, hover over and click on the **Export Prices Spreadsheet** button
 5. A new window will slide onto the screen, mark the box next to **include metadata in exported tables**
 6. Click on the blue **export table** button
-![2019 05 27 18 57 59 Price list.jpg?h=250](https://images.ctfassets.net/alneenqid6w5/3fhLCNPgh0gZO03Hwd9doY/a9dca1de548aa67081bbe578ac75d57d/2019_05_27_18_57_59_Price_list.jpg_h_250)
+![2019 05 27 18 57 59 Price list.jpg?h=250](//images.ctfassets.net/alneenqid6w5/3fhLCNPgh0gZO03Hwd9doY/a9dca1de548aa67081bbe578ac75d57d/2019_05_27_18_57_59_Price_list.jpg_h_250)
 
 You'll receive an email with the exported table shortly.
diff --git a/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md b/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
index 715bc0353..4cad8e6d9 100644
--- a/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
+++ b/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
@@ -3,8 +3,8 @@ title: 'How to insert a reverse proxy in front of VTEX services'
 id: 4PFWsfRAKviNVPf1bYdiir
 status: PUBLISHED
 createdAt: 2019-09-20T14:11:30.301Z
-updatedAt: 2020-08-20T21:15:13.613Z
-publishedAt: 2020-08-20T21:15:13.613Z
+updatedAt: 2023-10-26T22:21:31.465Z
+publishedAt: 2023-10-26T22:21:31.465Z
 firstPublishedAt: 2019-09-23T12:22:50.056Z
 contentType: tutorial
 productTeam: Reliability
@@ -16,11 +16,10 @@ subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
 <div class="alert alert-danger">
-  <strong>Warning:</strong> The explanations in this article aim to address cases of rare exception. We do not recommend any store to use reverse proxy. When using a reverse proxy, all VTEX managed and optimized edge services (CDN) will be set aside, so that the store service is responsible for the site's actual provisioning, which is tasked with the settings, monitoring and feature management such as header forwarding, cookies and cache management. We do not provide documentation for any of the above-mentioned.
-  <br>
-VTEX does not take responsibility for problems related to this system, be it the CDN itself, WAF service or any other resource that is in front of our servers. We will not have overview of any failures and therefore the solution will <strong>not</strong> be included in our SLA agreements.
-  </div>
-  
+  <p><strong>Warning:</strong> The explanations in this article aim to address cases of rare exception. We do not recommend any store to use reverse proxy. When using a reverse proxy, all VTEX managed and optimized edge services (CDN) will be set aside, so that the store service is responsible for the site's actual provisioning, which is tasked with the settings, monitoring and feature management such as header forwarding, cookies and cache management. We do not provide documentation for any of the above-mentioned.</p>
+  <p>VTEX does not take responsibility for problems related to this system, be it the CDN itself, WAF service or any other resource that is in front of our servers. We will not have overview of any failures and therefore the solution will <strong>not</strong> be included in our SLA agreements.</p>
+</div>
+
 If even after reading the warning  above you still want to forward your own CDN to the VTEX CDN, you need to insert a reverse proxy in front of VTEX services. To this end, create the TXT entries indicated below. These will serve as a confirmation input to let us know that the host actually points to VTEX. Without this, VTEX cannot provide navigation.
 
 1. In your domain's DNS, create a TXT type entry in `_{hostname}` having the same value as the one used in CNAME.
@@ -34,8 +33,10 @@ Therefore, the configuration should look as follows:
 In addition to this, all `/.well-known/acme-challenge/*` traffic must reach VTEX. Some reverse proxies capture this route and therefore cannot issue or renew the SSL certificate.
 
 <div class="alert alert-warning">
-VTEX only provides navigation if: <br>
-- We can confirm that the host points to VTEX (as per our CNAME).<br>
-- We can issue/renew SSL certificates to the host.<br>
-If either condition is not met, VTEX will stop delivering the site because it is characterized as being down.
-<br>
+  <p>VTEX only provides navigation if:
+    <ul>
+      <li>We can confirm that the host points to VTEX (as per our CNAME).</li>
+      <li>We can issue/renew SSL certificates to the host.</li>
+    </ul>
+If either condition is not met, VTEX will stop delivering the site because it is characterized as being down.</p>
+</div>
diff --git a/docs/tutorials/en/how-to-install-a-service-worker.md b/docs/tutorials/en/how-to-install-a-service-worker.md
index ad851945c..2fa7e5439 100644
--- a/docs/tutorials/en/how-to-install-a-service-worker.md
+++ b/docs/tutorials/en/how-to-install-a-service-worker.md
@@ -3,33 +3,35 @@ title: 'How to install a Service Worker'
 id: 2H057iW0mQGguKAciwAuMe
 status: PUBLISHED
 createdAt: 2018-03-13T14:53:11.260Z
-updatedAt: 2023-04-05T17:55:03.904Z
-publishedAt: 2023-04-05T17:55:03.904Z
+updatedAt: 2024-01-19T12:54:32.525Z
+publishedAt: 2024-01-19T12:54:32.525Z
 firstPublishedAt: 2018-03-13T17:48:34.728Z
 contentType: tutorial
 productTeam: Financial
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 2AhArvGNSPKwUAd8GOz0iU
 slug: how-to-install-a-service-worker
 locale: en
 legacySlug: how-to-install-a-service-worker
-subcategory: 
+subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
 Service Worker is a script that your browser runs in the background, separate from the Web, enabling features such as periodic synchronization, push notifications and even running offline.
 
 To create the script, follow the step-by-step instructions below:
 
-1. In the VTEX Admin, access the module __Portal__.
-2. Click the __Settings__ icon.
-3. Then click on the __Code__ tab.
-4. Click __New__ and then __File__.
-5. Include the file name exactly as: ` service-worker.js`.
-6. Set the __feature__.
-7. To finish, click __Save__.
+1. In the VTEX Admin, go to **Store Settings > Storefront > Checkout**, or type **Checkout** in the search bar at the top of the page.
+2. Click the <i class="fas fa-cog"></i> icon of the desired site.
+3. In the `Code` tab, click the `New` buttton.
+4. Then click on `File`.
+5. Fill in the file name exactly like: `service-worker.js`.
+6. Click the `Create` button.
+7. Set the feature.
+8. Click the `Save` button.
 
 Although the file is in `/files/service-worker.js`, it receives the `Service-Worker-Allowed` header with the value `/`, which allows you to intercept requests from the site root.
 
-For [more information](https://developers.google.com/web/fundamentals/primers/service-workers/), see Google Developers Web Fundamentals.
+For more information, see Google Developers [Web Fundamentals](https://developers.google.com/web/fundamentals/primers/service-workers/).
 
 ### Related articles
+
 - [How to turn my store into a PWA](https://help.vtex.com/en/tutorial/how-to-turn-my-store-website-into-a-pwa--3i8VmYeToAUGKgo2kKK6I2)
diff --git a/docs/tutorials/en/how-to-integrate-an-external-gift-card-provider-with-vtex.md b/docs/tutorials/en/how-to-integrate-an-external-gift-card-provider-with-vtex.md
index 2e6df86c3..640a611f3 100644
--- a/docs/tutorials/en/how-to-integrate-an-external-gift-card-provider-with-vtex.md
+++ b/docs/tutorials/en/how-to-integrate-an-external-gift-card-provider-with-vtex.md
@@ -3,8 +3,8 @@ title: 'How to integrate an external Gift Card provider with VTEX'
 id: tutorials_450
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:26.566Z
-updatedAt: 2023-04-13T12:40:41.423Z
-publishedAt: 2023-04-13T12:40:41.423Z
+updatedAt: 2024-06-04T18:55:35.271Z
+publishedAt: 2024-06-04T18:55:35.271Z
 firstPublishedAt: 2017-04-27T23:03:24.938Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,18 @@ legacySlug: how-to-integrate-with-a-gift-card
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, you can use the Gift Card as a credit program.
+At VTEX, you can use the gift card as a credit program.
 
 In this context, there are cases of customers who already work with their own provider. This system manages your credits under a base of customers who participate in a loyalty system, for example.
 
-That said, the customer has the option of integrating the external solution with the VTEX system. In this article we will explain the step by step to make this integration.
+If the customer wishes to integrate an external gift card solution into the VTEX system, it is necessary to use the [Giftcard Provider Protocol](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol).
 
 ## Provider development
-VTEX has a Gift Card Provider Protocol, a guide to API calls that will be made to communicate with our system.
 
-The customer must develop a middleware - a system that intermediates between two different systems, in this case, the external provider and VTEX’s systems.
-Once implemented, it will be able to receive calls from VTEX and interpret the information contained in each of them.
+Through the [Giftcard Provider Protocol](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol), the external gift card provider must develop a [middleware](https://en.wikipedia.org/wiki/Middleware) to transmit information between your system and VTEX.
 
-For more details, read our technical documentation on the [Gift Card Provider Protocol](https://developers.vtex.com/docs/guides/giftcard-provider-protocol-overview). 
+For more information about the gift card system at VTEX, visit [Giftcard Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api).
 
-## Sending the endpoint
-After that, the customer must send to VTEX the endpoint that will be used to make the calls. This route will act as a bridge between the two systems.
-Finally, VTEX adds the provider's endpoint to its system. In this way, the external Gift Card system will be integrated with VTEX and will be used every time the customer uses it as a payment method.
+## Sending endpoint information
+
+After creating the middleware, the provider must open a [ticket](https://help.vtex.com/en/support) on VTEX informing the endpoints to be used for customers to carry out payment transactions using its gift card system.
diff --git a/docs/tutorials/en/how-to-manage-subscriptions.md b/docs/tutorials/en/how-to-manage-subscriptions.md
index f4f20e31a..1ef0cd6aa 100644
--- a/docs/tutorials/en/how-to-manage-subscriptions.md
+++ b/docs/tutorials/en/how-to-manage-subscriptions.md
@@ -3,8 +3,8 @@ title: 'How to manage Subscriptions'
 id: 6Jk50FPbv6iuz1OsFypv8x
 status: PUBLISHED
 createdAt: 2020-02-05T14:18:54.781Z
-updatedAt: 2022-12-05T16:48:31.127Z
-publishedAt: 2022-12-05T16:48:31.127Z
+updatedAt: 2023-12-21T14:08:39.725Z
+publishedAt: 2023-12-21T14:08:39.725Z
 firstPublishedAt: 2020-02-11T14:56:17.333Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -35,22 +35,26 @@ The **Unique Subscriptions** section allows you to:
 - View a **dynamic chart** with the *active*, *canceled* and *all* subscriptions within the selected period. By hovering the cursor over the chart lines, you can see in detail the subscriptions variation per day.
 - **Export subscriptions** within the filtered period by clicking on the button in the upper right corner of the screen.
 
- ![EN Dashboard Assinatura única](https://images.ctfassets.net/alneenqid6w5/1UiNoDxKut3m9UUbhDBZoa/5d6af9bbfcc2d46e751050f5c848f206/EN_Dashboard_Assinatura___nica.png)
+ ![EN Dashboard Assinatura única](//images.ctfassets.net/alneenqid6w5/1UiNoDxKut3m9UUbhDBZoa/5d6af9bbfcc2d46e751050f5c848f206/EN_Dashboard_Assinatura___nica.png)
 
 ### Subscription Orders
 
+<div class = "alert alert-info">
+You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
+</div>
+
 The **Subscription Orders** section allows you to:
 
 - Filter the **Subscription Orders Funnel** by date, applying the following filters: `today`, `yesterday`, `this week`, `this month`, `this year`, `last week`, `last month`, `last year` or a `custom` period (by selecting specific dates).
 - Monitor the **absolute number and corresponding percentage** of Subscription Orders that were *scheduled*, *processed*, *generated* and *completed* per period.
 - View a **chart** with the percentage of *skipped* orders, *cycles with an issue* and *payment errors*.
 
-![EN Dashboard Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/hZxhtReMjrrwi4VQl8Pyu/bb2e62f626072108fba24e78db87dc15/EN_Dashboard_Pedidos_Assinatura.png)
+![EN Dashboard Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/hZxhtReMjrrwi4VQl8Pyu/bb2e62f626072108fba24e78db87dc15/EN_Dashboard_Pedidos_Assinatura.png)
 
 - When accessing each tab of the **Subscription Orders** table, you can view the flow and details of the orders that were *skipped*, those that presented *Cycles with an issue*, those that contain a *Payment Error* and the *Completed* orders. 
 - In addition to listing the details of the errors that occurred during the  Subscription orders flow, it is also possible to perform a **manual retry** of orders with errors. Check out our article on [Troubleshooting of Subscription orders issues](https://help.vtex.com/tutorial/como-solucionar-pedidos-de-assinatura-com-erros--uLL8AYBGdtAmbbdL5gRCf) to learn more.
 
-![EN Log Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/X9H4zlZTb6t7hpAKvbJ7L/9592cb74a6690ea5c76001bfa0218c33/EN_Log_Pedidos_Assinatura.png)
+![EN Log Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/X9H4zlZTb6t7hpAKvbJ7L/9592cb74a6690ea5c76001bfa0218c33/EN_Log_Pedidos_Assinatura.png)
 
 ### Subscribers
 
diff --git a/docs/tutorials/en/how-to-manage-the-kit-stock.md b/docs/tutorials/en/how-to-manage-the-kit-stock.md
index f55141590..7e37d9401 100644
--- a/docs/tutorials/en/how-to-manage-the-kit-stock.md
+++ b/docs/tutorials/en/how-to-manage-the-kit-stock.md
@@ -3,8 +3,8 @@ title: 'Managing the kit stock'
 id: frequentlyAskedQuestions_156
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.252Z
-updatedAt: 2019-12-31T15:26:27.183Z
-publishedAt: 2019-12-31T15:26:27.183Z
+updatedAt: 2024-04-29T13:09:03.955Z
+publishedAt: 2024-04-29T13:09:03.955Z
 firstPublishedAt: 2019-01-24T22:03:46.311Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,17 +19,13 @@ A kit can be assembled in two ways. Below, see some considerations about each of
 
 ## Kit product without components
 
-That's normally a product that is already structured as a kit (several components) in the store distribution center. VTEX only indicates this product, without the need for registration of its components. 
-
-That is, both the price and the stock are displayed directly on the SKU kit.
+That's normally a product that is already structured as a kit (several components) in the store distribution center. VTEX only indicates this product, without the need for registration of its components. That is, both the price and the stock are displayed directly on the SKU kit.
 
 ## Kit product with components
 
 The kit with components is the idea of a kit product whose SKU is a "cluster" of other SKUs. This model is normally used when the kit consists of other products that are already in store, and are sold separately by origin. So, the store SKUs are selected, and the price and the stock needed for each SKU to compose 1 (one) of this kit products are settled.
 
-![](//images.contentful.com/alneenqid6w5/42WZMhNkPSaq2mCkQSQI0G/4c411361196ea8d24a8a1a08aabfa783/kit.png)
-
-In the example above, the kit Product called **Colorido** is composed by other 10 SKUs. Each, with its required amount of 1 (one) SKU item to compose the kit.
+For example, a kit product called Colorido is composed by other 10 SKUs. Each, with its required amount of 1 (one) SKU item to compose the kit.
 
 ![](//images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
 
diff --git a/docs/tutorials/en/how-to-manually-invoice-an-order.md b/docs/tutorials/en/how-to-manually-invoice-an-order.md
index 2506b77a4..430b759c2 100644
--- a/docs/tutorials/en/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/en/how-to-manually-invoice-an-order.md
@@ -3,8 +3,8 @@ title: 'How to invoice an order'
 id: 7p1h852V5t54KyscpgxE2v
 status: PUBLISHED
 createdAt: 2020-12-28T20:50:42.445Z
-updatedAt: 2023-05-31T14:44:54.458Z
-publishedAt: 2023-05-31T14:44:54.458Z
+updatedAt: 2024-04-01T17:55:58.671Z
+publishedAt: 2024-04-01T17:55:58.671Z
 firstPublishedAt: 2020-12-28T21:01:55.107Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,7 +21,7 @@ It is also on this page that the store can manually add and check the [order inv
 
 To invoice the order on the VTEX platform, you need to add the items' invoice to the **Orders** module. You must invoice the order so that the invoice is available to the customer and the [order flow](https://help.vtex.com/en/tutorial/order-flow-on-the-oms--tutorials_196) is complete. The invoice can be sent:
 
-* Via [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice) 
+* Via [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice).
 * Via VTEX Admin.
 
 <div class = "alert alert-info">
@@ -34,7 +34,7 @@ To send the invoice via VTEX Admin, follow the steps below:
 2. Search for the order by using the search bar [or the filters](https://help.vtex.com/en/tutorial/como-filtrar-pedidos--tutorials_192).  
 3. Click the desired order.     
 4. Scroll down to the Invoice to items section, and click on the arrow icon <i class="fas fa-chevron-right"></i> to expand.  
-![Itens faturarEN](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
+![Itens faturarEN](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
 5. Click the `Invoice` button. 
 6. Click the desired billing option:      
     * **Submit invoice referencing items:** to invoice the order referencing the package items.  
@@ -64,7 +64,8 @@ To send the invoice via VTEX Admin, follow the steps below:
 
 After the order is `Invoiced`, go to the **Invoice** section to check the invoices added, as shown in the image below:
 
-![FaturaEN](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
+![FaturaEN](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
 
 For [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe), when [changing or removing items from an order](https://help.vtex.com/en/tutorial/how-to-change-order-items--7jekq618QxgbsOxKkXBjE8), the order total will be updated after invoicing and will correspond to what is captured by the VTEX payment gateway.
 
+Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
diff --git a/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md b/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md
index 737871ffa..cbf999860 100644
--- a/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md
+++ b/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md
@@ -3,8 +3,8 @@ title: 'Modifying details of customers’ addresses'
 id: 3IQsuOvkMgmuwWQMQoo8UM
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:49.820Z
-updatedAt: 2023-03-28T22:57:51.457Z
-publishedAt: 2023-03-28T22:57:51.457Z
+updatedAt: 2024-06-06T20:47:33.052Z
+publishedAt: 2024-06-06T20:47:33.052Z
 firstPublishedAt: 2019-01-24T22:10:21.264Z
 contentType: tutorial
 productTeam: Master Data
@@ -18,12 +18,12 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 To edit customer information you must do the following:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. Select the **Endereços** tab. Here you will find all the users who have registered at least one address.
+2. Click on the **Addresses** tab. Here you will find all the users who have registered at least one address.
 3. Find the customer you want.
-4. In the **Ações** column of the table, click on the option **Editar**.
-5. Create or edit the required information.
-6. Click on **Salvar**.
-7. Then click on **Voltar** to see the list of addresses again.
+4. In the **Actions** column of the table, click on the edit icon <i class="fas fa-edit"></i>.
+5. Add or edit the desired information.
+6. Click `Save`.
+7. Click `Go Back` to see the list of addresses again.
 
 <div class="alert alert-warning">
 This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
diff --git a/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
index e8d3fd8ba..a03d2234b 100644
--- a/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
@@ -1,10 +1,10 @@
 ---
 title: 'Optimizing searches with substitute words '
 id: 32FqSsl5VuQyiIMEc02Uwu
-status: PUBLISHED
+status: CHANGED
 createdAt: 2019-01-24T20:45:49.707Z
-updatedAt: 2021-09-14T19:00:59.249Z
-publishedAt: 2021-09-14T19:00:59.249Z
+updatedAt: 2024-02-28T22:28:58.551Z
+publishedAt: 2024-01-10T13:30:55.078Z
 firstPublishedAt: 2019-01-24T22:00:22.364Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,8 +16,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 ---
 
 <div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+We don't recommend using <a href="https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu">Substitute Words</a> when using Intelligent Search. To associate words with products, we recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Synonyms</a>, which allows you to manage terms per product in a more scalable way. For more information, contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a>.</div>
 
 ## How the search engine works 
 VTEX has an intelligent algorithm that, based on the term searched for, identifies the best result for the user, i.e., it always shoes the result that will generate more conversions into sales.
@@ -39,15 +38,13 @@ A resource frequently used by the internal teams to expedite searches is to inpu
 
 ### 1. Product integration 
 Integrating the products with the ProductInsertUpdate webservice permits to aggregate their Substitute Words and to associate them with the relevant products:
-<http://help.vtex.com/en/tutorial/manual-of-classes-and-methods-used-on-webservice>
+[](http://help.vtex.com/en/tutorial/manual-of-classes-and-methods-used-on-webservice)
 
 ### 2. Import by spreadsheet
-Input the Substitute Words directly through product spreadsheet, on a massive basis:
-<https://help.vtex.com/en/tutorial/registering-a-product#importing-products-through-worksheet>
+Input the Substitute Words directly through product spreadsheet, on a massive basis [](https://help.vtex.com/en/tutorial/registering-a-product#importing-products-through-worksheet)
 
 ### 3. To edit a product 
-Input the Substitute Words directly to each product individually in the field "Substitute Words":
-<https://help.vtex.com/en/tutorial/registering-a-product#registering-a-product-through-the-admin>
+Input the Substitute Words directly to each product individually in the field **Substitute Word** https://help.vtex.com/en/tutorial/registering-a-product#registering-a-product-through-the-admin
 
 ## Where do I get substitute words
 ### Google Trends
diff --git a/docs/tutorials/en/how-to-request-receivables-anticipation.md b/docs/tutorials/en/how-to-request-receivables-anticipation.md
index 36af65e58..56edb8f7b 100644
--- a/docs/tutorials/en/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/en/how-to-request-receivables-anticipation.md
@@ -31,7 +31,7 @@ Now that you have checked the balance, it is important to keep in mind that the
 
 For example, if your lowest receivable is R$ 10, this is the minimum amount you can anticipate. The maximum amount is informed in the Admin’s “Anticipate receivables” page - the balance you just checked.
 
-![antecipaçãoEN](https://images.ctfassets.net/alneenqid6w5/655LHSr6GS2RpCvCKYfAup/bade73d74e819b410247130a7662df03/image.png_h_250)
+![antecipaçãoEN](//images.ctfassets.net/alneenqid6w5/655LHSr6GS2RpCvCKYfAup/bade73d74e819b410247130a7662df03/image.png_h_250)
 
 <div class="alert alert-info">
 <strong>Warning</strong>: receivables in dispute or expected for the next business day cannot be anticipated.
diff --git a/docs/tutorials/en/how-to-retrieve-the-access-password.md b/docs/tutorials/en/how-to-retrieve-the-access-password.md
index d974cf89c..80d29bf4b 100644
--- a/docs/tutorials/en/how-to-retrieve-the-access-password.md
+++ b/docs/tutorials/en/how-to-retrieve-the-access-password.md
@@ -18,12 +18,12 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 All access passwords are managed by __VTEX ID__. Accordingly, you must access the login page, and enter your email and password to request the creation of a new password.
 
 1. In some login screen, click on **Login using your email and password;**
-![forgot-password-step1 en](https://images.ctfassets.net/alneenqid6w5/1DMWGiuOukwOYUAc0KCQmc/6dfa7485f88c61ea5dc49536edff3bb6/login_1.png)
-2. Click on **Forgot my password;**![forgot-password-step2 en](https://images.ctfassets.net/alneenqid6w5/6t3ChxuWHYkaooUiKi0OOO/6092c99fbbbc6c4acddd218e24a3abb1/login_2.png)
-3. Fill out the field with your email;![forgot-password-step3 en](https://images.ctfassets.net/alneenqid6w5/1kKj8C5zlKg6uuSyOImGEM/debf868fd9a81176e9c11a8cc9ad7f07/login_3.png)
-4. Fill out the field with the new password and click on **Register a new password**;![forgot-password-step4 en](https://images.ctfassets.net/alneenqid6w5/z7KbKetc3uMkWQgmiaQis/645c8e95657829d49e43d456625891f7/login_4.png)
+![forgot-password-step1 en](//images.ctfassets.net/alneenqid6w5/1DMWGiuOukwOYUAc0KCQmc/6dfa7485f88c61ea5dc49536edff3bb6/login_1.png)
+2. Click on **Forgot my password;**![forgot-password-step2 en](//images.ctfassets.net/alneenqid6w5/6t3ChxuWHYkaooUiKi0OOO/6092c99fbbbc6c4acddd218e24a3abb1/login_2.png)
+3. Fill out the field with your email;![forgot-password-step3 en](//images.ctfassets.net/alneenqid6w5/1kKj8C5zlKg6uuSyOImGEM/debf868fd9a81176e9c11a8cc9ad7f07/login_3.png)
+4. Fill out the field with the new password and click on **Register a new password**;![forgot-password-step4 en](//images.ctfassets.net/alneenqid6w5/z7KbKetc3uMkWQgmiaQis/645c8e95657829d49e43d456625891f7/login_4.png)
 5. Wait for the access code to be sent to you by email;
 6. Paste it on the field requested.
-7. Click on **Change password**.![forgot-password-step5 en](https://images.ctfassets.net/alneenqid6w5/3Fqh9NYhIImo8k86UKGSwa/4e38214443a88d0d1230c5ce8aca2223/login_5.png)
+7. Click on **Change password**.![forgot-password-step5 en](//images.ctfassets.net/alneenqid6w5/3Fqh9NYhIImo8k86UKGSwa/4e38214443a88d0d1230c5ce8aca2223/login_5.png)
 
 Done! The password was retrieved, and the access is released.
diff --git a/docs/tutorials/en/how-to-return-order-items.md b/docs/tutorials/en/how-to-return-order-items.md
index ca789883f..1f87cc4f8 100644
--- a/docs/tutorials/en/how-to-return-order-items.md
+++ b/docs/tutorials/en/how-to-return-order-items.md
@@ -3,8 +3,8 @@ title: 'How to return items from an order'
 id: 2bSNWwD0g8fcUmuupLao9i
 status: PUBLISHED
 createdAt: 2020-12-28T21:23:42.045Z
-updatedAt: 2023-04-11T14:58:43.881Z
-publishedAt: 2023-04-11T14:58:43.881Z
+updatedAt: 2024-06-10T23:02:44.957Z
+publishedAt: 2024-06-10T23:02:44.957Z
 firstPublishedAt: 2020-12-28T21:27:16.332Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,14 +26,18 @@ On the Order Details page, you can orchestrate this operation by completing the
 3. In the **Invoices** section, click `Return items`.
 4. Select the checkbox of the items that you want to return.
 5. Define the number of units of each item that you want to return.
-6. Enter the additional value that will be charged from your client in the `Additional value` field. This value is for the shipping cost of the returned order.<p>For example, if an order had a shipping cost of $20.00, you should fill this field with $20.00. If it is filled in with an amount less than the total shipping cost, the customer receives half of the filled in amount (**Additional Value**) as a reversal of the purchase, and the other half in giftcard. Following the example given, suppose that instead of $20.00 (which is the total shipping cost) the store has filled in the **Additional Value** as $12.00. The customer will receive this back in the form of a chargeback of US$6.00 plus a US$6.00 giftcard.</p> *It’s an optional field. Please fill in if the additional value is part of your store’s return policy.* 
+6. Enter the additional value that you will reimburse your client in the `Additional value` field. This value is for the shipping cost of the returned order.<p>For example, if an order had a shipping cost of $20.00, you should fill this field with $20.00. If it is filled in with an amount less than the total shipping cost, the customer receives half of the filled in amount (**Additional Value**) as a reversal of the purchase, and the other half in giftcard. Following the example given, suppose that instead of $20.00 (which is the total shipping cost) the store has filled in the **Additional Value** as $12.00. The customer will receive this back in the form of a chargeback of US$6.00 plus a US$6.00 giftcard.</p> *It’s an optional field. Please fill in if the additional value is part of your store’s return policy.* 
 7. Enter the reason for that added value in the `Referred to` field.
     > *It’s an optional field. Please fill in if the additional value is part of your store’s return policy.* 
 
 8. Enter the number of the `Entrance Invoice`.
-    > *This field refers to the return invoice, when the item returns back to your inventory.*
+    > *This field refers to the return invoice, when the item returns back to your inventory. The invoice number must be different from the previous invoice.*
 
 9. Inform the `Reason of return`.
 10. Click `Request chargeback`.
 
 After the refund is processed in the system, your returned items and information will be displayed in the **Returned items** section.
+
+<div class = "alert alert-info">
+You can change orders via API using the endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a>, and issue invoices after changes using the endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice">Order invoice notification</a>.
+</div>
diff --git a/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md b/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md
index 4c5b1aa01..5b6342485 100644
--- a/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md
+++ b/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md
@@ -20,7 +20,7 @@ In the section __Orders management__ you can filter the orders made in a certain
 If you want to see the orders that were closed with this benefit applied, just follow the steps below:
 
 1. In the admin menu, click on __Orders management__
-2. Click the filter button and, under the __Others__ section, click the __Promotions & Taxes__ option.![promo-filter-en](https://images.ctfassets.net/alneenqid6w5/1JFiP4ZNhmu4cWcOK4Ugs8/cdebe29a683b1561ddaacd034bbaeb1b/promo-filter-en.png)
+2. Click the filter button and, under the __Others__ section, click the __Promotions & Taxes__ option.![promo-filter-en](//images.ctfassets.net/alneenqid6w5/1JFiP4ZNhmu4cWcOK4Ugs8/cdebe29a683b1561ddaacd034bbaeb1b/promo-filter-en.png)
 3. Select this benefit and click on __Confirm__
 
 In the order list, you'll see all orders closed with this benefit.
diff --git a/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md b/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
index 490aface6..40ef81f9a 100644
--- a/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
+++ b/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
@@ -30,7 +30,7 @@ Just include an attribute with the name `salesChannel`, as illustrated in the se
 
 Thereafter, the next orders will be created using the sales channel that was set up. In the event there is no stock for a given item in this channel, the item will be excluded from the order.   
 
-![posicao.en](https://images.ctfassets.net/alneenqid6w5/8TLvzlzTkt2yUtr5Lmj5z/507d00037f92756ddc01008590350a7b/posicao.en.png)
+![posicao.en](//images.ctfassets.net/alneenqid6w5/8TLvzlzTkt2yUtr5Lmj5z/507d00037f92756ddc01008590350a7b/posicao.en.png)
 
 *The screen showing the salesChannel ID*
 
@@ -40,5 +40,5 @@ Just include an attribute with the name `defaultSLA`, as illustrated in the setu
 
 Thereafter, the SLA set up will take preference over the cheaper SLA for the next orders created – whereby, if it has a delivery window, the first interval available will be selected.
 
-![transportadora.en](https://images.ctfassets.net/alneenqid6w5/5qOOw2KsCHgxP5XmbjmEMd/7b6d0aa40ae6f9e28c269ac42f5313d5/transportadora.en.png)
+![transportadora.en](//images.ctfassets.net/alneenqid6w5/5qOOw2KsCHgxP5XmbjmEMd/7b6d0aa40ae6f9e28c269ac42f5313d5/transportadora.en.png)
 *The screen showing the ID of the SLA*
diff --git a/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
index e1e46526f..6de3fe121 100644
--- a/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
@@ -91,7 +91,7 @@ Once the tag has been set up, it is necessary to save the JS captured from the c
 
 - Accessing the VTEX panel in the CMS menu >> Layout >> File Manager >> .js File Management >> Add.
 
-![cms js](https://images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
+![cms js](//images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
 
 __Attachment__: [md5.js](//assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
 
diff --git a/docs/tutorials/en/how-to-set-up-recurrence-in-payment-conditions.md b/docs/tutorials/en/how-to-set-up-recurrence-in-payment-conditions.md
index 43b487fa1..12a4bc372 100644
--- a/docs/tutorials/en/how-to-set-up-recurrence-in-payment-conditions.md
+++ b/docs/tutorials/en/how-to-set-up-recurrence-in-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'How to set up recurrence in payment conditions '
 id: 6EGuoAytLqU2CqUuaI2GUW
 status: PUBLISHED
 createdAt: 2017-06-29T20:56:04.718Z
-updatedAt: 2023-03-30T15:57:59.484Z
-publishedAt: 2023-03-30T15:57:59.484Z
+updatedAt: 2024-01-09T19:47:20.977Z
+publishedAt: 2024-01-09T19:47:20.977Z
 firstPublishedAt: 2017-07-03T15:16:40.562Z
 contentType: tutorial
 productTeam: Financial
@@ -27,7 +27,7 @@ After this, it is possible to set the special conditions and, finally, the recur
 3. Click on the payment condition created;
 4. Click on **Add special condition**;
 5. Select the option **Expiration Date**;
-6. We will set the day range for the validity of the payment condition in **Only for these period**;
-7. Under the period, we will see the field **Recurrency**. There we can select **Every day** or (Disabling the option "All days") we can select the **weekdays** we want; ee can also set up a time to start and a time to finish;
+6. We will set the day range for the validity of the payment condition in **Only for this period**;
+7. Under the period, we will see the field **Recurrence**. There we can select **Every day** or (Disabling the option "All days") we can select the **weekdays** we want; ee can also set up a time to start and a time to finish;
 8. If we want to add another **Recurrency**, click on button `+`;
 
diff --git a/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 81c5ed263..35de21e36 100644
--- a/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'How to set up the connector to accept payments with Adyen at VTEX'
 id: tutorials_2337
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:55:10.101Z
-updatedAt: 2023-03-24T14:56:13.138Z
-publishedAt: 2023-03-24T14:56:13.138Z
+updatedAt: 2024-03-18T17:52:42.714Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:52.166Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: how-to-configure-the-adyen-gateway-on-vtex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 <div class="alert alert-warning">The configurations documented in this article are performed in an environment external to VTEX and, therefore, may be discontinued without prior notice.</div>
 
 If Adyen is your chosen affiliate, follow the necessary configuration in the step-by-step below for a seamless communication between Adyen and VTEX. 
@@ -68,7 +70,7 @@ Next, you'll just need to collect information from Adyen to register on VTEX. St
 5. Remember to write down the username and password that appear in the Password field, since it can't be viewed again!
 6. Click on the **Save** button, located in the page footer.
 7. By following these steps, your user will be successfully set up. In the image below number 1 (highlighted in red) is the username and number 2 is the password that you will have to enter on VTEX’s environment.
-![Adyen - Image 2](https://images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
+![Adyen - Image 2](//images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
 8. Send an email to Adyen support (suporte@adyen.com), requesting the permissions listed in the model below:
 
 > Subject: Setting VTEX web-service user permissions for `{accountName}`
@@ -94,13 +96,13 @@ If you intend Adyen's platform to manually revise the anti-fraud analysis of imp
 
 <ui>5. The configuration should appear as in the image below. Don't forget to click on **Save configuration** to save the changes.</ui>
 
-![Adyen - Image 1](https://images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
+![Adyen - Image 1](//images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
 
 ## VTEX Configuration
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Access the **Gateway Affiliations** tab.
-3. Click on **Adyen**.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Adyen__ in the search bar and click on the name of the provider.
 4. Fill out the form fields with the data obtained from Adyen and click on **Save**:
 
 - **Username** - Adyen username (**Adyen's configuration** 5th step)
diff --git a/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
index 5062f56c5..440d9609a 100644
--- a/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -66,6 +66,6 @@ Fill it out with the HTML below:
 <script src="https://h.online-metrix.net/fp/check.js?org_id={{cs_orgId}}&amp;session_id={{cs_merchantId}}{{cs_sessionId}}" type="text/javascript"></script>
 ```
 
-![braspag fingerprint](https://images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/84f93e14dac3c4471bb1d30b09fbf62e/image.png_h_250)
+![braspag fingerprint](//images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/84f93e14dac3c4471bb1d30b09fbf62e/image.png_h_250)
 
 At last, post the changes.
diff --git a/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
index 82ba26cf0..52c28f030 100644
--- a/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -31,7 +31,7 @@ The customer schedules the appointment using a form created by Indeva. Then you
 
 Your customer’s schedule flow starts by choosing the physical store of his preference. In the image below, there is only one registered store. But you can register as many physical stores as you want.
 
-![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
+![indeva1](//images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
 <div class="alert alert-info">
 You can also provide your customers a link that takes them directly to a specific physical store form. You just have to add the store ID at the end of the URL. Hence, your seller can share your store’s link—for example, using a QR Code or on social media.
@@ -48,7 +48,7 @@ By clicking on a store, your customer is automatically redirected to the form. T
 
 Finally, your customer must click on the Schedule appointment button. Now this visit will be in the appointment queue displayed in the seller’s app.
 
-![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
+![indeva2](//images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
 <div class=”alert alert-warning”>
 For now, you will have to confirm the appointment manually in the store. Your customer does not receive automatic messages.
@@ -58,13 +58,13 @@ For now, you will have to confirm the appointment manually in the store. Your cu
 
 Indeva Store’s app organizes the appointment queue for every physical store. Sellers and managers can use it to control the next appointments and view the history of already done visits. 
 
-![indeva3](https://images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
+![indeva3](//images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
 
 By selecting a specific appointment, the seller can see all appointment details: date and time of the visit, customer’s name, the message they sent, the number of people, and the customer’s phone number.
 
 If you want to contact your customer through this screen, you just have to click on the Open WhatsApp button. Then you will be redirected to a chat with that specific customer on the messaging app.
 
-![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
+![indeva4](//images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
 <div class=”alert alert-info”>
 You can install the app on multiple devices of the same store, but we recommend that your team use one app per store, not one per seller. 
@@ -114,7 +114,7 @@ The app for store’s sellers and managers is available for both Android and iOS
 
 After installing and opening the app, the seller must inform a 10-digit token to synchronize the device and log in.
 
-![indeva5](https://images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
+![indeva5](//images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
 
 To receive the token, please contact the Indeva support team via:
 - __Phone__: +55(21)3609-2830
diff --git a/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index 846cc5a4d..9794b53d3 100644
--- a/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -3,8 +3,8 @@ title: 'How to set up the "Responsible for pick up" field in SmartCheckout™ V6
 id: 2GsFnXUJxSOYEE6U2c4Syw
 status: PUBLISHED
 createdAt: 2018-11-09T12:18:14.596Z
-updatedAt: 2023-03-23T19:34:48.154Z
-publishedAt: 2023-03-23T19:34:48.154Z
+updatedAt: 2023-07-27T17:07:55.563Z
+publishedAt: 2023-07-27T17:07:55.563Z
 firstPublishedAt: 2018-11-26T14:43:00.552Z
 contentType: tutorial
 productTeam: Shopping
@@ -22,7 +22,7 @@ The <strong>Responsible for Pick Up</strong> field is only available for the <st
 The [pick up points](/tutorial/configurar-pontos-de-retirada-pickup-points?locale=en) give your customers one more option: instead of waiting for delivery, they can choose to go to a determined point and collect the item in person. By default, this action is linked to the user who made the purchase. However, you can enable the `Responsible for pick up` field at your store checkout so that your customer can appoint someone else to pick up the product.
 
 <div class="alert alert-warning">
-If you have the <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> app installed on your store, the CSS code described in the procedure below must only be entered via the app. Scripts inserted via the Admin interface (<b>Code > Files</b>) are not reproduced in stores that have the application installed.
+If you have the <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> app installed on your store, the CSS code described in the procedure below must only be entered via the app. Scripts inserted via the VTEX Admin interface (<b>Code > Files</b>) are not reproduced in stores that have the application installed.
 </div>
 
 To set this field up (which is disabled by default), follow the steps below:
@@ -36,7 +36,7 @@ To set this field up (which is disabled by default), follow the steps below:
 
 ```
 .vtex-omnishipping-1-x-container.shp-pickup-receiver{
-    display: block;
+    display: block; !import;
 }
 ```
 
diff --git a/docs/tutorials/en/how-to-set-up-the-zoom.md b/docs/tutorials/en/how-to-set-up-the-zoom.md
index 5d83691b6..f0435037a 100644
--- a/docs/tutorials/en/how-to-set-up-the-zoom.md
+++ b/docs/tutorials/en/how-to-set-up-the-zoom.md
@@ -19,7 +19,7 @@ A tool very commonly used in online stores is the zoom.
 
 It allows the customer to see a detailed image by passing the mouse over a photo of the product. Let us see how to set up and implement this function.
 
-![zoom-configurações](https://images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
+![zoom-configurações](//images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
 
 ## Setting up the CSS
 
@@ -35,7 +35,7 @@ Next we are going to send the saved CSS file to the server. To do this, click on
 
 Then find the CSS file you saved and send it to the server, clicking on **Localizar** ("Find") and then on **Salvar arquivo** ("Save File")
 
-![add-cms-.css ](https://images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
+![add-cms-.css ](//images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
 
 Your file will then be listed in the window, as shown above.
 
@@ -52,4 +52,4 @@ Now all you have to do is insert `zoom="on"` in the product tag, like this:
 
 You also have to set up the standard size for the zoom image. You can do this in **CMS** module > **Settings** > **File Types**. By default, this type of zoom image is set up with 1000×1000 pixels.
 
-![zoom-tiposdearquivos EN](https://images.ctfassets.net/alneenqid6w5/36CmHtsFyg0Ue2wuwYw8QG/de092d8f46a6e304744482144561747d/zoom_file_types.png)
+![zoom-tiposdearquivos EN](//images.ctfassets.net/alneenqid6w5/36CmHtsFyg0Ue2wuwYw8QG/de092d8f46a6e304744482144561747d/zoom_file_types.png)
diff --git a/docs/tutorials/en/how-to-set-up-visa-debit.md b/docs/tutorials/en/how-to-set-up-visa-debit.md
index 430540307..a15bc3d39 100644
--- a/docs/tutorials/en/how-to-set-up-visa-debit.md
+++ b/docs/tutorials/en/how-to-set-up-visa-debit.md
@@ -22,17 +22,17 @@ To set up payments made with Visa Debit at your store, in the VTEX Admin, go to
 First, you need to create a payment condition to enable Visa Debit in the Checkout.
 To do so, in **Settings** access the menu of **Payment conditions** options:
 
-![2.2](https://images.ctfassets.net/alneenqid6w5/3chvXc20lyciSmoSEgmqqk/51bbbbe0bb0de7e4a63b9e4ce239b4c7/2.2.png)
+![2.2](//images.ctfassets.net/alneenqid6w5/3chvXc20lyciSmoSEgmqqk/51bbbbe0bb0de7e4a63b9e4ce239b4c7/2.2.png)
 
 Select Visa Electron to create the payment condition:
 
-![4.2](https://images.ctfassets.net/alneenqid6w5/4e2znPWITSSKSmumCyaeG2/d655f5b0b44f4a48fb7236a6f8d46a1a/4.2.png)
+![4.2](//images.ctfassets.net/alneenqid6w5/4e2znPWITSSKSmumCyaeG2/d655f5b0b44f4a48fb7236a6f8d46a1a/4.2.png)
 
 ### Configure payment condition
 
 Select the desired affiliation to transact the payments; enable the payment condition; and, finally, save the changes: 
 
-![3.2](https://images.ctfassets.net/alneenqid6w5/7lW3rrIqbYcgsW8agM00qk/a8309e05cde5ac3f72ca724da4142e48/3.2.png)
+![3.2](//images.ctfassets.net/alneenqid6w5/7lW3rrIqbYcgsW8agM00qk/a8309e05cde5ac3f72ca724da4142e48/3.2.png)
 
 ### Display credit cards in Checkout
 
diff --git a/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md b/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md
index 282a4cf01..cde570400 100644
--- a/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md
+++ b/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: First Steps for the Seller'
 id: 6w1vBdRH2uuBGmUqgNQjwK
 status: PUBLISHED
 createdAt: 2021-01-26T15:08:22.524Z
-updatedAt: 2023-03-02T21:29:12.945Z
-publishedAt: 2023-03-02T21:29:12.945Z
+updatedAt: 2024-05-30T22:41:41.434Z
+publishedAt: 2024-05-30T22:41:41.434Z
 firstPublishedAt: 2021-09-15T20:50:27.452Z
 contentType: tutorial
 productTeam: Channels
@@ -53,6 +53,8 @@ Here are some details about the Seller Portal:
 
 ## Setting up your store
 
+<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+
 To start selling your products on the marketplace, you need to configure your store on the Seller Portal. This article explains the complete flow of this initial setup and indicates other documentation for you to access each step in more detail. The basic configuration of the Seller Portal includes the steps listed below.
 
 ### 1. Catalog
@@ -131,9 +133,18 @@ Whenever a product or variation is created on the Seller Portal, they are automa
 ### 7. Orders
 The moment the end customer pushes the Checkout button, an order is generated inside VTEX. This means that you will now be able to track the order flow through the Order Management module within your store's admin panel. That is, you can now know the details of each step throughout the order progress. To access the Orders module, go to the sidebar and click on Orders > All Orders / Transactions.
  To learn more, check out our article:  
- - [How Orders work in VTEX](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE)
+ - [How Orders work in VTEX](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE)  
+
+### 8. Creating and managing promotions
+
+The **Promotions** page on the Seller Portal allows sellers and marketplaces to create promotions and manage a complete list of registered promotions, simplifying promotion management.
+
+To learn more, check out the following articles:
+
+- [Seller Portal: Promotions](https://help.vtex.com/en/tutorial/seller-portal-promocoes--73LL7Ja0P4JbD77AH0jHwu)  
+- [Seller Portal: Creating a promotion](https://help.vtex.com/en/tutorial/seller-portal-criar-uma-promocao--kzNPEaiJE8EWkDzO9dbBI)  
 
-### 8. Supervising Offer Management
+### 9. Supervising Offer Management
 
 The _Offer Management_ module allows sellers to monitor their offers’ submission and synchronization on all channels integrated with the store. The main page features two components that display in real-time the status of the offers and their updates based on data from the marketplace and other VTEX modules. It’s where sellers can track all interactions of Catalog, Price, or Stock type in their offers in order to identify errors while sending and syncing offers.
 
@@ -143,7 +154,7 @@ To learn more, check out the following articles:
 - [Offer Management: offer details](https://help.vtex.com/en/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P)  
 - [Offer Management: interaction details](https://help.vtex.com/en/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf)
 
-### 9. Sales Performance Dashboard
+### 10. Sales Performance Dashboard
 The _Dashboards_ menu is a control panel that displays data for your unified commerce. The analyses presented here can inform decisions and help prioritize tasks for different professionals, from operations to commercial and marketing. The Dashboards include up-to-date data from all sales channels in which your store operates with VTEX, including key metrics that impact your store revenue.
 
 ## Optional configurations
diff --git a/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md b/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md
index ed9dc7920..8ce36b45d 100644
--- a/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md
+++ b/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md
@@ -3,8 +3,8 @@ title: 'Configuring Google Analytics 4 in VTEX stores'
 id: G2P0rmSrEiqCcmUMyUUwG
 status: PUBLISHED
 createdAt: 2017-07-30T22:53:46.285Z
-updatedAt: 2023-05-03T16:21:13.207Z
-publishedAt: 2023-05-03T16:21:13.207Z
+updatedAt: 2023-07-17T13:35:10.259Z
+publishedAt: 2023-07-17T13:35:10.259Z
 firstPublishedAt: 2017-07-30T23:24:21.394Z
 contentType: tutorial
 productTeam: Others
@@ -35,5 +35,5 @@ In both cases, save the Google Analytics property ID code in the `G-xxxxxxx` for
 
 Once you have configured the necessary settings in your Google Analytics account, you will need to change Google Tag Manager settings in the VTEX Admin to track your store events. To do so, follow the steps described in [Configuring Google Tag Manager](https://help.vtex.com/en/tutorial/integration-with-google-tag-manager).
 
-If your store uses [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), in addition to the setup, you will need to configure a new version of the Google Tag Manager app. For more information, see [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+If your store uses [VTEX IO - Store Framework](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), in addition to the setup, you will need to configure a new version of the Google Tag Manager app. For more information, see [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
diff --git a/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md b/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md
index e3a4fdbc9..c1b01645b 100644
--- a/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md
+++ b/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md
@@ -1,10 +1,10 @@
 ---
 title: "How to turn my store's website into a PWA"
 id: 3i8VmYeToAUGKgo2kKK6I2
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-03-19T18:20:25.794Z
-updatedAt: 2023-03-29T13:18:46.962Z
-publishedAt: 2023-03-29T13:18:46.962Z
+updatedAt: 2024-05-07T14:04:52.042Z
+publishedAt: 2023-07-10T14:28:55.813Z
 firstPublishedAt: 2018-03-20T14:54:55.189Z
 contentType: tutorial
 productTeam: Others
@@ -66,7 +66,7 @@ __To create the JSON, follow the step-by-step below:__
 
 __Your file should be imported into index.html, like this: __
 
-`<link rel="manifest" href="/files/manifest.json">`
+`<link rel="manifest" href="/arquivos/manifest.json">`
 
 After that, your web application could open a screen just like native apps.
 
@@ -84,7 +84,7 @@ __To create the script, follow the step-by-step below:__
 6. Program the functionality.
 7. To finish, click on __Save__
 
-Although the file is in `/files/service-worker.js`, it receives the `Service-Worker-Allowed` header with `/` value, which allows you to intercept requests from the site's root.
+Although the file is in `/arquivos/service-worker.js`, it receives the `Service-Worker-Allowed` header with `/` value, which allows you to intercept requests from the site's root.
 
 ### Third step
 
diff --git a/docs/tutorials/en/how-to-use-conditions-builder-app.md b/docs/tutorials/en/how-to-use-conditions-builder-app.md
index ef1c49fe1..ae6c6e722 100644
--- a/docs/tutorials/en/how-to-use-conditions-builder-app.md
+++ b/docs/tutorials/en/how-to-use-conditions-builder-app.md
@@ -36,12 +36,12 @@ After installing it, you can access it from the sidebar (installed apps section)
 4. (Optional) Write a short description. This is for internal control only and will not be visible to your customers.
 5. Click on "Start Building".
 
-![createCondition](https://images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
+![createCondition](//images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
 
 After you hit the "Create button", you are going to see a workspace with a block list on the left side of the screen.  
 Now you only have to drag the blocks onto the workspace and conect them, and finally creating your logic. 
 
-![creating](https://images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
+![creating](//images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
 
 
 ### Editing a condition
@@ -55,4 +55,4 @@ If you want a condition to no longer be applied, you can simply disable it inste
 - When toggle button is blue -> it is enabled
 - When toggle button is gray -> it is disabled
 
-![enableDisableEnglish](https://images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
+![enableDisableEnglish](//images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
diff --git a/docs/tutorials/en/how-to-use-the-index-report.md b/docs/tutorials/en/how-to-use-the-index-report.md
index c45eb8957..55e6e4e2f 100644
--- a/docs/tutorials/en/how-to-use-the-index-report.md
+++ b/docs/tutorials/en/how-to-use-the-index-report.md
@@ -1,10 +1,10 @@
 ---
 title: 'How to use the Index Report'
 id: 4ikVpMhwByyS8sysaeOIm4
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-07-04T13:10:40.431Z
-updatedAt: 2023-03-29T19:04:52.988Z
-publishedAt: 2023-03-29T19:02:27.075Z
+updatedAt: 2023-07-13T19:45:25.468Z
+publishedAt: 2023-07-13T19:45:25.468Z
 firstPublishedAt: 2017-07-04T19:16:21.471Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 5yDQmr18K4GgQAeGwq8USa
 
 The **Index Report** shows the indexing status of all products of the store. 
 
-![Indexingreport](https://images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
+![Indexingreport](//images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
 
 <div class="alert alert-info">
 <strong>Notice:</strong> For more information, access <a href="/en/tutorial/understanding-how-indexation-works">Understanding the operation of the indexation.</a>
diff --git a/docs/tutorials/en/how-to-use-the-meta-tags-control.md b/docs/tutorials/en/how-to-use-the-meta-tags-control.md
index 30dae2fa6..0e468fcf6 100644
--- a/docs/tutorials/en/how-to-use-the-meta-tags-control.md
+++ b/docs/tutorials/en/how-to-use-the-meta-tags-control.md
@@ -3,8 +3,8 @@ title: 'How to use the meta tags control'
 id: 2OPiSPubgcEqIikAWsCouk
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:38.270Z
-updatedAt: 2023-03-29T17:49:39.799Z
-publishedAt: 2023-03-29T17:49:39.799Z
+updatedAt: 2023-10-17T14:24:54.898Z
+publishedAt: 2023-10-17T14:24:54.898Z
 firstPublishedAt: 2019-01-24T22:06:45.424Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -55,5 +55,5 @@ See an example of meta tags inserted by the `<vtex:metaTags/>` control for the p
 ```
 
 <div class="alert alert-info">
-If you don't want to use the canonical tag (&lt;link rel="canonical"&gt;), you can disable it using a <a href="http://help.vtex.com/en/faq/control-to-disable-the-canonical-tag">specific control</a>.
+If you don't want to use the canonical tag (&lt;link rel="canonical"&gt;), you can disable it using a <a href="https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag">specific control</a>.
 </div>
diff --git a/docs/tutorials/en/how-to-use-the-search-result-control.md b/docs/tutorials/en/how-to-use-the-search-result-control.md
index 867ad38c5..657713e05 100644
--- a/docs/tutorials/en/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/en/how-to-use-the-search-result-control.md
@@ -46,14 +46,14 @@ See below the list of all attributes of the Search Result control:
 
 The code rendered by the Search Result control has the following structure by default:
 
-![searchResult1](https://images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
+![searchResult1](//images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
 
 And the corresponding elements that are rendered by the control in its non-customized version follow the pattern below:
 
-![searchResult2](https://images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
+![searchResult2](//images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
 
-![searchResult3](https://images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
+![searchResult3](//images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
 
-![searchResult4](https://images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
+![searchResult4](//images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
 
-![searchResult5](https://images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
+![searchResult5](//images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
diff --git a/docs/tutorials/en/how-to-use-the-shareable-cart-app.md b/docs/tutorials/en/how-to-use-the-shareable-cart-app.md
index 64dd94ff6..b66126c2f 100644
--- a/docs/tutorials/en/how-to-use-the-shareable-cart-app.md
+++ b/docs/tutorials/en/how-to-use-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 The [Shareable Cart](https://apps.vtex.com/vtex-social-selling/p) app allows sales assistants to select products for their customers and share the cart through channels such as WhatsApp, Facebook Messenger and email (Social Selling).
 
-![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 This article details the steps needed to use this feature: activate the app, choose products, add sales assistant code, share and create a new cart. Before you start, you need to [activate this feature in your store](https://help.vtex.com/en/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg).
 
@@ -31,25 +31,25 @@ You must activate the app in your first access, by accessing the store from the
 
 The cart sharing interface should appear on the screen, including some of the icons below. The options available depend on the configuration chosen by the store.
 
-![Screen Shot 2020-05-03 at 17.37.11](https://images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
+![Screen Shot 2020-05-03 at 17.37.11](//images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
 
 ## Choosing products
 
 Once the app is activated, it is not necessary to log in to start browsing and to select products. Just browse the store as usual, as if you were making an online purchase. After choosing all products for the customer, open the cart and follow the next steps in the cart sharing interface.
 
-![shareable-cart-chooseproducts](https://images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
+![shareable-cart-chooseproducts](//images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
 
 ## Adding a sales assistant code
 
-After selecting the products, click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> button to add your sales assistant code. Follow the store's instructions for filling out, as each store can choose different ways to identify sales assistants and add discounts to their carts.
+After selecting the products, click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> button to add your sales assistant code. Follow the store's instructions for filling out, as each store can choose different ways to identify sales assistants and add discounts to their carts.
 
-![shareable-cart-addcode](https://images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
+![shareable-cart-addcode](//images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
 
 ## Filling in personal data and address (optional)
 
 Depending on the customer's preference and your store’s guidelines, you can fill in the personal and shipping data for the order. Payment data must always be filled in by the customer.
 
-![shareable-cart-customerdetails](https://images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
+![shareable-cart-customerdetails](//images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
 
 <div class="alert alert-danger" role="alert"><strong>Never ask for payment details when sending the cart.</strong> Even if the customer insists, explain that they should fill in the payment details for security reasons.</div>
 
@@ -57,13 +57,13 @@ Depending on the customer's preference and your store’s guidelines, you can fi
 
 After adding your sales assistant code, click on the button corresponding to the desired option. See below the steps for each sharing option.
 
-![shareable-cart-sharecart](https://images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
+![shareable-cart-sharecart](//images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
 
 ### Whatsapp
 
 To share the cart via WhatsApp:
 
-1. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/34fTsrnmu0yZKKAU2Kq9iR/a9e805534e6bc81434026357529be8a3/image11.png" /> button
+1. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/34fTsrnmu0yZKKAU2Kq9iR/a9e805534e6bc81434026357529be8a3/image11.png" /> button
 2. Enter the **customer’s phone number** and click on OK
 3. (Optional) Customize the message on WhatsApp
 4. Send the message via WhatsApp
@@ -74,7 +74,7 @@ To share the cart via WhatsApp:
 
 To share the cart via Facebook Messenger:
 
-1. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/513wjcWdQzEydkFpsdm2Kb/e6ffef11d724e6fc1b66bf00504c81bb/image1.png" /> button
+1. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/513wjcWdQzEydkFpsdm2Kb/e6ffef11d724e6fc1b66bf00504c81bb/image1.png" /> button
 2. Enter the **client’s name** on Facebook Messenger
 3. Customize the message on Facebook Messenger
 4. Send the message via Facebook Messenger
@@ -88,7 +88,7 @@ You cannot share carts in Messenger with people you’re not friends with on Fac
 
 To share the cart via SMS: 
 
-1. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/aYyWKNKx0Fb4sSNT5yNJQ/34f7516d18c2f6efcb6c62c70ba8c04b/image7.png" /> button
+1. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/aYyWKNKx0Fb4sSNT5yNJQ/34f7516d18c2f6efcb6c62c70ba8c04b/image7.png" /> button
 2. Enter the **customer’s phone number** and click on OK
 3. (Optional) Customize the message on your SMS app
 4. Send the message via SMS
@@ -97,7 +97,7 @@ To share the cart via SMS:
 
 To share the cart via Link:
 
-1. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2GZp3YTXtUkh5KvG9BTFx6/0921f73c5c553a90ddd39056ab918202/image15.png" /> button
+1. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2GZp3YTXtUkh5KvG9BTFx6/0921f73c5c553a90ddd39056ab918202/image15.png" /> button
 2. Copy the link highlighted in **Link to share**
 3. (Optional) Write a custom message with the link
 4. Send the link to the customer on your contact channel
@@ -106,7 +106,7 @@ To share the cart via Link:
 
 To share the cart via Gmail:
 
-1. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/1rQ6MAeLHDZZ4vnX2p3Gyq/17bcbb4ebb94ac94a34dffb6c3515663/image14.png" /> button
+1. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/1rQ6MAeLHDZZ4vnX2p3Gyq/17bcbb4ebb94ac94a34dffb6c3515663/image14.png" /> button
 2. Enter the **customer's email address** and click on OK
 3. (Optional) Customize the message in Gmail
 4. Send the message via Gmail
@@ -115,7 +115,7 @@ To share the cart via Gmail:
 
 ### Email
 
-1. Click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/1B5ehv90NAceay9z6PPr7R/70fd43fed7c4aaec4e5a902c01255072/image8.png" /> button
+1. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/1B5ehv90NAceay9z6PPr7R/70fd43fed7c4aaec4e5a902c01255072/image8.png" /> button
 2. Enter the **customer's email address** and click on OK
 3. (Optional) Customize the message in your email app 
 4. Send the message via email
@@ -124,7 +124,7 @@ To share the cart via Gmail:
 
 ## Clearing the cart
 
-After finishing assisting a customer, click on the <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2fM6iuMfYNkTWlPA1vaSFM/c5c7c03611d846d609907d272b66684b/image5.png"/> button to empty your cart and choose new products for another customer.
+After finishing assisting a customer, click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2fM6iuMfYNkTWlPA1vaSFM/c5c7c03611d846d609907d272b66684b/image5.png"/> button to empty your cart and choose new products for another customer.
 
 <div class="alert alert-info" role="alert"><strong>Each salesperson can serve multiple customers!</strong> We recommend keeping the links you’ve shared in a spreadsheet or notepad. This way you keep your carts organized and can make changes whenever a customer requests.</div>
 
diff --git a/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md b/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md
index c3af6c7e0..c400e2804 100644
--- a/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md
+++ b/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md
@@ -17,6 +17,6 @@ subcategory:
 
 When a product is added to the cart, the amounts charged for each tax previously set up will be charged. To calculate the tax, it is necessary to fill in the customer’s data and purchase delivery data. Taxes will be always specified on the checkout page. The party responsible for the store will also have the information on Orders Management.
 
-![Screenshot 2](https://images.ctfassets.net/alneenqid6w5/6I5qA3ZzMWuC4gMeoi628W/a5a3d1a6fdae11ca486d1fef33157c6a/Screenshot_2.png)
+![Screenshot 2](//images.ctfassets.net/alneenqid6w5/6I5qA3ZzMWuC4gMeoi628W/a5a3d1a6fdae11ca486d1fef33157c6a/Screenshot_2.png)
 
 [Continue reading about TaxHub with the article about its API REST structure](/en/tutorial/how-is-taxhub-api-rest-structure)
diff --git a/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md b/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md
index f4ff904d6..a4a8c1409 100644
--- a/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md
+++ b/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md
@@ -21,7 +21,7 @@ On the main interface, you can find all transactions listed, from the most rece
 
 This listing indicates the current status, the start (date and time) of the transaction, the customer's name, the order's ID, the payment method used to close the order and the value transacted.
 
-![payment_en](https://images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/1ea0a2b0479a1d411935a9e873213252/payment_en.jpg)
+![payment_en](//images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/1ea0a2b0479a1d411935a9e873213252/payment_en.jpg)
 
 Each order registration will its data restricted to the payment conditions used for its closure. Authorization, transaction and NSU codes, among others, [are available within each record.](http://help.vtex.com/tutorial/como-visualizar-detalhes-do-pedido/ "are available within each record.")
 
diff --git a/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
index e143164c2..3bb392cf2 100644
--- a/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
@@ -37,7 +37,7 @@ After that a new section will be available and you can define through the fields
 
 It is possible to limit the availability of the template to a predetermined period of time by filling in the __From__ and __To__ fields as well as to define in which categories, products, brands and collections the chosen template will be applied.
 
-![template-condicionado-cms](https://images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
+![template-condicionado-cms](//images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
 
 After filling in all the needed fields, do not forget to save the changes made by clicking on __Save Layout__.
 
diff --git a/docs/tutorials/en/how-trade-policies-work.md b/docs/tutorials/en/how-trade-policies-work.md
index 43bde12fb..dda76bcbf 100644
--- a/docs/tutorials/en/how-trade-policies-work.md
+++ b/docs/tutorials/en/how-trade-policies-work.md
@@ -3,8 +3,8 @@ title: 'How trade policies work'
 id: 6Xef8PZiFm40kg2STrMkMV
 status: PUBLISHED
 createdAt: 2021-05-25T20:05:42.155Z
-updatedAt: 2022-12-08T14:39:11.093Z
-publishedAt: 2022-12-08T14:39:11.093Z
+updatedAt: 2024-06-20T22:52:38.544Z
+publishedAt: 2024-06-20T22:52:38.544Z
 firstPublishedAt: 2021-05-25T20:17:12.408Z
 contentType: tutorial
 productTeam: Others
@@ -33,7 +33,10 @@ See how different VTEX configurations relate to trade policies:
 
 To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), contact our Growth Operations team through Support by selecting **Commercial** and `Create a trade policy`.
 
-Additional trade policies to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores are free of charge.
+Additional trade policies to integrate with [certified connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores are free of charge.
+
+<div class=alert alert-warning>
+If the same trade policy is applied to a certified connector and a partner connector, there is no fee exemption.</div>
 
 ## Catalog
 You can restrict which products are available for certain trade policies when [adding new products](https://help.vtex.com/en/tutorial/cadastrando-produtos--tutorials_2567) to the catalog. In doing so, the catalog will be segmented according to different business strategies. These strategies can have products segmented by region, marketplace, or specific types of customers, such as employees. Learn more about how to configure your [catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ).
diff --git a/docs/tutorials/en/i-cant-import-the-price-table.md b/docs/tutorials/en/i-cant-import-the-price-table.md
new file mode 100644
index 000000000..169a44f8c
--- /dev/null
+++ b/docs/tutorials/en/i-cant-import-the-price-table.md
@@ -0,0 +1,67 @@
+---
+title: "I can't import the price table"
+id: bglrzs7gLKWf97q8qRdRm
+status: PUBLISHED
+createdAt: 2024-06-10T15:11:02.787Z
+updatedAt: 2024-06-10T19:44:11.614Z
+publishedAt: 2024-06-10T19:44:11.614Z
+firstPublishedAt: 2024-06-10T17:28:51.238Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: i-cant-import-the-price-table
+locale: en
+legacySlug: i-cant-import-the-price-table
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Keywords__: *price table, spreadsheet import, cells.*
+
+[Price tables, or price spreadsheets](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8), store SKU information which, when applied in specific contexts, such as trade policies, promotions, or customer clusters, allows you to calculate the product prices in a VTEX store. For more information, see [Base price](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) and [Fixed price](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy). 
+
+<div class ="alert alert-warning">
+  You cannot import a <b>calculated price</b> table into the VTEX Admin. The <b>Export</b> function is available for this table only for the merchant to check the final price for each product.
+</div>
+
+After [importing a price table](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D), error messages may display for certain SKUs, as shown in the examples below:
+
+- `"The resource you are looking for cannot be found: Price not found"`
+- `"Error occurred while converting spreadsheet: Object reference not set to an instance of an object."`
+- `"Import Fixed Table Error: Invalid headers - SKU ID"`
+
+If you encounter error messages, incorrect price values, or other difficulties importing a table, check out the possible solutions below.
+
+## Solution
+
+To address any issues when importing a price table, consider the following solutions:
+
+### Templates
+
+Tables created by customers or customized after being exported from the VTEX Admin can generate integration errors when imported.
+
+To avoid this scenario, use only the available templates (base price or fixed price) and do not apply any customizations. Learn more in [Exporting prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#exporting-prices).
+
+### Data input
+
+Errors may occur while completing the table, such as entering the product ID where the SKU ID should be or [adjusting the price of a SKU](https://help.vtex.com/en/tutorial/sku-price-change--tutorials_95#price-change-rule) by more than 70% upward or more than 30% downward relative to its current price. This can cause inconsistencies during import.
+
+Make sure that all fields in your table are properly populated based on the guidelines in the following articles:
+
+- [Planilha de preço-base](https://help.vtex.com/en/tutorial/table-of-base-prices--4Jox8TeQ5feqAn78TZ0DNA)
+- [Planilha de preço fixo](https://help.vtex.com/en/tutorial/filling-out-an-import-spreadsheets-fixed-price-fields--50RFoH3ruV97FJgeBUCURh)
+
+<div class ="alert alert-warning">
+  Before importing the table into the VTEX Admin, make sure that it does not contain columns with error information (<b>Error Code</b> and <b>Error Message</b>) or any filters applied to the cells. Importing a table under these conditions may cause errors in the data import process.
+</div>
+
+Example of a table with filters applied and __Error Code__ and __Error Message__ fields:
+
+![Price spreadsheet](//images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/a88f798c1962786dadfd35573453242e/Price_spreadsheet.PNG)
+
+#### File size
+
+Price tables should not exceed a maximum size limit of 1 megabyte (MB). If your current file is larger, divide the information into files smaller than 1 megabyte (MB).
+
+<div class ="alert alert-warning">
+  All data for a specific SKU must be in a single table. You cannot enter information for the same SKU in different tables.
+</div>
diff --git a/docs/tutorials/en/i-cant-receive-emails-from-vtex.md b/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
new file mode 100644
index 000000000..80b31ad29
--- /dev/null
+++ b/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
@@ -0,0 +1,98 @@
+---
+title: "I can't receive emails from VTEX"
+id: 4M2uVZdtrJzgyAySuZ4OLg
+status: PUBLISHED
+createdAt: 2024-05-28T17:21:01.400Z
+updatedAt: 2024-06-10T18:28:15.898Z
+publishedAt: 2024-06-10T18:28:15.898Z
+firstPublishedAt: 2024-05-29T13:14:04.884Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: i-cant-receive-emails-from-vtex
+locale: en
+legacySlug: i-cant-receive-emails-from-vtex
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Keywords__: *message center, store settings, email templates, data export, error logs, spreadsheet import, authentication token.*
+
+Through the [Message Center](https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84), VTEX allows merchants to customize email templates to be sent to users. These emails can be used to convey the following information:
+- In-store authentication token
+-	Notification for creating and paying orders
+- Data export confirmation
+- Spreadsheet import error logs
+
+If your store's emails aren't being appropriately forwarded, preventing relevant information from being sent to your customers, see below the possible solutions to identify the source of this problem.
+
+## Solution
+
+To fix any disruption in sending emails from VTEX, see the following solutions:
+
+- [Confirm sender](#confirming-sender)
+- [Configure a mail server](#configuring-a-mail-server)
+- [Configure order and payment notifications](#configuring-order-and-payment-notifications)
+- [Remove email from the AWS suppression list](#aws-suppression-list)
+
+### Confirming sender
+
+If your store has a customized sender in addition to the standard __VTEX-DEFAULT__ sender, run a test message following the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Email Templates > Senders__.
+2. In the box with your sender's name, click `Test`. After a few seconds, an email confirmation message will display.
+3. Check if an email from VTEX has been forwarded to the email address of the user logged into the Admin.
+4. If you haven't received the email from VTEX, proceed to the next solution.
+
+### Configuring a mail server
+
+On VTEX, you can use the native mail server or [configure an external SMTP server](https://help.vtex.com/en/tutorial/customizing-the-vtex-smtp--tutorials_2733). If you are using an external SMTP server, see the scenarios below.
+
+#### Configuring SMTP in the VTEX Admin
+
+1. In the VTEX Admin, go to __Store Settings > Email Templates > Senders__.
+2. Click the box with the name of your sender.
+3. Under __SMTP Data__, make sure that all the data is correct.
+4. Click `Save`.
+5. In the box with the name of your sender, click `Test`. After a few seconds, an email confirmation message will be displayed.
+6. Check if an email from VTEX has been forwarded to the email address of the user logged into the Admin.
+
+After the test, if the message from VTEX has not been sent to the email address of the user logged into the Admin, we recommend using the VTEX sender (__VTEX-DEFAULT__) as the default and test sending the message again. If you still haven't received the email from VTEX, proceed to the next solution.
+
+#### Configuring SPF (Sender Policy Framework)
+
+Check if the external SMTP server is configured according to the [SPF system](https://help.vtex.com/en/tutorial/best-practices-on-spf--42t0lkl2VyC6Yewc4wA6wI), which prevents unauthorized servers from sending emails on behalf of a specific domain. You can configure [SPF](https://developers.vtex.com/docs/guides/setting-up-the-spf) and [DKIM](https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails) (DomainKeys Identified Mail) on the server if necessary.
+
+<div class ="alert alert-warning">
+Check your spam folder to ensure that VTEX emails are not being sent there. This may be due to internal mail server rules.
+</div>
+
+### Configuring order and payment notifications
+
+VTEX sends emails to users immediately after an order is created or a payment is made. Follow the steps below to check your payment notification settings:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__.
+2. Click the __Settings__ tab.
+3. Make sure your email is in the field corresponding to the My VTEX email option. If you want, enter a secondary email in the Other email field and test sending the message as described in the [Confirming sender](#confirm-sender) section.
+4. Check if an email from VTEX has been forwarded to the email address of the user logged into the Admin.
+5. If you haven't received the email from VTEX, proceed to the next solution.
+
+### AWS suppression list
+
+Amazon (AWS) has an email platform called Amazon Simple Email Service ([Amazon SES](https://aws.amazon.com/pt/ses/)). Among the many features of this service, there is an email address suppression list containing recipients who may have shown suspicious behavior that affected an AWS customer.
+
+Generally, an email can be added to the AWS suppression list and removed after approximately 12 hours. During this period, emails sent by VTEX will not be received by the email address added to the list.
+
+<div class ="alert alert-warning">
+AWS manages the suppression list, and VTEX has no control over the addresses on and off the list.
+</div>
+
+If you suspect AWS has blocked your email, wait 12 hours and try resending an email to the blocked address.
+
+You can also check whether the email is registered as a copy in any of the store's transactional email templates. To check this, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Email Templates > Templates__.
+2. Click the desired template card.
+3. Check if the email does not appear in the template's __Cc:__ or __Bcc:__ fields. If it does, remove it and click `Save`.
+4. Do this for each store's template card and test sending an email to the desired address.
+
+![copia_email_en](//images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/60df1d00ff23e4a1847d76a09e4dd44b/copia_email_en.png)
diff --git a/docs/tutorials/en/i-cant-update-the-ean-of-my-skus-via-api.md b/docs/tutorials/en/i-cant-update-the-ean-of-my-skus-via-api.md
new file mode 100644
index 000000000..0389112ee
--- /dev/null
+++ b/docs/tutorials/en/i-cant-update-the-ean-of-my-skus-via-api.md
@@ -0,0 +1,50 @@
+---
+title: "I can't update the EAN of my SKUs via API"
+id: 1gHfGo3TpSTHqb5ZNzwq3m
+status: PUBLISHED
+createdAt: 2024-06-18T16:50:42.770Z
+updatedAt: 2024-06-18T17:29:20.394Z
+publishedAt: 2024-06-18T17:29:20.394Z
+firstPublishedAt: 2024-06-18T17:28:22.909Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: i-cant-update-the-ean-of-my-skus-via-api
+locale: en
+legacySlug: i-cant-update-the-ean-of-my-skus-via-api
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Product tags:** Catalog
+
+**Keywords:** SKU, product, EAN, catalog
+
+When trying to update the EAN (European Article Number), which contains the barcode information for a SKU, you may face issues with catalog synchronization between the VTEX Admin and API. This can impact inventory management and customer experience.
+
+## Solution
+
+To solve this issue, consider [deleting the SKU EAN](#deleting-the-sku-ean) and then [adding a new EAN](#step-1-add-a-new-ean-to-the-sku). 
+
+### Deleting the SKU EAN
+
+To update the current SKU EAN, you must first delete all the EAN values associated with the SKU.
+
+- [Delete SKU EAN](https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/stockkeepingunit/-skuId-/ean/-ean-): Use the endpoint to delete a specific EAN.
+- [Delete all SKU EAN values](https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/stockkeepingunit/-skuId-/ean): Use the endpoint to delete all the EANs associated with the SKU.
+
+#### Step 1 - Add a new EAN to the SKU
+
+Only after all previous EANs have been deleted can you add a new EAN to the SKU. To do this, use the [Create SKU EAN](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/ean/-ean-) endpoint to create the new EAN value.
+
+#### Step 2 - Check whether the SKU EAN has been updated
+
+After adding the new EAN, use the [Get SKU by EAN](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/sku/stockkeepingunitbyean/-ean-) endpoint to confirm it has been updated. The new EAN values will be displayed in the `AlternateIdValues` array.
+
+```json
+"AlternateIdValues":
+[
+"8781",
+"878181"
+]
+```
+
diff --git a/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
new file mode 100644
index 000000000..390c5d0af
--- /dev/null
+++ b/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
@@ -0,0 +1,241 @@
+---
+title: "I can't view the product in the search results"
+id: 2Ry55Fh6JW8v7oKBiB2pH3
+status: PUBLISHED
+createdAt: 2024-07-24T16:39:50.379Z
+updatedAt: 2024-07-25T15:47:00.673Z
+publishedAt: 2024-07-25T15:47:00.673Z
+firstPublishedAt: 2024-07-24T18:55:15.925Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: i-cant-view-the-product-in-the-search-results
+locale: en
+legacySlug: i-cant-view-the-product-in-the-search-results
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Keywords__: *product, search, catalog, intelligent search, apps, rewriter, graphql, vtex io, redirect.*
+
+When the user searches in a VTEX store using [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG), the desired product may not be found, even if the search term is included in the item's information.
+
+Example scenario: When searching the store's website for products containing the term "Pendleton," the search results return 6 products. However, when we access the VTEX Admin (__Storefront > Intelligent Search > Explained Search__) and enter the same term, 9 products are displayed.
+
+![Filter_1](//images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/568f6f3868b13d54ed4335b4574ac434/Filter_1.png)
+
+![Filter_2](//images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/06017d321b1996515da01c11ea53403c/Filter_2.png)
+
+This behavior can occur due to the following reasons:
+
+1. Incorrect product registration in the Catalog.
+
+2. The term used is not in one of the product's searchable fields. Learn more about [Search behavior configuration](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/23mytRDsEduqLO0Lo7yufy#standard-search-behavior) and [Search configuration](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx).
+
+3. Internal route redirecting the search result to a brand page.
+
+## Solutions
+
+To enable the searched products to be displayed correctly in the site's search results, consider the following solutions:
+
+- [Verify product registration fields](#verifying-product-registration-fields)
+- [Change search filters in Rewriter](#changing-search-filters-in-rewriter)
+- [Removing internal search route in Rewriter](#removing-internal-search-route-in-rewriter)
+
+### Verifying product registration fields
+
+A missing product in a search result may come from incomplete fields during the [product registration](https://help.vtex.com/en/tutorial/product-registration-fields--4dYXWIK3zyS8IceKkQseke). Follow the steps below to check the __Brand, Show on site__, and __Show when out of stock__ fields:
+
+<blockquote><ui>1. In the Admin VTEX, go to </b>Catalog > All Products</b>.</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Stores using the <b>Produtos and SKUS (Beta)</b> page should check the product registration fields by going to <b>Catalog > Products and SKUs</b> in the VTEX Admin. Learn more about <a href="https://help.vtex.com/en/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">Produtos and SKUS (Beta)</a>.
+</div></blockquote>
+
+<blockquote><ui>2. Find the product you want and click <b>Edit product</b>.</ui>
+
+<blockquote><ui>3. In the <b>Brand</b> field, confirm if the information is correct. If necessary, add the brand corresponding to the product. You can only add brands that have already been <a href="https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/7lEGOSpAlQJCs5eUc5XFmR">created in the store</a>.</ui>
+
+<blockquote><ui>4. Confirm if the <b>Show on site</b> option is checked.</ui>
+
+<blockquote><ui>5. Confirm if the <b>Show when out of stock</b> option is checked.</ui>
+
+<blockquote><ui>6. Click <i>Save</i>.</ui>
+
+<blockquote><ui>7. Go to the store's website, search for the desired term, and ensure that the products displayed in the search results are the same as the ones available on the <b>Explained Search</b> page under Intelligent Search (<b>Storefront > Intelligent Search > Explained Search</b>).</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  If the search term is included in the product's name or description, but the product belongs to a different brand than the term specified in the search, proceed with the other steps to solve the problem.
+</div></blockquote>
+
+### Changing search filters in Rewriter
+
+Another reason a product may not be displayed in search results is the [Rewriter](https://developers.vtex.com/docs/apps/vtex.rewriter) app's default behavior when displaying products.
+
+If a term is listed in Rewriter as a brand, [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4uSFqyJVCMVMIvVrtz3lxZ) will understand that it should only be displayed when it is included in a brand name.
+
+To remove the restriction on searching by *brand* and allow products to be found also by terms in the name or description (*full text*), follow the steps below:
+
+<blockquote><ui>1. In the VTEX Admin, go to <b>Storefront > Intelligent Search > Explained Search</b> enter the desired term, and see how many products are returned in the search.</ui>
+
+<blockquote><ui>2. Configure the <a href="https://developers.vtex.com/docs/apps/vtex.rewriter">Rewriter</a> app. If this app is not installed in your store, go to the <a href="https://help.vtex.com/en/tracks/extensions-hub--AW7klkYMh557y5IUOgzco/2LDRvGujYsumxi7IlE7CEJ">App Store</a> and install it.</ui>
+
+<blockquote><ui>3. Access the <a href="https://developers.vtex.com/docs/guides/graphql-ide#graphql-basics">GraphQL IDE</a> in <b>Store Settings > Storefront > GraphQL IDE</b>.</ui>
+
+<blockquote><ui>4. Under <b>Choose an app</b>, click the Rewriter app option (<b>vtex.rewriter@{app-version-number}</b>).</ui>
+
+![Graphql_ide_en](//images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/6e0774e72b9a6e4a6b85a4c47986fe84/Graphql_ide_en.png)
+
+<blockquote><ui>5. In the query input field (below <b>GraphiQL</b>), enter the details of the <i>saveInternal</i> mutation function.<ui>
+
+```
+mutation saverInternal($route: InternalInput!) {
+internal {
+ save(route: $route) {
+   from
+   declarer
+   type
+   id
+   query
+   endDate
+   binding
+   resolveAs
+   origin
+   disableSitemapEntry
+ }
+}
+}
+```
+
+<blockquote><ui>6. In <b>Query Variables</b>, enter the route details. You must replace the <i>Pendleton</i> value with the desired term and the <i>id</i> field value with the product ID.<ui>
+
+```
+{
+"route": {
+ "from": "/Pendleton",
+ "declarer": "vtex.store@2.x",
+ "type": "fullText",
+ "id": "2000307",
+ "query": {
+     "map": "ft"
+ },
+   "origin": "user-canonical"
+ }
+}
+```
+
+<blockquote><ui><div class ="alert alert-warning">
+  The value <i>ft</i> (full text) instead of <i>b</i> (brand) in the <i>map</i> parameter indicates that products with the term <i>Pendleton</i> in the name or description will also be displayed in the search.
+</div></blockquote>
+
+<blockquote><ui>7. Click the GraphiQL IDE arrow (next to <b>GraphiQL</b>) to update the search filter. The display of the following message in the GraphiQL IDE results field will confirm the new default search filter for the term.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "save": {
+        "from": "/Pendleton",
+        "declarer": "vtex.store@2.x",
+        "type": "fullText",
+        "id": "2000307",
+        "query": {
+          "map": "ft"
+        },
+        "endDate": null,
+        "binding": "0be568e5-52f5-44f0-9308-3ea701a9f847",
+        "resolveAs": null,
+        "origin": "user-canonical",
+        "disableSitemapEntry": null
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>8. Go to the store's website, search for the desired term, and ensure that the products displayed in the search results are the same as the ones available on the <b>Explained Search</b> page under Intelligent Search (<b>Storefront > Intelligent Search > Explained Search</b>).</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  If the search term is associated with a brand that no longer exists on your site, you will need to remove the internal search route within the Rewriter app, as described in the solution below</a>.
+</div></blockquote>
+
+### Removing internal search route in Rewriter
+
+[Internal search routes](https://developers.vtex.com/docs/guides/vtex-io-documentation-routes#routes-in-rewriter) in the [Rewriter](https://developers.vtex.com/docs/apps/vtex.rewriter) app can prevent a product from being displayed in the search if it is associated with a brand that is no longer available in the store.
+
+To display products using the search terms only in the name or description, you need to delete the search route.
+
+To remove an internal search route for the term, follow the steps below:
+
+<blockquote><ui>1. In the VTEX Admin, go to <a href="https://developers.vtex.com/docs/guides/graphql-ide#graphql-basics">GraphQL IDE</a> in <b>Store Settings > Storefront > GraphQL IDE</b>.</ui>
+
+<blockquote><ui>2. Under <b>Choose an app</b>, click the Rewriter app option (<b>vtex.rewriter@{app-version-number}</b>).</ui>
+
+<blockquote><ui>3. In the query input field (below <b>GraphiQL</b>), enter the data for the <i>internal get</i> function, replacingo <i>pendleton</i> with the desired term.</ui> 
+
+```
+{
+  internal {
+    get(path: "/Pendleton") {
+      from
+      resolveAs
+      type
+    }
+  }
+}
+```
+
+<blockquote><ui>4. Click the GraphiQL IDE arrow (next to <b>GraphiQL</b>) and check the results field to see if the internal route is described as a <i>brand</i>.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "get": {
+        "from": "/Pendleton",
+        "resolveAs": "/Pendleton",
+        "type": "brand"
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>5. In the query input field (below <b>GraphiQL</b>), enter the data for the <i>mutation</i> function, replacing <i>pendleton</i> with the desired term.</ui> 
+
+```
+mutation {
+  internal {
+    delete(path: "/Pendleton"){
+      type
+    }
+  }
+}
+```
+
+<blockquote><ui>6. Click the GraphiQL IDE arrow (next to <b>GraphiQL</b>) to remove the internal filter route by <i>brand</i> and confirm that the information below appears in the GraphiQL IDE results field.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "delete": {
+        "type": "brand"
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>7. Repeat steps 3 and 4 to confirm that the internal redirection route from term to brand has been deleted. This can be indicated by the <i>"get": null</i> result in the GraphiQL IDE results field.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "get": null
+    }
+  }
+}
+```
+
+<blockquote><ui>8. Go to the store's website, search for the desired term, and ensure that the products displayed in the search results are the same as the ones available on the <b>Explained Search</b> page under Intelligent Search (<b>Storefront > Intelligent Search > Explained Search</b>).</ui>
diff --git a/docs/tutorials/en/image-compression.md b/docs/tutorials/en/image-compression.md
new file mode 100644
index 000000000..5178f89e3
--- /dev/null
+++ b/docs/tutorials/en/image-compression.md
@@ -0,0 +1,63 @@
+---
+title: 'Image compression'
+id: 4klbgpsPksq44KcwqKeye8
+status: PUBLISHED
+createdAt: 2017-08-17T22:59:59.002Z
+updatedAt: 2024-04-15T14:59:26.688Z
+publishedAt: 2024-04-15T14:59:26.688Z
+firstPublishedAt: 2017-08-17T23:30:18.772Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: image-compression
+locale: en
+legacySlug: how-the-automatic-compacting-of-images-works
+subcategory: 2g6LxtasS4iSeGEqeYUuGW
+---
+
+Image compression is a process that reduces the size of image files, optimizing them for the web and ensuring that images load quickly as a user browses a website.
+
+This process aims to boost the speed and performance of the store, which significantly affects user experience, [SEO](https://developers.google.com/search/blog/2010/04/using-site-speed-in-web-search-ranking), and conversion rates.
+
+There are two types of image compression, as described in the table below:
+
+| Compression type | Description |
+| - | - |
+| Lossy | Reduces the image size and quality to retain the most significant information without keeping all the pixels. |
+| Lossless | Rewrites an image file without removing any information. While it maintains the original quality, this type is less effective than lossy compression in reducing file size. |
+
+On VTEX, files are stored in their original format but are compressed in real time during store browsing.
+
+We automatically convert images to the [WebP](https://developers.google.com/speed/webp/) format when there is a size advantage — resulting in smaller images — regardless of whether the original file is in **PNG** or **JPG/JPEG format**.
+
+Using WebP can lead to a reduction in page load time by 1 to 2 seconds, depending on the layout. Below is an explanation of how image optimization functions with each format.
+
+<div class="alert alert-info">
+  <p>Browsers not yet <a href="https://developers.google.com/speed/webp/faq#which_web_browsers_natively_support_webp">compatible with the WebP format</a> and services, such as integrations and marketplaces, always receive unconverted images in any format. GIF files are not converted to WebP.</p>
+</div>
+
+## PNG
+
+For images in PNG format, which is ideal for solid colors, detailed graphics, and high contrast, conversion to WebP uses lossless compression to minimize quality loss. Lossless WebP images can be up to 26% smaller than PNG images.
+
+Additionally, PNG images are optimized with [pngquant](https://pngquant.org/), which maintains the format while reducing the image size by up to 70%.
+
+Finally, VTEX delivers the smallest file between the lossless WebP and the optimized PNG, as illustrated in the diagram below.
+
+![png-image-compression](//images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/c3f60b063fbfa38ed197d44d6e7da014/png-image-compression.PNG)
+
+## JPG / JPEG
+
+For images in the **JPG/JPEG** formats, which are ideal for photos, the conversion to WebP uses lossy compression. This approach might lead to some quality loss but ensures an optimized file size. Lossy WebP images are 25% to 34% smaller than similar images with an equivalent [SSIM](https://ece.uwaterloo.ca/~z70wang/research/ssim/) quality index.
+
+VTEX delivers the image with the smallest file size to the customer, choosing between the original and the one converted to lossless WebP, as illustrated in the diagram below.
+
+![webp-image-compression](//images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/0a711ec8fb9135cbddeada05f9191d95/webp-image-compression.PNG)
+
+## Related articles
+
+* [Best practices for using images in the Catalog](https://help.vtex.com/en/tutorial/best-practices-for-using-images-in-the-catalog--738K2yfq5U86kUI2k4AQIk)
+* [Add image to product description](https://help.vtex.com/en/tutorial/add-image-to-product-description--2hQGTAAiyUSoISGSyOK8Y4)
+* [Importing images from a spreadsheet](https://help.vtex.com/en/tutorial/importing-images-from-a-spreadsheet--tutorials_262)
+* [Updating the image of an SKU](https://help.vtex.com/en/tutorial/how-to-update-the-image-of-an-sku--5PMb54FnvUuWOq2qGyAosu)
+* [Reusing images with Image Widget](https://help.vtex.com/en/tutorial/image-widget--7pRSVI2xXpQUzjUZj0m4ov)
diff --git a/docs/tutorials/en/image-widget.md b/docs/tutorials/en/image-widget.md
index 6cbacf87e..a4ff143d0 100644
--- a/docs/tutorials/en/image-widget.md
+++ b/docs/tutorials/en/image-widget.md
@@ -3,8 +3,8 @@ title: 'Reusing images with Image Widget'
 id: 7pRSVI2xXpQUzjUZj0m4ov
 status: PUBLISHED
 createdAt: 2021-06-30T18:06:46.531Z
-updatedAt: 2023-03-28T13:24:31.101Z
-publishedAt: 2023-03-28T13:24:31.101Z
+updatedAt: 2024-03-27T14:07:43.190Z
+publishedAt: 2024-03-27T14:07:43.190Z
 firstPublishedAt: 2021-07-02T21:20:16.653Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -42,12 +42,12 @@ Now that you know how to access the Image Widget, see what you can do next:
 
 After [accessing the Image Widget](#accessing-image-widget), you can add images to it:
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px">
+<div class="alert alert-warning">
 When adding new images in the Image Widget modal using a <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">development workspace</a>,  the performed settings will be saved directly in the master workspace. In other words, they will immediately be reflected in your store's modal.
 </div>
 <br>
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px">
+<div class="alert alert-warning">
   The maximum file size supported by Image Widget is 4 MB. 
 </div>
 
@@ -67,7 +67,7 @@ Furthermore, If you [added images](#adding-an-image) to your modal, now you can
 
 With the modal open, click on `more actions` in an image thumbnail.
 
-| Options     | Description    |
+| Options    | Description    |
 | ---------- | ---------- |
 | __Preview__ | Opens a new page to show a preview of the picture.|
 | __Copy URL__| Allows you to copy the image’s URL and use it in other sections of your store.|
@@ -84,6 +84,6 @@ Go to the block in which you want to replace a picture and:
 ### Removing an image
 To remove a picture in the desired block, click on `More actions` in an image thumbnail and select __remove__. After this, the image will no longer be visible in the block.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px; margin-bottom: 10px">
+<div class="alert alert-warning">
   When you remove an image, it does not mean it was deleted from the repository. To do that, check the section <a href="#features-within-image-widget">Features within Image Widget</a>.
 </div>
diff --git a/docs/tutorials/en/import-customer-data-brazil.md b/docs/tutorials/en/import-customer-data-brazil.md
index f064b25d9..f01c73b93 100644
--- a/docs/tutorials/en/import-customer-data-brazil.md
+++ b/docs/tutorials/en/import-customer-data-brazil.md
@@ -3,8 +3,8 @@ title: 'Import customer data'
 id: 2zWYVOyj0sISYQmeUwCsI0
 status: PUBLISHED
 createdAt: 2017-06-22T20:55:49.745Z
-updatedAt: 2022-10-17T20:32:21.800Z
-publishedAt: 2022-10-17T20:32:21.800Z
+updatedAt: 2023-10-09T20:34:05.165Z
+publishedAt: 2023-10-09T20:34:05.165Z
 firstPublishedAt: 2017-06-27T14:40:29.106Z
 contentType: tutorial
 productTeam: Master Data
@@ -19,12 +19,12 @@ The import of customer data must be made in Master Data. To find out more about
 
 <div class="alert alert-danger">
   <p>This article refers to Master Data v1 fields specifically for stores in <strong>Brazil</strong>. You should check for valid values for different countries.</p>
-  <p>You can also see the guide on <a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2">how to import customer information programattically using the Master Data v2 API</a>.</p>
+  <p>You can also see the guide on <a href="https://developers.vtex.com/docs/guides/import-customer-data">how to import customer information programattically using the Master Data v2 API</a>.</p>
 </div>
 
 The checkout works with CL (customer) and AD (address) entities data.
 
-Please note that, for checkout to display the customer's data in the chart based on the e-mail, you must ensure that all the following data is correctly registered in Master Data.
+Please note that, for checkout to display the customer's data in the chart based on the email, you must ensure that all the following data is correctly registered in Master Data.
 
 The tables below include the data and the formats required for the import.  
 
@@ -32,14 +32,14 @@ The tables below include the data and the formats required for the import.
 
 | Field Name | Description | Format |
 |---------------|-----------|---------|
-| firstName | name | text |
-| lastName | surname | text |
-| e-mail | customer e-mail | e-mail |
+| firstName | Customer name | Text |
+| lastName | Customer surname | Text |
+| email | Customer email | Email |
 | documentType | Document Type | "cpf" for Brazil |
 | document | Document (CPF) | 11 digits, without mask |
-| homePhone | Telephone | in "+5511999999999" format, +55 being the country code, followed by the area code and the phone number |
+| homePhone | Telephone | In "+5511999999999" format, +55 being the country code, followed by the area code and the phone number. |
 
-The ‘id’ field is generated by the system right after the import, and it will be used as “userld” when importing the address.
+The `id` field is generated by the system right after the import, and it will be used as “userld” when importing the address.
 
 Customers’ ‘userId’ field should be left blank, since it will not be used now. It will be generated by the system after the first purchase made by the customer.
 
@@ -47,11 +47,11 @@ For clients that are **legal entities**, the document and documentType fields ar
 
 | Field Name | Description | Format |
 |---------------|-----------|---------|
-| isCorporate | defines whether the customer is a legal entity | should be "true" |
-| corporateName | corporate name | text |
-| tradeName | trade name | text |
-| stateRegistration | state registration | should be "Exempt" or text/alphanumeric |
-| corporateDocument | CNPJ | 14 digits, without input mask |
+| isCorporate | Defines whether the customer is a legal entity | Should be "true" |
+| corporateName | Corporate name | Text |
+| tradeName | Trade name | Text |
+| stateRegistration | State registration | Should be "Exempt" or text/alphanumeric value |
+| corporateDocumet | CNPJ | 14 digits, without input mask |
 
 ### Address
 
@@ -60,20 +60,20 @@ Customers must have at least one address.
 | Field Name | Description | Format |
 |---------------|-----------|---------|
 | id | Address ID | blank |
-| userId | Customer ID | ‘id’ field, generated after customers import |
-| addressName | address name | text/alphanumeric |
-| addressType | address type | must be "residential" or "commercial" |
-| country | country | "BRA" for Brazil |
-| state | state (UF) | two letters |
-| city | city | text |
-| neighborhood | district | text |
-| postalCode | Postal Code | 8 or 9 digits, with hyphen |
-| street | address | text |
-| number | number | alphanumeric |
-| complement | Complement and reference | text |
-| reference | field not used | blank |
-| receiverName | addressee | text |
+| userId | Customer ID | `id` field, generated after customers import. |
+| addressName | Address name | Text or alphanumeric value |
+| addressType | Address type | Must be "residential" or "commercial" |
+| country | Country code | "BRA" for Brazil. |
+| state | State | Two letters |
+| city | City | Text |
+| neighborhood | District | Text |
+| postalCode | Postal Code | 8 or 9 digits, with hyphen. |
+| street | Address | Text |
+| number | Number | Alphanumeric |
+| complement | Complement and reference | Text |
+| reference | Deprecated field | Blank |
+| receiverName | Addressee | Text |
 
 ---
 
-If data (customer or address) is not consistent, including a valid CPF (a Brazilian ID number unique for each Brazilian citizen)/CNPJ (Brazilian company registration number), the checkout will not fill in the customer's data, and he/she will make the purchase as a new user.
+If data (customer or address) is not consistent, including a valid CPF (a Brazilian ID number unique for each Brazilian citizen) or CNPJ (Brazilian company registration number), the checkout will not fill in the customer's data, and he/she will make the purchase as a new user.
diff --git a/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md b/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md
index 6bbfe466e..444de1696 100644
--- a/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md
+++ b/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md
@@ -3,8 +3,8 @@ title: 'Importing and exporting an inventory spreadsheet'
 id: tutorials_2034
 status: PUBLISHED
 createdAt: 2017-04-27T21:55:43.488Z
-updatedAt: 2023-03-29T14:51:46.368Z
-publishedAt: 2023-03-29T14:51:46.368Z
+updatedAt: 2023-07-24T15:03:49.647Z
+publishedAt: 2023-07-24T15:03:49.647Z
 firstPublishedAt: 2017-04-27T23:03:50.695Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -31,7 +31,7 @@ If you have more than one existing inventory, this same action also allows you t
 
 1. In the VTEX Admin, go to **Shipping > Shipping Strategy**, or type *Shipping Strategy* in the search bar at the top of the page.    
 2. Click on **Warehouses** tab.  
-3. Click on `more_vert` button next to *Create warehouse*.  
+3. Click on :` button next to *Create warehouse*.  
 4. Click on the **Import items** option.  
 5. Choose a file from your computer and drag it into the box.  
 6. Click on **Import**. 
diff --git a/docs/tutorials/en/importing-data-into-master-data.md b/docs/tutorials/en/importing-data-into-master-data.md
index 7505e4aa2..1ddbac22a 100644
--- a/docs/tutorials/en/importing-data-into-master-data.md
+++ b/docs/tutorials/en/importing-data-into-master-data.md
@@ -3,8 +3,8 @@ title: 'How to import data into Master Data'
 id: tutorials_1135
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:12.437Z
-updatedAt: 2023-03-28T23:29:25.337Z
-publishedAt: 2023-03-28T23:29:25.337Z
+updatedAt: 2023-06-15T19:48:45.566Z
+publishedAt: 2023-06-15T19:48:45.566Z
 firstPublishedAt: 2017-04-27T23:03:43.488Z
 contentType: tutorial
 productTeam: Master Data
@@ -42,10 +42,10 @@ Keep the same format of the worksheet (xls) for the import to be successful.
 </div>
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. Click on the **Aplicações** tab.
-3. Click on the **Modo de Importação** button.
+2. Click on the **Applications** tab.
+3. Click on the **Import** button.
 4. Select the data entity to be entered or updated (here, you must enter the data entity of the form containing the records that you intend to include or update).
 5. Select the file.
-6. Click on the **Importar** button at the bottom of the screen.
+6. Click on the **Import** button at the bottom of the screen.
 
 ![Importando](//images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
diff --git a/docs/tutorials/en/importing-images-from-a-spreadsheet.md b/docs/tutorials/en/importing-images-from-a-spreadsheet.md
index 6914c1364..d6cdc4d53 100644
--- a/docs/tutorials/en/importing-images-from-a-spreadsheet.md
+++ b/docs/tutorials/en/importing-images-from-a-spreadsheet.md
@@ -3,8 +3,8 @@ title: 'Importing images from a spreadsheet'
 id: tutorials_262
 status: PUBLISHED
 createdAt: 2017-04-27T22:11:24.581Z
-updatedAt: 2023-03-29T17:46:11.384Z
-publishedAt: 2023-03-29T17:46:11.384Z
+updatedAt: 2024-03-04T22:25:58.399Z
+publishedAt: 2024-03-04T22:25:58.399Z
 firstPublishedAt: 2017-04-27T23:03:11.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -57,11 +57,11 @@ Below, you'll find information on how to fill in each field in the image import
 <p>This is a mandatory field. No special characters, periods or accents are admitted on the image name.</p>
 </div>
 
-It is the URL of the image to be linked to the SKU, which must be public and hosted on an FTP server where the image link originates. The URL must start with the HTTPS protocol identifier (`https://`) and end with the file extension (`.jpg`, `.png` or `.gif`). Example: `https://www.exemploimagem.com.br/imagem03/teste01/exemplo15.jpg`.
+It is the URL of the image to be linked to the SKU, which must be public and hosted on an FTP server where the image link originates. The URL must start with the HTTP protocol identifier (`http://`) and end with the file extension (`.jpg`, `.png` or `.gif`). Example: `http://www.imageexample.com.br/imagem03/teste01/exemplo15.jpg`.
 
-To avoid any possible mistakes, you should verify the image URL you entered in the template: it should go from `https://` to the file extension. Otherwise, the system will not be able to access the URL and the image will not be imported.
+To avoid any possible mistakes, you should verify the image URL you entered in the template: it should go from `http://` to the file extension. Otherwise, the system will not be able to access the URL and the image will not be imported.
 
-You don't need to have your own FTP server to forward the image URLs. You may host that data on free websites and external or internal FTP servers, if they use the HTTPS protocol.
+You don't need to have your own FTP server to forward the image URLs. You may host that data on free websites and external or internal FTP servers, if they use the HTTP protocol.
 
 In addition, you can use an external provider to authenticate the URL.
 
diff --git a/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md b/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md
index 665b4f99c..e7d866f9d 100644
--- a/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md
+++ b/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md
@@ -21,7 +21,7 @@ The PLPs are correlated as each product links back to a category page — Appare
 
 To improve the SEO performance of PLPs, you must allow web crawlers such as Google to notice this connection between PLPs. This way,  these crawlers will be able to browse different pages and access other products they show. 
 
-![Show more button](https://images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/ec462ab024d44052f0eba3ddd360c00d/bt-show-more.png)
+![Show more button](//images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/ec462ab024d44052f0eba3ddd360c00d/bt-show-more.png)
 
 See the section below on how to improve the SEO performance of PLPs [using the Site Editor](#using-the-site-editor).
 
@@ -39,7 +39,7 @@ To improve the SEO performance of PLPs via Site Editor, you have to configure th
 4. Click on __Fetch more.__
 5. On __Button behavior,__ select the option __Link to page - Improves SEO, may change how the button looks.__
 
-![bt-config-en](https://images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/4ac3a699c734b39ebc5bfae46c27696a/bt-config-en.gif)
+![bt-config-en](//images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/4ac3a699c734b39ebc5bfae46c27696a/bt-config-en.gif)
 
 6. Click on `SAVE`.
 7. To configure the __Fetch previous__ item, expand the __Search Result Flexible Layout__ block.
diff --git a/docs/tutorials/en/indexes-in-master-data.md b/docs/tutorials/en/indexes-in-master-data.md
new file mode 100644
index 000000000..e92bbde33
--- /dev/null
+++ b/docs/tutorials/en/indexes-in-master-data.md
@@ -0,0 +1,88 @@
+---
+title: 'Indexes in Master Data'
+id: tutorials_785
+status: PUBLISHED
+createdAt: 2017-04-27T21:58:03.173Z
+updatedAt: 2024-07-17T13:57:12.010Z
+publishedAt: 2024-07-17T13:57:12.010Z
+firstPublishedAt: 2017-04-27T23:03:42.760Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 1malnhMX0vPThsaJaZMYm2
+slug: indexes-in-master-data
+locale: en
+legacySlug: setting-up-an-index-on-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+An index in Master Data is a reference to one or more fields used to optimize queries on a data entity. Using indexes allows you to search for records more quickly.
+
+To illustrate, imagine the index of a book, which lists the themes contained in the book and the page number for each theme. To search, instead of having to go through all the pages of the book to find the result you want, you can access the index and go straight to the theme you want. Likewise, the index in Master Data provides a more efficient method for finding documents.
+
+## Configuring indexes
+
+Follow the instructions below to define one or more fields as indexes in Master Data v1:
+
+1. In the VTEX Admin, go to **Store Settings > Storefront > Master Data**.
+2. Click the gear icon <i class="fas fa-cog"></i> in the application where you want to add the index.
+3. Click **Data structure**.
+4. Click the **Index** tab.
+5. Click `Add`.
+6. Complete the following fields:
+
+    * **Name:** Name of the index.
+    * **Unique values:** Option to block new records with repeated values for the index(es) created. See the section [Restricting values per document (alternative key)](#restricting-values-per-document-alternative-key) for more details.
+    * **Data entity:** Name of the data entity containing the fields to be configured as indexes.
+    * **Fields:** Name of one or more fields that will be configured as indexes. If you add more than one field name, separate them with a comma. Example: `firstName,document`.
+7. Click `Save`.
+
+## Use cases
+
+Learn more about the main scenarios for using indexes in Master Data in the following sections.
+
+### Queries of up to a thousand documents
+
+The use of indexes is recommended for searches that return results of up to a thousand documents. If searches for an index frequently return more than a thousand documents, you can obtain better search performance by indexing the field, i.e., [configuring it as a filter in the data entity](https://help.vtex.com/en/tutorial/filtrando-dados-no-master-data--tutorials_778).
+
+### Restricting values per document (alternative key)
+
+The index configuration allows you to block one or more fields to prevent records with repeated values. These fields act as alternative keys, providing alternative values to identify a record.
+
+The alternative key is configured via the **Unique values** field in [Index Settings](#configuring-indexes). Its behavior varies depending on the number of fields included in the index. The following sections show the alternative key's behavior in each case.
+
+#### Only one field in the index
+
+If only one field is configured as an index, the alternative key will not allow a value that has already been entered in that field to be entered again.
+
+For example, the **Customer** table has two columns: **ID** and **Name**. To make searching easier, the **Name** field (`firstName`) can be configured as an index and marked as **Unique values**, as illustrated below:
+
+![indices-1-en](//images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/73cc5f6e47530f8a25b428b858c3d0df/indices-1-en.png)
+
+As a result, it will not be possible to enter a name that has already been entered in **Customer**:
+
+![indices-2-en](//images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/8caded1ca96fdf9c0bcd93a5afc12d27/indices-2-en.png)
+
+In the example above, as there is already a record with the **Name** equal to **Mary**, you cannot add another one with the same value.
+
+<div class="alert alert-warning">
+  <p>Use the <strong>Unique values</strong> option with caution. If a value that you want to allow to be repeated is configured as unique, the system will block duplicate records, preventing another one from being entered.</p>
+</div>
+
+#### Multiple fields in the index
+
+If there is more than one field in the index, the alternative key will prevent a set of values from being repeated in the selected fields.
+
+For example, imagine that the **Customer** entity has three fields: **ID**, **Name** and **Document**. In the index configuration, under **Fields**, you enter Name (`firstName`) and Document (`document`), as shown below:
+
+![indices-3-en](//images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/6dfd99a8e88c85ea424e31bafd163572/indices-3-en.png)
+
+In this case, the **Name** value can be repeated, or the **Document** value can be repeated, but the combination of the two values cannot be repeated. In other words, there can be no record that repeats the same pair of values (such as identical **Name** and **Document**).
+
+![indices-4-en](//images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/f56a0b860946eec272c8973d57eb6368/indices-4-en.png)
+
+In the example above, there is already a record with the **Name** as **Mary**. You can include another record with the same **Name** as long as the **Document** value is different.
+
+<div class="alert alert-warning">
+  <p>If the same combination of values repeats, the record will not be saved. Use the <strong>Unique values</strong> option only when you are certain that a set of values will not be repeated in different records.
+</p>
+</div>
diff --git a/docs/tutorials/en/indexing-history-beta.md b/docs/tutorials/en/indexing-history-beta.md
index a40828f76..e9bb12d8e 100644
--- a/docs/tutorials/en/indexing-history-beta.md
+++ b/docs/tutorials/en/indexing-history-beta.md
@@ -21,12 +21,12 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 
 **Indexing history** is the page that monitors the synchronization status of all products in the Catalog sent to Intelligent Search. It provides a broad view of the indexing progress of your store.
 
-![Histórico da Indexação 1 - EN](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
 
 The **Indexing status** section displays the following information:
 
 * **Average indexing time:** The average time for products to be indexed, from the time the system received the change notification to the in-store update. Indexing time performance is measured by a green (healthy) or red (bad) dot. 
-![Historico Indexação 2 - EN](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
+![Historico Indexação 2 - EN](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
 * **Products in store:** Quantity of products with up-to-date information currently displayed in the store.
 * **Indexing status share:** The percentage of products in each indexing step. Status breakdown performance is measured by a green (healthy) or red (bad) dot. The steps displayed are:
     * **Updated:** Latest product update has been entered in the store.
@@ -35,17 +35,17 @@ The **Indexing status** section displays the following information:
 
 You can filter the list of indexed products for a custom view. It is important to note that the average indexing time and status breakdown will be recalculated from the products filtered. 
 
-To filter the list of indexed products, click on `Filter` <img src="https://images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
+To filter the list of indexed products, click on `Filter` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
 
-![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
 
 If you filter by `Status` you can select which status you want to filter by, which could be `Updated`, `Updating`, `Error`.
 
-![Historico indexação 4 - EN](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
+![Historico indexação 4 - EN](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
 
 If you filter by `Indexing time` you can select whether the time interval `Is greater than`, `Is equal to or greater than`, `Is shorter than` or `Is equal to or less than` a defined time.
 
-![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
 
 After defining the filter, click `Apply` to activate it. 
 
@@ -55,17 +55,17 @@ You can also filter the products displayed in the listing by **ID**, **Last upda
 
 If you want more information about the indexing of a specific product, you can click on the product row in the table to access a page that contains more details, as illustrated below.
 
-![Historico indexação 6 - EN](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
+![Historico indexação 6 - EN](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
 
 In addition to the information displayed in the product list, you can also see:
 
 * **Indexing time:** Is an entry of how long the product indexing lasted using the `hh:mm:ss` format`.
 * **Indexing timeline:** Shows a log of every status change with date and time. You can view more details of each step by clicking the <i class="fa-solid fa-chevron-down"></i> icon.
 
-![Historico indexação 7 - EN](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
+![Historico indexação 7 - EN](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
 
 It is possible to manually reindex a product without having to update the entry. To reindex a product, click <i class="fa-solid fa-arrows-rotate"></i> `Reindex`. Only products in **Updated** status can be indexed.
 
 You can access the product **Indexing history**, a list with the date and time of each update performed. Therefore, it is possible to have a record of every change that was made to the product. To access it, click <i class="fa-solid fa-arrows-rotate"></i> `History`. 
 
-![Histórico da Indexação 8 - EN](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
+![Histórico da Indexação 8 - EN](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
diff --git a/docs/tutorials/en/indexing-history.md b/docs/tutorials/en/indexing-history.md
new file mode 100644
index 000000000..c6c8f4768
--- /dev/null
+++ b/docs/tutorials/en/indexing-history.md
@@ -0,0 +1,67 @@
+---
+title: 'Indexing History'
+id: 55SRQ79PXk5lTURF54DRyJ
+status: PUBLISHED
+createdAt: 2024-06-27T16:51:28.631Z
+updatedAt: 2024-06-27T16:52:45.090Z
+publishedAt: 2024-06-27T16:52:45.090Z
+firstPublishedAt: 2024-06-27T16:52:45.090Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: indexing-history
+locale: en
+legacySlug: indexing-history
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+**Indexing history** is the page that monitors the synchronization status of all products in the Catalog sent to Intelligent Search. It provides a broad view of the indexing progress of your store.
+
+![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+
+The **Indexing status** section displays the following information:
+
+* **Average indexing time:** The average time for products to be indexed, from the time the system received the change notification to the in-store update. Indexing time performance is measured by a green (healthy) or red (bad) dot. 
+![Historico Indexação 2 - EN](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
+* **Products in store:** Quantity of products with up-to-date information currently displayed in the store.
+* **Indexing status share:** The percentage of products in each indexing step. Status breakdown performance is measured by a green (healthy) or red (bad) dot. The steps displayed are:
+    * **Updated:** Latest product update has been entered in the store.
+    * **Updating:** New product information is being prepared and entered into the store.
+    * **Error**: Means that an error occurred during indexing. There was a problem adding the product and it cannot be indexed. If it is a new product, it will not be available in the store.
+
+You can filter the list of indexed products for a custom view. It is important to note that the average indexing time and status breakdown will be recalculated from the products filtered. 
+
+To filter the list of indexed products, click on `Filter` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
+
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
+
+If you filter by `Status` you can select which status you want to filter by, which could be `Updated`, `Updating`, `Error`.
+
+![Historico indexação 4 - EN](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
+
+If you filter by `Indexing time` you can select whether the time interval `Is greater than`, `Is equal to or greater than`, `Is shorter than` or `Is equal to or less than` a defined time.
+
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
+
+After defining the filter, click `Apply` to activate it. 
+
+To add a new filter, click <i class="fa-solid fa-plus"></i> `Add filter`. To remove the configured filters, click `Clear filters`.
+
+You can also filter the products displayed in the listing by **ID**, **Last update** and **Status**, by clicking on the desired column. To find a specific product in the list, you can search by ID in the search bar.
+
+If you want more information about the indexing of a specific product, you can click on the product row in the table to access a page that contains more details, as illustrated below.
+
+![Historico indexação 6 - EN](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
+
+In addition to the information displayed in the product list, you can also see:
+
+* **Indexing time:** Is an entry of how long the product indexing lasted using the `hh:mm:ss` format`.
+* **Indexing timeline:** Shows a log of every status change with date and time. You can view more details of each step by clicking the <i class="fa-solid fa-chevron-down"></i> icon.
+
+![Historico indexação 7 - EN](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
+
+It is possible to manually reindex a product without having to update the entry. To reindex a product, click <i class="fa-solid fa-arrows-rotate"></i> `Reindex`. Only products in **Updated** status can be indexed.
+
+You can access the product **Indexing history**, a list with the date and time of each update performed. Therefore, it is possible to have a record of every change that was made to the product. To access it, click <i class="fa-solid fa-arrows-rotate"></i> `History`. 
+
+![Histórico da Indexação 8 - EN](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
diff --git a/docs/tutorials/en/indexing.md b/docs/tutorials/en/indexing.md
new file mode 100644
index 000000000..3bcaf78e6
--- /dev/null
+++ b/docs/tutorials/en/indexing.md
@@ -0,0 +1,28 @@
+---
+title: 'Indexing'
+id: 7J6tepFgD3wohCGEP2PqDB
+status: PUBLISHED
+createdAt: 2024-06-27T16:49:13.712Z
+updatedAt: 2024-06-27T16:50:18.969Z
+publishedAt: 2024-06-27T16:50:18.969Z
+firstPublishedAt: 2024-06-27T16:50:18.969Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: indexing
+locale: en
+legacySlug: indexing
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Indexing is the syncing process between store and search catalogs. This feature allows you to keep your content up to date with continuous updates of the product index. It also performs data processing to be used in the search.
+
+Initially, it syncs all the products from your VTEX catalog. After that, data changes — such as product name and status — are updated in real time by the search indexer.
+
+In this sync process, the system queues up the information that has been updated to add it to the search catalog. Once all changes have been indexed, they will be available on the website.
+
+The indexing process is safe and has a retry mechanism — if an item is not indexed on the first attempt, the system makes subsequent attempts until it is successfully completed.
+
+Indexing is fundamental to analyze, process, and organize data as best as possible to improve your search results.
+
+Check [Indexing History](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) for more information on how to monitor the indexing process.
diff --git a/docs/tutorials/en/information-about-chile-custom-payments.md b/docs/tutorials/en/information-about-chile-custom-payments.md
index b58902f68..72d6c3b97 100644
--- a/docs/tutorials/en/information-about-chile-custom-payments.md
+++ b/docs/tutorials/en/information-about-chile-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Information about Chile custom payments'
 id: 1cqQ4JInfcOGUwW2aMOoEK
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.205Z
-updatedAt: 2019-12-31T15:26:29.898Z
-publishedAt: 2019-12-31T15:26:29.898Z
+updatedAt: 2024-03-19T12:13:49.935Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:11:20.233Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/information-about-colombia-custom-payments.md b/docs/tutorials/en/information-about-colombia-custom-payments.md
index 1e66cd268..87d86b313 100644
--- a/docs/tutorials/en/information-about-colombia-custom-payments.md
+++ b/docs/tutorials/en/information-about-colombia-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Information about Colombia custom payments'
 id: 3tcvqc6LBSKOqMWCumwyaq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:36.914Z
-updatedAt: 2019-12-31T15:22:34.694Z
-publishedAt: 2019-12-31T15:22:34.694Z
+updatedAt: 2024-03-19T12:16:11.844Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:11:29.228Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/information-about-uruguay-custom-payments.md b/docs/tutorials/en/information-about-uruguay-custom-payments.md
index f1f7e3b75..678ce5b61 100644
--- a/docs/tutorials/en/information-about-uruguay-custom-payments.md
+++ b/docs/tutorials/en/information-about-uruguay-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Information about Uruguay custom payments'
 id: 4cXMr3C5rqIkUkMWgCcWeU
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:36.816Z
-updatedAt: 2019-12-31T15:20:18.360Z
-publishedAt: 2019-12-31T15:20:18.360Z
+updatedAt: 2024-03-19T12:18:07.525Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:06.326Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/inserting-images-into-let-me-know-email.md b/docs/tutorials/en/inserting-images-into-let-me-know-email.md
index d6dd7914a..378015b7c 100644
--- a/docs/tutorials/en/inserting-images-into-let-me-know-email.md
+++ b/docs/tutorials/en/inserting-images-into-let-me-know-email.md
@@ -32,7 +32,7 @@ Here's how to do so:
 5. Go to the __HTML__ box.  
 6. Enter the __code__ of the images you want to insert. 
 
-  ![Let me know - EN](https:https://images.ctfassets.net/alneenqid6w5/57IqVpUH7SZKkH8sRtlfSf/7911794b89b0b35d0d59a6ece5c05c30/57IqVpUH7SZKkH8sRtlfSf_Imagem_Message_Center_EN.jpg)
+  ![Let me know - EN](https://images.ctfassets.net/alneenqid6w5/57IqVpUH7SZKkH8sRtlfSf/7911794b89b0b35d0d59a6ece5c05c30/57IqVpUH7SZKkH8sRtlfSf_Imagem_Message_Center_EN.jpg)
 
 7. Click `Save`.  
 
diff --git a/docs/tutorials/en/installing-my-orders-through-the-extension-store.md b/docs/tutorials/en/installing-my-orders-through-the-extension-store.md
index e3be5f950..c8b4f1c2a 100644
--- a/docs/tutorials/en/installing-my-orders-through-the-extension-store.md
+++ b/docs/tutorials/en/installing-my-orders-through-the-extension-store.md
@@ -19,7 +19,7 @@ Following the evolution of VTEX platform, the viewpart of __My Orders__ is now a
 
 In order to perform the installation, you need to access the [VTEX App Store.](https://extensions.vtex.com/)
 
-![app store1 EN](https://images.ctfassets.net/alneenqid6w5/4TNMg7DSxWco4KCyO6yaYU/941ee734d6e7a6ee93f85a6d59d8324c/app_store1_EN.png)
+![app store1 EN](//images.ctfassets.net/alneenqid6w5/4TNMg7DSxWco4KCyO6yaYU/941ee734d6e7a6ee93f85a6d59d8324c/app_store1_EN.png)
 
 __After installing the app, you already have the following updates:__
 
@@ -29,7 +29,7 @@ __After installing the app, you already have the following updates:__
 - Trace information for multiple items.
 - Minor Bug Fix.
 
-![app store2 EN](https://images.ctfassets.net/alneenqid6w5/uWM5x8qG5ia6okQ0kgIak/1caf4e8275bb8e8514b7073396553b6a/app_store2_EN.png)
+![app store2 EN](//images.ctfassets.net/alneenqid6w5/uWM5x8qG5ia6okQ0kgIak/1caf4e8275bb8e8514b7073396553b6a/app_store2_EN.png)
 
 In addition, with the new app you can perform version tests and update it whenever a new version is available, receiving continuous improvements and updates of new features.
 
@@ -42,4 +42,4 @@ To test the customizations on your page, you may work on a different workspace w
 5. Ready! Now you will see how your page will behave before you upload it.
 6. To move My Orders to the production environment (where your customers can actually use it), you must publish the change. To do that, just click on the __Publish__ button.
 
-![app store3 EN](https://images.ctfassets.net/alneenqid6w5/Dhrybc8B7qCwacYMmAwcC/7970fef7fc718f082683ad218603a829/app_store3_EN.png)
+![app store3 EN](//images.ctfassets.net/alneenqid6w5/Dhrybc8B7qCwacYMmAwcC/7970fef7fc718f082683ad218603a829/app_store3_EN.png)
diff --git a/docs/tutorials/en/integrating-with-enjoei.md b/docs/tutorials/en/integrating-with-enjoei.md
index 6aeafa2bc..9019f3c27 100644
--- a/docs/tutorials/en/integrating-with-enjoei.md
+++ b/docs/tutorials/en/integrating-with-enjoei.md
@@ -3,8 +3,8 @@ title: 'Integrating with Enjoei'
 id: 3mV9uhw1AdqFol8K2tfwly
 status: PUBLISHED
 createdAt: 2021-11-05T19:27:31.160Z
-updatedAt: 2023-03-29T15:54:34.785Z
-publishedAt: 2023-03-29T15:54:34.785Z
+updatedAt: 2024-02-19T20:17:35.239Z
+publishedAt: 2024-02-19T20:17:35.239Z
 firstPublishedAt: 2021-11-05T20:49:41.372Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/integrating-with-madeiramadeira.md b/docs/tutorials/en/integrating-with-madeiramadeira.md
index 4ece7c8c1..7c9b2debc 100644
--- a/docs/tutorials/en/integrating-with-madeiramadeira.md
+++ b/docs/tutorials/en/integrating-with-madeiramadeira.md
@@ -3,8 +3,8 @@ title: 'Integrating with MadeiraMadeira'
 id: J4QCENKiz4urYNfaMuE0i
 status: PUBLISHED
 createdAt: 2021-11-05T21:04:22.888Z
-updatedAt: 2023-06-07T21:22:36.808Z
-publishedAt: 2023-06-07T21:22:36.808Z
+updatedAt: 2024-02-19T20:17:16.961Z
+publishedAt: 2024-02-19T20:17:16.961Z
 firstPublishedAt: 2021-11-05T21:34:03.556Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/integrating-with-renner-and-camicado.md b/docs/tutorials/en/integrating-with-renner-and-camicado.md
index d73467af6..bdd005612 100644
--- a/docs/tutorials/en/integrating-with-renner-and-camicado.md
+++ b/docs/tutorials/en/integrating-with-renner-and-camicado.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integrating with Renner and Camicado'
 id: 5qf2wloosKlmIB8o2AitnT
-status: CHANGED
+status: PUBLISHED
 createdAt: 2021-07-02T19:25:31.689Z
-updatedAt: 2022-12-15T20:40:16.364Z
-publishedAt: 2022-12-15T20:38:45.121Z
+updatedAt: 2023-08-25T18:50:55.909Z
+publishedAt: 2023-08-25T18:50:55.909Z
 firstPublishedAt: 2021-07-02T21:07:36.096Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/integration-guide-for-erps-full-catalog.md b/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
index 07db17751..8df50aa70 100644
--- a/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
+++ b/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
@@ -19,7 +19,7 @@ subcategory: 5fKgQZhrCw88ACy6Su6GUc
 
 This document is intended to assist on the catalog integration (department, category, brand, images, fields, field values, SKUs activation) of the ERP for a store hosted in VTEX. In this type of integration most of the store's management is ERP.
 
-![ERParchitecture](https://images.ctfassets.net/alneenqid6w5/zUnuBAtUoo6CQcmCwkoEs/91110c5c16af13c0b9c4fa56f1a8d70b/ERParchitecture.png)
+![ERParchitecture](//images.ctfassets.net/alneenqid6w5/zUnuBAtUoo6CQcmCwkoEs/91110c5c16af13c0b9c4fa56f1a8d70b/ERParchitecture.png)
 
 In this scenario of complete flow, most of product data and SKUs are handled through the ERP (brand, images, category, activation, etc). The handling of specification fields in this model can be done through REST API, but the best practice would be for the VTEX admin.
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md b/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md
index ab50a78df..f4d4c42ec 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integration guide for marketplaces - Seller non VTEX'
 id: yMji0ow0rQuYgQsg26Kus
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-10-14T21:55:39.633Z
-updatedAt: 2021-08-10T18:51:48.080Z
-publishedAt: 2021-08-10T18:51:48.080Z
+updatedAt: 2023-08-18T19:03:38.625Z
+publishedAt: 
 firstPublishedAt: 2017-10-14T22:00:36.965Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/integration-with-google-tag-manager.md b/docs/tutorials/en/integration-with-google-tag-manager.md
index b3ab3f4dd..95e2ec095 100644
--- a/docs/tutorials/en/integration-with-google-tag-manager.md
+++ b/docs/tutorials/en/integration-with-google-tag-manager.md
@@ -3,8 +3,8 @@ title: 'Configuring Google Tag Manager'
 id: frequentlyAskedQuestions_616
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:56.745Z
-updatedAt: 2023-05-12T15:09:43.299Z
-publishedAt: 2023-05-12T15:09:43.299Z
+updatedAt: 2023-07-17T13:33:10.627Z
+publishedAt: 2023-07-17T13:33:10.627Z
 firstPublishedAt: 2019-01-24T22:13:48.493Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
 <div class="alert alert-warning">
-If your store is built with <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, you also need to install the Google Tag Manager pixel app to integrate all pages. See how to do this in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">app documentation</a>.
+If your store is built with <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">Store Framework</a>, you also need to install the Google Tag Manager pixel app to integrate all pages. See how to do this in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">app documentation</a>.
 </div>
 
 Google Tag Manager is a tag management system created by Google to manage JavaScript and HTML tags used for website tracking and analytics.
@@ -48,7 +48,7 @@ After this, you have to set up the store identification code from Tag Manager on
 4. In the __Google Tag Manager__ field, enter the store identification code in `GTM-XXXX` format, as shown in the image below.
 5. Click `Save`. 
 
-![Google Tag Manager](https://images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/c16814591d79d4165f6c6c7954c0c48a/Google_Tag_Manager_-_EN.PNG)
+![Google Tag Manager](//images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/c16814591d79d4165f6c6c7954c0c48a/Google_Tag_Manager_-_EN.PNG)
 
 To check available events (triggers) and variables on the pages, which will be used in the tags, you can use the Google Tag Manager preview mode. For more information, check the [Google Tag Manager documentation](https://support.google.com/tagmanager/answer/6107056?hl=pt-BR).
 
@@ -58,7 +58,7 @@ You can use the Facebook pixel app among your store's Google Tag Manager to trac
 
 ## VTEX IO: Installing the Google Tag Manager pixel app
 
-If your store uses [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), in addition to the setup, you need to install a new version of the Google Tag Manager app. For more information, see [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+If your store uses [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), in addition to the setup, you need to install a new version of the Google Tag Manager app. For more information, see [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
 This step is not required for stores using the [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
 
diff --git a/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
index abf1131ba..f1f0b5094 100644
--- a/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
@@ -1,10 +1,10 @@
 ---
-title: 'Intelligent Search synonym suggestions (Beta)'
+title: 'Intelligent Synonyms'
 id: 18A9JTCPrMsHWpFntNoKEr
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-06-01T20:18:10.087Z
-updatedAt: 2023-06-01T20:44:40.993Z
-publishedAt: 2023-06-01T20:44:40.993Z
+updatedAt: 2024-04-02T13:08:36.724Z
+publishedAt: 
 firstPublishedAt: 2023-06-01T20:33:35.148Z
 contentType: tutorial
 productTeam: Others
@@ -15,22 +15,27 @@ legacySlug: intelligent-search-synonym-suggestions-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
+
 <div class="alert alert-info">
-  <p>This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>.</p>
-  <p>For selected customers, the functionality is available for free use in the VTEX Admin during its Beta period, or until decided by VTEX. Extra fees may apply in the future.</p>
+  <p>This feature is available for accounts that have a minimum number of sessions and orders for the Artificial Intelligence model to be trained. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>. Extra fees may apply in the future.</p>
 </div>
 
 The [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) allows you to add words, or similar sentences, as synonyms for customer search terms, increasing the chance of successful searches.
 
-The **Synonyms** page in the VTEX Admin now provides intelligent suggestions of terms for approval and manual configuration of synonyms. The platform leverages artificial intelligence to suggest synonyms based on customer search behavior in your store.
+With the Intelligent Synonyms feature, the **Synonyms** page in the VTEX Admin provides intelligent recommendations of terms, as well as manual configuration of synonyms. The platform leverages artificial intelligence to suggest synonyms based on customer search behavior in your store.
 
 VTEX Intelligent Search achieves this by counting how many times in the last 30 days  customers have searched for a term that returned few or no search results and replaced the original term with an alternative one.
 
-> _Example:_ Suppose five customers typed `facial soap` in their search but later changed it to `face soap`. The system records this behavior, and the most rewritten terms will be displayed as suggested synonyms.
+Example: Suppose five customers typed `facial soap` in their search but later changed it to `face soap`. The system records this behavior, and the most rewritten terms will be displayed as suggested synonyms.
+
+The suggestions are displayed in two categories in the list of synonyms, as shown below:
+
+* **New suggestions:** Suggestions generated by the platform that have not yet been viewed.
+* **Saved suggestions:** Suggestions saved for later, as described in step 5 of the [Reviewing suggestions](#revisar-sugestoes) section.
 
-You can review the suggestions and choose one of three actions: decline, edit, or approve. See the steps in the next section.
+![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
 
-![syn-sug-en](https://images.ctfassets.net/alneenqid6w5/3bDrkDw6O6d8mHvvBKwWGm/7bb4dc43cc0ef0c5cf439d57f1ef7d1b/syn-sug-en.png)
+You can review the suggestions and choose to save for later, decline, edit, or approve. See the steps in the next section.
 
 ## Reviewing suggestions
 
@@ -38,13 +43,19 @@ Follow these instructions to view the synonym suggestions and choose whether to
 
 1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
 2. In **Intelligent Search**, click **Synonyms**.
-    If there are suggestions for you to review, a modal will pop up, indicating the number of generated suggestions.
-3. Click `Review` to continue. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
-4. To review the suggestion, choose one of the following actions:
+3. When accessing the **Synonyms** page, if there are suggestions that have not yet been reviewed, a modal will be displayed indicating the number of suggestions generated. In this case, click `Review` to review them.
+
+    If you click `Not Now`, the suggestions will remain in the **New suggestions** box, indicating the number of generated suggestions. To review them, click `Review`. 
+4. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
+
+   ![synonym-suggestion-en](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
+
+5. To review each suggestion, choose one of the following actions:
+    * <i class="fas fa-bookmark"></i> **Save for Later:** Removes the suggestion from the **New suggestions** count and stores it in the **Saved suggestions** box. To review the saved suggestions later, click `Review`.
     * <i class="fas fa-times-circle"></i> **Decline**: Rejects the proposed suggestion.
-    * <i class="fas fa-pencil"></i> **Edit**: Changes the suggested synonym configuration fields. After editing, you need to click <i class="fas fa-check-circle"></i> to save. To learn more about the available fields, read the[ Configuring Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL) article.
+    * <i class="fas fa-pencil-alt"></i> **Edit**: Changes the suggested synonym configuration fields. After editing, you need to click <i class="fas fa-check-circle"></i> to save. To learn more about the available fields, read the[ Configuring Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL) article.
     * <i class="fas fa-check-circle"></i> **Approve**: Applies and saves the proposed suggestion.
-5. After reviewing all suggestions, close the modal to access the list of synonyms configured in your store.
+6. After reviewing all suggestions, close the modal to access the list of synonyms configured in your store.
 
 <div class="alert alert-error">
   <p>Once an action is performed, it cannot be undone, as the next available suggestion will be displayed immediately.</p>
diff --git a/docs/tutorials/en/intelligent-synonyms.md b/docs/tutorials/en/intelligent-synonyms.md
new file mode 100644
index 000000000..85171b8df
--- /dev/null
+++ b/docs/tutorials/en/intelligent-synonyms.md
@@ -0,0 +1,68 @@
+---
+title: 'Intelligent Synonyms'
+id: 1rR47Kk96UgFYwh8dkDG7i
+status: PUBLISHED
+createdAt: 2024-06-17T13:41:39.402Z
+updatedAt: 2024-06-17T13:42:26.751Z
+publishedAt: 2024-06-17T13:42:26.751Z
+firstPublishedAt: 2024-06-17T13:42:26.751Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: intelligent-synonyms
+locale: en
+legacySlug: intelligent-synonyms
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+
+<div class="alert alert-info">
+  <p>This feature is available for accounts that have a minimum number of sessions and orders for training the artificial intelligence model. If you would like to implement it, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>. Additional fees may apply in the future.</p>
+</div>
+
+The [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) allows you to add words, or similar sentences, as synonyms for customer search terms, increasing the chance of successful searches.
+
+With the Intelligent Synonyms feature, the **Synonyms** page in the VTEX Admin provides intelligent recommendations of terms, as well as manual configuration of synonyms. The platform leverages artificial intelligence to suggest synonyms based on customer search behavior in your store.
+
+VTEX Intelligent Search achieves this by counting how many times in the last 30 days  customers have searched for a term that returned few or no search results and replaced the original term with an alternative one.
+
+Example: Suppose five customers typed `facial soap` in their search but later changed it to `face soap`. The system records this behavior, and the most rewritten terms will be displayed as suggested synonyms.
+
+The suggestions are displayed in two categories in the list of synonyms, as shown below:
+
+* **New suggestions:** Suggestions generated by the platform that have not yet been viewed.
+* **Saved suggestions:** Suggestions saved for later, as described in step 5 of the [Reviewing suggestions](#revisar-sugestoes) section.
+
+![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
+
+You can review the suggestions and choose to save for later, decline, edit, or approve. See the steps in the next section.
+
+## Reviewing suggestions
+
+Follow these instructions to view the synonym suggestions and choose whether to decline, edit, or approve them:
+
+1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
+2. In **Intelligent Search**, click **Synonyms**.
+3. When accessing the **Synonyms** page, if there are suggestions that have not yet been reviewed, a modal will be displayed indicating the number of suggestions generated. In this case, click `Review` to review them.
+
+    If you click `Not Now`, the suggestions will remain in the **New suggestions** box, indicating the number of generated suggestions. To review them, click `Review`. 
+4. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
+
+   ![synonym-suggestion-en](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
+
+5. To review each suggestion, choose one of the following actions:
+    * <i class="fas fa-bookmark"></i> **Save for Later:** Removes the suggestion from the **New suggestions** count and stores it in the **Saved suggestions** box. To review the saved suggestions later, click `Review`.
+    * <i class="fas fa-times-circle"></i> **Decline**: Rejects the proposed suggestion.
+    * <i class="fas fa-pencil-alt"></i> **Edit**: Changes the suggested synonym configuration fields. After editing, you need to click <i class="fas fa-check-circle"></i> to save. To learn more about the available fields, read the[ Configuring Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL) article.
+    * <i class="fas fa-check-circle"></i> **Approve**: Applies and saves the proposed suggestion.
+6. After reviewing all suggestions, close the modal to access the list of synonyms configured in your store.
+
+<div class="alert alert-error">
+  <p>Once an action is performed, it cannot be undone, as the next available suggestion will be displayed immediately.</p>
+</div>
+
+## Learn more
+
+* [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV)
+* [Configuring Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL)
+* [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
diff --git a/docs/tutorials/en/interacting-with-masterdata-through-graphql.md b/docs/tutorials/en/interacting-with-masterdata-through-graphql.md
index d7b413796..5ca765ee0 100644
--- a/docs/tutorials/en/interacting-with-masterdata-through-graphql.md
+++ b/docs/tutorials/en/interacting-with-masterdata-through-graphql.md
@@ -27,7 +27,7 @@ Start off by making sure you have the latest version of the VTEX CLI and cloning
 
 run `vtex init` and select `graphql getting-started`
 
-![Screen Shot 2019-01-16 at 15.00.29](https://images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
+![Screen Shot 2019-01-16 at 15.00.29](//images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
 
 We'll be using it's basic structure to adapt to our needs.
 
@@ -149,15 +149,15 @@ Open up Postman and type in the following search:
 
 Choose an ID, copy it.  We'll be pasting it in our query.
 
-![Screen Shot 2019-01-16 at 16.14.31](https://images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
+![Screen Shot 2019-01-16 at 16.14.31](//images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
 
-![Screen Shot 2019-01-16 at 17.34.04](https://images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
+![Screen Shot 2019-01-16 at 17.34.04](//images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
 
 You should now see the output light up on the right. 
 Congratulations! You've already acomplished a simple query in record time.
 
 You can look under the hood by switching back to the terminal and seeing GraphQL resolving the queries how you normally would have.
-![Screen Shot 2019-01-16 at 16.29.03](https://images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
+![Screen Shot 2019-01-16 at 16.29.03](//images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
 
 
 **But what if we want to SEARCH by using all possible filters?**
@@ -269,6 +269,6 @@ query{
 
 ```
 
-![Screen Shot 2019-01-16 at 17.23.00](https://images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
+![Screen Shot 2019-01-16 at 17.23.00](//images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
 
 And there you have it :) Happy coding!
diff --git a/docs/tutorials/en/interaction-details.md b/docs/tutorials/en/interaction-details.md
index 6ff4df494..57b542d31 100644
--- a/docs/tutorials/en/interaction-details.md
+++ b/docs/tutorials/en/interaction-details.md
@@ -1,10 +1,10 @@
 ---
 title: 'Offer Management: interaction details'
 id: 5qC6XPkyUsYPd0dqKHQNlf
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T01:16:13.273Z
-updatedAt: 2023-03-31T04:45:50.134Z
-publishedAt: 2023-03-31T04:45:50.134Z
+updatedAt: 2024-06-20T21:43:33.011Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:20:58.901Z
 contentType: tutorial
 productTeam: Channels
@@ -12,9 +12,15 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: interaction-details
 locale: en
 legacySlug: interaction-details
-subcategory: 2zVauFUkYn8vgS0y0MfWeK
+subcategory: 
 ---
 
+<div class="alert alert-info">
+To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
+For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
+</div>  
+
 The **Interaction details** page in the [Offer Management](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) module allows sellers to view all interactions of an offer regarding its sending and syncing processes in a comprehensive manner. Interaction details will be available for ten days after registration.
 
 To access the **Interaction details** page, follow the steps below:
@@ -33,7 +39,7 @@ In <b>Offer Management</b> , you can track offers using <a href="https://help.vt
 </div>
 
 ## Header
-![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/d28534c5926b61794e3b16ac91636f86/Interaction_details_EN_cabe__alho.jpg)
+![Interaction details PT cabeçalho](//images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/d28534c5926b61794e3b16ac91636f86/Interaction_details_EN_cabe__alho.jpg)
 The *header* summarizes the offer’s main information for quick viewing, such as the SKU name, the logo of the channel it was sent to, its ID on the VTEX platform and on the channel.
 
 ## Interaction result
@@ -42,23 +48,23 @@ The *header* summarizes the offer’s main information for quick viewing, such a
 The *Interaction result* block provides information on the effect of the interaction on the offer, based on the combination of logs in the interaction. The status of an offer is determined by the result of its interactions. It indicates whether it was possible to send the offer to the channel and sync it. Here are possible interaction results: 
 
 ### Result: Success
-![Interaction details PT resultado sucesso](https://images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/e0f5c0733c6ad25cc3eda476500bcd6a/Interaction_details_EN_resultado_sucesso.jpg)
+![Interaction details PT resultado sucesso](//images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/e0f5c0733c6ad25cc3eda476500bcd6a/Interaction_details_EN_resultado_sucesso.jpg)
 The *Success* result indicates that the interaction fulfilled its expected effect. It means that the offer has been sent to the channel correctly, or that the offer’s price, inventory, or catalog information has been updated. 
 
 ### Result: Failure
-![Interaction details PT resultado falha](https://images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/c7dce5355ca57a597664740779478344/Interaction_details_ES_resultado_falha.jpg)
+![Interaction details PT resultado falha](//images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/c7dce5355ca57a597664740779478344/Interaction_details_ES_resultado_falha.jpg)
 The *Failure* result indicates that the system could not complete the interaction due to an issue. This result leads to the *Error* status in the offer, preventing it from being sent or updated on the channel. When the interaction result is *Failure*, the issues detected will be listed and you can expand them for more information.
 
 ### Result: Notification
-![Interaction details PT resultado aviso](https://images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/f9983790af5371a5412ba1127390655e/Interaction_details_EN_resultado_aviso.jpg)
+![Interaction details PT resultado aviso](//images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/f9983790af5371a5412ba1127390655e/Interaction_details_EN_resultado_aviso.jpg)
 The *Notification* result provides information about the offer’s sending and syncing processes, making it easier for the seller to monitor it.
 
 ### Result: Processing
-![Interaction details PT resultado processing](https://images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/e9a13da08b1a3e1b572c6363182d15e9/Interaction_details_EN_resultado_processing.jpg)
+![Interaction details PT resultado processing](//images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/e9a13da08b1a3e1b572c6363182d15e9/Interaction_details_EN_resultado_processing.jpg)
 The *Processing* result means the interaction has not been completed and is still in progress. This is a temporary status because once the interaction's process is completed, it can only result in `success`, `failure`, or `notification`. 
 
 ## Timeline
-![Interaction details EN linha do tempo](https://images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/67355b2fccc741b3774e3789a17773e5/Interaction_details_EN_linha_do_tempo.jpg)
+![Interaction details EN linha do tempo](//images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/67355b2fccc741b3774e3789a17773e5/Interaction_details_EN_linha_do_tempo.jpg)
 The system generates interactions to update information, and they use logs to make the necessary actions during the process. 
 
 The timeline on the **Interaction details** page displays the logs generated for the interaction in chronological order, and the information is available for consultation for ten days. Once the interaction objective is achieved and no further logs are to be generated, the interaction is automatically closed. The timeline displays the following data:
diff --git a/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
index 1eaf06bc0..003f5e460 100644
--- a/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
@@ -26,7 +26,7 @@ The following data set is displayed on the __All orders__ screen in the __Orders
 
 Alongside each of these values, a percentage representing the variation against today's orders will appear.
 
-![order-metric-en](https://images.ctfassets.net/alneenqid6w5/6gLFOziUnYEGuyU6S8iUuA/58c55d9286f28db09faf423fa6c5d2da/order-metric-en.png)
+![order-metric-en](//images.ctfassets.net/alneenqid6w5/6gLFOziUnYEGuyU6S8iUuA/58c55d9286f28db09faf423fa6c5d2da/order-metric-en.png)
 
 In the screenshot of the metrics above, the following information will be displayed:
 
diff --git a/docs/tutorials/en/introduction-to-vtex-apis.md b/docs/tutorials/en/introduction-to-vtex-apis.md
index e09a3a2d6..88756363c 100644
--- a/docs/tutorials/en/introduction-to-vtex-apis.md
+++ b/docs/tutorials/en/introduction-to-vtex-apis.md
@@ -117,7 +117,7 @@ They are divided by module or functionality.  Click on one of them to find the c
  
 On the right side of these indications, Postman displays one Sample Request for each API. In accordance with the wording selected on the check box placed above it, the Sample Request shows the application of the request in the code.
 
-![sample request](https://images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
+![sample request](//images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
  
 Some APIs also have a Sample Response, which is an example of a response to that request.
  
diff --git a/docs/tutorials/en/inventory-data-pipeline-beta.md b/docs/tutorials/en/inventory-data-pipeline-beta.md
new file mode 100644
index 000000000..9306a9d2f
--- /dev/null
+++ b/docs/tutorials/en/inventory-data-pipeline-beta.md
@@ -0,0 +1,97 @@
+---
+title: 'Inventory Data Pipeline (Beta)'
+id: 2IvKMZV9SNrE6ipBRQr8h2
+status: PUBLISHED
+createdAt: 2024-02-02T17:41:24.979Z
+updatedAt: 2024-07-29T19:12:57.037Z
+publishedAt: 2024-07-29T19:12:57.037Z
+firstPublishedAt: 2024-05-27T19:26:59.588Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: inventory-data-pipeline-beta
+locale: en
+legacySlug: inventory
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+The dataset of the `item_inventory` table provides information about the availability of items in the inventory, specifying the total quantity of available items, active reservations, unlimited inventory option, as well as SKU and inventory IDs. This table also records updates with timestamps and control IDs.  
+
+This section includes the following information:  
+
+- [Inventory data characteristics](#data-characteristics)
+- [Table: item_update_latest](#table-item-update-latest)
+- [Table: item_update_historical](#table-item-update-historical)
+- [Analyses with item_inventory](#analyses-with-inventory)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics
+
+| **Characteristic** | **Description** |
+|:---:|:---:|
+| **Data source** | Obtained from information in the logistics module. |
+| **Availability** | VTEX Admin. |
+| **History** | The data is retained for two years, from 2024 for clients who already use the VTEX platform. |
+| **Minimum update interval** | One hour. |
+
+## Table: item_update_latest
+
+The table fields are described below:
+
+| **Column name** | **Column type** | **Column description** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | Identifier used when data is loaded into the table for quality control of data ingestion. |
+| **last_date** | timestamp without time zone | Date and time of the last change to the inventory. |
+| **item_availabilty_id** | character varying(65535) | SKU inventory schema's id. |
+| **item_id** | character varying(65535)	 | Item’s identifier. |
+| **main_account_name** | character varying(65535)	 | Name of the parent account associated with the item. |
+| **account_name** | character varying(65535)	 | Name of the account related to the item. |
+| **is_unlimited_quantity** | boolean | Boolean flag that indicates whether a sku is always available regardless of its quantity. |
+| **quantity** | integer | SKU quantity on stock. |
+| **reserved_quantity** | integer | Reserved SKU units. Orders for these reservations have not yet been approved for payment. |
+| **reservation_id** | character varying(65535) | Identification of a reserve for that item. |
+
+## Table: item_update_historical
+
+The table fields are described below:
+
+| **Column name** | **Column type** | **Column description** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | Identifier used when data is loaded into the table for quality control of data ingestion. |
+| **created_at** | timestamp without time zone | Date and time of the change to the inventory. |
+| **item_availabilty_id** | character varying(65535) | SKU inventory schema's id |
+| **item_id** | character varying(65535)	 | Item’s identifier |
+| **main_account_name** | character varying(65535)	 | Name of the parent account associated with the item. |
+| **account_name** | character varying(65535)	 | Name of the account related to the item. |
+| **author_id** | character varying(65535) | Author of the inventory change |
+| **event_type** | character varying(65535) | Type of availability change (e.g. reservation-create, reservation-cancel, item-availability-update) |
+| **metadata_created_at** | timestamp without time zone | Time an event was generated |
+| **is_unlimited_quantity** | boolean | Boolean flag that indicates whether a sku is always available regardless of its quantity |
+| **quantity** | integer | SKU quantity on stock |
+| **reserved_quantity** | integer | Reserved SKU units. Orders for these reservations have not yet been approved for payment. |
+| **reservation_id** | character varying(65535) | Identification of a reserve for that item |
+
+## Analyses with inventory
+
+Some of the analyses that can be run using the inventory table are mentioned below:
+
+- **Inventory level analysis:** Assess whether the inventory meets demand and identify items at risk of running out of stock.
+- **Inventory reservation trends:** Analyze the number of items that have been reserved over time to identify patterns and adjust inventory management strategies.
+- **Inventory distribution analysis by account:** Optimize inventory management across multiple accounts and understand how inventory is distributed.
+
+## Correlations with other data
+
+Inventory data correlates with order and product sets, and provides a more comprehensive analysis for purchases, sales, and marketing. Some examples are: 
+
+- **Interaction with order data:** Joint analysis with order data offers insights about how efficiently is customer demand being met and helps forecast restocking needs.
+- **Relationship with SKUs:** Integration with SKU data helps manage inventory based on product popularity and availability.
+- **Purchase and supplier data:** Coordination with purchase data allows you to maintain an ideal inventory balance, which avoids overstocking or shortages.
+- **Sales and marketing analysis:** Understanding inventory directly impacts marketing and sales strategies, which allows aligning promotions and campaigns with product availability.
+
+### Discover other Datasets
+
+- [Navigation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Payments](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Orders](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Prices](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promotions](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/en/inventory-update-history.md b/docs/tutorials/en/inventory-update-history.md
index dd747a2d8..e78e6cafc 100644
--- a/docs/tutorials/en/inventory-update-history.md
+++ b/docs/tutorials/en/inventory-update-history.md
@@ -3,8 +3,8 @@ title: 'Inventory update history'
 id: 5AM7xbmMzmKSEQewakamc2
 status: PUBLISHED
 createdAt: 2017-08-01T15:03:08.876Z
-updatedAt: 2023-03-29T19:59:22.057Z
-publishedAt: 2023-03-29T19:59:22.057Z
+updatedAt: 2024-04-02T18:24:14.768Z
+publishedAt: 2024-04-02T18:24:14.768Z
 firstPublishedAt: 2017-08-01T15:06:58.792Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -31,11 +31,14 @@ To view the update history of a SKU, follow the steps below:
 2. Select the SKU of which you want to see the history. To learn how to use the filters and search, check out the article [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139).
 3. In the **Last update** column, click the blue number.
 4. The **Update Logs** window will open with all the changes. Each row corresponds to an update, and the columns contain:
-    * The user who made the change.	
-    * Last updated date and time.
-    * The quantity of items before and after the update.
+  * The user who made the change.	
+  * Last updated date and time.
+  * The quantity of items before the update.
+  * The quantity of itemsafter the update.
 
- <div class="alert alert-warning">
+<div class="alert alert-warning">
 You can only see the last 50 updates in the update log of a given SKU.
 </div>
 
+The total quantity of items on the [Inventory Management](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139) page is updated in real-time, but it may take up to 1 hour to reflect in the inventory history.
+
diff --git a/docs/tutorials/en/kit-registration.md b/docs/tutorials/en/kit-registration.md
index b3d965374..aca0e8dcd 100644
--- a/docs/tutorials/en/kit-registration.md
+++ b/docs/tutorials/en/kit-registration.md
@@ -3,8 +3,8 @@ title: 'Kit registration'
 id: tutorials_215
 status: PUBLISHED
 createdAt: 2017-04-27T22:13:50.843Z
-updatedAt: 2023-03-29T14:48:43.077Z
-publishedAt: 2023-03-29T14:48:43.077Z
+updatedAt: 2024-05-06T14:40:12.311Z
+publishedAt: 2024-05-06T14:40:12.311Z
 firstPublishedAt: 2017-04-27T23:02:48.663Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -26,7 +26,7 @@ A kit may or may not allow for its components to be sold separately. See the dif
 
 To set up the kit, all its products – that is, its components – must have already been created. See the example below:
 
-![01-components EN](https://images.ctfassets.net/alneenqid6w5/3pQ4a93uZi8sqQA2oGywi4/4c0acd198d16920872025de5d95ed61f/01-components_EN.png)
+![01-components EN](//images.ctfassets.net/alneenqid6w5/3pQ4a93uZi8sqQA2oGywi4/4c0acd198d16920872025de5d95ed61f/01-components_EN.png)
 
 After creating all component products, we can move on to defining the kit’s settings.
 
@@ -37,7 +37,7 @@ After creating all component products, we can move on to defining the kit’s se
 5. If you would like a look kit, click on the option __Bundle with SKUs sold separately__.
 6. Click on `Save`.
 
-![02-kit EN](https://images.ctfassets.net/alneenqid6w5/5O4ZP4iGI0YE60aMOkAI4Q/830694f23e7b6b7d2e4b0cd6c2438c41/02-kit_EN.png)
+![02-kit EN](//images.ctfassets.net/alneenqid6w5/5O4ZP4iGI0YE60aMOkAI4Q/830694f23e7b6b7d2e4b0cd6c2438c41/02-kit_EN.png)
 
 ## Associating components
 
@@ -52,9 +52,9 @@ After the kit product has been created, you must associate the components, accor
 7. Enter the SKU unit price inside the kit.
 6. Click on `Save`.
 
-![03-add component to kit EN](https://images.ctfassets.net/alneenqid6w5/1qBz4qjkAQ8OE8kMMeiw0o/eb5437d1d8a7c40e30998f2ad3723c5e/03-add_component_to_kit_EN.gif)
+![03-add component to kit EN](//images.ctfassets.net/alneenqid6w5/1qBz4qjkAQ8OE8kMMeiw0o/eb5437d1d8a7c40e30998f2ad3723c5e/03-add_component_to_kit_EN.gif)
 
-![04-kit in cart ALL](https://images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
+![04-kit in cart ALL](//images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
 
 ## Kit Weight
 
@@ -62,11 +62,7 @@ The weight of the kit will be made up by the sum of the weight of its components
 
 ## Inventory
 
-The kit’s inventory will always be the inventory of its components. In other words, it is not possible to enter inventory merely in the kit, but rather in each and every independent component, in order to update the kit’s inventory. 
-
-This information can be easily previewed in __Inventory &amp; shipping &gt; Inventory__:
-
-![05-manage inventory by kit EN](https://images.ctfassets.net/alneenqid6w5/TIr2YphaMMW2WO8wKma8W/9c561bfa69de4943eea8efe9480a369b/05-manage_inventory_by_kit_EN.gif)
+The kit’s [inventory](https://help.vtex.com/en/tutorial/inventory-management--tutorials_139) will always be the inventory of its components. In other words, it is not possible to enter inventory merely in the kit, but rather in each and every independent component, in order to update the kit’s inventory. You can access this information in your VTEX Admin in **Catalog > Inventory > Inventory Management**.
 
 Since the SKUs that make up the kit must be sold together, the kit overall inventory will be equal to the SKU which has less inventory items. This is as such due to the fact that when a component is out of stock, the kit cannot be purchased.
 
@@ -87,7 +83,7 @@ You may only change the final price of the kit by directly accessing the pricing
 Please note that any change in any component will generate a new final price, updating what had been previously registered. 
 
 Merely changing the final price will not update the price of the components.
-![06-price list EN](https://images.ctfassets.net/alneenqid6w5/1OFwACSPPuCiiWA4YqYa28/5b4ef3a2e50e78b0be869c97288e5778/06-price_list_EN.png)
+![06-price list EN](//images.ctfassets.net/alneenqid6w5/1OFwACSPPuCiiWA4YqYa28/5b4ef3a2e50e78b0be869c97288e5778/06-price_list_EN.png)
 
 ### Learn more
 
diff --git a/docs/tutorials/en/kr1-test.md b/docs/tutorials/en/kr1-test.md
new file mode 100644
index 000000000..eb3c3fa8a
--- /dev/null
+++ b/docs/tutorials/en/kr1-test.md
@@ -0,0 +1,18 @@
+---
+title: 'KR1 - TEST'
+id: 4QvsXwhDJm778DgTsMZmGw
+status: DRAFT
+createdAt: 2024-05-07T02:16:58.777Z
+updatedAt: 2024-05-07T02:22:22.011Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Undefined
+author: 
+slug: kr1-test
+locale: en
+legacySlug: kr1-test
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
new file mode 100644
index 000000000..f1d606981
--- /dev/null
+++ b/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
@@ -0,0 +1,104 @@
+---
+title: 'Lead time: Shipping time at SKU level'
+id: 16yv5Mkj6bTyWR1hCN2f4B
+status: PUBLISHED
+createdAt: 2023-09-22T00:32:26.416Z
+updatedAt: 2023-09-22T13:32:38.292Z
+publishedAt: 2023-09-22T13:32:38.292Z
+firstPublishedAt: 2023-09-22T01:35:53.577Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: lead-time-shipping-time-at-sku-level
+locale: en
+legacySlug: lead-time-shipping-time-at-sku-level
+subcategory: 3PQwnyOcNyYgawy06oe6gE
+---
+
+Lead time is an optional configuration for shipping time at SKU level. This means that you can set a shipping period for a [warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) SKU, and this time will be added to the order's total shipping time.
+
+Lead time configuration is done within [inventory management](https://help.vtex.com/en/tutorial/gerenciar-inventario--tutorials_139) as it relates to items in a warehouse that are available for sale.
+
+This article covers the following:
+
+- [Total shipping time:](#total-shipping-time) How lead time affects the order's shipping time.
+- [Main use cases:](#main-use-cases) Scenarios where lead time can optimally apply.
+- [SKU availability:](#sku-availability) How the platform behaves when the SKU is unavailable for sale.
+- [Configuring lead time:](#configuring-lead-time) How to configure lead time through the VTEX Admin.
+- [Configuring lead time calculation in calendar days:](#configuring-lead-time-calculation-in-calendar-days-optional) Optional step for the lead time calculation to be in calendar days, not business days (default).
+
+<div class = "alert alert-info">
+To configure lead time via API, see <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## Total shipping time
+
+When configured, the lead time is an additional time comprising the shipping time for the order displayed to the customer at checkout. The image below shows how the total time is calculated:
+
+![lead_time_image_total_time_EN](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
+
+- **Lead time:** The amount of time that can be configured for a warehouse SKU. For example, this period could correspond to the item's handling or manufacturing time. This configuration is optional and, by default, is set as zero days
+- [Warehouse time:](https://help.vtex.com/en/tutorial/gerenciar-estoque--tutorials_137) Time the SKU takes to leave a warehouse and arrive at a [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). This configuration is required, but you can set the time to zero.
+- [Loading dock time:](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) Time the SKU takes to leave the loading dock, the point between the warehouse and the [carrier](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE), and be shipped to the customer. This configuration is required, but you can set the time to zero.
+- [Shipping policy:](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) Gathers the rules and conditions displayed to customers at checkout, including:
+    - [Shipping rates](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127)
+    - Carrier business hours
+    - Delivery windows
+    - Delivery capacity
+    - Types of deliverable products (modals)
+
+## Main use cases
+
+Here are some use cases where the lead time setting is particularly useful.
+
+### Third-party suppliers
+
+Easily manage the time a third-party supplier, such as a factory or manufacturer, takes to produce, handle, ship, or deliver a product.
+
+### Large and customizable products
+
+For operations that sell large products, such as furniture or customizable products, lead time enables them to manage product handling time, contributing to warehouse and dock management efficiency.
+
+### Dropshipping
+
+In dropshipping — when the supplier ships the product directly to the customer — configuring shipping time at SKU level means having more flexibility to set deadlines for handling and shipping the product from third-parties.
+
+## SKU availability
+
+The VTEX platform will behave differently depending on SKU availability, and these are the possible scenarios:
+
+- <i class="far fa-check-circle"></i> **SKU is in stock:** You set the SKU lead time, the time considered in the order shipping calculation, and the total time will be displayed to the customer at checkout.
+- <i class="fas fa-times"></i> **SKU is out of stock:** You set the SKU lead time, but the SKU is not considered valid because there are no units available for sale.
+- <i class="far fa-check-circle"></i> **Infinite inventory:** You set the SKU lead time, the time considered in the order's shipping calculation, and the total time will be displayed to the customer at checkout. As long as inventory is enabled as infinite, the SKU will always be valid for sales.
+
+## Configuring lead time
+
+Lead time is set to zero, and the limit is 365 days. By default, the calculation is made in business days, considering public holidays and other [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) conditions, but you can change the [calculation to calendar days](#configuring-lead-time-calculation-in-calendar-days-optional).
+
+To configure the lead time for a SKU, follow the steps below:
+
+1. In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type **Inventory Management** in the search bar at the top of the page.
+2. Select the SKU you want to configure. You can use the search bar and filters.
+3. In the SKU row and the **Lead time (days)** column, enter the days you want.
+  ![lead_time_inventory_management_EN](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png)
+4. Click `Save` at the bottom of the page.
+
+<div class = "alert alert-info">
+In the VTEX Admin, lead time is always configured in days, but you can configure it in hours, minutes, and seconds using the Update inventory by SKU and warehouse endpoint.
+</div>
+
+## Configuring lead time calculation in calendar days (optional)
+
+If you want the lead time to be calculated in calendar days, follow the steps below:
+
+1. In the VTEX Admin, go to **Shipping > Shipping Strategy > Shipping Policies**, or type **Shipping Policies** in the search bar at the top of the page.
+2. Find the shipping policy you want. You can use the search bar and filters.
+    > To create a new shipping policy, read the [Shipping Policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) article.
+3. In the shipping policy row, click the <i class="fas fa-ellipsis-v"></i> menu icon and select `Edit`.
+4. In the **Weekends and Holidays** section, activate the desired toggles:
+    - <i class="fas fa-toggle-on"></i> **Saturday delivery**
+    - <i class="fas fa-toggle-on"></i> **Sunday delivery**
+    - <i class="fas fa-toggle-on"></i> **Holiday delivery**
+
+5. Click `Save Changes`.
+
diff --git a/docs/tutorials/en/license-manager-resources.md b/docs/tutorials/en/license-manager-resources.md
index fd918e010..71f60ef51 100644
--- a/docs/tutorials/en/license-manager-resources.md
+++ b/docs/tutorials/en/license-manager-resources.md
@@ -3,8 +3,8 @@ title: 'License Manager resources'
 id: 3q6ztrC8YynQf6rdc6euk3
 status: PUBLISHED
 createdAt: 2022-02-14T17:53:22.572Z
-updatedAt: 2022-08-24T14:51:33.355Z
-publishedAt: 2022-08-24T14:51:33.355Z
+updatedAt: 2024-06-05T13:16:40.276Z
+publishedAt: 2024-06-05T13:16:40.276Z
 firstPublishedAt: 2022-02-14T19:56:27.935Z
 contentType: tutorial
 productTeam: Identity
@@ -15,24 +15,24 @@ legacySlug: license-manager-resources
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-VTEX provides several pre-defined [roles](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) for administrative users. This allows employees to do their jobs requiring the minimum resources necessary. However, we know that every ecommerce has its unique needs, and flexibility is essential for addressing specific business problems. 
+VTEX provides several pre-defined [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) for administrative users. This allows employees to do their jobs requiring the minimum resources necessary. However, we know that every ecommerce has its unique needs, and flexibility is essential for addressing specific business problems. 
 
-Therefore, the VTEX platform offers you the possibility to create custom access profiles, allowing you to choose precisely which custom profile can access specific resources. Below you will find links to the description of the resources available on the VTEX platform by product.
+Therefore, the VTEX platform offers you the possibility to create custom access profiles, allowing you to choose precisely which custom profile can access specific resources. Below you will find the descriptions of the resources available on the VTEX platform by product.
 
 <div class="alert alert-danger">
-Unrestricted use of resources increases the risk of store attacks by leaking login credentials with access to critical resources.
-If you have questions about the description of a specific feature, please feel free to contact us.
+  <p>Unrestricted use of resources increases the risk of store attacks by leaking login credentials with access to critical resources.
+If you have questions about the description of a specific feature, please feel free to contact us.</p>
 </div>
 
-<iframe src="https://help.vtex.com/tables/resources/en" title="License Manager resources" frameBorder="0" width="800" height="850"></iframe>
+<iframe src="https://help.vtex.com/tables/resources/en" title="License Manager resources" frameBorder="0" width="100%" height="850"></iframe>
 
 <div class = "alert alert-info">
-In the <a href="https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a> application, License Manager resources are identified by the corresponding keys.
+  <p>In the <a href="https://help.vtex.com/en/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a> application, License Manager resources are identified by the corresponding keys.</p>
 </div>
 
 ## Internal or deprecated resources
 
 In the License Manager interface, you can also find resources that are deprecated or exclusively for internal use by VTEX. These have no impact on your store. They are:
 
-<iframe src="https://help.vtex.com/tables/internalresources/en" title="Internal or deprecated resources" frameBorder="0" width="800" height="700"></iframe>
+<iframe src="https://help.vtex.com/tables/internalresources/en" title="Internal or deprecated resources" frameBorder="0" width="100%" height="700"></iframe>
 
diff --git a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
new file mode 100644
index 000000000..7b384020a
--- /dev/null
+++ b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -0,0 +1,66 @@
+---
+title: 'How to limit access to the store using a trade policy'
+id: tutorials_3063
+status: PUBLISHED
+createdAt: 2017-04-27T21:52:28.228Z
+updatedAt: 2024-05-24T19:16:43.055Z
+publishedAt: 2024-05-24T19:16:43.055Z
+firstPublishedAt: 2017-04-27T23:03:54.732Z
+contentType: tutorial
+productTeam: Master Data
+author: authors_3
+slug: limiting-access-to-the-store-by-means-of-the-trade-policy
+locale: en
+legacySlug: limiting-access-to-the-store-by-means-of-the-sales-policy
+subcategory: 42hDtnYXHw5ExG6l19RP1l
+---
+
+You can limit access to a store for a number of different reasons, such as when it has a B2B site on which only registered, authorized companies may browse, or when it is an environment for exclusive customers.
+
+This can be achieved by using Master Data v1 and the store’s sales policy.
+
+<div class="alert alert-warning">
+This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+ <ul>
+<li>
+<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+Master Data version characteristics
+ </a>
+</li>
+<li>
+<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+Master Data v2
+</a>
+</li>
+</ul>
+</div>
+
+## Creating a cluster of customers
+
+The first step is to create a cluster which will identify those customers that can access the store. [To learn how to create a cluster of customers, read our manual](/en/faq/how-can-i-create-cluster-of-customers/).
+
+## Changing a trade policy
+
+After creating a cluster, you must include a rule in the trade policy allowing access to the site only to customers in that cluster.
+
+1. In the VTEX Admin, click **Store Settings** > **Channels** > **Trade Policies**.
+2. In the sales policy used, click __Alter__.
+3. In the **Conditional Rule** field, enter the value **ClusterName=”true”**. Note that the value **ClusterName** must be changed to the name of the field in the data entity.
+4. Click on the **Save** button.
+
+![Catalog EN](//images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/8d11cabbb359f20a73667b2a787e1ee4/politicas_comerciais_EN.png)
+
+In the above configuration, only customers with the value “true” (using a Boolean field – where values are either true or false) can access the site.
+
+However there are other possibilities for configuration. For instance, you can configure **ClusterName="false"** – where only customers with the field value **false** can access the site, or **ClusterName="silva"** – where only customers with the value **silva** in the field used for the cluster can access the site.
+
+## Registering customers with access
+
+In the case of B2B, where the store does not know which customers may have access, a form will have to be created for them to register their details. The store will then use Master Data to verify the details and decide whether or not to grant access. [For this configuration, see our manual for B2B stores](/en/tutorial/setting-up-b2b-on-vtex/).
+
+## Learn more
+
+- [Marketplace strategies at VTEX](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete)
+- [How trade policies work](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+- [Creating a trade policy](https://help.vtex.com/en/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE)
+- [Configuring a marketplace trade policy](https://help.vtex.com/en/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)
diff --git a/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md b/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md
index 1900ac4da..a8e27f9cb 100644
--- a/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md
+++ b/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md
@@ -19,7 +19,7 @@ You can configure one of your store’s banners to redirect users to a page of y
 
 ## Internal URLs
 
-![internal-url](https://images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3a727394e2f315558ccb783aa9cccb20/image2.png)
+![internal-url](//images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3a727394e2f315558ccb783aa9cccb20/image2.png)
 
 1. In the VTEX Admin, access **Storefront > Site Editor**.
 2. Select a __Carousel__ block and choose the banner whose content you want to edit.
@@ -33,7 +33,7 @@ The <i>Banner target page</i> and <i>Params</i> fields have been deprecated. The
 
 ## External URLs
 
-![external-url](https://images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/43eece9d63ba77a5e63945c17bc74e7c/image1.png)
+![external-url](//images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/43eece9d63ba77a5e63945c17bc74e7c/image1.png)
 
 1. In the VTEX Admin, access **Storefront > Site Editor**.
 2. Select a __Carousel__ block and choose the banner whose content you want to edit.
diff --git a/docs/tutorials/en/list-of-payment-providers-by-country.md b/docs/tutorials/en/list-of-payment-providers-by-country.md
index f4ddcf012..891313357 100644
--- a/docs/tutorials/en/list-of-payment-providers-by-country.md
+++ b/docs/tutorials/en/list-of-payment-providers-by-country.md
@@ -3,8 +3,8 @@ title: 'List of Payment Providers by Country'
 id: 2im3BEGXxSAcRuxEaIHPvp
 status: PUBLISHED
 createdAt: 2022-02-01T18:37:56.763Z
-updatedAt: 2023-04-17T15:31:26.758Z
-publishedAt: 2023-04-17T15:31:26.758Z
+updatedAt: 2023-11-13T18:15:23.134Z
+publishedAt: 2023-11-13T18:15:23.134Z
 firstPublishedAt: 2022-02-01T18:39:26.915Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: list-of-payment-providers-by-country
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-VTEX offers the possibility of several [payment providers](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete) for your business in many countries.
+VTEX offers the possibility of several [payment providers](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444) for your business in many countries.
 
 To identify the available options, enter the name of the country name, payment provider or Split Payout availability (Yes/No) in the **Search** field from the list below. You can also choose to display 10, 25, 50 or 100 results per page by selecting the **Show Entries** field.
 
diff --git a/docs/tutorials/en/loading-dock.md b/docs/tutorials/en/loading-dock.md
index fd04d290b..f24d80b6d 100644
--- a/docs/tutorials/en/loading-dock.md
+++ b/docs/tutorials/en/loading-dock.md
@@ -20,7 +20,7 @@ The loading dock is part of the logistics system and usually acts as an intermed
 
 On VTEX, the loading dock is an intermediary between storing items and delivering orders. The loading dock integrates the necessary parts for your store’s logistics system: [Warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb), [Trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) and [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140).
 
-![Doca EN](https://images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/0e98be333d982b352836b24b72f65997/Doca_EN.svg)
+![Doca EN](//images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/0e98be333d982b352836b24b72f65997/Doca_EN.svg)
 
 <div class = "alert alert-info">
 The Warehouse is the physical storage for the goods sold by the store; the Trade policy is the configuration of the store's sales strategies; and the Shipping policy is a set of rules that define the shipping options and conditions.
diff --git a/docs/tutorials/en/locations-details-page-beta.md b/docs/tutorials/en/locations-details-page-beta.md
index 14e96948f..d0ec0da8d 100644
--- a/docs/tutorials/en/locations-details-page-beta.md
+++ b/docs/tutorials/en/locations-details-page-beta.md
@@ -1,10 +1,10 @@
 ---
 title: "Location's details page (Beta)"
 id: 3se4QBRYsNCwC8Wo56J6zG
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-05-09T16:24:38.315Z
-updatedAt: 2023-05-10T00:53:18.368Z
-publishedAt: 2023-05-10T00:53:18.368Z
+updatedAt: 2023-11-10T14:44:21.843Z
+publishedAt: 
 firstPublishedAt: 2023-05-09T20:47:55.824Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/en/logistics-module-overview.md b/docs/tutorials/en/logistics-module-overview.md
index f777d567a..aa95c230e 100644
--- a/docs/tutorials/en/logistics-module-overview.md
+++ b/docs/tutorials/en/logistics-module-overview.md
@@ -27,7 +27,7 @@ That's where you can register the relation between **[Warehouse](https://help.vt
 
 That's where you can register the set prices and delivery time for a particular ZIP code range, considering cubic weight, dimensions, among other factors.
 
-![tarifas-envioEN](https://images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/217dcd115a91f09f1e2fd9735a1a6326/tarifas_envioEN.png)
+![tarifas-envioEN](//images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/217dcd115a91f09f1e2fd9735a1a6326/tarifas_envioEN.png)
 
 - [Shipping rates](https://help.vtex.com/en/tutorial/shipping-rates--1Balpg3rv0854udEPedvMM)
 
@@ -37,35 +37,35 @@ Here you can play with different scenarios for the delivery of your product, cho
 
 this section then shows the values and the carriers related to the delivery, dimension and weight of the products, price of the delivery and estimated time, besides additional details on the Zip Code range values, percentages that vary according to the product weight range, volume, additional value per gram, cost to the dock, cubic factor and cubic weight.
 
-![simulador envioEN](https://images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/3defae0446513bfa01b1a2c9b648492c/simulador_envioEN.png)
+![simulador envioEN](//images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/3defae0446513bfa01b1a2c9b648492c/simulador_envioEN.png)
 - [How to simulate a shipping](http://help.vtex.com/en/tutorial/freight-simulation)
 
 ## Inventory
 
 A place to manage and track the stock movement held in store products. It registers the reservations made on a product so far and if they have been confirmed or not.
 
-![gerenciar inventarioEN](https://images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/e2938a93d57002ec668b1e99726a9b30/gerenciar_inventarioEN.png)
+![gerenciar inventarioEN](//images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/e2938a93d57002ec668b1e99726a9b30/gerenciar_inventarioEN.png)
 - [Managing inventory](http://help.vtex.com/en/tutorial/managing-stock-items)
 
 ## Geolocation shipping
 
 Here you can build polygons for a specific logistic service. That’s typically used in rural and industrial areas, for example, where the division is made by lots, or in hazardous areas, where it's necessary to avoid determined sites. The feature’s structure is dynamic, so that you can easily draw on the map the area to be delimited.
 
-![geolocalizaçaoEN](https://images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/192f4e00b0517e5ee00249a3de300125/geolocaliza__aoEN.png)
+![geolocalizaçaoEN](//images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/192f4e00b0517e5ee00249a3de300125/geolocaliza__aoEN.png)
 - [Geolocation](http://help.vtex.com/en/tutorial/registering-geolocation)
 
 ## Pickup points
 
 Here you can delete, edit and register a Pickup Point. As a new delivery channel option, the Pickup Point feature provides greater flexibility and purchase experience to the customer as it allows the order pickup to be made in a physical point.
 
-![pontos retiradaEN](https://images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/43fa5c2895d2e53ea19c6ac2a60dd93e/pontos_retiradaEN.png)
+![pontos retiradaEN](//images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/43fa5c2895d2e53ea19c6ac2a60dd93e/pontos_retiradaEN.png)
 - [Registering Pickup Points](http://help.vtex.com/en/tutorial/registering-pickup-points)
 
 ## Holidays
 
 Here it is possible to register the days that **will not** be considered as useful for your store. The module will consider the holidays registered on this section and these days will not be counted in the delivery deadline.
 
-![feriadoEN](https://images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/0b78db315a91567102ebeb81f864cdef/feriadoEN.png)
+![feriadoEN](//images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/0b78db315a91567102ebeb81f864cdef/feriadoEN.png)
 - [Registering Holidays](http://help.vtex.com/en/tutorial/registering-holidays)
 
 ## General settings
diff --git a/docs/tutorials/en/making-a-master-data-field-editable.md b/docs/tutorials/en/making-a-master-data-field-editable.md
new file mode 100644
index 000000000..9abdaadfa
--- /dev/null
+++ b/docs/tutorials/en/making-a-master-data-field-editable.md
@@ -0,0 +1,31 @@
+---
+title: 'Making a Master Data field editable'
+id: frequentlyAskedQuestions_3049
+status: PUBLISHED
+createdAt: 2019-01-24T20:46:00.411Z
+updatedAt: 2024-06-11T16:11:17.714Z
+publishedAt: 2024-06-11T16:11:17.714Z
+firstPublishedAt: 2019-01-24T22:15:32.298Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: making-a-master-data-field-editable
+locale: en
+legacySlug: how-can-i-make-master-data-field-editable
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+An editable field is one in a Master Data form where you can edit or enter data when editing or creating a record. In other words, it is a field where you can amend the content.
+
+By default, not all the Master Data fields can be edited. To change this, proceed as follows:
+
+1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data.**
+2. Choose the application you want, and click on the cog symbol <i class="fas fa-cog"></i>.
+3. Click on the edition icon <i class="fas fa-edit"></i> for the form you want to change.
+4. Click on the tab **Layout Schemas**.
+5. Click on the edition icon <i class="fas fa-edit"></i> beside the field you want to change. ![master-data-edit-field-layout](//images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/b369c1c29a118ce9a9a1d11d78d3bede/Group_2.png)
+6. Uncheck the option **Display field as read-only**.
+7. Click on the `OK` button.
+8. Click on the `Save` button.
+
+The fields you changed can now be edited.
diff --git a/docs/tutorials/en/manage-the-sales-comissions-report.md b/docs/tutorials/en/manage-the-sales-comissions-report.md
index d634351a6..cd2163639 100644
--- a/docs/tutorials/en/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/en/manage-the-sales-comissions-report.md
@@ -61,7 +61,7 @@ Generating the report may take a while if the volume of data is big. In such cas
 Leaving the page will not affect the operation.
 </div>
 
-![Sales Comission Report EN](https://images.ctfassets.net/alneenqid6w5/3WoTE8ibcuYshdJf5sT6KV/e30dfb7f7de7b6dbcd506782e405d470/image.png)
+![Sales Comission Report EN](//images.ctfassets.net/alneenqid6w5/3WoTE8ibcuYshdJf5sT6KV/e30dfb7f7de7b6dbcd506782e405d470/image.png)
 
 Later, you can also download the recently generated report using a link provided in the list of reports.  
 
diff --git a/docs/tutorials/en/managing-b2b-organizations.md b/docs/tutorials/en/managing-b2b-organizations.md
new file mode 100644
index 000000000..53a451ea8
--- /dev/null
+++ b/docs/tutorials/en/managing-b2b-organizations.md
@@ -0,0 +1,100 @@
+---
+title: 'Managing B2B organizations'
+id: 1UwNCWhML3BsV6anpoUvVZ
+status: PUBLISHED
+createdAt: 2024-06-12T17:24:48.991Z
+updatedAt: 2024-06-12T17:36:48.744Z
+publishedAt: 2024-06-12T17:36:48.744Z
+firstPublishedAt: 2024-06-12T17:36:48.744Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: managing-b2b-organizations
+locale: en
+legacySlug: managing-b2b-organizations
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+The **B2B Organizations** app allows you to group B2B users into organizations. You can assign specific payment methods, price lists, and product collections to each organization, allowing all users in the organization to share the same commercial conditions. Each organization is segmented into one or more cost centers, each with its own shipping address.
+
+## Accessing a buyer organization
+
+To access a buyer organization in the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+To access an organization, follow these steps:
+
+1.	Click the **Organizations** tab.
+
+2.	Click the name of the desired buyer organization.
+
+This section lists all the organizations created in your store, their status, and allow store admins to:
+
+- Add new organizations.
+
+- Access the organization details page, which comprises organization data, cost centers, collections, payment terms, price lists, and users.
+
+## Organization Status
+
+In the **Status** column in the Organizations tab, you can see the status of the organization.
+
+You can use the search bar to find organizations by name or filter organizations by status.
+
+Each organization can have one of the following status:
+
+- **Active:** The organization has been approved by store admins and is currently active.
+
+- **On hold:** The organization is currently paused, which means that its users cannot complete purchases.
+
+- **Inactive:** Store admins have deactivated the organization, so your users won't be able to log in.
+
+![Status- EN](//images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/075f575659ca723e1fd8ac6f1400eb5c/Status-_EN.gif)
+
+## Adding a new organization
+
+To add a new organization in the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+
+To add a new organization, follow the steps below:
+
+1. Click the Organizations tab.
+2. Click the `New` button, and select the Add Individually option.
+3. Complete the necessary information about the new organization:
+    - **Organization name:** Name of the organization you want to create.
+    - **Cost center name:** Name of the initial cost center associated with the organization.
+    - **Country:** The country where the cost center is located.
+    - **Postal code:** Postal code of the cost center address.
+    - **Address:** Name of the street where the cost center is located.
+    - **Number:** Address number where the cost center is located.
+    - **Additional information:** Information that can be added to the cost center's address information.
+    - **Neighborhood:** Name of the neighborhood where the cost center is located.
+    - **City:** City where the cost center is located. This is completed automatically based on the postal code entered.
+    - **State:** State where the cost center is located. This is completed automatically based on the postal code entered.
+    - **Recipient:** Name of the person who will receive the orders at the address provided.
+4. Click the `Add` button.
+
+![Adiconar organização- EN](//images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/9f298b8d96c542d3c45aadef5cc67b80/Adiconar_organiza__o-_EN.gif)
+
+## Email notifications
+
+The **B2B Organizations** app provides a set of email templates that are automatically triggered based on specific changes and sent to the organization's users.
+
+| Template name               | Recipient                             | Trigger                                                 |
+|-----------------------------|---------------------------------------|---------------------------------------------------------|
+| Organization Created        | Users with Sales Admin profile        | When the organization is created.                       |
+| Organization Approved       | Users with Organization Admin profile | When the request to create an organization is approved. |
+| Organization Declined       | Users with Organization Admin profile | When the request to create an organization is denied.   |
+| Organization Status Changed | Users with Organization Admin profile | When the organization's status changes.                 |
+
+To view or customize any of these templates, follow the steps below:
+
+1. In the VTEX Admin, go to Store Settings > Email Templates > Templates.
+
+2. In the search bar, type Organization.
+
+3. Click the template you want to view or edit.
+
+4. Make the desired changes to the template.
+
+5. Click `Save`.
+
+To learn more about editing email templates, see [How to create and edit transactional email templates](https://help.vtex.com/en/tracks/transactional-emails--6IkJwttMw5T84mlY9RifRP/335JZKUYgvYlGOJgvJYxRO).
+
diff --git a/docs/tutorials/en/managing-credit-with-customer-credit.md b/docs/tutorials/en/managing-credit-with-customer-credit.md
index 84b89b40e..2e0377b6d 100644
--- a/docs/tutorials/en/managing-credit-with-customer-credit.md
+++ b/docs/tutorials/en/managing-credit-with-customer-credit.md
@@ -75,11 +75,11 @@ For a small number of registrations, the customer can create accounts one by one
 - Email
 - Credit limit
 
-![CustomerCredit1-EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5nCFYt3M86PvAR6XYQkOjM/3dbfd3dcd28b1f6463be48f237092636/CustomerCredit1-EN.png_h_250)
+![CustomerCredit1-EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5nCFYt3M86PvAR6XYQkOjM/3dbfd3dcd28b1f6463be48f237092636/CustomerCredit1-EN.png_h_250)
 
 If the database has a large number of accounts, it is best to import a spreadsheet in CSV format. You can download a template in the Accounts section and fill it with the required information. To do this, click on the Import button.
 
-![CustomerCredit2-EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3dOP4y1k14B70DhB07n7zx/f2bd8cb4463b5132c176875373b5daf7/CustomerCredit2-EN.png_h_250)
+![CustomerCredit2-EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3dOP4y1k14B70DhB07n7zx/f2bd8cb4463b5132c176875373b5daf7/CustomerCredit2-EN.png_h_250)
 
 ### Large databases
 
diff --git a/docs/tutorials/en/managing-delivery-capacity.md b/docs/tutorials/en/managing-delivery-capacity.md
index 0e0db0a40..6aab4b6c8 100644
--- a/docs/tutorials/en/managing-delivery-capacity.md
+++ b/docs/tutorials/en/managing-delivery-capacity.md
@@ -3,8 +3,8 @@ title: 'Managing delivery capacity'
 id: 2y217FQZCjD0I1n62yxVcz
 status: PUBLISHED
 createdAt: 2021-04-19T14:43:24.606Z
-updatedAt: 2023-03-24T20:39:18.594Z
-publishedAt: 2023-03-24T20:39:18.594Z
+updatedAt: 2024-03-25T20:04:31.192Z
+publishedAt: 2024-03-25T20:04:31.192Z
 firstPublishedAt: 2021-05-24T17:00:14.134Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,25 +15,25 @@ legacySlug: managing-delivery-capacity
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
-You can track the availability of delivery windows and the number of items/orders that can still be placed in each delivery window on the **Delivery capacity** page.
+You can track the availability of delivery windows and the number of items/orders that can still be placed in each delivery window on the **Delivery capacity** page. 
 
-<div class="alert alert-warning"> 
-To manage your delivery capacity, you must previously configure your shipping policies and enable scheduled deliveries. To learn how to do that, check out the articles <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy</a> and <a href="https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a>.
-</div>
+To manage your **Delivery capacity**, you must previously configure your [shipping policies](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) and enable [scheduled deliveries](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi). 
 
-In the Admin, go to **Shipping > edit or create a Shipping Policy > Delivery capacity section of the form**.
+<div class="alert alert-warning">
+For <a href="https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a> and <a href="https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Delivery capacity</a> to perform correctly, you must follow the rules below:<p><ul><li>The result from {<a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {shipping policy ID} cannot exceed 60 characters.</li><li>Do not use spaces in <a href="https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">shipping policy IDs</a>.</li></ul></p>
+</div>
 
-The Delivery capacity page displays a list of your store's delivery windows. The list is based on the shipping policy selected in the Shipping policy filter and the time frame specified in the Date filter.
+In the VTEX Admin, go to **Shipping > Delivery capacity**, or type **Delivery capacity** in the search bar at the top of the page. The **Delivery capacity** displays a list of your store's delivery windows. The list is based on the shipping policy selected in the `Shipping policy` filter and the time frame specified in the `Date` filter.
 
 Once you have selected a shipping policy and a date, you will see the delivery windows available for those specifications. Each row in the list represents a delivery window and displays the following data:
 
-*   **Delivery date**: the dates available for delivery.
-*   **Delivery time**: the times available for delivery.
+*   **Delivery Date**: the dates available for delivery.
+*   **Delivery Time**: the times available for delivery.
 *   **Capacity**: the total delivery capacity.
 *   **Booked**: the number of items/orders already booked (purchase confirmed, not payment).
 *   **Available**: number of items/orders that can still be scheduled (the total capacity minus the booked items).
 *   **Status**: classified as visible or not visible, depending on the availability of the delivery window. The delivery window will be shown as visible for your customers if its capacity hasn’t been reached yet.
 
-<div class="alert alert-warning"> 
+<div class = "alert alert-info">
 By clicking on <b>EDIT SHIPPING POLICY</b>, you’ll be redirected to the shipping policy page selected in the Shipping policy filter, where you can edit it.
 </div>
diff --git a/docs/tutorials/en/managing-http-headers.md b/docs/tutorials/en/managing-http-headers.md
new file mode 100644
index 000000000..537e8fcb3
--- /dev/null
+++ b/docs/tutorials/en/managing-http-headers.md
@@ -0,0 +1,65 @@
+---
+title: 'Managing HTTP headers'
+id: 2cCTvwQR3Z4ENVKMJU6NK3
+status: PUBLISHED
+createdAt: 2024-06-07T17:58:18.041Z
+updatedAt: 2024-06-07T18:40:52.927Z
+publishedAt: 2024-06-07T18:40:52.927Z
+firstPublishedAt: 2024-06-07T18:40:52.927Z
+contentType: tutorial
+productTeam: Reliability
+author: YRJ73j8mt38D5TUleocQB
+slug: managing-http-headers
+locale: en
+legacySlug: managing-http-headers
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+The HTTP (Hypertext Transfer Protocol) is a fundamental communication protocol used to transfer data on the World Wide Web. It operates on the client-server model, where clients such as web browsers request resources like web pages from web servers. These requests are exchanged in message format, following a set of rules and standards defined by the protocol.
+
+Headers play a crucial role in HTTP communication, providing additional information about the ongoing transaction. There are two main types of headers: 
+
+- __Request Headers:__ Sent by the client to the server. They contain information about the request made, such as the type of HTTP method used, the type of accepted content, cookies, among others.
+- __Response Headers:__ Sent by the server to the client. They provide information about the sent response, such as the response status, type of returned content, cookies, among others.
+
+<div class = "alert alert-info">
+For more information, refer to the <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP">MDN’s HTTP</a> guide and related documentation.
+</div>
+
+In this guide, you will learn how to manage Security Response Headers in your Store Framework store.
+## Security Response Headers
+
+In Store Framework stores, if you need to add or change the value of a Security Response Header, open a ticket to [VTEX Support](https://help.vtex.com/en/support).
+
+Below, check the headers that accept editing:
+
+- [**X-Frame-Options**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options): Allows the control of how websites can be incorporated into other ones through the use of frames. This header is a security measure to protect users against [click-jacking](https://developer.mozilla.org/en-US/docs/Web/Security/Types_of_attacks#click-jacking) attacks, which occur when an attacker tricks users into clicking on something on a web page without their consent.
+- [**X-Content-Type-Options**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options): Protects against [MIME](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types) vulnerabilities, which can occur when a website allows users to upload content to a site.
+- [**Content-Security-Policy (CSP)**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy): Allows the control the resources the user agent can load in a given page, helping against [cross-site scripting](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting) attacks.
+- [**Strict-Transport-Security (HSTS)**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security): Informs browsers that the site should only be accessed using HTTPS.
+- [**X-XSS-Protection**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection): Instructs browsers on how to handle cross-site scripting (XSS) attacks, activating the integrated filter to block malicious scripts from executing in the user’s browser.
+- [**Referrer-Policy**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy): Determines which origin page information is shared with the destination page in HTTP requests. It is essential to protect user privacy and website security.
+
+## Custom headers
+
+It is possible to configure a custom header, which is a value that is not standardized and is specific to the store's particular requirements or functionalities.
+
+<div class="alert alert-warning">
+Each account is limited to adding a single custom header.
+</div>
+
+If you need to configure a custom header, open a ticket to the VTEX Support, providing the keys and values to be set, as you are entirely responsible for this information. To guide you, refer to the MDN’s documentation about [Headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers). 
+
+Below, see an example of a custom header:
+
+```json
+"customHeader": {
+   "key": "Strict-Transport-Security",
+   "value": "max-age=31536000; includeSubdomains; preload"
+ }
+```
+
+The value `max-age=31536000; includeSubdomains` in the context of the Strict-Transport-Security (HSTS) header represents the maximum duration, in seconds, that the HSTS policy should be enforced by the browser for a specified domain and its subdomains.
+
+The `preload` directive indicates that the domain should be included in the HSTS preload list, which ensures that compliant browsers will only connect via HTTPS, even for the initial request.
+
diff --git a/docs/tutorials/en/managing-page-and-template-content.md b/docs/tutorials/en/managing-page-and-template-content.md
index 27f1d70a1..6224e8027 100644
--- a/docs/tutorials/en/managing-page-and-template-content.md
+++ b/docs/tutorials/en/managing-page-and-template-content.md
@@ -32,7 +32,7 @@ In the VTEX Admin:
 
 1. Select the block to which you desire to create a new content. You can select it using the list on your right corner or through the interface:
 
-![seta-interface-en](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
+![seta-interface-en](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
 
 2. Click on `Versions` on your top-right corner.
 
@@ -59,7 +59,7 @@ The Site Editor applies content configurations according to the parameter hierar
 
 1. Select the desired block whose content will be overwritten. You can select it using the list on your right corner or through the interface:
 
-![seta-interface-en](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
+![seta-interface-en](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
 
 2. The available content is from the current active one. Edit the fields with the new values or click on `Versions` to edit other contents' configurations. 
 3. Save your changes.
@@ -72,7 +72,7 @@ Contents derived from the source code, i.e., the Store Theme app, can not have t
 
 1. Select the desired block whose content will be deleted or reset. You can select it using the list on your right corner or through the interface:
 
-![seta-interface-en](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
+![seta-interface-en](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
 
 2. Click on `Versions` on your top-right corner. 
 3. Click on the desired content's kebab menu (three points). 
diff --git a/docs/tutorials/en/managing-pages.md b/docs/tutorials/en/managing-pages.md
index 898e4eae7..dc72577ce 100644
--- a/docs/tutorials/en/managing-pages.md
+++ b/docs/tutorials/en/managing-pages.md
@@ -3,8 +3,8 @@ title: 'Managing Pages in the Headless CMS'
 id: 3DO6rBhZ1p3zndnFu5BgRt
 status: PUBLISHED
 createdAt: 2023-03-23T19:46:08.568Z
-updatedAt: 2023-04-25T19:19:08.542Z
-publishedAt: 2023-04-25T19:19:08.542Z
+updatedAt: 2024-06-17T12:55:20.070Z
+publishedAt: 2024-06-17T12:55:20.070Z
 firstPublishedAt: 2023-03-23T20:06:47.380Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,16 +15,36 @@ legacySlug: managing-pages-beta
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-In **Headless CMS**, you can find all your store’s website URL routes and page templates: `Global Alert Page` `Page`,`Product Page`. You can also create and link custom pages to predefined templates and manage pages created directly in the source code of your storefront project.
+In **Headless CMS**, you can manage all the URL routes and page templates for your store's website, including the `Global Alert Page` `Page`,`Product Page`. You can also create and link custom pages to predefined templates and manage pages created directly in the source code of your storefront project.
 
-Follow the instructions below to create and manage a page:
-![Pages](https://images.ctfassets.net/alneenqid6w5/6rzTf5xTBpR3P8sUonA0Ms/859e7a998e9ebc681c8bc5e2983e1777/pages_um.png)
+## Overview
+
+![New pages](//images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/7171a74a194bd96221f481de02d5599f/new_pages_-_en.png)
+
+| Option         | Description                                           |
+| -------------- | ----------------------------------------------------- |
+| Create Document   | Creates a new page based on the options available, e.g., `Product Page` or `Home`.  |
+| Settings (⚙️)  | Opens a modal that displays project configurations organized into three tabs: <ul><li>**General:** Edits the project ID and API settings or archives the project.</li> <li>**Content-Types:** Saves the content types created in the source code in the Headless CMS. **{Qual o significado dessa tela?}**</li> <li>**Build:** Connects the CMS project with your code source through webhooks by setting up the content types and sections. </li></ul>       |
+| Search      | Searches specific pages within the project. |
+| Status      | Filters the pages according to their status: <ul><li><code>Published</code>: Pages that are published and already available in the live store.</li> <li><code>Draft</code>: Pages that are in draft with work in progress and haven't been published yet.</li></ul> |
+| Type      | Filters the pages according to their content type. The content types are defined in your store code. For more information, see [Adding Content Types to the Headless CMS](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-2-adding-content-types-to-the-headless-cms). |
+
+## Creating a new page
+
+To create and manage a page, follow these steps:
 
 1. In your VTEX Admin, access **Headless CMS**.
-2. Click `CREATE NEW` and select the desired page. 
-3. Click <i class="fa-solid fa-circle-plus"></i> and choose a section.
-![Gif - Pages](https://images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/d35ca90a8b65f2f436173375fee0bf9d/Ingles_gif_da_pag.gif)
-4. Name the page and fill in the fields.
-5. Click `Publish`. 
+<div class="alert alert-warning">
+  Make sure you are in the correct project. If not, go to the <b>Project</b> menu in the upper left corner, select the name of the project where you want to create the page, and continue to step 2.
+</div>
+2. Click `Create document` and select the desired page type. 
+
+3. Under `Untitled`, name the page.
+
+4. Click on `Sections` and select the desired section.
+![Gif - Pages](//images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/d35ca90a8b65f2f436173375fee0bf9d/Ingles_gif_da_pag.gif)
+5. Add more sections if needed and fill them out.
+
+6. Click `Publish`. 
 
-By clicking <i class="fa-solid fa-ellipsis-vertical"></i>, you can choose to `Duplicate` your page or `Delete` it. 
+To duplicate or delete the page, click on the **More actions** menu (`⋮`) of the page.
diff --git a/docs/tutorials/en/managing-placeholders.md b/docs/tutorials/en/managing-placeholders.md
index fc98b5148..f6fd9b0f8 100644
--- a/docs/tutorials/en/managing-placeholders.md
+++ b/docs/tutorials/en/managing-placeholders.md
@@ -35,14 +35,14 @@ It creates a configurable element in the part of the code where it is inserted.
 
 It is important to enter an `id` value. It will be the identifier of that placeholder in the system.
 
-![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configuring the placeholder
 
 Once the placeholder control has been inserted into the template, you can configure it in the settings of the layout that uses this template.
 
 1. Open the layout and then click on the **Settings** tab. The new placeholder should appear there, with the name equal to the id value defined in the control. For now, this placeholder is empty, meaning there are no objects inside it.
-![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. To insert an object, click on **add object**.
 3. Then choose the object type and click on the **Add** button.
 4. Finally, click on the **Save Settings** button.
@@ -51,7 +51,7 @@ You can now edit the object inserted in the placeholder.
 
 To do this, click on the pencil icon inside the object, and then click on **add content**.
 
-![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 You can now name this object, upload images to it and configure the conditions under which it will be rendered.
 
diff --git a/docs/tutorials/en/managing-projects.md b/docs/tutorials/en/managing-projects.md
new file mode 100644
index 000000000..83f26779a
--- /dev/null
+++ b/docs/tutorials/en/managing-projects.md
@@ -0,0 +1,129 @@
+---
+title: 'Managing Projects'
+id: 42IpDFqTVTESH8DCypJMPM
+status: PUBLISHED
+createdAt: 2023-11-01T13:45:57.091Z
+updatedAt: 2024-06-21T14:14:20.212Z
+publishedAt: 2024-06-21T14:14:20.212Z
+firstPublishedAt: 2023-11-01T19:38:50.237Z
+contentType: tutorial
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: managing-projects
+locale: en
+legacySlug: managing-projects
+subcategory: 27t6x0lngvjI3bnUg5AgEO
+---
+
+Projects is a feature in the VTEX Headless CMS that simplifies the management of multiple frontend projects like mobile apps, websites, and email marketing from one control panel.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
+
+Each project is customized with its own settings, content, and branding according to specific audiences or purposes. 
+
+In this guide, you will learn how to manage each frontend project of your store.
+
+<div class="alert alert-warning">
+  <a href="https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview"> FastStore WebOps users</a>: Changes made through the Headless CMS in VTEX Admin, such as creating new content types, adding sections, or updating fields, may not automatically appear in the storefront once you publish them. This is a known issue, and you should contact your development team to implement the necessary workaround. For detailed instructions, refer to the <a href="https://help.vtex.com/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW"> WebOps app is not fully integrated with Headless CMS</a> known issue article.
+</div>
+
+## Before you begin
+For the Headless CMS management, make sure the [resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar`, `Settings*`, and `CMS GraphQL API` are associated with your [user role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Otherwise, [create a custom user role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role) and add these resources to it or add these resources to an existing user role.
+
+## Overview
+To access **Projects**, go to the VTEX Admin and access **Storefront > Headless CMS**.
+
+![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c7ccee21dc6cae85a41886c49d9a3d8f/projects-two-en.png)
+
+| Option         | Description                                           |
+| -------------- | ----------------------------------------------------- |
+| Project card   | Opens the selected project, allowing you to create and edit pages for the project content.      |
+| Settings (⚙️)  | Opens a modal that displays project configurations organized into three tabs: <ul><li>**General:** Edits the project ID and API settings or archives the project.</li> <li>**Content-Types:** Connects the Headless CMS project with your code source through webhooks by setting up the content types and sections.</li> <li>**Build:** Initiates and manages website builds. Set a webhook URL for build notifications and an endpoint to preview the page versions. </li></ul>| 
+| Create new       | Opens a page to configure a new project from scratch. |
+
+## Creating a new project
+
+Create a new project for your store by setting general settings such as **Project ID**. To effectively connect a Headless CMS project with your project's source code, you will also need to set up webhooks and build settings such as *Build Webhook URL* and *Preview URL*. 
+
+A webhook is an HTTP endpoint that enables automated communication between the VTEX Headless CMS and the project's source code. For example, it allows the CMS to notify a FastStore project of content changes or other events, triggering actions like real-time content synchronization.
+
+1. In the **Projects** page, click `Create new`.
+2. In the **New project** page, fill in the fields according to the [Project settings](#project-settings) section.
+3. After setting each field of the page, click `Create` and a successful message will appear on the screen.
+
+Once you have created a new project, you can create pages for it with all the URL routes and corresponding page templates of your store’s website, such as home, product, and login pages. 
+
+To create a new page, follow the steps in [Managing Pages in the Headless CMS](https://help.vtex.com/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt)
+
+## Project settings
+The Project settings allow you to configure your project according to three main categories:
+
+- [General](#general): Edits the project ID, API settings and archives the project.
+- [Content-Types](#content-types): Connects the Headless CMS project with your code source through webhooks by setting up the content types and sections. 
+- [Build](#build): Initiates and manages website builds. Set a webhook URL for build notifications and an endpoint to preview the page versions.
+
+### General
+
+| Field name             | Description           | Value example     |
+| ---------------------- | --------------------- | ----------------- |
+| Project ID (mandatory) | ID of the project.    | E.g., `faststore`       |
+| Storefront      | Defines the VTEX storefronts available (`FastStore` or `Custom`) and their purpose.  | See the [Storefront](#storefront) section for more information. |
+
+#### Storefront
+
+This field determines the [build](#build) configuration settings based on your chosen storefront. Options include:
+
+- **VTEX Storefronts**:
+
+Choose a storefront from your account (e.g., FastStore). [Build](#build) automatically adjusts based on the storefront chosen. You can still customize them later.
+
+- **Custom**
+   Choosing a `Custom` storefront gives you the flexibility to define your own [build](#build) settings.
+
+### Content-Types
+
+| Field name             | Description           | Value example     |
+| ---------------------- | --------------------- | ----------------- |
+| Sections URL | Webhook URL for receiving and saving the sections created in the source code in the Headless CMS. | E.g., `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{projectId}/sections`       |
+| Content types URL       | Webhook URL for receiving and saving the content types created in the source code in the Headless CMS.       | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/content-types`       |
+
+### Build
+
+| Field name             | Description           | Value example     |
+| ---------- | ---------- | ---------- |
+| Sections URL      | Webhook URL for receiving and saving the sections created in the source code in the Headless CMS.       | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/sections`      |
+| Content types URL       | Webhook URL for receiving and saving the content types created in the source code in the Headless CMS.       | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/content-types`       |
+| Build Webhook URL      | Webhook URL for starting a new build in the Headless CMS when a page or content is added or edited. | `https://app.io.vtex.com/vtex.cms-builder-sf-jamstack/v1/{accountName}/{workspace}/build-releases` |
+| Save Webhook* URL       | Webhook URL for enabling real-time previews of the project by notifying you to refresh the page to reflect the latest changes in the Headless CMS.      | -      |
+| Preview URL      | Webhook URL that provides the preview for pages in the Headless CMS.       | `https://{accountName}.vtex.app/api/preview`      |
+
+## Editing a project
+After creating the project, you can also edit all the information you have set during the [creation of it](#creating-a-new-project).
+have set during the [creation of it](#creating-a-new-project).
+On the Projects main page, click Settings (⚙️), and a modal window will open with two tabs for [General](#general) and [Build](#build) settings.
+
+### Restoring default Sections URL
+
+Once you have [created the project](creating-a-new-project) and want to edit the [**Sections URL**](#content-types) field click `Edit`, add the new webhook URL and click `Save`. If you want to restore the default URL, click `Restore default`.
+
+## Archiving a project
+Archiving a project disables the API and access to the content within the project. 
+To archive a project, follow the steps below:
+
+1. Go to **Storefront > Projects**.
+2. Choose the project you want to archive and click **Settings** (⚙️) to open a modal.
+3. Click `Archive project` on the `General` page. A pop-up message will appear to confirm that you want to archive the project.
+![Archive project](//images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/018e5e76e204d63fd86fdb9abe8ee82c/projects-three-en.png)
+4. Click `Archive`. A message informing that the project was successfully archived will appear.
+
+If you want to restore an archived project, follow the steps in [Restoring a project](#restoring-the-project).
+
+### Restoring a project
+Restoring a project re-enables its API and allows the content within the project to be accessible once again.
+To restore the project, follow the steps below:
+
+1. Go to **Storefront > Projects**.
+2. Click the archived project card.
+3. Click `Restore project`. A pop-up message will appear to confirm if you want to restore the project.
+4. Click `Restore`. A message informing that the project was successfully restored will appear.
+
diff --git a/docs/tutorials/en/managing-redirects-per-binding.md b/docs/tutorials/en/managing-redirects-per-binding.md
index 5d26df5a7..e9ac20e1a 100644
--- a/docs/tutorials/en/managing-redirects-per-binding.md
+++ b/docs/tutorials/en/managing-redirects-per-binding.md
@@ -3,8 +3,8 @@ title: 'Managing URL redirects per binding'
 id: 67GAK2TCQgjvmtPXxAqREb
 status: PUBLISHED
 createdAt: 2021-04-20T15:03:54.330Z
-updatedAt: 2023-03-24T22:20:43.304Z
-publishedAt: 2023-03-24T22:20:43.304Z
+updatedAt: 2023-09-04T12:42:32.729Z
+publishedAt: 2023-09-04T12:42:32.729Z
 firstPublishedAt: 2021-05-05T18:11:25.521Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -21,12 +21,16 @@ Multi-domain stores commonly ask for redirect management per [binding](https://h
 
 Taking this into consideration, VTEX enables you to manage your URL redirects according to the store bindings through the admin interface.
 
+<div class="alert alert-warning" role="alert">
+To create, edit, or remove redirects, the Admin user must have a role that has the <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager</a> <strong>CMS Settings</strong> resource. You can grant the user a role with the resource by following the instructions in the <a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512#editing-users">How to manage users</a> article or create a new role including the resource by following the instructions in the <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role">Roles</a> article.
+</div>
+
 In VTEX Admin:
 
 1. Access **Storefront > Pages**.
 2. Click on the `Redirects` tab.
 
-![en-redirecttab](https://images.ctfassets.net/alneenqid6w5/7G20PhFKWBFNKmvN2T8MFo/4b88bd44abc30aa3af4e0f9ca8557e3e/new-redirect.png)
+![en-redirecttab](//images.ctfassets.net/alneenqid6w5/7G20PhFKWBFNKmvN2T8MFo/4b88bd44abc30aa3af4e0f9ca8557e3e/new-redirect.png)
 
 ## Manually creating redirects
 
@@ -36,7 +40,7 @@ In VTEX Admin:
 4. Check whether your redirect will be permanent or temporary — in case it is temporary, you can toggle the `This redirect has an end date` button to set an end date for it. 
 5. Save your changes.
 
-![en-novoredirect](https://images.ctfassets.net/alneenqid6w5/4CdPssJV4wAfbvr0ZB2ugi/2d3efd147908ec9e1da471403cba2cf9/redirect-novo.png)
+![en-novoredirect](//images.ctfassets.net/alneenqid6w5/4CdPssJV4wAfbvr0ZB2ugi/2d3efd147908ec9e1da471403cba2cf9/redirect-novo.png)
 
 ## Manually deleting redirects
 
@@ -44,7 +48,7 @@ In VTEX Admin:
 2. Click on the `Remove` button.
 3. Confirm your action. 
 
-![en-remove-redirect](https://images.ctfassets.net/alneenqid6w5/4Ki1noxgrPgStT4wZGbrCk/7de9c0c5b3a4b9c734657c96ae20cccf/remove-redirect.png)
+![en-remove-redirect](//images.ctfassets.net/alneenqid6w5/4Ki1noxgrPgStT4wZGbrCk/7de9c0c5b3a4b9c734657c96ae20cccf/remove-redirect.png)
 
 <div class="alert alert-warning">
 A bug may be found when trying to click on redirects with query strings. The VTEX product team is already aware of this unexpected behavior and working on the fix. If you cannot click on the desired redirect to delete it, opt to do it through the spreadsheet while the issue is not resolved. 
@@ -73,7 +77,7 @@ The spreadsheet's inputs will be mandatorily created or deleted from the store's
 4. Click on the `Import` button.
 5. Check the `Save` or the `Delete` button according to your scenario.
 
-  ![en-redirect-planilha](https://images.ctfassets.net/alneenqid6w5/1LA0kpUcu5NhfUgWWhkjea/b83ae63b44fa2367877b00daf47467c7/redirect-planilha.png)
+  ![en-redirect-planilha](//images.ctfassets.net/alneenqid6w5/1LA0kpUcu5NhfUgWWhkjea/b83ae63b44fa2367877b00daf47467c7/redirect-planilha.png)
 
   <div class="alert alert-warning">
 By clicking on the <code>Save</code> button, you will create all the redirects listed in your spreadsheet, whereas clicking on the <code>Delete</code> button will remove all of them from your store's redirect database.
diff --git a/docs/tutorials/en/managing-shipping-policies.md b/docs/tutorials/en/managing-shipping-policies.md
new file mode 100644
index 000000000..770714923
--- /dev/null
+++ b/docs/tutorials/en/managing-shipping-policies.md
@@ -0,0 +1,114 @@
+---
+title: 'Managing shipping policies'
+id: 30nynylgbWieimhaMtGTIE
+status: PUBLISHED
+createdAt: 2024-01-30T16:15:33.582Z
+updatedAt: 2024-01-31T13:48:35.723Z
+publishedAt: 2024-01-31T13:48:35.723Z
+firstPublishedAt: 2024-01-31T00:54:58.302Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: managing-shipping-policies
+locale: en
+legacySlug: managing-shipping-policies
+subcategory: 7fTH6bP0C4IaM8qWi0kkQC
+---
+
+[Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) is a set of rules and settings that define the shipping options displayed to customers at checkout. The relationship between shipping policy, [warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb), and [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) makes up your [shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) on VTEX, as shown in the image below:
+
+![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
+
+This article explains how to monitor and manage your shipping policies. In the VTEX Admin, under **Shipping > Shipping Strategy**, the **Shipping Policies** tab is where you can do the following:
+
+* [View the shipping policy list](#viewing-the-shipping-policy-list)
+* [Search for shipping policies](#searching-for-shipping-policies)
+* [Filter shipping policies](#filtering-shipping-policies)
+* [View the carrier dashboard (optional)](#viewing-the-carrier-dashboard-optional)
+* [Edit shipping policies](#editing-shipping-policies)
+* [Activate or deactivate shipping policies](#activating-or-deactivating-shipping-policies)
+* [Delete shipping policies](#deleting-shipping-policies)
+
+You can also create shipping policies. Read the instructions in the [Creating a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) article.
+
+## Viewing the shipping policy list
+
+In the VTEX Admin, by going to **Shipping > Shipping Strategy** in the **Shipping Policies** tab, you will see a list as shown in the image below:
+
+![shipping_policy_EN](//images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/68d66c99a43db25f4e297fbc238f0375/shipping_policy_EN.png)
+
+The information displayed on this page is described in the table below:
+
+| **Column** | **Description** |
+| :---: | :--- |
+| Shipping Policy | Name that identifies your [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) for users with access to your VTEX Admin. Learn more in the [Creating a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) article. |
+| Shipping Method | <p><a href="https://help.vtex.com/en/tutorial/como-funciona-o-tipo-de-envio--tutorials_126">Shipping method</a> is the name you set in the shipping policy displayed to customers at checkout. Thus, you should use intuitive names when creating a shipping policy.</p><p>Example: `Express shipping` and `Standard shipping`.</p> |
+| Loading Docks | Identifies which [loading docks](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) are associated with the [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140). When you hover over the number in this column, you will see the names of all the loading docks associated with the shipping policy. |
+| Status | <p>Shipping policy activation status, which can be:</p><p><ul><li><b>Active:</b> The shipping policy is activated and valid for the order shipping <a href="https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116">calculation</a>.</li><li><b>Inactive:</b> The shipping policy is deactivated and not valid for shipping.</li></ul></p> |
+| Carrier (Brazil only) | This field only appears in the VTEX Admin for stores that have activated the [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) or requested the [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs). It uniquely identifies Correios. |
+| Contract (Brazil only) | <p>This field only appears in the VTEX Admin for stores that have activated the <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa">VTEX Shipping Network Correios</a>.</p><p>Possible values are:</p><p><ul><li><b>VTEX:</b> The store has requested a Correios price list intermediated by VTEX.</li><li><b>Store:</b> The store requested a price list on its own before activating the VTEX Shipping Network Correios.</li></ul></p> |
+
+## Searching for shipping policies
+
+In the search box with the magnifying glass icon <i class="fas fa-search"></i>, you can search for shipping policies by name. Typing a character into the search bar immediately initiates the search. To clear the search, click the close icon <i class="far fa-times-circle"></i>.
+
+<div class = "alert alert-info">
+If the search does not return any results, check the spelling used in the search and if a filter has been selected.
+</div>
+
+## Filtering shipping policies
+
+You can filter shipping policies by their status, which can be `Active` or `Inactive`. See the steps below:
+
+1. In the VTEX Admin, go to **Shipping > Shipping Strategy** or type **Shipping Strategy** in the search bar at the top of the page.
+2. In the **Shipping policies** tab, click `Status`.
+3. Select one of the status options:
+    * **Active:** The shipping policy is activated and valid for the order shipping [calculation](https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116).
+    * **Inactive:** The shipping policy is deactivated and not valid for shipping. 
+4. Click `Apply`.
+
+To remove the applied filter, click `Status` and then `Clear`.
+
+### Filter for contract types (Brazil only)
+
+Stores that have requested the [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) or activated the [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) can search by contract type:
+
+  * `VTEX`: The store has requested a Correios price list intermediated by VTEX.
+  * `Store`: The store has directly requested the Correios price list.
+
+## Viewing the carrier dashboard (optional)
+
+Stores that have requested the [VTEX Shipping Network](https://help.vtex.com/en/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) or activated the [VTEX Shipping Network Correios](https://help.vtex.com/en/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) will see the "Carriers Dashboard" button on the **Shipping Policies** page. By clicking it, the user will be redirected to the [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92) dashboard, where they can manage the carrier operations for their products.
+
+## Editing shipping policies
+
+To edit a shipping policy, follow the steps below:
+
+1. In the VTEX Admin, go to **Shipping > Shipping Strategy** or type **Shipping Strategy** in the search bar at the top of the page.
+2. In the **Shipping Policies** tab, in the row for the shipping policy you want, click the menu icon <i class="fas fa-ellipsis-v"></i>. You can [search](#searching-for-shipping-policies) for policies or [filter by](#filtering-shipping-policies) certain criteria.
+3. Click `Edit`.
+4. Make the desired changes. For more information on the fields, read the [Creating a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) article.
+5. Click `Save Changes`.
+
+## Activating or deactivating shipping policies
+
+To activate or deactivate a shipping policy, follow the steps below:
+
+1. In the VTEX Admin, go to **Shipping > Shipping Strategy** or type **Shipping Strategy** in the search bar at the top of the page.
+2. In the **Shipping Policies** tab, in the row for the shipping policy you want, click the menu icon <i class="fas fa-ellipsis-v"></i>. You can [search](#searching-for-shipping-policies) for policies or [filter by](#filtering-shipping-policies) certain criteria.
+3. Click `Activate` or `Deactivate`.
+4. In the modal that opens, click `Activate` or `Deactivate` again.
+
+## Deleting shipping policies
+
+To delete a shipping policy, follow the steps below:
+
+<div class="alert alert-danger">
+Deleting a shipping policy is permanent and cannot be undone.
+</div>
+
+1. In the VTEX Admin, go to **Shipping > Shipping Strategy** or type **Shipping Strategy** in the search bar at the top of the page.
+2. In the **Shipping Policies** tab, in the row for the shipping policy you want, click the menu icon <i class="fas fa-ellipsis-v"></i>. You can [search](#searching-for-shipping-policies) for policies or [filter by](#filtering-shipping-policies) certain criteria.
+3. Click `Delete`.
+4. In the modal that opens, click `Delete` again.
+
diff --git a/docs/tutorials/en/managing-singleton-content-types.md b/docs/tutorials/en/managing-singleton-content-types.md
index 8d3258338..2558f3c73 100644
--- a/docs/tutorials/en/managing-singleton-content-types.md
+++ b/docs/tutorials/en/managing-singleton-content-types.md
@@ -3,8 +3,8 @@ title: 'Managing Singleton content types'
 id: VBibMN1BqV2OFmavUFCdo
 status: PUBLISHED
 createdAt: 2023-04-05T17:55:26.748Z
-updatedAt: 2023-04-06T19:11:57.614Z
-publishedAt: 2023-04-06T19:11:57.614Z
+updatedAt: 2024-06-05T19:07:02.549Z
+publishedAt: 2024-06-05T19:07:02.549Z
 firstPublishedAt: 2023-04-06T19:11:57.614Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -18,10 +18,10 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 Singleton content types allow creating and managing a single page, ensuring that only one page of this content type exists in Headless CMS.
 
 This content type avoids potential conflicts and inconsistencies when multiple pages of the same content type are created. For example, you can use Singleton for your store's Home page to ensure that there is only one Home page and that all updates and requests to this page always return the same result.
-![singleton-en](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
+![singleton-en](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-  To create the Singleton content type, check with your developer team if the <i>isSingleton</i> property is implemented or ask them to follow the instructions in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using `isSingleton` in a content type</a> to add it to the desired content type.
+<div class="alert alert-warning">
+  To create the Singleton content type, check with your developer team if the <i>isSingleton</i> property is implemented or ask them to follow the instructions in <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> to add it to the desired content type.
 </div>
 
 ## Creating the Singleton
@@ -29,19 +29,32 @@ This content type avoids potential conflicts and inconsistencies when multiple p
 2. Select `CREATE NEW` and choose the name of the singleton content type, for example, **Home**.
 3. Edit the page as you desire using new sections.
 
-<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
 You can only create the Singleton once. The Singleton page will not be displayed in the content type list if it already exists.
 </div>
 
 ## Editing the Singleton
 1. Access the **Admin > Storefront > Headless CMS**.
-2. Select the Singleton that you created, for example, **Home**.
-3. On the **Home** page, edit as you desire by adding new sections.
+2. Click on the project where the Singleton were created.
+3. Select the Singleton that you created, for example, **Home**.
+4. On the **Home** page, edit as you desire by adding new sections.
+
+## Unpublishing the Singleton
+1. Access the **Admin > Storefront > Headless CMS**.
+2. Click the project where the Singleton was created.
+3. Click `Unpublish` > `Unpublish Now`.
+
+<div class="alert alert-warning">
+Before unpublishing, make sure there are no existing drafts. Otherwise, you won't be able to proceed. If you have drafts, either delete them or schedule them for publication.
+</div>
+
+4. A modal will display for you to confirm the unpublishing of the page.
+5. Click and hold `UNPUBLISH` to unpublish content.
 
 ## Deleting the Singleton
 1. On the Singleton page, select `more`(kebab menu) and choose `Delete`.
 2. Choose`DELETE` and `BACK TO PAGES`. 
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
   If you want to restore the page and its content, click <i>RESTORE</i>.
 </div>
diff --git a/docs/tutorials/en/managing-stock-items.md b/docs/tutorials/en/managing-stock-items.md
index 2d591b4de..1941045c3 100644
--- a/docs/tutorials/en/managing-stock-items.md
+++ b/docs/tutorials/en/managing-stock-items.md
@@ -3,8 +3,8 @@ title: 'Inventory management'
 id: tutorials_139
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:21.085Z
-updatedAt: 2023-03-31T00:44:36.047Z
-publishedAt: 2023-03-31T00:44:36.047Z
+updatedAt: 2024-04-18T15:25:20.097Z
+publishedAt: 2024-04-18T15:25:20.097Z
 firstPublishedAt: 2017-04-27T23:00:44.889Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,19 +15,9 @@ legacySlug: managing-stock-items
 subcategory: 3PQwnyOcNyYgawy06oe6gE
 ---
 
-At VTEX, inventory is the relationship between a store's sales items and the locations where those items are stored. Log in to the VTEX Admin and go to **Catalog > Inventory > Inventory Management** to view the SKUs registered in the [catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) and their respective [warehouses](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb).
+At VTEX, [warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) is the physical location where the store products are stored, and inventory is the relationship between the warehouses and the SKUs available for sale. To view the SKUs registered in your [catalog](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) and respective warehouses, in your VTEX Admin, access **Catalog > Inventory > Inventory Management**.
 
-Other possible actions in the **Inventory Management** page are:
-
-* [Tracking the item update history](https://help.vtex.com/en/tutorial/inventory-update-history--5AM7xbmMzmKSEQewakamc2).
-* [Checking if the SKUs have reserved units](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#how-to-track-reservation-status). 
-* [Updating the number of SKUs available for sale](https://help.vtex.com/en/tutorial/updating-the-quantity-of-items-in-inventory--2MDwYV1COA6YuoiY22AyGo).
-
-<div class="alert alert-info"> 
-Remember that <b>warehouse</b> is the physical location where the store products are stored, and <b>inventory</b> is the relationship between the warehouses and the SKUs available for sale.
-</div>
-
-This article contains information about the **Inventory Management** section in the VTEX Admin. Learn how:
+This article contains information about the **Inventory Management** page. Learn how:
 
 * [The inventory information is divided](#inventory-information).
 * [The search filters are organized to make it easier to find specific SKUs](#search-filters).
@@ -36,34 +26,39 @@ This article contains information about the **Inventory Management** section in
 To access the inventory using SKUs, loading docks, or warehouses via API, use the <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-"> Inventory API</a>.
 </div>
 
-## Inventory information
+Other possible actions in the **Inventory Management** page are:
 
-In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type **Inventory Management** in the search bar at the top of the page.
+* [Tracking the item update history](https://help.vtex.com/en/tutorial/inventory-update-history--5AM7xbmMzmKSEQewakamc2).
+* [Checking if the SKUs have reserved units](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#how-to-track-reservation-status). 
+* [Updating the number of SKUs available for sale](https://help.vtex.com/en/tutorial/updating-the-quantity-of-items-in-inventory--2MDwYV1COA6YuoiY22AyGo).
 
-A table will display the SKUs and their respective warehouses. The table is organized as follows:
+## Inventory information
+
+In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type **Inventory Management** in the search bar at the top of the page. A table will display the SKUs and their respective warehouses. The table is organized as follows:
 
 * **Rows**: each row contains the information for one SKU and one warehouse. This allows you to check the details for each SKU and warehouse. 
 * **Columns** identify different aspects of the SKU, and are divided into:
     * **Products:** the name of the product.
     * **Warehouse**: to which warehouse the SKU belongs to.
     * **SKU ID:** the identifier code for the SKU.
-    * **Last Update**: most recent quantity of SKU units registered on the VTEX platform. <p> You can click on the values in this field to check the **Update log**, with information about the users who updated this field, the dates when the changes occurred, and the quantities before and after the updates</p>
+    * **Last Update**: most recent quantity of SKU units registered on the VTEX platform.<p><div class = "alert alert-info">If you click any number in the <b>Last Update</b> column, the <a href="https://help.vtex.com/en/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2">Update Logs</a> window will open with the changes registers. Each row corresponds to an update with the user who made the change, the date and the inventory quantity before an and after the update. You can only see the last 50 updates of a SKU.</div></p>
     * **Reserved:** reserved SKU units. Orders for these reservations have not yet been approved for payment.
     By clicking on the values in this column to see details about the SKU reservation data, you are redirected to the Order management page. To learn more about how to view a reservation, please refer to [How to track reservation status](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#como-acompanhar-o-status-da-reserva)
     * **Fulfilled:** shipped units of that SKU. The items in this column are from orders with `Payment approved`, `Preparing for delivery` or `Invoiced` status. <p>By clicking on the items to view details of shipped SKUs, you will be redirected to the Order management page.</p>
     * **Available:** SKU units available for sale.
     * **Update Count:** manual update of the available quantity of SKU items. To learn more about how to update the count, read the article [Updating the quantity of SKUs in stock](https://help.vtex.com/en/tutorial/atualizar-quantidade-de-skus-em-estoque--IKMWjOjMcMqKusSGko8c0).
     * **Infinite Inventory:** allows you to add infinite SKU units, making it always available for your store's checkout. This rules out the need to update the count for this SKU.
+    * **Lead time (days):** Optional setting of shipping time at SKU level. When you define a time for the SKU of a warehouse, that is added to the [shipping time calculation](https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116). By default, the [lead time](https://help.vtex.com/en/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) is set as zero days and counted as business days, but you can [change it to calendar days](https://help.vtex.com/en/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#configuring-lead-time-calculation-in-calendar-days-optional). To configure hours, minutes, and seconds, use the [Update inventory by SKU and warehouse endpoint](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 <div class="alert alert-danger">
 To ensure the items added to the inventory will be available for sale on the store, the <a href="https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW">SKU ID</a> cannot contain <b>a leading zero</b>. For instance, the system does not read IDs with a <code>01</code>, <code>02</code>, <code>021</code> format because the expected format is <code>1</code>, <code>2</code>, <code>21</code>.
 </div>
 
-### Search filters
+The total quantity of items on the **Inventory Management** page is updated in real-time, but it may take up to 1 hour to reflect in the [inventory history](https://help.vtex.com/en/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2).
 
-In the **Inventory Management** page, you can search for SKUs in the search bar, and also use search filters.
+### Search filters
 
-To perform a search, simply type the name or SKU ID and click <i class="fa-solid fa-magnifying-glass"></i> the magnifying glass icon. To use filters, see the available oenions:
+In the **Inventory Management** page, to perform a search, simply type the name or SKU ID and click <i class="fa-solid fa-magnifying-glass"></i> the magnifying glass icon. To use filters, see the available oenions:
 
 - **Last update:** shows the updated number of items in stock. You can enter a value `Greater than or equal to`, `Less than or equal to`, or `Between` two values. If you do not enter a value, `All` items will be displayed.
 - **Reserved:** shows the reserved items. You can enter a value `Greater than or equal to`, `Less than or equal to`, or `Between` two values. If you do not enter a value, `All` items will be displayed.
diff --git a/docs/tutorials/en/managing-url-redirects.md b/docs/tutorials/en/managing-url-redirects.md
index 4a03d6cf9..d6a96c2c3 100644
--- a/docs/tutorials/en/managing-url-redirects.md
+++ b/docs/tutorials/en/managing-url-redirects.md
@@ -3,8 +3,8 @@ title: 'Managing URL redirects'
 id: 3UJuFrU8imSVWg134mkvJV
 status: PUBLISHED
 createdAt: 2022-02-03T13:17:46.873Z
-updatedAt: 2023-03-24T22:07:21.230Z
-publishedAt: 2023-03-24T22:07:21.230Z
+updatedAt: 2023-11-14T18:03:08.019Z
+publishedAt: 2023-11-14T18:03:08.019Z
 firstPublishedAt: 2022-02-03T14:42:10.000Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,7 +15,11 @@ legacySlug: managing-url-redirects
 subcategory: 1znnjA17XqaUNdNFr42PW5
 ---
 
-**Redirects** is a feature that redirects the customer to any other internal or external page. It is done in the search area using selected terms or filters. 
+**Redirects** is a feature that redirects the customer to any other internal or external page. It is done in the search area using selected terms or filters.
+
+<div class="alert alert-warning" role="alert">
+To create, edit, or remove redirects, the Admin user must have a role that has the <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager</a> <strong>CMS Settings</strong> resource. You can grant the user a role with the resource by following the instructions in the <a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512#editing-users">How to manage users</a> article or create a new role including the resource by following the instructions in the <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role">Roles</a> article.
+</div>
 
 Multiple redirects are possible in a single URL. To create a redirect, follow the instructions below. 
 
@@ -27,15 +31,20 @@ Multiple redirects are possible in a single URL. To create a redirect, follow th
 4. In the checkbox, indicate whether this redirect is temporary or permanent. If it is temporary, you need to set an end date.
 5. Click `Save`.
 
-![gerenciando redirecionamentos en 1](https://images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/342b99d95882506fce9b9e3be1205bac/image6.png)
+![gerenciando redirecionamentos en 1](//images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/342b99d95882506fce9b9e3be1205bac/image6.png)
 ## Importing redirects
 Follow the steps below to import a redirect.
 
 1. Click <i class="fas fa-upload"></i> `Import`.
-2. Choose a CSV file from your computer.
+2. Choose a CSV file from your computer, making sure that the separator is a semicolon (`;`).
 3. Click `Import File`.
 4. Click `Save`.
 
+<div class="alert alert-warning" role="alert">
+Please note that some editors can automatically change the separator. Therefore, before importing a file, make sure that it is correctly formatted as CSV and that it uses a semicolon (<code>;</code>) as the value separator. Files containing other separators, such as comma (<code>,</code>) or tab (<code>&nbsp;&nbsp;</code>), are not supported.<br><br>
+Some editors, such as Google Sheets, export CSV files using a comma (<code>,</code>) as the default separator and may not accept semicolons (<code>;</code>). In these cases, we recommend using other editors that allow you to replace separators or save the file using semicolons (<code>;</code>) as separators.
+</div>
+
 ## Exporting redirects 
 
 If you want to export your redirects, click <i class="fas fa-download"></i> `Export`, and they will be downloaded to your computer. 
diff --git a/docs/tutorials/en/managing-users-in-b2b-organizations.md b/docs/tutorials/en/managing-users-in-b2b-organizations.md
new file mode 100644
index 000000000..cf2167af8
--- /dev/null
+++ b/docs/tutorials/en/managing-users-in-b2b-organizations.md
@@ -0,0 +1,67 @@
+---
+title: 'Managing users in B2B organizations'
+id: 659ESiB9rjsR6Tg9KLl5He
+status: PUBLISHED
+createdAt: 2024-07-05T11:36:43.947Z
+updatedAt: 2024-07-05T13:50:41.743Z
+publishedAt: 2024-07-05T13:50:41.743Z
+firstPublishedAt: 2024-07-05T13:47:56.220Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: managing-users-in-b2b-organizations
+locale: en
+legacySlug: managing-users-in-b2b-organizations
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+In a VTEX B2B operation, users are those authorized to access the platform within a B2B organization. They can:
+- Place orders.
+- Manage information.
+- Perform administrative tasks.
+
+The **Users** tab in the VTEX Admin is essential for managing who can access and operate the platform on behalf of an organization. Defining users and their permissions ensures secure operations, consistent with the responsibilities and roles of each organization member.
+
+See how you can manage users by:
+- [Adding new users to the organization](#adding-new-users-to-the-organization).
+- [Editing users](#editing-users).
+- [Removing users](#removing-users).
+
+## Adding new users to the organization
+To add a new user to the organization, follow these steps:
+
+<ol>
+    <li>In the VTEX Admin, go to <strong>Apps &gt; B2B Organizations and Cost Centers &gt; Organizations</strong>, or type <strong>Organizations</strong> in the search bar at the top of the page.</li>
+    <li>Click the name of the desired organization to access its details page.</li>
+    <li>Click the <strong>Users</strong> tab.</li>
+    <li>Click <code>New</code>.</li>
+    <li>Complete the user information as shown below:
+        <ul>
+            <li><strong>Name:</strong> User's full name.</li>
+            <li><strong>Email:</strong> User email.</li>
+            <li><strong>Organization:</strong> Name of the organization.</li>
+            <li><strong>Cost Center:</strong> Cost center with which the user will be associated.</li>
+            <li><strong>Role:</strong> Role that the user will have in the store. See more details on the available roles in the <a href="https://help.vtex.com/en/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA" target="_blank">Permissions management in B2B Suite documentation</a>.</li>
+        </ul>
+    </li>
+    <li>Click <code>Save</code>.</li>
+</ol>
+
+## Editing users
+To edit information about an existing user, follow these steps:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access its details page.
+3. Click the **Users** tab.
+4. Click the user you want to edit.
+5. Edit the **Role:**
+6. Click `Save`.
+
+## Removing users
+ To remove a user, follow these steps:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access its details page.
+3. Click the **Users** tab.
+4. Click the user you want to remove.
+5. Click `Remove User`.
diff --git a/docs/tutorials/en/managing-users.md b/docs/tutorials/en/managing-users.md
index 1da40ae31..ed8286814 100644
--- a/docs/tutorials/en/managing-users.md
+++ b/docs/tutorials/en/managing-users.md
@@ -3,8 +3,8 @@ title: 'How to manage users'
 id: tutorials_512
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:09.608Z
-updatedAt: 2022-08-24T14:24:37.685Z
-publishedAt: 2022-08-24T14:24:37.685Z
+updatedAt: 2024-06-10T18:24:36.901Z
+publishedAt: 2024-06-10T18:24:36.901Z
 firstPublishedAt: 2017-04-27T23:03:28.211Z
 contentType: tutorial
 productTeam: Identity
@@ -15,60 +15,59 @@ legacySlug: creating-users
 subcategory: 63DHe3VQEEE6Uuua8gIs2M
 ---
 
-The user management with access to the administrative environment of your VTEX store is done through the [Account Management](/en/tutorial/visao-geral-do-modulo-license-manager/), in the **Users** section. To access this section, go to __Account Management__ > __Users__ in the Admin menu on the left. 
-![Menu Users](https://images.ctfassets.net/alneenqid6w5/4ufKrojjLZwb8zBdD5xz7f/2cf992fa7af4cbc9bfaca54209013274/Menu_Users.png)
+The user management with access to the administrative environment of your VTEX store is done through the [Account settings](https://help.vtex.com/en/tutorial/account-settings-overview--6USYxLuzNt4uAkvjdPF7I8), in the **Users** page. To access the page, click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
 
-This section will show the list of users with their __Name__, __Email__ and __MFA__ configuration. There are also options to search for users, export users and create new ones. Other options available on this interface are to edit or delete each user. 
-![Lista Usuários User Management EN](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
+This page displays the list of users with their __Name__, __Email__ and __MFA__ configuration. There are also options to search for users, export users and create new ones. Other options available on this interface are to edit or delete each user.
 
-## Creating a new user
-
-1. Access the __Account Management__ module.
-2. Click on the __Users__ tab.  
-![Menu Users](https://images.ctfassets.net/alneenqid6w5/4ufKrojjLZwb8zBdD5xz7f/2cf992fa7af4cbc9bfaca54209013274/Menu_Users.png)
-3. Click on the **(+) New** button.  
-![New User Management button EN](https://images.ctfassets.net/alneenqid6w5/2MzlIdrqPecPcrnjeSMTTx/b644d484f14eab4e084a8e6218cda5f7/Bot__o_Novo_Usu__rio_User_Management_EN.png)
-4. Fill in the **Email**.  
-![Add new User Management EN](https://images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/1c78fe3f13064af0b12685dba1ab85a0/Cadastro_Novo_usu__rio_User_Management_EN.png)
-5. Add the desired [Roles](https://help.vtex.com/en/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc).  
-![Select the User Management Profiles EN](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/78572b4e973e968383a582f44b9aecee/Selecionar_perfis_User_Management__EN.png)
-6. Click on the **Save** button.  
-![User Management Save button EN](https://images.ctfassets.net/alneenqid6w5/707TZ7u4fRaSVGVDfaLcMC/b59901034f50198e7012ae2ce91f0b7c/Bot__o_Salvar_Usu__rio_User_Management_EN.png)
-
-The user will receive an email confirming the information was received and a link to register the password.
+![Lista Usuários User Management EN](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
 
-The password must have at least eight characters and a number, a capital letter and a low-code letter. After filling them in, an access key will be sent by email to confirm the account.
+<div class="alert alert-warning">
+Any user that wants to manage users or application keys must have a profile with the <b>Save User</b> <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete">resource</a>. You can use the default profile <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, for example.
+</div>
 
-## Editing users
+## Creating a new user
 
-To edit an existing user, click on their name in the list of users. Another possibility is to click on the button with three points next to the desired user and then on **Edit**.
+1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
+2. Click on the `+ New` button.  
+3. Fill in the **Email**.  
+  ![Add new User Management EN](//images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/1c78fe3f13064af0b12685dba1ab85a0/Cadastro_Novo_usu__rio_User_Management_EN.png)
+4. Click on `+ Add roles`.
+5. Add the desired [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).  
+  ![Select User Management roles EN](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/b06bd642bf1763e915d49e3016ab845a/select-roles.PNG)
+6. Click on `Add roles` to confirm the selection.
+7. Click on `Save`.  
 
-![Botão Editar Usuário User Management EN](https://images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/03aa67401cc9eb46480cd9a6bbb9a65e/Bot__o_Editar_Usu__rio_User_Management_EN.png)
+The user will receive an email confirming the information was received, with a link to register the password.
 
-It is not possible to change the email. In this case, it is necessary to add the information as it was the first time.
+The password must have at least eight characters and a number, a capital letter and a lowercase letter. After filling them in, an access key will be sent by email to confirm the account.
 
-The email cannot be changed so, a new user must be created.
+## Editing users
 
-In the editing screen you can add and remove the [Roles](https://help.vtex.com/en/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc) of the user. 
-![Select the User Management Profiles EN](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/78572b4e973e968383a582f44b9aecee/Selecionar_perfis_User_Management__EN.png)
+1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
+2. To edit an existing user, click on their name in the list of users. Another possibility is to click on the menu button <i class="fas fa-ellipsis-v"></i> next to the desired user and then on **Edit**.
+  ![Botão Editar Usuário User Management EN](//images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/03aa67401cc9eb46480cd9a6bbb9a65e/Bot__o_Editar_Usu__rio_User_Management_EN.png)
+   <div class="alert alert-warning" role="alert">It is not possible to change the email of an existing user. In this case, it is necessary to delete the user and create them again with the new email.</div>
+3. In the editing page you can add and remove the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) of the user, as shown in the image below. 
+  ![Select User Management roles EN](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/b06bd642bf1763e915d49e3016ab845a/select-roles.PNG)
+4. Click on `Add roles` to confirm the selection.
+5. Click on `Save`.
 
 <div class="alert alert-info" role="alert">An alert will appear when adding roles to a user who does not use multiple factor authentication (MFA). The article <a href="https://help.vtex.com/en/tutorial/habilitar-login-por-autenticacao-de-2-fatores--4Ae1fcQi12g8u4SkQKCqWQ">Enable login by 2-factor authentication</a> shows how to enable this setting.</div>
 
-<div class="alert alert-warning" role="alert">If all roles are removed from the user, he will also no longer be able to access admin.</div>
+<div class="alert alert-warning" role="alert">If all roles are removed from the user, they will no longer be able to access VTEX Admin.</div>
 
 ## Deleting a user
 
-1. To delete a user's access, in the user list click on the three-point button next to the user you want to remove;
-2. Click on the **Delete** option;  
-![Delete a User Management button EN](https://images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/da5bdd0600085cb4b8e4203308c89f36/Bot__o_Excluir_Usu__rio_User_Management_EN.png)
-3. A message will appear to confirm the removal of the user. To confirm, click on the button **YES, REVOKE ALL ACCESS**.  
-![Confirmar Remover Acesso User Management EN](https://images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/9773084eac472c468e94d67f575a92e0/Confirmar_Remover_Acesso_User_Management_EN.png)
-
-<div class="alert alert-info">
-Although integration tokens appear in the user list, they cannot be deleted. To disable them, go to <em>Account Setup > Account Management > Account</em> and uncheck the field <strong>Status of Tokens</strong>.
-</div>
+1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
+2. Click on the menu button <i class="fas fa-ellipsis-v"></i> next to the user you want to remove.
+3. Click on the **Delete** option.
+  ![Delete a User Management button EN](//images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/da5bdd0600085cb4b8e4203308c89f36/Bot__o_Excluir_Usu__rio_User_Management_EN.png)
+  A message will appear to confirm the removal of the user.
+4. To confirm, click on the button `YES, REVOKE ALL ACCESS`.  
+  ![Confirmar Remover Acesso User Management EN](//images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/9773084eac472c468e94d67f575a92e0/Confirmar_Remover_Acesso_User_Management_EN.png)
 
 ## Exporting user data
 
-1. To export user data, click on **EXPORT**.
-2. Save the csv file to your device. The file includes the ID, email and name of each user.
+1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
+2. To export user data, click <i class="fas fa-download"></i> `Export`.
+3. Save the CSV file to your device. The file includes the ID, email and name of each user.
diff --git a/docs/tutorials/en/marketplace-invited-sellers.md b/docs/tutorials/en/marketplace-invited-sellers.md
index 4d98066f0..633c8a9f0 100644
--- a/docs/tutorials/en/marketplace-invited-sellers.md
+++ b/docs/tutorials/en/marketplace-invited-sellers.md
@@ -27,7 +27,7 @@ In addition to sending invitations, the page also displays a list of sellers to
 
 For new sellers to integrate with your marketplace, you must perform the following actions on the VTEX platform: [Invite](#inviting-sellers) and [Connect](#connecting-sellers).
 
-![EN seller invite](https://images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/48e7ae5bdb892b7e0b0811c2d868a8b4/EN_Seller_invite.jpg)
+![EN seller invite](//images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/48e7ae5bdb892b7e0b0811c2d868a8b4/EN_Seller_invite.jpg)
 
 ## Inviting sellers
 
diff --git a/docs/tutorials/en/marketplace-overview.md b/docs/tutorials/en/marketplace-overview.md
index d5cb733cd..c7ab59224 100644
--- a/docs/tutorials/en/marketplace-overview.md
+++ b/docs/tutorials/en/marketplace-overview.md
@@ -3,8 +3,8 @@ title: 'Marketplace Overview'
 id: 40Zd0z9h2RXsM9uMUp3kEb
 status: PUBLISHED
 createdAt: 2023-03-31T19:13:35.911Z
-updatedAt: 2023-03-31T19:18:29.348Z
-publishedAt: 2023-03-31T19:18:29.348Z
+updatedAt: 2023-09-13T22:33:02.149Z
+publishedAt: 2023-09-13T22:33:02.149Z
 firstPublishedAt: 2023-03-31T19:18:29.348Z
 contentType: tutorial
 productTeam: Channels
@@ -21,8 +21,6 @@ A marketplace is a virtual platform where different sellers offer their products
 
 We have grouped all the features related to these operations in the __Marketplace__ menu of your redesigned Admin. 
 
-![Admin v4 marketplace menu EN](https://images.ctfassets.net/alneenqid6w5/5y304Ab4DxbE2GRKVihDjJ/26aade5ceada45f55e0cec377adc3a32/Admin_v4_marketplace_menu_EN.jpg)
-
 Learn more about different sections and pages in this menu.
 
 ## Sellers
diff --git a/docs/tutorials/en/marketplace-strategies-at-vtex.md b/docs/tutorials/en/marketplace-strategies-at-vtex.md
index 86825bcc5..7da47d820 100644
--- a/docs/tutorials/en/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/en/marketplace-strategies-at-vtex.md
@@ -3,168 +3,185 @@ title: 'Marketplace strategies at VTEX'
 id: tutorials_402
 status: PUBLISHED
 createdAt: 2017-04-27T22:06:47.209Z
-updatedAt: 2023-04-20T20:53:42.948Z
-publishedAt: 2023-04-20T20:53:42.948Z
+updatedAt: 2024-06-20T20:13:23.276Z
+publishedAt: 2024-06-20T20:13:23.276Z
 firstPublishedAt: 2017-04-27T23:03:23.819Z
 contentType: tutorial
 productTeam: Channels
-author: 5l9ZQjiivHzkEVjafL4O6v
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: marketplace-strategies-at-vtex
 locale: en
 legacySlug: integrating-with-marketplace
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-A marketplace is a virtual platform through which different sellers offer their products. In addition to owning products, sellers are also responsible for delivering them to customers.
+A marketplace is a virtual platform through which different sellers offer their products. In addition to owning products, sellers are often responsible for the [fulfillment process](https://help.vtex.com/en/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP).  
 
-<img src="https://drive.google.com/uc?export=download&id=1qT3lLaKflfnWyHknf7IgjNbRNCki9FuQ"/>
+![Marketplace strategies](//images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/8f611e6a89c168b7322aa14e1f6b7024/Ecommerce_web_page-pana.png)  
 
-[VTEX promotes digital collaboration](https://vtex.com/us-en/ecommerce-marketplace/) in different scenarios. For example, in addition to selling your products on other marketplaces, you can also act as a marketplace and sell products from other sellers on your website.
+[VTEX promotes digital collaboration](https://vtex.com/en-us/marketplace/) in different scenarios. For example, besides selling your products on other marketplaces, you can also act as a marketplace and sell products from other sellers on your website.  
 
-In addition, VTEX allows you to manage everything in one place with a concept we call “one single panel”. With this unified management, you can manage your B2C catalog, pricing, inventory, and the different channels for which VTEX provides integration.
+VTEX allows you to manage everything in one place with a concept we call “one single panel”. With this unified management, you can manage your B2C catalog, pricing, inventory, and the different channels VTEX provides integration.  
 
 Here are some of the main transactions when selling products on marketplaces:
 
-- Inventory control in multiple channels.
-- Promotions sync.
-- Order processing.
-- Channel management.
+- Inventory control in multiple channels.  
+- Promotions sync.  
+- Order processing.  
+- Channel management.  
 
-At VTEX, there is no extra fee to integrate with marketplaces. There is also no additional charge for a VTEX store to offer products from sellers, or sell products in other VTEX stores.
+The product assortment sent to a marketplace is defined when you choose the [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).  
 
-<div class="alert alert-info">
-Orders placed through marketplaces are subject to the same <a href="https://help.vtex.com/en/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">contractual rules</a> as the ones placed through other channels.
-</div>
+[Additional trade policies can be requested](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) via a ticket to our [Support](https://help.vtex.com/pt/support) team by selecting the Commercial option and the New Trade Policy request type. A monthly fee is charged for each additional trade policy, whether used for integration with certified, partner, external, or VTEX marketplaces.  
 
-You select the product assortment to send to a marketplace when choosing your [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `Create a trade policy`.
+<div class="alert alert-info">
+ Orders placed through marketplaces are subject to the same <a href="https://help.vtex.com/en/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">contractual rules</a> as the ones placed through other channels.  
+</div>  
 
-Requesting additional trade policies to integrate with certified connectors, certified connectors, or other VTEX stores is free of charge.
+Here are the scenarios we will address next:  
 
-Here are the scenarios we will address next:
+- [Acting as a marketplace](#acting-as-a-marketplace)  
+- [Selling on marketplaces](#selling-on-marketplace)  
+- [Seller Portal](#seller-portal)  
 
-- [Selling on marketplaces](#selling-on-marketplaces)
-- [Acting as a marketplace](#acting-as-a-marketplace)
+## Acting as a marketplace
 
-## Selling on marketplaces
+VTEX's architecture allows stores hosted on its platform to offer products from other stores, whether they are VTEX stores or not. When a VTEX store starts selling products from sellers, it becomes a VTEX marketplace.  
 
-Marketplaces are online sales spaces where sellers offer their products. There are several reasons why it can be strategically advantageous to sell on a marketplace. Some of the main ones are:
+You benefit from this relationship when your store operates as an environment where other sellers offer their products. Below are some of the main advantages of operating as a marketplace:  
 
-- **Gain visibility for your store**: centralizing different sellers and a wide variety of products on a single marketplace attracts user traffic. Besides, by offering your products on multiple channels, you can increase brand visibility and reach new audiences.
-- **Use a cost-effective service**: each marketplace has its own commercial conditions. The most common one is to pay a commission on sales. Therefore, if a seller’s products do not sell, no commissions will be charged.
-- **Increase sales**: operating in multiple channels diversifies your revenue streams and can increase conversion rates.
-- **Diversify your audience**: you can define a specific product assortment for each marketplace, and from there build market validation strategies or make seasonal sales.
-- **Add value to your products**: you can benefit from the trust relationship between a marketplace and its customers, especially if the audience is not familiar with your brand. This adds value to your product and can increase your conversion rates.
+- __Increase revenue:__ There are different ways to monetize an online marketplace. The most common is receiving a commission on sales made on your website.  
+- __Diversify your product offering:__ Offer more products and options for your customers.  
+- __Reach new customers:__ Sellers attract new customers to the marketplace, expanding your market reach and increasing your brand visibility.  
+- __Improve your customer’s shopping experience:__ Diversifying and expanding your product catalog can deliver a higher-quality customer experience. As a result, your customers will be able to buy everything they need in one place (one-stop shop).  
+- __Keep your costs low:__ This collaboration process does not increase your costs, as it is a scalable model that does not require investments in inventory, structure, or staff because delivering products is the sellers' responsibility.  
+- __Improve your brand reputation:__ If your store is well-known in the market, customers will trust your marketplace and the products you offer on your website. In addition, you can increase your profits by offering sellers added value to their products.  
 
-At VTEX, you can sell on other channels by:
+A VTEX store can sell products from other sellers by:  
 
-- [Being a VTEX seller](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller)
-- [Integrating with a certifified marketplace](#integrating-with-a-certified-marketplace)
-- [Integrating with marketplaces partners](#integrating-with-marketplaces-partners)
-- [Integrating with an external marketplace](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-an-external-marketplace)
+- [Integrating with an external seller](#integrating-with-an-external-seller)  
+- [Operating as a VTEX marketplace](#operating-as-a-vtex-marketplace)  
 
-<div class="alert alert-info">
-A VTEX store can act simultaneously as a <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller">VTEX seller</a> and a <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplace</a>.
-</div>
-
-<div class = "alert alert-info">
-VTEX platform offers different fulfillment features that can be combined for scenarios such as dropshipping, when the seller receives and forwards the customer's order to a third party responsible for the fulfillment. The most fitting <a href="https://help.vtex.com/en/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP">logistics</a> solution for the seller will depend on architecture and business model and can be implemented through <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">Back office integration (ERP/PIM/WMS)</a>.
-</div>
+### Integrating with an external seller
 
-### Being a VTEX seller
+For sellers not integrated with VTEX but want to sell their products on a VTEX marketplace, a custom connector can be developed for this integration. VTEX provides a set of APIs and instructions to facilitate the process. For more information, see our [guide for integrating with external sellers](https://developers.vtex.com/vtex-developer-docs/docs/external-seller-integration-guide).  
 
-VTEX's architecture allows stores hosted in the VTEX environment to sell their products in other VTEX stores. A VTEX store that sells its products on another VTEX store is called a VTEX seller. Later on in this article, you will see more information about VTEX stores that offer products from VTEX sellers, acting as [VTEX marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace).
+### Operating as a VTEX marketplace
 
-Setting up an [integration between VTEX stores](https://help.vtex.com/en/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP) is simple and has fewer steps than other integrations. You can also use the feature __Marketplaces and Integrations__, which has a catalog of stakeholders interested in partnerships, facilitating contact between VTEX sellers, VTEX marketplaces and certified connectors.
+The process to configure your store as [a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) does not require some of the steps required in other integrations. Once your marketplace is configured, see [Actions for a VTEX marketplace operation](https://help.vtex.com/en/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev).  
 
-The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) is a VTEX platform edition for sellers to connect and sell their products on VTEX marketplaces. The portal allows sellers to access all the key features necessary to operate ecommerce on big storefronts, increasing visibility and sales conversion.
+See below for the main VTEX marketplaces:  
 
-<div class = "alert alert-info">
-In VTEX, it is possible to act as a <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a>, a seller unknown to the consumer in his shopping experience. This type of seller is the standard for <a href="https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">franchise accounts</a>, for example, and can be strategic for certain business models. To learn more, see the article <a href="https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Choosing between standard account, franchise account or Seller Portal</a>.
-</div>
+![mkt br](//images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
 
-### Integrating with a certified Marketplace
-
-There are national and international marketplaces that are excellent options for promoting your products and boosting your sales.
-
-Currently, you can use the following certified connectors on the VTEX platform:
-
-- [Amazon](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP)
-- [Mercado Livre](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq)
-- [Magazine Luiza](https://help.vtex.com/en/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y)
-- [Carrefour](https://help.vtex.com/en/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2)
-- [Centauro](https://help.vtex.com/en/tracks/integracao-com-a-centauro--D8Qnjbr5lfLkUfMRhsfbj)
-- [Facebook](https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc)
-- [Google Shopping](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw)
-- [Google Shopping Ads](https://help.vtex.com/en/tracks/como-fazer-campanhas-atraves-do-google-ads--47kz5PRQPK0IEaqGqiIuA)  
-- [Dafiti](https://help.vtex.com/en/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i)
-- [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm)
-- [Tik Tok](https://help.vtex.com/en/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd)
-- [CSU (Opte+)](https://help.vtex.com/en/tutorial/integrando-com-csu-opte-2--tutorials_4258)
-- Zoom
-- Kabum
-- GPA
-- MadeiraMadeira
-- Riachuelo
-- Camicado
-- Renner
-- Loopi
-- GrupoLTM
-- TudoAzul
-- Webcontinental
-- Farfetch
+The __Marketplaces and Integrations__ module also promotes and enables contact between VTEX marketplaces and certified VTEX sellers interested in collaborations.  
 
-<div class="alert alert-info">
-Although Facebook, Google Shopping, Google Shopping Ads, and TikTok are not marketplaces, we added their connectors to this list as they offer a similar experience of sending products from VTEX stores.
-</div>
+## Selling on marketplaces
 
-For more information on how external marketplaces can join the [business plan](https://vtex.com/us-en/partner/) and obtain partner certification, see the article [Become a certified connector (partner)](https://help.vtex.com/en/tutorial/tornar-se-um-conector-certificado-parceiro--66mnclLFVFolMBGNtZbKzt).
+There are several reasons why it can be strategically advantageous to sell on a marketplace, which are:  
 
-### Integrating with marketplaces partners
+- __Gain visibility for your store:__ Centralizing different sellers and a wide variety of products on a single marketplace attracts user traffic. Besides, by offering your products on multiple channels, you can increase brand visibility and reach new audiences.  
+- __Use a cost-effective service:__ Each marketplace has its own commercial conditions. The most common one is to pay a commission on sales. Therefore, if a seller’s products do not sell, the marketplace will charge no commissions.   
+- __Increase sales:__ Operating in multiple channels diversifies your revenue streams and can increase conversion rates.  
+- __Diversify your audience:__ You can define a specific product assortment for each marketplace, build market validation strategies, or make seasonal sales.  
+- __Add value to your products:__ You can benefit from the trust relationship between a marketplace and its customers, especially if the audience is not familiar with your brand. This adds value to your product and can increase your conversion rates.  
 
-There are external integrations, which were developed together with partner hubs.
+### Marketplace types
 
-- Shopee
-- [Wish](https://help.vtex.com/en/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4)  
-- Olist
-- Conecta Lá
-- Anymarket
-- TudoAzul
-- Easy Live
-- Mimo
-- Wap Store
-- Plugg.to
-- Fast Shop
-- Hubplus
+There are national and international marketplaces that are great for promoting your products and boosting your sales.  
 
-### Integrating with an external marketplace
+By acting as a VTEX seller, you can integrate with four marketplace types: certified, partner, external, and VTEX marketplaces.  
 
-If you want to sell your products on a marketplace that is not integrated with VTEX, you can develop a custom connector for this integration. VTEX provides a set of APIs and instructions to facilitate the process. See more details in the [guide for integrating with external marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide).
+To integrate with a marketplace, the content linked above provides support to guide the configuration process. As a VTEX customer, you can contact our support team if you experience any issues.  
 
-## Acting as a marketplace
+At VTEX, you can sell on other channels in the following situations:  
 
-Besides selling on other marketplaces, your store can also sell products from other sellers. Here are some of the main advantages of acting as a marketplace:
+- [Integrating with external marketplaces](#integrating-with-external-marketplaces)  
+- [Integrating with certified marketplaces](#integrating-with-certified-marketplaces)  
+- [Integrating with partner marketplaces](#integrating-with-partner-marketplaces)  
+- [Operating as a VTEX seller](#operating-as-a-vtex-seller)  
 
-- **Increase revenue**: there are different ways to monetize an online marketplace. The most common one is to receive a commission on sales made on your website.
-- **Diversify your product offering**: you will be able to offer more products and options for your customers.
-- **Reach new customers**: sellers attract new customers to the marketplace, expanding your market reach and increasing your brand visibility.
-- **Improve your customer’s shopping experience**: by diversifying and expanding your product catalog, you deliver a higher quality customer experience. As a result, your customers will be able to buy everything they need in one place (one-stop-shop).
-- **Keep your costs low**: this collaboration process does not increase your costs. It is a scalable model that does not require investments in inventory, structure, or staff because delivering products is the sellers' responsibility.
-- **Improve your brand reputation:** if your store is well-known in the market, customers will trust your marketplace and the products you offer in your website. In addition, you can increase your profits by offering sellers an added value to their products.
+<div class="alert alert-info">
+  A VTEX store can act simultaneously as a <a href="#selling-on-marketplaces">VTEX seller</a> and a <a href="#operating-as-a-vtex-marketplces">VTEX marketplace</a>.  
+The VTEX platform offers different fulfillment features that can be combined for scenarios such as dropshipping, where the seller receives and forwards the customer's order to a third party responsible for the fulfillment. The most fitting <a href="https://help.vtex.com/en/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP">logistics</a> solution for the seller will depend on the architecture and business model and can be implemented through <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">Back office integration (ERP/PIM/WMS)</a>.
+</div>  
 
-A VTEX store can sell products from other sellers by:
+### Integrating with an external marketplace
 
-- [Being a VTEX marketplace](#being-a-vtex-marketplace)
-- [Integrating with an external seller](#integrating-with-an-external-seller)
+If you want to sell your products on a marketplace not integrated with VTEX, you can develop a custom connector for this integration. VTEX provides a set of APIs and instructions to facilitate the process. See more details in the [guide for integrating with external marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide).  
+
+### Integrating with certified marketplaces
+
+Certified marketplaces are those whose integration has been developed by VTEX's engineering team. For these integrations, the additional trade policy is exempt from the monthly fee when orders are linked to the policy via the certified marketplace. Instead, fees will be based solely on the take rate of the orders.  
+
+<div class="alert alert-warning">
+Additional trade policies requested for integrating with certified marketplaces that are also used for integrating with other marketplace types are subject to a monthly fee.
+</div>  
+
+Currently, on the VTEX platform, you can find the following certified marketplaces:  
+
+- [Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP)  
+- [Mercado Libre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq)  
+- [Magazine Luiza](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y)  
+- [Carrefour](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2)  
+- [Centauro](https://help.vtex.com/pt/tracks/integracao-com-a-centauro--D8Qnjbr5lfLkUfMRhsfbj)  
+- [Dafiti](https://help.vtex.com/pt/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i)  
+- [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm)  
+- [Zoom](https://help.vtex.com/pt/tutorial/integrando-com-zoom--2OoQjigCVOIEWWkgOqwCK6?&utm_source=autocomplete)  
+- [CSU (Opte+)](https://help.vtex.com/pt/tutorial/integrando-com-csu-opte-2--tutorials_4258)  
+- [MadeiraMadeira](https://help.vtex.com/pt/tutorial/integracao-com-madeiramadeira--J4QCENKiz4urYNfaMuE0i)  
+- [Riachuelo](https://help.vtex.com/pt/tutorial/integracao-com-riachuelo--kpfxAgwEcANihHLT4iW81)  
+- [Camicado](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)  
+- [Renner](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)  
+- [Enjoei](https://help.vtex.com/tutorial/integracao-com-enjoei--3mV9uhw1AdqFol8K2tfwly)  
+- [Wish](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4)  
+- Kabum  
+- Grupo LTM  
+- TudoAzul  
+- GPA  
+- Climario  
+- Juntoz  
+- SMPlaces  
+- Farfetch  
+- Falabella  
+- Linio  
+
+### Integrating with partner marketplaces  
+Partner marketplaces are those whose integration has been developed by a hub of VTEX partner developers. The additional trade policy requested for this integration type is subject to the monthly fee and order take rate.  
+
+Below, you will find the partner marketplaces available in the VTEX catalog:  
+
+- Americanas  
+- Via Varejo  
+- [Shopee](https://help.vtex.com/pt/tutorial/integracao-com-a-shopee-beta--5OV9idUY6fHu3P8grnCnqj)  
+- [Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc)  
+- [Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw)  
+- [Google Shopping Ads](https://help.vtex.com/pt/tracks/como-fazer-campanhas-atraves-do-google-ads--47kz5PRQPK0IEaqGqiIuA)  
+- [Tik Tok](https://help.vtex.com/pt/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd)  
+- [Livelo](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/5rhGcaM0SedoK7lDMBkVFD)  
+- Olist  
+- Anymarket  
+- Easy Live  
+- Mimo  
+- Wap Store  
+- Plugg.to  
+- Fast Shop  
+- Hubplus  
 
-### Being a VTEX marketplace
+<div class="alert alert-info">
+Facebook, Google Shopping, Google Shopping Ads, and TikTok are not marketplaces, but they offer a similar experience of sending products from VTEX stores.
+</div>  
 
-VTEX's architecture allows stores hosted on the VTEX platform to offer products from other stores, be they VTEX stores or not. When a VTEX store starts selling products from other sellers, it becomes a VTEX marketplace.
+### Operating as a VTEX seller  
 
-Setting up your store to [become a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) is simple and has fewer steps than other integrations. Once your marketplace is set up, check out [Actions for a VTEX marketplace operation](https://help.vtex.com/pt/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev).
+VTEX's architecture allows stores hosted in your platform to sell their products in other VTEX stores. A VTEX store that sells its products on another VTEX store is called a VTEX seller. Later in this article, you will see more information about VTEX stores offering products from VTEX sellers, acting as [VTEX marketplaces](#operating-as-a-vtex-marketplaces).  
 
-You can also use the __Marketplaces and Integrations__ feature, which promotes and facilitates contact between VTEX marketplaces, VTEX sellers, and certified connectors interested in partnerships.
+Setting up an [integration between VTEX stores](https://help.vtex.com/en/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP) is simple and requires fewer steps than other integrations. You can also use the Marketplaces and Integrations module, which provides a catalog of marketplaces interested in partnerships and facilitates contact between VTEX sellers, VTEX marketplaces, and certified marketplaces.   
 
-### Integrating with an external seller
+## Seller Portal  
 
-For sellers that are not integrated with VTEX but want to sell their products on a VTEX marketplace, a custom connector can be developed for this integration. VTEX provides a set of APIs and instructions to facilitate the process. For more information, see our [guide for integrating with external sellers](https://developers.vtex.com/vtex-developer-docs/docs/external-seller-integration-guide).
+The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) is a VTEX platform edition for sellers to connect and sell their products on VTEX marketplaces. The portal allows sellers to access all the key features necessary to operate ecommerce on big storefronts, increasing visibility and sales conversion.  
 
+<div class="alert alert-info">
+At VTEX, it is possible to act as a <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a>, a seller unknown to the consumer in his shopping experience. This type of seller is the standard for <a href="https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">franchise accounts</a>, for example, and can be strategic for certain business models. To learn more, see the article <a href="https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Choosing between standard account, franchise account, or Seller Portal</a>.
+</div>
diff --git a/docs/tutorials/en/marketplaces-and-integrations.md b/docs/tutorials/en/marketplaces-and-integrations.md
index c9e71ef2e..73a522b00 100644
--- a/docs/tutorials/en/marketplaces-and-integrations.md
+++ b/docs/tutorials/en/marketplaces-and-integrations.md
@@ -3,8 +3,8 @@ title: 'Marketplaces and Integrations'
 id: 5AcBO1t29nhq7rBHas9b6V
 status: PUBLISHED
 createdAt: 2023-04-18T13:51:54.217Z
-updatedAt: 2023-05-04T18:59:04.105Z
-publishedAt: 2023-05-04T18:59:04.105Z
+updatedAt: 2024-02-19T20:19:40.774Z
+publishedAt: 2024-02-19T20:19:40.774Z
 firstPublishedAt: 2023-05-03T17:09:07.242Z
 contentType: tutorial
 productTeam: Channels
@@ -33,7 +33,7 @@ If you want to act as a VTEX marketplace, read the <a href="https://help.vtex.co
 
 To access the page, in the VTEX Admin, click __Marketplace > Connections > Marketplaces and Integrations__. On the page, you can see the recommended marketplaces to connect to and the complete list of all available or already connected marketplaces.  
 
-![Marketplaces and Integrations](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
+![Marketplaces and Integrations](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
 
 The table listing the marketplaces has the following columns:  
 
@@ -124,4 +124,4 @@ See the list of tutorials available for marketplace integration:
 - [Farmácias App](https://help.vtex.com/pt/tutorial/integrando-com-farmacias-app--tutorials_6271)    
 - [Shopee](https://help.vtex.com/pt/tutorial/integracao-com-a-shopee-beta--5OV9idUY6fHu3P8grnCnqj)  
 - [Wish ](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4) 
-- [Conecta Lá](https://help.vtex.com/pt/tutorial/integracao-com-conecta-la--403fvPYdv2f6VeP0na3awP)  
+
diff --git a/docs/tutorials/en/master-data.md b/docs/tutorials/en/master-data.md
index 27c2760b3..6c98951a8 100644
--- a/docs/tutorials/en/master-data.md
+++ b/docs/tutorials/en/master-data.md
@@ -3,8 +3,8 @@ title: 'Master Data'
 id: 4otjBnR27u4WUIciQsmkAw
 status: PUBLISHED
 createdAt: 2018-04-02T19:01:38.026Z
-updatedAt: 2023-05-23T14:24:05.123Z
-publishedAt: 2023-05-23T14:24:05.123Z
+updatedAt: 2024-06-07T20:19:30.086Z
+publishedAt: 2024-06-07T20:19:30.086Z
 firstPublishedAt: 2018-04-02T20:54:18.272Z
 contentType: tutorial
 productTeam: Master Data
@@ -27,7 +27,7 @@ Note that depending on the functionality and version you wish to use, it is nece
 
 ## Versions available
 
-Currently there are two versions available and you can choose the one that best suits your operational needs. The main difference between the two is that v2 does not have a graphical interface and can be used only through [Master Data v2 API](https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview), although it has other relevant functionalities, such as the use of [JSON schemas](https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema).
+Currently there are two versions available and you can choose the one that best suits your operational needs. The main difference between the two is that v2 does not have a graphical interface and can be used only through [Master Data v2 API](https://developers.vtex.com/docs/api-reference/master-data-api-v2), although it has other relevant functionalities, such as the use of [JSON schemas](https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema).
 
 <div class = "alert alert-info">
 Note that the VTEX platform natively saves customer data from your store in Master Data v1.
@@ -35,130 +35,194 @@ Note that the VTEX platform natively saves customer data from your store in Mast
 
 Check the table below to learn more about the different functionalities of each version.
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><b>Functionality</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>v1</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>v2</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>Learn more</b>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Graphical interface
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">-
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">API
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v1-overview">Master Data v1 API</a></li> 
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview">Master Data v2 API</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Importing and exporting spreadsheets
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">
-<ul><li><a href="https://help.vtex.com/en/tutorial/importing-data-into-master-data--tutorials_1135#">Import data into Master Data v1</a></li> <li><a href="https://help.vtex.com/en/tutorial/exporting-data--tutorials_1125#">Export data from Master Data v1</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Attachments (imagens)
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">-
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Triggers
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#triggers”>Triggers</a></li><li><a href="https://help.vtex.com/en/tutorial/creating-trigger-in-master-data--tutorials_1270#">Creating triggers with Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2">Creating triggers with Master Data v2</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">JSON Schemas
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="http://json-schema.org/">JSON schemas</a></li><li><a href="https://spacetelescope.github.io/understanding-json-schema">Understanding JSON schemas</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema">Starting to work with JSON schemas in Master Data v2</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/master-data-schema-lifecycle">Schema life cycle in Master Data v2</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Nested properties
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#nested-properties”>Nested properties</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Data entities
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Referenced by acronyms composed of two capital letters. For example, the 'CL' entity stores client data from the store and 'AD' stores addresses. Cannot be created via API.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Referenced by their names. For example, 'Client' and 'Address'. Can only be created via API.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#data-entities”>Data entities</a></li><li><a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265">Data entities in Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/creating-relationships-between-data-entities-using-api">Creating relationships between Master Data v2 data entities</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Fields
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">They must be filled in in the specific format configured in the data entity.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Firstly, there is no restriction on fields and formats. Format validation is made through JSON schemas.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos">Field types in Master Data v1</a></li><li><a href=”#v2-schemas”>JSON schemas</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Indexes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://help.vtex.com/en/tutorial/setting-up-an-index-on-master-data--tutorials_785">How to set up indexes in Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/reference/putindices">How to set up indexes with Master Data v2 API</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">VTable
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://developers.vtex.com/vtex-rest-api/docs/vtable">VTable</a></li></ul>
-   </td>
-  </tr>
-</table>
+<div style="overflow: auto;"><table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px;border-collapse: collapse;">
+   <thead class="bb b--muted-3 tl">
+      <tr>
+         <th class="t-body fw5 pa5" style="min-width: 10rem">Functionality</th>
+         <th class="t-body fw5 pa5" style="min-width: 10rem;">v1</th>
+         <th class="t-body fw5 pa5" style="min-width: 10rem;">v2</th>
+         <th class="t-body fw5 pa5" style="min-width: 10rem;">Learn more</th>
+      </tr>
+   </thead>
+   <tbody>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Graphical interface
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">No
+         </td>
+         <td class="t-body pa5">-
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">API
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="https://developers.vtex.com/docs/api-reference/masterdata-api" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Master
+                     Data
+                     v1 API</a></li>
+               <li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Master
+                     Data
+                     v2 API</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Importing and exporting spreadsheets
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">No
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="https://help.vtex.com/en/tutorial/importing-data-into-master-data--tutorials_1135#" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Import
+                     data into Master Data v1</a></li>
+               <li><a href="https://help.vtex.com/en/tutorial/exporting-data--tutorials_1125#" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Export
+                     data from Master
+                     Data v1</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Attachments (imagens)
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">No
+         </td>
+         <td class="t-body pa5">-
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Triggers
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="#triggers" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Triggers</a>
+               </li>
+               <li><a href="https://help.vtex.com/en/tutorial/creating-trigger-in-master-data--tutorials_1270#" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Creating
+                     triggers with Master Data v1</a></li>
+               <li><a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Creating
+                     triggers with Master Data v2</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">JSON Schemas
+         </td>
+         <td class="t-body pa5">No
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="http://json-schema.org/" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">JSON
+                     schemas</a></li>
+               <li><a href="https://json-schema.org/understanding-json-schema" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Understanding
+                     JSON schemas</a>
+               </li>
+               <li><a href="https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Starting
+                     to work with JSON schemas in Master Data v2</a></li>
+               <li><a href="https://developers.vtex.com/vtex-rest-api/docs/master-data-schema-lifecycle" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Schema
+                     life
+                     cycle in Master Data v2</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Nested properties
+         </td>
+         <td class="t-body pa5">No
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="#nested-properties" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Nested
+                     properties</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Data entities
+         </td>
+         <td class="t-body pa5">Referenced by acronyms composed of two capital letters. For example, the 'CL' entity stores client data from the store and 'AD' stores addresses. Cannot be created via API.
+         </td>
+         <td class="t-body pa5">Referenced by their names. For example, 'Notification'. Can only be created via API.
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="#data-entities" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Data
+                     entities</a></li>
+               <li><a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Data
+                     entities
+                     in Master Data v1</a></li>
+               <li><a href="https://developers.vtex.com/vtex-rest-api/docs/creating-relationships-between-data-entities-using-api" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Creating
+                     relationships between Master Data v2 data entities</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Fields
+         </td>
+         <td class="t-body pa5">Must be filled in in the specific format configured in the data entity.
+         </td>
+         <td class="t-body pa5">At first, there is no restriction on fields's formats. Format is validated through JSON schemas.
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265#understanding-the-types" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Field
+                     types in Master Data v1</a></li>
+               <li><a href="#v2-schemas" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">JSON
+                     schemas</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">Indexes
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="https://help.vtex.com/en/tutorial/setting-up-an-index-on-master-data--tutorials_785" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">How
+                     to
+                     set up indexes in Master Data v1</a></li>
+               <li><a href="https://developers.vtex.com/docs/api-reference/master-data-api-v2#put-/api/dataentities/-dataEntityName-/indices" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">How
+                     to set up indexes with
+                     Master Data v2 API</a></li>
+            </ul>
+         </td>
+      </tr>
+      <tr class="bb b--muted-3">
+         <td class="t-body pa5">VTable
+         </td>
+         <td class="t-body pa5">No
+         </td>
+         <td class="t-body pa5">Yes
+         </td>
+         <td class="t-body pa5">
+            <ul style="padding-inline-start: 0px;">
+               <li><a href="https://developers.vtex.com/docs/guides/vtable" rel="noopener noreferrer" target="_blank" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">VTable</a>
+               </li>
+            </ul>
+         </td>
+      </tr>
+   </tbody>
+</table></div>
 
 <div class="alert alert-danger">
 Note that the data entities of the two versions are independent, even if some may be analogous. This means that a data created in a v1 entity cannot be queried or edited using v2 resources and vice versa.
@@ -211,7 +275,7 @@ As mentioned above, each document has an ID automatically generated by the platf
 For example, you can query a document with a client's information by specifying the value of the 'email' field for the client.
 
 <div class = "alert alert-info">
-Learn more about <a href=”https://help.vtex.com/en/tutorial/setting-up-an-index-on-master-data--tutorials_785”>setting up indexes in Master Data v1</a> or <a href=”https://developers.vtex.com/vtex-rest-api/reference/putindices”>setting up indexes with Master Data v2 API</a>.
+Learn more about <a href=https://help.vtex.com/en/tutorial/setting-up-an-index-on-master-data--tutorials_785>setting up indexes in Master Data v1</a> or <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>setting up indexes with Master Data v2 API</a>.
 </div>
 
 ## Triggers
@@ -228,12 +292,12 @@ Learn more about how [to configure triggers in Master Data v1](https://help.vtex
 With Master Data v2, you can define data formats with JSON schemas. This format indicates how the Master Data should validate and index documents.
 
 <div class = "alert alert-info">
-Learn more about <a href=”https://json-schema.org/”>JSON schemas</a>.
+Learn more about <a href=https://json-schema.org/>JSON schemas</a>.
 </div>
 
 You can save a document to any data entity if the content is a valid JSON. A data entity may or may not have multiple JSON schemas associated with it.
 
-![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/72f691a72fe0166b1e16a38c6bf89d11/schemas_en.jpg)
+![Master Data schemas](//images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/72f691a72fe0166b1e16a38c6bf89d11/schemas_en.jpg)
 
 <div class = "alert alert-info">
 A document can be compatible with multiple JSON Schemas, but also with none.
diff --git a/docs/tutorials/en/match-offers-mercado-livre.md b/docs/tutorials/en/match-offers-mercado-livre.md
new file mode 100644
index 000000000..e2a1627c7
--- /dev/null
+++ b/docs/tutorials/en/match-offers-mercado-livre.md
@@ -0,0 +1,20 @@
+---
+title: 'Match Offers Mercado Livre'
+id: 1C4HjNLbNk2Y6evD0luXMr
+status: PUBLISHED
+createdAt: 2024-05-06T21:14:40.722Z
+updatedAt: 2024-06-20T21:30:01.461Z
+publishedAt: 2024-06-20T21:30:01.461Z
+firstPublishedAt: 2024-05-06T21:49:40.831Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: match-offers-mercado-livre
+locale: en
+legacySlug: match-offers-mercado-livre
+subcategory: 
+---
+
+<div class="alert alert-warning">
+This is a regional exclusive content not applicable to English speaking countries.
+  </div> 
diff --git a/docs/tutorials/en/media-overview.md b/docs/tutorials/en/media-overview.md
index 428fa2f05..7b8147eed 100644
--- a/docs/tutorials/en/media-overview.md
+++ b/docs/tutorials/en/media-overview.md
@@ -3,8 +3,8 @@ title: 'Media - Overview'
 id: 31fhjHTt4TBoo50AmGQ9b2
 status: PUBLISHED
 createdAt: 2023-05-29T23:26:35.354Z
-updatedAt: 2023-05-31T12:29:38.226Z
-publishedAt: 2023-05-31T12:29:38.226Z
+updatedAt: 2024-07-03T19:28:25.937Z
+publishedAt: 2024-07-03T19:28:25.937Z
 firstPublishedAt: 2023-05-30T18:01:54.161Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,8 +15,13 @@ legacySlug: media-overview
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-Media is responsible for managing your store's media files, such as images and GIFs. With Media, you can upload and organize media files in the following formats: `PNG`, `JPG`, `GIF`, `SVG`, and `WEBP`.
-![Media Overview](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4151c07cdf6675310b41607256633894/en-media-overview.png)
+Media is a feature responsible for managing your store's media files, such as images and videos. For images, you can upload and organize files up to 5 MB in the following formats: `png`, `jpg`, `gif`, `svg` and `webp`. For videos, you can add a URL to the externally hosted video provider, e.g. YouTube or Vimeo.
+
+<div class="alert alert-warning">
+  For upload, files must have a lowercase extension (e.g., <code>store.png</code>) and be up to <b>5 MB</b>.
+</div>
+
+![Media Overview](//images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4151c07cdf6675310b41607256633894/en-media-overview.png)
 
 In addition, Media is integrated with **Site Editor** and **Headless CMS**. This integration allows you to access and manage Media directly through VTEX CMS solutions.
 
@@ -30,46 +35,98 @@ There are three ways to access Media:
 
 - **Media**: In the VTEX Admin, go to **Storefront > Media**.
 
-- **Site Editor** (for stores using the Store Framework): In the VTEX Admin, go to **Storefront > Site Editor**, choose a block that contains an image (e.g. Carousel), and click `Add`.  A modal will open.
+- **Site Editor** (for stores using the Store Framework): In the VTEX Admin, go to **Storefront > Site Editor**, choose a block that contains an image (e.g. Carousel), and click `Add`. A Media panel will open.
 
-- **Headless CMS**: In the VTEX Admin, go to **Storefront > Headless CMS**. Choose one of the created pages, such as a product page. From the available sections, select one to which you can add an image (for example, Hero), and click the Hero image component. A modal will open.
+- **Headless CMS**: In the VTEX Admin, go to **Storefront > Headless CMS**. Choose one of the created pages, such as a product page. From the available sections, select one to which you can add an image, e.g. , [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero), and click the Hero image component. A Media panel will open.
+
+<div class="alert alert-warning">
+Note that the section must use the <a href="https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms">media-gallery</a> to leverage Media. For <a href="https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore">FastStore</a> projects, the sections that use the <i>media-gallery</i> widget are <a href="https://developers.vtex.com/docs/guides/faststore/organisms-navbar">Navbar</a> and <a href="https://developers.vtex.com/docs/guides/faststore/organisms-hero">Hero</a>.
+</div>
 
 In the following image, you can see an overview of the Media interface and the actions available for managing your media files:
 
-![Media Features](https://images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/7466fed34ed8183fde0b9d61e68b9e1f/en-media-features.png)
+![Media Features](//images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/7466fed34ed8183fde0b9d61e68b9e1f/en-media-features.png)
 
 | Field | Description |
 | ---------- | ------------- |
 | **I - Search Field** | Search for available files in Media. |
 | **II - Sort by** | Sort how files are displayed in the interface based on the filters: `Newest`, `Oldest`, `Name (A-Z)`, and `Name (Z-A)`. |
-| **III - Pages** Browse the available file pages. |
+| **III - Pages** | Browse the available file pages. |
 | **IV - View Mode** | Choose the view mode for the files: `List View` or `Grid View`. |
 | **V - Add Image** | Upload a new file from your device. |
 
 ## Managing files in Media
 See in the sections below the actions available for managing files in Media:
 
-### Uploading files to Media
-1. On the **Media** page, click `Add New`.
+### Uploading images 
+In Media, you can upload images, and the feature supports the following formats: `png`, `jpg`, `gif`, `svg` and `webp`, with a file size limit of 5 MB. To start uploading your store’s image, follow these steps:
+
+1. On the **Media** page or panel, click `Add New` and click `Image`.
+
+<div class="alert alert-warning">
+  <p>In the Media panel available in the Headless CMS and Site Editor, you can drag and drop images.</p>
+</div>
+
 2. Choose the image you want to upload and click `Open`.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Keep in mind that Media supports the following formats: <i>PNG</i>, <i>JPG</i>, <i>GIF</i>, <i>SVG</i>, and <i>WEBP</i>.
+<div class="alert alert-warning">
+ Please note that Media accepts the following formats: <code>png</code>, <code>jpg</code>, <code>gif</code>, <code>svg</code>, and <code>webp</code>, in lowercase and with a file size limit of 5 MB.
 </div>
 
-3. After the image is loaded, a success message will be displayed. Now, you can perform other actions by clicking `More actions` (three vertical dots) on the image thumbnail and choosing one of the following actions:
+3. After the image is loaded, a success message will be displayed.
+
+Now, you can perform other actions by clicking `More actions` (three vertical dots) on the image thumbnail and choosing one of the following actions:
 
 | Field | Description |
 | ---------- | ------------- |
-| **View** | Opens the image on a new page. |
+| **Preview** | Opens the image on a new page. |
 | **Copy URL** | Copies the URL of the image so that you can use it in other sections of your store. |
 | **Download** | Downloads the image to your computer. |
 | **Delete** |	Deletes the image from the repository. |
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
 Deleting the image will only remove it from the Media repository. If you have added the image to a Hero component, for example, the image will continue to be used in that component. However, you will not be able to use it in other components.
 </div>
 
-### Canceling an upload in Media
+### Adding videos
+Besides images, in Media, you can also store videos and then use them in your store to create visual appeal for users navigating the store.
+
+1. On the **Media** page, click `Add New` and choose `Video`.
+2. In the modal, enter the video’s name and its URL accordingly.
+
+- **Video Name:** Add a name for the video that helps you better identify it in the gallery.
+- **Video URL:** Add the video’s URL.
+
+3. Click `Add Video`. 
+
+With the video added, you can choose what to do with the video by clicking on the menu `⋮` in the video’s thumbnail:
+
+- **Copy URL**: Get the video’s URL address to use in your store through the Headless CMS.
+- **Open Video**: See a preview of the video in a new browser tab.
+- **Delete**: Delete the video from your Gallery.
+
+### Adding a video to content in Headless CMS
+Integrating multimedia content, such as videos, into your Headless CMS can enhance the user experience of your website. Follow the steps below to add videos to your store.
+
+1. In the VTEX Admin, go to **Storefront > Headless CMS**.
+2. Select the [Project](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) where you want to add the video.
+3. Choose a page to add the video, e.g. **Home**.
+4. With the **Home** page open, in the **Sections** tab, add (`+`) a section that has the `media-gallery` Widget, e.g. Hero.
+5. In the Hero fill the following fields:
+
+- **URL address**: paste the URL that you copied from the Media.
+- **Video description**: Image description for accessibility.
+
+6. Click `Save`. 
+7. If you want to check your changes before publishing it, click `Preview`.
+
+### Canceling an upload
+
+- **Images**
+
 If you are uploading a new image and do not want to continue, you can cancel the upload by clicking the `X` overlay on the image thumbnail.
 
+- **Videos**
+
+Once you have uploaded the video, hover over the video's thumbnail, click on the menu (`⋮`), and choose **Delete**. If this video is already in use somewhere in your store, it will remain there, but it won't be available for future use. 
+
diff --git a/docs/tutorials/en/mercado-libre-size-chart.md b/docs/tutorials/en/mercado-libre-size-chart.md
new file mode 100644
index 000000000..4bbfe5513
--- /dev/null
+++ b/docs/tutorials/en/mercado-libre-size-chart.md
@@ -0,0 +1,20 @@
+---
+title: 'Mercado Libre size chart'
+id: 5dCc9IJ83SjllG75BVCWnr
+status: PUBLISHED
+createdAt: 2024-07-23T20:28:35.058Z
+updatedAt: 2024-07-23T21:11:23.954Z
+publishedAt: 2024-07-23T21:11:23.954Z
+firstPublishedAt: 2024-07-23T21:11:23.954Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: mercado-libre-size-chart
+locale: en
+legacySlug: mercado-libre-size-chart
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning">
+  This is a regional exclusive content not applicable to English speaking countries.
+  </div>
diff --git a/docs/tutorials/en/merchandising-rule-conditions.md b/docs/tutorials/en/merchandising-rule-conditions.md
new file mode 100644
index 000000000..7e1e385c4
--- /dev/null
+++ b/docs/tutorials/en/merchandising-rule-conditions.md
@@ -0,0 +1,32 @@
+---
+title: 'Merchandising rule conditions'
+id: 4K9WCBiQ4ndU396ZygDpc2
+status: PUBLISHED
+createdAt: 2024-06-27T17:17:15.295Z
+updatedAt: 2024-06-27T17:19:47.360Z
+publishedAt: 2024-06-27T17:19:47.360Z
+firstPublishedAt: 2024-06-27T17:18:32.359Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: merchandising-rule-conditions
+locale: en
+legacySlug: merchandising-rule-conditions
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+In the [Manual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) and the [Visual Editor (beta)](https://help.vtex.com/en/tutorial/creating-merchandising-rules-visual-editor-beta--6xteumx9MsDt0uEppbChu3), the merchandising rule conditions follow the `{criterion} {operator} {value}` format. For example, a condition may be `brand is athletic`, in which `brand` corresponds to the criterion, `is` to the operator, and `athletic` to the value.
+
+Learn about the criteria and possible operators for each type of editing in the following tables:
+
+## Criteria
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"> <thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Name</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operators</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Types of editing</th> </tr> </thead> <tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span></td> <td rowspan="2" class="t-body pa5">Word searched by the customer that will be related to the rule. Open input field.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td rowspan="2" class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br>Customization rules </td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contains</span></td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Searches for the exact ID of a catalog element related to the rule. Possible IDs are: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong>, and <strong>EAN</strong>. Open input field.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Customization rules</td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">category</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a category added to the store's catalog. </td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">department</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a department added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">brand</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a brand added to the store's catalog. </td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">productclusternames</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a collection added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promotion</span></td> <td rowspan="2" class="t-body pa5">Selectable value that validates if there is at least one promotion linked to the item (<span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">yes</span>).</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sellername</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents the name of a seller.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategory</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a subcategory added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{specification}}</span></td> <td rowspan="2" class="t-body pa5">Any active catalog specification appears as a custom criterion, with the same possible values. The name of the criterion is exactly the name of the added specification. For example, if there is an active specification called <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>, the displayed criterion is <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> </tbody></table>
+
+<div class="alert alert-warning">
+  <p>The <code>department</code>, <code>category</code>, and <code>subcategory</code> criteria only appear as options to be included in Merchandising Rules if all three category levels are previously configured in the <strong>Catalog</strong>.</p>
+</div>
+
+## Operators
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"><thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Name</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Criteria</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Example</th> </tr></thead><tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">If you create a rule in the Manual Editor using <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span> as a criterion, it will return search results with exact words.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span></td> <td class="t-body pa5">If you add <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> and a customer searches for <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span>, the merchandising rule is triggered. However, if the customer searches for <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday promotion</span>, the rule will not be triggered.<br> </td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">In other editing scenarios, it enables other conditions than the current one to also be applied.</td> <td class="t-body pa5">All (except for <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span>)</td> <td class="t-body pa5">If the condition is brand is <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>, even if the customer selects <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">hotsport</span>, <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sportist</span>, and <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span> in the search, the merchandising rule will be triggered.</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contains</span></td> <td class="t-body pa5">When creating a rule in the Manual Editor using <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span> as a criterion, it generates search results that are not limited to exact words.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span></td> <td class="t-body pa5">If you add <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> and a customer searches for <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> or similar expressions such as <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday promotion</span>, the merchandising rule will be triggered.</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5">Limits the filter to the one that you added.</td> <td class="t-body pa5">All (except for <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span>)</td> <td class="t-body pa5">If the condition is brand is <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>, and the customer selects <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">hotsport</span> first in the search, even if they select <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span> later, the merchandising rule will not be triggered. It will only work if the first brand filter selected is <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>.</td> </tr></tbody></table>
diff --git a/docs/tutorials/en/merchandising-rules-list.md b/docs/tutorials/en/merchandising-rules-list.md
new file mode 100644
index 000000000..392f619a2
--- /dev/null
+++ b/docs/tutorials/en/merchandising-rules-list.md
@@ -0,0 +1,71 @@
+---
+title: 'Merchandising rules list'
+id: 3CZOjyie1LZVOhzeviVCgu
+status: PUBLISHED
+createdAt: 2024-07-03T17:08:55.426Z
+updatedAt: 2024-07-03T17:10:24.720Z
+publishedAt: 2024-07-03T17:10:24.720Z
+firstPublishedAt: 2024-07-03T17:10:24.720Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: merchandising-rules-list
+locale: en
+legacySlug: merchandising-rules-list
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+On VTEX Admin, the page **Storefront** > **Intelligent Search** > **Merchandising Rules** allows you to do the following actions: 
+
+* [Create](#creating-merchandising-rules)
+* [Search](#searching-merchandising-rules)
+* [Edit](#editing-merchandising-rules)
+* [Delete](#deleting-merchandising-rules)
+
+![merch-rules-en](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/6b6dc34a4127cd654dab40fa17a70664/merch-rules-en.PNG)
+
+The page displays the following information: 
+
+| Column | Description |
+| - | - |
+| __Name__ | Name that identifies the merchandising rule, defined in the "[Creating merchandising rules](#creating-merchandising-rules)" section. |
+| __Start date__ | Date that sets the date the merchandising rule becomes available. |
+| __End date__ | Date that sets the date the merchandising rule is no longer available. |
+| __Type__ | Indicates the [type of editing](#type-of-editing) used in the merchandising rule. |
+| __Active__ | Option that enables or disables a merchandising rule. |
+| __Actions__ <i class="fas fa-ellipsis-v"></i>| Menu with actions to `Edit` or `Delete` a merchandising rule. |
+
+## Creating merchandising rules
+
+To add a new merchandising rule, click `+ New`. Learn more about all the information needed to create a merchandising rule in the sections below.
+
+### Types of editing
+
+There are two types of editor to create or modify Merchandising rules: the [Manual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) and the [Visual Editor](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr).
+
+Below are the features of each editor:
+
+| Feature | Description | Manual Editor | Visual Editor |
+|---|---|---|---|
+| Trigger rules | Set conditions for the merchandising rule to be triggered. | Yes | Yes |
+| Customization Rules | Control search results using specific conditions. | Yes | No |
+| Preview | Preview how search results will be displayed to customers while navigating the store. | No | Yes |
+| Reorder search results | Change the order of the items listed as search results. | No | Yes |
+| Pin products to the top positions | Determine that a given item in a search result will always be displayed in the top position among search results. | No | Yes |
+
+## Searching for merchandising rules
+
+Enter the name of the merchandising rule in the search bar to search for a merchandising rule.
+
+## Editing merchandising rules
+
+You can edit the information in a merchandising rule by following the steps below.
+
+1. Click the menu <i class="fas fa-ellipsis-v"></i> in the row of the merchandising rule, then click <i class="fas fa-pencil-alt"></i> `Edit`.
+2. Change the information you want in the merchandising rule.
+3. Click `Save`.
+
+## Deleting merchandising rules
+
+You can delete a merchandising rule by clicking the menu <i class="fas fa-ellipsis-v"></i> in the row of the merchandising rule, then <i class="fas fa-trash"></i> `Delete`.
+
diff --git a/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md b/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md
new file mode 100644
index 000000000..3e6fa6c03
--- /dev/null
+++ b/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md
@@ -0,0 +1,43 @@
+---
+title: 'Metrics are not displayed in the order dashboard'
+id: 1B5OAicmK3AvnwPzs4iq7Z
+status: PUBLISHED
+createdAt: 2024-06-10T11:28:08.507Z
+updatedAt: 2024-06-10T17:15:44.616Z
+publishedAt: 2024-06-10T17:15:44.616Z
+firstPublishedAt: 2024-06-10T17:15:44.616Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: metrics-are-not-displayed-in-the-order-dashboard
+locale: en
+legacySlug: metrics-are-not-displayed-in-the-order-dashboard
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Keywords:** *dashboard, admin dashboard, overview, update, role.*
+
+When accessing the Admin dashboard, it may fail to load metrics in the **Overview** dashboard, indicated by warning icons and the message "Something went wrong". This can be due to:
+
+- **Delay in updating data:** There may be a delay in updating the information displayed on the dashboard.
+- **Inadequate comparison period:** The period selected in the top right corner of the dashboard may not contain sufficient order data for comparison.
+- **Insufficient access permissions:** You might not have the necessary role to view certain information on the dashboard.
+
+![Visão geral - EN](//images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/92d249251094dd01515b571876066e7c/Vis_o_geral_-_EN.png)
+
+## Solution
+To solve inconsistencies in the initial dashboard of the Admin, you can try the following:
+
+### Adjust the comparison period
+Adjusting the comparison period can solve the issue by displaying relevant metrics. To ensure the selected period in the **Overview** dashboard contains valid order data, follow these steps:
+
+1. In the VTEX Admin, go to **Dashboard > Overview**.
+2. In the top right corner, select the comparison period.
+
+![Dashboard - EN](//images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/a8aee6d86d8db48453f20cc8d9be48b7/Dashboard_-_EN.png)
+
+### Wait for information to be updated
+Please allow 10 to 80 minutes for the information to be updated on the dashboard. This period is necessary for the data to be processed and displayed correctly. For more information about the waiting time, see [Comparing periods](https://help.vtex.com/en/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ?&utm_source=autocomplete).
+
+### Check access permissions
+To view the information on the dashboard, make sure that your role contains the **Insights Metrics** [resource](https://help.vtex.com/en/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3). For more information about roles and how to configure them, see [Roles](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/tutorials/en/minimum-stock-control-for-integrations.md b/docs/tutorials/en/minimum-stock-control-for-integrations.md
index 604f0bf30..8666f1528 100644
--- a/docs/tutorials/en/minimum-stock-control-for-integrations.md
+++ b/docs/tutorials/en/minimum-stock-control-for-integrations.md
@@ -40,7 +40,7 @@ To set the minimum inventory for your integration, follow the steps below:
 2. In the Marketplace > Connection menu, click on **Integrations**.
 3. Select the **Settings** option.
 4. Choose the integration you want to configure.
-5. Then, click on the gears icon <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+5. Then, click on the gears icon <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 6. Select the **Edit Config** option.
 7. In the **Minimum inventory** field, enter the desired value.
 8. **Save** your changes.
diff --git a/docs/tutorials/en/mode-off-faq.md b/docs/tutorials/en/mode-off-faq.md
index e1e1f926d..b7cf3abb2 100644
--- a/docs/tutorials/en/mode-off-faq.md
+++ b/docs/tutorials/en/mode-off-faq.md
@@ -1,10 +1,10 @@
 ---
 title: 'Mode-Off: FAQ'
 id: 6hbd7PuvoxuRbPCvTqjxeB
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-01-21T17:29:10.793Z
-updatedAt: 2021-04-06T20:20:55.582Z
-publishedAt: 2021-04-06T20:20:55.581Z
+updatedAt: 2024-04-11T19:26:47.407Z
+publishedAt: 2024-04-11T19:22:34.569Z
 firstPublishedAt: 2021-01-21T17:54:12.941Z
 contentType: tutorial
 productTeam: Financial
@@ -51,9 +51,10 @@ Transactions shall be resumed when the partner stops experiencing a rate of five
 
 ## For how long VTEX runs processing reattempts for transactions on standby?
 
-Each partner defines the retry time during their integration with the Payment Provider Protocol. 
+The time between transaction processing reattempts (_retries_) can be defined by the partner when sending payment information. When configuring the payment cancellation time (`delayToCancel` field) for a period of less than 1 day, retry attempts will be made every 1 hour. If the time to cancel the payment is set to be equal to or greater than 1 day, retry attempts will be made every 4 hours. For more information, visit [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol?endpoint=post-/payments).
 
-In case you haven’t previously defined it, the default time is __four hours__.
+<div class="alert alert-info">
+ If payment is made by <a href="https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf">PIX (Brazilian instant payment method)</a> or the payment cancellation time is set between 5 minutes and 1 hour, retry calls will occur every 5 minutes.</div>
 
 ## How to identify the mode-off? What to do if it is active?
 
diff --git a/docs/tutorials/en/moving-order-to-start-handling-shipping.md b/docs/tutorials/en/moving-order-to-start-handling-shipping.md
index 747dc463c..7e51f2d4d 100644
--- a/docs/tutorials/en/moving-order-to-start-handling-shipping.md
+++ b/docs/tutorials/en/moving-order-to-start-handling-shipping.md
@@ -3,8 +3,8 @@ title: 'Moving order to Handling Shipping'
 id: tutorials_198
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:17.090Z
-updatedAt: 2023-03-31T14:47:04.890Z
-publishedAt: 2023-03-31T14:47:04.890Z
+updatedAt: 2023-06-15T13:32:59.728Z
+publishedAt: 2023-06-15T13:32:59.728Z
 firstPublishedAt: 2017-04-27T23:02:47.756Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,10 +21,12 @@ The reservation clearing does not happen automatically. It should be controlled
 
 See below for possible ways to update this status.
 
-## Through integration
+## Through integration and API
 
 Integrations automate this process. They happen when other systems consult VTEX order to track the shipment flow. This integration can be done via API REST, according to our [ERP integration guide](https://developers.vtex.com/docs/erp-integration-set-up-order-processing).
 
+Once that is done, you will be able to call the API [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
+
 ## Through VTEX Admin
 
 If the store doesn't have an ERP or some system that integrates the orders, it's possible to manually move the flow to the next stages. The step-by-step for that is described below:
diff --git a/docs/tutorials/en/multilevel-omnichannel-inventory.md b/docs/tutorials/en/multilevel-omnichannel-inventory.md
index 3d7323808..ca4a36a48 100644
--- a/docs/tutorials/en/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/en/multilevel-omnichannel-inventory.md
@@ -3,24 +3,24 @@ title: 'Multilevel Omnichannel Inventory'
 id: 7M1xyCZWUyCB7PcjNtOyw4
 status: PUBLISHED
 createdAt: 2020-11-30T19:44:58.255Z
-updatedAt: 2023-04-19T00:59:40.265Z
-publishedAt: 2023-04-19T00:59:40.265Z
+updatedAt: 2024-07-24T14:21:41.092Z
+publishedAt: 2024-07-24T14:21:41.092Z
 firstPublishedAt: 2020-12-08T19:12:43.325Z
 contentType: tutorial
-productTeam: Shopping
-author: 127RQ7SUoFfyTh5gbXUpdM
+productTeam: Channels
+author: 0QBQws7rk0t5Mnu8fgfUv
 slug: multilevel-omnichannel-inventory
 locale: en
 legacySlug: recursive-marketplace-v2
-subcategory: 6riYYNZCpO8wyksi8Ksgyq
+subcategory: 5RAUzLD6X9Wa1maenj1eGA
 ---
 
-_Multilevel Omnichannel Inventory_ (formerly called Recursive Marketplace) is the configuration on the VTEX platform that allows a master account to make the inventory from [white label sellers](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) and [franchise accounts](https://help.vtex.com/en/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) available for sale on marketplaces. This article covers the following information about the feature:
+__Multilevel Omnichannel Inventory__ is the configuration on the VTEX platform that allows a master account to make the inventory from [white label sellers](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) and [franchise accounts](https://help.vtex.com/en/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) available for sale on marketplaces. This article covers the following information about the feature:  
 
-* [Account Architecture](#account-architecture)
-* [Benefits](#benefits)
-* [Restrictions](#restrictions)
-* [How to configure it](#how-to-configure-it)
+* [Account Architecture](#account-architecture)  
+* [Benefits](#benefits)  
+* [Restrictions](#restrictions)  
+* [How to configure it](#how-to-configure-it)  
 
 <div class="alert alert-info">
 Read our <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory">Developer Portal</a> article to learn more about the Multilevel Omnichannel Inventory order architecture and how to configure it via REST API. 
@@ -30,7 +30,7 @@ Read our <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omni
 
 The [marketplace](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) is the environment where the product is sold, also called storefront, whereas the [seller](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#selling-on-marketplaces) owns the inventory and ships the orders.  
 
-When stores sell their products in a marketplace, we have a single-level relationship between seller and marketplace. But VTEX's architecture allows stores to operate both as marketplaces and sellers, expanding the range of possible combinations. 
+When stores sell their products in a marketplace, we have a two-level relationship between seller and marketplace. But VTEX's architecture allows stores to operate both as marketplaces and sellers, expanding the range of possible combinations. 
 
 A main account seller may act as a marketplace for [white-label](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) sellers. This is the case of store chains configured as [franchise accounts](https://help.vtex.com/en/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa?&utm_source=help) and physical stores, which are, by definition, sellers in another VTEX store. 
 
@@ -38,7 +38,7 @@ The main seller may also sell its products in a marketplace.
 
 In this case, there is a three-tier architecture between the marketplace, the main seller, and its white-label sellers, as shown in the image below.
 
-![Arquitetura Multilevel omichannel inventory](https://images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/fd36e953d3a8f70d068bcd69991e998c/Screen_Shot_2022-09-30_at_18.57.26.png)
+![Arquitetura Multilevel omichannel inventory](//images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/fd36e953d3a8f70d068bcd69991e998c/Screen_Shot_2022-09-30_at_18.57.26.png)
 
 By default, products from physical stores, or white-label sellers (level 3 in the image), are not available for selling in the marketplace (level 1 in the image). But you can make them available using the _Multilevel Omnichannel Inventory_ capability. 
 
@@ -69,11 +69,9 @@ To learn more details about order architecture applied in Multilevel Omnichannel
 
 Some of the features available in the traditional marketplace model are not available for a _Multilevel Omnichannel Inventory_ scenario. It is important to understand these restrictions before enabling the configuration.
 
-### External marketplaces
+### Availability
 
-You can configure this feature on [VTEX marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace), [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), and [certified partners](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner). Even though they support the feature, it is not automatically available for these marketplaces, so you need to configure and adapt the integration for each one. This applies to newly integrated marketplaces and those already using the fulfillment API, which is restricted to two levels. Learn more in the [How to configure it](#how-to-configure-it) section, or in our [article on the Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). 
-
-Multilevel Omnichannel Inventory can cause integration errors when applied to non-VTEX marketplaces. In these scenarios, the order ID will change, for example. We recommend checking with your development team to ensure a seamless migration. Learn more in our [article on the Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). 
+This Multilevel Omnichannel Inventory feature is only available for [VTEX marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace). To use it, the marketplace (level 1) must configure it for each direct seller (level 2) they want to include. You can do this by adding new sellers or editing the configuration of existing sellers in your store. Learn more in the [How to configure it](#how-to-configure-it) section, or in our [article on the Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
 
 ### Splitting payouts
 
@@ -87,7 +85,11 @@ Note that when direct sellers are not responsible for white-label sellers’ pay
 
 ### Payment methods
 
-Once the configuration is done, only marketplace payment methods will be displayed as an option at checkout. Payment methods from direct sellers (level 2) and white-label sellers (level 3) are not imported to the account architecture. Therefore, the checkout only displays the marketplace's payment methods, even if the direct seller's affiliate is configured to use their payment methods. The franchise account [affiliate](https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187) should always have the flag for using payment methods unchecked. 
+Once the configuration is done, only marketplace payment methods will be displayed as an option at checkout. Payment methods from direct sellers (level 2) and white-label sellers (level 3) are not imported to the account architecture. Therefore, the checkout only displays the marketplace's payment methods, even if the direct seller's affiliate is configured to use their payment methods.  
+
+<div class="alert alert-warning">
+The franchise account <a href="https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187">affiliate</a> must always have the setting for using payment methods disabled.
+</div>
 
 ### Changing sellers
 
@@ -95,9 +97,7 @@ If a white-label seller (level 3) is assigned to fulfill an order and rejects it
 
 ### Stores editing completed orders
 
-VTEX Stores cannot change orders made in VTEX marketplaces when they were placed in a Multilevel Omnichannel Inventory scenario. It is necessary to cancel the order and create a new one.
-
-However, VTEX stores can change chain orders made in external marketplaces. For more information, see [Change chain orders in external marketplaces](https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces).
+VTEX Stores cannot change orders made in VTEX marketplaces when they were placed in a Multilevel Omnichannel Inventory scenario. It is necessary to cancel the order and create a new one. For more information, see [Change chain orders in external marketplaces](https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces).
 
 ### Customers editing completed orders
 
@@ -105,10 +105,10 @@ Customers cannot change orders in the **My Orders** section. Changes can only be
 
 ### Manual Price
 
-The Manual Price feature does not apply to Multilevel Omnichannel Inventory. Therefore, you cannot manually change prices in the cart, so you have to update prices via: 
+The Manual Price feature does not apply to Multilevel Omnichannel Inventory. Therefore, you cannot manually change prices in the cart, so you have to update prices via:  
 
 - [ERP Integration](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide)   
-- [Pricing API REST](https://developers.vtex.com/vtex-rest-api/reference/createupdatepriceorfixedprice). 
+- [Pricing API REST](https://developers.vtex.com/vtex-rest-api/reference/createupdatepriceorfixedprice).  
 - [Pricing page in the VTEX Admin](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)  
 
 ### New user information
@@ -123,9 +123,17 @@ A marketplace (level 1) cannot configure the display of prices and availability
 
 The use of [coupons](https://help.vtex.com/en/tutorial/cupons-beta--1aAEN3ADpz19ss5JCIEBdL), [gift cards](https://help.vtex.com/en/tutorial/gift-card--tutorials_995) and benefits linked to [UTMs](https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) are restricted to marketplaces (level 1). The ones configured on direct sellers (level 2) and franchise accounts or white-label sellers (level 3) will not be applied. 
 
+### Orders integrated asynchronously with price divergence
+
+The store is unable to process orders that have been integrated asynchronously with divergent values for Multilevel Omnichannel Inventory. The [Order Authorization](https://help.vtex.com/en/tutorial/como-funciona-a-autorizacao-de-pedidos--3MBK6CmKHAuUjMBieDU0pn) feature does not support [price divergence rules](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW#) for this scenario. 
+
+### Price Table
+
+You can't create price tables using the [Price Table](https://help.vtex.com/en/tutorial/criar-tabelas-de-precos--58YmY2Iwggyw4WeSCGg24S) feature. Prices must be entered via integration with the ERP or via spreadsheets. 
+
 ## How to configure it
 
-The marketplace must configure the Multilevel Omnichannel Inventory in the VTEX Admin or via the [Rest API](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). This configuration can be done for integrated sellers and newly integrated ones. 
+The marketplace must configure the __Multilevel Omnichannel Inventory__ in the VTEX Admin or via the [Rest API](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). This configuration can be done for integrated sellers and newly integrated ones. 
 
 <div class="alert alert-info">
 Note that the marketplace must configure the Multilevel Ominichannel Inventory for each direct seller (level 2) to which they want to apply the feature, but not for each white-label seller or franchise account (level 3).
@@ -135,22 +143,20 @@ Note that the marketplace must configure the Multilevel Ominichannel Inventory f
 
 The marketplace should follow the steps below to configure it on already integrated sellers:
 
-   1. In the Marketplace section in your VTEX Admin, go to the **Sellers** tab.  
-   2. Click on **Seller Management**.  
-   3. In the row corresponding to the seller whose white-label sellers you want to view, click `Change/View`.
-   4. Fill in the **Fulfillment EndPoint** field following the example:  
-`https://{{sellerAccount}}.vtexcommercestable.com.br/api/checkout?affiliateid={{affiliateId}}&sc={{tradePolicyId}}`  
-   5. Replace the fields that are between curly brackets with the values described below, removing the curly brackets:   
+1. In the VTEX Admin, go to **Marketplace > Sellers > Management.**
+2. In the row corresponding to the seller whose white label sellers you want to view, click <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Click Seller Details.
+4. Fill in the **Fulfillment EndPoint** field following the example: `https://{{sellerAccount}}.vtexcommercestable.com.br/api/checkout?affiliateid={{affiliateId}}&sc={{tradePolicyId}}`  
+5. Replace the fields that are between curly brackets with the values described below, removing the curly brackets:  
 
     - **sellerAccount**: The seller’s [account name](https://help.vtex.com/en/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) on the VTEX platform.   
     - **affiliateId**: Three-digit code corresponding to the [affiliate](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) created by the seller. The seller should report this value to the marketplace.   
     - **tradePolicyId**: [Trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) ID created by the seller in its own VTEX environment to sell in the marketplace. The seller must report this value to the marketplace.   
-
-   6. Click `Save`.  
+6. Click **Save.**  
 
 ### Newly integrated sellers
 
-If the marketplace wants to [add a new seller](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392) configuring a Multilevel Omnichannel Inventory from scratch, please follow the instructions in [Add seller](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392), and fill in the `Fulfillment Endpoint` field following steps 4 and 5 of the tutorial in the [Integrated sellers section](#integrated-sellers). 
+If the marketplace wants to [add a new seller](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392) configuring a Multilevel Omnichannel Inventory from scratch, please follow the instructions in [Add seller](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392), and fill in the `Fulfillment Endpoint` field following steps 4 and 5 of the tutorial in the [Integrated sellers section](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#integrated-sellers). 
 
 ### Example
 
diff --git a/docs/tutorials/en/my-ad-is-not-displayed-on-mercado-livre.md b/docs/tutorials/en/my-ad-is-not-displayed-on-mercado-livre.md
new file mode 100644
index 000000000..eab84901b
--- /dev/null
+++ b/docs/tutorials/en/my-ad-is-not-displayed-on-mercado-livre.md
@@ -0,0 +1,19 @@
+---
+title: 'My ad is not displayed on Mercado Livre'
+id: 2UpudfowEvG97e2lstj4qc
+status: PUBLISHED
+createdAt: 2024-06-13T16:38:00.931Z
+updatedAt: 2024-06-13T18:11:28.836Z
+publishedAt: 2024-06-13T18:11:28.836Z
+firstPublishedAt: 2024-06-13T18:01:04.982Z
+contentType: tutorial
+productTeam: Channels
+author: YRJ73j8mt38D5TUleocQB
+slug: my-ad-is-not-displayed-on-mercado-livre
+locale: en
+legacySlug: my-ad-is-not-displayed-on-mercado-livre
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
+English speaking countries.</div>
diff --git a/docs/tutorials/en/my-inventory-is-negative.md b/docs/tutorials/en/my-inventory-is-negative.md
new file mode 100644
index 000000000..c2a60f095
--- /dev/null
+++ b/docs/tutorials/en/my-inventory-is-negative.md
@@ -0,0 +1,34 @@
+---
+title: 'My inventory is negative'
+id: JSFHaWsASXbnrX9dgNEeP
+status: PUBLISHED
+createdAt: 2024-06-10T11:08:39.990Z
+updatedAt: 2024-06-10T17:21:47.755Z
+publishedAt: 2024-06-10T17:21:47.755Z
+firstPublishedAt: 2024-06-10T17:21:47.755Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: my-inventory-is-negative
+locale: en
+legacySlug: my-inventory-is-negative
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Keywords:** *inventory, reservation, trade policy, VTEX Admin, inventory management.*
+
+When the product available quantity is displayed as negative, it may indicate that the number of items [reserved](https://help.vtex.com/en/tutorial/como-a-reserva-funciona--tutorials_92) exceeds the total quantity in stock. This problem usually happens when an order item is deducted from the inventory while still being reserved by the system.
+
+## Solution
+
+The item's inventory information must be updated to reflect the items in stock. Thus, the recorded value of available items should be the sum of available items plus the items that are reserved and not yet in the **Handling Shipping** status.
+
+To update the number of available items, follow the steps below:
+
+1. In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type **Inventory Management** in the search bar at the top of the page.
+2. Click **Inventory Management**.
+3. Search for the desired SKU.
+4. In the **Update Count** column, enter the correct number of items in stock, considering the sum of the available items plus the reserved ones.
+5. Click **Save**.
+
+When two or more inventories use the same [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV), and one has a negative number of items, the SKU will be unavailable for sale, even if items are available in one of the [inventories](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139).
diff --git a/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md b/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md
new file mode 100644
index 000000000..f187f4e66
--- /dev/null
+++ b/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md
@@ -0,0 +1,20 @@
+---
+title: 'My orders in Mercado Libre have errors'
+id: 170njWgSw9UQ5DG6NRl14d
+status: PUBLISHED
+createdAt: 2024-06-28T15:03:26.959Z
+updatedAt: 2024-06-28T16:08:10.242Z
+publishedAt: 2024-06-28T16:08:10.242Z
+firstPublishedAt: 2024-06-28T16:04:14.266Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: my-orders-in-mercado-libre-have-errors
+locale: en
+legacySlug: my-orders-in-mercado-libre-have-errors
+subcategory: 2LcLWCYaEm5qPmOuYUiKIS
+---
+
+<div class="alert alert-warning">
+  This is a regional exclusive content not applicable to English speaking countries.
+  </div>
diff --git a/docs/tutorials/en/my-store-order-was-not-created.md b/docs/tutorials/en/my-store-order-was-not-created.md
new file mode 100644
index 000000000..ad151e24e
--- /dev/null
+++ b/docs/tutorials/en/my-store-order-was-not-created.md
@@ -0,0 +1,64 @@
+---
+title: 'My store order was not created'
+id: 7xQZqkMHXkHCEEZl5UlX8I
+status: PUBLISHED
+createdAt: 2024-07-18T20:10:20.933Z
+updatedAt: 2024-07-18T20:56:20.706Z
+publishedAt: 2024-07-18T20:56:20.706Z
+firstPublishedAt: 2024-07-18T20:56:20.706Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: my-store-order-was-not-created
+locale: en
+legacySlug: my-store-order-was-not-created
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags / Keywords:** order, order integration, XML integration, product configuration, negative inventory, out-of-stock.
+
+When a customer tries to buy a product and an error occurs in creating the order, it can be due to different reasons, such as payment problems, logistics issues, or [backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) with ERPs (Enterprise Resource Planning).
+
+Before considering complex causes for errors with orders that were not created, try the troubleshooting processes presented in this article. Some of the most common error scenarios are:
+
+* The item was not available in the [inventory](https://help.vtex.com/en/tutorial/inventory-management--tutorials_139), and the store was not configured to sell _out-of-stock_ products.
+* The XML integration was not configured to send information about _out-of-stock_ products.
+
+## Solutions
+
+Consider the following troubleshooting processes for order creation errors:
+
+* [Manage inventory](#manage-inventory): If you have no items for the product in your inventory and your store is not configured to sell _out-of-stock_ products.
+* [Review XML integration](#review-xml-integration): If your XML integration is not configured to send information about products with no inventory.
+
+### Manage inventory
+
+There are two ways to manage your [inventory](https://help.vtex.com/en/tutorial/inventory-management--tutorials_139):
+
+* **Via API:** Using the endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
+* **Via VTEX Admin:** Accessing _Catalog > Inventory > Inventory Management_.
+
+The following solutions focus on inventory management via VTEX Admin:
+
+* **Update inventory count:** In the line that corresponds to the desired SKU and warehouse, on the _Update Count_ column, type the number of items available for sales, and click `Save`. This number cannot be negative, otherwise you will have a [negative inventory](https://help.vtex.com/en/faq/why-is-my-stock-negative--frequentlyAskedQuestions_159).
+* **Configure Infinite Inventory:** In the line that corresponds to the desired SKU and warehouse, on the _Infinite Inventory_ column, turn on the switch, and click `Save`. When this configuration is activated, the item is considered always available for sales and the store never runs _out-of-stock_ for it.
+
+<div class = "alert alert-info">
+To configure <i>out-of-stock</i> products to be displayed in your storefront, in your VTEX Admin access <b>Catalog > All Products</b>, and in the product configuration page, in the <b>Product</b> tab, select the checkbox <b>Yes</b> for <i>Show when out of stock</i>.
+</div>
+
+### Review XML integration
+
+XML is a markup language that defines and stores data in a shareable manner. When your [store’s XML integration](https://help.vtex.com/en/tutorial/configurando-xml--tutorials_242) is not set for certain configurations, it might not be able to export a product information.
+
+An error with product missing information can happen when the product has no inventory and the integration is not set for sending _out-of-stock_ products. To activate the configuration, follow the steps below:
+
+1. In the VTEX Admin, go to **Store Settings > Channels > XML Integration** or type **XML Integration** in the search bar at the top of the page.
+2. In the line of the desired XML integration, click `Edit`.
+3. In the `Edit XML` tab, for the option **Show unavailable SKUs**, select the checkbox `Show out-of-stock (sold-out) SKUs in the results`.
+4. Click `Save`.
+
+<div class="alert alert-warning">
+You can have invoicing errors when trying to invoice an order with incorrect or missing XML information.
+</div>
+
diff --git a/docs/tutorials/en/names-of-vtex-branches-worldwide.md b/docs/tutorials/en/names-of-vtex-branches-worldwide.md
index 48bd58f59..1678094f4 100644
--- a/docs/tutorials/en/names-of-vtex-branches-worldwide.md
+++ b/docs/tutorials/en/names-of-vtex-branches-worldwide.md
@@ -29,4 +29,4 @@ VTEX is proud to have offices and clients around the world. Each country office
 
 To know which country office you are invoiced from, consult your contract or [download your invoice](https://help.vtex.com/en/tutorial/como-fazer-download-faturas-da-VTEX--tutorials_653). When you open an invoice, you will find the company name and address from which your store is being invoiced in the left corner of your invoice, below VTEX’s logo.  
 
-![reconhecimento fatura](https://images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
+![reconhecimento fatura](//images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
diff --git a/docs/tutorials/en/navigation.md b/docs/tutorials/en/navigation.md
new file mode 100644
index 000000000..883e5fa17
--- /dev/null
+++ b/docs/tutorials/en/navigation.md
@@ -0,0 +1,208 @@
+---
+title: 'Navigation Data Pipeline (Beta)'
+id: 4X4hK0zdIHN0Xn5x2MLYYd
+status: PUBLISHED
+createdAt: 2024-02-02T17:48:16.639Z
+updatedAt: 2024-06-21T16:24:13.980Z
+publishedAt: 2024-06-21T16:24:13.980Z
+firstPublishedAt: 2024-05-27T19:26:59.542Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: navigation
+locale: en
+legacySlug: navigation
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+The navigation dataset operates with two main tables: `pageviews` and `sessions`. A `pageview` refers to each new page that a user accesses while browsing a store, while a `session` is the set of all pageviews made by a user in a single visit.
+Each `session` remains active until no new `pageviews` occur for a period of 30 minutes.
+
+<div class="alert alert-warning">
+The navigation dataset does not capture all types of events that occur during browsing. For example, specific clicks, special events, and interactions with the mini cart are not recorded.
+  </div>
+
+This section includes the following information:
+
+- [Characteristics of navigation data](#data-characteristics)
+- [Table: sessions](#table-sessions)
+- [Table: pageviews](#table-sessions)
+- [Analyses with navigation data](#analyses-with-item-inventory)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics
+
+| Characteristic | Description |
+|:---:|:---:|
+| Data source | The data in this set comes from a script that runs on the store frontend and logs user session information and activity. |
+| Availability | Navigation data can be accessed through the [Overview dashboard](https://help.vtex.com/en/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ#dados) in the VTEX Admin, with a focus on total sessions and the conversion funnel, or also through third-party tools such Google Analytics. |
+| History | The data is retained for two years, starting 2022 for clients who already use the VTEX platform. |
+| Minimum update interval | One hour. |
+
+<div class="alert alert-warning">
+  Data Pipeline only provides data from sessions originating from VTEX storefront solutions: Legacy CMS, Store Framework, and FastStore. VTEX does not have access to sessions originating from third-party marketplaces or proprietary storefronts. Furthermore, storefront customizations   may interfere with or even disable the script, resulting in some sessions not being recorded, or in discrepancies in the conversion rate observed in the dashboard.
+To minimize the impact on store performance, the script is configured to be the last element to load on the page. This means that very brief sessions may not be captured.
+</div>
+
+## Table: sessions
+
+This table only contains closed sessions, whether due to inactivity or because a purchase was completed. It's sorted by `session_id`, `session_end_time`, and `store_name`. Avoid filtering large data ranges by columns that are not part of this sorting strategy. The table fields are described below:
+
+| **Column name** | **Field type** | **Description** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | Control ID of data ingestion. |
+| **session_id** | character varying(127) | Session UUID, corresponding to the VtexRCSessionIdv7 cookie. |
+| **store_name** | character varying(127) | Name of the store that generated the page views for this session. |
+| **account_name** | character varying(127) | VTEX account of the store that is generating this session. |
+| **economic_group_id** | character varying(127) | Identifier of the economic group used for billing. |
+| **economic_group_name** | character varying(1024) | Name of the economic group used for billing. |
+| **company_id** | character varying(127) | Company identifier for billing. |
+| **company_name** | character varying(1024) | Name of the company for billing. |
+| **main_account_name** | character varying(127) | Name of the main VTEX account related to the store generating this session. |
+| **os_family** | character varying(1023) | Operating system family, extracted from user_agent. |
+| **os_major** | character varying(1023) | Major operating system version, extracted from user_agent. |
+| **os_minor** | character varying(1023) | Minor operating system version, extracted from user_agent. |
+| **os_patch** | character varying(1023) | Operating system patch, extracted from user_agent. |
+| **os_patch_minor** | character varying(1023) | Minor operating system patch, extracted from user_agent. |
+| **device_brand** | character varying(1023) | Device brand, extracted from user_agent. |
+| **device_family** | character varying(1023) | Device family, extracted from user_agent. |
+| **device_model** | character varying(1023) | Device model, extracted from user_agent. |
+| **browser_family** | character varying(1023) | Browser family, extracted from user_agent. |
+| **browser_major** | character varying(1023) | Major browser version, extracted from user_agent. |
+| **browser_minor** | character varying(1023) | Minor browser version, extracted from user_agent. |
+| **browser_patch** | character varying(1023) | Browser patch, extracted from user_agent. |
+| **user_id** | character varying(16383) | Unique identifier of the buyer, mapped by the VtexRCMacIdv7 cookie. |
+| **pageviews_count** | integer | Count of page views in this session. |
+| **views_home** | integer | Count of home page views in this session. |
+| **views_category** | integer | Count of [category](https://help.vtex.com/en/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) page views in this session. |
+| **views_department** | integer | Count of [department](https://help.vtex.com/en/tutorial/o-que-e-um-departamento--22rKjmYWVmmKAK8CWa8yKw) page views in this session. |
+| **views_search** | integer | Count of search page views in this session. |
+| **views_product** | integer | Count of product page views in this session. |
+| **views_checkout** | integer | Count of checkout page views in this session. |
+| **views_other** | integer | Count of views for pages [other](https://help.vtex.com/en/tutorial/o-que-e-um-produto--2zrB2gFCHyQokCKKE8kuAw) than product, search, [category](https://help.vtex.com/en/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg), [department](https://help.vtex.com/en/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg), or checkout in this session. |
+| **views_checkout_cart** | integer | Count of checkout page views at the cart stage. |
+| **views_checkout_payment** | integer | Count of checkout page views at the payment stage. |
+| **views_checkout_shipping** | integer | Count of checkout page views at the shipping stage. |
+| **views_checkout_profile** | integer | Count of checkout page views at the profile stage. |
+| **views_checkout_orderplaced** | integer | Count of checkout page views at the completed order stage. |
+| **views_checkout_email** | integer | Count of checkout page views at the email stage. |
+| **workspace** | character varying(16383) | VTEX workspace. |
+| **user_agent** | character varying(16383) | User-agent string extracted from the request server. |
+| **is_first_visit** | boolean | Specifies whether this is the user's first visit. It doesn't count for recurring visitors using different browsers. |
+| **session_start_time** | timestamp without time zone | Start date and time of the session. |
+| **entrance_page_url** | character varying(16383) | URL of the first page view in this session. |
+| **entrance_page_type** | character varying(16383) | Page type of the first view in this session. |
+| **entrance_page_checkout_step** | character varying(16383) | Checkout stage of the first page view in this session. |
+| **session_end_time** | timestamp without time zone | End date and time of the session. |
+| **exit_page_url** | character varying(16383) | URL of the last page view in this session. |
+| **exit_page_type** | character varying(16383) | Page type of the last view in this session. |
+| **exit_page_checkout_step** | character varying(16383) | Checkout stage of the last page view in this session.  |
+
+## Table: pageviews
+
+Each item in this table corresponds to a page viewed by the buyer, such as homepage, product page, and checkout stage.  
+A page view is counted after the buyer's browser loads the page. Each page has specific attributes, however, because this table brings everything together in a single schema, many null values will appear. For example, product page attributes are expected to be null when the page view corresponds to a shopping cart stage. The table fields are described below:  
+
+| **Column name** | **Field type** | **Description** |
+|:---:|:---:|:---:|
+| **client_date** | timestamp without time zone | Date and time of the page view. |
+| **session_id** | character varying(127) | Unique identifier of a session, which maps directly to the VtexRCSessionIdv7 cookie. |
+| **page_type** | character varying(127) | Type of page accessed, with predefined values such as 'home', 'category', 'product', among others. |
+| **checkout_step** | character varying(127) | Checkout stage of the page, valid when page_type is 'checkout'. |
+| **economic_group_id** | character varying(127) | Identifier of the economic group used for billing. |
+| **economic_group_name** | character varying(1024) | Name of the economic group used for billing. |
+| **company_id** | character varying(127) | Company identifier for billing. |
+| **company_name** | character varying(1024) | Name of the company for billing. |
+| **main_account_name** | character varying(127) | Main License Manager account the store is associated to. |
+| **account_name** | character varying(127) | License Manager account the store is associated to. |
+| **store_name** | character varying(127) | Name of the store that generated the page view event. |
+| **url** | character varying(16383) | Full URL of the page view. |
+| **store_host** | character varying(127) | Hostname extracted from the URL. |
+| **page_url** | character varying(16383) | Clean URL of the page view, without query parameters. |
+| **ref** | character varying(16383) | URL of the page that referred the buyer to this page. |
+| **workspace** | character varying(127) | VTEX workspace, usually 'master'. |
+| **workspace_ab_test_id** | character varying(127) | AB test ID extracted from the workspace name. |
+| **user_agent** | character varying(16383) | User-agent string extracted from the server side. |
+| **os_family** | character varying(1023) | OS family extracted from user_agent. |
+| **os_major** | character varying(1023) | Major OS version extracted from user_agent. |
+| **os_minor** | character varying(1023) | Minor OS version extracted from user_agent. |
+| **os_patch** | character varying(1023) | OS patch extracted from user_agent. |
+| **os_patch_minor** | character varying(1023) | Minor OS patch extracted from user_agent. |
+| **device_brand** | character varying(1023) | Device brand extracted from user_agent. |
+| **device_family** | character varying(1023) | Device family extracted from user_agent. |
+| **device_model** | character varying(1023) | Device model extracted from user_agent. |
+| **browser_family** | character varying(1023) | Browser family extracted from user_agent. |
+| **browser_major** | character varying(1023) | Major browser version extracted from user_agent. |
+| **browser_minor** | character varying(1023) | Minor browser version extracted from user_agent. |
+| **browser_patch** | character varying(1023) | Browser patch extracted from user_agent. |
+| **user_id** | character varying(127) | Unique buyer identifier. |
+| **is_first_visit** | boolean | Specifies whether this is the user's first visit. |
+| **category_id** | character varying(127) | Category identifier. |
+| **category_name** | character varying(16383) | Category name. |
+| **department_id** | character varying(127) | Department identifier. |
+| **department_name** | character varying(16383) | Department name. |
+| **product_id** | character varying(127) | Product identifier. |
+| **product_reference_id** | character varying(1024) | Product reference. |
+| **product_name** | character varying(16383) | Product name. |
+| **product_brand_id** | integer | Product brand identifier. |
+| **product_brand_name** | character varying(1024) | Product brand name. |
+| **product_department_id** | integer | Product department identifier. |
+| **product_department_name** | character varying(1024) | Name of the product department. |
+| **product_category_id** | integer | Product category identifier. |
+| **product_category_name** | character varying(1024) | Name of the product category. |
+| **product_list_price** | numeric(22,4) | List price of the product. |
+| **product_price** | numeric(22,4) | Product price. |
+| **seller_id** | character varying(127) | Seller identifier. |
+| **seller_ids** | character varying(16383) | Seller identifiers. |
+| **site_search_term** | character varying(16383) | Search term on the website. |
+| **site_search_form** | character varying(16383) | Search form on the website. |
+| **site_search_category** | character varying(127) | Search category on the website. |
+| **site_search_results** | integer | Website search results. |
+| **sales_channel** | character varying(10) | Sales channel. |
+| **order_form_id** | character varying(127) | Identifier of the order form. |
+| **order_form_shipping** | numeric(22,4) | Shipping cost on the order form. |
+| **order_form_total** | numeric(22,4) | Total on the order form. |
+| **order_form_tax** | numeric(22,4) | Tax on the order form. |
+| **campaign_name** | character varying(16383) | Campaign name. |
+| **campaign_source** | character varying(16383) | Campaign source. |
+| **campaign_medium** | character varying(16383) | Campaign medium. |
+| **internal_campaign_name** | character varying(16383) | Name of the internal campaign. |
+| **internal_campaign_part** | character varying(16383) | Part of the internal campaign. |
+| **order_form_payment_type** | character varying(127) | Type of payment on the order form. |
+| **order_group** | character varying(127) | Order group. |
+| **transaction_id** | character varying(127) | Transaction identifier. |
+| **visitor_login_state** | character varying(16383) | Visitor login status. |
+| **visitor_type** | character varying(16383) | Visitor type. |
+| **visitor_optin_news_letter** | boolean | Specifies whether the visitor opted in to the newsletter. |
+| **profile_id** | character varying(127) | Profile ID of the buyer received from the VTEX Profile system. |
+| **batch_id** | character varying(13) | Control ID of data ingestion. |
+| **id** | character varying(36) | UUID generated during data ingestion. |
+| **transaction_products** | super | Products in the transaction. |
+| **transaction_total** | numeric(22,4) | Transaction total. |
+
+## Analyses with navigation data
+
+Navigation data can be used for the following analyses:  
+
+- **Overall conversion rate:** Calculate the proportion of sessions that resulted in a purchase in relation to the total number of sessions to assess the overall effectiveness of the website in converting visitors into buyers.
+- **Conversion funnel analysis:** Group pageviews by funnel stages (home, search, product, cart, checkout) and count how many sessions have passed through each stage, identifying where users give up.
+- **Most visited pages:** Count the number of pageviews for each type of page (home, category, product) to identify the pages that attract the most attention and optimize them for conversion.
+- **User path tracking:** Follow the sequence of the pageviews for each session to understand the path taken by the user and discover common navigation patterns.
+- **Traffic source:** Analyze the reference URL of each session to determine the traffic source and get insight about which marketing channels are most effective.
+- **Bounce rate by page type:** Identify sessions that end after a single page view and calculate the bounce rate by page type to improve the content or design of these pages.
+
+## Correlations with other data
+
+VTEX navigation data has significant interactions with other datasets that enrich user behavior analysis, for example:  
+
+- **Interaction with order data:** Comparative analysis between navigation and order conversions reveals the impact of user journeys on purchase decisions.
+- **Relationship with SKUs:** User interaction with product and category pages offers insights into the popularity and effectiveness of product presentation.
+- **Marketing data and campaigns:** The correlation between navigation and marketing campaigns helps evaluate how efficient campaigns are in attracting traffic and generating conversions.
+
+### Discover other Datasets
+
+- [Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)   
+- [Payments](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Orders](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Prices](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promotions](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/en/new-integration-with-erede-erederest.md b/docs/tutorials/en/new-integration-with-erede-erederest.md
index 127960f2a..2e4bc45be 100644
--- a/docs/tutorials/en/new-integration-with-erede-erederest.md
+++ b/docs/tutorials/en/new-integration-with-erede-erederest.md
@@ -25,11 +25,11 @@ To set up the new version, you must first request Rede to activate the __ERede__
 
 Once notified, go to the menu and then navigate through __e.Rede > Settings > Token generation__.
 
-![GerarToken](https://images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
+![GerarToken](//images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
 
 Then, click the button to create the token.
 
-![GerarToken Click](https://images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
+![GerarToken Click](//images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
 
 With this, you will have access to the token that must be informed in the ERedeRest gateway affiliation configuration form. In addition to the token, you will also need to inform the PV, which is  the identification number of the establishment on Rede's website.
 
@@ -39,10 +39,10 @@ To do this configuration in VTEX, follow the steps below:
 2. Click on __Settings__ and access __Gateways Affiliations__; 
 3. Click on the green button __+__ _I want to receive payment by the connector..._ and search for the connector __ERedeRest .__
 
-![erederestEN](https://images.ctfassets.net/alneenqid6w5/6LI5jh2u5OcYaGQ4cikuE2/29031380ce30470072c9b06db0d14118/erederestEN.jpg) 
+![erederestEN](//images.ctfassets.net/alneenqid6w5/6LI5jh2u5OcYaGQ4cikuE2/29031380ce30470072c9b06db0d14118/erederestEN.jpg) 
 
-![erederestEN-config](https://images.ctfassets.net/alneenqid6w5/2I770mrYbeueky266cqooO/cf6ffb075ece540e7b3224c99e9c415c/erederestEN-config.jpg)
+![erederestEN-config](//images.ctfassets.net/alneenqid6w5/2I770mrYbeueky266cqooO/cf6ffb075ece540e7b3224c99e9c415c/erederestEN-config.jpg)
 
-![PegarPV](https://images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
+![PegarPV](//images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
 
 This new connector offers a number of configuration options, including ApplePay support. 
diff --git a/docs/tutorials/en/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md b/docs/tutorials/en/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
index 9f79f32a0..16fa41d64 100644
--- a/docs/tutorials/en/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
+++ b/docs/tutorials/en/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
@@ -1,10 +1,10 @@
 ---
 title: 'Newsletter records with <vtex.cmc:newsletterOptIn/> control'
 id: xqKrRRHBscEI8O6UKi8eE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-07T18:35:59.237Z
-updatedAt: 2023-03-31T11:24:39.916Z
-publishedAt: 2023-03-31T11:24:39.916Z
+updatedAt: 2023-12-08T18:44:28.114Z
+publishedAt: 
 firstPublishedAt: 2019-01-25T17:16:54.823Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/en/offer-details.md b/docs/tutorials/en/offer-details.md
index e9e0879fb..6596a3a67 100644
--- a/docs/tutorials/en/offer-details.md
+++ b/docs/tutorials/en/offer-details.md
@@ -1,10 +1,10 @@
 ---
 title: 'Offer Management: offer details'
 id: 4FF9QYAewqAn610mDHwb0P
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T01:07:12.412Z
-updatedAt: 2023-03-31T04:51:33.756Z
-publishedAt: 2023-03-31T04:51:33.756Z
+updatedAt: 2024-06-20T21:34:45.076Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:13:19.773Z
 contentType: tutorial
 productTeam: Channels
@@ -15,6 +15,12 @@ legacySlug: offer-details
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
+<div class="alert alert-info">
+To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
+For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
+</div>  
+
 An offer is an SKU from a seller that has been sent to different sales channels and whose price and inventory have been configured. The [Offer Management](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) module allows sellers to supervise the sending of their offers to marketplaces and see their sync status.
 
 In this module, the **Offer details** page is where you can view all the information about a specific offer, such as its interactions, [interaction details](https://help.vtex.com/en/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf), and errors detected. Interaction details will be available for ten days after registration.
@@ -35,7 +41,7 @@ In <b>Offer Management</b> , you can track offers using <a href="https://help.vt
 
 ## Header
 
-![Offer details EN cabecalho](https://images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/95810a56417e12b9296cd728ac3cb326/Offer_details_EN_cabecalho.jpg)
+![Offer details EN cabecalho](//images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/95810a56417e12b9296cd728ac3cb326/Offer_details_EN_cabecalho.jpg)
 
 The header displays the main information about the offer for quick viewing, such as its image, channel, name, status, ID on VTEX, and ID on the channel. You can also make the following changes by clicking on the `Edit` button:
 
@@ -51,13 +57,13 @@ The Status block shows details about the offer status, which can be Synched, Err
 
 ### Status: Synched
 
-![Offer details PT status sucesso](https://images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/c2968ed1f70e475991cf6ab432099d7d/Offer_details_EN_status_sucesso.jpg)
+![Offer details PT status sucesso](//images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/c2968ed1f70e475991cf6ab432099d7d/Offer_details_EN_status_sucesso.jpg)
 
 The *Synched* status indicates that the offer has been successfully received on a channel and is being updated by both the marketplace and the seller in real time.   
 
 ### Status: Error
 
-![Offer details PT status erro](https://images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/482919e396734cfdc6e1ccc0ba1a555b/Offer_details_EN_status_erro.jpg)
+![Offer details PT status erro](//images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/482919e396734cfdc6e1ccc0ba1a555b/Offer_details_EN_status_erro.jpg)
 
 The *Error* status indicates that the system identified an issue that prevents an offer from being sent or updated on a channel, and the seller needs to take action to fix it. Errors can be generated on the VTEX seller side, such as product descriptions that exceed the character limit, and on the marketplace side, such as failed API calls.   
 
@@ -75,19 +81,19 @@ If there are still errors to be fixed, or if all errors have been fixed but the
 
 ### Status: Unavailable
 
-![Offer details PT status indisponivel](https://images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/5631d49b42f0b71ae84b5f6892657c7b/Offer_details_EN_status_indisponivel.jpg)
+![Offer details PT status indisponivel](//images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/5631d49b42f0b71ae84b5f6892657c7b/Offer_details_EN_status_indisponivel.jpg)
 
 The *Unavailable* status indicates that the offer has been discarded for being inactive or not included in the [sales channel](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) (or trade policy) determined for the channel.
 
 ### Status: Sending
 
-![Offer details PT status enviando](https://images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1f50f1f4b63b5a94ab6747fd70ab8df5/Offer_details_EN_status_enviando.jpg)
+![Offer details PT status enviando](//images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1f50f1f4b63b5a94ab6747fd70ab8df5/Offer_details_EN_status_enviando.jpg)
 
 The *Sending* status indicates that the offer is being submitted to the channel. This status refers to offers that: are being submitted to the marketplace for the first time; are migrating to a new channel; or have been resent after being discarded in another channel.   
 
 ## List of interactions
 
-![Offer details PT lista interacoes](https://images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/6a9970fc7c50d001f4bc1df358247641/Offer_details_EN_lista_interacoes.jpg)
+![Offer details PT lista interacoes](//images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/6a9970fc7c50d001f4bc1df358247641/Offer_details_EN_lista_interacoes.jpg)
 
 The *Interactions* tab lists all `inventory`, `price` or `catalog` updates that that SKU has undergone. You can filter them by origin or status and adjust the number of items displayed per page. Each row corresponds to an interaction regarding that offer and includes the following data:
 
diff --git a/docs/tutorials/en/offer-management-moderation-and-quality-of-mercado-libre.md b/docs/tutorials/en/offer-management-moderation-and-quality-of-mercado-libre.md
index 9843cc253..28fddc134 100644
--- a/docs/tutorials/en/offer-management-moderation-and-quality-of-mercado-libre.md
+++ b/docs/tutorials/en/offer-management-moderation-and-quality-of-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Offer Management: moderation and quality of Mercado Libre'
 id: xSbPzA41jiWPAorlBCEA4
 status: PUBLISHED
 createdAt: 2022-10-24T16:38:07.914Z
-updatedAt: 2022-10-24T17:03:57.020Z
-publishedAt: 2022-10-24T17:03:57.020Z
+updatedAt: 2024-06-20T21:41:34.703Z
+publishedAt: 2024-06-20T21:41:34.703Z
 firstPublishedAt: 2022-10-24T17:03:57.020Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/offer-management.md b/docs/tutorials/en/offer-management.md
index c62e3cdcd..1d6cde9f3 100644
--- a/docs/tutorials/en/offer-management.md
+++ b/docs/tutorials/en/offer-management.md
@@ -1,10 +1,10 @@
 ---
 title: 'Offer Management module'
 id: 7MRb9S78aBdZjFGpbuffpE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T00:44:49.452Z
-updatedAt: 2023-03-31T04:39:55.235Z
-publishedAt: 2023-03-31T04:39:55.235Z
+updatedAt: 2024-06-20T21:34:27.585Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:05:49.343Z
 contentType: tutorial
 productTeam: Channels
@@ -15,19 +15,25 @@ legacySlug: offers-listing
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
+<div class="alert alert-info">
+To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
+For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
+</div>  
+
 The **Offer Management** module allows sellers to track the sending and syncing of their offers on all sales channels integrated with the store. On the VTEX platform, an offer is a SKU from a seller that has been sent to a sales channel and whose price and inventory information have been configured.
 
-![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 In **Offer Management**, you can track offers sent to the following channels: [Mercado Libre](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic and Premium), [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) and VTEX marketplaces. For connectors to integrate via API, see [Offer Management Integration Guide](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 To access the module, in the VTEX Admin go to **Marketplace > Connections > Offer Management**. The following interface is displayed:
 
-![sent-offers-en_2](https://images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/ab112c902aff07dd90b1271dbac0cfae/sent-offers-en_2.png)
+![sent-offers-en_2](//images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/ab112c902aff07dd90b1271dbac0cfae/sent-offers-en_2.png)
 
 The **Offer Management** interface displays a list of your offers, and you can click on any of the offers to access the [offer details](https://help.vtex.com/en/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) and check the [interaction details](https://help.vtex.com/en/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf). Interactions are the offer logs when sending and syncing them with the sales channel and are available for consultation for ten days.
 
-![diagrama ju meyer sent offers en](https://images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/4537ebb6b68838ee6ee4d1bc03dd87c8/diagrama_ju_meyer_sent_offers_en.png)
+![diagrama ju meyer sent offers en](//images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/4537ebb6b68838ee6ee4d1bc03dd87c8/diagrama_ju_meyer_sent_offers_en.png)
 
 On the **Offer Management** page, you can perform the following actions:
 
diff --git a/docs/tutorials/en/offer-quality-filters.md b/docs/tutorials/en/offer-quality-filters.md
index 4c4bb85ba..8a2f4b38f 100644
--- a/docs/tutorials/en/offer-quality-filters.md
+++ b/docs/tutorials/en/offer-quality-filters.md
@@ -1,10 +1,10 @@
 ---
 title: 'Offer Quality Filters'
 id: 4xm0gi8leCyxHj8YdgHSJH
-status: CHANGED
+status: PUBLISHED
 createdAt: 2023-02-27T12:15:26.682Z
-updatedAt: 2023-05-30T21:12:51.762Z
-publishedAt: 2023-02-28T13:45:44.808Z
+updatedAt: 2024-06-20T21:38:38.621Z
+publishedAt: 2024-06-20T21:38:38.621Z
 firstPublishedAt: 2023-02-27T19:32:00.584Z
 contentType: tutorial
 productTeam: Channels
@@ -12,7 +12,7 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: offer-quality-filters
 locale: en
 legacySlug: offer-quality-filters
-subcategory: 4hU8QWlzhxWg711Kz7Gmib
+subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
 [Marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace) need to review and approve offers submitted by sellers to add products to the catalog. In the VTEX Admin, this [cataloging process](https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus--tutorials_396) is done through the Received SKUs page.
@@ -21,7 +21,7 @@ Quality criteria are important for the marketplace's operation so that the offer
 
 **Offer quality filters** is the page where marketplaces add and manage the requirement groups applied to the received SKU cataloging process. To access it, in your VTEX Admin, go to **Marketplace > Offer Quality** or type __"Offer Quality"__ in the search bar.
 
-![EN offer quality](https://images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/73ac6313be9a602772446d24f0dbd8ba/EN_offer_quality.png)
+![EN offer quality](//images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/73ac6313be9a602772446d24f0dbd8ba/EN_offer_quality.png)
 
 In this article, learn how to:
 
@@ -46,7 +46,7 @@ The feature allows the marketplace operator to perform many actions, each offeri
 | Bring more transparency to the cataloging criteria for submitted offers and how sellers and offers do or do not comply.                                                                     | It allows you to identify which sellers and offer types do not meet the requirements, speeding up corrections.         |
 
 ## Viewing Default requirements
-![EN Default requirements](https://images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/83dd62ff723ec843269ea0919c31633d/EN_Default_requirements.png)
+![EN Default requirements](//images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/83dd62ff723ec843269ea0919c31633d/EN_Default_requirements.png)
 
 The page, by default, has some pre-configured requirements that will apply to all categories, sellers, and brands, called _Default requirements_. Some of these criteria are natively configured in [VTEX Matcher](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), the tool applied to VTEX marketplaces to support the cataloging process of submitted offers.
 
diff --git a/docs/tutorials/en/offer-status.md b/docs/tutorials/en/offer-status.md
new file mode 100644
index 000000000..948f5f20c
--- /dev/null
+++ b/docs/tutorials/en/offer-status.md
@@ -0,0 +1,241 @@
+---
+title: 'Offer Status'
+id: 2OE87wU26F7lApl99OdwvJ
+status: PUBLISHED
+createdAt: 2023-09-29T19:16:05.771Z
+updatedAt: 2024-03-04T20:03:00.144Z
+publishedAt: 2024-03-04T20:03:00.144Z
+firstPublishedAt: 2023-09-29T20:07:16.003Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: offer-status
+locale: en
+legacySlug: offer-status-beta
+subcategory: 2zVauFUkYn8vgS0y0MfWeK
+---
+
+The **Offer Status** module allows sellers to track the sending and syncing of their offers on all sales channels integrated with the store. On VTEX, an offer is an SKU from a seller sent to a sales channel whose price and inventory information have been configured.  
+
+**Offer Status** allows you to track offers sent only to VTEX marketplaces. To access the module, in the VTEX Admin, go to **Marketplace > Connections > Offer Status**, or type **Offer Status** in the search bar.
+
+![Offer Status Screen](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/2de2b349e1c114b7b50db65533eee1df/-EN-_Offer_Status_-_GIF.gif)
+
+The **Offer Status** page comprises three tabs: [**Published**](#published-tab), [**Issues**](#issue-tab), and [**Awaiting Completion**](#awaiting-completion-tab), all listing your offers according to their status. You can access and view details of each offer, such as their status, inventory, price, update date, and reasons for being rejected by the marketplace.
+
+![Offer Status schema](//images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/4d8fe1a14fdcfc61f9ec87be31fa2c0a/offer-status-schema-en.png)
+
+## Published tab
+
+In the **Published** tab, you can track the offers sent and approved by the marketplace. In this tab, you can:  
+
+- [Search for and filter offers](#searching-for-and-filtering-offers) 
+- [View offer details](#viewing-offer-details)  
+- [Edit offer details](#editing-offer-details)
+- [Export published offer list](#export-published-offer-list)  
+
+### Searching for and filtering offers
+
+At the top right of the page, there is a search bar with a <i class="fas fa-search"></i> magnifying glass. You can use this bar to search by **offer name.**
+
+Additionally, you can filter the search results using the following criteria:
+
+- **Marketplace:** Sales channel to which the offer was sent.
+- **Inventory:** Number of products available in stock, which can be:
+  - `Minimum:` Minimum number of items in stock for a product.
+  - `Maximum:` Maximum number of items in stock for a product.
+- **Update:** Price and inventory update status of published offers.
+
+To filter the offers by **Marketplace**, click the down arrow, select the desired marketplaces, and then click **Apply**.
+
+To filter the offers by **Inventory**, click the down arrow, enter the minimum and/or maximum inventory, and click **Apply**.
+
+![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/48708c0e98b5c01060748b5def3c6184/inventory-filter.png)
+
+To filter the offers by **Update**, click the down arrow, select one of the options, and then click **Apply.**
+
+See below the options available for this filter:
+
+- **Updated**: Offers that had their price and/or inventory updated by the seller and have been processed successfully.
+- **Error updating:** Offers that had inconsistencies and failed to update.
+
+![Filtro atualizado offer status](//images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/92bc3b3358618470087e57c1566215ae/update-filter.png)
+
+You can use a single filter or combine them in a single search. The filters are not selected by default, so the home page displays the total number of existing offers.
+
+### Viewing offer details
+
+At the top of the **Offer Status** page, there is an overview of the seller's offers with the following information:
+
+- Number of offers published versus offers sent.
+- Number of offers with **Updated** status.
+- Number of offers with **Error updating** status.
+
+The offer list contains columns with the following information:
+
+| **Column** | **Description** |
+|---|---|
+| **Name** | Displays the SKU image, the offer name on the sales channel, and the SKU ID on VTEX. |
+| **Marketplace** | Sales channel to where the offer was sent. |
+| **Price** | SKU offer price. |
+| **Inventory** | Number of items in <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">stock</a> for the offer SKU. |
+| **Update** | Update processing status, which can be Updated <i class="far fa-check-circle"></i> or Error updating<div class="error-icon"></div>. |
+
+You can click the column names to sort the offers in ascending or descending order. For example, by clicking the **Price** column, you can sort offers by price, from the lowest to highest or vice versa.
+
+### Editing offer details
+
+When you click an offer, a window will open with the following offer details:
+
+- **Price:** The offer's current price, when it was last updated, and whether the update was successful or not.
+- **Inventory:** The current availability of the offered item, when it was last updated, and whether the update was successful or not.
+- **Content:** When the content was last updated and whether the update was successful or not.
+
+To update any details of an already published offer, you must do the following:
+
+1. In the **Published tab,** click the desired offer.
+2. Click the <i class="fas fa-ellipsis-v"></i> action icon in the top right corner.
+3. Click one of the options:  
+- **Edit Price**
+- **Edit Inventory**
+- **Edit Content**
+
+You will be redirected to the corresponding page to make the necessary changes.
+
+![Ações offer status](//images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/990566155ec8712979614688eb549ad0/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.006.jpeg)
+
+### Export published offer list
+
+To export the published offer list in XLSX format, click the down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
+
+<div class="alert alert-info">
+  The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
+  </div>
+
+## Issues tab
+
+In the **Issues** tab, you can track the offers that have been sent but were rejected by the marketplace. In this tab, you can also do the following:
+
+- [Search for and filter offers with issues](#searching-for-and-filtering-offers-with-issues)
+- [View issue details](#viewing-issue-details)
+- [Edit offer details](#editing-offer-details)
+- [Export issues offer list](#export-issues-offer-list)
+
+### Searching for and filtering offers with issues
+
+At the top right of the page, there is a search bar with the <i class="fas fa-search"></i> magnifying glass icon, where you can search an offer by:
+
+- Offer name
+- SKU ID
+
+Additionally, you can filter the search results using the following criteria:
+
+- **Marketplace:** Sales channel to which the offer was sent.
+- **Sent:** When the offer was sent to the marketplace. You can choose from the predefined ranges: **Today,** **Last 7 days,** or **Last month.**
+- **Inventory:** Number of products available in stock, which can be:
+- Minimum: Minimum number of items in stock for a product.
+- Maximum: Maximum number of items in stock for a product.
+
+To filter the offers by **Marketplace**, click the down arrow, select the desired marketplaces, and then click **Apply**.  
+
+To filter the offers by **Sent**, click the down arrow, select one of the options, and then click **Apply.**  
+
+To filter the offers by **Inventory**, click the down arrow, enter the minimum and/or maximum inventory, and click **Apply**.  
+![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/48708c0e98b5c01060748b5def3c6184/inventory-filter.png)
+
+You can use a single filter or combine them in a single search. The filters are not selected by default, so the home page displays the total number of existing offers.  
+
+### Viewing issue details
+
+The offer list contains columns with the following information:
+
+| **Column** | **Description** |
+|---|---|
+| **Name** | Displays the SKU image, the offer name on the sales channel, and the SKU ID on VTEX. |
+| **Marketplace** | Sales channel to where the offer was sent. |
+| **Price** | SKU offer price. |
+| **Inventory** | Number of items in stock for the offer SKU. |
+| **Issues** | Number of issues found in the offer. |
+| **Sent** | When the offer was sent to the marketplace. |
+
+### Editing offer details
+
+When you click an offer, a window will open with the following offer details:
+
+- **Possible errors**  
+  - **Offer denied in marketplace:** Occurs when the marketplace has rejected the offer because it does not meet their specified requirements.  
+  - **Inventory update:** Occurs when the offer SKU has no inventory configured.  
+  - **Price update:** Occurs when the offer price was not configured.  
+To update any details of an offer with issues, please follow the steps below:  
+
+1. In the **Issues** tab, click the desired offer.  
+2. Click the <i class="fas fa-ellipsis-v"></i>action icon in the top right corner.  
+3. Click one of the options:  
+  - **Edit Price**
+  - **Edit Inventory**
+  - **Edit Content**
+
+You will be redirected to the corresponding page to make the necessary changes.
+
+### Export issues offer list
+
+To export the issues offer list in XLSX format, click the down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
+
+<div class="alert alert-info">
+  The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
+  </div>
+
+## Awaiting Completion tab
+
+In the **Awaiting Completion** tab, you can track the offers that are awaiting review from the marketplace. In this tab, you can also do the following:  
+
+- [Search for and filter offers under review](#searching-for-and-filtering-offers-under-review)
+- [Edit offer details](#editing-offer-details)
+- [Export awaiting completion offer list](#export-awating-completion-offer-list)
+
+### Searching for and filtering offers under review
+
+At the top right of the page, there is a search bar with a <i class="fas fa-search"></i> magnifying glass. You can use this bar to search by:
+
+- Offer name
+- SKU ID
+
+Additionally, you can filter the search results using the following criteria:
+
+- **Marketplace:** Sales channel to which the offer was sent.
+- **Sent:** When the offer was sent to the marketplace. You can choose from the predefined ranges: **Today, Last 7 days**, or **Last month**.  
+
+To filter the offers by **Marketplace**, click the down arrow, select the desired marketplaces, and then click **Apply**.  
+
+To filter the offers by **Sent**, click the down arrow, select one of the options, and then click **Apply.**  
+
+You can use a single filter or combine them in a single search. The filters are not selected by default, so the home page displays the total number of existing offers.  
+
+### Editing offer details
+
+The **Awaiting Completion** tab contains columns with the following information:
+
+| **Column** | **Description** |
+|---|---|
+| **Name** | Displays the SKU image, the offer name on the sales channel, and the SKU ID on VTEX. |
+| **Marketplace** | Sales channel to where the offer was sent. |
+| **Sent** | When the offer was sent to the marketplace. |
+
+You can click the column names to sort the offers in ascending or descending order. To update any details of an offer under review, please do the following:
+
+1. In the **Awaiting Completion** tab, click the desired offer.
+2. Click the <i class="fas fa-ellipsis-v"></i>action icon in the top right corner.
+2. Click one of the options:
+  - **Edit Price**
+  - **Edit Inventory**
+  - **Edit Content**
+
+You will be redirected to the corresponding page to make the necessary changes.
+
+### Export awaiting completion offer list
+
+To export the awaiting offer list in XLSX format, click the down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
+
+<div class="alert alert-info">
+  The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
+  </div>
diff --git a/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md b/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
index 4d8fe77b0..7a0856475 100644
--- a/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
+++ b/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
@@ -23,7 +23,7 @@ By default, the product that will be shipped from the seller must also be in [st
 
 The following image is an example in which Seller A sends a product to Marketplace A. Only after Marketplace A has added to its inventory the product sent by Seller A can the item be sent to Marketplace B.
 
-![erro-envio-skus-sellers-marketplaces-docnovo](https://images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
+![erro-envio-skus-sellers-marketplaces-docnovo](//images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
 
 Marketplaces based on this business model have more advantages, as they are able to expand their product assortment in third-party sales channels, generating more sales opportunities.
 
diff --git a/docs/tutorials/en/oms-page-structure.md b/docs/tutorials/en/oms-page-structure.md
index 0ca4bf129..fa2016137 100644
--- a/docs/tutorials/en/oms-page-structure.md
+++ b/docs/tutorials/en/oms-page-structure.md
@@ -37,7 +37,7 @@ For all the data of order variations, and also for the numbers of evolution in t
 Important: If the order comparison is done based on 0 orders in the past, the variation is 0%.
 </div>
 
-![barra-status-oms en](https://images.ctfassets.net/alneenqid6w5/3B36BC5ZO8q66GYEOoeOK4/051f7dea8deea96f4bdc321251cfca31/status_bar_en.png)
+![barra-status-oms en](//images.ctfassets.net/alneenqid6w5/3B36BC5ZO8q66GYEOoeOK4/051f7dea8deea96f4bdc321251cfca31/status_bar_en.png)
 
 ### Filters
 
@@ -45,7 +45,7 @@ Allows you to apply multiple filters to see only the list of orders you want. Th
 
 - [How to filter requests](/en/tutorial/filtering-orders-on-the-oms/)
 
-![botão-filtro-oms en](https://images.ctfassets.net/alneenqid6w5/UOgfCVBLUakMIOyKYMCuI/bfb88ea859e7c45fe3435048286d14de/filter_en.png)
+![botão-filtro-oms en](//images.ctfassets.net/alneenqid6w5/UOgfCVBLUakMIOyKYMCuI/bfb88ea859e7c45fe3435048286d14de/filter_en.png)
 
 ### Search Bar
 
@@ -53,7 +53,7 @@ The search bar is used to search for the terms found in the order, such as order
 
 - [How to search for orders](http://help.vtex.com/en/tutorial/searching-for-orders-on-the-oms)
 
-![barra-search-oms en](https://images.ctfassets.net/alneenqid6w5/2G2huhosg8iuG2a2uwKgme/f4a281931a68cf6866cb71838a336b11/search_bar_en.png)
+![barra-search-oms en](//images.ctfassets.net/alneenqid6w5/2G2huhosg8iuG2a2uwKgme/f4a281931a68cf6866cb71838a336b11/search_bar_en.png)
 
 ### Information Bar
 
@@ -63,7 +63,7 @@ It also brings the store's sales ranking in relation to all other VTEX stores. T
 
 - [Interpreting the data of the order bar on the All Orders screen](http://help.vtex.com/en/tutorial/interpreting-the-data-of-the-oms-order-bar)
 
-![barra-info-oms en](https://images.ctfassets.net/alneenqid6w5/6bcXNGPCDus62Y86ICu6ke/d660ca280398c5cd98415051f40ce1e0/info_bar_en.png)
+![barra-info-oms en](//images.ctfassets.net/alneenqid6w5/6bcXNGPCDus62Y86ICu6ke/d660ca280398c5cd98415051f40ce1e0/info_bar_en.png)
 
 ### Export button
 
@@ -71,7 +71,7 @@ Used to export the orders brought by the search, always considering the filters
 
 - [Exporting orders with Orders Management](http://help.vtex.com/en/tutorial/exporting-orders-with-oms)
 
-![botão-export-oms en](https://images.ctfassets.net/alneenqid6w5/2RGkY0fZjyG8yAWeM0cI2/885b73c5a94c50d94bf9d0ac9139249a/botao_export._en.png)
+![botão-export-oms en](//images.ctfassets.net/alneenqid6w5/2RGkY0fZjyG8yAWeM0cI2/885b73c5a94c50d94bf9d0ac9139249a/botao_export._en.png)
 
 ### List of Orders
 
@@ -79,7 +79,7 @@ It is the main area of Orders Management. It brings the last orders made in the
 
 - [List of orders](/en/tutorial/list-of-orders/)
 
-![all-orders-oms en](https://images.ctfassets.net/alneenqid6w5/GKQ3gsB6aAMAAiyWAWQSQ/d91077f73672ba17a4c026496c275b9b/orders_list_en.png)
+![all-orders-oms en](//images.ctfassets.net/alneenqid6w5/GKQ3gsB6aAMAAiyWAWQSQ/d91077f73672ba17a4c026496c275b9b/orders_list_en.png)
 
 ### VTEX DO
 
@@ -87,7 +87,7 @@ It brings together the store's pending tasks and is generated by the different V
 
 - [How VTEX Do task list works.](http://help.vtex.com/en/tutorial/understanding-the-task-list-vtex-do)
 
-![VTEX-do-oms en](https://images.ctfassets.net/alneenqid6w5/5JdvIU3YiIaKIYsWuIWKYa/524090c1e26b1319138bcc47e900ce77/vtex_do_en.png)
+![VTEX-do-oms en](//images.ctfassets.net/alneenqid6w5/5JdvIU3YiIaKIYsWuIWKYa/524090c1e26b1319138bcc47e900ce77/vtex_do_en.png)
 
 ## Subscriptions
 
@@ -105,5 +105,5 @@ The second tab, **Affiliates**, is intended for affiliate configurations in your
 
 - [Configuring affiliates.](http://help.vtex.com/en/tutorial/configuring-affiliates/) 
 
-![settings-oms en](https://images.ctfassets.net/alneenqid6w5/51iFkeJMnSWk4oswQOICoM/c119aa472d2f0db29b1c2db2a5e29bd2/settings_oms.png)
+![settings-oms en](//images.ctfassets.net/alneenqid6w5/51iFkeJMnSWk4oswQOICoM/c119aa472d2f0db29b1c2db2a5e29bd2/settings_oms.png)
 
diff --git a/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
index aa2b9144a..934f8ddd4 100644
--- a/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
@@ -1,10 +1,10 @@
 ---
 title: 'Opening tickets to VTEX financial support'
 id: 1ad3TguXzCSKq4yuYSK80c
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-04-04T13:58:56.872Z
-updatedAt: 2020-11-27T19:40:27.285Z
-publishedAt: 2020-03-09T18:09:31.386Z
+updatedAt: 2024-07-29T22:02:21.897Z
+publishedAt: 2024-07-29T22:02:21.897Z
 firstPublishedAt: 2018-04-04T19:53:34.588Z
 contentType: tutorial
 productTeam: Billing
@@ -35,16 +35,17 @@ Once you have authenticated using the chosen method, you enter the support panel
 
 To open a ticket, simply click the __Send a request__ red button.
 
-![chamado financeiro1 EN](https://images.ctfassets.net/alneenqid6w5/fJpJBPNaKcMSkuKau28eA/16c703c7fe792f12fd996f557a21651d/chamado_financeiro1_EN.png)
+![chamado financeiro1 EN](//images.ctfassets.net/alneenqid6w5/fJpJBPNaKcMSkuKau28eA/16c703c7fe792f12fd996f557a21651d/chamado_financeiro1_EN.png)
 
 You will be taken to the ticket opening form, where you must fill in:
 - Your name.
 - The VTEX account to which the ticket refers (the form loads a list of the accounts to which you have access. If you do not have access to any VTEX accounts, you can not open tickets).
+- Your business registration number (i.e. EIN in the USA).
 - That your question is Financial.
 - The subject.
 - The question or problem.
 
-![chamado financeiro2 EN](https://images.ctfassets.net/alneenqid6w5/1HAPK6tTKE2isE4KUuYuQ6/857347142afec501604095328eb785de/chamado_financeiro2_EN.png)
+![chamado financeiro2 EN](//images.ctfassets.net/alneenqid6w5/1HAPK6tTKE2isE4KUuYuQ6/857347142afec501604095328eb785de/chamado_financeiro2_EN.png)
 
 You can also include attachments, such as screenshots or animated gifs, that help you describe the context of your request.
 
@@ -84,7 +85,7 @@ By clicking __My Requests__, you'll see the history of tickets opened by your ow
 
 If you click __All Requests__, you can see the history of tickets opened by any employees in your store.
 
-![chamado financeiro3 EN](https://images.ctfassets.net/alneenqid6w5/2KBx2P4jCUkOyWkcSkMAKe/fb734b3e0dd80c2362d769f3336eec7f/chamado_financeiro3_EN.png)
+![chamado financeiro3 EN](//images.ctfassets.net/alneenqid6w5/2KBx2P4jCUkOyWkcSkMAKe/fb734b3e0dd80c2362d769f3336eec7f/chamado_financeiro3_EN.png)
 
 ## The ticket statuses
 
@@ -99,4 +100,4 @@ After that, it goes through the statuses `Pending`, `Solved` and `Closed`.
 
 In your support panel, you can filter the tickets search by status. To do this, simply use the checkbox below the request button.
 
-![chamado financeiro4 EN](https://images.ctfassets.net/alneenqid6w5/3Wy8oPFBYQO6KEQ0uQiy0y/a28356d8e2742fa8065b1bf097ea76c1/chamado_financeiro4_EN.png)
+![chamado financeiro4 EN](//images.ctfassets.net/alneenqid6w5/3Wy8oPFBYQO6KEQ0uQiy0y/a28356d8e2742fa8065b1bf097ea76c1/chamado_financeiro4_EN.png)
diff --git a/docs/tutorials/en/opening-tickets-to-vtex-support.md b/docs/tutorials/en/opening-tickets-to-vtex-support.md
index 0068c398b..e7347d696 100644
--- a/docs/tutorials/en/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/en/opening-tickets-to-vtex-support.md
@@ -1,10 +1,10 @@
 ---
 title: 'Opening tickets to VTEX support'
 id: 16yOEqpO32UQYygSmMSSAM
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-11-21T22:18:13.507Z
-updatedAt: 2022-12-16T19:09:29.363Z
-publishedAt: 2022-05-31T21:10:30.601Z
+updatedAt: 2023-12-01T18:51:22.803Z
+publishedAt: 2023-12-01T18:51:22.803Z
 firstPublishedAt: 2017-11-22T02:37:19.330Z
 contentType: tutorial
 productTeam: Others
@@ -65,7 +65,7 @@ If you choose this option, you are required to fill in the information described
    * *I have a concern and would like to ask a question*
    * *I would like to request a setup*
 2. In the **Request subject** field, fill in the information about the type of problem you need help with. Based on your problem description, we will indicate some articles from the [Help Center](https://help.vtex.com/en/) that might help you solve your problem. If none of these articles can help you solve your problem, please move on to the next step.
-![https help.vtex.com en support](https://images.ctfassets.net/alneenqid6w5/2HMCgvH7smDk0aRpZqbNx7/0daa37d669331fdeeea4c91ff8e41684/https___help.vtex.com_en_support.gif)
+![https help.vtex.com en support](//images.ctfassets.net/alneenqid6w5/2HMCgvH7smDk0aRpZqbNx7/0daa37d669331fdeeea4c91ff8e41684/https___help.vtex.com_en_support.gif)
 3. Click `Continue`.
 You will be redirected to another page.
 4. In the Problem impact field, select the option that best describes the scenario:
diff --git a/docs/tutorials/en/operational-capacity-beta.md b/docs/tutorials/en/operational-capacity-beta.md
new file mode 100644
index 000000000..7fe75d9f1
--- /dev/null
+++ b/docs/tutorials/en/operational-capacity-beta.md
@@ -0,0 +1,198 @@
+---
+title: 'Operational Capacity (Beta)'
+id: 2thSYLMAS8KAd8V4XuBLSy
+status: PUBLISHED
+createdAt: 2023-05-08T18:03:07.644Z
+updatedAt: 2024-04-08T18:59:56.706Z
+publishedAt: 2024-04-08T18:59:56.706Z
+firstPublishedAt: 2023-05-09T17:22:57.861Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: operational-capacity-beta
+locale: en
+legacySlug: locations-module
+subcategory: 13sVE3TApOK1C8jMVLTJRh
+---
+
+<div class = "alert alert-info">
+This feature is in beta, which means that we are working to improve it. To use <b>Operational Capability (Beta)</b>, fill out the <a href="https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform">contact form</a>. To use the feature, it is required to have <a href="https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl">franchise accounts</a> associated with the <a href="https://help.vtex.com/en/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#vtex-account-types">main account</a>.
+</div>
+
+The **Operational Capacity** page allows you to manage the sellers' capacity to receive and handle the store's orders to optimize your logistics network. You can monitor the order allocation between sellers and perform [actions](#acoes-na-pagina-de-detalhes-do-seller) to improve order allocation between them.
+
+A good seller operational capacity management leads to the following advantages:
+
+- Better reallocates product demand between different sellers' warehouses.
+- Optimizes order shipping times by avoiding overloading sellers.
+- Improves the shopping experience for customers, who receive their orders on time.
+
+When you go to the VTEX Admin under **Shipping > Operational Capacity**, you will find a page like the one below:
+
+![operational_capacity_image1_EN](//images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/87f03e4f1a667a76349095e450244602/operational_capacity_image1_EN.png)
+
+<div class="alert alert-warning">
+The sellers displayed on the interface are your operation's sellers, previously configured by our team. To add a new seller, contact <a href="https://help.vtex.com/en/support">our Support</a> team.
+</div>
+
+The chart shows the following data:
+
+- **Total sellers:** Total number of sellers in your operation.
+- **Active:** Number of sellers receiving new orders.
+- **Paused:** Number of sellers who are paused and not receiving new orders.
+- **Number of sellers that exceeded capacity:** Number of sellers that received more orders than their configured limit. You can view results from the last `7 days` or `28 days`.
+
+The **Operational Capacity** page displays the following information:
+
+| **Column** | **Description** |
+| :----------: | :---------- |
+| Name | Identification of the <a href="https://help.vtex.com/en/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w">seller</a> to which the operational capacity refers. |
+| Capacity Usage | <p>Percentage of operational capacity used on the day.</p><p><b>Example:</b> A seller with the capacity to handle 100 orders has used 80% of its capacity for the day. Therefore, they can only receive 20 more new orders that day.</p><p>In this column, an alert icon is displayed when the seller reaches 100% of their capacity, so they cannot receive any new orders for the day.</p><p>You can <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#editing-the-sellers-operational-capacity">edit the operational capacity of sellers</a> individually or in bulk, as detailed in the Editing operational capacity of sellers section.</p> |
+| Status | <p>Status of the seller's operational capacity, which can be of two types:</p><p><ul><li><i class="fas fa-toggle-on" aria-hidden="true"></i> <b>Active:</b> The toggle switch is activated, and the seller can receive new orders.</li><li><i class="fas fa-toggle-off" aria-hidden="true"></i><b>Paused:</b> The toggle switch is deactivated, and the seller cannot receive new orders.</li></ul></p><p>To choose when to pause a seller, see the section <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#choosing-between-pausing-or-increasing-operational-capacity">Choosing between pausing or increasing operational capacity</a>.</p> |
+
+When you click a seller, you are redirected to the [seller's details page](#actions-on-the-seller-details-page), which will be seen below.
+
+## Operational Capacity actions
+
+In the VTEX Admin, under **Shipping > Operational Capacity**, you can do the following:
+
+- [Search for sellers](#searching-for-sellers)
+- [Filter sellers](#filtering-sellers)
+- [Activate and pause sellers' operational capacity](#activating-and-pausing-the-operational-capacity-of-sellers)
+- [Edit the seller's operational capacity unit](#editing-the-sellers-operational-capacity-unit)
+
+### Searching for sellers
+
+Using the search bar, you can search for sellers by their name.
+
+<div class = "alert alert-info">
+You can associate the search for sellers with the <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtering-sellers">filter by status</a>. If your search did not return any results, make sure no filters are active.
+</div>
+
+### Filtering sellers
+
+You can filter the listed sellers by their status by clicking `Status` and selecting `Active` or `Paused`. Then click `Apply`.
+
+To clear the applied filters, click **Status > Clear**.
+
+### Activating and pausing the operational capacity of sellers
+
+A seller will have the <i class="fas fa-toggle-on" aria-hidden="true"></i> `Active` status if the toggle switch is activated, and the <i class="fas fa-toggle-off" aria-hidden="true"></i> `Paused` status if the toggle switch is deactivated. To change the operational capacity status of a single seller, click the toggle switch in the corresponding row and confirm the change by clicking `Pause`/`Activate`. 
+
+To activate or pause the operational capacity of multiple sellers, follow these steps:
+
+1. In the VTEX Admin, go to **Shipping > Operational Capacity**, or type **Operational Capacity** in the search bar at the top of the page.
+2. Select the sellers you want by clicking the checkboxes next to their names. You can select all the sellers by clicking a checkbox and then clicking `Select all`.
+3. Click `More actions`.
+4. Click `Activate` or `Pause`, as desired.
+5. Confirm by clicking `Activate` or `Pause`, as desired.
+
+### Editing the seller's operational capacity unit
+
+The seller's operational capacity considers the number of orders or order items. To edit the operational capacity of one or more sellers, follow the steps below:
+
+1. In the VTEX Admin, go to **Shipping > Operational Capacity**, or type **Operational Capacity** in the search bar at the top of the page.
+2. Select the sellers you want by clicking the checkboxes next to their names. You can select all the sellers by clicking a checkbox and then clicking `Select all`.
+3. Click `Edit Capacity`.
+4. Choose the **Operational Capacity unit**:
+    - **Number of orders:** The seller's operational capacity will be based on the number of orders.
+    - **Number of items:** The seller's operational capacity will be based on the number of items in an order.
+5. Click `Save Changes`.
+
+<div class="alert alert-warning">
+The platform has some restrictions regarding <a href="https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">comprehensive sellers</a>. Learn more in the <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#comprehensive-seller-operational-capacity">Comprehensive seller operational capacity</a> section.
+</div>
+
+## Actions on the seller details page
+
+In the VTEX Admin, under **Shipping > Operational Capacity**, when you click a seller, you are redirected to their details page, where you can:
+
+- [Pause and activate the seller's operational capacity](#pause-and-activate-the-sellers-operational-capacity)
+- [Monitor capacity usage](#monitoring-capacity-usage)
+- [Edit the address associated with the seller](#editing-the-address-associated-with-the-seller)
+- [Edit the seller's operational capacity](#editing-the-sellers-operational-capacity)
+
+### Pause and activate the seller's operational capacity
+
+At the top right of the seller's details page, you'll find a toggle switch to activate or pause their operational capacity:
+
+- **Activate:** Enable the toggle switch for `Active` and click `Activate`.
+- **Pause:** Toggle the switch for `Paused` and click `Pause`.
+
+<div class="alert alert-warning">
+The platform has some restrictions regarding <a href="https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">comprehensive sellers</a>. Learn more in the <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#comprehensive-seller-operational-capacity">Comprehensive seller operational capacity</a> section.
+</div>
+
+### Monitoring capacity usage
+
+The **Operational Capacity Status** chart shows, in real time, the percentage of the seller's capacity that has already been used, as in the image below:
+
+![operational_capacity_image2_EN](//images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/0bed6fad834c5b5ab6d22ce713abd11d/operational_capacity_image2_EN.png)
+
+The chart shows the following periods:
+
+- Today
+- Tomorrow
+- Date of the next two days
+
+If you set up the _Continue to receive orders by consuming the capacity of the following days_ [rule](https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#iii-rule) for the seller, the chart will display the percentage of operational capacity for the following days already used for orders from previous days. Learn more in [Editing the seller's operational capacity](#editing-the-sellers-operational-capacity).
+
+### Editing the address associated with the seller
+
+To edit the seller's address or identification name in **Operational Capacity**, follow the steps below:
+
+1. In the **Basic Information** section, click `Edit Basic Information`.
+2. Change the desired information.
+3. Click `Save Changes`.
+
+### Editing the seller's operational capacity
+
+In the **Operational Capacity** section, you can see the seller's current operational capacity settings for each day of the week, as in the following image:
+
+![operational_capacity_image3_EN](//images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/7aa99cf4ff1a7deb322671c5e1961537/operational_capacity_image3_EN.png)
+
+To change these settings, follow the steps below:
+
+1. In the **Operational Capacity** section, click `Edit`.
+2. Change the desired options:
+    - [I - Operational Capacity Unit](#i-operational-capacity-unit)
+    - [II - Capacity](#ii-capacity)
+    - [III - Rule](#iii-rule)
+3. Click `Save Changes`.
+
+Below are the field descriptions mentioned in the instructions.
+
+#### I - Operational Capacity Unit
+
+Choose whether operational capacity is defined by the number of _orders_ or _items_. The number of items considers the items of all the orders placed that day.
+
+#### II - Capacity
+
+Set the seller's operational capacity limit for each day of the week. The system does not set a maximum value.
+
+When the configured limit is reached, your store keeps receiving new orders, which can be allocated to other sellers or to the same seller but within the capacity for the following days. This will depend on the rule you choose.
+
+#### III - Rule
+
+Choose the rule for when the seller reaches maximum capacity for the day:
+
+- **Continue to receive orders by consuming the capacity of the following days:** The seller keeps receiving new orders when the capacity is reached, which are allocated to the capacity of the following days. The delivery promise for the next orders is adjusted at checkout. You can't configure this period in hours because it automatically adjusts to correspond to the number of following days allocated.
+  - If you choose this rule, determine the number of following days to allocate orders that exceed the current day's capacity.
+  > **Example:** A seller sells chocolates, and its operational capacity today reached 100%. The seller keeps receiving new orders, but they will be handled the next day, as the team can only handle orders already scheduled for today. At checkout, the delivery promise for new orders now displays a day later, as the orders will be handled tomorrow. If tomorrow's capacity is consumed today, new orders will be allocated for the day after tomorrow and handled in two days. This is because the store has set up a period of three days to receive orders by using the following days' capacity.
+- **Pause this seller until the end of the day:** Once a seller reaches their capacity limit for the day, they stop receiving new orders, which are allocated to other sellers.
+
+## Choosing between pausing or increasing operational capacity
+
+To decide whether the best strategy for your business is to [edit a seller's operational capacity](#-editing-the-sellers-operational-capacity) or [pause](#pause-and-activate-the-sellers-operational-capacity) them, it's important to understand the following:
+
+- **Paused seller:** The seller stops receiving new orders until they are reactivated. Even if the rule _Continue to receive orders by consuming the capacity of the following days_ is configured, new orders are not accepted.
+  > **Example:** The seller's store had problems with their facilities, affecting the handling of new orders. In this case, it is strategic to pause the seller and only reactivate them once they are able to handle orders again.
+- **Seller reached the maximum limit:** When the seller reaches 100% capacity, they stop receiving new orders for that day. However, their operational capacity becomes fully available the next day, and they automatically receive new orders.
+  > **Example:** On Christmas Eve, the seller reached its maximum capacity for the day and could not handle more orders, so it would not be worth [increasing the seller's operational capacity](#editing-the-sellers-operational-capacity). Since new orders can be handled the next day, there's no need to edit the seller, as their capacity will reset and be available to receive new orders again.
+
+### Comprehensive seller operational capacity
+
+When customers don't enter their location on your store, they can see your store's products (seller 1) and those from [comprehensive sellers](https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI).
+
+Due to a platform limitation, when you deactivate the operational capacity of a comprehensive seller, their products are still displayed on the store, but customers can't buy them. 
+We therefore recommend leaving the comprehensive sellers' operational capacity enabled at all times.
diff --git a/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
index 191e26055..17b554621 100644
--- a/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
@@ -53,7 +53,7 @@ To disable the __Optimized Shipping Options__ function, follow the steps below:
 3. In the blue options menu located at the top of the page, click on __Checkout__.
 4. Under __Optimized Shipping Options__, click the <i class="fas fa-toggle-off"></i> to disable the __Optimize Shipping options display option__.
 
-![Optimized shipping options](https://images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/838428bac6e785ad6472fd87c18f1e1c/Optimized_shipping_options_EN.PNG)
+![Optimized shipping options](//images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/838428bac6e785ad6472fd87c18f1e1c/Optimized_shipping_options_EN.PNG)
 
 <ul>
   5. Click <b>Save</b>.
diff --git a/docs/tutorials/en/order-allocation-algorithm-beta.md b/docs/tutorials/en/order-allocation-algorithm-beta.md
index 06f0aa08a..b0319a1ef 100644
--- a/docs/tutorials/en/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/en/order-allocation-algorithm-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Order Allocation Algorithm (Beta)'
 id: 1zLCAyEdnVe3EsE9Kz88xA
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-07-12T23:39:25.008Z
-updatedAt: 2023-03-21T17:27:34.101Z
-publishedAt: 2023-03-21T17:27:34.101Z
+updatedAt: 2023-08-14T17:29:11.705Z
+publishedAt: 
 firstPublishedAt: 2022-07-12T23:51:23.186Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/order-cancellation-requested-by-the-customer.md b/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
index c34abdb94..0958c324f 100644
--- a/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
@@ -3,8 +3,8 @@ title: 'Order cancellation requested by the customer'
 id: 3wEI6DUNtecooG2Ki4Akqo
 status: PUBLISHED
 createdAt: 2019-01-24T21:42:57.276Z
-updatedAt: 2023-04-28T00:40:54.949Z
-publishedAt: 2023-04-28T00:40:54.949Z
+updatedAt: 2024-04-01T15:51:58.098Z
+publishedAt: 2024-04-01T15:51:58.098Z
 firstPublishedAt: 2019-01-24T21:42:57.707Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,6 +21,10 @@ Customers may request to cancel their order for various reasons. They can [cance
 Once an order is canceled, it is no longer possible to change its status.
 </div>
 
+<div class = "alert alert-warning">
+Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
+</div>
+
 ## Cancellation within the grace period
 
 When the customer requests to cancel an order during the [grace period](https://help.vtex.com/en/tutorial/setting-the-grace-period-for-order-cancellation--jYFdnPDtNm4WCEkYWqqC), the order is automatically canceled without needing the store's authorization. Until that moment, following the [order flow](https://help.vtex.com/en/tutorial/order-flow-on-the-oms--tutorials_196), the retailer did not have to take any action regarding that order.
diff --git a/docs/tutorials/en/order-details-page.md b/docs/tutorials/en/order-details-page.md
index f475679dd..6bd12e2f1 100644
--- a/docs/tutorials/en/order-details-page.md
+++ b/docs/tutorials/en/order-details-page.md
@@ -3,8 +3,8 @@ title: 'Order details page'
 id: 2Y75n54Cc9VizrlG1N6ZNl
 status: PUBLISHED
 createdAt: 2020-12-28T15:51:29.428Z
-updatedAt: 2023-03-23T19:27:38.026Z
-publishedAt: 2023-03-23T19:27:38.026Z
+updatedAt: 2023-12-21T14:06:02.509Z
+publishedAt: 2023-12-21T14:06:02.509Z
 firstPublishedAt: 2020-12-28T19:33:51.059Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,20 @@ legacySlug: order-details-page-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
+<div class = "alert alert-info">
+You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
+</div>
+
 The order details page allows you to view all the information of an order and manage it in a single place. To access it, in the VTEX Admin, go to **Orders > [All orders](https://help.vtex.com/en/tutorial/lista-de-pedidos-beta--2QTduKHAJMFIZ3BAsi6Pi)**, and click the desired order.
 
-On this page, you can:
+You can also search for orders from any page in the VTEX Admin using the global search bar at the top bar. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
+
+On the order details page, you can:
 
 * Check in which stage of the order flow the order is (order status).
 * View the entire change history of the order.
@@ -39,7 +50,7 @@ You will find below a list of all possible sections for the <b>Order details pag
 
 ## Top bar
 
-![BarrasuperiorEN](https://images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/ee97e23a21b0ba350ee47cf6ded14cde/BarrasuperiorEN.jpg)
+![BarrasuperiorEN](//images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/ee97e23a21b0ba350ee47cf6ded14cde/BarrasuperiorEN.jpg)
 
 The top bar contains the following information and actions:
 
@@ -53,7 +64,7 @@ The top bar contains the following information and actions:
 
 ## General information 
 
-![Informacao geraisEN](https://images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/5a4a537da2ec23a9153aa7027a4b2c49/Informacao_geraisEN.jpg)
+![Informacao geraisEN](//images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/5a4a537da2ec23a9153aa7027a4b2c49/Informacao_geraisEN.jpg)
 
 General order information is displayed at the top of the page, just below the top bar, and includes:
 
@@ -77,7 +88,7 @@ To learn more about the order flow and when to handle an order, read the article
 
 ### Items to invoice
 
-![Itens faturarEN](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
+![Itens faturarEN](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
 
 The block **Items to Invoice** contains packages with items for which payment has been approved but not yet [invoiced](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), i.e. their invoices have not been uploaded to the platform.
 
@@ -90,7 +101,7 @@ In the top left corner, the following actions are available:
 
 ###  Invoices
 
-![FaturaEN](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
+![FaturaEN](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
 
 This block displays the invoiced items with their respective invoices and the packages that make up the deliveries.
 
@@ -103,7 +114,7 @@ In this block, the retailer can:
 
 ### Returned items
 
-![Itens devolvidosEN](https://images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/d6354bb77f2ab0ffa3f01f81afe5de19/Itens_devolvidosEN.png)
+![Itens devolvidosEN](//images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/d6354bb77f2ab0ffa3f01f81afe5de19/Itens_devolvidosEN.png)
 
 The block **Returned Items** is displayed when order items are returned. See the information and actions available in this block:
 
@@ -117,7 +128,7 @@ The block **Returned Items** is displayed when order items are returned. See the
 
 ### History of changed items
 
-![Historico Itens alteradosEN](https://images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/d96c4ca6d673fd5222086070ea9c64ae/Historico_Itens_alteradosEN.png)
+![Historico Itens alteradosEN](//images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/d96c4ca6d673fd5222086070ea9c64ae/Historico_Itens_alteradosEN.png)
 
 This block is displayed when changes are made to order items. The **History of changed items** displays the details of the changes made, such as which items were added or removed, the date the change occurred, and the prices of the products (the price of the returned item, the price of the added item, and the difference between the two).
 
@@ -125,7 +136,7 @@ If there are changes in the final amount of the order, the difference will be di
 
 ### Order history
 
-![Historico pedidoEN](https://images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/3d9701b380306223f795295b4ecf3cae/Historico_pedidoEN.jpg)
+![Historico pedidoEN](//images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/3d9701b380306223f795295b4ecf3cae/Historico_pedidoEN.jpg)
 
 This block displays all the order activity and  interactions that took place within the order, with date and time information. 
 
@@ -139,7 +150,7 @@ You can also view details of notifications emailed to the customer by clicking o
 
 ### Comments
 
-![ComentariosEN](https://images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/89520a487885e12fbacf0b7b614c1347/ComentariosEN.png)
+![ComentariosEN](//images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/89520a487885e12fbacf0b7b614c1347/ComentariosEN.png)
 
 This section allows you to add internal comments with remarks about the order. To do this, you can type in the text box and click on `Send`.
 
@@ -147,7 +158,7 @@ Comments are recorded on the order details page with the date, time, and email a
 
 ## Financial details
 
-![Lateral](https://images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/c9be1169615d4c8c08d6108fd4171395/LateralEN.png)
+![Lateral](//images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/c9be1169615d4c8c08d6108fd4171395/LateralEN.png)
 
 On the right side of the page, you can view the financial details of the order. This information is updated automatically as the order progresses. 
 
diff --git a/docs/tutorials/en/order-errors-in-the-mercado-livre-integration.md b/docs/tutorials/en/order-errors-in-the-mercado-livre-integration.md
index 200454fee..67b63d5c5 100644
--- a/docs/tutorials/en/order-errors-in-the-mercado-livre-integration.md
+++ b/docs/tutorials/en/order-errors-in-the-mercado-livre-integration.md
@@ -3,8 +3,8 @@ title: 'Order errors in the Mercado Livre integration'
 id: 4w4jAIWUy3OELgu3HFmGgh
 status: PUBLISHED
 createdAt: 2021-08-30T18:04:27.780Z
-updatedAt: 2023-03-29T23:44:08.721Z
-publishedAt: 2023-03-29T23:44:08.721Z
+updatedAt: 2023-08-04T18:43:32.189Z
+publishedAt: 2023-08-04T18:43:32.189Z
 firstPublishedAt: 2021-08-30T18:37:05.901Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/order-flow-and-status.md b/docs/tutorials/en/order-flow-and-status.md
index c8813c8e8..e308e76fe 100644
--- a/docs/tutorials/en/order-flow-and-status.md
+++ b/docs/tutorials/en/order-flow-and-status.md
@@ -3,8 +3,8 @@ title: 'Order flow and status'
 id: tutorials_196
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:33.518Z
-updatedAt: 2023-02-28T16:04:19.511Z
-publishedAt: 2023-02-28T16:04:19.511Z
+updatedAt: 2024-04-01T15:37:30.788Z
+publishedAt: 2024-04-01T15:37:30.788Z
 firstPublishedAt: 2017-04-27T23:02:47.616Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -41,7 +41,7 @@ For incomplete orders, check out the article <a href="https://help.vtex.com/en/t
 
 ### Marketplace flow
 
-![pedido_marketplace_en](https://images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/315b6d8c70b8631d2be02c4dd659af98/pedido_marketplace_en.png)
+![pedido_marketplace_en](//images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/315b6d8c70b8631d2be02c4dd659af98/pedido_marketplace_en.png)
 
 The marketplace flow is integrated with the seller flow. When an order delivered by an external seller (which is not the main seller) is finalized, this is the flow visible to the marketplace:
 
@@ -58,7 +58,7 @@ Learn how to identify orders from marketplaces in the article [Viewing marketpla
 
 ### Seller flow
 
-![pedido_fluxo_seller_en](https://images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/9cc2dbb00ed43160d6e4699594107b22/pedido_fluxo_seller_en.png)
+![pedido_fluxo_seller_en](//images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/9cc2dbb00ed43160d6e4699594107b22/pedido_fluxo_seller_en.png)
 
 This is the order flow visible to the store responsible for shipping the order products. In this case, the order was placed through another store (online marketplace), and the seller flow starts once the order is confirmed.
 
@@ -97,7 +97,7 @@ Please note that:
 
 ### Complete flow
 
-![pedido_fluxo_completo_en_2](https://images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/4dffff0e3ad8bd51e4bdcacb14a10b50/pedido_fluxo_completo_en.png)
+![pedido_fluxo_completo_en_2](//images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/4dffff0e3ad8bd51e4bdcacb14a10b50/pedido_fluxo_completo_en.png)
 
 The complete order flow is visible to the store that sells and delivers the order. It is composed of the marketplace flow followed by the seller flow.
 
@@ -126,6 +126,8 @@ Orders can be canceled for several reasons. Each type of cancellation is indicat
 
 Once there is a request to cancel an order, the platform processes the order cancellation automatically. The payment refund to the customer depends on the stage the payment is at and the payment method used.
 
+Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
+
 <div class = "alert alert-info">
 Learn more about cancellation and refunds in the articles <a href="https://help.vtex.com/en/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente">Why was my cancelled order charged in the customer's invoice?</a>, and <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento">Refund or cancellation</a>.
 </div>
@@ -140,7 +142,7 @@ Learn more about order cancellation in the article [Why was my order cancelled?]
 
 ### Chain flow
 
-![pedido_fluxo_chain_en](https://images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/7617928cd9328c928ecd09d05b08af2e/pedido_fluxo_chain_en.png)
+![pedido_fluxo_chain_en](//images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/7617928cd9328c928ecd09d05b08af2e/pedido_fluxo_chain_en.png)
 
 The order flow seen by the intermediate store in a [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) is similar to the marketplace order flow, except for receiving the payment for orders. In the `Payment pending` stage, instead of the chain receiving payment directly from the gateway, the marketplace informs the chain it has received the payment confirmation. 
 
@@ -274,7 +276,7 @@ Note that the complete order flow (visible to the stores responsible for selling
     <td class="tg-zr06"><span style="font-weight:400">-</span></td>
     <td class="tg-zr06"><span style="font-weight:400">waiting-for-fulfillment</span></td>
     <td class="tg-zr06"><span style="font-weight:400">Seller</span></td>
-    <td class="tg-zr06"><span style="font-weight:400">Waits for order's fulfillment. Status exclusive for stores that have a Warehouse Management System (WMS).</span></td>
+    <td class="tg-zr06"><span style="font-weight:400">Waits for order's fulfillment. Status exclusive for stores that have a Warehouse Management System (WMS). When the marketplace does not authorize the seller to fulfill the order within 30 days, this order is automatically canceled by the platform.</span></td>
   </tr>
   <tr>
     <td class="tg-zr06"><span style="font-weight:400">-</span></td>
@@ -292,7 +294,7 @@ Note that the complete order flow (visible to the stores responsible for selling
     <td class="tg-zr06"><span style="font-weight:400">Authorize fulfillment</span></td>
     <td class="tg-zr06"><span style="font-weight:400">authorize-fulfillment</span></td>
     <td class="tg-zr06"><span style="font-weight:400">Seller and complete flow</span></td>
-    <td class="tg-zr06"><span style="font-weight:400">Internal process for approving the order handling. In this status, the platform confirms the</span> <a href="https://help.vtex.com/en/tutorial/como-a-reserva-funciona--tutorials_92#reserva-confirmada"><span style="font-weight:400;color:#F71963;background-color:transparent">item reservation</span></a><span style="font-weight:400">.</span></td>
+    <td class="tg-zr06"><span style="font-weight:400">Internal process for approving the order handling. In this status, the platform confirms the</span> <a href="https://help.vtex.com/en/tutorial/como-a-reserva-funciona--tutorials_92#reserva-confirmada"><span style="font-weight:400;color:#F71963;background-color:transparent">item reservation</span></a><span style="font-weight:400">. When the marketplace does not authorize the seller to fulfill the order within 30 days, this order is automatically canceled by the platform.</span></td>
   </tr>
   <tr>
     <td class="tg-zr06"><span style="font-weight:400">Cancellation window</span></td>
diff --git a/docs/tutorials/en/order-replacement.md b/docs/tutorials/en/order-replacement.md
index f21372ffa..6f7d4c3e6 100644
--- a/docs/tutorials/en/order-replacement.md
+++ b/docs/tutorials/en/order-replacement.md
@@ -3,8 +3,8 @@ title: 'Order replacement'
 id: 2IK9mwQjBKseQmE8K8saO8
 status: PUBLISHED
 createdAt: 2018-02-20T19:29:21.502Z
-updatedAt: 2023-03-29T15:54:02.723Z
-publishedAt: 2023-03-29T15:54:02.723Z
+updatedAt: 2024-07-08T14:22:27.104Z
+publishedAt: 2024-07-08T14:22:27.104Z
 firstPublishedAt: 2018-02-20T20:24:08.083Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -61,7 +61,7 @@ The information that can be modified using the Order replacement feature are:
 Orders cannot be modified in the cases of:
 
 * [Incomplete orders](https://help.vtex.com/en/tutorial/understanding-incomplete-orders--tutorials_294): when the order does not contain all the information necessary to be completed on the platform.
-* Shared transaction: orders with more than one seller and payment made to the marketplace.
+* Shared transaction: orders with one or more sellers and payment made to the marketplace.
 * Orders already modified by the store.
 * Orders with status:
     * Verifying invoice
diff --git a/docs/tutorials/en/order-report.md b/docs/tutorials/en/order-report.md
index 9f918a4b5..3fb5ee613 100644
--- a/docs/tutorials/en/order-report.md
+++ b/docs/tutorials/en/order-report.md
@@ -3,8 +3,8 @@ title: 'Order report'
 id: 31m1ewsmsEe0WS4So2aGMY
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:42.311Z
-updatedAt: 2023-05-31T15:43:26.524Z
-publishedAt: 2023-05-31T15:43:26.524Z
+updatedAt: 2024-03-01T01:28:57.258Z
+publishedAt: 2024-03-01T01:28:57.258Z
 firstPublishedAt: 2019-01-24T22:03:18.967Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -114,7 +114,7 @@ Each column corresponds to specific information, as described below.
 *    **Taxes:** the sum of the values defined as Tax and CustomTax, the taxes applied to the SKU. If those values do not exist, the column will be empty.
 *    **Invoice Numbers:** the order's invoice number.
 *    **Country:** country in which the order was placed.
-*    **Input Invoices Numbers:** number of an invoice of Input type, which means that it refers to a return.
-*    **Output Invoices Numbers:** number of an invoice of Output type, which means that it refers to a purchase.
+*    **Input Invoices Numbers:** number of an invoice of Output type, which means that it refers to a purchase.
+*    **Output Invoices Numbers:** number of an invoice of Input type, which means that it refers to a return.
 *    **Status raw value (temporary):** the raw status value of an order. For example, the status of an order can be displayed on the interface as `Handling` while in this field it would be `handling`.
 *   **Cancellation Data**: the reason given by the end-customer for canceling the order, as shown in the `Reason` field of the `cancellationData` object in the [Orders API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/cancel). If the user does not fill in this field when canceling the order, this column will be empty in the report.
diff --git a/docs/tutorials/en/order-split-and-delivery-split.md b/docs/tutorials/en/order-split-and-delivery-split.md
index f9236cdae..0e9629c55 100644
--- a/docs/tutorials/en/order-split-and-delivery-split.md
+++ b/docs/tutorials/en/order-split-and-delivery-split.md
@@ -3,8 +3,8 @@ title: 'Order split and delivery split'
 id: jQvzA6QgSd51e2p6bthoV
 status: PUBLISHED
 createdAt: 2021-09-27T21:06:59.520Z
-updatedAt: 2023-01-13T18:53:14.386Z
-publishedAt: 2023-01-13T18:53:14.386Z
+updatedAt: 2023-09-23T01:00:23.558Z
+publishedAt: 2023-09-23T01:00:23.558Z
 firstPublishedAt: 2021-09-27T21:12:55.418Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,7 +15,6 @@ legacySlug: order-split-and-delivery-split
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-
 On the VTEX platform, there are scenarios in which the end customer receives their order in different packages. This article provides an overview of **package splits (or delivery splits)** and **order splits**, and indicates the configurations that can be made by the retailer.
 
 See below for the main differences between order split and package split scenarios.
@@ -57,4 +56,4 @@ The order is fulfilled by a single seller, but more than one delivery is require
   We do not recommend operating the store with the <code>allowMultipleDeliveries</code> field indicated as <i>false</i>. In this configuration, when there are items in the cart that do not have any delivery method in common, that is, the SLAIDs are different, and the cart has a pickup-point, it will not be possible to complete the order.
 </div>
 
-* **Different warehouses:** a single store offers all the items in an order, but they are in different warehouses. Then, _the delivery packages must be split_, but without splitting the order between different stores. The platform does this automatically.
+* **Different loading docks:** a single store offers all the items in an order, but in the calculated logistic route they are related to different docks. Then, _the delivery packages must be split_, but without splitting the order between different stores. The platform does this automatically.
diff --git a/docs/tutorials/en/order-transactional-email-templates.md b/docs/tutorials/en/order-transactional-email-templates.md
index 2b00f7af1..d4963a1f6 100644
--- a/docs/tutorials/en/order-transactional-email-templates.md
+++ b/docs/tutorials/en/order-transactional-email-templates.md
@@ -3,8 +3,8 @@ title: 'Order transactional email templates'
 id: 3g2S2kqBOoSGcCaqMYK2my
 status: PUBLISHED
 createdAt: 2018-11-06T21:01:19.818Z
-updatedAt: 2023-02-28T01:10:27.048Z
-publishedAt: 2023-02-28T01:10:27.048Z
+updatedAt: 2024-03-01T01:15:49.954Z
+publishedAt: 2024-03-01T01:15:49.954Z
 firstPublishedAt: 2018-11-07T18:11:42.445Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -27,19 +27,19 @@ To view the available templates, follow the steps below:
 2. Click __Templates__.
 3. Type the template name or key in the search bar. Check the list below for more information on each template.
 
-| Template   | Key        | Description| Trigger    |
+| Template | Key | Description | Trigger |
 | ---------- | ---------- | ---------- | ---------- |
-| Order confirmation | vtexcommerce-new-order | Email is sent when the order is completed | Checkout places a new order |
-| Replace Order | vtexcommerce-replace-order | Email is sent when the order was successfully replaced | Checkout places a new order and informs OMS of the replacement |
-| Order change payment | vtexcommerce-order-change-payment | Notifies that the payment has been changed | Customer changes the payment and Checkout notifies OMS that the payment has been changed |
-| Payment pending | vtexcommerce-payment-pending | Notifies of pending payment  | OMS sends the e-mail 2 days before the boleto expires |
-| Payment approved | vtexcommerce-payment-approved | Notifies that payment was approved | Order status changes to __Payment Approved__ |
-| Change of information order | vtexcommerce-order-changed | Notifies that the [order has been changed](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) | Checkout notifies of order changed event (discount, add item or remove item) |
-| Order invoiced | vtexcommerce-order-invoiced | Notifies that the order was invoiced | Order status changes to __Invoiced__ |
-| Cancel billed request | vtexcommerce-order-invoiced-with-cancel-request | Notifies that the order can't be cancelled after being invoiced | Seller denies a cancellation request when the order has the Handling Shipping status |
-| Cancel shipped order | vtexcommerce-order-shipped-with-cancel-request | Notifies that the order can't be canceled after it has been shipped | Seller denies a cancellation request when the order has alraedy received a tracking number or tracking URL data |
-| Order shipped | vtexcommerce-order-shipped | Notify the order was shipped | Order receives invoice with tracking number or tracking URL data |
-| Shipping Update | vtexcommerce-order-shipping-update | Notification of delivery events, like "collected by the carrier" and "delivery route has started", for example. | The order must have the invoice and a tracking number or tracking URL attached to the invoice. It should also include delivery events, the main information of this template |
+| Order confirmation | vtexcommerce-new-order | Email is sent when the order is completed. | Checkout places a new order. |
+| Replace Order | vtexcommerce-replace-order | Email is sent when the order was successfully replaced. | Checkout places a new order and informs OMS of the replacement. |
+| Order change payment | vtexcommerce-order-change-payment | Notifies that the payment has been changed. | Customer changes the payment and Checkout notifies OMS that the payment has been changed. |
+| Payment pending | vtexcommerce-payment-pending | Notifies of pending payment. | OMS sends the e-mail 48 hours after placing the order. |
+| Payment approved | vtexcommerce-payment-approved | Notifies that payment was approved. | Order status changes to __Payment Approved__. |
+| Change of information order | vtexcommerce-order-changed | Notifies that the [order has been changed](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190). | Checkout notifies of order changed event (discount, add item or remove item). |
+| Order invoiced | vtexcommerce-order-invoiced | Notifies that the order was invoiced. | Order status changes to __Invoiced__. |
+| Cancel billed request | vtexcommerce-order-invoiced-with-cancel-request | Notifies that the order can't be cancelled after being invoiced. | Seller denies a cancellation request when the order has the Handling Shipping status. |
+| Cancel shipped order | vtexcommerce-order-shipped-with-cancel-request | Notifies that the order can't be canceled after it has been shipped. | Seller denies a cancellation request when the order has alraedy received a tracking number or tracking URL data. |
+| Order shipped | vtexcommerce-order-shipped | Notify the order was shipped. | Order receives invoice with tracking number or tracking URL data. If sending for the first time, you will need to fill in both information: `trackingNumber` and `trackingURL`. |
+| Shipping Update | vtexcommerce-order-shipping-update | Notification of delivery events, like "collected by the carrier" and "delivery route has started", for example. | The order must have the invoice and a tracking number or tracking URL attached to the invoice. It should also include delivery events, the main information of this template. |
 | Order delivered | vtexcommerce-order-shipping-finished | Notifies that shipping is completed. The order must have the invoice and a tracking number or tracking URL attached to the invoice. | Seller confirms delivery. This action changes the field `isDelivered` value to `true` on the order json. |
-| Order cancelled | vtexcommerce-order-cancelled | Order cancellation notification | Order status changes to __Cancelled__ |
-| [Order refund](https://help.vtex.com/en/tutorial/template-de-e-mail-transacional-para-pedido-estornado--5uy6FCBb6DLyIJlSDeM10G) | vtexcommerce-order-refunded | Order refund notification | Seller inserts invoice with the refund value through the [Order Invoice Notification]() API, with `input` as the value on the `type` field. In the Admin, this event is triggered when you click on the __Return items__ button on the order details page |
+| Order cancelled | vtexcommerce-order-cancelled | Order cancellation notification. | Order status changes to __Cancelled__. |
+| [Order refund](https://help.vtex.com/en/tutorial/template-de-e-mail-transacional-para-pedido-estornado--5uy6FCBb6DLyIJlSDeM10G) | vtexcommerce-order-refunded | Order refund notification. | Seller inserts invoice with the refund value through the [Order Invoice Notification](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice) API, with `input` as the value on the `type` field. In the Admin, this event is triggered when you click on the __Return items__ button on the order details page. |
diff --git a/docs/tutorials/en/orderform-settings.md b/docs/tutorials/en/orderform-settings.md
new file mode 100644
index 000000000..c7e74258f
--- /dev/null
+++ b/docs/tutorials/en/orderform-settings.md
@@ -0,0 +1,40 @@
+---
+title: 'orderForm settings'
+id: 7EAqNk48KP2QHnCxu856jT
+status: DRAFT
+createdAt: 2024-06-18T13:34:07.902Z
+updatedAt: 2024-06-18T13:44:46.612Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Shopping
+author: 1malnhMX0vPThsaJaZMYm2
+slug: orderform-settings
+locale: en
+legacySlug: orderform-settings
+subcategory: 
+---
+
+# orderForm settings
+
+In the following sections, you'll find some of the security settings available in Checkout that can be enabled by the [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) endpoint.
+
+## Require login when placing an order
+
+Setting the `requiresLoginToPlaceOrder` field to `true` allows purchases to be made only by customers who have gone through the authentication process. The customer must be logged in using the same email address provided when products were added to the cart.
+
+When you choose to enable this field, [SmartCheckout](https://help.vtex.com/en/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB) will be disabled for all your customers.
+
+## Minimum time between orders
+
+By setting a numeric value for the `minimumPurchaseDowntimeSeconds` field, you can determine the minimum time in seconds a buyer must wait before placing another order. This setting prevents customers from creating multiple orders in a short time.
+
+We recommend setting this field to 90 seconds and using this setting in combination with [Require login to place order](#require-login-to-place-order).
+
+## Minimum time for a cart to exist before a new credit card can be used
+
+Setting a numeric value in the `cartAgeToUseNewCardSeconds` field specifies how many seconds a new cart needs to exist before a new credit card can be used.
+
+This setting reduces the risk of creating multiple carts and adding new credit cards. Activating this field does not affect orders placed with cards previously saved in the customer account.
+
+We recommend setting this field to 30 seconds.
diff --git a/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md b/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
index 0b7fed995..5d3a6b20d 100644
--- a/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
+++ b/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
@@ -29,6 +29,6 @@ Among all SKU images, the principal image will be that marked as the principal i
 
 As you can see in the example below, even not being the first image registered, the image defined as principal appears on the product page when the SKU is selected.
 
-![sku_imagem_principal en](https://images.ctfassets.net/alneenqid6w5/391ITg389WwqEsUYe2sUe8/0b7ae4c9e54ce81ef067a4bba83712e3/ex_2__en.png)
+![sku_imagem_principal en](//images.ctfassets.net/alneenqid6w5/391ITg389WwqEsUYe2sUe8/0b7ae4c9e54ce81ef067a4bba83712e3/ex_2__en.png)
 
 - When uploading the image spreadsheet, the platform considers line by line; then, the first line of a sku will be considered the main one and so on.
diff --git a/docs/tutorials/en/orders-list.md b/docs/tutorials/en/orders-list.md
index 1e7092881..d4d49a290 100644
--- a/docs/tutorials/en/orders-list.md
+++ b/docs/tutorials/en/orders-list.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Using the list of orders from the Orders Managment, stores owner can monitor purchases made in their store. The list is available on the first screen of the Orders Managment module.
 
-![todosospedidos.en](https://images.ctfassets.net/alneenqid6w5/4ovDqNLqLNMUxrwjgQ8oDx/2557b8aa39c07af3ce23f85508b49de3/todosospedidos.en.png)
+![todosospedidos.en](//images.ctfassets.net/alneenqid6w5/4ovDqNLqLNMUxrwjgQ8oDx/2557b8aa39c07af3ce23f85508b49de3/todosospedidos.en.png)
 
 The standard view lists all store orders, beginning with the most recent. You can change the order by clicking on the column names, as well as by searching or filtering the orders using specific data, in addition to exporting this data.
 
@@ -30,7 +30,7 @@ By clicking on any order, the user is directed to the order details page.
 
 Whenever Orders Managment is open and new orders are placed, a notice will be displayed, allowing you to click and update the list of orders.
 
-![novopedido.en](https://images.ctfassets.net/alneenqid6w5/7c1NoN8MjO6b9jI6YAUVzM/6b461e799f1dd8f7039bf9a8b1755ae5/novopedido.en.png)
+![novopedido.en](//images.ctfassets.net/alneenqid6w5/7c1NoN8MjO6b9jI6YAUVzM/6b461e799f1dd8f7039bf9a8b1755ae5/novopedido.en.png)
 
 See more details about the columns on the list below:
 
@@ -38,7 +38,7 @@ See more details about the columns on the list below:
 
 Nothing more than the order number (displayed to the customer), with the suffix and the sequential transaction code (for in-house use).
 
-![nsequencial.en](https://images.ctfassets.net/alneenqid6w5/4BOiejle8VtmGM364EiKXl/bb1e5d5d8b1020ce6d89c01262ef644c/nsequencial.en.png)
+![nsequencial.en](//images.ctfassets.net/alneenqid6w5/4BOiejle8VtmGM364EiKXl/bb1e5d5d8b1020ce6d89c01262ef644c/nsequencial.en.png)
 
 ### Order number
 
diff --git a/docs/tutorials/en/orders-overview.md b/docs/tutorials/en/orders-overview.md
index 760cdca2d..875419561 100644
--- a/docs/tutorials/en/orders-overview.md
+++ b/docs/tutorials/en/orders-overview.md
@@ -3,8 +3,8 @@ title: 'Orders Overview'
 id: tutorials_201
 status: PUBLISHED
 createdAt: 2017-04-27T22:13:42.525Z
-updatedAt: 2023-04-26T14:51:44.363Z
-publishedAt: 2023-04-26T14:51:44.363Z
+updatedAt: 2023-12-21T14:01:20.828Z
+publishedAt: 2023-12-21T14:01:20.828Z
 firstPublishedAt: 2017-04-27T23:03:03.051Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -30,6 +30,17 @@ This section includes the following pages:
 - [Transactions](https://help.vtex.com/en/tutorial/how-to-view-transactions-on-pci-gateway--tutorials_461) 
 - [Bank reconciliation](https://help.vtex.com/en/tutorial/bank-reconciliations--tutorials_453) 
 
+Besides searching for orders in **Orders > All Orders**, you can search for orders from any page in the VTEX Admin using the global search bar at the top bar. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
+
+<div class = "alert alert-info">
+You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
+</div>
+
 ## Subscriptions
 
 On the VTEX platform, you can create [subscriptions](https://help.vtex.com/en/tutorial/how-subscriptions-work--frequentlyAskedQuestions_4453), which means that you can offer your customers the possibility to automatically place recurring orders at a set frequency.
diff --git a/docs/tutorials/en/orders.md b/docs/tutorials/en/orders.md
new file mode 100644
index 000000000..b60753c0c
--- /dev/null
+++ b/docs/tutorials/en/orders.md
@@ -0,0 +1,372 @@
+---
+title: 'Orders Data Pipeline (Beta)'
+id: 2f3GlRJ5L5IRGVIxOmzrFv
+status: PUBLISHED
+createdAt: 2024-02-02T17:58:53.962Z
+updatedAt: 2024-06-21T16:26:28.394Z
+publishedAt: 2024-06-21T16:26:28.394Z
+firstPublishedAt: 2024-05-27T19:26:59.238Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: orders
+locale: en
+legacySlug: orders
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+The order dataset is composed of two main tables: `orders_historical` and `orders_latest`. These tables include several `SUPER` fields that encompass information such acquired items, shipping details, related sellers, payments, among others.
+
+We have implemented special auxiliary tables, such as `orders_shipping` and `orders_items` to help manage this data, which can be a complex task due to the 1-to-N relationship between many of the `SUPER` fields and the orders and the amount of information they contain.
+
+When running analyses, it's common to create direct selections in the `SUPER` fields to highlight specific parts for extraction. You can also join one of the main tables (`orders` or `latest`) to the auxiliary tables, using orderid as key.
+
+This method allows you to efficiently extract specific information, enabling a detailed analysis of the orders and their related components.
+
+This section includes the following information:
+
+- [Characteristics of order data](#data-characteristics)
+- [Table: orders_latest](#table-orders_latest)
+- [Table: orders_historical](#table-orders_historical)
+- [Table: orders_totals](#table-orders_totals)
+- [Table: orders_shipping](#table-orders_shipping)
+- [Table: orders_sellers](#table-orders_sellers)
+- [Table: orders_rateandbenefitsidentifiers](#table-orders_rateandbenefitsidentifiers)
+- [Table: orders_payments](#table-orders_payments)
+- [Table: orders_packages](#table-orders_packages)
+- [Table: orders_items](#table-orders_items)
+- [Analyses with order data](#analyses-with-order-data)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics
+
+|**Characteristic**|**Description**|
+| - | - |
+|**Data source**|The data of the order set come from the [OMS (Order Management System)](https://help.vtex.com/en/tutorial/gerenciamento-de-pedidos-visao-geral--tutorials_201).|
+|**Availability**|Order data can be accessed through the [Orders report](https://help.vtex.com/en/tutorial/exportacao-de-pedidos-no-modulo-pedidos--tutorials_6417) in the VTEX Admin and also through the[ Orders APIs](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders?endpoint=get-/api/oms/pvt/orders). Keep in mind that the data available through the API may not be structured exactly the same way as it is in the Data Pipeline dataset.|
+|**History**|The data is retained for two years, from 2022 for clients who already use the VTEX platform.|
+|**Minimum update interval**|One hour.|
+
+## Table: orders_latest
+
+The *latest* table stores the latest status of each order, including details such as update date, order ID, and customer information. The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier of the order.|
+|hostname|character varying(16383)|Name of the host related to the order.|
+|value|double precision|Total amount of the order.|
+|totals|super|Summary of order totals, such as subtotal, taxes, discounts, etc.|
+|creationdate|timestamp with time zone|Date and time the order was created.|
+|items|super|Detailed information about the order items.|
+|clientprofiledata_userprofileid|character varying(65535)|Profile ID of the user in the customer management system.|
+|shippingdata_address_city|character varying(65535)|Shipping city of the order.|
+|shippingdata_address_state|character varying(65535)|Shipping state of the order.|
+|shippingdata_address_country|character varying(65535)|Shipping country of the order.|
+|shippingdata_logisticsinfo|super|Logistical information about order shipment.|
+|sellers|super|Information about the sellers associated with the order.|
+|storepreferencesdata_countrycode|character varying(65535)|Country code of the store.|
+|storepreferencesdata_timezone|character varying(65535)|Time zone of the store.|
+|storepreferencesdata_currencycode|character varying(65535)|Code of the currency used in the store.|
+|packages|super|Details about the packaging used for order items.|
+|origin|character varying(16383)|Source of the order.|
+|iscompleted|boolean|Specifies whether the order is completed.|
+|affiliateid|character varying(16383)|Affiliate ID associated with the order.|
+|status|character varying(16383)|Current status of the order.|
+|authorizeddate|timestamp with time zone|Date and time of order authorization.|
+|invoiceddate|timestamp with time zone|Date and time of issue of order invoice.|
+|marketplaceorderid|character varying(16383)|Order ID in the marketplace.|
+|marketplaceservicesendpoint|character varying(16383)|Service endpoint of the marketplace.|
+|lastchange|timestamp with time zone|Date and time of the last change to the order.|
+|marketingdata_utmsource|character varying(65535)|UTM source for marketing purposes.|
+|marketingdata_utmmedium|character varying(65535)|UTM medium for marketing purposes.|
+|marketingdata_utmcampaign|character varying(65535)|UTM campaign for marketing purposes.|
+|marketingdata_utmpartner|character varying(65535)|UTM partner for marketing purposes.|
+|marketingdata_utmipage|character varying(65535)|UTM page for marketing purposes.|
+|marketingdata_utmipart|character varying(65535)|UTM part for marketing purposes.|
+|marketingdata_utmicampaign|character varying(65535)|Alternative UTM campaign for marketing purposes.|
+|marketingdata_coupon|character varying(65535)|Discount coupon code applied to the order.|
+|marketingdata_marketingtags|super|Marketing tags associated with the order.|
+|marketplace_name|character varying(65535)|Name of the marketplace associated with the order.|
+|marketplace_iscertified|super|Specifies whether the marketplace is certified.|
+|marketplace_baseurl|character varying(65535)|Base URL of the marketplace.|
+|contextdata_loggedin|super|Specifies whether the user was logged in while placing the order.|
+|contextdata_useragent|character varying(65535)|User agent used when placing the order.|
+|contextdata_userid|character varying(65535)|ID of the user who placed the order.|
+|rateandbenefitsidentifiers|super|Identifiers of charges and promotions applied to the order.|
+|transactions|super|Details of the financial transactions of the order.|
+|giftcards|super|Information about gift cards used in the order.|
+|saleschannel|character varying(16383)|Sales channel through which the order was placed.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|
+|sellerorderid|character varying(16383)|Order ID assigned by the seller.|
+|ordergroup|character varying(16383)|Order group this order belongs to.|
+|workflowisinerror|boolean|Specifies whether there was an error in the order workflow.|
+|clientprofiledata_email|character varying(256)|Email of the customer profile associated with the order.|
+|changesattachment_id|character varying(256)|ID of the customization attachment of the order.|
+|changesattachment_changesdat a|super|Details of changes made to the order.|
+|shippingdata_postal_code|character varying(256)|Postal code of the order's shipping address.|
+
+## Table: orders_historical
+
+The `historical` table stores a complete record of all order updates. The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order, usually used as the primary key.|
+|hostname|character varying(16383)|Name of the host associated with the order, which indicates the server or domain that is managing the order.|
+|value|double precision|Total monetary value of the order. It may include taxes, discounts, and shipping costs.|
+|totals|super|Summary of order totals. It may be broken down into subtotals, taxes, discounts, etc.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|items|super|Detailed information about the order items. It may include SKU, quantity, price, and item-specific discounts.|
+|clientprofiledata_userprofileid|character varying(65535)|User profile identifier of the customer who placed the order.|
+|shippingdata_address_city|character varying(65535)|City portion of the order's shipping address.|
+|shippingdata_address_state|character varying(65535)|State or region portion of the order's shipping address.|
+|shippingdata_address_country|character varying(65535)|Country portion of the order's shipping address.|
+|shippingdata_logisticsinfo|super|Logistical information related to the order shipment. It may include carrier details and tracking information.|
+|sellers|super|Information about the sellers associated with the order. It may include seller IDs and names.|
+|storepreferencesdata_countryc ode|character varying(65535)|Country code of the store where the order was placed.|
+|storepreferencesdata_timezone|character varying(65535)|Time zone of the store where the order was placed.|
+|storepreferencesdata_currency code|character varying(65535)|Currency code used in the order transaction.|
+|packages|super|Details about packaging of order items. It may include packaging types and dimensions.|
+|origin|character varying(16383)|Source of the order, including where and how the order was started.|
+|iscompleted|boolean|Specifies whether the order was completed.|
+|affiliateid|character varying(16383)|Identifier of an affiliate or reference source associated with the order.|
+|status|character varying(16383)|Current status of the order, such as 'pending', 'shipped', or 'completed'.|
+|authorizeddate|timestamp with time zone|Date and time the order was authorized.|
+|invoiceddate|timestamp with time zone|Date and time the order invoice was issued.|
+|marketplaceorderid|character varying(16383)|Order identifier within a marketplace, if applicable.|
+|marketplaceservicesendpoint|character varying(16383)|Endpoint or URL for marketplace services related to the order.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order.|
+|marketingdata_utmsource|character varying(65535)|UTM source parameter in marketing data, indicating the traffic or campaign origin.|
+|marketingdata_utmmedium|character varying(65535)|UTM medium parameter in marketing data, indicating the campaign medium (e.g., email, social).|
+|marketingdata_utmcampaign|character varying(65535)|UTM campaign parameter in marketing data, indicating the specific campaign name or code.|
+|marketingdata_utmpartner|character varying(65535)|UTM partner parameter, indicating a marketing partnership or collaborator.|
+|marketingdata_utmpartner|character varying(65535)|UTM page parameter. It may indicate the specific page or location of the campaign.|
+|marketingdata_utmipart|character varying(65535)|UTM part parameter. It may indicate a specific component or section of the marketing campaign.|
+|marketingdata_utmicampaign|character varying(65535)|UTM alternative campaign parameter for additional campaign tracking.|
+|marketingdata_coupon|character varying(65535)|Coupon code used, if any, for applying discounts to the order.|
+|marketingdata_marketingtags|super|Tags or keywords associated with the order's marketing efforts.|
+|marketplace_name|character varying(65535)|Name of the marketplace where the order was placed, if applicable.|
+|marketplace_iscertified|super|Specifies whether the marketplace where the order was placed is certified or recognized.|
+|marketplace_baseurl|character varying(65535)|Base URL of the marketplace where the order was placed.|
+|contextdata_loggedin|super|Specifies whether the user was logged in when placing the order.|
+|contextdata_useragent|character varying(65535)|User-agent string of the browser or device used when placing the order.|
+|contextdata_userid|character varying(65535)|ID of the user who placed the order.|
+|rateandbenefitsidentifiers|super|Identifiers of charges and promotions applied to the order, such as loyalty points or member discounts.|
+|transactions|super|Detailed information about the financial transactions associated with the order.|
+|giftcards|super|Information about gift cards used in the order.|
+|saleschannel|character varying(16383)|Sales channel through which the order was placed (online store, physical store, or others).|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|
+|sellerorderid|character varying(16383)|An order ID assigned by the seller, different from the main order ID.|
+|ordergroup|character varying(16383)|Order group the order belongs to, used to group several orders together.|
+|workflowisinerror|boolean|Specifies whether there was an error in the order processing workflow.|
+|clientprofiledata_email|character varying(256)|Email address of the customer associated with the order.|
+|changesattachment_id|character varying(256)|Unique identifier for a change operation related to the order.|
+|changesattachment_changesda ta|super|Details of changes made to the order, such as adding or removing items and other modifications.|
+|shippingdata_postal_code|character varying(256)|Postal code of the order's shipping address.|  
+
+## Table: orders_totals
+
+The *totals* table provides a summary of the totals related to each order, including total order amount, applied discounts, and taxes. The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order. This is usually joined with the 'orderid' column of the 'vtex.orders_latest' table for cross-analysis.|
+|hostname|character varying(16383)|Name of the host associated with the order, which indicates the server or domain that is managing the order.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order, reflecting the most recent status or content update.|
+|status|character varying(16383)|Current status of the order. This is frequently joined with the 'status' column of the 'vtex.orders_latest' table to track status changes.|
+|totals_id|character varying(65535)|Unique identifier for order totals, used to reference specific details of the order total.|
+|totals_name|character varying(65535)|Name or description of the order totals, giving an overview of what the total represents (for example: subtotal, taxes, discounts).|
+|totals_value|double precision|Numeric value associated with order totals, such as the total amount, subtotal, taxes, discounts, etc.|
+|batch_id| character varying(13) |Identifier used when data is loaded into the table for quality control of data ingestion.|  
+
+## Table: orders_shipping
+
+The *shipping* table contains order shipping information, such as shipping address, shipping costs, and logistics service providers. 
+
+The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order.|
+|hostname|character varying(16383)|Name of the host related to the order. This is frequently joined with 'hostname' from the 'vtex.client_registry_gold' table.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change to the order.|
+|status|character varying(16383)|Current status of the order.|
+|shippingdata_address_city|character varying(65535)|City of the order's shipping address.|
+|shippingdata_address_state|character varying(65535)|State of the order's shipping address.|
+|shippingdata_address_country|character varying(65535)|Country of the order's shipping address.|
+|deliveryids|super|Identifiers associated with order delivery.|
+|shippingestimate|character varying(65535)|Estimated shipping time.|
+|pickupstoreinfo_ispickupstore|boolean|Specifies whether the pickup location is a physical store.|
+|pickupstoreinfo_friendlyname|character varying(65535)|Friendly name of the pickup location.|
+|pickupstoreinfo_dockid|character varying(65535)|Pickup location identifier.|
+|deliverychannel|character varying(65535)|Delivery channel used for the order.|
+|deliverywindow|character varying(65535)|Estimated time window for delivery.|
+|sellingprice|double precision|Sales price of the order item.|
+|listprice|double precision|List price of the order item.|
+|price|double precision|Final price of the order item.|
+|shippingestimatedate|timestamp with time zone|Estimated shipping date for the order.|
+|selecteddeliverychannel|character varying(65535)|Delivery channel selected for the order.|
+|selectedsla|character varying(65535)|Service level agreement (SLA) selected for the order.|
+|deliverychannels|super|Delivery channels available for the order.|
+|slas|super|Available SLAs for the order.|
+|pickupdistance|double precision|Distance to the pickup location.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|
+|shippingdata_postal_code|character varying(256)|Postal code of the order's shipping address.|  
+
+## Table: orders_sellers
+
+The *sellers* table stores the list of sellers related to each order. The table fields are described below:  
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order. This is frequently joined with the 'orderid' column of the 'vtex.orders_historical' table for cross-analysis.|
+|hostname|character varying(16383)|Name of the host associated with the order, which indicates the server or domain that is managing the order.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order, reflecting the most recent status or content update.|
+|status|character varying(16383)|Current status of the order.|
+|id|character varying(65535)|Unique identifier, generally used to refer to a specific element within a larger context.|
+|name|character varying(65535)|Name or title of the referenced element, providing a human-readable identification.|
+|logo|character varying(65535)|Path or URL to the associated logo, often used for branding or visual identification.|
+|fulfillmentendpoint|character varying(65535)|Endpoint or URL for fulfillment services that specifies where order fulfillment operations are managed.|
+|subsellerid|character varying(65535)|Identifier for a subseller or secondary seller associated with the order or operation.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|  
+
+# Table: orders_rateandbenefitsidentifiers
+
+The *rateandbenefitsidentifiers* table contains data about promotions applied to orders. The table fields are described below: 
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order.|
+|hostname|character varying(16383)|Name of the host associated with the order, which indicates the server or domain that is managing the order.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order, reflecting the most recent status or content update.|
+|status|character varying(16383)|Current status of the order.|
+|rateandbenefitsidentifiers_id|character varying(65535)|Unique identifier for surcharge and promotion identifiers associated with the order.|
+|rateandbenefitsidentifiers_name|character varying(65535)|Name or title of surcharge and promotion identifiers, providing clear identification for the promotion or surcharge.|
+|rateandbenefitsidentifiers_featur ed|boolean|Specifies whether surcharge and promotion identifiers are highlighted or have a special feature.|
+|rateandbenefitsidentifiers_descri ption|character varying(65535)|Detailed description of surcharge and promotion identifiers, explaining their features or benefits.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|  
+
+## Table: orders_payments
+
+The *payments* table contains payment method information. The table fields are described below:  
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order. This is frequently joined with the 'orderid' column of the 'vtex.orders_latest' table.|
+|hostname|character varying(16383)|Name of the host associated with the order, which indicates the server or domain that is managing the order.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order, reflecting the most recent status or content update.|
+|status|character varying(16383)|Current status of the order.|
+|transactions_merchantname|character varying(65535)|Name of the merchant associated with the order transaction.|
+|group|character varying(65535)|Group or category the order or element belongs to.|
+|installments|integer|Number of installments to pay the order.|
+|value|double precision|Monetary value associated with the transaction or order element.|
+|transactions_paymentsystemname|character varying(65535)|Name of the payment system used in the transaction.|
+|transactions_paymentsystem|character varying(65535)|Identifier of the payment system used in the transaction.|
+|giftcards_id|character varying(65535)|Unique identifier of the gift card used in the order.|
+|giftcards_name|character varying(65535)|Name of the gift card used.|
+|giftcards_caption|character varying(65535)|Description or caption of the gift card used.|
+|giftcards_value|double precision|Monetary value of the gift card.|
+|giftcards_balance|double precision|Remaining gift card balance after use.|
+|giftcards_provider|character varying(65535)|Gift card provider or issuer.|
+|giftcards_groupname|character varying(65535)|Name of the group or category the gift card belongs to.|
+|giftcards_inuse|boolean|Specifies whether the gift card is in use or has been used in the order.|
+|giftcards_isspecialcard|boolean|Specifies whether this is a special or promotional gift card.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|
+|transactions_transactionid|character varying(65535)|Unique identifier of the financial transaction associated with the order.|
+|transactions_referencevalue|double precision|Transaction reference value. This will probably be the total amount before discounts or charges.|
+
+## Table: orders_packages
+
+The *packages* table stores product packaging and shipping information. The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order.|
+|hostname|character varying(16383)|Name of the host associated with the order, which indicates the server or domain that is managing the order.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order, reflecting the most recent status or content update.|
+|status|character varying(16383)|Current status of the order.|
+|courier|character varying(65535)|Name of the carrier company or delivery service associated with the order.|
+|invoicenumber|character varying(65535)|Invoice number associated with the order.|
+|invoicevalue|double precision|Total amount indicated on the order invoice.|
+|invoiceurl|character varying(65535)|URL to access the electronic invoice for the order.|
+|issuancedate|timestamp with time zone|Date of issue of the order invoice.|
+|trackingnumber|character varying(65535)|Tracking number associated with order delivery.|
+|invoicekey|character varying(65535)|Unique key that identifies the order invoice.|
+|trackingurl|character varying(65535)|URL for tracking order delivery.|
+|embeddedinvoice|character varying(65535)|Embedded information or details of the order invoice.|
+|type|character varying(65535)|Type or category of the element or service associated with the order.|
+|courierstatus_delivereddate|timestamp with time zone|Delivery date of the order as recorded by the carrier service.|
+|courierstatus_status|character varying(65535)|Current delivery status as recorded by the carrier service.|
+|courierstatus_finished|boolean|Specifies whether the delivery process has been completed.|
+|courierstatus_data|super|Detailed data about the delivery status provided by the carrier service.|
+|cfop|character varying(65535)|Código Fiscal de Operações e Prestações (CFOP) code associated with the order in Brazil.|
+|packages_lastchange|timestamp with time zone|Date and time of the last change recorded in the order packages.|
+|volumes|integer|Total number of packages in the order.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|
+
+## Table: orders_items
+
+The *items* table stores details about the individual items in each order, including SKU, quantity, price, and discounts. The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|orderid|character varying(16383)|Unique identifier for each order. This is usually joined with the 'orderid' column of the 'vtex.orders_latest' table.|
+|hostname|character varying(16383)|Name of the host associated with the order. This is frequently joined with columns from other tables, such as 'vtex.client_registry_gold.hostname'.|
+|creationdate|timestamp with time zone|Date and time the order was created, including time zone.|
+|lastchange|timestamp with time zone|Date and time of the last change made to the order.|
+|status|character varying(16383)|Current status of the order.|
+|tax|double precision|Tax amount applied to the order.|
+|id|character varying(65535)|Unique identifier, frequently joined with 'sku_id' from the 'vtex.fulfillment_simulations_ca_silver' table.|
+|productid|character varying(65535)|Product identifier associated with the order.|
+|quantity|integer|Product quantity in the order.|
+|seller|character varying(65535)|Identifier or name of the product seller.|
+|sellersku|character varying(65535)|Product SKU as listed by the seller.|
+|pricevaliduntil|timestamp with time zone|Date and time the product price is valid through.|
+|name|character varying(65535)|Name of the product.|
+|additionalinfo_brandname|character varying(65535)|Product brand name.|
+|additionalinfo_brandid|character varying(65535)|Product brand identifier.|
+|additionalinfo_caregoriesid|character varying(65535)|Category identifiers associated with the product.|
+|additionalinfo_dimension_cubicw eight|double precision|Cubic weight of the product for shipping purposes.|
+|additionalinfo_dimension_height|double precision|Product height.|
+|additionalinfo_dimension_length|double precision|Product length.|
+|additionalinfo_dimension_weight|double precision|Product weight.|
+|additionalinfo_dimension_width|double precision|Product width.|
+|price|double precision|Product price.|
+|pricetags|super|Price tags associated with the product. This may include discounts and offers.|
+|sellingprice|double precision|Sales price of the product.|
+|listprice|double precision|List price of the product.|
+|imageurl|character varying(65535)|Product image URL.|
+|measurementunit|character varying(65535)|Unit of measure of the product.|
+|unitmultiplier|double precision|Unit multiplier for the product, used in price and quantity calculations.|
+|batch_id|character varying(13)|Identifier used when data is loaded into the table for quality control of data ingestion.|
+
+## Analyses with order data
+
+Order data can be used in the following analyses:
+
+- **Ecommerce website sales analysis:** Evaluate sales volume, identify best-selling products, analyze seasonal trends, and get insights into consumer behavior.  
+- **Order cancellation rate analysis:** Look into cancellation reasons, identify patterns related to specific products or logistical problems, and develop strategies to reduce cancellation rates.  
+- **SKU performance:** Analyze the performance of individual SKUs, understand market demand, and make adjustments to inventory and marketing strategies.  
+
+## Correlations with other data
+
+The order dataset has correlations with the following sets of the VTEX data ecosystem:
+
+- **Navigation:** Correlating navigation data with orders offers insights into consumer behavior and the purchasing journey, which helps optimize the user experience.  
+- **Promotions:** Interaction with promotion data is key for assessing the effectiveness of promotional campaigns on order volumes and types.  
+- **Transactions:** Joint analysis with transaction data can reveal payment patterns, consumer preferences, and payment processing efficiency.   
+
+### Discover other datasets
+
+- [Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navegation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Payments](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)   
+- [Prices](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promotions](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/en/overview-of-b2b-orders-history.md b/docs/tutorials/en/overview-of-b2b-orders-history.md
new file mode 100644
index 000000000..e3918f46c
--- /dev/null
+++ b/docs/tutorials/en/overview-of-b2b-orders-history.md
@@ -0,0 +1,30 @@
+---
+title: 'Overview of B2B Orders History'
+id: C2i93MZmjSrqhEx16YYuA
+status: PUBLISHED
+createdAt: 2024-07-26T13:17:45.094Z
+updatedAt: 2024-07-26T14:02:09.115Z
+publishedAt: 2024-07-26T14:02:09.115Z
+firstPublishedAt: 2024-07-26T14:02:09.115Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: overview-of-b2b-orders-history
+locale: en
+legacySlug: overview-of-b2b-orders-history
+subcategory: 2LaAukjQB4QEbqSYdgjq7l
+---
+
+In a [B2B operation](https://help.vtex.com/pt/tutorial/b2b-visao-geral--5vb9SNXhX2bZnkpAh7ADdC), multiple users from the same organization place orders on behalf of the company. The **B2B Orders History** app was developed to meet these specific needs, allowing users to view and manage orders in an integrated and collaborative way.
+
+## Feature
+The **B2B Orders History** app replaces the standard Orders page in [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) with a version tailored to the B2B scenario. This customization allows logged-in [users](https://help.vtex.com/en/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA) of an organization to view their orders and access orders placed by other members of the same organization or cost center, provided they have the necessary permissions.
+
+## Advantages
+A centralized view of orders is important to:
+
+- Allow all authorized members of the organization to monitor their orders, avoiding duplication and errors.
+- Facilitate order management, ensuring all orders comply with company policies.
+- Provide quick and easy access to orders, improving operational efficiency and facilitating decision-making.
+
+For more information, see [B2B Orders History](https://developers.vtex.com/docs/apps/vtex.b2b-orders-history).
diff --git a/docs/tutorials/en/overview-pricing-module.md b/docs/tutorials/en/overview-pricing-module.md
index 2cc6014fc..ff2529e27 100644
--- a/docs/tutorials/en/overview-pricing-module.md
+++ b/docs/tutorials/en/overview-pricing-module.md
@@ -21,7 +21,7 @@ There are four departments within this module responsible for configuring each o
 
 ## Campaign Audiences
 
-![campanha-en](https://images.ctfassets.net/alneenqid6w5/5K7LSd8kVJ6Zq1EnDUPxHF/17299aa9e8c91b40b427b402e6c09e70/campanha-en.png)
+![campanha-en](//images.ctfassets.net/alneenqid6w5/5K7LSd8kVJ6Zq1EnDUPxHF/17299aa9e8c91b40b427b402e6c09e70/campanha-en.png)
 
 A campaign audience is a way of defining the target audience to which a benefit can be applied. In other words, you can create customer segments based on the definition of some criteria that will be eligible for a given campaign audience and consequently one or more benefits. A campaign audience can be associated with one or more campaign benefits.
 
@@ -29,7 +29,7 @@ A campaign audience is a way of defining the target audience to which a benefit
 
 ## Benefits
 
-![promoções.en](https://images.ctfassets.net/alneenqid6w5/23MV9Zb4N0CLUcyoeZaP1r/08a7f435db69a7a826ba336b58603a45/promo____es.en.png)
+![promoções.en](//images.ctfassets.net/alneenqid6w5/23MV9Zb4N0CLUcyoeZaP1r/08a7f435db69a7a826ba336b58603a45/promo____es.en.png)
 
 Here, the discounts that your store will offer are created. You can also view, filter, search and file all promotions. According to each store configuration, there is a limit of promotions that can be enabled at the same time. To find out how many, read the message that appears on the upper right corner, below the paging. The types of promotions that can be created are:
 
@@ -42,12 +42,12 @@ Here, the discounts that your store will offer are created. You can also view, f
 
 ## Coupons
 
-![cupons.en](https://images.ctfassets.net/alneenqid6w5/4dFwRo3yG2ZLWwFosYJBRI/5a717e969314bd7492d9a6d1d4f24f7a/cupons.en.png)
+![cupons.en](//images.ctfassets.net/alneenqid6w5/4dFwRo3yG2ZLWwFosYJBRI/5a717e969314bd7492d9a6d1d4f24f7a/cupons.en.png)
 
 It's in this department that the coupons are created, but you can also search and file them. [Learn how to create coupons in our documentation](/en/tutorial/creating-a-coupon/).
 
 ## Taxes
 
-![taxas.en](https://images.ctfassets.net/alneenqid6w5/4kQJ4px0w7kUgDdzmc1lR0/f9ee86721f6888e957be3db820f3afbb/taxas.en.png)
+![taxas.en](//images.ctfassets.net/alneenqid6w5/4kQJ4px0w7kUgDdzmc1lR0/f9ee86721f6888e957be3db820f3afbb/taxas.en.png)
 
 Here, you can define the incidence of taxes on your products. You can also filter, search and file fees. [To better understand the characteristics of this configuration, check out our article about fees.](/en/tutorial/creating-surchargestaxes)
diff --git a/docs/tutorials/en/payment-provider-protocol.md b/docs/tutorials/en/payment-provider-protocol.md
index c06cfd659..c36e6d7a0 100644
--- a/docs/tutorials/en/payment-provider-protocol.md
+++ b/docs/tutorials/en/payment-provider-protocol.md
@@ -3,8 +3,8 @@ title: 'Payment Provider Protocol '
 id: RdsT2spdq80MMwwOeEq0m
 status: PUBLISHED
 createdAt: 2018-01-02T15:40:00.920Z
-updatedAt: 2023-05-31T14:44:41.300Z
-publishedAt: 2023-05-31T14:44:41.300Z
+updatedAt: 2024-07-24T13:58:10.009Z
+publishedAt: 2024-07-24T13:58:10.009Z
 firstPublishedAt: 2018-01-02T17:53:48.934Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,6 @@ legacySlug: payment-provider-protocol
 subcategory: 2Xay1NOZKE2CSqKMwckOm8
 ---
 
-## What is the Payment Provider Protocol?
 The Payment Provider Protocol is the integration protocol between VTEX and other companies that process payments.
 
 Through it, VTEX offers a public contract available to all providers that wish to integrate into our platform. As a result, providers become more autonomous regarding such integration.
@@ -43,9 +42,10 @@ __Oauth:__ authorization protocol for web APIs designed to allow client applicat
 __Acquirer:__  a company that specializes in processing payments. It is responsible for transferring the values which the issuing bank receives from the client to the account of your store.
 
 ## Implementation prerequisites
-### Signing a business partnership agreement for financial services
 
-Implementing, publishing, and updating a payment connector on VTEX requires signing a partnership agreement that is **specific to financial services** covering the details of this subject and platform regulations. If you don’t have a partnership agreement yet but are interested in becoming a payment provider, contact our team through our [website](https://vtex.com/us-en/partner/).
+### A business partnership agreement for financial services
+
+For implementing, publishing, and updating a payment connector on VTEX, you need to sign a partnership agreement for financial services that covers the particularities of this domain and the regulations within the platform. If you do not have a partnership agreement yet but want to become a payment provider, please contact our team through the[website](https://vtex.com/us-en/partners).
 
 ### Access to a VTEX environment
 
@@ -54,6 +54,7 @@ To publish a connector, you need to have a VTEX environment, which you can only
 If the partner is a SI (Service Implementer) developing integrations for clients or other payment providers, the VTEX account of the main provider must be used and not the account of the contractor agency.
 
 ### Payment method requirements
+
 #### Payment providers with credit, debit or cobranded cards (solutions without redirect)
 
 To become an integrated VTEX provider, you must use one of the following solutions:
@@ -74,7 +75,7 @@ The SAQ (Self-Assessment Questionnaire) and AOC (Attestation of Compliance for O
 </div>
 <br>
 
-#### Payment providers with promissory, Brazilian boleto or private label cards (or providers of any kind of card using redirect solutions)
+#### Payment providers with notes payables, Brazilian boleto or private label cards (or providers of any kind of card using redirect solutions)
 
 For these types of providers, VTEX does not require evidence of PCI DSS certification. Just contact the VTEX commercial team to begin the integration.
 
@@ -87,113 +88,92 @@ Before setting up the VTEX environment, the provider must implement the back-end
 ### 2. Specific use cases
 In some cases, connectors can be built for a specific solution. The references below will help you identify such cases:
 
-- [Payment Provider Framework (PPF)](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework): Solution for implementing connectors through VTEX IO from a boilerplate, which already comes with most of the work done, including the protocol endpoints. VTEX IO also speeds up the development process and in-store testing.
-- [Payment Provider Protocol POS payments](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-ppp-applied-to-pos): PPP application for payments in physical stores using a payment terminal (POS), which can be used with credit and debit cards. The payment flow starts with a purchase made on [inStore](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc), then communication is established with the POS, where the customer inserts the card.
+- [Payment Provider Framework (PPF)](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework): Solution for implementing connectors through VTEX IO from a boilerplate, which already comes with most of the work done, including the protocol endpoints. VTEX IO also speeds up the development process and in-store testing.
+- [Payment Provider Protocol POS payments](https://developers.vtex.com/docs/guides/payments-integration-ppp-applied-to-pos): PPP application for payments in physical stores using a payment terminal (POS), which can be used with credit and debit cards. The payment flow starts with a purchase made on [inStore](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc), then communication is established with the POS, where the customer inserts the card.
 
 ### 3. Payment Provider Homologation 
-After receiving the access data and deploying the backend, the provider must install the Payment Provider Test Suite app to access the testing tool. Installation is done on the [VTEX App Store](https://apps.vtex.com/vtex-payment-provider-test-suite/p "VTEX App Store").
 
-![print1](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d9d72ca9a6fa585f959fa932412930d7/print1.png)
+After getting access information and implementing the backend, the provider has to install the Payment Provider Test Suite app to access the testing tool. The installation is done through the VTEX App Store.
+
+![ppp-vtex-store-en](//images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/ea2026578b79d3c5edd33c997b62efa9/image.png)
 
 <div class="alert alert-warning">
-All communication with servers, either during the homologation process or in production, must occur via HTTPS, which by default uses port 443. It is important to remember that all HTTPS communication should be exclusively with <strong>TLS 1.2</strong>.
+<p>To pass the homologation process, you need to implement specific logic to handle the test requirements. When sending requests to Test Suite, use the extra header <code>X-VTEX-API-Is-TestSuite = true</code> to identify them and mask any required case.<br><br>All communication with servers, whether during the homologation process or in production, must be via HTTPS, which by default uses port 443. Note that all HTTPS communication must be exclusively over TLS 1.2.
+</p>
 </div> 
 
-After installing it, check the Other module in Admin's left side menu. Then, select the Payment Provider option to configure it correctly.
-
-This way, you will see two forms: Service Information and Tests.
-
-Fill them out according to the instructions below:
+After installing, click __Apps__ in the left menu of the Admin. Then, select the __Payment Provider Test Suite__ app to complete the setup.
 
-#### Service Information
+Depending on the Admin version that the store account uses, the app will not be visible in the app list. To access it, go to [https://{{accountName}}.myvtex.com/admin/test-suite/payment-provider](https://{{accountName}}.myvtex.com/admin/test-suite/payment-provider), replacing {{accountName}} with the account name of your store.
 
-- __Service URL__: Set the URL for your service provider. This URL will be the protocol’s base address and must follow the format determined by it. For example, if the service URL is *https://10.10.10.10*, the full URL for the */payments* endpoint will be *https://10.10.10.10/payments*.
+Then, you will find a form with three sections: Service information, Payment method, and Test cases. Complete the fields following the instructions below.
 
-- __Connector Name__: Fill it in with the name you want to give your connector within VTEX. The name can only have lowercase letters, numerals and hyphens.
+#### Service information
 
-- __X-VTEX-API-AppKey__: Enter the value for the "PROVIDER-API-AppKey" on your provider's request header for testing.
+* **Service URL:** Define the URL of the service provider. This URL will be the base address for the protocol and must follow the format determined by it. For example, if the service URL is `https://example.com/`, the full URL for the /payments endpoint will be `https://example.com/payments`.
+* **AppKey and AppToken:** The Test with AppKey and AppToken button allows you to choose whether or not to configure the values of these fields, which can make testing easier during the development stage. If you do not enable this option, the credentials will be sent in the headers as an empty string.
 
-- __X-VTEX-API-AppToken__: Enter the value for the "PROVIDER-API-AppToken" on your provider's request header for testing.
-
-<div class="alert alert-warning">
-Your provider should expect the headers: <strong>X-VTEX-API-AppKey</strong> and <strong>X-VTEX-API-AppToken</strong>. This combination provides the credentials with which a retailer may be identified. The gateway stores the retailers' credentials as well as other parameters which are used to configure the affiliation and sends them to the provider during the transaction process.
+<div class="alert alert-info">
+<p>The gateway saves the store credentials configured in the affiliation and sends them in the X-VTEX-API-AppKey and X-VTEX-API-AppToken headers. The exceptions are integrations developed using VTEX IO, for which the headers will be sent as x-provider-api-appKey and x-provider-api-appToken. If you are developing using the <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework">Payment Provider Framework (IO)</a>, this is configured by the usesProviderHeadersName option. See the available settings <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework#available-configurable-options">here</a>.
+</p>
 </div>
 
-![Payment Provider Test Suite 0](https://images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
-
-#### Tests
+![Payment Provider Test Suite 0](//images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
 
-After reviewing all fields, click on the __CHECK URL__ button.
+#### Payment method
 
-The system will verify the payment methods through a call to your provider's __/manifest__ endpoint. See the API reference [here](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#get-/manifest).
+After completing the Service URL field, Test Suite will validate the[ Manifest endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#get-/manifest) and check the declared payment methods. They will be displayed as options in this field. Select the payment method you want to test.
 
-After the call, the endpoints of the available operations from your provider will be identified and the tests corresponding to each operation will be automatically enabled.
+#### Test cases
 
-You can select which tests you want to run, but for your integration to go through our team’s analysis, __all automatically enabled tests need to be performed__. Therefore, we recommend that all of them remain selected.
+In this section, you need to select the cases you want to test. If you are testing a credit card method, your integration must pass the Approved, Denied, Cancellation, Async Approved, and Async Denied cases. Only the Redirect flow is required for a payment method with [redirect](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows#redirect).
 
-![Payment Provider Test Suite 1](https://images.ctfassets.net/alneenqid6w5/5LROAprSeFd1O64M2WCisC/af4e2408feb2d1e5dfb9b9bac7067f6d/Payment_Provider_Test_Suite_1.jpg)
+![ppp-config-en](//images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/d49d66d80caa61f70720395a5dfca49b/image.png)
 
 ### 4. Testing
-When you click the __RUN TESTS__ button, the Payment Provider will apply the tests in your integration to the different possible scenarios. It's important to remember that to run them, your service must be in HTTPS. The tests are:
 
-- __Authorize__: This test is divided into three stages. At first, we send a _Create Payments_ request to `{{ServiceURL}}/payments`, waiting the _approved_ status as response. On the second, a _Settle Payment_ request is sent to `/payments/{PAYMENT_ID}/settlements` and we expect a response with _settleId_ filled in. Finally, we send a _Refund Payment_ request to `/payments/{PAYMENT_ID}/refunds`, waiting for a reply with _refundId_ filled in.
+When you click the `Run Test` button, Test Suite will call the provided service URL and run the selected test cases. The tests are:
 
-- __Denied__: In this test, we send a _Create Payments_ request to `{{ServiceURL}}/payments`, waiting for the _denied_ status to be answered.
+* **Approved flow:** This test is divided in three steps. First, we send a [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to `{{ServiceURL}}/payments`, expecting status approved as a response. Second, we send a [Settle Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/settlements) request to `{{ServiceURL}}/payments/{paymentId}/settlements`, expecting a response with settleId completed. And finally, we send a [Refund Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/refunds) request to `{{ServiceURL}}/payments/{paymentId}/refunds`, and expect a response with refundId completed.
+* **Denied flow:** In this test, we send a [Create Payment](https://developers.vtex.com/vtex-rest-api/reference/createpayment) request to `{{ServiceURL}}/payments`, expecting status denied as a response.
+* **Cancellation flow:** For this test, first, we need status approved as a response to the [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to `{{ServiceURL}}/payments`. Then, we send a [Cancel Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/cancellations) request to `{{ServiceURL}}/payments/{paymentId}/cancelations` and expect status canceled as a response.
+* **Async Approved flow:** This test is divided in two steps. First, we send a[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to {{ServiceURL}}/payments, expecting the status undefined as a response. After 15 seconds, we expect to receive another response in the same format via a POST with the URL sent in the callbackUrl field with status approved. When the integration is in production, this last call made by callbackUrl is authenticated using the partner’s environment keys: vtex-app-key and vtex-app-token. Learn more about the callback flow in the [Payment Authorization](#payment-authorization) section.
+* **Async Denied flow:** This test is also divided in two steps, as the previous one. First, we send a [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to {{ServiceURL}}/payments, expecting status undefined as a response. After 15 seconds, we expect to receive another response in the same format via a POST with the URL sent in the callbackUrl field and with status denied. When the integration is in production, this last call made by callbackUrl is authenticated using the partner’s environment keys: vtex-app-key and vtex-app-token. You can learn more about the callback flow in the [Payment Authorization](#payment-authorization) section.
+* **Boleto flow:** Boleto is a popular payment method in Brazil. In this test, we send a[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to {{ServiceURL}}/payments, expecting the status undefined as a response and the bankIssueUrl field containing the boleto ticket URL. After 15 seconds, we expect to receive another response in the same format via a POST with the URL sent in the callbackUrl field and with status approved. When the integration is in production, this last call made by callbackUrl is authenticated with the partner’s environment keys: vtex-app-key and vtex-app-token. Learn more about the callback flow in the [Payment Authorization](#payment-authorization) section.
+* **Redirect flow:** This test is divided in two steps. First, we send a [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to `{{ServiceURL}}/payments`, expecting the status undefined as a response and the redirectUrl field containing the URL that will be used to redirect the customer. After 15 seconds, we expect to receive another response in the same format via a POST with the URL sent in the callbackUrl field and with status approved. When the integration is in production, this last call made by callbackUrl is authenticated with the partner's environment keys: vtex-app-key and vtex-app-token. Learn more about the callback flow in the [Payment Authorization](#payment-authorization) section. Connectors that will use **Redirect** don’t need to pass all Test Suite tests, only the **Redirect** test.
 
-- __Cancel__: For this test, we first need the _approved_ status as response to the _Create Payments_ request for `{{ServiceURL}}/payments`. We then send a _Cancel Payment_ request to `/payments/{PAYMENT_ID}/cancellations` and expect a response with _cancelled_ status.
+<div class="alert alert-warning"><p>
+For credit cards, the mandatory tests are Authorize, Denied, Cancel, Async Approved, and Async Denied.
+</p></div>
 
-- __AsyncApproved__: This test is divided into two steps. At first, we send a _Create Payments_ request to `{{ServiceURL}}/payments`, waiting for the _undefined_ status to be answered. Then we expect to receive the same response within 15 seconds, but with _approved_ status on a POST in the URL sent in the _callbackUrl_ field. After the integration is in production, this last call made by callbackUrl is authenticated with the partner environment keys: _vtex-app-key_ and _vtex-app-token_.
+Use the following numbers to identify how to correctly respond to each credit card test:
 
-- __AsyncDenied__: Like the previous one, this test is divided into two steps. At first, we send a _Create Payments_ request to `{{ServiceURL}}/payments`, waiting for the _undefined_ status in the response. Then we expect to receive the same response within 15 seconds, but with _denied_ status on a POST in the URL sent in the _callbackUrl_ field. After the integration is in production, this last call made by callbackUrl is authenticated with the partner environment keys: _vtex-app-key_ and _vtex-app-token_.
-
-- __BankInvoice__: In this test, we send a _Create Payments_ request to `{{ServiceURL}}/payments`, waiting for the response to come with the _undefined_ status and the `bankIssueInvoiceUrl` field filled in with the ticket URL. Then we expect to receive the same response within 15 seconds, but with _approved_ status on a POST in the URL sent in the _callbackUrl_ field. When the integration is in production, this last call made by callbackUrl will be authenticated with the partner environment keys: _vtex-app-key_ and _vtex-app-token_.
-
-- __Redirect__: This test is divided into two steps. At first, we send a _Create Payments_ request to `{{ServiceURL}}/payments`, waiting for the response to come with the _undefined_ status and the `redirectUrl` field filled with the URL that will be used to redirect the client. Then we expect to receive the same response within 15 seconds, but with _approved_ status on a POST in the URL sent in the _callbackUrl_ field. When the integration is in production, this last call made by callbackUrl will be authenticated with the partner environment keys: _vtex-app-key_ and _vtex-app-token_. For the connector that will use Redirect, there is no need to pass all the Test Suit tests, only the Redirect one.
-
-<div class="alert alert-warning">
-In the case of credit cards, the required tests are: <strong>Authorize</strong>, <strong>Denied</strong>, <strong>Cancel</strong>, <strong>AsyncApproved</strong> and <strong>AsyncDenied</strong>.
-</div>
-
-<div class="alert alert-info">
-For each credit card test, we send a specific number to return the expected response. They are:<br>
-<strong>Response with status approved:</strong> card number 4444333322221111<br>
-<strong>Response with status denied:</strong> card number 4444333322221112<br>
-<strong>Response with status undefined and return in callbackUrl with status approved:</strong> card number 4222222222222224<br>
-<strong>Response with status undefined and return in callbackUrl with status denied:</strong> card number 4222222222222225<br>
-</div>
+| Card number      | Response status                             |
+| ---------------- | ------------------------------------------- |
+| 4444333322221111 | __approved__                                    |
+| 4444333322221112 | __denied__                                      |
+| 4222222222222224 | __undefined__, `callbackUrl` with status __approved__ |
+| 4222222222222225 | __undefined__, `callbackUrl` with status __denied__   |
 
 ### 5. Results
-After running the tests, the system returns the results, both positive and negative. The system also provides information on the expected results for each test. Thus, you have more visibility about what should be adjusted in case of error.
 
-![Payment Provider Test Suite 2](https://images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/38e5f5d1391d10ca831eba5682c5544b/Payment_Provider_Test_Suite_2.jpg)
+After running the tests, the system will display the Test Report, where you can see the detailed results of each test case. This way, you can have more visibility into what should be adjusted if an error occurs.
 
-To see in detail each action performed by the integration (and thus to identify possible errors), just click on the __TRY LOADING AGAIN?__ button. A list of the complete information about the events that happened during the test will be displayed below the results.
+![Payment Provider Test Suite 2_EN](//images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/ee1f759bf436aa38fff080f561ce4eb7/Payment_Provider_Test_Suite_2_EN.JPG)
 
-![Payment Provider Test Suite Logs](https://images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/12a0a237d1c8725b8eeb9bb61eb48fbc/Payment_Provider_Test_Suite_Logs.jpg)
+To see the messages exchanged between Test Suite and the payment provider implementation, click the Inspect Log button for the test case you want. A modal will open showing the message list and the payload of each request and response. The button in the upper right corner allows you to copy the code to the clipboard.
 
-![Payment Provider Test Suite 3](https://images.ctfassets.net/alneenqid6w5/7svc9sEJaMiwsYK0ykU0SS/590453ef17cda1dab3b1bb4342f1d9d1/Payment_Provider_Test_Suite_3.jpg)
-
-When your integration has successfully passed all tests, please open a ticket in our [VTEX support](/en/support "VTEX Help"). However, before opening the ticket, make sure you have the following information:
-
-- __Connector Name__: a description of the provider. Use max. 16 alphanumeric characters. This name can not be modified after being published.
-- __Partner contact__: partner email address in case we need to communicate changes and new features of our protocol.
-- __Production Service Provider Endpoint__: the base path that will be used for API calls to the provider, e.g., _https://vtex.pagseguro.com_. It has to respond to the route `{{serviceUrl}}/manifest`. This endpoint must be publicly available. 
-- __Sandbox Service Provider Endpoint__: the base path that will be used in test mode for API calls to the provider. E.g., _https://sandboxserviceproviderendpoint.com_. 
-- __Owner account__: the VTEX account name which will be used in callback requests. This account must be available at _{account}.myvtex.com_. 
-- __Allowed Accounts__: describe which VTEX accounts from this provider will be available (all accounts or specific accounts).
-- __New Payment methods__: inform if this connector supports a payment method that is not yet available in the VTEX Admin. 
-- __New Payment method purchase flow__: if a “New Payment method” is supported,  inform whether it works with Redirect or Payment App. For more information, access [Purchase Flows](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-purchase-flows).
-
-<div class="alert alert-warning">
-The SLA required for the payment team to carry out the homologation is 30 days. This term will start only after the submission of the document <b>Master Partner Agreement for Financial Services (MPA)</b>. For homologation requests without using the MPA, the SLA term may be extended due to the need for additional analysis by the payment team.
-</div>
+![Payment Provider Test Suite Logs_EN](//images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/87c2ba89961c5bf5a73532ea073b4083/Payment_Provider_Test_Suite_Logs_en.JPG)
 
 ## Payment protocol flow
 Here we explain the integrated payment stream in detail. The image below illustrates the entire flow, showing VTEX Payments and the responsibilities of your supplier.
 
 It all starts with requesting a new payment after the creation of a new order. VTEX creates a new payment representation and proceeds to the payments processing.
 
-![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+![fluxo-atualizado-ppp](//images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+
+<div class="alert alert-info">
+  The default period of 7 days for asynchronous payment retries is only applied when the user does not specify a value in the <code>delayToCancel</code> field of the <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> endpoint or when sending the callbackURL.</div>
 
 ### Payment Authorization
 
@@ -208,7 +188,7 @@ In any case, once the processing is completed and the provider has a final statu
 
 The complete flow with __undefined__ status and use of notification can be seen below:
 
-![Payment authorization callback notification flow](https://images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/a72be587d650da053ecbe220a5daa642/image1.png)
+![Payment authorization callback notification flow](//images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/a72be587d650da053ecbe220a5daa642/image1.png)
 
 1. The payment authorization is initiated when the gateway calls the Create Payment (__/payment__) endpoint for the provider. The `callbackUrl` field is submitted in the body of the request and contains the URL to send the notification.
 2. The payment occurs asynchronously (it does not generate the final status when the transaction is initiated). The gateway then receives the response with __undefined__ status and waits for the payment processing to be completed. Finally, once the processing is completed, the final status (__approved__ or __denied__) is updated.
@@ -217,7 +197,7 @@ The complete flow with __undefined__ status and use of notification can be seen
 
 The complete flow with __undefined__ status and use of __retry__ can be seen below:
 
-![Payment authorization callback retry flow](https://images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/3f43bcbf5d48a9c459b553ca6ad7b216/image2.png)
+![Payment authorization callback retry flow](//images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/3f43bcbf5d48a9c459b553ca6ad7b216/image2.png)
 
 1. The payment authorization is initiated when the gateway calls the Create Payment (__/payment__) endpoint for the provider. The `callbackUrl` field is submitted in the body of the request and contains the URL of the retry endpoint.
 2. The payment occurs asynchronously (it does not generate the final status when the transaction is initiated). The gateway then receives the response with __undefined__ status and waits for the payment processing to be completed. Finally, once the processing is completed, the final status (__approved__ or __denied__) is updated.
@@ -237,6 +217,20 @@ https://gatewayqa.vtexpayments.com.br/api/pvt/payment-provider/transactions/8FB0
 
 In the [Transactions page of the Admin](https://help.vtex.com/en/tutorial/how-to-view-the-orders-details--tutorials_452), the signature token appears masked for security reasons, as in this example: `X-VTEX-signature=Rj******tk`.
 
+See below an example of a payload forwarded along with the callback URL:
+
+```json
+{"paymentId":"8B3BA2F4352545A8B1C5A215F356A01C","status":"approved","authorizationId":"184520","nsu":"21705348","tid":"21705348","acquirer":"pagarme","code":"0000","message":"Transação aprovada com sucesso","delayToAutoSettle":1200, "delayToAutoSettleAfterAntifraud":1200, "delayToCancel":86400,"cardBrand":"Mastercard","firstDigits":"534696","lastDigits":"6921","maxValue":16.6}
+```
+
+<div class="alert alert-info">
+  The parameter values sent in the callback payload replace the original values informed in the <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> request.  
+</div>
+
+<div class="alert alert-warning">
+  If the waiting parameters (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) are not sent with the callback URL, these values will be automatically set to 24 hours.
+</div>
+
 When making the callback request, we recommend that payment providers use the callback URL exactly as received, which guarantees that all the parameters are included.
 
 When calling Callback URL, your provider should send in the request the *X-VTEX-API-AppKey* and *X-VTEX-API-AppToken* headers. Check more information about this in the [VTEX credentials section](/en/tutorial/payment-provider-protocol#vtex-credentials).
diff --git a/docs/tutorials/en/payments.md b/docs/tutorials/en/payments.md
new file mode 100644
index 000000000..3f491e760
--- /dev/null
+++ b/docs/tutorials/en/payments.md
@@ -0,0 +1,99 @@
+---
+title: 'Payments Data Pipeline (Beta)'
+id: 7LWkFaA1jPabzc5JAt1rGs
+status: PUBLISHED
+createdAt: 2024-02-02T17:53:35.949Z
+updatedAt: 2024-06-21T16:28:44.958Z
+publishedAt: 2024-06-21T16:28:44.958Z
+firstPublishedAt: 2024-05-27T19:26:59.478Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: payments
+locale: en
+legacySlug: payments
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+The payment dataset is composed of two main tables: `payments_transitions` and `transaction_transitions`.
+
+This section includes the following information:
+
+- [Characteristics of payment data](#data-characteristics)
+- [Table: payments_transitions](#table-payments_transitions)
+- [Table: transaction_transitions](#table-transaction_transitions)
+- [Analyses with payment data](#analyses-with-payment-data)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics
+
+|**Characteristic**|**Description**|
+| - | - |
+|**Data source**|The data in this set comes from the [VTEX Payments module](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB). It can be collected and organized to reflect the transactions and payments completed on the platform.|
+|**Availability**|Navigation data can only be accessed through the VTEX Admin.|
+|**History**|The data is retained for two years, from 2023 for clients who already use the VTEX platform. The data in the `transaction_interactions` table only has history since 07/05/24 (dd/mm/yy).|
+|**Minimum update interval**|One hour.|
+
+## Table: payments_transitions
+
+The `payments_transitions` table stores detailed information about payments, including the provider and the payment method used in each transaction. The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| :-: | - | - |
+|batch_id|character varying(13)|Control ID of the data ingestion batch.|
+|event_date_ti me|timestamp with time zone|Date and time of transition, including time zone information.|
+|account|character varying(128)|Account name, mapped to 'account_name' on VTEX License Manager.|
+|account_id|character varying(36)|Account identifier, mapped to 'id' on VTEX License Manager after removing hyphens.|
+|connector|character varying(1024)|Provider that processes the payment.|
+|delta_value|double precision|Time in milliseconds spent in the 'from_transition' transition.|
+|from_transiti on|character varying(64)|Payment status up to the date and time of the event.|
+|to_transition|character varying(64)|New transaction status after the date and time of the event.|
+|payment_id|character varying(32)|Unique payment identifier.|
+|payment_sys tem|character varying(1024)|Payment type, such as credit card, debit card, etc.|
+|transaction_i d|character varying(36)|Unique identifier of the transaction this payment belongs to.|
+|tid|character varying(1024)|External code received from the operator, representing an identification number for an ecommerce transaction.|
+|nsu|character varying(1024)|NSU (Número Sequencial Único) is a unique sequential number used in Brazil to identify a card sales transaction and is associated to each created invoice.|
+|currency_cod e|character varying(1024)|Currency code that is represented using three capital letters.|
+|value|integer|Payment amount multiplied by 100. For example, this amount will be 235 for a payment of $2.35.|
+
+## Table: transaction_transitions
+
+The `transaction_transitions` table stores the transactions from completed orders.
+Each transaction has a set of payments and changes the status based on a predefined flow. 
+
+The table fields are described below:
+
+|**Column name**|**Field type**|**Description**|
+| - | - | - |
+|batch_id|character varying(13)|Control ID of the data ingestion batch.|
+|event_date_tim e|timestamp with time zone|Date and time of transition, including time zone information.|
+|account|character varying(128)|Maps to an 'account_name' on VTEX License Manager.|
+|account_id|character varying(36)|Maps to an 'id' in the VTEX license management system after removing hyphens.|
+|delta_value|double precision|Time in milliseconds spent in the 'from_transition' transition.|
+|from_transition|character varying(64)|Transaction status up to the date and time of the event.|
+|to_transition|character varying(64)|New transaction status after the date and time of the event.|
+|transaction_id|character varying(36)|Unique identifier of the transaction.|
+
+## Analyses with payment data
+
+The payment dataset can be used for the following analyses:
+
+- **Payment processor efficiency analysis:** Evaluate the performance of different payment providers by analyzing the average time spent on each transition to identify the most efficient and reliable ones.  
+- **Monitoring payment status transitions:** Track changes in payment status over time to understand patterns and identify potential issues in the payment flow.  
+- **Transaction volume analysis by account:** Determine the volume of transactions processed by each account to get insights about the demand for payment services on different accounts.  
+- **Distribution of payment type:** Analyze the use distribution of different payment systems to assess customer preferences for different payment methods. 
+
+## Correlations with other data
+
+The payment data of the VTEX platform has correlations with other datasets which give more insight into the purchase cycle:  
+
+- **Interaction with [order](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) data:** Analyzing payment data alongside orders offers insights into how payment methods influence order conversions and reveal trends in customer purchasing behavior.    
+- **Financial and accounting analyses:** Integrating payment data with financial analyses contributes to more efficient cash flow management and enables more accurate financial forecasts, helping improve the company's financial health. 
+
+### Discover other datasets
+
+- [Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navigation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Orders](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Prices](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promotion](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)  
diff --git a/docs/tutorials/en/payu-romania-refund-details.md b/docs/tutorials/en/payu-romania-refund-details.md
index c9c63a1b9..3ad0c60d5 100644
--- a/docs/tutorials/en/payu-romania-refund-details.md
+++ b/docs/tutorials/en/payu-romania-refund-details.md
@@ -38,7 +38,7 @@ If the Delete button is not active and the timeout has not expired, you can quic
 
 If the void or refund request has already been sent by the system to the issuing bank, we will no longer be able to delete/stop it in any way.
 
-![PayU Romania](https://images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
+![PayU Romania](//images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
 
 Once PayU has sent the void or refund request to the issuing bank, the status of the order will be updated in the PayU cPanel as `REVERSE` (for voids) or `REFUND`. And VTEX is going to receive a webhook from PaymentsOS, so the order status can also be updated on the platform (on Payments and consequently reflected in the OMS).
 
diff --git a/docs/tutorials/en/pci-gateway-overview.md b/docs/tutorials/en/pci-gateway-overview.md
index 3081d97ad..8c820615b 100644
--- a/docs/tutorials/en/pci-gateway-overview.md
+++ b/docs/tutorials/en/pci-gateway-overview.md
@@ -19,7 +19,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 # Starting to use
 
-![new-admin-payments](https://images.ctfassets.net/alneenqid6w5/7w2PFtni9ykY0qGuasgU84/32d9c5341fb170a8b02abbea0ee3c628/NEW_ADMIN_PAGAMENTOS_EN.png)
+![new-admin-payments](//images.ctfassets.net/alneenqid6w5/7w2PFtni9ykY0qGuasgU84/32d9c5341fb170a8b02abbea0ee3c628/NEW_ADMIN_PAGAMENTOS_EN.png)
 
 Designed to provide maximum flexibility when it comes to payment configurations, VTEX Payments module processes transactions based on some business concepts. Understand each one:
 
diff --git a/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md b/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md
index 9282079e7..12667cc96 100644
--- a/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md
+++ b/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md
@@ -1,52 +1,154 @@
 ---
-title: 'Penetration testing and vulnerability notice'
+title: 'Penetration tests and vulnerability notifications'
 id: 6jodF6s1I50Fg84ZwutOCb
 status: PUBLISHED
 createdAt: 2022-11-30T14:20:37.453Z
-updatedAt: 2023-05-22T14:22:24.398Z
-publishedAt: 2023-05-22T14:22:24.398Z
+updatedAt: 2024-04-25T03:01:48.522Z
+publishedAt: 2024-04-25T03:01:48.522Z
 firstPublishedAt: 2022-11-30T14:42:44.449Z
 contentType: tutorial
 productTeam: Others
-author: 2Gy429C47ie3tL9XUEjeFL
+author: 1malnhMX0vPThsaJaZMYm2
 slug: penetration-testing-and-vulnerability-notice
 locale: en
 legacySlug: security-assessment-and-vulnerability-report
 subcategory: vONCJSxwN5qZiElOEtKkH
 ---
 
-VTEX rigorously evaluates platform resources, testing and identifying vulnerabilities through regular scans and penetration tests. These vulnerability checks are conducted periodically.
+<div class="alert alert-info">
+  <p>This feature is part of <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/br-pt/contato/">contact form</a>.</p>
+</div>
 
-If you want to conduct your own penetration test in your store environment, VTEX will evaluate your request and check the feasibility of running the test. Below, you will find the details for submitting a request.
+<div class="alert alert-warning">
+  <p>If you require an analysis of your penetration test report by a VTEX Security analyst, it is necessary to have VTEX Shield. Furthermore, all penetration tests must be previously <a href="#scheduling-penetration-tests">scheduled with VTEX</a>. Any test conducted autonomously without prior notice to VTEX will be considered an unauthorized action attempt.</p>
+</div>
 
-## Penetration tests
+VTEX rigorously evaluates platform features by testing and detecting vulnerabilities through recurring scanning and penetration testing. These vulnerability checks are performed periodically.
 
-To request and schedule a penetration test, follow these steps:
+In addition to the standard checks, stores using [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) can run a penetration test and report any vulnerabilities detected, as long as they schedule it with VTEX in advance.
 
-1. Open a ticket with [VTEX support](https://help.vtex.com/en/support) to request scheduling a penetration test.
-2. If the test is approved by VTEX, our team will ask the necessary details for scheduling the test and signing a confidentiality agreement. If you hire a third-party company to conduct the test, they also have to sign the confidentiality agreement.
-3. Update your ticket by attaching the confidentiality agreement and other information requested by VTEX.
-4. Save your ticket number. You will need it for future communication.
+Penetration tests, or pentests, are simulated attacks on a computer system, network, or web application to assess security, identify vulnerabilities, and fix them.  This test is run ethically to assess the system's security without causing real damage.
 
-After receiving your information, the VTEX team will contact you to confirm the penetration test.
+In this guide, we explain how to schedule a penetration test and report any potential vulnerabilities in the platform:
 
-## Vulnerability report
+- [Scheduling penetration tests](#scheduling-penetration-tests)
+   - [Penetration test reports](#penetration-test-reports)
+   - [Unauthorized procedures](#unauthorized-procedures)
+- [Reporting vulnerabilities](#reporting-vulnerabilities)
+   - [Vulnerability definition](#vulnerability-definition)
+   - [Reply from VTEX](#reply-from-vtex)
 
-After submitting the [request](#requesting-a-security-assessment) and performing your security assessment, if there are any findings, follow these steps:
+## Scheduling penetration tests
 
-1. Review and validate all assessment findings. You will need a security resource on your end, especially for an automated scan report.
-2. Write a report specifying the following information for each vulnerability found:
-    - Which URLs and functionality flows were affected.
-    - How the problem was detected.
-- What is the impact of this vulnerability on the target app if exploited, including what advantages an intruder could gain.
-    - The prioritization and ranking criteria used. Consider using a recognized framework or describe the methodology for ranking the criticality of the vulnerability.
-    - Describe the problem, detailing the procedure for replicating the failure. Include screenshots, if possible.
-- If you decide to include in the report a section reporting an attack, describe which vulnerabilities were exploited in it. In this case, include image evidence, video is optional.
-3. Open a ticket with [VTEX support](https://help.vtex.com/pt/support) and include the following information:
-- The ticket number of the [security assessment request](#requesting-a-security-assessment) corresponding to the test.
-- Vulnerability report generated as described in item 2.
+<div class="alert alert-warning">
+  <p>Only stores using <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a> can schedule a penetration test and are entitled to a reply from the Security team, with access to an in-depth test report analysis, as described in the procedures in this guide.</p>
+</div>
 
-## Confidentiality agreement
+To run a penetration test in your store's environment, you must align the test schedule with VTEX, for internal organization and planning by the Security team. Follow the instructions below:
 
-Here you can download the [confidentiality agreement regarding security testing](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+1. Open a ticket with [VTEX support](https://help.vtex.com/en/support) to inform that you want to schedule a penetration test.
+2. Our team will request the necessary information to schedule it. If you hire a third-party company to perform the test, they must also sign the [confidentiality agreement](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
 
+   VTEX recommends clients to run their penetration tests with partners whose teams have a minimum level of certification in the field and are aware of [unauthorized procedures](#unauthorized-procedures).
+
+   Companies with professionals certified in programs such as EC-Council's [Certified Ethical Hacker](https://www.eccouncil.org/train-certify/certified-ethical-hacker-ceh/), [CompTIA PenTest+](https://www.comptia.org/pt/certificacoes/pentest), and [GIAC Exploit Researcher and Advanced Penetration Tester](https://www.giac.org/certifications/exploit-researcher-advanced-penetration-tester-gxpn/) often provide more detailed and standardized reports, which improves both communication and the quality of the assessment.
+3. Update your ticket by attaching the [confidentiality agreement](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip) signed by the third-party company conducting the test, along with the information requested by VTEX.
+4. Save the ticket number. You will need it for future communications.
+5. After receiving the information, the VTEX team will contact you to confirm the penetration test within two business days.
+6. Run the test on the scheduled date, subject to authorization from VTEX.
+7. Send a report with the results in the same ticket to [VTEX Support](https://help.vtex.com/en/support).
+
+   <div class="alert alert-warning">
+  <p>You must follow the guidelines described in <a href="#penetration-test-reports">Penetration test reports</a> to meet the analysis deadline set by VTEX.</p>
+   </div>
+
+   Assign a person from your security team to be the point of contact for the VTEX Security team throughout the test report analysis.
+
+The VTEX Security team is committed to conducting a comprehensive analysis of all findings reported by the client from penetration tests previously authorized and scheduled by VTEX.
+
+Within 10 working days after receiving the [report](#penetration-test-reports), the team will identify false positives and reclassify the threat severity as necessary, following VTEX's best practices. Each decision in this process will include a detailed rationale to ensure full transparency and understanding.
+
+<div class="alert alert-warning">
+  <p>Stores planning their go-live and willing to run a penetration test must also schedule it in advance. In this case, they must send the report with the results to <a href="https://help.vtex.com/en/support">VTEX Support</a> at least <strong>45 days</strong> before the planned go-live date. During this period, VTEX will analyze the results and address any vulnerabilities identified. </p>
+</div>
+
+### Penetration test reports
+
+To ensure VTEX meets the 10-working-day deadline for analyzing the report, you must follow the guidelines below when creating the penetration test report:
+
+- **Details of what was affected**
+
+    Include information about where the problem was detected (URL, feature flow, etc.).
+- **Details of the impact on business**
+
+    Detail the effects of this security problem and the advantages it could provide to hackers.
+- **Details of the vulnerability classification criteria**
+
+    Use a structure or document that details the criteria for classifying the severity of the alleged vulnerability.
+- **Problem description**
+
+    Add images to illustrate the problem.
+- **Description of the steps to reproduce or proof of concept**
+
+    Describe the procedures for reproducing the security problem, preferably with images.
+- **Attack description** (optional)
+
+    If the report mentions an attack, describe the security problems used to trigger the attack, with images of evidence (videos are optional).
+
+### Unauthorized procedures
+
+We recommend using only authorized tests to identify vulnerabilities. The following procedures are prohibited:
+
+*	Running penetration tests without scheduling with VTEX.
+* Actions that may negatively impact VTEX, its products, or its users.For example: spam, brute force, denial-of-service, and other actions stated in [the confidentiality agreement regarding security tests](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+* Accessing or trying to access data or information that does not belong to your account.
+* Destroying or attempting to corrupt data or information belonging to VTEX.
+* Any type of physical or electronic attack on VTEX personnel or property.
+* Social engineering techniques.
+* Breaking any laws and regulations or breaching any agreement to detect vulnerabilities.
+
+## Reporting vulnerabilities
+
+We encourage our clients to responsibly report any security vulnerabilities they believe they found during authorized tests.
+
+If you wish to report a vulnerability, you should first work with your security and development teams to conduct a security assessment and eliminate false positives or issues arising from custom configurations. Only cases compatible with the [definition of vulnerability](#vulnerability-definition) will be analyzed.
+
+<div class="alert alert-warning">
+  <p>Please review the<a href="https://vtex.com/us-en/security/security-practices/"> VTEX Security Practices</a> document and our<a href="https://help.vtex.com/en/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX#risk-assessment-at-vtex"> Security FAQ</a> before reporting any vulnerabilities. These documents clarify our processes and help eliminate false positives.</p>
+</div>
+
+After this, follow the steps below to report if there is a vulnerability:
+
+1. Download the vulnerability notification [template](https://assets.ctfassets.net/alneenqid6w5/7FNzoEpl67wH6crmW98If2/fdab37d3a7a49778abfaca7ca7531fe8/Modelo__Comunica____o_de_Vulnerabilidade_-_EN_v2.pdf).
+2. Complete the vulnerability notification template with detailed information about each vulnerability detected. Add as many details as possible about the vulnerabilities you found to explain the identified suspicion, providing proof and images to help us understand, reproduce, and validate the issue.
+
+   Vulnerabilities must be reported individually, following the template. If you encountered more than one vulnerability in your test, please complete multiple templates and attach them to your ticket.
+
+  <div class="alert alert-warning">
+    <p>All information must be provided and is essential for the assessment. The VTEX Security team will not address vulnerability notifications that do not follow the established template.</p>
+  </div>
+
+3. Open a ticket with our [Support](https://help.vtex.com/en/support) to submit the security vulnerability notification. Do not forget to attach the completed vulnerability notification template in the ticket.
+4. Save your ticket number, as you may need it in future communications.
+
+### Vulnerability definition
+
+VTEX considers a security vulnerability to be any flaw in our components that could allow the confidentiality, integrity, or availability of products or infrastructure to be compromised in any way.
+
+We do not consider as a vulnerability:
+
+* Presence or absence of HTTP headers (X-Frame-Options, CSP, nosniff, among others).
+* Lack of security attributes in cookies.
+* Cache-related issues.
+* Stack error messages.
+* Content injection by admin users.
+* Customized store sections.
+* Autocomplete enabled.
+
+### Reply from VTEX
+
+VTEX makes no commitment to reply to bulk reports generated by automated scanners. If your analysis is based on an automated vulnerability identification process, we recommend having a security professional review the reports to ensure the accuracy of the findings before reporting the vulnerabilities to VTEX.
+
+VTEX is committed to responding to notifications received by [Support](https://help.vtex.com/en/support) as soon as possible to inform about vulnerability fixes or to provide clear reasons that prevent pursuing further analysis or fixes.
+
+VTEX is dedicated to analyzing, verifying, and fixing any vulnerabilities reported to us that may threaten your security.
diff --git a/docs/tutorials/en/permissions-management-in-b2b-suite.md b/docs/tutorials/en/permissions-management-in-b2b-suite.md
new file mode 100644
index 000000000..72ac8b27e
--- /dev/null
+++ b/docs/tutorials/en/permissions-management-in-b2b-suite.md
@@ -0,0 +1,68 @@
+---
+title: 'Permissions management in B2B Suite'
+id: 2PLR7mIFxgbmsGq84paLeA
+status: PUBLISHED
+createdAt: 2024-06-05T18:01:03.375Z
+updatedAt: 2024-06-07T13:37:21.121Z
+publishedAt: 2024-06-07T13:37:21.121Z
+firstPublishedAt: 2024-06-06T10:57:21.290Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: permissions-management-in-b2b-suite
+locale: en
+legacySlug: permissions-management-in-b2b-suite
+subcategory: 1qGLxbxcX8kwKSWESbLZca
+---
+
+In an organization, the Organization Admin (main user) manages access for different people in a B2B store. To do this, they use the permission system in B2B Suite.
+
+Through this app, you can do the following:
+
+- **Initial configuration:** The admin creates the predefined roles and assigns their permissions.
+
+- **Associate roles and permissions:** Predefined roles are associated with different functions and responsibilities within the organization, each with specific permissions.
+
+- **Sync automatic information:** The app automatically communicates with other B2B Suite apps, such as [B2B Organizations](https://developers.vtex.com/docs/apps/vtex.b2b-organizations), to enable different organization management capabilities based on each user role.
+
+- **Check permissions:** When a user performs an action in the store, such as placing an order or accessing certain features, the app checks if the user has the necessary permissions based on their assigned role.
+
+- **Manage permissions:** The app operates backstage and stores predefined roles.
+
+## Roles and permissions
+
+The Storefront Permissions app allows that within an organization, each user can have different roles. For example, a buyer who places orders with budget limits from a predefined cost center or a manager in charge of reviewing and approving orders. These roles can be associated with multiple permissions, depending on the actions the user needs to perform.
+
+## Roles
+
+The following table shows the roles available, along with their keys and descriptions.
+
+| Rol                   | Clave                | Descripción                                                                                                                           |
+|-----------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Role                  | Key                  | Description                                                                                                                           |
+| Store Admin           | store-admin          | User who accesses the VTEX Admin and manages the store.                                                                               |
+| Sales Admin           | sales-admin          | User who can manage all sales users.                                                                                                  |
+| Sales Manager         | sales-manager        | User who can manage sales users in the same organization, assist buyers, and simulate purchases in a store.                           |
+| Sales Representative  | sales-representative | User who can assist or simulate purchases in a store.                                                                                 |
+| Organization Admin    | customer-admin       | Main user of the organization who manages the company's information, as well as its members and cost centers.                         |
+| Organization Approver | customer-approver    | User who can retrieve a cart or quote previously saved by an Organization Buyer and create a new order.                               |
+| Organization Buyer    | customer-buyer       | User who can add items to the cart. If the [B2B Quotes](https://developers.vtex.com/docs/apps/vtex.b2b-quotes) app is installed, they can also save the cart for future use or create a quote. |
+
+## Configuring role management
+
+To manage roles and permissions, configure permissions by following the steps below on the Storefront Permissions page.
+
+1. In the VTEX Admin, go to Apps > Installed Apps > Storefront Permissions, or type Storefront Permissions in the search bar at the top of the page.
+Click a role available in the store.
+
+2. Click a role available in the store.
+
+3. Click one of the listed apps.
+
+4. Select the permissions you want to enable for the role.
+
+5. Click `Save`.
+
+![Gerenciamento de permissões - EN](//images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/8cab9bcae960a2f30d855789b065a0ee/Gerenciamento_de_permiss_es_-_EN.gif)
+
+Once you have associated the roles with the desired permissions, you can assign them to users. Learn more in [B2B Organizations](https://developers.vtex.com/docs/guides/vtex-b2b-organizations#users).
diff --git a/docs/tutorials/en/physical-store-instore-beta.md b/docs/tutorials/en/physical-store-instore-beta.md
index 224622d5c..2047b0ec1 100644
--- a/docs/tutorials/en/physical-store-instore-beta.md
+++ b/docs/tutorials/en/physical-store-instore-beta.md
@@ -28,7 +28,7 @@ This page allows you to perform the following actions:
 * [Edit](#editing-a-store)
 * [Delete](#editing-a-store)
 
-![loja-fisica-EN](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
+![loja-fisica-EN](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
 
 The page displays the following information: 
 
@@ -53,7 +53,7 @@ You can add a physical store by following the steps below:
 
 ### Physical store fields
 
-![loja-fisica2-en](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
+![loja-fisica2-en](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
 
 #### Identification
 
diff --git a/docs/tutorials/en/pickup-points-for-subscription-orders.md b/docs/tutorials/en/pickup-points-for-subscription-orders.md
new file mode 100644
index 000000000..91f074ac0
--- /dev/null
+++ b/docs/tutorials/en/pickup-points-for-subscription-orders.md
@@ -0,0 +1,54 @@
+---
+title: 'Pickup points for subscription orders'
+id: csIqB6iBh4QNIFdEj0nVv
+status: PUBLISHED
+createdAt: 2021-05-17T12:45:21.450Z
+updatedAt: 2023-11-16T15:59:51.093Z
+publishedAt: 2023-11-16T15:59:51.093Z
+firstPublishedAt: 2021-05-17T20:55:05.477Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 1malnhMX0vPThsaJaZMYm2
+slug: pickup-points-for-subscription-orders
+locale: en
+legacySlug: pickup-points-for-subscription-orders-beta
+subcategory: 1rA9wuuskW3PpjvMrhatAM
+---
+
+A pickup point is a physical location where customers can pick up their orders, instead of having them delivered to their homes. A common usage scenario for this feature is the in-store pickup, for example.
+
+In addition to regular orders, you can provide pickup points for subscription orders if you use the [Subscriptions module](https://help.vtex.com/en/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj).
+
+Check out how to enable this feature:
+
+- [Requirements](#requirements)
+- [Choosing pickup points](#choosing-pickup-points)
+
+<div class="alert alert-info">
+  <p>The pickup points feature is available only for accounts using the <a href="https://help.vtex.com/en/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH">Checkout V6</a>.</p>
+</div>
+
+## Requirements
+
+To offer pickup points for subscription orders, you must fulfill the logistical requirements listed below.
+
+*    You must have the [Subscriptions module](https://help.vtex.com/en/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj) installed and the pickup points option enabled. To do that, please contact [our Support](https://support.vtex.com/hc/pt-br/requests).
+*    You need to configure pickup points for your store. You can only use pickup points from the main store or franchises (white label sellers) for subscription orders. Learn how to configure pickup points in our article [Adding pickup points](https://help.vtex.com/en/tutorial/adding-pickup-points--2R5ClQiwe4KoSQgsuiOw4E).
+*    Carriers associated with pickup points for subscription orders **cannot** have any [delivery windows](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) configured.
+*   Make sure that you have the items in stock at the subscription cycle date (the moment when recurring orders are created).
+
+## Choosing pickup points
+
+Customers can choose pickup points for items in a subscription order at checkout, as illustrated in the image below.
+
+![subscriptionspickup EN](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
+
+You can also assign pickup points when [creating new subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#post_api-rns-pub-subscriptions) via the [Subscriptions API](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1). For existing subscriptions, you can change the delivery address by using the [API subscription upgrade route](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#patch_api-rns-pub-subscriptions-id) to start using a pickup point.
+
+To find out available pickup points near specific ZIP codes or geographic coordinates, you can use the [Checkout API](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview).
+
+## Related articles
+
+- [How to configure subscriptions in your store](https://help.vtex.com/en/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj)
+- [Adding pickup points](https://help.vtex.com/en/tutorial/configurar-pontos-de-retirada-pickup-points--2R5ClQiwe4KoSQgsuiOw4E)
+- [Setting up a white label seller as a pickup point](https://help.vtex.com/en/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e)
diff --git a/docs/tutorials/en/pickup-points.md b/docs/tutorials/en/pickup-points.md
index 890a61b72..e1adf41c4 100644
--- a/docs/tutorials/en/pickup-points.md
+++ b/docs/tutorials/en/pickup-points.md
@@ -3,8 +3,8 @@ title: 'Pickup points'
 id: 2fljn6wLjn8M4lJHA6HP3R
 status: PUBLISHED
 createdAt: 2020-07-01T19:16:21.675Z
-updatedAt: 2023-03-29T19:48:10.418Z
-publishedAt: 2023-03-29T19:48:10.418Z
+updatedAt: 2023-07-25T16:53:09.640Z
+publishedAt: 2023-07-25T16:53:09.640Z
 firstPublishedAt: 2020-07-01T19:25:40.136Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -72,7 +72,7 @@ VTEX considers the pickup point to be a shipping method, and therefore the setti
     - Step 2: On the **Shipping Policies** tab, select the shipping policy created for the pickup point.
     - Step 3: In the **Actions** column, click on the <i class="fas fa-pen"></i> icon for editing.
     - Step 4: Enable the <i class="fas fa-toggle-on"></i> of the **Link pickup points** field.
-    - Step 5: Select the pickup point from the available fields. ![relacionarpontosretiradaEN](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/6df4f0848577031ee8dcab4898061a62/relacionarpontosretiradaEN.png)<div class = "alert alert-info">For stores that have more than 50 pick points, we recommend using the Pickup Point Tags field when creating a pick point. Using tags makes it easier to find the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140#adding-a-shipping-policy">pickup points when linking them to the shipping policy.</a> Also remember that the shipping policy that is linked to a pickup point will not be available for any other shipping method. We recommend creating a shipping policy that is exclusive to the pickup point.</div>
+    - Step 5: Select the pickup point from the available fields. ![relacionarpontosretiradaEN](//images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/6df4f0848577031ee8dcab4898061a62/relacionarpontosretiradaEN.png)<div class = "alert alert-info">For stores that have more than 50 pick points, we recommend using the Pickup Point Tags field when creating a pick point. Using tags makes it easier to find the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140#adding-a-shipping-policy">pickup points when linking them to the shipping policy.</a> Also remember that the shipping policy that is linked to a pickup point will not be available for any other shipping method. We recommend creating a shipping policy that is exclusive to the pickup point.</div>
 
 4. [Registering geolocation](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): for greater accuracy of the location of the pickup points at the checkout.<div class = "alert alert-info">Viewing pickup points with map and time at checkout is only available for Checkout V6.</div>
 
@@ -80,8 +80,8 @@ VTEX considers the pickup point to be a shipping method, and therefore the setti
     - Step 1: In the VTEX Admin, go to **Store settings > Storefront > Checkout**, or type *Checkout* in the search bar at the top of the page.  
     - Step 2: Select the configuration used in the store and click the <i class="fas fa-cog"></i> icon.
     - Step 3: Click the **Checkout** tab in the top bar.
-    - Step 4: Select the <i class="fas fa-toggle-on"></i> from the **Invoice address in pickup**.![NFpontoretiradaEN](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/a221ea377c5b7629eba243f55cf80058/NFpontoretiradaEN.png)<div class="alert alert-warning">The option of <b>Invoice address in pickup</b> must be enabled in all stores in Brazil, as it is a requirement that the invoice issued contains the customer's address information, even if the option to delivery of the order is at the pick-up point. The address filled in by the customer will be recorded in the `invoiceData` field of the <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - Step 4: Select the <i class="fas fa-toggle-on"></i> from the **Invoice address in pickup**.![NFpontoretiradaEN](//images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/a221ea377c5b7629eba243f55cf80058/NFpontoretiradaEN.png)<div class="alert alert-warning">The option of <b>Invoice address in pickup</b> must be enabled in all stores in Brazil, as it is a requirement that the invoice issued contains the customer's address information, even if the option to delivery of the order is at the pick-up point. The address filled in by the customer will be recorded in the `invoiceData` field of the <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
 
 6. Set the amount of pickup points that are displayed at checkout:
     - Step 1: In the VTEX Admin, go to **Store settings > Shipping > Settings**, or type *Shipping* in the search bar at the top of the page and select *Store settings / Shipping*.    
-    - Step 2: Change the **Pickup points configuration** field: use the <i class="far fa-caret-square-up"></i> and <i class="far fa-caret-square-down"></i> buttons and select the first pickup points that will become available in the search list (displayed at checkout).
+    - Step 2: Change the **Pickup points configuration** field: use the <i class="far fa-caret-square-up"></i> and <i class="far fa-caret-square-down"></i> buttons and select the quantity of pickup points that will become available in the search list (displayed at checkout).
diff --git a/docs/tutorials/en/plan-your-project.md b/docs/tutorials/en/plan-your-project.md
index 375f9b700..612edc6b9 100644
--- a/docs/tutorials/en/plan-your-project.md
+++ b/docs/tutorials/en/plan-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Plan your Project'
 id: tutorials_2546
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:54:42.370Z
-updatedAt: 2019-12-31T15:20:45.999Z
-publishedAt: 2019-12-31T15:20:45.999Z
+updatedAt: 2024-03-11T13:20:06.594Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:51.704Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/planner-calendar-page-beta.md b/docs/tutorials/en/planner-calendar-page-beta.md
index 3c32dbdd5..a3a55b0aa 100644
--- a/docs/tutorials/en/planner-calendar-page-beta.md
+++ b/docs/tutorials/en/planner-calendar-page-beta.md
@@ -40,7 +40,7 @@ You can view the **Calendar** page in three ways:
 
 In the following image, you will see the view per month and what you can do in the interface:
 
-![releases-calendar-monthly-view-en](https://images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6dc0c1f3eef1fa4aef0bbd7a6f462f63/releases-calendar-monthly-view-en.png)
+![releases-calendar-monthly-view-en](//images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6dc0c1f3eef1fa4aef0bbd7a6f462f63/releases-calendar-monthly-view-en.png)
 
 In this page, you can:
 
@@ -58,7 +58,7 @@ In this page, you can:
 
 In the following image, you'll see the view per week and what you can do in the interface:
 
-![releases-calendar-weekly-view-en](https://images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/a968361f0e0d1f0eece420ff190c1a94/releases-calendar-weekly-view-en.png)
+![releases-calendar-weekly-view-en](//images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/a968361f0e0d1f0eece420ff190c1a94/releases-calendar-weekly-view-en.png)
 
 In this page, you can:
 
@@ -76,7 +76,7 @@ In this page, you can:
 
 In the following image, you'll see the view per day and what you can do in the interface:
 
-![daily view v2 en](https://images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/b41cc39641404cceacfee3fb47d35615/daily_view_v2_en.png)
+![daily view v2 en](//images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/b41cc39641404cceacfee3fb47d35615/daily_view_v2_en.png)
 
 Apart from viewing information about the release, in this page, you can:
 
diff --git a/docs/tutorials/en/planner-releases-page-beta.md b/docs/tutorials/en/planner-releases-page-beta.md
index cf3c530f4..96b5a19a8 100644
--- a/docs/tutorials/en/planner-releases-page-beta.md
+++ b/docs/tutorials/en/planner-releases-page-beta.md
@@ -35,7 +35,7 @@ The order of the scheduled releases is based on the publication date: The furthe
 
 Go to the **Releases** navigation menu to access the **Releases** page in the VTEX Admin. In the following image, you'll see the interface and what you can do in it:
 
-![Releases list view v2 - EN](https://images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/431af585bfbfef7f3920e38aca9aab6b/Releases_list_view_v2_-_EN.png)
+![Releases list view v2 - EN](//images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/431af585bfbfef7f3920e38aca9aab6b/Releases_list_view_v2_-_EN.png)
 
 | **Field** | **Description** |
 |---|---|
diff --git a/docs/tutorials/en/predefined-roles.md b/docs/tutorials/en/predefined-roles.md
index c207c245e..a25c5e7a5 100644
--- a/docs/tutorials/en/predefined-roles.md
+++ b/docs/tutorials/en/predefined-roles.md
@@ -3,8 +3,8 @@ title: 'Predefined roles'
 id: jGDurZKJHvHJS13LnO7Dy
 status: PUBLISHED
 createdAt: 2022-04-07T21:34:06.385Z
-updatedAt: 2023-06-06T21:37:23.798Z
-publishedAt: 2023-06-06T21:37:23.798Z
+updatedAt: 2024-05-22T17:50:31.567Z
+publishedAt: 2024-05-22T17:50:31.567Z
 firstPublishedAt: 2022-04-07T21:48:28.951Z
 contentType: tutorial
 productTeam: Identity
@@ -15,14 +15,20 @@ legacySlug:
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-In this document we  list the predefined [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#) for new VTEX stores. To access them directly, use the list below:
+[Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#) group [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#), with each resource representing a permission in the VTEX platform.
+
+In this document, are listed the roles that are predefined for new VTEX stores and their respective resources. To access them directly, use the list below.
+
+<div class="alert alert-info">
+<p>Learn more about each resource listed in the roles below in <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">License Manager Resources</a>.</p>
+</div>
 
 * [Admin - Start page only](#admin-start-page-only)
 * [Checkout Admin](#checkout-admin)
 * [Call center operator](#call-center-operator)
 * [Finance](#finance)
 * [Finance - Full access](#finance-full-access)
-* [inStore Sales Person](#instore-sales-person)
+* [Sales App - Sales Associate](#sales-app-sales-associate)
 * [IntegrationProfile - Fulfillment](#integrationprofile-fulfillment)
 * [IntegrationProfile - Fulfillment Gateway](#integrationprofile-fulfillment-gateway)
 * [IntegrationProfile - Fulfillment Gateway GetOrder](#integrationprofile-fulfillment-gateway-getorder)
@@ -44,1143 +50,288 @@ In this document we  list the predefined [roles](https://help.vtex.com/en/tutori
 
 This is the basic role that grants access to the home page of the administrative environment. It is the minimum required for a user not to be received with an error message when logging into the administrative environment.
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Home page</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Help home page</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Homepage | Catalog | Administration | Home page |
+| Help page | Catalog | Administration | Help home page |
 
 ## Checkout Admin
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Shopping Cart Full Access</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Full Access</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td>Access all orders</td>
-  </tr>
-  <tr>
-    <td>Order Cancelation</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td></td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Shopping Cart Full Access | Checkout | CheckoutResources |
+| Orders Full Access | Checkout | CheckoutResources | Access all orders |
+| Order Cancelation | Checkout | CheckoutResources |
 
 ## Call center operator
 
-This role includes special resources. The **Assisted Sales** resource causes the user to be automatically redirected to the store, which will leave the user who logs in to an account with this role without access to important resources in the administrative menu. We recommend using two accounts for telesales users - a separate account for the **Call center operator** role and one for other operations that the user may need to perform in the administrative menu.
+This is a role dedicated to telesales operators, as it grants access to VTEX's [telesales features](https://help.vtex.com/en/tutorial/telesales-features--UqhiccIRIK2KD0OqkzJaS) and allows you to view orders.
+
+The Assisted Sales resource causes the user to be automatically redirected to the store's telesales page, which will leave the user logging into an account with this role without access to important features of the administrative menu.
+
+We therefore recommend using two separate accounts (with different emails) for telesales users: one account for the __Call center operator__ role (with the *Assisted Sales* and *View order* resources) and another account for carrying out operations in Admin, if necessary.
 
 <div class="alert alert-warning">
-When creating a  <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">role</a>, avoid including call center <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">resources</a> with other resources. Otherwise, the role might not work as expected.
+When creating a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">role</a>, avoid including call center <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">resources</a> with other resources. Otherwise, the role might not work as expected.
 </div>
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Assisted Sales</td>
-    <td>Catalog</td>
-    <td>Telesales</td>
-    <td>After logging in, the user will be redirected to the telesales website www.yourstore.com/a/telesales. In this way, the operator can carry out operations in the store on the customer’s behalf. A bar will be displayed at the top of the screen.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view orders in OMS.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Assisted Sales | Catalog | Telesales | Telesales features. After the login, the user is redirected to the telesales site www.{storename}.com.br/a/telesales. This way, the operator can use telesales features such as navigating the store in the name of the customer.As this feature causes an automatic redirect to the store, the user who logs in an account with this resource in their role will not have access to important resources from Admin. |
+| View order | OMS | AcessoOMS | Allows users to view orders in OMS. |
 
 ## Finance  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>UI - Account list</td>
-    <td>License Manager</td>
-    <td>Web Access Control</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-  <tr>
-    <td>Invoices List</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Customers, billing and finance managers have access. Allows users to view invoices.</td>
-  </tr>
-  <tr>
-    <td>Edit Company Information</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows users to edit Company data.</td>
-  </tr>
-  <tr>
-    <td>Contracts List</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Customers, billing and finance managers have access. Allows users to view all contracts (active and inactive) for a company.</td>
-  </tr>
-  <tr>
-    <td>Display Company info</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Customers, billing and finance managers have access. Allows users to view Company data.</td>
-  </tr>
-  <tr>
-    <td>Contacts List</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Customers, billing and finance managers have access. Allows users to view the list of Contacts that receive email notifications when charges are incurred.</td>
-  </tr>
-  <tr>
-    <td>Edit Contacts</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Only billing and finance managers have access. Allows users to edit contacts that receive notifications when charges are incurred.</td>
-  </tr>
-  <tr>
-    <td>Generate new Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Finance managers can manually incur charges in the invoice through contracts.</td>
-  </tr>
-  <tr>
-    <td>Recalc Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Incur new charge with interest.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| UI - Account list | License Manager | Web Access Control |
+| View order | OMS | AcessoOMS | Allows users to view orders in OMS. |
+| View store sales stats | OMS | AcessoOMS | Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details. |
+| Invoices List | Billing | Invoice | Customers, billing and finance managers have access. Allows users to view invoices. |
+| Edit Company Information | Billing | Company | Only billing and finance managers have access. Allows users to edit Company data. |
+| Contracts List | Billing | Contracts | Customers, billing and finance managers have access. Allows users to view all contracts (active and inactive) for a company. |
+| Display Company info | Billing | Company | Customers, billing and finance managers have access. Allows users to view Company data. |
+| Contacts List | Billing | Contacts | Customers, billing and finance managers have access. Allows users to view the list of Contacts that receive email notifications when charges are incurred. |
+| Edit Contacts | Billing | Contacts | Only billing and finance managers have access. Allows users to edit contacts that receive notifications when charges are incurred. |
+| Generate new Invoice | Billing | Invoice | Only billing and finance managers have access. Finance managers can manually incur charges in the invoice through contracts. |
+| Recalc Invoice | Billing | Invoice | Only billing and finance managers have access. Incur new charge with interest. |
 
 ## Finance - Full access  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Save account</td>
-    <td>License Manager</td>
-    <td>Service Access Control</td>
-    <td>Save an account</td>
-  </tr>
-  <tr>
-    <td>Get account by identifier</td>
-    <td>License Manager</td>
-    <td>Service Access Control</td>
-    <td>Query that returns account by identifier, which can be the account id or the account application host.</td>
-  </tr>
-  <tr>
-    <td>UI - Account list</td>
-    <td>License Manager</td>
-    <td>Web Access Control</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>UI - Edit account</td>
-    <td>License Manager</td>
-    <td>Web Access Control</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>UI - Edit role</td>
-    <td>License Manager</td>
-    <td>Web Access Control</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-  <tr>
-    <td>Invoices List</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Customers, billing and finance managers have access. Allows users to view invoices.</td>
-  </tr>
-  <tr>
-    <td>Edit Company Information</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows users to edit Company data.</td>
-  </tr>
-  <tr>
-    <td>Contracts List</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Customers, billing and finance managers have access. Allows users to view all contracts (active and inactive) for a company.</td>
-  </tr>
-  <tr>
-    <td>Display Company info</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Customers, billing and finance managers have access. Allows users to view Company data.</td>
-  </tr>
-  <tr>
-    <td>Contacts List</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Customers, billing and finance managers have access. Allows users to view the list of Contacts that receive email notifications when charges are incurred.</td>
-  </tr>
-  <tr>
-    <td>Edit Contacts</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Only billing and finance managers have access. Allows users to edit contacts that receive notifications when charges are incurred.</td>
-  </tr>
-  <tr>
-    <td>Generate new Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Finance managers can manually incur charges in the invoice through contracts.</td>
-  </tr>
-  <tr>
-    <td>Edit Company's Document</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows users to edit the Company's document data (company registration number or individual taxpayer registration number), with which the invoice will be generated.</td>
-  </tr>
-  <tr>
-    <td>Add Account</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows users to add an account to group other accounts linked to that customer into one billing.</td>
-  </tr>
-  <tr>
-    <td>Delete Account</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows users to delete an account associated with a company. Company is the entity created to encompass several accounts from the same store.</td>
-  </tr>
-  <tr>
-    <td>Save contracts</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Only billing, sales operations/growth and finance managers have access. Allows users to create new contracts.</td>
-  </tr>
-  <tr>
-    <td>Cancel Invoice Document</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Cancel fiscal document in municipal administrations; gives the power to cancel a fiscal document even if the invoice has already been generated.</td>
-  </tr>
-  <tr>
-    <td>Issue Invoice Document</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Used in specific cases of countries that do not generate fiscal documents automatically, depending on their financial system. In this case, they can be generated manually.</td>
-  </tr>
-  <tr>
-    <td>Conciliate Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. The default is to automatically mark it as paid, but the customer can pay it outside the system, depending on the negotiation. In this case, the finance manager has the power to manually mark it as paid, conciliating the invoices.</td>
-  </tr>
-  <tr>
-    <td>Generate Invoice Overdue without Interest</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Incur new charge with interest.</td>
-  </tr>
-  <tr>
-    <td>Cancel Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Cancel charges in billing; gives the power to cancel invoices even if they have already been generated.</td>
-  </tr>
-  <tr>
-    <td>Change payment status</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. The finance manager has the power to change a company’s payment status, depending on his negotiation with the client.</td>
-  </tr>
-  <tr>
-    <td>Recalc Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. Incur new charge with interest.</td>
-  </tr>
-  <tr>
-    <td>Get Unscrewed Dashboard Charges</td>
-    <td>Billing</td>
-    <td>Dashboard</td>
-    <td>Only billing and finance managers have access. Access to a dashboard external to Admin, which displays invoices issued at that time, and which accounts are provisioned.</td>
-  </tr>
-  <tr>
-    <td>Merge companies</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows the merger between two companies, unifying their billing.</td>
-  </tr>
-  <tr>
-    <td>Split companies</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Only billing and finance managers have access. Allows to split a company into different companies.</td>
-  </tr>
-  <tr>
-    <td>Unpaid invoices</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Only billing and finance managers have access. The finance manager can manually deselect the payment of a charge if it has not been made or if it has been made incorrectly.</td>
-  </tr>
-  <tr>
-    <td>Get App</td>
-    <td>Log</td>
-    <td>Log Admin</td>
-    <td>VTEX internal use.</td>
-  </tr>
-  <tr>
-    <td>Create Table</td>
-    <td>Log</td>
-    <td>Log Admin</td>
-    <td>VTEX internal use.</td>
-  </tr>
-</table>
-
-## inStore Sales Person  
-
-&nbsp;&nbsp;&nbsp;&nbsp; Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Product Form</td>
-    <td>Catalog</td>
-    <td>Content</td>
-    <td>Access to product screen</td>
-  </tr>
-  <tr>
-    <td>Store Texts</td>
-    <td>Catalog</td>
-    <td>Settings</td>
-    <td>Developer tool with all the store’s basic texts</td>
-  </tr>
-  <tr>
-    <td>Assisted Sales</td>
-    <td>Catalog</td>
-    <td>Telesales</td>
-    <td>After logging in, the user is redirected to the store (accountname.myvtex.com)</td>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Home page</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Help home page</td>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recovers a transaction.</td>
-  </tr>
-  <tr>
-    <td>Manage Store</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ManageStore</td>
-    <td>Allows users to modify configuration settings</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to access actions within the workflow to change order status, through the Actions button in the Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Access to the button that manually notifies payments to the gateway in the payment area within the order.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to manually inform invoices and data for tracking in OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to cancel orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Full access to all documents</td>
-    <td>Dynamic Storage</td>
-    <td>Generic resources for Dynamic Storage</td>
-    <td>Resource automatically registered by Dynamic Storage.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Save account | License Manager | Service Access Control | Save an account |
+| Get account by identifier | License Manager | Service Access Control | Query that returns account by identifier, which can be the account id or the account application host. |
+| UI - Account list | License Manager | Web Access Control |
+| UI - Edit account | License Manager | Web Access Control |
+| UI - Edit role | License Manager | Web Access Control |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| View store sales stats | OMS | AcessoOMS | Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details. |
+| Invoices List | Billing | Invoice | Customers, billing and finance managers have access. Allows users to view invoices. |
+| Edit Company Information | Billing | Company | Only billing and finance managers have access. Allows users to edit Company data. |
+| Contracts List | Billing | Contracts | Customers, billing and finance managers have access. Allows users to view all contracts (active and inactive) for a company. |
+| Display Company info | Billing | Company | Customers, billing and finance managers have access. Allows users to view Company data. |
+| Contacts List | Billing | Contacts | Customers, billing and finance managers have access. Allows users to view the list of Contacts that receive email notifications when charges are incurred. |
+| Edit Contacts | Billing | Contacts | Only billing and finance managers have access. Allows users to edit contacts that receive notifications when charges are incurred. |
+| Generate new Invoice | Billing | Invoice | Only billing and finance managers have access. Finance managers can manually incur charges in the invoice through contracts. |
+| Edit Company's Document | Billing | Company | Only billing and finance managers have access. Allows users to edit the Company's document data (company registration number or individual taxpayer registration number), with which the invoice will be generated. |
+| Add Account | Billing | Company | Only billing and finance managers have access. Allows users to add an account to group other accounts linked to that customer into one billing. |
+| Delete Account | Billing | Company | Only billing and finance managers have access. Allows users to delete an account associated with a company. Company is the entity created to encompass several accounts from the same store. |
+| Save contracts | Billing | Contracts | Only billing, sales operations/growth and finance managers have access. Allows users to create new contracts. |
+| Cancel Invoice Document | Billing | Invoice | Only billing and finance managers have access. Cancel fiscal document in municipal administrations; gives the power to cancel a fiscal document even if the invoice has already been generated. |
+| Issue Invoice Document | Billing | Invoice | Only billing and finance managers have access. Used in specific cases of countries that do not generate fiscal documents automatically, depending on their financial system. In this case, they can be generated manually. |
+| Conciliate Invoice | Billing | Invoice | Only billing and finance managers have access. The default is to automatically mark it as paid, but the customer can pay it outside the system, depending on the negotiation. In this case, the finance manager has the power to manually mark it as paid, conciliating the invoices. |
+| Generate Invoice Overdue without Interest | Billing | Invoice | Only billing and finance managers have access. Incur new charge with interest. |
+| Cancel Invoice | Billing | Invoice | Only billing and finance managers have access. Cancel charges in billing; gives the power to cancel invoices even if they have already been generated. |
+| Change payment status | Billing | Invoice | Only billing and finance managers have access. The finance manager has the power to change a company’s payment status, depending on his negotiation with the client. |
+| Recalc Invoice | Billing | Invoice | Only billing and finance managers have access. Incur new charge with interest. |
+| Get Unscrewed Dashboard Charges | Billing | Dashboard | Only billing and finance managers have access. Access to a dashboard external to Admin, which displays invoices issued at that time, and which accounts are provisioned. |
+| Merge companies | Billing | Company | Only billing and finance managers have access. Allows the merger between two companies, unifying their billing. |
+| Split companies | Billing | Company | Only billing and finance managers have access. Allows to split a company into different companies. |
+| Unpaid invoices | Billing | Invoice | Only billing and finance managers have access. The finance manager can manually deselect the payment of a charge if it has not been made or if it has been made incorrectly. |
+| Get App | Log | Log Admin | VTEX internal use. |
+| Create Table | Log | Log Admin | VTEX internal use. |
+
+## Sales App - Sales Associate
+
+<div class="alert alert-warning">
+  <p>Sales associates registered in Sales App cannot access the VTEX Admin, only Sales App.</p>
+</div>
+
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Assisted Sales | Catalog | Televendas | After logging in, the user is redirected to the store (accountname.myvtex.com) |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recovers a transaction. |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| Cancel order | OMS | AcessoOMS | Allows users to cancel orders in OMS. |
 
 ## IntegrationProfile - Fulfillment
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
 
 ## IntegrationProfile - Fulfillment Gateway
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recovers a transaction.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Access to the button that manually notifies payments to the gateway in the payment area within the order.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to cancel orders in OMS.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Represents the payment gateway transactional operations. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recovers a transaction. |
+| Notify payment | OMS | AcessoOMS | Access to the button that manually notifies payments to the gateway in the payment area within the order. |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Cancel order | OMS | AcessoOMS | Allows users to cancel orders in OMS. |
 
 ## IntegrationProfile - Fulfillment Gateway GetOrder
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recovers a transaction.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Represents the payment gateway transactional operations. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recovers a transaction. |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
 
 ## IntegrationProfile - Fulfillment Gateway Oms
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recovers a transaction.</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to access actions within the workflow to change orders status, through the Actions button in the Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Access to the button that manually notifies payments to the gateway in the payment area within the order.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to manually inform invoices and data for tracking in OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Notify refund</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to notify when an accounts receivable invoice is in processing, indicating a journal entry for something that was refunded. Allows the input of a return invoice.</td>
-</tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to cancel orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to subscribe to receive order status updates in the Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to register changes in the order (discounts and/or exchanges)</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Represents the payment gateway transactional operations. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recovers a transaction. |
+| Change order workflow status | OMS | AcessoOMS | Allows users to access actions within the workflow to change orders status, through the Actions button in the Workflow |
+| Notify payment | OMS | AcessoOMS | Access to the button that manually notifies payments to the gateway in the payment area within the order. |
+| Notify invoice | OMS | AcessoOMS | Allows users to manually inform invoices and data for tracking in OMS. |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Notify refund | OMS | AcessoOMS | Allows users to notify when an accounts receivable invoice is in processing, indicating a journal entry for something that was refunded. Allows the input of a return invoice. |
+| Cancel order | OMS | AcessoOMS | Allows users to cancel orders in OMS. |
+| Order feed subscription | OMS | AcessoOMS | Allows users to subscribe to receive order status updates in the Order Feed. |
+| Change order | OMS | AcessoOMS | Allows users to register changes in the order (discounts and/or exchanges) |
+| View store sales stats | OMS | AcessoOMS | Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details. |
 
 ## IntegrationProfile - Fulfillment Oms
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows access to actions within the workflow to change order status, through the Actions button in the Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Access to the button that manually notifies payments to the gateway in the payment area within the order.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to manually inform invoices and data for tracking in OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Notify refund</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to notify when an accounts receivable invoice is in processing, indicating a journal entry for something that was refunded. Allows the input of a return invoice.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to cancel orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to subscribe to receive order status updates in the Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to register changes in the order (discounts and/or exchanges)</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Change order workflow status | OMS | AcessoOMS | Allows access to actions within the workflow to change order status, through the Actions button in the Workflow |
+| Notify payment | OMS | AcessoOMS | Access to the button that manually notifies payments to the gateway in the payment area within the order. |
+| Notify invoice | OMS | AcessoOMS | Allows users to manually inform invoices and data for tracking in OMS. |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| List Orders | OMS | AcessoOMS | Allows users to list all orders from the given account. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Notify refund | OMS | AcessoOMS | Allows users to notify when an accounts receivable invoice is in processing, indicating a journal entry for something that was refunded. Allows the input of a return invoice. |
+| Cancel order | OMS | AcessoOMS | Allows users to cancel orders in OMS. |
+| Order feed subscription | OMS | AcessoOMS | Allows users to subscribe to receive order status updates in the Order Feed. |
+| Change order | OMS | AcessoOMS | Allows users to register changes in the order (discounts and/or exchanges) |
+| View store sales stats | OMS | AcessoOMS | Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details. |
 
 ## IntegrationProfile - OrderSimulation
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources | |
 
 ## Logistics - Full access
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Home page</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Help home page</td>
-  </tr>
-  <tr>
-    <td>Logistics full access</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Gives full access to all logistics resources (viewing, creating, editing and canceling settings)</td>
-  </tr>
-  <tr>
-    <td>Logistics viewer</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Permission to view the start page of the logistics module.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory full access</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Gives full access to the logistics inventory (viewing, creating, editing and canceling settings).</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory read only</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Allows users to view the inventory module.</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping full access</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Gives full access to all shipping functions of the logistics module (creation, editing and cancelation of settings).</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping read only</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>test</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Home-page | Catalog | Administration | Home page |
+| Help-page | Catalog | Administration | Help home page |
+| Logistics full access | Logistics | Access to Logistics | Gives full access to all logistics resources (viewing, creating, editing and canceling settings) |
+| Logistics viewer | Logistics | Access to Logistics | Permission to view the start page of the logistics module. |
+| Logistics inventory full access | Logistics | Access to Logistics | Gives full access to the logistics inventory (viewing, creating, editing and canceling settings). |
+| Logistics inventory read only | Logistics | Access to Logistics | Allows users to view the inventory module. |
+| Logistics shipping full access | Logistics | Access to Logistics | Gives full access to all shipping functions of the logistics module (creation, editing and cancelation of settings). |
+| Logistics shipping read only | Logistics | Access to Logistics |   |
 
 ## Logistics - Read only
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Logistics viewer</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Permission to view the start page of the logistics module.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory read only</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Allows users to view the inventory module.</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping read only</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>test</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Logistics viewer | Logistics | Access to Logistics | Permission to view the start page of the logistics module. |
+| Logistics inventory read only | Logistics | Access to Logistics | Allows users to view the inventory module. |
+| Logistics shipping read only | Logistics | Access to Logistics | test |
 
 ## OMS - Full access
 
 Resource table:
 
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Home page</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administration</td>
-    <td>Help home page</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AccessOMS</td>
-    <td>Allows users to access actions within the workflow to change orders status, through the Actions button in the Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-      <td>Access to the button that manually notifies payments to the gateway in the payment area within the order.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to manually inform invoices and data for tracking in OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Logistics full access</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Gives full access to all logistics resources (viewing, creating, editing and canceling settings)</td>
-  </tr>
-  <tr>
-    <td>Notify refund</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to notify when an accounts receivable invoice is in processing, indicating a journal entry for something that was refunded. Allows the input of a return invoice.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to cancel orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to subscribe to receive order status updates in the Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to register changes in the order (discounts and/or exchanges)</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory full access</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Gives full access to the logistics inventory (viewing, creating, editing and canceling settings).</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping full access</td>
-    <td>Logistics</td>
-    <td>Access to Logistics</td>
-    <td>Gives full access to all shipping functions of the logistics module (creation, editing and cancelation of settings).</td>
-  </tr>
-</table>
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Home-page | Catalog | Administration | Home page |
+| Help-page | Catalog | Administration | Help home page |
+| Change order workflow status | OMS | AccessOMS | Allows users to access actions within the workflow to change orders status, through the Actions button in the Workflow |
+| Notify payment | OMS | AcessoOMS | Access to the button that manually notifies payments to the gateway in the payment area within the order. |
+| Notify invoice | OMS | AcessoOMS | Allows users to manually inform invoices and data for tracking in OMS. |
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| Logistics full access | Logistics | Access to Logistics | Gives full access to all logistics resources (viewing, creating, editing and canceling settings) |
+| Notify refund | OMS | AcessoOMS | Allows users to notify when an accounts receivable invoice is in processing, indicating a journal entry for something that was refunded. Allows the input of a return invoice. |
+| Cancel order | OMS | AcessoOMS | Allows users to cancel orders in OMS. |
+| Order feed subscription | OMS | AcessoOMS | Allows users to subscribe to receive order status updates in the Order Feed. |
+| Change order | OMS | AcessoOMS | Allows users to register changes in the order (discounts and/or exchanges) |
+| View store sales stats | OMS | AcessoOMS | Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details. |
+| Logistics inventory full access | Logistics | Access to Logistics | Gives full access to the logistics inventory (viewing, creating, editing and canceling settings). |
+| Logistics shipping full access | Logistics | Access to Logistics | Gives full access to all shipping functions of the logistics module (creation, editing and cancelation of settings). |
 
 ## OMS - Read only
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Allows users to view all orders in OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details.</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| View order | OMS | AcessoOMS | Allows users to view all orders in OMS. |
+| View store sales stats | OMS | AcessoOMS | Displays totalizers within the All Orders section in Orders Management. Displays total sales in addition to orders details. |
 
 ## Seller Manager
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>View Seller</td>
-    <td>Seller Register</td>
-    <td>Seller Administration</td>
-    <td>Allows users to view all sellers from an account</td>
-  </tr>
-  <tr>
-    <td>Save Seller</td>
-    <td>Seller Register</td>
-    <td>Seller Administration</td>
-    <td>Allows users to create and edit all sellers from an account</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| View Seller | Seller Register | Seller Administration | Allows users to view all sellers from an account |
+| Save Seller | Seller Register | Seller Administration | Allows users to create and edit all sellers from an account |
 
 ## User Administrator - RESTRICTED
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Save user</td>
-    <td>License Manager</td>
-    <td>Services access control</td>
-    <td>Create users, add or delete user roles, edit user data, create and edit application keys..</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Save user | License Manager | Services access control | Create users, add or delete user roles, edit user data, create and edit application keys.. |
 
 ## VTEX IO Admin
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Get resource by key</td>
-    <td>License Manager</td>
-    <td>Service Access Control</td>
-    <td>Checks access permissions</td>
-  </tr>
-  <tr>
-    <td>Read Workspace Apps</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading the apps installed in the workspace and their direct and indirect dependencies.</td>
-  </tr>
-  <tr>
-    <td>Link App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows listing existing links and linking and unlinking apps.</td>
-  </tr>
-  <tr>
-    <td>Install App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows users to install and uninstall apps.</td>
-  </tr>
-  <tr>
-    <td>Vbase Read Only</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Read-only access to vbase.</td>
-  </tr>
-  <tr>
-    <td>Vbase Read Write</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Read and write access to vbase.</td>
-  </tr>
-  <tr>
-    <td>Read Workspace Services</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading the infra apps in the workspace.</td>
-  </tr>
-  <tr>
-    <td>Install Service</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows users to install and uninstall apps</td>
-  </tr>
-  <tr>
-    <td>Log Access - Read-only</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading logs from all applications</td>
-  </tr>
-  <tr>
-    <td>Read Published Service</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading the services data from the infra registry</td>
-  </tr>
-  <tr>
-    <td>Debug App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows connecting a debugger to a linked app</td>
-  </tr>
-  <tr>
-    <td>Workspace CRUD</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows creating, deleting and modifying workspaces</td>
-  </tr>
-  <tr>
-    <td>Import Redirects</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Enable users to manage redirects with VTEX IO's command line interface</td>
-  </tr>
-  <tr>
-    <td>Manage A/B Test</td>
-    <td>VTEX IO</td>
-    <td>A/B Test</td>
-    <td>Allows users to start, finish or get status of an A/B Test</td>
-  </tr>
-  <tr>
-    <td>Read logs</td>
-    <td>Application Logs Stream</td>
-    <td>Logs</td>
-    <td>Read logs from VTEX IO apps owned from this account</td>
-  </tr>
-</table>
+Resource table:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Get resource by key | License Manager | Service Access Control | Checks access permissions |
+| Read Workspace Apps | VTEX IO | Infrastructure | Allows reading the apps installed in the workspace and their direct and indirect dependencies. |
+| Link App | VTEX IO | Infrastructure | Allows listing existing links and linking and unlinking apps. |
+| Install App | VTEX IO | Infrastructure | Allows users to install and uninstall apps. |
+| Vbase Read Only | VTEX IO | Infrastructure | Read-only access to vbase. |
+| Vbase Read Write | VTEX IO | Infrastructure | Read and write access to vbase. |
+| Read Workspace Services | VTEX IO | Infrastructure | Allows reading the infra apps in the workspace. |
+| Install Service | VTEX IO | Infrastructure | Allows users to install and uninstall apps |
+| Log Access - Read-only | VTEX IO | Infrastructure | Allows reading logs from all applications |
+| Read Published Service | VTEX IO | Infrastructure | Allows reading the services data from the infra registry |
+| Debug App | VTEX IO | Infrastructure | Allows connecting a debugger to a linked app |
+| Workspace CRUD | VTEX IO | Infrastructure | Allows creating, deleting and modifying workspaces |
+| Import Redirects | VTEX IO | Infrastructure | Enable users to manage redirects with VTEX IO's command line interface |
+| Manage A/B Test | VTEX IO | A/B Test | Allows users to start, finish or get status of an A/B Test |
+| Read logs | Application Logs Stream | Logs | Read logs from VTEX IO apps owned from this account |
 
 ## VTEX Payment - Account Holder
 
@@ -1192,20 +343,8 @@ This role allows users to read information about the VTEX Payment operation.
 
 ## Webservice - Full access
 
-&nbsp;&nbsp;&nbsp;&nbsp;Resource table:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Resource name</th>
-    <th bgcolor="#efefef" >Product</th>
-    <th bgcolor="#efefef" >Category</th>
-    <th bgcolor="#efefef" >Description</th>
-  </tr>
-  <tr>
-    <td>Webservice access</td>
-    <td>WebService</td>
-    <td>webservice</td>
-    <td>Permission to use any SOAP request</td>
-  </tr>
-</table>    
+Resource table:
 
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Webservice access | WebService | webservice | Permission to use any SOAP request |
diff --git a/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md b/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md
index a616f27f9..a66b4f213 100644
--- a/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md
+++ b/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md
@@ -3,8 +3,8 @@ title: 'How to prevent a carrier from meeting a certain ZIP code range?'
 id: 6GEYG5p9E4MOEy2qmY4uGa
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:39.807Z
-updatedAt: 2023-03-29T14:15:58.885Z
-publishedAt: 2023-03-29T14:15:58.885Z
+updatedAt: 2024-03-01T01:07:45.930Z
+publishedAt: 2024-03-01T01:07:45.930Z
 firstPublishedAt: 2019-01-24T22:03:33.994Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -31,5 +31,8 @@ To do so, you would follow these steps:
 2. Download the shipping spreadsheet on **Shipping Rates**.    
 3. Open the spreadsheet and look for the lines corresponding to the zip code range where the code to be disregarded is located, ie: `ZipCodeStart` = __37900-001__ and `ZipCodeEnd` = __97904-999__.  
 4. Each of these lines must be turned into two, so that the zip code 45920-000 is ignored. So you would have: `ZipCodeStart` = __37900-001__ and `ZipCodeEnd` = __45919-999__ / `ZipCodeStart` = __45920-001__ and `ZipCodeEnd` = __97904-999__.  
-
 With this, the spreadsheet would "jump" the zip code 45920-000. And consequently it would no longer be considered as an address served by that carrier.
+
+<div class = "alert alert-info">
+The postal code examples in this article refer to Brazil, each country has its own postal code format.
+</div>
diff --git a/docs/tutorials/en/price-divergence-rule.md b/docs/tutorials/en/price-divergence-rule.md
index 70780b7e0..38db6e3f8 100644
--- a/docs/tutorials/en/price-divergence-rule.md
+++ b/docs/tutorials/en/price-divergence-rule.md
@@ -3,8 +3,8 @@ title: '​​Price Divergence rule'
 id: 6RlFLhD1rIRRshl83KnCjW
 status: PUBLISHED
 createdAt: 2021-12-25T20:10:25.853Z
-updatedAt: 2023-03-29T21:53:14.071Z
-publishedAt: 2023-03-29T21:53:14.071Z
+updatedAt: 2024-03-22T15:11:31.300Z
+publishedAt: 2024-03-22T15:11:31.300Z
 firstPublishedAt: 2021-12-25T21:05:20.600Z
 contentType: tutorial
 productTeam: Channels
@@ -29,7 +29,7 @@ The Price Divergence rule is composed of one or more order authorization rules.
 - **Automatically deny:** Orders with a price difference within the defined range are automatically rejected and are not integrated.
 - **Create a task in VTEX DO for approval:** For price differences within the defined range, the order is integrated but needs to be [manually approved](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#approving-orders-manually) by an authorized user.
 
-![print_1_EN](https://drive.google.com/uc?export=download&id=10tfCItSpjc08OSwSYHCK9rs9enBOJ2vC)
+![price_divergence_rules_EN](//images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/813c44996850c4bd68a5ea4be1a92f41/price_divergence_rules_EN.png)
 
 When the [Price Divergence rule configuration](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) was not made, orders with price divergence errors are automatically approved. This applies to VTEX marketplaces, external marketplaces, and certified connectors (partners), but not to [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex).
 
diff --git a/docs/tutorials/en/price-divergence-rules-beta.md b/docs/tutorials/en/price-divergence-rules-beta.md
index 2ae67b509..eedbdc967 100644
--- a/docs/tutorials/en/price-divergence-rules-beta.md
+++ b/docs/tutorials/en/price-divergence-rules-beta.md
@@ -57,7 +57,7 @@ To create a rule, follow the steps below:
    * The system automatically configures a rule with a percentage of divergence between 0% and 30%, corresponding to the light blue bar.
 6. hoose one of the following options for the authorization rule: `Automatically authorize`, `Automatically deny`, or `Create a VTEX DO task to approve`.
 7. To increase or decrease the divergence percentage, click on the bar and drag its extremities considering the symbols "<" (less than) and ">" (greater than).
-8. To create the second rule, click on the icon <img class="shadow-4" src="https://https://images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> and repeat steps 6 and 7.
+8. To create the second rule, click on the icon <img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> and repeat steps 6 and 7.
 9. Click on `Save rules`.
 
 During the process of creating rules, you will see the following tabs:
diff --git a/docs/tutorials/en/price-table-management-in-b2b-organizations.md b/docs/tutorials/en/price-table-management-in-b2b-organizations.md
new file mode 100644
index 000000000..8d2f58c2b
--- /dev/null
+++ b/docs/tutorials/en/price-table-management-in-b2b-organizations.md
@@ -0,0 +1,48 @@
+---
+title: 'Price table management in B2B organizations'
+id: 1iNpulqvLT2KJ2fnznpN4L
+status: PUBLISHED
+createdAt: 2024-06-25T18:44:58.230Z
+updatedAt: 2024-06-25T19:14:38.840Z
+publishedAt: 2024-06-25T19:14:38.840Z
+firstPublishedAt: 2024-06-25T19:14:38.840Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: price-table-management-in-b2b-organizations
+locale: en
+legacySlug: price-table-management-in-b2b-organizations
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+The [price tables](https://help.vtex.com/pt/tutorial/criar-tabelas-de-precos?locale=pt) in a VTEX B2B operation are essential for customizing the commercial conditions offered to different organizations. They allow you to:
+
+- Define specific prices for products.
+- Create and manage multiple price tables.
+- Ensure that each customer sees the correct price in their category.
+
+You can manage price tables by:
+- [Associating price tables with an organization](#associating-price-tables-with-an-organization)
+- [Removing a price table association](#removing-a-price-table-association
+)
+
+## Associating price tables with an organization
+On VTEX, an organization is an entity that represents a company. To associate price tables with an organization, follow these steps:
+
+1. In the VTEX Admin, go to **Apps > Organizations > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access its details page.
+3. On the details page, click the **Price Tables** tab.
+4. Select the desired price tables from the **Available** list.
+5. Click `ADD TO ORG` to add it to the organization.
+6. Click `Save` at the top right of the page.
+
+## Removing the price table association
+To remove price tables from an organization, follow these steps:
+
+1. In the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizations**, or type **Organizations** in the search bar at the top of the page.
+2. Click the name of the desired organization to access its details page.
+3. On the details page, click the **Price Tables** tab.
+4. Select the desired price tables from the **Assigned to organization** list.
+5. Click `REMOVE FROM ORG`.
+6. Click `Save` at the top right of the page.
+
diff --git a/docs/tutorials/en/price-waterfall.md b/docs/tutorials/en/price-waterfall.md
index 8834531c2..7582c3fe4 100644
--- a/docs/tutorials/en/price-waterfall.md
+++ b/docs/tutorials/en/price-waterfall.md
@@ -21,7 +21,7 @@ With this new feature, we now have a new price entity called *Conditional Prices
 
 Below we have an illustration showing how this price waterfall works:
 
-![priceWaterfall](https://images.ctfassets.net/alneenqid6w5/5SSTp5o3VS4eucykWG4wo2/6699e0bd2c023a46cfc322fd89b0b04c/Screen_Shot_2018-08-27_at_14.01.54.png)
+![priceWaterfall](//images.ctfassets.net/alneenqid6w5/5SSTp5o3VS4eucykWG4wo2/6699e0bd2c023a46cfc322fd89b0b04c/Screen_Shot_2018-08-27_at_14.01.54.png)
 
 When a price for a specific SKU is requested to the *Pricing* module:
 1. A *Fixed Price* is selected according to its criteria like **scheduling** and **minimum quantity**.
diff --git a/docs/tutorials/en/prices-data-pipeline-beta.md b/docs/tutorials/en/prices-data-pipeline-beta.md
new file mode 100644
index 000000000..72ff682b8
--- /dev/null
+++ b/docs/tutorials/en/prices-data-pipeline-beta.md
@@ -0,0 +1,92 @@
+---
+title: 'Prices Data Pipeline (Beta)'
+id: 3NMGJ8dtv73Bwvo9PSz1fz
+status: PUBLISHED
+createdAt: 2024-06-21T14:58:43.084Z
+updatedAt: 2024-06-21T16:20:22.452Z
+publishedAt: 2024-06-21T16:20:22.452Z
+firstPublishedAt: 2024-06-21T15:27:43.768Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: prices-data-pipeline-beta
+locale: en
+legacySlug: prices-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+The price dataset contains historical price information for each SKU in a merchant's store, enabling analysis of markup values and monthly price trends.  
+
+This article includes the following information:  
+
+- [Data characteristics](#data-characteristics)
+- [Table: pricing_latest](#table-pricing-latest)
+- [Table: pricing_historical](#table-pricing-historical)
+- [Analyses with price data](#analyses-with-price-data)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics  
+
+| **Feature** | **Description** |
+|:-----------:|:---------------:|
+| Data source | Prices module.  |
+| Availability| VTEX Admin and Pricing APIs. Keep in mind that the data available through the API may not be structured exactly the same way as it is in the Data Pipeline dataset. |
+| History    | Data history starts in August 2023. For clients already using the VTEX platform, data is retained for two years from 2024. |
+| Minimum update interval | One hour. | 
+
+## Table: pricing_latest  
+
+The `pricing_latest` table contains current price data for the store's products. The table includes the following fields:  
+
+| **Column name**  | **Column type** | **Column description** |
+|:------------:|:---------------:|:---------------:|
+| account_name | character varying(255) | Name of the account associated with the item. |
+| last_date   | date  | Date and time of the last price change. |
+| sku_id   | character varying(255) | SKU identifier.  |
+| batch_id | character varying(255) 	| Identifier used when data is loaded into the table for quality control of data ingestion. |
+| listPrice   | double precision   | SKU list price. |
+| costPrice   | double precision   | SKU cost price. |
+| markup   | double precision   | SKU markup.   |
+| basePrice  | double precision | SKU base price. |
+| fixedPrices| super   | Fixed price.  |
+
+## Table: pricing_historical
+
+The `pricing_historical` table provides a historical record of your store's prices. The table fields are described below:  
+
+| **Column name**  | **Column type** | **Column description** |
+|:------------:|:----------:|:-------------:|
+| account_name | character varying(255) | Name of the account associated with the item. |
+| date   | date   | Date and time of the last price change. |
+| sku_id | character varying(255) 	| SKU identifier. |
+| author_id | character varying(255) 	| Identifier of the user who made the price change. |
+| batch_id  | character varying(255) 	| Identifier used when data is loaded into the table for quality control of data ingestion. |
+| id  | character varying(255) 	| Price change ID. |
+| listPrice | double precision  | SKU list price. |
+| costPrice | double precision | SKU cost price. |
+| markup    | double precision  | SKU markup.   |
+| basePrice | double precision  | SKU base price. |
+| fixedPrices | super  | Fixed price.  |
+
+## Analyses with price data    
+
+Price data can be used in the following analyses:  
+
+- __Current SKU price:__ Assess the current price for a particular SKU or for a product range.  
+- __SKU price history:__ Explore the price history for a particular SKU or for a product range.  
+- __SKU price per account:__ For stores with multiple VTEX accounts, this data helps to compare prices across different stores.  
+## Correlations with other data  
+
+The price dataset has correlations with the following sets of the VTEX data ecosystem:  
+
+- **Interaction with order data:** Combining order data provides insights into sales trends related to a product price, allowing price elasticity analysis.  
+- **Relationship with inventory:** Integrating with inventory data enables you to assess the total value of your assets accurately.  
+- **Impact on conversion rates:** By examining navigation and conversion funnel data, you can understand the influence of price on conversion rates.  
+
+### Discover other Datasets
+
+- [Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navigation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Payments](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Orders](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Promotions](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/en/prices-settings.md b/docs/tutorials/en/prices-settings.md
index 602f215ea..d3316d9ff 100644
--- a/docs/tutorials/en/prices-settings.md
+++ b/docs/tutorials/en/prices-settings.md
@@ -3,8 +3,8 @@ title: 'Prices Settings'
 id: 3hbBtCzNUBrj8GaWgCtSWN
 status: PUBLISHED
 createdAt: 2020-10-14T18:43:49.750Z
-updatedAt: 2023-03-29T20:45:21.665Z
-publishedAt: 2023-03-29T20:45:21.665Z
+updatedAt: 2023-08-21T17:13:42.982Z
+publishedAt: 2023-08-21T17:13:42.982Z
 firstPublishedAt: 2020-10-22T19:38:48.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: price-configuration
 subcategory: 3O1NvPgBPqE0qU88MSQaie
 ---
 
-The _Store Settings > Products > Price Settings_ page on VTEX Admin allows you to change general pricing settings in an easy and fast way. 
+The **Store Settings > Products > Price Settings** page on VTEX Admin allows you to change general pricing settings in an easy and fast way. 
 
 You can set the default markup and price variation limit for your store, as well as inherit prices from your parent account and overwrite sellers' prices with those from your account.
 
diff --git a/docs/tutorials/en/prices.md b/docs/tutorials/en/prices.md
index 9eb4a1266..bc29ee15f 100644
--- a/docs/tutorials/en/prices.md
+++ b/docs/tutorials/en/prices.md
@@ -3,8 +3,8 @@ title: 'Prices'
 id: tutorials_4393
 status: PUBLISHED
 createdAt: 2017-04-27T21:50:28.982Z
-updatedAt: 2021-12-20T21:12:57.515Z
-publishedAt: 2021-12-20T21:12:57.515Z
+updatedAt: 2023-08-21T17:24:39.459Z
+publishedAt: 2023-08-21T17:24:39.459Z
 firstPublishedAt: 2017-04-27T23:11:16.737Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: prices-v2
 subcategory: 3pGCbMh80UueoeSqoAgSuS
 ---
 
-Pricing is managed in the *Pricing module*. Rates and promotions on the VTEX platform are taken care of in the *Promotions & Taxes*.
+Pricing is managed in the Pricing module. Rates and promotions on the VTEX platform are taken care of in the Promotions.
 
 Some of the advantages brought by the new price list are:
 
diff --git a/docs/tutorials/en/product-list.md b/docs/tutorials/en/product-list.md
index 72b126ca5..46f4cf59e 100644
--- a/docs/tutorials/en/product-list.md
+++ b/docs/tutorials/en/product-list.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Products'
 id: 49vxWqoaWRZC4atwLz6cMg
 status: PUBLISHED
 createdAt: 2021-04-12T15:21:30.529Z
-updatedAt: 2023-03-24T14:24:33.863Z
-publishedAt: 2023-03-24T14:24:33.863Z
+updatedAt: 2023-11-22T13:59:30.669Z
+publishedAt: 2023-11-22T13:59:30.669Z
 firstPublishedAt: 2021-04-12T18:21:27.025Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Products** page allows you to view and manage the complete list of products added to your store, simplifying catalog management on Seller Portal. You can access this page through the **Catalog** menu on VTEX Admin.
 
-![product-list-en](https://images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/db6872b42868dbe018b1f85c1a4d9da1/product-list-en.png)
+![product-list-en](//images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/db6872b42868dbe018b1f85c1a4d9da1/product-list-en.png)
 
 On the **Products** page, you can:
 
@@ -30,6 +30,8 @@ On the **Products** page, you can:
 
 By clicking on the `CREATE PRODUCT` button, you will be redirected to the page where you can add a new product to the catalog. Check out the article[ How to create a product](https://help.vtex.com/en/tutorial/how-to-create-a-product-beta--671zAWe0B9eCikzDu7kB1G) for more details.
 
+<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+
 ## Searching for product
 
 To search for a specific product, you can enter the product ID or name in the search bar above the product list. Search results are updated in real-time, so as you type, the product list displays updated results according to the term you are searching for.
diff --git a/docs/tutorials/en/products-and-skus-beta.md b/docs/tutorials/en/products-and-skus-beta.md
index 5c3b55cac..b2d4313a3 100644
--- a/docs/tutorials/en/products-and-skus-beta.md
+++ b/docs/tutorials/en/products-and-skus-beta.md
@@ -3,8 +3,8 @@ title: 'Products and SKUs (Beta)'
 id: 2ig7TmROlirWirZjFWZ3By
 status: PUBLISHED
 createdAt: 2022-11-30T17:55:25.970Z
-updatedAt: 2023-05-09T22:11:41.664Z
-publishedAt: 2023-05-09T22:11:41.664Z
+updatedAt: 2023-07-11T15:12:54.179Z
+publishedAt: 2023-07-11T15:12:54.179Z
 firstPublishedAt: 2022-11-30T19:04:31.183Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -21,7 +21,7 @@ subcategory: 6XPsLadoT3moZ7eTduCg3c
 
 The **Products and SKUs** page allows you to view and manage the list of all products in your store, including information about SKUs, last updated, and status. To access it, go to **Catalog > Products and SKUs**.
 
-![produtos-skus-en](https://images.ctfassets.net/alneenqid6w5/1XLBRg7olhbAUmgkD6kb7K/1fde8ca0724350f086e7983a937dbe67/produtos-skus-en.PNG)
+![products-skus-en](//images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/f02b69940302cf42cf3eefd80ec56445/products-skus-en.png)
 
 <div class="alert alert-info">
   <p>This page is only available to stores operating with the <a href="https://help.vtex.com/en/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">New VTEX Admin</a>. To access this page and be part of the new experience, join the New VTEX Admin <a href="https://content.vtex.com/participe-do-programa-beta-en/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">Beta program</a>.</p>
@@ -42,10 +42,8 @@ From the product list, you can find the following information:
 
 | **Column** | **Description** |
 |----|----|
-| **Name** | The product name, set when adding it. Below the name, the page displays the ID, which is the product's unique identifier code. |
-| **SKUs** | Displays the `View SKUs` option and, in parentheses, the number of SKUs of the product. For more details about it, read the [Viewing the SKU list](#viewing-the-sku-list) section. <br/><br/> To hide a product's SKUs, click the` Hide SKUs` button.|
+| **Name** | The product name, set when adding it. Below the name, the page displays the ID, which is the product's unique identifier code. <br/><br/> Next to the name, each row displays an arrow <i class="fas fa-chevron-right"></i> to [view the list of SKUs](#viewing-the-sku-list) associated with the product, an icon that represents [product status](#tracking-product-status) and the product image. |
 | **Last Update** | Date of the most recent product [indexing](https://help.vtex.com/en/tutorial/understanding-how-indexation-works--tutorials_256). For more details about this process, go to the [Viewing indexing information](#viewing-indexing-information) section. |
-| **Status** | Current product status. Check the possible status in the [Tracking product status](#tracking-product-status) section.|
 
 ## Creating a product
 
@@ -65,7 +63,7 @@ To find a specific product, you can type one of the following in the search bar:
 
 Then, click on the criteria you want to use for the search, as illustrated in the following image:
 
-![facelift-product-search-en](https://images.ctfassets.net/alneenqid6w5/PCBjrNpVcVr5Z4x3RdTgW/c27b9b7e3c947a913bdcd071c5fb085a/facelift-product-search-en.gif)
+![products-skus-search-en](//images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/f0f028bb188ed98868f4fc9738e96511/search-en.gif)
 
 The list of products displayed will then be refreshed according to your search. 
 
@@ -103,9 +101,9 @@ To view the status of a product's SKUs, read the section [Viewing the SKU List](
 
 ## Viewing the SKU list
 
-When you click `View SKUs` in the product row in the list, the platform displays a list with all the SKUs of that product: 
+When you click the arrow <i class="fas fa-chevron-right"></i> in the product row in the list, the platform displays a list with all the SKUs of that product: 
 
-![sku-quick-actions-en](https://images.ctfassets.net/alneenqid6w5/71pxP9DeCFZ9UrQdl67r9X/bf3e1916b4091622c4344afd1fdc4aa1/sku-quick-actions-en.gif)
+![sku-actions-en](//images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/06822a59851d6f677c47c4cd3d1d4230/sku-actions-en.gif)
 
 In the SKU list, you will find the following information:
 
@@ -118,6 +116,8 @@ In the SKU list, you will find the following information:
 * **Name:** SKU name.
 * <svg xmlns="http://www.w3.org/2000/svg" width="1.25rem" height="1.25rem" fill="currentColor" viewBox="0 0 256 256" class=" admin-ui-c-dnTJPl"><rect width="16rem" height="16rem" fill="none"></rect><path d="M224,177.32117V78.67873a8,8,0,0,0-4.07791-6.9726l-88-49.5a8,8,0,0,0-7.84418,0l-88,49.5A8,8,0,0,0,32,78.67873v98.64244a8,8,0,0,0,4.07791,6.97261l88,49.5a8,8,0,0,0,7.84418,0l88-49.5A8,8,0,0,0,224,177.32117Z" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></path><polyline points="222.897 74.626 128.949 128 33.108 74.617" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></polyline><line x1="128.94915" y1="127.99996" x2="128.01036" y2="234.82127" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line></svg> &nbsp; <strong>Edit inventory:</strong> It takes you to the inventory management page in VTEX Admin, to change the quantity of the SKU available in stock. Check out the [Inventory management](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139) article for more information.
 * <svg xmlns="http://www.w3.org/2000/svg" width="1.25rem" height="1.25rem" fill="currentColor" viewBox="0 0 256 256" class=" admin-ui-c-dnTJPl"><rect width="16rem" height="16rem" fill="none"></rect><line x1="128" y1="72" x2="128" y2="88" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line><line x1="128" y1="168" x2="128" y2="184" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line><circle cx="128" cy="128" r="96" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></circle><path d="M104,168h36a20,20,0,0,0,0-40H116a20,20,0,0,1,0-40h36" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></path></svg> &nbsp;<strong>Edit prices:</strong> It takes you to the **Price list** in the VTEX Admin to change the prices of the SKU.
+* <i class="far fa-clone"></i> __Copy SKU Code:__ Copies the SKU ID to the clipboard.
+* <i class="far fa-eye"></i> __Activate__ / <i class="far fa-eye-slash"></i> __Deactivate:__ Makes the SKU active or inactive in the store.
 
 ## Editing products
 
@@ -148,7 +148,7 @@ When clicking the menu on a product line and choosing **View indexed info**, you
 
 This modal tab displays the SKU list associated with the product and its corresponding indexed information.
 
-![catalog-price-inventory-en](https://images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/b3968e801767f2d06423bc507f2ea6b5/price-inventory-en.PNG)
+![catalog-price-inventory-en](//images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/b3968e801767f2d06423bc507f2ea6b5/price-inventory-en.PNG)
 
 By clicking the arrow `>` in each SKU row, you can view a table with the following information:
 
@@ -163,7 +163,7 @@ By clicking the arrow `>` in each SKU row, you can view a table with the followi
 
 This modal tab displays the log, in other words, the detailed technical indexing record for the product and related SKUs.
 
-![indexed-log-en](https://images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/4c2095af6dec446e27db570e067b4d5f/indexed-log-en.PNG)
+![indexed-log-en](//images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/4c2095af6dec446e27db570e067b4d5f/indexed-log-en.PNG)
 
 ## Learn more
 
diff --git a/docs/tutorials/en/promotion-alerts-beta.md b/docs/tutorials/en/promotion-alerts-beta.md
index 08b28b161..527498de4 100644
--- a/docs/tutorials/en/promotion-alerts-beta.md
+++ b/docs/tutorials/en/promotion-alerts-beta.md
@@ -29,7 +29,7 @@ Suppose you only configure the email alert action, further orders with the unwan
 
 To access the page in the VTEX Admin, go to *Promotions > Promotion Alert*. You will see the following interface:
 
-![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
+![simuladordepromocoes gerenciar](//images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
 
 The table below shows the column descriptions for the promotion list:
 
diff --git a/docs/tutorials/en/promotion-list-beta.md b/docs/tutorials/en/promotion-list-beta.md
index 90516a36e..2ce5b7f10 100644
--- a/docs/tutorials/en/promotion-list-beta.md
+++ b/docs/tutorials/en/promotion-list-beta.md
@@ -3,8 +3,8 @@ title: 'Promotion List'
 id: 4yB7nNdliiFxBTXE19GCIi
 status: PUBLISHED
 createdAt: 2022-05-05T13:39:53.273Z
-updatedAt: 2023-03-02T15:34:23.200Z
-publishedAt: 2023-03-02T15:34:23.200Z
+updatedAt: 2023-07-24T13:34:09.177Z
+publishedAt: 2023-07-24T13:34:09.177Z
 firstPublishedAt: 2022-05-05T13:52:17.590Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -30,7 +30,7 @@ The page displays the list of your store's promotions and their basic informatio
 | `To` | Promotion end date. |
 | `Status` | Promotion status, which can be: <p> __Active:__ when a promotion is active.</p> <p>__Scheduled:__ when the promotion was scheduled.</p> <p>__Paused:__ when the promotion is paused. <p>__Completed:__ when the promotion ended.</p> |
 
-![listadepromocoes en](https://images.ctfassets.net/alneenqid6w5/3QkCDSGnYVvzz6ygn3ZUm8/c790e13db5f9ce7b8e9fa276478813d1/listadepromocoes_en.gif)
+![listadepromocoes en](//images.ctfassets.net/alneenqid6w5/3QkCDSGnYVvzz6ygn3ZUm8/c790e13db5f9ce7b8e9fa276478813d1/listadepromocoes_en.gif)
 
 You can sort the promotions by name, date, or status. To do this, click on the title of the column with the information you want to use as sorting criteria.
 
@@ -82,7 +82,7 @@ The file contains the following information about each promotion:
 
 ## Promotion usage
 
-![usodaspromoções en](https://images.ctfassets.net/alneenqid6w5/5cvRZbj2TqwHuQcx6jjqm4/d94a8916fcd88257d83f8c8edd0a0dbf/usodaspromo____es_en.JPG)
+![usodaspromoções en](//images.ctfassets.net/alneenqid6w5/5cvRZbj2TqwHuQcx6jjqm4/d94a8916fcd88257d83f8c8edd0a0dbf/usodaspromo____es_en.JPG)
 
 To view the total of your active promotions and the remaining quota for new promotions, click `Promotion usage`. 
 
@@ -90,7 +90,7 @@ By default, the maximum number of active promotions is 100. If you need to incre
 
 ## Filter promotions
 
-![filtrodepromocoes en](https://images.ctfassets.net/alneenqid6w5/5ejpdUDVPbixeLp6nmDB1q/d637dba80b4cbda6194cae7cbf630785/filtrodepromocoes_en.gif)
+![filtrodepromocoes en](//images.ctfassets.net/alneenqid6w5/5ejpdUDVPbixeLp6nmDB1q/d637dba80b4cbda6194cae7cbf630785/filtrodepromocoes_en.gif)
 
 The promotion list can be filtered according to your needs by using the following filters:
 
diff --git a/docs/tutorials/en/promotion-summary.md b/docs/tutorials/en/promotion-summary.md
index 8b328098b..99c8f8ae7 100644
--- a/docs/tutorials/en/promotion-summary.md
+++ b/docs/tutorials/en/promotion-summary.md
@@ -64,19 +64,19 @@ High-risk alerts indicate that critical configurations or registration errors mu
 
 Example:
 
-![alert-alto-risco-EN](https://images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/6024c1bf2aee399450f05cbf2648798c/image.png)
+![alert-alto-risco-EN](//images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/6024c1bf2aee399450f05cbf2648798c/image.png)
 
 ### Medium risk
 Medium-risk alerts indicate that there are configurations that may cause undesired effects on the promotion.
 
 Example:
 
-![alert-medio-risco-EN](https://images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/38a07c0774736c5005638e78987d4a23/image.png)
+![alert-medio-risco-EN](//images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/38a07c0774736c5005638e78987d4a23/image.png)
 
 ### Low risk
 Low-risk alerts present relevant information about the promotion configuration, which can contribute to better performance.
 
 Example:
 
-![alert-baixo-risco-EN](https://images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/65f04416a92b8c5bd606064165803313/image.png)
+![alert-baixo-risco-EN](//images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/65f04416a92b8c5bd606064165803313/image.png)
 
diff --git a/docs/tutorials/en/promotions-beta.md b/docs/tutorials/en/promotions-beta.md
index e6958a9e4..3847c9501 100644
--- a/docs/tutorials/en/promotions-beta.md
+++ b/docs/tutorials/en/promotions-beta.md
@@ -32,20 +32,20 @@ The home page displays the promotions list in a grid that allows you to easily v
 - Duplicate or archive promotions using the <i class="fas fa-ellipsis-v"></i>  button;
 - Manage promotion conditions by clicking anywhere in the grid row (see [New promotion](#new-promotion) for more details about promotion conditions).
 
-![promobeta1 acoes lista promocoes EN](https://images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b3f2216333e8dd4cbd084b6408524541/promobeta1_acoes_lista_promocoes_EN.gif)
+![promobeta1 acoes lista promocoes EN](//images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b3f2216333e8dd4cbd084b6408524541/promobeta1_acoes_lista_promocoes_EN.gif)
 
 You can filter and sort your promotion list according to your needs. The VTEX platform allows you to filter your promotions by *Effects*, *Status*, *Starting date*, *Ending date*, or *Trade policy*.
 
-![promobeta2 filtros lista promocoes EN](https://images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/e1e802f323d8eba2e296a27ae0f27135/promobeta2_filtros_lista_promocoes_EN.gif)
+![promobeta2 filtros lista promocoes EN](//images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/e1e802f323d8eba2e296a27ae0f27135/promobeta2_filtros_lista_promocoes_EN.gif)
 
 You can also sort your list in ascending or descending order based on the basic information of the promotion by clicking on the filter title.
 
-![promobeta3 ordenacao lista promocoes EN](https://images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5f56351941377f0829b3582324ed347f/promobeta3_ordenacao_lista_promocoes_EN.gif)
+![promobeta3 ordenacao lista promocoes EN](//images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5f56351941377f0829b3582324ed347f/promobeta3_ordenacao_lista_promocoes_EN.gif)
 
 ## New promotion
 On the Promotions page, click on the __NEW PROMOTION__ button to access the promotion creation page, where you will fill in a series of fields to configure the desired conditions for your promotion. 
 
-![promobeta4 botao novapromocao EN](https://images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/29b06b468de480f45adef9896a7eabe4/promobeta4_botao_novapromocao_EN.png)
+![promobeta4 botao novapromocao EN](//images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/29b06b468de480f45adef9896a7eabe4/promobeta4_botao_novapromocao_EN.png)
 
 The new promotion conditions and fields are divided into the following groups:
 
diff --git a/docs/tutorials/en/promotions-overview.md b/docs/tutorials/en/promotions-overview.md
index 79fafd1e6..b2a1db584 100644
--- a/docs/tutorials/en/promotions-overview.md
+++ b/docs/tutorials/en/promotions-overview.md
@@ -3,8 +3,8 @@ title: 'Promotions Overview'
 id: 3PeHVYcooLIDmA33IAnjhm
 status: PUBLISHED
 createdAt: 2023-03-29T19:29:50.947Z
-updatedAt: 2023-03-29T19:33:24.646Z
-publishedAt: 2023-03-29T19:33:24.646Z
+updatedAt: 2023-09-13T22:35:44.331Z
+publishedAt: 2023-09-13T22:35:44.331Z
 firstPublishedAt: 2023-03-29T19:31:43.053Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,8 +19,6 @@ A promotion is a discount granted to the customer on one or more products in the
 
 In the **Promotions** menu of your redesigned Admin you can set up a promotion restricted to certain product lists, customer lists, zip code ranges, minimum cart value, and more.
 
-![visao-geral-promo-EN](https://images.ctfassets.net/alneenqid6w5/6FHow2OrXNqAoiKaJngwPU/57e0072889c99d6cfff9846f58fc28a9/image.png)
-
 Check out the menu’s different sections and pages below.
 
 ## Promotions
diff --git a/docs/tutorials/en/promotions-simulator-beta.md b/docs/tutorials/en/promotions-simulator-beta.md
index a2aad58bd..498258894 100644
--- a/docs/tutorials/en/promotions-simulator-beta.md
+++ b/docs/tutorials/en/promotions-simulator-beta.md
@@ -1,10 +1,10 @@
 ---
-title: 'Promotions Simulator (Beta)'
+title: 'Promotions Simulator '
 id: 4zc8SNqjqeIJ0ZRMhjlnvy
 status: PUBLISHED
 createdAt: 2022-09-13T21:22:59.620Z
-updatedAt: 2022-09-27T19:37:29.437Z
-publishedAt: 2022-09-27T19:37:29.437Z
+updatedAt: 2024-03-13T19:31:16.281Z
+publishedAt: 2024-03-13T19:31:16.281Z
 firstPublishedAt: 2022-09-13T22:59:58.058Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -12,96 +12,92 @@ author: 46G4yHIZerH7B9Jo0Iw5KI
 slug: promotions-simulator-beta
 locale: en
 legacySlug: promotions-simulator-beta
-subcategory: 6iTRZiMeCGXYiO2ckABFZi
+subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-<div class = "alert alert-info">
-This module is in Beta phase, which means that we are working to improve it. If you have any questions, please contact <a href="https://help.vtex.com/en/support">our Support team.</a>
+<div class="alert alert-warning">
+  <p>Users must have an authorized <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> that grants access to the <strong>Promotions</strong> module in the VTEX Admin to access the <strong>Promotion Simulator</strong>.</p>
 </div>
 
-<div class = "alert alert-warning">
-Users must have a <a href="https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">role</a> authorized to access the Promotions module in the VTEX Admin in order to access the Promotions Simulator.
-</div>
+The **Promotion Simulator** is a tool that allows you to view not only the promotions created in the VTEX platform and applied to the shopping cart but also their activation conditions. You can also test the application of promotions before activating them, including scheduled and inactive promotions.
 
-The **Promotions Simulator** is a tool that allows you to see not only the promotions created in the VTEX platform and which were applied to the shopping cart, but also their activation conditions. Since there are multiple configurations for the promotions, it is important to be able to see the [competition](https://help.vtex.com/en/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270), the accumulation of promotions during the purchase and the causes that trigger them.
+With multiple configuration possibilities for promotions, the simulator brings visibility into promotion [competition](https://help.vtex.com/en/tutorial/how-promotion-competition-works--tutorials_2270), how they are combined during the purchase, and the triggers that activate them.
 
-By using the simulator, you will be able to manage the promotions in your store and target them according to your business strategy.
+The **Promotion Simulator** is available for all VTEX stores through [Cartman](https://help.vtex.com/en/tutorial/configure-cartman--1ACMTStZYkMqB0lTgwg451), a tool for merchants at checkout. To access the simulator, follow the steps below:
 
-You can also [manage promotions](#managing-promotions), whether they are active or inactive, by clicking on the `Manage promotions` button.
+1. In the top bar of the VTEX Admin, click the `Preview` button to open your store's restricted access page.
 
-The simulator interface has five columns:
+    If you prefer, you can access it directly from the URL `https://{accountname}.myvtex.com/`, replacing `{accountname}` with the name of your VTEX account.
 
-| **Columns** |**Description**| 
-| ----------- | ------------- |
-| **Product** | List of products in the cart |
-| **Price** | Previous price (of) and final price (by) of the promotion applied |
-| **Quantity** | Total number of items in the cart |
-| **Total** | Total price that will be charged for the product, considering the promotion discounts and the number of items |
-| **Discount** | Status do desconto no carrinho, que podem serDiscount status in the cart, which can be: `Applied` ou `Not applied`. The status `Applied` indicates that at least one promotion has been applied to the product |
+2. Add products to the cart and access the checkout at `https://{accountname}.myvtex.com/checkout/#/cart`.
+3. Click the blue button <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> in the bottom right corner of the page to launch Cartman.
+4. Click **Promotion Simulator**.
 
-<div class = "alert alert-info">
-In the right corner of the screen, you'll see a megaphone button <i class="fas fa-bullhorn"></i> through which you can send feedback about your experience using the <b>Promotions Simulator</b>. 
-</div>
+   In the new window, you will find a list of the products in your cart and all the promotions that have been applied and are applicable to each item.
 
-To take advantage of the benefits of this feature, this article is divided into two sections:
+![Simulator-promo-en-gif-1](//images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/c05b0c30d34a029e4bff69dff70de0d5/simulador-promo-en-230706.gif)
 
-- [Access the Promotions Simulator](#accessing-the-promotions-simulator)
-- [Manage promotions](#managing-promotions)
+The **Promotion Simulator** interface displays the following information:
 
-## Accessing the Promotions Simulator
+| Column | Description |
+|---|---|
+| **Product** | List of products in the cart. |
+| **Price** | Full price and discounted price of the promotion applied. |
+| **Quantity** | Total number of items in the cart. |
+| **Total** | Total price that will be charged for the product, considering the promotion discounts and the number of items. |
+| **Discount** | Discount status in the cart, which can be: `Applied` or `Not applied`. The `Applied` status indicates that at least one promotion has been applied to the product.  |
 
-To access this feature, you need to [set up Cartman](https://help.vtex.com/en/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451) first, a tool that simulates, shares and researches carts from VTEX stores.
+<div class="alert alert-info">
+  <p>You can send us your feedback about your experience using the <strong>Promotion Simulator</strong> from the megaphone <i class="fas fa-megaphone"></i> button in the right corner of the screen.</p>
+</div>
 
-When you access the Simulator, you'll see a list with the products in your cart. You'll see all the promotions that can be applied to each of the items, followed by a check box <i class="fas fa-check-square"></i> in the promotion applied.
+### Updating the simulator
 
-The tool includes a search bar to find the promotions by product name or by promotion name. Besides, you can filter the promotions by **Promotion type** and **Discount**.
+If you need to add or remove items from your cart, you can keep the simulator window open. After making changes to your cart, click `Update` in the **Promotion Simulator** to review the promotions applied to the updated cart.
 
-By clicking on each product, you can see more information about the promotions that can be applied, details about your selection and the condition to activate them.
+### Searching and filtering promotions
 
-![simuladordepromocoes acessar](https://images.ctfassets.net/alneenqid6w5/7piR33ciR1x0givnQyxbk7/cdb47a1c812d3fa244aeb6127be100ee/simuladordepromocoes_acessar.gif)
+The tool provides a search bar for finding promotions by product or promotion name. Additionally, you can filter promotions by **Promotion type** ([Regular](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), [Buy Together](https://help.vtex.com/en/tutorial/buy-together--tutorials_323), [Get More for Less](https://help.vtex.com/en/tutorial/creating-a-more-for-less-promotion--tutorials_325), [Progressive Discount](https://help.vtex.com/en/tutorial/progressive-discount--tutorials_324), [Buy One, Get One](https://help.vtex.com/en/tutorial/buy-one-get-one--tutorials_322), or [Campaign Promotion](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume)) and **Discount** (Applied or Not Applied).
 
-Once Cartman is set up, follow these steps to access the Promotions Simulator:
+### Viewing applied promotions details
 
-1. Access your VTEX store shopping cart.
-2. Add the products you want to test. 
-3. In the shopping cart, open `Cartman`. 
-4. Click on the **See promotion details option**.
-5. There will appear the promotions applied to the cart. For further details about the promotions, click on See details.
-  > You’ll be redirected to the **Promotions Simulator**. When you access the Simulator, you'll see a list with the products in your cart. You'll see all the promotions that can be applied to each of the items, followed by a check box in the promotion applied.
-6. In case you modify the products in the cart, click on `Update` to load the new information.
+By clicking each product, you can see more information about the promotions applied to it, details about their effects, and the triggers that activated them. You can also see the promotions that have not been applied and the reason they were not.
 
-### Edit promotions
+### Editing promotions
 
 To edit a promotion, follow the steps below:
 
-1. Select a product in the **Promotions Simulator**.
-2. Click on the name of the promotion you want to edit.
-  >  You'll be redirected to the promotion form.
-3. Edit the [promotion fields](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#quais-os-dados-gerais-desta-promocao).
-4. Once you've made all the changes, click on `Save`.
+1. In the **Promotion Simulator**, click a product row or the arrow <i class="fas fa-chevron-right"></i>.
+2. Click the name of the promotion you want to edit.
+
+   You'll be redirected to the promotion form.
+
+3. Edit the [promotion fields](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#1-promotion-overview).
+4. Once you have made all changes, click `Save`.
+
+### Simulating promotions
 
-## Managing promotions
+The **Promotion Simulator** allows you to test the application of another promotion or simulate the effects of deactivating applied promotions. To do this, click the `Select Promotions` button at the top right of the page, as shown in the image below.
 
-If you want to simulate a new promotion or manage the existing ones, you should click the button `Manage promotions`, located on the top right corner of the screen.
+![ui-Simulator-promo-en-gif-2](//images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/31e593dbdb4fed07df101576ecc63f20/ui-simulador-promo-en-230706.gif)
 
-You'll be able to see all the active, paused, scheduled or completed promotions in the cart. By doing so, you'll be able to test a future status of the store. 
+To run a simulation, follow the instructions below:
 
-![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/6J3Bp4YcEZ6V5cgVj4dnhM/c0a6896fcec1bb0cf3bbc6ea3362d19f/simuladordepromocoes_gerenciar.gif)
+1. In the **Promotion Simulator**, click `Select Promotions` at the top right of the page.
 
-To test a promotion, follow these steps:
+    A list of all promotions in your store will be displayed, including active, paused, scheduled, and ended promotions.
 
-1. In the Promotions Simulator, click on `Manage promotions`.
-2. Select one or more promotions, regardless of the status.
-3. Click on the `Test` button.
+2. Select one or more promotions to simulate their application in your cart. You can also deselect active promotions if you wish to simulate their deactivation.
+3. Click the `Simulate` button.
 
-To check if the tested promotion has been applied, take a look at the status in the **Discount** column or click on the product for further details.
+    After running the simulation, you will see the results of the selected promotions. To verify if the tested promotions were applied to the cart items in the simulation, you can check the status of the **Discount** column or click the respective product.
 
-<div class = "alert alert-info">
-You can apply promotions to products that already have an active promotion. Although not all promotions can be applied, the VTEX system will always choose the most favorable one for your store customers, considering the total price of the items or the shipping cost.
+<div class="alert alert-info">
+  <p>You can apply promotions to products that already have an active promotion. However, please note that not all promotions can be applied. The VTEX system will always choose the most favorable one for your store customers, considering factors such as the total price of the items or the shipping cost.</p>
 </div>
 
 ### Learn more
 
- * [How promotions work](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR)
- * [Promotions for specific scenarios](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy)
- * [Configure Cartman](https://help.vtex.com/en/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451)
+* [How promotions work](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR)
+* [Promotions for specific scenarios](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy)
+* [Configuring Cartman](https://help.vtex.com/en/tutorial/configure-cartman--1ACMTStZYkMqB0lTgwg451)
diff --git a/docs/tutorials/en/promotions-simulator.md b/docs/tutorials/en/promotions-simulator.md
index 6ced2c982..3480b6de6 100644
--- a/docs/tutorials/en/promotions-simulator.md
+++ b/docs/tutorials/en/promotions-simulator.md
@@ -24,12 +24,12 @@ The **Promotions Simulator** allows you to view the promotions applied to shoppi
 To use this feature, you need to [configure Cartman](https://help.vtex.com/en/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451), a tool that simulates, shares, and explores carts. Once Cartman has been configured, follow the steps below to access the **Promotions Simulator**.
 
 1. Add products included in your store's promotions to your shopping cart.
-2. In the cart, click the following button <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> to open Cartman.
+2. In the cart, click the following button <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> to open Cartman.
 3. Select `View promotion details`.
 4. This window displays the promotions applied to the cart. For more details, click <i class="fas fa-search"></i>`View details`.
-![cartman-analisador-promoção-EN](https://images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/5e79f607478f8e4174edde1e1a1d6028/Screen_Shot_2022-03-07_at_11.13.45.png)
+![cartman-analisador-promoção-EN](//images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/5e79f607478f8e4174edde1e1a1d6028/Screen_Shot_2022-03-07_at_11.13.45.png)
 5. The **Promotions Simulator** window will be displayed.
-![analisador-promoção-EN](https://images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/2c0cc35c6a27d25365dc925faf204af4/image.png)
+![analisador-promoção-EN](//images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/2c0cc35c6a27d25365dc925faf204af4/image.png)
 
 In this window, you can view the following information:
 
diff --git a/docs/tutorials/en/promotions.md b/docs/tutorials/en/promotions.md
new file mode 100644
index 000000000..ad3ce8421
--- /dev/null
+++ b/docs/tutorials/en/promotions.md
@@ -0,0 +1,108 @@
+---
+title: 'Promotions Data Pipeline (Beta)'
+id: 3WZ1syNucDFdvVhfKtA6Qd
+status: PUBLISHED
+createdAt: 2024-02-02T18:02:01.395Z
+updatedAt: 2024-06-21T16:25:25.745Z
+publishedAt: 2024-06-21T16:25:25.745Z
+firstPublishedAt: 2024-05-27T19:26:59.739Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: promotions
+locale: en
+legacySlug: promotions
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+The promotion dataset is composed of four tables: `promotion_archived`, `promotion_created`, `promotion_removed`, and `promotion_unarchived`. These four tables cover the entire lifecycle of promotional campaigns, from launch to archiving, reactivation, or removal, providing a complete view of the store's promotional strategies.
+
+This section includes the following information:
+
+- [Data characteristics](#data-characteristics)
+- [Table: promotion_archived](#table-promotion-archived)
+- [Table: promotion_created](#table-promotion-created)
+- [Table: promotion_removed](#table-promotion-removed)
+- [Table: promotion_unarchived](#table-promotion-unarchived)
+- [Analyses with promotion data](#analyses-with-promotion-data)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics
+
+|**Characteristic**|**Description**|
+| - | - |
+|**Data source**|Obtained from the [Promotions module](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR) in the VTEX Admin.|
+|**Availability**|Promotion data can be accessed through the VTEX Admin and also via the [Promotions APIs](https://developers.vtex.com/docs/guides/promotions-overview).|
+|**History**|The data is retained for two years, from 2024 for clients who already use the VTEX platform.|
+|**Minimum update interval**|One hour.|
+
+## Table: promotion_archived
+
+The `promotion_archived` table contains all archived promotions. It includes details of promotions temporarily or permanently removed from active use, allowing a history and analysis of previous campaigns. The table fields are described below:
+
+|**Column name**|**Column type**|**Column description**|
+| - | - | - |
+|version|character varying(16383)|Table data version, useful for version control and compatibility.|
+|ingestion_time|timestamp without time zone|Date and time the data was added to the table.|
+|payload|super|Dataset actually stored in the table, comprising various details.|
+|batch_id|character varying(13)|Data batch identifier, used to track data ingestion and management.|
+
+## Table: promotion_created
+
+The `promotion_created` table contains information about newly created promotions. This table is very important for tracking new promotional campaign launches, offering insights into current marketing strategies and initiatives. The table fields are described below:
+
+|**Column name**|**Column type**|**Column description**|
+| - | - | - |
+|version|character varying(16383)|Specifies the version of the table data.|
+|ingestion_time|timestamp without time zone|The time the data was added to the table.|
+|payload|super|Contains the dataset or information that are actually loaded to the table.|
+|batch_id|character varying(13)|Unique identifier of the data batch, used to track and manage data ingestion.|
+
+## Table: promotion_removed
+
+The `promotion_removed` table contains promotions that have been deleted or deactivated, and allows analyzing promotions that have been discontinued and see the reasons behind their discontinuation. The table fields are described below:
+
+|**Column name**|**Column type**|**Column description**|
+| - | - | - |
+|version|character varying(16383)|Data version.|
+|ingestion_time|timestamp without time zone|Date and time of data ingestion.|
+|payload|super|Content of the data that was added.|
+|batch_id|character varying(13)|Control ID of the data batch.|
+
+## Table: promotion_unarchived
+
+The `promotion_unarchived` table contains promotions that have been reactivated or removed from the archive. It provides information about campaigns that have been reintroduced, which gives insights into strategies for reusing or revising previous promotions. The table fields are described below:
+
+|**Column name**|**Column type**|**Column description**|
+| - | - | - |
+|version|character varying(16383)|Version of the table data.|
+|ingestion_time|timestamp without time zone|Date and time the data was added to the table.|
+|payload|super|Dataset actually stored in the table.|
+|batch_id|character varying(13)|Identifier of the data batch added to the table.|
+
+## Analyses with promotion data
+
+The promotion dataset can be used for the following analyses:
+
+- **Promotion lifecycle analysis:** Compare the frequency and duration of promotions to assess the longevity and success of campaigns.  
+- **Promotion reactivation rate:** Analyze the number of promotions that are reactivated to determine the effectiveness of reusing or revising previous campaigns.  
+- **Promotion removal trends:** Track the number and types of discontinued promotions to understand the removal reasons and adjust future strategies.  
+- **Impact of new promotions:** Assess the immediate impact of new promotion launches by comparing them with changes in sales and traffic.  
+
+## Correlations with other data
+
+The promotion dataset has key relationships with other datasets, some of which are mentioned below:  
+
+- **[Order](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) data:** Analyzing the influence of promotions on orders helps to understand their impact on sales.  
+- **[Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2) data:** Correlating inventory data is important to guarantee the availability of promoted products.  
+- **Marketing and advertising analyses:** Integrating this data allows measuring how effective promotions are in attracting traffic and engagement.  
+- **Website [navigation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) data:** Analyzing the effect of promotions on navigation provides insights into customer behavior and the effectiveness of promotion display.  
+
+### Discover other datasets
+
+- [Inventory](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navigation](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Orders](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Payments](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Prices](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz) 
+
diff --git a/docs/tutorials/en/protection-against-transaction-attacks.md b/docs/tutorials/en/protection-against-transaction-attacks.md
index ed24b5e86..6c29c465b 100644
--- a/docs/tutorials/en/protection-against-transaction-attacks.md
+++ b/docs/tutorials/en/protection-against-transaction-attacks.md
@@ -3,7 +3,7 @@ title: 'Protection against transaction attacks'
 id: 62oQBmi7UZlYlgb0Ha1hZ3
 status: DRAFT
 createdAt: 2021-10-25T19:02:59.690Z
-updatedAt: 2021-12-10T13:52:07.652Z
+updatedAt: 2024-03-01T15:58:16.139Z
 publishedAt: 
 firstPublishedAt: 
 contentType: tutorial
@@ -36,9 +36,9 @@ To enable the protection, please follow the instructions below:
 4. In the upper right corner, click on the Settings icon.
 5. Under __Attack protection__, click on the button to enable it (green color indicates "enabled").
 
-![proteção-botao-configurações](https://images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
+![proteção-botao-configurações](//images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
 
-![protection-option-enable1](https://images.ctfassets.net/alneenqid6w5/QSVTQfbO9BDFUB33KXgj7/9ee748c43264183f31f071514862a068/protection-option-enable1.png)
+![protection-option-enable1](//images.ctfassets.net/alneenqid6w5/QSVTQfbO9BDFUB33KXgj7/9ee748c43264183f31f071514862a068/protection-option-enable1.png)
 
 ### How to disable protection against transaction attacks?
 
@@ -69,13 +69,13 @@ To access this information, please follow the instructions below.
 6. To select __Detected threats__ or __Neutralized threats__, click on one of the arrows on the right.
 7. Check the details of the events in the popup window displayed.
 
-![protection-option-historic1](https://images.ctfassets.net/alneenqid6w5/6oUr155OKf1tKDw3O3i2ZD/a0a2156aa0b0b791992c67cc21f71279/protection-option-historic1.png)
+![protection-option-historic1](//images.ctfassets.net/alneenqid6w5/6oUr155OKf1tKDw3O3i2ZD/a0a2156aa0b0b791992c67cc21f71279/protection-option-historic1.png)
 
-![protection-screen-historic1](https://images.ctfassets.net/alneenqid6w5/6mjiUMYjTQ2nmU7NZKGnyk/c92c6fe16f49fab604337c8749c10657/protection-screen-historic1.png)
+![protection-screen-historic1](//images.ctfassets.net/alneenqid6w5/6mjiUMYjTQ2nmU7NZKGnyk/c92c6fe16f49fab604337c8749c10657/protection-screen-historic1.png)
 
-![screen-threat-potential1](https://images.ctfassets.net/alneenqid6w5/4ZyYbA7qHIc5PvpxxiHlKk/22a6858af2e7a5acac9ef3d5bb6ff106/screen-threat-potential1.png)
+![screen-threat-potential1](//images.ctfassets.net/alneenqid6w5/4ZyYbA7qHIc5PvpxxiHlKk/22a6858af2e7a5acac9ef3d5bb6ff106/screen-threat-potential1.png)
 
-![screen-threat-neutralized1](https://images.ctfassets.net/alneenqid6w5/EhBQQcXklgecc5X2dwHR7/d67780094c2c7cfeaacd2935c2516854/screen-threat-neutralized1.png)
+![screen-threat-neutralized1](//images.ctfassets.net/alneenqid6w5/EhBQQcXklgecc5X2dwHR7/d67780094c2c7cfeaacd2935c2516854/screen-threat-neutralized1.png)
 
 ### Related Articles
 - [What is an anti-fraud solution?](https://help.vtex.com/en/tutorial/o-que-e-antifraude)
diff --git a/docs/tutorials/en/ready-to-dispatch.md b/docs/tutorials/en/ready-to-dispatch.md
index bfe29e6b4..78371256a 100644
--- a/docs/tutorials/en/ready-to-dispatch.md
+++ b/docs/tutorials/en/ready-to-dispatch.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Ready to dispatch'
 id: 5YOZV7Aotv3pap0fGNESDs
 status: PUBLISHED
 createdAt: 2021-11-11T20:13:17.128Z
-updatedAt: 2023-06-09T12:57:15.077Z
-publishedAt: 2023-06-09T12:57:15.077Z
+updatedAt: 2024-02-29T19:44:25.837Z
+publishedAt: 2024-02-29T19:44:25.837Z
 firstPublishedAt: 2021-11-11T20:44:13.846Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/received-skus-beta.md b/docs/tutorials/en/received-skus-beta.md
new file mode 100644
index 000000000..c5203bb96
--- /dev/null
+++ b/docs/tutorials/en/received-skus-beta.md
@@ -0,0 +1,224 @@
+---
+title: 'Received SKUs'
+id: 4hxDUmbgOEVFSTU2Eqi8DK
+status: PUBLISHED
+createdAt: 2024-04-29T13:48:12.818Z
+updatedAt: 2024-06-25T19:27:37.735Z
+publishedAt: 2024-06-25T19:27:37.735Z
+firstPublishedAt: 2024-04-29T14:16:25.091Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: received-skus-beta
+locale: en
+legacySlug: received-offers
+subcategory: 
+---
+
+The Received SKUs page provides a way for [marketplaces](https://help.vtex.com/en/tutorial/visao-geral-marketplace--40Zd0z9h2RXsM9uMUp3kEb) to view, prioritize, and catalog items sent by the sellers. This way, they can create new products and link them to existing SKUs or products to make them available for sale. You can access this page on the VTEX Admin by going to Marketplace > Received SKUs or typing Received SKUs in the Admin search bar.  
+
+Cataloging can be done manually or automatically [using one or more matchers](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) or [autoApprove](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions/#put-/suggestions/configuration/autoapproval/toggle). You can also use third-party tools to do this.  
+
+This article provides an overview in the sections [Page structure](#page-structure), [Cataloging priority](#cataloging-priority), and [Cataloging items](#cataloging-items).  
+
+## Page structure  
+
+The Received SKUs page is divided in tabs that correspond to the different offer statuses:  
+
+- [Pending](#pending)  
+- [Issues](#issues)  
+- [Approved](#approved)  
+- [Processing](#processing)  
+- [Blocked](#blocked)  
+
+Each tab displays a SKU list, offer SKU specifications, and the percentage of offers that have that status. Additionally, the tab has filter options that you can apply to the offers.  
+
+![received-skus-tabs-en](//images.ctfassets.net/alneenqid6w5/4jNrRvJsZgja1LuSz204P1/09fa16e993ba58dffa27b8809bb22c8f/received-skus-tabs-en.png)
+
+### Pending
+
+In the __Pending__ tab, you can see a list of all offers sent by a seller that haven't been approved yet. Offers can be filtered by __Seller, Category, Brand, and Inventory.__ Offer actions in this tab include: __Create new product, Link to product or SKU, Reject for correction, or Reject and block.__  
+
+Each row in the list represents a product and contains the following information:  
+
+- __Offer:__ Name of the product.  
+- __SKU ID:__ Identification number of the product.  
+- __Seller:__ Name of the seller who sent the offer.  
+- __Category:__ Category the product is linked to, if it's already mapped. Otherwise, it will show as Unmapped.  
+- __Price:__ Price of the product sent by the seller.  
+- __Inventory:__ Number of products available in stock.  
+
+To check all the specifications of a product, click the name of the product. This will open a window that contains all the product information.  
+
+![received-skus-tabs-en](//images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/ff94df985c2cc930548645ac0fbd5e98/received-skus-analyse-product-en.png)
+
+### Issues  
+
+The __Issues__ tab contains all the offers that haven't been approved because they have issues that need to be corrected by the seller. The filters, actions, and identification fields of the Issues tab are similar to the ones in the __[Pending](#pending)__ tab.  
+
+<div class="alert alert-info">
+ The <b>Issues</b> tab doesn't have the option to request a correction.
+</div>
+
+To identify the issue of an offer, simply click the name of the product. This will open a window with the product information, an error message, and the offer reviewer.  
+
+![received-skus-problems-tab](//images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/58d57ab4904c6794299855c91bfa6ef1/received-skus-problems-tab.png)
+
+### Approved  
+
+The __Approved__ tab shows the received and approved offers. You can __Edit the product, View the product page,__ and __Filter products by Seller, Category, and Brand.__
+
+Each row in the list represents a product and contains the following information:  
+
+- __Offer:__ Name of the product.  
+- __SKU ID:__ Identification number of the product.  
+- __Seller:__ Name of the seller who sent the offer.  
+- __Category:__ The category the product belongs to.  
+
+### Processing  
+
+The __Processing__ tab contains Received SKUs that are being evaluated by the VTEX system.  This is only a view tab. You can filter by __Seller__ and __Submitted Date.__
+
+Each row in the list represents a product and contains the following information:  
+
+- __Offer:__ Name of the product.  
+- __SKU ID:__ Identification number of the product.  
+- __Seller:__ Name of the seller who sent the offer.  
+- __Submitted Date:__ Date when the offer was sent to the marketplace.  
+
+<div class="alert alert-info">
+The offers in this tab are being evaluated by Matcher and Offer Quality or autoApprove, if they're configured. After evaluation, the offer can be sent to the <b>Pending, Issues, Approved, or Blocked</b> tabs, depending on the requirements.
+</div>
+
+### Blocked  
+
+In the __Blocked__ tab, you can see the offers that were sent by the seller that have been blocked by the marketplace. You can __Unblock__ an offer, as well as filter by __Seller__ or __Reviewer.__  
+
+Each row in the list represents a product and contains the following information:  
+
+- __Offer:__ Name of the product.  
+- __SKU ID:__ Identification number of the product.  
+- __Seller:__ Name of the seller who sent the offer.  
+- __Reviewer:__ Name of the agent that reviewed the offer.  
+
+## Cataloging priority  
+
+The Received SKUs list was developed to prioritize and streamline cataloging items. When you click any SKU in the list, you will see an overview of the SKU details in a sidebar, without leaving the list page. The sidebar also includes the match percentage assigned to the SKU by the matcher installed in your store.  
+
+Some features that help prioritization are:  
+
+### Filters  
+
+Each tab described in the section above allows combining filters to create a SKU view.  
+
+For example, if you select brand "ABC" and the "Socks" category, the view will display all SKUs of brand "ABC" that belong to the "Socks" category.  
+
+Keep in mind that filter options are based on the SKUs available in the list. Suppose, for example, that the marketplace is connected to Seller A, B, and C, but there are only pending SKUs from Seller B and C. This means that the applied filters in the [Pending](#pending) tab will only show results from Seller B and C.  
+
+### Sorting  
+
+By default, the items that were submitted most recently are displayed at the top. However, you can also sort them by __Price__ and __Inventory__.  
+
+In this case, the items will be sorted in ascending or descending order when you click the __Price__ or __Inventory__ column headers.  
+
+![received-skus-ord-en](//images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/585afe9679294087fe9351cea7f0799a/received-skus-ord-en.png)
+
+## Cataloging items  
+
+All the SKUs displayed in the list are available for cataloging. However, we recommend [mapping the categories and brands](https://help.vtex.com/pt/tutorial/mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta--6NU8LwR6i0tTb8nk30bnbE) before this step to streamline the cataloging process.  
+
+<div class="alert alert-warning">
+The offers in the Pending tab are only available for 30 days. After this period, they automatically expire and the seller will need to submit them again.
+</div>
+
+### Cataloging options
+
+To catalog an offer, access the __Received SKUs__ page on the VTEX Admin by going to __Marketplace > Received SKUs__ or typing __Received SKUs__ in the Admin search bar.  
+
+<div class="alert alert-info">
+All the offers on the Pending tab can be cataloged individually or in bulk.
+</div>
+
+The available cataloging actions are:  
+
+- __Create new product:__ Creates a new SKU in the catalog and, consequently, a new product. We recommend using this option when a product doesn't exist in the marketplace catalog. To apply this action, follow the steps below:  
+
+1. 	Select the desired SKUs.  
+2. 	Click the <i class="fas fa-plus" aria-hidden="true"></i> Create new product button.  
+3. 	Complete the Category and Brand fields for each product. If the mapping was previously completed, the fields will be filled automatically.  
+4. 	Click `Approve`.  
+
+<div class="alert alert-info">
+This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
+</div>
+
+![received-skus-create-new-product-en](//images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/2d18fb18e7711cb4cd341795ac0820b4/received-skus-create-new-product-en.png)
+
+- __Link to an existing product:__ Creates a relationship between the seller product and a product in the marketplace catalog. To apply this action, follow the steps below:  
+
+1. 	Select the desired SKUs.  
+2. 	Click the <i class="fas fa-link" aria-hidden="true"></i> Link to product button.  
+3. 	Enter the product ID you want to associate them with.  
+4. 	Click `Approve`.  
+
+#### Use case  
+
+Imagine that a marketplace already has the White Shirt SKU in S, M, and L, and a seller recently submitted sizes XS and XL for the same White Shirt.  
+
+Creating a new link groups the new sizes with the existing ones. After this, the product will have XS, S, M, L, and XL as available sizes.  
+
+<div class="alert alert-info">
+This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
+</div>  
+
+![received-skus-bind-to-product-en](//images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/fc02d18fe2771b0603f861f8516ab7ae/received-skus-bind-to-product-en.png)
+
+- __Link to an existing SKU:__ Creates a relationship between the new seller SKU and a SKU in the marketplace catalog. To apply this action, follow the steps below:  
+
+1. 	Select the desired products.  
+2. 	Click the <i class="fas fa-link" aria-hidden="true"></i>Link to SKU button.  
+3. 	Enter the SKU ID that you want to link for each SKU you're approving.  
+4. 	Click `Approve`.  
+
+#### Use case  
+
+A possible use case would be a marketplace that has Phone XYZ with a 128 GB memory from Seller 1.  
+
+Now, let's say the marketplace received the same 128 GB SKU from Seller 2. To avoid duplicates in the catalog, the marketplace would have to link these two SKUs.  
+
+<div class="alert alert-info">
+This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
+</div>
+
+![received-skus-bind-to-sku-en](//images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/8bc6c9b98e03afe02252bd69342005d1/received-skus-bind-to-sku-en.png)
+
+- __Block:__ Blocks the selected offers. This will prevent them from being automatically processed again. To apply this action, follow the steps below:  
+
+1. 	Select the desired products.
+2. 	Click the `Reject and block` button.
+3. 	Complete the __Block reason__ field. This field is optional.
+4. 	Click `Reject`.  
+
+When the marketplace blocks a SKU, it won't be included with other submitted offers the next time that the seller sends products. A SKU can be unblocked using a REST API if the marketplace wants to receive it as a suggestion from the seller. To learn more about SKU approval, see [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).  
+
+<div class="alert alert-info">
+This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>. Blocked offers can be viewed in the <b>Blocked</b> tab.
+</div>
+
+![received-skus-reject-and-block-en](//images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/247d5dcfb554755d091b1367d84db2d5/received-skus-reject-and-block-en.png)
+
+- __Reject for correction:__ Rejects the offer and sends an information correction request to the seller. To apply this action, follow the steps below:  
+
+1. 	Select the desired SKUs.  
+2. 	Click the __Reject for correction__ button.  
+3. 	Enter the information that needs correction in the Corrections field.  
+4. 	Click Reject.  
+
+<div class="alert alert-info">
+	<p>This action can be applied in the offer tab <b>Pending</b>. The offers that need correction will show in the <b>Issues</b> tab.</p>
+</div>  
+
+![received-skus-reject-for-correction-en](//images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/7d456cf95d5a4ed7011accdfe0550fba/received-skus-reject-for-correction-en.png)
+
+- __Automatic approval:__ You can also set up automatic approval for SKUs from a specific seller regardless of their Matcher score. This action can only be applied through a REST API. To learn more, see [Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions).  
+
diff --git a/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
new file mode 100644
index 000000000..c57d0f9d1
--- /dev/null
+++ b/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -0,0 +1,116 @@
+---
+title: 'Recovering abandoned checkouts with WhatsApp AI Campaigns'
+id: 20i0zLQHt72LKzVEmk1CRZ
+status: PUBLISHED
+createdAt: 2024-06-25T11:27:41.160Z
+updatedAt: 2024-06-25T16:27:45.935Z
+publishedAt: 2024-06-25T16:27:45.935Z
+firstPublishedAt: 2024-06-25T15:29:15.011Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: recovering-abandoned-checkouts-with-whatsapp-ai-campaigns
+locale: en
+legacySlug: recovering-abandoned-checkouts-with-whatsapp-ai-campaigns
+subcategory: 4SC2gPmUH3cHD5HjGfQ5Vg
+---
+
+WhatsApp AI Campaigns is a feature developed by VTEX to recover abandoned checkouts.
+
+When a user leaves the payment page, the platform identifies this action. If the user does not return to complete the order within 1 hour, the feature sends them a notification via WhatsApp.
+
+The main advantages of this feature are:
+
+- **Improved customer experience:** Messages can be personalized to increase relevance and strengthen the relationship with the brand.
+
+- **Increased conversion rates and sales:** The feature encourages customers to return to the payment page to complete their purchase, thereby increasing sales and conversion rates for retailers.
+
+<div class = "alert alert-info">
+WhatsApp AI Campaigns is only available for stores using <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> that don't have Checkout customizations.
+</div>
+
+## Activating WhatsApp AI Campaigns
+
+To activate the WhatsApp AI Campaigns feature, you must [install the Connectly app](#installing-conectly-app) and then [configure a WhatsApp number in the app](#configuring-new-whatsapp-number).
+
+### Installing the Connectly app
+
+To install the Connectly app, follow the steps below:
+
+1. Go to VTEX [App Store](https://apps.vtex.com/).
+
+2. Type Connectly in the search bar.
+
+3. Click Connectly app, then click `Get App`.
+
+4. Click `Place Order`.
+
+5. Click `Go to Install Page', and you will be redirected to the Apps section in the VTEX Admin.
+
+6. On the Connectlyvtex app installation page, click `Install`.
+
+7. Click `Save`.
+
+### Configuring a new WhatsApp number
+
+To configure a new WhatsApp number, you need to have admin access to your Facebook profile. Follow these steps to configure a new number and link it:
+
+<div class = "alert alert-info">
+We recommend creating a new phone number exclusively for linking to WhatsApp Business. This helps to avoid losing access to numbers previously used for other purposes.
+</div>
+
+<ol start="1">
+  <li>In the VTEX Admin, go to <strong>Promotions &gt; WhatsApp Campaigns &gt; Overview</strong>, or type <strong>WhatsApp Campaigns Overview</strong> in the search bar at the top of the page.</li>
+  <li>Click <code>Configure Account</code>.</li>
+  <li>Select <strong>Yes, I want a free number (recommended)</strong>, and click <code>Next</code>.</li>
+  <li>Copy the phone number provided, and click <code>Connect</code> to link this number to your Meta for business account.</li>
+  <li>Click <code>Continue as User</code>.</li>
+  <li>Click <code>Get Started</code>.</li>
+  <li>Confirm that the <strong>Business Portfolio</strong>, <strong>Company Name</strong>, <strong>Website</strong>, or <strong>Company Business Profile</strong> and <strong>Country</strong> information is correct.</li>
+  <li>Click <code>Next</code>.</li>
+</ol>
+
+<p>Creating a WhatsApp Business account:</p>
+
+<ol start="9">
+  <li>Select <strong>Create new WhatsApp Business account</strong> and <strong>Create a new WhatsApp Business profile</strong>.</li>
+  <li>Click <code>Continue</code>.</li>
+  <li>Complete the fields below:
+    <ul>
+      <li><strong>WhatsApp Business account name (internal)</strong>, for example: VTEX Store name.</li>
+      <li><strong>WhatsApp Business display name (visible to customers)</strong>, for example: Store name.</li>
+      <li><strong>Category</strong>.</li>
+      <li>Click <code>Continue to Step 3</code></li>
+    </ul>
+  </li>
+  <li>Paste the phone number you copied in the previous step, select the option <strong>SMS</strong>, and click <code>Send Code</code>.</li>
+</ol>
+
+<div class="alert alert-warning">
+  The number generated may be American, but if your Facebook page is verified, your customers will see your company name. If it is not verified, we recommend following the <a href="https://www.facebook.com/business/help/2058515294227817?id=180505742745347">verification process with Meta</a>.
+</div>
+
+<ol start="13">
+  <li>Copy the verification code displayed in the VTEX Admin.</li>
+  <li>Paste the verification code in the field within the Facebook popup, and click <code>Verify</code>.</li>
+  <li>Click <code>OK</code>.</li>
+  <li>Click <code>Complete</code>.</li>
+  <li>Choose a 400x400 px logo for your new WhatsApp number. The image does not need to be high resolution.</li>
+</ol>
+
+<p>Accepting the terms and conditions:</p>
+
+<ol start="18">
+  <li>Review the Terms and Conditions.</li>
+  <li>Click <code>I Agree and Accept</code>.</li>
+  <li>Click <code>Complete</code>.</li>
+</ol>
+
+<div class="alert alert-warning">
+Once an abandoned checkout recovery campaign has been activated, it can take up to 48 hours for analytics metrics to start being displayed.
+</div>
+
+<div class = "alert alert-info">
+Learn more about <a href="https://help.vtex.com/en/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">WhatsApp AI Campaigns management and details</a>.
+</div>
+
diff --git a/docs/tutorials/en/redirect-from-other-addresses.md b/docs/tutorials/en/redirect-from-other-addresses.md
new file mode 100644
index 000000000..4d3cc2448
--- /dev/null
+++ b/docs/tutorials/en/redirect-from-other-addresses.md
@@ -0,0 +1,81 @@
+---
+title: 'Redirect from other addresses'
+id: 3Xi2AeLUx2QpJQu8DTX8KQ
+status: PUBLISHED
+createdAt: 2022-09-19T21:21:24.455Z
+updatedAt: 2024-01-23T18:16:55.386Z
+publishedAt: 2024-01-23T18:16:55.386Z
+firstPublishedAt: 2022-09-19T21:40:22.913Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: redirect-from-other-addresses
+locale: en
+legacySlug: 
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+An online store must have a single main address [pointing to VTEX's servers](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ) before the store is officially launched. Read the [Configuring the store domain](https://help.vtex.com/en/tutorial/configure-the-store-domain--tutorials_2450) article to understand the rules the address must comply with and the process for adding it.
+
+To allow access to the store through other addresses and versions without a subdomain, you need to configure these addresses to redirect to the store's main address, which is listed in **Account settings > Account > Stores** in the VTEX Admin. See examples below:
+
+| Address | Type |
+|---|---|
+| `www.mystore.com ` | Main domain |
+| `www.previousaddress.com ` | Redirect |
+| `mystore.com `  | Redirect |
+
+## Configuring redirects
+
+You can configure redirects in different ways; one of the most popular is using[ htaccess](https://developer.mozilla.org/en-US/docs/Learn/Server-side/Apache_Configuration_htaccess) on the server. You can also use a DNS redirect from many services, including domain providers such as [domain.com](http://domain.com/).
+
+Below are instructions for setting up redirects to your store's main address using the [Redirect Center](http://redirect.center/) tool.
+
+<div class="alert alert-warning">
+  <p><a href="http://redirect.center/">Redirect Center</a> is not a service provided by VTEX and does not support HTTPS. While there are other similar services available, VTEX does not endorse any specific one. VTEX is not liable for any issues caused by external redirect services.</p>
+</div>
+
+### Address redirects without a subdomain (such as www)
+
+To visit your store from an address without subdomains, such as `www`, you need to create a redirect to your store's main address. For example, to access `http://www.mysite.com` from the address without a subdomain `http://mysite.com`, you need to create a redirect in your DNS provider by following the instructions below:
+
+1.	Create an A record for the domain root, usually represented by `.`, `@`, or just `mysite.com`, pointing to `54.84.55.102` ([Redirect Center's](http://redirect.center/) IP).
+
+   |   |   |   |
+   |---|---|---|
+   | Host Record: <leave-empty\> | Type: A | To: 54.84.55.102 |
+
+2. Create a `redirect` CNAME record (or `redirect.mysite.com`) pointing to `www.mysite.com.redirect.center.com`.
+
+  |   |   |   |
+  |---|---|---|
+  | Host Record: redirect | Type: CNAME | To: www.mysite.com.redirect.center.com |
+
+Learn more about such situations in [Best practices for accessing the store without www](https://help.vtex.com/en/tutorial/best-practices-for-accessing-the-store-without-www--tutorials_4278).
+
+Depending on the DNS provider, redirect propagation may take a few minutes to complete.
+
+### Redirecting from one address to another
+
+To redirect from one address to another that doesn't share the same domain root, create a CNAME entry in the old address (access origin), following the pattern `{newAddress}.opts-uri.redirect.center.com`.
+
+For example, to redirect from `www.previousdomain.com` to `www.newdomain.com`:
+
+* Create a `www` entry in the domain `previousdomain.com` with the CNAME `www.newdomain.com.opts-uri.redirect.center.com`.
+
+To redirect from `store.anaddress.com` to `www.site.com`:
+
+*	Create a `store` entry in the `anaddress.com` domain with the CNAME `www.site.com.opts-uri.redirect.center.com`.
+
+### Redirecting access with HTTPS
+
+VTEX automatically directs `http://` addresses to `https://`. However, it may still be necessary to redirect an `https://` address, such as a version of the address without a subdomain or one with a different domain, to an `https://` address.
+
+When accessing an HTTPS page, the server responding to the address must have an SSL certificate installed. Not having an SSL certificate means the browser will recognize the connection as not secure and block the request. This prevents access to the desired page and makes it impossible to redirect to a different address.
+
+In [Redirect Center](http://redirect.center/), you cannot install an SSL certificate for each domain you point to. Therefore, it does not redirect accesses coming from HTTPS.
+
+To deal with this limitation, consider the following aspects:
+
+1. If the source domain does not have a subdomain, such as `site.com`, point it to a server managed by the store itself, i.e., a physical or virtual server managed by the user or company itself. This server must have an **SSL certificate installed for the source domain**, enabling secure access via HTTPS. Read the[ Security certificate (SSL)](https://help.vtex.com/en/tutorial/hiring-the-security-certificate-sll--tutorials_1308) article for more information.
+2. Define a **redirect rule**. To use a self-managed server to redirect HTTPS traffic, you must define a redirect rule on the server, which can vary depending on the type of server used (Apache, ASP, nginx). Therefore, to configure this rule, you must know which server type is being used and apply the corresponding settings.
diff --git a/docs/tutorials/en/redirects.md b/docs/tutorials/en/redirects.md
new file mode 100644
index 000000000..2023a30d1
--- /dev/null
+++ b/docs/tutorials/en/redirects.md
@@ -0,0 +1,41 @@
+---
+title: 'Redirects'
+id: 3okF84cImJwKzcc8hxmZ2r
+status: PUBLISHED
+createdAt: 2024-06-27T17:04:44.975Z
+updatedAt: 2024-06-27T17:05:31.676Z
+publishedAt: 2024-06-27T17:05:31.676Z
+firstPublishedAt: 2024-06-27T17:05:31.676Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: redirects
+locale: en
+legacySlug: redirects
+subcategory: 1wvyJwJhKgewxGeAGCVmM6
+---
+
+The **Redirects** feature directs customers to another page, either internal or external to the store. This redirection is done in the search area of your storefront, using terms or filters selected by the customer. This way, one of the advantages of the Redirects feature is to contemplate communication scenarios that are not covered by the store's catalog search, such as redirecting a search for a brand to its promotional page.
+
+<div class="alert alert-warning">
+<p>This feature is available in VTEX Intelligent Search: Multilanguage. To learn more, please refer to our article VTEX Intelligent Search: Multilanguage settings (Beta).</p>
+</div>
+
+## How redirects work
+
+When creating a redirect, you also need to create conditions, called rules. They must contain a set of registered terms and filters. The number of rules per redirect is unlimited.
+
+With this feature, you can create rules that contemplate both the interests of the manager and the final customer. Other benefits are:
+
+- Increasing the search possibilities for the website. Searches without results statistically generate a bounce rate, which is the percentage of visitors who enter an ecommerce website and leave without seeing other pages.
+- Facilitating the end-customer's usability, as in post-purchase situations or promotional actions.
+
+Once the customer performs a search, VTEX Intelligent Search captures the search term and checks if there is a redirection rule related to that search.
+
+The search term is eligible when there is at least one existing rule for it. This redirects the client to the registered URL.
+
+If the customer searches for "my orders" or "orders", you can create a redirect that directs them to the orders in their account instead of displaying an empty search page.
+
+You can also configure the tool to redirect the customer to a landing page for specific promotions. In this case, if the customer searches for "Black Friday", they will be redirected to the promotion.
+
+In another scenario, if the customer searches for "running shoes" and filters for the brand Nike, they will be redirected to a dedicated page for the brand.
diff --git a/docs/tutorials/en/registered-ticket-flow.md b/docs/tutorials/en/registered-ticket-flow.md
index 116ac4201..b94950b9b 100644
--- a/docs/tutorials/en/registered-ticket-flow.md
+++ b/docs/tutorials/en/registered-ticket-flow.md
@@ -23,7 +23,7 @@ Here's how the basic flow of a registered ticket payment works. The flow is divi
  
 ## Ticket Issue
 
-![processo-boleto-registrado-en ex 2](https://images.ctfassets.net/alneenqid6w5/3QIX0MyLCgqcmcsGgEAwsU/e7530c4c911dd93a995425db4a9e5fff/paint_bank_en_2.png)
+![processo-boleto-registrado-en ex 2](//images.ctfassets.net/alneenqid6w5/3QIX0MyLCgqcmcsGgEAwsU/e7530c4c911dd93a995425db4a9e5fff/paint_bank_en_2.png)
 
 1. Your __e-commerce__ informs the __Gateway__ that an order will be paid via registered ticket.
 2. The gateway contacts the __Bank__ to register the ticket.
@@ -35,7 +35,7 @@ At this time, the ticket has not yet been paid by the customer.
 
 ## Ticket Payment and Bank Reconciliation
 
-![processo-boleto-registrado-en ex 1](https://images.ctfassets.net/alneenqid6w5/1c6VvblROiioeMmacWkuii/37a83bad6931c6ae6a8fa89a5b773127/paint_bank_en.png)
+![processo-boleto-registrado-en ex 1](//images.ctfassets.net/alneenqid6w5/1c6VvblROiioeMmacWkuii/37a83bad6931c6ae6a8fa89a5b773127/paint_bank_en.png)
 
 1. the __Client__ pays the ticket directly to the __Bank__.
 2. The bank sends the [bank reconciliation](/en/tutorial/bank-reconciliations) files to the __Gateway__ with information on the tickets payment status.
diff --git a/docs/tutorials/en/registering-a-category.md b/docs/tutorials/en/registering-a-category.md
index 8c18de7c0..724db174c 100644
--- a/docs/tutorials/en/registering-a-category.md
+++ b/docs/tutorials/en/registering-a-category.md
@@ -3,8 +3,8 @@ title: 'Registering a category'
 id: tutorials_206
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:39.383Z
-updatedAt: 2023-03-29T17:45:06.786Z
-publishedAt: 2023-03-29T17:45:06.786Z
+updatedAt: 2023-11-29T19:10:35.853Z
+publishedAt: 2023-11-29T19:10:35.853Z
 firstPublishedAt: 2017-04-27T23:00:46.516Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -38,4 +38,4 @@ Follow the instructions below to create a category:
 - [Fill in category registration fields](/en/tutorial/category-registration-fields)
 - [Cleaning store's data base](/en/tutorial/understanding-how-to-maintain-a-database)
 - [Registering a product](/en/tutorial/registering-a-product)
-- [Registering an SKU](/en/tutorial/registering-sku)
+- [Registering an SKU](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ)
diff --git a/docs/tutorials/en/registering-brands.md b/docs/tutorials/en/registering-brands.md
index b6b694dad..f3e75fe65 100644
--- a/docs/tutorials/en/registering-brands.md
+++ b/docs/tutorials/en/registering-brands.md
@@ -23,4 +23,4 @@ To register a brand, follow these steps:
 4. Fill in the [Brand registration fields](https://help.vtex.com/en/tutorial/brand-registration-fields--37Ky7lTbEkiWIAYA80EMyI).
 5. Click on `Save`.
 
-![ENcadastrarmarcas3.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
+![ENcadastrarmarcas3.PNG?h=250](//images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
diff --git a/docs/tutorials/en/registering-gateway-affiliations.md b/docs/tutorials/en/registering-gateway-affiliations.md
index dfe5f73d9..b2dedecb1 100644
--- a/docs/tutorials/en/registering-gateway-affiliations.md
+++ b/docs/tutorials/en/registering-gateway-affiliations.md
@@ -1,10 +1,10 @@
 ---
-title: 'Registering gateway affiliations'
+title: 'Register payment and anti-fraud providers'
 id: tutorials_444
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:18.209Z
-updatedAt: 2023-03-21T20:55:24.198Z
-publishedAt: 2023-03-21T20:55:24.198Z
+updatedAt: 2024-01-22T20:37:11.273Z
+publishedAt: 2024-01-22T20:37:11.273Z
 firstPublishedAt: 2017-04-27T23:03:24.823Z
 contentType: tutorial
 productTeam: Financial
@@ -15,28 +15,81 @@ legacySlug: registering-gateway-affiliations
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A gateway affiliation is a set of configurations that represent your contract with a payment provider (gateway, acquirer, or subacquirer). 
+VTEX allows you to set up different providers: gateways, acquirers, sub-acquirers, [orchestrators](https://www.y.uno/br), [PSPs](https://en.wikipedia.org/wiki/Payment_service_provider), and more. These allow you to provide your customers with different payment methods and conditions and antifraud protection services. Previously, these settings were referred to in our system as "gateway providers".
 
-At VTEX, you can configure many payment providers and offer different payment methods and conditions to your customers.
+The provider management screen allows you to:
 
-To set up a gateway affiliation, follow the steps below:
+- [Add new providers](#adding-providers)
+- [View added providers](#viewing-added-providers)
+- [Edit provider settings](#editing-provider-settings)
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
+![interface_provedor_EN_1](//images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/7a033eb73b124608c07471301501da64/artigo_interface_provedor_EN_1.jpg)
+
+## Adding providers
+
+To add a new payment or antifraud provider to your store, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payments > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. Click `New Provider`.
 3. Click on your preferred payment provider.
-4. Fill in the __Application Key__ and __Application Token__ fields with the information provided by the payment provider.
-5. If an alert message appears indicating the need to install the app, click on the __Install app__ button and follow the installation instructions. This message is only displayed for some types of gateway affiliations. 
-6. Click on __Save__.
+4. Complete the __App key__ and __App token__ fields with the information supplied by the payment provider.
+5. If a warning message is displayed indicating that you need to install the app, click the __Install App__ button and follow the installation instructions. This message is only displayed for some gateway provider types. 
+6. Click `Save`.
 
 <div class = "alert alert-info">
-  <p>If there are other fields to be filled in besides the <b>Application Key</b> and <b>Application Token</b> (Step 6), the gateway affiliation must be configured according to the specific tutorial. For more information, check the subsection <a href="https://help.vtex.com/en/subcategory/configuracoes-de-pagamentos--3tDGibM2tqMyqIyukqmmMw">Payment Settings</a>.</p>
+  <p>If there are other fields to be completed besides App key and App token (Step 6), the gateway provider must be configured according to the specific tutorial. For more information, see the <a href="https://help.vtex.com/en/subcategory/payment-settings--3tDGibM2tqMyqIyukqmmMw">Payment Settings</a> subsection.</p>
 </div>
 
 <div class = "alert alert-danger">
-The payment provider must provide the credentials used to populate the <strong>Application Key</strong> and <strong>Application Token</strong> fields to identify the store. No <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet">credentials generated in the Admin</a>, which start with <code>vtexappkey-</code>, should be used.
+The credentials used to complete the App key and Appn token fields must be supplied by the payment provider to identify the store. <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet">Credentials generated in the Admin</a> starting with <code>vtexappkey-</code> should be used.
 </div>
 
-To configure the payment methods to be processed by the chosen payment provider, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
+To configure the payment methods that will be processed by your chosen payment provider, read [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455).
+
+To set special conditions for payment methods, read [Configuring payment special  conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+
+![interface_provedor_EN_2](//images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/06ebd4ed620be2fd6a2ea7f3b61e25e7/artigo_interface_provedor_EN_2.JPG)
+
+## Viewing added providers
+
+The main provider management screen, available in the VTEX Admin under __Store Settings > Payments > Providers__, displays all the payment or antifraud providers in a store. To allow quick access to information on specific providers, you can search or use filters.
+
+### Searching for providers
+
+To search for providers by name, go to the provider management page and enter the name of the provider you want to find.
+
+![interface_provedor_EN_3](//images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/1c93dc9bbf26acf87e54224c5471407f/artigo_interface_provedor_EN_3.JPG)
+
+### Filtering providers
+
+To select the providers using filters, go to the provider management page and apply one or more of the filters shown below:
+
+- __Name__: Select the payment provider using the name by checking the box or using the menu search bar.
 
-To set special conditions on payment methods, go to [Configuring payment special  conditions](https://help.vtex.com/en/tutorial/conditiones-especiales--tutorials_456?&utm_source=autocomplete).
+![interface_provedor_EN_4](//images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/c5e5aa3880b070e45a891d477906b78d/artigo_interface_provedor_EN_4.JPG)
+
+- __Type__: Select to display payment providers, antifraud providers, or both.
+
+![interface_provedor_EN_5](//images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/2dde50a266e104a6f1652e7d7294d560/artigo_interface_provedor_EN_5.JPG)
+
+- __Environment__: Select the providers by type of operating environment (production or test).
+
+![interface_provedor_EN_6](//images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/bb0b07f72dac4a7b01f5e94aa388899c/artigo_interface_provedor_EN_6.JPG)
+
+<div class = "alert alert-danger">
+To clear the applied filters and see all the providers in the store again, click the <code>Clear All</code> button.</div>
+
+## Editing provider settings
+
+To edit the settings of existing payment or antifraud providers in the store, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payments > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. Click the desired payment or antifraud provider.
+3. On the provider configuration screen, click `Edit`.
+4. Make the necessary changes and click `Save`.
+
+![interface_provedor_EN_7](//images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/6dffc24a68b01dd43309f119907ed1d0/artigo_interface_provedor_EN_7.JPG)
+
+<div class = "alert alert-danger">
+Before changing the provider's settings, such as authorization details, processing mode, or refund type, ensure the new information entered will not affect your store's performance.</div>
 
diff --git a/docs/tutorials/en/registering-geolocation.md b/docs/tutorials/en/registering-geolocation.md
index 8aae26bd4..65eb3c308 100644
--- a/docs/tutorials/en/registering-geolocation.md
+++ b/docs/tutorials/en/registering-geolocation.md
@@ -3,8 +3,8 @@ title: 'Registering geolocation'
 id: tutorials_138
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:36.462Z
-updatedAt: 2023-03-29T13:25:16.724Z
-publishedAt: 2023-03-29T13:25:16.724Z
+updatedAt: 2023-08-25T14:52:20.340Z
+publishedAt: 2023-08-25T14:52:20.340Z
 firstPublishedAt: 2017-04-27T23:00:44.871Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -32,6 +32,10 @@ Access the [Generate your polygons with geojson.io](http://geojson.io/#map=2/20.
 
 This JSON will be used to add the polygon to the platform, that will translate that language to understand which Zip Codes are included in your area.
 
+<div class="alert alert-danger">
+When generating a polygon, it is not possible to delimit overlapping areas, meaning it is not possible to overlap geographic coordinates.
+</div>
+
 ## How to add a polygon
 
 When adding a polygon, name it in a way it can be identified later on the freight spreadsheet, enabling consultation by Zip Code.
diff --git a/docs/tutorials/en/registering-the-skus-barcode-for-vtex-sales-app.md b/docs/tutorials/en/registering-the-skus-barcode-for-vtex-sales-app.md
index 4bb0cee3c..eee74fd45 100644
--- a/docs/tutorials/en/registering-the-skus-barcode-for-vtex-sales-app.md
+++ b/docs/tutorials/en/registering-the-skus-barcode-for-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Registering the SKUs barcodes for VTEX Sales App'
 id: 2jkOdRB4XSMG2ke0uUQIKS
 status: PUBLISHED
 createdAt: 2018-03-12T17:23:32.837Z
-updatedAt: 2023-05-31T16:11:54.350Z
-publishedAt: 2023-05-31T16:11:54.350Z
+updatedAt: 2023-07-26T19:04:52.107Z
+publishedAt: 2023-07-26T19:04:52.107Z
 firstPublishedAt: 2018-03-12T17:27:18.421Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
index 6226e7d03..9657b8aec 100644
--- a/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -20,7 +20,7 @@ When you create a [regular promotion](https://help.vtex.com/en/tutorial/regular-
 
 By selecting this type of discount, you need to create a formula defining how the applied discount will be calculated. In this article, we’ll explain how to build a formula which meets your promotion's objectives.
 
-![discount-type-formula](https://images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/c7e753bddc57ad9ec18b30f05f654688/desc.PNG)
+![discount-type-formula](//images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/c7e753bddc57ad9ec18b30f05f654688/desc.PNG)
 
 The formula used to calculate the nominal discount generally follows the same logic as the [Microsoft Excel formulas](https://support.microsoft.com/pt-br/office/f%C3%B3rmulas-e-fun%C3%A7%C3%B5es-294d9486-b332-48ed-b489-abe7d0f9eda9), which means you can use [variables](#variables) (`total`, `freight` and `quantity`), make [operations](#operations) (sum, subtraction, multiplication and division) and apply (`min` and `max` [functions](#functions).
 
@@ -79,19 +79,19 @@ The promotion will apply the lowest discount in each case, comparing the 20% cal
 
 A customer added a $ 45 item to the cart. By calculating 20% of the total price, the result is 9, as per `total * 0.2 = 9`. Since 9 is below the discount limit value, the applied discount will be $ 9.
 
-![scenario1-en](https://images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/7cedfaa3ffa9b54192807f47a4b1fe18/scenario1-en.png)
+![scenario1-en](//images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/7cedfaa3ffa9b54192807f47a4b1fe18/scenario1-en.png)
 
 #### Scenario 2
 
 Another customer added a $ 2600 item to the cart. By calculating 20% of this amount, the result is 520, as per `total * 0.2 = 520`. Since this value is above the limit ($ 10), the discount will be $ 10.
 
-![scenario2-en](https://images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/7bd025f1787a20a9fdc1332c54e73568/scenario2-en.png)
+![scenario2-en](//images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/7bd025f1787a20a9fdc1332c54e73568/scenario2-en.png)
 
 #### Scenario 3
 
 A third customer added two items to the cart: One costs $ 100 and the other $ 2600. Their sum is $ 2700, as per `total = 2700`. By calculating 20% of the total amount, the result is 540, according to `total * 0.2 = 540`. Since this value is above the limit ($ 10), the applied discount will be $ 10.
 
-![scenario3-en](https://images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/11a3e761ff2194ad9e63ee9a575cd62c/scenario3-en.png)
+![scenario3-en](//images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/11a3e761ff2194ad9e63ee9a575cd62c/scenario3-en.png)
 
 The total discount of $ 10 is proportionally distributed among the items, based on each item's price and quantity. The platform makes this distribution automatically, as explained below.
 
diff --git a/docs/tutorials/en/regular-promotion-with-reward-value.md b/docs/tutorials/en/regular-promotion-with-reward-value.md
index 759ae67be..cca5d3560 100644
--- a/docs/tutorials/en/regular-promotion-with-reward-value.md
+++ b/docs/tutorials/en/regular-promotion-with-reward-value.md
@@ -38,7 +38,7 @@ The **nominal reward value** adds a fixed credit amount to the user's account in
 
 In the following example, the customers will earn R$10,00 in store credit when the order status changes to **Invoiced**.
 
-![vf-nominal-en](https://images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/fc3a24297d99657c141f3b8d295f6f69/vf-nominal-en.png)
+![vf-nominal-en](//images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/fc3a24297d99657c141f3b8d295f6f69/vf-nominal-en.png)
 
 ### Percentage reward value
 
@@ -49,7 +49,7 @@ The **percentage reward value** adds a percentage credit amount based on the pri
 
 In the following example, customers will earn 20% of the purchase value when the order status changes to **Payment Approved**.
 
-![vf-percentual-en](https://images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4b8f2e869e868607f53e9d8dae42b175/vf-percentual-en.png)
+![vf-percentual-en](//images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4b8f2e869e868607f53e9d8dae42b175/vf-percentual-en.png)
 
 ## How to set up restrictions
 
@@ -85,19 +85,19 @@ When a customer places an order which is eligible to receive a reward credit, yo
 
 The name of the promotion applied to the order appears in the **Sales and marketing** section:
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/708046486a825d2d2ec3c40ec20a9da2/detalhes-oms-en.png" alt="order-details" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/708046486a825d2d2ec3c40ec20a9da2/detalhes-oms-en.png" alt="order-details" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
 </em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/6acf4788ee8432dbfb24d7d790197022/detalhes-neworders-en.png" alt="order-details-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/6acf4788ee8432dbfb24d7d790197022/detalhes-neworders-en.png" alt="order-details-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Order details
  (Beta)</em></figcaption></figure>
 
 In the **Order flow** section, you can check the reward value applied:
 
-![fluxo-oms-en](https://images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/cd08683f3137aa01fd0e88138865a36e/fluxo-oms-en.png)
+![fluxo-oms-en](//images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/cd08683f3137aa01fd0e88138865a36e/fluxo-oms-en.png)
 
 If you use the new [Order details (Beta)](https://help.vtex.com/en/tutorial/order-details-page-beta--2Y75n54Cc9VizrlG1N6ZNl) interface, go to `See interactions` to check the applied value:
 
-![interacoes-neworders-en](https://images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/111404a4067208154e3eb05fe28df3aa/interacoes-neworders-en.png)
+![interacoes-neworders-en](//images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/111404a4067208154e3eb05fe28df3aa/interacoes-neworders-en.png)
 
 Consider that the promotion applied to the order illustrated offers a **percentage reward value** of **50%**. Therefore, the client earned a credit of `R$ 54.28` for  future purchases, which is equivalent to **50%** of `R$ 108.55`, the total value of the order.
 
@@ -105,13 +105,13 @@ Consider that the promotion applied to the order illustrated offers a **percenta
 
 The reward value available for use is displayed to your store customers at the **Payment** stage during checkout, as shown below.
 
-![checkout-pt (1)](https://images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
+![checkout-pt (1)](//images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
 
 The applied value can be used to calculate the payment. To do so, the customer must click on `use credit` and then enter the value they want to use.
 
 Note that the value will be discounted from the other method of payment selected. In the following example, the _boleto_ shows the amount of `R$ 113.50`, which corresponds to `R$ 167.80` minus the reward value used (`R$ 54.30`).
 
-![checkout-2-pt (1)](https://images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
+![checkout-2-pt (1)](//images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
 
 ## Learn more
 
diff --git a/docs/tutorials/en/regular-promotion.md b/docs/tutorials/en/regular-promotion.md
index a9896a6d4..657e11de0 100644
--- a/docs/tutorials/en/regular-promotion.md
+++ b/docs/tutorials/en/regular-promotion.md
@@ -1,10 +1,10 @@
 ---
 title: 'Regular Promotion'
 id: tutorials_327
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-04-27T22:07:59.690Z
-updatedAt: 2022-12-08T19:33:36.098Z
-publishedAt: 2022-08-23T19:50:18.784Z
+updatedAt: 2024-05-15T16:38:18.730Z
+publishedAt: 2024-05-15T16:38:18.730Z
 firstPublishedAt: 2017-04-27T23:03:15.647Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -89,7 +89,7 @@ For the promotion to be valid for all sales policies, leave the checkboxes empty
 
 In this section, you need to choose whether this promotion will apply to all products in your store or only to specific products, as illustrated below.
 
-![promocoes-restricao-en](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
+![promocoes-restricao-en](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
 
 If you want the promotion to apply to your entire catalog, select the **Apply to all products** option.
 
@@ -99,7 +99,7 @@ You can add or remove **Categories**, **Brands**, **Collections**, **Products**
 
 See an example below. In this case, the promotion includes all products from the category **Home Appliances** whose brand is **Brastemp**, except the product **Refrigerator 100**.
 
-![exemplo-en](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
+![exemplo-en](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
 
 In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
 
@@ -113,12 +113,12 @@ Products must meet all the conditions specified in this section to be available
 
 The customer's request must meet the conditions added in this section to be valid in the promotion.
 
-- **Minimum and maximum order value:** The promotion will apply considering the "gross" cart value, without taking other discounts/promotions or shipping into account.
+- **Minimum and maximum order value:** for price promotions that directly adjust the value of items in the cart, the promotion activation is based on the original price of the items. And for promotions that offer other benefits, such as free shipping or gifts, the price considered to activate the promotion is the price already discounted.
 - **Aggregate value of purchases:** The discount will apply if the total value of all purchases made by the customer reaches the required value.
 - **Item price between:** The discount will apply if the value of the item is within the range of values set by the store.
 - **Price "From" and "to"; prices are the same** or **"from" and "to" prices are different:** Refers to the added product values. Only one can be selected.
 - **Use restriction BINs:** The discount will be granted if the card's BIN is given.
-- **Marketing Tags:** Field used to restrict the activation of the promotion if the purchase is made by the [VTEX Subscription System module](https://help.vtex.com/en/tutorial/how-do-subscriptions-work--frequentlyAskedQuestions_4453#). 
+- **Marketing Tags:** Field used to restrict the activation of the promotion. 
 - **Affiliates:** Marketplace order identifier. The discount will apply to selected affiliates. Read the article on [What is an affiliate](https://help.vtex.com/en/tutorial/what-is-an-affiliate--4bN3e1YarSEammk2yOeMc0?locale=en) for more information.
 - **Customer cluster:** The discount will apply if the client is part of the selected cluster. It is important to stress that the name of the cluster must be the same as the one added; any spelling error will prevent the correct functioning of the configuration.
 - **Shipping countries**: The discount will apply to the selected countries given in this field. 
diff --git a/docs/tutorials/en/releases-module-beta.md b/docs/tutorials/en/releases-module-beta.md
index 7a462055e..a432c5ea9 100644
--- a/docs/tutorials/en/releases-module-beta.md
+++ b/docs/tutorials/en/releases-module-beta.md
@@ -72,7 +72,7 @@ In this stage, the fields <b>Day to publish</b> and <b>Time</b> are not required
 
 8. Click `Create`.
 
-![print_cms_beta_en](https://images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/9c938423b576e80d181f0cc8d32a6b46/print_cms_beta_en.png)
+![print_cms_beta_en](//images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/9c938423b576e80d181f0cc8d32a6b46/print_cms_beta_en.png)
 
 ### How to create a release using the Releases module
 
@@ -92,7 +92,7 @@ In this stage, the fields <b>Day to publish</b> and <i>Time</i> are not required
 
 All the releases are listed in the VTEX Admin, in **Store Settings > Releases**. The page displays two tabs, `SCHEDULED` and `UNSCHEDULED`, depending on whether the release has been created with a set publish date. 
 
-![print_releases_en](https://images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/4895efa9b36315602d5b877de0a8a60c/print_releases_en.png)
+![print_releases_en](//images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/4895efa9b36315602d5b877de0a8a60c/print_releases_en.png)
 
 On the `SCHEDULED` tab, each column is described as follows:
 
diff --git a/docs/tutorials/en/releasing-the-store-for-production.md b/docs/tutorials/en/releasing-the-store-for-production.md
index 8ffc8de42..1b68e4d29 100644
--- a/docs/tutorials/en/releasing-the-store-for-production.md
+++ b/docs/tutorials/en/releasing-the-store-for-production.md
@@ -30,7 +30,7 @@ Then, you have to place your store on a production status on its relevant Licens
 4. On the option **Is it n production, **click on the **No button**, to change it to **Yes**;
 5. Click on the **Save** button.
 
-![accounts.en](https://images.ctfassets.net/alneenqid6w5/5VattCUDKiUuh4fFbZUUZH/2cf97d683b28608f863ffcb803348a2e/accounts.en.png)
+![accounts.en](//images.ctfassets.net/alneenqid6w5/5VattCUDKiUuh4fFbZUUZH/2cf97d683b28608f863ffcb803348a2e/accounts.en.png)
 
 After this is set up, the access to the final URL of the store will be redirected to your e-commerce!
 
diff --git a/docs/tutorials/en/relevance-rules.md b/docs/tutorials/en/relevance-rules.md
new file mode 100644
index 000000000..a64bec3be
--- /dev/null
+++ b/docs/tutorials/en/relevance-rules.md
@@ -0,0 +1,108 @@
+---
+title: 'Relevance rules'
+id: 1o9jtVGjSIiptbqdNXIlNK
+status: PUBLISHED
+createdAt: 2024-06-27T17:12:27.900Z
+updatedAt: 2024-06-27T17:13:52.839Z
+publishedAt: 2024-06-27T17:13:52.839Z
+firstPublishedAt: 2024-06-27T17:13:52.839Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: relevance-rules
+locale: en
+legacySlug: relevance-rules
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+**Relevance rules** define the order in which products are shown in search results in product listing pages (PLP). The order changes according to the criteria and priorities configured for the Search Engine.
+
+Relevance rules are applied to the search results only when the results are sorted by relevance in your store's search. For example, if a customer sorts results by price, relevance settings will not be considered when displaying search results.
+
+You can configure relevance in two ways:
+
+  - __Priority Criteria__: it imposes that one or more criteria has a higher priority among the others. In this situation, there are no weights; all products that have this feature will be shown first in the search results.
+  - __Criteria Composition__: it is a way to distribute weights for each option, ranging from 0 to 10. Here, there is no order between the criteria; the weights will define the relevance.
+
+![criterios-en](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/56c8163ed9b449419c17db066dd4506e/criterios-en.png)
+
+The information considered for the relevance is:
+
+- __Discount__: it compares the [List Price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#list-price) and the [Base Price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definition) to determine whether the product will be classified as having a discount.
+- __Release date__: this criterion assigns an automatic decreasing value (between 1 and 0) to the product, based on the date it was added to the catalog and considering a 90-day interval. Products added to the catalog today would have the value 1. This value would decrease every day until it becomes 0 after 90 days. This value will be multiplied by the weight you assign to the __Release date__ criterion to compose product relevance.
+- __Best-selling__: number of orders for the product in the last 90 days.
+- __Best-selling by revenue__: the total revenue generated by the product in the last 90 days.
+- __Popularity__: the number of clicks the item received in the last 90 days.
+- __Promotion__: it checks for [Campaign Audiences](https://help.vtex.com/en/tutorial/overview-2--tutorials_326?&utm_source=autocomplete#campaign-audiences) or [Promotions](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#) linked to the item to determine whether the product will be classified as a promotion.
+- __Catalog score__: Catalog sorting tie-breaker based on the value given to the **Score** field of products. For this purpose of composing relevance, the higher the score, the greater the weight, i.e. the behavior is descending: products with a higher score are prioritized. Find out more about the field and its behavior in the guide [How does the Score field work?](https://help.vtex.com/en/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcae).
+- __Available matrix variety__: Relevance is based on the percentage of SKUs available per product. In a scenario where _Product A_ has 3 SKUs and 3 of them are available, and _Product B_ has 5 SKUs and 2 of them are available, _Product A_ stands out over _Product B_ because the percentage of SKUs is higher.
+
+The set of weights and criteria distribution generates a score for the product, which determines its position in the search result ranking.
+
+<div class="alert alert-warning">
+  <p>IIf you want to use priority criteria, we recommend adding only one criterion in this field. Adding more criteria compromises the ordering or search results, since only the first criterion will be considered.</p>
+</div>
+
+So you can tailor the behavior of the search results to a specific strategy.
+
+## Example
+
+A fashion store receives new collections frequently. The retailer chooses to prioritize new products instead of products with discounts. To do that, the tool can be configured as follows:
+
+> __Priority criteria:__
+> 
+> - Empty
+> 
+> __Criteria composition:__
+> 
+> - Popularity: 7
+> - Release date: 10
+> - Best-selling: 6
+> - Best-selling by revenue: 6
+> - Promotion: 0
+> - Discount: 0
+> - Available matrix variety: 10
+
+If this retailer wants new products to always have the highest priority, there are two ways to configure the Relevance rules:
+
+> __A:__
+> 
+> __Priority criteria:__
+> - Release date
+> 
+> __Criteria composition:__
+> - Popularity: 7
+> - Best-selling: 6
+> - Best-selling by revenue: 6
+> - Promotion: 0
+> - Discount: 0
+> - Available matrix variety: 10
+
+> __B:__
+> 
+> __Priority criteria:__
+> - Empty
+> 
+> __Criteria composition__
+> - Popularity: 0
+> - Release date: 10
+> - Best-selling: 0
+> - Best-selling by revenue: 0
+> - Promotion: 0
+> - Discount: 0
+> - Available matrix variety: 0
+
+## Configuring relevance rules
+
+To change relevance settings, follow the steps below.
+
+1. In the Admin, go to the **Storefront** module.
+2. In **Intelligent Search**, click **Relevance Rules**.
+3. Choose the criterion whose weight you want to change.
+4. Click the arrow down <i class="fas fa-chevron-down"></i> or arrow up <i class="fas fa-chevron-up"></i> icons to set a number.
+
+   If you want to change a criterion from **Criteria Composition** to **Priority Criteria**, click on the <i class="fas fa-grip-vertical"></i> icon and drag it to the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight. 
+
+   ![criterios-prioritarios-en](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/326edf2ab5b2c2ee3050a97a98090dd9/criterios-prioritarios-en.gif)
+5. Click `Save` to finish.
+
diff --git a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
new file mode 100644
index 000000000..21933dbd4
--- /dev/null
+++ b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -0,0 +1,90 @@
+---
+title: 'How to remove the error message "Request headers must only contain ASCII characters"'
+id: 19psKZvLXrBqqK1bPaTIHG
+status: PUBLISHED
+createdAt: 2024-07-25T16:54:41.663Z
+updatedAt: 2024-07-25T21:25:10.665Z
+publishedAt: 2024-07-25T21:25:10.665Z
+firstPublishedAt: 2024-07-25T21:21:03.197Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: removing-error-message-request-headers-must-only-contain-ascii
+locale: en
+legacySlug: removing-error-message-request-headers-must-only-contain-ascii
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras-chave__: *request headers, ascii, special characters, devtools, headers, utm, custom javascript, script.*
+
+The message "__Request headers must contain only ASCII characters__" can be displayed in the user's browser when they navigate the store and try to access a new page or perform an action on the site, such as adding items to the shopping cart.
+
+This scenario occurs if the requested page or feature contains a cookie with special characters (non-ASCII).
+
+![ascii_1](//images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/d2137c6c3021d640daf3631e02f941a8/ascii_1.png)
+
+Per [IETF](https://www.ietf.org/) (Internet Engineering Task Force) standards, the institution that documents the standards used on the internet, cookies should not contain special characters (non-ASCII). For more information on the characters accepted in cookies and headers, see [IETF - Request for Comments 7230 - Section 3.2.6 - Field Value Components](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6).
+
+## Solutions
+
+To remove the error message and allow the page or feature to be accessed again, you need to do the following:
+
+- [Identify cookies with special characters](#identifying-cookies-with-special-characters)
+- [Disable cookies with special characters](#disabling-cookies-with-special-characters)
+- [Creating a script to remove cookies](#creating-a-script-to-remove-cookies)
+
+### Identifying cookies with special characters
+
+On the page where the message "__Request headers must contain only ASCII characters__" is displayed, follow the steps below to identify which cookie contains special characters:
+
+<blockquote><ui>1. Access <a href="https://help.vtex.com/pt/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">DevTools</a> in your browser by pressing <b>F12</b> or by right-clicking and choosing the <b>Inspect</b> option.</ui>
+
+  <blockquote><ui>2. In the top bar of the screen, go to the <b>Network</b> tab and sort the requests by clicking <b>Status</b>. The <b>400</b> information in the status indicates that a request has not been processed correctly, and there may be incorrect cookies among the possible errors.</ui>  
+
+![ascii 2](//images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/eb74d2c115b78d65dd60b70da67bfd5b/ascii_2.png)
+
+<blockquote><ui>3. Click a request and then the <b>Preview</b> tab to identify whether the error found refers to the message "<b>Request headers must contain only ASCII characters</b>".</ui>
+
+![ascii 3](//images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/2151b1260e9f10a1327b5b6f4441ef23/ascii_3.png)
+
+<blockquote><ui>4. Click the <b>Headers</b> tab and copy the cookie details.</ui>
+
+![ascii 4](//images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/305a23cbb5b90bfde1ca139c83978a92/ascii_4.png) 
+
+<blockquote><ui>5. Go to <a href="https://pages.cs.wisc.edu/~markm/ascii.html">online ASCII character validator</a> and enter the cookie information. If one or more special characters are identified, the types and positions will be displayed at the bottom of the character validator.</ui>     
+
+![ascii 5](//images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/917872a195c9cce233a183a4f44b4677/ascii_5.png)  
+
+<blockquote><ui>6. Repeat steps 3 to 5 with all the requests that have errors to identify which of them contain cookies with special characters.</ui>      
+
+### Disabling cookies with special characters
+
+Once cookies containing special characters have been identified, their origin must be verified so that they can be removed from the page. The most common sources of incorrect cookies are:
+
+- [UTMs](https://help.vtex.com/pt/tutorial/o-que-sao-as-utms-internas-utmi-cp-utmi-pc-e-utmi-p--5Pvo8ufYWs00AUeCCEY68a) created in your store or in advertising campaigns on Google, Meta, or others with special characters. Example of UTM used on a holiday date in Spanish: `www.site.com?utm_source=mothers-day`.
+- Custom Javascript, where frontend implementations are used to store data or other types of functions, may contain special characters.
+- Scripts from partner clients that create cookies with special characters.
+
+Once you have located the source of the cookie, carry out the necessary procedures to remove it from the page or ask the partner client to stop sending the cookie to your store.
+
+### Creating a script to remove cookies
+
+When you remove the cookie with special characters, the page or feature should go back to normal, and the message "__Request headers must contain only ASCII characters__" will no longer be displayed. However, this will only work for new users, i.e., customers who have not accessed the page when the incorrect cookie was enabled.
+
+Users who visited the page or feature while the incorrect cookie was enabled will continue to see the error message "Request headers must contain only ASCII characters" in their browser. This is because the cookie has been stored in the user's browser cache.
+
+To solve this problem and allow all users to have the correct access to the store, you must create a script on the page to be executed in the user's browser (client-side) to expire the incorrect cookie.
+
+The script must set the cookie to expire on an old date (a date before the script was created). See the example below:
+
+`document.cookie = "cookiename= ; expires = Thu, 01 Jan 1970 00:00:00 GMT"`  
+
+If you want, you can also include the following functions in the script:
+- Intercept cookie values upon page request
+- Validate ASCII characters in cookies
+- Automatically expire cookies containing special characters
+- Trigger page reload using the function `window.location.reload()`  
+
+<div class="alert alert-warning">
+  Deleting cookies via script is not a permanent solution. As described in the <b>Disabling cookies with special characters</b> section, you must identify the source and stop sending cookies with special characters.
+</div>
diff --git a/docs/tutorials/en/requesting-a-new-organization.md b/docs/tutorials/en/requesting-a-new-organization.md
new file mode 100644
index 000000000..7f6bba67c
--- /dev/null
+++ b/docs/tutorials/en/requesting-a-new-organization.md
@@ -0,0 +1,97 @@
+---
+title: 'Requesting a new organization'
+id: 4bTIDPay4fNz39l5XHijAh
+status: PUBLISHED
+createdAt: 2024-06-06T16:21:26.266Z
+updatedAt: 2024-06-07T10:55:22.825Z
+publishedAt: 2024-06-07T10:55:22.825Z
+firstPublishedAt: 2024-06-06T16:27:05.446Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: requesting-a-new-organization
+locale: en
+legacySlug: requesting-a-new-organization
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+To add an organization in your store, the Add a new organization form must be completed as follows:
+
+1. Access the form by adding `/organization-request` to the end of your store's URL.
+
+2.	Complete the form with the company's details as described in this document.
+
+3.	Click the Send button.
+
+After sending the form, the store team must review and approve the request in the VTEX Admin.
+
+## Request form
+
+The form for adding a new organization is divided into the following sections:
+- [Add a new organization](#add-a-new-organization)
+- [Organization admin user](#organization-admin-user)
+- [Default cost center](#default-cost-center)
+
+### Add a new organization
+
+The requesting company must provide the following registration data, including any custom fields:
+
+- **Organization name:** Name of the organization you want to add.
+- **Trade name:** Trade name used by the company.
+
+### Organization admin user
+
+Details of the user who will be assigned as the admin of the new organization include:
+
+- **Name:** User first name .
+- **Last name:** User last name.
+- **Email:** User email.
+
+### Default cost center
+
+Details of the cost center with which this organization will be associated.
+
+The form includes the following fields:
+
+- **Cost center name:** Name of the initial cost center associated with the organization.
+
+- **Phone:** Telephone number to contact the organization.
+
+- **Business document:** You can use the corporate registration number, tax identification number, VAT number, or other document.
+
+- **State registration:** Company state registration number.
+
+- **Country:** Country where the cost center is located.
+
+- **Postal code:** Postal code of the cost center address.
+
+- **Address:** Name of the street where the cost center is located.
+
+- **Number:** Address number where the cost center is located.
+
+- **Additional information:** Extra details about the cost center's address.
+
+- **Neighborhood:** Name of the neighborhood where the cost center is located.
+
+- **City:** City where the cost center is located. This is completed automatically based on the postal code entered.
+
+- **State:** State where the cost center is located. This is completed automatically based on the postal code entered.
+
+- **Recipient:** Name of the person who will receive the orders at the address provided.
+
+## Verifying organizational requests
+
+After submitting the request, the store team must review it in the VTEX Admin by going to **Apps > B2B Organizations & Cost Centers > Organizations** or typing **Organizations** in the search bar at the top of the page.
+
+On this page, you can view a list of all the organization requests made in your store.
+
+Each organization can have a status of pending, approved, or denied. Pending requests are those still awaiting review.
+
+To review a request, follow these steps:
+
+- Click an organization or the <i class="fas fa-ellipsis-v" aria-hidden="true"></i> icon to view it.
+- Write a comment in the Add note field, if necessary.
+- Click the `Approve` or `Deny` button.
+
+The organization's admin will receive an email notification of the approval.
+
diff --git a/docs/tutorials/en/requesting-an-additional-trade-policy.md b/docs/tutorials/en/requesting-an-additional-trade-policy.md
index 470055398..451d1735c 100644
--- a/docs/tutorials/en/requesting-an-additional-trade-policy.md
+++ b/docs/tutorials/en/requesting-an-additional-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Requesting an additional trade policy'
 id: 61vuFOw4yGh6nwSmkLJL1X
 status: PUBLISHED
 createdAt: 2021-12-06T23:25:42.650Z
-updatedAt: 2022-12-08T20:01:23.876Z
-publishedAt: 2022-12-08T20:01:23.876Z
+updatedAt: 2024-06-20T23:00:50.418Z
+publishedAt: 2024-06-20T23:00:50.418Z
 firstPublishedAt: 2021-12-06T23:51:25.043Z
 contentType: tutorial
 productTeam: Channels
@@ -19,20 +19,13 @@ VTEX uses [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-p
 
 Using trade policies, you can determine catalog, price, promotion, payment, inventory, logistics, and audience segmentation settings for sales channels. It is not necessary to [create a different trade policy](https://help.vtex.com/en/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) for each sales channel, as the same trade policy can be used in multiple channels.
 
-Requesting additional trade policies to integrate with native connectors, certified connectors (partners), or other VTEX stores is free of charge. For more information, read our article [Marketplace strategies at VTEX](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
+Requesting additional trade policies to integrate with certified marketplaces or other VTEX stores is free of charge. For more information, read our article [Marketplace strategies at VTEX](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
-To request a trade policy for a sales channel outside the VTEX ecosystem, such as a marketplace for which there is no [native connector](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex)<span style="text-decoration:underline;">,</span> for example, there are two possible flows:
-
-- [Requesting a trade policy for the Brazilian market](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X#requesting-a-trade-policy-for-the-brazilian-market)
-- [Requesting a trade policy for the international market](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X#requesting-a-trade-policy-for-the-international-market)
-
-## Requesting a trade policy for the Brazilian market
-
-To request an additional trade policy for operating in the Brazilian market, fill out the [Trade Policy Release form](https://docs.google.com/forms/d/e/1FAIpQLSe9qCGB_KM_xsV5e9uNe06JE8tMZrWcv6EuHUOmqTiM8oRW7w/viewform). If you have any questions, please contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `Create a trade policy`.
+To request a trade policy for a sales channel outside the VTEX ecosystem, such as a marketplace for which there is no [native connector](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex)<span style="text-decoration:underline;">,</span> for example, follow the flow of [Requesting a trade policy for the international market](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X#requesting-a-trade-policy-for-the-international-market)
 
 ## Requesting a trade policy for the international market
 
-To request an additional commercial policy for operating in the international market, contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `Create a trade policy`.
+To request an additional trade policy for operating in the international market, contact our Growth Operations team through *[Support](https://help.vtex.com/en/support)* by selecting **Commercial** and `New trade policy`.
 
 <br></br>
 ### Learn more
diff --git a/docs/tutorials/en/resetting-your-two-factor-authentication-app-configuration.md b/docs/tutorials/en/resetting-your-two-factor-authentication-app-configuration.md
index a621e4af7..c2d65992a 100644
--- a/docs/tutorials/en/resetting-your-two-factor-authentication-app-configuration.md
+++ b/docs/tutorials/en/resetting-your-two-factor-authentication-app-configuration.md
@@ -3,8 +3,8 @@ title: 'Resetting your two-factor authentication app configuration'
 id: 4ftaOCZono1MiQia2hxbTy
 status: PUBLISHED
 createdAt: 2023-02-08T13:55:25.623Z
-updatedAt: 2023-02-08T14:26:33.141Z
-publishedAt: 2023-02-08T14:26:33.141Z
+updatedAt: 2024-03-12T18:52:44.442Z
+publishedAt: 2024-03-12T18:52:44.442Z
 firstPublishedAt: 2023-02-08T14:26:33.141Z
 contentType: tutorial
 productTeam: Identity
@@ -17,11 +17,11 @@ subcategory: 4sY1T2qdFehvVmC0tL5xW3
 
 If you have already [enabled two-factor authentication login](https://help.vtex.com/pt/tutorial/enabling-2-factor-authentication-login--4Ae1fcQi12g8u4SkQKCqWQ) but made a mistake during the configuration or lost access to your two-factor authentication app, you might not be able to access your VTEX account.
 
+## Regaining access to VTEX Admin
+
 To regain access to your account, follow these steps:
-1. Go to this address to see your account's login page:
-```
-https://{accountName}.myvtex.com/admin
-```
+
+1. Go to VTEX Admin to see your account's login page.
 2. Enter your email address.
 3. Click `Continue`.
 4. Click **Forgot password**.
@@ -32,12 +32,13 @@ https://{accountName}.myvtex.com/admin
 
 Once you have regained access to your account as described above, you can reset the two-step verification app by following these steps:
 
-1. Go to the two-step verification configuration page in your account here:
-```
-https://{accountName}.myvtex.com/admin/myuser/twostepverification
-```
-2. Click **Change** in the **Google Authenticator app** section.
-3. If you do not have the Google Authenticator app installed, install it on your mobile device.
-4. Scan the QR code using the Google Authenticator app.
-5. Enter the code that appears in the app in the field indicated on the page.
-
+1. In the top bar of the VTEX Admin, click your profile avatar, indicated by the initial letter of your email address.
+2. Click **User Settings**.
+3. In the **Authentication**, click on the **2-Step Verification** row.
+4. Select **Google Authenticator app**.
+5. Click `Setup` or`Change`, if you already have an authenticator app configured.
+6. In case you do not have the __Google Authenticator__ ([App Store](https://itunes.apple.com/us/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2)), install it on your mobile device.
+7. Scan the QR code using the Google Authenticator app.
+8. Click `Next`.
+9. Enter the code that appears in the app in the field indicated on the page.
+10. Click `Confirm`.
diff --git a/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
new file mode 100644
index 000000000..0a5277650
--- /dev/null
+++ b/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
@@ -0,0 +1,201 @@
+---
+title: 'Responsibilities within the VTEX ecosystem'
+id: 3vL9aWICDr3WR64DYi1fJ3
+status: PUBLISHED
+createdAt: 2024-01-31T17:08:24.444Z
+updatedAt: 2024-02-16T17:22:16.507Z
+publishedAt: 2024-02-16T17:22:16.507Z
+firstPublishedAt: 2024-01-31T23:11:13.804Z
+contentType: tutorial
+productTeam: Billing
+author: 1malnhMX0vPThsaJaZMYm2
+slug: responsibilities-in-the-vtex-ecosystem
+locale: en
+legacySlug: responsibilities-in-the-vtex-ecosystem
+subcategory: 1VvCpaa8NCA6a0MK6W6oWg
+---
+
+The future of digital commerce is collaborative, and successful partnerships are crucial to successful store operations. When operating a store, doubts often arise about the responsibilities of each player in the ecosystem.
+
+This article outlines the main players' responsibilities in a digital commerce operation to optimize your store's operation and ensure efficient communication between the merchant and VTEX support. Check out the responsibilities in each scenario below:
+
+- [Back-office integrations (ERP/PIM/WMS)](#back-office-integrations-erp-pim-wms)
+- [Payment provider integrations](#payment-provider-integrations)
+- [Implementation agencies](#implementation-agencies)
+- [Marketplace integrations](#marketplace-integrations)
+
+## Back-office integrations (ERP / PIM / WMS)
+
+During the initial setup on VTEX, if your store uses[ external integrations with ERP/PIM/WMS](https://developers.vtex.com/docs/guides/erp-integration-guide), these systems should send your store's products, prices, and inventory to VTEX. Next, you must build a middleware to send and receive information from VTEX based on your store's routine events.
+
+Once the initial product, price, and inventory integration has been set up and the middleware built, the information flow will be as shown in the diagram below.
+
+![back-office-en](//images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/1d2fe04cb3d2bd6c09b2fd000544d3e4/back-office-en.PNG)
+
+During routine operations, responsibilities are divided as follows:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <tr>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Player</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Responsibilities</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>ERP / PIM / WMS</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">Sending the following information to VTEX via integration:
+        <ul>
+          <li>Changes to product information</li>
+          <li>Prices</li>
+          <li>Inventory</li>
+          <li>Invoice</li>
+          <li>Order tracking details</li>
+          <li>Order changes</li>
+          <li>Cancellations</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>VTEX</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">Sending the following information to the ERP, based on the store's configuration via <a href="https://developers.vtex.com/docs/guides/orders-feed" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Order Feed</a> or <a href="https://developers.vtex.com/docs/guides/orders-feed" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Hook</a>:
+        <ul>
+          <li>Notifications of a new order created.</li>
+          <li>Notifications of an order's progress.</li>
+        </td>
+    </tr>
+  </tbody>
+</table>
+
+## Payment provider integrations
+
+To process payments for orders in a VTEX store, the payment infrastructure responsibilities are divided as follows:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <tr>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Player</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Responsibilities</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Merchant</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Contract payment providers (gateways, acquirers, or subacquirers).</li>
+          <li>Contract an anti-fraud solution provider (optional).</li>
+          <li>Configure the store with the payment and anti-fraud providers with whom you have established contracts.</li>
+          <li>Configure payment methods and conditions in the store based on the specifications of each contract established with payment and anti-fraud providers.</li>
+          <li>Manually cancel or refund a payment when the payment provider does not do this automatically or in specific cases where the merchant needs to do it manually.</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Payment providers (gateways, acquirers, or subacquirers)</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Develop the payment provider integration according to the instructions in<a href="https://developers.vtex.com/docs/guides/integrating-a-new-payment-provider-on-vtex" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"> Integrating a new payment provider on VTEX</a>.</li>
+          <li>Obtain<a href="https://developers.vtex.com/docs/guides/payments-integration-pci-dss-compliance" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"> PCI-DSS</a> certification or develop the integration with VTEX using<a href="https://developers.vtex.com/docs/guides/payments-integration-secure-proxy" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"> Secure Proxy</a> to process payment transactions with sensitive information, such as credit, debit, and co-branded card details.</li>
+          <li>Process financial transactions securely and efficiently, which includes:
+            <ul>
+              <li>Approving or denying payments, following internal policies.</li>
+              <li>Settling or refunding payments.</li>
+              <li>Acquirer: Processing payments made with credit and debit cards.</li>
+              <li>Subacquirer: Enabling payments between acquirers, anti-fraud solution providers, and merchants.</li>
+              <li>Sending payment transaction status updates to the VTEX gateway.</li>
+            </ul>
+          </li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Anti-fraud solution provider</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Conduct risk analysis on transactions involving credit, debit, and co-branded cards to identify fraudulent activities.</li>
+          <li>Send analysis information to the VTEX gateway.</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>VTEX Gateway</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Create payment transactions for new orders.</li>
+          <li>Send transaction and order details to partners processing or analyzing payment information (payment and anti-fraud providers).</li>
+          <li>Record all the actions during the payment transaction flow, such as creation, approval, cancellation, etc.</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+If inconsistencies or errors are detected during the order payment transaction, the merchant must:
+
+1. Contact who is handling the transaction (payment and anti-fraud providers).
+2. If the issue remains unresolved, contact [VTEX Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe) providing details of the incident.
+
+## Implementation agencies
+
+With native CMS solutions, merchants often rely on an implementation agency to customize the storefront's layout and customer experience.
+
+VTEX offers the following native CMS options: [Layout](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj#layout) for [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) stores, [Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) for stores using the [Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework), and [Headless CMS](https://help.vtex.com/en/tutorial/headless-cms-visao-geral--3U5gvhHdQL0jczYH8gjX09) for stores using [FastStore](https://www.faststore.dev/). You can also integrate your external CMS with the VTEX APIs using a [headless](https://developers.vtex.com/docs/guides/headless-commerce) approach.
+
+Issues related to how the content is being displayed to the end user should always be addressed initially with the agency's support. Some examples of these issues are:
+
+* Incorrect or outdated images, titles, or banners.
+* Products unavailable on the storefront.
+* Blank pages.
+* Incorrect or outdated category menu.
+* Incorrect or incomplete search or collection results.
+* Call-to-action buttons (e.g., Buy, Notify Me, Add to Cart) with unexpected behavior.
+* Product prices or shipping rates inconsistent with the information stored on the platform.
+
+If the agency identifies that the problem is with VTEX controls, apps, or native components, contact [VTEX Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe) including all evidence from the agency's investigation.
+
+## External marketplace integrations
+
+VTEX has a native multi-seller architecture that allows VTEX stores to become marketplaces or sellers in other VTEX stores. The platform has native integrations with external marketplaces, allowing you to sell your products without having to write a single line of code. The marketplaces with native integrations can be found in the [Marketplaces and Integrations](https://help.vtex.com/en/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V) tab.
+
+Even so, there may be strategic partner stores for your business that operate outside this native collaborative network. In such cases, VTEX allows developing[ integrations with external marketplaces](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide), where external connectors (hubs) establish the communication between a VTEX store and a non-native external marketplace.
+
+For merchants operating in this scenario, it's important to understand the responsibilities of each player involved in the operation, as detailed below.
+
+<div class="alert alert-warning">
+  <p>The following sections consider a store already integrated with an external marketplace via an external connector. Learn how to integrate your VTEX Catalog with an external connector for the first time, go to the <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Catalog Integration</a> guide.</p>
+</div>
+
+### Updating or sending new products and SKUs
+
+Below are the responsibilities involved in updating or sending new products and SKUs to external marketplaces:
+
+| **Player** | **Responsibilities** |
+|---|---|
+| **VTEX** | Send a notification of a new product or SKU created or updated to the affiliate endpoint provided by the hub and added to the VTEX platform. |
+| **Partner connector (integration hub)** | Process the notification and send the updated product or SKU to the marketplace. <br /><br />This process encompasses many steps: checking if this SKU already exists in the marketplace and adding it if necessary, validating if the product is active and associating it with the marketplace's trade policy, running an order simulation to check the SKU's updated price and inventory, etc. |
+| **Non-native external marketplace** | Provide the necessary endpoints for the hub to send the updated SKU, log the received SKU, and reply the status to the connector.= |
+
+### Updating or creating new orders
+
+See below the responsibilities involved in updating or creating orders based on the order flow.
+
+1. The **marketplace** provides the products and the checkout for placing orders and notifies the connector when a new order is created.
+2. The **connector** creates the order on VTEX.
+3. VTEX replies to the connector with the order creation status: Success or Failure. In this step, contact the connector's support if an error occurs while creating the order on VTEX or if the order is created with the **Canceled** status.
+4. Once the order is created on VTEX, the responsibility for updating its status in the OMS depends on the process stage:
+
+   * If the order is being handled or invoiced, for example, the **ERP** notifies VTEX.
+   * If the order was canceled in the marketplace, it is the **connector**'s responsibility to update the status.
+
+For more information on who is responsible for each step of the order flow in an external marketplace scenario, see [Order flow and status - Seller flow](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196#seller-flow).
+
+To understand the right support to request in case of issues with updating the order status, follow the steps below:
+
+1. In the VTEX Admin, go to **Orders > All Orders**.
+2. Click the desired order to go to the [order details page](https://help.vtex.com/en/tutorial/order-details-page--2Y75n54Cc9VizrlG1N6ZNl).
+3. In the **Order History** section, click `View Interactions` (button illustrated below) and check for any error messages.
+
+![view-interactions-en](//images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/0f0830c6ea1439877301be64f17c0ccf/view-interactions-en.png)
+
+If the error message does not provide sufficient information, the merchant can contact [VTEX Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe), providing the interaction screen and order ID as evidence, and our team of experts will help identify the source of the issue.
diff --git a/docs/tutorials/en/responsive-vs-mobile-version.md b/docs/tutorials/en/responsive-vs-mobile-version.md
index e4a56a472..1e2dd06f5 100644
--- a/docs/tutorials/en/responsive-vs-mobile-version.md
+++ b/docs/tutorials/en/responsive-vs-mobile-version.md
@@ -55,7 +55,7 @@ Main mobile and desktop screen resolutions currently in use (there can be variat
 
 #### Main visual elements seen in mobile devices
 
-![menu_mobile_version en](https://images.ctfassets.net/alneenqid6w5/6Q1KNePAFUUOKEIyswQcA2/2288e7aeef0d78d51391a1d658333cd6/modelo_menu_ingles.png)
+![menu_mobile_version en](//images.ctfassets.net/alneenqid6w5/6Q1KNePAFUUOKEIyswQcA2/2288e7aeef0d78d51391a1d658333cd6/modelo_menu_ingles.png)
 
 #### Quality is the same regardless of the size!
 
diff --git a/docs/tutorials/en/restrict-public-access-to-master-data-fields.md b/docs/tutorials/en/restrict-public-access-to-master-data-fields.md
new file mode 100644
index 000000000..69a6e4ece
--- /dev/null
+++ b/docs/tutorials/en/restrict-public-access-to-master-data-fields.md
@@ -0,0 +1,57 @@
+---
+title: 'Restrict public access to Master Data fields'
+id: 5eu1N1h4Vqe8GY1yHXUsvz
+status: PUBLISHED
+createdAt: 2024-06-25T12:54:28.672Z
+updatedAt: 2024-06-25T13:28:43.112Z
+publishedAt: 2024-06-25T13:28:43.112Z
+firstPublishedAt: 2024-06-25T13:28:43.112Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: restrict-public-access-to-master-data-fields
+locale: en
+legacySlug: restrict-public-access-to-master-data-fields
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+In [Master Data v1](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw), it is possible to [create data entities](https://help.vtex.com/en/tutorial/data-entity--tutorials_1265#creating-data-entities) with different access restrictions for each field:
+
+* Make readable without credentials
+* Allow editing without credentials
+* Allow filtering without credentials
+
+Depending on the data stored, public access without authentication can pose a risk to your business. To enforce authentication and restrict public access to fields containing sensitive data, follow the instructions below.
+
+1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data.**
+2. In Master Data, click **Applications**.
+3. Click the gear <i class="fas fa-cog"></i> next to **Profile System**:
+
+   ![1-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/60f8fe775c03019223c0efb4c4b1974f/1-master-data-confidential-data-en.png)
+4. In **Settings**, click **Data structure**.
+
+   ![2-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/43d3dad46261ca9248a3f0d1f0486045/2-master-data-confidential-data-en.png)
+5. Click the **Data Entities** tab.
+6. In the data entity row, click the edit <i class="fas fa-edit"></i> button.
+
+   ![3-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/ede7660d491b4a499894812f929baf02/3-master-data-confidential-data-en.png)
+7. Click the gear icon <i class="fas fa-cog"></i> in the row of a field that contains confidential data.
+
+   ![4-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/5f85332ba75a41caa9d1dc30040ed4c7/4-master-data-confidential-data-en.png)
+8. Uncheck the following options:
+
+   * **Make readable without credentials**
+   * **Allow editing without credentials**
+   * **Allow filtering without credentials**
+
+   ![5-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/df29906627fc7f068ad13733a6d18dc2/5-master-data-confidential-data-en.png)
+9. Click `Save`.
+10. In the row of the changed data entity, click the Publish button <i class="fas fa-save"></i> to publish the saved settings.
+11. Click `OK`.
+
+## Required permissions
+
+After following the previous instructions, it is mandatory to have a [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) with the necessary [permissions](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) to access the following information:
+
+* At least one resource from the **Generic resources** category in the **Master Data** product: **READONLY_USER_CRM**, **POWER_USER_CRM**, **NOREMOVE_USER_CRM**, or **ADMIN_CRM**.
+* At least one resource from the **Dynamic storage generic resources** category in the **Dynamic Storage** product:** READONLY_USER_DS**, **NOREMOVE_USER_DS**, **POWER_USER_DS**, or **ADMIN_DS**.
diff --git a/docs/tutorials/en/risk-assessment.md b/docs/tutorials/en/risk-assessment.md
new file mode 100644
index 000000000..5b7fae382
--- /dev/null
+++ b/docs/tutorials/en/risk-assessment.md
@@ -0,0 +1,465 @@
+---
+title: 'Risk Assessment'
+id: 4K97IpqkpCpDYsZOSxtfkX
+status: PUBLISHED
+createdAt: 2022-05-26T13:08:53.479Z
+updatedAt: 2024-05-28T16:54:14.044Z
+publishedAt: 2024-05-28T16:54:14.044Z
+firstPublishedAt: 2022-05-26T13:17:48.374Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: risk-assessment
+locale: en
+legacySlug: the-risk-assessment-process
+subcategory: vONCJSxwN5qZiElOEtKkH
+---
+
+Risk assessment is critical for a vendor risk management program that works. The process consists of third-party risk assessment questionnaires that aim to help an organization identify potential risks among third-party providers and partners.
+
+The questionnaires are submitted to VTEX in order to:
+
+* Check whether VTEX meets the security requirements set by the client.
+* Share technical details about the security architecture.
+* Assess potential platform risks.
+
+To support risk assessments conducted by clients, VTEX provides FAQ pages answering the most frequent questions about platform structure and security.
+
+Click the points below to go to the related FAQ:
+
+* [Policies and compliance](#policies-and-compliance)
+* [Security education and awareness](#security-education-and-awareness)
+* [Asset management](#asset-management)
+* [Data and privacy](#data-and-privacy)
+* [Encryption](#encryption)
+* [Access control, identification, and authentication](#access-control-identification-and-authentication)
+* [Platform security](#platform-security)
+* [Log auditing](#log-auditing)
+* [Secure development](#secure-development)
+* [Physical security and data centers](#physical-security-and-data-centers)
+* [Vulnerability management](#vulnerability-management)
+* [Incident response and mitigation](#incident-response-and-mitigation)
+* [Disaster recovery and business continuity](#disaster-recovery-and-business-continuity)
+
+Some security information is restricted to VTEX Admin users, and it's not available in the VTEX Help Center. To access the restricted information, enter your VTEX account name below:
+
+<iframe src="https://help.vtex.com/insertaccountname?id=7AmPOGXykmE9SYyYDzdAZ4" title="Enter your account name and click the button." frameBorder="0" width="400" height="50"></iframe>
+
+<div class="alert alert-warning">
+  If you are having dificulty accessing the FAQs, try installing the latest version of the app <code>vtex.admin-docs</code> using <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">VTEX CLI</a> and repeating the process.
+</div>
+
+## FAQ - Security
+
+### Policies and compliance
+
+#### Does VTEX have an information security policy? If yes, how often is it reviewed? Has the policy been distributed and communicated to the entire company?
+
+VTEX takes a rigorous approach to information security, and through a document management process, the information security policy is reviewed annually. All employees formally accept the policy, which is communicated to the entire company through our internal channels. The policy follows security best practices that are aligned with the ISO/IEC 27001 standard and industry-recognized frameworks. It also meets the requirements of data protection laws and other VTEX obligations.
+
+#### Are VTEX information security controls audited by third-party companies? What certifications does VTEX have?
+
+VTEX, committed to transparency and excellence, regularly submits its information security controls to be audited by third-party professionals. Auditors are impartial and objective, which ensures a rigorous and unbiased assessment of the measures implemented by VTEX. This is important because it provides external validation for policies and procedures, ensuring they align with security standards, frameworks, and best practices. Third-party audits build trust with clients, partners, and other stakeholders and demonstrates the commitment VTEX has to upholding high information security standards. We currently hold the following certifications:
+
+* SOC 1 Type 2: A report that that covers internal controls over financial reporting systems.
+* SOC 2 Type 2: A report covering security, availability, integrity, confidentiality, and privacy.
+* PCI DSS: A control validation of cardholder data to reduce credit card fraud.
+* 
+These certifications are available on the [Compliance](https://vtex.com/us-en/compliance/) page of the [VTEX Trust Hub](https://vtex.com/us-en/trust/).
+
+In addition, as a publicly traded company, VTEX is SOX (Sarbanes-Oxley Act) compliant.
+
+#### Who is responsible for managing the VTEX information security program?
+
+Our organization has executive leaders that oversee the information security program, as well as a data protection officer (DPO) who coordinates the privacy program. The teams, which include engineers and highly specialized information security analysts, are structured specifically to support the main security processes.
+
+#### Are information security polices critically analyzed and maintained to comply with legal, regulatory, or contractual cybersecurity obligations? How often are they reviewed?
+
+Our information security policies and procedures were designed based on industry best practices and guidelines, such as the ISO/IEC 27001 standard. We manage these resources through internal VTEX tools. Leaders and security experts review them annually.
+
+#### How is the VTEX audit and certification calendar managed?
+
+VTEX has a specialized security team dedicated to managing certifications to guarantee compliance with all necessary requirements. This team works to ensure that all applicable certifications are obtained and renewed in a timely manner, reinforcing our commitment with the highest security standards.
+
+#### How many members does the information security team have?
+
+The VTEX team includes managers, engineers, and analysts who are highly specialized in information security. Our team is structured and dedicated to supporting the main security processes. It's ready 24/7 and spread over different time zones, ensuring constant coverage beyond business hours.
+
+In addition to the information security team, other VTEX teams have dedicated members who take part in the security processes, demonstrating the global commitment of our organization to data protection and integrity.
+
+#### Are information security policies and controls contractually applied to third-party providers?
+
+All providers and partners involved in processing our data, and that of our clients, are subject to contractual agreements that include security clauses. The agreements establish specific guidelines and requirements to guarantee appropriate data protection and ensure that all parties are committed to the highest information security standards.
+
+Learn more about our [third-party infrastructure providers](https://vtex.com/us-en/privacy-and-agreements/subprocessors/).
+
+### Security education and awareness
+
+#### Does VTEX have processes and guidelines for information security awareness?
+
+VTEX has different recurring information security trainings:
+
+* Security onboarding for all new employees, covering topics such as security team structure, communication channels, guideline documents, policies, approved tools, and external obligations; as well as security best practices, secure passwords, social engineering, and document management.
+* Monthly training on security best practices and tips for day-to-day activities.
+* Monthly global meetings to discuss new information security topics, security control details and updates, and best practices.
+* Periodic phishing tests, phishing reporting tool, and additional training for users who click the phishing simulations.
+* In-person initiatives during events that cover security best practices and physical and technical controls.
+
+We also have an information security and awareness guideline document that describes the initiatives mentioned above.
+
+#### Is there technical training available for the security team?
+
+There are internal training sessions related to secure development practices, information security controls, incident response, and other training opportunities that cover the technical context of security and privacy.
+
+#### Does VTEX have an awareness program focused on malware protection and mitigation? Are employees trained on this subject?
+
+The company has internal programs to raise awareness about malware and its potential consequences. Through internal communications and training, all VTEX employees are regularly informed about malware risks, how it can be installed on a device, and signs that a device is infected. If the presence of malware is suspected, employees are instructed to contact the appropriate team.
+
+Additionally, protection is implemented through security tools that continuously monitor for malware.
+
+In production environments, malware is actively monitored by anti-malware software installed in the instances. If malware is detected, the affected instance is terminated so that the automatic scaling processes can create a clean instance from scratch.
+
+### Asset management
+
+#### How does VTEX manage the most critical assets of the organization?
+
+Assets are centrally managed through an inventory management system that stores and tracks owner, location, status, maintenance, and descriptive information for AWS-owned assets. Following procurement, assets are scanned and tracked, and assets undergoing maintenance are checked and monitored for ownership, status, and resolution.
+
+#### How does VTEX manage asset inventory within the company?
+
+VTEX is 100% cloud-based and is the largest AWS partner in Latin America. Therefore, it doesn't need to keep a physical asset inventory. For software inventory, we use AWS Systems Manager, which provides visibility into our AWS computing environment. At the corporate level, we use a dedicated solution to manage endpoints and apply security rules.
+
+#### How does VTEX handle asset destruction and disposal (removable media, USB flash drives, etc.)?
+
+Media storage devices used to store customer data are classified as critical and of high impact and are handled accordingly throughout their lifecycles. We have strict standards for installing, maintaining, and eventually destroying devices when they are no longer useful. When a storage device reaches the end of its useful life, it is decommissioned using techniques detailed in NIST 800-88.
+
+### Data and privacy
+
+#### Does the company have a data protection and privacy policy? If yes, how often is it reviewed? Has the policy been distributed and communicated to the entire company?
+
+Yes, VTEX has data protection and privacy policies, which are reviewed annually. The internal and external privacy policies were distributed and communicated to the entire company through our internal announcements channel. The internal privacy policy is kept in our internal corporate document tool to facilitate open access by employees. Our [External Privacy Notice](https://vtex.com/us-en/privacy-and-agreements/external-notice/) can be found on the VTEX website.
+
+#### Does the organization have a data protection officer (DPO) with the authority, mission, responsibility, and resources to coordinate, develop, and implement applicable privacy requirements and manage privacy risks through a privacy program?
+
+Yes, VTEX has a DPO that coordinates the privacy program: Angela Fonseca (dpo@vtex.com).
+
+#### What type of personal data does VTEX process on behalf of its clients?
+
+As a data processor, VTEX processes personal data from shoppers only when necessary, in accordance with the requirements of each platform module in order to carry out ecommerce operations. The following list includes the personal data that VTEX may process:
+
+* Name
+* Email
+* IP address
+* Browsing data ([cookies](https://vtex.com/us-en/privacy-and-agreements/vtex-platform-cookies-information/))
+* Cart details
+* Order details and history
+* Shipping address
+* ID number (when required by the country where the store operates)
+* Gift card history
+* Abandoned cart
+* [Conversation Tracker](https://help.vtex.com/en/tutorial/conversation-tracker) chat
+* Session passwords (encrypted)
+* Generated tokens
+
+The data list above is described in the [Data Processing Addendum (DPA)](https://help.vtex.com/en/tracks/data-and-privacy--4Lc0i0an0DgnEtB0AUwlcq/5f8hTEw3xOALgqzus9VXKd#data-processing-addendum-dpa).
+
+#### How does VTEX ensure compliance with the General Data Protection Regulation (GDPR) or the Brazilian General Data Protection Law (LGPD)?
+
+VTEX is committed to be compliant with all applicable data protection regulations, including GDPR and LGPD. You can read more about our data protection policies, agreements, and compliance commitment on the [Privacy & Agreements](https://vtex.com/us-en/privacy-and-agreements/) page of our website.
+
+Check our [Data Processing Addendum (DPA)](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/) to learn how personal data is processed by VTEX.
+
+#### What data subject rights does the VTEX platform guarantee?
+
+VTEX acts as a data processor of end consumer data that is processed by our clients (merchants). Therefore, VTEX cannot handle data subject requests directly. If a data subject (or their representative) submits a request, VTEX will notify the merchant as indicated by the data subject.
+
+As the controller, the merchant defines the legal basis and purpose of data processing. If you are unable to handle a request due to technical, contractual, or legal reasons, you can justify the reason for refusal.
+
+If you would like help in exercising the data subject rights of one of your store customers, check [Erasing customer data](https://help.vtex.com/en/tutorial/exclusao-de-dados-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU).
+
+#### Does VTEX have a data classification policy?
+
+VTEX established a data classification policy to guide employees in correctly categorizing data based on sensitivity level. This policy aims to ensure data security, integrity, and confidentiality on VTEX, as well as help manage appropriate access to the data.
+
+Our policy establishes the classification levels as public, internal, and confidential, and it specifies the security measures associated with each category.
+
+#### How may data come into contact with third parties and outsourced or subcontracted projects? How are these interactions protected and monitored?
+
+The VTEX infrastructure is completely reliant on third-party providers, which ensures external partners do not have access to tenant data. See the full list of subprocessors at [VTEX Subprocessors](https://vtex.com/us-en/privacy-and-agreements/subprocessors/).
+
+Secure data processing and transmission to third parties is a key priority for VTEX. We use a comprehensive approach that combines advanced technology, rigorous security processes, and continuous employee training. Technical measures, such as robust encryption, are used to protect data during transmission and processing. Also, we have implemented strict information security processes and access controls to ensure that only authorized individuals have access to the data. Among other measures, we constantly invest in updates and improvements to ensure effective protection for the data that is shared with external partners. You can learn more about our current security measures in[ Security Practices](https://vtex.com/us-en/security/security-practices/).
+
+#### Can you guarantee that data does not migrate beyond a defined geographical region?
+
+Currently, most of the data stored by VTEX is based on AWS us-east-1. This means that the client can't define the geographical region. On the other hand, it also means that VTEX won't migrate the data outside that region unless it's authorized by the client.
+
+#### Does VTEX use data anonymization?
+
+VTEX has been using tokenization to anonymize data. This mechanism replaces any sensitive piece of data with a different value, ensuring the original data is completely unrecoverable.
+
+#### What ports and protocols does VTEX use to transfer data? How are they protected?
+
+VTEX doesn't transfer data through servers. All our data is transferred using HTTPS over port 443. All sensitive data is stored with encryption. Data in transit is encrypted with TLS 1.2; data at rest is encrypted using the AES-256 or RSA algorithms with keys of at least 2048 bits.
+
+### Encryption
+
+#### What are the encryption options in transit and at rest?
+
+VTEX has defined encryption standards that apply to all clients for data at rest and data in transit. To meet the requirements of certifications such as PCI and SOC 2, VTEX keeps user data encrypted at all times, both in storage and in transit.
+
+Data in transit is protected by the TLS 1.2 security standard. Connections that use older and less secure encryption methods are denied.
+
+When working with storage or data at rest, VTEX can use one of the following algorithms to support applications that need to encrypt data:
+
+* Two-way encryption
+    * RSA with keys of 2048 bits or more
+    * AES-256
+* One-way encryption
+    * PBKDF2 based on SHA-256
+
+All relevant systems make automatic backups at a daily frequency by default, but this can be adjusted as necessary to ensure data integrity and availability.
+
+#### Are the encryption keys stored in a secure place?
+
+To guarantee a high level of security, the encryption keys are provided by the AWS service, which is recognized for its reliability and robustness in terms of security. Moreover, access keys are stored in a separate environment with adequate encryption to guarantee data confidentiality and integrity.
+
+Login passwords are a good example: before being stored, passwords are hashed using PBKDF2 based on SHA-256. During this process, only the resulting hash value is stored, ensuring that the original passwords remain secure and are not directly accessible. These additional security measures guarantee sensitive data is protected and give users peace of mind about the confidentiality of their information.
+
+### Access control, identification, and authentication
+
+#### Does VTEX have a logical access management policy? Provide an overview of how your access management controls work.
+
+VTEX manages logical access efficiently to guarantee adequate control and monitoring of access permissions to systems and data.
+
+Our practices ensure compliance with security policies and include measures such as the principle of least privilege and segregation of duties, which means that users will only have access to the information they need in order to fulfill their specific responsibilities based on legitimate needs.
+
+Our access revocation procedure is triggered immediately, with the direct involvement of the VTEX Security team.
+
+In the corporate environment, we have an access management policy that was developed based on industry best practices, including implementing two-factor authentication to access our servers and VPN, when necessary.
+
+#### How is access provisioning managed in VTEX internal systems?
+
+In the corporate environment, a centralized team handles access management, from granting to revoking access. This team establishes metrics and executes the procedures.
+
+Specific groups within this team are assigned to manage the critical systems of the company. When an employee needs access, they start the process through our centralized and automated digital service channel.
+
+The request is then evaluated to make sure that the employee needs and should receive the requested access, going through several authentication, validation, and formal approval stages before being granted.
+
+#### Does VTEX restrict access based on the principle of least privilege?
+
+VTEX restricts access based on the principle of least privilege. This means that users are given only the [access permissions](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) that are strictly required to fulfill their responsibilities, minimizing undue risk of sensitive information and increasing the security of our systems and data.
+
+#### What is the authentication and identity management architecture available on the VTEX platform like?
+
+The VTEX platform has a ready-to-use identity solution called VTEX ID. We also support the integration of [external SSO identity providers](https://developers.vtex.com/docs/guides/login-integration-guide) in the Admin and on the store website.
+
+The Admin uses [SAML 2.0](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) as authentication protocol, which allows VTEX clients to integrate an existing identity provider using that standard. The store website can be integrated with external identity providers through the[ OAuth 2.0](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) protocol.
+
+We have an [access control](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) process that includes access to production environments and other related environments.
+
+Below, we include links to more detailed technical content about our authentication controls:
+
+* [Login integration guide](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide)
+* [SAML 2 integration](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide-admin-saml2)
+* [OAuth 2.0 integration](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide-webstore-oauth2)
+
+#### What relevant authentication and identity management security resources are available on the platform? For example, password complexity, password reuse, session timeout, account blocking, password reset, and multi-factor authentication.
+
+Passwords under VTEX ID have the following requirements:
+
+* Minimum length of 8 characters + MFA token of 6 digits.
+* Minimum of 1 upper case character.
+* Minimum of 1 numeric character.
+* Minimum of 1 special character.
+* Must not match the last 4 previous passwords.
+
+Merchants can choose to [enable password expiration](https://help.vtex.com/en/tutorial/autenticacao--21CkKHLKP1o41lUpGhuRUs#aplicar-expiracao-de-senha) after a specific period of time for Admin users, which may be 15, 30, or 90 days.
+
+Another option for merchants is to integrate an external identity provider, which would allow them to define their own custom password policies. Check[ Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) for more information.
+
+If an account is blocked due to several incorrect password attempts (security measure), the legitimate user can still log in through other methods, such as an email token or [integrated social login](https://help.vtex.com/en/tutorial/configurar-login-com-facebook-e-google--tutorials_513) (Google or Facebook), which prevents potential brute force attacks from exploiting weak passwords.
+
+#### Does the VTEX platform offer single sign-on (SSO)?
+
+As an additional layer of security, we offer the single sign-on (SSO) resource, available both on the store's VTEX Admin (admin environment) and on the actual storefront for customers.
+
+Security Assertion Markup Language (SAML) has been adopted as the standard for exchanging authentication and authorization between domains. SAML 2.0, an XML-based protocol, facilitates SSO in web browsers. This protocol uses secure, digitally signed tokens, and encrypted messages to transmit data between trusted parties.
+
+For more detailed information, see the [SAML 2 integration guide](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2).
+
+#### Does the platform implement identification, access control, and segregation for client data through physical or logical controls?
+
+VTEX keeps client data segregated through robust logical controls. All our applications are multitenant and require identifying the origin store in each request, recording all the specific information of each store with the corresponding ID. This allows us to have a server infrastructure that is completely shared between all our clients.
+
+It's important to note that there is no integrated access method. Each client only has access to their own data, which ensures data security and privacy.
+
+This approach allows a fast implementation of improvements and bug fixes and efficient scalability to meet the specific needs of each client while always maintaining security and resilience.
+
+#### How is user access managed on the platform, including moving, adding, editing, and deleting accounts?
+
+Admin users are managed directly in the VTEX Admin. They are assigned roles that can contain one or more [permissions](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3), which are established by the account's [sponsor user](https://help.vtex.com/en/tutorial/what-is-the-sponsor-user--3oPr7YuIkEYqUGmEqIMSEy) or by users that have the [User Administrator - RESTRICTED](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted) role or a customized role containing the Save User [resource](https://help.vtex.com/en/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3). Learn more in the article [How to manage users](https://help.vtex.com/en/tutorial/managing-users--tutorials_512).
+
+#### Does the platform have features for managing, organizing, and customizing store management permissions?
+
+Every action on VTEX, such as accessing a page in the Admin or making an API call, is made through a request to our infrastructure. To ensure the security of these operations, we have a system, **License Manager**, that checks whether a user has the right permissions to perform an action. License Manager is based on resources and roles to simplify permission management.
+
+A resource is an entity associated with an action or information within our infrastructure. For example, the Product management resource allows a user to access and edit product information in **Catalog**. For a detailed description of each available resource, see [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
+
+A [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) determines the set of resources accessible to a group of users on VTEX. Each administrative user can be associated with one or more roles. When creating a new role, you can use one of the [predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy) provided by VTEX or [create a custom role](https://help.vtex.com/en/tutorial/roles--jGDurZKJHvHJS13LnO7Dy), selecting each required resource.
+
+### Platform security
+
+#### Does the platform use Secure Sockets Layer (SSL) certificates?
+
+Secure Sockets Layer (SSL) is a protocol developed to increase the security of data transmitted over the internet. SSL connections are particularly recommended for sending information such as credit card numbers, passwords, and any other sensitive data over the internet.
+
+A merchant doesn't need to buy an SSL certificate. VTEX generate an SSL certificate for your store and guarantees its automatic renewal. The certificate is issued through Let's Encrypt and VTEX is responsible for creating it at the store's go-live. Learn more in[ Security certificate (SSL)](https://help.vtex.com/en/tutorial/certificado-de-seguranca-ssl--tutorials_1308).
+
+#### How are security patches managed?
+
+Our clients are not responsible for applying patches. VTEX has a patch management process that ensures all tenants use the same software version.
+
+VTEX manages software releases as major, minor, and patch updates. Patches and minor updates don't impact API contracts and can be released to all customers without affecting store operation.
+
+Operating system and application components, such as libraries, are regularly updated and undergo rigorous security checks.
+
+#### Is the platform monitored in terms of performance evaluation? Which variables define platform scalability?
+
+The VTEX platform is a SaaS (Software as a Service) solution and can be accessed using any web browser. VTEX launches and updates the solution regularly with new features and fully monitors system health. In addition, specialized teams ensure platform scalability by constantly monitoring the performance of each store.
+
+#### Does the platform restrict access to public internet IPs?
+
+Blocking access to the store administrative environment (VTEX Admin) for specific IPs is possible. However, the store website is always open to the general public. To request specific blocking, please contact [Support](https://help.vtex.com/en/support).
+
+#### Does the solution use a secure protocol (HTTPS)?
+
+The VTEX platform uses the secure HTTPS protocol, which ensures that communication between the system components is protected and that data is transmitted securely.
+
+#### Does the solution use a Web Application Firewall (WAF)?
+
+We offer a [WAF](https://help.vtex.com/en/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn) solution as part of the [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) add-on product. To learn more, check the WAF documentation.
+
+#### Does the VTEX platform use an API-first approach?
+
+VTEX prioritizes API-first development, and all data exchanged within the platform can be manipulated using APIs. Learn more about [VTEX APIs](https://developers.vtex.com/docs/api-reference).
+
+VTEX segregates the backend, API, frontend, and component layers to ensure all interactions stay within their relevant layer. Developer support documentation is available on the [Developer Portal](https://developers.vtex.com/).
+
+#### Does the solution provide anomaly detection, that is, does it have the ability to detect unusual behavior and potentially malicious traffic, as well as user account behavior?
+
+The VTEX platform is constantly monitored by a monitoring system that is managed by the VTEX Security team. We have a comprehensive set of controls that covers the entire platform and is constantly connected to the systems to detect a wide range of anomalies. Monitoring is an ongoing and gradual effort, and the designated team is constantly working to add new rules and alerts.
+
+Some of these alerts are forwarded to our internal teams, while others are directly sent to store administrators. Yet, other alerts are only logged and do not trigger notifications. For example, failed login attempts are limited and logged but don't trigger alerts. However, the account owner will receive an email if a user tries to modify administrative credentials.
+
+The [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) add-on product triggers additional alerts to increase security and allow more autonomy for merchants to set up their own monitoring.
+
+#### How is the platform monitored in terms of performance evaluation? Which variables define platform scalability?
+
+Our platform is equipped with various performance indicators that alert us to potential problems. Indicators include CPU and server memory metrics, request response time, and average volume of sales. We constantly monitor a number of indicators, including the ones mentioned above, with the help of proprietary artificial intelligence (AI)-based heuristics. The AI identifies and notifies our team if there is a deviation from the expected standard.
+
+We have an engineering team available 24/7 to handle these alerts. The team is always on call and ready to act when technical issues arise, thus ensuring the stability and healthy operation of our platform.
+
+### Log auditing
+
+#### What is the minimum content of log entries recorded by the platform?
+
+All sensitive operations on the platform are automatically logged, with no option to disable this feature. VTEX stores all platform error logs in a security information and event management (SIEM) system, which the VTEX team can access for analyzing and improving the product. In addition, VTEX monitors certain patterns in the application and infrastructure logs that may indicate a potential security risk in the system, triggering alerts or even automatic countermeasures when such patterns are identified.
+
+Also, VTEX logs various operations, including author and timestamp, in[ Audit](https://help.vtex.com/en/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA) — a module available in the VTEX Admin that allows searching and investigating log history using filters. Every platform module has a dedicated development team that analyzes and determines the information logged for it. Check the list of[ events available in Audit](https://help.vtex.com/en/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
+
+#### How can VTEX clients get real-time access to all platform logs?
+
+VTEX doesn't grant access to its internal systems to protect the privacy and security of our clients, as well as to ensure compliance with applicable laws and regulations.
+
+However, we provide logs containing different[ events](https://help.vtex.com/en/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ) in[ Audit](https://help.vtex.com/en/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA) and clients can request logs for specific events via[ Support](https://help.vtex.com/en/support). Clients also have the option of implementing a reverse proxy layer before VTEX that would allow them greater visibility over the requests that reach their environment. This approach gives clients a more detailed and customized control over the data flow in their infrastructure, while maintaining privacy and security as required.
+
+### Secure development
+
+#### What secure development best practices does the company use?
+
+The software development process goes through automated steps to ensure efficiency. When a development team completes a portion of software, it gets tagged in the version control system. This automatically triggers deployment in a test environment called `BETA` or in the real production environment, known as `STABLE`.
+
+In addition to the tests experts or clients themselves run in `BETA`, automatic tests are updated to adapt to new changes in the software or infrastructure. These tests are key to detect problems that may arise in a new version or due to technical issues. This approach ensures the stability and quality of the software throughout its lifecycle.
+
+#### Are the development, staging/QA, and production environments fully segregated? Are company developers excluded from access to the production environment?
+
+Yes, all environments are fully segregated. Deployments to the production environment can only be made through the change management process, which is automated.
+
+#### Are there secure coding guidelines and standards used for application development?
+
+VTEX developers follow OWASP principles to ensure code quality and security. Peer review is mandatory, which adds another layer of quality assurance and security. Moreover, all production code has to be approved by at least two developers with security expertise.
+
+VTEX engineers use the methods outlined in OWASP Top 10 to prevent malicious code insertion. To further increase security, VTEX has implemented a code scanning system in the repository, which is reviewed by dedicated security experts.
+
+All team members are trained in secure development. Their knowledge is continually updated through periodic training and tests.
+
+#### Does the company run vulnerability analysis in libraries and software packages?
+
+Yes, VTEX has in place a vulnerability analysis process in libraries and software packages as part of its security practices. The analysis is run regularly to identify any vulnerabilities or security flaws in the libraries and packages used for software development. This proactive approach helps ensure that only secure components with no vulnerabilities are integrated into company systems, increasing the security of our solutions and protecting the data of our clients.
+
+### Physical security and data centers
+
+#### Does VTEX have security measures in place for the physical protection of devices and network equipment?
+
+The VTEX platform is a SaaS (Software as a Service) solution hosted in a highly controlled and secure environment. As part of our risk management policy, the security practices and compliance of providers is periodically reevaluated. It's important to note that VTEX is a 100% cloud commerce solution, operating exclusively on Amazon Web Services (AWS) infrastructure. We don't have our own physical servers to provide services.
+
+All data, our own and that of our clients, is hosted on AWS, one of the world's main infrastructure service providers on a public cloud. We have agreements with AWS to guarantee a baseline of physical security and environmental protection for the execution of our services. We recommend clients check the [physical security controls provided by AWS](https://aws.amazon.com/compliance/data-center/controls/?nc1=h_ls) as part of their due diligence when assessing data security on the VTEX platform.
+
+#### How does VTEX apply physical security measures for data center protection?
+
+VTEX is a company entirely based on cloud commerce, using Amazon Web Services (AWS) as our data center provider. AWS operates its data centers in compliance with [Tier III+ guidelines](https://aws.amazon.com/compliance/uptimeinstitute/?nc1=h_ls), ensuring a high standard of reliability and security.
+
+Regarding office security, VTEX has offices in several parts of the world and applies strict physical security control in all facilities. This includes monitoring and access control in all offices, supervised by a professional security team. Physical access is strictly controlled at the building entrance through surveillance systems, such as turnstiles and other electronic devices. All authorized accesses are logged to ensure complete control over entries and exits.
+
+In addition, our offices are equipped with closed-circuit television (CCTV) systems to ensure continuous surveillance and image recording in accordance with legal and compliance requirements. We also have advanced power controls and a fire suppression system installed that meet industry best practices to prevent power failures and surges, ensuring the safety and integrity of our physical facilities.
+
+#### In which countries and locations are the data centers located?
+
+VTEX mainly uses the following AWS data regions for the described purposes:
+
+* AWS Northern Virginia: Primary data storage.
+* AWS Northern California: Backup site.
+
+### Vulnerability management
+
+#### What is the frequency of the vulnerability scans run by VTEX?
+
+Vulnerability checks are continually run. Each check has to be run again until it's approved with no issues found. An auditor will accept them during recertification periods.
+
+#### Could product customizations or configurations made by clients introduce security vulnerabilities to the platform? If yes, how would such event be handled?
+
+Merchants and any implementation agency hired by them can create customizations within their own environment. If a vulnerability is detected in the VTEX system, our security and development team will quickly take action to address the issue. Due to the customizable nature of the platform, the merchant and the implementation agency are responsible for handling vulnerabilities that may arise from customizations during development. For more information, check[ Responsibilities within the VTEX ecosystem](https://help.vtex.com/en/tutorial/responsibilities-in-the-vtex-ecosystem--3vL9aWICDr3WR64DYi1fJ3#implementation-agencies).
+
+### Incident response and mitigation
+
+#### Do you have a formal incident response plan?
+
+Yes, VTEX has a formal security incident response protocol that covers the key phases of the process: preparation, incident detection, containment, eradication, recovery, and post-incident activity. This procedure also includes an integrated communication plan that is applied during all phases of the response. Moreover, we have detailed playbooks to guide the service team. We also run gray box intrusion tests annually to continually assess and increase our security measures.
+
+#### Does the company have a pentest calendar? What is the frequency of tests?
+
+Pentests are conducted every six months at VTEX. Merchants who want to conduct pentests and vulnerability scans in their environments must use the [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) add-on product. They are encouraged to share their results with VTEX, allowing our security team to address any detected issues.
+
+#### Does VTEX have an incident response procedure for data breaches that complies with personal data protection laws?
+
+Yes, the VTEX security incident response plan covers incidents related to data breach and complies with personal data protection laws. It includes guidelines for the key phases of the process: preparation, incident detection, containment, eradication, recovery, post-incident activity. This procedure also includes an integrated communication plan that is applied during all phases of the response.
+
+#### What controls does VTEX use to mitigate ransomware attacks?
+
+VTEX takes a comprehensive approach to mitigate ransomware attacks through the use of advanced antivirus systems, firewalls, and content filters to block malware. In addition, we keep regular backups of critical data to allow recovery without complying with attacker demands. We prioritize security updates and employee awareness training, alongside constantly monitoring activities to detect suspicious behavior. All these measures combined create a robust defense against the growing threat of ransomware.
+
+### Disaster recovery and business continuity
+
+#### Does VTEX have a business continuity plan?
+
+VTEX has a carefully designed business continuity plan to deal with the challenges that arise in emergencies. This plan establishes a solid foundation for quickly and effectively resuming normal operations, regardless of the nature of the emergency, ensuring a smooth transition and minimizing potential impacts.
+
+#### Does VTEX have a disaster recovery plan?
+
+VTEX has a disaster recovery plan focused on ensuring operational continuity and availability of critical resources during emergency situations. The plan covers detailed guidelines about how to act during unplanned incidents, classified as crises, which may arise from natural disasters, cyberattacks, or other disruptive events. It incorporates key recovery phases, including the definition of a recovery point objective (RPO) and a recovery time objective (RTO), as well as backup testing to ensure the plan is efficient and ready for real-life scenarios.
+
+#### Does VTEX periodically test the disaster recovery plan?
+
+The disaster recovery plan is tested at least once a year to ensure its effectiveness. We don't test the entire plan in a single event. Different components or processes that have independent lifecycles are tested based on their relevance and required frequency. However, all parts undergo an annual test.
+
+If any part of the plan is deemed ineffective, a new version of the process is developed to address the problem. Traditionally, the events that precede Black Friday and Cyber Monday give us the ideal opportunity for conducting disaster recovery tests.
diff --git a/docs/tutorials/en/roles.md b/docs/tutorials/en/roles.md
index f4af995dd..2cfdda83a 100644
--- a/docs/tutorials/en/roles.md
+++ b/docs/tutorials/en/roles.md
@@ -1,105 +1,70 @@
 ---
 title: 'Roles'
 id: 7HKK5Uau2H6wxE1rH5oRbc
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-04-08T15:21:05.110Z
-updatedAt: 2022-10-04T19:58:47.622Z
-publishedAt: 2022-10-04T19:58:47.622Z
+updatedAt: 2023-11-30T21:36:49.415Z
+publishedAt: 2023-09-26T13:32:10.280Z
 firstPublishedAt: 2020-04-08T20:52:12.334Z
 contentType: tutorial
 productTeam: Identity
-author: 127RQ7SUoFfyTh5gbXUpdM
+author: 1malnhMX0vPThsaJaZMYm2
 slug: roles
 locale: en
 legacySlug: configuring-access-profiles, access-profiles
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-Every action that takes place on the VTEX platform, such as accessing a page in the administrative interface, clicking on a button or making API calls, involves a request to our infrastructure. As it is common for administrative interfaces to be shared by several of the company’s employees, it is important to be able to limit access to critical actions within an account. In this way, the possibility of disruptions in a store’s operation is minimized and you ensure that each user will access only what they should.
 
-## What is a role?
+The **Roles** page in the VTEX Admin allows you to manage the [roles](https://help.vtex.com/en/tutorial/access-control--4rM3gyiWqtkim4Q8hOvLTC#roles) added to your store and the users associated with them. To access it, in the top bar of the VTEX Admin, click your profile avatar — indicated by your email initial letter — and then click **Account settings** > **Roles**.
 
-At VTEX, we use a system based on ** resources ** to achieve greater precision in access control. A ** resource ** is an entity associated with an action or information within our infrastructure. Whenever our systems receive a request, a security analysis is performed to ensure that the user who made it has the necessary permission. For the request to be successful, the resources associated with it must be present in the user’s account.
+From the **Roles** page, you can do the following:
 
-Currently, we work with a few hundred different features in VTEX products. To facilitate user access management by the account’s administrators, there is the concept of **Role**. To learn more details on each available resource, see [License Manager Resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
+* [Create a role](#creating-a-role)
+* [Search for a role](#searching-for-a-role)
+* [Edit a role](#editing-a-role)
+* [Delete a role](#deleting-a-role)
 
-An **Role** is a set of features designed to serve a common type of user. For example, call center operators often perform a well-defined set of tasks. If provided with the necessary [resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#), the account administrator can create a custom ** Role** with all the necessary permissions for those employees and control all of their accesses at once.
+![roles-en](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/d0c8e68b433a987fb1d0c9f031726d6f/roles-en.png)
 
-### Types of roles
+The page displays a list of all roles added to the account and their respective information in a table:
 
-When creating a new **role** for your store, you have the option of creating a custom role, selecting each necessary resource, or one of the predefined roles made available by VTEX. See this article for all [Predefined roles](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#) and associated permissions.
+| **Column** | **Description** |
+|---|---|
+| **Name** | Name that identifies the role. |
+| **Users** | Number of users with this role. |
+| **Role Type** | Type of role, which can be __Predefined__ or __Custom__. For more information on each type, see [Role types](https://help.vtex.com/en/tutorial/access-control--4rM3gyiWqtkim4Q8hOvLTC#role-types). |
+| **Products** | License Manager products included in the role. See the available products in the __Product__ column of the table in [License Manager resources](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3). |
+| **Created Date** | Date on which the custom role was created. For roles predefined or created before December 2023, no date is displayed in this column. |
 
-In case you wish to create custom roles, see more details on the [License Manager Resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
-
-## Creating a role
-
-Roles can be managed through the administrative dashboard of your VTEX account. In [Admin’s](https://help.vtex.com/subcategory/admin-overview--Se4oi5LroIII2Ei0uGAoE) sidebar menu, go to **Account settings > Account management > Roles**.
-
-![List roles](https://images.ctfassets.net/alneenqid6w5/5SsjVcIztKJQ3yxY1udwOH/8221fd52b20d28b39952ad447fa0424c/List_roles.png)
-
-This screen shows a list with all **roles** that were added for the account. In a newly created account, only the *Owner (Admin Super)* role will be listed. This role gives unrestricted access to all the **resources** of the platform.
+In a newly created account, only the *Owner (Admin Super)* role will be listed. This role gives the user unrestricted access to all native resources of the platform.
 
 <div class="alert alert-warning">
-Some products, like <a href="https://help.vtex.com/en/tracks/vtex-payment--7iCCIoIZFmd9OabU6QlmXu/1lZWKCGdy7xpYjukTLfFJL">VTEX Payment</a>, are sold separately. The resources associated with these products are not included in the <i>Owner (Admin Super)</i> role. To enable the resources associated with these products, you need to use the corresponding access roles.
+  <p>The number of users with the <em>Owner (Admin Super)</em> role should be as few as possible. In addition, make sure there is visibility and control over who is granted this access.</p>
 </div>
 
-The number of users with an *Owner (Admin Super)* role should be as low as possible. In addition, it is necessary to make sure that there are visibility and control of those who receive this access.
+## Creating a role
 
-<table>
-  <tr>
-    <td style="border-left: 4px solid #F71963;" bgcolor="#FFE6E6"> <b>Warning!</b> Unrestricted use of very permissive roles increases the risk of attacks on stores by login credentials leakage.</td>
-  </tr>
-</table>
+To create a new role, click `+ Create Role`. For details on how to complete the form, read [Creating roles](https://help.vtex.com/en/tutorial/creating-roles--qGtNQpKSSAduX94l2WZBW).
 
-For users who should not have unrestricted access to the platform, it is important to create **roles** that limit the available resources to those strictly necessary for that type of users. You can do that by clicking on **New Role**.
+## Searching for a role
 
-![New role](https://images.ctfassets.net/alneenqid6w5/1UGqU2dlXOZGUhGinBv8IN/d8b9a082f038af71a57b2813d61a9fcc/New_role.png)
+You can search for a role by entering part of its name in the search bar. The list of results will be updated in real time.
 
-This screen allows the creation of new roles. These can be based on predefined formats, created by the VTEX team to meet common scenarios in operations, or you can customize them by selecting which features of each product can be accessed by the users that have this role.
+## Editing a role
 
-By clicking on **Choose role**, the *dropdown* menu displays a list of predefined roles.
+You can edit the resources and users associated with a role. To do so, click ⫶ in the row of the role you want to edit, and then click <i class="fas fa-pencil-alt"></i> `Edit`.
 
-![Menu predefined profiles](https://images.ctfassets.net/alneenqid6w5/4XGZb5WvW216z8RfX5Vp3c/7d40a4c6d0adb10c4a4fe0723fc1bb51/last_with_shadow_Wed_Apr__8_17_01_12_-03_2020.png)
+## Deleting a role
 
-By selecting one of the listed roles, you can check which resources are included in that role, separated by product.
+To delete a role, click `⫶` in the row of the role you want to delete, and then click <i class="far fa-trash-alt"></i> `Delete`.
 
-<div class="alert alert-info">
-  To learn more details on each available resource, see <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager Resources</a>.
+<div class="alert alert-warning">
+  <p>By deleting a role, users associated with that role will lose access to the <a href="https://help.vtex.com/entutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager resources</a> from the deleted role, unless they are also assigned other roles with the same permissions.</p>
 </div>
 
-![New role saved](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/a4452a13454d847c991800db970f0a7e/New_role_saved.png)
-
-The **Call center operator** role, for example, includes a resource of the *Catalog* product that allows the user to perform operations in a store on behalf of a customer and a resource of the *OMS* that allows the user to check the status of an order.
-
-To create a custom role, the administrator can choose the **Custom** option from the **Choose role** dropdown menu. When clicking on a product in the **Choose a product** dropdown menu, all resources associated with it will be listed.
-
-![Configuring product](https://images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/d03c6a1a56b6d18039e3dcbd3b7dbb43/last_with_shadow_Wed_Apr__8_17_12_33_-03_2020.png)
-
-You can add as many products you need to the role. Just click on the **Configure Another Product** button below the products and resources list.
-
-![Configure another product](https://images.ctfassets.net/alneenqid6w5/Dsc2k29SxUDKB8t6VXScn/c0e5126dd09c37e32d94e097ffc21c84/last_with_shadow_Wed_Apr__8_17_13_09_-03_2020.png)
-
-After configuring products and resources, the administrator can choose a name for the role in **Role name**, if it is a custom setting.
-
-![Role name](https://images.ctfassets.net/alneenqid6w5/gTuv92HFXKn4jklYX0Hzj/7a6fb49f9f0a61bc0f51321c1ab1d390/Role_name.png)
-
-<table>
-  <tr>
-    <td style="border-left: 4px solid #F71963;" bgcolor="#FFE6E6"> <b>Warning!</b> It is important to choose descriptive names for the roles, in order to make clear which type of users should have that access, ideally indicating their position in the company or the activities they will perform on the platform.</td>
-  </tr>
-</table>
-
-Best management practices for roles increase operations’ security and reinforce the awareness of everyone involved with sensitive data from the store and its customers. We recommend creating roles that are analogous to the hierarchical structures of the managing organization. In this way, everyone is responsible for the information they can access.
-
-It is also possible to add users to the custom or predefined roles, by filling in the **Add users to this role** field with the user’s email. If the user does not exist, a new user will be created using the email as name as well (name and email will be the same).
-
-![Role users](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/af25bb3f499bc71be10dd1707d6ddeb6/last_with_shadow_Wed_Apr__8_17_25_08_-03_2020.png)
-
-After configuring the new role, you must save it by clicking on the blue button at the bottom of the page.
-
-![Save profile](https://images.ctfassets.net/alneenqid6w5/68NycUF3T52sg96R6HDIna/910ec9e690127479753a4b7900319afa/last_with_shadow_Wed_Apr__8_17_33_36_-03_2020.png)
-
-After you’ve created the new role, it will be listed next to the other roles. To view it, go to **Account settings > Account management > Roles** in the Admin’s sidebar menu.
+## Learn more
 
-![New list roles](https://images.ctfassets.net/alneenqid6w5/3uQ5SvsqjpFCSJimcg9naY/fc6c4356fe38252d09c804ea39b89b45/New_list_roles.png)
+* [Access control](https://help.vtex.com/en/tutorial/access-control--4rM3gyiWqtkim4Q8hOvLTC)
+* [Creating roles](https://help.vtex.com/en/tutorial/creating-roles--qGtNQpKSSAduX94l2WZBW)
 
diff --git a/docs/tutorials/en/rounding-rules.md b/docs/tutorials/en/rounding-rules.md
index 2de7197f6..0ba0027f5 100644
--- a/docs/tutorials/en/rounding-rules.md
+++ b/docs/tutorials/en/rounding-rules.md
@@ -60,16 +60,16 @@ Below you can see examples of the flows of adding, editing and deleting rounding
 
 *_Procedure for creating a rule_*
 
-![config-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/77tOZFjGCbkDjfCbPVeg4c/cf07a45f811bd5bfd6c80ddbc478c2a4/config-arrendodamento-EN.gif)
+![config-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/77tOZFjGCbkDjfCbPVeg4c/cf07a45f811bd5bfd6c80ddbc478c2a4/config-arrendodamento-EN.gif)
 
 *_Procedure for modifying a rule_*
 
-![editar-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/4vuF4QJxVCoTc4iatE1MSZ/728e6875c0ed2787808b5cd9be46a2d3/editar-arrendodamento-EN.gif)
+![editar-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/4vuF4QJxVCoTc4iatE1MSZ/728e6875c0ed2787808b5cd9be46a2d3/editar-arrendodamento-EN.gif)
 
 *_Procedure for deleting a rule_*
 
-![deletar-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/6fDPWVbwtpyCYixRinlkxp/a5420a0633b35607bb4cca0b309c4b89/deletar-arrendodamento-EN.gif)
+![deletar-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/6fDPWVbwtpyCYixRinlkxp/a5420a0633b35607bb4cca0b309c4b89/deletar-arrendodamento-EN.gif)
 
 *_Price simulation for a rule_*
 
-![teste-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/66dsqzAfz27KJgAUAaXYFp/b3d61dcf614d390d72c7e3d5418ff86e/teste-arrendodamento-EN.gif)
+![teste-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/66dsqzAfz27KJgAUAaXYFp/b3d61dcf614d390d72c7e3d5418ff86e/teste-arrendodamento-EN.gif)
diff --git a/docs/tutorials/en/sales-app-sales-performance.md b/docs/tutorials/en/sales-app-sales-performance.md
index 1e917897c..9e07c9cd6 100644
--- a/docs/tutorials/en/sales-app-sales-performance.md
+++ b/docs/tutorials/en/sales-app-sales-performance.md
@@ -23,7 +23,7 @@ You can access your store sales performance metrics by following the steps below
 2. 	Click the <i class="fas fa-bars"></i> button.
 3. 	Click **Sales Performance**.
 
-![Sales Performance (Store)](https://images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/dafd378b97bb9b972d78cd86879f6dc2/analytics_en.png)
+![Sales Performance (Store)](//images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/dafd378b97bb9b972d78cd86879f6dc2/analytics_en.png)
 
 On this page, you will have access to the following metrics:
 
@@ -37,7 +37,7 @@ On this page, you will have access to the following metrics:
 
 To view specific metrics for a sales associate, follow the steps below:
 
-![Bruna's Sales - VTEX Sales App](https://images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/5919666bcebd4123cd176461d667da02/Kate_Stewart-s_Sales.png)
+![Bruna's Sales - VTEX Sales App](//images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/5919666bcebd4123cd176461d667da02/Kate_Stewart-s_Sales.png)
 
 1. 	Click the <i class="far fa-id-badge"></i> icon.
 2. 	Select the sales associate profile and enter the password.
diff --git a/docs/tutorials/en/sales-associate-code-field-at-checkout.md b/docs/tutorials/en/sales-associate-code-field-at-checkout.md
new file mode 100644
index 000000000..375c48fba
--- /dev/null
+++ b/docs/tutorials/en/sales-associate-code-field-at-checkout.md
@@ -0,0 +1,96 @@
+---
+title: 'Sales associate code field at Checkout'
+id: 6hiRCXt5Cz250o7hBnN2Tp
+status: PUBLISHED
+createdAt: 2023-06-20T12:18:18.542Z
+updatedAt: 2023-06-20T21:50:57.120Z
+publishedAt: 2023-06-20T21:50:57.120Z
+firstPublishedAt: 2023-06-20T15:04:21.346Z
+contentType: tutorial
+productTeam: Shopping
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: sales-associate-code-field-at-checkout
+locale: en
+legacySlug: sales-associate-code-field-at-checkout
+subcategory: 
+---
+
+On VTEX, you can create a field to add the sales associate code at Checkout. It allows you to:
+- Link a particular order to a sales associate.
+- Give exclusive discounts to the customer.
+- Manage your sales associates' performance, collecting data such as the number of sales / average ticket per sales associate and sales commission ranking.
+
+<div class="alert alert-warning">
+  The <b>sales associate code</b>  field does not replace the <b>discount coupon</b> field (native on the VTEX platform). By completing the settings outlined in this article, both can be used to give discounts.
+</div>
+
+To create the field and add it to the Checkout page of your store, you need to complete three steps:
+
+1. [Creating a new data entity](#creating-a-new-data-entity)
+2. [Creating a sales associate code promotion](#creating-a-sales-associate-code-promotion)
+3. [Customizing the Checkout UI](#customizing-the-checkout-ui)
+
+## Creating a new data entity
+
+The **sales associate code** field must be added to [Master Data](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) as a new entity. To create the data entity, follow the steps below:
+
+1. In VTEX Admin, go to **Store Settings > Storefront > Master Data**, or type **Master Data** in the search bar at the top of the page.
+2. Create a new [data entity](https://help.vtex.com/en/tutorial/creating-data-entity--tutorials_1265#how-to-set-up) called *salesassociatecode*.
+3. In the new data entity, create the following fields:
+    - **Sales associate code**: with a maximum of 10 characters (Varchar10 type).
+    - **Email**: sales associate email address (Email type).
+    - **Name**: sales associate name (Text type).
+    - **Status**: indicates whether the sales associate is active or inactive (Boolean type).
+    - **Store**: identification of the store where the sales associate works (Text type).
+    - Other fields (as needed).
+
+<blockquote><ui>4. Add the information for each sales associate to the fields you created in the previous step.</ui>
+
+<blockquote><ui>5. Create a <a href="https://help.vtex.com/en/tutorial/creating-form-in-master-data--tutorials_1047">form</a> to access the information of the new <i>salesassociatecode</i> entity through the Master Data interface.</ui>
+
+## Creating a sales associate code promotion
+
+After creating the salesassociatecode entity, you need to link it to a promotion. To create a new promotion, follow the steps below:
+
+1. In the VTEX Admin, go to **Promotions > Promotions**, or type **Promotions** in the search bar at the top of the page.
+2. Create a new [regular promotion](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N). Complete the **Promotion overview** and the **To which items will this promotion apply?** fields.
+
+<div class="alert alert-info">
+  Callout Information: If you want to use the sales associate code field to give a discount on the purchase amount, complete the information in the <b>What is the type and amount of discount?</b>.
+</div>
+
+<blockquote><ui>3. In <b>To which items will this promotion apply?</b>, click the <b>utm_campaign</b> option and type <i>salesassociatecode</i>.</ui>
+
+![utm campaign codigovendedor](//images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/4886ffbd85e8e08257a5d8249a734a4f/UTM_Campaign_codigovendedor_en.PNG)
+
+<blockquote><ui>4. In <b>Restrictions and limitations of use</b>, add the other available restrictions if desired. Select the <b>Apply with other promotions</b> option.</ui>
+
+<blockquote><ui>5. Click <b>Save</b>.</ui>
+
+## Customizing the Checkout UI
+
+The last step is configuring the Checkout interface to display the **sales associate code** field.
+
+To customize this, you need to contact the partner agency that built your store and request that the new field be added, allowing the customer to enter the sales associate code and see their name displayed.
+
+Additionally, you need to complete the following steps:
+
+1. When simulating a purchase and entering the sales associate code on the Checkout page, make sure that the GET [Search Documents](https://developers.vtex.com/docs/api-reference/master-data-api-v2#get-/api/dataentities/-dataEntityName-/search) call performs the search in the entity `salesassociatecode` and returns all the information added for the sales associate. Example call: https://{accountName}.{environment}.com.br/api/dataentities/codigovendedor/search?codigovendedor=12345.
+
+<div class="alert alert-warning">
+  The <b>status</b> field must return <b>true</b>, indicating that the sales associate code is valid.
+</div>
+
+<blockquote><ui>2. Run the <a href="https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm">Update orderForm configuration</a> POST call to add the following information to the store <a href="https://developers.vtex.com/docs/guides/orderform-fields">orderForm</a></ui>:
+
+<blockquote><blockquote>- <b>marketingData</b>: In <i>"utmCampaign"</i>, enter <i>"salesassociatecode"</i>. If this information is not described, the promotion (sales associate code) will not be applied to the cart, and the field will not be displayed.
+
+<blockquote><blockquote>- <b>openTextField</b> (optional): Add notes or comments (e.g., information for commissioning filters).
+
+<div class="alert alert-warning">
+  Only the sales associate name should be displayed on the Checkout page.
+</div>
+
+After completing all the above steps, the **Sales associate code** field will be available on the Checkout page.
+
+![Sales associate code](//images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/6f6627b73ef728a83841ed4017256925/Checkout_UI_-_EN_2.png)  
diff --git a/docs/tutorials/en/sales-associates-instore-beta.md b/docs/tutorials/en/sales-associates-instore-beta.md
index 70beca28e..c6fc8a123 100644
--- a/docs/tutorials/en/sales-associates-instore-beta.md
+++ b/docs/tutorials/en/sales-associates-instore-beta.md
@@ -29,7 +29,7 @@ This page allows you to manage your sellers from the following actions:
 * [Edit](#editing-sales-associate-information)
 * [Delete](#deleting-a-sales-associate)
 
-![vendedores-en](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/da3c90c0dfb50c0b5c40b9743b421c8b/image.png)
+![vendedores-en](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/da3c90c0dfb50c0b5c40b9743b421c8b/image.png)
 
 The page displays the following information: 
 
@@ -52,7 +52,7 @@ You can add a sales associate by following the steps below:
 
 After creation, the sales associate will receive a confirmation email and will be redirected to the sales associate's login option in the inStore app.
 
-![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+![email-vendedor-pt](//images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
 <div class ="alert alert-warning">
 <p>Sales associates registered in inStore cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.</p> 
diff --git a/docs/tutorials/en/sales-performance.md b/docs/tutorials/en/sales-performance.md
index 5a7b24203..95f643701 100644
--- a/docs/tutorials/en/sales-performance.md
+++ b/docs/tutorials/en/sales-performance.md
@@ -3,8 +3,8 @@ title: 'Sales Performance'
 id: 3DMube0sEsK9vPcRYGas72
 status: PUBLISHED
 createdAt: 2021-10-19T12:49:42.165Z
-updatedAt: 2022-12-20T14:05:11.128Z
-publishedAt: 2022-12-20T14:05:11.128Z
+updatedAt: 2023-11-09T19:56:56.074Z
+publishedAt: 2023-11-09T19:56:56.074Z
 firstPublishedAt: 2021-10-19T12:55:27.227Z
 contentType: tutorial
 productTeam: Others
@@ -26,7 +26,7 @@ To access the page, go to __Dashboards__ and click on __Sales performance__.
 
 You can customize the view of chart and list data by filtering by period, dimensions and metrics.
 
-![Sales Perf Dash EN](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
+![Sales Perf Dash EN](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
 
 ## Data 
 
@@ -36,7 +36,9 @@ To ensure that you have access to the latest updated data as well as to all of y
 
 These groups are also processed by different systems, which may cause a difference between the data of the OMS and Sales Performance. Although, we do aim for a maximum of 5% divergence.
 
+<div class ="alert alert-warning">
 The revenue metric may differ from the average ticket metric recorded in the OMS and Sales Performance, for example. This is because Sales Performance considers an order's item values, while OMS also considers discounts, freight, fees, and promotions applied to the order, which may increase or decrease its final total.
+</div>
 
 ## Period
 
@@ -152,7 +154,7 @@ In addition to applying filters, you can also perform the actions below.
 
 ## Views
 
-![Sales perf update EN](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
+![Sales perf update EN](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
 
 The Sales Performance dashboard can be customized by applying different filters and selecting the metrics that will be displayed in the chart and in the list. To facilitate your data exploration on a daily basis, we have created views, which save the filters and metrics applied on the page for your direct viewing. You can save, edit, and share different dashboard views. The page comes with the following views configured by default:
 
diff --git a/docs/tutorials/en/scheduled-delivery.md b/docs/tutorials/en/scheduled-delivery.md
index 1c103bbde..9f15d8ad9 100644
--- a/docs/tutorials/en/scheduled-delivery.md
+++ b/docs/tutorials/en/scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'Scheduled delivery'
 id: 22g3HAVCGLFiU7xugShOBi
 status: PUBLISHED
 createdAt: 2021-04-19T13:26:44.564Z
-updatedAt: 2021-10-27T16:49:43.778Z
-publishedAt: 2021-10-27T16:49:43.778Z
+updatedAt: 2024-03-25T19:12:45.519Z
+publishedAt: 2024-03-25T19:12:45.519Z
 firstPublishedAt: 2021-05-24T17:01:23.885Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,6 +21,10 @@ The delivery time frames that are available to customers are called delivery win
 
 If this is the case, you can enable scheduled deliveries by configuring delivery windows and setting the delivery capacity for each of them. To do that, access the Scheduled delivery section on the Shipping Policy page.
 
+<div class="alert alert-warning">
+For <a href="https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a> and <a href="https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Delivery capacity</a> to perform correctly, you must follow the rules below:<p><ul><li>The result from {<a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {shipping policy ID} cannot exceed 60 characters.</li><li>Do not use spaces in <a href="https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">shipping policy IDs</a>.</li></ul></p>
+</div>
+
 Once you've enabled the __Scheduled Delivery__ feature in the Shipping Policy, you can fill in the fields that will determine how it will work. Fill them to define the [maximum delivery time](#maximum-delivery-time), the [delivery window](#delivery-window), and the [delivery capacity limit](#delivery-capacity).
 
 For more information, read our article on [Shipping policies](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140).
diff --git a/docs/tutorials/en/scheduling-features-for-special-events.md b/docs/tutorials/en/scheduling-features-for-special-events.md
index 369c96241..7b8f7930e 100644
--- a/docs/tutorials/en/scheduling-features-for-special-events.md
+++ b/docs/tutorials/en/scheduling-features-for-special-events.md
@@ -70,7 +70,7 @@ To schedule content, follow the steps below:
 3. Use the URL field in the top corner to navigate to the page that displays the block whose content you want to overwrite.
 4. Select the block for which you want to create new content. You can select it using the list on the right side or the interface:
 
-![seta-interface](https://images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
+![seta-interface](//images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
 
 5. Click `Configurations` in the upper right corner.
 6. Click the `New content` button.
diff --git a/docs/tutorials/en/search-behavior.md b/docs/tutorials/en/search-behavior.md
new file mode 100644
index 000000000..e205e2d25
--- /dev/null
+++ b/docs/tutorials/en/search-behavior.md
@@ -0,0 +1,135 @@
+---
+title: 'Search behavior'
+id: B9o3JbV6utAinBJ1ETujs
+status: PUBLISHED
+createdAt: 2024-06-27T17:30:43.356Z
+updatedAt: 2024-06-27T17:33:21.153Z
+publishedAt: 2024-06-27T17:33:21.153Z
+firstPublishedAt: 2024-06-27T17:33:21.153Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: search-behavior
+locale: en
+legacySlug: search-behavior
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+The Search Engine is the core of VTEX Intelligent Search's intelligence. It interprets the search term and displays a filtered and ordered list of products. This tool allows a more objective search through indexing and treatment of the catalog data.
+
+This feature is included by default in VTEX Intelligent Search and covers the vast majority of scenarios. However, you can also adjust the Search Engine to improve search results. This guide covers the following:
+
+* [Standard search behavior](#standard-search-behavior)
+* [Search behavior configuration](#search-behavior-configuration)
+* [Alternative ways to search](#alternative-ways-to-search)
+
+## Standard search behavior
+
+The following are characteristics of Intelligent Search's standard behavior.
+
+### Autocorrect
+
+Users can make spelling mistakes when searching. The tool interprets these misspellings and shows similar products.
+
+The search engine performs an automatic correction for each search based on the items added to the catalog. For each search term, a specific number of wrong characters is allowed. The number of accepted misspellings is called _fuzzy_.
+
+The _fuzzy_ varies depending on the length of the search term. By default, if the term is 3 to 5 characters long, the _fuzzy_ applied will be 1, which means that 1 misspelled character is allowed. For terms of 6 characters or more, the _fuzzy_ applied will be 2.
+
+The predicted misspellings considering *fuzzy* = 1 are:
+
+* Add 1 more character.
+* Remove 1 character.
+* Change 1 character.
+* Swap 2 characters that are next to each other.
+
+Example: Suppose a customer wants to search for the term `ball`. Using the default configuration (*fuzzy* = 1 for terms of 3 to 5 characters), the search engine will return results for `ball` in any search that contains accepted errors, such as:
+
+* `bawll` (add 1 more character)
+* `bal` (remove 1 character)
+* `balk` (change 1 character)
+* `abll` (swap 2 characters next to each other)
+
+<div class ="alert alert-info">
+  <p>Blank spaces are not considered in <em>fuzzy</em>, so <code>base ball</code> will not be corrected to <code>baseball</code>. We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">synonyms</a> for such cases.</p>
+</div>
+
+### Minimum result
+
+The minimum number of results displayed for any search is 1. If a search does not meet this minimum, [autocorrect](#autocorrect) is applied.
+
+In a search with multiple terms, the following logic occurs:
+
+1. If the minimum result is not reached even after the initial autocorrect, the search starts to include more comprehensive results containing any of the search terms. For example, if a user searches for "nike sneakers" and the catalog doesn't have any products matching that name, the search will return products with only the term "sneakers" instead.
+2. If the comprehensive search doesn't return the minimum result, the process will be repeated, applying autocorrect again to each term.
+
+<div class= "alert alert-warning">
+  <p>Searches with multiple terms are more efficient when customers sort the results by relevance, as such sorting can return more results than the initial search context. When sorted by relevance, items with multiple terms are prioritized. However, with other sorting criteria, such as price or bestsellers, the result ranking is based on these numerical values and does not necessarily prioritize items that match more search terms.</p>
+</div>
+
+### Pagination limit
+
+VTEX Intelligent Search limits the search results to 50 pages, which encourages the customer to use filters, creating a more relevant and focused experience.
+
+## Search behavior configuration
+
+There is a set of settings that change the products that are displayed in search results and their order. In the following sections, you will see the main definitions that affect search behavior.
+
+### Defining searchable fields
+
+Determines which product information is searchable. From this configuration, every search in the search bar checks the content of these fields to generate search results. Check the following table to understand which information is searchable by default and the other configuration options:
+
+| Information | Configuration |
+| - | - |
+| Product name, brand, product ID (`ProductID`), product reference code (`ProductRefID`), SKU ID (`SKUID`), SKU reference code (`SKURefID`), and EAN  | This information is searchable by default in VTEX Intelligent Search. To remove any of this information, please contact our [Support](https://help.vtex.com/support?/cultureInfo=en-us). |
+| Product and SKU specifications | To include the desired specifications as searchable fields, you must configure the **Searchable specifications** option in the VTEX Admin, under **Intelligent Search > Search Settings**.<br /><br /> For example, if a shirt doesn't have the color in the product name or SKU, by default, Intelligent Search won't identify this attribute in a search for "blue shirt", displaying shirts of different colors as results. However, if the color specification is configured as searchable, the search will likely return blue shirts at the top of search results.<br /><br /> For more details about defining searchable specifications, check out the [Search configuration](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#general-settings) guide. 
+<br /><br /> Learn more about specifications in [Product and SKU specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP). |
+| Manufacturer code (`ManufactureID`) | Please contact our [Support](https://help.vtex.com/support?/cultureInfo=en-us) to set this field as searchable. |
+
+For example: The "color" specification is set as searchable and the product was added with the name "Nike Total 90 Sneakers" and the color "black". If a customer searches for "Black Sneakers", the tool will return products that have the term "sneakers" and the color "black" at the top of search results.
+
+You can include special characters ( `-` and `/`) when searching for a product.
+
+<div class="alert alert-warning">
+	<p>Choosing the search fields affects the <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">merchandising rule</a> options, as only searchable fields can be used to set up the rules. For example, if you set only the <strong><code>SKUID</code></strong> field as searchable, you cannot promote a<strong><code> ProductID</code></strong> or a <strong><code>ProductRefID</code></strong> using merchandising rules. </p>
+</div>
+
+### Defining and sorting filter fields
+
+In all search results, users can select filters. Some filters are pre-defined by default, but it is also possible to create more filters to meet  store needs. The display order is also customizable. Example: In a search results list, there can be filters for Price, Categories, and Brand.
+
+### Configuring relevance
+
+Relevance is the ordering principle of search results. In this section, you can assign weights and prioritize certain criteria in the Search Engine, such as popularity, release date, and promotions. The relevance of a product is composed by the combination of weights and priorities defined by each merchant.
+
+_For example_: a merchant configured that "promotion" has greater relevance than other criteria. When a customer searches for "t-shirt", the tool might display the t-shirts on sale at the top of search results, depending on the weights assigned to other criteria.
+
+For more information on how to customize the order of results to meet your store's needs, read the article [Relevance settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+<div class="alert alert-info">
+	<p>When using Intelligent Search, two options define the sorting order of your collections. By using the <code>map=productClusterIds</code> command, you are setting the order of your collections to be the one pre-defined by the merchant, with its relevance criteria. If you choose to use <code>productClusterNames</code>, you are setting that you want your collections to follow Intelligent Search's own relevance standards.</p>
+</div>
+
+## Alternative ways to search
+
+It is possible to search by the ID of one or more items in the search bar or by adding search parameters (*query*) in the store URL.
+
+### Partial match
+
+By entering the exact first digits of the product ID (`ProductID`), product reference code (`ProductRefID`), SKU ID (`SKUID`), SKU reference code (`SKURefID`), or EAN in the search bar, Intelligent Search will partially match products and SKUs active in the store, adding them to the search results.
+
+For example, if the product ID is `123456789` and you search for `123`, it will be listed in the search results. However, the product will not be displayed if the search is `234` and does not include any of the first ID numbers.
+
+### URL
+
+To search from your store URL, add search parameters (*query*) at the end of the store URL, respecting one of the following structures:
+
+- Example for searching an item: `[account address]/[id type]:[id_1]?q=[id type]&map=ft`
+- Example for searching a list: `[account address]/[id type]:[id_1];[id_2];[id_3]?q=[id type]:[id_1];[id_2];[id_3]&map=ft`
+
+The possible value types for the ID type field are `product.id`, `sku.id`,`sku.ean`, `sku.reference`, or `id` (ProductID, ProductRefID, SKUID, SKURefID, and EAN). All searched IDs should be of the same type.   
+
+- **Search by SKU ID:**  `?q=sku.id:<id>` or `?q=sku:<id>`
+- **Search by EAN:**  `?q=sku.ean:<id>`
+- **Search by reference ID:**  `?q=sku.reference:<id>`
+- **Search by slug:**  `?q=product.link:<link>`
+- **Search by product ID:**  `?q=product:<id>` or `?q=product.id:<id>`
diff --git a/docs/tutorials/en/search-configuration.md b/docs/tutorials/en/search-configuration.md
new file mode 100644
index 000000000..ad183ed96
--- /dev/null
+++ b/docs/tutorials/en/search-configuration.md
@@ -0,0 +1,52 @@
+---
+title: 'Search configuration'
+id: 1yNCDwz0k77ovSGqkTbZMv
+status: PUBLISHED
+createdAt: 2024-06-17T14:08:59.824Z
+updatedAt: 2024-06-17T14:10:20.364Z
+publishedAt: 2024-06-17T14:10:20.364Z
+firstPublishedAt: 2024-06-17T14:10:20.364Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: search-configuration
+locale: en
+legacySlug: search-configuration
+subcategory: 1EmKjP83dy0RWD9GzZkYsG
+---
+
+The **Search Settings** page comprises the VTEX Intelligent Search general settings. To access it in the VTEX Admin, go to **Store Settings > Intelligent Search > Search Settings**. The page is divided into two sections: [General Settings](#general-settings) and [Facet Settings](#facet-settings).
+
+## General settings
+
+The general settings display the following options related to[ product and SKU specifications](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP):
+
+* **Use SKU specifications to display individual products in search results**: Defines which specifications will sort the SKUs in the search results.
+
+    Suppose you have a product available in two colors: blue and red. If you select the attribute "color" in this field, the search result will return two products (one blue and one red) instead of only one product.
+
+    To configure this field, click the dropdown arrow and select the specifications you want to add.
+
+    Check the guide [Detaching SKUs by specification](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE) for more details on this configuration behavior.
+
+* **Searchable specifications:** Determines which product specifications can be searched by the search engine.
+
+    For example, if a shirt doesn't have a color in the product name or SKU, by default, Intelligent Search won't identify this attribute in the search results for "blue shirt", returning shirts of different colors. However, if the color specification is set as searchable, the search can return blue shirts in the top results.
+
+## Facet settings
+
+The facet settings have settings related to the[ filters](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) displayed to your customers during the search:
+
+![Facet configurations](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
+
+* **Facet order:** Order in which the facets will be displayed in the store. If no facet is selected, the default order is alphabetical.
+
+    To add a facet, click `Add`, select the facet, and click `Save` to confirm.
+
+    You can change the order by dragging the three-bar icon <i class="fas fa-grip-vertical"></i> on each facet to the desired position.
+
+    To delete a facet, click the trash can icon <i class="fas fa-trash-alt"></i>.
+
+* **Hide facets:** Option that allows you to hide certain facets in the store. To hide a facet, click the dropdown menu and select the facet you want to hide.
+
+    To redisplay a facet, click the X next to its name. If you want to show all the previously hidden facets again, click the X on the right side of the field.
diff --git a/docs/tutorials/en/search-navigator-control.md b/docs/tutorials/en/search-navigator-control.md
index bbea13a73..23a061c25 100644
--- a/docs/tutorials/en/search-navigator-control.md
+++ b/docs/tutorials/en/search-navigator-control.md
@@ -52,7 +52,7 @@ For a category to be rendered by this control, it must be marked with the __Menu
 
 This flag can be found on the category registration screen.
 
-![How Search Navigator control works EN 2](https://images.ctfassets.net/alneenqid6w5/4lSSrBSvyUqEGUEw0oMiac/f132379724b8855996e6f41c2e195ce6/2018-10-23_2233_EN_2.png)
+![How Search Navigator control works EN 2](//images.ctfassets.net/alneenqid6w5/4lSSrBSvyUqEGUEw0oMiac/f132379724b8855996e6f41c2e195ce6/2018-10-23_2233_EN_2.png)
 
 <div class="alert alert-info">
   <strong>Important</strong>: The <code>&lt;vtex.cmc:searchNavigator/&gt;</code> control displays, by default, only the primary-level categories (root) and the lowest-level sub-categories, within the current context. Intermediate splits in the categories tree are omitted. 
@@ -85,7 +85,7 @@ For a product field or SKU field to be displayed on the menu by the Search Navig
 
 Both are found on the field registration screen.
 
-![How Search Navigator control works EN 3](https://images.ctfassets.net/alneenqid6w5/2qjmz7DHFaSUq00CGy0cQw/1794e1b088a4ee376627e856dab2cd86/2018-10-23_22-24-47_EN_3.png)
+![How Search Navigator control works EN 3](//images.ctfassets.net/alneenqid6w5/2qjmz7DHFaSUq00CGy0cQw/1794e1b088a4ee376627e856dab2cd86/2018-10-23_22-24-47_EN_3.png)
 
 ## Price ranges
 
diff --git a/docs/tutorials/en/searching-for-old-orders.md b/docs/tutorials/en/searching-for-old-orders.md
index 5a7a9f977..490e8b870 100644
--- a/docs/tutorials/en/searching-for-old-orders.md
+++ b/docs/tutorials/en/searching-for-old-orders.md
@@ -19,7 +19,7 @@ To search through your old orders, follow the steps below:
 
 1. In the admin's side menu, click on __Orders Management__
 2. Select __All Orders__
-3. Click on the filter button ![filter](https://images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
+3. Click on the filter button ![filter](//images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
 4. Choose a filter *by period*: __Invoiced date__, __Order date__, __Authorized date__ or **Shipping estimate**
 5. Within the chosen filter, click on the __calendar icon__, next to the text __All dates__
 6. Choose a starting date/hour and an end date/hour
diff --git a/docs/tutorials/en/searching-for-transactions-on-payments.md b/docs/tutorials/en/searching-for-transactions-on-payments.md
index a9fd391db..ebbc82dc2 100644
--- a/docs/tutorials/en/searching-for-transactions-on-payments.md
+++ b/docs/tutorials/en/searching-for-transactions-on-payments.md
@@ -35,13 +35,13 @@ To return to the original list of transactions, just delete the value previously
 
 In the Orders Management, if you click on a given order, you'll see a page with its main information. There you'll find the link _See transaction details_. Click on it to know more about the order:
 
-![Link transação OMS (EN)](https://images.ctfassets.net/alneenqid6w5/2CgW46clF6cSU0uQYGyA4s/7b61faff11c95caab8b01d65e7460c33/Link_transa____o_OMS__EN_.png)
+![Link transação OMS (EN)](//images.ctfassets.net/alneenqid6w5/2CgW46clF6cSU0uQYGyA4s/7b61faff11c95caab8b01d65e7460c33/Link_transa____o_OMS__EN_.png)
 
 ## Payment TID and Payment ID
 
 The search using these codes must necessarily contain all digits, or your search will return empty. Here's how to find them:
 
-![Códigos EN](https://images.ctfassets.net/alneenqid6w5/3TyYDhqphmKCCEGce8o6EE/6a2fe4bb481b991e2d9c0d8d25d3c3d3/C__digos_EN.png)
+![Códigos EN](//images.ctfassets.net/alneenqid6w5/3TyYDhqphmKCCEGce8o6EE/6a2fe4bb481b991e2d9c0d8d25d3c3d3/C__digos_EN.png)
 
 These values, within the transaction detail, represent the communication with the respective connector. At [transaction events](/en/tutorial/how-to-view-the-orders-details), it is possible to validate each contact made.
 
diff --git a/docs/tutorials/en/security-certificate-ssl.md b/docs/tutorials/en/security-certificate-ssl.md
new file mode 100644
index 000000000..4d74dcffb
--- /dev/null
+++ b/docs/tutorials/en/security-certificate-ssl.md
@@ -0,0 +1,26 @@
+---
+title: 'Security certificate (SSL)'
+id: tutorials_1308
+status: PUBLISHED
+createdAt: 2017-04-27T21:56:41.946Z
+updatedAt: 2023-11-16T17:44:04.092Z
+publishedAt: 2023-11-16T17:44:04.092Z
+firstPublishedAt: 2017-04-27T23:03:50.121Z
+contentType: tutorial
+productTeam: Identity
+author: authors_84
+slug: security-certificate-ssl
+locale: en
+legacySlug: hiring-the-security-certificate-sll
+subcategory: 2TNXiKzLZOPxjMTyGiEeJu
+---
+
+The SSL (Secure Socket Layer) is a protocol intended to increase the security of data transmitted on the Internet. SSL connections are particularly recommended for sending data such as credit card numbers, passwords and any other confidential information through the Internet.
+
+Whenever you access a safe web page, that is, an Internet page that is protected by an SSL certificate, a key, or a lock, appears on the status bar to indicate that the connection is safe. Traditional certificates require that you click on the key or lock in order to have access to the information of SSL certificate holders.
+
+There is no need to request the purchase of an SSL certificate. VTEX generates an SSL certificate for your store and guarantees its automatic renewal. The certificate is issued via Let's Encrypt and its creation is VTEX's responsibility at [the time of the store's Go-Live](https://help.vtex.com/en/tutorial/configuring-dns-pointing-to-vtex--tutorials_4280).
+
+<div class="alert alert-warning">
+<p>We do not recommend installing other certificates. However, if necessary, please contact our <a href="https://help.vtex.com/pt/support">support</a>.</p>
+</div>
diff --git a/docs/tutorials/en/security-education-and-awareness.md b/docs/tutorials/en/security-education-and-awareness.md
index 4fb2de995..3d4cecb8c 100644
--- a/docs/tutorials/en/security-education-and-awareness.md
+++ b/docs/tutorials/en/security-education-and-awareness.md
@@ -3,7 +3,7 @@ title: 'Security education and awareness'
 id: 5t6HaGHiHFVrCIvePJKkV6
 status: DRAFT
 createdAt: 2022-05-26T13:50:41.046Z
-updatedAt: 2022-08-18T20:43:54.577Z
+updatedAt: 2023-07-19T23:57:15.726Z
 publishedAt: 
 firstPublishedAt: 
 contentType: tutorial
@@ -15,4 +15,4 @@ legacySlug: security-education-and-awareness
 subcategory: 
 ---
 
-
+test
diff --git a/docs/tutorials/en/security-monitor.md b/docs/tutorials/en/security-monitor.md
new file mode 100644
index 000000000..402520dc4
--- /dev/null
+++ b/docs/tutorials/en/security-monitor.md
@@ -0,0 +1,130 @@
+---
+title: 'Security Monitor'
+id: 5LOVNLrrtmgSj99pM1NS4x
+status: PUBLISHED
+createdAt: 2024-04-25T00:42:30.944Z
+updatedAt: 2024-04-25T03:01:13.448Z
+publishedAt: 2024-04-25T03:01:13.448Z
+firstPublishedAt: 2024-04-25T02:41:44.798Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: security-monitor
+locale: en
+legacySlug: security-monitor
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>This feature is part of <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/br-pt/contato/">contact form</a>.</p>
+</div>
+
+Security Monitor is a dashboard that helps merchants identify and manage potential risks in their environment in real time. The tool identifies configuration risks and the behavior of admin users, then notifies merchants via email, enabling them to take preventive action against security vulnerabilities.
+
+To access the dashboard, follow the steps below:
+
+1. In the VTEX Admin, go to **Dashboards**, or type **Dashboards** in the search bar.
+2. Under **Security Monitor**, click **Security Monitor Dashboard**.
+
+![1-security-monitor-en](//images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/1593b6df63e997d6933dcfd3215d72b0/1-security-monitor-en__2_.png)
+
+Security Monitor displays the findings in three tabs based on their status:
+
+- [Open](#open)
+- [Snoozed](#snoozed)
+- [Closed](#closed)
+
+In all tabs, you can:
+
+- [Search for findings](#searching-for-findings)
+- [Filter findings by type](#filtering-findings-by-type)
+- [Edit notification settings](#editing-notification-settings)
+
+Below, you will find specific details about the information available in each tab and their related actions.
+
+## Open
+
+The **Open** tab displays the threats detected by the Security Monitor that have not yet been managed or snoozed.
+
+The top bar displays the total number of findings and the number of threats by severity level (high, medium, or low).
+
+![2-findings-en](//images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/08aac5eda3f4d38354ba6a003b72016d/2-findings-en.png)
+
+The tab displays the full list of open findings in a table, from the most recent to the oldest:
+
+| Column fields | Description |
+| --- | --- |
+| Finding | User email or application key related to the finding. |
+| Type | Type of finding detected:<br/><ul><li><strong>Old app keys:</strong> <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Application keys</a> that were created more than 6 months ago.</li><li><strong>Excessive Super Admins:</strong> Users or application keys with the <strong>Owner (Admin Super)</strong>  <a href="https://help.vtex.com/en/tutorial/role--7HKK5Uau2H6wxE1rH5oRbc" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">role</a>.</li><li><strong>Leaked App Keys:</strong> <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Application keys</a> that have been leaked on the web and identified by the VTEX Security team.</li><li><strong>Inactive Users:</strong> Users who have not accessed the Admin in the last 30 days.</li></ul> |
+| Detected | Date the finding was detected. |
+| Sensor | Sensor that detected the threat: <br/><ul><li><strong>VTEX Identity</strong></li></ul> |
+| Severity| Level of threat severity, determined by the impact or potential risk associated with the threat: <br /><ul><li><strong>High</strong></li><li><strong>Medium</strong></li><li><strong>Low</strong></li></ul> |
+| Action menu ⋮ | Menu of possible actions for the finding: <br/><ul><li><a href="#managing-findings" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Manage findings</a></li><li><a href="#snoozing-findings" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Snoozing findings</a></li></ul> |
+
+### Managing findings
+
+To manage a finding, follow the instructions below:
+
+1. In the finding row, click the ⋮ menu.
+2. Select `Manage`.
+
+   You will be redirected to the **Users** screen in **Account Management** to edit the roles associated with the specific user or application key.
+
+### Snoozing findings
+
+To move a finding to the **Snoozed** tab, removing it temporarily from the **Open** tab, follow the instructions below:
+
+1. In the finding row, click the ⋮ menu.
+2. Select  `Snooze`.
+3. Choose the number of days you want the finding to remain in the **Snoozed** tab. The options available are: **7**, **90**, or **120** days.
+4. Click `Snooze`.
+
+![3-snooze-finding-en](//images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/ae0ac9742c235ac0bc1299efd0017521/3-snooze-finding-en.png)
+
+## Snoozed
+
+The **Snoozed** tab lists the findings that have been snoozed in a table, with the same information as described in the [Open](#open) tab.
+
+In the **Snoozed** tab, the actions menu in each finding's row only displays the `Unsooze` option, which allows you to undo the snooze action and send the finding back to the **Open** tab.
+
+## Closed
+
+The **Closed** tab displays a list of findings that have been managed and are therefore closed. It displays the following information in a table:
+
+| Column fields | Description |
+| --- | --- |
+| Finding | User email or application key related to the finding. |
+| Type | Type of finding detected:<br/><ul><li><strong>Old app keys:</strong> <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Application keys</a> that were created more than 6 months ago.</li><li><strong>Excessive Super Admins:</strong> Users or application keys with the <strong>Owner (Admin Super)</strong>  <a href="https://help.vtex.com/en/tutorial/role--7HKK5Uau2H6wxE1rH5oRbc" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">role</a>.</li><li><strong>Leaked App Keys:</strong> <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Application keys</a> that have been leaked on the web and identified by the VTEX Security team.</li><li><strong>Inactive Users:</strong> Users who have not accessed the Admin in the last 30 days.</li></ul> |
+| Detected | Date the finding was detected. |
+| Closed | Date the finding was closed. |
+| Closed By | Indicates that the finding was automatically closed after being managed by an admin user. |
+| Severity | Level of threat severity, determined by the impact or potential risk associated with the threat: <br /><ul><li><strong>High</strong></li><li><strong>Medium</strong></li><li><strong>Low</strong></li></ul> |
+
+## Searching for findings
+
+In the search bar, enter the user's email address or the name of the application key to find related findings.
+
+## Filtering findings by type
+
+By clicking `Type` <i class="fas fa-chevron-down"></i>, you can choose one of the finding types to filter the results displayed in the list. Click `Apply` to confirm the chosen filter, and the list will be updated.
+
+![4-filter-findings-en](//images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/f6f39af22a936af16bde30ed57f35f99/4-filter-findings-en.png)
+
+## Editing notification settings
+
+To edit the admin users who will be notified about the findings, follow the steps below:
+
+1. Click the gear button in the top right corner of the screen.
+2. Enter the email address of the user that will receive notifications and press `Enter`. Repeat this step for as many users as you want.
+
+   To remove a user, click the `X` next to their email.
+3. Click `Save`.
+
+![5-edit-notifications-en](//images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/0c5ecc5bccd18569a94b72781632d3f2/5-edit-notifications-en.png)
+
+## Learn more
+
+* [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh)
+* [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [Users](https://help.vtex.com/en/tutorial/managing-users--tutorials_512)
+* [Application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet)
diff --git a/docs/tutorials/en/seller-management.md b/docs/tutorials/en/seller-management.md
index 3d75c1d84..6e6c973aa 100644
--- a/docs/tutorials/en/seller-management.md
+++ b/docs/tutorials/en/seller-management.md
@@ -17,7 +17,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 **Seller Management** is the page where marketplace operators [add sellers](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392), input their information, and manage their status. The page features metrics that allow marketplaces to assess their operation. It is also possible to apply filters to the seller list and group sellers using the _Group_ option. 
 
-![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 ## Metrics
 
@@ -47,7 +47,7 @@ This feature allows merchants to better monitor their operations by:
 
 You can create groups manually by clicking on Add sellers or Manage groups. Once created, you can edit and delete each one.  
 
-![Seller management](https://images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/fc25e05f46cc203be9777110c6bacbde/seller_management_en.png)  
+![Seller management](//images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/fc25e05f46cc203be9777110c6bacbde/seller_management_en.png)  
 
 ## Managing groups  
 
diff --git a/docs/tutorials/en/seller-monitoring.md b/docs/tutorials/en/seller-monitoring.md
new file mode 100644
index 000000000..a7315cabe
--- /dev/null
+++ b/docs/tutorials/en/seller-monitoring.md
@@ -0,0 +1,60 @@
+---
+title: 'Seller Monitoring'
+id: 3Gt3Zu7BPFAaTRRehi27ez
+status: DRAFT
+createdAt: 2023-07-18T19:35:09.684Z
+updatedAt: 2023-07-19T13:53:51.474Z
+publishedAt: 
+firstPublishedAt: 2023-07-18T19:55:46.688Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: seller-monitoring
+locale: en
+legacySlug: seller-monitoring
+subcategory: 2xWRgEIlR2ookieEmm4KQu
+---
+
+**Seller Monitoring** is a tool of the [Seller Management](https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv) module that allows your marketplace to evaluate seller performance. To access this page,go to your VTEX Admin > **Marketplace > Sellers > Seller Management > click the Configure Metric button**. On the home page,you will find the following sections:
+
+- **Operation health**: In this section,you will find all the data from all your sellers, including:
+  - Total active sellers
+  - Average invoicing time
+- **Overview**: Here,you will monitor the metric details with an in-depth view of the infraction that caused the seller to be classified as ⚠ **Acceptable or** ❌ **Unsatisfactory**. You can click the button (paste the button icon) to filter by seller and select only the desired sellers.
+
+When clicking the **View Orders** button,a pop-up will be displayed with the **Order ID**, **Time**, and the **View button.**
+
+|**Field**|**Description**|
+| - | - |
+|**Order ID**| Code that is automatically generated for each order placed in the marketplace.|
+|**Time**| Amount of time that order has been pending invoicing.|
+|**View**|Redirect button, which will redirect you to the OMS order details.|
+
+If you are accessing the tool for the first time,you will need to set up the **Invoicing time** metric to set the maximum and preferred time for seller orders to be invoiced. Configuration steps are presented below.
+
+## Configuring metrics
+
+Follow the steps below to configure metrics.
+
+1. In your VTEX Admin, go to **Marketplace > Sellers > Seller Management > Configure metric.**
+2. Click **Invoicing Time** and fill in the fields.
+3. Click **+ Add Variation** and fill in the required fields to set up variations for a segment or a group of sellers.
+4. Click **Save**.
+
+When you click **`Save`**, you will receive notifications in the Admin about the seller performance in your operation. You will also have visibility of the sellers not meeting the expected deadlines.
+
+|**Field ( * required)** |**Description**|
+| - | - |
+|**Value limit***|Value limit set to measure whether or not the seller is meeting your marketplace's standards.|
+|**Segmentation***|You will define which sellers or seller groups will be affected by the value set in **Time limit.**|
+|**Preferred limit**|The set time to warn that the seller is reaching the **Time limit.**|
+
+When variation is configured in a metric, the ordering defines the priority. For cases where there is only one segmentation per group and one per exception, there is no conflict, regardless of the order.
+
+## Editing metrics
+
+After being configured, metrics can be edited. Follow the steps below:
+
+1. Click the **Edit metric** button.
+2. Change the values in the fields that will be displayed.
+3. Click **Save**.
diff --git a/docs/tutorials/en/seller-portal-creating-a-promotion.md b/docs/tutorials/en/seller-portal-creating-a-promotion.md
new file mode 100644
index 000000000..a1df04050
--- /dev/null
+++ b/docs/tutorials/en/seller-portal-creating-a-promotion.md
@@ -0,0 +1,102 @@
+---
+title: 'Seller Portal: Creating a promotion'
+id: kzNPEaiJE8EWkDzO9dbBI
+status: PUBLISHED
+createdAt: 2023-09-01T15:28:13.875Z
+updatedAt: 2023-11-16T18:06:30.499Z
+publishedAt: 2023-11-16T18:06:30.499Z
+firstPublishedAt: 2023-09-01T16:58:54.457Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: seller-portal-creating-a-promotion
+locale: en
+legacySlug: seller-portal-creating-a-promotion
+subcategory: 4hisB47iAVZk4r3SEmMoG
+---
+
+To create a new promotion as a seller in the Seller Portal, follow the steps below:
+
+1. In the VTEX Admin, go to **Products > Promotions > Promotions **or type **Promotions** in the search bar at the top of the page.
+2. Click `Create Promotion`.
+3. Complete the [Promotion fields](#promotion-fields).
+4. Click `Save`.
+5. Review your promotion configuration before publishing it.
+![seller-portal-promo-revisao-en](//images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/cde8b71b347ade7c49aed0056cb8f134/image.png)
+6. After reviewing the details, click `Confirm`.
+
+Then, the promotion will be activated and applied to your store.
+
+<div class = "alert alert-info">
+When multiple promotions apply to the same cart items, the Promotions module applies the one offering the highest discount to benefit the customer.
+</div> 
+
+## Promotion fields
+
+### General
+
+In this section, you need to configure your promotion's general information.
+
+![seller-portal-promo-geral-en](//images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/c1148e5222e0a6e990c10371a00547f0/image.png)
+
+* **Name:** Promotion name.
+* **Status:** Option that defines whether the promotion is active <i class="fas-toggle-on"></i> or inactive <i class="fas-toggle-off"></i>.
+* **Description:** An internal description of the promotion. The purpose of this field is to be used as internal communication in your store to indicate whether the promotion comes from a campaign, clearance sale, etc.
+* **Start date:** Start date of the promotion. You can set a future date for the promotion to start on your website. If that is the case, the promotion will be in the **scheduled** status until the start date is reached.
+* **End date:** End date of the promotion. As long as the end date is valid, the promotion will maintain its active status. Once the end date is reached, the discount will be automatically deactivated.
+* **Start time:** Start time of the promotion.
+* **End time:** End time of the promotion.
+
+### Discount type
+
+Section that defines the discount type and amount that will be applied in the promotion. See the discount options below:
+
+![seller-portal-promo-tipo-desconto-en](//images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/d9d72c7fc562111e4e454a4b2df35b09/image.png)
+
+#### Price
+
+* **Percentage:** Percentage discount that will be applied to the product price.
+* **Maximum price per item:** The maximum price for each eligible item will be the price set above. This option will only apply to products priced higher than the amount configured.
+
+#### Shipping
+
+* **Free shipping:** Discount on the full shipping cost of the items eligible for the promotion.
+* **Percentage:** Percentage discount that will be applied to the shipping cost.
+* **Maximum shipping:** Sets a maximum amount for the shipping cost. If there is a shipping option cheaper than the maximum value configured, the lower cost will be charged.
+
+### Eligible products
+
+In this section, you need to choose whether the promotion will apply to all your store products or only specific products, as in the image below.
+
+![seller-portal-promo-produtos-elegiveis-en](//images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/dacb5c26ee3d3fd9f066617340a7d861/image.png)
+
+* **All products:** Applies the promotion to your whole catalog.
+* **Products that meet all the following rules:** Limits your promotion to specific products based on the following rules:
+  * **Product, Category, Brand, SKU:** Option that defines the criterion for selecting products.
+    * `is one of`: Includes the product selection criterion.
+    * `is not one of`: Excludes the product selection criterion.
+
+After defining the selection criteria, enter the name of the items to be included or excluded.
+
+To add more than one selection rule, click `+ Add Rule`. If more than one rule is configured, only items that meet both rules will have the discount applied.
+
+To remove a rule, click <i class="fas-trash-can"></i> `Remove rule`.
+
+### Conditions
+
+The order must meet all the conditions specified in this section for the promotion to apply.
+
+![seller-portal-promo-condicoes-en](//images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/08cb480d481c4787c8e077b6055980a3/image.png)
+
+* **Item price:** The discount will apply only to items within the specified price range.
+* **Shipping method:** The discount will apply only if the customer selects the same shipping method specified in the promotion.
+* **Shipping country:** The discount will apply to items shipped to the countries selected in this field.
+* **Shipping postal code:** The discount will apply if the shipping postal code meets the configured rule. You can add more than one postal code range to include or exclude more zones.
+
+### Restrictions
+
+The promotion will be limited by the following criteria:
+
+![seller-portal-promo-restricoes-en](//images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/8aab96f2312f7a40532d717b51e355bb/image.png)
+
+* **Limit the number of eligible items per cart:** Defines the maximum number of items in the cart that will be affected by the promotion. If the cart has more items than the limit, the discount will only be applied to the number of items configured in this field.
diff --git a/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
index a9bee80b6..1a6afd936 100644
--- a/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
@@ -27,7 +27,7 @@ The Seller Portal enables marketplaces to:
 - Decrease sales conversion time with self-service onboarding of new sellers, which is now faster and frictionless.  
 - Easily share product assortment with the seller and quickly manage shared product offers.  
 
-![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 ## Seller and marketplace interaction in the Seller Portal
 
diff --git a/docs/tutorials/en/seller-portal-product-details.md b/docs/tutorials/en/seller-portal-product-details.md
index ff553bb26..01484736f 100644
--- a/docs/tutorials/en/seller-portal-product-details.md
+++ b/docs/tutorials/en/seller-portal-product-details.md
@@ -15,7 +15,7 @@ legacySlug: seller-portal-product-details
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
-![Shared products product details EN](https://images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/cc3f300460749e515607a49f6e6d2bc2/Shared_products_product_details_EN.jpg)
+![Shared products product details EN](//images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/cc3f300460749e515607a49f6e6d2bc2/Shared_products_product_details_EN.jpg)
 
 On the product details page of the [Shared Products](https://help.vtex.com/en/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) module, you can view all information about a specific product, including: 
 
diff --git a/docs/tutorials/en/seller-portal-promotions.md b/docs/tutorials/en/seller-portal-promotions.md
new file mode 100644
index 000000000..060fb08de
--- /dev/null
+++ b/docs/tutorials/en/seller-portal-promotions.md
@@ -0,0 +1,97 @@
+---
+title: '​​Seller Portal: Promotions'
+id: 73LL7Ja0P4JbD77AH0jHwu
+status: PUBLISHED
+createdAt: 2023-10-03T16:07:24.166Z
+updatedAt: 2023-10-03T21:29:14.851Z
+publishedAt: 2023-10-03T21:29:14.851Z
+firstPublishedAt: 2023-10-03T21:26:29.611Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: seller-portal-promotions
+locale: en
+legacySlug: seller-portal-promotions
+subcategory: 4hisB47iAVZk4r3SEmMoG
+---
+
+The **Promotions** page in the Seller Portal allows you to view and manage the complete list of existing promotions, streamlining seller promotion management. Go to **Promotions > Promotions** in the VTEX Admin to access the page.
+
+![seller-portal-promo-en](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/9bef7119b64fec9b074b7f20f6659985/image.png)
+
+From the promotion list in the Seller Portal, you can do the following:
+
+* [Create a new promotion](#creating-a-new-promotion)
+* [Search for promotions](#searching-for-promotions)
+* [Filter promotions](#filtering-promotions)
+* [Export promotions](#exporting-promotions)
+* [View promotion usage data](#viewing-promotion-usage-data)
+* [Access the promotion action menu](#accessing-the-promotion-action-menu)
+* [View archived promotions](#viewing-archived-promotions)
+
+The **Promotions** page displays the following information in a table:
+
+| Column     | Description           |
+| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Name       | Promotion name and description.            |
+| Start Date | Date the promotion will apply.       |
+| End Date   | Date the promotion will end.      |
+| Status     | Promotion status, which can be:<br><br>-  **Active:** If the promotion is activated and applied in the store.<br>-  **Scheduled:** If the promotion has been scheduled.<br>-  **Paused:** If the promotion is paused.<br>-  **Completed:** If the promotion is completed. |
+
+## Creating a new promotion
+
+To create a new promotion, click the `Create Promotion` button. For more information, read the guide [Seller Portal: Creating a promotion](https://help.vtex.com/en/tutorial/seller-portal-creating-a-promotion--kzNPEaiJE8EWkDzO9dbBI).
+
+## Searching for promotions
+
+To search for a specific promotion in the list, you can use the search bar to search by name and description.
+
+## Filtering promotions
+
+You can filter the promotions in the list using the following information:
+
+* **Status**: Promotion status, which can be `Active`, `Scheduled`, `Paused`, and `Completed`.
+* **Last Modified:** Filters the latest edits in the last 12 months, 3 months, 30 days, 7 days, or the day before the query.
+
+Select the desired filters and click `Apply` to filter the promotions. To cancel the selection, click `Clear` on the desired filters.
+
+## Exporting promotions
+
+You can download a CSV file with the promotions available in your store and their respective information. To do this, click the `Export` button next to the search bar. The file content will be exported considering applied filters and does not include archived promotions.
+
+The file contains the following information about each promotion:
+
+| Column     | Description                                                              |
+| ---------- | ------------------------------------------------------------------------ |
+| ID         | Promotion ID.                                                            |
+| Name       | The promotion name.                                                      |
+| Start Date | The promotion start date.                                                |
+| End Date   | The promotion end date.                                                  |
+| Status     | Promotion status, which can be **Active**, **Scheduled**, **Paused**, and **Completed**. |
+
+## Viewing promotion usage data
+
+To view the number of active promotions in your store and the remaining quota for new promotions, click `Promotion usage`.
+
+By default, the maximum number of active promotions is 100. If you need to increase this limit, please contact [our Support](https://support.vtex.com/hc/en-us/requests) team.
+
+ ![seller-portal-promo-ativas-en](//images.ctfassets.net/alneenqid6w5/3tnyz6u3HxC6Qjezn9PvLr/6e62fdd0fa7a104df792d27d8a4496e1/image.png)
+
+## Accessing the promotion action menu
+
+By clicking the <i class="fas fa-ellipsis-v"></i> menu icon of a promotion, you can do the following:
+
+* <i class="fas fa-pencil-alt"></i> **Edit:** To edit a promotion.
+* <i class="far fa-clone"></i> **Duplicate:** To create a new promotion using the information from the existing one.
+* <i class="fas fa-archive"></i> **Archive:** To archive the promotion. The promotion will automatically move to the [Archived Promotions](#viewing-archived-promotions) page.
+
+## Viewing archived promotions
+
+To go to the **Archived Promotions** page, click the <i class="fas fa-ellipsis-v"></i> icon and then <i class="fas fa-box"></i>.
+
+You can unarchive or duplicate archived promotions by clicking the <i class="fas fa-ellipsis-v"></i> icon.
+
+<div class="alert alert-info">
+  <p>When you unarchive a promotion, the status will change to <code>Paused</code>.</p>
+  </div>
+
diff --git a/docs/tutorials/en/seller-portal-shared-products.md b/docs/tutorials/en/seller-portal-shared-products.md
index f8ffa7670..fa232480a 100644
--- a/docs/tutorials/en/seller-portal-shared-products.md
+++ b/docs/tutorials/en/seller-portal-shared-products.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Shared Products'
 id: 6vUGj2UmOuLzQTK9pj04lu
 status: PUBLISHED
 createdAt: 2021-02-02T20:31:40.476Z
-updatedAt: 2023-03-31T15:18:11.408Z
-publishedAt: 2023-03-31T15:18:11.408Z
+updatedAt: 2023-11-22T14:00:41.976Z
+publishedAt: 2023-11-22T14:00:41.976Z
 firstPublishedAt: 2021-09-15T20:52:51.767Z
 contentType: tutorial
 productTeam: Channels
@@ -15,6 +15,9 @@ legacySlug: seller-portal-shared-products
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
+
+<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+
 **Shared Products** is the module where you can manage the products in your catalog that are already offered in the marketplace. The shared products dashboard displays all the products that the marketplace has made available for your store to sell. These products have been synced with the marketplace catalog.
 
 The Shared Products feature reduces the complexity of selling products that are already available in the marketplace catalog, allowing the seller to start selling faster and with less friction. 
@@ -26,7 +29,7 @@ In the Shared Products page you will find two tabs:
 - Available  
 
  ## Imported
- ![Shared products Importados EN](https://images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/00980934a6d88d6aeccc1d1ed66778a2/Shared_products_Importados_EN.jpg)
+ ![Shared products Importados EN](//images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/00980934a6d88d6aeccc1d1ed66778a2/Shared_products_Importados_EN.jpg)
 
 The *Imported* tab displays products from the marketplace catalog that you have already imported and are ready to become offers. This is also where you activate your products. Above the list there is a search bar where you can search for products by name or SKU.  
 
@@ -35,7 +38,7 @@ The first time you access the Seller Portal the *Imported* tab will be empty bec
 When you click on a product in the list, you will be redirected to a page containing the [Product's Details](https://help.vtex.com/en/tutorial/seller-portal-detalhes-do-produto--K0WWsERWj7aQtmZinhYoP).
 
 ## Available
-![Shared products Disponíveis EN](https://images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/5511033385ff07608a9eb279f1dae94f/Shared_products_Dispon__veis_EN.jpg)
+![Shared products Disponíveis EN](//images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/5511033385ff07608a9eb279f1dae94f/Shared_products_Dispon__veis_EN.jpg)
 
 The *Available* tab displays products from the marketplace catalog that have been made available to the seller but which have not been added to the their catalog.  You can filter the available products by brand or category to facilitate the import process.
 
diff --git a/docs/tutorials/en/send-item-price-with-tax-shown-separately.md b/docs/tutorials/en/send-item-price-with-tax-shown-separately.md
index b0dde4f96..c2747bc01 100644
--- a/docs/tutorials/en/send-item-price-with-tax-shown-separately.md
+++ b/docs/tutorials/en/send-item-price-with-tax-shown-separately.md
@@ -3,8 +3,8 @@ title: 'Send the item price, with tax shown separately, to the Gateway or the ER
 id: 77O1rBSLHqW8eWWsE6IEii
 status: PUBLISHED
 createdAt: 2017-08-14T15:30:39.027Z
-updatedAt: 2019-12-31T15:21:46.929Z
-publishedAt: 2019-12-31T15:21:46.929Z
+updatedAt: 2024-04-17T14:38:57.929Z
+publishedAt: 2024-04-17T14:38:57.929Z
 firstPublishedAt: 2017-08-16T17:43:33.301Z
 contentType: tutorial
 productTeam: Others
@@ -23,10 +23,10 @@ In this article we will show how the system works in these cases.
 
 **Scenario 1**: My ERP sends the price including VAT to VTEX, so I do not need to calculate it.
 
-1. Category page![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
-2. Product page![PRODUCTOSINIVA](https://images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
-3. Shopping cart![CARRITOSINIVA](https://images.ctfassets.net/alneenqid6w5/xX5Coy1UVUc0weEoY4Gik/c7131a671b35316aba28aaf7e8bbbb75/3_cart.png)
-4. Checkout![CHECKOUTSINIVA](https://images.ctfassets.net/alneenqid6w5/5QoFlwnTGg0WG86a6ekYu4/20de3c81acb0967787aaa10565e13d2f/4_check.png)
+1. Category page![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
+2. Product page![PRODUCTOSINIVA](//images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
+3. Shopping cart![CARRITOSINIVA](//images.ctfassets.net/alneenqid6w5/xX5Coy1UVUc0weEoY4Gik/c7131a671b35316aba28aaf7e8bbbb75/3_cart.png)
+4. Checkout![CHECKOUTSINIVA](//images.ctfassets.net/alneenqid6w5/5QoFlwnTGg0WG86a6ekYu4/20de3c81acb0967787aaa10565e13d2f/4_check.png)
 
 **Scenario 2**: My ERP sends the price *without* VAT to VTEX.
 
@@ -34,11 +34,11 @@ To show the price including charges in the store window, use the attribute `$pro
 
 Then to create a JS and add the amount of tax in the store window, you can also use the control `$product.Tax` (It shows the charges registered for the product).
 
-[See documentation on controls here](/en/tutorial/shelf-template-controls)
+[See documentation on controls here](https://developers.vtex.com/docs/guides/shelf-template-controls)
 
 __Attention__: On the product page you have to enter a JavaScript to add the values.
 
-1. Category page![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
-2. Product page![PRODUCTOCONIVA](https://images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
-3. Shopping cart![CARRITOCONIVA](https://images.ctfassets.net/alneenqid6w5/2cVDEuAgwoMYOSegQeQUiO/1b2666371b65289bb3956029b2911742/3a_cart.png)
-4. Checkout![CHECKOUTCONIVA](https://images.ctfassets.net/alneenqid6w5/6G4BksRmNO4giagOGga8Sq/7a3c7dd3426abc549ea6b61284a14fe0/4a_check.png)
+1. Category page![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
+2. Product page![PRODUCTOCONIVA](//images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
+3. Shopping cart![CARRITOCONIVA](//images.ctfassets.net/alneenqid6w5/2cVDEuAgwoMYOSegQeQUiO/1b2666371b65289bb3956029b2911742/3a_cart.png)
+4. Checkout![CHECKOUTCONIVA](//images.ctfassets.net/alneenqid6w5/6G4BksRmNO4giagOGga8Sq/7a3c7dd3426abc549ea6b61284a14fe0/4a_check.png)
diff --git a/docs/tutorials/en/sending-sku-attributes-to-amazon.md b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
index 5fbf0172d..474a924f8 100644
--- a/docs/tutorials/en/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
@@ -19,7 +19,7 @@ Having done the initial settings for the [Amazon integration](/en/tutorial/integ
 
 The mapping will only be done once for each category. With that, even once you have done the mapping, when new products are created, they will be directly integrated. A __from/to__ of the attributes registered in VTEX will be made with the attributes accepted by Amazon.
 
-1. Create an __upload spreadsheet__ in the format ".xlsx" and fill in the columns title as shown below.![Modelo Atributos Amazon](https://images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
+1. Create an __upload spreadsheet__ in the format ".xlsx" and fill in the columns title as shown below.![Modelo Atributos Amazon](//images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
 
 2. Fill in the fields of the mapping spreadsheet as follows:
 
@@ -46,7 +46,7 @@ Note: If <strong>none</strong> of the category attributes is required by Amazon,
 
 Sample spreadsheet using the Clothing & Accessories category:
 
-![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
+![Amazon Mapeamento ](//images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
 <div class = "alert alert-danger">
 Note that these values must conform to the ones from Amazon. Check which terms are allowed and make the From/To between what is registered in your SKU field in VTEX and the values accepted by Amazon.
diff --git a/docs/tutorials/en/sent-offers-beta.md b/docs/tutorials/en/sent-offers-beta.md
index a86329de3..ade99a2bb 100644
--- a/docs/tutorials/en/sent-offers-beta.md
+++ b/docs/tutorials/en/sent-offers-beta.md
@@ -21,7 +21,7 @@ The Sent Offers module allows sellers to monitor their offers’ submission and
 - [Offers](https://help.vtex.com/en/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#offers)            
 - [Channels](https://help.vtex.com/en/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#channels)          
 
-![Anuncios enviados Home EN](https://images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/a9028554a465b67e3dec924aa11d0afa/Anuncios_enviados_Home_EN.jpg)
+![Anuncios enviados Home EN](//images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/a9028554a465b67e3dec924aa11d0afa/Anuncios_enviados_Home_EN.jpg)
 
 ## Offers
 
diff --git a/docs/tutorials/en/sent-offers-buybox-opportunities.md b/docs/tutorials/en/sent-offers-buybox-opportunities.md
index 57ca12bff..3574b3a13 100644
--- a/docs/tutorials/en/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/en/sent-offers-buybox-opportunities.md
@@ -1,10 +1,10 @@
 ---
 title: 'Offer Management: Buybox opportunities'
 id: 1hO9eI1th47EGxQoTzGewC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-07-29T19:59:30.988Z
-updatedAt: 2022-10-20T01:38:56.059Z
-publishedAt: 2022-10-20T01:38:56.059Z
+updatedAt: 2024-06-20T21:42:56.304Z
+publishedAt: 
 firstPublishedAt: 2021-07-29T20:20:39.780Z
 contentType: tutorial
 productTeam: Channels
@@ -12,9 +12,15 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: sent-offers-buybox-opportunities
 locale: en
 legacySlug: sent-offers-buybox-opportunities-beta
-subcategory: 2zVauFUkYn8vgS0y0MfWeK
+subcategory: 
 ---
 
+<div class="alert alert-info">
+To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
+For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
+</div>  
+
 An offer is a SKU from a seller that has been sent to a sales channel and whose price and inventory have been configured. The [Offer Management](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) module in the VTEX Admin allows sellers to monitor their offers’ submission and sync on marketplaces. Besides, it can lead to an increase in your product sales. 
 
 The *Opportunities* feature identifies offers that can have an outstanding performance on the channels they are being sold and then performs actions to take those opportunities. 
@@ -33,13 +39,13 @@ On the [Offer Management](https://help.vtex.com/en/tutorial/offers-listing--7MRb
 
 ## Offer details
 
-![EN Oportunidades Offer details](https://images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/6ed62b0628ffc356995b4aa59321f28c/EN_Oportunidades_Offer_details.jpg)
+![EN Oportunidades Offer details](//images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/6ed62b0628ffc356995b4aa59321f28c/EN_Oportunidades_Offer_details.jpg)
 
 The [Offer details](https://help.vtex.com/en/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) page displays a message about the `Opportunity` at the top of the page. By clicking on `View opportunity`, you will be redirected to the following page.
 
 ## Offer opportunities
 
-![EN Oportunidades oportunidades do anúncio](https://images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/f4ca300fea32688a1dcb606f92104cb9/EN_Oportunidades_oportunidades_do_an__ncio.jpg)
+![EN Oportunidades oportunidades do anúncio](//images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/f4ca300fea32688a1dcb606f92104cb9/EN_Oportunidades_oportunidades_do_an__ncio.jpg)
 
 The **Offer opportunities** page displays the Buybox-eligible offer next to the one already available for sale on the marketplace. On this page, you can compare the data of both offers, such as their brand information, specifications, and dimensions.
 
diff --git a/docs/tutorials/en/set-up-mundi-gateway.md b/docs/tutorials/en/set-up-mundi-gateway.md
index e86fb60a5..280d4a8a5 100644
--- a/docs/tutorials/en/set-up-mundi-gateway.md
+++ b/docs/tutorials/en/set-up-mundi-gateway.md
@@ -3,8 +3,8 @@ title: 'Set up Mundi gateway'
 id: 2yn9dKzvZOF5tn4RCX2Nbq
 status: PUBLISHED
 createdAt: 2019-04-04T21:12:48.808Z
-updatedAt: 2023-03-26T21:57:24.882Z
-publishedAt: 2023-03-26T21:57:24.882Z
+updatedAt: 2024-01-23T19:02:29.463Z
+publishedAt: 2024-01-23T19:02:29.463Z
 firstPublishedAt: 2019-04-04T21:20:22.149Z
 contentType: tutorial
 productTeam: Financial
@@ -21,13 +21,13 @@ At VTEX, it is possible to integrate with the Mundi payment provider.
 If you also want to use Mundi's anti-fraud, the settings for this function must be performed by the company's own hub. In case of doubts about this stage of the operation, consult Mundi's technical support.
 </div>
 
-To configure Mundi affiliation, follow the steps below:
+To configure Mundi, follow the steps below:
 
-<ui>1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.</ui>
+<ui>1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.</ui>
 
-<ui>2. In the __Gateway affiliations__ tab, click on the __+__ button.</ui>
+<ui>2. On the providers screen, click the `New Provider` button.</ui>
 
-<ui>3. Click on the __Mundi__ connector.</ui>
+<ui>3. Type the name __Mundi__ in the search bar and click on the name of the provider.</ui>
 
 <ui>4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Mundi.</ui>
 
diff --git a/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md b/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md
index 4421d2d12..9b1167eeb 100644
--- a/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md
+++ b/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md
@@ -27,6 +27,6 @@ To configure this authentication, follow the steps below.
 2. Acces **Settings**
 3. Activate the flag __Require user authentication for automatically authorized payments__.
 
-![autenticação-usuario-pagamento-recorrencia en](https://images.ctfassets.net/alneenqid6w5/2BF2Kr1kowiCAIWOgmqSAA/d65d2bd11d5ac0a2019b9737685a2471/autentica____o-usuario-pagamento-recorrencia_en.png)
+![autenticação-usuario-pagamento-recorrencia en](//images.ctfassets.net/alneenqid6w5/2BF2Kr1kowiCAIWOgmqSAA/d65d2bd11d5ac0a2019b9737685a2471/autentica____o-usuario-pagamento-recorrencia_en.png)
 
 4. Click on the __Save__ button.
diff --git a/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md b/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md
index 9f51de3ba..ce6ffee89 100644
--- a/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md
+++ b/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md
@@ -3,8 +3,8 @@ title: 'How to set up similar product, suggestions, accessories and generics'
 id: tutorials_280
 status: PUBLISHED
 createdAt: 2017-04-27T22:10:17.727Z
-updatedAt: 2023-03-29T14:45:42.789Z
-publishedAt: 2023-03-29T14:45:42.789Z
+updatedAt: 2024-07-25T21:19:12.871Z
+publishedAt: 2024-07-25T21:19:12.871Z
 firstPublishedAt: 2017-04-27T23:03:13.377Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -35,7 +35,7 @@ To help you use the above techniques, we can use the fields in the register of p
 4. Fill out the fields correctly as indicated below.
 5. Click on the `Save` button.
 
-![produto-similar-sugestão-acessório-exemplo en](https://images.ctfassets.net/alneenqid6w5/4HXcbiIWFGY4eum8MSWwYs/ab6fde2f960fdca559c6a2ec3419fa55/produto-simular-sugest__o-acess__rio-exemplo_en.png)
+![produto-similar-sugestão-acessório-exemplo en](//images.ctfassets.net/alneenqid6w5/4HXcbiIWFGY4eum8MSWwYs/ab6fde2f960fdca559c6a2ec3419fa55/produto-simular-sugest__o-acess__rio-exemplo_en.png)
 
 **Acessories:** in this field we register the products that must be sold to complement another product. In this option, the products registered as accessories are shown as a purchase option by enabling the selection checkbox (function included in the layout).
 
@@ -45,6 +45,4 @@ To help you use the above techniques, we can use the fields in the register of p
 
 **Show together:** Displays SKUs of suggested products for joint purchase.
 
-Other Cross Selling options can be enabled when building the store layout, such as the option for Shelf templates “Who bought also bought”, "Who saw also bought" and “Who saw also saw”. For further information, access our tutorial about [shelf template controls](https://help.vtex.com/en/tutorial/list-of-controls-for-templates--tutorials_563).
-
 The Up-Selling option can be also worked by using the benefit “[Buy Together](http://help.vtex.com/en/tutorial/buy-together)”.
diff --git a/docs/tutorials/en/setting-up-abandoned-carts.md b/docs/tutorials/en/setting-up-abandoned-carts.md
index 8c68edddd..cd536272a 100644
--- a/docs/tutorials/en/setting-up-abandoned-carts.md
+++ b/docs/tutorials/en/setting-up-abandoned-carts.md
@@ -3,8 +3,8 @@ title: 'Setting up Cart Abandonment (Trigger)'
 id: tutorials_740
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:05.882Z
-updatedAt: 2023-04-28T14:50:21.362Z
-publishedAt: 2023-04-28T14:50:21.362Z
+updatedAt: 2024-06-24T14:49:04.124Z
+publishedAt: 2024-06-24T14:49:04.124Z
 firstPublishedAt: 2017-04-27T23:03:41.572Z
 contentType: tutorial
 productTeam: Shopping
@@ -40,7 +40,7 @@ You can create your own custom email template or use the default template option
 4. Fill in the __Template XHTML__ field with the template codes.
 5. Click on `Save Template`.
 
-![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/d48bd1624a47451e2314e2296237992f/Template_XHTML.PNG)
+![template xhtml](//images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/d48bd1624a47451e2314e2296237992f/Template_XHTML.PNG)
 
 <div class="alert alert-warning">
 We recommend that template customization should be performed by professionals with experience in the CMS module, and preferably, who have already configured other page and shelf templates.
@@ -50,7 +50,7 @@ We recommend that template customization should be performed by professionals wi
 2. Under __CMS > HTML__ Templates, click on the `CEM-Abandoned-Cart` icon.
 3. Check the information of the template codes present in the __Template XHTML__ field.
 
-![CEM-Abandoned-Cart](https://images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/45690f27bc8825ff3819ac3204d168e8/CEM-Abandoned-Cart.PNG)
+![CEM-Abandoned-Cart](//images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/45690f27bc8825ff3819ac3204d168e8/CEM-Abandoned-Cart.PNG)
 
 #### Configuring email template in Message Center
 
@@ -69,7 +69,7 @@ Once the new email template has been created or the data from the default templa
 The JSON Data field must not be filled or its data used in the email template. It only contains information to allow a preview of the format in which the data will be viewed in the email.
 </div>
 
-![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/72c7499b2fdc65ee661c3cb45a387a60/new_template.PNG)
+![New template - message center](//images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/72c7499b2fdc65ee661c3cb45a387a60/new_template.PNG)
 
 #### SPF Release
 
@@ -77,7 +77,7 @@ The SPF release is essential to avoid problems with email deliverability and mus
 
 As a good practice for configuring DNS for a generic domain (not mandatory), follow the example below:
 
-![Hostnames - SPF](https://images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/1ca34737e3275712b51c45283ec5b0c5/Hostnames_-_SPF.PNG)
+![Hostnames - SPF](//images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/1ca34737e3275712b51c45283ec5b0c5/Hostnames_-_SPF.PNG)
 
 Learn more at [Setting up DNS pointing to VTEX](https://help.vtex.com/en/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280#).
 
@@ -126,7 +126,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><blockquote><ui>-> Último Carrinho - Não está nulo (Last cart - is not null)</ui>   
 
-![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/6408ac4ab3b36d015790bcf1b1b5d667/Filter_Master_Data.PNG)
+![Filter master data 2](//images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/6408ac4ab3b36d015790bcf1b1b5d667/Filter_Master_Data.PNG)
 
 <div class="alert alert-warning">
   In addition to the filters indicated above, it is recommended to insert another filter in the following format: <code>Receives newsletter? - Equal to - True</code>. This ensures compliance with <a href="https://help.vtex.com/en/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">data subject rights</a>, as only customers subscribed to the newsletter will receive abandoned cart emails. Subscription to your store's newsletter can be managed at checkout or in the <a href="https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">My Account</a> section of your store.
@@ -134,7 +134,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><ui> 10. Click on the <b>Schedule</b> tab and select whether to send the email on a specific date or on a dynamic date.</ui>
 
-![Schedule date](https://images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/6956b67734b6b7c3970d193c03e8fefc/Schedule_date.PNG)
+![Schedule date](//images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/6956b67734b6b7c3970d193c03e8fefc/Schedule_date.PNG)
 
 <blockquote><ui>11. In the <b>If positive</b> tab:</ui>
 
@@ -157,7 +157,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><blockquote><ui>h. In <b>URL</b>, enter your store’s address, including the folders in which the layout of the abandoned cart was set up, followed by the cart tag (?refs={!carttag_SCORE}). Ex.: storename.com/CEM/Abandoned-Cart?refs={!carttag_SCORE}.</ui>  
 
-![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)  
+![PastasCarrinhoAbandonado](//images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)  
 
 <div class="alert alert-warning">The URL address must be the real one of the store, not the URL with vtexcommercestable.
 </div>
@@ -171,7 +171,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 <div class="alert-warning">A page’s session expires in 30 minutes. Only after that time, the system schedules the abandoned cart trigger. In other words, the time to be considered is the session's time + the trigger schedule.
 </div>  
 
-![If positive tab](https://images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/44d05312148341427e720b76d8a1f24f/If_positive_Tab.PNG)  
+![If positive tab](//images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/44d05312148341427e720b76d8a1f24f/If_positive_Tab.PNG)  
 
 ### Configuration for VTEX IO stores
 
@@ -182,7 +182,7 @@ To configure the abandoned cart functionality in VTEX IO stores, follow these st
 3. Perform the [SPF release](#spf-release).
 4. [Configure the trigger](#trigger-configuration) the same way as in Legado stores up to Step 10. From Step 11 (__If positive__ tab), follow the instructions available at [Trigger configuration information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#trigger-configuration-information).
 
-  ![If positive tab IO](https://images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/1b177fab2726c1d05d39608727cc2057/If_positive_Tab_IO.PNG)
+  ![If positive tab IO](//images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/1b177fab2726c1d05d39608727cc2057/If_positive_Tab_IO.PNG)
 
 ## Frequently Asked Questions (FAQ)
 
diff --git a/docs/tutorials/en/setting-up-amazonpay-beta.md b/docs/tutorials/en/setting-up-amazonpay-beta.md
index 1bdfb274f..597f6b404 100644
--- a/docs/tutorials/en/setting-up-amazonpay-beta.md
+++ b/docs/tutorials/en/setting-up-amazonpay-beta.md
@@ -59,7 +59,7 @@ Before setting up the affiliation in VTEX Admin, first you need to have your **S
 
 1. Access the **Apps** module on the left panel of VTEX Admin.
 2. Click on **My apps**.  
-![My apps menu EN](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
+![My apps menu EN](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
 3. Find the AmazonPay app installed by VTEX and click on **Settings**.  
 ![Admin My apps AmazonPay EN](//images.contentful.com/alneenqid6w5/4oy769BIF5gz08hPMeFdRv/92a6cb38ddb94d4e76078959642cc57c/Admin_My_apps_AmazonPay_EN.png)
 4. Fill the settings according to the table below:
diff --git a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
index d4751af23..5288765b8 100644
--- a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -17,7 +17,7 @@ subcategory:
 
 This article aims to explain how the inStore app configures AppLinking for `payment` and `payment-reversal` actions with the acquirers' apps.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Setting fields
 
diff --git a/docs/tutorials/en/setting-up-bradesco-registered-ticket.md b/docs/tutorials/en/setting-up-bradesco-registered-ticket.md
index a2b1dcc5b..9c76e182c 100644
--- a/docs/tutorials/en/setting-up-bradesco-registered-ticket.md
+++ b/docs/tutorials/en/setting-up-bradesco-registered-ticket.md
@@ -3,7 +3,7 @@ title: 'Setting up Bradesco registered ticket'
 id: bbnXBjvKOkWYiOosmASiA
 status: DRAFT
 createdAt: 2018-03-20T22:08:43.187Z
-updatedAt: 2022-12-23T20:13:39.299Z
+updatedAt: 2024-03-18T18:04:46.311Z
 publishedAt: 
 firstPublishedAt: 2018-03-21T17:27:23.026Z
 contentType: tutorial
diff --git a/docs/tutorials/en/setting-up-braspag-gateway.md b/docs/tutorials/en/setting-up-braspag-gateway.md
index 0c6928db9..adf56eb2a 100644
--- a/docs/tutorials/en/setting-up-braspag-gateway.md
+++ b/docs/tutorials/en/setting-up-braspag-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Braspag gateway'
 id: 7tQmfLMvtYEsWoaaAaeKSC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-27T18:21:37.603Z
-updatedAt: 2023-03-29T01:03:06.303Z
-publishedAt: 2023-03-29T01:03:06.303Z
+updatedAt: 2023-09-19T14:26:39.079Z
+publishedAt: 
 firstPublishedAt: 2018-02-27T18:52:38.519Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-conductor-gateway.md b/docs/tutorials/en/setting-up-conductor-gateway.md
index a34f1aab4..2b79dd940 100644
--- a/docs/tutorials/en/setting-up-conductor-gateway.md
+++ b/docs/tutorials/en/setting-up-conductor-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Conductor gateway'
 id: Q5Ezi95TSEyE2GCQSs8ak
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-05-02T17:09:15.090Z
-updatedAt: 2023-03-29T00:55:20.862Z
-publishedAt: 2023-03-29T00:55:20.862Z
+updatedAt: 2024-03-18T18:11:12.675Z
+publishedAt: 
 firstPublishedAt: 2018-05-02T18:38:56.879Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-conductor-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Conductor is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) with [PCI certification](/en/faq/what-is-the-pci-ssc) that is more than 20 years old. In VTEX, it can be configured to process payments made with __credit cards with store brand__.
 
 To enable Conductor in your store, follow the steps below:
 
-## Setting up Conductor gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Conductor__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Conductor__ in the search bar and click on the name of the provider.
 4. In the __External Service Url__ field, configure the external URL that will be associated with `/pvt/payments?an={AccoutName}`.
 5. Fill in the registration fields with the data provided by Conductor (fields _appKey_ and _appToken_).
 6. Under __Implements Installments Service__, choose whether you want to use external installment services or what the one configured on the portal. If you choose _yes_, the system will use the URL configured in the __Installments Service Url__ field.
diff --git a/docs/tutorials/en/setting-up-cybersource-antifraud.md b/docs/tutorials/en/setting-up-cybersource-antifraud.md
index 9804bc5cc..ebe939523 100644
--- a/docs/tutorials/en/setting-up-cybersource-antifraud.md
+++ b/docs/tutorials/en/setting-up-cybersource-antifraud.md
@@ -3,8 +3,8 @@ title: 'Setting up CyberSource antifraud'
 id: 2Z88QmpRAsWmI0qaCo4aQg
 status: PUBLISHED
 createdAt: 2018-04-30T18:08:44.396Z
-updatedAt: 2023-03-26T21:48:46.023Z
-publishedAt: 2023-03-26T21:48:46.023Z
+updatedAt: 2024-03-15T15:29:09.166Z
+publishedAt: 2024-03-15T15:29:09.166Z
 firstPublishedAt: 2018-04-30T20:25:40.199Z
 contentType: tutorial
 productTeam: Financial
@@ -24,30 +24,32 @@ If you are looking for more details about __gateway__ CyberSource, read [this He
 <div class="alert alert-info">
 Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before performing Step 6. of this section.
 </div>
-1. 
-2. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-3. On the __Gateway Affiliations__ tab, click the __+__ button.
-4. Click the __CyberSource__ connector that is in the _ANTIFRAUDS_ section.
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the provider's screen, click the `New Provider` button.
+3. Type __Cybersource__ in the search bar and click on the provider's name.
+4. If you wish to modify the identification name to be displayed for the Cybersource anti-fraud on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
 5. Set the `https://{store}.vtexpayments.com.br/api/pub/cybersource/antifraud/notification` URL on the CyberSource website, replacing `{store}` with your store name. This will enable notifications when the status of an order changes.
 6. Set up the device fingerprint in Google Tag Manager using [this Help article](/en/faq/how-to-set-up-the-device-fingerprint-for-braspagcybersource).
-7. Fill in the registration fields with the data provided by CyberSource (_Merchant ID at CyberSource_, _Your CyberSource's username_ and _Your CyberSource's password_).
-8. In the __Your company's name__ field, enter the business name of your store.
-9. In __Your company's tax id__, inform the tax id number of your store.
+7. Fill in the __Merchant ID on Cybersource__, __Your CyberSource username__, and __Your Cybersource password__ fields according to data provided by CyberSource.
+8. In __Your company's name__, enter the business name of your store.
+9. In __Your company's registration number__, inform the tax id number of your store.
 10. Under __Private certificate (.p12)__, upload a valid private certificate (generated by you, using a third-party certifier or software), with a .p12 extension and key.
 11. In __Private certificate password__, enter the password you created to access the certificate.
 12. In __Merchant Key ID__ and __Merchant Secret Key__, enter data provided by CyberSource to access reporting API.
 13. In __Documento Opcional__, select whether document submission is required for fraud analysis.
 14. Under __Send authenticated transactions?__, choose whether to send all transactions for anti-fraud analysis or only those that are not authenticated.
-15. Click __Save__.
+15. Click `Save`.
 
 ## Associating the anti-fraud with a payment condition
 After setting up CyberSource's anti-fraud system, it will be available for use in your store. But you must associate it with the payment conditions, either the ones that are already configured or the ones that you are still going to make available.
 
-1. Within PCI Gateway __Settings__, click on the __Payment Conditions__ tab.
-2. Click on the desired condition or [create a new payment condition](/en/tutorial/how-to-configure-payment-conditions).
-3. Check the __Use antifraud__ option.
-4. Select __CyberSource__.
-5. Click __Save__.
+1. In the VTEX Admin, access __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. On the __Payment Conditions__ tab, click the `+` button.
+3. Click on the desired condition or [create a new payment condition](/en/tutorial/how-to-configure-payment-condition).
+5. Check the __Use anti-fraud solution__ option.
+6. Select CyberSource.
+7. Click `Save`.
 
 <div class="alert alert-warning">
 For a transaction to go through antifraud analysis, <strong>the payment condition used by the customer must be associated with it</strong>.
diff --git a/docs/tutorials/en/setting-up-cybersource-gateway.md b/docs/tutorials/en/setting-up-cybersource-gateway.md
index 4145d0cec..117369757 100644
--- a/docs/tutorials/en/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/en/setting-up-cybersource-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up CyberSource gateway'
+title: 'Setting up CyberSource gateway IO'
 id: 6nhvUTrLxeacsoYG6GkGM
 status: PUBLISHED
 createdAt: 2018-04-30T17:34:57.517Z
-updatedAt: 2023-03-29T00:33:54.554Z
-publishedAt: 2023-03-29T00:33:54.554Z
+updatedAt: 2024-04-22T14:35:34.191Z
+publishedAt: 2024-04-22T14:35:34.191Z
 firstPublishedAt: 2018-04-30T20:20:44.704Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,211 @@ legacySlug: setting-up-cybersource-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-CyberSource is a [gateway](/en/tutorial/what-is-a-payment-gateway) that offers a number of solutions to help your store manage payments. Among them is a payment __gateway__, which offers integration with the VTEX platform. If you are looking for more details about CyberSource __antifraud__, read [this Help article](/en/tutorial/setting-up-cybersource-antifraud).
+CyberSource is a company that offers several solutions to help manage payments in your store. Among them are a [gateway](https://help.vtex.com/en/tutorial/what-is-a-payment-gateway--2KH9Wdi7F6swOU4amECSOk) and [anti-fraud](https://help.vtex.com/en/tutorial/what-is-anti-fraud--69SjFCc4rC6Ii0OMAeYAsG), both with integrations available at VTEX.
 
-To set up CyberSource __gateway__, follow the steps below:
+If you want more information about integrating Cybersource anti-fraud into your store, go to [Setting up CyberSource anti-fraud](https://help.vtex.com/en/tutorial/setting-up-cybersource-antifraud--2Z88QmpRAsWmI0qaCo4aQg).
 
-## Setting up CyberSource gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __CyberSource__ connector that is in the _OTHERS_ section.
-4. Fill in the registration fields with the data provided by CyberSource (_Merchant ID/ Id of Merchant at CyberSource_, _Username / Username used on Cybersource panel_ and _Password / Password used on Cybersource panel_).
-5. In the __Company's  name__ field, enter the business name of your store.
-6. In __Company's CNPJ__, inform the number of your store's CNPJ.
-7. In the __Currency__ field, choose the currency that will be used in your store transactions.
-8. In __Private certificate (.p12)__ , upload a valid private certificate (generated by you, using a third-party certifier or software) with a .p12 extension and key.
-9. In the __Private certificate password__, enter the password (it is your _Merchant ID/ Id of Merchant at CyberSource_).
+To use the Cybersource IO gateway in your store, the following actions are required:
+
+1. [Install Cybersource IO applications (VTEX IO CLI)](#installing-cybersource-io-apps)
+2. [Create authentication keys in Cybersource (Cybersource environment)](#creating-authentication-keys-in-cybersource)
+3. [Perform Cybersource app settings (Admin VTEX)](#setting-up-cybersource-io-app)
+4. [Configure Cybersource gateway (Admin VTEX)](#setting-up-cybersource-gateway)
+5. [Configure payment conditions (Admin VTEX)](#setting-up-payment-condition)
+6. [Configurar o Device Fingerprint (opcional)](#setting-up-cybersource-io-device-fingerprint-optional)
+7. [Configure merchant fields (optional)](#setting-up-merchant-fields-optional)
+
+## Installing Cybersource IO apps
+
+The following Cybersource apps must be installed in your store account:
+
+- __vtex.cybersource-ui__
+- __vtex.cybersource__
+- __vtex.cybersource-payer-auth__
+
+<div class="alert alert-warning">
+If you intend to use Cybersource's anti-fraud system, but want to transact payments on a non-Cybersource gateway, you will need to install the <b>vtex.cybersource-fraud</b> app.
+  </div>
+
+Learn more about installing applications on a VTEX account in [Installing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app). 
+
+## Creating authentication keys in Cybersource 
+
+After installing the apps, you must create authentication keys in the Cybersource environment.
+
+<div class="alert alert-warning">
+  Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Cybersource account for the latest information.
+  </div>
+
+Follow the steps below:
+
+1. Access [Cybersource's EBC panel](https://businesscenter.cybersource.com/ebc2/) (Enterprise Business Center) with your data.
+2. In the side navigation menu, select __Payment Configuration > Key Management__.
+3. Click __Generate Key__.
+4. In __REST APIs__, select the __REST - Shared Secret__ option.
+5. Click __Generate Key__.
+6. Click __Download key__ or copy the key information using the copy function located in front of the __Key__ and __Shared Secret__ fields.
+
+## Setting up Cybersource IO app
+
+Once you have obtained the available authentication keys, it is time to configure the Cybersource IO app in the Admin. 
+
+![Cybersource Admin settings EN](//images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/9d036d1151c88215344459a3ae57fd91/Cybersource_Admin_settings_EN.JPG)
+
+Follow the steps below to configure the Cybersource IO app:
+
+1. In the VTEX Admin, go to __Apps > Installed Apps > Cybersource__, or type __Cybersource__ in the search bar at the top of the page.
+2. On the __Admin Settings__ tab, fill in or select the fields below:
+<br>
+<ul>
+<br>
+    	<li><b>Merchant id</b>: Your merchant ID at Cybersource.</li>
+    	<li><b>Merchant key</b> and <b>Shared secret key</b>: The two keys obtained in the Cybersource environment.</li>
+  <li><b>Processor</b>: Select the company that will process the payment, or click <b>Other</b> if it is not on the list.</li>
+    	<li><b>Region</b>: Select one of the regions or click <b>Other</b> if the desired region is not in the list.</li>
+    	<li><b>Reference Suffix (optional)</b>: By default, orders in the Cybersource system will be associated with the VTEX order group ID, but this setting can be used to append a suffix such as "-01".</li>
+    	<li><b>Custom NSU (optional)</b>: Replace default NSU with custom value.</li>
+    	<li><b>Use Order Id For Device Fingerprint</b>: Select whether you want to use the order ID instead of the session ID for device fingerprinting.</li>
+    	<li><b>Enable Tax Calculations</b>: Select whether you want to use Cybersource at checkout as your tax calculation provider.</li>
+    	<li><b>Enable transaction posting</b>: Select whether to enable posting completed transactions for tax reporting issues.</li>
+    	<li><b>Sales Channels to Exclude from Cybersource (optional)</b>: Enter any sales channel where you do not want to use Cybersource transactions.</li>
+    	<li><b>Shipping Product Code (optional)</b>: Enter a product code for shipping tax calculation purposes.</li>
+    	<li><b>Tax Nexus Regions (optional)</b>: Enter a list of regions where taxes must be collected.</li>
+</ul>
+3. Click __Save settings__.
+
+## Setting up Cybersource gateway
+
+To configure the Cybersource gateway, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the provider's screen, click the `New Provider` button.
+3. Type __Cybersource IO__ in the search bar and click on the provider's name.
+4. In __Provider Authorization__, it is not necessary to fill in the __App key__ and __App token__ fields.
+5. If you wish to modify the identification name to be displayed for the Cybersource gateway on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following options:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic, but scheduled to be carried out after 4 days (or if the order is invoiced, whichever comes first).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>      
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. In __Provider fields__, fill in or select the fields below:
+<ul>
+<br>
+    	<li><b>Company Name</b>: Name of the company.</li>
+      <li><b>Company Tax id</b>: Identification number of the company.</li>
+  <li><b>Capture Setting</b>: select <b>Delayed Capture</b> to follow the standard VTEX platform procedure (separate calls for authentication and capture) or <b>Immediate Capture</b>, where a single authentication and capture call will be sent to CyberSource when the order is made.</li>
+    	<li><b>Payer Authentication</b>: If you wish to enable this option, <a href="https://www.cybersource.com/en/solutions/fraud-and-risk-management/payer-authentication-for-3d-secure.html">3-D Secure Payer Authentication da Cybersource</a> must be used.</li>
+    	<li><b>Capture Delay</b> and <b>Capture Delay Interval</b>: Determine the period before automatic capture.</li>
+    	<li><b>Using Decision Manager</b>: Select whether <a href="https://www.cybersource.com/apac/en/solutions/fraud-and-risk-management/decision-manager.html">CyberSource Decision Manager</a> will be active on your account.</li>
+      <li><b>Authorized Payments Flagged by Decision Manager</b>: When the status is Authorized, Fraud Reject, select the following options:</li>
+      <blockquote><li><b>Treat as Successful Authorizations</b>: Accept the order.</li></blockquote>
+      <blockquote><li><b>Treat as Failed Authorizations</b>: Deny the order.</li></blockquote>
+      <blockquote><li><b>Treat as Pending Authorizations</b>: Hold the order pending a final decision.</li></blockquote>  
+</ul>
+9. The __Merchant Id__, __Merchant Key__ and __Shared Secret Key__ fields must be left blank, as the values defined in step 2 of the section [Configurando o app Cybersource IO](#setting-up-cybersource-io-app) will be used. If the fields are filled in with a value, they will overwrite the information entered in step 2.
 10. Click __Save__.
 
-## Setting up the payment condition
-After following the steps indicated above, the CyberSource gateway will be configured in your store. So while you're registering a payment condition, it will be available in the __Process with affiliation__ field (provided the payment method is compatible with CyberSource). To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+## Setting up payment condition
+
+To process credit card payments through Cybersource, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__ or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the + button.
+3. Click on the name of the desired credit card.
+4. Fill the __Condition name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. In __Process with provider__ select the __Cybersource - IO__ option.
+7. If you want to use an anti-fraud system, select the __Use anti-fraud solution__ option and choose your preferred provider.
+8. If you wish, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+9. Click __Save__.
+
+<div class="alert alert-warning">
+  If you have previously created credit card payment conditions for other gateways (including the legacy Cybersource provider), you can set those conditions to <b>Inactive</b>. In-progress transactions initiated from that provider will still be processed by that provider, even if it is inactive. Only new transactions will be processed by the new Cybersource IO provider. If you need to revert to your previous provider for any reason, simply set their payment conditions to <b>Active</b> and the Cybersource IO payment conditions to <b>Inactive</b>.</div>
+
+## Setting up Cybersource IO Device Fingerprint (optional)
+
+Device Fingerprint is an identifier that acts in payment processing to improve fraud risk analysis. 
+
+By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
+
+<div class="alert alert-info">
+Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
+</div>
+
+To configure Cybersource IO Device Fingerprint, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Storefront > Checkout__, or type __Checkout__ in the search bar at the top of the page.
+2. Click on the <i class="fas fa-cog" alt="engrenagem azul"></i> icon of the desired website.
+3. In the blue options menu located at the top of the page, click on __Chode__.
+4. In __Files__, click __checkout5.custom.js__.
+5. Enter the code below into the text field and click `Save`.
+
+    function addsDeviceFingerPrint() {
+      if (!window.vtex) return;
+      if (window.vtex.deviceFingerprint) return;
+      $.ajax({
+type: 'get',
+async: true,
+url: rootPath() + '/api/sessions?items=*'
+      }).then(function(response) {
+var ORG_ID = "{{ORG_ID}}";
+var MERCHANT_ID = "{{MERCHANT_ID}}";
+console.log('session', response);
+window.vtex.deviceFingerprint = response.id;
+var sessionId = response.id || "CYBERSOURCE";
+var script = document.createElement("script");
+script.type = "text/javascript";
+script.src = `https://h.online-metrix.net/fp/tags.js?org_id=${ORG_ID}&session_id=${MERCHANT_ID}${sessionId}`;
+document.head.appendChild(script);
+var noScript = document.createElement("noscript");
+var iframe = document.createElement("iframe");
+iframe.style = "width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;";
+iframe.src = `https://h.online-metrix.net/fp/tags?org_id=${ORG_ID}&session_id=${MERCHANT_ID}${sessionId}`;
+noScript.appendChild(iframe);
+document.body.appendChild(noScript);
+      })
+    }
+
+## Setting up merchant fields (optional)
+
+Additionally, you can define custom fields that will be included in orders forwarded from VTEX to Cybersource. 
+
+![Cybersource Admin merchant define fields EN](//images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/176d6380fb7ef021d18822973f392ab0/Cybersource_Admin_merchant_define_fields_EN.JPG)
+
+See below how to create these fields:
+
+1. In the VTEX Admin, go to __Aplicativos > Installed Apps > Cybersource__, or type __Cybersource__ in the search bar at the top of the page.
+2. On the __Merchant Defined Fields__ tab, under __Merchant Defined Information__, you can insert fields following the following rules:
+<ul>
+<br>
+    	<li>Any values outside the keys <b>{{}}</b> will be considered as a direct value.</li>
+      <li>Any values between <b>{{}}</b> must be in the following format <i>Reference Word|Modification Word|Values</i>.</li>
+      <li>All <b>reference words</b> can be found in the <b>Show all referenceable words</b> drop-down menu:</li>
+  <blockquote><li><b>Reference words</b> can be left blank if the <b>Modification Word</b> and <b>Values</b> are present.</li></blockquote>
+  <blockquote><li>The <b>reference word</b> is case sensitive.</li></blockquote>
+    	<li><b>Modification words</b> must be <b>Pad</b>, <b>Date</b>, <b>Trim</b>, <b>Age</b>, or <b>Equals</b>. See below the characteristics when registering each of them:</li>
+      <blockquote><li><b>Pad</b>: The <b>Values</b> must be in the format <b>desired length:fill character</b>.</li></blockquote>
+      <blockquote><blockquote><li>The <b>filled character</b> must be a unique value. For example, <i>9:x</i> will result in a desired length of 9, and will fill gaps with x.</li></blockquote></blockquote>
+  <blockquote><blockquote><li>If the field value exceeds the <b>desired length</b>, the field will be trimmed.</li></blockquote></blockquote>         
+<br>       
+      <blockquote><li><b>Date</b>: <b>Values</b> must be in the format dd/MM/yyyy or any combination thereof.</li></blockquote>
+      <blockquote><blockquote><li><b>M</b> for month must be capitalized. This format can be ordered as desired, such as <b>yyyy/MM</b> or <b>yyyy</b> or <b>dd/yyyy/MM</b>.</li></blockquote></blockquote>
+      <blockquote><li><b>Trim</b>: Will limit the maximum length of the field value without adding padding characters.</li></blockquote>
+      <blockquote><li><b>Age</b>: Will return the difference between the current date and the field value using Timespan format.</li></blockquote>
+      <blockquote><li><b>Equals</b>: Will return the boolean value of a string comparison between the field value and the comparison value.</li></blockquote>
+<br>
+    	<li>Each new line is considered a new field defined by the merchant.</li>
+
+Examples:
+
+| Value entered in Admin under `Merchant Defined Information`    | Simulated scenario     | Result     |
+| ---------- | ---------- | ---------- |
+| `969{{Reference|PAD|9:0}}`       | When `Reference` is 6023       | 969602300000       |
+| `{{OrderId}}-01`       | Where `OrderId` is 124578       | 124578-01       |
+| `{{MiniCart.Buyer.LastName}},{{MiniCart.Buyer.FirstName}}`       | Where Buyer is John Doe       | Doe,John       |        
+
diff --git a/docs/tutorials/en/setting-up-firstdata-acquirer.md b/docs/tutorials/en/setting-up-firstdata-acquirer.md
index 3b5bf185a..d2f6e6ed0 100644
--- a/docs/tutorials/en/setting-up-firstdata-acquirer.md
+++ b/docs/tutorials/en/setting-up-firstdata-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up FirstData acquirer'
 id: 4mW6gU343eWY6c8m6ocO0i
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-26T21:04:20.319Z
-updatedAt: 2023-03-21T18:04:57.904Z
-publishedAt: 2023-03-21T18:04:57.904Z
+updatedAt: 2024-03-18T18:23:46.570Z
+publishedAt: 
 firstPublishedAt: 2018-04-26T22:08:51.029Z
 contentType: tutorial
 productTeam: Financial
@@ -15,5 +15,49 @@ legacySlug: setting-up-firstdata-acquirer
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning" role="alert">This is a regional exclusive content not applicable to 
-English speaking countries.</div>
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
+At VTEX, it is possible to integrate with FirstData. With this provider, your store can make sales using credit and debit cards, and Plan Ahora (Argentine payment system).
+
+To configure FirstData, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __FirstData__ in the search bar and click on the name of the provider.
+4.  Fill in the requested fields with the following information:
+
+- __Username__: User ID that has permission to access the Web Service API. This information is necessary to perform basic authorization.  
+- __Basic authorization password__: FirstData user's general password (the same one mentioned in the “Username” field), which will be used for authorization.  
+- __Store ID__: Code that is sent in the .xml file of the requests.
+- __Country__: Country of origin. 
+- __Currency__: Currency of the country of origin. 
+- __Soft descriptor__: Text that will identify the purchase on your customer's statement. 
+- __Private certificate password__: Certificate password in your store. 
+- __Private certificate (.p12)__: Upload a valid private certificate (generated by you, using a certifier or specialized software), with a .p12 extension and key.
+- __Plan Ahora__: If you have enabled Ahora government plan options with FirstData, choose "True", otherwise choose "False". For more details about the Ahora plan, [click on](http://planesahora.gob.fiservargentina.com/).
+
+  - __Ahora 3 program__: For discounts on installments made in 3 installments.
+  - __Ahora 6 program__: For discounts on installments made in 6 installments.
+  - __Ahora 10 program__: For discounts on installments made in 10 installments.
+  - __Ahora 12 program__: For discounts on installments made in 12 installments.
+  - __Ahora 18 program__: For discounts on installments made in 18 installments.
+  - __Ahora 24 program__: For discounts on installments made in 24 installments.
+  - __Ahora 30 program__: For discounts on installments made in 30 installments.
+
+- __Auto Settle__: Configure this option to define when automatic payment capture will take place.
+
+  - __Inmediatamente__: Settlement will be carried out immediately after payment is authorized.
+  - __1 a 30 dias__: The settlement will be carried out after payment authorization, taking into account the selected number of days.
+  - __Desactivado__: Automatic capture will be turned off and will not have the platform's default behavior (4 days for capture). This way, the order will only be captured at the time it is invoiced, or if [manual settlement](https://developers.vtex.com/docs/api-reference/payments-gateway-api#post-/api/pvt/transactions/-transactionId-/settlement-request) is triggered.
+
+- __Change Margin__: Set the percentage margin for a payment to be modified to a higher amount than initially authorized. If the purchase was closed and authorized for BRL 100.00, for example, but there is a [change in the order](https://help.vtex.com/en/tutorial/changing-items-from-a-complete-order) to a higher value before capture, this connector allows the increase to be up to 20% of the initially authorized value.
+
+<ul>
+5. Click <b>Save</b>.
+  </ul>
+
+To configure the payment methods to be processed by Appmax, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, FirstData connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-getnet-acquirer-with-egetnet-connector.md b/docs/tutorials/en/setting-up-getnet-acquirer-with-egetnet-connector.md
index d43c37e2b..3e42f9f73 100644
--- a/docs/tutorials/en/setting-up-getnet-acquirer-with-egetnet-connector.md
+++ b/docs/tutorials/en/setting-up-getnet-acquirer-with-egetnet-connector.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up Getnet acquirer with Egetnet connector '
+title: 'Setting up payments with Egetnet'
 id: 75kwGKPKnK8mwiEmQGYiWq
 status: PUBLISHED
 createdAt: 2018-04-27T13:55:54.133Z
-updatedAt: 2023-03-29T00:59:42.828Z
-publishedAt: 2023-03-29T00:59:42.828Z
+updatedAt: 2024-03-14T18:03:01.948Z
+publishedAt: 2024-03-14T18:03:01.948Z
 firstPublishedAt: 2018-04-27T16:07:30.586Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,19 @@ legacySlug: setting-up-getnet-acquirer-with-egetnet-connector
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Getnet, one of the largest [acquirers](/en/tutorial/what-is-an-acquirer) in Brazil, can be configured in your store using the Egetnet connector. We recommend that you use this connector to gain access to the latest integration and to the new Getnet features.
+At VTEX, it is possible to integrate with the Egetnet payment provider. With this provider, your store can make sales through credit and debit cards, bank invoice and PIX.
 
-To set up Getnet with the Egetnet connector, follow the steps below:
+To configure Egetnet, follow the steps below:
 
-## Setting up Egetnet gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Egetnet__ connector.
-4. In the __Application Key__ field, enter the application key provided by Getnet.
-5. In __Application Token__, fill in the field with the token provided by Getnet.
-6. Click __Save__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Egetnet__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by Egetnet.
+5. If you wish to modify the identification name to be displayed for the Egetnet provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
 
-## Setting up the payment condition
-After following the steps indicated above, the Egetnet connector will be configured in your store. Thus, when you are registering a payment condition, it will be available in the __Process with affiliation__ field (provided the payment method is compatible with Egetnet). To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+To configure the payment methods to be processed by Egetnet, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Egetnet may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md b/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md
new file mode 100644
index 000000000..606077827
--- /dev/null
+++ b/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md
@@ -0,0 +1,31 @@
+---
+title: 'Setting up Intelligent Search integration with the Catalog'
+id: 3Nt5cIdwISSlzVtnYfLeIH
+status: PUBLISHED
+createdAt: 2024-06-27T16:56:47.833Z
+updatedAt: 2024-06-27T17:01:32.662Z
+publishedAt: 2024-06-27T17:01:32.662Z
+firstPublishedAt: 2024-06-27T16:57:41.295Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: setting-up-intelligent-search-integration-with-the-catalog
+locale: en
+legacySlug: integrations
+subcategory: 1EmKjP83dy0RWD9GzZkYsG
+---
+
+The **Store Settings** > **Intelligent Search** > **Integrations** page in the VTEX Admin handles the initial indexing of the Catalog with VTEX Intelligent Search. After installing the app, this will be the first step in integrating the app with the Catalog.
+
+Follow the instructions to start the integration process:
+
+1. In the VTEX Admin, go to **Store Settings**, or type **Store Settings** in the search bar at the top of the page.
+2. Under **Intelligent Search**, click **Integrations**.
+3. Click `Start Integration`.
+
+The indexing process will start. Once completed, the screen shown below will be displayed.
+
+![integracoes-is-en](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/20ef33f4ff2b33fca08a777d6c3c90c2/integracoes-is-en.PNG)
+
+You don't need to repeat this process. After starting the integration, you can follow the indexing status on the [Indexing History](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) page.
+
diff --git a/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md b/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md
index ad074a62d..563be0c2b 100644
--- a/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md
+++ b/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Itaú registered ticket (Itaú Registrado)'
 id: 6MEHf1oDTOkuWM2CaYi4gu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-11-30T18:23:45.696Z
-updatedAt: 2021-07-08T19:14:45.697Z
-publishedAt: 2021-07-08T19:14:45.697Z
+updatedAt: 2024-03-18T18:01:00.472Z
+publishedAt: 
 firstPublishedAt: 2018-12-11T17:59:44.827Z
 contentType: tutorial
 productTeam: Financial
@@ -15,28 +15,30 @@ legacySlug: setting-up-itau-registered-ticket-itau-registrado
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 To set up the Itaú registered boleto, you can choose between two connectors: __Invoice Itaú__ (also known as Itaú Registrado or Boleto Itaú, which you will learn how to configure on this very article) or [ItauShopline](https://help.vtex.com/en/tutorial/setting-up-itau-registered-ticket--3TqzCHPU7KIYGsOKuUeQcq). In __Invoice Itaú__'s case, the boleto is issued in a transparent way (without redirecting to Itaús's website). On the other hand, bank reconciliation must be done through reconciliation files.
 
 After setting up one of these gateway affiliations, you'll have to configure the Boleto Bancário payment condition. This way, all issued boletos will be registered by Itaú's system.
 
 ## Setting up Invoice Itaú (Itaú Registrado) gateway affiliation
-1. On the sidebar, click on __Payments__, inside the __Transactions__ section.
-2. In the listed options, click on __Settings__.
-3. Click on the __Gateway Affiliations__ tab and then on the __+__ icon.
-4. Click the __Invoice Itaú__ connector.
-5. Fill in with your company's name on the __Company name__ (Nome da Empresa) field. Remember that this data will be displayed in the boleto's _recipient_ field.
-6. In the __CNPJ__ field, fill in your company's registration number, without punctuation.
-7. Fill in your company's bank details in the __Bank branch number__ (Agência) and __Account number__ (Número de Conta) fields.
-8. In the __Boleto's expiration date__ (Validade do boleto em dias), choose the number of days for the boleto to expire.
-9. Fill in the __Boleto instructions__ (Instruções no boleto ao Caixa) field with important guidelines that will be printed on the boleto.
-10. Fill in the following fields with data provided by Itaú: _Portfolio_ (Portfólio ou Carteira), _Business agreement_ (Convênio), and _Assignor code_ (Código do Cedente). 
-11. In the __Recipient address__ (Endereço do Beneficiário) field, fill in with your company's address (only up to 200 characters allowed).
-12. Choose the option _Yes_ in the __Should it be registered?__ (Registrado?) field. By doing that, more fields shall appear.
-13. In the __Authentication environment__ (Ambiente de Autenticação) field, fill in the `beta` value.
-14. In the __Environment type__ (Tipo de Ambiente) field, fill in the `2` value.
-15. Fill in the following fields with data provided by Itaú: _Client ID_ (Id do cliente), _Client Secret_ (Secret do cliente), and _Itaú Key_ (Chave do itau).
-16. In the __Days until "boleto" expires__ field, set the number of days immediately succeeding the "boleto" - popular Brazilian offline payment method - expiry date after which the transaction itself expires.
-17. Click on the __Save__ button.
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __BankInvoiceItau__ in the search bar and click on the name of the provider.
+4. Fill in with your company's name on the __Company name__ (Nome da Empresa) field. Remember that this data will be displayed in the boleto's _recipient_ field.
+5. In the __CNPJ__ field, fill in your company's registration number, without punctuation.
+6. Fill in your company's bank details in the __Bank branch number__ (Agência) and __Account number__ (Número de Conta) fields.
+7. In the __Boleto's expiration date__ (Validade do boleto em dias), choose the number of days for the boleto to expire.
+8. Fill in the __Boleto instructions__ (Instruções no boleto ao Caixa) field with important guidelines that will be printed on the boleto.
+9. Fill in the following fields with data provided by Itaú: _Portfolio_ (Portfólio ou Carteira), _Business agreement_ (Convênio), and _Assignor code_ (Código do Cedente).
+10. In the __Recipient address__ (Endereço do Beneficiário) field, fill in with your company's address (only up to 200 characters allowed).
+11. Choose the option _Yes_ in the __Should it be registered?__ (Registrado?) field. By doing that, more fields shall appear.
+12. In the __Authentication environment__ (Ambiente de Autenticação) field, fill in the `beta` value.
+13. In the __Environment type__ (Tipo de Ambiente) field, fill in the `2` value.
+14. Fill in the following fields with data provided by Itaú: _Client ID_ (Id do cliente), _Client Secret_ (Secret do cliente), and _Itaú Key_ (Chave do itau).
+15. In the __Days until "boleto" expires__ field, set the number of days immediately succeeding the "boleto" - popular Brazilian offline payment method - expiry date after which the transaction itself expires.
+16. Click on the __Save__ button.
 
 ## Setting up the Boleto Bancario payment condition
 1. After setting up the __Invoice Itaú__ gateway affiliation, click on the Payment Conditions tab.
diff --git a/docs/tutorials/en/setting-up-itau-registered-ticket.md b/docs/tutorials/en/setting-up-itau-registered-ticket.md
index 30b3ae810..1ae6741c6 100644
--- a/docs/tutorials/en/setting-up-itau-registered-ticket.md
+++ b/docs/tutorials/en/setting-up-itau-registered-ticket.md
@@ -3,8 +3,8 @@ title: 'Setting up Itaú registered ticket (ItauShopline)'
 id: 3TqzCHPU7KIYGsOKuUeQcq
 status: PUBLISHED
 createdAt: 2018-02-28T15:50:53.154Z
-updatedAt: 2023-03-29T01:19:04.085Z
-publishedAt: 2023-03-29T01:19:04.085Z
+updatedAt: 2024-03-18T18:27:01.365Z
+publishedAt: 2024-03-18T18:27:01.365Z
 firstPublishedAt: 2018-02-28T19:38:07.445Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md b/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
index 619a95dea..dcb89c290 100644
--- a/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
+++ b/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Provu (Lendico) "boleto" in installments as a payment method (Brazilian off-line payment method)'
 id: 1pRpPlkppLDEc1TVXTgrcu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-12-02T10:58:09.076Z
-updatedAt: 2023-03-26T21:47:26.770Z
-publishedAt: 2023-03-26T21:47:26.770Z
+updatedAt: 2024-07-23T18:06:34.554Z
+publishedAt: 
 firstPublishedAt: 2020-12-02T12:54:57.731Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md b/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md
index 280c3cce8..1a0cd0db5 100644
--- a/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md
+++ b/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up MercadoPagoV1 sub-acquirer'
 id: 6wTlR3UTJe6YMAsEuquO26
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-08T13:05:57.452Z
-updatedAt: 2023-03-22T18:05:53.962Z
-publishedAt: 2023-03-22T18:05:53.962Z
+updatedAt: 2024-03-18T18:35:39.248Z
+publishedAt: 
 firstPublishedAt: 2018-03-08T19:45:23.370Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,21 @@ legacySlug: setting-up-mercadopagov1-sub-acquirer
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 With the VTEX gateway, you can configure the MercadoPago [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) to operate in various ways. __MercadoPagoV1__ allows your store to receive payments using debit and credit cards, in addition to Mercado Pago's [digital wallet](/en/faq/what-is-an-e-wallet).
 
 <div class="alert alert-warning">
-  The <strong>MercadoPagoV1</strong> affiliation does not support payment using boleto bancario (payment method in Brazil).
+  The <strong>MercadoPagoV1</strong> integration does not support payment using boleto bancario (payment method in Brazil).
 </div>
 
 The steps below will let you set up MercadoPagoV1:
 
-## Setting up MercadoPagoV1 gateway affiliation
+## Setting up MercadoPagoV1
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. Click on the __+__ button, in the __Gateway affiliations__ tab.
-3. Click on the __MarketPagoV1__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __MercadoPagoV1__ in the search bar and click on the name of the provider.
 4. The __OAuth login__ field is not used. Leave it as it is.
 5. Fill in the __PublicKey__ and __AccessToken__ fields with the data provided by MercadoPago.
 6. Leave the __RefreshToken__, __ExpiredTokenIn__, and __Merchant Account Id__ fields blank.
diff --git a/docs/tutorials/en/setting-up-mercadopagov2-sub-acquirer.md b/docs/tutorials/en/setting-up-mercadopagov2-sub-acquirer.md
index 339db4ea0..f6219604c 100644
--- a/docs/tutorials/en/setting-up-mercadopagov2-sub-acquirer.md
+++ b/docs/tutorials/en/setting-up-mercadopagov2-sub-acquirer.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up MercadoPagoV2 sub-acquirer'
+title: 'Setting up payments with MercadoPagoV2'
 id: 1y6k8lCSzJYfPs2yObNFo4
 status: PUBLISHED
 createdAt: 2021-11-30T18:49:42.837Z
-updatedAt: 2023-03-22T18:35:39.911Z
-publishedAt: 2023-03-22T18:35:39.911Z
+updatedAt: 2024-03-11T18:11:39.540Z
+publishedAt: 2024-03-11T18:11:39.540Z
 firstPublishedAt: 2021-11-30T19:32:27.420Z
 contentType: tutorial
 productTeam: Financial
@@ -15,38 +15,42 @@ legacySlug: setting-up-mercadopagov2-sub-acquirer
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-With the VTEX gateway, you can configure the MercadoPagoV2 [sub-acquirer](https://help.vtex.com/en/tutorial/what-is-a-sub-acquirer#). Through it, your store can receive payments using traditional methods, such as: boleto, PIX, debit and credit cards, as well as exclusive methods of Mercado Pago, such as: MercadoPagoOff, MercadoPagoPro and MercadoPagoWallet.
-
-<div class="alert alert-warning">
-  The sub-acquirers <strong>MercadoPago</strong> and <strong>MercadoPagoV1</strong> do not allow receive through the PIX. This is an exclusive feature of <strong>MercadoPagoV2</strong>.
-</div>
-
-## Setting up MercadoPagoV2 gateway affiliation
-
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __"+" button__.
-3. Click on the __MercadoPagoV2__ connector.
-4. Fill in the __Application Key__ and __Application Token__ fields with the data provided by Mercado Pago.
-5. In the __Prazo de vencimento do boleto__ (“Boleto expiration date”), choose the number of days (counted from the creation of the boleto) that your customer will have to make the payment.
-6. Fill in the name of your store in the __Nome da loja__ (“Store name”). Remember that this is the information that will be described in the Beneficiário field of the boleto or on the customer’s card bill.
-7. In __Parcelamento máximo__ (“Max installments”), choose the maximum number of installments sent to MercadoPago.
-8. In __Categoria principal da loja__ (“Main Category”), choose the category that best fits your store.
-9. In the field __Reembolso automático / manual__ (“Automatic / manual refund”), choose whether the customer will be refunded automatically or manually in case of order cancellation.
-10. In __Modo binário__ (“Binary mode”), select “Yes” or “No”. Selecting “Yes” indicates that the payment approval process takes place instantly and can be approved or declined. Selecting “No” indicates that the payment can be in “pending” status (if it requires any action by the buyer) or “in process” (if manual review is required).
-11. In __Métodos de pagamento excluídos__ (“Excluded payment methods”), describe the payment methods you do not want to use through MercadoPagoV2 (optional). If you choose to leave this field blank, all available payment methods from MercadoPagoV2 will be available in your store. 
-12. In __Tipos de pagamento excluídos__ (“Excluded payment types”), describe the specific credit and debit brands (Visa, Mastercard, among others) that you do not want to use through MercadoPagoV2 (optional). If you choose to leave this field blank, all available payment types from MercadoPagoV2 will be available in your store. 
-13. In __Modo de processamento__ (“Processing Mode”), choose how you want to use MercadoPagoV2: as a sub-acquirer or as a gateway. For more information, access [What is a sub-acquirer?](https://help.vtex.com/en/tutorial/o-que-e-um-subadquirente--64aX6PeRQQ66O8uCqo0W4q#) and [What is a payment gateway?](https://help.vtex.com/en/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk#). 
-14. In the __Integrator ID__ option, indicate the identifier code of the developer or agency that performs the Mercado Pago configuration.
-15. In the __Moeda__ (“Currency”) option, choose whether the currency used for payment will be “Local” (each country) or “US Dollar” (USD).
-16. Click on __Salvar__ (“Save”).
-
-## Setting up the payment condition
-After following the steps indicated above, MercadoPagoV2 will be configured in your store. Thus, while you're registering a payment condition, it will be available in the __Process with affiliation__ field (provided that the payment method is compatible with MercadoPagoV2).
-
-For more on how to set up payment conditions, access [configuring payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento#).
+At VTEX, it is possible to integrate with the payment provider MercadoPagoV2. Through it, your store can receive payments using traditional methods, such as: bank slip, PIX, debit and credit cards, as well as through exclusive Mercado Pago methods, such as: MercadoPagoOff, MercadoPagoPro and MercadoPagoWallet.
+
+To configure MercadoPagoV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __MercadoPagoV2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the registration fields __App key__ and __App token__ with the data provided by Mercado Pago.
+5. If you wish to modify the identification name to be displayed for the MercadoPagoV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Prazo de vencimento do boleto__ (“Boleto expiration date”), choose the number of days (counting from the creation of the invoice) that your customer will have to make the payment.
+8. In __Nome da loja__ ("Store name"), enter your company name. This information will be described in the Beneficiary field of the bill or on the customer's card invoice.
+9. In __Parcelamento máximo__ ("Max installments"), choose the maximum number of installments sent to MercadoPago.
+10. In __Suporte 3DS 2.0__ ("3DS 2.0 Support"), select "Sí" if you want to enable 3DS security validation. For this protocol to work correctly, make sure that the __Mercado Pago Payment app__ is already installed in your store and that the __Modo binário__ ("Binary Mode") field (step 14) is selected as __No__.
+11. In __Categoria principal da loja__ ("Main store category"), choose the category of your store's industry.
+12. In __Compartilhamento de categoria (loja ou produto) por transação__ ("Category sharing (store or product) per transaction"), select whether you want to share store or product category data with Mercado Pago in each transaction.
+13. In the option __Reembolso automático / manual__ ("Automatic / manual refund"), choose whether the customer will be refunded automatically or manually in case of order cancellation.
+14. In __Modo binário__ ("Binary Mode"), indicate whether the store should accept pending payments. Selecting "Yes" indicates that the payment approval process occurs instantly, and can be approved or rejected. Selecting "No" defines that the payment can remain in "pending" status (if it requires any action from the buyer) or "in process" (if manual review is required).
+15. In __Métodos de pagamento excluídos__ ("Excluded payment methods"), describe the payment methods you do not want to use through MercadoPagoV2 (optional). If you choose to leave this field blank, all available payment methods from MercadoPagoV2 will be available in your store.
+16. In __Tipos de pagamento excluídos__ ("Excluded payment types"), describe the specific credit and debit brands (Visa, Mastercard, among others) that you do not want to use through MercadoPagoV2 (optional). If you choose to leave this field blank, all available payment types from MercadoPagoV2 will be available in your store.
+17. In __Modo de processamento__ ("Processing Mode"), choose how you want to use MercadoPagoV2: as a subacquirer (aggregator) or gateway. For more information, access [What is a sub-acquirer?](https://help.vtex.com/en/tutorial/what-is-a-sub-acquirer--64aX6PeRQQ66O8uCqo0W4q) and [What is a payment gateway?](https://help.vtex.com/en/tutorial/what-is-a-payment-gateway--2KH9Wdi7F6swOU4amECSOk).
+18. In the __Integrator ID__ option, indicate the identifier code of the developer or agency that performs the Mercado Pago configuration.
+19. In the __Moeda__ ("Currency") option, choose whether the currency used for payment will be "Local" (each country) or "US Dollar" (USD).
+20. The __Merchant Account ID__ field identifies the merchant account. It is not necessary to fill it out.
+21. In __Prazo de captura de pagamento aprovado__  ("Approved payment capture deadline"), select the desired deadline for payment capture.
+22. Em __Tempo para cancelar compras de um carrinho abandonado__ ("Time to cancel purchases from an abandoned cart"), enter the time interval that must be waited until the enabled payment methods are not available to make the purchase.
+23. Click __Save__.
+
+## Setting up payment conditions
+
+To configure the default payment methods to be processed by MercadoPagoV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
 ## Setting up exclusive payment methods
 
-To learn more about how to configure exclusive payment methods for Mercado Pago, access [setting up Mercado Pago Offline and Wallet as payment methods](https://help.vtex.com/en/tutorial/configurar-mercado-pago-offline-e-wallet-como-metodos-de-pagamentos).
+To configure exclusive Mercado Pago payment methods, go to [setting up Mercado Pago Offline and Wallet as payment methods](https://help.vtex.com/en/tutorial/configurar-mercado-pago-offline-e-wallet-como-metodos-de-pagamentos).
 
-For more information about the integration with Mercado Pago, access the [DevSite Mercado Pago](https://www.mercadopago.com.br/developers/en/guides/plugins/unofficial/vtex/gateway-affiliations).
+For more information about integration with Mercado Pago, access the [DevSite Mercado Pago](https://www.mercadopago.com.br/developers/en/guides/plugins/unofficial/vtex/gateway-affiliations).
diff --git a/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
index dded50683..13f353ff4 100644
--- a/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
@@ -35,16 +35,16 @@ Let's now turn our attention to the step-by-step process below:
 
 1. Access your Apple __developer account__ at `https://developer.apple.com/account/#/overview/`;
 2. Select the __Certificates, IDs & Profiles__ option.
-![AP1](https://images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
+![AP1](//images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
 3. Select __Identifiers__;
- ![AP2](https://images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
+ ![AP2](//images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
 4. Next to Identifiers, click on the __blue + button__;
-![AP3](https://images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
+![AP3](//images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
 5. Select the __Merchant IDs__ option;
-6. Click on the blue __Continue__ button; ![AP4](https://images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
+6. Click on the blue __Continue__ button; ![AP4](//images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
 7. Fill on the __description__ field;
 8. Fill in the __identifier__ field;
-9. Click on __continue__; ![AP5](https://images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
+9. Click on __continue__; ![AP5](//images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
 
 You will have created your __Merchant ID__.
 
@@ -58,13 +58,13 @@ Thereafter, the retailer can submit the file to Apple Pay's system.
 
 Follow the instructions below to proceed to this step:
 
-1. On the left-hand side, open __Certificates__ from the menu; ![AP6](https://images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
+1. On the left-hand side, open __Certificates__ from the menu; ![AP6](//images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
 2. Type in your newly created __Merchant ID__ in the search bar;
-3. Select the desired __Merchant ID__; ![AP7](https://images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
+3. Select the desired __Merchant ID__; ![AP7](//images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
 4. Under __Apple Pay Payment Processing Certificate__, click the __Create Certificate__ button. 
-![AP8](https://images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
+![AP8](//images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
 5. Ensure that the question *"Will payments associated with this Merchant ID be processed exclusively in China?"* is ticked with the __default option (No)__.
-![AP9](https://images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
+![AP9](//images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
 
 You'll then be redirected to a screen with instructions on creating the Certificate Signing Request (CSR). 
 
@@ -77,9 +77,9 @@ With the {{merchantID}}.csr. that you've received, complete the following:
 1. Click on __Choose File__;
 2.  Select the desired __CSR file__;
 3.  Click on __Continue__; 
-![AP10](https://images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
+![AP10](//images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
 4. Click on __Download__;
-![AP11](https://images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
+![AP11](//images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
 5. Click on __Done__.
 
 ## Adding domains to Merchant ID
@@ -97,16 +97,16 @@ Lastly, you need to import this file to VTEX's system through Postman - an [API]
 Follow these steps:
 
 1. Search for the recently created __MerchantID__ in the search bar;
-![AP12](https://images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
+![AP12](//images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
 2. Click on the desired __MerchantID__;
 3. In the __Merchant Domain__ module, click on __Add Domain__;
-![AP13](https://images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
+![AP13](//images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
 4. Add the domain in the __Enter the domain you wish to register__ field;  5. Click on __save__.
 
 Thereafter, to upload the `.txt` file by API, follow these instructions:
 
 1. Click on __Download__ and make no changes to the file.
-![AP14](https://images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
+![AP14](//images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
 2. Open the `.txt` file and __copy__ all the content.
 
 Then, start a Postman session. You perform a call to VTEX's CDN using the POST method:
@@ -118,7 +118,7 @@ Then, start a Postman session. You perform a call to VTEX's CDN using the POST m
 Now, when making the _POST_ call, the response will inform you that your certificate will be saved for 60 minutes. During this time, you should complete the domain validation.
 
 Head back to the Apple's website. On the same screen where you downloaded the `.txt` file, click on __Verify__.
-![AP15](https://images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
+![AP15](//images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
 
 If you've followed the step-by-step correctly, your domain will be registered with the __verified__ status. If you want, you can repeat the process to add more domains by using the __Add Domain__ button in the __Merchant Domains__ section. 
 
@@ -134,12 +134,12 @@ Notice: we recommend an easy to remember password, since it will be filled into
 
 1. Access the __Certificate, Identifiers & Profilers__ module;
 2. From the left side menu, choose __Identifiers__;
-3. In the upper right corner, filter by __Merchant IDs__; ![AP16](https://images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
+3. In the upper right corner, filter by __Merchant IDs__; ![AP16](//images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
 4. Select the desired __Merchant Identifier__;
-5. Click on __Create Certificate__; ![AP17](https://images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
+5. Click on __Create Certificate__; ![AP17](//images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
 6. Follow the __instructions__ displayed on the screen to create a certificate;
-7. Click on __Continue__;  ![AP18](https://images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
-8. Click on __Download__.  ![AP19](https://images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
+7. Click on __Continue__;  ![AP18](//images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
+8. Click on __Download__.  ![AP19](//images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
 
 After the file has been downloaded, double-click it to install it in Keychain Access.
 
@@ -147,7 +147,7 @@ Afterwards, proceed to the following steps:
 
 1. Open __Keychain Access__;
 2. Locate the __certificate__ created in step 4 above;
-3. Right click on the __key__ icon; ![AP20](https://images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
+3. Right click on the __key__ icon; ![AP20](//images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
 4. Click on __Export__;
 5. Give the __certificate__ a name;
 6. Select the __.p12__ export format;
diff --git a/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md b/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md
index b637d38dc..dedc9d616 100644
--- a/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md
+++ b/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Mundipagg Fraud Prevention gateway'
 id: yFbysX42GW2wawu82q6QA
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-04-18T21:01:40.512Z
-updatedAt: 2023-03-29T00:39:20.112Z
-publishedAt: 2023-03-29T00:39:20.112Z
+updatedAt: 2024-03-18T18:40:56.708Z
+publishedAt: 2024-02-16T12:17:04.418Z
 firstPublishedAt: 2018-04-18T21:23:11.844Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-mundipagg-fraud-prevention-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Mundipagg offers a version of its [gateway](/en/tutorial/what-is-a-payment-gateway) with anti-fraud functionality. Mundipagg Fraud Prevention brings even more security to the processing of purchases made with bank slips, bank transfers and major credit card brands.
 
 To configure Mundipagg Fraud Prevention, follow the steps below:
 
-## Setting up Mundipagg Fraud Prevention gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Mundipagg Fraud Prevention__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Mundipagg Fraud Prevention__ in the search bar and click on the name of the provider.
 4. Fill in the __Merchant Key__ field with the key registered in Mundipagg. It consists of 36 characters, including letters, numbers and hyphens.
 5. In __País__ ("Country"), choose the country of your store.
 6. The __Register Url Post Notification em Mundipagg__ field gives an address for you to set up the receiving of notifications about payment statuses. In the `https://{sellerhost}.vtexpayments.com.br/mundipagg/payment/statusnotification` link, replace `{sellerhost}` with your store's account name. Then, send the final URL to Mundipagg to complete the registration.
diff --git a/docs/tutorials/en/setting-up-mundipagg-gateway.md b/docs/tutorials/en/setting-up-mundipagg-gateway.md
index 12f9ec4d9..2d51abf6b 100644
--- a/docs/tutorials/en/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/en/setting-up-mundipagg-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Mundipagg gateway'
 id: 6C9412jePCUMGguq0YWU8M
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T18:01:44.533Z
-updatedAt: 2023-03-29T00:36:17.690Z
-publishedAt: 2023-03-29T00:36:17.690Z
+updatedAt: 2024-03-18T18:39:56.272Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T20:58:03.675Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-mundipagg-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Mundipagg is a [gateway](/en/tutorial/what-is-a-payment-gateway) that processes payments made with bank slips, bank transfers and major credit card brands.
 
 To configure Mundipagg, follow the steps below:
 
-## Setting up Mundipagg gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Mundipagg__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Mundipagg__ in the search bar and click on the name of the provider.
 4. Fill in the __Merchant Key__ field with the key registered in Mundipagg. It consists of 36 characters, including letters, numbers and hyphens.
 5. In __Pais__ ("Country"), choose the country of your store.
 6. The __Register Url Post Notification at Mundipagg__ field gives an address for you to set up the receiving of notifications about payment statuses. In the link `https://{sellerhost}.vtexpayments.com.br/mundipagg/payment/statusnotification`, replace `{sellerhost}` with your store's account name. Then, send the final URL to Mundipagg to complete the registration.
diff --git a/docs/tutorials/en/setting-up-my-account.md b/docs/tutorials/en/setting-up-my-account.md
index c38bdf487..af19ff149 100644
--- a/docs/tutorials/en/setting-up-my-account.md
+++ b/docs/tutorials/en/setting-up-my-account.md
@@ -3,8 +3,8 @@ title: 'Setting up My Account'
 id: 23Ayv5D6b86UBnYfoXqZL1
 status: PUBLISHED
 createdAt: 2019-02-19T21:35:31.855Z
-updatedAt: 2021-05-24T18:07:48.662Z
-publishedAt: 2021-05-24T18:07:48.662Z
+updatedAt: 2023-12-21T14:12:18.587Z
+publishedAt: 2023-12-21T14:12:18.587Z
 firstPublishedAt: 2019-02-19T21:37:25.249Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: setting-up-my-account
 subcategory: 1RWR7qSyaREbD5RfgCjdYG
 ---
 
+<div class = "alert alert-info">
+In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
+</div>
+
 The new [My Account](https://help.vtex.com/en/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh) is already installed in all VTEX accounts pertaining to a <strong>test environment</strong>, allowing adjustments on the new page to be implemented without impacting user experience.
 
 This means that My Account already makes it possible for your store to customize when needed, before the app's bulk migration to production, through the link shown below:
diff --git a/docs/tutorials/en/setting-up-nexxpago-gateway.md b/docs/tutorials/en/setting-up-nexxpago-gateway.md
index 89a5cc029..fd2e2634c 100644
--- a/docs/tutorials/en/setting-up-nexxpago-gateway.md
+++ b/docs/tutorials/en/setting-up-nexxpago-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Nexxpago gateway'
 id: 28Fgmof1WYEeAcM8MkOcWm
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T15:46:11.611Z
-updatedAt: 2023-03-29T01:08:32.601Z
-publishedAt: 2023-03-29T01:08:32.601Z
+updatedAt: 2024-03-18T18:58:03.614Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T16:05:40.588Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-nexxpago-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Nexxpago is a [PCI-certified](/en/faq/what-is-the-pci-ssc) company that offers a variety of payment solutions. The main one is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) that allows processing payments through bank and credit cards.
 
 To configure Nexxpago, follow the steps below:
 
-## Setting up NexxPago gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Nexxpago__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Nexxpago__ in the search bar and click on the name of the provider.
 4. In the __External Service Url__ field, you must configure the external URL that will be associated with `/pvt/payments?an={AccountName}`.
 5. Fill in the registration fields with the data provided by Nexxpago (fields _appKey_ and _appToken_).
 6. In __Implements Installments Service__, choose whether you want to use external installment services or the one configured on the portal. If you choose _yes_, the system will use the URL configured in the __Installments Service Url__ field.
@@ -31,7 +32,10 @@ To configure Nexxpago, follow the steps below:
 9. In __SoftDescriptor__, indicate the text that will appear to identify transactions made in your store.
 10. In __Early security capture__, choose how long you want the capture to take after the transaction approval and the anti-fraud analysis. You can also disable this function.
 11. In __Use Anti-fraude__, inform if you wish to use the anti-fraud system.
-12. Click __Save__.
+12. Click `Save`.
+
+To configure the payment methods to be processed by Nexxpago, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-## Setting up the payment condition
-After following the indicated steps, Nexxpago will be configured in your store. So while you're registering a payment condition, it will be available in the __Process with affiliation__ field (provided the payment method is compatible with Nexxpaago). To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+After following the indicated steps, Nexxpago may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-nps-gateway.md b/docs/tutorials/en/setting-up-nps-gateway.md
index e137e6bc4..91710997a 100644
--- a/docs/tutorials/en/setting-up-nps-gateway.md
+++ b/docs/tutorials/en/setting-up-nps-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Ingenico ePayments (NPS) gateway'
 id: 4DtjieyNQIQeI2O2kymEgq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T13:22:00.721Z
-updatedAt: 2023-03-29T01:15:32.462Z
-publishedAt: 2023-03-29T01:15:32.462Z
+updatedAt: 2024-03-18T19:00:20.612Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T15:09:45.694Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-nps-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Ingenico ePayments (NPS) is a [gateway](/en/tutorial/what-is-a-payment-gateway) with a strong presence in Latin America which allows your store to accept various payment conditions.
 
 To set up NPS, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-pagar-me-gateway.md b/docs/tutorials/en/setting-up-pagar-me-gateway.md
index 523016883..94b1164e2 100644
--- a/docs/tutorials/en/setting-up-pagar-me-gateway.md
+++ b/docs/tutorials/en/setting-up-pagar-me-gateway.md
@@ -3,8 +3,8 @@ title: 'Setting up Pagar.me gateway'
 id: egFyDkXjfa80wkSkUWsmc
 status: PUBLISHED
 createdAt: 2018-04-10T17:54:18.410Z
-updatedAt: 2023-03-26T21:05:35.943Z
-publishedAt: 2023-03-26T21:05:35.943Z
+updatedAt: 2024-01-23T19:17:28.562Z
+publishedAt: 2024-01-23T19:17:28.562Z
 firstPublishedAt: 2018-04-10T18:10:52.337Z
 contentType: tutorial
 productTeam: Financial
@@ -19,10 +19,9 @@ Pagar.me is a [gateway](/en/tutorial/what-is-a-payment-gateway) that offers seve
 
 To set up Pagar.me, follow the steps below:
 
-## Setting up Pagar.me gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Pagar.me__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Pagar.me__ in the search bar and click on the name of the provider.
 4. In the __External Service Url__ field, configure the external URL that will be associated with `/pvt/payments?an={AccountName}`.
 5. Fill in the registration fields with the data provided by Pagar.me (fields __appKey__ and __appToken__).
 6. In __Implements Installments Service__, you must choose whether you want to use external installment services or the one that is configured on the portal. If you choose _yes_, the system will use the URL configured in the __Installments Service Url__ field.
diff --git a/docs/tutorials/en/setting-up-pagarmev2-gateway.md b/docs/tutorials/en/setting-up-pagarmev2-gateway.md
index cbeadc7bf..f4281bb50 100644
--- a/docs/tutorials/en/setting-up-pagarmev2-gateway.md
+++ b/docs/tutorials/en/setting-up-pagarmev2-gateway.md
@@ -3,8 +3,8 @@ title: 'Setting up PagarMeV2 gateway'
 id: 5TugxXNMOs0Ocyg4uqussM
 status: PUBLISHED
 createdAt: 2018-04-10T18:50:48.932Z
-updatedAt: 2023-03-26T21:04:07.182Z
-publishedAt: 2023-03-26T21:04:07.182Z
+updatedAt: 2024-01-23T19:19:58.174Z
+publishedAt: 2024-01-23T19:19:58.174Z
 firstPublishedAt: 2018-04-11T21:51:25.333Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,20 @@ legacySlug: setting-up-pagarmev2-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-PagarMeV2 is the latest version of the [Pagar.me gateway](https://help.vtex.com/pt/tutorial/o-que-e-um-gateway-de-pagamentos) affiliation. Follow the steps below to configure it:
+At VTEX, it is possible to process payments with the PagarMe provider through V2 and V3 integrations.
 
-## Setting up PagarMeV2 gateway affiliation
+<div class="alert alert-warning">
+If you want to configure the V3 version of Pagarme in your store, go to <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-pagarmev3--5PMavdamrVijwIrHas9ndE">Setting up payments with PagarMeV3</a>.
+</div>
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In __Gateway Affiliations__, click on the green “__+__” button.
-3. Search for __PagarMeV2__ and select its card.
+To configure PagarMeV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagarMeV2__ in the search bar and click on the name of the provider.
 4. Fill in the fields with the following information:<br>
 <ul>
-<li><b>Application Key</b> e <b>Application Token</b>: enter the information provided by Pagar.me.</li>
+<li><b>App Key</b> e <b>App Token</b>: enter the information provided by Pagar.me.</li>
 <li><b>Payment capture:</b>: select one of the following options:<br><br>
     <ul>
     	<li><b>Use behavior recommended by the payment processor</b>: acapture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior.).</li>
diff --git a/docs/tutorials/en/setting-up-pagbrasil-gateway.md b/docs/tutorials/en/setting-up-pagbrasil-gateway.md
index 367f190cf..abf1588d5 100644
--- a/docs/tutorials/en/setting-up-pagbrasil-gateway.md
+++ b/docs/tutorials/en/setting-up-pagbrasil-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up PagBrasil gateway'
 id: 2vzj6MkFRuKm4KQAOOmWaa
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-10T12:40:34.957Z
-updatedAt: 2023-03-29T01:00:48.970Z
-publishedAt: 2023-03-29T01:00:48.970Z
+updatedAt: 2024-03-18T19:02:31.069Z
+publishedAt: 
 firstPublishedAt: 2018-04-10T12:50:24.707Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-pagbrasil-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 PagBrasil is a gateway specialized in Brazilian payment methods, mainly credit and debit cards, online transfers, and bank vouchers.
 
 To configure PagBrasil, follow the steps below:
 
-## Setting up PagBrasil gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __PagBrasil__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagBrasil__ in the search bar and click on the name of the provider.
 4. In the __External Service Url__ field, you must configure the external URL that will be associated with `/pvt/payments?an={AccountName}`.
 5. Fill in the registration fields with the data provided by PagBrasil (fields _appKey_ and _appToken_).
 6. In __Implements Installments Service__, choose whether you want to use external installment services or the one configured on the portal. If you choose _yes_, the system will use the URL configured in the __Installments Service Url__ field.
diff --git a/docs/tutorials/en/setting-up-paghiper-gateway.md b/docs/tutorials/en/setting-up-paghiper-gateway.md
index 494b5aeb3..0cfefd29e 100644
--- a/docs/tutorials/en/setting-up-paghiper-gateway.md
+++ b/docs/tutorials/en/setting-up-paghiper-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up PagHiper gateway'
 id: I3KXAIIJG0oyyg4A4MykE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-09T22:06:11.621Z
-updatedAt: 2023-03-29T01:13:11.291Z
-publishedAt: 2023-03-29T01:13:11.291Z
+updatedAt: 2024-03-18T19:04:40.079Z
+publishedAt: 
 firstPublishedAt: 2018-04-09T22:43:35.309Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-paghiper-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 PagHiper is a [gateway](/en/tutorial/what-is-a-payment-gateway) specialized in the processing of purchases made through bank slips.
 
 To set up PagHiper, follow the steps below:
 
-## Setting up PagHiper gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __PagHiper__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagHiper__ in the search bar and click on the name of the provider.
 4. In the __External Service Url__ field, you must configure the external URL that will be associated with `/pvt/payments?an={AccountName}`.
 5. Fill in the registration fields with the data provided by PagHiper (fields _appKey_ and _appToken_).
 6. In __Implements Installments Service__, you must choose whether you want to use external installment services or the one configured on the portal. If you choose _yes_, the system will use the URL configured in the __Installments Service Url__ field.
diff --git a/docs/tutorials/en/setting-up-pagseguro-v3.md b/docs/tutorials/en/setting-up-pagseguro-v3.md
index 9f27aaebe..590076435 100644
--- a/docs/tutorials/en/setting-up-pagseguro-v3.md
+++ b/docs/tutorials/en/setting-up-pagseguro-v3.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up PagSeguro V3'
+title: 'Setting up payments with PagBankV3'
 id: 5Noi1mUbBQ6CyqdeDQtWfw
 status: PUBLISHED
 createdAt: 2021-12-02T12:14:58.698Z
-updatedAt: 2023-03-23T15:40:31.170Z
-publishedAt: 2023-03-23T15:40:31.170Z
+updatedAt: 2024-03-14T18:59:12.645Z
+publishedAt: 2024-03-14T18:59:12.645Z
 firstPublishedAt: 2021-12-02T19:18:21.251Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,30 @@ legacySlug: setting-up-pagseguro-v3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-If you have a PagSeguro account, you can configure PagseguroV3 on the VTEX gateway to receive payments by: boleto, PIX, debit and credit cards.
+At VTEX, it is possible to integrate with the payment provider PagBankV3. Through this provider, your store can make sales via bank slip, PIX, debit and credit cards.
 
-## Setting up PagseguroV3 gateway affiliation
+To configure PagBankV3, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __"+" button__.
-3. Click on the __PagSeguroV3__ connector.
-4. In __Click to authorize VTEX to make payments__, click on __Authorize__. At this moment, you will be redirected to the PagSeguro webpage, where you will have to access your account, and authorize the connection of VTEX in your PagSeguro account.
-5. After authorizing, you will automatically return to the VTEX Admin, and the __Application Key__, __Application Token__, __Application Id__ fields will already be filled in.
-6. Click on __Save__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagBankV3__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, click on __Authorize via OAuth__. At this point, you will be redirected to the PagBank page, where you must access your account and authorize the connection of VTEX to your PagBank account. After the authorization process, you will automatically return to the VTEX Admin.
+5. If you wish to modify the identification name to be displayed for the PagBankV3 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Under __Payment Control__, in the __Automatic Settlement__ field, select one of the following options:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+7. If you want to use [payment split](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx) in your store, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
+8. In __Provider Fields__, in the __Prazo para captura do pagamento__ field, select the desired period to capture the payment.
+9. Click __Save__.
 
-## Setting up the payment condition
-After following the steps indicated above, PagSeguroV3 will be configured in your store. Thus, while you're registering a payment condition, it will be available in the __Process with affiliation__ field (provided that the payment method is compatible with PagSeguroV3).
+To configure the payment methods to be processed by PagBankV3, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-For more on how to set up payment conditions, access [configuring payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento#).
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PagBankV3 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payment-with-paypal.md b/docs/tutorials/en/setting-up-payment-with-paypal.md
index c0129819d..df8bd2b48 100644
--- a/docs/tutorials/en/setting-up-payment-with-paypal.md
+++ b/docs/tutorials/en/setting-up-payment-with-paypal.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with PayPal'
 id: 4p3sD9u1moq2Aya2oc684w
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-21T17:15:53.516Z
-updatedAt: 2023-03-21T20:46:52.481Z
-publishedAt: 2023-03-21T20:46:52.481Z
+updatedAt: 2024-03-18T20:29:36.504Z
+publishedAt: 
 firstPublishedAt: 2018-02-21T17:54:19.079Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-payment-with-paypal
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 At VTEX gateway, you can set up the PayPal sub-acquirer to receive your payments. Through it, your customer chooses the PayPal __payment method__ and performs their authentication in the PayPal environment.
 
 To set it up, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-paymentez-gateway.md b/docs/tutorials/en/setting-up-paymentez-gateway.md
index 9620f3afc..86adf5e58 100644
--- a/docs/tutorials/en/setting-up-paymentez-gateway.md
+++ b/docs/tutorials/en/setting-up-paymentez-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Paymentez gateway'
 id: 7zmH2WCtVuAoUUQWyU2qgO
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-28T17:47:41.909Z
-updatedAt: 2023-03-26T22:08:53.622Z
-publishedAt: 2023-03-26T22:08:53.622Z
+updatedAt: 2024-03-18T19:16:05.956Z
+publishedAt: 
 firstPublishedAt: 2018-03-28T18:18:57.206Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-paymentez-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Paymentez is a [gateway](/en/tutorial/what-is-a-payment-gateway) with [PCI certification](/en/faq/what-is-the-pci-ssc) level 2 and has its operations concentrated in Latin America.
 
-To set up Paymentez, follow the steps below:
+To configure Paymentez, follow the steps below:
 
-## Setting up Paymentez gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway affiliations__ tab, click the __+__ button.
-3. Click the __Paymentez__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Paymentez__ in the search bar and click on the name of the provider.
 4. In the __External Service Url__ field, you must configure the external URL that will be associated with `/pvt/payments?an={AccountName}`.
 5. Fill in the registration fields with the data provided by Paymentez (_appKey_ and _appToken_ fields).
 6. In __Implements Installments Service__, choose whether you want to use external installment services or the one that is configured on the portal. If you choose _yes_, the system will use the URL configured in the __Installments Service Url__ field.
@@ -31,7 +32,10 @@ To set up Paymentez, follow the steps below:
 9. In __SoftDescriptor__, insert the thext that will appear to identify the transactions made in your store.
 10. In __Early security capture__ , choose how long you want the capture to take after the transaction approval and anti-fraud analysis. You can also disable this function.
 11. In __Have an anti-fraud deal with this affiliation?__ , tell us if you wish to use anti-fraud.
-12. Click __Save__.
+12. Click `Save`.
+
+To configure the payment methods to be processed by Paymentez, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-## Setting up the payment condition
-After following the steps indicated above, Paymentez will be configured in your store. So while you're registering a payment condition, it will be available in the __Process with affiliation__ field (provided the payment method is compatible with Paymentez). To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+After following the indicated steps, Paymentez may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-55pay.md b/docs/tutorials/en/setting-up-payments-with-55pay.md
index c26dd06d9..837e693bb 100644
--- a/docs/tutorials/en/setting-up-payments-with-55pay.md
+++ b/docs/tutorials/en/setting-up-payments-with-55pay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with 55PAY'
 id: 4ktYG4reu5T6taEj2pKjvZ
 status: PUBLISHED
 createdAt: 2022-05-05T13:22:59.869Z
-updatedAt: 2023-03-26T21:43:11.110Z
-publishedAt: 2023-03-26T21:43:11.110Z
+updatedAt: 2024-01-23T18:31:36.516Z
+publishedAt: 2024-01-23T18:31:36.516Z
 firstPublishedAt: 2022-05-05T13:44:32.122Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-99pay.md b/docs/tutorials/en/setting-up-payments-with-99pay.md
index 8d637c941..deacd5aea 100644
--- a/docs/tutorials/en/setting-up-payments-with-99pay.md
+++ b/docs/tutorials/en/setting-up-payments-with-99pay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with 99Pay'
 id: QIStxPsGb6LoIwFBfcTfb
 status: PUBLISHED
 createdAt: 2023-04-06T19:37:06.116Z
-updatedAt: 2023-04-06T19:41:32.060Z
-publishedAt: 2023-04-06T19:41:32.060Z
+updatedAt: 2024-01-23T18:31:10.050Z
+publishedAt: 2024-01-23T18:31:10.050Z
 firstPublishedAt: 2023-04-06T19:41:32.060Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-99pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the 99Pay payment provider. With this connector, your store can make sales through 99Pay.
+At VTEX, it is possible to integrate with the 99Pay payment provider. With this provider, your store can make sales through 99Pay.
 
-To configure 99Pay affiliation, follow the steps below:
+To configure 99Pay, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __99Pay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __99Pay__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by 99Pay.
 5. In the __Payment settlement__ field, select one of the available options:
 
diff --git a/docs/tutorials/en/setting-up-payments-with-aarin.md b/docs/tutorials/en/setting-up-payments-with-aarin.md
index 48931d1ff..a1eac90c4 100644
--- a/docs/tutorials/en/setting-up-payments-with-aarin.md
+++ b/docs/tutorials/en/setting-up-payments-with-aarin.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Aarin'
 id: 2kVQVFqutbZYK3I6XBVgLp
 status: PUBLISHED
 createdAt: 2022-06-22T12:45:29.082Z
-updatedAt: 2023-03-26T21:42:40.807Z
-publishedAt: 2023-03-26T21:42:40.807Z
+updatedAt: 2024-01-23T18:32:06.337Z
+publishedAt: 2024-01-23T18:32:06.337Z
 firstPublishedAt: 2022-06-22T13:00:38.494Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-addi.md b/docs/tutorials/en/setting-up-payments-with-addi.md
index 4afd90011..6e76e3b91 100644
--- a/docs/tutorials/en/setting-up-payments-with-addi.md
+++ b/docs/tutorials/en/setting-up-payments-with-addi.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Addi'
 id: 7FhMbT3hN2i5je74lqx6QI
 status: PUBLISHED
 createdAt: 2022-02-14T12:22:11.957Z
-updatedAt: 2023-03-27T12:46:46.989Z
-publishedAt: 2023-03-27T12:46:46.989Z
+updatedAt: 2024-01-23T18:29:23.380Z
+publishedAt: 2024-01-23T18:29:23.380Z
 firstPublishedAt: 2022-02-14T15:04:37.219Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-addi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Addi payment provider. With this connector, your store can make installment sales without a credit card.
+At VTEX, it is possible to integrate with the Addi payment provider. With this provider, your store can make installment sales without a credit card.
 
-To configure Addi affiliation, follow the steps below:
+To configure Addi, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __+__ button.
-3. Click on the __Addi__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Addi__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Addi.
 5. In the __Country of Operation__ field, select the country where the connector will operate.
 6. Click on __Save__.
diff --git a/docs/tutorials/en/setting-up-payments-with-alignet.md b/docs/tutorials/en/setting-up-payments-with-alignet.md
index 407556ddb..03d768380 100644
--- a/docs/tutorials/en/setting-up-payments-with-alignet.md
+++ b/docs/tutorials/en/setting-up-payments-with-alignet.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with Alignet'
 id: 4qfl6jgDyMGA0IuM0siEii
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-28T20:48:01.728Z
-updatedAt: 2023-03-29T01:04:08.516Z
-publishedAt: 2023-03-29T01:04:08.516Z
+updatedAt: 2024-03-18T17:48:35.669Z
+publishedAt: 
 firstPublishedAt: 2018-03-28T23:00:56.209Z
 contentType: tutorial
 productTeam: Financial
@@ -15,30 +15,32 @@ legacySlug: setting-up-payments-with-alignet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 On VTEX platform, you can set up the Alignet [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) to receive payments in your store. With it, your client chooses the __payment method__ Alignet and is redirected for authentication in the sub-acquirer's environment.
 
-To set it up, follow the steps below:
+To configure Alignet, follow the steps below:
 
-## Setting up Alignet gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway affiliations__ tab, click the __+__ button.
-3. Click the __Alignet__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Alignet__ in the search bar and click on the name of the provider.
 4. In the __Acquirer__ field, choose the acquirer that will be used in the integration.
 5. Fill in the registration fields with the data provided by Alignet (fields _Código Adquirente_, _CodigoComercio_, _CodigoMall_, _CodigoTerminal_ _ChavePrivadaAssinatura_, _ChavePrivadaCriptografia_, _ChavePublicaAssinaturaAlignet_ and _ChavePublicaCriptografiaAlignet_).
 6. In the __CodigoMoeda__ field, fill in the code [ISO 4217](https://pt.wikipedia.org/wiki/ISO_4217) of the currency that will be used in the payments.
 7. In __Linguagem__ ("Language"), choose between Spanish and English.
 8. In the __Vector__ field, fill in the sequence of up to 16 characters (letters and numbers only) generated by your store.
-9. Click __Save__.
+9. Click `Save`.
 
 ## Setting up Alignet payment condition
+
 1. Within the Payments __Settings__, click on the __Payment conditions__ tab.
 2. Click the __+__ button.
 3. Click __Alignet__ payment method.
 4. Click the __Status__ button to enable this payment condition.
 5. If your store has an anti-fraud set up, you can activate it by checking the __Use Anti-Fraud__ box.
 6. If you wish, you can also add a [special payment condition](/en/tutorial/special-conditions).
-8. Click __Save__.
+8. Click ´Save`.
 
 After following the steps indicated above, Alignet will appear at your store checkout as a payment option. After clicking __Finish Purchase__, your client will be redirected to authentication in the Alignet environment. 
 
-You may also enable this payment condition by using the [Pay-me connector](/en/tutorial/setting-up-pay-me-gateway).
+You may also enable this payment condition by using the [PayMee](https://help.vtex.com/en/tutorial/setting-up-the-paymee-gateway--3fsilRdrBS6GOAy622soWy).
diff --git a/docs/tutorials/en/setting-up-payments-with-alignetv2.md b/docs/tutorials/en/setting-up-payments-with-alignetv2.md
new file mode 100644
index 000000000..4beb5882e
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-alignetv2.md
@@ -0,0 +1,39 @@
+---
+title: 'Setting up payments with AlignetV2'
+id: 1rZU7cexTYdzB4SHWjr3eJ
+status: PUBLISHED
+createdAt: 2024-03-07T16:37:07.030Z
+updatedAt: 2024-03-07T16:56:11.973Z
+publishedAt: 2024-03-07T16:56:11.973Z
+firstPublishedAt: 2024-03-07T16:56:11.973Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-alignetv2
+locale: en
+legacySlug: setting-up-payments-with-alignetv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the AlignetV2 payment provider. With this provider, your store can make sales through credit cards.
+
+To configure AlignetV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __AlignetV2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ fields with data provided by your account AlignetV2.
+5. If you wish to modify the identification name to be displayed for the AlignetV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on the name of the desired credit card brand.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, AlignetV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-ame-digital.md b/docs/tutorials/en/setting-up-payments-with-ame-digital.md
index 9fc8f11e0..82e76ff93 100644
--- a/docs/tutorials/en/setting-up-payments-with-ame-digital.md
+++ b/docs/tutorials/en/setting-up-payments-with-ame-digital.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Ame Digital'
 id: 4oEhDjLM4uk95X8omwLEG2
 status: PUBLISHED
 createdAt: 2022-02-14T17:02:38.944Z
-updatedAt: 2023-03-26T21:42:08.346Z
-publishedAt: 2023-03-26T21:42:08.346Z
+updatedAt: 2024-01-23T18:28:00.633Z
+publishedAt: 2024-01-23T18:28:00.633Z
 firstPublishedAt: 2022-02-14T17:35:18.865Z
 contentType: tutorial
 productTeam: Financial
@@ -15,9 +15,9 @@ legacySlug: setting-up-payments-with-ame-digital
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Ame Digital payment provider. With this connector, your store can make sales in full or installments payments, with QR Code or payment link. In addition, your customers can have access to cashback during their purchases.
+At VTEX, it is possible to integrate with the Ame Digital payment provider. With this provider, your store can make sales in full or installments payments, with QR Code or payment link. In addition, your customers can have access to cashback during their purchases.
 
-To configure Ame Digital affiliation, follow the steps below:
+To configure Ame Digital, follow the steps below:
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. In the __Gateway affiliations__ tab, click on the __+__ button.
@@ -27,9 +27,9 @@ To configure Ame Digital affiliation, follow the steps below:
 
 ## Setting up the payment condition
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Payment Conditions__ tab, click on the __+__ button.
-3. Choose the payment condition __AmeDigital__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __AmeDigital__ in the search bar and click on the name of the provider.
 4. Fill the __Rule Name__ field with a name of your choice for identification.
 5. Activate the condition in the __Status__ field.
 6. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
diff --git a/docs/tutorials/en/setting-up-payments-with-apple-pay.md b/docs/tutorials/en/setting-up-payments-with-apple-pay.md
index f553505ec..17678bf4d 100644
--- a/docs/tutorials/en/setting-up-payments-with-apple-pay.md
+++ b/docs/tutorials/en/setting-up-payments-with-apple-pay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Apple Pay'
 id: 5L3NWMgvdKswWQa6eIc008
 status: PUBLISHED
 createdAt: 2018-04-12T20:38:42.521Z
-updatedAt: 2023-03-26T21:54:30.284Z
-publishedAt: 2023-03-26T21:54:30.284Z
+updatedAt: 2024-06-25T21:20:56.252Z
+publishedAt: 2024-06-25T21:20:56.252Z
 firstPublishedAt: 2018-05-23T19:26:11.000Z
 contentType: tutorial
 productTeam: Financial
@@ -24,40 +24,32 @@ Your customers can shop using Apple Pay, the [digital wallet](/en/faq/what-is-an
   Apple Pay currently only works on MacOs, IOS operating systems, and the Safari browser. For more information, go to <a href="https://support.apple.com/en-gb/HT208531">Devices compatible with Apple Pay</a>.
 </div>
 
-With these requirements met, just follow the steps below to offer this payment condition in your store:
+## Setting up the payment provider
 
-## Setting up the gateway affiliation
-Offering payment conditions to customers in your store depends on gateway affiliates being able to process them. On the VTEX platform, the affiliations currently compatible with __Apple Pay__ are __ERedeREST__ (integration of the acquirer Rede), __Adyen__ and __Stripe__.
+Firstly, you need to configure a provider in your store's Admin that processes transactions with Apple Pay, such as [Adyen](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3) and [Stripe](https://help.vtex.com/en/tutorial/configuring-stripe-gateway-affiliation--fwF2wk2FQKrODrWWkvSLO).
 
-These articles show how to set up [ERedeREST](/en/tutorial/setting-up-rede-acquirer-with-erederest), [Adyen](/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex) and [Stripe](https://help.vtex.com/en/tutorial/configuring-stripe-gateway-affiliation--fwF2wk2FQKrODrWWkvSLO).  
+To check all the provider options available for this payment method, access the list as described in Step 5 of the section [Set up payment with Apple Pay](#setting-up-payment-with-apple-pay).
 
-But remember: it's critical to [register the Merchant ID on Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay) before setting up the gateway affiliation.
+<div class="alert alert-warning">
+  Before starting to configure the provider, you must <a href="register your Merchant ID with Apple Pay">register your Merchant ID with Apple Pay</a>.
+</div>
 
-## Downloading and installing VTEX App Store application
-1. On the admin side menu, click __Apps__.
-2. Access the __VTEX App Store__ link or use the URL `https://apps.vtex.com/?an={{AccountName}}` directly in the browser, changing `{{AccountName}}` to the name of the store in which you want to offer Apple Pay.
-3. Browse for the __Apple Pay__ app and click __Get__.
-4. You will be directed to an order review screen. Check the data and click the __Confirm order and begin installation__ button.
-5. You will get to the installation screen. There, you can review the application permissions and start the download (by clicking __Instalar__).
-6. The app will be installed on your workspace, but you will need to fill in the __Merchant ID__ (in the __Merchant Identifier__ field) to be applied in your store.
-7. Click __Save__.
+## Setting up payment with Apple Pay
 
-## Setting up Apple Pay payment condition
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. Click the __Payment conditions__ tab and then the __+__ button.
 3. Select the __Apple Pay__ payment method.
-4. Click the __Status__ button to enable this payment condition.
-5. In the __Process with affiliation__ field, select the option that will be used to process the payments.
-6. If there is an anti-fraud set up in your store, you can activate it for this payment condition by checking the __Use Anti-Fraud__ box.
+4. Click the `Status` button to enable this payment condition.
+5. In the __Process with provider__ field, select the provider that will be used to process the payments.
+6. If there is an anti-fraud set up in your store, you can activate it for this payment condition by checking the __Use anti-Fraud solutio__ box.
 7. Choose whether you want payments to be made in cash or installments.
 8. If you wish, you can also opt for a [special payment condition](/en/tutorial/special-conditions).
-9. Click __Save__.
+9. Click `Save`.
 
-After following the steps indicated above, __Apple Pay__ will appear at your store checkout as a payment option for your customers to use.
+After following the indicated steps, Apple Pay may take up to 10 minutes to appear at your store's checkout as a payment option.
 
 ### Related articles
-- [Setting up Rede acquirer with ERedeRest](/en/tutorial/setting-up-rede-acquirer-with-erederest)
-- [How to set up your Adyen gateway in VTEX platform](/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex)
+
 - [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay)
-- [Configuring payment special conditions](/en/tutorial/special-conditions)
-- [What is an e-wallet?](/en/faq/what-is-an-e-wallet)
+- [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456)
+- [What is an ewallet?](https://help.vtex.com/en/tutorial/what-is-an-e-wallet--4v5wcOe4A0SiaimWM2cU60)
diff --git a/docs/tutorials/en/setting-up-payments-with-appmax.md b/docs/tutorials/en/setting-up-payments-with-appmax.md
new file mode 100644
index 000000000..0e5017c8c
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-appmax.md
@@ -0,0 +1,33 @@
+---
+title: 'Setting up payments with Appmax'
+id: 6IIo8dyXKtdmXykBOhYmi0
+status: PUBLISHED
+createdAt: 2023-12-18T14:21:48.704Z
+updatedAt: 2024-01-23T18:26:05.083Z
+publishedAt: 2024-01-23T18:26:05.083Z
+firstPublishedAt: 2023-12-18T14:32:23.030Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-appmax
+locale: en
+legacySlug: setting-up-payments-with-appmax
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Appmax payment provider. With this provider, your store can make sales through credit cards, bank invoice and Pix (brazilian payment method).
+
+To configure Appmax, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Appmax__ in the search bar and click on the name of the provider.
+4. In __Click to authorize VTEX to make payments__, click on __Authorize__. At this moment, you will be redirected to the Appmax webpage, where you will have to access your account, and authorize the connection of VTEX in your Appmax account.
+5. After authorizing, you will automatically return to the VTEX Admin, and the __Application Key__, __Application Token__, __Application Id__ fields will already be filled in.
+6. Click on `Save`.
+
+To configure the payment methods to be processed by Appmax, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Appmax connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-argonpay.md b/docs/tutorials/en/setting-up-payments-with-argonpay.md
new file mode 100644
index 000000000..4c51c29eb
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-argonpay.md
@@ -0,0 +1,50 @@
+---
+title: 'Setting up payments with argonPAY'
+id: 6Pktml6MJpdc7dNvJ4zwzI
+status: PUBLISHED
+createdAt: 2023-12-18T14:51:00.261Z
+updatedAt: 2023-12-18T15:02:08.524Z
+publishedAt: 2023-12-18T15:02:08.524Z
+firstPublishedAt: 2023-12-18T15:02:08.524Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-argonpay
+locale: en
+legacySlug: setting-up-payments-with-argonpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the argonPAY payment provider. With this connector, your store can make sales through the argonPAY.
+
+To configure argonPAY provider, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Gateway affiliations__ tab, click on the `+` button.
+3. Click on the __ArgonPay__ connector.
+4. Fill in the __Application Key__ and __Application Token__ fields with the data provided by argonPAY.
+5. In the __Payment capture__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use Behavior Recommended By The Payment Processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic Capture Immediately After Payment Authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic Capture Immediately After Anti-fraud Analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic Capture Immediately After Payment Authorization".</li>
+   		<li><b>Scheduled: Schedules The Automatic Capture</b>: By selecting this option, the field <b>Scheduled time frame in hours for automatic capture</b> will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.</li>        
+   		<li><b>Deactivated: Not Automatically Captured</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+
+6. In __Enable payout split and send payment recipients?__, select whether split payments will be available for the marketplace and sellers.
+7. Click on the `Save` button.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Choose the payment condition __ArgonPay__.
+4. Fill the __Rule Name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on `Save`.
+
+After following the indicated steps, argonPAY connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-astropay.md b/docs/tutorials/en/setting-up-payments-with-astropay.md
index e59ea4d25..face2073a 100644
--- a/docs/tutorials/en/setting-up-payments-with-astropay.md
+++ b/docs/tutorials/en/setting-up-payments-with-astropay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Astropay'
 id: 1A5hrnp3wLTlkUkYLlielB
 status: PUBLISHED
 createdAt: 2022-08-15T18:20:38.640Z
-updatedAt: 2023-03-26T21:21:01.948Z
-publishedAt: 2023-03-26T21:21:01.948Z
+updatedAt: 2024-01-25T19:07:17.927Z
+publishedAt: 2024-01-25T19:07:17.927Z
 firstPublishedAt: 2022-08-15T18:39:51.774Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: setting-up-payments-with-astropay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Astropay payment provider. With this connector, your store can make sales through the Astropay.
+At VTEX, it is possible to integrate with the Astropay payment provider. With this integration, your store can make sales through the Astropay.
 
-To set up Astropay affiliation, follow the steps below:
+To set up Astropay, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __AstroPayOneTouch__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __AstroPayOneTouch__ in the search bar and click on the name of the provider.
 4. Click the __Install app__ button and follow the installation instructions.
 5. Fill in the __Application Key__, __Application Token__, __App Key - Astropay__ and __Api Secret - Astropay__ fields with data provided by Astropay.
-6. Click on `Save`.
+6. Click `Save`.
 
 ## Setting up Astropay payment condition 
 
@@ -32,6 +32,6 @@ To set up Astropay affiliation, follow the steps below:
 2. In the __Payment Conditions__ tab, click on the `+` button.
 3. Choose the payment condition __Astropay__.
 4. Activate the condition in the __Status__ field.
-5. Click on `Save`.
+5. Click `Save`.
 
-After following the indicated steps, Astropay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Astropay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-bamboo.md b/docs/tutorials/en/setting-up-payments-with-bamboo.md
index 7a5c74cdd..2c38e3b82 100644
--- a/docs/tutorials/en/setting-up-payments-with-bamboo.md
+++ b/docs/tutorials/en/setting-up-payments-with-bamboo.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Bamboo'
 id: 33TDZBp1wmgzJdiZtvu1xY
 status: PUBLISHED
 createdAt: 2022-08-12T20:06:37.117Z
-updatedAt: 2022-08-12T20:13:31.863Z
-publishedAt: 2022-08-12T20:13:31.863Z
+updatedAt: 2024-01-25T19:18:30.701Z
+publishedAt: 2024-01-25T19:18:30.701Z
 firstPublishedAt: 2022-08-12T20:13:31.863Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: setting-up-payments-with-bamboo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Bamboo payment provider. With this connector, your store can make sales through a credit, debit, private labels and cobranded cards, and bank invoices.
+At VTEX, it is possible to integrate with the Bamboo payment provider. With this provider, your store can make sales through a credit, debit, private labels and cobranded cards, and bank invoices.
 
-To set up your Bamboo affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
+To set up your Bamboo, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
 
-After following the indicated steps, Bamboo connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Bamboo may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-bancolombia-bnpl.md b/docs/tutorials/en/setting-up-payments-with-bancolombia-bnpl.md
index 0b0106b99..8ec0383b9 100644
--- a/docs/tutorials/en/setting-up-payments-with-bancolombia-bnpl.md
+++ b/docs/tutorials/en/setting-up-payments-with-bancolombia-bnpl.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Bancolombia BNPL'
 id: 16iFxjwsOPwmBwmjhb17WN
 status: PUBLISHED
 createdAt: 2023-03-30T16:25:46.370Z
-updatedAt: 2023-03-30T17:24:01.279Z
-publishedAt: 2023-03-30T17:24:01.279Z
+updatedAt: 2024-01-24T21:15:43.651Z
+publishedAt: 2024-01-24T21:15:43.651Z
 firstPublishedAt: 2023-03-30T17:24:01.279Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-bancolombia-bnpl
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Bancolombia BNPL payment provider. With this connector, your store can make sales through Bancolombia BNPL (Buy Now Pay Later).
+At VTEX, it is possible to integrate with the Bancolombia BNPL payment provider. With this provider, your store can make sales through Bancolombia BNPL (Buy Now Pay Later).
 
-To configure Bancolombia BNPL affiliation, follow the steps below:
+To configure Bancolombia BNPL, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __BancolombiaBNPL__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __BancolombiaBNPL__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account Bancolombia.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
@@ -36,4 +36,4 @@ To configure Bancolombia BNPL affiliation, follow the steps below:
 6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
 7. Click on `Save`.
 
-After following the indicated steps, Bancolombia BNPL connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Bancolombia BNPL may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-banqi.md b/docs/tutorials/en/setting-up-payments-with-banqi.md
index 360c43a88..358a956ad 100644
--- a/docs/tutorials/en/setting-up-payments-with-banqi.md
+++ b/docs/tutorials/en/setting-up-payments-with-banqi.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with banQi'
 id: 41rk9E7JUmCl683MJ9p52P
 status: PUBLISHED
 createdAt: 2023-03-30T12:31:49.459Z
-updatedAt: 2023-03-30T19:51:34.281Z
-publishedAt: 2023-03-30T19:51:34.281Z
+updatedAt: 2024-01-23T18:25:15.982Z
+publishedAt: 2024-01-23T18:25:15.982Z
 firstPublishedAt: 2023-03-30T13:04:03.008Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-banqi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the banQi payment provider. With this connector, your store can make sales through payment book banQi.
+At VTEX, it is possible to integrate with the banQi payment provider. With this provider, your store can make sales through payment book banQi.
 
-To configure banQi affiliation, follow the steps below:
+To configure banQi, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __banQi__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __banQi__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account banQi.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-bitfy.md b/docs/tutorials/en/setting-up-payments-with-bitfy.md
index 6327e3589..405bf612c 100644
--- a/docs/tutorials/en/setting-up-payments-with-bitfy.md
+++ b/docs/tutorials/en/setting-up-payments-with-bitfy.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Bitfy'
 id: 2PSTfW4PsMh19K9y3DkQec
 status: PUBLISHED
 createdAt: 2022-08-15T17:30:29.886Z
-updatedAt: 2023-03-24T15:05:15.559Z
-publishedAt: 2023-03-24T15:05:15.559Z
+updatedAt: 2024-01-23T18:24:11.153Z
+publishedAt: 2024-01-23T18:24:11.153Z
 firstPublishedAt: 2022-08-15T17:41:45.501Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-bitfy
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Bitfy payment provider. With this connector, your store can make sales through the Bitfy.
+At VTEX, it is possible to integrate with the Bitfy payment provider. With this provider, your store can make sales through the Bitfy.
 
-To set up Bitfy affiliation, follow the steps below:
+To configure Bitfy, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __BitfyBr__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __BitfyBr__ in the search bar and click on the name of the provider.
 4. Click the __Install app__ button and follow the installation instructions.
 5. Fill in the __Application Key__ and __Application Token__ fields with data provided by Bitfy.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-bluepay.md b/docs/tutorials/en/setting-up-payments-with-bluepay.md
index 99f75058f..1edb7b00d 100644
--- a/docs/tutorials/en/setting-up-payments-with-bluepay.md
+++ b/docs/tutorials/en/setting-up-payments-with-bluepay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with BluePay'
 id: 26gzpfmEiwgpE8yhkaFS16
 status: PUBLISHED
 createdAt: 2023-04-03T14:55:51.576Z
-updatedAt: 2023-04-03T15:04:37.336Z
-publishedAt: 2023-04-03T15:04:37.336Z
+updatedAt: 2024-07-24T13:29:26.700Z
+publishedAt: 2024-07-24T13:29:26.700Z
 firstPublishedAt: 2023-04-03T15:04:37.336Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-bluepay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the BluePay payment provider. With this connector, your store can make sales through PIX.
+At VTEX, it is possible to integrate with the BluePay payment provider. With this provider, your store can make sales through PIX.
 
-To configure BluePay affiliation, follow the steps below:
+To configure BluePay, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __BluePay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __BluePay__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account BluePay.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-boletoflex.md b/docs/tutorials/en/setting-up-payments-with-boletoflex.md
index 6caf53698..d7fb8dd0a 100644
--- a/docs/tutorials/en/setting-up-payments-with-boletoflex.md
+++ b/docs/tutorials/en/setting-up-payments-with-boletoflex.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with BoletoFlex'
 id: 3ikLbJGXMI6bkAm6YiglOx
 status: PUBLISHED
 createdAt: 2022-01-10T17:36:39.512Z
-updatedAt: 2023-03-22T19:10:38.069Z
-publishedAt: 2023-03-22T19:10:38.069Z
+updatedAt: 2024-01-23T15:50:34.329Z
+publishedAt: 2024-01-23T15:50:34.329Z
 firstPublishedAt: 2022-01-10T20:19:23.317Z
 contentType: tutorial
 productTeam: Financial
@@ -18,9 +18,10 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 BoletoFlex is a payment method where users can pay their purchases in installments using the boleto, with pre-determined interest rates and without the need to use a credit card.
 
 ## Setting up BoletoFlex gateway affiliation 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __+__ button.
-3. Click on the __BoletoFlex__ connector.
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __BoletoFlex__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by BoletoFlex.
 5. Click on __Save__.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-bom-pra-credito.md b/docs/tutorials/en/setting-up-payments-with-bom-pra-credito.md
index 8a4ea1f64..96442e64c 100644
--- a/docs/tutorials/en/setting-up-payments-with-bom-pra-credito.md
+++ b/docs/tutorials/en/setting-up-payments-with-bom-pra-credito.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Bom Pra Credito'
 id: 2arjSmF9ksov6IXTEMaGkl
 status: PUBLISHED
 createdAt: 2022-08-10T19:47:21.251Z
-updatedAt: 2023-03-26T21:24:13.881Z
-publishedAt: 2023-03-26T21:24:13.881Z
+updatedAt: 2024-01-23T18:19:59.534Z
+publishedAt: 2024-01-23T18:19:59.534Z
 firstPublishedAt: 2022-08-10T19:52:22.782Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-braintree.md b/docs/tutorials/en/setting-up-payments-with-braintree.md
new file mode 100644
index 000000000..bd652161a
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-braintree.md
@@ -0,0 +1,49 @@
+---
+title: 'Setting up payments with Braintree'
+id: 3Is3N2MmTldXPa2FtiV8xy
+status: PUBLISHED
+createdAt: 2022-08-11T12:01:04.231Z
+updatedAt: 2024-03-18T11:55:35.217Z
+publishedAt: 2024-03-18T11:55:35.217Z
+firstPublishedAt: 2022-08-11T12:27:01.656Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-braintree
+locale: en
+legacySlug: setting-up-payments-with-braintree
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the payment provider Braintree.
+Through this provider, your store can make sales throughc credit and debit cards.
+
+To configure Braintree-DCC, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Braintree-DCC__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the registration fields __App key__ and __App token__ with the data provided by Braintree.
+5. If you wish to modify the identification name to be displayed for the Braintree provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. In __Provider Fields__, select or complete the fields below with your Braintree account information:
+   - __Change Order Single Charge__
+   - __PayPal Secret (opcional)__
+   - __PayPal Client ID (opcional)__
+   - __PayPal Merchant ID (opcional)__
+   - __Merchant Account Id (opcional)__
+   - __Merchant Id (Braintree)__
+9. Click `Save`.
+
+To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
+
+After following the indicated steps, Braintree-DCC may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-braspagv2.md b/docs/tutorials/en/setting-up-payments-with-braspagv2.md
index b01cc1e4b..44b7792aa 100644
--- a/docs/tutorials/en/setting-up-payments-with-braspagv2.md
+++ b/docs/tutorials/en/setting-up-payments-with-braspagv2.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with BraspagV2'
 id: 6gaw7zu9wlItgjfDVndRPn
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-01-20T19:41:22.154Z
-updatedAt: 2023-03-22T19:03:11.096Z
-publishedAt: 2023-03-22T19:03:11.096Z
+updatedAt: 2023-09-19T14:27:03.358Z
+publishedAt: 
 firstPublishedAt: 2022-01-21T16:38:10.049Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-brinks-cash-ecommerce.md b/docs/tutorials/en/setting-up-payments-with-brinks-cash-ecommerce.md
index 252c3ec4e..5e398751c 100644
--- a/docs/tutorials/en/setting-up-payments-with-brinks-cash-ecommerce.md
+++ b/docs/tutorials/en/setting-up-payments-with-brinks-cash-ecommerce.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Brinks Cash Ecommerce'
 id: 5Zoex6NXtyzUFOCctdGjlZ
 status: PUBLISHED
 createdAt: 2022-08-15T17:49:34.660Z
-updatedAt: 2023-03-26T21:22:32.556Z
-publishedAt: 2023-03-26T21:22:32.556Z
+updatedAt: 2024-01-24T21:18:37.297Z
+publishedAt: 2024-01-24T21:18:37.297Z
 firstPublishedAt: 2022-08-15T18:04:15.733Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-brinks-cash-ecommerce
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Brinks Cash Ecommerce payment provider. With this connector, your store can make sales through Recaudo Efectivo (cash collection) in Colombia.
+At VTEX, it is possible to integrate with the Brinks Cash Ecommerce payment provider. With this provider, your store can make sales through Recaudo Efectivo (cash collection) in Colombia.
 
-To set up Brinks Cash Ecommerce affiliation, follow the steps below:
+To set up Brinks Cash Ecommerce, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Brinks Cash Ecommerce__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Brinks Cash Ecommerce__ in the search bar and click on the name of the provider.
 4. Click the __Install app__ button and follow the installation instructions.
 5. Fill in the __Application Key__ and __Application Token__ fields with data provided by Brinks Cash Ecommerce.
 6. Click on `Save`.
@@ -34,4 +34,4 @@ To set up Brinks Cash Ecommerce affiliation, follow the steps below:
 4. Activate the condition in the __Status__ field.
 5. Click on `Save`.
 
-After following the indicated steps, Brinks Cash Ecommerce connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Brinks Cash Ecommerce may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md b/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md
new file mode 100644
index 000000000..acf3bef8a
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md
@@ -0,0 +1,66 @@
+---
+title: 'Setting up payments with CieloEcommerce'
+id: 6zuELBqEo0QzApbU4l7L4
+status: PUBLISHED
+createdAt: 2023-09-18T14:07:22.540Z
+updatedAt: 2024-03-27T17:13:40.793Z
+publishedAt: 2024-03-27T17:13:40.793Z
+firstPublishedAt: 2023-09-18T15:29:57.321Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-cieloecommerce
+locale: en
+legacySlug: setting-up-payments-with-cieloecommerce
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the CieloEcommerce. With this integration, your store can make sales through credit, debit, private labels and cobranded cards, bank invoices, PIX, among others. 
+
+To configure CieloEcommerce, follow the steps below:
+
+<blockquote><ui>1. In the VTEX Admin, go to <b>Store Settings > Payment > Providers</b>, or type <b>Providers</b> in the search bar at the top of the page.</ui>
+
+<blockquote><ui>2. On the providers screen, click the <b>New Provider</b> button.</ui>
+
+<blockquote><ui>3. Type the name <b>CieloEcommerce</b> in the search bar and click on the name of the provider.</ui>
+
+<blockquote><ui>4. In <b>Provider Authorization</b>, fill in the <b>App key</b> and <b>App token</b> fields with <b>MerchantID</b> and <b>MerchantKey</b> provided by CieloEcommerce.</ui>
+
+<blockquote><ui>5. If you wish to modify the identification name to be displayed for the CieloEcommerce provider on the VTEX Admin screen, enter the information in the <b>Name</b> field in <b>Basic Information</b>.</ui>
+
+<blockquote><ui>6. In <b>Payment Control</b>, select whether you want to activate the provider in a test environment by clicking <b>Enable test mode</b>.</ui>
+
+<blockquote><ui>7. If you want to use <a href="https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx">Payment split</a> in your store, select the option <b>Enable payout split and send payment recipients</b> and indicate the <b>Accountable for payment processing charges</b> and <b>Accountable for chargebacks</b> (marketplace, sellers or marketplaces and sellers).</ui>
+
+<blockquote><ui>8. In <b>Integration</b>, select whether the connector will be used as <b>Adquirencia</b> or <b>Gateway</b>.
+
+<blockquote><ui>9. In <b>Provider</b>, select the acquirer to be used with the CieloEcommerce connector.</ui>
+
+<blockquote><ui>10. In <b>IsSplit</b>, choose whether the split option will be available.</ui>
+
+<blockquote><ui>11. In <b>UseMpi</b>, choose whether transactions will be authenticated (3DS 2.0). This field is mandatory for the debit payment type. If you select "True", go to Step 12. If you select "False", go to Step 13.</ui>
+
+<blockquote><ui>12. Fill in the <b>MpiClientId</b>, <b>MpiClientSecret</b>, <b>MpiMerchantName</b>, <b>MpiMCC</b>, and <b>MpiEstablishmentCode</b> fields with you Mpi access data.</ui>
+
+<blockquote><ui>13. In <b>SoftDescriptor</b>, indicate the information to be displayed to identify the transaction carried out in your store.</ui>
+
+<blockquote><ui>14. In <b>AntifraudProvider</b>, select the antifraud provider you want to use with CieloEcommerce.</ui>
+
+<blockquote><div class="alert alert-warning">
+  Check with Cielo whether the anti-fraud options in CieloEcommerce are already available for use. If still under development, both fields described in step 15 must be left blank. For more information about using anti-fraud options in your store, visit <a href="https://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud">Configuring the anti-fraud</a>.
+  </div></blockquote>
+<br>  
+<blockquote><ui>15. In <b>Antifraud</b> and <b>AntifraudSequenceCriteria</b>, select the options according to information from CieloEcommerce antifraud.</ui>
+
+<blockquote><ui>16. In <b>Captura</b>, select the period in which payment capture should be requested. Standard time will be held four days after authorization.</ui>
+
+<blockquote><ui>17. Select the <b>UseVerifyCard</b>, <b>AcceptInternationalCard_</b>, <b>AcceptPrePaidCard</b>, <b>SaveCard</b> and <b>CancelRefundType</b> fields according to your settings in CieloEcommerce.</ui>
+
+<blockquote><ui>18. Click <b>Save</b>.</ui>
+
+To configure the payment methods to be processed by CieloEcommerce, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, CieloEcommerce connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-cielov4.md b/docs/tutorials/en/setting-up-payments-with-cielov4.md
index 04507d910..a9acf4035 100644
--- a/docs/tutorials/en/setting-up-payments-with-cielov4.md
+++ b/docs/tutorials/en/setting-up-payments-with-cielov4.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with CieloV4'
 id: 7M2CqJxprwpDtbgLZHBoiI
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-07-20T14:25:28.188Z
-updatedAt: 2023-03-26T21:25:12.482Z
-publishedAt: 2023-03-26T21:25:12.482Z
+updatedAt: 2023-09-19T14:27:43.425Z
+publishedAt: 
 firstPublishedAt: 2022-07-20T17:07:25.186Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-conekta.md b/docs/tutorials/en/setting-up-payments-with-conekta.md
index b16a6a06f..bacbd0635 100644
--- a/docs/tutorials/en/setting-up-payments-with-conekta.md
+++ b/docs/tutorials/en/setting-up-payments-with-conekta.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Conekta'
 id: 7kiAD3SlnABF75xLSL3eSA
 status: PUBLISHED
 createdAt: 2022-08-11T12:41:42.110Z
-updatedAt: 2023-03-26T21:16:15.989Z
-publishedAt: 2023-03-26T21:16:15.989Z
+updatedAt: 2024-01-25T17:54:14.697Z
+publishedAt: 2024-01-25T17:54:14.697Z
 firstPublishedAt: 2022-08-11T12:54:43.579Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-conekta
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Conekta payment provider. With this connector, your store can make sales through a credit, debit cards, OXXO and promissories.
+At VTEX, it is possible to integrate with the Conekta payment provider. With this provider, your store can make sales through a credit, debit cards, OXXO and Notes Payable.
 
-To configure Conekta affiliation, follow the steps below:
+To configure Conekta, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Conekta__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Conekta__ in the search bar and click on the name of the provider.
 4. Fill in the fields below your Conekta account information:
    - __Application Key__
    - __Application Token__
@@ -31,8 +31,10 @@ To configure Conekta affiliation, follow the steps below:
    - __Tiempo de expiración para OXXOPay__
    - __Metadata 4__
    - __Metadata 5__ 
-5. Click on `Save`.
+5. Click `Save`.
 
-To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/conditiones-especiales--tutorials_456?&utm_source=autocomplete).
+To configure the payment methods to be processed by Conekta, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-After following the indicated steps, Conekta connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Conekta may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-crecoscorp.md b/docs/tutorials/en/setting-up-payments-with-crecoscorp.md
index 6fdd170f8..0f9a657a6 100644
--- a/docs/tutorials/en/setting-up-payments-with-crecoscorp.md
+++ b/docs/tutorials/en/setting-up-payments-with-crecoscorp.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with CrecosCorp'
 id: 2NNAhG7ugxXhyk7U45hIeZ
 status: PUBLISHED
 createdAt: 2022-08-15T18:54:07.978Z
-updatedAt: 2022-08-15T18:59:46.828Z
-publishedAt: 2022-08-15T18:59:46.828Z
+updatedAt: 2024-01-25T17:37:02.016Z
+publishedAt: 2024-01-25T17:37:02.016Z
 firstPublishedAt: 2022-08-15T18:59:46.828Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: setting-up-payments-with-crecoscorp
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the CrecosCorp payment provider. With this connector, your store can make sales through private labels.
+At VTEX, it is possible to integrate with the CrecosCorp payment provider. With this provider, your store can make sales through private labels.
 
-To set up your CrecosCorp affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
+To set up your CrecosCorp, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 To set up payment by private labels cards, access [Setting up Private Label payments](https://help.vtex.com/en/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4#).
 
-After following the indicated steps, CrecosCorp connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, CrecosCorp may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-credimarcas.md b/docs/tutorials/en/setting-up-payments-with-credimarcas.md
new file mode 100644
index 000000000..e4c08dbfb
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-credimarcas.md
@@ -0,0 +1,60 @@
+---
+title: 'Setting up payments with Credimarcas'
+id: 78855lTT6A1vX2wFURmxV
+status: PUBLISHED
+createdAt: 2023-12-18T13:12:50.542Z
+updatedAt: 2023-12-18T14:09:15.538Z
+publishedAt: 2023-12-18T14:09:15.538Z
+firstPublishedAt: 2023-12-18T14:09:15.538Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-credimarcas
+locale: en
+legacySlug: setting-up-payments-with-credimarcas
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Credimarcas payment provider. With this connector, your store can make sales through Notes Payable and Private Labels cards.
+
+To configure Credimarcas provider, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Gateway affiliations__ tab, click on the `+` button.
+3. Click on the __credimarcas__ connector.
+4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Credimarcas.
+5. In the __Payment settlement__ field, select one of the available options:
+
+    - __Use Behavior Recommended By The Payment Processor__: capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization.
+    - __Immediate: Automatic Settlement After Payment Authorization__: capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.
+    - __Immediate: Automatic Settlement After Anti-Fraud Analysis__:  Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in __Immediate: Automatic Settlement After Payment Authorization__.
+    - __Scheduled: Schedules The Automatic Settlement__: By selecting this option, the field __Scheduled time frame in hours for automatic settlement__ will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.
+    - __Deactivated: Not Automatically Captured__: capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.
+
+<ui>  6. In <b>Type Payment</b>, select whether the payment will be made via "Payment App" or "Redirect".</ui>
+
+<ui>  7. If an alert message appears indicating the need to install the app, click on the <b>Install app</b> button and follow the installation instructions.</ui>
+
+<ui>  8. Click on <b>Save.</b></ui>
+
+## Setting up Notes Payable
+
+<div class="alert alert-warning">
+  <p>If you have not yet configured the Notes Payable as a payment method in other connectors in your store, go to <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable">Setting up payments with Notes Payable</a>.</p>
+</div>
+
+To use Credimarcas with notes payable, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. On __Custom Payment__, click the button corresponding to the name used for the Notes Payable payment method (previously configured).
+4. Activate the condition in the __Status__ field.
+5. On __Process with affiliation__, select __confepartnerco-credimarcas-v0__.
+6. If you wish, you can also configure [payment special conditionso](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+7. Click on `Save`.
+
+## Setting up Private label
+
+To use Credimarcas with private labels cards, access [Setting up Private Label payments](https://help.vtex.com/en/tutorial/setting-up-private-label-payments--428FgVdSGQUeAOoogkaIw4).
+
+After following the indicated steps, Credimarcas connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-credit-key.md b/docs/tutorials/en/setting-up-payments-with-credit-key.md
index e1e45d41b..333fa2e07 100644
--- a/docs/tutorials/en/setting-up-payments-with-credit-key.md
+++ b/docs/tutorials/en/setting-up-payments-with-credit-key.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Credit Key'
 id: 4TtmhhkcXQYnkaCPUa9adB
 status: PUBLISHED
 createdAt: 2023-04-20T14:33:42.988Z
-updatedAt: 2023-04-20T14:51:31.849Z
-publishedAt: 2023-04-20T14:51:31.849Z
+updatedAt: 2024-01-25T17:48:48.188Z
+publishedAt: 2024-01-25T17:48:48.188Z
 firstPublishedAt: 2023-04-20T14:51:31.849Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: setting-up-payments-with-credit-key
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Credit Key payment provider. With this connector, your store can make sales through Credit Key.
+At VTEX, it is possible to integrate with the Credit Key payment provider. With this provider, your store can make sales through Credit Key.
 
-To configure Credit Key affiliation, follow the steps below:
+To configure Credit Key, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __CreditKey__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __CreditKey__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Credit Key.
 5. If an alert message appears indicating the need to install the app, click on the __Install app__ button and follow the installation instructions.
-6. Click on `Save`.
+6. Click `Save`.
 
 ## Setting up payment condition 
 
@@ -34,6 +34,6 @@ To configure Credit Key affiliation, follow the steps below:
 4. Activate the condition in the __Status__ field.
 5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
 6. If you wish, you can also configure [payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
-7. Click on `Save`.
+7. Click `Save`.
 
-After following the indicated steps, Credit Key connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Credit Key may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-culqi.md b/docs/tutorials/en/setting-up-payments-with-culqi.md
new file mode 100644
index 000000000..590dd5fa8
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-culqi.md
@@ -0,0 +1,58 @@
+---
+title: 'Setting up payments with Culqi'
+id: 6LUOpYBpg48XSL8X0Le6e3
+status: PUBLISHED
+createdAt: 2023-11-16T13:31:38.132Z
+updatedAt: 2024-01-25T19:01:02.616Z
+publishedAt: 2024-01-25T19:01:02.616Z
+firstPublishedAt: 2023-11-16T14:54:41.647Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-culqi
+locale: en
+legacySlug: setting-up-payments-with-culqi
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Culqi payment provider. With this provider, your store can make sales through the Culqi.
+
+To configure Culqi, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Culqi__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__ and __Public Key__ fields with the data provided by Culqi.
+5. In the __Payment settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use Behavior Recommended By The Payment Processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic Capture Immediately After Payment Authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic Capture Immediately After Anti-fraud Analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic Capture Immediately After Payment Authorization".</li>
+   		<li><b>Scheduled: Schedules The Automatic Capture</b>: By selecting this option, the field <b>Scheduled time frame in hours for automatic capture</b> will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.</li>        
+   		<li><b>Deactivated: Not Automatically Captured</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+6. In __Aceptar tarjetas de crédito__, select whether you want to accept credit cards as a payment method.
+7. In __Aceptar YAPE__, select whether you want to accept [YAPE](https://www.yape.com.pe/) as a payment method.
+8. In __Aceptar billeteras móviles__, select whether you want to accept digital wallets as a payment method.
+9. In __Aceptar banca móvil o internet__, select whether you want to accept payments via mobile devices and internet banking.
+10. In __Aceptar agentes y bodegas__, select whether you want to accept payments via agents and bodegas (warehouses).
+11. In __Aceptar cuotéalo BCP__, select whether you want to accept payments in installments via [cuotéalo BCP](https://www.viabcp.com/cuotealo).
+12. In __Tiempo de expiración de pago__, select the period (in days) for payments to expire.
+13. In the __URL de logo__, __Tema elegido__, __RSA Id__, __Llave pública RSA__, __Usuario Webhook__ and __Password Webhook__ fields, enter the information provided by Culqi.
+14. In __Ativar divisão e enviar recebedores?__, select whether split payments will be available for the marketplace and sellers.
+15. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Choose the payment condition __Culqi__.
+4. Fill the __Rule Name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+7. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Click `Save`.
+
+After following the indicated steps, Culqi may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-dapp.md b/docs/tutorials/en/setting-up-payments-with-dapp.md
new file mode 100644
index 000000000..d052f9d36
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-dapp.md
@@ -0,0 +1,39 @@
+---
+title: 'Setting up payments with Dapp'
+id: 1p0FGViQcgCinPyi0GNXYM
+status: PUBLISHED
+createdAt: 2023-09-08T17:59:03.453Z
+updatedAt: 2024-01-25T18:09:29.307Z
+publishedAt: 2024-01-25T18:09:29.307Z
+firstPublishedAt: 2023-09-08T18:08:01.746Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-dapp
+locale: en
+legacySlug: setting-up-payments-with-dapp
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Dapp payment provider. With this provider, your store can make sales through Dapp.
+
+To configure Dapp, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Dapp__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__, __Clave 1 - Dapp__ and __Clave 2 - Dapp__ fields with data provided by your account Dapp.
+5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+6. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __Dapp__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, Dapp may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-deuna.md b/docs/tutorials/en/setting-up-payments-with-deuna.md
new file mode 100644
index 000000000..d7f190750
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-deuna.md
@@ -0,0 +1,48 @@
+---
+title: 'Setting up payments with Deuna'
+id: 5Y4BfCdbQWraZAyoSm0Zzr
+status: PUBLISHED
+createdAt: 2023-04-06T18:37:58.919Z
+updatedAt: 2024-01-23T18:11:08.945Z
+publishedAt: 2024-01-23T18:11:08.945Z
+firstPublishedAt: 2023-04-06T18:42:52.173Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-deuna
+locale: en
+legacySlug: setting-up-payments-with-deuna
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Deuna payment provider. With this provider, your store can make sales through Deuna.
+
+To configure Deuna, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __DEUNA__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Deuna.
+5. In the __Payment settlement__ field, select one of the available options:
+
+    - __Use Behavior Recommended By The Payment Processor__: capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization.
+    - __Immediate: Automatic Settlement After Payment Authorization__: capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.
+    - __Immediate: Automatic Settlement After Anti-Fraud Analysis__:  Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in __Immediate: Automatic Settlement After Payment Authorization__.
+    - __Scheduled: Schedules The Automatic Settlement__: By selecting this option, the field __Scheduled time frame in hours for automatic settlement__ will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.
+    - __Deactivated: Not Automatically Captured__: capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.
+
+<ui>  6. If an alert message appears indicating the need to install the app, click on the <b>Install app</b> button and follow the installation instructions.</ui>
+
+<ui>  7. Click on <b>Save.</b></ui>
+
+## Setting up payment condition 
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click the __DEUNA__ payment method.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you wish, you can also configure [payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+7. Click on `Save`.
+
+After following the indicated steps, Deuna connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-digital-river-v2.md b/docs/tutorials/en/setting-up-payments-with-digital-river-v2.md
index 709006ae6..21ec06f46 100644
--- a/docs/tutorials/en/setting-up-payments-with-digital-river-v2.md
+++ b/docs/tutorials/en/setting-up-payments-with-digital-river-v2.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Digital River V2'
 id: 5dlXHutd9Ik6vtN3WP7GRP
 status: PUBLISHED
 createdAt: 2022-02-17T12:11:27.726Z
-updatedAt: 2023-03-26T21:59:25.157Z
-publishedAt: 2023-03-26T21:59:25.157Z
+updatedAt: 2024-01-24T17:19:19.577Z
+publishedAt: 2024-01-24T17:19:19.577Z
 firstPublishedAt: 2022-02-17T13:44:17.095Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: setting-up-payments-with-digital-river-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Digital River V2 payment provider.  With this connector, your store can make sales through several [payment methods](https://www.digitalriver.com/payment-method-guide/).
+At VTEX, it is possible to integrate with the Digital River V2 payment provider.  With this provider, your store can make sales through several [payment methods](https://www.digitalriver.com/payment-method-guide/).
 
-To configure Digital River V2 affiliation, follow the steps below:
+To configure Digital River V2, follow the steps below:
 
-<ui>1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.</ui>
+<ui>1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Providers**, or type **Providers** in the search bar at the top of the page.</ui>
 
-<ui>2. In the __Gateway affiliations__ tab, click on the __+__ button.</ui>
+<ui>2. On the providers screen, click the `New Provider` button.</ui>
 
-<ui>3. Click on the __DigitalRiverV2__ connector.</ui>
+<ui>3. Type the name __DigitalRiverV2__ in the search bar and click on the name of the provider.</ui>
 
 <ui>4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Digital River V2.</ui>
 
diff --git a/docs/tutorials/en/setting-up-payments-with-dlocal-payments.md b/docs/tutorials/en/setting-up-payments-with-dlocal-payments.md
index 99f703ce3..261679e45 100644
--- a/docs/tutorials/en/setting-up-payments-with-dlocal-payments.md
+++ b/docs/tutorials/en/setting-up-payments-with-dlocal-payments.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with DLocal Payments'
 id: 50DpZAd6td8oJaAIzHfQB5
 status: PUBLISHED
 createdAt: 2023-04-03T13:40:15.432Z
-updatedAt: 2023-04-03T14:03:12.910Z
-publishedAt: 2023-04-03T14:03:12.910Z
+updatedAt: 2024-01-23T18:09:56.316Z
+publishedAt: 2024-01-23T18:09:56.316Z
 firstPublishedAt: 2023-04-03T14:03:12.910Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-dlocal-payments
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the DLocal Payments payment provider. With this connector, your store can make sales through credit, debit cards and bank invoice.
+At VTEX, it is possible to integrate with the DLocal Payments payment provider. With this provider, your store can make sales through credit, debit cards and bank invoice.
 
-To configure DLocal Payments affiliation, follow the steps below:
+To configure DLocal Payments, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __DLocalPayments__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __DLocalPayments__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by DLocal Payments.
 5. In the __Payment settlement__ field, select one of the available options:
 
diff --git a/docs/tutorials/en/setting-up-payments-with-dock.md b/docs/tutorials/en/setting-up-payments-with-dock.md
index ce7a52f42..8d349f31d 100644
--- a/docs/tutorials/en/setting-up-payments-with-dock.md
+++ b/docs/tutorials/en/setting-up-payments-with-dock.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Dock'
 id: 3Y0tLnXjBcG9qxHwAHGbHn
 status: PUBLISHED
 createdAt: 2022-07-19T19:58:56.608Z
-updatedAt: 2023-03-26T21:25:49.936Z
-publishedAt: 2023-03-26T21:25:49.936Z
+updatedAt: 2024-01-23T18:08:45.414Z
+publishedAt: 2024-01-23T18:08:45.414Z
 firstPublishedAt: 2022-07-19T20:12:07.212Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-e-sitef.md b/docs/tutorials/en/setting-up-payments-with-e-sitef.md
new file mode 100644
index 000000000..49c732a27
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-e-sitef.md
@@ -0,0 +1,48 @@
+---
+title: 'Setting up payments with e-Sitef'
+id: 6UEi0QAlU6BXz5RgWj34Ac
+status: PUBLISHED
+createdAt: 2021-12-06T14:51:20.250Z
+updatedAt: 2024-03-14T16:59:21.753Z
+publishedAt: 2024-03-14T16:59:21.753Z
+firstPublishedAt: 2021-12-06T17:37:55.667Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-e-sitef
+locale: en
+legacySlug: setting-up-payments-with-e-sitef
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the e-Sitef payment provider. With this provider, your store can make sales through credit, debit, private labels and cobranded cards, and PIX.
+
+To configure e-Sitef, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __ESITEF__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by e-Sitef.
+5. If you wish to modify the identification name to be displayed for the e-Sitef provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. In __Captura antecipada (em horas)__, choose how long you want the capture to take place (after the transaction is approved). You can also disable the function.
+9. In __Alterar tempo máximo para captura automática (em dias)__, fill in the maximum period of days in which the auto-capture should take place.
+10. In __Soft Descriptor__, you can enter a custom string (characters) which will be printed on the customer's invoice.
+11. In __Habilitar Pré-autorização__, select if you want orders made with a credit card to have the reserved amount (capture pre-authorized after transaction approval).
+12. In the __Captura antecipada após anti-fraude (em horas)__ field, choose how long you want the capture to take place (after anti-fraud analysis). You can also disable the function.
+13. Click `Save`.
+
+To configure the payment methods to be processed by e-Sitef, access [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, e-Sitef may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-easypay-marketplace.md b/docs/tutorials/en/setting-up-payments-with-easypay-marketplace.md
new file mode 100644
index 000000000..2663ce71c
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-easypay-marketplace.md
@@ -0,0 +1,18 @@
+---
+title: 'Setting up payments with easypay marketplace'
+id: 7EbImm3pJ8xCVRNxF06chN
+status: DRAFT
+createdAt: 2023-09-18T19:52:45.357Z
+updatedAt: 2023-09-19T12:04:40.833Z
+publishedAt: 
+firstPublishedAt: 2023-09-19T00:11:57.369Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-easypay-marketplace
+locale: en
+legacySlug: setting-up-payments-with-easypay-marketplace
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Content under translation.
diff --git a/docs/tutorials/en/setting-up-payments-with-easypay-seller.md b/docs/tutorials/en/setting-up-payments-with-easypay-seller.md
new file mode 100644
index 000000000..70793f19d
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-easypay-seller.md
@@ -0,0 +1,51 @@
+---
+title: 'Setting up payments with easypay seller'
+id: 5mYMCM1tiRiZO6PozuUncE
+status: PUBLISHED
+createdAt: 2023-09-19T00:16:47.408Z
+updatedAt: 2023-09-28T11:36:30.237Z
+publishedAt: 2023-09-28T11:36:30.237Z
+firstPublishedAt: 2023-09-19T00:26:38.480Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-easypay-seller
+locale: en
+legacySlug: setting-up-payments-with-seller
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+On VTEX, you, as a seller, can add your products to a marketplace integrated with the easypay payment provider. This connector enables your store to sell using easypay, MBWay, and MultiBanco.
+
+TYo use easypay affiliation in your marketplace, you need to:
+
+- [Install the easypay Seller Account app](#installing-the-easypay-seller-account-app)
+- [Configure the easypay Seller Account app](#configuring-the-easypay-seller-account-app)
+
+<div class="alert alert-warning" role="alert">If you want to configure easypay for a non-seller context, read <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay--3xJQqjMIn0ARDI1HcwK88J">Setting up payments with easypay</a> or <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Setting up payments with easypay marketplace</a>.</div>
+
+## Installing the easypay Seller Account app
+
+To install the easypay Seller Account app, follow the steps below:
+
+1. In the [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), run the command `vtex login accountname` to log in to your account.
+2. Install the easypay app using the `vtex install easypaypartnerpt.easypay-seller` command. 
+
+## Configuring the easypay Seller Account app
+
+After installing the easypay Seller Account app, you need to configure it. To access the configuration screen, follow the steps below:
+
+<blockquote><ui>1. In the VTEX Admin, go to <b>Extensions Hub > App Management</b>, or type <b>App Management</b> in the search bar at the top of the page.</ui>
+
+<blockquote><ui>2. Find the <b>Easypay Seller Account</b> app and click <b>Settings</b>.</ui>
+
+<blockquote><ui>3. In the <b>Easypay Seller Account</b> screen, complete the following fields:</ui>
+
+<blockquote><ui>- <b>VTEX Marketplace Account</b>: URL of the VTEX account you are associated with. E.g. https://{your-account-name}.myvtex.com/admin</ui> 
+
+<blockquote><ui>- <b>Easypay Account UID</b>: Identification of your seller account where purchase amounts from store sales will be deposited. To get this information, access the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo at the top of the screen, and click the desired account. Copy and save the <b>Account UID</b> information.</ui> 
+
+![easypay_en_18](//images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/2e4dd4665f90512068d9f145b7a81caa/easypay_en_18.png)
+
+<blockquote><ui>4. Click <b>Save</b>.</ui>
+
diff --git a/docs/tutorials/en/setting-up-payments-with-easypay.md b/docs/tutorials/en/setting-up-payments-with-easypay.md
new file mode 100644
index 000000000..afc5fa306
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-easypay.md
@@ -0,0 +1,210 @@
+---
+title: 'Setting up payments with easypay'
+id: 3xJQqjMIn0ARDI1HcwK88J
+status: PUBLISHED
+createdAt: 2023-09-18T16:48:21.184Z
+updatedAt: 2024-06-17T15:38:51.146Z
+publishedAt: 2024-06-17T15:38:51.146Z
+firstPublishedAt: 2023-09-18T18:53:57.235Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-easypay
+locale: en
+legacySlug: setting-up-payments-with-easypay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+On VTEX, you can integrate with the easypay payment provider. Your store can sell using easypay, MBWay, and MultiBanco through this provider.
+
+To use easypay, you need to:
+
+- [Install the easypay app](#install-the-easypay-app)
+- [Configure the easypay app](#configure-the-easypay-app)
+- [Configure the easypay webhook](#configure-the-easypay-webhook)
+- [Configure the easypay affiliation](#configure-the-easypay-affiliation)
+- [Configure payment with Apple Pay on easypay (optional)](#configure-payment-with-apple-pay-on-easypay-optional)     
+
+<div class="alert alert-warning" role="alert">If you are a marketplace or seller, read <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configuring payment with easypay in a marketplace</a> or <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-easypay-seller--5mYMCM1tiRiZO6PozuUncE">Configuring payment with easypay seller</a>.</div>
+
+## Install the easypay app
+
+To install the easypay app, follow the steps below:
+
+1. In the [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), run the command `vtex login accountname` to log in to your account.
+2. Install the easypay app using the `vtex install easypaypartnerpt.payment-provider-easypay` command. 
+
+## Configure the easypay app
+
+After installing the easypay app, you need to configure it. To access the settings screen, follow the steps below:
+
+1. In the VTEX Admin, go to __Extensions Hub > App Management__, or type __App Management__ in the search bar at the top of the page.
+2. Find the __Easypay Payment Provider__ app and click __Settings__.
+
+Configuration is divided in four sections:
+
+- [easypay credentials (required)](#easypay-credentials)
+- [Payment (required)](#payment)
+- [easypay checkout customization (required)](#easypay-checkout-customization)
+- [Sandbox mode](#sandbox-mode)
+
+![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+
+<div class="alert alert-warning" role="alert">You must set up the following configurations in the <a href="https://backoffice.easypay.pt/">easypay environment</a>. easypay controls these settings, therefore, VTEX does not guarantee that the steps below will be permanently updated. Use this document as a reference and check your <a href="https://backoffice.easypay.pt/">easypay environment</a> for up-to-date information.</div>
+
+### easypay credentials
+
+The information in this section must be completed.
+
+__Key ID e Key Value__: easypay key value and ID.
+
+<blockquote><ui>1. In the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo in the top left corner of the screen and the arrow of the desired account.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+<blockquote><ui>2. Go to <b>Web Services > Configuration API 2.0 > Keys</b>.</ui>
+
+![easypay_en_3](//images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/7a37b868b1d80e24001ad58e3debeee8/easypay_en_3.png)
+
+<blockquote><ui>3. Copy and save the <b>ID</b> and <b>Key</b> information.</ui>
+
+![easypay_en_4](//images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/9cd6f593c3f473726fc0380c0688d219/easypay_en_4.png)
+
+__Merchant account UID__: identification of the merchant account where purchase amounts from store sales will be deposited. If there is no separate merchant account, you can use the "Account UID" of the payment account.
+
+<blockquote><ui>1. In the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo in the top left corner of the screen, then click the arrow on the "MERCHANT 1" account.</ui>
+
+![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+
+<blockquote><ui>2. Copy and save the <b>Account UID</b> information.</ui>
+
+![easypay_en_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/e15357e9cfb846850ada8bfeda405d48/easypay_en_6.png)
+
+__Margin account UID__: identification of the margin account. 
+
+<div class="alert alert-info" role="alert">This field should only be completed if the store is a marketplace and splits payments. Learn more in the <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configuring payment with easypay in a marketplace</a> article.</div>
+
+__Refund account ID and Refund account key__: If there is no specific refund account, the __Key ID__ value must be entered in the __Refund account ID__ field, and the __Key value__ in the __Refund account key__.
+
+### Payment
+
+In this section, you must indicate whether your store will use asynchronous and/or synchronous payments. See the easypay documentation to check the available [payment methods](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) and their identification [acronyms](https://docs.quality-utility.aws.easypay.pt/checkout/reference).
+
+![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+
+__Accepted asynchronous payment types__: asynchronous payment methods available to the customer. Only enter the acronyms of the asynchronous payment types, separated by commas without periods or spaces.
+
+Example:
+
+| Correct | Incorret |
+| ---------------- | ---------------- |
+| mb,dd,vi,sc | mb, dd, vi, sc |
+
+<div class="alert alert-warning" role="alert">If you complete this field, you must also complete the <b>Expiration days for asynchronous payments</b> field.</div>
+
+__Accepted synchronous payment types__: synchronous payment methods available to the customer. Only enter the acronyms of the synchronous payment types, separated by commas without periods or spaces.
+
+Example:
+
+| Correct | Incorret |
+| ---------------- | ---------------- |
+| cc,mbw,uf | cc, mbw, uf |
+
+__Expiration days for asynchronous payments__: expiration period, in days, for asynchronous payments. Only enter the desired number of days.
+
+Example:
+
+| Correct | Incorret |
+| ---------------- | ---------------- |
+| 10 | 10 days, Dec, or 05/10/2023 |
+
+### easypay checkout customization
+
+easypay has a native checkout layout configured in the app. See below:
+
+![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+
+If you want to customize easypay's native checkout, complete one or more fields in this section:
+
+- __Checkout logo URL__: logo displayed at the easypay checkout. Enter the link to the image you want to use
+- __Checkout background color__: background color. Enter the HEX code of the desired color. Native default: #ffffff.
+- __Checkout accent color__: highlight color, button pattern, and input borders. Enter the HEX code of the desired color. Native default: #0d71f9.
+- __Checkout error color__: error message color. Enter the HEX code of the desired color. Native default: #ff151f.
+- __Checkout input background color__: input background color. Enter the HEX code of the desired color. Native default: transparent.
+- __Checkout input border color__: input border color. Enter the HEX code of the desired color. Native default: the same color used in the __accent color__.
+- __Checkout input border radius__: allows you to define the rounded borders of the inputs. Enter the desired value in pixels (numbers only). Native default: 50 pixels.
+
+Example:
+
+| Correct | Incorret |
+| ---------------- | ---------------- |
+| 35 | 35px |
+
+- __Checkout button background color__: background color of the buttons. Enter the HEX code of the desired color. Native default: the same color used in the __accent color__.
+- __Checkout button border radius__: allows you to set the rounded borders of the buttons. Enter the desired value in pixels (numbers only). Native default: 50 pixels.
+
+Example:
+
+| Correct | Incorret |
+| ---------------- | ---------------- |
+| 30 | 30px |
+
+- __Checkout button box shadow__: option to enable or disable the button shadow.
+- __Checkout font family__: fonts used in texts. Enter the generic family name, web-safe font, or font link. Native default: Overpass. Example, correct: sans-serif, verdana, ou https://fonts.gstatic.com/s/overpass/v12/qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PPbM5qKl8Kuo8AzesE.woff2
+
+- __Checkout base font size__: allows you to set the font size in the root element. Enter the desired value in pixels (numbers only). Native default: 10 pixels.
+
+Example:
+
+| Correct | Incorret |
+| ---------------- | ---------------- |
+| 11 | 11px |
+
+<div class="alert alert-warning" role="alert">Do not use fonts over 12 pixels, as they can blur the layout.</b></div>
+
+### Sandbox mode
+
+To enable the development test environment, select the __Enable sandbox mode__ option. You must use test credentials.
+
+After completing the configuration fields, click __Save__.
+
+## Configure the easypay webhook
+
+To configure the easypay webhook, follow the steps below:
+
+<blockquote><ui>1. In the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo in the top left corner of the screen, then click the arrow of the desired account.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+<blockquote><ui>2. Go to <b>Web Services > URL Configuration</b>.</ui>
+
+<blockquote><ui>3. In <b>URL: Notify</b>, use the link below, adding the name of your store.</ui>
+
+`https://{your-account-name}.myvtex.com/_v/easypaypartnerpt.payment-provider-easypay/webhook`
+
+![easypay_en_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/a07d223716625952489b062874cf0aab/easypay_en_9.png)
+
+<blockquote><ui>4. Click <b>Submit</b>.</ui>
+
+## Configure the easypay affiliation
+
+To configure the easypay affiliation, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __easypay__ in the search bar and click on the name of the provider.
+4. Complete the __Application Key__ and __Application Token__ fields with your easypay account information.
+5. In __Payment Settlement__, select the __Use Payment Behavior Recommended by Payment Processor__ option.
+6. In __Enable payout split and sending payment recipients?__, select __Yes__.
+7. Click `Save`.
+
+## Configure payment with Apple Pay on easypay (optional) 
+
+To process payments with Apple Pay on easypay, you must first perform configurations to enable your store in the Apple Pay environment. Learn more at [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/docs/guides/setting-up-merchant-id-in-apple-pay).    
+
+To configure other payment methods that easypay will process, read the [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions) article.
+
+To set special conditions for payment methods, read [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+
+After following the instructions, it can take up to 10 minutes for the easypay connector to be displayed as a payment option at your store checkout.  
+
diff --git a/docs/tutorials/en/setting-up-payments-with-ebanx-local.md b/docs/tutorials/en/setting-up-payments-with-ebanx-local.md
index 2f1c36ac4..70de824b6 100644
--- a/docs/tutorials/en/setting-up-payments-with-ebanx-local.md
+++ b/docs/tutorials/en/setting-up-payments-with-ebanx-local.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Ebanx-Local'
 id: 6vVYppbwct3B4j8KuCAvUR
 status: PUBLISHED
 createdAt: 2023-03-22T17:09:50.665Z
-updatedAt: 2023-03-23T12:45:48.284Z
-publishedAt: 2023-03-23T12:45:48.284Z
+updatedAt: 2024-01-23T18:06:33.564Z
+publishedAt: 2024-01-23T18:06:33.564Z
 firstPublishedAt: 2023-03-22T17:34:38.586Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-ebanx-local
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Ebanx payment provider. With this connector, your store can make sales through bank invoice, credit cards and PIX.
+At VTEX, it is possible to integrate with the Ebanx payment provider. With this provider, your store can make sales through bank invoice, credit cards and PIX.
 
-To configure Ebanx affiliation, follow the steps below:
+To configure Ebanx, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __EBANX-Local__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __EBANX-Local__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account Ebanx.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-ebanx.md b/docs/tutorials/en/setting-up-payments-with-ebanx.md
index 6deda1be1..f811d4d2a 100644
--- a/docs/tutorials/en/setting-up-payments-with-ebanx.md
+++ b/docs/tutorials/en/setting-up-payments-with-ebanx.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Ebanx'
 id: 4yKdQrt57AW7aElfHH4QKM
 status: PUBLISHED
 createdAt: 2023-03-22T14:27:42.440Z
-updatedAt: 2023-03-23T12:45:53.859Z
-publishedAt: 2023-03-23T12:45:53.859Z
+updatedAt: 2024-01-23T18:07:19.598Z
+publishedAt: 2024-01-23T18:07:19.598Z
 firstPublishedAt: 2023-03-22T17:04:49.283Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-ebanx
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Ebanx payment provider. With this connector, your store can make sales through bank invoice, credit cards and PIX.
+At VTEX, it is possible to integrate with the Ebanx payment provider. With this provider, your store can make sales through bank invoice, credit cards and PIX.
 
-To configure Ebanx affiliation, follow the steps below:
+To configure Ebanx, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Ebanx__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Ebanx__ in the search bar and click on the name of the provider.
 4. Click on __Authorize__. You will be redirected to the Ebanx environment.
 5. In the Ebanx environment, enter your Ebanx account login and password. Follow the indicated instructions to complete the Ebanx account linking with VTEX.
 6. After returning to __Admin VTEX__, click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-egetnetv2.md b/docs/tutorials/en/setting-up-payments-with-egetnetv2.md
index b2b89b0a4..7a84b60c1 100644
--- a/docs/tutorials/en/setting-up-payments-with-egetnetv2.md
+++ b/docs/tutorials/en/setting-up-payments-with-egetnetv2.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with EgetnetV2'
 id: 6jfBE8ocN5T0xQo8BTGH31
 status: PUBLISHED
 createdAt: 2023-02-13T13:55:05.519Z
-updatedAt: 2023-02-13T14:12:54.200Z
-publishedAt: 2023-02-13T14:12:54.200Z
+updatedAt: 2024-03-14T18:21:39.711Z
+publishedAt: 2024-03-14T18:21:39.711Z
 firstPublishedAt: 2023-02-13T14:12:54.200Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,21 @@ legacySlug: setting-up-payments-with-egetnetv2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the EgetnetV2 payment provider. With this connector, your store can make sales through credit cards, bank invoice and PIX.
+At VTEX, it is possible to integrate with the EgetnetV2 payment provider. With thisprovider, your store can make sales through credit cards, bank invoice and PIX.
 
-To configure EgetnetV2 affiliation, follow the steps below:
+To configure EgetnetV2, follow the steps below:
 
-1. Access the __Admin__ VTEX.
-2. Click on __Payments__.
-3. Then, click on __Settings__.
-4. In the __Gateway affiliations__ tab, click on the `+` button.
-5. Click on the __EgetnetV2__ connector.
-6. Fill in the __Application Key__ and __Application Token__ fields with data provided by EgetnetV2.
-7. In __Enable payout split and sending payment recipients?__, select whether split payments will be available for the marketplace and sellers.
-8. Click on `Save`.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __EgetnetV2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by EgetnetV2.
+5. If you wish to modify the identification name to be displayed for the EgetnetV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. If you want to use [payment split](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx) in your store, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
+8. Click `Save`.
 
-To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions).
+To configure the payment methods to be processed by EgetnetV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-After following the indicated steps, EgetnetV2 connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, EgetnetV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-etpay.md b/docs/tutorials/en/setting-up-payments-with-etpay.md
index bc765a4e0..6a0df97c6 100644
--- a/docs/tutorials/en/setting-up-payments-with-etpay.md
+++ b/docs/tutorials/en/setting-up-payments-with-etpay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with ETpay'
 id: 1vYO022oVj4MdVKP5fCMNx
 status: PUBLISHED
 createdAt: 2022-10-18T17:45:32.139Z
-updatedAt: 2023-03-21T20:54:12.646Z
-publishedAt: 2023-03-21T20:54:12.646Z
+updatedAt: 2024-01-24T17:24:23.326Z
+publishedAt: 2024-01-24T17:24:23.326Z
 firstPublishedAt: 2022-10-18T17:56:29.587Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: setting-up-payments-with-etpay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the ETpay payment provider. With this connector, your store can make sales through the ETpay.
+At VTEX, it is possible to integrate with the ETpay payment provider. With this provider, your store can make sales through the ETpay.
 
-To set up ETpay affiliation, follow the steps below:
+To set up ETpay, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __EtPayment__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __EtPayment__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by ETpay.
-5. Click on `Save`.
+5. Click `Save`.
 
 ## Setting up ETpay payment condition 
 
@@ -33,4 +33,4 @@ To set up ETpay affiliation, follow the steps below:
 4. Activate the condition in the __Status__ field.
 5. Click on `Save`.
 
-After following the indicated steps, ETpay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, ETpay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-evopayments.md b/docs/tutorials/en/setting-up-payments-with-evopayments.md
new file mode 100644
index 000000000..b24b518cf
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-evopayments.md
@@ -0,0 +1,46 @@
+---
+title: 'Setting up payments with EvoPayments'
+id: 7CxSgoftps0DHsfR8otQMf
+status: PUBLISHED
+createdAt: 2024-03-11T17:36:12.910Z
+updatedAt: 2024-03-14T16:37:46.611Z
+publishedAt: 2024-03-14T16:37:46.611Z
+firstPublishedAt: 2024-03-11T18:19:00.757Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-evopayments
+locale: en
+legacySlug: setting-up-payments-with-evopayments
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the EVO Payments payment provider. With this provider, your store can make sales through credit, debit, private labels and cobranded cards, and bank invoices.
+
+To configure EVO Payments, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __EvoPayments__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by EVO Payments.
+5. If you wish to modify the identification name to be displayed for the EVO Payments provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. In __Habilitar autenticación 3DS__, select whether you want to enable 3DS security validation.
+9. In __Habilitar autorización y captura__, select whether you want to activate this function.
+10. In __Habilitar plan Iphone For Life__, select whether you want to activate this option. 
+11. Click `Save`.
+
+To configure the payment methods to be processed by EVO Payments, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, EVO Payments may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-fcamara-payment-initiator.md b/docs/tutorials/en/setting-up-payments-with-fcamara-payment-initiator.md
index 411099be8..58204dcf4 100644
--- a/docs/tutorials/en/setting-up-payments-with-fcamara-payment-initiator.md
+++ b/docs/tutorials/en/setting-up-payments-with-fcamara-payment-initiator.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with FCamara (Payment initiator)'
 id: 4p5E3jc9J5xHkOI6AbnhTV
 status: PUBLISHED
 createdAt: 2023-04-03T15:12:23.123Z
-updatedAt: 2023-04-03T16:42:01.758Z
-publishedAt: 2023-04-03T16:42:01.758Z
+updatedAt: 2024-01-23T18:01:44.039Z
+publishedAt: 2024-01-23T18:01:44.039Z
 firstPublishedAt: 2023-04-03T16:42:01.758Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-fcamara-payment-initiator
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the FCamara payment initiator. With this connector, your store can make sales through PIX.
+At VTEX, it is possible to integrate with the FCamara payment initiator. Through it, your store can make sales through PIX.
 
-To configure FCamara affiliation, follow the steps below:
+To configure FCamara, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __iniciadorfcamara__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __iniciadorfcamara__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account FCamara.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-fintoc.md b/docs/tutorials/en/setting-up-payments-with-fintoc.md
new file mode 100644
index 000000000..85faa0e21
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-fintoc.md
@@ -0,0 +1,39 @@
+---
+title: 'Setting up payments with Fintoc'
+id: 3TIz2oxbNtzhypWiypqrOZ
+status: PUBLISHED
+createdAt: 2023-07-14T17:06:16.055Z
+updatedAt: 2024-01-24T17:39:34.960Z
+publishedAt: 2024-01-24T17:39:34.960Z
+firstPublishedAt: 2023-07-14T17:49:20.115Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-fintoc
+locale: en
+legacySlug: setting-up-payments-with-fintoc
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Fintoc. With this provider, your store can make sales through the Fintoc.
+
+To configure Fintoc, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Fintoc__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__ y __Secret Key__ fields with data provided by your account Fintoc.
+5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+6. Click on `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the __+__ button.
+3. Click on __Fintoc__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on `Save`.
+
+After following the indicated steps, Fintoc connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-flywire.md b/docs/tutorials/en/setting-up-payments-with-flywire.md
index 797e26fa4..937158baf 100644
--- a/docs/tutorials/en/setting-up-payments-with-flywire.md
+++ b/docs/tutorials/en/setting-up-payments-with-flywire.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Flywire'
 id: 12nQ0teCWM1UUtd2Fo6lzO
 status: PUBLISHED
 createdAt: 2023-04-03T13:05:10.955Z
-updatedAt: 2023-04-03T13:32:26.361Z
-publishedAt: 2023-04-03T13:32:26.361Z
+updatedAt: 2024-01-25T18:15:31.540Z
+publishedAt: 2024-01-25T18:15:31.540Z
 firstPublishedAt: 2023-04-03T13:32:26.361Z
 contentType: tutorial
 productTeam: Financial
@@ -15,31 +15,31 @@ legacySlug: setting-up-payments-with-flywire
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Flywire payment provider. With this connector, your store can make sales through promissory and Flywire.
+At VTEX, it is possible to integrate with the Flywire payment provider. With this provider, your store can make sales through Notes Payable and Flywire.
 
-To configure Flywire affiliation, follow the steps below:
+To configure Flywire, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Flywire__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Flywire__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__, __Application Token__, __Recipient__, __Locale__, __Provider__ and __Callback version__ fields with data provided by Flywire.
 5. Under __Environment__, choose one of two options: __Demo__ or __Production__.
 6. Under __Display Payer Information__, choose one of two options: __True__ or __False__.
-7. Click on `Save`.
+7. Click `Save`.
 
-## Setting up payment condition Promissory
+## Setting up payment condition Notes Payable
 
-If you want to use Flywire with a promissory note and you have not yet configured the promissory note as a payment method in other connectors in your store, go to [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-promissory--5pW7avTwtyQcMu4uiW8quQ).
+If you want to use Flywire with a note payable and you have not yet configured the note payable as a payment method in other connectors in your store, go to [Setting up payments with Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ).
 
 Then, follow the steps below:
 
 1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
 2. In the __Payment Conditions__ tab, click on the `+` button.
-3. On __Custom Payment__, click the button corresponding to the name used for the promissory note payment method (configured in the previous section).
+3. On __Custom Payment__, click the button corresponding to the name used for the note payable payment method (configured in the previous section).
 4. Activate the condition in the __Status__ field.
 5. On __Process with affiliation__, select __flywirepartnermx-payment-provider-config-v0__.
 6. If you wish, you can also configure [payment special conditionso](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
-7. Click on `Save`.
+7. Click `Save`.
 
 ## Setting up payment condition Flywire
 
@@ -49,6 +49,6 @@ Then, follow the steps below:
 4. Activate the condition in the __Status__ field.
 5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
 6. If you wish, you can also configure [payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
-7. Click on `Save`.
+7. Click `Save`.
 
-After following the indicated steps, Flywire connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Flywire may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-fpay.md b/docs/tutorials/en/setting-up-payments-with-fpay.md
index 794a5655b..949bc9edb 100644
--- a/docs/tutorials/en/setting-up-payments-with-fpay.md
+++ b/docs/tutorials/en/setting-up-payments-with-fpay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Fpay'
 id: 6BaLIO2R7tOh6E1MmNoDXj
 status: PUBLISHED
 createdAt: 2022-10-18T19:13:32.326Z
-updatedAt: 2023-03-21T20:52:34.889Z
-publishedAt: 2023-03-21T20:52:34.889Z
+updatedAt: 2024-01-24T17:26:52.492Z
+publishedAt: 2024-01-24T17:26:52.492Z
 firstPublishedAt: 2022-10-18T19:42:03.523Z
 contentType: tutorial
 productTeam: Financial
@@ -15,25 +15,25 @@ legacySlug: setting-up-payments-with-fpay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Fpay payment provider. With this connector, your store can make sales through the promissory.
+At VTEX, it is possible to integrate with the Fpay payment provider. With this provider, your store can make sales through the Notes Payable.
 
-To set up Fpay affiliation, follow the steps below:
+To set up Fpay, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Fpay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Fpay__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Fpay.
 5. Click on `Save`.
 
-## Setting up Promissory
+## Setting up Notes Payable
 
-If you have not yet configured the promissory note as a payment method in other connectors in your store, go to [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-promissory--5pW7avTwtyQcMu4uiW8quQ).
+If you have not yet configured the Notes Payable as a payment method in other connectors in your store, go to [Setting up payments with Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable).
 
 ## Setting up payment condition 
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. In the __Payment Conditions__ tab, click on the `+` button.
-3. On __Custom Payment__, click the button corresponding to the name used for the promissory note payment method (configured in the previous section).
+3. On __Custom Payment__, click the button corresponding to the name used for the Notes Payable payment method (configured in the previous section).
 4. Activate the condition in the __Status__ field.
 5. On __Process with affiliation__, select __fpaypartnercl-fpay-v0__.
 6. If you wish, you can also configure [payment special conditionso](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
diff --git a/docs/tutorials/en/setting-up-payments-with-geru.md b/docs/tutorials/en/setting-up-payments-with-geru.md
new file mode 100644
index 000000000..d6f0107fd
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-geru.md
@@ -0,0 +1,40 @@
+---
+title: 'Setting up payments with Geru'
+id: 2XmYp4Uh1Yulv3a9puRgwm
+status: PUBLISHED
+createdAt: 2024-02-05T11:49:37.163Z
+updatedAt: 2024-03-13T14:10:42.303Z
+publishedAt: 2024-03-13T14:10:42.303Z
+firstPublishedAt: 2024-02-05T13:45:07.728Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-geru
+locale: en
+legacySlug: setting-up-payments-with-geru
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Geru payment provider. With this provider, your store can make sales through Geru and BNPL.
+
+To configure Geru, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Geru__ in the search bar and click on the name of the provider.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account Geru.
+5. If you wish to modify the identification name to be displayed for the Geru provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __Geru__ or __BNPL__.
+4. Activate the condition in the __Status__ field. To use __BNPL__, in __Process with affiliation__, select the __boletoflex-geru-v0__ option.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, Geru may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-gocuotas.md b/docs/tutorials/en/setting-up-payments-with-gocuotas.md
new file mode 100644
index 000000000..95192e26e
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-gocuotas.md
@@ -0,0 +1,39 @@
+---
+title: 'Setting up payments with GOcuotas'
+id: 6oGcugCc3pXIJEhbOZ5YmV
+status: PUBLISHED
+createdAt: 2023-09-29T11:30:25.004Z
+updatedAt: 2024-02-05T13:42:55.988Z
+publishedAt: 2024-02-05T13:42:55.988Z
+firstPublishedAt: 2023-09-29T11:39:03.239Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-gocuotas
+locale: en
+legacySlug: setting-up-payments-with-gocuotas
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the GOcuotas payment provider. With this provider, your store can make sales through GOcuotas.
+
+To configure GOcuotas, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __GOcuotas__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account GOcuotas.
+5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+6. Click on `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __GOcuotas__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on `Save`.
+
+After following the indicated steps, GOcuotas may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-guatapay.md b/docs/tutorials/en/setting-up-payments-with-guatapay.md
new file mode 100644
index 000000000..abe2a0578
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-guatapay.md
@@ -0,0 +1,39 @@
+---
+title: 'Setting up payments with Guatapay'
+id: 57ilA6k1VKZjy0dgwSs7pu
+status: PUBLISHED
+createdAt: 2023-09-18T15:35:35.188Z
+updatedAt: 2024-01-25T17:04:24.009Z
+publishedAt: 2024-01-25T17:04:24.009Z
+firstPublishedAt: 2023-09-18T16:33:40.921Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-guatapay
+locale: en
+legacySlug: setting-up-payments-with-guatapay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Guatapay payment provider. With this provider, your store can make sales through Guatapay.
+
+To configure Guatapay, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Guatapay__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__, __Client ID - Guatapay__ and __Client Secret - Guatapay__ fields with data provided by your account Guatapay.
+5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+6. Click on `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __Guatapay__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on `Save`.
+
+After following the indicated steps, Guatapay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-inswitch.md b/docs/tutorials/en/setting-up-payments-with-inswitch.md
new file mode 100644
index 000000000..61fbd2095
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-inswitch.md
@@ -0,0 +1,49 @@
+---
+title: 'Setting up payments with Inswitch'
+id: XxY7tbpg4GMrexGQfto6Q
+status: PUBLISHED
+createdAt: 2023-07-14T17:56:24.581Z
+updatedAt: 2024-01-24T17:44:57.275Z
+publishedAt: 2024-01-24T17:44:57.275Z
+firstPublishedAt: 2023-07-14T18:11:24.293Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-inswitch
+locale: en
+legacySlug: setting-up-payments-with-inswitch
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Inswitch payment provider. With this provider, your store can make sales through the Inswitch.
+
+To configure Inswitch, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Inswitch__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__ and __Application Token__ fields with the data provided by Inswitch.
+5. In the __Payment capture__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use Behavior Recommended By The Payment Processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic Capture Immediately After Payment Authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic Capture Immediately After Anti-fraud Analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic Capture Immediately After Payment Authorization".</li>
+   		<li><b>Scheduled: Schedules The Automatic Capture</b>: By selecting this option, the field <b>Scheduled time frame in hours for automatic capture</b> will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.</li>        
+   		<li><b>Deactivated: Not Automatically Captured</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+6. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Choose the payment condition __Inswitch__.
+4. Fill the __Rule Name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+7. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Click `Save`.
+
+After following the indicated steps, Inswitch may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-itau-rede.md b/docs/tutorials/en/setting-up-payments-with-itau-rede.md
new file mode 100644
index 000000000..989b31c85
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-itau-rede.md
@@ -0,0 +1,91 @@
+---
+title: 'Setting up payments with Itaú Rede'
+id: 77BYOKxVzONWulAf8dTVSX
+status: PUBLISHED
+createdAt: 2024-04-18T15:03:32.890Z
+updatedAt: 2024-04-25T15:26:44.454Z
+publishedAt: 2024-04-25T15:26:44.454Z
+firstPublishedAt: 2024-04-25T14:54:53.085Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-itau-rede
+locale: en
+legacySlug: setting-up-payments-with-itau-rede
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Itaú Rede payment provider. With this provider, your store can make sales through credit cards.
+
+To use Itaú Rede, you must:
+
+- [Obtain credentials in the Userede environment](#obtain-credentials-in-the-userede-environment)
+- [Setting up Itaú Rede on VTEX](#setting-up-itau-rede-on-vtex)
+- [Setting up the payment condition](#setting-up-the-payment-condition) 
+
+## Obtain credentials in the Userede environment
+
+<div class="alert alert-warning">
+Configurations made in an environment external to VTEX may be discontinued or modified without prior notice. Check your Itaú Rede account for updated information.
+</div>
+
+To obtain the __App key__ and __App token__ credentials necessary to configure Itaú Rede on VTEX, follow the steps below:
+
+<blockquote><ui>1. Access the <a href="#https://meu.userede.com.br/login">Userede Portal</a> with your Itaú Rede account information.</ui>
+
+<blockquote><ui>2. Select the account in which you want to transact payments at VTEX and click <b>Aplicar</b>. Save the account number, as it must be used in the <b>App key</b> field in the <a href="#setting-up-itau-rede-on-vtex">Setting up Itaú Rede on VTEX</a>.</ui> 
+
+![Itaú Rede_1](//images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
+
+<blockquote><ui>3. After the screen updates to the desired account, in the <b>para vender</b> menu, select the <b>e-commerce</b> option.
+
+![Itaú Rede_2](//images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
+
+<blockquote><ui>4. On the <b>e-commerce</b> page, click on the <b>chave de integração</b> card.
+
+![Itaú Rede_3](//images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
+
+<blockquote><ui>5. After reading the "chave de integração" information, click <b>li, estou ciente</b>.
+
+![Itaú Rede_4](//images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
+
+<blockquote><ui>6. Click the <b>gerar nova chave</b> button.
+
+![Itaú Rede_5](//images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
+
+<blockquote><ui>7. Check the information described in the <b>gerar nova chave de integração</b> window and click <b>gerar nova chave</b>.
+
+![Itaú Rede_6](//images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
+
+<blockquote><ui>8. After creating the new key, click <b>copiar</b> and preserve the information in a safe location. This key must be used in the <b>Token de aplicação</b> field in the section <a href="#setting-up-itau-rede-on-vtex">Setting up Itaú Rede on VTEX</a>.
+
+<blockquote><ui><div class="alert alert-warning">
+Once an "chave de integração" is created in the Network environment, it cannot be accessed again from other locations. Record the "chave" information in a protected location, and if lost, repeat the process to generate a new key.
+  </div></ui></blockquote>
+
+## Setting up Itaú Rede on VTEX
+
+To configure Itaú Rede, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __ItauRede__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ obtained in steps 2 and 8 of the section [Obtain credentials in the Userede environment](#obtain-credentials-in-the-userede-environment).
+5. If you wish to modify the identification name to be displayed for the Itaú Rede provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In __merchantName__, enter the name of your store.
+8. In __SoftDescriptor__, describe the identification message to be displayed in the transaction carried out in your store.
+9. In __delayToAutoSettle__, choose how long you want the capture to take after the transaction approval and the anti-fraud analysis.
+10. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on the name of the desired credit card brand.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+7. Click `Save`.
+
+After following the indicated steps, Itaú Rede may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-iugu.md b/docs/tutorials/en/setting-up-payments-with-iugu.md
index ce8e14bfb..583873c4b 100644
--- a/docs/tutorials/en/setting-up-payments-with-iugu.md
+++ b/docs/tutorials/en/setting-up-payments-with-iugu.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up payments with Iugu'
+title: 'Setting up payments with iugu'
 id: 2c1nAo5iR6jG1UySzRB89t
 status: PUBLISHED
 createdAt: 2022-03-31T18:58:08.146Z
-updatedAt: 2022-03-31T19:22:31.835Z
-publishedAt: 2022-03-31T19:22:31.835Z
+updatedAt: 2024-03-13T11:53:59.094Z
+publishedAt: 2024-03-13T11:53:59.094Z
 firstPublishedAt: 2022-03-31T19:22:31.835Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,69 @@ legacySlug: setting-up-payments-with-iugu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Iugu payment provider. With this connector, your store can make sales through credit cards, bank invoice and PIX.
+[iugu](https://partnerportal.vtex.com/iugu-156/p) is a VTEX partner solution that offers the following payment options through [transparent checkout](https://help.vtex.com/en/tutorial/what-is-transparent-checkout--2Y4ECegUmcYUggmck2GOwe): credit card, pix and bank slip. Furthermore, it is possible to carry out [recurrence](https://help.vtex.com/en/tutorial/how-to-set-up-recurrence-in-payment-conditions--6EGuoAytLqU2CqUuaI2GUW) and [split payment](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx) operations (receivables and transactions) between marketplaces.
 
-To set up your Iugu affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
+To add iugu to your store, follow the steps below:
 
-To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __iugu__ in the search bar and click on the name of the provider.
+4. In the __App key__ and __App token__ fields, enter the information provided by iugu ([Account ID and API Key](https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#localizando-id-da-conta-e-chave-api-no-painel-da-iugu)).
+5. If you wish to modify the identification name to be displayed for the iugu provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. If you wish to use the bank slip as a payment method, in __Provider fields__, fill in the field __Prazo de vencimento do boleto (em dias)__ with the same value configured in your customer area on the iugu portal.
+8. Click `Save`.
 
-After following the indicated steps, Iugu connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+## Setting up payment conditions
+
+To process credit card, pix and bank slip payment methods with iugu in your store, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on the desired payment method (credit card brand name, pix or bank slip).
+4. Fill the __Condition name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. In __Process with provider__ select the iugu option.
+7. For credit card payments, select whether you want to use an anti-fraud system by selecting the __Use anti-fraud solution__ option. It is also possible to configure whether credit card payments should be made [in full or in installments (with and without interest)](https://help.vtex.com/en/tutorial/condicoes-de-pagamento--tutorials_455#payment-in-full).
+8. If you wish, you can also configure [special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+9. Click `Save`.
+
+After following the indicated steps, iugu provider may take up to 10 minutes to appear at your store's checkout as a payment option.
+
+<div class="alert alert-warning">
+  Before carrying out transactions by credit card, PIX or bank slip with iugu in your store, check whether these payment methods are already enabled in <a href="https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento">your customer area on the iugu portal</a>.
+  </div>
+
+## Setting up split payment on the marketplace with iugu
+
+To process payments on [marketplace with split payment](https://help.vtex.com/en/tutorial/payments-in-vtex-marketplaces--2kYOfWCZYweJkYl18bw9yD#payment-split) with iugu it is necessary to register sellers of your store with the same CNPJ (seller identification number) in the VTEX Admin and in your customer area on the iugu portal.
+
+Find out more about creating sellers on VTEX at [Adding a seller](https://help.vtex.com/en/tutorial/adding-a-seller--tutorials_392) and access iugu documentation to create subaccounts (sellers) via [area of client](https://support.iugu.com/hc/pt-br/articles/4411276874779-Como-criar-uma-subconta-pelo-painel-iugu-) or [API](https://dev.iugu.com/docs/configurar-subconta-por-api).
+
+### Enable payout split with iugu
+
+To enable payout split with iugu in your store, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. Type the name __iugu__ in the search bar and click on the name of the provider.
+3. In __Details__, click on the `Edit` button.
+4. In __Payment control__, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
+5. Click `Save`.
+
+<div class="alert alert-warning">
+  The payout split option is not available for use in a test environment.
+  </div>
+
+After following the steps indicated, the payout split functionality with the iugu provider may take up to 10 minutes to be activated in your store.
+
+<div class="alert alert-warning">
+  To define specific commissions for each seller in your store, access <b>Marketplace > Sellers> Management</b> in the VTEX Admin, select the desired seller and enter the commission values in <b>Commissions</b>.
+  </div>
+
+## Setting up recurrence with iugu
+
+To make [recurrence](https://help.vtex.com/en/tutorial/how-to-set-up-recurrence-in-payment-conditions--6EGuoAytLqU2CqUuaI2GUW) available as a special payment condition through iugu, it is necessary:
+
+- Enable recurrence mode in the VTEX Admin.
+- Configure credit card or bank slip payment methods in the VTEX Admin and iugu.
+- Configure the [subscriptions](https://help.vtex.com/en/tutorial/how-to-configure-subscriptions--1FA9dfE7vJqxBna9Nft5Sj) functionality in your store.
diff --git a/docs/tutorials/en/setting-up-payments-with-k8bank.md b/docs/tutorials/en/setting-up-payments-with-k8bank.md
new file mode 100644
index 000000000..ee89cfa61
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-k8bank.md
@@ -0,0 +1,44 @@
+---
+title: 'Setting up payments with K8Bank'
+id: 1ewZll1fwjClvp5Wl1uES1
+status: PUBLISHED
+createdAt: 2023-09-18T13:14:17.375Z
+updatedAt: 2024-01-23T17:56:32.780Z
+publishedAt: 2024-01-23T17:56:32.780Z
+firstPublishedAt: 2023-09-18T13:48:29.694Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-k8bank
+locale: en
+legacySlug: setting-up-payments-with-k8bank
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the K8Bank payment provider. With this provider, your store can make sales through a credit, debit, private labels and cobranded cards, bank invoices and PIX.
+
+To configure K8Bank, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __K8Bank__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__, __cnpj__ and __CobrancasClientId__ fields with the data provided by K8Bank.
+5. In the __Payment capture__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use Behavior Recommended By The Payment Processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Immediate: Automatic Capture Immediately After Payment Authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Immediate: Automatic Capture Immediately After Anti-fraud Analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic Capture Immediately After Payment Authorization".</li>
+   		<li><b>Scheduled: Schedules The Automatic Capture</b>: By selecting this option, the field <b>Scheduled time frame in hours for automatic capture</b> will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.</li>        
+   		<li><b>Deactivated: Not Automatically Captured</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+6. In __Enable payout split and sending payment recipients?__, select whether split payments will be available for the marketplace and sellers.
+
+7. Click on the `Save` button.
+
+To configure the payment methods to be processed by K8Bank, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, K8Bank connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-kaiowa.md b/docs/tutorials/en/setting-up-payments-with-kaiowa.md
index 7e3f4e312..ecc0ef758 100644
--- a/docs/tutorials/en/setting-up-payments-with-kaiowa.md
+++ b/docs/tutorials/en/setting-up-payments-with-kaiowa.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Kaiowa'
 id: 1QfsSpAF0CHQFVd9qSGcA5
 status: PUBLISHED
 createdAt: 2023-04-06T18:20:04.972Z
-updatedAt: 2023-04-06T18:26:07.966Z
-publishedAt: 2023-04-06T18:26:07.966Z
+updatedAt: 2024-01-23T17:58:45.045Z
+publishedAt: 2024-01-23T17:58:45.045Z
 firstPublishedAt: 2023-04-06T18:26:07.966Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-kaiowa
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Kaiowa payment provider. With this connector, your store can make sales through Kaiowa.
+At VTEX, it is possible to integrate with the Kaiowa payment provider. With this provider, your store can make sales through Kaiowa.
 
-To configure Kaiowa affiliation, follow the steps below:
+To configure Kaiowa, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Kaiowa__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Kaiowa__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account Kaiowa.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-khipu.md b/docs/tutorials/en/setting-up-payments-with-khipu.md
index 32e1aa344..de81f4ec4 100644
--- a/docs/tutorials/en/setting-up-payments-with-khipu.md
+++ b/docs/tutorials/en/setting-up-payments-with-khipu.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Khipu'
 id: RcHQjURWDXa0doL15DiUj
 status: PUBLISHED
 createdAt: 2023-03-24T19:34:06.675Z
-updatedAt: 2023-03-30T14:08:54.819Z
-publishedAt: 2023-03-30T14:08:54.819Z
+updatedAt: 2024-01-24T17:53:53.676Z
+publishedAt: 2024-01-24T17:53:53.676Z
 firstPublishedAt: 2023-03-30T14:08:54.819Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-khipu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Khipu payment provider. With this connector, your store can make sales through promissory.
+At VTEX, it is possible to integrate with the Khipu payment provider. With this provider, your store can make sales through Notes Payable.
 
-To configure Khipu affiliation, follow the steps below:
+To configure Khipu, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Khipu__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Khipu__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Khipu.
 5. In the __Payment settlement__ field, select one of the available options:
 
@@ -35,18 +35,18 @@ To configure Khipu affiliation, follow the steps below:
 
 <ui>  7. Click on <b>Save.</b></ui>
 
-## Setting up Promissory
+## Setting up Notes Payable
 
-If you have not yet configured the promissory note as a payment method in other connectors in your store, go to [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-promissory--5pW7avTwtyQcMu4uiW8quQ).
+If you have not yet configured the Notes Payable as a payment method in other connectors in your store, go to [Setting up payments with Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable).
 
 ## Setting up payment condition 
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. In the __Payment Conditions__ tab, click on the `+` button.
-3. On __Custom Payment__, click the button corresponding to the name used for the promissory note payment method (configured in the previous section).
+3. On __Custom Payment__, click the button corresponding to the name used for the Notes Payable payment method (configured in the previous section).
 4. Activate the condition in the __Status__ field.
 5. On __Process with affiliation__, select __srconsultores-khipu-v0__.
 6. If you wish, you can also configure [payment special conditionso](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
 7. Click on `Save`.
 
-After following the indicated steps, Khipu connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Khipu may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-koin-payments.md b/docs/tutorials/en/setting-up-payments-with-koin-payments.md
index f89f2686d..c71ccf149 100644
--- a/docs/tutorials/en/setting-up-payments-with-koin-payments.md
+++ b/docs/tutorials/en/setting-up-payments-with-koin-payments.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Koin-Payments'
 id: 5nTQFgTLGkPcJrqi7PKlO1
 status: PUBLISHED
 createdAt: 2022-08-18T12:40:14.512Z
-updatedAt: 2023-03-21T21:02:35.479Z
-publishedAt: 2023-03-21T21:02:35.479Z
+updatedAt: 2024-03-11T17:58:22.260Z
+publishedAt: 2024-03-11T17:58:22.260Z
 firstPublishedAt: 2022-08-18T12:56:36.170Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,20 @@ legacySlug: setting-up-payments-with-koin-payments
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Koin-Payments payment provider. With this connector, your store can make sales through a credit and debit cards, PIX and BoletoParceladoKoin.
+At VTEX, it is possible to integrate with the Koin-Payments payment provider. With this provider, your store can make sales through a credit and debit cards, PIX and BoletoParceladoKoin.
 
-To configure Koin-Payments affiliation, follow the steps below:
+To configure Koin-Payments, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Koin-Payments__ connector.
-4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Koin-Payments.
-5. Click on `Save`.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Koin-Payments__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by Koin-Payments.
+5. If you wish to modify the identification name to be displayed for the Koin-Payments provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. Click `Save`.
 
 To configure the payment methods to be processed by Koin-Payments, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
 To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-After following the indicated steps, Koin-Payments connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Koin-Payments may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-koin.md b/docs/tutorials/en/setting-up-payments-with-koin.md
index a0030d492..c3cdc301e 100644
--- a/docs/tutorials/en/setting-up-payments-with-koin.md
+++ b/docs/tutorials/en/setting-up-payments-with-koin.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with Koin'
 id: 415vLlrVSUgeYYwycCaGiQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-24T19:48:39.401Z
-updatedAt: 2023-03-29T00:51:56.272Z
-publishedAt: 2023-03-29T00:51:56.272Z
+updatedAt: 2024-03-18T18:30:25.798Z
+publishedAt: 
 firstPublishedAt: 2018-04-24T21:17:23.835Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,8 @@ legacySlug: setting-up-payments-with-koin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 You can set up Koin to receive payments at your store. Through it, your customer chooses the Koin Post-pay payment method to make the purchase.
 
 To set up payments with Koin, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-payments-with-kueski-pay.md b/docs/tutorials/en/setting-up-payments-with-kueski-pay.md
index 64a1121cd..fc15bd414 100644
--- a/docs/tutorials/en/setting-up-payments-with-kueski-pay.md
+++ b/docs/tutorials/en/setting-up-payments-with-kueski-pay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Kueski Pay'
 id: 3jDfBFi33tMC12Ifi8M6X7
 status: PUBLISHED
 createdAt: 2022-08-10T17:09:57.124Z
-updatedAt: 2022-08-10T17:13:39.881Z
-publishedAt: 2022-08-10T17:13:39.881Z
+updatedAt: 2024-01-25T18:14:41.859Z
+publishedAt: 2024-01-25T18:14:41.859Z
 firstPublishedAt: 2022-08-10T17:13:39.881Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: setting-up-payments-with-kueski-pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Kueski Pay payment provider. With this connector, your store can make sales through promissories.
+At VTEX, it is possible to integrate with the Kueski Pay payment provider. With this provider, your store can make sales through Notes Payable.
 
-To set up your Kueski Pay affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
+To set up your Kueski Pay, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
-To set up payment through promissories, access [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-promissory#).
+To set up payment through Notes Payable, access [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable).
 
-After following the indicated steps, Kueski Pay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Kueski Pay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-liquido-payment.md b/docs/tutorials/en/setting-up-payments-with-liquido-payment.md
new file mode 100644
index 000000000..ee266195c
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-liquido-payment.md
@@ -0,0 +1,32 @@
+---
+title: 'Setting up payments with Liquido Payment'
+id: 1GKtFlkdwLqabKAyK6pa3J
+status: PUBLISHED
+createdAt: 2023-09-08T20:08:53.120Z
+updatedAt: 2024-01-23T18:36:25.367Z
+publishedAt: 2024-01-23T18:36:25.367Z
+firstPublishedAt: 2023-09-08T20:28:25.462Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-liquido-payment
+locale: en
+legacySlug: setting-up-payments-with-liquido-payment
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Liquido Payment payment provider. With this provider, your store can make sales through the credit cards and PIX.
+
+To configure Liquido Payment, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __LiquidoPayment__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__ and __Client ID__ fields with the data provided by Liquido Payment.
+5. Click `Save`.
+
+To configure the payment methods to be processed by Liquido Payment, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Liquido Payment connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-mach.md b/docs/tutorials/en/setting-up-payments-with-mach.md
index ae13f67aa..d74122616 100644
--- a/docs/tutorials/en/setting-up-payments-with-mach.md
+++ b/docs/tutorials/en/setting-up-payments-with-mach.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with MACH'
 id: 7h2NpL6p94NSkNFoOhVG4q
 status: PUBLISHED
 createdAt: 2022-10-18T17:01:32.912Z
-updatedAt: 2023-03-21T20:50:53.363Z
-publishedAt: 2023-03-21T20:50:53.363Z
+updatedAt: 2024-01-24T17:56:37.977Z
+publishedAt: 2024-01-24T17:56:37.977Z
 firstPublishedAt: 2022-10-18T17:19:40.370Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-mach
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the MACH payment provider. With this connector, your store can make sales through the MACH.
+At VTEX, it is possible to integrate with the MACH payment provider. With this integration, your store can make sales through the MACH.
 
-To set up MACH affiliation, follow the steps below:
+To set up MACH, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Mach-PayBot__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Mach-PayBot__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by MACH.
 5. Click on `Save`.
 
@@ -33,4 +33,4 @@ To set up MACH affiliation, follow the steps below:
 4. Activate the condition in the __Status__ field.
 5. Click on `Save`.
 
-After following the indicated steps, MACH connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, MACH may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-meliuz.md b/docs/tutorials/en/setting-up-payments-with-meliuz.md
index b110904d6..c127f0b1a 100644
--- a/docs/tutorials/en/setting-up-payments-with-meliuz.md
+++ b/docs/tutorials/en/setting-up-payments-with-meliuz.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Méliuz'
 id: 6ajsvgOtRWnKhmgZjnOmZN
 status: PUBLISHED
 createdAt: 2022-07-19T12:45:45.247Z
-updatedAt: 2023-03-26T21:35:11.618Z
-publishedAt: 2023-03-26T21:35:11.618Z
+updatedAt: 2024-01-23T18:53:00.570Z
+publishedAt: 2024-01-23T18:53:00.570Z
 firstPublishedAt: 2022-07-19T13:15:41.771Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-mercado-pago.md b/docs/tutorials/en/setting-up-payments-with-mercado-pago.md
index 73f201282..278409198 100644
--- a/docs/tutorials/en/setting-up-payments-with-mercado-pago.md
+++ b/docs/tutorials/en/setting-up-payments-with-mercado-pago.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Mercado Pago'
 id: 2FPdhTma6QywUmwEcEUGoS
 status: PUBLISHED
 createdAt: 2018-03-08T21:11:28.158Z
-updatedAt: 2023-03-23T16:02:38.696Z
-publishedAt: 2023-03-23T16:02:38.696Z
+updatedAt: 2024-01-23T11:46:52.226Z
+publishedAt: 2024-01-23T11:46:52.226Z
 firstPublishedAt: 2018-03-08T22:43:32.092Z
 contentType: tutorial
 productTeam: Financial
@@ -23,10 +23,11 @@ In addition to a sub-acquirer that processes transactions carried out with vario
 
 Below are the settings for __Mercado Pago__ connector.
 
-## Setting up MercadoPago gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __MercadoPago__ connector.
+## Setting up MercadoPago gateway
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __MercadoPago__ in the search bar and click on the name of the provider.
 4. Fill in the registration fields with the credentials provided by MercadoPago (fields _Client id_ and _Client secret_). Remember that they should not start with __APP\_USR__.
 5. In the __País__ field ("Country"), select the country of your store.
 6. In __Time Zone__, specify the region that defines your local time.
diff --git a/docs/tutorials/en/setting-up-payments-with-mobbex.md b/docs/tutorials/en/setting-up-payments-with-mobbex.md
new file mode 100644
index 000000000..900a37210
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-mobbex.md
@@ -0,0 +1,34 @@
+---
+title: 'Setting up payments with Mobbex'
+id: 2pgHFFeRRe7LRJOTCWigmh
+status: PUBLISHED
+createdAt: 2023-09-29T12:02:01.214Z
+updatedAt: 2024-01-24T13:31:18.969Z
+publishedAt: 2024-01-24T13:31:18.969Z
+firstPublishedAt: 2023-09-29T12:27:46.314Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-mobbex
+locale: en
+legacySlug: setting-up-payments-with-mobbex
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Mobbex payment provider. With this provider, your store can make sales through credit cards, debit cards and Mobbex.
+
+To configure Mobbex, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Mobbex__ in the search bar and click on the name of the provider.
+4. In __Click to authorize VTEX to make payments__, click on __Authorize__. At this moment, you will be redirected to the Mobbex webpage, where you will have to access your account, and authorize the connection of VTEX in your Mobbex account.
+5. After authorizing, you will automatically return to the VTEX Admin, and the __Application Key__, __Application Token__, __Application Id__ fields will already be filled in.
+6. In __Enable payout split and send payment recipients?__, select whether split payments will be available for the marketplace and sellers.
+7. Click `Save`.
+
+To configure the payment methods to be processed by Mobbex, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Mobbex connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-msc-payment.md b/docs/tutorials/en/setting-up-payments-with-msc-payment.md
new file mode 100644
index 000000000..9665ed41a
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-msc-payment.md
@@ -0,0 +1,51 @@
+---
+title: 'Setting up payments with MSC Payment'
+id: 6hPTXSe57DSCuo7i2r3cjV
+status: PUBLISHED
+createdAt: 2023-09-11T14:04:54.926Z
+updatedAt: 2024-01-25T17:06:19.483Z
+publishedAt: 2024-01-25T17:06:19.483Z
+firstPublishedAt: 2023-09-11T14:17:31.484Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-msc-payment
+locale: en
+legacySlug: setting-up-payments-with-msc-payment
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the MSC Payment payment provider. With this provider, your store can make sales through the MSC Payment.
+
+To configure MSC Payment, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Gateway affiliations__ tab, click on the __"+"__ button.
+3. Click on the __MSC-Payment__ connector.
+4. Fill in the __Application Key__, __Application Token__ and __tasaCambio__ fields with the data provided by MSC Payment.
+5. In the __Payment capture__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use Behavior Recommended By The Payment Processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic Capture Immediately After Payment Authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic Capture Immediately After Anti-fraud Analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic Capture Immediately After Payment Authorization".</li>
+   		<li><b>Scheduled: Schedules The Automatic Capture</b>: By selecting this option, the field <b>Scheduled time frame in hours for automatic capture</b> will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.</li>        
+   		<li><b>Deactivated: Not Automatically Captured</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+
+6. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+
+7. Click on the __Save__ button.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the __+__ button.
+3. Choose the payment condition __MSC Payment__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on __Save__.
+
+After following the indicated steps, MSC Payment may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-netpay-and-netpay-checkout.md b/docs/tutorials/en/setting-up-payments-with-netpay-and-netpay-checkout.md
index 6d5203823..fab7bbde0 100644
--- a/docs/tutorials/en/setting-up-payments-with-netpay-and-netpay-checkout.md
+++ b/docs/tutorials/en/setting-up-payments-with-netpay-and-netpay-checkout.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with NetPay and NetPay Checkout'
 id: 4x03ZhET2ocg9jzx6y482Y
 status: PUBLISHED
 createdAt: 2023-03-02T12:01:13.847Z
-updatedAt: 2023-03-22T17:33:39.076Z
-publishedAt: 2023-03-22T17:33:39.076Z
+updatedAt: 2024-01-25T18:29:38.914Z
+publishedAt: 2024-01-25T18:29:38.914Z
 firstPublishedAt: 2023-03-02T12:47:50.707Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,19 @@ legacySlug: setting-up-payments-with-netpay-and-netpay-checkout
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the NetPay payment provider. With this connector, your store can make sales through bank invoice, credit cards and redirect.
+At VTEX, it is possible to integrate with the NetPay payment provider. With this provider, your store can make sales through bank invoice, credit cards and redirect.
 
-To configure NetPay affiliation, follow the steps below:
+To configure NetPay, follow the steps below:
 
-1. Access the __Admin__ VTEX.
-2. Click on __Payments__.
-3. Then, click on __Settings__.
-4. In the __Gateway affiliations__ tab, click on the `+` button.
-5. Click on one of the connectors, __NetPay__ or __NetPayCheckout__.
-6. Fill in the __Application Key__, __Application Token__ and __Numero del comercio__ fields with data provided by NetPay.
-7. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
-8. Click on `Save`.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __NetPay__ or __NetPayCheckout__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__ and __Numero del comercio__ fields with data provided by NetPay.
+5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+6. Click `Save`.
 
 To configure the payment methods to be processed by NetPay, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
 To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-After following the indicated steps, NetPay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, NetPay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-notes-payable.md b/docs/tutorials/en/setting-up-payments-with-notes-payable.md
new file mode 100644
index 000000000..40a70b788
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-notes-payable.md
@@ -0,0 +1,56 @@
+---
+title: 'Setting up payments with Notes Payable'
+id: 5pW7avTwtyQcMu4uiW8quQ
+status: PUBLISHED
+createdAt: 2018-06-21T20:20:24.484Z
+updatedAt: 2023-10-18T11:58:23.708Z
+publishedAt: 2023-10-18T11:58:23.708Z
+firstPublishedAt: 2018-06-25T15:42:31.515Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: setting-up-payments-with-notes-payable
+locale: en
+legacySlug: setting-up-payments-with-notes-payable
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+On VTEX, your store can receive payments made with __Notes Payable__. To enable this option, you must perform the following steps:
+
+1. [Setting up the gateway affiliation](#setting-up-the-gateway-affiliation)
+2. [Notes Payable setup](#notes-payable-setup)
+3. [Setting up the payment condition](#setting-up-the-payment-condition)
+
+## Setting up the gateway affiliation
+
+To set up a gateway affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
+
+<div class="alert alert-warning">
+Check that the desired gateway affiliation supports Notes Payable payment processing.
+</div>
+
+## Notes Payable Setup
+
+After configuring one of the gateway affiliations listed above, you must configure the __Notes Payable__ custom payment.
+
+1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
+2. Click on the __Custom Payments__ tab.
+3. In __Notes Payable__, click on one of the five configuration boxes.
+4. Fill in the following fields:
+- __Name:__ the name that will be used to identify the payment.
+- __Description:__ details of the payment condition.
+- __Note payable expiration date:__ the due date for your customer to pay the note payable before it expires.
+- __Automatic authorization:__ select whether you want to authorize payments automatically. We recommend enabling this option only for payments on delivery or in-store pickup. By choosing Yes, the order status will automatically change to Handling shipping without requiring payment verification.
+- __Change margin range:__ percentage margin range allowed for changes in the value of the Note Payable. Some customers may want to authorize [changes to orders](https://help.vtex.com/en/tutorial/changing-items-from-a-complete-order--tutorials_190). In this case, please fill in the _Change margin range_ field to determine the percentage margin allowed for changes.
+- __Split payment:__ choose whether to use the [split payment solution](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx). If you opt to use it, the Note Payable will be split between the sellers and the marketplace, when applicable.
+- __Automatic invoicing:__ number of days for the system to invoice the Note Payable after payment authorization. By default, Notes Payable are invoiced upon payment authorization. If this field is set to __Yes__, invoicing will no longer occur upon authorization but after the number of days you have determined.<br>
+
+<ul> 
+5. Click on <b>Save</b>.
+  </ul>
+
+## Setting up the payment condition
+
+After completing the steps above, Notes Payable will be available as a payment method in your store.
+
+Learn how to associate it with a payment condition in our article [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions).
diff --git a/docs/tutorials/en/setting-up-payments-with-nupay.md b/docs/tutorials/en/setting-up-payments-with-nupay.md
index 05dc5e54f..f28d5fa5c 100644
--- a/docs/tutorials/en/setting-up-payments-with-nupay.md
+++ b/docs/tutorials/en/setting-up-payments-with-nupay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Nubank (NuPay)'
 id: 4nVjWfJw7PwraBHCoS45tc
 status: PUBLISHED
 createdAt: 2022-07-19T17:39:57.710Z
-updatedAt: 2023-03-26T21:17:16.116Z
-publishedAt: 2023-03-26T21:17:16.116Z
+updatedAt: 2024-01-23T19:13:04.800Z
+publishedAt: 2024-01-23T19:13:04.800Z
 firstPublishedAt: 2022-07-19T18:24:09.993Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-nuvei.md b/docs/tutorials/en/setting-up-payments-with-nuvei.md
new file mode 100644
index 000000000..d82dab85c
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-nuvei.md
@@ -0,0 +1,69 @@
+---
+title: 'Setting up payments with Nuvei'
+id: 67DjdrpIaZZmhXv9Iwa6Ev
+status: DRAFT
+createdAt: 2024-03-27T12:55:27.016Z
+updatedAt: 2024-03-27T17:47:53.436Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-nuvei
+locale: en
+legacySlug: setting-up-payments-with-nuvei
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with Nuvei. Through this provider, your store can make sales with credit and debit cards.
+
+To use Nuvei, follow the steps below:
+
+- [Configure Nuvei on VTEX](#configuring-nuvei-provider-on-vtex)
+- [Configure the DMN Url in the Cloud](#configurar-dmn-url-in-the-cloud)
+
+## Configuring Nuvei provider on VTEX
+
+<blockquote><ui>1. In the VTEX Admin, go to <b>Store Settings > Payment > Providers</b>, or type <b>Providers</b> in the search bar at the top of the page.</ui>
+
+<blockquote><ui>2. On the providers screen, click the <b>New Provider</b> button.</ui>
+
+<blockquote><ui>3. Type the name <b>nuvei-payment-provider</b> in the search bar and click on the name of the provider.</ui>
+
+<blockquote><ui>4. In <b>Provider Authorization</b>, fill in the <b>App key</b> and <b>App token</b> fields with with your Nuvei account information.</ui>
+
+<blockquote><ui>5. If you wish to modify the identification name to be displayed for the Nuvei provider on the VTEX Admin screen, enter the information in the <b>Name</b> field in <b>Basic Information</b>.</ui>
+
+<blockquote><ui>6. In <b>Payment Control</b>, select whether you want to activate the provider in a test environment by clicking <b>Enable test mode</b>.</ui>
+
+<blockquote><ui>7. To fill in the fields <b>Merchant Id</b>, <b>Merchant Site Id</b> and <b>Client Secret</b> (Secret Key), access the information available in <b>Settings > My Integration Settings</b> within the control panel of your account in the Nuvei environment.</ui>
+
+<blockquote><ui><div class="alert alert-warning">
+ Nuvei has specific credentials (Merchant Id, Merchant Site Id and Client Secret) for each type of environment. Access the test <a href="sandbox.nuvei.com">(Integration)</a> and <a href="cpanel.nuvei.com">Live</a> environments to identify the credentials relating to each of them.
+  </div></blockquote>
+<br>  
+<blockquote><ui>8. In <b>Environment</b>, select whether you want to configure the Nuvei provider in the <b>Integration</b> or <b>Live</b> environment.</ui>
+
+<blockquote><ui>9. In <b>Test 3ds challenge Integration only</b>, if you have selected the test environment (<b>Integration</b>) it is possible to perform 3DS security tests using the <b>Force 3ds Challenge</b>, <b>Force 3ds Frictionless</b> or <b>User cardHolder name</b> options. For more information about the tests, access the <a href="https://docs.nuvei.com/documentation/integration/testing/testing-cards/?highlight=test%20cards#3d-secure-v2-test-scenarios">Nuvei</a> documentation.</ui>
+
+ <blockquote><ui><div class="alert alert-warning">
+   Whenever the provider's <b>Environment</b> is configured as <b>Live</b>, the option selected for the <b>Test 3ds challenge Integration only</b> field must be <b>User cardHolder name</b>.
+  </div></blockquote>
+<br>  
+<blockquote><ui>10. Click <b>Save</b>.</ui>
+
+## Configuring DMN Url on Nuvei
+
+To configure DMN Url information on Nuvei, follow the steps below:
+
+1. Access your Nuvei test environment ([Integration](sandbox.nuvei.com)) or [Live](cpanel.nuvei.com).
+2. On the __Settings__ menu, click __My Integration settings__.
+3. In __DMN URL__, replace the __{account-name}__ field with the name of your VTEX account.
+
+`https://master--{account-name}.myvtex.com/_v/api/nuvei-payment-provider/v0/dmn` 
+
+To configure the payment methods to be processed by Nuvei, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Nuvei provider may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-pagaleve.md b/docs/tutorials/en/setting-up-payments-with-pagaleve.md
index 95d8f2a0e..cda167ee5 100644
--- a/docs/tutorials/en/setting-up-payments-with-pagaleve.md
+++ b/docs/tutorials/en/setting-up-payments-with-pagaleve.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Pagaleve'
 id: 3ro5eb99noG7T4QpoQaJI5
 status: PUBLISHED
 createdAt: 2022-06-22T16:26:18.290Z
-updatedAt: 2023-03-26T21:40:42.801Z
-publishedAt: 2023-03-26T21:40:42.801Z
+updatedAt: 2024-01-23T19:14:42.547Z
+publishedAt: 2024-01-23T19:14:42.547Z
 firstPublishedAt: 2022-06-22T16:33:24.266Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-pagarmev3.md b/docs/tutorials/en/setting-up-payments-with-pagarmev3.md
index 865bf2799..982816803 100644
--- a/docs/tutorials/en/setting-up-payments-with-pagarmev3.md
+++ b/docs/tutorials/en/setting-up-payments-with-pagarmev3.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with PagarMeV3'
 id: 5PMavdamrVijwIrHas9ndE
 status: PUBLISHED
 createdAt: 2022-06-22T17:05:12.930Z
-updatedAt: 2023-03-26T21:02:02.940Z
-publishedAt: 2023-03-26T21:02:02.940Z
+updatedAt: 2024-03-11T14:27:05.534Z
+publishedAt: 2024-03-11T14:27:05.534Z
 firstPublishedAt: 2022-06-22T17:51:37.670Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,21 @@ legacySlug: setting-up-payments-with-pagarmev3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the PagarMeV3 payment provider. With this connector, your store can make sales through credit and debit cards, bank invoice and PIX.
+At VTEX, it is possible to integrate with the PagarMeV3 payment provider. With this provider, your store can make sales through credit and debit cards, bank invoice and PIX.
 
-To configure PagarMeV3 affiliation, follow the steps below:
+To configure PagarMeV3, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __PagarMeV3__ connector.
-4. Fill in the __Application Key__ and __Application Token__ fields with data provided by PagarMeV3.
-5. In __Enable payout split and send payment recipients?__, select whether split payments will be available for the marketplace and sellers.
-6. Click on `Save`.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagarMeV3__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by PagarMeV3.
+5. If you wish to modify the identification name to be displayed for the PagarMeV3 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. If you want to use [payment split](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx) in your store, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
+8. Click `Save`.
 
-To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
+To configure the payment methods to be processed by PagarMeV3, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-After following the indicated steps, PagarMeV3 connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PagarMeV3 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-pagbrasilv2.md b/docs/tutorials/en/setting-up-payments-with-pagbrasilv2.md
new file mode 100644
index 000000000..b89221619
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-pagbrasilv2.md
@@ -0,0 +1,40 @@
+---
+title: 'Setting up payments with PagBrasilV2'
+id: 5ONHAWmRbZpNIDPXCkNJXD
+status: PUBLISHED
+createdAt: 2024-03-13T16:31:07.244Z
+updatedAt: 2024-03-13T22:24:02.876Z
+publishedAt: 2024-03-13T22:24:02.876Z
+firstPublishedAt: 2024-03-13T22:21:24.967Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: setting-up-payments-with-pagbrasilv2
+locale: en
+legacySlug: setting-up-payments-with-pagbrasilv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the payment provider PagBrasilV2. Through this provider, your store can make sales using debit and credit cards, bank slips, notes payable and PIX.
+
+To configure PagBrasilV2, follow the steps below:
+
+1. In the VTEX Admin, access __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New provider` button.
+3. Type the name __PagBrasil-v2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App Token__ fields with your PagBrasilV2 account information.
+5. If you wish to modify the identification name to be displayed for the PagBrasilV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __External Service Url__, enter the external URL that will be associated with `/pvt/payments?an={AccountName}`.
+7. In __Implements Installments Service__, select whether you want to use external installment services or what is configured in the portal. If you choose the __Yes__ option, the system will use the URL configured in the __Installments Service Url__ field.
+8. In __External Cancellation Service__, select whether an external cancellation service should be used. If you choose the __Yes__ option, the system will access the URL configured in the __External Service Url__ field.
+9. In __Installments Service Url__, enter the external URL that will be associated with `/options`.
+10. In __SoftDescriptor__, indicate what information should appear to identify the transaction carried out in your store.
+11. In __Captura antecipada__ (Early capture), choose how long you want the capture to be carried out (after transaction approval and anti-fraud analysis). This function can also be deactivated.
+12. In __Do you have an anti-fraud agent hired with this affiliation?__, indicate whether you want to use an anti-fraud agent.
+13. Click __Save__.
+
+To configure the payment methods to be processed by PagBrasilV2, access [Configuring payment vonditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PagBrasilV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-paghiperv2.md b/docs/tutorials/en/setting-up-payments-with-paghiperv2.md
new file mode 100644
index 000000000..bd2486fbe
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-paghiperv2.md
@@ -0,0 +1,36 @@
+---
+title: 'Setting up payments with PagHiperV2'
+id: 131E6zBcTTkzZtL82cZh1x
+status: PUBLISHED
+createdAt: 2024-03-14T12:01:07.521Z
+updatedAt: 2024-03-14T12:18:12.256Z
+publishedAt: 2024-03-14T12:18:12.256Z
+firstPublishedAt: 2024-03-14T12:18:12.256Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-paghiperv2
+locale: en
+legacySlug: setting-up-payments-with-paghiperv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PagHiperV2 payment provider. With this provider, your store can make sales through bank invoices and PIX.
+
+To configure PagHiperV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagHiperV2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by PagHiperV2.
+5. If you wish to modify the identification name to be displayed for the PagHiperV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Limite Vencimento__, enter how many days the bank invoice will remain open after its expiration date.
+7. In __Exibir Frase fixa__, select whether you want to include a phrase to be displayed on the bank invoices issued.
+8. In __Frase variável do vendedor__, if desired, configure the phrase to be displayed for each specific bank invoice.
+9. Click `Save`.
+
+To configure the payment methods to be processed by PagHiperV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PagHiperV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-paghiperv3.md b/docs/tutorials/en/setting-up-payments-with-paghiperv3.md
new file mode 100644
index 000000000..cb44d2a5e
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-paghiperv3.md
@@ -0,0 +1,38 @@
+---
+title: 'Setting up payments with PagHiperV3'
+id: 1dYVbSK0yHNY5vp0gJj4fC
+status: PUBLISHED
+createdAt: 2024-03-14T12:27:03.520Z
+updatedAt: 2024-03-14T12:39:32.791Z
+publishedAt: 2024-03-14T12:39:32.791Z
+firstPublishedAt: 2024-03-14T12:39:32.791Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-paghiperv3
+locale: en
+legacySlug: setting-up-payments-with-paghiperv3
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PagHiperV3 payment provider. With this provider, your store can make sales through bank invoices and PIX.
+
+To configure PagHiperV3, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagHiperV3__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by PagHiperV3.
+5. If you wish to modify the identification name to be displayed for the PagHiperV3 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In __Limite Vencimento__, enter how many days the bank invoice will remain open after its expiration date.
+8. In __Dias corridos até o vencimento__, enter the maximum expiration date for the bank invoices. For PIX payments, it is not possible to change the expiration period, the default period is 15 minutes.
+9. In __Exibir Frase fixa__, select whether you want to include a phrase to be displayed on the bank invoices issued.
+10. In __Frase variável do vendedor__, if desired, configure the phrase to be displayed for each specific bank invoice.
+11. Click `Save`.
+
+To configure the payment methods to be processed by PagHiperV3, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PagHiperV3 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-pagoefectivo.md b/docs/tutorials/en/setting-up-payments-with-pagoefectivo.md
index 5426a22c2..ca0e3fa0c 100644
--- a/docs/tutorials/en/setting-up-payments-with-pagoefectivo.md
+++ b/docs/tutorials/en/setting-up-payments-with-pagoefectivo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with PagoEfectivo'
 id: 1GGyNqZSYE2a8ga4UemYyw
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-09T20:26:14.388Z
-updatedAt: 2021-06-17T18:59:09.202Z
-publishedAt: 2021-06-17T18:59:09.202Z
+updatedAt: 2024-03-18T19:11:11.066Z
+publishedAt: 
 firstPublishedAt: 2018-04-09T21:57:41.363Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-pagoefectivov2.md b/docs/tutorials/en/setting-up-payments-with-pagoefectivov2.md
new file mode 100644
index 000000000..17fa73fc0
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-pagoefectivov2.md
@@ -0,0 +1,55 @@
+---
+title: 'Setting up payments with PagoEfectivoV2'
+id: 63Raoh7hlWoWbMJOAacfMV
+status: PUBLISHED
+createdAt: 2024-02-06T11:22:25.720Z
+updatedAt: 2024-03-13T15:08:00.716Z
+publishedAt: 2024-03-13T15:08:00.716Z
+firstPublishedAt: 2024-02-06T11:40:45.294Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-pagoefectivov2
+locale: en
+legacySlug: setting-up-payments-with-pagoefectivov2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PagoEfectivoV2 payment provider. With this provider, your store can make sales through Cuotealo and PagoEfectivo.
+
+To configure PagoEfectivoV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagoEfectivoV2__ in the search bar and click on the name of the provider.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account PagoEfectivoV2.
+5. If you wish to modify the identification name to be displayed for the PagoEfectivoV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. In __Provider Fields__, enter the __TradeID__, __TradeName__, __TradeEmail__ and __MaxActiveCipTime__ information according to your PagoEfectivoV2 account information.
+
+9. In __Country__, select the country where the payment transaction will be carried out.
+
+10. In __Currency__, select the currency to be used in the payment transaction.
+
+11. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __PagoEfectivo__ or __Cuotealo__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, PagoEfectivoV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-pagoexpress.md b/docs/tutorials/en/setting-up-payments-with-pagoexpress.md
new file mode 100644
index 000000000..0002cb37d
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-pagoexpress.md
@@ -0,0 +1,40 @@
+---
+title: 'Setting up payments with PagoExpress'
+id: 4VmPz20GbXZ1gMKPaJ09l0
+status: PUBLISHED
+createdAt: 2024-02-05T19:13:06.972Z
+updatedAt: 2024-03-13T15:13:51.485Z
+publishedAt: 2024-03-13T15:13:51.485Z
+firstPublishedAt: 2024-02-05T20:10:35.385Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-pagoexpress
+locale: en
+legacySlug: setting-up-payments-with-pagoexpress
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PagoExpress payment provider. With this provider, your store can make sales through PIX.
+
+To configure PagoExpress, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PagoExpress__ in the search bar and click on the name of the provider.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account PagoExpress.
+5. If you wish to modify the identification name to be displayed for the PagoExpress provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __PIX__.
+4. Activate the condition in the __Status__ field. 
+5. In __Process with affiliation__, select the __pagoexpresspartnerbr-pagoexpress-v0__ option.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, PagoExpress may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-pagosweb.md b/docs/tutorials/en/setting-up-payments-with-pagosweb.md
index d74a5e5c9..857427023 100644
--- a/docs/tutorials/en/setting-up-payments-with-pagosweb.md
+++ b/docs/tutorials/en/setting-up-payments-with-pagosweb.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with PagosWEB'
 id: 2qKIeEPUBKqEGo2OyikyQw
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-05T15:48:50.151Z
-updatedAt: 2023-03-29T01:06:09.900Z
-publishedAt: 2023-03-29T01:06:09.900Z
+updatedAt: 2024-03-18T19:12:24.950Z
+publishedAt: 
 firstPublishedAt: 2018-04-05T22:01:49.141Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-payments-with-pagosweb
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 You can set up PagosWEB to receive payments in your store. With it, your customer chooses PaymentsWEB __payment method__ to make the purchase.
 
 To enable payments with PagosWEB, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-payments-with-parcelex.md b/docs/tutorials/en/setting-up-payments-with-parcelex.md
index 81754482f..7d75c04ca 100644
--- a/docs/tutorials/en/setting-up-payments-with-parcelex.md
+++ b/docs/tutorials/en/setting-up-payments-with-parcelex.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Parcelex'
 id: 2CqB2f1A8pxaAFyk8lxbzy
 status: PUBLISHED
 createdAt: 2022-06-22T19:16:08.714Z
-updatedAt: 2023-03-26T21:40:05.111Z
-publishedAt: 2023-03-26T21:40:05.111Z
+updatedAt: 2024-01-23T21:03:35.230Z
+publishedAt: 2024-01-23T21:03:35.230Z
 firstPublishedAt: 2022-06-22T19:19:11.694Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-pay4fun.md b/docs/tutorials/en/setting-up-payments-with-pay4fun.md
new file mode 100644
index 000000000..bd8ed8176
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-pay4fun.md
@@ -0,0 +1,40 @@
+---
+title: 'Setting up payments with Pay4Fun'
+id: 7xCpO35RMDRcp1UCvOGZX3
+status: PUBLISHED
+createdAt: 2024-02-05T14:53:57.694Z
+updatedAt: 2024-03-13T15:15:38.399Z
+publishedAt: 2024-03-13T15:15:38.399Z
+firstPublishedAt: 2024-02-05T15:29:05.357Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-pay4fun
+locale: en
+legacySlug: setting-up-payments-with-pay4fun
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Pay4Fun payment provider. With this provider, your store can make sales through PIX.
+
+To configure Pay4Fun, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Pay4Fun__ in the search bar and click on the name of the provider.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account Pay4Fun.
+5. If you wish to modify the identification name to be displayed for the Pay4Fun provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __PIX__.
+4. Activate the condition in the __Status__ field. 
+5. In __Process with affiliation__, select the __p4fpartnerbr-pay4fun-v0__ option.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, Pay4Fun may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-paycash.md b/docs/tutorials/en/setting-up-payments-with-paycash.md
index d6d95d905..e360f1db3 100644
--- a/docs/tutorials/en/setting-up-payments-with-paycash.md
+++ b/docs/tutorials/en/setting-up-payments-with-paycash.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Paycash'
 id: 5gxrb0YlEhq0JnprN2uaOf
 status: PUBLISHED
 createdAt: 2023-04-06T17:19:09.254Z
-updatedAt: 2023-04-06T17:57:16.146Z
-publishedAt: 2023-04-06T17:57:16.146Z
+updatedAt: 2024-01-23T21:05:57.921Z
+publishedAt: 2024-01-23T21:05:57.921Z
 firstPublishedAt: 2023-04-06T17:40:32.746Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-paycash
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Paycash payment provider. With this connector, your store can make sales through Paycash.
+At VTEX, it is possible to integrate with the Paycash payment provider. With this provider, your store can make sales through Paycash.
 
-To configure Paycash affiliation, follow the steps below:
+To configure Paycash, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Paycash__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Paycash__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__, __Application Token__ and __Paycash Production Api Key__ fields with data provided by Paycash.
 5. In the __Payment settlement__ field, select one of the available options:
 
diff --git a/docs/tutorials/en/setting-up-payments-with-payclub.md b/docs/tutorials/en/setting-up-payments-with-payclub.md
index 2ddf29e75..2f1790a30 100644
--- a/docs/tutorials/en/setting-up-payments-with-payclub.md
+++ b/docs/tutorials/en/setting-up-payments-with-payclub.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with PayClub'
 id: 3C3bDia3Tyq48MOuMomcUW
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-03T13:12:17.337Z
-updatedAt: 2023-03-28T00:07:06.076Z
-publishedAt: 2023-03-28T00:07:06.076Z
+updatedAt: 2024-03-18T19:14:09.539Z
+publishedAt: 
 firstPublishedAt: 2018-04-03T15:07:32.416Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-payments-with-payclub
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 You can configure PayClub [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) to receive payments at your store. With it, your client chooses the __payment method__ PayClub and performs the authentication in the external environment of the payment solution.
 
 To enable PayClub payments, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-payments-with-paymentezv2.md b/docs/tutorials/en/setting-up-payments-with-paymentezv2.md
new file mode 100644
index 000000000..e98cfd50c
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-paymentezv2.md
@@ -0,0 +1,34 @@
+---
+title: 'Setting up payments with PaymentezV2'
+id: 6MQiFTLnSaQoCswRUN1SVe
+status: PUBLISHED
+createdAt: 2024-03-14T12:48:31.013Z
+updatedAt: 2024-03-14T13:10:44.458Z
+publishedAt: 2024-03-14T13:10:44.458Z
+firstPublishedAt: 2024-03-14T13:10:44.458Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-paymentezv2
+locale: en
+legacySlug: setting-up-payments-with-paymentezv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PaymentezV2 payment provider. With this provider, your store can make sales through TuyaPay, cards (credit, private label, co-branded) and notes payable.
+
+To configure PaymentezV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PaymentezV2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by PaymentezV2.
+5. If you wish to modify the identification name to be displayed for the PaymentezV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. Click `Save`.
+
+To configure the payment methods to be processed by PaymentezV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PaymentezV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-paypalv2.md b/docs/tutorials/en/setting-up-payments-with-paypalv2.md
new file mode 100644
index 000000000..735790aa3
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-paypalv2.md
@@ -0,0 +1,43 @@
+---
+title: 'Setting up payments with PayPalV2'
+id: 2nGiQVk3YKvOAu8Zg4RKFr
+status: PUBLISHED
+createdAt: 2024-03-14T18:53:09.449Z
+updatedAt: 2024-07-24T19:40:23.978Z
+publishedAt: 2024-07-24T19:40:23.978Z
+firstPublishedAt: 2024-03-14T19:02:53.958Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-paypalv2
+locale: en
+legacySlug: setting-up-payments-with-paypalv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the payment provider PayPalV2. Through this provider, your store can make sales via PayPalCP and PayPal.
+
+To configure PayPalV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __paypal-v2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ fields with data provided by PayPalV2. In the Paypal environment, the __App key__ corresponds to the __Client ID__, and the __App token__ refers to the __Secret__.
+5. If you wish to modify the identification name to be displayed for the PayPalV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In __Automatic Settlement__ field, select one of the following options:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. Click __Save__.
+
+To configure the payment methods to be processed by PayPalV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PayPalV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-payu-india.md b/docs/tutorials/en/setting-up-payments-with-payu-india.md
index 2db9b4a65..58342b979 100644
--- a/docs/tutorials/en/setting-up-payments-with-payu-india.md
+++ b/docs/tutorials/en/setting-up-payments-with-payu-india.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with PayU India'
 id: 7JFaP3jBukdZHWel9p7dKX
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-08-15T12:33:46.519Z
-updatedAt: 2023-03-21T20:56:57.589Z
-publishedAt: 2023-03-21T20:56:44.797Z
+updatedAt: 2024-01-25T19:21:08.479Z
+publishedAt: 2024-01-25T19:21:08.479Z
 firstPublishedAt: 2022-08-15T14:38:06.151Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,18 @@ legacySlug: setting-up-payments-with-payu-india
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the PayU India payment provider. With this connector, your store can make sales through credit cards and promissories.
+At VTEX, it is possible to integrate with the PayU India payment provider. With this provider, your store can make sales through credit cards and Notes Payable.
 
-To configure PayU India affiliation, follow the steps below:
+To configure PayU India, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __+__ button.
-3. Click on the __PayuIndia__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PayuIndia__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__, __Application Token__, __Public API Key__, __Soft descriptor__ and __Type of refund__ fields with data provided by PayU India.
 5. In the __Early capture__ field, choose how long you want the capture to take place (after transaction approval and anti-fraud review). You can also disable the function.
 6. In __Have an anti-fraud deal with this affiliation?__, select whether your store will use an anti-fraud deal with this connector.
-7. Click on __Save__.
+7. Click `Save`.
 
 To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento).
 
-After following the indicated steps, PayU India connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, PayU India may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-payuv2.md b/docs/tutorials/en/setting-up-payments-with-payuv2.md
new file mode 100644
index 000000000..06f459ba4
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-payuv2.md
@@ -0,0 +1,48 @@
+---
+title: 'Setting up payments with PayUv2'
+id: 7twMgKUZZtJGmR72wS1k3n
+status: PUBLISHED
+createdAt: 2024-03-08T18:30:40.587Z
+updatedAt: 2024-03-13T15:35:06.533Z
+publishedAt: 2024-03-13T15:35:06.533Z
+firstPublishedAt: 2024-03-08T18:47:05.125Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-payuv2
+locale: en
+legacySlug: setting-up-payments-with-payuv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PayUv2 payment provider. With this provider, your store can make sales through cards (credit, debit, private label, cob-branded), notes payable and bank slips.
+
+To configure PayUv2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PayUv2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ fields with data provided by your account PayUv2.
+5. If you wish to modify the identification name to be displayed for the PayUv2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. If you want to use [payment split](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx) in your store, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
+9. In __Provider Fields__, in the __Tipo Authorizacion__ field, select whether your payment transactions are executed in one- or two-step flows. For one-step flows, select __Autorizacion y Captura__. For two-step flows, select __Pre-Autorizacion__.
+10. In __Public Key__, enter your PayU API key.
+11. In __Idioma__, select which language should be used in the PayU system.
+12. In __Expiración pago (días)__, select the period in which you want to configure the expiration of payments made by notes payable.
+13. Click `Save`.
+
+To configure the payment methods to be processed by PayUv2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PayUv2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-payway.md b/docs/tutorials/en/setting-up-payments-with-payway.md
new file mode 100644
index 000000000..194d1b655
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-payway.md
@@ -0,0 +1,37 @@
+---
+title: 'Setting up payments with Payway'
+id: wHkvX7olfPPsAdeFq7obp
+status: PUBLISHED
+createdAt: 2024-03-07T17:04:59.563Z
+updatedAt: 2024-03-13T15:29:48.955Z
+publishedAt: 2024-03-13T15:29:48.955Z
+firstPublishedAt: 2024-03-07T19:10:55.092Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-payway
+locale: en
+legacySlug: setting-up-payments-with-payway
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Payway payment provider. With this provider, your store can make sales through PayWay, cards (credit, debit, private label, co-branded), notes payable and bank slips.
+
+To configure Payway, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Payway__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ fields with data provided by your account Payway.
+5. If you wish to modify the identification name to be displayed for the Payway provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In __Provider Fields__, enter the __User ID__, __Consume Username (PUBLIC)__ and __Consume Username (PRIVATE)__ information according to your Payway account information.
+8. In __Payment type__, select the option __Simple Payment__ or __Two Steps Payment__.
+9. In __Do you use Cybersource?__, select whether you want to use Cybersource as your anti-fraud provider.
+10. Click `Save`.
+
+To configure the payment methods to be processed by Payway, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Payway may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-picpay.md b/docs/tutorials/en/setting-up-payments-with-picpay.md
index 21060709b..d53349bc2 100644
--- a/docs/tutorials/en/setting-up-payments-with-picpay.md
+++ b/docs/tutorials/en/setting-up-payments-with-picpay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with PicPay'
 id: 5jd6wgPCaWm8IcguyCyaY2
 status: PUBLISHED
 createdAt: 2018-03-13T15:53:25.279Z
-updatedAt: 2023-03-29T01:02:29.955Z
-publishedAt: 2023-03-29T01:02:29.955Z
+updatedAt: 2024-01-23T21:16:28.952Z
+publishedAt: 2024-01-23T21:16:28.952Z
 firstPublishedAt: 2018-03-13T19:36:37.769Z
 contentType: tutorial
 productTeam: Financial
@@ -17,16 +17,16 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 PicPay is a [digital wallet](/en/faq/what-is-an-e-wallet) that allows transfers between users, including merchants. Your customer chooses to pay with it and receives a code to scan using the smartphone application.
 
-To set up payments with this digital wallet, you first need to register __PicPay__ gateway affiliation by following the steps below:
+To configure PicPay, follow the steps below:
 
-## Setting up PicPay gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __PicPay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PicPay__ in the search bar and click on the name of the provider.
 4. Fill in the _Application Key_ and _Application Token_ fields with your __PicPay__ account information.
-5. Click __Save__.
+5. Click `Save`.
 
 ## Setting up the payment condition
+
 1. Within Payments __Settings__, click on the __Payment Conditions__ tab.
 2. Click the __+__ button.
 3. Select __PicPay__ payment method.
diff --git a/docs/tutorials/en/setting-up-payments-with-pine-labs.md b/docs/tutorials/en/setting-up-payments-with-pine-labs.md
index 531924e4e..ccc0da19b 100644
--- a/docs/tutorials/en/setting-up-payments-with-pine-labs.md
+++ b/docs/tutorials/en/setting-up-payments-with-pine-labs.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Pine Labs'
 id: 6cmZ0Qs9HUpN7AUBZQDmc0
 status: PUBLISHED
 createdAt: 2023-04-03T17:01:53.868Z
-updatedAt: 2023-04-14T12:48:59.843Z
-publishedAt: 2023-04-14T12:48:59.843Z
+updatedAt: 2024-01-25T19:11:09.123Z
+publishedAt: 2024-01-25T19:11:09.123Z
 firstPublishedAt: 2023-04-03T17:17:06.240Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,19 @@ legacySlug: setting-up-payments-with-pine-labs
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Pine Labs payment provider. With this connector, your store can make sales through credit cards, bank invoice and promissories.
+At VTEX, it is possible to integrate with the Pine Labs payment provider. With this provider, your store can make sales through credit cards, bank invoice and Notes Payable.
 
-To configure Pine Labs affiliation, follow the steps below:
+To configure Pine Labs, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Pinelabs connector__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Pinelabs connector__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account Pine Labs.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
-6. Click on `Save`.
+6. Click `Save`.
 
 To configure the payment methods to be processed by Pine Labs, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
 To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-After following the indicated steps, Pine Labs connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Pine Labs may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-poolpay.md b/docs/tutorials/en/setting-up-payments-with-poolpay.md
new file mode 100644
index 000000000..da6133443
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-poolpay.md
@@ -0,0 +1,33 @@
+---
+title: 'Setting up payments with PoolPay'
+id: 5N3llK2tpVPKdfJvOIJmQ0
+status: PUBLISHED
+createdAt: 2023-09-11T14:36:06.412Z
+updatedAt: 2024-01-25T17:26:19.086Z
+publishedAt: 2024-01-25T17:26:19.086Z
+firstPublishedAt: 2023-09-11T14:58:37.086Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-poolpay
+locale: en
+legacySlug: setting-up-payments-with-poolpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the PoolPay payment provider. With this provider, your store can make sales through the credit cards, PIX, ITP (Brazilian payment transaction initiator) and BNPL (Buy Now Pay Later).
+
+To configure PoolPay, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PoolPay__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__ and __Application Token__ fields with the data provided by Liquido Payment.
+5. In __Enable payout split and sending payment recipients?__, select whether split payments will be available for the marketplace and sellers.
+6. Click on the `Save` button.
+
+To configure the payment methods to be processed by PoolPay, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, PoolPay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-powerpay.md b/docs/tutorials/en/setting-up-payments-with-powerpay.md
new file mode 100644
index 000000000..a9d6a9e1d
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-powerpay.md
@@ -0,0 +1,50 @@
+---
+title: 'Setting up payments with Powerpay'
+id: 4v3ohBfSTxIyi06aqvlrPp
+status: PUBLISHED
+createdAt: 2023-09-08T18:31:43.851Z
+updatedAt: 2024-01-23T21:22:03.339Z
+publishedAt: 2024-01-23T21:22:03.339Z
+firstPublishedAt: 2023-09-08T19:50:37.486Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-powerpay
+locale: en
+legacySlug: setting-up-payments-with-powerpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Powerpay payment provider. With this provider, your store can make sales through the Powerpay.
+
+To configure Powerpay, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Powerpay__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__, __secretKey__ and __merchant_id__ fields with the data provided by Powerpay.
+5. In the __Payment capture__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use Behavior Recommended By The Payment Processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic Capture Immediately After Payment Authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic Capture Immediately After Anti-fraud Analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic Capture Immediately After Payment Authorization".</li>
+   		<li><b>Scheduled: Schedules The Automatic Capture</b>: By selecting this option, the field <b>Scheduled time frame in hours for automatic capture</b> will be displayed, and it must be completed with the period in which the automatic capture will take place. This period must be in accordance with the limits allowed by the payment provider.</li>        
+   		<li><b>Deactivated: Not Automatically Captured</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+6. In __Enable payout split and sending payment recipients?__, select whether split payments will be available for the marketplace and sellers.
+
+7. Click on the __Save__ button.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings__ > __Payment__ > __Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the __+__ button.
+3. Choose the payment condition __Powerpay__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on __Save__.
+
+After following the indicated steps, Powerpay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-puntos-colombia.md b/docs/tutorials/en/setting-up-payments-with-puntos-colombia.md
index 20df86161..dc40ed476 100644
--- a/docs/tutorials/en/setting-up-payments-with-puntos-colombia.md
+++ b/docs/tutorials/en/setting-up-payments-with-puntos-colombia.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Puntos Colombia'
 id: 5lj66uK0w5XxfzfncEyhP6
 status: PUBLISHED
 createdAt: 2022-03-17T14:14:06.885Z
-updatedAt: 2023-03-26T21:55:55.409Z
-publishedAt: 2023-03-26T21:55:55.409Z
+updatedAt: 2024-01-25T17:08:21.898Z
+publishedAt: 2024-01-25T17:08:21.898Z
 firstPublishedAt: 2022-03-17T14:23:01.073Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-puntos-colombia
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Puntos Colombia payment provider. With this connector, your store can make sales through the Puntos Colombia loyalty program.
+At VTEX, it is possible to integrate with the Puntos Colombia payment provider. With this provider, your store can make sales through the Puntos Colombia loyalty program.
 
-To configure Puntos Colombia affiliation, follow the steps below:
+To configure Puntos Colombia, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the __+__ button.
-3. Click on the __PuntosColombia__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PuntosColombia__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Puntos Colombia.
 5. Click on __Save__.
 
@@ -36,4 +36,4 @@ To configure Puntos Colombia affiliation, follow the steps below:
 7. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
 8. Click on __Save__.
 
-After following the indicated steps, Puntos Colombia connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Puntos Colombia may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-qhantuy.md b/docs/tutorials/en/setting-up-payments-with-qhantuy.md
index cca8bbda5..44810276a 100644
--- a/docs/tutorials/en/setting-up-payments-with-qhantuy.md
+++ b/docs/tutorials/en/setting-up-payments-with-qhantuy.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Qhantuy'
 id: 4KO2beK0scqVy4lrrs3Myq
 status: PUBLISHED
 createdAt: 2023-04-20T13:44:39.377Z
-updatedAt: 2023-04-20T17:36:03.040Z
-publishedAt: 2023-04-20T17:36:03.040Z
+updatedAt: 2024-01-24T17:10:50.292Z
+publishedAt: 2024-01-24T17:10:50.292Z
 firstPublishedAt: 2023-04-20T14:12:44.589Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-qhantuy
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Qhantuy payment provider. With this connector, your store can make sales through credit cards and Qhantuy.
+At VTEX, it is possible to integrate with the Qhantuy payment provider. With this provider, your store can make sales through credit cards and Qhantuy.
 
-To configure Qhantuy affiliation, follow the steps below:
+To configure Qhantuy, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Qhantuy__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Qhantuy__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Qhantuy.
 5. In the __Payment settlement__ field, select one of the available options:
 
@@ -35,7 +35,7 @@ To configure Qhantuy affiliation, follow the steps below:
 
 <ui>  7. If an alert message appears indicating the need to install the app, click on the <b>Install app</b> button and follow the installation instructions.</ui>
 
-<ui>  8. Click on <b>Save.</b></ui>
+<ui>  8. Click <b>Save.</b></ui>
 
 To configure the payment methods to be processed by Qhantuy, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
diff --git a/docs/tutorials/en/setting-up-payments-with-retrypay.md b/docs/tutorials/en/setting-up-payments-with-retrypay.md
index 03723295a..9a4153d0a 100644
--- a/docs/tutorials/en/setting-up-payments-with-retrypay.md
+++ b/docs/tutorials/en/setting-up-payments-with-retrypay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Retrypay'
 id: 3QGioVKVI1Qnk3JbbJlJVY
 status: PUBLISHED
 createdAt: 2023-03-30T19:35:06.661Z
-updatedAt: 2023-03-30T20:01:51.283Z
-publishedAt: 2023-03-30T20:01:51.283Z
+updatedAt: 2024-02-08T14:23:02.038Z
+publishedAt: 2024-02-08T14:23:02.038Z
 firstPublishedAt: 2023-03-30T20:01:51.283Z
 contentType: tutorial
 productTeam: Financial
@@ -15,31 +15,31 @@ legacySlug: setting-up-payments-with-retrypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Retrypay payment provider. With this connector, your store can make sales through promissory and Retrypay.
+At VTEX, it is possible to integrate with the Retrypay payment provider. With this provider, your store can make sales through Notes Payable and Retrypay.
 
-To configure Retrypay affiliation, follow the steps below:
+To configure Retrypay, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Retrypay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __RetryPay__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__, __Application Token__, __Tenant__, __Retripay Merchant API Key__ and __Retripay Hook Token__ fields with data provided by Retrypay.
 5. Under __Payment Method__, choose one of two options: __Redirect__ or __Payment App__.
 6. Under __Environment__, choose one of two options: __Demo__ or __Production__.
-7. Click on `Save`.
+7. Click `Save`.
 
-## Setting up payment condition Promissory
+## Setting up payment condition Notes Payable
 
-If you want to use Retrypay with a promissory note and you have not yet configured the promissory note as a payment method in other connectors in your store, go to [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-promissory--5pW7avTwtyQcMu4uiW8quQ).
+If you want to use Retrypay with a Notes Payable and you have not yet configured the Notes Payable as a payment method in other providers in your store, go to [Setting up payments with Promissory](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable).
 
 Then, follow the steps below:
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. In the __Payment Conditions__ tab, click on the `+` button.
-3. On __Custom Payment__, click the button corresponding to the name used for the promissory note payment method (configured in the previous section).
+3. On __Custom Payment__, click the button corresponding to the name used for the Notes Payable payment method (configured in the previous section).
 4. Activate the condition in the __Status__ field.
 5. On __Process with affiliation__, select __retrypaypartnermx-payment-provider-v1__.
-6. If you wish, you can also configure [payment special conditionso](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
-7. Click on `Save`.
+6. If you wish, you can also configure [payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+7. Click `Save`.
 
 ## Setting up payment condition Retrypay
 
@@ -49,6 +49,6 @@ Then, follow the steps below:
 4. Activate the condition in the __Status__ field.
 5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
 6. If you wish, you can also configure [payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
-7. Click on `Save`.
+7. Click `Save`.
 
-After following the indicated steps, Retrypay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Retrypay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-safetypayv2.md b/docs/tutorials/en/setting-up-payments-with-safetypayv2.md
new file mode 100644
index 000000000..35114ef84
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-safetypayv2.md
@@ -0,0 +1,33 @@
+---
+title: 'Setting up payments with SafetyPayV2'
+id: 5VBwbJODDKJ6zIW5a23l8V
+status: PUBLISHED
+createdAt: 2024-03-14T17:24:16.678Z
+updatedAt: 2024-03-14T17:44:09.769Z
+publishedAt: 2024-03-14T17:44:09.769Z
+firstPublishedAt: 2024-03-14T17:41:17.188Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-safetypayv2
+locale: en
+legacySlug: setting-up-payments-with-safetypayv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the SafetyPayV2 payment provider. With this provider, your store can make sales through Safetypay y Lottery.
+
+To configure SafetyPayV2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __SafetyPayV2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by SafetyPayV2.
+5. If you wish to modify the identification name to be displayed for the SafetyPayV2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
+
+To configure the payment methods to be processed by SafetyPayV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, SafetyPayV2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-scalapay.md b/docs/tutorials/en/setting-up-payments-with-scalapay.md
index cbe86a60c..bfbe963e2 100644
--- a/docs/tutorials/en/setting-up-payments-with-scalapay.md
+++ b/docs/tutorials/en/setting-up-payments-with-scalapay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Scalapay'
 id: 6SCh3WUqjeqIrOl209MENA
 status: PUBLISHED
 createdAt: 2022-08-12T19:31:38.569Z
-updatedAt: 2023-05-09T14:07:50.542Z
-publishedAt: 2023-05-09T14:07:50.542Z
+updatedAt: 2024-01-25T18:03:45.856Z
+publishedAt: 2024-01-25T18:03:45.856Z
 firstPublishedAt: 2022-08-12T19:39:58.598Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: setting-up-payments-with-scalapay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Scalapay payment provider. With this connector, your store can make sales through credit card and Scalapay.
+At VTEX, it is possible to integrate with the Scalapay payment provider. With this provider, your store can make sales through credit card and Scalapay.
 
-To configure Scalapay affiliation, follow the steps below:
+To configure Scalapay, follow the steps below:
 
-<ui>1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.</ui>
+<ui>1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.</ui>
 
-<ui>2. In the __Gateway affiliations__ tab, click on the __+__ button.</ui>
+<ui>2. On the providers screen, click the `New Provider` button.</ui>
 
-<ui>3. Click on the __Scalapay__ connector.</ui>
+<ui>3. Type the name __Scalapay__ in the search bar and click on the name of the provider.</ui>
 
 <ui>4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Scalapay.</ui>
 
@@ -34,8 +34,8 @@ To configure Scalapay affiliation, follow the steps below:
  - __Automatic Capture Immediately After Anti-fraud Analysis__:  Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in __Automatic Capture Immediately After Payment Authorization__.  
  - __Deactivated: Not Automatically Captured__: capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.
 
-<ui>6.Click on __Save__.</ui>
+<ui>6.Click `Save`.</ui>
 
 To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/condicoes-de-pagamento). For the credit card option, select the __vtex-integration-scalapay-v0__ affiliation.
 
-After following the indicated steps, Scalapay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Scalapay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-shipay.md b/docs/tutorials/en/setting-up-payments-with-shipay.md
index 081c72797..a58d42653 100644
--- a/docs/tutorials/en/setting-up-payments-with-shipay.md
+++ b/docs/tutorials/en/setting-up-payments-with-shipay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Shipay'
 id: 2GVBCDdxZPexI2TikFf9Au
 status: PUBLISHED
 createdAt: 2023-03-27T14:40:05.161Z
-updatedAt: 2023-03-27T16:15:57.347Z
-publishedAt: 2023-03-27T16:15:57.347Z
+updatedAt: 2024-01-23T21:27:19.732Z
+publishedAt: 2024-01-23T21:27:19.732Z
 firstPublishedAt: 2023-03-27T14:44:22.502Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-shipay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Shipay payment provider. With this connector, your store can make sales through PIX.
+At VTEX, it is possible to integrate with the Shipay payment provider. With this provider, your store can make sales through PIX.
 
-To configure Shipay affiliation, follow the steps below:
+To configure Shipay, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Shipay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Shipay__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account Shipay.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-sibs.md b/docs/tutorials/en/setting-up-payments-with-sibs.md
index 1774fff14..c02a988a5 100644
--- a/docs/tutorials/en/setting-up-payments-with-sibs.md
+++ b/docs/tutorials/en/setting-up-payments-with-sibs.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with SIBS'
 id: sNLPtJlAMnDpq40CCPKNo
 status: PUBLISHED
 createdAt: 2023-04-06T18:57:27.591Z
-updatedAt: 2023-04-06T19:07:28.327Z
-publishedAt: 2023-04-06T19:07:28.327Z
+updatedAt: 2024-01-25T19:05:01.739Z
+publishedAt: 2024-01-25T19:05:01.739Z
 firstPublishedAt: 2023-04-06T19:07:28.327Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-sibs
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the SIBS payment provider. With this connector, your store can make sales through SIBS credit card, promissory notes, MBWay and MultiBanco.
+At VTEX, it is possible to integrate with the SIBS payment provider. With this provider, your store can make sales through SIBS credit card, Notes Payable, MBWay and MultiBanco.
 
-To configure SIBS affiliation, follow the steps below:
+To configure SIBS, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __SIBS__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type 1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __SIBS__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by SIBS.
 5. In the __Payment settlement__ field, select one of the available options:
 
@@ -38,4 +38,4 @@ To configure the payment methods to be processed by SIBS, access [Configuring Pa
 
 To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-After following the indicated steps, SIBS connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, SIBS may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-stark-bank.md b/docs/tutorials/en/setting-up-payments-with-stark-bank.md
new file mode 100644
index 000000000..c42bfe32e
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-stark-bank.md
@@ -0,0 +1,34 @@
+---
+title: 'Setting up payments with Stark Bank'
+id: 19pwHHVuEGN743WOGXcbUM
+status: PUBLISHED
+createdAt: 2023-09-08T15:29:02.297Z
+updatedAt: 2024-01-23T21:44:38.751Z
+publishedAt: 2024-01-23T21:44:38.751Z
+firstPublishedAt: 2023-09-08T15:45:11.373Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-stark-bank
+locale: en
+legacySlug: setting-up-payments-with-stark-bank
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Stark Bank payment provider. With this provider, your store can make sales through bank invoice and PIX.
+
+To configure Stark Bank, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __StarkBank__ in the search bar and click on the name of the provider.
+4. If a warning message is displayed indicating that the app needs to be installed, click the __Install app__ button and follow the installation instructions.
+5. Click on __Authorize__. You will be redirected to the Stark Bank environment.
+6. In the Stark Bank environment, enter your Stark Bank account login and password. Follow the indicated instructions to complete the Stark Bank account linking with VTEX.
+7. After returning to __Admin VTEX__, click on `Save`.
+
+To configure the payment methods to be processed by Stark Bank, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Stark Bank connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-stelo.md b/docs/tutorials/en/setting-up-payments-with-stelo.md
index 5d82d902a..76e727ac9 100644
--- a/docs/tutorials/en/setting-up-payments-with-stelo.md
+++ b/docs/tutorials/en/setting-up-payments-with-stelo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with Stelo'
 id: 6c16nRhAGWaA2mSUOOuC00
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T20:20:44.376Z
-updatedAt: 2023-03-29T01:07:31.337Z
-publishedAt: 2023-03-29T01:07:31.337Z
+updatedAt: 2024-03-18T20:21:28.181Z
+publishedAt: 
 firstPublishedAt: 2018-03-05T19:08:32.807Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-payments-with-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 In addition to a [sub-acquirer](/en/tutorial/setting-up-sub-acquirer-stelo) that processes transactions carried out with various payment conditions, Stelo also offers a [digital wallet service](/en/faq/what-is-an-e-wallet). Your customer chooses to pay with it and is redirected to authentication in Stelo's environment.
 
 To set up payments with the Stelo digital wallet in your store, you first need to register the __Stelo Redirect__ gateway affiliation.
diff --git a/docs/tutorials/en/setting-up-payments-with-stelom1v2.md b/docs/tutorials/en/setting-up-payments-with-stelom1v2.md
new file mode 100644
index 000000000..91d5d6c8b
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-stelom1v2.md
@@ -0,0 +1,33 @@
+---
+title: 'Setting up payments with SteloM1V2'
+id: 1lO9Rn87U0iyBTCpgBlqYD
+status: PUBLISHED
+createdAt: 2024-03-14T13:56:38.010Z
+updatedAt: 2024-03-14T14:05:14.839Z
+publishedAt: 2024-03-14T14:05:14.839Z
+firstPublishedAt: 2024-03-14T14:05:14.839Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-stelom1v2
+locale: en
+legacySlug: setting-up-payments-with-stelom1v2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the SteloM1V2 payment provider. With this provider, your store can make sales through credit cards and bank invoices.
+
+To configure SteloM1V2, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __SteloM1V2__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by SteloM1V2.
+5. If you wish to modify the identification name to be displayed for the SteloM1V2 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
+
+To configure the payment methods to be processed by SteloM1V2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, SteloM1V2 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md b/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md
index d4a1183ac..a6279ee32 100644
--- a/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md
+++ b/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Store Card (cobranded)'
 id: jrkLK41IjuquUmyKUi86Q
 status: PUBLISHED
 createdAt: 2018-06-25T15:48:13.031Z
-updatedAt: 2023-03-22T19:19:30.029Z
-publishedAt: 2023-03-22T19:19:30.029Z
+updatedAt: 2023-09-22T21:25:38.666Z
+publishedAt: 2023-09-22T21:25:38.666Z
 firstPublishedAt: 2018-06-27T20:17:05.882Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,10 +26,18 @@ The first configuration step will be the creation of the custom payment __(cobra
 4. In __Name__, fill in the name of the card.
 5. In __Description__, write the text that will give more details about the payment condition.
 6. In the __Card Brand__ field, choose the banner to which your store card is linked. Currently, the possible options are: American Express, Cabal, Diners, Elo, Mastercard and Visa.
-7. In __BIN ranges__, enter the BIN codes of the cards so that they are validated by the system. You can insert a range of BINs (by inserting the first and last code of the sequence, separated by hyphen) or several (separating each one by comma and without spaces). If you prefer, you can use the co-branded card validator, filling in the values `100000-999999`.
-8. In the field __Acquirer Payment Code__, enter the code to be sent and processed by the acquirer you have contracted.
-9. In __Split Payments__, if you choose to use this option, when the sale involves marketplace stores, the amounts will be split between the sellers and the marketplace.
-10. Click __Save__.
+7. In __BIN ranges (optional)__, 
+you can enter a range of BINs (by entering the first and last code in the sequence, separated by a hyphen) or several (separating each range by a comma and without spaces).
+
+<div class="alert alert-warning">
+  When the customer enters a bin number outside the range specified in this field, the following message will be displayed "Check the digits printed on your card. We couldn't confirm if the card number is correct". If there is no error in the number entered, they can click on "YES, THE NUMBER IS CORRECT" to continue completing the order.
+</div>
+
+<blockquote><ui>8. In the field <b>Acquirer Payment Code (optional)</b>, enter the code to be sent and processed by the acquirer you have contracted.</ui>
+
+<blockquote><ui>9. In <b>Split Payments</b>, if you choose to use this option, when the sale involves marketplace stores, the amounts will be split between the sellers and the marketplace.</ui>
+
+<blockquote><ui>10. Click <b>Save</b>.</ui>
 
 ## Set up payment condition
 After configuring the card, you will need to configure the payment condition.
diff --git a/docs/tutorials/en/setting-up-payments-with-transfero-crypto-checkout.md b/docs/tutorials/en/setting-up-payments-with-transfero-crypto-checkout.md
new file mode 100644
index 000000000..54696e235
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-transfero-crypto-checkout.md
@@ -0,0 +1,49 @@
+---
+title: 'Setting up payments with Transfero Crypto Checkout'
+id: 29ZW22EW09zQDWZlPdyZ1T
+status: PUBLISHED
+createdAt: 2024-04-17T18:14:15.873Z
+updatedAt: 2024-04-17T18:44:01.978Z
+publishedAt: 2024-04-17T18:44:01.978Z
+firstPublishedAt: 2024-04-17T18:44:01.978Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-transfero-crypto-checkout
+locale: en
+legacySlug: setting-up-payments-with-transfero-crypto-checkout
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Transfero Crypto Checkout payment processor. Through it, your store can make sales through cryptocurrencies and PIX, and receive in [Fiat money](https://en.wikipedia.org/wiki/Fiat_money).
+
+To configure Transfero Crypto Checkout, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __CryptoCheckout__ in the search bar and click on the name of the processor.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account [Transfero Crypto Checkout](https://onboarding.transfero.com/).
+5. If you wish to modify the identification name to be displayed for the Transfero Crypto Checkout processor on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the processor in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __Transfero Checkout__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+7. Click `Save`.
+
+After following the indicated steps, Transfero Crypto Checkout processor may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-tyendacrypto.md b/docs/tutorials/en/setting-up-payments-with-tyendacrypto.md
index 1085f66e7..c1dbf81bc 100644
--- a/docs/tutorials/en/setting-up-payments-with-tyendacrypto.md
+++ b/docs/tutorials/en/setting-up-payments-with-tyendacrypto.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with TiendaCrypto'
 id: 7qC52v2j7q7B0YUtLnW2I9
 status: PUBLISHED
 createdAt: 2023-05-26T18:19:21.462Z
-updatedAt: 2023-05-26T22:40:14.439Z
-publishedAt: 2023-05-26T22:40:14.439Z
+updatedAt: 2024-01-24T13:32:40.359Z
+publishedAt: 2024-01-24T13:32:40.359Z
 firstPublishedAt: 2023-05-26T18:43:41.573Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-tyendacrypto
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the TiendaCrypto payment provider. With this connector, your store can make sales through cryptocurrencies.
+At VTEX, it is possible to integrate with the TiendaCrypto payment provider. With this provider, your store can make sales through cryptocurrencies.
 
-To configure TiendaCrypto affiliation, follow the steps below:
+To configure TiendaCrypto, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __TiendaCrypto__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __TiendaCrypto__ in the search bar and click on the name of the provider.
 4. Click on __Authorize__. You will be redirected to the TiendaCrypto environment.
 5. In the __Payment settlement__ field, select one of the available options:
 
diff --git a/docs/tutorials/en/setting-up-payments-with-unlimit.md b/docs/tutorials/en/setting-up-payments-with-unlimit.md
new file mode 100644
index 000000000..a17d1c60b
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-unlimit.md
@@ -0,0 +1,44 @@
+---
+title: 'Setting up payments with Unlimit'
+id: 5emdjkgQOEQruDinUrfXY8
+status: PUBLISHED
+createdAt: 2024-06-05T15:41:23.584Z
+updatedAt: 2024-07-29T15:08:14.122Z
+publishedAt: 2024-07-29T15:08:14.122Z
+firstPublishedAt: 2024-06-06T15:38:46.103Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-unlimit
+locale: en
+legacySlug: setting-up-payments-with-unlimit
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Unlimit payment provider. 
+Through this provider, your store can make sales using different payment methods, such as: cards (credit, debit, private label, cob-branded), bank slips and PIX.
+
+To configure Unlimit, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Unlimit__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ fields with data provided by your account Unlimit.
+5. If you wish to modify the identification name to be displayed for the Unlimit provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. Click `Save`.
+
+To configure the payment methods to be processed by Unlimit, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Unlimit may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-ventipay.md b/docs/tutorials/en/setting-up-payments-with-ventipay.md
index 04b9d4382..5b3ab7e2a 100644
--- a/docs/tutorials/en/setting-up-payments-with-ventipay.md
+++ b/docs/tutorials/en/setting-up-payments-with-ventipay.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with VentiPay'
 id: 11n076tXgeLa1wDT3n2hyZ
 status: PUBLISHED
 createdAt: 2022-10-18T18:04:20.082Z
-updatedAt: 2023-03-21T20:49:01.107Z
-publishedAt: 2023-03-21T20:49:01.107Z
+updatedAt: 2024-01-24T18:08:16.663Z
+publishedAt: 2024-01-24T18:08:16.663Z
 firstPublishedAt: 2022-10-18T18:28:35.755Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-ventipay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the VentiPay payment provider. With this connector, your store can make sales through the VentiPay.
+At VTEX, it is possible to integrate with the VentiPay payment provider. With this provider, your store can make sales through the VentiPay.
 
-To set up VentiPay affiliation, follow the steps below:
+To configure VentiPay, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Ventipay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Ventipay__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by VentiPay.
 5. Click on `Save`.
 
@@ -33,4 +33,4 @@ Choose the payment condition __Ventipay__.
 Activate the condition in the __Status__ field.
 Click on `Save`.
 
-After following the indicated steps, VentiPay connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, VentiPay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-virtuspay.md b/docs/tutorials/en/setting-up-payments-with-virtuspay.md
index 3ea5b2346..590ed3a84 100644
--- a/docs/tutorials/en/setting-up-payments-with-virtuspay.md
+++ b/docs/tutorials/en/setting-up-payments-with-virtuspay.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up payments with VirtusPay'
 id: 2Agqwp19cwyIbxuHErVG8I
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-08-11T15:02:59.728Z
-updatedAt: 2023-03-27T12:42:29.231Z
-publishedAt: 2023-03-26T21:15:04.050Z
+updatedAt: 2024-01-23T21:50:25.883Z
+publishedAt: 2024-01-23T21:50:25.883Z
 firstPublishedAt: 2022-08-11T16:38:04.718Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setting-up-payments-with-virtuspayv2.md b/docs/tutorials/en/setting-up-payments-with-virtuspayv2.md
index 3b1cdad90..3dd1ce195 100644
--- a/docs/tutorials/en/setting-up-payments-with-virtuspayv2.md
+++ b/docs/tutorials/en/setting-up-payments-with-virtuspayv2.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with VirtusPayV2'
 id: 1tbcLRNIB5Bz0oWl8LnayB
 status: PUBLISHED
 createdAt: 2023-03-27T12:14:53.392Z
-updatedAt: 2023-03-27T12:56:49.578Z
-publishedAt: 2023-03-27T12:56:49.578Z
+updatedAt: 2024-01-23T21:52:05.259Z
+publishedAt: 2024-01-23T21:52:05.259Z
 firstPublishedAt: 2023-03-27T12:56:49.578Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-virtuspayv2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the VirtusPayV2 payment provider. With this connector, your store can make sales through VirtusPay and VirtusPay Transparente.
+At VTEX, it is possible to integrate with the VirtusPayV2 payment provider. With this provider, your store can make sales through VirtusPay and VirtusPay Transparente.
 
-To configure VirtusPayV2 affiliation, follow the steps below:
+To configure VirtusPayV2, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __VirtusPayV2__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __VirtusPayV2__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__ and __Application Token__ fields with data provided by your account VirtusPay.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 6. Click on `Save`.
diff --git a/docs/tutorials/en/setting-up-payments-with-webpayoneclick.md b/docs/tutorials/en/setting-up-payments-with-webpayoneclick.md
new file mode 100644
index 000000000..b0a82f464
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-webpayoneclick.md
@@ -0,0 +1,39 @@
+---
+title: 'Setting up payments with WebpayOneClick'
+id: 7jIwDOcBbF3cxIyHKaj4LF
+status: PUBLISHED
+createdAt: 2024-03-07T14:01:33.652Z
+updatedAt: 2024-03-07T15:06:06.370Z
+publishedAt: 2024-03-07T15:06:06.370Z
+firstPublishedAt: 2024-03-07T15:06:06.370Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-webpayoneclick
+locale: en
+legacySlug: setting-up-payments-with-webpayoneclick
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the WebpayOneClick payment provider. With this provider, your store can make sales through Transbank Oneclick.
+
+To configure WebpayOneClick, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __WebpayOneClick__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App key__ and __App token__ fields with data provided by your account WebpayOneClick.
+5. If you wish to modify the identification name to be displayed for the WebpayOneClick provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click __Transbank Oneclick__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click `Save`.
+
+After following the indicated steps, WebpayOneClick may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-wepay4u.md b/docs/tutorials/en/setting-up-payments-with-wepay4u.md
new file mode 100644
index 000000000..240b5b600
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-wepay4u.md
@@ -0,0 +1,52 @@
+---
+title: 'Setting up payments with Wepay4u'
+id: 7xbyIPpU7PAXQNCfpVBqGC
+status: PUBLISHED
+createdAt: 2024-02-05T20:19:10.668Z
+updatedAt: 2024-03-13T15:09:57.098Z
+publishedAt: 2024-03-13T15:09:57.098Z
+firstPublishedAt: 2024-02-05T20:29:59.689Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-wepay4u
+locale: en
+legacySlug: setting-up-payments-with-wepay4u
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Wepay4u payment provider. With this provider, your store can make sales through Wepay4u.
+
+To configure Wepay4u, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Wepay4u__ in the search bar and click on the name of the provider.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account Wepay4u.
+5. If you wish to modify the identification name to be displayed for the Wepay4u provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. In __Provider Fields__, enter the __MerchantCode__ and __SecretKey__ information as per your Wepay4u account information.
+
+9. In __Currency__, select the currency to be used in the payment transaction.
+
+10. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __Wepay4u__.
+4. Activate the condition in the __Status__ field.
+5. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+6. Click `Save`.
+
+After following the indicated steps, Wepay4u may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-wompi.md b/docs/tutorials/en/setting-up-payments-with-wompi.md
index 53ffc2b23..5aa4d2aff 100644
--- a/docs/tutorials/en/setting-up-payments-with-wompi.md
+++ b/docs/tutorials/en/setting-up-payments-with-wompi.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Wompi'
 id: 40d6lWEyzLViHS7aYvcsqV
 status: PUBLISHED
 createdAt: 2022-02-21T18:22:13.804Z
-updatedAt: 2023-03-26T22:00:59.701Z
-publishedAt: 2023-03-26T22:00:59.701Z
+updatedAt: 2024-01-24T13:49:31.304Z
+publishedAt: 2024-01-24T13:49:31.304Z
 firstPublishedAt: 2022-02-21T19:06:12.105Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: setting-up-payments-with-wompi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Wompi payment provider. With this connector, your store can make sales through credit and debit cards, bank transactions, Nequi and PSE (colombian payment systems) and banking correspondents.
+At VTEX, it is possible to integrate with the Wompi payment provider. With this provider, your store can make sales through credit and debit cards, bank transactions, Nequi and PSE (colombian payment systems) and banking correspondents.
 
-To configure Wompi affiliation, follow the steps below:
+To configure Wompi, follow the steps below:
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. In the __Gateway affiliations__ tab, click on the __+__ button.
 3. Click on the __WompiCo__ connector.
 4. Click on __Authorize__. You will be redirected to the Wompi environment.
 5. In the Wompi environment, enter your Wompi account login and password, and click on __Vincular cuenta__. Follow the indicated instructions to complete the Wompi account linking with VTEX.
-6. After returning to VTEX Admin, click on __Save__.
+6. After returning to VTEX Admin, click `Save`.
 
 ## Setting up the payment condition
 
diff --git a/docs/tutorials/en/setting-up-payments-with-wompicov2.md b/docs/tutorials/en/setting-up-payments-with-wompicov2.md
index 024de7774..edd931df4 100644
--- a/docs/tutorials/en/setting-up-payments-with-wompicov2.md
+++ b/docs/tutorials/en/setting-up-payments-with-wompicov2.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with WompiCoV2'
 id: SnkXNUXkESqKxfFZu0LS4
 status: PUBLISHED
 createdAt: 2023-04-14T13:55:18.776Z
-updatedAt: 2023-04-14T14:23:30.858Z
-publishedAt: 2023-04-14T14:23:30.858Z
+updatedAt: 2024-01-24T13:54:46.662Z
+publishedAt: 2024-01-24T13:54:46.662Z
 firstPublishedAt: 2023-04-14T14:23:30.858Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: setting-up-payments-with-wompicov2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the WompiCoV2 payment provider. With this connector, your store can make sales through credit and debit cards.
+At VTEX, it is possible to integrate with the WompiCoV2 payment provider. With this provider, your store can make sales through credit and debit cards.
 
-To configure WompiCoV2 affiliation, follow the steps below:
+To configure WompiCoV2, follow the steps below:
 
 1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
 2. In the __Gateway affiliations__ tab, click on the `+` button.
 3. Click on the __WompiCoV2__ connector.
 4. Click on __Authorize__. You will be redirected to the Wompi environment.
 5. In the Wompi environment, enter your Wompi account login and password, and click on __Vincular cuenta__. Follow the indicated instructions to complete the Wompi account linking with VTEX.
-6. After returning to VTEX Admin, click on `Save`.
+6. After returning to VTEX Admin, click `Save`.
 
 To configure the payment methods to be processed by WompiCoV2, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
diff --git a/docs/tutorials/en/setting-up-payments-with-woovi.md b/docs/tutorials/en/setting-up-payments-with-woovi.md
new file mode 100644
index 000000000..72b65075b
--- /dev/null
+++ b/docs/tutorials/en/setting-up-payments-with-woovi.md
@@ -0,0 +1,40 @@
+---
+title: 'Setting up payments with Woovi'
+id: a61xxlOLJTQRrPx2MrVfs
+status: PUBLISHED
+createdAt: 2023-09-08T17:29:33.321Z
+updatedAt: 2024-01-23T21:54:32.467Z
+publishedAt: 2024-01-23T21:54:32.467Z
+firstPublishedAt: 2023-09-08T17:49:01.961Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: setting-up-payments-with-woovi
+locale: en
+legacySlug: setting-up-payments-with-woovi
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+At VTEX, it is possible to integrate with the Woovi payment provider. With this provider, your store can make sales through Woovi and Woovi Parcelado.
+
+To configure Woovi, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __WooviConnector__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__, __Application Token__ and __App ID__ fields with data provided by your account Woovi.
+5. In __Method__, select __Pix__ or __Woovi Parcelado__.
+6. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
+7. Click `Save`.
+
+## Setting up the payment condition
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the `+` button.
+3. Click on __Woovi__ or __Woovi Parcelado__.
+4. Activate the condition in the __Status__ field.
+5. If you want to use an anti-fraud system, select the option __Use anti-fraud__.
+6. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Click on `Save`.
+
+After following the indicated steps, Woovi connector may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-yuno.md b/docs/tutorials/en/setting-up-payments-with-yuno.md
index 04256bc6c..4cb2b9501 100644
--- a/docs/tutorials/en/setting-up-payments-with-yuno.md
+++ b/docs/tutorials/en/setting-up-payments-with-yuno.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Yuno'
 id: h7PS0vDJJokqI9axZPNzE
 status: PUBLISHED
 createdAt: 2023-04-14T12:42:43.736Z
-updatedAt: 2023-04-14T13:21:45.782Z
-publishedAt: 2023-04-14T13:21:45.782Z
+updatedAt: 2024-01-23T21:56:16.050Z
+publishedAt: 2024-01-23T21:56:16.050Z
 firstPublishedAt: 2023-04-14T13:21:45.782Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: setting-up-payments-with-yuno
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Yuno payment provider. With this connector, your store can make sales through credit cards, bank invoice and promissories.
+At VTEX, it is possible to integrate with the Yuno payment provider. With this provider, your store can make sales through credit cards, bank invoice and notes payable.
 
-To configure Yuno affiliation, follow the steps below:
+To configure Yuno, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Yuno__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Yuno__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__, __Application Token__ and __Account ID__ fields with data provided by your account Yuno.
 5. In __Auto Capture__, select whether the payment capture will be automatic after authorization.
 6. In __Delay To Capture (in days) Default 1 day, max 7 days__, fill in the period (in days) in which the payment capture must wait to be carried out. The default value is 1 day and the maximum is 7 days.
diff --git a/docs/tutorials/en/setting-up-payments-with-zenki.md b/docs/tutorials/en/setting-up-payments-with-zenki.md
index e75a83394..cd486cf55 100644
--- a/docs/tutorials/en/setting-up-payments-with-zenki.md
+++ b/docs/tutorials/en/setting-up-payments-with-zenki.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Zenki'
 id: 6LK7wMg0OB39UQKoZILoNL
 status: PUBLISHED
 createdAt: 2023-03-30T17:34:01.758Z
-updatedAt: 2023-03-30T18:04:59.870Z
-publishedAt: 2023-03-30T18:04:59.870Z
+updatedAt: 2024-01-25T18:50:47.590Z
+publishedAt: 2024-01-25T18:50:47.590Z
 firstPublishedAt: 2023-03-30T18:02:25.796Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: setting-up-payments-with-zenki
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Zenki. With this connector, your store can make sales through bitcoins.
+At VTEX, it is possible to integrate with the Zenki. With this provider, your store can make sales through bitcoins.
 
-To configure Zenki affiliation, follow the steps below:
+To configure Zenki, follow the steps below:
 
-1. In the VTEX Admin, go to __Store Settings > Payments > Settings__, or type __Settings__ in the search bar at the top of the page.
-2. In the __Gateway affiliations__ tab, click on the `+` button.
-3. Click on the __Zenki__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Zenki__ in the search bar and click on the name of the provider.
 4. Fill in the __Application Key__, __Application Token__, __API key__, __Secret Key__ and __Webhook signing secret__ fields with data provided by your account Zenki.
 5. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
-6. Click on `Save`.
+6. Click `Save`.
 
 ## Setting up the payment condition
 
@@ -35,6 +35,6 @@ To configure Zenki affiliation, follow the steps below:
 5. Activate the condition in the __Status__ field.
 6. If you want to use an anti-fraud system, select the option __Use anti-fraud solution__.
 7. If you want, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
-8. Click on `Save`.
+8. Click `Save`.
 
-After following the indicated steps, Bancolombia BNPL connector may take up to 10 minutes to appear at your store's checkout as a payment option.
+After following the indicated steps, Zenki may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payments-with-zoop.md b/docs/tutorials/en/setting-up-payments-with-zoop.md
index bfd4ab62a..f44d45d4d 100644
--- a/docs/tutorials/en/setting-up-payments-with-zoop.md
+++ b/docs/tutorials/en/setting-up-payments-with-zoop.md
@@ -3,8 +3,8 @@ title: 'Setting up payments with Zoop'
 id: 5bRYiUjX1sewZuON8HA6Ld
 status: PUBLISHED
 createdAt: 2023-02-13T18:17:14.240Z
-updatedAt: 2023-02-13T18:57:07.275Z
-publishedAt: 2023-02-13T18:57:07.275Z
+updatedAt: 2024-01-23T21:58:29.652Z
+publishedAt: 2024-01-23T21:58:29.652Z
 firstPublishedAt: 2023-02-13T18:50:09.746Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,24 @@ legacySlug: setting-up-payments-with-zoop
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX, it is possible to integrate with the Zoop payment provider. With this connector, your store can make sales through credit cards and bank invoice.
+At VTEX, it is possible to integrate with the Zoop payment provider. With this provider, your store can make sales through credit cards and bank invoice.
 
-To configure Zoop affiliation, follow the steps below:
+To configure Zoop, follow the steps below:
 
-1. Access the __Admin__ VTEX.
-2. Click on __Payments__.
-3. Then, click on __Settings__.
-4. In the __Gateway affiliations__ tab, click on the `+` button.
-5. Click on the __Zoop__ connector.
-6. Fill in the __Application Key__ and __Application Token__ fields with data provided by Zoop.
-7. In the __Payment settlement__ field, select one of the available options:
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Zoop__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__ and __Application Token__ fields with data provided by Zoop.
+5. In the __Payment settlement__ field, select one of the available options:
 
     - __Use Behavior Recommended By The Payment Processor__: capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization.
     - __Immediate: Automatic Settlement After Payment Authorization__: capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.
     - __Immediate: Automatic Settlement After Anti-Fraud Analysis__:  Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in __Immediate: Automatic Settlement After Payment Authorization__.
     - __Deactivated: Not Automatically Captured__: capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.
 
-<ui>  8. In <b>Enable payout split and send payment recipients?</b>, select whether split payments will be available for the marketplace and sellers.</ui>
+<ui>  6. In <b>Enable payout split and send payment recipients?</b>, select whether split payments will be available for the marketplace and sellers.</ui>
 
-<ui>  9. Click on <b>Save.</b></ui>
+<ui>  7. Click on <b>Save.</b></ui>
 
 To set up payment conditions, access [Configure special payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions).
 
diff --git a/docs/tutorials/en/setting-up-paypal-plus.md b/docs/tutorials/en/setting-up-paypal-plus.md
index a7935a555..90e26eb78 100644
--- a/docs/tutorials/en/setting-up-paypal-plus.md
+++ b/docs/tutorials/en/setting-up-paypal-plus.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up PayPal Plus (Transparent PayPal)'
 id: 2akxq3I92k8A4kymIYOiWy
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-20T20:15:36.950Z
-updatedAt: 2023-03-29T01:12:02.453Z
-publishedAt: 2023-03-29T01:12:02.453Z
+updatedAt: 2024-03-18T20:30:56.156Z
+publishedAt: 
 firstPublishedAt: 2018-02-20T22:56:13.192Z
 contentType: tutorial
 productTeam: Financial
@@ -15,38 +15,44 @@ legacySlug: setting-up-paypal-plus
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-At VTEX Payments, you can set up the PayPal Plus sub-acquirer, PayPal's transparent checkout. Through this payment mode, the client simply enters their __credit card information__ and finishes the purchase normally. Payment is made directly on your site, without the need to redirect your customers.
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
+At VTEX Payments, you can set up the PayPal Plus sub-acquirer, PayPal's transparent checkout. Through this payment mode, the client simply enters their credit card information and finishes the purchase normally. Payment is made directly on your site, without the need to redirect your customers.
 
 To set it up, follow the steps below:
 
-## Setting up PayPal Plus gateway affiliation
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button. 
+3. Type the name __PayPalPlus__ in the search bar and click on the name of the provider.
+4. If you wish to modify the identification name to be displayed for the PayPal Plus on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+5. Under __Payment Control__, select whether you want to activate PayPal Plus in a test environment by clicking __Enable test mode__.
+6. Fill in the fields below according to the data provided by PayPal:
+    - In __Client ID__ enter the _clientId_.
+    - In __Secret__ enter _secret_.
+    - In __Username__ enter _userName_.
+    - In __Password__ enter the _password_.
+    - In __Signature__ insert the _signature_.
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __PayPalPlus__ connector.
+<blockquote><ui>  7. Under <b>Save Cards</b>, select <b>Yes</b> so the customer can select the option to save the card at checkout. If you do not wish to enable this option, select <b>No</b>.</ui>
 
-Fill in the registration fields with the information provided by PayPal, as follows.
-- Fill in the __Client ID__ field with the *clientId*.
-- Fill in the __Secret__ field with the *secret*.
-- Fill in the __Username__ field with the *userName*.
-- Fill in the __Password__ field with the *password*.
-- Fill in the __Signature__ field with the *signature*.
+<blockquote><ui>  8. In <b>Currency</b>, choose the transaction currency.</ui>
 
-Then, follow these steps:
-1. In the __Save cards__ field, select __Yes__ so that the customer may choose the option to save the card at the time of checkout. If you don't want to enable this option, select __No__.
-2. In __Currency__, choose the currency of the transaction.
-3. In __Local__, select the location of the transaction.
-4. Click __Save__.
+<blockquote><ui>  9. In <b>Transaction location</b>, select the country of the transaction.</ui>
 
-## Setting up PayPal Plus payment condition
+<blockquote><ui>  10. In <b>Enable Risk API (STC)</b>, select the option according to your PayPal settings.</ui>
 
-1. Within the __Setting__ area of Payments, click on the __Payment Conditions__.
-2. Click the __+__ button.
-3. Click on the __PayPalPlus__ payment method.
-4. Click the __Status__ button to enable this payment condition.
-5. If you want, check the __Use Anti-Fraud__ box to activate the basic anti-fraud.
-6. Since payment with PayPal Plus is a credit card payment, you can choose between [setting up cash payment or payment with installments](/en/tutorial/how-to-configure-payment-conditions).
-7. If you want, you can also configure [special payment conditions](/en/tutorial/special-conditions).
-8. After you have made the settings, click __Save__.
+<blockquote><ui>  11. Click <b>Save</b>.</ui>
+
+## Setting up PayPal Plus payment condition
 
-Great! Now checkout will show the __credit card__ payment option using [PayPal as a sub-acquirer](/en/tutorial/what-is-a-sub-acquirer).
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. In the __Payment Conditions__ tab, click on the + button.
+3. Click on __PayPalPlus__.
+4. Fill the __Condition name__ field with a name of your choice for identification.
+5. Activate the condition in the __Status__ field.
+6. Select whether you want to use an anti-fraud system by selecting the __Use anti-fraud solution__ option.
+7.  Indicate whether credit card payments must be made [in full or with installments](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455).
+9. If you wish, you can also configure [special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
+10. Click `Save`.
+
+After following the indicated steps, PayPal Plus may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-payu-gateway.md b/docs/tutorials/en/setting-up-payu-gateway.md
index 7f1f86ed3..4cbebce76 100644
--- a/docs/tutorials/en/setting-up-payu-gateway.md
+++ b/docs/tutorials/en/setting-up-payu-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up PayU gateway'
 id: 36zWOAFHmwIAoWIEU2Y08q
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-27T15:25:04.654Z
-updatedAt: 2023-03-21T20:17:16.717Z
-publishedAt: 2023-03-21T20:17:16.717Z
+updatedAt: 2024-03-18T20:27:28.378Z
+publishedAt: 
 firstPublishedAt: 2018-03-27T22:13:40.899Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: setting-up-payu-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 PayU is a [gateway](/en/tutorial/what-is-a-payment-gateway) that offers a number of solutions to make transactions in your store easier and safer. With [PCI certification](/en/faq/what-is-the-pci-ssc), this solution is exclusive for Argentina, Brazil, Chile, Colombia, Mexico, Panama and Peru.
 
 To set PayU up, follow the steps below:
 
-## Setting up PayU gateway affiliation
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __PayU__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PayU__ in the search bar and click on the name of the provider.
 4. Fill in the registration fields with the data provided by PayU (fields _API Login_, _API Key_, _Account Id_ and _Merchant Id_).
 5. In the __Authorization method__ field, choose how you want to authorize transactions.
 6. In __Currency__ , select the currency that will be used in the transactions.
diff --git a/docs/tutorials/en/setting-up-payzen-gateway.md b/docs/tutorials/en/setting-up-payzen-gateway.md
index 4b1b5f6f5..146f63817 100644
--- a/docs/tutorials/en/setting-up-payzen-gateway.md
+++ b/docs/tutorials/en/setting-up-payzen-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up PayZen gateway'
 id: 3v3n5eQvxem8MQOCkugk24
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-13T19:39:04.093Z
-updatedAt: 2023-03-29T00:56:10.654Z
-publishedAt: 2023-03-29T00:56:10.654Z
+updatedAt: 2024-03-18T19:50:54.475Z
+publishedAt: 
 firstPublishedAt: 2018-03-13T22:27:11.198Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-payzen-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 With VTEX, you can set up [PayZen gateway](/en/tutorial/what-is-a-payment-gateway) in your store. Easily integrated, it follows the security standards defined by [Payments](/en/faq/what-is-the-pci-ssc).
 
 To set PayZen up, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md b/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md
index 31b5f106d..6cd79f969 100644
--- a/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md
+++ b/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md
@@ -21,18 +21,18 @@ To access it, follow the steps below:
 
 1. In the top bar of the Admin, in the right corner, click on the button with your initials;
 2. Select the __User Settings__ option.  
-![User Settings option User Management EN](https://images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/f3e6f932c1db9f19103b8e0f4679e557/Op____o_Configura____es_de_usu__rio_User_Management_EN.png)
+![User Settings option User Management EN](//images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/f3e6f932c1db9f19103b8e0f4679e557/Op____o_Configura____es_de_usu__rio_User_Management_EN.png)
 
 There are two menu options:
 
 - In __Personal__, you can see your name, your e-mail that is used in the Admin, and you can also edit your phone number.  
-![Personal Configuration User Management EN](https://images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/977702361ea9b9eab8b64e5bd7136e75/Configura____o_Pessoal_User_Management_EN.png)
+![Personal Configuration User Management EN](//images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/977702361ea9b9eab8b64e5bd7136e75/Configura____o_Pessoal_User_Management_EN.png)
 - In __Name__, you can edit your first and last name.  
-  ![Configuração Nome User Management EN](https://images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/7a96df88e5d4eda5f1059efb854e7e89/Configura____o_Nome_User_Management_EN.png)
+  ![Configuração Nome User Management EN](//images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/7a96df88e5d4eda5f1059efb854e7e89/Configura____o_Nome_User_Management_EN.png)
 In __Mobile number__, you can edit your cell phone number with the country code.  
-  ![Configuração Celular User Management EN](https://images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/87437ca6668c91e16964aeb519575f03/Configura____o_Celular_User_Management_EN.png)
+  ![Configuração Celular User Management EN](//images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/87437ca6668c91e16964aeb519575f03/Configura____o_Celular_User_Management_EN.png)
 - In __Authentication__, you can find the password options, 2-factor authentication (2FA) for your VTEX Admin login and session management. See the options in detail below.  
-![Configuration User Management Authentication EN](https://images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/1fd6875c57e30b7b6957e306a3426b30/Configura____o_Autentica____o_User_Management_EN.png)
+![Configuration User Management Authentication EN](//images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/1fd6875c57e30b7b6957e306a3426b30/Configura____o_Autentica____o_User_Management_EN.png)
 
 ## 2-step verification
 
@@ -50,4 +50,4 @@ Here you must configure the application that will provide the authentication key
 
 See in detail how to configure the application in the article on [Enabling two-factor authentication login](https://help.vtex.com/en/tutorial/habilitar-login-por-autenticacao-de-2-fatores#habilitar-o-2fa-por-aplicativo).
 
-![Configuration 2-step User Management EN](https://images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/6882baabe4044696de7b6016c0397b07/Configura____o_Verifica____o_em_2_passos_User_Management_EN.png)
+![Configuration 2-step User Management EN](//images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/6882baabe4044696de7b6016c0397b07/Configura____o_Verifica____o_em_2_passos_User_Management_EN.png)
diff --git a/docs/tutorials/en/setting-up-place2pay-gateway.md b/docs/tutorials/en/setting-up-place2pay-gateway.md
index 4dbe7002d..85e10287d 100644
--- a/docs/tutorials/en/setting-up-place2pay-gateway.md
+++ b/docs/tutorials/en/setting-up-place2pay-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Place2Pay gateway'
 id: 2NmmnLpUPY0A8aMi0oyiQq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-07T21:45:23.671Z
-updatedAt: 2023-03-29T01:09:24.503Z
-publishedAt: 2023-03-29T01:09:24.503Z
+updatedAt: 2024-03-18T19:53:38.738Z
+publishedAt: 
 firstPublishedAt: 2018-03-07T22:13:43.326Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-place2pay-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Place2Pay is the redirect version of the PlaceToPay gateway, which offers solutions for both large and small stores.
 
 To set Place2Pay up, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-price-tables-for-specific-users.md b/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
index 6a411246b..336402697 100644
--- a/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
@@ -77,11 +77,11 @@ In the Admin, go to __Prices__ > __Price List__.
 
 In the search filter, enter the names of the tables created in __Master Data__.
 
-![Filters](https://images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
+![Filters](//images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
 
 Price tables are shown as columns of the price list, as are trade policies.
 
-![Prices](https://images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
+![Prices](//images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
 
 To update a fixed price in a specific table, on the column corresponding to that table, and then on __Define fixed prices__. 
 
@@ -98,7 +98,7 @@ When a user is not logged into your store, the default prices set by the trade p
 If the user is logged in, they will see the prices corresponding to the price table with which their email is associated.
 
 For example, these two clients are linked to different price tables:
-![Clients](https://images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
+![Clients](//images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
 
 When Daniel, who is linked to the Silver price table, is logged into the store, he will see the prices set on this table. The backpack in the example above will cost USD 50.00.
 
diff --git a/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md b/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md
index 97c350e64..074cfc219 100644
--- a/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md
+++ b/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Rede acquirer with ERedeRest'
 id: 5TD6Ap9kiIUSiAMUsgYmcY
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-12T15:47:44.783Z
-updatedAt: 2023-03-29T01:11:21.243Z
-publishedAt: 2023-03-29T01:11:21.243Z
+updatedAt: 2024-03-18T18:22:35.227Z
+publishedAt: 
 firstPublishedAt: 2018-04-13T15:41:42.879Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-rede-acquirer-with-erederest
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 In VTEX, you can integrate with the [acquirer](/en/tutorial/what-is-an-acquirer) Rede using the ERedeREST connector. This connector brings a number of enhancements, including pre-authorization support (__Visa__, __Mastercard__, __American Express__, __Diners__, __Hipercard__, __JCB__ and __Credz__).
 
 <div class="alert alert-warning">
diff --git a/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md b/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md
index 9e1b097e2..4bebe57b9 100644
--- a/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md
+++ b/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Seller White Label as a Pickup Point'
 id: 6fSUE2O0taaoKieAaiuc4e
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-09-04T14:22:05.290Z
-updatedAt: 2023-03-29T18:58:34.411Z
-publishedAt: 2023-03-29T18:58:34.411Z
+updatedAt: 2023-07-26T21:33:59.946Z
+publishedAt: 
 firstPublishedAt: 2018-09-05T20:38:04.270Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -48,6 +48,10 @@ To know more about filling out the spreadsheet fields, access our article [Fill
 
 If the pickup point configuration has been correctly made in the Franchise Account, SKUs with __stock available and price__ may be sold on the Main Account, where the Franchise Account will act as a __Seller White Label__ and the Main Account will function as a __Marketplace__.
 
+<div class="alert alert-warning">
+Make sure your franchise seller is active. In your VTEX Admin, go to <b>Marketplace > Sellers > Management</b>, and in the seller row in column <i>Status</i>, click <code>Active</code>.
+</div>
+
 ### Seller White Label/Franchise Account
 
 To check if the seller white label is delivering a SKU through the registered pickup point, you must do a `POST` on the fulfillment route:
diff --git a/docs/tutorials/en/setting-up-shipment.md b/docs/tutorials/en/setting-up-shipment.md
index 37ebd03ce..eae01a26d 100644
--- a/docs/tutorials/en/setting-up-shipment.md
+++ b/docs/tutorials/en/setting-up-shipment.md
@@ -27,7 +27,7 @@ The first box with a total time of __2 days__ will wait for the item represented
 
 The period considers T = 0 as the date of the order.
 
-![Configuração em estoque e entrega EN](https://images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/c529a129854fed2bf8c6309e132bb0c4/Configura____o_em_estoque_e_entrega_EN.png)
+![Configuração em estoque e entrega EN](//images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/c529a129854fed2bf8c6309e132bb0c4/Configura____o_em_estoque_e_entrega_EN.png)
 
 ## How to set up the shipment
 
diff --git a/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md b/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md
index f33dd8361..20daaaba5 100644
--- a/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md
+++ b/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Sitef gateway with pre-auth'
 id: 2ZH4DLmZpKw022aSGcGYag
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-05T21:07:59.629Z
-updatedAt: 2023-03-29T01:21:24.445Z
-publishedAt: 2023-03-29T01:21:24.445Z
+updatedAt: 2024-03-18T20:04:33.165Z
+publishedAt: 
 firstPublishedAt: 2018-03-06T14:09:56.654Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-sitef-gateway-with-pre-auth
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 In order to allow purchases made with credit card to have the amount reserved, you may set up the __Sitef gateway with pre-auth__ (pre-authorization) in your store.
 
 To do this, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-sitef-gateway.md b/docs/tutorials/en/setting-up-sitef-gateway.md
index 0049d59a4..dcda8cf0c 100644
--- a/docs/tutorials/en/setting-up-sitef-gateway.md
+++ b/docs/tutorials/en/setting-up-sitef-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up Sitef gateway'
 id: 1y3gqmbb6wgwscW8yeccAc
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-05T17:07:51.846Z
-updatedAt: 2023-03-29T01:01:36.029Z
-publishedAt: 2023-03-29T01:01:36.029Z
+updatedAt: 2024-03-18T20:02:31.580Z
+publishedAt: 
 firstPublishedAt: 2018-03-05T17:35:10.870Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,17 @@ legacySlug: setting-up-sitef-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-In VTEX, you can configure the __Sitef__ gateway. If you would like to receive payments from Sitef, follow the steps below:
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
 
-## Setting up Sitef gateway affiliation
+In VTEX, you can configure the Sitef gateway. To configure it, follow the steps below:
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Sitef__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Sitef__ in the search bar and click on the name of the provider.
 4. In the __Store ID__ field , fill in your MerchantId in Sitef. 
 5. In __Access Key__ , fill in the MerchantKey provided by Sitef.
 6. In __Advanced security capture__ , choose how long to capture the value after the transaction is approved.
-7. Click __Save__.
+7. Click `Save`.
 
 ## Setting up the payment condition
 
diff --git a/docs/tutorials/en/setting-up-sms-password-recovery.md b/docs/tutorials/en/setting-up-sms-password-recovery.md
index 364784839..441f3a239 100644
--- a/docs/tutorials/en/setting-up-sms-password-recovery.md
+++ b/docs/tutorials/en/setting-up-sms-password-recovery.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up SMS password recovery'
 id: 4MBZmPN2GSBNFooa9la555
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-03-07T21:02:11.023Z
-updatedAt: 2020-09-17T21:00:30.654Z
-publishedAt: 2020-09-17T21:00:30.654Z
+updatedAt: 2024-05-22T13:29:09.953Z
+publishedAt: 
 firstPublishedAt: 2019-03-07T21:04:24.196Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,13 +26,13 @@ That being said, check out the step-by-step on how to set it up:
 1. Enter the __Message Center__.
 2. Click __Templates__.
 
-  ![5NrtBpFRTxInFl4aY2FrVz-en](https://images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/588f1c7842ebdfce815de1890a561264/5NrtBpFRTxInFl4aY2FrVzt-en.png)
+  ![5NrtBpFRTxInFl4aY2FrVz-en](//images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/588f1c7842ebdfce815de1890a561264/5NrtBpFRTxInFl4aY2FrVzt-en.png)
 
 3. Click on the __Password Recovery__ template.
 4. Click the __SMS__ tab.
 5. Choose the option __"Enable SMS sending?"__.
 
-  ![password-recovery-sms-tab-en](https://images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/68638513852254018741915f68cfa795/password-recovery-sms-tab-en.gif)
+  ![password-recovery-sms-tab-en](//images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/68638513852254018741915f68cfa795/password-recovery-sms-tab-en.gif)
 
   *After clicking on "Enable SMS sending", the platform presents the other sending settings.*
 
@@ -40,7 +40,7 @@ That being said, check out the step-by-step on how to set it up:
 7. Fill in the __Destination__ field with the variable `{{_accountInfo.Telephone}}`.
 8. Fill in the __Message Text__ field with the message content. The information `Name: {{name}}`, `Login: {{login}}` and `Password: {{password}}` are essential.
 
-  ![password-recovery-sms-fields-en](https://images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ab09b49184ae0bc382ab26bc551d4b6e/password-recovery-sms-fields-en.png)
+  ![password-recovery-sms-fields-en](//images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ab09b49184ae0bc382ab26bc551d4b6e/password-recovery-sms-fields-en.png)
 
 9. Review the SMS content in __Preview__.
 10. Click __Save__.
diff --git a/docs/tutorials/en/setting-up-sub-acquirer-stelo.md b/docs/tutorials/en/setting-up-sub-acquirer-stelo.md
index febd0dd6e..2c9d861ce 100644
--- a/docs/tutorials/en/setting-up-sub-acquirer-stelo.md
+++ b/docs/tutorials/en/setting-up-sub-acquirer-stelo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up sub-acquirer Stelo'
 id: 3gHWiaK9wQg08wOsoysciQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T17:43:45.957Z
-updatedAt: 2023-03-29T01:10:18.026Z
-publishedAt: 2023-03-29T01:10:18.026Z
+updatedAt: 2024-03-18T20:16:43.458Z
+publishedAt: 
 firstPublishedAt: 2018-03-02T20:17:14.474Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-sub-acquirer-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 Stelo is a [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) that facilitates the integration of payment methods into your store.
 
 To set up Stelo, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-the-notes-payable-conector.md b/docs/tutorials/en/setting-up-the-notes-payable-conector.md
new file mode 100644
index 000000000..1a23192a8
--- /dev/null
+++ b/docs/tutorials/en/setting-up-the-notes-payable-conector.md
@@ -0,0 +1,31 @@
+---
+title: 'Setting up the Notes Payable conector'
+id: 7Gy0SJRVS0Qi2CuWMAqQc0
+status: CHANGED
+createdAt: 2018-06-22T15:15:02.946Z
+updatedAt: 2024-01-19T19:28:16.938Z
+publishedAt: 2023-10-18T17:29:11.714Z
+firstPublishedAt: 2018-06-22T19:10:55.195Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: setting-up-the-notes-payable-conector
+locale: en
+legacySlug: setting-up-the-notes-payable-conector
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+The __Notes Payable__ connector, as its name suggests, allows your store to accept notes payable as a payment method.
+
+To set it up, follow the steps below:
+
+## Setting up the Notes payable gateway affiliation
+1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
+2. On the __Gateway Affiliations__ tab, click the `+` button.
+3. Click the __Notes Payable__ Connector.
+4. In __Note payable expiration date in days (maximum is 180)__ , set how many days your customer will have to pay the note before it loses its validity.
+5. Under __Automatically authorize__, inform if you want to approve the payment immediately. We only recommend choosing this option in cases where payment is made on delivery or withdrawal in the store. By choosing _Yes_, the order automatically changes to the status _Preparing Delivery_ without going through any payment checks.
+6. Click `Save`.
+
+## Setting up the payment condition
+After following the steps indicated above, the Notes Payable connector will be configured in your store. Thus, when registering a note payable (on Payments'  __Custom Payments__ tab), it will be available in the __Process with affiliation__ field. To learn how to register custom payments, access [How to configure a custom payment](https://help.vtex.com/en/tutorial/how-to-configure-a-custom-payment).
diff --git a/docs/tutorials/en/setting-up-the-notify-me-option.md b/docs/tutorials/en/setting-up-the-notify-me-option.md
index 99988f3a0..d7cc3f641 100644
--- a/docs/tutorials/en/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/en/setting-up-the-notify-me-option.md
@@ -23,7 +23,7 @@ When a product is out of [stock](https://help.vtex.com/en/tutorial/managing-stoc
 
 See below an example of how the **Notify me** option is displayed in a store. To receive a notification when the item is back in store, the customer must type in the name and the email in the marked fields and then click on the `Send` button.
 
-![aviseme-en](https://images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/1ae27f3cae7404d1ba86d4e06c231fd6/132012045-06c65073-2692-4827-b08a-7be5730b6422.png)
+![aviseme-en](//images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/1ae27f3cae7404d1ba86d4e06c231fd6/132012045-06c65073-2692-4827-b08a-7be5730b6422.png)
 
 As soon as the item is back in stock, the system automatically sends an email to the customer informing them that the product is available for purchase again. 
 
diff --git a/docs/tutorials/en/setting-up-the-paymee-gateway.md b/docs/tutorials/en/setting-up-the-paymee-gateway.md
index 38f0bdf52..38cb536f1 100644
--- a/docs/tutorials/en/setting-up-the-paymee-gateway.md
+++ b/docs/tutorials/en/setting-up-the-paymee-gateway.md
@@ -3,8 +3,8 @@ title: 'Setting up the PayMee gateway'
 id: 3fsilRdrBS6GOAy622soWy
 status: PUBLISHED
 createdAt: 2018-02-28T21:29:08.666Z
-updatedAt: 2019-12-31T15:20:50.800Z
-publishedAt: 2019-12-31T15:20:50.800Z
+updatedAt: 2024-03-14T17:02:16.884Z
+publishedAt: 2024-03-14T17:02:16.884Z
 firstPublishedAt: 2018-03-01T21:53:29.140Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,19 @@ legacySlug: setting-up-the-paymee-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-In VTEX, you can set up the PayMee payment gateway. With this connector, your store can receive payments through bank transfer or cash.
+At VTEX, it is possible to integrate with the PayMee payment provider. With this provider, your store can make sales through PayMee and PIX.
 
-To set it up, follow the steps below:
+To configure PayMee, follow the steps below:
 
-## Setting up PayMee gateway affiliation
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __PayMee__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by PayMee.
+5. If you wish to modify the identification name to be displayed for the PayMee provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
 
-1. Enter the __Payments__ module.
-2. Click __Settings__.
-3. On the __Gateway Affiliations__ tab, click the __+__ button.
-4. Click the __PayMee__ connector.
-5. Fill in the __Application Key__ and __Application Token__ fields with the data provided by PayMee.
-6. Click __Save__.
+To configure the payment methods to be processed by PayMee, access [Configuring payment conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-## Settting up PayMee payment condition
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-1. Within the __Settings__ section of Payments, click on the __Payment Conditions__ tab.
-2. Click the __+__ button.
-3. Click the __PayMee__ payment method.
-4. Click the __Status__ button to enable this payment condition.
-5. If desired, check the box __Use Anti-Fraud__ to activate the basic anti-fraud.
-6. Click __Save__.
-
-That's it! Now __PayMee__ checkout option will be displayed for your customers.
+After following the indicated steps, PayMee may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-the-price-range-filter.md b/docs/tutorials/en/setting-up-the-price-range-filter.md
index 89f9e775f..9fcf7feef 100644
--- a/docs/tutorials/en/setting-up-the-price-range-filter.md
+++ b/docs/tutorials/en/setting-up-the-price-range-filter.md
@@ -20,7 +20,7 @@ They are very important for browsing and searching products in the store.
 
 The registration is simple, and different price ranges may be determined for categories, as shown below:
 
-![faixa-de-preço en](https://images.ctfassets.net/alneenqid6w5/1Xj5nkiiYgugKioamYQEs4/6aa1023fbcda148c33b73fa52890b1b7/faixa-de-pre__o_en.png)
+![faixa-de-preço en](//images.ctfassets.net/alneenqid6w5/1Xj5nkiiYgugKioamYQEs4/6aa1023fbcda148c33b73fa52890b1b7/faixa-de-pre__o_en.png)
 
 In Price Ranges, click on “New Price Range” and fill in the fields below:
 
diff --git a/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
index 76fa6773a..0777c9720 100644
--- a/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
@@ -25,23 +25,23 @@ To make it easier, the entire setup in this article can be <a href="https://supp
 
 For manual configuration or editing of an existing goal, the first step is to access Analytics and click on the __Administrator__ button in the lower left corner. Then go to the __Goals__ option, from the "View" column.
 
-![image](https://images.ctfassets.net/alneenqid6w5/2lSqr5sq9cEJqQ8OrYeMrO/8bb8294a785ec55c4bc812780d010377/Screenshot_2019-10-28_14.59.53.png)
+![image](//images.ctfassets.net/alneenqid6w5/2lSqr5sq9cEJqQ8OrYeMrO/8bb8294a785ec55c4bc812780d010377/Screenshot_2019-10-28_14.59.53.png)
 
 In the goal administration screen, choose to create a new goal or to edit an existing one.
 
 __In step 1__ you can follow with a custom type goal:
 
-![image](https://images.ctfassets.net/alneenqid6w5/5vv17y3LYwEZ99E531Rw8E/0e73bbfed92a27dbc893aa1ab3f6cb2e/Screenshot_2019-10-28_15.01.15.png)
+![image](//images.ctfassets.net/alneenqid6w5/5vv17y3LYwEZ99E531Rw8E/0e73bbfed92a27dbc893aa1ab3f6cb2e/Screenshot_2019-10-28_15.01.15.png)
 
 __In step 2__ you can define the name you prefer for your goal and a position code (for internal Google Analytics use). In type, let's use "Destination":
 
-![image](https://images.ctfassets.net/alneenqid6w5/3TSWIxs5EPBQAfPYY4DKeD/f937330ad2fc5496c44a58acbc05f99d/Screenshot_2019-10-28_15.03.02.png)
+![image](//images.ctfassets.net/alneenqid6w5/3TSWIxs5EPBQAfPYY4DKeD/f937330ad2fc5496c44a58acbc05f99d/Screenshot_2019-10-28_15.03.02.png)
 
 __In step 3__ we have the most sensitive settings. In it we set the page that determines the completion of the goal and the path the clients will take to reach it.
 
 In the "Destination" field select the regular expression option and enter the URL of the order placed page: `^/checkout/orderPlaced`
 
-![image](https://images.ctfassets.net/alneenqid6w5/7foRf9TbRzb0pUNlXpqATQ/593d9162dfe76f4f8ab6a59eadbb330e/Screenshot_2019-10-28_15.04.07.png)
+![image](//images.ctfassets.net/alneenqid6w5/7foRf9TbRzb0pUNlXpqATQ/593d9162dfe76f4f8ab6a59eadbb330e/Screenshot_2019-10-28_15.04.07.png)
 
 Then configure the path that the client will go through until an order is finished. In such case, we're taking into account that the purchase process starts on the product screen; then my funnel will serve to measure the number of customers who access this screen, how many orders have been finished and at which step customers are giving up the purchase.
 
@@ -54,7 +54,7 @@ Still __in step 3__, enable the __Funnel__ option with the following steps:
 5. __Delivery__ = `^/checkout/(\?.*)?#/shipping$`
 6. __Payment__ = `^/checkout/(\?.*)?#/payment$`
 
-![image](https://images.ctfassets.net/alneenqid6w5/6W1evwkmfds3ok1h8Hjzsx/da9bef2d395db2170446ebd7d1df1dda/Screenshot_2019-10-28_15.06.24.png)
+![image](//images.ctfassets.net/alneenqid6w5/6W1evwkmfds3ok1h8Hjzsx/da9bef2d395db2170446ebd7d1df1dda/Screenshot_2019-10-28_15.06.24.png)
 
 One way to verify that the goal is set correctly is to use the "Check this goal" link. Google will generate a goal conversion simulation within the last 7 days.
 
diff --git a/docs/tutorials/en/setting-up-the-tnspay-gateway.md b/docs/tutorials/en/setting-up-the-tnspay-gateway.md
index 517dc81d5..4f44f5340 100644
--- a/docs/tutorials/en/setting-up-the-tnspay-gateway.md
+++ b/docs/tutorials/en/setting-up-the-tnspay-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up the TNSPay gateway'
 id: 6jIUr6Va00QyEuMEGAmQA6
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T12:43:42.795Z
-updatedAt: 2023-03-29T01:14:08.864Z
-publishedAt: 2023-03-29T01:14:08.864Z
+updatedAt: 2024-03-18T20:23:20.750Z
+publishedAt: 
 firstPublishedAt: 2018-03-02T15:56:49.389Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: setting-up-the-tnspay-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 TNSPay is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) with PCI certification that offers a number of security features to facilitate the processing of [recurring purchases](/en/faq/how-does-recurring-purchase-work).
 
 To configure TNSPay, follow the steps below:
diff --git a/docs/tutorials/en/setting-up-the-type-of-interest-rate.md b/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
index 82973edf4..7150488a9 100644
--- a/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
@@ -25,7 +25,7 @@ The payment method's ID can be configured to have Simple Interest Rates and is o
 - Select the Payment Condition that should be configured to use Simple Interest Rates
 - Copy the last URL parameter, which shows the ID of this Payment Method (see image)
 
-![ENjuros](https://images.ctfassets.net/alneenqid6w5/27ScAtFzUYwYm8y5zGqsEP/ae3915ad736e96121017aba11d87a522/ENjuros.png)
+![ENjuros](//images.ctfassets.net/alneenqid6w5/27ScAtFzUYwYm8y5zGqsEP/ae3915ad736e96121017aba11d87a522/ENjuros.png)
 
 ## Setting up the interest rate type using API
 
diff --git a/docs/tutorials/en/setting-up-the-voucher-list.md b/docs/tutorials/en/setting-up-the-voucher-list.md
index 09fda0744..b272e4129 100644
--- a/docs/tutorials/en/setting-up-the-voucher-list.md
+++ b/docs/tutorials/en/setting-up-the-voucher-list.md
@@ -26,14 +26,14 @@ To create this type of list, an SKU must be set up as follows:
 - The SKU price must be R$0.01.
 - The SKU must be set up to generate a credit voucher.
 
-![sku-opção-credito-vale en](https://images.ctfassets.net/alneenqid6w5/4CQusNMh8csmAs6qOkYAIi/07ea9ef632ca04b3e8b39c170732e18b/sku-op____o-credito-vale_en.png)
+![sku-opção-credito-vale en](//images.ctfassets.net/alneenqid6w5/4CQusNMh8csmAs6qOkYAIi/07ea9ef632ca04b3e8b39c170732e18b/sku-op____o-credito-vale_en.png)
 
 
 ## List Types Settings
 
 The creation of this type of list requires that in the List Types settings the delivery is marked as “Value of products purchased will be converted into a gift card voucher”. See the example image.
 
-![entrega-tipos-lista en](https://images.ctfassets.net/alneenqid6w5/3WBtZ9m8zSsUmaIgYaIUSq/00be0c7191f283fa2f4ef1abdab917b6/entrega-tipos-lista_en.png)
+![entrega-tipos-lista en](//images.ctfassets.net/alneenqid6w5/3WBtZ9m8zSsUmaIgYaIUSq/00be0c7191f283fa2f4ef1abdab917b6/entrega-tipos-lista_en.png)
 
 
 Save your list after you have defined all settings.
diff --git a/docs/tutorials/en/setting-up-the-worldpay-acquirer.md b/docs/tutorials/en/setting-up-the-worldpay-acquirer.md
index e510f3113..3df7f318e 100644
--- a/docs/tutorials/en/setting-up-the-worldpay-acquirer.md
+++ b/docs/tutorials/en/setting-up-the-worldpay-acquirer.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up the Worldpay acquirer'
+title: 'Setting up payments with Worldpay-Payments-Via-WPG'
 id: 7GCtigwhNYMi604UM0KeO6
 status: PUBLISHED
 createdAt: 2018-02-28T22:09:45.321Z
-updatedAt: 2023-03-29T00:47:52.166Z
-publishedAt: 2023-03-29T00:47:52.166Z
+updatedAt: 2024-03-18T17:20:43.467Z
+publishedAt: 2024-03-18T17:20:43.467Z
 firstPublishedAt: 2018-02-28T22:38:14.737Z
 contentType: tutorial
 productTeam: Financial
@@ -17,18 +17,31 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Worldpay is a global [acquirer](/en/tutorial/what-is-an-acquirer) which can process payments on various types of currencies and cards.
 
-To set Worldpay up, follow the steps below:
+To configure Worldpay, follow the steps below:
 
-## Setting up Worldpay gateway affiliation
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Worldpay-Payments-Via-WPG__ in the search bar and click on the name of the provider.
+4. Fill in the __App key__ and __App token__ fields with data provided by your account Worldpay.
+5. If you wish to modify the identification name to be displayed for the Worldpay provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. In __Payment Control__, select whether you want to activate the provider in a test environment by clicking __Enable test mode__.
+7. In the __Automatic settlement__ field, select one of the following option:
+<br>
+<ul>
+<br>
+    	<li><b>Use behavior recommended by the payment processor</b>: Capture is not automatic; it is scheduled according to the period specified by the acquirer. The acquirer indicates whether the payment has been authorized and can determine or recommend a number of days for the capture upon payment authorization. (This is the platform's default behavior).</li>
+    	<li><b>Automatic capture immediately after payment authorization</b>: Capture is automatically performed right after payment authorization, even if the transaction includes an anti-fraud analysis.</li>
+   		<li><b>Automatic capture immediately after anti-fraud analysis</b>: Capture is automatically performed right after payment authorization and anti-fraud analysis. If you select this behavior and do not have anti-fraud analysis, the system will perform the payment capture as in "Automatic capture immediately after payment authorization".</li>     
+   		<li><b>Disabled</b>: Capture takes place only when the order is invoiced. If you select this behavior, it is important to pay attention to the invoicing time, as invoicing can exceed the capture time agreed with the payment provider and lead to the cancellation of the transaction.</li>
+</ul>
+8. If you want to use [payment split](https://help.vtex.com/en/tutorial/split-payment--6k5JidhYRUxileNolY2VLx) in your store, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
 
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Worldpay__ Connector.
-4. Fill in the registration fields with your Worldpay account information (fields _UserName_, _Password_, _Version_, _MerchantCode_).
-5. In the __Currency__ field, choose the currency of the transactions.
-6. In the __Captura de segurança antecipada__ field, choose how long you want the capture to take place after the transactionapproval and the anti-fraud analysis. You can also disable this function.
-7. Click __Save__.
+9. If an alert message appears indicating the need to install the app, click on the `Install app` button and follow the installation instructions.
 
-## Setting up the payment condition
+10. Click `Save`.
 
-After following the steps indicated above, Worldpay will be configured in your store. So when you enter a payment condition, it will be available in the __Process with affiliation__ field (provided the payment method is part of the Worldpay acquiring network). To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+To configure the payment methods to be processed by Worldpay, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
+
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, Worldpay may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-the-yamisplitmoipv1-gateway.md b/docs/tutorials/en/setting-up-the-yamisplitmoipv1-gateway.md
index 1318088cc..6671ec6f3 100644
--- a/docs/tutorials/en/setting-up-the-yamisplitmoipv1-gateway.md
+++ b/docs/tutorials/en/setting-up-the-yamisplitmoipv1-gateway.md
@@ -3,8 +3,8 @@ title: 'Setting up the YamiSplitMoipV1 gateway'
 id: 5qrjr9yukwsk4oaMMAisSK
 status: PUBLISHED
 createdAt: 2018-02-28T16:56:41.540Z
-updatedAt: 2023-03-29T00:48:49.159Z
-publishedAt: 2023-03-29T00:48:49.159Z
+updatedAt: 2024-03-12T21:02:38.695Z
+publishedAt: 2024-03-12T21:02:38.695Z
 firstPublishedAt: 2018-02-28T21:48:56.044Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,19 @@ legacySlug: setting-up-the-yamisplitmoipv1-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-YamiSplitMoipV1 is a dedicated gateway that extends Moip functionality. With it, it's possible to make payment splits in the marketplaces (which allows the user to make a single payment, even buying products from different sellers) using the sub-acquirer.
+At VTEX, it is possible to integrate with the payment provider YamiSplitMoipV1. Through this provider, your store can make sales with credit cards and bank slips.
 
-## Setting up the gateway affiliation YamiSplitMoipV1
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __YamiSplitMoipV1__ Connector.
-4. Fill in the _Application Key_ and _Application Token_ fields with your __Moip__ account information.
-5. Click __Save__.
+To configure YamiSplitMoipV1, follow the steps below:
 
-## Setting up the payment condition
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __YamiSplitMoipV1__ in the search bar and click on the name of the provider.
+4. In __Provider Authorization__, fill in the __App Key__ and __App token__ fields with data provided by Moip.
+5. If you wish to modify the identification name to be displayed for the YamiSplitMoipV1 provider on the VTEX Admin screen, enter the information in the __Name__ field in __Basic Information__.
+6. Click `Save`.
 
-After following the steps above, YamiSplitMoipV1 will be configured in your store. Thus, while you are registering a payment condition to be used in a marketplace, it will be available in the __Process with affiliation__ field. 
+To configure the payment methods to be processed by YamiSplitMoipV1, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-To learn how to set payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
+
+After following the indicated steps, YamiSplitMoipV1 may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-vcmais-gateway.md b/docs/tutorials/en/setting-up-vcmais-gateway.md
index ee0ca2ba9..579416d5f 100644
--- a/docs/tutorials/en/setting-up-vcmais-gateway.md
+++ b/docs/tutorials/en/setting-up-vcmais-gateway.md
@@ -3,8 +3,8 @@ title: 'Setting up vcmais gateway'
 id: 28nAmwnfxWSoQEIO8EYYaI
 status: PUBLISHED
 createdAt: 2018-04-17T21:48:38.248Z
-updatedAt: 2023-03-29T00:43:23.712Z
-publishedAt: 2023-03-29T00:43:23.712Z
+updatedAt: 2023-10-18T12:07:58.261Z
+publishedAt: 2023-10-18T12:07:58.261Z
 firstPublishedAt: 2018-04-18T21:26:18.172Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: setting-up-vcmais-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-On the VTEX platform, you may set up VC+ [gateway](/en/tutorial/what-is-a-payment-gateway) to receive payments through promissory notes.
+On the VTEX platform, you may set up VC+ [gateway](/en/tutorial/what-is-a-payment-gateway) to receive payments through Notes Payable.
 
 To set VC+ up, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-vindi-gateway.md b/docs/tutorials/en/setting-up-vindi-gateway.md
index d823a7e80..698aeec2b 100644
--- a/docs/tutorials/en/setting-up-vindi-gateway.md
+++ b/docs/tutorials/en/setting-up-vindi-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: 'Setting up Vindi gateway'
+title: 'Setting up payments with Vindi '
 id: 61EXzfrBZYIgGU26EGcaMo
-status: DRAFT
+status: PUBLISHED
 createdAt: 2018-03-01T15:25:39.368Z
-updatedAt: 2022-12-23T20:47:23.110Z
-publishedAt: 
+updatedAt: 2024-01-23T21:49:28.618Z
+publishedAt: 2024-01-23T21:49:28.618Z
 firstPublishedAt: 2018-03-01T16:21:19.864Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,18 @@ legacySlug: setting-up-vindi-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Vindi is a payment gateway with PCI certification, which guarantees the security of the data transacted by it. Currently, it processes payments made with credit cards, bank slips and Paypal.
+At VTEX, it is possible to integrate with the Vindi payment provider. With this provider, your store can make sales through the credit cards, bank slips and Paypal.
 
-To set Vindi up, follow the steps below:
+To configure Vindi, follow the steps below:
 
-## Setting up Vindi gateway affiliation
-1. Enter the __Payments__ module.
-2. Click __Settings__.
-3. On the __Gateway Affiliations__ tab, click the __+__ button.
-4. Click the __Vindi__ connector.
-5. Fill in the registration fields with the data provided by Vindi (_Application Key_ and _Application Token_ fields).
-6. Click __Save__.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __Vindi__ in the search bar and click on the name of the provider.
+4. Fill in the __Application Key__ and __Application Token__ fields with the data provided by Vindi.
+5. Click `Save`.
 
-## Setting up the payment condition
+To configure the payment methods to be processed by Vindi, access [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455#).
 
-After following the steps above, Vindi will be configured in your store. Thus, while you're registering a payment condition, this gateway will be available in the __Process with affiliation__ field (provided that the payment methods are compatible with Vindi). 
+To set special conditions on payment methods, go to [Configuring payment special conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456#).
 
-To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
+After following the indicated steps, Vindi provider may take up to 10 minutes to appear at your store's checkout as a payment option.
diff --git a/docs/tutorials/en/setting-up-webpay2p-gateway.md b/docs/tutorials/en/setting-up-webpay2p-gateway.md
index bf26e5dc9..0b049aa44 100644
--- a/docs/tutorials/en/setting-up-webpay2p-gateway.md
+++ b/docs/tutorials/en/setting-up-webpay2p-gateway.md
@@ -3,8 +3,8 @@ title: 'Setting up WebPay2P gateway'
 id: 34Bn1nOoVO6iesWAgSEQQA
 status: PUBLISHED
 createdAt: 2018-04-02T19:30:48.720Z
-updatedAt: 2021-07-07T17:45:55.414Z
-publishedAt: 2021-07-07T17:45:55.414Z
+updatedAt: 2024-03-07T13:50:16.754Z
+publishedAt: 2024-03-07T13:50:16.754Z
 firstPublishedAt: 2018-04-02T19:46:03.221Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/setup-safetypay.md b/docs/tutorials/en/setup-safetypay.md
index c50301696..611cc4084 100644
--- a/docs/tutorials/en/setup-safetypay.md
+++ b/docs/tutorials/en/setup-safetypay.md
@@ -1,10 +1,10 @@
 ---
 title: 'Setting up the SafetyPay gateway'
 id: lf89DOdeveuMOI4Q0CwgC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-22T13:57:16.523Z
-updatedAt: 2023-03-29T00:44:35.344Z
-publishedAt: 2023-03-29T00:44:35.344Z
+updatedAt: 2024-03-18T19:57:00.504Z
+publishedAt: 
 firstPublishedAt: 2018-02-22T15:12:57.862Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: setup-safetypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+
 SafetyPay is a payment solution that directly connects your store's checkout to your customer's bank. With it, your customer chooses SafetyPay as a payment method and is *redirected* to the secure internet banking environment you choose. Once redirected, the customer can make a bank transfer and pay for the order.
 
 To set up SafetyPay, follow the steps below:
 
-## Setting up SafetyPay gateway affiliation
-
-1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
-2. On the __Gateway Affiliations__ tab, click the __+__ button.
-3. Click the __Safety Pay__ connector.
+1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
+2. On the providers screen, click the `New Provider` button.
+3. Type the name __SafetyPay__ in the search bar and click on the name of the provider.
 4. Fill in the registration fields with the data provided by SafetyPay (Fields *ApiKey, SignatureKey, Custom Merchant Name*).
 5. The __Tracking Code__ field is optional. It can be used for marketing analysis purposes.
 6. In the __Product ID__ field, fill in the desired payment method: __Express__ for bank transfer or __Cash__ for cash payment.
@@ -31,7 +31,7 @@ To set up SafetyPay, follow the steps below:
 8. In __Language__, choose the language that will be used in the UI.
 9. In the __Time To Expire (in hours)__ field, choose the payment expiration time.
 10. In __Time To Expire for Lottery Payment (in days)__, choose the expiration time for payments to be made in lottery (applies only to Brazil).
-11. Click __Save__.
+11. Click `Save`.
 
 ## Setting up the SafetyPay payment condition
 
diff --git a/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md b/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
index 02d10ebcf..977373bde 100644
--- a/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
+++ b/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
@@ -3,8 +3,8 @@ title: 'Shared information between a marketplace and a seller on VTEX'
 id: 3o7WGiBtfnKKZ3Ddug26k3
 status: PUBLISHED
 createdAt: 2022-04-07T13:32:06.199Z
-updatedAt: 2023-04-17T21:51:10.740Z
-publishedAt: 2023-04-17T21:51:10.740Z
+updatedAt: 2023-10-31T19:54:13.803Z
+publishedAt: 2023-10-31T19:54:13.803Z
 firstPublishedAt: 2022-04-07T14:23:25.578Z
 contentType: tutorial
 productTeam: Channels
@@ -44,7 +44,7 @@ Also, to [add the seller](https://help.vtex.com/en/tutorial/configurando-seller)
 You can integrate a VTEX marketplace with a VTEX seller or with an external seller either through the VTEX Admin or through API. In either case, the information shared between the marketplace and the seller will be the same.
 
 <div class = "alert alert-info">
-For more information on how to connect a VTEX marketplace to a VTEX seller using the VTEX Admin, please check out the article <a href="https://help.vtex.com/en/tutorial/configurando-seller">Adding a seller</a>. For integration via API use the call <a href="https://developers.vtex.com/vtex-rest-api/reference/upsertsellerrequest">Configure Seller Account</a>. For external sellers, check out the <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">External Seller Integration Guide</a>.
+For more information on how to connect a VTEX marketplace to a VTEX seller using the VTEX Admin, please check out the article <a href="https://help.vtex.com/en/tutorial/configurando-seller">Adding a seller</a>. For integration via API use the call <a href="https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers">Configure Seller Account</a>. For external sellers, check out the <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">External Seller Integration Guide</a>.
 </div>
 
 ### Connecting a VTEX marketplace to a VTEX seller
@@ -75,14 +75,14 @@ An external seller not hosted on the VTEX environment will have to provide the V
 
 Once the VTEX marketplace and the VTEX seller, or the external seller, are connected, the marketplace can access the seller information through the VTEX Admin, in **MARKETPLACE > Management**.
 
-The information provided by the seller, whether it is a VTEX seller or an external one, can be requested via API, using the call [Get Seller data by ID](https://developers.vtex.com/vtex-rest-api/reference/getretrieveseller).
+The information provided by the seller, whether it is a VTEX seller or an external one, can be requested via API, using the call [Get Seller data by ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-).
 
 ## Sharing customer emails
 
 The marketplace can give the seller partial access to the email addresses of its customer base, in order to use them for query requests to commercial conditions and for order creation. This is not a standard configuration, and this information is managed via API using the following calls in the `trustPolicy` field:
 
-- [Configure Seller Account](https://developers.vtex.com/vtex-rest-api/reference/upsertsellerrequest): this allows setting up the seller account, whether it is a VTEX seller or an external one.
-- [Update Seller by Seller ID](https://developers.vtex.com/vtex-rest-api/reference/updateseller): this allows updating the seller information, whether it is a VTEX seller or an external one.
+- [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers): this allows setting up the seller account, whether it is a VTEX seller or an external one.
+- [Update Seller by Seller ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#patch-/seller-register/pvt/sellers/-sellerId-): this allows updating the seller information, whether it is a VTEX seller or an external one.
 
 <div class = "alert alert-info">
 For orders placed in the marketplace, the customer email is not displayed to the seller. The customer establishes a relationship with the marketplace. Therefore, the customer's consent would be necessary for sharing their information.
diff --git a/docs/tutorials/en/shipping-options-beta.md b/docs/tutorials/en/shipping-options-beta.md
index d55a0e764..041b7bf3c 100644
--- a/docs/tutorials/en/shipping-options-beta.md
+++ b/docs/tutorials/en/shipping-options-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Shipping Options (Beta)'
 id: 7gsdck3519Z3VPqzwFFHJL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-05-27T15:35:44.505Z
-updatedAt: 2023-03-21T17:44:07.634Z
-publishedAt: 2023-03-21T17:44:07.634Z
+updatedAt: 2023-08-14T17:28:57.629Z
+publishedAt: 
 firstPublishedAt: 2022-05-31T18:53:28.695Z
 contentType: tutorial
 productTeam: Others
@@ -93,7 +93,7 @@ Follow the steps below to create a shipping option:
     - **Free shipping:** Free of charge for the consumer; no additional configuration is required.
 8. Click `Save`.
 
-![opcoes_envio_criacao_en](https://images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/3f6e3be89d0d3b4c22216df25aa2c875/opcoes_envio_criacao_en.png)
+![opcoes_envio_criacao_en](//images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/3f6e3be89d0d3b4c22216df25aa2c875/opcoes_envio_criacao_en.png)
 
 ## Editing a shipping option
 
@@ -117,7 +117,7 @@ Besides editing a shipping option from the menu icon <i class="fas fa-ellipsis-v
 
 Once you have configured the shipping options, they will be listed under **Store Settings > Shipping > Shipping Options**, as shown in the following image:
 
-![opcoes_envio_listagem_en](https://images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/7c6c0928864ee46602bdf7799c9f00b1/opcoes_envio_listagem_en.png)
+![opcoes_envio_listagem_en](//images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/7c6c0928864ee46602bdf7799c9f00b1/opcoes_envio_listagem_en.png)
 
 The table below contains the description of the columns shown:
 
diff --git a/docs/tutorials/en/shipping-policy.md b/docs/tutorials/en/shipping-policy.md
index 46a26670e..b93d62436 100644
--- a/docs/tutorials/en/shipping-policy.md
+++ b/docs/tutorials/en/shipping-policy.md
@@ -3,8 +3,8 @@ title: 'Shipping policy '
 id: tutorials_140
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:12.502Z
-updatedAt: 2023-03-29T18:19:38.883Z
-publishedAt: 2023-03-29T18:19:38.883Z
+updatedAt: 2024-01-31T01:24:50.628Z
+publishedAt: 2024-01-31T01:24:50.628Z
 firstPublishedAt: 2017-04-27T23:00:45.247Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,72 +15,44 @@ legacySlug: adding-a-carrier, manage-carrier
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
+[Shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) is a set of essential [logistics](https://help.vtex.com/en/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) settings in a VTEX store, which refers to the combination of the following aspects:
 
-A shipping policy is a set of rules that define the shipping options and conditions that will be displayed to the customer at checkout. Shipping conditions include the information you have configured for carrier working hours, delivery time frames, additional shipping rates, types of deliverable products (modals), and delivery windows.
+1. Shipping policy
+2. [Warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+3. [Loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
 
- These settings are based primarily on the contracts between your store and[ carriers](https://help.vtex.com/en/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE), service providers, or any other type of contract for shipping services that your store offers to customers.
+The image below shows how these concepts relate to each other:
 
- <div class="alert alert-info"> 
-A single carrier can be linked to multiple shipping policies, each with its particularities. See below how to create, edit, and delete shipping policies
-</div>
+![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
 
-On the VTEX platform, you can:
+**Shipping policy** is a set of rules and settings that specify the shipping options that will be displayed to customers at checkout. When calculating the [shipping time for an order](https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116), the VTEX platform takes into account several settings from the shipping policy, including:
 
-* [Add shipping policies](#adding-a-shipping-policy)
+* [Carrier](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE)
+* [Carrier business hours](https://help.vtex.com/en/tutorial/horario-de-funcionamento-das-transportadoras--2oGpbInIgdxSWUi3TZjdCS)
+* [Holidays](https://help.vtex.com/en/tutorial/cadastrar-feriados--2ItOthSEAoyAmcwsuiO6Yk)
+* [Additional shipping costs](https://help.vtex.com/en/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV)
+* [Scheduled delivery](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)
+* [Pickup points](https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R)
 
-* [Edit shipping policies](#editing-a-shipping-policy)
+To learn how to create a shipping policy, check the [Creating a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) article. For information on management, read the [Managing shipping policies](https://help.vtex.com/en/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE) article.
 
-* [Delete shipping policies](#deleting-a-shipping-policy)
+## Shipping policy and shipping rate template
 
-## Adding a shipping policy
+Every shipping policy is associated with a [shipping rate template](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127), where you enter information such as:
 
-1. In the VTEX Admin, go to **Shipping > Shipping Strategy > Shipping Policies**, or type *Shipping Strategy* in the search bar at the top of the page.  
-2. Click on the `Create shipping policy` button.
-3. Fill in the fields on the screen and click on `Save changes`.
-*    **Active/Inactive**: enables or disables the shipping policy.
-*   **Name**: the internal name of the shipping policy.
-*   **ID**: the internal identifier also used for integrators. You must fill in this field only with letters and numbers. If it is not filled in, an ID will be created automatically.
-*   **[Shipping method](https://help.vtex.com/en/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126)**: the delivery type,  which is used to differentiate delivery services. It will be displayed for customers at checkout. For example, express vs. standard shipping.
-*   **[Upload shipping rates](https://help.vtex.com/en/tutorial/como-montar-a-planilha-de-frete--tutorials_127)**: this is where you upload the spreadsheet with the shipping rates and delivery time frames based on the shipping policy.
-*   **[Package dimensions](https://help.vtex.com/en/tutorial/como-funciona-o-empilhamento--tutorials_124):**
-    *   **Sum of all dimensions:** size limit of the package. It considers the sum of the lengths of all edges of the box. If this limit is exceeded, the order will be split into two or more packages or the delivery will not be made. This information is given by the carrier when the contract is signed.
-    *   **Largest edge:** size limit of the largest edge of the package. If this limit is exceeded, the order will be split into two or more packages or the delivery will not be made.
-    *   **[Cubic weight factor](https://help.vtex.com/en/tutorial/como-o-peso-cubado-e-calculado--tutorials_128)**: the factor that will be used to calculate the dimensional weight of the package. The sum of measures divided by the cubic factor.
-    *   **Minimum weight factor:** use the cubic weight only if it exceeds this value. If this is the case, the cubic weight will be considered for calculating the shipping rate.
-*   **Weekends and holidays:** days on which deliveries can be made. Click the toggles to enable or disable delivery in the following scenarios: `Saturday Delivery`, `Sunday Delivery`, `Holiday Delivery`.
-*   **[Active modals](https://help.vtex.com/en/tutorial/como-funciona-o-modal--tutorials_125):** specifications for products that require special delivery. They indicate product shipping limitations covered by the shipping policy. Check the boxes to enable delivery in the following scenarios: `chemicals`, `electronics`, `furniture`, `glass`, `liquids`, `mattresses`, `refrigerated products`, `tires`,`appliances`, and `firearms`.
-*   **Package items:** specification of the price and number of items in the package.
-    *    **Minimum value:** minimum shipment price accepted by the shipping policy to make the delivery.
-    *   **Minimum of Items:** minimum multiple of the quantity of items accepted by the carrier. For example, if the value is **3**, it means that the carrier only ships items with quantities multiple of three (3, 6, 9, 21...).
-    *   **Maximum value:** the maximum shipment price accepted by the shipping policy to make the delivery.
-*   **Link pickup points:** Click the toggle to view the pickup point options. Choose one of the options and fill it in by clicking on its dropdown menu. You can select between `Pickup points tags`, `Pickup points names`, or `Import sellers' pickup point` that have been previously configured in your store.
-*   **[Business hours:](https://help.vtex.com/en/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS)** the time frames in which the carrier ships items to customers and the times at which it picks up items for delivery, as specified in the shipping policy. These settings influence the calculation of delivery time.
-    *    **Shipping window:** here you can add the time frames in which the carrier ships items to customers. To configure it, select the `Shipping window` card.
-        *    `Accept purchases outside working hours`: click the toggle button to enable or disable the option to receive orders outside working hours. When this option is enabled and an order is placed outside working hours, the time until the next available shipping window will be added to the total delivery time.
-        *   Select the `Day of the week`, the `Start time`, and the `End time`.
-        *   To add more days of the week, click on `Add shipping window`.
-    *    **Pickup time:** here you can add the times at which the carrier will pick up packages from your warehouse or distribution center to send them to end customers. If an order is placed after the pickup time, the time until the next available pickup time will be added to the total delivery time.
-        *   Select the `Day of the week` and the `Pickup time`.
-        *   To add more days of the week, click on `Add pickup time`.
-*   **[Scheduled delivery](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)**: this feature can be enabled if this service is included in your shipping policy. Here you must add the delivery windows that will be displayed to customers at checkout. To use this feature, click the toggle and fill in the following fields:
-    *    **Maximum delivery time:** the maximum number of days to deliver a product.
-    *   **Delivery windows:** the time frames during which the carrier delivers packages to customers. Set the days of the week, the `Start` and `End` times, and any additional rates. Click `Add delivery window` to set more time frames.
-    *   **Delivery capacity:** allows you to limit how many items/orders can be delivered in each delivery window. This feature is optional.   To learn more about these features, check out the articles[Scheduled delivery](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) and [Managing delivery capacity](https://help.vtex.com/en/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz). If you enable this feature, you must:
-        *   Choose a delivery capacity unit (`items` or `orders`).
-        *   Check the delivery windows.
-        *   Define the `delivery capacity`. We recommend choosing the delivery capacity unit and the maximum number of items carefully because the system does not consider the number of items in the cart to calculate the delivery window availability. So if a delivery window has a remaining capacity of 2 items and your customer is buying 4 items, they will be able to select this delivery window.
+* Carrier identification
+* Carrier shipping cost
+* Postal code ranges or [polygons](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138) valid for shipping
 
-            Once the delivery window has reached its full `delivery capacity` it will no longer be available to customers. To make a delivery window available to customers again, you must increase the number of items/orders in its `delivery capacity`.
+Once the shipping rate template is associated with the shipping policy, this information becomes part of your VTEX logistics operation.
 
-## Editing a shipping policy
+## Initial logistics settings
 
-1. In the VTEX Admin, go to **Shipping > Shipping Strategy > Shipping Policies**, or type *Shipping Strategy* in the search bar at the top of the page.  
-2. Click on the `shipping policy` you want to edit.
-3. Edit `the content you want to change` (the fields are described in Adding a shipping policy) and save.
+You can configure initial settings through the VTEX Admin or via API. If you are starting to configure your [shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), we recommend the following order:
 
-## Deleting a shipping policy
+| **Topic** | **Configuration via VTEX Admin** | **Configuration via API** |
+| :--- | :--- | :--- |
+| 1. Shipping policy | [Creating a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| 2. [Warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) | [Managing warehouses](https://help.vtex.com/en/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| 3. [Loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) | [Managing loading docks](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
 
-1. In the VTEX Admin, go to **Shipping > Shipping Strategy > Shipping Policies**, or type *Shipping Strategy* in the search bar at the top of the page.  
-2. Hover the mouse pointer over the shipping policy you want to delete.
-3. Click on the trash can icon.
-4. Click on the `Delete` button.
diff --git a/docs/tutorials/en/shipping-rate-template.md b/docs/tutorials/en/shipping-rate-template.md
index 8ffe35393..1d19bca35 100644
--- a/docs/tutorials/en/shipping-rate-template.md
+++ b/docs/tutorials/en/shipping-rate-template.md
@@ -3,8 +3,8 @@ title: 'Shipping rate template'
 id: tutorials_127
 status: PUBLISHED
 createdAt: 2019-02-22T19:36:18.509Z
-updatedAt: 2023-03-29T18:18:59.537Z
-publishedAt: 2023-03-29T18:18:59.537Z
+updatedAt: 2023-10-10T13:26:19.271Z
+publishedAt: 2023-10-10T13:26:19.271Z
 firstPublishedAt: 2019-02-22T19:36:22.375Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -121,7 +121,7 @@ See below the spreadsheet columns content to understand each field in detail.
             <td class="t-body pa5" style="min-width: 15rem;">
                 <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">PricePercent</span>
             </td>
-            <td class="t-body pa5" style="min-width: 15rem;"> <a href="https://help.vtex.com/en/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV"> Price-based additional shipping charge</a>, calculated based on the total price of the order, in decimal number. You must fill in this field with a percentage value. For example, for an additional charge of 10%, fill in the table with 10.
+            <td class="t-body pa5" style="min-width: 15rem;"> <a href="https://help.vtex.com/en/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV"> Price-based additional shipping charge</a> calculated in decimal number based on the total price of the products in the shopping cart. You must fill in this field with a percentage value. For example, for an additional charge of 10%, fill in the table with 10.
             </td>
             <td class="t-body pa5" style="min-width: 15rem;"> <a href="https://help.vtex.com/en/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">Additional shipping costs</a> will be added to the fixed cost.
             </td>
@@ -179,7 +179,7 @@ We used the term "weight" when referring to "mass" in this documentation for rea
 </div>
 
 Here is an example of how to fill in the fields in the spreadsheet.
-![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
+![modelo_planilhanumerica](//images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
 
 ## Upload the spreadsheet in VTEX Admin
 
@@ -192,7 +192,7 @@ Follow the steps below:
 4. In both cases, download the spreadsheet and [complete its fields](#fill-in-the-fields-in-the-spreadsheet). Then, upload the file in the **Upload shipping rates** section, as illustrated in the image below.
 5. After completing these steps, click on `Save changes`.
 
-![upload tarifas envioEN](https://images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/38cfc78b89a4e0e68bfec882af0ea9f4/upload_tarifas_envioEN.png)
+![upload tarifas envioEN](//images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/38cfc78b89a4e0e68bfec882af0ea9f4/upload_tarifas_envioEN.png)
 
 <div class="alert alert-warning">
 For <b>new</b> shipping policies, other steps are required. Check out the article <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy</a> for more information.
diff --git a/docs/tutorials/en/shipping-rates.md b/docs/tutorials/en/shipping-rates.md
index c9aeb74d5..24aa4d24b 100644
--- a/docs/tutorials/en/shipping-rates.md
+++ b/docs/tutorials/en/shipping-rates.md
@@ -21,7 +21,7 @@ Shipping rates are the shipping options your store offers to customers, and they
 The <a href="https://help.vtex.com/en/tutorial/total-shipping-cost--5bwhIO108VA5Y2YOpef9lV">total shipping cost</a> to the customer includes the shipping rate, <a href="https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV">additional shipping costs</a> and, a loading dock fee.
 </div>
 
-![Tarifa envio EN](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
+![Tarifa envio EN](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
 
 You can add shipping rates in the Admin by using:
 
diff --git a/docs/tutorials/en/shipping-simulation.md b/docs/tutorials/en/shipping-simulation.md
index a7fb21b7c..63e00fa8b 100644
--- a/docs/tutorials/en/shipping-simulation.md
+++ b/docs/tutorials/en/shipping-simulation.md
@@ -3,8 +3,8 @@ title: 'Shipping Simulator'
 id: tutorials_144
 status: PUBLISHED
 createdAt: 2017-04-27T22:16:36.879Z
-updatedAt: 2023-03-29T19:24:17.032Z
-publishedAt: 2023-03-29T19:24:17.032Z
+updatedAt: 2024-06-18T19:48:13.737Z
+publishedAt: 2024-06-18T19:48:13.737Z
 firstPublishedAt: 2017-04-27T23:00:45.450Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -41,7 +41,7 @@ There may be a discrepancy between the final price indicated by the simulator an
  6. Select the SKU `quantity`.  
  7. Fill in the `Price`. This field is optional.
 
- > The simulator does not take into account the price given in the Catalog module. Therefore, the rate indicated by the simulator does not consider any current promotion for those SKUs, and may indicate a rate that is different from the real rate in your store. We suggest that you manually enter the SKU’s exact rate with the applied promotions, so that the simulator returns an accurate calculation.*
+ > The simulator does not take into account the price registered in the Catalog module. Therefore, the calculation does not consider any current promotions for those SKUs, or shipping taxes for the shopping cart price, if there is any. This may result in a different rate from the real one in your store. To avoid this, we suggest that you manually enter the SKU’s exact rate with the applied promotions, which will make the simulator result more accurate.
 
  8. Click on the `+` icon to add more than one product to the simulation.
 If you want, you can check the `Simulate items individually` box.
@@ -60,7 +60,7 @@ The items measurements in the simulation result appear in centimeters and grams;
 
 ## Simulation details
 
-The shipping simulation shows all the shipping possibilities and availability for the items included in the simulation and describes [delivery details for an order](https://help.vtex.com/tutorial/ver-detalhes-de-entrega-de-um-pedido?locale=en) or shipping cost and delivery time taking into account the factors below.
+The shipping simulation shows all the shipping possibilities and availability for the items included in the simulation and describes [delivery details for an order](https://help.vtex.com/en/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl) or shipping cost and delivery time taking into account the factors below.
 
 * **Excluded carriers**: when running the simulation, some carriers may be unavailable because they do not meet the [Shipping Policy’s](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) criteria  (see[excluded carriers](#excluded-carrier) for more information).
 * **Simulation sharing**: the simulation can be shared by clicking `share shipping simulation` in the upper right corner of the page. When you click, a share link is copied to your clipboard. This feature makes it easy to get the VTEX team, or your store’s team, to resolve issues on specific orders. Only users who have access to the VTEX environment can view the share link.
diff --git a/docs/tutorials/en/shipping-strategy.md b/docs/tutorials/en/shipping-strategy.md
index edf44d0d8..d46e3627d 100644
--- a/docs/tutorials/en/shipping-strategy.md
+++ b/docs/tutorials/en/shipping-strategy.md
@@ -3,8 +3,8 @@ title: 'Shipping strategy'
 id: 58vLBDbjYVQzJ6rRc5QNz3
 status: PUBLISHED
 createdAt: 2021-07-15T17:04:23.563Z
-updatedAt: 2021-09-23T22:21:40.782Z
-publishedAt: 2021-09-23T22:21:40.782Z
+updatedAt: 2024-01-31T15:00:05.216Z
+publishedAt: 2024-01-31T15:00:05.216Z
 firstPublishedAt: 2021-07-15T17:27:37.590Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 The shipping strategy refers to the relationship between inventory, loading dock and shipping policy. The way they communicate will define the structure combination for shipping your customers’ orders. 
 
-![EstrategiaEnvio_EN](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/950f5a0342bba5b62dcd0bee100e8a71/Frame_2__3_.svg)
+![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
    <tr class="bb b--muted-3">
@@ -29,7 +29,7 @@ The shipping strategy refers to the relationship between inventory, loading dock
     </tr>
     <tr class="bb b--muted-3">
             <td class="t-body pa5" style="min-width: 15rem;">
-                <b><a href="https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj">Loading dock;</a></b>
+                <b><a href="https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj">Loading dock</a></b>
             </td>
             <td class="t-body pa5" style="min-width: 15rem;">Where goods are loaded onto trucks to be delivered or distributed. Operates as a product storage area.
             </td>
@@ -43,14 +43,12 @@ The shipping strategy refers to the relationship between inventory, loading dock
     </tr>
 </table>
 
-<div class="alert alert-warning">
-For the logistics system to work as expected, we suggest that you configure it in the following order:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Trade policy;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy;</a></li>
-<li><a href="https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj">Loading dock;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Warehouse.</li></a>
-</ol>
-</body>
-</div>
+## Initial logistics settings
+
+You can configure initial settings through the VTEX Admin or via API. If you are starting to configure your shipping strategy, we recommend the following order:
+
+| **Topic** | **Configuration via VTEX Admin** | **Configuration via API** |
+| :--- | :--- | :--- |
+| 1. [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) | [Creating a shipping policy](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| 2. [Warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) | [Managing warehouses](https://help.vtex.com/en/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| 3. [Loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) | [Managing loading docks](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
diff --git a/docs/tutorials/en/shopee-integration.md b/docs/tutorials/en/shopee-integration.md
index dfc5a990d..dcbb4aa96 100644
--- a/docs/tutorials/en/shopee-integration.md
+++ b/docs/tutorials/en/shopee-integration.md
@@ -3,8 +3,8 @@ title: 'Shopee Integration'
 id: 5OV9idUY6fHu3P8grnCnqj
 status: PUBLISHED
 createdAt: 2022-09-05T19:33:02.717Z
-updatedAt: 2022-12-08T20:41:49.398Z
-publishedAt: 2022-12-08T20:41:49.398Z
+updatedAt: 2024-04-17T16:10:43.661Z
+publishedAt: 2024-04-17T16:10:43.661Z
 firstPublishedAt: 2022-09-06T01:42:40.106Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/site-editor-overview.md b/docs/tutorials/en/site-editor-overview.md
index 411e6ca17..b1cc2d9d5 100644
--- a/docs/tutorials/en/site-editor-overview.md
+++ b/docs/tutorials/en/site-editor-overview.md
@@ -23,7 +23,7 @@ Site Editor is a graphical interface for managing your storefront content. It al
 
 In your VTEX Admin, access **Storefront > Site Editor** and you’ll see the main tools available in the graphical interface.
 
-![Site Editor - EN](https://images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/216b3664d5d3f8b6d901a0b8cf427906/site-editor-ui-en.png)
+![Site Editor - EN](//images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/216b3664d5d3f8b6d901a0b8cf427906/site-editor-ui-en.png)
 
 | **Tool**    | **Description** |
 | ----------  | ----------    |
diff --git a/docs/tutorials/en/sku-bindings.md b/docs/tutorials/en/sku-bindings.md
index 943bf9f6a..2e08621d7 100644
--- a/docs/tutorials/en/sku-bindings.md
+++ b/docs/tutorials/en/sku-bindings.md
@@ -1,10 +1,10 @@
 ---
 title: 'SKU Bindings'
 id: 1SmrVgNwjJX17hdqwLa0TX
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-27T17:27:26.963Z
-updatedAt: 2023-05-25T15:51:50.053Z
-publishedAt: 2023-03-31T19:05:52.334Z
+updatedAt: 2024-01-23T15:50:13.022Z
+publishedAt: 2024-01-23T15:50:13.022Z
 firstPublishedAt: 2022-05-31T17:14:23.589Z
 contentType: tutorial
 productTeam: Channels
@@ -27,7 +27,7 @@ By default, <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlG
 
 The **SKU Bindings** page allows the marketplace to track and manage the binding relationship between the seller’s SKUs and the ones from the marketplace. To access the page, go to the VTEX Admin, **Marketplace > Sellers > SKU Bindings**. You'll see the following interface:
 
-![sku-bindings-en](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/9a76d4471db1707286f7464e19cadcb8/sku-bindings-en.png)
+![sku-bindings-en](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/9a76d4471db1707286f7464e19cadcb8/sku-bindings-en.png)
 
 The following table contains a description of the columns in the SKU binding list:
 
diff --git a/docs/tutorials/en/sku-price-change.md b/docs/tutorials/en/sku-price-change.md
index 771ec08af..392d73e63 100644
--- a/docs/tutorials/en/sku-price-change.md
+++ b/docs/tutorials/en/sku-price-change.md
@@ -3,8 +3,8 @@ title: "Changing a SKU's price"
 id: tutorials_95
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:48.759Z
-updatedAt: 2023-03-30T16:36:10.950Z
-publishedAt: 2023-03-30T16:36:10.950Z
+updatedAt: 2024-01-05T17:59:41.793Z
+publishedAt: 2024-01-05T17:59:41.793Z
 firstPublishedAt: 2017-04-27T23:00:42.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -35,14 +35,14 @@ This updating normally occurs where a quick adjustment is needed to the SKU pric
 2. Enter the ID of the SKU whose **SKU** field you wish to change in **Search**.
 3. Click on the SKU desired. 
 4. Add the **Cost Price ($)** + **Initial Markup (%)** = **Base Price (final value of product to consumer)**.
-5. The information will automatically be saved by closing the tab 
+5. The information will automatically be saved by closing the tab. 
 
 ## Fields of the SKU price change form
 
 These fields represent the information that is changed in any of the three manners mentioned. The difference is that whoever enters data manually, sees this form, when importing a spreadsheet, arranged in columns, while in the case of integration the request structure shows fields in the JSon format.
 
-- **ID:** code of the SKU you accessed
-- **SKU:** name of the SKU
+- **ID:** code of the SKU you accessed.
+- **SKU:** name of the SKU.
 - **Parceiro (utm\_source):** Optional field. This is a parameter for conditioning differentiated pricing, by using it on the site of the utm source registered here.
 - **Campaign Audience (utm\_campaign):** Optional field. This is a parameter for conditioning differentiated pricing, by using it on the site of the utm campaign registered here, which can also be used in e-mail marketing links.
 - **Internal Campaign Audience (utmi\_cp):** Optional field. This is a parameter for conditioning differentiated pricing, by using it on the site of the utm source registered here. Normally used for store employees, when it’s the case of having differentiated purchase conditions.
@@ -77,26 +77,24 @@ Once the e-mail arrives and you download it, only change those SKUs that really
 
 These are the spreadsheet columns that arrive at the user’s e-mail upon export, as mentioned in the step-by-step procedure above. The text below is exactly how it appears in the spreadsheet. The mandatory completion of each column abides by the same standard as the fields of the form described in the topic mentioned above.
 
-- **StockKeepingUnitId:** id of the SKU;
-- **Source:** utm\_source;
-- **Price:** product selling price;
-- **Id:** Price ID. Do not change this value, otherwise the system will create a new line on the price table and two prices will be registered for the SKU;
-- **StoreId:** id of the sales policy in which the price will be applied. If you have any doubts about the identification code of any policy, access the module E-Commerce &gt; Marketplace &gt; Política Comercial. Check the number that appears in the “Id – Nome” column, this is the code that should be used here;
-- **Medium (Disregard):** Discontinued field;
-- **Campaign:** utm\_campaign;
-- **InternalCampaign:** utmi\_cp;
+- **StockKeepingUnitId:** id of the SKU.
+- **Source:** utm\_source.
+- **Price:** product selling price.
+- **Id:** Price ID. Do not change this value, otherwise the system will create a new line on the price table and two prices will be registered for the SKU.
+- **StoreId:** id of the sales policy in which the price will be applied. If you have any doubts about the identification code of any policy, access the module E-Commerce &gt; Marketplace &gt; Política Comercial. Check the number that appears in the “Id – Nome” column, this is the code that should be used here.
+- **Medium (Disregard):** Discontinued field.
+- **Campaign:** utm\_campaign.
+- **InternalCampaign:** utmi\_cp.
 - **DateFrom:** initial effective date for the price. Fill out in the dd/mm/yyyy format.
 - **DateTo:** final effective date for the price. Fill out in the dd/mm/yyyy format.
-- **ListPrice:** price of, also known as the list price. It is the one that appears crossed out (e.g.: De: R$ 10,00) on the site;
-- **RefId (Unchangeable):** product reference code, as per the product registration. Do not change this value;
-- **Ean13Default (Unchangeable):** product ean, as per the product registration. Do not change this value;
-- **BrandName (Unchangeable):** product brand name, as per the product registration. Do not change this value;
-- **StockKeepingUnitName (Unchangeable):** name of the SKU, as per the product registration. Do not change this value;
+- **ListPrice:** price of, also known as the list price. It is the one that appears crossed out (e.g.: From: $ 10,00) on the site.
+- **RefId (Unchangeable):** product reference code, as per the product registration. Do not change this value.
+- **Ean13Default (Unchangeable):** product ean, as per the product registration. Do not change this value.
+- **BrandName (Unchangeable):** product brand name, as per the product registration. Do not change this value.
+- **StockKeepingUnitName (Unchangeable):** name of the SKU, as per the product registration. Do not change this value.
 - **SellerId:** id of the seller who owns the product. This will only be pre-populated in the event your store is the marketplace of another store.
 
 ## Through integration with ERP
 
-This is usually configured when your store is being set up, and you and your technical team must follow the integration manual to avoid inconsistent integrations or any problem that might adversely affect the information that will be fed into the platform. The price is updated via REST, using the POST method, with the body in the JSon standard.
+This is usually configured when your store is being set up, and you and your technical team must follow the integration manual to avoid inconsistent integrations or any problem that might adversely affect the information that will be fed into the platform. The price update is performade via API, for information, access [Pricing API](https://developers.vtex.com/docs/api-reference/pricing-api#overview).
 
-Check out the API documentation in our Developer Docs:
-https://developers.vtex.com/reference/pricing-api-overview#listorders
diff --git a/docs/tutorials/en/sku-registration-fields.md b/docs/tutorials/en/sku-registration-fields.md
index b0f4d4081..c0d26ebb0 100644
--- a/docs/tutorials/en/sku-registration-fields.md
+++ b/docs/tutorials/en/sku-registration-fields.md
@@ -3,8 +3,8 @@ title: 'Filling in SKU registration fields'
 id: 21DDItuEQc6mseiW8EakcY
 status: PUBLISHED
 createdAt: 2017-09-22T00:20:45.920Z
-updatedAt: 2022-12-19T18:03:03.864Z
-publishedAt: 2022-12-19T18:03:03.864Z
+updatedAt: 2023-07-14T20:59:40.541Z
+publishedAt: 2023-07-14T20:59:40.541Z
 firstPublishedAt: 2017-09-22T00:40:16.232Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ For more information on each field, read their complete description below.
 
 __Product Name:__ This field is already filled in with the SKU product name.
 
-__Name:__ The SKU name, that is, the variation of the previously added product. Product - Fridge, SKU - 110V.
+__Name:__ The SKU name, that is, the variation of the previously added product. Example: Product - Fridge, SKU - 110V. The SKU name is limited to 200 characters.
 
 __Loyalty Value:__ Credit that the customer receives upon completing a purchase of 1 (one) specific SKU unit. If you enter "1" in this field, this means that the customer will get U$ 1 credit on the website.
 
diff --git a/docs/tutorials/en/skus.md b/docs/tutorials/en/skus.md
new file mode 100644
index 000000000..5e6d648e5
--- /dev/null
+++ b/docs/tutorials/en/skus.md
@@ -0,0 +1,128 @@
+---
+title: 'SKUs'
+id: 4zkfF1asM3ayvIigsySevw
+status: DRAFT
+createdAt: 2024-02-02T18:06:58.601Z
+updatedAt: 2024-05-27T20:55:21.862Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: skus
+locale: en
+legacySlug: skus
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+# SKUs
+
+The SKU dataset is composed of the `products_sku` table. This table centralizes detailed product information, including identifiers, descriptions, and brand data, making it easier to manage and analyze product catalogs.
+
+This section includes the following information:
+
+- [Characteristics of SKU data](#data-characteristics)
+- [Table: products_sku](#table-products_sku)
+- [Analyses with products_sku](#analyses-with-products_sku)
+- [Correlations with other data](#correlations-with-other-data)
+
+## Data characteristics
+
+|**Characteristic**|**Description**|
+| - | - |
+|**Data source**|Obtained from the **product catalog**.|
+|**Availability**|Catalog data can be accessed through the VTEX Admin report and also via the [Catalog APIs](https://developers.vtex.com/docs/api-reference/catalog-api/).|
+|**History**|The data is retained for two years, from 2024 for clients who already use the VTEX platform.|
+|**Minimum update interval**|One hour.|
+
+## Table: products_sku
+
+In addition to the catalog data, this table also centralizes product identification information, such as description, brand, and specifications. The table fields are described below.
+
+| **Column name** | **Column type** | **Column description** |
+|:---:|:---:|:---:|
+| **id** | integer | Unique product identifier. |
+| **product_id** | integer | Unique product identifier in the system. |
+| **name_complete** | character varying(255) | Full product name. |
+| **complement_name** | character varying(255) | Additional product name. |
+| **product_name** | character varying(255) | Product name. |
+| **product_description** | character varying(1000) | Detailed product description. |
+| **sku_name** | character varying(255) | Product SKU name. |
+| **product_ref_id** | character varying(255) | External or internal product reference. |
+| **tax_code** | character varying(255) | Tax code associated with the product. |
+| **is_active** | boolean | Specifies whether the product is active. |
+| **is_transported** | boolean | Specifies whether the product can be transported. |
+| **is_inventoried** | boolean | Specifies whether the product is subject to inventory. |
+| **is_gift_card_recharge** | boolean | Specifies whether the product is a gift card reload. |
+| **image_url** | character varying(1024) | Product image URL. |
+| **detail_url** | character varying(1024) | Product details URL. |
+| **csc_identification** | character varying(255) | CSC identification of the product. |
+| **brand_id** | character varying(255) | Product brand identifier. |
+| **brand_name** | character varying(255) | Product brand name. |
+| **is_brand_active** | boolean | Specifies whether the product brand is active. |
+| **dimension** | super | Product dimensions. |
+| **real_dimension** | super | Actual product dimensions. |
+| **manufacturer_code** | character varying(255) | Product manufacturer code. |
+| **is_kit** | boolean | Specifies whether the product is a kit. |
+| **kit_items** | super | Items included in the product kit. |
+| **services** | super | Services associated with the product. |
+| **categories** | super | Categories the product belongs to. |
+| **categories_full_path** | super | Full path of product categories. |
+| **attachments** | super | Attachments related to the product. |
+| **collections** | super | Collections the product belongs to. |
+| **sku_sellers** | super | Sellers of the product SKU. |
+| **sales_channels** | super | Product sales channels. |
+| **images** | super | Product images. |
+| **videos** | super | Product videos. |
+| **sku_specifications** | super | Product SKU specifications. |
+| **product_specifications** | super | Product specifications. |
+| **product_clusters_ids** | character varying(255) | Product cluster IDs. |
+| **positions_in_clusters** | super | Positions in product clusters. |
+| **product_cluster_names** | super | Names of product clusters. |
+| **product_cluster_highlights** | super | Highlights of product clusters. |
+| **product_category_ids** | character varying(255) | Product category IDs. |
+| **is_direct_category_active** | boolean | Specifies whether the product's direct category is active. |
+| **product_global_category_id** | integer | Global product category ID. |
+| **product_categories** | super | Product categories. |
+| **commercial_condition_id** | integer | ID of the product commercial condition. |
+| **reward_value** | double precision | Reward value associated with the product. |
+| **alternate_ids** | super | Alternative product IDs. |
+| **alternate_id_values** | super | Values of the alternative product IDs. |
+| **estimated_date_arrival** | character varying(255) | Estimated arrival date of the product. |
+| **measurement_unit** | character varying(255) | Unit of measure of the product. |
+| **unit_multiplier** | double precision | Product unit multiplier. |
+| **information_source** | character varying(255) | Source of product information. |
+| **modal_type** | character varying(255) | Type of product modal. |
+| **key_words** | character varying(1000) | Keywords associated with the product. |
+| **release_date** | character varying(255) | Product launch date. |
+| **product_is_visible** | boolean | Specifies whether the product is visible. |
+| **show_if_not_available** | boolean | Specifies whether the product should be shown even if it's not available. |
+| **is_product_active** | boolean | Specifies whether the product is active. |
+| **product_final_score** | integer | Final product score. |
+| **account_name** | character varying(255) | Name of the account associated with the product. |
+| **batch_id** | character varying(13) | Control ID of the data ingestion batch. |
+
+## Analyses with products_sku
+
+Some of the analyses that can be run using the catalog table are mentioned below:
+
+- **Product performance analysis:** Calculate sales by SKU to identify the most popular products, targeting marketing and replenishment strategies.  
+- **Product category trends:** Group SKUs by category to analyze sales trends in different segments, adjusting the catalog focus as needed.  
+- **Price and promotion analysis:** Examine the prices and commercial conditions of each SKU to identify opportunities for promotions and price adjustments.  
+- **Inventory monitoring:** Check the availability of each SKU against sales trends to manage inventory efficiently.  
+
+## Correlations with other data
+
+Catalog data correlations with other datasets are key for deeper analysis. Some of these correlations are mentioned below:  
+
+- **Interaction with inventory data:** The correlation between SKUs and inventory is essential for managing sales and stock operations, aligning product availability with demand.  
+- **Order data:** The joint analysis of catalog and order data reveals insights into purchasing preferences, which helps catalog optimization.  
+- **Navigation data:** Interaction with navigation data offers insight into how customers explore the catalog, indicating which products attract the most attention and guiding marketing and promotion strategies.  
+
+### Discover other datasets
+
+- [Inventory](2IvKMZV9SNrE6ipBRQr8h2)
+- [Navigation](4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Orders](2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Payments](7LWkFaA1jPabzc5JAt1rGs)   
+- [Promotions](3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/en/smartcheckout-v5-general-characteristics.md b/docs/tutorials/en/smartcheckout-v5-general-characteristics.md
new file mode 100644
index 000000000..c0a4e4a1e
--- /dev/null
+++ b/docs/tutorials/en/smartcheckout-v5-general-characteristics.md
@@ -0,0 +1,69 @@
+---
+title: 'SmartCheckout™ V5 general characteristics'
+id: tutorials_3811
+status: PUBLISHED
+createdAt: 2017-04-27T21:51:49.943Z
+updatedAt: 2024-02-08T15:03:13.491Z
+publishedAt: 2024-02-08T15:03:13.491Z
+firstPublishedAt: 2017-04-27T23:11:15.321Z
+contentType: tutorial
+productTeam: Shopping
+author: authors_65
+slug: smartcheckout-v5-general-characteristics
+locale: en
+legacySlug: migrating-to-the-new-version-of-smart-checkout
+subcategory: 8AGXmtpbTqUE2KQu0Swwk
+---
+
+SmartCheckout™ V5 allows purchase without VTEX login and password (one-click-buy checkout). Check here its main characteristics and advantages.
+
+### Iframe for the card payments
+
+Payment with credit card, debit card and private label (type of card issued by the retailer and only accepted within your network of stores) is now isolated inside an iframe, which makes it impossible to customize JavaScript, increasing the security of your store. For more information about data protection, visit [SmartCheckout Security](https://help.vtex.com/en/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB#).
+
+Note that, besides the fact of being inside an iframe, it's still possible to apply CSS on the field. But you must pay attention to the CSS selector you're using: It needs to start with elements that are inside `#app-container .App` and without i.e. `#payment-data` or `.payment-group`, that are outside the iframe.
+
+A practical example: to hide the 'Pay with different cards' option, use the element `.ChangeNumberOfPayments {display: none}`.
+
+### New geocoordinate freight calculation option
+
+By using this feature, you may define delivery regions based on a geographical point (latitude and longitude) instead of a postal code.
+
+In case you wish to understand that feature in further details, read the article [Geolocation at Checkout](/en/tutorial/geolocation-at-checkout).
+
+__Attention:__ Once the API Key has been included in the Checkout configuration, the geolocation will be visible in your store checkout, even if you are not migrated to the new version of Smart Checkout._
+
+### Page title
+
+The SmartCheckout™ page title, which appears in the browser's bar or tab, can be customized. Just follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Storefront > Checkout__, or type __Checkout__ in the search bar at the top of the page.
+2. Click on the <i class="fas fa-cog" alt="engrenagem azul"></i> icon of the desired website.
+3. In the blue options menu located at the top of the page, click on __Checkout__.
+4. In the __Website Title__ field, write the desired title and check the result in the PREVIEW box.
+5. Click the `Save` button.
+
+### Customized JavaScript
+
+You can use the files `checkout5-custom.js` and `orderplaced2-custom.js` in order to insert your JavaScript customizations into Checkout and into the finished order screen, respectively. Just follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Storefront > Checkout__, or type __Checkout__ in the search bar at the top of the page.
+2. Click on the <i class="fas fa-cog" alt="engrenagem azul"></i> icon of the desired website.
+3. In the blue options menu located at the top of the page, click on __Code__.
+4. In the __Files__ menu, located on the right side of the page, click on the ones you want to make adjustments to the code.
+5. Click the `Save` button.
+
+<div class="alert alert-warning">
+  Customizing JavaScript files can damage your Checkout. VTEX <b>does not recommend</b> customizations and doesn't take responsibility for any damage caused by this code.
+</div>
+
+__IMPORTANT:__ Do not use these files to insert marketing and integration tags. In case you need them, do so through Google Tag Manager.
+
+### PayPal Plus
+
+The SmartCheckout™ V5 supports the PayPal Plus payment method. This allows payment to be made directly on your website, without the need to redirect your customers (transparent checkout).
+
+### Google Enhanced Ecommerce
+
+The SmartCheckout™ V5 adds to the data layer information to be used along with Google Enhanced Ecommerce. If you wish to understand how to use these tags, check Google's documentation: https://developers.google.com/tag-manager/enhanced-ecommerce.
+
diff --git a/docs/tutorials/en/special-conditions.md b/docs/tutorials/en/special-conditions.md
index ba118104b..028f18ebf 100644
--- a/docs/tutorials/en/special-conditions.md
+++ b/docs/tutorials/en/special-conditions.md
@@ -3,8 +3,8 @@ title: 'Configuring payment special conditions'
 id: tutorials_456
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:58.783Z
-updatedAt: 2023-02-24T20:54:02.331Z
-publishedAt: 2023-02-24T20:54:02.331Z
+updatedAt: 2023-07-27T16:59:12.708Z
+publishedAt: 2023-07-27T16:59:12.708Z
 firstPublishedAt: 2017-04-27T23:03:26.753Z
 contentType: tutorial
 productTeam: Financial
@@ -19,11 +19,7 @@ Special conditions are part of the configuration of payment conditions which all
 
 To identify the special conditions applicable to each payment method, in the VTEX Admin, access  __Payments > Settings > Payment Conditions__, select the desired payment method and check the options as shown in the illustration below.
 
-![special payment conditions](https://images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/5f674ce32524424a33df81b671e04e5c/Special_payment_conditions.png)
-
-<div class = "alert alert-info">
-  <p>The special conditions of the payment rules apply only to the number of installments. The payment method remains the same.</p>
-</div>
+![special payment conditions](//images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/5f674ce32524424a33df81b671e04e5c/Special_payment_conditions.png)
 
 ## Commercial condition
 
@@ -33,7 +29,7 @@ To learn how to add a new commercial condition, and link it to a SKU, read the d
 
 ## How to configure a commercial condition on the payment condition
 
-![condicao-comercial en](https://images.ctfassets.net/alneenqid6w5/2YSz1udqP6YCgSQ6u2c8II/1b9ec111a6f65a1a254908fd141a97f7/commercial-condition.png)
+![condicao-comercial en](//images.ctfassets.net/alneenqid6w5/2YSz1udqP6YCgSQ6u2c8II/1b9ec111a6f65a1a254908fd141a97f7/commercial-condition.png)
 
 1. Inside the payment condition, click on `Add special condition`.
 3. Then, click on `Commercial Condition`.
@@ -93,7 +89,7 @@ Allows a payment condition to be applied to a specific trade policy, or as many
 
 How to configure a trade policy for the payment condition
 
-![politica-comercial en](https://images.ctfassets.net/alneenqid6w5/4FEkjd6rSMuA6mKOQ6O0aC/3d100357b97b18b7f073adc686ad0a1a/sales-policy.png)
+![politica-comercial en](//images.ctfassets.net/alneenqid6w5/4FEkjd6rSMuA6mKOQ6O0aC/3d100357b97b18b7f073adc686ad0a1a/sales-policy.png)
 
 1. Inside Payment Conditions, click on `Add special condition`.
 3. Then, click on `Trade Policy (Sales Channel)`.
@@ -118,7 +114,7 @@ How to configure the issuing bank in the payment condition
 6. If you want to segment by co-brand, select the desired option in __Co-brand__ (this box will only appear if VTEX was made aware of the co-brand card list beforehand).
 7. Save changes.
 
-![banco-emissor en](https://images.ctfassets.net/alneenqid6w5/6q6yz9BnLaAkCCkCOy2EYS/9129d3e6448169fa3f940b627a31160c/issuing-bank.png)
+![banco-emissor en](//images.ctfassets.net/alneenqid6w5/6q6yz9BnLaAkCCkCOy2EYS/9129d3e6448169fa3f940b627a31160c/issuing-bank.png)
 
 ### Examples
 
@@ -150,7 +146,7 @@ Allow you to set up an expiration date for the payment condition, so that its ap
 
 How to configure the payment condition period:
 
-![periodo en](https://images.ctfassets.net/alneenqid6w5/1SHkE4MhWYke8YAuiu0gii/cebe25c6535946b788e28bd24afa3c18/period.png)
+![periodo en](//images.ctfassets.net/alneenqid6w5/1SHkE4MhWYke8YAuiu0gii/cebe25c6535946b788e28bd24afa3c18/period.png)
 
 1. In Payment Conditions, click on `Add special condition`.
 2. Then, click on `Period`.
diff --git a/docs/tutorials/en/split-payment.md b/docs/tutorials/en/split-payment.md
index fe5c9beb2..31eaf9783 100644
--- a/docs/tutorials/en/split-payment.md
+++ b/docs/tutorials/en/split-payment.md
@@ -3,8 +3,8 @@ title: 'Split Payment'
 id: 6k5JidhYRUxileNolY2VLx
 status: PUBLISHED
 createdAt: 2021-04-06T20:03:53.443Z
-updatedAt: 2023-04-24T19:09:31.016Z
-publishedAt: 2023-04-24T19:09:31.016Z
+updatedAt: 2024-06-18T17:50:44.146Z
+publishedAt: 2024-06-18T17:50:44.146Z
 firstPublishedAt: 2021-04-07T18:57:19.713Z
 contentType: tutorial
 productTeam: Financial
@@ -19,13 +19,18 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 This is a marketplace payment solution.
 </div>
 
-To guarantee that our marketplace clients automatically divide the payment between all sellers, set a commission based on a fixed percentage, and stay compliant with the current regulations, VTEX offers the __Split Payment solution__.
+To guarantee that our [marketplace](https://help.vtex.com/en/tutorial/what-is-a-marketplace--680lLJTnmEAmekcC0MIea8) clients automatically divide the payment between all [sellers](https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w), set a commission based on a fixed percentage, and remain operating in accordance with current regulations, VTEX offers the __Split Payment__.
 
-When a shopper adds multiple products of multiple sellers in the same shopping cart and pays for them in a unified checkout experience, VTEX automatically splits that payment so every party can get their share directly into their bank account.
+Below are two examples of split payment application scenarios where a consumer adds products from different sellers to the same cart:
 
-However, this amount may or may not be equally divided among recipients. The distribution is done according to the seller's predefined conditions and the commissions taken by the marketplace. When configured, the Split Payment allows the amount paid for an order to be automatically divided between [sellers](https://help.vtex.com/tutorial/what-is-a-seller) and [marketplaces](https://help.vtex.com/en/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8).
+1. When the marketplace is responsible for processing payment for the purchase, VTEX automatically divides this payment so that each beneficiary receives their share directly into their own bank account, thus carrying out the [Payout Split](https://help.vtex.com/tutorial/split-payment--6k5JidhYRUxileNolY2VLx#payout-split).
+2. When the cart involves sellers who are responsible for processing their own payment method (without depending on the marketplace), VTEX creates different payment transactions for the Marketplace and the sellers, performing the [Transaction Split](https://help.vtex.com/tutorial/split-payment--6k5JidhYRUxileNolY2VLx#transaction-split).
 
-You can configure split payment in two different ways: [Payout Split](https://help.vtex.com/en/tutorial/split-payment#payout-split) and [Transaction Split](https://help.vtex.com/en/tutorial/split-payment#transaction-split). Both types of Split Payment have some differences that might be taken into consideration before choosing between them. 
+<div class="alert alert-warning">
+The distribution of purchase amounts is always carried out in accordance with pre-defined commission percentage agreements between the marketplace and sellers.
+</div>
+
+Check below for more details about each of the split payment models:
 
 | Characteristics    | Payout Split     | Transaction Split     |
 | ---------- | ---------- | ---------- |
@@ -34,7 +39,7 @@ You can configure split payment in two different ways: [Payout Split](https://he
 | __Number of purchases in the customer’s credit card statement__       | Only one       | One purchase to each seller. <li>*This fact may lead to misunderstandings and increase disputes and chargebacks*.</li>       |
 | __Fees negotiation__  | Marketplace will be responsible for negotiating all fees. <li>In scale, this can be positive to increase bargain power.</li>       | Marketplace will be responsible for negotiating all fees. In scale, this can be positive to increase bargain power.       |
 | __Anti fraud assessment__      | As only one transaction is generated, the entire order is assessed by one anti-fraud.       | As multiple transactions are generated, each of them run into a different analysis. If one transaction is denied, all others are automatically denied as well       |
-| __Payment providers integrated__       | Information available in the [List of Payment Providers by Country](https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp) | All payment providers integrated to VTEX.       |
+| __Payment providers integrated__       | See which payment providers use Payout Split in the [List of Payment Providers by Country](https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp) | All payment providers integrated to VTEX.       |
 | __Cost__       |Costs according to the negotiated fee. <ul><li>Usually costs more than non-split transactions.</li><li>Carts that only have marketplace products, will still be processed taking into consideration the negotiated fee, potentially increasing cost.</li></ul>       | No additional costs, VTEX clients will only be responsible for their usual fees with payment providers       |
 | __Checkout Experience__       | No limitations regarding payment methods and payment conditions. Those will be defined by the marketplace. <ul><li>The payment provider must also support Split in specific payment methods (Pix, for example). Nowadays our partners support split with one or two credit cards, debit cards and boleto (Brazil).</li></ul>      | Only displays payment methods accepted by all sellers fulfilling the order. In other words, payments by credit card, cash or card promissory (promissories that can be splited), will only be available if all sellers involved in the order accept them. Incompatible with:<ul><li>Boleto (Brazil).</li><li>Pix (Brazil).</li></ul><ul><li>Cards with 3DS2 or any authentication.</li></ul> |
 | __Ideal for__       | <ul><li>Marketplaces that want to charge automatic commissions, avoiding the risk of delinquency.</li><li>Marketplaces whose sellers do not have a payment provider.</li></ul><ul><li> Marketplaces that want to have more control over the payment flow of sellers.</li><li> Marketplaces that want to process transactions with Pix (Brazil), boleto (Brazil) and credit cards with 3DS2 or any other authentication.</li></ul>       | <ul><li> Marketplaces that don't want to be merchants of record (common for B2B businesses from Europe and the United States).</li><li> Cases in which the seller has more decision power than the marketplace and only accepts that the payment is processed by their own payment provider.</li></ul><ul><li> Marketplaces that have urgency to implement split and do not have partners supporting split in their countries.</li><li>Marketplaces that don't want to have all the chargeback risks.</li></ul>       |
@@ -50,31 +55,26 @@ For example, a shopper adds two products to the same shopping cart. One of them
 
 __The payment is distributed as follows:__
 
-![Payout Split](https://images.ctfassets.net/alneenqid6w5/2Pqz4t4XkfA1WGZOi1VCX0/1694e5c9947473a360e50010881fee70/PAYOUT.png)
+![Payout Split](//images.ctfassets.net/alneenqid6w5/2Pqz4t4XkfA1WGZOi1VCX0/1694e5c9947473a360e50010881fee70/PAYOUT.png)
 
 As you can see, our Gateway calculates and distributes payouts for each recipient when the order is invoiced and sends that info to the payment provider. The distribution is done according to the amount destined to each merchant in the order and the commissions taken by the marketplace.
 
-![Receivables](https://images.ctfassets.net/alneenqid6w5/1rJ1dG3TMX9UqjPr5H4GMR/1b024e71291ab003f9b6379d0ffcecca/RECEBIVEIS.png)
-
-With this model, our marketplace clients also have access to a Commission Report, and using this feature, they can check the listing of orders invoiced by each of their sellers and the respective commission rates retained.
-
-The Commission Report brings transparency to the amounts due to each seller and the commissions those orders brought to the marketplace.
-
-<div class="alert alert-warning">
-Currently, our commission report is only available for specific clients that are part of our beta test.</div>
+![Receivables](//images.ctfassets.net/alneenqid6w5/1rJ1dG3TMX9UqjPr5H4GMR/1b024e71291ab003f9b6379d0ffcecca/RECEBIVEIS.png)
 
 Our __Payout Split__ solution has some limitations that are important to consider:
 
 - __Combined Payment Methods__: it does not support when one of them does not support Split. Example: gift card + credit card (gift card does not support Split).  Currently, it is only possible to have the split payment when the combined methods are two credit cards due to a checkout limitation.
-- __Change Order__: it does not work with changes in values or items after the order is placed. That also means that it isn't possible to partially cancel an order with split.
+- __Change Order__: it does not work with changes in values or items after the order is placed. Orders containing splits can be partially refunded, but not cancelled.
 - __VTEX Subscriptions__: it does not support marketplace orders.
 - __Sellers ID__: CNPJ is the primary  key to make the split, so the recipients (marketplaces or sellers) need to be legal entities.
 - __Same CNPJ__: since the CNPJ is the primary key to make the Split, it is not possible for two or more recipients/sales participants with the same CNPJ to be seen as different "entities".
 - __Parties Involved__: it does not allow to Split the payment with recipients who are not selling products in the cart. For example: to split the freight directly to the carrier.
 - __Nominal Fees__: it does not allow nominal fees. Currently, it is only possible to apply percentage commissions on products and/or freight.
 - __Assigning transactions to the provider__: today it is only possible to assign a preferred affiliation at the gateway to process Split using commercial conditions for the SKUs that are sold by the Seller. However, there are limitations:
-        - If the seller and the marketplace have the same SKU, the cart will always go to the Split payment method.
-        - The list of SKUs has to be constantly updated.
+    - If the seller and the marketplace have the same SKU, the cart will always go to the Split payment method.
+    - The list of SKUs has to be constantly updated.
+
+- __Transaction interest__: it is not possible to select who will receive the interest information (marketplace or seller). All transactions in which the customer made interest payments are automatically sent to the marketplace.
 
 ## Transaction Split
 
@@ -86,11 +86,11 @@ Meaning that the marketplace has less control over the payment flow. Unlike the
 
 For example, a shopper adds two products to the same shopping cart. One of them will be fulfilled by the marketplace itself and the other one belongs to a seller called __Seller A__.
 
-![Transaction Split](https://images.ctfassets.net/alneenqid6w5/3uiBeqiyYlaneMksnW4G0v/8a47d871bdc64ccec3d812b4449b053e/TRANSACTION.png)
+![Transaction Split](//images.ctfassets.net/alneenqid6w5/3uiBeqiyYlaneMksnW4G0v/8a47d871bdc64ccec3d812b4449b053e/TRANSACTION.png)
 
 In the __Transaction Split__, the marketplace has no need to make any configuration. The seller is the one that needs to configure their own payment method in the affiliation with a given marketplace. Check our documentation [Send the Seller White Label payment methods to the Marketplace](https://help.vtex.com/en/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW) for more details. 
 
-![Report](https://images.ctfassets.net/alneenqid6w5/3YX8MmCPvAWyJpZ7tFAHt4/7276a3b6c1ff1cf1d4d6fe5ccd7bdba9/REPORT.png)
+![Report](//images.ctfassets.net/alneenqid6w5/3YX8MmCPvAWyJpZ7tFAHt4/7276a3b6c1ff1cf1d4d6fe5ccd7bdba9/REPORT.png)
 
 The transaction split has a few __limitations__ that must be taken into account:
 
@@ -109,7 +109,5 @@ When Transaction Split and Payout Split are combined, the Transaction Split will
 
 #### Learn more
 
-- [Configure Payout Split - PagarMeV2](https://help.vtex.com/en/tutorial/setting-up-pagarmev2-gateway--5TugxXNMOs0Ocyg4uqussM?&utm_source=autocomplete)
-- [Configure Payout Split - VTEX Payment](https://help.vtex.com/en/tracks/vtex-payment--7iCCIoIZFmd9OabU6QlmXu/1lZWKCGdy7xpYjukTLfFJL)
 - [Send the Seller White Label payment methods to the Marketplace](https://help.vtex.com/en/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW) (for more information about how to setup Transaction Split).
 
diff --git a/docs/tutorials/en/store-access-permission.md b/docs/tutorials/en/store-access-permission.md
index 23fef3b1c..bae7bfe1a 100644
--- a/docs/tutorials/en/store-access-permission.md
+++ b/docs/tutorials/en/store-access-permission.md
@@ -25,4 +25,4 @@ To configure this feature in your store, access the Admin and follow the instruc
 4. Select the __VTEX Store__ option.
 5. Check the box next to __"Enables B2B behavior"__ and save the changes.
 
-![Enable B2B scenario](https://images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
+![Enable B2B scenario](//images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
diff --git a/docs/tutorials/en/store-overview-beta.md b/docs/tutorials/en/store-overview-beta.md
new file mode 100644
index 000000000..c902edbf5
--- /dev/null
+++ b/docs/tutorials/en/store-overview-beta.md
@@ -0,0 +1,160 @@
+---
+title: 'Store Overview (Beta)'
+id: 7i8wNsQQgbbFhYMYbQ5X46
+status: PUBLISHED
+createdAt: 2023-06-14T17:43:51.256Z
+updatedAt: 2023-11-09T19:56:54.060Z
+publishedAt: 2023-11-09T19:56:54.060Z
+firstPublishedAt: 2023-06-15T14:16:58.510Z
+contentType: tutorial
+productTeam: Management
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: store-overview-beta
+locale: en
+legacySlug: store-overview-beta
+subcategory: QPnz120TdtLcXSh65c4Gs
+---
+
+<div class="alert alert-info">
+The updated version of the Store Overview (beta) page is available for use free of charge on the VTEX Admin during the beta phase or until stipulated by VTEX. It is important to note that charges may apply in the future. For the time being, the current version of the Store Overview page on the VTEX Admin will continue to be available.
+</div>
+
+The Store Overview (Beta) page in your VTEX Admin provides real-time tracking of your operation on the current day, giving visibility into indicators that allow you and your team to get feedback about actions applied to the store and to quickly implement improvements.
+
+This tool is available on the homepage of the VTEX Admin. To view it, click **Dashboards > Overview** in the navigation menu, or type _Overview_ in the search bar at the top of the page.
+
+![EN visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/88b40023b0c9d38dae93d2ccb563e378/EN_visa__o_geral_beta.png)
+
+In this article, we describe the main page sections and actions. You will learn more about:
+
+- [Page data](#page-data)
+- [Analyzing results and operation health](#analyzing-results-and-operation-health)
+-	[Period comparison](#comparing-periods)
+- [Views](#views)
+- [Monitoring](#monitoring)
+- [Metrics](#metrics)
+
+## Page data
+
+The metrics on this page include order and browsing data collected by different systems.
+
+<div class ="alert alert-warning">
+The revenue metric may differ from the average ticket metric recorded in the OMS and Sales Performance, for example. This is because Sales Performance considers an order's item values, while OMS also considers discounts, freight, fees, and promotions applied to the order, which may increase or decrease its final total.
+</div>
+
+-	**Orders and revenue:** The order and revenue data comes from the VTEX Order Management System (OMS) and includes orders placed on all your sales channels.
+-	**Sessions:** The browsing data comes from the platform’s internal system, which collects user sessions from storefronts of VTEX stores. Sessions represent the total number of views on pages accessed by a single user while browsing through your ecommerce store, excluding marketplaces, apps, VTEX Sales App, or other sales channels.
+
+## Data restrictions
+
+We do not collect browsing data from non-VTEX storefronts or from sellers who only offer products on external marketplaces.  This means that the charts displayed in the [Monitoring](#monitoring) section may not be available, depending on whether we collected browsing data from your store.
+
+Although we aim to show a maximum of 3% divergence from the VTEX OMS data, sometimes you may find discrepancies between the data reported on the Store Overview dashboard and the OMS data.
+
+### Data update
+
+Different page data have different update frequencies. The charts in the [Monitoring](#monitoring) section may be updated as often as every three minutes, depending on the [View](#view), while other sections are updated every 15 minutes. The <i class='fas fa-circle-notch blue-color'></i>  "1 min" label shows the last time that the page data was updated.
+
+## Analyzing results and operation health 
+
+You can use different metrics and monitoring charts for analyzing results, depending on what you want to explore. The table below can help guide your analysis. Click each metric listed in the table to learn more about how it is calculated and how it works.
+
+| Objective         | Related metrics and charts                                                                                                                                                                                                                                    |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Action engagement | - [New sessions](#monitoring) <br>- [Best-selling products](#metrics)                                                                                                                                                                                                                     |
+| Financial results | - Revenue captured <br>- [Average ticket](#monitoring) <br>- [Highest grossing products](#metrics)                                                                                                                                                                                         |
+| Conversion        | - [Conversion rate](#metrics) <br>- [Sales funnel](#sales-funnel) <br>- [Orders captured](#monitoring), compared to the number of canceled orders. Depending on the outcome, this can guide your team to identify operational problems in fulfillment or customer service that resulted in canceled orders. |
+
+<div class="alert alert-info"> Keep in mind that while the Monitoring charts are updated within three minutes, Metrics charts take fifteen minutes to be updated, which can influence the analysis of results. Learn more in <a href="#data-update">Data update</a>.
+</div>
+
+### Analyzing campaign results
+
+If you want to analyze the results generated by campaigns, promotions, or new product launches that occurred in the past, follow the instructions below:
+
+1. Select the **Store** where the action occurred.
+2. Select the campaign **Date** to [compare that period](#comparing-periods) with today's date.
+3. Select the `Accumulated` [view](#views).
+4. Track the hourly performance of metrics.
+
+![EN visão geral Beta acumulado](//images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/787362a926aa9a3b503353d1f691fd49/EN_visa__o_geral_Beta_acumulado.png)
+
+### Tracking the impact of changes in the store
+
+To maintain a healthy and stable operation, it's important to identify if any deploys, campaigns, or setting changes have a negative impact on the number of orders, sessions, or customer conversion immediately after they are applied.
+
+If you want to see the impact of store changes, either to identify negative effects or changes in the health of your business, follow the instructions below.
+
+1. Select the **Store** where the action occurred.
+2. Select the `Last 2 hours` [view](#views).
+3. Check the pulse of the metrics or inflection points in the chart in the last two hours.
+4. [Compare the times](#comparing-periods) of the inflection points with the applied changes to identify their cause and impact.
+
+![EN visão geral Beta ultimas duas horas](//images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/b0d5752df79f525b07d023b5e984fd18/EN_visa__o_geral_Beta_ultimas_duas_horas.png)
+
+## Comparing periods
+
+You can filter data based on the selected period and compare store metrics with past dates. To compare data from different periods, at the top of the page, select the date next to `Compare today with:` and, then, select one of the following actions:
+
+| Period      | Start                                                                          | End                                |
+|-------------|--------------------------------------------------------------------------------|------------------------------------|
+| Yesterday   | 00:00 of the previous day                                                      | 23:59 of the previous day          |
+| 7 days ago  | 00:00 of the eighth day before the current day                                 | 23:59 of the day before today      |
+| 28 days ago | 00:00 of the 29th day before the current day                                   | 23:59 of the day before today      |
+| Custom      | Select in the calendar the desired Comparison date up to 13 months in the past | 23:59 of the day before today|
+
+## Views
+
+When you click the `View:` button in the Monitoring section, you can toggle between the following options:
+
+-	**Accumulated:** Total value accumulated per day for each monitoring metric from 00:00 to the last update. The data in this view are updated every three minutes.
+-	**Last 2 hours:** Value received in the last two hours for each monitoring metric. This view doesn't show the comparison with other periods or the increase or decrease percentage of the metric. The data in this view are updated every minute.
+
+You can also filter by store if you select one in the dropdown menu.
+
+## Monitoring
+
+Each chart has the following elements:
+
+- The X axis shows the time and the Y axis shows the value of the monitoring metric.
+- Absolute value of each metric, which can be `Accumulated` or `Latest hours`. Learn more in [Views](#views).
+- The thicker blue line indicates the evolution of values today.
+- The dotted gray line indicates the rate for the comparison period.
+- When you hover over the chart, it will show the absolute value for each period being compared.
+
+The table below describes the charts included in the _Monitoring_ section of the page.
+
+| Metric           | Description                                                                                                                                                                  |
+|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Revenue captured | Total amount determined by the final amount of captured orders, which shows the amount that the store received as revenue. Comparison between today and the selected period. |
+| Orders captured  | Number of orders received by your store today compared with the selected period.                                                                                             |
+| Average ticket   | Average revenue per order captured today compared with the selected period.                                                                                                  |
+| New sessions     | Number of new visits or interactions in your store, depending on the selected [View](#views). This metric is only available for stores that [collect browsing data](#data-restrictions).                     |
+
+## Metrics
+
+![EN visão geral Beta metricas](//images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/479e453368ec833c2c88109f606ae488/EN_visa__o_geral_Beta_metricas.png)
+
+The table below describes the metrics available on the home dashboard. All metrics are related to purchase flows in VTEX stores during the selected period.
+
+| Metric                    | Description                                                                                                                                                                                                                                                                                                                                           |
+|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Average ticket            | Average amount paid for captured orders in the selected period. This metric is tracked as a down icon <i class='fa fa-caret-down'></i> or an up icon <i class='fa fa-caret-up'></i> to show the increase or decrease percentage of the average ticket.                                                                                                |
+| Conversion rate           | Percentage calculated by dividing the total number of orders by the total number of sessions in your store. When you click the arrow <i class='fa fa-chevron-down'></i>, the Sales funnel is expanded.                                                                                                                                                |
+| Highest grossing products | Products that generated the most revenue in the selected period. Shows the amount of revenue received and a percentage indicating the revenue increase or decrease, as well as a comparison between the selected periods. When you click the arrow icon <i class='fa fa-chevron-down'></i>, you switch between this metric and Best-selling products. |
+| Best-selling products     | Products that sold the most units in the selected period. Shows the number of items sold and a percentage indicating the increase or decrease of items sold, as well as a comparison between the selected periods. When you click the arrow icon <i class='fa fa-chevron-down'></i>, you switch between this metric and Highest grossing products.    
+### Sales funnel
+
+In the _Conversion rate_ metric, when you click the arrow icon <i class='fa fa-chevron-down'></i>, the **Sales funnel** will be expanded. This chart tracks and monitors session volume in the intermediate stages of the purchase flow and allows you to identify opportunities to optimize the conversion rate of your store. The table below describes the intermediate stages of the purchase flow.
+
+| Stage    | Description                                                    |
+|----------|----------------------------------------------------------------|
+| Sessions | Total number of visits to your store                           |
+| Product  | The user accessed a product page during the session            |
+| Cart     | The user added a product to the cart during the session        |
+| Shipping | The user completed the shipping information during the session |
+| Payment  | Payment information was completed during the session           |
+| Orders   | Orders placed during the session                               |
+
+Each blue bar in the chart represents the volume of sessions that have reached a certain stage of the purchase flow. This volume is represented as an absolute value and as a percentage of the number of sessions together with the increase or decrease percentage points in the sales funnel.
+
diff --git a/docs/tutorials/en/store-overview.md b/docs/tutorials/en/store-overview.md
index 98fcd956c..65561d1ff 100644
--- a/docs/tutorials/en/store-overview.md
+++ b/docs/tutorials/en/store-overview.md
@@ -17,7 +17,7 @@ subcategory: 1TIJqw8kV2Yok4iQe4SAkq
 
 VTEX Admin’s Overview page is where store owners can get a quick overview of key metrics that impact the store’s revenue. Through this dashboard, you can track the evolution of your sales through order trend analysis, conversion rate and sales funnel charts. You can access this tool in the VTEX Admin, by clicking on **Dashboards > Overview** in the navigation menu, or type *Overview* in the search bar at the top of the page.
 
-![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
  The Overview page provides a summary of your business with VTEX. For deeper analysis of your store's metrics, visit [Sales Performance](https://help.vtex.com/en/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp).
 
@@ -55,7 +55,7 @@ To compare data from different periods, on the top of the page, select the date
 
 ## Metrics
 
-![Store overview Metricas EN](https://images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/e607a9f5f31572420c0e149195f17f3a/Metricas_EN.png)
+![Store overview Metricas EN](//images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/e607a9f5f31572420c0e149195f17f3a/Metricas_EN.png)
 The table below describes the key metrics available in the homepage dashboard. All metrics refer to purchase flows made in VTEX stores in a given time frame.
 
 | Metric                               | Description                                                                                                                                                                                                                                                                               |
@@ -69,7 +69,7 @@ The table below describes the key metrics available in the homepage dashboard. A
 | Orders in the past hour              | Orders placed in your store in the past hour. By clicking on this metric, you are redirected to the All Orders page.                                                                                                                                                                      |
 
 ## Highest grossing products
-![Store overview Growing products PT](https://images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/12b76c6938510fc269a4fe561021690a/Store_overview_Growing_products_EN.jpg)  
+![Store overview Growing products PT](//images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/12b76c6938510fc269a4fe561021690a/Store_overview_Growing_products_EN.jpg)  
 
 This component lists your highest grossing products and products with the highest number of units sold in the selected period. 
 
@@ -80,16 +80,16 @@ Know more about the metrics:
 - __Highest sold units products:__ the products with most units sold in the selected period. This list shows the quantity of sold units, and a percentage indicating the increase or decrease in sold units, comparing the selected periods.
 
 ## Performed orders
-![Store overview Pedidos realizados EN](https://images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/b10ae305893dc43f313b412731c7d356/Pedidos_realizados_EN.png)
+![Store overview Pedidos realizados EN](//images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/b10ae305893dc43f313b412731c7d356/Pedidos_realizados_EN.png)
 
 This chart displays the number of orders that were received by your store in the selected period. The thick blue line represents the orders placed in the more recent period. The thin gray line represents the orders placed in the period selected for comparison. By hovering the mouse over the chart, the number of orders captured at a specific time is displayed.
 
 ## Canceled orders
-![Store overview Pedidos cancelados EN](https://images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/fff4e13c813fd3daf99aa0cd839a2259/Pedidos_cancelados_EN.png)
+![Store overview Pedidos cancelados EN](//images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/fff4e13c813fd3daf99aa0cd839a2259/Pedidos_cancelados_EN.png)
 This chart displays the number of orders that have been canceled in your store in the selected period. The thick blue line represents the orders canceled in the more recent period. The thin gray line represents the orders canceled in the period selected for comparison. By hovering the mouse over the chart, the number of canceled orders at a specific time is displayed.  
 
 ## Order trend analysis
-![Store overview Order trend EN](https://images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/694055732b0c694049732420163291a8/Store_overview_Order_trend_EN.jpg)  
+![Store overview Order trend EN](//images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/694055732b0c694049732420163291a8/Store_overview_Order_trend_EN.jpg)  
 
 This chart shows your store’s order trend, indicating the number of orders placed by shoppers in the selected period.
 
@@ -98,13 +98,13 @@ The line indicates the order curve for the selected period. By hovering the mous
 The number shown on top of the chart refers to the orders placed in the last hour and it is updated every five minutes.  The label on top of the chart indicates whether orders are being placed at a `normal`, `low` or `high` rate when compared to your store’s usual performance for that period. 
 
 ## Conversion rate
-![Store overview Conversion rate EN](https://images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/f6435fce96325abc0e8c4f11021234bf/Store_overview_Conversion_rate_EN.jpg)  
+![Store overview Conversion rate EN](//images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/f6435fce96325abc0e8c4f11021234bf/Store_overview_Conversion_rate_EN.jpg)  
 
 This chart shows your store’s conversion rate in the selected periods you wish to compare. The conversion rate is calculated by dividing the total number of orders by the total number of sessions in your store. The thick blue line indicates the conversion rate for the most recent period. The thin blue line indicates the conversion rate for the the period selected for comparison. The chart also indicates the percentage (%) and percentual points (p.p) of increase or decrease for this metric. By hovering the mouse over the chart, you can see the value of that metric at specific times. 
 
 ## Sales funnel
 
-![Store overview sales funnel EN](https://images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/a477554ecdb6d2e8eccc427f06503b2b/Store_overview_sales_funnel_EN.jpg)  
+![Store overview sales funnel EN](//images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/a477554ecdb6d2e8eccc427f06503b2b/Store_overview_sales_funnel_EN.jpg)  
 
 This chart allows you to track the volume of sessions in the intermediate stages of the purchase flow and view opportunities for optimizing the store's conversion rate. The table below describes the intermediate stages of the purchase flow.
 
@@ -120,7 +120,7 @@ This chart allows you to track the volume of sessions in the intermediate stages
 Each blue bar in the chart represents the volume of sessions that have reached a certain stage of the purchase flow. This volume is represented as an absolute value (above), and as a percentage of the number of sessions (below), together with the percentual points (p.p) of increase or decrease in the sales funnel. By hovering the mouse over the percentage, you can view more details about that intermediate stage.
 
 ## Highest grossing categories
-![Categorias EN](https://images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/0bd3ce0bde40ba19ea5f6c246236878f/Categorias_EN.png)
+![Categorias EN](//images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/0bd3ce0bde40ba19ea5f6c246236878f/Categorias_EN.png)
 
 This chart indicates the ten categories in your store which generated the most revenue in the selected period. The blue bar indicates the revenue generated on the most recent date. The gray bar indicates the revenue generated on the period selected for comparison. By hovering the mouse over the chart, the conversion rate for each compared period is displayed. 
 By clicking on the chart title it is possible to change the view to __Highest sold categories by orders__.
diff --git a/docs/tutorials/en/store-profile.md b/docs/tutorials/en/store-profile.md
new file mode 100644
index 000000000..18657cce0
--- /dev/null
+++ b/docs/tutorials/en/store-profile.md
@@ -0,0 +1,85 @@
+---
+title: 'Store Profile'
+id: 72qjh4BIc9ppKsbEpdBKoo
+status: PUBLISHED
+createdAt: 2023-07-19T21:17:55.736Z
+updatedAt: 2023-07-19T21:29:37.370Z
+publishedAt: 2023-07-19T21:29:37.370Z
+firstPublishedAt: 2023-07-19T21:29:37.370Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: store-profile
+locale: en
+legacySlug: store-profile
+subcategory: 6riYYNZCpO8wyksi8Ksgyq
+---
+
+VTEX provides in its Admin the **Find Sellers** and **[Marketplaces and Integrations](https://help.vtex.com/en/tutorial/marketplaces-and-integrations--5AcBO1t29nhq7rBHas9b6V)** pages. Both aim to enable and promote communication between sellers and marketplaces operating in the VTEX ecosystem, creating new business opportunities and mutual growth for all involved.  
+
+To contact potential partners in these lists, you need to activate your store profile as a marketplace, seller, or both on the Store Profile page in **Marketplace > Store Profile** or by typing **Store Profile** in the search bar.  
+
+## Store Information  
+
+The information completed in the Store Information section will not be applied to your storefront but to the *Find Sellers* and *Marketplaces and Integrations* pages.  
+
+- **Logo**: Your store logo image, with a maximum size of 500 kB.
+- **Store name:** Your store trade name.  
+- **Industry:** Your store industry. Select the industry in which your store
+operates from the dropdown list.  
+- **Country**: The country where the headquarters or the store main operation is located.  
+- **Ecommerce link:** URL of the brand official website.  
+- **Select the states where your store delivers to:** Checkboxes for each state are displayed.  
+
+## Activating the Seller Profile  
+
+If you want to operate only as a seller and sell your products on other marketplaces, you will need to activate your seller profile by following the steps and recommendations below.  
+
+1. In the *Marketplace* section of your VTEX Admin, click **Store Profile** or type **Store Profile** in the search bar.  
+1. Complete the form with your **Store Information**.  
+1. Complete the **Seller Profile** section.  
+1. Click the **Terms and Conditions of Use of Marketplace Network** link and scroll down to read them.  
+1. Click the `Save Changes` button in the top right corner of the page.  
+
+### Completing the Seller Profile  
+
+To complete the Seller Profile, click the <i class="fas fa-toggle-on"></i> to start completing the profile. Then, click `Save changes`, and your store will be visible or hidden on the **Find Sellers** page for the marketplaces.  
+Below are the fields and guidelines for completing the section.  
+
+- **Public profile description**: Text with up to 1,200 characters describing your store and operation that will be visible on your profile. We suggest you add your operation details, such as delivery SLA, logistics coverage, and the main categories of your product mix, among others.  
+- **Contact name:** Name of the person responsible for contacting potential partners. We suggest that this contact is the person in your team already responsible for engaging with partners.  
+- **Email**: Email address of the person responsible for contacting potential partners. Ensure it is a valid email address, as this is where you will receive the messages sent.  
+- **Phone number**: Phone number of the person responsible for contacting potential partners.  
+- **Use standard message:** Message created by the store to be used as default in the messages marketplaces will see in the `Contact seller` field when clicking your profile. Even if you activate this option, you can edit the message before sending it to the potential partner.  
+
+## Activating the Marketplace Profile
+
+If you want to operate only as a marketplace and sell other sellers' products in your environment, you will need to activate your marketplace profile by following the steps below.  
+
+1. In the *Marketplace* section of your VTEX Admin, click **Store Profile** or type **Store Profile** in the search bar.  
+2. Complete the form with your **Store Information**.  
+3. Complete the **Marketplace Profile** section.  
+4. Click the **Terms and Conditions of Use of the Marketplace Network** link and scroll down to read them.  
+5. Click the `Save Changes` button.  
+
+### Completing the Marketplace Profile  
+
+To complete the Marketplace Profile, click the <i class="fas fa-toggle-on"></i> to start completing the profile. Then, click `Save Changes`, and your store will be visible or hidden on the **Marketplaces and Integrations** page.  
+
+Below are the fields and guidelines for completing the section.  
+
+- **Public profile description**: Text with up to 1,200 characters describing your store and operation that will be visible on your profile. We suggest you add your operation details, such as the highest revenue categories, billing policies, commissions over products, and whether you allow the seller to process the payment.  
+- **Contact name:** Name of the person responsible for contacting potential partners. We suggest that this contact is the person in your team already responsible for engaging with partners.  
+- **Email**: Email address of the person responsible for contacting potential partners. Ensure it is a valid email address, as this is where the messages sent to your store will arrive.  
+- **Phone number**: Phone number of the person responsible for contacting potential partners.  
+- **Use standard message:** The customized message sellers will see as default in the Send a message field when clicking your profile. Even if you enable this option, you can edit the message before sending it to the potential partner.  
+
+## Recommendations  
+
+When interacting with the **Find Sellers** and **Marketplaces and Integrations** pages, please be aware of the following recommendations to leverage the feature to its fullest:  
+
+- Add the brand's official website when completing your store profile.  
+- We suggest putting the contact of employees already qualified and responsible for attracting partners.  
+- Ensure that the entered email and phone number are valid and up-to-date.  
+- Keep your profile updated with the proper links and information about the company.  
+- Write an appealing description of your store. Your profile is displayed in the **[Find Sellers](https://help.vtex.com/tutorial/encontrar-sellers--6kkZaxIgfDyvN5trgIuwBl)** and **[Marketplaces and Integrations](https://help.vtex.com/en/tutorial/marketplaces-and-integrations--5AcBO1t29nhq7rBHas9b6V)** lists, so it is crucial to give context and mention your strengths.  
diff --git a/docs/tutorials/en/store-settings-overview.md b/docs/tutorials/en/store-settings-overview.md
index 62503e3c0..6b4c07773 100644
--- a/docs/tutorials/en/store-settings-overview.md
+++ b/docs/tutorials/en/store-settings-overview.md
@@ -3,8 +3,8 @@ title: 'Store Settings Overview'
 id: 6VtlMoid6iM9dP14X1CopT
 status: PUBLISHED
 createdAt: 2023-03-29T23:00:51.439Z
-updatedAt: 2023-03-29T23:07:38.446Z
-publishedAt: 2023-03-29T23:07:38.446Z
+updatedAt: 2023-09-13T22:38:50.560Z
+publishedAt: 2023-09-13T22:38:50.560Z
 firstPublishedAt: 2023-03-29T23:07:38.446Z
 contentType: tutorial
 productTeam: Management
@@ -17,14 +17,12 @@ subcategory: 5RAUzLD6X9Wa1maenj1eGA
 
 **Store Settings** are the configurations applied to your store, storefront and how your end customers interact with your ecommerce. We have grouped all settings applied to your store under the __Store Settings__ section on the left navigation menu. That is where you can access settings applied to Payments, Orders, Email Templates, Shipping, Product, Storefront, Channels and Intelligent Search. 
 
-To access this feature, click on the __Store Settings__ icon on the left navigation menu, and click on the desired section.
+To access this feature, click __Store Settings__ on the left navigation menu, and click on the desired section.
 
 <div class="alert alert-warning" role="alert">
 Note that the settings you had configured in the previous environment have not changed. We have only rearranged how you reach them.  
 </div>
 
-![Admin v4 Store settings menu EN](https://images.ctfassets.net/alneenqid6w5/2EIX54YHzIivbQjreHGV4B/de97901ab7998117667296e7ce096cf2/Admin_v4_Store_settings_menu_EN.jpg)
-
 Check out more details about the different sections and pages of this menu below. 
 
 ## Payment
diff --git a/docs/tutorials/en/styles-overview.md b/docs/tutorials/en/styles-overview.md
index 552c620e6..8e75345b8 100644
--- a/docs/tutorials/en/styles-overview.md
+++ b/docs/tutorials/en/styles-overview.md
@@ -19,7 +19,7 @@ The **Styles** page allows you to define the typography and color palette of you
 
 To access it, log in to VTEX Admin, access **Storefront > Styles**, and check out the main tools available in the interface.
 
-![Styles - Overview](https://images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/f87ba6014f0f8bee71aedf4b7c24c66b/EN.png)
+![Styles - Overview](//images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/f87ba6014f0f8bee71aedf4b7c24c66b/EN.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   To apply and preview the changes in your store's styles, make sure to use a workspace that supports production traffic, i.e., <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace)">production workspaces</a>. 
diff --git a/docs/tutorials/en/subscription-plans.md b/docs/tutorials/en/subscription-plans.md
index 5895aeca2..df3e99994 100644
--- a/docs/tutorials/en/subscription-plans.md
+++ b/docs/tutorials/en/subscription-plans.md
@@ -21,7 +21,7 @@ To offer subscription plans for your customers, you need to install the Subscrip
 
 On the **Plans** page, you can view and manage the subscription plans available to your customers, as illustrated below.
 
-![planslist EN](https://images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/0355551976bbb3465d4ddad5ca8cd254/planslist_EN.png)
+![planslist EN](//images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/0355551976bbb3465d4ddad5ca8cd254/planslist_EN.png)
 
 Here are the main features of this page:
 
diff --git a/docs/tutorials/en/synonym-list.md b/docs/tutorials/en/synonym-list.md
new file mode 100644
index 000000000..a3b283cc5
--- /dev/null
+++ b/docs/tutorials/en/synonym-list.md
@@ -0,0 +1,112 @@
+---
+title: 'Synonym list'
+id: 3E1fi0C6tVrR0klMFXAaU8
+status: PUBLISHED
+createdAt: 2024-06-07T13:18:30.251Z
+updatedAt: 2024-06-17T13:55:16.006Z
+publishedAt: 2024-06-17T13:55:16.006Z
+firstPublishedAt: 2024-06-17T13:43:23.975Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: synonym-list
+locale: en
+legacySlug: synonym-list
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+The **Synonyms** page allows you to view and manage all Intelligent Search [synonyms](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) added to your store. You can access it in the VTEX Admin by clicking **Storefront > Intelligent Search > Synonyms**.
+
+![lista-sinonimos-en](//images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/7803ace6dbfd3804a8decfa1081ee08e/lista-sinonimos-en.PNG)
+
+The page displays the following information in a table: 
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Column</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Terms</td>
+      <td class="t-body pa5">
+        Terms set as synonyms and the type of synonym:
+        <ul>
+          <li><i class="fas fa-exchange-alt"></i> Bidirectional</li>
+          <li><i class="fas fa-long-arrow-alt-right"></i> Unidirectional</li>
+        </ul>
+        Learn more in the
+        <a
+          href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#types-of-synonyms"
+          target="_blank"
+          rel="noopener noreferrer"
+          >Types of synonyms</a> article.
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Created on</td>
+      <td class="t-body pa5">Synonym created date.</td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Status</td>
+      <td class="t-body pa5">
+        Synonym status, which can be:
+        <ul>
+          <li>Active</li>
+          <li>Inactive</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+This page allows you to do the following: 
+
+- [Create synonyms](#creating-synonyms)
+- [Import synonyms](#importing-synonyms)
+- [Search for synonyms](#searching-for-synonyms)
+- [Filter synonyms](#filtering-synonyms)
+- [Edit synonyms](#editing-synonyms)
+- [Delete synonyms](#deleting-synonyms)
+
+## Creating synonyms
+
+You can create synonyms individually by clicking the `Create Synonym` button. Follow the instructions described in [Configuring synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#creating-synonyms-individually).
+
+## Importing synonyms
+
+You can create synonyms in bulk by importing a CSV file using the` Import` button. Check out the instructions in the [Configuring synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#importing-csv) article to learn about the spreadsheet template and how to upload it. 
+
+## Searching for synonyms
+
+The Synonyms page allows you to search for any term configured as a synonym using the search bar. The synonyms listed are updated automatically.
+
+## Filtering synonyms
+
+You can filter the synonym list using the following options: 
+
+* **Status**
+    * Active
+    * Inactive
+* **Creation date**
+    * Today
+    * Yesterday
+    * Last 7 days
+    * Last 15 days
+    * Last 30 days
+    * Last 3 months
+    * Last 12 months
+
+## Editing synonyms
+
+To edit an existing synonym, click its corresponding row in the synonym list. Learn more about the editable fields in the [Configuring synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#creating-synonyms-individually) article. 
+
+## Deleting synonyms
+
+To delete a synonym, follow the steps below:
+
+1. Hover over the synonym row.
+2. Click the trash can icon <i class="fas fa-trash-alt"></i>.
+3. Click `Delete` to confirm.
diff --git a/docs/tutorials/en/table-of-base-prices.md b/docs/tutorials/en/table-of-base-prices.md
index 224f96eeb..5ba32f46a 100644
--- a/docs/tutorials/en/table-of-base-prices.md
+++ b/docs/tutorials/en/table-of-base-prices.md
@@ -44,7 +44,7 @@ The next spreadsheet fields are optional, used only to make SKU identification e
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/2XX0xwgVreVnFb6U2rjJR7/3d3cd52b27e5831b6b105e8104e20714/baseprices_table.png" style="display: block; margin-left: auto; margin-right: auto;" alt="base prices table" title="base prices table">
+    <img src="https://images.ctfassets.net/alneenqid6w5/2XX0xwgVreVnFb6U2rjJR7/3d3cd52b27e5831b6b105e8104e20714/baseprices_table.png" style="display: block; margin-left: auto; margin-right: auto;" alt="base prices table" title="base prices table">
    </td>
   </tr>
   <tr>
diff --git a/docs/tutorials/en/telesales-features.md b/docs/tutorials/en/telesales-features.md
index 2d4ac41ae..2361367e6 100644
--- a/docs/tutorials/en/telesales-features.md
+++ b/docs/tutorials/en/telesales-features.md
@@ -1,10 +1,10 @@
 ---
 title: 'Telesales features'
 id: UqhiccIRIK2KD0OqkzJaS
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-05-13T18:26:51.189Z
-updatedAt: 2023-03-07T00:19:05.776Z
-publishedAt: 2023-03-07T00:19:05.776Z
+updatedAt: 2023-12-20T16:58:46.983Z
+publishedAt: 2023-10-18T17:09:06.185Z
 firstPublishedAt: 2021-05-17T12:07:02.897Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -37,7 +37,7 @@ The telesales toolbar is displayed at the top of your store's website for users
 To learn how to use this feature, check out the [Telesales toolbar](https://help.vtex.com/en/tutorial/usando-e-customizando-toolbar-de-televendas--tutorials_5500) tutorial.
 
 <div class = "alert alert-info">
-A use case for the telesales feature is to import orders from other platforms to the VTEX <b>Orders</b> module. To do this, you can associate a specific <a href="https://help.vtex.com/en/tutorial/creating-a-sales-policy--563tbcL0TYKEKeOY4IAgAE">trade policy</a> with payment by note <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-promissory--5pW7avTwtyQcMu4uiW8quQ">payable</a> (payment method immediately and manually approved by the operator).
+A use case for the telesales feature is to import orders from other platforms to the VTEX <b>Orders</b> module. To do this, you can associate a specific <a href="https://help.vtex.com/en/tutorial/creating-a-sales-policy--563tbcL0TYKEKeOY4IAgAE">trade policy</a> with payment <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ">Notes Payable</a> (payment method immediately and manually approved by the operator).
   </div>
 
 ### My Account
diff --git a/docs/tutorials/en/telesales-toolbar.md b/docs/tutorials/en/telesales-toolbar.md
index 3133bc9fb..c1d99be78 100644
--- a/docs/tutorials/en/telesales-toolbar.md
+++ b/docs/tutorials/en/telesales-toolbar.md
@@ -3,8 +3,8 @@ title: 'Telesales toolbar'
 id: tutorials_5500
 status: PUBLISHED
 createdAt: 2017-04-27T21:48:31.368Z
-updatedAt: 2023-03-29T19:50:13.858Z
-publishedAt: 2023-03-29T19:50:13.858Z
+updatedAt: 2023-12-07T15:29:46.537Z
+publishedAt: 2023-12-07T15:29:46.537Z
 firstPublishedAt: 2017-04-27T23:11:19.311Z
 contentType: tutorial
 productTeam: Shopping
@@ -19,7 +19,7 @@ The telesales toolbar is displayed at the top of your store's website for users
 
 Once the registered operator logs into the store environment, the toolbar will be displayed at the top of all sections of the website.
 
-![toolbartelevendas EN](https://images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ab7894a0dc03568e5e1745a0adbec2f3/toolbartelevendas_EN.png)
+![toolbartelevendas EN](//images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ab7894a0dc03568e5e1745a0adbec2f3/toolbartelevendas_EN.png)
 
 See below the main features of the telesales toolbar:
 *   [Log in as customer](#log-in-as-customer)
@@ -58,8 +58,9 @@ By clicking on the customer's name, the operator will view the following informa
 
 ## Related articles
 
-*   [Roles - telesales](https://help.vtex.com/en/tutorial/como-criar-um-usuario-de-televendas--frequentlyAskedQuestions_4227.)
-*   [Customizing the telesales toolbar](https://help.vtex.com/en/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg)
-*   [My orders](https://help.vtex.com/pt/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#pedidos)
-*   [How to use telesales features](https://help.vtex.com/en/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS)
-*   [How to configure telesales features](https://help.vtex.com/en/tutorial/como-configurar-as-funcionalidades-de-televendas--76FNgQP2Glc4umMJ5Yr50R)
+* [Predefined roles - Call center operator](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator)
+* [Creating a call center user](https://help.vtex.com/en/tutorial/how-can-i-create-callcenter-user--frequentlyAskedQuestions_4227)
+* [Customizing the telesales toolbar](https://help.vtex.com/en/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg)
+* [My orders](https://help.vtex.com/pt/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#pedidos)
+* [How to use telesales features](https://help.vtex.com/en/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS)
+* [How to configure telesales features](https://help.vtex.com/en/tutorial/como-configurar-as-funcionalidades-de-televendas--76FNgQP2Glc4umMJ5Yr50R)
diff --git a/docs/tutorials/en/test-kr1.md b/docs/tutorials/en/test-kr1.md
new file mode 100644
index 000000000..abecf139e
--- /dev/null
+++ b/docs/tutorials/en/test-kr1.md
@@ -0,0 +1,18 @@
+---
+title: 'Test KR1'
+id: 4IbRozfaZJHar1adTlr1yq
+status: DRAFT
+createdAt: 2024-06-07T18:51:10.051Z
+updatedAt: 2024-06-07T18:52:10.590Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: VTEX IO
+author: 
+slug: test-kr1
+locale: en
+legacySlug: test-kr1
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+
diff --git a/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md b/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md
new file mode 100644
index 000000000..a2e0de12b
--- /dev/null
+++ b/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md
@@ -0,0 +1,46 @@
+---
+title: 'The order was split into packages with separate deliveries'
+id: 3OCOC82543vOsc3Ex32XTY
+status: PUBLISHED
+createdAt: 2024-06-19T15:03:37.373Z
+updatedAt: 2024-06-19T15:13:11.172Z
+publishedAt: 2024-06-19T15:13:11.172Z
+firstPublishedAt: 2024-06-19T15:13:11.172Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: the-order-was-split-into-packages-with-separate-deliveries
+locale: en
+legacySlug: the-order-was-split-into-packages-with-separate-deliveries
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags / Keywords:** separate deliveries, order split, packages, shipping, pre-sale products.
+
+On VTEX, customers may receive their orders split into several packages, regardless of whether the [order has been split](https://help.vtex.com/en/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV) on the platform. Customers can receive their order items in separate packages in the following cases:
+
+* **Order with different sellers:** An order is generated for each seller, resulting in at least one package per seller's delivery.
+* **Selection of white label sellers:** Orders involving [white label sellers](https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) may be delivered in separate packages.
+* **Seller with different SLAs for shipping items:** Even if a single seller fulfills the order, different product SLAs can cause the order to be split into multiple packages.
+* **Pre-sale products:** Orders containing both [pre-sale](https://help.vtex.com/en/tutorial/cadastrar-um-produto-para-pre-venda--4o6cUJ4gIg0MQWW8WfN34K) and regular products will be delivered in separate packages.
+
+When an order is generated, the estimated delivery date at checkout applies to both pre-sale and regular products. However, this is only a delivery estimate. Once payment is approved, the order is divided into different packages, one for pre-sale products and one for regular products. 
+
+The delivery date for each package will be adjusted based on the `shippingEstimateDate` for each product, which can be checked via the [Get order](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-) endpoint.
+
+## Solution
+
+To avoid splitting packages in orders that include pre-sale products, you can configure [shipping groups](https://help.vtex.com/en/tutorial/como-funciona-a-remessa). This allows you to group all packages to be delivered by the same carrier and from the same [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) into a single shipment.
+
+<div class="alert alert-danger">
+By configuring shipping groups, this behavior will be applied to all orders with different delivery dates, not just those containing pre-sale products.
+</div>
+
+### Configuring shipping groups
+
+To configure shipping groups in your store, follow the steps below: 
+
+1. In the VTEX Admin, go to **Store Settings > Shipping > Settings**, or type **Shipping** in the search bar at the top of the page and select **Store Settings / Shipping**.
+2. On the **General Settings** page, in the section **Delivery Groups**, enter the desired number of days for the [shipment](https://help.vtex.com/en/tutorial/como-funciona-a-remessa) in the field _Create shipping groups with intervals of {X} day(s)_.
+3. Click **Save**.
+
diff --git a/docs/tutorials/en/the-price-in-the-search-result-is-different-from-the-product-page.md b/docs/tutorials/en/the-price-in-the-search-result-is-different-from-the-product-page.md
index 64083f596..a3a85922a 100644
--- a/docs/tutorials/en/the-price-in-the-search-result-is-different-from-the-product-page.md
+++ b/docs/tutorials/en/the-price-in-the-search-result-is-different-from-the-product-page.md
@@ -3,8 +3,8 @@ title: 'The price in the search result is different from the product page'
 id: 1108Xha3zw6ZvVUINfY7HR
 status: PUBLISHED
 createdAt: 2022-11-22T14:26:20.489Z
-updatedAt: 2022-11-22T14:42:50.738Z
-publishedAt: 2022-11-22T14:42:50.738Z
+updatedAt: 2024-06-04T12:45:41.670Z
+publishedAt: 2024-06-04T12:45:41.670Z
 firstPublishedAt: 2022-11-22T14:42:50.738Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -12,7 +12,7 @@ author: 2o8pvz6z9hvxvhSoKAiZzg
 slug: the-price-in-the-search-result-is-different-from-the-product-page
 locale: en
 legacySlug: the-price-in-the-search-result-is-different-from-the-product-page
-subcategory: 4tkE7m5rJisNuhJisIxWHD
+subcategory: 23NGhMgqA1eCYad7kzRFGu
 ---
 
 When [updating a SKU price](https://help.vtex.com/en/tutorial/alteracao-de-preco-de-sku--tutorials_95), the price in the search result may differ from the price or inventory on the product page if the store uses [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb). 
diff --git a/docs/tutorials/en/tools-to-help-the-performance-of-your-e-commerce.md b/docs/tutorials/en/tools-to-help-the-performance-of-your-e-commerce.md
index b64728467..8fa18d2fd 100644
--- a/docs/tutorials/en/tools-to-help-the-performance-of-your-e-commerce.md
+++ b/docs/tutorials/en/tools-to-help-the-performance-of-your-e-commerce.md
@@ -1,10 +1,10 @@
 ---
 title: 'Tools to help the performance of your E-Commerce'
 id: tutorials_4852
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:49:27.344Z
-updatedAt: 2020-07-26T15:27:37.237Z
-publishedAt: 2020-07-26T15:27:37.237Z
+updatedAt: 2024-03-11T13:20:56.413Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:11:17.373Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/total-shipping-cost.md b/docs/tutorials/en/total-shipping-cost.md
index 70983c834..f87eedf91 100644
--- a/docs/tutorials/en/total-shipping-cost.md
+++ b/docs/tutorials/en/total-shipping-cost.md
@@ -31,7 +31,7 @@ See how they are calculated:
 
 So, in general, the total shipping cost is calculated as follows:
 
-![Custo-final-envio-EN](https://images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/4b04d0319eb18cd1ee0e9c03858c5bc1/Custo-final-envio-EN.svg)
+![Custo-final-envio-EN](//images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/4b04d0319eb18cd1ee0e9c03858c5bc1/Custo-final-envio-EN.svg)
 
 <div class="alert alert-danger">
 If the <b>price-based charge</b> is lower than the <b>insurance charge</b>, the system only considers the insurance charge. The price-based charge will not be taken into account for the total shipping cost.<p>
diff --git a/docs/tutorials/en/tracking-your-sales-analytics.md b/docs/tutorials/en/tracking-your-sales-analytics.md
index d51a04f17..ce3c8a167 100644
--- a/docs/tutorials/en/tracking-your-sales-analytics.md
+++ b/docs/tutorials/en/tracking-your-sales-analytics.md
@@ -1,10 +1,10 @@
 ---
 title: 'Tracking your sales analytics'
 id: 5QtyTR0jFy9gDnr4EYCjdq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-09-10T13:32:39.637Z
-updatedAt: 2020-09-11T00:16:35.791Z
-publishedAt: 2020-09-11T00:16:35.791Z
+updatedAt: 2023-10-18T15:24:34.576Z
+publishedAt: 
 firstPublishedAt: 2020-09-10T17:37:50.007Z
 contentType: tutorial
 productTeam: Management
@@ -36,7 +36,7 @@ The Insights interface displays the sales metrics of your store in three dashboa
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/2f8tj5XokKtnZOvjfgmFVf/ee8427085b56a71a78e7271156a149eb/Insights_-_Conhecendo_a_interface__2_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Conhecendo a interface" title="Insights - Conhecendo a interface">
+    <img src="https://images.ctfassets.net/alneenqid6w5/2f8tj5XokKtnZOvjfgmFVf/ee8427085b56a71a78e7271156a149eb/Insights_-_Conhecendo_a_interface__2_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Conhecendo a interface" title="Insights - Conhecendo a interface">
    </td>
   </tr>
   <tr>
@@ -55,7 +55,7 @@ This dashboard allows you to compare the value of the consolidated metrics betwe
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/5lKQrdbytYWAaMV3tHnOi4/ad7df2bffda20bafbd679491334828ab/Insights_-_Visa__o_Geral__2_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Visão Geral" title="Insights - Visão Geral">
+    <img src="https://images.ctfassets.net/alneenqid6w5/5lKQrdbytYWAaMV3tHnOi4/ad7df2bffda20bafbd679491334828ab/Insights_-_Visa__o_Geral__2_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Visão Geral" title="Insights - Visão Geral">
    </td>
   </tr>
   <tr>
@@ -74,7 +74,7 @@ This dashboard allows you to trace the evolution of the metrics throughout the d
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/L43eNghJLlakmOFcGmKiM/dea01625e5f1adeb73d9e5949a6986ce/Insights_-_Detalhes__2_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 1" title="Insights - Detalhes 1">
+    <img src="https://images.ctfassets.net/alneenqid6w5/L43eNghJLlakmOFcGmKiM/dea01625e5f1adeb73d9e5949a6986ce/Insights_-_Detalhes__2_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 1" title="Insights - Detalhes 1">
    </td>
   </tr>
   <tr>
@@ -89,7 +89,7 @@ This dashboard allows you to trace the evolution of the metrics throughout the d
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/1TExoNJjCZInwh3LGQrkzO/00a419a264cca2d9fbe7a50d26bd2dbf/image15.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 2" title="Insights - Detalhes 2">
+    <img src="https://images.ctfassets.net/alneenqid6w5/1TExoNJjCZInwh3LGQrkzO/00a419a264cca2d9fbe7a50d26bd2dbf/image15.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 2" title="Insights - Detalhes 2">
    </td>
   </tr>
   <tr>
@@ -115,7 +115,7 @@ This dashboard allows you to trace the volume of sessions in the intermediate st
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/4DdN3hdCz7CdoukLu3H0Ea/bfac11a598fd989f1b0370d12566dbb3/Insights_-_Funil_de_conversa__o__2_.png?h=250" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Funil de conversão" title="Insights - Funil de conversão">
+    <img src="https://images.ctfassets.net/alneenqid6w5/4DdN3hdCz7CdoukLu3H0Ea/bfac11a598fd989f1b0370d12566dbb3/Insights_-_Funil_de_conversa__o__2_.png?h=250" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Funil de conversão" title="Insights - Funil de conversão">
    </td>
   </tr>
   <tr>
diff --git a/docs/tutorials/en/transactional-emails-for-subscription-orders.md b/docs/tutorials/en/transactional-emails-for-subscription-orders.md
index 657c063f9..42ad38c24 100644
--- a/docs/tutorials/en/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/en/transactional-emails-for-subscription-orders.md
@@ -3,8 +3,8 @@ title: 'Transactional emails for subscription orders'
 id: 2NYHqHMRqZ43Cn6s84ZCB5
 status: PUBLISHED
 createdAt: 2020-02-11T15:13:38.504Z
-updatedAt: 2021-11-30T18:14:37.654Z
-publishedAt: 2021-11-30T18:14:37.654Z
+updatedAt: 2023-12-21T14:14:10.536Z
+publishedAt: 2023-12-21T14:14:10.536Z
 firstPublishedAt: 2020-02-17T21:15:14.903Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -28,6 +28,10 @@ You can also create your own email template. Learn how to [configure transaction
 
 ## How your customer tracks their Subscription Orders
 
+<div class = "alert alert-info">
+In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
+</div>
+
 Each action that occurs within the Subscription order flow contains a trigger that sends an email notifying your customer. After activating the Subscription, your customer will receive e-mails with details of the status of each subscription order every time they perform an action.
 
 It is not necessary to activate the e-mail sending manually, since they are sent automatically according to each scenario included in the Message Center. However, if you wish, you can disable the sending of specific emails:
diff --git a/docs/tutorials/en/transactions-events.md b/docs/tutorials/en/transactions-events.md
index 665274341..16464b342 100644
--- a/docs/tutorials/en/transactions-events.md
+++ b/docs/tutorials/en/transactions-events.md
@@ -76,4 +76,4 @@ Generally, affiliations allow you to set a capture date to force a capture and a
 
 Here you can see the automatic capture schedule date:
 
-![captura-auto-agendada pt](https://images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
+![captura-auto-agendada pt](//images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
diff --git a/docs/tutorials/en/transferring-store-ownership.md b/docs/tutorials/en/transferring-store-ownership.md
index f06b399db..52fa4d55d 100644
--- a/docs/tutorials/en/transferring-store-ownership.md
+++ b/docs/tutorials/en/transferring-store-ownership.md
@@ -25,7 +25,7 @@ The Sponsor management page allows you to identify the current Sponsor user, tra
 
 You should see a screen that is similar to the image below, with contact information for the current Sponsor user, a disclaimer indicating the risks associated with transferring store ownership and a button that allows you to acknowledge the risks and transfer ownership anyway.
 
-![Sponsor management panel](https://images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/b4b9533827aeb3d03960c24eb092cb98/Sponsor_Management_en.png)
+![Sponsor management panel](//images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/b4b9533827aeb3d03960c24eb092cb98/Sponsor_Management_en.png)
 
 ## Steps in the ownership transfer flow
 
@@ -51,7 +51,7 @@ This will complete the ownership transfer – cancelling the invitation will no
 
 The Sponsor user is responsible for critical maintenance and authorization actions, and mistakes made by this user role can have drastic consequences. Therefore, it is essential to track  changes related to this user role. To monitor and audit  account ownership transfers, you can access the activity log on the Sponsor management page by clicking on the **Activity Log** button. 
 
-![Activity Log](https://images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/a4d638c4dac1442a317acc1e40686326/Activity_Log_en.gif)
+![Activity Log](//images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/a4d638c4dac1442a317acc1e40686326/Activity_Log_en.gif)
 
 All events related to the transfer of account ownership are logged in the activity log with the date they occurred and the user associated with the event.
 
diff --git a/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
index a20904176..bcb3302c2 100644
--- a/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
@@ -3,8 +3,8 @@ title: 'Troubleshooting errors in subscription orders'
 id: uLL8AYBGdtAmbbdL5gRCf
 status: PUBLISHED
 createdAt: 2020-02-05T14:32:49.763Z
-updatedAt: 2022-12-05T17:09:40.639Z
-publishedAt: 2022-12-05T17:09:40.639Z
+updatedAt: 2023-12-21T14:07:42.772Z
+publishedAt: 2023-12-21T14:07:42.772Z
 firstPublishedAt: 2020-02-11T15:00:00.666Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: how-to-troubleshoot-subscription-orders-with-errors
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
+<div class = "alert alert-info">
+You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
+</div>
+
 You can identify and manage errors in subscription orders in the Admin, in **Subscriptions** > **Dashboards** > **Subscription Orders**.
 
 There are two types of errors that can occur in subscription orders:
@@ -28,7 +32,7 @@ Issues in subscription cycles indicate that an obstacle prevented a subscription
 
 The **Cycles with an issue** tab displays subscription orders with such problems, as illustrated in the image below.
 
-![cicloscomproblema EN](https://images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/8985fa930def4ec541d9127bc855740d/cicloscomproblema_EN.png)
+![cicloscomproblema EN](//images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/8985fa930def4ec541d9127bc855740d/cicloscomproblema_EN.png)
 
 In this tab, you can manage orders with issues in subscription cycles and retry placing orders manually. For example, when a product is unavailable, you can edit its inventory and then try to order it again.
 
@@ -185,7 +189,7 @@ Payment errors occur during the payment approval flow, such as having a credit c
 
 You can view orders with this error on the **Payment Error** tab, as shown in the image below.
 
-![errosdepagamento EN](https://images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/4bea9e2c3fa3385e1fd1b1c0add2b0f0/errosdepagamento_EN.png)
+![errosdepagamento EN](//images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/4bea9e2c3fa3385e1fd1b1c0add2b0f0/errosdepagamento_EN.png)
 
 To analyze payment errors, follow the steps below:
 
@@ -193,7 +197,7 @@ To analyze payment errors, follow the steps below:
 2. Click on the **Dashboards** tab.
 3. In the **Subscription Orders** section, click on the **Payment Error** tab.
 4. Identify the order you want to analyze and click on its ID, as illustrated in the image below. You will be redirected to the order details page in the **All Orders** module.
-  ![EN Log Erro de pagamento](https://images.ctfassets.net/alneenqid6w5/2Bb1XYgaZEdNMVhcnX5lF3/a10c69783d57d09b70234c6dda18542d/EN_Log_Erro_de_pagamento.png)
+  ![EN Log Erro de pagamento](//images.ctfassets.net/alneenqid6w5/2Bb1XYgaZEdNMVhcnX5lF3/a10c69783d57d09b70234c6dda18542d/EN_Log_Erro_de_pagamento.png)
 5. Then, click on **View transaction details** under the **Payment** card. You will be redirected to the **Transactions** page in the **Payments** module.
 6. On the **Transactions** page, you can view and analyze the order transaction events. Read the article [Viewing the order's details in Payments](https://help.vtex.com/en/tutorial/como-visualizar-detalhes-do-pedido) for more information.
 
diff --git a/docs/tutorials/en/understanding-b2b-orders.md b/docs/tutorials/en/understanding-b2b-orders.md
index 882862ea5..28ec99bc7 100644
--- a/docs/tutorials/en/understanding-b2b-orders.md
+++ b/docs/tutorials/en/understanding-b2b-orders.md
@@ -19,7 +19,7 @@ In B2B e-commerce operations, it is often necessary to inform an order's status
 
 The **B2B Orders** app makes this process simple, allowing any employee to consult the company's orders through its online store.
 
-![orders VTEX B2B](https://images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
+![orders VTEX B2B](//images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
 
 This self-service experience is possible, thanks to API integration with the ERP. With this, the employee can search for orders by:
 
diff --git a/docs/tutorials/en/understanding-how-indexation-works.md b/docs/tutorials/en/understanding-how-indexation-works.md
index 2b19d4611..0ffb0b27b 100644
--- a/docs/tutorials/en/understanding-how-indexation-works.md
+++ b/docs/tutorials/en/understanding-how-indexation-works.md
@@ -3,8 +3,8 @@ title: 'How indexing works'
 id: tutorials_256
 status: PUBLISHED
 createdAt: 2017-04-27T22:11:43.688Z
-updatedAt: 2023-03-29T19:50:49.722Z
-publishedAt: 2023-03-29T19:50:49.722Z
+updatedAt: 2024-03-04T16:39:16.578Z
+publishedAt: 2024-03-04T16:39:16.578Z
 firstPublishedAt: 2017-04-27T23:03:11.322Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,6 +15,12 @@ legacySlug: understanding-how-indexation-works
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
+<div class="alert alert-warning">
+<p>This tutorial is valid only for stores using <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">Legacy CMS Portal</a> search.</p>
+<p>If your store uses <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>, check <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Indexing History
+</a> to follow the indexing process.</p>
+</div>
+
 Indexing is a process that prepares the general SKU data, such as catalogue data, prices and inventory, and updates the information to serve as a basis for searches and for setting up the site's product display shelves.
 
 Every time product listing data is altered as shown below, the database is reindexed. 
@@ -27,7 +33,7 @@ Every time product listing data is altered as shown below, the database is reind
 
 Once a product is marked for reindexing, the text _pending indexing_ is included in the product listing in admin. The indexer places these products in a queue for processing, with a 2-minute waiting time. After the 2 minutes, the product is available for indexing. In this process, all the VTEX modules are consulted, with prices and availability updated for every sales policy. This process takes an average of 4 minutes.
 
-![indexaçao.en](https://images.ctfassets.net/alneenqid6w5/1OCaCwIsLA1CeKVqnwIU7E/b014aa1be9f142f208b3c000b3e80998/indexa__ao.en.png)
+![indexaçao.en](//images.ctfassets.net/alneenqid6w5/1OCaCwIsLA1CeKVqnwIU7E/b014aa1be9f142f208b3c000b3e80998/indexa__ao.en.png)
 
 ## Indexing Report
 
@@ -42,7 +48,7 @@ The products are divided according to each step of the indexing process and to t
 - **Total Indexed**, **Not yet in queue** and **Total in Queue**: relate to the stages of the product in the process **Not yet in queue** are those that were changed in less than 2 minutes, and _Total na fila_ (Total in queue) are those that have started the indexing process, after these 2 minutes.
 - **In queue from 1 to 2 hours** and **In queue from 2 to 4 hours**, **In queue from 4 to 8 hours**: represent the periods for which the products have been in the indexing process.
 
-![Indexingreport](https://images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
+![Indexingreport](//images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
 
 The indexing report also indicates the time the last item took to be reindexed. This is shown in the upper right side of the report (see the image above). 
 
diff --git a/docs/tutorials/en/understanding-how-the-cache-works.md b/docs/tutorials/en/understanding-how-the-cache-works.md
index 4518350f8..82447429f 100644
--- a/docs/tutorials/en/understanding-how-the-cache-works.md
+++ b/docs/tutorials/en/understanding-how-the-cache-works.md
@@ -25,11 +25,11 @@ The browser submits a **request** and the server’s reply is its **response**.
 
 See the schematic chart shown below:
 
-![How the cache works - communication between server and browser](https://images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/c0dd7b6c39dd72bc71c60185e926fa67/1_EN.png)
+![How the cache works - communication between server and browser](//images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/c0dd7b6c39dd72bc71c60185e926fa67/1_EN.png)
 
 The cache is represented by a layer between the browser and server. So when a **request** is made, instead of the system going straight to the server to find the information, it first goes to this layer, which makes the response much quicker. A schematic diagram is shown below:
 
-![How cache works - communication with cache (without expiring)](https://images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/fa4aaef1190355a31e8afb5b08a85630/2_EN.png)
+![How cache works - communication with cache (without expiring)](//images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/fa4aaef1190355a31e8afb5b08a85630/2_EN.png)
 
 However, since the latest information is in the server, the cache has to be updated from time to time. The frequency varies according to the type of **request**: it is different for a single page, for a java script or CSS file, or for an image.
 
@@ -58,7 +58,7 @@ As mentioned the cache duration time varies for each type of **request**. The fo
 
 When a **request** cache (page or file) expires, and you make a new request (i.e. load the URL again) the system goes to the server, collects the latest information and updates the content of the URL in the cache. Once updated, the cached version will be returned for a new request for the URL. The following illustrates how this works:
 
-![How cache works - communication with cache (expired)](https://images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/5ab850cc08928054e7c5133016702c17/3_EN.png)
+![How cache works - communication with cache (expired)](//images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/5ab850cc08928054e7c5133016702c17/3_EN.png)
 
 So we can separate responses into two groups: cached and not cached.
 
diff --git a/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md b/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md
index 2a64e004f..a908c0b2c 100644
--- a/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md
+++ b/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md
@@ -15,7 +15,7 @@ legacySlug: understanding-storebuilder-and-stylesbuilder
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-![UI Blocks Voando.mp4](https://images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
+![UI Blocks Voando.mp4](//images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
 
 This documentation is structured to explain Store 2.xx's StoreBuilder and StyleBuilder.  Throughout the documentation we will be using DreamStore (a `Store 2.xx` template) to understand key concepts that will allow you to successfully structure and style your store.
 
@@ -39,7 +39,7 @@ Store 2 makes big paradigm shifts from Store 1 by introducing the concept of **b
 
 Let's look inside DreamStore's `/manifest.json` in order to see what our app requires to function properly:
 
-![Screen Shot 2019-01-25 at 16.40.06](https://images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
+![Screen Shot 2019-01-25 at 16.40.06](//images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
 
 Notice how we have two `builders` specified:
 
@@ -62,7 +62,7 @@ Since every theme app (a store) makes use of the `Store` app (through the `"vtex
 
 Let's `vtex link` and send our DreamStore app to a workspace so we can study it for a minute.
 
-![Screen Shot 2019-01-27 at 22.24.47](https://images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
+![Screen Shot 2019-01-27 at 22.24.47](//images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
 
 
 If you're familiar  with React or other modern JavaScript frameworks, you will be familiar with the concept of components on a webpage. As you can quickly tell, our webpage has a `header`, `carousel` and a `shelf`.  How were these components inserted? 
@@ -101,7 +101,7 @@ In order to better understand this, we should look into how `Store 2.xx` app wor
 
 Let's look inside Store2.xx's `/manifest.json` file to see what the `Store` app brings to the table.
 
-![Screen Shot 2019-01-25 at 17.18.56](https://images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
+![Screen Shot 2019-01-25 at 17.18.56](//images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
 
 As we can see it's structured similarly to `Dreamstore`'s `manifest.json`.  
 
@@ -146,7 +146,7 @@ Let's now explore how the blocks inside a page (a page is just a block containin
 Open the `store` folder and open `interfaces.json`.
 
 ### Interfaces
-![Screen Shot 2019-01-25 at 17.35.10](https://images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
+![Screen Shot 2019-01-25 at 17.35.10](//images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
 
 An interface is a conjunction of `blocks` and exists exclusively inside `Store2.xx`. It serves as a contract, using well defined constraits explaining how the blocks will work together.
 
@@ -203,7 +203,7 @@ Let's continue analyzing `store.home`.  I'll be commenting inline.
 ```
 
 If we scroll we can see the same JSON objects defining and setting the block organization. Another example is the search results page:
-![Screen Shot 2019-01-25 at 18.22.12](https://images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
+![Screen Shot 2019-01-25 at 18.22.12](//images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
 
 The information describes the following interface information:
   
@@ -224,7 +224,7 @@ It's time to visit  Dreamstore app's blocks.json and understand how the entire s
 
 ### Structuring and configuring our store with `StoreBuilder`
 
-![Codigo voando blocks.mp4](https://images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
+![Codigo voando blocks.mp4](//images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
 
 Open up `/blocks.json` and find our trusty `store.home.`Let's begin by analyzing the first block inside `store.home`: `carousel#home`.
 
@@ -246,12 +246,12 @@ Scroll down until we find `carousel#home`. Through `props` our `carousel#home` h
   
   
 ### Styling our store with `StylesBuilder`
-![StyleBuilder.mp4](https://images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
+![StyleBuilder.mp4](//images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
 
 
 StylesBuilder takes your styles.json file when building and generates uses [Tachyons](https://tachyons.io/) generator to produce your store's CSS.  
 
 We designed StylesBuilder to be extremely intuitive and self explanatory.  It's as simple as adjusting the hexcodes accordingly and seeing the results permeate throughout the store.  
 
-![Screen Shot 2019-01-28 at 00.40.17](https://images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
+![Screen Shot 2019-01-28 at 00.40.17](//images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
 
diff --git a/docs/tutorials/en/understanding-the-additional-shipping-cost.md b/docs/tutorials/en/understanding-the-additional-shipping-cost.md
index e402bb0ae..ad3498598 100644
--- a/docs/tutorials/en/understanding-the-additional-shipping-cost.md
+++ b/docs/tutorials/en/understanding-the-additional-shipping-cost.md
@@ -29,7 +29,7 @@ There are three possible ways to add a value to the shipping rate: additional c
 
 In this field, a percentage of the product's price must be set, which will then be added to the shipping value.
 
-![adicionalfrete1 EN](https://images.ctfassets.net/alneenqid6w5/OqyvMFeOU6OmsMGAMQ2km/ba3c318b0b158ccbccb511863dc7fc57/adicionalfrete1_EN.png)
+![adicionalfrete1 EN](//images.ctfassets.net/alneenqid6w5/OqyvMFeOU6OmsMGAMQ2km/ba3c318b0b158ccbccb511863dc7fc57/adicionalfrete1_EN.png)
 
 In the example above, the product's price $ 80.00, and the percentage set in the __Additional value__ field is 10%. Therefore, $ 8.00 will be added to the shipping rate. The shipping rate plus this first additional fee results in a $ 18.00 total fee.
 
@@ -43,7 +43,7 @@ The calculation of this field considers the product's weight and its difference
 
 __It looks as follows:__
 
-![adicionalfrete2 EN](https://images.ctfassets.net/alneenqid6w5/1FbPWgvxpuOQeImAS0S6uS/2a9740e4bff83d1a1e3c51d77729bede/adicionalfrete2_EN.png)
+![adicionalfrete2 EN](//images.ctfassets.net/alneenqid6w5/1FbPWgvxpuOQeImAS0S6uS/2a9740e4bff83d1a1e3c51d77729bede/adicionalfrete2_EN.png)
 
 In the example above, the product's lower weight limit range is 100g. The value set in the **Additional value per weight** field is 0.1. Therefore, the amount to be added to the shipping rate total is $ 10.00. As the shipping calculation previously totaled $ 14.00, the final value is now $ 24.00.
 
@@ -58,7 +58,7 @@ This additional fee is calculated on top of the final shipping rate, as opposed
 
 The additional percentage fee is the last shipping calculation made, which means that it's added to the shipping price table value + the other additional fees above * the value set in the field.
 
-![adicionalfrete3 EN](https://images.ctfassets.net/alneenqid6w5/1K03RGdwsMsuQGe8Awqsua/8ffe9ec0b094914ed4d14be361542cad/adicionalfrete3_EN.png)
+![adicionalfrete3 EN](//images.ctfassets.net/alneenqid6w5/1K03RGdwsMsuQGe8Awqsua/8ffe9ec0b094914ed4d14be361542cad/adicionalfrete3_EN.png)
 
 In this case, the value entered in the field __Additional value__ will be the percentage fee that is to be added to the final shipping rate calculation. For example, if shipping, with all its additional fees included, is $ 20.00, and the value set in the Additional Shipping fee field is 10, $ 2.00 would be added to those original $ 20.00, totaling $ 22.00 that the customer would pay for shipping. This is a simple way of having a profit margin on shipping.
 
diff --git a/docs/tutorials/en/understanding-the-cubic-weight-factor.md b/docs/tutorials/en/understanding-the-cubic-weight-factor.md
index 1f9cc3d04..9c25cdcc5 100644
--- a/docs/tutorials/en/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/en/understanding-the-cubic-weight-factor.md
@@ -3,8 +3,8 @@ title: 'Calculating the Cubic Weight Factor'
 id: tutorials_128
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:52.970Z
-updatedAt: 2022-11-08T19:15:57.550Z
-publishedAt: 2022-11-08T19:15:57.550Z
+updatedAt: 2023-12-19T17:17:26.713Z
+publishedAt: 2023-12-19T17:17:26.713Z
 firstPublishedAt: 2017-04-27T23:00:44.419Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -23,8 +23,8 @@ Cubage is the relationship between the volume and weight of the goods, which is
 
 The function of cubage in transport is to avoid filling the entire physical space of the vehicle without using all its capacity in terms of weight or vice versa. Thus, the concept is linked to the ability to complete the loading of a vehicle using its entire volume available for load and weight or tonnage capacity.
 
-- __Real weight:__ is the one indicated on the scale.
-- __Cubed Weight:__ is the calculation that determines the actual space occupied by the package on the vehicle.
+- __Minimum weight:__ is the one indicated on the scale.
+- __Cubic Weight:__ is the calculation that determines the actual space occupied by the package on the vehicle.
 
 ## Cubic Factor
 
@@ -32,33 +32,33 @@ Is the resulting coefficient of the relationship between weight and volume that
 
 ## Calculation
 
-The calculation of the cubed weight is performed by multiplying Length x Width x Height, and dividing the result by the cubic factor provided by the carrier.
+The calculation of the cubic weight is performed by multiplying Length x Width x Height, and dividing the result by the cubic factor provided by the carrier.
+
+<div class="alert alert-warning">
+When calculating the cubic weight factor, VTEX platform does not consider measurement units, and the numbers generated are absolute. Therefore, the measurement units you consider for the calculation will be those of the final result. Notice that the your measurement unit must be the same one used by the carrier.
+</div>
 
 Check out the following example:
 
-![](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
+![example_cubic_weight_en](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
 
 - __Package size:__ `50cm x 15cm x 60cm`
-- __Actual package weight:__ `9kg`
+- __Minimum weight:__ `9kg`
 - __Cubic factor:__ `6.000`
-- __Cubed Weight__: `50cm * 60cm * 15cm / 6.000= 7,5kg`
+- __Cubic weight__: `50cm * 60cm * 15cm / 6.000= 7,5kg`
 
-By comparing the real weight to the cubed weight of the package, the carrier will charge for the actual weight, because it is larger than the cubed weight.
+By comparing the minimum weight to the cubic weight of the package, the carrier will charge for the minimum weight, because it is larger than the cubic weight.
 
 However, the calculation above is merely illustrative. For the carrier, the value registered as cubic factor will be multiplied to the result of `Length x Width x Height`. Which means the calculation is `Length x Width x Height x Cubic Factor`.
 
-That is, if the value offered by your carrier is `6,000`, you must perform the division by 1000. Example: `1.000 / 6.000 = 0,167`.
+That is, if the value offered by your carrier is `6,000`, you must perform the division by 1000. Example: `1000g/6000 cm³ = 0,167`.
 
-When registering a carrier, this is the value you must fill out the __Cubic Weight Factor__ field with:
+This is the value you must fill out the **Cubic weight factor** field in your [shipping policy](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![Cubic Weight](//images.contentful.com/alneenqid6w5/1hQDHg79Z8QaGCiIc0wekq/1d1eef7297b59f508ce508e0b926961f/Cubic_Weight.png)
+![cubic_weight_EN](//images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/dc63a437a83448eaafd90e0fb545879e/cubic_weight_EN.png)
 
 Therefore, the final calculation will be:
 
 - __Package size:__ `50cm x 60cm x 15cm`
-- __Actual package weight:__ `9kg`
-- __Cubed Weight:__ `50cm x 60cm x 15cm x 0,167= 7,515kg`
-
-<div class="alert alert-info">
-  <p>Check with your carrier if the unit of measure is in grams, which is the unit used by VTEX.</p>
-</div>
+- __Minimum weight:__ `9kg`
+- __Cubic weight:__ `50cm x 60cm x 15cm x 0,167= 7,515kg`
diff --git a/docs/tutorials/en/understanding-the-message-center.md b/docs/tutorials/en/understanding-the-message-center.md
index 7093c5f4e..7a847b4d2 100644
--- a/docs/tutorials/en/understanding-the-message-center.md
+++ b/docs/tutorials/en/understanding-the-message-center.md
@@ -31,7 +31,7 @@ Understand the information that each template card contains:
 
 To facilitate browsing, in addition to the free text search field, the interface provided filters per application (modules) and type (standard/default and/or personalized/amended message).
 
-![busca-templates-central-mensagens en](https://images.ctfassets.net/alneenqid6w5/6unXvbEcUgaQAucsKCcm8W/9aebebd28a45aea02949470c429fe4db/busca-templates-central-mensagens_en.png)
+![busca-templates-central-mensagens en](//images.ctfassets.net/alneenqid6w5/6unXvbEcUgaQAucsKCcm8W/9aebebd28a45aea02949470c429fe4db/busca-templates-central-mensagens_en.png)
 
 After understanding the basic about the templates, you can see how to edit them. This step is not mandatory, since VTEX provides a basic and responsive layout for all messages, with information needed to communicate properly with your customer, but it is natural that the stores adapt the brand communication standard they already use.
 
diff --git a/docs/tutorials/en/understanding-the-price-change-rule.md b/docs/tutorials/en/understanding-the-price-change-rule.md
index 16fd19339..a824a5ee2 100644
--- a/docs/tutorials/en/understanding-the-price-change-rule.md
+++ b/docs/tutorials/en/understanding-the-price-change-rule.md
@@ -26,6 +26,6 @@ All other options to update prices will also be blocked.
 
 The price limits percentages can be removed or redefined by accessing the __Settings__ tab on the __Prices__ module. 
 
-![trava-variação-preço en](https://images.ctfassets.net/alneenqid6w5/7q0Dp7AIQokuGIGcIKOmqm/e1798e4757cba658c2dd5b5bde1a69bf/trava-varia____o-pre__o_en.png)
+![trava-variação-preço en](//images.ctfassets.net/alneenqid6w5/7q0Dp7AIQokuGIGcIKOmqm/e1798e4757cba658c2dd5b5bde1a69bf/trava-varia____o-pre__o_en.png)
 
 Some marketplaces also have this price variation limit. If you wish to change prices beyond the limit ranges, contact the marketplace asking for the change.
diff --git a/docs/tutorials/en/understanding-the-security-report.md b/docs/tutorials/en/understanding-the-security-report.md
index 900e214c5..a7246e018 100644
--- a/docs/tutorials/en/understanding-the-security-report.md
+++ b/docs/tutorials/en/understanding-the-security-report.md
@@ -31,7 +31,7 @@ Several filters are available, beginning with the fields below, bearing in mind
 
 In the example, I set up a filter for a change (whether creation or updating) to the price of an SKU. To do this I have used the fields __Data__ with the SKU Id, __Screen__, with the location of the platform where the change is happening and a specific time frame. According to the report you want, you may have to use other fields at the same time, or as a replacement for those I have used in the example.
 
-![relatorioseguran aPT.gif?h=250](https://images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/ef82dec5acc0f07090f01d3484407e75/relatorio-seguranca-en.gif)
+![relatorioseguran aPT.gif?h=250](//images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/ef82dec5acc0f07090f01d3484407e75/relatorio-seguranca-en.gif)
 
 Read the section below to understand all the available fields for filtering the report.
 
diff --git a/docs/tutorials/en/understanding-the-topbar.md b/docs/tutorials/en/understanding-the-topbar.md
index 195c8d4da..725282789 100644
--- a/docs/tutorials/en/understanding-the-topbar.md
+++ b/docs/tutorials/en/understanding-the-topbar.md
@@ -19,18 +19,18 @@ The sidebar is the starting point for all admin areas. See below the details reg
 
 **Browse the modules**: to do so, just click on the desired module in the Admin sidebar with all available module.
 
-![paginainicial.en](https://images.ctfassets.net/alneenqid6w5/68DVYFXEFfShDhVJLoP90E/ab49f60e0a7fccda830f4f7cfccdc32b/paginainicial.en.png)
+![paginainicial.en](//images.ctfassets.net/alneenqid6w5/68DVYFXEFfShDhVJLoP90E/ab49f60e0a7fccda830f4f7cfccdc32b/paginainicial.en.png)
 
 **Browse the sub-domains:** To browse the sub-domains of your store, just click on the current domain. You will view all options. To go to the admin of a sub-domain, just click on it on the menu.
-![subdominios.en](https://images.ctfassets.net/alneenqid6w5/14NnbogRz9imPMypMsSFSF/6c19b199374901b350a95eedf7094372/subdominios.en.png)
+![subdominios.en](//images.ctfassets.net/alneenqid6w5/14NnbogRz9imPMypMsSFSF/6c19b199374901b350a95eedf7094372/subdominios.en.png)
 
 **Select the admin language:** to select a language, just click on the language icon and select a language.
-![idioma.en](https://images.ctfassets.net/alneenqid6w5/3wBMDVQVe1C1lILiOFPSG8/ec5ff60fd97703e88e229190f8d65d17/idioma.en.png)
+![idioma.en](//images.ctfassets.net/alneenqid6w5/3wBMDVQVe1C1lILiOFPSG8/ec5ff60fd97703e88e229190f8d65d17/idioma.en.png)
 
 
 **Access new knowledge bases: **to access one of our bases, click on your support profile and select the site you intend to access just clicking on it.
 
-![support.en](https://images.ctfassets.net/alneenqid6w5/4SvEqHGVINK4P0gwGaZlXB/139f810e98f3f1ef0ca45d767d1e4aab/support.en.png)
+![support.en](//images.ctfassets.net/alneenqid6w5/4SvEqHGVINK4P0gwGaZlXB/139f810e98f3f1ef0ca45d767d1e4aab/support.en.png)
 
 
 **Logging off: **to log off, click on your name and then on the link **Sair.**
diff --git a/docs/tutorials/en/understanding-the-updating-of-the-xml.md b/docs/tutorials/en/understanding-the-updating-of-the-xml.md
index da7cdb86a..163c2debf 100644
--- a/docs/tutorials/en/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/en/understanding-the-updating-of-the-xml.md
@@ -3,8 +3,8 @@ title: 'Understanding the updating of the XML'
 id: tutorials_297
 status: PUBLISHED
 createdAt: 2017-04-27T22:09:31.811Z
-updatedAt: 2019-12-31T15:28:59.361Z
-publishedAt: 2019-12-31T15:28:59.361Z
+updatedAt: 2024-02-29T14:57:59.233Z
+publishedAt: 2024-02-29T14:57:59.233Z
 firstPublishedAt: 2017-04-27T23:03:14.354Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,4 +23,4 @@ You can view the date of the latest XML update. This information is shown in UTC
 
 [![xml](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
 
-<div class="alert alert-info">If the option “Exibir SKUs sem saldo disponível (esgotados) em Estoque entre os resultados” is not checked, out-of-stock products/SKUs will NOT be shown in the XML. Inactive products also do <strong>not</strong> appear in the XML.</div>
+<div class="alert alert-info">If the option “Display SKUs without available stock (out of stock) in Inventory among the results” is not checked, out-of-stock products/SKUs will NOT be shown in the XML. Inactive products also do <strong>not</strong> appear in the XML.</div>
diff --git a/docs/tutorials/en/understanding-vtexs-email-capture-system.md b/docs/tutorials/en/understanding-vtexs-email-capture-system.md
index a6b1d003a..561d186f0 100644
--- a/docs/tutorials/en/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/en/understanding-vtexs-email-capture-system.md
@@ -3,8 +3,8 @@ title: 'Email capture'
 id: 15oNhcDa7HA8ztfJnpvhmJ
 status: PUBLISHED
 createdAt: 2022-10-17T19:51:45.533Z
-updatedAt: 2022-10-17T19:55:21.831Z
-publishedAt: 2022-10-17T19:55:21.831Z
+updatedAt: 2023-07-20T17:49:29.730Z
+publishedAt: 2023-07-20T17:49:29.730Z
 firstPublishedAt: 2022-10-17T19:53:55.523Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: understanding-vtexs-email-capture-system
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
-The purpose of this article is to show how a user's email is received in the [Master Data CRM](https://help.vtex.com/en/subcategory/visao-geral-do-master-data--5gtjaqCG7eIseyCI0aSqc2#). For this, it will be demonstrated how **Checkout**, **RC.JS** and **Master Data** work together to capture the email information of a new user.
+The purpose of this article is to show how a user's email is received in the [Master Data CRM](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). For this, it will be demonstrated how **Checkout**, **RC.JS** and **Master Data** work together to capture the email information of a new user.
 
 For better understanding, we will present a scenario (divided into 3 steps), where the user successfully completes his purchase and the order is forwarded to OMS, while his email is transmitted securely to Master Data. In this context, user actions and platform flow occur in the following order:
 
@@ -51,5 +51,5 @@ So that the <a href="https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandon
 Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
 </div>
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/tutorials/en/untitled-entry-2024-03-13-at-16-25-15.md b/docs/tutorials/en/untitled-entry-2024-03-13-at-16-25-15.md
new file mode 100644
index 000000000..143e6bb88
--- /dev/null
+++ b/docs/tutorials/en/untitled-entry-2024-03-13-at-16-25-15.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 4GN2eQe58qKvEaLA4u7Cl8
+status: DRAFT
+createdAt: 2024-03-13T16:25:15.804Z
+updatedAt: 2024-03-13T16:25:21.748Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: 
+author: 
+slug: untitled-entry-2024-03-13-at-16-25-15
+locale: en
+legacySlug: untitled-entry-2024-03-13-at-16-25-15
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/en/untitled-entry-2024-07-25-at-21-25-31.md b/docs/tutorials/en/untitled-entry-2024-07-25-at-21-25-31.md
new file mode 100644
index 000000000..2b0d9d606
--- /dev/null
+++ b/docs/tutorials/en/untitled-entry-2024-07-25-at-21-25-31.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 3eu2vU8e9uMF7eNHJMHcYU
+status: DRAFT
+createdAt: 2024-07-25T21:25:31.372Z
+updatedAt: 2024-07-25T21:25:33.666Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: 
+author: 
+slug: untitled-entry-2024-07-25-at-21-25-31
+locale: en
+legacySlug: untitled-entry-2024-07-25-at-21-25-31
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md b/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md
index e5e25a74c..9f96d7fb9 100644
--- a/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md
+++ b/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md
@@ -45,7 +45,7 @@ _Available units = updated quantity of units - reserved units_
 
 Negative stock usually occurs when an SKU corresponding to an order that already has a reservation is removed from inventory. To avoid this situation, it is important that the SKU quantity update takes place  once the [status of the orders](https://help.vtex.com/en/tutorial/order-flow-on-the-oms--tutorials_196) has changed from `Preparing for delivery`. At this point, the platform has already [acknowledged the reservation](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#acknowledged-reservation), and it won't interpret the SKU quantity update as a reduction in the quantity of units of a product that hasn't been sold yet.
 
-![Inventory management](https://images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/d591d4682810d9f6549772a0e03f7f32/Inventory_management.gif)
+![Inventory management](//images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/d591d4682810d9f6549772a0e03f7f32/Inventory_management.gif)
 
 ## Related articles
 
diff --git a/docs/tutorials/en/using-recaptcha-at-checkout.md b/docs/tutorials/en/using-recaptcha-at-checkout.md
index 79b3496ca..559226624 100644
--- a/docs/tutorials/en/using-recaptcha-at-checkout.md
+++ b/docs/tutorials/en/using-recaptcha-at-checkout.md
@@ -3,8 +3,8 @@ title: 'Using reCAPTCHA at Checkout'
 id: 18Te3oDd7f4qcjKu9jhNzP
 status: PUBLISHED
 createdAt: 2021-08-03T12:53:12.155Z
-updatedAt: 2023-03-21T17:52:28.440Z
-publishedAt: 2023-03-21T17:52:28.440Z
+updatedAt: 2023-12-11T22:07:06.233Z
+publishedAt: 2023-12-11T22:07:06.233Z
 firstPublishedAt: 2021-08-03T13:51:19.441Z
 contentType: tutorial
 productTeam: Others
@@ -16,17 +16,17 @@ subcategory: 3shmvletqbB206RqbY2vYQ
 ---
 
 
-ReCAPTCHA is a solution for user validation on orders that will be paid by credit or debit card. It anticipates the use of malware for fraudulent purposes, preventing access by fake users. 
+reCAPTCHA is a solution for user validation on orders that will be paid by credit or debit card. It anticipates the use of malware for fraudulent purposes, preventing access by fake users. 
 
-To enhance security, VTEX provides [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) checkbox and recommends that customers enable it to protect order placement and payments. This version of reCAPTCHA is optimized. The user only has to select the checkbox, and will only be presented with the validation challenge if Google suspects them.
+We recommend enabling it to protect the creation and payment of orders in your store.
 
-ReCAPTCHA will be required according to the option set for the store via the [checkout configuration API.](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) For more information, read our article on [using reCAPTCHA for integrations.](https://developers.vtex.com/vtex-rest-api/docs/recaptcha)
+reCAPTCHA will be required according to the option set for the store via the [checkout configuration API.](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) For more information, read our article on [using reCAPTCHA for integrations.](https://developers.vtex.com/vtex-rest-api/docs/recaptcha)
 
 Before enabling it, please pay attention to:
 
 * **Interface adaptation:** when enabling the feature, you must adapt your store’s order creation interface (desktop and mobile). Otherwise, order creation will be affected. Learn more about how to adapt the interface in [reCAPTCHA's integration guide.](https://developers.vtex.com/vtex-rest-api/docs/recaptcha)
 * **Consequences for the account:** enabling the feature implies that it will be used in the entire account, including all stores and sub-accounts.
-* **Performing tests:** you must have a [Beta environment](https://help.vtex.com/en/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) and use [Checkout V6](https://help.vtex.com/en/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH) to test the feature.
+* **Performing tests:** you must use the [Beta environment](https://help.vtex.com/en/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) with [Checkout V6](https://help.vtex.com/en/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH) to test the feature without impacting your store in production.
 
 ## Application rule
 
@@ -36,19 +36,50 @@ VTEX recommends the [VTEX criteria](https://developers.vtex.com/docs/api-referen
 
 It is focused on user experience and aims to minimize the volume of use, while still providing the appropriate protection.  Sessions that are deemed trusted are exempt from reCAPTCHA. It is only enabled for potentially malicious sessions.
 
-## Shopping experience with VTEX Criteria
+## reCAPTCHA versions
+
+VTEX is integrated with reCAPTCHA enterprise, which offers two validation approaches: checkbox (equivalent to [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display)) and score-based (equivalent to [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3)). Check the table below to see which version applies to your operation.
+
+| **Store details**           | **reCAPTCHA version** |
+|-----------------------------|-----------------------|
+| Native VTEX storefront      | Checkbox (v2)                    |
+| Own storefront - web        | Checkbox (v2) or Score-based (v3)              |
+| Own storefront - mobile app | Score-based (v3)                    |
+
+## reCAPTCHA v2
+
+You can use reCAPTCHA checkbox (v2). So, when applicable, the user should click the <i class="far fa-check-square"></i> _(checkbox),_ and the validation challenge will only be displayed if Google suspects the user. See below for more details on the shopping experience.
+
+### Shopping experience with VTEX Criteria and reCAPTCHA v2
 
 The shopping experience with debit or credit cards tends to follow the flow below. It minimizes the occurrence of some types of fraud and attacks with minimal friction for the user.
-![reCAPTCHA scenariosEN](https://images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/21964354890c244b42bc479983335b9d/reCAPTCHA_scenarios__1_.jpg)
+![reCAPTCHA scenariosEN](//images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/21964354890c244b42bc479983335b9d/reCAPTCHA_scenarios__1_.jpg)
 As shown in the image above, there are different possible results in this flow:
 
 1. If the VTEX Criteria algorithm does not consider the session suspicious, the platform proceeds normally with the purchase.
 
 2. If the session is considered suspicious, the interface will display the reCAPTCHA Checkbox for the customer to select it. If reCAPTCHA does not consider the behavior suspicious when the Checkbox is selected, the purchase proceeds normally.
-![newCaptchaAnchor](https://images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/10ed6d11b50a947a6186b549e27c4723/newCaptchaAnchor.gif)
+![newCaptchaAnchor](//images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/10ed6d11b50a947a6186b549e27c4723/newCaptchaAnchor.gif)
 
 3. If reCAPTCHA considers the behavior suspicious, the interface will display the challenge.
-![desafio recaptcha](https://images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/3156077db9ee243bea20308c304d183c/desafio_recaptcha.png)
+![desafio recaptcha](//images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/3156077db9ee243bea20308c304d183c/desafio_recaptcha.png)
 
 4. If the challenge is successfully solved, the platform proceeds with the purchase. Otherwise, the behavior is considered compatible with that of a bot and the platform does not conclude the purchase.
 
+## reCAPTCHA v3
+
+Score-based reCAPTCHA ([v3](https://developers.google.com/recaptcha/docs/v3)) does not interrupt the user experience in your store. It checks the interactions on the site and returns a score between `1.0` (most likely a regular interaction) and `0.0` (most likely a bot).
+
+When configuring score-based reCAPTCHA for your VTEX store, you have the option to set a minimum score for [each added key](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#getting-the-recaptcha-key-for-mobile-implementations) and a [minimum score for your store](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#recaptcha-v3-score). Possible values are `0.1`, `0.3`, `0.7`, and `0.9`.
+
+The priority for applying the minimum score for a given order is:
+
+```
+Key score > Account score > VTEX default score (0.7)
+```
+
+If you set a minimum score for your key and your account, the key score will be applied. However, if you do not set any score, VTEX will apply the default value of `0.7`.
+
+Interactions that return a value less than the applicable minimum will not be able to make a purchase.
+
+To configure reCAPTCHA and set minimum scores for keys or accounts, please contact your development team and see the [Integration with reCAPTCHA guide](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
diff --git a/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 1f84fe31d..350c2af95 100644
--- a/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -41,7 +41,7 @@ Apps that have a session dependency monitor changes to their inputs and modify s
 
 Transforms often trigger other transforms, repeating until no further parameter updates are sent by apps. This operation is, naturally, carefully monitored for loop conditions. The diagram below illustrates one such transform cycle:
 
-![EN - Session Manager](https://images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
+![EN - Session Manager](//images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
 
 1. A change was made to session parameter X
 2. App A was monitoring session parameter X, so that triggered Transform 1
diff --git a/docs/tutorials/en/using-the-project-task-timeline.md b/docs/tutorials/en/using-the-project-task-timeline.md
index ab29b953b..b30da0518 100644
--- a/docs/tutorials/en/using-the-project-task-timeline.md
+++ b/docs/tutorials/en/using-the-project-task-timeline.md
@@ -1,10 +1,10 @@
 ---
 title: 'Using the project task timeline'
 id: tutorials_1864
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:55:58.397Z
-updatedAt: 2019-12-31T15:21:08.316Z
-publishedAt: 2019-12-31T15:21:08.316Z
+updatedAt: 2024-03-11T13:20:50.510Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:51.067Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/validating-your-store-and-uploading-it-for-production.md b/docs/tutorials/en/validating-your-store-and-uploading-it-for-production.md
index 07cbf78e6..0f2c4ea58 100644
--- a/docs/tutorials/en/validating-your-store-and-uploading-it-for-production.md
+++ b/docs/tutorials/en/validating-your-store-and-uploading-it-for-production.md
@@ -1,10 +1,10 @@
 ---
 title: 'Validating the store to move it to production'
 id: tutorials_1419
-status: CHANGED
+status: DRAFT
 createdAt: 2017-04-27T21:56:14.582Z
-updatedAt: 2022-06-01T20:06:41.976Z
-publishedAt: 2019-12-31T15:29:01.968Z
+updatedAt: 2023-07-25T21:07:26.780Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:49.725Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/en/via-inventory-integration-errors.md b/docs/tutorials/en/via-inventory-integration-errors.md
index 68ca95110..7782693d6 100644
--- a/docs/tutorials/en/via-inventory-integration-errors.md
+++ b/docs/tutorials/en/via-inventory-integration-errors.md
@@ -3,8 +3,8 @@ title: 'Via inventory integration errors'
 id: 2jzz4Ip0M2BDzwslEtCzPc
 status: PUBLISHED
 createdAt: 2021-10-26T23:55:47.528Z
-updatedAt: 2023-03-29T14:41:26.271Z
-publishedAt: 2023-03-29T14:41:26.271Z
+updatedAt: 2023-11-30T21:50:54.362Z
+publishedAt: 2023-11-30T21:50:54.362Z
 firstPublishedAt: 2021-10-27T00:08:05.224Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md b/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md
index a1ccd8930..58e2810db 100644
--- a/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md
+++ b/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md
@@ -17,7 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 *User settings* is the name of a set of configurations applied to your personal profile in the Admin. It is not related to your store or your VTEX business account. To access this page, click on your __profile avatar__, which can be identified by the first letter of your email address, and click on __User Settings__.
 
-![Admin v4 User settings menu EN](https://images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/3c37c9c64a2ff1832734671556b359b9/Admin_v4_User_settings_menu_EN.jpg)
+![Admin v4 User settings menu EN](//images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/3c37c9c64a2ff1832734671556b359b9/Admin_v4_User_settings_menu_EN.jpg)
 
 On this page, soon to be included in Admin v4, you can perform the following actions:
 
diff --git a/docs/tutorials/en/vtex-ad-network-beta.md b/docs/tutorials/en/vtex-ad-network-beta.md
new file mode 100644
index 000000000..19b1d8af1
--- /dev/null
+++ b/docs/tutorials/en/vtex-ad-network-beta.md
@@ -0,0 +1,123 @@
+---
+title: 'VTEX Ad Network (Beta)'
+id: 2cgqXcBuJmXN2livQvClur
+status: CHANGED
+createdAt: 2024-04-23T17:38:07.378Z
+updatedAt: 2024-07-05T13:14:45.135Z
+publishedAt: 2024-07-05T13:13:03.955Z
+firstPublishedAt: 2024-04-23T19:11:42.313Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: vtex-ad-network-beta
+locale: en
+legacySlug: vtex-ad-network-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>VTEX Ad Network is in beta, which means that we are working to improve it. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
+</div>
+
+**VTEX Ad Network** connects VTEX stores with brands interested in advertising their products. This connection allows advertisers and merchants to boost their business:
+
+- **Advertisers:** Brands that can create ad campaigns to promote products in VTEX stores offering the same products in their catalogs, thus increasing sales.
+- **Merchants:** Can offer ad space in their stores for advertisers to promote products. In return, these merchants will receive a fee for each click on an ad in their stores.
+
+## Campaigns
+
+A **VTEX Ad Network** campaign is based on the following characteristics:
+
+- Promoted products.
+- Total budget.
+- Bid, which is the cost per click (CPC) — the amount the advertiser is willing to pay for each click on the ad. This amount also determines the [priority of different ads](#ad-priority) for the same ad space and is defined per product.
+- Duration.
+- Coverage, which determines whether the campaign will run in the Ad Network or specific stores.
+
+When creating a campaign, the advertiser defines one or more EAN codes (barcodes) associated with the products they want to promote. VTEX can display these ads in all the stores that sell that product and have joined **VTEX Ad Network**, or advertisers can choose specific stores for their campaigns.
+
+## Ad format
+
+VTEX currently offers a single ad format: sponsored products. This means that products promoted by advertisers can be highlighted in some contexts where products are listed:
+
+- Search results.
+- Category pages.
+
+Below, there's an example of how sponsored products are displayed:
+
+![vtex_ad_network_sponsored_EN](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/1abdea32c119ed4890e414ad7dbc8fea/vtex_ad_network_sponsored.png)
+
+Stores participating in **VTEX Ad Network** will be able to [configure the amount of ad space](https://help.vtex.com/en/tutorial/advertising-with-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse#creating-campaigns) available in each store context.
+
+## Ad priority
+
+Every time a customer browses a store with available ad space, **VTEX Ad Network** determines which ads will be displayed.
+
+This prioritization process consists of three stages:
+
+#### 1. Selection
+
+- **VTEX Ad Network** considers customer behavior, such as search terms, categories, or window displays, and selects campaigns with products that fit this context. The platform even considers a minimum relevance score to ensure that only ads that might interest the customer are displayed.
+- At this stage, VTEX also considers compatibility from the point of view of [campaign settings](#campaigns), such as coverage and negative keywords.
+
+#### 2. Budget pacing
+
+- At this stage, VTEX weighs up the budget for campaigns, excluding the ones with no available budget and optimizing expenditure based on the likelihood of clicks and conversions.
+
+#### 3. Auction
+
+- **VTEX Ad Network** determines the best-promoted products to fill the available spaces from the candidates selected in the previous stages.
+- The platform classifies the ads based on their bid (CPC) and [quality score](#quality-score).
+- There is also a random factor in the auction calculation to avoid biases. Therefore, the higher the CPC value x quality score, the more likely an ad will be ranked higher, but there is no guarantee that it will always be the case.
+
+The bid amount is set once the ads displayed on the page have been defined. The winning bid will be the final amount of the second-highest bid plus $0.01 USD.
+
+<div class="alert alert-warning">
+Ads may not be selected through the prioritization process if the promoted products do not fit the customer behavior, store coverage, or available budget.</div>
+
+### Quality score
+
+The ad quality score is a measure that considers different evaluation criteria and influences the auction stage of the [Ad priority](#ad-priority) process. The higher the quality score, the more likely a particular ad will rank well in the auction.
+
+### Priorization example
+
+Consider the following ads from different campaigns competing in the same store.
+
+| **Ad** | **Product** | **Quality Score** | **Bid** | **Budget** |
+| :---: | :---: | :---: | :---: | :---: |
+| 1 | Perfume A | 10% | $1.00 USD | $0 USD |
+| 2 | Perfume B | 1% | $2.00 USD | $10 USD |
+| 3 | Perfume C | 10% | $0.90 USD | $10 USD |
+| 4 | Shampoo A | 5% | $0.50 USD | $10 USD |
+
+If a store customer accesses the **Perfumes** category page with 300 products, the prioritization process would go as follows:
+
+1. At the targeting stage, the platform discards ad 4, which doesn't fit the customer behavior.
+2. After assessing the pacing, the platform discards ad 1, as it has no available budget.
+3. In the auction, product 3 has a greater chance of being ranked first, considering its **bid** and **conversion rate**.
+
+## Attribution window
+
+**VTEX Ad Network's** attribution window is 15 days. If a customer clicks a product ad and buys that product within 15 days of clicking it, VTEX Ad Network attributes this sale to the ad.
+
+However, if the customer buys after this period, the sale will not be allocated to the ad.
+
+## How to join VTEX Ad Network
+
+See below how you can join **VTEX Ad Network** as a [merchant](#merchants) that displays ads or an [advertiser](#advertisers).
+
+### Merchants
+
+<div class="alert alert-warning">
+Currently, only stores developed with <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> can offer ad space.
+</div>
+
+To make ad space available in your store, you need to contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) to request the installation of the __VTEX Ad Network app for merchants__ in your VTEX account.
+
+Learn more about the functionalities for merchants in the [Displaying VTEX Ad Network ads in your store (Beta)](https://help.vtex.com/en/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA) article.
+
+### Advertisers
+
+Any brand interested in promoting products already sold in VTEX stores can advertise using **VTEX Ad Network**. To do this, you need to contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) to request that the __VTEX Ad Network__ app be installed on your VTEX account.
+
+Learn more about the features available to advertisers in the [Advertising with VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/advertising-with-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse) article.
diff --git a/docs/tutorials/en/vtex-admin-start-here.md b/docs/tutorials/en/vtex-admin-start-here.md
index 0706b861d..ed03e3000 100644
--- a/docs/tutorials/en/vtex-admin-start-here.md
+++ b/docs/tutorials/en/vtex-admin-start-here.md
@@ -3,8 +3,8 @@ title: 'VTEX Admin: Start Here'
 id: 531cHtUCUi3puRXNDmKziw
 status: PUBLISHED
 createdAt: 2019-02-04T15:41:26.380Z
-updatedAt: 2023-05-24T18:06:55.015Z
-publishedAt: 2023-05-24T18:06:55.015Z
+updatedAt: 2024-07-03T11:18:48.914Z
+publishedAt: 2024-07-03T11:18:48.914Z
 firstPublishedAt: 2019-02-04T15:51:04.667Z
 contentType: tutorial
 productTeam: Others
@@ -12,23 +12,31 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: vtex-admin-start-here
 locale: en
 legacySlug: find-here-all-the-answers-you-need
-subcategory: 
+subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 ---
 
 VTEX Admin allows merchants to manage their entire digital commerce experience in one place, in a simple and smart way. This is where they track orders, add products, set up fulfillment, and all the other aspects of a unified commerce operation.
 
 ## Homepage
-![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
 The homepage provides a high-level overview of your store, like a cockpit for your digital commerce operations, and for this reason it’s called  [Overview](https://help.vtex.com/en/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
 As soon as you log in to the Admin, you will see useful metrics and charts to monitor your store's performance, such as revenue and number of orders, sales funnel and conversion rate, and the 10 highest grossing products.
 
 ## Navigation menu
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 Our side navigation menu and top bar group similar categories together to reduce distractions and help your team find what they need faster. You can also use the search bar to find specific sections in the side menu.
 
+![admin navigation menu SEP2023](//images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/2569ef82429dd4bab5131004749acf22/admin-navigation.png)
+
+You can use the global search bar on the topbar to search for VTEX Admin pages or orders from your store. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
+
+- Order ID
+- Customer name
+- Customer email
+- Customer document
+
 Check out our articles for an overview of each menu in your VTEX Admin to learn more about their features and the pages included in each section:
 
 - [Dashboards](https://help.vtex.com/en/v4/docs/visao-geral-dashboards--3FA56jDSTQjuSDwJRYQihm)   
@@ -39,7 +47,7 @@ Check out our articles for an overview of each menu in your VTEX Admin to learn
 - [Shipping](https://help.vtex.com/en/v4/docs/visao-geral-envio--1hw1otLpTkIjQh4WiBTFYv)  
 - [Marketplace](https://help.vtex.com/en/v4/docs/visao-geral-marketplace--1MwABSIGjYSrFPUXhnUXiV)  
 - [Apps](https://help.vtex.com/en/v4/docs/apps-overview--Abz99oney4PUmrf7QcHc9)  
-- [Store Settings](https://help.vtex.comenpt/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4)  
+- [Store Settings](https://help.vtex.com/en/tutorial/visao-geral-configuracoes-da-loja--6VtlMoid6iM9dP14X1CopT)  
 - [Account Settings](https://help.vtex.com/en/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r)  
 - [User Settings](https://help.vtex.com/en/v4/docs/visao-geral-configuracoes-usuario--1qYAvOTZBVYMosJ7tQm3Ry)  
 - [Billing](https://help.vtex.com/en/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC)  
@@ -49,12 +57,47 @@ You can also use the search bar at the top of the VTEX Admin to find specific pa
 </div>
 
 ### Information Center
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+
+![information center admin SEP2023](//images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/3fe0b6fb2ef2ec7a54d546217515052c/Information_center.gif)
 
 This is where you can find all the useful links regarding the VTEX ecosystem to help you make the most of our platform. By clicking the <i class='fa fa-question-circle-o'></i> button on the top bar, you can access [Help Center](https://help.vtex.com), [Developer Portal](https://developers.vtex.com/), [Plataform Status](https://status.vtex.com/), [blog](https://vtex.com/en/blog/) and support pages.
 
+### Giving feedback through the VTEX Admin
+The Give Feedback button allows users to send feedback about their experience on the platform through the VTEX Admin. To access it, follow the steps below:
+1. Click the Information Center icon in the top right corner of the VTEX Admin.
+2. Click the **Give Feedback option**.
+
+You will be directed to a Google form where you can give your feedback. After submitting it, you will receive a confirmation email.
+
+![Botão feedback - EN](//images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/90f7b35d3923b55047dfa200c2a1e7e1/Bot_o_feedback_-_EN.gif)
+
+#### Feedback form
+The main purpose of the feedback form questions is to collect detailed information about experiences and insights about the product in the VTEX Admin.
+This information helps us to direct our development and support efforts to better meet user needs.
+
+##### Description of form fields
+- **Email:** Enter your email.
+- **Admin page URL:** Enter the page URL for which you want to give feedback.
+
+Feedback type (select one or more options):
+- **Overall experience:** Evaluates the overall experience with the product.
+- **Features:** Focuses on the product features.
+- **Interface & Usability:** Relates to the interface and usability.
+- **Translation:** Evaluates the content translation.
+- **Loading time:** Verifies loading time performance.
+- **Other:** Input field for adding another feedback type not previously covered.
+
+**Describe your feedback:** Enter details about the products and types of feedback selected in the previous sections of the form.
+
+**A screenshot will help us better understand your feedback (optional):** Optional field to add screenshots or documents that can help us understand your feedback in more detail.
+
+<div class = "alert alert-info">
+This feedback process should not be used to create a ticket or technical support request at VTEX.
+</div>
+
 ### User and Account Settings
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+
+![avatar settings admin SEP2023](//images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/ee5a09f9a303042e1e83bb6ffa4e7982/Avatar_settings2.gif)
 
 Your profile avatar is a central hub for all your user and account settings. By clicking it, you can access your [User settings](https://help.vtex.com/en/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Account settings](https://help.vtex.com/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), and [Billing](https://help.vtex.com/en/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC) information, as well as change the language of your Admin, and log out.
 
@@ -74,9 +117,7 @@ The VTEX Admin offers a localized experience in the following language options:
 
 ### Store Settings
 
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
-
-We have grouped the settings of all the Admin sections in one specific meni: [Store Settings](https://help.vtex.com/en/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). With this improvement, you can easily access all the settings that affect each service in your operation.
+We have grouped the settings of all the Admin sections in one specific menu: [Store Settings](https://help.vtex.com/en/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). With this improvement, you can easily access all the settings that affect each service in your operation.
 
 ## Performance and compatibility
 We recommend accessing the VTEX Admin on the latest versions of either Windows and Mac Operating Systems for optimal performance. The VTEX Admin supports all the most popular browsers, as listed below:
diff --git a/docs/tutorials/en/vtex-admin-start-here1.md b/docs/tutorials/en/vtex-admin-start-here1.md
index eee5e771d..4dcb7597b 100644
--- a/docs/tutorials/en/vtex-admin-start-here1.md
+++ b/docs/tutorials/en/vtex-admin-start-here1.md
@@ -18,30 +18,30 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 The Admin allows merchants to manage their entire digital commerce experience in one place, in a simple and smart way. 
 
 ## Homepage
-![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
 The Admin homepage has been redesigned to provide a high-level overview of your store, like a cockpit for your digital commerce operations, and is now called [Overview](https://help.vtex.com/en/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
 As soon as you log in to the Admin, you will see useful metrics and charts to monitor your store's performance, such as revenue and number of orders, sales funnel and conversion rate, and the 10 highest grossing products.
 
 ## Enhanced Navigation 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 Everything you need to manage your VTEX store is still available in the Admin, but now with a simpler interface. The side navigation menu and the top bar have been completely redesigned. Now, similar categories are grouped more clearly to reduce distractions and help your team find what they need faster. You can also use the search bar to find specific sections in the side menu.
 
 ### Information Center
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 This is where you can find all the useful links regarding the VTEX ecosystem to help you make the most of our platform. By clicking on the `?` button on the top bar, you can access the Help Center, Developer Portal, Platform Status, Blog, and support pages.
 
 ### Store Settings
 
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 For this experience, we have grouped the settings of all the Admin sections in one tab: [Store Settings](https://help.vtex.com/en/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Now, you can easily access all the settings that affect each service in your account.
 
 ### User and Account Settings
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 Your profile avatar, in the upper right corner, now displays all the settings related to your user and account. By clicking on your avatar, you can access your [User settings](https://help.vtex.com/en/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Account settings](https://help.vtex.com/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), and [Billing](https://help.vtex.com/en/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC) information, and you can also change the language of your Admin panel and logout. 
 
diff --git a/docs/tutorials/en/vtex-agreement.md b/docs/tutorials/en/vtex-agreement.md
new file mode 100644
index 000000000..219f06249
--- /dev/null
+++ b/docs/tutorials/en/vtex-agreement.md
@@ -0,0 +1,34 @@
+---
+title: 'VTEX Agreement'
+id: gjJL5j4zZuiC2qAuSuoG4
+status: PUBLISHED
+createdAt: 2019-01-24T20:45:47.050Z
+updatedAt: 2024-02-20T18:14:26.057Z
+publishedAt: 2024-02-20T18:14:26.057Z
+firstPublishedAt: 2019-01-24T22:07:46.230Z
+contentType: tutorial
+productTeam: Billing
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: vtex-agreement
+locale: en
+legacySlug: why-didnt-i-receive-the-signed-contract-from-vtex
+subcategory: 22TaEgFhwE6a6CG2KASYkC
+---
+
+The VTEX Agreement, or Commercial Agreement, consists of two parts: the [MSA (Master Service Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/) and the **Appendix 1 Order** Form for the provision of services to companies, or the [MPA (Master Partner Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) and the **specific Terms and Conditions tailored for the partnership**.
+
+![VTEX Agreement](//images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/0927a3945c933046bc6eae8ba1fd0ced/En.png)
+
+The [Master Service Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/) and the [Master Partner Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) are the main service and partnership agreements, respectively. They regulate the relationship between VTEX and its customers or partners. Both vary based on the region in which the company or partner is located.
+
+The **Appendix 1 Order Form** and the **partnership-specific Terms and Conditions** establish all the commercial conditions agreed upon for each company or partner under legal contract conditions.
+
+## Where can I find my agreement with VTEX?
+
+The Master Agreement applicable to you is available under **Privacy Policy > Privacy & Agreements > [Master Services Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements-archive/#:~:text=Master%20Agreements,September%2006%2C%202020%5D)** for clients and **Privacy Policy > Privacy & Agreements > [Partner Agreement](https://vtex.com/br-pt/privacy-and-agreements/agreements-archive/#:~:text=Contratos%20Anteriores,Partner%20Agreement)** for partners, depending on the region and the date on which **Appendix 1** or the **partnership-specific Terms and Conditions** were signed. **Appendix 1** and the **Terms and Conditions** signed with VTEX can be requested directly from the CS of your account via [VTEX Support](https://help.vtex.com/support?/cultureInfo=pt-br).
+
+You can also find the most updated Master Agreements — the ones applicable to new clients and partners — on the [VTEX Agreement](https://vtex.com/br-pt/privacy-and-agreements/agreements/) page.
+
+<div class="alert alert-info">
+  If the <b>MSA, MPA, Appendix 1,</b> or <b>partnership-specific Terms and Conditions</b> signed with VTEX contain any information different from the one described in this documentation, prioritize your document signed with VTEX.
+  </div>
diff --git a/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
new file mode 100644
index 000000000..6ce3ed4ac
--- /dev/null
+++ b/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
@@ -0,0 +1,201 @@
+---
+title: 'VTEX dashboard guide for Black Week: FAQ'
+id: 6O3CiGiZctVIgIrpIcko9h
+status: PUBLISHED
+createdAt: 2023-11-17T17:09:40.720Z
+updatedAt: 2023-11-21T16:06:22.017Z
+publishedAt: 2023-11-21T16:06:22.017Z
+firstPublishedAt: 2023-11-20T18:30:27.790Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: vtex-dashboard-guide-for-black-week-faq
+locale: en
+legacySlug: vtex-dashboard-guide-for-black-week-faq
+subcategory: 1TIJqw8kV2Yok4iQe4SAkq
+---
+
+This guide answers the most frequently asked questions about how to use the VTEX Admin dashboards during Black Week.  
+
+- [What's the best way to monitor my ecommerce website during Black Week in the VTEX Admin?](#whats-the-best-way-to-monitor-my-ecommerce-website-during-black-week-in-the-vte-admin)
+- [How can I track my ecommerce data beyond today?](#how-can-i-track-my-ecommerce-data-beyond-today)
+- [Why are my metrics different from the Orders page in the Admin?](#why-are-my-metrics-different-from-the-orders-page-in-the-admin)
+- [Why don't I have session or conversion rate data?](#why-dont-i-have-session-or-conversion-rate-data)
+- [Why don't my conversion rate, new sessions, or sales funnel metrics match the numbers from my internal tools?](#why-dont-my-conversion-rate-new-sessions-or-sales-funnel-metrics-match-the-numbers-from-my-internal-tools)
+- [Why is my revenue metric only showing in one currency when I operate with more than one?](#why-is-my-revenue-metric-only-showing-in-one-currency-when-i-operate-with-more-than-one)
+- [Why doesn’t the number of orders in the sales funnel analysis match the one in the Monitoring section?](#why-doesnt-the-number-of-orders-in-the-sales-funnel-analysis-match-the-one-in-the-monitoring-section)
+- [Why is the new Overview in a separate URL?](#why-is-the-new-overview-in-a-separate-url)
+
+## What's the best way to monitor my ecommerce website during Black Week in the VTEX Admin?  
+
+During Black Week, a period of intense sales activity and volatility, the ideal monitoring tool is the new **VTEX real-time Overview.** To access this page, go to **Dashboards > Overview** in the navigation menu or enter **Overview** in the bar at the top of the page.  
+
+Below are some tips to best leverage this feature:  
+
+Start by setting the desired time zone and selecting the store you want to monitor in the real-time Overview.    
+
+![timezone-en](//images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/3693d76ead0495c35a66f8c099d60f9c/timezone-en.png)  
+
+### Reference filter  
+
+The reference filter or **Compare today with** compares your current performance against a specific period.  
+
+To configure the reference filter, follow these steps:  
+
+1. Click `Compare today with`.  
+2. Select `Custom`.  
+3. Set a date.  
+4. Click `Apply`.  
+
+<div class="alert alert-warning">
+A useful comparison during Black Week is with the same date last year. In the reference filter, select a date between November 21, 2022 and November 27, 2022, ideally the same days of the week. <br>This option is available for clients who were already using the VTEX platform during that period last year.</br>
+</div>
+
+![reference-en](//images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/2d4ca5424f4c45e4e8104f37ca11186d/reference-en.png)
+
+### View filter  
+
+- **Track the day’s performance with the cumulative view:** Use the **cumulative view** to monitor the sales performance of your ecommerce website minute by minute. This will provide insights that will enable quick operation adjustments.  
+To select the **cumulative view** in the dashboard, click **View<i class="fas fa-angle-down"></i> > Accumulated.**  
+
+![accumulated-en](//images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/573168bd8086f888f6f98cddc84c0e6c/accumulated-en.png)
+
+- **Track performance in the last hours:** **The Last 2 hours view** shows the metrics isolated minute by minute, which is important for guaranteeing the operational stability of your store during the event.  
+To select **Last 2 hours** in the dashboard, click **View<i class="fas fa-angle-down"></i> > Last 2 hours.**  
+
+![hours-en](//images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/119053d48e6874dcfd5905473e754c17/hours-en.png)
+
+### Metrics  
+
+The real-time Overview provides important insights into your sales strategy. For instance, you can use the best-selling products as a reference to boost campaigns and further leverage your results.  
+
+To view the best-selling products, in the **Metrics** section click the <i class="fas fa-ellipsis-v"></i> button and select **Best-selling products.**  
+
+![best-selling-en](//images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/61ac987b15602d8dfd633019a448fa04/best-selling-en.png)
+
+<div class="alert alert-warning">
+For analyzing or monitoring longer periods, we recommend using our Sales Performance dashboard, which will be explained in the next question.
+  </div>
+
+## How can I track my ecommerce data beyond today?  
+
+The VTEX Sales Performance dashboard is the right tool for normal monitoring of your ecommerce operation. It offers a longer history with a refresh rate of 90 minutes. The points below explain how to leverage this dashboard.  
+
+### Filters  
+
+- **Date**  
+When you go to the dashboard, the first step is to set the date for **Main period** and **Compared with.** If you’re running an analysis after Black Week, select Last week to compare with last year's Black Week (available if you were a VTEX client at that time). During Black Week, select Custom date and set the specific days to analyze.  
+
+![sales-date-en](//images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/05805210036ffecd73251cc0d8581eb7/sales-date-en.png)  
+
+- **Combined filters**  
+The data displayed on the Sales Performance dashboard can be segmented using combined filters, such as category. To add a new filter, follow the steps below:  
+
+1. In the Sales Performance dashboard, click **Filters.**  
+2. Click <i class="fas fa-plus"></i> Add Filter.  
+3. Select the desired categories.  
+4. Click `Apply`.  
+
+You can explore other filters based on the needs and specific aspects of your ecommerce operation.  
+
+![add-filter-en](//images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/fa01df4adc0b1a05a20225da3ccb7bc8/add-filter-en.png)  
+
+### Metrics  
+
+You can customize the displayed metrics to analyze different things. Metrics can be edited by clicking the <i class="fas fa-ellipsis-v"></i> button next to the name.  
+During Black Week, this dashboard can be used to analyze the following performance metrics:  
+
+- Revenue (approved)
+- Orders (approved)
+- Orders (captured)
+- Average ticket (approved)
+- Orders (canceled)  
+
+![change-metric-en](//images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/c08adbff229f6ff0116568228b741bdf/change-metric-en.png)  
+
+- **Week’s performance**  
+After making adjustments, compare the current week's performance with last year's Black Week to identify trends and opportunities.  
+
+![week-performance-en](//images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/993675a67d0bb68327994f5250fa8d9d/week-performance-en.png)    
+
+- **Table analysis**  
+Analyze the breakdown table for deeper insights. For example, SKU analysis can reveal which products should be highlighted in future campaigns.  
+
+![table-analysis-en](//images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/c9a20889c76d79221b42972fd1c1dc5c/table-analysis-en.png)  
+
+- **Save your view**  
+Save your dashboard configuration for future queries. Click **Sales Management > <i class="fas fa-plus"></i>  > Add a name > `Create`** to save your custom view.  
+
+![create-view-en](//images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/aefb269aa88b6c50dcf98fa2a92ad197/create-view-en.png)    
+
+## Why are my metrics different from the Orders page in the Admin?  
+
+There are several reasons why metrics in the real-time Overview might differ from the Orders page in the Admin:  
+
+- Overview: The metrics displayed by the VTEX Admin dashboards only consider sales from one store at a time. Therefore, all the metrics refer to the store selected in the dashboard filter.  
+- Orders: The order metrics consider all sales completed during the selected period.  
+- Different refresh rates: The Overview page refreshes every 1 to 3 minutes. Therefore, a slight discrepancy (1 to 3% of the total) between the two pages is common.  
+- Revenue calculation formula: The metrics in Overview don’t consider discounts, shipping, surcharges, and promotions in the revenue calculation, while the Orders page does take these factors into account.  
+
+![change-store-en](//images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/1951bcca25915d306c0062c2d69ed361/change-store-en.png)
+
+To see the data from all stores, use the Sales Performance page, which shows aggregated data with an approximate refresh rate of 90 minutes.  
+
+<div class="alert alert-danger">
+  If your operation uses more than one currency, the <b>Overview dashboard</b> will sum your orders in the currency that is most used in your sales. <br>To make a comparison with the <b>Orders</b> page, you need to sum the order total from all your currencies.</br>
+  </div>
+
+![all-orders-en](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
+
+- **Time zone:** This filter is available in **Overview.** If you use a time zone that is different from the Orders page default (which is your current time zone), the metrics will not match. Adjust the time zone as needed.  
+
+![timezone-en](//images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/2a62c6b5c8883593286347b27a87fb6d/sales-timezone-en.png)  
+
+## Why don't I have session or conversion rate data?  
+
+The conversion rates, sessions, and sales funnel analyses in VTEX are based on data captured by our navigation base, which relies on a specific script executed within the online stores of the clients. This script is crucial for recording the necessary information for these analyses.  
+
+However, it’s important to note that our script does not capture data from sessions originating from marketplaces, apps, or headless implementations where we don't manage the frontend. Furthermore, custom modifications to the frontend of the store can interfere with or even deactivate our script. This means that, in some cases, these sessions and activities are not recorded, resulting in a lack of session or conversion rate data on your dashboard.  
+
+If you notice this data is missing, it may be due to these limitations. We recommend checking the script settings and any frontend customizations that might be affecting data capture.  
+
+![sales-overview-en](//images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/a3b342736ed0ba9f09c79eed98be6066/sales-overview-en.png)  
+
+## Why don't my conversion rate, new sessions, or sales funnel metrics match the numbers from my internal tools?  
+
+Other analytics tools, such as Google Analytics, are usually installed with customizations and higher priority and are thus able to capture a broader spectrum of data. This often results in discrepancies when compared to our numbers.  
+
+On the other hand, VTEX captures navigation data using its own script, which is executed within the online stores of clients. Because this script is loaded last on the page to minimize the impact on performance, very brief sessions may not be recorded.  
+
+It’s important to note that our script does not capture data from sessions originating from marketplaces, apps, or headless implementations. Furthermore, customizations made by the client to the frontend can interfere with or even deactivate our script, impacting data collection.  
+
+## Why is my revenue metric only showing in one currency when I operate with more than one?  
+
+VTEX displays the value in a single currency to simplify the renderization of the revenue graph in the monitoring section of the real-time Overview. This provides a clear and straightforward view of revenue without the added complexity of multiple currencies.  
+
+To determine which currency to display, we assess the most used currency in online store sales and convert all other amounts to that currency. This is done to offer a simpler and more direct understanding of sales performance.  
+
+As a result, if you operate with more than one currency, you need to sum the total orders from the Admin Orders page across all your currencies to match the order data shown in the real-time Overview.  
+
+![all-orders-en](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
+![monitoring-en](//images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/97d4da4d04313aec7d1cdd95de40378b/monitoring-en.png)  
+
+## Why doesn’t the number of orders in the sales funnel analysis match the Monitoring section?  
+
+To understand this discrepancy, it’s important to remember that the monitoring metrics in the real-time Overview are generated from our Order Management System (OMS). The OMS contains information about all different types of store orders, including marketplace, direct, and app sales.  
+
+On the other hand, the data from the sales funnel is collected from the site's navigation base, which exclusively captures sales data from within the client’s online store. This means that sales completed on marketplaces or in other stores that do not use the VTEX storefront are not included in the funnel.  
+
+As a result, it is common for the number of orders in the sales funnel to be lower than the Monitoring section, which provides a broader view of store sales, including channels outside the VTEX platform.  
+
+![conversation-rate-en](//images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/0e640c18f48f1d6576b2b366e5a26f34/conversation-rate-en.png)  
+![new-sessions-en](//images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/fd44b2bc0036ac47ea0421bcb74b36b8/new-sessions-en.png)  
+
+## Why is the new Overview in a separate URL?  
+
+VTEX chose to temporarily maintain the old Overview page while introducing the new real-time Overview. To ensure a smooth transition and uninterrupted access to the previous version, the new Overview is being hosted in a separate environment. This means that when accessing the new Overview, you may be prompted to log in to the VTEX Admin again.  
+
+It’s important to note that occasionally, you might encounter errors when trying to load the new Overview page. These errors are generally related to re-authentication in the system due to the separate environment where the new Overview is being hosted.  
+
+We are working towards integrating the new Overview back into the original VTEX Admin environment. Once this integration is complete, we plan to deprecate the old page to simplify the process and enhance the user experience. We appreciate your patience and understanding during this transition.  
+
diff --git a/docs/tutorials/en/vtex-do-interface.md b/docs/tutorials/en/vtex-do-interface.md
index 44d81bd38..1db8b2e6a 100644
--- a/docs/tutorials/en/vtex-do-interface.md
+++ b/docs/tutorials/en/vtex-do-interface.md
@@ -3,8 +3,8 @@ title: 'VTEX DO'
 id: 7KMbRL4OslN8DTX9oiuCiu
 status: PUBLISHED
 createdAt: 2022-04-04T21:12:30.592Z
-updatedAt: 2023-03-29T14:50:36.206Z
-publishedAt: 2023-03-29T14:50:36.206Z
+updatedAt: 2023-11-06T14:21:27.706Z
+publishedAt: 2023-11-06T14:21:27.706Z
 firstPublishedAt: 2022-04-04T21:58:08.236Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,10 +17,10 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 VTEX DO manages tasks automatically created by the VTEX Admin that require manual action by the ecommerce team. To access it, log in to your VTEX Admin, go to **Orders > [All orders](https://help.vtex.com/en/tutorial/lista-de-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**, and click on the inbox icon in the bottom right corner of the page. By clicking on the icon, a modal will display the list of tasks related to the store's orders. 
 
-![VTEX Do overview EN](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
+![VTEX Do overview EN](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
 
 <div class = "alert alert-info">
-Only users with the <a href = "https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> registered as a  <a href = "https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">role</a> can perform tasks through VTEX DO.
+Only users with the <a href = "https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> role can perform tasks through VTEX DO.
 </div>
 
 The tasks are listed in two tabs:
@@ -115,7 +115,7 @@ Tasks managed through VTEX DO can include messages from all VTEX systems. Some e
 
 ## Task details
 
-![VTEX Do details EN](https://images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/9bb5a8bb66f10645c751d11ae95b4ee0/VTEX_Do_details_EN.jpg)
+![VTEX Do details EN](//images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/9bb5a8bb66f10645c751d11ae95b4ee0/VTEX_Do_details_EN.jpg)
 
 By clicking on the name of a task in the list, you are redirected to the task details modal, which displays more information about the task and actions to solve it. The following fields are displayed:
 
diff --git a/docs/tutorials/en/vtex-insurance.md b/docs/tutorials/en/vtex-insurance.md
index 5827225ea..302c73d66 100644
--- a/docs/tutorials/en/vtex-insurance.md
+++ b/docs/tutorials/en/vtex-insurance.md
@@ -1,10 +1,10 @@
 ---
 title: 'VTEX Insurance'
 id: 2aF3SDIj5t2qGe3bWKCjLD
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-05-23T20:15:25.639Z
-updatedAt: 2023-05-26T18:43:28.958Z
-publishedAt: 2023-05-26T18:43:28.958Z
+updatedAt: 2024-01-11T20:01:57.317Z
+publishedAt: 
 firstPublishedAt: 2023-05-26T17:46:59.436Z
 contentType: tutorial
 productTeam: B2B
@@ -15,4 +15,113 @@ legacySlug: vtex-insurance
 subcategory: 
 ---
 
-<div class="alert alert-warning" role="alert">Content under translation.</div>
+**VTEX Insurance** is an app that enables merchants to bind store products to insurance offers provided by their insurance partner [Assurant](https://www.assurant.com.br/). This feature allows your store to provide customized insurance to customers, offering financial protection in case of failure or defect of the purchased product or service. You can provide your customers with an extra layer of security with an extended warranty.
+
+Once the payment is confirmed, your customer will receive an email from our support team with the purchased insurance document. This document is a receipt that confirms the purchased product is insured and contains all the information describing the insurance coverage, including instructions to contact the insurance company.
+
+Check out the table below to see the insurance types available in VTEX Insurance.
+
+Code   | Insurance Type
+--------- | ------
+EW | Extended Warranty
+TH | Theft and Qualified Theft
+RQ | Theft and Accidental Damage
+QA | Accidental Damage
+
+To configure VTEX Insurance in your store, you need to:
+
+1. <a href="#vtex-insurance-prerequisites">Install the VTEX Insurance app.</a>
+2. <a href="#setting-up-the-catalog">Set up the store catalog to cover the insurance plans.</a>
+3. <a href="#configuring-insurance">Configure Insurance.</a>
+
+## VTEX Insurance prerequisites
+To set up VTEX Insurance, follow the steps below.
+
+1. In the VTEX Admin, go to **Account Settings> Users** or type **Users** in the search bar at the top of the page.
+2. Click `New`.
+3. Enter the email of the store installing VTEX Insurance in the **Email** field. If the email is not accepted, click  ́Add Profiles ́. On this page, you will need to select an existing [profile](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) that has already been added as **Owner** or **Developer**.
+4.  Click `Save`.
+
+The registered email address will receive an email from our support team with access to the VTEX Insurance app.
+
+## Setting up the catalog
+After installing VTEX Insurance, you need to complete the Catalog setup to cover insurance plans and products. To configure it, follow the steps below.
+
+1. Add [Assurant as a seller in your store](https://help.vtex.com/en/tutorial/adding-a-seller--tutorials_392).
+
+2. [Create a collection](https://help.vtex.com/en/tutorial/creating-collections-beta--yJBHqNMViOAnnnq4fyOye) to group products for binding the insurance options. You need to create a specific collection for each insurance type, as the collection will be used to specify which insurance policy the products will belong to.
+
+3. [Create a category specification group](https://help.vtex.com/en/tutorial/creating-a-specification-group-in-a-category--tutorials_246) to add manufacturer warranties to your catalog, such as Warranty.
+
+4. [Create a product specification](https://help.vtex.com/en/tutorial/adding-specifications-or-product-fields--tutorials_106) with the insurance information you want to provide, such as Extended Warranty, for example.
+
+5. After creating the **Manufacturer warranty** field, set the desired warranty period. In the **Standard value** field, we recommend entering "12", representing 12 months.
+
+6. [Create a specific category](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1) for an insurance product.
+
+7. [Create an insurance product](https://help.vtex.com/en/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By).
+
+8. [Create insurance SKUs](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY). We recommend creating more than three SKUs for each insurance.![Insurance - SKUs](//images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/e1b53a46f844d679277074c59386b0de/image3.png)
+
+9. [Bind the created SKUs](https://help.vtex.com/en/tutorial/sku-bindings--1SmrVgNwjJX17hdqwLa0TX) to the Assurant seller.
+
+10. [Bind the insurance to the desired](https://help.vtex.com/en/tutorial/adding-specifications-or-product-fields--tutorials_106) product.
+
+<div class="alert alert-info" role="alert">
+<p> You need to repeat this process for all categories and products that offer insurance coverage. </p>
+</div>
+
+## Configuring Insurance
+After setting up the catalog, your store will have the products bound to insurance. In **Insurance** > **Configuration**, complete the VTEX Insurance setup.
+
+Follow the steps below to set up your VTEX Insurance app.
+
+### Company Information
+![Insurance Configuration](//images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/b779f15fc609605bb8c26452fa596251/image5.png)
+1. Complete the following information:
+- **Email**: Store email.
+- **Name**: Store name.
+- **Phone**: Store phone number.
+- **Mark-Up Value**: Profit margin to be achieved. Enter 0 (zero).
+- **Street Name**: The street your store or office is located.
+- **City**: The city your store or office is located.
+- **State**: The state your store or office is located.
+- **Postal Code**: Store or office postal code.
+- **Country**: The country of your store or office.
+2. Click `Submit`.
+
+### Items bound to insurance items
+
+![Items Bound to Source Items](//images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/3aa3ac21584d7226965e0584eb738150/image2.png)
+
+1. Select the codes that correspond to the insurance types you want for the collection you have created.
+
+2. Bind the SKUs created to insurance plans: you must add the insurance plan followed by the SKU ID. Example_: When binding the **Extended Warranty** insurance type (Code **EW**) to the SKU created for that same insurance type (ID **357**), the binding will be presented as **EW|357** (no spacing).
+If you want to bind more than one insurance plan, such as **Theft and Qualified Theft** (Code **TH**) with the created SKU (ID **358**), **TH|358** binding, the field should be completed as **EW|357, TH|358**.
+3. Click `Submit`.
+
+### Warranty field name
+
+![Warranty Field Name](//images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/c7440e8c3189d41c05d3a837cec3e273/image8.png)
+
+1.  Specify the manufacturer's warranty field, indicating the name of the warranty used in the catalog.
+
+2.  Click `Submit`.
+
+### Insurance attachment setup
+![Insurance Attachement Setup](//images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/0cc20efa1f556b1cd5ed82e97f456ced/insurance_attachement_setup.png)
+
+1. [Add an](https://help.vtex.com/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU) attachment for Assurant with the information received from the support team when contracting the service.
+
+2. In **Insurance > Configuration**, click `Add attachment` in the **Insurance** section **Attachment Setup**.
+
+3. On the **Attachment** page, click the `Change` button related to the **assurant.insurance** attachment. For each item in the table, click `Change` and delete all the values in the **Allowed values** field.
+
+4. Click `Save`.
+
+### Manual pricing setup
+![Manual Pricing](//images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/c35b802ce82a4b0ddb077c7d62cae53e/image11.png)
+
+1. [Activate the manual pricing](https://help.vtex.com/en/tutorial/change-the-price-of-an-item-in-the-shopping-cart--7Cd37aCAmtL1qmoZJJvjNf) in your store.
+
+2. Click `Done, next`.
diff --git a/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
index ce93657e0..1f669d450 100644
--- a/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -3,8 +3,8 @@ title: 'VTEX Intelligent Search: Multilanguage settings (Beta)'
 id: 2WahlTESLXIJ9XBdQMdTYO
 status: PUBLISHED
 createdAt: 2021-03-09T22:44:16.513Z
-updatedAt: 2023-03-30T17:45:54.079Z
-publishedAt: 2023-03-30T17:45:54.079Z
+updatedAt: 2023-07-26T19:15:24.855Z
+publishedAt: 2023-07-26T19:15:24.855Z
 firstPublishedAt: 2021-03-10T21:13:35.816Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,11 +27,7 @@ VTEX Intelligent Search: Multilanguage expands [Intelligent Search’s](https://
 <p> If you want to expand your ecommerce to another language, contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a> and the VTEX team will perform the necessary configurations.</p>
 </div>
 
-After installing VTEX Intelligent Search: Multilanguage, your Catalog’s information will be translated by the [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) app, provided that you have classified terms as translatable in the following fields: Name, Brand, Description, Categories, CategoryTrees, metadata, metadataKeyword, Specifications, SKU {name}.
-
-<div class="alert alert-warning">
-<p> If you do not add a translation for a term in Messages, an automatic service will translate it. For this reason, it is important <a href="https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization">to add translations for all fields</a> to avoid undesired effects, such as literal translations that do not reflect the language used in a particular region. For example, the product “whole milk” may be automatically translated into Brazilian Portuguese as “leite inteiro” instead of the correct term “leite integral”.</p>
-</div>
+After installing VTEX Intelligent Search: Multilanguage, your Catalog’s information will be translated by the [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) app, provided that you have added translations for the following fields: Name, Brand, Description, Categories, CategoryTrees, metadata, metadataKeyword, Specifications, SKU {name}. Read the developer guide on [Translating Catalog content](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) for more details.
 
 From the [Multi-Tenant API](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-multi-language-stores), VTEX Intelligent Search: Multilanguage obtains all locations and respective languages (examples: `pt-br`, `en-GB`) that were added to the store. Each location has its URL.
 
@@ -47,7 +43,7 @@ VTEX Intelligent Search: Multilanguage allows you to customize the search experi
 ### Merchandising rules
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Merchandising Rules — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Merchandising rules__ —  will contain the additional __Locales__ field, which allows you to choose the locales to which the Merchandising Rules will apply, as shown in the image below.
 
-![img regrasmerch intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/1ff4219f9c71ad2dfe0ed7b897268a94/01-merchrules-en.png)
+![img regrasmerch intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/1ff4219f9c71ad2dfe0ed7b897268a94/01-merchrules-en.png)
 
 To learn more about this field, read our article on [how to configure Merchandising rules in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8).
 
@@ -61,7 +57,7 @@ You can configure Synonyms for a multi-language store in the Admin by filling ou
 #### Creating Synonyms via form
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Synonyms (available through — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Synonyms__ —  will contain the additional __Locales__ field, which allows you to choose the locales to which the Synonyms will apply, as illustrated in the image below. Click on the languages you want to select.
 
-![img sinonimos intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/eea0dbf7bf687c0c952599a555ef35fd/image_3.png)
+![img sinonimos intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/eea0dbf7bf687c0c952599a555ef35fd/image_3.png)
 
 To learn more about this field, read our article on [how to configure Synonyms in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
@@ -85,7 +81,7 @@ To learn more about importing Synonyms spreadsheets, read our article on [how to
 
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Redirects — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Redirects__ —  will contain the additional __Locales__ field, which allows you to choose which locales the Redirects will apply to, as illustrated in the image below. Click on the languages you want to select.
 
-![img redirecionamentos intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/abd1dc44643c8c89b6165e5c304ba97b/03-redirecionamento-es.png)
+![img redirecionamentos intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/abd1dc44643c8c89b6165e5c304ba97b/03-redirecionamento-es.png)
 
 To learn more about this field, read our article on [how to configure Redirects in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4Gd2wLQFbCwTsh8RUDwSoL).
 
@@ -93,6 +89,6 @@ To learn more about this field, read our article on [how to configure Redirects
 
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Banners — available on VTEX Admin through __Storefront__ > __Banners__ —  will contain the additional __Locales__ field, which allows you to choose which locales the Banners will apply to, as illustrated in the image below. Click on the languages you want to select.
 
-![img banner intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8c927f2f9eb629778e628333ce788575/image_10.png)
+![img banner intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8c927f2f9eb629778e628333ce788575/image_10.png)
 
 To learn more about this field, read our article on [how to configure Banners in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
diff --git a/docs/tutorials/en/vtex-invoice-notifier.md b/docs/tutorials/en/vtex-invoice-notifier.md
index a6d3ab7a8..e5f15d01b 100644
--- a/docs/tutorials/en/vtex-invoice-notifier.md
+++ b/docs/tutorials/en/vtex-invoice-notifier.md
@@ -15,7 +15,7 @@ legacySlug: vtex-invoice-notifier
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-![chart EN](https://images.ctfassets.net/alneenqid6w5/3OMTqAs3Zhp1GFeBEtX8q0/4bcd68580be161fc3e98fc2877357e1a/chart.jpg_h_250)
+![chart EN](//images.ctfassets.net/alneenqid6w5/3OMTqAs3Zhp1GFeBEtX8q0/4bcd68580be161fc3e98fc2877357e1a/chart.jpg_h_250)
 
 ## App installation - VTEX Invoice Notifier
 
@@ -25,7 +25,7 @@ User should install the App from VTEX App Store - app.vtex.com
 
 When proceeding with the installation, a setup page will appear, in which the user should insert the endpoint responsible for communication with the invoice issuing system.
 
-![install-app](https://images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
+![install-app](//images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
 
 ## OMS notify invoice issuer
 
@@ -33,9 +33,9 @@ Once the endpoint is added to the App, OMS recognizes that the store is able to
 
 In the order, the operator must select the already invoiced package or items and create a new notification: 
 
-![notify-invoicer1](https://images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
+![notify-invoicer1](//images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
 
-![notify-invoicer2](https://images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
+![notify-invoicer2](//images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
 
 When the OMS user clicks the __Request Invoice__ button, the app would perform a POST request to the registered App endpoint with the following BODY example:
 
@@ -57,7 +57,7 @@ This property should be used to know which address sends the Invoice.
 
 Once successfully notified, the APP records this notification in VBASE (databank).
 
-![callBackProperty](https://images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
+![callBackProperty](//images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
 
 ## Invoice issuer gets invoice details
 
@@ -168,7 +168,7 @@ Pickup orders may or may not contain a client's identification. An order placed
 
 The way to identify if an order is Delivery or Pickup is by looking at the __shippingData.logisticsInfo[0].deliveryChannel__ object.
 
-![shipping-type](https://images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
+![shipping-type](//images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
 
 ## Inserting the tax invoice into an order
 
diff --git a/docs/tutorials/en/vtex-operation-service-level-agreement-sla.md b/docs/tutorials/en/vtex-operation-service-level-agreement-sla.md
new file mode 100644
index 000000000..87c906b30
--- /dev/null
+++ b/docs/tutorials/en/vtex-operation-service-level-agreement-sla.md
@@ -0,0 +1,26 @@
+---
+title: 'VTEX operation Service Level Agreement (SLA)'
+id: 2cIFrsY5S8usk84OU4QOKm
+status: PUBLISHED
+createdAt: 2019-01-24T20:45:48.688Z
+updatedAt: 2024-03-11T22:27:09.058Z
+publishedAt: 2024-03-11T22:27:09.058Z
+firstPublishedAt: 2019-01-24T22:13:57.539Z
+contentType: tutorial
+productTeam: Reliability
+author: 7FpKZ0rc6k4WqeymES80cw
+slug: vtex-operation-service-level-agreement-sla
+locale: en
+legacySlug: what-the-platform-s-operation-sla-is
+subcategory: 5PYkoNDZyo2G80yiiqG2YW
+---
+
+The [Service Level Agreement (SLA)](https://vtex.com/us-en/privacy-and-agreements/agreements/) is a document that regulates the use of the VTEX platform under the terms of the contract between VTEX and the customer, who is the contractor. This document specifies all the services that a contractor can expect from VTEX.
+
+The SLA expresses the service level of the platform's infrastructure and technically clarifies its operational uptime and downtime, as well as all the events that are or are not counted as incidents.
+
+Read our SLA at [VTEX Commerce - SLA Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/).
+
+## Learn more
+
+- [How is the platform’s operation SLA determined?](https://help.vtex.com/en/tutorial/how-is-the-platforms-operation-sla-determined--frequentlyAskedQuestions_662)
diff --git a/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
index e323d921c..50d063c10 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack: Fulfillment'
 id: 1zGUEItEEVsal6cuBEBNcA
 status: PUBLISHED
 createdAt: 2023-04-10T15:43:59.687Z
-updatedAt: 2023-04-20T15:41:30.789Z
-publishedAt: 2023-04-20T15:41:30.789Z
+updatedAt: 2023-08-31T19:52:23.529Z
+publishedAt: 2023-08-31T19:52:23.529Z
 firstPublishedAt: 2023-04-10T17:57:34.714Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: vtex-pick-and-pack-fulfillment
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
+<div class = "alert alert-info">
+If you are interested in implementing for your business, fill out our <a href="https://vtex.com/us-en/contact/">form</a> and indicate the name of the desired product in the <code>Comments</code> section.
+</div>
+
 [VTEX Pick and Pack](https://help.vtex.com/en/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU) is a solution to streamline stores’ fulfillment processes by optimizing orders’ picking and packing, and the last-mile delivery. The solution is composed of the [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) and **VTEX Pick and Pack Fulfillment** features, and appears in your VTEX Admin in **Apps**.
 
 The **VTEX Pick and Pack Fulfillment** module is related to the order handling process and has the following sections:
diff --git a/docs/tutorials/en/vtex-pick-and-pack-insights.md b/docs/tutorials/en/vtex-pick-and-pack-insights.md
new file mode 100644
index 000000000..83227437a
--- /dev/null
+++ b/docs/tutorials/en/vtex-pick-and-pack-insights.md
@@ -0,0 +1,65 @@
+---
+title: 'VTEX Pick and Pack: Insights'
+id: 5C4wXYmbbHTnMAUO0o11rn
+status: PUBLISHED
+createdAt: 2024-01-05T17:27:08.558Z
+updatedAt: 2024-01-05T20:28:40.388Z
+publishedAt: 2024-01-05T20:28:40.388Z
+firstPublishedAt: 2024-01-05T20:24:02.931Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-insights
+locale: en
+legacySlug: vtex-pick-and-pack-insights
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
+</div>
+
+**Insights** is a VTEX Admin page that displays information about your store's performance regarding VTEX Pick and Pack.
+
+![pick-pack-insights-en](//images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/147307180023927ebf3a6b7fce67583e/image.png)
+
+This page includes the following sections:
+
+* [Orders - Total in current period](#orders-total-in-current-period)
+* [Time on each step](#time-on-each-step)
+* [Orders - Order Performance](#orders-order-performance)
+* [Items](#items)
+
+## Orders - Total in current period
+
+In this section, you will see the total number of orders or worksheets for a given date and at a given facility. You can select the following:
+
+* Last day
+* Last 7 days
+* Last month
+* Last 3 months
+* Last 6 months
+
+![pick-pack-insights-2-en](//images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/78201db1138e08681fd53e5e1936bcd2/image.png)
+
+## Time on each step
+
+In this section, you will find information regarding the duration of each step in the handling process. You can see the time taken for the following steps:
+
+* Time in Picking
+* Time in Packing
+* Time in Shipping
+
+![pick-pack-insights-3-en](//images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/bbe1920023985fcaeb319696c4990efe/image.png)
+
+## Orders - Order Performance
+
+In this section, you will see information on the overall order performance and the average fulfillment time for each order.
+
+![pick-pack-insights-4-en](//images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/d94b159d309b0412229a89e7c5901a7e/image.png)
+
+## Items
+
+In this section, you will see information about the order items managed in VTEX Pick and Pack, the average picking time per item, the number of items picked by picker, and the order fulfillment rate.
+
+![pick-pack-insights-5-en](//images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/eb0fceee067533570ddbf10ec4f3a0fd/image.png)
diff --git a/docs/tutorials/en/vtex-pick-and-pack-last-mile.md b/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
index 6ad2ea93a..ff9d60f5e 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack: Last Mile'
 id: HN7WKV0xoq2ssVjsJlfzr
 status: PUBLISHED
 createdAt: 2023-04-10T16:01:14.613Z
-updatedAt: 2023-04-20T15:46:42.209Z
-publishedAt: 2023-04-20T15:46:42.209Z
+updatedAt: 2023-08-25T15:52:19.799Z
+publishedAt: 2023-08-25T15:52:19.799Z
 firstPublishedAt: 2023-04-10T16:35:43.623Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: vtex-pick-and-pack-last-mile
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
+<div class = "alert alert-info">
+If you are interested in implementing for your business, fill out our <a href="https://vtex.com/us-en/contact/">form</a> and indicate the name of the desired product in the <code>Comments</code> section.
+</div>
+
 [VTEX Pick and Pack](https://content.vtex.com/en/pick-and-pack/) is a solution to streamline stores’ fulfillment processes by optimizing orders’ picking and packing, and the last-mile delivery. The solution is composed of the [VTEX Fulfillment](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) and the **Last Mile** modules. 
 
 With **Last Mile**, merchants have complete visibility of shipping and order tracking. The module has the following sections:
diff --git a/docs/tutorials/en/vtex-pick-and-pack-mobile.md b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
new file mode 100644
index 000000000..3945b240a
--- /dev/null
+++ b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
@@ -0,0 +1,224 @@
+---
+title: 'VTEX Pick and Pack Mobile'
+id: 3i1K01CQlDBFYYp42WFOet
+status: PUBLISHED
+createdAt: 2024-04-04T20:42:46.548Z
+updatedAt: 2024-04-06T02:45:49.741Z
+publishedAt: 2024-04-06T02:45:49.741Z
+firstPublishedAt: 2024-04-06T01:59:46.300Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-mobile
+locale: en
+legacySlug: vtex-pick-and-pack-mobile
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+<p>If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
+</div>
+
+The [VTEX Pick and Pack](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) mobile app helps the picker — the person who picks and packs items in the facility — handle orders, from picking to shipping. This makes the store's order picking and delivery flow smoother and more efficient.
+
+![pickpack-mobile-en](//images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/c130518e5a14f76ca2ee9268bc298d92/image.png)
+
+Order handling is divided into four steps, following the usual store order flow:
+
+- [Create worksheets](#creating-worksheets)
+- [Picking](#picking)
+- [Packing](#packing)
+- [Shipping](#shipping)
+
+## Worksheets
+
+A worksheet consists of a set of orders that will be processed by the Pick and Pack flow simultaneously. This allows for efficient management and speeds up the processing of multiple orders at once.
+
+For example, a worksheet with only three orders:
+
+- Order 1: A red t-shirt and a pink skirt.
+- Order 2: Two red t-shirts and a white hat.
+- Order 3: A pink skirt and a white hat.
+When selecting this worksheet for handling, the app will display the following items for picking:
+
+- Three red t-shirts.
+- Two pink skirts.
+- Two white hats.
+
+The app will then help you pack each order with its respective items.
+
+<div class="alert alert-warning">
+Worksheets only apply to the order picking and packing steps. You must ship each order separately.
+</div>
+
+## Creating worksheets
+
+The __Unassigned__ tab lists the orders that should be selected for [worksheets](#worksheets). 
+
+![pickpack-ordemservico-en](//images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/fe3519449de97380728a84ea34d7ba86/image.png)
+
+To create a worksheet, follow the steps below:
+
+1. On the initial screen, click __Unassigned__ <i class="fas fa-arrow-right"></i>.
+2. Select the orders you want to add to the worksheet. To create a worksheet with all the orders, click <i class="fas fa-square"></i> `Select All`. 
+3. Click `Start Picking`.
+
+## Picking products
+
+The picking step consists of manually selecting the items listed in a [worksheet](#worksheets) and taking them to the appropriate packaging area in your facility.
+
+### Pending worksheets
+
+The Pending tab displays the list of worksheets that have not been picked yet.
+
+![pickpack-pendente-en](//images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/0b818a175fc5f290de6f37e1cff2d16f/image.png)
+
+In this tab, you can select the worksheet ID if you only want to see the picked items from that order.
+
+If there are worksheets assigned to the picker, you can access them from the picking screen by following these steps:
+
+1. On the app's home page, click **Continue Picking**. A list will be displayed with the [worksheets](#worksheets) assigned to the picker in the picking step.
+2. Click the worksheet you want to start picking.
+
+When clicking a worksheet, the following information is displayed:
+
+- __Items:__ Products to be picked from the worksheet.
+- __Approvals:__ Products that were rejected or replaced.
+- __Info:__ General information about the worksheet and the order.
+- __Summary:__ Products that have already been picked.
+
+![pickpack-em-separacao-en](//images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/53ee187d9cf252ce233ab2c5b5c2b9ea/image.png)
+
+By clicking the <i class="fas fa-ellipsis-v"></i> menu, the following options will be displayed:
+
+- **Add Note:** Add a note to the worksheet.
+- **Set as Ready for Packing:** Used to bulk pick orders or bulk reject orders.
+- **Pause Picking:** Pause the time count for picking the products listed in the worksheet.
+- **Open Barcode Reader:** Use the device's camera to read product barcodes.
+- **Print Picking List:** Generates a list of items from the worksheet for printing.
+- **Close Menu:** Closes the menu and returns to the picking screen. 
+
+To pick a product, follow the steps below:
+
+1. On the Picking screen, go to the __Items__ tab.
+2. Click the product you want to pick or drag the product to the right. If the product has more than one unit, you need to click the number of units. For products with weight or volume, confirm the measurements first, then confirm your selection, as shown in the example below.
+
+![pickpack-item-en](//images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/de6e921ac69b112aee8ac14a81810c60/image.png)
+
+To pick all the products from the worksheet at once, follow these steps:
+
+1. Click the <i class="fas fa-ellipsis-v"></i> menu.
+2. Click the **Set ready for packaging** option.
+3. Click **Pick all Available Items.**
+
+Once picked, the products will be listed in the __Summary__ tab.
+
+## Rejecting items
+
+There are some scenarios in which products may have to be rejected due to store settings and item availability. 
+
+<div class="alert alert-warning">
+The option to reject items may not be available. If you have any questions, please contact the store admin.
+</div>
+
+To reject a product from the worksheet, follow the steps below:
+
+1. Go to the __Items__ tab.
+2. Click and drag the product you want to reject to the left.
+3. Select the reason for rejection from the **Rejection reasons** list.
+4. Select the number of items you want to reject or click `Confirm and Discard All`.
+5. Click `Discard Item`.
+
+To reject all the products from the worksheet at once, follow these steps:
+
+1. Click the <i class="fas fa-ellipsis-v"></i> menu.
+2. Click the **Set ready for packaging** option.
+3. Click **Reject All Available Items**.
+
+<div class="alert alert-danger">
+If all the items from an order are rejected, the order will be completed automatically.
+</div>
+
+## Replacing items
+
+You can also replace the item with another one, depending on the store's settings and the item's availability.
+
+<div class="alert alert-warning">
+The option to replace items may not be available. If you have any questions, please contact the store admin.
+</div>
+
+To replace worksheet items, follow the steps below:
+
+1. Go to the __Items__ tab.
+2. Press and hold the product you want to replace.
+3. Click the **Replace Item** option.
+4. Search for or select the replacement item for the order and check the box <i class="fas fa-check-square"></i>.
+5. Select the number of units to be replaced.
+6. Select the reason for the replacement from the list of options.
+7. Complete the **Description** field with more information about the replacement.
+8. Click the `Confirm Replacement` button.
+
+## Completing the picking process
+
+After all items on the worksheet have been picked, rejected, or replaced, click the `Start Packing` button to move the worksheet to the [packing](#packing) step.
+
+## Packing
+
+During packing, the picker organizes order items into their respective shipping packages.  The Pick and Pack mobile app allows you to organize all the packages needed for multiple orders easily.
+
+![pickpack-empacotamento-en](//images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/a12a99b9e9988032ac4b4950d1f85f01/image.png)
+
+You can access the Packing page once you have [completed picking](#completing-the-picking-process) the items on a worksheet or by following these steps:
+
+1. On the app's initial screen, click **To pack**. A list will be displayed with the [worksheets](#worksheets) assigned to the picker in the packing step.
+2. Click the worksheet you want to start picking. 
+
+![pickpack-item-pendente-en](//images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/e3b58759bf7b7dfed1a7232f302bda2b/image.png)
+
+Follow the steps below to pack items:
+
+1. Under Packing, click the order you want to pack.
+2. Click the <i class="fas fa-plus"></i> button of the product you want to add to the package, or click <i class="fas fa-box"></i> to pack all products at once.
+<div class="alert alert-warning"> If you choose to pack all the order items, the remaining unpacked products will automatically be listed in a new package.</div>
+3. Select an existing package or add a new one by clicking `+ Create Package`.
+4. Select the package type you want to add.
+5. Select the number of units of this product you want to add to that package.
+6. Click the `Pack` button.
+
+You need to repeat this procedure as many times as necessary to pack all the items from a worksheet.
+
+The packed items will be displayed on the **Packed Items** tab. You can switch between viewing items as a list or by orders and packages by clicking <i class="fas fa-toggle-on"></i>.
+
+__Item list__
+![pickpack-item-empacotado-en](//images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/ec354b5f4e8e0dbce8102dac4bdc554e/image.png)
+
+__Orders and packages__
+![pickpack-item-empacotado-2-en](//images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/893b8268f9e01e764ca6f952852af1d1/image.png)
+
+After packing all items listed in the worksheet, complete the packing process on the Packed Items tab by clicking the `Confirm Packing` button.
+
+Then, the order will be completed in the app. Depending on your store's settings, the picker may proceed to the shipping step.
+
+## Shipping
+
+The shipping step allows you to create shipping services for orders picked and packed.
+
+<div class="alert alert-warning">
+Shipping is an optional step in the app. It depends on your operation and the store settings.
+</div>
+
+To ship packages using the Pick and Pack app, follow the steps below:
+
+1. In the initial screen, click the <i class="fas fa-ellipsis-v"></i> menu.
+2. Click the **To ship** option.
+3. Select the package you want to ship. You need to select an order with the `Preparing shipment` [status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196).
+4. Complete all shipping information:
+    - **Expected pickup date**
+    - **Expected delivery date**
+    ![pickpack-envio-en](//images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/91bf904272cdd0c22037fafa64e273a4/image.png)
+5. Select a carrier.
+6. Click `Select and Continue`.
+7. Confirm the shipping information. If no corrections are needed, click the `Create Service` button. If not, click `Back` and go back to step 5. 
+
+After that, the shipping information will be displayed on the app's next screen. The shipped orders will be available in the <i class="fas fa-ellipsis-v"></i> > __Completed__ menu. 
+
diff --git a/docs/tutorials/en/vtex-pick-and-pack-orders.md b/docs/tutorials/en/vtex-pick-and-pack-orders.md
new file mode 100644
index 000000000..52eeffe0e
--- /dev/null
+++ b/docs/tutorials/en/vtex-pick-and-pack-orders.md
@@ -0,0 +1,94 @@
+---
+title: 'VTEX Pick and Pack: Orders'
+id: 3rGbJlyedHdbWjvZ52p95b
+status: PUBLISHED
+createdAt: 2023-12-14T17:26:02.135Z
+updatedAt: 2024-01-05T17:31:16.218Z
+publishedAt: 2024-01-05T17:31:16.218Z
+firstPublishedAt: 2023-12-19T15:00:12.093Z
+contentType: tutorial
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-orders
+locale: en
+legacySlug: vtex-pick-and-pack-orders
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
+</div>
+
+**Orders** is a VTEX Admin page that displays information on orders placed and managed by VTEX Pick and Pack.
+
+This page allows you to:
+
+- [View orders](#viewing-orders)
+- [Search for orders](#searching-for-an-order)
+- [Filter orders](#filtering-orders)
+- [Export orders](#exporting-orders)
+
+![pick-and-pack-pedidos-EN](//images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/3ffa21f585d6c45e374ac2fb9c42f8aa/image.png)
+
+The page displays the following information in a table:
+
+| Table field | Description                                                                    |
+| ----------- | ------------------------------------------------------------------------------ |
+| Order ID    | Order identification number. It also indicates the date the order was created. |
+| Invoices    | Order invoice status, which can be **Invoiced** or **Not Invoiced**.                   |
+| Items       | Number of order items.                                                         |
+| Shipping    | Type of shipping, including **Delivery To Customer** and **In-store pickup**.          |
+| Payment     | Payment method used to place the order.                                        |
+| Tags        | Tags related to the order, such as UTM or coupons.                             |
+| Due Date    | Delivery or pickup due date.                                                   |
+| Status      | Step in the order fulfillment process.                                         |
+
+## Viewing orders
+You can optimize order search by using the following tabs:
+
+- **All:** All orders placed.
+- **Pending:** Orders that are pending, ready for picking and were picked.
+- **To Ship:** Orders awaiting shipping.
+- **Delivered:** Orders delivered to the customer via in-store pickup or carrier.
+- **Canceled:** Canceled orders.
+- **Rejected:** Rejected orders.
+
+You can also find more detailed information about each order by clicking the respective order in the table.
+
+![pick-and-pack-pedidos-2-EN](//images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/3f3ba4f4f9caac0b31d041afb33ce8b0/image.png)
+
+By selecting the desired order, you will see the following information:
+
+- **Items:** The list of items in the order. You can search for an item by entering its SKU ID or name in the search bar. You can also click the item to view more details about it.
+- **Order Notes:** Notes added by the merchant.
+- **Shipping Information:** Shipping information, including the shipping status.
+- **Payment Information:** Information related to the order payment.
+- **Additional Information:** Extra information related to the order.
+- **Logs:** Timeline with the order's update history.
+
+## Searching for an order
+
+You can search for an order by using the search bar. To do so, enter the order ID in the search bar, for example: `SLR-1341470502250-01`. 
+
+## Filtering orders
+
+You can refine the search and view orders by selecting the **Filter** option. Filter the orders by:
+
+- **Created Data:** Select the order created date.
+- **Delivery Date:** Select the order delivery date.
+- **Categories:** Select the category from order items.
+- **Payment Methods:** Select the payment method used for the order.
+- **Shipping Strategy:** Select the shipping strategy used for the order.
+- **Shipping Type:** Select the type of shipping chosen for the order.
+
+Click `Clear All` to remove the selected filters.
+
+## Exporting orders
+
+You can export orders by following the steps below:
+
+1. Click `Export`.
+2. Select the information you want to export: `Package Report` or `Order Report`.
+    * For the `Package Report`, select the date range you want to export, the shipping type, and the shipping method.
+![pick-and-pack-pedidos-3-EN](//images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/391f380bce100cf14645602f81b3fc9f/image.png)
+3.  Click `Export`.
diff --git a/docs/tutorials/en/vtex-pick-and-pack-settings.md b/docs/tutorials/en/vtex-pick-and-pack-settings.md
new file mode 100644
index 000000000..4b0210899
--- /dev/null
+++ b/docs/tutorials/en/vtex-pick-and-pack-settings.md
@@ -0,0 +1,267 @@
+---
+title: 'VTEX Pick and Pack: Settings'
+id: 16cs3e7hWk7c4cSZqe10O9
+status: PUBLISHED
+createdAt: 2024-01-05T20:43:38.480Z
+updatedAt: 2024-01-09T18:30:22.578Z
+publishedAt: 2024-01-09T18:30:22.578Z
+firstPublishedAt: 2024-01-09T16:30:00.192Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-settings
+locale: en
+legacySlug: vtex-pick-and-pack-settings
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
+</div>
+
+**Settings** is a VTEX Admin page that allows you to select the VTEX Pick and Pack settings for your store. The settings are distributed in the following tabs:
+
+* [Picking](#picking)
+* [Categories](#categories)
+* [Packing](#packing)
+* [Orders](#orders)
+* [Automation](#automation)
+* [Users](#users)
+* [Catalog](#catalog)
+* [Facilities](#facilities)
+
+## Picking
+
+In this tab, you'll find the settings related to the picking of order items. Here, you can set actions the picker can take during the picking process, including notifying you that an order item is unavailable and suggesting replacements.
+
+![pick-and-pack-separacao-en](//images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/0b5dd839ffadbb4fc7670bae7b6a1e27/image.png)
+
+### Picking Strategy
+
+In this section, you can define the picking strategy types you would like for your pickers.
+
+<div class = "alert alert-info">
+  Only the <strong>Wave picking</strong> strategy is currently available.
+</div>
+
+### Order Changes
+
+In this section, you can set actions related to order changes, such as when items are out of stock.
+
+* **Send changes to the OMS:** Allows you to send the changes made by the picker to the [VTEX OMS](https://help.vtex.com/en/tutorial/gerenciamento-de-pedidos-visao-geral--tutorials_201). You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow changing item prices:** Allows the picker to change the item prices from an order. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow replacing items:** Allows the picker to replace unavailable items from an order. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow rejecting items:** Allows the picker to reject unavailable items from an order. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow changing item quantity:** Allows the picker to change the number of items in an order. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow adding order notes:** Allows the picker to add notes to orders, such as the reason for a price change. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow adding item notes:** Allows the picker to add notes to items, such as why an item was rejected. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Rejection reasons:** Displays the options available for the picker to choose from when rejecting items from an order. The picker can choose as many options as they want.
+* **Price change reasons:** Displays the options available for the picker to choose from when changing item prices from an order. The picker can choose as many options as they want.
+* **Limit for quantity changes in order items:** Percentage that limits how many items can be changed from an order.
+* **Limit for price changes in order items:** Percentage that limits how many item prices can be changed from an order.
+* **Total limit for order changes:** Percentage that limits the total number of orders that can be changed.
+
+#### Worksheets
+
+In this section, you can set the options that will be applied to your store worksheets.
+
+* **Allow multiple orders in one worksheet:** Allows adding multiple orders to a worksheet. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Enable quick picking:** Allows fast picking and automatic confirmation of product quantities and prices, avoiding the need for manual checks by the picker. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Enable express fulfillment:** Allows the express fulfillment option, enabling orders to be picked and packed simultaneously. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow moving orders after the picking process has started:** Allows editing worksheets even after the picking process has started. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow moving orders between worksheets:** Allows editing worksheets by moving the added orders between worksheets. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Worksheet tags:** Allows adding custom tags to optimize the order-picking process.
+* **Enable dynamic EAN codes:** Enables the use of dynamic barcodes, which can be changed based on the product's characteristics, such as weight. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+
+### Onboarding
+
+You can activate the VTEX Pick and Pack app configuration process by following the steps below:
+
+1. Click `Onboarding`.
+2. Click `Start`.
+3. Select the options you want to set for the app. This setting will only apply to parentAccount.
+4. Click `Next`.
+5. Select the worksheets to be managed in the app and the number of tabs you want to create.
+6. Click `Next`.
+7. Activate <i class="fas fa-toggle-on"></i> the sales associates to whom you want the settings to apply.
+8. Click `Completed`.
+9. Click `Close`.
+
+Click `Save` to save the changes.
+
+## Categories
+
+On this tab, you can configure the order of the categories in which the orders will be picked. This enables the picker to manage the order picking process efficiently.
+
+![pick-pack-categorias-en](//images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/1399599a366ab0232398093187d11eaa/image.png)
+
+* **Fast configuration**: Applies the settings to all facilities. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Facility**: Determines the facility to which the category settings will be applied.
+
+To add a category to the list, click the desired category. To reorder, drag the category to the desired position in the list.
+
+You can import a CSV file or export the already configured list.
+
+## Packing
+In this tab, you will find the packing settings for order items.
+
+![pick-pack-empacotamento-en](//images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/af91942f280c2312c521db86060c706e/image.png)
+* **Allow package reports**: Enables the visualization of the package report, which will be displayed on the Orders screen. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+* **Allow automatic packing**: Allows automatic packaging of orders. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
+
+### Configuring package label printing
+
+In this section, you can configure the characteristics of the label that will be attached to the order package. See the available characteristics below:
+
+* **Print package label settings enabled**: Enables or disables the option to edit the label characteristics.
+* **Format**: Determines the label format.
+* **Font size (px)**: Determines the font size (in pixels) that will be printed on the label.
+
+#### Margins
+
+* **Left**: Size of the label's left margin in millimeters.
+* **Right**: Size of the label's right margin in millimeters.
+* **Top**: Size of the label's top margin in millimeters.
+* **Bottom**: Size of the label's bottom margin in millimeters.
+
+#### Dimensions
+
+* **Width**: Label width in millimeters.
+* **Height**: Label height in millimeters.
+
+### Configuring print receipt
+
+In this section, you can configure the order receipt printing characteristics. See the available characteristics below:
+
+* **Print receipt settings enabled**: Enables or disables the option to edit the receipt's characteristics.
+* **Format**: Determines the receipt format.
+* **Font size (px)**: Determines the font size (in pixels) that will be printed on the receipt.
+
+#### Margins
+
+* **Left**: Size of the receipt's left margin in millimeters.
+* **Right**: Size of the receipt's right margin in millimeters.
+* **Top**: Size of the receipt's top margin in millimeters.
+* **Bottom**: Size of the receipt's bottom margin in millimeters.
+
+#### Dimensions
+
+* **Width**: Receipt width in millimeters.
+* **Height**: Receipt height in millimeters.
+
+### Envelopes
+
+In this section, you must add the types of envelopes your store will use to package and ship orders. To add a new envelope, follow these steps:
+
+1. Click `Create`.
+2. Complete the fields below:
+   * **Name**: Name that will identify the envelope.
+   * **Type**: Envelope type. The options are Box, Bag, Envelope, Tape, Paper, and Others.
+   * **Description**: Envelope description for internal use.
+   * **Code**: Envelope identification code.
+   * **Cubic weight**: Envelope [cubic weight](https://help.vtex.com/en/tutorial/como-o-peso-cubado-e-calculado--tutorials_128).
+   * **Height**: Envelope height in millimeters.
+   * **Length**: Envelope length in millimeters.
+   * **Weight**: Envelope weight in millimeters.
+   * **Width**: Envelope width in millimeters.
+3. Click `Save`.
+
+Click `Save` to save the changes.
+
+## Orders
+
+In this tab, you will find settings for orders processed by VTEX Pick and Pack.
+
+![pick-pack-config-pedidos-en](//images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/557e12764b6dc82064c62cc8e9f6a405/image.png)
+
+* **Download Orders From OMS**: Allows exporting orders from the OMS.
+* **Payment methods**: Payment methods used in the orders being exported.
+* **Shipping method**: Shipping methods used in the orders being exported.
+* **Shipment type**: Shipping types used in the orders being exported.
+* **Order tags**: Tags used in the orders being exported.
+
+Click `Save` to save the changes.
+
+## Automation
+
+In this tab, you will find the automation settings for VTEX Pick and Pack processes.
+
+![pick-pack-automacao-en](//images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/5bdf2473a93291bf2c839415872f4805/image.png)
+
+To create a new automation, follow the steps below:
+
+1. Click `Create`.
+2. Complete the __Name__ field with the name of the automation and __Automation for__ with the option you want to automate.
+3. Click `Save`.
+
+## Users
+
+In this tab, you can manage users, admins, and pickers from your VTEX Pick and Pack operation. Users with Admin permission will have access to the VTEX Admin and be able to make changes within the tool. Users with Picker permission can only access the VTEX Pick and Pack app.
+
+![pick-pack-usuarios-en](//images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/445bb2e98986273d4fbd0afba11a6310/image.png)
+
+To create a new user, follow the steps below:
+
+1. Click `Create`.
+2. Select the permission type you want for your new user: __Admin__ or __Picker__.
+3. Add users based on the desired permissions:
+  * __Admin__ permission
+    1. Select the listed user you want to add as __Admin__.
+    2. Click `Create`.
+    ![pick-pack-usuarios-2-en](//images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/b91e3d2d4268d779b7df0453d8cbf7c1/image.png)
+  * __Picker__ permission
+    1. Complete the form with the following information:
+       * User name
+       * Name
+       * Email (required)
+       * Password (required)
+       * Facilities
+       * Allow shipping packages
+       * Categories
+    2. Click `Create`.
+    ![pick-pack-usuarios-3-en](//images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/5ab7dd935ac929c4c3bd2c2f7feac3af/image.png)
+
+## Catalog
+
+In this tab, you can access information about items in orders that are currently in the shipping stage.
+
+![pick-pack-catalogo-en](//images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/846976dd5b8fab2a93d32264334f9686/image.png)
+
+The page displays the following information in a table:
+
+| Column fields | Description                                                                                                   |
+| ------------- | ------------------------------------------------------------------------------------------------------------- |
+| Item          | Product name.                                                                                                 |
+| Product ID    | Product identification number.                                                                                |
+| SKU           | Product SKU identification number.                                                                            |
+| EAN           | Product EAN number.                                                                                           |
+| Categories    | Categories in which the product is listed.                                                                    |
+| Dimensions    | Product dimensions.                                                                                           |
+| Weight        | Product weight.                                                                                               |
+| Weighable     | Products that must be weighed to indicate their weight in kilograms or grams, depending on the configuration. |
+| Temperature   | Products that must be stored at a minimum temperature to avoid deterioration.                                 |
+| Active        | Whether the product is available to customers or not.                                                         |
+
+You can add bulk SKU IDs and EANs for your products via a CSV file. To do this, follow the steps below:
+
+1. Click the `Bulk Upload SKU/EAN` button.
+2. Add the file you want to upload.
+3. Click `Continue`.
+
+You can also index the catalog to update the product list. To do this, click `Index Catalog` and then `Continue`.
+
+<div class = "alert alert-danger">
+Indexing the catalog will delete and recreate all its contents, so you could lose all your custom EAN and SKU codes.
+</div>
+
+## Facilities
+
+In this tab, you will be able to add and view your store's facilities.
+
+![pick-pack-instalacoes-en](//images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/3c3a6b90a27abf2d6144ae505a64d46c/image.png)
+
+To create a new facility, follow these steps:
+
+1. Click `Create`.
+2. Complete the form with your facility's address. You must complete the __Street__, __City__, and __State__ fields.
+3. Click `Save`.
diff --git a/docs/tutorials/en/vtex-pick-and-pack-worksheets.md b/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
new file mode 100644
index 000000000..09a1bdf1f
--- /dev/null
+++ b/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
@@ -0,0 +1,79 @@
+---
+title: 'VTEX Pick and Pack: Worksheets'
+id: 7bUwvmTY6eOqxzhyMIIzvz
+status: PUBLISHED
+createdAt: 2024-01-03T18:38:05.781Z
+updatedAt: 2024-01-03T20:13:50.986Z
+publishedAt: 2024-01-03T20:13:50.986Z
+firstPublishedAt: 2024-01-03T19:55:03.094Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-worksheets
+locale: en
+legacySlug: vtex-pick-and-pack-worksheets
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
+</div>
+
+**Worksheets** is a VTEX Admin page to manage the worksheets used by pickers to group and pick the order items in real time. Pickers can group as many orders as they like in each worksheet.
+
+This page allows you to:
+
+* [Create worksheets](#create-worksheets)
+* [Search for worksheets](#search-for-worksheets)
+* [Filter worksheets](#filter-worksheets)
+
+![pick-pack-ordem-servico-en](//images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/f2df0910a4b7c2b1be73553b20394536/image.png)
+
+Orders are displayed in cards with the following information:
+
+![pick-pack-ordem-servico-2-en](//images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/d0d6b35257db31e3b166b8a30edd83ed/image.png)
+
+* Worksheet ID.
+* Number of orders in the worksheet.
+* Number of items in the worksheet.
+* Name of the worksheet picker.
+* Facility name.
+* Worksheet status.
+
+## Creating a worksheet
+
+You can create a new worksheet by following the steps below:
+
+1. In the **Unassigned Orders** menu, select the orders you want to add to the worksheet. There is no limit to the number of orders per worksheet.
+2. Click `Assign to`.
+3. Click the **Manual** tab to create the worksheet manually.
+4. Click the `+` icon to create a worksheet. You can create more than one worksheet.
+5. Drag the orders you want to add to the worksheet.
+  ![pick-pack-ordem-servico-3-en](//images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/e0acc7025f39b107b668caca52555544/image.png)
+6. Click `Create`.
+
+## Viewing worksheets
+
+You can optimize the worksheet query from the following tabs:
+
+* **All:** All worksheets created.
+* **Picking:** Worksheets in which the picking is in progress.
+* **Packing:** Worksheets awaiting shipping.
+* **Completed:** Completed worksheets.
+* **Canceled:** Canceled worksheets.
+
+You can also view more worksheet details by clicking the <i class="fas fa-chevron-down"></i> button on the card.
+
+![pick-pack-ordem-servico-4-en](//images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/bdf69bd28c64d9ff9e855c08d9e26645/image.png)
+
+## Searching for a worksheet
+
+You can search for a worksheet using the search bar. You can enter the worksheet ID or the order ID you want to find.
+
+## Filtering worksheets
+
+You can refine the search and view orders by selecting the Filter option. Filter the worksheets by:
+
+* **Categories:** Item categories from the orders.
+* **Available Pickers:** Pickers that are available.
+* **Facilities:** Added facilities. You can view all facilities or filter to view only specific ones.
diff --git a/docs/tutorials/en/vtex-pick-and-pack.md b/docs/tutorials/en/vtex-pick-and-pack.md
index 3d570b0a3..0290e00db 100644
--- a/docs/tutorials/en/vtex-pick-and-pack.md
+++ b/docs/tutorials/en/vtex-pick-and-pack.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack'
 id: 1OOops3WrUyz7e0bnhkfXU
 status: PUBLISHED
 createdAt: 2023-04-10T15:22:56.572Z
-updatedAt: 2023-04-20T00:55:31.302Z
-publishedAt: 2023-04-20T00:55:31.302Z
+updatedAt: 2023-08-25T15:48:44.351Z
+publishedAt: 2023-08-25T15:48:44.351Z
 firstPublishedAt: 2023-04-10T15:42:38.221Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: vtex-pick-and-pack
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
+<div class = "alert alert-info">
+If you are interested in implementing for your business, fill out our <a href="https://vtex.com/us-en/contact/">form</a> and indicate the name of the desired product in the <code>Comments</code> section.
+</div>
+
 **VTEX Pick and Pack** is the solution that enables merchants to manage order picking, packing, and delivery from physical stores and warehouses to customers’ addresses or [pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). All management is made in one place, providing visibility and control for merchants through the whole fulfillment process.
 
 ## Capabilities
diff --git a/docs/tutorials/en/vtex-shield.md b/docs/tutorials/en/vtex-shield.md
new file mode 100644
index 000000000..9e479ff02
--- /dev/null
+++ b/docs/tutorials/en/vtex-shield.md
@@ -0,0 +1,63 @@
+---
+title: 'VTEX Shield'
+id: 2CVk6H9eY2CBtHjtDI7BFh
+status: PUBLISHED
+createdAt: 2024-04-25T00:31:01.895Z
+updatedAt: 2024-07-09T13:39:54.272Z
+publishedAt: 2024-07-09T13:39:54.272Z
+firstPublishedAt: 2024-04-25T01:19:00.025Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-shield
+locale: en
+legacySlug: vtex-shield
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/us-en/contato/">contact form</a>.</p>
+</div>
+
+VTEX Shield offers additional, customizable protection layers for stores that prioritize platform resilience and the security standards guaranteed by VTEX's existing security [certifications and practices](https://vtex.com/us-en/security/security-practices/).
+
+The solution provides advanced security features, allowing you to detect potential risks and take preventive actions. This ensures your store remains protected from unexpected disruptions, keeping it operational and reliable.
+
+When requesting VTEX Shield, you can choose from the following features:
+
+* [Security Monitor](#security-monitor)
+* [Penetration tests](#penetration-tests)
+* [Web Application Firewall (WAF)](#web-application-firewall-waf)
+* [Data Protection Plus](#data-protection-plus)
+
+## Security Monitor
+
+Security Monitor is a VTEX Admin dashboard that detects security threats related to the behavior of admin users and incorrect settings. Potential risks include outdated or compromised [application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet), users or credentials with excessive permissions, and inactive users. The tool provides an overview of threats and solutions, along with the option to send email notifications to merchants for each finding.
+
+Security Monitor is available in the VTEX Admin only for stores using VTEX Shield. For more information, check out the [Security Monitor](https://help.vtex.com/en/tutorial/security-monitor--5LOVNLrrtmgSj99pM1NS4x) guide.
+
+## Penetration tests
+
+Penetration tests, or pentests, are simulated attacks on a computer system, network, or web application to assess security, identify vulnerabilities, and fix them.
+
+Only stores with VTEX Shield that request this feature are authorized to run penetration tests, following the procedures indicated in [Penetration tests and vulnerability notifications](https://help.vtex.com/en/tutorial/penetration-testing-and-vulnerability-notice--6jodF6s1I50Fg84ZwutOCb).
+
+## Web Application Firewall (WAF)
+
+The Web Application Firewall (WAF) protects web applications by monitoring and filtering internet traffic.
+
+This security feature plays a key role in protecting websites, online services, and web applications from attacks such as SQL injection, cross-site scripting (XSS), and other common web vulnerabilities.
+
+Only stores with VTEX Shield that request this feature can request WAF activation. Learn more about how the [Web Application Firewall (WAF)](https://help.vtex.com/pt/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn) works and the types of threats it protects against.
+
+## Data Protection Plus
+
+<div class="alert alert-info">
+  <p>This feature is in closed beta and is only available in some regions. If you have any questions, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>.</p>
+</div>
+
+[Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) is a data architecture that offers an additional layer of protection for personal data. In this architecture, all PII (Personally Identifiable Information) data is stored in the [Profile System](https://developers.vtex.com/docs/guides/profile-system), a service developed specifically for processing PII following a [set of rules and processes](https://developers.vtex.com/docs/guides/pii-data-architecture-specifications) appropriate for this purpose. 
+
+Other platform modules, such as Orders and Checkout, only store anonymized data associated with a Profile System token, increasing the security of this information.
+
+See the set of guides for the [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) category in the Developer Portal for more details and specifications about this architecture.
diff --git a/docs/tutorials/en/vtex-shipping-network-correios-activation.md b/docs/tutorials/en/vtex-shipping-network-correios-activation.md
new file mode 100644
index 000000000..72c408433
--- /dev/null
+++ b/docs/tutorials/en/vtex-shipping-network-correios-activation.md
@@ -0,0 +1,20 @@
+---
+title: 'VTEX Shipping Network Correios: Activation'
+id: 57opHihFbRAwrjQjCTymTa
+status: PUBLISHED
+createdAt: 2023-08-31T13:25:47.887Z
+updatedAt: 2023-08-31T14:48:48.682Z
+publishedAt: 2023-08-31T14:48:48.682Z
+firstPublishedAt: 2023-08-31T14:36:56.281Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: vtex-shipping-network-correios-activation
+locale: en
+legacySlug: vtex-shipping-network-correios-activation
+subcategory: 5n5MnINzWTQUX1I2EZl4Ib
+---
+
+<div class="alert alert-warning" role="alert">
+This is a regional exclusive content not applicable to English speaking countries.
+</div>
diff --git a/docs/tutorials/en/vtex-shipping-network-correios-faq.md b/docs/tutorials/en/vtex-shipping-network-correios-faq.md
index 42e4a86af..9c26c3628 100644
--- a/docs/tutorials/en/vtex-shipping-network-correios-faq.md
+++ b/docs/tutorials/en/vtex-shipping-network-correios-faq.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network Correios: FAQ'
 id: 2Wavf7Wie5GEUAEHKtn5oC
 status: PUBLISHED
 createdAt: 2023-06-01T13:24:23.895Z
-updatedAt: 2023-06-09T12:55:42.194Z
-publishedAt: 2023-06-09T12:55:42.194Z
+updatedAt: 2023-08-25T15:32:25.418Z
+publishedAt: 2023-08-25T15:32:25.418Z
 firstPublishedAt: 2023-06-01T14:47:24.289Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/en/vtex-shipping-network-dashboard.md b/docs/tutorials/en/vtex-shipping-network-dashboard.md
index e328fec60..e37c646a1 100644
--- a/docs/tutorials/en/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/en/vtex-shipping-network-dashboard.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Dashboard'
 id: 51e8tx1IehiN4ZtURRWU92
 status: PUBLISHED
 createdAt: 2020-04-06T20:01:00.909Z
-updatedAt: 2023-06-09T12:56:22.175Z
-publishedAt: 2023-06-09T12:56:22.175Z
+updatedAt: 2024-02-29T19:20:49.152Z
+publishedAt: 2024-02-29T19:20:49.152Z
 firstPublishedAt: 2020-04-16T21:37:18.831Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -48,8 +48,8 @@ This tab is used to monitor and supervise the financial result of your Logistics
 | **Overall Projected Cost**        | It is, regardless of VTEX Shipping Network, the sum of the shipping values estimated by the Inventory & Shipping module for all orders. It includes arrows that indicate the percentage of cost growth or decrease. The cost reduction on that (down arrow) card is a positive measure for a store's results.                                                                                                                                 |
 | **VTEX Shipping Network Projected Cost**     | Sum of the shipping values estimated for all orders by the Inventory & Shipping, filtering only by VTEX Shipping Network carriers. It includes arrows that indicate the percentage of cost growth or decrease. The cost reduction on this (down arrow) card is a positive measure for a store's results.
                                                                                                             |
-| **Cost Issued via CTE**        | Cost that came from CONEMB for all these orders. VTEX receives this information through the CONEMB files, which are sent by the carriers. This file shows in detail how much the carrier has spent, and the order invoice number. It includes arrows that indicate the percentage of cost growth or decrease. The cost reduction on this (down arrow) card is a positive measure for a store's results.                                                                                           |
-| **Indicated cost difference** | Difference between the projected cost and the cost issued via CTE. CTE is the file received from the VTEX Shipping Network carriers, which shows in detail how much the carrier has spent, and the order invoice number. It includes arrows that indicate the percentage of cost growth or decrease. The increase in the cost difference on this card is a positive measure for a store's results.                                          |
+
+* We are improving the **Cost Issued via CTE** and the **Indicated cost difference**, and they are currently unavailable.
 
 ## Performance
 
@@ -59,7 +59,7 @@ For calculating the performance, the system considers all packages for delivery.
 
 Carrier performance is presented as a percentage and is calculated by dividing the number of packages delivered on time by the total number of packages delivered. Thus, the performance calculation only takes into account the packages that have been delivered.
 
-![equation EN performance](https://images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/f899c821db95eef10472ae180e5b74e4/equation_EN_performance.gif)
+![equation EN performance](//images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/f899c821db95eef10472ae180e5b74e4/equation_EN_performance.gif)
 
  The VTEX Shipping Network Performance tool allows you to:
 
@@ -83,9 +83,9 @@ All VTEX Shipping Network carriers have a verified badge. You can see the pink b
 
 If a carrier’s performance is not displayed on the platform, it means the tracking data has not been integrated with VTEX Shipping Network.
 
-To calculate the performance of carriers that are not VTEX Shipping Network, sellers must send their data through a tracking API provided by the VTEX Shipping Network solution.
+To calculate the performance of carriers that are not VTEX Shipping Network, sellers must send their data through a tracking API provided by the VTEX Shipping Network solution. In such cases, note that the panel data may be inaccurate because there is no validation of delivery being carried out within the indicated deadline.
 
-To learn more about how to perform this integration, see the[ VTEX Shipping Network overview](https://developers.vtex.com/vtex-rest-api/reference/vtex-log-api-overview) in our API documentation.
+To learn more about how to perform this integration, see the[ VTEX Shipping Network overview](https://developers.vtex.com/docs/api-reference/vtex-shipping-network-api) in our API documentation.
 
 ### Exporting reports
 
@@ -95,4 +95,4 @@ You can download a report with data from the carriers and package deliveries. To
 2. Wait until you receive the spreadsheet by email.
 3.  Download the spreadsheet.
 
-![Resumo de performance EN](https://images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/786e60dd75dc0118711259b8ab4bbd7d/Resumo_de_performance_EN.png)
+![Resumo de performance EN](//images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/786e60dd75dc0118711259b8ab4bbd7d/Resumo_de_performance_EN.png)
diff --git a/docs/tutorials/en/vtex-status-page.md b/docs/tutorials/en/vtex-status-page.md
new file mode 100644
index 000000000..8d928b8a8
--- /dev/null
+++ b/docs/tutorials/en/vtex-status-page.md
@@ -0,0 +1,169 @@
+---
+title: 'VTEX Status page'
+id: gPhqDn9IQ3c67wbJEX3JJ
+status: PUBLISHED
+createdAt: 2019-01-14T19:58:58.431Z
+updatedAt: 2023-12-21T17:10:08.895Z
+publishedAt: 2023-12-21T17:10:08.895Z
+firstPublishedAt: 2019-01-14T20:01:43.663Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-status-page
+locale: en
+legacySlug: untitled-entry-2019-01-14-at-07-58-58, vtex-status-understand-how-the-platform-status-works, platform-status-page
+subcategory: 5PYkoNDZyo2G80yiiqG2YW
+---
+
+On the [VTEX Status](https://status.vtex.com/) page, you can monitor the platform's stability in real time and access the full incident history.
+
+Our team reports events whenever our automatic monitoring system identifies an instability in the platform modules. Scheduled maintenance is also reported in detail on this page.
+
+![statuspage-1](//images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/d8aea2fa393bfb699b6ea71b9b59d7a9/statuspage-1.png)
+
+Below, you can find details of the VTEX platform's status page elements, developed with the [incident.io](https://incident.io/) tool:
+
+* [Report a problem](#reporting-a-problem)
+* [Notifications](#notifications)
+* [General status](#general-status)
+* [System status](#system-status)
+* [Calendar](#calendar)
+* [Incident logs](#incident-logs)
+* [Scheduled maintenance logs](#scheduled-maintenance-logs)
+
+## Reporting a problem
+
+By clicking the `Report a problem` button in the top right corner of the page, you can contact [our support](https://support.vtex.com/hc/en-us/requests) team to let us know about platform instabilities.
+
+## Notifications
+
+The status page displays the `Subscribe to updates` button in the top right corner. By clicking it, you can subscribe to receive updates via email, [RSS feed](https://rss.com/blog/how-do-rss-feeds-work/), or [Slack](https://slack.com/).
+
+By choosing the email subscription option, you can receive notifications only for certain components. To do so, select the **Subscribe to specific components** option. Then, check the components you want to monitor.
+
+![statuspage-2](//images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/2e3c6f8f076298d91e2ff5b8139325e0/statuspage-2.png)
+
+## General status
+
+In this section, you can view the platform's general status, which can be _fully operational_, _experiencing issues_, or _undergoing maintenance_.
+
+When problems or maintenance affect a system, the impacted component and the incident description are displayed. See examples below.
+
+![statuspage-3](//images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/21bc090adf8b43e7579831a500e4b627/statuspage-3.png)
+
+![statuspage-4](//images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/80950f0d2faadb58b813eddc64eec7bc/statuspage-4.png)
+
+![statuspage-5](//images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/6d7fb7f4ffbf645810e4ade63efa9e64/statuspage-5.png)
+
+## System status
+
+In this section, you can check the status of each platform system and its components in real time.
+
+![statuspage-6](//images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/fdc22b9eff6d4bf11bfba43a283da409/statuspage-6.png)
+
+By clicking the arrow <i class="fas fa-chevron-down"></i> next to the number of components, you can view the status of specific components for each system.
+
+If maintenance is scheduled for a future date, you will also see the `Upcoming maintenance scheduled` button, as shown below. Hovering over this button will display the scheduled maintenance event. You can click to view its log.
+
+![statuspage-7](//images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/1fbf5de5c36e02ec2bfd6204471a2ebf/statuspage-7.png)
+
+The possible statuses for each component are:
+
+* **Operational:** Operation is stable.
+* **Degraded performance:** Performance is below the expected.
+* **Partial outage:** Features are operating partially.
+* **Full outage:** Operation is completely disrupted.
+* **Under maintenance:** System is undergoing maintenance.
+
+Below, we detail the components displayed on the page.
+
+### Storefront
+
+Problems navigating the storefront.
+
+* **Portal/CMS:** Instabilities observed in stores developed with [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) storefront technology.
+* **Store Framework:** Instabilities observed in stores developed using [Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) storefront technology.
+* **FastStore:** Instabilities observed in stores developed using [FastStore](https://www.faststore.dev/) storefront technology.
+* **Sales App:** Instabilities observed in [Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf), a VTEX solution for assisted sales in physical stores.
+* **3rd Party Apps**: Instabilities observed in extensions maintained by third parties.
+
+### Checkout
+
+Problems in features related to the order creation flow, i.e., checkout and its dependencies.
+
+* **Order Placement:** Disruptions in the sales flow.
+* **Shipping Calculation:** Inconsistencies in shipping conditions.
+* **Pricing Calculation:** Inconsistencies in prices, promotions, or surcharges.
+* **Payments Gateway:** Inconsistencies in payment transactions.
+* **Payment Connectors:** Instabilities observed in specific payment providers.
+
+### Admin
+
+Problems related to navigating the VTEX Admin and its modules, such as Order Management, Price Settings, and Logistics.
+
+* **Catalog Management:** Disruptions in updating catalog content (product details, images, prices, inventory, search indexing, etc.).
+* **Content Management:** Disruptions in updating non-product-related content (banners, landing pages, promotions, coupons, gift cards, etc.).
+* **Order Management:** Disruptions in order fulfillment.
+* **Marketplace Connectors:** Instabilities observed in specific marketplace connectors.
+* **Admin Operations:** Other impacts on the merchant experience outside the scope of other Admin components.
+
+### Developer Tools
+
+Problems related to app development, integrations, and store themes.
+
+* **VTEX IO:** Instabilities observed in apps developed using VTEX IO.
+* **Master Data:** Instabilities observed in integrations that depend on Master Data.
+* **API Integrations:** Other impacts on the use of VTEX APIs.
+
+## Calendar
+
+The calendar section displays the incidents and scheduled maintenance logs that occurred each day of the current month.
+
+To navigate to previous months, click the arrow `<`.
+
+To view incidents from a specific day, hover over the date. To access the page with the complete event log, click the listed incident or maintenance.
+
+![statuspage-8](//images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/8ca30c0cd6d89aaca8d92dc21af7274e/statuspage-8.png)
+
+<div class="alert alert-warning">
+  <p>If the scheduled maintenance lasts longer than a day, only the start date will be selected in the calendar. You must open the <a href="#scheduled-maintenance-logs"> maintenance log</a> to see the start and end dates.</p>
+</div>
+
+Below, we detail the information available in the [incident log](#incident-logs) and the [scheduled maintenance log](#scheduled-maintenance-logs).
+
+## Incident logs
+
+The incident details page displays the following information:
+
+![status-page-9-en](//images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/6cacbbfc2e5b7e99bf4309e3622edda4/status-page-9-en.png)
+
+* **Title:** Title describing the incident.
+* **Status:** Each incident has a defined cycle in which our team works to identify and solve problems. These are stages of this cycle:
+    * **Investigating:** The incident's first status focuses on analyzing the impacts and related services and identifying the root cause.
+    * **Identified:** With the origin of the error properly identified, the development team begins to perform actions towards the solution.
+    * **Monitoring:** After completing the system stabilization actions, with the operation indicators normalized, we continue to stay in alert and closely monitor the performance of impacted services or modules.
+    * **Resolved:** Once the platform's performance is stabilized, we return to normal monitoring and consider that the platform is working as expected.
+* **Duration:** Time taken to solve the incident.
+* **Summary:** Text summarizing the incident.
+* **Affected components:** The platform components impacted by the incident. By clicking the arrow next to the number of components, you can view the impact on more specific components.
+* **Updates**: Timeline with incident updates and status changes.
+
+By clicking the `Subscribe to updates` button on an incident log, you can sign up to receive updates on that specific incident via email, RSS feed, or Slack.
+
+## Scheduled maintenance logs
+
+Platform updates are made constantly and generally do not impact our clients' operations. However, occasionally, some of them require the service to be temporarily unavailable.
+
+For cases that affect the platform's stability, we use the VTEX status page to inform you of all the details, such as when the maintenance will be carried out, its duration, and its impact.
+
+The scheduled maintenance log displays the same information as the incident logs. The possible statuses for a scheduled maintenance are:
+
+* **Scheduled:** The maintenance event is scheduled.
+* **In progress:** The maintenance event is in progress.
+* **Complete:** The maintenance event has been completed
+
+Below are some examples illustrating the status and timeline of scheduled maintenance events.
+
+![statuspage-10](//images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/7dc874395f5b13ba6e1ce62b76913398/statuspage-10.png)
+
+![statuspage-11](//images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/9900eb1dd6b9086a6c6049855dbc17c9/statuspage-11.png)
diff --git a/docs/tutorials/en/vtex-support-apac.md b/docs/tutorials/en/vtex-support-apac.md
new file mode 100644
index 000000000..81ce333f9
--- /dev/null
+++ b/docs/tutorials/en/vtex-support-apac.md
@@ -0,0 +1,182 @@
+---
+title: 'VTEX Support - APAC'
+id: 4tHKlUwXgjW8ebnCxd6COc
+status: PUBLISHED
+createdAt: 2024-04-29T23:32:23.667Z
+updatedAt: 2024-04-30T11:02:29.768Z
+publishedAt: 2024-04-30T11:02:29.768Z
+firstPublishedAt: 2024-04-29T23:36:32.127Z
+contentType: tutorial
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: vtex-support-apac
+locale: en
+legacySlug: vtex-support-apac
+subcategory: 
+---
+
+This article presents the availability, SLA, and additional support resources available to customers served by our offices in **Asia-Pacific Region.** For a broader perspective of our global support resources, see: [How does VTEX support work?](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe)
+
+## Availability
+Our regular support hours are Monday through Friday, from 9am GMT+8 to 7pm GMT+8. Our average first response time varies according to ticket urgency, as seen in the table below.
+
+| **Ticket urgency** | **Average first response time** | **Average next response time** | **Pausable Update** | **Agent Work Time**
+| -----|----- |----- |
+| **Low**   | 8 hours  | 18 hours | 45 hours | 45 hours
+| **Normal** | 8 hours hours | 16 hours | 45 hours | 45 hours
+| **High** | 4 hours | 12 hours | 45 hours | 45 hours
+| **Urgent**| 3 hours | 10 hours | 45 hours | 45 hours
+
+Keep in mind that our first response time calculation is based on working hours. The criteria for ticket urgency are defined in the section below.  
+
+<div class="alert alert-warning">
+Emergency support will be available <b>exclusively</b> for Urgent requests and provided via <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Zendesk tickets</a>. Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in <a href="#ticket-urgency">Ticket Urgency</a>.
+</div>
+
+## Ticket urgency
+
+Urgent tickets report critical problems that have a direct impact on sales. The table below lists the scenarios we consider when classifying ticket urgency.
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <thead>
+        <tr class="bb b--muted-3">
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Scenario</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th>
+        </tr>
+    </thead>
+    <tbody>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">VTEX Platform Unavailable</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Storefront or Admin completely down</li>
+                <li>Open incident in our <a href="https://status.vtex.com" target="_blank">status page</a></li>
+              </ul>
+            </td>
+        </tr>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">Checkout Unavailable</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Shipping calculations preventing orders from being placed</li>
+                <li>Taxes not being calculated preventing orders from being placed</li>
+                <li>Shopping cart or checkout pages not loading (completely down)</li>
+              </ul>
+            </td>
+        </tr>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">Unable to Fulfill Order</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Orders status isn’t being updated</li>
+                <li>Order feed or hook isn’t working</li>
+              </ul>
+            </td>
+        </tr>
+        <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 15rem;">Store Usability Unavailable</td>
+            <td class="t-body pa5" style="min-width: 15rem;">
+              <ul>
+                <li>Unable to add to cart</li>
+                <li>Unable to register on the site</li>
+                <li>Onsite search not responding</li>
+              </ul>
+            </td>
+        </tr>
+    </tbody>
+</table>
+
+## Ticket Priorities
+
+The following table lists the scenarios we consider when ranking ticket priority based on how the ticket forms were filled out.  
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <thead>
+        <tr class="bb b--muted-3">
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Source</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Type</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Users impacted</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Impact</th>
+            <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Priority</th>
+        </tr>
+    </thead>
+    <tr class="bb b--muted-3">
+        <td>Financial
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td rowspan="8" >Technical
+        </td>
+        <td>Question
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>Task
+        </td>
+        <td>
+        </td>
+        <td>
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td rowspan="6" >Incident
+        </td>
+        <td rowspan="3" >Internal
+        </td>
+        <td>Low
+        </td>
+        <td>Low
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>Moderate
+        </td>
+        <td>Normal
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>High
+        </td>
+        <td>High
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td rowspan="3" >External / All
+        </td>
+        <td>Low
+        </td>
+        <td>Normal
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>Moderate
+        </td>
+        <td>High
+        </td>
+    </tr>
+    <tr class="bb b--muted-3">
+        <td>High
+        </td>
+        <td>Urgent
+        </td>
+    </tr>
+</table>
+
+The priority of a ticket may change over time, based on VTEX's analysis of the impact of the request. You can check the priority of your open requests through the [support panel](https://support.vtex.com/hc/en/requests).
+
diff --git a/docs/tutorials/en/warehouse.md b/docs/tutorials/en/warehouse.md
index 96feb8b9a..e493ca86c 100644
--- a/docs/tutorials/en/warehouse.md
+++ b/docs/tutorials/en/warehouse.md
@@ -20,7 +20,7 @@ On the VTEX platform, warehouses are physical storage spaces for goods sold by t
 
 It is important to pay attention to the inventory logistics and how the settings on the VTEX platform affect order delivery. From the warehouse, orders are sent to loading docks, where they are picked up by the carriers. 
 
-![EstrategiaEnvio_EN](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/950f5a0342bba5b62dcd0bee100e8a71/Frame_2__3_.svg)
+![EstrategiaEnvio_EN](//images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/950f5a0342bba5b62dcd0bee100e8a71/Frame_2__3_.svg)
 
 <div class="alert alert-info">
 The carrier that will deliver a certain order is defined by the <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">shipping policy</a>. For a carrier to be selected to deliver the order, its shipping policy must meet the conditions required for the delivery of the order. The shipping policy is linked to the warehouse by the Loading dock.
diff --git a/docs/tutorials/en/web-application-firewall-waf.md b/docs/tutorials/en/web-application-firewall-waf.md
new file mode 100644
index 000000000..5b530990f
--- /dev/null
+++ b/docs/tutorials/en/web-application-firewall-waf.md
@@ -0,0 +1,58 @@
+---
+title: 'Web Application Firewall (WAF)'
+id: 6BZYLlU03ws72iqIFF6jdn
+status: PUBLISHED
+createdAt: 2024-04-25T00:17:16.172Z
+updatedAt: 2024-04-30T15:03:41.186Z
+publishedAt: 2024-04-30T15:03:41.186Z
+firstPublishedAt: 2024-04-25T01:16:27.468Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: web-application-firewall-waf
+locale: en
+legacySlug: web-application-firewall-waf
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>This feature is part of <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
+</div>
+
+The Web Application Firewall (WAF) is a security layer designed to protect web applications by monitoring and filtering internet traffic.
+
+The WAF is aimed at HTTP (Hypertext Transfer Protocol) and HTTPS (HTTP Secure) communications, scanning inbound and outbound data to detect and block possible threats.
+
+![waf-en](//images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/19c4af7d54a4e27985a697270e5ea662/waf-en.png)
+
+The WAF's operation begins with the VTEX Security team defining [security rules](#security-rules) based on the analysis of information flow patterns. Based on these rules, the WAF continuously monitors web traffic. When it detects potentially harmful activity, it can block the traffic, thus preventing vulnerabilities in the web application.
+
+## Security rules
+
+Stores using VTEX Shield and choosing the WAF have the following security rules against threats:
+
+| Threat | Security rule |
+|---|---|
+| Remote File Inclusions (RFI) | Detects attempts to include files, usually via scripts on the web server. |
+| Directory Traversal | Verifies and validates file names provided by users, preventing unauthorized access to sensitive files and folders. |
+| Cross-Site Scripting (XSS) | Prevents the injection of client-side scripts into the pages viewed by visitors. |
+| File upload | Detects attempts to upload files to the web server. |
+| Evasion techniques | Protects against some coding techniques used to bypass protection mechanisms. |
+| Unwanted access | Detects attempts to access admin or vulnerable pages, bots, and security scanning tools. |
+| Identified attacks | Prevents many common attacks and known vulnerabilities that must be blocked.   |
+| IP filter | Checks a list of IP addresses to view their access permissions or blocks. |
+| Tor network blocking | Prevents access to the site using the Tor browser. |
+
+## Requesting WAF activation
+
+To request WAF activation for your store, please contact [VTEX Support](https://help.vtex.com/en/support). Include the following information in the ticket:
+
+* URLs to be added to the WAF.
+* Name and contact information of the point of contact with the VTEX Security team during the activation process.
+* Provider: To access the WAF, all store URL traffic must go through [Azion](https://www.azion.com/), the provider currently used by VTEX. If that's not the case, a procedure must be followed with the VTEX Traffic team, which can take between 1 and 2 weeks.
+
+After submitting the request, the deadline for activating the WAF on the store URLs is 4 weeks, plus the period needed to migrate to [Azion](https://www.azion.com/), if applicable.
+
+## Learn more
+
+* [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh)
diff --git a/docs/tutorials/en/web-page-performance.md b/docs/tutorials/en/web-page-performance.md
index 8a05ef0fd..5dfa2cbab 100644
--- a/docs/tutorials/en/web-page-performance.md
+++ b/docs/tutorials/en/web-page-performance.md
@@ -25,7 +25,7 @@ Web Page Performance brings Google's [PageSpeed Insights](https://developers.goo
 
 Although the Web Page Performance dashboard offers the same features as Google's PageSpeed Insights tool, it is only on the VTEX Admin that merchants will be able to add multiple URLs and assess them constantly. 
 
-![Web page performance Dash EN](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
+![Web page performance Dash EN](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
 
 ## Why should you track a web page's performance?
 
@@ -108,7 +108,7 @@ Note that the top 10 most accessed pages in your ecommerce cannot be deleted. Yo
 
 ## Core Web Vitals
 
-![Core web vitals EN](https://images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/b135473eb67bc50d6d504f74da8bf111/Screen_Shot_2022-06-29_at_16.00.41.png)
+![Core web vitals EN](//images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/b135473eb67bc50d6d504f74da8bf111/Screen_Shot_2022-06-29_at_16.00.41.png)
 
  For each URL, the Web Page Performance page displays the score of [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals) for that web page. 
 
diff --git a/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md b/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
index c4df83b67..a26d02ff6 100644
--- a/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
+++ b/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
@@ -19,7 +19,7 @@ By accessing the section __All orders__, in __Orders management__, it is possibl
 
 The column __Origin__ indicates where the order came from, distinguishing each other in two possible origins: __Marketplace__ and __Fulfillment__.
 
-![orders-list-origin-en](https://images.ctfassets.net/alneenqid6w5/3uvgTmIP1uEnAs0E4idyvb/832dd7e9618de51ffd8d2c56ab988f53/oders-list-origin-en.png)
+![orders-list-origin-en](//images.ctfassets.net/alneenqid6w5/3uvgTmIP1uEnAs0E4idyvb/832dd7e9618de51ffd8d2c56ab988f53/oders-list-origin-en.png)
 
 
 ## Marketplace
diff --git a/docs/tutorials/en/what-are-templates.md b/docs/tutorials/en/what-are-templates.md
index 5b20511eb..a69059c98 100644
--- a/docs/tutorials/en/what-are-templates.md
+++ b/docs/tutorials/en/what-are-templates.md
@@ -32,7 +32,7 @@ In addition to these two basic types, there is also a subdivision of the __page
 
 And speaking of organization, you will find all templates in **Storefront > Layout > CMS**, gathered in folders according to their type (HTML or Shelves). __Sub Templates__ are in the folder of the same name, which is inside the __HTML Templates__ directory. There, you will be able to create new templates and edit the ones that already exist.
 
-![cms](https://images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
+![cms](//images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
 
 ### Related articles
 - [What is CMS?](/en/tutorial/what-is-cms)
diff --git a/docs/tutorials/en/what-customized-payments-are-available-in-latin-america.md b/docs/tutorials/en/what-customized-payments-are-available-in-latin-america.md
index 7c514cb4b..35c12fd49 100644
--- a/docs/tutorials/en/what-customized-payments-are-available-in-latin-america.md
+++ b/docs/tutorials/en/what-customized-payments-are-available-in-latin-america.md
@@ -1,10 +1,10 @@
 ---
 title: 'What customized payments are available in Latin America?'
 id: 6plXudxQJiwaE0key20Yoe
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.217Z
-updatedAt: 2019-12-31T15:29:09.442Z
-publishedAt: 2019-12-31T15:29:09.442Z
+updatedAt: 2024-03-19T12:09:37.330Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T21:58:52.021Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md b/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
index e55b07296..8b0f7fd03 100644
--- a/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
+++ b/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
@@ -24,4 +24,4 @@ When configuring a **Buy one and Get one** promotion, it’s possible to **Activ
 For both scenarios it is necessary to fill out the maximum selectable quantity. With the **active** gift multiplier, choose the **maximum quantity** of gifts for the condition. For the **inactive** gift multiplier, the quantity is **always 1**.
 
 
-![ativar-multiplicador-brinde en](https://images.ctfassets.net/alneenqid6w5/42NpoBzyXCuagoceC0IAgQ/15fd07baa0eddbd1086831ec6e9440b7/gift_multi_en.png)
+![ativar-multiplicador-brinde en](//images.ctfassets.net/alneenqid6w5/42NpoBzyXCuagoceC0IAgQ/15fd07baa0eddbd1086831ec6e9440b7/gift_multi_en.png)
diff --git a/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md b/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
index df8401eb0..fb472c171 100644
--- a/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
+++ b/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
@@ -33,7 +33,7 @@ To learn how to access the orders that were considered for revenues calculation,
 All financially approved orders will receive this status, which can be seen in the orders management module:
 
 
-![image (2)](https://images.ctfassets.net/alneenqid6w5/1Q14q5mtiayBLRBSupsKGs/53c5555a68359b9fd3dd882336beccb7/image__2_.png)
+![image (2)](//images.ctfassets.net/alneenqid6w5/1Q14q5mtiayBLRBSupsKGs/53c5555a68359b9fd3dd882336beccb7/image__2_.png)
 
 
 To access this module, follow the step by step below:
diff --git a/docs/tutorials/en/what-is-a-franchise-account.md b/docs/tutorials/en/what-is-a-franchise-account.md
index 74728ec9c..4ddd9587c 100644
--- a/docs/tutorials/en/what-is-a-franchise-account.md
+++ b/docs/tutorials/en/what-is-a-franchise-account.md
@@ -3,8 +3,8 @@ title: 'What is a franchise account?'
 id: kWQC6RkFSCUFGgY5gSjdl
 status: PUBLISHED
 createdAt: 2021-10-13T20:38:07.014Z
-updatedAt: 2023-05-31T15:20:29.177Z
-publishedAt: 2023-05-31T15:20:29.177Z
+updatedAt: 2024-05-24T16:38:26.710Z
+publishedAt: 2024-05-24T16:38:26.710Z
 firstPublishedAt: 2021-10-13T20:57:01.457Z
 contentType: tutorial
 productTeam: Shopping
@@ -19,15 +19,15 @@ On the VTEX platform, you have the option to register physical stores, franchise
 
 The franchise account is associated with a main account. In the case of a brand that has several physical stores, franchisees or representatives, each of them can have a franchise account linked to the brand's main account. This allows them to deliver the products sold by the brand's ecommerce.
 
-![diagrama contas v2 - en](https://images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/bf1a348a817eb6a839db435d5dce1a9c/diagrama_contas_v2_-_en.png)
+![diagrama contas v2 - en](//images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/bf1a348a817eb6a839db435d5dce1a9c/diagrama_contas_v2_-_en.png)
 
 In this article, we will cover the following topics:
 
 - [Characteristics of the franchise account](#characteristics-of-the-franchise-account)
 - [Relationship between franchise account and White Label Seller](#relationship-between-franchise-account-and-white-label-seller)
 - [Franchise account configuration](#franchise-account-configuration)
-    -  [Pricing](#pricing)    
-    -  [Payments](#payments)
+  - [Pricing](#pricing)
+  - [Payments](#payments)
 - [Request the creation of a franchise account](#request-the-creation-of-a-franchise-account)
 
 ## Characteristics of the franchise account
@@ -38,7 +38,7 @@ In addition, when using the franchise account you can manage prices and payment
 
 A franchise account does not have its own website. Consumers browse directly on the main account website, which functions as a marketplace in this situation. Customer data is stored in the Master Data of the main account.
 
-![diagrama admin contas - en](https://images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/34a3ac170c1d3f7db9f4f03d27fa2a03/diagrama_admin_contas_-_en.png)
+![diagrama admin contas - en](//images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/34a3ac170c1d3f7db9f4f03d27fa2a03/diagrama_admin_contas_-_en.png)
 
 ## Relationship between franchise account and White Label Seller
 
@@ -57,7 +57,7 @@ As these concepts are independent, it is <strong>eventually</strong> possible th
 
 ## Franchise account configuration
 
-You can access and configure the [Logistics](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/7k4SWtm3EIvLQ3aGXWC07), [Order management](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa), [Prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP),[Payments](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG) and [Promotions & Taxes](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR) modules directly in the Admin of each of the franchise accounts or using [VTEX APIs](https://developers.vtex.com/vtex-rest-api/reference/get-to-know-vtex-apis).
+You can access and configure the [Logistics](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/7k4SWtm3EIvLQ3aGXWC07), [Order management](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa), [Prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP),[Payments](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG) and [Promotions &amp; Taxes](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR) modules directly in the Admin of each of the franchise accounts or using [VTEX APIs](https://developers.vtex.com/vtex-rest-api/reference/get-to-know-vtex-apis).
 
 To access the Admin of each franchise account, enter the URL `{{franchiseaccountname}}.myvtex.com/admin`, replacing the `{{franchiseaccountname}}` with the name of the franchise account you wish to manage.
 
@@ -73,6 +73,11 @@ In order for the franchise account to use the prices configured in the main acco
 
 To configure specific prices for the franchise account, you must deselect the option **Inherit prices from parent account** in the Settings of the **Prices** module of the franchise account, as described in [this article](https://help.vtex.com/en/tutorial/price-configuration--3hbBtCzNUBrj8GaWgCtSWN#price-general-settings). In addition, it is necessary to configure the desired prices in the [Prices module](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) or via the [Pricing API](https://developers.vtex.com/vtex-rest-api/reference/pricing-api-overview).
 
+When prices vary across franchise accounts, you should [configure regionalization](https://help.vtex.com/en/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw?&utm_source=autocomplete) to ensure a consistent shopping experience. 
+By adopting regionalization, you can request the customer postal code before they navigate your store.This will allow you to display the products and prices available to their franchise account before proceeding to checkout.
+If regionalization is not implemented, a certain product price may be displayed in the store, but when the customer proceeds to checkout and enters their postal code, the price might differ for the franchise account fulfilling the order, resulting in another price.
+This discrepancy occurs because the catalog with the lowest price is prioritized during store navigation. However, at checkout, if the franchise account with the lowest price does not have the product in stock, the seller that has the product available will be selected, and the price will adjust to that seller's price.
+
 ### Payments
 
 #### Using the payment methods of the main account
@@ -92,7 +97,7 @@ Once you have [changed this configuration](#configuring-payment-methods-specific
 VTEX offers split payment solutions that can make the distribution of receivables to sellers automatic. For more information, please refer to the article about [Split payment](https://help.vtex.com/en/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx).
 
 <div class="alert alert-warning">
-<p>If you want to implement VTEX Sales App in your physical stores, we do not recommend setting up specific payment methods for franchise accounts. Ideally, franchise accounts should use the payment methods of the main account to avoid payment conflicts.</p>
+<p>If you wish to implement the VTEX Sales App, it is necessary for physical stores to use the payment methods from the main account.</p>
 </div>
 
 ## Request the creation of a franchise account
@@ -110,6 +115,6 @@ If the number of accounts is greater than 10, please include them in an attached
 
 ## Learn more
 
--	[Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4)
--	[Choosing between standard account, franchise account or Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78)
+- [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4)
+- [Choosing between standard account, franchise account or Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78)
 
diff --git a/docs/tutorials/en/what-is-a-service.md b/docs/tutorials/en/what-is-a-service.md
index ff149d07e..9ab1fb95f 100644
--- a/docs/tutorials/en/what-is-a-service.md
+++ b/docs/tutorials/en/what-is-a-service.md
@@ -3,8 +3,8 @@ title: 'What is a Service?'
 id: 46Ha8CEEQoC6Y40i6akG0y
 status: PUBLISHED
 createdAt: 2018-02-16T13:35:47.291Z
-updatedAt: 2020-09-10T14:25:34.223Z
-publishedAt: 2020-09-10T14:25:34.223Z
+updatedAt: 2023-11-16T17:24:14.877Z
+publishedAt: 2023-11-16T17:24:14.877Z
 firstPublishedAt: 2018-02-16T17:24:14.979Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,5 +25,5 @@ If your purchased product is a Brazilian National Team Shirt, the name of your s
 
 ### Related articles
 - [What is an attachment?](/en/tutorial/what-is-an-attachment)
-- [Registering an attachment](/en/tutorial/registering-an-attachment)
+- [Registering an attachment](/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU)
 - [How to create a service for a SKU](/en/tutorial/creating-a-service-for-a-sku)
diff --git a/docs/tutorials/en/what-is-a-transaction.md b/docs/tutorials/en/what-is-a-transaction.md
index ddf03876e..7876632a0 100644
--- a/docs/tutorials/en/what-is-a-transaction.md
+++ b/docs/tutorials/en/what-is-a-transaction.md
@@ -1,10 +1,10 @@
 ---
 title: 'What is a transaction?'
 id: 36vMP5PES4oUWMWQuskIQ6
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-02-23T16:09:38.585Z
-updatedAt: 2020-11-27T19:39:37.153Z
-publishedAt: 2020-04-28T19:07:01.620Z
+updatedAt: 2023-09-28T16:00:07.059Z
+publishedAt: 2023-09-28T16:00:07.059Z
 firstPublishedAt: 2018-02-26T20:24:17.085Z
 contentType: tutorial
 productTeam: Financial
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 The movement that money makes when exchanged for a product or service is what we call __transaction__. Thus, payment is only one step in a process that involves an intense flow of information exchange between several parties: [gateways](/en/tutorial/what-is-a-payment-gateway), [sub-acquirers](/en/tutorial/what-is-a-sub-acquirer) and/or [acquirers](/en/tutorial/what-is-an-acquirer), [brands](/en/tutorial/what-is-a-credit-card-brand) and [issuing banks](/en/tutorial/what-is-the-issuing-bank).
 
-In a VTEX store, a transaction starts every time a user chooses a [payment condition](/en/tutorial/difference-between-payment-methods-and-payment-conditions) and closes their order. From there, the purchase data is sent for the validation of each of the members involved in this process. You can track each step of the [transaction flow](/en/faq/transaction-flow-in-pci-gateway) on the Payments. With this module, you accurately visualize the status of a payment through each status.
+In a VTEX store, a transaction starts every time a user chooses a [payment condition](/en/tutorial/difference-between-payment-methods-and-payment-conditions) and closes their order. From there, the purchase data is sent for the validation of each of the members involved in this process. You can track each step of the [transaction flow](/en/tutorial/transaction-flow-in-payments) on the Payments. With this module, you accurately visualize the status of a payment through each status.
 
 ### Related articles
 - [What is a payment gateway?](/en/tutorial/what-is-a-payment-gateway)
@@ -26,4 +26,4 @@ In a VTEX store, a transaction starts every time a user chooses a [payment condi
 - [What is a credit card brand?](/en/tutorial/what-is-a-credit-card-brand)
 - [What is the issuing bank?](/en/tutorial/what-is-the-issuing-bank)
 - [Difference between payment methods and payment conditions](/en/tutorial/difference-between-payment-methods-and-payment-conditions)
-- [Transaction flow in Payments ](https://help.vtex.com/en/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ "Transaction flow in Payments")
+- [Transaction flow in Payments](https://help.vtex.com/en/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ "Transaction flow in Payments")
diff --git a/docs/tutorials/en/what-is-an-affiliate.md b/docs/tutorials/en/what-is-an-affiliate.md
index 2298c886d..d66a5ffdc 100644
--- a/docs/tutorials/en/what-is-an-affiliate.md
+++ b/docs/tutorials/en/what-is-an-affiliate.md
@@ -3,8 +3,8 @@ title: 'What is an affiliate'
 id: 4bN3e1YarSEammk2yOeMc0
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:48.620Z
-updatedAt: 2022-10-05T18:24:46.905Z
-publishedAt: 2022-10-05T18:24:46.905Z
+updatedAt: 2024-05-23T16:09:45.545Z
+publishedAt: 2024-05-23T16:09:45.545Z
 firstPublishedAt: 2019-01-24T22:01:57.938Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/en/what-is-an-e-wallet.md b/docs/tutorials/en/what-is-an-e-wallet.md
index 23d168fbc..1ab423da5 100644
--- a/docs/tutorials/en/what-is-an-e-wallet.md
+++ b/docs/tutorials/en/what-is-an-e-wallet.md
@@ -1,10 +1,10 @@
 ---
-title: 'What is an e-wallet?'
+title: 'What is an ewallet?'
 id: 4v5wcOe4A0SiaimWM2cU60
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:38.294Z
-updatedAt: 2019-12-31T15:26:35.284Z
-publishedAt: 2019-12-31T15:26:35.284Z
+updatedAt: 2023-09-26T15:16:20.294Z
+publishedAt: 2023-09-26T15:16:20.294Z
 firstPublishedAt: 2019-01-24T22:05:07.777Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: what-is-an-e-wallet
 subcategory: 2Xay1NOZKE2CSqKMwckOm8
 ---
 
-A digital wallet (also called an e-wallet) is a secure environment where bank and/or credit card information can be stored. This information is encrypted in the system and, when accessed by its owner, can be used to make purchases on the internet.
+A digital wallet (also called an ewallet) is a secure environment where bank and/or credit card information can be stored. This information is encrypted in the system and, when accessed by its owner, can be used to make purchases on the internet.
 
 Buying with a digital wallet offers more security for the user since they don't need to enter their payment information at the store checkout. Instead, the user is redirected to the digital wallet environment, where they must undergo authentication steps.
 
diff --git a/docs/tutorials/en/what-is-deposit-slip.md b/docs/tutorials/en/what-is-deposit-slip.md
index 0bebc5cf4..7bb232399 100644
--- a/docs/tutorials/en/what-is-deposit-slip.md
+++ b/docs/tutorials/en/what-is-deposit-slip.md
@@ -3,8 +3,8 @@ title: 'What is Deposit Slip'
 id: 5zcak00O9G2KqoysQggus6
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:35.451Z
-updatedAt: 2019-12-31T15:25:20.325Z
-publishedAt: 2019-12-31T15:25:20.325Z
+updatedAt: 2024-03-18T13:03:11.449Z
+publishedAt: 2024-03-18T13:03:11.449Z
 firstPublishedAt: 2019-01-24T22:10:45.867Z
 contentType: tutorial
 productTeam: Financial
@@ -23,6 +23,13 @@ To pay with Deposit Slip, the user must choose this payment condition at the che
 To make the purchase effective, the user must go to one of the accredited places and pay the value of the document. This payment can be made in cash or with credit cards.
 
 ## How to accept deposit slips in your store
-Your VTEX store can accept payments with Deposit Slip, as long as it operates in Mexico and is registered in Citibanamex. This Mexican bank has integration with our platform and can be configured in your store.
 
-To learn how to configure the Banamex connector (responsible for communicating with Citibanamex), visit [this Help article](/en/tutorial/setting-up-banamex-gateway).
+To check the providers that carry out transactions with Ficha Depósito and configure them in your store, follow the steps below:
+
+1. In the VTEX Admin, go to __Store Settings > Payment > Settings__, or type __Settings__ in the search bar at the top of the page.
+2. On the __Payment Conditions__ tab, click the `+` button.
+3. Click __FichaDeposito__.
+4. Activate the condition in the __Status__ field.
+5. Select the available provider options and make the necessary settings for each of them.
+6. Click `Save`.
+
diff --git a/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md b/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
index 805c8680c..a8c0217ea 100644
--- a/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
+++ b/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
@@ -1,10 +1,10 @@
 ---
 title: 'What is the role of financial agents in the payment flow of an application in Brazil?'
 id: 1dyPJ3gQCCO4ea2o6OMgCi
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-10-11T19:08:49.654Z
-updatedAt: 2020-11-27T19:40:35.496Z
-publishedAt: 2019-12-31T15:27:52.279Z
+updatedAt: 2024-03-18T18:55:40.724Z
+publishedAt: 2024-03-18T18:55:40.724Z
 firstPublishedAt: 2017-10-11T19:34:43.203Z
 contentType: tutorial
 productTeam: Financial
@@ -21,7 +21,7 @@ In this article, we will clarify the concepts of acquirer, sub-aquirer, gateway,
 
 ## Gateway
 
-A gateway (also called payment gateway) is a __system that transmits data from purchases made in your store at checkout__ to companies such as Braspag e Mundipagg.
+A gateway (also called payment gateway) is a __system that transmits data from purchases made in your store at checkout__.
 
 As the first player in the flow, it's responsible for sending this information to acquirers, card brands and [issuing banks](https://help.vtex.com/en/tutorial/what-is-the-issuing-bank?locale=en "What is the Issuing Bank?") then obtain a response about the continuation of the process or its cancellation. In other words, the gateway sends data and receives responses so that you know whether or not a particular purchase should be confirmed, showing whether the payment was approved or not. 
 
@@ -31,7 +31,6 @@ By activating the [connectors](https://help.vtex.com/en/tutorial/what-is-the-con
 
 VTEX platform has its own [PCI](https://help.vtex.com/en/tutorial/what-is-the-pci-ssc?locale=en "What is the PCI SSC") certified gateway, which means that data from any payment made in your store is protected according to the highest security standards.
 
-
 ## Acquirer
 
 An acquirer (also called a creditor) is a __company that specializes in processing payments__, meaning that it processes credit or debit card payments on behalf of a merchant.  Through its network of accredited partners (or acquiring network), it enables a store to offer various payment conditions to its customers.
@@ -45,7 +44,7 @@ When everything is in order and a purchase is authorized by the other players wi
 ## Sub-acquirer
 
 A sub-acquirer is a company that processes payments and transmits the generated data to the other players involved in the [payment flow](https://help.vtex.com/en/tutorial/credit-card-basic-payment-flow "Credit Card - Basic payment flow"). Its role is similar to that of an acquirer, but it doesn't completely replace it due to the lack of autonomy to perform all the funcilnatilies of an acquirer. 
- 
+
 A sub-acquirer can therefore __be understood as a kind of intermediary player between acquirer and store__. Some examples of sub-acquirers are: PagSeguro e Paypal.
 
 The main advantages of a sub-acquirer are its low implementation cost , own anti-fraud system and ease of integration which makes this a very attractive solution for small stores. On the other hand,  the choice of using the sub-acquirer may jeopardize the retailer's profits because of the high rates charged for each transaction (greater than the acquirers). 
@@ -60,23 +59,20 @@ These brands keep a close relationship with the acquirers to guarantee the accep
 
 In the [credit card payment flow](https://help.vtex.com/en/tutorial/credit-card-basic-payment-flow "Credit Card - Basic payment flow"), the brand receives the information of the purchase made in your store from the acquirer. It then validates the conditions (such as the number of installments) and sends the data to the issuing bank, which verifies that the buyer has sufficient limit available. Hence, the card brand serves  to both regulate the use of the card and as a bridge between the acquirer and the consumer's bank.
 
-
 ## Issuing Bank
 
 The issuing bank is the financial institution responsible for the payment method, be it by bank slip, debit or credit card. It is the one who, when receiving the data of a purchase made in your store, will either authorize the sale or not (depending on the  available credit limit or available monetary resources in the user's account). If everything is OK, the bank collects the value.
 
 This concept is important because it allows you to set up [special conditions](https://help.vtex.com/en/tutorial/special-conditions?locale=en "Configuring payment special conditions") for payments made through specific banks. In addition, for registered payment tickets, each bank has its own form of issuance. In addition, in order to implement this configuration, you need to know how the chosen issuing bank process is and follow the instructions in [this article](https://help.vtex.com/en/tutorial/how-do-i-configure-registered-payment-ticket?locale=en "Configuring a registered bank slip"). Some examples of Issuing Banks are: Itau, Santander, Bradesco e Citibank.
 
-
 ## Anti-fraud
 
 Anti-fraud is a system specialized in analyzing the purchases made on websites, in order to identify fraudulent transactions.
- 
+
 It collects data about the behavior of users and compares them with suspicious patterns to then approve or deny the order. The anti-fraud therefore adds an extra layer of security to your store.
- 
-At VTEX, the payment operator first approves the purchase and then the anti-fraud assesses the order. If everything goes OK, it follows its normal flow. Some examples of anti-fraud are: ClearSale and Konduto. 
 
----
+At VTEX, the payment operator first approves the purchase and then the anti-fraud assesses the order. If everything goes OK, it follows its normal flow. Some examples of anti-fraud are: ClearSale and Konduto. 
 
+<div class="alert alert-info">
 It is important to emphasize that each business depends on specific factors that influence the decision of which modality to use. There are several variables that can determine the choice of a payment method and what your financial flow will be. It is critical, therefore, to keep the actual needs and purposes of the retailer and desired project in mind.
-
+</div>
diff --git a/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md b/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md
index 33be7b580..4e45d0b7f 100644
--- a/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md
+++ b/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md
@@ -25,7 +25,7 @@ __The three stages of logistics are represented by the following structure:__
 
 __They can be illustrated by this flow:__
 
-![EN Conceitos Logistics](https://images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/614cb763d596936df13033e89067f7f4/EN_Conceitos_Logistics.png)
+![EN Conceitos Logistics](//images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/614cb763d596936df13033e89067f7f4/EN_Conceitos_Logistics.png)
 
 ## Warehouse
 It's the physical space used to store the goods of an e-commerce, functioning as the repository of the items of your store.
diff --git a/docs/tutorials/en/what-is-the-difference-between-product-and-sku.md b/docs/tutorials/en/what-is-the-difference-between-product-and-sku.md
index 5daec5cf6..ffb762e49 100644
--- a/docs/tutorials/en/what-is-the-difference-between-product-and-sku.md
+++ b/docs/tutorials/en/what-is-the-difference-between-product-and-sku.md
@@ -3,8 +3,8 @@ title: 'What is the difference between product and SKU?'
 id: 5yhABFDOpyiUcicce2W4CM
 status: PUBLISHED
 createdAt: 2018-01-26T17:49:48.383Z
-updatedAt: 2022-06-08T15:45:08.032Z
-publishedAt: 2022-06-08T15:45:08.032Z
+updatedAt: 2023-07-17T13:15:51.969Z
+publishedAt: 2023-07-17T13:15:51.969Z
 firstPublishedAt: 2018-01-26T18:00:17.827Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,6 +27,4 @@ Structurally, first you define the product information and then you create your
 
 ## Learn more
 
-- [Registering a product](/en/tutorial/registering-a-product)
-
-- [Registering an SKU](/en/tutorial/registering-sku)
+- [Registering a product](https://help.vtex.com/en/tutorial/adding-products--tutorials_2567)
diff --git a/docs/tutorials/en/what-is-the-maximum-limit-of-promotions.md b/docs/tutorials/en/what-is-the-maximum-limit-of-promotions.md
index e107ebef0..2d764534d 100644
--- a/docs/tutorials/en/what-is-the-maximum-limit-of-promotions.md
+++ b/docs/tutorials/en/what-is-the-maximum-limit-of-promotions.md
@@ -1,10 +1,10 @@
 ---
-title: 'How many coupons, fees and promotions may I have in my store?'
+title: 'How many coupons, taxes and promotions may I have in my store?'
 id: frequentlyAskedQuestions_352
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:52.883Z
-updatedAt: 2021-02-01T15:43:04.116Z
-publishedAt: 2021-02-01T15:43:04.116Z
+updatedAt: 2023-07-10T18:00:19.469Z
+publishedAt: 2023-07-10T18:00:19.469Z
 firstPublishedAt: 2019-01-24T22:05:32.884Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,12 +15,12 @@ legacySlug: what-is-the-maximum-limit-of-promotions
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-Nowadays, we have a limitation on the number of active promotions, fees and coupons.
+Nowadays, we have a limitation on the number of active promotions, taxes and coupons.
 
 - [Promotions](/en/tutorial/como-criar-promocoes--tutorials_320): 100
-- [Fees](/en/tutorial/creating-surchargestaxes): 100
+- [Taxes](/en/tutorial/creating-surchargestaxes): 100
 - [Coupons](/en/tutorial/creating-a-coupon/): 50.000
 
-_Only active promotions, fees or  coupons will be accounted, which means that the filed promotions, fees or coupons will not be considered._
+Only active promotions, taxes or coupons are counted when calculating this limit, which means that archived promotions, taxes or coupons are not considered.
 
-Get in touch with VTEX in case you need to change any of these limits.
+If it is necessary to change any of these limits, please contact our [Support](https://help.vtex.com/en/support) to analyze the viability of the change.
diff --git a/docs/tutorials/en/what-is-the-pci-ssc.md b/docs/tutorials/en/what-is-the-pci-ssc.md
index bfdf2bfb2..180e03877 100644
--- a/docs/tutorials/en/what-is-the-pci-ssc.md
+++ b/docs/tutorials/en/what-is-the-pci-ssc.md
@@ -3,8 +3,8 @@ title: 'What is the PCI SSC'
 id: 4jo3Vkox3amSO2w4qIWa0E
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:48.373Z
-updatedAt: 2021-09-22T12:32:07.193Z
-publishedAt: 2021-09-22T12:32:07.193Z
+updatedAt: 2024-07-23T15:26:30.020Z
+publishedAt: 2024-07-23T15:26:30.020Z
 firstPublishedAt: 2019-01-24T22:12:41.627Z
 contentType: tutorial
 productTeam: Financial
@@ -21,4 +21,4 @@ It was founded by American Express, Discover Financial Services, JCB Internatio
 
 PCI SSC is a certification given by that institution, through which VTEX guarantees the safety of its services. It brings security information that we make available for the stores and your customers. 
 
-For more information, see the [VTEX PCI SSC certification category](https://secure.vtex.com/?an=VTEX).
+For more information, see the [VTEX PCI SSC certification category](https://vtex.com/us-en/compliance/certifications/).
diff --git a/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
index 1d635a630..7e8af8311 100644
--- a/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
@@ -31,7 +31,7 @@ The types include Banner, BannerDHTML Collection or HTML.
 
 To create a customized control tag, click on Add, enter a name, a tag name, and select the type.
 
-![cms-custom-elements EN / ES](https://images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
+![cms-custom-elements EN / ES](//images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
 
 <div class="alert alert-warning">
   <p><b>Warning:</b> do not create an HTML type control with an element <code>title</code>. This may interfere with your store operation.</p>
diff --git a/docs/tutorials/en/what-is-transparent-checkout.md b/docs/tutorials/en/what-is-transparent-checkout.md
index 6a423b2cd..c4d51069c 100644
--- a/docs/tutorials/en/what-is-transparent-checkout.md
+++ b/docs/tutorials/en/what-is-transparent-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'What is transparent checkout?'
 id: 2Y4ECegUmcYUggmck2GOwe
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-02-27T18:58:12.252Z
-updatedAt: 2020-11-27T19:39:49.137Z
-publishedAt: 2020-05-31T14:34:28.895Z
+updatedAt: 2023-07-20T18:06:08.385Z
+publishedAt: 2023-07-20T18:06:08.385Z
 firstPublishedAt: 2018-02-27T20:40:08.480Z
 contentType: tutorial
 productTeam: Shopping
@@ -15,7 +15,7 @@ legacySlug: what-is-transparent-checkout
 subcategory: 8AGXmtpbTqUE2KQu0Swwk
 ---
 
-Depending on the payment condition that the user chooses when making a purchase, he or she may be redirected to an external environment. A bank transfer (which requires access to internet banking) or the use of a solution such as Paypal (which requires the user to be logged in) are examples of payment methods that can generate this redirection.
+Depending on the payment condition that the user chooses when making a purchase, they may be redirected to an external environment. A bank transfer (which requires access to internet banking) or the use of a solution such as Paypal (which requires the user to be logged in) are examples of payment methods that can generate this redirection.
 
 The problem is that, at a time so critical to sales conversion as checkout, an extra step can be decisive for user decision making. Enters the __transparent checkout__, which eliminates the need for an extra step, making the shopping experience more fluid.
 
diff --git a/docs/tutorials/en/what-offline-payment-conditions-are-available-in-latin-america.md b/docs/tutorials/en/what-offline-payment-conditions-are-available-in-latin-america.md
index 79a500d92..66a444aa9 100644
--- a/docs/tutorials/en/what-offline-payment-conditions-are-available-in-latin-america.md
+++ b/docs/tutorials/en/what-offline-payment-conditions-are-available-in-latin-america.md
@@ -1,10 +1,10 @@
 ---
 title: 'What offline payment conditions are available in Latin America?'
 id: 2lXPwiH6KcsSMuWaoigueq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.602Z
-updatedAt: 2019-12-31T15:19:41.744Z
-publishedAt: 2019-12-31T15:19:41.744Z
+updatedAt: 2024-03-19T12:05:40.449Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:19.092Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md b/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md
index 4910f338f..ab3e0d2f0 100644
--- a/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md
+++ b/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md
@@ -3,8 +3,8 @@ title: 'What to do when my report does not reach my inbox?'
 id: 1zUBgmgkgMZyHyy0veR7Oj
 status: PUBLISHED
 createdAt: 2022-10-17T19:56:25.618Z
-updatedAt: 2023-03-28T23:24:48.040Z
-publishedAt: 2023-03-28T23:24:48.040Z
+updatedAt: 2024-06-11T16:48:56.974Z
+publishedAt: 2024-06-11T16:48:56.974Z
 firstPublishedAt: 2022-10-17T19:59:15.174Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: what-to-do-when-my-report-does-not-reach-my-inbox
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-At VTEX, each store can access a report on [data exports](/tutorial/exporting-data?locale=en) from [Master Data](/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw) - our module that gathers information about the customers of the store.
+At VTEX, each store can access a report on [data exports](https://help.vtex.com/en/tutorial/exporting-data--tutorials_1125) from [Master Data](https://help.vtex.com/en/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw) - our module that gathers information about the customers of the store.
 
 These reports are sent to the email owned by the person who requested the action. However, for reasons not concerning VTEX, such content may take longer than expected to reach the requester's inbox.
 
@@ -24,8 +24,9 @@ However, there is a way to extract this report manually by accessing Master Data
 Let's see how in the following step-by-step:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. Click __"Exportations"__.![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
-3. Make sure that the tab currently open is __"Applications"__.![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
-4. Under __"Export Status"__, click the report you want to download.
+2. Click __Exports__. ![exports-md](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/1ac3c2bd600edaac1440899274a8005b/exportaciones.png)
+3. Make sure that the tab currently open is __Applications__.
+4. Under __Export Status__, identify the row of the report you want to download.
+5. If the __Status__ is __Completed - Download__, click **Download** to download the file.
 
-With this, you'll be able access the content even if the original email has not arrived.
+With this, you will be able access the content even if the original email has not arrived.
diff --git a/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md b/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md
new file mode 100644
index 000000000..361aa6c9b
--- /dev/null
+++ b/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md
@@ -0,0 +1,96 @@
+---
+title: 'WhatsApp AI Campaigns management and details'
+id: q9JqDErMqGV4zvsYqkD4s
+status: PUBLISHED
+createdAt: 2024-06-25T11:58:05.514Z
+updatedAt: 2024-06-25T16:28:52.542Z
+publishedAt: 2024-06-25T16:28:52.542Z
+firstPublishedAt: 2024-06-25T16:11:51.825Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: whatsapp-ai-campaigns-management-and-details
+locale: en
+legacySlug: whatsapp-ai-campaigns-management-and-details
+subcategory: 4SC2gPmUH3cHD5HjGfQ5Vg
+---
+
+This page provides an overview of WhatsApp AI Campaigns management and details on the VTEX platform. It covers everything from configuration to monitoring performance metrics, helping you optimize the effectiveness of your campaigns and boost conversions.
+
+This article outlines how to manage and monitor your campaigns by:
+
+- [Selecting dates](#selecting-dates)
+- [Sending reports](#sending-reports)
+- [Editing campaigns](#editing-campaigns)
+- [Pausing campaigns](#pausing-campaigns)
+- [Viewing details of the Analytics dashboard](#viewing-details-of-the-analytics-dashboard)
+
+## WhatsApp AI Campaigns management
+
+The WhatsApp AI Campaigns page allows you to view data on Analytics and Active Campaigns.
+
+### Selecting dates
+
+Go through the specific days to see the messages triggered during each period.
+
+1. In the VTEX Admin, go to Promotions > WhatsApp Campaigns > Overview.
+2. Click on the date selector.
+3. Select the date you want to view the analytics data.
+
+### Sending reports
+
+1. In the VTEX Admin, go to Promotions > WhatsApp Campaigns > Overview.
+2. Click `Send Report` in the top right corner of the section.
+3. Enter the email address you want to receive the report.
+4. Click `Send Report`.
+
+The report sent by email will be a `csv` file with the following information:
+
+- **userId:** unique identifier of the user who made the purchase.
+- **deliveredReminderAt:** date and time when a reminder about the purchase was sent to the user.
+- **readReminderAt:** date and time when the user viewed the sent reminder.
+- **orderCreatedAt:** date and time when the order was created in the system.
+- **hasClickedOnReminder:** indicates whether the user clicked on the sent reminder or not.
+- **checkoutItems:** list of items that the user added to the cart during the checkout process.
+- **orderItems:** list of items that were actually purchased by the user.
+- **orderTotal:** total value of the order, summing the price of all purchased items.
+- **currency:** currency used for the payment of the order.
+- **orderFormId:** unique identifier of the order form used during the checkout.
+
+### Editing campaigns
+
+Once the campaign is configured, you can edit the language or the type of message you want to customize.
+
+1. In the VTEX Admin, go to Promotions > WhatsApp Campaigns > Overview.
+2. Click the <i class="fas fa-ellipsis-v" aria-hidden="true"></i> icon.
+3. Click `Edit`.
+4. Edit the information you want.
+5. Click `Confirm`.
+
+### Pausing campaigns
+
+To pause sending messages from a campaign, follow the steps below:
+
+1. In the VTEX Admin, go to Promotions > WhatsApp Campaigns > Overview.
+2. Click the <i class="fas fa-ellipsis-v" aria-hidden="true"></i> icon.
+3. Click `Pause`.
+4. Click `Confirm`.
+
+## Viewing details of the Analytics dashboard
+
+You can find information about your active campaigns in the VTEX Admin.
+
+![Visão geral-EN](//images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/0ec14467b481aeba99f2d0f3fc461ff4/Vis_o_geral-EN.png)
+
+Below are the details of the available metrics:
+
+- **Messages delivered:** Total number of messages that successfully reached the intended recipients without any delivery problems.
+- **Messages read:** Total number of messages opened by recipients, indicating audience engagement.
+- **Unique clicks:** Number of users who clicked the message buttons.
+- **Total clicks:** Total number of interactions using the buttons embedded in the messages, providing a quantitative measure of engagement.
+- **Total Conversions:** the total number of conversions that occur after the successful delivery of a message to a recipient. The total conversions are the sum of the two metrics below:
+      - **Assisted Conversions:** conversions that occur within 3 days after receiving the message.
+      - **Click-Through Conversions (CTC):** conversions that occur when users click on the message link and make a purchase within 15 days.
+- **Conversion total value:** Total order amount from conversions.
+- **Click-through conversion total value:** Total order amount from click-through conversions.
+
diff --git a/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md b/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md
index 010db0c56..98f79c281 100644
--- a/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md
+++ b/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md
@@ -22,4 +22,4 @@ But remember: a subscribers only appears in the listing after the payment is app
 1. Access the __Orders Management__ module.
 2. Click the __Subscriptions__ tab.
 
-![subscriptions EN](https://images.ctfassets.net/alneenqid6w5/jT7LGvlNOS2iQGIQIqEi/591dc39ef6d0f5824956f819817520fd/subscriptions_EN.png)
+![subscriptions EN](//images.ctfassets.net/alneenqid6w5/jT7LGvlNOS2iQGIQIqEi/591dc39ef6d0f5824956f819817520fd/subscriptions_EN.png)
diff --git a/docs/tutorials/en/which-security-certificates-may-be-added-to-my-store.md b/docs/tutorials/en/which-security-certificates-may-be-added-to-my-store.md
index ed75c5241..54a5034b7 100644
--- a/docs/tutorials/en/which-security-certificates-may-be-added-to-my-store.md
+++ b/docs/tutorials/en/which-security-certificates-may-be-added-to-my-store.md
@@ -1,10 +1,10 @@
 ---
 title: 'Which security certificates may be added to my store?'
 id: 29ivkiHbXqMIa8QMKCSQ2K
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:48.223Z
-updatedAt: 2019-12-31T15:23:12.479Z
-publishedAt: 2019-12-31T15:23:12.479Z
+updatedAt: 2024-03-11T13:21:15.878Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:15:04.845Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/en/white-label-seller.md b/docs/tutorials/en/white-label-seller.md
index b527b2066..53ba8b749 100644
--- a/docs/tutorials/en/white-label-seller.md
+++ b/docs/tutorials/en/white-label-seller.md
@@ -3,8 +3,8 @@ title: 'White label seller'
 id: 5orlGHyDHGAYciQ64oEgKa
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:34.034Z
-updatedAt: 2022-10-17T17:52:42.676Z
-publishedAt: 2022-10-17T17:52:42.676Z
+updatedAt: 2023-07-14T15:15:56.338Z
+publishedAt: 2023-07-14T15:15:56.338Z
 firstPublishedAt: 2019-01-24T22:03:52.175Z
 contentType: tutorial
 productTeam: Channels
@@ -48,3 +48,4 @@ To add a white label seller, this model must be provided for in your contract wi
 - [Selecting white label sellers](https://help.vtex.com/en/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa)
 - [Configuring a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb)
 - [Adding a seller](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392)
+- [Choosing between standard account, franchise account or Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78)
diff --git a/docs/tutorials/en/white-label-sellers-selection.md b/docs/tutorials/en/white-label-sellers-selection.md
index ceccf5d2d..e297c9365 100644
--- a/docs/tutorials/en/white-label-sellers-selection.md
+++ b/docs/tutorials/en/white-label-sellers-selection.md
@@ -112,13 +112,13 @@ If there is a tie between sellers on the best cost or time, the tiebreaker crite
 
 A customer added five SKUs to the shopping cart. Each of the sellers delivering in the customer's region (sellers A, B, C, and D) has only part of the ordered items in [stock](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139), as illustrated below: 
 
-![print_selecao_seller_white_label_1](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
+![print_selecao_seller_white_label_1](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
 
 The VTEX platform selects the seller that has available in stock the maximum quantity of the SKUs added to the shopping cart. In this case, it's Seller B, the only one that can deliver three SKUs. 
 
 After Seller B is selected, there are two SKUs still to be delivered. If a single seller were able to deliver both items, it would be a decisive selection factor because the objective is to find the lowest number of sellers to cover the shopping cart. However, Sellers A and C will be selected for delivering SKUs 1 and 4, as illustrated in the image below:
 
-![print_selecao_seller_white_label_2](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
+![print_selecao_seller_white_label_2](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
 
 In the first image, Seller C was able to deliver SKUs 3 and 4, and Seller D could deliver SKU 5. But Seller B has already been selected to deliver those items, so those SKUs will be disregarded in the following steps of the selection. This is represented by removing the arrow connecting Seller C to SKU 3 and Seller D to SKU 5.
 
@@ -128,7 +128,7 @@ The selection result for the delivery method is a combination between sellers A,
 
 A customer added five SKUs to the shopping cart and there are four sellers delivering in their region: sellers A, B, C, and D. None of them has all of the items in [stock](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139), as illustrated below:
 
-![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+![print_selecao_seller_white_label_3](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
 
 The VTEX platform selects the seller that has available in stock the highest number of the SKUs added to the shopping cart. Seller B and Seller D are able to deliver three items. Because both can deliver SKU 3, they are in competition.
 
@@ -141,11 +141,11 @@ Suppose Seller B has the cheapest shipping and Seller D has the fastest shipping
 
 - **Fastest shipping:** After Seller D is selected, SKUs 3 and 4 remain to be delivered. Seller C is able to deliver both, therefore it will be selected. The selection result is a combination of sellers D and C.
 
-![print_selecao_seller_white_label_4](https://images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
+![print_selecao_seller_white_label_4](//images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
 
 - **Cheapest shipping cost:** After Seller B is selected, SKUs 1 and 4 remain to be delivered. Since only Seller A is able to deliver SKU 1 and Seller C SKU 4, the selection result is a combination of sellers A, B, and C. 
 
-![print_selecao_seller_white_label_5](https://images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
+![print_selecao_seller_white_label_5](//images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
 
 In the images showing the fastest shipping and the cheapest shipping, the arrows pointing repeatedly to sellers which delivered SKUs covered by sellers B and D were removed. During the selection process, SKUs that are already covered are disregarded.
 
diff --git a/docs/tutorials/en/why-dont-marketplace-orders-integrate-with-my-store.md b/docs/tutorials/en/why-dont-marketplace-orders-integrate-with-my-store.md
new file mode 100644
index 000000000..0af13588a
--- /dev/null
+++ b/docs/tutorials/en/why-dont-marketplace-orders-integrate-with-my-store.md
@@ -0,0 +1,43 @@
+---
+title: "Why don't marketplace orders integrate with my store?"
+id: 275YvF8dyry5KmfY9epoET
+status: PUBLISHED
+createdAt: 2024-06-21T14:24:48.621Z
+updatedAt: 2024-06-21T14:50:25.468Z
+publishedAt: 2024-06-21T14:50:25.468Z
+firstPublishedAt: 2024-06-21T14:48:49.434Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: why-dont-marketplace-orders-integrate-with-my-store
+locale: en
+legacySlug: why-dont-marketplace-orders-integrate-with-my-store
+subcategory: 2LcLWCYaEm5qPmOuYUiKIS
+---
+
+**Tags:** orders, marketplace  
+**Keywords:** integration, marketplace, orders, SKU, inventory  
+
+When order integration errors occur between a marketplace and your store, messages are displayed on the page of each order with the error. The possible order integration errors are the following:  
+
+- Incomplete shipping information.  
+- Amount divergence.  
+- Invalid SKU ID.  
+- Unavailable inventory.  
+- Unavailable status.  
+- Carrier not registered in the ERP.  
+
+Check the status of order integration and messages by going to the VTEX Admin, and clicking **Marketplace > Connections > Orders** or typing **Orders** in the search bar.  
+
+## Solution
+
+To understand the meaning of the error and fix it, see the table below:  
+
+| **Error type** | **Meaning** | **Required action** |
+|:---:|:---:|:---:|
+| **Incomplete shipping information** | The delivery information is incomplete or incorrect. | Correct or complete the requested information following the documentation [Order flow and status.](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196) |
+|  <br>**Amount divergence** |  <br>The total amount of the order placed on the marketplace differs from the amount expected by the VTEX store, and this difference exceeds the percentage accepted by the VTEX store, or the Price Divergence rule is not configured.<br> <br>**Example**<br> <br>The total amount paid for the order on the marketplace was $311.77 USD, and the amount expected by the store was $313.61 USD. In other words, the order has a difference of $1.84 USD. | [Reprocess the order](https://help.vtex.com/en/tutorial/verificando-integracao-no-bridge#pedidos) or Configure the [Price Divergence rule](https://help.vtex.com/en/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW). |
+| **Invalid SKU ID** | The product IDs in the trade policy differ from those in the marketplace. | Change the SKU IDs in the marketplace to have the same codes as the products in the trade policy. |
+| **Unavailable inventory** | The SKU is not being displayed in the marketplace.<br> <br>See the full list of [Inventory integration errors with marketplaces.](https://help.vtex.com/en/tutorial/erros-de-integracao-de-estoque-com-marketplaces--32bcsv9Dx1Dtl0YQOwWDpc).<br>  | Apply the required fix based on the error identified in the documentation [Inventory integration errors with marketplaces.](https://help.vtex.com/en/tutorial/erros-de-integracao-de-estoque-com-marketplaces--32bcsv9Dx1Dtl0YQOwWDpc)<br>  |
+| **Unavailable status** | The product is available in your store, but the marketplace has blocked the item in the storefront. The order status will be displayed as **Unavailable**. | Contact the marketplace to release the order. |
+| **Carrier not registered in the ERP** | The carrier selected to deliver the product is not registered in the ERP.<br> <br>**Example**<br>A new carrier has been added to VTEX but has not been registered in the ERP. | Update the carrier information in the ERP as aligned with the information on the VTEX platform. |
diff --git a/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 774d2e5b0..36f575a75 100644
--- a/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -1,10 +1,10 @@
 ---
 title: 'Why was a customer able to register a CPF in a CNPJ field?'
 id: K6zJn8JFOKk5ON1XFB6ZJ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-10-17T19:22:31.749Z
-updatedAt: 2023-03-28T22:55:52.032Z
-publishedAt: 2023-03-28T22:55:52.032Z
+updatedAt: 2024-07-11T19:21:58.380Z
+publishedAt: 
 firstPublishedAt: 2022-10-17T19:43:17.176Z
 contentType: tutorial
 productTeam: Master Data
@@ -37,7 +37,7 @@ Follow the steps below to validate the information:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
 2. In the __Profile System__ box, click __Customers__.
-3. Select the option __Email__ and search the client's email.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+3. Select the option __Email__ and search the client's email.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 4. Click the customer record to access the profile details.
 
 In the __Contact__ section, you will see that the `Is Company?` option is filled with the value `No`. At the same time, in the section __Company Data__, you will see that the `Document Type` field is filled with the value `cnpj`.
diff --git a/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md b/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md
index fe1c71117..26d5fd9e9 100644
--- a/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md
+++ b/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md
@@ -1,10 +1,10 @@
 ---
-title: 'Writing an effective ticket to VTEX support'
+title: 'Best practices for opening a ticket to VTEX Support'
 id: 6u4ehk6F0ksuDgYuCbFDRX
 status: PUBLISHED
 createdAt: 2023-03-23T22:00:24.560Z
-updatedAt: 2023-03-24T18:24:48.580Z
-publishedAt: 2023-03-24T18:24:48.580Z
+updatedAt: 2024-04-22T23:02:06.481Z
+publishedAt: 2024-04-22T23:02:06.481Z
 firstPublishedAt: 2023-03-23T22:57:50.828Z
 contentType: tutorial
 productTeam: Others
@@ -15,20 +15,63 @@ legacySlug: writing-an-effective-ticket-to-vtex-support
 subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 ---
 
-All clients and partners have access to support provided by the [VTEX support](https://help.vtex.com/en/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe) team of specialists. To contact them, you must open a ticket through the ticket system.
+All clients and partners have access to support provided by the [VTEX support](https://help.vtex.com/en/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe)  team of experts. To contact them, you need to open a ticket.
 
-Our specialists are qualified to provide the best possible experience to solve every ticket. However, there are some guidelines you should follow when opening a ticket to ensure a faster and more streamlined process.
+Our specialists are qualified to provide the best possible Our experts are trained to provide the best experience possible to solve tickets. However, there are some guidelines you should follow when opening a ticket to ensure a faster and more streamlined process.
 
 Keep in mind that the more context you provide our specialists with, the quicker they'll be able to find a solution to your problem.
 
-This article aims to guide clients and partners on opening tickets with key information to speed up the investigation process for our specialists. It's divided into two sections:
+This article guides VTEX clients and partners to open tickets with relevant information to speed up the investigation process and reach a faster solution to their problems. It's divided into two sections:
 
-- [General guidelines](#general-guidelines)
-- [Key information per scenario](#key-information-per-scenario)
+- [Before opening a ticket](#Before-opening-a-ticket)
+- [Completing a ticket](#Completing-a-ticket)
 
-## General guidelines
+To learn how to open a ticket to VTEX Support, see [Opening tickets to VTEX support](https://help.vtex.com/en/tutorial/opening-chamados-para-o-tickets-to-vtex-support).
 
-When writing a ticket, please follow these guidelines to provide all the necessary information:
+## Before opening a ticket
+
+Before opening a ticket, check whether the problem is related to the store's customizations. If the source of the problem is a customization, you'll need to contact your customization team. Otherwise, open a ticket to VTEX Support.
+
+### Cart, Checkout and CMS Stores
+
+It is important to validate whether the scenario occurs without customizing the store. To run this test, disable customizations (JS and CSS) and try to reproduce the error. Learn more about this in the article[Blocking customizations to troubleshoot frontend issues](https://help.vtex.com/en/faq/como-bloquear-customizacoes-para-investigar-problemas-no-front-end-da-loja--5c1a4bvVK8rAvKLczhkCnY)  If the error persists, please contact our [Support team](https://help.vtex.com/support?/cultureInfo=pt-br).
+
+### Store Framework
+To check if the problem is associated with IO, follow the steps below:
+
+1.	Open the command prompt and log in to your store using the [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference).
+2. Access a development workspace by running the following command:
+    ```
+    vtex use {workspace}
+    ```
+3.	If your store has a Store Framework theme installed, uninstall it using the command below:
+    ```
+    vtex uninstall {theme}
+    ```
+
+    <div class="alert alert-info">
+    You can check for any installed themes using the <code>vtex list</code> command, which lists all the applications installed in the store.
+    </div>
+
+4.	Clone the default Store Framework theme on your computer.
+5.	At the command prompt, access the default theme folder.
+6.	Run the command:
+    ```
+    vtex link
+    ```
+    <div class="alert alert-warning"> If your store doesn't have the Reviews and Ratings app installed, you may receive an error when trying to create the link. To avoid this, remove this app from the `peer dependencies` list in the `manifest.json` file of the default theme. </div>
+
+7.	Access your workspace's storefront using the URL:
+    ```
+    https://{workspace}--{accountName}.myvtex.com
+    ```
+8.	Try to reproduce the error.
+
+If the error does not occur after blocking the files or in the default Store Framework theme, it means that the error is related to the site's customizations. To solve it, you should contact the team responsible for your store's frontend.
+
+## Completing a ticket
+
+To provide all the required details when completing a ticket, please follow the guidelines below:
 
 | Information | Guidelines |
 | ----------- | ----------- |
@@ -39,7 +82,7 @@ When writing a ticket, please follow these guidelines to provide all the necessa
 | Ticket scope | <p> - Do not address more than one problem in the same ticket. </p> <p> - Do not create more than one ticket for the same problem. </p> |
 | Priority | Check the proper priority according to the nature of the problem to apply the correct SLA. |
 
-## Key information per scenario
+### Key information per scenario
 
 You can open a ticket due to many scenarios. This section lists the most common ones, along with the basic information required to open a ticket for each.
 
@@ -48,7 +91,7 @@ You can adapt this information to your specific scenario and use it to guide you
 | Scenario | Information |
 | ----------- | ----------- |
 | Orders | <p> - Order ID or <code> orderForm </code>. </p> <p> - The order URL in <strong> Order Management </strong> or <strong> Bridge </strong> (for orders from marketplaces with native integrations). </p> |
-| Checkout | <p> - The shopping cart URL generated by <a href="https://help.vtex.com/en/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451">Cartman</a>. </p> <p> - SKU IDs and postal code for reproducing the cart. </p>
+| Checkout | <p> - The shopping cart URL generated by <a href="https://help.vtex.com/en/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451">Cartman</a>. </p> <p> - SKU IDs and postal code for reproducing the cart. </p> <p> - <a href= "https://help.vtex.com/pt/tutorial/generating-a-har-file--15xVlw8nuakk2k6Cao4k2Q"> HAR </a> for reproducing information about the error.
 | Logistics | <p> - Seller ID. </p> <p> - URL of the seller's inventory, loading dock, or carrier. </p> <p> - Information to simulate delivery, such as SKU IDs and postal codes. </p> |
 | Payments | <p> - Transaction ID. </p> <p> - Transaction link available in your VTEX Admin under <em> Payments > Transactions. </em> </p>
 | VTEX IO | <p> - The app name and version used. </p> <p> - Workspace used. </p> <p> - ZIP file with the <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-3-settingyourstoretheme">store-theme</a> if the theme is linked but not installed. </p> |
diff --git a/docs/tutorials/es/ab-testing-how-where-when-and-why.md b/docs/tutorials/es/ab-testing-how-where-when-and-why.md
index bb05614d8..ab5d3088b 100644
--- a/docs/tutorials/es/ab-testing-how-where-when-and-why.md
+++ b/docs/tutorials/es/ab-testing-how-where-when-and-why.md
@@ -1,10 +1,10 @@
 ---
-title: 'Prueba AB: cómo, dónde, cuándo y por qué'
+title: 'Pruebas A/B para tiendas en CMS Portal Legado'
 id: tutorials_581
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:39.133Z
-updatedAt: 2019-12-31T17:00:44.367Z
-publishedAt: 2019-12-31T17:00:44.367Z
+updatedAt: 2024-04-04T17:00:10.270Z
+publishedAt: 2024-04-04T17:00:10.270Z
 firstPublishedAt: 2017-04-27T23:03:41.601Z
 contentType: tutorial
 productTeam: Others
@@ -15,63 +15,24 @@ legacySlug: prueba-ab-como-donde-cuando-y-por-que
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-Últimamente, hubo un gran aumento en la búsqueda de información sobre prueba AB. Basta participar de cualquier evento sobre el mercado de e-commerce y allá está el asunto en las ruedas con los especialistas. Pero ¿por qué tanto interés en saber más sobre el asunto? Simple, el interés es reflejo de la evolución del e-commerce nacional.
+Las pruebas A/B son un método para comparar dos versiones de un sitio web y determinar cuál genera un mayor engagement de usuarios, tasas de conversión y otras métricas relevantes. El objetivo de las pruebas A/B es evaluar qué versión (A o B) obtiene tasas de éxito más altas y mejores resultados.
 
-En primer lugar quiero aclarar la diferencia entre Prueba AB y Prueba Multivariable.
+En el contexto de tiendas en el CMS - Portal Legado, las herramientas nativas de pruebas A/B no están disponibles. Sin embargo, puedes aprovechar soluciones de terceros como [Optimizely](https://docs.developers.optimizely.com/full-stack-experimentation/docs/welcome) y su [solución de pruebas A/B](https://docs.developers.optimizely.com/full-stack-experimentation/docs/run-a-b-tests). Esta herramienta permite crear y gestionar pruebas A/B, facilitando el análisis de desempeño de diferentes versiones del sitio web en un entorno controlado.
 
-**Prueba AB:** no es más que dos (o más) versiones de una misma página creadas con un elemento diferente para probar cuál versión presenta un mejor resultado. Esas pruebas son realizadas al mismo tiempo, o sea, las dos versiones se publican simultáneamente para atingir el mismo perfil de público en un mismo período de tiempo:
+## Casos de uso de las pruebas A/B
 
-![ab_teste_modelo1 esp](https://images.ctfassets.net/alneenqid6w5/6EoMdJwiqWcGCaeAAsI6oc/b9c144ed504084906bc2b586f7e76035/modelo_1_ESPANHOL.png)
+En VTEX, las pruebas A/B pueden realizarse con las siguientes tecnologías de desarrollo de tiendas:
 
-_En este ejemplo estamos probando el elemento “color del botón”_
+| Tecnología | ¿Pueden realizarse pruebas A/B nativas entre las tecnologías?  | Referencia     |
+| ---------- | ---------- | ---------- |
+| CMS Portal Legado - VTEX IO (Store Framework) | Sí      | [A/B testing Legacy and IO store versions](https://developers.vtex.com/docs/guides/vtex-io-documentation-performing-ab-testing-between-legacy-and-io)     |
+| CMS Portal Legado - FastStore | No | - |
+| VTEX IO (Store Framework) - VTEX IO (Store Framework)   | No | - |
+| VTEX IO (Store Framework) - FastStore     | No | - |
+| FastStore - FastStore  | No | - |
 
-**Prueba Multivariable:** parecida con la Prueba AB, la Prueba Multivariable también tiene el propósito de probar versiones diferentes de una misma pantalla, pero se prueba más de una modificación pro versión creada.
+## Pruebas A/B entre CMS - Portal Legado y las versiones de tiendas VTEX IO
 
-![ab_teste_modelo2 esp](https://images.ctfassets.net/alneenqid6w5/46py0F6og0UgceIwWYgWsW/4fa4e120d982c1845432d3cba3344b63/MODELO_2_espanhol.png)
-
-_En este ejemplo, estamos probando el elemento “color del botón”, el elemento “texto” y el elemento “tamaño de la fuente”_
-
-Explicadas las diferencias, nos basta saber por qué los profesionales especialistas en conversión defienden el uso de la Prueba AB mucho más que la Prueba Multivariable.
-
-¡Es obvio! Con la Prueba AB usted sabe exactamente lo que generó la variación en los resultados y puede aprender con eso. Ya con la Prueba Multivariable se hace imposible decir si la variación fue causada por el color del botón o por la modificación del texto.
-
-Existen sitios específicos para la divulgación de resultados de Prueba AB. Pero, a pesar de muy útiles, deben ser vistos con cuidado, ya que no todo lo que funciona para el público A va a funcionar para el público B. Además, el perfil del consumidor brasileño es bastante diferente del perfil del consumidor extranjero.
-
-Vale darle una mirada a los sitios whichtestwon.com y abtests.com para conocer un poco de lo que otros dueños de tienda andan probando.
-
-Sabiendo de eso, surgen algunas dudas comunes:
-
-- ¿Cómo realizar una prueba de estas?
-- ¿Dónde puedo probar? ¿En qué parte de la página?
-- ¿Cuándo puedo empezar a probar?
-- ¿Por qué debo gastar recurso probando mi tienda?
-
-### ¿Cómo?
-
-Hoy existen diversas herramientas en el mercado (pagadas y gratuitas) para realizar Prueba AB. Yo recomiendo el uso de Google Analytics, que ganó recursos del extinto Google Optimizer para realizar Pruebas AB de forma simple y rápida. Basta acceder su cuenta en el Analytics y buscar la pestaña **Content > Experiments** (Contenido > Experiencias). Tiene un paso a paso sencillo de ser seguido y no encontrará grandes dificultades para rodar una prueba.
-
-También recomiendo la herramienta Visual Website Optimizer. Es pagada, pero ofrece recursos más avanzados para realizar las pruebas, incluso con la capacidad de modificar algunas cosas en la página sin necesidad de contactar al desarrollador front-end. Vale la pena dar una mirada en la versión de prueba de la herramienta para conocer un poco más.
-
-Cualquier prueba debe ser aplicada por un periodo mínimo de una semana, ya que usuarios de final de semana poseen el perfil de navegación diferente de los usuarios que navegan durante la semana. Las pruebas deben ser aplicadas al menos 1.000 impresiones por versión creada, o sea, si ha creado dos versiones de una misma página, no saque ninguna conclusión mientras la prueba no se exhiba por lo menos 2.000 veces.
-
-### ¿Dónde?
-
-En cualquier lugar. Todas las páginas de su sitio pueden participar de pruebas AB. Las pruebas harán con que usted entienda mejor cómo piensa el usuario, qué funciona y qué no funciona en internet.
-
-Las pruebas pueden ser aplicadas en todos los elementos de la página como colores de botones, textos, colores de texto, tamaño de fuentes, disposición de un elemento, diagramación de la página, inserción de íconos, tamaño de imágenes, tipo de imagen, etc. Cuanto más lo pruebe, mayor será el conocimiento adquirido sobre el perfil del usuario.
-
-Incluso las pruebas que no resulten en un aumento en sus tasas de conversión o aun los que representen una caída significativa en los resultados pueden usarse para mejorar todas las demás páginas y hacer que su conversión despegue.
-
-### ¿Cuándo?
-
-La gran ventaja de las Pruebas AB es que el usuario final no tiene noción de que ha participado en alguna prueba, ya que él verá sólo una de las versiones creadas y tendrá la seguridad de que aquella es su página original independientemente de cuál se le presente.
-Siendo así, no hay límites de cuántas pruebas se pueden crear y aplicar, por eso, pruebe todo el tiempo; todo el tiempo.
-
-### ¿Por qué?
-
-Esa es una pregunta a la que podría dar decenas de justificativas, pero voy a enfocarme en las más importantes:
-
-1. Sólo con la Prueba AB va a entender cuáles son las mejores decisiones a tomar en su tienda basado en datos mensurables sobre su público específico. No todo lo que funciona para su competencia va a funcionar para usted;
-2. Apostar sus fichas en un layout puramente basado en el instinto del designer es peligroso y puede dar mucho perjuicio. Gusto personal es un peligro;
-3. No se saca nada con invertir todo su presupuesto en traer tráfico para su tienda si ésta no está preparada para recibir a sus visitantes y convertirlos en compradores. Solamente aplicando estas pruebas sabrá lo que debe ser hecho DENTRO de su tienda para aumentar su tasa de conversión y sacarle mucho más provecho al presupuesto invertido en anuncios aumentando su lucro, ROI, facturación, etc.
+Si estás considerando migrar tu tienda a VTEX IO y deseas comparar el desempeño mediante pruebas A/B, consulta la [guía A/B testing Legacy and IO store versions](https://developers.vtex.com/docs/guides/vtex-io-documentation-performing-ab-testing-between-legacy-and-io), que ofrece instrucciones detalladas sobre cómo realizar pruebas A/B entre los workspaces de la tienda en CMS - Portal Legado y en VTEX IO.
 
+Ejecutar una prueba A/B entre estas dos versiones de la tienda te permite analizar el impacto de la transición a VTEX IO en el engagement de los usuarios, las conversiones y el desempeño general.
diff --git a/docs/tutorials/es/access-control.md b/docs/tutorials/es/access-control.md
new file mode 100644
index 000000000..bf0333b06
--- /dev/null
+++ b/docs/tutorials/es/access-control.md
@@ -0,0 +1,61 @@
+---
+title: 'Control de acceso'
+id: 4rM3gyiWqtkim4Q8hOvLTC
+status: DRAFT
+createdAt: 2023-11-30T16:29:30.077Z
+updatedAt: 2023-11-30T21:42:00.250Z
+publishedAt: 
+firstPublishedAt: 2023-11-30T21:40:59.550Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: control-de-acceso
+locale: es
+legacySlug: control-de-acceso
+subcategory: 1HSqkejwuYcQSMC400uY84
+---
+
+Cada acción en VTEX, como acceder a una página en el Admin o hacer una llamada de API, implica un request a nuestra infraestructura. Para garantizar la seguridad de estas operaciones, existe **License Manager**, el sistema encargado de comprobar si un usuario tiene los permisos adecuados para realizar una acción en la plataforma.
+
+Para facilitar la gestión de estos permisos, License Manager se basa en [recursos](#recursos) y [roles](#roles). Consulta a continuación más información sobre estos conceptos.
+
+## Recursos
+
+Un **recurso** es una entidad asociada a una acción o información dentro de nuestra infraestructura. Por ejemplo, el recurso _Product management_ permite a un usuario acceder y editar el formulario de registro de productos en el Catálogo. Para obtener más detalles sobre cada recurso disponible consulta [Recursos de License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3).
+
+Cada request pasa por un análisis de seguridad para comprobar que el usuario dispone de los recursos necesarios, es decir, del permiso necesario para llevar a cabo esa acción. Sin los recursos necesarios, el request no podrá completarse.
+
+## Roles
+
+Los **roles** determinan el conjunto de recursos a los que un grupo de usuarios puede acceder en VTEX. Cada usuario administrativo puede ser asociado a uno o varios roles.
+
+Dado que al Admin suelen acceder múltiples colaboradores, es importante limitar el acceso a las acciones críticas dentro de una cuenta, para así minimizar disrupciones en la operación de la tienda y garantizar que cada usuario tenga acceso únicamente a las acciones necesarias para desempeñar su función.
+
+Por ejemplo, un equipo de operadores de televentas solo necesita acceso a la información de los pedidos, por lo que no debería tener acceso a otros ajustes de la plataforma. En este caso, el rol solo debe contener recursos relacionados con la lectura de información de pedidos.
+
+Para gestionar los roles registrados en tu tienda y los usuarios asociados a ellos, accede a la [lista de roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+Consulta a continuación los diferentes tipos de roles que puedes registrar en la tienda.
+
+### Tipos de rol
+
+Al [crear un nuevo rol](https://help.vtex.com/es/tutorial/crear-nuevo-rol--qGtNQpKSSAduX94l2WZBW), tienes la opción de utilizar uno de los predefinidos que proporciona VTEX o crear uno personalizado, seleccionando cada recurso necesario.
+
+El administrador necesita tener un rol con el [recurso](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) _Save access profile_ para crear roles en License Manager.
+
+#### Predefinidos
+
+Los roles predefinidos son conjuntos de recursos predeterminados por VTEX que cubren los casos de uso más comunes. Consulta la lista completa de [roles predefinidos](https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy) y sus permisos asociados.
+
+#### Personalizados
+
+Además de utilizar roles predefinidos, puedes [crear roles personalizados](https://help.vtex.com/pt/tutorial/crear-nuevo-rol--qGtNQpKSSAduX94l2WZBW#rol-personalizado) con los recursos necesarios para un grupo de usuarios administrativos de tu tienda.
+
+Por ejemplo, un equipo encargado de mantener actualizado el catálogo de la tienda generalmente lleva a cabo un conjunto de tareas bien definidas, como registrar y editar productos, categorías y marcas. En este caso, un administrador de cuenta puede crear un rol personalizado con todos los recursos necesarios para estos colaboradores.
+
+Consulta la lista completa de [recursos de License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) que se pueden utilizar.
+
+## Más información
+
+* [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [Crear nuevo rol](https://help.vtex.com/pt/tutorial/crear-nuevo-rol--qGtNQpKSSAduX94l2WZBW)
diff --git a/docs/tutorials/es/accessing-a-client-abandoned-cart.md b/docs/tutorials/es/accessing-a-client-abandoned-cart.md
index e36b5ad2e..3bf4c7983 100644
--- a/docs/tutorials/es/accessing-a-client-abandoned-cart.md
+++ b/docs/tutorials/es/accessing-a-client-abandoned-cart.md
@@ -28,26 +28,26 @@ Ver estos campos es muy simple. Una vez registrado en el Admin de su tienda, só
 
 1. En la _sidebar_ del Admin, haga clic en __Master Data__;
 
-  ![Carrinho Abandonado - 1 - ES](https://images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/76369f4dd2d1483fe5e4d3a501bc9d53/4GdZSkwtm9f76BIVFnC65D_Masterdata_ES.jpg)
+  ![Carrinho Abandonado - 1 - ES](//images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/76369f4dd2d1483fe5e4d3a501bc9d53/4GdZSkwtm9f76BIVFnC65D_Masterdata_ES.jpg)
 
 2. Haga clic en el icono de configuración (engranaje) del __Profile System__.
 
-  ![Carrinho Abandonado - 2 - ES](https://images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/6515d98ac1ca841647e50989854ca0cf/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
+  ![Carrinho Abandonado - 2 - ES](//images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/6515d98ac1ca841647e50989854ca0cf/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
 
 3. Asegúrese de que está en la pestaña __Aplicaciones__.
 
-  ![Carrinho Abandonado - 3 - ES](https://images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/32716ff3964171724751aebc9536efca/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
+  ![Carrinho Abandonado - 3 - ES](//images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/32716ff3964171724751aebc9536efca/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
 
 4. Acceda a Editar (Lápiz) en la categoría __Clientes__.
 
-  ![Carrinho Abandonado - 4 - ES](https://images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/87cb6addecfe6afd4f4135ca89e02df8/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
+  ![Carrinho Abandonado - 4 - ES](//images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/87cb6addecfe6afd4f4135ca89e02df8/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
 
 5. Seleccione __"Último carrito"__ y __"Carrito"__ entre las opciones de __Campos de Listados__;
 
-  ![Carrinho Abandonado - 5 - ES](https://images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/786f5d9a8362fd704daa2b8a88596ad0/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 5 - ES](//images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/786f5d9a8362fd704daa2b8a88596ad0/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
 
 6. Haga clic en __Guardar__.
 
-  ![Carrinho Abandonado - 6 - ES](https://images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/40b0c1cc04474521d0f89ac54e9ab961/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
+  ![Carrinho Abandonado - 6 - ES](//images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/40b0c1cc04474521d0f89ac54e9ab961/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
 
 Con eso, usted ya podrá ver los parámetros de los carritos abandonados de sus clientes.
diff --git a/docs/tutorials/es/accessing-the-beta-environment.md b/docs/tutorials/es/accessing-the-beta-environment.md
index 144e8b106..1de99affd 100644
--- a/docs/tutorials/es/accessing-the-beta-environment.md
+++ b/docs/tutorials/es/accessing-the-beta-environment.md
@@ -1,10 +1,10 @@
 ---
-title: 'Acceder al ambiente beta por el dominio myvtex.com'
+title: 'Accede al entorno beta a través del dominio myvtex.com'
 id: 3BHM289568gcSwk2O80Asu
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-07-26T18:09:29.968Z
-updatedAt: 2019-12-31T15:26:39.674Z
-publishedAt: 2019-12-31T15:26:39.674Z
+updatedAt: 2024-03-13T12:00:57.622Z
+publishedAt: 2024-03-12T19:18:51.136Z
 firstPublishedAt: 2018-07-26T18:43:10.906Z
 contentType: tutorial
 productTeam: Reliability
@@ -15,26 +15,36 @@ legacySlug: acceder-al-ambiente-beta
 subcategory: Se4oi5LroIII2Ei0uGAoE
 ---
 
-En VTEX, todas las tiendas tienen un ambiente beta.
+En VTEX, todas las tiendas disponen de un entorno beta. En este entorno, los usuarios de la plataforma, ya sean retailers, desarrolladores u otras personas con acceso, pueden llevar a cabo pruebas para validar nuevas configuraciones o versiones de aplicaciones/servicios antes de implementar cambios en el entorno donde los clientes realizan sus compras, conocido como entorno de producción (stable).
 
-Este ambiente es un lugar de prueba para que el usuario de la plataforma pueda validar cambios en una tienda antes de promover los cambios al ambiente principal.
+<div class = "alert alert-info">
+El entorno beta es una reproducción exacta del entorno de producción (stable), que incluye todos los datos y configuraciones de la tienda.
+</div>
 
-## Cómo funciona el ambiente beta
+De esta manera, **cualquier modificación de datos en el entorno beta afecta a los datos en el entorno stable**.
 
-El ambiente beta funciona como un ambiente de prueba para diferentes versiones de aplicaciones/servicios de VTEX en su tienda. Es un ambiente que reproduce toda la información del ambiente principal (`stable`). Así, los datos de la tienda son los mismos, tanto en beta y en stable. De esta forma, __el cambio de datos en el ambiente beta afecta a los datos en el ambiente stable__.
+## Accede al entorno beta
 
-## Acceder al ambiente beta
+Para acceder al entorno beta de tu tienda debes habilitar la cookie <code>vtex-commerce-env</code>siguiendo estos pasos:
 
-El acceso al ambiente beta se encuentra al final del menú lateral del Admin. Sólo hay que hacer clic en `Usar beta` para acceder al ambiente de prueba.
+<ol start="1">
+  <li>En el Admin VTEX, accede a la pantalla DevTools en tu navegador presionando la tecla <code>F12</code> o haciendo clic derecho y seleccionando la opción <b>Inspeccionar</b>.
+.</li>
+  <li>En la barra superior de la pantalla accede a la pestaña <b>Aplicación</b>, y en la barra lateral izquierda, en Cookies, haz clic en la URL de tu tienda.
 
-![politica-comercial-es](https://images.ctfassets.net/alneenqid6w5/6opF8h3ijmqoIkam4ugAim/d194277f2d7e26fc52fc967a866b7e4a/usar-beta-es.png)
+</li>
+  <li>En la tabla, ingresa la siguiente información en las celdas de la última fila:
+</li>
+  <ul>
+<li>Nombre: <code>vtex-commerce-env</code></li>
+<li>Valor: <code>beta</code>
+</li>
+</ul>
+<img src="https://images.ctfassets.net/alneenqid6w5/3g8wintA1heJbzdV8J0s45/8eb6f5917e2d9d8a134b81231dc42728/Ambiente_beta_.png" alt="beta">
+<li>Actualiza la página presionando <code>F5</code> o la tecla de actualización de tu navegador. Una vez que a página se haya cargado, el Admin de la tienda ya estará en el entorno beta.
+</li>
+</ol>
 
-<div class="alert alert-info">
-Para volver al ambiente principal, haga clic en <code>Usar stable</code>, también ubicado al final del menú lateral del Admin.
+<div class = "alert alert-info">
+Para restaurar la tienda a su entorno principal, accede nuevamente a la pantalla DevTools de tu navegador y elimina la cookie vtex-commerce-env. Actualiza la página una vez más para volver al entorno de producción <b>stable</b>.
 </div>
-
-## Comprobar cambios en el ambiente beta
- 
-Para acceder a su tienda en modo beta y comprobar cómo los cambios realizados afectaron a su store front, basta con hacer clic en el botón `VISITE LA TIENDA` después de haber realizado el acceso al ambiente beta descrito en el paso anterior.
-
-![visite-a-loja-beta-es](https://images.ctfassets.net/alneenqid6w5/7H26DYk6Oc0moGgckKu2gE/a44101d0044c62582c6af8c364157958/visite-a-loja-beta-es.png)
diff --git a/docs/tutorials/es/account-management.md b/docs/tutorials/es/account-management.md
index 46f5aca9d..cdb24e315 100644
--- a/docs/tutorials/es/account-management.md
+++ b/docs/tutorials/es/account-management.md
@@ -84,90 +84,10 @@ Después que un usuario llena y guarda **Nombre** e **E-mail**, en los campos de
 La plantilla para este correo electrónico automático se puede cambiar en el <a href="https://help.vtex.com/es/tutorial/understanding-the-message-center--tutorials_84">Centro de mensajes</a> modificando la plantilla de <i>registro de cuenta</i>.
 </div>
 
-![registro de cuenta](https://images.ctfassets.net/alneenqid6w5/7uIJliLTJ6wEMeeoqiSMQ/6c37511bd70d8035b11e18abc99b36d0/registro_de_cuenta.jpg)
+![registro de cuenta](//images.ctfassets.net/alneenqid6w5/7uIJliLTJ6wEMeeoqiSMQ/6c37511bd70d8035b11e18abc99b36d0/registro_de_cuenta.jpg)
 
 ## Seguridad
 
 En esta área se crean los [appKeys y appTokens](https://help.vtex.com/es/tutorial/chaves-de-aplicacao) utilizados para autenticar integraciones con su tienda.
 
 Apenas el usuario Titular tiene permiso para crear appKeys y appTokens, ya que estos dan acceso a su tienda por API, lo que puede ser crítico si no lo utilizan profesionales habilitados.
-piedad de la tienda a otro usuario.
-
-## Tiendas
-
-En la pestaña Tiendas, puedes:
-
-- Consultar la [lista de tiendas](#tiendas).
-- [Agregar una nueva tienda](#crear-tienda).
-- [Editar tienda](#editar-tienda).
-- [Eliminar tienda](#eliminar-tienda).
-
-Al hacer clic en la pestaña **Tiendas** en la parte superior de la pantalla, verás una lista con la información de todas las tiendas creadas en tu cuenta VTEX.
-
-![Página de detalles de la cuenta - Tiendas](https://images.ctfassets.net/alneenqid6w5/rAFyEsEDLBDqj3UBGufrb/3d7a7f2d6029d2d36193ebe2d89c0fa9/2es.png)
-
-Para cada tienda, puedes ver los siguientes detalles:
-
-- Nombre de la tienda:** el identificador interno de la tienda.
-- **Nombre comercial:** el nombre utilizado comercialmente.
-- **Hosts:** los dominios asociados a la tienda.
-
-Puedes utilizar el cuadro de búsqueda para filtrar las tiendas que aparecen en la lista por cualquiera de los atributos.
-
-También puedes [crear una nueva tienda](#crear-tienda), [editar una tienda](#editar-tienda) o [eliminar](#eliminar-tienda) tiendas existentes.
-
-### Crear tienda
-
-Para crear una nueva tienda, sigue los pasos a continuación.
-
-1. Ve a la página **Cuenta** haciendo clic en el **avatar de tu perfil**, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Cuenta**.
-2. Haz clic en la pestaña **Tiendas** en la parte superior de la pantalla.
-3. Haz clic en el botón `+ Nueva tienda`.
-4. Rellena la información básica de la tienda:
-	- Nombre de la tienda:** el identificador interno de la tienda.
-	- **Nombre comercial:** el nombre utilizado comercialmente.
-	- **Región:** el idioma predefinido asociado a esta tienda.
-    - **Política comercial:** la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#) que deseas asociar a la nueva tienda.
-5. Si deseas iniciar el proceso [go-live](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM) para tu tienda, rellena el campo **Hosts** con el dominio de tu tienda. En caso contrario, deja este campo en blanco.
-6. Haz clic en el botón `Crear`.
-
-<div class = "alert alert-info">
-  Para obtener más información sobre la configuración de los <b>Hosts</b> de tu tienda, consulta el artículo <a href="https://help.vtex.com/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450">Configurar el dominio de tu tienda</a>.
-</div>
-
-<div class="alert alert-warning">
-No utilice un dominio de tipo ".com" en el campo Store name. Este tipo de entrada sólo puede existir en el campo Hosts.
-</div>
-
-### Editar tienda
-
-Puedes editar la información de una tienda existente siguiendo los pasos a continuación.
-
-1. Ve a la página **Cuenta** haciendo clic en el **avatar de tu perfil**, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Cuenta**.
-2. Haz clic en la pestaña **Tiendas** en la parte superior de la pantalla.
-3. Haz clic en el botón de acción <i class="fas fa-ellipsis-v"></i> correspondiente a la tienda que deseas editar.
-4. Haz clic en `Editar`.
-5. Verás la página de edición de la cuenta. Edita la información que desees.
-6. Haz clic en `Guardar`.
-
-### Eliminar tienda
-
-Para eliminar una tienda, sigue los pasos a continuación.
-
-1. Ve a la página **Cuenta** haciendo clic en el **avatar de tu perfil**, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Cuenta**.
-2. Haz clic en la pestaña **Tiendas** en la parte superior de la pantalla.
-3. Haz clic en el botón de acción <i class="fas fa-ellipsis-v"></i> correspondiente a la tienda que deseas eliminar.
-4. Haz clic en `Eliminar`.
-5. Verás un modal de confirmación. Haz clic en `Eliminar`.
-
-<div class="alert alert-warning">
-Ten en cuenta que la tienda principal, marcada con una estrella junto a su nombre en la lista de tiendas, no se puede eliminar.
-</div>
-
-Más información:
-- [¿Qué es un nombre de cuenta?](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)
-- [Usuario titular](https://help.vtex.com/es/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy)
-- [Transferir la propiedad de la tienda](https://help.vtex.com/es/tutorial/transferencia-de-propriedade-da-loja)
-- [Configurando el dominio de tu tienda](https://help.vtex.com/es/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450)
-- [Go-live](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM)
-
diff --git a/docs/tutorials/es/account-settings-overview.md b/docs/tutorials/es/account-settings-overview.md
index bd081bf5e..aab05b6d9 100644
--- a/docs/tutorials/es/account-settings-overview.md
+++ b/docs/tutorials/es/account-settings-overview.md
@@ -21,7 +21,7 @@ En **Configuración de la cuenta**, puedes controlar el acceso al Admin y modifi
 
 Para acceder a la _Configuración de la cuenta_, haz clic en tu **avatar de perfil**, marcado con la inicial de tu email, y luego haz clic en el botón **Configuración de la cuenta**.  
 
-![Admin v4 account settings menu ES](https://images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/db9e1eb25c423a3c797521dad3658d9b/Admin_v4_account_settings_menu_ES.jpg)
+![Admin v4 account settings menu ES](//images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/db9e1eb25c423a3c797521dad3658d9b/Admin_v4_account_settings_menu_ES.jpg)
 
 La sección incluye las siguientes páginas, que pronto se incluirán en el diseño del Admin v4.
 
diff --git a/docs/tutorials/es/accounts-payable-brazil.md b/docs/tutorials/es/accounts-payable-brazil.md
index a54b2deb6..52c33a1f8 100644
--- a/docs/tutorials/es/accounts-payable-brazil.md
+++ b/docs/tutorials/es/accounts-payable-brazil.md
@@ -3,8 +3,8 @@ title: 'Cuentas a Pagar - Brasil'
 id: tutorials_660
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:25.003Z
-updatedAt: 2023-01-24T21:41:37.901Z
-publishedAt: 2023-01-24T21:41:37.901Z
+updatedAt: 2024-02-23T15:08:20.685Z
+publishedAt: 2024-02-23T15:08:20.685Z
 firstPublishedAt: 2017-04-27T23:03:40.609Z
 contentType: tutorial
 productTeam: Billing
@@ -15,4 +15,5 @@ legacySlug: procedimientos-de-cuentas-a-pagar
 subcategory: 22TaEgFhwE6a6CG2KASYkC
 ---
 
-<div class="alert alert-warning" role="alert">Este conteúdo é exclusivamente regional e portanto, não aplicável a países de língua portuguesa.</div>
+<div class="alert alert-warning" role="alert">Este conteúdo é exclusivamente regional e portanto, não aplicável a países de língua portuguesa. 
+La versión en español está disponible en <a href="https://help.vtex.com/es/tutorial/accounts-payable-international--3yea9sIlsA0KgUC28ASCGs">Cuentas por Pagar - Internacional</a></div>
diff --git a/docs/tutorials/es/activating-new-vtex-cdn.md b/docs/tutorials/es/activating-new-vtex-cdn.md
index 8498b849b..285c81952 100644
--- a/docs/tutorials/es/activating-new-vtex-cdn.md
+++ b/docs/tutorials/es/activating-new-vtex-cdn.md
@@ -1,10 +1,10 @@
 ---
 title: 'Activar nueva CDN de VTEX'
 id: 400JfRm4VGgsKgqgOw4WWA
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-10-02T23:12:05.096Z
-updatedAt: 2019-12-31T15:25:39.216Z
-publishedAt: 2019-12-31T15:25:39.216Z
+updatedAt: 2023-08-09T20:43:20.267Z
+publishedAt: 
 firstPublishedAt: 2017-10-03T02:09:58.361Z
 contentType: tutorial
 productTeam: Reliability
diff --git a/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md b/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md
index f0d7c5376..55f3cf6a3 100644
--- a/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md
+++ b/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md
@@ -20,7 +20,7 @@ El link de **Lista Completa** en el menu de categorias categorías es muy usado
 
 Como, por ejemplo, en el caso abajo, el "Departamento 2":
 
-![categoria.es](https://images.ctfassets.net/alneenqid6w5/7JXmPnw1lzfdGxgkshSztX/56e6b6587d0076dfb156867a953dd0e6/categoria.es.png)
+![categoria.es](//images.ctfassets.net/alneenqid6w5/7JXmPnw1lzfdGxgkshSztX/56e6b6587d0076dfb156867a953dd0e6/categoria.es.png)
 
 De todas las categorías, la tienda prefirió exhibir en el menú solamente algunas.
 
@@ -29,5 +29,5 @@ Esta configuración se hace en el registro de categoría, en la opción **Menu c
 - Si está marcada, la categoría aparece en el menú.
 - Si no está marcada, la categoría no aparece y se muestra opción Lista Completa en el sitio.
 
-![categoria2.es](https://images.ctfassets.net/alneenqid6w5/5fQJfwQpdMCpfE7s1P1Nx2/d8e05f4023ffbe92a7db72086af1dbf2/categoria2.es.png)
+![categoria2.es](//images.ctfassets.net/alneenqid6w5/5fQJfwQpdMCpfE7s1P1Nx2/d8e05f4023ffbe92a7db72086af1dbf2/categoria2.es.png)
 
diff --git a/docs/tutorials/es/adapting-your-integration-for-change-order-beta.md b/docs/tutorials/es/adapting-your-integration-for-change-order-beta.md
new file mode 100644
index 000000000..4dde3e75c
--- /dev/null
+++ b/docs/tutorials/es/adapting-your-integration-for-change-order-beta.md
@@ -0,0 +1,305 @@
+---
+title: 'Adaptando tu integración para Modificar pedido (Beta)'
+id: 6kGQWs0IvpwIZoyeoLMjlp
+status: PUBLISHED
+createdAt: 2024-06-03T18:54:30.094Z
+updatedAt: 2024-07-09T17:18:19.900Z
+publishedAt: 2024-07-09T17:18:19.900Z
+firstPublishedAt: 2024-06-03T20:02:10.248Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: adaptando-tu-integracion-para-modificar-pedido-beta
+locale: es
+legacySlug: adaptando-tu-integracion-para-modificar-pedido-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+Para evolucionar las modificaciones de pedidos en la plataforma VTEX, estamos lanzando [Modificar pedido (Beta)](https://help.vtex.com/es/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ), una solución mucho más completa, versátil y que proporciona una [nueva experiencia en el Admin VTEX](https://help.vtex.com/es/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw).
+
+Después de las interacciones entre nuestro equipo de ingenieros y los clientes y partners que ya se habían unido a la versión beta, hemos creado este contenido que incluye buenas prácticas de implementación y dudas frecuentes. Nuestro objetivo es que los próximos clientes y partners que comiencen a utilizar **Modificar pedido (Beta)** tengan este material de apoyo a su disposición.
+
+El artículo se organiza de la siguiente manera:
+
+* [Adaptación en distintos casos de uso](#adaptacion-en-distintos-casos-de-uso)
+* [Modificaciones en el cuerpo de los requests](#modificaciones-en-el-cuerpo-de-los-requests)
+* [Requests con errores y fallos](#requests-con-errores-y-fallos)
+* [Preguntas frecuentes](#preguntas-frecuentes)
+
+## Adaptación en distintos casos de uso
+
+Las siguientes secciones presentan los principales casos de uso de **Modificar pedido (Beta)** y sus respectivas recomendaciones.
+
+### Comunicación con el cliente por email transaccional
+
+**Modificar pedido (Beta)** utiliza nuevas plantillas para los [emails transaccionales](https://help.vtex.com/es/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my) (Message Center) que se ajustan a las funcionalidades innovadoras de la solución.
+
+Para personalizar una plantilla de email en el Admin VTEX, copia y pega el siguiente link en tu navegador sustituyendo `{nombreDeCuenta}` por el [nombre de cuenta](https://help.vtex.com/es/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) de tu tienda, y luego pulsa `Enter`:
+
+`https://{nombreDeCuenta}.myvtex.com/admin/message-center/#/templates/vtexcommerce-order-changed-v2`
+
+### Gestión de la modificación de pedidos en el Admin VTEX
+
+Las tiendas que utilizan la versión actual de la funcionalidad de modificación de pedidos tendrán acceso inmediato a las interfaces actualizadas de **Modificar pedido (Beta)** en el Admin VTEX una vez que el equipo de VTEX instale la nueva solución. Esto incluye una nueva gestión y comunicación de [Mi cuenta](https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#pedidos) y de [plantillas de emails transaccionales](https://help.vtex.com/es/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my).
+
+### Gestión de la modificación de pedidos vía API
+
+Las tiendas que utilizan nuestras API deben asegurarse de que la implementación en la integración siga la nueva arquitectura de la funcionalidad.
+
+En **Modificar pedido (Beta)**, el endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) funciona de forma asíncrona y el [usuario](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) o integración que realiza el request recibe un `requestId` de la plataforma, que se trata de un identificador único para dar seguimiento a la operación de modificación del pedido. Este identificador luego se utilizará en determinados endpoints. Todos los endpoints de **Modificar pedido (Beta)** son:
+
+* [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes)
+* [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview)
+* [Get order change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-)
+* [Get order change history](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes)
+* [Retry order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry)
+* [Cancel order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel)
+
+Después de modificar el pedido utilizando el endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), el integrador puede utilizar varias alternativas para los nuevos requests a los endpoints de **Modificar pedido (Beta)**:
+
+* **Polling:** baja complejidad.
+* **Preview:** mediana complejidad.
+
+La siguiente tabla muestra cada una:
+
+| **Tipo de flujo** | **Cómo funciona** |
+| :---: | :--- |
+| **Polling**<p>Baja complejidad</p> | <p>Después de la operación de modificación del pedido se genera un código único que la identifica, `requestId`, y que permite dar seguimiento a los detalles del request a través del endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get change details</a>. Tras la modificación del pedido, la propiedad del cuerpo de respuesta `finished` pasa a tener el valor `true` en este endpoint.</p><p>Además, <a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get change details</a> también se puede utilizar para obtener información sobre fallos y errores que dieron lugar a la cancelación de la operación de modificación del pedido, según se describe en la sección <a href="#requests-con-errores-y-fallos">Requests con errores y fallos</a>.</p> |
+| **Preview**<p>Mediana complejidad</p> | <p>Antes de enviar un request a <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a>, la integración tiene la opción de obtener una vista previa que produce un cuerpo de respuesta exactamente igual al del request de modificación. Para ello, solo hay que utilizar el mismo cuerpo de request en el request enviado al endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a>.</p><p>Esta vista previa es una simulación de la modificación y no genera efectos reales de modificar el pedido. El uso de <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a> es útil para obtener los valores totales asociados a la modificación del pedido en cuestión y también para validar los detalles del requests con un cuerpo de request válido.</p><p>Tras recibir una respuesta de éxito `200 OK` para obtener la vista previa de la modificación, la integración puede proceder con el request a <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> para modificar el pedido.</p><p>Luego, puedes adaptar la integración a escenarios tales como:<ul><li><b>Creación optimista:</b> los datos de las validaciones obtenidas con la simulación de la modificación cubren la mayor parte de los casos de éxito `200 OK`.</li><li><b>Implementación de polling:</b> mencionado anteriormente.</li></ul></p> |
+
+## Modificaciones en el cuerpo de los requests
+
+**Modificar pedido (Beta)** mantiene algunos de los atributos de la solución anterior, sin embargo, posee otros que fueron creados o transformados, tanto en nombre como funcionamiento. Los principales cambios se describen de la siguiente forma:
+
+* [Valores manuales](#valores-manuales)
+* [Agregar y remover ítems](#agregar-y-remover-items)
+* [Atributos obligatorios y opcionales de los ítems](#atributos-obligatorios-y-opcionales-de-los-items)
+* [Responsabilidad del usuario en la automatización del sistema](#responsabilidad-del-usuario-en-la-automatizacion-del-sistema)
+
+### Valores manuales
+
+* **Antes:** los campos `discountValue` y `incrementValue` definían el valor de la modificación del pedido como disminución o incremento del valor, respectivamente. El usuario calculaba el valor de la modificación y el resultado se sumaba o restaba del valor total del pedido mediante estos campos.
+  > **Ejemplo:** en un pedido de 100 USD que se debe modificar para agregar un ítem de 50 USD, el usuario enviaba `incrementValue` con el valor de 50 USD y el sistema calculaba el total del pedido como 150 USD. Si el usuario deseaba conceder un descuento de 30 USD al cliente en la modificación, tenía que enviar un `discountValue` con el valor de 30 USD para que el total del pedido fuera 120 USD.
+* **Ahora:** los nuevos campos `manualDiscountValue` y `manualIncrementValue` definen valores manuales adicionales que se suman o restan del costo total del pedido, independientemente de las modificaciones que se estén realizando. Como el sistema calcula el resultado de las modificaciones automáticamente (considerando el precio y condiciones de finalización de compra), el usuario puede incrementar o disminuir los valores utilizando los campos mencionados.
+  > **Ejemplo:** en un pedido de 100 USD que debe modificarse para agregar un ítem de 50 USD, tras agregar el ítem, el sistema calcula automáticamente el incremento de 50 USD del valor y el usuario no tiene que enviarlo manualmente. El resultado del valor total del pedido será 150 USD. Si el usuario desea conceder un descuento de 30 USD al cliente en la modificación, solo tiene que enviar el campo `manualDiscountValue` con el valor de 30 USD y el valor total del pedido será 120 USD.
+
+### Agregar y remover ítems
+
+* **Antes:** los atributos utilizados para agregar y remover ítems del pedido eran los arreglos `itemsAdded` y `itemsRemoved` que contenían objetos de ítems con los campos `id`, `price` y `quantity`.
+* **Ahora:** los atributos para agregar y remover ítems del pedido son los objetos `add` y `remove` que contienen un nuevo nivel que define un objeto para cada ítem a través del arreglo `items`.
+
+Ejemplo de cómo remover ítems en **Modificar pedido (Beta)**:
+
+```
+{
+    "remove": {
+        "items": [
+            {
+                "id": "1",
+                "quantity": 1
+            }
+        ]
+    }
+}
+```
+
+<br>
+
+### Atributos obligatorios y opcionales de los ítems
+
+Los ítems del cuerpo del request necesitan menos atributos obligatorios que antes: `id` y `quantity`. Los demás atributos se obtienen del pedido o del sistema Catálogo.
+
+Existen otros campos que pueden ajustarse para sobrescribir la información de un ítem que se está modificando, en caso de ser necesario agregar o modificar ítems ya existentes. Los campos opcionales son `price`, `unitMultiplier` y `measurementUnit`. El sistema no tiene en cuenta ningún otro campo enviado en el request.
+
+### Responsabilidad del usuario en la automatización del sistema
+
+* **Antes:** el usuario era responsable de calcular el valor que se iba a modificar en el pedido. Enviaba dicho valor en el atributo `discountValue` o `incrementValue`, dependiendo de si era un aumento o disminución de precio.
+* **Ahora:** el sistema es responsable de proporcionar la información de los ítems y automáticamente calcula el valor final del pedido con la modificación. En otras palabras, el usuario ahora informa lo mínimo necesario y no tiene que calcular el valor final del pedido, lo que reduce las posibilidades de error.
+
+## Requests con errores y fallos
+
+Cuando se produce un error o fallo en el request de **Modificar pedido (Beta)**, se puede obtener la información del procesamiento a través del endpoint [Get change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-) mediante el atributo `logs`.
+
+Ejemplo de `logs` con error de procesamiento:
+
+```
+{
+    "requestId": "de88ad2b-a927-47ad-b5af-a6fab4d2a22f",
+    "workflowId": "418827ee-0efd-4127-87c0-6d881358b750",
+    "status": "preparing",
+    "finished": false,
+    "reason": "test",
+    "manualDiscountValue": 1000,
+    "manualIncrementValue": 0,
+    "totalChangeValue": 0,
+    "totals": [],
+    "add": {
+        ...
+    },
+    "logs": [
+       {
+            "date": "2024-05-13T21:35:00.1952066Z",
+            "message": "Automatic transition failed. Current retry counter is 1. Failed with message: Failure to run the action 'preparing'. Content: '{\"error\":{\"code\":\"001\",\"message\":\"An error has occurred\"},\"operationId\":\"f69e8934-5f93-4ba2-9ebe-408080c6733b\",\"fields\":{}}'",
+            "source": "Workflow Engine",
+            "status": "preparing"
+        },
+        {
+            "date": "2024-05-13T21:35:00.1481754Z",
+            "message": "OperationId:f69e8934-5f93-4ba2-9ebe-408080c6733b\nSystem.NullReferenceException: Object reference not set to an instance of an object.\n   at VTEX.SOS.Services.OrderService.OrderServiceCapabilities.ChangeOrderV2.ChangeOrderMerger.MergeWithEnrichedItemMetadata(Seller seller, OrderItem itemToEnrich, OrderItem enrichedItem)\n   at VTEX.SOS.Services.OrderService.OrderService.FillAddedItemMetadataAsync(IContext context, IEnumerable`1 enrichedOrderItems, Seller seller, OrderItem addedItem, String salesChannel, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 284\n   at VTEX.SOS.Services.OrderService.OrderService.FillAddedItemInfoAsync(IContext context, OrderSource orderOrigin, IEnumerable`1 enrichedOrderItems, Seller seller, OrderItem addedItem, String salesChannel, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 273\n   at VTEX.SOS.Services.OrderService.OrderService.EnrichItemsOnlyAsync(IContext context, Order order, ChangeOrderInput changeOrderInput, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 238\n   at VTEX.SOS.Services.OrderService.OrderService.PrepareChangeOrderAsync(IContext context, Order order, ChangeOrderInput changeOrderInput, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 38\n   at VTEX.SOS.Services.OrderService.ChangeOrderService.PrepareChangeInternalAsync(String orderId, String changeRequestId, IContext context, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Service/ChangeOrderService.cs:line 288\n   at VTEX.SOS.Services.OrderService.ChangeOrderService.PrepareChangeInternalAsync(String orderId, String changeRequestId, IContext context, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Service/ChangeOrderService.cs:line 288",
+            "source": "ChangeOrderService:PrepareChangeInternalAsync",
+            "status": "preparing"
+        }
+    ]
+}
+```
+
+<br>
+
+El sistema automáticamente reintenta el procesamiento de cada fallo (errores no tratados). Si los reintentos no funcionan, se cancela el request de modificación. El motivo del error se puede obtener utilizando [Get change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-) mediante el atributo `cancellationData`.
+
+Si el origen del error es incumplimiento de las reglas de validación del request por parte del usuario, la operación se cancela automáticamente y no se realicen nuevos intentos de procesamiento. En este caso, el motivo del error también se comunica a través de `cancellationData`. 
+
+Ejemplo de objeto `cancellationData`: la modificación de precio solicitada en el request es mayor que el valor límite configurado para la cancelación de pedidos.
+
+```
+{
+    "requestId": "29004325-e2b8-4b7e-a82c-f588e6d3c07f",
+    "workflowId": "ea392ae2-1db5-432c-97d3-adc4436ca4aa",
+    "status": "canceled",
+    "finished": false,
+    "reason": "test",
+    "manualDiscountValue": 37500,
+    "manualIncrementValue": 0,
+    "totalChangeValue": 0,
+    "totals": [],
+    "remove": {
+        ...
+    },
+    "cancellationData": {
+        "requestedByUser": false,
+        "reason": "The value of the change exceed the order's price",
+        "cancellationDate": "2024-05-13T21:31:38.8596Z"
+    }
+}
+```
+
+<br>
+
+## Preguntas frecuentes
+
+Esta sección presenta dudas comunes de los clientes y partners que utilizan **Modificar pedido (beta)**:
+
+[1 - ¿Cómo puedo sobrescribir el precio de un ítem específico?](#1-como-puedo-sobrescribir-el-precio-de-un-item-especifico)
+
+[2 - ¿Cómo puedo saber y cambiar el valor total antes de modificar el pedido?](#2-como-puedo-saber-y-cambiar-el-valor-total-antes-de-modificar-el-pedido)
+
+[3 - ¿Tengo que informar el precio de envío o se recalcula automáticamente?](#3-tengo-que-informar-el-precio-de-envio-o-se-recalcula-automaticamente)
+
+[4 - ¿Cómo funcionan las promociones en Modificar pedidos (Beta)?](#4-como-funcionan-las-promociones-en-modificar-pedidos-beta)
+
+[5 - ¿Qué debo hacer cuando el request devuelve el status canceling o canceled?](#5-que-debo-hacer-cuando-el-request-devuelve-el-status-canceling-o-canceled)
+
+### 1 - ¿Cómo puedo sobrescribir el precio de un ítem específico?
+
+Para sobrescribir el precio de un ítem específico, puedes aplicarle un valor manual al ítem al mismo tiempo que se modifica la cantidad.
+
+En el endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), el atributo `price` tiene la misma función que el flujo de finalización de pedidos y hace referencia al precio nominal del ítem. Por ejemplo, en un pedido que contiene un ítem pesable, como una manzana, `price` es el precio por kilo de la manzana.
+
+Ejemplo de cómo sobrescribir el precio de un ítem pesable:
+
+```
+{
+    "reason": "the client wanted to change",
+    "add": {
+        "items": [
+            {
+                "id": "1",
+                "quantity": 1,
+                "price": 150,
+            }
+        ]
+}
+```
+
+<br>
+
+### 2 - ¿Cómo puedo saber y cambiar el valor total antes de modificar el pedido? 
+
+El endpoint [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) permite al usuario simular el resultado de la modificación del pedido que se desea realizar mediante [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), ya que utiliza el mismo cuerpo de request y proporciona el mismo cuerpo de respuesta pero sin modificar el pedido. `totalChangeValue` es el atributo que informa el valor total que se está modificando en el pedido, ya sea un incremento (por ej.: cargo o ítem adicional) o disminución (por ej.: reducción manual del valor o remover un ítem).
+
+Si deseas que la integración manipule la variación del valor del pedido modificado, puedes utilizar el mismo cuerpo de request que se usa en [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) en un request a [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), incrementando o disminuyendo el valor de los campos `manualIncrementValue` y `manualDiscountValue`, respectivamente.
+
+### 3 - ¿Tengo que informar el precio de envío o se recalcula automáticamente?
+
+Cuando se producen cambios en la cantidad, tamaño o peso de los ítems, el costo de envío se recalcula automáticamente y el valor se suma al nuevo valor total del pedido.
+
+La regla de cálculo del nuevo costo de envío sigue las mismas condiciones aplicadas en la finalización del pedido.
+
+### 4 - ¿Cómo funcionan las promociones en Modificar pedidos (beta)?
+
+Al modificar el pedido se aplican automáticamente las mismas promociones y cargos que eran válidos para los ítems cuando se finalizó la compra. No se recalculan nuevas promociones y cargos en las condiciones del pedido modificado.
+
+**Ejemplo:** una tienda tenía una promoción de "Paga 2 y lleva 3", pero el cliente solo compró 2 ítems y no pudo beneficiarse del descuento. Cuando el cliente solicita que se agregue un ítem adicional a su pedido, ahora tiene 3 ítems, pero la promoción no se aplica porque no se aplicó en el pedido original.
+
+Para informar la promoción de un ítem al modificar el pedido, puedes hacerlo manualmente con [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) mediante el atributo `priceTags`. Este es el comportamiento predeterminado de la plataforma. 
+
+Ejemplo de un ítem con promociones aplicadas en el pedido original:
+
+```
+{
+    "reason": "teste",
+    "replace": [
+        {
+            "from": {
+                "items": [
+                    {
+                        "id": "16",
+                        "quantity": 1,
+                        "measurementUnit": "kg",
+                        "unitMultiplier": 0.5
+                    }
+                ]
+            },
+            "to": {
+                "items": [
+                    {
+                        "id": "16",
+                        "quantity": 1,
+                        "measurementUnit": "kg",
+                        "unitMultiplier": 0.750,
+                        "price": 530,
+                        "priceTags": [
+                            {
+                                "name": "DISCOUNT@MANUALPRICE",
+                                "value": -50,
+                                "isPercentual": false
+                            }
+                        ]
+                    }
+                ]
+            }
+        }
+    ]
+}
+```
+
+<br>
+
+En este ejemplo, se utilizó la tag de descuento manual `DISCOUNT@MANUALPRICE`. La tag equivalente para cargos manuales sería `TAX@MANUALPRICE`. El endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) también puede utilizar el atributo `priceTag` de una promoción existente y cambiar el valor de la modificación del pedido.
+
+### 5 - ¿Qué debo hacer cuando el request devuelve el status canceling o canceled?
+
+Los status `canceling` y `canceled` significan que la modificación del pedido no se procesó correctamente, los cambios no se aplicaron al pedido y el usuario puede ignorar el intento. Los fallos y errores pueden deberse a:
+
+* El usuario no cumplió las reglas de validación del request.
+* El sistema excedió el número de intentos de reprocesamiento automático.
+* Otros fallos de procesamiento del sistema.
+
+La recomendación general es investigar el origen del error y comprobar el cuerpo del request que se está enviando a través del endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) o [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview). Más información en la sección [Requests con errores y fallos](http://heading).
+
+## Más información
+
+| **Help Center** | **Developer Portal** |
+| :--- | :--- |
+| <p>Modificar pedidos en el Admin VTEX:<ul><li><a href="https://help.vtex.com/es/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Cómo funciona Modificar pedido (Beta)</a></li><li><a href="https://help.vtex.com/es/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw">Cómo modificar pedidos (Beta)</a></li></ul></p> | <p>Modificar pedidos vía API:<ul><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change details</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes">Get order change history</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry">Retry order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel">Cancel order change</a></li></ul></p> |
+
diff --git a/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md b/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md
index 96d28fbbc..67afd8673 100644
--- a/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md
+++ b/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md
@@ -3,8 +3,8 @@ title: 'Añadir soporte a 3DS en la integración con Adyen'
 id: 3DNZeC9qJaC2GMIw4mawYk
 status: PUBLISHED
 createdAt: 2017-07-25T18:20:05.681Z
-updatedAt: 2023-03-26T22:04:52.559Z
-publishedAt: 2023-03-26T22:04:52.559Z
+updatedAt: 2024-06-13T21:44:14.602Z
+publishedAt: 2024-06-13T21:44:14.602Z
 firstPublishedAt: 2017-08-01T16:58:04.306Z
 contentType: tutorial
 productTeam: Financial
@@ -20,10 +20,10 @@ Para añadir soporte para [3DS](https://help.vtex.com/es/tutorial/what-is-3d-sec
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
 2. Acceda a la pestaña __Afiliaciones__.
 3. Haga clic en la card de afiliación de Adyen.
-4. Vaya a Live __Endpoint URL Prefix__ y siga este [tutorial](https://www.adyen.help/hc/es/articles/360014322079--C%C3%B3mo-puedo-encontrar-la-URL-del-punto-final-para-mi-cuenta-LIVE-) de Adyen para obtener la información.
+4. Vaya a Live __Endpoint URL Prefix__ y siga este [tutorial](https://help.adyen.com/es_ES/knowledge/ecommerce-integrations/integrations-basics/how-can-i-find-the-endpoint-url-for-my-live-account) de Adyen para obtener la información.
 5. Seleccione la opción __Sí__ en el campo __¿Activar 3D Secure?__.
 6. Elija el modo de 3DS (3DS, 3DS2 o 3DS2 Data only) acordado cuando se creó la asociación comercial con Adyen.
-7. Termine de rellenar los otros campos siguiendo [este tutorial](https://help.vtex.com/es/tutorial/como-configurar-o-gateway-adyen-na-vtex--tutorials_2337).
+7. Termine de rellenar los otros campos siguiendo [este tutorial](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3--7xAz67E2Eg63LWCQNjVdwv).
 8. Haga clic en __Salvar__ para guardar los cambios.
 
 ### Habilitar las respuestas de 3DS
diff --git a/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md b/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md
index b98f65b05..6c82f8051 100644
--- a/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md
+++ b/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md
@@ -24,4 +24,4 @@ La estructura del archivo debe de ser la siguiente:
 - Columna D: Fecha Inicial (Formato: DD/MM/AAAA)
 - Columna E: Fecha Final (Formato: DD/MM/AAAA)
 
-![urlbuilder es](https://images.ctfassets.net/alneenqid6w5/3R4XJx8UHekUASMY6euqAy/24705df3a75db5c4fcc780102689c322/urlbuilder_es.png)
+![urlbuilder es](//images.ctfassets.net/alneenqid6w5/3R4XJx8UHekUASMY6euqAy/24705df3a75db5c4fcc780102689c322/urlbuilder_es.png)
diff --git a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
index 561b20872..8680c1bf9 100644
--- a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
+++ b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
@@ -1,10 +1,10 @@
 ---
-title: 'Registrar Client Id y Client Secret para inicio de sesión con Facebook'
+title: 'Registrar Client ID y Secreto del cliente para Inicio de sesión con Facebook'
 id: 3R7rzXWG1GswWOIkYyy8SO
 status: PUBLISHED
 createdAt: 2017-08-29T17:46:04.080Z
-updatedAt: 2023-02-08T14:33:31.750Z
-publishedAt: 2023-02-08T14:33:31.750Z
+updatedAt: 2023-10-20T21:29:11.632Z
+publishedAt: 2023-10-20T21:29:11.632Z
 firstPublishedAt: 2017-08-29T17:51:41.650Z
 contentType: tutorial
 productTeam: Identity
@@ -15,52 +15,73 @@ legacySlug: registrar-client-id-y-client-secret-para-login-con-facebook
 subcategory: 14V5ezEX0cewOMg0o0cYM6
 ---
 
-Para activar el inicio de sesión de OAuth2 vía Facebook, usted necesita acceder a VTEX ID desde su Admin y rellenar los campos `Client ID` y `Client Secret`, como se explica [en este artículo](/pt/tutorial/integracao-google-e-facebook-para-login).
-
-![Facebook OAuth ES](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/ffc13a1eb81a285feea15e78a72342b9/facebook_ES.png)
-
-Para obtener estos valores, siga los pasos a continuación:
-
-1. Entre en el link [`https://developers.facebook.com/`](https://developers.facebook.com/);
-2. Cree una cuenta de desarrollador de Facebook;
-3. Cree una aplicación de Inicio de sesión con de Facebook;
-4. En la parte superior derecha, haga clic en __Mis apps__;
- ![Mis Apps Facebook ES](https://images.ctfassets.net/alneenqid6w5/2XUFbJ20Z1Op022DLzNru7/7f96fc5e36e1f32d338d8f3cad63b2d8/Meus_Aplicativos_Facebook_ES.png)
-5. Haca clic en Crear app;
-6. Elija __Administrar integraciones comerciales__;  
-    ![Criar ID Aplicativo Facebook ES](https://images.ctfassets.net/alneenqid6w5/4nEHH7m3rzaIjNyXCS7jwQ/db4a8fc8aec751ce1ed1c7e89c1c9407/Facebook_Login_App_Type_ES.png)
-7. En __Nombre para mostrar de la app__, ingrese el nombre que corresponda a su tienda;
-8. De las dos opciones disponibles en __Propósito de la app__, elija la que mejor se adapte a las necesidades de su tienda;
-9. Haga clic en __Crear identificador de la app__;
-    ![Configurar Criação ID Aplicativo Facebook ES](https://images.ctfassets.net/alneenqid6w5/aJ4qEYEBdQXp3IkQwcwBe/d1b7193d89c798ea761aa8f533624930/App_details_ES.png)
-10. Seleccione __Configurar__ en __Inicio de sesión con Facebook__;
-    ![Adicionar Configuração Login Facebook ES](https://images.ctfassets.net/alneenqid6w5/4Kz42ev7FSm0uEYIYwQ8C8/369bbf953861b544ab04c86e6e3d7d87/add_products_ES.png)
-11. En __Productos__, en el panel lateral izquierdo, haga clic en __Inicio de sesión con Facebook > Configuración__.
-    ![Login Configurações Menu Facebook ES](https://images.ctfassets.net/alneenqid6w5/7CosZB53qkywCS1NG3Cj0r/04980ce0595cfcbe1dc4d392236a42ee/menu_configura____es_ES.png)
-    Defina los estados como se indica en la imagen a continuación.
-    ![Configuração URI OAuth Facebook ES](https://images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/1e318e6f8fb6c7465445f7c25fddf883/configuracoes_Oauth_ES.png)
-    Ingrese las URL a continuación en __URI de redireccionamiento de OAuth válidos__, reemplazando `{{HOST_URL}}` por la URL base de su tienda y `{{accountName}}` por el nombre de su cuenta de acuerdo con lo descrito en el menú de administración de la tienda:
-    - `https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
-    - `https://{{HOST_URL}}/api/vtexid/pub/authentication/oauth/authorizationcode`
-    - `https://{{accountName}}.myvtex.com/api/vtexid/pub/authentication/oauth/authorizationcode`
-
-12. Al final de la página, haga clic en el botón __Guardar cambios__.
-    ![Guardar cambios ES](https://images.ctfassets.net/alneenqid6w5/6xrSjyVnjTdpMwK6mmg7qQ/efeb20d6725434cede246d12262f18f7/Salvar_Altera____es_ES.png)
-
-13. Acceda a __Configuración > Básica__ en el panel lateral izquierdo.
-    ![Menu Configurações Aplicativo Facebook ES](https://images.ctfassets.net/alneenqid6w5/2hW7fOAt85ErH30RUI9KLA/43d7a90387cae90c6083b60a27cad765/menu_configura____es_b__sica_ES.png)
-
-14. En __Clave secreta de la aplicación__, haga clic en el botón __Mostrar__.
-    - Copie el campo __Identificador de la aplicación__ y péguelo en el campo `Client ID` en el Admin de VTEX ID.
-    - Copie el campo __Clave secreta de la aplicación__ de la Aplicación de Facebook y péguelo en el campo `Client Secret` en el Admin de VTEX ID.
-    ![ID Clave Facebook ES](https://images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/52d539cc7b482efc811c229213348700/ID_Chave_Facebook_ES.png)
-
-15. Ingrese un ícono para su aplicación de exactamente 1024x1024 píxeles y con fondo transparente;
-16. Agregue la __URL de la Política de privacidad__ de su tienda;
-    ![Configuración Básica Facebook ES](https://images.ctfassets.net/alneenqid6w5/66rxFKyvG7eCptwC7BdSWT/bf35bc1ed1326cb9f798f5c98a5a73a7/Configura____o_B__sica_Facebook_ES.png)
-17. Seleccione una __Categoría__. Para tiendas, sugerimos utilizar __Compras__;
-    ![Categoría Facebook ES](https://images.ctfassets.net/alneenqid6w5/20X5DqI7WEuGwksOO6cMS2/d33b98069ae6e0aee3888c173a524f3b/Categoria_Facebook_ES.png)
-18. En la parte inferior del formulario, ingrese la __Información de contacto del delegado de protección de datos__ con los datos de la empresa responsable de la tienda;
-    ![Dirección Facebook ES](https://images.ctfassets.net/alneenqid6w5/3TenJ8YunJ6gFRs0aZQkp7/81405fa9f3849e91bea5363f3a6ce239/Endere__o_Facebook_ES.png)
-19. Al final de la página, haga clic en __Guardar cambios__;
-    ![Guardar Cambios ES](https://images.ctfassets.net/alneenqid6w5/6xrSjyVnjTdpMwK6mmg7qQ/efeb20d6725434cede246d12262f18f7/Salvar_Altera____es_ES.png)
+Para activar el inicio de sesión por OAuth2 a través de Facebook, accede al Admin VTEX > **Configuración de cuenta > Autenticación** y completa los campos **Client ID** y **Secreto del cliente**, tal como se describe en el artículo [Configurar inicio de sesión con Facebook y Google](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
+
+![Facebook OAuth ES](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/e85e70614c1ff706937104c8f5ec917c/1-login-fb-es.PNG)
+
+Para obtener las credenciales, sigue las instrucciones en las secciones a continuación:
+
+1. [Crear aplicación](#1-crear-aplicacion)
+2. [Configurar Inicio de sesión con Facebook en la aplicación](#2-configurar-inicio-de-sesion-con-facebook-en-la-aplicacion)
+3. [Realizar la configuración básica de la aplicación](#3-realizar-la-configuracion-basica-de-la-aplicacion)
+
+## 1. Crear aplicación
+
+Para empezar, debes registrar una aplicación en Facebook siguiendo los pasos a continuación:
+
+1. Accede a la página web [Meta for Developers](https://developers.facebook.com/).
+2. Crea una cuenta de Meta for Developers.
+3. En la barra superior, haz clic en **Mis apps**.
+4. Haz clic en `Crear app`.
+5. Haz clic en **Permitir que las personas inicien sesión con su cuenta de Facebook** entre las opciones que se ilustran a continuación.
+
+   ![2-login-fb-es](//images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/077ab05e546169ba636a59aca0281498/2-login-fb-es.png)
+
+6. Haz clic en `Siguiente`.
+7. Añade el nombre de la aplicación y el correo electrónico de contacto de la persona responsable de la aplicación en los campos que se ilustran a continuación.
+
+   ![3-login-fb-es](//images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/d2dc7a5cb5d859f25a892ad3e93575fe/3-login-fb-es.png)
+
+8. Haz clic en `Crear app`.
+
+## 2. Configurar el Inicio de sesión con Facebook en la aplicación
+
+El siguiente paso es configurar el producto Inicio de sesión con Facebook en la aplicación que creaste. Para hacerlo, sigue las instrucciones a continuación:
+
+1. Haz clic en **Productos** en el menú lateral o en el **panel **de Meta for Developers, resaltado en la imagen siguiente.
+
+   ![4-login-fb-es](//images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/967682b6e1942ed15ab2c40d75f8a4f0/4-login-fb-es.png)
+
+2. Haz clic en `Configurar` y después selecciona `Configurar` en el menú desplegable.
+
+   ![5-login-fb-es](//images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/3c181d675c97d893402af45974d65e95/5-login-fb-es.png)
+
+3. Define los estados como se detalla a continuación:
+
+   ![Configuração URI OAuth Facebook ES](//images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/1e318e6f8fb6c7465445f7c25fddf883/configuracoes_Oauth_ES.png)
+
+   Inserta las URL siguientes en **URI de redireccionamieno de OAuth válidos**, sustituyendo `{{HOST_URL}}`  por la URL base de tu tienda y `{{accountName}}` por el nombre de tu cuenta tal y como se describe en el menú de administración de la tienda:   
+
+      * `https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
+      * `https://{{HOST_URL}}/api/vtexid/pub/authentication/oauth/authorizationcode`
+      * `https://{{accountName}}.myvtex.com/api/vtexid/pub/authentication/oauth/authorizationcode`
+
+4. En la parte inferior de la página, haz clic en el botón `Guardar cambios`.
+
+## 3. Realizar la configuración básica de la aplicación
+
+Por último, debes rellenar algunos datos sobre la aplicación para completar el proceso de registro. En este paso obtendrás el **Client ID** y el **Secreto del cliente** que se utilizarán en la configuración de inicio de sesión con Facebook realizada en el Admin VTEX. Sigue los pasos a continuación:
+
+1. En el menú lateral de Meta for Developers, haz clic en **Configuración de la aplicación** y después en **Básica:**
+
+   ![7-login-fb-es](//images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/f84756573e40f40e8f94c062e68da397/7-login-fb-es.png)
+
+2. Copia el valor del campo **Identificador de la aplicación**. Debes ingresar este valor en el campo **Client ID** al [configurar el Inicio de sesión con Facebook en el Admin VTEX](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
+3. En **Clave secreta de aplicación**, haz clic en el botón **Mostrar** y, a continuación, copia el valor del campo. Debes ingresar este valor en el campo **Secreto del cliente** al [configurar el inicio de sesión con Facebook en el Admin VTEX](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
+4. En el campo **URL de la política de privacidad**, ingresa el link a la política de privacidad de tu tienda.
+5. En **Icono de la aplicación (1024 x 1024)**, inserta un ícono de exactamente 1024x1024 píxeles y fondo transparente.
+6. Selecciona una **Categoría**. Para tiendas, te sugerimos seleccionar **Compras**.
+7. Después, ingresa la **información de contacto del delegado de protección de datos** con los datos de la empresa responsable de la tienda.
+8. Haz clic en `Guardar cambios` en la parte inferior de la página.
+
+Después de completar todas estas etapas ya puedes utilizar el **Client ID** y el **Secreto del cliente** obtenidos para configurar el Inicio de sesión con Facebook en tu tienda, tal como se describe en el artículo [Configurar inicio de sesión con Facebook y Google](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
diff --git a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
index 1b05e2bec..329e7d5e8 100644
--- a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
+++ b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Para habilitar el inicio de sesión por OAuth2 vía Google, usted necesita acceder al VTEX ID por su Admin y rellenar los campos `Client ID` y `Client Secret`, como se detalla en [este artículo](/pt/tutorial/integracao-google-e-facebook-para-login).
 
-![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
+![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
 
 Estos valores se obtienen de un proyecto que debe ser creado en el servicio de APIs de la plataforma de Google Cloud Platform.
 
@@ -30,17 +30,17 @@ Los siguientes pasos describen procedimientos en una plataforma externa y pueden
 1. Entre en el enlace [`https://console.developers.google.com/`](https://console.developers.google.com/);
 2. Haga clic en __Credenciales__, en la pestaña lateral;
 3. Haga clic en __Crear Proyecto__;
-    ![Criar Projeto Google ES](https://images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/7ae1980ea25092ef02e7f1952370fbd9/Criar_Projeto_Google_ES.png)
+    ![Criar Projeto Google ES](//images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/7ae1980ea25092ef02e7f1952370fbd9/Criar_Projeto_Google_ES.png)
 4. Defina el nombre del proyecto y haga clic en __Crear__;
-    ![Novo Projeto Google ES](https://images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/56b4d080ea4da99a5d626fc3c0329261/Novo_Projeto_Google_ES.png)
+    ![Novo Projeto Google ES](//images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/56b4d080ea4da99a5d626fc3c0329261/Novo_Projeto_Google_ES.png)
 5. En la parte superior de la página, haga clic en el botón __Crear credenciales__;
-    ![Criar Credenciais Google ES](https://images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/25ac7be759c40d281dc4bd2cb817ecc4/Criar_Credenciais_Google_ES.png)
+    ![Criar Credenciais Google ES](//images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/25ac7be759c40d281dc4bd2cb817ecc4/Criar_Credenciais_Google_ES.png)
 6. Haga clic en la opción __ID de cliente de OAuth__;
-    ![ID cliente OAuth Google ES](https://images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/4a2d0e88620740449f9240d87e8dec7e/ID_cliente_OAuth_Google_ES.png)
+    ![ID cliente OAuth Google ES](//images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/4a2d0e88620740449f9240d87e8dec7e/ID_cliente_OAuth_Google_ES.png)
 7. Haga clic en el botón __Configurar página de consentimiento__;
-    ![Configurar Tela Consentimento Google ES](https://images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/9db551614331a844bf870661fac5d7bf/Configurar_Tela_Consentimento_Google_ES.png)
+    ![Configurar Tela Consentimento Google ES](//images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/9db551614331a844bf870661fac5d7bf/Configurar_Tela_Consentimento_Google_ES.png)
 8. Elija el tipo de usuario que desea para su tienda (__Interno__ o __Externo__) y haga clic en el botón __Crear__;
-    ![Tipo usuário Google ES](https://images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/f153fed0cf0864141b55c83932558d28/Tipo_usu__rio_ES.png)
+    ![Tipo usuário Google ES](//images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/f153fed0cf0864141b55c83932558d28/Tipo_usu__rio_ES.png)
 9.  __Nombre de aplicación__: se mostrará a sus clientes al iniciar sesión;
 10. __Correo electrónico de asistencia del usuario__: para que los usuarios se comuniquen contigo si tienen preguntas sobre su consentimiento;
 11. __Logotipo de la app__: corresponde al logotipo de su tienda;
@@ -49,19 +49,19 @@ Los siguientes pasos describen procedimientos en una plataforma externa y pueden
     - `vtex.com.br`, referente a nuestros servidores BackEnd.
 13. __Información de contacto del desarrollador__: Google enviará notificaciones sobre cualquier cambio en tu proyecto a estas direcciones de correo electrónico;
 14. Haga clic en el botón  __Guardar y continuar__;
-    ![Configurações Tela Consentimento ES](https://images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4db11d3ef54d615651a84aafe086df4c/Configura____es_Tela_Consentimento_ES.png)
+    ![Configurações Tela Consentimento ES](//images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4db11d3ef54d615651a84aafe086df4c/Configura____es_Tela_Consentimento_ES.png)
 13. Haga clic en __Credenciales__, en el menú lateral izquierdo;
 14. Elija __Aplicación web__, en Tipo de aplicación;
-    ![Credenciais Aplicativo Web Google ES](https://images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/7253773b80efb5e1c5d1074dec6a578e/Credenciais_Aplicativo_Web_Google_ES.png)
+    ![Credenciais Aplicativo Web Google ES](//images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/7253773b80efb5e1c5d1074dec6a578e/Credenciais_Aplicativo_Web_Google_ES.png)
 15. __Nombre__: para identificación interna;
 16. __Orígenes de JavaScript autorizados__: registrar las direcciones exactas que podrán usar este método de autenticación, lo que corresponde a su sitio web; por ejemplo, `https://www.tienda.com`. También se recomienda registrar la dirección `https://{{accountName}}.myvtex.com` de su cuenta, `{{accountName}}` es el nombre de la cuenta como se describe en el menú de administración de la tienda;
 17. __URIs de redireccionamiento autorizados__: registrar la URL de servicio de VTEX:
     -`https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
-    ![Configurações Aplicativo Web Google ES](https://images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/56174b702c831b3154fac9e2dbc45e21/Configura____es_Aplicativo_Web_ES.png)
+    ![Configurações Aplicativo Web Google ES](//images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/56174b702c831b3154fac9e2dbc45e21/Configura____es_Aplicativo_Web_ES.png)
 
 18. Después de completar este ajuste, se presentarán sus credenciales:
-    ![Cliente OAuth criado Google ES](https://images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/7d36d109c612b4efa19410bd65da54c1/Cliente_OAuth_criado_Google_ES.png)
+    ![Cliente OAuth criado Google ES](//images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/7d36d109c612b4efa19410bd65da54c1/Cliente_OAuth_criado_Google_ES.png)
     - Copie el __ID de cliente__ de Google y péguelo en el campo `Client Id` en el Admin de VTEX ID.
     - Copie su __clave secreta de cliente__ de Google y péguelo en el campo `Client Secret` en el Admin de VTEX ID.
-    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
+    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
     Una vez que haya completado todos estos pasos, guarde los cambios. 
diff --git a/docs/tutorials/es/adding-a-record-on-a-master-data-form.md b/docs/tutorials/es/adding-a-record-on-a-master-data-form.md
new file mode 100644
index 000000000..de574821b
--- /dev/null
+++ b/docs/tutorials/es/adding-a-record-on-a-master-data-form.md
@@ -0,0 +1,57 @@
+---
+title: 'Agregar un registro en un formulario de Master Data'
+id: tutorials_6264
+status: PUBLISHED
+createdAt: 2017-04-27T21:48:37.277Z
+updatedAt: 2024-07-17T21:25:51.382Z
+publishedAt: 2024-07-17T21:25:51.382Z
+firstPublishedAt: 2017-04-27T23:11:18.994Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: agregar-un-registro-en-un-formulario-de-master-data
+locale: es
+legacySlug: como-incluir-un-registro-en-un-formulario-del-master-data
+subcategory: 42hDtnYXHw5ExG6l19RP1l
+---
+
+
+Para agregar un registro en un formulario de Master Data, debes acceder a Master Data y seleccionar la aplicación que deseas ver siguiendo las instrucciones que se detallan en las secciones a continuación.
+
+Los campos pueden configurarse como editables o no editables directamente en la entidad de datos. Más información en [Entidad de datos](https://help.vtex.com/es/tutorial/entidade-de-dados--tutorials_1265).
+
+<div class="alert alert-warning">
+Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar la versión de Master Data que es más adecuada para tu operación o verificar la que esté en uso. Más información:
+<ul>
+<li>
+<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+Características de las versiones de Master Data
+</a>
+</li>
+<li>
+<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+Master Data v2
+</a>
+</li>
+</ul>
+</div>
+
+## Agregar un registro
+
+Para guardar un nuevo registro, como el perfil de un nuevo cliente, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En la aplicación, busca la fila del formulario al que deseas agregar un registro y haz clic en Nuevo <i class="fas fa-plus-circle"></i>.
+3. Rellena los campos del formulario.
+4. Haz clic en `Guardar`.
+
+## Editar un registro
+
+Para editar un registro existente, como por ejemplo la información de un cliente de la tienda, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En la aplicación, busca la fila del formulario que contiene el registro que deseas editar y haz clic en el ícono de lápiz <i class="fas fa-bars"></i>.
+3. Si lo deseas, busca el registro utilizando un campo que se haya configurado como buscable en la entidad de datos.
+4. Haz clic en el ícono de editar <i class="fas fa-edit"></i> en la fila del registro que deseas editar.
+5. Realiza los cambios deseados.
+6. Haz clic en `Guardar`.
diff --git a/docs/tutorials/es/adding-an-attachment.md b/docs/tutorials/es/adding-an-attachment.md
index 89e8d5cae..c97a9cf78 100644
--- a/docs/tutorials/es/adding-an-attachment.md
+++ b/docs/tutorials/es/adding-an-attachment.md
@@ -3,8 +3,8 @@ title: 'Registrar un anexo'
 id: 7zHMUpuoQE4cAskqEUWScU
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:42.901Z
-updatedAt: 2023-03-29T15:07:58.328Z
-publishedAt: 2023-03-29T15:07:58.328Z
+updatedAt: 2023-11-16T17:23:31.034Z
+publishedAt: 2023-11-16T17:23:31.034Z
 firstPublishedAt: 2019-01-24T22:06:25.639Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -31,7 +31,7 @@ El objetivo de un anexo es [complementar el producto con una información person
 Después de realizar el registro inicial del anexo, es necesario añadir las claves y los **Valores permitidos** relacionados con el anexo creado. Puede añadir las claves que desee. Para añadir las claves y los **Valores permitidos**, realice los siguientes pasos.
 
 1. En la página **Campos personalizados**, identifique la línea del anexo creado y haga clic en `Editar`, como se ilustra en la siguiente imagen.
-    ![anexos.pt](https://images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/e56ba5ba51d3c9e60593faa82eb4d790/custom-product-attributes-es.PNG)
+    ![anexos.pt](//images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/e56ba5ba51d3c9e60593faa82eb4d790/custom-product-attributes-es.PNG)
 2. Complete los campos indicados a continuación.
     * **Nombre de la clave:** nombre de la información personalizada. Este campo es obligatorio y no puede contener caracteres especiales, solo letras, números o puntos. Ejemplo: si el producto personalizable es una camiseta de la selección brasileña, los nombres de sus claves pueden ser `Nombre` y `Número`.
     * **Máximo de caracteres:** número máximo de caracteres que el cliente puede digitar para introducir una información personalizada en el producto. Este campo es obligatorio. Ejemplo: en este campo puede definir el límite de caracteres para el nombre que se imprimirá en una camiseta.
diff --git a/docs/tutorials/es/adding-bin-information.md b/docs/tutorials/es/adding-bin-information.md
new file mode 100644
index 000000000..930d62e0c
--- /dev/null
+++ b/docs/tutorials/es/adding-bin-information.md
@@ -0,0 +1,42 @@
+---
+title: 'Registrar información de BIN'
+id: 7xvo4JJ53WM7aLzufdC4au
+status: PUBLISHED
+createdAt: 2024-05-02T19:11:00.734Z
+updatedAt: 2024-05-03T13:40:32.363Z
+publishedAt: 2024-05-03T13:40:32.363Z
+firstPublishedAt: 2024-05-02T19:44:35.388Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: registrar-informacion-de-bin
+locale: es
+legacySlug: registrar-informacion-de-bin
+subcategory: 2Xay1NOZKE2CSqKMwckOm8
+---
+
+El número de identificación bancaria (BIN) se compone de los primeros seis u ocho dígitos de una tarjeta de crédito o débito y caracteriza la entidad emisora de la tarjeta.
+
+![BIN_image_digits_ES_2](//images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/474de4b5b02f9be016dd9aae13d83b4a/BIN_image_digits_ES_2.png)
+
+Cuando la entidad emisora desea crear nuevos perfiles de tarjetas o emitir nuevas tarjetas para un modelo existente, debe crear nuevos BIN. Esto también se aplica cuando una [bandera de tarjeta](https://help.vtex.com/es/tutorial/que-es-una-bandera-de-tarjeta-de-credito--4bNba5QYuIwKEmac88KwyI) es adquirida por otra.
+
+En estos casos, se debe notificar a VTEX para permitir que las nuevas tarjetas se validen de forma correcta en el proceso de pago durante una compra realizada en la plataforma.
+
+## Solicitar la inclusión de BIN
+
+Para agegar un BIN o actualizar la información de un BIN existente en VTEX, debes abrir un ticket con el [Soporte VTEX](https://help.vtex.com/es/support).
+
+El ticket debe incluir como adjunto una plantilla rellenada con la siguiente información:
+
+- __code__: el nuevo BIN que se debe agregar o el BIN existente que se debe actualizar.
+- __cardBrand__: red de la tarjeta correspondiente al BIN.
+- __cardType__: tipo de tarjeta (crédito o débito).
+- __country__: país de utilización de la tarjeta.
+- __bank__: banco emisor de la tarjeta.
+- __cvvSize__: número de caracteres del CVV (Card Verification Value).
+- __cardLevel__: clasificación de la tarjeta (Gold, Platinum, Black, entre otros).
+
+Modelo de plantilla rellenada:
+
+![Bin_spreadsheet](//images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/34d0045e509662b159b442818a9854f6/Bin_spreadsheet.PNG)
diff --git a/docs/tutorials/es/adding-collections-cms.md b/docs/tutorials/es/adding-collections-cms.md
index 609090740..6e8e8e34c 100644
--- a/docs/tutorials/es/adding-collections-cms.md
+++ b/docs/tutorials/es/adding-collections-cms.md
@@ -33,7 +33,7 @@ Cuando la cantidad de colecciones creadas supera el límite de veinte, las colec
 
 La elección de los productos que van a hacer parte de una colección se hace a través de la creación de un __grupo__. Para esto, basta con hacer clic en __New Group__ dentro de la colección deseada. 
 
-![2019-06-06 16 22 46-Layout](https://images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
+![2019-06-06 16 22 46-Layout](//images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
 
 Antes de escoger qué productos harán parte del grupo, como veremos a continuación, es necesario atribuir un nombre y especificar el tipo de grupo creado.
 
@@ -75,17 +75,17 @@ Por ejemplo: al seleccionar la categoría `A` y la marca `B`, apenas los product
 
 Para agregar todos los productos de un determinado Departamento a un grupo, basta con seleccionar el Departamento deseado y hacer clic en __Save Group__, como muestra la imagen a continuación. 
 
-![seleção-departamento ES](https://images.ctfassets.net/alneenqid6w5/dpKPktmtrMoOqVwdkTgGe/6c5ecc0f0446688acbe62f725811830b/sele____o-departamento_ES.png)
+![seleção-departamento ES](//images.ctfassets.net/alneenqid6w5/dpKPktmtrMoOqVwdkTgGe/6c5ecc0f0446688acbe62f725811830b/sele____o-departamento_ES.png)
 
 Lo mismo aplica para los productos de una determinada Categoría o Subcategoría.
 
-![seleção-categoria-subcategoria ES](https://images.ctfassets.net/alneenqid6w5/669cvCxhxCDtUObugHirqT/41a3b8cccc9e832a74452ce97256f8d5/sele____o-categoria-subcategoria_ES.png)
+![seleção-categoria-subcategoria ES](//images.ctfassets.net/alneenqid6w5/669cvCxhxCDtUObugHirqT/41a3b8cccc9e832a74452ce97256f8d5/sele____o-categoria-subcategoria_ES.png)
 
 ## Productos por Marca
 
 Para crear un grupo con productos de una o más marcas, basta con seleccionar la marca deseada en la lista correspondiente. 
 
-![seleção-marca-coleção ES](https://images.ctfassets.net/alneenqid6w5/7iBwt7BrU46rtjQagSZCtg/9b061b4b72ae669caa7b510e7db8f29f/sele____o-marca-cole____o_ES.png)
+![seleção-marca-coleção ES](//images.ctfassets.net/alneenqid6w5/7iBwt7BrU46rtjQagSZCtg/9b061b4b72ae669caa7b510e7db8f29f/sele____o-marca-cole____o_ES.png)
 
 Las marcas se encuentran dispuestas en orden alfabética. Al hacer clic en la letra correspondiente a la inicial de la marca deseada, la lista se expande y exhibe las marcas existentes. 
 
@@ -95,7 +95,7 @@ Las marcas se encuentran dispuestas en orden alfabética. Al hacer clic en la le
 
 Al agregar un SKU a un grupo, el producto al cual está vinculado también será agregado. En un escenario en el que un producto tenga más de un SKU atribuido, agregar un único SKU hará con que todos los otros también sean agregados al grupo.  
 
-![selecao-sku-manual en & es](https://images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
+![selecao-sku-manual en & es](//images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
 
 En el campo __Find SKUs__, es posible digitar el ID de cuantos SKUs se deseen, escribiendo los valores entre comas. 
 
@@ -117,21 +117,21 @@ Obtenga el modelo de archivo para la inclusión y exclusión de SKUs de la colec
 
 En el campo __Bulk Insert SKUs__, es posible importar por plantilla (formato `.xls`) una lista de SKUs que harán parte del grupo.
 
-![selecao-sku-planilha-insert en & es](https://images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
+![selecao-sku-planilha-insert en & es](//images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
 
 En la plantilla importada, todos los IDs de los SKUs deben estar dispuestos en la primera columna, con el encabezado, como se ejemplifica en la siguiente figura: 
 
-![exemplo-planilha-seleção-sku-coleção](https://images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
+![exemplo-planilha-seleção-sku-coleção](//images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
 
 Después de seleccionar la plantilla deseada, haga clic en la opción __import skus__ para enviar la información.
 
-![Import SKUs](https://images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
+![Import SKUs](//images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
 
 #### Exclusión masiva 
 
 Para evitar la exclusión manual de un SKU a la vez, también es posible usar el recurso de importación de plantilla para la exclusión masiva.
 
-![exclusao-skus-manualmente-planilha-coleção-cms en & es](https://images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
+![exclusao-skus-manualmente-planilha-coleção-cms en & es](//images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
 
 En este caso específico, los SKUs listados en la plantilla importada se excluirán del  grupo. Para esto, haga clic en la opción __remove skus__ después que el archivo sea cargado.
 
@@ -147,7 +147,7 @@ En la sección de <strong>Other options</strong>, las opciones <strong>Pre-sales
 
 Note que apenas es posible seleccionar una de las dos opciones. Si quiere que se contemplen ambos escenarios, cree dos grupos y configure cada uno con la respectiva opción.
 
-![other-options-cms-coleções ES](https://images.ctfassets.net/alneenqid6w5/4MijWxcZbcIjsVvHl3AcCB/14a9f700d992c28b2afb959829609bd1/other-options-cms-cole____es_ES.png)
+![other-options-cms-coleções ES](//images.ctfassets.net/alneenqid6w5/4MijWxcZbcIjsVvHl3AcCB/14a9f700d992c28b2afb959829609bd1/other-options-cms-cole____es_ES.png)
 
 ### Pre-sales
 
diff --git a/docs/tutorials/es/adding-sku-specifications-or-fields.md b/docs/tutorials/es/adding-sku-specifications-or-fields.md
index ee6bf177f..4085ff0c8 100644
--- a/docs/tutorials/es/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/es/adding-sku-specifications-or-fields.md
@@ -3,8 +3,8 @@ title: 'Registrar especificaciones o campos de SKU'
 id: tutorials_119
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:08.662Z
-updatedAt: 2023-03-29T17:31:34.699Z
-publishedAt: 2023-03-29T17:31:34.699Z
+updatedAt: 2023-11-30T12:05:25.945Z
+publishedAt: 2023-11-30T12:05:25.945Z
 firstPublishedAt: 2017-04-27T23:00:44.181Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: criando-campo-de-sku
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-La especificación de SKU es un campo en el registro del SKU en el cual se ingresan las características específicas para cada variación de un producto.
+La especificación de SKU es un campo obligatorio en el registro del SKU en el cual se ingresan las características específicas para cada variación de un producto.
 
 En VTEX, una especificación siempre forma parte de un [grupo de especificaciones](https://help.vtex.com/es/tutorial/criando-grupo-de-categoria--tutorials_246) que está asociado a una [categoría](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf). Es precisamente por esto que, para crear una especificación (campo) del SKU, debe existir, al menos, el registro de una categoría y de un grupo de especificaciones.
 
@@ -43,7 +43,7 @@ Antes de crear especificaciones, es importante entender que las especificaciones
 
 Por ejemplo: tomemos el producto **Camisa masculina**. En __Catálogo > Productos y SKU > SKU > Especificaciones__ (en la imagen a continuación), se puede ver que el grupo de especificaciones llamado **Características** está asociado a la categoría de la camisa. Ese grupo incluye un campo llamado **Color** y un campo llamado **Tamaño**.
 
-![heranca-especificacoes-sku-es](https://images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/da96d3be83a3131b2eb3af35cb7f40fc/sku-specifications-inheritance-es.PNG)
+![heranca-especificacoes-sku-es](//images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/da96d3be83a3131b2eb3af35cb7f40fc/sku-specifications-inheritance-es.PNG)
 
 Como se trata de una especificación del SKU, la información seleccionada en esa página se validará únicamente para esa variación del producto **Camisa masculina**. Se deben haber ingresado esas especificaciones de todos los SKU registrados en el producto **Camisa masculina** y todos los SKU de productos de la misma categoría.
 
@@ -85,7 +85,7 @@ Para crear un campo del SKU, sigue las instrucciones a continuación:
     * **Activo**: inserta o elimina este campo en el registro del SKU.
 7. Haz clic en `Guardar`.
 
-![sku-spec-1](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/849a49c91c0d22674c810c59e025ece3/es-sku-spec-2.gif)
+![sku-spec-1](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/849a49c91c0d22674c810c59e025ece3/es-sku-spec-2.gif)
 
 #### Tipos de campo de SKU
 
@@ -130,13 +130,13 @@ Los **valores** de los campos del SKU variarán según el tipo de campo elegido:
 
     Inserta un valor por línea y haz clic en la tecla `Enter` entre un valor y otro, tal como se muestra en la imagen a continuación.
 
-    ![valores-campo-sku-es](https://images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/07d380bbf447d55bab05d846b4202501/valores-especificacoes-sku-es.PNG)
+    ![valores-campo-sku-es](//images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/07d380bbf447d55bab05d846b4202501/valores-especificacoes-sku-es.PNG)
 
 8. Haz clic en `Guardar`.
 
     Los valores registrados se mostrarán en la [interfaz del registro del SKU](#registro-del-sku).
 
-![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/157aeb729b88c61a3341697b60008c7c/es-sku-spec-2.gif)
+![sku-spec-2](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/157aeb729b88c61a3341697b60008c7c/es-sku-spec-2.gif)
 
 <div class = "alert alert-info">
   <p>Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción <strong>Activo</strong>.</p>
@@ -181,7 +181,7 @@ Para completar las especificaciones de cada SKU de forma individual, sigue las i
 
 8. Haz clic en `Guardar`.
 
-![sku-spec-3](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/60cd4ea95d71f88edc9df50717d96ab7/es-sku-spec-3.gif)
+![sku-spec-3](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/60cd4ea95d71f88edc9df50717d96ab7/es-sku-spec-3.gif)
 
 #### Plantilla
 
@@ -204,7 +204,7 @@ Para rellenar las especificaciones del SKU de forma masiva por plantilla, debes
 9. Haz clic en **Seleccionar** para seleccionar el archivo con la plantilla completa en la computadora.
 10.  Haz clic en `Importar`.
 
-![sku-spec-4](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/0f468d1b9b92ac4b64aee8251491aaf1/es-sku-spec-4.gif)
+![sku-spec-4](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/0f468d1b9b92ac4b64aee8251491aaf1/es-sku-spec-4.gif)
 
 ## Más información
 - [Registrar especificaciones o campos de producto](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-producto--tutorials_106)
diff --git a/docs/tutorials/es/adding-specifications-or-product-fields.md b/docs/tutorials/es/adding-specifications-or-product-fields.md
index e87f6d0cd..f9ebb9b52 100644
--- a/docs/tutorials/es/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/es/adding-specifications-or-product-fields.md
@@ -43,7 +43,7 @@ Antes de crear especificaciones, es importante entender que las especificaciones
 
 Tomemos como ejemplo el producto **Televisor**. En __Catálogo > Productos y SKU > Modificar > Especificaciones__, en la imagen que vemos a continuación, se puede ver que el grupo de especificaciones llamado **Características** está asociado a la categoría de televisor. Ese grupo incluye un campo llamado **Pulgadas** y un campo llamado **Rango etario** que son obligatorios.
 
-![especificaciones-es](https://images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/1dba4d4f967811f7b3f0a22872a2734d/especificaciones-es.PNG)
+![especificaciones-es](//images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/1dba4d4f967811f7b3f0a22872a2734d/especificaciones-es.PNG)
 
 Como se trata de una especificación de producto, la información seleccionada en esa página será válida para todas las variaciones del producto **Televisor**. Estas especificaciones también deben haber sido rellenadas en todos los productos registrados en la misma categoría de televisor porque son campos obligatorios.
 
@@ -80,7 +80,7 @@ Para crear un campo de producto, sigue los pasos a continuación:
     * **Activo**: inserta o elimina este campo en el registro del producto (pestaña **Especificaciones**).
 7. Haz clic en `Guardar`.
 
-![product-spec-1](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/26805d3f463bbfeb47e8cbcb7a023005/ES_ProdutoGif_1_Alterado.gif)
+![product-spec-1](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/26805d3f463bbfeb47e8cbcb7a023005/ES_ProdutoGif_1_Alterado.gif)
 
 #### Tipos de campo de producto
 
@@ -146,7 +146,7 @@ Sin embargo, para los campos **Combo**, **Radio** y **Checkbox** es necesario re
 
     Los valores creados se mostrarán en la pestaña **Especificaciones** en el registro de Producto.
 
-![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/35fc1b6e4edc189e4d4195d35f777514/ES_ProdutoGif_2_Alterado.gif)
+![product-spec-2](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/35fc1b6e4edc189e4d4195d35f777514/ES_ProdutoGif_2_Alterado.gif)
 
 <div class = "alert alert-info">
   <p>Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción <strong>Activo</strong>.</p>
@@ -188,7 +188,7 @@ Para rellenar las especificaciones de cada producto individualmente, siga las  i
 
 6. Haz clic en `Guardar`.
 
-![product-spec-3](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/2f3c1e78b21f035b190aa3adcc55c8c2/ES_ProdutoGif_3_Alterado.gif)
+![product-spec-3](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/2f3c1e78b21f035b190aa3adcc55c8c2/ES_ProdutoGif_3_Alterado.gif)
 
 #### Plantilla
 
@@ -211,7 +211,7 @@ Para rellenar las especificaciones de los productos de forma masiva mediante una
 9. Haz clic en **Seleccionar** para seleccionar el archivo con la plantilla completada en su ordenador.
 10. Haz clic en `Importar`.
 
-![product-spec-4](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/fbb88c9ededec1bef032d9276837059e/ES_ProdutoGif_4_Alterado.gif)
+![product-spec-4](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/fbb88c9ededec1bef032d9276837059e/ES_ProdutoGif_4_Alterado.gif)
 
 ## Más información
 - [Registrar especificaciones o campos de SKU](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-sku--tutorials_119)
diff --git a/docs/tutorials/es/additional-shipping-costs.md b/docs/tutorials/es/additional-shipping-costs.md
index f72441610..9134e04bc 100644
--- a/docs/tutorials/es/additional-shipping-costs.md
+++ b/docs/tutorials/es/additional-shipping-costs.md
@@ -17,7 +17,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Los adicionales de flete son importes que se añaden al costo de envío mediante las [políticas de envío](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Así, al configurar un valor de costo para la entrega de los ítems de su tienda, puede establecer una tarifa fija e incluir valores adicionales. El costo de envío fijo más los adicionales constituyen el costo de la [tarifa de envío](https://help.vtex.com/pt/tutorial/gerenciar-valores-de-frete--tutorials_141).
 
-![Tarifa envio ES](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
+![Tarifa envio ES](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
 
 Los valores adicionales pueden configurarse según:
 
@@ -29,7 +29,7 @@ Los valores adicionales pueden configurarse según:
 * El costo de envío: 
 [adicional de flete](https://help.vtex.com/es/tutorial/adicionales-de-flete--2vqGwMn0LabkOHY6zSHYNV#adicional-de-flete).
 
-![adicionais frete ES](https://images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/9aef6304664af38fa0a9c03ed1916f7e/adicionais_frete_ES.svg)
+![adicionais frete ES](//images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/9aef6304664af38fa0a9c03ed1916f7e/adicionais_frete_ES.svg)
 
 <div class="alert alert-danger">
 Es posible tener todos los adicionales configurados al mismo tiempo para una única tarifa de envío. El cálculo final de la <a href="https://help.vtex.com/es/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">tarifa de envío</a> es la suma de todos los adicionales registrados más la tarifa fija del flete. 
@@ -62,7 +62,7 @@ Adicional de flete: ($10+$0+$2+$5)x10%=$1,70
 Adicionales de flete: ($2+$5+$1,7)=$8,70  
 Tarifa de envío: ($10+$8,70)=$18,70  
 
-![faixa-peso ES](https://images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/2af51a115ce00bd21c47e0d38fbea3d1/faixa-peso_ES.png)
+![faixa-peso ES](//images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/2af51a115ce00bd21c47e0d38fbea3d1/faixa-peso_ES.png)
 
 ### Configuración 
 
@@ -162,5 +162,5 @@ Para configurar el adicional de flete, vaya al menú del Admin.
     1. Si desea incluir una tasa del 10%, rellene el campo con 10. Para los números decimales, utilice puntos en lugar de comas, como en 1.67.
 3. Haga clic en `Guardar`.
 
-![adicional configuracoes ES](https://images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/9e15747bc9585ee7467ecad7c06ecc7e/adicional_configuracoes_ES.png)
+![adicional configuracoes ES](//images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/9e15747bc9585ee7467ecad7c06ecc7e/adicional_configuracoes_ES.png)
 
diff --git a/docs/tutorials/es/admin-redirect-search-returns-no-results.md b/docs/tutorials/es/admin-redirect-search-returns-no-results.md
new file mode 100644
index 000000000..f1e6aa23b
--- /dev/null
+++ b/docs/tutorials/es/admin-redirect-search-returns-no-results.md
@@ -0,0 +1,110 @@
+---
+title: 'La búsqueda de redirecciones en el Admin no devuelve resultados'
+id: 2u5cJhUSVM6bbEAFkgUww7
+status: PUBLISHED
+createdAt: 2024-07-24T13:41:02.016Z
+updatedAt: 2024-07-24T14:33:50.131Z
+publishedAt: 2024-07-24T14:33:50.131Z
+firstPublishedAt: 2024-07-24T14:13:11.586Z
+contentType: tutorial
+productTeam: Others
+author: 4ubliktPJIsvyl1hq91RdK
+slug: la-busqueda-de-redirecciones-en-el-admin-no-devuelve-resultados
+locale: es
+legacySlug: la-busqueda-de-redirecciones-en-el-admin-no-devuelve-resultados
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palabras clave:** redirección
+
+Cuando hay un número excesivo de redirecciones, la página Redirecciones del Admin no puede procesar la búsqueda. Por lo tanto, al intentar realizarla, no se obtiene ningún resultado. Para más información sobre la página Redirecciones, consulta el artículo [Gestionar redirecciones según el binding](https://help.vtex.com/es/tutorial/administrando-redireccionamientos-de-url-por-binding--67GAK2TCQgjvmtPXxAqREb).
+
+## Solución
+
+Sigue los pasos a continuación para obtener las redirecciones:
+
+1. Accede a la página de **IDE de GraphQL** desde `{nombre_de_la_cuenta}.myvtex.com/admin/graphql-ide`. Sustituye `{nombre_de_la_cuenta}` por el nombre de tu cuenta VTEX.
+2. Selecciona la aplicación `vtex.rewriter@x`. donde `x` es la versión de la aplicación. Por ejemplo, `vtex.rewriter@1.62.0`.
+3. Utiliza la siguiente consulta GraphQL para listar las redirecciones de la tienda:
+
+  ```
+  query {
+    redirect{
+      listRedirects{
+        routes{
+          from
+          to
+          endDate
+          type
+          binding
+        }
+      }
+    }
+  }
+  ```
+
+  El resultado esperado se mostrará en el siguiente formato:
+
+  ```json
+  {
+    "data": {
+      "redirect": {
+        "listRedirects": {
+          "routes": [
+            {
+              "from": "/hello",
+              "to": "hola",
+              "endDate": null,
+              "type": "PERMANENT",
+              "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+            },
+            {
+              "from": "/v/*",
+              "to": "https://masrefacciones.backend.verbolia.com",
+              "endDate": null,
+              "type": "PERMANENT",
+              "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+            }
+          ]
+        }
+      }
+    }
+  }
+  ```
+
+4. Alternativamente, si la ruta de la redirección que deseas encontrar es conocida, utiliza la siguiente consulta GraphQL sustituyendo `/hello` por la ruta de la redirección deseada:
+
+  ```
+  query {
+    redirect{
+      get(path:"/hello"){
+        from
+        to
+        endDate
+        type
+        binding
+      }
+    }
+  }
+  ```
+
+  El resultado esperado se mostrará en el siguiente formato:
+  ```json
+  {
+    "data": {
+      "redirect": {
+        "get": {
+          "from": "/hello",
+          "to": "hola",
+          "endDate": null,
+          "type": "PERMANENT",
+          "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+        }
+      }
+    }
+  }
+  ```
+
+Si las redirecciones no son las esperadas, la aplicación Rewriter permite realizar otras operaciones con las redirecciones, como eliminar las existentes y crear nuevas. Para más información sobre estas operaciones, consulta la guía [Rewriter GraphQL API](https://developers.vtex.com/docs/apps/vtex.rewriter/rewriter-graphql-api).
+
+También puedes exportar e importar redirecciones con `archivos.csv` utilizando la página Redirecciones o el [plugin](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-plugins) `redirects` de VTEX IO CLI. Para más información sobre la importación y exportación de redirecciones, consulta el artículo [Gestionar redirecciones según el binding](https://help.vtex.com/es/tutorial/administrando-redireccionamientos-de-url-por-binding--67GAK2TCQgjvmtPXxAqREb#importar-y-exportar-redirecciones) y la [referencia de comandos de VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-command-reference#redirects-delete).
diff --git a/docs/tutorials/es/admin-v4-getting-started.md b/docs/tutorials/es/admin-v4-getting-started.md
index 9fdd93eb2..31cf72442 100644
--- a/docs/tutorials/es/admin-v4-getting-started.md
+++ b/docs/tutorials/es/admin-v4-getting-started.md
@@ -24,24 +24,24 @@ Para lograrlo, estamos rediseñando múltiples partes de la experiencia y realiz
 ## Mejora en la navegación
 Todo lo que necesita para gestionar su tienda VTEX sigue presente en el Admin v4, solo que ahora con una organización más sencilla. Nuestro menú de navegación superior y lateral izquierdo se ha reestructurado desde cero, agrupando categorías similares de una manera más clara para reducir distracciones y ayudar a su equipo a encontrar lo que necesita con mayor rapidez. También puede utilizar la barra de búsqueda para encontrar secciones específicas en el menú lateral.
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Centro de información
 Aquí es donde reunimos todos los enlaces útiles de nuestro ecosistema VTEX, para ayudarlo a obtener lo mejor de nuestra plataforma VTEX. Al hacer clic en el botón «?» de la barra superior, puede acceder a nuestro Centro de ayuda, Blog, Portal del desarrollador, Status de la plataforma y página de soporte.    
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Configuración de la tienda
 Para esta nueva experiencia, hemos concentrado todas las configuraciones de todas las secciones en una pestaña específica: Configuración de la tienda. A través de esta mejora, puede acceder fácilmente a todas las configuraciones que afectan a cada servicio de su cuenta.
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Configuración del perfil
 El avatar de su perfil, en la esquina superior derecha, alberga ahora toda la configuración relacionada con su usuario y su cuenta. A través del avatar puede acceder a la configuración del usuario, la configuración de la cuenta, la información de facturación, cambiar la configuración regional de su administrador, cambiar a la versión anterior y cerrar la sesión. Con esta mejora, hemos separado la configuración de su perfil de las configuraciones que afectan a su tienda en sí. Ahora tiene más control y visibilidad sobre las acciones que afectan a su negocio y las que afectan a su perfil.
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 ## Página de inicio renovada
 Nuestra página de inicio del panel administrativo ha sido rediseñada para ofrecerle una visión general de alto nivel de su tienda, como una cabina de mando para sus operaciones de comercio digital. Por eso ahora se llama **Dashboard**.
 Tan pronto como inicie sesión en Admin v4, verá métricas y gráficos útiles para monitorear el rendimiento de su tienda, como los ingresos y el número de pedidos, el embudo de ventas y las tasas de conversión, y sus 10 productos de mayor venta. Vea todos los componentes del nuevo Dashboard y aprenda cómo funcionan en la siguiente lista.
-![Dashboard v4](https://images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
+![Dashboard v4](//images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
 
 - **Pedidos:**  número de pedidos realizados.  Todos los datos sobre pedidos e ingresos que proceden del Sistema de Gestión de Pedidos de VTEX.  
 - **Sesiones:** número de visitas a la tienda.  
diff --git a/docs/tutorials/es/ads-from-vtex-sales-app.md b/docs/tutorials/es/ads-from-vtex-sales-app.md
index 29e5e6807..54baf9acb 100644
--- a/docs/tutorials/es/ads-from-vtex-sales-app.md
+++ b/docs/tutorials/es/ads-from-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Anuncios de VTEX Sales App'
 id: 3UtOFwbwD4muz3p72RBPmC
 status: PUBLISHED
 createdAt: 2023-05-25T17:16:06.902Z
-updatedAt: 2023-05-30T15:53:49.413Z
-publishedAt: 2023-05-30T15:53:49.413Z
+updatedAt: 2024-06-26T18:31:53.389Z
+publishedAt: 2024-06-26T18:31:53.389Z
 firstPublishedAt: 2023-05-26T22:11:51.769Z
 contentType: tutorial
 productTeam: Shopping
@@ -17,6 +17,8 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 
 La nueva funcionalidad de anuncios de VTEX Sales App tiene dos tipos principales de anuncios: productos específicos y resultados de búsqueda. Esta flexibilidad permite que los administradores de la tienda adapten las estrategias de marketing a sus necesidades y objetivos específicos y puedan promover productos individuales o grupos de productos relacionados.
 
+Para personalizar la vitrina de una tienda, los retailers pueden agregar una página de `Anuncio por tienda` especificando el ID de la tienda a la que se asociará el anuncio en [Master Data](https://developers.vtex.com/docs/guides/master-data-introduction), lo que permite crear vitrinas personalizadas para cada tienda.
+
 En este documento, se presentan las instrucciones detalladas para instalar, configurar y utilizar la nueva funcionalidad de anuncios. Sigue los pasos a continuación para configurar esta herramienta e impulsar tus ventas online.
 
 * [Instalar las dependencias de VTEX](#instalar-las-dependencias-de-vtex)
@@ -29,30 +31,30 @@ En este documento, se presentan las instrucciones detalladas para instalar, conf
 
 Antes de instalar las dependencias, debes tener la [CLI de VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install) instalada. Después de tener la CLI de VTEX IO instalada, ejecuta los siguientes comandos en el terminal para instalar las dependencias necesarias:
 
-```
-vtex login {account}
-
-vtex install vtex.admin-cms@1.x vtex.admin-cms-graphql@0.x 
-vtex.admin-cms-graphql-rc@1.x vtex.admin-releases@0.x 
-vtex.cms-builder-sf-jamstack@1.x
-```
+1.
+    ```
+    vtex login {account}  
+    ```
+2.
+    ```
+    vtex install vtex.admin-cms@1.x vtex.admin-cms-graphql@0.x vtex.admin-cms-graphql-rc@1.x vtex.admin-releases@0.x vtex.cms-builder-sf-jamstack@1.x
+    ```
 
 ## Configurar la aplicación Headless CMS
 
 1. En el Admin VTEX, accede a **Apps > Mis Apps** o escribe **Mis Apps** en la barra de búsqueda en la parte superior de la página.
 2. Haz clic en `Configuración` en la tarjeta de **CMS (alpha)**.
 3. Haz clic en `Add More`.
-4. En el campo **Project ID**, ingresa `instore`.
+4. En el campo **Project ID**, ingresa `assisted-sales-app`.
 5. En el campo **Sections URL**, ingresa[ https://instore--instore.vtex.app/assisted-sales/cms/sections.json](https://instore--instore.vtex.app/assisted-sales/cms/sections.json).
 6. En el campo **Content types URL**, ingresa[ https://instore--instore.vtex.app/assisted-sales/cms/content-types.json](https://instore--instore.vtex.app/assisted-sales/cms/content-types.json).
-7. En el campo **Translation keys URL**, ingresa[ https://instore--instore.vtex.app/assisted-sales/cms/translation-keys.json](https://instore--instore.vtex.app/assisted-sales/cms/translation-keys.json).
-8. Haz clic en `Guardar`.
+7. Haz clic en `Guardar`.
 
 ## Crear la página de anuncios
 
 Para crear una página de anuncios para VTEX Sales App, sigue los pasos a continuación:
 
-1. Accede a la URL del Admin VTEX: `https://{account}.myvtex.com/admin/new-cms/instore`.
+1. Accede a la URL del Admin VTEX: `https://{account}.myvtex.com/admin//admin/new-cms/assisted-sales-app`.
 2. Haz clic en **Crear nuevo** y selecciona **Anuncios**.
 3. Haz clic en **Untitled** para editar e incluir el nombre que desees. Recomendamos el nombre **Anuncios**.
 4. En la pestaña **Secciones** haz clic en el botón `+` para agregar una nueva sección. Cada sección es una colección de productos o términos de búsqueda. Cada sección se mostrará como una vitrina en formato de carrusel. Puedes ordenar las vitrinas haciendo clic en los botones `Mover hacia abajo` o `Mover hacia arriba`.
@@ -61,23 +63,27 @@ Para crear una página de anuncios para VTEX Sales App, sigue los pasos a contin
     - **Título de la vitrina:** nombre de la vitrina que se mostrará en la página.
     - **ID del producto:** número identificador del producto que deseas mostrar. Campo obligatorio.
     - **ID del SKU del producto:** número identificador del SKU del producto que deseas mostrar. Campo opcional.
-![vitrine-produto-es](https://images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/99d80481198a5789b864e7b3cc621c9f/image.png)
+![vitrine-produto-es](//images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/99d80481198a5789b864e7b3cc621c9f/image.png)
 Después de rellenar los campos, se mostrará la imagen del producto con precio "a partir de". Si incluyes el SKU, se mostrará el precio y la promoción del SKU indicado. Puedes incluir más productos al hacer clic en `+ NUEVO PRODUCTO`. Puedes agregar hasta 10 productos en cada vitrina.
 El resultado de la vitrina de productos se mostrará como en la siguiente imagen.
-![vitrine-produto-2-es](https://images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/2b1605234e989064a7c188b6f3ce31a8/image.png)
+![vitrine-produto-2-es](//images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/2b1605234e989064a7c188b6f3ce31a8/image.png)
   - **Vitrina de resultados de búsqueda:** mostrará los productos de resultados de búsqueda que determines. Rellena la siguiente información:
     - **Título de la vitrina:** nombre de la vitrina que se mostrará en la página.
     - **Imagen de búsqueda:** imagen que mostrará la selección de productos en la vitrina.
     - **Nombre de la búsqueda:** nombre de la búsqueda que se mostrará en la página.
     - **Término de búsqueda:** término de búsqueda que servirá de referencia para los productos.
-![vitrine-busca-es](https://images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/832a5b243a2a82f170eebb8d77574009/image.png)
+![vitrine-busca-es](//images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/832a5b243a2a82f170eebb8d77574009/image.png)
 Cuando el vendedor haga clic en el término de búsqueda, se le redirigirá a los resultados de búsqueda que se hayan establecido en **Término de búsqueda**. Puedes incluir hasta 10 búsquedas en cada vitrina. El resultado del ejemplo se muestra en la siguiente imagen:
-![vitrine-busca-2-es](https://images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/2381c9859c4adeaec5953b0ac87d7b42/image.png)
+![vitrine-busca-2-es](//images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/2381c9859c4adeaec5953b0ac87d7b42/image.png)
 <ol start="6">
   <li>Después de crear las secciones, haz clic en <code>Guardar</code> y, luego, haz clic en <code>Publicar</code> y <code>Publicar ahora</code> para finalizar.</li>
 </ol> 
 
 La publicación de la vitrina se añadirá a la fila de indexación y se publicará en unos segundos.
+- **Vitrina de colección:** mostrará los productos de la colección que definas. Rellena la siguiente información: 
+  - **Título de la vitrina:** nombre de la vitrina que se mostrará en la página.   - **ID de la colección:** número del identificador de la colección que se mostrará en la página.
+
+![Vitrine - ES](//images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/b512969705a8d78857febbdbbc892fc8/Vitrine_-_ES.png)
 
 ## Activar el menú de anuncios en VTEX Sales App
 
@@ -88,12 +94,12 @@ https://{account}.myvtex.com/admin/portal/#/sites
 2. Haz clic en el botón del engranaje <i class="fas fa-cog"></i>.
 3. Selecciona la pestaña **Código**.
 4. En la pestaña lateral, selecciona `checkout-instore-custom-js`.
-![checkout-instore-custom-js-file](https://images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/a09ddfdf23851e0ada81931af2ed5b19/image.png)
-5. En el objeto `window.INSTORE_CONFIG`, agrega la flag `enableExplore: true`.
-![window.INSTORE_CONFIG](https://images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/c0003c9637209f503401fea07db839cb/image.png)
+![checkout-instore-custom-js-file](//images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/a09ddfdf23851e0ada81931af2ed5b19/image.png)
+5. En el objeto `window.INSTORE_CONFIG`, agrega la flag `enableExplore: true,`.
+![window.INSTORE_CONFIG](//images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/c0003c9637209f503401fea07db839cb/image.png)
 6. Haz clic en <i class="fas fa-save"></i> `Guardar`. 
-7. Opcionalmente, puedes determinar que la página de inicio del vendedor sea la página de anuncios. Para lograrlo, agrega la flag `initialPage : advertisements` en el objeto `window.INSTORE_CONFIG`.
-![initialPage : advertisements](https://images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/88e4f64f2707fd1dbbe95d6b9861e712/image.png)
+7. Opcionalmente, puedes determinar que la página de inicio del vendedor sea la página de anuncios. Para lograrlo, agrega la flag `initialPage : 'advertisements',` en el objeto `window.INSTORE_CONFIG`.
+![initialPage : advertisements](//images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/88e4f64f2707fd1dbbe95d6b9861e712/image.png)
 
 ## Acceder a los anuncios en VTEX Sales App
 
@@ -102,4 +108,4 @@ En VTEX Sales App, el vendedor podrá acceder a la página de anuncios de dos ma
 * **Página de inicio:** si el administrador de la tienda previamente registró la página de anuncios como la página de inicio del vendedor, al iniciar sesión en la plataforma, se redirigirá al vendedor directamente a la página de anuncios. Esta configuración garantiza que los vendedores siempre estén al día sobre los anuncios y promociones relevantes, de manera inmediata y en cuanto acceden al sistema.
 * **Menú Explorar:** si la página de anuncios no es la página de inicio, el vendedor puede acceder a ella fácilmente desde el menú **Explorar**. Para acceder a la página de anuncios, el vendedor debe hacer clic en el menú **Explorar**. Luego, se redirigirá al vendedor a la página de anuncios, donde podrá ver e interactuar con los productos y promociones disponibles.
 
-![vitrine-sale-app-es](https://images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/ffca39f0f0a2b0bdc59c39ebd88ddc71/image.png)
+![vitrine-sale-app-es](//images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/ffca39f0f0a2b0bdc59c39ebd88ddc71/image.png)
diff --git a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
new file mode 100644
index 000000000..5b160f79c
--- /dev/null
+++ b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
@@ -0,0 +1,161 @@
+---
+title: 'Anunciar con VTEX Ad Network (Beta)'
+id: 5WoXcJzHc7EQElpPjziqse
+status: PUBLISHED
+createdAt: 2024-04-23T18:57:14.559Z
+updatedAt: 2024-07-30T15:01:46.734Z
+publishedAt: 2024-07-30T15:01:46.734Z
+firstPublishedAt: 2024-04-23T19:16:43.333Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: anunciar-con-vtex-ad-network-beta
+locale: es
+legacySlug: anunciar-con-vtex-ad-network-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+[VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) te permite anunciar productos de tu marca en storefronts de retailers VTEX que tengan tu producto en su catálogo.
+
+Para comenzar a anunciarte en VTEX Ad Network, debes ponerte en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar la instalación de la aplicación __VTEX Ad Network__ en tu cuenta VTEX.
+
+Si ya eres un anunciante de **VTEX Ad Network**, en este artículo puedes ver detalles sobre cómo gestionar y monitorear tus campañas.
+
+- [Crear campaña](#crear-campana)
+- [Editar campaña](#editar-campana)
+- [Pausar campaña](#pausar-campana)
+- [Monitorear campañas](#monitorear-campanas)
+- [Ver más detalles por campaña y producto](#ver-mas-detalles-por-campana-y-producto)
+
+## Crear campaña
+
+Para crear una [campaña de VTEX Ad Network](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanas), sigue los pasos a continuación:
+
+<div class = "alert alert-info">
+Actualmente, VTEX cuenta con un único formato de anuncio: resultados de búsqueda. Consulta más información sobre este <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#formato-de-anuncio">formato de anuncio</a>.
+</div>
+
+1. En el Admin VTEX, accede a __Storefront > Ad Network > Campañas__.
+2. Haz clic en `Crear campaña`.
+3. En la sección **Nombre de la campaña**, haz clic en el botón de editar <i class="fas fa-pencil-alt"></i>.
+4. Ingresa el nombre que deseas utilizar para tu campaña y haz clic en `Guardar`.
+5. En la sección **Productos**, haz clic en el botón de editar <i class="fas fa-pencil-alt"></i>.
+6. Selecciona los productos que deseas anunciar utilizando una de las siguientes opciones:
+
+   * __Buscar productos por EAN:__ buscar productos de tu catálogo por EAN.
+   * __Cargar archivo:__ enviar un archivo CSV con una lista de códigos EAN y ofertas, según [este ejemplo](//assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/c61c4a27f462bb3fa85457eed1bad0b8/teste-ads.csv). Los EAN son obligatorios y las ofertas son opcionales en el archivo.
+
+7. En la sección **Presupuesto, oferta y cronograma**, haz clic en el botón de editar <i class="fas fa-pencil-alt"></i>.
+8. Define los valores de las ofertas para cada producto. Puedes definir cada valor individualmente.
+	<div class="alert alert-info">
+	La oferta de un producto es el costo por clic (CPC), el valor gastado cuando un usuario hace clic en el anuncio. Más información sobre <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanas">campañas</a> y cómo funciona la <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#priorizacion-de-anuncios">subasta</a>.
+	</div>
+9. Haz clic en `Siguiente`.
+10. Define el presupuesto diario de la campaña.
+11. Define la duración de la campaña seleccionando la fecha de fin.
+12. En la sección **Cobertura de anuncios**, haz clic en el botón de editar <i class="fas fa-pencil-alt"></i>.
+13. Selecciona las tiendas en que deseas mostrar esta campaña.
+
+   De forma predeterminada, VTEX muestra los anuncios en todas las tiendas de retailers participantes de VTEX Network que venden los productos seleccionados en tu campaña.
+
+   Si no deseas mostrar tus anuncios en todas las tiendas, marca la opción **O escoge tus retailers** y selecciona las tiendas de retailers en que deseas mostrar los anuncios de esta campaña.
+
+14. Haz clic en `Guardar`.
+15. Haz clic en `Publicar`.
+
+En unos minutos, los productos seleccionados comenzarán a anunciarse en lugares destacados de tiendas VTEX.
+
+## Editar campaña
+
+Después de crear una campaña, puedes editar cualquiera de sus características. Para editar, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Storefront > Ad Network > Campañas__.
+2. Haz clic en la fila de la tabla correspondiente a la campaña que deseas editar.
+3. Haz clic en el ícono <i class="fas fa-pencil-alt"></i>.
+4. Cambia la información que desees.
+5. Haz clic en el ícono <i class="fa-solid fa-check"></i>.
+
+## Pausar campaña
+
+Puedes pausar campañas para que sus anuncios dejen de mostrarse. Si deseas pausar una de tus campañas, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Storefront > Ad Network > Campañas__.
+2. En la fila correspondiente a la campaña que deseas pausar, haz clic en <i class="fas fa-ellipsis-v"></i>.
+3. Haz clic en `Pausar`.
+
+## Pausar producto
+
+Puedes pausar un producto específico de tu campaña para que el anuncio correspondiente deje de mostrarse. Si deseas pausar un producto específico dentro de una de tus campañas, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Storefront > Ad Network > Campañas__.
+2. Haz clic en la fila correspondiente a la campaña que contiene el producto que deseas pausar.
+3. En la fila correspondiente al producto que deseas pausar, haz clic en <i class="fas fa-ellipsis-v"></i>.
+4. Haz clic en `Pausar`.
+
+## Monitorear campañas
+
+En la pantalla de inicio de la aplicación [VTEX Ad Network](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), también encontrarás información sobre tus campañas en curso.
+
+![vtex_ad_network_create_campaign_ES](//images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/1d60c965f3c6e4cf92a2f7487e938cb9/vtex_ad_network_create_campaign.png)
+
+En la parte superior se muestran los datos agregados:
+
+- **Presupuesto total:** presupuesto total designado para tus campañas.
+- **Presupuesto gastado:** valor gastado hasta la fecha.
+- **ROAS promedio:** promedio del retorno de inversión publicitaria.
+- **Ventas por anuncios:** ingresos totales de ventas derivadas de anuncios.
+
+A continuación, se muestra una tabla con la información de cada campaña:
+
+- **Duración:** duración de la campaña hasta la fecha.
+- **Impresiones:** número de veces que los anuncios recibieron impresiones en la página.
+- **Vistas:** número de veces que los anuncios fueron realmente vistos. VTEX Ad Network cuenta una vista cuando se produce una impresión de anuncio y, si es necesario, el usuario desplaza la página lo suficiente como para visualizar al menos el 50 % del área del anuncio durante un segundo.
+- **Clics:** número de clics en anuncios. VTEX Ad Network descarta clics en el mismo producto que ocurran en menos de un minuto entre sí.
+- **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
+- **Pedidos:** número de pedidos derivados de clics en anuncios.
+- **Unidades vendidas:** número de unidades de productos vendidas a partir de anuncios de esa campaña.
+- **Ventas:** ingresos totales de ventas.
+- **ROAS:** retorno de inversión publicitaria.
+- **Presupuesto:** presupuesto total.
+- **Presupuesto restante:** presupuesto que aún está disponible.
+
+<div class = "alert alert-info">
+Consulta más información sobre <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ventana-de-atribucion">atribución de ventas a anuncios</a>.
+</div>
+
+Puedes filtrar los datos de la tabla utilizando las siguientes opciones:
+
+- **Buscar campaña:** filtra las campañas por nombre.
+- **Status:** selecciona si deseas ver solo las campañas activas o inactivas.
+
+### Ver más detalles por campaña y producto
+
+En la tabla de la pantalla de inicio de la aplicación [VTEX Ad Network](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) también puedes hacer clic en las filas de tus campañas para ver detalles más específicos.
+
+- **Vistas/Clics:** vistas y clics en anuncios.
+- **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
+- **Presupuesto gastado:** valor gastado hasta la fecha.
+- **ROAS:** retorno de inversión publicitaria.
+- **Ingresos:** ingresos por ventas derivadas de anuncios.
+
+Debajo de los datos agregados, se muestra una tabla con la información del desempeño de cada producto de esa campaña:
+
+- **CPC:** valor gastado cuando un usuario hace clic en un anuncio.
+- **Impresiones:** número de veces que los anuncios recibieron impresiones en la página.
+- **Vistas:** número de veces que los anuncios fueron realmente vistos. VTEX Ad Network cuenta una vista cuando hay una impresión del anuncio y, de ser necesario, el usuario desliza la página lo suficiente para verlo.
+- **Clics:** número de clics en anuncios.
+- **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
+- **Pedidos:** número de pedidos derivados de clics en anuncios.
+- **Unidades vendidas:** número de unidades del producto vendidas a partir de anuncios de esta campaña.
+- **Ventas:** ingresos totales de ventas.
+- **ROAS:** retorno de inversión publicitaria.
+- **Presupuesto restante:** presupuesto que aún está disponible actualmente.
+
+<div class = "alert alert-info">
+Consulta más información sobre <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ventana-de-atribucion">atribución de ventas a anuncios</a>.
+</div>
+
diff --git a/docs/tutorials/es/affiliates-program-app.md b/docs/tutorials/es/affiliates-program-app.md
index dd34260f9..d86916f29 100644
--- a/docs/tutorials/es/affiliates-program-app.md
+++ b/docs/tutorials/es/affiliates-program-app.md
@@ -40,11 +40,11 @@ La aplicación crea tres tipos de páginas para los afiliados, que disponen de e
 
 La **página del afiliado** es la URL de la tienda VTEX que comparten con los clientes. Ve un ejemplo en la siguiente imagen:
 
-![url_pagina_es_3](https://images.ctfassets.net/alneenqid6w5/3BxA8DMUUHVt7qZs5mYUhx/72903370216b4def73a08cc485c3c81d/url_pagina_es.png)
+![url_pagina_es_3](//images.ctfassets.net/alneenqid6w5/3BxA8DMUUHVt7qZs5mYUhx/72903370216b4def73a08cc485c3c81d/url_pagina_es.png)
 
 La **página del perfil del afiliado** es una interfaz a través de la cual pueden seguir y gestionar sus pedidos y comisiones. Ve un ejemplo en la siguiente imagen:
 
-![profile_pagina_es_3](https://images.ctfassets.net/alneenqid6w5/37jFSHHD7RweXxkvOzelPL/25c11f8c83fe7871282c513bef26c2ee/profile_pagina_es.png)
+![profile_pagina_es_3](//images.ctfassets.net/alneenqid6w5/37jFSHHD7RweXxkvOzelPL/25c11f8c83fe7871282c513bef26c2ee/profile_pagina_es.png)
 
 La página de **registro** permite que los interesados en convertirse en afiliados completen sus datos para solicitar el registro en su tienda VTEX.
 
@@ -72,7 +72,7 @@ La página **de Gestión de afiliados** permite realizar las siguientes acciones
 - [Ver detalles del afiliado](#ver-detalles-del-afiliado)
 - [Editar afiliado](#editar-afiliado)
 
-![affiliates_management_page_es](https://images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/de5a0b8ff2c25569692f4c2eb99c730d/affiliates_management_page_es.jpg)
+![affiliates_management_page_es](//images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/de5a0b8ff2c25569692f4c2eb99c730d/affiliates_management_page_es.jpg)
 
 ### Agregar afiliado
 
@@ -119,7 +119,7 @@ La página de **Gestión de pedidos** permite realizar las siguientes acciones:
 - [Exportar plantilla de pedidos](#exportar-lista-de-pedidos)
 - [Ver detalles del pedido](#ver-detalles-del-pedido)
 
-![orders_management_page_es](https://images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/56d938c239cb62d2396e4152adf5df08/orders_management_page_es.jpg)
+![orders_management_page_es](//images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/56d938c239cb62d2396e4152adf5df08/orders_management_page_es.jpg)
 
 ### Seguir dashboard
 
@@ -172,7 +172,7 @@ La página de **Gestión de comisiones** permite realizar las siguientes accione
 - [Importar comisiones](#importar-comisiones)
 - [Descargar la última importación](#descargar-la-ultima-importacion)
 
-![commissions_ management_page_es](https://images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/a87a79d01580e58605e0a21461d8a381/commissions__management_page_en.png)
+![commissions_ management_page_es](//images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/a87a79d01580e58605e0a21461d8a381/commissions__management_page_en.png)
 
 ### Buscar comisiones
 
diff --git a/docs/tutorials/es/all-orders.md b/docs/tutorials/es/all-orders.md
index 79272a861..9bd41a43e 100644
--- a/docs/tutorials/es/all-orders.md
+++ b/docs/tutorials/es/all-orders.md
@@ -3,8 +3,8 @@ title: 'Todos los pedidos'
 id: 2QTduKHAJMFIZ3BAsi6Pi
 status: PUBLISHED
 createdAt: 2022-04-04T21:50:53.330Z
-updatedAt: 2023-03-23T16:27:45.086Z
-publishedAt: 2023-03-23T16:27:45.086Z
+updatedAt: 2023-12-21T14:05:13.862Z
+publishedAt: 2023-12-21T14:05:13.862Z
 firstPublishedAt: 2022-04-04T22:39:11.450Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: lista-de-pedidos-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
+<div class = "alert alert-info">
+Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
+</div>
+
 La página **Todos los pedidos** permite a los administradores de la tienda hacer seguimiento de los pedidos de su tienda y extraer información para la gestión inteligente de su negocio. Para acceder a la página, en el menú del Admin VTEX, haz clic en **Pedidos > Todos los pedidos**. En esta página puedes: 
 
 - Consultar las métricas de pedidos y ventas.
@@ -24,7 +28,14 @@ La página **Todos los pedidos** permite a los administradores de la tienda hace
 
 Las siguientes secciones proporcionan más detalles sobre cada componente de la página y sus acciones.
 
-![Order Listing EN](https://images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/458efe24f7fcb7653eb23d1ea1d7110b/Order_Listing_EN.gif)
+![Order Listing EN](//images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/458efe24f7fcb7653eb23d1ea1d7110b/Order_Listing_EN.gif)
+
+Además de buscar pedidos en **Pedidos > Todos los pedidos**, puede buscar pedidos desde cualquier página del Admin VTEX utilizando la barra de búsqueda global en la parte superior de la página. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
 
 ## Barra superior
 
@@ -156,7 +167,7 @@ A continuación, encontrarás más detalles sobre cada columna:
 
 ## VTEX DO
 
-![VTEX Do overview ES](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
+![VTEX Do overview ES](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
 
 [VTEX DO](https://help.vtex.com/es/tutorial/vtex-do-beta--7KMbRL4OslN8DTX9oiuCiu) es un gestor de tareas creadas por el Admin VTEX automáticamente y que requieren una acción manual por parte del equipo de _ecommerce_. 
 
diff --git a/docs/tutorials/es/amaro-integration.md b/docs/tutorials/es/amaro-integration.md
new file mode 100644
index 000000000..c9a979cb2
--- /dev/null
+++ b/docs/tutorials/es/amaro-integration.md
@@ -0,0 +1,19 @@
+---
+title: 'Integración con AMARO'
+id: 7615C3U8EHbxbVw82D9pH8
+status: PUBLISHED
+createdAt: 2023-09-20T21:43:42.533Z
+updatedAt: 2024-01-05T19:46:36.030Z
+publishedAt: 2024-01-05T19:46:36.030Z
+firstPublishedAt: 2023-09-20T22:13:13.268Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: integracion-con-amaro
+locale: es
+legacySlug: integracion-con-amaro
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; 
+por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
index 99ea9573b..bc2642bed 100644
--- a/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
@@ -110,7 +110,7 @@ Para instalar la aplicación, accede a VTEX App Store:
 Las configuraciones realizadas en el campo Automatic Invoice se aplicarán a todos los pedidos.
 </div>
 
-![MCF](https://images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/604c465dd3344b9cc04b722d03cb5005/Amazon_MCF_EN.PNG)
+![MCF](//images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/604c465dd3344b9cc04b722d03cb5005/Amazon_MCF_EN.PNG)
 
 ### Integración del catálogo
 
diff --git a/docs/tutorials/es/amazon-offer-matching.md b/docs/tutorials/es/amazon-offer-matching.md
index 350796345..0554299bb 100644
--- a/docs/tutorials/es/amazon-offer-matching.md
+++ b/docs/tutorials/es/amazon-offer-matching.md
@@ -3,8 +3,8 @@ title: 'Match de anuncios Amazon'
 id: 7fRfoP69kYgg8znImMhyQ0
 status: PUBLISHED
 createdAt: 2023-05-29T15:07:38.220Z
-updatedAt: 2023-05-29T16:59:25.926Z
-publishedAt: 2023-05-29T16:59:25.926Z
+updatedAt: 2023-07-27T21:32:07.360Z
+publishedAt: 2023-07-27T21:32:07.360Z
 firstPublishedAt: 2023-05-29T16:38:11.840Z
 contentType: tutorial
 productTeam: Channels
@@ -12,14 +12,14 @@ author: 2p7evLfTcDrhc5qtrzbLWD
 slug: match-de-anuncios-amazon
 locale: es
 legacySlug: match-de-anuncios-amazon
-subcategory: 4YvjazdRUhQzjHJ53FCYJM
+subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
 Cada vez que se envía a Amazon un [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) con [EAN](https://sellercentral.amazon.es/ap/signin?clientContext=261-8757701-2350731&openid.return_to=https%3A%2F%2Fsellercentral.amazon.es%2Fhome&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.assoc_handle=sc_es_amazon_v2&openid.mode=checkid_setup&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&mons_redirect=sign_in&ssoResponse=eyJ6aXAiOiJERUYiLCJlbmMiOiJBMjU2R0NNIiwiYWxnIjoiQTI1NktXIn0.OXnfPkFrVoFi4dXfMrd7Kwek1FssNeqXCta87Q1sSl7DqyJ98__Ryw.4muN2tysN_PkuvSf.GznbHEikHTllZro87ZYZUVtkWUrdodtIbspeQgF7icUzljTLsJ9OJCcDhh3SWh6pjIEoME_cB7BjSiYsMxXdzC_6AmgEYy6ZwL4Fbh3ihkizNyVPa1j09UxedsZRR3M0Q5ScowfAIkBLN3E-_dLmYWprisRLsH4P7E5Mgqwe_kYo3nw8cyd8thAySiZqAqsohOOz9vlb.nEUzoBpuJOR05XA169HidA) registrado en VTEX, el marketplace realiza el proceso de matching (hallar coincidencias), que consiste en unificar los anuncios de un mismo producto a través de su EAN.  
 
 El EAN registrado en VTEX se utiliza para hacer la equivalencia con los [ASIN](https://afiliados.amazon.com.mx/) (*Amazon Standard Identification Number, o número de identificación estándar de Amazon*) correspondientes en Amazon. Para hacer el emparejamiento entre EAN y ASIN, es necesario realizar el matching manualmente. La correspondencia entre EAN y ASIN debe ser exacta para que los anuncios se vinculen correctamente.  
 
-![Match Amazon ES](https://images.ctfassets.net/alneenqid6w5/2w6NrOhlTwsknC27Soe0pr/d731d68d1df056004825eabd1106eecf/Match_del_anuncios_Amazon.gif)
+![Presentación match de anuncios](//images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/4c1f3a16c14e3201bd0724e0c6907cad/Match-an__ncios-Amazon.gif)
 
 ## Pestaña Oportunidad  
 
@@ -62,18 +62,42 @@ A continuación te explicamos más sobre la estructura de esta pestaña.
 
 Tras el [envío](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD), los productos estarán disponibles en la página de Match de anuncios Amazon. Para visualizar los anuncios no aprobados, accede al Admin VTEX, haz clic en *Marketplace >* __Match de anuncios Amazon__ o utiliza la barra de búsqueda de la parte superior de la página.  
 
+### Match individual de anuncios  
+
+En la pestaña `Oportunidad`, al hacer clic sobre el ícono <i class="fas fa-ellipsis-v"></i> que aparece al lado de cada producto, se muestran dos opciones `Ver detalles` y `Ver anuncio sugerido`. Ambas redirigen a nuevas páginas, una al match individual del producto y la otra para ver el anuncio sugerido publicado en el sitio web de Amazon, respectivamente.
+
+Estos son los botones disponibles en cada una de las páginas y sus acciones: 
+
+- **Botón `Rechazar`:** este botón elimina la sugerencia de match y el seller deberá enviar nuevamente el producto si lo desea, siguiendo el [tutorial de envío de productos](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).
+- **Botón `Rechazar y pedir revisión`:** si el seller no está de acuerdo con la sugerencia de match y desea pedir una revisión a Amazon, debe escoger esta opción. Al hacer clic en este botón, se redirigirá al seller a la página para abrir tickets de soporte de Amazon y la sugerencia de match se mostrará en la lista de oportunidades.
+El seguimiento de la revisión se debe realizar mediante el dashboard de tickets de Amazon.
+- **Botón `Publicar`:** si el seller está de acuerdo con la sugerencia propuesta por Amazon, solo basta hacer clic en `Publicar`.
+
+Para aprobar el match, el seller debe seguir los pasos a continuación:  
+
+1. En la pestaña `Oportunidad`, haz clic en el ícono <i class="fas fa-ellipsis-v"></i>.  
+2. Haz clic en la opción `Ver detalles`.  
+3. Consulta la información que aparece en la página.    
+![Match individual de anuncios](//images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/eac88bc236fafb26cf67f89276e6162f/Match_individual_AMZ.png)
+
+4. Según la conclusión del análisis, haz clic en uno de los botones disponibles: `Publicar`, `Rechazar y pedir revisión` o `Rechazar`.
+
+Tras la confirmación, tus anuncios se enviarán y se pondrán en cola para su procesamiento. Una vez aprobado, el anuncio aparecerá en la pestaña __Anuncios__, donde podrás __"ver detalles" de tu anuncio, ver "anuncio sugerido por Amazon"__ y __buscar__ anuncios en la barra de búsqueda.  
+
+### Match de anuncios en masa
+
 En la pestaña `Oportunidad`, todos los productos listados que presenten equivalencia entre Tu anuncio y Sugerencia de Amazon necesitan aprobarse manualmente. Para aprobar correspondencias de SKU y ASIN sigue los pasos a continuación.  
 
 1. En la pestaña `Oportunidad`, marca la casilla situada junto al título de los anuncios con equivalencia SKU <> ASIN.  
 Al seleccionar los productos, aparecerá en la pantalla el siguiente pop up indicando cuántos productos se han seleccionado.  
 
-![popupES](https://images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/4b97de7bb44236561a9474189936cb4c/MATCHAMZ_ES.png)
+![popupES](//images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/4b97de7bb44236561a9474189936cb4c/MATCHAMZ_ES.png)
 
 2. Al finalizar la selección de productos, haz clic en `Publicar seleccionados`.  
 
 3. En el pop up de confirmación del matching, comprueba los anuncios elegidos y haz clic en `Publicar seleccionados`.  
 
-![Confirmacioin del matching](https://images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/5762aa090ef7e6e3137fd99e81cba8f5/CONFIRMACION_MATCH.png)
+![Confirmacioin del matching](//images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/5762aa090ef7e6e3137fd99e81cba8f5/CONFIRMACION_MATCH.png)
 
 Tras la confirmación, tus anuncios se enviarán y se pondrán en cola para su procesamiento. Una vez aprobado, el anuncio aparecerá en la pestaña __Anuncios__, donde podrás __"ver detalles" de tu anuncio__, __ver "anuncio sugerido" por Amazon__ y __buscar__ anuncios en la barra de búsqueda.  
 
diff --git a/docs/tutorials/es/analytics.md b/docs/tutorials/es/analytics.md
new file mode 100644
index 000000000..92798fc89
--- /dev/null
+++ b/docs/tutorials/es/analytics.md
@@ -0,0 +1,87 @@
+---
+title: 'Analytics'
+id: 6qRMAHDL9hvv3oE0bh8mA1
+status: PUBLISHED
+createdAt: 2024-06-27T16:53:32.304Z
+updatedAt: 2024-06-27T16:54:23.587Z
+publishedAt: 2024-06-27T16:54:23.587Z
+firstPublishedAt: 2024-06-27T16:54:23.587Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: analytics
+locale: es
+legacySlug: analytics
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+**Analytics** es una pantalla en el VTEX Intelligent Search que organiza los datos relacionados con las búsquedas realizadas en la tienda y permite exportar esos datos en un archivo .csv.
+
+Con esta información, podrá ver el desempeño de los resultados de la búsqueda y de los términos de búsqueda de [Autocomplete](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4gXFsEWjF7QF7UtI2GAvhL?&utm_source=autocomplete) y realizar acciones para mejorar el rendimiento, como configurar una redirección o registrar un nuevo sinónimo.
+
+A continuación se indican los pasos necesarios para acceder a la página:
+
+1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda en la parte superior de la página.
+2. En __Intelligent Search__, haz clic en __Analytics__. 
+
+<div class = "alert alert-info">
+  <p>La página <strong>Analytics</strong> es nativa en VTEX Intelligent Search. No se puede deshabilitar en el Admin.</p>
+</div>
+
+## Datos
+
+Los datos que componen el informe se actualizan cada 4 horas y contienen la siguiente información:
+
+*   **Término de búsqueda**: contenido de las búsquedas realizadas. 
+*   **Búsquedas**: número de búsquedas realizadas para un término específico. Cuando el cliente busca un término en la tienda y hace clic en otra página o actualiza la página, también se cuenta como una búsqueda. 
+*   **Clics**: número total de clics en los resultados de búsqueda de un término. 
+*   **Clics únicos**: número de clics en los resultados de búsqueda de un término, excluyendo los clics repetidos de un mismo usuario. Indica el número de personas que han hecho clic en un determinado resultado a partir de la búsqueda. 
+*   **CTR _(click-through rate)_**: la tasa de clics según el total de búsquedas. Esta tasa se calcula de la siguiente forma: `(Clics/Búsquedas) * 100`. 
+*   **Conversión**: tasa de conversión de los términos buscados. El cálculo de la conversión sigue la fórmula: `(Pedidos/Clics únicos) * 100`.  Es posible que la tasa de conversión sobrepase el 100 %, ya que toma en cuenta la cantidad de pedidos efectuados entre clics. Por ejemplo, es posible que el usuario realice más de un pedido utilizando el término _camisa_ y, en ese caso, la conversión sería mayor que el 100 %.
+*   **Pedidos**: número de pedidos realizados desde la búsqueda. Para calcular esta métrica, consideramos que la búsqueda genera un pedido cada vez que, después buscar un término, el cliente hace clic en algún producto que aparece en los resultados y luego compra cualquier producto (no necesariamente el producto en el que hizo clic). 
+*   **Ventas**: ingresos totales generados por los pedidos realizados a partir de la búsqueda. El cálculo sigue la misma lógica que la métrica de **Pedidos**, la diferencia es que el resultado refleja los ingresos en lugar del número de pedidos.
+
+<div class="alert alert-info">
+  <p>Los datos mostrados en el informe se limitan a los 10 mil términos más buscados. Si deseas obtener los datos de búsqueda completos de tu tienda, tienes que <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacion">exportar el informe</a>.</p>
+</div>
+
+Cuando se elige [exportar un informe](#exportacion), también existe la posibilidad de generarlo con las __métricas de embudo__. Si se selecciona esa opción, se agregarán 4 nuevas columnas al archivo:
+
+* **ProductClicks**: dado un término de búsqueda, esta columna muestra los ID de los productos en los que se han hecho clic y el número de clics que se han producido, respectivamente. Por ejemplo: `3378|1`; `3659|2`; `4038|3` significa que se ha hecho clic 1 vez en el producto con ID 3378, se ha hecho clic 2 veces en el producto con ID 3659, y se ha hecho clic 3 veces en el producto con ID 4038. 
+* **PositionClickAverage**: dado un término de búsqueda, esta columna muestra los ID de los productos en los que se ha hecho clic y su posición promedio en la lista de resultados. Por ejemplo: `4321|1` significa que el producto cuyo ID es 4321 ocupa el primer lugar como posición promedio en la lista de resultados de la búsqueda.
+* **ProductsAddToCart**: dado un término de búsqueda, esta columna muestra los ID de los productos que han sido añadidos al carrito y la cantidad añadida, respectivamente. Por ejemplo: `3380|1`; `3910|2` significa que se ha añadido al carrito 1 unidad del producto con ID 3380, y que se han añadido 2 unidades del producto con ID 3910 al carrito. 
+* **ProductsSold**: dado un término de búsqueda, esta columna muestra los ID de los productos que fueron vendidos y la cantidad vendida, respectivamente. Por ejemplo: `3500|1` significa que se ha vendido 1 unidad del producto con ID 3500. 
+
+## Filtros
+
+Como opción para restringir los datos, la pantalla **Analytics** permite combinar criterios. Consulte a continuación las opciones de filtros disponibles:
+
+* **Búsqueda** o **Autocomplete** 
+* **Con resultados** o **Sin resultados**: elegir entre las búsquedas que obtuvieron resultados o no. 
+* **Todos**, **Celular** o **Computador**: limitar los dispositivos en los que se han realizado las búsquedas. 
+* **Hoy**, **Ayer**, **Últimos 7 días**, **Últimos 30 días** y **Personalizar**: seleccionar el periodo a analizar. La opción **Personalizar** permite introducir fechas de inicio y de fin que se deben considerar. 
+
+La página **Analytics** solo muestra información para un intervalo de un mes. Si desea acceder a los datos de un periodo de hasta 6 meses, debe [exportarlos en un archivo con formato CSV](#exportacion).
+
+## Exportación
+
+Para exportar un informe en formato CSV, debe seguir los pasos que se indican a continuación.
+
+1. En la página **Storefront** > **Intelligent Search** > **Analytics**, haga clic en `Exportar`. 
+2. Configure los filtros del informe que se generará. 
+3. Elija si desea marcar la opción **Con métricas de embudo** o no. Si se selecciona, esta opción agrega las columnas **[ProductsClick, PositionClickAverage, ProductsAddToCart y ProductsSold](#datos)** al archivo, correlacionando la información sobre el número de clics y ventas con los ID de los productos buscados. 
+4. A continuación, haga clic en `Exportar`. 
+5. Espere a que el archivo esté disponible para su descarga. Salir de esta página no interrumpe el proceso. 
+6. Haga clic en `Descargar`. 
+
+<div class = "alert alert-info">
+  <p>El archivo permanece disponible para descarga durante 48 horas.</p>
+</div>
+
+El informe CSV descargado tiene dos tablas. La primera tabla, que se muestra a continuación, contiene información sobre los términos de búsqueda y las métricas de embudo (desde la columna **ProductsClick** hasta la columna **ProductsSold**), si se ha seleccionado esa opción.
+
+![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
+
+La segunda tabla, que se muestra a continuación, muestra los datos del periodo seleccionado, mostrando la columna **Date**, que indica la fecha de la búsqueda.
+
+![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
diff --git a/docs/tutorials/es/antifraud-provider.md b/docs/tutorials/es/antifraud-provider.md
index cc3f16499..75eef0170 100644
--- a/docs/tutorials/es/antifraud-provider.md
+++ b/docs/tutorials/es/antifraud-provider.md
@@ -46,14 +46,14 @@ Antes de configurar el ambiente VTEX, el proveedor debe implementar el servicio
 ### 3. Portal de administración del Antifraud Provider
 Después de recibir los datos de acceso e implementar el back-end, el proveedor puede acceder a la herramienta de aprobación a través del Admin de VTEX. Para ello, debe instalar el App del Antifraud Provider en el menú Apps:
 
-![print5](https://images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
+![print5](//images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
 
 Haga clic en la App instalada o acceda a `https://{{AccountName}}.myvtex.com/admin/antifraud-provider`, sustituyendo `{{AccountName}}` por el nombre de su cuenta en la plataforma. En este ambiente, es posible registrar los datos de configuración de back-end del proveedor y realizar pruebas de integración.
 
-![print6](https://images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
+![print6](//images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
 
 ### 4. Configuración inicial
-![print1](https://images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
+![print1](//images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
 
 Al acceder al ambiente por el enlace descrito arriba, usted verá un formulario. Rellene los campos de acuerdo con las siguientes indicaciones:
 
@@ -77,7 +77,7 @@ Después de llenar los campos correctamente, el sistema comprobará las transacc
 
 Las pruebas que se deben realizar en su integración antes de mandarla para la evaluación de VTEX se muestran abajo. Usted puede seleccionar qué pruebas desea ejecutar, pero para que su integración pase por el análisis de nuestro equipo, __todas ellas necesitan ser realizadas__. Por lo tanto, recomendamos que todos ellos permanezcan seleccionados.
 
-![print2](https://images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
+![print2](//images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
 
 ### 5. Pruebas
 Al hacer clic en el botón __Execute tests__, el Antifraud Provider aplicará las pruebas en su integración para los diferentes escenarios posibles. Es importante recordar que __todos ellos son obligatorios__ y, para ejecutarlos, su servicio necesita estar en HTTPS. Las pruebas son:
@@ -107,11 +107,11 @@ Para cada prueba del Antifraud Provider Protocol, enviamos un final de ID espec
 ### 6. Resultados
 Después de ejecutar las pruebas, el sistema devuelve los resultados, tanto positivos como negativos. El sistema también trae la información de los resultados esperados para cada prueba. Así, usted tiene más visibilidad de lo que debe ser ajustado en caso de error.
 
-![print3](https://images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
+![print3](//images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
 
 Para visualizar de forma detallada cada acción realizada por la integración (y, así, identificar posibles errores), basta con hacer clic en el enlace __Show logs__. Una lista con la información completa de los eventos que ocurrieron durante la prueba se mostrará por debajo de los resultados.
 
-![print4](https://images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
+![print4](//images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
 
 Cuando su integración ha pasado todas las pruebas con éxito, sólo tiene que abrir un ticket en el [help de VTEX](/es/support) informando la conclusión. Sin embargo, antes de abrir el ticket, asegúrese de tener la siguiente información:
 
@@ -135,7 +135,7 @@ Utilice la URL `https://{{AccountName}}.myvtex.com/admin/license-manager/#/home`
 Una vez que la integración con su antifraude está aprobada, un conector se pondrá a disposición para que las tiendas VTEX lo configuren en sus respectivos sitios web. Para hacer esto, además del contrato con su empresa, la tienda deberá tener en las manos dos claves: "X-PROVIDER-API-AppKey" y "X-PROVIDER-API-AppToken".
 
 Un ejemplo de cómo va a quedar la pantalla de configuración del antifraude para la tienda VTEX:
-![print8](https://images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
+![print8](//images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
 
 Estas llaves deben estar disponibles por usted y van a servir para identificar la tienda que ha contratado y está utilizando su servicio de antifraude.
 
diff --git a/docs/tutorials/es/application-keys.md b/docs/tutorials/es/application-keys.md
index 5c19bc5c6..cf5cff2de 100644
--- a/docs/tutorials/es/application-keys.md
+++ b/docs/tutorials/es/application-keys.md
@@ -3,134 +3,170 @@ title: 'Claves de aplicación'
 id: 2iffYzlvvz4BDMr6WGUtet
 status: PUBLISHED
 createdAt: 2021-08-19T17:45:31.084Z
-updatedAt: 2022-11-25T18:39:48.683Z
-publishedAt: 2022-11-25T18:39:48.683Z
+updatedAt: 2023-10-17T20:17:39.441Z
+publishedAt: 2023-10-17T20:17:39.441Z
 firstPublishedAt: 2021-08-19T18:08:07.096Z
 contentType: tutorial
 productTeam: Identity
-author: 56yU9Wz6mLwmzo82TjgAHy
+author: 1malnhMX0vPThsaJaZMYm2
 slug: claves-de-aplicacion
 locale: es
 legacySlug: claves-de-aplicacion
 subcategory: 5GYFjiMQg0qIKpnnQY2qjh
 ---
 
-Cada integración por API utilizada para conectar su cuenta VTEX con sistemas externos requerirá la creación de una clave de aplicación (también conocida en inglés como _application key_ o _app key_). Estas credenciales de [autenticación](https://developers.vtex.com/vtex-rest-api/docs/getting-started-authentication) se utilizan para dar acceso seguro a los datos que desea compartir con estas integraciones, sin exponer su cuenta a usuarios o aplicaciones no autorizados. 
+Cada integración por API utilizada para conectar tu cuenta VTEX con sistemas externos requerirá la creación de una clave de aplicación (_application key_ o _app key_).
 
-En la página de **Claves de aplicación** puede gestionar las claves de aplicación [internas](#claves-de-aplicacion-internas) y [externas](#claves-de-aplicacion-externas) que tienen acceso a su cuenta, incluyendo:
+Estas credenciales de [autenticación](https://developers.vtex.com/docs/guides/authentication) se utilizan para dar acceso seguro a los datos que deseas compartir con las integraciones, sin exponer tu cuenta a aplicaciones o usuarios no autorizados.
 
-- [Generar claves de aplicación en su cuenta](#generar-claves-de-aplicacion-en-su-cuenta)
-- [Gestionar los permisos de las claves de aplicación](#gestionar-los-permisos-de-las-claves-de-aplicacion)
-- [Activar o desactivar las claves de aplicación](#activar-o-desactivar-claves-de-aplicacion)
-- [Exportar claves de aplicación con acceso a su cuenta](#exportar-claves-de-aplicacion-con-acceso-a-su-cuenta)
+## Tipos de claves de aplicación
 
-Para acceder a esta página, vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_.
+Existen dos tipos de claves de aplicación: [internas](#claves-de-aplicacion-internas) o [externas](#claves-de-aplicacion-externas). Esta definición depende de la cuenta que crea, gestiona y utiliza la credencial.
 
-<div class = "alert alert-info">
-  Vea este artículo sobre <a href="https://help.vtex.com/es/tutorial/best-practices-application-keys--7b6nD1VMHa49aI5brlOvJm">Buenas prácticas para el uso de claves de aplicación</a>.
+### Claves de aplicación internas
+
+Las claves de aplicación internas son credenciales generadas y gestionadas en tu cuenta VTEX. Esto significa que debes tener acceso a todos los pares de claves y tokens de aplicación (el equivalente a los nombres de usuario y las contraseñas para las integraciones de API).
+
+### Claves de aplicación externas
+
+Las claves de aplicación externas son credenciales generadas y administradas por otras cuentas VTEX. Al agregar [roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) a las claves de aplicación (el equivalente a los nombres de usuario) proporcionadas por terceros, tienes la opción de permitir que accedan a recursos específicos de tu cuenta.
+
+## Gestionar claves de aplicación
+
+<div class="alert alert-warning">
+  <p>Se requiere un <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">rol</a> con el recurso <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3"></a> <strong>Save user</strong> para gestionar usuarios y claves de aplicación. El rol predeterminado para este fin es <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, pero también es posible <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol">crear un rol personalizado</a> con este recurso.</p>
 </div>
 
-## Tipos de claves de aplicación
+En la página **Claves de aplicación** puedes gestionar las claves de aplicación [internas](#claves-de-aplicacion-internas) y [externas](#claves-de-aplicacion-externas) que tienen acceso a tu cuenta, incluyendo:
 
-### Claves de aplicación internas
+- [Generar claves de aplicación internas](#generar-claves-de-aplicacion-internas)
+- [Agregar claves de aplicación externas](#agregar-claves-de-aplicacion-externas)
+- [Gestionar permisos de las claves de aplicación](#gestionar-permisos-de-claves-de-aplicación)
+- [Activar o desactivar claves de aplicación](#activar-o-desactivar-claves-de-aplicacion)
+- [Exportar claves de aplicación con acceso a tu cuenta](#exportar-claves-de-aplicación-con-acceso-a-tu-cuenta)
 
-Las claves de aplicación internas son credenciales generadas en su cuenta VTEX y gestionadas por ella. Esto significa que debe tener acceso a todos los pares de claves y tokens de aplicación, que son los equivalentes a los nombres de usuario y las contraseñas para las integraciones por API.
+Para acceder a esta página, en la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** (marcado con la inicial de tu email) y luego en **Configuración de la cuenta** > **Claves de aplicación**.
 
-### Claves de aplicación externas
+<div class = "alert alert-info">
+ <p>Consulta este artículo para saber más sobre <a href="https://help.vtex.com/es/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm">buenas prácticas para el uso de claves de aplicación.</p></a>
+</div>
+
+## Generar claves de aplicación internas
+
+Como las claves de aplicación permiten que sistemas externos accedan a tu cuenta, solo pueden ser creadas por usuarios con el recurso `License Manager / Services access control / Save user` en sus [roles](https://help.vtex.com/es/tutorial/roles-de-acceso--7HKK5Uau2H6wxE1rH5oRbc).
 
-Las claves de aplicación externas son credenciales generadas en otras cuentas VTEX y gestionadas por ellas. Al añadir [perfiles de acceso](https://help.vtex.com/es/tutorial/perfiles-de-acceso--7HKK5Uau2H6wxE1rH5oRbc) a las claves de aplicación (el equivalente a los nombres de usuario) proporcionadas por terceros, puede permitirles acceder a recursos específicos de su cuenta.
+Para crear claves de aplicación internas en tu cuenta sigue los pasos a continuación:
 
-## Generar claves de aplicación en su cuenta
+1. Para acceder a esta página, en la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** (marcado con la inicial de tu email) y luego en **Configuración de la cuenta** > **Claves de aplicación**.
+2. Haz clic en el botón `Administrar mis claves`.
 
-Para crear claves de aplicación en su cuenta, vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_ y haga clic en el botón **Administrar mis claves**. Esto le llevará a la página **Mis claves**, donde podrá encontrar todas las [claves de aplicación internas](#claves-de-aplicacion-internas).
+    Se te redirigirá a la página **Mis claves**, ilustrada a continuación,  donde podrás consultar todas las [claves de aplicación internas](#claves-de-aplicacion-internas).
 
-![My Keys](//images.contentful.com/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/1c98224b6f50673c4567f21e22de4978/image3.png)
+    ![Mis Claves](//images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/68300cda392cc27ff02bc50af0bc2b7e/mis-claves-es.png)
 
-Vea a continuación los campos que se muestran en la página **Mis claves**:
+    Estos son los campos visibles en la página **Mis claves**:
 
-- **Etiqueta:** campo de texto que describe el propósito de la clave de aplicación.
-- **Clave:** campo de texto que contiene el identificador único de la clave de aplicación.
-- **Status:** campo booleano que indica si la clave de aplicación está activa o inactiva.
+    - **Etiqueta:** texto que describe la finalidad de la clave de aplicación.
+    - **Clave:** identificador único para la clave de aplicación.
+    - **Status:** status actual de la clave de aplicación, que puede ser activa o inactiva.
 
-Dado que las claves de aplicación permiten que sistemas externos accedan a su cuenta, su creación está restringida a los usuarios con el recurso `License Manager / Services access control / Save user` incluidos en sus [perfiles de acceso](https://help.vtex.com/es/tutorial/perfiles-de-acceso--7HKK5Uau2H6wxE1rH5oRbc).
+3. Haz clic en el botón `+ Generar nueva`.
+2. (Opcional) Rellena la **Etiqueta** con una descripción de la finalidad de la clave de aplicación. Este campo es inmutable y solo puede definirse durante la creación de la clave de aplicación. Si se deja en blanco, el campo se rellenará automáticamente con el valor del campo **Clave** de la clave de aplicación generada.
+3. (Opcional) Haz clic en `+ Agregar roles` para [gestionar los permisos de la clave de aplicación](#gestionar-permisos-de-las-claves-de-aplicacion).
+4. Haz clic en el botón `Agregar rol`.
+5. Haz clic en <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> para copiar el **Token de aplicación**. _Este secreto se mostrará una vez.  Guárdalo en un lugar seguro._
 
-Para generar una nueva clave de aplicación, siga los pasos a continuación:
+<div class="alert alert-warning">
+  <p>Protege tus pares de claves y tokens de aplicación como lo harías con otras credenciales, como nombres de usuario y contraseñas. Si sospechas que una clave de aplicación está comprometida, debes desactivarla inmediatamente en tu cuenta. Para más detalles, consulta la sección <a href="#ativar-ou-desativar-chaves-de-aplicacao">Activar o desactivar claves de aplicación</a> de este artículo.</p>
+</div>
+
+## Agregar claves de aplicación externas
 
-1. Haga clic en el botón **⊕ Generar clave**.
-2. (Opcional) Rellene la **Etiqueta** con una descripción del propósito de la clave de aplicación. Este campo es inmutable y solo se puede definir cuando se está generando la clave de aplicación. Si se deja en blanco, el campo se rellenará con el valor del campo **Clave** de la clave de aplicación generada.
-3. (Opcional) Haga clic en el botón **+ Agregar perfiles** para [gestionar los permisos de la clave de aplicación](#gestionar-los-permissos-de-las-claves-de-aplicacion).
-4. Haga clic en el botón **Generar**.
-5. Haga clic en el botón <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> para copiar el **token de aplicación** _Este secreto solo se mostrará una vez. Guárdelo en un lugar seguro._
+Para agregar claves de aplicación de terceros sigue los pasos a continuación:
 
-<div class="alert alert-warning">Proteja sus pares de claves y tokens de aplicación como lo haría con otras credenciales, como nombres de usuario y contraseñas. Si sospecha que una clave de aplicación está comprometida, desactive inmediatamente la clave en su cuenta. Para saber más detalles, consulte la sección <a href="#activar-o-desactivar-claves-de-aplicacion">Activar o desactivar las claves de aplicación</a> deste articulo.</div>
+1. Para acceder a esta página, en la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** (marcado con la inicial de tu email) y luego en **Configuración de la cuenta** > **Claves de aplicación**.
+2. Haz clic en el botón `+ Agregar clave de app externa`.
+3. Rellena el campo \{b\>Clave\<b\} con la clave de aplicación proporcionada por la aplicación externa.
+4. Haz clic en `+ Agregar roles` para [gestionar los permisos de la clave de aplicación](#gestionar-permisos-de-las-claves-de-aplicacion). Agrega roles para otorgarles el acceso a los recursos que desees.
+5. Haz clic en `Guardar`.
 
 ## Gestionar los permisos de las claves de aplicación
 
-Para que una clave de aplicación pueda realizar con éxito solicitudes de API a su cuenta, debe estar activa y tener [perfiles de acceso](https://help.vtex.com/es/tutorial/perfiles-de-acceso--7HKK5Uau2H6wxE1rH5oRbc) que especifiquen los recursos de la cuenta a los que puede acceder.
+Para que una clave de aplicación pueda realizar requests de API a tu cuenta, debe estar activa y tener [roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) que especifiquen los recursos de la cuenta a los que puede acceder. 
 
 <div class="alert alert-danger">
-<b>¡Atención!</b> El uso sin restricciones de perfiles de acceso muy permisivos aumenta el riesgo de ataques en las tiendas por la fuga de credenciales de acceso.
+<p>El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas al filtrarse las credenciales de inicio de sesión.</p>
 </div>
 
-Las claves de aplicación se crean, por defecto, sin permiso para acceder a ningún recurso de la cuenta. 
+Las claves de aplicación se crean, de manera predeterminada, sin permisos para acceder a ningún recurso de la cuenta.
+
+Hay tres maneras de llegar a la página donde se pueden editar los roles de una clave de aplicación:
 
-Hay tres caminos diferentes para llegar a la página donde se pueden editar los perfiles de acceso de una clave de aplicación:
+- Haciendo clic en el botón `+ Agregar roles` para [generar claves de aplicación](#generar-claves-de-aplicacion-en-tu-cuenta) en tu cuenta.
+- Haciendo clic en el botón `+Agregar clave de app externa` en la página **Claves de aplicación**.
+- Haciendo clic en el botón `፧` y seleccionando la opción **Editar** en las páginas **Claves de aplicación** o **Mis claves**.
 
-- Utilizar el botón **+ Agregar perfiles** al [generar claves de aplicación](#generar-claves-de-aplicacion-en-su-cuenta) en su cuenta.
-- Utilizar el botón **⊕ Agregar** en la página **Claves de aplicación**.
-- Utilizar el botón **፧** y seleccionar la opción **Editar** en las páginas **Claves de aplicación** o **Mis claves**.
+Al editar una clave de aplicación, puedes: 
 
-Al editar una clave de aplicación, puede:
+- Agregar roles de acceso haciendo clic en el botón `+ Agregar roles`, seleccionando uno o más roles y haciendo clic el botón `Agregar roles`. 
+- Eliminar roles de acceso marcando las casillas de selección y haciendo clic en el botón `Eliminar roles`.
+- Guardar los cambios haciendo clic en el botón `Guardar`.
 
-- Agregar perfiles de acceso haciendo clic en el botón **+ Agregar perfiles**, seleccionando uno o más perfiles de acceso y haciendo clic en el botón **Agregar perfiles**. 
-- Eliminar perfiles de acceso utilizando las casillas para seleccionarlos y haciendo clic en el botón **Eliminar perfiles**.
-- Guarde los cambios haciendo clic en el botón **Guardar**.
+Tras agregar los roles de acceso a una clave de aplicación, esta aparecerá en la página **Claves de aplicación**.
 
-Después de haber añadido perfiles de acceso a una clave de aplicación, esta aparecerá en la página **Claves de aplicación**.
+![Claves de aplicación](//images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/931a3bd780840b11e47bf7d2a84ff718/claves-es.png)
 
-![Application Keys](//images.contentful.com/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/da66ebc249dd18cbc709d872ce78719c/image2.png)
+Consulta a continuación los campos visibles en la página **Claves de aplicación**:
 
-Vea a continuación los campos que se muestran en la página  **Claves de aplicación**:
+- **Clave:** identificador único para la clave de la aplicación.
+- **Cuenta:** cuenta VTEX responsable de gestionar la clave de aplicación.
+- **Status:** status actual de la clave de aplicación, que puede ser activa o inactiva.
+
+<div class="alert alert-info">
+  <p>Observa que el campo <strong>Etiqueta</strong> no se muestra en la página <strong>Claves de aplicación</strong>. Para ver la descripción de la finalidad de una clave de aplicación interna, utiliza el valor de la<strong>Clave</strong> para encontrarla en la página <strong>Mis claves</strong>. No es posible agregar etiquetas a claves de aplicación externas.</p>
+</div>
+
+## Activar y desactivar claves de aplicación
+
+Si una clave de aplicación que tiene acceso a tu cuenta se ve comprometida, debes cancelar su acceso inmediatamente. Si cometes un error puedes volver a activarla para restablecer la integración afectada. La forma de hacerlo dependerá del [tipo de clave de aplicación](#tipos-de-clave-de-aplicacion).
+
+<div class="alert alert-warning">
+  <p>Vuelve a activar una clave de aplicación solamente si estás seguro de que no ha sido comprometida. Cualquier usuario con el token de aplicación asociado recuperará el acceso privilegiado a tu cuenta.</p>
+</div>
 
-- **Clave:** campo de texto que contiene el identificador único de la clave de aplicación.
-- **Cuenta:** campo de texto que indica la cuenta VTEX que gestiona la clave de aplicación.
-- **Status:** campo booleano que indica si la clave de aplicación está activa o inactiva.
+### Desactivar clave de aplicación interna
 
-<div class="alert alert-info">Tenga en cuenta que el campo <strong>Etiqueta</strong> no se muestra en la página <strong>Claves de aplicación</strong>. Para ver la descripción del objetivo de una clave de aplicación interna, utilice el valor de la <strong>Clave</strong> para encontrarla en la página <strong>Mis claves</strong>. No es posible añadir etiquetas a claves de aplicación externas.</div>
+Para desactivar una clave de aplicación interna sigue los pasos a continuación: 
 
-## Activar o desactivar claves de aplicación
+1. En la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil**, con la inicial de tu email, y luego en **Configuración de la cuenta** > **Claves de aplicación**.
+2. Haz clic en el botón `Administrar mis claves`.
+3. En la lista, busca la clave de aplicación que deseas desactivar y haz clic en el botón `፧`.
+4. Haga clic en la opción **Desactivar**.
 
-Si una clave de aplicación que tiene acceso a su cuenta se ve comprometida, debe cancelar inmediatamente dicho acceso. Si se equivoca, puede volver a activarla para restablecer la integración afectada. La forma de hacerlo va a depender del [tipo de clave de aplicación](#tipos-de-claves-de-aplicacion).
+### Desactivar clave de aplicación externa
 
-<div class="alert alert-warning">Solo debe volver a habilitar una clave de aplicación si está seguro de que no ha sido comprometida. Cualquier usuario con el token de aplicación asociado recuperará el acceso privilegiado a su cuenta.</div>
+Para desactivar una clave de aplicación externa sigue los pasos a continuación: 
 
-Para desactivar una clave de aplicación interna, siga los pasos a continuación:
+1. Para acceder a esta página, en la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** (marcado con la inicial de tu email) y luego en **Configuración de la cuenta** > **Claves de aplicación**.
+2. En la lista, busca la clave de aplicación que deseas desactivar y haz clic en el botón `፧`.
+3. Haz clic en la opción **Desactivar**.
 
-1. Vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_.
-2. Haga clic en el botón **Administrar mis claves**.
-3. Busque la clave de aplicación que desea desactivar en la lista y haga clic en el botón **፧**.
-4. Seleccione la opción **Desactivar**.
+### Activar clave de aplicación interna
 
-Para desactivar una clave de aplicación externa, siga los pasos a continuación:
+Para reactivar claves de aplicación internas que se habían desactivado previamente sigue los pasos a continuación:
 
-1. Vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_.
-2. Busque la clave de aplicación que desea desactivar en la lista y haga clic en el botón **፧**.
-3. Seleccione la opción **Eliminar**.
+1. Para acceder a esta página, en la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** (marcado con la inicial de tu email) y luego en **Configuración de la cuenta** > **Claves de aplicación**.
+2. Haz clic en el botón `Administrar mis claves`.
+3. En la lista, busca la clave de aplicación que deseas reactivar y haz clic en el botón `፧`.
+4. Haz clic en la opción **Activar**.
 
-Para volver a activar claves de aplicación internas que se han desactivado previamente, siga los pasos a continuación:
+### Activar clave de aplicación externa
 
-1. Vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_.
-2. Haga clic en el botón **Administrar mis claves**.
-3. Busque la clave de aplicación que desea desactivar en la lista y haga clic en el botón **፧**.
-4. Seleccione la opción **Activar**.
+Para reactivar las claves de aplicación externas que se hayan desactivado previamente, deberás repetir las instrucciones descritas en [agregar claves de aplicación externas](#agregar-claves-de-aplicacion-externas).
 
-Para volver a activar claves de aplicación externas que se han desactivado previamente, siga los pasos a continuación:
+## Exportar claves de aplicación con acceso a tu cuenta
 
-1. Vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_.
-2. Haga clic en el botón **⊕ Adicionar**.
-3. Rellene el campo **Clave** con la clave de aplicación proporcionada por el tercero.
-4. Añada perfiles de acceso para permitirles el acceso a los recursos que desee.
+Si es necesario para una auditoría de seguridad, puedes exportar un archivo CSV que contenga los valores **Clave** de todas las claves de aplicación internas y externas que actualmente tienen acceso a tu cuenta, es decir, con roles asociados a la misma.
 
-## Exportar claves de aplicación con acceso a su cuenta
+Para exportar las claves, accede a _Configuración de la cuenta > Claves de aplicación > <span style="display: inline-block;"><img src="//images.contentful.com/alneenqid6w5/25JqGWNUZPZattDX6ORXX6/742e99e17042024b9cae641564909171/image4.png" alt="export-button"/> <strong>Exportar</strong></span>.
 
-Si es necesario para una auditoría de seguridad, puede exportar un archivo CSV que contenga los valores de la **Clave** para todas las claves de aplicación internas y externas que actualmente tienen acceso a su cuenta, es decir, que tienen perfiles de acceso asociados. Para exportar las claves, vaya a _Configuración de la cuenta > Gestión de la cuenta > Claves de aplicación_ y haga clic en el botón <span style="display: inline-block;"><img src="//images.contentful.com/alneenqid6w5/25JqGWNUZPZattDX6ORXX6/742e99e17042024b9cae641564909171/image4.png" alt="export-button"/> <strong>Exportar</strong></span>.
diff --git a/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
index 17789a685..e0492085b 100644
--- a/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
@@ -3,8 +3,8 @@ title: 'Aprobar pago de boleto'
 id: tutorials_184
 status: PUBLISHED
 createdAt: 2017-04-27T22:16:19.919Z
-updatedAt: 2023-03-26T21:44:48.077Z
-publishedAt: 2023-03-26T21:44:48.077Z
+updatedAt: 2024-06-03T20:36:09.927Z
+publishedAt: 2024-06-03T20:36:09.927Z
 firstPublishedAt: 2017-04-27T23:00:46.699Z
 contentType: tutorial
 productTeam: Financial
@@ -25,7 +25,7 @@ Se puede hacer esa aprobación manualmente por el OMS de forma simple, conforme
 2. Haga clic en la transaccione.
 3. Haga clic en el botón __Notificar el pago__.
 
-![NotificarES](https://images.ctfassets.net/alneenqid6w5/3IfQ1FNhluYWWgcMUEaUq0/ea25ce5d59b8ff98c593bc9382312f85/NotificarES.png)
+![NotificarES](//images.ctfassets.net/alneenqid6w5/3IfQ1FNhluYWWgcMUEaUq0/ea25ce5d59b8ff98c593bc9382312f85/NotificarES.png)
 
 **Después de la aprobación del pago, el pedido entrará en el flujo normal de compra.**
 
@@ -33,7 +33,7 @@ Se puede hacer esa aprobación manualmente por el OMS de forma simple, conforme
 En el módulo de Gestión de la cuenta, el usuario debe tener un perfil de acceso que incluya el permiso <code>Notify payment</code> para poder aprobar los pagos.
 </div>
 
-Para aprobar pagos por API, vea la [documentación sobre el reqyuest de notificación de pago](https://developers.vtex.com/reference/payment#getorder).
+Para aprobar pagos por API, vea la [documentación sobre la solicitud de notificación de pago](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/payments/-paymentId-/payment-notification).
 
 <div class="alert alert-warning">
 Como las <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integraciones con los ERP</a> se rigen por el <a href="https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#">flujo de pedidos</a>, la aprobación manual de un pago continuará la integración de este pedido con el back office de la tienda normalmente. Por lo tanto, se recomienda precaución al aprobar los pagos manualmente, para garantizar que se reciba cada pedido procesado y enviado.
diff --git a/docs/tutorials/es/apps-overview.md b/docs/tutorials/es/apps-overview.md
index b92ee8f46..4a4419b85 100644
--- a/docs/tutorials/es/apps-overview.md
+++ b/docs/tutorials/es/apps-overview.md
@@ -36,7 +36,7 @@ El menú de Apps permite a los comerciantes descargar nuevas aplicaciones direct
 
 Puedes encontrar estas operaciones en el menú Apps de tu Admin actualizado.
 
-![Apps Overview menu ES](https://images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/ae534adadd4b3455ed9ba7827f367a2d/Apps_Overview_menu_ES.jpg)
+![Apps Overview menu ES](//images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/ae534adadd4b3455ed9ba7827f367a2d/Apps_Overview_menu_ES.jpg)
 
 A continuación encontrarás más detalles sobre las diferentes secciones y páginas de esta funcionalidad, que pronto estará disponible en el Admin actualizado. 
 
diff --git a/docs/tutorials/es/assembly-options-app.md b/docs/tutorials/es/assembly-options-app.md
index bff13cdd0..1928fe4b4 100644
--- a/docs/tutorials/es/assembly-options-app.md
+++ b/docs/tutorials/es/assembly-options-app.md
@@ -37,7 +37,7 @@ Una vez instalada, la página **Catálogo > Opciones de ensamblaje** estará dis
 
 En el Admin VTEX, en **Catálogo > Opciones de ensamblaje**, tendrás acceso a una lista con todas las Opciones de ensamblaje registradas en tu tienda cuando uses la aplicación.
 
-![assembly-options-app-es](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
+![assembly-options-app-es](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
 
 La información que aparecerá en la lista será:
 
diff --git a/docs/tutorials/es/assembly-options-in-vtex-sales-app.md b/docs/tutorials/es/assembly-options-in-vtex-sales-app.md
new file mode 100644
index 000000000..16463ee8b
--- /dev/null
+++ b/docs/tutorials/es/assembly-options-in-vtex-sales-app.md
@@ -0,0 +1,55 @@
+---
+title: 'Assembly Options en VTEX Sales App'
+id: 4fTfqOMcXyhAhWXkl935lr
+status: PUBLISHED
+createdAt: 2024-04-30T11:16:48.636Z
+updatedAt: 2024-04-30T17:04:30.041Z
+publishedAt: 2024-04-30T17:04:30.041Z
+firstPublishedAt: 2024-04-30T14:58:57.024Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: assembly-options-en-vtex-sales-app
+locale: es
+legacySlug: assembly-options-en-vtex-sales-app
+subcategory: 4T6qfa6gNO6g4sAUIa6s2G
+---
+
+[VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) es una aplicación que permite la integración entre los canales de venta online y físicos. Con esta aplicación, los vendedores de las tiendas físicas pueden ofrecer una atención personalizada a los clientes, y realizar el proceso de venta de forma completa y presencial, desde la elección de los productos hasta la selección del mejor medio de pago y envío.
+
+Para obtener más información sobre la instalación de [VTEX Sales App, accede a VTEX Sales App - Configuración básica](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO).
+
+[Assembly Options](https://help.vtex.com/es/tutorial/assembly-options-app), disponible en [VTEX  App Store](https://apps.vtex.com/vtex-admin-assembly-options/p), es la funcionalidad que permite a los vendedores ofrecer servicios adicionales durante el proceso de venta, como garantía extendida y seguros. Además, también permite la creación de conjuntos compuestos por distintos SKU, como cestas de Navidad o de desayuno, kits de maquillaje, entre otros. 
+
+## Instalar Assembly Options
+
+Para utilizar Assembly Options es necesario tener instaladas en tu tienda las aplicaciones [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) y Assembly Options. La aplicación [Assembly Options](https://help.vtex.com/es/tutorial/assembly-options-app--54mWg37mojrqOgCA79iqqk) está disponible solamente para tiendas [VTEX IO](https://developers.vtex.com/docs/guides/welcome).
+
+## Escenarios de aplicación de Assembly Options en VTEX Sales App
+
+Existen dos escenarios en los que se pueden agregar servicios a productos presentes en un único carrito.
+
+**Escenario 1:** selección de un único servicio
+
+1. Agrega al carrito un producto que tenga una opción de ensamblaje de servicios asociados.
+2. Selecciona la opción de servicio que deseas y haz clic en el botón **Continuar al carrito**.
+3. Una vez finalizado el proceso, podrás ver en tu carrito el servicio seleccionado, con el valor total del pedido.
+
+![Garantia estendida - ES](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/700c85400ed179eb7aaeecfd963160ee/Cen_rio_1__T1__-_ES.png)
+
+![Carrinho - ES](//images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/2b1f4c689a2f9ff02705f9e2772c799f/Cen_rio_1__T2__-_ES.png)
+
+**Escenario 2:** selección de múltiples servicios
+
+1. Agrega al carrito un producto que tenga más de una opción de ensamblaje de servicios asociados.
+2. Puedes elegir más de un servicio, solo tienes que seleccionar la opción del servicio que desees y pulsar el botón Siguiente.
+3. Elige otro servicio que quieras agregar y haz clic en el botón Continuar al carrito.
+4. Una vez finalizado el proceso, podrás ver en tu carrito los servicios seleccionados con el valor total del pedido.
+5. Haz clic en el botón Continuar. Si alguno de los servicios requiere información adicional, rellena los campos necesarios para vincular esta información al servicio adquirido.
+6. Haz clic en el botón Aplicar.
+
+![Garantia estendida - ES](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/700c85400ed179eb7aaeecfd963160ee/Cen_rio_1__T1__-_ES.png)
+
+![Seguro - ES](//images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/dae714edffa7f98926c9b86a321a2170/Cen_rio_2__T2__-_ES.png)
+
+![Ordem pedido - ES](//images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/7cab56abab6aa79d6f1483bb492486c2/Cen_rio_2__T3__-_ES.png)
diff --git a/docs/tutorials/es/assembly-options.md b/docs/tutorials/es/assembly-options.md
index 5dfacc489..173584d1d 100644
--- a/docs/tutorials/es/assembly-options.md
+++ b/docs/tutorials/es/assembly-options.md
@@ -3,8 +3,8 @@ title: 'Assembly Options'
 id: 5x5FhNr4f5RUGDEGWzV1nH
 status: PUBLISHED
 createdAt: 2021-10-25T20:22:43.094Z
-updatedAt: 2023-03-29T17:55:49.763Z
-publishedAt: 2023-03-29T17:55:49.763Z
+updatedAt: 2024-06-06T19:38:13.881Z
+publishedAt: 2024-06-06T19:38:13.881Z
 firstPublishedAt: 2021-10-25T21:39:46.746Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Una assembly option es un [anexo](https://help.vtex.com/es/tutorial/que-es-un-an
 
 En el siguiente ejemplo, una tienda ofrece múltiples assembly options para el producto _custom bell_ (campana personalizada). Estas opciones se muestran en la página de producto, donde el cliente puede seleccionar las opciones deseadas. Dependiendo de las opciones, puede haber un coste adicional para el SKU.
 
-![assembly-option-ES](https://images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/a4598c720776d55966ff96a0423af592/image.png)
+![assembly-option-ES](//images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/a4598c720776d55966ff96a0423af592/image.png)
 
 Puedes combinar distintos [SKU](https://help.vtex.com/es/tutorial/que-es-un-sku--1K75s4RXAQyOuGUYKMM68u) para ofrecer assembly options, como los _Bells add-ons Roman_ o los _Bells add-ons 1-3 lines_ en el ejemplo anterior. Si un ítem está agotado, se mostrará como no disponible.
 
@@ -61,7 +61,7 @@ El primer `[x-y]` corresponde a las reglas que se aplican al grupo, y entre cada
 | \[0-3\]#10000\[1-2\]**\[1\]**pricetable1;#20000\[0-2\]**\[0\]**pricetable2;#30000\[0-2\]**\[0\]**pricetable3 | Este segmento define la cantidad seleccionada por defecto para cada SKU.  |
 | \[0-3\]#10000\[1-2\]\[1\]**pricetable1**;#20000\[0-2\]\[0\]**pricetable2**;#30000\[0-2\]\[0\]**pricetable3** | El último segmento indica la tabla de precios de cada ítem.                    |
 
-![assembly-option-exemplo-ES](https://images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/3f3dbae528ee506cf1eddf109168bf1a/image.png)
+![assembly-option-exemplo-ES](//images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/3f3dbae528ee506cf1eddf109168bf1a/image.png)
 
 #### Configuración del anexo
 
diff --git a/docs/tutorials/es/associate-a-sku-to-a-trade-policy.md b/docs/tutorials/es/associate-a-sku-to-a-trade-policy.md
index 2796bdf92..32148c8b6 100644
--- a/docs/tutorials/es/associate-a-sku-to-a-trade-policy.md
+++ b/docs/tutorials/es/associate-a-sku-to-a-trade-policy.md
@@ -1,10 +1,10 @@
 ---
 title: 'Asociación de SKU a una política comercial'
 id: 1qFAiybogHCStRO65sy4vb
-status: CHANGED
+status: PUBLISHED
 createdAt: 2021-03-30T17:18:09.088Z
-updatedAt: 2023-03-29T18:27:48.036Z
-publishedAt: 2021-08-04T18:13:54.928Z
+updatedAt: 2024-05-31T22:32:04.940Z
+publishedAt: 2024-05-31T22:32:04.940Z
 firstPublishedAt: 2021-03-30T17:34:49.644Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -29,4 +29,8 @@ En la página de configuración de cada SKU, existe la opción de asociar solo a
 6. Marque la casilla correspondiente a la Política Comercial del escenario B2B.
 7. Al final de la página, haga clic en el botón `Guardar` para registrar los cambios.
 
+<div class="alert alert-warning" role="alert">
+  <p>Si no se selecciona una política comercial específica en la configuración del SKU, todas las políticas comerciales tendrán acceso al SKU.</p>
+</div>
+
 Cada cambio realizado en un SKU necesita tiempo para procesarse completamente, incluidas las asociaciones a las Políticas Comerciales. Usted puede conocer más detalles en el artículo [Cómo funciona la indexación](https://help.vtex.com/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion--tutorials_256).
diff --git a/docs/tutorials/es/associating-a-template-with-a-layout.md b/docs/tutorials/es/associating-a-template-with-a-layout.md
index a04378485..505d89abd 100644
--- a/docs/tutorials/es/associating-a-template-with-a-layout.md
+++ b/docs/tutorials/es/associating-a-template-with-a-layout.md
@@ -30,4 +30,4 @@ Esta asociación se realiza en la configuración de las propiedades del layout.
 5. Haga clic en el menú desplegable **Template**. Ahí se listarán los templates configurados en HTML Templates.
 6. Seleccione el template que desea asociar a este layout.
 7. Digite `yes` para confirmar el cambio (este paso es necesario porque se trata de un cambio crítico para el sitio web, ya que el front-end de la página será reemplazado). 
-![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tutorials/es/audit.md b/docs/tutorials/es/audit.md
new file mode 100644
index 000000000..2a9bc689e
--- /dev/null
+++ b/docs/tutorials/es/audit.md
@@ -0,0 +1,139 @@
+---
+title: 'Audit'
+id: 5RXf9WJ5YLFBcS8q8KcxTA
+status: PUBLISHED
+createdAt: 2021-10-21T16:51:06.108Z
+updatedAt: 2024-04-18T14:03:48.943Z
+publishedAt: 2024-04-18T14:03:48.943Z
+firstPublishedAt: 2021-10-21T21:55:42.939Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: audit
+locale: es
+legacySlug: como-encontrar-eventos-en-audit
+subcategory: 2TNXiKzLZOPxjMTyGiEeJu
+---
+
+Para aumentar la transparencia y la confianza de los usuarios administrativos de tu tienda, VTEX registra varias operaciones junto con sus autores y marcas de hora en **Audit**, un módulo utilizado para consultar e investigar el historial por medio de filtros.
+
+Para acceder a la página de Audit en el Admin VTEX, ve a **Apps > Apps instaladas > Audit** o ingresa **Audit** en la barra de búsqueda. En esta página, puedes realizar las siguientes acciones:
+
+* [Consultar eventos en Audit](#consultar-eventos-en-audit)
+* [Verificar las últimas consultas realizadas en Audit](#verificar-las-ultimas-consultas-realizadas-en-audit)
+
+<div class="alert alert-info">
+  <p>Para visualizar los eventos de Audit, debe tener un <a href="https://help.vtex.com/es/tutorial/perfis-de-acceso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acceso</a> asociado al <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <em>Insights Metrics</em>.</p>
+</div>
+
+![audit-ui-es](//images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/7c0a482122fe0605d75492f02b44f20d/audit-ui-es__1_.png)
+
+## Consultar eventos en Audit
+
+Audit permite consultar eventos mediante filtros de aplicación, fecha, acción, autor y detalles del evento. A continuación, explicamos cómo utilizar los [filtros](#filtros) de Audit y la presentación de los [resultados](#resultados). También mostramos el uso de filtros con [ejemplos](#ejemplos-de-consultas) prácticos.
+
+### Filtros
+
+Para consultar un evento utilizando los filtros disponibles en Audit, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Apps > Apps instaladas > Audit** o ingresa _Audit_ en la barra de búsqueda. Se te redirigirá a la pestaña **Eventos de auditoría** en Audit.
+2. En el menú **Aplicación** dentro de la sección **Filtros**, selecciona la aplicación relacionada con la consulta.
+3. En el menú **Fecha**, escoge una de las fechas predefinidas para la consulta. Si prefieres definir el intervalo de fechas exacto, activa la opción de usar una fecha **Personalizada **y selecciona la fecha de **Inicio** y **Fin** para la consulta.
+
+   <div class= "alert alert-info">
+     <p>Solo se almacenan los registros de los últimos tres meses.</p>
+   </div>
+
+4. Si lo desea, añada un filtro por Acción. Para ello, en el campo situado junto a `Acción debe ser`, escriba el nombre de la acción y pulse `Enter`. Puede introducir más de un valor pulsando `Enter` después de cada selección. Compruebe el nombre de cada acción en [Eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
+5. Puedes agregar filtros más específicos para consultar eventos con más precisión haciendo clic en el botón `Agregar filtro`.
+6. Selecciona el parámetro del filtro (_Autor_ o _Detalles del evento_) e indica el valor al que se debe comparar. Puede introducir más de un valor pulsando `Enter` después de cada selección.
+
+    Al agregar filtros con el mismo parámetro (ejemplo: `Acción = Change Promotion Configuration` o `Change Coupon Configuration`), los resultados incluyen eventos que sean iguales a cualquiera de los valores ingresados. Al agregar filtros con parámetros diferentes (ejemplo: `Acción = Change Coupon Configuration` y `Autor = email@email.com`), los criterios se suman.
+
+    Ten en cuenta que puedes repetir los pasos 4 y 5 para agregar más filtros.
+
+    Por ejemplo, la consulta que corresponde a la siguiente imagen devuelve resultados cuyas acciones son _Change Promotion Configuration_ o _Change Coupon Configuration_ y cuyo autor es `email@mail.com`.
+
+    ![filtros-es (1)](//images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/2898f4f9247621f62bbe7fa00a65a313/filtros-es__1_.png)
+
+7. Haz clic en el botón `Aplicar` para obtener los eventos encontrados.
+
+    Consulta la sección [Resultados](#resultados) para entender la presentación de los eventos.
+
+<div class= "alert alert-warning">
+  <p>Los resultados de consulta corresponden exactamente al contenido ingresado en la casilla del filtro. Para evitar resultados inesperados, comprueba que no se hayan ingresado espacios adicionales en los términos de consulta.</p>
+</div>
+
+Si lo deseas, puedes compartir la consulta con otro usuario haciendo clic en `Compartir consulta` en la parte superior derecha de la página. El enlace a la búsqueda de Audit se copiará en su portapapeles.
+
+### Resultados
+
+La sección **Resultados** lista cada evento encontrado en la consulta y muestra la información de cada evento, según la tabla a continuación.
+
+| Columna | Descripción |
+|---|---|
+| __Copiar evento__ | Botón para copiar la información del evento que se muestra en la tabla al portapapeles. |
+| __Hora del evento__ | Fecha y hora en que ocurrió el evento, mostradas en la zona horaria del navegador o del sistema operativo. |
+| __Acción__ | Acción realizada en la aplicación seleccionada para la consulta. Consulta las posibles acciones en la [lista de eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ). |
+| __Detalles del evento__ | Información adicional sobre el evento. Consulta los detalles de cada evento en la [lista de eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ). |
+| __Autor__ | Email, ID o token del usuario que realizó el evento. |
+| __Más detalles__ | Botón que abre un modal con más información sobre el evento, cuando corresponda. Los detalles mostrados pueden incluir: <ul><li class="t-body mb5 lh-copy"><strong>Nombre de la entidad:</strong> ID de la entidad modificada.</li><li class="t-body mb5 lh-copy"><strong>Entidad antes de la acción:</strong> información de la entidad antes del evento, en formato <a href="http://www.json.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" rel="noopener noreferrer" target="_blank">JSON</a>.</li><li class="t-body mb5 lh-copy"><strong>Entidad después de la acción:</strong> información de la entidad después del evento, en formato <a href="http://www.json.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" rel="noopener noreferrer" target="_blank">JSON</a>.</li></ul>La exhibición completa de la información previamente mencionada puede variar dependiendo del evento. Por ejemplo, un evento para eliminar información mostrará únicamente la entidad antes de la acción. Sin embargo, un evento que implica agregar información solo mostrará la entidad después de la acción. <br /><br /> Algunos eventos no proporcionan ninguna información adicional. En estos casos, el modal aparece vacío. |
+
+### Ejemplos de consultas
+
+A continuación, listamos algunos escenarios de consulta comunes para ilustrar cómo se deben componer los filtros con base en lo que deseas obtener.
+
+#### Activación de producto
+
+Para consultar si un producto fue activado en el Catálogo en determinada fecha:
+
+1. Selecciona la fecha deseada.
+2. En el menú **Aplicación**, selecciona _Catálogo (Admin)_.
+3. Agrega un filtro cuya **Acción** deba ser igual a `Product Activation`.
+4. Agrega un filtro cuyos **Detalles del evento** deban ser igual a `product id "X" activated`, donde `X` sea el ID del producto deseado.
+
+#### Cambio de precio
+
+Para consultar si el precio de un SKU fue modificado en determinada fecha:
+
+1. Selecciona la fecha deseada.
+2. En el menú **Aplicación**, selecciona _Precios_.
+3. Agrega un filtro cuya **Acción** sea igual a `Put Price`.
+4. Agrega un filtro cuyos **Detalles del evento** sean igual al ID del SKU del ítem deseado.
+
+#### Exclusión de stock
+
+Para consultar si un stock fue eliminado en determinada fecha:
+
+1. Selecciona la fecha deseada.
+2. En el menú **Aplicación**, selecciona _Stock y envío_.
+3. Agrega un filtro cuya **Acción** sea igual a `Warehouse Delete`.
+4. Agrega un filtro cuyos **Detalles del evento** sean igual al ID del ítem deseado.
+
+#### Exclusión de transportadora
+
+Para consultar si una transportadora fue eliminada en determinada fecha:
+
+1. Selecciona la fecha deseada.
+2. En el menú **Aplicación**, selecciona _Stock y envío_.
+3. Agrega un filtro cuya **Acción** sea igual a `Carrier Delete`.
+4. Agrega un filtro cuyos **Detalles del evento** sean igual al ID de la transportadora deseada.
+
+## Verificar las últimas consultas realizadas en Audit
+
+Toda consulta realizada en Audit se guarda en la pestaña **Últimas consultas**. Para repetir una consulta en esta pestaña, haz clic en el botón  correspondiente a la consulta que deseas rehacer.
+
+Esta pestaña contiene la siguiente información:
+
+| Columna | Descripción |
+|---|---|
+| Consultado el | Fecha y hora en que se realizó la consulta en Audit. |
+| Aplicación | Aplicación de VTEX en que se buscaron los eventos. |
+| Términos | Filtros utilizados en la consulta. |
+| Periodo | Fecha de inicio y fin del periodo seleccionado para la consulta. |
+| Rehacer consulta | Botón que permite repetir la consulta. |
+
+<div class= "alert alert-warning">
+  <p>Solo se almacenan 50 consultas en la pestaña <strong>Últimas consultas</strong>. Si deseas guardar consultas por encima de límite, agrégalas a los favoritos de tu navegador.</p>
+</div>
+
diff --git a/docs/tutorials/es/authentication.md b/docs/tutorials/es/authentication.md
new file mode 100644
index 000000000..095bfcf32
--- /dev/null
+++ b/docs/tutorials/es/authentication.md
@@ -0,0 +1,86 @@
+---
+title: 'Autenticación'
+id: 21CkKHLKP1o41lUpGhuRUs
+status: PUBLISHED
+createdAt: 2021-10-25T19:06:37.982Z
+updatedAt: 2024-02-26T20:32:47.823Z
+publishedAt: 2024-02-26T20:32:47.823Z
+firstPublishedAt: 2021-11-08T18:39:50.432Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: autenticacion
+locale: es
+legacySlug: pagina-de-autenticacion
+subcategory: 14V5ezEX0cewOMg0o0cYM6
+---
+
+La autenticación es el procedimiento de validación de la identidad de los usuarios. En VTEX, este proceso tiene lugar en tres escenarios diferentes:
+
+* [Inicio de sesión](#inicio-de-sesion): verificación y validación de la identidad de los usuarios que desean acceder a una tienda virtual o al Admin VTEX.
+* [Desarrollo de integraciones](#desarollo-de-integraciones): autentica las requests realizadas a las API de VTEX a partir de integraciones con servicios externos. Esta validación suele realizarse mediante claves de API o tokens de usuario.
+* [Desarrollo de aplicaciones](#desarollo-de-aplicaciones): garantiza la legitimidad de la comunicación entre las aplicaciones desarrolladas con VTEX IO y las API de VTEX. Esta validación suele realizarse mediante tokens de autenticación.
+
+## Inicio de sesión
+
+En VTEX, la autenticación por inicio de sesión se produce en dos contextos: en la tienda virtual, cuando los clientes inician sesión para acceder a su perfil o realizar una compra, y en el Admin VTEX, cuando los usuarios administrativos inician sesión para operar en el entorno administrativo de la tienda.
+
+Es necesario configurar el método de autenticación que se ofrecerá en cada contexto. Consulta las opciones disponibles en la siguiente tabla:
+
+| Opciones de inicio de sesión | Descripción | Tienda virtual | Admin |
+|---|---|---|---|
+| Código de acceso | Se envía al email del usuario un código numérico aleatorio; el usuario debe informar dicho código para iniciar sesión. | Se puede activar | Siempre activa |
+| Contraseña | El usuario puede registrar una contraseña e iniciar sesión utilizando el email y la contraseña registrados. El retailer puede activar la opción [Vencimiento de la contraseña](#vencimiento-de-la-contrasena) después de un período específico para usuarios del Admin. | Se puede activar | Siempre activa. Se puede activar el vencimiento de la contraseña. |
+| Facebook | El usuario inicia sesión utilizando su cuenta de Facebook. Consulta la guía [Configurar inicio de sesión con Facebook y Google](https://help.vtex.com/es/tutorial/configurar-login-com-facebook-e-google--tutorials_513) para más detalles. | Se puede activar | No disponible |
+| Google | El usuario inicia sesión utilizando su cuenta de Google. Consulta la guía [Configurar inicio de sesión con Facebook y Google](https://help.vtex.com/es/tutorial/configurar-login-com-facebook-e-google--tutorials_513) para más detalles. | Se puede activar | Se puede activar |
+| Integración con otros proveedores de identidad | El usuario puede iniciar sesión utilizando su cuenta de otros proveedores de identidad externos a partir de una integración. Consulta la guía para desarrolladores [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) para obtener más detalles. | Se puede activar utilizando el protocolo OAuth.  Consulta la guía para desarrolladores [Webstore (OAuth 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) para obtener más detalles. | Se puede activar utilizando o protocolo SAML. Consulta la guía para desarrolladores [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) para obtener más detalles. |
+
+<div class="alert alert-info">
+  <p>Al menos una de las opciones de inicio de sesión de la tabla anterior debe estar activa en la tienda virtual.</p>
+</div>
+
+<div class="alert alert-warning">
+  <p>Para acceder al Admin VTEX es necesario tener un <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512">usuario</a> administrativo registrado. Los <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> relacionados con el usuario y los permisos propios de dicho rol determinan los <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recursos</a> que ese usuario puede utilizar en el Admin.</p>
+</div>
+
+### Activar formas de inicio de sesión
+
+En la página **Autenticación**, puedes elegir las opciones de inicio de sesión que deseas ofrecer a los clientes de tu tienda y a los usuarios administrativos que tendrán acceso al Admin de tu cuenta.
+
+![Página de autenticación](//images.ctfassets.net/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/ed710d537b491e8a182de685fa8d0d97/Tela_de_Autentica____o_ES.png)
+
+Sigue estos pasos para activar las opciones de inicio de sesión que desees:
+
+1. En la barra superior del Admin VTEX, haz clic en el avatar de tu perfil que tiene la inicial de tu email.
+2. Haz clic en **Configuración de la cuenta > Autenticación**.
+
+    Se te redirigirá a la pestaña **Tienda virtual**, donde se muestran los métodos de inicio de sesión disponibles en tu tienda virtual. En esta pestaña puedes activar las opciones para el inicio de sesión de los clientes.
+
+    Para configurar métodos de inicio de sesión en el Admin para usuarios administrativos, haz clic en la pestaña **Admin**.
+
+    Consulta la tabla en la sección [Inicio de sesión](#inicio-de-sesion) para conocer los métodos de inicio de sesión disponibles y acceder a la documentación que explica cómo configurarlos.
+
+### Vencimiento de la contraseña de usuarios del Admin
+
+Si la opción de inicio de sesión con contraseña está activada, puedes establecer la expiración de las contraseñas de usuario del Admin después de un número específico de días. Para llevar a cabo esta acción, sigue las instrucciones a continuación:
+
+1. En la barra superior del Admin VTEX haz clic en el avatar de tu perfil, marcado con la inicial de tu email.
+2. Haz clic en **Configuración de la cuenta > Autenticación**.
+3. Ve a la pestaña **Admin**.
+4. En la fila **Contraseña**, haz clic en `Editar`.
+5. Marca la opción** Vencimiento de la contraseña**.
+6. Selecciona el periodo después del cual la contraseña de los usuarios perderá su validez. Puedes elegir entre **15**, **30** o **90** días.
+7. Haz clic en `Guardar`.
+
+Tras el periodo especificado, al intentar iniciar sesión, el usuario del Admin deberá restablecer su contraseña.
+
+## Desarrollo de integraciones
+
+Al desarrollar integraciones utilizando las [API](https://developers.vtex.com/docs/guides/getting-started) de VTEX, es necesario proporcionar parámetros de autenticación para realizar las operaciones deseadas. Consulta a continuación los métodos disponibles:
+
+* **Claves de aplicación (appKeys):** las [claves de aplicación](https://help.vtex.com/es/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) se utilizan para autenticar los requests a las API de VTEX. Los administradores de la tienda pueden crear claves y asociarlas a [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) con permisos para utilizar determinados [recursos](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) de la plataforma. Consulta más información en la siguiente guía para desarrolladores, [API authentication using application keys](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys).
+* **Tokens de usuario:** los tokens de usuario se utilizan para autenticar los requests de API, especialmente para aplicaciones [frontend](https://help.vtex.com/es/tracks/desarrollo-de-la-tienda--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl) desarrolladas con VTEX IO. Consulta más información en la siguiente guía para desarrolladores, [API authentication using user tokens](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens).
+
+## Desarrollo de aplicaciones
+
+El uso de tokens de autenticación (auth tokens) es necesario para la autenticación cuando se desarrollan aplicaciones en VTEX IO. Consulta más información en la siguiente guía para desarrolladores, [App authentication using auth tokens](https://developers.vtex.com/docs/guides/app-authentication-using-auth-tokens).
diff --git a/docs/tutorials/es/autocomplete.md b/docs/tutorials/es/autocomplete.md
new file mode 100644
index 000000000..3ca439981
--- /dev/null
+++ b/docs/tutorials/es/autocomplete.md
@@ -0,0 +1,75 @@
+---
+title: 'Autocomplete'
+id: 6qhP0ZQ4JqUBdgFnbnxS4a
+status: PUBLISHED
+createdAt: 2024-06-27T16:42:03.645Z
+updatedAt: 2024-06-27T16:42:56.071Z
+publishedAt: 2024-06-27T16:42:56.071Z
+firstPublishedAt: 2024-06-27T16:42:56.071Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: autocomplete
+locale: es
+legacySlug: autocomplete
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+
+<div class = "alert alert-warning">
+    Autocomplete es una herramienta que ya está activa en VTEX Intelligent Search. No es posible desactivarla en el Admin.
+    </div>
+
+Autocomplete funciona según la información obtenida a través del historial de búsqueda de términos relacionados con el Catálogo. Estos resultados se muestran en cuatro listas diferentes, que pueden estar juntas o separadas, dependiendo de la interacción con el cliente. Las secciones son:
+
+- Últimas búsquedas realizadas.
+- Sugerencia de búsqueda.
+- Sugerencia de productos.
+- Términos más buscados.
+
+<div class="alert alert-warning" role="alert">
+<p>Cuando se busca un término no registrado, Autocomplete no encuentra productos con las especificaciones deseadas y no muestra ninguna sugerencia.
+</p>
+</div>
+
+Durante la interacción con la barra de búsqueda, VTEX Intelligent Search inmediatamente muestra el conjunto de Términos más buscados y Últimas búsquedas, si el cliente ya ha realizado alguna búsqueda.
+
+Cuando el usuario comienza a escribir, el sistema muestra las Sugerencias de búsqueda y Sugerencias de productos y elimina las listas anteriores.
+
+<div class = "alert alert-info">
+  <p>La información de las secciones <b>Términos más buscados</b> y <b>Sugerencia de búsquedas</b> es actualizada diariamente. Para la actualización, se utilizan los datos de los últimos 14 días de interacción de los clientes con la búsqueda.</p>
+  </div>
+
+De esta forma, es posible proporcionar al cliente una experiencia de búsqueda más fluida y personalizada. Así puede ver el resultado rápidamente, además de recibir sugerencias basadas en su búsqueda. 
+
+Otra ventaja para el administrador de la tienda es el aumento de conversión, que es el resultado de la dinámica de facilidad de uso y experiencia.
+
+<div class = "alert alert-info">
+  <p>Autocomplete ofrece sugerencias de búsqueda incluso cuando la tienda es nueva y aún no muestra datos de interacciones con los clientes, como clics y búsquedas.
+    En este caso, la funcionalidad genera sugerencias de búsqueda a partir de un algoritmo que extrae palabras clave del catálogo, productos, marcas y categorías registradas en la tienda.
+</p>
+  </div>
+
+## Términos más buscados
+
+En esta sección se muestran los términos más buscados por otros clientes dentro del sitio web.
+
+![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+
+## Últimas búsquedas realizadas
+
+En esta sección se muestran las últimas búsquedas realizadas por el cliente. Así, es posible comenzar la interacción con la búsqueda instantáneamente.
+
+![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+
+## Sugerencia de búsquedas
+
+En esta sección se muestran los términos buscados por otros usuarios que se relacionan con la búsqueda realizada en ese momento. Además de términos, también se sugieren categorías relacionadas con la búsqueda.
+
+![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+
+## Sugerencia de productos
+
+En esta sección se muestran los productos que coinciden con la búsqueda realizada en ese momento. Así, al mostrar productos relacionados con su búsqueda durante la escritura, se reducen las interrupciones y se le permite al usuario realizar una compra más dinámica.
+
+![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tutorials/es/availability.md b/docs/tutorials/es/availability.md
new file mode 100644
index 000000000..4f93c7eb0
--- /dev/null
+++ b/docs/tutorials/es/availability.md
@@ -0,0 +1,32 @@
+---
+title: 'Disponibilidad'
+id: 3ZcZOzTSr2RdauUbn7qTa9
+status: PUBLISHED
+createdAt: 2024-06-24T17:51:07.903Z
+updatedAt: 2024-06-24T18:00:08.767Z
+publishedAt: 2024-06-24T18:00:08.767Z
+firstPublishedAt: 2024-06-24T18:00:08.767Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: disponibilidad
+locale: es
+legacySlug: disponibilidad
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Al elaborar un resultado de búsqueda, VTEX Intelligent Search tiene en cuenta la disponibilidad de cada producto encontrado en la búsqueda. Los productos disponibles siempre tendrán prioridad sobre los no disponibles en los resultados de búsqueda. 
+
+Al verificar la disponibilidad del producto, VTEX Intelligent Search utiliza el campo **Mostrar producto agotado** registrado en el [Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) para saber qué productos se mostrarán aunque no estén disponibles. Si la configuración del producto determina que no debe mostrarse cuando esté fuera de stock, la plataforma no presentará el producto. Sin embargo, si la configuración indica que el producto debe mostrarse incluso cuando esté sin stock, la plataforma lo colocará al final de los resultados de búsqueda.
+
+VTEX Intelligent Search también verifica si:
+
+- El producto en cuestión está activo.
+- Al menos un SKU del producto está activo.
+- La categoría del producto está activa.
+- La marca del producto está activa.
+- El campo **Mostrar en la tienda** del producto está configurado como activo.
+
+Tras verificar la disponibilidad, el sistema combina ítems de tu tienda, del catálogo de los [sellers](https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w) y las configuraciones de las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) registradas para llegar al precio y stock finales. Si alguno de estos ítems tiene precio y stock, el producto está disponible. Cada vez que el stock y el precio del producto cambian, se programa una nueva [indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) y se actualiza esta información.
+
+Se pueden añadir otros factores, como [Relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) y [Reglas de _merchandising_](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), para influir en el resultado. Sin embargo, la disponibilidad seguirá siendo el criterio más importante para el resultado de búsqueda. 
diff --git a/docs/tutorials/es/b2b-checkout-settings.md b/docs/tutorials/es/b2b-checkout-settings.md
new file mode 100644
index 000000000..da228c04b
--- /dev/null
+++ b/docs/tutorials/es/b2b-checkout-settings.md
@@ -0,0 +1,72 @@
+---
+title: 'B2B Checkout Settings'
+id: u7wG1SjmeCqXCSF2UsVok
+status: PUBLISHED
+createdAt: 2024-07-26T14:09:31.973Z
+updatedAt: 2024-07-26T19:06:26.485Z
+publishedAt: 2024-07-26T19:06:26.485Z
+firstPublishedAt: 2024-07-26T18:46:07.935Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-checkout-settings-es
+locale: es
+legacySlug: b2b-checkout-settings-es
+subcategory: 6sgdAY3pCuZ7qNws6gnzDX
+---
+
+La aplicación **B2B Checkout Settings** forma parte de la solución [B2B Suite](https://help.vtex.com/es/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3) de VTEX, una colección de aplicaciones que permiten a las tiendas gestionar organizaciones, roles y permisos de storefront, así como la configuración del checkout para relaciones comerciales B2B.
+
+Las transacciones B2B (business-to-business) son más complejas que las B2C (business-to-consumer). Las empresas B2B suelen tratar con:
+
+- Pedidos de gran volumen.
+- Contratos personalizados.
+- Condiciones de pago específicas.
+- Una gama diversificada de clientes.
+
+En el comercio B2B es necesario ofrecer opciones personalizadas durante el checkout. Estas personalizaciones incluyen:
+
+- Disponibilizar medios de pago para cada organización o centro de costos.
+- Direcciones predefinidas.
+- Agregar un campo para ingresar número de orden de compra.
+- Ofrecer la opción de crear una cotización de pedido antes de realizar una compra real.
+
+La aplicación **B2B Checkout Settings** complementa otras aplicaciones de [B2B Suite](https://help.vtex.com/es/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3#aplicativo-configuracoes-de-checkout-b2b) para ampliar la experiencia de checkout a usuarios que son miembros de una organización.
+
+## Roles de Checkout
+Esta aplicación verifica automáticamente los roles de los usuarios que forman parte de la organización y se comunica con la aplicación [B2B Organizations](https://help.vtex.com/es/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#aplicativo-organizacoes-b2b). También confirma que los usuarios disponen de los [permisos](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) necesarios para acceder al checkout al interactuar con la aplicación [*Storefront Permissions*](https://help.vtex.com/es/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA).
+
+De forma predeterminada, cualquier usuario con un rol que permita el acceso al storefront puede acceder al checkout, excepto aquellos con el rol Organization Buyer. Si un usuario intenta proseguir al checkout sin contar con el permiso necesario, recibirá una notificación con el mensaje: No tienes acceso al checkout.
+
+## Direcciones de los centros de costos
+La aplicación **B2B Checkout Settings** se comunica con la aplicación [B2B Organizations](https://help.vtex.com/es/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3#aplicativo-organizacoes-b2b) y proporciona una lista con las direcciones del centro de costos asociadas al usuario durante la etapa de checkout.
+
+## Campo número de orden de compra
+Una orden de compra (PO) es un acuerdo comercial entre una empresa compradora y una tienda B2B por el que se autoriza el pago de productos o servicios que se entregarán en el futuro, en un plazo determinado.
+
+Disponer de un número de orden de compra permite a los clientes B2B pagar las compras autorizadas utilizando ese número como referencia. La empresa que realiza la compra autoriza y emite la orden de compra con antelación.
+
+Utilizando la aplicación **B2B Checkout Settings**, puedes habilitar un campo opcional de Número de referencia u orden de compra para que los clientes ingresen esta información durante la etapa de checkout.
+
+## Personalizaciones en B2B Checkout Settings
+Las tiendas B2B requieren personalizaciones específicas en el proceso de checkout. Por eso, la aplicación B2B Checkout Settings ofrece una página de checkout personalizada, ideal para estos escenarios. Este recurso permite personalizar la página de checkout según las necesidades de tu tienda.
+
+En la sección siguiente, veremos cómo configurar la aplicación B2B Checkout Settings.
+
+### Configurar la aplicación B2B Checkout Settings
+Sigue las instrucciones a continuación para personalizar el proceso de checkout B2B en tu tienda:
+
+<ol start="1">
+<li>En el Admin VTEX, ve a <strong>Configuración de la tienda > Storefront > B2B Checkout Settings</strong>, ou digite <strong>B2B Checkout Settings</strong> en la barra de búsqueda de la parte superior de la página.</li>
+<li>Al activar <code>Mostrar campo de número de orden de compra (PO)</code>, se incluirá en la página de compra durante el proceso de checkout un campo destinado a ingresar dicho número.
+</li>
+<li>Al activar <code>Mostrar el botón Crear una cotización</code>, se agregará el botón <code>Crear una cotización</code>  en el checkout, lo que permite crear un presupuesto utilizando el contenido actual del carrito.</li>
+</ol>
+
+<div class = "alert alert-info">
+Solo se debe activar el botón <code>Crear una cotización</code> si tu tienda tiene instalada la aplicación B2B Quotes & Carts. Para más información consulta  <a href="https://developers.vtex.com/docs/apps/vtex.b2b-quotes">B2B Quotes & Carts</a>.
+</div>
+
+<ol start="4">
+<li>Haz clic en <code>Guardar</code>.</li>
+</ol>
diff --git a/docs/tutorials/es/b2b-cost-center-management.md b/docs/tutorials/es/b2b-cost-center-management.md
new file mode 100644
index 000000000..5fcd28164
--- /dev/null
+++ b/docs/tutorials/es/b2b-cost-center-management.md
@@ -0,0 +1,101 @@
+---
+title: 'Gestión de centros de costos en B2B'
+id: 2fjt1Layng8iKdvEEzRhuk
+status: PUBLISHED
+createdAt: 2024-07-25T10:55:43.882Z
+updatedAt: 2024-07-25T16:15:44.248Z
+publishedAt: 2024-07-25T16:15:44.248Z
+firstPublishedAt: 2024-07-25T13:38:42.344Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gestion-de-centros-de-costos-en-b2b
+locale: es
+legacySlug: gestion-de-centros-de-costos-en-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+En el contexto de las organizaciones B2B, los centros de costos representan unidades de negocio o departamentos vinculados a una organización específica. La funcionalidad facilita la gestión y asociación de centros de costos clave para tu organización, lo que simplifica la asignación y análisis de los gastos financieros.
+
+## Agregar centro de costos
+Para agregar un centro de costos vía Admin VTEX, accede a **Apps> Organizaciones y centros de costos B2B > Organizaciones** o ingresa **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+
+Para agregar un nuevo centro de costos sigue los pasos a continuación:
+
+<ol>
+  <li>Haz clic en el nombre de la organización.</li>
+  <li>Después, en la pestaña <strong>Centros de costos</strong>.</li>
+  <li>Haz clic en <code>Nuevo</code>.</li>
+  <li>
+    Rellena los campos solicitados, especificados a continuación:
+    <ul>
+      <li><strong>Nombre</strong>: nombre del centro de costos que deseas asociar a la organización.</li>
+      <li><strong>Número de teléfono</strong>: teléfono para ponerse en contacto con la organización.</li>
+      <li><strong>Documento empresarial</strong>: puede ser el número de registro corporativo, el número de identificación fiscal, el número de IVA u otro documento.</li>
+      <li><strong>Inscripción estatal</strong>: número de registro de la empresa.</li>
+      <li><strong>País</strong>: país donde se encuentra el centro de costos.</li>
+      <li><strong>Código postal</strong>: código postal del centro de costos.</li>
+      <li><strong>Dirección</strong>: nombre de la calle donde se ubica el centro de costos.</li>
+      <li><strong>Número</strong>: número de la dirección donde se encuentra el centro de costos.</li>
+      <li><strong>Información adicional</strong>: información que puede complementar la dirección del centro de costos.</li>
+      <li><strong>Barrio</strong>: nombre del barrio donde se ubica el centro de costos.</li>
+      <li><strong>Ciudad</strong>: ciudad donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.</li>
+      <li><strong>Estado</strong>: estado donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.</li>
+      <li><strong>Destinatario</strong>: nombre de la persona que recibirá los pedidos en la dirección informada.</li>
+    </ul>
+  </li>
+  <li>Haz clic en el botón <code>Agregar</code>.</li>
+  <li>Haz clic en <code>Guardar</code> en la esquina superior derecha de la página después de cualquier cambio.</li>
+</ol>
+
+## Información del centro de costos
+Para ver, agregar o editar los detalles de un centro de costos en el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones** o ingresa **Organizaciones** en la barra de búsqueda de la parte superior de la página.
+
+Consulta los pasos a continuación para agregar un centro de costos:
+
+1. Haz clic en el nombre de la organización.
+2. Después, en la pestaña **Centros de costos**.
+3. Haz clic en `Nuevo` y rellena los campos del formulario.
+4. Para agregar información, haz clic en el centro de costos y rellena los campos.
+5. Haz clic en `Agregar`. 
+
+### Formulario del centro de costos
+El formulario para ver o editar el centro de costos se divide en las siguientes secciones:
+- [Campos de información](#campos-de-información)
+- [Direcciones](#direcciones)
+- [Campos personalizados](#campos-personalizados)
+
+#### Campos de información
+En esta página, puedes ver o editar los siguientes campos:
+- **Nombre:** nombre del centro de costos que deseas asociar a la organización.
+- **Número de teléfono:** teléfono para ponerse en contacto con la organización.
+- **Documento empresarial:**  puede ser el número de registro corporativo, el número de identificación fiscal, el número de IVA u otro documento.
+- **Inscripción estatal:** número de registro de la empresa.
+
+#### Direcciones
+Para editar o eliminar una dirección existente, haz clic en <i class="fas fa-ellipsis-v" aria-hidden="true"></i> y selecciona `Editar` o `Eliminar`.
+
+Si deseas agregar una nueva dirección de envío relacionada con este centro de costos, sigue estas instrucciones:
+
+<ol>
+  <li>Haz clic en el botón <code>Agregar nueva dirección</code>.</li>
+  <li>
+    Rellena la información requerida sobre la nueva dirección:
+    <ul>
+      <li><strong>País</strong>: país donde se encuentra el centro de costos.</li>
+      <li><strong>Código postal</strong>: código postal del centro de costos.</li>
+      <li><strong>Dirección</strong>: nombre de la calle donde se ubica el centro de costos.</li>
+      <li><strong>Información adicional</strong>: información que puede complementar la dirección del centro de costos.</li>
+      <li><strong>Ciudad</strong>: ciudad donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.</li>
+      <li><strong>Estado</strong>: estado donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.</li>
+      <li><strong>Destinatario</strong>: nombre de la persona que recibirá los pedidos en la dirección informada.</li>
+    </ul>
+  </li>
+  <li>Haz clic en el botón <code>Agregar</code>.</li>
+  <li>Haz clic en <code>Guardar</code> en la esquina superior derecha de la página después de cualquier cambio.</li>
+  <li>Haz clic en <code>Eliminar</code> para remover el centro de costos.</li>
+</ol>
+
+#### Campos personalizados
+Los campos personalizados permiten a los usuarios agregar información relevante para la empresa. Para más información, consulta [Campos personalizados en el registro  de organizaciones](https://help.vtex.com/es/tutorial/campos-personalizados-no-cadastro-de-organizacao--2MqEVusOvcbqagNwOuHA7f).
+
diff --git a/docs/tutorials/es/b2b-organization-general-settings.md b/docs/tutorials/es/b2b-organization-general-settings.md
new file mode 100644
index 000000000..bea90537d
--- /dev/null
+++ b/docs/tutorials/es/b2b-organization-general-settings.md
@@ -0,0 +1,34 @@
+---
+title: 'Configuración general de organizaciones B2B'
+id: 6OSJHuiJJ7beRZaflNtzx5
+status: PUBLISHED
+createdAt: 2024-06-07T11:34:25.125Z
+updatedAt: 2024-06-07T11:45:51.047Z
+publishedAt: 2024-06-07T11:45:51.047Z
+firstPublishedAt: 2024-06-07T11:44:14.228Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configuracion-general-de-organizaciones-b2b
+locale: es
+legacySlug: configuracion-general-de-organizaciones-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+La pantalla de configuración general permite registrar la información básica de cada organización B2B integrada en VTEX.
+
+En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones**, o ingresa **Organizaciones** en la barra de búsqueda de la parte superior de la página.
+
+1.	Haz clic en el nombre de la organización.
+
+2.	Haz clic en la pestaña General.
+
+3.	Rellena la información necesaria:
+    - **Nombre de la organización:** nombre de la organización ingresado durante el registro.
+    - **Nombre comercial:** nombre comercial que la empresa utiliza.
+    - **Status:** indica si la organización compradora está activa.
+    - **Campos personalizados:** campos adicionales de una organización.
+
+![Configurações gerais organizações - ES](//images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/274406c28db0e41c23bfee501214b547/Configura__es_gerais_organiza__es_-_ES.gif)
+
+Asegúrate de hacer clic en el botón `Guardar` en la parte superior derecha de la página al realizar cualquier cambio.
diff --git a/docs/tutorials/es/b2b-overview.md b/docs/tutorials/es/b2b-overview.md
index 118405e0c..adf5fd751 100644
--- a/docs/tutorials/es/b2b-overview.md
+++ b/docs/tutorials/es/b2b-overview.md
@@ -3,8 +3,8 @@ title: 'B2B: visión general'
 id: 5vb9SNXhX2bZnkpAh7ADdC
 status: PUBLISHED
 createdAt: 2021-03-30T12:31:10.644Z
-updatedAt: 2021-05-11T17:43:13.209Z
-publishedAt: 2021-05-11T17:43:13.209Z
+updatedAt: 2024-05-10T13:56:48.012Z
+publishedAt: 2024-05-10T13:56:48.012Z
 firstPublishedAt: 2021-03-30T18:43:45.812Z
 contentType: tutorial
 productTeam: B2B
@@ -12,7 +12,7 @@ author: 7qy2DBsUp8U5P9lqV0JHfR
 slug: b2b-vision-general
 locale: es
 legacySlug: vision-general
-subcategory: 5N5GjDrKSycIQMeoS7CLtj
+subcategory: 1PSq4adEARlFaK5Mdv74Y7
 ---
 
 Es habitual separar el ecommerce en dos tipos de modelo de negocio: B2C (Business to Consumer) y B2B (Business to Business).
diff --git a/docs/tutorials/es/b2b-store-settings.md b/docs/tutorials/es/b2b-store-settings.md
new file mode 100644
index 000000000..b0ece9789
--- /dev/null
+++ b/docs/tutorials/es/b2b-store-settings.md
@@ -0,0 +1,42 @@
+---
+title: 'Configuración de tiendas B2B'
+id: 7riBcnrOv4Cz7qMeACyVLm
+status: PUBLISHED
+createdAt: 2023-10-11T15:17:39.003Z
+updatedAt: 2024-06-06T16:33:44.798Z
+publishedAt: 2024-06-06T16:33:44.798Z
+firstPublishedAt: 2023-10-19T13:27:04.087Z
+contentType: tutorial
+productTeam: B2B
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: configuracion-de-tiendas-b2b
+locale: es
+legacySlug: configuracion-de-tiendas-b2b
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+Consulta en esta página los pasos para realizar la configuración general de tu tienda B2B.  
+
+1. En tu Admin VTEX, accede a Aplicaciones > Organizaciones y centros de costos B2B > Organizaciones, o ingresa Organizaciones y centros de costos B2B en la barra de búsqueda.
+2. Define la configuración general
+
+- **Auto approve new organizations:** selecciona esta opción si deseas que la aprobación de las nuevas organizaciones sea de manera automática.
+- **Make business document ready only:** al seleccionar esta opción, el comprador no podrá editar el campo Business document.
+- __Make state registration ready only:__ al seleccionar esta opción, el comprador no podrá editar el campo State registration.
+- __Use modal to switch company:__ esta opción mejorará la experiencia del usuario al facilitar el mantenimiento de las tiendas. 
+- __Clear cart when switching company or logging in:__ al seleccionar esta opción, si cambias de tienda o inicias sesión en otras cuentas se limpiará el carrito automáticamente.
+## Términos de pago
+![Tiendas B2B - General Settings + Payment Terms](//images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/2fe3ea82f74231488ec3b9d0d3ce3d57/image1.jpg)
+Puedes agregar medios de pago seleccionándolos según las necesidades de tu negocio.   
+Ejemplo: tarjeta de crédito, débito o pagarés. 
+## Tablas de precios
+Puedes agregar un patrón predeterminado de precios para las tiendas añadidas. Lea más sobre tablas de precios en [Pricing](https://developers.vtex.com/docs/guides/pricing-overview)
+
+## Políticas comerciales
+
+Puedes vincular tu tienda directamente con políticas comerciales y canales de venta.
+![Tiendas B2B -  Políticas comerciais ES](//images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/348fed16a33c05d72acf883315d48c6d/image2.jpg)
+
+1. En la lista **Políticas comerciales disponibles**, haz clic en la política comercial que deseas incluir en tu tienda y luego haz clic en `Agregar a política comercial`; esta se mostrará en la lista **Políticas comerciales seleccionadas**.
+2. Haz clic en `Guardar` al finalizar los ajustes.
+
diff --git a/docs/tutorials/es/b2b-suite-overview.md b/docs/tutorials/es/b2b-suite-overview.md
new file mode 100644
index 000000000..fd715c5b9
--- /dev/null
+++ b/docs/tutorials/es/b2b-suite-overview.md
@@ -0,0 +1,93 @@
+---
+title: 'B2B Suite - Visión general'
+id: 5eG6UfveWrai7looK0kVG3
+status: PUBLISHED
+createdAt: 2024-05-09T10:31:51.517Z
+updatedAt: 2024-05-10T18:37:56.917Z
+publishedAt: 2024-05-10T18:37:56.917Z
+firstPublishedAt: 2024-05-10T11:07:09.230Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-suite-vision-general
+locale: es
+legacySlug: b2b-suite-vision-general
+subcategory: 1PSq4adEARlFaK5Mdv74Y7
+---
+
+B2B Suite es un conjunto de [aplicaciones VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) que permite a las tiendas gestionar organizaciones, permisos de acceso y configuraciones de checkout para relaciones comerciales B2B, entre otras funciones. Estos recursos son importantes para simplificar el flujo de compra, reducir costos y ofrecer una experiencia de compra personalizada.
+
+Los clientes B2B desempeñan distintos roles dentro de tu organización, como compradores, gestores o supervisores. Cada rol está asociado a un conjunto diferente de permisos de tienda, dependiendo de las acciones que el usuario necesite llevar a cabo.
+
+Algunas de las funcionalidades clave de B2B Suite son:
+
+- **Agrupación de usuarios:** centralización de varios usuarios de una misma empresa en una sola organización, lo que facilita una gestión unificada.
+
+- **Medios de pago personalizados:** configuración de medios de pago específicos para cada cliente, atendiendo a sus necesidades particulares.
+
+- **Selección de productos y fijación de precios:** adaptación de la selección de productos y estructuración de precios individualizados para cada cliente, esencial para las transacciones B2B.
+
+Durante el proceso de checkout, es importante ofrecer opciones personalizadas para satisfacer las necesidades específicas de los clientes B2B. Estas personalizaciones incluyen:
+
+- **Selección de medios de pago:** permite elegir medios de pago específicos por organización o centro de costo.
+
+- **Autocompletar dirección:** automatiza el llenado de la dirección para agilizar el proceso de checkout.
+
+- **Números de orden de compra:** facilita la inclusión de números de órdenes de compra, esenciales para rastreo y control.
+
+- **Cotizaciones de pedidos:** ofrece la posibilidad de obtener cotizaciones de pedidos durante el checkout.
+
+## Instalar B2B Suite en tu tienda
+
+Para instalar B2B Suite, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, accede a **Apps > Hub de extensiones > App Store** o ingresa **App Store** en la barra de búsqueda en la parte superior de la página.
+
+2. En la página de la App Store, encuentra **B2B Suite** en la galería de aplicaciones o ingresa **B2B Suite** en la barra de búsqueda de la página.
+
+3. A continuación, haz clic para instalar la aplicación.
+
+![Instalação B2B Suite - ES](//images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/c127f17208e4daeb0746bbb38f1c93b9/Instala__o_B2B_Suite_-_ES.gif)
+
+## Conjunto de aplicaciones B2B Suite
+
+Las aplicaciones que componen **B2B Suite** se desarrollaron para impulsar las operaciones de negocios B2B. Son las siguientes:
+
+### Storefront Permissions
+
+Almacena un conjunto predefinido de roles y permisos que determina lo que los usuarios B2B pueden acceder y realizar en el storefront. Es útil para operaciones que desean definir permisos específicos para usuarios con diferentes roles organizacionales.
+
+### Storefront Permissions UI
+
+Esta aplicación ofrece una interfaz para la aplicación Storefront Permissions, brindando a los usuarios del Admin VTEX la posibilidad de gestionar directamente las funciones B2B y los permisos de aplicaciones relacionadas por medio del propio Admin.
+
+### B2B Organizations
+
+Permite agrupar a los usuarios B2B en organizaciones a las que pueden asignarse medios de pago específicos, tablas de precios y colecciones de productos. Así, todos los usuarios de la organización comparten las mismas condiciones comerciales.
+
+Cada organización puede segmentarse en uno o varios centros de costos, con sus propias direcciones de envío, que estarán disponibles para los usuarios de los centros de costos en el momento del checkout.
+
+#### **Estructura organizacional**
+
+- **Organización compradora:** representa a una empresa u organización que realiza compras a través de la plataforma, pudiendo tener múltiples usuarios asociados y acceso a recursos específicos relacionados con sus necesidades comerciales.
+
+- **Usuarios:** son miembros o colaboradores de una organización B2B que están autorizados para acceder y operar la plataforma B2B Suite en nombre de la organización. Desempeñan funciones específicas en el proceso de compra, como realizar pedidos, gestionar catálogos de productos o aprobar transacciones. Cada usuario tiene un acceso controlado a los recursos de la plataforma en función de sus roles y permisos específicos.
+
+- **Centro de costos:** es una categoría o sector dentro de una organización B2B diseñada para la atribución y rastreo de costos asociados a actividades específicas o departamentos dentro de la empresa. Así, la empresa puede realizar un seguimiento más detallado y preciso de los gastos relacionados con las distintas áreas de negocios, facilitando una gestión eficiente de los gastos corporativos.
+
+### B2B Quotes & Carts
+
+Permite a los usuarios B2B crear cotizaciones y guardar carritos, que pueden compartirse con otros miembros de la organización. Los usuarios con los permisos adecuados en la tienda pueden modificar cotizaciones para aplicar descuentos o editar la cantidad de ítems, de modo que la cotización final pueda utilizarse para realizar un pedido.
+
+### B2B Checkout Settings
+
+Amplía la experiencia de checkout para usuarios que son miembros de organizaciones B2B. Esta aplicación permite ofrecer medios de pago específicos para la organización del usuario, autocompletar la dirección según el centro de costos del usuario, agregar un número de orden de compra al pedido y posibilitar que los clientes creen una cotización de pedido antes de realizar la compra.
+
+### B2B Orders History
+
+Proporciona una nueva página de Pedidos en [Mi cuenta](https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh) para que los usuarios B2B puedan ver todos los pedidos anteriores realizados por usuarios de su organización o centro de costos, en función de su rol.
+
+### B2B Admin Customers
+
+Proporciona funciones adicionales de gestión de información de clientes en el Admin VTEX, permitiendo a los administradores de la tienda crear, editar y buscar clientes.
+
diff --git a/docs/tutorials/es/b2b-trade-policies-overview.md b/docs/tutorials/es/b2b-trade-policies-overview.md
new file mode 100644
index 000000000..fd25b4d92
--- /dev/null
+++ b/docs/tutorials/es/b2b-trade-policies-overview.md
@@ -0,0 +1,33 @@
+---
+title: 'Vista general de las políticas comerciales en B2B'
+id: sKrYjDJPBChgIxzYFpUvu
+status: PUBLISHED
+createdAt: 2024-07-05T11:20:38.780Z
+updatedAt: 2024-07-05T11:34:04.566Z
+publishedAt: 2024-07-05T11:34:04.566Z
+firstPublishedAt: 2024-07-05T11:34:04.566Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: vista-general-de-las-politicas-comerciales-en-b2b
+locale: es
+legacySlug: vista-general-de-las-politicas-comerciales-en-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Asociar una [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) a una organización es imprescindible para una operación B2B. Esto permite aplicar reglas específicas de precios, descuentos y condiciones de pago, facilitando así la gestión personalizada de relaciones comerciales.
+
+El objetivo principal de las políticas comerciales en B2B es garantizar que todas las transacciones sigan las condiciones comerciales definidas por la empresa con el fin de brindar una experiencia de compra consistente y adaptada a las estrategias de negocio, incluyendo:
+- Establecer precios específicos para productos o grupos de productos, ajustándolos según sea necesario para diferentes clientes o sectores del mercado.
+- Configurar condiciones, plazo y medios de pago personalizados.
+- Implementar reglas específicas para calcular el envío y aplicar impuestos, en función de la ubicación y perfil del cliente.
+
+La correcta implementación y gestión de las políticas es importante para garantizar que la operación B2B sea eficiente y se ajuste a los objetivos estratégicos de la empresa.
+
+## Asociar una política comercial
+1. En el Admin VTEX, accede a **Apps > Organizaciones > Organizaciones y centros de costos B2B > Organizaciones** o escribe **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de Información de la organización.
+3. Haz clic en la pestaña **Política comercial**.
+4. Selecciona la política comercial que deseas asociar a la organización.
+5. Haz clic en `Guardar`.
+
diff --git a/docs/tutorials/es/bank-reconciliations.md b/docs/tutorials/es/bank-reconciliations.md
index e63f6c69e..14f4afc92 100644
--- a/docs/tutorials/es/bank-reconciliations.md
+++ b/docs/tutorials/es/bank-reconciliations.md
@@ -36,7 +36,7 @@ Después de recibir el archivo del banco y guardarlo en su máquina, conforme ci
 
 Luego que seleccione el archivo, la plataforma empezará a procesarlo y registrará en histórico cuántos pagos se conciliaron con éxito o error. Los pagos que se concilien con éxito actualizarán los status de los pedidos para Pago Aprobado.
 
-![upload-archivo-ret](https://images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7ee6df418b9638eaab055282675b9f6/uploadret_ES.JPG)
+![upload-archivo-ret](//images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7ee6df418b9638eaab055282675b9f6/uploadret_ES.JPG)
 
 ## Visualizar el histórico
 
@@ -48,7 +48,7 @@ De entre los detalles es posible saber el banco al cual el boleto pertenece, el
 2. En **Historial**, haga clic en una de las fechas de las operaciones de conciliación bancaria realizadas.
 3. En **Más detalles**, haga clic en **Conciliado Satisfactoriamente** o **No conciliados** para verificar los detalles de las transacciones realizadas en un banco en particular. 
 
-![historico-conciliacion](https://images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/3f2bc9203d264a3b45523211ea06ccb2/historico_conciliacao_ES.jpg)
+![historico-conciliacion](//images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/3f2bc9203d264a3b45523211ea06ccb2/historico_conciliacao_ES.jpg)
 
 ## Payclub
 
@@ -59,4 +59,4 @@ Aquí es posible hacer el download de los pagos del día que se han hecho a trav
 3. Seleccione la fecha que desee del calendario.
 4. Haga clic en **Descargar archivo**.
 
-![descarga-archivo-conciliación](https://images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/6c23d0bf478fdbf20d1176271a29840e/Download_Concilia____o_ES.JPG)
+![descarga-archivo-conciliación](//images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/6c23d0bf478fdbf20d1176271a29840e/Download_Concilia____o_ES.JPG)
diff --git a/docs/tutorials/es/banners.md b/docs/tutorials/es/banners.md
new file mode 100644
index 000000000..85bcb83b1
--- /dev/null
+++ b/docs/tutorials/es/banners.md
@@ -0,0 +1,68 @@
+---
+title: 'Banners'
+id: 72XytEoeqOAOiH05oVF0pH
+status: PUBLISHED
+createdAt: 2024-06-27T16:30:55.610Z
+updatedAt: 2024-06-27T16:31:52.889Z
+publishedAt: 2024-06-27T16:31:52.889Z
+firstPublishedAt: 2024-06-27T16:31:52.889Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: banners
+locale: es
+legacySlug: banners
+subcategory: z6qcw06Z38YDu1fOcu9Jn
+---
+
+Banners es la funcionalidad de Intelligent Search responsable de mostrar banners, como acciones promocionales, en la página de resultados de búsqueda del cliente. La exhibición de los banners se basa en el análisis del contexto de búsqueda, incluyendo los términos y filtros seleccionados, en la jornada de compra del cliente. También puedes configurar banners para cada una de las categorías existentes en tu catálogo, así como para los departamentos y las subcategorías.
+
+Con diferentes perfiles, cada grupo de clientes de tu tienda tiene sus propios intereses. Tus campañas de marketing deben tener esto en cuenta para que sean efectivas y puedan aumentar las tasas de conversión en ventas. La flexibilidad de configuración de los banners permite crear campañas de marketing más creativas, trabajando la relación de tu marca con el público de forma individualizada.
+
+Cabe destacar que esta configuración puede realizarse tanto por términos como por filtros utilizados durante la búsqueda. Si un cliente busca "zapatillas de correr", puede filtrar el resultado de la búsqueda por diferentes atributos ("talla", "tipo" y "marca"). Seleccionando el filtro "nike", si hay un banner de esa marca en la tienda, se puede mostrar al cliente (filtro).
+
+A partir de la captura del contexto realizada por Intelligent Search, el sistema selecciona qué contenido previamente registrado es el más relevante para el escenario.
+
+Por ejemplo, el cliente busca "zapatilla de correr" y, en el resultado de la búsqueda, puede filtrar por varios atributos ("talla", "tipo" y "marca"). Al seleccionar el filtro "Nike", si tiene una campaña de la marca en la tienda, esta se puede mostrar al cliente (filtro). El cliente también puede ser dirigido a una promoción más específica de zapatilla de correr Nike (término y filtro) si se ha creado una campaña y está relacionada con el banner.
+
+## Lista de Banners
+
+En VTEX Admin, la página **Storefront** > **Banners** muestra la lista completa de banners registrados y permite realizar las siguientes acciones:
+
+* [Crear banner](#crear-banner)
+* [Buscar banner](#buscar-banner)
+* [Editar banner](#editar-banner)
+* [Eliminar banner](#eliminar-banner) 
+
+![banners-intro-es](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
+
+La página contiene la siguiente información:
+
+| Columna         | Descripción                                                                   |
+| --------------- | ----------------------------------------------------------------------------- |
+| Nombre          | Nombre que identifica el banner, definido en la etapa [Crear banner](#crear-banner).           |
+| Posición        | Zona en la que aparecerá el banner en la página de resultados de la búsqueda. |
+| Fecha de inicio | Fecha en la que el banner comenzará a estar disponible.                       |
+| Fecha de fin    | Fecha en la que el banner dejará de estar disponible.                         |
+| Activo          | Opción que activa o desactiva un banner.                                      |
+| Acciones        | Acción para eliminar o editar un banner.                                      |
+
+## Crear banner
+
+Para configurar un banner, haga clic en `Nuevo`. Más información sobre toda la información necesaria para crear un Banner en [Configurar Banners](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
+
+## Buscar banner
+
+Para buscar un banner, escribe su nombre en la barra de búsqueda.
+
+## Editar banner
+
+Puedes editar la información de un banner siguiendo los pasos a continuación.
+
+1. Haz clic en el botón del lápiz <i class="fa-solid fa-pencil"></i>.
+2. Edita la información deseada del banner.
+3. Haz clic en `Guardar`.
+
+## Eliminar banner
+
+Puedes eliminar un banner haciendo clic en el botón de la papelera <i class="fa-solid fa-trash-can"></i>.
diff --git a/docs/tutorials/es/best-practices-against-virtual-attacks.md b/docs/tutorials/es/best-practices-against-virtual-attacks.md
index fd72a1fe8..fde43b901 100644
--- a/docs/tutorials/es/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/es/best-practices-against-virtual-attacks.md
@@ -3,8 +3,8 @@ title: 'Prácticas recomendadas para evitar ataques virtuales'
 id: 191rpbF7UgrKapVCi1PCDE
 status: PUBLISHED
 createdAt: 2022-04-06T19:04:13.387Z
-updatedAt: 2022-06-10T14:24:42.121Z
-publishedAt: 2022-06-10T14:24:42.121Z
+updatedAt: 2024-06-18T20:41:01.987Z
+publishedAt: 2024-06-18T20:41:01.987Z
 firstPublishedAt: 2022-04-06T19:23:22.326Z
 contentType: tutorial
 productTeam: Reliability
@@ -18,46 +18,55 @@ subcategory: 6uJgdHqWf1Mo0rUfgxseTn
 VTEX cuenta con varias protecciones contra posibles ataques a las tiendas. Sin embargo, existen configuraciones y productos de terceros que pueden mejorar la seguridad de tu operación. En este artículo, se describen algunos de esos recursos:
 
 - [Antifraude](#antifraude)
-- [Protección contra ataques en las transacciones](#proteccion-contra-ataques-en-las-transaciones)
-- [reCAPTCHA en el checkout](#recaptcha-en-el-checkout)
-- [Deshabilitar el inicio de sesión con contraseña](#deshabilitar-el-inicio-de-sesión-con-contrasena)
+- [Protección contra ataques a las transacciones](#proteccion-contra-ataques-a-las-transaciones)
+- [reCAPTCHA v3 en el checkout](#recaptcha-v3-en-el-checkout)
+- [Desactivar el inicio de sesión con contraseña](#desactivar-el-inicio-de-sesión-con-contrasena)
 
 <div class = "alert alert-info">
-Estas medidas no eliminan por completo la posibilidad de sufrir un ataque, pero sí pueden reducir bastante las probabilidades si se aplican adecuadamente.
+Las medidas mencionadas en esta guía no eliminan por completo la posibilidad de ataques, pero sí pueden disminuir las probabilidades de que ocurran si se aplican adecuadamente.
 </div>
 
 ## Antifraude
 
-El antifraude es un sistema que se especializa en el análisis de las compras realizadas en los sitios web de ecommerce con el objetivo de identificar operaciones fraudulentas. Este sistema analiza datos sobre el comportamiento de los compradores de un ecommerce e impide que se concreten compras sospechosas.
+Los sistemas de antifraude se especializan en analizar compras de tiendas online para identificar transacciones fraudulentas. También analizan los datos de comportamiento de los compradores con el fin de evitar compras sospechosas.
 
-Obtén más información sobre los [sistemas antifraude](https://help.vtex.com/es/tutorial/what-is-anti-fraud#) y su integración a la plataforma VTEX.
+Aprende más sobre [sistemas antifraude](https://help.vtex.com/es/tutorial/what-is-anti-fraud) y cómo utilizarlos en VTEX.
 
 <div class="alert alert-warning">
-Para más seguridad, configura la opción de antifraude en todos los métodos de pago disponibles en tu tienda.
+Para mayor seguridad, configura tu antifraude en todos los medios de pago disponibles en la tienda.
 </div>
 
-## Protección contra ataques en las transaciones
+## Protección contra ataques a las transaciones
+
+Para acceder a la documentación, ingrese su [nombre de cuenta](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) VTEX a continuación, haz clic en el botón e inicia sesión en el Admin.
 
-Para acceder a la documentación, ingrese su [nombre de cuenta](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) VTEX abajo, haga click en el botón y inicia sesión en el Admin.
 <iframe src="https://help.vtex.com/insertaccountname?id=62oQBmi7UZlYlgb0Ha1hZ3" title="Ingrese su nombre de cuenta y haga click en el botón." frameBorder="0" width="400" height="50"></iframe>
 
-## reCAPTCHA en el checkout
+## reCAPTCHA v3 en el checkout
+
+reCAPTCHA es una solución utilizada para la validación de usuarios reales en pedidos que se pagarán con tarjetas de crédito o débito y evita situaciones en que se utilizan programas maliciosos para cometer fraude.
 
-reCAPTCHA es una solución que se utiliza para la validación de usuarios reales en pedidos que se pagarán con tarjetas de crédito o débito. Prevé situaciones en que se utilizan programas maliciosos para cometer fraude.
+Recomendamos utilizar [reCAPTCHA v3](https://help.vtex.com/es/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-v3), ya que emplea una puntuación de calidad en vez de una validación por medio de una ventana emergente, lo que hace que sea más difícil de evadir en estos casos.
 
-Aquí obtendrás más información sobre cómo configurar esta validación en el checkout de tu tienda [reCAPTCHA en el checkout](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#).
+Aprende a configurar esta validación en el checkout de tu tienda en [reCAPTCHA en el checkout](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP). Para implementar reCAPTCHA v3 en una tienda VTEX, consulta la guía de desarrolladores [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
 
 <div class = "alert alert-info">
 La validación por reCAPTCHA también está activada de forma predeterminada en el flujo de <a href=tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes>registro de tarjetas</a> de los clientes de la tienda; por lo tanto, no es necesario que la tienda la configure.
 </div>
 
-## Deshabilitar el inicio de sesión con contraseña
+## Configuración de orderForm
+
+Para acceder a la documentación, ingrese su [nombre de cuenta](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) VTEX a continuación, haz clic en el botón e inicia sesión en el Admin.
+
+<iframe src="https://help.vtex.com/insertaccountname?id=7EAqNk48KP2QHnCxu856jT" title="Ingrese su nombre de cuenta y haga click en el botón." frameBorder="0" width="400" height="50"></iframe>
+
+## Desactivar el inicio de sesión con contraseña
 
-Si tu tienda sufre ataques a pesar de haberse aplicado los recursos que mencionamos anteriormente, te recomendamos deshabilitar el inicio de sesión con contraseña. Esta medida se puede aplicar de forma temporal o permanente, y tiene como objetivo poner fin al flujo de automatización del ataque.
+Si tu tienda sufre ataques incluso con la aplicación de los recursos mencionados anteriormente, recomendamos desactivar el inicio de sesión con contraseña. Esta medida puede aplicarse temporal o permanentemente con el fin de interrumpir el flujo de automatización del ataque.
 
-Para activar esta configuración:
-1. Ingresa a **Configuración de la cuenta** > **Autenticación**.
-2. Desactiva el campo **Contraseña**.
+Para realizar esta configuración:
 
-Obtén más información sobre cómo [gestionar las formas de autenticación](https://help.vtex.com/es/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs#).
+1. Accede a **Configuración de la cuenta** > **Autenticación**.
+2. En la pestaña __Tienda virtual__, desactiva el campo **Contraseña**.
 
+Aprende más sobre cómo [gestionar los métodos de autenticación](https://help.vtex.com/es/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) de tu tienda.
diff --git a/docs/tutorials/es/best-practices-application-keys.md b/docs/tutorials/es/best-practices-application-keys.md
index 0335170a2..fc9a6c9ab 100644
--- a/docs/tutorials/es/best-practices-application-keys.md
+++ b/docs/tutorials/es/best-practices-application-keys.md
@@ -1,9 +1,9 @@
 ---
 title: 'Buenas prácticas para el uso de claves de aplicación'
 id: 7b6nD1VMHa49aI5brlOvJm
-status: PUBLISHED
+status: CHANGED
 createdAt: 2022-10-04T21:36:57.185Z
-updatedAt: 2022-10-04T21:41:08.638Z
+updatedAt: 2024-03-19T14:22:43.610Z
 publishedAt: 2022-10-04T21:41:08.638Z
 firstPublishedAt: 2022-10-04T21:41:08.638Z
 contentType: tutorial
@@ -22,6 +22,7 @@ Este tipo de credencial se utiliza para la autenticación de la identidad a trav
 </div>
 
 El manejo inadecuado de las [claves de aplicación](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) puede generar fugas y, en consecuencia, situaciones de acceso indebido. A continuación, puedes ver las buenas prácticas que recomendamos para la gestión de estas credenciales que puedes implementar para aumentar la seguridad de tu tienda.
+
 ## Rotar las claves periódicamente
 
 Es aconsejable que desactives las claves antiguas y crees claves nuevas a lo largo del tiempo. De esta forma te aseguras de que tus [claves de aplicación](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) tengan una duración determinada.
diff --git a/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md b/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md
new file mode 100644
index 000000000..392cac69d
--- /dev/null
+++ b/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md
@@ -0,0 +1,73 @@
+---
+title: 'Mejores prácticas para acceder a tienda sin www'
+id: tutorials_4278
+status: PUBLISHED
+createdAt: 2017-04-27T21:51:11.002Z
+updatedAt: 2024-01-23T17:50:54.783Z
+publishedAt: 2024-01-23T17:50:54.783Z
+firstPublishedAt: 2017-04-27T23:11:15.960Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: mejores-practicas-para-acceder-a-tienda-sin-www
+locale: es
+legacySlug: configurando-acceso-sin-www
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+El dominio principal de la tienda debe contar con un subdominio, como `www` u otro. Para acceder a la tienda mediante un dominio puro (por ejemplo, `mitienda.com`, sin subdominio), se requiere realizar una redirección. En esta guía, explicamos las razones detrás de esta necesidad y proporcionamos instrucciones detalladas sobre cómo llevar a cabo la redirección. Consulta las secciones a continuación:
+
+* [Antes de empezar](#antes-de-empezar)
+* [Dificultades de los dominios sin subdominios](#dificultades-de-los-dominios-sin-subdominios)
+* [Solución recomendada: redirección](#solucion-recomendada-redireccion)
+* [Solución alternativa: CNAME Flattening](#solucion-alternativa-cname-flattening)
+
+## Antes de empezar
+
+Recomendamos leer las siguientes guías para entender cómo funcionan los dominios y la configuración de DNS en VTEX:
+
+* [Configurar dominio de la tienda](https://help.vtex.com/es/tutorial/configurar-dominio-de-la-tienda--tutorials_2450)
+* [Cómo funciona la configuración de DNS en VTEX](https://help.vtex.com/es/tutorial/como-funciona-la-configuracion-de-dns-en-vtex--2P5k3oMYOj7TgSK4Mrxmgy)
+
+## Limitaciones en la configuración de DNS para dominios puros
+
+Esta sección explora la complejidad y las dificultades relacionadas con la configuración del sistema de DNS para dominios puros. La gestión de dominios sin subdominios requiere una atención especial, sobre todo para preservar la funcionalidad y la integridad del sitio web, sin comprometer elementos cruciales como emails, seguridad y certificados.
+
+### Redirecciones de tipo A para dominios puros 
+
+La configuración de DNS en VTEX debe hacerse para el dominio principal de la tienda, y no se recomienda el uso de dominios puros. Un dominio puro, sin subdominio, también conocido como naked domain (por ejemplo, `mitienda.com`, sin `www`), implica la creación de una configuración de tipo A (Address Record) en el DNS. El registro A se utiliza para apuntar directamente el dominio a una dirección IP específica.
+
+Sin embargo, no se recomienda este tipo de configuración. No es posible utilizar configuraciones A que apunten directamente a una dirección IP, por las siguientes razones:
+
+* **Riesgo de sitio web inaccesible:** Si un dominio puro está configurado con un registro A que apunta a una dirección IP específica y esa dirección IP cambia, el sitio puede volverse inaccesible hasta que se actualice la nueva IP en el registro A.
+* **Rendimiento limitado:** si el dominio puro apunta directamente a una única dirección IP, todos los visitantes que accedan al sitio web, sin importar su ubicación, se ven obligados a conectarse a ese servidor. Esto podría provocar una degradación del rendimiento, ya que los visitantes ubicados a mayor distancia tendrían una experiencia más lenta.
+
+### Redirecciones CNAME para dominios puros
+
+Deben evitarse las redirecciones CNAME para dominios puros. Un registro CNAME se comporta como una redirección en el contexto de DNS: cuando alguien accede a `www.mitienda.com`, el DNS redirige automáticamente a `www.mitienda.com.cdn.vtex.com`. Sin embargo, según las reglas del protocolo DNS, un registro CNAME no puede coexistir con otras configuraciones de DNS en el mismo dominio. Esto significa que si utilizamos un registro CNAME para redirigir un sitio web, todas las configuraciones de ese sitio deben seguir esa redirección. No es posible redirigir solamente una parte de las configuraciones realizadas. 
+
+Este comportamiento entra en conflicto directo con los dominios puros, ya que los retailers a menudo desean configurar otras funcionalidades, como registros MX para emails, registros TXT para seguridad, registros CAA para certificados y registros NS y SOA para demostrar que controlan el dominio puro.
+
+## Dominios puros
+
+Dadas las restricciones en la configuración de DNS para dominios puros, esta sección aborda las mejores prácticas para garantizar el acceso a la tienda sin requerir el prefijo www.
+
+### Solución recomendada: redirección
+
+Al [configurar el dominio principal](https://help.vtex.com/es/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450) de la tienda, VTEX recomienda utilizar siempre `www` u otro subdominio, para integrar la necesidad de utilizar CNAME junto a otras configuraciones. En este escenario, se recomienda utilizar redirecciones para acceder a la dirección web sin `www` u otros subdominios. Para saber cómo configurar redirecciones, consulta [Redirección de otras direcciones](https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ).
+
+Si bien algunos proveedores de DNS soportan registros CNAME en el dominio puro ([CNAME Flattening](#solucion-alternativa-cname-flattening)), es posible que no todos ofrezcan esta opción, por lo que recomendamos el uso obligatorio de un subdominio para garantizar la coexistencia de todas las funcionalidades necesarias.
+
+### Solución alternativa: CNAME Flattening
+
+VTEX recomienda, como opción predeterminada, utilizar un subdominio `www` para evitar problemas relacionados con la dinamicidad de las IP en la CDN. Sin embargo, algunas empresas proveedoras de hosting y servicios de DNS ofrecen una solución alternativa para resolver este problema, denominada [CNAME Flattening](https://developers.cloudflare.com/dns/cname-flattening/).
+
+CNAME Flattening es una técnica que permite asociar un dominio puro directamente con un registro CNAME, en lugar de con un registro A. De esta manera, es posible configurar un dominio puro (sin subdominio) para que funcione con una CDN, incluso cuando haya cambios en las direcciones IP. Sin embargo, esta funcionalidad no es compatible con todos los proveedores de DNS.
+
+Algunos proveedores de DNS, como [Cloudflare](https://www.cloudflare.com/pt-br/), ofrecen soporte para CNAME Flattening. En este caso, se puede configurar el dominio puro con un CNAME que apunte al servicio de CDN de VTEX. Esto permite que el dominio puro funcione de manera parecida al subdominio `www` y además se beneficie de la CDN.
+
+Por lo tanto, si deseas utilizar un dominio puro con una CDN en una configuración específica, la primera etapa es comprobar si tu proveedor de DNS soporta CNAME Flattening. En caso afirmativo, puedes configurar el dominio puro de esa manera.
+
+<div class="alert alert-warning">
+  <p>Cuando se utiliza la solución DNS Flattening, se comportará de la misma forma que un <a href="https://help.vtex.com/es/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir">proxy inverso</a>. En este caso, se debe configurar una entrada de verificación TXT.</p>
+</div>
diff --git a/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md b/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md
new file mode 100644
index 000000000..6bd5cf3da
--- /dev/null
+++ b/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md
@@ -0,0 +1,171 @@
+---
+title: 'Mejores prácticas para el éxito de tu tienda VTEX'
+id: ItKyLqcRl9wNADMhYH8O4
+status: PUBLISHED
+createdAt: 2024-05-24T21:33:12.690Z
+updatedAt: 2024-05-24T22:42:51.899Z
+publishedAt: 2024-05-24T22:42:51.899Z
+firstPublishedAt: 2024-05-24T22:42:51.899Z
+contentType: tutorial
+productTeam: Others
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: mejores-practicas-para-el-exito-de-tu-tienda-vtex
+locale: es
+legacySlug: mejores-practicas-para-el-exito-de-tu-tienda-vtex
+subcategory: 4PeX73EGpmULh9Ip5F4XER
+---
+
+Este artículo presenta algunas de las principales prácticas para que gestiones tu tienda VTEX con eficiencia y facilidad, además de promover la escalabilidad de tu operación. El contenido está organizado de la siguiente manera:
+
+* **[Desempeño y seguridad](#desempeno-y-seguridad)**
+    * [Mantén la arquitectura de tu tienda documentada](#manten-la-arquitectura-de-tu-tienda-documentada)
+    * [Sigue las directrices de seguridad](#sigue-las-directrices-de-seguridad)
+    * [Controla el nivel de acceso de los permisos](#controla-el-nivel-de-acceso-de-los-permisos)
+    * [Conoce nuestros partners y marketplaces certificados](#conoce-nuestros-partners-y-marketplaces-certificados)
+* **[Actualizaciones y noticias](#actualizaciones-y-noticias)**
+    * [Sigue nuestros lanzamientos y noticias](#sigue-nuestros-lanzamientos-y-noticias)
+    * [Recibe notificaciones de status de la plataforma](#recibe-notificaciones-de-status-de-la-plataforma)
+    * [Conoce nuestros contenidos de onboarding](#conoce-nuestros-contenidos-de-onboarding)
+* **[Comunidad y soporte](#comunidad-y-soporte)**
+    * [Participa en VTEX Community](#participa-en-vtex-community)
+    * [Conoce las mejores prácticas en tickets de soporte VTEX](#conoce-las-mejores-practicas-en-tickets-de-soporte-vtex)
+
+<div class = "alert alert-info">
+<b>Agencias partners</b><p>Existen varias agencias y partners de implementación que han sido certificados por VTEX debido a su demostrada excelencia y fiabilidad en proyectos realizados con la plataforma. Por lo tanto, ya sea para una implementación eficiente, una arquitectura de tienda personalizada o para obtener apoyo continuo en infraestructura, recomendamos contratar agencias partners. Para conocer a nuestros partners, accede al <a href="https://partnerportal.vtex.com/parceiros">Partner Portal</a> (solamente en portugués) o a <a href="http://vtex.com">vtex.com</a> (otros idiomas).</p>
+</div>
+
+## Desempeño y seguridad
+
+En esta sección te presentamos las mejores prácticas para promover la eficiencia y la seguridad de tu operación.
+
+### Mantén la arquitectura de tu tienda documentada
+
+Una operación de ecommerce suele implicar la integración de diferentes sistemas y tecnologías. Mantener actualizada la documentación de la [arquitectura de la tienda](https://help.vtex.com/es/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitetura-da-loja) es estratégico para garantizar el mejor desempeño de la estructura y de los profesionales implicados.
+
+Los principales beneficios de elaborar y mantener actualizada la documentación de la arquitectura de tu operación son:
+
+* **Eficiencia en la implementación y el mantenimiento:** la fase inicial del desarrollo de la tienda es más rápida y el mantenimiento de la operación se realiza de manera más fácil. Mantener una documentación de la arquitectura disminuye la necesidad de depender de profesionales con contexto previo y optimiza la colaboración entre las partes involucradas.
+* **Facilidad de evolución:** la documentación de la arquitectura de la tienda disminuye las dificultades al realizar cambios, lo que impulsa la capacidad de innovación de tu empresa.
+* **Decisiones fundamentadas:** entender el funcionamiento de la tienda permite a los líderes ejecutivos tomar decisiones fundamentadas sobre la infraestructura.
+* **Actuación rápida en problemas de seguridad:** solucionar problemas de seguridad o vulnerabilidades es más rápido cuando se comparte la documentación de la arquitectura.
+* **Optimización del soporte:** cuando se requiere asistencia de nuestro equipo de soporte o de terceros, compartir la documentación de la arquitectura agiliza la comunicación entre las partes y aumenta la eficiencia de su actuación.
+
+<div class = "alert alert-info">
+Para documentar la arquitectura de la tienda, visita la página <a href="https://developers.vtex.com/docs/guides">Get started</a> en nuestro portal para desarrolladores y explora el <a href="https://assets.vtex.com/4524045/">framework interactivo</a> de la plataforma VTEX.
+</div>
+
+### Sigue las directrices de seguridad
+
+Existen estrategias para prevenir y reducir la exposición de tu tienda al riesgo de ataques maliciosos. Algunas de las principales son:
+
+* **Antifraude:** configura un sistema [antifraude](https://help.vtex.com/es/tutorial/what-is-anti-fraud) para todos los medios de pago de tu tienda.  
+* **reCAPTCHA:** utiliza [reCAPTCHA](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#) para prevenir fraudes con falsos usuarios creados por programas maliciosos.
+* **Autenticación:** si tu tienda está experimentando ataques recurrentes, considera desactivar el inicio de sesión mediante contraseña y opta por otro método de [autenticación](https://help.vtex.com/es/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) para los clientes de tu tienda.
+
+<div class = "alert alert-info">
+Para más información sobre acciones preventivas, consulta el artículo <a href="https://help.vtex.com/es/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE">Prácticas recomendadas para evitar ataques virtuales</a> y este <a href="https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470">post</a> (disponible en portugués) en VTEX Community.
+</div>
+
+### Controla el nivel de acceso de los permisos
+
+Respecto a la [seguridad de las tiendas VTEX](https://help.vtex.com/es/subcategory/seguranca-para-lojistas--6uJgdHqWf1Mo0rUfgxseTn), existen medidas preventivas y [mejores prácticas](https://help.vtex.com/es/tutorial/boas-praticas-para-evitar-golpes-que-utilizam-a-marca-da-vtex--6uPwUr2Fnj2m3TM4hAj2Ec) que aumentan el nivel de seguridad de tu negocio. Una de las principales es la gestión de roles en tu Admin VTEX. 
+
+Consulta a continuación algunas de las recomendaciones más importantes sobre [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) en VTEX:
+
+* **Concede el nivel mínimo de permiso necesario:** crea roles de manera que el acceso a la información y configuraciones sea únicamente el requerido para llevar a cabo la actividad prevista. Además de los [roles predeterminados](https://help.vtex.com/es/tutorial/perfis-de-acesso), también puedes crear [roles personalizados](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso). Reducir el nivel de permisos de terceros a contenidos críticos implica disminuir tu exposición al riesgo de accesos no deseados, fugas de datos u otros escenarios perjudiciales. 
+* **Reevalúa roles:** [gestiona los usuarios](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) de manera periódica y mantén actualizado el nivel de permiso adecuado de cada usuario. Es esencial eliminar roles de empleados o proveedores que ya no participan en tu negocio. Realizar revisiones periódicas y proactivas de usuarios ayuda a prevenir violaciones de seguridad causadas por accesos indebidos.
+* **Controla el permiso de las claves de aplicación:** el acceso a tu tienda VTEX también puede realizarse mediante [claves de aplicación](https://help.vtex.com/es/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) utilizadas en integraciones. Es importante seguir nuestras recomendaciones de [Mejores prácticas para el uso de claves de aplicación](https://help.vtex.com/es/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm).
+* **Restringe el acceso al Admin VTEX a dominios corporativos:** al utilizar un dominio corporativo, se crea una barrera adicional que impide que personas y sistemas no autorizados accedan a tu tienda. Limitar el acceso solamente a emails corporativos ayuda a mitigar el riesgo de fugas de datos (intencionadas o accidentales), aumenta la protección contra el phishing y facilita la trazabilidad de las actividades de auditoría.
+* **Activa la autenticación de 2 factores:** con la [autenticación de 2 factores (2FA)](https://help.vtex.com/es/tutorial/habilitar-login-por-autenticacao-de-2-fatores--4Ae1fcQi12g8u4SkQKCqWQ) agregas una capa extra de seguridad a tu operación y proteges el acceso a tu tienda en caso de que la confidencialidad de tu contraseña se vea comprometida. Activar esta autenticación es aún más importante para los usuarios con acceso a información y configuraciones de niveles críticos.
+
+### Conoce nuestros partners y marketplaces certificados
+
+La arquitectura de la plataforma VTEX permite que las tiendas actúen simultáneamente como [marketplaces o como sellers](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402), y la página [Marketplaces e integraciones](https://help.vtex.com/es/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V) facilita el descubrimiento y la comunicación entre marketplaces y sellers VTEX. Además, VTEX ofrece integraciones nativas con varios [marketplaces certificados](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-certificado) y [partners](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-partner) (como Amazon y Mercado Libre).
+
+Si deseas desarrollar una integración con un marketplace externo, consulta el artículo [External Marketplace](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide).
+
+## Actualizaciones y noticias
+
+En esta sección te presentamos las mejores prácticas para dar seguimiento al status de la plataforma y a las innovaciones en los productos VTEX.
+
+### Sigue nuestros lanzamientos y noticias
+
+La plataforma VTEX está en constante evolución, y una excelente forma para que tanto tú como tu equipo se mantengan informados sobre los lanzamientos es consultando nuestros portales de documentación, que se detallan a continuación:
+
+| **Portal de documentación** | **Cómo acceder** |
+| :---: | :---: |
+| Help Center | Página: [Noticias](https://help.vtex.com/es/announcements) |
+| Developer Portal | Página: [Release Notes](https://developers.vtex.com/updates/release-notes) |
+
+Algunos de los principales beneficios de mantenerse informado son:
+
+* Al mantener tus operaciones alineadas con los últimos lanzamientos, aprovechas al máximo el potencial de la plataforma y conservas tu ventaja competitiva en el mercado.
+* Conocer el funcionamiento de los nuevos recursos, lo que garantiza una implementación más ágil.
+* Al configurar las actualizaciones, aumentas la seguridad de tu tienda, ya que estamos constantemente innovando para proteger tu negocio.
+* Si necesitas contactar al equipo de soporte, comprender el funcionamiento de las nuevas funciones te permitirá interactuar de manera más eficaz con ellos, lo que resultará en resoluciones más rápidas.
+
+<div class = "alert alert-info">
+Los anuncios de la página <b>Noticias</b> del Help Center también están disponibles a través de tu Admin VTEX. Para acceder al contenido, basta con hacer clic en el ícono de campana situado en la parte superior de la página.
+</div>
+
+### Recibe notificaciones de status de la plataforma
+
+Cuando se produce un incidente en la plataforma, VTEX se esfuerza por actuar de la forma más transparente e informativa posible. 
+
+Por este motivo, VTEX pone a disposición la página [VTEX Status](https://status.vtex.com/). Además de monitorear la estabilidad de la plataforma en tiempo real, el contenido de la página te permite conocer cuándo hay mantenimientos programados. Puedes inscribirte para recibir notificaciones de la página vía:
+
+* Email
+* [Feed RSS](https://rss.com/blog/how-do-rss-feeds-work/)
+* [Slack](https://slack.com/)
+
+<div class = "alert alert-info">
+Para comprender los detalles de la página de status de la plataforma, accede al artículo <a href="https://help.vtex.com/es/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ">Página VTEX Status</a>.
+</div>
+
+### Conoce nuestros contenidos de onboarding
+
+VTEX ofrece una amplia gama de funcionalidades y productos, y es importante conocerlos para identificar los recursos que mejor se adaptan al perfil de tu negocio.
+
+Por este motivo, ofrecemos una serie de contenidos de onboarding sobre la plataforma, que puedes consultar a continuación:
+
+| **Formato** | **Cómo acceder** | **Idioma** |
+| :---: | :--- | :--- |
+| Documentación | Help Center: [Guía de onboarding](https://help.vtex.com/es/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | Español, portugués e inglés. |
+| Videos | Sitio web: [Onboarding VTEX](https://sites.google.com/vtex.com.br/onboardingvtex/trilha) | Solamente disponible en portugués. |
+| Demos e ebooks | Sitio web: [vtex.com](https://vtex.com/co-es/resources) | Cada contenido está disponible en español, inglés o portugués, dependiendo de tu ubicación. |
+
+## Comunidad y soporte
+
+En esta sección te presentamos las mejores prácticas para optimizar tu red de apoyo en el ecosistema VTEX.
+
+### Participa en VTEX Community
+
+[VTEX Community](https://community.vtex.com/) es un espacio accesible al público en general, donde nuestros especialistas, clientes, partners de implementación y todo el ecosistema VTEX comparten conocimientos y se apoyan mutuamente. 
+
+El enfoque colaborativo de nuestra comunidad es una importante fuente de soporte en VTEX, y algunas de sus principales ventajas son:
+
+* **Velocidad de respuesta:** VTEX Community está activa las 24 horas del día, todos los días de la semana, y cuenta con la participación de miembros diferentes países. Cuando planteas una pregunta, puede ser respondida en cualquier momento. Además de los especialistas de VTEX, otras personas que hayan experimentado situaciones similares pueden ofrecerte apoyo y compartir su conocimiento.
+* **Perspectivas diversas:** al interactuar con diferentes miembros de la comunidad, se obtienen distintos puntos de vista y enfoques para resolver problemas. Esta diversidad de experiencias suele dar lugar a soluciones innovadoras.
+* **Compartir información:** nuestra comunidad se ha convertido en una especie de biblioteca virtual donde puedes encontrar consejos, sugerencias de buenas prácticas y mucho contenido práctico para operar tu tienda VTEX de la mejor manera.
+* **Contactos profesionales y comerciales:** una presencia activa en la comunidad contribuye al desarrollo de tu red profesional.
+
+### Conoce las mejores prácticas en tickets de soporte VTEX
+
+Existen algunos casos en los que se requiere soporte a través de la apertura de tickets. Por ejemplo, situaciones que impliquen información confidencial o escenarios urgentes. 
+
+Nuestros especialistas están preparados para resolver tu consulta y brindarte una excelente experiencia durante todo el proceso, pero tu colaboración puede contribuir a que el soporte funcione de la manera más rápida y eficaz posible. 
+
+Existen [Buenas prácticas para abrir un ticket con el soporte VTEX](https://help.vtex.com/es/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX), con el fin de recibir una atención más rápida y objetiva. Algunas de las principales son:
+
+* Proporcionar información detallada sobre el motivo de la apertura del ticket.
+* Describir la situación o el problema de forma clara, precisa y objetiva (especialmente en el caso de problemas urgentes).
+* Mantener una comunicación clara y proactiva durante todo el proceso.
+* Cuando sea posible, adjuntar capturas de pantalla e incluir los registros (logs) relevantes.
+* Cuando sea posible, proporcionar instrucciones sobre cómo reproducir situaciones de error y problemas.
+
+Estas recomendaciones son algunas de las más importantes. Para más información, consulta el artículo [Buenas prácticas para abrir un ticket con el soporte VTEX](https://help.vtex.com/es/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX).
+
+<div class = "alert alert-info">
+Para una visión general de nuestro soporte vía tickets, consulta la serie <a href="https://help.vtex.com/es/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">Soporte VTEX</a>, presente en la <b>Guía de onboarding</b>.
+</div>
+
diff --git a/docs/tutorials/es/best-practices-for-using-images-in-the-catalog.md b/docs/tutorials/es/best-practices-for-using-images-in-the-catalog.md
index abbf04581..930b5dce5 100644
--- a/docs/tutorials/es/best-practices-for-using-images-in-the-catalog.md
+++ b/docs/tutorials/es/best-practices-for-using-images-in-the-catalog.md
@@ -3,8 +3,8 @@ title: 'Buenas prácticas para el uso de imágenes en el Catálogo'
 id: 738K2yfq5U86kUI2k4AQIk
 status: PUBLISHED
 createdAt: 2018-01-30T14:45:53.934Z
-updatedAt: 2022-07-07T15:32:57.069Z
-publishedAt: 2022-07-07T15:32:57.069Z
+updatedAt: 2024-01-23T15:54:22.159Z
+publishedAt: 2024-01-23T15:54:22.159Z
 firstPublishedAt: 2018-01-31T18:36:10.087Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/es/best-practices-on-spf.md b/docs/tutorials/es/best-practices-on-spf.md
index 60fbedb4c..803f5247b 100644
--- a/docs/tutorials/es/best-practices-on-spf.md
+++ b/docs/tutorials/es/best-practices-on-spf.md
@@ -3,8 +3,8 @@ title: 'Buenas prácticas de SPF (Sender Policy Framework)'
 id: 42t0lkl2VyC6Yewc4wA6wI
 status: PUBLISHED
 createdAt: 2017-08-09T16:58:00.716Z
-updatedAt: 2023-03-10T18:49:18.935Z
-publishedAt: 2023-03-10T18:49:18.935Z
+updatedAt: 2024-02-22T18:11:49.023Z
+publishedAt: 2024-02-22T18:11:49.023Z
 firstPublishedAt: 2017-08-10T00:04:19.239Z
 contentType: tutorial
 productTeam: Reliability
@@ -25,13 +25,13 @@ Para conocer más detalles de la sintaxis, recomendamos [esta documentación](ht
 
 En el gestor de DNS, el SPF será una entrada TXT en la raíz del dominio (ej.: sitio.com), con el siguiente formato:
 
-`site.com. IN TXT “v=spf1 a mx ip4:192.0.2.32/27 include:provedor.com -all”`
+`site.com. IN TXT “v=spf1 a mx ip4:192.0.2.32/27 include:provedor.com ~all”`
 
 Podemos dividir la anterior política en las siguientes secciones:
 
 - `v=spf1`: prefijo obligatorio.
 - `a mx ip4: 192.0.2.32/27 include:proveedor.com`: remitentes permitidos.
-- `-all`: condición de inclusión o exclusión de remitentes fuera de los declarados anteriormente.
+- `~all`: condición de inclusión o exclusión de remitentes fuera de los declarados anteriormente.
 
 En el elemento de remitentes permitidos, las reglas mencionadas implican que un servidor puede enviar mensajes en nombre del dominio en cuestión (site.com) cuando:
 
@@ -44,10 +44,10 @@ La condición de inclusión o exclusión puede presentar los siguientes valores:
 
 - `+all`: se permitirá cualquier remitente fuera de los declarados.
 - `-all`: se rechazará cualquier remitente fuera de los declarados.
-- `~all`: se necesitará otra etapa de verificación para rechazar a los remitentes no autorizados.
+- `~all`: se necesitará otra etapa de verificación para rechazar a los remitentes no autorizados. (Recomendado)
 - `?all`: se omitirá la verificación de los remitentes no autorizados.  
 
-Recomendamos la utilización de -all, que tiene una mejor tasa de entregabilidad. Sin embargo, debe asegurarse de que todos los dominios que envían mensajes en su nombre están correctamente configurados, de lo contrario los mensajes no se entregarán.   
+Recomendamos utilizar `~all`, que tiene un mejor índice de entregabilidad. Si hay un remitente no autorizado, esta opción no detiene el envío del correo, sino que informa de que la validación SPF ha fallado.
 
 ## SPF en el contexto VTEX
 
diff --git a/docs/tutorials/es/best-practices-to-avoid-scams-using-the-vtex-brand.md b/docs/tutorials/es/best-practices-to-avoid-scams-using-the-vtex-brand.md
new file mode 100644
index 000000000..2ec5326da
--- /dev/null
+++ b/docs/tutorials/es/best-practices-to-avoid-scams-using-the-vtex-brand.md
@@ -0,0 +1,53 @@
+---
+title: 'Buenas prácticas de prevención de fraudes que utilizan la marca VTEX'
+id: 6uPwUr2Fnj2m3TM4hAj2Ec
+status: PUBLISHED
+createdAt: 2024-03-19T14:09:14.448Z
+updatedAt: 2024-03-19T14:21:08.209Z
+publishedAt: 2024-03-19T14:21:08.209Z
+firstPublishedAt: 2024-03-19T14:21:08.209Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: buenas-practicas-de-prevencion-de-fraudes-que-utilizan-la-marca-vtex
+locale: es
+legacySlug: buenas-practicas-de-prevencion-de-fraudes-que-utilizan-la-marca-vtex
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+Como retailer, es fundamental ser consciente de la existencia de estafadores que pueden utilizar la marca VTEX de forma fraudulenta. En este artículo, compartiremos algunas recomendaciones para ayudarte a identificar y evitar fraudes.
+
+Proteger tu tienda contra prácticas fraudulentas que utilizan la marca VTEX requiere una vigilancia y precaución constantes. Siguiendo las directrices de esta guía y permaneciendo alerta ante posibles amenazas estarás contribuyendo a la seguridad e integridad de tu negocio online.
+
+## Verificar la autenticidad de la comunicación
+
+Por lo general, VTEX se comunica con sus clientes a través de canales oficiales:
+
+* Mensajes en el Admin VTEX
+* Emails corporativos
+* Comunicados en el [Help Center](https://help.vtex.com/es/) o en el [Developer Portal](https://developers.vtex.com/)
+* Publicaciones en el [sitio web](https://vtex.com/mx-es/) o en las redes sociales oficiales de VTEX
+
+Desconfía de cualquier comunicación que solicite información confidencial o acciones sospechosas, especialmente si procede de fuentes no verificadas.
+
+Es habitual que los estafadores intenten persuadirte para que actúes de inmediato, mencionando plazos cortos o posibles riesgos. Por lo tanto, mantén la calma y reflexiona antes de hacer clic o proporcionar cualquier información. 
+
+## Proteger credenciales de inicio de sesión
+
+Guarda las [claves de aplicación](https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet), los [tokens de usuario](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) y las [credenciales de inicio de sesión](https://help.vtex.com/es/tutorial/autenticacion--21CkKHLKP1o41lUpGhuRUs#login) en VTEX, como email, contraseña y códigos de acceso. Nunca compartas con terceros datos personales y confidenciales, información de la tienda, códigos u otra información sensible.
+
+Los estafadores pueden intentar acceder a tu cuenta para realizar actividades fraudulentas en nombre de tu empresa. Antes de actuar o facilitar cualquier información, confirma que es realmente VTEX quien se está comunicando contigo.
+
+## Identificar ofertas engañosas
+
+Si recibes ofertas en nombre de VTEX que afirman ser parte de programas de incentivos, no sigas las instrucciones del remitente. VTEX no ofrece un programa de incentivos y no solicita pagos a particulares o empresas al margen del contrato de servicios de la plataforma.
+
+Comprueba siempre la URL de destino antes de hacer clic en un link o acceder a una página y confirma que se trata de uno de los [canales de comunicación oficiales](#verificar-la-autenticidad-de-la-comunicacion) de VTEX. En caso de dudas, ponte en contacto con nuestro equipo de [soporte](https://help.vtex.com/support?/cultureInfo=es-419). 
+
+## Consulta los recursos de seguridad de VTEX
+
+VTEX ofrece recursos de seguridad y directrices para ayudar a sus clientes a proteger sus tiendas online contra fraudes y estafas. Familiarízate con estos recursos y utilízalos para reforzar la seguridad de tu tienda. Puedes consultar más información sobre nuestras prácticas de seguridad en [Seguridad - VTEX](https://vtex.com/es-es/security/).
+
+## Reportar actividades sospechosas
+
+Si sospechas de actividades fraudulentas utilizando la marca VTEX, repórtalo inmediatamente al equipo de [soporte](https://help.vtex.com/support?/cultureInfo=es-419). A continuación, el equipo de seguridad de VTEX investigará la situación y tomará las medidas necesarias para prevenir y combatir posibles fraudes.
diff --git a/docs/tutorials/es/beta-price-configuration.md b/docs/tutorials/es/beta-price-configuration.md
index c61b9b402..55a96bf88 100644
--- a/docs/tutorials/es/beta-price-configuration.md
+++ b/docs/tutorials/es/beta-price-configuration.md
@@ -72,11 +72,11 @@ Para crear una nueva regla, siga los pasos a continuación:
 
   b. **Activar en condiciones específicas:** la tabla de precios se activará según las condiciones configuradas en la regla. Vea las alternativas de configuración en las siguientes imágenes: 
 
-  ![config-preco-ES](https://images.ctfassets.net/alneenqid6w5/yNbbBH6crnGlgSflYJOuI/443a122a3b4909c114898816ae27e9b8/config-preco-ES.png)
+  ![config-preco-ES](//images.ctfassets.net/alneenqid6w5/yNbbBH6crnGlgSflYJOuI/443a122a3b4909c114898816ae27e9b8/config-preco-ES.png)
 
-  ![config-preco2-ES](https://images.ctfassets.net/alneenqid6w5/4TUUMNundZb1RjgBDKHNUn/4b279c50a93f6911b705e83b3970f2c2/config-preco2-ES.png)
+  ![config-preco2-ES](//images.ctfassets.net/alneenqid6w5/4TUUMNundZb1RjgBDKHNUn/4b279c50a93f6911b705e83b3970f2c2/config-preco2-ES.png)
 
-  ![config-preco3-ES](https://images.ctfassets.net/alneenqid6w5/1MUMEqGPxoW6XBr6Yfp9L1/52b2a01a72eef3cb0caa6881dff491ac/config-preco3-ES.png)
+  ![config-preco3-ES](//images.ctfassets.net/alneenqid6w5/1MUMEqGPxoW6XBr6Yfp9L1/52b2a01a72eef3cb0caa6881dff491ac/config-preco3-ES.png)
 
 7. Haga clic en **Confirmar**. 
 
diff --git a/docs/tutorials/es/billing-module-overview.md b/docs/tutorials/es/billing-module-overview.md
index 5d6426a91..0db8b4846 100644
--- a/docs/tutorials/es/billing-module-overview.md
+++ b/docs/tutorials/es/billing-module-overview.md
@@ -23,7 +23,7 @@ Para acceder a esta sección, haz clic en tu **avatar de perfil**, que se puede
 Solo los usuarios con perfil de acceso <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> o con recursos de <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> vinculadas a su Perfil de acceso tendrán acceso a esta sección del VTEX Admin.         
 </div>            
 
-![Admin v4 Faturas menu ES](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/369081b189fa73fa6f87aa849e21ec58/Admin_v4_Faturas_menu_ES.jpg)
+![Admin v4 Faturas menu ES](//images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/369081b189fa73fa6f87aa849e21ec58/Admin_v4_Faturas_menu_ES.jpg)
 
 A continuación encontrarás más detalles sobre las diferentes secciones y páginas de esta funcionalidad.
 
diff --git a/docs/tutorials/es/brands.md b/docs/tutorials/es/brands.md
index d6b7efadc..b93e4e9a2 100644
--- a/docs/tutorials/es/brands.md
+++ b/docs/tutorials/es/brands.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 La página **Marcas** te permite ver, gestionar y registrar marcas en Seller Portal. Puedes acceder a la página en el Admin VTEX en **Catálogo** > **Marcas**.
 
-![brands-es](https://images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/b663576009bbc4719d4091ba8ef46b5d/brands-es.PNG)
+![brands-es](//images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/b663576009bbc4719d4091ba8ef46b5d/brands-es.PNG)
 
 ## Crear marcas 
 Para registrar una nueva marca, haz clic en el botón `Crear marca`. Mira a continuación cómo rellenar los campos en la pantalla __Nueva marca__.
diff --git a/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md b/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md
index cc05ca15d..bd712adee 100644
--- a/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md
+++ b/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md
@@ -25,13 +25,13 @@ Navegue hasta el proyecto y abra el archivo `pages.json`.
 
 Añadimos el `"admin/"` al nombre de la página, así como a la ruta. Es importante también añadir `"admin/"` al principio del nombre de todas las extensiones que se utilizarán. Su `pages.json` debe quedar así:
 
-![2 pages](https://images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
+![2 pages](//images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
 
 ## Actualizar las dependencias para usar vtex.admin
 
 Ahora necesitamos actualizar el archivo manifest.json para listar el `vtex.admin` como dependencia. Recuerde que en VTEX IO siempre especificamos la versión que se utilizará. El manifest.json debe quedar así:
 
-![3 manifest](https://images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
+![3 manifest](//images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
 
 ## Los toques finales
 
@@ -43,5 +43,5 @@ Utilizaremos el `componentDidMount()` para comprobar que la string se ha renderi
 
 Sólo hay que navegar a `index.js` y añadir el `componentDidMount()` por encima de nuestro render. Se va a quedar así:
 
-![4 final touches](https://images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
-![5 completo](https://images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
+![4 final touches](//images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
+![5 completo](//images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
diff --git a/docs/tutorials/es/buy-one-get-one.md b/docs/tutorials/es/buy-one-get-one.md
index 9e666b4ec..f2edf97a1 100644
--- a/docs/tutorials/es/buy-one-get-one.md
+++ b/docs/tutorials/es/buy-one-get-one.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona la promoción Compre y gane'
 id: tutorials_322
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:41.148Z
-updatedAt: 2021-12-13T17:23:17.182Z
-publishedAt: 2021-12-13T17:23:17.182Z
+updatedAt: 2024-02-19T11:48:37.254Z
+publishedAt: 2024-02-19T11:48:37.254Z
 firstPublishedAt: 2017-04-27T23:03:14.992Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,47 +15,112 @@ legacySlug: como-funciona-la-promocion-compre-y-gane
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-Este tipo de promoción se utiliza para ofrecer envío gratis o un regalo en caso de que se compre un determinado producto.  Por ejemplo, "compre una televisión y no pague el envío", o "compre un videojuego y gane un juego".
+La promoción Compra uno y lleva uno gratis se utiliza para ofrecer envío gratuito o un regalo si se compra un determinado producto. Por ejemplo, “compra un televisor y no pagues gastos de envío”, o “compra un videojuego y llévate un juego totalmente gratis”.
 
-## ¿Cuáles son los datos generales de esta promoción?
+En este artículo detallaremos los pasos necesarios para configurar la promoción Compra uno y lleva uno gratis:
 
-- __Nombre__
-- __Nombre de la promoción__
-- __Status__
-- __Activa o Inactiva la promoción__
-- __Descripción interna de la promoción__: el objetivo de este campo es que sea utilizado para comunicación interna en su tienda, a fin de dejar claro si la promoción es debido a alguna campaña, quema de inventario, etc.
-- __Validez__: fecha y hora de inicio y fin de la promoción. (Se puede utilizar una fecha y/o horario futuros, para que la promoción comience a aplicarse en el sitio. Si se configura de esta forma, la promoción tendrá el status de programada hasta que se alcance la fecha y hora. Mientras la promoción esté válida, esta tendrá el status de activa y al término de la fecha y hora definidas, el status se cambiará a inactivo automáticamente.)
-- __Especificar días de la semana para activación__: esta opción es del tipo casilla de selección, que cuando se marca pone a disposición siete otras casillas de selección, para que se elijan los días de la semana en que se aplicará la promoción. Si desea que la promoción se aplique en cualquier día de la semana, no seleccione esta opción.
-- __¿Cuál tipo es el valor del descuento? __:
-  1. __Precio Máximo por Ítem__: define el precio máximo para cada ítem de la compra.
-  2. __Envío gratis__: descuento total sobre el valor del flete.
-  3. __Regalo__: descuento total sobre el valor del producto definido como regalo. Al seleccionar esta opción abren los campos para ingresar un SKU, la caja para activar el multiplicador de regalos y la cantidad de productos diferentes que serán dados de regalo. El SKU puede ser ingresado por el nombre o Id, pudiendo ser incluido más de uno. Para aprender a configurar este tipo de descuento, lea el artículo [Configurar promoción Compre y gane para un SKU específico](/pt/tutorial/configurar-promocao-compre-e-ganhe-para-um-sku-especifico).
-- __Destaque en los productos__: ingrese un tag con el nombre de la promoción. Utilizado en la vitrina y en la página de producto. Este flag solo se ingresará si utiliza el control correcto de exhibición de promoción en el template. <vtex.cmc:discountHightLight>;
-- __Seller__: seleccione el seller que ofrecerá el descuento. Si tiene multitienda, aparecerán aquí todos los sellers que haya registrado en su cuenta. Esta opción posibilita crear, condicionar un descuento diferente para cada seller.
-- __Política Comercial__: seleccione las Políticas Comerciales que ofrecerán el descuento. Se listarán aquí todas las políticas que haya registrado en: `E-Commerce> Marketplace> Políticas Comerciales`. Esta opción permite crear una promoción específica para una o más de una política comercial.
+1. [Resumen de la promoción](#1-resumen-de-la-promocion)
+    - [Restringir la promoción a los productos de los sellers](#restringir-la-promocion-a-los-productos-de-los-sellers)
+    - [Política comercial](#politica-comercial)
+2. [Compra uno y lleva uno gratis](#2-compra-uno-y-lleva-uno-gratis)
+3. [Condiciones de la promoción](#3-condiciones-de-la-promocion)
+4. [Restricciones y limitaciones de uso](#4-restricciones-y-limitaciones-de-uso)
 
-## Compre y Gane
+# Crear la promoción
 
-- __Colecciones__: digite el nombre de la colección de productos a la que desea ofrecer este tipo de descuento. Se puede ingresar más de una. La promoción se aplicará solamente a los productos que estén en las colecciones registradas en este campo.
-- __SKUs__: puede ingresar el nombre o Id de los SKUs a los que desea aplicar el descuento. Puede importar una lista de SKUs, que debe estar guardado en un archivo de texto (.txt) con cada ID en una línea diferente.
+En el Admin VTEX, accede a Promociones > Promociones o ingresa Promociones en la barra de búsqueda en la parte superior de la página.
 
-__OBS__: si no se limitan productos por colección o SKU, la plataforma no permitirá la creación de la promoción.
+1. Haz clic en el botón `Crear promoción`.
+2. Selecciona la opción **Compra uno y lleva uno gratis**.
+3. Rellena los campos de la promoción.
+4. Haz clic en `Guardar`.
 
-__Atención__: solo es posible registrar, como máximo, 100 SKUs en la promoción Compre y Gane.
+# 1. Resumen de la promoción
 
-- __Cantidad de productos para el Beneficio__: permite definir la cantidad de productos que deben ingresarse en el carrito, para que el descuento sea concedido. Este campo debe rellenarse obligatoriamente.
+En esta sección se proporciona información detallada sobre los datos generales de la promoción.
 
-## ¿Cuáles son las condiciones para que la promoción sea válida?
+- **Nombre:** nombre de la promoción. Campo obligatorio.
+- **Status:** botón que activa o desactiva la promoción.
+- **Descripción:** este campo se utiliza para la comunicación interna de tu tienda, para dejar claro si la promoción se debe a alguna campaña o liquidación de stock, por ejemplo.
+- **Fecha de vencimiento:** fecha y hora de inicio y fin de la promoción. Se puede seleccionar una fecha y hora futuras para que la promoción comience a aplicarse en el sitio web. Si se configura de esta forma, el status de la promoción se mostrará de las siguientes maneras:
+    - Programada: antes de la fecha y hora de inicio seleccionadas.
+    - Activa: durante el periodo programado de la promoción.
+    - Completada: después de la fecha y hora de fin seleccionadas.
+- **Utilizar configuración de recurrencia:**  seleccionando esta opción, puedes realizar ajustes de recurrencia, por ejemplo, día de la semana y horario.
+- **Tipo y valor del descuento:** permite seleccionar una de las opciones siguientes.
+1. **Precio máximo por ítem:** define el precio máximo para cada ítem de la compra.
+2. **Envío gratis:** es el descuento total sobre el valor del envío.
+3. **Regalo:** es el descuento total sobre el valor del producto definido como regalo. Seleccionando esta opción podrás indicar el SKU (por nombre o ID) que se considerará como regalo, elegir si debe activarse el [multiplicador de regalo](https://help.vtex.com/es/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK) y la cantidad máxima de productos que se pueden utilizar como regalos en la promoción. Para más información sobre este tipo de descuento, consulta [Configurar una promoción Compra uno y lleva uno gratis para un SKU específico](https://help.vtex.com/es/tutorial/configurar-promocao-compre-e-ganhe-para-um-sku-especifico).
+- **Información adicional (opcional):** permite incluir en la promoción información adicional que incluye un nombre y un valor.
+- **Promoción resaltada:** al elegir esta opción, se crea una tag que destaca el nombre de la promoción. Se implementa en la vitrina y en la página de producto, siempre y cuando se utilice el control de visualización de promociones correcto en la plantilla. `<vtex.cmc:discountHightLight>`.
 
-- __Restricción por BIN__: define para qué tarjetas de crédito la promoción estará activa.
-- __Cluster de Clientes__: puede utilizar un campo existente en la Entidad de Datos __CL__ para crear una restricción. Ejemplo: `edad=25`
-- __Tipo de flete__: el descuento se concederá si el tipo de flete es el mismo que el registrado.
-- __Utm\_source__: el descuento se concederá si la navegación se realiza con utm\_source con el valor registrado.
-- __Utm\_campaign__: el descuento se concederá si la navegación se realiza con utm\_campaign con el valor registrado.
-- Restricciones y limitaciones de uso
+![Resumen de la promoción](//images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/e10d90b18e8ce27fda6345f72b86a802/Resumen_de_la_promocion.png)
 
-## Restricciones y Limitaciones de uso
+## Restringir esta promoción a los productos de los sellers
 
-- __Solamente para ítems iguales__: el descuento solamente será aplicado por SKU, siempre que cada uno tenga la cantidad mínima registrada. Si no marca esta opción, el descuento se aplicará a los productos de la colección o lista de SKU, sin que cada uno de estos tenga en el carrito necesariamente la cantidad registrada, siendo considerado la sumatoria de las unidades de estos productos.
-- __Permitir acumular promociones__: permite que más de una promoción con el mismo tipo de descuento sea concedida al mismo tiempo.
+En esta sección se pueden definir los sellers a los que se aplicará la promoción. Es decir, tienes la opción de decidir qué sellers se incluirán o excluirán del descuento.
 
+- Igual a: selecciona los nombres de los sellers que deseas incluir.
+- Diferentes de: selecciona los nombres de los sellers que deseas excluir.
+
+Para que la promoción sea válida para todos los sellers, deja la selección sin marcar.
+
+<div class = "alert alert-warning">
+  <p>No es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:</p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.</ol>
+</div>
+
+![Restringir esta promoción a los productos de los sellers](//images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/2b00df355cb9670e4a5b799e5c9482e7/Restringir_esta_promoci_n_a_los_productos_de_los_sellers.png)
+
+## Política comercial
+Esta sección establece las políticas comerciales válidas para la promoción. Puedes incluir o excluir políticas comerciales del descuento.
+
+- **Igual a:** selecciona las políticas comerciales que deseas incluir.
+- **Diferentes de:** selecciona las políticas comerciales que deseas excluir.
+- **Proporcionado por mí (Mi tienda):** selección de las políticas comerciales para productos de tu tienda. Puedes seleccionar más de una política comercial.
+- **Entregado por mí (Otras tiendas):** selección de las políticas comerciales bajo las cuales tus productos aparecen en tiendas de terceros. Puedes seleccionar más de una política comercial.
+
+Para que la promoción sea válida para todas las políticas comerciales, deja la selección sin marcar.
+
+![Política comercial-ES](//images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/3580c9712e545dbd89b07b473e7409fb/Politica_comercial-ES.png)
+
+# 2. Compra uno y lleva uno gratis
+
+En esta sección se definen las colecciones, SKU y cantidad mínima que deben rellenarse.
+
+- **Colecciones:**  escribe el nombre de una o varias colecciones de productos en las que deseas aplicar este tipo de descuento. La promoción solo se aplicará a los productos que figuren en las colecciones registradas en este campo.
+- **SKUs:** permite seleccionar el nombre o ID de los SKU sobre los que deseas aplicar el descuento. También puedes importar una lista de SKU, que debe guardarse en un archivo de texto (**.txt**) con cada ID descrito en una fila diferente.
+- **Cantidad mínima:** permite definir la cantidad mínima de productos que deben agregarse al carrito para que se conceda el descuento. Es un campo obligatorio.
+
+<div class = "alert alert-warning">
+ <p>La promoción no se creará si no se rellenan los campos Colecciones o SKUs.<p>
+</div>
+
+<div class = "alert alert-warning">
+ <p>Se puede crear una promoción Compra uno y lleva uno gratis con un máximo de 100 SKU diferentes al mismo tiempo.<p>
+</div>
+
+![Compra uno y lleva uno gratis](//images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c37f45ddde8ac8ddab99cae1500a951d/Compra_uno_y_lleva_uno_gratis.png)
+
+# 3. Condiciones de la promoción
+
+En esta sección se proporciona información detallada sobre las condiciones que se deben cumplir para que una promoción sea válida.
+
+- **Usar BIN de restricción:** permite activar o desactivar la restricción del BIN, limitando las tarjetas de crédito que se pueden utilizar en la promoción creada. También puedes importar una lista de BIN, que debe guardarse en un archivo de texto (.txt) con cada BIN descrito en una fila diferente.
+- **Clúster de clientes:** permite activar o desactivar el uso del clúster de clientes. Al activarse, se puede elegir un clúster de clientes creado vía Master Data.
+- **Método de envío:** permite elegir si la promoción se aplicará a uno o varios métodos de envío seleccionados.  Cuando se activa, debes seleccionar un método de envío; cuando no se activa, tendrás la opción de elegir aplicar el descuento al envío más barato.
+- **Medio de pago:** permite elegir si la promoción se aplicará a uno o varios de los medios de pago seleccionados.
+- **Utm_source:** el descuento se concederá si la navegación utiliza un parámetro utm_source con el valor registrado.
+- **Utm_campaign:** el descuento se concederá si la navegación utiliza un parámetro utm_campaign con el valor registrado.
+
+![Cuáles son las condiciones para que la promoción sea válida?](//images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/feb16501d81f3fc85591b837bf06b42d/Cu_les_son_las_condiciones_para_que_la_promoci_n_sea_v_lida.png)
+
+# 4. Restricciones y limitaciones de uso
+
+En esta sección se proporciona información importante sobre las condiciones y restricciones aplicables a la promoción.
+
+- **Cuántas veces se aplicará esta promoción en tu tienda:** te permite restringir la aplicación de la promoción en tu tienda para un número determinado de veces o utilizarla de forma ilimitada.
+- **Cuántas veces por cliente se aplicará esta promoción:** permite restringir la cantidad de veces que cada cliente puede aplicar la promoción o si se puede utilizar de manera ilimitada.
+- **Solo para los mismos ítems:** si se activa esta opción, la promoción solo se aplica si se alcanza la cantidad mínima de ítems (previamente registrados) con el mismo SKU en el carrito. Si la opción está desactivada, la promoción se aplicará incluso cuando se agregue la cantidad mínima de ítems en el carrito, independientemente de si los SKU son diferentes o iguales.
+- **Aplicar con otras promociones:** permite aplicar esta promoción en el carrito simultáneamente con otras promociones que ofrezcan el mismo tipo de descuento.
+
+![Restricciones y limitaciones de uso](//images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/9f8d369b64e79bc40aad64c2464112c8/Restricciones_y_limitaciones_de_uso.png)
diff --git a/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md b/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
index a02cb1252..f5b91bf54 100644
--- a/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
+++ b/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
@@ -24,4 +24,4 @@ Para ello, siga los pasos abajo:
 
 Para los sellers White Label, existe un límite de 50 unidades con el mismo SKU en el carrito. Se puede ajustar este límite a través de una solicitud al equipo de [soporte](https://help.vtex.com/es/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe).
 
-![Carrinho Max ES](https://images.ctfassets.net/alneenqid6w5/E8mj8DGIKcWKMAACse4CM/eee01547a76ce8f486a0b315e139d478/Carrinho_Max_ES.png)
+![Carrinho Max ES](//images.ctfassets.net/alneenqid6w5/E8mj8DGIKcWKMAACse4CM/eee01547a76ce8f486a0b315e139d478/Carrinho_Max_ES.png)
diff --git a/docs/tutorials/es/campaign-audiences-list.md b/docs/tutorials/es/campaign-audiences-list.md
index 074c5a63f..0ccb615c7 100644
--- a/docs/tutorials/es/campaign-audiences-list.md
+++ b/docs/tutorials/es/campaign-audiences-list.md
@@ -17,7 +17,7 @@ subcategory: 2cI57eZ3ZiWSeaQs26Gwys
 
 Tal como se muestra a continuación, podrás ver la lista de audiencias de campañas registradas en tu tienda desde la página *Promociones > Audiencia de campañas* del Admin VTEX.
 
-![lista-audiencias-campanha-es](https://images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/e4d2a074233382a8563b46391f15f446/lista-audiencias-campanha-es.png)
+![lista-audiencias-campanha-es](//images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/e4d2a074233382a8563b46391f15f446/lista-audiencias-campanha-es.png)
 
 Desde esta página, puedes realizar las acciones a continuación:
 
@@ -50,7 +50,7 @@ Las audiencias de campaña se presentan en _tarjetas_ que incluyen la informaci
 
 Para ver las audiencias de campaña [archivadas](#archivar-audiencias-de-campana), dirígete a la opción **Presentar** y haz clic en **Archivados**, tal como se muestra a continuación:
 
-![toggle-audiencias-campanha-arquivadas-es](https://images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/8c1426c228b3415d28557c63bb7efc27/toggle-audiencias-campanha-arquivadas-es.png)
+![toggle-audiencias-campanha-arquivadas-es](//images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/8c1426c228b3415d28557c63bb7efc27/toggle-audiencias-campanha-arquivadas-es.png)
 
 Para volver a ver las audiencias de campaña no archivadas, haz clic en **No archivados**.
 
diff --git a/docs/tutorials/es/campaign-audiences.md b/docs/tutorials/es/campaign-audiences.md
index 459f5724b..6b1a69b23 100644
--- a/docs/tutorials/es/campaign-audiences.md
+++ b/docs/tutorials/es/campaign-audiences.md
@@ -27,7 +27,7 @@ Ejemplo: en el segmento de moda, al registrar una audiencia de campaña, puedes
 
 El público objetivo segmenta los usuarios y las condiciones elegibles de la audiencia de campaña. Si la audiencia de la campaña está activa, al cumplir todos los criterios definidos en el público objetivo, se activarán las promociones asociadas a la audiencia de la campaña.
 
-![campanha-es](https://images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/dc2f1ab65b1a442f47a5542bccc7786e/campanha-es.png)
+![campanha-es](//images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/dc2f1ab65b1a442f47a5542bccc7786e/campanha-es.png)
 
 Cuando la campaña está activada, es elegible para el contexto de compra y se cumplen todas sus restricciones, no significa necesariamente que se aplicarán todas las promociones de audiencia de la campaña asociadas a ella. Para ello, también deben cumplirse las restricciones definidas en [promoción de campaña](https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume).
 
diff --git a/docs/tutorials/es/campaign-promotion.md b/docs/tutorials/es/campaign-promotion.md
index 2591f53b2..58bf3054d 100644
--- a/docs/tutorials/es/campaign-promotion.md
+++ b/docs/tutorials/es/campaign-promotion.md
@@ -121,7 +121,7 @@ Para que la promoción sea válida para todas las políticas comerciales, deje l
 
 En esta sección, debe elegir si la promoción se aplicará a todos los productos registrados en su tienda o solo a productos específicos, como se ilustra a continuación.
 
-![promocoes-restricao-es](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/9219ee59e0e23d8a881a2ea678ff0249/promocoes-restricao-es.PNG)
+![promocoes-restricao-es](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/9219ee59e0e23d8a881a2ea678ff0249/promocoes-restricao-es.PNG)
 
 Si desea aplicar la promoción a todo su catálogo, seleccione la opción **Aplicar a todos los productos<b>**</b>.
 
@@ -131,7 +131,7 @@ Puede incluir o excluir **categorías**, **marcas**, **colecciones** y **product
 
 Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en la promoción todos los productos de la categoría **Vestido** cuya marca es **Farm**, con la excepción del producto **Vestido Rosas**.
 
-![exemplo-es](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/4b294969b056e682bd853a323e213b33/exemplo-es.PNG)
+![exemplo-es](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/4b294969b056e682bd853a323e213b33/exemplo-es.PNG)
 
 En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
 
diff --git a/docs/tutorials/es/canceling-orders.md b/docs/tutorials/es/canceling-orders.md
index eaa9dc8d4..a9dff5b78 100644
--- a/docs/tutorials/es/canceling-orders.md
+++ b/docs/tutorials/es/canceling-orders.md
@@ -3,8 +3,8 @@ title: 'Cómo cancelar pedido'
 id: tutorials_186
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:47.296Z
-updatedAt: 2023-03-31T00:26:08.605Z
-publishedAt: 2023-03-31T00:26:08.605Z
+updatedAt: 2024-04-01T17:34:46.564Z
+publishedAt: 2024-04-01T17:34:46.564Z
 firstPublishedAt: 2017-04-27T23:00:46.851Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,23 +17,28 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Tiene lugar la cancelación de Pedido en VTEX en prácticamente cualquier status de su evolución. Corresponde destacar que, una vez cancelado el pedido, no se revierte el status del pedido.
 
+<div class = "alert alert-warning">
+No es posible cancelar pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
+</div>
+
 Hay dos formas de hacer esta acción, por el Admin VTEX o API.
 
 ## Cancelación en el módulo Pedidos
 
 1. En el Admin VTEX, accede a **Pedidos > Todos los pedidos**, o escribe *Todos los pedidos* en la barra de búsqueda en la parte superior de la página.  
 2. En **Todos los pedidos**, acceda al pedido deseado.
-3. Haga clic en el botón **Confirmar cancelación** junto al card principal del status.
-4. Se requerirá confirmar que está consciente del resultado de esta acción..
+3. En el topo de la página, haga clic en `Cancelar pedido`.
+4. Rellena los campos presentados.
+5. Haga clic en `Confirmar`.
 
 Cuando el pedido está en estado **Listo para manejo** o **A preparar la entrega**, es necesario que la cancelación se haga dos veces. Esto, porque la primera vez el status se cambia a **Cancelación solicitada**.
 Cuando la solicitud ya se encuentra en el status **Cancelación solicitada**, basta hacer clic en **Confirmar cancelación** que el pedido se cambiará a **Cancelado**. Si desea continuar con este pedido, simplemente introduzca la nota fiscal.
 
-**¡Recuerde!** No se puede cambiar un pedido cuando el mismo ya está en el estado **Facturado**.
+No se puede cambiar un pedido cuando el mismo ya está en el estado `Facturado`.
 
 ## Cancelación en el ERP
 
-Esa acción por medio del ERP puede tener lugar por nuestra API REST, según nuestro [guía de integración de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing).
+Esa acción por medio del ERP puede tener lugar por nuestra API REST, según nuestro [guía de integración de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing), utilizando la llamada [Cancel order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/cancel).
 
 ## Cancelación solicitada por el cliente
 
diff --git a/docs/tutorials/es/carrefour-inventory-integration-errors.md b/docs/tutorials/es/carrefour-inventory-integration-errors.md
index 68023f7e7..3876a095b 100644
--- a/docs/tutorials/es/carrefour-inventory-integration-errors.md
+++ b/docs/tutorials/es/carrefour-inventory-integration-errors.md
@@ -3,8 +3,8 @@ title: 'Errores de integración de stock con Carrefour'
 id: 4oDrYCkrIvWETCW34I2CKF
 status: PUBLISHED
 createdAt: 2021-10-25T22:15:47.447Z
-updatedAt: 2023-03-29T14:40:33.949Z
-publishedAt: 2023-03-29T14:40:33.949Z
+updatedAt: 2024-06-17T15:05:00.226Z
+publishedAt: 2024-06-17T15:05:00.226Z
 firstPublishedAt: 2021-10-25T22:30:07.082Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/carrier-working-hours.md b/docs/tutorials/es/carrier-working-hours.md
index 5aa3542df..c34694458 100644
--- a/docs/tutorials/es/carrier-working-hours.md
+++ b/docs/tutorials/es/carrier-working-hours.md
@@ -3,8 +3,8 @@ title: 'Horario de atención de las transportadoras'
 id: 2oGpbInIgdxSWUi3TZjdCS
 status: PUBLISHED
 createdAt: 2019-02-06T16:21:24.412Z
-updatedAt: 2021-08-11T17:43:41.414Z
-publishedAt: 2021-08-11T17:43:41.414Z
+updatedAt: 2024-04-11T00:33:50.619Z
+publishedAt: 2024-04-11T00:33:50.619Z
 firstPublishedAt: 2019-02-06T18:25:37.545Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,32 +15,39 @@ legacySlug: configurar-horario-de-funcionamiento-para-transportistas, configurar
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-En la plataforma VTEX, se puede determinar el horario de atención de las transportadoras de su tienda a través de la configuración de horarios de recolección y periodos de envío en los que define la disponibilidad de las entregas de su tienda.
+En VTEX, es posible determinar los horarios de atención de las [transportadoras](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) de tu tienda a través de configuraciones de la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140), en la que defines los períodos laborales para que la transportadora recolecte y envíe los pedidos.
 
-Para configurar el horario de atención, acceda a **Inventario y envío > Estrategia de envío** y cree una nueva [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) o edite una existente. 
+Para configurar el horario laboral, an el Admin VTEX acceda a **Envío > Estrategia de envío** y cree una [nueva política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) o [edite](https://help.vtex.com/es/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE) una existente.
 
-La configuración del horario de atención influye en el cálculo del tiempo de entrega y se encuentra en la parte inferior de la página de detalles de la política de envío seleccionada, cuenta con las siguientes opciones:
+La configuración del horario laboral influye en el cálculo del tiempo de entrega y se encuentra en la parte inferior de la página de detalles de la política de envío seleccionada, cuenta con las siguientes opciones:
 
-* **[Periodo de envío](#periodo-de-envio)**: periodos en que la transportadora envía ítems a los clientes.
-* **[Horario de recolección](#horario-de-recoleccion)**: horarios en que la transportadora realiza la recolección de ítems para entrega.
+* **[Ventana de envío](#ventana-de-envio)**: periodos en que la transportadora envía ítems a los clientes.
+* **[Hora de recogida](#hora-de-recogida)**: horarios en que la transportadora realiza la recolección de ítems para entrega.
 
-## Periodo de envío
+## Ventana de envío
 
-1. Haga clic en `Período de envío`.
-2. Si lo desea, active la opción `Aceptar compras fuera del horario de atención`.
+1. En la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140), en la seción **Horario laboral**, haga clic en `Ventana de envío`.
+2. Si quieres activar la opción `Aceptar compras fuera del horario laboral`, activa el interruptor. De lo contrario, déjelo desactivado.
 
-    Esta opción permite que la transportadora acepte pedidos fuera de su horario de atención. Al configurarla como `ACTIVA`, se influirá en el cálculo del tiempo de entrega (el intervalo de tiempo desde que se realiza el pedido hasta la hora de inicio del periodo de envío de la transportadora se sumará al tiempo total de la entrega).
+  <div class="alert alert-danger">
+Para autorizar la transportadora a recibir pedidos los fines de semana, este interruptor debe estar marcado como <code>Activo</code>. Incluso si los sábados y domingos están configurados como ventanas válidas, activar el interruptor es obligatorio para autorizar al transportista a recibir pedidos fuera del horario laboral.
+</div>
 
-3. Seleccione el `Día de la semana`, así como la hora de `Inicio` y `Fin` del periodo de envío, considerando que:
-* **Día de la semana:** los días de la semana en que la transportadora realiza entregas.
-* **Inicio:** la hora en que comienza el periodo de envío.
-* **Fin:** la hora en que finaliza el periodo de envío.
-4. Haga clic en `Nuevo periodo de envío` para añadir un nuevo periodo.
-5. Para finalizar, haga clic en el botón `Guardar cambios`.
+  <div class = "alert alert-info">
+Cuando esta opción está habilitada, el <a href="https://help.vtex.com/es/tutorial/how-shipping-calculation-works--tutorials_116">cálculo del envío</a> del pedido se ve influenciado y al tiempo total de envío se suma el tiempo desde que se realiza el pedido hasta la hora de apertura del transportista.
+</div>
 
-## Horario de recolección
+3. Seleccione el `Día de la semana`, así como la `Hora de inicio` y `Hora de fin` del periodo de envío, considerando que:
+    * **Día de la semana:** los días de la semana en que la transportadora realiza entregas.
+    * **Hora de inicio:** la hora en que comienza el periodo de envío.
+    * **Hora de fin:** la hora en que finaliza el periodo de envío.
+4. Para añadir un nuevo periodo, haga clic en `Agregar ventana de envío`.
+5. Haga clic en `Guardar cambios`.
 
-1. Haga clic en la ventana `Horario de recolección`.
-2. Seleccione el `Día de la semana` y ´Horario de recolección`. 
-3. Haga clic en `Nuevo horario de recolección` para añadir un nuevo horario.
-4. Para finalizar, haga clic en el botón `Guardar cambios`.
+## Hora de recogida
+
+1. En la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140), en la seción **Horario laboral**, haga clic en la ventana `Hora de recogida`.
+2. Seleccione el `Día de la semana`.
+3. Seleccione la `Hora de recogida`. 
+4. Para añadir un nuevo horario, haga clic en `Agregar hora de recogida`.
+5. Haga clic en el botón `Guardar cambios`.
diff --git a/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md
index 02284fdac..bcc018810 100644
--- a/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -20,7 +20,7 @@ El módulo *Inventario y envío* es donde usted realiza toda la gestión de la l
 Algunas secciones de la página de registro **Política de envío** cambiaron, para darle una mayor flexibilidad cuando configure su estrategia de entrega. En la anterior versión, había una sección denominada *Configuración de tiempo*, en la que era posible seleccionar *Horario de operación*, *Horario de corte* o *Entrega agendada* para cada transportadora. 
 
 __Anterior versión__
-![ES Configurações de tempo versão antiga](https://images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/6afb6a15f8cc04c2167bc2a33ccf510d/ES_Configura____es_de_tempo_vers__o_antiga.jpg)
+![ES Configurações de tempo versão antiga](//images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/6afb6a15f8cc04c2167bc2a33ccf510d/ES_Configura____es_de_tempo_vers__o_antiga.jpg)
 
 En la nueva versión:  
 - Cambiamos los nombres de las opciones para que sean más fáciles de entender.   
@@ -28,7 +28,7 @@ En la nueva versión:
 - Añadimos la opción Configurar capacidad de entrega, para que la entrega programada se base en la realidad de su operación.   
 
 __Versión Beta__
-![ES Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/de667ba6adbdcd826ed90da21a6aa385/ES_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![ES Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/de667ba6adbdcd826ed90da21a6aa385/ES_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 ## Horario de recolección
 
@@ -45,7 +45,7 @@ Al igual que en la versión anterior, no es posible configurar las opciones de *
 Esta funcionalidad se denominaba *Entrega agendada* en la anterior versión y ahora se denomina *Entrega programada*. Además, antes solo era posible optar por esta funcionalidad omitiendo la configuración de *Horario de operación*. Sin embargo, ahora es posible configurar *Entrega programada* junto con la opción *Horario de atención* para que su cliente elija este método de entrega durante el checkout del pedido. Vea los campos que se deben completar para configurar esta opción.
 
 **Versión Beta**
-![ES entrega agendada](https://images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/62dcaef0097e846366826ae301a35714/ES_entrega_agendada.jpg)
+![ES entrega agendada](//images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/62dcaef0097e846366826ae301a35714/ES_entrega_agendada.jpg)
 
 - **Tiempo máximo de entrega**:  este campo se debe completar de acuerdo con su operación logística. Defina cuál es el mayor periodo de tiempo que la transportadora emplea para realizar una entrega programada, desde la confirmación del pedido hasta la confirmación de la entrega.
 - **Configurar capacidad de entrega**: dependiendo de las características de su operación y de cómo la transportadora envía sus productos, puede tener más sentido definir la capacidad de entrega en número de ítems o en número de pedidos. Por ejemplo, si su tienda es del segmento de supermercados y el medio de transporte para la entrega programada es una motocicleta, hay un número límite de ítems que ese vehículo puede almacenar y por eso recomendamos que seleccione «ítems» como unidad. Por otro lado, si su operación tiene pocos ítems por pedido, tendrá más sentido definir «pedidos» como unidad, por ejemplo.
diff --git a/docs/tutorials/es/carries-on-vtex.md b/docs/tutorials/es/carries-on-vtex.md
index b4e3c2174..48aed97ef 100644
--- a/docs/tutorials/es/carries-on-vtex.md
+++ b/docs/tutorials/es/carries-on-vtex.md
@@ -3,8 +3,8 @@ title: 'Transportadoras en VTEX'
 id: 7u9duMD5UQa2QQwukAWMcE
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:39.775Z
-updatedAt: 2023-03-31T01:00:22.710Z
-publishedAt: 2023-03-31T01:00:22.710Z
+updatedAt: 2023-07-31T22:14:54.618Z
+publishedAt: 2023-07-31T22:14:54.618Z
 firstPublishedAt: 2019-01-24T22:14:26.579Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/es/catalog-overview-2.md b/docs/tutorials/es/catalog-overview-2.md
index e0a062ca2..56bf0d45e 100644
--- a/docs/tutorials/es/catalog-overview-2.md
+++ b/docs/tutorials/es/catalog-overview-2.md
@@ -1,10 +1,10 @@
 ---
 title: 'Visión General Catálogo'
 id: FFrumKPYFpvIWKRXfhQYp
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-28T17:25:52.296Z
-updatedAt: 2023-03-28T17:31:02.205Z
-publishedAt: 2023-03-28T17:31:02.205Z
+updatedAt: 2024-03-14T16:38:37.477Z
+publishedAt: 
 firstPublishedAt: 2023-03-28T17:31:02.205Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -24,8 +24,6 @@ El menú **Catálogo** contiene las funcionalidades relativas al surtido de prod
 
 El menú **Catálogo** de tu Admin actualizado reúne las páginas donde gestionas tu catálogo, los precios y el stock de tu *ecommerce*.
 
-![visao-geral-produto-ES](https://images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/ad397a99b3db19ea9187ef5667577a26/image.png)
-
 A continuación, encontrarás más detalles sobre las diferentes secciones y páginas de este menú.
 
 ## Catálogo
diff --git a/docs/tutorials/es/catalog-overview.md b/docs/tutorials/es/catalog-overview.md
index 62f1ae06b..a920d2697 100644
--- a/docs/tutorials/es/catalog-overview.md
+++ b/docs/tutorials/es/catalog-overview.md
@@ -15,18 +15,17 @@ legacySlug: catalogo-vision-general
 subcategory: 
 ---
 
-![Catalogo overview (tapa)](https://raw.githubusercontent.com/vtexdocs/help-center-content/main/images/es/catalogo-vision-general-0.jpg)
-El catálogo es el módulo de administración de tu tienda que te permite configurar las funcionalidades relacionadas con los productos de tu ecommerce. Para que tu cliente pueda ver los productos en el sitio web, debes registrarlos en este módulo.
+![Catalogo overview (tapa)](//images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/acb839745dcafabbe9cfa2dfbd529484/image1.jpg)
+El catálogo es el módulo de administración de tu tienda que te permite configurar las funcionalidades relacionadas con los productos de tu ecommerce. Para que tu cliente pueda ver los productos en el sitio web, debes registrarlos en este módulo. 
 
 En este artículo, encontrarás una visión general de los ítems del catálogo y su funcionalidad.
 
 ## Categorías
-
 La categoría es el segundo nivel de categorización de tu tienda, debajo del nivel [Departamentos](https://help.vtex.com/es/tutorial/que-es-un-departamento--22rKjmYWVmmKAK8CWa8yKw), que son secciones o sectores que categorizan las áreas de tu negocio. La categoría esencial para el registro de productos.
 
 El módulo **Categorías** te permite ver y gestionar el árbol de categorías registradas en tu tienda, como se muestra en el ejemplo a continuación.
 
-![Estructura del catalogo](https://raw.githubusercontent.com/vtexdocs/help-center-content/main/images/es/catalogo-vision-general-1.png)
+![Estructura del catalogo](//images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/6f11799fa0f016fa0429a2e49e757f27/image5.png)
 
 Puedes registrar una categoría siguiendo el tutorial [Registrar una categoría](https://help.vtex.com/es/tutorial/registrando-categoria--tutorials_206). Si deseas gestionar o desactivar una categoría, sigue los pasos del tutorial [Desactivar y reorganizar categorías](https://help.vtex.com/es/tutorial/desactivando-y-reorganizando-categorias--tutorials_264).
 
@@ -35,7 +34,6 @@ Dentro de las categorías, existen las [subcategorías](https://help.vtex.com/es
 Las [categorías similares](https://help.vtex.com/es/tutorial/configurando-categoria-similar--tutorials_204) permiten que un producto esté en más de una categoría al mismo tiempo, y las [categorías globales](https://help.vtex.com/es/tutorial/configurando-a-categoria-global--tutorials_188) se utilizan para las integraciones externas, como con los marketplaces u otros canales de venta.  
 
 ## Marcas
-
 La marca es un campo obligatorio para la creación de un producto, ya que sin ella no es posible registrarlo. En VTEX, hay una sección específica para que registres las marcas de los productos disponibles en tu tienda.
 
 Al asociar una marca a tus productos, puedes crear una navegación utilizando este atributo como filtro en tu tienda. Los clientes suelen buscar productos empleando el nombre de una marca como palabra clave.
@@ -46,9 +44,9 @@ Puedes registrar una marca siguiendo el tutorial [Registrar marcas](https://help
 
 ## Productos y SKU
 
-El producto es la definición más genérica de algo disponible en tu tienda, como, por ejemplo, "Camisa". Los SKU son variaciones de este producto, como el color y el tamaño, por ejemplo. Una misma camisa (producto) puede estar disponible en las tallas P, M o G, que son las especificaciones.
+El producto es la definición más genérica de algo disponible en tu tienda, como, por ejemplo, "Camisa". Los SKU son variaciones de este producto, como el color y el tamaño, por ejemplo. Una misma camisa (producto) puede estar disponible en las tallas P, M o G, que son las especificaciones. 
 
-La combinación de especificaciones de un producto es un SKU, como, por ejemplo, camisa P. Es obligatorio que un producto tenga al menos un SKU.
+La combinación de especificaciones de un producto es un SKU, como, por ejemplo, camisa P. Es obligatorio que un producto tenga al menos un SKU. 
 
 La sección Productos y SKU del VTEX Admin te permite gestionar tus productos y SKU. Puedes registrar un producto siguiendo el tutorial [Registrar productos](https://help.vtex.com/es/tutorial/registrar-productos--tutorials_2567). A continuación, registra un SKU siguiendo los pasos del tutorial [Rellenar los campos de registro de SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY).
 
@@ -64,13 +62,13 @@ Para registrar una especificación, accede a los tutoriales [Crear un campo de p
 
 ## Importación y exportación
 
-Esta funcionalidad permite al usuario del Admin importar [imágenes](https://help.vtex.com/es/tutorial/importando-imagenes-por-plantilla--tutorials_262), [productos](https://help.vtex.com/es/tutorial/como-exportar-planilla-de-productos--2sIroGeqZqaN3NAvaSGwWV), [SKU](https://help.vtex.com/es/tutorial/importar-y-exportar-especificacion-de-producto-y-sku--tutorials_274), marcas y [plantillas de stock](https://help.vtex.com/es/tutorial/importando-y-exportando-plantilla-de-stock--tutorials_2034) en tu tienda a través de plantillas, lo que facilita el llenado en masa.
+Esta funcionalidad permite al usuario del Admin importar [imágenes](https://help.vtex.com/es/tutorial/importando-imagenes-por-plantilla--tutorials_262), [productos](https://help.vtex.com/es/tutorial/como-exportar-planilla-de-productos--2sIroGeqZqaN3NAvaSGwWV), [SKU](https://help.vtex.com/es/tutorial/importar-y-exportar-especificacion-de-producto-y-sku--tutorials_274), marcas y [plantillas de stock](https://help.vtex.com/es/tutorial/importando-y-exportando-plantilla-de-stock--tutorials_2034) en tu tienda a través de plantillas, lo que facilita el llenado en masa. 
 
 Para entender cómo utilizar esta funcionalidad, lee el artículo [Rellenar los campos de la plantilla de importación](https://help.vtex.com/es/tutorial/rellenar-campos-de-la-planilla-de-importacion--4nYhx63Q5yokQWaMguaIgI).
 
 ## Tipos de listas
 
-Las listas son agrupaciones de productos que ofrecer a tus clientes en tu tienda. Pueden ser de varios tipos y estar asociadas a eventos, como bodas, cumpleaños u otras ocasiones.
+Las listas son agrupaciones de productos que ofrecer a tus clientes en tu tienda. Pueden ser de varios tipos y estar asociadas a eventos, como bodas, cumpleaños u otras ocasiones. 
 
 En esta sección se configuran las listas que estarán disponibles en el sitio web. Para aprender a crear una lista, sigue el tutorial [Crear un tipo de lista](https://help.vtex.com/es/tutorial/criando-tipo-de-lista--tutorials_254).
 
@@ -89,25 +87,22 @@ En VTEX, la funcionalidad de configuración de XML utiliza combinaciones de dife
 Para entender cómo configurar un XML, sigue los pasos del tutorial [Cómo configurar un XML](https://help.vtex.com/es/tutorial/como-configurar-xml--tutorials_242).
 
 ## Informes
-
 Puedes obtener informes de los movimientos en tu tienda. Los informes disponibles en la tienda son:
 
-- [Informe de seguridad](https://help.vtex.com/es/tutorial/informe-de-seguridad--tutorials_282)
-- [Informe de indexación](https://help.vtex.com/es/tutorial/utilizando-el-informe-de-indexacion--4ikVpMhwByyS8sysaeOIm4)
-- Informe de lista de compras
-- Informe de Avísame
-- Informe de newsletter
-- [Informe de evaluación](https://help.vtex.com/es/tutorial/acceder-a-las-evaluaciones-de-productos--139sIVny6fyXK0Nk60L1NF)
-- Informe de descargas
+ - [Informe de seguridad](https://help.vtex.com/es/tutorial/informe-de-seguridad--tutorials_282)
+ - [Informe de indexación](https://help.vtex.com/es/tutorial/utilizando-el-informe-de-indexacion--4ikVpMhwByyS8sysaeOIm4)
+ - Informe de lista de compras
+ - Informe de Avísame
+ - Informe de newsletter
+ - [Informe de evaluación](https://help.vtex.com/es/tutorial/acceder-a-las-evaluaciones-de-productos--139sIVny6fyXK0Nk60L1NF)
+ - Informe de descargas
 
 ## Condiciones comerciales
-
 La condición comercial es una agrupación de SKU que sirve para crear diferentes escenarios de pago. Por ejemplo, esta configuración puede permitir el pago en 12 cuotas con tarjetas de crédito solo para productos electrónicos en tu tienda.
 
 Para registrar una condición comercial, sigue el tutorial [Registrar una condición comercial](https://help.vtex.com/es/tutorial/registrar-condicion-comercial--tutorials_445).
 
 ## Proveedores
-
 Esta funcionalidad te permite registrar proveedores para tu tienda o marketplace. Para registrar un proveedor, sigue los pasos a continuación.
 En el Admin, haz clic en **Catálogo** > **Proveedores**.
 Haz clic en `Nuevo proveedor`.
@@ -122,7 +117,6 @@ Rellena los siguientes campos de registro:
 6. Haz clic en `Guardar`.
 
 ## Colecciones
-
 La colección es la agrupación de dos o más SKU que pueden tener o no características comunes para ser presentados en las páginas de productos de tu tienda.
 
 Se pueden crear colecciones para asociar los SKU utilizando otros criterios de agrupación, como festividades, lanzamientos o productos más vendidos.
@@ -130,3 +124,4 @@ Se pueden crear colecciones para asociar los SKU utilizando otros criterios de a
 Por ejemplo, puedes crear una página para celebrar el Día de San Valentín y hacer una lista de regalos recomendados para la ocasión, creando una colección de "regalos".
 
 Para crear una colección, sigue el tutorial [Crear una colección](https://help.vtex.com/es/tutorial/registrar-colecciones-beta--yJBHqNMViOAnnnq4fyOye).
+
diff --git a/docs/tutorials/es/categories.md b/docs/tutorials/es/categories.md
index 03a006220..06467c9fc 100644
--- a/docs/tutorials/es/categories.md
+++ b/docs/tutorials/es/categories.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 La página **Categorías** te permite ver y gestionar el árbol de categorías registradas en Seller Portal. Puedes acceder a la página en VTEX Admin en **Productos** > **Categorías**.
 
-![categorias-es](https://images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/efff0f39ab9b9e36ed69ec8f9cf928ec/categorias-es.PNG)
+![categorias-es](//images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/efff0f39ab9b9e36ed69ec8f9cf928ec/categorias-es.PNG)
 
 En el árbol de categorías, puedes realizar diversas acciones:
 
@@ -51,7 +51,7 @@ Para encontrar una categoría, debes escribir su nombre en la barra de búsqueda
 ## Navegar por el árbol de categorías
 La página de categorías muestra los niveles más externos de las categorías. Haz clic en el ícono <i class="fas fa-angle-right"></i> para acceder a las subcategorías, como se muestra a continuación.
 
-![arvore-categoria-ES](https://images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/d28b34e0bc719c604dcfbbb3f28a2956/arvore-categoria-ES.gif)
+![arvore-categoria-ES](//images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/d28b34e0bc719c604dcfbbb3f28a2956/arvore-categoria-ES.gif)
 
 Para ver la información de registro de una categoría, haz clic en su nombre.
 
diff --git a/docs/tutorials/es/category-registration-fields.md b/docs/tutorials/es/category-registration-fields.md
index 53011de34..20a5b9f55 100644
--- a/docs/tutorials/es/category-registration-fields.md
+++ b/docs/tutorials/es/category-registration-fields.md
@@ -3,8 +3,8 @@ title: 'Llenar campos de registro de categoría'
 id: 5Z7RrvW41yumyQCmk2iqoG
 status: PUBLISHED
 createdAt: 2017-09-20T14:44:06.897Z
-updatedAt: 2022-08-01T18:47:26.486Z
-publishedAt: 2022-08-01T18:47:26.486Z
+updatedAt: 2024-01-04T14:40:33.174Z
+publishedAt: 2024-01-04T14:40:33.174Z
 firstPublishedAt: 2017-09-20T14:58:27.420Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -43,9 +43,9 @@ Para entender mejor el significado de cada campo del registro de categoría, vea
 - __Score (utilizado para ordenación de búsqueda):__ valor utilizado para definir la prioridad en la página de resultados de búsqueda. Para entender más sobre Score, accede a nuestro artículo [¿Cómo funciona el campo Score?](https://help.vtex.com/es/tutorial/como-funciona-el-campo-score--1BUZC0mBYEEIUgeQYAKcae).
 - __Modo de visualización de los productos:__ define cómo se mostrarán los SKUs en la página del producto. Vea abajo las opciones de relleno de este campo:
   - __Lista de SKUs:__ todos los SKUs del departamento o categoría en cuestión se mostrarán en el formato de lista. Cada uno con su botón de Comprar al lado.
-  ![1Lista.es](https://images.ctfassets.net/alneenqid6w5/37tngqcxF8hJTzWqxUG8jA/1c5f90c33525bfaf34b6ab729a9d02b5/Lista.es.png)
+  ![1Lista.es](//images.ctfassets.net/alneenqid6w5/37tngqcxF8hJTzWqxUG8jA/1c5f90c33525bfaf34b6ab729a9d02b5/Lista.es.png)
   - __Ingeles de selección de radio (radioBox):__ todos los SKUs de ese departamento/categoría necesitarán ser seleccionados a través de selección de radio.
-  ![RadioBox.es](https://images.ctfassets.net/alneenqid6w5/F33F8dSkcV2SePNONlGb2/d0029323d5f7f07f2d1c53fb5d784ccc/RadioBox.es.png)
+  ![RadioBox.es](//images.ctfassets.net/alneenqid6w5/F33F8dSkcV2SePNONlGb2/d0029323d5f7f07f2d1c53fb5d784ccc/RadioBox.es.png)
   - __Sigue la definición de la especificación SKU:__ todos los SKUs de ese departamento/categoría serán seleccionados de acuerdo con la pestaña Especificación, en el formulario de registro de SKU. Las opciones preconfiguradas son Combo o Radio.
-  ![Campos.es](https://images.ctfassets.net/alneenqid6w5/17S7QKJpvr31r3LGRRCSSn/c3350ddfca051df6be8592fad107410f/Campos.es.png)
+  ![Campos.es](//images.ctfassets.net/alneenqid6w5/17S7QKJpvr31r3LGRRCSSn/c3350ddfca051df6be8592fad107410f/Campos.es.png)
 
diff --git a/docs/tutorials/es/change-a-placeholder-title.md b/docs/tutorials/es/change-a-placeholder-title.md
index 778b5e23d..6eb14a2d2 100644
--- a/docs/tutorials/es/change-a-placeholder-title.md
+++ b/docs/tutorials/es/change-a-placeholder-title.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 El título de un placeholder es el que aparece en la esquina derecha del objeto, como indica la imagen abajo.
 
-![cms-placeholder es](https://images.ctfassets.net/alneenqid6w5/UWClcSxWUKaG4qwSiSekQ/3c19965a673d3d5904b0098cad0da60a/placeholder_destaque_es.png)
+![cms-placeholder es](//images.ctfassets.net/alneenqid6w5/UWClcSxWUKaG4qwSiSekQ/3c19965a673d3d5904b0098cad0da60a/placeholder_destaque_es.png)
 
 El texto que se inserta en ese campo es el que se mostrará como título del placeholder en el sitio de la tienda.
 
@@ -26,7 +26,7 @@ Para cambiar el título de un placeholder, basta con seguir los pasos abajo:
 1. Haga clic en el título.
 
 2. Introduzca el nuevo título.
-![placeholder-change-name es](https://images.ctfassets.net/alneenqid6w5/6gMl2GzVlY8gwyWQ4SA0me/96ede6e52392d55358cf786e932e899f/change_name_es.png)
+![placeholder-change-name es](//images.ctfassets.net/alneenqid6w5/6gMl2GzVlY8gwyWQ4SA0me/96ede6e52392d55358cf786e932e899f/change_name_es.png)
 
 3. Haga clic en __Rename__.
 
diff --git a/docs/tutorials/es/change-seller.md b/docs/tutorials/es/change-seller.md
index d49c13ef8..fcc455301 100644
--- a/docs/tutorials/es/change-seller.md
+++ b/docs/tutorials/es/change-seller.md
@@ -26,13 +26,13 @@ Un cambio de <i>seller</i> puede ocurrir en dos situaciones:
 - <i>Seller</i> cancela un pedido.
 - <i>Marketplace</i> decide cambiar el <i>seller</i>.
 
-![seller_cancela_pedido_ES](https://images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/9a1899752e5df76040cbcbdb12aaf456/seller_cancela_pedido_ES.png)
+![seller_cancela_pedido_ES](//images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/9a1899752e5df76040cbcbdb12aaf456/seller_cancela_pedido_ES.png)
 
 Puede [configurar el periodo para cambiar de seller de 0 a 30 días](https://developers.vtex.com/vtex-rest-api/reference/updatewindowtochangeseller), por defecto, la ventana de cambio es de dos días. Al configurar la ventana a 0 días, no hay un período efectivo para el cambio de _sellers_ y la _feature_, aunque configurada, no funciona en la práctica, lo que provoca que el pedido proceda a la cancelación.
 
 Cuando el <i>seller</i> le notifica la cancelación, el <i>marketplace</i> puede configurar el número de días para actuar y decidir entre cancelar la compra o cambiar de <i> seller.</i> Tenga en cuenta que si opta por el cambio, el <i>marketplace</i> es el responsable de comunicarlo al cliente final.
 
-![mkt_cancela_seller_ES](https://images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/28c420f005191ccba061053f44833275/mkt_cancela_seller_ES.png)
+![mkt_cancela_seller_ES](//images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/28c420f005191ccba061053f44833275/mkt_cancela_seller_ES.png)
 
 ## Limitaciones
 
diff --git a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
index 23bdf3150..90ff72846 100644
--- a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -33,7 +33,7 @@ Después de [habilitar la funcionalidad](https://developers.vtex.com/vtex-rest-a
 3. Cambie el precio al valor deseado y presione `ENTER`.
 4. Haga clic en `Cerrar pedido`.
 
-![manualprice](https://images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/a2c63f9fd22cbc180cb95ca790ab7b61/manualprice.gif)
+![manualprice](//images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/a2c63f9fd22cbc180cb95ca790ab7b61/manualprice.gif)
 
 Además de la configuración en la pantalla de Checkout , el precio de un producto también se puede modificar a través de la API [Change Price](https://developers.vtex.com/vtex-rest-api/reference/pricechange), obtenga más información en [Setting the price of an item manually](https://developers.vtex.com/vtex-rest-api/docs/enable-the-manual-price#setting-the-price-of-an-item-manually).
 
diff --git a/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
index 924fbfc0a..8846b1286 100644
--- a/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
@@ -51,9 +51,9 @@ Es decir, estoy usando las variables `preposicaonomeloja2` y `nomeloja`.
 Al utilizar variables para crear un texto, reemplace el símbolo <code>#</code> por <code>@</code>. Es decir, <b>#variable#</b> se convierte <b>@variable@</b>.
 </div>
 
-![textos-importantes es](https://images.ctfassets.net/alneenqid6w5/3Trct11oXCGe0EigiUA4g0/f701207101145a1222f5e45cb61d4073/textos_importantes_es.png)
+![textos-importantes es](//images.ctfassets.net/alneenqid6w5/3Trct11oXCGe0EigiUA4g0/f701207101145a1222f5e45cb61d4073/textos_importantes_es.png)
 
-![exemplo-textos-da-loja es](https://images.ctfassets.net/alneenqid6w5/vKgZfyW6dieKAqUy242OC/f57ed59d90b2db3ae86d77b62dea3a69/3_es.png)
+![exemplo-textos-da-loja es](//images.ctfassets.net/alneenqid6w5/vKgZfyW6dieKAqUy242OC/f57ed59d90b2db3ae86d77b62dea3a69/3_es.png)
 
 Como defini que el contenido de la primera variable es "a" y el de la segunda es "VtexArgentina", el texto final renderizado en el sitio será "Bienvenido a VtexArgentina".
 
diff --git a/docs/tutorials/es/changing-items-from-a-complete-order.md b/docs/tutorials/es/changing-items-from-a-complete-order.md
index 6471a8840..dc2fa989c 100644
--- a/docs/tutorials/es/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/es/changing-items-from-a-complete-order.md
@@ -3,8 +3,8 @@ title: 'Cambiar ítems de un pedido finalizado'
 id: tutorials_190
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:22.411Z
-updatedAt: 2023-05-03T14:22:00.584Z
-publishedAt: 2023-05-03T14:22:00.584Z
+updatedAt: 2024-04-01T17:40:33.284Z
+publishedAt: 2024-04-01T17:40:33.284Z
 firstPublishedAt: 2017-04-27T23:00:47.264Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -37,8 +37,9 @@ Antes de realizar cambios en el pedido, ten en cuenta las restricciones de la fu
 * Una solicitud de cambio solo se produce si hay cambios en la cantidad de ítems o la sustitución de al menos un SKU en el pedido.
 * No está permitido cambiar ítems que no sean del propio _marketplace_ o de una cuenta franquicia.
 * Es necesario que el [adquirente](https://help.vtex.com/es/tutorial/que-es-un-adquirente--7N1oRTG8dGmOiIugC0cs4E) acepte el nuevo valor de la transacción para que se produzca el cambio.
-* El aumento del precio solo se permite si el pedido se ha pagado con [tarjeta de crédito pagaré](https://help.vtex.com/es/tutorial/como-configurar-pagamento-personalizado--tutorials_451#pagares), [efectivo](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ) o [control de crédito](https://help.vtex.com/es/tutorial/customer-credit-vision-general--1uIqTjWxIIIEW0COMg4uE0). Además, el [adquirente](https://help.vtex.com/es/tutorial/que-es-un-adquirente--7N1oRTG8dGmOiIugC0cs4E) debe permitir transacciones sin el uso del código CVV y dos operaciones de cobro en el mismo pedido.
+* El aumento del precio solo se permite si el pedido se ha pagado con [tarjeta de crédito pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ), [efectivo](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ) o [control de crédito](https://help.vtex.com/es/tutorial/customer-credit-vision-general--1uIqTjWxIIIEW0COMg4uE0). Además, el [adquirente](https://help.vtex.com/es/tutorial/que-es-un-adquirente--7N1oRTG8dGmOiIugC0cs4E) debe permitir transacciones sin el uso del código CVV y dos operaciones de cobro en el mismo pedido.
 * La [reserva](https://help.vtex.com/es/tutorial/como-se-maneja-la-reserva--tutorials_92) de los ítems en el _stock_ no es automática. Es necesario actualizar manualmente la cantidad de ítems que siguen disponibles en el _[stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139)_.
+* No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible cambiar el pedido.
 * No se puede modificar un pedido con una transacción finalizada. Por ejemplo, para los cambios en el valor de un pedido con descuento, el OMS considera que, si el status que se muestra en Detalles de la transacción es distinto de «Finished», todavía puedes cambiar el valor de la transacción, aunque el valor ya se haya liquidado.  
 * No es posible realizar cambios en  pedidos procedentes de _[marketplaces integrados con VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-en-vtex--tutorials_402)_ (ya sean conectores nativos o conectores de _partners_).
 * Solo se pueden modificar los pedidos que están en preparación.
diff --git a/docs/tutorials/es/changing-the-total-cost-of-the-order.md b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
index 8dd951d3d..48dbb21fb 100644
--- a/docs/tutorials/es/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
@@ -28,13 +28,13 @@ Para hacer el cambio, sigue los pasos a continuación:
 3. Haz clic en el pedido para acceder a la página de **Detalles del pedido**.   
 4. En la página *Detalles del pedido*, ve a la sección **Costo total del pedido**.
 5. Haz clic en `Cambiar el costo final`.  
-![valorfinalES](https://images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/625d67dbe3011b8aea8574e247f9a2d4/valorfinalES__1_.png)  
+![valorfinalES](//images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/625d67dbe3011b8aea8574e247f9a2d4/valorfinalES__1_.png)  
 6. Se abrirá la página **Cambiar el valor**, en la que debes rellenar los siguientes campos obligatorios:  
 7.  Rellena los campos obligatorios:
     * **Valor:** Selecciona Descuento o Aumentar e introduce el valor que deseas modificar.  
     * **Razón**: indica los motivos del cambio.  
 8. En la parte derecha de la página, haz clic en `Enviar`;
-![Alterar valorES](https://images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/8488873894611990391d7bb132ab9c04/Alterar_valorES.png)
+![Alterar valorES](//images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/8488873894611990391d7bb132ab9c04/Alterar_valorES.png)
 
 Los cambios en el pedido se actualizarán en la sección *Ítems a Facturar*, y en el *Historial de Pedidos*. Ten en cuenta que el valor total del pedido también cambiará.
 
diff --git a/docs/tutorials/es/changing-tracking-data.md b/docs/tutorials/es/changing-tracking-data.md
index 838d519e3..b0139cb81 100644
--- a/docs/tutorials/es/changing-tracking-data.md
+++ b/docs/tutorials/es/changing-tracking-data.md
@@ -38,4 +38,4 @@ Para cambiar los datos de un pedido manualmente, sigue los pasos a continuación
     * **Seleccionar transportadora: **selecciona la transportadora que realizará la entrega.
 7. Haz clic en `Guardar`.
 
-![FaturaES](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
+![FaturaES](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
diff --git a/docs/tutorials/es/check-order-delivery-details.md b/docs/tutorials/es/check-order-delivery-details.md
index ee84c0a9a..ffe0a4d27 100644
--- a/docs/tutorials/es/check-order-delivery-details.md
+++ b/docs/tutorials/es/check-order-delivery-details.md
@@ -45,6 +45,6 @@ Para ver estos detalles, basta con hacer una [simulación de flete](/es/tutorial
 6. Introduzca el código postal del pedido.
 7. Haga clic en __Simular Flete__.
 
-![simular-frete es](https://images.ctfassets.net/alneenqid6w5/4uPm4LFmr6wGSwOMu800kW/e7dbece799e4f3920ef3e82f7ea56220/simular-frete_es.png)
+![simular-frete es](//images.ctfassets.net/alneenqid6w5/4uPm4LFmr6wGSwOMu800kW/e7dbece799e4f3920ef3e82f7ea56220/simular-frete_es.png)
 
 Para cada transportista considerado en la simulación, usted puede ver los detalles del pedido correspondiente. Para ello, haga clic en __detallar__.
diff --git a/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md b/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md
index 808c3dfe5..62cf0def8 100644
--- a/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md
+++ b/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md
@@ -23,7 +23,7 @@ Digamos que usted desea saber cuáles fueron los criterios que la plataforma uti
 
 En primer lugar, vamos a acceder a la página Todos los Pedidos para ver el pedido.
 
-![1](https://images.ctfassets.net/alneenqid6w5/xkTs21R8sUe67U2UynJDC/047786ceb646c4545fd1bada4dec38a0/1.png)
+![1](//images.ctfassets.net/alneenqid6w5/xkTs21R8sUe67U2UynJDC/047786ceb646c4545fd1bada4dec38a0/1.png)
 > En la esquina superior derecha, está la __fecha en la que se realizó el pedido__ (06 MAYO).
 > Y en el inferior, se puede ver el __plazo de entrega del pedido__ (22 MAYO).
 
@@ -31,25 +31,25 @@ Ahora vamos a entrar en el módulo __Envío__ y simular el flete de ese pedido.
 
 Para ello, siga los pasos abajo:
 1. En el Admin VTEX, accede a **Envío > Simulador de envío**, o escribe *Simulador de envío* en la barra de búsqueda en la parte superior de la página.  
-2. Introduzca el nombre o el ID de cada SKU que estaba en el carrito del pedido que usted desea investigar, incluyendo la cantidad de cada uno de ellos.![2](https://images.ctfassets.net/alneenqid6w5/4imJypzFvYSmMeQij3XLjp/429d397d9bec73f104cff43053b3c6a0/2.png)
+2. Introduzca el nombre o el ID de cada SKU que estaba en el carrito del pedido que usted desea investigar, incluyendo la cantidad de cada uno de ellos.![2](//images.ctfassets.net/alneenqid6w5/4imJypzFvYSmMeQij3XLjp/429d397d9bec73f104cff43053b3c6a0/2.png)
 3. Introduzca el código postal del pedido.
 4. Haga clic en __Simular envío__.
 
 En el ejemplo siguiente, tenga en cuenta que 4 transportistas fueron considerados, y 12 fueron desconsiderados.
 
-![3](https://images.ctfassets.net/alneenqid6w5/5k78O44E8Nr8nrTkBoe6MX/5d17f0a86264d1d09befbba43b0b1339/3.png)
+![3](//images.ctfassets.net/alneenqid6w5/5k78O44E8Nr8nrTkBoe6MX/5d17f0a86264d1d09befbba43b0b1339/3.png)
 
 Al consultar una vez más la pantalla del pedido en el módulo OMS, vemos que el tipo de entrega elegido por el cliente para ese pedido fue el __Expressa__, y que la transportista elegida por la plataforma para realizar la entrega fue __Expressa & CO__.
 
-![4](https://images.ctfassets.net/alneenqid6w5/2LjWMpCXtfH3lMYgAAjc7s/b62a52b045292c305143286ebcf93b88/4.png)
+![4](//images.ctfassets.net/alneenqid6w5/2LjWMpCXtfH3lMYgAAjc7s/b62a52b045292c305143286ebcf93b88/4.png)
 
 Por lo tanto, volviendo a la simulación de flete, en el menu Envío, concluimos que la tercera opción fue la elegida en ese pedido - y que, por lo tanto, el plazo de entrega total del pedido fue de 12 días.
 
-![5](https://images.ctfassets.net/alneenqid6w5/25KVkamW576ta3MkOpuYaN/2ae8577822b36650afe8153ebe4c6127/5.png)
+![5](//images.ctfassets.net/alneenqid6w5/25KVkamW576ta3MkOpuYaN/2ae8577822b36650afe8153ebe4c6127/5.png)
 
 Ahora basta con hacer clic en __detallar__ para ver los tiempos de costo que se utilizaron para calcular el plazo de entrega.
 
-![6](https://images.ctfassets.net/alneenqid6w5/42029fSPhJS5KKdio01gzh/dd0d9612093783f0cddf259f1b2e5798/6.png)
+![6](//images.ctfassets.net/alneenqid6w5/42029fSPhJS5KKdio01gzh/dd0d9612093783f0cddf259f1b2e5798/6.png)
 
 Cada uno de los tres tiempos de costo corresponde a lo que se definió para las tres etapas de la ruta de logística: stock, muelle y transportadora.
 
diff --git a/docs/tutorials/es/checkout-vtex-overview.md b/docs/tutorials/es/checkout-vtex-overview.md
index 18078746b..4d712c47e 100644
--- a/docs/tutorials/es/checkout-vtex-overview.md
+++ b/docs/tutorials/es/checkout-vtex-overview.md
@@ -35,7 +35,7 @@ A continuación, se describe la experiencia de compra de un cliente, además de
 
 Siempre que el cliente realiza un cambio en el carrito (agrega o elimina ítems), o cuando se actualiza la pantalla del checkout, se ejecuta la siguiente cadena de procesos internos en el módulo Checkout.
 
-![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/435f909fb3e5493329a6a76fcb398134/Checkout_Overview_ES.png)
+![Checkout overview](//images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/435f909fb3e5493329a6a76fcb398134/Checkout_Overview_ES.png)
 
 <div class="alert alert-info">
 Si un <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#">Seller white label</a>, puede entregar uno o más ítems de los que eligió el cliente, se realizarán simulaciones (tal como se muestra a la derecha de la imagen) para determinar qué sellers serán los responsables de entregar los ítems. Obtén más información en <a href="https://help.vtex.com/es/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Selección de sellers white label</a>.
diff --git a/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md b/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
index 2c80b520c..9c1a01485 100644
--- a/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
+++ b/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
@@ -3,8 +3,8 @@ title: 'Elegir entre arquitectura multitienda o entorno adicional'
 id: 4HRNpa1OCKZ5YzP8yiilBL
 status: PUBLISHED
 createdAt: 2023-05-25T16:33:11.450Z
-updatedAt: 2023-05-25T19:39:40.359Z
-publishedAt: 2023-05-25T19:39:40.359Z
+updatedAt: 2023-10-02T16:57:08.371Z
+publishedAt: 2023-10-02T16:57:08.371Z
 firstPublishedAt: 2023-05-25T19:35:27.925Z
 contentType: tutorial
 productTeam: Management
@@ -35,23 +35,23 @@ Para arquitecturas de marketplace, también se puede <a href="https://help.vtex.
 
 La tabla siguiente muestra cómo se relacionan las distintas arquitecturas con los componentes y funcionalidades de la plataforma VTEX.
 
-| Tema                                     | Arquitectura multitienda (store)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Arquitectura de entornos adicionales                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Arquitectura                             | Un solo Admin VTEX ([account](https://help.vtex.com/es/tutorial/o-que-e-account-name)) con múltiples subcuentas ([stores](https://help.vtex.com/es/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Dos entornos ([accounts](https://help.vtex.com/es/tutorial/o-que-e-account-name)) del Admin VTEX separados.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| Segmentación de las condiciones de venta | Posibilidad de segmentar aplicaciones del catálogo, precios, pagos, promociones y otros componentes utilizando [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y [bindings](https://help.vtex.com/es/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W).                                                                                                                                                                                                                                                                                                                                                                                                                                | Al tratarse de dos entornos separados y con configuraciones independientes, el administrador de la tienda tiene mucho más control sobre las posibilidades de segmentar las condiciones de venta en diferentes escenarios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| Tipo de equipo                           | Recomendado cuando una misma empresa y un mismo equipo gestionan dos o más tiendas online con catálogos similares e ítems en común, pero que quieren ofrecer storefronts distintos para que sus compradores accedan a experiencias con marcas diferentes.                                                                                                                                                                                                                                                                                                                       | Recomendado cuando equipos diferentes de una misma empresa se ocupan de tiendas online distintas.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| Storefront                               | Los storefronts son diferentes para cada tienda, pero se gestionan desde un mismo Admin VTEX.Si la intención es solamente cambiar el idioma del sitio web, pero el funcionamiento de la tienda es el mismo, se puede utilizar [multibinding](https://help.vtex.com/es/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) y la [internacionalización de catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization) para la configuración en un mismo entorno VTEX.<br>Esta arquitectura es diferente de una [cuenta franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), ya que esta cuenta no tiene un sitio web propio. Los consumidores navegan directamente en el sitio web de la cuenta principal, que en este contexto actúa como un marketplace.     | Cada account gestiona sus propios storefronts en Admins VTEX separados y pueden utilizar todas las opciones disponibles de segmentación de storefronts.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| Desempeño del Admin VTEX                 | El desempeño del Admin VTEX puede verse afectado cuantas más [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) haya asociadas a una misma cuenta principal, ralentizando el uso de las funcionalidades de la plataforma, ya que es necesario actualizar la información en cada política comercial. <br>También se prevén impactos en el desempeño del Admin si el catálogo de productos es muy extenso, con más de 2 millones de ítems, lo que aumenta el tiempo de indexación.                                                                                                                             | Es posible crear varias [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?), independientes para cada entorno.<br>El desempeño del Admin VTEX puede verse afectado cuantas más políticas comerciales haya asociadas a una misma cuenta principal, ralentizando el uso de determinadas funcionalidades de la plataforma.<br>Sin embargo, al tratarse de entornos separados, se reduce la necesidad de registrar varias políticas comerciales.                                                                                                                                                                                                                                                                                                                                                                                              |
-| Costos                                   | Aunque agregar una store no tiene costo adicional, es necesario [contratar una política comercial adicional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) si se quiere diferenciar el storefront en los sitios web. Más información sobre las políticas comerciales y la segmentación de los ajustes disponibles en [Cómo funciona una política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).                                                                                                                                                                                                                                                                      | Es necesario [contratar un entorno adicional](https://help.vtex.com/es/tutorial/contratar-novo-ambiente--tutorials_2542), con costo adicional previsto en el contrato con VTEX. <br>Si lo deseas, también puedes [contratar una política comercial adicional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), si quieres segmentar la configuración de cada entorno para condiciones diferentes. Más información sobre las políticas comerciales y la segmentación de las configuraciones disponibles en [Cómo funciona una política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).                                                                                                                                                                                                                                                                                                                                                                                                      |
-| Operación                                | Cuando utilices este tipo de arquitectura, evalúa la complejidad de gestionar el catálogo, las promociones, los precios, el stock, los pedidos y los pagos pensando en diferentes stores, ya que todos los datos estarán en el mismo Admin. Es posible configurar la [internacionalización del catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization) para vender en diferentes países.                                                                                                                                                                                                                                        | Recomendamos esta arquitectura en los casos donde haya operaciones en dos países diferentes, cuando es necesaria la separación lingüística directamente en el catálogo, para facilitar el funcionamiento de equipos que se comunican también en idiomas distintos.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| Master Data                              | A medida que se crea una subaccount, [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) se genera también por separado y de forma predeterminada, lo que significa que cada cuenta tiene el suyo. Sin embargo, es posible unificarlos abriendo un [ticket con nuestro equipo de Soporte](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).                                                                                                                                                                                                                                                                                                                                |  Cada cuenta tendrá su propio [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| Seguridad de la información              | Todos los componentes se comparten entre las stores, como catálogo, promociones, precios y configuración de pagos. <br>Es importante tener en cuenta este punto cuando diferentes equipos de una misma empresa tienen acceso al Admin VTEX. Por ejemplo, los empleados de la marca B podrán visualizar el catálogo, los precios y los pedidos de la marca A, aunque la marca A y la marca B sean dos stores distintas.                                                                                                                                                          | La separación de entornos significa que los empleados de equipos diferentes no tienen acceso a los datos y configuración del catálogo, promociones, precios y configuración de pagos, entre otros componentes.<br>Por ejemplo, los empleados de la marca B no podrán visualizar el catálogo, los precios y los pedidos de la marca A, ya que la marca A y la marca B son entornos VTEX separados.                                                                                                                                                                                                                                                                                                                                                                                                           |
-| License Manager                          | El mismo [License Manager](https://help.vtex.com/es/tutorial/visao-geral-do-modulo-license-manager) gestiona todos los usuarios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Cada Admin tendrá su propio [Licence Manager](https://help.vtex.com/es/tutorial/visao-geral-do-modulo-license-manager), con gestión de usuarios independiente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| Tarjeta de regalo                        | Las subaccounts tendrán acceso a la misma gestión de tarjetas de regalo y se podrán utilizar en storefronts diferentes.                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Cada Admin tendrá su gestión única de tarjetas de regalo, y las que se generan en un entorno no podrán utilizarse en el otro.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| Estructura de marketplace                | La estructura de marketplace no se aplica entre stores diferentes, puesto que ya comparten catálogo, precios y stock. <br>                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Es posible que un entorno sea seller en el otro y viceversa, poniendo todos sus productos en venta en ambos sitios web, con base en la relación seller-marketplace. Más información en [Configurar marketplaces VTEX](https://help.vtex.com/es/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) y [Cómo configurar el seller para vender en un marketplace VTEX](https://help.vtex.com/es/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP). <br>También es posible crear cuentas franquicia, para que operen como sellers white label, ya que tienen precios, stock y logística diferentes. Más información en [Elegir entre cuenta estándar, cuenta franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).<br>Esto puede hacerse contratando un entorno adicional (en caso de que tengan ítems del catálogo en común, pero no todos) o una cuenta franquicia (en caso de catálogos exactamente iguales). Más información en [Elegir entre cuenta estándar, cuenta franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).   |
-| Sitemap                                  | Habrá un [sitemap](https://help.vtex.com/es/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) único para la account principal, que se compartirá entre las stores.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Cada account posee su [sitemap](https://help.vtex.com/es/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) independiente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| B2B: Catálogo                            | No es posible cambiar la unidad de medida registrada en el catálogo para cada [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#catalogo). Por ejemplo, las tiendas B2B venden al por mayor, mientras que las B2C lo hacen al por menor. <br>El storefront B2B con catálogo centralizado tendrá la página de producto con una sola unidad. Dependiendo del negocio, será necesario personalizar el storefront para permitir un mínimo de unidades de ese SKU. <br>Es posible ampliar el catálogo creando kits, pero serían kits creados para la mayoría de los productos, generando un catálogo prácticamente duplicado. | Como los catálogos de cada entorno son independientes, no se aplican las restricciones presentes en el entorno multitienda.Es posible adaptar uno de los catálogos únicamente para ventas B2B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| B2B: configuración del orderForm         | Al aplicarse una arquitectura multitienda, todas las stores compartirán la misma [configuración del orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm), en el checkout.<br>Existen sistemas que pueden integrarse con el Admin VTEX y dependen de este tipo de configuración para realizar la integración, como es el caso de los proveedores de impuestos, por ejemplo.<br>En la práctica, en la integración de un proveedor de impuestos, el orderform será llamado tanto en B2C como en B2B en un entorno multitienda, lo que perjudica a la operación del cliente.                                                    | Es posible crear una configuración independiente del [orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) para cada entorno, satisfaciendo las necesidades de las integraciones externas en el checkout de una tienda B2B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| Tema | Arquitectura multitienda (store) | Arquitectura de entornos adicionales |
+| - | - | - |
+| Arquitectura | Un solo Admin VTEX ([account](https://help.vtex.com/es/tutorial/o-que-e-account-name)) con múltiples subcuentas ([stores](https://help.vtex.com/es/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)). | Dos entornos ([accounts](https://help.vtex.com/es/tutorial/o-que-e-account-name)) del Admin VTEX separados. |
+| Segmentación de las condiciones de venta | Posibilidad de segmentar aplicaciones del catálogo, precios, pagos, promociones y otros componentes utilizando [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y [bindings](https://help.vtex.com/es/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W). | Al tratarse de dos entornos separados y con configuraciones independientes, el administrador de la tienda tiene mucho más control sobre las posibilidades de segmentar las condiciones de venta en diferentes escenarios. |
+| Tipo de equipo | Recomendado cuando una misma empresa y un mismo equipo gestionan dos o más tiendas online con catálogos similares e ítems en común, pero que quieren ofrecer storefronts distintos para que sus compradores accedan a experiencias con marcas diferentes. | Recomendado cuando equipos diferentes de una misma empresa se ocupan de tiendas online distintas. |
+| Storefront | Los storefronts son diferentes para cada tienda, pero se gestionan desde un mismo Admin VTEX.Si la intención es solamente cambiar el idioma del sitio web, pero el funcionamiento de la tienda es el mismo, se puede utilizar [multibinding](https://help.vtex.com/es/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) y la [internacionalización de catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization) para la configuración en un mismo entorno VTEX.<br>Esta arquitectura es diferente de una [cuenta franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), ya que esta cuenta no tiene un sitio web propio. Los consumidores navegan directamente en el sitio web de la cuenta principal, que en este contexto actúa como un marketplace. | Cada account gestiona sus propios storefronts en Admins VTEX separados y pueden utilizar todas las opciones disponibles de segmentación de storefronts. |
+| Desempeño del Admin VTEX | El desempeño del Admin VTEX puede verse afectado cuantas más [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?) haya asociadas a una misma cuenta principal, ralentizando el uso de las funcionalidades de la plataforma, ya que es necesario actualizar la información en cada política comercial. <br>También se prevén impactos en el desempeño del Admin si el catálogo de productos es muy extenso, con más de 2 millones de ítems, lo que aumenta el tiempo de indexación. | Es posible crear varias [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?), independientes para cada entorno.<br>El desempeño del Admin VTEX puede verse afectado cuantas más políticas comerciales haya asociadas a una misma cuenta principal, ralentizando el uso de determinadas funcionalidades de la plataforma.<br>Sin embargo, al tratarse de entornos separados, se reduce la necesidad de registrar varias políticas comerciales. |
+| Costos | Aunque agregar una store no tiene costo adicional, es necesario [contratar una política comercial adicional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) si se quiere diferenciar el storefront en los sitios web. Más información sobre las políticas comerciales y la segmentación de los ajustes disponibles en [Cómo funciona una política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). | Es necesario [contratar un entorno adicional](https://help.vtex.com/es/tutorial/contratar-novo-ambiente--tutorials_2542), con costo adicional previsto en el contrato con VTEX. <br>Si lo deseas, también puedes [contratar una política comercial adicional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), si quieres segmentar la configuración de cada entorno para condiciones diferentes. Más información sobre las políticas comerciales y la segmentación de las configuraciones disponibles en [Cómo funciona una política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). |
+| Operación | Cuando utilices este tipo de arquitectura, evalúa la complejidad de gestionar el catálogo, las promociones, los precios, el stock, los pedidos y los pagos pensando en diferentes stores, ya que todos los datos estarán en el mismo Admin. Es posible configurar la [internacionalización del catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization) para vender en diferentes países. | Recomendamos esta arquitectura en los casos donde haya operaciones en dos países diferentes, cuando es necesaria la separación lingüística directamente en el catálogo, para facilitar el funcionamiento de equipos que se comunican también en idiomas distintos. |
+| Master Data | Cuando se crea una subcuenta, [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) se crea por defecto por separado, es decir, cada cuenta tiene su propio Master Data. Puede replicar los datos de una cuenta a otra para rellenar las entidades estándar (CL, AD y OD) solicitándolo a través de [ticket a nuestro equipo de Soporte](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). Sin embargo, las entidades personalizadas sólo existen en la cuenta en la que se crearon y no pueden replicarse a otras cuentas. |  Cada cuenta tendrá su propio [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). |
+| Seguridad de la información | Todos los componentes se comparten entre las stores, como catálogo, promociones, precios y configuración de pagos. <br>Es importante tener en cuenta este punto cuando diferentes equipos de una misma empresa tienen acceso al Admin VTEX. Por ejemplo, los empleados de la marca B podrán visualizar el catálogo, los precios y los pedidos de la marca A, aunque la marca A y la marca B sean dos stores distintas. | La separación de entornos significa que los empleados de equipos diferentes no tienen acceso a los datos y configuración del catálogo, promociones, precios y configuración de pagos, entre otros componentes.<br>Por ejemplo, los empleados de la marca B no podrán visualizar el catálogo, los precios y los pedidos de la marca A, ya que la marca A y la marca B son entornos VTEX separados. |
+| License Manager | El mismo [License Manager](https://help.vtex.com/es/tutorial/visao-geral-do-modulo-license-manager) gestiona todos los usuarios. | Cada Admin tendrá su propio [Licence Manager](https://help.vtex.com/es/tutorial/visao-geral-do-modulo-license-manager), con gestión de usuarios independiente. |
+| Tarjeta de regalo | Las subaccounts tendrán acceso a la misma gestión de tarjetas de regalo y se podrán utilizar en storefronts diferentes. | Cada Admin tendrá su gestión única de tarjetas de regalo, y las que se generan en un entorno no podrán utilizarse en el otro. |
+| Estructura de marketplace | La estructura de marketplace no se aplica entre stores diferentes, puesto que ya comparten catálogo, precios y stock. <br> | Es posible que un entorno sea seller en el otro y viceversa, poniendo todos sus productos en venta en ambos sitios web, con base en la relación seller-marketplace. Más información en [Configurar marketplaces VTEX](https://help.vtex.com/es/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) y [Cómo configurar el seller para vender en un marketplace VTEX](https://help.vtex.com/es/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP). <br>También es posible crear cuentas franquicia, para que operen como sellers white label, ya que tienen precios, stock y logística diferentes. Más información en [Elegir entre cuenta estándar, cuenta franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).<br>Esto puede hacerse contratando un entorno adicional (en caso de que tengan ítems del catálogo en común, pero no todos) o una cuenta franquicia (en caso de catálogos exactamente iguales). Más información en [Elegir entre cuenta estándar, cuenta franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78). |
+| Sitemap | Habrá un [sitemap](https://help.vtex.com/es/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) único para la account principal, que se compartirá entre las stores. | Cada account posee su [sitemap](https://help.vtex.com/es/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) independiente. |
+| B2B: Catálogo | No es posible cambiar la unidad de medida registrada en el catálogo para cada [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#catalogo). Por ejemplo, las tiendas B2B venden al por mayor, mientras que las B2C lo hacen al por menor. <br>El storefront B2B con catálogo centralizado tendrá la página de producto con una sola unidad. Dependiendo del negocio, será necesario personalizar el storefront para permitir un mínimo de unidades de ese SKU. <br>Es posible ampliar el catálogo creando kits, pero serían kits creados para la mayoría de los productos, generando un catálogo prácticamente duplicado. | Como los catálogos de cada entorno son independientes, no se aplican las restricciones presentes en el entorno multitienda.Es posible adaptar uno de los catálogos únicamente para ventas B2B. |
+| B2B: configuración del orderForm | Al aplicarse una arquitectura multitienda, todas las stores compartirán la misma [configuración del orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm), en el checkout.<br>Existen sistemas que pueden integrarse con el Admin VTEX y dependen de este tipo de configuración para realizar la integración, como es el caso de los proveedores de impuestos, por ejemplo.<br>En la práctica, en la integración de un proveedor de impuestos, el orderform será llamado tanto en B2C como en B2B en un entorno multitienda, lo que perjudica a la operación del cliente. | Es posible crear una configuración independiente del [orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) para cada entorno, satisfaciendo las necesidades de las integraciones externas en el checkout de una tienda B2B. |
 
 ## Más información
 
diff --git a/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
index 1755c970f..d902aa8f0 100644
--- a/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -3,8 +3,8 @@ title: 'Elegir entre cuenta estándar, cuenta franquicia o Seller Portal'
 id: 4S90HzzhMyZESsHqrnUs78
 status: PUBLISHED
 createdAt: 2022-04-20T14:15:50.164Z
-updatedAt: 2022-06-22T21:39:18.954Z
-publishedAt: 2022-06-22T21:39:18.954Z
+updatedAt: 2023-11-22T14:09:05.122Z
+publishedAt: 2023-11-22T14:09:05.122Z
 firstPublishedAt: 2022-04-27T21:42:35.010Z
 contentType: tutorial
 productTeam: Channels
@@ -23,6 +23,8 @@ En VTEX, existen tres tipos de cuenta, y cada una permite actuar con un perfil d
 - **Cuenta franquicia:** en el momento en que se crea, se asocia a una cuenta estándar, de la cual hereda el catálogo. La [cuenta franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) puede configurar su propia logística, pagos y precios, y tiene los módulos de la plataforma VTEX en forma parcial, además de un [seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 - **Seller Portal:** el [Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) es una edición de la plataforma VTEX que les permite a los _sellers_ conectarse y vender productos en _marketplaces_ del ecosistema VTEX, independientemente de si el _seller_ ya tiene una cuenta en VTEX o no. El Seller Portal brinda acceso parcial a los módulos de la plataforma, y el _seller_ puede ser normal o [white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 
+<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+
 La tabla que figura a continuación muestra los principales escenarios de uso de cada tipo de cuenta:
 
 | **Seller Portal** | **Cuenta estándar** | **Cuenta franquicia** |
@@ -61,7 +63,7 @@ A continuación, hay una serie de comparaciones sobre cómo el Seller Portal, la
 | **Aspecto** | **Seller Portal** | **Cuenta estándar** | **Cuenta franquicia** |
 |---------- | ---------- | ---------- | ---------- |
 | Heredar precio de otra cuenta | Cuando el _marketplace_ VTEX [invita](https://help.vtex.com/es/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A) al _seller_ al Seller Portal a través de la opción [Seller White Label](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa), los productos del _seller_ heredan los precios del _marketplace_. Sin embargo, el _seller_ puede editar los precios. | La cuenta estándar no hereda precios de otra cuenta. Es necesario registrarlos en su propio entorno. | La cuenta franquicia puede heredar precios de la cuenta principal. |
-| El _marketplace_ VTEX puede sobreescribir precios del _seller_ | No, el _marketplace_ VTEX solo puede definir reglas comerciales para el _seller_. | Sí. | No, el _marketplace_ VTEX solo puede definir reglas comerciales para la cuenta franquicia. |
+| El _marketplace_ VTEX puede sobreescribir precios del _seller_ | Si el seller creado a través de una invitación es un seller común, su precio puede sobreescribirse, lo que no es posible si se trata de un seller white label. | Sí. | No, el _marketplace_ VTEX solo puede definir reglas comerciales para la cuenta franquicia. |
 | Tiene [Manual Pricing](https://help.vtex.com/es/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS#ingresar-precio-manual) | Sí. | Sí. | Sí. |
 
 ## Promociones
diff --git a/docs/tutorials/es/cms-overview.md b/docs/tutorials/es/cms-overview.md
index 57274a157..cea545a63 100644
--- a/docs/tutorials/es/cms-overview.md
+++ b/docs/tutorials/es/cms-overview.md
@@ -1,10 +1,10 @@
 ---
 title: 'CMS - Descripción General'
 id: 2X1xWJi9WmtNylxmggn3ts
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-29T18:36:32.910Z
-updatedAt: 2023-03-29T19:34:13.250Z
-publishedAt: 2023-03-29T19:34:13.250Z
+updatedAt: 2023-07-18T18:36:27.273Z
+publishedAt: 
 firstPublishedAt: 2023-03-29T18:38:26.442Z
 contentType: tutorial
 productTeam: Others
@@ -15,7 +15,7 @@ legacySlug: cms-descripcion-general
 subcategory: 3PNmhq67KMmGTBSfIWJdcQ
 ---
 
-![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/4d6d76df74914b87f0f47e986ea7b405/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/4d6d76df74914b87f0f47e986ea7b405/CAPA_OVERVIEW_CMS.png)
 El CMS (Content Management System) es una funcionalidad dedicada a la gestión de contenido de manera práctica y constante.
 
 En VTEX, el CMS se encarga de gestionar las páginas que conforman el sitio web de tu tienda, ofreciéndote autonomía para crear, organizar, editar y definir toda la estructura de las carpetas, los archivos y los componentes de tu vitrina.
diff --git a/docs/tutorials/es/cms-store-overview.md b/docs/tutorials/es/cms-store-overview.md
index 4204c70fa..0e2603424 100644
--- a/docs/tutorials/es/cms-store-overview.md
+++ b/docs/tutorials/es/cms-store-overview.md
@@ -19,7 +19,7 @@ La página **Tienda** te permite realizar configuraciones de SEO, habilitar las
 
 En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Tienda** y descubre las principales herramientas disponibles en la interfaz.
 
-![CMS Tienda](https://images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/1493fec4898f2f28e98bdd749b507fbf/store-es-overview.png)
+![CMS Tienda](//images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/1493fec4898f2f28e98bdd749b507fbf/store-es-overview.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Antes de realizar cambios en la <b>pestaña Advanced (Avanzado)</b>, ponte en contacto con tu equipo de desarrolladores y consulta nuestra <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-best-practices-for-optimizing-performance#enabling-store-settings">documentación sobre la optimización del rendimiento</a> para mais informações.
diff --git a/docs/tutorials/es/collection-highlight-control.md b/docs/tutorials/es/collection-highlight-control.md
index 57b1f7b27..3439feba1 100644
--- a/docs/tutorials/es/collection-highlight-control.md
+++ b/docs/tutorials/es/collection-highlight-control.md
@@ -3,8 +3,8 @@ title: 'Control de destaque de colección'
 id: 1tGdb2ndjqy6yWsk2YwKMu
 status: PUBLISHED
 createdAt: 2018-02-21T19:12:49.216Z
-updatedAt: 2023-03-29T18:01:46.386Z
-publishedAt: 2023-03-29T18:01:46.386Z
+updatedAt: 2023-06-22T17:42:41.479Z
+publishedAt: 2023-06-22T17:42:41.479Z
 firstPublishedAt: 2018-02-21T20:51:49.939Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
 <div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
+  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el Portal CMS Legado</a>.</p>
 </div>
 
 El control `<vtex.cmc:HightLight/>` (para páginas de producto) o `$product.HightLight` (para estantes) renderiza un elemento HTML con una clase específica en el contexto de los productos que forman parte de una colección marcada con la flag __Highlight__.
diff --git a/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md b/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
index 8e8dd460f..17ea95885 100644
--- a/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
+++ b/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
@@ -31,7 +31,7 @@ Ahora que ha verificado el saldo, es importante tener en cuenta que el valor mí
 
 Por ejemplo, si el menor valor que puede recibir es R$10, ese es el valor mínimo que puede anticipar. El valor máximo se informa en el propio Admin - el saldo que usted acabó de verificar - en la página "Anticipar cuentas por cobrar".
 
-![anteciparpaymentES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/2tIGxzUGlbr3JwUMKFIKqu/57222cbc6c044d15be5e3a46f583e3e1/anteciparpaymentES.png_h_250_h_250)
+![anteciparpaymentES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/2tIGxzUGlbr3JwUMKFIKqu/57222cbc6c044d15be5e3a46f583e3e1/anteciparpaymentES.png_h_250_h_250)
 
 <div class=”alert alert-info”>
 <strong>Atención</strong>: las cuentas por cobrar en disputa o programadas para el siguiente día hábil no pueden ser anticipadas.
diff --git a/docs/tutorials/es/conditions-builder-usage-examples.md b/docs/tutorials/es/conditions-builder-usage-examples.md
index dea047382..5b38bdea8 100644
--- a/docs/tutorials/es/conditions-builder-usage-examples.md
+++ b/docs/tutorials/es/conditions-builder-usage-examples.md
@@ -24,7 +24,7 @@ Para entender __para qué__ crear condiciones, vea el artículo [Crear Precios C
 
 UTM (Marketing tag) es una información que se refiere al origen del tráfico del cliente. Entonces, en el app existe un bloque que comprueba este tipo de información.
 
-![utm_source_english](https://images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
+![utm_source_english](//images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
 
 <div class="alert alert-warning"><strong>Nota: </strong>
 Es posible que su tienda utilice personalización y, por eso, las informaciones de UTM contenidas en la URL no se están pasando a nuestro sistema. Si utiliza personalización de Javascript, lea el artículo <a href="https://help.vtex.com/es/faq/por-que-las-utms-no-se-aplican-al-carrito">¿Por qué las UTMs no se aplican al carrito?</a>
@@ -42,7 +42,7 @@ __utm_campaign__ informa en __cuál campaña__ específicamente su cliente ha he
 
 __utm_medium__ informa cuál __canal de propaganda__ alcanzó a su cliente que puede ser, por ejemplo, Email o Banner en un website. En el caso de la imagen, el bloque comprueba si el canal fue *email*.
 
-![utmenglish](https://images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
+![utmenglish](//images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
   
 Para cada uno de estos bloques, usted tiene la opción de verificar si:
 
@@ -86,7 +86,7 @@ Este bloque analiza el valor total que existe en el carrito.
 
 Vamos a suponer que usted quiera dar un precio más barato a un champú si el cliente está llevando __exactamente 3 unidades__, pero, además de eso, debe estar llevando __como mínimo 150 reales__ en compras. La condición que se creará será:
 
-![Exemplo2](https://images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
+![Exemplo2](//images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
 
 *cantidad de este artículo en el carrito es **exactamente** 3
 **Y**
diff --git a/docs/tutorials/es/conecta-la-integration.md b/docs/tutorials/es/conecta-la-integration.md
index 5a04ee36b..5958aa99f 100644
--- a/docs/tutorials/es/conecta-la-integration.md
+++ b/docs/tutorials/es/conecta-la-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integración con Conecta Lá'
 id: 403fvPYdv2f6VeP0na3awP
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-06-08T17:54:34.361Z
-updatedAt: 2023-03-29T15:27:11.094Z
-publishedAt: 2023-03-29T15:27:11.094Z
+updatedAt: 2024-02-19T20:16:43.888Z
+publishedAt: 
 firstPublishedAt: 2021-06-08T18:36:46.591Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/configure-cartman.md b/docs/tutorials/es/configure-cartman.md
index 04e562109..a0c303c01 100644
--- a/docs/tutorials/es/configure-cartman.md
+++ b/docs/tutorials/es/configure-cartman.md
@@ -3,8 +3,8 @@ title: 'Configurar Cartman'
 id: 1ACMTStZYkMqB0lTgwg451
 status: PUBLISHED
 createdAt: 2019-09-03T15:02:48.303Z
-updatedAt: 2022-06-15T23:16:07.805Z
-publishedAt: 2022-06-15T23:16:07.805Z
+updatedAt: 2024-03-13T18:18:17.017Z
+publishedAt: 2024-03-13T18:18:17.017Z
 firstPublishedAt: 2019-09-09T18:28:20.208Z
 contentType: tutorial
 productTeam: Shopping
@@ -25,13 +25,14 @@ Para dominios oficiales de la tienda (`www.{sutienda}.com`), debe activar [activ
 
 Este artículo cubrirá los siguientes temas:
 
-- [Activar Cartman manualmente](configurar-cartman#activar-cartman-manualmente)
-- [Funciones Cartman](configurar-cartman#funciones-cartman)
-  - [Obtener información sobre los ítems en el carrito](configurar-cartman#obtener-informacion-sobre-los-items-en-el-carrito)
-  - [Agregar ítems específicos al carrito](configurar-cartman#agregar-items-especificos-al-carrito)
-  - [Agregar ítems aleatorios al carrito](configurar-cartman#agregar-items-aleatorios-al-carrito)
-  - [Establecer datos de marketing](configurar-cartman#establecer-datos-de-marketing)
-- [Deshabilitar Cartman](configurar-cartman#deshabilitar-cartman) 
+- [Activar Cartman manualmente](#activar-cartman-manualmente)
+- [Funciones Cartman](#funciones-cartman)
+  - [Simulador de promociones](#simulador-de-promociones)
+  - [Obtener información sobre los ítems en el carrito](#obtener-informacion-sobre-los-items-en-el-carrito)
+  - [Agregar ítems específicos al carrito](#agregar-items-especificos-al-carrito)
+  - [Agregar ítems aleatorios al carrito](#agregar-items-aleatorios-al-carrito)
+  - [Establecer datos de marketing](#establecer-datos-de-marketing)
+- [Deshabilitar Cartman](#deshabilitar-cartman) 
 
 <div class="alert alert-warning">
   Solo el comerciante tiene acceso a <b>Cartman</b>. Sus funciones no están disponibles para el uso de los usuarios en una tienda.
@@ -43,15 +44,21 @@ Para activar Cartman manualmente, siga los pasos a continuación:
 
 1. Acceda a cualquier página de Checkout de su tienda (`https://{accountname}.myvtex.com/checkout/`).
 2. Inserte la query string `?cartman=on` al final de la URL (`https://accountname.myvtex.com/checkout?cartman=on`).
-3. En la esquina inferior derecha de la pantalla, haga clic en el botón <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para acceder a Cartman.
+3. En la esquina inferior derecha de la pantalla, haga clic en el botón <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para acceder a Cartman.
 
 ## Funciones Cartman
 
+### Simulador de promociones
+
+Al acceder al **Simulador de promociones**, puedes ver las promociones creadas en tu tienda que se aplicaron al carrito y por qué se activaron. También puedes probar aplicar promociones antes de activarlas, incluyendo promociones inactivas y programadas.
+
+Para más información sobre esta herramienta, consulta el artículo [Simulador de promociones](https://help.vtex.com/es/tutorial/simulador-de-promociones-beta--4zc8SNqjqeIJ0ZRMhjlnvy).
+
 ### Obtener información sobre los ítems en el carrito
 
 Accediendo al **Ver detalles del carrito**, es posible consultar la información específica de cada uno de los productos seleccionados en el carrito.
 
-![Detalles del ítem](https://images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/a643ad49b22b39430ab5b671288c4f7f/Detalles_del___tem.PNG)
+![Detalles del ítem](//images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/a643ad49b22b39430ab5b671288c4f7f/Detalles_del___tem.PNG)
 
 ### Agregar ítems específicos al carrito
 
@@ -61,7 +68,7 @@ En **Agregar ítems por ID de SKU**, se pueden agregar nuevos ítems al carrito
 - **Cantidad de cada ítem**: indicación de cuántas unidades SKU se agregarán al carrito.
 - **ID do seller**: indicación de cuántas unidades SKU se agregarán al carrito. 
 
-![Agregar ítems por ID de SKU](https://images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/784f07a4ade0a1cc3ac1f2bc2e5face2/Agregar___tems_por_ID_de_SKU.PNG)
+![Agregar ítems por ID de SKU](//images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/784f07a4ade0a1cc3ac1f2bc2e5face2/Agregar___tems_por_ID_de_SKU.PNG)
 
 ### Agregar ítems aleatorios al carrito
 
@@ -75,7 +82,7 @@ En **Agregar ítems al azar**, nuevos ítems del catálogo de la tienda se puede
 - ID do seller
 - Gama de precios (Precio desde / Precio hasta)
 
-![Agregar ítems al azar](https://images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/06250c93160b6506a130e4e7f34c3f9f/Agregar___tems_al_azar.PNG)
+![Agregar ítems al azar](//images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/06250c93160b6506a130e4e7f34c3f9f/Agregar___tems_al_azar.PNG)
 
 ### Establecer datos de marketing
 
@@ -87,7 +94,7 @@ En la opción **Establecer datos de marketing**, puede aplicar cupones de descue
 - **utmi_cp**: utm interna utilizada para definir cuándo se aplicará una determinada promoción, según la utm descrita en la URL del pedido.  
 - **Cupón**: código de cupón de descuento para agregar al carrito.
 
-![Establecer datos de marketing](https://images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/77827b5abd6f7cddb1c431468317589c/Establecer_datos_de_marketing.PNG)
+![Establecer datos de marketing](//images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/77827b5abd6f7cddb1c431468317589c/Establecer_datos_de_marketing.PNG)
 
 Para obtener más información sobre UTMs y UTMIs, vaya a [Qué son utm_source, utm_campaign y utm_medium](https://help.vtex.com/es/tutorial/que-son-utm-source-utm-campaign-y-utm-medium--2wTz7QJ8KUG6skGAoAQuii#) y [Qué son las UTMs internas utmi_cp, utmi_pc y utmi_p](https://help.vtex.com/es/tutorial/o-que-sao-as-utms-internas-utmi_cp-utmi_pc-e-utmi_p#).
 
@@ -96,7 +103,7 @@ Para obtener más información sobre UTMs y UTMIs, vaya a [Qué son utm_source,
 Cartman se puede desactivar en cualquier momento según lo requiera el lojista. Para deshabilitarlo, siga los pasos a continuación:
 
 1. Acceda a cualquier página de Checkout de su tienda   (`https://{accountname}.myvtex.com/checkout/`).
-2. En la esquina inferior derecha de la pantalla, haga clic en el botón <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
+2. En la esquina inferior derecha de la pantalla, haga clic en el botón <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
 3. En la parte inferior del menú de Cartman, haz clic en `Deshabilitar Cartman`.
 
 <div class="alert alert-info">
diff --git a/docs/tutorials/es/configure-direct-consumer-credit-cdc-by-losango.md b/docs/tutorials/es/configure-direct-consumer-credit-cdc-by-losango.md
index 24be8276f..93b8c4e1a 100644
--- a/docs/tutorials/es/configure-direct-consumer-credit-cdc-by-losango.md
+++ b/docs/tutorials/es/configure-direct-consumer-credit-cdc-by-losango.md
@@ -3,8 +3,8 @@ title: 'Configurar crédito directo al consumidor (CDC) de Losango'
 id: 4vfoIULHTs8S9t3WDyldCE
 status: PUBLISHED
 createdAt: 2020-11-23T20:29:21.353Z
-updatedAt: 2023-03-30T15:42:27.683Z
-publishedAt: 2023-03-30T15:42:27.683Z
+updatedAt: 2024-01-23T18:47:11.153Z
+publishedAt: 2024-01-23T18:47:11.153Z
 firstPublishedAt: 2020-11-23T21:04:18.389Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
index dd59caa7e..6686a9908 100644
--- a/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
@@ -45,7 +45,7 @@ Aquí, la propiedad común de los clientes será que también son empleados de l
 En este artículo se asume que los empleados están debidamente registrados con un campo booleano `isEmployee` establecido como true en sus respectivos documentos para la entidad de datos CL, como se muestra en la siguiente imagen.
 
 Si no lo están, revise el artículo [Crear un campo en Master Data](https://help.vtex.com/es/tutorial/how-can-i-create-field-in-master-data) para crear un campo que identifique a los empleados y configurarlo adecuadamente para cada documento correspondiente a los mismos.
-![Campo empleado](https://images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/a66c5d5bdd16ae4152d7f07b1483d5f2/Campo_empleado.png)
+![Campo empleado](//images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/a66c5d5bdd16ae4152d7f07b1483d5f2/Campo_empleado.png)
 
 <div class="alert alert-info" role="alert">Hay muchos detalles para configurar completamente una promoción. Si necesita información adicional sobre este asunto, consulte el artículo <a href="https://help.vtex.com/es/tutorial/creating-promotions-2">Crear promociones</a>.</div>
 
@@ -59,5 +59,5 @@ Con el campo configurado, la promoción puede crearse siguiendo los siguientes p
 6. En el campo inferior a **Clúster de clientes**, ingrese el clúster que identifica que los clientes son empleados (un par `{field}={value}`). En este caso, se usa `isEmployee=true` .
 7. Al final de la página, haga clic en **Guardar**.
 
-Después de esta configuración, la promoción ya debería estar funcionando como fue configurada. El descuento se muestra solo en el carrito de compra. La siguiente imagen muestra un ejemplo con 99% de descuento. ![Carrito con descuento](https://images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/856ec8d08b57e045760ad5e2eb76efa3/Carrinho_com_desconto.png)
+Después de esta configuración, la promoción ya debería estar funcionando como fue configurada. El descuento se muestra solo en el carrito de compra. La siguiente imagen muestra un ejemplo con 99% de descuento. ![Carrito con descuento](//images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/856ec8d08b57e045760ad5e2eb76efa3/Carrinho_com_desconto.png)
 
diff --git a/docs/tutorials/es/configure-payment-with-pix-at-nubank.md b/docs/tutorials/es/configure-payment-with-pix-at-nubank.md
index c462dc127..f2b1f6147 100644
--- a/docs/tutorials/es/configure-payment-with-pix-at-nubank.md
+++ b/docs/tutorials/es/configure-payment-with-pix-at-nubank.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Pix en Nubank'
 id: 2pJBJdtkvyn645rL2sxyJy
 status: PUBLISHED
 createdAt: 2022-07-19T16:38:08.465Z
-updatedAt: 2023-03-24T15:03:05.135Z
-publishedAt: 2023-03-24T15:03:05.135Z
+updatedAt: 2024-01-23T19:11:23.258Z
+publishedAt: 2024-01-23T19:11:23.258Z
 firstPublishedAt: 2022-07-19T16:56:30.888Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/configure-payment-with-shopfacil.md b/docs/tutorials/es/configure-payment-with-shopfacil.md
new file mode 100644
index 000000000..77e1ad4bc
--- /dev/null
+++ b/docs/tutorials/es/configure-payment-with-shopfacil.md
@@ -0,0 +1,18 @@
+---
+title: 'Configurar pago con ShopFácil'
+id: 4v3z3CLrgZ2bByMx7uoMeG
+status: PUBLISHED
+createdAt: 2023-07-14T16:49:07.504Z
+updatedAt: 2024-01-23T21:31:46.325Z
+publishedAt: 2024-01-23T21:31:46.325Z
+firstPublishedAt: 2023-07-14T16:57:55.320Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-shopfacil
+locale: es
+legacySlug: configurar-pago-con-shopfacil
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+<div class="alert alert-warning" role="alert">Este es un contenido exclusivo regional no aplicable a los países de habla hispana.</div>
diff --git a/docs/tutorials/es/configure-seller-regionalization.md b/docs/tutorials/es/configure-seller-regionalization.md
index fa8b9690e..c109dae29 100644
--- a/docs/tutorials/es/configure-seller-regionalization.md
+++ b/docs/tutorials/es/configure-seller-regionalization.md
@@ -3,8 +3,8 @@ title: 'Configurar la regionalización del seller'
 id: 32t6wLpQCEnumoh8TjT5fw
 status: PUBLISHED
 createdAt: 2022-08-26T13:58:10.648Z
-updatedAt: 2022-08-26T18:34:14.924Z
-publishedAt: 2022-08-26T18:34:14.924Z
+updatedAt: 2023-07-17T12:11:40.614Z
+publishedAt: 2023-07-17T12:11:40.614Z
 firstPublishedAt: 2022-08-26T18:34:14.924Z
 contentType: tutorial
 productTeam: Shopping
@@ -41,7 +41,7 @@ Con el uso de **Region**, si el cliente inicia sesión en la tienda durante el p
 Para activar **Region** en tu tienda, debes realizar los siguientes pasos:
 
 1. [Configurar el precio y la disponibilidad de SKUs por Region](https://help.vtex.com/es/tutorial/configurar-el-precio-y-la-disponibilidad-de-skus-por-region--12ne58BmvYsYuGsimmugoc#)
-2. [Habilitar la funcionalidad Region](https://developers.vtex.com/vtex-rest-api/docs/how-to-configure-region-feature-sku)
+2. [Habilitar la funcionalidad Region](https://developers.vtex.com/docs/guides/enable-the-region-for-skus)
 
 <div class="alert alert-info">
   Actualmente, el <b>Region</b> está disponible para su uso en todas las tiendas VTEX en v2. Obtenga más información en <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
diff --git a/docs/tutorials/es/configure-template-in-smartcheckout-update.md b/docs/tutorials/es/configure-template-in-smartcheckout-update.md
index 898bc3354..024966ca5 100644
--- a/docs/tutorials/es/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/es/configure-template-in-smartcheckout-update.md
@@ -37,11 +37,11 @@ Cada sitio registrado corresponde a un multidominio (si la cuenta tiene multidom
 
 Creación del nuevo sitio web: 
 
-![ses.smartchackout1](https://images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) 
+![ses.smartchackout1](//images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) 
 
 Acceso a __Nombre de cuenta__:
 
-![ses.smartchackout2](https://images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
+![ses.smartchackout2](//images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
 
 ## Editar y configurar sitio
 
@@ -56,14 +56,14 @@ Acceso a __Nombre de cuenta__:
    - __Páginas__: mostrar páginas existentes para el sitio. 
 
 Ejemplo de sitios existentes en la misma cuenta:
-![ES Cards Portal](https://images.ctfassets.net/alneenqid6w5/lHivoZotqDLXjLShaqv2i/a60e8f0fba49b962fd33f6d56652bec7/ES_Cards_Portal.png)
+![ES Cards Portal](//images.ctfassets.net/alneenqid6w5/lHivoZotqDLXjLShaqv2i/a60e8f0fba49b962fd33f6d56652bec7/ES_Cards_Portal.png)
 
 Si desea __eliminar__ un sitio web, haga clic en el botón Eliminar del sitio web deseado, como en el siguiente ejemplo:
-![ses.smartchackout3](https://images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
+![ses.smartchackout3](//images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
 
 Si desea __eliminar__ una página existente, haga clic en el botón indicado en la imagen de abajo:
 
-![ses.smartchackout5](https://images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
+![ses.smartchackout5](//images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
 
 A continuación, pasaremos a la configuración paso a paso de las opciones del menú: __Código__ y __Checkout__ - pues configuran las páginas de *Checkout* y *Order Placed*.
 
@@ -80,7 +80,7 @@ A continuación, pasaremos a la configuración paso a paso de las opciones del m
   <li><b>Cálculo de las Opciones de Entrega (Beta y Stable)</b>: seleccione si el cálculo del flete se hará desde la hoja de cálculo o por geolocalización.</li>
   </ul>
 
-![ses.smartchackout6](https://images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
+![ses.smartchackout6](//images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
 
 ## Configurar código
 
@@ -90,7 +90,7 @@ A continuación, pasaremos a la configuración paso a paso de las opciones del m
 
 Ejemplo:
 
-![ses.smartchackout7](https://images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
+![ses.smartchackout7](//images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
 
 ### Configurar templates del menú "Código"
 
@@ -110,27 +110,27 @@ A continuación se muestran ejemplos de cómo se pueden llenar los códigos pres
 
 - Template __checkout-header__ y la cabecera de página del sitio web:
 
-![ses.smartchackout10](https://images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) 
+![ses.smartchackout10](//images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) 
 
-![checkout-header-page-es](https://images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/d98e30e3889f5c94d509c6c3cf4c586e/smartcheckout11.pt.png)
+![checkout-header-page-es](//images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/d98e30e3889f5c94d509c6c3cf4c586e/smartcheckout11.pt.png)
 
 - Template __checkout-footer__ y pie de página del sitio web:
 
-![checkout-footer-codigo-pt](https://images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
+![checkout-footer-codigo-pt](//images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
 
-![checkout-footer-cesta-es](https://images.ctfassets.net/alneenqid6w5/4P9DSkLsgPN8F2x5JM1dQM/b71853e444095cbacba1b45a6f6110b6/checkout_footer_cesta.es.png)
+![checkout-footer-cesta-es](//images.ctfassets.net/alneenqid6w5/4P9DSkLsgPN8F2x5JM1dQM/b71853e444095cbacba1b45a6f6110b6/checkout_footer_cesta.es.png)
 
 - Template __vtex-checkout__ y página de carrito al finalizar la compra:
 
-![smartcheckout16.pt](https://images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
+![smartcheckout16.pt](//images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
 
-![vtex-checkout-pagina-es](https://images.ctfassets.net/alneenqid6w5/6yT3yPkqatyVRLQ4Cn0TVb/643e0bc15c803d5d50053e7eabc2fb29/ses.smartchackout17.png)
+![vtex-checkout-pagina-es](//images.ctfassets.net/alneenqid6w5/6yT3yPkqatyVRLQ4Cn0TVb/643e0bc15c803d5d50053e7eabc2fb29/ses.smartchackout17.png)
 
 - Template __vtex-orderPlaced__ y página de pedido confirmado:
 
-![ses.smartchackout18](https://images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) 
+![ses.smartchackout18](//images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) 
 
-![vtex-orderplaced-paginas-es](https://images.ctfassets.net/alneenqid6w5/2gFpnjs8tsTfOvmAgKQ3hh/8adc2c384b5ed34fbc5b02a82850c03e/ses.smartchackout19.png)
+![vtex-orderplaced-paginas-es](//images.ctfassets.net/alneenqid6w5/2gFpnjs8tsTfOvmAgKQ3hh/8adc2c384b5ed34fbc5b02a82850c03e/ses.smartchackout19.png)
 
 ### Cuentas con multidominio 
 
diff --git a/docs/tutorials/es/configure-template-in-the-smartcheckout.md b/docs/tutorials/es/configure-template-in-the-smartcheckout.md
index f41c49da4..89828722b 100644
--- a/docs/tutorials/es/configure-template-in-the-smartcheckout.md
+++ b/docs/tutorials/es/configure-template-in-the-smartcheckout.md
@@ -32,7 +32,7 @@ Ahora, rellene los campos abajo siguiendo las instrucciones:
 
 Vea imagen abajo:
 
-![ses.smartchackout1](https://images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) ![ses.smartchackout2](https://images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
+![ses.smartchackout1](//images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) ![ses.smartchackout2](//images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
 
 Haga clic em Salvar para concluir el registro del nuevo sitio.
 
@@ -47,17 +47,17 @@ Como se indica en la próxima imagen, al hacer clic en el nombre del Sitio, el s
 - Código: Templates relacionados al sitio
 - Páginas: Exhibe las páginas que existen para el sitio: De modo estándar, se crean dos páginas, **checkout **y **checkout/orderPlaced**. Como fue dicho, al inicio de este post, la página** checkout **corresponde a las páginas de carrito, datos personales, dirección y forma de pago. La página **checkout/orderPlaced** corresponde a la página de Confirmación de Compra
 
-![ses.smartchackout3](https://images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
+![ses.smartchackout3](//images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
 
 En** Páginas** es posible **Crear** nuevas páginas, **Editar** y **Excluir** páginas existentes. Vea las dos imágenes siguientes demostrando **Edición** y **Exclusión**. La creación sigue las mismas reglas de edición.
 
 Edición de página:
 
-![ses.smartchackout4](https://images.ctfassets.net/alneenqid6w5/RtUdwXSva1HNq5LO4MMxN/726dacd630de7e3ec6372238b020b0a8/ses.smartchackout4.png)
+![ses.smartchackout4](//images.ctfassets.net/alneenqid6w5/RtUdwXSva1HNq5LO4MMxN/726dacd630de7e3ec6372238b020b0a8/ses.smartchackout4.png)
 
 Exclusión de Página:
 
-![ses.smartchackout5](https://images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
+![ses.smartchackout5](//images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
 
 En **Checkout** podemos editar los campos abajo:
 
@@ -68,39 +68,39 @@ En **Checkout** podemos editar los campos abajo:
 
 Sigue imagen con ejemplos de cómo rellenar este formulário:
 
-![ses.smartchackout6](https://images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
+![ses.smartchackout6](//images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
 
 En **Código**, se exhibirán a la derecha todos los templates relacionados al Sitio. Como estándar, el sistema configura los templates que figuran como ejemplo en la imagen abajo:
 
-![ses.smartchackout7](https://images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
+![ses.smartchackout7](//images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
 
 De esos templates, los únicos que no pueden modificarse son **vtex-checkout **e **vtex-orderPlaced**. Esos templates corresponden al funcionamiento nativo de la plataforma, o sea, son los que renderizan el contenido principal de esas páginas, tanto el checkout como el orderPlaced.
 
 En la siguiente imagen, demostramos el área afatada en el checkout por la configuración del template **checkout-footer**. Este es sólo un ejemplo de template vacío.
 
-![ses.smartchackout8](https://images.ctfassets.net/alneenqid6w5/5xl9GdBzkLtWnJJXurEDuF/9c3d6c2c0499727c315aff8e085481d1/ses.smartchackout8.png) ![ses.smartchackout9](https://images.ctfassets.net/alneenqid6w5/4bcDYXgUTPhSTEs98ptJe1/b807afcb4bf3eeb63d754646f074b321/ses.smartchackout9.png)
+![ses.smartchackout8](//images.ctfassets.net/alneenqid6w5/5xl9GdBzkLtWnJJXurEDuF/9c3d6c2c0499727c315aff8e085481d1/ses.smartchackout8.png) ![ses.smartchackout9](//images.ctfassets.net/alneenqid6w5/4bcDYXgUTPhSTEs98ptJe1/b807afcb4bf3eeb63d754646f074b321/ses.smartchackout9.png)
 
 En la próxima imagen, tenemos un ejemplo equivalente al anterior, pero, esta vez, con código HTML rellenado. Note que el código rellenado a la izquierda corresponde al área superior de la derecha. Ese es el template** checkout-header**.
 
-![ses.smartchackout10](https://images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) ![ses.smartchackout11](https://images.ctfassets.net/alneenqid6w5/3rQkwWZiERd3L9Js6DqHoj/5f724a23f6951f069f368b346ff7c206/ses.smartchackout11.png)
+![ses.smartchackout10](//images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) ![ses.smartchackout11](//images.ctfassets.net/alneenqid6w5/3rQkwWZiERd3L9Js6DqHoj/5f724a23f6951f069f368b346ff7c206/ses.smartchackout11.png)
 
 Como podemos ver en la próxima imagen, todos los templates que tengan el prefijo** checkout **se usarán en todas las páginas del Checkout. En este ejemplo ya estamos en la página Forma de Pagamento y note que el header cargado es el mismo del ejemplo anterior.
 
-![ses.smartchackout12](https://images.ctfassets.net/alneenqid6w5/3xZgBYnuTjYcwQDop5eYxT/f2120bdf05a5883ee11d91f7c308a41e/ses.smartchackout12.png) ![ses.smartchackout13](https://images.ctfassets.net/alneenqid6w5/2PZAzsLIwAp1wL6YiXuidN/913d83cb447406bd2597029808818880/ses.smartchackout13.png)
+![ses.smartchackout12](//images.ctfassets.net/alneenqid6w5/3xZgBYnuTjYcwQDop5eYxT/f2120bdf05a5883ee11d91f7c308a41e/ses.smartchackout12.png) ![ses.smartchackout13](//images.ctfassets.net/alneenqid6w5/2PZAzsLIwAp1wL6YiXuidN/913d83cb447406bd2597029808818880/ses.smartchackout13.png)
 
 Como en los templates del **checkout**, lo mismo ocurre con los templates de orderPlaced. O sea, los templates con prefijo **orderPlaced** corresponden solamente a la página OrderPlaced (Confirmación de Compra).
 
-![ses.smartchackout14](https://images.ctfassets.net/alneenqid6w5/4EfbPzpvD6Buwn71HNchoC/7437e0cf4506f83c59587511f78f6d39/ses.smartchackout14.png) ![ses.smartchackout15](https://images.ctfassets.net/alneenqid6w5/5XEhlCcJKuXETy1z5P2cMu/aa70c832db354d9f4060e0771efeafcc/ses.smartchackout15.png)
+![ses.smartchackout14](//images.ctfassets.net/alneenqid6w5/4EfbPzpvD6Buwn71HNchoC/7437e0cf4506f83c59587511f78f6d39/ses.smartchackout14.png) ![ses.smartchackout15](//images.ctfassets.net/alneenqid6w5/5XEhlCcJKuXETy1z5P2cMu/aa70c832db354d9f4060e0771efeafcc/ses.smartchackout15.png)
 
 Como se ha explicado arriba, los únicos templates en que no se permiten modificaciones son **vtex-checkout** y **vtex-orderPlaced**. Esos templates renderizan al contenido básico de las páginas Checkout y OrderPlaced. A continuación, ejemplos del contenido renderizado por los templates.
 
 Template **vtex-checkout**:
 
-![ses.smartchackout16](https://images.ctfassets.net/alneenqid6w5/6YRb9FuRRmLJStVlx6giuY/40569c34738b82ccf51296f6dbf92272/ses.smartchackout16.png) ![ses.smartchackout17](https://images.ctfassets.net/alneenqid6w5/4vYztmiow2QijU3rPh9tET/77bfd5e4bea43fc71657f44b3cbb46bf/ses.smartchackout17.png)
+![ses.smartchackout16](//images.ctfassets.net/alneenqid6w5/6YRb9FuRRmLJStVlx6giuY/40569c34738b82ccf51296f6dbf92272/ses.smartchackout16.png) ![ses.smartchackout17](//images.ctfassets.net/alneenqid6w5/4vYztmiow2QijU3rPh9tET/77bfd5e4bea43fc71657f44b3cbb46bf/ses.smartchackout17.png)
 
 Template **vtex-orderPlaced**:
 
-![ses.smartchackout18](https://images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) ![ses.smartchackout19](https://images.ctfassets.net/alneenqid6w5/1Atqv6If7ZP9N5PgrYZlMH/8f38382856a04c34d6cc6570e7f55797/ses.smartchackout19.png)
+![ses.smartchackout18](//images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) ![ses.smartchackout19](//images.ctfassets.net/alneenqid6w5/1Atqv6If7ZP9N5PgrYZlMH/8f38382856a04c34d6cc6570e7f55797/ses.smartchackout19.png)
 
 Las cuentas que tengan multi dominio pueden usar sólo un sitio, si no hay necesidad de configuraciones específicas. Esto porque, aunque existe sólo un Sitio, la plataforma incluye una clase en la tag "body" de acuerdo al dominio accedido. Así, es sencillo aplicar layouts diferentes para el mismo sitio.
 
diff --git a/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md b/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md
index ddf000ef1..28f89f5e8 100644
--- a/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md
+++ b/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md
@@ -33,7 +33,7 @@ Después de determinar el descuento en Checkout, se debe vincular el SKU al medi
 3. Haga clic en el template de su página de producto en la lista de templates.
 4. En la propiedad `skuPrice`, añada la variable `paymentSystemId` con el ID del medio de pago deseado. 
 
-![Screenshot 2020-12-18 Crear precio al contado](https://images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
+![Screenshot 2020-12-18 Crear precio al contado](//images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
 
 6. Luego, haga clic en __Save Template__ en el campo superior, para guardar la alteración.
 
diff --git a/docs/tutorials/es/configuring-a-marketplace-trade-policy.md b/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
index 639439c8d..60a12ba75 100644
--- a/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar política comercial para marketplace'
 id: tutorials_404
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T22:06:38.350Z
-updatedAt: 2022-12-08T17:30:09.288Z
-publishedAt: 2022-12-08T17:30:09.288Z
+updatedAt: 2024-06-14T14:19:35.130Z
+publishedAt: 2024-05-15T00:18:56.253Z
 firstPublishedAt: 2017-04-27T23:03:23.796Z
 contentType: tutorial
 productTeam: Channels
@@ -30,21 +30,23 @@ Vea cómo se pueden configurar las políticas comerciales en los siguientes mód
 
 Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)* seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`.
 
-La contratación de políticas comerciales adicionales para integración con un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), un [conector certificado (partner)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX está exenta de la cuota mensual.
+La contratación de políticas comerciales adicionales para integración con un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), un [conector certificado](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX está exenta de la cuota mensual.
+
+<div class=alert alert-warning> Si se aplica la misma política comercial a un conector certificado y a un conector asociado, no hay exención de tarifas.</div>
 
 ## Configuración de la tienda 
 La creación de una nueva política comercial es el primer paso para definir las condiciones aplicadas a cada *marketplace* en el que opera un *seller*. Los *sellers* pueden crear múltiples políticas comerciales o pueden aplicar la misma política en más de un *marketplace*. 
 
 Esta configuración se realiza en el módulo «Configuración de la tienda», en la página «Políticas comerciales». Debe crear [una nueva política comercial](https://help.vtex.com/es/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) cuando la configuración de catálogo, precios, promociones, logística y pagos sean diferentes entre los *marketplaces* en que los *sellers* venden sus productos. 
 
-![ES Add Politica comercial](https://images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e6ae3d0e4f32b580ebda4800b173e981/ES_Add_Politica_comercial.jpg)
+![ES Add Politica comercial](//images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e6ae3d0e4f32b580ebda4800b173e981/ES_Add_Politica_comercial.jpg)
 
 ## Gestión de pedidos
 Después de crear una política comercial, debe asociarla a cada *marketplace* en que el *seller* venda productos al registrar [afiliados](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). Así es como los *sellers* identifican la política comercial que opera en cada *marketplace*. Si su tienda vende productos en tres *marketplaces* diferentes, deberá crear tres afiliados, cada uno de los cuales representará un *marketplace*. 
 
 Esto se hace en la página *Configuración* del módulo *Gestión de pedidos* de su tienda al registrar afiliados. Incluso si crea varias, es importante tener en cuenta que solamente se aplicará una política comercial a la vez en el *marketplace*. 
 
-![PT Afiliado](https://images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/0db945d3f87f491d66023b8cd25c2c03/PT_Afiliado.jpg)
+![PT Afiliado](//images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/0db945d3f87f491d66023b8cd25c2c03/PT_Afiliado.jpg)
 
 *En el ejemplo anterior, el afiliado «Amazon» está vinculado a la política comercial «1».* 
 
@@ -58,7 +60,7 @@ La configuración se realiza en el módulo *Promociones* en todas las [promocion
 
 Si no selecciona ninguna política comercial, la promoción estará disponible en todos los canales de venta.
 
-![ES Promoções Politica Comercial](https://images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/b1ff93abd371c23100c5447f48ed1452/ES_Promo____es_Politica_Comercial.jpg)
+![ES Promoções Politica Comercial](//images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/b1ff93abd371c23100c5447f48ed1452/ES_Promo____es_Politica_Comercial.jpg)
 
 *En el ejemplo anterior, la promoción solo se aplicará a los pedidos de las políticas comerciales «Marketplace-BRL» y «Argentina-ARS», donde la tienda opera como seller. La promoción no estará disponible en el storefront de VTEX.* 
 
@@ -67,7 +69,7 @@ Los *sellers* que tramitan el pago de las ventas de sus productos en un *marketp
 
 La configuración se realiza en el módulo *Pagos* al [crear una condición especial](https://help.vtex.com/es/tutorial/condicoes-especiais--tutorials_456) y asociarla a las políticas comerciales deseadas. Si no establece ninguna restricción, la política comercial se aplicará a todos los canales de venta. 
 
-![ES Pagamento Politica comercial](https://images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/0873eeb5985892804d08ad32da2c0ef4/ES_Pagamento_Politica_comercial.jpg)
+![ES Pagamento Politica comercial](//images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/0873eeb5985892804d08ad32da2c0ef4/ES_Pagamento_Politica_comercial.jpg)
 
 *En el ejemplo anterior, el plazo de pago está asociado a la política comercial «Marketplace». Esto hace que la condición de pago esté disponible solo en los canales de venta asociados a esta política comercial.*
 
@@ -80,7 +82,7 @@ Esta configuración se realiza en el módulo *Catálogo*, al [registrar producto
   No recomendamos vincular políticas comerciales a colecciones para determinar el surtido de productos, especialmente para los marketplaces fuera de VTEX. Cuando se elimina un producto de la colección de políticas comerciales, el sistema VTEX no notifica al marketplace de esta actualización, lo que hace que el producto continúe disponible en el marketplace.
   </div>
 
-[![ES Catalogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/7be99b14d44e2f31d29e740e71954830/ES_Catalogo_Politica.jpg)
+[![ES Catalogo Politica](//images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/7be99b14d44e2f31d29e740e71954830/ES_Catalogo_Politica.jpg)
 
 *En el ejemplo anterior, el producto solo estará disponible para los canales de venta que utilicen las políticas comerciales «Carrefour» y «Marketplace».* 
 
@@ -92,7 +94,7 @@ Esta configuración se realiza en el módulo *Precios* mediante políticas comer
 - [Reglas de precio](https://help.vtex.com/es/tutorial/configurar-regra-de-preco-para-politica-comercial--5LQMLwcUcEGCWK6SMI6cEM): para determinar un *markup* para categorías y marcas específicas;
 - [Precios fijos](https://help.vtex.com/es/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy): para diferenciar precios en productos específicos.
 
-![ES Regra de preço](https://images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/29127a3e4000ccab87c352d3f1366d88/ES_Regra_de_pre__o.jpg)
+![ES Regra de preço](//images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/29127a3e4000ccab87c352d3f1366d88/ES_Regra_de_pre__o.jpg)
 
 *En el ejemplo anterior, la regla de precios aplicó un *markup* a la política comercial «Marketplace» para los productos de la categoría «Fera-Fashion».* 
 
@@ -102,10 +104,10 @@ Los *sellers* pueden configurar [rutas logísticas](https://help.vtex.com/es/tra
 
 Ambas configuraciones se realizan en el módulo *Estrategia de envío*. Al crear un [muelle](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj), debe indicar las políticas comerciales a las que servirá. Esto hace que las políticas de envío que estén asociadas a ese muelle estén disponibles para las políticas comerciales vinculadas. Luego, debe asociar el [stock](https://help.vtex.com/es/tutorial/gerenciar-estoque) deseado a un muelle para que el inventario esté disponible para las políticas comerciales asociadas a ese muelle. 
 
-![ES Doca Politica](https://images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/3e55a5e475674fd88cbf71df09daaca7/ES_Doca_Politica.jpg)
+![ES Doca Politica](//images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/3e55a5e475674fd88cbf71df09daaca7/ES_Doca_Politica.jpg)
 *En el ejemplo anterior, el muelle está asociado a la política comercial «Marketplace», que recibirá servicio de la transportadora «Transportadora A».*
 
-![ES Estoque Politica](https://images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/152ee7c4c467347a3276be98cd2c55f6/ES_Estoque_Politica.jpg)
+![ES Estoque Politica](//images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/152ee7c4c467347a3276be98cd2c55f6/ES_Estoque_Politica.jpg)
 *En el ejemplo anterior, el stock está asociadao al "Muelle A", por lo que este será el *stock* que utilizarán las políticas comerciales vinculadas al "Muelle A".* 
 
 ## Integraciones
@@ -113,7 +115,7 @@ Las políticas comerciales también se aplican a todas las integraciones en las
 
 Las [integraciones](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#vender-em-marketplace) se realizan en la página *Configuración* del módulo *Integraciones*. Cada canal suele requerir condiciones comerciales específicas, aunque es posible que diferentes canales compartan la misma política comercial. 
 
-![ES Integracao Politica](https://images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/46985758c94413183a675ee1993162f8/ES_Integracao_Politica.jpg)
+![ES Integracao Politica](//images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/46985758c94413183a675ee1993162f8/ES_Integracao_Politica.jpg)
 *En el ejemplo anterior, la política comercial «Marketplace» se aplica a la integración con Google Shopping.*
 
 ## Sepa más
diff --git a/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md b/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md
index 8c31d014d..615c68be9 100644
--- a/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md
+++ b/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md
@@ -3,8 +3,8 @@ title: 'Configurar regla de precio para política comercial'
 id: 5LQMLwcUcEGCWK6SMI6cEM
 status: PUBLISHED
 createdAt: 2018-03-19T17:49:25.791Z
-updatedAt: 2023-03-29T20:00:47.266Z
-publishedAt: 2023-03-29T20:00:47.266Z
+updatedAt: 2023-08-21T17:23:00.178Z
+publishedAt: 2023-08-21T17:23:00.178Z
 firstPublishedAt: 2018-03-19T18:26:04.279Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,7 +25,7 @@ Por estándar, el __precio base__ registrado para un producto se aplica a todas
 
 Para crear una regla de precio específica para una política comercial, siga estos pasos:
 
-1. En el Admin VTEX, accede a *Precios > Reglas de precios* , o escribe *Reglas de precios* en la barra de búsqueda en la parte superior de la página.
+1. En el Admin VTEX, accede a **Precios > Reglas de precios** , o escribe **Reglas de precios** en la barra de búsqueda en la parte superior de la página.
 2. Haga clic en `Nueva regla`.
 3. En el campo __Política comercial__, elija la política comercial deseada.
 4. Seleccione si la regla se aplicará a __todos los productos__ de esta política o __solo en las marcas y categorías elegidas__.
diff --git a/docs/tutorials/es/configuring-a-registered-boleto.md b/docs/tutorials/es/configuring-a-registered-boleto.md
index 7457be24b..02fe08de9 100644
--- a/docs/tutorials/es/configuring-a-registered-boleto.md
+++ b/docs/tutorials/es/configuring-a-registered-boleto.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto registrado (método de pago brasileño)'
 id: frequentlyAskedQuestions_2867
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:46:00.197Z
-updatedAt: 2020-11-24T13:14:10.947Z
-publishedAt: 2020-11-24T13:14:10.947Z
+updatedAt: 2024-03-18T18:09:27.673Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:08:27.705Z
 contentType: tutorial
 productTeam: Financial
@@ -26,22 +26,13 @@ VTEX se adecuó a esta determinación y, actualmente, ya existen algunas maneras
 - [Boleto Santander](https://help.vtex.com/es/tutorial/configurar-boleto-registrado-santander--67siNqkC7mcgy2GWUYimaa)
 - [Boleto Itaú](https://help.vtex.com/es/tutorial/configurar-boleto-registrado-itau-itau-registrado--6MEHf1oDTOkuWM2CaYi4gu)
 - [Itaú Shopline](https://help.vtex.com/es/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq)
-- [Bradesco Registrado](https://help.vtex.com/es/tutorial/configurar-boleto-registrado-bradesco--bbnXBjvKOkWYiOosmASiA)
+- [Boleto Bradesco Registrado](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-bradesco--bbnXBjvKOkWYiOosmASiA)
 
-Además, VTEX tiene integración automática para boletos registrados Bradesco e Itaú Shopline. Sin embargo, para los boletos generados sin una adquirencia, la conciliación se realiza a través de un archivo (.RET).
+Además, VTEX tiene integración automática para boletos registrados Bradesco y Itaú Shopline. Sin embargo, para los boletos generados sin una adquirencia, la conciliación se realiza a través de un archivo (.RET).
 
 Cada cliente debe obtener los archivos de sus respectivos bancos. En este caso específico, Itaú Registrado y Santander. Hacemos hincapié en que estos archivos deben seguir necesariamente el estándar establecido por Febraban - Federación Brasileña de Bancos.
 
-Para otros bancos es necesario usar uno de los siguientes gateways de pago:
-
-- Braspag
-- PagSeguro Transparente
-- Mundipagg
-- Moip
-- MercadoPago Transparente
-- Pagar.Me
-- CieloV3
-- Adyen
+Para otros bancos, debe utilizar una de los gateways disponibles en el Admin de su tienda (por ejemplo, Braspag, PagSeguro Transparente, CieloV3, entre otras).
 
 Los costos del boleto registrado son diferentes a los del boleto tradicional y varían de acuerdo con su negociación con el banco. Preste atención para planificar y controlar su margen.
 
@@ -56,5 +47,4 @@ La creación de este número por VTEX garantiza la particularidad de cada boleto
 ## Artículos relacionados
 
 - [Cómo configurar afiliaciones de Gateway](/es/tutorial/afiliaciones-de-gateway)
-- [Cómo configurar PagSeguro transparente](/es/tutorial/como-configurar-el-pagseguro-sin-redirect/)
-- [Configurar boleto registrado Itaú](/es/tutorial/configurar-boleto-registrado-itau)
+
diff --git a/docs/tutorials/es/configuring-a-santander-registered-boleto.md b/docs/tutorials/es/configuring-a-santander-registered-boleto.md
index 522025170..c3e4174a1 100644
--- a/docs/tutorials/es/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/es/configuring-a-santander-registered-boleto.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto registrado Santander '
 id: 67siNqkC7mcgy2GWUYimaa
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-12-04T19:04:02.215Z
-updatedAt: 2023-03-30T16:12:20.970Z
-publishedAt: 2023-03-30T16:12:20.970Z
+updatedAt: 2024-03-18T18:03:25.298Z
+publishedAt: 
 firstPublishedAt: 2019-01-25T17:15:35.225Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/configuring-affiliates.md b/docs/tutorials/es/configuring-affiliates.md
index af4e784ec..90503988a 100644
--- a/docs/tutorials/es/configuring-affiliates.md
+++ b/docs/tutorials/es/configuring-affiliates.md
@@ -3,8 +3,8 @@ title: 'Configurar afiliado'
 id: tutorials_187
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:31.422Z
-updatedAt: 2023-03-29T18:05:11.905Z
-publishedAt: 2023-03-29T18:05:11.905Z
+updatedAt: 2024-01-08T18:13:15.897Z
+publishedAt: 2024-01-08T18:13:15.897Z
 firstPublishedAt: 2017-04-27T23:00:46.992Z
 contentType: tutorial
 productTeam: Channels
@@ -15,9 +15,9 @@ legacySlug: como-configurar-afiliado
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-Solo es necesario hacer el registro de un afiliado si actúa como seller de un marketplace, ya que el seller crea el código del afiliado para identificar el marketplace.
+En VTEX, el [afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) es un código que identifica el marketplace para el seller. El [seller VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#como-seller-vtex) necesita configurar un código de afiliado para poder integrarse con un [marketplace VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex), y esta configuración solo es necesaria cuando el mercado integrado y el vendedor son ambos tiendas VTEX.
 
-Esta configuración solo debe ser hecha para integraciones en que el marketplace y el seller son tiendas VTEX o [cuando el marketplace no es tienda VTEX y no tiene configuración por el módulo de Integraciones.](/es/tutorial/integrando-con-marketplace/). En estos casos, el afiliado es creado automáticamente.
+Cuando el marketplace no es una tienda VTEX (como en las [integraciones externas](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-externo)), o cuando la tienda se integra con un [marketplace certificado](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-certificado) (como Amazon o Mercado Livre), la plataforma crea automáticamente el código de afiliado.
 
 ## Cómo configurar
 
diff --git a/docs/tutorials/es/configuring-banners.md b/docs/tutorials/es/configuring-banners.md
new file mode 100644
index 000000000..38f7dec6d
--- /dev/null
+++ b/docs/tutorials/es/configuring-banners.md
@@ -0,0 +1,70 @@
+---
+title: 'Configurar Banners'
+id: 3AdnZhxAhgmlxJjpa02Svc
+status: PUBLISHED
+createdAt: 2024-06-27T16:32:24.435Z
+updatedAt: 2024-06-27T16:33:49.674Z
+publishedAt: 2024-06-27T16:33:49.674Z
+firstPublishedAt: 2024-06-27T16:33:39.573Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configurar-banners
+locale: es
+legacySlug: configurar-banners
+subcategory: z6qcw06Z38YDu1fOcu9Jn
+---
+
+Para configurar un banner, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Storefront** 
+2. Haz clic en **Banners**.
+3. Haz clic en <i class="fas fa-plus"></i> `Nuevo`.
+4. Rellena los [campos relativos al banner](#campos-de-registro-del-banner).
+5. Para terminar, haz clic en `Guardar`.
+
+Después de configurar el banner, debes agregarlo a una página de tu tienda. Para ello, sigue los pasos del artículo [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner).
+
+<div class="alert alert-info">
+<p> Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configuración Multidioma (Beta)</a>para saber más.</p>
+</div>
+
+![banner-form-es](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
+
+## Campos de registro del banner
+
+Para registrar el banner, debes rellenar los siguientes campos:
+
+### Información general
+
+  * **Nombre:** nombre del banner registrado.
+  * **Posición:** zona en la que aparecerá el banner en la página de resultados de la búsqueda. Los banners se pueden colocar en cuatro zonas distintas de la página web. La disposición depende del administrador de la tienda y será determinada por la opción seleccionada en este campo o definida a través de los blocks en store-theme.
+
+### Tipo
+
+* **Tipo de banner:** contenido del banner que se creará. El banner puede ser un HTML o una URL de imagen:
+  * **HTML:** el administrador puede agregar medios, vídeos de YouTube, imágenes o líneas de código, como JavaScript, en el campo HTML.
+  * **Imagen:** el sistema pide la URL de la imagen que se utilizará y el link de destino del banner.
+    * URL de la imagen
+    * Link de destino
+* **Zona horaria:** zona horaria para las horas configuradas en el banner.
+* **Fecha de inicio:** fecha en la que el banner comenzará a estar disponible.
+* **Hora de inicio:** hora en la que el banner comenzará a estar disponible.
+* **Fecha de fin:** fecha en la que el banner dejará de estar disponible. Esto permite al administrador programar futuras campañas, lo que facilita su control.
+* **Hora de fin:** hora en la que el banner dejará de estar disponible.
+* **Idiomas:** idiomas en los que se aplicará el banner. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+### Reglas de activación
+
+**Reglas de activación** son un conjunto de condiciones de términos o filtros que se aplicarán a cada búsqueda realizada. Es necesario tener al menos una condición registrada, ya sea por término o por filtro.
+
+Haz clic en <i class="fa-solid fa-link"></i> `Autocompletar desde URL` para agregar la URL de la página de búsqueda donde se aplicarán las reglas de activación.
+
+![banner-url-es](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
+
+Haz clic en <i class="fas fa-plus"></i> `Agregar condición` para crear una regla. Pueden ser de los siguientes tipos:
+
+* **Término:** palabra buscada por el cliente que estará relacionada con la regla.
+* **Filtro:** atributo seleccionable ya definido que restringe los resultados de la búsqueda. Puedes seleccionar categorías, departamentos y subcategorías.
+
+Haz clic en `Limpiar reglas` para borrar todas las reglas registradas.
diff --git a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
new file mode 100644
index 000000000..ab0909160
--- /dev/null
+++ b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -0,0 +1,68 @@
+---
+title: 'Configurar la importación en masa de datos de organizaciones y centros de costos'
+id: 41FwcZHF3GctzKcgyKGaoF
+status: PUBLISHED
+createdAt: 2024-04-25T11:45:15.945Z
+updatedAt: 2024-05-21T14:04:56.238Z
+publishedAt: 2024-05-21T14:04:56.238Z
+firstPublishedAt: 2024-04-29T18:38:46.485Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configurar-la-importacion-en-masa-de-datos-de-organizaciones-y-centros-custo
+locale: es
+legacySlug: configurar-la-importacion-en-masa-de-datos-de-organizaciones-y-centros-custo
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+La importación de datos en masa simplifica el proceso de actualización y mantenimiento de información para organizaciones compradoras y sus usuarios (miembros) y centros de costo.
+
+<div class="alert alert-warning">
+Antes de configurar la funcionalidad de importación en masa, necesitas tener la aplicación <a href="https://developers.vtex.com/docs/apps/vtex.b2b-suite">B2B Suite</a> instalada en tu tienda.
+</div>
+
+Para importar los datos en masa a la plataforma VTEX, sigue los pasos a continuación:
+
+1.	En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones**, o ingresa **Organizaciones** en la barra de búsqueda de la parte superior de la página.
+
+2.	En la pestaña Organizaciones, haz clic en **Nuevo** y luego en Importar en masa. Haz clic en el botón Cargar y selecciona tu archivo **XLSX**, o arrastra y suelta el archivo a la área punteada. El tamaño del archivo importado debe ser menor que 50 MB.
+
+<div class = "alert alert-info">
+Puedes bajar un archivo de plantilla haciendo clic en VTEX file template en la parte inferior de la ventana de importación y rellenar los datos.
+</div>
+
+<ol start="3">
+	<li>Después de que la plataforma realice la verificación del archivo de importación y no encuentre errores, haz clic en Importar.</li>
+</ol>
+
+<div class = "alert alert-info">
+  Si la plataforma detecta algún error, consulta la sección <b>Errores de importación</b>.
+</div>
+
+<ol start="4">
+	<li>Una vez finalizado el proceso de importación, puedes hacer clic en Ver detalles de la importación para acceder al informe de importación.</li>
+</ol>
+
+![Importação em massa - ES](//images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/b8c5a8462d5e9f330a9601975ef2fca9/Bulk_import_vers_o_original-gif-ES.gif)
+
+# Errores de importación
+
+Durante el proceso de importación, el sistema comprobará si hay errores en el archivo. Si se producen errores, se te notificará por email y recibirás una alerta en la pantalla.
+
+Para ver los detalles de los problemas encontrados, sigue los pasos a continuación:
+
+1. Haz clic en Ver detalles de la importación y accede al informe de errores correspondiente.
+
+2. Descarga la plantilla revisada haciendo clic en **Bajar XLSX revisado**, que muestra las celdas con error.
+
+3. Después de corregir los errores, puedes reiniciar el proceso de importación cargando el archivo corregido nuevamente.
+
+<div class = "alert alert-info">
+Asegúrate de que el archivo que cargues solo contenga las correcciones de los errores previamente identificados para garantizar que la importación se realice correctamente.
+</div>
+
+![Bulk import - ES](//images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/2cdc7eb8e0710fff44a55b1a2619c58b/Bulk_import_vers_o_error-gif-ES.gif)
+
+# Importación vía API
+
+También se pueden importar los datos a través de la API de [Bulk Import](https://developers.vtex.com/docs/api-reference/buyer-organizations?endpoint=overview), que permite validar e importar archivos, dar seguimiento al progreso y ver el resultado de la importación.
diff --git a/docs/tutorials/es/configuring-cargo-splitting.md b/docs/tutorials/es/configuring-cargo-splitting.md
index c72c13df6..58b052b2b 100644
--- a/docs/tutorials/es/configuring-cargo-splitting.md
+++ b/docs/tutorials/es/configuring-cargo-splitting.md
@@ -3,8 +3,8 @@ title: 'Cómo se maneja el reparto de carga'
 id: tutorials_109
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:24.631Z
-updatedAt: 2023-03-28T14:07:28.837Z
-publishedAt: 2023-03-28T14:07:28.837Z
+updatedAt: 2024-04-30T14:30:11.052Z
+publishedAt: 2024-04-30T14:30:11.052Z
 firstPublishedAt: 2017-04-27T23:00:42.951Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,16 +15,15 @@ legacySlug: como-se-maneja-el-reparto-de-carga
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
+El reparto de carga es la configuración que permite que se divida una compra en varias entregas cuando el cálculo total de peso sobrepasa el límite de la política de envío.
 
-El reparto de carga es la configuración que permite que se divida una compra en varias entregas cuando el cálculo total de peso sobrepasa el límite del transportista.
+No tener esta configuración puede imposibilitar el cierre de una compra, pues, caso la suma del peso de los productos del carrito sea mayor que el límite máximo de peso catastrado en las políticas de envío, no será posible la finalización de la compra.
 
-Y esa configuración puede imposibilitar el cierre de una compra. Pues, caso la suma del peso de todos los productos del carrito sea mayor que el límite máximo de peso catastrado en los transportistas, no será posible la finalización de la compra.
-
-![divisao-carga-desenho es](https://images.ctfassets.net/alneenqid6w5/13LOZvGLCCIm8YKSg2oeiI/186189daff4771ee6368096b8d267394/divisao-carga_es.png)
+![divisao-carga-desenho es](//images.ctfassets.net/alneenqid6w5/13LOZvGLCCIm8YKSg2oeiI/186189daff4771ee6368096b8d267394/divisao-carga_es.png)
 
 ### Cómo configurar el reparto de carga
 
 1. En el Admin VTEX, accede a **Configuración de la tienda > Envío > Configuración**, o escribe *Envío* en la barra de búsqueda en la parte superior de la página, y haga clic en *Configuración de la tienda / Envío*.      
-2. En el área **Dividir la carga cuando llegue al límite de la transportadora**, seleccione la opción de *Sí, permitir la compra con entregas divididas.*. 
+2. En el área **Dividir la carga cuando llegue al límite de la transportadora**, seleccione la opción de *Sí, permitir la compra con entregas divididas*. 
 3. Haga clic en **Guardar**.  
 
diff --git a/docs/tutorials/es/configuring-cielo-acquirer.md b/docs/tutorials/es/configuring-cielo-acquirer.md
index 5020f3195..dabf8bf03 100644
--- a/docs/tutorials/es/configuring-cielo-acquirer.md
+++ b/docs/tutorials/es/configuring-cielo-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar adquirente Cielo'
 id: 3avjZ7q65WcM02K8K0eeWu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-05-02T19:02:05.427Z
-updatedAt: 2023-03-21T18:55:28.551Z
-publishedAt: 2023-03-21T18:55:28.551Z
+updatedAt: 2023-09-19T14:27:20.410Z
+publishedAt: 
 firstPublishedAt: 2018-05-02T19:49:35.201Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
index 3929e3a13..c9a2a432b 100644
--- a/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
@@ -78,7 +78,7 @@ Para configurar ClearSale Global, deberá:
 <br>  
   <ui>11. En la esquina superior derecha, hacer clic en <b>Publicar</br>.</ui>
 
-![Fingerprint ClearSalve_Pantalla](https://images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/2f5d30cbf3147be7da09d3f86186dafc/Fingerprint_ClearSalve_Pantalla.png)
+![Fingerprint ClearSalve_Pantalla](//images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/2f5d30cbf3147be7da09d3f86186dafc/Fingerprint_ClearSalve_Pantalla.png)
 
 Para más detalles sobre el código introducido en Google Tag Manager, recomendamos leer [esta documentación](https://api.clearsale.com.br/docs/behavior-analytics) de ClearSale.
 
diff --git a/docs/tutorials/es/configuring-clearsale-v3-antifraud.md b/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
index b3a85476d..50b09a38d 100644
--- a/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar antifraude ClearSale v3'
 id: 2pPORygesIqQOa6cIG6agg
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-10-30T14:10:20.822Z
-updatedAt: 2021-12-15T21:23:21.984Z
-publishedAt: 2021-12-15T21:23:21.984Z
+updatedAt: 2024-04-24T18:52:20.944Z
+publishedAt: 2024-04-24T18:49:44.223Z
 firstPublishedAt: 2017-10-30T14:26:53.089Z
 contentType: tutorial
 productTeam: Financial
@@ -15,22 +15,32 @@ legacySlug: configurar-antifraude-clearsale-v3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Para habilitar el antifraude ClearSale v3, debes [añadir la afiliación de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444) en la sección de Pagos eligiendo la opción **ClearSaleV3**. La configuración de la afiliación de ClearSale v3 contiene los siguientes campos:
+En VTEX es posible integrarse con el [antifraude](https://help.vtex.com/es/tutorial/como-configurar-antifraude--tutorials_446) ClearSaleV3. A través de este sistema es posible aumentar el nivel de seguridad en las transacciones de pago realizadas en tu tienda mediante análisis de riesgos que identifican posibles fraudes.
+
+Para configurar ClearSaleV3 siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __ClearSaleV3__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagoEfectivoV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+5. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+6. Complete la siguiente información de acuerdo con su configuración de ClearSale:
+<br>
+<ul>
+<br>
+  <li><b>Login</b>: login.</li>
+  <li><b>Password</b>: contraseña.</li>
+  <li><b>SLA personalizado en minutos (opcional)</b>: período en el que ClearSale tendrá que procesar el análisis de fraude.</li>
+  <li><b>Producto (opcional)</b>: valor numérico. Corresponde al ID del producto contratado en ClearSale.</li>
+  <li><b>Transaction currency</b>: moneda en la que se realiza la transacción.</li>
+  <li><b>Observation (opcional)</b>: texto abierto para enviar a ClearSale como nota.</li>
+  <li><b>¿Enviar transacciones autenticadas?</b>: indica si las transacciones de pago deben autenticarse con una contraseña en el programa 3DSecure.</li>
+</ul>
+7. Haga clic en `Guardar`.
 
-- **Login**: Login.
-- **Password**: Contraseña.
-- **Custom SLA en minutos** (opcional):  Número de minutos que ClearSale tendrá para procesar el análisis de fraude.
-- **Producto** (opcional): Valor numérico. Corresponde al ID del producto contratado en la clearsale.
-- **Transaction currency**: Moneda.
-- **Observation** (opcional): Texto abierto para enviar a ClearSale como nota.
-- **Enviar transacciones autenticadas?**: Tiene las opciones **Sí** y **No**. Las transacciones autenticadas son aquellas con pagos verificados con una contraseña usando el programa 3DSecure.
-
-<div class = "alert alert-info">
-La documentación de ClearSale acerca de <a href="https://api.clearsale.com.br/docs/finger-print" target="_blank"> FingerPrint </a> explica en detalle el script de abajo.
-</div>
-
-<div class="alert alert-warning">
-Si desea configurar el antifraude <strong>ClearSale T</strong>, siga este <a href="http://help.vtex.com/es/tutorial/como-configurar-antifraude">paso a paso</a>.
+<div class="alert alert-info">
+<p>Si tiene una aplicación móvil que utiliza API de VTEX en el momento del pago, es necesario implementar la recolección de datos de huellas dactilares para enviarlos a Clearsale, según la plataforma utilizada por la aplicación. Obtenga más información en <a href="https://api.clearsale.com.br/docs/behavior-analytics" target="_blank">Clearsale Behavior Analytics</a>.</p>
+  <p>Con la implementación del SDK es necesario recolectar el valor de <span class="bg-muted-4">sessionId</span> y enviarlo en el <span class="bg-muted-4">deviceFingerprint</span> a través de la <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">API al momento de crear el pago</a>.</p>  
 </div>
 
 ## Creación de la etiqueta de Google Tag Manager
diff --git a/docs/tutorials/es/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md b/docs/tutorials/es/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
index 5e4ae6900..57974054f 100644
--- a/docs/tutorials/es/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
+++ b/docs/tutorials/es/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
@@ -3,8 +3,8 @@ title: 'Configurar descuento de precio al contado para Google Shopping'
 id: 40K3R5d4NogMvCzIWdWt3e
 status: PUBLISHED
 createdAt: 2020-12-18T19:17:16.033Z
-updatedAt: 2023-03-30T16:56:23.457Z
-publishedAt: 2023-03-30T16:56:23.457Z
+updatedAt: 2024-01-19T16:37:47.493Z
+publishedAt: 2024-01-19T16:37:47.493Z
 firstPublishedAt: 2021-05-04T20:06:46.945Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,7 +25,12 @@ Para configurar el descuento de precio al contado para Google Shopping es necesa
 4. Haga clic en el template de su página de producto en la lista de templates.
 5. En el componente `richSnippets`, debe añadir el parámetro `paymentSystemId` con el valor del medio de pago deseado.
 
-![Screenshot 2020-12-18 Crear precio al contado para Google Shopping](https://images.ctfassets.net/alneenqid6w5/3cZKIpG2uAhDmFTJDslHZk/1bd7628049b5c5b7326df8044ac673f2/Screenshot_2020-12-18_Criar_pre__o____vista_para_Google_Shopping.png)
+```
+<body id="product-page">
+    <!--  Component: richSnippets -->
+    <vtex.cmc:productRichSnippets showGoogle="1" paymentSystemId="6"/>
+    <!-- /Component: richSnippets -->
+```
 
 6. Después, haga clic en __Save Template__ en el campo superior, para guardar la alteración.
 
diff --git a/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md b/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md
index 3af89df97..65986e287 100644
--- a/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md
+++ b/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md
@@ -35,7 +35,7 @@ La utlización de esas variables en los Layouts de email poseen la siguiente sin
 **HTML del template**
 `<strong>{{_accountInfo.HostName}}</strong> => lojavirtual`
 
-![exemplohtml](https://images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
+![exemplohtml](//images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
 
 El ejemplo arriba puede tener diferentes valores cuando se comparan Sellers y Marketplaces.
 
diff --git a/docs/tutorials/es/configuring-kushki-gateway.md b/docs/tutorials/es/configuring-kushki-gateway.md
index 1f1823e68..b6088b5da 100644
--- a/docs/tutorials/es/configuring-kushki-gateway.md
+++ b/docs/tutorials/es/configuring-kushki-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway Kushki'
 id: 69VC8nQMkEE0yu8oIyG2wG
 status: PUBLISHED
 createdAt: 2018-04-24T15:50:00.468Z
-updatedAt: 2023-03-29T00:41:16.269Z
-publishedAt: 2023-03-29T00:41:16.269Z
+updatedAt: 2024-01-23T17:48:58.465Z
+publishedAt: 2024-01-23T17:48:58.465Z
 firstPublishedAt: 2018-04-24T19:47:19.057Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,20 @@ legacySlug: configurar-gateway-kushki
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Kushki es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) con certificación [PCI](/es/faq/que-es-el-pci-ssc) que opera enfocado en América Latina.
+Kushki es un [gateway](https://help.vtex.com/es/tutorial/que-es-un-gateway-de-pagos--2KH9Wdi7F6swOU4amECSOk) con certificación [PCI](https://help.vtex.com/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E) que opera enfocado en América Latina.
 
 Para configurar Kushki, siga estos pasos:
 
-## Configurar la afiliación de gateway Kushki
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Kushkiv2__.
-4. Rellene los campos con los datos proporcionados por Kushki.
-5. El campo __appKey__ debe rellenarse con la __clave privada__ de Kushki.
-6. El campo __appToken__ debe rellenarse con la __clave pública__ de Kushki.
-7. Para guardar, haga clic en el botón __Salva__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Kushkiv2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En los campos __Clave de aplicación__ y __Token de aplicación__, ingrese la información proporcionada por Kushki.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor iugu en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Haga clic en `Guardar`.
 
-Después de finalizar esta configuración, usted tiene que crear las credenciales de VTEX para configurar la afiliacón Kushki en su tienda. Para más detalles, consulte la [guía de autenticación](https://developers.vtex.com/docs/getting-started-authentication "guía de autenticación") en el Portal del Desarrollador.  
+Para configurar los métodos de pago a procesar por Liquido Payment, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
-## Configurar la condición de pago
-Luego de realizar los ajustes anteriores, Kushki estará configurada en su tienda. Por lo tanto, cuando registre una condición de pago estará disponible en el campo __Proceso con la afiliación__ (cuando el medio de pago sea compatible con Kushki). Para saber cómo definir las condiciones de pago, acceda a [este artículo](/es/tutorial/condiciones-de-pago).
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Kushki puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/configuring-login-with-facebook-and-google.md b/docs/tutorials/es/configuring-login-with-facebook-and-google.md
index 3752d156b..e325ab6ac 100644
--- a/docs/tutorials/es/configuring-login-with-facebook-and-google.md
+++ b/docs/tutorials/es/configuring-login-with-facebook-and-google.md
@@ -3,42 +3,51 @@ title: 'Configurar inicio de sesión con Facebook y Google'
 id: tutorials_513
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:01.743Z
-updatedAt: 2023-02-08T14:32:57.255Z
-publishedAt: 2023-02-08T14:32:57.255Z
+updatedAt: 2023-10-20T19:35:59.221Z
+publishedAt: 2023-10-20T19:35:59.221Z
 firstPublishedAt: 2017-04-27T23:03:27.844Z
 contentType: tutorial
 productTeam: Identity
 author: authors_84
-slug: integracion-google-y-facebook-en-smartcheckout
+slug: configurar-inicio-de-sesion-con-facebook-y-google
 locale: es
 legacySlug: integracion-google-y-facebook-en-smartcheckout, configurar-login-con-facebook-y-google
 subcategory: 14V5ezEX0cewOMg0o0cYM6
 ---
 
-En VTEX, no se necesita crear una cuenta o iniciar sesión para realizar una compra. Sin embargo, si el cliente quiere efectuar alguna alteración en los datos informados durante la primera compra, debe comprobar la propiedad del correo electrónico que proporcionó.
+En VTEX, no es necesario crear una cuenta o iniciar sesión para realizar una compra. Sin embargo, si el cliente desea editar la información proporcionada en su primera compra, deberá verificar su email.
 
-De forma nativa, la plataforma ofrece opciones de inicio de sesión mediante correo electrónico y contraseña o un código de acceso enviado al correo electrónico del cliente. También ofrece integraciones nativas con Google y Facebook, que son opcionales y deben ser configuradas.
+El comportamiento nativo de la plataforma es ofrecer opciones de inicio de sesión con email y contraseña y con código de acceso al email del cliente. También ofrecemos integraciones opcionales nativas con Google y Facebook que requieren configuración. Esta guía explica los pasos para configurar los proveedores de inicio de sesión:
 
-## Realice el registro con los proveedores
+1. [Obtener credenciales de los proveedores](#obtener-credenciales-de-los-proveedores)
+2. [Configurar inicio de sesión con los proveedores](#configurar-inicio-de-sesion-con-los-proveedores)
+3. [Validar la configuración](#validar-la-configuracion)
 
-Antes de configurar nuestra integración de inicio de sesión con Google o Facebook, necesita crear credenciales de OAuth 2.0 (protocolo utilizado para la integración) en estos servicios. Para realizar esto, siga las instrucciones indicadas en los siguientes artículos: 
+## Obtener credenciales de los proveedores
 
-- [Facebook](/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-facebook)
-- [Google](/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google)
+Antes de configurar nuestra integración de inicio de sesión con Google y Facebook, se deben crear credenciales de OAuth 2.0 (protocolo para la integración) en esos servicios. Para obtenerlas, sigue las instrucciones en los artículos a continuación:
 
-## Configure en su tienda
+- [Facebook](https://help.vtex.com/es/tutorial/cadastrar-client-id-e-client-secret-para-login-com-facebook)
+- [Google](https://help.vtex.com/es/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google)
 
-Después de la configuración en Facebook y/o Google, es necesario configurar la opción de inicio de sesión mediante estos proveedores en su tienda VTEX. En ambos casos, debe tener a la mano el 'Client ID' y el 'Client Secret' registrados. 
+## Configurar inicio de sesión con los proveedores
 
-1. Acceda al módulo de VTEX ID por el panel de administración de su tienda en el menú Configuración de la Cuenta > Autenticación;
-  ![Lista Autenticación](https://images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/d63b5b6892d8e1dfd756e2977ea753b4/autenticacao_ES.png)
-2. Seleccione el proveedor y haga clic en **EDITAR**;
-3. Complete el formulario ingresando el `Client ID` y el `Client Secret` registrados;
-  ![Facebook OAuth ES](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/ffc13a1eb81a285feea15e78a72342b9/facebook_ES.png)
-4. Active la utilización del proveedor mediante el interruptor.  
-  ![Lista Autenticación Switch On Highlight](https://images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/7567505995ce1af975d6b5c69159a323/switch_On_highlight_ES.png)
+Después de realizar la configuración en Facebook y Google, debes configurar la opción de inicio de sesión mediante el proveedor deseado en el Admin VTEX. En ambos casos, debes tener listos el `Client ID` y el `Client Secret` proporcionados por los proveedores.
 
-## Valide la configuración
+1. En la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** que tiene la inicial de tu email.
+2. Haz clic en **Configuración de la cuenta > Autenticación**.
 
-Después de realizar todos los ajustes anteriores, puede probar su configuración. Recomendamos que haga esto accediendo a la URL final que sus usuarios utilizarán para ingresar a su tienda. Al intentar iniciar sesión, las opciones referentes a los proveedores activos deben estar disponibles y el proceso se debe efectuar sin ningún problema. 
+  Se te redirigirá a la pestaña **Tienda virtual** de la página **Autenticación**, que lista los métodos de inicio de sesión disponibles en tu tienda.
 
+  ![Lista Autenticación](//images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/814b27712f00a7a00bcc3c717a3aee5f/autenticacao-es.png)
+3. En la fila del proveedor de inicio de sesión deseado, haz clic en `Configurar`.
+4. Rellena el formulario con el `Client ID` y el `Secreto del cliente` registrados en la [etapa anterior](#obtener-credenciales-de-los-proveedores) y haz clic en `Guardar`.
+
+  ![Facebook OAuth ES](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/e85e70614c1ff706937104c8f5ec917c/1-login-fb-es.PNG)
+5. En la página **Autenticación**, activa el uso del proveedor haciendo clic en el botón de alternancia. 
+
+  ![Lista Autenticación Switch On Highlight](//images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/7567505995ce1af975d6b5c69159a323/switch_On_highlight_ES.png)
+
+## Validar la configuración
+
+Después de completar la configuración en el Admin VTEX, recomendamos probar el inicio de sesión con el proveedor a través de la URL final que tus usuarios utilizarán para acceder a la tienda. Al probar el inicio de sesión, se mostrarán las opciones de los proveedores activos.
diff --git a/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
index faadeb13e..838917b43 100644
--- a/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -58,7 +58,7 @@ Para configurar esta liquidación, siga los pasos a continuación:
 8. En el campo __Captura anticipada__, seleccione una de las opciones de tiempo disponibles. 
 9. Rellene el  campo __Cambiar el tiempo máximo de captura automática__ con el periodo acordado con el adquirente. __Si usted prefiere dejar el campo en blanco, se utilizará el estándar de 4 días.__
 
-![captura_automatica_ES](https://images.ctfassets.net/alneenqid6w5/4jX317pC0aLgMXygXxd1XU/6a7d21e16d4ef26e0076ad7b641e877f/image.png)
+![captura_automatica_ES](//images.ctfassets.net/alneenqid6w5/4jX317pC0aLgMXygXxd1XU/6a7d21e16d4ef26e0076ad7b641e877f/image.png)
 10. Haga clic en el __botón Salva__ para guardar.
 
 De esta manera, se implementará el nuevo recurso de liquidación.
diff --git a/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
index 56f548b03..8cc4b8229 100644
--- a/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
@@ -63,13 +63,13 @@ Para asegurarse de que este recurso funciona, es necesario revisar los detalles
 4. En la siguiente página, haga clic en __+Información__.
 5. Al hacer clic en __+Información__, busque el campo __deviceFingerprint__ y verifique si el  código disponible inicia con la palabra __armor__, según el siguiente ejemplo. 
 
-![Device Fingerprint Armor](https://images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/ea05aa211a85d6731b7eb6308ebfd192/DEVICEFINGERPRINTARMOR.png)
+![Device Fingerprint Armor](//images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/ea05aa211a85d6731b7eb6308ebfd192/DEVICEFINGERPRINTARMOR.png)
 
 <ui>
 6. Después de confirmar que la información es correcta, el paso final para la verificación deDevice Fingerprint es enviar el ID de la transacción al equipo de Mercado Pago. Este ID puede encontrarse en el campo <b>authorizationConnectorResponse</b>, en el detalle de la transacción.
   </ui>
 
-  ![Autorización](https://images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/5c71d9b8d1eed010b71ddb838fd47f19/AUTHORIZATION.png)
+  ![Autorización](//images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/5c71d9b8d1eed010b71ddb838fd47f19/AUTHORIZATION.png)
 
 <ui>
   7. Copie el ID y <a href=https://www.mercadopago.com.ar/developers/es/support>envíe un email</a> a Mercado Pago con esta información y pídales que validen la transacción. De esta manera, Mercado Pago podrá evaluar si el Dispositivo Fingerprint está funcionando correctamente.
diff --git a/docs/tutorials/es/configuring-my-account-conversational-commerce.md b/docs/tutorials/es/configuring-my-account-conversational-commerce.md
index eb25d30b9..8c16a6bf4 100644
--- a/docs/tutorials/es/configuring-my-account-conversational-commerce.md
+++ b/docs/tutorials/es/configuring-my-account-conversational-commerce.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar Mi cuenta (Conversational Commerce)'
 id: 42bnIdyC2c5dwz9KKT0UKc
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-07T19:10:12.107Z
-updatedAt: 2023-03-07T20:00:20.806Z
-publishedAt: 2023-03-07T20:00:20.806Z
+updatedAt: 2024-01-05T16:28:41.167Z
+publishedAt: 
 firstPublishedAt: 2023-03-07T19:58:45.529Z
 contentType: tutorial
 productTeam: Shopping
@@ -24,7 +24,7 @@ subcategory: 5bBAgUbHdh6ovdZ4kGsN7O
 
 ## Campos de configuración de conversación
 
-![my account - conversational commerce - ES](https://images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/78adcfa1fc6e5d221e9bcd57aee82a28/image.png)
+![my account - conversational commerce - ES](//images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/78adcfa1fc6e5d221e9bcd57aee82a28/image.png)
 
 - **Idioma: **el idioma predeterminado para los mensajes del bot con los clientes en VTEX Conversational Commerce. Campo obligatorio.
 
diff --git a/docs/tutorials/es/configuring-openpay-payment-gateway.md b/docs/tutorials/es/configuring-openpay-payment-gateway.md
index 275b3b492..90079881f 100644
--- a/docs/tutorials/es/configuring-openpay-payment-gateway.md
+++ b/docs/tutorials/es/configuring-openpay-payment-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar el gateway Openpay'
 id: 5vGj3UIFCU4GFFqVBlYKW2
 status: PUBLISHED
 createdAt: 2021-07-06T17:31:51.598Z
-updatedAt: 2021-07-06T18:01:16.234Z
-publishedAt: 2021-07-06T18:01:16.234Z
+updatedAt: 2024-01-25T18:44:58.747Z
+publishedAt: 2024-01-25T18:44:58.747Z
 firstPublishedAt: 2021-07-06T17:54:12.638Z
 contentType: tutorial
 productTeam: Financial
@@ -25,7 +25,7 @@ Para configurar Openpay, necesitará:
 
 1. [Configurar Google Tag Manager](#configurar-google-tag-manager)
 2. [Configurar Openpay](#configurar-openpay)
-3. [Asociar una condición de pago a Openpay](#asociar-una-condicion-de-pago)
+3. [Configurar condiciones de pago](#configurar-condiciones-de-pago)
 
 ## Configurar Google Tag Manager
 
@@ -35,19 +35,20 @@ Al terminar, continúe con el siguiente paso de configuración de Openpay en el
 
 ## Configurar Openpay 
 
-Después de crear y activar el tag en Google Tag Manager, debe instalar el conector de Openpay en su tienda. Siga los pasos a continuación:
+Después de crear y activar el tag en Google Tag Manager, debe instalar el proveedor de Openpay en su tienda. Siga los pasos a continuación:
 
-1. Acceda al __Admin__ de VTEX.
-2. En el módulo __Pagos__, haga clic en __Configuración__.
-3. En __Afiliaciones__, haga clic en el botón verde «__+__».
-4. Busque y haga clic en __Openpay__.
-5. En __Nombre de la afiliación__, ingrese __Openpay__.
-6. Rellene los campos __Application Key__ y __Application Token__. [Haga clic aquí](https://www.openpay.mx/en/docs/vtex.html) para acceder a la documentación de Openpay y ver las instrucciones que explican cómo obtener esta información.
-7. Haga clic en __Salvar__ para guardar los cambios.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Openpay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Nombre de la afiliación__, ingrese __Openpay__.
+5.  Rellene los campos __Application Key__ y __Application Token__. [Haga clic aquí](https://www.openpay.mx/en/docs/vtex.html) para acceder a la documentación de Openpay y ver las instrucciones que explican cómo obtener esta información.
+6.  Haga clic en `Salvar`.
 
-## Asociar una condición de pago
+## Configurar condiciones de pago
 
-Después de completar todos los pasos, la configuración de Openpay estará lista.
+Para configurar los métodos de pago a procesar por Openpay, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
-Si desea asociarlo a una condición de pago compatible con Openpay, siga el artículo [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento).
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Openpay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
 
diff --git a/docs/tutorials/es/configuring-payment-conditions-for-b2b.md b/docs/tutorials/es/configuring-payment-conditions-for-b2b.md
new file mode 100644
index 000000000..05102e499
--- /dev/null
+++ b/docs/tutorials/es/configuring-payment-conditions-for-b2b.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurar condiciones de pago B2B'
+id: 6NMeukzx5H7n1YaePPS7pr
+status: PUBLISHED
+createdAt: 2024-07-25T16:31:16.186Z
+updatedAt: 2024-07-25T17:07:27.442Z
+publishedAt: 2024-07-25T17:07:27.442Z
+firstPublishedAt: 2024-07-25T17:07:27.442Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configurar-condiciones-de-pago-b2b
+locale: es
+legacySlug: configurar-condiciones-de-pago-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+En una operación B2B, las [condiciones de pago](https://help.vtex.com/es/tutorial/how-to-configure-payment-conditions--tutorials_455?&utm_source=autocomplete) se asignan a la organización compradora. Las elecciones que realices determinarán las opciones de pago disponibles para los usuarios de la organización durante el checkout.
+
+Los usuarios con rol de administrador de la organización pueden personalizar por centro de costos las opciones de pago disponibles.
+
+<div class = "alert alert-info">
+Cuando configuras una condición de pago en el módulo de Pagos, se mostrará como un medio de pago en la sección <b>Disponible</b> dentro de la pestaña <b>Condiciones de pago</b>. Para acceder a esta sección solo tienes que hacer clic en el nombre de la organización. Los medios de pago listados son aquellos que ya están asignados a la organización.
+</div>
+
+## Asociar condiciones de pago a la organización
+Para asociar una condición de pago con una organización de compras sigue las instrucciones a continuación:
+
+1. En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones**, o ingresa **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de información de la organización.
+3. En la página de información de la organización, haz clic en la pestaña **Condiciones de pago**.
+4. En la sección **Disponible**, marca las opciones de pago que desees y haz clic en `Agregar a la org.`. 
+5. Haz clic en `Guardar` en la esquina superior derecha de la página.
+
+## Remover asociación de condiciones de pago
+Sigue las instrucciones a continuación para desasociar las condiciones de pago de una organización compradora:
+
+1. En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones**, o ingresa **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de información de la organización.
+3. En la página de información de la organización, haz clic en la pestaña **Condiciones de pago**.
+4. Selecciona las opciones deseadas de la lista **Asignado a la organización** y haz clic en `Remover de la organización`.
+5. Haz clic en `Guardar` en la esquina superior derecha de la página.
+
diff --git a/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index af99580a6..5eca3a143 100644
--- a/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Configurar pagos con AdyenV3 en VTEX Sales App'
 id: 24yO6KloBn6DN6CbprHtgt
 status: PUBLISHED
 createdAt: 2023-05-09T14:12:03.567Z
-updatedAt: 2023-06-01T11:38:18.504Z
-publishedAt: 2023-06-01T11:38:18.504Z
+updatedAt: 2024-07-26T16:55:23.474Z
+publishedAt: 2024-07-26T16:55:23.474Z
 firstPublishedAt: 2023-05-11T20:30:50.460Z
 contentType: tutorial
 productTeam: Financial
@@ -51,12 +51,16 @@ Para habilitar el acceso de VTEX en el entorno Adyen, sigue los pasos a continua
 2. En la barra lateral izquierda, copia y guarda la información descrita antes de **Company**. Esta es tu Company Account.
 3. En la lista de abajo, busca el nombre de la Merchant Account a utilizar (resaltada en blanco). Copia y guarda esta información.
 
-![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtener la POS Live URL
 
+Esta información hace referencia a los endpoints utilizados por las API de terminales de Adyen en un entorno productivo. Para obtener más información, vaya a [documentación Adyen](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api#cloud).
+
+### Obtener la Live URL prefix
+
 1. En la barra lateral, accede a **Developers > API URLs**.
-2. Haz clic en `Copy` en el campo **Point of Sale** y anota la información guardada en un lugar seguro.
+2. Haz clic en `Copy` en el campo **Prefix** y anota la información guardada en un lugar seguro. Este prefijo controla su terminal en la plataforma Adyen.
 
 ### Obtener la API Key
 
@@ -66,7 +70,7 @@ La información a continuación supone que la API Key se ha generado previamente
 2. Selecciona tu credencial API.
 3. En **Server Settings > Authentication**, selecciona **API key**. 
 
-![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Haz clic en <b>Generate Key</b> y anota la información creada en un lugar seguro.</ui>
 
@@ -82,7 +86,7 @@ Configura el webhook según los pasos a continuación:
 4. En **General > Description**, agrega una descripción para el nuevo webhook. Ejemplo: "Webhook Adyen Connector Provider v3".
 5. En **General > Server configuration > URL**, introduce la URL de tu cuenta VTEX. Ejemplo https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Haz clic en <b>Apply</b>.</ui>
 
@@ -90,11 +94,11 @@ Configura el webhook según los pasos a continuación:
 
 <blockquote><ui>8. Haz clic en <b>Save changes</b>.</ui>
 
-![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
@@ -102,22 +106,19 @@ Si tienes varias tiendas, es necesario configurar el webhook para cada una de el
 
 ## Configurar el conector AdyenV3 (VTEX Sales App) en VTEX
 
-1. En el Admin VTEX, ve a **Configuración de la tienda > Pagos > Configuración**, o ingresa **Configuración** en la barra de búsqueda situada en la parte superior de la página.
-2. En la pestaña **Afiliaciones de gateway**, haz clic en el botón `+`.
-3. Haz clic en el conector **AdyenV3**.
-4. Rellena los siguientes campos con tus datos de Adyen:
-    - **Application Key**: el nombre de tu Adyen Merchant Account (paso 3 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account).
-    - **Application Token**: API Key (paso 4 de la sección [Obtener la API Key](#obtener-la-api-key)).
-    - **Live URL prefix**: no es necesario rellenar este campo (solo aplicable a otros canales de venta online).
-    - **Company account**: el nombre de tu company account (paso 2 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account)).
-    - **Live POS URL**: URL prefix (paso 2 de la sección [Obtener la POS Live URL](#obtener-la-pos-live-url). 
-    - **Client key**: no es necesario rellenar este campo (solo aplicable a otros canales de venta online).
-
-<blockquote><ui>  5. Si aparece un mensaje de alerta indicando la necesidad de instalar la aplicación, haz clic en el botón <b>Instalar aplicación</b> y sigue las instrucciones para hacerlo.</ui>
-
-<blockquote><ui>  6. Haz clic en <b>Guardar</b>.</ui>
-
-![Adyenv3_9](https://images.ctfassets.net/alneenqid6w5/SCflCIOFcwFro09YTxEZy/27b941b772a6afb021d0fa2fe25c9fa9/Adyenv3_9.PNG)
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __AdyenV3__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Clave de aplicación__, el nombre de tu Adyen Merchant Account (paso 3 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account).
+5. En __Token de aplicación__, ingrese la clave API (paso 4 de la sección [Obtener la API Key](#obtener-la-api-key)).
+6. Si desea modificar el nombre de identificación que se mostrará para el proveedor AdyenV3 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+7. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+8. En __Live URL prefix__, complete el prefijo disponible en el área de clientes de Adyen (paso 2 de la sección [Obtener la Live URL prefix](#obtener-la-live-url-prefix)).
+9. En __Company account__, ingrese el nombre de tu company account (paso 2 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account)).
+10. En __Live POS URL__, complete los endpoints utilizados para acceder a las API de terminales de Adyen. Obtenga más información en [documentación de Adyen] (https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api#cloud).
+11. No es necesario rellenar el campo __Client key__, ya que sólo es aplicable a otro tipo de canales de venta online.
+12. En __Auto Capture Settings__, seleccione cuándo desea capturar el pago.
+13. Haga clic en `Guardar`.  
 
 ## Configurar condición de pago
 
diff --git a/docs/tutorials/es/configuring-payment-with-adyenv3.md b/docs/tutorials/es/configuring-payment-with-adyenv3.md
index e195a2cb6..bd4d4f466 100644
--- a/docs/tutorials/es/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/es/configuring-payment-with-adyenv3.md
@@ -3,8 +3,8 @@ title: 'Configurar pagos con AdyenV3'
 id: 7xAz67E2Eg63LWCQNjVdwv
 status: PUBLISHED
 createdAt: 2023-05-08T20:00:38.610Z
-updatedAt: 2023-05-31T19:42:52.614Z
-publishedAt: 2023-05-31T19:42:52.614Z
+updatedAt: 2024-06-25T21:10:30.984Z
+publishedAt: 2024-06-25T21:10:30.984Z
 firstPublishedAt: 2023-05-11T20:32:21.638Z
 contentType: tutorial
 productTeam: Financial
@@ -39,15 +39,15 @@ Para habilitar el acceso de VTEX en el entorno Adyen, sigue los pasos a continua
 ### Obtener las credenciales Company y Merchant Account 
 
 1. Accede a tu [Área de Cliente](https://ca-test.adyen.com/) en Adyen.
-2. En la barra lateral izquierda, copia y guarda la información descrita antes de **Company**. Esta es tu Company Account.
+2. En la barra lateral izquierda, copia y guarda la información descrita antes de __Company__. Esta es tu Company Account.
 3. En la lista de abajo, busca el nombre de la Merchant Account a utilizar (resaltada en blanco). Copia y guarda esta información.
 
-![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtener la Live URL
 
-1. En la barra lateral, accede a **Developers > API URLs**.
-2. Haz clic en `Copy` en el campo **Prefix** y anota la información guardada en un lugar seguro.
+1. En la barra lateral, accede a __Developers > API URLs__.
+2. Haz clic en `Copy` en el campo __Prefix__ y anota la información guardada en un lugar seguro.
 
 ### Obtener la API Key y la Client Key
 
@@ -55,11 +55,11 @@ Para habilitar el acceso de VTEX en el entorno Adyen, sigue los pasos a continua
 La información a continuación supone que la API Key y la Client Key se han generado previamente en el entorno de Adyen. En caso de que necesites crearlas, consulta la documentación de <a href="https://docs.adyen.com/">Adyen</a>.
 </div>
 
-1. Haz clic en **Developers** en la barra lateral y luego en **API credentials**.
+1. Haz clic en __Developers__ en la barra lateral y luego en __API credentials__.
 2. Selecciona tu credencial API.
-3. En **Server Settings > Authentication**, selecciona **API key**. 
+3. En __Server Settings > Authentication__, selecciona __API key__. 
 
-![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Haz clic en <b>Generate Key</b> y anota la información creada en un lugar seguro.</ui>
 
@@ -67,7 +67,7 @@ La información a continuación supone que la API Key y la Client Key se han gen
 
 <blockquote><ui>6. Haz clic en <b>Generate Client Key</b> y anota la información creada en un lugar seguro.
 
-![Adyenv3_3](https://images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
+![Adyenv3_3](//images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
 
 ### Configura el webhook
 
@@ -75,13 +75,13 @@ La configuración del webhook es necesaria para que Adyen envíe actualizaciones
 
 Configura el webhook según los pasos a continuación:
 
-1. En tu [Área de Cliente](https://ca-test.adyen.com/) en Adyen, accede a **Developers > Webhooks**.
+1. En tu [Área de Cliente](https://ca-test.adyen.com/) en Adyen, accede a __Developers > Webhooks__.
 2. Haz clic en el botón azul `+ Webhook`.
-3. Selecciona la opción **Standard Webhook** haciendo clic en el botón **Add**.
-4. En **General > Description**,  agrega una descripción para el nuevo webhook. Ejemplo: "Webhook Adyen Connector Provider v3".
-5. En **General > Server configuration > URL**, introduce la URL de tu cuenta VTEX. Ejemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
+3. Selecciona la opción __Standard Webhook__ haciendo clic en el botón __Add__.
+4. En __General > Description__, agrega una descripción para el nuevo webhook. Ejemplo: "Webhook Adyen Connector Provider v3".
+5. En __General > Server configuration > URL__ introduce la URL de tu cuenta VTEX. Ejemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Haz clic en <b>Apply</b>.</ui>
 
@@ -89,11 +89,11 @@ Configura el webhook según los pasos a continuación:
 
 <blockquote><ui>8. Haz clic en <b>Save changes</b>.</ui>
 
-![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
@@ -101,25 +101,35 @@ Si tienes varias tiendas, es necesario configurar el webhook para cada una de el
 
 ## Configurar el conector AdyenV3 en VTEX
 
-1. En el Admin VTEX, ve a **Configuración de la tienda > Pagos > Configuración**, o ingresa **Configuración** na barra de busca no topo da página.
-2. En la pestaña **Afiliações de Gateways**, haz clic en el botón `+`.
-3. Haz clic en el conector **AdyenV3**.
-4. Rellena los siguientes campos con tus datos de Adyen:
-    - **Application Key**: el nombre de tu Adyen Merchant Account (paso 3 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account).
-    - **Application Token**: API Key (paso 4 de la sección [Obtener la API Key y la Client Key](#obtener-la-api-key-y-la-client-key)).
-    - **Live URL prefix**: URL prefix (paso 2 de la sección [Obtener la Live URL](#obtener-la-live-url)).
-    - **Company account**: el nombre de tu Company Account (paso 2 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account)).
-    - **Live POS URL**: no es necesario rellenar este campo (solo aplicable a Sales App). 
-    - **Client key**: Client key (paso 6 de la sección [Obtener la API Key y la Client Key](#obtener-la-api-key-y-la-client-key)).
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __AdyenV3__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Clave de aplicación__, complete el nombre de Merchant Account (paso 3 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account).
+5. En __Token de aplicación__, ingrese el API Key (paso 4 de la sección [Obtener la API Key y la Client Key](#obtener-la-api-key-y-la-client-key)).
+6. Si desea modificar el nombre de identificación que se mostrará para el proveedor AdyenV3 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+7. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.  
+8. En __Live URL prefix__, complete el URL prefix (paso 2 de la sección [Obtener la Live URL](#obtener-la-live-url)).
+9. En __Company account__, introduzca el nombre de tu Company Account (paso 2 de la sección [Obtener las credenciales Company y Merchant Account](#obtener-las-credenciales-company-y-merchant-account)).
+10. En __Live POS URL__, no es necesario rellenar este campo (solo aplicable a Sales App).
+11. En __Client key__, complete el Client key (paso 6 de la sección [Obtener la API Key y la Client Key](#obtener-la-api-key-y-la-client-key)). 
+12. Haga clic en `Guardar`.
 
-<blockquote><ui> 5. Si aparece un mensaje de alerta indicando la necesidad de instalar la aplicación, haz clic en el botón <b>Instalar aplicación</b> y sigue las instrucciones para hacerlo.</ui>
+Para configurar los medios de pago que procesará AdyenV3, accede a [Condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455). Si deseas realizar ventas a través de Sales App, ve a [Configurar pagos con AdyenV3 en Sales App](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3-en-vtex-sales-app--24yO6KloBn6DN6CbprHtgt).
 
-<blockquote><ui> 6. Haz clic en <b>Guardar</b>.</ui>
+Para establecer condiciones especiales en los medios de pago, ve a [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condicoes-especiais--tutorials_456).
 
-![Adyenv3_8](https://images.ctfassets.net/alneenqid6w5/6VHaDn8IejGCUoatLIyUtk/bb93a701e80a942064818a54ac401714/Adyenv3_8.PNG)
+## Configura la tarjeta de crédito
 
-Para configurar los medios de pago que procesará AdyenV3, accede a [Condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455). Si deseas realizar ventas a través de Sales App, ve a [Configurar pagos con AdyenV3 en Sales App](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3-en-vtex-sales-app--24yO6KloBn6DN6CbprHtgt).
+Si desea procesar pagos con tarjeta de crédito en su tienda utilizando AdyenV3, además de realizar las configuraciones anteriores descritas en este artículo, debe abrir un ticket en [Soporte VTEX](https://help.vtex.com/es/support), con la siguiente solicitud "Provider review - Add Endpoint SecureProxy - AdyenV3".  
 
-Para establecer condiciones especiales en los medios de pago, ve a [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condicoes-especiais--tutorials_456).
+En el ticket también deberás enviar la URL que será autorizada por Adyen para realizar la transacción con tarjeta de crédito en tu tienda. El formato de la URL debe ser `https://{live URL prefix}-checkout-live.adyenpayments.com`, donde la información "{live URL prefix}" debe ser la misma que la ingresada por usted en las configuraciones de Adyen en el VTEX Admin .  
+
+<div class="alert alert-warning">
+La dirección URL completa debe escribirse únicamente en letras minúsculas, incluso si el "Live URL prefix" configurado en el VTEX Admin tiene algunas letras mayúsculas.
+</div>  
+
+## Configurar el pago con Apple Pay en Adyen (opcional) 
+
+Para procesar pagos con Apple Pay en Adyen, primero debes realizar configuraciones para habilitar tu tienda en el entorno de Apple Pay. Obtenga más información en [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/docs/guides/setting-up-merchant-id-in-apple-pay). 
 
 Tras seguir los pasos indicados, el conector AdyenV3 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como opción de pago.
diff --git a/docs/tutorials/es/configuring-price-divergence-rule.md b/docs/tutorials/es/configuring-price-divergence-rule.md
index 6d2a97ab7..251da6535 100644
--- a/docs/tutorials/es/configuring-price-divergence-rule.md
+++ b/docs/tutorials/es/configuring-price-divergence-rule.md
@@ -3,8 +3,8 @@ title: 'Configuración de regla de Divergencia de precios'
 id: awAKP0sS5J8jgLs2g7pPe
 status: PUBLISHED
 createdAt: 2021-12-03T01:24:41.194Z
-updatedAt: 2023-03-29T19:19:25.326Z
-publishedAt: 2023-03-29T19:19:25.326Z
+updatedAt: 2024-03-27T21:10:37.241Z
+publishedAt: 2024-03-27T21:10:37.241Z
 firstPublishedAt: 2021-12-03T01:31:08.666Z
 contentType: tutorial
 productTeam: Channels
@@ -15,37 +15,43 @@ legacySlug: configuracion-de-regla-de-divergencia-de-valores
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-Cuando el precio definido por el _seller_ es diferente del precio ofrecido por el _marketplace_, es posible que los pedidos no se procesen correctamente. En VTEX, el flujo de Autorización de pedidos permite controlar y aprobar automáticamente estos pedidos, a partir de la configuración de una [regla de Divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW). Este artículo explica cómo los _sellers_ pueden crear y editar una regla de Divergencia de precios y autorizar pedidos manualmente.
+Cuando el precio definido por el _seller_ es diferente del precio ofrecido por el _marketplace_, es posible que los pedidos no se procesen correctamente. En VTEX, el flujo de autorización de pedidos permite controlar y aprobar automáticamente estos pedidos, a partir de la configuración de una [regla de divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW). Este artículo explica cómo los _sellers_ pueden crear y editar una regla de divergencia de precios y autorizar pedidos manualmente.
 
-Cuando no se ha creado ninguna regla de Divergencia de precios, los pedidos con divergencia de valores se aprueban automáticamente. Esto se aplica a los _marketplaces_ VTEX, a los _marketplaces_ externos y a los [conectores certificados (_partners_)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner), pero no a los [conectores nativos](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex). 
+Cuando no se crea ninguna regla de divergencia de precios, la plataforma VTEX tendrá un comportamiento específico para cada una de las situaciones que se indican a continuación:
 
-Cuando un _seller_ está integrado a un conector nativo, como Mercado Libre, pero no ha configurado una regla de Divergencia de precios, los pedidos con error por diferencia de valores quedan pendientes hasta que se cree la regla. Puedes seguirlos en tu Admin VTEX, en **MARKETPLACE > Conexiones > Pedidos**.
+- **Pedidos creados por la interfaz del marketplace:** se denegarán automáticamente.
+- **Pedidos creados a través de la API:** se denegarán automáticamente si no se envía el campo `isCreatedAsync`.
+- **Pedidos con divergencia de precios relacionados con descuentos manuales:** se aprobarán automáticamente.
 
-Recomendamos que el _seller_ cree la regla de Divergencia de precios antes de configurar la integración con un conector nativo. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios.
+Para utilizar el flujo de autorización de pedidos en casos de divergencia de precios es necesario enviar el campo `isCreatedAsync` en la [API de Place Fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders), independientemente del tipo de conector utilizado. Este escenario es válido para marketplaces VTEX, marketplaces externos, [conectores certificados (partners)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) o [conectores nativos.](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex)
 
-## Crear una regla de Divergencia de precios
+Cuando un _seller_ está integrado a un conector nativo, como Mercado Libre, pero no ha configurado una regla de divergencia de precios, los pedidos con error por diferencia de valores quedan pendientes hasta que se cree la regla. Puedes seguirlos en tu Admin VTEX, en **MARKETPLACE > Conexiones > Pedidos**.
 
-La [regla de Divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) se compone de una o varias reglas de autorización de pedidos, que corresponden a intervalos entre el 0% y el 100% del precio del pedido. La configuración se realiza de forma que cada intervalo esté asociado a una acción automática de procesamiento.
+Recomendamos que el _seller_ cree la regla de Divergencia de precios antes de configurar la integración con un conector nativo. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se cree la regla de divergencia de precios.
+
+## Crear una regla de divergencia de precios
+
+La [regla de divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) se compone de una o varias reglas de autorización de pedidos, que corresponden a intervalos entre el 0% y el 100% del precio del pedido. La configuración se realiza de forma que cada intervalo esté asociado a una acción automática de procesamiento.
 
 <div class = "alert alert-info">
-Para crear una regla de Divergencia de precios, el usuario debe tener el <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">rol</a> Admin Super (Owner) o OMS Full. Garantiza la seguridad en la gestión de tus operaciones y consulta las <a href="https://help.vtex.com/es/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM">buenas prácticas de seguridad para la gestión de usuarios</a>.
+Para crear una regla de divergencia de precios, el usuario debe tener el <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">rol</a> Admin Super (Owner) o OMS Full. Garantiza la seguridad en la gestión de tus operaciones y consulta las <a href="https://help.vtex.com/es/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM">buenas prácticas de seguridad para la gestión de usuarios</a>.
 </div>
 
-Para crear una regla de Divergencia de precios, sigue los pasos a continuación:
+Para crear una regla de divergencia de precios, sigue los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda > Pedidos > Autorización de pedidos**, o escribe **Autorización de pedidos** en la barra de búsqueda en la parte superior de la página.  
+1. En el Admin VTEX, accede a **Configuración de la tienda > Pedidos > Autorización de pedidos**, o escribe **Autorización de pedidos** en la barra de búsqueda en la parte superior de la página.
 2. En la sección _Divergencia de precios, haz clic en `CREAR REGLAS`.
-3. En la nueva página que se abre, haz clic en `CREAR REGLAS`. 
+3. En la nueva página que se abre, haz clic en `CREAR REGLAS`.
 
 Verás la siguiente pantalla:
 
-![print_01_ES](https://drive.google.com/uc?export=download&id=1SHYBnQSnp-B8k-Gm3SSBxwPtNa57sQvx)
+![print_01_ES](//images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/9f087e8080a0a18dbb9caeb890a4beae/print_01_ES.png)
 
-La pestaña **Todas** muestra todas las reglas de autorización configuradas. 
+La pestaña **Todas** muestra todas las reglas de autorización configuradas.
 
 Para crear la primera regla de autorización, haz clic en **CREAR REGLAS**. Se mostrará una nueva pestaña, llamada **1ª regla**. Al clicar en esta pestaña, aparecerán las opciones de configuración.
 
-![print_02_ES](https://drive.google.com/uc?export=download&id=1mzQfJw-9llpMJzrI_sWmVusEIzpeqQGi)
+![print_02_ES](//images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/b44238cace132525165ab84ba6eacf7c/print_02_ES.png)
 
 Para configurar la **1ª regla**, puedes aumentar o disminuir el porcentaje de divergencia arrastrando los extremos de la barra. El signo > define el inicio del intervalo y el signo < determina su fin. El intervalo elegido puede ser del 0% al 100%.
 
@@ -59,38 +65,38 @@ Una vez definido el intervalo de la regla de autorización, selecciona una de la
 
 Para configurar una jerarquía de usuarios responsables de aprobar los pedidos, debes introducir más de un email y ordenar los usuarios registrados. Puedes cambiar estos usuarios en cualquier momento editando la regla de autorización de pedidos. Ten en cuenta que solo usuarios con los [roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (Owner) o OMS Full pueden editar la regla.
 
-Para crear la **segunda regla**, haz clic en el <img class="shadow-4" src="https://https://images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> signo más. Lo mismo se aplica a la creación de una tercera o cuarta regla, y así en adelante. Tras hacer clic en el ícono, se mostrará la siguiente interfaz:
+Para crear la **segunda regla**, haz clic en el `<img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" />` signo más. Lo mismo se aplica a la creación de una tercera o cuarta regla, y así en adelante. Tras hacer clic en el ícono, se mostrará la siguiente interfaz:
 
-![print_03_ES](https://drive.google.com/uc?export=download&id=1nEg5Ra2shCtA9gPSzejiXxDF-lX3t0T5)
+![print_03_ES](//images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/4c61f021b61f9147dbf87ff2a68b474f/print_03_ES.png)
 
-Configura la nueva regla de autorización y, después de definir todas las reglas que desees, haz clic en el botón **GUARDAR REGLAS**. Verás el siguiente mensaje: _Después de guardar las reglas, puedes editarlas o eliminarlas cuando quieras_. Haz clic en **OK** para confirmar. Una vez que hayas hecho esto, se creará la regla de Divergencia de precios.
+Configura la nueva regla de autorización y, después de definir todas las reglas que desees, haz clic en el botón **GUARDAR REGLAS**. Verás el siguiente mensaje: _Después de guardar las reglas, puedes editarlas o eliminarlas cuando quieras_. Haz clic en **OK** para confirmar. Una vez que hayas hecho esto, se creará la regla de divergencia de precios.
 
 <div class="alert alert-warning">
-Después de que hayas configurado la regla de Divergencia de precios, esta se aplicará a todos los <i>marketplaces</i> en los que actúes como seller.
+Después de que hayas configurado la regla de divergencia de precios, esta se aplicará a todos los <i>marketplaces</i> en los que actúes como seller.
 </div>
 
-## Editar una regla de Divergencia de precios
+## Editar una regla de divergencia de precios
 
-La regla de Divergencia de precios se puede editar en cualquier momento. Para ello, ve al Admin VTEX y haz clic en **Configuración de la tienda > Pedidos > Autorización de pedidos > Divergencia de precios > EDITAR REGLAS**.
+La regla de divergencia de precios se puede editar en cualquier momento. Para hacerlo, ve al Admin VTEX y haz clic en **Configuración de la tienda > Pedidos > Autorización de pedidos > Divergencia de precios > EDITAR REGLAS**.
 
-En la página de edición de reglas, puedes eliminar la regla de Divergencia de precios haciendo clic en **ELIMINAR REGLAS**. Esto hace que todas las reglas de autorización configuradas se eliminen permanentemente.
+En la página de edición de reglas, puedes eliminar la regla de divergencia de precios haciendo clic en **ELIMINAR REGLAS**. Esto hace que todas las reglas de autorización configuradas se eliminen permanentemente.
 
 <div class = "alert alert-info">
-Si eliminas la regla de Divergencia de precios, esta acción no se puede revertir. Para que vuelva a aplicarse, será necesario configurarla de nuevo. Lo mismo se aplica a las reglas de autorización que componen la regla de Divergencia de precios.
+Si eliminas la regla de divergencia de precios, esta acción no se puede revertir. Para que vuelva a aplicarse, será necesario configurarla de nuevo. Lo mismo se aplica a las reglas de autorización que componen la regla de divergencia de precios.
 </div>
 
 En la misma página, en la pestaña **Todas**, puedes ver la lista de todas las reglas de autorización de pedidos creadas. Para eliminar una regla de autorización, haz clic en el botón **ELIMINAR REGLA** junto a la regla que deseas eliminar.
 
-Si quieres editar una regla de autorización, haz clic en la pestaña correspondiente a la regla que quieres modificar. El proceso de edición de reglas es el mismo que el que se describe en la etapa de [creación de la regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#crear-una-regla-de-divergencia-de-precios).
+Si quieres editar una regla de autorización, haz clic en la pestaña correspondiente a la regla que quieres modificar. El proceso de edición de reglas es el mismo que el que se describe en la etapa de [creación de la regla de divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#crear-una-regla-de-divergencia-de-precios).
 
 Una vez que hayas hecho los cambios deseados, haz clic en el botón **GUARDAR REGLAS** y luego en **OK**.
 
 ## Autorizar pedidos manualmente
 
-Cuando una regla de autorización se configura con la opción _Crear una tarea en VTEX DO para aprobación_, esto significa que se ha asignado al menos un usuario para autorizar manualmente el pedido. La [gestión de pedidos con Divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW#gestion-de-pedidos-con-divergencia-de-precios) es similar a la de otros canales de venta, como la tienda física o el ecommerce.
+Cuando una regla de autorización se configura con la opción _Crear una tarea en VTEX DO para aprobación_, esto significa que se ha asignado al menos un usuario para autorizar manualmente el pedido. La [gestión de pedidos con divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW#gestion-de-pedidos-con-divergencia-de-precios) es similar a la de otros canales de venta, como la tienda física o el ecommerce.
 
 <div class="alert alert-warning">
-Es importante hacer un seguimiento regular de los pedidos en <b>Pedidos > Todos los pedidos</b>. Si requieren aprobación manual, los pedidos con errores de divergencia de precios quedan pendientes de autorización por parte de un usuario habilitado, definido al crear la regla de autorización. Una buena práctica es tener al menos dos usuarios autorizados a realizar el procesamiento manual.
+Es importante hacer un seguimiento regular de los pedidos en <b>Pedidos > Todos los pedidos</b>. Si requieren aprobación manual, los pedidos con errores de divergencia de precios quedan pendientes de autorización por parte de un usuario habilitado, definido al crear la regla de autorización. Una buena práctica es tener al menos dos usuarios con autorización para realizar el procesamiento manual.
 </div>
 
 Hay dos maneras de autorizar manualmente un pedido con divergencia de precios:
@@ -100,7 +106,7 @@ Hay dos maneras de autorizar manualmente un pedido con divergencia de precios:
 
 ### Autorizar un pedido por el módulo Pedidos
 
-Esta forma de aprobación se realiza en la página de la [Todos los pedidos](https://help.vtex.com/es/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi). Para ello, sigue los pasos a continuación:
+Esta forma de aprobación se realiza en la página [Todos los pedidos](https://help.vtex.com/es/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi). Para ello, sigue los pasos a continuación:
 
 1. Accede al Admin VTEX y haz clic en _PEDIDOS > Gestión de pedidos > Todos los pedidos_.
 2. Haz clic en el pedido que tiene el status `Esperando autorización manual`.
@@ -108,9 +114,9 @@ Esta forma de aprobación se realiza en la página de la [Todos los pedidos](htt
 
 ### Autorizar pedidos por VTEX DO
 
-VTEX DO es un gestor de las tareas producidas por los módulos de la plataforma VTEX. Permite a los usuarios habilitados realizar manualmente tareas como autorizar o cancelar pedidos, entre otras. Aprende más en el artículo [VTEX DO](https://help.vtex.com/es/tutorial/vtex-do--tutorials_203).
+VTEX DO es un gestor de las tareas producidas por los módulos de la plataforma VTEX. Permite a los usuarios habilitados realizar manualmente tareas como autorizar o cancelar pedidos, entre otras. Aprende más en el artículo [VTEX DO](https://help.vtex.com/es/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu).
 
-Para autorizar un pedido con Divergencia de valores por VTEX DO, sigue los pasos a continuación:
+Para autorizar un pedido con divergencia de valores por VTEX DO, sigue los pasos a continuación:
 
 1. En el Admin VTEX, accede a **Pedidos > Todos los pedidos**, o escribe **Todos los pedidos** en la barra de búsqueda en la parte superior de la página.
 2. En la esquina inferior derecha de la pantalla, haz clic en el componente de VTEX DO.
@@ -123,3 +129,4 @@ Para autorizar un pedido con Divergencia de valores por VTEX DO, sigue los pasos
 - [Regla de Divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW)
 - [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi)
 - [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402)
+
diff --git a/docs/tutorials/es/configuring-product-visited.md b/docs/tutorials/es/configuring-product-visited.md
index d0ab170ac..d98221244 100644
--- a/docs/tutorials/es/configuring-product-visited.md
+++ b/docs/tutorials/es/configuring-product-visited.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar producto visitado'
 id: tutorials_3136
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T21:52:11.184Z
-updatedAt: 2023-03-28T23:34:22.351Z
-publishedAt: 2023-03-28T23:34:22.351Z
+updatedAt: 2024-06-18T21:19:01.080Z
+publishedAt: 2024-06-18T21:15:58.589Z
 firstPublishedAt: 2017-04-27T23:03:54.918Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,6 +15,10 @@ legacySlug: configurar-producto-visitado
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
+<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Tutorial válido solo para tiendas CMS Portal Legado.
+</div>
+
 El producto visitado es la funcionalidad que envía emails a los clientes que navegaron por un producto en su site pero que no finalizaron compra. Ese email tiene como objetivo la recuperación de la venta, enviando, además del producto abandonado, sugerencias de nuevos productos. Todo ello es posible a través de su Master Data.
 
 [![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
diff --git a/docs/tutorials/es/configuring-promotions-for-marketplaces.md b/docs/tutorials/es/configuring-promotions-for-marketplaces.md
index 74409d791..58d45d8c0 100644
--- a/docs/tutorials/es/configuring-promotions-for-marketplaces.md
+++ b/docs/tutorials/es/configuring-promotions-for-marketplaces.md
@@ -3,8 +3,8 @@ title: 'Configurar promoción para marketplace'
 id: tutorials_406
 status: PUBLISHED
 createdAt: 2017-04-27T22:06:28.854Z
-updatedAt: 2023-01-26T18:41:34.664Z
-publishedAt: 2023-01-26T18:41:34.664Z
+updatedAt: 2024-01-18T17:21:44.418Z
+publishedAt: 2024-01-18T17:21:44.418Z
 firstPublishedAt: 2017-04-27T23:03:23.902Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,42 +15,43 @@ legacySlug: promocion-para-marketplace
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-El módulo de promociones de VTEX permite la creación de diferentes tipos de promoción, desde las más clásicas hasta las más innovadoras. Sin embargo, su utilización en marketplaces está restringido a algunos tipos específicos. Este tutorial explica cómo definir los marketplaces en los que se aplicará una promoción y cuáles son las condiciones que son aplicables en ese escenario. 
+VTEX permite la creación de diferentes tipos de [promociones](https://help.vtex.com/es/tutorial/visao-geral-promocoes--3PeHVYcooLIDmA33IAnjhm?&utm_source=autocomplete#). Sin embargo, las promociones que se configuran en la cuenta de un seller y se utilizan en marketplaces (VTEX o externos) se limitan a algunos tipos específicos. Este tutorial explica cómo definir las promociones y condiciones que son aplicables en estos escenarios.
 
-## Promociones disponibles para marketplaces
+## Promociones disponibles de sellers para marketplaces
 
-Solo los siguientes tipos de [promociones regulares](https://help.vtex.com/es/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) funcionan en los marketplaces:
+En marketplaces, solamente pueden aplicarse los siguientes tipos de [promociones regulares](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI):
 
-- Promoción de flete gratis.
-- Promoción de flete porcentual.
-- Promoción de precio porcentual.
+* Envío gratis
+* Envío porcentual
+* Porcentaje de precio
+* Tabla de precios
 
-La configuración disponible para marketplaces VTEX es diferente a la ofrecida para marketplaces externos, y el comportamiento de esas promociones es ligeramente diferente a lo habitual. 
+La [configuración disponible](#heading=h.2et92p0) para marketplaces VTEX es diferente de la que se ofrece a los marketplaces externos. Por esta razón, el comportamiento de las promociones en otros marketplaces es ligeramente distinto del habitual.
 
-### Promociones de flete gratis y porcentual
+### Promociones de envío gratis y envío porcentual
 
-Para este tipo de promoción se debe considerar la siguiente información: 
+Para este tipo de promociones es importante tener en cuenta la siguiente información:
 
-- Algunos marketplaces utilizan su propia tabla de fletes. Esto impide que una promoción de flete gratis sea aplicada en un pedido, ya que el marketplace no consulta el valor del flete registrado en VTEX.  
-- Para que la promoción afecte al valor del flete, el marketplace debe simular el flete utilizando el endpoint `POST` `https://{accountName}.vtexcommercestable.com.br/api/fulfillment/pvt/orderForms/simulation?sc={salesChannel}&affiliateId={affiliateId}`.
-- La promoción no afectará al valor del producto si el marketplace utiliza el endpoint [List Freight Values](https://developers.vtex.com/docs/api-reference/logistics-api#get-/logistics/pvt/configuration/freights/-carrierId-/-cep-/values) de Logistics API para la consulta de fletes. Este endpoint solo devuelve los fletes registrados en VTEX, sin considerar los efectos de las promociones.
-- Los sellers determinan los límites de reducción de precio que el marketplace puede aplicar sobre el flete cobrado. En caso de que sobrepase el límite establecido, el pedido no es rechazado.
+* Algunos marketplaces utilizan sus propias tablas de envío. Esto impide que se aplique una promoción de envío a un pedido, ya que el marketplace no consulta el precio del envío registrado en VTEX.
+* Para que la promoción se aplique al valor del envío, el marketplace debe simular el envío utilizando el endpoint [Fulfillment simulation - External Marketplace](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/checkout/pub/orderForms/simulation).
+* La promoción no se aplicará al valor del producto si el marketplace utiliza el endpoint [List Freight Values](https://developers.vtex.com/vtex-developer-docs/reference/carriers#freightvalues) de la API de Logistics para la consulta de tarifas de envío. Este endpoint devuelve únicamente las tarifas de envío registradas en VTEX, sin considerar los efectos de la aplicación de la promoción.
+* Los sellers determinan los límites de reducción de precio que el marketplace puede aplicar al valor del envío. Si el valor de la reducción supera el límite establecido, no se realizará el pedido.
 
-### Promoción de precio porcentual
+### Promociones de porcentaje de precio
 
-Para este tipo de promoción se debe considerar lo siguiente: 
+Para este tipo de promociones es importante tener en cuenta la siguiente información:
 
-- El marketplace no recibe la promoción en sí, solamente una notificación por API que indica que el precio sufrió alteraciones. Por ello, al marketplace le corresponde consultar el precio promocional. 
-- Para que la promoción afecte al valor del producto, el marketplace debe simular el precio del SKU utilizando el endpoint [Do OrderForm Simulation](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pub/orderForms/simulation) de Checkout API.
-- La promoción no afectará al valor del producto si el marketplace utiliza el endpoint [Get Price](https://developers.vtex.com/docs/api-reference/pricing-api#get-/prices/-itemId-) de Pricing API para consultas de precios. Este endpoint solo devuelve los precios registrados en VTEX, sin considerar los efectos de las promociones. 
-- Los sellers determinan los límites de reducción de precio que el marketplace puede aplicar sobre el valor total del pedido. En caso de que sobrepase el límite establecido, el pedido es rechazado. Usted puede modificar la configuración de su tienda en la sección [Autorización de Pedidos](https://help.vtex.com/es/tutorial/como-funciona-la-autorizacion-de-pedidos--3MBK6CmKHAuUjMBieDU0pn#divergencia-de-valores).
+* Una vez que el seller crea y activa la promoción, esta no genera ningún tipo de notificación para el marketplace. Corresponde al marketplace consultar el precio promocional.
+* Para que la promoción se aplique al valor del producto, el marketplace debe simular el precio del SKU utilizando el endpoint [Do OrderForm Simulation](https://developers.vtex.com/vtex-developer-docs/reference/orderform#orderformsimulation) de la API de Checkout.
+* La promoción no se aplicará al valor del producto si el marketplace utiliza el endpoint [Get Price](https://developers.vtex.com/vtex-developer-docs/reference/prices-and-fixed-prices#getprice) de la API de Pricing para consulta de envíos. Este endpoint devuelve únicamente los precios registrados en VTEX, sin considerar los efectos de la aplicación de la promoción.
+* Los sellers determinan los límites de reducción de precio que el marketplace puede aplicar sobre el valor total del envío. Si el valor de la reducción supera el límite establecido, no se realizará el pedido. Puedes modificar la configuración de tu tienda en la sección [Autorización de pedidos](https://help.vtex.com/es/tutorial/como-funciona-a-autorizacao-de-pedidos--3MBK6CmKHAuUjMBieDU0pn?&utm_source=autocomplete#divergencia-de-valores).
 
-### Configuraciones disponibles
+### Configuración disponible
 
-Existen diferencias entre la configuración que está disponible para marketplaces VTEX y para marketplaces externos. Vea las funcionalidades que aplican a cada caso en la siguiente tabla.  
+Existen diferencias entre la configuración disponible para marketplaces VTEX y para marketplaces externos. Consulta en la tabla siguiente las funcionalidades que se aplican en cada caso.
 
 <div class = "alert alert-warning">
-  <p><b>Importante:</b>en el caso de las integraciones externas, las configuraciones son únicas para cada marketplace, y estos deciden qué funcionalidades utilizarán.</p>
+  <p>En el caso de las integraciones externas, las configuraciones son únicas para cada marketplace, y estos deciden qué funcionalidades utilizarán.</p>
 </div>
 
 | Nombre  | Descripción      | ¿Disponible para marketplaces VTEX? | ¿Disponible para marketplaces externos? |
@@ -73,9 +74,49 @@ Existen diferencias entre la configuración que está disponible para marketplac
 | Canales de venta| La promoción se aplicará a una lista de canales de venta| Sí| Sí|
 | Valor del ítem entre| Establece las políticas comerciales válidas para la promoción| Sí| Sí|
 
-## Definiendo dónde se aplicará la promoción
-
-Si es necesario, se puede segmentar promociones para marketplaces específicos. Existen dos opciones que se pueden utilizar para obtener ese resultado:
+## Promociones no disponibles para marketplaces**
+
+Consulta a continuación las promociones que no están disponibles para marketplaces:
+
+* Descuento nominal
+* Precio máximo por ítem
+* Envío nominal
+* Envío máximo
+* Regalo
+* Valor de fidelidad
+* Comprar juntos
+* Más por menos
+* Descuento progresivo
+* Compra uno y lleva uno gratis
+* Promoción de campaña
+
+### Configuración no disponible
+
+A continuación se muestran las opciones de configuración** **no disponibles para marketplaces:
+
+| Nombre | Descripción |
+| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Clúster de clientes                                                  | Descuento concedido si el cliente está registrado en el [clúster](https://help.vtex.com/es/tutorial/como-criar-um-cluster-de-clientes--frequentlyAskedQuestions_1724) seleccionado.                                           |
+| Tag de marketing                                                     | Utilizado para restringir la activación de la promoción si la compra se realiza a través del [módulo de Suscripciones de VTEX](https://help.vtex.com/es/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#). |
+| UTM                                                                  | Descuento concedido en función del valor de un determinado [parámetro UTM](https://help.vtex.com/es/tutorial/o-que-sao-utm-source-utm-campaign-e-utm-medium--2wTz7QJ8KUG6skGAoAQuii).                                         |
+| Audiencia de campaña                                                 | Permite segmentar las promociones de tu tienda definiendo [públicos objetivos](https://help.vtex.com/es/tutorial/audiencias-de-campanhas--3o7lhpNseXY2WmjZO0gQ6m#publico-alvo) que cumplan criterios específicos.             |
+| Cupones                                                              | Código que permite aplicar promociones sobre el valor del carrito.                                                                                                                                                            |
+| Valor mínimo o máximo del carrito                                    | Se aplica teniendo en cuenta el valor del carrito sin considerar ni otras promociones ni el envío.                                                                                                                            |
+| Número de cuotas                                                     | Descuento concedido si el número de cuotas seleccionado por el cliente se encuentra dentro del intervalo registrado.                                                                                                          |
+| Restricción por BIN                                                  | Descuento concedido si el BIN de la tarjeta figura entre los números ingresados.                                                                                                                                              |
+| Medio de pago                                                        | Descuento concedido si el medio de pago seleccionado por el cliente es el mismo que el registrado en la promoción.                                                                                                            |
+| Primera compra                                                       | Descuento concedido en la primera compra del cliente.                                                                                                                                                                         |
+| Valor acumulado de las compras                                       | Descuento concedido si el valor total de todas las compras ya realizadas por el cliente coincide con el valor ingresado.                                                                                                      |
+| Permitir acumular con precios manuales                               | Permite aplicar la promoción a productos cuyos precios han sido ingresados manualmente por el teleoperador de ventas.                                                                                                         |
+| Precio "de" y "por" son iguales o Precio "de" y "por" son diferentes | Hace referencia a los valores del registro del producto.                                                                                                                                                                      |
+| Filtro de sellers                                                    | Define a qué sellers se aplicará la promoción.                                                                                                                                                                                |
+| Uso máximo de la promoción por cliente                               | Limita la cantidad de veces que cada cliente puede recibir la promoción.                                                                                                                                                      |
+| Uso máximo de la promoción por tienda                                | Limita el número de veces que se aplicará la promoción.                                                                                                                                                                       |
+| Uso máximo del cupón por producto                                    | Limita el número de veces que el cupón será válido por producto.                                                                                                                                                              |
+
+## Definir el contexto en el que se aplicará la promoción
+
+Los sellers pueden segmentar las promociones para mercados específicos. Hay dos modos de realizarlo:
 
 - [Política comercial](https://help.vtex.com/es/tutorial/que-es-una-politica-comercial--563tbcL0TYKEKeOY4IAgAE): se utiliza cuando todos los marketplaces objetivos comparten la misma configuración de canal de ventas (catálogo, precio y logística).
 - [Afiliado](https://help.vtex.com/es/tutorial/que-es-afiliado--4bN3e1YarSEammk2yOeMc0): se utiliza para seleccionar uno o más marketplaces específicos, aunque no compartan la misma configuración de canal de ventas.
@@ -95,5 +136,5 @@ Si es necesario, se puede segmentar promociones para marketplaces específicos.
 4. Haga clic en `Guardar`.
 
 <div class = "alert alert-warning">
-  <p>Una vez creada la promoción, recuerde <a href = "https://help.vtex.com/es/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar los productos afectados</a>. De esta manera, sus productos tendrán los precios actualizados.</p>
+  <p>Una vez creada la promoción, recuerde <a href = "https://help.vtex.com/es/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar los productos afectados</a> al inicio y al final de las promociones. De esta manera, sus productos tendrán los precios actualizados.</p>
 </div>
diff --git a/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md b/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md
index ef3f438bc..6429b0e23 100644
--- a/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md
+++ b/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md
@@ -3,8 +3,8 @@ title: 'Configurar promoción con destaque / flag'
 id: tutorials_2295
 status: PUBLISHED
 createdAt: 2017-04-27T21:55:19.949Z
-updatedAt: 2023-03-31T19:22:08.848Z
-publishedAt: 2023-03-31T19:22:08.848Z
+updatedAt: 2024-07-29T18:59:29.549Z
+publishedAt: 2024-07-29T18:59:29.549Z
 firstPublishedAt: 2017-04-27T23:03:51.539Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,6 +15,10 @@ legacySlug: configurando-promocion-con-destaque-flag
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
+<div class="alert alert-warning" role="alert">
+Tutorial válido solo para tiendas CMS Portal Legado.
+</div>
+
 El destaque en la promoción es un aviso que puede ser colocado en los estantes y en las páginas de los productos, informando que el producto es elegible para una promoción. Un ejemplo muy común es una imagen debajo de la imagen del producto indicando flete gratis.
 
 ![ExemploPromocaoDestaque2](//images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
@@ -62,7 +66,7 @@ Esta configuración consiste en la edición de la plantilla de la página utiliz
 9. En la ventana, haga clic en la opción **New Layout**.
 10. En el menú lateral, haga clic sobre el layout marcado con un check rojo y en el campo __template__, verifique cuál es el nombre de la plantilla utilizada.
 
-![Layout com check - PT](https://images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
+![Layout com check - PT](//images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
 
 ![Template](//images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
 
diff --git a/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md b/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md
new file mode 100644
index 000000000..611a2cd91
--- /dev/null
+++ b/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md
@@ -0,0 +1,73 @@
+---
+title: 'Configurar PWA en tu tienda Store Framework'
+id: 1xWVQTONeROlSOXG8lSyKV
+status: PUBLISHED
+createdAt: 2024-06-18T14:58:53.804Z
+updatedAt: 2024-06-20T12:15:54.742Z
+publishedAt: 2024-06-20T12:15:54.742Z
+firstPublishedAt: 2024-06-18T15:49:26.862Z
+contentType: tutorial
+productTeam: Others
+author: YRJ73j8mt38D5TUleocQB
+slug: configurar-pwa-en-tu-tienda-store-framework
+locale: es
+legacySlug: configurar-pwa-en-tu-tienda-store-framework
+subcategory: 7ogirQ8NClawO2X6xdgCKc
+---
+
+Las tiendas creadas con VTEX IO Store Framework incorporan de forma nativa una aplicación web progresiva (PWA), la cual brinda una experiencia de usuario similar a la de una aplicación nativa, pero se ejecuta directamente en un navegador web.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Para tiendas CMS Portal Legado, consulta la guía <a href="https://help.vtex.com/es/tutorial/how-to-turn-my-store-website-into-a-pwa--3i8VmYeToAUGKgo2kKK6I2">Cómo transformar el sitio web de mi tienda en una PWA</a>.
+</div>
+
+Para configurar una PWA en tu tienda, accede a Configuración de la tienda > **Storefront > Tienda** en el Admin VTEX, y sigue los pasos que se indican a continuación:
+
+1. Haz clic en la pestaña **PWA**.
+2. Define **Color del tema**, **Color de fondo**, y agrega el **ícono del logotipo Android (512x512, PNG)** y **el del logotipo iOS (512x512, PNG)**. Los colores deben especificarse en código hexadecimal (por ejemplo, #F71963) y los íconos deben tener un tamaño de 512x512 px y una extensión `.png`.
+
+  ![pwa-settings-1-es](//images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/b3547450cdd0b02c68e36806bf78410f/pwa-settings-1-es.png)
+
+3. Desplázate hacia abajo hasta el campo **Otras configuraciones de PWA**. Haz clic en la flecha para mostrarlas.
+
+  ![pwa-settings-2-es](//images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/90ef8a3581aabdb1078872a6afcffd53/pwa-settings-2-es.png)
+
+4. En **Otras configuraciones de PWA**, rellena los campos según las directrices que se indican a continuación:
+
+    - **URL de inicio**: URL de la página de inicio de la PWA.
+    - **Orientación de la pantalla**: formato en el que se muestra el contenido en la PWA. Se puede asignar uno de los siguientes valores: Cualquiera, Natural, Horizontal, Horizontal (primaria), Horizontal (secundaria), Vertical, Vertical (primaria), Vertical (secundaria).
+
+    | **Orientación de la pantalla** | **Descripción** |
+    |--------------------------------|-----------------|
+    | Cualquiera                     | La página puede verse en cualquier orientación, y el contenido se ajusta automáticamente a la posición actual del dispositivo. |
+    | Natural                        | Configuración predeterminada del dispositivo. |
+    | Horizontal                     | El contenido solo se muestra en posición horizontal. Es útil para aplicaciones o juegos optimizados para una vista más amplia. |
+    | Horizontal (primaria)          | Posición horizontal con la parte superior del dispositivo alineada a la izquierda. |
+    | Horizontal (secundaria)        | Posición horizontal con la parte superior del dispositivo alineada a la derecha. |
+    | Vertical                       | El contenido solo se muestra en posición vertical. Esta es la configuración predeterminada de la mayoría de las aplicaciones para teléfonos celulares. |
+    | Vertical (primaria)            | En posición vertical, el botón de inicio o la parte inferior del dispositivo apunta hacia abajo. |
+    | Vertical (secundaria)          | En posición vertical invertida, el botón de inicio o la parte inferior del dispositivo apunta hacia arriba. Es útil cuando los dispositivos se utilizan en posición contraria. |
+
+    - **Visualización**: modos de visualización del contenido de la PWA. Se puede asignar uno de los siguientes valores: Pantalla completa, Independiente (agregar a la pantalla de inicio), UI minimalista (no admitida por Chrome), Navegador.
+
+    | **Visualización**                     | **Descripción** |
+    |---------------------------------------|-----------------|
+    | Pantalla completa                     | La PWA ocupa toda la pantalla del dispositivo, ocultando todos los elementos de la interfaz de usuario del navegador, como la barra de direcciones y otras notificaciones del sistema. Es ideal para juegos o aplicaciones que requieren una inmersión total, maximizando el espacio disponible en pantalla. |
+    | Independiente (agregar a la pantalla de inicio) | La PWA se comporta como una aplicación nativa ya que se ejecuta en una ventana independiente del navegador y no muestra los elementos usuales del mismo, como la barra de direcciones. Cuando se agrega a la pantalla de inicio del dispositivo, la presencia de la PWA es casi indistinguible de una aplicación nativa. |
+    | UI minimalista (no admitida por Chrome) | La PWA muestra un mínimo de elementos de la interfaz de usuario del navegador, como la barra de direcciones y algunos controles adicionales. Es un término medio entre el modo Aplicación y el modo Navegador. |
+    | Navegador                            | La PWA se abre como una página convencional del navegador, mostrando todas las funciones habituales, como la barra de direcciones, las pestañas y otros controles de la interfaz. No cambia la forma estándar en que el usuario interactúa con el contenido web y proporciona una experiencia menos inmersiva en comparación con otros modos de visualización. |
+
+    - **Agregar a la pantalla de inicio**: cuando se activa, permite que la PWA la instale el usuario.
+    - **Mostrar promt "Agregar a la pantalla de inicio"**: define el momento en que se le sugerirá al usuario instalar la PWA. Se puede asignar uno de los siguientes valores: En la primera visita, En el primer ítem agregado al carrito o Al finalizar la primera compra. Esta opción solo es aplicable cuando la opción **Agregar a pantalla de inicio** está activada.
+
+    ![pwa-settings-3-es](//images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/d5c70b92839c1f5ff880c00c98d93307/pwa-settings-3-es.png)
+
+5. Haz clic en `Guardar`.
+
+## Utilizar un service worker personalizado
+
+Nuestro service worker (trabajador de servicios) admite pulsaciones nativas para instalar la aplicación en la primera visita, el primer artículo añadido al carrito o la primera compra. Puedes personalizar las notificaciones en la PWA de tu tienda mediante el uso de tu propio service worker, que operará en conjunto con el nuestro.
+
+Para saber cómo crear tu propio service worker, consulta la documentación [Cómo instalar un service worker](https://help.vtex.com/es/tutorial/como-instalar-um-service-worker--2H057iW0mQGguKAciwAuMe).
+
+Para aprender a utilizar el service worker builder para agrupar varios service workers en tu tienda, consulta la documentación [Using several service workers in your store](https://developers.vtex.com/docs/guides/vtex-io-documentation-using-several-service-workers-in-your-store).
diff --git a/docs/tutorials/es/configuring-redirects.md b/docs/tutorials/es/configuring-redirects.md
new file mode 100644
index 000000000..a4f128cc9
--- /dev/null
+++ b/docs/tutorials/es/configuring-redirects.md
@@ -0,0 +1,81 @@
+---
+title: 'Configurar redireccionamientos'
+id: 35JPufOvunMHnAAVJA6azu
+status: PUBLISHED
+createdAt: 2024-06-27T17:05:37.927Z
+updatedAt: 2024-06-27T17:06:40.835Z
+publishedAt: 2024-06-27T17:06:40.835Z
+firstPublishedAt: 2024-06-27T17:06:40.835Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configurar-redireccionamientos
+locale: es
+legacySlug: configurar-redireccionamientos
+subcategory: 
+---
+
+Para configurar un redireccionamiento, es necesario seguir los siguientes pasos:
+
+1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda en la parte superior de la página.
+2. En **Intelligent Search**, haz clic en **Redireccionamientos**.
+3. Haz clic en el botón <i class="fas fa-plus"></i> `Agregar`.
+4. Rellena los campos relativos a las [informaciones generales](#informaciones-generales) del redireccionamiento que se detallarán en la sección siguiente.
+5. Haz clic en <i class="fa-solid fa-plus"></i> `Agregar condición`.
+6. Rellena los campos para las [reglas de activación](#reglas-de-activacion).
+7. Para terminar, haz clic en `Aplicar`.
+
+Debes rellenar los siguientes campos:
+
+![redirecionamentos-adminv4-ES](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
+
+### Informaciones generales
+
+Esta sección proporciona las siguientes informaciones generales sobre el redireccionamiento:
+
+- **Nombre**: nombre del conjunto de reglas del redireccionamiento creado.
+- **URL de redireccionamiento**: URL de destino al cual el cliente será dirigido. Debe ser registrado de forma absoluta - dirección completa - y no relativa. Ejemplo: `https://www.tienda.com/_secure/account/#/orders` en vez de `_secure/account/#/orders`.
+- **Idiomas:** idiomas en los que se aplicará el redireccionamiento. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+### Reglas de activación
+
+Conjunto de condiciones de términos o filtros que se aplicarán en cada búsqueda realizada. Es necesario que se registre por lo menos una condición, ya sea por término o por filtro
+
+Selecciona el tipo de alcance de las reglas, ya sea por término o por filtro.
+
+- **Término**: palabra buscada por el cliente que estará relacionada con la regla. El término presenta dos opciones:
+    - `es`: necesita ser una búsqueda con palabras exactas. Ejemplo: si registras “Black Friday” y el cliente busca “Black Friday”, se activará el redireccionamiento. Si el cliente busca “promoción Black Friday”, no se activará.
+    - `contiene`: no tiene que ser una búsqueda con palabras exactas. Ejemplo: si registras “Black Friday” y el cliente busca “Black Friday”, se activará el redireccionamiento. Si el cliente busca “promoción Black Friday”, también se activará.
+- **Filtro**: atributo de búsqueda ya definido que restringe los resultados de la búsqueda. Con solo seleccionar el filtro ya registrado se activa el redireccionamiento creado. El filtro presenta dos opciones:
+    - `es`: esta opción permite que no se seleccione solamente el filtro de la regla. Ejemplo: si la regla es ``es``: Filtro _marca_, valor Nike, incluso si el cliente ha seleccionado Adidas, el redireccionamiento se activará.
+    - `solo`: esta opción permite seleccionar solamente el filtro registrado. Ejemplo: si la regla es ``solo``: Filtro _marca_, valor Nike, si el cliente ya ha seleccionado Adidas, no se activará el redireccionamiento. Solo funcionaría si el primer filtro de marca fuera Nike.
+
+Si quieres crear más de una regla, debes añadir una condición de interacción entre las reglas. Estas pueden ser:
+
+- `o`: cualquiera de las reglas registradas activa el redireccionamiento.
+- `y`: todas las reglas deben cumplirse conjuntamente para activar el redireccionamiento.
+
+Al hacer clic en <i class="fas fa-ellipsis-v"></i>, tendrás las siguientes opciones:
+
+- <i class="fas fa-clone"></i> **Duplicar**: crea una copia de la regla seleccionada.
+- <i class="far fa-trash-alt"></i> **Eliminar**: elimina la regla seleccionada.
+
+Para borrar todas las reglas configuradas, haz clic en "Borrar reglas".
+
+### Importar CSV
+
+Si hay que registrar muchos redireccionamientos, puedes crear un archivo .csv y luego importarlo en el Admin. El archivo debe seguir el siguiente formato para cada uno de los redireccionamientos creados: `<Nombre>;<URL>;<Tipo>;<Activo>;<Tema>;<Verbo>;<Valor>`.
+
+- **Nombre**: define el título del redireccionamiento. Los valores posibles son `término` o `filtro`.
+- **URL:** URL del redireccionamiento.
+- **Tipo:**  regla de activación. Los valores posibles son `y` u `o`.
+- **Activo:** condición de activación del redireccionamiento. Los valores posibles son `true` o `false`.
+- **Tema:** atributo de búsqueda. Los valores posibles son `term` para el redireccionamiento de términos o `brand`, `category`, `department`, `sellername` y `subcategory` para el redireccionamiento de filtros.
+- **Verbo:** opción de inclusión del **Tema**. Los valores posibles son `es` o `contiene`.
+- **Valor:** valor del término o del filtro.
+
+Para importar el archivo, siga las instrucciones a continuación.
+
+1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda en la parte superior de la página.
+2. En **Intelligent Search**, haz clic en **Redireccionamientos**.
+3. Haz clic en el botón <i class="fas fa-plus"></i> `Importar CSV`.
diff --git a/docs/tutorials/es/configuring-samsung-pay-as-a-payment-method.md b/docs/tutorials/es/configuring-samsung-pay-as-a-payment-method.md
index 6608234bf..33803a8fe 100644
--- a/docs/tutorials/es/configuring-samsung-pay-as-a-payment-method.md
+++ b/docs/tutorials/es/configuring-samsung-pay-as-a-payment-method.md
@@ -3,8 +3,8 @@ title: 'Configurar Samsung Pay como medio de pago '
 id: 5Yj9rgzOCVYuGmAumQlfpP
 status: PUBLISHED
 createdAt: 2020-08-26T13:40:16.356Z
-updatedAt: 2023-03-29T01:17:07.597Z
-publishedAt: 2023-03-29T01:17:07.597Z
+updatedAt: 2024-07-24T13:36:58.723Z
+publishedAt: 2024-07-24T13:36:58.723Z
 firstPublishedAt: 2020-08-26T16:30:52.180Z
 contentType: tutorial
 productTeam: Financial
@@ -15,27 +15,23 @@ legacySlug: configurar-samsung-pay-como-medio-de-pago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En este tutorial, enseñaremos cómo configurar una cartera digital Samsung Pay como un medio de pago. 
+En VTEX puedes utilizar la cartera digital Samsung Pay como medio de pago en tu tienda.
 
-El primer paso es configurar el conector de Adyen —afiliación de gateway que procesa los pagos realizados a través de Samsung Pay— en su tienda. Usted puede ver el paso a paso completo para realizar esa acción [aquí](https://help.vtex.com/es/tutorial/como-configurar-o-gateway-adyen-na-vtex--tutorials_2337?locale=es "aquí").
+En primer lugar, debes configurar el proveedor de pagos [Adyen](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3--7xAz67E2Eg63LWCQNjVdwv) en tu tienda, ya que será el responsable de procesar los pagos. recibido a través de Samsung Pay.
 
-A continuación, configure el medio de pago en cuestión. 
+Después debes configurar Samsung Pay de acuerdo con los pasos a continuación:
 
 Siga las instrucciones:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. Asegúrese de estar en la pestaña __Planes de pago__.
-3. Al lado de la barra de búsqueda, haga clic en el __botón verde “+”__.
-4. En la sección “Otro”, haga clic en la opción __Samsung Pay__.
-5. Al inicio de la página, defina un nombre en el campo __Nombre de la Regla__.
-6. Debajo, haga clic en el botón __Status__ para activar la regla.
-7. En Proceso con la afiliación, seleccione la opción __Adyen__
-8. Si es necesario, seleccione el servicio de __Antifraude__ que será utilizado.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en la opción __Samsung Pay__.
+4. Active la condición en el campo __Status__.
+5. En __Procesar con proveedor__, seleccione la opción __Adyen__.
+6. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+7. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Haga clic en `Guardar`.
 
-De esa manera, usted habrá realizado la configuración más básica del medio de pago. 
+Para establecer condiciones especiales en Samsung Pay, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
-Sin embargo, aún existe la opción de __definir las condiciones especiales de pago__, estas son reglas específicas para Samsung Pay que solo se aplican en determinados contextos definidos por periodo, país, política comercial (canal de ventas), condición comercial o nombre de una cuenta. 
-
-Solamente necesita hacer clic en el botón blanco __“Condición Especial”__ y seleccionar el contexto que desea especificar. Es importante recordar que es posible definir más de una condición especial por medio de pago. Para saber más detalles, revise el [tutorial sobre cómo configurar cada una de las condiciones especiales de pago](https://help.vtex.com/es/tutorial/condicoes-especiais--tutorials_456?locale=es "tutorial sobre cómo configurar cada una de las condiciones especiales de pago").
-
-Si eso no es necesario, finalice la configuración haciendo clic en el botón __“Salva”__ para guardar los ajustes.
+Después de seguir los pasos indicados, Samsung Pay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
new file mode 100644
index 000000000..57517ba93
--- /dev/null
+++ b/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
@@ -0,0 +1,51 @@
+---
+title: 'Configurar la asignación de sellers a organizaciones compradoras (B2B)'
+id: 3VJtKNbLpVAl71uVdaOqpE
+status: PUBLISHED
+createdAt: 2023-12-21T18:05:34.497Z
+updatedAt: 2024-06-06T16:46:09.065Z
+publishedAt: 2024-06-06T16:46:09.065Z
+firstPublishedAt: 2023-12-21T18:07:21.012Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configurar-la-asignacion-de-sellers-a-organizaciones-compradoras-b2b-xky
+locale: es
+legacySlug: configurar-la-asignacion-de-sellers-a-organizaciones-compradoras-b2b-xky
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Fabricantes y distribuidores desempeñan un papel fundamental en el proceso de compras entre empresas (B2B). En determinados escenarios, como en el ámbito de los marketplace, las características operacionales de estos fabricantes y distribuidores pueden llevar a conflictos en los canales de compra. Aquí tienes algunos ejemplos:
+
+* Fabricantes: tienen un amplio conocimiento de sus productos y de la gestión de su cartera, pero necesitan crear portales de venta para gestionar mejor los procesos de sell in (venta de productos del fabricante al distribuidor) y sell out (venta del distribuidor al consumidor final).
+* Distribuidores: se encargan de actuar directamente con las organizaciones compradoras y cuentan con capacidades complementarias, como la concesión de créditos, la capacitación masiva y una amplia red de distribución, pero optan por desarrollar múltiples portales de venta propios.
+
+En este contexto, la organización compradora necesita acceder a diferentes canales y el proceso de compra se fragmenta y se vuelve ineficaz.
+
+En VTEX, las organizaciones compradoras (B2B) pueden crear una regla de asignación que les permita realizar compras de productos de manera selectiva, enfocándose solamente en sellers que atiendan sus necesidades operativas o logísticas.
+
+Para asignar sellers a una determinada organización compradora sigue los pasos a continuación:
+<ol>
+<li>En el Admin VTEX, accede a <b>Apps > Organizaciones y centros de costos B2B > Organizaciones</b>, o ingresa <b>Organizaciones</b> en la barra de búsqueda de la parte superior de la página.</li>
+<li>En la pestaña <b>Organizaciones</b>, haz clic en el nombre de la organización compradora deseada.</li>
+
+![Organizacion](//images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/998262e5b1c591ad1aa65ed5ca7f40b3/ORGANIZACOES_-_ES.jpg)
+
+<li>En la pestaña <b>Sellers</b>, en <b>Disponible</b>, selecciona los sellers deseados.</li>
+
+![Detalles Organización](//images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/cf1fba7aa6959bccfcb91e87a20393ef/ORGANIZACOES-DETALHES_-_ES__com_clique_.jpg)
+
+<li>Haz clic en el botón <b>AGREGAR A LA ORG.</b></li>
+
+![Detalles Organización 2](//images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/1ab4089682ebc12c99c766be8de507a4/ORGANIZACOES-DETALHES2_-_ES.jpg)
+
+<li>Haz clic en el botón <b>Guardar</b>.</li>
+
+A partir de ahora, cada vez que la organización realice una búsqueda en la plataforma VTEX, solamente se mostrarán los productos de los sellers que tenga asignados.
+</ol>
+
+<div class="alert alert-warning">
+Las organizaciones compradoras que opten por no crear asignaciones de sellers, podrán acceder igualmente a la información y realizar compras a todos los sellers disponibles en el marketplace.
+</div>
+
+Para más información sobre cómo integrar un nuevo seller, consulta el artículo [Agregar seller](https://help.vtex.com/es/tutorial/adicionar-seller--tutorials_392).
diff --git a/docs/tutorials/es/configuring-seo-in-your-store.md b/docs/tutorials/es/configuring-seo-in-your-store.md
new file mode 100644
index 000000000..b4fd21a2f
--- /dev/null
+++ b/docs/tutorials/es/configuring-seo-in-your-store.md
@@ -0,0 +1,62 @@
+---
+title: 'Configurar SEO en la tienda'
+id: 1sKskEsjUSvgHyqM8oknVR
+status: PUBLISHED
+createdAt: 2024-04-29T19:07:56.533Z
+updatedAt: 2024-05-03T18:39:56.071Z
+publishedAt: 2024-05-03T18:39:56.071Z
+firstPublishedAt: 2024-04-29T19:26:31.511Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: YRJ73j8mt38D5TUleocQB
+slug: configurar-seo-en-la-tienda
+locale: es
+legacySlug: configurar-seo-en-la-tienda
+subcategory: 7ogirQ8NClawO2X6xdgCKc
+---
+
+SEO (Search Engine Optimization) es una de las estrategias más importantes para que tu sitio web logre un buen posicionamiento orgánico en las páginas de resultados de los motores de búsqueda. La configuración de tags, metatags y faviconos es parte del conjunto de estrategias para optimizar el desempeño de tu sitio web.
+
+La tag de título ayuda a definir el tema de la página para los motores de búsqueda e influye directamente en los clics de los usuarios en los resultados de búsqueda. La tag de descripción les da a los usuarios una idea de lo que pueden encontrar en el sitio web. La metatag robots controla el comportamiento de rastreo e indexación de los mecanismos de búsqueda.
+
+En todas las tiendas VTEX IO se pueden configurar estos parámetros de forma nativa siguiendo los pasos descritos a continuación.
+
+### Instrucciones
+
+#### Tag de título, tag de descripción y metatag robots
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Tienda**.
+2. Haz clic en la pestaña **General**.
+3. Rellena los campos según se describe a continuación:
+
+  - **Nombre de la tienda**: ingresa el nombre de tu tienda.
+  - **Activar la configuración por vinculación**: esta opción solo es válida para tiendas que tienen varios bindings. Activarla te permite configurar ajustes específicos de tags y metatags para cada binding de la tienda. Las tiendas que tienen un solo binding no tienen que activar esta opción.
+  - **Tag de título predeterminada**: ingresa una descripción breve y que incluya palabras clave relevantes. El valor de esta tag aparece en la parte superior de la barra de título del navegador cuando alguien visita una página del sitio web de tu tienda.
+  - **Metatag de descripción**: ingresa una descripción breve del contenido de la página que sea informativa y contenga palabras clave relevantes.
+  - **Metatag robots**: define cómo los motores de búsqueda deben rastrear e indexar una página específica. Los valores predeterminados son `index, follow`. Para ver los otros valores compatibles con Google, consulta la [lista de reglas válidas](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag?hl=es-419#directives).
+
+  ![seo-es](//images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/614ecc04bb0994fbab579bc917aeaafa/seo-es.png)
+
+#### Faviconos
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Tienda**.
+2. Haz clic en la pestaña **General**.
+3. Haz clic en **Agregar**.
+
+  ![favicon-es](//images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/1befbd1af3f398f6ef7d7bc575f32f5b/favicons-es.png)
+
+4. Rellena la pantalla que se abre según se describe a continuación:
+
+     - **Relación del favicono**: define la relación entre la URL configurada en el campo *Href del favicono* y el favicono del sitio web. Por ejemplo, asignar el valor `icon` indica que la URL configurada está relacionada al ícono del sitio web.
+     - **Tipo de multimedia del favicono** (opcional): especifica el tipo del favicono siguiendo los estándares de HTML y de W3C. Para más información, consulta la documentación [HTML Favicon](https://www.w3schools.com/html/html_favicon.asp).
+     - **Tamaño del favicono** (opcional): indica las dimensiones del favicono en formato {anchura}x{altura}. Por ejemplo: 180x180.
+     - **Href del favicono**: ingresa la URL completa que apunta al lugar donde se almacena el archivo del favicono.
+
+    A continuación se muestra un ejemplo:
+
+    ![relacao-favicon-es](//images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/a400fa8cb893d6012d400210198b3963/relacao-favicon-es.png)
+
+5. Haz clic en **Aplicar** para que la configuración se refleje en tu tienda. Esto puede demorar unos minutos.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">El campo <strong>Ruta del término de búsqueda</strong> es un ajuste heredado que era compatible con <code>vtex.search-resolver@0.x</code>.
+</div>
diff --git a/docs/tutorials/es/configuring-shipping-promotions.md b/docs/tutorials/es/configuring-shipping-promotions.md
index 9f64ef683..679e8684c 100644
--- a/docs/tutorials/es/configuring-shipping-promotions.md
+++ b/docs/tutorials/es/configuring-shipping-promotions.md
@@ -40,7 +40,7 @@ Si habilita la opción **Aplicar el descuento solo para la opción de envío má
 ![Aplicar el descuento solo para la opción de envío más barata - ES](//images.contentful.com/alneenqid6w5/4dO4pM8BrIVl4r27K5xgqT/d8a5a9992eb31f05591aaf88c79f4268/image.png)
 
 #### Resultado
-![saggincaso1.2](https://images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
+![saggincaso1.2](//images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
 
 ### Escenario 2
 
@@ -50,27 +50,27 @@ Si desactiva la opción **Aplicar el descuento solo para la opción de envío m
 ![Nenhum frete selecionado - ES](//images.contentful.com/alneenqid6w5/7a7lDpKd56Md9xIlJQF9tX/4a3dc46a38e0d43a3d4947af0368c191/image.png)
 
 #### Resultado
-![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Escenario 3
 
 Si solo habilita la opción **Tipo de carga** y selecciona los tipos de flete deseados, el descuento de flete se aplicará a todos los tipos de flete seleccionados.
 
 #### Configuración
-![Tipo de carga - ES](https://images.ctfassets.net/alneenqid6w5/MkF8ImPwJ04FtN5DoJINV/e72d10be17632100b45beba4ba056d50/image.png)
+![Tipo de carga - ES](//images.ctfassets.net/alneenqid6w5/MkF8ImPwJ04FtN5DoJINV/e72d10be17632100b45beba4ba056d50/image.png)
 
 #### Resultado
-![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Escenario 4
 
 Si habilita las opciones **Tipo de carga** y **Aplique el descuento solo cuando el cliente seleccione uno de los transportistas anteriores** y selecciona los tipos de flete deseados, el descuento de flete se aplicará a todos los tipos de flete seleccionados solamente cuando el cliente elija el tipo de flete en el checkout.
 
 #### Configuración
-![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - ES](https://images.ctfassets.net/alneenqid6w5/3asUPbHRyLXbY57HqCahA0/d042659aba597af795a1c6e1ae5ede4e/image.png)
+![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - ES](//images.ctfassets.net/alneenqid6w5/3asUPbHRyLXbY57HqCahA0/d042659aba597af795a1c6e1ae5ede4e/image.png)
 
 #### Resultado
-![saggincaso3.2](https://images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
+![saggincaso3.2](//images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
 
 En resumen, la casilla **Aplique el descuento solo cuando el cliente seleccione uno de los transportistas anteriores** se utiliza para aplicar el descuento solamente cuando se selecciona la transportadora.
 
diff --git a/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
new file mode 100644
index 000000000..cbddd5779
--- /dev/null
+++ b/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
@@ -0,0 +1,88 @@
+---
+title: 'Configurar inicio de sesión con Apple ID (Beta)'
+id: 5qprgEmHYfPTghnYwm0KrV
+status: PUBLISHED
+createdAt: 2023-09-05T17:38:23.553Z
+updatedAt: 2023-09-05T18:22:20.252Z
+publishedAt: 2023-09-05T18:22:20.252Z
+firstPublishedAt: 2023-09-05T18:22:20.252Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configurar-inicio-de-sesion-con-apple-id-beta
+locale: es
+legacySlug: configurar-inicio-de-sesion-con-apple-id-beta
+subcategory: 5uXA9a0laSLMkfbv6jQRDS
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>.</p>
+</div>
+
+En VTEX, no es necesario crear una cuenta o iniciar sesión para realizar una compra. Sin embargo, si el cliente desea editar los datos informados durante la primera compra, debe comprobar que el email en cuestión le pertenece.
+
+La funcionalidad nativa de la plataforma ofrece opciones de inicio de sesión con email y contraseña y con código de acceso enviado por email al cliente. También ofrecemos integraciones opcionales nativas con Apple ID, [Google y Facebook](https://help.vtex.com/es/tutorial/integracion-google-y-facebook-en-smartcheckout--tutorials_513) que se pueden utilizar después de configurarlas. Esta guía explica la configuración necesaria para activar el inicio de sesión con [Apple ID](https://support.apple.com/es-mx/apple-id) en tu tienda:
+
+- [Prerrequisitos](#prerrequisitos)
+- [Registrarse en Apple](#registrarse-en-apple)
+- [Rellenar la información de autenticación](#rellenar-la-informacion-de-autenticacion)
+- [Probar el inicio de sesión con Apple ID](#probar-el-inicio-de-sesion-con-apple-id)
+- [Limitaciones](#limitaciones)
+
+## Prerrequisitos
+
+Antes de empezar a configurar el inicio de sesión con Apple ID en tu tienda, debes tener un [Apple ID](https://support.apple.com/es-mx/apple-id) y estar inscrito en el [Apple Developer Program](https://developer.apple.com/programs/).
+
+## Registrarse en Apple
+
+Para configurar la integración de inicio de sesión con Apple, debes crear credenciales de OAuth 2.0 (protocolo utilizado para la integración) en el servicio. Para crear las credenciales, sigue las instrucciones de nuestra guía para desarrolladores [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login).
+
+## Rellenar la información de autenticación
+
+Después de registrarte en Apple, debes activar la opción de inicio de sesión con ese proveedor en tu tienda siguiendo las instrucciones a continuación. Debes tener listas las credenciales obtenidas en el paso de registro.
+
+1. En la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** que tiene la inicial de tu email.
+2. Haz clic en **Configuración de la cuenta > Autenticación**.
+
+    Se te redirigirá a la pestaña **Tienda virtual** de la página **Autenticación**, que lista los métodos de inicio de sesión disponibles en tu tienda.
+
+3. En la fila **Apple**, haz clic en `Configurar`.
+4. Rellena los campos de configuración con las [credenciales registradas previamente en Apple](#registrarse-en-apple):
+
+    - **Key ID:** identificación de clave privada generada por Apple que VTEX utilizará para generar el [OAuth client secret](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/).
+    - **Team ID:** identificación de tu equipo en[ Apple Developer Portal](https://developer.apple.com/).
+    - **Service ID:** identificación de tu servicio en Apple, que se utilizará como el [OAuth `client_id`](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/).
+    - **P8 certificate:** clave privada guardada en un archivo de texto en formato `.p8`. Apple lo genera una sola vez durante la creación de la clave.
+
+    Para más información sobre cómo obtener estas credenciales, consulta nuestra guía para desarrolladores [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login).
+
+    ![apple-id-setup-es](//images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/83719fc4ecc831b785e06d485eb13188/apple-id-setup-pt.png)
+
+5. Haz clic en `Guardar`.
+6. Haz clic en `Proveedores de tienda virtual` para volver a la página anterior.
+7. Haz clic en el _botón de alternancia_ <i class="fas fa-toggle-on"></i> para activar el uso de Apple como proveedor de inicio de sesión.
+
+## Probar el inicio de sesión con Apple ID
+
+Ahora que todo está listo, puedes probar la configuración. Recomendamos que realices las pruebas con la URL final que tus usuarios utilizarán para acceder a tu tienda. Al intentar iniciar sesión, la opción de utilizar el Apple ID debe estar disponible.
+
+1. Accede al sitio web de tu tienda y haz clic en `Entrar` para iniciar sesión.
+2. Haz clic en `Entrar con Apple`. Se te redirigirá a la pantalla de inicio de sesión de Apple.
+3. Ingresa tu ID y contraseña de Apple.
+4. Completa la autenticación de dos factores, si se te solicita.
+5. Escoge si deseas compartir tu email con la aplicación u [Ocultar mi correo](https://support.apple.com/es-mx/HT210425) y haz clic en `Continuar`. Recomendamos compartir el email, ya que hay [limitaciones](#limitaciones) respecto al email oculto en VTEX.
+
+<div class="alert alert-info">
+  <p>La opción de compartir u ocultar el email solo aparece la primera vez que se accede a la tienda con el Apple ID. Después, solo es necesario hacer clic en <code>Continuar</code>. Para redefinir la opción de compartir el email, accede a la <a href="https://appleid.apple.com/mx/">página de administración de Apple ID</a>, revoca la autorización de la tienda y vuelve a iniciar sesión.</p>
+</div>
+
+Luego de eso, estarás autenticado en la tienda.
+
+## Limitaciones
+
+Ten en cuenta las limitaciones actuales del inicio de sesión con Apple ID en tiendas VTEX:
+
+- Message Center no es compatible con emails de usuarios Apple; en otras palabras: los emails configurados en la herramienta no se enviarán a usuarios que inicien sesión con un Apple ID.
+- Si el usuario escoge la opción de Apple [Ocultar mi correo](https://support.apple.com/es-mx/HT210425), VTEX generará una nueva cuenta cada vez que el usuario inicie sesión.
+
+    Esto significa que si alguien inicia sesión con un email y contraseña primero, realiza un pedido y luego inicia sesión con un Apple ID que tiene la opción de ocultar el email activada, VTEX creará una cuenta separada. La nueva cuenta no tendrá relación con la cuenta original y no permitirá acceder al historial de pedidos anteriores o a otra información del usuario. Esta acción no se puede deshacer.
diff --git a/docs/tutorials/es/configuring-stripe-gateway-affiliation.md b/docs/tutorials/es/configuring-stripe-gateway-affiliation.md
index efff1b89d..6478b07a1 100644
--- a/docs/tutorials/es/configuring-stripe-gateway-affiliation.md
+++ b/docs/tutorials/es/configuring-stripe-gateway-affiliation.md
@@ -3,8 +3,8 @@ title: 'Configurar la afiliación Stripe'
 id: fwF2wk2FQKrODrWWkvSLO
 status: PUBLISHED
 createdAt: 2021-10-25T16:01:40.789Z
-updatedAt: 2023-03-22T19:17:05.286Z
-publishedAt: 2023-03-22T19:17:05.286Z
+updatedAt: 2024-04-25T12:58:35.923Z
+publishedAt: 2024-04-25T12:58:35.923Z
 firstPublishedAt: 2021-10-25T17:34:52.274Z
 contentType: tutorial
 productTeam: Financial
@@ -32,30 +32,40 @@ Para procesar sus pagos con Stripe, necesita:
 
 Después de instalar el conector de Stripe, sigue los pasos a continuación para la configuración en la plataforma VTEX.
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En **Afiliaciones**, haga clic en el icono "**+**".
-3. Busca el conector **StripeConnector** y haz clic en él.
-4. En la siguiente página, rellena los campos con la siguiente información:
-<ol><br/>
-  <li><strong>Application Key:</strong> Clave publicable que has obtenido en el <a href="https://dashboard.stripe.com/">dashboard de tu cuenta de Stripe</a>.
-  <li><strong>Application Token:</strong> Clave secreta que has obtenido en el <a href="https://dashboard.stripe.com/">dashboard de tu cuenta de Stripe</a>.
-</ol>
-5. Haz clic en **Guardar**.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __StripeConnector__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellena los campos con la siguiente información:
+<br>
+<ul>
+<br>
+    	<li><b>Clave de aplicación</b>: Clave publicable que has obtenido en el <a href="https://dashboard.stripe.com">dashboard de tu cuenta de Stripe</a>.</li>
+    	<li><b>Token de aplicación</b>: Clave secreta que has obtenido en el <a href="https://dashboard.stripe.com">dashboard de tu cuenta de Stripe</a>.</li>
+</ul>
+5. Haga clic en __Guardar__.
 
 Después de realizar la configuración en el ambiente VTEX, también debes configurar el *webhook* en tu cuenta de Stripe.
 
 1. Accede al [dashboard de tu cuenta de Stripe](https://dashboard.stripe.com/).
-2. Haz clic en el botón **Desarrolladores**.
-3. Haz clic en la pestaña **Webhooks**.
-4. Haz clic en el botón **Agregar un punto de conexión**.
-5. En el campo **URL del punto de conexión**, introduce la URL del *endpoint* de tu tienda VTEX en el formato `https://{nombre-de-la-cuenta}.myvtex.com/_v/notifications` sustituyendo `{nombre de la cuenta}` por el nombre de tu cuenta VTEX.
-6. Haz clic en **+ Seleccionar eventos**.
-7. Añade los eventos que deben ser escuchados.
-8. Haz clic en **Agregar punto de conexión**.
+2. Haga clic en el botón __Desarrolladores__.
+3. Haga clic en la pestaña __Webhooks__.
+4. Haga clic enn el botón __Añadir un punto de conexión__.
+5. En el campo __URL del punto de conexión__, introduce la URL del *endpoint* de tu tienda VTEX en el formato `https://{nombre-de-la-cuenta}.myvtex.com/_v/notifications` sustituyendo `{nombre de la cuenta}` por el nombre de tu cuenta VTEX.
+6. Haga clic en __+ Seleccionar eventos__.
+7. Haga clic en las categorías y seleccione los eventos deseados. Si no está seguro de qué eventos agregar, comuníquese con el soporte de Stripe y ellos podrán ayudarlo con este tipo de configuración.
+8. Haga clic en __Añadir eventos__.
+9. Haga clic en __Añadir punto de conexión__.
+
+<div class="alert alert-info">
+  <p>Si deseas realizar transacciones con tarjeta de crédito en Stripe, debes abrir un ticket en Stripe de la siguiente manera:</p>
+  <p>- Solicitar la liberación de la función "raw card data", indicando que VTEX y Stripe son socios de pago.</p>
+  <p>- Enviar como archivo adjunto el VTEX AOC (Attestation of Compliance for Onsite Assessments – Service Providers). Para consultar la última versión de AOC VTEX acceda a la página de <a href="https://vtex.com/es-es/compliance/certifications">certificaciones VTEX</a> y descargue el archivo disponible en la sección PCI.</p>
+  <p>Las acciones anteriores evitarán que ocurran errores relacionados con la transmisión de datos sensibles en la integración entre Stripe y VTEX.</p>
+</div>
 
 ## Configuración de condición de pago
 
-Cuando hayas completado los pasos indicados, Stripe estará configurado en tu tienda. Así que cuando registres una condición de pago, esta estará disponible en el campo **Proceso con la afiliación** (siempre y cuando el método de pago sea compatible con Stripe).
+Cuando hayas completado los pasos indicados, Stripe estará configurado en tu tienda. Así que cuando registres una condición de pago, esta estará disponible en el campo __Proceso con la afiliación__ (siempre y cuando el método de pago sea compatible con Stripe).
 
 Para configurar condiciones de pago, accede al artículo [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455).
 
@@ -63,11 +73,12 @@ Para configurar condiciones de pago, accede al artículo [Configurar condiciones
 
 El conector Stripe te permite añadir Google Pay como método de pago en el checkout de tu tienda. Con el conector Stripe configurado, puedes añadir Google Pay siguiendo los pasos que se indican a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En **Planes de pago**, haz clic en el botón verde "**+**".
-3. Busca la condición **Google Pay** y haz clic en ella.
-4. Haz clic en el botón Status para activar esta condición de pago.
-5. Haz clic en Salva para guardar los cambios.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En __Condiciones de pago__, haz clic en el botón verde `+`.
+3. Haga clic en la opción __Google Pay__.
+4. Active la condición en el campo __Status__.
+5. En __Procesar con afiliación__, seleccione la opción __StripeConnector__.
+6. Haga clic en __Guardar__.
 
 Cuando hayas realizado estos pasos, Google Pay figurará en el *checkout* de la tienda como uno de los métodos de pago disponibles.
 
@@ -82,25 +93,25 @@ Apple Pay actualmente solo funciona en los sistemas operativos MacOs e IOS, y el
 Con el conector Stripe configurado, puedes añadir Apple Pay siguiendo los pasos que se indican a continuación:
 
 1. Acceda al [dashboard de su cuenta de Stripe](https://dashboard.stripe.com/settings/payments) en la sección de configuración de pagos.
-2. En **Configuración**, haga clic en **Métodos de pago**.
-3. Haga clic en **Apple Pay > Configurar** y luego en **Agregar a nuevo dominio**.
+2. En __Configuración__, haga clic en __Métodos de pago__.
+3. Haga clic en __Apple Pay > Configurar__ y luego en __Agregar a nuevo dominio__.
 4. Introduce el dominio público del sitio web de tu tienda.
-5. Haga clic en **Descargar archivo de verificación** para guardarlo en su dispositivo.
+5. Haga clic en __Descargar archivo de verificación__ para guardarlo en su dispositivo.
 6. Crear las credenciales [appkey e apptoken](https://help.vtex.com/es/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet#).
 7. Realice una llamada al endpoint para enviar el archivo de verificación previamente descargado, agregando las credenciales creadas y su dirección de dominio público en el encabezado (https://{{dominioPublicodoSite}}/well-known/raw/apple-developer-merchantid-domain-association).
-8. Haga clic en **Add**.
-9. Acceda al **Admin** VTEX.
-10. Haga clic en **Pagos**.
-11. Después, haga clic en **Configuración**.
-12. En la pestana **Condiciones de pago**, haga clic en el botón **+**.
-13. Haga clic en **Apple Pay**.
-14. Rellene el campo **Nombre de la regla** con un nombre de su elección para su identificación.
-15. Active la condición en el campo **Status**.
-16. En el campo **Procesar con afiliación**, selecciona la opción Stripe.
-17. Si tiene un antifraude configurado en su tienda, puede habilitarlo para esa condicione de pago marcando la casilla **Utilizar antifraude**.
+8. Haga clic en __Add__.
+9. Acceda al __Admin VTEX__.
+10. Haga clic en __Pagos__.
+11. Después, haga clic en __Configuración__.
+12. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+13. Haga clic en __Apple Pay__.
+14. Rellene el campo __Nombre de la regla__ con un nombre de su elección para su identificación.
+15. Active la condición en el campo __Status__.
+16. En el campo __Procesar con afiliación__, selecciona la opción Stripe.
+17. Si tiene un antifraude configurado en su tienda, puede habilitarlo para esa condicione de pago marcando la casilla __Utilizar antifraude__.
 18. Elige si los pagos será con o sin cuotas.
 19. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condicoes-especiais).
-20. Haga clic en **Guardar**.
+20. Haga clic en __Guardar__.
 
 Cuando hayas realizado estos pasos, Apple Pay figurará en el checkout de la tienda como uno de los métodos de pago disponibles.
 
diff --git a/docs/tutorials/es/configuring-the-scheduled-delivery.md b/docs/tutorials/es/configuring-the-scheduled-delivery.md
index eb1a73936..02792acac 100644
--- a/docs/tutorials/es/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/es/configuring-the-scheduled-delivery.md
@@ -29,7 +29,7 @@ En **Inventario y envío**, acceda **Paneles** y haga clic en la **Transportador
 
 En **Tipo de Entrega**, haga clic en **Entrega agendada**.
 
-![entrega-agendada es](https://images.ctfassets.net/alneenqid6w5/PF5fC5oPoiAmsK0KAW2G2/aee508bb7392ef5c0dfd62d3a607f25d/entrega-agendada_es.png)
+![entrega-agendada es](//images.ctfassets.net/alneenqid6w5/PF5fC5oPoiAmsK0KAW2G2/aee508bb7392ef5c0dfd62d3a607f25d/entrega-agendada_es.png)
 Para compreender mejor sobre la cumplimentación del resto de los campos, vea también nuestro documento de cómo [registrar una transportadora](http://help.vtex.com/es/tutorial/gestionar-transportista).
 
 
@@ -44,7 +44,7 @@ En esta estructura, tenemos los siguientes datos:
 Utilizando igual ejemplo de la tienda más arriba, sigue la configuración de la transportadora según su demanda:
 
 
-![entrega-agendada-exemplo es](https://images.ctfassets.net/alneenqid6w5/1kwunX9pCYUUQUSQ8QO42u/bab6a450319e8ddcd081db0aebb9b9fe/entrega-agendada-exemplo_es.png)
+![entrega-agendada-exemplo es](//images.ctfassets.net/alneenqid6w5/1kwunX9pCYUUQUSQ8QO42u/bab6a450319e8ddcd081db0aebb9b9fe/entrega-agendada-exemplo_es.png)
 
 
 Suponiendo que el Inventario tiene 2 días de plazo, el Muelle 1 día y la Tabla de Flete 5 días, el primer día que se pondrá a disposición será 8 días después de la fecha en que se está realizando el pedido y cómo el Tiempo máximo de entrega es de 10 días, el último día disponible para la elección será el 18º día después de la fecha en que se está efectuando el pedido.
diff --git a/docs/tutorials/es/configuring-the-store-domain.md b/docs/tutorials/es/configuring-the-store-domain.md
new file mode 100644
index 000000000..e56035df4
--- /dev/null
+++ b/docs/tutorials/es/configuring-the-store-domain.md
@@ -0,0 +1,103 @@
+---
+title: 'Configurar dominio de la tienda'
+id: tutorials_2450
+status: PUBLISHED
+createdAt: 2017-04-27T21:55:00.603Z
+updatedAt: 2024-03-12T19:53:14.012Z
+publishedAt: 2024-03-12T19:53:14.012Z
+firstPublishedAt: 2017-04-27T23:03:51.625Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configurar-dominio-de-la-tienda
+locale: es
+legacySlug: configuracion-de-dominios-del-license-manager
+subcategory: yMp6sKDiJEi66CGAIQ4ma
+---
+
+La configuración relacionada con el dominio es necesaria para que una dirección web se dirija correctamente a una tienda VTEX. En esta guía explicamos lo siguiente:
+
+* [Estructura de la dirección de la tienda](#estructure-de-la-direccion-de-la-tienda)
+* [Reglas para el host principal](#reglas-para-el-host-principal)
+* [Cómo registrar un nuevo host](#registrar-nuevo-host)
+* [Cómo cambiar el host de una tienda activa](#cambiar-host)
+
+## Estructura de la dirección de la tienda
+
+ La dirección de la tienda se compone de los elementos ilustrados a continuación:
+
+![url-diagram-es](//images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/70d9e55fc1f035bfb1b8733aa0cfdec4/url-diagram-es.png)
+
+| Elemento | Descripción | Ejemplo |
+|---|---|---|
+| Protocolo | Protocolo de comunicación utilizado en internet. | `https://` |
+| Subdominio | Prefijo añadido al nombre de dominio. | `www` |
+| Dominio | Nombre único que sirve para ubicar e identificar tu tienda en la web. | `mystore` |
+| Dominio de nivel superior (TLD) | Sufijo después del punto final de un nombre de dominio. | `com` |
+| Nombre de dominio / Dominio puro / Dominio raíz | Dominio + dominio de nivel superior. | `mystore.com` |
+| Host | Subdominio + dominio + dominio de nivel superior. | `www.mystore.com` |
+
+Una vez definido el dominio de tu tienda, debes configurar el host principal en el Admin VTEX para establecer la comunicación entre la dirección y el contenido de la tienda.
+
+## Reglas para el host principal
+
+Antes de continuar con la configuración de las direcciones de tu tienda, toma en cuenta las siguientes prácticas para garantizar una implementación exitosa:
+* **Proveedores de CDN:** VTEX utiliza dos proveedores de CDN en las tiendas: **Cloudfront** y **Azion**. Es importante que el dominio de tu tienda no esté registrado en estos servicios al momento de realizar el apuntamiento. De lo contrario, se producirá un fallo en el aprovisionamiento de CDN de tu tienda y, en consecuencia, en el go live. Por lo tanto, si tienes el dominio de la tienda registrado en la plataforma Cloudfront o Azion, remueve el registro antes de apuntar el DNS a VTEX.
+* **Dirección principal:** La tienda debe tener un único host principal, que apuntará a los servidores de VTEX. Este host **debe contener un subdominio**, que puede ser `www` u otros.
+* **Direcciones adicionales:** cualquier dirección adicional, ya sea con un dominio diferente o una versión sin subdominios, se debe redirigir al único host principal, según se describe en Redirecciones.
+
+### Ejemplos de host
+
+Consulta los siguientes ejemplos y observa los que se pueden utilizar como host principal:
+
+| Ejemplo de host | Puede utilizarse como host: sí (✔️) o no (❌) | Explicación |
+|---|---|---|
+| `www.mitienda.com` | ✔️ | Contiene el subdominio `www`. |
+| `mitienda.com` | ❌ | No contiene subdominio. Para configurar el acceso a través de esta dirección, hay que configurar un host con un subdominio de tipo `www.mitienda.com` y, luego, crear una redirección. Consulta Configurar acceso sin www para más detalles. |
+| `tienda.mimarca.com` | ✔️ | Contiene el subdominio tienda. |
+| `www.tienda.mimarca.com` | ✔️ | Contiene dos subdominios: `www` y `tienda`. |
+
+### Redirecciones
+
+Para garantizar el acceso a tu tienda a través de diferentes URL, tales como `www.mitienda.com` y `mitienda.com` debes configurar un único host principal y redirigir las direcciones adicionales a la dirección principal. Para más información sobre redirecciones, consulta:
+
+* [Redirección de otras direcciones](https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ)
+* [Mejores prácticas para acceder a tienda sin www](https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278)
+
+Ten en cuenta que lo recomendado es implementar un único host en tu tienda.
+
+## Registrar nuevo host
+
+Para registrar un nuevo host, el mismo debe cumplir con las prácticas descritas en la sección [Reglas para el host principal](#reglas-para-el-host-principal). Sigue las instrucciones a continuación:
+
+1. En la barra superior del Admin VTEX, haz clic en el avatar de tu perfil que tiene la inicial de tu email.
+2. Haz clic en **Configuración de la cuenta**.
+3. Haz clic en **Cuenta**.
+4. Haz clic en la pestaña **Tiendas**.
+5. Haz clic en el botón de acciones correspondiente a la tienda en que deseas registrar el host y luego en `Acciones`.
+6. Ingresa el host en el campo **Hosts**. Por ejemplo, `www.mitienda.com`.
+7. Haz clic en el botón `Agregar`.
+8. Haz clic en el botón `Guardar`.
+
+Después de estos pasos, puedes [configurar el apuntamiento de DNS a VTEX](https://help.vtex.com/es/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
+
+<div class="alert alert-warning">
+  <p>Para las tiendas<a href="https://www.faststore.dev/"> FastStore</a>, también es necesario configurar una dirección con el subdominio <code>secure</code>. Para más información, consulta la guía <a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns">Configuring external DNS for a custom domain</a>.</p>
+</div>
+
+<div class="alert alert-danger">
+  <p>Si tu operación tiene más de una cuenta VTEX o <a href="https://help.vtex.com/es/tutorial/crear-subconta-multitienda-multidominio--tutorials_510">subcuentas</a>, no cambies el host de una cuenta a otra. Esto causará fallas en varias partes de tu tienda.</p>
+</div>
+
+## Cambiar host
+
+La plataforma VTEX admite cambios de host sin efectos adversos. Si necesitas cambiar el host de la tienda, sigue los pasos a continuación:
+
+1. Crea nuevas entradas de host para la tienda deseada, según los pasos descritos en [Registrar nuevo host](#registrar-nuevo-host). En este punto, el DNS del nuevo dominio aún no debe apuntar a VTEX.
+2. En el Admin VTEX, verifica la configuración de Checkout en **Configuración de la tienda > Storefront > Checkout**, según se describe en [Configurar template en SmartCheckout](https://help.vtex.com/es/faq/configurar-template-no-smartcheckout/). Este paso es esencial para que Checkout siga funcionando después del cambio.
+
+    Debes comprobar que los sitios web configurados estén asociados a la cuenta registrada en **Configuración de la cuenta > Cuentas**. Para más información, consulta [Gestión de la cuenta](https://help.vtex.com/es/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq).
+
+3. Apunta el DNS del nuevo dominio a VTEX. En esta serie puedes encontrar más información sobre el [apuntamiento de DNS](https://help.vtex.com/es/tutorial/configurando-o-apontamento-de-dns-para-a-vtex/).
+4. Si su tienda utiliza [VTEX IO - Store Framework](https://developers.vtex.com/docs/guides/storefront-implementation) o [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), ponte en contacto con el [soporte VTEX](https://help.vtex.com/es/support) y solicita el apuntamiento interno. La solicitud debe incluir el nuevo dominio. Una vez abierto el ticket, el equipo de soporte tiene hasta tres días laborables para analizar la configuración y realizar el apuntamiento.
+5. Después de confirmar el apuntamiento interno y la propagación de DNS del nuevo host, elimina hosts antiguos y mantén solo el nuevo.
diff --git a/docs/tutorials/es/configuring-tuna-gateway-affiliation.md b/docs/tutorials/es/configuring-tuna-gateway-affiliation.md
index 3a157f212..471b1c9ef 100644
--- a/docs/tutorials/es/configuring-tuna-gateway-affiliation.md
+++ b/docs/tutorials/es/configuring-tuna-gateway-affiliation.md
@@ -3,8 +3,8 @@ title: 'Configurar la afiliación a la Tuna'
 id: 5Db0j4pE76ma9pUvYuAhfF
 status: PUBLISHED
 createdAt: 2021-07-07T14:47:34.162Z
-updatedAt: 2023-03-26T21:51:52.610Z
-publishedAt: 2023-03-26T21:51:52.610Z
+updatedAt: 2024-01-23T21:47:01.684Z
+publishedAt: 2024-01-23T21:47:01.684Z
 firstPublishedAt: 2021-07-07T14:57:45.358Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: configurar-la-afiliacion-a-la-tuna
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX, puede configurar su tienda con la afiliación de gateway Tuna para recibir pagos a través de: boleto, tarjetas de débito y crédito, PIX y Bitcoin.
+En VTEX, puede configurar su tienda con el gateway Tuna para recibir pagos a través de: boleto, tarjetas de débito y crédito, PIX y Bitcoin.
 
 <div class="alert alert-warning">
   La integración de su tienda con Tuna se realiza a través de una <b>Application Key</b> y un <b>Application Token.</b> Los datos de acceso para obtener esta información y habilitar la configuración en VTEX se le enviarán después de crear su cuenta. Para esto, debe rellenar <a href="https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform">este formulario</a> y esperar la respuesta de Tuna con más detalles.
@@ -23,9 +23,9 @@ En VTEX, puede configurar su tienda con la afiliación de gateway Tuna para reci
 
 Después de crear su cuenta y obtener la __Application Key__ y el __Application Token__, siga los pasos a continuación para configurar Tuna en su tienda:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en el conector __Tuna__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Tuna__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Tuna.
 5. En __Captura de pago automática__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/configuring-vtex-marketplace.md b/docs/tutorials/es/configuring-vtex-marketplace.md
index 4645d24d7..88bd2e1ac 100644
--- a/docs/tutorials/es/configuring-vtex-marketplace.md
+++ b/docs/tutorials/es/configuring-vtex-marketplace.md
@@ -3,12 +3,12 @@ title: 'Configurar marketplaces VTEX'
 id: 7splyp5MqIyt2Iyz5jsNzb
 status: PUBLISHED
 createdAt: 2022-01-26T21:27:16.808Z
-updatedAt: 2023-04-17T22:04:41.917Z
-publishedAt: 2023-04-17T22:04:41.917Z
+updatedAt: 2024-05-23T15:18:17.648Z
+publishedAt: 2024-05-23T15:18:17.648Z
 firstPublishedAt: 2022-01-26T23:06:58.565Z
 contentType: tutorial
 productTeam: Channels
-author: 0QBQws7rk0t5Mnu8fgfUv
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: configurar-marketplaces-vtex
 locale: es
 legacySlug: configuraciones-para-marketplace-vtex
@@ -73,7 +73,7 @@ Puedes definir si la tienda del _seller_ será visible en la experiencia de comp
 - **_Seller_ identificable:** el _seller_ es visible en el _storefront_ de tu _marketplace,_ y es elegido por el consumidor durante la experiencia de compra en _buy box_.  
 - **_Seller_ no identificable (_white label_):** los _[sellers white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label)_ son cuentas franquicia en VTEX, ocultas en la experiencia de compra, y seleccionadas automáticamente por el sistema del _checkout_ para el _fulfillment_.  
 
-Para agregar un _seller_ no identificable (_seller white label_), es necesario tener este modelo previsto en el contrato con VTEX. Una vez acordado un contrato con el representante de ventas de VTEX responsable de tu _marketplace_, solicita la adición de una cuenta franquicia por email a `sales-ops-br@vtex.com.br`. Todas las cuentas franquicia se crean como un _seller white label_, y no es posible cambiar el tipo de _seller_ después de su creación. Obtén más información en [Agregar sellers](https://help.vtex.com/es/tutorial/adding-a-seller--tutorials_392).
+Para agregar un _seller_ no identificable (_seller white label_), es necesario tener este modelo previsto en el contrato con VTEX. Una vez acordado un contrato con el representante de ventas de VTEX responsable de tu _marketplace_, envía una solicitud para agregar una cuenta franquicia siguiendo las instrucciones presentes en el siguiente artículo: [Solicitar la creación de una cuenta franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl#solicitar-criacao-de-conta-franquia). Todas las cuentas franquicia se crean como un _seller white label_, y no es posible cambiar el tipo de _seller_ después de su creación. Obtén más información en [Agregar sellers](https://help.vtex.com/es/tutorial/adding-a-seller--tutorials_392).
 
 ### Ubicación
 
diff --git a/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md b/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md
index e6e2af352..3b474b6ed 100644
--- a/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md
+++ b/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md
@@ -25,7 +25,7 @@ Para ello, en el Admin VTEX, accede a **Storefront > Layout > CMS** y hacer clic
 
 El botón se encuentra en la esquina superior derecha, como se muestra en la siguiente imagen.
 
-!![copiar layout](https://images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
+!![copiar layout](//images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
 
 El sistema le preguntará a qué web site desea copiar el layout.
 
diff --git a/docs/tutorials/es/coupons-list-beta.md b/docs/tutorials/es/coupons-list-beta.md
index 01ad690e7..226ba7dd4 100644
--- a/docs/tutorials/es/coupons-list-beta.md
+++ b/docs/tutorials/es/coupons-list-beta.md
@@ -31,7 +31,7 @@ Desde esta página puedes:
 
 Para acceder a la página desde el Admin VTEX, haz clic en **Promociones > Cupones**.
 
-![lista-cupons](https://images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/1526330ae6f09ee70d1250a5c6ac0082/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_13_40_1.png)
+![lista-cupons](//images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/1526330ae6f09ee70d1250a5c6ac0082/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_13_40_1.png)
 
 Luego, verás la descripción de las acciones y los componentes incluidos en la página.
 
@@ -83,7 +83,7 @@ El archivo que se genera contiene la siguiente información:
 
 A continuación, puedes ver un ejemplo del archivo CSV exportado:
 
-![cupons-exportados](https://images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
+![cupons-exportados](//images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
 
 #### Exportar códigos del lote de cupones
 
@@ -100,13 +100,13 @@ Para ver o exportar todos los códigos de un lote de cupones, sigue los pasos a
     * <i class="far fa-clone"></i> **Copiar todos:** permite copiar los códigos generados a su área de transferencia. También puedes copiar cada código haciendo clic sobre él.
     * **Exportar:** permite exportar los códigos generados a un archivo CSV. El archivo exportado tiene una columna con un código por línea.
 
-![exportar-cupones](https://images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/e41e4a9922531597949431314c41ed5d/image_6.png)
+![exportar-cupones](//images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/e41e4a9922531597949431314c41ed5d/image_6.png)
 
 ### Ver uso de cupones
 
 Para ver el total de los cupones activos y el espacio disponible restante para los cupones nuevos, haz clic en <i class="fas fa-chart-line"></i> `Uso de los cupones`.
 
-![uso-de-cupones](https://images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/0ed73731ce39d27daf747bae02757a81/image_9.png)
+![uso-de-cupones](//images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/0ed73731ce39d27daf747bae02757a81/image_9.png)
 
 La cantidad máxima de cupones activos que puedes tener es de 5000. Para liberar espacio, puedes archivar cupones desde la [Lista de cupones](#lista-de-cupones). Si necesitas aumentar el límite de los cupones activos, ponte en contacto con [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
@@ -155,13 +155,13 @@ La ventana **Ver detalles de uso** muestra los datos de uso de cada cupón, que
 
     Esta sección muestra la lista de pedidos en que se usó el cupón y permite buscar por número de pedido. Al hacer clic en el número de un pedido, serás redirigido a la página de detalles del pedido en **Gestión de pedidos**.
 
-![ver-detalles-de-uso](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
+![ver-detalles-de-uso](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
 
 * **Uso general de códigos de cupon** (lotes de cupones): muestra la cantidad total de usos de los códigos de un grupo de cupones y la cantidad de usos restantes, si ha limitado la cantidad de usos.
 
     Esta sección también muestra la lista de códigos en el lote de cupones y le permite buscar un código específico. Al hacer clic en un código, se accede a la lista de pedidos en los que se ha utilizado el código y se puede buscar por un número de pedido. Al hacer clic en un número de pedido, accederá a la página de detalles del pedido en **Gestión de pedidos**.
 
-![selecciona-el-codigo-lotes-cupones](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
+![selecciona-el-codigo-lotes-cupones](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
 
 ## Más información
 
diff --git a/docs/tutorials/es/creating-a-campaign-audience.md b/docs/tutorials/es/creating-a-campaign-audience.md
index 12c181302..e632caa58 100644
--- a/docs/tutorials/es/creating-a-campaign-audience.md
+++ b/docs/tutorials/es/creating-a-campaign-audience.md
@@ -3,8 +3,8 @@ title: 'Crear audiencias de campaña'
 id: 6cnuDZJzIkIeocewAQQK4K
 status: PUBLISHED
 createdAt: 2018-12-02T18:34:21.663Z
-updatedAt: 2023-03-31T13:38:38.613Z
-publishedAt: 2023-03-31T13:38:38.613Z
+updatedAt: 2023-10-31T19:23:55.713Z
+publishedAt: 2023-10-31T19:23:55.713Z
 firstPublishedAt: 2018-12-03T16:51:36.457Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -69,7 +69,7 @@ Luego de hacer clic en `Crear nuevo público-objetivo`, debes seguir las instruc
     * **o:** la audiencia de campaña estará compuesta por clientes que encajen en cualquiera de los públicos-objetivo.
     * **y:** la audiencia de campaña estará compuesta por clientes que encajen en todos los públicos-objetivo y sumen todos sus criterio
 
-![publico-alvo-e-ou-es](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
+![publico-alvo-e-ou-es](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
 
 ### Define a tu público-objetivo
 
@@ -85,13 +85,12 @@ Luego de hacer clic en `Crear nuevo público-objetivo`, debes seguir las instruc
 
 Ejemplo: en la imagen a continuación, los ítems cuya marca es **Nike** forman parte del público-objetivo. La configuración también indica que, al menos, 3 ítems deben cumplir con estos criterios. Por ende, un cliente debe tener en el carrito al menos **3** ítems que cumplan con estos criterios para ser parte del público-objetivo.
 
-![exemplo-marca-publico-alvo-es](https://images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7f6a8b503e122d865d8c0f6ae78a6c4e/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_02_43_1__1_.png)
+![exemplo-marca-publico-alvo-es](//images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7f6a8b503e122d865d8c0f6ae78a6c4e/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_02_43_1__1_.png)
 
 ### Condiciones para que se aplique tu público-objetivo
 
 * **Valor mínimo del pedido:** valor mínimo que debe tener el total de los ítems en el carrito del cliente. Este total incluye la suma de los precios de los productos en el carrito que cumplen con los criterios de la audiencia de campaña.
 * **Valor máximo del pedido:** valor máximo que puede tener el total de los ítems en el carrito del cliente. Este total incluye la suma de los precios de los productos en el carrito que cumplen con los criterios de la audiencia de campaña.
-* **Uso de histórico a la promoción:** permite que se tenga en cuenta el historial de compras del cliente al momento de evaluar si este forma parte del público-objetivo o no. En caso de seleccionar esta opción, deberás elegir el periodo del historial que se considerará. Puedes agregar fechas específicas o contar días a partir de la fecha actual.
 * **Valor del ítem entre __ y __:** precio mínimo y máximo que puede tener cada ítem en el carrito. La audiencia de campaña se activará si el valor del ítem cumple con el intervalo de valores completados.
 * **Restricción de promoción por BIN:** la audiencia de campaña se activará si el _Número de Identificación Bancaria_ (BIN) de la tarjeta de crédito está entre los caracteres rellenados. El BIN corresponde a los 6 u 8 primeros números de una tarjeta y sirve para identificar al banco y al emisor de la tarjeta.
 * **Marketing Tags:** campo usado para restringir la activación de la audiencia de campaña si la compra la realiza el [módulo de Suscripciones de VTEX](https://help.vtex.com/es/tutorial/como-funciona-suscripciones--frequentlyAskedQuestions_4453).
diff --git a/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md b/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
index 608eaff43..d6ea23aec 100644
--- a/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
+++ b/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
@@ -1,17 +1,17 @@
 ---
 title: 'Crear un punto de recogida de contingencia para garantizarlo como opción en el checkout  '
 id: 3mowqWEfjyM2g6WoWgE0Ao
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-04-01T16:02:02.437Z
-updatedAt: 2020-06-20T04:56:48.306Z
-publishedAt: 2020-06-14T22:20:33.622Z
+updatedAt: 2023-08-01T21:35:48.449Z
+publishedAt: 2023-08-01T21:35:48.449Z
 firstPublishedAt: 2019-01-25T17:26:19.150Z
 contentType: tutorial
 productTeam: Shopping
 author: authors_35
-slug: crear-punto-de-recogida-de-contingencia-como-opcion-en-el-checkout  
+slug: crear-punto-de-recogida-de-contingencia-como-opcion-en-el-checkout
 locale: es
-legacySlug: crear-punto-de-recogida-de-contingencia-como-opcion-en-el-checkout  
+legacySlug: crear-punto-de-recogida-de-contingencia-como-opcion-en-el-checkout
 subcategory: 8AGXmtpbTqUE2KQu0Swwk
 ---
 
@@ -21,15 +21,19 @@ Si su cliente final compra un producto en cualquiera de sus canales (en línea o
 
 Sin embargo, usted puede preferir que esa tienda funcione como un punto de recogida __ incluso si no tiene stock__. Para esto, su logística necesita asegurar que el producto llegará a esa tienda desde otro stock, por ejemplo, desde el stock del comercio electrónico. En este caso, necesita tener una política de envío en el comercio electrónico en el que esté configurado el punto de recogida de la tienda física.
 
-![contingency pickup](https://images.ctfassets.net/alneenqid6w5/7sxWH5eDPpCmNlEPfHiZF1/7a10b60e1273d58d9c2ca7610a9ba888/contingency_pickup.png)
+![Crear punto de retiro de contingencia para garantizarlo como opción en checkout](//images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/aebc9c8a6dded36f5b31496626099186/diagrama-como-criar-um-ponto-de_contigencia-es.jpg)
 
 ## Cómo implementar un punto de recogida de contingencia
 
-Siga estos pasos para implementar un stock de contingencia:
-- En el panel administrativo del comercio electrónico o de la tienda que desee utilizar como fallback, es decir, la tienda de cuyo stock saldrán los productos para abastecer el punto de recogida, configure un nuevo punto de recogida con la información de la tienda física deseada.
-- Aún en el comercio electrónico o en la tienda de fallback, cree una nueva política de envío. Esta política de envío debe tener exactamente el __mismo tipo de entrega__ ya configurado en la logística de recogida que se utiliza en la tienda física donde los productos serán retirados.
-- Asocie el nuevo punto de recogida creado con esta política de envío.
+Para implementar un punto de recogida de contingencia, es necesario configurar los siguientes pasos:
 
-<div class="alert alert-info">
-Con esto, tendrá dos rutas logísticas con el mismo punto de recogida: una con el stock local de la tienda física y la otra con el stock de otro canal (comercio electrónico u otra tienda física). Cuando un cliente elige este punto de recogida en el checkout, las dos rutas competirán. Siempre que haya stock local, su SLA será más ventajoso y por lo tanto ganará. Cuando no haya stock local, el pedido caerá en la ruta que usted configuró a partir de este artículo.
-</div>
+1. En el Admin VTEX, [agrega un nuevo](https://help.vtex.com/es/tutorial/cadastro-de-pontos-de-retirada--2R5ClQiwe4KoSQgsuiOw4E) punto de recogida en la tienda, con stock para suministrar los ítems que abastecerán dicho punto de recogida.
+2. [Crea una nueva política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) cuya estrategia de envío coincida con la estrategia de envío previamente configurada en la política que utiliza la tienda física donde se recogerán los productos.
+3. Asocia esta nueva política al punto de recogida recién creado.
+
+De esta forma, tendrás dos rutas logísticas: una que utilizará el stock de la tienda física, y otra logística que utilizará el stock de una tienda diferente.
+
+Cuando el cliente elija este punto de recogida en el checkout, el sistema procederá de la siguiente manera:
+
+- Si hay stock local, el plazo de entrega será más corto. En este caso, se seleccionará el punto de recogida principal.
+- Si no hay stock local, se seleccionará la ruta logística configurada como contingencia.
diff --git a/docs/tutorials/es/creating-a-coupon-beta.md b/docs/tutorials/es/creating-a-coupon-beta.md
index 76e4d11dc..eead12525 100644
--- a/docs/tutorials/es/creating-a-coupon-beta.md
+++ b/docs/tutorials/es/creating-a-coupon-beta.md
@@ -40,7 +40,7 @@ El formulario para crear o editar un cupón consta de las siguientes secciones:
 
 El panel superior del formulario de creación y edición del cupón, ilustrado a continuación, muestra el número de usos del cupón y el número de promociones vinculadas a él.
 
-![crear-cupon-1](https://images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/e17457a01186b62c3b011796d0167c67/crear-cupon-1.png)
+![crear-cupon-1](//images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/e17457a01186b62c3b011796d0167c67/crear-cupon-1.png)
 
 Al hacer clic sobre cualquier información del panel, tendrás acceso a la ventana __Ver detalles de uso__, donde aparecen los datos que se describen a continuación.
 
@@ -52,11 +52,11 @@ Al hacer clic sobre cualquier información del panel, tendrás acceso a la venta
 
     Si el cupón es sencillo, Esta sección muestra la lista de pedidos en que se usó el cupón y permite buscar por número de pedido. Al hacer clic en el número de un pedido, serás redirigido a la página de detalles del pedido en **Gestión de pedidos**.
 
-    ![ver-detalles-de-uso](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
+    ![ver-detalles-de-uso](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
 
     Si se trata de un grupo de cupones, esta sección muestra la lista de códigos del grupo de cupones y permite buscar un código específico. Al hacer clic en un código, se accede a la lista de pedidos en los que se ha utilizado el código y se puede buscar un número de pedido. Al hacer clic en un número de pedido, accederá a la página de detalles del pedido en **Gestión de pedidos**.
 
-![selecciona-el-codigo-lotes-cupones](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
+![selecciona-el-codigo-lotes-cupones](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
 
 ### General
 
@@ -92,7 +92,7 @@ Si creaste un [lote de cupones](https://help.vtex.com/es/tutorial/cupones-beta--
 * <i class="far fa-clone"></i> **Copiar todos:** permite copiar los códigos generados a su área de transferencia. Luego, si lo deseas, puedes pegarlos en un editor de planillas como Excel o Google Sheets. También puedes copiar cada código haciendo clic sobre él.
 * **Exportar:** permite exportar los códigos generados a un archivo CSV. El archivo exportado tiene una columna con un código por línea.
 
-![cupons-gerados-es](https://images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/8e8d4674d5df0558a76a9c3b1bc72af6/cupons-gerados-es.gif)
+![cupons-gerados-es](//images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/8e8d4674d5df0558a76a9c3b1bc72af6/cupons-gerados-es.gif)
 
 ## Asociar el cupón con una promoción
 
diff --git a/docs/tutorials/es/creating-a-more-for-less-promotion.md b/docs/tutorials/es/creating-a-more-for-less-promotion.md
index 239bd6b7c..734fcc06c 100644
--- a/docs/tutorials/es/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/es/creating-a-more-for-less-promotion.md
@@ -3,8 +3,8 @@ title: 'Crear promoción Más por Menos'
 id: tutorials_325
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:17.186Z
-updatedAt: 2023-03-31T19:57:42.646Z
-publishedAt: 2023-03-31T19:57:42.646Z
+updatedAt: 2024-03-28T15:36:24.222Z
+publishedAt: 2024-03-28T15:36:24.222Z
 firstPublishedAt: 2017-04-27T23:03:15.551Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,119 +15,136 @@ legacySlug: mas-por-menos
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-La promoción Más por Menos se utiliza para conceder un descuento cuando el cliente añade varias unidades del mismo producto al carrito. Un ejemplo clásico de este tipo de promoción sería «Lleve 3, pague 2».
+La promoción Más por menos se utiliza para conceder un descuento cuando el cliente añade varias unidades del mismo producto al carrito. Un ejemplo 2. ilustrativo de este tipo de promoción sería “Lleva 3, paga 2”.
 
-En este artículo, detallamos los campos que debe rellenar durante los pasos de configuración de una promoción **Más por Menos**, según se describen a continuación.
+Este artículo describe los pasos necesarios para configurar una promoción Más por menos:
 
-1. [¿Cuáles son los datos generales de la promoción?](#1-cuales-son-los-datos-generales-de-la-promocion)
-    - [Restringir esta promoción a los productos de los sellers](#restringir-esta-promocion-a-los-productos-de-los-sellers)
+1. [Resumen de la promoción]()
+    - [Restringir la promoción a los productos de los sellers](#restringir-esta-promocion-a-los-productos-de-los-sellers)
     - [Política comercial](#politica-comercial)
 2. [Más por menos](#2-mas-por-menos)
-3. [¿Cuáles son las condiciones para que la promoción sea válida?](#3-cuales-son-las-condiciones-para-que-la-promocion-sea-valida)
+3. [Condiciones de la promoción](#condiciones-de-la-promocion)
 4. [Restricciones y limitaciones de uso](#4-restricciones-y-limitaciones-de-uso)
 
-Para entender cómo funciona la implementación de las promociones, lea nuestro artículo [Ejemplos de promociones](https://help.vtex.com/es/tutorial/ejemplos-de-promociones--5A8UTc7knvAscxo7e7rMFD).
+Para entender cómo funciona la implementación de promociones, consulta nuestro artículo [Ejemplos de promociones](https://help.vtex.com/es/tutorial/ejemplos-de-promociones--5A8UTc7knvAscxo7e7rMFD).
 
 ## Crear la promoción
 
-1. En el Admin VTEX, accede a *Promociones > Promociones*, o escribe *Promociones* en la barra de búsqueda en la parte superior de la página.
-2. Haga clic en el botón `Crear promoción`.
-3. Seleccione la opción **Más por Menos**.
-4. Rellene los campos de la promoción.
-5. Haga clic en `Guardar`.
+1. En el Admin VTEX, accede a **Promociones > Promociones** o escribe **Promociones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el botón `Crear promoción`.
+3. Selecciona la opción **Más por menos**.
+4. Rellena los campos de la promoción.
+5. Haz clic en `Guardar`.
 
-## 1. ¿Cuáles son los datos generales de la promoción?
+## 1. Resumen de la promoción
 
-- **Nombre:** es el nombre de la promoción. Campo obligatorio.
-- **Status:** define si la promoción está activa o inactiva. Campo obligatorio.
-- **Descripción:** es la descripción interna de la promoción. Este campo se utiliza para la comunicación interna de su tienda, para que quede claro si la promoción se debe a alguna campaña o liquidación de stock.
-- **Validez:** es la fecha y hora de inicio y fin de la promoción. Se puede utilizar una fecha y hora futuras para que la promoción comience a aplicarse en el sitio web. Si se configura de este modo, la promoción tendrá el status de programada hasta la fecha y hora establecidas. Mientras esté en vigor, la promoción tendrá el status de activa, y al final de la fecha y hora establecidas el status cambiará a inactiva automáticamente. Campo obligatorio.
-- **Utilizar la configuración de recurrencia:** al seleccionar esta casilla, se mostrarán otros campos para configurar los días de la semana y las horas del día en que se aplicará la promoción. Si desea que la promoción se aplique en cualquier día de la semana, no seleccione esta opción.
-- **Destaque en los productos:** inserta una bandera con el nombre de la promoción, utilizada en la vitrina y en la página del producto. Esta bandera solo se insertará si se utiliza el control de visualización de promociones correcto en la plantilla: `<vtex.cmc:discountHightLight/>`. Campo obligatorio.
+En esta sección se proporciona información detallada sobre los datos generales de la promoción.
+
+- **Nombre:** nombre de la promoción. Campo obligatorio.
+- **Status:** activa o desactiva la promoción.
+- **Descripción:** descripción interna de la promoción. Este campo se utiliza para la comunicación interna de tu tienda, para que quede claro si la promoción se debe a alguna campaña o liquidación de stock.
+- **Fecha de vencimiento:** fecha y hora de inicio y fin de la promoción. Se pueden seleccionar una fecha y hora futuras para que la promoción comience a aplicarse en el sitio web. Si se configura de esta forma, el status de la promoción se mostrará de las siguientes maneras:
+    - **Programada:** antes de la fecha y hora de inicio seleccionadas.
+    - **Activa:** durante el periodo previsto para la promoción.
+    - **Inactiva:** después de la fecha y hora de fin seleccionadas.
+- **Utilizar configuración de recurrencia:** seleccionando esta opción, puedes realizar ajustes de recurrencia, por ejemplo, día de la semana y horario.
+- **Información adicional (opcional):** permite incluir en la promoción información adicional compuesta por un nombre y un valor.
+- **Promoción resaltada:** inserta una tag con el nombre de la promoción utilizada en la vitrina y en la página del producto. La tag solo se inserta si se utiliza el control de visualización de promociones correcto en la plantilla: `<vtex.cmc:discountHightLight/>`. Campo obligatorio.
+
+![Dados gerais 1 - ES](//images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/9a0848ea2c4741f7fbba52db0138e7fb/Dados_gerais_1_-_ES.png)
 
 ### Restringir esta promoción a los productos de los sellers
 
-En esta sección puede definir en qué _sellers_ se aplicará la promoción. Puede determinar qué _sellers_ se incluirán o excluirán del descuento. 
+En esta sección se pueden definir los sellers a los que se aplicará la promoción. Es decir, tienes la opción de decidir los sellers que se incluirán o excluirán del descuento.
 
-- **Es igual a:** seleccione los nombres de los _sellers_ deseados para incluirlos.
-- **Diferente de:** seleccione los nombres de los _sellers_ deseados para excluirlos.
+- **Igual a:** selecciona los nombres de los sellers deseados para incluirlos.
+- **Diferentes de:** selecciona los nombres de los sellers deseados para excluirlos.
 
-Para que la promoción sea válida para todos los _sellers_, deje la selección sin marcar.
+Para que la promoción sea válida para todos los sellers, deja la selección sin marcar.
 
 <div class = "alert alert-warning">
-  <p>No es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:</p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.</ol>
+  <p>No es posible seleccionar directamente un <i>seller white label</i>. Hay dos opciones para incluir un <i>seller white label</i> en la promoción: </p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de tu tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir todos los <i>sellers</i>. En este caso, todos los tipos de <i>sellers, white label</i> y otros, se agregan a la promoción.</ol>
 </div>
 
+![Restringir - ES](//images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/709b4d87b04c6bcdb845f948e27f46ed/Restringir_-_ES.png)
+
 ### Política comercial
 
 Esta sección establece las políticas comerciales válidas para la promoción. Puede incluir o excluir las políticas comerciales del descuento.
 
-- **Es igual a:** seleccione las políticas comerciales deseadas para incluirlas.
-- **Diferente de:** seleccione las políticas comerciales deseadas para excluirlas.
-- **Proporcionado por mí (Mi tienda):** selección de las políticas comerciales para productos de su tienda. Puede seleccionar más de una política comercial.
-- **Entregado por mí (Tienda de otros):** selección de las políticas comerciales para sus productos que están en las tiendas de otros. Puede seleccionar más de una política comercial.
+- **Es igual a:** selecciona las políticas comerciales que deseas incluir.
+- **Diferente de:** selecciona las políticas comerciales que deseas excluir.
+- **Proporcionado por mí (Mi tienda):** selección de las políticas comerciales con productos de tu tienda. Puedes seleccionar más de una política comercial.
+- **Entregado por mí (Tienda de otros):** selección de políticas comerciales que rigen la presencia de tus productos en tiendas de terceros. Puedes seleccionar más de una política comercial.
 
-Para que la promoción sea válida para todas las políticas comerciales, deje la selección sin marcar.
+Para que la promoción sea válida en todas las políticas comerciales, deja la selección sin marcar.
+
+![Politica - ES](//images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/df186b6fa5750448e15cf7cae1e5c2bf/Politica_-_ES.png)
 
 ## 2. Más por Menos
 
-En esta sección se definen los productos, la cantidad y el descuento que se verán afectados por la promoción.
+En esta sección se definen los productos, la cantidad y el descuento que serán impactados por la promoción.
 
-- **El cliente compra** `cantidad` **de los siguientes productos:** cantidad de unidades del mismo producto que se deben introducir en el carrito para que se aplique la promoción. Campo obligatorio.
-- - **SKU:** los nombres o ID de los SKU a los que se aplicará el descuento. Puede importar una lista de SKU haciendo clic en el botón `Seleccione un archivo .txt`. El archivo de texto (.txt) debe tener cada ID de SKU en una línea diferente. También puede descargar la lista de SKU añadida al campo haciendo clic en el botón `Descargar lista de SKU`.
-- **Colecciones:** selección de las colecciones que se incluirán en la promoción. La promoción solo se aplicará a los productos que figuren en las colecciones registradas en este campo. Para ello, introduzca el nombre de la colección de productos para la que desea ofrecer este tipo de descuento. Es posible seleccionar más de una colección.
+- **El cliente compra** `número` **de los siguientes productos:** cantidad de unidades del mismo producto que se deben introducir en el carrito para que se aplique la promoción. Campo obligatorio.
+    - **SKUs:** nombres o ID de los SKU a los que se aplicará el descuento. Puedes importar una lista de SKU haciendo clic en el botón `Selecciona un archivo .txt`. El archivo de texto (.txt) debe tener cada ID de SKU en una línea diferente. También puedes descargar la lista de SKU agregada al campo haciendo clic en el botón `Descargar lista de SKU`.
+- **Colecciones:** selección de las colecciones que se incluirán en la promoción. La promoción solo se aplicará a los productos que figuren en las colecciones registradas en este campo. Solo tienes que introducir el nombre de la colección de productos en la que deseas ofrecer este tipo de descuento. Es posible seleccionar más de una colección.
 
 <div class = "alert alert-info">
   <p>Si no se especifican los productos por colección o SKU, la plataforma no permitirá la creación de la promoción.</p>
 </div>
 
-- **Y lleva** `cantidad` **de estos productos:** la cantidad de unidades del producto que recibirá el descuento configurado. Campo obligatorio.
-   - **Con un descuento de:** el cliente se llevará la cantidad seleccionada de productos con un descuento porcentual definido en el campo. 
-   - **Con un precio máximo por ítem de:** el cliente se llevará la cantidad seleccionada de productos con un precio máximo por ítem definido en el campo. 
+- **Y lleva**  `número` **de estos productos:** la cantidad de unidades del producto que recibirá el descuento configurado. Campo obligatorio.
+    - **Con un descuento de:**  el cliente se llevará la cantidad seleccionada de productos con un descuento porcentual definido en el campo.
+    - **Con un precio máximo por ítem de:**  el cliente se llevará la cantidad seleccionada de productos con un precio máximo por ítem definido en el campo.
 
-|![Leve mais por menos 1 - ES](//images.contentful.com/alneenqid6w5/4JHVAhStNu1aNdMqkS2Ca/7c11d9dbf29b90cf4071b8c741f99a1c/image.png)|
-|:--:|
-| _Ejemplo de promoción «Lleve 3, pague 2»_|
+![Leve Mais -ES](//images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/c765ca884eede6552e6f29c55e25aa8c/Leva_Mais_-_ES.png)
 
 ### Configuración avanzada
 En esta sección puede especificar la aplicación del descuento.
-
-#### El descuento debe aplicarse
+Se debe aplicar el descuento:
 
 - **Considerando:** 
-  - **Cualquier producto:** el descuento se aplicará a los productos de la colección o de la lista de SKU, sin que el carrito tenga necesariamente la cantidad previamente registrada. Así, se considera la suma de las unidades de estos productos.
-  - **Solo productos iguales:** el descuento solo se aplicará al SKU. Para que la aplicación sea válida, es necesario tener la cantidad mínima previamente registrada. 
-
-- **A los productos de:**
-  - **Precio más bajo:** el descuento se aplicará a los ítems más baratos de la promoción.
-  - **Precio más alto:** el descuento se aplicará a los ítems más caros de la promoción.
+    - **Cualquier producto:** el descuento se aplicará a diferentes productos en la colección o lista de SKU, incluso si el número de ítems por producto en el carrito es menor que el número definido en la promoción. En este caso, el sistema considera la suma de las unidades de esos productos.
+    - **Solo productos idénticos y variaciones:** el descuento solo se aplicará al SKU. Para que la aplicación sea válida, debes haber agregado al menos el número mínimo de ítems registrado anteriormente.
+    - **A**:
+        - **Los productos más baratos:** el descuento se aplicará a los ítems más baratos de la promoción.
+        - **Los productos más caros:** el descuento se aplicará a los ítems más caros de la promoción.
 
-![Leve mais por menos 2 - ES](//images.contentful.com/alneenqid6w5/71NtRCWE7NxOCxxkUSS1i5/84c1592933571b53f52c84317fa54fa9/image.png)
+![Leve Mais por menos - ES](//images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/676669ab0baa7690e4097ad39325bb66/Leve_Mais_por_menos_-_ES.png)
 
 #### ¿Cómo debe distribuirse el descuento?
 
-- **Solo entre los** `Cantidad`** productos que reciben el descuento:** el descuento se aplicará en su totalidad a la cantidad de productos seleccionada.
-- **Proporcionalmente entre los** `Cantidad` **productos:** el descuento se distribuirá por igual entre la cantidad de productos seleccionada.
+- **Solo entre los `número` productos que reciben el descuento:**  el descuento se aplicará en su totalidad a la cantidad de productos seleccionada.
+- **Proporcionalmente entre los** `número` **productos:**  el descuento se distribuirá por igual entre la cantidad de productos seleccionada.
 
-## 3. ¿Cuáles son las condiciones para que la promoción sea válida?
+## 3. Condiciones de la promoción
+
+En esta sección se proporciona información detallada sobre las condiciones que se deben cumplir para que la promoción sea válida.
 
 - **Valor mínimo y máximo del pedido:** la promoción se aplicará teniendo en cuenta el valor bruto del carrito, sin considerar otras promociones o costos de envío.
-- **Los precios «de» y «por» son iguales o diferentes**: Solo se puede seleccionar una opción. Se refiere a los precios de registro del producto.
-- **Restricción de la promoción por BIN:** el descuento se concederá a los usuarios que paguen con tarjetas cuyo BIN esté entre los números introducidos en este campo.
-- **Clúster de clientes:** el descuento se concederá si el cliente está registrado en el clúster seleccionado. El nombre del clúster debe coincidir exactamente con el registrado en el Master Data. Cualquier error ortográfico impedirá que la configuración funcione correctamente.
-- **Utm_source:** el descuento se concederá si la navegación utiliza un parámetro utm_source correspondiente a cualquiera de los valores registrados. El cliente solo puede introducir un utm_source en el _checkout_.
+- **Precio "de" y "por" son iguales o Precio "de" y "por" son diferentes:** solo se puede seleccionar una de las dos opciones. Se refiere a los precios de registro del producto.
+- **Usar BINs de restricción:** el descuento se concederá a aquellos usuarios que paguen con tarjetas cuyos BIN estén entre los números ingresados en este campo.
+- **Clúster de clientes:** el descuento se concederá si el cliente está registrado en el clúster seleccionado. Es importante resaltar que el nombre del clúster debe coincidir exactamente con el nombre registrado. Cualquier error ortográfico impedirá que la configuración funcione correctamente.
+- **Utm_source:** el descuento se concederá si la navegación utiliza un parámetro utm_source correspondiente a cualquiera de los valores registrados. Es importante resaltar que el cliente solo puede ingresar un utm_source en el checkout.
 - **Utm_campaign:** el descuento se concederá si la navegación utiliza un parámetro utm_campaign con el valor registrado.
-- **Crear cupón a partir de las UTM arriba:** crea un cupón a partir de las UTM registradas para que el cliente tenga acceso a esta promoción solo con el código del cupón.
-- **Medio de pago:** el descuento se concederá si el medio de pago seleccionado por el cliente es el mismo que el registrado en la promoción. Este descuento sólo se aplicará al finalizar la compra, cuando el cliente seleccione el mismo medio de pago que el registrado.
+- **Crear un nuevo cupón con los UTM anteriores:** crea un cupón a partir de los UTM registrados para que el cliente tenga acceso a esta promoción solo con el código del cupón.
+- **Medio de pago:** permite elegir si la promoción se aplicará a uno o varios de los medios de pago seleccionados.
 
-  <div class = "alert alert-info">
-  <p> Por defecto, puede registrar hasta 20 medios de pago por promoción. Además, existe la posibilidad de personalización para incluir hasta 100 medios de pago. Si necesita utilizar más de 20, póngase en contacto con <a href="https://support.vtex.com/hc/es-419/requests">nuestro equipo de soporte</a>.</p>
+ <div class = "alert alert-info">
+  <p> El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con <a href="https://support.vtex.com/hc/es-419/requests">nuestro equipo de soporte</a>.</p>
  </div>
 
-## 4. Restricciones y limitaciones de uso
+ ![Condições de promoção - ES](//images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/13714c02ac6369e9274f4045af6b208b/Condi__es_de_promo__o_-_ES.png)
+
+ ## 4. Restricciones y limitaciones de uso
+
+ En esta sección se proporciona información importante sobre las condiciones y restricciones aplicables a la promoción.
+
+- **Cuántas veces se aplicará esta promoción en tu tienda:** limita la cantidad de veces que se aplicará la promoción. Al deseleccionar la opción ilimitado, se habilita un campo para registrar la cantidad de veces que se puede aplicar la promoción. Si la promoción ya ha sido creada, esta condición solo se aplicará a partir del día en que se configure, sin afectar los pedidos realizados anteriormente.
+- **Cuántas veces por cliente se aplicará esta promoción:** el valor de este campo determina la cantidad máxima de veces que cada cliente puede beneficiarse de la promoción. Por ejemplo, si se establece un límite de tres usos y la promoción se aplica tres veces en un mismo pedido, se considerará como un único uso en relación con el límite total. Esto significa que el cliente aún podrá utilizar la promoción en otros dos pedidos diferentes. Es importante resaltar que este cálculo es independiente de la cantidad de veces que se utilice la promoción en cada pedido individual.
+- **Establecer el número máximo de ítems elegibles para cada carrito:** define la cantidad de ítems del carrito sobre los que la promoción surtirá efecto. Consulta el artículo [Límite de ítems con promoción en el carrito](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para más información.
+- **Aplicar con otras promociones:** permite que se conceda más de una promoción al mismo tiempo sin importar el tipo de descuento. Aprende más sobre cómo [funciona la competencia de promociones](https://help.vtex.com/es/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270#).
+- **Aplicar con precios manuales:** permite aplicar la promoción a productos cuyos precios hayan sido ingresados manualmente por el agente de televentas. Para activar la funcionalidad de precios manuales, utiliza el endpoint [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
+
+![Restrições e limitações - ES](//images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/4c29419ba1d3639afcf175d3639b5ee2/Restri__es_e_limita__es_-_ES.png)
 
-- **Cuántas veces se aplicará esta promoción en su tienda:** limita la cantidad de veces que se aplicará la promoción. Al deseleccionar la opción **ilimitado**, se habilita un campo para registrar la cantidad de veces que se puede aplicar la promoción. Si la promoción ya ha sido creada, esta condición sólo se aplicará a partir del día en que la configure, sin afectar a los pedidos realizados anteriormente.
-- **Cuántas veces por cliente se aplicará esta promoción en su tienda:** determina el número máximo de veces que cada cliente puede utilizar la promoción. Si el campo anterior también está seleccionado, tendrá una prioridad de aplicación mayor que éste.
-- **Definir la cantidad máxima de ítems afectados por carrito**\: define cuántos ítems del carrito serán afectados por la promoción. Lea [este artículo](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-items-con-promocion-en-el-carrito) para saber cómo configurar el campo.
-- **Permitir la acumulación de promociones:** permite que más de una promoción se aplique al mismo tiempo, independientemente del tipo de descuento. Sepa más sobre [cómo compiten las promociones](https://help.vtex.com/es/tutorial/entendiendo-la-competencia-de-las-promociones-2--tutorials_2270).
-- **Permitir acumular con precios manuales:** permite aplicar la promoción a los productos cuyos precios fueron introducidos manualmente por el agente de televentas. Para habilitar la funcionalidad de precios manuales, utilice el endpoint [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration).
diff --git a/docs/tutorials/es/creating-a-product-collection.md b/docs/tutorials/es/creating-a-product-collection.md
index fd21606aa..8c647e907 100644
--- a/docs/tutorials/es/creating-a-product-collection.md
+++ b/docs/tutorials/es/creating-a-product-collection.md
@@ -25,7 +25,7 @@ Para crear una colección, siga las siguientes instrucciones:
 2. Haga clic en **Layout**.
 3. Haga clic en **Product Clusters (Collections)**.
 4. Haga clic en el botón `new collection`, como se muestra a continuación.
-	![Layout 4](https://images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
+	![Layout 4](//images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
 5. Rellene la información requerida:
 	- **Product Cluster Id:** código identificador de la colección. Este campo no debe rellenarse ya que el sistema lo genera automáticamente al guardar.
 	- **Nombre:** nombre de la colección.
@@ -49,17 +49,17 @@ Cada grupo puede ser de uno de los siguientes tipos: __Inclusión__ o __Exclusi
 
 Para crear el Grupo, basta hacer clic en el botón _new group_ como en el ejemplo de la imagen abajo.
 
-![Layout 5](https://images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
+![Layout 5](//images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
 
 Para agregar todos los productos de un determinado Departamento a un grupo, basta con seleccionar el Departamento en cuestión, como indica el ítem 1 de la figura a seguir. Lo mismo se aplica a los productos de una determinada Categoría (ítem 2) o subcategoría (ítem 3).
 
-![Filtro_por_categoria](https://images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
+![Filtro_por_categoria](//images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
 
 ### Crear Grupo por Marca
 
 Para crear un grupo con productos de una o más marcas, basta con seleccionar la marca deseada en la lista correspondiente. Las marcas se encuentran dispuestas en orden alfabética y al hacer clic en la letra correspondiente a la inicial de la marca, la lista se despliega y exhibe las marcas existentes.
 
-![FIltro_por_marca](https://images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
+![FIltro_por_marca](//images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
 
 ### Definir Grupo por productos en preventa o en periodo de lanzamiento
 
@@ -73,7 +73,7 @@ Estas opcciones son un <em>complemento</ em> a la elección de los productos. Es
 
 Al contrario de la versión anterior, en la que la inclusión de productos específicos se hacía a partir del ID del Producto, en el nuevo módulo, las inclusiones manuales se hacen usándose el SKU de un producto. En el campo correspondiente es posible digitar el ID de un SKU o de varios, separando los valores con una coma. Ej: `2000004,2000009,2000005`. Pese a la diferencia en la forma del registro, en la práctica, el efecto será el mismo, ya que al asociar un SKU a un grupo, el producto “padre” de este también será agregado a la colección. En caso que un producto tenga más de un SKU, basta con agregar uno de los SKUs al grupo, que todos los SKUs asociados se incluirán en él. El campo de inclusión de los IDs no permite la digitación de caracteres alfanuméricos, ni la utilización de la combinación de teclas `Control + C` y `Control + V`. Además, cuando el número de SKUs en el listado ultrapase los 10 ítems, un control de paginación se hará disponible. Para excluir un SKU de la lista, basta con hacer clic en el botón rojo al lado del SKU correspondiente.
 
-![Inserir_sku_espec_fico](https://images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
+![Inserir_sku_espec_fico](//images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
 
 ### Importar un listado de SKUS para el grupo
 
@@ -81,7 +81,7 @@ Pese a que los filtros de grupos son muy prácticos para crear agrupamientos de
 
 ![](//images.contentful.com/alneenqid6w5/6t9b1mIYmsSewCEu8yOagi/c0f73dc7b921e0f7cc65cea1ae572b7b/Importar_lista_de_skus.jpg)
 
-Después que el sistema importa la planilla, los SKUs se presentan de la siguiente forma: ![Importar_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
+Después que el sistema importa la planilla, los SKUs se presentan de la siguiente forma: ![Importar_lista_de_skus](//images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
 
 SKUs que estén inactivos no tendrán sus IDs importados, aunque estén incluidos en la planilla.
 
@@ -91,7 +91,7 @@ Recuerde que, cuando se selecciona más de un tipo de grupos, sólo los producto
 
 Para evitar que un administrador tenga que excluir manualmente diversos SKUs, uno por uno, es posible usar también el recurso de importación de SKUs de la misma forma como en el ejemplo arriba. En este caso, después que el archivo se cargue, haga clic en la opción _excluir skus_ (ítem 1 de la imagen).
 
-![Excluir_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
+![Excluir_lista_de_skus](//images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
 
 Obtenga un modelo de archivo para importación tanto para inclusión como para exclusión de ítems en la colección [aquí](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "aquí").
 
@@ -99,4 +99,4 @@ Obtenga un modelo de archivo para importación tanto para inclusión como para e
 
 Cuando la cantidad de colecciones creadas exceda el límite de exhibición, que es veinte ítems, las colecciones podrán ser encontradas a través del campo de búsqueda. La búsqueda debe hacerse con base en el nombre de la colección.
 
-![Pesquisar_cole__o](https://images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
+![Pesquisar_cole__o](//images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
diff --git a/docs/tutorials/es/creating-a-shipping-policy.md b/docs/tutorials/es/creating-a-shipping-policy.md
new file mode 100644
index 000000000..adb99b66b
--- /dev/null
+++ b/docs/tutorials/es/creating-a-shipping-policy.md
@@ -0,0 +1,71 @@
+---
+title: 'Crear una política de envío'
+id: 66rJO4LKBdyMJOH6Z3dsaT
+status: PUBLISHED
+createdAt: 2024-01-30T21:08:12.106Z
+updatedAt: 2024-06-11T19:05:19.723Z
+publishedAt: 2024-06-11T19:05:19.723Z
+firstPublishedAt: 2024-01-31T01:09:33.011Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: crear-una-politica-de-envio
+locale: es
+legacySlug: crear-una-politica-de-envio
+subcategory: 7fTH6bP0C4IaM8qWi0kkQC
+---
+
+La [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) es un conjunto de reglas y ajustes que definen las opciones de envío que se mostrarán a los clientes en el checkout. La relación entre la política de envío, [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) y [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) es lo que conforma la [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) en VTEX.
+
+Este artículo presenta cómo se crea una política de envío a través de VTEX Admin. Si desea gestionar sus políticas, consulte el artículo [Gestionar políticas de envío](https://help.vtex.com/es/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE).
+
+Para crear una nueva política de envío, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Envío > Estrategia de Envío > Políticas de Envío**, o escribe **Estrategia de Envío** en la barra de búsqueda en la parte superior de la página.  
+2. Haga clic en e`Crear Política de Envío`.
+3. Complete los campos que se muestran y, al terminar, haga clic en `Guardar`.
+
+*   **Nombre:** nombre interno de la política de envío.
+*   **ID:** identificador interno y para integradores. Debe rellenarse solo con letras y números, no utiliza espacio. Si no se rellena, se creará un ID automáticamente.
+*   **[Método de envío](https://help.vtex.com/es/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126):** nombre del tipo de entrega. Sirve para separar los diferentes servicios de entrega. Es el nombre que se mostrará al cliente al finalizar la compra. Por ejemplo, expreso vs. regular. 
+*   **Cargar [tarifas de envío](https://help.vtex.com/es/tutorial/como-montar-a-planilha-de-frete--tutorials_127):** tabla con los valores y plazos de envío asumidos por la política de envío.
+*   **[Dimensiones del paquete](https://help.vtex.com/es/tutorial/como-funciona-o-empilhamento--tutorials_124):**
+    *   **Suma de dimensiones:** límites máximos de las aristas del paquete, aceptados. Al llegar a este valor, la entrega se divide en paquetes o no se realiza por esta política de envío. Son datos que se pasan al cerrar el contrato con la política de envío. 
+    *   **Longitud máxima:** máxima medida aceptada. Cuando se alcanza este valor, la entrega se divide en paquetes o no se realiza por esta política de envío. Si un ítem tiene una arista con un tamaño superior a la longitud máxima, nunca se entregará por la política de envío.
+    *   **[Factor de peso volumétrico](https://help.vtex.com/es/tutorial/como-o-peso-cubado-e-calculado--tutorials_128):** factor que se utilizará para calcular el peso volumétrico. Suma de las medidas, dividida por el factor de conversión. 
+    *   **Factor de peso mínimo:** utilice el peso volumétrico solo si supera este valor. Límite de peso donde, a partir de este, se considerará el cálculo del peso volumétrico para el envío.
+    *   **Fines de semana y feriados:** días de la semana para las entregas. Marque los flags para activar la entrega en los siguientes escenarios: `entrega sábados`, `entrega domingos`, `entrega feriados`.
+*   **Fines de semana y feriados:**  para entregas en fines de semana o feriados. Marque los flags para habilitar la entrega en los siguientes escenarios: `entrega sábados`, `entrega domingos`, `entrega feriados`.
+*   **[Modalidades activas](https://help.vtex.com/es/tutorial/como-funciona-o-modal--tutorials_125):** especificaciones de productos que requieren una entrega especial. Estas son las limitaciones de envío del producto que permite la política de envío. Entender más sobre las modalidades. Marque los flags para habilitar la entrega en los siguientes escenarios: `productos químicos`, `electrónicos`, `muebles`, `vidrio`, `líquidos`, `colchones`, `productos refrigerados`, `llantas`, `electrodomésticos` y `armas de fuego`.
+*   **Ítems del paquete: **cantidad mínima de ítems aceptados por envío, de acuerdo con la política de envío.
+    *   **Valor mínimo:** valor mínimo aceptado por la política de envío para realizar el servicio.
+    *   **Mínimo de ítems:** múltiplo mínimo de la cantidad de ítems aceptados por la transportadora. Por ejemplo, si se rellena con el valor **3**, significa que la transportadora solo hace entregas con cantidades de ítems múltiplos de tres (3, 6, 9, 21...).
+    *   **Valor máximo:** valor máximo aceptado por la política de envío para realizar el servicio.
+*   **Relacionar puntos de recogida:** marque este flag, para abrir la opción de Puntos de Recogida. Haga clic en el menú desplegable y seleccione entre `Tags de los puntos de recogida`, `Nombres de los puntos de recogida` y `Importar puntos de recogida de los sellers` previamente registrados.
+*   **Configuración de tiempo:** seleccione el día y la hora de apertura y cierre en los siguientes escenarios. Puede añadir más de un plazo por escenario.
+*   **[Horario laboral:](https://help.vtex.com/es/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS)** horarios en los que la política de envío hace recolecciones o los ventanas de envío en los que envía los ítems a los clientes. Estos ajustes influyen en el cálculo del plazo de entrega:
+    *   **Ventana de envío:** es donde se registran los periodos laboral de la política de envío, es decir, los horarios en los es posible recibir pedidos. Para configurar, seleccione la opción `Ventana de envío`:
+        *   Habilite `Aceptar compras fuera del horario laboral` si la política de envío acepta compras fuera del horario laboral. Ahora bien, aunque la política de envío acepte pedidos fuera del horario laboral, el tiempo hasta el próximo periodo disponible se añadirá al SLA final.
+        *   Seleccione `Día de la semana`, y rellene la hora de `Hora de inicio` y `Hora de fin`.
+        *   Para añadir más días de la semana, haga clic en `Agregar ventana deb envío`.
+    *   **Hora de recogida:** es donde se registran los horarios en que la política de envío recolecta los paquetes en su almacén o centro de distribución, para luego enviarlos a los clientes finales. Es importante destacar que si el pedido se realiza antes de la hora de recolección del mismo día, no se agregará tiempo adicional al SLA final, si se realiza después de la hora de recolección, el tiempo hasta el próximo horario de recolección se agregará al SLA.  
+        *   Seleccione `Día de la semana` y rellene el `Hora de recogida`. 
+        *   Para añadir más días de la semana, haga clic en `Agregar hora de recogida`.
+
+<div class="alert alert-warning">
+La <b>Ventana de envío</b> y la <b>Hora de recogida</b> son opciones que se excluyen entre sí, ya que no se puede asignar el mismo período simultáneamente a acciones distintas.
+</div> 
+
+*   **[Entrega programada](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)**: esta funcionalidad puede habilitarse si la política de envío ofrece un servicio de entrega programada. Aquí es donde debe añadir las ventanas de entrega que estarán disponibles para el cliente al final de la compra. Para utilizarla, habilite `entrega programada` y rellene:
+    *   **Tiempo máximo de entrega:** define el tiempo máximo de entrega, debe ser completado con el tiempo en días.
+    *   **Periodo de entrega:** define las ventanas de entrega de la política de entrega. Debe añadir los días de la semana, las horas de `inicio` y `fin` de la ventana de entrega y el valor adicional. Haga clic en `Nuevo periodo de entrega` para añadir más ventanas de entrega. 
+    *   **Capacidad de entrega:** le permite limitar el número de ítems/pedidos que pueden entregarse para cada ventana de entrega. Esta funcionalidad puede habilitarse o no. El uso o no de esta funcionalidad no interfiere con el funcionamiento de la plataforma. Para saber más sobre estos recursos, consulte [Entrega programada](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) y [Gestionar capacidad de entrega](https://help.vtex.com/es/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz). Si está habilitada debe: 
+        *   Elija la unidad de la capacidad de entrega entre `ítems` y `pedidos`.
+        *   Verifique las ventanas de entrega.
+        *   Definir el número de la `capacidad de entrega`. Recomendamos tener especial cuidado a la hora de elegir la unidad de capacidad de entrega porque el sistema no calcula la disponibilidad de la capacidad de entrega teniendo en cuenta la cantidad de ítems que se compran. Así, si la ventana de entrega todavía tiene capacidad para 2 ítems y su cliente está comprando 4 ítems, aún tendrá la opción de seleccionar la ventana de entrega disponible.
+
+### Sepa más
+
+* [Política de envío](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+* [Gestionar políticas de envío](https://help.vtex.com/es/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE)
+* [Estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
diff --git a/docs/tutorials/es/creating-a-subscription-plan.md b/docs/tutorials/es/creating-a-subscription-plan.md
index 2742bb126..4addb36c6 100644
--- a/docs/tutorials/es/creating-a-subscription-plan.md
+++ b/docs/tutorials/es/creating-a-subscription-plan.md
@@ -92,7 +92,7 @@ En esta pantalla, puede realizar las siguientes acciones:
 
 * **Seleccionar:** al hacer clic en la casilla (<i class="far fa-square"></i>) en la fila de cada producto, puede seleccionar productos o SKU individualmente. Otra opción es hacer clic en la primera casilla (<i class="far fa-square"></i>) y seleccionar todos los productos y SKU que aparecen en la página para añadirlos al plan, según se ilustra en la siguiente imagen.
 
-![selecionarskus ES](https://images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/9786f043859be876f63855568e6d00d3/selecionarskus_ES.gif)
+![selecionarskus ES](//images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/9786f043859be876f63855568e6d00d3/selecionarskus_ES.gif)
 
 * __Botón de flecha__ (<i class="fas fa-chevron-down"></i>): muestra los SKU, es decir, las variaciones del producto.
 * **Añadir:** al hacer clic en este botón, se añaden los productos o SKU al plan de suscripción.
diff --git a/docs/tutorials/es/creating-a-subscription-promotion.md b/docs/tutorials/es/creating-a-subscription-promotion.md
index 4bd2d8973..e4c4824a5 100644
--- a/docs/tutorials/es/creating-a-subscription-promotion.md
+++ b/docs/tutorials/es/creating-a-subscription-promotion.md
@@ -23,7 +23,7 @@ En este artículo, encontrará el paso a paso para crear promociones por suscrip
 4. Seleccione `Promoción Regular`.
 5. En la sección **¿Cuáles son las condiciones para que la promoción sea válida?**, seleccione la casilla **Es un pedido de suscripción**.  Así, la promoción se aplicará a los pedidos por suscripción. Sólo los productos con una suscripción en la cesta recibirán el descuento. Para entender las posibilidades de configuración, vea las siguientes condiciones:
 
-![frequencia1](https://images.ctfassets.net/alneenqid6w5/3Tg0ujk38ip94YogUGdD9M/ca5cd9a587aaff53b054efb27bf04008/image__3_.png)
+![frequencia1](//images.ctfassets.net/alneenqid6w5/3Tg0ujk38ip94YogUGdD9M/ca5cd9a587aaff53b054efb27bf04008/image__3_.png)
 
 - **Pedido original**: pedidos que generan las suscripciones, pero que aún no forman parte de los ciclos de suscripción.
 - **Pedidos recurrentes**: pedidos que forman parte de los ciclos de suscripción.
diff --git a/docs/tutorials/es/creating-a-trade-policy.md b/docs/tutorials/es/creating-a-trade-policy.md
index 5e5031a32..d55514a9d 100644
--- a/docs/tutorials/es/creating-a-trade-policy.md
+++ b/docs/tutorials/es/creating-a-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Crear una política comercial'
 id: 563tbcL0TYKEKeOY4IAgAE
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:49.369Z
-updatedAt: 2022-12-08T14:40:14.268Z
-publishedAt: 2022-12-08T14:40:14.268Z
+updatedAt: 2024-04-15T21:21:00.376Z
+publishedAt: 2024-04-15T21:21:00.376Z
 firstPublishedAt: 2019-01-24T22:14:00.848Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,39 +17,30 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 En VTEX las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) se utilizan para agrupar configuraciones de catálogo, precios, promociones, inventario, logística de envío y pagos para distintos canales de venta. Los canales de venta pueden incluir, por ejemplo, marketplaces, ecommerces, tiendas físicas o tiendas B2B.
 
+<div class="alert alert-danger">
+Por defecto, las nuevas políticas comerciales se aplican a todos los vendedores activos. Si desea aplicarlas solo a un grupo específico de vendedores, por favor, indíquelo en el ticket.
+</div>
+
+## Manejar políticas comerciales
+
 La sección Políticas Comerciales de su Admin presenta una tabla con todas las políticas comerciales ya registradas. También es posible filtrar los resultados, hacer una búsqueda por palabra clave y ordenar en la tabla las políticas comerciales que se registraron. El ID de la política comercial es determinado automáticamente por el sistema con base en el orden cronológico de creación de las nuevas políticas.
 
-Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)* seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`.
+Para definir la configuración logística aplicada a una política comercial, hay que [crear o editar un muelle](https://help.vtex.com/es/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW) relacionado con las transportadoras deseadas: es necesario introducir el ID de la política comercial en la página para crear/editar muelles.
 
-La contratación de políticas comerciales adicionales para integración con un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), un [conector certificado (partner)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX está exenta de la cuota mensual.
+Para utilizar el mismo catálogo en más de una política comercial, acceda a la documentación [Associate Product with Trade Policy](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/salespolicy/-tradepolicyId-).
 
-1. En la sección *Configuración de la Tienda*, haga clic en __Políticas comerciales__.  
-2. Haga clic en __Nueva Política Comercial__.  
-3. Rellene los campos.  
-4. Haga clic en __Guardar__.   
+## Contratar una política comercial
+
+Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)* seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`. Al solicitar la creación de una política comercial a través de un ticket, tenga en cuenta un tiempo de respuesta de hasta tres días hábiles.
 
 <div class="alert alert-info">
-Para definir la configuración logística aplicada a una política comercial, hay que <a href="https://help.vtex.com/es/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW">crear o editar un muelle</a> relacionado con las transportadoras deseadas: es necesario introducir el ID de la política comercial en la página para crear/editar muelles.
+Para que el uso de política comercial adicional para integrarse con <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex"conector nativo</a>, un <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conector certificado (partner)</a> u otras tiendas VTEX esté exento de tarifas, los pedidos deben estar asociados a la misma.
 </div>
 
-## Campos a rellenar
-
-- __Nombre__: nombre que identifica su política comercial en otros módulos del Admin de VTEX.  
-- __Colección__: colección de productos que se registró en el catálogo válida para la política comercial.  
-- __Sellers__: casilla de verificación que asocia a los vendedores con las reglas de la política comercial.  
-- __Código de moneda__: moneda que se aplicará al canal de venta que utiliza la política comercial.  
-- __Símbolo de moneda__: símbolo de la moneda elegida. Aparecerá en los precios de los productos en el canal de venta que utiliza la política comercial. Este campo es opcional; si se deja en blanco, asumirá el símbolo predeterminado de la moneda elegida.  
-- __Decimales de moneda:__ cantidad de decimales que los precios de los productos pueden tener. Este campo es opcional; si se deja en blanco, asumirá el valor por defecto de la moneda elegida.  
-- __Código de país:__ código del país donde se encuentra el canal de ventas.  
-- Información cultural: idioma elegido para la política comercial entre las opciones disponibles para el país seleccionado.  
-- __Zona horaria__: zona horaria aplicada a la política comercial según el estándar de tiempo UTC (Tiempo Universal Coordinado).  
-- __Activo__: casilla de verificación para activar o desactivar la política comercial en su entorno VTEX.  
-- __Regla condicional__: campo personalizable a través del cual es posible definir un criterio adicional para la política comercial. Un ejemplo de regla condicional es limitar el acceso a la tienda a través de un [clúster de clientes](https://help.vtex.com/es/tutorial/como-criar-um-cluster-de-clientes).  
-- __Heredar catálogo de una política comercial:__ indica si la política comercial que se está registrando heredará el catálogo de una política comercial ya existente. Si las políticas comparten el mismo catálogo y solo difieren en otros campos, marque este campo siempre que sea posible para optimizar el rendimiento del sistema.     
-
 ## Más información
 
 - [Como funciona una política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)  
 - [Política comercial para marketplace](https://help.vtex.com/es/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)  
+- [Contratación de políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X)
 - [Crear un muelle](https://help.vtex.com/es/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW)  
 
diff --git a/docs/tutorials/es/creating-a-type-of-list.md b/docs/tutorials/es/creating-a-type-of-list.md
index e4f07245f..1f2c9a081 100644
--- a/docs/tutorials/es/creating-a-type-of-list.md
+++ b/docs/tutorials/es/creating-a-type-of-list.md
@@ -61,7 +61,7 @@ El dueño de la tienda decide si la lista tendrá o no evento. Una vez grabado e
 
 Al seleccionar **Posee evento**, el formulario hace disponibles otras opciones de configuración para el evento, donde será posible configurar todas las fechas límites para la creación de ese tipo de lista, conforme a la imagen abajo.
 
-![eventos.es](https://images.ctfassets.net/alneenqid6w5/Q48lA7Ybjz6mQ8wH27hms/85a9a1f23758f6e1fdc3a016dadeb68b/eventos.es.png)
+![eventos.es](//images.ctfassets.net/alneenqid6w5/Q48lA7Ybjz6mQ8wH27hms/85a9a1f23758f6e1fdc3a016dadeb68b/eventos.es.png)
 
 El área de evento es responsable de definir si la lista creada tiene o no un período preestablecido para la fecha del evento. Listas de desejo o listas de compras no necesitan un período determinado para ocurrencia del evento. En cambio, listas de casamento o de chá de bebe, deben tener en cuenta la fecha del evento, para que así, todos los productos comprados se entreguen al dueño en período hábil según la fecha del evento.
 
@@ -77,7 +77,7 @@ El área de evento es responsable de definir si la lista creada tiene o no un pe
 
 Después de crear el tipo de lista, usted será dirigido a la pantalla donde aparecen los tipos de listas ya registrados en la tienda. Esa pantalla ofrece las siguientes informaciones y funciones:
 
-![listagem.es](https://images.ctfassets.net/alneenqid6w5/3BTiBXCbQovhe3duPewHZx/410066a38327a8a69a3ffc1ed7bd2029/listagem.es.png)
+![listagem.es](//images.ctfassets.net/alneenqid6w5/3BTiBXCbQovhe3duPewHZx/410066a38327a8a69a3ffc1ed7bd2029/listagem.es.png)
 
 - **Exportar a Excel**: Permite exportar los datos de tipos de listas para Excel.
 - **Versión**:Identificación de listas creadas en la versión antigua de la funcionalidad, con limitaciones. La versión más actual es la “v2”.
diff --git a/docs/tutorials/es/creating-an-application-in-master-data.md b/docs/tutorials/es/creating-an-application-in-master-data.md
index c601de24e..d967a5785 100644
--- a/docs/tutorials/es/creating-an-application-in-master-data.md
+++ b/docs/tutorials/es/creating-an-application-in-master-data.md
@@ -3,8 +3,8 @@ title: 'Crear una aplicación en Master Data'
 id: tutorials_1115
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:27.067Z
-updatedAt: 2023-03-28T23:26:06.249Z
-publishedAt: 2023-03-28T23:26:06.249Z
+updatedAt: 2024-06-25T20:45:29.002Z
+publishedAt: 2024-06-25T20:45:29.002Z
 firstPublishedAt: 2017-04-27T23:03:43.159Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,32 +15,33 @@ legacySlug: creando-una-aplicacion-en-el-vtex-master-data
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-Aplicación es un agrupador de forms. Tiene la función de organizar, dividir y establecer accesos restritos por área, o sea, facilita la organización de los datos de acuerdo a la necesidad. Ejemplo: Aplicación de Atención al Cliente tiene forms de Cliente y Ticket.
+Una aplicación es un agrupador de formularios que organiza, divide y establece acceso refinado por temas en Master Data. Al crear una aplicación, puedes incluir varios formularios en la misma para facilitar la organización de los datos según sea necesario. Por ejemplo, en la aplicación Soporte, podrías tener los formularios Cliente y Ticket.
 
-## Como crear la aplicación
+## Crear aplicaciones
 
-1. Accesar el módulo **Master Data**;
-2. Haz click en la pestaña **Aplicações**;
-3. Haz click en el botón **Criar Aplicação**;
-4. Llenar el nombre de la **Aplicación**;
-5. Llenar el campo **Criar Cópia De** en caso de que quiera hacer una copia de los forms de una otra aplicación;
-6. Haz click en el botón **Salvar(Guardar)**;
-7. Al cargar la página de aplicaciones, haz click en el botón **Recarregar Aplicações**.
+Sigue las instrucciones a continuación para crear una nueva aplicación:
 
-<video class="wp-video-shortcode" id="video-1115-2" width="840" height="411" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4?_=2" />[//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4](//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4 "//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4")</video>
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. Haz clic en el botón `Crear aplicaciones`.
+4. Rellena el **Nombre** de la aplicación.
+5. Selecciona una opción en el campo **Crear copia de** si deseas copiar los formularios de otra aplicación.
+6. Haz clic en el botón `Guardar`.
 
-## Como editar la aplicación
+## Editar aplicaciones
 
-1. Accesar el módulo **Master Data**;
-2. Haz click en la pestaña **Aplicações**;
-3. En la aplicación deseada, haz click en el ícono del engranaje;
-4. Editar la aplicación;
-5. Haz click en **Salvar(Guardar)**.
+Sigue las instrucciones a continuación para editar una aplicación:
 
-## Como borrar la aplicación
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+3. En la aplicación deseada, haz clic en el ícono de engranaje <i class="fas fa-cog"></i>.
+4. Edita la aplicación.
+5. Haz clic en `Guardar`.
 
-1. Accesar el módulo **Master Data**;
-2. Haz click en la pestaña **Aplicações**;
-3. En la aplicación deseada, haz click en el ícono del engranaje;
-4. Haz click en la opción **Aplicações**;
-5. En la aplicación deseada, haz click en el botón **Excluir**, el de color rojo.
+## Eliminar aplicaciones
+
+Sigue las instrucciones a continuación para eliminar una aplicación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En la aplicación deseada, haz clic en el ícono de engranaje <i class="fas fa-cog"></i>.
+4. Haz clic en **Aplicaciones**.
+5. En la fila de la aplicación deseada, haz clic en el botón de eliminar ⛔.
+6. Haz clic en `OK`.
diff --git a/docs/tutorials/es/creating-an-oauth2-authentication.md b/docs/tutorials/es/creating-an-oauth2-authentication.md
index ab982c90b..51bde355a 100644
--- a/docs/tutorials/es/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/es/creating-an-oauth2-authentication.md
@@ -38,7 +38,7 @@ Puede consultar la guía oficial del protocolo OAuth2 en esta dirección: https:
 ### Flujo de integración de OAuth2 con VTEX ID
 
 Con base en la documentación oficial, vea a continuación una ilustración que explica la integración de OAuth2 con VTEX ID:
-![oauth2](https://images.ctfassets.net/alneenqid6w5/ZIsxie9YMmuWgWcgkeUis/313ac04141d8975528a273f1d2d47023/Fluxo_OAuth2_VTEX_ID__ES_.png)
+![oauth2](//images.ctfassets.net/alneenqid6w5/ZIsxie9YMmuWgWcgkeUis/313ac04141d8975528a273f1d2d47023/Fluxo_OAuth2_VTEX_ID__ES_.png)
 
 A partir de esta ilustración, vamos a detallar los pasos a seguir.  
 
diff --git a/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
index dc341b1b1..7ad341cdd 100644
--- a/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -23,7 +23,7 @@ Para aplicar un precio diferenciado a los productos por XML, es necesario asocia
   2. Busque el archivo XML que se modificará y haga clic en `Editar`. Si quiere crear uno nuevo, lea nuestro artículo [Configurar XML](https://help.vtex.com/es/tutorial/como-configurar-xml--tutorials_242).
   3. Aquí debe verificar si los campos relacionados con el precio del SKU (menor precio del producto, mayor precio del producto, precio original del SKU, precio actual del SKU y precio actual del SKU + tasas) se rellenaron. Al menos uno de los campos debe contener información para que la operación funcione correctamente.
   4. Rellene el campo __Tablas de precios__ con el nombre de la tabla de precios deseada. A continuación, haga clic en la casilla correspondiente al tag en la columna __Exhibe contenido__. La tabla de precios seleccionada debe tener registrados los precios fijos. De lo contrario, la configuración no se realizará.
-![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
+![PT-tabela de precos](//images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
 <div class="alert alert-warning">
   <p>Cuando se incluya la tabla de precios en el XML, se sobrescribirán todos los campos de precios.</p>
 </div>
@@ -37,5 +37,5 @@ Luego de terminar el registro del XML y guardar los cambios, puede verificar la
 
 Ejemplo de XML actualizado:
 
-![XML-exemplo](https://images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/febf8db73d3de4579799de5a70e93de3/XML-exemplo.png)
+![XML-exemplo](//images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/febf8db73d3de4579799de5a70e93de3/XML-exemplo.png)
 
diff --git a/docs/tutorials/es/creating-collections-beta.md b/docs/tutorials/es/creating-collections-beta.md
index d3e75e011..4419de250 100644
--- a/docs/tutorials/es/creating-collections-beta.md
+++ b/docs/tutorials/es/creating-collections-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Registar Colecciones (Beta)'
 id: yJBHqNMViOAnnnq4fyOye
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-08-17T20:29:25.500Z
-updatedAt: 2023-03-29T14:50:46.438Z
-publishedAt: 2023-03-29T14:50:46.438Z
+updatedAt: 2024-03-04T20:48:30.215Z
+publishedAt: 2024-02-22T12:15:26.041Z
 firstPublishedAt: 2020-08-27T15:16:59.673Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -88,39 +88,40 @@ La selección de productos vía Admin VTEX se puede realizar a través de la lis
 
 Hay una variedad de filtros que se pueden seleccionar para reducir la cantidad de productos que se muestran en la lista. 
 
-![Colecciones - ES](https://images.ctfassets.net/alneenqid6w5/3FPMxYUHhfXCFgdJ1YaWBA/01b312b5cec4047135e06017b227eec3/Colecciones_-_ES.PNG)
+![Colecciones - ES](//images.ctfassets.net/alneenqid6w5/3FPMxYUHhfXCFgdJ1YaWBA/01b312b5cec4047135e06017b227eec3/Colecciones_-_ES.PNG)
 
 Usted puede crear nuevos filtros a partir de otros criterios que no se incluyen en los filtros predeterminados. Las siguientes imágenes muestran algunas opciones:
 
-![Novo filtro - ES](https://images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/fd2f6536dba1a15e56d64a94df9f66f8/Novo_filtro_-_ES.PNG)
+![Novo filtro - ES](//images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/fd2f6536dba1a15e56d64a94df9f66f8/Novo_filtro_-_ES.PNG)
 
-![Filtro Colecao detalhes - ES](https://images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/5426ac9eab57f5e5b9241ec8525140e8/Filtro_Colecao_detalhes_-_ES.PNG)
+![Filtro Colecao detalhes - ES](//images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/5426ac9eab57f5e5b9241ec8525140e8/Filtro_Colecao_detalhes_-_ES.PNG)
 
 Para agregar un producto a la colección, solo haga clic en el ícono <i class="fas fa-plus-circle" title = "símbolo de agregar en círculo"></i> del producto. De esa forma, se guardará en la colección automáticamente.  
 
 Si desea más información sobre el ítem, haga clic en el ícono <i class="fas fa-external-link-alt" title = "enlace externo"></i> para abrir la página del producto, o haga clic en la imagen para verla de forma ampliada. 
 
-![ES-colecao-adicionar](https://images.ctfassets.net/alneenqid6w5/301ci58WsAbhxqAjczEVwj/1683d83db5dfa0526adef94f3c2bc7b0/ES-colecao-adicionar.gif)
+![ES-colecao-adicionar](//images.ctfassets.net/alneenqid6w5/301ci58WsAbhxqAjczEVwj/1683d83db5dfa0526adef94f3c2bc7b0/ES-colecao-adicionar.gif)
 
 Si desea incluir productos de forma masiva, aplique uno de los filtros y haga clic en el botón `Agregar Todo`. Es importante destacar que el producto debe tener al menos un SKU registrado para ser incluido en una colección.
 
-![ES-colecao-adicionar-todos](https://images.ctfassets.net/alneenqid6w5/1Qtj7Lq2xPebiPh4SrSV4R/6e66d5f68b4ffe07f6d1dd86bf16726c/ES-colecao-adicionar-todos.png)
+![ES-colecao-adicionar-todos](//images.ctfassets.net/alneenqid6w5/1Qtj7Lq2xPebiPh4SrSV4R/6e66d5f68b4ffe07f6d1dd86bf16726c/ES-colecao-adicionar-todos.png)
 
 <div class = "alert alert-danger">
 <p>No agregue de forma masiva una cantidad superior a 150 mil productos. Eso puede comprometer la indexación del catálogo y el funcionamiento de la tienda.</p>
 </div>
 
 #### Por plantilla
-
 Usted también puede agregar ítems a una colección mediante una plantilla. 
 
+<div class = "alert alert-info">El límite máximo para la importación e exportación es de 10,000 SKUs por operación.</div>
+
 Para eso, realice los siguientes pasos: 
 
   1. En el panel de su colección, haga clic en el botón `Importar`.
   2. Haga clic en la opción **Incluir productos a la colección**, y luego en el botón `Importar`.
   3. Haga clic en `Descargar la plantilla` para obtener la plantilla correcta como se muestra aquí:
 
-![colecao-planilha -ES](https://images.ctfassets.net/alneenqid6w5/4Mqxv9SSr8WynEiEah45ix/fa56634539212f663c2a3f36782b5f66/colecao-planilha_-ES.png)
+![colecao-planilha -ES](//images.ctfassets.net/alneenqid6w5/4Mqxv9SSr8WynEiEah45ix/fa56634539212f663c2a3f36782b5f66/colecao-planilha_-ES.png)
 
   4. Complete la plantilla con los IDs o los RefIDs de los productos o de los SKUs. Solo agregue un ID en cada fila. Independientemente del ID que ingrese, todos los SKUs del producto seleccionado se añadirán a la colección después de la importación.
   5. Después de completar la plantilla, guarde las modificaciones e importe el documento en el Admin. Usted puede arrastrar y soltar el archivo en el área indicada o hacer clic en **Selecciona un archivo**. Se aceptan archivos en formato CSV o XML. En caso de que utilice un arquivo CSV, use , para delimitar los campos.
@@ -138,11 +139,11 @@ Los productos se pueden eliminar mediante la selección de los ítems en la list
 
 Para eliminar un ítem de la colección, solo debe hacer clic en el ícono <i class="fas fa-check-circle" title = "check en círculo"></i> del producto. 
 
-![ES-colecao-remover](https://images.ctfassets.net/alneenqid6w5/4FcChdnT9NIYu69aS13TgM/f0b6c63d35ec92f9eb18f005b49d8d8a/ES-colecao-remover.gif)
+![ES-colecao-remover](//images.ctfassets.net/alneenqid6w5/4FcChdnT9NIYu69aS13TgM/f0b6c63d35ec92f9eb18f005b49d8d8a/ES-colecao-remover.gif)
 
 Si desea eliminar productos de forma masiva, aplique uno de los filtros y haga clic en el botón `Eliminar Todo`.
 
-![ES-colecao-remover-todos](https://images.ctfassets.net/alneenqid6w5/7s9ZJCnRkWSeY8xMJ5DelL/a2ca949f1e3d59fe49a2428b27c0d86e/ES-colecao-remover-todos.png)
+![ES-colecao-remover-todos](//images.ctfassets.net/alneenqid6w5/7s9ZJCnRkWSeY8xMJ5DelL/a2ca949f1e3d59fe49a2428b27c0d86e/ES-colecao-remover-todos.png)
 
 También puede hacer clic en el botón <i class="far fa-check-circle" title = "produtos nesta coleção"></i> (Productos nen esta colección) en la barra superior y después seleccionar `Eliminar Todo`. 
 
@@ -175,7 +176,7 @@ Para alterar el orden de su colección, siga estos pasos:
 
   b. Seleccione la caja de los productos que desea alterar y haga clic en `Mover a la posición`. Indique el número de la nueva posición y, para finalizar, haga clic en `Mover`. De esta manera, puede ordenar todos los ítems de la lista de forma masiva. 
 
-![mover-colecao-ES](https://images.ctfassets.net/alneenqid6w5/2fhHZIuCwN7aysjh78tOae/20aa235a1c6afa1a6c3504b0110a2b9d/mover-colecao-ES.png)
+![mover-colecao-ES](//images.ctfassets.net/alneenqid6w5/2fhHZIuCwN7aysjh78tOae/20aa235a1c6afa1a6c3504b0110a2b9d/mover-colecao-ES.png)
 
 ### Exportar la plantilla de la colección
 
diff --git a/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md b/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md
new file mode 100644
index 000000000..e99608de1
--- /dev/null
+++ b/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md
@@ -0,0 +1,62 @@
+---
+title: 'Crear consulta personalizada en Master Data v1'
+id: tutorials_799
+status: PUBLISHED
+createdAt: 2017-04-27T21:57:44.496Z
+updatedAt: 2024-07-17T13:34:47.245Z
+publishedAt: 2024-07-17T13:34:47.245Z
+firstPublishedAt: 2017-04-27T23:03:43.119Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: crear-consulta-personalizada-en-master-data-v1
+locale: es
+legacySlug: creando-una-cconsulta-customizada-en-el-vtex-master-data
+subcategory: 2AThnkEZAYbk4G4EIs53rL
+---
+
+Una consulta personalizada en Master Data es un filtro o combinación de filtros que se pueden guardar y utilizar directamente desde la lista de registros en un formulario. 
+
+## Prerrequisitos
+
+Antes de crear una consulta es necesario seguir los pasos descritos en [Filtrar datos en Master Data](https://help.vtex.com/es/tutorial/filtrando-dados-no-master-data--tutorials_778) para configurar un filtro tanto en la entidad de datos como en el formulario.
+
+## Guardar una consulta
+
+Sigue los pasos a continuación para filtrar los registros de un formulario y guardar una consulta personalizada.
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. Comprueba que estás en la pestaña **Aplicaciones**.
+3. En la aplicación deseada, identifica el formulario que deseas ver y haz clic en el ícono de lista <i class="fas fa-bars"></i>.
+
+    Serás redirigido a la lista de registros del formulario. En el lado izquierdo verás los filtros configurados. 
+
+4. Para filtrar, selecciona el nombre del filtro y su valor, y haz clic en `Filtrar`.
+
+    Puedes filtrar por varios campos a la vez y por varios valores en el mismo campo. Para eliminar un filtro, basta con hacer clic en la `X` situada junto al valor.
+
+5. Haz clic en el botón `Guardar consulta`.
+6. Asigna un nombre a la consulta personalizada.
+7. Haz clic en `OK`.
+8. Haz clic en `OK` nuevamente.
+9. Haz clic en la pestaña **Aplicaciones**.
+10. Haz clic en el botón `Volver a cargar aplicaciones`.
+
+Tras seguir las instrucciones anteriores, la consulta aparecerá como una opción de vista en la lista del formulario.
+
+![consultas-2-es](//images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/5e6ce3c1f84ca1d99e8c2761a66c6954/consultas-2-es.png)
+
+También puedes acceder a las consultas guardadas haciendo clic en el botón **Consultas**, en la lista del formulario:
+
+![consultas-es](//images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/22fd8166b6442947fd09734856ac675a/consultas-es__1_.png)
+
+## Configuración de consulta predeterminada
+
+Para garantizar que un formulario siempre abra la lista utilizando una consulta personalizada en lugar de mostrar todos los registros, puedes configurar una consulta predeterminada. Para hacerlo, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. Comprueba que estás en la pestaña **Aplicaciones**.
+3. Haz clic en el símbolo de engranaje <i class="fas fa-cog"></i> de la aplicación donde deseas modificar el formulario.
+4. Haz clic en el ícono de edición <i class="fas fa-edit"></i> en la fila del formulario donde deseas agregar la consulta predeterminada.
+5. En la opción **Consulta predeterminada**, selecciona la consulta personalizada que deseas para que se muestre automáticamente al abrir la lista de registros del formulario.
+6. Haz clic en el botón `Guardar`.
diff --git a/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md b/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md
index f09a39b4d..d2748314f 100644
--- a/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md
+++ b/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md
@@ -3,8 +3,8 @@ title: 'Crear formularios de Cliente y Dirección en nuevas tiendas'
 id: 46ETfuaGogKwaMau4ESAAM
 status: PUBLISHED
 createdAt: 2017-08-16T16:57:24.708Z
-updatedAt: 2023-03-28T22:59:22.957Z
-publishedAt: 2023-03-28T22:59:22.957Z
+updatedAt: 2024-06-11T17:38:43.775Z
+publishedAt: 2024-06-11T17:38:43.775Z
 firstPublishedAt: 2017-08-16T17:21:19.815Z
 contentType: tutorial
 productTeam: Master Data
@@ -36,13 +36,12 @@ Master Data v2
 Es posible crear estos formularios automáticamente, bastando seguir las instrucciones a continuación para cada tienda que se desee.
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
-2. Luego de autenticarse, acceder a la siguiente URL, a fin de efectuar una requisición (GET) a la API: `meusegundosite.vtexcrm.com.br/api/crm/pvt/provisioning`.
-3. El resultado será una pantalla en blanco en el navegador, pero que corresponde a una respuesta de status “200”.
-4. Tras algunos minutos, en el Master Data, hacer clic en **Área avanzada**.
-6. En la opción **¿Desea limpiar el cache?** Hacer clic **Sí**.
-7. Volver a la página inicial del Master Data.
-8. Hacer clic en **Recargar Aplicaciones**.
+2. Luego de autenticarse, accede a la siguiente URL, a fin de efectuar una requisición (GET) a la API: `{nombredelatienda}.vtexcrm.com.br/api/crm/pvt/provisioning`. Sustituya `{nombredelatienda}` por el nombre de su tienda.
 
-Una vez concluidos los pasos arriba, los formularios de la aplicación **Profile System** ya deberán estar disponibles en tu Master Data.
+  El resultado será una pantalla en blanco en el navegador, pero que corresponde a una respuesta de status __200 OK__.
+3. Tras algunos minutos, en el Master Data, haz clic en **Configuración avanzada**.
+4. En la opción **¿Quieres limpiar el caché?** haz clic en **Sí**.
+5. Haz clic en la aba **Apliaciones** para volver a la página inicial del Master Data.
+6. Haz clic en **Volver a cargar aplicaciones**.
 
-![3 - ES](https://images.ctfassets.net/alneenqid6w5/d2hevHhL68Siy82aO0E0s/d0cc7aa57c4520704353663cabc2d868/3_-_ES.png)
+Una vez concluidos los pasos arriba, los formularios de la aplicación **Profile System** ya deberán estar disponibles en tu Master Data.
diff --git a/docs/tutorials/es/creating-form-in-master-data.md b/docs/tutorials/es/creating-form-in-master-data.md
index e68501da3..1dff55900 100644
--- a/docs/tutorials/es/creating-form-in-master-data.md
+++ b/docs/tutorials/es/creating-form-in-master-data.md
@@ -3,8 +3,8 @@ title: 'Crear formulario en Master Data'
 id: tutorials_1047
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:35.614Z
-updatedAt: 2023-03-28T23:49:11.948Z
-publishedAt: 2023-03-28T23:49:11.948Z
+updatedAt: 2024-06-19T15:04:30.932Z
+publishedAt: 2024-06-19T15:04:30.932Z
 firstPublishedAt: 2017-04-27T23:03:43.083Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,37 +15,45 @@ legacySlug: creando-formulario-en-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-El formulario es una forma de exhibición y manipulación de una entidad de datos. El formulario es un agrupador de campos que a pesar de siempre estar ligado a una entidad no precisamente muestra todos los campos que la entidad tiene. Puede ser ajustado de acuerdo a las necesidades del cliente, inclusive una entidad puede tener diferentes formularios.
+Un formulario sirve como interfaz para la visualización y manipulación de una entidad de datos. En esencia, actúa como un agrupador de campos.
 
-## Como crear
+Aunque siempre está asociado a una entidad de datos, no es obligatorio que contenga todos los campos relacionados con ella; puede ser personalizado según la demanda. De esta manera, es posible crear diferentes formularios para una misma entidad, adaptándose a diversas necesidades. Por ejemplo, un formulario de compra puede incluir campos como ID, cliente y fecha.
 
-1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
-2. Haga click en **Aplicações.**
-3. En la aplicación que desea crear un formulario, haga click en el símbolo del engrane.
-4. Haga click en **Novo.**
-5. Complete los campos según se detalla a continuación.
-6. Haga click en el botón **Salvar.**
+Para crear un formulario, sigue los pasos a continuación:
 
-## Entendiendo los campos
+1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. Asegúrate de que se encuentra en la pestaña __Aplicaciones__.
+3. En la aplicación que desea crear un formulario, haz clic en el símbolo del engrane.
+4. Haz clic en `Nuevo`.
+5. Completa los campos según se detalla en [Campos para el nuevo formulario](#campos-para-el-nuevo-formulario).
+6. Haz clic en el botón `Guardar`.
 
-- **Nome: **Nombre del formulario.
-- **Filtros: **Campos marcados como filtro de la entidad, esos campos forman los filtros laterales del formulario. Este debe ser creado en el nombre interno del campo. Para más de un campo lo puede separar por comas. Ej.: campo1,campo2.
-- **Entidade de dados: **La entidad de datos para la cual el formulario va a ser creado.
-- **Destaques de busca: **Los campos que serán mostrados los resultados de la búsqueda. Este debe de ser registrado en el nombre del campo interno. Para más de un campo, debe de ser separado por “,”. Ejemplo: Si busco por cliente, quiero que la lista de resultados aparezca el CPF del cliente o el nombre, entonces, es necesario hacer la búsqueda de la siguiente manera: CPF, Nombre.
-- **Consultas na visualização**: Activa una nueva sección en el formulario de visualización, con registros de una entidad relacionada con la entidad del formulario. Las informaciones mostradas serán relacionadas con el registro que está sendo visualizado. Ejemplo: en la entidad Atendimiento hay un campo relacionado con la entidad Cliente. Así, en el formulario Cliente, en el campo Consultas na visualização, inserte este campo de atendimiento que se refiere a Cliente. Si el acrónimo de la entidad Atendimiento es AT y el nombre del campo es Cliente, se debe insertar: &#8220;AT.Cliente&#8221;. Así serán cargados los atendimientos del cliente que se está visualizando en el formulario. ![registrosRelacionados2](//images.contentful.com/alneenqid6w5/2NrlYdzzR66Og4waCIekGe/e4d47ef3e257c749c09c0c9151383c45/registrosRelacionados2.png)![registrosRelacionados](//images.contentful.com/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/d80177bdf01586c97f1321c74c881ac3/registrosRelacionados-1.png)
+## Campos para el nuevo formulario
+
+- **Nombre:** Nombre del formulario.
+- **Filtros:** Campos marcados como filtro de la entidad, esos campos forman los filtros laterales del formulario. Este debe ser creado en el nombre interno del campo. Para más de un campo lo puede separar por comas. Ej.: campo1,campo2.
+- **Entidad de datos:** La entidad de datos para la cual el formulario va a ser creado.
+- **Buscar destacados:** Los campos que serán mostrados los resultados de la búsqueda. Este debe de ser registrado en el nombre del campo interno. Para más de un campo, debe de ser separado por “,”. Ejemplo: Si busco por cliente, quiero que la lista de resultados aparezca el CPF del cliente o el nombre, entonces, es necesario hacer la búsqueda de la siguiente manera: CPF, Nombre.
+- **Consultas de visualización**: Activa una nueva sección en el formulario de visualización, con registros de una entidad relacionada con la entidad del formulario. Las informaciones mostradas serán relacionadas con el registro que está sendo visualizado.
+
+   Ejemplo: en la entidad __Lista de compras__ hay un campo de tipo __Relationship__ relacionado con la entidad __Cliente__. Así, en el formulario __Cliente__, en el campo __Consultas de visualización__, inserte este campo de atendimiento que se refiere a __Cliente__.
+
+   Si el acrónimo de la entidad __Lista de compras__ es __LC__ y el nombre del campo es __Cliente__, se debe insertar: `LC.Cliente`. Así serán cargados los atendimientos del cliente que se está visualizando en el formulario:
+
+   ![registrosRelacionados-es](//images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/e5f7e4a9c173af6654b4e7123d3c79c2/Untitled.png)
 
 Después de llenar los campos requeridos, aparecerán las fichas disponibles para configuración. Los siguientes son los campos para cada una de ellas.
 
-- **Campos da listagem: **Aquí deben ser seleccionados los campos que aparecerán en la lista de registros, cuando se dá click para visualizar el formulario. Para eso, basta seleccionar las cajas de selección al lado de los campos que usted desea incluir. También es posible seleccionar la largura del campo de lista, el orden de exhibición y la organización. El orden de exhibición de los campos sigue el orden de esta pantalla, es decir, para un campo que aparezca en la primera columna, haga click en la flecha hacia arriba hasta que él sea el primer campo. La organización es definida por un campo. Usted debe seleccionarlo y elijir entre orden ascendente (Asc) o descendente (Desc).
-- **Schemas de Layout: **En los Schemas de layout, será hecha la definición de como los campos realmente serán exhibidos en el formulario, tanto para visualización como para la edición y creación. Es decir, en esta parte realamente será configurado donde quedará cada campo en el formulario. Todo puede ser divido por secciones.
+- **Campos de la lista:** Aquí deben ser seleccionados los campos que aparecerán en la lista de registros, cuando se dá click para visualizar el formulario. Para eso, basta seleccionar las cajas de selección al lado de los campos que usted desea incluir. También es posible seleccionar la largura del campo de lista, el orden de exhibición y la organización.
 
-1. Haga click en el botón **Incluir nova seção**;
-2. Ingrese el campo **Nome**;
-3. Arrastre un campo de la lista de campos disponibles (**Campos disponíveis)** para la columna **Campos da coluna 1**. Lo mismo puede ser hecho para la columna** Campos da coluna 2**.
+   El orden de exhibición de los campos sigue el orden de esta pantalla, es decir, para un campo que aparezca en la primera columna, haga click en la flecha hacia arriba hasta que él sea el primer campo. La organización es definida por un campo. Usted debe seleccionarlo y elijir entre orden ascendente (Asc) o descendente (Desc).
+- **Esquemas de layout:** Aquí será hecha la definición de como los campos realmente serán exhibidos en el formulario, tanto para visualización como para la edición y creación. Es decir, en esta parte realamente será configurado donde quedará cada campo en el formulario. Todo puede ser divido por secciones.
 
-Estos trés pasos pueden ser repetidos hasta que se tenga el formulario en el formato que se desea. Es posible registrar varios campos en la misma columna así cómo es posible crear varias secciones. 
+   1. Haz clic en el botón `Agregar nueva sección`.
+   2. Ingresa el campo **Nombre** para nombrar la sección.
+   3. Arrastra un campo de la lista de **Campos disponibles** para la columna **Campos de la columna 1**. Lo mismo puede ser hecho para la columna **Campos de la columna 2**.
 
-- **Consultas: **Sirve solamente para exhibir las [consultas creadas en la lista](/es/tutorial/creando-una-cconsulta-customizada-en-el-vtex-master-data).
-- **Folha de estilo: **Es la sección para registrar los estilos (CSS) para la edición del front-end del formulario.
+   Estos trés pasos pueden ser repetidos hasta que se tenga el formulario en el formato que se desea. Es posible registrar varios campos en la misma columna así cómo es posible crear varias secciones. 
 
-<video class="wp-video-shortcode" id="video-1047-3" width="840" height="411" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/7oRARnBsVamuk8iQ0mogQa/438e55214f38f7f16634da4fbc238d68/CriandoFormulario-1.mp4?_=3" /></video>
+- **Consultas:** Sirve solamente para exhibir las [consultas creadas en la lista](https://help.vtex.com/es/tutorial/creando-una-cconsulta-customizada-en-el-vtex-master-data--tutorials_799).
+- **Hoja de estilo:** La sección para registrar los estilos (CSS) para la edición del frontend del formulario.
diff --git a/docs/tutorials/es/creating-landing-pages-per-binding.md b/docs/tutorials/es/creating-landing-pages-per-binding.md
index eb2e73d10..4e133ec85 100644
--- a/docs/tutorials/es/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/es/creating-landing-pages-per-binding.md
@@ -23,7 +23,7 @@ En el Admin, puede crear páginas de destino personalizadas según el [*binding*
 2. Seleccione el *binding* en el que debe crearse la nueva página de destino en el menú desplegable de la página.
 3. Haga clic en el botón `Crear nueva`.
 
-  ![es-landing-page-binding](https://images.ctfassets.net/alneenqid6w5/4VS1mFcJKaXeex3Cwr8V2/f22a1f99d5fe04ec192e8467ff7957cb/es-landing-page-binding.png)
+  ![es-landing-page-binding](//images.ctfassets.net/alneenqid6w5/4VS1mFcJKaXeex3Cwr8V2/f22a1f99d5fe04ec192e8467ff7957cb/es-landing-page-binding.png)
 
 4. En la sección `Detalles de la página`, rellene los campos y defina los metadatos de su nueva página de destino según los valores esperados:
 
diff --git a/docs/tutorials/es/creating-landing-pages.md b/docs/tutorials/es/creating-landing-pages.md
index 7c5c99144..20abdce60 100644
--- a/docs/tutorials/es/creating-landing-pages.md
+++ b/docs/tutorials/es/creating-landing-pages.md
@@ -3,8 +3,8 @@ title: 'Crear páginas de destino'
 id: 2DqFleXKz0Vsg3KhHLuUEB
 status: PUBLISHED
 createdAt: 2022-02-02T13:57:03.484Z
-updatedAt: 2023-03-24T22:24:37.311Z
-publishedAt: 2023-03-24T22:24:37.311Z
+updatedAt: 2024-08-01T13:10:40.896Z
+publishedAt: 2024-08-01T13:10:40.896Z
 firstPublishedAt: 2022-02-02T14:41:53.952Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -27,7 +27,7 @@ En el Admin puedes crear páginas de destino personalizadas, como páginas para
 
 2.Haz clic en **CREAR NUEVA**.
 
-![Crear Landing Pages](https://images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/b02f8122f28275b8e93a3241a7b7ba3f/cms-pages-es.png)
+![Crear Landing Pages](//images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/b02f8122f28275b8e93a3241a7b7ba3f/cms-pages-es.png)
 
 3.En la sección **Detalles de la página**, rellena los siguientes campos para definir los metadatos de la página:
 
@@ -39,6 +39,11 @@ En el Admin puedes crear páginas de destino personalizadas, como páginas para
 | Descripción | Resumen de la nueva página web que se mostrará en las páginas de resultados de los motores de búsqueda. |
 | Palabras clave | Temas que definen el contenido de la página, ayudando a mostrar la página a los usuarios interesados en los resultados de los motores de búsqueda. |
 
+<div class="alert alert-warning">
+<p>Para evitar conflictos y garantizar la integridad del sistema, no se permite modificar la URL de una ruta existente. Si es necesario modificarla, se recomienda crear una nueva página con la nueva ruta y, de ser necesario, desactivar la anterior.
+</p>
+</div>
+
 <div class = "alert alert-info">
 <p>Los cinco campos anteriores impactan directamente en los accesos a la tienda y en el posicionamiento en las páginas de resultados de los motores de búsqueda. Antes de rellenar los metadatos de la página, ten en cuenta las mejores prácticas de SEO.
 </p>
diff --git a/docs/tutorials/es/creating-merchandising-rules-manual-editor.md b/docs/tutorials/es/creating-merchandising-rules-manual-editor.md
new file mode 100644
index 000000000..6fef79910
--- /dev/null
+++ b/docs/tutorials/es/creating-merchandising-rules-manual-editor.md
@@ -0,0 +1,98 @@
+---
+title: 'Crear regla de merchandising - Editor manual'
+id: 3jrXB1MSvi14ezvKancorc
+status: PUBLISHED
+createdAt: 2024-06-27T17:14:53.957Z
+updatedAt: 2024-06-27T17:15:56.346Z
+publishedAt: 2024-06-27T17:15:56.346Z
+firstPublishedAt: 2024-06-27T17:15:56.346Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: crear-regla-de-merchandising-editor-manual
+locale: es
+legacySlug: crear-regla-de-merchandising-editor-manual
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Si deseas configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) en el Editor manual de VTEX Intelligent Search, debes seguir los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront**.
+2. En **Intelligent Search**, haz clic en **Reglas de merchandising**.
+3. Haz clic en el botón <i class="fas fa-plus"></i> `Agregar`.
+4. Rellena los siguientes campos:
+    * **Nombre de la regla**: nombre de la regla de _merchandising_. Ejemplo: promover el producto A cuando se busca «galletas de chocolate».
+    * **Fecha de inicio (opcional)**: define la fecha a partir de la cual se aplicará la regla de _merchandising_. La fecha considera la zona horaria UTC-0.
+    * **Fecha de fin (opcional)**: define la fecha en que la regla de _merchandising_ dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
+    * **Aplicar a los idiomas:** idiomas en los que se aplicará la regla de merchandising. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Haga clic en **Editor Manual**. Para más información sobre cada editor, consulte [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicion).
+6. Haz clic en `Siguiente`.
+7. Si lo necesitas, modifica la información básica ya definida sobre la nueva regla de _merchandising_ en la sección [Información general](#informacion-general).
+8. Define las [Reglas de activación](#reglas-de-activacion),  es decir, el conjunto de condiciones que determinan cuándo se aplicará la regla de merchandising.
+9. Define las [Reglas de personalización](#regras-de-personalizacion), es decir, el conjunto de condiciones que controlan que el resultado de las búsquedas cumpla con las reglas de activación definidas en el paso 8.
+  Para aplicar el efecto de personalización deseado, debes definir una o varias condiciones en esta etapa. Si deseas conocer cómo registrar una condición, lee [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+10. Haz clic en `Guardar`.
+
+<div class="alert alert-info">
+  <p>Una vez guardados, la actualización de los cambios en las reglas de merchandising demoran un promedio de dos minutos.</p>
+</div>
+
+## Ejemplo
+
+Considera el siguiente ejemplo: deseas promover productos de la marca Beautyx durante la semana de un carnaval de modo que cuando el cliente busque «jabón» o «champú», la búsqueda promueva los productos de la marca Beautyx. Para esto, debes configurar la regla de _merchandising_ del siguiente modo:
+
+* **Nombre**: Promoción de carnaval
+* **Fecha de inicio**: selecciona el primer día del carnaval.
+* **Fecha de fin**: selecciona el último día del carnaval.
+* **Reglas de activación:**
+    * `Término es jabón`
+        `o`
+    * `Término es champú`
+* **Reglas de personalización**:
+    * **Promover**
+        * `marca es beautyx`
+
+## Campos del Editor manual
+
+### Información general
+
+* **Nombre**: nombre de la regla de _merchandising_. Ejemplo: promover el producto A cuando se buscan «galletas de chocolate».
+* **Fecha de inicio**: define la fecha a partir de la cual se aplicará la regla de _merchandising_. La fecha considera la zona horaria UTC-0.
+* **Fecha de fin**: define la fecha en que la regla de _merchandising_ dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
+* **Regiones:** idiomas en los que se aplicará la regla de _merchandising_.
+
+### Reglas de activación
+
+* **Activación global**: si activas esta opción, la regla de _merchandising_ siempre estará activa e incluirá todos los términos de búsqueda y filtros sin necesidad de configurar las condiciones para las reglas de activación. Esta funcionalidad te permite agregar, eliminar, promover y dejar de promover productos en todas las búsquedas de la tienda.
+
+    En cambio, si optas por mantener desactivada la activación global, deberás registrar — al menos — una condición para componer las reglas de activación. Si deseas obtener información detallada sobre cómo registrar una condición, consulta  [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+
+* <i class="fa-solid fa-link"></i> `Rellenar a partir de una URL`: agrega la URL de la página de búsqueda en la que se aplicarán las reglas de activación. La URL debe incluir  `map` y `query` para funcionar y respetar el siguiente formato: `https://{nombreDeCuenta}.myvtex.com/busca/{término}?map=ft&query={término}`. Debes reemplazar `{nombreDeCuenta}` por el nombre de la cuenta VTEX y `{término}` por el término de búsqueda.
+
+* `Agregar condición`: al crear una condición, la regla de _merchandising_ solo se aplicará a los casos que cumplan con la combinación de las condiciones establecidas. Para saber cómo crear condiciones, consulta [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+
+### Reglas de personalización
+
+* **Agregar**: incluye las condiciones seleccionadas en el resultado, es decir, agrega productos que no estarían en el resultado de la búsqueda. Los resultados de la búsqueda no consideran el orden de los productos registrados.
+
+    Los productos agregados también se sitúan en las primeras posiciones, sin embargo, tienen un peso inferior que aquellos de la opción **Promover**. Por lo tanto, si tienes un producto agregado y otro promovido, el producto promovido aparecerá primero y luego lo hará el agregado.
+
+* **Remover**: excluye las condiciones seleccionadas del resultado, es decir, elimina los productos que estarán en el resultado de la búsqueda.
+
+  <div class="alert alert-info">
+   <p><strong>Agregar</strong> y <strong>Eliminar</strong> son compatibles con otros tipos de formas de ordenar que no se basan en la relevancia configurada. Por lo tanto, si agregas o eliminas un producto utilizando una regla de <em>merchandising </em>y si, por ejemplo, el cliente de tu tienda ordena los resultados de búsqueda por precio, los productos se ordenarán por precio, pero los productos mostrados respetarán la regla de <em>merchandising</em>.</p>
+  </div>
+
+* **Promover**: resalta las condiciones seleccionadas en el resultado. Da más relevancia a un producto que ya aparecería en el resultado de la búsqueda.
+
+    El orden de las condiciones influye en la prioridad de exhibición de los productos. Además, cualquier producto que se incluye en este campo solo se promociona en un único resultado.
+
+* **Dejar de promover**: oculta las condiciones seleccionadas en el resultado. Permite dejar de priorizar un producto que ya aparece en los resultados de la búsqueda.
+
+  <div class="alert alert-info">
+   <p><strong>Promover</strong> y <strong>Dejar de promover</strong> solo funcionan cuando el cliente de la tienda ordena los resultados de la búsqueda por relevancia. En cambio, si ordena los resultados por precio, por ejemplo, los productos se ordenarán estrictamente por precio y no se utilizará la regla de <em>merchandising</em>.</p>
+  </div>
+
+  <div class="alert alert-warning">
+   <p>No configures condiciones que afecten a los mismos productos tanto en la sección <strong>Promover</strong> como en la sección <strong>Dejar de promover</strong> porque se producirán efectos opuestos. Si la configuración de esta condición es incorrecta, esa configuración incorrecta afecta negativamente el comportamiento de la funcionalidad y no se mostrarán los resultados deseados.</p>
+  </div>
diff --git a/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
index 988c29088..703b2c9b0 100644
--- a/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Crear regla de merchandising - Editor visual (Beta)'
 id: 6xteumx9MsDt0uEppbChu3
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-03T21:05:14.304Z
-updatedAt: 2023-04-11T22:34:40.303Z
-publishedAt: 2023-04-11T22:34:40.303Z
+updatedAt: 2024-01-29T17:17:03.584Z
+publishedAt: 
 firstPublishedAt: 2023-04-03T21:30:34.359Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,59 +19,80 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
   <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solamente clientes seleccionados pueden acceder a ella. Si tienes interés en implementarla en tu negocio, comunícate con <a href="https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
 </div>
 
-El Editor visual (beta) de las [reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) de VTEX Intelligent Search permite realizar las acciones que se indican en la imagen a continuación:
+Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) de VTEX Intelligent Search utilizando el [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), sigue los pasos a continuación.
 
-![visual-merch-rules-ES](https://images.ctfassets.net/alneenqid6w5/5Pah0D3Y9CfUyczqFR99bd/21b0a087a9f1172d279ce68672813e94/visual-merch-rules-ES.png)
+1. En el Admin VTEX, accede a **Storefront**, o ingresa **Storefront **en la barra de búsqueda.
+2. En **Intelligent Search**, haz clic en **Reglas de merchandising**.
+3. Haz clic en el botón `+ Agregar`.
+4. Rellena los siguientes campos:
+
+    * **Nombre de la regla**: nombre de la regla de merchandising. Ejemplo: promocionar el producto A cuando el cliente busque "galletas de chocolate".
+    * **Fecha de inicio (opcional)**: define la fecha a partir de la cual se aplicará la regla de merchandising. La fecha considera la zona horaria UTC-0.
+    * **Fecha de fin (opcional)**: define la fecha en que la regla de merchandising dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
+    * **Aplicar a los idiomas:** idiomas en los que se aplicará la regla de merchandising. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Haz clic en **Editor visual**. Para más información sobre cada editor, consulta [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
+6. Haz clic en `Siguiente`.
+7. Define al menos un término de búsqueda o filtro para aplicar la regla de merchandising:
+
+    * Para definir un término de búsqueda, ingresa el término en la barra de búsqueda (ítem **II** de la sección [Acciones disponibles en el Editor visual](https://docs.google.com/document/d/1zUZ_FhSGgJ8b3E0oF-q04sfcaDw6_btr/edit#bookmark=id.2et92p0)).
+    * Si deseas crear un filtro para aplicar la regla de merchandising (ítem **III** de la sección [Acciones disponibles en el Editor visual](https://docs.google.com/document/d/1zUZ_FhSGgJ8b3E0oF-q04sfcaDw6_btr/edit#bookmark=id.2et92p0)), sigue las instrucciones descritas en la sección [Agregar filtros y condiciones](https://help.vtex.com/es/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes).
+8. Si lo deseas, realiza las acciones opcionales que se indican a continuación para personalizar los resultados de la búsqueda.
+    * Definir cantidad de ítems por fila en los resultados de búsqueda.
+    * Definir cantidad de ítems por página en los resultados de búsqueda.
+    * Ocultar producto en los resultados de búsqueda.
+    * Fijar producto, es decir, anclarlo en las primeras posiciones de los resultados de búsqueda.
+    * Arrastrar el producto fijado a la posición deseada en los resultados de búsqueda.
+    * Editar la configuración inicial de la regla de merchandising, que incluye el nombre de la regla, las fechas de inicio y fin y, si la tienda utiliza la [Configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO), los idiomas a los que se aplicará.
+
+      Más información sobre estas acciones en los puntos **4, 5, 6, 8, 9** y **11** de la sección [Acciones disponibles en el Editor visual](#acciones-disponibles-en-el-editor-visual).
+9. Haz clic en `Guardar`.
+
+ <div class="alert alert-info">
+  <p>Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.</p>
+</div>
+
+## Acciones disponibles en el Editor visual
+
+El Editor visual de reglas de merchandising de VTEX Intelligent Search permite realizar las acciones que se ilustran en la imagen siguiente:
+
+![visual-merch-rules-ES-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
 
 <ol class="mv7" type="I">
-    <li class="t-body c-on-base mb5 lh-copy">Editar el nombre de la regla de <em>merchandising</em>.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir los términos de búsqueda para aplicar la regla de
-        <em>merchandising</em>.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#agregar-filtros-y-condiciones" rel="noopener noreferrer" target="_self"
-            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">los
-            filtros</a> para aplicar la regla de <em>merchandising</em>.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir la cantidad de ítems por línea.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir la cantidad de ítems por página.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Navegar entre las páginas de resultado de la búsqueda.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Arrastrar el producto a la posición deseada en los resultados de la
-        búsqueda. Solo se pueden arrastrar productos que estén fijos (acción IX).</li>
-    <li class="t-body c-on-base mb5 lh-copy">Ocultar producto en los resultados de búsqueda. No podrás anular esta
-        acción, por lo tanto, deberás crear otra regla de <em>merchandising</em> para que un producto vuelva a aparecer
-        en los resultados.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Fijar el producto en las primeras posiciones de los resultados de la
-        búsqueda. Al fijar el producto A e inmediatamente después el producto B, los resultados de la búsqueda
-        respetarán este orden y estos productos aparecerán antes que los demás.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Ver detalles del producto.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar nombre de la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir los términos de búsqueda para aplicar la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#agregar-filtros-y-condiciones" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a> para aplicar la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir cantidad de ítems por fila en los resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir cantidad de ítems por página en los resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ocultar producto en los resultados de búsqueda. En el Editor visual, los productos ocultos aparecen en gris con el ícono del ojo tachado <i class="far fa-eye-slash"></i>. Para volver a mostrar un producto oculto, pasa el mouse sobre él y haz clic en el ícono del ojo <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ver detalles del producto. La información mostrada es:<br /><br />
+	   <ul>
+		  <li class="t-body c-on-base mb5 lh-copy"><strong>Disponible:</strong> indica si el producto está o no disponible en la tienda.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Clics:</strong> número de clics durante los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Pedidos:</strong> número de pedidos realizados que incluyen el producto en los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Ingresos:</strong> ingresos que generó el producto en los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Fecha de lanzamiento:</strong> fecha de lanzamiento del producto.</li> 
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Promoción:</strong> indica si el producto forma parte o no de una promoción.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Descuento:</strong> descuento aplicado sobre el producto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Variedad de matriz disponible: </strong>representa el porcentaje de SKU disponibles del producto. Por ejemplo, si un producto tiene cinco SKU y solo hay tres disponibles, la variedad de matriz disponible será del 60 %, representada como 0.6 en este campo. Si todos los SKU están disponibles, el valor del campo será 1.</li>
+	   </ul>
+    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Arrastrar producto anclado a la posición deseada en los resultados de búsqueda. Solo pueden arrastrarse productos que hayan sido anclados (acción <strong>IX</strong> de esta lista).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Anclar producto, es decir, situarlo en las primeras posiciones de los resultados de búsqueda. Al anclar el producto A y, a continuación, el producto B, aparecerán en ese orden en los resultados de búsqueda, antes que los demás. Para desanclar un producto, pasa el cursor sobre él y haz clic en el ícono de la tachuela tachada <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar la configuración inicial de la regla de merchandising, que incluye el nombre de la regla, las fechas de inicio y fin y, si la tienda utiliza la <a rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO">Configuración multidioma (beta)</a>, los idiomas a los que se aplicará.</li>
     <li class="t-body c-on-base mb5 lh-copy">Cancelar edición.</li>
     <li class="t-body c-on-base mb5 lh-copy">Guardar configuración.</li>
 </ol>
 
-## Configurar regla de merchandising
-
-Si deseas configurar una regla de _merchandising_ en el Editor visual, sigue los pasos que se indican a continuación.
-
-1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront**.
-2. En **Intelligent Search**, haz clic en **Reglas de merchandising**.
-3. Haz clic en el botón `Nuevo`.
-4. Rellena los siguientes campos:
-    * **Nombre de la regla**: nombre de la regla de _merchandising_. Ejemplo: promover el producto A cuando se buscan «galletas de chocolate».
-    * **Fecha de inicio (opcional)**: define la fecha a partir de la cual se aplicará la regla de _merchandising_. La fecha considera la zona horaria UTC-0.
-    * **Fecha de fin (opcional)**: define la fecha en que la regla de _merchandising _dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
-    * **Idiomas:** idiomas en los que se aplicará la regla de _merchandising_.
-5. Haz clic en **Editor visual**. Para más información sobre cada editor, consulta [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicion).
-6. Haz clic en `Siguiente`.
-7. Para definir un término de búsqueda que determine la aplicación de la regla de _merchandising_, escribe el término en la barra de búsqueda (ítem II de la imagen anterior). Debes definir al menos un término o un filtro (paso 8) para la aplicación de la regla.
-8. Si deseas crear un filtro para aplicar la regla de _merchandising_ (punto III de la imagen anterior), sigue cada uno de los pasos descritos en la sección [Agregar filtros y condiciones](#agregar-filtros-e-condicoes). Debes definir al menos un filtro o un término (paso 7) para la aplicación de la regla.
-9. Si lo deseas, realiza el resto de las acciones opcionales para personalizar los resultados de la búsqueda (ítems IV, V, VII, VIII, IX de la imagen anterior).
-10. Haz clic en `Guardar`.
-
 ### Agregar filtros y condiciones
 
 El filtro es un atributo seleccionable predefinido que restringe los resultados de la búsqueda, por ejemplo, permite filtrar por todos los productos de una categoría o marca, entre otras condiciones. Puedes agregar una o más condiciones a un filtro, tal como se muestra a continuación.
 
-![filtros-merchrules-es](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
+![filtros-merchrules-es](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
 
-Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
+Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
 
 1. Haz clic en `Filtro`.
 2. Haz clic en `Agregar condición`.
@@ -81,4 +102,3 @@ Si deseas agregar una condición en el Editor visual, sigue cada uno de los paso
 Las condiciones definidas pueden funcionar en forma conjunta (`y`) o alternativamente (`o`).
 
 En el menú de cada una de las condiciones existentes, puedes `Duplicar` o `Eliminar` la condición. Si deseas desactivar todas las condiciones creadas, haz clic en `Borrar filtros`.
-
diff --git a/docs/tutorials/es/creating-merchandising-rules-visual-editor.md b/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
new file mode 100644
index 000000000..4ba815a79
--- /dev/null
+++ b/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
@@ -0,0 +1,100 @@
+---
+title: 'Crear regla de merchandising - Editor visual'
+id: 3gPO5CMJ3Off0OtA3EPzow
+status: PUBLISHED
+createdAt: 2024-06-27T17:16:02.371Z
+updatedAt: 2024-06-27T17:16:43.289Z
+publishedAt: 2024-06-27T17:16:43.289Z
+firstPublishedAt: 2024-06-27T17:16:43.289Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: crear-regla-de-merchandising-editor-visual
+locale: es
+legacySlug: crear-regla-de-merchandising-editor-visual
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) de VTEX Intelligent Search utilizando el [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), sigue los pasos a continuación.
+
+1. En el Admin VTEX, accede a **Storefront**, o ingresa **Storefront **en la barra de búsqueda.
+2. En **Intelligent Search**, haz clic en **Reglas de merchandising**.
+3. Haz clic en el botón `+ Agregar`.
+4. Rellena los siguientes campos:
+
+    * **Nombre de la regla**: nombre de la regla de merchandising. Ejemplo: promocionar el producto A cuando el cliente busque "galletas de chocolate".
+    * **Fecha de inicio (opcional)**: define la fecha a partir de la cual se aplicará la regla de merchandising. La fecha considera la zona horaria UTC-0.
+    * **Fecha de fin (opcional)**: define la fecha en que la regla de merchandising dejará de aplicarse a las búsquedas de la tienda. La fecha considera la zona horaria UTC-0.
+    * **Aplicar a los idiomas:** idiomas en los que se aplicará la regla de merchandising. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Haz clic en **Editor visual**. Para más información sobre cada editor, consulta [Tipos de edición](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
+6. Haz clic en `Siguiente`.
+7. Define al menos un término de búsqueda o filtro para aplicar la regla de merchandising:
+
+    * Para definir un término de búsqueda, ingresa el término en la barra de búsqueda (ítem **II** de la sección [Acciones disponibles en el Editor visual](https://docs.google.com/document/d/1zUZ_FhSGgJ8b3E0oF-q04sfcaDw6_btr/edit#bookmark=id.2et92p0)).
+    * Si deseas crear un filtro para aplicar la regla de merchandising (ítem **III** de la sección [Acciones disponibles en el Editor visual](https://docs.google.com/document/d/1zUZ_FhSGgJ8b3E0oF-q04sfcaDw6_btr/edit#bookmark=id.2et92p0)), sigue las instrucciones descritas en la sección [Agregar filtros y condiciones](https://help.vtex.com/es/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes).
+8. Si lo deseas, realiza las acciones opcionales que se indican a continuación para personalizar los resultados de la búsqueda.
+    * Definir cantidad de ítems por fila en los resultados de búsqueda.
+    * Definir cantidad de ítems por página en los resultados de búsqueda.
+    * Ocultar producto en los resultados de búsqueda.
+    * Fijar producto, es decir, anclarlo en las primeras posiciones de los resultados de búsqueda.
+    * Arrastrar el producto fijado a la posición deseada en los resultados de búsqueda.
+    * Editar la configuración inicial de la regla de merchandising, que incluye el nombre de la regla, las fechas de inicio y fin y, si la tienda utiliza la [Configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO), los idiomas a los que se aplicará.
+
+      Más información sobre estas acciones en los puntos **4, 5, 6, 8, 9** y **11** de la sección [Acciones disponibles en el Editor visual](#acciones-disponibles-en-el-editor-visual).
+9. Haz clic en `Guardar`.
+
+ <div class="alert alert-info">
+  <p>Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.</p>
+</div>
+
+## Acciones disponibles en el Editor visual
+
+El Editor visual de reglas de merchandising de VTEX Intelligent Search permite realizar las acciones que se ilustran en la imagen siguiente:
+
+![visual-merch-rules-ES-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Editar nombre de la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir los términos de búsqueda para aplicar la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#agregar-filtros-y-condiciones" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a> para aplicar la regla de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir cantidad de ítems por fila en los resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir cantidad de ítems por página en los resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ocultar producto en los resultados de búsqueda. En el Editor visual, los productos ocultos aparecen en gris con el ícono del ojo tachado <i class="far fa-eye-slash"></i>. Para volver a mostrar un producto oculto, pasa el mouse sobre él y haz clic en el ícono del ojo <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ver detalles del producto. La información mostrada es:<br /><br />
+	   <ul>
+		  <li class="t-body c-on-base mb5 lh-copy"><strong>Disponible:</strong> indica si el producto está o no disponible en la tienda.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Clics:</strong> número de clics durante los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Pedidos:</strong> número de pedidos realizados que incluyen el producto en los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Ingresos:</strong> ingresos que generó el producto en los últimos 90 días.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Fecha de lanzamiento:</strong> fecha de lanzamiento del producto.</li> 
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Promoción:</strong> indica si el producto forma parte o no de una promoción.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Descuento:</strong> descuento aplicado sobre el producto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Variedad de matriz disponible: </strong>representa el porcentaje de SKU disponibles del producto. Por ejemplo, si un producto tiene cinco SKU y solo hay tres disponibles, la variedad de matriz disponible será del 60 %, representada como 0.6 en este campo. Si todos los SKU están disponibles, el valor del campo será 1.</li>
+	   </ul>
+    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Arrastrar producto anclado a la posición deseada en los resultados de búsqueda. Solo pueden arrastrarse productos que hayan sido anclados (acción <strong>IX</strong> de esta lista).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Anclar producto, es decir, situarlo en las primeras posiciones de los resultados de búsqueda. Al anclar el producto A y, a continuación, el producto B, aparecerán en ese orden en los resultados de búsqueda, antes que los demás. Para desanclar un producto, pasa el cursor sobre él y haz clic en el ícono de la tachuela tachada <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de búsqueda.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar la configuración inicial de la regla de merchandising, que incluye el nombre de la regla, las fechas de inicio y fin y, si la tienda utiliza la <a rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO">Configuración multidioma (beta)</a>, los idiomas a los que se aplicará.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Cancelar edición.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Guardar configuración.</li>
+</ol>
+
+### Agregar filtros y condiciones
+
+El filtro es un atributo seleccionable predefinido que restringe los resultados de la búsqueda, por ejemplo, permite filtrar por todos los productos de una categoría o marca, entre otras condiciones. Puedes agregar una o más condiciones a un filtro, tal como se muestra a continuación.
+
+![filtros-merchrules-es](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
+
+Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
+
+1. Haz clic en `Filtro`.
+2. Haz clic en `Agregar condición`.
+3. Rellena las condiciones que deseas crear. Las opciones disponibles se describen en [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+4. Haz clic en `Guardar`.
+
+Las condiciones definidas pueden funcionar en forma conjunta (`y`) o alternativamente (`o`).
+
+En el menú de cada una de las condiciones existentes, puedes `Duplicar` o `Eliminar` la condición. Si deseas desactivar todas las condiciones creadas, haz clic en `Borrar filtros`.
diff --git a/docs/tutorials/es/creating-price-tables.md b/docs/tutorials/es/creating-price-tables.md
index d6b6aa64f..918751b92 100644
--- a/docs/tutorials/es/creating-price-tables.md
+++ b/docs/tutorials/es/creating-price-tables.md
@@ -1,15 +1,15 @@
 ---
 title: 'Creación de tablas de precios '
 id: 58YmY2Iwggyw4WeSCGg24S
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-12-02T21:35:14.220Z
-updatedAt: 2020-11-27T19:39:45.134Z
-publishedAt: 2019-12-31T15:26:59.677Z
+updatedAt: 2023-11-30T16:46:22.924Z
+publishedAt: 2023-11-30T16:46:22.924Z
 firstPublishedAt: 2018-12-02T21:36:28.350Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
 author: 1E4UkWguFZAXjkguvNHPIv
-slug: creación-de-tablas-de-precios
+slug: creacion-de-tablas-de-precios
 locale: es
 legacySlug: creación-de-tablas-de-precios
 subcategory: 4id9W3RDyw02CasOm2C2iy
@@ -17,13 +17,13 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Para crear una Tabla de Precios siga estos pasos:
 
- 1. Haga clic en **Precios** en el menú izquierdo de la página.
- 2. Haga clic en **Lista de Precios**.
- 3. Haga clic en el botón **Tabla de Precios**.
- 4. Seleccione **Crear nueva Tabla de Precios**.
- 5. Seleccione el nombre de la tabla de precios que desea crear y haga clic en el botón azul **Crear tabla de precios**.
- 
- ![TutorialPriceTableES 2806](https://images.ctfassets.net/alneenqid6w5/2r1rSI1tIDEWDMDSxJmt3b/9559174f94375c2a8c4c080d6e4d3609/TutorialPriceTableES_2806.gif)
+ 1. En el Admin VTEX, accede a **Catálogo > Precios > lista de precios >** o escribe **Lista de precios** en la barra de búsqueda en la parte superior de la página.
+ 2. Haga clic en **Tabla de Precios**.
+ 3. Seleccione **Crear nueva tabla de precios**.
+ 4. Elija el nombre de la tabla de precios que desea crear.
+ 5. Clic **Crear tabla de precios**.
+
+![creacion-de-tablas-de-precios](//images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/fdc959523e5c2608a20bb3f454d064a3/criar-tabela-precos-es.gif)
 
 Para encontrar una Tabla de Precio:
 
@@ -41,4 +41,3 @@ No se pueden añadir caracteres especiales a los nombres de las tablas de precio
 Por motivos de seguridad, no se puede eliminar tablas de precio manualmente. Si necesita borrar una tabla de precios, abra una llamada con el soporte de VTEX.
 </div>
 
-
diff --git a/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
index ee9fca67a..55ebb15d5 100644
--- a/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
@@ -62,9 +62,9 @@ En la siguiente configuración, por ejemplo, solo los registros de ``empleados``
 
 De esta manera también se podría establecer `empleado=false`, donde solo los registros de `empleado` con un valor `false` en el campo obtendrían la promoción.
 
-![Campo funcionário Master Data ES](https://images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/8fdaea6b5ced25c76bea649ccc0e9e12/Campo_funcion__rio_Master_Data_ES.png)
+![Campo funcionário Master Data ES](//images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/8fdaea6b5ced25c76bea649ccc0e9e12/Campo_funcion__rio_Master_Data_ES.png)
 
-![Cluster de clientes ES](https://images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/cb74a3f5ecba7fe987381e62543a13de/Cluster_de_clientes_ES.png)
+![Cluster de clientes ES](//images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/cb74a3f5ecba7fe987381e62543a13de/Cluster_de_clientes_ES.png)
 
 Dado un campo **[Varchar](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#)**, podríamos configurar `empleado="sí"` para que solo los clientes con el valor `"sí"` en el campo recibieran la promoción.
 
@@ -82,8 +82,8 @@ La expresión `{nombredelapropiedad} contains {valor}` debe utilizarse cuando la
 
 Por ejemplo, si quiere crear un clúster sólo con clientes cuyas direcciones de correo electrónico contengan `@test.com`, la configuración sería igual a la representada en la imagen siguiente.
 
-![Campo Email Master Data](https://images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
+![Campo Email Master Data](//images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
 
-![cluster email ES](https://images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/8139bb8d0546b62edf917418c5c92c5b/cluster_email_ES.PNG)
+![cluster email ES](//images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/8139bb8d0546b62edf917418c5c92c5b/cluster_email_ES.PNG)
 
 En este caso, `email contains test.com` será verdadero, por ejemplo, cuando el valor sea `joao@test.com` y falso cuando el valor sea `joao@test.org`.
diff --git a/docs/tutorials/es/creating-promotions.md b/docs/tutorials/es/creating-promotions.md
index 5d84817d2..1ba006a07 100644
--- a/docs/tutorials/es/creating-promotions.md
+++ b/docs/tutorials/es/creating-promotions.md
@@ -78,7 +78,7 @@ Puedes cambiar las configuraciones y los datos de cualquier promoción siguiendo
 La programación de una promoción se produce cuando esta se crea (o modifica) con una fecha y hora de validez posteriores al momento actual. La hora considerada es la del sistema del computador en el que se creó la promoción, sin tener en cuenta los ajustes de zona horaria.
 Estas promociones se pueden identificar fácilmente en la página principal de Promociones, ya que tienen una franja naranja con la palabra programada en la esquina superior derecha de la tarjeta, como se muestra a continuación:
 
-![programada](https://images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/cc495af0c2c31c27cc53870ed7a95aee/programada..png)
+![programada](//images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/cc495af0c2c31c27cc53870ed7a95aee/programada..png)
 
 Para programar una promoción, sigue los pasos descritos en la sección [Programar promociones](https://help.vtex.com/es/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI?&utm_source=autocomplete#programar-promociones) del artículo [Programación de funcionalidades para eventos especiales](https://help.vtex.com/pt/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI).
 
diff --git a/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md
index b02797b9b..0e5b152ec 100644
--- a/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md
@@ -1,9 +1,9 @@
 ---
 title: 'Crear relaciones entre entidades de Master Data utilizando el Admin'
 id: 1qzbCit8SYXbKwrT5x2FfA
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-08-11T13:48:26.272Z
-updatedAt: 2022-10-17T19:11:39.513Z
+updatedAt: 2024-06-06T19:36:29.525Z
 publishedAt: 2022-10-17T19:11:39.513Z
 firstPublishedAt: 2020-08-18T19:47:29.772Z
 contentType: tutorial
@@ -31,23 +31,23 @@ En este ejemplo se crea una entidad denominada `Lista de Compras` que se relacio
 
 1. Haga clic en la pestaña **Aplicações**.
 2. Después, haga clic en el botón **Advanced settings**.  
-![Configuraciones Avanzadas](https://images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
+![Configuraciones Avanzadas](//images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
 3. Haga clic en la opción **Estrutura de dados**. Eso abrirá una nueva pestaña a Dynamic Storage (DS).  
-![Estructura de datos](https://images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
+![Estructura de datos](//images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
 4. En Dynamic Storage, haga clic en la pestaña **Data Entities**.
 5. Si desea crear una relación en una nueva entidad, haga clic en el botón **Add new** para crear una nueva entidad de datos. _En caso de que quiera crear una relación en una entidad existente, haga clic en el botón **Edit** de dicha entidad, y continue a partir del paso 7_.  
-![Agregar nueva entidad de datos](https://images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
-![Editar entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
+![Agregar nueva entidad de datos](//images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
+![Editar entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
 6. Configure la entidad que será creada completando los campos **Acronym** y **Name** y agregando los campos deseados. En este ejemplo, la entidad utilizará el nombre `Lista de compras`, acrónimo `LC` y campo `compras` de tipo `Varchar 750`.
 7. Agregue un campo de tipo `Relationship` y defina su nombre. En el ejemplo, este se denominará `Cliente`.
 8. Luego, haga clic en el botón **Edit** (ícono de engranaje) del campo de relación para configurarlo.
 9. En la configuración **Custom field type settings** seleccione la entidad a la que desea hacer referencia y el campo que se mostrará en esa relación. En este ejemplo, la relación se hará en la entidad "Cliente" y se mostrará el campo "email".  
-![Relación entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
+![Relación entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
 10. Haga clic en **Save** para guardar los ajustes.  
-![Guardar entidad de datos](https://images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
+![Guardar entidad de datos](//images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
 11. Vuelva a la lista de entidades. Recuerde que tiene que publicar la nueva entidad haciendo clic en el botón **Publish** (ícono de disquete) de la misma. También puede ser necesario actualizar las aplicaciones para que se implementen las alteraciones, para eso vaya a **Aplicações** y haga clic en el botón **Reload applications**.  
-![Publicar entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
-![Master Data Reload applications](https://images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
+![Publicar entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
+![Master Data Reload applications](//images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
 
 ## ¿Cómo crear una relación entre documentos?
 
@@ -55,45 +55,45 @@ Las relaciones también se pueden aplicar a documentos específicos de las entid
 
 1. Para relacionar los documentos agregue el campo de relación en el formulario de la entidad que contiene la referencia. Para facilitar eso, puede definir el campo como un cuadro combinado para mostrar todos los valores disponibles. Puede ver más detalles en el artículo [Crear un campo en Master Data](https://help.vtex.com/es/tutorial/como-crear-un-campo-en-master-data--frequentlyAskedQuestions_1829#crm).
 2. Seleccione el valor deseado (en este caso, el cliente al que se relacionará la lista de compras).  
-![Seleccionar relación de documento Master Data](https://images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/0db9c1fe76beb2a136ed446e72982438/Selecionar_relacionamento_de_documento_Master_Data.png)
+![Seleccionar relación de documento Master Data](//images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/0db9c1fe76beb2a136ed446e72982438/Selecionar_relacionamento_de_documento_Master_Data.png)
 3. Haga clic en **Salvar** para guardar la configuración.
 
 Cuando agregue el campo en la tabla, verifique los valores que se definieron.
-![Tabla de relaciones de documentos Master Data](https://images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/d120164f9a1d553be92eb2eefb6cf251/Tabela_de_relacionamento_de_documentos_Master_Data.png)
+![Tabla de relaciones de documentos Master Data](//images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/d120164f9a1d553be92eb2eefb6cf251/Tabela_de_relacionamento_de_documentos_Master_Data.png)
 
 ## ¿Cómo agregar filtros a los campos de relación?
 
 Las relaciones se mantienen a través de los IDs de los documentos. Por tanto, cuando intente ingresar el valor del campo de relación como filtro en el formulario solo obtendrá los valores de los IDs de los documentos referenciados, y no los valores del campo elegido para cada documento. Las siguientes imágenes muestran ese resultado. Puede encontrar más información sobre filtros en el artículo [Filtrar datos en Master Data](https://help.vtex.com/es/tutorial/filtrando-dados-no-master-data--tutorials_778)
 
-![Seleccionar filtro de relación](https://images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/715c368b1c0d3ed81a5eb25f06bb3bcc/Selecionar_filtro_relacionamento.png)
+![Seleccionar filtro de relación](//images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/715c368b1c0d3ed81a5eb25f06bb3bcc/Selecionar_filtro_relacionamento.png)
 
-![Filtro de relación ID](https://images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/1218b7078443c3666502a20333970467/Filtro_relacionamento_ID.png)
+![Filtro de relación ID](//images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/1218b7078443c3666502a20333970467/Filtro_relacionamento_ID.png)
 
 En caso de que desee ver los valores de los campos, y no sus IDs, se puede filtrar estos mediante un campo automático. Para eso: 
 
 1. En el Master Data, vaya a **Aplicações** > **Advanced settings** > **Estrutura de dados** para acceder a Dynamic Storage.
 2. Luego, acceda a las entidades de datos en **Data Entities**.
 3. En la entidad que contiene la relación (en este caso `Lista de Compras`), haga clic en el botón **Editar**.  
-![Editar entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
+![Editar entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
 4. Haga clic en la pestaña **Automatic fields**.
 5. Luego, clic en el botón **New Calculated field**.  
-![Relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
+![Relacionamento automatic fields](//images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
 6. Complete los campos **Name**, **Display Name** y **Type** según lo deseado. En este ejemplo se utilizarán `emailCliente`, `E-mail cliente` y Varchar 50.
 7. Haga clic en el ícono de engranaje para realizar una configuración adicional.  
-![Nombre automatic field](https://images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/38f68d5ee8cc3d06b6e26cc571f047f0/Nome_automatic_field.png)
+![Nombre automatic field](//images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/38f68d5ee8cc3d06b6e26cc571f047f0/Nome_automatic_field.png)
 8. Realice los ajustes que desea y utilice la fórmula para elegir el campo de la entidad relacionada que desea mostrar en el fitro. En este ejemplo, se utilizará el correo electrónico del cliente.
 
-![Configurar relación automatic fields](https://images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/79d487b39c0ca6abdc98826232dc17d0/Configurar_relacionamento_automatic_fields.png)
+![Configurar relación automatic fields](//images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/79d487b39c0ca6abdc98826232dc17d0/Configurar_relacionamento_automatic_fields.png)
 9. Haga clic en el botón **Validate**.
 10. En la ventana que se abrirá, ingrese un email genérico y haga clic en **Ok**.  
-![Validar automatic field](https://images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
+![Validar automatic field](//images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
 11. Luego, aparecerá un aviso indicando que la fórmula es válida, como se muestra en la siguiente imagen. Haga clic en **Ok**.  
-![Fórmula válida automatic field](https://images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
+![Fórmula válida automatic field](//images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
 12. Para finalizar, guarde los ajustes haciendo clic en **Save**.
 
 Luego de los anteriores pasos el filtro se aplica a la relación. En el formulario de la entidad (`Lista de Compras`), agregue el campo al filtro después de actualizar los registros.
-![Seleccionar filtro de relación valor](https://images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/17f4b5b4e9a5a67c197f9351501a8598/Selecionar_filtro_relacionamento_valor.png)
+![Seleccionar filtro de relación valor](//images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/17f4b5b4e9a5a67c197f9351501a8598/Selecionar_filtro_relacionamento_valor.png)
 
 De esta forma podemos ver el filtro con los valores en vez de los IDs.
-![Filtro relación valor](https://images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/2c5f45e9e00c7a9c37cec54dea7c35eb/Filtro_relacionamento_valor.png)
+![Filtro relación valor](//images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/2c5f45e9e00c7a9c37cec54dea7c35eb/Filtro_relacionamento_valor.png)
 
diff --git a/docs/tutorials/es/creating-roles.md b/docs/tutorials/es/creating-roles.md
new file mode 100644
index 000000000..1ec4d8562
--- /dev/null
+++ b/docs/tutorials/es/creating-roles.md
@@ -0,0 +1,98 @@
+---
+title: 'Crear nuevo rol'
+id: qGtNQpKSSAduX94l2WZBW
+status: DRAFT
+createdAt: 2023-11-30T16:42:01.373Z
+updatedAt: 2023-11-30T21:59:23.416Z
+publishedAt: 
+firstPublishedAt: 2023-11-30T17:12:45.125Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: crear-nuevo-rol
+locale: es
+legacySlug: crear-nuevo-rol
+subcategory: 1HSqkejwuYcQSMC400uY84
+---
+
+Los roles determinan el conjunto de recursos a los que un grupo de usuarios puede acceder en VTEX. Puedes gestionarlos a través del Admin VTEX, donde puedes definir los [recursos](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) y usuarios asociados a cada rol.
+
+Al crear un nuevo rol, puedes optar por utilizar uno [predefinido](https://help.vtex.com/es/tutorial/control-de-acceso--4rM3gyiWqtkim4Q8hOvLTC#predefinidos), diseñado por el equipo de VTEX para abordar escenarios operativos comunes, o registrar uno [personalizado](https://help.vtex.com/es/tutorial/control-de-acceso--4rM3gyiWqtkim4Q8hOvLTC#personalizados), definiendo los recursos específicos a los cuales los usuarios con ese rol tendrán acceso.
+
+Consulta a continuación los pasos a seguir para cada una de estas opciones:
+
+* [Rol predefinido](#rol-predefinido)
+* [Rol personalizado](#rol-personalizado)
+
+Recomendamos crear roles análogos a las estructuras jerárquicas de la tienda. De este modo, todos los colaboradores son responsables de la información a la que pueden acceder. Las buenas prácticas de gestión de los roles de usuario no solo mejoran la seguridad de las operaciones, sino que también fortalecen el compromiso de todas las partes involucradas en la protección de los datos sensibles de la tienda y tus clientes.
+
+<div class="alert alert-warning">
+  <p>El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas en caso de que se filtren las credenciales de inicio de sesión.</p>
+</div>
+
+## Rol predefinido
+
+Para empezar a utilizar un rol predefinido sigue las instrucciones a continuación:
+
+1. En la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil**, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Roles de usuario**.
+
+    Verás una lista con todos los roles registrados en la cuenta. Consulta más información sobre esta página accediendo al artículo [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+2. Haz clic en `+ Crear rol`.
+3. Haz clic en `Seleccionar rol` y en uno de los roles predefinidos que aparecen en el menú desplegable. No elijas la opción **Custom**, ya que está destinada a perfiles personalizados.
+
+    Verás los recursos que se incluyen en este rol, separados por producto.
+
+    Por ejemplo, el rol **Call center operator** contiene un recurso del producto _Catálogo_ que permite realizar operaciones en una tienda en nombre de un cliente, y un recurso de _OMS_ que permite consultar el status de un pedido:
+
+    ![Nuevo perfil de acceso](//images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/377d5de0c9b4af5667a4e8f10c171ae0/last_with_shadow_Wed_Apr__8_17_06_18_-03_2020.png)
+
+    Consulta más información sobre los roles predefinidos disponibles y los recursos asociados en [Roles de usuario predefinidos](https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy).
+4. Agrega usuarios administrativos al rol rellenando el email del usuario en **Agregar usuarios para este rol** y haciendo clic en `Agregar`.
+
+    ![Usuarios de perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/5d76addf0b92724ac97f66aa517a110d/usuarios-es.PNG)
+
+    Si el usuario no existe, se creará uno nuevo utilizando el email como nombre, es decir, el nombre y el email serán iguales.
+
+5. Haz clic en `Guardar`.
+
+## Rol personalizado
+
+Sigue las instrucciones a continuación para crear un rol personalizado que responda a las necesidades de acceso de un grupo de usuarios:
+
+1. En la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil**, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Roles de usuario**.
+
+    Verás una lista con todos los roles registrados en la cuenta. Consulta más información sobre esta página accediendo al artículo [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+2. Haz clic en `+ Crear rol`.
+3.  Para crear un rol personalizado, haz clic en ` Seleccionar rol` y después en la opción **Custom** del menú desplegable.
+4. Haz clic en el menú desplegable en **Seleccionar un producto** y, a continuación, haz clic en uno de los productos que aparece en la lista.
+
+    Verás una lista de todos los recursos disponibles para ese producto:
+
+    ![Configurando producto](//images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/0393d07c7e603da3fab9a589adf8e58c/configurar-produto-es.png)
+5. Marca los recursos a los que el rol tendrá acceso. Para más información sobre [Recursos, consulta la lista completa de License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3).
+6. Si deseas agregar recursos de otro producto, haz clic en el botón **Configurar otro producto** situado en la parte inferior de la lista de productos y recursos y repite los pasos 4 y 5.
+
+    Puedes agregar al rol recursos de tantos productos como necesites.
+
+7. Asigna un nombre para el rol personalizado en el campo **Nombre del rol**.
+
+  <div class="alert alert-warning">
+    <p>Es importante elegir nombres descriptivos para los roles, que indiquen claramente qué tipo de usuario debe tener ese acceso. Se recomienda especificar el cargo en la empresa o la función a desempeñar en la plataforma.</p>
+  </div>
+
+8. Agrega usuarios administrativos al rol rellenando el email del usuario en **Agregar usuarios para este rol** y haciendo clic en `Agregar`.
+
+      ![Usuarios de perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/5d76addf0b92724ac97f66aa517a110d/usuarios-es.PNG)
+
+      Si el usuario no existe, se creará uno nuevo utilizando el email como nombre, es decir, el nombre y el email serán iguales.
+9. Haz clic en `Guardar`.
+
+      Una vez creado, el nuevo rol aparecerá en la página [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
+
+## Más información
+
+* [Control de acceso](https://help.vtex.com/es/tutorial/control-de-acceso--4rM3gyiWqtkim4Q8hOvLTC)
+* [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [Recursos de License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3)
diff --git a/docs/tutorials/es/creating-service-for-a-sku.md b/docs/tutorials/es/creating-service-for-a-sku.md
index b894ee920..1a2cf2396 100644
--- a/docs/tutorials/es/creating-service-for-a-sku.md
+++ b/docs/tutorials/es/creating-service-for-a-sku.md
@@ -3,8 +3,8 @@ title: 'Crear servicio para un SKU'
 id: tutorials_252
 status: PUBLISHED
 createdAt: 2017-04-27T22:12:00.282Z
-updatedAt: 2023-05-04T13:15:14.224Z
-publishedAt: 2023-05-04T13:15:14.224Z
+updatedAt: 2024-03-04T22:36:04.117Z
+publishedAt: 2024-03-04T22:36:04.117Z
 firstPublishedAt: 2017-04-27T23:03:11.914Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -40,17 +40,10 @@ Para registrar un tipo de servicio, sigue los pasos a continuación:
 En esta sección debes registrar un nombre para tu tipo de servicio y configurar su comportamiento de acuerdo con las opciones que se indican a continuación.
 
 - **Nombre:** es el nombre del tipo de servicio.
-- **Exhibe en el producto:** opción para mostrar el tipo de servicio en la página del producto.
-- **Exhibe en el carrito:** opción para mostrar el tipo de servicio en el carrito.
-- **Exhibe en el servicio:** opción para mostrar el tipo de servicio en la página de servicios.
 - **Tarjeta de regalo:** opción para mostrar el tipo de servicio en la tarjeta de regalo.
 - **Servicio obligatorio:** opción que hace que el tipo de servicio sea obligatorio.
 - **Status:** opción que activa o desactiva el tipo de servicio.
-- **Anexos:** selección de los anexos que se añadirán al tipo de servicio. El anexo se utiliza para añadir una información personalizada al servicio. Para saber más, lee nuestro artículo ¿Qué es un Anexo?.
-
-<div class = "alert alert-warning">
-  <p>Para mostrar el servicio en la página del producto, debes activar la opción <b>Exhibe en el produto</b> y añadir el control <code><vtex.cmc:stockKeepingUnitService/></code> a la página del producto en el CMS. Para más información, lee nuestro artículo <a href ="https://help.vtex.com/es/tutorial/que-son-controles--6e2qsk9zu8IQuyEysKweag" >¿Qué son los controles?</a>.</p> 
-</div>
+- **Anexos:** selección de los anexos que se añadirán al tipo de servicio. El anexo se utiliza para añadir una información personalizada al servicio. Para saber más, lee nuestro artículo [¿Qué es un Anexo?](https://help.vtex.com/es/tutorial/que-es-un-anexo--aGICk0RVbqKg6GYmQcWUm).
 
 ## Crear un valor de servicio y asociarlo a un tipo de servicio
 Después de registrar el tipo de servicio, debes asignarle un valor. Para registrar el valor de un tipo de servicio, sigue los pasos a continuación:
@@ -86,7 +79,7 @@ Para vincular un servicio a un SKU, sigue los pasos a continuación:
   <p>El tamaño del archivo de la plantilla no debe superar los 4Mb (4096KB).</p>
 </div>
 8. Haz clic en la barra que se encuentra junto al botón `Select`, que se muestra a continuación.
-  ![Anexos - ES](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/844c4cb0282e3b4e32c9b494906b0597/sku-services-ES.png)
+  ![Anexos - ES](//images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/844c4cb0282e3b4e32c9b494906b0597/sku-services-ES.png)
 9. Selecciona la plantilla CSV actualizada.
 10. Haz clic en `Vincular valores de servicios a SKU` para finalizar.
 
diff --git a/docs/tutorials/es/creating-subaccount-multi-store-multi-domain.md b/docs/tutorials/es/creating-subaccount-multi-store-multi-domain.md
new file mode 100644
index 000000000..f716b4f66
--- /dev/null
+++ b/docs/tutorials/es/creating-subaccount-multi-store-multi-domain.md
@@ -0,0 +1,65 @@
+---
+title: 'Crear subconta / multitienda / multidominio '
+id: tutorials_510
+status: PUBLISHED
+createdAt: 2017-04-27T22:03:17.733Z
+updatedAt: 2024-01-18T17:56:47.931Z
+publishedAt: 2024-01-18T17:56:47.931Z
+firstPublishedAt: 2017-04-27T23:03:27.832Z
+contentType: tutorial
+productTeam: Others
+author: authors_84
+slug: crear-subconta-multitienda-multidominio
+locale: es
+legacySlug: como-crear-multitienda-multidominio
+subcategory: yMp6sKDiJEi66CGAIQ4ma
+---
+
+Subconta, multitienda o multidominio es una segunda tienda administrada dentro de un mismo panel administrativo VTEX. Esta feature generalmente se utiliza cuando la tienda tiene otras marcas pero existe una similitud de logística y medios de pago o cuando la tienda necesita otro ambiente, por ejemplo para las ventas de B2B.
+
+La creación de una multitienda es gratuita para el comerciante. Sin embargo, si necesita [contratar una póliza comercial adicional](https://help.vtex.com/es/tutorial/contratacion-de-politicas-comerciales-adicionales--61vuFOw4yGh6nwSmkLJL1X), se aplicarán costes adicionales.
+
+En un ambiente multidominio es posible definir layouts distintos (además de productos y/o precios) para cada tienda, variando de acuerdo con el dominio accedido. Ejemplo: accountname.com, b2baccountname.com.br, etc.
+
+## Configurar nueva tienda en Gestión de la cuenta
+
+El primer paso para configurar la multitienda es configurar una nueva tienda en la página de detalles de la cuenta. Aprende cómo hacerlo con el artículo de [Gestión de cuentas](https://help.vtex.com/en/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq).
+
+Ten en cuenta que también debes especificar el dominio de tu nueva tienda. Obtén más información con el artículo [Configuración del dominio de tu tienda](https://help.vtex.com/tutorial/configuring-domains-in-account-management--tutorials_2450).
+
+## Configurar website en el CMS - Portal Legado
+
+La configuración en el CMS - Portal Legado realmente crea el ambiente para que los clientes pueden tener acceso. El paso a paso siguiente muestra cómo crear un website ya copiando la estructura de carpetas de su website principal para facilitar la creación de su layout. Sin embargo, esta configuración también se puede hacer creando un website nuevo.
+
+1. Acceda al módulo **Storefront > Layout**.
+2. Haga clic en **CMS**.
+3. Haga clic en **Sites and channels**.
+4. Haga clic en su website principal.
+5. Haga clic en el botón `Copy Website`.
+6. Haga clic de nuevo en **Sites and channels** en la columna lateral.
+7. Haga clic en el website creado.
+8. Cambie el nombre.
+9. Haga clic en el botón `Save Website`.
+10. En la misma pantalla, haga clic en el botón `Agregar`.
+11. Rellene el campo **Store name from License Manager** con el valor de la tienda creada en el paso anterior en __Gestión de la cuenta__.
+12. Rellene el campo **Available sales policies** seleccionando las políticas comerciales que se asociarán a esta tienda.
+13. Haga clic en el botón `Save Binding`.
+14. Haga clic en el botón `Save Website`.
+
+Se atente a la ordenación de sus políticas comerciales. Ellas siempre deben ser ordenadas de acuerdo con su uso en websites, es decir, primero las políticas comerciales que son usadas por websites (principal, b2b, etc.) y luego las políticas comerciales que no están asociadas a ningún website (políticas comerciales de marketplace, por ejemplo). 
+
+Esto es porque si existe una política comercial no asociada a ningún website, ella está disponible para todos ellos. Y en caso de que venga antes de la política comercial asociada al website, éste asumirá la política comercial incorrecta.
+
+Para conocer más detalles sobre la relación entre websites y políticas comerciales, [accede a nuestro artículo](/es/faq/como-funciona-la-relacion-entre-sitios-web-y-politicas-comerciales).
+
+### Editar el diccionario
+
+También es posible definir variables específicas para cada website mediante el diccionario. Para ello, dentro del website, haga clic en **diccionario**.
+
+## Eliminar subcuenta / multitienda / multidominio
+
+Para eliminar una multitienda existente, siga los pasos descritos en la [sección Eliminar tienda de la guía Gestión de la cuenta](https://help.vtex.com/es/tutorial/gestion-de-la-cuenta--2vhUVOKfCaswqLguT2F9xq#eliminar-tienda). El nombre de la subcuenta eliminada no puede volver a utilizarse.
+
+## Más información
+
+- [Elegir entre arquitectura multitienda o entorno adicional](https://help.vtex.com/es/tutorial/elegir-entre-arquitectura-multitienda-o-entorno-adicional--4HRNpa1OCKZ5YzP8yiilBL)
diff --git a/docs/tutorials/es/creating-surchargestaxes.md b/docs/tutorials/es/creating-surchargestaxes.md
index e2fdd3fee..89f5744f8 100644
--- a/docs/tutorials/es/creating-surchargestaxes.md
+++ b/docs/tutorials/es/creating-surchargestaxes.md
@@ -3,8 +3,8 @@ title: 'Crear tasa/impuesto'
 id: tutorials_321
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:49.745Z
-updatedAt: 2023-03-31T16:53:05.461Z
-publishedAt: 2023-03-31T16:53:05.461Z
+updatedAt: 2023-10-26T13:20:22.531Z
+publishedAt: 2023-10-26T13:20:22.531Z
 firstPublishedAt: 2017-04-27T23:03:14.603Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -30,31 +30,32 @@ El impuesto se aplica conforme al registro que hará el vendedor. A continuaci
 
 ### Cuáles son los datos generales de ese impuesto?
 
-- **Nombre**: Nombre del impuesto.
-- **Estatus**: Impuesto activo o inactivo.
-- **Descripción**: Descripción interna del impuesto. El objetivo de este campo es si se va a utilizar para la comunicación interna en su tienda con el fin de dejar claro si el impuesto debe de ser una regla especial, por ejemplo.
-- **Validez**: Fecha y hora del inicio y fin del impuesto. Una fecha puede ser usada a tiempo real / o futuro, por lo que el impuesto comienza a ser aplicado en el sitio. Si se ha configurado de esta manera, el impuesto tendrá el estado de programar hasta que se alcancen la fecha y la hora. Mientras que el impuesto es válido, tendrá la condición de activo y al final de la fecha y hora definida, el estado se cambia a inactivo automáticamente.
+- **Nombre**: nombre del impuesto.
+- **Estatus**: impuesto activo o inactivo.
+- **Descripción**: descripción interna del impuesto. El objetivo de este campo es si se va a utilizar para la comunicación interna en su tienda con el fin de dejar claro si el impuesto debe de ser una regla especial, por ejemplo.
+- **Validez**: fecha y hora del inicio y fin del impuesto. Una fecha puede ser usada a tiempo real / o futuro, por lo que el impuesto comienza a ser aplicado en el sitio. Si se ha configurado de esta manera, el impuesto tendrá el estado de programar hasta que se alcancen la fecha y la hora. Mientras que el impuesto es válido, tendrá la condición de activo y al final de la fecha y hora definida, el estado se cambia a inactivo automáticamente.
 - **Qué tipo y importe del Tributo?**:
-  - **Porcentaje de tributo**: Porcentual sobre el valor del producto que será añadido al valor.
-  - **Tributo basado en fórmula**: El impuesto seguirá el cálculo indicado en el campo.
-  - **Tributo procentual de envío**: Acrecimiento porcentual sobre el valor del flete.
-- **Política Comercial**: Seleccione las políticas comerciales donde el impuesto será aplicado.
+  - **Porcentaje de tributo**: porcentual sobre el valor del producto que será añadido al valor.
+  - **Tributo basado en fórmula**: el impuesto seguirá el cálculo indicado en el campo.
+  - **Tributo procentual de envío**: acrecimiento porcentual sobre el valor del flete.
+  - **Impuesto nominal**: cargo adicional con valor predefinido.
+- **Política comercial**: seleccione las políticas comerciales donde el impuesto será aplicado.
 
 ### En qué artículos este impuesto será aplicado?
 
-- **Categorias, Marcas, Colecciones y Productos**: Debe de cumplir con todas las condiciones registradas. Ej.: Si se registra una categoría y marca, el producto debe cumplir estas dos condiciones.
+- **Categorias, Marcas, Colecciones y Productos**: debe de cumplir con todas las condiciones registradas. Ej.: Si se registra una categoría y marca, el producto debe cumplir estas dos condiciones.
 
 ### Cuáles son las condiciones para que el impuesto sea válido?
 
-- **Valor acumulado en compras**: El impuesto se aplicará si se completa el valor con las compras realizadas por el cliente.
-- **Marketing Tags**: Campo utilizado para restringir la activación de la campaña si la compra es realizada por el Sistema de Recurrición de VTEX.
-- **Afiliados**: Identificador de pedidos del marketplace
-- **Cluster de clientes**: El impuestos se aplicará si el cliente se ha registrado en el cluster seleccionado.
-- **El códiogo postal de entrega debe**: El impuesto será aplicado en el caso de que CEP atienda a la regla configurada.
-- **Tipo de carga**: El impuesto se aplicará si el tipo de carga es la misma que la registrada
+- **Valor acumulado en compras**: el impuesto se aplicará si se completa el valor con las compras realizadas por el cliente.
+- **Marketing Tags**: campo utilizado para restringir la activación de la campaña si la compra es realizada por el sistema de recurrición de VTEX.
+- **Afiliados**: identificador de pedidos del marketplace
+- **Cluster de clientes**: el impuestos se aplicará si el cliente se ha registrado en el cluster seleccionado.
+- **El códiogo postal de entrega debe**: el impuesto será aplicado en el caso de que CEP atienda a la regla configurada.
+- **Tipo de carga**: el impuesto se aplicará si el tipo de carga es la misma que la registrada
 
 ## Programación
 
 La planificación de un impuesto se produce cuando es creado o modificado con el tiempo y la fecha de validación más adelante del actual. Visualmente se pueden identificar estos impuestos en la página principal del módulo de Tsas y Promociones a través de una franja naranja en la esquina superior derecha de la lista de precios con la palabra programado. A continuación se muestra un ejemplo de cómo se identifica el impuesto cuando está programado.
 
-![agendamento.es](https://images.ctfassets.net/alneenqid6w5/2DPKlUdsr38TTIwc3e9GH5/31b3319951c14c8faa6ab3558cebf19b/agendamento.es.png)
+![agendamento.es](//images.ctfassets.net/alneenqid6w5/2DPKlUdsr38TTIwc3e9GH5/31b3319951c14c8faa6ab3558cebf19b/agendamento.es.png)
diff --git a/docs/tutorials/es/creating-synonyms.md b/docs/tutorials/es/creating-synonyms.md
new file mode 100644
index 000000000..706b6ebce
--- /dev/null
+++ b/docs/tutorials/es/creating-synonyms.md
@@ -0,0 +1,96 @@
+---
+title: 'Crear sinónimos'
+id: 5IfjhvjxNAvJGEWNn0AhOA
+status: PUBLISHED
+createdAt: 2024-06-27T16:36:30.904Z
+updatedAt: 2024-06-27T16:39:00.981Z
+publishedAt: 2024-06-27T16:39:00.981Z
+firstPublishedAt: 2024-06-27T16:37:25.800Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: crear-sinonimos
+locale: es
+legacySlug: configurar-sinonimos
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+<div class = "alert alert-info"> Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ">Sinónimos</a> en lugar de <a href="https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palabras sustitutas</a> para asociar palabras con productos, ya que los sinónimos permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>. </div>
+
+Hay dos formas de configurar sinónimos en VTEX Admin: [individualmente](#crear-sinonimos-individualmente) o [importando una hoja de cálculo en formato CSV](#). Si necesita registrar sinónimos en bloque, le recomendamos que utilice la hoja de cálculo. Consulte las instrucciones para cada método de configuración en las secciones siguientes.
+
+La configuración de sinónimos funciona de forma recursiva. Esto significa que cuando agrega un segundo sinónimo a uno existente, también se convertirá en sinónimo del primero.
+
+<div class="alert alert-info" role="alert">
+<p>Los sinónimos no deben ser usados para resolver errores de ortografía, plural y singular o incluso pronombres, artículos y preposiciones en los términos investigados. En todos estos puntos, VTEX Intelligent Search es capaz de interpretar, aprender y resolver automáticamente por medio de algoritmos.
+</p>
+</div>
+
+## Crear sinónimos individualmente
+
+Siga el proceso paso a paso para configurar sinónimos individualmente en VTEX Admin:
+
+1. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
+2. En **Intelligent Search**, haga clic en __Sinónimos__. 
+2. Haga clic en `Crear sinónimo`.
+3. Rellene los campos referentes al sinónimo:
+   - __Tipo:__ define el tipo de sinónimo. Consulte [Tipos de sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) para obtener más información.
+   - __Términos:__ palabras o expresiones que se definirán como sinónimos. Debe pulsar `Enter` después de cada término para insertar otro término.
+   - **Idiomas:** idiomas en los que se aplicará el sinónimo. Campo solo disponible para tiendas que utilizan [configuración multidioma (beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+   - __Status:__ define si el sinónimo estará activo o inactivo.
+4. Para terminar, haga clic en `Publicar`.
+
+La alteración puede tardar hasta dos horas en aplicarse.
+
+<div class="alert alert-info">
+<p>Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos">VTEX Intelligent Search: configuración Multidioma (Beta)</a> para saber más.</p>
+</div>
+
+## Importar CSV
+
+Si existen muchos sinónimos para registrar, puedes hacer un archivo .csv y luego importarlo en el Admin.
+
+Para importar la hoja de cálculo, siga los pasos que se indican a continuación:
+
+1. Cree un archivo CSV en el formato indicado en [Plantilla de sinónimos](#plantilla-de-sinonimos).
+2. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
+3. En **Intelligent Search**, haga clic en __Sinónimos__. 
+4. Haga clic en <i class="fas fa-download"></i> `Importar`.
+5. Arrastre el archivo CSV al área delimitada o haga clic en `selecciona un archivo` para seleccionar el archivo de su dispositivo.
+6. Haga clic en `Importar`.
+
+## Plantilla de sinónimos
+
+El fichero debe contener el siguiente formato, según los [tipos de sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) elegidos:
+
+- __Unidireccional:__ `{términos separados por una coma};{término equivalente};{status}`
+
+   __Ejemplos:__
+
+    - `smartphone;iphone;true`: al buscar por `smartphone`, se mostrarán los resultados para `iphone`. Sin embargo, al buscar por `iphone`, los resultados para `smartphone` no se mostrarán.
+    - `tablet;ipad;true`: al buscar por `tablet`, se mostrarán los resultados para `ipad`. Sin embargo, al buscar por `ipad`, los resultados para `tablet` no se mostrarán.
+
+ - __Bidireccional:__ `{términos separados por una coma};{status}`
+
+    __Ejemplos:__
+
+    - `tv,televisión,televisor;true`: al buscar por cualquiera de los términos, el producto que contenga uno de estos será devuelto.
+    - `monitor,pantalla,display;true`: al buscar por cualquiera de los términos, el producto que contenga uno de estos será devuelto.
+
+#### Tiendas multidioma (Beta)
+
+Tiendas que utilizan configuración multidioma (beta) deben seguir la siguiente plantilla para importar Sinónimos para idiomas específicos.
+
+- __Unidireccional__: `{términos separados por una coma};{término equivalente};{status};{locales separados por coma}`.
+
+   __Ejemplo:__
+   - `smartphone;iphone;true;en-GB`: al buscar smartphone en la tienda en el idioma inglés (`locale en-GB`), se mostrará los resultados de iphone.  Sin embargo, al buscar iphone, no aparecerán los resultados de smartphone.
+
+- __Bidireccional__: `{términos separados por una coma};{status};{locales separados por coma}`.
+
+   __Ejemplo:__
+   - `tv,smart tv;true;en-GB`: al buscar cualquiera de estos términos en la tienda en el idioma inglés (`locale en-GB`), se mostrará cualquier producto que contenga uno de esos términos en los resultados de búsqueda.
+
+<div class="alert alert-warning">
+  <p> Si el archivo .csv importado no contiene el <code>locale</code>, el sinónimo será válido para todos los idiomas disponibles en la tienda. </p>
+</div>
diff --git a/docs/tutorials/es/creating-trigger-in-master-data.md b/docs/tutorials/es/creating-trigger-in-master-data.md
index 4d34c5e37..daddb1c6a 100644
--- a/docs/tutorials/es/creating-trigger-in-master-data.md
+++ b/docs/tutorials/es/creating-trigger-in-master-data.md
@@ -3,8 +3,8 @@ title: 'Crear trigger en Master Data v1'
 id: tutorials_1270
 status: PUBLISHED
 createdAt: 2017-04-27T21:56:49.666Z
-updatedAt: 2022-12-14T18:27:30.828Z
-publishedAt: 2022-12-14T18:27:30.828Z
+updatedAt: 2024-06-27T13:01:58.637Z
+publishedAt: 2024-06-27T13:01:58.637Z
 firstPublishedAt: 2017-04-27T23:03:50.015Z
 contentType: tutorial
 productTeam: Master Data
@@ -16,144 +16,157 @@ subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
 <div class="alert alert-info">
-Este artículo hace referencia al Master Data v1. Si desea utilizar el Master Data v2, vea los pasos de <a href="https://help.vtex.com/es/tutorial/configurar-triggers--54eVOFGhS0EWyAUieoqKWo">este artículo</a>.
+  <p>Este artículo hace referencia a Master Data v1. Si deseas utilizar Master Data v2, consulta los pasos de la guía <a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2">Setting up triggers in Master Data v2</a>.</p>
 </div>
 
-Conceptualmente, **trigger** es un recurso de programación que ejecuta determinada acción cada vez que se produce un evento asociado. En el Master Data, un trigger es la configuración de uno o más disparos (eventos) cuando ocurre una determinada situación. Esta situación se configura en función de diversas variables.
+Conceptualmente, un trigger es un recurso de programación que ejecuta una acción específica siempre que se produce un evento asociado. En Master Data, un trigger es la configuración de uno o varios eventos disparadores que se activan cuando se produce una determinada situación, en función de diversas variables.
 
-Esto permite varias automatizaciones y control de datos, aumentando la eficiencia de su gestión de datos. Es decir, de modo simple, trigger es una funcionalidad que permite la programación de acciones en caso de que ocurra una acción de disparo.
+La implementación de triggers posibilita diversas automatizaciones y optimiza el control de datos, lo cual se traduce directamente en una mayor eficiencia en tu gestión de información. En resumen, un trigger es una funcionalidad que permite programar acciones para que se ejecuten automáticamente cuando se cumplan condiciones predefinidas por eventos disparadores.
 
-1. Una entidad de datos contiene los datos de todas sus tiendas físicas
-2. Se incluye un nuevo registro en esta entidad
-3. Un trigger configurado envía a todos los clientes un correo electrónico contándoles la novedad
+Por ejemplo:
 
-Imagine que se hacen programaciones de determinadas acciones para, cuando se cumpla una condición, realizar estas acciones. Entonces, cualquier información registrada en el MasterData puede ser una acción que dispare otras innumerables acciones, de acuerdo con lo que se desee. El trigger posee algunas características importantes, descritas a continuación:
+1. Una entidad de datos contiene los datos de todas tus tiendas físicas.
+2. Se inserta un nuevo registro en esa entidad.
+3. Un trigger configurado envía a todos los clientes un email informando sobre la actualización.
+
+Los triggers permiten programar acciones que se llevarán a cabo cuando se cumplan determinadas condiciones. Cualquier información registrada en Master Data puede activar otras muchas acciones, según se desee.
+
+Las principales características de los triggers son las siguientes:
 
 - Se asocian a una entidad de datos.
-- Se llaman automáticamente.
-- No pueden llamarse directamente.
-- Dispara diversas acciones.
-- Permite la creación de escenarios de recursividad.
-- Puede impactar en la manipulación de datos de la entidad, debido a la característica anterior.
+- Se activan automáticamente.
+- No pueden ser llamados directamente.
+- Activan diversas acciones.
+- Permiten crear escenarios de recursividad.
+- Pueden impactar el manejo de datos de la entidad debido a la característica anterior.
 
-La configuración se da por 4 partes. Cada una de estas se detalla a continuación:
+## Estructura del trigger
 
-1. Configuración de la acción que disparará el trigger. Para esto, decida cuál acción debe ser seguida por otra. Y esta configuración se separa en dos partes: la **condición** del trigger y los **filtros adicionales**. La condición es la acción que dispara el trigger, un registro por ejemplo, mientras que los filtros son las especificaciones que aquella acción debe cumplir para que la acción de respuesta se ejecute, como hacerse el registro por el formulario de newsletter y no por la finalización de compra. En este caso, la condición del trigger sería: "siempre que se ingrese  un registro" y, en los filtros adicionales, exista un campo "origen" filtrando por "newsletter". Así, cada vez que se realice un nuevo registro, el trigger verificaría si el cliente se registró por el newsletter y, solamente en este caso, realizaría la acción configurada para este fin.
+Antes de [crear un trigger](#configurar-trigger), es necesario comprender que su configuración consta de cuatro partes, que se explican a continuación.
 
-2. Tiempo para el disparo. Es posible configurar varios envíos separados por un intervalo de tiempo. O incluso programar el disparo de acuerdo con la fecha de otro campo. Ejemplo: existe el campo "Fecha de Vencimiento" en el registro de una entidad "Producto" y se desea que, 1 mes antes de esta fecha, se envíe una notificación por API a otro sistema. En este caso, el tiempo de disparo será "Fecha de Vencimiento" menos 1 mes.
+![trigger](//images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/4dee23f7b89e1ce4acd9479dcd0babd9/trigger-es.png)
 
-Acciones que se ejecutarán si un registro cumple la condición del trigger y los filtros. Aquí, se configuran todas las acciones que se ejecutarán cuando el registro que cumplió las condiciones también haya cumplido con los filtros y haya llegado a la fecha establecida en la programación. Estas acciones pueden ser envío de correo electrónico, de comentario, cambiar otro campo y otras posibilidades, detalladas más adelante. Ejemplo real: 
-- **Condición**: el atributo Checkout se altera.
-- **Filtro adicional**: el Checkout es igual a Finalizado.
-- **Acciones en caso positivo**: alterar el campo Bonus (tipo score), colocando el tag bonus con valor 10 y validez 30 días.
+### Acción que activa el trigger
 
-En este caso, es un escenario donde se busca hacer la puntuación de un campo a cada nueva compra del cliente. Es decir, cada vez que el cliente finaliza un pedido, se suman 10 puntos en el campo "Bonus". Suponiendo que se conceda el bonus  cuando este campo sume 40 puntos, existe la necesidad de otro trigger que verifique ese bonus y conceda la promoción. Para esto, el segundo trigger va a asociar al cliente a un clúster que ya está configurado en una promoción. Vea la configuración del segundo trigger:
+Lo primero es decidir qué acción debe impulsar la siguiente acción. Esta configuración se divide en dos partes:
 
-- **Condición**: el atributo Bonus se altera
-- **Filtro adicional**: el Bonus es mayor o igual a 40
-- **Acciones en caso positivo**: alterar el campo ClusterBonus para verdadero.
+- **Regla**: acción que activa el trigger. Ejemplo: un nuevo registro en una tienda.
+- **Filtros adicionales**: condiciones que la acción debe cumplir para que se ejecute la acción de respuesta, como que el registro se realice a través del formulario de la newsletter y no mediante la finalización de la compra. 
 
-Acciones que se ejecutarán si un registro cumple la condición del trigger pero no cumple los filtros. Esta opción es exactamente lo contrario de la opción anterior. Solamente se ejecutará si el registro que pasó por la condición del trigger **no** cumple los filtros adicionales. Ejemplo real:
-- **Condición**: se ingresa un nuevo registro en Registro Extendido
-- **Filtro adicional**: el Sexo es igual a femenino
-- **Acciones en caso positivo**: enviar un correo electrónico con ofertas del departamento femenino.
-- **Acciones en caso negativo**: enviar un correo electrónico con ofertas del departamento masculino.
+En este ejemplo, la condición del trigger sería **Siempre que se crea un registro** y, en los filtros adicionales, debería haber un campo "origen" filtrando por "newsletter". De este modo, cada vez que se produjera un nuevo registro, el trigger comprobaría si el cliente se registró vía newsletter y, solo en ese caso, realizaría la acción configurada.
 
-## Cómo configurar
+### Tiempo para activar el trigger
 
-1. Ingrese al DynamicStorage (https://*SUTIENDA*.ds.vtexcrm.com.br).
-2. Haga clic en la pestaña **Trigger**.
-3. Haga clic en el botón **Nuevo**.
-4. Introduzca el Nombre del trigger.
-5. Ingrese un correo electrónico para que sea notificado si ocurre algún error en la ejecución.
-6. Seleccione la [entidad de datos](/es/tutorial/entidades-de-datos-creacion-y-mantenimiento/ "entidade de dados") que disparará la acción del trigger.
-7. Después de seleccionar la entidad de datos, surgirán los demás campos de configuración.
-8. Seleccione un status para el trigger.
-9. Siga en la configuración de cada una de las pestañas como se indica a continuación.
+Pueden configurarse múltiples envíos separados por un rango de tiempo, o incluso programar el trigger en función de la fecha de otro campo. Ejemplo: hay un campo **Fecha de vencimiento** en el registro de una entidad **Producto** y deseas que un mes antes de esta fecha se envíe una notificación mediante API a otro sistema. En este caso, el tiempo de activación será: **Fecha de vencimiento** menos 1 mes.
 
-### Condiciones 
+### Acciones que se realizarán si un registro cumple la regla del trigger y los filtros
 
-Aquí, se configuran las condiciones que van a disparar el (los) evento (s) configurado (s) en el trigger. La forma de hacer esta configuración se describe de la siguiente manera:
+Aquí debes configurar todas las acciones que serán ejecutadas cuando el registro cumpla tanto las condiciones establecidas como los filtros. Estas acciones pueden incluir el envío de email, la asignación de una puntuación en un campo de tipo Score2, entre otras posibilidades detalladas a continuación.
 
-#### Condición del trigger
+Ejemplo: un escenario en el que se desea puntuar un campo con cada nuevo pedido del cliente. Cada vez que el cliente finaliza un pedido, se suman 10 puntos al valor actual del campo **Bonus**.
 
-- **Si el valor de un atributo se altera**: significa que, cuando el valor del campo que se informe abajo se altera, en cualquier registro, se disparará este trigger.
-Se debe informar el campo que se filtrará. Ej.: cuando se altera el campo "correo electrónico", se debe disparar el trigger  &#8211; informe campo "correo electrónico" en el campo "Informe el atributo".
-- **Si un evento se levanta**: este tipo fue descontinuado.
-- **Un registro se altera**: significa que, cuando un registro se altera, en cualquier campo, se disparará este trigger.
-- **Un registro se comenta**: significa que, cuando un registro se comenta, se disparará este trigger.
-- **Un registro se ingresa**: significa que, cuando un registro se ingresa, se disparará este trigger.
-- **Un registro se elimina**: significa que, cuando un registro se elimina, se disparará este trigger.
+- **Regla: cuando se modifica el atributo Checkout.
+- **Filtro adicional**: Checkout igual a Finalizado.
+- **Acciones en caso positivo**: modificar el campo Bonus (tipo Score2), configurando la tag de bonus con valor 10 y validez de 30 días.
 
-#### Filtro adicional
+### Acciones que se realizarán si un registro cumple la regla del trigger pero no los filtros
 
-**Agregar grupo**: crea grupos que contienen filtros. Cada uno de estos grupos puede relacionarse con los demás, formando capas más complejas de filtro.
-![relacionGrupos](//images.contentful.com/alneenqid6w5/6n2ipjsapUYyG8quIucIke/1b789ceed1f6ea993096f0d3c857b114/relacaoGrupos.png)
-**Incluir filtro**: es posible crearlo dentro del último grupo creado o sin la necesidad de grupos. Un filtro siempre interactúa con los demás, en el modelo de conjunto, siendo las opciones "Y" u "O" para cada uno de estos.
-Se debe seleccionar cuáles son los campos y cuáles son los valores aceptados o no para que se dispare el trigger.
-![filtroTrigger](//images.contentful.com/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/cf6c5ef321a8d39e16a09d30c2ca1245/filtroTrigger.png)
+En esta configuración, debes definir acciones que se realizarán únicamente si el registro que cumplió la condición del trigger **no** cumple la de los filtros adicionales. Ejemplo:
 
-<div class="alert alert-info">
-Master Data v1 no permite la configuración de reintentos, a diferencia de Master Data v2.
-</div>
+- **Regla: cuando se crea un nuevo campo de registro personalizado.
+- **Filtro adicional**: género igual a femenino.
+- **Acciones si es positivo**: enviar un email con ofertas de la sección femenina.
+- **Acciones si es negativo**: enviar un email con ofertas de la sección masculina.
 
-### Programación 
+## Configurar trigger
 
-Aquí, se configura cuándo el trigger debe dispararse. Puede ser inmediatamente, con la opción "Ejecutar lo más rápido posible", programado con una fecha en el calendario con "Programar para una fecha específica" o un valor en el futuro, partiendo de la fecha actual o de la fecha de algún campo de fecha, pudiendo utilizar minutos, horas, días, mes y años con la opción "Programar ejecución para una fecha dinámica".
+Sigue los pasos a continuación para crear un trigger en Master Data v1:
 
-### Acciones en caso positivo
+1. Accede a Master Data en `https://{nombredelacuenta}.ds.vtexcrm.com.br/`, sustituyendo `{nombredelacuenta}` por el nombre de tu cuenta VTEX.
+2. Haz clic en la pestaña **Trigger**.
+3. Haz clic en el botón `Agregar`.
+4. Ingresa el **Nombre** del trigger.
+5. Selecciona la [entidad de datos](https://help.vtex.com/es/tutorial/entidad-de-datos--tutorials_1265/ "entidad de datos") que activará la acción del trigger.
 
-Se configurarán los eventos que se dispararán si el registro que desencadenó el evento pasa por todos los filtros adicionales.
+   Una vez seleccionada la entidad de datos se mostrarán los demás campos de configuración.
+7. Selecciona un status para el trigger, que puede ser **Activado** o **Desactivado**.
+8. Realiza los ajustes en cada una de las pestañas, según las secciones a continuación:
 
-#### Alterar un atributo
+    - [Reglas](#reglas)
+    - [Programar](#programar)
+    - [Si es positivo](#si-es-positivo)
+    - [Si es negativo](#si-es-negativo)
 
-Esta acción altera un campo del registro que disparó el trigger. Se debe informar cuál campo (atributo) debe alterarse, así como cuál fórmula debe utilizarse. El campo "Expresiones dinámicas" muestra cuáles son los valores que se deben ingresar en la fórmula si desea utilizar valores contenidos en campos del registro o de los registros relacionados (si tuviera). Se entiende como fórmula un código en C# que devuelva algún valor del mismo tipo definido en la entidad de datos para el campo.
-![fórmula](//images.contentful.com/alneenqid6w5/F3qRfRkScKWAYoCas4GCe/36f27cb6e71425b80340e1221251d3d2/f_C3_B3rmula-1.png)
-El botón validar va a compilar el código en el campo fórmula para verificar si es o no válido y mostrará cuál valor devolverá para el campo.  
-![validacionFormula](//images.contentful.com/alneenqid6w5/3Fjh4Q1hVCqkY0yAmMSmOM/67564a371055792fd5c0f40efed7670b/validacaoFormula.png)
+9. Haz clic en `Guardar`.   
 
-#### Incluir un comentario
+### Reglas
 
-Incluye un comentario en el registro que disparó el trigger. Se debe escribir el comentario que se ingresará.
+Aquí debes definir las condiciones que activarán el evento o eventos configurados en el trigger.
 
-#### Enviar correo electrónico
+#### Reglas de activación
 
-Envía un correo electrónico a destinatarios dinámicos (contenidos en el registro) o fijos. El correo electrónico que se enviará es todo personalizado, pudiendo ser un texto, HTML o incluso el contenido de una URL. Puede ingresar adjuntos, y el campo "tag válidas" muestra cómo ingresar valores de campos del registro.
+- **Se modifica el valor de un atributo**: cuando el valor del campo a continuación se modifica en cualquier registro, se activará el trigger.
 
-![email](//images.contentful.com/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/89d9d75e4cfdb2fd539dece5a542f8ce/email.png)
+   En la opción **Campo**, selecciona el campo que deseas utilizar. Si deseas activar el trigger cuando se modifique el campo **Email**, selecciona dicho campo.
 
-#### Puntuar campo Score
+- **Se modifica un atributo de filtro**: cuando se modifica un atributo de filtro, se activa el trigger.
+- **Se modifica un registro**: cuando se modifica un registro, en cualquier campo, se activa el trigger.
+- **Se crea un registro**: cuando se inserta un registro, se activa el trigger.
+- **Se elimina un registro**: cuando se elimina un registro, se activa el trigger.
 
-Un campo score es un tipo especial de dato que guarda 3 informaciones: clave, puntos y validez. Usted puede definir un valor para cada uno de estos puntos y guardarlo en un campo de tipo Score.
+#### Filtro adicional
 
-#### Generar un QRCode
+- **Agregar grupo**: crea grupos que contienen filtros. Cada uno de estos grupos puede relacionarse con los demás, formando capas de filtro más complejas.
+- **Agregar filtro**: es posible crear un filtro dentro del último grupo creado o independientemente de los grupos. Un filtro siempre interactúa con otros filtros según la configuración establecida, utilizando las opciones "y" y "o" para cada uno de ellos.
 
-Genera un QRCode con el contenido ingresado. Este QRCode debe insertarse en algún campo del tipo "file" del registro.
+   Selecciona los campos y los valores que activarán o no el trigger.
 
-Se pueden configurar más de una acción; sin embargo, se recomienda hasta 3 acciones por trigger. Configure las acciones de acuerdo con la prioridad, pues si hay algún error en la configuración de un evento, todos los eventos que le siguen no se dispararán.
+   ![filters-es](//images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/ce8019b7300c8c857ac71ffb4f0091c9/filters-es.png)
 
-#### Enviar request HTTP
+<div class="alert alert-info">
+  <p>Master Data v1 no permite la configuración de reintentos de trigger, a diferencia de Master Data v2.</p>
+</div>
 
-Envía un request HTTP con la posibilidad de guardar la información de la respuesta en Master Data.
+### Programar
+
+Esta pestaña permite configurar cuándo debe dispararse el trigger:
+
+- **Ejecutar lo antes posible:** inmediatamente.
+- **Programar en una fecha específica:** programar fecha y hora en el calendario.
+- **Programar en una fecha dinámica:** establecer una fecha futura a partir de la fecha actual o de un campo de fecha, permitiendo ajustar minutos, horas, días, meses y años.
 
-Rellena la sección **Request data** con la información del request que se enviará. En la sección **Response action**, puedes indicar cómo se debe guardar la información de la respuesta en Master Data.
+### Si es positivo
 
-![Master Data v1 send http request screenshot](https://images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/638a4b496b682354af486971ab6418c3/mdv1_trigger_http_request.PNG)
+En esta pestaña debes configurar los eventos que deben dispararse si el registro que activó el evento cumple todos los filtros adicionales.
+
+#### Enviar un email
+
+Envía un email a destinatarios dinámicos (contenidos en el registro) o estáticos. El email puede personalizarse y estar en formato de texto, HTML o incluir el contenido de una URL. Se pueden ingresar archivos adjuntos y el campo **Tags válidas** muestra cómo ingresar valores de campos del registro.
+
+![send-email-es](//images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/e413677641a756923fa9fd6e477002e2/send-email-es.png)
+
+#### Enviar un email utilizando una plantilla de VTEX Message Center
+
+Envía un email utilizando una plantilla existente en Message Center.
+
+#### Agregar puntuación al campo Score2
+
+Un campo de tipo Score2 es un tipo especial de dato que almacena 3 informaciones: clave, puntos y validez. Puedes definir un valor para cada uno de estos puntos y guardarlo en un campo de este tipo.
+
+#### Enviar un request HTTP
+
+Envía un request HTTP con la posibilidad de guardar la información de la respuesta en Master Data.
 
-Para configurar **Response action**, selecciona la entidad de datos deseada y define, para cada campo que se debe guardar, la ruta JSON correspondiente en la respuesta.
+Rellena el apartado **Información del request** con los datos de la solicitud que deseas enviar. En la sección **Acción de respuesta**, puedes indicar cómo debe guardarse la información de la respuesta en Master Data.
 
-### Acciones en caso negativo
+![http-request-es](//images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/a24d038b06e2153e667a90c9a42920d9/http-request-es.png)
 
-Se harán los disparos de eventos cuando el registro no pase por los filtros adicionales del trigger. Se pueden configurar los mismos eventos de las "Acciones en caso positivo".
+Para configurar la **Acción de respuesta** selecciona la entidad de datos deseada y especifica la ruta JSON correspondiente para cada campo que se debe guardar en la respuesta.
 
-<!--
-## Ejemplo
-Vea el siguiente video con la configuración del siguiente escenario: envío de un correo electrónico de Bienvenida a cada nuevo cliente de la tienda. A no ser que el cliente forme parte de un clúster. En este caso, el enfoque de bienvenida se hará por teléfono; por lo tanto, clientes del clúster "Cluster 1" no deben recibir el  correo electrónico.
+### Si es negativo
 
-<iframe width="840" height="473" src="https://www.youtube.com/embed/A6UrxcYIq5E?feature=oembed" frameborder="0" allowfullscreen></iframe>
--->
+Los eventos se activarán cuando el registro no cumpla los filtros adicionales del trigger. Puedes configurar los mismos eventos de las [acciones si es positivo](#si-es-positivo).
 
 ## Ejemplos
 
-- [Configurar carrito abandonado
-](https://help.vtex.com/es/tutorial/configurando-carrinho-abandonado--tutorials_740)
+- [Configurar carrito abandonado](https://help.vtex.com/es/tutorial/configurar-carrito-abandonado--tutorials_740)
diff --git a/docs/tutorials/es/credit-card-basic-payment-flow.md b/docs/tutorials/es/credit-card-basic-payment-flow.md
index ff1f881c9..9cedd29dd 100644
--- a/docs/tutorials/es/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/es/credit-card-basic-payment-flow.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 Este artículo tiene como objetivo explicar cómo funciona el flujo básico de un pago por __tarjeta de crédito__:
 
-![ES Flujo Tarjeta de Credito](https://images.ctfassets.net/alneenqid6w5/JziB4sI4XzTW0lpAwt1xL/dcd6a342402fc2f003fe76b6f1d38c8e/ES_Flujo_Tarjeta.svg)
+![ES Flujo Tarjeta de Credito](//images.ctfassets.net/alneenqid6w5/JziB4sI4XzTW0lpAwt1xL/dcd6a342402fc2f003fe76b6f1d38c8e/ES_Flujo_Tarjeta.svg)
 
 1. En la pantalla de Checkout, el cliente elige el __Medio de Pago__ tarjeta de crédito para realizar el pago de su compra.
 2. La información de este pago se pasa al __Gateway de Pagos__. El [gateway](/es/tutorial/que-es-un-gateway-de-pagos) es el player responsable de garantizar que este pago se realice con éxito.
diff --git a/docs/tutorials/es/criar-um-produto-beta.md b/docs/tutorials/es/criar-um-produto-beta.md
new file mode 100644
index 000000000..4ba8d98e5
--- /dev/null
+++ b/docs/tutorials/es/criar-um-produto-beta.md
@@ -0,0 +1,174 @@
+---
+title: 'Agregar producto (Beta)'
+id: 2nkoy6RakJEVF7ug4ZP0bP
+status: PUBLISHED
+createdAt: 2023-10-31T13:43:19.226Z
+updatedAt: 2023-11-05T15:00:16.505Z
+publishedAt: 2023-11-05T15:00:16.505Z
+firstPublishedAt: 2023-11-05T14:13:41.744Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: criar-um-produto-beta
+locale: es
+legacySlug: criar-um-produto-beta
+subcategory: 
+---
+
+<div class="alert alert-info">
+Esta funcionalidad se encuentra en fase beta, lo que significa que estamos trabajando para optimizarla. Si tienes alguna duda ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>.</div>
+
+La página **Agregar producto(Beta)** permite crear y editar [productos](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) y sus correspondientes SKU en el Admin VTEX. Para agregar un nuevo producto sigue los pasos a continuación: 
+
+1. En el Admin VTEX, accede a **Catálogo**>**Productos y SKUs** o ingresa Productos y SKUs en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en `+ Agregar producto`.
+3. Define si el producto que vas a crear estará activo en la tienda. Para que el producto se cree como activo en la tienda debes seleccionar la opción **Activo** <i class="fas fa-toggle-on"></i> en la esquina superior derecha de la página.
+ Si deseas crear un producto en modo inactivo, haz clic en el botón <i class="fas fa-toggle-on"></i> y observa que la opción cambia a **Inactivo**. También puedes activarlo posteriormente desde la página de edición del producto o desde la lista de productos.
+5. Rellena la información solicitada en cada pestaña; a continuación, proporcionamos detalles sobre cada una.         
+- [Producto](https://docs.google.com/document/d/1CLB5arQdCD4eCQLBhU50QzpgH88PTVQ2/edit#bookmark=id.z337ya)
+- [Atributos](https://docs.google.com/document/d/1CLB5arQdCD4eCQLBhU50QzpgH88PTVQ2/edit#bookmark=id.3j2qqm3)
+- [SKUs](https://docs.google.com/document/d/1CLB5arQdCD4eCQLBhU50QzpgH88PTVQ2/edit#bookmark=id.1y810tw)
+6.  Selecciona la opción Activo <i class="fas fa-toggle-on"></i> en la parte superior derecha de la página para activar el SKU.
+7.  Haz clic en `Guardar`.
+
+Una vez hecho esto, el producto se activará y estará disponible en tu tienda.
+
+<div class="alert alert-info">Si tras crear el producto no se muestra en el sitio web de tu tienda, consulta el artículo <a href="https://help.vtex.com/es/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382">¿Por qué el producto no aparece en el sitio web?</a>, para saber cómo solucionar este problema.</div>
+
+## Producto
+
+En esta pestaña se realiza el registro del producto, para lo que es necesario rellenar los campos que se describen a continuación con las características del ítem.
+
+### Información general
+![image9](//images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
+**- Nombre**: ingresa el título del producto en la tienda. Utiliza vocabulario sencillo y evita términos en otro idioma o redacción compleja. Este campo es importante para SEO y se debe respetar el límite de 150 caracteres. Campo obligatorio. Ejemplo: Calzado deportivo Ultralight.
+
+**- Palabras sustitutas**: ingresa sinónimos de términos relacionados con el nombre asignado al producto, separados por comas (`,`). Este campo es importante para ampliar el alcance de las búsquedas y debe respetarse el límite de 8000 caracteres.
+
+Ejemplo: para el producto Calzado deportivo Ultralight, las palabras similares podrían ser: Tenis ultraligeros, Zapatillas de deporte Ultra. No es necesario rellenar este campo si tu tienda utiliza VTEX Intelligent Seach. Para saber más, consulta el artículo Sinónimos.
+
+**- Marca**: selecciona una marca ya registrada en la tienda para relacionarla con el producto. Campo obligatorio. Ejemplo: SportXtreme.
+
+**- Categoría**: selecciona la categoría o subcategoría relacionada con el producto. Campo obligatorio. Ejemplo: Calzado deportivo.
+
+**- Código de referencia**: ingresa el código de referencia único del producto para facilitar la organización de tu tienda. Ejemplo: TXU1234.
+
+## Descripción
+
+En este paso, debes ingresar una descripción de la información más importante relacionada con el producto. El texto debe ser un resumen sencillo y fácilmente comprensible para el cliente. 
+
+**Ejemplo**: "El calzado deportivo Ultralight es la elección perfecta para atletas que buscan alto rendimiento y comodidad. Con un diseño innovador y materiales de alta tecnología, estos tenis proporcionan máxima ligereza y resistencia durante la actividad física."
+
+El editor de texto de la descripción es de tipo texto enriquecido, es decir, tienes a tu disposición varios recursos de formato utilizando la barra de herramientas de este campo, ilustrada a continuación.
+
+![image10](//images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
+Estos son los recursos disponibles en la barra de herramientas:
+
+- __Estilos__: define el estilo del texto seleccionado. Las opciones son: **Normal** y **Título 1** hasta **Título 6**.
+**Tamaño de la fuente**: modifica el tamaño de la fuente del texto seleccionado. Puedes elegir un valor entre 10 y 36 puntos.
+- __Negrita__: aplica formato de negrita al texto seleccionado.
+- __Cursiva__: aplica formato de cursiva al texto seleccionado.
+- __Subrayado__: subraya el texto seleccionado.
+- __Alinear texto a la izquierda__: alinea el texto seleccionado a la izquierda.
+- __Centrar texto__: centra el texto seleccionado.
+- __Alinear texto a la derecha__: alinea el texto seleccionado a la derecha.
+- __Lista con viñetas__: transforma el texto seleccionado en un elemento de una lista organizada con viñetas.
+- __Lista numerada__: transforma el texto seleccionado en un elemento de una lista ordenada numéricamente.
+- __Agregar link__: vincula un link al texto seleccionado. Al hacer clic en este botón, debes ingresar la siguiente información y después hacer clic en `Guardar`.
+
+  **- Texto del link:** ingresa el texto que contendrá el link.
+
+  **- URL:** inserta el link cuyo texto redireccionará al usuario.
+
+   **- Abrir link en una nueva pestaña:** selecciona esta opción si deseas que el usuario abra la página en una nueva pestaña del navegador cuando haga clic en el link. No la selecciones si el objetivo es que el usuario acceda al link en la misma pestaña.
+
+- **Código fuente**: muestra el código fuente de la descripción en HTML. Si lo deseas, puedes editar la descripción directamente desde el código fuente. Para regresar a la vista anterior, debes volver a hacer clic en el botón del código fuente.
+
+## SEO
+![image11](//images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
+- **URL del producto**: ingresa la URL a través de la cual se podrá acceder al producto en la tienda. En este campo no se pueden utilizar espacios ni caracteres especiales. Si la URL está compuesta por más de una palabra, debes separarlas con un `-`. Campo obligatorio. Ejemplo: calzado-deportivo-ultralight.
+- **Título de la página**: ingresa el título de la página del producto. Para optimizar la posición de tu producto en los resultados de búsqueda, es recomendable no exceder los 60 caracteres. Campo obligatorio. Ejemplo: Calzado deportivo 
+Ultralight.
+- **Metadescripción**: ingresa el título de la página del producto. Para optimizar la posición de tu producto en los resultados de búsqueda, es recomendable no exceder los 60 caracteres. Campo obligatorio. Ejemplo: Te presentamos el calzado deportivo Ultralight de SportXtreme, perfecto para atletas que buscan ligereza y máxima resistencia durante la actividad física.
+## Operaciones y logística
+![image7](//images.ctfassets.net/alneenqid6w5/7u4kwyRsDBKFi1WVu5nV2q/3372b498b4d49932670575ea0b8211ab/image7.png)
+- **Políticas comerciales**: selecciona una o más [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) para relacionarlas con el producto y determinar en qué marketplaces estará disponible. 
+Si no seleccionas ninguna política comercial, el producto se vinculará a todas ellas de manera predeterminada. Ejemplo: B2C.
+- **Proveedor**: selecciona un proveedor ya registrado en tu tienda para relacionarlo con el producto.
+
+- **Código fiscal**: ingresa el número de identificación fiscal del producto.
+
+## Visibilidad
+![image4](//images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)- **Mostrar en el sitio web**: activa o desactiva la visibilidad del producto en tu tienda. Si, por ejemplo, el producto es un regalo que no está disponible para la compra, es importante desactivar esta opción.
+
+- **Mostrar cuando no tenga stock**: activa o desactiva la opción de mostrar el producto en la tienda incluso si está fuera de stock. Si está activada, el producto agotado se mostrará en tu tienda en el formato [Avísame](https://help.vtex.com/es/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e), campo en que el cliente informa su email para ser avisado cuando el producto vuelva a estar disponible.
+ Si la opción está desactivada, el producto no se mostrará en la tienda cuando esté agotado.
+- **Prioridad en el orden de búsqueda**: ingresa un valor numérico para definir la prioridad en la página de resultados de búsqueda. Consulta el artículo [¿Cómo funciona el campo Score?](https://help.vtex.com/es/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae), para saber más sobre este campo. Si tu tienda utiliza VTEX Intelligent Search, consulta [¿Cómo funciona VTEX Intelligent Search?](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/23mytRDsEduqLO0Lo7yufy)
+
+## Atributos
+
+Dependiendo de la categoría a la que pertenece el producto que creaste, en la pestaña **Atributos** pueden aparecer campos para rellenar. Estos campos son [especificaciones](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) que puedes añadir a tus SKU para atribuir características a los productos de tu tienda.
+
+Si creaste algún campo de producto que sea obligatorio, el producto solo podrá activarse una vez que se haya rellenado la especificación.
+
+En la pestaña Atributos se mostrarán los grupos de especificaciones con las especificaciones que registres. Como se puede observar en la imagen, el grupo de especificación es **Características** y las especificaciones registradas son **Video** y **Ver más**.
+![image3](//images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
+## SKUs
+
+En esta pestaña, registrarás los [SKUs](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA#) que estarán vinculados al producto que creaste anteriormente. 
+
+<div class="alert alert-info">
+El producto debe tener al menos un SKU activo para estar disponible en tu tienda. Es necesario adjuntar una imagen al SKU para activarlo.</div>
+
+## Especificaciones
+Aquí se mostrarán las especificaciones anteriormente creadas para los SKU. Si creaste algún campo de SKU obligatorio, el SKU solo podrá activarse una vez que se haya rellenado esa especificación. 
+
+## Información general
+![image2](//images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
+- **Nombre**: el nombre del SKU que se mostrará en la tienda. Campo obligatorio.
+- **Código de referencia**: código que utilizará la tienda internamente para identificar el SKU. Campo obligatorio si no se ha rellenado el EAN/UPC del SKU.
+- **EAN/UPC**: campo que debe contener la información del código de barras. Campo obligatorio si no se ha rellenado el Código de referencia del SKU.
+- **Código del fabricante**: proporcionado por el fabricante para identificar su producto. Si un producto tiene un código específico, este campo debe rellenarse.
+- **Condición comercial**: utilizada para definir promociones o reglas de pago en cuotas para SKU. Si no hay ninguna condición específica, utiliza el valor predeterminado. Más información en el artículo Registrar condición comercial.  
+- **Modal**: campo que vincula un producto inusual (carne, vidrio, colchón) a un transportista especializado en el envío de ese tipo de producto. Para más información consulta el artículo Cómo funciona el modal.
+
+## Imágenes
+
+<div class="alert alert-info" role="alert">Es necesario adjuntar al menos una imagen a cada SKU para activarlos.</div>
+
+Para agregar una imagen al SKU, sigue los pasos a continuación:
+
+1. Haz clic en el botón +.![image8](//images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
+2. Agrega el link a la imagen en el campo 🔗. Puedes añadir más de una imagen a tu SKU. Para hacerlo, haz clic en + Agregar imagen e inserta el nuevo link.![image6](//images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
+3. Haz clic en `Guardar`.
+
+La primera imagen agregada será la imagen principal del SKU, la que se mostrará en la tienda y en los resultados de búsqueda.</div>
+
+Para editar los metadatos de una imagen haz clic en el botón <i class="fas fa-ellipsis-v"></i> y selecciona <i class="fas fa-pencil-alt"></i> `Editar metadatos`.
+
+También puedes eliminar una imagen haciendo clic en el botón <i class="fas fa-ellipsis-v"></i> y seleccionando<i class="fas fa-trash-alt"></i> `Eliminar`.
+
+## Peso y dimensiones
+![image1](//images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
+### Peso y dimensiones de envío
+- **Peso del paquete**: peso del paquete vacío en kilogramos. Campo obligatorio.
+- **Anchura del paquete**: ancho del paquete en centímetros. Campo obligatorio.
+- **Altura del paquete**: alto del paquete en centímetros. Campo obligatorio.
+- **Longitud del paquete:** largo del paquete en centímetros. Campo obligatorio.
+
+### Peso y dimensiones reales
+- **Peso real**: peso del SKU en kilogramos.
+- **Anchura real**: ancho del SKU en centímetros. 
+- **Altura real**: alto del SKU en centímetros.
+- **Longitud real**: largo del SKU en centímetros.
+
+### Sistema de medidas
+- **Unidad de medida**: se utiliza solo en los casos en que es necesario convertir la unidad de medida para la venta. Por ejemplo, cuando el producto se vende en cajas pero los clientes quieren comprarlo por m². En casos comunes se utiliza "ud." (abreviatura de unidad).
+
+- **Multiplicador de unidad**: unidad numérica que multiplica la cantidad seleccionada del producto cuando se agrega al carrito. Si el multiplicador es 5, el producto se añadirá en múltiplos de 5, es decir, 5, 10, 15, 20, sucesivamente. 
+
+## Configuración avanzada
+![image5](//images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
+- **Activar kit**: los SKU que componen un kit solo pueden venderse juntos. Puedes hacer que un SKU forme parte de un kit <i class="fas fa-toggle-on"></i> o no <i class="fas fa-toggle-off"></i>.
+- **Generar crédito en tarjeta de regalo**: crédito que recibe el cliente al completar la compra de un SKU determinado. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+
diff --git a/docs/tutorials/es/custom-fields-when-adding-an-organization.md b/docs/tutorials/es/custom-fields-when-adding-an-organization.md
new file mode 100644
index 000000000..9dbdee0bc
--- /dev/null
+++ b/docs/tutorials/es/custom-fields-when-adding-an-organization.md
@@ -0,0 +1,48 @@
+---
+title: 'Campos personalizados en el registro de organizaciones'
+id: 2MqEVusOvcbqagNwOuHA7f
+status: PUBLISHED
+createdAt: 2024-06-06T12:19:51.817Z
+updatedAt: 2024-07-03T17:35:29.850Z
+publishedAt: 2024-07-03T17:35:29.850Z
+firstPublishedAt: 2024-06-06T12:40:11.507Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: campos-personalizados-en-el-registro-de-organizaciones
+locale: es
+legacySlug: campos-personalizados-en-el-registro-de-organizaciones
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+
+La plataforma VTEX permite a los usuarios de una organización con rol de administrador crear y gestionar campos personalizados en el proceso de registro de nuevas organizaciones o centros de costos. Este recurso facilita la inclusión de información específica y relevante para la empresa.
+
+## Definición y gestión de campos
+
+Los usuarios de la organización con rol de administrador pueden definir campos adicionales en el Admin VTEX, que estarán disponibles para ser completados al registrar nuevas organizaciones o centros de costos. Estos campos personalizados se diseñaron para recopilar datos específicos y relevantes para la empresa, datos no contemplados en el formulario estándar de inscripción. 
+
+## Registrar campo personalizado
+
+Los campos personalizados permiten a los usuarios agregar información específica y personalizada para organizaciones o centros de costos. Estos campos pueden adaptarse en función de las necesidades de la empresa, permitiendo así la captura de información relevante para sus operaciones.
+
+Para registrar un campo personalizado sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a Apps > Organizaciones y centros de costos B2B > Organizaciones, o ingresa Organizaciones en la barra de búsqueda de la parte superior de la página.
+
+2. Haz clic en la pestaña **Campos personalizados**.
+
+3. En el menú desplegable, selecciona Organizaciones o Centros de costos.
+
+4. Haz clic en el botón Agregar campo. Se añadirá una fila vacía a la lista de campos personalizados.
+
+5. Haz clic en <i class="fas fa-ellipsis-v" aria-hidden="true"></i> para editar.
+
+6. Rellena la información necesaria:
+    - Utilizar en el registro: indica si el campo debe mostrarse en el formulario de registro.
+    - Tipo de campo: determina si el campo mostrado será un texto o una lista desplegable con valores que el usuario debe seleccionar.
+    - Nombre del campo personalizado: nombre del campo que deseas personalizar.
+7. Haz clic en `Actualizar`.
+
+Para finalizar, asegúrate de hacer clic en `Guardar configuración` en la esquina superior derecha de la página después de cualquier cambio realizado.
+
diff --git a/docs/tutorials/es/custom-payment-information-for-argentina.md b/docs/tutorials/es/custom-payment-information-for-argentina.md
index 1657cacc5..5d3d6814a 100644
--- a/docs/tutorials/es/custom-payment-information-for-argentina.md
+++ b/docs/tutorials/es/custom-payment-information-for-argentina.md
@@ -1,10 +1,10 @@
 ---
 title: 'Información de pagos personalizados de Argentina'
 id: jvDroisg0wu0sQMAW4qAs
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.320Z
-updatedAt: 2019-12-31T15:27:50.416Z
-publishedAt: 2019-12-31T15:27:50.416Z
+updatedAt: 2024-03-19T12:11:44.590Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:14:28.069Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/custom-product-fields.md b/docs/tutorials/es/custom-product-fields.md
new file mode 100644
index 000000000..794c2dcde
--- /dev/null
+++ b/docs/tutorials/es/custom-product-fields.md
@@ -0,0 +1,90 @@
+---
+title: 'Campos de producto personalizables'
+id: 6tJOSJ2o9phVIb8XXG6QSk
+status: PUBLISHED
+createdAt: 2024-07-23T19:44:34.554Z
+updatedAt: 2024-07-23T20:25:32.123Z
+publishedAt: 2024-07-23T20:25:32.123Z
+firstPublishedAt: 2024-07-23T20:17:01.358Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: campos-de-producto-personalizables
+locale: es
+legacySlug: campos-de-producto-personalizables
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+Los campos personalizables le permiten adaptar los atributos del producto según sea necesario, mejorando la información sobre los productos enviados a Mercado Livre.  
+En esta documentación encontrarás **qué campos se pueden personalizar**, **cómo crear un nuevo campo** y **qué valores se aceptan**.  
+
+## Campos personalizables
+
+Consulte la siguiente tabla sobre qué campos se pueden personalizar y la descripción del campo:
+
+| **Nombre del campo** | **Descripción** |
+|:---:|:---:|
+| meli_title | Envíe el nombre registrado en este campo en lugar del nombre en el campo `título`. |
+| meli_shipping_mode | Define el [tipo de logística](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy) utilizada por el vendedor: [me1](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy#mercado-envios-1-me1) o [me2](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy#mercado-envios-2-me2). |
+| officialstoreid_meli | Define la tienda oficial del vendedor en Mercado Livre. |
+| plaintext_description_meli | Envía la descripción del producto registrado en este campo en lugar de la descripción en el campo `productDescription`. |
+| free_shipping | Informar a Mercado Livre si el producto se ofrece con la opción de envío gratuito. |
+
+## Crear un campo de producto
+
+Para crear un campo de producto, sigue los pasos a continuación:  
+
+1. En el Admin VTEX, accede a Catálogo, o escribe Catálogo en la barra de búsqueda en la parte superior de la página.  
+2. Haz clic en Categorías.  
+3. Haz clic en la categoría asociada al grupo de especificaciones en el que deseas crear un campo.  
+  Verás que, al crear un campo en un nivel de categoría superior, la especificación aparecerá en todos los niveles de categoría inferiores.  
+4. Haz clic en __Acciones.__  
+5. Haz clic en __Campo (Producto).__  
+6. Haz clic en __Nuevo campo.__  
+7. Completa la información del campo que estás creando:  
+<div class="alert alert-warning">
+El nombre del campo debe completarse exactamente como uno de los nombres presentados en la tabla de secciones<a href="#campos-personalizables">Campos personalizables</a>.
+</div>  
+
+  __Nombre:__ nombre de la especificación (campo) de producto.  
+  __Texto:__ descripción del campo.  
+  __Tipo:__ tipo de campo, el cual puede variar entre __Texto, Texto grande, Número, Combo, Radio, Checkbox, Texto indexado y Texto grande indexado.__ Consulta la sección Tipos de campo de producto para obtener más información sobre cada opción.  
+  __Valor predeterminado:__ valor de llenado ya definido en la creación del campo.  
+  __Grupo:__ nombre del grupo de especificaciones creado previamente y del cual formará parte ese campo.  
+  __Filtro:__ define si la especificación se usará como filtro en la navegación del sitio web.  
+  __Obligatorio:__ define si el valor se debe completar obligatoriamente en el registro del producto o no. Si el campo es obligatorio, el producto solo podrá activarse luego de rellenar la información de esta especificación.  
+  __Muestra especificación:__ define si el campo se muestra en la página de detalles del producto, en la pestaña Especificaciones.  
+  __Link en el menú superior:__ define si el link para los valores del campo se muestra en el menú principal del sitio web.  
+  __Link en el menú lateral:__ define si el link para los valores del campo se muestra en el menú lateral del sitio web.  
+  __Activo:__ inserta o elimina este campo en el registro del producto (pestaña Especificaciones).  
+8. Haz clic en __Guardar.__
+
+## Registrar valores en el campo de producto
+
+Los valores de los campos de producto variarán según el tipo de campo. No se crearán valores predefinidos para los campos __Texto__ y __Número.__ Estos se rellenarán libremente durante el registro del producto en la pestaña __Especificaciones.__  
+
+Sin embargo, para los campos __Combo, Radio y Checkbox__ es necesario registrar valores predefinidos para seleccionarlos durante el registro del producto. Verifique los valores aceptados para cada campo personalizable en la siguiente tabla:  
+
+| **Nombre del campo** | **Tipo de campo** | **Descripción del tipo de campo** | **Valor de campo** |
+|:---:|:---:|:---:|:---:|
+| meli_title | Texto grande | Rellenar contenido como texto libre, adecuado para estructuras HTML grandes. | Texto libre |
+| meli_shipping_mode | Combo | Contenido con dos o más valores predefinidos, para seleccionar una opción en una lista desplegable. | me1 e me2 |
+| officialstoreid_meli | Texto | Rellenar el contenido como texto libre, apto para textos pequeños con formato sencillo. No apto para estructuras HTML grandes. | Texto alfanumérico. Ej: 8457 |
+| plaintext_description_meli | Texto grande | Rellenar contenido como texto libre, adecuado para estructuras HTML grandes. | Texto libre |
+| free_shipping | Checkbox | Opción que solo tiene valores equivalentes a verdadero o falso. | Si la casilla está marcada el envío es gratuito, si la casilla no está marcada el envío no es gratuito. |
+
+Sigue las instrucciones a continuación:
+
+1. En el Admin VTEX, accede a **Catálogo**, o escribe **Catálogo** en la barra de búsqueda en la parte superior de la página.  
+2. Haz clic en Categorías.  
+3. Haz clic en la categoría en la que está guardado el campo de producto.  
+4. Haz clic en el botón **Acciones**<i class="fas fa-angle-down" aria-hidden="true"></i>.
+5. Haz clic en **Campo (Producto)**.
+6. Haz clic en la flecha hacia abajo <i class="fas fa-angle-down" aria-hidden="true"></i>.
+7. Haz clic en **Valores**.  
+  Si ya hay valores registrados, deberás hacer clic también en Nuevo valor.  
+8. Rellena el campo **Nombre** con los valores que desees crear para ese campo. Ingresa un valor por línea y presiona la tecla `Enter` entre cada valor.  
+9. Haz clic en **Guardar**.  
+
+Los valores creados se mostrarán en la pestaña **Especificaciones** en el registro de Producto.
+
diff --git a/docs/tutorials/es/customer-approval.md b/docs/tutorials/es/customer-approval.md
index f73175c15..4a4da58e7 100644
--- a/docs/tutorials/es/customer-approval.md
+++ b/docs/tutorials/es/customer-approval.md
@@ -3,8 +3,8 @@ title: 'Aprobación de clientes'
 id: 2fDHMMLJl00Pm6imiACU72
 status: PUBLISHED
 createdAt: 2021-03-30T16:54:48.752Z
-updatedAt: 2023-03-29T00:06:00.612Z
-publishedAt: 2023-03-29T00:06:00.612Z
+updatedAt: 2024-06-18T22:16:38.698Z
+publishedAt: 2024-06-18T22:16:38.698Z
 firstPublishedAt: 2021-03-30T17:14:26.769Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,25 +15,25 @@ legacySlug: aceptacion-clientes, aprobacion-clientes
 subcategory: 42hDtnYXHw5ExG6l19RP1l
 ---
 
-La aprobación de clientes ocurre en Master Data y puede realizarse vía Admin o vía API.
+La aprobación de clientes se lleva a cabo en Master Data y puede realizarse a través del Admin o a través de API. Consulte a continuación las instrucciones sobre cada una de las dos formas de aprobación.
 
-## Aprobación de clientes vía Admin
+## Aprobar clientes vía Admin
 
-Para aprobar clientes en el Admin:
+Para aprobar clientes en Admin, siga los pasos que se indican a continuación:
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
-2. Dentro de __Profile System__, haga clic en el ícono <i class="fas fa-bars"></i> junto a __Clientes.__
+2. Dentro de __Profile System__, haga clic en el ícono <i class="fas fa-bars"></i> junto a __Clientes__.
 3. Haga clic en la línea correspondiente al cliente que desea aprobar.
-4. En la parte inferior de la página, haga clic en el botón azul __Editar.__
+4. En la parte inferior de la página, haga clic en el botón `Editar`.
 5. Seleccione la __casilla__ del campo «Aprobado».
-6. En la parte inferior de la página, haga clic en el botón azul __Guardar.__
+6. En la parte inferior de la página, haga clic en el botón `Guardar`.
 
 De este modo, el contenido de la tienda se mostrará a los clientes seleccionados. 
 
-## Aprobación de clientes vía API
+## Aprobar clientes vía API
 
-Puede aprobar varios clientes a la vez a través de una ruta de [API de Master Data](https://developers.vtex.com/vtex-developer-docs/reference/master-data-api-v2-overview "API de Master Data").
+Puede aprobar varios clientes a la vez a través de una ruta de [API de Master Data](https://developers.vtex.com/docs/api-reference/masterdata-api).
 
-Toda la información relacionada con un cliente puede interpretarse como un documento en [entidad de datos «Cliente»](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265). Por lo tanto, la ruta [PATCH Create or Update partial document](https://developers.vtex.com/vtex-developer-docs/reference/documents#createorupdatepartialdocument "PATCH Create or Update partial document") debe ser utilizada para cambiar masivamente el valor relacionado con el campo «Aprobado».
+Toda la información relacionada con un cliente puede interpretarse como un documento en [entidad de datos](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265) __Cliente__. Por lo tanto, la ruta [PATCH Update partial document](https://developers.vtex.com/docs/api-reference/masterdata-api#patch-/api/dataentities/-acronym-/documents/-id-) debe ser utilizada para cambiar masivamente el valor relacionado con el campo __Aprobado__.
 
-Consulte el artículo [Importar datos de clientes](https://help.vtex.com/es/tutorial/importar-datos-de-clientes-brasil?locale=pt "Importar datos de clientes") para saber qué campos deben crearse para un documento específico de persona física. 
+Consulte el artículo [Importar datos de clientes](https://developers.vtex.com/docs/guides/import-customer-data) para saber qué campos deben crearse para un documento específico de persona física.
diff --git a/docs/tutorials/es/customer-credit-overview.md b/docs/tutorials/es/customer-credit-overview.md
index 3c2b9c73d..fcfa845d8 100644
--- a/docs/tutorials/es/customer-credit-overview.md
+++ b/docs/tutorials/es/customer-credit-overview.md
@@ -3,8 +3,8 @@ title: 'Customer Credit - Visión General'
 id: 1uIqTjWxIIIEW0COMg4uE0
 status: PUBLISHED
 createdAt: 2018-11-08T17:11:28.486Z
-updatedAt: 2023-03-29T14:46:02.462Z
-publishedAt: 2023-03-29T14:46:02.462Z
+updatedAt: 2024-02-09T21:37:56.199Z
+publishedAt: 2024-02-09T21:37:56.199Z
 firstPublishedAt: 2018-11-08T19:14:39.491Z
 contentType: tutorial
 productTeam: Financial
@@ -15,89 +15,77 @@ legacySlug: credit-control-vision-general
 subcategory: 7EWKfPIGfmI0G8iMYK8Aiy
 ---
 
-Customer Credit es la aplicación de VTEX que permite que la tienda ofrezca crédito a los clientes de confianza. Con más tiempo para pagar, el cliente tiene más poder de compra.
-
-Por la plataforma es posible configurar plazos y cuotas, así como gestionar cuentas, definiendo límites de crédito y acompañando los títulos de cobro emitidos. Sus clientes tienen visibilidad sobre el crédito disponible y los valores a pagar directamente en el sitio web de su tienda.
+Customer Credit es la aplicación de VTEX que permite a una tienda ofrecer crédito exclusivo a sus clientes de confianza, aumentando el poder adquisitivo al permitir un mayor plazo de pago de los pedidos.
 
 ## Cuándo utilizar
 
-Los modelos de negocio que tienen una relación comercial con sus clientes suelen necesitar un sistema de gestión de crédito para poder emitir boletas de pago para compras facturadas sin poner en riesgo el flujo de caja de la empresa. 
+Los modelos de negocio que tienen una relación comercial consolidada con sus clientes generalmente requieren de un sistema de gestión de crédito que permita la emisión de facturas sin comprometer el flujo de caja de la empresa.
 
-La aprobación de estos pagos en plataformas de comercio electrónico suele demandar esfuerzo manual de aprobación para cada pedido, incluso con clientes que tienen crédito disponible.
+La aprobación de estos tipo de pagos en plataformas de comercio electrónico generalmente requiere un esfuerzo de aprobación manual pedido por pedido, incluso para aquellos clientes que ya tienen crédito disponible.
 
-Las tiendas con relaciones B2B como distribuidores de redes minoristas, venta directa a revendedores, material de oficina para empresas o insumos industriales pueden utilizar Customer Credit para ofrecer una experiencia integrada a la plataforma VTEX de compra y pago a plazo.
+Los comercios que realizan transacciones comerciales B2B, como distribuidores de red minoristas, venta directa a revendedores, artículos de oficina para empresas o insumos industriales, pueden utilizar Customer Credit para ofrecer una experiencia de compras y pago de cuotas integrada con la plataforma VTEX.
 
 ## Cómo funciona
 
-**Flujo básico de cómo funciona Customer Credit en las tiendas VTEX.**
+A través de VTEX Admin o [API de Customer Credit](https://developers.vtex.com/docs/api-reference/customer-credit-api), es posible realizar las siguientes acciones en la aplicación Customer Credit:
 
-1. La tienda instala la app de Customer Credit y hace las configuraciones iniciales.
-2. La tienda establece límite de crédito para la cuenta corriente del usuario.
-3. El usuario hace un pedido utilizando el crédito de la tienda en Smartcheckout.
-4. El pedido carga el valor del límite de crédito del usuario y genera un título.
-5. Después, el usuario paga el título generado.
-6. El pago del título recarga el límite de crédito de la cuenta corriente del usuario.
+- Crear y administrar cuentas para clientes elegidos.
+- Establecer límites de crédito y tolerancias para cada cuenta.
+- Configurar plazos y cuotas para documentos de facturas.
+- Monitorear y modificar el status de las facturas emitidas.
 
-Por haber sido desarrollado en VTEX, Customer Credit está plenamente integrado al SmartCheckout, lo que significa que la experiencia de compra de sus clientes sigue siendo la misma.
-Usted puede elegir los usuarios que recibirán crédito, establecer el límite de crédito para cada uno de ellos y administrar individualmente cada título.
+<div class="alert alert-info">
+Cuando se instala, el Customer Credit aparece como una opción de pago en el momento del pago solo para los clientes seleccionados por el administrador de la tiend, y muestra la cantidad de crédito disponible para usar en la compra.
+</div>
 
-Customer Credit puede ser utilizado tanto por la interfaz web del Admin como por la API. 
+Vea a continuación el flujo básico de cómo funciona el Customer Credit en las tiendas VTEX:
 
-## Conceptos
+![GIF_CC_ES](//images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/99a8ceaf503fd3154ab5e2aa9b2f3021/GIF_CC_ES.gif)
 
-### Cuenta corriente
+## Definiciones en Customer Credit
 
-Para obtener acceso al pago a plazo el usuario debe tener acceso a una cuenta registrada en Customer Credit. Esta cuenta se compone de identificadores como e-mail y documento, así como el límite de crédito definido.
+### Cuenta (Cuenta de Customer Credit)
 
-### Límite de crédito
+Para utilizar Customer Credit como medio de pago de una compra, el cliente debe tener una cuenta registrada por el administrador de la tienda en la aplicación Customer Credit. Esta cuenta tiene información como tipo y número de documento del titular, correo electrónico, límite de crédito y tolerancia.
 
-Para cada cuenta usted debe definir un límite de crédito. Este límite indica el valor máximo que la cuenta puede tener en títulos abiertos al mismo tiempo. 
-Cuando los títulos se pagan o se cancelan, sus valores restauran el límite de crédito. El límite puede ser restablecido por el usuario, en cualquier momento, con los permisos necesarios.
+### Limite de crédito
 
-En el momento de la compra, el cliente tiene visibilidad de cuánto crédito tiene disponible. Cuando no es suficiente para el valor total, no es posible utilizar sus créditos.
+Cada cuenta tiene un límite de crédito registrado al momento de su apertura. Este límite indica el monto máximo que el cliente puede utilizar para realizar una o más compras al mismo tiempo a través de Customer Credit.
 
-El límite de crédito definido en una cuenta también puede ser utilizado por más de un dependiente. 
+<div class="alert alert-warning">
+El administrador de la tienda puede cambiar el límite de crédito de una cuenta en cualquier momento.
+</div>
 
-### Título
+### Crédito disponible
 
-Títulos son referencias de pagos futuros. Se crean automáticamente cuando un pedido pagado con Customer Credit se factura. Se compone de fecha de vencimiento, valor y descripción. 
+Monto que el cliente aún tiene disponible en su cuenta para realizar compras a través de Customer Credit.
 
-Un enlace de pago externo se puede agregar a cada título para facilitar su liquidación.
+Cada vez que el cliente completa una compra y se factura el pedido, la cantidad de crédito disponible disminuye. Sin embargo, después de que el cliente realiza el pago de la factura emitida, el valor del crédito disponible vuelve al valor previo a la compra.
 
-Hay tres estados posibles para los títulos: **Abierto**, **Pagado** y **Cancelado**. En la interfaz habrá un cuarto estado,  **Vencido**, pero que es en realidad un título **Abierto** cuya fecha de vencimiento ha expirado.
+<div class="alert alert-warning">
+En el momento de una compra, el cliente tiene visibilidad de cuánto crédito puede utilizar a través del Customer Credit. Si el valor de la compra es mayor que el crédito disponible, no se podrá realizar el pago a través de Customer Credit.
+</div>
 
-Un título siempre se crea con el estado Abierto, y dependiendo de las acciones del Admin o las llamadas de API puede transitar al estado de Pagado o Cancelado.
+### Factura
 
-### Tolerancia
+Factura es el documento que se genera luego de que el cliente realiza una compra utilizando Customer Credit como medio de pago y se factura el pedido.
 
-Permite que una compra sea aprobada aunque supere el crédito disponible del usuario. Si esta funcionalidad está activada, un porcentaje puede configurarse de forma individual para cada cuenta registrada.
+En los casos de compras a plazos, los títulos se generan según el número de cuotas. Por ejemplo, una compra realizada con pago en 10 cuotas sobre Customer Credit generará 10 facturas relacionadas con el mismo número de pedido.
 
 ### Plazos y cuotas
 
-Customer Credit le permite configurar como desee los plazos de las cuotas que estarán disponibles para sus clientes. Algunos ejemplos comunes de plazos usados son de 7 días, 28, 45, 30/60, 30/60/90, etc.
+Customer Credit permite a los administradores de tiendas configurar diferentes condiciones de pago y escenarios de cuotas para ofrecer una mayor flexibilidad de pago a los clientes registrados.
 
 ### Preautorización y liquidación
 
-Después de aprobado el pago con crédito, el sistema preautoriza el valor, reservándolo automáticamente después de 5 días hábiles o hasta que el pedido sea facturado. En ese momento, ocurre la liquidación del valor en la cuenta y los títulos se generan.
-
-El flujo sigue el mismo estándar de las tarjetas de crédito: las modificaciones realizadas en el pedido durante el período de preautorización alteran el valor de crédito reservado. Las modificaciones realizadas después de la liquidación; es decir, después de la emisión de los títulos, actualizan los títulos ya emitidos si el valor disminuye y emiten nuevos títulos si el valor del pedido aumenta.
-
-## Puntos de contacto
-
-### Admin
-
-La interfaz de Customer Credit en el Admin de VTEX proporciona visibilidad completa del sistema: títulos, cuentas y configuraciones generales. La interfaz también le permite buscar, filtrar y ordenar datos, además de importarlos y exportarlos.
-
-### Checkout
-
-Es por el Checkout de VTEX que el usuario podrá cerrar compras usando Customer Credit. El sistema comprobará automáticamente si el usuario ya tiene una cuenta con crédito y, en caso positivo, le permitirá autentificarse para visualizar el crédito disponible y las opciones de plazos y cuotas para cerrar la compra.
-
-### Mis Créditos
+Luego de que el cliente realiza la compra utilizando Customer Credit, el pago se aprueba como crédito y la plataforma preautoriza el monto, reservándolo automáticamente después de 5 días hábiles o hasta que se facture el pedido. En este punto, se liquida el importe de la cuenta y se generan las facturas.
 
-Es la interfaz por la cual su cliente tendrá acceso a la información de su cuenta. Es muy similar a la página de Cuentas del Admin de VTEX. En esta, el usuario ve sus límites disponibles, títulos pagados y en abierto, además del historial de la cuenta.
+El flujo en Customer Credit es similar al de las tarjetas de crédito en relación a las modificaciones de pedidos. Cuando se produce un cambio en el valor del pedido durante el período de preautorización, el monto del crédito cambia.
 
-## Instalación y configuración
-Preparamos una guía detallada para que usted [empiece a usar Customer Credit en su tienda](/es/tracks/customer-credit-como-empezar). Acceda y ofrezca crédito exclusivo a sus mejores clientes ahora mismo.
+<div class="alert alert-warning">
+Si es necesario cambiar una orden para reducir su valor después del período de liquidación (emisión de facturas), el sistema actualizará las facturas al nuevo valor. Si el valor del pedido aumenta, el sistema creará nuevas facturas.
+</div>
 
-Para obtener más información sobre las API de Customer Credit, visite [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api).
+## Instalacion y configuracion
 
+Para instalar y configurar Customer Credit en su tienda, acceda a Track [Customer Credit - Cómo Empezar](https://help.vtex.com/es/tracks/customer-credit-como-empezar--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
diff --git a/docs/tutorials/es/customizing-your-stores-typography.md b/docs/tutorials/es/customizing-your-stores-typography.md
index 447eecea4..38870d9c2 100644
--- a/docs/tutorials/es/customizing-your-stores-typography.md
+++ b/docs/tutorials/es/customizing-your-stores-typography.md
@@ -27,7 +27,7 @@ En el Admin, tienes la flexibilidad de personalizar la tipografía de tu tienda
 1. En el Admin VTEX, accede a **Storefront > Styles (Estilos)**.
 2. Selecciona el ícono de kebab (tres puntos).
 
-![Styles - More Options ES](https://images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/f58a158cd09d76ad56efc3876b742e2e/styles-two-es.png)
+![Styles - More Options ES](//images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/f58a158cd09d76ad56efc3876b742e2e/styles-two-es.png)
 
 3. Haz clic en **Edit (Editar) > Typography (Tipografía) > Font Family (Familia de fuentes)**.
 
@@ -51,7 +51,7 @@ Consulta la sección [Tokens de tipo](#type-tokens) para ver más información s
 2. Selecciona el ícono de kebab (tres puntos).
 3. Haz clic en **Edit (Editar) > Typography (Tipografía) >Type Tokens (Tokens de tipo)**.
 
-![Styles - Type tokens ES](https://images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/45b1dfaa49adb3535975be65b03938bf/styles-three-es.gif)
+![Styles - Type tokens ES](//images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/45b1dfaa49adb3535975be65b03938bf/styles-three-es.gif)
 
 4. Elige el token de tipo que deseas personalizar como, por ejemplo, **Heading 1** y haz clic en él.
 
diff --git a/docs/tutorials/es/dashboards-overview.md b/docs/tutorials/es/dashboards-overview.md
index 1da07b6e1..892323365 100644
--- a/docs/tutorials/es/dashboards-overview.md
+++ b/docs/tutorials/es/dashboards-overview.md
@@ -3,8 +3,8 @@ title: 'Vista General Dashboards'
 id: 1yn2nZUoXtDO3teTEJsCNl
 status: PUBLISHED
 createdAt: 2023-03-29T21:16:46.179Z
-updatedAt: 2023-03-29T21:18:04.195Z
-publishedAt: 2023-03-29T21:18:04.195Z
+updatedAt: 2024-06-19T15:30:06.441Z
+publishedAt: 2024-06-19T15:30:06.441Z
 firstPublishedAt: 2023-03-29T21:18:04.195Z
 contentType: tutorial
 productTeam: Others
@@ -23,5 +23,4 @@ La sección incluye las siguientes páginas, que ya son parte del Admin:
 
 - [Visión general](https://help.vtex.com/es/v4/docs/vision-general-de-la-tienda--6mcM4LPUqQxSiXY6uFtXZy): es donde los administradores de tiendas tienen acceso a las principales métricas que afectan a los ingresos de sus tiendas. En este panel, puedes seguir la evolución de tus ventas a través de los recursos de análisis de tendencias de pedidos, tasa de conversión y gráficos de embudo de ventas.  
 - [Desempeño de ventas](https://help.vtex.com/es/v4/docs/desempeno-de-ventas--6gx46RGRzWO8qgaVck7PRp): un panel diseñado para el comercio unificado que ayuda a las tiendas a hacer crecer su negocio y a tomar decisiones más precisas.  
-- [Rendimiento de páginas web](https://help.vtex.com/es/v4/docs/rendimiento-de-paginas-web--7DeyhX8cGtG9PtAGkL8zvc): incorpora la herramienta PageSpeed Insights de Google a tu Admin VTEX para permitirte hacer un seguimiento del rendimiento de las URL de tu ecommerce. 
 
diff --git a/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md b/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md
new file mode 100644
index 000000000..06a0adc0e
--- /dev/null
+++ b/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md
@@ -0,0 +1,53 @@
+---
+title: 'Diccionario de datos de VTEX: Data Pipeline (Beta)'
+id: 69hMoE2woVw14nWR3ujVto
+status: PUBLISHED
+createdAt: 2024-02-01T18:51:29.281Z
+updatedAt: 2024-06-25T14:23:40.720Z
+publishedAt: 2024-06-25T14:23:40.720Z
+firstPublishedAt: 2024-05-27T19:26:59.681Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: diccionario-de-datos-de-vtex-data-pipeline-beta
+locale: es
+legacySlug: catalogo-vtex-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+<div class="alert alert-info">
+Esta funcionalidad se encuentra en fase beta, lo que significa que estamos trabajando para optimizarla. Si tienes alguna duda, ponte en contacto con <a  href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">nuestro soporte</a>.
+</div>  
+
+**VTEX Data Pipeline**, disponible exclusivamente para clientes VTEX, es una herramienta diseñada para explorar y analizar los datos de la tienda online almacenados en nuestros servidores. **Data Pipeline** es un producto add-on de VTEX que integra los datos del sitio web de tu tienda online con el almacén de datos y herramientas BI de tu preferencia, de forma limpia y segura.
+
+## Seguridad y privacidad
+
+**VTEX Data Pipeline** mejora la seguridad de los datos del sitio web de tu tienda online estableciendo una conexión directa y segura desde nuestro almacén de datos a tu herramienta de infraestructura de datos. Este enfoque elimina la necesidad de depender de procesos ETL (Extracción, Transformación y Carga) llevados a cabo por herramientas de terceros, proporcionando un control directo y seguro sobre el flujo de datos. Además, un aspecto clave de nuestra solución es la eliminación proactiva de toda la información personal identificable (PII) de los usuarios presentes en las tablas, lo que garantiza las mejores prácticas de protección de datos.  
+
+## ¿Qué es un diccionario de datos?
+
+En este diccionario tendrás acceso a todos los conjuntos de datos que ofrece **VTEX Data Pipeline**, cada uno detallado en una sección específica que describe sus características.
+
+Cada sección proporciona información como:
+
+- Características de los datos  
+  - Origen  
+  - Disponibilidad para el cliente  
+  - Historial  
+  - Intervalo mínimo de actualización  
+- Tablas de conjunto de datos  
+- Análisis con el conjunto de datos  
+- Correlaciones con otros datos  
+
+## Conjunto de datos
+
+A lo largo de las siguientes secciones puedes consultar la forma en que se relacionan los datos con tu negocio y la relevancia para tu proyecto.  
+Los conjuntos de datos disponibles son los siguientes:  
+
+- [Navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)  
+- [Pagos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Precios](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promociones](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)  
+- [Stock](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
diff --git a/docs/tutorials/es/data-entity.md b/docs/tutorials/es/data-entity.md
new file mode 100644
index 000000000..313daaa0a
--- /dev/null
+++ b/docs/tutorials/es/data-entity.md
@@ -0,0 +1,109 @@
+---
+title: 'Entidad de datos'
+id: tutorials_1265
+status: PUBLISHED
+createdAt: 2017-04-27T21:56:57.118Z
+updatedAt: 2024-06-21T21:12:23.798Z
+publishedAt: 2024-06-21T21:12:23.798Z
+firstPublishedAt: 2017-04-27T23:03:49.803Z
+contentType: tutorial
+productTeam: Master Data
+author: authors_3
+slug: entidade-de-datos
+locale: es
+legacySlug: entidades-de-datos-creacion-y-mantenimiento
+subcategory: 1l3IVVYwrrG5YOtdt7R2SN
+---
+
+Una entidad de datos es una representación de un conjunto de información sobre un determinado concepto. Toda entidad tiene campos, que son los datos que forman las entidades.
+
+Para ilustrarlo, imaginemos un sistema de control de bibliotecas. Este sistema controla los libros que los clientes pueden tomar prestados. En este ejemplo, los conceptos libro, cliente y préstamo (alquiler) son entidades que poseen informaciones sobre cada una de ellas. Una entidad de datos, por lo tanto, es un grupo de información sobre un determinado concepto.
+
+![data-entity-es](//images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/be338269e04b9d5835cda9a16ec9b601/data-entity-es.png)
+
+Estos conceptos permiten configurar los más diversos escenarios de control de datos en Master Data. De forma predeterminada, se ingresan las siguientes entidades de datos: Cliente, Dirección, Tiendas, etc. Puedes crear todas las entidades de datos que desees para personalizar el entorno de acuerdo con las necesidades de cada tienda.
+
+<div class="alert alert-warning">
+<p>Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar la versión de Master Data que satisface las necesidades de tu operación o que ya está en uso. Más información:</p>
+	<ul>
+    	<li><a href="https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versiones-disponibles">Características de las versiones de Master Data</a></li>
+    	<li><a href="https://developers.vtex.com/docs/guides/master-data-v2-basics">Master Data v2</a></li>
+	</ul>
+</div>
+
+## Tipos de datos
+
+Una entidad de datos se compone de campos que, a su vez, tienen un tipo. El tipo identifica las características de la información que se almacena en el campo y realiza validaciones, filtros y cálculos según el valor seleccionado.
+
+Al crear un campo puedes seleccionar cualquiera de los tipos que se describen a continuación:
+
+| Tipo de campo | Descripción |
+| - | - |
+| **Auto Increment** | Almacena números enteros y se incrementa automáticamente, es decir, con cada nuevo registro, este campo recibe el valor del registro anterior + 1. |
+| **Boolean** | Almacena información de valores booleanos, es decir, siempre se rellenará como `true` (verdadero) o `false` (falso). |
+| **CEP** | Almacena un CEP (código postal en Brasil). |
+| **CPF / CNPJ** | Almacena la información de CPF y CNPJ (identificación fiscal e identificación de persona jurídica en Brasil, respectivamente). |
+| **Currency** |  Almacena información en el formato de moneda. |
+| **Date** |  Almacena información sobre la fecha. |
+| **Date and Time** |  Almacena fecha y hora. |
+| **Decimal** |  Almacena números con la parte fraccionaria siempre configurada como 2. Es decir, este campo siempre almacena 2 dígitos como lugares decimales del valor ingresado. |
+| **Email** |  Almacena un email. |
+| **File** |  Almacena un archivo. Puedes definir el tamaño máximo en la configuración del campo que se muestra al hacer clic en el botón de engranaje <i class="fas fa-cog"></i>. |
+| **Integer** |  Almacena números enteros, es decir, números sin la parte fraccionaria. Almacena los números enteros entre `-2147483648` y `2147483647`. |
+| **Long** | Es el mismo tipo que **Integer**, pero con la posibilidad de almacenar más números. Almacena de `-2⁶³` a `2⁶³-1`. |
+| **Percent** | Almacena información en porcentajes. |
+| **Phone** |  Almacena información en formato de número de teléfono. |
+| **Relationship** | Crea una relación con otra entidad. Una relación es la información de una entidad que se muestra en otra entidad. Por ejemplo, si en una biblioteca deseamos que el nombre del **Cliente** se muestre en el registro de **Préstamo**, debemos crear una relación entre **Préstamo** y **Cliente** utilizando el campo **Nombre registrado en Préstamo**.<br><br>Para crearla, en la configuración del tipo **Relationship** primero debes seleccionar la entidad que deseas mostrar (**Cliente** en este caso) y luego el campo **Nombre**. |
+| **Score2** | Campo compuesto por clave, valor y validez. Un ejemplo de uso es el control de compra por cliente en cuyo caso se guardaría la cantidad comprada por el cliente y la cantidad de compras realizadas. Este campo se debe rellenar mediante el endpoint [Update scores](https://developers.vtex.com/docs/api-reference/masterdata-api#put-/api/dataentities/-acronym-/documents/-id-/score) o [Update score by field](https://developers.vtex.com/docs/api-reference/masterdata-api#put-/api/dataentities/-acronym-/documents/-id-/score/-field-name-) de [Master Data API v1](https://developers.vtex.com/docs/api-reference/masterdata-api). |
+| **Text** | Almacena números, letras y caracteres especiales. En este caso, no hay límite de caracteres. |
+| **Time** | Almacena información de hora. |
+| **URL** |  Almacena una URL. |
+| **User Login** | Selecciona automáticamente el usuario que tiene sesión iniciada. Se utiliza cuando se desea registrar el email del usuario que realiza una acción en un registro de entidad. |
+| **Varchar 10** | Almacena números, letras y caracteres especiales con un límite de 10 caracteres. |
+| **Varchar 100** | Almacena números, letras y caracteres especiales con un límite de 100 caracteres. |
+| **Varchar 50** | Almacena números, letras y caracteres especiales con un límite de 50 caracteres. |
+| **Varchar 750** | Almacena números, letras y caracteres especiales con un límite de 750 caracteres. |
+
+## Crear entidad de datos
+
+Sigue los pasos a continuación para configurar una nueva entidad de datos.
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En Master Data, haz clic en **Aplicaciones** > **Configuración avanzada** > **Estructura de datos**.
+3. Haz clic en la pestaña **Entidades de datos**.
+4. Haz clic en el botón `Agregar`.
+5. Rellena el campo **Acrónimo** con 2 letras que identifiquen la entidad de datos. Estas letras serán las iniciales del campo que identifica el registro. Ejemplo: para el acrónimo SP, el identificador es SP-0001.
+6. Rellena el **Nombre** de la entidad de datos que deseas crear.
+7. Selecciona el tipo de clave primaria, que puede ser una de las siguientes:
+
+   - **Generar identificador único universal (GUID)**: una secuencia de números y caracteres que no se repiten y que identifica un registro.
+   - **La clave primaria debe indicarse mediante la propiedad 'ID'**: no crea un campo identificador automáticamente. Este campo se debe crear manualmente y debe tener el nombre **ID**.
+8. Si es necesario consultar los registros sin filtro y sin autenticación, marca la opción **Permitir la consulta de todos los documentos sin filtro**. Atención: esta configuración es crítica, ya que permite listar todos los registros a través de API.
+9.  Rellena la pestaña **Campos** con los campos que deseas incluir en la nueva entidad de datos según los pasos a continuación.
+10. Rellena la columna **Nombre** con el valor de identificación del campo. No se admiten espacios ni caracteres especiales. Ejemplo: NombreDelCliente.
+11. Rellena la columna **Nombre para mostrar** con el nombre que se mostrará en el formulario. Ejemplo: Nombre del cliente.
+12. Selecciona el tipo de campo según las opciones descritas en la sección [Tipos de datos](#tipos-de-datos).
+13. Haz clic en el botón de engranaje <i class="fas fa-cog"></i> para abrir las opciones de configuración del campo.
+14. Completa la **Configuración general**.
+
+ 	- **¿Es anulable?**: marca esta opción si se puede crear o editar un registro con un campo en blanco (nulo). Si no se marca esta opción, no se podrá crear un registro con un campo sin valor.
+ 	- **Permitir la lectura sin credenciales:** marca esta opción si es posible leer los datos del campo sin necesidad de autenticación a través de Master Data API.
+ 	- **Permitir editar sin credenciales:** marca esta opción si es posible ingresar datos en el campo sin necesidad de autenticación a través de Master Data API.
+ 	- **Permitir filtrar credenciales:** marca esta opción si es posible filtrar datos del campo sin necesidad de autenticación a través de Master Data API.
+
+15. Completa la **Configuración de búsqueda y filtro**:
+
+	- **¿Es buscable?**: determina si el campo se utiliza para búsquedas en el formulario y por API.
+	- **¿Es filtrable?:** determina si el campo se utiliza para filtrar en el formulario y por API.
+16. Ingresa la descripción del campo.
+17. Para agregar más campos, haz clic en el botón `Nuevo campo` y repite los pasos 10 al 16.
+18. Después de definir los campos, haz clic en el botón `Guardar` para finalizar o `Guardar y crear` para continuar con la creación de una nueva entidad de datos.
+
+	Se te redirigirá de vuelta a la pestaña **Entidad de datos**.
+
+19. En la fila de la nueva entidad, haz clic en el botón de disquete <i class="fas fa-save"></i> para publicar la entidad de datos creada.
+20. Haz clic en `OK`.
+
+<div class="alert alert-info">
+	<p>Después de crear la entidad de datos, debes <a href="https://help.vtex.com/es/tutorial/creando-formulario-en-master-data--tutorials_1047">crear el formulario para agregar, editar y mostrar los datos en Master Data</a>.</p>
+</div>
diff --git a/docs/tutorials/es/data-subject-rights.md b/docs/tutorials/es/data-subject-rights.md
index bde9a70a9..ac8e0f693 100644
--- a/docs/tutorials/es/data-subject-rights.md
+++ b/docs/tutorials/es/data-subject-rights.md
@@ -3,8 +3,8 @@ title: 'Derechos de los titulares de datos personales'
 id: 6imchxTx09icupKMbzHVIM
 status: PUBLISHED
 createdAt: 2023-04-26T18:56:45.938Z
-updatedAt: 2023-04-27T12:43:48.560Z
-publishedAt: 2023-04-27T12:43:48.560Z
+updatedAt: 2023-06-22T21:47:26.569Z
+publishedAt: 2023-06-22T21:47:26.569Z
 firstPublishedAt: 2023-04-26T19:50:54.254Z
 contentType: tutorial
 productTeam: Others
@@ -50,7 +50,7 @@ Para exportar datos de Master Data v1 a través del dashboard del Admin, sigue l
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
 2. Haz clic en la pestaña **Applications**.
 3. Haz clic en el ícono de visualizar (derecha) de la entidad de datos deseada.
-![Master Data botón](https://images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/fe25569f2fe5847e02eefdd165c3f95e/visualizar_bot__o_master_data_EN.png)
+![Master Data botón](//images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/fe25569f2fe5847e02eefdd165c3f95e/visualizar_bot__o_master_data_EN.png)
 4. Utiliza el [filtro de Master Data v1](https://help.vtex.com/es/tutorial/filtering-data-on-master-data--tutorials_778) para obtener solo los datos del usuario deseado. Utiliza `email` o `User ID` como campo del filtro.
 5. Haz clic en el botón `Export XLS`.
 6. Selecciona la opción `Select all fields`.
diff --git a/docs/tutorials/es/database-maintenance-full-cleanup.md b/docs/tutorials/es/database-maintenance-full-cleanup.md
index 8787ca41b..e27ca8a86 100644
--- a/docs/tutorials/es/database-maintenance-full-cleanup.md
+++ b/docs/tutorials/es/database-maintenance-full-cleanup.md
@@ -3,8 +3,8 @@ title: 'Mantenimiento de Base de Datos (Full Cleanup)'
 id: 34P9LGs7BCIQK6acQom802
 status: PUBLISHED
 createdAt: 2018-02-07T14:32:22.879Z
-updatedAt: 2022-12-08T22:26:21.443Z
-publishedAt: 2022-12-08T22:26:21.443Z
+updatedAt: 2023-08-02T16:15:41.168Z
+publishedAt: 2023-08-02T16:15:41.168Z
 firstPublishedAt: 2018-02-07T16:44:48.971Z
 contentType: tutorial
 productTeam: Others
@@ -41,10 +41,6 @@ Estas son las operaciones disponibles:
 
 - __Eliminar Categorías, Tags, Campos e Ítems relacionados:__ al borrar categorías, marcas y campos, además de sus ítems relacionados, se eliminarán de forma definitiva de su tienda. Para que la exclusión se produzca, es necesario que antes se borren productos y SKU.
 
-  <div class="alert alert-info">
-    <p>Para los casos en los que se realice la operación <b>Eliminar Productos/SKU e ítems relacionados</b> o <b>Eliminar Categorías, Tags, Campos e Ítems relacionados</b> y la tienda utilice <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG"VTEX> Intelligent Search</a>, póngase en contacto con nuestro <a href="https://support.vtex.com/hc/es-419/requests">equipo de soporte</a> para realizar un mantenimiento completo de la base de datos.</p>
-  </div>
-
 - __Eliminar sellers e ítems relacionados:__ al borrar sus sellers, además de sus ítems relacionados, se eliminarán de forma definitiva de su tienda.
 
 - __Programar reindexación completa:__ al reindexar la base, usted entra en una fila para iniciar el proceso de indexación de sus productos. __Los productos de la tienda continúan disponibles para la venta durante el proceso de indexación__. Estos apenas entran en una fila para la actualización de datos y siguen disponibles en el sitio web para su venta. Atención: después de hacer clic en __Reindexar base__, el proceso se inicia automáticamente.
diff --git a/docs/tutorials/es/declining-order-cancelation.md b/docs/tutorials/es/declining-order-cancelation.md
new file mode 100644
index 000000000..486e3a06e
--- /dev/null
+++ b/docs/tutorials/es/declining-order-cancelation.md
@@ -0,0 +1,89 @@
+---
+title: 'Denegar solicitud de cancelación del pedido'
+id: F2n0h1TeQ5td540Gjyff4
+status: PUBLISHED
+createdAt: 2023-09-21T02:29:56.663Z
+updatedAt: 2024-04-01T15:47:27.833Z
+publishedAt: 2024-04-01T15:47:27.833Z
+firstPublishedAt: 2023-09-21T16:08:07.567Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: denegar-solicitud-de-cancelacion-del-pedido
+locale: es
+legacySlug: negacion-de-cancelacion-de-pedido
+subcategory: 2t00bBkcAwIkgSCGKsMOwY
+---
+
+Hay diversas situaciones en las que es necesario cancelar un pedido, ya sea por parte del seller, del marketplace o del cliente. Sin embargo, en algunos casos la cancelación de un pedido le acarrea al seller importantes pérdidas económicas, por lo que este tiene la posibilidad de denegar una solicitud de cancelación del pedido.
+
+En el flujo de pedidos hay un [periodo de cancelación](https://help.vtex.com/es/tutorial/order-flow-and-status--tutorials_196) (o periodo de gracia) en el que el cliente puede cancelar un pedido automáticamente. Excepto durante ese periodo, el seller puede denegar una solicitud de cancelación del pedido, independientemente de si ha sido realizada por el cliente o por el marketplace.
+
+> **Ejemplo:** un seller vende productos personalizables en un marketplace. Después de comprar un ítem, y una vez finalizado el periodo de cancelación, el cliente decide cancelar el pedido, para lo que se pone en contacto con el marketplace. Si el marketplace cancela el pedido, el seller tiene una pérdida financiera, ya que un producto personalizable difícilmente puede venderse a otro cliente, por lo que el seller opta por denegar la solicitud de cancelación.
+
+Para contenido para desarrolladores, consulte [Order canceling improvements](https://developers.vtex.com/docs/guides/order-canceling-improvements).
+
+<div class = "alert alert-info">
+En este artículo, los términos marketplace y seller se refieren a <a href="https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace">marketplace VTEX</a> y <a href="https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-seller">seller VTEX</a>. La funcionalidad de denegar solicitudes de cancelación de pedidos no está disponible para sellers o marketplaces externos.
+</div>
+
+<div class = "alert alert-warning">
+No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
+</div>
+
+## Diagrama de denegación de cancelación de pedidos
+
+En la siguiente imagen puedes consultar cómo se desarrolla la denegación de las solicitudes de cancelación del pedido, una vez finalizado el periodo de cancelación:
+
+![cancel_api_improvements_help_center_ES_v2](//images.ctfassets.net/alneenqid6w5/68eCO8cFvRz9NsvLaalNMe/716a0f4775bc8418b72578fd1e384130/cancel_api_improvements_help_center_ES_v2.png)
+
+La descripción de cada paso es la siguiente:
+
+1. El cliente se pone en contacto con el marketplace para cancelar un pedido o lo hace a través de [Mi cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
+2. El marketplace envía una solicitud de cancelación al seller. En este punto, el [status del pedido](https://help.vtex.com/es/tutorial/order-flow-and-status--tutorials_196) para el marketplace es `esperando decisión del seller`.
+3. Si el pedido se encuentra dentro del periodo de cancelación, se cancelará automáticamente, siendo este el comportamiento predeterminado de la plataforma. Los próximos pasos reflejan lo que ocurre cuando el periodo de cancelación ha terminado.
+4. El seller recibe la **Solicitud de cancelación** del pedido y decide si la acepta o no. Los próximos pasos informan lo que ocurre cuando el seller decide no cancelar el pedido.
+
+  <div class="alert alert-danger">
+Para denegar una solicitud de cancelación, el status del pedido para marketplace y seller deben ser los siguientes:
+<ul>
+<li><b>Status del marketplace:</b> esperando decisión del seller.</li>
+<li><b>Status del seller:</b> cancelación solicitada.</li>
+</ul>
+</div>
+
+5. El seller deniega la solicitud de cancelación del pedido y se lo notifica al marketplace.
+6. Una vez que el marketplace recibe la respuesta del seller, el pedido continúa su progresión en el flujo de pedidos.
+
+## Denegar solicitud de cancelación del pedido
+
+La solicitud de cancelación de un pedido puede realizarse por el marketplace o el propio cliente a través de **Mi cuenta.** Cuando se realiza directamente a través de [Mi cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), el cliente recibe un mensaje de confirmación de que la solicitud se ha enviado correctamente.
+
+Después, el [status del pedido](https://help.vtex.com/es/tutorial/order-flow-and-status--tutorials_196) se mostrará de la siguiente manera: `cancelación solicitada` para el marketplace y `esperando decisión del seller` para el seller, hasta que este tome una decisión, ya sea para aceptar o denegar la solicitud.
+
+<div class="alert alert-warning">
+Si en el plazo de 30 días el seller no toma ninguna acción respecto a la solicitud de cancelación del pedido, el pedido será cancelado automáticamente por la plataforma VTEX.
+</div>
+
+Para denegar una solicitud de cancelación del pedido a través del Admin VTEX, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, ve a **Pedidos > Todos los pedidos,** o ingresa [Todos los pedidos](https://help.vtex.com/es/tutorial/all-orders--2QTduKHAJMFIZ3BAsi6Pi) en la barra de búsqueda de la parte superior de la página.
+2. Selecciona el pedido deseado para acceder a la [página de información del pedido](https://help.vtex.com/es/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl).
+3. En la parte superior de la página, haz clic en `Denegar`.
+
+  ![deny cancel request](//images.ctfassets.net/alneenqid6w5/53kKd5oNkEjeziq9XR4yvO/19f9b7716df1f0e011b11850d3866e13/deny_cancel_request_ES.png)
+
+4. Ingresa en el campo Solicitud de cancelación el motivo por el que se deniega la solicitud de cancelación del pedido.
+
+  ![deny cancel request reason](//images.ctfassets.net/alneenqid6w5/1okkX2L4JdZ57qcdZ758O4/fae33faa395d0aa0c51b2cd645bbf2f8/deny_cancel_request_reason_ES.png)
+
+  <div class="alert alert-warning">
+Atención: el cliente puede recibir el mensaje que ingreses en este campo a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi cuenta</a> o a través del marketplace.
+</div>
+
+5. Haz clic en `Denegar`.
+
+Tras esta acción, se rechaza la solicitud de cancelación del pedido, y este continúa su progresión en el flujo de pedidos actualizándose al siguiente status:
+- **Para el marketplace:** `pago aprobado`.
+- **Para el seller:** `listo para preparación` o `preparando envío`, dependiendo de su status anterior a la solicitud de cancelación.
+
diff --git a/docs/tutorials/es/defining-mandatory-fields-in-master-data-v1-forms.md b/docs/tutorials/es/defining-mandatory-fields-in-master-data-v1-forms.md
new file mode 100644
index 000000000..4ca7bd805
--- /dev/null
+++ b/docs/tutorials/es/defining-mandatory-fields-in-master-data-v1-forms.md
@@ -0,0 +1,30 @@
+---
+title: 'Definir campos obligatorios en los formularios de Master Data v1'
+id: 3ufvQPc02Aybg7K1r1HADV
+status: PUBLISHED
+createdAt: 2022-10-17T19:47:22.675Z
+updatedAt: 2024-07-04T13:15:32.435Z
+publishedAt: 2024-07-04T13:15:32.435Z
+firstPublishedAt: 2022-10-17T19:50:55.489Z
+contentType: tutorial
+productTeam: Master Data
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: definir-campos-obligatorios-en-los-formularios-de-master-data-v1
+locale: es
+legacySlug: no-puedo-editar-un-campo-obligatorio-en-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+Para cambiar los campos que aparecen como obligatorios en el __Profile System__ de Master Data v1, siga los pasos que se indican a continuación:
+
+1. En el Admin VTEX, acceda **Configuración de la tienda** > **Storefront** > **Master Data**. 
+2. Asegúrate de que se encuentra en la pestaña __Aplicaciones__.
+3. Haz clic en el engranaje <i class="fas fa-cog"></i> en __Profile System__.
+4. Haz clic en el icono de edición <i class="far fa-edit"></i> situado junto al formulario que desea configurar.
+5. Haz clic en __Esquemas de layout__.
+6. Haz clic en el icono de edición <i class="far fa-edit"></i> en la línea del campo que desea configurar.
+7. En __Configuración avanzadas de campos__, seleccione __Campo obligatorio del formulario__.
+8. Haz clic en `OK`.
+9. Haz clic en `Guardar`.
+
+La opción puede cambiarse siempre que sea necesario.
diff --git a/docs/tutorials/es/defining-window-displays.md b/docs/tutorials/es/defining-window-displays.md
index ff3b7f976..deee3799a 100644
--- a/docs/tutorials/es/defining-window-displays.md
+++ b/docs/tutorials/es/defining-window-displays.md
@@ -27,7 +27,7 @@ Realizadas las debidas definiciones, el vínculo de la colección con la vitrina
 
 En el ejemplo abajo, vamos a definir la vitrina presentada en la Home, siendo así, se debe realizar la modificación en el siguiente layout:
 
-![cms_layout_home ](https://images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
+![cms_layout_home ](//images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
 
 En el layout seleccionado, agregue el control correspondiente a la vitrina en la que desea exhibir la colección haciendo clic en **Add object**.
 
@@ -35,19 +35,19 @@ Después de seleccionar el tipo de control deseado, defina su nombre y haga clic
 
 **No olvide guardar las configuraciones hechas en "Save Settings" para que pueda editar el control creado.**
 
-![ed](https://images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
+![ed](//images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
 
 ### Edición del control
 
 Para editar sus controles, haga clic en el **símbolo de lápiz**, como se muestra en la siguiente imagen de ejemplo:
 
-![banner_edit_cms](https://images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
+![banner_edit_cms](//images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
 
 Al editar el control es necesario agregar sus contenidos, que representan cada conjunto de ítems que será exhibido.
 Para eso, haga clic en **Add content**
 
-![cadastro_conteudo_cms ](https://images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
-![cadastro_conteudo_cms 2](https://images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
+![cadastro_conteudo_cms ](//images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
+![cadastro_conteudo_cms 2](//images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
 
 - **"Adicionar arquivo" (Agregar archivo):** para seleccionar la colección que aparecerá en ese contenido.
 - **Partner / Campaign / Source:** define la visualización de ese contenido si el visitante tiene alguna UTM correspondiente en su URL de origen.
@@ -63,7 +63,7 @@ Se debe marcar la opción **Active Content** y hacer clic en **Add content list*
 
 si el contenido necesita ser editado, basta con hacer clic en el segundo símbolo de lápiz como se muestra en la siguiente imagen:
 
-![edit_content_cms](https://images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
+![edit_content_cms](//images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
 
 Al realizar los cambios deseados, haga clic en **Update Content List** y guarda todas las configuraciones hechas haciendo clic en **Save Settings** después.
 
diff --git a/docs/tutorials/es/deleting-a-category.md b/docs/tutorials/es/deleting-a-category.md
index f26bffe6e..73375c2cc 100644
--- a/docs/tutorials/es/deleting-a-category.md
+++ b/docs/tutorials/es/deleting-a-category.md
@@ -26,7 +26,7 @@ Para que una categoría no les aparezca a los clientes de la tienda, puede inact
 3. Haga clic en la categoría que desea inactivar.
 4. Haga clic en el botón `Acciones`.
 5. Haga clic en `Editar`.
-6. Desmarque el campo __Activo | Categoría está activa en la tienda__, según se muestra en esta imagen: ![img inativarcategoria ES](https://images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/32994a6c1018db2d24e5acca0e2dcce0/img_inativarcategoria_ES.png)
+6. Desmarque el campo __Activo | Categoría está activa en la tienda__, según se muestra en esta imagen: ![img inativarcategoria ES](//images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/32994a6c1018db2d24e5acca0e2dcce0/img_inativarcategoria_ES.png)
 7. Haga clic en `Guardar`.
 
 ## Eliminar todas las categorías
diff --git a/docs/tutorials/es/deliveries-progress-vtex-shipping-network.md b/docs/tutorials/es/deliveries-progress-vtex-shipping-network.md
index 3e146e1db..0c63e3ced 100644
--- a/docs/tutorials/es/deliveries-progress-vtex-shipping-network.md
+++ b/docs/tutorials/es/deliveries-progress-vtex-shipping-network.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Progreso de las entregas'
 id: 5CZRA0lq60EecmwZpsjvfq
 status: PUBLISHED
 createdAt: 2022-03-04T13:12:38.617Z
-updatedAt: 2023-06-09T12:56:36.259Z
-publishedAt: 2023-06-09T12:56:36.259Z
+updatedAt: 2024-03-04T21:51:37.046Z
+publishedAt: 2024-03-04T21:51:37.046Z
 firstPublishedAt: 2022-03-04T13:17:13.380Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/detaching-skus-by-specification.md b/docs/tutorials/es/detaching-skus-by-specification.md
new file mode 100644
index 000000000..0d0048ea2
--- /dev/null
+++ b/docs/tutorials/es/detaching-skus-by-specification.md
@@ -0,0 +1,35 @@
+---
+title: 'Separar SKUs por especificación'
+id: 2q34xCKFuob941cOmz9Fx
+status: PUBLISHED
+createdAt: 2024-06-27T16:45:42.418Z
+updatedAt: 2024-06-27T16:47:01.429Z
+publishedAt: 2024-06-27T16:47:01.429Z
+firstPublishedAt: 2024-06-27T16:47:01.429Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: separar-skus-por-especificacion
+locale: es
+legacySlug: separar-skus-por-especificacion
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Una de las funcionalidades de VTEX Intelligent Search es la **separación de SKUs por especificación**. Este recurso permite que el administrador de la tienda determine los diferentes SKUs que se mostrarán en los resultados de búsqueda.
+
+Antes, solo los productos sin ninguna distinción entre sí se mostraban en los resultados de búsqueda. Por eso, se necesitaba registrar cada SKU como un producto único para mostrarlo de forma separada.
+
+Ahora, no se necesita realizar ningún cambio en el Catálogo para que los SKUs se muestren en los resultados de búsqueda. En el Admin, basta [configurar las especificaciones del SKU que desea mostrar en la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx). 
+
+Esta herramienta se recomienda, principalmente, para las tiendas de ropa, porque se puede mostrar los productos por color o material.  
+
+A continuación, vea un ejemplo de separación de SKUs por color. La sandalia que se destaca en la siguiente imagen se exhibe en dos colores en el resultado de la búsqueda:
+
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+
+<div class="alert alert-info"><p>
+Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.</p></div>
+
+## Configuración
+Para configurar los atributos que se usarán para separar los SKUs, acceda a nuestro artículo de [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
+
diff --git a/docs/tutorials/es/determine-the-minimum-number-of-items-in-a-cart.md b/docs/tutorials/es/determine-the-minimum-number-of-items-in-a-cart.md
index 2b1155137..03c048908 100644
--- a/docs/tutorials/es/determine-the-minimum-number-of-items-in-a-cart.md
+++ b/docs/tutorials/es/determine-the-minimum-number-of-items-in-a-cart.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Es posible determinar el mínimo de items en un carrito?'
 id: 3rhoZXYon6aaGqusgOwukQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:41.366Z
-updatedAt: 2023-03-30T15:55:10.926Z
-publishedAt: 2023-03-30T15:55:10.926Z
+updatedAt: 2024-02-05T18:20:53.788Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:19.953Z
 contentType: tutorial
 productTeam: Shopping
@@ -12,16 +12,15 @@ author: 7FpKZ0rc6k4WqeymES80cw
 slug: determinar-el-minimo-de-items-en-un-carrito
 locale: es
 legacySlug: determinar-el-minimo-de-items-en-un-carrito
-subcategory: 3tDGibM2tqMyqIyukqmmMw
+subcategory: 
 ---
 
-Sí. De forma predeterminada, la cantidad mínima de items en el carrito es de 1 item. Sin embargo, usted puede cambiar este valor y especificar el número que la tienda entiende como ideal para su negocio.
+De forma predeterminada, a cantidad mínima de ítems en el carrito es 1 artículo. Sin embargo, es posible cambiar este valor y especificar el número que la tienda cree que es ideal para su negocio.
 
-Si se cambia el número de 1 *(predeterminado)* a 2, esto impedirá que el cliente cierre la compra sin tener al menos 2 items en el carrito.
+Por ejemplo, si cambias el número de 1 *(predeterminado)* a 2, esto evitará que el cliente pueda completar la compra sin haber añadido al menos 2 ítems al carrito.
 
-__Para cambiar este número, siga los pasos abajo:__
+Para cambiar la cantidad mínima de ítems en el carrito, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Apps** > **Afiliados** > **Gestión de Pedidos**, o escribe **Gestión de Pedidos** en la barra de búsqueda en la parte superior de la página
-2. Haga clic en __Configuración__.
-3. Ajuste el valor del campo __Cantidad mínima de ítems en el carrito__.
-4. Haga clic en el botón __Salvar__.
+1. En el Admin de VTEX, acceda a __Configuración de Tienda > Pedidos > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __General__, sección __Carrito__, ajuste el valor del campo __Cantidad mínima de ítems en el carrito__ según lo desee.
+3. Haga clic en "Guardar".
diff --git a/docs/tutorials/es/direct-migration-magazine-luiza.md b/docs/tutorials/es/direct-migration-magazine-luiza.md
new file mode 100644
index 000000000..7d5dd2d0f
--- /dev/null
+++ b/docs/tutorials/es/direct-migration-magazine-luiza.md
@@ -0,0 +1,20 @@
+---
+title: 'Migración Directa Magazine Luiza'
+id: 6QRyRfi16YMVdPesThw3AA
+status: PUBLISHED
+createdAt: 2024-05-31T19:52:31.191Z
+updatedAt: 2024-05-31T21:02:13.878Z
+publishedAt: 2024-05-31T21:02:13.878Z
+firstPublishedAt: 2024-05-31T20:07:32.221Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: migracion-directa-magazine-luiza
+locale: es
+legacySlug: migracion-directa-magazine-luiza
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning">
+Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
+</div>
diff --git a/docs/tutorials/es/disable-cloudflare-proxy.md b/docs/tutorials/es/disable-cloudflare-proxy.md
index 6e275e8c2..6d0d3c171 100644
--- a/docs/tutorials/es/disable-cloudflare-proxy.md
+++ b/docs/tutorials/es/disable-cloudflare-proxy.md
@@ -21,7 +21,7 @@ Como consecuencia, el sitio web puede quedar fuera de línea. Si el dominio est
 
 Para desactivar el proxy de CloudFlare (y, en consecuencia, deshabilite los servicios CDN y WAF de CloudFlare), entra en tu cuenta de Cloudflare y haz clic en el botón **DNS**. En el __*panel DNS management*__, haz clic en el ícono de la nube naranja debajo de __*Proxy status*__ para cada entrada de DNS que debe apuntar a VTEX. 
 
-![Configuración de proxy de Cloudflare](https://images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/7b76e3396ed5b27b0c14ae76bb77b76a/DNS_Management.png)
+![Configuración de proxy de Cloudflare](//images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/7b76e3396ed5b27b0c14ae76bb77b76a/DNS_Management.png)
 
 Observa que si el proxy está activado, el ícono será de color naranja con el texto __*Proxied*__. De lo contrario, el ícono se mostrará en gris con el texto __*DNS Only*__.
 
diff --git a/docs/tutorials/es/displaying-the-store-in-another-language.md b/docs/tutorials/es/displaying-the-store-in-another-language.md
index da0645426..8ad9b7e5f 100644
--- a/docs/tutorials/es/displaying-the-store-in-another-language.md
+++ b/docs/tutorials/es/displaying-the-store-in-another-language.md
@@ -17,7 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 Para exhibir la tienda en otro idioma es necesario [crear una nueva Politica Comercial](/es/tutorial/configurar-politica-comercial-para-marketplace/) y relacionarla al idioma deseado por el campo __Culture Info__.
 
-![exibição-loja-idioma-diferente es](https://images.ctfassets.net/alneenqid6w5/38du9gVEQomS0Y2sGqMYeW/3abd36c8b8714cb4297c58680499ad62/exibi____o-loja-outra-l__ngua_es.png)
+![exibição-loja-idioma-diferente es](//images.ctfassets.net/alneenqid6w5/38du9gVEQomS0Y2sGqMYeW/3abd36c8b8714cb4297c58680499ad62/exibi____o-loja-outra-l__ngua_es.png)
 
 Desupués de configurar la política comercial, es necesario un tratamiento en el front-end de su tienda para que cambie el idioma y pronto cambie también la Politicas Comercial. 
 Para eso, es necesario configurar que cada cambio de idioma incluya en la URL el parámetro `?sc=iddelapolíticacomercial` reemplazando __iddelapolíticacomercial__ por el Id de la política comercial registrada que sea relacionada al idioma deseado.
diff --git a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
new file mode 100644
index 000000000..895c2533a
--- /dev/null
+++ b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -0,0 +1,84 @@
+---
+title: 'Mostrar anuncios de VTEX Ad Network en tu tienda (Beta)'
+id: 6gWgZrMLcS5FDFFdl5LETA
+status: CHANGED
+createdAt: 2024-04-23T18:51:12.785Z
+updatedAt: 2024-07-05T13:10:03.749Z
+publishedAt: 2024-07-05T13:05:44.686Z
+firstPublishedAt: 2024-04-23T19:13:52.053Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: mostrar-anuncios-de-vtex-ad-network-en-tu-tienda-beta
+locale: es
+legacySlug: mostrar-anuncios-de-vtex-ad-network-en-tu-tienda-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+[VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) les permite a los retailers VTEX disponibilizar espacio publicitario para que las marcas promocionen productos en tu tienda. VTEX seleccionará anuncios de productos que ya sean parte de tu catálogo y tu tienda recibirá una comisión por cada clic en los anuncios de tu storefront.
+
+Para unirte a VTEX Ad Network y publicar anuncios en tu tienda, solo tienes que instalar la aplicación VTEX Ad Network para retailers.
+
+<div class="alert alert-warning">
+Por el momento, los retailers VTEX solo pueden disponibilizar inventario de anuncios en storefronts creados con <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
+</div>
+
+## Seguimiento de los resultados
+
+En la pantalla de inicio de la aplicación [VTEX Ad Network para retailers](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#retailers), puedes dar seguimiento a los resultados de los anuncios en tu tienda.
+
+![vtex_ad_network_admin_ES](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/2bc7abac921ebb2cf334a5cdaf855e9a/vtex_ad_network_admin.png)
+
+En la parte superior se muestran los datos agregados:
+
+- **Gasto total en anuncios:** valor gastado por marcas en anuncios mostrados en tu tienda.
+- **Ventas por anuncios:** ingresos totales por ventas derivadas de anuncios mostrados en tu tienda.
+- **Ingresos:** valor total que tu tienda ha recibido gracias a los anuncios.
+
+A continuación se muestra una tabla con la información de cada una de las campañas que se han mostrado o podrían mostrarse en tu tienda:
+
+- **Duración:** duración de la campaña hasta la fecha.
+- **Impresiones:** número de veces que los anuncios recibieron impresiones en la página.
+- **Vistas:** número de veces en que los anuncios fueron realmente vistos. VTEX Ad Network cuenta una vista cuando hay una impresión del anuncio y, de ser necesario, el usuario desliza la página lo suficiente para ver el anuncio.
+- **Clics:** número de clics en anuncios.
+- **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
+- **Pedidos:** número de pedidos derivados de clics en anuncios.
+- **Unidades vendidas:** número de unidades de productos vendidas a partir de anuncios de esa campaña.
+- **Ventas por anuncios:** ingresos totales de ventas derivadas de anuncios mostrados en tu tienda.
+- **ROAS:** retorno de la inversión publicitaria de esa campaña en tu tienda.
+- **Presupuesto gastado:** presupuesto de la campaña gastado en tu tienda.
+
+También puedes utilizar los filtros disponibles en la parte superior de la tabla:
+
+- **Buscar campaña:** filtra las campañas por nombre.
+- **Status:** selecciona si deseas ver solo las campañas activas o inactivas.
+- **Anunciante:** selecciona ver los datos de las campañas de un anunciante específico.
+
+### Ver más detalles por campaña y producto
+
+En la tabla de la pantalla principal de la aplicación [VTEX Ad Network para retailers](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#retailers) también puedes hacer clic en la fila de una campaña para ver detalles más específicos.
+
+![vtex_ad_network_details_ES](//images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/f46649cbecca07932a31eaf0216ccb82/vtex_ad_network_details.png)
+
+- **Vistas/Clics:** vistas y clics en anuncios.
+- **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
+- **Presupuesto gastado:** valor gastado hasta la fecha.
+- **ROAS:** retorno de inversión publicitaria.
+- **Ingresos:** ingresos por ventas derivadas de anuncios.
+
+Debajo de los datos agregados, hay una tabla con la información del desempeño de cada producto en esa campaña:
+
+- **CPC:** costo por clic. Este es el valor pagado por el anunciante por cada clic en un anuncio.
+- **Impresiones:** número de veces que los anuncios recibieron impresiones en la página.
+- **Vistas:** número de veces en que los anuncios fueron realmente vistos. VTEX Ad Network cuenta una vista cuando hay una impresión del anuncio y, de ser necesario, el usuario desliza la página lo suficiente para verlo.
+- **Clics:** número de clics en anuncios.
+- **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
+- **Pedidos:** número de pedidos derivados de clics en anuncios.
+- **Unidades vendidas:** número de unidades del producto vendidas a partir de anuncios de esta campaña.
+- **Ventas por anuncios:** ingresos totales por ventas de ese producto derivadas de anuncios.
+- **ROAS:** retorno de inversión publicitaria.
+- **Presupuesto gastado:** presupuesto de la campaña gastado en ese producto en tu tienda.
diff --git a/docs/tutorials/es/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md b/docs/tutorials/es/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
new file mode 100644
index 000000000..3308eca69
--- /dev/null
+++ b/docs/tutorials/es/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
@@ -0,0 +1,40 @@
+---
+title: 'DPAN y FPAN: comprender la seguridad en el flujo de pagos tokenizados online'
+id: 3RM7RvhKZ057wja5xVEOqb
+status: PUBLISHED
+createdAt: 2023-06-19T16:55:51.107Z
+updatedAt: 2023-06-26T13:27:44.965Z
+publishedAt: 2023-06-26T13:27:44.965Z
+firstPublishedAt: 2023-06-19T17:10:43.124Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: dpan-y-fpan-comprender-la-seguridad-en-el-flujo-de-pagos-tokenizados-online
+locale: es
+legacySlug: dpan-y-fpan-comprender-la-seguridad-en-el-flujo-de-pagos-tokenizados-online
+subcategory: 
+---
+
+Un token es una representación digital de un activo físico que tiene valor comercial. En el contexto de los pagos, la tokenización es un procedimiento de seguridad que permite proteger la información sensible de los clientes durante las transacciones con tarjeta de crédito o débito o cartera digital, como Apple Pay, Google Pay y Samsung Pay.
+
+En primer lugar, es necesario comprender la siguiente información relacionada con las tarjetas:
+
+- **PAN (Primary Account Number)**: número físico impreso en el anverso o reverso de una tarjeta de débito o crédito, utilizado para identificar al titular de la cuenta y a su entidad financiera emisora. Contiene entre 14 y 19 dígitos.
+
+- **DPAN (Device Primary Account Number)**: versión tokenizada del PAN, utilizada en pagos por dispositivos móviles o carteras digitales. Este número está vinculado al dispositivo móvil del usuario (smartphone, smartwatch, tablet) y a la cuenta del titular de la tarjeta. 
+
+- **FPAN (Funding Primary Account Number)**: identificación de la cuenta en la que se cargará el importe en una operación de pago. Se utiliza exclusivamente cuando la compra se realiza a través de carteras digitales o servicios que permitan elegir más de un medio de pago al mismo tiempo, como pagar con diferentes tarjetas de crédito o débito o cuentas bancarias.
+
+A continuación, se muestra un ejemplo de flujo de pago utilizando tokens:
+
+1. El cliente introduce la información de la tarjeta en un sitio web, una aplicación o en un datáfono, o utiliza una cartera digital como medio de pago en una compra.
+
+2. El proveedor de pagos o el sistema de la cartera digital realiza una petición a la entidad financiera que emitió la tarjeta, solicitando la creación de un token que represente el PAN.
+
+3. El banco genera el token (DPAN) y lo envía al proveedor de pagos o al sistema de la cartera digital. El PAN solo queda registrado en el sistema del banco.
+
+4. Durante el procesamiento de la transacción, el proveedor de pagos envía el DPAN al banco, solicitando la autorización de la transacción. Cuando sea el caso, también se genera y envía el FPAN para la autorización de la transacción.
+
+5. El banco comprueba el vínculo existente entre el DPAN y el PAN, y autoriza el pago. En caso de que se utilice FPAN, el banco también comprobará que el FPAN es válido y que la fuente de financiación (cuenta) tiene saldo suficiente antes de autorizar el pago. 
+
+6. La transacción se completa y el administrador de la tienda recibe la confirmación del pago. Los datos físicos de la tarjeta (PAN) no se comparten ni con el administrador de la tienda ni con terceros, lo que reduce el riesgo de fraudes.
diff --git a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
new file mode 100644
index 000000000..5a9705909
--- /dev/null
+++ b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
@@ -0,0 +1,78 @@
+---
+title: 'Relevancia dinámica en Intelligent Search (beta)'
+id: rFaW7JPnBKNDBFzMxpBn8
+status: PUBLISHED
+createdAt: 2023-09-01T17:14:43.241Z
+updatedAt: 2024-01-05T17:24:55.378Z
+publishedAt: 2024-01-05T17:24:55.378Z
+firstPublishedAt: 2023-09-01T18:59:54.853Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: relevancia-dinamica-en-intelligent-search-beta
+locale: es
+legacySlug: relevancia-dinamica-en-intelligent-search-beta
+subcategory: 23WdCYqmn2V2Z7SDlc14DF
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>.</p>
+  <p>Para los clientes seleccionados, la funcionalidad está disponible para su uso gratuito en VTEX Admin durante su período Beta, o hasta que lo decida VTEX. Es posible que en el futuro se apliquen tarifas adicionales.</p>
+</div>
+
+Intelligent Search es una solución de búsqueda de la plataforma VTEX que, de forma sencilla e intuitiva, devuelve resultados relevantes basados en el catálogo desde la primera interacción del usuario con la tienda, ya sea a través de la barra de búsqueda, al navegar por las categorías o incluso a través de las vitrinas de productos. 
+
+La relevancia es la funcionalidad que define el orden de los productos en los resultados de la búsqueda. Esta configuración permite asignar pesos y dar prioridad a determinados criterios, como la popularidad, la fecha de lanzamiento del producto y la participación en promociones. Intelligent Search determina la relevancia de cada producto mediante la combinación de pesos y prioridades definidas por cada administrador de la tienda.
+
+En Intelligent Search, hay dos formas de configurar la relevancia de búsqueda:
+
+* [Manual](#manual)
+* [Dinámica](#dinamica)
+
+Solamente una de ellas se aplica a tu tienda por vez, pero puedes [cambiar el tipo de relevancia](#cambiar-el-tipo-de-relevancia) configurado. Si cambias la relevancia manual a dinámica, todas las reglas manuales ya registradas se seguirán guardando.
+
+<div class = "alert alert-info">
+La relevancia manual está configurada como predeterminada en la tienda.
+</div>
+
+## Manual 
+
+La relevancia manual se configura distribuyendo los pesos en la página **Reglas de relevancia**. Para activar la Relevancia manual, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, accede a **Storefront > Intelligent Search >** **Reglas de relevancia**  o ingresa **Reglas de relevancia** en la barra de búsqueda de la parte superior de la página.
+2. Selecciona la opción **Relevancia manual**.
+![relevancia-manual-es](//images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/eedc0f4e7adac60ba0e457a525c5e642/image.png)
+3. Haz clic en `Guardar`.
+
+Para configurar la relevancia manual, consulta el artículo [Relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+## Dinámica
+
+La relevancia dinámica es una funcionalidad de VTEX que utiliza inteligencia artificial para encontrar tendencias en el comportamiento de tus usuarios, basándose en sus búsquedas y en la posición del resultado en el que hacen clic o realizan un pedido. Esta funcionalidad puede mejorar los resultados de las búsquedas incrementando la relevancia de los productos cuya popularidad va en aumento. 
+
+Por ejemplo, en una página de últimas novedades, la relevancia dinámica puede identificar qué productos más recientes aumentan la conversión sin necesidad de que el administrador de la tienda realice ninguna configuración.
+
+También puede reposicionar los resultados que no sean relevantes para tus usuarios en el contexto de una búsqueda específica.
+
+Para activar la relevancia dinámica, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Storefront > Intelligent Search > Reglas de relevancia**  o ingresa **Reglas de relevancia** en la barra de búsqueda de la parte superior de la página.
+2. Lee la información sobre relevancia dinámica y haz clic en `Siguiente`.
+3. Selecciona la opción **Relevancia dinámica**.
+![relevancia-dinamica-es](//images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/d4b2d75e6d45e40ddd06bc9cf1332bcc/image.png)
+4. Haz clic en `Guardar`.
+5. Espera a que la barra de progreso alcance el 100 %. Este proceso puede demorar algunas horas, pero recibirás un email cuando haya finalizado.
+6. Haz clic en `Activar`.
+
+## Cambiar el tipo de relevancia
+
+Para cambiar el tipo de relevancia sigue los pasos a continuación:
+
+<div class = "alert alert-warning">
+No recomendamos cambiar constantemente el tipo de relevancia que utiliza tu tienda. El sistema necesita una semana para asentarse.
+</div>
+
+1. En el Admin VTEX, accede a **Storefront > Intelligent Search > Reglas de relevancia**  o ingresa **Reglas de relevancia** en la barra de búsqueda de la parte superior de la página.
+2. Haz clic en `Cambiar`.
+3. Selecciona el tipo de relevancia que deseas aplicar.
+4. Haz clic en `Guardar`.
diff --git a/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md b/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md
index a10fad94b..919d3099f 100644
--- a/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md
+++ b/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md
@@ -1,10 +1,10 @@
 ---
-title: 'Edite un campo obligatório en Profile System de Master Data'
+title: 'Editar un campo obligatório en Profile System de Master Data'
 id: 3Kat18isG7ZQptlLusUKnj
 status: PUBLISHED
 createdAt: 2019-03-29T14:18:37.284Z
-updatedAt: 2023-03-28T23:00:24.414Z
-publishedAt: 2023-03-28T23:00:24.414Z
+updatedAt: 2024-06-19T14:27:27.495Z
+publishedAt: 2024-06-19T14:27:27.495Z
 firstPublishedAt: 2019-03-29T15:48:22.604Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: edite-un-campo-obligatorio-en-profile-system-de-master-data
 subcategory: 42hDtnYXHw5ExG6l19RP1l
 ---
 
-El Master Data es un módulo dentro de la plataforma VTEX utilizado para almacenar y organizar los datos de los clientes. Vea cómo editar un campo, haciéndolo obligatorio o no, utilizando la funcionalidad Profile System.
+El Master Data es un módulo de la plataforma VTEX utilizado para almacenar y organizar documentos. Descubre cómo hacer obligatorio un campo de formulario en Master Data en las instrucciones que aparecen a continuación.
 
 <div class="alert alert-warning">
 Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
@@ -33,16 +33,16 @@ Master Data v2
 </ul>
 </div>
 
-Para seleccionar un campo para rellenar que desee que sea obligatorio, siga los pasos que se indican a continuación:
+Los siguientes pasos te permitirán seleccionar un campo y hacerlo obligatorio:
 
-1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**. 
-2. Asegúrese de que se encuentra en la pestaña Aplicaciones, dentro de __ Links Rápidos__.
-3. Haga clic en el __engranaje__ en __Profile System__. ![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
-4. Haga clic en el __lápiz__ al lado del ítem que desea configurar. ![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
-5. Haga clic en __Schemas de Layout__.
-6. En la __Sección 1__, escoja el ítem del campo que desea configurar.
-7. En __Configuraciones avanzadas del campo__, seleccione __Campo obligatorio__ en el formulario. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
-8. Haga clic en __ok__.
-
-Listo. A partir de ahora, necesitará rellenarse obligatoriamente las opciones seleccionadas en la tienda. La opción también puede modificarse siempre que lo desee. 
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**. 
+2. Asegúrate de que se encuentra en la pestaña __Aplicaciones__.
+3. Haz clic en el engranaje <i class="fas fa-cog"></i> en __Profile System__.
+4. Haz clic en el lápiz <i class="fas fa-edit"></i> al lado del ítem que desea configurar.
+5. Haz clic en __Esquemas de layout__.
+6. Dentro de una de las secciones del formulario, busca el campo que desea configurar y haz clic en <i class="fas fa-edit"></i> junto a él para abrir la __Configuración avanzada de campos__.
+7. En __Configuración avanzada de campos__, selecciona __Campo obligatorio del formulario__.
+8. Haz clic en `OK`.
+9. Haz clic en `Guardar`.
 
+A partir de ahora, las opciones seleccionadas serán obligatorias en el formulario. Los ajustes anteriores pueden modificarse si es necesario.
diff --git a/docs/tutorials/es/enable-checkout-v6.md b/docs/tutorials/es/enable-checkout-v6.md
index 316ca1c90..5176f1f42 100644
--- a/docs/tutorials/es/enable-checkout-v6.md
+++ b/docs/tutorials/es/enable-checkout-v6.md
@@ -28,7 +28,7 @@ Para actualizar el checkout de su tienda a la última versión (Checkout v6), de
 5. Haga clic en __Guardar__. 
 6. [Acceda a su tienda en ambiente beta](/tutorial/acceder-al-ambiente-beta--3BHM289568gcSwk2O80Asu) y haga los ajustes de estilo necesarios. El Checkout v6 posee nuevas clases _CSS_ que debem ser llevadas en consideración para personalización del estilo.
 
-![Checkoutv6_box](https://images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/dbef571b8ec2baed5bbc8546effaed82/CheckoutV6_box_ES.png)
+![Checkoutv6_box](//images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/dbef571b8ec2baed5bbc8546effaed82/CheckoutV6_box_ES.png)
 
 ## Activar el Checkout v6 en Ambiente de Producción
 
@@ -42,7 +42,7 @@ Después de realizar los ajustes necesarios en el ambiente de prueba, puede inic
 
 Después de este paso, el Checkout v6 estará instalado en su tienda.
 
-![checkoutv6_box_2](https://images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/a3606a1f0b82a825c4625e19c83086de/CheckoutV6_box2_ES.png)
+![checkoutv6_box_2](//images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/a3606a1f0b82a825c4625e19c83086de/CheckoutV6_box2_ES.png)
 
 ## ¿Cómo verificar si el Checkout v6 fue instalado correctamente?
 
diff --git a/docs/tutorials/es/enabling-2-factor-authentication-login.md b/docs/tutorials/es/enabling-2-factor-authentication-login.md
index 9d3693263..688de1d50 100644
--- a/docs/tutorials/es/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/es/enabling-2-factor-authentication-login.md
@@ -3,8 +3,8 @@ title: 'Habilitar inicio de sesión por autenticación de dos factores'
 id: 4Ae1fcQi12g8u4SkQKCqWQ
 status: PUBLISHED
 createdAt: 2017-11-09T00:46:29.023Z
-updatedAt: 2023-02-08T14:28:53.895Z
-publishedAt: 2023-02-08T14:28:53.895Z
+updatedAt: 2024-03-12T17:52:28.500Z
+publishedAt: 2024-03-12T17:52:28.500Z
 firstPublishedAt: 2017-11-09T13:09:54.237Z
 contentType: tutorial
 productTeam: Identity
@@ -17,8 +17,6 @@ subcategory: 4sY1T2qdFehvVmC0tL5xW3
 
 La autenticación de dos fatores (2FA) es un método de verificación que aumenta en gran medida la seguridad del inicio de sesión de su tienda. 
 
-![ES- LoginAdmin](https://images.ctfassets.net/alneenqid6w5/3elCQzyG1TLdPwoFjgkW6u/6472c560259c581f731f9d55ffa1d4c8/ES-_LoginAdmin.png)
-
 Esto porque, en el inicio de sesión, el sistema además de exigir el email y la contraseña exige una clave de acceso (en el caso de VTEX, esta puede ser un código enviado por SMS o generado por aplicación).
 
 Como esa clave se genera durante el inicio de sesión y tiene una validez corta, se vuelve casi imposible que alguien acceda a su tienda utilizando sus datos sin autorización. Sin 2FA, si alguien tiene su email y contraseña puede tener un acceso amplio a la cuenta de su tienda.
@@ -36,7 +34,7 @@ Existen dos opciones de autenticación, a través de:
 - Clave generada por una __aplicación__ de autenticación.
 - Clave enviada por mensaje de celular (__SMS__).
 
-![2FA - Select - ES](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
+![2FA - Select - ES](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
 
 <div class="alert alert-danger">
 Recomendamos enfáticamente que <strong>elija la opción de autenticación por aplicación</strong>, toda vez que en la autenticación por SMS usted depende de que no haya fallas en el servicio de su operador de telefonía. A través de la aplicación, la clave de acceso siempre estará disponible cuando sea necesaria.
@@ -51,17 +49,17 @@ Si configuró 2FA por SMS y el código está tardando en llegar, posiblemente es
 Para utilizar una clave generada a través de la aplicación de autenticación:
 1. Descargue la aplicación **Google Autenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)). 
 
-![2FA - App Download - ES](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
+![2FA - App Download - ES](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
 
 2. Utilice la aplicación para leer el código QR a través de la cámara del celular.
 
-![mfa código](https://images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/d930110f1a75a7cdb78f8650e0771df8/mfa_qr_code_correction_es.jpg)
+![mfa código](//images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/d930110f1a75a7cdb78f8650e0771df8/mfa_qr_code_correction_es.jpg)
 
 3. Su cuenta VTEX se agregará a la aplicación, que generará un código de 6 dígitos. Ingrese ese código para finalizar su inicio de sesión.
 
   *El código de la app se actualiza periódicamente. No es necesario que lo memorice, solo debe consultar la aplicación cuando lo necesite.*
 
-![2FA - App Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
+![2FA - App Insert Code - ES](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
 
 <div class="alert alert-info">
 Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso <strong> cada 3 días</strong>. Cuando eso suceda, basta con consultar el código en la aplicación.
@@ -73,11 +71,11 @@ Para utilizar una clave enviada a través de mensaje de texto:
 
 1. Ingrese su número de celular para que le enviemos el código por SMS, no olvide colocar el código de país y área. 
 
-![2FA - SMS Insert Phone - ES](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
+![2FA - SMS Insert Phone - ES](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
 
 2. Usted recibirá un mensaje de texto de VTEX en el celular indicado. Ingrese la clave de 6 dígitos para finalizar su inicio de sesión.
 
-![2FA - SMS Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
+![2FA - SMS Insert Code - ES](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
 
 <div class="alert alert-warning">
 No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o <a href="#habilitar-o-2fa-por-aplicativo">habilitar 2FA a través de la aplicación</a>.
@@ -93,11 +91,11 @@ Para modificar la configuración de la verificación en dos etapas:
 
 1. Acceda a su configuración de usuario, haciendo clic en el círculo con sus iniciales en el lado superior derecho del Admin. 
 
-![2FA - User Initials - ES](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
+![2FA - User Initials - ES](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
 
 2. Haga clic en **Verificación en 2 pasos** para ver su configuración.
 
-![2FA - My User - ES](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
+![2FA - My User - ES](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
 
 3. Usted también puede modificar su configuración siguiendo pasos similares a los anteriores para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) y por [aplicación](#habilitar-o-2fa-por-aplicativo).
 
diff --git a/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
index eea6f0ee6..0714f394e 100644
--- a/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Añadir soporte a 3DS2 en la integración con Redsýs V2'
 id: 1ixji2XORg9p0UoW8gBtUG
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-08T14:53:08.780Z
-updatedAt: 2023-03-23T15:42:17.139Z
-publishedAt: 2023-03-23T15:42:17.139Z
+updatedAt: 2024-03-18T19:54:47.084Z
+publishedAt: 
 firstPublishedAt: 2021-03-08T16:29:32.443Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: anadir-soporte-a-3ds2-en-la-integracion-con-redsys-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 La funcionalidad 3DS2 ahora está disponible también para pagos realizados con tarjeta de crédito y procesados a través del *gateway* de pagos [Redsýs](https://help.vtex.com/pt/tutorial/configurar-gateway-redsys--7xRnMyzZS0kQoIG2ISagY8).
 
 3DS2 es una solución de seguridad que permite autenticar al comprador en el banco emisor, lo que garantiza aún más seguridad para sus transacciones en línea.
@@ -33,6 +35,6 @@ En este tutorial, le explicaremos cómo realizar esta integración a través del
 4. Desplácese hacia abajo y active la opción __3DS Enabled__. 
 5. Haga clic en __Salva__.
 
-![RedsysV2 ES](https://images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/6e85fe90224d28365930fe21c4c673aa/Redsys_3DS2_-_ES.png)
+![RedsysV2 ES](//images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/6e85fe90224d28365930fe21c4c673aa/Redsys_3DS2_-_ES.png)
 
 Una vez hecho esto, la solución se habilitará para las transacciones con tarjeta de crédito de Redsýs.
diff --git a/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
index df836ef06..11d88b787 100644
--- a/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -77,7 +77,7 @@ Deberás seleccionar un vendedor de la tienda en la que quieras probar Venta en
 1. Tras [seleccionar un vendedor](https://help.vtex.com/es/tutorial/vendedores-instore-beta--4rzit1pzp28km4HSDEdrEC), accede a Sales App e inicia sesión.
 2. Busca un ítem que exista en el almacén de la cuenta franquicia registrada. Este ítem debe mostrar la cantidad disponible correspondiente en el stock del seller.
 
-![instore-pdp-es](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/b2feab0b2eb3c3893ed654801743e5cd/image.png)
+![instore-pdp-es](//images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/b2feab0b2eb3c3893ed654801743e5cd/image.png)
 
 <div class="alert alert-info">
 <p>Si has habilitado el stock infinito, el número mostrado será superior a 1 millón de ítems y no cambiará cuando se complete una venta.</p>
@@ -92,9 +92,9 @@ También puedes configurar la Venta en mano para ignorar la cantidad de ítems e
 2. Haz clic en el botón del engranaje <i class="fas fa-cog"></i> para editar.
 3. Selecciona la pestaña **Código**.
 4. En la pestaña lateral, selecciona `checkout-instore-custom-js`.
-![instore-custom-js-es](https://images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/50b77b80f4cba77048ea3454cda557bc/image.png)
+![instore-custom-js-es](//images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/50b77b80f4cba77048ea3454cda557bc/image.png)
 5. En la clave `window.INSTORE_CONFIG`, agrega la flag `venderSinStockEnMano: true`.
-![sellWithoutStockInHands-es](https://images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/d4f24d0e6eef4783be120f6533c3a6f0/image.png)
+![sellWithoutStockInHands-es](//images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/d4f24d0e6eef4783be120f6533c3a6f0/image.png)
 6. Haz clic en <i class="fas fa-save"></i> `Guardar`.
 
 ### Habilitar la venta con carrito mixto (opcional)
diff --git a/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md b/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md
index f6e49d082..09bcb2249 100644
--- a/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md
+++ b/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md
@@ -17,7 +17,7 @@ subcategory: 7ogirQ8NClawO2X6xdgCKc
 
 Todas las tiendas VTEX IO disponen de forma nativa de una Progressive Web App (PWA). Una PWA es un tipo de aplicación web que se utiliza para promover de forma nativa recursos beneficiosos para los usuarios, como funcionalidades offline o un ícono en la pantalla de inicio.
 
-![pwa-noticees](https://images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/85250a88ec6b95a39839de71dfdf60ef/Screenshot_162.png)
+![pwa-noticees](//images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/85250a88ec6b95a39839de71dfdf60ef/Screenshot_162.png)
 
 La PWA puede estar disponible para instalación en tres momentos distintos de la experiencia de navegación del usuario: durante la primera visita al sitio web de su tienda, al añadir el primer ítem al carrito o al finalizar la primera compra.
 Vea cómo configurar la notificación en su tienda siguiendo los pasos a continuación.
diff --git a/docs/tutorials/es/entering-tax-receipts-in-the-order.md b/docs/tutorials/es/entering-tax-receipts-in-the-order.md
index 1363efdd2..7a0130794 100644
--- a/docs/tutorials/es/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/es/entering-tax-receipts-in-the-order.md
@@ -19,7 +19,7 @@ Ese es el procedimiento después del manejo del pedido: la creación de la nota
 
 Para hacerlo manualmente por **Gestión de pedidos**, basta hacer clic en el botón `Facturar Paqueta`, como en la imagen abajo.
 
-![faturar-pedido-ex es](https://images.ctfassets.net/alneenqid6w5/3JeHgjEDtmm4ksSwamsW2W/d49ebe8fa3ea9e920e8d52f530182895/ex_1_es.png)
+![faturar-pedido-ex es](//images.ctfassets.net/alneenqid6w5/3JeHgjEDtmm4ksSwamsW2W/d49ebe8fa3ea9e920e8d52f530182895/ex_1_es.png)
 
 Con la inserción de la nota fiscal con el valor completo del pedido, él pasará para el status **Facturado.**
 
diff --git a/docs/tutorials/es/erasing-customer-data.md b/docs/tutorials/es/erasing-customer-data.md
new file mode 100644
index 000000000..a3014b65d
--- /dev/null
+++ b/docs/tutorials/es/erasing-customer-data.md
@@ -0,0 +1,66 @@
+---
+title: 'Eliminación de los datos de clientes'
+id: 1R9Fn7A06Ifj4R9YD4JTKU
+status: PUBLISHED
+createdAt: 2022-04-14T13:28:53.209Z
+updatedAt: 2023-06-23T15:06:52.315Z
+publishedAt: 2023-06-23T15:06:52.315Z
+firstPublishedAt: 2022-04-14T13:50:08.688Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: eliminacion-de-los-datos-de-clientes
+locale: es
+legacySlug: eliminacion-de-los-datos-de-clientes
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+Según las normas de protección de datos como [LGPD y RGPR] (https://vtex.com/us-en/privacy-and-agreements/vtex-commitment/), las empresas que utilizan datos personales de sus clientes deben aceptar sus solicitudes de eliminación del registro. Por lo tanto, VTEX te permite solicitar la eliminación de datos de los clientes de tu tienda.
+
+## Antes de solicitar la eliminación de datos
+
+Antes de [solicitar la eliminación a través del soporte](#pedir-eliminacion-via-soporte), es importante que compruebes qué entidades de Master Data almacenan datos de clientes en tu operación.
+
+Debes tener cuidado de no eliminar ningún dato de las [entidades nativas de Master Data](#entidades-nativas-de-master-data). Sin embargo, debes eliminar manualmente la información del cliente en [otras entidades de Master Data](#otras-entidades-de-datos), en caso de que tu tienda tenga alguna. Puedes encontrar más detalles a continuación.
+
+### Entidades nativas de Master Data
+
+Con tu [solicitud vía soporte](#pedir-eliminacion-via-soporte), VTEX eliminará los datos de las entidades de datos nativas **CL** y **AD**. Es importante que no elimines los datos de estas entidades.
+
+### Otras entidades de datos
+
+Si tu tienda almacena la información de los clientes en otras entidades de datos, debes eliminar manualmente estos datos antes de hacer una solicitud a través del soporte. Para ello, utiliza la API de Master Data:
+
+1. Busca el documento con el endpoint [Search document](https://developers.vtex.com/vtex-rest-api/reference/searchdocuments-1)
+
+2. Utiliza el request [Delete document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1)
+
+<div class="alert alert-danger">
+No realices este proceso para las entidades <b>CL</b> y <b>AD</b>. 
+</div>
+
+## Pedir eliminación vía soporte
+
+Deberás solicitar la extensión de la eliminación de los datos personales de tus clientes en los sistemas de VTEX mediante la apertura de un ticket en nuestro [Soporte VTEX](https://help.vtex.com/es/support).
+
+Para solicitar la eliminación de los datos personales de clientes, sigue los pasos a continuación:
+
+1. Accede a [Soporte VTEX](https://help.vtex.com/es/support).
+2. Ingresa tu nombre completo en el campo **Nombre** y selecciona en el campo **Tienda** el nombre de la tienda para la cual deseas abrir el ticket.
+3. Haz clic en la opción `Continuar`.
+4. Selecciona la opción `Técnico`.
+5. En el campo **Tipo de problema**, selecciona la opción `Quiero solicitar una configuración`.
+6. En el campo **Asunto de la solicitud**, deberás rellenar la siguiente información:
+   * Solicitud de Data Subject Request
+   * Cuentas VTEX
+   * Email vinculado a las cuentas VTEX cuyos datos deben eliminarse
+7. En el campo **Tu experiencia con la plataforma**, selecciona la opción correspondiente a tu experiencia como usuario de la plataforma VTEX.
+8. Rellena el campo **Describe en detalle lo sucedido** con los detalles de tu solicitud.
+9. Haz clic en `Enviar`.
+
+<div class="alert alert-warning">
+Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará. 
+</div>
+
+La solicitud se enviará a nuestro equipo de soporte. Al cerrar el ticket, se emitirá un certificado que se enviará al email relacionado con la cuenta por la cual se abrió el ticket para comprobar que realmente se eliminaron los datos.
+
diff --git a/docs/tutorials/es/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md b/docs/tutorials/es/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
new file mode 100644
index 000000000..6c4829715
--- /dev/null
+++ b/docs/tutorials/es/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
@@ -0,0 +1,40 @@
+---
+title: 'Error al intentar importar SKUs vía plantilla en el Admin VTEX'
+id: 1TDF87s7P1UJT1hNDGZsuk
+status: PUBLISHED
+createdAt: 2024-07-01T15:07:50.982Z
+updatedAt: 2024-07-22T18:56:05.856Z
+publishedAt: 2024-07-22T18:56:05.856Z
+firstPublishedAt: 2024-07-01T18:24:23.096Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: error-al-intentar-importar-skus-via-plantilla-en-el-admin-vtex
+locale: es
+legacySlug: error-al-intentar-importar-skus-via-plantilla-en-el-admin-vtex
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Product tags:** *Catalog, SKU*
+
+**Keywords:** *catálogo, sku, plantilla, importación*
+
+Después de definir el árbol de categorías y el registro de [especificaciones de productos y SKUs] en tu tienda, es necesario rellenar los valores de las especificaciones creadas. En el Admin VTEX, este proceso se puede realizar mediante una plantilla o manualmente al [registrar productos y SKUs].
+Si al realizar la importación de SKUs vía plantilla se muestra el mensaje `"An error occurred in the data writing process. Make sure your worksheet data is consistent with the instructions and try again."`, puede ser que durante la importación:
+- [No se rellenaron las especificaciones de SKU obligatorias](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).
+- El archivo tiene un formato incorrecto.
+
+## Solución
+Para resolver este problema es posible:
+
+[Modificar el archivo](#modificar-el-archivo): el archivo debe seguir las reglas de formato y guardarse como plantilla XML en el formato .xls.
+### Solución - Modificar el archivo
+
+1. En el Admin VTEX, accede a **Catálogo** > **Importación y exportación** > **Todos los productos** > **Exportación/Importación** y haz clic en **Importar**.
+2. Después, pulsa `Haz clic aquí` para descargar el modelo de plantilla.
+3. Edita el modelo de plantilla con los SKU que desees, siguiendo todas las recomendaciones de la página **Importación y exportación**.
+4. Guarda la plantilla en formato `.xls`.
+5. En la misma página, en Cargar archivo para importación, selecciona el archivo y haz clic en `Importar`.
+
+Si el error persiste después de modificar el archivo, ponte en contacto con [nuestro soporte](https://support.vtex.com/hc/pt-br/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests).
+
diff --git a/docs/tutorials/es/events-available-in-audit.md b/docs/tutorials/es/events-available-in-audit.md
index 38be1df0c..de7727465 100644
--- a/docs/tutorials/es/events-available-in-audit.md
+++ b/docs/tutorials/es/events-available-in-audit.md
@@ -3,673 +3,234 @@ title: 'Eventos disponibles en Audit'
 id: 6r1Mzcu5NmkmmDLJlz9CCZ
 status: PUBLISHED
 createdAt: 2022-06-22T16:05:16.214Z
-updatedAt: 2023-04-25T14:51:35.871Z
-publishedAt: 2023-04-25T14:51:35.871Z
+updatedAt: 2024-06-28T18:16:11.762Z
+publishedAt: 2024-06-28T18:16:11.762Z
 firstPublishedAt: 2022-06-22T16:28:52.801Z
 contentType: tutorial
 productTeam: Master Data
-author: 2Gy429C47ie3tL9XUEjeFL
+author: 1malnhMX0vPThsaJaZMYm2
 slug: eventos-disponibles-en-audit
 locale: es
 legacySlug: eventos-disponibles-en-audit
 subcategory: 2TNXiKzLZOPxjMTyGiEeJu
 ---
 
-A continuación, verás la lista de posibles eventos disponibles en [Audit] (https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA#) para cada aplicación.
+A continuación, verás la lista de posibles eventos disponibles en [Audit] (https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA) para cada aplicación.
+
+* [OMS](#oms)
+* [Pedidos](#pedidos)
+* [Autorización del pedido](#autorizacion-del-pedido)
+* [Inventario y envio](#inventario-y-envio)
+* [Catálogo (Admin)](#catalogo-admin)
+* [Catálogo (API)](#catalogo-api)
+* [Precios](#precios)
+* [Promociones](#promociones)
+* [Suscripciones](#suscripciones)
+* [Carteras](#carteras)
+* [Tarjeta de regalo](#tarjeta-de-regalo)
+* [Checkout](#checkout)
+* [Portal CMS](#portal-cms)
+* [License Manager](#license-manager)
+* [VTEX ID](#vtex-id)
+* [Headless CMS](#headless-cms)
+* [Gestión de sellers](#gestion-de-sellers)
 
 <div class = "alert alert-info">
 Si, en Audit, ves algún evento no incluido en esta lista, por favor, envíanos más información a través de la <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback sobre documentación</a>.
 </div>
 
 <div class="alert alert-warning">
-En el módulo Audit, al hacer clic en los filtros de auditoría puedes encontrar <code>Profile System</code>, además de otras aplicaciones citadas a continuación. Esta opción se refiere a funcionalidades en beta cerrada, por lo que la mayoría de las cuentas no tendrán eventos asociados.
+En el módulo Audit, al hacer clic en los filtros de auditoría puedes encontrar <strong>Opciones de envío</strong>, <strong>Profile System</strong> y <strong>Billing</strong>, además de otras aplicaciones citadas a continuación. Estas opciónes se refieren a recursos internos o funcionalidades en beta cerrada, por lo que la mayoría de las cuentas no tendrán eventos asociados.
 </div>
 
-## Catalog admin
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Product Activation
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Activación de producto.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del producto.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Product Commercial Condition Change
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cambios en las condiciones comerciales de un producto.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del producto y lista de las condiciones modificadas.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Attachment Association    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Asociación de un adjunto a un SKU.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del SKU, nombre e ID del adjunto.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Archive Upload    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Envío de archivo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre de archivo.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Field Activation    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Activación de campo de catálogo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre, ID y status del campo.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Binding    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Conexión de un SKU con un <em>seller</em>.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del <em>seller</em>, ID del SKU en el catálogo del <em>seller </em>e ID del SKU en el catálogo del <em>marketplace</em>.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Unbinding
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación de la conexión entre un SKU y un <em>seller</em>.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del <em>seller</em>, ID del SKU en el catálogo del <em>seller </em>e ID del SKU en el catálogo del <em>marketplace</em>.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Removal
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación del SKU del <em>seller</em>.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del SKU en el catálogo del <em>seller</em>.
-   </td>
-  </tr>
-</table>
-
-## Pricing
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Put Price
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación o modificación del precio de un SKU determinado.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del SKU.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Price Table
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación o modificación de la tabla de precios.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación de la tabla creada o modificada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Price Tables
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación o modificación de varias tablas de precios.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación de las tablas creadas o modificadas.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Price Deleted
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación del precio de un SKU determinado.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del SKU.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Config
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación o modificación de la configuración del precio.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación de la configuración creada o modificada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Fixed Price Modified
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación del precio fijo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación del precio fijo modificado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Put Catalog Step
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación o modificación de una regla de precio.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Regla de precio creada o modificada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Deleted Fixed Prices From Table
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación del precio fijo de la lista de precios correspondiente.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación de la lista y del precio eliminado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Compatibility Post Prices
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación del precio utilizando la API de compatibilidad con el contrato de PricingV1.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación del precio modificado.
-   </td>
-  </tr>
-
-</table>
-
-## Logistics
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de transportadora.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de la transportadora.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Actualización de transportadora.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de la transportadora.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación de la transportadora.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de la transportadora.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de almacén.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del almacén.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Actualización de almacén.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del almacén.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación de almacén.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del almacén.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de stock.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del stock.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Actualización de stock.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del stock.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación de stock.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del stock.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Pickup Point Save
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación o modificación del punto de recogida.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del punto de recogida.
-   </td>
-  </tr>
-</table>
-
 ## OMS
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Start Handling
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Acción que le indica a VTEX que la tienda comenzó a preparar determinado pedido. Esto desencadena la continuidad del flujo de dicho pedido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del pedido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Status
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cambio en el status de un pedido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del pedido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Payment Notification
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Envío de notificación de pago de un pedido determinado.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del pedido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cambio en la configuración del módulo de pedidos.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Breve descripción del cambio.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resend Last Email
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Reenvío del último email relacionado con el pedido en el Centro de mensajes.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del pedido.
-   </td>
-  </tr>
-</table>
-
-## Promotions
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Rate Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación de la configuración de la tasa.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de la configuración de la tasa.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Promotion Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación de la configuración de la promoción.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de la configuración de la promoción.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Coupon Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cambio en el cupón.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Código de cupón.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Unarchived Calculator
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Desarchivar promoción o tasa.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de la configuración de la promoción o tasa.
-   </td>
-  </tr>
-</table>
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| Start Handling | Acción que le indica a VTEX que la tienda comenzó a preparar determinado pedido. Esto desencadena la continuidad del flujo de dicho pedido. | ID del pedido. |
+| Change Status | Cambio en el status de un pedido. | ID del pedido. |
+| Shipping Notification  | Notificación de envío de un pedido determinado.  | ID del pedido.  |
+| Payment Notification | Envío de notificación de pago de un pedido determinado. | ID del pedido. |
+| Save Configuration | Cambio en la configuración del módulo de pedidos. | Breve descripción del cambio. |
+| Resend Last Email | Reenvío del último email relacionado con el pedido en el Centro de mensajes. | ID del pedido. |
+
+## Pedidos
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| Change State | Cambio en el status de un pedido. | ID del pedido. |
+| Order Cancellation | Cancelación de un pedido. | ID del pedido. |
+| Start Handling  | Acción que le indica a VTEX que la tienda comenzó a preparar determinado pedido. Esto desencadena la continuidad del flujo de dicho pedido.  | ID del pedido.  |
+| Notify Payment | Envío de notificación de pago de un pedido determinado. | ID del pedido. |
+
+## Autorización del pedido
+
+| Acción | Descripción del evento  | Detalles del evento  |
+|---|---|---|
+| Create Rule | Creación de una regla de divergencia de valores.  | ID de la regla. |
+| New Dimension | Creación de dimensiones para la aprobación de pedidos, como el intervalo de valor del pedido, lista de correos electrónicos autorizados a realizar la aprobación de pedidos, entre otros.  | ID de la dimensión. |
+| Delete Dimension | Exclusión de dimensiones para la aprobación de pedidos, como el intervalo de valor del pedido, lista de correos electrónicos autorizados a realizar la aprobación de pedidos, entre otros.  | ID de la dimensión. |
+| Update Dimension | Actualización de dimensiones para la aprobación de pedidos, como el intervalo de valor del pedido, lista de correos electrónicos autorizados a realizar la aprobación de pedidos, entre otros.  | ID de la dimensión. |
+| Update Rule | Edición de una regla de divergencia de valores.  | ID de la regla. |
+| Delete Rule | Exclusión de una regla de divergencia de valores.  | ID de la regla. |
+
+## Inventario y envio
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| Carrier Create | Creación de transportadora. | ID de la transportadora. |
+| Carrier Update | Actualización de transportadora. | ID de la transportadora. |
+| Carrier Delete | Eliminación de la transportadora. | ID de la transportadora. |
+| Dock Create | Creación de almacén. | ID del almacén. |
+| Dock Update | Actualización de almacén. | ID del almacén. |
+| Dock Delete | Eliminación de almacén. | ID del almacén. |
+| Warehouse Create | Creación de stock. | ID del stock. |
+| Warehouse Update | Actualización de stock. | ID del stock. |
+| Warehouse Delete | Eliminación de stock. | ID del stock. |
+| Pickup Point Save | Creación o modificación del punto de recogida. | ID del punto de recogida. |
+
+## Catálogo (Admin)
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| Product Activation | Activación del producto. Este evento se registra únicamente cuando se realizan cambios en el Admin. Los cambios realizados en plantillas no se registran en este evento. | ID del producto. |
+| Product Commercial Condition Change | Cambios en las condiciones comerciales de un producto. | ID del producto y lista de las condiciones modificadas. |
+| SKU Attachment Association | Asociación de un adjunto a un SKU. | ID del SKU, nombre e ID del adjunto. |
+| Archive Upload | Envío de archivo. | Nombre de archivo. |
+| Field Activation | Activación de campo de catálogo. | Nombre, ID y status del campo. |
+| SKU Seller Binding | Conexión de un SKU con un seller. | ID del seller, ID del SKU en el catálogo del seller e ID del SKU en el catálogo del marketplace. |
+| SKU Seller Unbinding | Eliminación de la conexión entre un SKU y un seller. | ID del seller, ID del SKU en el catálogo del seller e ID del SKU en el catálogo del marketplace. |
+| SKU Seller Removal | Eliminación del SKU del seller. | ID del SKU en el catálogo del seller. |
+
+## Catálogo (API)
+
+| Acción | Descripción | Detalles del evento |
+|---|---|---|
+|  SKU Seller Binding Removal | Eliminación de enlace de SKU. | ID del SKU en seller y ID del seller. |
+| Seller Update | Actualización de seller. | ID del seller. |
+| Seller Creation | Creación de seller. | ID del seller. |
+| SKU Seller Binding Activation | Activación de vinculación de SKU. | ID del SKU en seller y ID del seller. |
+| SKU Seller Binding Inactivation | Inactivación de vinculación de SKU. |  ID del SKU en seller y ID del seller. |
+
+## Precios
+
+| Acción | Descripción | Detalles del evento |
+|---|---|---|
+| Put Price | Creación o modificación del precio de un SKU determinado. | ID del SKU. |
+| Save Price Table | Creación o modificación de la tabla de precios. | Identificación de la tabla creada o modificada. |
+| Save Price Tables | Creación o modificación de varias tablas de precios. | Identificación de las tablas creadas o modificadas. |
+| Price Deleted | Eliminación del precio de un SKU determinado. | ID del SKU. |
+| Save Config | Creación o modificación de la configuración del precio. | Identificación de la configuración creada o modificada. |
+| Fixed Price Modified | Modificación del precio fijo. | Identificación del precio fijo modificado. |
+| Put Catalog Step | Creación o modificación de una regla de precio. | Regla de precio creada o modificada. |
+| Deleted Fixed Prices From Table | Eliminación del precio fijo de la lista de precios correspondiente. | Identificación de la lista y del precio eliminado. |
+| Compatibility Post Prices | Modificación del precio utilizando la API de compatibilidad con el contrato de PricingV1. | Identificación del precio modificado. |
+| Change Rnb Config  | Cambio en la configuración de precios para nuevas cuentas.  | Nombre de la cuenta que ha realizado el cambio. |
+
+## Promociones
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| Archive Coupon | Archivar un cupón. | Código del cupón. |
+| Unarchive Coupon | Desarchivar un cupón. | Código del cupón. |
+| Change Rate Configuration | Modificación de la configuración de la tasa. | ID de la configuración de la tasa. |
+| Change Promotion Configuration | Modificación de la configuración de la promoción. | ID de la configuración de la promoción. |
+| Change Coupon Configuration | Cambio en el cupón. | Código de cupón. |
+| Unarchived Calculator | Desarchivar promoción o tasa. | ID de la configuración de la promoción o tasa. |
+| Archived Calculator | Archivar promoción o tasa. | ID de la configuración de la promoción o tasa. |
+
+## Suscripciones
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| SubscriptionGroup Update | Actualización de un grupo de suscripción. | ID de grupo de suscripción. |
+| Subscription Create | Creación de una suscripción. | ID de suscripción. |
+| SubscriptionGroup Place Order | Creación de un pedido de suscripción dentro de un grupo de suscripción. | ID de grupo de suscripción. |
+| SubscriptionGroup Retry | Ejecución de un intento de generar un ciclo de suscripción. | ID de grupo de suscripción. |
+| Subscription Delete | Eliminación de una suscripción. | ID de suscripción. |
+| Plan Create | Creación de un plan de suscripción en el que las tiendas pueden asociar diferentes artículos y SKU. | ID de plan de suscripción. |
+| Plan Update | Actualización de un plan de suscripción, donde las tiendas pueden asociar diferentes artículos y SKUs. | ID de plan de suscripción. |
+| Subscriber Fetch By Email | Auditoría de quién ha buscado los datos de perfil de un cliente de una tienda que se ha suscrito, a partir del correo electrónico del cliente. | ID del usuario que ha realizado la búsqueda. |
+| SubscriptionGroup Create For Order | Creación de un grupo de suscripción para un pedido existente. | ID de grupo de suscripción. |
+| Plan Delete | Eliminación de un plan de suscripción. | ID de plan de suscripción. |
+| Store Payments Update | Actualización de los métodos de pago aceptados por la tienda para las suscripciones. | Nombre de la cuenta. |
+
+## Carteras
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| TOGGLE_WALLET | Activar o desactivar una cartera digital. | toggle-wallet-action |
+
+## Tarjeta de regalo
+
+| Acción | Descripción | Detalles del evento |
+|---|---|---|
+| LIST_GIFT_CARD | Consultación de la lista de tarjetas de regalo. | list-gift-card |
+| EXPORT_GIFT_CARD | Exportación de tarjetas de regalo. | export-gift-card |
+| EDIT_GIFT_CARD | Edición del valor de la tarjeta de regalo. | add-gift-card-value |
+| CREATE_GIFT_CARD | Creación de tarjeta de regalo. | create-multiple-gift-cards |
 
 ## Checkout
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Configurated OrderForm
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cambio de la configuración de OrderForm, que se encarga del funcionamiento del checkout de la tienda.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Descripción de la acción (”configurated OrderForm”)
-   </td>
-  </tr>
-</table>
-
-## Portalv2
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Configuration Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación de la configuración del portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">“*”
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Saved
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación del archivo del portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre del archivo modificado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Site Created
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de sitio web.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre del sitio web creado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Template Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación de plantilla del portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre de la plantilla modificada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Page Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación de la página.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre de la página.
-   </td>
-  </tr>
-</table>
-
-## Portal CMS
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Modificación del archivo del portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre e ID del archivo modificado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Upload
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Carga del archivo del portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre del archivo modificado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Deleted
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminación de archivo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nombre e ID del archivo modificado.
-   </td>
-  </tr>
-</table>
-
-## Conditions
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PutCondition
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de condición.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificación de la condición creada.
-   </td>
-  </tr>
-</table>
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| SaveOrderFormConfiguration | Cambio de la configuración de OrderForm, que se encarga del funcionamiento del checkout de la tienda. | Descripción de la acción (”configurated OrderForm”) |
+
+## License Manager
+
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| Block AppToken | Bloqueo de clave de aplicación. | Clave de aplicación bloqueada. |
+| Accept Sponsor Invite | Aceptación de invitaciones para ser usuario titular. | ID del usuario que aceptó la invitación. |
+| Save User | Creación de nuevo usuario o modificar sus datos. | ID de usuario. |
+| Save Account | Creación de cuenta o modificar la información de la misma. | Cuenta creada o modificada. |
+| Change Role | Editar rol. | Rol editado. |
+| Delete Role | Eliminar rol. | Rol eliminado. |
+| Unblock AppToken | Bloqueo de clave de aplicación. | Clave de aplicación bloqueada. |
+| Resource Access Allowed | Acceso al recurso permitido. | Clave del recurso e ID del usuario al que se le ha dado acceso. |
+| Cancel Sponsor Invite | Cancelación de invitación para usuario titular. | ID de usuario invitado. |
+| Delete User | Eliminar usuario. | ID del usuario eliminado. |
+| Update Binding | Actualización de binding. | Binding actualizado. |
+| Resource Access Denied | Acceso al recurso denegado. | Clave del recurso e ID del usuario al que se le denegó. |
+| Create New AppToken | Creación de clave de aplicación. | Clave de aplicación creada. |
+| Create Sponsor Invite | Crear invitación para usuario titular. | ID del usuario que recibirá la invitación. |
 
 ## VTEX ID
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PasswordCreated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">El usuario registra una contraseña por primera vez en la tienda o en el Admin VTEX.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de usuario.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PasswordUpdated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">El usuario cambia su contraseña de la tienda o del Admin VTEX.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de usuario.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">IdentityProviderChanged
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cambios en la configuración del proveedor de identidad. Por ejemplo, cuando se crea una integración OAuth personalizada, o se modifica la información de una configuración OAuth existente.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Proveedor de identidad.
-   </td>
-  </tr>
-</table>
+| Acción | Descripción del evento | Detalles del evento |
+|---|---|---|
+| PasswordCreated | El usuario registra una contraseña por primera vez en la tienda o en el Admin VTEX. | ID de usuario. |
+| PasswordUpdated | El usuario cambia su contraseña de la tienda o del Admin VTEX. | ID de usuario. |
+| IdentityProviderChanged | Cambios en la configuración del proveedor de identidad. Por ejemplo, cuando se crea una integración OAuth personalizada, o se modifica la información de una configuración OAuth existente. | Proveedor de identidad. |
 
-## License Manager
+## Master Data
+
+| Acción  | Descripción  | Detalles del evento |
+|---|---|---|
+| DeleteDocument | Eliminación de un documento. | ID del documento. |
+
+## Headless CMS
+
+| Acción | Descripción | Detalles del evento |
+|---|---|---|
+| TRY_PUBLISHING | Intento de publicar una página. | ID del evento. |
+| TRY_PUBLISH_IN_RELEASE | Intento de publicar un release. | ID del evento. |
+| TRY_UNPUBLISHING | Intento de despublicar una página. | ID del evento. |
+| RESTORE_CONTENT | Restauración de contenido. | ID del evento. |
+| TRY_UPDATING_DRAFT | Intento de actualizar un borrador. | ID del evento. |
+| TRY_UNPUBLISHING_AND_OVERWRITING | Intento de despublicar y sobrescribir una página. | ID del evento. |
+| done.invoke.deleteContent | Eliminación de contenido. | ID del evento. |
+| done.invoke.deleteContentVariant | Eliminación de una versión del contenido. | ID del evento. |
+
+En la columna **Acción**, todos los eventos de Headless CMS también muestran la siguiente información:
+
+* **CONTENT_ID:** código identificador único de contenido.
+* **VARIANT_ID:** código identificador único de la versión del contenido.
+* **WORKSPACE**: workspace en el que se realizó el cambio.
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Acción</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descripción del evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalles del evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Block AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Bloqueo de clave de aplicación.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Clave de aplicación bloqueada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Accept Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Aceptación de invitaciones para ser usuario titular.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del usuario que aceptó la invitación.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save User
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de nuevo usuario o modificar sus datos.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de usuario.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Account
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de cuenta o modificar la información de la misma.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cuenta creada o modificada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Role
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Editar rol.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Rol editado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Delete Role
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminar rol.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Rol eliminado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Unblock AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Bloqueo de clave de aplicación.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Clave de aplicación bloqueada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resource Access Allowed
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Acceso al recurso permitido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Clave del recurso e ID del usuario al que se le ha dado acceso.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Cancel Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cancelación de invitación para usuario titular.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID de usuario invitado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Delete User
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Eliminar usuario.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del usuario eliminado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Update Binding
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Actualización de binding.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Binding actualizado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resource Access Denied
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Acceso al recurso denegado.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Clave del recurso e ID del usuario al que se le denegó.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Create New AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Creación de clave de aplicación.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Clave de aplicación creada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Create Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Crear invitación para usuario titular.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID del usuario que recibirá la invitación.
-   </td>
-  </tr>
-</table>
+## Gestión de sellers
 
+| Acción | Descripción | Detalles del evento |
+|---|---|---|
+| Update Seller | Edición de seller. | Seller ID. |
+| Save Seller | Creación de seller. | Seller ID. |
diff --git a/docs/tutorials/es/explained-search.md b/docs/tutorials/es/explained-search.md
new file mode 100644
index 000000000..65d936fe7
--- /dev/null
+++ b/docs/tutorials/es/explained-search.md
@@ -0,0 +1,31 @@
+---
+title: 'Explicación de Búsqueda'
+id: F2yxrRvTNt4aEZGC7HV65
+status: PUBLISHED
+createdAt: 2024-06-27T16:54:49.509Z
+updatedAt: 2024-06-27T16:55:37.629Z
+publishedAt: 2024-06-27T16:55:37.629Z
+firstPublishedAt: 2024-06-27T16:55:37.629Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: explicacion-de-busqueda
+locale: es
+legacySlug: explicacion-de-busqueda
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+Explicación de búsqueda es una funcionalidad que interpreta un término buscado y presenta la lista de productos como resultado de la búsqueda. También muestra todas las referencias que se utilizaron para determinar el orden. Estas son:
+
+  - Configuraciones y reglas de búsqueda (configurados en VTEX Intelligent Search).
+  - Informaciones de los productos.
+
+Con la herramienta es posible visualizar qué datos impactan en el orden final. De esta manera, al mostrar esta información se pueden hacer cambios para alcanzar el objetivo deseado de la búsqueda.
+
+Siga las instrucciones a continuación para acceder a la página:
+
+1. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
+2. En **Intelligent Search**, haga clic en **Explicación de la búsqueda**. 
+
+![Explicación de Búsqueda](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
+
diff --git a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
index 28b2779a1..c6ba19cd0 100644
--- a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
@@ -3,8 +3,8 @@ title: 'Exportar y importar especificaciones de producto y SKU'
 id: tutorials_274
 status: PUBLISHED
 createdAt: 2017-04-27T22:10:43.787Z
-updatedAt: 2023-03-29T15:30:59.932Z
-publishedAt: 2023-03-29T15:30:59.932Z
+updatedAt: 2024-02-21T20:34:56.013Z
+publishedAt: 2024-02-21T20:34:56.013Z
 firstPublishedAt: 2017-04-27T23:03:12.428Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -32,14 +32,18 @@ Vea a continuación cómo exportar la plantilla con las especificaciones del pro
 1. En el Admin VTEX, accede a **Catálogo**, o escribe **Catálogo** en la barra de búsqueda en la parte superior de la página.
 2. Haz clic en **Importación y exportación**.
 3. Haz clic en la pestaña __Especificaciones de producto__ o **Especificaciones de SKU**, en función de sus necesidades.
-    ![skuexport1.es](https://images.ctfassets.net/alneenqid6w5/6dlUefWP7lw3FzqWZjcLet/1d604f16ca07a32db13bdb1a3d52836a/skuexport1.es.png)
+    ![skuexport1.es](//images.ctfassets.net/alneenqid6w5/6dlUefWP7lw3FzqWZjcLet/1d604f16ca07a32db13bdb1a3d52836a/skuexport1.es.png)
 4. Haz clic con el botón derecho en la categoría deseada.
     No puede exportar especificaciones de todas las categorías a la vez. Debe elegir sólo una categoría cuyas especificaciones desee exportar. 
 5. Haz clic en `Exportar`.
     Aparecerá un rectángulo verde en pantalla.
 6. Haz clic en `Haz clic aquí para descargar el archivo` para exportar la plantilla.
 
-![skuexport2.es](https://images.ctfassets.net/alneenqid6w5/6aQThG8rLVv6c48ZAO1in4/eeb2118c25334f4b18d485b2c2127cd5/skuexport2.es.png)
+![skuexport2.es](//images.ctfassets.net/alneenqid6w5/6aQThG8rLVv6c48ZAO1in4/eeb2118c25334f4b18d485b2c2127cd5/skuexport2.es.png)
+
+<div class = "alert alert-info">
+  <p>La hoja de plantilla exportada estará disponible en tu email durante una semana. Si supera este periodo, vuelva a seguir la exportación paso a paso para generar una nueva hoja de plantilla.</p>
+</div>
 
 ## Importar especificaciones de producto o SKU
 
@@ -59,7 +63,7 @@ Siga los pasos a continuación para importar la plantilla:
 2. Haz clic en **Seleccionar** para seleccionar el archivo con la plantilla completa en la computadora.
 3.  Haz clic en `Importar`.
 
-![skuexport3.es](https://images.ctfassets.net/alneenqid6w5/5IJmGafmCsB9tawXSYAyz1/473921b906075a53364a0018aaf08176/skuexport3.es.png)
+![skuexport3.es](//images.ctfassets.net/alneenqid6w5/5IJmGafmCsB9tawXSYAyz1/473921b906075a53364a0018aaf08176/skuexport3.es.png)
 
 ## Más información
 - [Especificaciones de producto e de SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
diff --git a/docs/tutorials/es/exporting-data.md b/docs/tutorials/es/exporting-data.md
index 356455ac4..654368134 100644
--- a/docs/tutorials/es/exporting-data.md
+++ b/docs/tutorials/es/exporting-data.md
@@ -3,8 +3,8 @@ title: 'Exportación de datos de Master Data v1'
 id: tutorials_1125
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:19.601Z
-updatedAt: 2023-03-28T23:31:33.420Z
-publishedAt: 2023-03-28T23:31:33.420Z
+updatedAt: 2024-06-20T15:09:14.414Z
+publishedAt: 2024-06-20T15:09:14.414Z
 firstPublishedAt: 2017-04-27T23:03:43.216Z
 contentType: tutorial
 productTeam: Master Data
@@ -21,21 +21,21 @@ La exportación de datos en lote de los registros en Master Data v1 puede hacer
 La operación de exportación de datos del Master Data no es inmediata, y su tiempo de ejecución depende de la cantidad de datos en el Master Data. Por lo tanto, en tiendas con muchos datos y con una alta frecuencia de actualización, el archivo exportado puede quedar desfasado con relación a los nuevos datos. Si esto ocurre, la solución es volver a exportar los datos, preferiblemente en un momento en el que no se estén produciendo muchas actualizaciones (por ejemplo, fuera del horario comercial o en los fines de semana).
 </div>
 
-## Como exportar
+## Exportar informe con datos de Master Data v1
+
+Siga las instrucciones que se indican a continuación para exportar un informe con datos de registro de un formulario de Master Data v1.
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
-2. Haga clic en la pestaña **Aplicações.**
-3. Haga clic en visualizar (icono de la derecha) en el formulario deseado.
-![visualizar button master data](https://images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
-4. Esto cargará el formulario seleccionado.
-5. Haga clic en el botón **Exportar XLS.**
-6. Seleccione los campos que desea recibir en el informe.
-7. Rellene el e-mail al que desea enviar el informe (el campo se rellena automáticamente con el correo electrónico del usuario logado, pero puede ser cambiado).
-8. Haga clic en el botón **Exportar.**
+2. Asegúrate de que se encuentra en la pestaña **Aplicaciones**.
+3. Haz clic en el icono de lista <i class="fas fa-bars"></i> junto al formulario deseado.
+4. Haz clic en el botón `Exportar XLS`.
+6. Selecciona los campos que desea recibir en el informe.
+7. Rellena el email al que desea enviar el informe (el campo se rellena automáticamente con el correo electrónico del usuario logado, pero puede ser cambiado).
+8. Haz clic en el botón `Exportar`.
 
 ## Datos exportados de clientes
 
-Debajo encontrará nuestra lista identificando campos default exportados en la aba **Clientes** de Master Data v1.
+Debajo encontrará nuestra lista identificando campos estándar exportados en la aba **Clientes** de Master Data v1.
 
 | Campo     | Descripción     | Origem     |
 | ---------- | ---------- | ---------- |
@@ -72,5 +72,5 @@ Debajo encontrará nuestra lista identificando campos default exportados en la a
 | rclastcartvalue       | Valor del último carrito	       | Script de navegación       |
 | carttag       | Lista de IDs de los SKUs del último Carrito	       | Script de navegación       |
 
-Recuerde que estos campos, son campos que vienen por default en el formulario __Cliente__. En el caso de que la tienda haya personalizado esta entidad (Cliente), puede haber otros campos que fueron creados.
+Recuerde que estos campos, son campos que vienen por estándar en el formulario __Cliente__. En el caso de que la tienda haya personalizado esta entidad (__Cliente__), puede haber otros campos que fueron creados.
 
diff --git a/docs/tutorials/es/facebook-faq.md b/docs/tutorials/es/facebook-faq.md
index f87bd5292..d713039fa 100644
--- a/docs/tutorials/es/facebook-faq.md
+++ b/docs/tutorials/es/facebook-faq.md
@@ -37,7 +37,7 @@ Lo primero que debe verificar en este escenario es si el SKU realmente no posee
 
 En el caso de que el SKU posea un precio, verifique el status del SKU porque el error también puede estar relacionado con la situación de activo/inactivo. La mejor manera de hacerlo es realizando una simulación de checkout:
 
-![face faq01](https://images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
+![face faq01](//images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
 
 En esta simulación es importante analizar los campos:  
 
@@ -55,7 +55,7 @@ Este proceso es recomendado cuando la integración está teniendo algún problem
 
 #### Eliminar la App de integración de VTEX en Facebook 
 1. Acceda a Facebook utilizando su cuenta vinculada a VTEX. 
-2. En la esquina superior derecha de la pantalla, haga **clic en el botón** <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/7bplP3pn7Pu5gpfYKGHUjQ/688fda65e48070afcf18f57e396c2b22/sua_conta_fb.JPG" />
+2. En la esquina superior derecha de la pantalla, haga **clic en el botón** <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/7bplP3pn7Pu5gpfYKGHUjQ/688fda65e48070afcf18f57e396c2b22/sua_conta_fb.JPG" />
 3. Seleccione la opción **Configuración y privacidad**, luego haga clic en **Configuración**.
 4. Haga clic en **Integraciones comerciales**.
 5. Seleccione la opción **VTEX Integration** y haga clic en **Eliminar**.
@@ -64,7 +64,7 @@ Este proceso es recomendado cuando la integración está teniendo algún problem
 1. Acceda a la página de [Facebook Business Manager](https://business.facebook.com/).
 2. Seleccione la opción **Más herramientas**.
 3. Haga clic en **Configuración del negocio**.
-4. Seleccione el catálogo de VTEX que desea eliminar y haga clic en la papelera <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6zFRTeiTa9xkTlafUVBIcK/d2c5a40219dbee8084d22f76d0b88109/excluir_fb.JPG" />
+4. Seleccione el catálogo de VTEX que desea eliminar y haga clic en la papelera <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6zFRTeiTa9xkTlafUVBIcK/d2c5a40219dbee8084d22f76d0b88109/excluir_fb.JPG" />
 5. Haga clic en **Confirmar**.
 
 #### Eliminar la configuración de integración de Facebook en VTEX
diff --git a/docs/tutorials/es/facilitating-b2b-store-operation.md b/docs/tutorials/es/facilitating-b2b-store-operation.md
index 1f545a6b1..03fb9626d 100644
--- a/docs/tutorials/es/facilitating-b2b-store-operation.md
+++ b/docs/tutorials/es/facilitating-b2b-store-operation.md
@@ -1,9 +1,9 @@
 ---
 title: 'Facilitar la operación de una tienda B2B'
 id: 8t1f9FYBsSCopHHVujKWR
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-03-30T14:29:12.548Z
-updatedAt: 2021-05-20T18:17:16.108Z
+updatedAt: 2024-05-10T10:59:55.549Z
 publishedAt: 2021-05-20T18:17:16.108Z
 firstPublishedAt: 2021-03-30T19:54:13.259Z
 contentType: tutorial
@@ -12,7 +12,7 @@ author: 7qy2DBsUp8U5P9lqV0JHfR
 slug: facilitar-la-operacion-de-una-tienda-b2b
 locale: es
 legacySlug: facilitar-la-operacion-de-una-tienda-b2b
-subcategory: 5N5GjDrKSycIQMeoS7CLtj
+subcategory: 2LrbEY7MFeKqmdfYLBCnfi
 ---
 
 Puede facilitar la operación de su tienda a través de aplicaciones que se pueden instalar en la misma para solucionar problemas de negocio específicos que están relacionados con la usabilidad de la tienda, las ventas y la posventa.
@@ -91,7 +91,7 @@ VTEX cuenta con [My account](https://help.vtex.com/es/tutorial/como-funciona-o-m
 
 Esta herramienta permite al consumidor seguir el status de su pedido en el flujo de posventa, así como realizar algunas operaciones. Entre estas, «Pedir nuevamente» para volver a realizar un pedido que se efectuó anteriormente.  
 
-![reorder ES](https://images.ctfassets.net/alneenqid6w5/53BeeU3MFPuA26NepAhXrI/708213aadff4d416977f6e5dc6b18638/reorder_ES.png)
+![reorder ES](//images.ctfassets.net/alneenqid6w5/53BeeU3MFPuA26NepAhXrI/708213aadff4d416977f6e5dc6b18638/reorder_ES.png)
 
 Para saber más detalles de My Account, lea el tutorial sobre [cómo configurar esta funcionalidad](https://help.vtex.com/pt/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1 "cómo configurar esta funcionalidad").
 
diff --git a/docs/tutorials/es/faq-security-2.md b/docs/tutorials/es/faq-security-2.md
index d90ef7f9e..db7bc16c7 100644
--- a/docs/tutorials/es/faq-security-2.md
+++ b/docs/tutorials/es/faq-security-2.md
@@ -3,7 +3,7 @@ title: 'FAQ - Seguridad 2'
 id: 1ayXEtqawI9yuxFXutiITh
 status: DRAFT
 createdAt: 2022-05-26T13:33:48.633Z
-updatedAt: 2022-08-22T12:33:50.220Z
+updatedAt: 2024-05-28T16:48:10.138Z
 publishedAt: 
 firstPublishedAt: 2022-06-09T22:09:20.893Z
 contentType: tutorial
diff --git a/docs/tutorials/es/faq-security-restricted-content.md b/docs/tutorials/es/faq-security-restricted-content.md
new file mode 100644
index 000000000..f1db171d1
--- /dev/null
+++ b/docs/tutorials/es/faq-security-restricted-content.md
@@ -0,0 +1,187 @@
+---
+title: 'FAQ - Seguridad (contenido restringido)'
+id: 7AmPOGXykmE9SYyYDzdAZ4
+status: DRAFT
+createdAt: 2022-05-26T00:09:53.997Z
+updatedAt: 2024-05-28T16:45:09.328Z
+publishedAt: 
+firstPublishedAt: 2022-06-02T18:56:44.116Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: faq-seguridad-contenido-restringido
+locale: es
+legacySlug: faq-seguridad-contenido-restringido
+subcategory: 
+---
+
+# FAQ - Seguridad (contenido restringido)
+
+<div class="alert alert-danger">
+  <p>No compartas las respuestas de estas preguntas frecuentes con usuarios que no tengan acceso al Admin VTEX.</p>
+</div>
+
+Para asistir con las evaluaciones de riesgos de los clientes, VTEX proporciona páginas de preguntas frecuentes con respuestas a las principales preguntas sobre la estructura y seguridad de la plataforma. Este contenido solo está disponible para los usuarios con acceso al Admin VTEX. Las preguntas y respuestas públicas están disponibles en Preguntas frecuentes - Seguridad en VTEX Help Center.
+
+Haz clic en los siguientes puntos para acceder a las preguntas y respuestas de cada tema:
+
+* [Gestión de riesgos](#gestión-de-riesgos)
+* [Control de acceso, identificación y autenticación](#control-de-acceso-identificación-y-autenticación)
+* [Seguridad de la plataforma](#seguridad-de-la-plataforma)
+* [Seguridad de los datos](#seguridad-de-los-datos)
+* [Seguridad de la red](#seguridad-de-la-red)
+* [Gestión de vulnerabilidades](#gestión-de-vulnerabilidades)
+* [Monitoreo de seguridad](#monitoreo-de-seguridad)
+* [Respuesta y mitigación de incidentes](#respuesta-y-mitigación-de-incidentes)
+* [Recuperación ante desastres y continuidad de negocio](#recuperación-ante-desastres-y-continuidad-de-negocio)
+
+## Gestión de riesgos
+
+### ¿Cómo gestiona VTEX los riesgos de ciberseguridad en la plataforma y en la infraestructura interna?
+
+VTEX realiza análisis periódicos de amenazas y vulnerabilidades en la plataforma, en los procesos operativos y en el negocio. La identificación de riesgos nos ayuda a mejorar los sistemas de monitoreo y notificación para hacer frente a su eventual materialización, ya sea notificando a las personas capaces de gestionarlos o activando acciones automatizadas que puedan mitigarlos o eliminarlos.
+
+### ¿Tiene VTEX un programa de gestión de riesgos de los proveedores?
+
+VTEX cuenta con un sólido proceso de gestión de riesgos de terceros. Esto se lleva a cabo a través de una evaluación cuidadosa y continua de los partners y proveedores con el fin de identificar, analizar y mitigar los riesgos asociados a las actividades realizadas por esos colaboradores externos. El objetivo de este proceso es garantizar la seguridad y compliance en todas las interacciones con terceros, reforzando de esta manera la postura de gestión de riesgos de la organización.
+
+Para integrarse a nuestro ecosistema, exigimos que los terceros adopten medidas de seguridad adecuadas. Esta condición asegura que todas las partes mantengan altos estándares de seguridad de la información, lo que contribuye a la integridad y confiabilidad de nuestro entorno operativo.
+
+Si deseas obtener más información sobre los partners que actúan como subencargados en nuestros procesos operativos, accede a la página[ Subencargados VTEX](https://vtex.com/mx-es/privacy-and-agreements/subprocessors/).
+
+## Control de acceso, identificación y autenticación
+
+### ¿Tiene VTEX una política de contraseñas para los empleados? En caso afirmativo, ¿cuáles son los criterios considerados?
+
+Adoptamos una configuración segura y una política de contraseñas robusta para el acceso a nuestros sistemas internos que incluyen requisitos como número mínimo de caracteres y caracteres especiales, periodicidad del cambio de contraseñas, no utilización de contraseñas anteriores y control e inactividad de la sesión. Presentamos un ejemplo a continuación:
+
+* Longitud mínima de 16 caracteres.
+* Combinación de letras, mayúsculas y minúsculas, números y caracteres especiales (`%`, `#`, `$`, `@`, `&`, entre otros).
+* No repetir números o letras, en secuencia o series obvias, como `aaaabbbb`, `12345678`, `asdfghjk`.
+* Utilizar cifrado complejo para que las credenciales de autenticación sean ilegibles durante la transmisión y almacenamiento en todos los componentes del sistema.
+* Opción de cambiar contraseña en el primer inicio de sesión desactivada.
+* No utilizar contraseñas anteriores.
+
+### ¿La plataforma cierra la sesión por inactividad?
+
+La plataforma VTEX dispone de un mecanismo de cierre de sesión por inactividad. Se cierra la sesión del cliente en el entorno de checkout automáticamente después de 15 minutos de inactividad.
+
+## Seguridad de la plataforma
+
+### ¿Cómo la plataforma almacena y mantiene la base de usuarios? ¿Cómo se almacenan y protegen las credenciales de los usuarios?
+
+Las contraseñas en la plataforma VTEX utilizan una combinación de hash y sal. Actualmente utilizamos algoritmos de hash SHA1 y PBKDF2 con una sal al principio o al final que proporciona una capa adicional de seguridad. Los emails de los usuarios se almacenan y separan lógicamente en función de una determinada cuenta de la tienda, y no se puede acceder a ellos de forma cruzada, ni siquiera los empleados de VTEX. Las bases de datos que contienen los emails y los hashes están completamente cifradas con AES-256.
+
+### ¿Cómo funciona el proceso de hardening?
+
+VTEX siempre crea sus entornos utilizando la AMI (imagen de máquina de Amazon) más reciente proporcionada por AWS para los servicios de implementación, ya sea Elastic Beanstalk, OpsWorks o simplemente Cloud Formation. Así, aprovechamos la protección de seguridad que AWS proporciona a las instancias implementadas por sus servicios y complementamos las configuraciones de seguridad con nuestros procesos de hardening específicos para cada activo.
+
+### ¿Qué recursos de seguridad tiene la infraestructura que aloja la plataforma?
+
+La plataforma VTEX es una solución SaaS (Software as a Service) hospedado en un entorno muy controlado y que cuenta con una amplia gama de medidas de seguridad. Esto incluye protección de red con filtros y protección del tráfico de entrada y salida, así como también el uso de WAF (Web Application Firewall) para proteger los activos internos, implementar monitoreo automático en tiempo real y recibir alertas de los entornos.
+
+También se llevan a cabo otras acciones como la implementación de líneas base, el hardening de activos y el establecimiento de controles de acceso físicos y lógicos, entre otros procedimientos necesarios. El objetivo de estas medidas es garantizar que la plataforma esté constantemente protegida y que cumpla con los más altos estándares de seguridad del mercado.
+
+## Seguridad de los datos
+
+### ¿Qué medidas toma VTEX para prevenir la fuga de datos?
+
+Invertimos en medidas preventivas y métodos que aumentan la seguridad de nuestra plataforma y de la infraestructura en la que se basa. Además, constantemente reforzamos la gestión de accesos a los sistemas, especialmente a los que contienen datos sensibles, y siempre aplicamos el mínimo privilegio posible. También tenemos pautas generales que deben seguirse al operar en un entorno regulado, como con los datos de las tarjetas de pago (PCI-DSS) y a los que les apliquen las leyes de protección de datos, etc.
+
+Analizamos la forma en que se tratan los datos en diferentes entornos, internos o externos, para evitar exponerlos sin necesidad y reducir el perímetro de seguridad. Otros esfuerzos para prevenir la fuga de datos son concienciar a los profesionales sobre buenas prácticas de seguridad de la información y proporcionar capacitación constante. Además, automatizamos los controles de procesos basándonos en el principio de que las computadoras mantienen la uniformidad con mayor eficacia. Por último, vigilamos de cerca la evolución del proceso de protección contra fugas de datos y lo actualizamos continuamente a medida que surgen nuevos riesgos, demandas tecnológicas o estrategias de la empresa.
+
+## Seguridad de la red
+
+### ¿Están las redes de producción internas segregadas de alguna manera, por ejemplo, mediante la restricción y/o filtrado del tráfico entre redes?
+
+Las redes de producción de VTEX están totalmente aisladas de las redes externas, lo que garantiza un entorno altamente seguro. Los empleados responsables del funcionamiento de los entornos de producción pueden necesitar ocasionalmente una conexión VPN (red privada virtual) para acceder a esta red.
+
+Los equilibradores de carga son los únicos objetos a los que se accede externamente a través de la DMZ (zona desmilitarizada), mientras que las capas de la plataforma y la base de datos se encuentran en subredes separadas de la DMZ. Estas capas están protegidas por medidas de seguridad adicionales, garantizando que solo los usuarios autorizados puedan acceder a ellas. Esta estructura de red proporciona una capa de protección adicional y mantiene los datos sensibles y los sistemas de VTEX protegidos contra amenazas externas.
+
+### ¿Utiliza VTEX la protección de acceso a la red mediante firewalls?
+
+VTEX implementa firewalls para proteger el acceso a las redes. Además de los firewalls locales de los sistemas operativos en los servidores, contamos con varias capas de seguridad en la infraestructura de AWS.
+
+Utilizamos grupos de seguridad AWS, configuración ELB (Elastic Load Balancing) y enrutamiento VPC (Virtual Private Cloud) para lograr funcionalidades de firewall en nuestros sistemas. Estas medidas garantizan que solo se permita el tráfico autorizado en nuestra red, reforzando la seguridad de los datos y servicios.
+
+Gracias a que el proceso de implementación de aplicaciones está automatizado y que todos los logs están centralizados, nuestro equipo no necesita acceso directo a los servidores a diario. El acceso al entorno de producción suele realizarse a través de la consola AWS o de nuestras aplicaciones web y API.
+
+Para garantizar una capa de seguridad adicional, nuestros grupos de seguridad y ELB están configurados para solo permitir acceso HTTP y HTTPS a los ELB que exponen recursos públicamente. Si alguna tarea específica requiere acceso adicional, podemos solicitar y autorizar este acceso temporalmente de forma controlada y segura. Estas prácticas garantizan la integridad y seguridad de nuestra infraestructura de red.
+
+### ¿Qué controles utiliza VTEX para mitigar ataques DDoS (ataques distribuidos de denegación de servicio)?
+
+Para mitigar ataques DDoS, VTEX utiliza una estrategia basada en dos capas de defensa. La primera capa se encuentra en el nivel de la CDN (Content Delivery Network), en el que se aplican medidas de seguridad para filtrar y bloquear tráfico malicioso antes de que llegue a la infraestructura principal.
+
+Además, se aplica una regla de limitación adaptativa en el proxy frontal que se sitúa delante de todos los microservicios de VTEX. Esta regla ayuda a detectar y limitar tráfico malicioso o excesivo, reduciendo así el impacto de posibles ataques DDoS.
+
+VTEX también aprovecha los beneficios de[ AWS Shield](https://aws.amazon.com/es/shield/?nc1=h_ls), además de las medidas internas, que es un servicio proporcionado por Amazon Web Services para proteger contra ataques DDoS. Esta combinación de estrategias en varias capas refuerza significativamente la capacidad de VTEX de mitigar y responder ante ataques DDoS, garantizando la disponibilidad e integridad de nuestros servicios.
+
+Los clientes tienen la opción de reforzar la seguridad de sus tiendas contratando un WAF (Web Application Firewall) al adquirir el producto add-on VTEX Shield además de las medidas de protección estándar implementadas por VTEX. Un WAF ofrece una capa de protección adicional y ayuda a filtrar y bloquear tráfico malicioso antes de que llegue a la tienda. Esta solución personalizada permite que los clientes adopten las medidas de seguridad que satisfagan sus necesidades específicas y garanticen una protección más robusta contra posibles ciberataques. Adquirir VTEX Shield permite a los retailers garantizar una protección completa y proactiva para sus tiendas online y tener mayor tranquilidad y confianza en sus negocios digitales.
+
+### ¿Cuenta VTEX con un IDS (sistema de detección de intrusiones) y un IPS (sistema de prevención de intrusiones)? En caso afirmativo, ¿con qué frecuencia se revisan las reglas?
+
+Sí, la solución VTEX incluye sistemas IDS e IPS. Estos sistemas juegan un papel fundamental en la detección y prevención de actividades maliciosas en nuestra infraestructura de red y otros sistemas.
+
+Las reglas IDS e IPS se revisan periódicamente para garantizar que se ajustan a las amenazas y vulnerabilidades más recientes. La revisión se lleva a cabo con bastante frecuencia y es parte integral de nuestro proceso de seguridad. El objetivo es mantener nuestros sistemas actualizados y protegidos contra las técnicas de ataque más recientes y vulnerabilidades emergentes.
+
+La práctica de revisión constante de las reglas IDS e IPS refleja nuestro compromiso con la seguridad y protección de los datos de nuestros clientes, garantizando que siempre estamos adelantados a la constante evolución de las ciberamenazas.
+
+## Gestión de vulnerabilidades
+
+### ¿Cuál es el plazo de corrección de vulnerabilidades?
+
+Elaboramos nuestro procedimiento de gestión de vulnerabilidades cuidadosamente para garantizar la eficaz corrección de posibles fallos de seguridad. Tenemos políticas internas establecidas que definen el plazo de corrección tomando en cuenta la criticidad y complejidad de las vulnerabilidades identificadas. El plazo varía para garantizar que se les asigne mayor prioridad a las vulnerabilidades más críticas y urgentes y, por otro lado, que las menos graves se atiendan adecuadamente sin comprometer la seguridad del sistema. De esta forma, podemos gestionar los riesgos de seguridad con mayor eficiencia y mantener nuestros sistemas protegidos contra posibles amenazas.
+
+### ¿Permite VTEX que los clientes realicen verificaciones de vulnerabilidad mediante escaneos y pruebas de penetración (pentests) independientes preestablecidas por un consultor independiente?
+
+Las instancias de VTEX están alojadas en la infraestructura de AWS, lo que impide la realización de auditorías personales de los sistemas. AWS cuenta con estrictos [programas de conformidad (compliance)](https://aws.amazon.com/es/compliance/programs/) para garantizar la seguridad de las instancias.
+
+VTEX no autoriza el acceso a las instalaciones o archivos para la realización de auditorías en nuestros sistemas y procedimientos internos. En su lugar, VTEX recibe informes de una empresa auditora especializada e independiente. Para demostrar nuestro cumplimiento y compromiso con la privacidad, seguridad, compliance y gobernanza, VTEX divulga sus documentos, políticas y certificaciones en un [portal de seguridad](https://vtex.com/mx-es/trust/). Asimismo, como parte del compromiso permanente con la seguridad, VTEX siempre busca obtener nuevas certificaciones.
+
+Los clientes tienen permiso para realizar[ escaneos de vulnerabilidad](https://help.vtex.com/es/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb#reportar-vulnerabilidade) en sus propios entornos, bajo dos condiciones: no realizar ataques reales que puedan impactar el sistema de producción y no intentar acceder a datos que no sean de su propiedad.
+
+### ¿Cómo se lleva a cabo la gestión de vulnerabilidades en términos concretos? ¿El proceso está documentado? ¿En qué medida se gestionan y corrigen las vulnerabilidades identificadas?
+
+Los escaneos de vulnerabilidad son realizados de forma continua por un grupo restringido de individuos autorizados utilizando sistemas aprobados y dedicados. Cuando se detectan vulnerabilidades en el sistema o software, accionamos un proceso de gestión de parches para realizar las correcciones necesarias. Nuestro equipo coordina efectivamente la participación de todos los desarrolladores responsables para apoyar la reproducción y, de ser necesario, el desarrollo de parches de seguridad. Después de la implementación de las correcciones, realizamos pruebas adicionales para garantizar la eficacia de las soluciones. Si los resultados son positivos, cerramos el caso y llevamos a cabo un análisis similar a la etapa de gestión de problemas, de ser necesario.
+
+## Monitoreo de seguridad
+
+### ¿Están protegidos los logs del sistema contra alteraciones, falsificaciones o accesos indebidos?
+
+Nuestras aplicaciones cuentan con sistemas de registro de auditoría que capturan y almacenan logs relevantes para garantizar compliance con nuestras normas internas y leyes aplicables. Los logs abarcan una variedad de eventos, incluyendo eventos de seguridad, privacidad y autenticación (inicios de sesión fallidos y exitosos y bloqueos de cuenta), de acuerdo con los requisitos normativos; además de los eventos básicos para nuestros análisis internos. De este modo, mantenemos un registro completo y detallado de todas las actividades relevantes en la plataforma y garantizamos la transparencia, seguridad y compliance en nuestras operaciones.
+
+### ¿VTEX registra eventos de seguridad?
+
+Nuestra organización utiliza una herramienta para centralizar los registros de actividad, así como para implementar recursos SIEM (Security Information and Event Management). Por lo general, los registros se conservan durante un periodo de 18 meses. Tanto las soluciones propias como las proporcionadas por AWS se utilizan para analizar continuamente la seguridad y examinar las vulnerabilidades en la nube. Estas herramientas se utilizan por lo menos trimestralmente.
+
+El equipo de VTEX es responsable de disponibilizar y mantener la solución actualizada con nuevas funcionalidades, además de monitorear todo su funcionamiento. También contamos con un equipo especializado que garantiza la capacidad de escalar la solución en periodos estacionales o durante un aumento en la demanda y continuamente monitorea el desempeño de las tiendas con base en una heurística propia.
+
+### ¿Protege VTEX el servidor de email contra spoofing (suplantación de identidad)?
+
+VTEX utiliza Google Workspace como su principal herramienta de comunicación. Para reforzar la seguridad de nuestro servidor de email contra falsificaciones, implementamos medidas como SPF (Sender Policy Framework) y DKIM (DomainKeys Identified Mail). SPF establece una lista de servidores y dominios autorizados para enviar emails a nombre de nuestra organización, mientras que DKIM agrega una firma digital única a cada mensaje enviado. Estas medidas garantizan que los servidores de destino puedan autenticar el origen de los mensajes, lo que ofrece una capa de protección adicional contra posibles actividades fraudulentas. El equipo de seguridad de VTEX es el único que gestiona estas configuraciones.
+
+### ¿Se protegen los endpoints con antivirus?
+
+Contamos con una sólida tecnología antivirus que integramos con todos nuestros endpoints y servidores. Esto es imprescindible para reforzar la seguridad no solo de nuestra infraestructura, sino también para proteger la información y datos sensibles de nuestros clientes. Al hacer obligatoria la instalación de antivirus en todos los dispositivos y servidores, mitigamos de forma proactiva las posibles ciberamenazas, garantizando así una experiencia segura y fiable para todos los que participan en nuestras operaciones.
+
+## Respuesta y mitigación de incidentes
+
+### ¿El plan de respuesta ante incidentes establece criterios de notificación?
+
+Sí, como parte de nuestros protocolos operativos, nos comprometemos a notificar a los clientes afectados dentro de un plazo máximo de 24 horas tras confirmar cualquier incidente de seguridad. Esto es importante para garantizar la transparencia y proporcionar la información necesaria a nuestros clientes para que puedan tomar medidas apropiadas para proteger sus datos y sistemas. Además, al divulgar la información de incidentes de seguridad con prontitud, demostramos nuestro compromiso continuo con la ciberseguridad y la confianza de nuestros clientes.
+
+## Recuperación ante desastres y continuidad de negocio
+
+### ¿Cuál es el RPO (Recovery Point Objective) y el RTO (Recovery Time Objective) de la recuperación ante desastres?
+
+El RPO es la antiguedad máxima de los datos de copia de seguridad antes de que se consideren obsoletos y está directamente relacionado con la política de retención de copia de seguridad. En VTEX, el RPO estándar es de 24 horas. Sin embargo, es importante resaltar que este plazo se refiere a la frecuencia de las copias de seguridad de Catálogo; en los sistemas transaccionales como Checkout, el punto de recuperación es la última transacción guardada.
+
+El RTO es el tiempo máximo permitido para que se restauren los servicios. El tiempo de inactividad de un servicio puede ser ocasionado por una interrupción de la aplicación, corrupción o pérdida de datos, fallos del servidor o interrupción en la zona o región de disponibilidad de AWS. Consulta el RTO estándar por tipo de inactividad en la siguiente tabla:
+
+| Tipo de inactividad | RTO estándar |
+|---|---|
+| Interrupción de la aplicación | 10 minutos |
+| Corrupción o pérdida de datos | 30 minutos |
+| Fallo del servidor de datos | 1 hora |
+| Interrupción de la zona de disponibilidad de AWS | 4 horas |
+| Interrupción en la región de AWS | 24 horas |
diff --git a/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 9f427c9b9..22c55e9a8 100644
--- a/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -17,7 +17,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Para comprender mejor el significado de cada campo de la plantilla de registro de precio fijo, vea la descripción completa de los ítems.
 
-![tabela.preço.fixo](https://images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
+![tabela.preço.fixo](//images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
 
 - **SKU ID:** el ID del SKU al que quiere añadir el precio fijo.
 - **Trade Policy:** el nombre o el ID de la política comercial a la que se aplicará el precio fijo.
diff --git a/docs/tutorials/es/filtering-all-orders.md b/docs/tutorials/es/filtering-all-orders.md
index 553f13d74..81e9cfec9 100644
--- a/docs/tutorials/es/filtering-all-orders.md
+++ b/docs/tutorials/es/filtering-all-orders.md
@@ -3,8 +3,8 @@ title: 'Filtrar pedidos en Todos los pedidos'
 id: tutorials_192
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:05.494Z
-updatedAt: 2023-05-31T14:45:05.491Z
-publishedAt: 2023-05-31T14:45:05.491Z
+updatedAt: 2023-12-21T14:06:54.896Z
+publishedAt: 2023-12-21T14:06:54.896Z
 firstPublishedAt: 2017-04-27T23:00:47.449Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,13 @@ legacySlug: como-filtrar-pedidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
+<div class = "alert alert-info">
+Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
+</div>
+
 En el módulo **Pedidos**, la página **Todos los pedidos** permite acceder a todos los pedidos de la tienda y buscar utilizando la barra de búsqueda y filtros según se muestra en la imagen a continuación:
 
-![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Este artículo explica cómo utilizar estos recursos y se divide en:
 
@@ -26,6 +30,13 @@ Este artículo explica cómo utilizar estos recursos y se divide en:
 - [Filtrar por status](#filtrar-por-status)
 - [Creado](#creado)
 
+Además de buscar pedidos en **Pedidos > Todos los pedidos**, puede buscar pedidos desde cualquier página del Admin VTEX utilizando la barra de búsqueda global en la parte superior de la página. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
 ## Barra de búsqueda
 
 Para realizar una búsqueda en la barra de búsqueda, ingresa el término deseado y pulsa la tecla `Intro`. Puedes buscar utilizando los siguientes criterios:
@@ -52,7 +63,7 @@ La búsqueda en todos los pedidos devuelve todos los pedidos relacionados con el
 
 Para buscar en todos los pedidos, ingresa el término deseado en la casilla de búsqueda. Se mostrará la opción <i class="fas fa-toggle-on"></i> `Remover límite de fechas`. Solo hay que activarla para iniciar la búsqueda.
 
-![search_bar_without_time_limit_ES](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/3e96ddad7e6e25df9bfc57510655390b/search_bar_without_time_limit_ES.png)
+![search_bar_without_time_limit_ES](//images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/3e96ddad7e6e25df9bfc57510655390b/search_bar_without_time_limit_ES.png)
 
 <div class="alert alert-danger">
 La búsqueda en todos los pedidos no se puede asociar a otros filtros. Es decir, al remover el límite de fechas de búsqueda, cualquier filtro activo pasa a estar inactivo. Si se remueve el término de búsqueda o se desactiva el botón de alternancia <i class="fas fa-toggle-off"></i>, los filtros configurados anteriormente se vuelven a activar.
@@ -70,7 +81,7 @@ Realizar una búsqueda con filtros permite combinar diferentes filtros que se de
 
 La página **Pedidos > Todos los pedidos** tiene la opción `Filtros` según se muestra en la imagen a continuación:
 
-![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Al hacer clic en `Filtros`, se muestra una ventana modal que presenta las siguientes opciones:
 
@@ -186,7 +197,7 @@ Para utilizar estos filtros, haz `Filtros` y selecciona **Otros**. Puedes buscar
 
 La página **Pedidos > Todos los pedidos** tiene la opción `Filtrar por status` <i class="fas fa-angle-down"></i> según se muestra en la siguiente imagen:
 
-![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Al hacer clic en `Filtrar por status` <i class="fas fa-angle-down"></i>, se muestran las opciones de [status de pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196) de tu tienda. Por ejemplo, si no hay pedidos cancelados entre todos tus pedidos, esta opción no estará visible.
 
@@ -198,7 +209,7 @@ Para más opciones de filtros de status, consulta la sección <a href="https://h
 
 La página **Pedidos > Todos los pedidos** tiene la opción `Creado: Hoy` <i class="fas fa-angle-down"></i> según se muestra en la siguiente imagen:
 
-![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Este filtro tiene la fecha **Hoy** activada como estándar, pero al hacer clic aparecen las siguientes opciones:
 
diff --git a/docs/tutorials/es/filtering-data-on-master-data.md b/docs/tutorials/es/filtering-data-on-master-data.md
index 19f80d8db..b33da8666 100644
--- a/docs/tutorials/es/filtering-data-on-master-data.md
+++ b/docs/tutorials/es/filtering-data-on-master-data.md
@@ -3,8 +3,8 @@ title: 'Filtrar datos en el Master Data'
 id: tutorials_778
 status: PUBLISHED
 createdAt: 2017-04-27T21:58:11.041Z
-updatedAt: 2023-03-28T23:42:30.477Z
-publishedAt: 2023-03-28T23:42:30.477Z
+updatedAt: 2024-06-27T00:07:07.554Z
+publishedAt: 2024-06-27T00:07:07.554Z
 firstPublishedAt: 2017-04-27T23:03:42.905Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,40 +15,55 @@ legacySlug: filtrar-datos-en-el-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-En el Master Data, es posible crear filtros tanto para acceso por API como para la visualización en los formularios. La creación de filtros facilita la búsqueda y la consulta de datos, posibilitando un mayor control sobre sus datos. La creación de filtro debe configurarse primero en la entidad de datos y posteriormente en el formulario deseado. El requisito para que un campo sea configurado como filtro es que no se utilicen los tipos CEP, Text y File. Además, es una buena práctica poner como filtro un campo que contenga pocas opciones en su llenado, como “Categoria”, por ejemplo.
-
-## Cómo configurar filtro en la Entidad de Datos
-
-1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
-2. En Master Data, haz clic en **Aplicações** > **Estrutura de dados.**
-2. Acceda a la pestaña **Entidade de Dados.**
-3. Haga clic en el botón **editar** en la entidad en la que desea configurar el filtro.
-4. Abrirá el listado de campos.
-5. Haga clic en el botón con símbolo de engranaje en el campo que desea configurar.
-6. Marque la opción **É filtro.**
-7. Haga clic en el botón **Salvar.**
-8. En el listado de entidades, haga clic en el botón **Publicar**, con símbolo de diskette.
-9. Espere la publicación y la reindexación de los datos para visualizar el filtro.
-
-## Cómo configurar filtro en el formulario
-
-1. Acceda al módulo **Master Data**;
-2. Haga clic en la pestaña **Aplicações**;
-3. En la aplicación en que está el formulario en el que desea crear el filtro, haga clic en el símbolo de engranaje;
-4. Se abrirá el listado de formularios, haga clic en el símbolo lápiz en el formulario que desea editar;
-5. Complete el campo **Filtros** con el nombre interno del campo marcado como Filtro. Se entiende nombre interno como la primera columna en la creación y edición de entidad de datos, el nombre que no es posible modificar. Para insertar más de un valor, basta separarlos por coma, sin espacio;
-6. Haga clic en el botón **Salvar**.
-
-## Cómo filtrar
-
-Tras la creación del filtro es posible utilizarlo en el formulario. Para ello, siga el paso a paso siguiente.
-
-1. Acceda al módulo **Master Data**;
-2. Haga clic en la pestaña **Aplicações**;
-3. En la aplicación deseada, identifique el formulario que desea visualizar;
-4. En el formulario deseado, haga clic en el icono de listado;
-5. Se abrirá la página con el listado de registros de ese formulario. En la lateral, usted verá los filtros configurados. 
-6. Para filtrar, basta hacer clic en el nombre del filtro y en su valor. 
-7. Para verificar el resultado en el filtro, haga rodar la página hacia abajo y haga clic en el botón **Filtrar**.
-8. Es posible filtrar por varios campos al mismo tiempo y varios valores en el mismo campo. Para retirar un filtro, basta hacer clic símbolo **x** al lado do valor.
+En Master Data puedes crear filtros tanto para el acceso vía API como para la vista en los formularios. La creación de filtros facilita la búsqueda y consulta de datos, proporcionando un mayor control sobre los mismos.
+
+La creación de filtros debe configurarse primero en la entidad de datos y después en el formulario deseado, según los pasos descritos en las secciones a continuación.
+
+## Requisitos para filtros
+
+Sigue las recomendaciones a continuación para definir campos de filtros:
+
+- No utilices campos de tipo **CEP**, **Text** y **File** como filtros.
+- Agrega como filtro un campo que contenga pocas opciones disponibles para rellenar, como "Categoría", por ejemplo.
+
+## Configurar filtro en la entidad de datos
+
+Sigue los pasos a continuación para definir un campo existente como filtro en la entidad de datos:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En Master Data, haz clic en el engranaje situado <i class="fas fa-cog"></i> junto al nombre de una aplicación.
+3. Haz clic en **Estructura de datos**.
+4. Accede a la pestaña **Entidades de datos**.
+5. Haz clic en el botón de editar <i class="fas fa-edit"></i> sobre la entidad en la que deseas configurar el filtro.
+
+   Serás redirigido a la lista de campos de la entidad.
+6. Haz clic en el botón con el símbolo de engranaje <i class="fas fa-cog"></i> en el campo que deseas configurar como filtro.
+7. Marca la casilla **¿Es filtrable?**.
+8. Haz clic en el botón `Guardar`.
+9. En la lista de entidades, haz clic en el botón de publicar <i class="fas fa-save"></i> para publicar la entidad.
+10. Haz clic en el botón de reindexar <i class="fas fa-expand-arrows-alt"></i> para indexar la entidad.
+
+## Configurar filtros en el formulario
+
+Sigue los pasos a continuación para configurar filtros en el formulario:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En la aplicación donde se encuentra el formulario en el que deseas crear el filtro, haz clic en el símbolo del engranaje <i class="fas fa-cog"></i>.
+
+   Serás redirigido a la lista de formularios de la aplicación.
+3. Haz clic en el botón de editar <i class="fas fa-edit"></i> en la fila del formulario que deseas editar.
+4. Rellena el campo **Filtros** con el nombre interno del campo marcado como filtro. El nombre interno corresponde al valor del primer campo al crear y editar la entidad de datos, y no se puede modificar. Para ingresar más de un valor solo hay que separarlos con una coma, sin espacio.
+5. Haz clic en el botón `Guardar`.
+
+## Filtrar registros del formulario
+
+Una vez creado el filtro ya puede utilizarse en el formulario. Para hacerlo, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
+2. En la aplicación deseada, identifica el formulario que deseas ver y haz clic en el ícono de lista <i class="fas fa-bars"></i>.
+
+   Serás redirigido a la lista de registros del formulario. En lado izquierdo verás los filtros configurados. 
+3. Para filtrar, selecciona el nombre del filtro y su valor, y haz clic en `Filtrar`.
+
+   Puedes filtrar por varios campos a la vez y por varios valores en el mismo campo. Para eliminar un filtro, basta con hacer clic en la `X` situada junto al valor.
 
diff --git a/docs/tutorials/es/filtering-transactions-on-pci-gateway.md b/docs/tutorials/es/filtering-transactions-on-pci-gateway.md
index 212ea1fa2..fcf2bb9d8 100644
--- a/docs/tutorials/es/filtering-transactions-on-pci-gateway.md
+++ b/docs/tutorials/es/filtering-transactions-on-pci-gateway.md
@@ -3,8 +3,8 @@ title: 'Filtrar transacciones en la sección de Pedidos'
 id: 6LUq65FqUgIKkKEeWa4IwC
 status: PUBLISHED
 createdAt: 2019-01-24T21:38:42.313Z
-updatedAt: 2023-03-26T21:29:36.950Z
-publishedAt: 2023-03-26T21:29:36.950Z
+updatedAt: 2023-10-18T16:58:56.709Z
+publishedAt: 2023-10-18T16:58:56.709Z
 firstPublishedAt: 2019-01-24T21:38:42.695Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/filters.md b/docs/tutorials/es/filters.md
new file mode 100644
index 000000000..19bc7793d
--- /dev/null
+++ b/docs/tutorials/es/filters.md
@@ -0,0 +1,51 @@
+---
+title: 'Filtros'
+id: k24mQQa9SjmhNWSwdqIMB
+status: PUBLISHED
+createdAt: 2024-06-27T16:43:43.811Z
+updatedAt: 2024-06-27T16:44:34.723Z
+publishedAt: 2024-06-27T16:44:34.723Z
+firstPublishedAt: 2024-06-27T16:44:34.723Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: filtros
+locale: es
+legacySlug: filtros
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+La funcionalidad Filtros muestra las especificaciones de los resultados de una búsqueda de forma agrupada. Permite que el cliente explore características relevantes de un producto durante la experiencia de búsqueda, además de proporcionar escenarios que facilitan la toma de decisiones del usuario.
+
+Cuando un cliente selecciona un filtro (precio, color, tamaño y marca), esta información se utiliza para restringir tanto los ítems devueltos como los demás filtros existentes en este contexto de búsqueda.
+
+**VTEX Intelligent Search** utiliza el contexto de los productos que se muestran como resultados de la búsqueda para saber exactamente qué filtros deben mostrarse al cliente, de acuerdo con la configuración del catálogo.
+
+<div class="alert alert-info">
+  <p>El orden de los filtros de marca, departamento, categoría y subcategoría se determina por la cantidad de productos registrados en cada uno de los filtros.</p>
+</div>
+
+Ejemplo: tenga en cuenta que el filtro *Tamaño* está registrado en el catálogo de una tienda y que solo el producto *zapatilla* tiene la especificación *Tamaño* rellenada. En una búsqueda por el término *zapatilla*, *Tamaño* aparecerá como un filtro. En la búsqueda de cualquier otro término, como *gorra*, esta especificación no se mostrará como un filtro.
+
+El resultado de búsqueda no mostrará una especificación si solo existe como filtro o si el cliente accede a ella a través del menú de la tienda. Ejemplo: si el cliente selecciona el filtro Electrodomésticos directamente en el menú, no se mostrará Departamento como filtro lateral.
+
+<div class="alert alert-info">
+  <p>Si el resultado de la búsqueda devuelve más de 30 mil productos, se omitirán algunos valores de filtros, ya que solo se considerarán las especificaciones de una parte de estos productos.</p>
+</div>
+
+La funcionalidad Filtros tiene las siguientes funciones:
+
+- Búsqueda que permite al cliente buscar un término dentro de un filtro.
+- Configurar y definir la cantidad máxima de opciones en un filtro antes de generar un desplazamiento.
+- Configurar en cuál *layout* se mostrará un filtro. Puede elegir entre los siguientes formatos:
+
+   - Lista vertical (formato estándar).
+   - Lista horizontal: se utiliza para mostrar filtros como «Tamaño» y «Color».
+   - Barra deslizante: utilizada para alternar del precio mínimo al precio máximo.
+   - Entrada de valores: permite al cliente indicar el precio “De” y “Hasta” que se utilizará en el filtro.
+
+Consulte la guía [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) en el Developer Portal para obtener más detalles técnicos sobre el uso de filtros.
+
+<div class="alert alert-warning">
+  <p>Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.</p>
+</div>
diff --git a/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
index 9c8e8665e..e6157f294 100644
--- a/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -1,10 +1,10 @@
 ---
 title: 'Marketplace Network: encuentre marketplaces y sellers en el ecosistema VTEX'
 id: 2bzC7tXlVgLEEjxo4ixcAM
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-09-14T22:21:50.677Z
-updatedAt: 2022-04-07T14:44:29.576Z
-publishedAt: 2022-04-07T14:44:29.576Z
+updatedAt: 2023-07-19T21:34:02.498Z
+publishedAt: 
 firstPublishedAt: 2020-09-14T23:03:21.356Z
 contentType: tutorial
 productTeam: Apps
@@ -20,7 +20,7 @@ Marketplace Network facilita el encuentro y la comunicación entre marketplaces
 Tenga en cuenta que *Marketplace Network* es una herramienta que promueve el contacto entre partners potenciales, pero no es una etapa obligatoria para convertirse en un *marketplace* o *seller* en VTEX. Sepa más sobre las [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
 ## Encontrar sellers y marketplaces
-![Marketplace network tour](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
+![Marketplace network tour](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
 
 Para acceder a la lista de marketplaces y sellers registrados, vaya a *Marketplace > Marketplace Network > Encontrar sellers / Encontrar marketplaces*. En ambas pestañas, puedes buscar por palabras clave y filtrar la lista para obtener resultados más precisos, así como contactar con potenciales partners.
 
@@ -43,7 +43,7 @@ El potencial partner comercial recibirá un email con la información ingresada.
 </div>
 
 ## Perfil de la tienda
-![Network profile ES](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/ae9aa04caa553c344ab6e5f958469e68/Marketplace_store_profile_ES.gif)
+![Network profile ES](//images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/ae9aa04caa553c344ab6e5f958469e68/Marketplace_store_profile_ES.gif)
 
 1. En la sección «Marketplace» de su tienda, haga clic en __Marketplace Network__.    
 2. Haga clic en la pestaña __Perfil de la tienda__.    
diff --git a/docs/tutorials/es/find-sellers.md b/docs/tutorials/es/find-sellers.md
new file mode 100644
index 000000000..77f9fd3c4
--- /dev/null
+++ b/docs/tutorials/es/find-sellers.md
@@ -0,0 +1,57 @@
+---
+title: 'Encontrar sellers'
+id: 6kkZaxIgfDyvN5trgIuwBl
+status: PUBLISHED
+createdAt: 2023-07-19T20:18:59.741Z
+updatedAt: 2023-07-19T20:46:01.656Z
+publishedAt: 2023-07-19T20:46:01.656Z
+firstPublishedAt: 2023-07-19T20:41:17.099Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: encontrar-sellers
+locale: es
+legacySlug: encontrar-sellers
+subcategory: 6riYYNZCpO8wyksi8Ksgyq
+---
+
+La página **Encontrar sellers** facilita la búsqueda y comunicación con sellers que operan en el ecosistema VTEX,lo que abre oportunidades de nuevas actividades comerciales y crecimiento mutuo para todas las partes. La página funciona como un catálogo de partners interesados y permite el registro, la consulta y el contacto entre marketplaces y sellers para que firmen acuerdos comerciales.
+
+Para utilizar la página,debes crear un **Perfil de la tienda**,según se describe en la documentación.
+
+<div class="alert alert-info">
+  Ten en cuenta que <b>Encontrar sellers</b> es una herramienta que promueve el contacto entre posibles partners, sin embargo, no es un paso obligatorio para operar como marketplace y seller en VTEX.
+Si deseas operar como marketplace y seller simultáneamente, lee la documentación <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace">Estrategias de marketplace en VTEX.</a>
+</div>  
+
+Para acceder a la lista de sellers registrados, ve a **Marketplace > Encontrar sellers** o ingresa **Encontrar sellers** en la barra de búsqueda.
+
+## Buscary filtrar
+
+Puedes utilizar la barra de búsqueda de la página para buscar por nombre del seller o nombre de la cuenta VTEX. También puedes filtrar la lista de forma combinada o individual para obtener resultados más precisos y enviar mensajes a partners potenciales.
+
+**Filtros fijos**
+
+- País
+- Segmento
+
+**Filtro condicional**
+
+- Región
+
+## Contacto
+
+La página **Encontrar sellers** permite el contacto directo con partners potenciales. Al hacer clic en los perfiles de la lista, puedes acceder a los datos del seller. Ten en cuenta que solo puedes enviar mensajes después de activar tu **Perfil de la tienda**.
+
+Cuando envíes un mensaje, proporciona toda la información que ese seller necesita para conectarse con tu empresa. También sugerimos anticipar las dudas o puntos que pudieran discutirse en una futura reunión.
+
+Para ponerte en contacto:
+
+1. En la sección Marketplace de tu Admin VTEX, haz clic en **Encontrar sellers** o ingresa **Encontrar sellers** en la barra de búsqueda.
+1. En la lista, haz clic en el **perfil** de un partner potencial.
+1. Rellena el campo **Contactar seller**.
+1. Haz clic en el botón **Enviar**.
+
+<div class="alert alert-info">
+El partner potencial recibirá un email con la información incluida. Si el interés es mutuo,el encargado del seller o el marketplace puede ponerse en contacto contigo y negociar las condiciones del acuerdo entre marketplace y seller.
+</div>
diff --git a/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
index bfd39f900..15d8d7731 100644
--- a/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
@@ -26,7 +26,7 @@ A partir del 17 de enero de 2023, la nueva interfaz será el estándar de todas
 
 En la imagen a continuación, puedes ver la correspondencia de secciones y campos entre la versión antigua de la página **Detalles del pedido** y la nueva versión:
 
-![board_comparativo_interface_pedido_v2_es](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
+![board_comparativo_interface_pedido_v2_es](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
 
 ## ¿Qué pasó con el filtro de búsqueda de seis meses?
 
@@ -38,17 +38,17 @@ La búsqueda en todos los pedidos no puede asociarse a otros filtros, por lo que
 
 Para buscar en todos los pedidos, ingresa el término deseado en la casilla de búsqueda. Se mostrará la opción <i class="fas fa-toggle-off"></i> `Remover límite de fechas`. Solo tienes que activarla para iniciar la búsqueda.
 
-![busca_sem_limite_data_all_es](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
+![busca_sem_limite_data_all_es](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
 
 ## ¿Cómo ver el diagrama de flujo del pedido?
 
 En la nueva interfaz, el estándar es mostrar una línea de tiempo con los eventos de **Status del pedido** según ilustrado en la siguiente imagen:
 
-![timeline_pedido_es](https://images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/60bd22f37e038db53247d83f3252efe1/timeline_pedido_es.png)
+![timeline_pedido_es](//images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/60bd22f37e038db53247d83f3252efe1/timeline_pedido_es.png)
 
 Si deseas ver el **Diagrama del pedido** como en la interfaz anterior, haz clic en `Ver diagrama` y aparecerá una ventana modal según se muestra en la imagen a continuación:
 
-![diagrama_pedido_es](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
+![diagrama_pedido_es](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
 
 ## ¿Cómo facturar el pedido?
 
@@ -56,7 +56,7 @@ En la sección **Ítems a facturar** de la nueva interfaz, se puede acceder a to
 
 * **Enviar factura con la referencia de los ítems:** esta opción solo aparece en la nueva interfaz y permite emitir la factura total o parcial de determinados ítems, que se identifican por SKU, stock y precio. Ve un ejemplo en la siguiente imagen:
 
-![faturar_referenciar_pedidos_final_es](https://images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/2427b16f419457736699f1cae0cf3dd3/faturar_referenciar_pedidos_final_es.png)
+![faturar_referenciar_pedidos_final_es](//images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/2427b16f419457736699f1cae0cf3dd3/faturar_referenciar_pedidos_final_es.png)
 
 * **Enviar una sola factura:** esta opción corresponde a la antigua _Enviar factura_ y permite facturar el valor total o parcial del pedido. La presentación de la página es diferente, pero los campos siguen siendo los mismos.
 
@@ -75,6 +75,6 @@ En la sección **Historial del pedido**, hay una línea de tiempo que presenta l
 
 Para reenviar un email al cliente, haz clic en el evento de email enviado o en el ícono de flecha <i class="fas fa-angle-right"></i> para ver los detalles del evento, que aparecerán como se muestra en la siguiente imagen:
 
-![enviar_email_es](https://images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/a4d25f7e071dd7f4c23cbcd157d8008a/enviar_email_es.png)
+![enviar_email_es](//images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/a4d25f7e071dd7f4c23cbcd157d8008a/enviar_email_es.png)
 
 Haz clic en el botón Reenviar email y se reenviará el email inmediatamente al cliente y se mostrará el siguiente mensaje de confirmación: _El email se reenvió con éxito al cliente_.
diff --git a/docs/tutorials/es/fulfillment-logistics-vtex.md b/docs/tutorials/es/fulfillment-logistics-vtex.md
index 2ee8a8aa3..99bbcd7fc 100644
--- a/docs/tutorials/es/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/es/fulfillment-logistics-vtex.md
@@ -47,7 +47,7 @@ Para saber qué configuraciones logísticas son necesarias y cómo realizarlas,
 <div class = "alert alert-info">Ten en cuenta que el proceso de envío dependerá de la configuración realizada en la plataforma. Aquí presentamos los escenarios para cada tipo de envío (entrega y recogida), pero hay otros flujos posibles en el proceso de envío. Por ejemplo, cuando se realiza el envío por recogida y el almacén coincide con el punto de recogida, no es necesario transportar los paquetes entre estos lugares.
 </div>
 
-![Envio ES](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/b45650074aea4947a048e8140434fa46/Envio_ES.svg)
+![Envio ES](//images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/b45650074aea4947a048e8140434fa46/Envio_ES.svg)
 ## Configuración del proceso logístico
 
 El proceso logístico debe configurarse según las necesidades de tu tienda. Estas configuraciones se hacen en el módulo **Envío**. Mira las funcionalidades disponibles en el módulo y cómo afecta cada una de ellas a tu negocio:
diff --git a/docs/tutorials/es/fulfillment-magalu.md b/docs/tutorials/es/fulfillment-magalu.md
new file mode 100644
index 000000000..f9524ee3e
--- /dev/null
+++ b/docs/tutorials/es/fulfillment-magalu.md
@@ -0,0 +1,18 @@
+---
+title: 'Fulfillment Magalu'
+id: 7ckyEv4Z8HmiCRydo0a9P6
+status: PUBLISHED
+createdAt: 2023-12-19T19:09:47.849Z
+updatedAt: 2024-01-05T11:58:20.772Z
+publishedAt: 2024-01-05T11:58:20.772Z
+firstPublishedAt: 2023-12-19T19:44:22.896Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: fulfillment-magalu
+locale: es
+legacySlug: fulfillment-magalu
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning" role="alert">Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.</div>
diff --git a/docs/tutorials/es/general-configurations-on-the-oms.md b/docs/tutorials/es/general-configurations-on-the-oms.md
index 12f8daf06..f8315ce12 100644
--- a/docs/tutorials/es/general-configurations-on-the-oms.md
+++ b/docs/tutorials/es/general-configurations-on-the-oms.md
@@ -3,8 +3,8 @@ title: 'Configuraciones Generales de los Pedidos'
 id: tutorials_194
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:49.644Z
-updatedAt: 2023-03-29T16:11:56.900Z
-publishedAt: 2023-03-29T16:11:56.900Z
+updatedAt: 2024-07-02T19:07:22.178Z
+publishedAt: 2024-07-02T19:07:22.178Z
 firstPublishedAt: 2017-04-27T23:00:47.468Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -19,7 +19,7 @@ Es posible realizar configuraciones directamente relacionadas con las condicione
 
 En el Admin VTEX, accede a **Configuración de la tienda > Pedidos > Configuración**, o escribe *Pedidos* en la barra de búsqueda en la parte superior de la página, y haga clic en *Configuración de la tienda / Pedidos*.  
 
-![configuracoes_pedidos_es](https://images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/228fb71ccb74cc99cb820bac2b5a94d1/configuracoes_pedidos_es.png)
+![configuracoes_pedidos_es](//images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/228fb71ccb74cc99cb820bac2b5a94d1/configuracoes_pedidos_es.png)
 
 ## Carrito
 
@@ -33,7 +33,7 @@ Esta configuración es un flag que activa o inactiva la exigencia de una autenti
 
 - **Cantidad mínima de ítems en el carrito:** _Estándar: 1 ítem._ Esto impedirá que el cliente cierre la compra sin tener al menos el valor en cantidad de ítems igual al definido en este campo.
 - **Cifras decimales que se considerarán:** _Estándar: 2 cifras._ Esto hará con que los precios de los Productos sean ilustrados de acuerdo con la cantidad de cifras decimales definidas. No se hará redondeo de valor. 
-- **Valor mínimo total del carrito:** _Estándar: R$ 0,10._ Así como la cantidad mínima de ítems en el carrito, esto impedirá que el cliente cierre la compra sin tener al menos el valor en productos igual al definido en este campo.
+- **Valor mínimo total del carrito:** _Estándar: R$ 0,10._ Así como la cantidad mínima de ítems en el carrito, esto impedirá que el cliente cierre la compra sin tener al menos el valor en productos igual al definido en este campo. El valor mínimo del carrito también incluye tasas y costos de envío. Es el valor final del pedido que está siendo calculado.
 
 ## Pedidos
 
diff --git a/docs/tutorials/es/geolocation-at-checkout.md b/docs/tutorials/es/geolocation-at-checkout.md
index 8138f7492..b389d9a34 100644
--- a/docs/tutorials/es/geolocation-at-checkout.md
+++ b/docs/tutorials/es/geolocation-at-checkout.md
@@ -42,7 +42,7 @@ Cuando tengas la API, siga los pasos adelante:
 1. En el Admin VTEX, accede a __Configuración de la tienda > Envío > Envío por geolocalización__, o escribe __Envío por geolocalización__ en la barra de búsqueda en la parte superior de la página.
 2. Ponga la API Key en el campo disponible y haga un click en __Registrar Llave__.
 
-![Geolocalizacao 1 ES](https://images.ctfassets.net/alneenqid6w5/3XL4C5B5SM48uGaeocUiw4/22560c9c40cc587cb7fa0884e48fcd5f/Geolocalizacao_1_ES.png)
+![Geolocalizacao 1 ES](//images.ctfassets.net/alneenqid6w5/3XL4C5B5SM48uGaeocUiw4/22560c9c40cc587cb7fa0884e48fcd5f/Geolocalizacao_1_ES.png)
 
 <div class="alert alert-info">
 En algunos paises, el Google Maps no hace un mapping de buena calidad, lo que hace con que las direcciones queden mal escritas o incorrectas. En estes casos, la dirección debe ser alterada directamente en el mapa.
@@ -61,7 +61,7 @@ Después de crear el poligono y insertar el ID en la planilla de flete de la tra
 3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Checkout__.
 4. En el campo **Google Maps API Key**, inserte la misma API Key utilizada en la etapa de logística.
 
-![Google map keys](https://images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/687470ae8e86c210d778e34057af2a5c/google_maps_api_key_es.PNG)
+![Google map keys](//images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/687470ae8e86c210d778e34057af2a5c/google_maps_api_key_es.PNG)
 
 Asi que la API Key sea informada en las configuraciónes del Checkout, la geolocalización ya va estar visible en el checkout de la tienda.
 
diff --git a/docs/tutorials/es/gift-card.md b/docs/tutorials/es/gift-card.md
index f666e59bf..8499b2a24 100644
--- a/docs/tutorials/es/gift-card.md
+++ b/docs/tutorials/es/gift-card.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar Tarjeta de regalo'
 id: tutorials_995
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T21:57:54.816Z
-updatedAt: 2023-04-27T17:11:31.494Z
-publishedAt: 2023-04-27T17:11:31.494Z
+updatedAt: 2024-01-19T19:16:50.349Z
+publishedAt: 2024-01-12T12:46:20.978Z
 firstPublishedAt: 2017-04-27T23:03:42.674Z
 contentType: tutorial
 productTeam: Financial
@@ -33,13 +33,14 @@ Para crear un nuevo vale de compra, siga los pasos a continuación:
   <li>Haga clic en el botón azul <b>Nuevo vale</b>.</li>
   <br>   
 <div class = "alert alert-info">
-  <p>En la página de finalización, el campo <b>Vale</b> es el ID del vale. Esto es generado automáticamente por el sistema VTEX y se mostrará en el SmartCheckout para vales que no estén asociados con un CPF o CNPJ exclusivo.</p>
+  <p>En la pantalla de creación del vale, el campo <b>Vale</b> es llenado automáticamente por el sistema VTEX con el código ID del nuevo vale. Este es el código que debe ingresar el cliente en la pantalla de checkout para aplicar el vale al carrito y reducir el valor de pago del pedido.</p>
 </div>
 <br>
   <li>Complete los campos presentados de acuerdo con las orientaciones que se indican a continuación:</li>
   <br>
 <ul>  
   <li><b>Valor</b>: valor nominal que se concederá para el uso del vale.</li>
+  <li><b>Código de moneda</b>: moneda en la que se creará el vale. Las opciones disponibles para la selección se presentan de acuerdo con las políticas comerciales de cada tienda.</li>
   <li><b>Fecha de vencimiento</b>: es la fecha de vigencia de uso del vale.</li>
   <li><b>Doc. de identificación</b>: dato que identifica y define el vale para un cliente específico.</li>
   <li><b>Colección</b>: determina la colección de productos que define los ítems a los que se puede aplicar el vale.</li>
@@ -79,8 +80,9 @@ Para crear más de un nuevo vale de compra al mismo tiempo (un lote), siga los p
   <li>Complete los campos presentados de acuerdo con las orientaciones que se indican a continuación:</li>
 <br>
 <ul>
-  <li><b>Cantidad de vales</b>: este es el número de vales que desea crear como lote. Se puede crear un máximo de 500 (quinientos) vales por lote;</li>
+  <li><b>Cantidad de vales</b>: este es el número de vales que desea crear como lote. Se puede crear un máximo de 500 (quinientos) vales por lote.</li>
   <li><b>Valor</b>: valor nominal que se concederá a todos los vales de este lote;</li>
+  <li><b>Código de moneda</b>: moneda en la que se agruparán los vales. Las opciones disponibles para la selección se presentan de acuerdo con las políticas comerciales de cada tienda.</li>
   <li><b>Fecha de vencimiento</b>: es la fecha de vigencia de uso de todos los vales de este lote.</li>
   <li><b>Colección</b>: determina la colección de productos que define los ítems a los que se pueden aplicar los vales.</li>
 <br>
@@ -108,9 +110,9 @@ La creación de cupones no tiene límite, sin embargo, solo se pueden exportar 8
 
 ## Cómo configurar un Vale de Compra como un método de pago 
 
-<div style="text-align: justify"> ¡Perfecto! Ahora que su vale de compra se creó, es necesario configurarlo como un método de pago. Eso hará que su Gift Card se muestre en el Checkout y, así, sus clientes podrán finalizar compras utilizando el crédito del vale.</div>
+Después de crear el vale de compra, debe configurarse como método de pago. De esta manera, sus clientes podrán usarlo en el Checkout.
 
-Realice las siguientes instrucciones: 
+Siga los pasos a continuación para configurar el vale de compra:
 
 1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
diff --git a/docs/tutorials/es/google-analytics-faq.md b/docs/tutorials/es/google-analytics-faq.md
index 35eef7191..16742f4de 100644
--- a/docs/tutorials/es/google-analytics-faq.md
+++ b/docs/tutorials/es/google-analytics-faq.md
@@ -3,8 +3,8 @@ title: 'Google Analytics: preguntas frecuentes'
 id: 2VRtB07muo3vwO6KEmMVn0
 status: PUBLISHED
 createdAt: 2021-12-17T18:41:26.175Z
-updatedAt: 2023-03-31T15:22:28.277Z
-publishedAt: 2023-03-31T15:22:28.277Z
+updatedAt: 2023-07-31T18:35:26.120Z
+publishedAt: 2023-07-31T18:35:26.120Z
 firstPublishedAt: 2021-12-17T18:53:43.536Z
 contentType: tutorial
 productTeam: Others
@@ -15,6 +15,8 @@ legacySlug: google-analytics-preguntas-frecuentes
 subcategory: 1luKrYptdi8WoMYckakUaM
 ---
 
+Consulta a continuación las respuestas a algunas de las preguntas más frecuentes sobre Google Analytics en tiendas VTEX.
+
 ## ¿Cómo instalar Google Analytics en tu tienda?
 
 La instalación se realiza a través de [Google Tag Manager](https://help.vtex.com/es/tutorial/integracao-com-o-google-tag-manager#), como se describe en el artículo [Configuración de Google Analytics en tiendas VTEX](https://help.vtex.com/es/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG#).
@@ -31,26 +33,37 @@ La información disponible en la plataforma de Google proviene de los desencaden
 
 Los modelos de atribución dictan la metodología utilizada por una plataforma para atribuir una causa a un evento determinado. Cuando hablamos de Google Analytics, esto significa definir si una determinada venta en una tienda se produjo como resultado de un anuncio en una red social o de un email marketing, por ejemplo.
 
-Obtén más información sobre los [modelos de atribución en Google Analytics](https://support.google.com/analytics/answer/1662518?hl=es)
+Obtén más información sobre los [modelos de atribución en Google Analytics](https://support.google.com/analytics/answer/1662518?hl=es).
 
-## ¿Por qué hay divergencia en las métricas mostradas en VTEX y en Google Analytics?
+## ¿Por qué las métricas que se muestran en VTEX y en Google Analytics son diferentes?
 
 Hay diferencias en la forma en que cada plataforma obtiene los datos de tu tienda y esto puede dar lugar a cifras diferentes en el análisis. A continuación indicamos algunos de los casos más frecuentes y explicamos cómo interpretar estas diferencias.
 
 ### Transacciones
 
-Las divergencias en el registro de las transacciones suelen deberse a alguna irregularidad en el desencadenamiento de la [etiqueta de Google Analytics](https://help.vtex.com/es/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG#). En este caso, puede haber una duplicación o falla en el desencadenamiento.
+Como VTEX procesa las transacciones de tu tienda, todas las transacciones se registran en la plataforma. Sin embargo, en Google Analytics a veces hay irregularidades o fallas en la activación de la tag correspondiente. Algunos ejemplos son:
+
+- Navegadores con estricta configuración de privacidad.
+- Navegadores que bloquean JavaScript.
+- Bloqueadores de anuncios.
+- Error de configuración de la capa de datos de Google Analytics. Consulta la documentación oficial de Google para ver más información sobre cómo tu equipo de desarrollo puede [configurar la capa de datos de Google Analytics 4](https://developers.google.com/tag-manager/ecommerce-ga4).
+- La tag de transacción se activa incluso con transacciones que no se completaron con éxito.
+- Falla o duplicación de la visualización de la página de confirmación del pedido, si la tag de transacción está vinculada a la visualización de esta página.
+
+<div class = "alert alert-info">
+También debes tener en cuenta que hay un retraso de hasta 48 horas en el registro de datos de transacciones en Google Analytics.
+</div>
 
 Además, las integraciones pueden construirse de forma que acaben por no desencadenar determinadas etiquetas en tu storefront. Por ejemplo, hay integraciones que utilizan una [aplicación de pago](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-app) y finalizan la compra sin redirigir al cliente a la página de confirmación del pedido, como la integración desarrollada por AME Digital. Las transacciones siempre se registrarán en VTEX, pero en este caso es probable que no se registre en Google Analytics, generando divergencias.
 
 ### Atribución de ventas
 
-Es normal que existan diferencias entre la atribución en el módulo de **Pedidos** VTEX y en Google Analytics, ya que son herramientas diferentes con modelos de atribución distintos y que capturan la información a través de diferentes cookies.
+Es normal que existan diferencias entre la atribución en la plataforma VTEX y en Google Analytics, ya que son herramientas diferentes con [modelos de atribución](#que-son-los-modelos-de-atribucion) distintos y que capturan la información a través de diferentes cookies.
 
-La información de UTM reconocida por VTEX se puede verificar en el panel de herramientas para desarrolladores de tu navegador, en el objeto `marketingData` del [OrderForm.](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview#orderform-fields) Obtén más información en este artículo sobre las [UTM de marketing en el checkout.](https://help.vtex.com/es/tutorial/identificar-se-utms-de-marketing-estao-sendo-passadas-para-o-checkout--6kjHHfOWIgeI26qcQSU4Wg#)
+La información de UTM reconocida por VTEX se puede verificar en el panel de herramientas para desarrolladores de tu navegador, en el objeto `marketingData` del [OrderForm](https://developers.vtex.com/docs/guides/orderform-fields). Obtén más información en este artículo sobre las [UTM de marketing en el checkout](https://help.vtex.com/es/tutorial/identificar-se-utms-de-marketing-estao-sendo-passadas-para-o-checkout--6kjHHfOWIgeI26qcQSU4Wg#).
 
 Google Analytics utiliza por defecto el modelo de Última interacción.
-También se pueden utilizar diferentes modelos, descritos en la [documentación de Google Analytics sobre modelos de atribución.](https://support.google.com/analytics/answer/1662518?hl=es)
+También se pueden utilizar diferentes modelos, descritos en la [documentación de Google Analytics sobre modelos de atribución](https://support.google.com/analytics/answer/1662518?hl=es).
 
 Si también analizas los datos de los anuncios de Facebook, puedes encontrar otras divergencias. Por ejemplo, Facebook tendrá en cuenta a los clientes que vieron el anuncio y compraron en algún momento posterior, aunque hayan llegado a la tienda por otro camino en el momento de la compra.
 
@@ -68,9 +81,11 @@ A pesar de las diferencias, cabe destacar que ambas plataformas consideran que u
 
 ### Embudo de ventas
 
-Así como las sesiones son registradas por VTEX, hay una interpretación de los datos de navegación entre las páginas de productos y el flujo del carrito de compra. Con esto, VTEX genera la visualización del embudo de ventas.
+VTEX genera una visualización del embudo de ventas de tu tienda a partir de los registros de navegación generados por la plataforma, desde las páginas de producto hasta el flujo de carrito de compras y checkout.
+
+Por su parte, Google Analytics proporciona un embudo de ventas que se genera automáticamente con base en las tags de Google que estén configuradas en tu frontend. Aprende más sobre [cómo Google genera la visualización del embudo](https://support.google.com/analytics/answer/6014872#zippy=%2Ccontenido-del-art%C3%ADculo).
 
-Mientras que [Google Analytics tiene un embudo de ventas generado automáticamente](https://support.google.com/analytics/answer/6014872#zippy=%2Cin-this-article%2Cneste-artigo), basado en las etiquetas de Google, configuradas en tu storefront.
+Las visualizaciones del embudo, por estar basadas en información diferente, pueden presentar divergencias.
 
-Además, puedes configurar otro embudo de ventas en Google Analytics, que permite una visión personalizada y un mejor control de la jornada de compra. Consulta este artículo sobre cómo [implementar este embudo de ventas en Google Analytics](https://help.vtex.com/es/tutorial/configurar-funil-de-vendas-no-google-analytics#).
+Puedes configurar otro embudo de ventas en Google Analytics, que permite una vista personalizada y un mejor control de la jornada de compra. Consulta este artículo sobre cómo [implementar el embudo de ventas en Google Analytics](https://help.vtex.com/es/tutorial/configurar-funil-de-vendas-no-google-analytics).
 
diff --git a/docs/tutorials/es/google-integration-warnings.md b/docs/tutorials/es/google-integration-warnings.md
new file mode 100644
index 000000000..e1076c0c6
--- /dev/null
+++ b/docs/tutorials/es/google-integration-warnings.md
@@ -0,0 +1,20 @@
+---
+title: 'Avisos de integración de Google'
+id: 4BC0Epit2hACKbkBSqDR2A
+status: PUBLISHED
+createdAt: 2024-07-01T15:16:46.324Z
+updatedAt: 2024-07-01T20:42:52.728Z
+publishedAt: 2024-07-01T20:42:52.728Z
+firstPublishedAt: 2024-07-01T16:13:33.089Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: avisos-de-integracion-de-google
+locale: es
+legacySlug: avisos-de-integracion-de-google
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+<div class="alert alert-warning">
+Contenido en traducción.
+</div>
diff --git a/docs/tutorials/es/google-pay-beta.md b/docs/tutorials/es/google-pay-beta.md
index 101c5fffb..8a3e5769b 100644
--- a/docs/tutorials/es/google-pay-beta.md
+++ b/docs/tutorials/es/google-pay-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Google Pay (Beta)'
 id: 653pNFOw6L5CvGupLosJSq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-26T15:34:40.825Z
-updatedAt: 2023-06-14T19:34:39.943Z
-publishedAt: 2023-06-14T19:34:39.943Z
+updatedAt: 2023-06-27T21:56:34.229Z
+publishedAt: 
 firstPublishedAt: 2023-04-26T20:03:44.992Z
 contentType: tutorial
 productTeam: Shopping
@@ -40,7 +40,7 @@ Para activar Google Pay, sigue los pasos a continuación.
 
 Una vez hecho esto, Google Pay estará disponible en el checkout de tu tienda VTEX como nuevo medio de pago. La configuración puede demorarse alrededor de 10 minutos en aparecer en el checkout.
 
-![google pay - ES](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/fc1aa919d82b228ed26d2a967f4a4064/image.png)
+![google pay - ES](//images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/fc1aa919d82b228ed26d2a967f4a4064/image.png)
 
 <div class = "alert alert-warning">
 <p>Google Pay, por el momento, no admite suscripciones.</p>
diff --git a/docs/tutorials/es/headless-cms-overview.md b/docs/tutorials/es/headless-cms-overview.md
new file mode 100644
index 000000000..cfa99d44b
--- /dev/null
+++ b/docs/tutorials/es/headless-cms-overview.md
@@ -0,0 +1,53 @@
+---
+title: 'Headless CMS - Visión general'
+id: 3U5gvhHdQL0jczYH8gjX09
+status: PUBLISHED
+createdAt: 2023-12-15T20:27:39.404Z
+updatedAt: 2024-02-16T01:12:18.561Z
+publishedAt: 2024-02-16T01:12:18.561Z
+firstPublishedAt: 2023-12-18T13:33:50.044Z
+contentType: tutorial
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-visao-geral
+locale: es
+legacySlug: headless-cms-visao-geral
+subcategory: 27t6x0lngvjI3bnUg5AgEO
+---
+
+Headless CMS es un sistema de gestión de contenido desarrollado por VTEX para brindar a las empresas la flexibilidad de crear y entregar contenido en diversos canales, como sitios web y aplicaciones móviles.
+
+El término *headless* se refiere a la independencia existente entre la interfaz que muestra el contenido al usuario, o frontend, y el sistema responsable de gestionar y almacenar ese contenido, o backend. Este método permite que la gestión de contenido se produzca de forma independiente respecto a la interfaz de usuario, proporcionando flexibilidad y escalabilidad. Por ejemplo, un retailer puede actualizar una página de producto a través de Headless CMS sin que esto afecte la experiencia del usuario en el sitio web, lo que simplifica el mantenimiento de los contenidos y permite reutilizar los datos.
+
+Para acceder a Headless CMS, inicia sesión en el Admin VTEX > **Storefront > Headless CMS**. 
+
+<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+  Para gestionar el Headless CMS, asegúrese de que los <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos</a> <i>See CMS menu on the top-bar</i>, <i>Settings</i>, and <i>CMS GraphQL API</i> estén asociados con su <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol de usuario </a>. De lo contrario, <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol">cree un rol de usuario</a> y agregue estos recursos o añádalos a un rol de usuario existente.
+</div>
+
+Con Headless CMS puedes:
+
+- [Gestionar Proyectos](#gestionar-proyectos)
+- [Gestionar páginas](#gestionar-páginas)
+- [Gestionar content types de tipo Singleton](#gestionar-content-types-de-tipo-singleton)
+
+## Gestionar proyectos
+
+[Proyectos](https://help.vtex.com/es/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) es una funcionalidad de Headless CMS que permite crear y gestionar varios proyectos frontend, como aplicaciones móviles, sitios web e email marketing desde un único panel de control. 
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
+
+Para más información, consulta Gestionar Proyectos. 
+
+## Gestionar páginas
+En cada proyecto, también puedes gestionar todas las rutas de URL y modelos de página para el sitio web de tu tienda, incluyendo la página de inicio, la de producto (PDP) y otras. Para más información, consulta [Gestión de páginas en Headless CMS](https://help.vtex.com/es/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt).
+
+## Gestionar content types de tipo Singleton
+Singleton es un tipo de contenido que simplifica la gestión de contenido mediante la creación y gestión de una única página, garantizando la existencia de una única versión de este tipo de contenido en Headless CMS. Este método mejora la fiabilidad del contenido y simplifica la creación y mantenimiento del mismo en un entorno Headless CMS.  Para más información, consulta [Cómo gestionar content types Singleton](https://help.vtex.com/es/tutorial/managing-singleton-content-types--VBibMN1BqV2OFmavUFCdo).
+
+## Próximos pasos
+Consulta los siguientes tutoriales para empezar a gestionar el contenido de tu storefront:
+
+- [Gestionar Proyectos](https://help.vtex.com/es/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) 
+- [Gestión de páginas en Headless CMS](https://help.vtex.com/es/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt)
+- [Gestión de content types de tipo Singleton](https://help.vtex.com/en/tutorial/managing-singleton-content-types--VBibMN1BqV2OFmavUFCdo)
diff --git a/docs/tutorials/es/how-and-when-do-i-receive-my-invoice.md b/docs/tutorials/es/how-and-when-do-i-receive-my-invoice.md
index 58f240422..56c0c5d55 100644
--- a/docs/tutorials/es/how-and-when-do-i-receive-my-invoice.md
+++ b/docs/tutorials/es/how-and-when-do-i-receive-my-invoice.md
@@ -3,8 +3,8 @@ title: '¿Cómo y cuándo recibo mi factura y mi boleto bancario?'
 id: 4kRivWUH68iQ6AwI2QU6gm
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:47.627Z
-updatedAt: 2020-05-12T18:36:27.081Z
-publishedAt: 2020-05-12T18:36:27.081Z
+updatedAt: 2023-10-11T20:31:33.338Z
+publishedAt: 2023-10-11T20:31:33.338Z
 firstPublishedAt: 2019-01-24T22:08:59.617Z
 contentType: tutorial
 productTeam: Billing
@@ -15,16 +15,16 @@ legacySlug: como-y-cuando-recibo-mi-factura-y-mi-boleto-bancario
 subcategory: 5ZfsNR4ioEsIyu6wkyce0M
 ---
 
-<div class="alert alert-info" role="alert"><strong>ATENCIÓN: Este procedimiento es apenas para clientes facturados en Brasil.</strong></div>
-
+<div class="alert alert-warning" role="alert">
+  <p>Este procedimiento es apenas para clientes facturados en <strong>Brasil</strong>.</p>
+</div>
 
 La facturación se dispara hasta el quinto día hábil del mes. La factura y el boleto bancario están disponibles en el módulo __Facturas__ del Admin de su tienda.
 
 Cuando se realiza un cobro, enviamos un e-mail a los contactos registrados avisando de que la factura y el boleto bancario ya están disponibles para el pago o la consulta.
 
-Si no ha recibido el aviso hasta el quinto día hábil del mes, [consulte su panel administrativo](/es/tutorial/como-descargar-boletos-y-facturas-de-vtex). Si identifica alguna divergencia, [entre en contacto](https://support.vtex.com/hc/es-es/requests) con nuestro equipo financiero.
+Si no ha recibido el aviso hasta el quinto día hábil del mes, [consulte su panel administrativo](https://help.vtex.com/es/tutorial/como-descargar-las-facturas-de-vtex--tutorials_653). Si identifica alguna divergencia, [entre en contacto](https://support.vtex.com/hc/es-es/requests) con nuestro equipo financiero.
 
 Si no puede descargar su boleto bancario, es posible que no tenga un perfil financiero configurado en la cuenta de la tienda. En este caso, solicite al Super Admin de la cuenta que lo agregue.  
-  
-Si no está recibiendo el correo electrónico que informa que el boleto bancario está disponible para descargar en la plataforma, es posible que el correo electrónico no esté registrado como contacto financiero. En este caso, abra un [ticket](https://help-tickets.vtex.com/smartlink/sso/login/zendesk) para solicitar la inclusión del correo electrónico en los contactos financieros de la cuenta.
 
+Si no está recibiendo el correo electrónico que informa que el boleto bancario está disponible para descargar en la plataforma, es posible que el correo electrónico no esté registrado como contacto financiero. En este caso, abra un [ticket](https://support.vtex.com/hc/es-es/requests) para solicitar la inclusión del correo electrónico en los contactos financieros de la cuenta.
diff --git a/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
index eef69f568..78ec667e7 100644
--- a/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
@@ -25,7 +25,7 @@ La plataforma VTEX está lista para cambios de domínio sin impactos negativos.
 
 ### 1. Crear nuevas entradas HOST en el License Manager
 En el License Manager, en “Contas”, será necesario incluir el nuevo dominio cómo HOST de la tienda. Todavía el DNS del nuevo dominio no debe estar apuntado para VTEX. En secuencia la imágenes con ejemplo de cómo se hace la inclusión de nuevos HOSTs:
-![Cambiar dominio](https://images.ctfassets.net/alneenqid6w5/2mejT2jclm4MSwCoy8SwGo/c305404cae53e6c3bc7e4077f125c366/626-es.png)
+![Cambiar dominio](//images.ctfassets.net/alneenqid6w5/2mejT2jclm4MSwCoy8SwGo/c305404cae53e6c3bc7e4077f125c366/626-es.png)
 
 ### 2. Fijar las configuraciones del nuevo Portal
 Es paso es fundamental para que el Checkout funcione correctamente.
diff --git a/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
index 6cfa250f4..d2036eaf8 100644
--- a/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
@@ -45,7 +45,7 @@ Verifique el procedimiento:
 
 <div class="alert alert-info">Puede encontrar más información sobre <strong>Configuraciones generales</strong> y <strong>Configuraciones de búsqueda y filtro</strong> en la sesión <strong>Cómo configurar</strong> del artículo <a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Crear entidad de datos</a>.</div>
 
-![crear campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
+![crear campo master data ds](//images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
 De este modo, volverá a la página principal de la pestaña Entidad de Datos. Para finalizar, es necesario publicar el campo. Basta localizar la línea de la entidad en la que se agregó el campo y hacer clic en el ícono de disquete.
 
@@ -70,6 +70,6 @@ Dicho esto, prosiga con las instrucciones:
 7. Arrastre el campo de la lista Campos disponibles para las columnas Campos de la columna 1 o Campos de la columna 2.
 8. En la esquina inferior derecha de la pantalla, haga clic en el botón azul Guardar.
 
-![criar campo master data CRM](https://images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
+![criar campo master data CRM](//images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
 
 ¡Listo! Así, los campos se mostrarán en el formulario.
diff --git a/docs/tutorials/es/how-can-i-create-callcenter-user.md b/docs/tutorials/es/how-can-i-create-callcenter-user.md
index 07301148c..d22d469c4 100644
--- a/docs/tutorials/es/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/es/how-can-i-create-callcenter-user.md
@@ -41,7 +41,7 @@ Para crear un usuario con el rol de televentas, sigue los pasos a continuación:
 
 7. Haz clic en el botón **Guardar**.
 
-![GIF animado que muestra cómo crear un usuario de televentas](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/4d432b47fca70a6203a566bbe9d61abc/Adicionar_perfil_ES.gif)
+![GIF animado que muestra cómo crear un usuario de televentas](//images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/4d432b47fca70a6203a566bbe9d61abc/Adicionar_perfil_ES.gif)
 
 <div class="alert alert-warning">Al crear un <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evita incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televentas junto con otros recursos. De lo contrario, puede que el perfil no funcione de forma esperada.
 </div>
diff --git a/docs/tutorials/es/how-can-i-create-cluster-of-customers.md b/docs/tutorials/es/how-can-i-create-cluster-of-customers.md
index 789e59755..150a11dfa 100644
--- a/docs/tutorials/es/how-can-i-create-cluster-of-customers.md
+++ b/docs/tutorials/es/how-can-i-create-cluster-of-customers.md
@@ -3,8 +3,8 @@ title: 'Crear clúster de clientes'
 id: frequentlyAskedQuestions_1724
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:58.065Z
-updatedAt: 2022-10-17T21:24:38.123Z
-publishedAt: 2022-10-17T21:24:38.123Z
+updatedAt: 2024-05-24T19:15:04.156Z
+publishedAt: 2024-05-24T19:15:04.156Z
 firstPublishedAt: 2019-01-24T22:05:41.666Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -44,6 +44,6 @@ Técnicamente, un clúster en el CRM es nada más que un campo.
 
 Para rellenar este campo, usted puede usar una [planilla de importación](https://help.vtex.com/es/tutorial/importar-datos-en-el-master-data--tutorials_1135 "Importar datos en el Master Data") o una API, o puede hacerlo manualmente por el formulario Cliente en CRM. Todo depende de la estrategia de la tienda para agrupar a sus clientes.
 
-## Para saber más
+## Más información
 
 - [Crear promoción para un clúster](/es/tutorial/creando-promociones-cluster-clientes)
diff --git a/docs/tutorials/es/how-can-i-direct-a-financial-doubt-to-vtex.md b/docs/tutorials/es/how-can-i-direct-a-financial-doubt-to-vtex.md
index f900d8b5b..9bb280923 100644
--- a/docs/tutorials/es/how-can-i-direct-a-financial-doubt-to-vtex.md
+++ b/docs/tutorials/es/how-can-i-direct-a-financial-doubt-to-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Cómo direccionar duda financiera a VTEX?'
 id: 5h8wQ6AqIEKYcU2mASqGEU
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:46.689Z
-updatedAt: 2020-03-09T17:25:45.988Z
-publishedAt: 2020-03-09T17:25:45.988Z
+updatedAt: 2024-07-29T22:06:40.466Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T21:58:53.151Z
 contentType: tutorial
 productTeam: Billing
diff --git a/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md b/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md
index cc2013283..aef4fd4f9 100644
--- a/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md
+++ b/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md
@@ -3,8 +3,8 @@ title: 'Exportar la base de newsletter por Master Data'
 id: frequentlyAskedQuestions_1825
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:58.818Z
-updatedAt: 2023-03-28T23:50:45.779Z
-publishedAt: 2023-03-28T23:50:45.779Z
+updatedAt: 2024-05-24T18:56:12.924Z
+publishedAt: 2024-05-24T18:56:12.924Z
 firstPublishedAt: 2019-01-24T22:00:56.109Z
 contentType: tutorial
 productTeam: Master Data
@@ -19,10 +19,13 @@ Para exportar su base de clientes que han optado por recibir newsletter, siga el
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
 2. Haga clic en la pestaña **Clientes.**
-3. Haga clic en **Exportar XLS.**
+3. Haga clic en `Exportar XLS`.
 4. Seleccione el filtro `Recebe Newsletter?`, entre otros que quiera (`Nome` y `E-mail`, por ejemplo).
-5. Haga clic en **Exportar.**
-6. Será informado que la exportación se ha programado con éxito. Haga clic en **OK.**
-7. En la planilla que ha sido enviada a su e-mail habrá una columna titulada `isNewsletterOptIn`, que asigna el valor **true** para los clientes que reciben newsletter y **false** para aquellos que no la reciben.
+5. Haga clic en `Exportar`.
+6. Será informado que la exportación se ha programado con éxito. Haga clic en `OK`.
 
-_Esta opción sólo es válida para tiendas que tienen registro de newsletter por el Master Data. Si su tienda no tiene esa configuración y ella todavía se hace por un control de página, vea el artículo [Configurar la captación de newsletter por Master Data](/es/tutorial/como-configuro-la-captacion-de-newsletter-por-el-master-data--frequentlyAskedQuestions_1816) para saber como configurar._
+   En la planilla que ha sido enviada a su e-mail habrá una columna titulada `isNewsletterOptIn`, que asigna el valor **true** para los clientes que reciben newsletter y **false** para aquellos que no la reciben.
+
+<div class="alert alert-warning">
+  <p>Esta opción sólo es válida para tiendas que tienen registro de newsletter por el Master Data. Si su tienda no tiene esa configuración y ella todavía se hace por un control de página, vea el artículo <a href="https://help.vtex.com/es/tutorial/como-configuro-la-captacion-de-newsletter-por-el-master-data--frequentlyAskedQuestions_1816">Configurar la captación de newsletter por Master Data</a> para saber como configurar.</p>
+</div>
diff --git a/docs/tutorials/es/how-can-my-customer-login-to-my-store.md b/docs/tutorials/es/how-can-my-customer-login-to-my-store.md
index ea87611d4..78f7a7dfd 100644
--- a/docs/tutorials/es/how-can-my-customer-login-to-my-store.md
+++ b/docs/tutorials/es/how-can-my-customer-login-to-my-store.md
@@ -28,7 +28,7 @@ El objetivo de este artículo es mostrar cómo el cliente de su tienda debe hace
 
 Al hacer clic en un enlace para autenticarse, el cliente verá la pantalla de login.
 
-![vtex-id-pt](https://images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/f856e8dbe763a72e566f65a00c45be6c/vtex-id-en.png)
+![vtex-id-pt](//images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/f856e8dbe763a72e566f65a00c45be6c/vtex-id-en.png)
 
 Hay tres formas estándar de entrar en una tienda VTEX:
 
@@ -43,9 +43,9 @@ En este tipo de login se envía __un token de acceso para el e-mail del usuario
 Para que el cliente inicie sesión por este método, debe seguir los pasos abajo:
 
 1. En la pantalla de inicio de sesión, el usuario debe hacer clic en __Recibir clave de acceso rápido por email__.
-2. En la pantalla siguiente, el usuario debe rellenar su correo electrónico y hacer clic en el botón __Confirmar__![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-3. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si la ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-4. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Entrar__. ![fill-access-token-pt](https://images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
+2. En la pantalla siguiente, el usuario debe rellenar su correo electrónico y hacer clic en el botón __Confirmar__![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+3. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si la ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+4. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Entrar__. ![fill-access-token-pt](//images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
 
 ### Hacer login con email y contraseña
 
@@ -56,11 +56,11 @@ Este tipo de login __solicita email y contraseña__ para que el cliente pueda au
 - Si el cliente necesita __registrar una contraseña__, debe seguir los pasos abajo:
 
 1. En la pantalla de inicio de sesión, el usuario debe hacer clic en __Entrar con email y contraseña__.
-2. En la pantalla siguiente, debe hacer clic en __No tiene una contraseña? Registrela ahora__![register-password-pt](https://images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
-3. El usuario debe llenar su email y hacer clic en el botón __Confirmar__![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-4. En la pantalla siguiente, debe escribir su nueva contraseña en los campos __Nueva contraseña__ y __Confirmar nueva contraseña__ y, a continuación, hacer clic en el botón __Registrar nueva contraseña__![register-new-password-pt](https://images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
-5. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si lo ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-6. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Cambiar contraseña__ ![change-password-pt](https://images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)   
+2. En la pantalla siguiente, debe hacer clic en __No tiene una contraseña? Registrela ahora__![register-password-pt](//images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
+3. El usuario debe llenar su email y hacer clic en el botón __Confirmar__![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+4. En la pantalla siguiente, debe escribir su nueva contraseña en los campos __Nueva contraseña__ y __Confirmar nueva contraseña__ y, a continuación, hacer clic en el botón __Registrar nueva contraseña__![register-new-password-pt](//images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
+5. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si lo ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+6. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Cambiar contraseña__ ![change-password-pt](//images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)   
 
 ### Inicio de sesión con redes sociales
 
diff --git a/docs/tutorials/es/how-change-order-works-beta.md b/docs/tutorials/es/how-change-order-works-beta.md
new file mode 100644
index 000000000..9b198755f
--- /dev/null
+++ b/docs/tutorials/es/how-change-order-works-beta.md
@@ -0,0 +1,77 @@
+---
+title: 'Cómo funciona Modificar pedido (Beta)'
+id: 56TO0bOFXsfmpc7YZ3wIUZ
+status: PUBLISHED
+createdAt: 2023-11-27T14:51:09.723Z
+updatedAt: 2024-04-09T17:58:34.469Z
+publishedAt: 2024-04-09T17:58:34.469Z
+firstPublishedAt: 2023-11-27T22:39:50.675Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: como-funciona-modificar-pedido-beta
+locale: es
+legacySlug: como-funciona-modificar-pedido-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+<div class="alert alert-info">
+Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar <b>Modificar pedido (Beta)</b>, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a> e informa el nombre del <a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> en que deseas activarla.
+</div>
+
+La funcionalidad **Modificar pedido (beta)** brinda la posibilidad de editar un pedido de múltiples maneras, ya sea para atender las preferencias del cliente, abordar la falta de disponibilidad de productos u otras razones. Los principales tipos de modificaciones en el pedido son:
+
+- **Agregar:** una cantidad de ítems o nuevos productos.
+- **Remover:** una cantidad parcial o total de ítems.
+- **Modificar peso:** posibilidad de modificar el peso de los ítems, aumentándolo o disminuyéndolo según necesidad.
+- **Sustituir ítems:** permite reemplazar unos ítems por otros, incluyendo aquellos con precios basados en peso.
+- **Modificar precio:** modificar el valor total del pedido.
+
+En la siguiente guía puedes consultar las instrucciones sobre [Cómo modificar pedidos (Beta)](https://help.vtex.com/es/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw). Este artículo aborda otros aspectos sobre **Modificar pedido (beta)** y se organiza de la siguiente forma:
+
+- [Modificaciones a través del Admin VTEX y API](#modificaciones-a-traves-del-admin-vtex-y-api)
+- [Características generales](#caracteristicas-generales)
+- [Cambios de precio](#cambios-de-precio)
+
+## Modificaciones a través del Admin VTEX y API
+
+Hay dos formas de modificar un pedido, detalladas en la tabla a continuación:
+
+| **A través de** | **Descripción** | **Status que admite modificaciones** |
+|:---:|:--- |:--- |
+| Admin VTEX | <p>La modificación se realiza desde <a href="https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl">la página donde se muestran los detalles del pedido</a>, a la que se accede seleccionando el pedido deseado en <b>Pedidos > Todos los pedidos</b>.</p><p>También puedes acceder al pedido mediante la barra de búsqueda situada en la parte superior del Admin VTEX. Haz clic en la barra, selecciona la opción <b>Pedidos</b> y utiliza alguno de los siguientes criterios:</p><p><ul><li>ID del pedido</li><li>Nombre del cliente</li><li>Email del cliente</li><li>Documento del cliente</li></ul></p><p><b>Artículo en el Help Center:</b> <a href="https://help.vtex.com/es/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw">Cómo modificar pedidos (Beta)</a></p> | <ul><li><code>preparando envío</code></li></ul> |
+| API | <p>Se modifica por los endpoints:</p><p><ul><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change detail</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes">Get order change history</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry">Retry order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel">Cancel order change</a></li></ul></p> | <p><ul><li><code>ready-for-handling</code></li><li><code>handling</code></li><li><code>waiting-for-fulfillment</code></li><li><code>ready for invoicing</code></li></ul></p> |
+
+El historial de modificaciones en el pedido se registra en la [página de detalles](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), en la sección **Historial de ítems modificados**. Para consultar esta información a través de la API, utiliza el endpoint [Get order change history](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes).
+
+## Características generales
+
+La funcionalidad **Modificar pedidos (beta)** tiene características específicas, como se muestra en la tabla a continuación:
+
+| **Tema** | **Descripción** |
+|:---:|:--- |
+| Número de modificaciones en el pedido | No hay un límite específico respecto a la cantidad de veces que el pedido puede modificarse. |
+| Pedidos incompletos | No es posible modificar <a href="https://help.vtex.com/es/tutorial/entendendo-os-pedidos-incompletos--tutorials_294">pedidos incompletos</a>, es decir, aquellos que carecen de la información necesaria para su procesamiento en la plataforma VTEX. |
+| Cuentas franquicia | Es posible modificar pedidos en los que el seller sea una cuenta franquicia. |
+|  Marketplace VTEX, certificado, partner y externo | <p>La modificación de pedidos se comporta de forma diferente en los distintos escenarios de marketplaces en VTEX:</p><p><ul><li>Es posible modificar pedidos de tiendas que operan tanto como <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#como-seller-vtex">sellers VTEX</a> como <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex">marketplaces VTEX</a>.</li><li>Es posible modificar pedidos de <a href="https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a> cuando se realizan en <a href="https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces">marketplaces externos</a>.</li><li>No es posible modificar pedidos realizados en <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-certificado">marketplaces certificados</a> y <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-partner">marketplaces partners</a>.</li></ul></p> |
+| Reserva | La <a href="https://help.vtex.com/es/tutorial/how-does-reservation-work--tutorials_92">reserva</a> de ítems en escenarios de modificación de pedidos es automática. |
+| Actualización de stock | Al modificar un pedido, el <a href="https://help.vtex.com/es/tutorial/inventory-management--tutorials_139">stock de la tienda</a> no se actualiza automáticamente; esto debe hacerlo la tienda en el Admin VTEX en <b>Catálogo > Stock > Gestión del stock</b>, o a través de la API, utilizando el endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>. |
+| Permiso en Licence Manager | <p>Para que un usuario pueda modificar pedidos, su rol debe estar asociado con al menos uno de los siguientes <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos de Licence Manager</a>:</p><p><ul><li><code>Orders Full Access</code></li><li><code>Change order</code></li></ul></p> |
+
+## Cambios de precio
+
+Cuando la modificación de ítems en el pedido aumenta o disminuye el valor original de la compra, la comunicación del módulo **Pedidos** se envía automáticamente a **Pagos** y ocurre de la siguiente manera:
+
+- **Precio inferior tras las modificaciones:** se envía una notificación al [gateway](https://help.vtex.com/es/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#gateway) de pagos para revertir el valor que debe devolverse al cliente.
+- **Precio más alto tras las modificaciones:** se envía una notificación al gateway de pagos para pedir al cliente que pague el valor adicional.
+
+Consulta la tabla siguiente para obtener más información sobre el pago y la facturación al modificar pedidos:
+
+| **Tema** | **Información** |
+|:---:|:--- |
+| Condiciones para aumentar el precio del pedido | <p>Solo es posible aumentar el precio del pedido cuando cumple alguno de los siguientes criterios:</p><p><ul><li>El pedido se realizó utilizando una tarjeta de crédito, <a href="https://help.vtex.com/es/tutorial/setting-up-payments-notes--5pW7avTwtyQcMu4uiW8quQ">pagarés</a> o <a href="https://help.vtex.com/es/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0">customer credit</a>.</li><li>El <a href="https://help.vtex.com/es/tutorial/what-is-an-acquirer--7N1oRTG8dGmOiIugC0cs4E">adquirente</a> del pedido permite transacciones sin el código CVV.</li><li>El adquirente del pedido permite dos transacciones de cobro sobre el mismo pedido.</li></ul></p><p>Si el <a href="https://help.vtex.com/es/tutorial/o-que-e-conector--3lze0Cu0bmyC6u2o2iaeEA">conector</a> no permite cambios a valores mayores, se realizará una nueva transacción con el valor excedente, y la transacción no tendrá ningún vínculo con el pedido original.</p> |
+| Modificaciones en pedido liquidado | <p>En el <a href="https://help.vtex.com/es/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/1xjzgJZvqwaI1rfxLMCC3Y">flujo de la transacción</a>, el pedido puede cambiar de status <code>settled</code> (liquidado), siempre que cumpla las siguientes condiciones:</p><p><ul><li>El pedido se realizó con tarjeta de crédito.</li><li>La liquidación del pago tiene lugar antes de que el pedido sea <a href="https://help.vtex.com/es/tutorial/como-faturar-um-pedido--7p1h852V5t54KyscpgxE2v">facturado</a>.</li><li>El conector de pago está configurado para permitir reembolsos parciales. Actualmente, <a href="https://help.vtex.com/es/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv">Adyen</a> es el único conector de pago que admite esa operación.</li></ul></p><p>Los pedidos en que la transacción se encuentra con el status <code>finished</code> (finalizado) no pueden modificarse.</p> |
+| Transacción compartida entre sellers y marketplace | Es posible realizar modificaciones en pedidos que involucren a más de un seller y cuyos pagos tengan lugar en el entorno del marketplace, es decir, escenarios con <a href="https://help.vtex.com/es/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx">split de pagos</a>. |
+| Descuentos | No es posible modificar el pedido aplicando descuentos superiores o iguales al valor total del pedido original. |
+| Factura | <p>Con respecto a la <a href="https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT">factura</a>, la modificación de pedidos se comporta de la siguiente manera:</p><p><ul><li>Si el pedido ya ha sido <a href="https://help.vtex.com/es/tutorial/como-faturar-um-pedido--7p1h852V5t54KyscpgxE2v">facturado</a> por completo, no podrá modificarse.</li><li>Pueden modificarse pedidos aún no facturados o <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>.</li><li>El valor de las facturas parciales del pedido modificado debe ser igual o superior al valor de una factura ya emitida.</li><li>Si el valor total del pedido modificado es inferior al valor de una factura ya emitida, no podrá modificarse.</li></ul></p><p>En general, es la facturación del pedido lo que desencadena la liquidación del pago. Este comportamiento es diferente para las tiendas que han configurado la <a href="https://help.vtex.com/es/tutorial/configuring-maximum-automatic-payment-settlement-time-frame--7dwcaxrcgcFJUk7umqPBw2">liquidación automática</a>.</p> |
+
diff --git a/docs/tutorials/es/how-dns-configuration-works-on-vtex.md b/docs/tutorials/es/how-dns-configuration-works-on-vtex.md
new file mode 100644
index 000000000..81889386a
--- /dev/null
+++ b/docs/tutorials/es/how-dns-configuration-works-on-vtex.md
@@ -0,0 +1,36 @@
+---
+title: 'Cómo funciona la configuración de DNS en VTEX'
+id: 2P5k3oMYOj7TgSK4Mrxmgy
+status: PUBLISHED
+createdAt: 2024-01-23T16:53:52.076Z
+updatedAt: 2024-01-23T17:00:29.714Z
+publishedAt: 2024-01-23T17:00:29.714Z
+firstPublishedAt: 2024-01-23T16:58:57.454Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: como-funciona-la-configuracion-de-dns-en-vtex
+locale: es
+legacySlug: como-funciona-la-configuracion-de-dns-en-vtex
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+La configuración del DNS es un paso esencial para realizar el go live de tu tienda. En VTEX, la tienda requiere una configuración específica del sistema de DNS (Domain Name System) para funcionar correctamente. El DNS es el sistema que traduce los nombre de dominio (como `mitienda.com`) a direcciones IP de servidores que almacenan los archivos necesarios para mostrar una página web.
+
+Para configurar el DNS, debes crear un [CNAME](https://www.cloudflare.com/es-es/learning/dns/dns-records/dns-cname-record/) para el dominio principal de la tienda y dirigirlo a `{dominioPrincipal}.cdn.vtex.com`. Por ejemplo, para la tienda `www.mitienda.com` debes crear un CNAME que apunte a `www.mitienda.com.cdn.vtex.com`.
+
+Las redirecciones funcionan en etapas:
+
+1. El CNAME creado por tu equipo dirige el tráfico de la tienda a una ubicación específica en la infraestructura VTEX.
+
+   `www.mitienda.com` 🠖 `CNAME `🠖 `www.mitienda.com.cdn.vtex.com`
+2. Internamente, VTEX configura un segundo CNAME que dirige al servicio de Azion o CloudFront.
+
+   `www.mitienda.com.cdn.vtex.com` 🠖 `CNAME` 🠖 `uug412qft7.map.azionedge.net`
+3. Por último, una redirección de tipo A dirige la ruta de servicio Azion/CloudFront a una dirección IP específica.
+
+   `uug412qft7.map.azionedge.net` 🠖 `A` (tipo de registro que contiene una dirección IP) 🠖 `185.76.11.52`
+
+Esta configuración garantiza que la dirección IP resuelta sea dinámica y que pueda cambiar en cualquier momento. Esto se debe a que la dirección IP se adapta para coincidir con el servidor de CDN (Content Delivery Network) más cercano a la ubicación del visitante. La adaptación mejora el rendimiento del sitio web, ya que los archivos se entregan al visitante desde los servidores más cercanos geográficamente.
+
+Para más información sobre la configuración de DNS en VTEX, consulta[ Go live](https://help.vtex.com/es/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj).
diff --git a/docs/tutorials/es/how-do-i-terminate-my-contract-with-vtex.md b/docs/tutorials/es/how-do-i-terminate-my-contract-with-vtex.md
index 783182c93..7cd9b0a9e 100644
--- a/docs/tutorials/es/how-do-i-terminate-my-contract-with-vtex.md
+++ b/docs/tutorials/es/how-do-i-terminate-my-contract-with-vtex.md
@@ -3,19 +3,19 @@ title: '¿Cómo puedo rescindir mi contrato con VTEX?'
 id: HhPeg8EOismMSImoWwaI8
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:36.822Z
-updatedAt: 2019-12-31T15:22:44.073Z
-publishedAt: 2019-12-31T15:22:44.073Z
+updatedAt: 2024-01-18T16:03:47.790Z
+publishedAt: 2024-01-18T16:03:47.790Z
 firstPublishedAt: 2019-01-24T22:00:07.201Z
 contentType: tutorial
 productTeam: Financial
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: como-puedo-rescindir-mi-contrato-con-vtex
 locale: es
 legacySlug: como-puedo-rescindir-mi-contrato-con-vtex
 subcategory: 6SJnrkKDjGwSqKkMuQMOmm
 ---
 
-Para efectuar la cancelación de su contrato y dejar de utilizar la plataforma VTEX, es necesario abrir un [ticket](https://support.vtex.com/hc/es-419/requests) comunicando su decisión al Financiero.
+Para efectuar la cancelación de su contrato y dejar de utilizar la plataforma VTEX, es necesario abrir un [ticket](https://help.vtex.com/es/support) comunicando su decisión al Financiero.
 
 ## Asegúrese de que su llamada contenga la siguiente información:
 
@@ -25,4 +25,4 @@ Para efectuar la cancelación de su contrato y dejar de utilizar la plataforma V
 
 Hecho esto, el proceso se iniciará internamente y luego un distrato para la firma electrónica será enviado a través de __Clicksign__.
 
-En caso de que se confirme el deseo del cliente en relación a la rescisión, no se cobrará ninguna multa. El último cobro será referente al mes de la solicitud de rescisión. Su panel administrativo será __excluído en los primeros 5 días del mes siguiente__ a la solicitud.
+En caso de que se confirme el deseo del cliente en relación a __la rescisión, las clausulas de aviso prévio y multa serán verificadas y cobradas en la facturación del cliente.__ Su panel administrativo será __excluído en los primeros 5 días del mes siguiente__ a la solicitud.
diff --git a/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index 1b3023b50..d4ca3e0c4 100644
--- a/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -32,16 +32,16 @@ Es posible cambiar el protocolo en todas las carpetas de una sola vez con el uso
 2. Acceda a **Sites and channels**;
 3. Acceda el website deseado;
 4. Abra la carpeta raíz del website;
-![cms_instrução ES](https://images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
+![cms_instrução ES](//images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
 5. La pantalla que se abre muestra todas las carpetas que están en el primer nivel del sitio. Para cada carpeta pertinente, haga clic en **Edit** - para la home, considera el botón superior;
-![cms_edit ES](https://images.ctfassets.net/alneenqid6w5/5w8bfK8O3egookYkO80uum/af60a80fbf62a154124b05496c1773cf/edit_CMS_ES.png)
+![cms_edit ES](//images.ctfassets.net/alneenqid6w5/5w8bfK8O3egookYkO80uum/af60a80fbf62a154124b05496c1773cf/edit_CMS_ES.png)
 6. En el cuadro de selección **Protocol**, seleccione la opción **HTTPS**;
-![cms-protocol-https ES](https://images.ctfassets.net/alneenqid6w5/6iKmkVgCKkeEu6uqygUs4s/778574a06a8ec5bb2d8fdfe871af0763/cms_protocol_HTTPS_ES.png)
+![cms-protocol-https ES](//images.ctfassets.net/alneenqid6w5/6iKmkVgCKkeEu6uqygUs4s/778574a06a8ec5bb2d8fdfe871af0763/cms_protocol_HTTPS_ES.png)
 7. Haga clic en **Save Folder**.
 
 Atención a las carpetas que tienen subcarpetas, como Departamento, Categoria, Produto y otras carpetas, incluyendo también las creadas para la personalización de la tienda. 
 
 En el siguiente ejemplo, la carpeta **@Orders@**, contenida en **Account**, que también debe ser editada: 
-![cms_subcategoria_edit ES](https://images.ctfassets.net/alneenqid6w5/DugouRmlRQKqAI66eCYww/5bdea3c5bf8305e1693433b1adc14747/subcategoria_edit_ES.png)
+![cms_subcategoria_edit ES](//images.ctfassets.net/alneenqid6w5/DugouRmlRQKqAI66eCYww/5bdea3c5bf8305e1693433b1adc14747/subcategoria_edit_ES.png)
 
 Después del cache de hasta 10 minutos los cambios estarán en vigor.
diff --git a/docs/tutorials/es/how-do-reversals-work-when-an-item-is-returned.md b/docs/tutorials/es/how-do-reversals-work-when-an-item-is-returned.md
index 51093fd8a..5d3961c48 100644
--- a/docs/tutorials/es/how-do-reversals-work-when-an-item-is-returned.md
+++ b/docs/tutorials/es/how-do-reversals-work-when-an-item-is-returned.md
@@ -3,8 +3,8 @@ title: 'Funcionamiento del extorno cuando se devuelve un ítem'
 id: frequentlyAskedQuestions_298
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.904Z
-updatedAt: 2021-08-12T18:29:59.905Z
-publishedAt: 2021-08-12T18:29:59.905Z
+updatedAt: 2024-02-28T17:25:13.906Z
+publishedAt: 2024-02-28T17:25:13.906Z
 firstPublishedAt: 2019-01-24T21:55:16.859Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/how-does-promotion-proration-work.md b/docs/tutorials/es/how-does-promotion-proration-work.md
index 7793e0766..0d28d9aed 100644
--- a/docs/tutorials/es/how-does-promotion-proration-work.md
+++ b/docs/tutorials/es/how-does-promotion-proration-work.md
@@ -38,7 +38,7 @@ Digamos que tenemos una promoción de descuento nominal de $ 156,00 para ser apl
 
 Considerando la lógica del cálculo anterior, quedaría como sigue:
 
-![tabelaex.es](https://images.ctfassets.net/alneenqid6w5/5G6XOjSgYmXK29ODCJf58A/077a633df92bc68da6b5032e493a6157/tabelaex.es.png)
+![tabelaex.es](//images.ctfassets.net/alneenqid6w5/5G6XOjSgYmXK29ODCJf58A/077a633df92bc68da6b5032e493a6157/tabelaex.es.png)
 
 Este cálculo se aplica a productos unitarios, como una blusa o una mesa, pero también hay productos que tienen en su registro una configuración llamada unidad multiplicadora, como una caja de piso de 2,5 m², por ejemplo.
 
diff --git a/docs/tutorials/es/how-does-reservation-work.md b/docs/tutorials/es/how-does-reservation-work.md
index 39d14aa29..377fa0721 100644
--- a/docs/tutorials/es/how-does-reservation-work.md
+++ b/docs/tutorials/es/how-does-reservation-work.md
@@ -3,8 +3,8 @@ title: 'Cómo se maneja la reserva'
 id: tutorials_92
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:56.753Z
-updatedAt: 2023-04-28T22:58:58.294Z
-publishedAt: 2023-04-28T22:58:58.294Z
+updatedAt: 2023-10-18T17:20:21.911Z
+publishedAt: 2023-10-18T17:20:21.911Z
 firstPublishedAt: 2017-04-27T23:00:42.751Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index d16093e9b..1045fd2e9 100644
--- a/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -29,7 +29,7 @@ En lugar de usar los IDs de cada artículo (lo que generaría pedidos separados
 
 Usted puede encontrar los dos IDs a través del informe enviado desde el panel de integraciones en el Admin de VTEX.
 
-![mercalo-livre-pedido-id-es](https://images.ctfassets.net/alneenqid6w5/5JOUHJijbIVncRSfvx5lnC/6cceef1724619d4cd8d332d0e5aad89b/mercalo-livre-pedido-id-es.png)
+![mercalo-livre-pedido-id-es](//images.ctfassets.net/alneenqid6w5/5JOUHJijbIVncRSfvx5lnC/6cceef1724619d4cd8d332d0e5aad89b/mercalo-livre-pedido-id-es.png)
 
 <div class="alert alert-warning">
 Esta lógica de funcionamiento se aplica a todos los tipos de entrega, con excepción de aquellos que incluyen pickup points. En estos casos, la plataforma sigue utilizando el identificador antiguo.
diff --git a/docs/tutorials/es/how-does-the-delivery-flow-work.md b/docs/tutorials/es/how-does-the-delivery-flow-work.md
index 84e0e9276..4570857c6 100644
--- a/docs/tutorials/es/how-does-the-delivery-flow-work.md
+++ b/docs/tutorials/es/how-does-the-delivery-flow-work.md
@@ -27,4 +27,4 @@ La plataforma VTEX le da libertad para que su tienda utilice estas configuracion
 
 Pero, por ahora, vamos a atenerse al escenario más básico, ilustrado por la figura abajo:
 
-![Logistics Flow Espanhol](https://images.ctfassets.net/alneenqid6w5/586A760DbOKiaeSiuO0wW0/09da81662ed4e1865d8f8c7cab9da054/Component__21_.png)
+![Logistics Flow Espanhol](//images.ctfassets.net/alneenqid6w5/586A760DbOKiaeSiuO0wW0/09da81662ed4e1865d8f8c7cab9da054/Component__21_.png)
diff --git a/docs/tutorials/es/how-does-the-score-field-work.md b/docs/tutorials/es/how-does-the-score-field-work.md
index 998abe694..a28825cd8 100644
--- a/docs/tutorials/es/how-does-the-score-field-work.md
+++ b/docs/tutorials/es/how-does-the-score-field-work.md
@@ -1,38 +1,55 @@
 ---
-title: '¿Cómo funciona el campo Score?'
+title: '¿Cómo funciona el campo Puntuación?'
 id: 1BUZC0mBYEEIUgeQYAKcae
 status: PUBLISHED
 createdAt: 2018-02-16T16:17:51.610Z
-updatedAt: 2023-03-27T13:32:27.264Z
-publishedAt: 2023-03-27T13:32:27.264Z
+updatedAt: 2024-01-05T20:42:03.525Z
+publishedAt: 2024-01-05T20:42:03.525Z
 firstPublishedAt: 2018-02-16T18:09:11.291Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
-author: 7FpKZ0rc6k4WqeymES80cw
-slug: como-funciona-el-campo-score
+author: 1malnhMX0vPThsaJaZMYm2
+slug: como-funciona-el-campo-puntuacion
 locale: es
 legacySlug: como-funciona-el-campo-score
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-El campo __Score__, disponible en los registros de Producto, Categoría y Marca, es el valor que se utiliza para asegurar la ordenación de los productos en tu tienda y también como criterio de desempate para otras ordenaciones, como el precio más bajo, el mejor descuento, etc. Rellenando este campo, puedes definir la prioridad de unos productos respecto a otros, tanto en la vitrina como en la página de resultados de la búsqueda.
+El campo **Puntuación**, disponible en los formularios de registro de **Producto**, **Categoría** y **Marca**, es un valor utilizado para ordenar productos en la tienda, que sirve como criterio de desempate al aplicar otros órdenes comunes, tales como menor precio, mejor descuento, entre otros. Al rellenar el campo **Puntuación**, puedes definir la prioridad de unos productos sobre otros, tanto en la vitrina como en la página de resultados de búsqueda.
 
-El criterio de enumeración del campo sigue una ordenación sencilla (1, 2, 3, 4...) y solo hay que seguirlo para mostrar la secuencia en la vitrina de la tienda o en la página de resultados de la búsqueda. 
+El criterio para enumerar el campo sigue una ordenación numérica para mostrar la secuencia en la vitrina de la tienda o en la página de resultados de la búsqueda. De manera predeterminada, los productos sin puntuación registrada se comportan como si tuvieran una puntuación de 0.
 
-Sin embargo, cuando se trata del Score del producto, es importante saber que consiste en la suma de su propio score con los de la categoría y la marca. Es decir: `Score del producto + Score de la categoría + Score de la marca`.
+La puntuación total de un producto se obtiene al sumar su propia puntuación, más las puntuaciones definidas para la categoría y la marca: `puntuación total del producto = puntuación del producto + puntuación de la categoría + puntuación de la marca`.
 
-Puedes utilizar los siguientes parámetros para implementar la ordenación:
+Recomendamos definir la puntuación a nivel de producto, ya que lo más habitual es que la vitrina cambie constantemente.
 
-- __Orden ascendente:__ `?O=OrderByScoreASC`
-- __Orden descendente:__ `?O=OrderByScoreDESC`
+La importancia de utilizar la puntuación se evidencia claramente en eventos específicos, cuando es necesario destacar ciertos productos sobre otros para asegurar su visibilidad en la tienda.
 
-Lo más apropiado es que ingreses el score del producto uno a uno, ya que probablemente tu vitrina cambie con frecuencia.
+## Puntuación en el buscador de VTEX
 
-Un buen ejemplo para el uso del Score es en eventos puntuales, cuando tu tienda necesita colocar determinados productos delante de otros para garantizar su visualización.
+Si la tienda utiliza el [buscador de VTEX](https://help.vtex.com/es/tutorial/como-funciona-a-busca-da-vtex--tutorials_542), pueden utilizarse los siguientes parámetros para implementar la ordenación por puntuación:
 
-Para añadir o cambiar un score relacionado con un producto, sigue los pasos a continuación:
+* **Orden ascendente** (productos con puntuación más baja aparecen en primer lugar): `?O=OrderByScoreASC`
+* **Orden descendente** (productos con puntuación más alta aparecen en primer lugar): `?O=OrderByScoreDESC`
 
-1. En el Admin VTEX, accede a **Catalog > Productos y Skus**.
-2. Haz clic en `Agregar producto` para crear un nuevo producto o en `Cambiar` en el producto que deseas editar.
-3. Introduce el valor del score deseado en el campo **Score (utilizado para la ordenación de la búsqueda)**.
+## Puntuación en VTEX Intelligent Search
 
+Los parámetros `OrderByScoreASC` y `OrderByScoreDESC` no son compatibles con [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb), sino únicamente con el [buscador VTEX](https://help.vtex.com/es/tutorial/como-funciona-a-busca-da-vtex--tutorials_542).
+
+La ordenación directa de productos por la puntuación definida en el campo **Puntuación** no es posible en [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb). Al utilizar uno de los parámetros antes referidos en VTEX Intelligent Search, se genera una ordenación predeterminada, que es por [relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+Por otro lado, la puntuación del Catálogo consigue componer la [relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) en Intelligent Search frente a otros criterios, brindando la posibilidad de asignarle mayor peso e incluso prioridad. A efectos de componer la relevancia, a mayor puntuación, mayor peso; es decir, el comportamiento es decreciente: se priorizan los productos con una puntuación más alta.
+
+Sin tener en cuenta la influencia de otros criterios, o incluso considerando el uso de la ordenación prioritaria, en VTEX Intelligent Search los productos sin ninguna puntuación registrada aparecen después de los productos con puntuación registrada en los resultados de la búsqueda.
+
+Es necesario ponderar si esta práctica sería adecuada para tu caso de uso en relación con otros criterios calculados automáticamente por el sistema, como popularidad y ventas. Al priorizar un criterio, este prevalece sobre todos los demás, incluso alcanzando el mismo objetivo que `OrderByScore`, desestimando los demás ajustes de relevancia.
+
+Para ordenar manualmente los ítems de forma aislada, se recomienda utilizar [Reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), evitando efectos no deseados y respetando la configuración de relevancia.
+
+## Editar la puntuación de un producto
+
+Para agregar o modificar la puntuación de un producto, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Catálogo > Productos y SKUs**.
+2. Haz clic en Agregar producto para crear un nuevo producto o bien en Editar producto, en las opciones del producto que deseas editar.
+3. Introduce el valor deseado en el campo **Puntuación (utilizado para ordenar la búsqueda)**.
diff --git a/docs/tutorials/es/how-does-the-type-of-delivery-work.md b/docs/tutorials/es/how-does-the-type-of-delivery-work.md
index 23c2e5429..b4860e00c 100644
--- a/docs/tutorials/es/how-does-the-type-of-delivery-work.md
+++ b/docs/tutorials/es/how-does-the-type-of-delivery-work.md
@@ -3,8 +3,8 @@ title: 'Cómo se maneja el tipo de entrega'
 id: tutorials_126
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:17.250Z
-updatedAt: 2023-05-31T14:45:20.914Z
-publishedAt: 2023-05-31T14:45:20.914Z
+updatedAt: 2023-11-13T15:00:10.346Z
+publishedAt: 2023-11-13T15:00:10.346Z
 firstPublishedAt: 2017-04-27T23:00:44.173Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -29,7 +29,7 @@ En el checkout, no se exhiben los nombres de los transportistas, y sí los tipos
 
 Siguiendo en el ejemplo más arriba, sigue la imagen de cómo se exhibirían las opciones de flete en el cierre de compra:
 
-![Transportadoras Checkout ES](https://images.ctfassets.net/alneenqid6w5/3JEcAUPVTOsSsUCqiMSCUM/6085c74c27b51a0ffcfc5552d1a80eff/Transportadoras_Checkout_ES.png)
+![Transportadoras Checkout ES](//images.ctfassets.net/alneenqid6w5/3JEcAUPVTOsSsUCqiMSCUM/6085c74c27b51a0ffcfc5552d1a80eff/Transportadoras_Checkout_ES.png)
 
 O sea, aunque se tenga cinco transportistas catastrados (en las categorías **Normal**, **Expresa** y **Programada**), sólo se exhiben tres opciones de flete para el cliente. Y el motivo no es porque los demás transportistas no atienden al carrito, es porque dentro de un mismo tipo sólo se exhibirá el transportista de mayor ventaja al cliente.
 
diff --git a/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md b/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md
index 10764309b..27a40a658 100644
--- a/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md
+++ b/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md
@@ -21,6 +21,6 @@ La cuenta del descuento es: `average fee dividido por el número de días del me
 
 Entonces, si su mensualidad tuvo un valor de $ 750 en el mes de mayo - 31 días - y usted contrató a VTEX el día 06 de mayo, serán descontados $ 145,16 en su próxima factura.
 
-![prorata PT](https://images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
+![prorata PT](//images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
 
 La cuenta fue: `$ 750/31 = $ 24,19 x 3 (días) = $ 145,16`
diff --git a/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md b/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md
index 5ab0ca9c9..c410b1a19 100644
--- a/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md
+++ b/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md
@@ -3,8 +3,8 @@ title: '¿Cómo se calcula el plazo de entrega del pedido?'
 id: 1TOuKCIjGQmqOqQkEqCg82
 status: PUBLISHED
 createdAt: 2018-01-12T12:56:52.805Z
-updatedAt: 2023-03-29T14:09:06.429Z
-publishedAt: 2023-03-29T14:09:06.429Z
+updatedAt: 2023-09-23T00:34:19.034Z
+publishedAt: 2023-09-23T00:34:19.034Z
 firstPublishedAt: 2018-01-12T14:42:26.502Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,28 +15,22 @@ legacySlug: como-se-calcula-el-plazo-de-entrega-del-pedido
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-El plazo de entrega de una solicitud tiene en cuenta los __temos de costo__ definidos para las cinco etapas de la ruta de logística:
+El plazo de envío de un pedido es calculado considerando los seguientes aspectos:
 
-- Almacén.
-- Doca.
-- Transportadora.
-- Feriados.
-- Horários de corte.
+- [Lead time](https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B)
+- [Almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+- [Muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
+- [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140)
 
-Es decir, para cada uno de estos pasos usted puede establecer un tiempo de costo - y el plazo de entrega que su cliente verá en el checkout es la suma de estos tiempos de coste.
+![lead_time_image_total_time_ES](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
 
-![deliveryCostTimes](//images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
+Usted define una duración para cada una de esas etapas y su cliente en checkout vé um plazo de envío que es la suma de estos tiempos.  
 
-Los tiempos de coste del __almacén__ y de la __doca__ se definen en las pantallas de configuración de cada uno de estos pasos en el módulo **Envío > Estratégia de Envío.**
+El tiempo de envío de la transportadora está definido por la [plantilha de flete](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127), que tiene que estar asociada a su estrategia de envío por medio de una [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![entrega1.es](https://images.ctfassets.net/alneenqid6w5/11Sxc5vISEU8Knt0cf9uyJ/25e7778597e647d3bd5cd8c41fd6ccb9/entrega1.es.png) 
+Para configurar una política de envío, almacén o muelle, acceda a su Admin VTEX an **Envío > Estratégia de Envío**. Para configurar el lead time, acceda a **Catálogo > Gerenciamento de stock**.
 
-![entrega2.es](https://images.ctfassets.net/alneenqid6w5/187jUxkOBm3zEyU5zr1Uzy/c117ef2faf8d9f1aefd890cc4654739d/entrega2.es.png)
+### Sepa más
 
-El tiempo de coste de la __transportadora__ se define en la tabla de flete, enviada a VTEX a través de la pantalla de configuración del transportista, en **Envío > Estratégia de Envío > Política de Envío.**
-
-![entrega3.es](https://images.ctfassets.net/alneenqid6w5/3gd2irrk8fStTd7XSEf5eC/5d693f6e0a0e2538157f16ee97cb1665/entrega3.es.png)
-
-### Para obtener más información
-
-Por medio de la simulación de flete, puede comprobar cómo se ha calculado el plazo de entrega de una solicitud específica. Entiende como en el artículo [Verificar como el plazo de entrega de una solicitud fue calculado](/es/tutorial/comprobar-como-se-calculo-el-plazo-de-entrega-de-un-pedido).
+- [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144)
+- [Verificar como el plazo de entrega de una solicitud fue calculado](https://help.vtex.com/es/tutorial/comprobar-como-se-calculo-el-plazo-de-entrega-de-un-pedido).
diff --git a/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md b/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md
index 326428733..7142df077 100644
--- a/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md
+++ b/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md
@@ -3,8 +3,8 @@ title: '¿Cómo se comprueba el SLA de operación de la plataforma?'
 id: frequentlyAskedQuestions_662
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:57.436Z
-updatedAt: 2019-12-31T17:00:45.718Z
-publishedAt: 2019-12-31T17:00:45.718Z
+updatedAt: 2024-03-11T22:38:31.694Z
+publishedAt: 2024-03-11T22:38:31.694Z
 firstPublishedAt: 2019-01-24T22:11:03.028Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,26 +15,25 @@ legacySlug: como-se-comprueba-el-sla-de-operacion-de-la-plataforma
 subcategory: 5PYkoNDZyo2G80yiiqG2YW
 ---
 
-Además de los plazos, hay que identificar qué asumimos como violación del SLA. O sea, qué realmente contará como tiempo de indisponibilidad.
+Cualquier minuto de interrupción es muy costoso, tanto para las tiendas como para la misma VTEX. Así, tratamos de ser lo más transparentes posible con relación a la salud de nuestra plataforma. Ponemos a disposición la [página de status](https://status.vtex.com) en la que registramos todos los incidentes que impactaron nuestro SLA. Esos eventos se contabilizan como sigue.
 
-Como nuestro modelo comercial se basa en el rendimiento de la tienda, queda muy claro para todo el equipo VTEX que cualquier minuto de interrupción es muy costoso, tanto para las tiendas como para la misma VTEX. Así, tratamos de ser lo más transparentes posible con relación a la salud de nuestra plataforma. Ponemos a disposición la [página de status](http://status.vtex.com "página de status") en la que registramos todos los incidentes que impactaron nuestro SLA. Esos eventos se contabilizan como sigue.
+Para determinar las violaciones del SLA, es decir, para contabilizar el tiempo de indisponibilidad de la plataforma, consideramos los siguientes acontecimientos:
 
-### Se contabilizan
+- Interrupciones en la tienda virtual que estén impactando significativamente el número de pedidos realizados, por ejemplo: interrupción de la tienda, acceso lento, error en el checkout.
+- Interrupciones que duren al menos 10 minutos.
 
-- Cualquier interrupción en la tienda virtual que esté impactando significativamente el número de pedidos realizados. Ej.: tienda fuera del aire, lentitud en el acceso, error en el checkout.
-- Contabilizamos interrupciones con duración de, como mínimo, 10 minutos.
+<div class="alert alert-warning">
+  <p>No contabilizamos el mantenimiento programado como tiempo de indisponibilidad.</p>
+</div>
 
-### No se contabilizan
+## Verificar el status de VTEX
 
-- Manutenimientos programados.
-- Interrupción de algún servicio en el módulo administrativo.
+Para facilitar la identificación de escenarios de instabilidad, recomendamos consultar la página [Status VTEX](http://status.vtex.com) si sospecha que la herramienta no está disponible. El status se actualiza cuando la incidencia ha superado un mínimo de 10 minutos, con la siguiente información:
 
-### Verificando en el status
+- __Investigando/Identificado__: el equipo está investigando el incidente y llevando a cabo las acciones necesarias para restablecer el servicio.
+- __Monitoreando__: el incidente se ha resuelto y el servicio se ha estabilizado. Se está supervisando el ambiente.
+- __Resuelto__: caso cerrado, con registro del tiempo total de interrupción del SLA. En la mayoría de los casos, el tiempo total de interrupción es la suma del tiempo de inactividad del incidente.
 
-Para facilitar la identificación de esos escenarios, siempre recomendamos que se verifique el status en cualquier sospecha de indisponibilidad de la herramienta. El status es actualizado cuando el incidente excede del prazo mínimo de 10 minutos, con la siguiente información:
+## Más información
 
-- __Investigando/Identificado__: Incidente siendo investigado por el equipo. El equipo está tomando la acción necesaria para el restablecimiento del servicio.
-- __Monitoreando__: Incidente resuelto, servicio estabilizado. Ambiente bajo monitoreo.
-- __Resuelto__: Caso cerrado. Registrado tiempo total de interrupción. En la mayoría de los casos, el SLA es la suma del tiempo de indisponibilidad de cada incidente.
-
-![](//images.contentful.com/alneenqid6w5/2Le8koNu7YUoICaquSSuuY/134a3f2ca7cee4614a09c96397573dd9/Screen_Shot_2016-04-22_at_16.28.39.png)
+- [Página VTEX Status](https://help.vtex.com/es/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ)
diff --git a/docs/tutorials/es/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md b/docs/tutorials/es/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
index ea1a5b5d5..5ba25d3ce 100644
--- a/docs/tutorials/es/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
+++ b/docs/tutorials/es/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
@@ -3,8 +3,8 @@ title: '¿En cuánto tiempo un pedido de boleto sin pago se cancela?'
 id: frequentlyAskedQuestions_300
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.983Z
-updatedAt: 2021-10-28T11:55:41.026Z
-publishedAt: 2021-10-28T11:55:41.026Z
+updatedAt: 2024-06-11T21:26:30.893Z
+publishedAt: 2024-06-11T21:26:30.893Z
 firstPublishedAt: 2019-01-24T22:03:31.971Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/how-my-account-works.md b/docs/tutorials/es/how-my-account-works.md
index 0b9be4060..0ac03b6a1 100644
--- a/docs/tutorials/es/how-my-account-works.md
+++ b/docs/tutorials/es/how-my-account-works.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona Mi Cuenta'
 id: 2BQ3GiqhqGJTXsWVuio3Xh
 status: PUBLISHED
 createdAt: 2019-04-11T21:14:26.117Z
-updatedAt: 2023-04-24T23:39:56.581Z
-publishedAt: 2023-04-24T23:39:56.581Z
+updatedAt: 2023-12-21T14:09:42.863Z
+publishedAt: 2023-12-21T14:09:42.863Z
 firstPublishedAt: 2019-05-21T19:48:15.019Z
 contentType: tutorial
 productTeam: Identity
@@ -34,7 +34,7 @@ Para saper sobre cómo personalizar la funcionalidad <b>Mi cuenta</b>, consulte
 
 En esta pestaña, el cliente puede gestionar sus datos personales registrados en la tienda. Es posible [editar la información del perfil](#editar), [definir una nueva contraseña](#contrasena) y [elegir si desea recibir emails con promociones](#boletin-informativo).
 
-![profile ES](https://images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/98d696bdb6ca27fdcb6125d6ad83d60c/profile_ES.png)
+![profile ES](//images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/98d696bdb6ca27fdcb6125d6ad83d60c/profile_ES.png)
 
 ### Editar
 
@@ -77,9 +77,13 @@ El botón `Añadir dirección` permite incluir direcciones diferentes a las que
 
 ## Pedidos
 
+<div class = "alert alert-info">
+En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
+</div>
+
 Esta pestaña proporciona una lista completa de los pedidos realizados por un cliente en su tienda. La lista se ordena por fecha de creación y muestra detalles como la fecha del pedido, el valor total de la compra, el ID del pedido, el _status_ y los ítems comprados.
 
-![orders ES](https://images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/c6d01d4becb2a0f1173e34a82f83cb90/orders_ES.png)
+![orders ES](//images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/c6d01d4becb2a0f1173e34a82f83cb90/orders_ES.png)
 
 La pestaña **Pedidos** permite que el cliente haga el seguimiento del progreso del pedido y realice solicitudes como la cancelación y la modificación. Consulte a continuación todas las opciones disponibles.
 
@@ -104,7 +108,7 @@ Al hacer clic en un pedido del listado, el cliente podrá visualizar todos los d
 
 El cliente también puede [Hacer pedido de nuevo](#hacer-pedido-de-nuevo) desde esta página. Al hacer clic en `Más opciones`, se muestran las funcionalidades de [Modificar pedido](#modificar-pedido) (en caso de que esté habilitada y el _status_ del pedido sea `Preparando el pedido`) y [Solicitar cancelación](#solicitar-cancelacion).
 
-![order details ES](https://images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/d29f723e144d008ee0fc142db264a4a0/order_details_ES.png)
+![order details ES](//images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/d29f723e144d008ee0fc142db264a4a0/order_details_ES.png)
 
 #### Modificar pedido
 
@@ -116,7 +120,12 @@ Este botón permite que el cliente modifique la información del pedido, como di
 
 ## Tarjetas de crédito
 
-En la pestaña **Tarjetas de crédito**, el cliente tiene autonomía para gestionar las tarjetas de crédito relacionadas con su cuenta.  Es posible incluir y editar los datos de las tarjetas de crédito que ya se registraron en el _checkout_. Para agregar nuevas tarjetas, sigue los pasos a continuación:
+En la pestaña **Tarjetas de crédito**, el cliente tiene autonomía para administrar las tarjetas de crédito relacionadas con su cuenta a través de las siguientes acciones:
+
+- Agregar nuevas tarjetas
+- Eliminar tarjetas con fecha de vencimiento alcanzada
+
+Para agregar nuevas tarjetas, sigue los pasos a continuación:
 
 1. Abre **Mi cuenta** (My Account) en la tienda.
 2. Haz clic en la sección **Tarjetas de crédito**.
@@ -126,7 +135,7 @@ En la pestaña **Tarjetas de crédito**, el cliente tiene autonomía para gestio
 6. Resuelve el desafío de reCaptcha.
 7. Automáticamente se producirá un proceso de validación de tarjeta. Si no hay ningún problema, serás redirigido a la lista de tarjetas y la nueva tarjeta aparecerá en la lista.
 
-![Card ReCaptcha](https://images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/eb678f63dc5c69a402bae6db631c5ba8/Card_ReCaptcha_EN.gif)
+![Card ReCaptcha](//images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/eb678f63dc5c69a402bae6db631c5ba8/Card_ReCaptcha_EN.gif)
 
 Sin embargo, hay **limitaciones** que las tiendas que utilizan la autenticación [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) (V1 o V2) en sus adquirentes deben considerar:
 
@@ -148,7 +157,7 @@ En esta pestaña, el cliente puede gestionar todas sus suscripciones registradas
 
 Esta pestaña se puede acceder a ella en el panel izquierdo a través de **Autenticación** en la configuración del perfil del usuario. En la pestaña encontrará opciones para la gestión de contraseña y gestión de sesiones.
 
-![My Authentication app ES](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
+![My Authentication app ES](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
 
 ### Gestión de contraseña 
 
@@ -158,7 +167,7 @@ El componente **Contraseña** permite al usuario crear una contraseña (si aún
 2. En el campo **Código**, introduzca el código de verificación que recibió por email.
 3. En el campo **Nueva contraseña**, introduzca la nueva contraseña que desea asignar a su cuenta. Debajo del campo aparecen los requisitos que debe cumplir la contraseña para ser válida. A medida que escriba la contraseña, los símbolos de cada requisito cambiarán de rojo a verde. La contraseña solo será válida si todos los símbolos aparecen en verde.
 4. Una vez que haya introducido una contraseña válida, haga clic en el botón `GUARDAR CONTRASEÑA` para completar la creación de la contraseña.  
-![My Authentication create password ES](https://images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/c8f8a07de5442b0ffbc49c3b6a66de29/My_Authentication_create_password_ES.png)
+![My Authentication create password ES](//images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/c8f8a07de5442b0ffbc49c3b6a66de29/My_Authentication_create_password_ES.png)
 
 Para cambiar la contraseña actual:
 
@@ -166,7 +175,7 @@ Para cambiar la contraseña actual:
 2. Introduzca la contraseña actual en el campo correspondiente.
 3. Introduzca la nueva contraseña en el campo correspondiente, cumpliendo todos los requisitos.
 4. Haga clic en el botón `GUARDAR CONTRASEÑA` para completar el cambio de contraseña.  
-![My Authentication change password ES](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/55e5cdfbb4f5daeb591eadbbccf82183/My_Authentication_change_password_ES.png)
+![My Authentication change password ES](//images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/55e5cdfbb4f5daeb591eadbbccf82183/My_Authentication_change_password_ES.png)
 
 <div class="alert alert-info">
 Si ha olvidado su contraseña, no podrá recuperarla a través del componente de gestión de contraseña. Para ello, debe cerrar la sesión actual, hacer un intento de inicio de sesión con el email y la contraseña, y hacer clic en el link <strong>Olvidé mi contraseña</strong>.
@@ -180,7 +189,7 @@ Para ver sus sesiones activas, haga clic en el botón `VER SESIONES` y accederá
 
 Para cancelar el acceso a las demás sesiones, haga clic en el botón `CIERRE DE SESIÓN` de la sesión deseada.
 
-![My Authentication Session Management ES](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
+![My Authentication Session Management ES](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
 
 ## Configuraciones básicas
 
@@ -191,7 +200,7 @@ En **My Orders**, puedes determinar qué secciones estarán visibles para el cli
 * En **ORDERS**, la opción <a class="far fa-check-square"></a> _Visible_ determina si el cliente tiene la sección [Pedidos](#pedidos) para seguir sus pedidos.
 * En **ADDRESSES**, la opción <a class="far fa-check-square"></a> _Visible_ define si el cliente tendrá la sección [Direcciones](#direcciones) con detalles de su dirección. 
 
-![vtex-my-account_ES](https://images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/95b29a5b64c84fe70b4dc01e4a36b26a/vtex-my-account_ES.png)
+![vtex-my-account_ES](//images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/95b29a5b64c84fe70b4dc01e4a36b26a/vtex-my-account_ES.png)
 
 Por defecto, las opciones **CARDS** y **ORDERS** vienen configuradas como visibles. Para cambiarlas o habilitar otras configuraciones, realiza los pasos a continuación:
 
diff --git a/docs/tutorials/es/how-order-authorization-works.md b/docs/tutorials/es/how-order-authorization-works.md
index b1824e250..a07c223b8 100644
--- a/docs/tutorials/es/how-order-authorization-works.md
+++ b/docs/tutorials/es/how-order-authorization-works.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona la Autorización de pedidos'
 id: 3MBK6CmKHAuUjMBieDU0pn
 status: PUBLISHED
 createdAt: 2019-03-25T17:18:05.295Z
-updatedAt: 2023-03-29T22:05:18.017Z
-publishedAt: 2023-03-29T22:05:18.017Z
+updatedAt: 2024-07-08T17:06:56.254Z
+publishedAt: 2024-07-08T17:06:56.254Z
 firstPublishedAt: 2019-03-25T17:24:44.319Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,8 +17,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 En el Admin VTEX, en **Configuración de la tienda > Pedidos > Autorización de pedidos**, es posible controlar la aprobación de pedidos con divergencia de precios en su tienda.
 
-![print_autorizacao_pedidos_ES](https://drive.google.com/uc?export=download&id=1x7OUw3EN35oqhlmJ5Jq9Oe5X2xpJJhSg)
-
+![print_autorizacao_pedidos_ES](//images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/f0ce68dc289044000a20ec391475c4c9/print_autorizacao_pedidos_ES.png)
 La divergencia de precios en pedidos se pueden encontrar en dos escenarios principales:
 
 - [Descuentos manuales](https://help.vtex.com/es/tutorial/como-funciona-a-autorizacao-de-pedidos--3MBK6CmKHAuUjMBieDU0pn#descuentos-manuales)
diff --git a/docs/tutorials/es/how-order-authorization-workss.md b/docs/tutorials/es/how-order-authorization-workss.md
index ee586311f..10a42b2ff 100644
--- a/docs/tutorials/es/how-order-authorization-workss.md
+++ b/docs/tutorials/es/how-order-authorization-workss.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 En el módulo de gestión de pedidos, __La Autorización de pedidos__ permite el control y la aprobación de pedidos con divergencias de precios en su tienda.
 
-![autorização-de-pedidos ES](https://images.ctfassets.net/alneenqid6w5/7bov7XWzWzQ2qFPZ5OnJg7/3044ddd44a533fbd7a5d2499e7353374/autoriza____o-de-pedidos__ES.png)
+![autorização-de-pedidos ES](//images.ctfassets.net/alneenqid6w5/7bov7XWzWzQ2qFPZ5OnJg7/3044ddd44a533fbd7a5d2499e7353374/autoriza____o-de-pedidos__ES.png)
  
 Las divergencias de precios entre pedidos se pueden encontrar en dos escenarios principales:
 
diff --git a/docs/tutorials/es/how-promotion-competition-works.md b/docs/tutorials/es/how-promotion-competition-works.md
new file mode 100644
index 000000000..6aaebfc34
--- /dev/null
+++ b/docs/tutorials/es/how-promotion-competition-works.md
@@ -0,0 +1,213 @@
+---
+title: 'Cómo funciona la competencia de promociones'
+id: tutorials_2270
+status: PUBLISHED
+createdAt: 2017-04-27T21:55:27.997Z
+updatedAt: 2023-11-14T16:52:38.320Z
+publishedAt: 2023-11-14T16:52:38.320Z
+firstPublishedAt: 2017-04-27T23:03:50.791Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 46G4yHIZerH7B9Jo0Iw5KI
+slug: como-funciona-la-competencia-de-promociones
+locale: es
+legacySlug: entendiendo-la-competencia-de-las-promociones-2
+subcategory: 1yTYB5p4b6iwMsUg8uieyq
+---
+
+El módulo Promociones sigue una lógica para definir qué promoción se aplicará a una compra determinada, al igual que [Checkout](https://help.vtex.com/es/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) selecciona qué seller realizará el fullfilment del pedido. Esta lógica se denomina competencia de promociones.
+
+Estos son los escenarios donde ocurre la competencia de promociones:
+
+- Promociones con el mismo tipo de descuento
+- Aplicación de más de una promoción en el mismo ítem
+- Promociones no [configuradas](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restricciones-y-limitaciones-de-uso) para permitir que las promociones se acumulen.
+
+Para entender cómo funciona la selección de la promoción que se aplicará, explicamos a continuación algunos conceptos del módulo Promociones.
+
+- [Efectos de las promociones](#efectos-de-las-promociones)
+- [Ordenación de aplicación de las promociones](#ordenacion-de-aplicacion-de-las-promociones)
+- [Acumulación de promociones](#acumulacion-de-promociones)
+- [Estrategia de competencia entre las promociones](#estrategia-de-competencia-entre-las-promociones)
+
+## Efectos de las promociones
+
+Los efectos de las promociones están relacionados con el beneficio que cada promoción ofrece. Existen cuatro tipos:
+
+- **Descuento sobre el precio:** son promociones que aplican un descuento porcentual o nominal sobre el valor del producto. Aquí se incluyen algunos descuentos del tipo [promoción regular](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), [descuento progresivo](https://help.vtex.com/es/tutorial/desconto-progressivo--tutorials_324) y cualquier otra mecánica que incida en el precio de un ítem.
+- **Descuento en el envío:** son las [promociones con descuento de envío](https://help.vtex.com/es/tutorial/configurar-promocoes-de-frete--6Lo5BR61KMiUFAAHGCdgfW).
+- **Regalos:** son promociones que otorgan un regalo al cliente.
+- **Fórmula:** son las promociones con tipo de descuento nominal basado en [fórmula](https://help.vtex.com/es/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV), que es una de las opciones dentro de la promoción regular.
+
+## Ordenación de aplicación de las promociones
+
+La ordenación es el proceso que define en qué orden se aplicarán las promociones. Esto es importante para entender cuál será el precio final de los ítems agregados al carrito. La ordenación se basa en dos criterios:
+
+- [Ordenación por tipo de promoción y descuento](#ordenacion-por-tipo-de-promocion-y-descuento)
+- [Ordenación por valor](#ordenacion-por-valor)
+
+### Ordenación por tipo de promoción y descuento
+
+Las promociones aplicadas en el carrito respetan el siguiente orden:
+
+1. Porcentual
+2. Descuento Nominal (Monto especifico)
+3. Precio máximo
+4. Compre Junto (no es una promoción regular)
+5. Envío porcentual
+6. Envío nominal
+7. Regalos
+8. Fórmula
+
+### Ordenación por valor
+
+Las promociones aplicadas al carrito que sean del mismo tipo se comparan por su valor de descuento. A este respecto, el módulo Promociones intenta siempre aplicar la promoción más ventajosa para el comprador.
+
+En las promociones del tipo regalo, el orden viene dado por la promoción que ofrezca el mayor número de regalos.
+
+Ejemplo:
+
+- Promoción 1: 30% de descuento sobre el valor del producto.
+- Promoción 2: 50% de descuento
+
+Se dará prioridad a aquella promoción que otorgue el mayor descuento, es decir, el carrito aplicará la **Promoción 2** y a continuación la **Promoción 1**. 
+
+La **Promoción 1** se aplicará sobre el ítem con el valor previamente descontado por la **Promoción 2**.
+
+## Acumulación de promociones
+
+Cuando las promociones se [configuran](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restricciones-y-limitaciones-de-uso) marcando la casilla Aplicar con otras promociones, estas, sean del tipo que sean, siempre se aplicarán al carrito mientras se cumplan las condiciones establecidas. 
+
+Además, todas ellas inciden sobre el valor que ya se descontó al aplicarse la promoción que ganó la competencia de las no acumulativas. El orden de las promociones seleccionadas seguirá la ordenación por tipo y valor, tal y como se describe en el punto 1. 
+
+Por lo tanto, la secuencia de aplicación es:
+
+![promocao3 ES](//images.ctfassets.net/alneenqid6w5/1CAcjiuVQECwqcoA288Aey/251351f394db394a008ccdd699e47c6f/promocao3_ES.png)
+
+<div class="alert alert-warning">
+Los pedidos de origen <a href="https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> ((proporcionados por la tienda) y Fulfillment (entregados por la tienda) no permiten la acumulación de promociones, ya que el uso de las mismas en marketplaces VTEX o externos se limita a algunos tipos específicos.</div> 
+
+## Estrategia de competencia entre promociones
+
+Después de entender cómo se ordenan y acumulan las promociones, vamos a explicar cómo funciona la competencia de promociones no acumulativas.
+
+La selección de cada promoción considera únicamente promociones del mismo tipo de descuento (como se describe en [Efectos de promociones](#efectos-de-promociones)) y que puedan aplicarse, al menos, a un producto en común.
+
+Las promociones del mismo o distinto tipo que aplican a productos diferentes no compiten entre sí, es decir, serían automáticamente acumulativas.
+
+Consulta a continuación las dos estrategias de competencia de promociones: 
+
+- [Competencia por escenario](#competencia-por-escenario)
+- [Competencia por ítem](#competencia-por-item)
+
+<div class="alert alert-info">
+De manera predeterminada, todas las cuentas siguen la estrategia de competencia por escenario. Si el modelo de competencia por ítem se adapta mejor a las necesidades de tu negocio, <a href="https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abre un ticket</a> con nuestro equipo de soporte y solicita el cambio.</div>
+
+### Competencia por escenario
+
+La competencia por escenario sigue la lógica de agrupar aquellas promociones que no compiten con los mismos productos. Entonces, dentro de cada grupo creado, se realiza una comparación para determinar si es el grupo, o bien alguna promoción individual, la que ofrece mayores ventajas al cliente. 
+
+La que conceda el mejor descuento se aplicará al carrito. Fíjate en los ejemplos siguientes:
+
+#### Ejemplo 1
+
+Pedro va a comprar una camiseta de 10 USD + 4 USD de envío. En este pedido pueden aplicarse cinco promociones, todas ellas previamente [configuradas](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restricciones-y-limitaciones-de-uso) con la casilla `Aplicar con otras promociones desmarcada`, para no acumular promociones, excepto la primera:
+
+| Promociones acumulativas | Promociones no acumulativas |
+| ----------- | ----------- |
+| 10 % de descuento | Precio de envío: máximo 12 USD |
+| X | 80 % de descuento en el envío |
+| X | Descuento nominal de 5 USD |
+| X | Regalo al comprar la camiseta |
+
+El carrito mostrará que el precio final de la camiseta es de 4.50 USD y el de envío 0.80 USD. El sistema de promociones aplica la lógica de competencia entre promociones:
+
+- Camiseta de **10 USD**.
+   - Recibe descuento nominal de *5 USD*. Nuevo valor: **5 USD**.
+
+- Precio de envío: **4 USD**.
+   - Se aplica un descuento del *80%*. Nuevo valor: **0.80 USD**.
+   - Se aplica un precio de envío máximo de **12 USD**, pero no es válido porque el valor ya es inferior.
+
+A continuación, se aplican las promociones acumulativas:
+
+- Camiseta de ~~10 USD~~ quedaria en **5 USD**.
+   - Recibe un **10%** de descuento porcentual. Nuevo valor: **4.50 USD**.
+
+Así, el importe final de la compra de Pedro, quedaría:
+
+- Camiseta por **4.50 USD**
+- Envío por **0.80 USD**
+- Regalo al comprar la camiseta
+
+#### Ejemplo 2
+
+Carla creó un carrito con 1 camiseta y 1 par de zapatos. Estos ítems forman parte de colecciones:
+
+| Colección | Ítems | Valores |
+| ----------- | ----------- |  ----------- |
+| 1 | Camiseta | 10 USD |
+| 1 | Calzado | 50 USD |
+| 2 | Camiseta | 10 USD |
+
+- Promotions:
+   1. **10%** de descuento en la primera colección. Configurado para no acumular en el campo `Aplicar con otras promociones`.
+   2. **25%** de descuento en la segunda colección. Configurado para no acumular en el campo `Aplicar con otras promociones`.
+   3. **5%** de descuento en el producto. Configurado para acumular en el campo `Aplicar con otras promociones`. Incluye todos los productos del carrito.
+
+Como las dos primeras promociones se aplican al producto camiseta y no están marcadas para aplicarse con otras promociones, entran en competencia. 
+
+Cuando compiten, el módulo Promociones elegirá la promoción que proporcione el mejor descuento para el cliente. A continuación, se presenta un ejemplo de competencia por escenario.
+
+##### Escenario 1: aplicación de la promoción 1 del 10 % de descuento
+
+| Ítems | Promociones aplicadas | Valores |
+| ----------- | ----------- |  ----------- |
+| Camiseta | Promoción 1 y Promoción 3 | 8.55 USD |
+| Calzado | Promoción 1 y Promoción 3 | 42.75 USD |
+
+La camiseta tendría un precio de **8.55 USD**, aplicando el descuento de la *promoción del 10%* y *descuento del 5%* sobre el valor del producto. El calzado tendría un precio de: **42.75 USD** al aplicarse  la *promoción 1 del 10%* más el *descuento del 5%* sobre el producto.
+
+El valor total del pedido quedaría en **51.30 USD**.
+
+| Ítems | Promociones aplicadas | Valores |
+| ----------- | ----------- |  ----------- |
+| Camiseta | Promoción 2 y Promoción 3 | 7.12 USD |
+| Calzado | Promoción 2 y Promoción 3 | 47.50 USD |
+
+La camiseta tendría un precio de **7.12 USD**, aplicando el descuento de la *promoción 2 del 25%* más el *descuento del 5%* sobre el valor del producto. El calzado tendría un precio de **47.50 USD**, aplicando solamente el **5% de descuento** sobre el producto, ya que no forma parte de la colección de la promoción 2.
+
+En este escenario, el valor total del pedido quedaría en **54.62 USD**.
+
+En resumen, como en el escenario 1 el valor final del pedido es más barato para el cliente de la tienda, se ajusta a la premisa de ofrecer el mejor descuento posible. Por lo tanto, VTEX opta por aplicar la promoción 1 del 10 % para ambos ítems. Esto se debe a que las promociones 1 y 2 no han podido aplicarse por no estar marcada la casilla Aplicar con otras promociones.
+
+### Competencia por ítem
+
+El módulo Promociones también puede considerar el mayor descuento para el cliente en cada ítem del carrito. Para ello, el sistema tiene en cuenta las promociones aplicables a un ítem y selecciona la mejor, en lugar de considerar una combinación de promociones a nivel del carrito.
+
+En la competencia por ítem, lo que ocurriría siguiendo los datos del ejemplo anterior sería:
+
+| Colección | Ítems | Valores |
+| ----------- | ----------- |  ----------- |
+| 1 | Camiseta | 10 USD |
+| 1 | Calzado | 50 USD |
+
+- Promotions:
+   1. **10%** de descuento en la primera colección. Configurado para no acumular en el campo `Aplicar con otras promociones`.
+   2. **25%** de descuento en la segunda colección. Configurado para no acumular en el campo `Aplicar con otras promociones`.
+   3. **5%** de descuento en el producto. Configurado para acumular en el campo `Aplicar con otras promociones`. Incluye todos los productos del carrito.
+
+Aplicando la promoción, los valores serían:
+
+| Ítems | Promociones aplicadas | Valores |
+| ----------- | ----------- |  ----------- |
+| Camiseta | Promoción 2 | 7.50 USD |
+| Calzado | Promoción 1 | 45.00 USD |
+
+La camiseta tendría un precio de **7.50 USD** con el *descuento de la promoción 2, del 25%*. El calzado tendría un precio de **45.00 USD** con el descuento de la *promoción 1, del 10%*.
+
+En este escenario, el valor total del pedido quedaría en **52.50 USD**.
+
+Esta opción ofrecería un descuento menor al cliente que la selección realizada por [competencia por escenario](#competencia-por-escenario). Por lo tanto, esta configuración depende del objetivo de negocios definido por la tienda. 
+
+En caso de que el modelo de competencia por ítem se adapte mejor a las necesidades de tu negocio, [abre un ticket](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) con nuestro equipo de soporte y solicita el cambio.
diff --git a/docs/tutorials/es/how-recursive-marketplace-works.md b/docs/tutorials/es/how-recursive-marketplace-works.md
index 74c16f55e..541d7ae7d 100644
--- a/docs/tutorials/es/how-recursive-marketplace-works.md
+++ b/docs/tutorials/es/how-recursive-marketplace-works.md
@@ -33,7 +33,7 @@ Con eso:
 
 - __Cuando una tienda VTEX es intermediaria en el flujo de un pedido__: pedido de cadena con __Chain Workflow__:
 
-![marketplace-recursivo-chain-order-workflow](https://images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
+![marketplace-recursivo-chain-order-workflow](//images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
 
 
 ## Configuración
diff --git a/docs/tutorials/es/how-shipping-calculation-works.md b/docs/tutorials/es/how-shipping-calculation-works.md
index 91fcefac0..a68c728e1 100644
--- a/docs/tutorials/es/how-shipping-calculation-works.md
+++ b/docs/tutorials/es/how-shipping-calculation-works.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona el cálculo del envío'
 id: tutorials_116
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:59.694Z
-updatedAt: 2022-06-21T14:55:49.737Z
-publishedAt: 2022-06-21T14:55:49.737Z
+updatedAt: 2023-07-25T19:55:42.137Z
+publishedAt: 2023-07-25T19:55:42.137Z
 firstPublishedAt: 2017-04-27T23:00:43.230Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -85,7 +85,6 @@ En el Admin VTEX, se pueden configurar criterios y prioridades distintas para la
 - **Flete:** los precios del flete se configuran en las [tarifas de envío](https://help.vtex.com/es/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM), excepto la [tarifa del muelle de carga](https://help.vtex.com/es/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV), que es un valor adicional opcional que se configura al agregar el muelle de carga a un almacén.
 - **Plazo:** el tiempo para el envío se configura en la [estimación del SLA](#estimacion-del-tiempo-de-envio).
 - **División de paquetes:** los criterios adoptados se configuran en el módulo _Checkout_. Obtén más información en [División de pedidos y división de entregas](https://help.vtex.com/es/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV).
-- **Prioridad del stock:** la configuración de un criterio distinto para priorizar el stock solo puede hacerse por la API, a través de [Create/update warehouse](https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse), agregando la propiedad `priority`. 
 
 ## Estimación del tiempo de envío
 
diff --git a/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md b/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
index 812637bcc..b5c0fffc9 100644
--- a/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
+++ b/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
@@ -3,8 +3,8 @@ title: ' Cómo funciona el flete cuando la entrega es hecha por el marketplace (
 id: EY1l6tYW3IUquwwwcQqwQ
 status: PUBLISHED
 createdAt: 2017-08-28T23:17:57.225Z
-updatedAt: 2021-08-11T17:11:00.299Z
-publishedAt: 2021-08-11T17:11:00.299Z
+updatedAt: 2024-02-05T15:48:24.006Z
+publishedAt: 2024-02-05T15:48:24.006Z
 firstPublishedAt: 2017-08-29T20:09:40.790Z
 contentType: tutorial
 productTeam: Channels
@@ -23,7 +23,8 @@ Este flujo evita validaciones innecesarias del pedido, simplifica la configuraci
 
 La regla para elegir el stock que servirá al SKU siempre será de la siguiente manera:
 
-1. Mayor cantidad disponible del SKU.
+1. Memor cantidad disponible del SKU.
+    > _Para evitar que se retenga stock con pocos ítems._ 
 2. Menor tiempo de ruta entre stock y muelle.
 3. Menor precio de ruta entre stock y muelle.
 
@@ -35,7 +36,7 @@ Si el pedido tiene varias unidades de un SKU, es necesario que alguno de los sto
 
 Como la entrega será realizada por el marketplace, el OMS no traerá información del valor del flete, ya que esto quedó acordado entre el marketplace y el comprador del producto, no acarreando cargo a la tienda. La información de plazo que aparece en el pedido no es la que el marketplace informó a VTEX, sino una simulación de flete hecha en el momento de integrar el pedido.  
 
-En el lugar de las identificaciones de transportadora y tipo de entrega se presenta la información `vtex:fob_1111`, donde `1111` corresponderá al ID del stock en el que se reservó el SKU.
+En el lugar de las identificaciones de transportadora y tipo de entrega se presenta la información `vtex:fob_1111`, donde `1111` corresponderá al ID del muelle.
 
 ## API
 
@@ -43,7 +44,7 @@ Al igual que en la interfaz del OMS, la API trae la información `vtex:fob_1111`
 
 Es importante que el ERP sea adecuado para recibir los datos en este formato.
 
-![](https://images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
+![](//images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
 
 ## Etiqueta
 
@@ -51,6 +52,6 @@ El pedido se envía en un contrato con la oficina de correos del propio marketpl
 
 Es posible acceder a la etiqueta directamente por el OMS, debajo de los ítems del pedido. Basta hacer clic en el link y se abrirá una nueva ventana ya con el PDF de la etiqueta.
 
-![Etiqueta de entrega por Correios (BR) - Marketplace](https://images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/f715c425b47359c8d8735cde8aac8377/Screen_Shot_2020-03-25_at_11.44.05.png)
+![Etiqueta de entrega por Correios (BR) - Marketplace](//images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/f715c425b47359c8d8735cde8aac8377/Screen_Shot_2020-03-25_at_11.44.05.png)
 
-En el caso de que se quiera aprovechar la etiqueta dentro del ERP, esta también está disponible en la [API de Pedidos](https://developers.vtex.com/reference/orders#getorder), en el array `trackingHints` que se encuentra en el objecto `shippingData`.
+En el caso de que se quiera aprovechar la etiqueta dentro del ERP, esta también está disponible en la [Marketplace Protocol API](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/order-integration/orders), sepa más en [New Order Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-collect-orders#scenario-12-order-with-tracking-hints).
diff --git a/docs/tutorials/es/how-subscriptions-work.md b/docs/tutorials/es/how-subscriptions-work.md
index adf8d4973..6f121f844 100644
--- a/docs/tutorials/es/how-subscriptions-work.md
+++ b/docs/tutorials/es/how-subscriptions-work.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona Suscripciones '
 id: frequentlyAskedQuestions_4453
 status: PUBLISHED
 createdAt: 2019-01-24T20:46:00.886Z
-updatedAt: 2023-02-15T23:42:14.386Z
-publishedAt: 2023-02-15T23:42:14.386Z
+updatedAt: 2024-07-24T17:36:44.989Z
+publishedAt: 2024-07-24T17:36:44.989Z
 firstPublishedAt: 2019-01-24T22:14:56.290Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,13 +17,15 @@ subcategory: 1rA9wuuskW3PpjvMrhatAM
 
 El **Sistema de Suscripciones** es una aplicación desarrollada por VTEX para facilitar las ventas recurrentes, que sustiye el módulo de *Recurrencia*. Funciona como un programador automático: realiza una recompra en la frecuencia solicitada por el cliente de la tienda. 
 
-Su cliente indica con qué frecuencia desea repetir la compra de un determinado SKU y el sistema rehace el pedido de la compra automáticamente en cada periodo programado, con las mismas características configuradas en el pedido original. 
+Su cliente indica con qué frecuencia desea repetir la compra de un determinado SKU y el sistema rehace el pedido de la compra automáticamente en cada periodo programado, con las mismas características configuradas en el pedido original. La suscripción es una forma simple de ahorrarle tiempo a su cliente y traer un flujo programado de ventas adicional a su tienda. 
 
-Una suscripción para VTEX consiste en una lista de SKUs vinculada a cierta configuración de compra. Todas las operaciones de gestión giran en torno a la entidad «Suscripción», que contiene toda la información necesaria para generar el pedido correspondiente. El diagrama a continuación presenta el concepto de suscripción:
+Una suscripción para VTEX consiste en una lista de SKUs vinculada a cierta configuración de compra. Todas las operaciones de gestión giran en torno a la entidad «Suscripción», que contiene toda la información necesaria para generar el pedido correspondiente, tal como:
 
-![img8 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/0d226ff2f1bbcf31e803c7b9d297e35a/img8_subscriptions_ES_2.png)
-
-La suscripción es una forma simple de ahorrarle tiempo a su cliente y traer un flujo programado de ventas adicional a su tienda. 
+- Perfil de usuario
+- Dirección
+- Forma de pago
+- Frecuencia
+- Fecha de inicio del pedido por subscripción
 
 ## Cómo el cliente de su tienda genera un pedido con Suscripciones 
 
@@ -43,6 +45,10 @@ Para ello, solo hay que entrar a la página **Mi cuenta** en el sitio web de su
 
 ## Cómo el cliente de su tienda visualiza las Suscripciones
 
+<div class = "alert alert-info">
+En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
+</div>
+
 Después de finalizar el pedido con Suscripción, su cliente visualiza en la página **Mi cuenta** la sección **Suscripciones**. En esta sección, el cliente también puede encontrar la lista de suscripciones realizadas con los detalles y el estado individual. Su cliente también recibirá por *email* una confirmación de la suscripción y del pedido generado.
 
 La comunicación con su cliente acerca de la suscripción se llevará a cabo por el módulo **Centro de mensajes**. Consulte nuestro artículo [Correos Electrónicos Transaccionales para Pedidos de Suscripción](https://help.vtex.com/es/tutorial/e-mails-transacionais-para-pedidos-de-assinatura--2NYHqHMRqZ43Cn6s84ZCB5). 
@@ -104,3 +110,5 @@ Sí, el precio que paga el cliente por la suscripción se basa en el precio regi
 
 12. **¿A qué hora se crean pedidos de suscripción?**
 La creación de pedidos de suscripción se realiza entre 6:00 y 7:00 de la mañana, con referencia a la zona de Brasil (GMT-3).
+
+13. **¿La funcionalidad Suscripciones funciona con el Seller Portal?** No, Suscripciones no funciona con el [Seller Portal](https://help.vtex.com/es/tutorial/how-to-set-up-your-store-on-seller-portal).
diff --git a/docs/tutorials/es/how-the-carrefour-integration-works.md b/docs/tutorials/es/how-the-carrefour-integration-works.md
index e80903475..cc3154d69 100644
--- a/docs/tutorials/es/how-the-carrefour-integration-works.md
+++ b/docs/tutorials/es/how-the-carrefour-integration-works.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona la integración con Carrefour'
 id: UbtveAQnoQGKOkQIYG0uQ
 status: PUBLISHED
 createdAt: 2018-09-26T13:35:41.191Z
-updatedAt: 2021-07-09T19:05:35.482Z
-publishedAt: 2021-07-09T19:05:35.482Z
+updatedAt: 2023-09-22T20:09:43.231Z
+publishedAt: 2023-09-22T20:09:43.231Z
 firstPublishedAt: 2018-10-11T20:58:12.080Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/how-the-order-replacement-works.md b/docs/tutorials/es/how-the-order-replacement-works.md
index 6eedb1f72..be45a7e8d 100644
--- a/docs/tutorials/es/how-the-order-replacement-works.md
+++ b/docs/tutorials/es/how-the-order-replacement-works.md
@@ -62,7 +62,7 @@ Con esta funcionalidad, los usuarios de su tienda ganan una página de Mis Pedid
 
 ![meus pedidos1 ES](//images.contentful.com/alneenqid6w5/2ebQjrhfvOOCQMY486QSy4/3bc4cd2897dd9414e0a8b42c56bed1ff/meus_pedidos1_ES.png)
 
-![meus pedidos3 ES](https://images.ctfassets.net/alneenqid6w5/6yYHPkdA8EeIyAU4iUEKOI/f7fa26cebb8d40dce657324941fcc02e/meus_pedidos3_ES.png)
+![meus pedidos3 ES](//images.ctfassets.net/alneenqid6w5/6yYHPkdA8EeIyAU4iUEKOI/f7fa26cebb8d40dce657324941fcc02e/meus_pedidos3_ES.png)
 
 Al seleccionar **Alterar pedido**, el cliente es llevado a una pantalla en la que elige qué información le gustaría sustituir:
 
diff --git a/docs/tutorials/es/how-the-seller-portal-catalog-works.md b/docs/tutorials/es/how-the-seller-portal-catalog-works.md
index 5230aa96f..fdd064611 100644
--- a/docs/tutorials/es/how-the-seller-portal-catalog-works.md
+++ b/docs/tutorials/es/how-the-seller-portal-catalog-works.md
@@ -21,7 +21,7 @@ El Catálogo del Seller Portal es un módulo donde usted configura el surtido de
 
 La arquitectura del Catálogo del Seller Portal se basa en algunos conceptos fundamentales que se distribuyen según la siguiente jerarquía:
 
-![ilustra-catalogoES](https://images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/372a36eabdf9dec772108dcffa655814/ilustra-catalogoES.png)
+![ilustra-catalogoES](//images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/372a36eabdf9dec772108dcffa655814/ilustra-catalogoES.png)
 
 - **Categorías:** formas de organizar sus productos. Usted no puede agregar sus propias Categorías, ya que el marketplace define cuáles estarán disponibles para categorizar sus productos. Es obligatorio que cada producto esté relacionado con una de las categorías que fueron creadas por el marketplace.   
 - **Marcas:**  parte de los atributos que caracterizan a los Productos de su tienda. Permite que sus clientes puedan encontrar lo que buscan de forma más específica.   
diff --git a/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md b/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md
index fac36e637..c0e801261 100644
--- a/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md
+++ b/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 La app [Carrito Compartido](https://apps.vtex.com/vtex-social-selling/p) permite a los vendedores seleccionar productos para sus clientes y compartir el carrito lleno por canales como WhatsApp, Facebook Messenger y correo electrónico.
 
-![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artículo explica cómo instalar la app y configurar la funcionalidad en su tienda. Una vez completados los pasos de activación, sus vendedores podrán seguir las [instrucciones de uso](https://help.vtex.com/es/tutorial/como-usar-o-app-carrinho-compartilhavel--3ePPpkmeZ96GXbeIoGZbTN) para comenzar sus estrategias de Social Selling.
 
@@ -84,7 +84,7 @@ Si desea personalizar los colores de los botones de la interfaz de carrito compa
 
 En la siguiente imagen, la opción A muestra los colores originales y la opción B una posible personalización.
 
-![shareable-cart-ui-customization](https://images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
+![shareable-cart-ui-customization](//images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
 
 El código que figura a continuación debe añadirse al final del archivo `checkout5-custom.css` o `checkout6-custom.css`, disponible para su personalización en *Configuración de la tienda > Checkout > Código*. El archivo que debe editarse depende de la versión de Checkout utilizada por su tienda.
 
diff --git a/docs/tutorials/es/how-to-alter-a-banner.md b/docs/tutorials/es/how-to-alter-a-banner.md
index 51cdfc53b..1dec958d1 100644
--- a/docs/tutorials/es/how-to-alter-a-banner.md
+++ b/docs/tutorials/es/how-to-alter-a-banner.md
@@ -22,14 +22,14 @@ Para ejemplo, usaremos un banner de la Home en el paso a paso, pero estas instru
 3. Haga clic en la carpeta **“Sites and Channels”**
 4. Haga clic en el **nombre de su tienda**.
 5. Haga clic en la **carpeta "/"**
-![cms_instrução ES](https://images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
+![cms_instrução ES](//images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
 6. Haga clic en el archivo **“home”**
 7. Haga clic en la pestaña **Settings**
 8. Haga clic en el “lápiz” de edición. 
-![cms-home-settings ES](https://images.ctfassets.net/alneenqid6w5/2NaTvILk6k06CqmmWmQC8i/7e962cbf2fe343cb97dca469259b01ef/banner_home_settings_-_es.png)
+![cms-home-settings ES](//images.ctfassets.net/alneenqid6w5/2NaTvILk6k06CqmmWmQC8i/7e962cbf2fe343cb97dca469259b01ef/banner_home_settings_-_es.png)
 9. Se abrirá la ventana de banners
 10. Haga clic en el "lápiz" que aparecerá
-![cms_home_settings_lapis ES](https://images.ctfassets.net/alneenqid6w5/1XGZSbmX4MEs2kCcaKaaGu/8861c836393525c7d4f10fd688018816/cms_settings_lapis_es.png)
+![cms_home_settings_lapis ES](//images.ctfassets.net/alneenqid6w5/1XGZSbmX4MEs2kCcaKaaGu/8861c836393525c7d4f10fd688018816/cms_settings_lapis_es.png)
 11. Se abrirá el formulario de banner;
 
 **Modificar los contenidos del formulario:**
diff --git a/docs/tutorials/es/how-to-archive-ratestaxes.md b/docs/tutorials/es/how-to-archive-ratestaxes.md
index b8a326c0f..9a573ffd0 100644
--- a/docs/tutorials/es/how-to-archive-ratestaxes.md
+++ b/docs/tutorials/es/how-to-archive-ratestaxes.md
@@ -17,7 +17,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 Si quiere usted que una tasa creada no permanezca en la lista principal por no ser más utilizada, por ejemplo, puede desplazarla a la lista de archivadas. Al hacerlo, la tasa tendrá automáticamente alterado su status para inactivo. Para hacerlo siga los pasos siguientes:
 
-![ejemplo 1](https://images.ctfassets.net/alneenqid6w5/58rtXjsuvCsCyoyCUmUk4w/4a8253c930bdb09e01886162148e5cf7/ejemplo_1.png)
+![ejemplo 1](//images.ctfassets.net/alneenqid6w5/58rtXjsuvCsCyoyCUmUk4w/4a8253c930bdb09e01886162148e5cf7/ejemplo_1.png)
 
 1. En el Admin VTEX, accede a *Promociones > Impuestos*, o escribe *Impuestos* en la barra de búsqueda en la parte superior de la página.
 2. Busque la tasa que desea archivar.
diff --git a/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
index 7dd61d8d8..134cfd45d 100644
--- a/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
@@ -21,11 +21,11 @@ Para recuperar la IP de un cliente que realizó un pedido en su tienda, basta an
 
 Al abrir una ordén, haga clic en "Ver detalles de la transacción" en la caja de pagos:
 
-![ip pedido1 ES](https://images.ctfassets.net/alneenqid6w5/57bJimzndm6e0US0GywG6e/7830e3b7c8b98544013781daacc949d5/ip_pedido1_ES.png)
+![ip pedido1 ES](//images.ctfassets.net/alneenqid6w5/57bJimzndm6e0US0GywG6e/7830e3b7c8b98544013781daacc949d5/ip_pedido1_ES.png)
 
 Finalmente, la IP se visualiza en la parte superior derecha:
 
-![ip pedido2 ES](https://images.ctfassets.net/alneenqid6w5/3M7hIdC8la28CCkq2g0Wou/a3eb0f89c0f1b1c8112c533ba059c3a2/ip_pedido2_ES.png)
+![ip pedido2 ES](//images.ctfassets.net/alneenqid6w5/3M7hIdC8la28CCkq2g0Wou/a3eb0f89c0f1b1c8112c533ba059c3a2/ip_pedido2_ES.png)
 
 Ver más detalles en [Cómo visualizar detalle del pedido](/es/tutorial/como-visualizar-detalle-del-pedido)
 
diff --git a/docs/tutorials/es/how-to-change-orders-beta.md b/docs/tutorials/es/how-to-change-orders-beta.md
new file mode 100644
index 000000000..f751e6133
--- /dev/null
+++ b/docs/tutorials/es/how-to-change-orders-beta.md
@@ -0,0 +1,217 @@
+---
+title: 'Cómo modificar pedidos (Beta)'
+id: 7btlG91rb6sHpW1dkd2kBw
+status: PUBLISHED
+createdAt: 2023-11-27T22:40:33.769Z
+updatedAt: 2024-04-09T18:03:22.045Z
+publishedAt: 2024-04-09T18:03:22.045Z
+firstPublishedAt: 2023-11-28T15:16:50.272Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: como-modificar-pedidos-beta
+locale: es
+legacySlug: como-modificar-pedidos-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+<div class="alert alert-info">
+Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar <b>Modificar pedido (Beta)</b>, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a> e informa el nombre del <a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> en que deseas activarla.
+</div>
+
+La funcionalidad [Modificar pedido (beta)](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ) brinda la posibilidad de editar un pedido de múltiples maneras, ya sea para atender las preferencias del cliente, abordar la falta de disponibilidad de productos u otras razones. 
+
+Este artículo muestra las formas en que se puede modificar un pedido y describe cómo llevar a cabo estas acciones. Se estructura en las siguientes secciones:
+
+* [Requisitos](#requisitos)
+* [Tipos de modificaciones en los pedidos](#tipos-de-modificaciones-en-los-pedidos)
+* [Acciones comunes](#acciones-comunes)
+* [Errores de procesamiento](#errores-de-procesamiento)
+
+<div class="alert alert-warning">
+Para conocer las <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ#caracteristicas-generales">características generales</a> en escenarios de modificación de pedido, incluyendo reserva, actualización de stock y cuentas franquicia, o para comprender cuestiones de <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ#cambios-de-precio">precio, pago y factura</a>, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Cómo funciona Modificar pedido (Beta)</a>.
+</div>
+
+## Requisitos
+
+Existen algunas condiciones para la modificación de pedidos relacionadas con el status del pedido. Consulta los detalles a continuación.
+
+### Status del pedido a modificar
+
+Durante el [flujo del pedido](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196), el único status en el que **Modificar pedido (beta)** puede realizarse en el Admin VTEX es `preparando envío`. Para obtener información sobre modificaciones a través de API, consulta el artículo [Cómo funciona Modificar pedido (beta)](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ).
+
+### Permiso en Licence Manager
+
+Para que un usuario pueda modificar pedidos, su [rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) debe estar asociado con al menos uno de los siguientes [recursos de Licence Manager](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3):
+
+* `Orders Full Access`
+* `Change order`
+
+## Tipos de modificaciones en los pedidos
+
+Las principales modificaciones en los pedidos que se pueden realizar a través del Admin VTEX son: 
+
+* **Agregar:** una cantidad de ítems o nuevos productos.
+* **Remover:** una cantidad parcial o total de ítems.
+* **Modificar peso:** posibilidad de modificar el peso de los ítems, aumentándolo o disminuyéndolo según necesidad.
+* **Sustituir ítems:** permite reemplazar unos ítems por otros, incluyendo aquellos con precios basados en peso.
+* **Modificar precio:** [modificar el valor total del pedido](https://help.vtex.com/es/tutorial/alterar-valor-total-do-pedido--2asq4BmxvSD8Tw9xpfZuMo).
+
+Todas estas acciones se realizan a través de la [página de detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), a la que se puede acceder de dos formas, descritas a continuación.
+
+### Acceder al pedido desde la página Todos los pedidos
+
+En el Admin VTEX, ve a **Pedidos >** [Todos los pedidos](https://help.vtex.com/es/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi), y haz clic en el pedido deseado, o ingresa **Todos los pedidos** en la barra de búsqueda de la parte superior de la página. A continuación, haz clic en el pedido deseado. Utiliza los filtros para refinar la búsqueda si es necesario.
+
+### Acceder al pedido mediante la barra de búsqueda global
+
+Los pedidos pueden buscarse desde cualquier sección del Admin VTEX, utilizando la barra de búsqueda situada en la parte superior de la página. Solo hay que seleccionar la opción `Pedidos` en la esquina derecha de la barra y utilizar cualquiera de los siguientes criterios:
+
+* ID del pedido
+* Nombre del cliente
+* Email del cliente
+* Documento del cliente 
+
+Una vez en la página de detalles del pedido, puedes realizar las siguientes modificaciones:
+
+* [Agregar ítems](#agregar-items)
+* [Agregar nuevo producto](#agregar-nuevo-producto)
+* [Remover ítems](#remover-items)
+* [Remover producto](#remover-producto)
+* [Sustituir ítems](#sustituir-items)
+* [Modificar peso](#modificar-peso)
+
+<div class = "alert alert-info">
+Se puede realizar una sola modificación en el pedido o combinar varias a la vez. No hay un límite específico respecto a la cantidad de veces que el pedido puede modificarse. Para obtener más información, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Cómo funciona Modificar pedido (beta)</a>.
+</div>
+
+### Agregar ítems
+
+Para agregar uno o más ítems al pedido, sigue estos pasos:
+
+1. En el Admin VTEX, accede a la página de detalles del pedido en **Pedidos >** [Todos los pedidos](#acceder-al-pedido-desde-la-pagina-todos-los-pedidos) o por la [barra de búsqueda global](#acceder-al-pedido-mediante-la-barra-de-busqueda-global).
+2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
+3. En la página **Gestionar ítems del pedido**, haz clic en la flecha hacia arriba <i class="fas fa-angle-up"></i> hasta alcanzar la cantidad que desees, o ingresa el número en el campo. Después, la página mostrará el precio y la cantidad anterior tachados y aparecerá el siguiente mensaje: _"Ítem editado"_. 
+
+    ![change_order_adding_items_ES](//images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/9ed7c426af47193fb9a731a9cfe9911e/change_order_adding_items_ES.png)
+
+4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
+5. Haz clic en `Revisar y aplicar`.
+6. En el campo **Motivo de las modificaciones**, describe brevemente el motivo por el que se modifica el pedido. Si lo deseas, revisa nuevamente las modificaciones realizadas.
+7. Haz clic en `Aplicar`. Aparecerá el siguiente mensaje de confirmación: _“Solicitud de modificación completada”._
+
+Una vez hecho esto, serás redirigido a la página de detalles del pedido y en la sección **Facturación pendiente** puedes ver la nueva cantidad de ítems.
+
+### Agregar nuevo producto
+
+Para agregar uno o más productos al pedido, sigue estos pasos:
+
+1. En el Admin VTEX, accede a la página de detalles del pedido en **Pedidos >** [Todos los pedidos](#acceder-al-pedido-desde-la-pagina-todos-los-pedidos) o por la [barra de búsqueda global](#acceder-al-pedido-mediante-la-barra-de-busqueda-global).
+2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
+3. En la página **Gestionar ítems del pedido**, haz clic en <i class="fas fa-plus"></i> `Agregar ítem`.
+4. En la página **Agregar ítems**, en la <i class="fas fa-search"></i> barra de búsqueda, ingresa el nombre del producto deseado.
+5. Haz clic en <i class="fas fa-plus"></i> `Seleccionar`. Puedes añadir tantos productos como quieras, solo tienes que repetir el procedimiento. Con cada nueva adición, aparece el siguiente mensaje: _"Ítem seleccionado"_.
+  > Si haces clic en el nombre del producto, se te redirigirá a la página del producto en el sitio web de la tienda.
+6. A continuación, haz clic en `Agregar ítems seleccionados`. Aparecerá el siguiente mensaje: _"Ítems agregados"_.
+
+    ![change_order_adding_product_ES](//images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/24eff795e29b14252157be1dd0b510e1/change_order_adding_product_ES.png)
+
+4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
+8. Haz clic en `Revisar y aplicar`.
+9. En el campo **Motivo de las modificaciones**, describe brevemente el motivo por el que se modifica el pedido. Si lo deseas, revisa nuevamente las modificaciones realizadas.
+10. Haz clic en `Aplicar`. Aparecerá el siguiente mensaje de confirmación: _“Solicitud de modificación completada”_.
+
+Una vez hecho esto, serás redirigido a la página de detalles del pedido y en la sección **Facturación pendiente**, puedes ver los nuevos productos agregados.
+
+### Remover ítems
+
+Para remover uno o más ítems del pedido, sigue estos pasos:
+
+1. En el Admin VTEX, accede a la página de detalles del pedido en **Pedidos >** [Todos los pedidos](#acceder-al-pedido-desde-la-pagina-todos-los-pedidos) o por la [barra de búsqueda global](#acceder-al-pedido-mediante-la-barra-de-busqueda-global).
+2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
+3. En la página **Gestionar ítems del pedido**, haz clic en la flecha hacia abajo <i class="fas fa-angle-down"></i> hasta alcanzar la cantidad que desees, o ingresa el número en el campo. Después, la página mostrará el precio y la cantidad anterior tachados y aparecerá el siguiente mensaje: _“Ítem editado”_.
+
+    ![change_order_removing_items_ES](//images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/113a96a1c4ea5ade7dad11d4955fa648/change_order_removing_items_ES.png)
+
+4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
+5. A continuación, haz clic en `Revisar y aplicar`.
+6. En el campo **Motivo de las modificaciones**, describe brevemente el motivo por el que se modifica el pedido. Si lo deseas, revisa nuevamente las modificaciones realizadas.
+7. Haz clic en `Aplicar`. Aparecerá el siguiente mensaje de confirmación: _“Solicitud de modificación completada”_.
+
+Una vez hecho esto, serás redirigido a la página de detalles del pedido y, en la sección **Pendientes de facturación**, puedes ver la cantidad de ítems actualizada.
+
+### Remover producto
+
+Para remover un producto de un pedido, sigue estos pasos:
+
+1. En el Admin VTEX, accede a la página de detalles del pedido en **Pedidos >** [Todos los pedidos](#acceder-al-pedido-desde-la-pagina-todos-los-pedidos) o por la [barra de búsqueda global](#acceder-al-pedido-mediante-la-barra-de-busqueda-global).
+2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
+3. En la página **Gestionar ítems del pedido**, haz clic en el ícono de la papelera <i class="far fa-trash-alt"></i> `Remover ítem`. Aparecerá el siguiente mensaje de confirmación: _“Ítem removido”_.
+
+    ![change_order_removing_product_ES](//images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/71e1b2125064618c40ba8703c94cfd0c/change_order_removing_product_ES.png)
+
+4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
+5. A continuación, haz clic en `Revisar y aplicar`.
+6. En el campo **Motivo de las modificaciones**, describe brevemente el motivo por el que se modifica el pedido. Si lo deseas, revisa nuevamente las modificaciones realizadas.
+7. Haz clic en `Aplicar`. Aparecerá el siguiente mensaje de confirmación: _“Solicitud de modificación completada”_.
+
+Una vez hecho esto, serás redirigido a la página de detalles del pedido y, en la sección **Facturación pendiente,** puedes ver el pedido sin el producto removido.
+
+### Sustituir ítems
+
+Para sustituir ítems del pedido, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a la página de detalles del pedido en **Pedidos >** [Todos los pedidos](#acceder-al-pedido-desde-la-pagina-todos-los-pedidos) o por la [barra de búsqueda global](#acceder-al-pedido-mediante-la-barra-de-busqueda-global).
+2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
+3. En la página **Gestionar ítems del pedido**, en la fila del producto que deseas sustituir, haz clic en el menú <i class="fas fa-ellipsis-v"></i> y selecciona <i class="fas fa-pencil-alt"></i> `Sustituir ítem`.
+4. En la página **Sustitución de productos**, en la <i class="fas fa-search"></i> barra de búsqueda, escribe el nombre del producto que sustituirá al anterior.
+5. Haz clic en <i class="fas fa-plus"></i> `Seleccionar`. Aparecerá el siguiente mensaje: _"Ítem seleccionado"_. Si haces clic en el nombre del producto, se te redirigirá a la página del producto en el sitio web de la tienda.
+6. A continuación, haz clic en `Aplicar`. Aparecerá el siguiente mensaje: _“Modificaciones aplicadas”_.
+7. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
+8. Haz clic en `Revisar y aplicar`.
+9. En el campo **Motivo de las modificaciones**, describe brevemente el motivo por el que se modifica el pedido. Si lo deseas, revisa nuevamente las modificaciones realizadas.
+10. Haz clic en `Aplicar`. Aparecerá el siguiente mensaje de confirmación: _“Solicitud de modificación completada”_.
+
+Una vez hecho esto, serás redirigido a la página de detalles del pedido y en la sección **Facturación pendiente** puedes ver el ítem que sustituyó al anterior producto.
+
+### Modificar peso
+
+Para modificar el peso de un ítem, sigue estos pasos:
+
+1. En el Admin VTEX, accede a la página de detalles del pedido en **Pedidos >** [Todos los pedidos](#acceder-al-pedido-desde-la-pagina-todos-los-pedidos) o por la [barra de búsqueda global](#acceder-al-pedido-mediante-la-barra-de-busqueda-global).
+2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
+3. En la página **Gestionar ítems del pedido**, en la fila del producto deseado, ingresa el nuevo peso en el campo. La unidad de medida especificada se basa en los ajustes del Catálogo. 
+4. Una vez hecho esto, en la página se muestra el precio y el peso anterior tachados, seguido del mensaje _“Ítem editado”_.
+
+    ![change_order_changing_weight_ES](//images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/8013c321665ef7545a865b9583018d07/change_order_changing_weight_ES.png)
+
+5. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
+6. Haz clic en `Revisar y aplicar`.
+7. En el campo **Motivo de las modificaciones**, describe brevemente el motivo por el que se modifica el pedido. Si lo deseas, revisa nuevamente las modificaciones realizadas.
+8. Haz clic en `Aplicar`. Aparecerá el siguiente mensaje de confirmación: _“Solicitud de modificación completada”_.
+
+Una vez hecho esto, serás redirigido a la página de detalles del pedido y, en la sección **Facturación pendiente,** puedes ver el peso actualizado del ítem.
+
+## Acciones comunes
+
+Existen acciones comunes a la hora de realizar cualquier [tipo de modificación](#tipos-de-modificaciones-en-los-pedidos) en el pedido. Puedes consultarlas en esta sección:
+
+### Consultar detalles de los valores modificados
+
+En la página **Gestionar ítems del pedido**, al modificar el pedido, el valor total se actualiza automáticamente en **Valor total**, en la parte inferior de la página. Además, puedes ver las modificaciones de precio resultantes de cada operación realizada. Para ver los detalles de los valores, haz clic en la flecha <i class="fas fa-angle-up"></i> situada junto al valor total.
+
+### Deshacer acciones
+
+En la página **Gestionar ítems del pedido**, puedes deshacer las modificaciones si así lo deseas. Haz clic en el ícono de flecha curva `Deshacer acción`. Una vez hecho esto, aparecerá un mensaje de confirmación: _"Modificación deshecha"_, y la acción se habrá revertido.
+
+![change_order_undoing_actions_ES](//images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/46d482469764b19f63f778309f1c08b0/change_order_undoing_actions_ES.png)
+
+## Errores de procesamiento
+
+En cualquier tipo de [modificación de pedido](#tipos-de-modificaciones-en-los-pedidos), en la página **Gestionar ítems del pedido**, al hacer clic en `Revisar y aplicar`, es posible que la modificación no se apruebe. En este caso, serás redirigido nuevamente a la página de detalles del pedido. Algunos de los motivos por los que se deniegan los cambios son:
+
+* **Ítem no disponible:** el SKU puede [no aparecer en el sitio web de la tienda](https://help.vtex.com/es/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382) o no estar disponible por un error o falta de configuración de catálogo, precio o logística. 
+* **Stock insuficiente:** la cantidad de ítems agregados o sustituidos en la modificación puede ser superior a la cantidad de ítems disponibles para la venta en tu [stock](https://help.vtex.com/es/tutorial/gerenciar-inventario--tutorials_139).
+
+Si la configuración del catálogo y del stock es correcta y los intentos de modificar los pedidos siguen dando error, podría tratarse de un problema de procesamiento de la plataforma. En este caso, ponte en contacto con [nuestro equipo de soporte](https://help.vtex.com/es/support).
+
diff --git a/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md b/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md
index f04dd55c0..c150800d3 100644
--- a/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md
+++ b/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md
@@ -3,8 +3,8 @@ title: 'Modificar el orden de medios de pago en el checkout'
 id: frequentlyAskedQuestions_490
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:54.205Z
-updatedAt: 2022-04-25T15:09:37.985Z
-publishedAt: 2022-04-25T15:09:37.985Z
+updatedAt: 2023-10-31T17:27:08.660Z
+publishedAt: 2023-10-31T17:27:08.660Z
 firstPublishedAt: 2019-01-24T22:12:00.925Z
 contentType: tutorial
 productTeam: Shopping
@@ -16,15 +16,11 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
 Usted puede modificar el orden de visualización de los medios de pago en el Checkout de su tienda de dos formas:
-
 - Por el Admin.
-
 - Por medio de una personalización en JavaScript.
 
 <div class="alert alert-warning">
-
 <strong>Atención:</strong> aunque exista esta posibilidad, por cuestiones de seguridad y performance, <strong>no se recomienda</strong> que usted modifique los archivos JavaScript del Checkout. VTEX no se responsabiliza por cualquier problema generado luego de la edición de este código.
-
 </div>
 
 ## Cómo se establece el orden 
diff --git a/docs/tutorials/es/how-to-check-your-balance.md b/docs/tutorials/es/how-to-check-your-balance.md
index 8ffa03c7d..788d20c0d 100644
--- a/docs/tutorials/es/how-to-check-your-balance.md
+++ b/docs/tutorials/es/how-to-check-your-balance.md
@@ -28,7 +28,7 @@ Para consultar el saldo de su cuenta, realice los siguientes pasos:
 - Haga clic en __Resumen de la Cuenta__.
 - En el lado izquierdo de la pantalla, busque el recuadro __Saldo__.
 
-![saldodisponivelES](https://images.ctfassets.net/alneenqid6w5/7uDrErDTN4Crvs1CGfU0eE/193d46204f73726cbb3941e7e6592c84/image.png_h_250_h_250)
+![saldodisponivelES](//images.ctfassets.net/alneenqid6w5/7uDrErDTN4Crvs1CGfU0eE/193d46204f73726cbb3941e7e6592c84/image.png_h_250_h_250)
 
 El recuadro tiene dos valores. El primero, __Disponible__, presenta el saldo en cuenta libre para transacciones. El segundo, __Saldo a recibir__, muestra la suma de los pagos futuros que se registrarán en la cuenta digital corporativa.
 
diff --git a/docs/tutorials/es/how-to-configure-a-bank-slip.md b/docs/tutorials/es/how-to-configure-a-bank-slip.md
index fe9d447e2..7f53dd190 100644
--- a/docs/tutorials/es/how-to-configure-a-bank-slip.md
+++ b/docs/tutorials/es/how-to-configure-a-bank-slip.md
@@ -3,8 +3,8 @@ title: 'Configurar boleto bancario'
 id: tutorials_447
 status: PUBLISHED
 createdAt: 2017-04-27T22:04:55.249Z
-updatedAt: 2023-03-21T20:14:57.262Z
-publishedAt: 2023-03-21T20:14:57.262Z
+updatedAt: 2024-04-16T14:44:36.023Z
+publishedAt: 2024-04-16T14:44:36.023Z
 firstPublishedAt: 2017-04-27T23:03:25.766Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,22 @@ legacySlug: como-configurar-boleto-bancario
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-El boleto bancario es un instrumento de pago que, para el cobro, basta tener una cuenta bancaria y contratar una cartera de cobro junto al banco. 
+En VTEX, su tienda puede vender a través del [Boleto Bancário](https://help.vtex.com/es/tutorial/boleto-bancario-registrado-flujo--1WlPkeueWQiykUwW8mcM4S). Para configurar el Boleto Bancario, siga los pasos a continuación:
 
-A partir de eso, ya es posible emitir boletos y recibir directamente en su cuenta.
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón "Nuevo proveedor".
+3. Escriba en la barra de búsqueda el nombre del proveedor que procesará el Boleto Bancario.
+4. Rellene los campos del formulario según los datos proporcionados por el proveedor/banco.
+5. Haga clic en `Guardar`.
 
-Hay dos maneras de configurar el boleto:
-- Directamente en VTEX sin un gateway de enlace externo.
-- A través de un gateway de pago, como por ejemplo, PagSeguro. 
+## Configurar condición de pago
 
-Las dos formas de configuración se describen a continuación.
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. En __Boleto__, seleccione la opción __Boleto Bancário__.
+4. Active la condición en el campo __Status__.
+5. En __Procesar con proveedor__, seleccione el proveedor configurado previamente.
+6. Si lo deseas, también puedes [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+7. Haga clic en `Guardar`.
 
-## Cómo configurar
-
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. Acceda a la pestaña __Afiliaciones__.
-3. Haga clic en "__+__".
-4. Llene los campos del formulario de acuerdo con los datos informados por su banco - para cada banco son necesarias informaciones distintas. Por eso, siempre confirme con el banco cuáles son las informaciones obligatorias.
-5. Haga clic en __Guardar__.
-
-OBS.: Ese paso es opcional, pues es posible el catastro de boleto pasando por un Gateway de Pago. En este caso, es necesario catastrar el Gateway de Pago en Afiliaciones de Gateway y realizar la configuración abajo.
-
-Después de la configuración de la Afiliación de Gateway, es necesario configurar la condición de pago. Para eso, siga las configuraciones de cómo crear condiciones de pago.
-
-Con esas configuraciones realizadas, la forma de pago ya estará disponible en el checkout de su tienda.
+Después de seguir los pasos indicados, Boleto Bancário puede tardar hasta 10 minutos en aparecer en la caja de tu tienda como opción de pago.
diff --git a/docs/tutorials/es/how-to-configure-a-custom-payment.md b/docs/tutorials/es/how-to-configure-a-custom-payment.md
index e9cb9e363..8e1c87749 100644
--- a/docs/tutorials/es/how-to-configure-a-custom-payment.md
+++ b/docs/tutorials/es/how-to-configure-a-custom-payment.md
@@ -3,8 +3,8 @@ title: 'Configurar pago personalizado'
 id: tutorials_451
 status: PUBLISHED
 createdAt: 2017-04-27T22:04:32.144Z
-updatedAt: 2021-07-08T19:02:18.536Z
-publishedAt: 2021-07-08T19:02:18.536Z
+updatedAt: 2023-10-18T14:42:25.244Z
+publishedAt: 2023-10-18T14:42:25.244Z
 firstPublishedAt: 2017-04-27T23:03:25.828Z
 contentType: tutorial
 productTeam: Financial
@@ -21,17 +21,17 @@ Esos medios de pago son separados en tres categorías. Cada categoría permite c
 
 ## Pagarés
 
-Pagaré es una promesa de venta que necesita de aprobación manual del tendero para aprobar la transacción. Es utilizada a menudo para poner a disposición el pago a través de dinero. Para configurar Pagarés, acceda a la documentación [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ?&utm_source=autocomplete).
+Pagaré es una promesa de venta que necesita de aprobación manual del tendero para aprobar la transacción. Es utilizada a menudo para poner a disposición el pago a través de dinero. Para configurar Pagarés, acceda a la documentación [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare).
 
 ## Tarjetas de la Tienda (Own Brand)
 
-Permite que usted utilice una tarjeta de crédito con bandera propia de la Tienda. Para configurar este método de pago acceda a la documentación [Configurar pagos con Private Label (bandera propia)](https://help.vtex.com/es/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4?&utm_source=autocomplete).
+Permite que usted utilice una tarjeta de crédito con bandera propia de la Tienda. Para configurar este método de pago acceda a la documentación [Configurar pagos con Private Label (bandera propia)](https://help.vtex.com/es/tutorial/configurar-pagos-con-private-label).
 
 ## Tarjetas de la Tienda (Co-Branded)
 
-Permite que usted utilice una tarjeta de crédito de la Tienda con una de las siguientes banderas: Mastercard, Visa, Amex y Diners. Para configurar este método de pago acceda a la documentación [Configurar pagos con Tarjeta de Tienda (cobranded)](https://help.vtex.com/es/tutorial/configurar-pagamentos-com-cartoes-de-loja-cobranded--jrkLK41IjuquUmyKUi86Q?&utm_source=autocomplete).
+Permite que usted utilice una tarjeta de crédito de la Tienda con una de las siguientes banderas: Mastercard, Visa, Amex y Diners. Para configurar este método de pago acceda a la documentación [Configurar pagos con Tarjeta de Tienda (cobranded)](https://help.vtex.com/es/tutorial/configurar-pagos-con-tarjeta-de-tienda-cobranded).
 
-Después de esta configuración, será necesaria la creación de la [Condición de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455).
+Después de esta configuración, será necesaria la creación de la [Condición de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials).
 
 <div class="alert alert-warning">
 Cuando señale para autorizar automáticamente, el pedido sigue directamente para el status “Preparando Entrega”, o sea, no queda parado en el status “Pago pendiente” aguardando la aprobación, como ocurre caso la flag no esté señalada.
diff --git a/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index 48ec8dd93..9568c7764 100644
--- a/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -30,7 +30,7 @@ En las operaciones B2B, existe la necesidad de mantener relaciones con los compr
 2. En la pestaña __General__, complete el valor deseado en el campo __Valor total mínimo en el carrito__.
 3. Haga clic en `Guardar`.
 
-![Minimum Order Value - ES](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/3571a12b0a5367cc62e982c04e8e7ece/Minimum_Order_Value_-_ES.png)
+![Minimum Order Value - ES](//images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/3571a12b0a5367cc62e982c04e8e7ece/Minimum_Order_Value_-_ES.png)
 
 <div class="alert alert-warning">
 El cliente tiene permitido armar un carrito con un valor menor al especificado en la regla "Valor mínimo total de la compra". Sin embargo, en el momento de finalizar la compra, sólo se completarán los pedidos que sean iguales o superiores al valor especificado.
@@ -42,7 +42,7 @@ El cliente tiene permitido armar un carrito con un valor menor al especificado e
 2. En la pestaña __General__, complete el valor deseado en el campo __Cantidad máxima de un mismo SKU en el carrito__.
 3. Haga clic en `Guardar`.
 
-![Cantidad máxima de un mismo SKU en el carrito](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/cfcc10ac1d2bccfb10fcd174d832f3f3/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_ES.png)
+![Cantidad máxima de un mismo SKU en el carrito](//images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/cfcc10ac1d2bccfb10fcd174d832f3f3/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_ES.png)
 
 <div class="alert alert-warning">
 No hay límites en el número máximo de ítems <b>del mismo SKU</b> por carrito. La única restricción se refiere al número máximo de ítems de <b>SKUs diferentes</b>, que debe ser un máximo de 300 ítems por carrito.
diff --git a/docs/tutorials/es/how-to-configure-payment-conditions.md b/docs/tutorials/es/how-to-configure-payment-conditions.md
index 7addd05e0..037c2be71 100644
--- a/docs/tutorials/es/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/es/how-to-configure-payment-conditions.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar condiciones de pago'
 id: tutorials_455
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-04-27T22:04:07.105Z
-updatedAt: 2023-03-21T21:01:23.792Z
-publishedAt: 2023-03-21T21:01:12.557Z
+updatedAt: 2023-10-18T17:17:55.702Z
+publishedAt: 2023-10-18T17:17:55.702Z
 firstPublishedAt: 2017-04-27T23:03:26.687Z
 contentType: tutorial
 productTeam: Financial
@@ -38,7 +38,7 @@ En los pasos siguientes, utilizaremos la tarjeta de crédito como ejemplo de con
 
 ### A vista
 
-![pagamento-a-vista es](https://images.ctfassets.net/alneenqid6w5/2nH3F7oSW4OMiMQKcoAWeM/a5a96ec62da667f4f853cfc70d2def29/pago-a-vista.png)
+![pagamento-a-vista es](//images.ctfassets.net/alneenqid6w5/2nH3F7oSW4OMiMQKcoAWeM/a5a96ec62da667f4f853cfc70d2def29/pago-a-vista.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
@@ -56,7 +56,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 
 ### En cuotas sin interés
 
-![parcelamento-sem-juros es](https://images.ctfassets.net/alneenqid6w5/185SM0Kebg4S2a8IcysEsG/d0ec61a4b01dd19d2a9bcca5394d50a0/cuotas-sin-interes.png)
+![parcelamento-sem-juros es](//images.ctfassets.net/alneenqid6w5/185SM0Kebg4S2a8IcysEsG/d0ec61a4b01dd19d2a9bcca5394d50a0/cuotas-sin-interes.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
@@ -73,7 +73,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 
 ### En cuotas con interés
 
-![parcelamento-com-juros es](https://images.ctfassets.net/alneenqid6w5/3ZdPenx28oK0yG4QyeIq0c/b7184b8eeeda1573eaa60cf167be0e2c/cuotas-com-interes.png)
+![parcelamento-com-juros es](//images.ctfassets.net/alneenqid6w5/3ZdPenx28oK0yG4QyeIq0c/b7184b8eeeda1573eaa60cf167be0e2c/cuotas-com-interes.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
@@ -91,7 +91,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 14. Para elegir entre interés compuesto e interés simple, haga clic en __Interés compuesto aplicado. Cambiar__. Aparecerá una casilla de verificación que ofrece ambas opciones.
 15. Haga clic en __Guardar__.
 
-![Juros - es](https://images.ctfassets.net/alneenqid6w5/5DQndlL3ixGVYBKBOTsVM7/70c11c8cbf6fa5d088c381c34d63454b/Juros_-_es.png)
+![Juros - es](//images.ctfassets.net/alneenqid6w5/5DQndlL3ixGVYBKBOTsVM7/70c11c8cbf6fa5d088c381c34d63454b/Juros_-_es.png)
 
 #### Intereses Externos
 
@@ -107,4 +107,4 @@ En algunos países, los intereses de las compras parceladas son cobrados directa
 2. En la pestana __Condiciones de pago__, haga clic en el condición de pago que desea eliminar.
 3. Haga clic en el icono de la papelera.
 
-![Remover condición de pago](https://images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/76f4023f4e0262ebaefa8318e46330b3/remover_condicion_pago.png)
+![Remover condición de pago](//images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/76f4023f4e0262ebaefa8318e46330b3/remover_condicion_pago.png)
diff --git a/docs/tutorials/es/how-to-configure-rating-and-review-controls.md b/docs/tutorials/es/how-to-configure-rating-and-review-controls.md
index aa0b8306f..1cc59bf07 100644
--- a/docs/tutorials/es/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/es/how-to-configure-rating-and-review-controls.md
@@ -42,10 +42,10 @@ Diferente de los demás, estos controles necesitan una configuración imprescind
 
 En el registro de Categoria existe la opción de configurar la Avaliação (Evaluación) y normalmente esta configuración se hace en la categoría raíz:
 
-![avaliação-categoria ES](https://images.ctfassets.net/alneenqid6w5/2iOensHpjSW8aYCqi2o2O8/548b7ff362e70275c73dbc9b0b2239d6/avalia____o_es.png)
+![avaliação-categoria ES](//images.ctfassets.net/alneenqid6w5/2iOensHpjSW8aYCqi2o2O8/548b7ff362e70275c73dbc9b0b2239d6/avalia____o_es.png)
 
 Haga click en **Nueva Calificación** y rellene los datos Nome (Nombre) y Texto y después grabe.
 
-![nueva-calificacion-categorias ES](https://images.ctfassets.net/alneenqid6w5/5A1DGDfYGI4syYkYGkAI86/c9fd86d9e6bbe8c61828e28e4cd0f5de/Nueva_calificacion.png)
+![nueva-calificacion-categorias ES](//images.ctfassets.net/alneenqid6w5/5A1DGDfYGI4syYkYGkAI86/c9fd86d9e6bbe8c61828e28e4cd0f5de/Nueva_calificacion.png)
 
 ¡Listo! Sus controles de Reseña y Evaluación están listos para usarse.
diff --git a/docs/tutorials/es/how-to-configure-subscriptions.md b/docs/tutorials/es/how-to-configure-subscriptions.md
index a5eebb65a..81b36fa2c 100644
--- a/docs/tutorials/es/how-to-configure-subscriptions.md
+++ b/docs/tutorials/es/how-to-configure-subscriptions.md
@@ -3,8 +3,8 @@ title: 'Cómo configurar Suscripciones en su tienda'
 id: 1FA9dfE7vJqxBna9Nft5Sj
 status: PUBLISHED
 createdAt: 2019-01-31T16:00:03.228Z
-updatedAt: 2023-04-11T00:33:27.310Z
-publishedAt: 2023-04-11T00:33:27.310Z
+updatedAt: 2024-07-09T14:27:30.778Z
+publishedAt: 2024-07-09T14:27:30.778Z
 firstPublishedAt: 2019-01-31T16:01:57.927Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -67,7 +67,7 @@ Actualmente, los siguientes medios de pago están habilitados para pedidos de su
   <p>Para colocar a disposición la opción de pago <strong>Tarjeta de crédito</strong>, contacte al adquirente de cu tienda y verifique si acepta transacciones de compras recurrentes de tarjetas con token (sin CVV). El sistema de <strong>Suscripciones</strong> utilizará los mismos datos de la tarjeta empleada en la primera compra para realizar las demás compras de suscripción, garantizando la seguridad de todo el proceso.</p>
 </div>
 
-Para habilitar este tipo de transacción en el conector, el gestor de la tienda deberá solicitar al adquirente la habilitación para transaccionar pagos recurrentes.<a href="https://help.vtex.com/es/tutorial/pci-gateway-visao-geral/"> Vea nuestro artículo sobre cómo configurar un gateway de pago en su tienda</a>.
+Para habilitar este tipo de transacción en el conector, el gestor de la tienda deberá solicitar al adquirente la habilitación para transaccionar pagos recurrentes. Acceda a nuestro artículo sobre [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
 
 ## 3. Crear un plan de suscripción
 
@@ -94,12 +94,12 @@ Vea los recursos relacionados con el módulo de Suscripciones en la siguiente ta
 
 Para configurar los perfiles de acceso de Suscripciones, realice las siguientes instrucciones:
 
-1. En el módulo **Configuraciones de la cuenta**, acceda a la pestaña **Perfiles de acceso**.
-2. Haga clic en el botón `Nuevo perfil`.  
-3. Complete el **Nombre del perfil**.
-4. En **Productos y recursos**, seleccione **OMS**.
-5. Marque las casillas de los **Recursos de suscripción** que desea agregar.
-6. Haga clic en `Guardar`. 
+1. En el módulo **Configuración de la cuenta**, acceda a **Roles de usuario**.
+2. Haga clic en el botón `Nuevo rol`.
+3. Complete el **Nombre del rol**.
+4. En **Productos y recursos**, seleccione `Subscriptions`.
+5. Marque las casillas de los recursos que desea agregar.
+6. Haga clic en `Guardar`.
 
 Una vez que Suscripciones esté configurada en su tienda, acceda a nuestro artículo para verificar cómo [gestionar suscripciones](https://help.vtex.com/es/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x).
 
diff --git a/docs/tutorials/es/how-to-configure-the-anti-fraud.md b/docs/tutorials/es/how-to-configure-the-anti-fraud.md
index 0c90b97f9..b97712427 100644
--- a/docs/tutorials/es/how-to-configure-the-anti-fraud.md
+++ b/docs/tutorials/es/how-to-configure-the-anti-fraud.md
@@ -3,8 +3,8 @@ title: 'Configurar el antifraude'
 id: tutorials_446
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:02.912Z
-updatedAt: 2023-03-29T00:57:28.767Z
-publishedAt: 2023-03-29T00:57:28.767Z
+updatedAt: 2024-03-13T12:04:32.047Z
+publishedAt: 2024-03-13T12:04:32.047Z
 firstPublishedAt: 2017-04-27T23:03:25.730Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,23 @@ legacySlug: como-configurar-antifraude
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Antifraude es un sistema exterior que identifica fraudes y aumenta la seguridad para las compras realizadas. En VTEX, usted puede elegir algunas opciones de antifraude para su tienda. Y configurarlos es muy simple.
+Antifraude es un sistema externo que identifica el fraude y permite aumentar la seguridad en las transacciones de pago realizadas durante las compras online. En VTEX, usted puede elegir algunas opciones de proveedores antifraude para utilizar en su tienda.
 
-## Cómo configurar
+Para configurar un proveedor antifraude, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. Acceda a la pestaña **Afiliaciones**.
-3. Haga clic en “+”.
-4. Haga clic sobre la antifraude que desea configurar.
-5. Llene los campos del formulario con los datos indicados por la antifraude (EntityCode).
-6. Haga clic en **Guardar**.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el proveedor antifraude deseado en la barra de búsqueda y haga clic en su nombre.
+4. Rellena los campos del formulario con los datos indicados por el proveedor antifraude.
+5. Haga clic en `Guardar`.
 
-Después de la configuración en Afiliación de Gateways, es necesario entrar en las condiciones de pago y asociar la Antifraude en cada uno de ellos.
+Después de habilitar el proveedor antifraude, debe asociarlo con una o más condiciones de pago. Para realizar esta operación, siga los pasos a continuación:
 
-1. Acceda a la pestaña __Planes de Pago__.
-2. Haga clic sobre a condición deseada o [cree la condición de pago](/es/tutorial/condiciones-de-pago);
-3. Seleccione la opción “Usar antifraude”.
-4. Seleccione cuál antifraude desea utilizar.
-5. Haga clic en **Guardar**.
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en el método de pago deseado.
+4. Complete el campo __Nombre de la condición__ con un nombre de su elección para identificación.
+5. Active la condición en el campo __Status__.
+6. En __Procesar con proveedor__ seleccione el proveedor de pago deseado.
+7. En __Utilizar antifraude__, seleccione el proveedor antifraude previamente habilitado, si está disponible para usar con este método de pago.
+8. Haga clic en "Guardar".
diff --git a/docs/tutorials/es/how-to-configure-the-pagseguro-without-redirect-option-transparent.md b/docs/tutorials/es/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
index c50fcbed9..06866a6f3 100644
--- a/docs/tutorials/es/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
+++ b/docs/tutorials/es/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar el PagSeguro sin redirect (transparente)'
 id: tutorials_449
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T22:04:37.656Z
-updatedAt: 2023-03-29T01:24:00.848Z
-publishedAt: 2023-03-29T01:24:00.848Z
+updatedAt: 2024-07-24T12:05:55.438Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:25.912Z
 contentType: tutorial
 productTeam: Financial
@@ -19,24 +19,19 @@ _Las configuraciones documentadas en este artículo se realizan en un ambiente f
 
 Si usted tiene una cuenta en PagSeguro y ya utiliza la opción con redirect en su tienda, es posible habilitar la opción sin el redirect en el Pagos. Esto significa que, al momento de finalizar la compra, el cliente ya no saldrá de su sitio para realizar el pago, aunque haga la transacción por PagSeguro. Esto ocurrirá de forma transparente.
 
-Esta opción está disponible como un nuevo conector en la opción **Afiliaciones de Gateways**, como se muestra en la siguiente imagen.
-
 Atención: Si el administrador de la tienda tiene garantía de chargeback, es necesario configurar el antifraude de PagSeguro. Este proceso exige una etapa de configuración en Google Tag Manager. Para más detalles de cómo realizar esta acción, vea el [artículo en la página de PagSeguro](https://dev.pagseguro.uol.com.br/v2/docs/configurando-device-fingerprint "artigo na página do PagSeguro").
 
 Para habilitarla, verifique el siguiente procedimiento:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. Haga clic en __Afiliaciones de Gateways__ y luego en __"+"__.
-3. Haga clic en la afiliación __PagSeguroV2__.
-4. Guarde la __afiliación__.
-5. Vuelva al __panel__ de afiliaciones.
-6. Seleccione la afiliación __PagSeguroV2__ recién creada.
-7. Haga clic en __Autorizar__.
-8. Seleccione y envíe la __regla deseada__.
-9. Haga clic en __Entre con su e-mail y contraseña__.
-10. Entre en la __cuenta__ con su e-mail y contraseña PagSeguro
-11. Autorice la __aplicación__.
-12. Haga clic en __Guardar__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagSeguroV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Haga clic en __Authorize via OAuth__.
+5. Seleccione y envíe la __regla deseada__.
+6. Haga clic en __Entre con su e-mail y contraseña__.
+7. Entre en la __cuenta__ con su e-mail y contraseña PagSeguro.
+8. Autorice la __aplicación__.
+9. Haga clic en `Guardar`.
 
 ## Configurar condición de pago
 
diff --git a/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md b/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md
index 4175c2ee2..57843fe60 100644
--- a/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md
+++ b/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md
@@ -38,7 +38,7 @@ Para desarrollar una versión mobile con un nuevo WebSite, debe seguir los sigui
 
 Storefront > Layout > Carpeta de CMS > Sites and Channels > New Website
 
-![cms-new-website](https://images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
+![cms-new-website](//images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
 
 3. Crear estructura de carpetas del WebSite Mobile: en este paso será necesario crear las carpetas estándar del sistema que se usarán en la versión mobile (búsqueda, departamento, categoría, marca, producto, etc.)
 
diff --git a/docs/tutorials/es/how-to-create-a-financial-access-profile.md b/docs/tutorials/es/how-to-create-a-financial-access-profile.md
index 8507eebf6..954719d89 100644
--- a/docs/tutorials/es/how-to-create-a-financial-access-profile.md
+++ b/docs/tutorials/es/how-to-create-a-financial-access-profile.md
@@ -31,7 +31,7 @@ Para crear un rol financiero:
 6. (Opcional) Antes de guardar, usted puede **Agregar usuarios a este rol**.
 7. Haga clic en **Guardar**.
 
-![gif perfildeacessoES](https://images.ctfassets.net/alneenqid6w5/3JYWgBIlkkg4VFG1AgFHoc/9d68fb02cf08d64dda981ea3d1ff3935/gif_perfildeacessoES.gif)
+![gif perfildeacessoES](//images.ctfassets.net/alneenqid6w5/3JYWgBIlkkg4VFG1AgFHoc/9d68fb02cf08d64dda981ea3d1ff3935/gif_perfildeacessoES.gif)
 
 El rol financiero ahora está creado y está disponible para asociarlo con usuarios existentes.
 
@@ -44,10 +44,10 @@ Es posible asociar un usuario con el rol Finance ya existente:
 3. Haga clic en la pestaña **Usuarios**.
 4. Seleccione el usuario que desea asociar.
 5. Ahora, escoja el **rol Financiero**.
-6. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> al lado del rol seleccionado para agregarlo.
+6. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> al lado del rol seleccionado para agregarlo.
 7. Para finalizar, haga clic en **Guardar**.
 
-![gif usuárioES](https://images.ctfassets.net/alneenqid6w5/gRA4oVVbG7Z8ksFX4QiWm/f097214bc3c314a36dc384efcbc51980/gif_usu__rioES.gif)
+![gif usuárioES](//images.ctfassets.net/alneenqid6w5/gRA4oVVbG7Z8ksFX4QiWm/f097214bc3c314a36dc384efcbc51980/gif_usu__rioES.gif)
 
 El usuario seleccionado ahora está asociado con el rol Financiero y podrá acceder a facturas, información sobre contratos, cobros y otra información financiera.
 
diff --git a/docs/tutorials/es/how-to-create-a-page-template.md b/docs/tutorials/es/how-to-create-a-page-template.md
index c88aa5caf..b3ed441ce 100644
--- a/docs/tutorials/es/how-to-create-a-page-template.md
+++ b/docs/tutorials/es/how-to-create-a-page-template.md
@@ -3,15 +3,15 @@ title: 'Crear o editar un template de página'
 id: frequentlyAskedQuestions_1850
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:59.664Z
-updatedAt: 2023-03-27T14:56:34.174Z
-publishedAt: 2023-03-27T14:56:34.174Z
+updatedAt: 2023-11-01T20:27:09.646Z
+publishedAt: 2023-11-01T20:27:09.646Z
 firstPublishedAt: 2019-01-24T22:03:09.865Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
 author: authors_84
 slug: como-crear-un-template-de-pagina
 locale: es
-legacySlug: como-crear-un-template-de-pagina
+legacySlug: crear-un-template-de-pagina
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
@@ -46,7 +46,7 @@ Vea a continuación el procedimiento:
 <li><code>app</code></li>
 </ul></p>
 </div>
-6. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+6. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. En la esquina superior derecha, haga clic en el botón  __Save Template__.
 
 Para editar un template ya existente, el proceso es casi idéntico.
diff --git a/docs/tutorials/es/how-to-create-a-product.md b/docs/tutorials/es/how-to-create-a-product.md
index 2293b7d3b..1a63b52f8 100644
--- a/docs/tutorials/es/how-to-create-a-product.md
+++ b/docs/tutorials/es/how-to-create-a-product.md
@@ -165,7 +165,7 @@ Después de llevar a cabo este procedimiento, las especificaciones creadas y sus
 
 Además, a partir de las opciones creadas, la lista de SKU posibles se genera automáticamente y se muestra en la sección **[Variaciones](#variaciones)**.
 
-![variations ES](https://images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/74c9b1a069394f60e647acd42130f24c/variations_ES.png)
+![variations ES](//images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/74c9b1a069394f60e647acd42130f24c/variations_ES.png)
 
 ## Especificaciones
 
@@ -219,7 +219,7 @@ Para editar un gran número de variaciones a la vez, puede utilizar la funcional
 
 1. Haga clic en el botón `Edición en masa` para abrir la plantilla de edición de variaciones.
 2. Para editar la información en la plantilla, debe hacer doble clic en el campo que desee modificar.
-![edicao-massa-SKU-ES](https://images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/def837067f47c559d8199af8c9de8169/image.png)
+![edicao-massa-SKU-ES](//images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/def837067f47c559d8199af8c9de8169/image.png)
 
 En la plantilla puede editar la siguiente información:
 - **Activo:** indica si la variación está activa o no.
@@ -235,7 +235,7 @@ En la plantilla puede editar la siguiente información:
 Para filtrar las columnas mostradas en la plantilla, haga clic en `Filtrar columnas` y seleccione las columnas que desee ocultar.
 
 Puede replicar la información de una celda a otras filas y columnas. Para ello, haga clic en el cuadrado azul en la esquina inferior derecha de la celda y arrástrelo a las celdas en las que desee replicar automáticamente el valor, como se muestra en la imagen a continuación.
-![Formatacao-celula-ES](https://images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/bc801e55c612036ff1c0481bb1cc3bc3/Formatacao-celula-ES.gif)
+![Formatacao-celula-ES](//images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/bc801e55c612036ff1c0481bb1cc3bc3/Formatacao-celula-ES.gif)
 3. Después de editar, haga clic en `Aplicar` para guardar los cambios.
 
 ## SEO
diff --git a/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
index a2ead9ef7..642d3aca2 100644
--- a/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
@@ -21,7 +21,7 @@ Para que una promoción del tipo regular sea aplicada por un número limitado de
 <p>Los pedidos con status <code>Iniciando cancelación</code> o <code>Cancelado</code> no cuentan para el límite establecido.</p>
 </div>
 
-![Promocion con limite de uso](https://images.ctfassets.net/alneenqid6w5/6RuP1uG4Cc8MWm2OikwimK/9a4d5dcdf67edbd058cf1dae705fa1e9/Promocion_con_limite_de_uso.png)
+![Promocion con limite de uso](//images.ctfassets.net/alneenqid6w5/6RuP1uG4Cc8MWm2OikwimK/9a4d5dcdf67edbd058cf1dae705fa1e9/Promocion_con_limite_de_uso.png)
 
 También es posible configurar el límite por cliente, en vez de límite por promoción. Para ello, basta hacer la configuración arriba y hacer clic en la opción **Habilitar límite de uso por cliente**.
 
diff --git a/docs/tutorials/es/how-to-create-a-store-name.md b/docs/tutorials/es/how-to-create-a-store-name.md
index 0059b89f9..877348425 100644
--- a/docs/tutorials/es/how-to-create-a-store-name.md
+++ b/docs/tutorials/es/how-to-create-a-store-name.md
@@ -23,7 +23,7 @@ Para crear o editar un [nombre de la tienda](https://help.vtex.com/es/tutorial/o
 4. En el dashboard de la tienda, verás los nombres de la tienda que ya hay en tu cuenta. Puedes editar la información de cada tienda, o crear un nuevo nombre de la tienda, al hacer clic en el botón **Configurar esta tienda**.
 5. Para saber cómo configurar el dominio de tus tiendas, consulta el artículo [Cambiar el dominio de la tienda](https://help.vtex.com/es/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
-![Configuracion de nombre de tienda](https://images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/95ef9845c325ed8b55632be5ac1c3bab/ES.PNG)
+![Configuracion de nombre de tienda](//images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/95ef9845c325ed8b55632be5ac1c3bab/ES.PNG)
 
 Para saber cómo configurar el dominio de tus tiendas, consulta el artículo [Cambiar el dominio de la tienda](https://help.vtex.com/es/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
diff --git a/docs/tutorials/es/how-to-create-a-subscription-attachment.md b/docs/tutorials/es/how-to-create-a-subscription-attachment.md
index 34e5cc0dd..38220709f 100644
--- a/docs/tutorials/es/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/es/how-to-create-a-subscription-attachment.md
@@ -71,11 +71,11 @@ Siga las instrucciones a continuación para configurar la frecuencia y fechas de
 
         * **Semanalmente:** los valores posibles para completar este campo son = `0`, `1`, `2`, `3`, `4`, `5` y `6`, que equivalen a los días de la semana. Considere `0` = domingo, `1` = lunes, `2` = martes, y así sucesivamente hasta `6` = sábado. Separe los valores con `,`, según se muestra a continuación.
 
-        ![ES Assinatura Exemplo Valores week](https://images.ctfassets.net/alneenqid6w5/1KDaD3iRFBwt7xrikkB8V9/ecfe9cb9da8bb798d410f5d709c8b04d/ES_Assinatura_Exemplo_Valores_week.png)
+        ![ES Assinatura Exemplo Valores week](//images.ctfassets.net/alneenqid6w5/1KDaD3iRFBwt7xrikkB8V9/ecfe9cb9da8bb798d410f5d709c8b04d/ES_Assinatura_Exemplo_Valores_week.png)
 
         * **Mensualmente:** los valores posibles para rellenar este campo en el _checkout_ son = `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, (...) hasta `28`, que equivalen a los días del mes. Considere `1` = primer día del mes, `2` = segundo día del mes, `3` = tercer día del mes, y así sucesivamente hasta `28` = vigésimo octavo día del mes. Separe los valores con `,`, según se muestra a continuación.
 
-        ![ES Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/5tbntKlv4WeYUXQtM8EMGz/84d58a31d1b449fdbdfad60fae5dec0d/ES_Assinatura_Exemplo_Valores_month.png)
+        ![ES Assinatura Exemplo Valores month](//images.ctfassets.net/alneenqid6w5/5tbntKlv4WeYUXQtM8EMGz/84d58a31d1b449fdbdfad60fae5dec0d/ES_Assinatura_Exemplo_Valores_month.png)
 
 <div class="alert alert-info">
   <p>Si no se introduce ningún valor en el campo <strong>Valores permitidos</strong>, la fecha del ciclo de suscripción será el mismo día de la semana (si la frecuencia es semanal) o día del mes (si la frecuencia es mensual) del pedido original.</p>
diff --git a/docs/tutorials/es/how-to-create-conditional-prices.md b/docs/tutorials/es/how-to-create-conditional-prices.md
index 736d3ac21..781a8113c 100644
--- a/docs/tutorials/es/how-to-create-conditional-prices.md
+++ b/docs/tutorials/es/how-to-create-conditional-prices.md
@@ -33,4 +33,4 @@ El siguiente es un paso a paso de cómo usar estos precios condicionales:
 6. Usted puede definir un pequeño mensaje, llamado *Teaser*, para promover esa condición a su cliente. (Para entender mejor, vea [Teasers - En breve])
 7. Guarde.
 
-![conditionalPrice](https://images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
+![conditionalPrice](//images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
diff --git a/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md b/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md
new file mode 100644
index 000000000..80d2512a6
--- /dev/null
+++ b/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md
@@ -0,0 +1,87 @@
+---
+title: 'Ajustes en la interfaz personalizada del checkout en el Admin '
+id: 548aDBJciQu97Vh0BhEiWx
+status: PUBLISHED
+createdAt: 2024-01-04T13:27:04.734Z
+updatedAt: 2024-01-04T18:28:45.989Z
+publishedAt: 2024-01-04T18:28:45.989Z
+firstPublishedAt: 2024-01-04T18:28:45.989Z
+contentType: tutorial
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: ajustes-en-la-interfaz-personalizada-del-checkout-en-el-admin
+locale: es
+legacySlug: ajustes-en-la-interfaz-personalizada-del-checkout-en-el-admin
+subcategory: 6XAvmMxp7yyY06ewYMuggs
+---
+
+Las personalizaciones del checkout descritas en este artículo se llevan a cabo utilizando la aplicación Checkout UI Custom. Antes de iniciar los ajustes debes comprobar que la aplicación está instalada en la tienda, o instalarla como se indica en el artículo [Checkout UI Custom](https://developers.vtex.com/docs/apps/vtex.checkout-ui-custom).
+
+## Personalizar el checkout
+
+En el VTEX Admin, ve a **Configuración de la tienda > Storefront > Interfaz personalizada del checkout**, o ingresa **Interfaz personalizada del checkout** en la barra de búsqueda de la parte superior de la página. 
+
+Se puede acceder a las funcionalidades de personalización de la aplicación a través de las siguientes pestañas del Admin:
+
+* [Interfaz](#interfaz)
+* [Colores](#colores)
+* [JavaScript](#javascript)
+* [CSS](#css)
+* [Historial](#historial)
+
+## Interfaz
+
+En esta pestaña puedes configurar los siguientes ajustes:
+
+1. **Opciones de pago como acordeón:** al activar el botón, las formas de pago se muestran en cascada (acordeón) si hay hasta cinco medios de pago. Cuando está desactivado, los medios de pago se muestran en pestañas laterales.
+
+2. **Fecha de envío simplificada:** al activar el botón, podrás ver la estimación de envío en formato de fecha (por ejemplo, "lunes 18/09/23").  Cuando la opción está desactivada, los datos proporcionados se limitarán a una estimación del plazo en días por ejemplo, en hasta 5 días laborables.
+
+3. **Mostrar el precio unitario del ítem:** al activar el botón, el usuario verá el valor unitario de cada producto y el valor total sumado, si se agregan al carrito dos o más unidades. Cuando la opción está desactivada, solo se puede ver el valor unitario de cada producto.
+
+4. **Mostrar campo 'Notas':** al activar este botón se muestra un campo para agregar comentarios adicionales al pedido, como un mensaje de felicidades si el producto es un regalo o alguna observación relativa a la entrega del producto. Cuando está desactivado, este campo de comentarios no se muestra.
+
+5. **Ocultar el paso de email:** al activar el botón, se desactiva la opción del relleno automático de datos mediante la inserción del email. Cuando se desactiva, los datos de contacto deben ingresarse manualmente.
+
+6. **Formulario de dirección de Google:** es una integración del formulario de direcciones con Google (en fase beta). Cuando el botón está activado se proporcionan sugerencias para autocompletar la dirección; al seleccionarlas, los campos de dirección se rellenarán automáticamente.
+
+7. **Tamaño del texto:** esta configuración permite cambiar el tamaño de la fuente (en píxeles) en el checkout.
+
+8. **Radio del borde:** esta configuración permite personalizar el formato de redondeo del borde externo (en píxeles) en el checkout.
+
+9. **Radio del borde del botón:** esta configuración permite personalizar el formato del redondeo del borde de los botones (en píxeles) en el checkout.
+
+10. **Altura de los campos de texto:** permite personalizar la altura (en píxeles) de los campos de texto en el checkout.
+
+11. **Anchura máxima del contenido:** permite configurar la anchura máxima (en píxeles) de la información mostrada en el checkout.
+
+12. **Borde del contenedor:** permite configurar el [tipo de borde](https://www.w3schools.com/css/css_border.asp) de las secciones del checkout.
+
+13. **Familia de fuente:** permite configurar los tipos de fuentes utilizadas en el checkout.
+
+## Colores
+
+La pestaña Colores facilita la personalización de los colores del checkout de tu tienda, lo que incluye la modificación de los colores del fondo, de los botones o del texto, por ejemplo. Esta estandarización garantiza una armonía visual consistente.
+
+![Colores](//images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/a6ded356e1627c5cc91465aaca09c047/Colores_-_ES.png)
+
+## JavaScript
+
+La pestaña JavaScript agrega un nivel adicional de personalización de la interfaz al posibilitar la inserción de scripts.
+
+![Java - ES](//images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/828e33a5b4a8a02130e3c63de6588dfe/Java_-_ES.png)
+
+## CSS
+
+La pestaña CSS permite ajustar el aspecto visual de la tienda mediante la inclusión de código CSS.
+
+![CSS - ES](//images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/415c6d4c0d23401f7293a94b585da15c/CSS_-_ES.png)
+
+## Historial
+
+Permite ver y restaurar las personalizaciones creadas y publicadas anteriormente.
+
+![Histórico - ES](//images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/5f06f5a14093fa8f112e0fc08b3f686a/Hist_rico_-_ES.png)
+
+Para asegurarte de que la configuración se aplique correctamente, solo tienes que configurar los ajustes necesarios y hacer clic en el botón `Publicar`.
+
diff --git a/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
index 790d81879..61784f456 100644
--- a/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
@@ -23,7 +23,7 @@ Puedes cambiar el campo **textLink** de un producto existente en cualquier momen
 
 Consulta la sección [Reglas de llenado](#reglas-de-llenado) para conocer las restricciones de este campo.
 
-![textlink.es](https://images.ctfassets.net/alneenqid6w5/7Fn3c82EFti8PUc2qME3Xa/74abc336ae433344083479d28014696d/textlink.es.png)
+![textlink.es](//images.ctfassets.net/alneenqid6w5/7Fn3c82EFti8PUc2qME3Xa/74abc336ae433344083479d28014696d/textlink.es.png)
 
 <div class="alert alert-info">
   <p>También puedes cambiar la URL de un producto utilizando la<a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview"> API del Catálogo</a>. En este caso, el campo a modificar es <code>LinkId</code>. Consulta el artículo<a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product"> Update product</a> para obtener más información.</p>
diff --git a/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md b/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md
index bb5695a60..a7b27f1a6 100644
--- a/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md
+++ b/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md
@@ -19,4 +19,4 @@ Si usted necesita realizar un rollback de su aplicación, ejecute el comando `vt
 
 Si percibe enseguida que será necesario deshacer el rollback, usted podrá realizar el comando `vtex undeprecate`.
 
-![image (2)](https://images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
+![image (2)](//images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
diff --git a/docs/tutorials/es/how-to-disable-a-transactional-email.md b/docs/tutorials/es/how-to-disable-a-transactional-email.md
index 9be7636f4..a1d71603a 100644
--- a/docs/tutorials/es/how-to-disable-a-transactional-email.md
+++ b/docs/tutorials/es/how-to-disable-a-transactional-email.md
@@ -28,7 +28,7 @@ Se muestra a continuación:
 3. Busque __Payment Pending__ en el cuadro de búsqueda.
 4. Desactive la opción __"Activar envío de e-mail"__.
 
-  ![Message Center - Desativar - ES](https://images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d000be57bdf906c957380992d497ddb6/dlSCQPRLKf46SnYGl7X9a_ES_Payment_Pending.jpg)
+  ![Message Center - Desativar - ES](//images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d000be57bdf906c957380992d497ddb6/dlSCQPRLKf46SnYGl7X9a_ES_Payment_Pending.jpg)
 
 5. Haga clic en __Guardar__.
 
diff --git a/docs/tutorials/es/how-to-download-the-vtex-invoices.md b/docs/tutorials/es/how-to-download-the-vtex-invoices.md
index b8726923c..c0afd3919 100644
--- a/docs/tutorials/es/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/es/how-to-download-the-vtex-invoices.md
@@ -46,7 +46,7 @@ Para descargar su factura, realice los siguientes pasos:
 
 Una vez hecho esto, su factura estará disponible en otra pestaña.
 
-![baixar faturas es](https://images.ctfassets.net/alneenqid6w5/5sIBQUq8c2OKi0PHOb7qhs/8554b546c31d52e5f1a897a99c9341eb/baixar_faturas_es.gif)
+![baixar faturas es](//images.ctfassets.net/alneenqid6w5/5sIBQUq8c2OKi0PHOb7qhs/8554b546c31d52e5f1a897a99c9341eb/baixar_faturas_es.gif)
 
 ## Brasil 
 
@@ -66,7 +66,7 @@ Para descargar su boleto, realice los siguientes pasos:
 
 <div class="alert alert-info">En Brasil, una factura púrpura puede indicar que está atrasada pero se ha generado un nuevo boleto para una fecha cercana. En este caso, la factura permanecerá atrasada hasta que se realice el pago. Si no se paga el nuevo boleto, la factura se pondrá en rojo.</div>
 
-![baixar boletos es](https://images.ctfassets.net/alneenqid6w5/6JSRhGjBxWs4KDpVm9P5LL/57eb4cb973d27d600710cd8a91f7f4a6/baixar_boletos_es.gif)
+![baixar boletos es](//images.ctfassets.net/alneenqid6w5/6JSRhGjBxWs4KDpVm9P5LL/57eb4cb973d27d600710cd8a91f7f4a6/baixar_boletos_es.gif)
 
 ### Descargar la Nota Fiscal
 
@@ -83,6 +83,6 @@ De esta forma, la Nota Fiscal se abrirá en otra pestaña de su navegador. Haga
 1. En Destino, seleccione la opción **Guardar en PDF**.
 2. Para finalizar, haga clic en **Guardar**.
 
-![baixar notafiscal es](https://images.ctfassets.net/alneenqid6w5/y5FNSwSwYBOrMvX6mvHeO/c1f091d98df99caa716e3e2ad352b230/baixar_notafiscal_es.gif)
+![baixar notafiscal es](//images.ctfassets.net/alneenqid6w5/y5FNSwSwYBOrMvX6mvHeO/c1f091d98df99caa716e3e2ad352b230/baixar_notafiscal_es.gif)
 
 Si tiene dudas sobre el valor de la factura, lea el artículo [comprenda el valor de los ingresos aprobados](https://help.vtex.com/es/tutorial/como-acessar-o-valor-da-receita-aprovada--tutorials_4322) para entender el valor que se cobró.
diff --git a/docs/tutorials/es/how-to-identify-a-page-template.md b/docs/tutorials/es/how-to-identify-a-page-template.md
index 3b4e6b1c6..0a2a68656 100644
--- a/docs/tutorials/es/how-to-identify-a-page-template.md
+++ b/docs/tutorials/es/how-to-identify-a-page-template.md
@@ -19,7 +19,7 @@ Esa duda es muy común entre los comerciantes VTEX. Como el CMS es un módulo an
 
 Antes es necesario explicar rápidamente la estructura del CMS Layout, que queda en `{AccountName}.myvtex.com/admin/a`
 
-![cms_newadmin ES](https://images.ctfassets.net/alneenqid6w5/3t6uV7zLoAmIyYWSckwgOK/bbbad86f93506d49757da4aef80ce6d6/CMS__newadmin_ES.png)
+![cms_newadmin ES](//images.ctfassets.net/alneenqid6w5/3t6uV7zLoAmIyYWSckwgOK/bbbad86f93506d49757da4aef80ce6d6/CMS__newadmin_ES.png)
 
 La principal función del CMS Layout es permitir la administración del layout de su tienda. En él se crearán los Directorios y Templates que darán vida a su e-commerce.
 
@@ -29,7 +29,7 @@ VTEX usa el mismo principio. El directorio (carpeta) es donde debe guardarse tod
 
 Podemos crear innúmeros templates pero debemos especificar en el directorio qué template se exhibirá. Usando la página de __Account__ como ejemplo:
 
-![cms-template-pagina ES](https://images.ctfassets.net/alneenqid6w5/3AGqfnX5agco4McoGWOKIW/591aa19d419d552c23c9652cf87b8048/account_CMS_ES.png) 
+![cms-template-pagina ES](//images.ctfassets.net/alneenqid6w5/3AGqfnX5agco4McoGWOKIW/591aa19d419d552c23c9652cf87b8048/account_CMS_ES.png) 
 
 Storefront > Layout > Carpeta CMS > Sites and channels > Account Nombre > Carpeta (/) > Account *(como en el ejemplo)* > Haga clic en el link que presente la flecha roja de "ok".
 
@@ -41,13 +41,13 @@ Para dar flexibilidad es posible aún incluir subtemplates e innúmeros otros re
 
 Ahora un ejemplo real. Quiero identificar qué página es ésta en la que estoy navegando:
 
-![pagina-loja ES](https://images.ctfassets.net/alneenqid6w5/54CZB8Gt1CaY6W0MKG0u0S/df59e087977c87d972f78b4a689971ee/exemplo_loja_em_ES.png)
+![pagina-loja ES](//images.ctfassets.net/alneenqid6w5/54CZB8Gt1CaY6W0MKG0u0S/df59e087977c87d972f78b4a689971ee/exemplo_loja_em_ES.png)
 
 El propio dominio muchas veces ya me ayuda a identificar, pero algunas tiendas pueden customizar esto, lo que puede dificultar el trabajo. En el caso, tengo duda sobre si es una página de __Departamento__ o __Categoría__, tal vez pueda incluso ser una customización de anaquel.
 
 El mejor camino es por el cotejo en el Código Fuente de la página (ctrl + U). Tiendas VTEX van a tener un indicativo de a qué directorio pertenece la página.
 
-![exemplo-codigo-template-loja ES](https://images.ctfassets.net/alneenqid6w5/7ciwzN1BLOsg0KU46SaWQW/b7dd7f1a16cd6aedf0bb48dc74f45d40/exemplo_loja_em_espanhol_departamento.png)
+![exemplo-codigo-template-loja ES](//images.ctfassets.net/alneenqid6w5/7ciwzN1BLOsg0KU46SaWQW/b7dd7f1a16cd6aedf0bb48dc74f45d40/exemplo_loja_em_espanhol_departamento.png)
 
 En el ejemplo anterior: `<!-- CommerceContext.Current.VirtualFolder.Name: @Departamento@ -->`
 Ahora que sabemos que es una página de categoría, necesitamos identificar qué template está activo para la Categoría. Para ello, basta repetir el proceso aplicado en el ejemplo anterior.
diff --git a/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md b/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md
index 4be171335..67ccd9c7b 100644
--- a/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md
+++ b/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md
@@ -25,7 +25,7 @@ Para eso, siga los siguientes pasos:
 
 1. Para deshabilitar el JavaScript de la página basta colocar el `/tools.html` al final de la URL. Ej: {AccountName}.myvtex.com/tools.html
 2. Haga clic en __Disable__ en la pestaña __Client JavaScript is__.
-![javascript-disable ](https://images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
+![javascript-disable ](//images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
 
 3. Después retirar el `/tools.html` da URL y actualizar la página.
 
diff --git a/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
index cc49a01ab..06ac35e0b 100644
--- a/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
@@ -28,9 +28,9 @@ Puedes hacer un pedido de prueba en la tienda y, luego, verificar en **Gestión
 
 Ejemplo: imagina un pedido en el que se aplicó el envío gratis, pero no sabes por qué. Al hacer clic en un pedido en **Gestión de pedidos**, encontrarás el nombre de la promoción registrada en la sección **Ventas y Marketing** o **Promociones y asociaciones**.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/3a84036866c5ed37f964e79a36f8bcd4/detalhes-oms-es.png" alt="detalles-del-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/3a84036866c5ed37f964e79a36f8bcd4/detalhes-oms-es.png" alt="detalles-del-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/35b752b315cc8578199647fe535677fa/detalhes-neworders-en__1_.png" alt="detalles-del-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido (Beta)</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/35b752b315cc8578199647fe535677fa/detalhes-neworders-en__1_.png" alt="detalles-del-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido (Beta)</em></figcaption></figure>
 
 Si no hay ninguna promoción en la lista, eso significa que el envío gratis no se debe a una promoción, es decir, que el cálculo del envío en el módulo **Stock y entrega** tuvo como resultado cero. En ese caso, será necesario usar el **Simulador de envío** para comprender por qué razón el envío tiene un valor de cero.
 
@@ -40,7 +40,7 @@ En el carrito, puedes pasar el mouse sobre el ícono de interrogación que está
 
 Sin embargo, si se aplicó más de una promoción, aparecerá solo la sumatoria de todos los descuentos, lo cual dificultará el análisis del escenario.
 
-![example-cart](https://images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/8d5f5572c67f308480e9e4b1f65dc9e7/image6.png)
+![example-cart](//images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/8d5f5572c67f308480e9e4b1f65dc9e7/image6.png)
 
 ## orderForm
 
diff --git a/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
index 2c334383b..2278cb786 100644
--- a/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
@@ -28,8 +28,8 @@ Un archivo XLS de <strong>10 MB</strong> permite el registro de, aproximadamente
 ## Cómo subir la planilla
 1. En el menú lateral, haga clic en __Inventario y envío__, en la sección __Pedidos__.
 2. En las opciones que se abren, haga clic en __Puntos de recogida__.
-3. Haga clic en __Subir un XLS__, en la esquina superior derecha de la página. ![Subir XLS (ES)](https://images.ctfassets.net/alneenqid6w5/33W20ReDnWc4U4gIgeaOUW/b2eada442c781b9b21397aeb60deb127/Subir_XLS__ES_.png)
-4. Un modal va a surgir, permitiendo que usted envíe su archivo (con extensión `.xls`) o baje la [planilla de ejemplo](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Recuerde que esta planilla viene con valores de ejemplo rellenados, que deben ser borrados y reemplazados por los datos de sus propios puntos de recogida. ![modal (ES)](https://images.ctfassets.net/alneenqid6w5/2CxrD2w27CYIAwqYGwUEqu/ca5cebd0c3c7bc457f4f93fbee98178d/modal__ES_.png)
+3. Haga clic en __Subir un XLS__, en la esquina superior derecha de la página. ![Subir XLS (ES)](//images.ctfassets.net/alneenqid6w5/33W20ReDnWc4U4gIgeaOUW/b2eada442c781b9b21397aeb60deb127/Subir_XLS__ES_.png)
+4. Un modal va a surgir, permitiendo que usted envíe su archivo (con extensión `.xls`) o baje la [planilla de ejemplo](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Recuerde que esta planilla viene con valores de ejemplo rellenados, que deben ser borrados y reemplazados por los datos de sus propios puntos de recogida. ![modal (ES)](//images.ctfassets.net/alneenqid6w5/2CxrD2w27CYIAwqYGwUEqu/ca5cebd0c3c7bc457f4f93fbee98178d/modal__ES_.png)
 5. Con todo hecho correctamente, los nuevos puntos de recogida estarán configurados y disponibles para sus clientes.
 
 
diff --git a/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
index e2627b081..723d45f9b 100644
--- a/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -27,30 +27,30 @@ Realizadas las debidas definiciones, se hace el vínculo de la colección con la
 
 En el ejemplo abajo, vamos a definir la vitrina presentada en la Home. Por lo tanto, seleccione **Settings**, luego **add object**, como en la siguiente imagen.
 
-![coleção2](https://images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
+![coleção2](//images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
 
 Este comando abrirá **Visual Controls**, que corresponden al escaparate en el que desea mostrar la colección. Agregue una _Collection_, pero asegúrese de establecer un nombre para ella.
 
-![coleção3](https://images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
+![coleção3](//images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
 
-![coleção4](https://images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
+![coleção4](//images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
 
 Acuérdese de grabar las configuraciones para que sea posible editar el control creado!
 
-![coleção5](https://images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
+![coleção5](//images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
 
-![coleção6](https://images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
+![coleção6](//images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
 
 Al editar el control es necesario agregar sus contenidos, que representan cada conjunto de ítems que se exhibirán.
 Son ellos:
 _Layout_: seleccione la plantilla de estante utilizada en la muestra.
 _Number of Columns, Number of Items, Show Unavailable_ y _Ramdom ad Paged_: Defina el diseño, la cantidad y los criterios para mostrar los elementos.
 
-![coleção7](https://images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
+![coleção7](//images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
 
 Recuerde guardar antes de buscar o cambiar páginas.
 El siguiente paso es agregar el contenido seleccionando **Add Content**.
-![coleção8](https://images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
+![coleção8](//images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
 
 Es posible definir cada contenido usando colecciones o resultados de búsqueda, usando parámetros de búsqueda (más detalles [aquí](/es/tutorial/parametros-de-busqueda "aquí"))
 
@@ -60,7 +60,7 @@ _QueryString_: los parámetros ingresados en este campo definen el resultado de
 
 En el campo **Product Cluster (Collection)**, debe seleccionar la colección que se mostrará completando el siguiente paso:
 
-![coleção10](https://images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
+![coleção10](//images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
 
 Los contenidos a rellenar en la parte **Condición de visualización**:
 _Partner, Campaign_ y _Source_: definen la visualización de este contenido si el visitante tiene un UTM correspondiente en su URL de origen.
@@ -72,7 +72,7 @@ Después de la configuración, marque **Active Content** y agregue a la lista de
 
 En el ejemplo abajo tenemos una vitrina estándar, sin condiciones de exhibición y otra exclusiva para las visitas originadas de las audiencias de campañas patrocinadas de Google (utm_source=**google**/utm_medium=**cpc**):
 
-![coleção9](https://images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)![](//images.contentful.com/alneenqid6w5/28YV17bwwUyca6YyMo2Ckk/6d3d464c50b000d4a88c4132881d6236/exemplo_cpc-560x269.png)
+![coleção9](//images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)![](//images.contentful.com/alneenqid6w5/28YV17bwwUyca6YyMo2Ckk/6d3d464c50b000d4a88c4132881d6236/exemplo_cpc-560x269.png)
 
 En el escenario arriba, si el cliente tiene origen en la audiencia de campaña patrocinada se exhibirán en la vitrina **Lançamentos**, ubicada en la Home, los productos que corresponden al resultado de una búsqueda por la Marca de ID 200000, en caso contrario, se exhibirán los productos de la colección de ID 8.
 
diff --git a/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md b/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
index c40c4847d..bf8adafd5 100644
--- a/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
+++ b/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
@@ -18,7 +18,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 Para incluir metadatos al exportar una plantilla de precios de SKUs, siga los siguientes pasos:
 
 1. Haga clic en **Precios** en el menú de la izquierda de la página 
-![ESRefID 1.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/5VDIMnTlKtroiaZQtAwEsK/b9c0339593c7769260b2e57892e41d7c/ESRefID_1.png_h_250_h_250)
+![ESRefID 1.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/5VDIMnTlKtroiaZQtAwEsK/b9c0339593c7769260b2e57892e41d7c/ESRefID_1.png_h_250_h_250)
 
 2. Haga clic en **lista de precios** 
 
@@ -29,6 +29,6 @@ Para incluir metadatos al exportar una plantilla de precios de SKUs, siga los si
 5. Haga clic en **incluir metadados en las tablas exportadas**
 
 6. Haga clic en el botón **Exportar tabla**
-![ESRefID 2.png?h=250](https://images.ctfassets.net/alneenqid6w5/Yk3jKU2ZaUuZGoKkNjMhb/2cb1f11e7f8b26a401f77f3aa2d238a2/ESRefID_2.png_h_250)
+![ESRefID 2.png?h=250](//images.ctfassets.net/alneenqid6w5/Yk3jKU2ZaUuZGoKkNjMhb/2cb1f11e7f8b26a401f77f3aa2d238a2/ESRefID_2.png_h_250)
 
 En algunos minutos usted recibirá un e-mail con la tabla exportada.
diff --git a/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md b/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
index 8b1dc4199..3fd53d43c 100644
--- a/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
+++ b/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
@@ -3,22 +3,21 @@ title: 'Cómo insertar un proxy inverso frente a los servicios VTEX'
 id: 4PFWsfRAKviNVPf1bYdiir
 status: PUBLISHED
 createdAt: 2019-09-20T14:11:30.301Z
-updatedAt: 2020-08-20T21:15:13.613Z
-publishedAt: 2020-08-20T21:15:13.613Z
+updatedAt: 2023-10-26T22:21:31.465Z
+publishedAt: 2023-10-26T22:21:31.465Z
 firstPublishedAt: 2019-09-23T12:22:50.056Z
 contentType: tutorial
 productTeam: Reliability
 author: authors_24
-slug: cómo-insertar-un-proxy-inverso-frente-a-los-servicios-vtex
+slug: como-insertar-un-proxy-inverso-frente-a-los-servicios-vtex
 locale: es
-legacySlug: ¿por-qué-no-recomendamos-insertar-un-proxy-inverso-en-los-servicios-vtex?
+legacySlug: por-que-no-recomendamos-insertar-un-proxy-inverso-en-los-servicios-vtex
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
 <div class="alert alert-danger">
-<strong>Atención:</strong> las explicaciones de este artículo están destinadas a abordar casos de extrema excepción. No recomendamos que ninguna tienda use proxy inverso. Cuando se usa un proxy inverso, todo servicio perimetral (CDN) gestionado y optimizados por VTEX se dejará de lado, de modo que el trabajo de la tienda es quién será responsable de proveer de forma efectiva el sitio web, siendo responsable de realizar sus configuraciones, acompañamiento y gestión de particularidades como reenvío de encabezados, cookies y gestión de caché. No proporcionamos documentación de estas particularidades.
-  <br>
-VTEX no se responsabiliza por problemas en ese sistema, ya sea un CDN propio, servicio de WAF u otro recurso que se encuentre al frente de nuestros servidores. No tendremos visión de cualquier falla; por lo tanto, la solución <strong>no</strong> se encuadrará en nuestros acuerdos de SLA.
+  <p><strong>Atención:</strong> las explicaciones de este artículo están destinadas a abordar casos de extrema excepción. No recomendamos que ninguna tienda use proxy inverso. Cuando se usa un proxy inverso, todo servicio perimetral (CDN) gestionado y optimizados por VTEX se dejará de lado, de modo que el trabajo de la tienda es quién será responsable de proveer de forma efectiva el sitio web, siendo responsable de realizar sus configuraciones, acompañamiento y gestión de particularidades como reenvío de encabezados, cookies y gestión de caché. No proporcionamos documentación de estas particularidades.</p>
+  <p>VTEX no se responsabiliza por problemas en ese sistema, ya sea un CDN propio, servicio de WAF u otro recurso que se encuentre al frente de nuestros servidores. No tendremos visión de cualquier falla; por lo tanto, la solución <strong>no</strong> se encuadrará en nuestros acuerdos de SLA.</p>
 </div>
 
 Si incluso después de leer la alerta anterior desea apuntar su propia CDN a la CDN de VTEX, será necesario insertar un proxy inverso frente a los servicios de VTEX. Para hacer esto, cree las entradas TXT que se indican a continuación. Servirán como entrada de verificación para informarnos que el host de hecho apunta a VTEX. Sin esto, VTEX no puede proveer navegación.
@@ -34,10 +33,10 @@ Por lo tanto, la configuración debería quedar así:
 Además, también será necesario que todo el tráfico de `/.well-known /acme-challenge/*` llegue a VTEX. Algunos proxys inversos capturan esta ruta y, con eso, no podemos emitir o renovar el certificado SSL.
 
 <div class="alert alert-warning">
-VTEX solo provee navegación si::<br>
-- Podemos ver que el host apunta a VTEX (conforme nuestro CNAME).<br>
-- Conseguimos emitir/renovar certificados SSL para el host.<br>
-Si no se cumplen ambas condiciones, VTEX dejará de entregar el sitio web, pues se caracteriza por estar fuera del aire.
+  <p>VTEX solo provee navegación si:
+    <ul>
+      <li>Podemos ver que el host apunta a VTEX (conforme nuestro CNAME).</li>
+      <li>Conseguimos emitir/renovar certificados SSL para el host.</li>
+    </ul>
+Si no se cumplen ambas condiciones, VTEX dejará de entregar el sitio web, pues se caracteriza por estar fuera del aire.</p>
 </div>
-
-
diff --git a/docs/tutorials/es/how-to-install-a-service-worker.md b/docs/tutorials/es/how-to-install-a-service-worker.md
index 10eca1b94..d7cd5289a 100644
--- a/docs/tutorials/es/how-to-install-a-service-worker.md
+++ b/docs/tutorials/es/how-to-install-a-service-worker.md
@@ -3,33 +3,35 @@ title: 'Cómo instalar un Service Worker'
 id: 2H057iW0mQGguKAciwAuMe
 status: PUBLISHED
 createdAt: 2018-03-13T14:53:11.260Z
-updatedAt: 2023-04-05T17:55:03.904Z
-publishedAt: 2023-04-05T17:55:03.904Z
+updatedAt: 2024-01-19T12:54:32.525Z
+publishedAt: 2024-01-19T12:54:32.525Z
 firstPublishedAt: 2018-03-13T17:48:34.728Z
 contentType: tutorial
 productTeam: Financial
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 2AhArvGNSPKwUAd8GOz0iU
 slug: como-instalar-un-service-worker
 locale: es
 legacySlug: como-instalar-un-service-worker
-subcategory: 
+subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
 Service Worker es un script que su navegador ejecuta en segundo plano, independiente de la Web, permitiendo recursos como sincronización periódica, notificaciones push e incluso ejecución en modo off-line.
 
 Para crear el script, siga el paso a paso abajo:
 
-1. En el Admin VTEX, acceda al módulo __Portal__.
-2. Haga clic en el icono de __Configuración__.
-3. Después, en la pestaña __Código__.
-4. Haga clic en __Nuevo__ y luego en __Archivo__.
-5. Incluya el nombre del archivo exactamente como: `service-worker.js`.
-6. Programe la __funcionalidad__.
-7. Para finalizar, haga clic en __Guardar__.
+1. En el Admin VTEX, acceda **Configuración de la tienda > Escaparate > Pagar**, o escriba **Pagar** en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en el icono de <i class="fas fa-cog"></i> del sitio deseado.
+3. En la pestaña `Código`, haga clic en el botón `Nuevo`.
+4. Luego haga clic en `Archivo`.
+5. Rellene el nombre del archivo exactamente como: `service-worker.js`.
+6. Haga clic en el botón `Crear`.
+7. Programa la funcionalidad.
+8. Clic en `Guardar`.
 
-A pesar de que el archivo se encuentra en `/files/service-worker.js`, recibe el header` Service-Worker-Allowed` con valor `/`, lo que permite interceptar requests desde la raíz del sitio.
+A pesar de que el archivo se encuentra en `/archivos/service-worker.js`, recibe el header `Service-Worker-Allowed` con valor `/`, lo que permite interceptar requests desde la raíz del sitio.
 
-Para [más información](https://developers.google.com/web/fundamentals/primers/service-workers/), consulte el Web Fundamentals de Google Developers.
+Para más información, consulte el [Web Fundamentals](https://developers.google.com/web/fundamentals/primers/service-workers/) de Google Developers.
 
 ### Artículos relacionados
+
 - [Cómo transformar mi tienda en un PWA](https://help.vtex.com/es/tutorial/como-transformar-el-sitio-de-mi-tienda-en-un-pwa--3i8VmYeToAUGKgo2kKK6I2)
diff --git a/docs/tutorials/es/how-to-integrate-an-external-gift-card-provider-with-vtex.md b/docs/tutorials/es/how-to-integrate-an-external-gift-card-provider-with-vtex.md
index b5db776ca..dbfee57fe 100644
--- a/docs/tutorials/es/how-to-integrate-an-external-gift-card-provider-with-vtex.md
+++ b/docs/tutorials/es/how-to-integrate-an-external-gift-card-provider-with-vtex.md
@@ -3,8 +3,8 @@ title: 'Cómo integrar un proveedor externo de Tarjeta de Regalo a VTEX'
 id: tutorials_450
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:26.566Z
-updatedAt: 2023-04-13T12:40:41.423Z
-publishedAt: 2023-04-13T12:40:41.423Z
+updatedAt: 2024-06-04T18:55:35.271Z
+publishedAt: 2024-06-04T18:55:35.271Z
 firstPublishedAt: 2017-04-27T23:03:24.938Z
 contentType: tutorial
 productTeam: Financial
@@ -19,17 +19,14 @@ En VTEX, una de las opciones para usar una tarjeta de regalo es que se utilice c
 
 En este contexto, hay algunos casos de clientes que ya trabajan con su propio proveedor. Este sistema gestiona su relación de créditos o puntos bajo una base de clientes que participan en un sistema de fidelización, por ejemplo.
 
-Dicho esto, el cliente tiene la opción de integrar la solución externa al sistema VTEX. Aquí, explicaremos el procedimiento para realizar esta integración.
+Si el cliente desea integrar una solución externa de tarjetas de regalo al sistema VTEX, es necesario utilizar el [Giftcard Provider Protocol](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol).
 
 ## Desarrollo de provider
-VTEX cuenta con Gift Card Provider Protocol, es decir, una guía de llamadas de API que se harán para comunicarse con nuestro sistema.
 
-De este modo, el cliente debe desarrollar un middleware —sistema que intermedia entre dos sistemas diferentes, en este caso, el proveedor externo y los sistemas de VTEX.
-                                                                                  Luego, una vez implementado, podrá recibir las llamadas de VTEX e interpretar la información contenida en cada una de estas.
+A través del [Giftcard Provider Protocol](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol), el proveedor externo de tarjetas de regalo debe desarrollar un [middleware](https://es.wikipedia.org/wiki/Middleware) para transmitir información entre su sistema y VTEX.
 
-Para más detalles, consulte nuestra documentación técnica sobre [Gift Card Provider Protocol](https://developers.vtex.com/docs/guides/giftcard-provider-protocol-overview). 
+Para obtener más información sobre el sistema de tarjetas de regalo en VTEX, visite [Giftcard Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api).
 
-## Envío del endpoint 
-Terminada la primera etapa, el cliente debe enviar a VTEX el endpoint que se utilizará para realizar las llamadas. Esta ruta funcionará como un puente entre los dos sistemas. 
+## Envío de información del endpoint 
 
-Por último, VTEX registra el endpoint del proveedor en su sistema. Así, el sistema externo de tarjeta de regalo se integrará a VTEX y se utilizará en todo cierre de compra en el que el cliente lo utilice como medio de pago.
+Luego de crear el middleware, el proveedor debe abrir un [ticket](https://help.vtex.com/es/support) en VTEX informando los endpoints que utilizarán los clientes para realizar transacciones de pago utilizando su sistema de tarjetas de regalo.
diff --git a/docs/tutorials/es/how-to-manage-subscriptions.md b/docs/tutorials/es/how-to-manage-subscriptions.md
index 4dce5bef6..762c20abc 100644
--- a/docs/tutorials/es/how-to-manage-subscriptions.md
+++ b/docs/tutorials/es/how-to-manage-subscriptions.md
@@ -3,8 +3,8 @@ title: 'Cómo Gestionar Suscripciones '
 id: 6Jk50FPbv6iuz1OsFypv8x
 status: PUBLISHED
 createdAt: 2020-02-05T14:18:54.781Z
-updatedAt: 2022-12-05T16:48:31.127Z
-publishedAt: 2022-12-05T16:48:31.127Z
+updatedAt: 2023-12-21T14:08:39.725Z
+publishedAt: 2023-12-21T14:08:39.725Z
 firstPublishedAt: 2020-02-11T14:56:17.333Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -35,22 +35,26 @@ La sección de **Suscripciones Únicas** permite:
 - Visualizar un **gráfico dinámico** con la relación entre las *suscripciones activas*, *canceladas*, y *total de suscripciones*, dentro del período filtrado. - Al pasar el cursor sobre las líneas del gráfico, se puede ver en detalle el movimiento de las suscripciones por día.   
 - **Exportar suscripciones**  únicas dentro del período filtrado pulsando el botón de la esquina superior derecha de la pantalla.
 
-![ES Dashboard Assinatura única](https://images.ctfassets.net/alneenqid6w5/3BEDDrOsEARRJ1XfuwABDd/ecc8168966e3379654269a2d47b405c0/ES_Dashboard_Assinatura___nica.png)
+![ES Dashboard Assinatura única](//images.ctfassets.net/alneenqid6w5/3BEDDrOsEARRJ1XfuwABDd/ecc8168966e3379654269a2d47b405c0/ES_Dashboard_Assinatura___nica.png)
 
 ### Pedidos de Suscripción
 
+<div class = "alert alert-info">
+Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
+</div>
+
 La sección **Pedidos de Suscripción** permite: 
 
 - Filtrar la visualización del **Embudo de Pedidos de Suscripción** por período, entre los siguientes valores: `hoy`, `ayer`, `esta semana`, `este mes`, `este año`, `semana pasada`, `mes pasado`, `año pasado`, o un periodo `personalizado`, seleccionando fechas específicas.  
 - Acompañe el **número absoluto y porcentaje** correspondiente de Pedidos de Suscripción que han sido *programados*, *procesados*, *generados* y *completados* por período.  
 - Visualizar un **gráfico** con el porcentaje de pedidos *omitidos*, *ciclos con problemas* y *error de pago*. 
 
-![ES Dashboard Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/7s8Mp2U4qAUAxpiTQbJGy6/c24aea7486e45591e83591e452535db9/ES_Dashboard_Pedidos_Assinatura.png)
+![ES Dashboard Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/7s8Mp2U4qAUAxpiTQbJGy6/c24aea7486e45591e83591e452535db9/ES_Dashboard_Pedidos_Assinatura.png)
 
 - Al acceder a cada pestaña de la sección **Pedidos de Suscripción**, es posible visualizar el flujo y los detalles de los pedidos que fueron *omitidos*, los que presentaron *ciclos problemáticos*, aquellos que contienen un *error de pago* y  pedidos *completos*.  
 - Además de listar detalles de los errores que se produjeron durante el flujo de pedidos de suscripción, también es posible realizar el **reintento manual** de los pedidos con errores. Revise nuestro artículo sobre la [Resolución de problemas de  pedidos con suscripción](https://help.vtex.com/es/tutorial/como-solucionar-pedidos-de-assinatura-com-erros--uLL8AYBGdtAmbbdL5gRCf) para saber más. 
 
-![pedidos_assinaturas_print_es](https://images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
+![pedidos_assinaturas_print_es](//images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
 
 ### Suscriptores
 
diff --git a/docs/tutorials/es/how-to-manage-the-kit-stock.md b/docs/tutorials/es/how-to-manage-the-kit-stock.md
index 22133f265..0fa7ce14b 100644
--- a/docs/tutorials/es/how-to-manage-the-kit-stock.md
+++ b/docs/tutorials/es/how-to-manage-the-kit-stock.md
@@ -3,8 +3,8 @@ title: 'Gestionar el inventario del kit'
 id: frequentlyAskedQuestions_156
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.252Z
-updatedAt: 2019-12-31T15:26:27.183Z
-publishedAt: 2019-12-31T15:26:27.183Z
+updatedAt: 2024-04-29T13:09:03.955Z
+publishedAt: 2024-04-29T13:09:03.955Z
 firstPublishedAt: 2019-01-24T22:03:46.311Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,21 +19,13 @@ Es posible construir el Kit de dos formas. Siguen consideraciones sobre cada una
 
 ## Producto kit sin componente
 
-Normalmente es un Kit que en el CD del Tendero ya se encuentra en una estructura de Kit (diversos componentes) y en VTEX él sólo señala este Producto, sin la necesidad de catastro de sus componentes.
-
-Esto es, tanto el Precio como el Inventario son señalados directamente en SKU Kit.
+Normalmente es un Kit que en el CD del Tendero ya se encuentra en una estructura de Kit (diversos componentes) y en VTEX él sólo señala este Producto, sin la necesidad de catastro de sus componentes. Esto es, tanto el Precio como el Inventario son señalados directamente en SKU Kit.
 
 ## Producto kit con componente
 
-El kit con componentes se fundamenta en un Producto kit que posee un SKU que es nada más nada mismo que una “agrupación” de otros SKUs.
-
-Se utiliza normalmente este tipo cuando el kit se constituye de otros productos que ya se encuentran en la Tienda y son vendidos separadamente por origen.
-
-Esto es, usted selecciona aquellos SKUs de su tienda y señala que será el Precio y el Inventario necesario de cada SKU para componer 1 Kit de este Producto. Por ejemplo, en el siguiente catastro del kit Colorido:
-
-![](//images.contentful.com/alneenqid6w5/42WZMhNkPSaq2mCkQSQI0G/4c411361196ea8d24a8a1a08aabfa783/kit.png)
+El kit con componentes se fundamenta en un Producto kit que posee un SKU que es nada más nada mismo que una “agrupación” de otros SKUs. Se utiliza normalmente este tipo cuando el kit se constituye de otros productos que ya se encuentran en la Tienda y son vendidos separadamente por origen. Esto es, usted selecciona aquellos SKUs de su tienda y señala que será el Precio y el Inventario necesario de cada SKU para componer 1 Kit de este Producto. 
 
-O sea, el Producto Kit del Nombre Colorido se compone por otros diez SKUs. Cada uno con su precio y la cantidad necesaria de 1 ítem de cada SKU para que se pueda componer el Kit:
+Por ejemplo, un producto Kit Colorido se compone por otros diez SKUs. Cada uno con su precio y la cantidad necesaria de 1 ítem de cada SKU para que se pueda componer el Kit:
 
 ![](//images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
 
diff --git a/docs/tutorials/es/how-to-manually-invoice-an-order.md b/docs/tutorials/es/how-to-manually-invoice-an-order.md
index 8f0834ac9..22d740271 100644
--- a/docs/tutorials/es/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/es/how-to-manually-invoice-an-order.md
@@ -3,8 +3,8 @@ title: 'Como facturar un pedido'
 id: 7p1h852V5t54KyscpgxE2v
 status: PUBLISHED
 createdAt: 2020-12-28T20:50:42.445Z
-updatedAt: 2023-05-31T14:44:54.458Z
-publishedAt: 2023-05-31T14:44:54.458Z
+updatedAt: 2024-04-01T17:55:58.671Z
+publishedAt: 2024-04-01T17:55:58.671Z
 firstPublishedAt: 2020-12-28T21:01:55.107Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -34,7 +34,7 @@ Para enviar una factura a través del Admin VTEX, siga los pasos a continuación
 2. Busca el pedido en la barra de búsqueda o [usa los filtros](https://help.vtex.com/es/tutorial/como-filtrar-pedidos--tutorials_192).  
 3. Haz clic en el pedido deseado.
 4. Desplázate hacia abajo hasta la sección **Ítems a facturar** y haz clic en<i class = "fas fa-chevron-right"> </i> para ampliar.   
-![FaturaES](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)  
+![FaturaES](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)  
 5. Haz clic en el botón `Facturar`. 
 6. Haz clic en la opción de facturación deseada:    
     * **Enviar factura con referencia a los ítems:** para facturar el pedido haciendo referencia a los ítems del paquete.
@@ -64,6 +64,8 @@ Para enviar una factura a través del Admin VTEX, siga los pasos a continuación
 
 Una vez `facturado` el pedido, comprueba las facturas introducidas en la sección **Factura** como se muestra en la figura siguiente.
 
-![Itens faturarES](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
+![Itens faturarES](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
 
 En los casos de envío de [facturas parciales](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe), al [modificar o eliminar ítems de un pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190), el valor total del pedido se actualizará después de la facturación, y corresponderá al valor capturado por el _gateway_ de pagos de VTEX.
+
+No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
diff --git a/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md b/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md
index ea21882e8..3f50d641f 100644
--- a/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md
+++ b/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md
@@ -3,8 +3,8 @@ title: 'Modificar la información de dirección de los clientes'
 id: 3IQsuOvkMgmuwWQMQoo8UM
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:49.820Z
-updatedAt: 2023-03-28T22:57:51.457Z
-publishedAt: 2023-03-28T22:57:51.457Z
+updatedAt: 2024-06-06T20:47:33.052Z
+publishedAt: 2024-06-06T20:47:33.052Z
 firstPublishedAt: 2019-01-24T22:10:21.264Z
 contentType: tutorial
 productTeam: Master Data
@@ -18,12 +18,12 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 Para editar la información de los clientes es necesario que sigas los siguientes pasos:
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
-2. Selecciona la pestaña **Endereços** (Direcciones). Allí encontrarás a todos los usuarios que tienen registrada al menos una dirección.
+2. Clic en la pestaña **Direcciones**. Allí encontrarás a todos los usuarios que tienen registrada al menos una dirección.
 3. Realiza la búsqueda del cliente al cual le debas hacer el cambio.
-4. En la columna de **Ações** (Acciones) de la tabla, le da clic en la opción de **Editar**.
+4. En la columna de **Acciones** de la tabla, le da clic en la opción de editar <i class="fas fa-edit"></i>.
 5. Crea o edita la información necesaria.
-6. Clic en **Salvar** (Guardar).
-7. Luego clic en **Voltar** (Volver), para ver nuevamente el listado de direcciones.
+6. Clic en `Guardar`.
+7. Luego clic en `Volver`, para ver nuevamente el listado de direcciones.
 
 <div class="alert alert-warning">
 Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
diff --git a/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
index 5d57dc026..b27b50ab5 100644
--- a/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
@@ -1,10 +1,10 @@
 ---
 title: 'Optimizar las búsquedas con palabras sustitutas'
 id: 32FqSsl5VuQyiIMEc02Uwu
-status: PUBLISHED
+status: CHANGED
 createdAt: 2019-01-24T20:45:49.707Z
-updatedAt: 2021-09-14T19:00:59.249Z
-publishedAt: 2021-09-14T19:00:59.249Z
+updatedAt: 2024-02-28T22:28:58.551Z
+publishedAt: 2024-01-10T13:30:55.078Z
 firstPublishedAt: 2019-01-24T22:00:22.364Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 ---
 
 <div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
+No recomendamos el uso de <a href="https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu">Palabras sustitutas</a> cuando se utilice Intelligent search. Para asociar palabras con productos es preferible emplear <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ">Sinónimos</a>, ya que permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>.
 </div>
 
 ## Cómo funciona el buscador
@@ -39,15 +39,15 @@ Un recurso muy utilizado para agilizar las búsquedas del equipo interno es colo
 
 ### 1. Integración de productos
 Integrar los productos mediante el webservice ProductInsertUpdate permite agregar sus Palabras Sustitutas y asociarlas al producto en cuestión:
-<http://help.vtex.com/es/tutorial/manual-de-clases-y-metodos-utilizados-en-webservice>
+[](http://help.vtex.com/es/tutorial/manual-de-clases-y-metodos-utilizados-en-webservice)
 
 ### 2. Importación por planilla
 Cargar las Palabras Sustitutas directamente por planilla de producto, de modo masivo:
-<https://help.vtex.com/es/tutorial/registrando-producto#importacion-por-planilla>
+[](https://help.vtex.com/es/tutorial/registrando-producto#importacion-por-planilla)
 
 ### 3. Editar un producto
 Cargar las palabras sustitutas directamente a cada producto individualmente en el campo "Palabras Sustitutas":
-<https://help.vtex.com/es/tutorial/registrando-producto#registrando-por-el-admin>
+[](https://help.vtex.com/es/tutorial/registrando-producto#registrando-por-el-admin)
 
 ## Donde Consigo Palabras Sustitutas
 ### Google Trends
diff --git a/docs/tutorials/es/how-to-request-receivables-anticipation.md b/docs/tutorials/es/how-to-request-receivables-anticipation.md
index 7fcf4ce0d..9addc8edf 100644
--- a/docs/tutorials/es/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/es/how-to-request-receivables-anticipation.md
@@ -31,7 +31,7 @@ Ahora que ha verificado el saldo, es importante tener en cuenta que el valor mí
 
 Por ejemplo, si el menor valor que puede recibir es R$10, ese es el valor mínimo que puede anticipar. El valor máximo se informa en el propio Admin - el saldo que usted acaba de verificar - en la página "Anticipar cuentas por cobrar". 
 
-![antecipação](https://images.ctfassets.net/alneenqid6w5/2DQKbFjERNOa8wLmFq3nr9/ae2cced48c5774ced4415db9ab9756b6/image.png_h_250_h_250)
+![antecipação](//images.ctfassets.net/alneenqid6w5/2DQKbFjERNOa8wLmFq3nr9/ae2cced48c5774ced4415db9ab9756b6/image.png_h_250_h_250)
 
 <div class="alert alert-info">
 <strong>Atención</strong>: las cuentas por cobrar en disputa o programadas para el siguiente día hábil no pueden ser anticipadas.
diff --git a/docs/tutorials/es/how-to-return-order-items.md b/docs/tutorials/es/how-to-return-order-items.md
index 64522d3b2..f7143620a 100644
--- a/docs/tutorials/es/how-to-return-order-items.md
+++ b/docs/tutorials/es/how-to-return-order-items.md
@@ -3,8 +3,8 @@ title: 'Cómo devolver ítems del pedido'
 id: 2bSNWwD0g8fcUmuupLao9i
 status: PUBLISHED
 createdAt: 2020-12-28T21:23:42.045Z
-updatedAt: 2023-04-11T14:58:43.881Z
-publishedAt: 2023-04-11T14:58:43.881Z
+updatedAt: 2024-06-10T23:02:44.957Z
+publishedAt: 2024-06-10T23:02:44.957Z
 firstPublishedAt: 2020-12-28T21:27:16.332Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,12 +26,16 @@ La página de Detalles del pedido permite orquestar esa operación realizando lo
 3. En la sección «Facturas», haga clic en `Devolver ítems`.
 4. Seleccione los ítems que serán devueltos marcando la casilla de selección.
 5. Defina el número de unidades que se devolverán de cada ítem.
-6. Introduzca el valor adicional que se cobrará a su cliente en el campo `Valor adicional`. Este importe se refiere a los gastos de envío del pedido devuelto.<p>Por ejemplo, si un pedido tiene un coste de envío de $ 20,00, deberá rellenar este campo con $20,00 . Si se rellena con un valor inferior al total de los gastos de envío, el cliente recibe la mitad del valor rellenado (<b>Valor Adicional</b>) como inversión de la compra, y la otra mitad en tarjeta regalo. Siguiendo el ejemplo dado, suponga que en lugar de $20,00 (que es el coste total del envío) la tienda ha rellenado el Valor Adicional como $12,00. El cliente recibirá el reembolso de este importe en forma de una devolución de cargo de $6,00  más una voucher (GiftCard) de $6,00 reales.</p>*Este campo es opcional, se debe completar en caso de que el valor adicional forme parte de la política de devolución de su tienda.* 
+6. Introduzca el valor adicional que será devuelto a su cliente en el campo `Valor adicional`. Este importe se refiere a los gastos de envío del pedido devuelto.<p>Por ejemplo, si un pedido tiene un coste de envío de $ 20,00, deberá rellenar este campo con $20,00 . Si se rellena con un valor inferior al total de los gastos de envío, el cliente recibe la mitad del valor rellenado (<b>Valor Adicional</b>) como inversión de la compra, y la otra mitad en tarjeta regalo. Siguiendo el ejemplo dado, suponga que en lugar de $20,00 (que es el coste total del envío) la tienda ha rellenado el Valor Adicional como $12,00. El cliente recibirá el reembolso de este importe en forma de una devolución de cargo de $6,00  más una voucher (GiftCard) de $6,00 reales.</p>*Este campo es opcional, se debe completar en caso de que el valor adicional forme parte de la política de devolución de su tienda.* 
 7. Ingrese el motivo del valor adicional, en el campo `Referente a`.
-*Este campo es opcional, se debe completar en caso de que el valor adicional forme parte de la política de devolución de su tienda.*
+    > *Este campo es opcional, se debe completar en caso de que el valor adicional forme parte de la política de devolución de su tienda.*
 8. Introduzca el código de la `Factura de entrada`.
-*Se refiere a la factura de devolución, cuando el ítem regresa a su stock.*
+    > *Se refiere a la factura de devolución, cuando el ítem regresa a su stock. El número de la factura debe ser diferente al de la factura anterior.*
 9. Comente el `Motivo de la devolución`.
 10. Haz clic en `Solicitar reembolso`.
 
 Después de que el reembolso sea procesado por el sistema, los ítems devueltos y su información aparecerán en la sección *Ítems devueltos*.
+
+<div class = "alert alert-info">
+El cambio de pedidos se realiza a través de API por el endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> y la emisión de facturas actualizadas por el endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice">Order invoice notification</a>.
+</div>
diff --git a/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md b/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md
index 29121c531..ffd2feb0d 100644
--- a/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md
+++ b/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md
@@ -20,7 +20,7 @@ En la sección de __Gestión de pedidos__ es posible filtrar los pedidos realiza
 Si desea ver los pedidos que se han cerrado con esta promoción aplicada, basta con seguir los pasos abajo:
 
 1. En el menú del admin, haga clic en __Gestión de pedidos__.
-2. Haga clic en el botón de filtro y, dentro de la sección __Otros__, haga clic en la opción __Promociones__.![promo-filter-es](https://images.ctfassets.net/alneenqid6w5/4XQZ3Rs60MEQe0GOG2UUSu/ee14a01ab48b01b570445565a1979405/promo-filter-es.png)
+2. Haga clic en el botón de filtro y, dentro de la sección __Otros__, haga clic en la opción __Promociones__.![promo-filter-es](//images.ctfassets.net/alneenqid6w5/4XQZ3Rs60MEQe0GOG2UUSu/ee14a01ab48b01b570445565a1979405/promo-filter-es.png)
 3. Seleccione esta promoción y haga clic en __Confirmar__
 
 En la lista de pedidos, usted verá todos los pedidos cerradas con esta promoción.
diff --git a/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md b/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
index 9d239d65b..ef9246401 100644
--- a/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
+++ b/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
@@ -30,7 +30,7 @@ Basta incluir un atributo con el nombre `salesChannel`, conforme a lo ilustrado
 
 Y entonces, los siguientes pedidos se crearán con el canal de ventas configurado. Si no hay stock para determinado ítem en este canal el ítem será excluido del pedido.  
 
-![posicao.es](https://images.ctfassets.net/alneenqid6w5/1lTacScACYmqyzHKSZCydV/7a6e296f63afec40cf30c97a6a61e1ec/posicao.es.png)
+![posicao.es](//images.ctfassets.net/alneenqid6w5/1lTacScACYmqyzHKSZCydV/7a6e296f63afec40cf30c97a6a61e1ec/posicao.es.png)
 
 *Pantalla donde se encuentra el ID del salesChannel*
 
@@ -40,6 +40,6 @@ Basta incluir un atributo con el nombre `defaultSLA`, conforme a lo ilustrado en
 
 Y entonces, el SLA configurado tendrá precedencia sobre el SLA más barato para los siguientes pedidos que se crearán – y si éste tiene una ventana de entrega, será seleccionado el primer intervalo disponible.
 
-![transportadora.es](https://images.ctfassets.net/alneenqid6w5/41hy7FOGA3p94j3YX5kwiW/66ddd21e4f2ec65ae4a2ede3af059bbf/transportadora.es.png)
+![transportadora.es](//images.ctfassets.net/alneenqid6w5/41hy7FOGA3p94j3YX5kwiW/66ddd21e4f2ec65ae4a2ede3af059bbf/transportadora.es.png)
 
 *Pantalla donde se encuentra el ID del SLA*
diff --git a/docs/tutorials/es/how-to-set-up-recurrence-in-payment-conditions.md b/docs/tutorials/es/how-to-set-up-recurrence-in-payment-conditions.md
index df9ab2e28..cfc47b4cc 100644
--- a/docs/tutorials/es/how-to-set-up-recurrence-in-payment-conditions.md
+++ b/docs/tutorials/es/how-to-set-up-recurrence-in-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'Configurar recurrencia en condiciones de pago'
 id: 6EGuoAytLqU2CqUuaI2GUW
 status: PUBLISHED
 createdAt: 2017-06-29T20:56:04.718Z
-updatedAt: 2023-03-30T15:57:59.484Z
-publishedAt: 2023-03-30T15:57:59.484Z
+updatedAt: 2024-01-09T19:47:20.977Z
+publishedAt: 2024-01-09T19:47:20.977Z
 firstPublishedAt: 2017-07-03T15:16:40.562Z
 contentType: tutorial
 productTeam: Financial
@@ -26,8 +26,8 @@ Despues de realizar esta configuración podemos setear las condiciones especiale
 2. Clic en **Planes de pago**.
 3. Hacer clic en la condición de pago creada.
 4. Hacer clic en **Condición Especial**.
-5. Elegir la opción **Periodo**.
-6. Setearemos el rango de días para la validez de la condición de pago en **Sólo durante el período**.
+5. Elegir la opción **Fecha de vencimiento**.
+6. Setearemos el rango de días para la validez de la condición de pago en **Apenas para este periodo**.
 7. Debajo del periodo, veremos el campo **Recurrencia**. Alli podemos seleccionar **Todos los días** o (Desactivando la opción de "Todos los días") podemos seleccionar **los días de la semana** deseados; también podemos configurar una hora de inicio y una hora de finalización.
 8. Si queremos agregar otra **Recurrencia** debemos de hacer click en el boton `+`.
 
diff --git a/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index a630cea42..91d743bef 100644
--- a/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configure el conector para aceptar pagos con Adyen en VTEX'
 id: tutorials_2337
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:55:10.101Z
-updatedAt: 2023-03-24T14:56:13.138Z
-publishedAt: 2023-03-24T14:56:13.138Z
+updatedAt: 2024-03-18T17:52:42.714Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:52.166Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: como-configurar-el-gateway-adyen-en-vtex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 <div class="alert alert-warning">Las configuraciones documentadas en este artículo se realizan en un ambiente  externo a VTEX. Por lo tanto, pueden ser descontinuadas sin previo aviso.
 </div>
 
@@ -69,7 +71,7 @@ Luego, solo tiene que recoger las informaciones de Adyen para registrarlas en VT
 5. ¡Recuerde anotar el nombre de usuario y la contraseña que aparecerá en el campo Password, ya que no volverá a estar visible!
 6. Haga clic en el botón **Save**, que está al final de la página.
 7. Después de estos pasos, su usuario debería haber sido creado con éxito. El número 1 (indicado en la imagen en rojo) es el username. El número 2 es la contraseña (password) que deberá ingresarse en el ambiente VTEX.
-![Adyen - Image 2](https://images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
+![Adyen - Image 2](//images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
 8. Envíe un e-mail para el soporte de Adyen (suporte@adyen.com) solicitando las habilitaciones listadas en el siguiente modelo:
 
 > Asunto: Configuración de los permisos de usuario webservice de VTEX para `{accountName}`
@@ -94,13 +96,13 @@ Si pretende utilizar la plataforma de Adyen para hacer análisis antifraude con
 
 <ui>5. La configuración deberá verse conforme sigue abajo. Asegúrese de hacer clic en **Save configuration** después de completar las alteraciones.</ui>
 
-![Adyen - Image 1](https://images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
+![Adyen - Image 1](//images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
 
 ## Configuraciones en VTEX
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. Haga clic en **Afiliaciones de Gateways**.
-3. Haga clic en **Adyen**.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Adyen__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos del formulario con los datos obtenidos en Adyen y haga clic en el botón **Guardar**:
 
 - **username** - username Adyen (instrucción 5 de las **Configuraciones en  Adyen**).
diff --git a/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
index 4428fd74b..1d9f75046 100644
--- a/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -68,6 +68,6 @@ Rellene con el siguiente código HTML:
 <script src="https://h.online-metrix.net/fp/check.js?org_id={{cs_orgId}}&amp;session_id={{cs_merchantId}}{{cs_sessionId}}" type="text/javascript"></script>
 ```
 
-![braspag fingerprint](https://images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/f801a007a7d98773d06c741691a2e1ad/image.png_h_250_h_250)
+![braspag fingerprint](//images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/f801a007a7d98773d06c741691a2e1ad/image.png_h_250_h_250)
 
 Por último, publique los cambios.
diff --git a/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
index 130867c4c..d8665e158 100644
--- a/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -31,7 +31,7 @@ El consumidor programa una atención por medio de un formulario preparado por In
 
 El flujo de la programación que recorre el cliente comienza en la elección de la tienda física donde prefiere ser atendido. En la siguiente imagen, solo observamos una tienda registrada; sin embargo, su marca puede registrar las tiendas físicas que desee.
 
-![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
+![indeva1](//images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
 <div class="alert alert-info">
 También es posible proporcionar al cliente un enlace que conduce directamente al formulario de una tienda física específica. Simplemente agregue el ID de la tienda al final de la URL. Con eso, el vendedor puede compartir el enlace de su tienda, por ejemplo, a través de un código QR o en los medios sociales.
@@ -48,7 +48,7 @@ Al hacer clic en la tienda deseada, el cliente es conducido al formulario. Allí
 
 Finalmente, el cliente simplemente hace clic en Programar horario. Con eso, esta visita entrará en la fila de atención programada mostrada por la aplicación de los vendedores.
 
-![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
+![indeva2](//images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
 <div class="alert alert-warning">
 Por el momento, la confirmación de la programación debe ser realizada de forma manual por la tienda. El cliente no recibirá ningún mensaje automático.
@@ -58,13 +58,13 @@ Por el momento, la confirmación de la programación debe ser realizada de forma
 
 La aplicación de Indeva Store organiza la fila de programaciones realizadas para cada tienda física. Este puede ser usado por vendedores o gerentes tanto para controlar las próximas atenciones programadas como para la visualización del historial de visitas ya atendidas.
 
-![indeva3](https://images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
+![indeva3](//images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
 
 Al hacer clic en una programación específica, el vendedor tiene acceso a sus detalles: fecha, hora de la visita, nombre del cliente, mensaje enviado, cantidad de personas y el número de teléfono del cliente.
 
 Si desea entrar en contacto con el cliente a partir de esa pantalla, el vendedor puede hacer clic en el botón Abrir Whatsapp. Será direccionado directamente a una ventana de conversación con el cliente específico en la aplicación de mensajes.
 
-![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
+![indeva4](//images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
 <div class="alert alert-info">
 La aplicación puede ser instalada en diversos dispositivos de la misma tienda, pero recomendamos que su equipo utilice una app por tienda, y no por vendedor.
@@ -118,7 +118,7 @@ La aplicación para los vendedores y gerentes de la tienda está disponible tant
 
 Después de instalar y abrir la aplicación, el vendedor deberá informar el token de 10 dígitos de la tienda para sincronizar el dispositivo e iniciar sesión.
 
-![indeva5](https://images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
+![indeva5](//images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
 
 Para recibir el token, entre en contacto con el equipo de Indeva por los canales de soporte:
 
diff --git a/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index 218a9e086..a6fb2b281 100644
--- a/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -3,8 +3,8 @@ title: 'Cómo configurar el campo "Responsable de la recogida" en SmartCheckout
 id: 2GsFnXUJxSOYEE6U2c4Syw
 status: PUBLISHED
 createdAt: 2018-11-09T12:18:14.596Z
-updatedAt: 2023-03-23T19:34:48.154Z
-publishedAt: 2023-03-23T19:34:48.154Z
+updatedAt: 2023-07-27T17:07:55.563Z
+publishedAt: 2023-07-27T17:07:55.563Z
 firstPublishedAt: 2018-11-26T14:43:00.552Z
 contentType: tutorial
 productTeam: Shopping
@@ -22,7 +22,7 @@ El campo <strong>Responsable de la recogida</strong> sólo está disponible para
 Los [puntos de recogida](/tutorial/configurar-pontos-de-retirada-pickup-points?locale=es) dan una opción más a sus clientes: en lugar de esperar la entrega, ellos pueden elegir ir hasta un punto definido y buscar los produtos personalmente. Por defecto, esta acción está vinculada al usuario registrado que efectuó la compra. Sin embargo, usted puede habilitar el campo `Responsable por la recogida` en el checkout de su tienda, para que su cliente pueda nombrar a otra persona para recoger el producto.
 
 <div class="alert alert-warning">
-Si tiene instalada la aplicación <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> en su tienda, el código CSS descrito en el procedimiento a continuación solo debe ingresarse a través de la aplicación. Los scripts insertados a través de la interfaz de administración (pestaña <b>Código > Archivos</b>) no se reproducen en las tiendas que tienen la aplicación instalada.
+Si tiene instalada la aplicación <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> en su tienda, el código CSS descrito en el procedimiento a continuación solo debe ingresarse a través de la aplicación. Los scripts insertados a través de la interfaz de administración VTEX (pestaña <b>Código > Archivos</b>) no se reproducen en las tiendas que tienen la aplicación instalada.
 </div>
 
 Para configurar el campo (que viene desactivado de forma predeterminada), siga los pasos abajo:
@@ -36,7 +36,7 @@ Para configurar el campo (que viene desactivado de forma predeterminada), siga l
 
 ```
 .vtex-omnishipping-1-x-container.shp-pickup-receiver{
-    display: block;
+    display: block; !import;
 }
 ```
 
diff --git a/docs/tutorials/es/how-to-set-up-the-zoom.md b/docs/tutorials/es/how-to-set-up-the-zoom.md
index 2773e7608..351498c9c 100644
--- a/docs/tutorials/es/how-to-set-up-the-zoom.md
+++ b/docs/tutorials/es/how-to-set-up-the-zoom.md
@@ -19,7 +19,7 @@ Un recurso muy común en tiendas online es el zoom.
 
 Esto permite ver detalles de una imagen cuando el cliente va pasando el mouse sobre las fotos de un producto. Vamos a ver cómo configurar e implementar esta funcionalidad.
 
-![zoom-configurações](https://images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
+![zoom-configurações](//images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
 
 ## Configurando el CSS
 
@@ -33,7 +33,7 @@ Abajo reproducimos un trecho de CSS que puede usar como punto de partida para es
 
 Luego, vamos a enviar el archivo CSS grabado al servidor. Para eso, haga clic en el módulo de *CMS* > **Layout** > Haga click en la carpeta **CMS** > **Files Manager** > Haga click en **.css** > En la ventana que se despliega a la derecha, haga clic en el botón **Add**.
 
-![add-cms-.css ](https://images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
+![add-cms-.css ](//images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
 
 Luego, localice el archivo CSS grabado arriba y envíelo al servidor haciendo clic en el botón **Localizar** y luego en el botón **Salvar arquivo** ("salvar archivo").
 
@@ -52,4 +52,4 @@ Ahora sólo hay que insertar `zoom="on"` en la tag del producto. Como se ve abaj
 
 Usted debe también configurar el tamaño estándar de la imagen de zoom. Puede definir eso en el módulo de **CMS** > **Configuraciones** > **Tipos de archivos**. Como estándar, ese tipo de imagen de zoom ya viene configurada con 1000×1000 pixels.
 
-![zoom-tiposdearquivos ES](https://images.ctfassets.net/alneenqid6w5/4Re3BTK1hSSMOQcsWwQy8k/0eea4e4c0e26855df5a1e5346fff421f/zoom_tipo_de_archivos.png)
+![zoom-tiposdearquivos ES](//images.ctfassets.net/alneenqid6w5/4Re3BTK1hSSMOQcsWwQy8k/0eea4e4c0e26855df5a1e5346fff421f/zoom_tipo_de_archivos.png)
diff --git a/docs/tutorials/es/how-to-set-up-visa-debit.md b/docs/tutorials/es/how-to-set-up-visa-debit.md
index edd044b3f..8441c06d7 100644
--- a/docs/tutorials/es/how-to-set-up-visa-debit.md
+++ b/docs/tutorials/es/how-to-set-up-visa-debit.md
@@ -21,16 +21,16 @@ Para configurar el pago por Visa Débito en su tienda, en el Admin VTEX, accede
 En primer lugar, deberemos crear un plan de pagos para habilitar Visa Débito en el Checkout.
 Para eso, en **Configuración** acceda al menú de opciones de **Planes de pago**:
 
-![2.3](https://images.ctfassets.net/alneenqid6w5/42TQNxEPPO8c0wW8k64U2E/862916e5d2a003018fd37d03a470adbc/2.3.png)
+![2.3](//images.ctfassets.net/alneenqid6w5/42TQNxEPPO8c0wW8k64U2E/862916e5d2a003018fd37d03a470adbc/2.3.png)
 
 Seleccione Visa Electron para crear el plan de pagos:
 
-![4.3](https://images.ctfassets.net/alneenqid6w5/2XPKxgRKhWkGoqeUa0qmSS/ad23305902a49316570c5ac8f9b3cf7d/4.3.png)
+![4.3](//images.ctfassets.net/alneenqid6w5/2XPKxgRKhWkGoqeUa0qmSS/ad23305902a49316570c5ac8f9b3cf7d/4.3.png)
 
 ### Configurar Plan de Pagos
 Se deberá seleccionar la afiliación deseada para transaccionar los pagos, activar el plan de pagos y finalmente salvar los cambios:
 
-![3.3](https://images.ctfassets.net/alneenqid6w5/4dI5gmauwMGuukI2wCSMOO/89fa814df4dd450410ed5cabe0cb89b8/3.3.png)
+![3.3](//images.ctfassets.net/alneenqid6w5/4dI5gmauwMGuukI2wCSMOO/89fa814df4dd450410ed5cabe0cb89b8/3.3.png)
 
 ### Visualizando las tarjetas de débito en Checkout
 Luego de finalizar la configuración del plan de pagos de Visa Débito, se verá una nueva pestaña en el Checkout, llamada Tarjeta de Débito. Dicha pestaña contendrá la opción de Visa Débito para ser elegida por el cliente y pagar online.
diff --git a/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md b/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md
index e900218b8..99bdcf398 100644
--- a/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md
+++ b/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: primeros pasos del seller'
 id: 6w1vBdRH2uuBGmUqgNQjwK
 status: PUBLISHED
 createdAt: 2021-01-26T15:08:22.524Z
-updatedAt: 2023-03-02T21:29:12.945Z
-publishedAt: 2023-03-02T21:29:12.945Z
+updatedAt: 2024-05-30T22:41:41.434Z
+publishedAt: 2024-05-30T22:41:41.434Z
 firstPublishedAt: 2021-09-15T20:50:27.452Z
 contentType: tutorial
 productTeam: Channels
@@ -53,6 +53,8 @@ Conozca algunos detalles sobre el lanzamiento de la versión Beta de Seller Port
 
 ## Configurar su tienda
 
+<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+
 Para comenzar a vender sus productos en el marketplace, se debe configurar su tienda en el Seller Portal. Este artículo explica el flujo completo de esa configuración inicial, e indica otra documentación más detallada sobre los pasos a seguir. La configuración básica de Seller Portal incluye los pasos a continuación.
 
 ### 1. Catálogo
@@ -131,9 +133,18 @@ Anuncio es el nombre que le damos a un producto o variación de un seller, que h
 ### 7. Pedidos
 En el momento en que el cliente final de la tienda presiona el botón *Pagar*, se genera un pedido en VTEX. Esto significa que ahora usted podrá realizar el seguimiento del flujo del pedido en el módulo de Gestión de pedidos dentro del panel de administración de su tienda. Es decir, puede conocer los detalles de cada paso del progreso del pedido. Para acceder al módulo de pedidos, navegue por la barra lateral haciendo clic en  Pedidos > Todos los pedidos / Transacciones. Conozca más leyendo nuestro artículo:
 
-- [Como funcionan pedidos en VTEX](https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE)
+- [Como funcionan pedidos en VTEX](https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE)  
+
+### 8. Crear y gestionar promociones.
+
+La página **Promociones** en el Seller Portal permite a los retaillers y marketplaces crear promociones y administrar una lista completa de promociones registradas, simplificando la administración de promociones.
+
+Para aprender más, lea los siguientes artículos:
+
+- [Seller Portal: Promociones](https://help.vtex.com/es/tutorial/seller-portal-promocoes--73LL7Ja0P4JbD77AH0jHwu)  
+- [Seller portal: crear una promoción](https://help.vtex.com/es/tutorial/seller-portal-criar-uma-promocao--kzNPEaiJE8EWkDzO9dbBI)  
 
-### 8. Supervisar Gestión de anuncios
+### 9. Supervisar Gestión de anuncios
 
 El módulo «Gestión de anuncios» permite a los sellers supervisar el envío de anuncios a todos los canales integrados con la tienda y su sincronización. La página principal posee dos componentes que muestran, en tiempo real, el status de los anuncios y sus actualizaciones a partir de los datos procedentes del marketplace y de otros módulos VTEX.  Es donde los sellers pueden dar seguimiento a todas las interacciones de tipo Catálogo, Precio o Stock en sus anuncios para identificar errores durante el envío y sincronización de los anuncios.
 
diff --git a/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md b/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md
index f53e43df3..720d6e52f 100644
--- a/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md
+++ b/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md
@@ -3,8 +3,8 @@ title: 'Configurar Google Analytics 4 en una tienda VTEX'
 id: G2P0rmSrEiqCcmUMyUUwG
 status: PUBLISHED
 createdAt: 2017-07-30T22:53:46.285Z
-updatedAt: 2023-05-03T16:21:13.207Z
-publishedAt: 2023-05-03T16:21:13.207Z
+updatedAt: 2023-07-17T13:35:10.259Z
+publishedAt: 2023-07-17T13:35:10.259Z
 firstPublishedAt: 2017-07-30T23:24:21.394Z
 contentType: tutorial
 productTeam: Others
@@ -35,5 +35,5 @@ En ambos casos, almacena el código ID de la propiedad en Google Analytics en fo
 
 Una vez que hayas realizado las configuraciones necesarias en tu cuenta de Google Analytics, tendrás que cambiar la configuración de Google Tag Manager para detectar los eventos de tu tienda siguiendo los pasos descritos en [Configurar Google Tag Manager](https://help.vtex.com/es/tutorial/integracao-com-o-google-tag-manager).  
 
-Si tu tienda utiliza [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), además de realizar la configuración, debes configurar una nueva versión de la aplicación Google Tag Manager. Para más información, accede a [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+Si tu tienda utiliza [VTEX IO - Store Framework](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), además de realizar la configuración, debes configurar una nueva versión de la aplicación Google Tag Manager. Para más información, accede a [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
diff --git a/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md b/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md
index 519501a8d..ee081a33f 100644
--- a/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md
+++ b/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md
@@ -1,10 +1,10 @@
 ---
 title: 'Cómo transformar el sitio de mi tienda en un PWA'
 id: 3i8VmYeToAUGKgo2kKK6I2
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-03-19T18:20:25.794Z
-updatedAt: 2023-03-29T13:18:46.962Z
-publishedAt: 2023-03-29T13:18:46.962Z
+updatedAt: 2024-05-07T14:04:52.042Z
+publishedAt: 2023-07-10T14:28:55.813Z
 firstPublishedAt: 2018-03-20T14:54:55.189Z
 contentType: tutorial
 productTeam: Others
@@ -66,7 +66,7 @@ __Para crear el JSON, realice el siguiente procedimiento: __
 
 __Su archivo debe ser importado en index.html, así:__
 
-`<link rel="manifest" href="/files/manifest.json">`
+`<link rel="manifest" href="/arquivos/manifest.json">`
 
 Después de eso, su aplicación web podrá abrir una pantalla de bienvenida exactamente igual a las apps nativas.
 
@@ -83,7 +83,7 @@ __Para crear el script, realice el procedimiento a continuación:__
 6. Programe la funcionalidad.
 7. Para finalizar, haga clic en __Guardar__.
 
-A pesar de que el archivo se encuentra en `/files/service-worker.js`, este recibe el header `Service-Worker-Allowed` con valor `/`, lo que permite interceptar requests desde la raíz del sitio web.
+A pesar de que el archivo se encuentra en `/arquivos/service-worker.js`, este recibe el header `Service-Worker-Allowed` con valor `/`, lo que permite interceptar requests desde la raíz del sitio web.
 
 ### Tercer paso
 La forma fácil de saber si usted está en el camino correcto en la construcción de su PWA es usar alguna herramienta de inspección, como Lighthouse de Google.
diff --git a/docs/tutorials/es/how-to-use-conditions-builder-app.md b/docs/tutorials/es/how-to-use-conditions-builder-app.md
index 5bc58e663..d7b97c7aa 100644
--- a/docs/tutorials/es/how-to-use-conditions-builder-app.md
+++ b/docs/tutorials/es/how-to-use-conditions-builder-app.md
@@ -36,11 +36,11 @@ Después de instalar, usted puede acceder a la app desde la barra lateral (secci
 4. (Opcional) Escriba una pequeña descripción de su condición. Esta descripción es sólo para control interno, no será visible a sus clientes.
 5. Haga clic en "Empezar a construir".
 
-![createCondition](https://images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
+![createCondition](//images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
 
 Después de presionar el botón "Empezar a construir", usted verá un editor y una lista de bloques en el lado izquierdo de la pantalla. Ahora sólo tiene que arrastrar los bloques al editor y conectarlos, creando así su lógica.
 
-![creating](https://images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
+![creating](//images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
 
 ### Edición de una condición
 
@@ -53,4 +53,4 @@ Si desea que una condición ya no se aplique, usted puede simplemente deshabilit
 - Cuando el botón al lado de la condición es __azul__, está __habilitado__.
 - Cuando el botón al lado de la condición es __gris__, está __deshabilitado__.
 
-![enableDisableEnglish](https://images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
+![enableDisableEnglish](//images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
diff --git a/docs/tutorials/es/how-to-use-the-index-report.md b/docs/tutorials/es/how-to-use-the-index-report.md
index 87b41bf36..7389ace68 100644
--- a/docs/tutorials/es/how-to-use-the-index-report.md
+++ b/docs/tutorials/es/how-to-use-the-index-report.md
@@ -1,10 +1,10 @@
 ---
 title: 'Utilizar el Informe de Indexación'
 id: 4ikVpMhwByyS8sysaeOIm4
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-07-04T13:10:40.431Z
-updatedAt: 2023-03-29T19:04:52.988Z
-publishedAt: 2023-03-29T19:02:27.075Z
+updatedAt: 2023-07-13T19:45:25.468Z
+publishedAt: 2023-07-13T19:45:25.468Z
 firstPublishedAt: 2017-07-04T19:16:21.471Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 5yDQmr18K4GgQAeGwq8USa
 
 El **Informe de Indexación** es el reporte que indica el status de indexación de todos los productos de la tienda. 
 
-![productosindexados](https://images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
+![productosindexados](//images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> Acceda a ver más información en <a href="/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion">Entendiendo el funcionamiento de la indexación.</a>
diff --git a/docs/tutorials/es/how-to-use-the-meta-tags-control.md b/docs/tutorials/es/how-to-use-the-meta-tags-control.md
index 7c868d309..819054f45 100644
--- a/docs/tutorials/es/how-to-use-the-meta-tags-control.md
+++ b/docs/tutorials/es/how-to-use-the-meta-tags-control.md
@@ -3,8 +3,8 @@ title: 'Cómo utilizar el control de meta tags'
 id: 2OPiSPubgcEqIikAWsCouk
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:38.270Z
-updatedAt: 2023-03-29T17:49:39.799Z
-publishedAt: 2023-03-29T17:49:39.799Z
+updatedAt: 2023-10-17T14:24:54.898Z
+publishedAt: 2023-10-17T14:24:54.898Z
 firstPublishedAt: 2019-01-24T22:06:45.424Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -55,5 +55,5 @@ A continuación puede observar un ejemplo de meta tags insertadas por el control
 ```
 
 <div class="alert alert-info">
-Si usted no desea usar la tag canonical (&lt;link rel="canonical"&gt;), puede inhabilitarla a través de un <a href="http://help.vtex.com/es/faq/control-para-deshabilitar-la-tag-canonical">control específico para eso</a>.
+Si usted no desea usar la tag canonical (&lt;link rel="canonical"&gt;), puede inhabilitarla a través de un <a href="https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag">control específico para eso</a>.
 </div>
diff --git a/docs/tutorials/es/how-to-use-the-search-result-control.md b/docs/tutorials/es/how-to-use-the-search-result-control.md
index 46fc722cb..8d1889b3d 100644
--- a/docs/tutorials/es/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/es/how-to-use-the-search-result-control.md
@@ -46,14 +46,14 @@ A continuación se muestra la lista de todos los atributos del control Search Re
 
 El código renderizado por el control Search Result tiene, de forma predeterminada, la siguiente estructura:
 
-![searchResult1](https://images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
+![searchResult1](//images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
 
 Y los elementos correspondientes que son renderizados por el control en su versión no personalizada siguen el patrón abajo:
 
-![searchResult2](https://images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
+![searchResult2](//images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
 
-![searchResult3](https://images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
+![searchResult3](//images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
 
-![searchResult4](https://images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
+![searchResult4](//images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
 
-![searchResult5](https://images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
+![searchResult5](//images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
diff --git a/docs/tutorials/es/how-to-use-the-shareable-cart-app.md b/docs/tutorials/es/how-to-use-the-shareable-cart-app.md
index 01c743ea9..2c12eb90f 100644
--- a/docs/tutorials/es/how-to-use-the-shareable-cart-app.md
+++ b/docs/tutorials/es/how-to-use-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 La app [Carrito Compartible](https://apps.vtex.com/vtex-social-selling/p) permite a los vendedores seleccionar productos para sus clientes y compartir el carrito lleno por canales como WhatsApp, Facebook Messenger y correo electrónico (Social Selling).
 
-![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artículo explica todos los pasos para utilizar esta funcionalidad: activar app, elegir los productos, agregar el código del vendedor, compartir y crear un nuevo carrito. Antes de comenzar, tienes que [activar esta funcionalidad en su tienda](https://help.vtex.com/es/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg).
 
@@ -31,25 +31,25 @@ Donde `{Dirección web de su tienda}` debe ser reemplazada por la dirección del
 
 La interfaz de carrito compartible debe aparecer en la pantalla, incluyendo algunos de los íconos que se muestran a continuación. Las opciones disponibles dependen de la configuración elegida por la tienda.
 
-![Screen Shot 2020-05-03 at 17.37.11](https://images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
+![Screen Shot 2020-05-03 at 17.37.11](//images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
 
 ## Escoger los productos
 
 Una vez activada la app, no es necesario iniciar sesión para empezar a navegar y seleccionar productos. Basta con navegar por la tienda con normalidad, como si estuviera haciendo una compra en línea. Una vez que haya elegido todos los productos para el cliente, simplemente abra el carrito y siga los siguientes pasos en la interfaz de carrito compartible.
 
-![shareable-cart-chooseproducts](https://images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
+![shareable-cart-chooseproducts](//images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
 
 ## Agregar código de vendedor
 
-Después de seleccionar los productos, haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> para agregar su código de vendedor. Siga las instrucciones de la tienda al rellenar, pues cada tienda puede elegir diferentes formas de identificar a los vendedores y añadir descuentos a su carrito.
+Después de seleccionar los productos, haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> para agregar su código de vendedor. Siga las instrucciones de la tienda al rellenar, pues cada tienda puede elegir diferentes formas de identificar a los vendedores y añadir descuentos a su carrito.
 
-![shareable-cart-addcode](https://images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
+![shareable-cart-addcode](//images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
 
 ## Rellene los datos personales y la dirección (opcional)
 
 Según la preferencia del cliente y la orientación de su tienda, podrá rellenar los datos personales y de entrega del pedido. **Los datos de pago siempre deben ser ingresados por el cliente**.
 
-![shareable-cart-customerdetails](https://images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
+![shareable-cart-customerdetails](//images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
 
 <div class="alert alert-danger" role="alert"><strong>Nunca pida los datos de pago al enviar el carrito.</strong> Incluso si el cliente insiste, informe que es por la seguridad de todos que él debe ingresar los datos de pago.</div>
 
@@ -57,13 +57,13 @@ Según la preferencia del cliente y la orientación de su tienda, podrá rellena
 
 Después de agregar su código de vendedor, haga clic en el botón correspondiente a la opción deseada. A continuación, detallamos los pasos para cada forma en la que se puede compartir.
 
-![shareable-cart-sharecart](https://images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
+![shareable-cart-sharecart](//images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
 
 ### WhatsApp
 
 Para compartir el carrito por WhatsApp:
 
-1. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/34fTsrnmu0yZKKAU2Kq9iR/a9e805534e6bc81434026357529be8a3/image11.png" />
+1. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/34fTsrnmu0yZKKAU2Kq9iR/a9e805534e6bc81434026357529be8a3/image11.png" />
 2. Digite el **número de teléfono del cliente** y haga clic en OK.
 3. (Opcional) Personalice el mensaje en WhatsApp.
 4. Envíe el mensaje por WhatsApp.
@@ -74,7 +74,7 @@ Para compartir el carrito por WhatsApp:
 
 Para compartir el carrito por Facebook Messenger:
 
-1. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/513wjcWdQzEydkFpsdm2Kb/e6ffef11d724e6fc1b66bf00504c81bb/image1.png" />
+1. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/513wjcWdQzEydkFpsdm2Kb/e6ffef11d724e6fc1b66bf00504c81bb/image1.png" />
 2. Digite el **nombre del perfil del cliente** en Facebook Messenger.
 3. Personalice el mensaje en Facebook Messenger.
 4. Envíe el mensaje por Facebook Messenger.
@@ -88,7 +88,7 @@ No es posible compartir carritos en Messenger para perfiles desconocidos. Si el
 
 Para compartir el carrito por SMS: 
 
-1. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/aYyWKNKx0Fb4sSNT5yNJQ/34f7516d18c2f6efcb6c62c70ba8c04b/image7.png" />
+1. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/aYyWKNKx0Fb4sSNT5yNJQ/34f7516d18c2f6efcb6c62c70ba8c04b/image7.png" />
 2. Digite el **número de teléfono del cliente** y haga clic en OK.
 3. (Opcional) Personalice el mensaje en su aplicación de SMS.
 4. Envíe el mensaje por su aplicación de SMS.
@@ -97,7 +97,7 @@ Para compartir el carrito por SMS:
 
 Para compartir el carrito por Enlace: 
 
-1. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2GZp3YTXtUkh5KvG9BTFx6/0921f73c5c553a90ddd39056ab918202/image15.png" />
+1. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2GZp3YTXtUkh5KvG9BTFx6/0921f73c5c553a90ddd39056ab918202/image15.png" />
 2. Copie el enlace destacado en **Enlace para compartir**.
 3. (Opcional) Escriba un mensaje personalizado con el enlace. 
 4. Envíe el enlace al cliente en su canal de contacto.
@@ -106,7 +106,7 @@ Para compartir el carrito por Enlace:
 
 Para compartir el carrito por Gmail:
 
-1. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/1rQ6MAeLHDZZ4vnX2p3Gyq/17bcbb4ebb94ac94a34dffb6c3515663/image14.png" />
+1. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/1rQ6MAeLHDZZ4vnX2p3Gyq/17bcbb4ebb94ac94a34dffb6c3515663/image14.png" />
 2. Digite la **dirección de correo electrónico del cliente** y haga clic en OK.
 3. (Opcional) Personalice el mensaje en Gmail.
 4. Envíe el mensaje por Gmail.
@@ -117,7 +117,7 @@ Para compartir el carrito por Gmail:
 
 Para compartir el carrito por Correo Electrónico:
 
-1. Haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/1B5ehv90NAceay9z6PPr7R/70fd43fed7c4aaec4e5a902c01255072/image8.png" />
+1. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/1B5ehv90NAceay9z6PPr7R/70fd43fed7c4aaec4e5a902c01255072/image8.png" />
 2. Digite la **dirección de correo electrónico del cliente** y haga clic en OK.
 3. (Opcional) Personalice el mensaje en su aplicación de correo electrónico.
 4. Envíe el mensaje por su aplicación de correo electrónico.
@@ -126,7 +126,7 @@ Para compartir el carrito por Correo Electrónico:
 
 ## Limpiar carrito
 
-Después de terminar la atención de un cliente, haga clic en el botón <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2fM6iuMfYNkTWlPA1vaSFM/c5c7c03611d846d609907d272b66684b/image5.png"/> para limpiar su carrito y escoger nuevos productos para otro cliente.
+Después de terminar la atención de un cliente, haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2fM6iuMfYNkTWlPA1vaSFM/c5c7c03611d846d609907d272b66684b/image5.png"/> para limpiar su carrito y escoger nuevos productos para otro cliente.
 
 <div class="alert alert-info" role="alert"><strong>¡Cada vendedor puede trabajar con varios clientes!</strong> Recomendamos guardar los enlaces ya compartidos en una plantilla o en un cuaderno de notas. De esta manera, mantiene sus carritos organizados y podrá hacer cambios cuando lo solicite un cliente.</div>
 
diff --git a/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md b/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md
index b3746f7d6..6c3a5fef9 100644
--- a/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md
+++ b/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md
@@ -17,6 +17,6 @@ subcategory:
 
 Cuando un producto es agregado en el carrito serán destacados los valores cobrados de cada impuesto configurado anteriormente. Para el cálculo de impuesto es necesario el llenado de los datos del cliente y los datos de entrega de compra. En la página de finalizar compra, los impuestos estarán siempre destacados. El encargado de la tienda también tendrá la información destacada en el Gestión de Pedidos.
 
-![Screenshot 3 -Taxes](https://images.ctfassets.net/alneenqid6w5/1yksMys16QmgYSsa6SqCIC/3f71427d0e6c02d48db88c52da9dfe04/Screenshot_3.png)
+![Screenshot 3 -Taxes](//images.ctfassets.net/alneenqid6w5/1yksMys16QmgYSsa6SqCIC/3f71427d0e6c02d48db88c52da9dfe04/Screenshot_3.png)
 
 [Vea la estructura de API Rest para TaxHub](/es/tutorial/taxhub-estructura-del-api-rest)
diff --git a/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md b/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md
index 654926db5..e1ca2b4a4 100644
--- a/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md
+++ b/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md
@@ -23,7 +23,7 @@ Aquí ya tendremos indicado su status actual, el inicio (fecha y hora) de la tra
 
 Cada inscripción de Pedido tendrá sus datos restrictos a las condiciones de pago utilizadas para su cierre. Esto es, códigos de autorización, transacción, NSU, entre otros, están puestos a disposición dentro de cada registro.
 
-![payment_es](https://images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/f87572b076ab9705c62219316daa72d7/payment_es.jpg)
+![payment_es](//images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/f87572b076ab9705c62219316daa72d7/payment_es.jpg)
 
 Para mayores informaciones sobre los eventos generados en las transacciones, acceda: [Eventos de la transacción](/hc/es-419/articles/215876397 "Eventos de la transacción").
 
diff --git a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
index 4170b30b9..1bb48a014 100644
--- a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
@@ -38,7 +38,7 @@ Después de eso, una nueva sección estará disponible y podrá definir a travé
 
 Es posible limitar la disponibilidad del template a un período de tiempo predeterminado rellenando los campos __From__ y __To__, así como definir en qué categorías, productos, marcas y colecciones se aplicará el template elegido.
 
-![template-condicionado-cms](https://images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
+![template-condicionado-cms](//images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
 
 Después de llenar todos los campos, asegúrese de guardar los cambios realizados haciendo clic en __Save Layout__.
 
diff --git a/docs/tutorials/es/how-trade-policies-work.md b/docs/tutorials/es/how-trade-policies-work.md
index 1d431a163..20721d056 100644
--- a/docs/tutorials/es/how-trade-policies-work.md
+++ b/docs/tutorials/es/how-trade-policies-work.md
@@ -3,8 +3,8 @@ title: 'Como funciona una Política Comercial'
 id: 6Xef8PZiFm40kg2STrMkMV
 status: PUBLISHED
 createdAt: 2021-05-25T20:05:42.155Z
-updatedAt: 2022-12-08T14:39:11.093Z
-publishedAt: 2022-12-08T14:39:11.093Z
+updatedAt: 2024-06-20T22:52:38.544Z
+publishedAt: 2024-06-20T22:52:38.544Z
 firstPublishedAt: 2021-05-25T20:17:12.408Z
 contentType: tutorial
 productTeam: Others
@@ -33,7 +33,9 @@ Vea cómo se relacionan las diferentes configuraciones de VTEX con las política
 
 Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), póngase en contacto con nuestro equipo de Growth Operations en Soporte, seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`.
 
-La contratación de políticas comerciales adicionales para integración con un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), un [conector certificado (partner)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX está exenta de la cuota mensual.
+La contratación de políticas comerciales adicionales para integración con un [conector certificado](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX está exenta de la cuota mensual.
+
+<div class=alert alert-warning> Si se aplica la misma política comercial a un conector certificado y a un conector asociado, no hay exención de tarifas.</div>
 
 ## Catálogo
 Al [registrar productos](https://help.vtex.com/es/tutorial/cadastrando-produtos--tutorials_2567) en el catálogo, puede restringir su disponibilidad para determinadas políticas comerciales. De este modo, el catálogo se segmenta en función de las diferentes estrategias de negocio. Las estrategias pueden incluir la segmentación de productos por región, para un marketplace o para tipos específicos de clientes, como los empleados. Vea más información sobre la configuración del [catálogo](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ).
diff --git a/docs/tutorials/es/i-cant-import-the-price-table.md b/docs/tutorials/es/i-cant-import-the-price-table.md
new file mode 100644
index 000000000..2e112235b
--- /dev/null
+++ b/docs/tutorials/es/i-cant-import-the-price-table.md
@@ -0,0 +1,67 @@
+---
+title: 'No puedo importar la plantilla de precios'
+id: bglrzs7gLKWf97q8qRdRm
+status: PUBLISHED
+createdAt: 2024-06-10T15:11:02.787Z
+updatedAt: 2024-06-10T19:44:11.614Z
+publishedAt: 2024-06-10T19:44:11.614Z
+firstPublishedAt: 2024-06-10T17:28:51.238Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: no-puedo-importar-la-plantilla-de-precios
+locale: es
+legacySlug: no-puedo-importar-la-plantilla-de-precios
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras clave__: *plantilla de precios, importación de plantillas, celdas.*
+
+Las [tablas o plantillas de precio](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) almacenan información de SKU que tras aplicarse en determinados contextos, como políticas comerciales, promociones o clústeres de clientes, permiten calcular los valores de venta de los productos en una tienda VTEX. Para más información, consulta [Precio base](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) y [Precio fijo](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy).
+
+<div class ="alert alert-warning">
+  No se puede importar una plantilla de <b>precio calculado</b> en el Admin VTEX. Solo se permite <b>exportar</b> esta plantilla para que el retailer pueda consultar los valores de precio final de cada producto.
+</div>
+
+Tras [importar una plantilla de precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D) pueden aparecer algunos mensajes de error en algunos SKU según los ejemplos a continuación:
+
+- `"The resource you are looking for cannot be found: Price not found"`
+- `"Error occurred while converting spreadsheet: Object reference not set to an instance of an object."`
+- `"Import Fixed Table Error: Invalid headers - SKU ID"`
+
+Si identificas mensajes de error, valores de precio incorrectos u otros problemas al importar una plantilla, consulta las posibles soluciones que se describen a continuación.
+
+## Solución
+
+Para resolver problemas de importación en la plantilla de precios, intenta aplicar las siguientes soluciones:
+
+### Plantilla modelo
+
+Las plantillas creadas independientemente por los clientes o personalizadas después de exportarlas del Admin VTEX pueden generar errores de integración durante la importación.
+
+Para evitar este escenario, utiliza únicamente las plantillas modelo disponibles (de precio base o precio fijo) sin realizar ninguna personalización. Consulta más información en [Exportación de precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#exportacion-de-precios).
+
+### Datos rellenados
+
+Las plantillas rellenadas con datos incorrectos pueden generar errores durante la importación. Esto puede suceder si, por ejemplo, el ID del producto está ingresado donde correspondería tener el ID del SKU o si [hay una modificación de precio para un SKU](https://help.vtex.com/es/tutorial/alteracion-de-precio-de-sku--tutorials_95#regla-para-alteracion-de-precio) registrado que lo aumente en más de un 70 % o lo disminuya en más de un 30 % en relación con el valor actual.
+
+Comprueba que los campos de tu plantilla estén rellenados según las guías de los siguientes artículos:
+
+- [Plantilla de precios base](https://help.vtex.com/es/tutorial/tabla-de-precios-base--4Jox8TeQ5feqAn78TZ0DNA)
+- [Plantilla de precios fijos](https://help.vtex.com/es/tutorial/rellenar-campos-de-la-plantilla-de-importacion-de-precios-fijos--50RFoH3ruV97FJgeBUCURh)
+
+<div class ="alert alert-warning">
+  Antes de importar la plantilla en el Admin VTEX, comprueba que no contenga columnas con información de errores (<b>Error Code</b> y <b>Error Message</b>) ni que tenga algún tipo de filtro aplicado en las celdas. Si intentas importar una plantilla así, pueden generarse errores en el proceso de importación de datos.
+</div>
+
+Ejemplo de plantilla con filtros aplicados y con los campos __Error Code__ y __Error Messages__:
+
+![Hoja de precios](//images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/2412a0609e152f55f147e4c05e76e2be/Price_spreadsheet.PNG)
+
+#### Tamaño de archivo
+
+Las plantillas de precios no deben exceder el límite de tamaño máximo de 1 megabyte (1 MB). Si tu plantilla excede el límite de tamaño, divide los datos en plantillas de menos de 1 megabyte (1 MB).
+
+<div class ="alert alert-warning">
+  Todos los datos de un SKU específico deben mantenerse en la misma plantilla. No se permite registrar información del mismo SKU en plantillas diferentes.
+</div>
diff --git a/docs/tutorials/es/i-cant-receive-emails-from-vtex.md b/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
new file mode 100644
index 000000000..334894921
--- /dev/null
+++ b/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
@@ -0,0 +1,98 @@
+---
+title: '¿Por qué no recibo emails de VTEX?'
+id: 4M2uVZdtrJzgyAySuZ4OLg
+status: PUBLISHED
+createdAt: 2024-05-28T17:21:01.400Z
+updatedAt: 2024-06-10T18:28:15.898Z
+publishedAt: 2024-06-10T18:28:15.898Z
+firstPublishedAt: 2024-05-29T13:14:04.884Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: por-que-no-recibo-emails-de-vtex
+locale: es
+legacySlug: por-que-no-recibo-emails-de-vtex
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras clave__: *centro de mensajes, configuración de la tienda, plantillas de emails, exportación de datos, logs de errores, importación de plantillas, token de autenticación.*
+
+A través del [Centro de mensajes](https://help.vtex.com/es/tutorial/como-funciona-el-message-center--tutorials_84), VTEX ofrece a los retailers la opción de personalizar las plantillas para enviar emails a los usuarios. Estos emails pueden utilizarse para transmitir la siguiente información:
+- Token de autenticación en la tienda
+-	Notificaciones de creación y pago de pedidos
+- Confirmación de exportación de datos
+- Logs de errores de importación de plantillas
+
+Si detectas que los emails de tu tienda no se están enviando de la manera adecuada, perjudicando la transmisión de información importante a tus clientes, aquí tienes algunas posibles soluciones para identificar el origen de este problema.
+
+## Solución
+
+Para corregir interrupciones en el envío de emails de VTEX, consulta las siguientes soluciones:
+
+- [Verificar remitente](#verificar-remitente)
+- [Configurar servidor de correo](#configurar-servidor-de-correo)
+- [Configurar notificaciones de pedidos y pagos](#configurar-notificaciones-de-pedidos-y-pagos)
+- [Remover email de la lista de supresión de AWS](#lista-de-supresion-de-aws)
+
+### Verificar remitente
+
+Si tu tienda posee un remitente personalizado, además del remitente predeterminado __VTEX-DEFAULT__, realiza una prueba de envío de mensajes siguiendo los pasos que se indican a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Plantillas de email > Remitentes__.
+2. En la casilla con el nombre de tu remitente registrado, haz clic en __Test-again__. Al cabo de unos segundos se mostrará un mensaje de confirmación de email enviado.
+3. Comprueba que se envió un email de VTEX a la dirección del usuario con sesión iniciada en el Admin.
+4. Si no recibiste el email de VTEX, consulta la solución a continuación.
+
+### Configurar servidor de correo
+
+En VTEX puede utilizarse el servidor de correo nativo o [configurar un servidor SMTP externo](https://help.vtex.com/es/tutorial/personalizando-o-smtp-da-vtex--tutorials_2733). Si utilizas un servidor SMTP externo, comprueba los escenarios que se indican a continuación.
+
+#### Configurar SMTP en el Admin VTEX
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Plantillas de email > Remitentes__.
+2. Haz clic en el nombre de tu remitente registrado.
+3. En __EDIT_PROVIDER_SMTP_DATA__, verifica que todos los datos estén correctos.
+4. Haz clic en `Save`.
+5. En la tarjeta con el nombre de tu remitente registrado, haz clic en `Test-again`. Al cabo de unos segundos se mostrará un mensaje de confirmación de email enviado.
+6. Comprueba que se envió un email de VTEX a la dirección del usuario con sesión iniciada en el Admin.
+
+Después de la prueba, si el usuario que inició sesión en el Admin no recibió el email enviado por VTEX, te recomendamos que utilices el remitente de VTEX (__VTEX-DEFAULT__) como predeterminado y vuelvas a realizar la prueba nuevamente. Si tras repetir el procedimiento no recibiste el email de VTEX, consulta la solución a continuación.
+
+#### Configurar SPF (Sender Policy Framework)
+
+Comprueba que el servidor SMTP externo está correctamente configurado según el [sistema SPF](https://help.vtex.com/es/tutorial/configurar-spf--42t0lkl2VyC6Yewc4wA6wI), que se encarga de impedir que servidores no autorizados envíen emails en nombre de un dominio concreto. Si es necesario, puedes realizar la [configuración del SPF (Sender Policy Framework)](https://developers.vtex.com/docs/guides/setting-up-the-spf) y el [DKIM](https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails) (DomainKeys Identified Mail) en el servidor.
+
+<div class ="alert alert-warning">
+Comprueba que los emails no estén en la carpeta de spam. A veces caen en esta carpeta debido a reglas internas de los servidores de correo.
+</div>
+
+### Configurar notificaciones de pedidos y pagos
+
+VTEX envía emails a los usuarios cuando se crea un pedido o se efectúa un pago. Sigue los pasos que se indican a continuación para comprobar la configuración de las notificaciones de pagos:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__.
+2. Haz clic en la pestaña __Notificaciones__.
+3. Asegúrate de que tu email figura en el campo correspondiente a la opción __Mi email VTEX__. Si lo deseas, ingresa un email secundario en el campo __Otro email__ y realiza el envío del mensaje de prueba como se explica en la sección [Verificar remitente](#verificar-remitente).
+4. Comprueba que se envió un email de VTEX a la dirección de email del usuario con sesión iniciada en el Admin.
+5. Si no recibiste el email de VTEX, consulta la solución a continuación.
+
+### Lista de supresión de AWS
+
+Amazon (AWS) tiene una plataforma de email llamada Amazon Simple Email Service ([Amazon SES](https://aws.amazon.com/pt/ses/)). Entre las diversas características de este servicio, existe una lista de supresión de direcciones de email que contiene destinatarios que pueden haber mostrado algún tipo de comportamiento sospechoso que hayan afectado a un cliente de AWS.
+
+En situaciones normales, una dirección de email puede ser incluida en la lista de supresión de AWS y ser removida transcurridas aproximadamente 12 horas. Durante este periodo, los emails enviados por VTEX no se recibirán en la dirección de email incluida en la lista.
+
+<div class ="alert alert-warning">
+La gestión de la lista de supresión es responsabilidad de AWS, y VTEX no tiene ninguna responsabilidad sobre el movimiento de direcciones dentro y fuera de la lista.
+</div>
+
+Si sospechas que tu dirección de email ha sido bloqueada por AWS, espera 12 horas e intenta volver a enviar un email a la dirección bloqueada.
+
+También puedes comprobar si la dirección de email está registrada como copia en alguna de las plantillas de emails transaccionales de la tienda. Para comprobarlo, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Plantillas de email > Plantillas__.
+2. Haz clic en la tarjeta de la plantilla deseada.
+3. Comprueba que en los campos __CC:__ o __CCO:__ de la plantilla no figura ninguna dirección de email. En caso contrario, elimina la información y haz clic en `Save`.
+4. Realiza este procedimiento con cada una de las plantillas de la tienda y haz una prueba de envío de email a la dirección deseada.
+
+![copia_email_es](//images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/a31ab802e560774fa1ef533d50dffd88/copia_email_es.png)
diff --git a/docs/tutorials/es/i-cant-update-the-ean-of-my-skus-via-api.md b/docs/tutorials/es/i-cant-update-the-ean-of-my-skus-via-api.md
new file mode 100644
index 000000000..0f8444586
--- /dev/null
+++ b/docs/tutorials/es/i-cant-update-the-ean-of-my-skus-via-api.md
@@ -0,0 +1,50 @@
+---
+title: 'No logro actualizar el EAN de mis SKU vía API'
+id: 1gHfGo3TpSTHqb5ZNzwq3m
+status: PUBLISHED
+createdAt: 2024-06-18T16:50:42.770Z
+updatedAt: 2024-06-18T17:29:20.394Z
+publishedAt: 2024-06-18T17:29:20.394Z
+firstPublishedAt: 2024-06-18T17:28:22.909Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: no-logro-actualizar-el-ean-de-mis-sku-via-api
+locale: es
+legacySlug: no-logro-actualizar-el-ean-de-mis-sku-via-api
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags de producto:** Catálogo
+
+**Palabras clave:** SKU, producto, EAN, catálogo
+
+Al intentar actualizar el EAN (número de artículo europeo), que contiene información del código de barras de un SKU en el Admin VTEX y en la API, podrías encontrar problemas de sincronización del catálogo de la tienda, lo que afectaría la gestión del stock y la experiencia del cliente.
+
+## Solución
+
+Para resolver este problema, considera [eliminar el EAN del SKU](#eliminar-ean-del-sku) para luego [agregar un nuevo EAN](#etapa-1-agregar-nuevo-ean-al-sku).
+
+### Eliminar EAN del SKU
+
+Para actualizar el EAN del SKU actual, primero debes eliminar todos los EAN asociados al SKU. 
+
+- [Delete SKU EAN](https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/stockkeepingunit/-skuId-/ean/-ean-): utiliza el endpoint para eliminar un EAN específico.
+- [Delete all SKU EAN values](https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/stockkeepingunit/-skuId-/ean): utiliza el endpoint para eliminar todos los EAN asociados al SKU.
+
+#### Etapa 1: agregar nuevo EAN al SKU
+
+Solamente después de eliminar los EAN de un SKU será posible agregar un nuevo EAN. Para hacerlo, utiliza el endpoint [Create SKU EAN](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/ean/-ean-) para crear el nuevo valor de EAN.
+
+#### Etapa 2: consultar la actualización del EAN del SKU
+
+Una vez que se haya agregado el nuevo valor de EAN, utiliza el endpoint [Get SKU by EAN](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/sku/stockkeepingunitbyean/-ean-) para comprobar la actualización. Los nuevos valores de EAN se mostrarán en el arreglo `AlternateIdValues`.
+
+```json
+"AlternateIdValues":
+[
+"8781",
+"878181"
+]
+```
+
diff --git a/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
new file mode 100644
index 000000000..3fc1fbc8f
--- /dev/null
+++ b/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
@@ -0,0 +1,240 @@
+---
+title: 'El producto no se muestra en la búsqueda del sitio web'
+id: 2Ry55Fh6JW8v7oKBiB2pH3
+status: PUBLISHED
+createdAt: 2024-07-24T16:39:50.379Z
+updatedAt: 2024-07-25T15:47:00.673Z
+publishedAt: 2024-07-25T15:47:00.673Z
+firstPublishedAt: 2024-07-24T18:55:15.925Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: el-producto-no-se-muestra-en-la-busqueda-del-sitio-web
+locale: es
+legacySlug: nao-consigo-visualizar-o-produto-na-busca-do-site
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras clave__: *producto, búsqueda, catálogo, intelligent search, apps, rewriter, graphql, vtex io, redirect.*
+
+Cuando el usuario realiza una búsqueda en una tienda VTEX utilizando [Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG), es posible que no se muestre el producto deseado, aunque el término utilizado en la búsqueda esté presente en la información registrada del ítem.
+
+Ejemplo: al buscar en el sitio web de la tienda productos que contengan el término "Pendleton", los resultados de la búsqueda muestran 6 productos. Sin embargo, cuando accedemos al Admin VTEX (__Storefront > Intelligent Search > Explicación de la búsqueda__) e ingresamos el mismo término, se muestran 9 productos.
+
+![Filter_1](//images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/fd5b87b16752fbec8cfaec8258bf22d4/Filter_1.png)
+
+![Filter_2](//images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/d06e5b6d2114ea99424449d66eb3b887/Filter_2.png)
+
+Este comportamiento puede ocurrir debido a los siguientes escenarios:
+
+1. Registro incorrecto del producto en el catálogo.
+
+2. El término utilizado no está presente en uno de los campos buscables del producto. Más información en [Configuración del comportamiento de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/23mytRDsEduqLO0Lo7yufy#configuracion-del-comportamiento-de-la-busqueda) y [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx).
+
+3. Rota interna redirecionando o resultado da pesquisa para uma página de marca (brand).
+
+## Soluciones
+
+Para que los productos buscados se muestren correctamente en los resultados de búsqueda del sitio web, consulta las siguientes soluciones:
+
+- [Verificar campos de registro del producto](#verificar-campos-de-registro-del-producto)
+- [Modificar filtro de búsqueda en Rewriter](#modificar-filtro-de-busqueda-en-rewriter)
+- [Remover ruta interna de búsqueda en Rewriter](#remover-ruta-interna-de-busqueda-en-rewriter)
+
+### Verificar campos de registro del producto
+
+La ausencia del producto en un resultado de búsqueda puede atribuirse a que algunos campos se rellenaron incorrectamente durante el proceso de [registro del producto](https://help.vtex.com/es/tutorial/campos-de-registro-de-producto--4dYXWIK3zyS8IceKkQseke). Sigue los pasos a continuación para comprobar los campos __Marca__, __Mostrar en el sitio web__ y __Mostrar producto agotado__:
+
+<blockquote><ui>1. En el Admin VTEX, accede a </b>Catálogo > Todos los productos</b>.</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Las tiendas que utilizan la página <b>Productos y SKUs (beta)</b> deben verificar los campos de registro de productos accediendo a <b>Catálogo >  Productos y SKUs</b> en el Admin VTEX. Más información en <a href="https://help.vtex.com/es/tutorial/productos-y-skus-beta--2ig7TmROlirWirZjFWZ3By">Productos y SKUs (beta)</a>.
+</div></blockquote>
+
+<blockquote><ui>2. Haz clic en sobre el producto que deseas <b>EDITAR</b>.</ui>
+
+<blockquote><ui>3. Comprueba que la información contenida en el campo <b>Marca</b> es correcta. Si es necesario, agrega la marca del producto. Solo se pueden agregar marcas que hayan sido previamente <a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7lEGOSpAlQJCs5eUc5XFmR">registradas en la tienda</a>.</ui>
+
+<blockquote><ui>4. Confirma que la casilla correspondiente a la opción <b>Mostrar en el sitio web</b> está seleccionada.</ui>
+
+<blockquote><ui>5. Confirma que la casilla correspondiente a la opción <b>Mostrar producto agotado</b> está seleccionadao.</ui>
+
+<blockquote><ui>6. Haz clic en <i>Guardar</i>.</ui>
+
+<blockquote><ui>7. Accede al sitio web de la tienda, ingresa el término deseado y verifica que los productos que se muestran en los resultados de la búsqueda coinciden con los productos disponibles en la <b>Explicación de la búsqueda</b> de Intelligent Search (<b>Storefront > Intelligent Search > Explicación de la búsqueda</b>).</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Si el término buscado está presente en el nombre o la descripción del producto, pero el producto pertenece a una marca diferente a la especificada en la búsqueda, procede con los pasos a continuación para solucionar el problema.
+</div></blockquote>
+
+### Modificar filtro de búsqueda en Rewriter
+
+Otro factor que puede contribuir a que un producto no se muestre en un resultado de búsqueda es el comportamiento predeterminado que la aplicación [Rewriter](https://developers.vtex.com/docs/apps/vtex.rewriter) presenta al mostrar productos.
+
+Si un término está registrado en Rewriter como marca, [Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4uSFqyJVCMVMIvVrtz3lxZ) recibirá la información de que dicho término solo debe mostrarse cuando esté asociado a una marca específica.
+
+Para remover la restricción de búsqueda por marca (brand) y permitir que los productos también se muestren en los resultados de la búsqueda si contienen términos presentes en el nombre o la descripción (full text), sigue los pasos que se indican a continuación:
+
+<blockquote><ui>1. En el Admin VTEX, accede a <b>Storefront > Intelligent Search > Explicación de la búsqueda</b> e ingresa el término deseado para comprobar cuántos productos esta búsqueda devuelve.</ui>
+
+<blockquote><ui>2. Configure la aplicación <a href="https://developers.vtex.com/docs/apps/vtex.rewriter">Rewriter</a>. Si la aplicación aún no está instalada en tu tienda, accede a <a href="https://help.vtex.com/es/tracks/hub-de-extensiones--AW7klkYMh557y5IUOgzco/2LDRvGujYsumxi7IlE7CEJ">App Store</a> para instalarla.</ui>
+
+<blockquote><ui>3. En <b>Configuración de la tienda > Storefront</b>, accede a <a href="https://developers.vtex.com/docs/guides/graphql-ide#graphql-basics">GraphQL IDE</a>.</ui>
+
+<blockquote><ui>4. En <b>Selecciona una aplicación</b>, chaz clic en la opción de Rewriter (<b>vtex.rewriter@{app-version-number}</b>).</ui>
+
+![Graphql_ide_es](//images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/2751cf7c83a8d37216f82a532d77c3a7/Graphql_ide_es.png)
+
+<blockquote><ui>5. En el campo de entrada de datos de la consulta (debajo de <b>GraphiQL</b>), ingresa los datos de la función mutación <i>saveInternal</i>.<ui>
+
+```
+mutation saverInternal($route: InternalInput!) {
+internal {
+ save(route: $route) {
+   from
+   declarer
+   type
+   id
+   query
+   endDate
+   binding
+   resolveAs
+   origin
+   disableSitemapEntry
+ }
+}
+}
+```
+
+<blockquote><ui>6. En <b>Query Variables</b>, ingresa la información sobre la ruta. Debes sustituir el valor <i>Pendleton</i> por el término deseado y el valor del campo <i>id</i> por el ID del producto.<ui>
+
+```
+{
+"route": {
+ "from": "/Pendleton",
+ "declarer": "vtex.store@2.x",
+ "type": "fullText",
+ "id": "2000307",
+ "query": {
+     "map": "ft"
+ },
+   "origin": "user-canonical"
+ }
+}
+```
+
+<blockquote><ui><div class ="alert alert-warning">
+  El valor <i>ft</i> (full text) en lugar de <i>b</i> (brand) en el parámetro <i>map</i> indica que los productos en los que el término <i>Pendleton</i> esté presente en el nombre o la descripción también se mostrarán en la búsqueda.
+</div></blockquote>
+
+<blockquote><ui>7. Haz clic en la flecha de IDE de GraphiQL (a la derecha de <b>GraphiQL</b>) para actualizar el filtro de búsqueda. El nuevo valor predeterminado de filtro de búsqueda para el término será confirmado mostrando el siguiente mensaje en el campo de resultados de IDE de GraphiQL.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "save": {
+        "from": "/Pendleton",
+        "declarer": "vtex.store@2.x",
+        "type": "fullText",
+        "id": "2000307",
+        "query": {
+          "map": "ft"
+        },
+        "endDate": null,
+        "binding": "0be568e5-52f5-44f0-9308-3ea701a9f847",
+        "resolveAs": null,
+        "origin": "user-canonical",
+        "disableSitemapEntry": null
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>8. Accede al sitio web de la tienda, ingresa el término deseado y verifica que los productos que se muestran en los resultados de la búsqueda coinciden con los productos disponibles en la <b>Explicación de la búsqueda</b> de Intelligent Search (<b>Storefront > Intelligent Search > Explicación de la búsqueda</b>).</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Si el término de búsqueda está relacionado con una marca que ya no existe en su sitio web, deberá eliminar la ruta de búsqueda interna dentro de la aplicación Rewriter como se describe en la solución a continuación.</div></blockquote>
+
+### Remoção da rota interna de busca no Rewriter
+
+Las [rutas internas](https://developers.vtex.com/docs/guides/vtex-io-documentation-routes#routes-in-rewriter) de búsqueda en la aplicación [Rewriter](https://developers.vtex.com/docs/apps/vtex.rewriter) pueden evitar que un producto se muestre en la búsqueda si se ha registrado con una marca que ya no está disponible en la tienda.
+
+Para volver a mostrar productos que contengan los términos buscados únicamente en el nombre o la descripción es necesario eliminar la ruta de búsqueda correspondiente. 
+
+Para remover una ruta de búsqueda interna del término, sigue los pasos a continuación:
+
+<blockquote><ui>1. En el Admin VTEX, accede a <a href="https://developers.vtex.com/docs/guides/graphql-ide#graphql-basics">GraphQL IDE</a> en <b>Configuración de la tienda > Storefront > IDE de GraphQL</b>.</ui>
+
+<blockquote><ui>2. En <b>Selecciona una aplicación</b>, haz clic en la opción Rewriter (<b>vtex.rewriter@{app-version-number}</b>).</ui>
+
+<blockquote><ui>3. En el campo de entrada de datos de la consulta (debajo de <b>GraphiQL</b>), ingresa los datos de la función <i>internal get</i>, sustituyendo <i>pendleton</i> por el término deseado.</ui> 
+
+```
+{
+  internal {
+    get(path: "/Pendleton") {
+      from
+      resolveAs
+      type
+    }
+  }
+}
+```
+
+<blockquote><ui>4. Haz clic en la flecha de IDE de GraphiQL (a la derecha de <b>GraphiQL</b>) y verifica en el campo de resultados si la ruta interna está descrita como <i>brand</i>.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "get": {
+        "from": "/Pendleton",
+        "resolveAs": "/Pendleton",
+        "type": "brand"
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>5. En el campo de entrada de datos de la consulta (debajo de <b>GraphiQL</b>), ingresa los datos de la función <i>mutation</i>, sustituyendo <i>pendleton</i> por el término deseado.</ui> 
+
+```
+mutation {
+  internal {
+    delete(path: "/Pendleton"){
+      type
+    }
+  }
+}
+```
+
+<blockquote><ui>6. Haz clic en la flecha de IDE de GraphiQL (a la derecha de <b>GraphiQL</b>) para remover la ruta interna de filtro por <i>brand</i> y confirmar que la información a continuación aparece en el campo de resultados de IDE de GraphiQL.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "delete": {
+        "type": "brand"
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>7. Repite los pasos 3 y 4 para confirmar que la ruta interna de redirección del término hacia brand ha sido eliminada. Puedes confirmarlo observando que el campo de resultados en el IDE de GraphQL muestre <i>"get": null</i>.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "get": null
+    }
+  }
+}
+```
+
+<blockquote><ui>8. Accede al sitio web de la tienda, ingresa el término deseado y verifica que los productos que se muestran en los resultados de la búsqueda coinciden con los productos disponibles en la <b>Explicación de la búsqueda</b> de Intelligent Search (<b>Storefront > Intelligent Search > Explicación de la búsqueda</b>).</ui>
diff --git a/docs/tutorials/es/image-compression.md b/docs/tutorials/es/image-compression.md
new file mode 100644
index 000000000..f23430981
--- /dev/null
+++ b/docs/tutorials/es/image-compression.md
@@ -0,0 +1,63 @@
+---
+title: 'Compresión de imágenes'
+id: 4klbgpsPksq44KcwqKeye8
+status: PUBLISHED
+createdAt: 2017-08-17T22:59:59.002Z
+updatedAt: 2024-04-15T14:59:26.688Z
+publishedAt: 2024-04-15T14:59:26.688Z
+firstPublishedAt: 2017-08-17T23:30:18.772Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: compresion-de-imagenes
+locale: es
+legacySlug: como-funciona-la-compactacion-automatica-de-imagenes
+subcategory: 2g6LxtasS4iSeGEqeYUuGW
+---
+
+La compresión de imágenes es un proceso que reduce el tamaño de los archivos de imagen para optimizarlos para la web y garantizar que las imágenes se carguen rápidamente cuando los usuarios navegan por el sitio web.
+
+El objetivo de este proceso es aumentar la velocidad y el desempeño de la tienda, lo que a su vez impacta la experiencia del usuario en[ SEO](https://developers.google.com/search/blog/2010/04/using-site-speed-in-web-search-ranking?hl=es) y tasas de conversión.
+
+Hay dos tipos de compresión de imágenes, que se describen en la siguiente tabla:
+
+| Tipo de compresión | Descripción |
+| - | - |
+| Compresión con pérdida (lossy) | Reduce el tamaño y la calidad de la imagen reteniendo la información más importante. No mantiene todos los píxeles. |
+| Compresión sin pérdida (lossless) | Reescribe el archivo de imagen sin eliminar ninguna información. Aunque mantiene la calidad original, es menos eficaz que la compresión con pérdida a la hora de reducir el archivo. |
+
+En VTEX, los archivos se almacenan en su formato original, pero se comprimen en tiempo real durante la navegación por la tienda.
+
+Realizamos una conversión al formato[ WebP](https://developers.google.com/speed/webp?hl=es-419) siempre que sea más ventajoso, es decir, siempre que el tamaño de la imagen resultante sea menor, independientemente de si el formato es **PNG o **JPG/JPEG.
+
+El uso de WebP puede disminuir el tiempo de carga de páginas entre 1 a 2 segundos, dependiendo del layout. A continuación se describe cómo funciona la optimización de imágenes en cada formato.
+
+<div class="alert alert-info">
+  <p>Los navegadores que todavía no son<a href="https://developers.google.com/speed/webp/faq?hl=es-419#which_web_browsers_natively_support_webp"> compatibles con el formato WebP</a> y los servicios como integraciones y marketplaces siempre reciben imágenes no convertidas, sin importar el formato. Los archivos en formato GIF no se convierten a WebP.</p>
+</div>
+
+## PNG
+
+Para las imágenes en formato PNG, indicado para colores sólidos, gráficos detallados y para alto contraste, la conversión a WebP se realiza con compresión sin pérdida para evitar una degradación de la calidad notable. Las imágenes WebP sin pérdida pueden ser hasta un 26 % más compactas que las imágenes PNG.
+
+Al mismo tiempo, las imágenes PNG se optimizan utilizando[ pngquant](https://pngquant.org/), manteniendo el formato pero reduciendo el tamaño de la imagen hasta un 70 %.
+
+Por último, VTEX entrega el archivo más compacto de entre el WebP sin pérdida y el PNG optimizado, como se ilustra en el siguiente diagrama.
+
+![png-image-compression-es](//images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/ea1861651c0c3576bb865f2c050a3792/png-image-compression-es.PNG)
+
+## JPG/JPEG
+
+Para imágenes en formato **JPG/JPEG**, indicado para fotos, la conversión a WebP se realiza con compresión con pérdida, lo que puede suponer una pérdida en calidad pero garantiza un tamaño optimizado. Las imágenes WebP con pérdida son de un 25 % a un 34 % más compactas que imágenes similares con índice de calidad[ SSIM](https://ece.uwaterloo.ca/~z70wang/research/ssim/) equivalente.
+
+VTEX entrega al cliente la imagen que tenga el tamaño de archivo más pequeño de entre la original y la convertida a WebP sin pérdida, como se ilustra en el siguiente diagrama.
+
+![webp-image-compression-es](//images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/7213c5a45d35166c492201c6e8487d3f/webp-image-compression-es.PNG)
+
+## Artículos relacionados
+
+* [Buenas prácticas para el uso de imágenes en el Catálogo](https://help.vtex.com/es/tutorial/boas-praticas-para-o-uso-de-imagens-no-catalogo--738K2yfq5U86kUI2k4AQIk)
+* [Añadir imagen a la descripción del producto](https://help.vtex.com/es/tutorial/adicionar-imagem-a-descricao-do-produto--2hQGTAAiyUSoISGSyOK8Y4)
+* [Importar imágenes por plantilla](https://help.vtex.com/es/tutorial/importando-imagens-por-planilha--tutorials_262)
+* [¿Cómo actualizar la imagen de un SKU?](https://help.vtex.com/es/tutorial/como-atualizar-a-imagem-de-um-sku--5PMb54FnvUuWOq2qGyAosu)
+* [Reutilización de imágenes con Image Widget](https://help.vtex.com/es/tutorial/image-widget--7pRSVI2xXpQUzjUZj0m4ov)
diff --git a/docs/tutorials/es/image-widget.md b/docs/tutorials/es/image-widget.md
index 81939972f..7f8f09f6e 100644
--- a/docs/tutorials/es/image-widget.md
+++ b/docs/tutorials/es/image-widget.md
@@ -3,8 +3,8 @@ title: 'Reutilización de imágenes con Image Widget'
 id: 7pRSVI2xXpQUzjUZj0m4ov
 status: PUBLISHED
 createdAt: 2021-06-30T18:06:46.531Z
-updatedAt: 2023-03-28T13:24:31.101Z
-publishedAt: 2023-03-28T13:24:31.101Z
+updatedAt: 2024-03-27T14:07:43.190Z
+publishedAt: 2024-03-27T14:07:43.190Z
 firstPublishedAt: 2021-07-02T21:20:16.653Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -41,11 +41,11 @@ Ahora que ya sabe cómo acceder a Image Widget, vea lo que puede hacer a continu
 ### Añadir una imagen
 Después de [acceder a Image Widget](#acceso-a-image-widget) y con él abierto podrá añadir imágenes:
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px">
+<div class="alert alert-warning">
 Al agregar nuevas imágenes en el modal Image Widget usando un <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">development workspace</a>, la configuración realizada se guardará directamente en el espacio de trabajo principal. Es decir, se reflejarán inmediatamente en el modal de tu tienda.
 </div>
 <br>
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px">
+<div class="alert alert-warning">
   El tamaño máximo que admite Image Widget es de 4 MB por archivo.
 </div>
 
@@ -83,7 +83,7 @@ En el bloque en el que desea sustituir una imagen:
 ### Eliminar una imagen
 Para eliminar una imagen del bloque deseado, haga clic en `Más acciones` en la miniatura de la imagen y seleccione __Eliminar.__ Después de este procedimiento, la imagen ya no será visible en el bloque.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px; margin-bottom: 10px">
+<div class="alert alert-warning">
   Cuando se remueve una imagen, no significa que se excluya del repositorio. Para ello, consulte la sección <a href="#funcionalidades-dentro-de-image-widget">Funcionalidades dentro de Image Widget</a>.
 </div>
 
diff --git a/docs/tutorials/es/import-customer-data-brazil.md b/docs/tutorials/es/import-customer-data-brazil.md
index 915a831b8..b875256b5 100644
--- a/docs/tutorials/es/import-customer-data-brazil.md
+++ b/docs/tutorials/es/import-customer-data-brazil.md
@@ -3,8 +3,8 @@ title: 'Importar datos de clientes'
 id: 2zWYVOyj0sISYQmeUwCsI0
 status: PUBLISHED
 createdAt: 2017-06-22T20:55:49.745Z
-updatedAt: 2022-10-17T20:32:21.800Z
-publishedAt: 2022-10-17T20:32:21.800Z
+updatedAt: 2023-10-09T20:34:05.165Z
+publishedAt: 2023-10-09T20:34:05.165Z
 firstPublishedAt: 2017-06-27T14:40:29.106Z
 contentType: tutorial
 productTeam: Master Data
@@ -19,7 +19,7 @@ La importación de datos de clientes debe hacerse en el Master Data. Para el env
 
 <div class="alert alert-danger">
   <p>Este artículo se refiere a los campos del masterdata específicamente para las tiendas de <strong>Brasil</strong>. Debe verificar los valores válidos para diferentes países.</p>
-  <p>Vea también <a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2">importar datos de clientes con la API de Master Data v2</a>.</p>
+  <p>Vea también <a href="https://developers.vtex.com/docs/guides/import-customer-data">importar datos de clientes con la API de Master Data v2</a>.</p>
 </div>
 
 El checkout trabaja con los datos de las entidades CL (cliente) y AD (dirección).
@@ -32,12 +32,12 @@ Las siguientes tablas representan los datos o formatos necesarios para la import
 
 | Nombre del campo | Descripción | Formato |
 |---------------|-----------|---------|
-| firstName | nombre | texto |
-| lastName | apellido | texto |
-| email | email del cliente | email |
-| documentType | Tipo del documento | para Brasil debe ser "cpf" |
+| firstName | Nombre | Texto |
+| lastName | Apellido | Texto |
+| email | Email del cliente | Email |
+| documentType | Tipo del documento | Para Brasil debe ser "cpf" |
 | document | Documento (CPF) | 11 dígitos, sin máscara |
-| homePhone | Teléfono | en el formato "+5511999999999", siendo +55 para el país y seguido por el teléfono con DDD |
+| homePhone | Teléfono | En el formato "+5511999999999", siendo +55 para el país y seguido por el teléfono con DDD |
 
 El campo `id` lo genera el sistema tras la importación, y se usará como `userId` en la importación de la dirección.
 
@@ -47,10 +47,10 @@ Si el cliente es una **persona jurídica**, `document` y `documentType` ya no so
 
 | Nombre del campo | Descripción | Formato |
 |---------------|-----------|---------|
-| isCorporate | define si el cliente es persona jurídica | debe ser "true" |
-| corporateName | razón social | texto |
-| tradeName | nombre fantasía | texto |
-| stateRegistration | inscripción estatal | debe ser "Exento" o texto/alfanumérico |
+| isCorporate | Define si el cliente es persona jurídica | Debe ser "true" |
+| corporateName | Razón social | Texto |
+| tradeName | Nombre fantasía | Texto |
+| stateRegistration | Inscripción estatal | Debe ser "Exento" o texto/alfanumérico |
 | corporateDocument | CNPJ | 14 dígitos, sin máscara |
 
 ### Dirección
@@ -61,19 +61,19 @@ Es obligatorio que los clientes tengan por lo menos una dirección.
 |---------------|-----------|---------|
 | id | ID de la dirección | en blanco |
 | userId | ID del cliente | campo `id`, generado tras importación de clientes |
-| addressName | nombre de la dirección | texto/alfanumérico |
-| addressType | tipo de la dirección | debe ser "residential" o "commercial" |
-| country | país | "BRA" para Brasil |
-| state | estado (UF) | dos letras |
-| city | ciudad | texto |
-| neighborhood | barrio | texto |
+| addressName | Nombre de la dirección | texto/alfanumérico |
+| addressType | Tipo de la dirección | debe ser "residential" o "commercial" |
+| country | País | "BRA" para Brasil |
+| state | Estado (UF) | dos letras |
+| city | Ciudad | texto |
+| neighborhood | Barrio | texto |
 | postalCode | CEP | 8 ó 9 dígitos, con guion |
-| street | dirección | texto |
-| number | número | alfanumérico |
+| street | Dirección | texto |
+| number | Número | alfanumérico |
 | complement | Complemento y referencia | texto |
-| reference | campo no usado | en blanco |
-| receiverName | destinatario | texto |
+| reference | Campo no usado | en blanco |
+| receiverName | Destinatario | texto |
 
 ---
 
-En el caso de que los datos (cliente o dirección) no estén consistentes, incluyndo CPF/CNPJ [RUT] válidos, el checkout no completará los datos del cliente y éste hará la compra como un nuevo usuario.
+En el caso de que los datos (cliente o dirección) no estén consistentes, incluyndo CPF/CNPJ (RUT) válidos, el checkout no completará los datos del cliente y éste hará la compra como un nuevo usuario.
diff --git a/docs/tutorials/es/importing-and-exporting-an-inventory-spreadsheet.md b/docs/tutorials/es/importing-and-exporting-an-inventory-spreadsheet.md
index e7e42ac26..3dd7966ef 100644
--- a/docs/tutorials/es/importing-and-exporting-an-inventory-spreadsheet.md
+++ b/docs/tutorials/es/importing-and-exporting-an-inventory-spreadsheet.md
@@ -3,8 +3,8 @@ title: 'Importar y exportar plantilla de stock'
 id: tutorials_2034
 status: PUBLISHED
 createdAt: 2017-04-27T21:55:43.488Z
-updatedAt: 2023-03-29T14:51:46.368Z
-publishedAt: 2023-03-29T14:51:46.368Z
+updatedAt: 2023-07-24T15:03:49.647Z
+publishedAt: 2023-07-24T15:03:49.647Z
 firstPublishedAt: 2017-04-27T23:03:50.695Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/es/importing-data-into-master-data.md b/docs/tutorials/es/importing-data-into-master-data.md
index c6ed45a1b..349b35869 100644
--- a/docs/tutorials/es/importing-data-into-master-data.md
+++ b/docs/tutorials/es/importing-data-into-master-data.md
@@ -3,8 +3,8 @@ title: 'Importar datos en el Master Data'
 id: tutorials_1135
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:12.437Z
-updatedAt: 2023-03-28T23:29:25.337Z
-publishedAt: 2023-03-28T23:29:25.337Z
+updatedAt: 2023-06-15T19:48:45.566Z
+publishedAt: 2023-06-15T19:48:45.566Z
 firstPublishedAt: 2017-04-27T23:03:43.488Z
 contentType: tutorial
 productTeam: Master Data
@@ -42,9 +42,9 @@ Tras la exportación y edición de la planilla exportada, es hora de realizar la
 Mantenga el mismo formato de la planilla (xls) para realizar la importación con éxito.
 </div>
 
-1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
-2. Haga clic en la pestaña **Aplicações**.
-3. Haga clic en el botón **Modo de Importação**.
+1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
+2. Haga clic en la pestaña **Aplicações.**
+3. Haga clic en el botón **Importar.**
 4. Seleccione la entidad de datos que desea insertar o actualizar registros (Aquí, usted debe insertar la entidad de datos del formulario donde están los registros que desea insertar o actualizar).
 5. Elija el archivo.
 6. Haga clic en el botón **Importar** en la esquina inferior de la pantalla.
diff --git a/docs/tutorials/es/importing-images-from-a-spreadsheet.md b/docs/tutorials/es/importing-images-from-a-spreadsheet.md
index 52e754237..9d65dfff2 100644
--- a/docs/tutorials/es/importing-images-from-a-spreadsheet.md
+++ b/docs/tutorials/es/importing-images-from-a-spreadsheet.md
@@ -3,8 +3,8 @@ title: 'Importar imágenes por plantilla'
 id: tutorials_262
 status: PUBLISHED
 createdAt: 2017-04-27T22:11:24.581Z
-updatedAt: 2023-03-29T17:46:11.384Z
-publishedAt: 2023-03-29T17:46:11.384Z
+updatedAt: 2024-03-04T22:25:58.399Z
+publishedAt: 2024-03-04T22:25:58.399Z
 firstPublishedAt: 2017-04-27T23:03:11.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -22,8 +22,8 @@ Sigue los pasos a continuación para la importación masiva de las imágenes:
 1. En el Admin VTEX, accede a __Catálogo__, o escribe __Catálogo__ en la barra de búsqueda en la parte superior de la página.
 2. Haz clic en **Importación y exportación**.
 3. Haz clic en la pestaña **Importar imágenes**.
-4. Haz clic [aquí](https://docs.google.com/spreadsheets/d/17ItiEncnnioxLZFLiKDTxs5Yj0D6tn-i/edit?usp=sharing&ouid=115538149359194322936&rtpof=true&sd=true) para descargar la plantilla modelo en el formato aceptado por el sistema (.xls). Esto te evitará problemas al momento de importar las imágenes.
-5. Rellena la plantilla según se describe en la sección [Cómo completar la plantilla para importar imágenes](#como-completar-la-plantilla-para-importar-imagenes) y guárdala en tu computadora.
+4. Haz clic [aquí][1] para descargar la plantilla modelo en el formato aceptado por el sistema (.xls). Esto te evitará problemas al momento de importar las imágenes.
+5. Rellena la plantilla según se describe en la sección [Cómo completar la plantilla para importar imágenes][2] y guárdala en tu computadora.
 6. Haz clic en el botón <i class="fas fa-folder-open"></i> `Seleccionar archivo...`.
 7. Busca el archivo guardado en tu computadora y haz clic en `Abrir`.
 8. En el campo **Email para notificación**, ingresa una dirección de email donde recibirás las notificaciones de la importación. Por defecto, el email registrado será el que uses para acceder al Admin VTEX.
@@ -44,12 +44,12 @@ Por último, los productos de las filas de la plantilla cuyas imágenes se proce
 
 A continuación, se explica cómo rellenar cada campo de la plantilla de importación de imágenes:
 
-- [URL](#url)
-- [NomeImagem](#nomeimagem)
-- [TextoImagem](#textoimagem)
-- [Label](#label)
-- [IdSku](#idsku)
-- [CodigoreferenciaSku](#codigoreferenciasku)
+- [URL][3]
+- [NomeImagem][4]
+- [TextoImagem][5]
+- [Label][6]
+- [IdSku][7]
+- [CodigoreferenciaSku][8]
 
 ### URL
 
@@ -57,11 +57,11 @@ A continuación, se explica cómo rellenar cada campo de la plantilla de importa
 <p>Este campo es obligatorio. No está permitido utilizar caracteres especiales, puntos en el nombre de la imagen o tildes.</p>
 </div>
 
-Este campo debe rellenarse con la URL de la imagen que se asociará al SKU, la cual debe ser pública y estar alojada en un servidor FTP desde donde se origina el _link_ de la imagen. La URL debe comenzar, sin excepción, con el identificador de protocolo HTTPS (`https://`) y terminar con la extensión del archivo (`.jpg`, `.png` o `.gif`). Ejemplo: `https://www.exemploimagem.com.br/imagem03/teste01/exemplo15.jpg`.
+Este campo debe rellenarse con la URL de la imagen que se asociará al SKU, la cual debe ser pública y estar alojada en un servidor FTP desde donde se origina el _link_ de la imagen. La URL debe comenzar, sin excepción, con el identificador de protocolo HTTP (`http://`) y terminar con la extensión del archivo (`.jpg`, `.png` o `.gif`). Ejemplo: `http://www.ejemploimage.com.br/imagem03/teste01/exemplo15.jpg`.
 
-Para evitar errores, es importante verificar que la URL de la imagen ingresada en la plantilla esté completa, incluyendo desde `https://` hasta la extensión del archivo. De lo contrario, el sistema no podrá acceder a la URL y la imagen no se importará.
+Para evitar errores, es importante verificar que la URL de la imagen ingresada en la plantilla esté completa, incluyendo desde `http://` hasta la extensión del archivo. De lo contrario, el sistema no podrá acceder a la URL y la imagen no se importará.
 
-No es necesario que cuentes con un servidor FTP propio para enviar las URL de las imágenes. Puedes alojar esos datos en sitios web gratuitos y en servidores FTP externos o internos, siempre que utilicen el protocolo de seguridad HTTPS.
+No es necesario que cuentes con un servidor FTP propio para enviar las URL de las imágenes. Puedes alojar esos datos en sitios web gratuitos y en servidores FTP externos o internos, siempre que utilicen el protocolo de seguridad HTTP.
 
 Además, para verificar si las URL son correctas, puedes usar un servicio externo que verifique su validez.
 
@@ -103,8 +103,18 @@ __Label__ es la «etiqueta» que se usa para facilitar la organización de la pl
 <p>Este campo es obligatorio. El ID informado debe corresponderse con el ID de un SKU ya existente en el Catálogo.</p>
 </div>
 
-El ID del SKU es el código que identifica al SKU que se asociará a la imagen. Este código puede obtenerse exportando **Productos y SKU**. Para más información, consulta el artículo [Cómo exportar plantillas de productos](https://help.vtex.com/es/tutorial/como-exportar-planilla-de-productos--2sIroGeqZqaN3NAvaSGwWV).
+El ID del SKU es el código que identifica al SKU que se asociará a la imagen. Este código puede obtenerse exportando **Productos y SKU**. Para más información, consulta el artículo [Cómo exportar plantillas de productos][9].
 
 ### CodigoreferenciaSku
 
 El código de referencia del SKU es el código que consta en el registro del SKU en el campo **Código de referencia**. Este campo es obligatorio.
+
+[1]: https://docs.google.com/spreadsheets/d/17ItiEncnnioxLZFLiKDTxs5Yj0D6tn-i/edit?usp=sharing&ouid=115538149359194322936&rtpof=true&sd=true
+[2]: #como-completar-la-plantilla-para-importar-imagenes
+[3]: #url
+[4]: #nomeimagem
+[5]: #textoimagem
+[6]: #label
+[7]: #idsku
+[8]: #codigoreferenciasku
+[9]: https://help.vtex.com/es/tutorial/como-exportar-planilla-de-productos--2sIroGeqZqaN3NAvaSGwWV
diff --git a/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md b/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md
index 832ee0d02..1398f1e57 100644
--- a/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md
+++ b/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md
@@ -21,7 +21,7 @@ Las PLP están correlacionadas porque cada producto tiene un enlace a una págin
 
 Para mejorar el rendimiento SEO de las PLP, debes permitir que los rastreadores web, como Google, noten esta conexión entre las PLP. De esta manera, estos rastreadores podrán navegar por diferentes páginas y acceder a los diferentes productos que muestran.
 
-![Button mostrar más](https://images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/8723224ebef9b883e645b3d366e54d48/bt-mostrar-m__s.png)
+![Button mostrar más](//images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/8723224ebef9b883e645b3d366e54d48/bt-mostrar-m__s.png)
 
 Ve a continuación cómo mejorar el rendimiento SEO de las PLP [utilizando el Site Editor](#utilizando-site-editor).
 
@@ -39,7 +39,7 @@ Para mejorar el rendimiento SEO de las PLP a través del Site Editor, debes conf
 4. Haz clic en __Mostrar más.__
 5. En __Comportamiento del botón,__ selecciona la opción __Link a la página - Mejora el SEO, puede cambiar el aspecto del botón.__
 
-![bt-config-es](https://images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/528fc1e6393d25e09346b28e93aedd97/bt-config-es.gif)
+![bt-config-es](//images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/528fc1e6393d25e09346b28e93aedd97/bt-config-es.gif)
 
 6. Haz clic en `GUARDAR`.
 7.  Para configurar el ítem __Mostrar anterior,__ amplíe el bloque Resultado de búsqueda flexible.
diff --git a/docs/tutorials/es/indexes-in-master-data.md b/docs/tutorials/es/indexes-in-master-data.md
new file mode 100644
index 000000000..18affe23a
--- /dev/null
+++ b/docs/tutorials/es/indexes-in-master-data.md
@@ -0,0 +1,87 @@
+---
+title: 'Índices en Master Data'
+id: tutorials_785
+status: PUBLISHED
+createdAt: 2017-04-27T21:58:03.173Z
+updatedAt: 2024-07-17T13:57:12.010Z
+publishedAt: 2024-07-17T13:57:12.010Z
+firstPublishedAt: 2017-04-27T23:03:42.760Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 1malnhMX0vPThsaJaZMYm2
+slug: indices-en-master-data
+locale: es
+legacySlug: configurando-indice-en-el-vtex-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+Un índice en Master Data es una referencia a uno o varios campos, utilizada para optimizar las consultas en una entidad de datos. El uso de índices permite buscar registros con mayor rapidez.
+
+Para ilustrarlo, considera el índice de un libro: muestra los temas contenidos en el libro, así como la página correspondiente donde se desarrolla cada uno. Para realizar una búsqueda eficiente, en lugar de recorrer todas las páginas del libro para encontrar el resultado deseado, puedes consultar el índice y dirigirte directamente al tema que buscas. Del mismo modo, el índice en Master Data proporciona un método más eficaz para encontrar documentos.
+
+## Configurar índice
+
+Sigue los pasos a continuación para definir uno o varios campos como índices en Master Data:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Master Data**.
+2. Haz clic en el ícono de engranaje <i class="fas fa-cog"></i> en la aplicación donde deseas agregar el índice.
+3. Haz clic en **Estructura de datos**.
+4. Haz clic en la pestaña **Índice**.
+5. Haz clic en `Agregar`.
+6. Rellena los campos a continuación:
+
+    * **Nombre:** nombre del índice.
+    * **Valores únicos:** opción para bloquear nuevos registros con valores repetidos para el índice o índices creados. Consulta la sección [Restricción de valores por documento (clave alternativa)](#restriccion-de-valores-por-documento-clave-alternativa) para obtener más detalles.
+    * **Entidad de datos:** nombre de la entidad de datos que contiene los campos que se van a configurar como índices.
+    * **Campos:** nombre de uno o varios campos que se configurarán como índices. Si agregas más de un campo, sepáralos con una coma. Ejemplo: `firstName,document`.
+7. Haz clic en `Guardar`.
+
+## Casos de uso
+
+Aprende más sobre los principales escenarios de uso de índices en Master Data en las secciones a continuación.
+
+### Consultas de hasta mil documentos
+
+Se recomienda el uso de índices para búsquedas con resultados de hasta mil documentos. Si al buscar a través de un índice obtienes más de mil documentos como resultado, puedes optimizar el rendimiento indexando el campo, es decir, [configurándolo como filtro en la entidad de datos](https://help.vtex.com/es/tutorial/filtrando-dados-no-master-data--tutorials_778).
+
+### Restricción de valores por documento (clave alternativa)
+
+La configuración de índices permite bloquear uno o varios campos para evitar registros con valores repetidos. Estos campos actúan como claves alternativas, es decir, valores alternativos para identificar un registro.
+
+La clave alternativa está configurada por el campo **Valores únicos** en la [configuración del índice](#configurar-indice) y funciona de diferentes maneras dependiendo del número de campos insertados en el índice. Consulta las secciones a continuación para saber cómo funciona en cada caso.
+
+#### Un solo campo en el índice
+
+Si solo hay un campo configurado como índice, la clave alternativa evitará que se registre un valor que ya haya sido registrado en ese campo anteriormente.
+
+Por ejemplo, la tabla **Cliente** tiene dos columnas: **ID** y **nombre**. Para facilitar la búsqueda, el campo **Nombre** (`name`) puede configurarse como índice y marcarse como **Valores únicos**, como se ilustra a continuación:
+
+![indices-1-es](//images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/2a87ed75f094011598e43f6b019b9aac/indices-1-es.png)
+
+Como resultado, no será posible ingresar un nombre que ya haya sido registrado en **Cliente**:
+
+![indices-2-es](//images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/d6142ece91ab5f6db03a8e97d7adb57c/indices-2-es.png)
+
+En el ejemplo anterior, como ya existe un registro con el **Nombre** igual a **María**, no es posible registrar otro con el mismo valor.
+
+<div class="alert alert-warning">
+  <p>Utiliza la opción <strong>Valores únicos</strong> con precaución: si deseas permitir que un valor se repita, configurarlo como único hará que el sistema bloquee la inserción de registros duplicados, impidiendo su registro.</p>
+</div>
+
+#### Varios campos en el índice
+
+Si hay más de un campo en el índice, la clave alternativa evitará que un conjunto de valores se repita en los campos seleccionados.
+
+Por ejemplo, considera que la entidad **Cliente** tiene tres campos: **ID**, **Nombre** y **Documento**. En la configuración del índice, en **Campos**, se ingresaron los términos Nombre (`firstName`) y Documento (`document`), como se ilustra a continuación:
+
+![indices-3-es](//images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/bdd2956a7232c41559937286463a9c4b/indices-3-es.png)
+
+En este caso, se puede repetir o el valor del **Nombre** o el valor del **Documento**. Sin embargo, la combinación de ambos valores no puede repetirse; es decir, no puede existir ningún registro con el mismo par (**Nombre** y **Documento**).
+
+![indices-4-es](//images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/3f47ce97a3d99c3109bdcb9d421b036f/indices-4-es.png)
+
+En el ejemplo anterior, ya existe un registro con el **Nombre** igual a **María**. Es posible incluir otro registro con el mismo **Nombre**, siempre que el valor del **Documento** sea diferente.
+
+<div class="alert alert-warning">
+  <p>Si se repite la misma combinación de valores, el registro no se guardará. Utiliza la opción <strong>Valores únicos</strong> solo cuando no haya ninguna posibilidad de que un conjunto de valores se repita en registros diferentes.</p>
+</div>
diff --git a/docs/tutorials/es/indexing-history-beta.md b/docs/tutorials/es/indexing-history-beta.md
index 7a81e1fdb..508022eae 100644
--- a/docs/tutorials/es/indexing-history-beta.md
+++ b/docs/tutorials/es/indexing-history-beta.md
@@ -21,12 +21,12 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 
 El **Historial de indexación** es la página que monitorea el estado de sincronización de todos los productos del catálogo que se envían a Intelligent Search. Allí se puede ver ampliamente el progreso de la indexación de tu tienda.
 
-![Histórico da Indexação 1 - ES](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
 
 La sección **Status de la indexación** muestra la siguiente información:
 
 * **Tiempo promedio de indexación:** tiempo promedio para la indexación de los productos, desde el momento en que el sistema recibió la notificación de un cambio, hasta la actualización en la tienda. El desempeño del tiempo de indexación se mide por un punto verde (saludable) o rojo (no saludable). 
-![Historico Indexação 2 - ES](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
+![Historico Indexação 2 - ES](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
 * **Productos en tienda:** cantidad de productos con información actualizada que se muestran actualmente en la tienda.
 * **División de status de indexación:** porcentaje de productos en cada etapa de indexación. El desempeño de los estados compartidos se mide por un punto verde (saludable) o rojo (no saludable). Las etapas que se muestran son:
     * **Actualizado:** la actualización más reciente del producto que se introdujo en la tienda.
@@ -35,17 +35,17 @@ La sección **Status de la indexación** muestra la siguiente información:
 
 Puedes filtrar la lista de productos indexados para tener una vista personalizada. Cabe destacar que el tiempo medio de indexación y el desglose de los estados se recalcularán en base a los productos filtrados. 
 
-Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="https://images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
+Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
 
-![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
 
 Si filtras por `Status`, puedes seleccionar el estado por el que deseas filtrar: `Actualizado`, `Actualizando`, `Error`.
 
-![Historico indexação 4 - ES](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
+![Historico indexação 4 - ES](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
 
 Si filtras por `Tiempo de indexación`, puedes seleccionar si el intervalo de tiempo `Es mayor que`, `Es igual o mayor que`, `Es menor que` o `Es igual o menor que` un horario definido.
 
-![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
 
 Luego de definir el filtro, haz clic en `Aplicar` para activarlo. 
 
@@ -55,17 +55,17 @@ También puedes filtrar los productos exhibidos en la lista por **ID**, **Últim
 
 Si deseas obtener más información sobre la indexación de un producto específico, puedes hacer clic en la línea del producto en la lista para acceder a una ventana con más detalles, tal como se muestra a continuación.
 
-![Historico indexação 6 - ES](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
+![Historico indexação 6 - ES](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
 
 Además de los datos que se muestran en la lista de productos, también puedes ver:
 
 * **Tiempo de indexación:** registro de cuánto tiempo duró la última actualización del producto, en el formato `hh:mm:ss`.
 * **Cronología de indexación:** registro de cada cambio de estado con fecha y hora. Puedes ver más detalles de cada etapa haciendo clic en el ícono <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - ES](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
+![Historico indexação 7 - ES](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
 
 Puedes reindexar un producto manualmente sin tener que ingresar una actualización en su registro. Para reindexar un producto, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Reintentar la indexación`. Solo se pueden reindexar los productos en el estado **Actualizado**.
 
 Puedes acceder al **Historial de indexación** del producto, una lista con los datos y la hora de cada actualización realizada. De esta manera, puedes llevar un registro de todas las modificaciones que se le hicieron al producto. Para acceder al historial, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Historial`. 
 
-![Histórico da Indexação 8 - ES](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
+![Histórico da Indexação 8 - ES](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
diff --git a/docs/tutorials/es/indexing-history.md b/docs/tutorials/es/indexing-history.md
new file mode 100644
index 000000000..e5ec2141b
--- /dev/null
+++ b/docs/tutorials/es/indexing-history.md
@@ -0,0 +1,67 @@
+---
+title: 'Historial de indexación'
+id: 55SRQ79PXk5lTURF54DRyJ
+status: PUBLISHED
+createdAt: 2024-06-27T16:51:28.631Z
+updatedAt: 2024-06-27T16:52:45.090Z
+publishedAt: 2024-06-27T16:52:45.090Z
+firstPublishedAt: 2024-06-27T16:52:45.090Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: historial-de-indexacion
+locale: es
+legacySlug: historial-de-indexacion
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+El **Historial de indexación** es la página que monitorea el estado de sincronización de todos los productos del catálogo que se envían a Intelligent Search. Allí se puede ver ampliamente el progreso de la indexación de tu tienda.
+
+![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+
+La sección **Status de la indexación** muestra la siguiente información:
+
+* **Tiempo promedio de indexación:** tiempo promedio para la indexación de los productos, desde el momento en que el sistema recibió la notificación de un cambio, hasta la actualización en la tienda. El desempeño del tiempo de indexación se mide por un punto verde (saludable) o rojo (no saludable). 
+![Historico Indexação 2 - ES](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
+* **Productos en tienda:** cantidad de productos con información actualizada que se muestran actualmente en la tienda.
+* **División de status de indexación:** porcentaje de productos en cada etapa de indexación. El desempeño de los estados compartidos se mide por un punto verde (saludable) o rojo (no saludable). Las etapas que se muestran son:
+    * **Actualizado:** la actualización más reciente del producto que se introdujo en la tienda.
+    * **Actualizando:** se está preparando e introduciendo en la tienda la nueva información del producto.
+    * **Error**: indica que hubo un error en la indexación. El producto presenta un problema en el registro, por eso no puede indexarse. Si se trata de un nuevo producto registrado, no estará disponible en la tienda.
+
+Puedes filtrar la lista de productos indexados para tener una vista personalizada. Cabe destacar que el tiempo medio de indexación y el desglose de los estados se recalcularán en base a los productos filtrados. 
+
+Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
+
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
+
+Si filtras por `Status`, puedes seleccionar el estado por el que deseas filtrar: `Actualizado`, `Actualizando`, `Error`.
+
+![Historico indexação 4 - ES](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
+
+Si filtras por `Tiempo de indexación`, puedes seleccionar si el intervalo de tiempo `Es mayor que`, `Es igual o mayor que`, `Es menor que` o `Es igual o menor que` un horario definido.
+
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
+
+Luego de definir el filtro, haz clic en `Aplicar` para activarlo. 
+
+Para agregar un nuevo filtro, haz clic en <i class="fa-solid fa-plus"></i> `Agregar filtro`. Para remover los filtros configurados, haz clic en `Limpiar filtros`.
+
+También puedes filtrar los productos exhibidos en la lista por **ID**, **Última actualización** y **Status**, haciendo clic en la columna deseada. Para encontrar un producto específico en la lista, puedes buscarlo por su ID en la barra de búsqueda.
+
+Si deseas obtener más información sobre la indexación de un producto específico, puedes hacer clic en la línea del producto en la lista para acceder a una ventana con más detalles, tal como se muestra a continuación.
+
+![Historico indexação 6 - ES](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
+
+Además de los datos que se muestran en la lista de productos, también puedes ver:
+
+* **Tiempo de indexación:** registro de cuánto tiempo duró la última actualización del producto, en el formato `hh:mm:ss`.
+* **Cronología de indexación:** registro de cada cambio de estado con fecha y hora. Puedes ver más detalles de cada etapa haciendo clic en el ícono <i class="fa-solid fa-chevron-down"></i>.
+
+![Historico indexação 7 - ES](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
+
+Puedes reindexar un producto manualmente sin tener que ingresar una actualización en su registro. Para reindexar un producto, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Reintentar la indexación`. Solo se pueden reindexar los productos en el estado **Actualizado**.
+
+Puedes acceder al **Historial de indexación** del producto, una lista con los datos y la hora de cada actualización realizada. De esta manera, puedes llevar un registro de todas las modificaciones que se le hicieron al producto. Para acceder al historial, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Historial`. 
+
+![Histórico da Indexação 8 - ES](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
diff --git a/docs/tutorials/es/indexing.md b/docs/tutorials/es/indexing.md
new file mode 100644
index 000000000..eeb602c5b
--- /dev/null
+++ b/docs/tutorials/es/indexing.md
@@ -0,0 +1,26 @@
+---
+title: 'Indexación'
+id: 7J6tepFgD3wohCGEP2PqDB
+status: PUBLISHED
+createdAt: 2024-06-27T16:49:13.712Z
+updatedAt: 2024-06-27T16:50:18.969Z
+publishedAt: 2024-06-27T16:50:18.969Z
+firstPublishedAt: 2024-06-27T16:50:18.969Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: indexacion
+locale: es
+legacySlug: indexacion
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+La indexación es un proceso de sincronía entre los catálogos de la tienda y la búsqueda. Esta funcionalidad permite una actualización continua del índice de productos. Además, ejecuta un tratamiento de datos para utilizarlos en la búsqueda.
+
+Inicialmente, se realiza una sincronización con todos los productos del catálogo VTEX del cliente. Después, el indexador de búsqueda recibirá en tiempo real las futuras actualizaciones de datos, como el nombre y el status del producto.
+
+En este proceso de sincronía, el sistema forma una fila con la información que se ha actualizado para indexarlas en el catálogo de búsqueda. Una vez que se hayan indexado todos los cambios, estarán disponibles en el sitio web.
+
+El proceso de indexación es seguro y cuenta con reglas de recuperación: si un ítem no se indexa en el primer intento, el sistema realiza más intentos. La indexación también es muy importante para analizar, tratar y organizar los datos de la mejor manera para que se muestren en los resultados.
+
+Consulta [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) para ver más información sobre cómo monitorear el proceso de indexación.
diff --git a/docs/tutorials/es/information-about-chile-custom-payments.md b/docs/tutorials/es/information-about-chile-custom-payments.md
index 02f6c73d8..c3af9c0f0 100644
--- a/docs/tutorials/es/information-about-chile-custom-payments.md
+++ b/docs/tutorials/es/information-about-chile-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Información de los pagos personalizados de Chile'
 id: 1cqQ4JInfcOGUwW2aMOoEK
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.205Z
-updatedAt: 2019-12-31T15:26:29.898Z
-publishedAt: 2019-12-31T15:26:29.898Z
+updatedAt: 2024-03-19T12:13:49.935Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:11:20.233Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/information-about-colombia-custom-payments.md b/docs/tutorials/es/information-about-colombia-custom-payments.md
index 93ce7fe7c..be98a7027 100644
--- a/docs/tutorials/es/information-about-colombia-custom-payments.md
+++ b/docs/tutorials/es/information-about-colombia-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Información de los pagos personalizados de Colombia'
 id: 3tcvqc6LBSKOqMWCumwyaq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:36.914Z
-updatedAt: 2019-12-31T15:22:34.694Z
-publishedAt: 2019-12-31T15:22:34.694Z
+updatedAt: 2024-03-19T12:16:11.844Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:11:29.228Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/information-about-uruguay-custom-payments.md b/docs/tutorials/es/information-about-uruguay-custom-payments.md
index bc04cf30d..a3fb836fe 100644
--- a/docs/tutorials/es/information-about-uruguay-custom-payments.md
+++ b/docs/tutorials/es/information-about-uruguay-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Información de los pagos personalizados de Uruguay'
 id: 4cXMr3C5rqIkUkMWgCcWeU
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:36.816Z
-updatedAt: 2019-12-31T15:20:18.360Z
-publishedAt: 2019-12-31T15:20:18.360Z
+updatedAt: 2024-03-19T12:18:07.525Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:06.326Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/inserting-images-into-let-me-know-email.md b/docs/tutorials/es/inserting-images-into-let-me-know-email.md
index 26a9b36f1..135f95116 100644
--- a/docs/tutorials/es/inserting-images-into-let-me-know-email.md
+++ b/docs/tutorials/es/inserting-images-into-let-me-know-email.md
@@ -32,7 +32,7 @@ A continuación, explicamos cómo realizar esta configuración:
 5. Acceda a la caja de __HTML__.      
 6. Introduzca el código de las imágenes que desea insertar.  
 
-  ![Let me know - ES](https:https://images.ctfassets.net/alneenqid6w5/57IqVpUH7SZKkH8sRtlfSf/382e43e26ff37191c644e03babfd02cd/57IqVpUH7SZKkH8sRtlfSf_Imagem_Message_Center_ES.jpg)
+  ![Let me know - ES](https://images.ctfassets.net/alneenqid6w5/57IqVpUH7SZKkH8sRtlfSf/382e43e26ff37191c644e03babfd02cd/57IqVpUH7SZKkH8sRtlfSf_Imagem_Message_Center_ES.jpg)
 
 7. Haga clic en `Guardar`.  
 
diff --git a/docs/tutorials/es/installing-my-orders-through-the-extension-store.md b/docs/tutorials/es/installing-my-orders-through-the-extension-store.md
index bef31cfc9..d2275eee5 100644
--- a/docs/tutorials/es/installing-my-orders-through-the-extension-store.md
+++ b/docs/tutorials/es/installing-my-orders-through-the-extension-store.md
@@ -19,7 +19,7 @@ Acompañando la evolución de la plataforma VTEX, la viewpart de __Mis Pedidos__
 
 Para hacer la instalación, es necesario acceder a la [VTEX App Store.](https://extensions.vtex.com/)
 
-![app store1 ES](https://images.ctfassets.net/alneenqid6w5/2GobyKLKZGwMwUCEG4EK4M/f0c80ce9e43715e0c095ffba7bfe7c86/app_store1_ES.png)
+![app store1 ES](//images.ctfassets.net/alneenqid6w5/2GobyKLKZGwMwUCEG4EK4M/f0c80ce9e43715e0c095ffba7bfe7c86/app_store1_ES.png)
 
 __Al instalar la aplicación, uested ya cuenta con las siguientes actualizaciones:__
 
@@ -29,7 +29,7 @@ __Al instalar la aplicación, uested ya cuenta con las siguientes actualizacione
 - Información de rastreo para varios items.
 - Corrección de pequeños errores.
 
-![app store2 ES](https://images.ctfassets.net/alneenqid6w5/3lD83GV6Y0EAewCOmU2Gc2/c25bdcc4aa23d9389c673e3b9d288115/app_store2_ES.png)
+![app store2 ES](//images.ctfassets.net/alneenqid6w5/3lD83GV6Y0EAewCOmU2Gc2/c25bdcc4aa23d9389c673e3b9d288115/app_store2_ES.png)
 
 Además, con la nueva aplicación usted puede realizar pruebas de versiones y actualizarla cada vez que una nueva versión esté disponible, recibiendo mejoras continuas y actualizaciones de nuevas features.
 
@@ -42,4 +42,4 @@ Para realizar las pruebas de personalización en su página, usted puede trabaja
 5. ¡Listo! Ahora usted ve, antes de subir su página, cómo se comportará.
 6. Para mover My Orders al ambiente en producción (donde sus clientes pueden usarlo), usted debe publicar la modificación. Para ello, simplemente haga clic en el botón __Publicar__.
 
-![app store3 ES](https://images.ctfassets.net/alneenqid6w5/3TusFkUgZOEOEmGQguwSia/a58831055ce0618e0164685ff655cbd1/app_store3_ES.png)
+![app store3 ES](//images.ctfassets.net/alneenqid6w5/3TusFkUgZOEOEmGQguwSia/a58831055ce0618e0164685ff655cbd1/app_store3_ES.png)
diff --git a/docs/tutorials/es/integrating-with-enjoei.md b/docs/tutorials/es/integrating-with-enjoei.md
index f0a40a189..bf978ded3 100644
--- a/docs/tutorials/es/integrating-with-enjoei.md
+++ b/docs/tutorials/es/integrating-with-enjoei.md
@@ -3,8 +3,8 @@ title: 'Integración con Enjoei'
 id: 3mV9uhw1AdqFol8K2tfwly
 status: PUBLISHED
 createdAt: 2021-11-05T19:27:31.160Z
-updatedAt: 2023-03-29T15:54:34.785Z
-publishedAt: 2023-03-29T15:54:34.785Z
+updatedAt: 2024-02-19T20:17:35.239Z
+publishedAt: 2024-02-19T20:17:35.239Z
 firstPublishedAt: 2021-11-05T20:49:41.372Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/integrating-with-madeiramadeira.md b/docs/tutorials/es/integrating-with-madeiramadeira.md
index ad7cfd538..2f2893025 100644
--- a/docs/tutorials/es/integrating-with-madeiramadeira.md
+++ b/docs/tutorials/es/integrating-with-madeiramadeira.md
@@ -3,8 +3,8 @@ title: 'Integración con MadeiraMadeira'
 id: J4QCENKiz4urYNfaMuE0i
 status: PUBLISHED
 createdAt: 2021-11-05T21:04:22.888Z
-updatedAt: 2023-06-07T21:22:36.808Z
-publishedAt: 2023-06-07T21:22:36.808Z
+updatedAt: 2024-02-19T20:17:16.961Z
+publishedAt: 2024-02-19T20:17:16.961Z
 firstPublishedAt: 2021-11-05T21:34:03.556Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/integrating-with-renner-and-camicado.md b/docs/tutorials/es/integrating-with-renner-and-camicado.md
index 76e996b74..bbfbf72b8 100644
--- a/docs/tutorials/es/integrating-with-renner-and-camicado.md
+++ b/docs/tutorials/es/integrating-with-renner-and-camicado.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integración con Renner y Camicado'
 id: 5qf2wloosKlmIB8o2AitnT
-status: CHANGED
+status: PUBLISHED
 createdAt: 2021-07-02T19:25:31.689Z
-updatedAt: 2022-12-15T20:40:16.364Z
-publishedAt: 2022-12-15T20:38:45.121Z
+updatedAt: 2023-08-25T18:50:55.909Z
+publishedAt: 2023-08-25T18:50:55.909Z
 firstPublishedAt: 2021-07-02T21:07:36.096Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md b/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md
index 668571534..8c72655de 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'Guía de integración para marketplaces - Seller non VTEX'
 id: yMji0ow0rQuYgQsg26Kus
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-10-14T21:55:39.633Z
-updatedAt: 2021-08-10T18:51:48.080Z
-publishedAt: 2021-08-10T18:51:48.080Z
+updatedAt: 2023-08-18T19:03:38.625Z
+publishedAt: 
 firstPublishedAt: 2017-10-14T22:00:36.965Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/integration-interfaces.md b/docs/tutorials/es/integration-interfaces.md
index a370c42ef..d1041131b 100644
--- a/docs/tutorials/es/integration-interfaces.md
+++ b/docs/tutorials/es/integration-interfaces.md
@@ -19,7 +19,7 @@ La integración con un ERP le permite realizar el control de stock con relación
 
 En el sistema de VTEX, usted conseguirá realizar las integraciones de su ERP por diferentes Interfaces: __API REST__ (lenguaje en JSON) y __Web Service__ (lenguaje en SOAP - XML) - que está en desuso.
 
-![Interface de integração ES](https://images.ctfassets.net/alneenqid6w5/1qC18Uk3YAIWiesmEco8us/72aaeac0b223b07ab69d2d6df38f2eb2/Interface_de_integra____o.png)
+![Interface de integração ES](//images.ctfassets.net/alneenqid6w5/1qC18Uk3YAIWiesmEco8us/72aaeac0b223b07ab69d2d6df38f2eb2/Interface_de_integra____o.png)
 
 Además del ERP, para que el intercambio de información ocurra, es necesario que exista un sistema para hacer la comunicación entre el ERP y VTEX. Este sistema se llama __Integrador__. Generalmente, el propio ERP desarrolla su integrador, pero también puede ser desarrollado por la propia tienda o por una agencia contratada por la tienda.
 
diff --git a/docs/tutorials/es/integration-with-google-tag-manager.md b/docs/tutorials/es/integration-with-google-tag-manager.md
index f3da5dfa1..f481e3185 100644
--- a/docs/tutorials/es/integration-with-google-tag-manager.md
+++ b/docs/tutorials/es/integration-with-google-tag-manager.md
@@ -3,8 +3,8 @@ title: 'Configurar Google Tag Manager'
 id: frequentlyAskedQuestions_616
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:56.745Z
-updatedAt: 2023-05-12T15:09:43.299Z
-publishedAt: 2023-05-12T15:09:43.299Z
+updatedAt: 2023-07-17T13:33:10.627Z
+publishedAt: 2023-07-17T13:33:10.627Z
 firstPublishedAt: 2019-01-24T22:13:48.493Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
 <div class="alert alert-warning">
-Si su tienda está construida en <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, debe instalar la aplicación de pixel del Google Tag Manager para hacer la integración con todas las páginas. Vea cómo hacerlo en la <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">documentación de la app</a>.
+Si su tienda está construida en <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">Store Framework</a>, debe instalar la aplicación de pixel del Google Tag Manager para hacer la integración con todas las páginas. Vea cómo hacerlo en la <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">documentación de la app</a>.
 </div>
 
 Google Tag Manager es un sistema de gestión de etiquetas creado por Google para gestionar etiquetas JavaScript y HTML utilizadas para seguimiento y análisis de sitios web.
@@ -48,7 +48,7 @@ Después, debes configurar el código de identificación de la tienda en Tag Man
 4. En el campo __Google Tag Manager__, ingresa el código de identificación de la tienda, en el formato `GTM-XXXX`, ilustrado en la imagen siguiente.
 5. Haz clic en `Guardar`.
 
-![Google Tag Manager](https://images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/3689bbdd56348b8bfd8bb9689db86434/Google_Tag_Manager_-_ES.PNG)
+![Google Tag Manager](//images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/3689bbdd56348b8bfd8bb9689db86434/Google_Tag_Manager_-_ES.PNG)
 
 Para verificar eventos (activadores) y variables disponibles en las páginas que se utilizarán en las etiquetas, puedes utilizar el modo de vista previa de Google Tag Manager. Consulta este artículo en [Google Tag Manager](https://support.google.com/tagmanager/answer/6261285?hl=es) para más información.
 
@@ -58,6 +58,6 @@ Puedes utilizar el píxel de Facebook junto al Google Tag Manager de tu tienda p
 
 ## VTEX IO: instalar el píxel de Google Tag Manager
 
-Si tu tienda utiliza [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), además de la configuración, deberás usar una nueva versión de la aplicación Google Tag Manager. Para más información, accede a [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+Si tu tienda utiliza [VTEX IO - Store Framework](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), además de la configuración, deberás usar una nueva versión de la aplicación Google Tag Manager. Para más información, accede a [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
 Esta etapa no es necesaria para las tiendas que utilizan [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
diff --git a/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
index b22166e9a..27f0a7f28 100644
--- a/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
@@ -1,10 +1,10 @@
 ---
-title: 'Sugerencias de sinónimos de Intelligent Search (Beta)'
+title: 'Sinónimos Inteligentes'
 id: 18A9JTCPrMsHWpFntNoKEr
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-06-01T20:18:10.087Z
-updatedAt: 2023-06-01T20:44:40.993Z
-publishedAt: 2023-06-01T20:44:40.993Z
+updatedAt: 2024-04-02T13:08:36.724Z
+publishedAt: 
 firstPublishedAt: 2023-06-01T20:33:35.148Z
 contentType: tutorial
 productTeam: Others
@@ -16,21 +16,25 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
 <div class="alert alert-info">
-  <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>.</p>
-  <p>Para los clientes seleccionados, la funcionalidad está disponible para su uso gratuito en VTEX Admin durante su período Beta, o hasta que lo decida VTEX. Es posible que en el futuro se apliquen tarifas adicionales.</p>
+  <p>Esta funcionalidad está disponible para cuentas que tengan un número mínimo de sesiones y pedidos para que el modelo de Inteligencia Artificial sea entrenado. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>. Pueden aplicarse cargos adicionales en el futuro.</p>
 </div>
 
 La funcionalidad [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) te permite registrar palabras o expresiones con el mismo significado para los términos de búsqueda utilizados por los clientes al realizar búsquedas en tu tienda, lo que aumenta las posibilidades de que obtengan resultados de búsqueda relevantes.
 
-La página **Sinónimos** en el Admin VTEX, además de permitir la configuración manual de sinónimos, te ofrece sugerencias inteligentes de términos para que los registres. La plataforma sugiere sinónimos a partir de inteligencia artificial, basándose en el comportamiento de búsqueda de los clientes en tu tienda.
+Con la funcionalidad Sinónimos Inteligentes, la página **Sinónimos** en el Admin VTEX, además de permitir la configuración manual de sinónimos, te ofrece sugerencias inteligentes de términos para que los registres. La plataforma sugiere sinónimos a partir de inteligencia artificial, basándose en el comportamiento de búsqueda de los clientes en tu tienda.
 
 Para hacerlo, VTEX Intelligent Search contabiliza cuántas veces los clientes, durante los últimos 30 días, buscaron un término que devolvió pocos o ningún resultado de búsqueda, y tuvieron que sustituir el término original por otro. 
 
-> *Ejemplo:* cinco clientes escribieron `jabón para la cara` y luego cambiaron la búsqueda a `jabón facial`. El sistema registra este comportamiento y los términos más reescritos aparecerán como sinónimos sugeridos.
+Ejemplo: cinco clientes escribieron `jabón para la cara` y luego cambiaron la búsqueda a `jabón facial`. El sistema registra este comportamiento y los términos más reescritos aparecerán como sinónimos sugeridos.
 
-Puedes revisar las sugerencias generadas y elegir una de estas tres acciones: rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
+Las sugerencias se muestran en dos categorías en la lista de sinónimos, como se ilustra a continuación:
 
-![syn-sug-es](https://images.ctfassets.net/alneenqid6w5/3bDrkDw6O6d8mHvvBKwWGm/92ab32c06dcfa505720a0813be380cdb/syn-sug-es.png)
+* **Nuevas sugerencias:** son aquellas generadas por la plataforma que aún no se han revisado.
+* **Sugerencias guardadas:** son aquellas que se guardaron para su posterior revisión, tal como se describe en el paso 5 de la sección [Revisar sugerencias](#revisar-sugestoes).
+
+![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
+
+Puedes revisar las sugerencias generadas y elegir guardar para más tarde, rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
 
 ## Revisar sugerencias
 
@@ -38,11 +42,18 @@ Sigue las instrucciones para visualizar las sugerencias de sinónimos y definir
 
 1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda de la parte superior de la página.
 2. En **Intelligent Search**, haz clic en **Sinónimos**.
-    Si hay sugerencias para revisar, aparecerá un modal indicando el número de sugerencias generadas.
-3. Haz clic en `Revisar` para continuar. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
-4. Para revisar la sugerencia, elige una de las siguientes opciones:
+3. Al acceder a la página **Sinónimos**, si hay sugerencias todavía no revisadas, aparecerá un modal indicando el número de sugerencias generadas. Haz clic en `Revisar` para analizarlas.
+
+    Si optas por hacer clic en `Ahora no`, esas sugerencias se mantendrán en la sección **Nuevas sugerencias**, indicando la cantidad de sugerencias generadas. Para revisarlas, haz clic en `Revisar`.
+
+4. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
+
+   ![synonym-suggestion-es](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
+
+4. Para revisar cada sugerencia, elige una de las siguientes opciones:
+    * <i class="fas fa-bookmark"></i> **Guardar para más tarde:** remueve la sugerencia del recuento **Nuevas sugerencias** y la almacena en **Sugerencias guardadas**. Para analizarla posteriormente, haz clic en `Revisar`.
     * <i class="fas fa-times-circle"></i> **Rechazar**: descarta la sugerencia propuesta.
-    * <i class="fas fa-pencil"></i> **Editar**: modifica los campos de la configuración de sinónimos sugeridos. Después de editar, debes hacer clic en <i class="fas fa-check-circle"></i> para guardar los cambios. Para más información sobre los campos disponibles, consulta [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
+    * <i class="fas fa-pencil-alt"></i> **Editar**: modifica los campos de la configuración de sinónimos sugeridos. Después de editar, debes hacer clic en <i class="fas fa-check-circle"></i> para guardar los cambios. Para más información sobre los campos disponibles, consulta [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
     * <i class="fas fa-check-circle"></i> **Aprobar**: aplica y guarda la sugerencia propuesta.
 5. Después de revisar todas las sugerencias, cierra el modal para acceder a la lista de sinónimos configurada en tu tienda.
 
diff --git a/docs/tutorials/es/intelligent-synonyms.md b/docs/tutorials/es/intelligent-synonyms.md
new file mode 100644
index 000000000..ba8f5559f
--- /dev/null
+++ b/docs/tutorials/es/intelligent-synonyms.md
@@ -0,0 +1,68 @@
+---
+title: 'Sinónimos Inteligentes'
+id: 1rR47Kk96UgFYwh8dkDG7i
+status: PUBLISHED
+createdAt: 2024-06-17T13:41:39.402Z
+updatedAt: 2024-06-17T13:42:26.751Z
+publishedAt: 2024-06-17T13:42:26.751Z
+firstPublishedAt: 2024-06-17T13:42:26.751Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: sinonimos-inteligentes
+locale: es
+legacySlug: sinonimos-inteligentes
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad está disponible para cuentas que tengan una cantidad mínima de sesiones y pedidos para que el modelo de inteligencia artificial sea entrenado. Si estás interesado en implementarla, por favor, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>. Es posible que se apliquen tarifas adicionales en el futuro.</p>
+</div>
+
+La funcionalidad [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) te permite registrar palabras o expresiones con el mismo significado para los términos de búsqueda utilizados por los clientes al realizar búsquedas en tu tienda, lo que aumenta las posibilidades de que obtengan resultados de búsqueda relevantes.
+
+Con la funcionalidad Sinónimos Inteligentes, la página **Sinónimos** en el Admin VTEX, además de permitir la configuración manual de sinónimos, te ofrece sugerencias inteligentes de términos para que los registres. La plataforma sugiere sinónimos a partir de inteligencia artificial, basándose en el comportamiento de búsqueda de los clientes en tu tienda.
+
+Para hacerlo, VTEX Intelligent Search contabiliza cuántas veces los clientes, durante los últimos 30 días, buscaron un término que devolvió pocos o ningún resultado de búsqueda, y tuvieron que sustituir el término original por otro. 
+
+Ejemplo: cinco clientes escribieron `jabón para la cara` y luego cambiaron la búsqueda a `jabón facial`. El sistema registra este comportamiento y los términos más reescritos aparecerán como sinónimos sugeridos.
+
+Las sugerencias se muestran en dos categorías en la lista de sinónimos, como se ilustra a continuación:
+
+* **Nuevas sugerencias:** son aquellas generadas por la plataforma que aún no se han revisado.
+* **Sugerencias guardadas:** son aquellas que se guardaron para su posterior revisión, tal como se describe en el paso 5 de la sección [Revisar sugerencias](#revisar-sugestoes).
+
+![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
+
+Puedes revisar las sugerencias generadas y elegir guardar para más tarde, rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
+
+## Revisar sugerencias
+
+Sigue las instrucciones para visualizar las sugerencias de sinónimos y definir si deseas rechazarlas, editarlas o aprobarlas:
+
+1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda de la parte superior de la página.
+2. En **Intelligent Search**, haz clic en **Sinónimos**.
+3. Al acceder a la página **Sinónimos**, si hay sugerencias todavía no revisadas, aparecerá un modal indicando el número de sugerencias generadas. Haz clic en `Revisar` para analizarlas.
+
+    Si optas por hacer clic en `Ahora no`, esas sugerencias se mantendrán en la sección **Nuevas sugerencias**, indicando la cantidad de sugerencias generadas. Para revisarlas, haz clic en `Revisar`.
+
+4. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
+
+   ![synonym-suggestion-es](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
+
+4. Para revisar cada sugerencia, elige una de las siguientes opciones:
+    * <i class="fas fa-bookmark"></i> **Guardar para más tarde:** remueve la sugerencia del recuento **Nuevas sugerencias** y la almacena en **Sugerencias guardadas**. Para analizarla posteriormente, haz clic en `Revisar`.
+    * <i class="fas fa-times-circle"></i> **Rechazar**: descarta la sugerencia propuesta.
+    * <i class="fas fa-pencil-alt"></i> **Editar**: modifica los campos de la configuración de sinónimos sugeridos. Después de editar, debes hacer clic en <i class="fas fa-check-circle"></i> para guardar los cambios. Para más información sobre los campos disponibles, consulta [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
+    * <i class="fas fa-check-circle"></i> **Aprobar**: aplica y guarda la sugerencia propuesta.
+5. Después de revisar todas las sugerencias, cierra el modal para acceder a la lista de sinónimos configurada en tu tienda.
+
+<div class="alert alert-error">
+  <p>Cuando se realiza una acción no es posible deshacerla, ya que se muestra inmediatamente la siguiente sugerencia disponible.</p>
+</div>
+
+## Más información
+
+* [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV)
+* [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL)
+* [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
diff --git a/docs/tutorials/es/interacting-with-masterdata-through-graphql.md b/docs/tutorials/es/interacting-with-masterdata-through-graphql.md
index 73340edaf..4cf4e95c8 100644
--- a/docs/tutorials/es/interacting-with-masterdata-through-graphql.md
+++ b/docs/tutorials/es/interacting-with-masterdata-through-graphql.md
@@ -26,7 +26,7 @@ Comienze asegurándose de tener la versión más reciente de la VTEX CLI y clona
 
 Ejecute el comando `vtex init` y seleccione `graphql get-started`.
 
-![Screen Shot 2019-01-16 at 15.00.29](https://images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
+![Screen Shot 2019-01-16 at 15.00.29](//images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
 
 Vamos a usar su estructura básica y adaptarla a nuestras necesidades.
 
@@ -157,15 +157,15 @@ Abra el Postman y escriba la siguiente búsqueda:
 
 Seleccione un ID y cópielo. Vamos a pegarlo en nuestra consulta.
 
-![Screen Shot 2019-01-16 at 16.14.31](https://images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
+![Screen Shot 2019-01-16 at 16.14.31](//images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
 
-![Screen Shot 2019-01-16 at 17.34.04](https://images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
+![Screen Shot 2019-01-16 at 17.34.04](//images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
 
 Ahora usted debe ver la luz de salida a la derecha.
 Muy bien! Usted realizó su primera consulta simple en tiempo récord.
 
 Volviendo al terminal, usted puede mirar debajo del capó y percibir el GraphQL resolviendo las consultas, como normalmente usted habría hecho.
-![Screen Shot 2019-01-16 at 16.29.03](https://images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
+![Screen Shot 2019-01-16 at 16.29.03](//images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
 
 **Pero ¿y si queremos buscar utilizando todos los filtros posibles?**
 Vamos a seguir adelante para definir una nueva estructura de consulta y crear un nuevo resolver para manejar los nuevos parámetros.
@@ -279,6 +279,6 @@ query{
 
 ```
 
-![Screen Shot 2019-01-16 at 17.23.00](https://images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
+![Screen Shot 2019-01-16 at 17.23.00](//images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
 
 Y esto es todo :) Happy coding!
diff --git a/docs/tutorials/es/interaction-details.md b/docs/tutorials/es/interaction-details.md
index 24f8f3df6..6e950dc45 100644
--- a/docs/tutorials/es/interaction-details.md
+++ b/docs/tutorials/es/interaction-details.md
@@ -1,10 +1,10 @@
 ---
 title: 'Gestión de anuncios: detalles de la interacción'
 id: 5qC6XPkyUsYPd0dqKHQNlf
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T01:16:13.273Z
-updatedAt: 2023-03-31T04:45:50.134Z
-publishedAt: 2023-03-31T04:45:50.134Z
+updatedAt: 2024-06-20T21:43:33.011Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:20:58.901Z
 contentType: tutorial
 productTeam: Channels
@@ -12,9 +12,16 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: detalles-de-la-interaccion
 locale: es
 legacySlug: detalles-del-interaccion
-subcategory: 2zVauFUkYn8vgS0y0MfWeK
+subcategory: 
 ---
 
+<div class="alert alert-info">
+Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
+Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
+ </div>  
+
 La página **Detalles de la interacción** del módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) permite que los sellers visualicen de forma más completa todas las interacciones que ocurren en un anuncio durante su proceso de envío y sincronización con un canal. Detalles de la interacción estarán disponibles durante diez días después del registro.
 
 Para acceder a la página **Detalles de la interacción**:
@@ -33,7 +40,7 @@ La página **Detalles de la interacción** cuenta con las siguientes secciones:
 </div>  
 
 ## Encabezado
-![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/cc97295e6fa0f0d1cfaa76cd755904cb/Interaction_details_ES_cabe__alho.jpg)
+![Interaction details PT cabeçalho](//images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/cc97295e6fa0f0d1cfaa76cd755904cb/Interaction_details_ES_cabe__alho.jpg)
 El *encabezado* contiene la información principal del anuncio para la visualización rápida, como nombre del SKU, logo del canal al que fue enviado, su ID en VTEX e ID en el canal.
 
 ## Resultado de la interacción
@@ -42,23 +49,23 @@ Las interacciones, o actualizaciones de un [anuncio](https://help.vtex.com/es/tu
 El bloque *Resultado de la interacción* informa el efecto que la interacción tuvo sobre el anuncio, calculado a partir de la combinación de registros que forman la interacción. El resultado de una interacción permite que el sistema determine el status del anuncio, indicando si fue posible enviarlo o sincronizarlo al canal, o no. Los resultados de la interacción incluyen:
 
 ### Resultado: Satisfactorio
-![Interaction details PT resultado sucesso](https://images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/35d67af0da667655b5643e3509ccc427/Interaction_details_ES_resultado_sucesso.jpg)
+![Interaction details PT resultado sucesso](//images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/35d67af0da667655b5643e3509ccc427/Interaction_details_ES_resultado_sucesso.jpg)
 El status de una interacción es *Satisfactorio* cuando las interacciones cumplen con su efecto esperado. Eso significa que el anuncio se pudo enviar al canal correctamente, o que las interacciones generaron atualizaciones en un anuncio en términos de precio, stock o catálogo. 
 
 ### Resultado: Falla
-![Interaction details PT resultado falha](https://images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/8af1ee83533f4108433214dc2c3f0964/Interaction_details_ES_resultado_falha.jpg)
+![Interaction details PT resultado falha](//images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/8af1ee83533f4108433214dc2c3f0964/Interaction_details_ES_resultado_falha.jpg)
 El status de una interacción es *Falla* cuando las interacciones no se realizan debido a un error identificado por el sistema. Los resultados de ese tipo acaban generando el status *Con error* en un anuncio, impidiendo que el anuncio se envíe o actualice correctamente en el canal.  En caso de que el resultado de la interacción sea *Falla*, el bloque indica una lista con las fallas detectadas y donde cada una se puede expandir para que el seller acceda a más información sobre lo que ocurrió. 
 
 ### Resultado: Notificación
-![Interaction details PT resultado aviso](https://images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/28e3c2b39fc2740880338efcfb3d2729/Interaction_details_ES_resultado_aviso.jpg)
+![Interaction details PT resultado aviso](//images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/28e3c2b39fc2740880338efcfb3d2729/Interaction_details_ES_resultado_aviso.jpg)
 El status de una interacción es *Notificación* cuando hay interacciones que dan una mayor visibilidad a las etapas que se produjeron en el proceso de envío y actualización de un anuncio, pero que no generaron actualizaciones como tal. 
 
 ### Resultado: Procesando
-![Interaction details PT resultado processing](https://images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/d4f5b881db18ed358e6386c06e4cc2a8/Interaction_details_ES_resultado_processing.jpg)
+![Interaction details PT resultado processing](//images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/d4f5b881db18ed358e6386c06e4cc2a8/Interaction_details_ES_resultado_processing.jpg)
 El status de una interacción es *Procesando* cuando una interacción no fue finalizada y aún debe recibir más acciones. Es un status transitorio, considerando que cuando un evento se cierra, su resultado solo puede ser `satisfactorio`, `falla`, o `notificación`.
 
 ## Línea de tiempo
-![Interaction details ES linha do tempo](https://images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/b95c1753d211144af9336c13bd2002bf/Interaction_details_ES_linha_do_tempo.jpg)
+![Interaction details ES linha do tempo](//images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/b95c1753d211144af9336c13bd2002bf/Interaction_details_ES_linha_do_tempo.jpg)
 El sistema abre una interacción para iniciar una actualización y contiene una serie de registros para realizar las acciones necesarias para que eso suceda. 
 
 La línea de tiempo de la página **Detalles de la interacción** organiza cronológicamente los registros que se producen en cada interacción, e están disponibles para consulta durante diez días. El sistema cierra la interacción cuando cumple su objetivo y no hay más registros por realizar. La línea de tiempo de la interacción muestra los siguientes datos: 
diff --git a/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
index f1e2029db..765226eae 100644
--- a/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
@@ -26,7 +26,7 @@ El siguiente conjunto de datos es presentado en la pantalla de __Todos los pedid
 
 Al lado de cada uno de esos valores, se puede ver un porcentaje que representa la variación relativa a los pedidos de hoy.
 
-![order-metric-es](https://images.ctfassets.net/alneenqid6w5/39O5tZyXnGgEsYccEYcQiS/d790e5a55b8f10f9296ed2dfa8bf2328/order-metric-es.png)
+![order-metric-es](//images.ctfassets.net/alneenqid6w5/39O5tZyXnGgEsYccEYcQiS/d790e5a55b8f10f9296ed2dfa8bf2328/order-metric-es.png)
 
 En el screenshot de las métricas arriba, podemos ver la siguiente información:
 
diff --git a/docs/tutorials/es/introduction-to-vtex-apis.md b/docs/tutorials/es/introduction-to-vtex-apis.md
index 55e145a8f..140463a5d 100644
--- a/docs/tutorials/es/introduction-to-vtex-apis.md
+++ b/docs/tutorials/es/introduction-to-vtex-apis.md
@@ -121,7 +121,7 @@ Ellas quedan divididas por módulo o funcionalidad. Ingresando a uno de éstos,
  
 A la derecha de esas indicaciones, el Postman exhibe, para cada API, un Sample Request. De acuerdo con el lenguaje elegido en la caja de selección por encima de él, el Sample Request muestra cómo sería la aplicación de la solicitud en el código.
 
-![sample request](https://images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
+![sample request](//images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
  
 Para algunas APIs, hay también una Sample Response, que es un ejemplo de respuesta a aquel request.
  
diff --git a/docs/tutorials/es/inventory-data-pipeline-beta.md b/docs/tutorials/es/inventory-data-pipeline-beta.md
new file mode 100644
index 000000000..650b4a3f3
--- /dev/null
+++ b/docs/tutorials/es/inventory-data-pipeline-beta.md
@@ -0,0 +1,95 @@
+---
+title: 'Stock Data Pipeline (Beta)'
+id: 2IvKMZV9SNrE6ipBRQr8h2
+status: PUBLISHED
+createdAt: 2024-02-02T17:41:24.979Z
+updatedAt: 2024-07-29T19:12:57.037Z
+publishedAt: 2024-07-29T19:12:57.037Z
+firstPublishedAt: 2024-05-27T19:26:59.588Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: stock-data-pipeline-beta
+locale: es
+legacySlug: inventario
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+El conjunto de datos compuesto por la tabla `item_inventory` proporciona información sobre la disponibilidad de ítems en stock. Detalla la cantidad total y disponible de ítems, las reservas activas, la posibilidad de stock ilimitado, además de incluir identificaciones de SKU y stock. La tabla también registra actualizaciones con marcas de tiempo e ID de control.  
+
+En esta sección puedes consultar la siguiente información:
+
+- [Características de los datos de stock](#características-de-los-datos-de-stock)
+- [Tabla item_update_latest](#tabla-item-update-latest)
+- [Tabla item_update_historical](#tabla-item-update-historical)
+- [Análisis con item_inventory](#analisis-con-inventory)
+- [Correlaciones con otros datos](#correlaciones-con-otros-datos)
+
+## Características de los datos
+
+| **Característica** | **Descripción** |
+|:---:|:---:|
+| **Origen** | Alimentado por información del  módulo de logística. |
+| **Disponibilidad** | Admin VTEX. |
+| **Historial** | Los datos se conservan durante dos años, a partir de 2024 para clientes que ya utilizan la plataforma VTEX. |
+| **Intervalo mínimo de actualización** | Una hora. |
+
+## Tabla item_update_latest
+
+Estos son los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de columna** | **Descripción de la columna** |
+|:---:|:---:|:---:|
+| __batch_id__ |	character varying(13) |	Identificador utilizado cuando los datos se cargan en la tabla para el control de calidad de la ingestión de datos.|
+| __last_date__ |	timestamp without time | zone	Fecha y hora del último cambio en el inventario.|
+| __item_availabilty_id__| character varying(65535) |	ID del esquema de inventario del SKU. |
+| __item_id__ |	character varying(65535) | Identificador del artículo. |
+|__main_account_name__|	character varying(65535)|	Nombre de la cuenta principal asociada con el artículo.|
+|__account_name__|	character varying(65535)|	Nombre de la cuenta relacionada con el artículo.|
+|__is_unlimited_quantity__|	boolean	| Indicador booleano que indica si un SKU está siempre disponible, independientemente de su cantidad. |
+| __quantity__ | integer | Cantidad de SKU en stock. |
+| __reserved_quantity__ |	integer |	Unidades de SKU reservadas. Los pedidos para estas reservas aún no han sido aprobados para el pago. |
+|__reservation_id__|	character varying(65535) | Identificación de una reserva para ese artículo. |
+
+## Tabla item_update_historical
+
+| **Nombre de la Columna** | **Tipo de Columna** | **Descripción de la Columna** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | Identificador utilizado cuando los datos se cargan en la tabla para el control de calidad de la ingestión de datos. |
+| **created_at** | timestamp without time zone | Fecha y hora del cambio en el inventario. |
+| **item_availabilty_id** | character varying(65535) | ID del esquema de inventario del SKU |
+| **item_id** | character varying(65535) | Identificador del artículo |
+| **main_account_name** | character varying(65535) | Nombre de la cuenta principal asociada con el artículo. |
+| **account_name** | character varying(65535) | Nombre de la cuenta relacionada con el artículo. |
+| **author_id** | character varying(65535) | Autor del cambio en el inventario |
+| **event_type** | character varying(65535) | Tipo de cambio en la disponibilidad (por ejemplo, creación de reserva, cancelación de reserva, actualización de disponibilidad del artículo) |
+| **metadata_created_at** | timestamp without time zone | Hora en que se generó un evento |
+| **is_unlimited_quantity** | boolean | Indicador booleano que indica si un SKU está siempre disponible, independientemente de su cantidad. |
+| **quantity** | integer | Cantidad de SKU en stock |
+| **reserved_quantity** | integer | Unidades de SKU reservadas. Los pedidos para estas reservas aún no han sido aprobados para el pago. |
+| **reservation_id** | character varying(65535) | Identificación de una reserva para ese artículo |
+
+## Análisis con inventory
+
+A continuación se indican algunos de los análisis posibles con la tabla de stock:
+
+- **Análisis de niveles de stock:** evalúa si el stock cubre la demanda e identifica ítems en riesgo de agotarse.  
+- **Tendencias de reserva de stock:** analiza la cantidad de ítems reservados a lo largo del tiempo para identificar patrones y ajustar las estrategias de gestión de stock.  
+- **Análisis de la distribución del stock por cuenta:** optimiza la gestión de stock en varias cuentas para entender cómo se distribuye.  
+
+## Correlaciones con otros datos  
+
+Los datos de stock se correlacionan con los conjuntos de pedidos y productos, y proporcionan análisis más completos para compras, ventas y marketing. Consulta a continuación algunos ejemplos:  
+
+- **Interacción con datos de pedidos:** el análisis conjunto con los datos de pedidos ofrece insights sobre la eficiencia en atender las demandas de los clientes y ayuda a predecir las necesidades de reposición.  
+- **Relación con SKU:** la integración con los datos de SKU ayuda a gestionar el stock en función de la popularidad y disponibilidad de los productos.  
+- **Datos de compras y proveedores:** la coordinación con los datos de compras permite mantener un equilibrio ideal en el stock, evitando los excesos de stock o la escasez.  
+- **Análisis de ventas y marketing:** la comprensión del stock impacta directamente las estrategias de marketing y ventas, alineando promociones y campañas con la disponibilidad de productos.  
+
+### Descubra otros conjuntos de datos
+
+- [Navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Precios](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promociones](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/es/inventory-update-history.md b/docs/tutorials/es/inventory-update-history.md
index c3b3530ab..aafb711a4 100644
--- a/docs/tutorials/es/inventory-update-history.md
+++ b/docs/tutorials/es/inventory-update-history.md
@@ -3,8 +3,8 @@ title: '​​Historial de movimientos del stock'
 id: 5AM7xbmMzmKSEQewakamc2
 status: PUBLISHED
 createdAt: 2017-08-01T15:03:08.876Z
-updatedAt: 2023-03-29T19:59:22.057Z
-publishedAt: 2023-03-29T19:59:22.057Z
+updatedAt: 2024-04-02T18:24:14.768Z
+publishedAt: 2024-04-02T18:24:14.768Z
 firstPublishedAt: 2017-08-01T15:06:58.792Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -31,11 +31,13 @@ Para ver los movimientos de un SKU:
 2. Selecciona el SKU deseado. Para aprender a utilizar los filtros y realizar una búsqueda, consulta el artículo [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139).
 3. En la columna **Última actualización**, haz clic en el número en azul;
 4. Se abrirá la ventana **Registro de actualizaciones** con todos los cambios. Cada fila corresponde a una actualización, y las columnas contienen:
-    * El usuario que realizó el cambio.      
-    * La fecha y hora de la última actualización.
-    * La cantidad de ítems antes y después de la actualización.
+  * El usuario que realizó el cambio.      
+  * La fecha y hora de la última actualización.
+  * La cantidad de ítems antes de la actualización.
+  * La cantidad de ítems después de la actualización.
 
 <div class="alert alert-warning">
 Solo puedes consultar las últimas 50 actualizaciones en el registro de actualizaciones de un determinado SKU.
 </div>
 
+La cantidad total de ítems en la página [Gestión de stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) se actualiza en tiempo real, pero puede haber un retraso de hasta 1 hora para que la información aparezca en el historial de movimientos.
diff --git a/docs/tutorials/es/kit-registration.md b/docs/tutorials/es/kit-registration.md
index 0f6451553..f894bb785 100644
--- a/docs/tutorials/es/kit-registration.md
+++ b/docs/tutorials/es/kit-registration.md
@@ -3,8 +3,8 @@ title: 'Registrar kit'
 id: tutorials_215
 status: PUBLISHED
 createdAt: 2017-04-27T22:13:50.843Z
-updatedAt: 2023-03-29T14:48:43.077Z
-publishedAt: 2023-03-29T14:48:43.077Z
+updatedAt: 2024-05-06T14:40:12.311Z
+publishedAt: 2024-05-06T14:40:12.311Z
 firstPublishedAt: 2017-04-27T23:02:48.663Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -26,7 +26,7 @@ Un kit puede permitir o no que sus componentes se vendan por separado, entienda
 
 Para configurar el Kit es necesario que los productos que harán parte de este – sus componentes – ya estén creados. Como en el siguiente ejemplo:
 
-![01-Componentes ES](https://images.ctfassets.net/alneenqid6w5/1cgf40SaniUaYUIg4wuKyo/0f124e3ab1d1f881f5d0fe225b64d746/01-components_ES.png)
+![01-Componentes ES](//images.ctfassets.net/alneenqid6w5/1cgf40SaniUaYUIg4wuKyo/0f124e3ab1d1f881f5d0fe225b64d746/01-components_ES.png)
 
 Luego de crear los productos componentes, podemos continuar con la configuración del Kit.
 
@@ -38,7 +38,7 @@ Luego de crear los productos componentes, podemos continuar con la configuració
 5. Si quiere un Kit Look, haga clic en la opción __Kit con ítems vendidos por separado__.
 6. Haga clic en `Guardar`.
 
-![02-kit ES](https://images.ctfassets.net/alneenqid6w5/6PUdHiV1UAuMC6A80QYOQI/e14209f28e53d84e8f1af4ecb6261bac/02-kit_ES.png)
+![02-kit ES](//images.ctfassets.net/alneenqid6w5/6PUdHiV1UAuMC6A80QYOQI/e14209f28e53d84e8f1af4ecb6261bac/02-kit_ES.png)
 
 ## Asociar componentes
 
@@ -53,30 +53,26 @@ Después de crear el producto que se convertirá en el Kit, deben asociarse los
 7. Rellene el precio unitario del SKU dentro del Kit.
 6. Haga clic en `Guardar`.
 
-![03-agregar componente al Kit ES](https://images.ctfassets.net/alneenqid6w5/2ghV5EOOAQ4kQOIomsmusE/5f7f3a94ffb0df4b4cdb74f71373445a/03-add_component_to_kit_ES.gif)
+![03-agregar componente al Kit ES](//images.ctfassets.net/alneenqid6w5/2ghV5EOOAQ4kQOIomsmusE/5f7f3a94ffb0df4b4cdb74f71373445a/03-add_component_to_kit_ES.gif)
 
-![04-Kit en el carrito  TODO](https://images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
+![04-Kit en el carrito  TODO](//images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
 
 ## Peso del Kit
 
 El peso del Kit estará conformado por la suma del peso de sus componentes. Editar el peso directamente en la página del Kit no surtirá efectos en la plataforma. La simulación de coste de envío sigue la misma regla.
 
-## Inventario
+## Stock
 
-El inventario del Kit siempre será el inventario de sus componentes. Es decir, no es posible ingresar inventario apenas en el Kit, es necesario que se ingrese inventario en cada uno de sus componentes independientes, a fin de actualizar el inventario del Kit.
+El [stock](https://help.vtex.com/es/tutorial/inventory-management--tutorials_139) del Kit siempre será el inventario de sus componentes. Es decir, no es posible ingresar stock apenas en el Kit, es necesario que se ingrese stock en cada uno de sus componentes independientes, a fin de actualizar el stock del Kit. Esa información es visualizada en tu Admin VTEX en **Catálogo > Stock > Gestión del stock**.
 
-Esa información es visualizada en __Inventario y envío > Inventario__:
+Como todos los SKUs componentes del Kit solo pueden venderse juntos, el stock será igual al SKU con menos ítems en stock. Esto porque no puede comprarse el Kit cuando uno de los componentes ya no tiene stock.  
 
-![05-Administrar inventario por Kit ES](https://images.ctfassets.net/alneenqid6w5/4qlUYLkF1YyaAkQqyQkEKO/25614dccff3abf9ed8c52e06890d2fb9/05-manage_inventory_by_kit_ES.gif)
+Ejemplo: El Kit tiene dos componentes. El componente 1 tiene 30 unidades en stock. El componente 2 tiene 3 unidades en stock. Solo podrán venderse 3 unidades del Kit.
 
-Como todos los SKUs componentes del Kit solo pueden venderse juntos, el inventario será igual al SKU con menos ítems en inventario. Esto porque no puede comprarse el Kit cuando uno de los componentes ya no tiene inventario.  
-
-Ejemplo: El Kit tiene dos componentes. El componente 1 tiene 30 unidades en inventario. El componente 2 tiene 3 unidades en inventario. Solo podrán venderse 3 unidades del Kit.
-
-Los componentes del Kit pueden estar en distintos inventarios, siempre que se envíen desde el mismo muelle. Si no salen por el mismo muelle, todo el Kit deja de estar disponible. 
+Los componentes del Kit pueden estar en distintos stocks, siempre que se envíen desde el mismo muelle. Si no salen por el mismo muelle, todo el Kit deja de estar disponible. 
 
 <div class="alert alert-info">
-<p>Este escenario no ocurre con Kit Look, porque el Kit Look puede venderse con los componentes que quedan en inventario, sin necesidad de tener todos los componentes del Kit con inventario.</p>
+<p>Este escenario no ocurre con Kit Look, porque el Kit Look puede venderse con los componentes que quedan en stock, sin necesidad de tener todos los componentes del Kit con stock.</p>
 </div>
 
 ## Precio
@@ -88,7 +84,7 @@ También podrá modificar únicamente el precio final del Kit directamente desde
 Pero tenga en cuenta que al cambiar cualquier componente se generará un nuevo precio final, actualizando lo que se había registrado anteriormente.
 Alterar solo el precio final no actualiza el precio de los componentes.
 
-![06-Lista de precios ES](https://images.ctfassets.net/alneenqid6w5/4lM2ecWDE40Ooa44scKIq6/6fa14fb364430e3bfc2fa3fff64c8e96/06-price_list_ES.png)
+![06-Lista de precios ES](//images.ctfassets.net/alneenqid6w5/4lM2ecWDE40Ooa44scKIq6/6fa14fb364430e3bfc2fa3fff64c8e96/06-price_list_ES.png)
 
 ### Más información
 
diff --git a/docs/tutorials/es/kr1-test.md b/docs/tutorials/es/kr1-test.md
new file mode 100644
index 000000000..c7a2a82ea
--- /dev/null
+++ b/docs/tutorials/es/kr1-test.md
@@ -0,0 +1,18 @@
+---
+title: 'KR1 - TEST'
+id: 4QvsXwhDJm778DgTsMZmGw
+status: DRAFT
+createdAt: 2024-05-07T02:16:58.777Z
+updatedAt: 2024-05-07T02:22:22.011Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Undefined
+author: 
+slug: kr1-test
+locale: es
+legacySlug: kr1-test
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
new file mode 100644
index 000000000..bf506f653
--- /dev/null
+++ b/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
@@ -0,0 +1,103 @@
+---
+title: 'Lead time: tiempo de envío a nivel de SKU'
+id: 16yv5Mkj6bTyWR1hCN2f4B
+status: PUBLISHED
+createdAt: 2023-09-22T00:32:26.416Z
+updatedAt: 2023-09-22T13:32:38.292Z
+publishedAt: 2023-09-22T13:32:38.292Z
+firstPublishedAt: 2023-09-22T01:35:53.577Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: lead-time-tiempo-de-envio-a-nivel-de-sku
+locale: es
+legacySlug: lead-time-tiempo-de-envio-a-nivel-de-sku
+subcategory: 3PQwnyOcNyYgawy06oe6gE
+---
+
+El lead time es la configuración opcional del tiempo de envío a nivel de SKU. Esto significa que puedes definir un periodo de envío para el SKU de un [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) y este tiempo se agregará al tiempo total de envío del pedido.
+
+La configuración del lead time se realiza en el contexto de la [gestión del stock de tu tienda](https://help.vtex.com/es/tutorial/gerenciar-inventario--tutorials_139), ya que se refiere a ítems en stock y disponibles para la venta.
+
+Este artículo aborda los siguientes aspectos:
+
+- [Tiempo total de envío:](#tiempo-total-de-envio) qué papel juega el lead time en el plazo de envío del pedido.
+- [Principales casos de uso:](#principales-casos-de-uso) contextos en los que la configuración del lead time resulta especialmente útil.
+- [Stock del SKU:](#stock-del-sku) cómo se comporta la plataforma cuando el SKU está o no disponible para la venta.
+- [Configurar lead time:](#configurar-lead-time) cómo realizar la configuración en el Admin VTEX.
+- [Configurar el contaje del lead time en días naturales:](#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional) etapa opcional para que el contaje del lead time sea en días naturales y no en días laborables, que es el valor predeterminado.
+
+<div class = "alert alert-info">
+Para configurar el lead time vía API, accede a <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## Tiempo total de envío
+
+Cuando se configura, el lead time es un tiempo adicional que compone el plazo de envío del pedido que se muestra al cliente en el checkout. En la imagen a continuación, se muestran los elementos que componen el plazo total:
+
+![lead_time_image_total_time_ES](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
+
+* **Lead time:** cantidad de tiempo configurable para el SKU de un almacén. Este periodo puede corresponder al tiempo de procesamiento o fabricación del ítem, por ejemplo. Esta configuración es opcional y se establece en cero días de forma predeterminada.
+* [Tiempo de almacén:](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137) tiempo que tarda el SKU en pasar del almacén al [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Este ajuste es obligatorio, pero puedes configurar el tiempo como cero.
+* [Tiempo de muelle:](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) tiempo que tarda el SKU en salir del muelle, punto intermedio entre el almacén y la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE), para enviarse al cliente. Este ajuste es obligatorio, pero puedes configurar el tiempo como cero.
+* [Política de envío:](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) conjunto de reglas y condiciones que se presentan a los clientes en el checkout, incluyendo:
+    * [Tarifas de envío](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127)
+    * Horario laboral de la transportadora
+    * Ventanas de envío 
+    * Capacidad de entrega
+    * Tipos de productos entregables (modalidades)
+
+## Principales casos de uso
+
+Consulta a continuación algunos casos de uso en los que la configuración del lead time resulta especialmente útil.
+
+### Proveedores externos
+
+Gestiona más fácilmente el tiempo que tarda un proveedor externo, como una fábrica o un fabricante, en producir, procesar, despachar o entregar un producto.
+
+### Productos grandes y personalizables
+
+Para operaciones que venden productos de gran tamaño, como muebles, o productos personalizables, el lead time facilita la gestión del tiempo de procesamiento de los productos, lo que contribuye a una gestión eficaz de almacenes y muelles.
+
+### Dropshipping
+
+En un escenario de _dropshipping_ (cuando el proveedor envía el producto directamente al cliente), configurar el tiempo de envío a nivel de SKU supone tener más flexibilidad para definir plazos de procesamiento y envío del producto por terceros.
+
+## Stock del SKU
+
+La plataforma VTEX presentará comportamientos diferentes dependiendo de si el SKU está o no disponible para la venta. Los escenarios posibles son los siguientes:
+
+- <i class="far fa-check-circle"></i> **SKU en stock:** el administrador de la tienda configura el lead time del SKU; el periodo se considera en el cálculo de envío del pedido, y el plazo total se muestra al cliente en la etapa de checkout.
+- <i class="fas fa-times"></i> **SKU sin stock:** el administrador de la tienda configura el lead time del SKU, pero el SKU no se considera válido porque no hay unidades disponibles para la venta.
+- <i class="far fa-check-circle"></i> **Stock infinito:** el administrador de la tienda configura el lead time del SKU; el periodo se considera en el cálculo de envío del pedido, y el plazo total se muestra al cliente en la etapa de checkout. Si el stock está activado como infinito, el SKU siempre estará disponible para la venta.
+
+## Configurar lead time
+
+El valor predeterminado del lead time es cero, y su límite máximo es 365 días. De manera predeterminada, el contaje se realiza en días laborables, considerando feriados y otras condiciones de tu [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140), pero puedes [configurarlo para que sea en días naturales](#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional).
+
+Para configurar el lead time de un SKU sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Catálogo > Stock > Gestión del stock**, o ingresa **Gestión del stock** en la barra de búsqueda de la parte superior de la página.
+2. Selecciona el SKU que deseas configurar. Puedes utilizar la barra y los filtros de búsqueda.
+3. Ingresa el número de días en la fila del SKU y en la columna **Lead time (días)**.
+  ![lead_time_inventory_management_ES](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
+4. Haz clic en `Guardar` en la parte inferior de la página.
+
+<div class = "alert alert-info">
+En el Admin VTEX, el lead time siempre se configura en días, pero también se pueden configurar periodos en horas, minutos y segundos, utilizando el endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## Configurar el contaje del lead time en días naturales (opcional)
+
+Si deseas que el tiempo del lead time se cuente en días naturales, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, ve a **Envío > Estrategia de envío > Políticas de envío**, o ingresa **Políticas de envío** en la barra de búsqueda de la parte superior de la página.
+2. Busca la política de envío deseada; puedes utilizar la barra de búsqueda y los filtros.
+    > Para crear una nueva política de envío, consulta el artículo [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
+3. En la fila de la política de envío, haz clic en el ícono de tres puntos <i class="fas fa-ellipsis-v"></i> y selecciona `Editar`.
+4. En la sección **Fines de semana y feriados**, activa los botones de alternancia deseados:
+    - <i class="fas fa-toggle-on"></i> **Entrega sábados**
+    - <i class="fas fa-toggle-on"></i> **Entrega domingos**
+    - <i class="fas fa-toggle-on"></i> **Entrega feriados**
+
+5. Haz clic en `Guardar cambios`.
diff --git a/docs/tutorials/es/license-manager-resources.md b/docs/tutorials/es/license-manager-resources.md
index 9eca4d1a1..8bfebb6bf 100644
--- a/docs/tutorials/es/license-manager-resources.md
+++ b/docs/tutorials/es/license-manager-resources.md
@@ -3,8 +3,8 @@ title: 'Recursos del License Manager'
 id: 3q6ztrC8YynQf6rdc6euk3
 status: PUBLISHED
 createdAt: 2022-02-14T17:53:22.572Z
-updatedAt: 2022-08-24T14:51:33.355Z
-publishedAt: 2022-08-24T14:51:33.355Z
+updatedAt: 2024-06-05T13:16:40.276Z
+publishedAt: 2024-06-05T13:16:40.276Z
 firstPublishedAt: 2022-02-14T19:56:27.935Z
 contentType: tutorial
 productTeam: Identity
@@ -15,24 +15,24 @@ legacySlug: recursos-del-license-manager
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-VTEX ofrece varios [roles de usuario predefinidos] (https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) para los usuarios administrativos. Esto permite a los colaboradores de una empresa desempeñar sus funciones accediendo al mínimo de recursos necesarios. Sin embargo, sabemos que cada ecommerce tiene sus propias necesidades y que la flexibilidad es esencial para abordar problemas empresariales específicos.
+VTEX ofrece varios [roles de usuario predefinidos](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) para los usuarios administrativos. Esto permite a los colaboradores de una empresa desempeñar sus funciones accediendo al mínimo de recursos necesarios. Sin embargo, sabemos que cada ecommerce tiene sus propias necesidades y que la flexibilidad es esencial para abordar problemas empresariales específicos.
 
-Por lo tanto, la plataforma VTEX ofrece la posibilidad de crear roles de usuario personalizados, lo que permite elegir con precisión a qué recursos puede acceder un determinado rol personalizado. A continuación, encontrarás links que describen los recursos de VTEX disponibles para cada producto.
+Por lo tanto, la plataforma VTEX ofrece la posibilidad de crear roles de usuario personalizados, lo que permite elegir con precisión a qué recursos puede acceder un determinado rol personalizado. A continuación, encontrarás los recursos de VTEX disponibles para cada producto.
 
 <div class="alert alert-danger">
-El uso sin restricciones de los recursos aumenta el riesgo de ataques a las tiendas por la filtración de credenciales de acceso a los recursos críticos.
-Si tienes alguna duda sobre la descripción de un recurso específico, no dudes en ponerse en contacto con nosotros.
+  <p>El uso sin restricciones de los recursos aumenta el riesgo de ataques a las tiendas por la filtración de credenciales de acceso a los recursos críticos.
+Si tienes alguna duda sobre la descripción de un recurso específico, no dudes en ponerse en contacto con nosotros.</p>
 </div>
 
-<iframe src="https://help.vtex.com/tables/resources/es" title="Recursos del License Manager" frameBorder="0" width="800" height="850"></iframe>
+<iframe src="https://help.vtex.com/tables/resources/es" title="Recursos del License Manager" frameBorder="0" width="100%" height="850"></iframe>
 
 <div class = "alert alert-info">
-En la aplicación <a href="https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a>, los recursos de License Manager son identificados por las respectivas claves.
+  <p>En la aplicación <a href="https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a>, los recursos de License Manager son identificados por las respectivas claves.</p>
 </div>
 
 ## Recursos internos o obsoletos
 
 En la interfaz del License Manager, también encontrarás recursos obsoletos o que son de uso exclusivo interno de VTEX. Estos no tienen ningún impacto en tu tienda. Son:
 
-<iframe src="https://help.vtex.com/tables/internalresources/es" title="Recursos internos o obsoletos" frameBorder="0" width="800" height="700"></iframe>
+<iframe src="https://help.vtex.com/tables/internalresources/es" title="Recursos internos o obsoletos" frameBorder="0" width="100%" height="700"></iframe>
 
diff --git a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
new file mode 100644
index 000000000..c0a026e3c
--- /dev/null
+++ b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -0,0 +1,66 @@
+---
+title: 'Limitar acceso a la tienda por política comercial'
+id: tutorials_3063
+status: PUBLISHED
+createdAt: 2017-04-27T21:52:28.228Z
+updatedAt: 2024-05-24T19:16:43.055Z
+publishedAt: 2024-05-24T19:16:43.055Z
+firstPublishedAt: 2017-04-27T23:03:54.732Z
+contentType: tutorial
+productTeam: Master Data
+author: authors_3
+slug: limitar-acceso-la-politica-comercial-la-tienda
+locale: es
+legacySlug: limitar-acceso-la-politica-comercial-la-tienda
+subcategory: 42hDtnYXHw5ExG6l19RP1l
+---
+
+La limitación en el acceso a una tienda puede ser implementado por diversas razones, como por ejemplo cuando la tienda tiene un sitio B2B que sólo permite a las empresas registradas y autorizadas llevar a cabo la exploración del sitio o cuando es un ambiente para clientes exclusivos, por ejemplo.
+
+Este escenario se puede cumplir mediante el uso de Master Data v1 y la política comercial utilizada en la tienda.
+
+<div class="alert alert-warning">
+Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+ <ul>
+<li>
+<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+Características de las versiones de Master Data
+ </a>
+</li>
+<li>
+<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+Master Data v2
+ </a>
+</li>
+</ul>
+</div>
+
+## Crear cluster de clientes
+
+El primer paso es crear un clúster que la identificación de los clientes que pueden acceder a la tienda. [Para aprender cómo crear un grupo de clientes, visite nuestro manual.](/es/faq/como-crear-un-cluster-de-cliente/)
+
+## Cambiar Política Comercial
+
+Después de crear el clúster, debe crear la regla en la política comercial de manera que sólo los clientes dentro de ese grupo puedan acceder al sitio.
+
+1. En el menú lateral del Admin, haz clic en **Configuración de la tienda** > **Canales** > **Políticas Comerciales**.
+2. En la política comercial utilizada, haga clic en __Cambiar__.
+3. En el campo de la **Regla condicional**, rellene el valor **NombreDelCluster=”true”**. Tenga en cuenta que el valor **NombreDelCluster** debe de ser cambiado por el nombre del campo en la entidad de datos.
+4. Haga click en el botón **Guardar**.
+
+![Catálogo ES](//images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/d748769c9e6b3aa2f001942ed51d6e53/pol__ticas_comerciais_ES.png)
+
+En la configuración anterior, sólo los clientes con el valor verdadero (utilizando un campo booleano - cuando los datos son verdaderos o falsos) tendrán acceso al sitio.
+
+Sin embargo, hay otras opciones de configuración. Se puede configurar, por ejemplo, __NombreDelCluster="false"__ - donde sólo los clientes con valor __false__ en el campo tendrán acceso al sitio o __NombreDelCluster="smith"__ - donde solamente los clientes con un valor Silva en el campo utilizado para el clúster, tendrá acceso al sitio.
+
+## Registrar los clientes que pueden acceder
+
+Para el caso de B2B, donde la tienda no sabe qué clientes pueden acceder, se debe crear una forma en que las empresas registren sus datos. A través del Master Data se comprobará la verificación de datos y se dará acceso o no a la tienda. [Para realizar este ajuste, visite nuestro manual para las tiendas B2B.](/es/tutorial/configurando-b2b-na-vtex/)
+
+## Learn more
+
+- [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete)
+- [Como funciona una Política Comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+- [Crear una política comercial](https://help.vtex.com/es/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE)
+- [Configurar política comercial para marketplace](https://help.vtex.com/es/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)
diff --git a/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md b/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md
index eddeee1ae..526a55412 100644
--- a/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md
+++ b/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md
@@ -19,7 +19,7 @@ Puede configurar uno de los banners de su tienda para un redireccionamiento de p
 
 ## URLs Internas
 
-![url-interna](https://images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3d5a31e246e7525d91009ed3f1e77af1/image5.png)
+![url-interna](//images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3d5a31e246e7525d91009ed3f1e77af1/image5.png)
 
 1. En el Admin VTEX, accede a **Storefront > Site Editor**.
 2. Seleccione el bloque __Carrusel__ deseado y elija el banner cuyo contenido será editado.
@@ -33,7 +33,7 @@ Puede configurar uno de los banners de su tienda para un redireccionamiento de p
 
 ## URLs Externas
 
-![url-externa-es](https://images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/42317522340b78b7ce0a36ef8bb8163d/image3.png)
+![url-externa-es](//images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/42317522340b78b7ce0a36ef8bb8163d/image3.png)
 
 1. En el Admin VTEX, accede a **Storefront > Site Editor**.
 2.  Seleccione el bloque __Carrusel__ deseado y elija el banner cuyo contenido será editado.
diff --git a/docs/tutorials/es/list-of-payment-providers-by-country.md b/docs/tutorials/es/list-of-payment-providers-by-country.md
index f6fe8d7f4..89001d1d7 100644
--- a/docs/tutorials/es/list-of-payment-providers-by-country.md
+++ b/docs/tutorials/es/list-of-payment-providers-by-country.md
@@ -3,8 +3,8 @@ title: 'Lista de Proveedores de Pago por País'
 id: 2im3BEGXxSAcRuxEaIHPvp
 status: PUBLISHED
 createdAt: 2022-02-01T18:37:56.763Z
-updatedAt: 2023-04-17T15:31:26.758Z
-publishedAt: 2023-04-17T15:31:26.758Z
+updatedAt: 2023-11-13T18:15:23.134Z
+publishedAt: 2023-11-13T18:15:23.134Z
 firstPublishedAt: 2022-02-01T18:39:26.915Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: lista-de-proveedores-de-pago-por-pais
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-VTEX ofrece la posibilidad de varios [proveedores de pago](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete) para su negocio en muchos países.
+VTEX ofrece la posibilidad de varios [proveedores de pago](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444) para su negocio en muchos países.
 
 Para identificar las opciones disponibles, ingrese el nombre del país, el proveedor de pago o la disponibilidad de Split de Cobros (Sí/No) en el campo **Search** de la a continuación. También puede optar por mostrar 10, 25, 50 o 100 resultados por página seleccionando el campo **Show Entries**.
 
diff --git a/docs/tutorials/es/loading-dock.md b/docs/tutorials/es/loading-dock.md
index 627e64e9b..98fb5c453 100644
--- a/docs/tutorials/es/loading-dock.md
+++ b/docs/tutorials/es/loading-dock.md
@@ -20,7 +20,7 @@ El muelle forma parte del sistema logístico y representa un punto intermedio en
 
 En VTEX, el muelle es un intermediario entre el almacenamiento de ítems y la entrega de los pedidos de tu negocio. Es a través del muelle que se produce la integración de las partes necesarias para la logística de tu tienda, a saber: el [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb), la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![Doca ES](https://images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/e3f7d64c72c143e395895e7bf2865663/Doca_ES.svg)
+![Doca ES](//images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/e3f7d64c72c143e395895e7bf2865663/Doca_ES.svg)
 
 <div class = "alert alert-info">
 El almacén es el espacio físico de almacenamiento de los productos vendidos por la tienda; la política comercial es la configuración de las estrategias de venta de la tienda; y la política de envío es un conjunto de reglas que definen las opciones y condiciones de envío.
diff --git a/docs/tutorials/es/locations-details-page-beta.md b/docs/tutorials/es/locations-details-page-beta.md
index d8a18d8c2..567180d9c 100644
--- a/docs/tutorials/es/locations-details-page-beta.md
+++ b/docs/tutorials/es/locations-details-page-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Página de detalles de la localidad (Beta)'
 id: 3se4QBRYsNCwC8Wo56J6zG
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-05-09T16:24:38.315Z
-updatedAt: 2023-05-10T00:53:18.368Z
-publishedAt: 2023-05-10T00:53:18.368Z
+updatedAt: 2023-11-10T14:44:21.843Z
+publishedAt: 
 firstPublishedAt: 2023-05-09T20:47:55.824Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/es/logistics-module-overview.md b/docs/tutorials/es/logistics-module-overview.md
index becc1d9d5..bbbd0bc6f 100644
--- a/docs/tutorials/es/logistics-module-overview.md
+++ b/docs/tutorials/es/logistics-module-overview.md
@@ -27,7 +27,7 @@ Aquí podremos registrar la relación de **[Almacén](https://help.vtex.com/es/t
 
 Aquí conseguiremos levantar la definición de valores de precio y tiempo de entrega para una determinada rango de código ZIP con relación al peso cúbico del producto, dimensiones, entre otros factores. 
 
-![tarifas-envioES](https://images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/c390be3b109d17a73293fc3e7b3a9105/tarifas_envioES.png)
+![tarifas-envioES](//images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/c390be3b109d17a73293fc3e7b3a9105/tarifas_envioES.png)
 
 - [Tarifas de envío](https://help.vtex.com/es/tutorial/shipping-rates--1Balpg3rv0854udEPedvMM)
 
@@ -37,35 +37,35 @@ Aquí será posible reproducir diversos escenarios para la entrega del producto,
 
 Éste regresará los valores a los Transportistas que atienden a la entrega, las dimensiones y pesos de los productos, el precio de la entrega y el tiempo estimado para que se lleve a cabo. Además de los detalles adicionales sobre los valores del rango del código ZIP, porcentuales que varían de acuerdo con el rango de peso del Producto, volumen, valores adicionales por gramo excedente, costo para la Muelle, factor cúbico y Peso cubado.
 
-![simulador envioES](https://images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/6cc66af540be3895ae3af7c9c842dde7/simulador_envioES.png)
+![simulador envioES](//images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/6cc66af540be3895ae3af7c9c842dde7/simulador_envioES.png)
 - [Simulador de Envío](/es/tutorial/simulacion-de-flete)
 
 ## Inventario
 
 Aquí es posible gestionar y acompañar el movimiento de inventario realizada en los productos de la Tienda. Tanto cuánto las reservas que el producto posee en aquel momento y si ya fueron confirmadas o no.
 
-![gerenciar inventarioES](https://images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/7e629760904e66633a91146d74539a2c/gerenciar_inventarioES.png)
+![gerenciar inventarioES](//images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/7e629760904e66633a91146d74539a2c/gerenciar_inventarioES.png)
 - [Gestionar Inventario](/es/tutorial/gestionar-items-en-inventario)
 
 ## Envío por Geolocalización
 
 Aquí podremos montar “polígonos” para una atención logística específica, normalmente utilizado en zonas rurales e industriales, donde si hay la división por lotes, por ejemplo, o en áreas de riesgo, se hace necesario excluir determinados lugares dentro de una misma región. Su estructuración es dinámica, puede ser fácilmente y literalmente diseñada en el mapa la región a delimitarse. 
 
-![geolocalizaçaoE](https://images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/9e7f47a52db4e4234728b526cebdda4f/geolocaliza__aoES.png)
+![geolocalizaçaoE](//images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/9e7f47a52db4e4234728b526cebdda4f/geolocaliza__aoES.png)
 - [Geolocalización](/es/tutorial/gestionar-geolocalizacion)
 
 ## Puntos de recogida
 
 En Puntos de recogira es posible eliminar, editar y agregar un *Pickup Point*. La feature de Puntos de Rcogida agrega mayor flexibilidad y mejor experiencia de compra para el cliente al permitirle la retirada del pedido en un punto físico.
 
-![pontos retiradaES](https://images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/87f4cf5a13e62bccf5980e93e4f440ee/pontos_retiradaES.png)
+![pontos retiradaES](//images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/87f4cf5a13e62bccf5980e93e4f440ee/pontos_retiradaES.png)
 - [Configurar Puntos de Recogida](http://help.vtex.com/es/tutorial/configurar-puntos-de-recogida-pickup-points)
 
 ## Festivos
 
 Aquí es posible registrar los días que **no** se considerarán útiles para su tienda. El módulo considerará los días festivos registrados en esta sección y estos días no se contabilizarán en el plazo de entrega.
 
-![feriadoES](https://images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/8de4f976d60f5668a12c8537cff0b9d8/feriadoES.png)
+![feriadoES](//images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/8de4f976d60f5668a12c8537cff0b9d8/feriadoES.png)
 - [Registrar Feriados](http://help.vtex.com/es/tutorial/registrar-feriados)
 
 ## Configuraciones Generales
diff --git a/docs/tutorials/es/making-a-master-data-field-editable.md b/docs/tutorials/es/making-a-master-data-field-editable.md
new file mode 100644
index 000000000..233e7f80c
--- /dev/null
+++ b/docs/tutorials/es/making-a-master-data-field-editable.md
@@ -0,0 +1,31 @@
+---
+title: 'Dejar editable un campo del Master Data'
+id: frequentlyAskedQuestions_3049
+status: PUBLISHED
+createdAt: 2019-01-24T20:46:00.411Z
+updatedAt: 2024-06-11T16:11:17.714Z
+publishedAt: 2024-06-11T16:11:17.714Z
+firstPublishedAt: 2019-01-24T22:15:32.298Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: dejar-editable-un-campo-del-master-data
+locale: es
+legacySlug: como-dejar-editable-un-campo-del-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+Un campo editable es un campo en algún formulario del Master Data en el que es posible editar o insertar información en la edición o creación de un registro. Es decir, es un campo en el que es posible modificar su contenido.
+
+Por estándar, no todos los campos tienen esa configuración en el Master Data y para modificarla sigue los pasos a continuación.
+
+1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
+2. En la aplicación deseada, haga clic en el símbolo de engranaje <i class="fas fa-cog"></i>.
+3. Haga clic en el símbolo de edición <i class="fas fa-edit"></i> sobre el formulario que desea modificar.
+4. Haga clic en la pestaña **Esquemas de layout**.
+5. En el campo deseado, haga clic en el símbolo de edición <i class="fas fa-edit"></i>. ![master-data-modificar-campo-layout](//images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/87a10b5ef1435c74fb86ad88bcf5f54c/Group_1__1_.png)
+6. Desmarque la opción **Mostrar campo como solo lectura**.
+7. Haga clic en el botón `OK`.
+8. Haga clic en el botón `Guardar`.
+
+Los campos modificados estarán disponibles para edición.
diff --git a/docs/tutorials/es/manage-the-sales-comissions-report.md b/docs/tutorials/es/manage-the-sales-comissions-report.md
index 2115d72e8..c42e88dbe 100644
--- a/docs/tutorials/es/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/es/manage-the-sales-comissions-report.md
@@ -63,7 +63,7 @@ La creación del informe puede demorarse si el volumen de datos analizados es ex
 Salir de la página no afectará la operación.
 </div>
 
-![Informe de Comisiones](https://images.ctfassets.net/alneenqid6w5/1VW72vERimVjQn1cXy5TRM/0bcdb6a335b163625ebee90c5b2ea467/image.png)
+![Informe de Comisiones](//images.ctfassets.net/alneenqid6w5/1VW72vERimVjQn1cXy5TRM/0bcdb6a335b163625ebee90c5b2ea467/image.png)
 
 Posteriormente, usted también puede descargar el informe recién generado mediante un link de descarga en el listado de informes.
 
diff --git a/docs/tutorials/es/managing-b2b-organizations.md b/docs/tutorials/es/managing-b2b-organizations.md
new file mode 100644
index 000000000..4670598e8
--- /dev/null
+++ b/docs/tutorials/es/managing-b2b-organizations.md
@@ -0,0 +1,100 @@
+---
+title: 'Gestión de organizaciones B2B'
+id: 1UwNCWhML3BsV6anpoUvVZ
+status: PUBLISHED
+createdAt: 2024-06-12T17:24:48.991Z
+updatedAt: 2024-06-12T17:36:48.744Z
+publishedAt: 2024-06-12T17:36:48.744Z
+firstPublishedAt: 2024-06-12T17:36:48.744Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gestion-de-organizaciones-b2b
+locale: es
+legacySlug: gestion-de-organizaciones-b2b
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+
+La aplicación **B2B Organizations** permite agrupar a los usuarios B2B en organizaciones. Pueden asignarse a cada organización medios de pago específicos, tablas de precios y colecciones de productos, lo que permite que todos los usuarios de la organización compartan las mismas condiciones comerciales. Cada organización está segmentada en uno o varios centros de costos, con sus propias direcciones de envío.
+
+## Acceso a la organización compradora
+
+Accede a la organización compradora desde el Admin VTEX, en **Apps > Organizaciones y Centros de costos B2B > Organizaciones** o ingresa **Organizaciones** en la barra de búsqueda de la parte superior de la página.
+
+Para acceder a la organización, sigue estos pasos:
+
+1. Haz clic en la pestaña **Organizaciones**.
+
+2. Haz clic en el nombre de la organización compradora.
+
+En esta sección se incluye una lista de todas las organizaciones creadas en tu tienda y sus respectivos status, y permite a los administradores de la tienda:
+
+- Agregar nuevas organizaciones.
+
+- Acceder a la página de detalles de la organización, que incluye datos de la organización, centros de costos, colecciones, condiciones de pago, tablas de precios y usuarios.
+
+## Status de las organizaciones
+
+La pestaña **Status de las organizaciones** permite ver y monitorear el status de las solicitudes de registro de las organizaciones.
+
+Puedes utilizar la barra de búsqueda para encontrar una organización por nombre o filtrar las organizaciones por status.
+
+Los status son los siguientes:
+
+- **Activo:** la organización ha sido aprobada por los administradores de la tienda y está actualmente activa.
+
+- **En espera:** la organización está actualmente en pausa, lo que significa que sus usuarios no pueden completar compras en este momento.
+
+- **Inactivo:** la organización ha sido desactivada por los administradores de la tienda, por lo que sus usuarios no podrán iniciar sesión.
+
+![Status- ES](//images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/c3472217083893e427bd505924a3317a/Status-_ES.gif)
+
+## Agregar una nueva organización 
+
+Para agregar una nueva organización accede al Admin VTEX, Apps > Organizaciones y Centros de costos B2B > Organizaciones o ingresa Organizaciones en la barra de búsqueda de la parte superior de la página y sigue los pasos a continuación:
+
+1. Haz clic en la pestaña Organizaciones.
+
+2. Haz clic en el botón `Nuevo` y selecciona la opción Agregar individualmente.
+
+3. Rellena la información requerida sobre la nueva organización:
+    - **Nombre de la organización:** nombre de la organización que deseas crear.
+    - **Nombre del centro de costos:** nombre del centro de costos inicial asociado a la organización.
+    - **País:** país donde se encuentra el centro de costos.
+    - **Código postal:** código postal del centro de costos.
+    - **Dirección:** nombre de la calle donde se ubica el centro de costos.
+    - **Número:** número de la dirección donde se encuentra el centro de costos.
+    - **Información adicional:** información que puede complementar la dirección del centro de costos.
+    - **Barrio:** nombre del barrio donde se ubica el centro de costos.
+    - **Ciudad:** ciudad donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.
+    - **Estado:** estado donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.
+    - **Destinatario:** nombre de la persona que recibirá los pedidos en la dirección informada.
+4. Haz clic en el botón `Agregar`.
+
+![Adiconar organização- ES](//images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/5af4c08cc7df3765ee76eb20a1028e93/Adiconar_organiza__o-_ES.gif)
+
+## Notificaciones por email
+
+La aplicación **B2B Organizations** proporciona un conjunto de plantillas de emails para enviar a los usuarios de la organización, que se activan automáticamente en función de cambios específicos.
+
+| Nombre de la plantilla      | Destinatario                          | Activación                                                     |
+|-----------------------------|---------------------------------------|----------------------------------------------------------------|
+| Organization created        | Usuario con rol de Sales Admin        | Cuando se crea la organización.                                |
+| Organization approved       | Usuario con rol de Organization Admin | Cuando se aprueba la solicitud de creación de la organización. |
+| Organization declined       | Usuario con rol de Organization Admin | Cuando se rechaza la solicitud de creación de la organización. |
+| Organization status changed | Usuario con rol de Organization Admin | Cuando el status de la organización cambia.                    |
+
+Para ver o personalizar cualquiera de estas plantillas, sigue los pasos que se indican a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Plantillas de email > Plantillas**.
+
+2. En la barra de búsqueda, ingresa Organizaciones.
+
+3. Haz clic en el modelo que deseas ver o editar.
+
+4. Realiza los cambios deseados en el modelo.
+
+5. Haz clic en `Guardar`.
+
+Para más información sobre la edición de plantillas de email, consulta nuestro artículo[Crear o editar plantillas de email transaccional](https://help.vtex.com/es/tracks/transactional-emails--6IkJwttMw5T84mlY9RifRP/335JZKUYgvYlGOJgvJYxRO).
diff --git a/docs/tutorials/es/managing-content-versions.md b/docs/tutorials/es/managing-content-versions.md
index 653c11fba..a3c4043a1 100644
--- a/docs/tutorials/es/managing-content-versions.md
+++ b/docs/tutorials/es/managing-content-versions.md
@@ -19,7 +19,7 @@ La versión de un bloque es una copia de su contenido en un momento determinado.
 
 Con el recurso **Versiones**, puedes crear, programar y experimentar con diferentes contenidos para un bloque determinado, sin comprometer la versión publicada de tu tienda. Cada bloque disponible en el Site Editor puede tener varias versiones.
 
-![Activating Versions - Versiones](https://images.ctfassets.net/alneenqid6w5/2W6NS7tRlWMcUdSunI2ifx/72d7fa2f8c892de190e1e2a62f087490/activating-first-es.png)
+![Activating Versions - Versiones](//images.ctfassets.net/alneenqid6w5/2W6NS7tRlWMcUdSunI2ifx/72d7fa2f8c892de190e1e2a62f087490/activating-first-es.png)
 
 Ve en las siguientes secciones cómo:
 
diff --git a/docs/tutorials/es/managing-credit-with-customer-credit.md b/docs/tutorials/es/managing-credit-with-customer-credit.md
index 793e13128..dd54d3402 100644
--- a/docs/tutorials/es/managing-credit-with-customer-credit.md
+++ b/docs/tutorials/es/managing-credit-with-customer-credit.md
@@ -69,11 +69,11 @@ Para un número reducido de registros, el cliente puede crear las cuentas una po
 - Correo electrónico
 - Límite de crédito
 
-![CustomerCredit1-ES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/5i2WziEg0CmHZ1yZGSId6q/88cc7d5c78daa86685773aa3ce28da38/CustomerCredit1-ES.png_h_250_h_250)
+![CustomerCredit1-ES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/5i2WziEg0CmHZ1yZGSId6q/88cc7d5c78daa86685773aa3ce28da38/CustomerCredit1-ES.png_h_250_h_250)
 
 Si, por otro lado, la base tiene un gran número de cuentas, lo más indicado es importar una plantilla en formato CSV. Puede descargar un modelo de este documento en la sección de Cuentas y rellenarlo con la información necesaria. Para esto, haga clic en el botón __Importar__.
 
-![CustomerCredit2-ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/2kPzHCdKHPtdTRISkPpBP5/1d8832a989213974eff370027c655b3c/CustomerCredit2-ES.png_h_250)
+![CustomerCredit2-ES.png?h=250](//images.ctfassets.net/alneenqid6w5/2kPzHCdKHPtdTRISkPpBP5/1d8832a989213974eff370027c655b3c/CustomerCredit2-ES.png_h_250)
 
 ### Bases grandes
 
diff --git a/docs/tutorials/es/managing-delivery-capacity.md b/docs/tutorials/es/managing-delivery-capacity.md
index a8ae83331..17462ef0f 100644
--- a/docs/tutorials/es/managing-delivery-capacity.md
+++ b/docs/tutorials/es/managing-delivery-capacity.md
@@ -3,8 +3,8 @@ title: 'Gestionar capacidad de entrega'
 id: 2y217FQZCjD0I1n62yxVcz
 status: PUBLISHED
 createdAt: 2021-04-19T14:43:24.606Z
-updatedAt: 2023-03-24T20:39:18.594Z
-publishedAt: 2023-03-24T20:39:18.594Z
+updatedAt: 2024-03-25T20:04:31.192Z
+publishedAt: 2024-03-25T20:04:31.192Z
 firstPublishedAt: 2021-05-24T17:00:14.134Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,26 +15,25 @@ legacySlug: gestionar-capacidad-de-entrega
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
+Puede hacer un seguimiento de la disponibilidad de las ventanas de entrega y de la cantidad de ítems/pedidos que aún pueden atenderse en cada ventana de entrega a través de la página **Capacidad de entrega**.
 
-Puede hacer un seguimiento de la disponibilidad de las ventanas de entrega y de la cantidad de ítems/pedidos que aún pueden atenderse en cada ventana de entrega a través de la página Capacidad de entrega.
+Para gestionar su **Capacidad de entrega**, debe tener [políticas de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) previamente registradas y la [Capacidad de entrega](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) previamente configurada. 
 
-<div class="alert alert-warning"> 
-Para gestionar su capacidad de entrega, debe tener transportadoras previamente registradas y la capacidad de entrega previamente configurada. Lea <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">Registrar política de envío</a> y <a href="https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> para saber cómo realizar este registro y configuración.
+<div class="alert alert-warning">
+Para que la <a href="https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> y la <a href="https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidad de entrega</a> funcionen correctamente, debes tener en cuenta que:<p><ul><li>La suma de {<a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID de la política de envío} no puede exceder los 60 caracteres.</li><li>No se debe utilizar espacio en el ID de la <a href="https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">política de envío</a>.</li></ul></p>
 </div>
 
-La gestión de la capacidad de entrega se realiza desde el formulário de creación o edición de  **Política de envío** en el Admin.
-
-Al hacer clic en Capacidad de entrega, verá una página que contiene una lista de las ventanas de entrega de su tienda. La lista mostrada se refiere a la política de envío seleccionada en el filtro Política de envío y al periodo seleccionado en el filtro Fecha.
+En el Admin VTEX, accede a **Envío > Capacidad de entrega**, o escribe **Capacidad de entrega** en la barra de búsqueda en la parte superior de la página. La **Capacidad de entrega** contiene una lista de las ventanas de entrega de su tienda. La lista mostrada se refiere a la política de envío seleccionada en el filtro `Política de envío` y al periodo seleccionado en el filtro `Fecha`.
 
 Una vez que haya seleccionado la política de envío y la fecha que se mostrarán en la lista, tendrá acceso a las ventanas de entrega registradas. Cada línea de la lista representa una ventana de entrega y muestra los siguientes datos:
 
 *   **Fecha de entrega:** las fechas disponibles para entrega. 
-*   **Ventana de horario de entrega:** los horarios disponibles para entrega. 
+*   **Horario de entrega:** los horarios disponibles para entrega. 
 *   **Capacidad:** la capacidad de entrega. 
 *   **Reservado:** ítems/pedidos ya reservados (compra confirmada, pago no confirmado). 
 *   **Disponible:** cuántos ítems/pedidos están disponibles para programarse (cantidad de capacidad menos reservado) 
 *   **Status:** puede ser visible o no visible, dependiendo de si la ventana de entrega todavía está disponible. Si todavía está disponible, la ventana tendrá el status visible para sus clientes. 
 
-<div class="alert alert-warning"> 
+<div class = "alert alert-info">
 Puede hacer clic en <b>EDITAR POLÍTICA DE ENVÍO</b> para ser redirigido a la pantalla de edición de la política de envío seleccionada en el filtro Política de envío.
 </div>
diff --git a/docs/tutorials/es/managing-http-headers.md b/docs/tutorials/es/managing-http-headers.md
new file mode 100644
index 000000000..ea264acd4
--- /dev/null
+++ b/docs/tutorials/es/managing-http-headers.md
@@ -0,0 +1,65 @@
+---
+title: 'Gestionar encabezados HTTP'
+id: 2cCTvwQR3Z4ENVKMJU6NK3
+status: PUBLISHED
+createdAt: 2024-06-07T17:58:18.041Z
+updatedAt: 2024-06-07T18:40:52.927Z
+publishedAt: 2024-06-07T18:40:52.927Z
+firstPublishedAt: 2024-06-07T18:40:52.927Z
+contentType: tutorial
+productTeam: Reliability
+author: YRJ73j8mt38D5TUleocQB
+slug: gestionar-encabezados-http
+locale: es
+legacySlug: gestionar-encabezados-http
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+El protocolo de comunicación HTTP (Hypertext Transfer Protocol) es fundamental en la transmisión de datos a través de la World Wide Web. Opera con un modelo cliente-servidor en el que clientes como navegadores solicitan recursos como páginas de los servidores web. Las solicitudes se realizan mediante requests que se intercambian en formato de mensaje siguiendo un conjunto de reglas y normas definidas por el protocolo.
+
+Los encabezados son clave en la comunicación HTTP, ya que proporcionan información adicional sobre la transacción en curso. Hay dos tipos principales de encabezados:
+
+- __Encabezados de request:__ enviados por el cliente al servidor. Contienen información sobre el request realizado, tal como tipo de método HTTP utilizado, tipo de contenido aceptado, cookies, entre otros.
+- __Encabezados de respuesta:__ enviados por el servidor al cliente. Proporcionan información sobre la respuesta enviada, tal como status de la respuesta, tipo de contenido devuelto, cookies, entre otros.
+
+<div class = "alert alert-info">
+Para más información, consulta la guía de <a href="https://developer.mozilla.org/es/docs/Web/HTTP">MDN HTTP</a> y la documentación relacionada.
+</div>
+
+En esta guía, aprenderás a gestionar los encabezados de respuestas de seguridad.
+
+## Encabezados de respuestas de seguridad
+
+Si necesitas cambiar el valor de un encabezado de respuesta de seguridad en una tienda Store Framework, abre un ticket con el [soporte VTEX](https://help.vtex.com/es/support).
+
+A continuación se indican los encabezados que admiten modificación:
+
+- [**X-Frame-Options**](https://developer.mozilla.org/es/docs/Web/HTTP/Headers/X-Frame-Options): permite controlar la incorporación de unos sitios web en otros mediante el uso de frames. Este encabezado es una medida de seguridad para proteger a los usuarios contra ataques de [clickjacking](https://developer.mozilla.org/es/docs/Web/Security/Types_of_attacks), que ocurren cuando un atacante engaña al usuario para que haga clic en algún elemento de una página web sin su consentimiento.
+- [**X-Content-Type-Options**](https://developer.mozilla.org/es/docs/Web/HTTP/Headers/X-Content-Type-Options): protege contra vulnerabilidades de [MIME](https://developer.mozilla.org/es/docs/Web/HTTP/Basics_of_HTTP/MIME_types), que ocurren cuando un sitio web permite que los usuarios carguen contenido.
+- [**Content-Security-Policy (CSP)**](https://developer.mozilla.org/es/docs/Web/HTTP/Headers/Content-Security-Policy): permite controlar los recursos que el agente de usuario puede cargar a una cierta página, lo que ayuda contra ataques de [cross-site scripting](https://developer.mozilla.org/es/docs/Glossary/Cross-site_scripting).
+- [**Strict-Transport-Security (HSTS)**](https://developer.mozilla.org/es/docs/Web/HTTP/Headers/Strict-Transport-Security): les indica a los navegadores que solo se puede acceder al sitio web a través de HTTPS.
+- [**X-XSS-Protection**](https://developer.mozilla.org/es/docs/Web/HTTP/Headers/X-XSS-Protection): indica a los navegadores cómo reaccionar ante ataques de cross-site scripting (XSS), activando el filtro integrado para bloquear la ejecución de scripts maliciosos en el navegador del usuario.
+- [**Referrer-Policy**](https://developer.mozilla.org/es/docs/Web/HTTP/Headers/Referrer-Policy): determina la información de origen de la página que se comparte con la página de destino en requests de HTTP. Es esencial para proteger la privacidad de los usuarios y la seguridad del sitio web.
+
+## Encabezados personalizados
+
+Puedes configurar un encabezado personalizado, es decir, un valor que no está estandarizado y que es una adaptación a los requisitos o funcionalidades particulares de las necesidades de la tienda.
+
+<div class="alert alert-warning">
+Solo se puede agregar un encabezado personalizado por cuenta.
+</div>
+
+Si necesitas configurar un encabezado personalizado, abre un ticket con el soporte VTEX y proporciona las claves y valores. Esta información es tu responsabilidad. Puedes utilizar la documentación de [MDN HTTP headers](https://developer.mozilla.org/es/docs/Web/HTTP/Headers) como guía.
+
+A continuación se presenta un ejemplo de encabezado personalizado:
+
+```json
+"customHeader": {
+   "key": "Strict-Transport-Security",
+   "value": "max-age=31536000; includeSubdomains; preload"
+ }
+```
+
+El valor `max-age=31536000; includeSubdomains` en el contexto del encabezado Strict-Transport-Security (HSTS) representa la duración máxima, en segundos, que el navegador debe exigir la aplicación de la política HSTS en un dominio dado y sus subdominios.
+
+La directriz `preload` indica que se debe incluir el dominio en la lista de carga previa de HSTS para garantizar que los navegadores compatibles solo se conectarán a través de HTTPS, incluso para el request inicial.
diff --git a/docs/tutorials/es/managing-page-and-template-content.md b/docs/tutorials/es/managing-page-and-template-content.md
index b396db9bd..906964b8c 100644
--- a/docs/tutorials/es/managing-page-and-template-content.md
+++ b/docs/tutorials/es/managing-page-and-template-content.md
@@ -34,7 +34,7 @@ Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una p
 
 1. Seleccione el bloque para el que desea crear nuevo contenido. Puede seleccionarlo utilizando la lista en la esquina derecha o a través de la interfaz:
 
-![seta-interface-es](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
+![seta-interface-es](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
 
 2. Haga clic en `Versiones` en la esquina superior derecha. 
 
@@ -61,7 +61,7 @@ Site Editor aplica la configuración de contenido según la jerarquía de parám
 
 1. Seleccione el bloque cuyo contenido desea sobrescribir. Puede seleccionarlo utilizando la lista en la esquina derecha o a través de la interfaz:
 
-![seta-interface-es](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
+![seta-interface-es](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
 
 2. El contenido disponible corresponde al que está activo ahora. Modifique los campos con los nuevos valores o haga clic en `Versiones` para cambiar la configuración de otro contenido. 
 3. Guarde los cambios.
@@ -74,7 +74,7 @@ No puede actualizar la visibilidad del contenido que se derive del código fuent
 
 1. Seleccione el bloque cuyo contenido desea eliminar o restablecer. Puede seleccionarlo utilizando la lista en la esquina derecha o a través de la interfaz:
 
-![seta-interface-es](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
+![seta-interface-es](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
 
 2. Haga clic en `Versiones` en la esquina superior derecha. 
 3. Haga clic en el menú del contenido deseado (tres puntos verticales). 
diff --git a/docs/tutorials/es/managing-pages.md b/docs/tutorials/es/managing-pages.md
index c985bb888..50273d960 100644
--- a/docs/tutorials/es/managing-pages.md
+++ b/docs/tutorials/es/managing-pages.md
@@ -3,8 +3,8 @@ title: 'Gestión de Páginas en el Headless CMS'
 id: 3DO6rBhZ1p3zndnFu5BgRt
 status: PUBLISHED
 createdAt: 2023-03-23T19:46:08.568Z
-updatedAt: 2023-04-25T19:19:08.542Z
-publishedAt: 2023-04-25T19:19:08.542Z
+updatedAt: 2024-06-17T12:55:20.070Z
+publishedAt: 2024-06-17T12:55:20.070Z
 firstPublishedAt: 2023-03-23T20:06:47.380Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,17 +15,33 @@ legacySlug: gestion-de-paginas-beta
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-En **Headless CMS**, puedes ver todas las rutas URL y los modelos de página del sitio web de tu tienda:`Global Alert Page` `Page`,`Product Page`. También puedes crear y asociar páginas personalizadas a plantillas predefinidas y gestionar páginas creadas directamente en el código fuente de tu proyecto de storefront.
+En **Headless CMS**, puedes gestionar todas las rutas de URL y los modelos de página de tu tienda en línea, incluyendo las páginas `Global Alert Page` `Page`,`Product Page`. También puedes crear y asociar páginas personalizadas a plantillas predefinidas y gestionar páginas creadas directamente en el código fuente de tu proyecto de storefront.
 
- ![Paginas](https://images.ctfassets.net/alneenqid6w5/6rzTf5xTBpR3P8sUonA0Ms/64ef7886fa8e4531bdb8d6cb981b7396/paginas_uno.png)
+## Visión general
 
-Puedes crear y gestionar una página siguiendo las instrucciones a continuación:
+![New pages - es](//images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/76783d200466eafd99f1972a60068298/novas_pgs._es.png)
+
+| Opção               | Descrição                                              |
+| ------------------- | ------------------------------------------------------ |
+| Crear documento   | Crea una nueva página basada en las opciones disponibles, por ejemplo, `Product Page` o `Home`.  |
+| Configuraciones (⚙️) | Abre un modal con las configuraciones del proyecto divididas en tres pestañas: <ul><li>**General:** permite editar el ID del proyecto y las configuraciones de API o archivar el proyecto.</li> <li>**Content-Types:** Guarda los content types creados en el código de la tienda.</li><li>**Compilación:** permite conectar el proyecto CMS al código fuente mediante webhooks, configurando los tipos de contenido y las secciones.</li></ul> |
+| Buscar      | Busca páginas específicas dentro del proyecto. |
+| Status      | Filtra las páginas según su estado: <ul><li><code>Published</code>: Páginas publicadas y ya disponibles en la tienda.</li> <li><code>Draft</code>: Páginas que están en borrador, en desarrollo, y aún no han sido publicadas.</li></ul>|
+| Tipo      | Filtra las páginas según el tipo de contenido (content types). Los tipos de contenido son definidos en el código de su tienda. Para obtener más información, consulte [Adding Content Types to the Headless CMS](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-2-adding-content-types-to-the-headless-cms). |
+
+## Crear una nueva página
+
+Para crear y gestionar una página, sigue estos pasos:
 
 1. En el Admin VTEX, accede a **Headless CMS**.
-2. Haz clic en `Crear nuevo` y selecciona la página deseada.
-3. Haz clic en <i class="fa-solid fa-circle-plus"></i> y selecciona la seccion deseada.
-![Gif - Páginas](https://images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/e7e804bd75245d2571668725dfd82aba/Espanhol_gif_das_p__ginas.gif)
-4. Nombre la página y rellena los campos.
-5. Haz clic en `Publicar`.
+<div class="alert alert-warning">
+  Asegúrate de estar en el proyecto correcto. De lo contrario, ve al menú <b>Proyecto</b> en la esquina superior izquierda, selecciona el nombre del proyecto en el que deseas crear la página y continúa en el paso 2.
+</div>
+2. Haz clic en `Crear documento` y selecciona el tipo de página deseado.
+3. En `Untitled`, nombra la página.
+4. Haz clic en `Secciones` y selecciona la sección deseada.
+![Gif - Páginas](//images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/e7e804bd75245d2571668725dfd82aba/Espanhol_gif_das_p__ginas.gif)
+5. Agrega más secciones si es necesario y llénalas.
+6. Haz clic en `Publicar`.
 
-Clic <i class="fa-solid fa-ellipsis-vertical"></i> para `Duplicar` o `Eliminar` su página.
+Para duplicar o eliminar la página, haz clic en el menú **Más acciones** (`⋮`) de la página.
diff --git a/docs/tutorials/es/managing-placeholders.md b/docs/tutorials/es/managing-placeholders.md
index 424a0e711..bef342f9d 100644
--- a/docs/tutorials/es/managing-placeholders.md
+++ b/docs/tutorials/es/managing-placeholders.md
@@ -35,7 +35,7 @@ Lo que hace es crear un elemento configurable en el lugar del código donde se i
 
 Es importante ingresar un valor de `id`. Este será el identificador para este placeholder en el sistema.
 
-![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando el placeholder
 
@@ -43,7 +43,7 @@ Ahora que el control de placeholder se ha ingresado en el template, vamos a conf
 
 Esto se hace en las configuraciones del layout que utiliza este template.
 
-1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para ingresar un objeto, haga clic en **add object**. 
 3. A continuación, seleccione el tipo de objeto y haga clic en **Añadir**.
 4. Finalmente, haga clic en el botón  **Save Settings**, en la parte superior de la página.
@@ -52,7 +52,7 @@ Ahora puede editar el objeto que ha ingresado en el placeholder.
 
 Para esto, haga clic en el lápiz que se encuentra dentro del objeto y, a continuación, haga clic en **add content**.
 
-![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Ahora puede definir el nombre de este objeto, subir imágenes y configurar las condiciones en las que se renderizará, tales como el período. 
 
diff --git a/docs/tutorials/es/managing-projects.md b/docs/tutorials/es/managing-projects.md
new file mode 100644
index 000000000..6df958192
--- /dev/null
+++ b/docs/tutorials/es/managing-projects.md
@@ -0,0 +1,129 @@
+---
+title: 'Gestionar Proyectos'
+id: 42IpDFqTVTESH8DCypJMPM
+status: PUBLISHED
+createdAt: 2023-11-01T13:45:57.091Z
+updatedAt: 2024-06-21T14:14:20.212Z
+publishedAt: 2024-06-21T14:14:20.212Z
+firstPublishedAt: 2023-11-01T19:38:50.237Z
+contentType: tutorial
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: gestionar-proyectos
+locale: es
+legacySlug: gestionar-proyectos
+subcategory: 27t6x0lngvjI3bnUg5AgEO
+---
+
+Proyectos es una funcionalidad de VTEX Headless CMS que simplifica la gestión de varios proyectos de frontend, como aplicaciones móviles, páginas web y email marketing, desde un único dashboard.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
+
+Cada proyecto cuenta con sus propios ajustes, contenido y marca, pudiendo personalizarse en función de públicos u objetivos específicos. 
+
+En esta guía aprenderás a gestionar cada proyecto de frontend de tu tienda.
+
+<div class="alert alert-warning">
+  <a href="https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview"> FastStore WebOps usuarios</a>:Los cambios realizados a través del Headless CMS en el VTEX Admin, como la creación de nuevos tipos de contenido (content types), la adición de secciones o la actualización de campos, pueden no aparecer automáticamente en la tienda una vez que los publiques. Este es un problema conocido, y debes contactar a tu equipo de desarrollo para implementar la solución necesaria. Para obtener instrucciones detalladas, consulta el artículo sobre el problema conocido <a href="https://help.vtex.com/es/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW">La aplicación Webops no está totalmente integrada con Headless CMS</a>.
+</div>
+
+## Antes de empezar
+Para gestionar el Headless CMS, asegúrese de que los [recursos](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar`, `Settings*`, and `CMS GraphQL API` estén asociados con su [rol de usuario](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). De lo contrario, [cree un rol de usuario](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol) y agregue estos recursos o añádalos a un rol de usuario existente.
+
+## Visión general
+Para acceder a **Proyectos**, en el Admin VTEX ve a **Storefront > Headless CMS**.
+
+![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/fa66fd00d9a29e3eeb835369c70277d7/projects-two-es-outro.png)
+
+| Opciones     | Descripción     |
+| ---------- | ---------- |
+| Tarjeta del proyecto       | Abre el proyecto seleccionado, para que puedas crear y editar las páginas de su contenido.       |
+| Configuración (⚙️)      | Abre una ventana que muestra los ajustes del proyecto organizados en tres pestañas: <ul><li>**General:** permite editar el ID del proyecto y la configuración de la API o archivar el proyecto.</li><li>**Content-Types:** Conecta el proyecto Headless CMS con el código código de la tienda a través de webhooks configurando los tipos de contenido (content types) y las secciones. </li> <li>**Compilación:** Inicia y administra compilaciones del sitio web. Establece una URL de webhook para recibir notificaciones de compilación y un punto final para previsualizar las versiones de la página.</li></ul>      |
+| Crear nuevo | Abre una página para configurar un nuevo proyecto. |
+
+## Crear un nuevo proyecto
+
+Crea un nuevo proyecto para tu tienda configurando ajustes generales como **ID del proyecto** y **URL base de producción**. Para conectar eficazmente un proyecto Headless CMS con el código fuente de tu proyecto también será necesario configurar webhooks y ajustes de compilación, como *URL de compilación de webhook* y *URL de previsualización*. 
+
+Un webhook es un endpoint HTTP que permite la comunicación automatizada entre VTEX Headless CMS y el código fuente del proyecto. Por ejemplo, permite que el CMS notifique a un proyecto FastStore sobre cambios de contenido u otros eventos, desencadenando acciones como la sincronización de contenido en tiempo real.
+
+1. En la página **Proyectos**, haz clic en `Crear nuevo`.
+2. En la página **Nuevo proyecto**, rellena los campos de la sección [Configuración del proyecto](#configuración del proyecto).
+3. Después de definir cada campo de la página, haz clic en `Crear` y un mensaje de éxito se mostrará en la pantalla.
+
+Tras crear un nuevo proyecto, puedes crear páginas para el mismo con todas las rutas URL y modelos de página compatibles con tu tienda, como páginas de inicio, de producto y de inicio de sesión. 
+
+Para crear una nueva página sigue los pasos presentes en este artículo: [Gestión de páginas en Headless CMS](https://help.vtex.com/es/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt)
+
+## Configuración del proyecto
+En Configuración, puedes realizar ajustes en el proyecto en tres categorías principales:
+
+-[General](#general): permite editar el ID del proyecto, la configuración de la API y archivar el proyecto.
+-[Content-Types](#content-types): permite establecer la conexión entre el proyecto Headless CMS y el código de tu proyecto.
+-[Compilación](#compilación): inicia y administra las compilaciones del sitio web. Establece una URL de webhook para las notificaciones de compilación y un punto final para previsualizar las versiones de la página.
+
+### General
+
+| Nombre del campo     | Descripción     | Ejemplo de valor    |
+| ---------- | ---------- | ---------- |
+| ID del proyecto (obligatorio)      | ID del proyecto.       | `FastStore`        |
+| Storefront      | Define los storefronts VTEX disponibles (`FastStore` or `Custom`) y su propósito. | Consulte la sección [Storefront](#storefront) para obtener más información. |
+
+#### Storefront
+
+Este campo determina la configuración de [Compilación](#compilación) en función del storefront elegido. Las opciones incluyen:
+
+- **VTEX Storefronts**:
+
+Elija un storefront de su cuenta (por ejemplo, FastStore). [Compilación](#compilación) se ajusta automáticamente según el storefront elegido. Todavía puede personalizarlos más tarde.
+
+- **Custom**
+
+Elegir un storefront `Custom` (personalizado) le brinda la flexibilidad de definir su propia configuración de [Compilación](#compilación).
+
+### Content-Types
+
+| Field name             | Description           | Value example     |
+| ---------------------- | --------------------- | ----------------- |
+| URL de las secciones | URL del webhook para recibir y guardar las secciones creadas en el código fuente del CMS headless.. | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{projectId}/sections`       |
+| URL de los tipos de contenido       | URL del webhook para recibir y guardar los tipos de contenido creados en el código fuente del CMS headless.      | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/content-types`       |
+
+### Compilar
+
+| Nombre del campo    | Descripción     | Ejemplo del valor     |
+| ---------- | ---------- | ---------- |
+| URL de las secciones       | URL del webhook para recibir y guardar las secciones creadas en el código fuente en Headless CMS.      | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/sections`       |
+| URL de los tipos de contenido       | URL del webhook para recibir y guardar los tipos de contenido creados en el código fuente en Headless CMS.       | `https://infra.io.vtex.com/vbase/v0/{accountName}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/content-types`       |
+| URL de compilación del webhook       | URL del webhook para iniciar una nueva compilación en Headless CMS cuando se agrega o edita una página o contenido.       | `https://app.io.vtex.com/vtex.cms-builder-sf-jamstack/v1/{accountName}/{workspace}/build-releases`      |
+| Guardar URL de webhook      | URL de webhook para permitir previsualizaciones del proyecto en tiempo real, enviando una notificación para actualizar la página y que se reflejen los últimos cambios en Headless CMS.      | -       |
+| URL de previsualización      | URL de webhook que permite la previsualización de páginas en el Headless CMS. | `https://{accountName}.vtex.app/api/preview` |
+
+## Editar proyecto
+Después de crear el proyecto, también puedes editar toda la información definida durante la [creación del proyecto](#crear-nuevo-proyecto).
+En la página principal **Proyectos**, haz clic en **Configuración** (⚙️), y se abrirá una ventana con tres pestañas para realizar ajustes: [General](#general), [Content-Types](#content-types) y [Compilar](#compilar).
+
+### Restaurar la URL predeterminada de las secciones
+
+Una vez que has [creado el proyecto](#crear-un-nuevo-proyecto) y deseas editar el campo [**URL de las secciones**](#content-types), haz clic en `Editar`, agrega la nueva URL del webhook y haz clic en Guardar. Si deseas restaurar la URL predeterminada, haz clic en `Restaurar URL predeterminada`.
+
+## Archivar proyecto
+Al archivar un proyecto se desactiva la API y el acceso al contenido del proyecto. 
+Para archivar un proyecto sigue los pasos a continuación:
+
+1. Accede a **Storefront > Proyectos**.
+2. Selecciona el proyecto que deseas archivar y haz clic en **Configuración** (⚙️). 
+3. Haz clic en `Archivar proyecto` en la página `General`. Aparecerá un mensaje emergente para confirmar que deseas archivar el proyecto.
+![Arquivar projeto - ES](//images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/a7f9e04f4b9dc6161bd3f9a9c683f99c/projects-three-es.png)
+4. Haz clic en `Archivar`. A continuación aparecerá un mensaje informando que el proyecto se archivó con éxito.
+
+Para restaurar un proyecto archivado, sigue los pasos descritos en [Restaurar proyecto] (#restaurar-proyecto).
+
+### Restaurar proyecto
+Al restaurar un proyecto la API se reactiva y se puede acceder de nuevo a su contenido.
+Para restaurar un proyecto sigue los pasos a continuación:
+
+1. Accede a **Storefront > Proyectos**.
+2. Haz clic en la tarjeta del proyecto archivado.
+3. Haz clic en `Restaurar proyecto`. Aparecerá un mensaje emergente para confirmar que deseas restaurar el proyecto.
+4. Haz clic en `Restaurar`. A continuación aparecerá un mensaje informando que el proyecto se restauró con éxito.
+
diff --git a/docs/tutorials/es/managing-redirects-per-binding.md b/docs/tutorials/es/managing-redirects-per-binding.md
index 30f7bc78f..f7fbe0818 100644
--- a/docs/tutorials/es/managing-redirects-per-binding.md
+++ b/docs/tutorials/es/managing-redirects-per-binding.md
@@ -3,8 +3,8 @@ title: 'Gestionar redirecciones según el binding'
 id: 67GAK2TCQgjvmtPXxAqREb
 status: PUBLISHED
 createdAt: 2021-04-20T15:03:54.330Z
-updatedAt: 2023-03-24T22:20:43.304Z
-publishedAt: 2023-03-24T22:20:43.304Z
+updatedAt: 2023-09-04T12:42:32.729Z
+publishedAt: 2023-09-04T12:42:32.729Z
 firstPublishedAt: 2021-05-05T18:11:25.521Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -21,12 +21,16 @@ Las tiendas que tienen varios dominios suelen solicitar gestionar la redirecció
 
 Con esto en mente, VTEX le permite gestionar sus redirecciones de URL de acuerdo con el *binding* de la tienda a través de la interfaz del Admin.
 
+<div class="alert alert-warning" role="alert">
+Para crear, editar o eliminar redirecciones, el usuario del Admin VTEX debe tener un rol de acceso con el <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso de License Manager</a> <strong>CMS Settings</strong>. Puedes asignar al usuario un rol de acceso con el recurso siguiendo las instrucciones del artículo <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512#editando-usuarios">Gestionar usuarios</a>, o crear un nuevo rol de acceso que incluya dicho recurso consultando las instrucciones del artículo <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol">Roles</a>.
+</div>
+
 En el Admin VTEX:
 
 1. Acceda al módulo **Storefront > Páginas**.
 2. Haga clic en la pestaña `Redirecciones`.
 
-![es-redirect-tab](https://images.ctfassets.net/alneenqid6w5/5TkQzPBMxi9Wh4SCBgVWZ1/ca140110fbe426d775814a1fd5ae4350/redirect-tab.png)
+![es-redirect-tab](//images.ctfassets.net/alneenqid6w5/5TkQzPBMxi9Wh4SCBgVWZ1/ca140110fbe426d775814a1fd5ae4350/redirect-tab.png)
 
 ## Crear redirecciones manualmente
 
@@ -38,7 +42,7 @@ En la pestaña Redirecciones del módulo Páginas:
 4. Indique si la redirección será permanente o temporal. Si es temporal, puede activar el botón `Esta redirección tiene una fecha final` y definir la fecha final. 
 5. Guarde los cambios.
 
-![es-novoredirect](https://images.ctfassets.net/alneenqid6w5/1XJSvEL4ozDdupa3j0mcx8/95ddbd08e7902a6c7aa7f30a4af85120/nuevo-redirect.png)
+![es-novoredirect](//images.ctfassets.net/alneenqid6w5/1XJSvEL4ozDdupa3j0mcx8/95ddbd08e7902a6c7aa7f30a4af85120/nuevo-redirect.png)
 
 ## Eliminar redirecciones manualmente
 
@@ -48,7 +52,7 @@ En la pestaña Redirecciones del módulo Páginas:
 2. Haga clic en el botón `Remover`.
 3. Confirme la acción. 
 
-![es-remover-redirect](https://images.ctfassets.net/alneenqid6w5/5khhDBT5o6ESJjwlaFClr5/a6d978fecd07eba1007ea1b28d2675b6/remover-redirect.png)
+![es-remover-redirect](//images.ctfassets.net/alneenqid6w5/5khhDBT5o6ESJjwlaFClr5/a6d978fecd07eba1007ea1b28d2675b6/remover-redirect.png)
 
 <div class="alert alert-warning">
 Puede ocurrir un error al intentar hacer clic en las redirecciones que tienen cadenas de query. El equipo de producto de VTEX está al tanto de este comportamiento inesperado y está trabajando en la corrección. Si no puede hacer clic en la redirección que desea eliminar, puede utilizar la hoja de cálculo para eliminarla mientras arreglamos el error. 
@@ -79,7 +83,7 @@ En la pestaña Redirecciones del módulo Páginas:
 4. Haga clic en el botón `Importar`. 
 5. Haga clic en el botón `Guardar` o `Eliminar` según sea el caso. 
 
-  ![es-redirect-planilha](https://images.ctfassets.net/alneenqid6w5/4jcHxndX1LyV74UdFJgWNV/7efcfc5207e0972a2b31a4be847b7000/planilha-redirect.png)
+  ![es-redirect-planilha](//images.ctfassets.net/alneenqid6w5/4jcHxndX1LyV74UdFJgWNV/7efcfc5207e0972a2b31a4be847b7000/planilha-redirect.png)
 
   <div class="alert alert-warning">
 Al seleccionar la opción <code>Guardar</code>, creará todas las redirecciones enumeradas en la plantilla, mientras que seleccionar la opción <code>Eliminar</code> las eliminará todas de la base de datos de su tienda.
diff --git a/docs/tutorials/es/managing-shipping-policies.md b/docs/tutorials/es/managing-shipping-policies.md
new file mode 100644
index 000000000..e2db080ec
--- /dev/null
+++ b/docs/tutorials/es/managing-shipping-policies.md
@@ -0,0 +1,114 @@
+---
+title: 'Gestionar políticas de envío'
+id: 30nynylgbWieimhaMtGTIE
+status: PUBLISHED
+createdAt: 2024-01-30T16:15:33.582Z
+updatedAt: 2024-01-31T13:48:35.723Z
+publishedAt: 2024-01-31T13:48:35.723Z
+firstPublishedAt: 2024-01-31T00:54:58.302Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: gestionar-politicas-de-envio
+locale: es
+legacySlug: gestionar-politicas-de-envio
+subcategory: 7fTH6bP0C4IaM8qWi0kkQC
+---
+
+La [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) es un conjunto de reglas y ajustes que definen las opciones de envío que se mostrarán a los clientes en el checkout. La relación entre la política de envío, [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) y [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) es lo que conforma la [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) en VTEX, como se muestra en la siguiente imagen:
+
+![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
+
+Este artículo describe cómo monitorear y gestionar las políticas de envío. La pestaña **Políticas de envío** en el Admin VTEX, accesible en **Envío > Estrategia de envío**, te permite realizar las siguientes acciones:
+
+* [Ver lista de políticas de envío](#ver-lista-de-politicas-de-envio)
+* [Buscar políticas de envío](#buscar-politicas-de-envio)
+* [Filtrar políticas de envío](#filtrar-politicas-de-envio)
+* [Ver dashboard de transportadoras (opcional)](#ver-dashboard-de-transportadoras-solo-brasil)
+* [Editar políticas de envío](#editar-politicas-de-envio)
+* [Activar o desactivar políticas de envío](#activar-o-desactivar-politicas-de-envio)
+* [Eliminar políticas de envío](#eliminar-politicas-de-envio)
+
+También puedes crear políticas de envío. Consulta [Crear una política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) para más información.
+
+## Ver lista de políticas de envío
+
+La pestaña **Políticas de envío** del Admin VTEX, accesible a través de **Envío > Estrategia de envío**, muestra una lista como se ilustra a continuación:
+
+![shipping_policy_ES](//images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/04e7831e6af05ee2312eb51720c4e7f1/shipping_policy_ES.png)
+
+La información de la lista se describe en la siguiente tabla:
+
+| **Columna** | **Descripción** |
+| :---: | :--- |
+| Política de envío | Nombre que identifica tu [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) para los usuarios que tienen acceso al Admin VTEX. Para más información, consulta [Crear una política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT). |
+| Método de envío | <p><a href="https://help.vtex.com/es/tutorial/como-funciona-o-tipo-de-envio--tutorials_126">Método de envío</a> es el nombre que configuras en la política de envío que se mostrará a los clientes en el checkout. Por lo tanto, es importante utilizar nombres intuitivos al crear una política de envío.</p><p>Ejemplo: <code>Envío express</code> e <code>Envío estándar</code>.</p> |
+| Muelles | Identifica los [muelles](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) asociados a la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140). Al pasar el mouse sobre el número de esta columna, se muestran los nombres de todos los muelles asociados a la política de envío. |
+| Status | <p>Status de activación de la política de envío, que puede ser:</p><p><ul><li><b>Activa:</b> la política de envío está activada y se considera válida en el <a href="https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116">cálculo</a> de envío de pedidos.</li><li><b>Inactiva:</b> la política de envío está desactivada y no es válida para envíos.</li></ul></p> |
+| Transportadora (solo Brasil) | Este campo solo se muestra en el Admin VTEX de tiendas que activaron la funcionalidad [VTEX Shipping Network Correio](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) o que contrataron [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) y solamente identifica a Correios. |
+| Contrato (solo Brasil) | <p>Este campo solo se muestra en el Admin VTEX de tiendas que hayan activado <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa">VTEX Shipping Network Correios</a>.</p><p>Los valores pueden ser:</p><p><ul><li><b>VTEX:</b> la tienda contrató una tabla de Correios mediada por VTEX.</li><li><b>Propio:</b> la tienda contrató una tabla por cuenta propia antes de activar VTEX Shipping Network Correios.</li></ul></p> |
+
+## Buscar políticas de envío
+
+La caja de búsqueda que tiene el ícono de lupa <i class="fas fa-search"></i> te permite buscar políticas de envío por nombre. Ingresar un carácter en la barra de búsqueda activa la búsqueda inmediatamente. Para limpiar la búsqueda, haz clic en el ícono de cerrar <i class="far fa-times-circle"></i>.
+
+<div class = "alert alert-info">
+Si la búsqueda no devuelve ningún resultado, comprueba la ortografía del término o si hay algún filtro seleccionado.
+</div>
+
+## Filtrar políticas de envío
+
+Puedes filtrar políticas por status, ya sea `Activa` o `Inactiva`, según se describe a continuación:
+
+1. En el Admin VTEX, accede a **Envío > Estrategia de envío** o ingresa **Estrategia de envío** en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña **Políticas de envío**, haz clic en `Status`.
+3. Selecciona una de las opciones de status:
+    * **Activa:** la política de envío está activada y se considera válida en el [cálculo](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) de envío de pedidos.
+    * **Inactiva:** la política de envío está desactivada y no es válida para envíos. 
+4. Haz clic en `Aplicar`.
+
+Para remover el filtro aplicado, haz clic en `Status` y después en `Limpiar`.
+
+### Filtro para tipos de contrato (solo Brasil)
+
+Las tiendas que hayan contratado [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) o hayan activado [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) pueden buscar por tipo de contrato:
+
+* `VTEX`: la contratación de la tabla de Correios fue mediada por VTEX.
+* `Propio`: la propia tienda realizó la contratación de la tabla de Correios.
+
+## Ver dashboard de transportadoras (solo Brasil)
+
+Las tiendas que hayan contratado [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) o hayan activado [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) verán el botón `Dashboard de transportadoras` en la página **Políticas de envío**. El botón redirige al usuario al [dashboard de VTEX Shipping Network](https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92), donde puede gestionar la operación de transportadoras utilizadas en esos productos.
+
+## Editar políticas de envío
+
+Para editar una política de envío, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Envío > Estrategia de envío** o ingresa **Estrategia de envío** en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña **Políticas de envío**, en la fila correspondiente al política deseada, haz clic en el ícono de menú <i class="fas fa-ellipsis-v"></i>. Puedes [buscar](#buscar-politicas-de-envio) o [filtrar](#filtrar-politicas-de-envio) políticas.
+3. Haz clic en `Editar`.
+4. Realiza los cambios deseados. Para más información sobre los campos, consulta el artículo [Crear una política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
+5. Haz clic en `Guardar cambios`.
+
+## Activar o desactivar políticas de envío
+
+Para activar o desactivar una política de envío, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Envío > Estrategia de envío** o ingresa **Estrategia de envío** en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña **Políticas de envío**, en la fila correspondiente al política deseada, haz clic en el ícono de menú <i class="fas fa-ellipsis-v"></i>. Puedes [buscar](#buscar-politicas-de-envio) o [filtrar](#filtrar-politicas-de-envio) políticas.
+3. Haz clic en `Activar` o `Desactivar`, según la acción deseada.
+4. En la ventana modal que se abre, haz clic en `Activar` o `Desactivar` nuevamente.
+
+## Eliminar políticas de envío
+
+Para eliminar una política de envío, sigue estos pasos:
+
+<div class="alert alert-danger">
+La acción de eliminar una política de envío es permanente y no se puede deshacer.
+</div>
+
+1. En el Admin VTEX, accede a **Envío > Estrategia de envío** o ingresa **Estrategia de envío** en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña **Políticas de envío**, en la fila correspondiente al política deseada, haz clic en el ícono de menú <i class="fas fa-ellipsis-v"></i>. Puedes [buscar](#buscar-politicas-de-envio) o [filtrar](#filtrar-politicas-de-envio) políticas.
+3. Haz clic en `Eliminar`.
+4. En la ventana modal que se abre, vuelve a hacer clic en `Eliminar`.
+
diff --git a/docs/tutorials/es/managing-singleton-content-types.md b/docs/tutorials/es/managing-singleton-content-types.md
index 9715ac24e..ff01b9ea2 100644
--- a/docs/tutorials/es/managing-singleton-content-types.md
+++ b/docs/tutorials/es/managing-singleton-content-types.md
@@ -3,8 +3,8 @@ title: 'Cómo gestionar content types Singleton'
 id: VBibMN1BqV2OFmavUFCdo
 status: PUBLISHED
 createdAt: 2023-04-05T17:55:26.748Z
-updatedAt: 2023-04-06T19:11:57.614Z
-publishedAt: 2023-04-06T19:11:57.614Z
+updatedAt: 2024-06-05T19:07:02.549Z
+publishedAt: 2024-06-05T19:07:02.549Z
 firstPublishedAt: 2023-04-06T19:11:57.614Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -18,10 +18,10 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 El content type de tipo Singleton permite la creación y gestión de una única página garantizando que en el Headless CMS solo exista una página de dicho content type.
 
 Su uso evita conflictos e incoherencias que pueden ocurrir cuando se crean varias páginas del mismo content type. Por ejemplo, puedes utilizar Singleton para la página de inicio (Home) de tu tienda, asegurándote de que solo haya una página de inicio y todas las actualizaciones y solicitudes realizadas en ella siempre devuelvan el mismo resultado.
-![singleton-es](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
+![singleton-es](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-  Para crear un content type Singleton, verifica con tu equipo de desarrolladores que la propiedad <i>isSingleton</i> ya esté implementada o solicita que sigan las instrucciones en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using `isSingleton` in a content type</a> para agregarla al content type deseado.
+<div class="alert alert-warning">
+  Para crear un content type Singleton, verifica con tu equipo de desarrolladores que la propiedad <i>isSingleton</i> ya esté implementada o solicita que sigan las instrucciones en <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> para agregarla al content type deseado.
 </div>
 
 ## Crear el Singleton
@@ -29,7 +29,7 @@ Su uso evita conflictos e incoherencias que pueden ocurrir cuando se crean varia
 2. Selecciona `CREAR NUEVO` y elige el nombre del content type singleton, por ejemplo **Home**.
 3. Edita la página y agrega nuevas secciones según tu preferencia.
 
-<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
 Solamente se puede crear el Singleton una vez. Si creaste la página Singleton, esta ya no aparecerá en la lista de content types.
 </div>
 
@@ -39,13 +39,26 @@ Para editar o eliminar contenido, consulta las secciones a continuación:
 
 ## Editar el Singleton
 1. Accede a **Admin > Storefront > Headless CMS**.
-2. Selecciona el Singleton creado, por ejemplo **Home**.
-3. Ya puedes editar la página de inicio **Home** agregando nuevas secciones.
+2. Haz clic en el proyecto donde se creó el Singleton.
+3. Selecciona el Singleton creado, por ejemplo **Home**.
+4. Ya puedes editar la página de inicio **Home** agregando nuevas secciones.
+
+##Despublicar el Singleton
+1. Accede a **Admin > Storefront > Headless CMS**.
+2. Haz clic en el proyecto en que se creó el Singleton.
+3. Haz clic en `Despublicar` > `Despublicar ahora`.
+
+<div class="alert alert-warning">
+Antes de despublicar, asegúrate de que no haya ningún borrador o no podrás continuar. Si hay alguno, puedes eliminarlo o programarlo para publicación.
+</div>
+
+4. Se mostrará una ventana emergente para que confirmes la acción de despublicar la página.
+5. Haz clic y mantén presionado el botón `DESPUBLICAR` para despublicar el contenido.
 
 ## Eliminar el Singleton
 1. En la página del Singleton, selecciona `Más` (menu kebab) y haz clic en `Eliminar`.
 2. Después haz clic en `VOLVER A LAS PÁGINAS`.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
   Si quieres restaurar la página y su contenido, haz clic en `RESTAURAR`.
 </div>
diff --git a/docs/tutorials/es/managing-stock-items.md b/docs/tutorials/es/managing-stock-items.md
index 93fd2b38b..9b7555e8a 100644
--- a/docs/tutorials/es/managing-stock-items.md
+++ b/docs/tutorials/es/managing-stock-items.md
@@ -3,8 +3,8 @@ title: 'Gestión del stock'
 id: tutorials_139
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:21.085Z
-updatedAt: 2023-03-31T00:44:36.047Z
-publishedAt: 2023-03-31T00:44:36.047Z
+updatedAt: 2024-04-18T15:25:20.097Z
+publishedAt: 2024-04-18T15:25:20.097Z
 firstPublishedAt: 2017-04-27T23:00:44.889Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,19 +15,9 @@ legacySlug: gestionar-items-en-inventario
 subcategory: 3PQwnyOcNyYgawy06oe6gE
 ---
 
-En VTEX, el _stock_ es la relación entre los ítems de venta de una tienda y los lugares donde se almacenan dichos artículos. Accede al Admin VTEX y haz clic en **Catálogo > Stock > Gestión del stock** para visualizar los SKU registrados en el [catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) y los respectivos [almacenes](https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb). 
+En VTEX, [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) es la identificación de las ubicaciones físicas de almacenamiento de productos de la tienda y _stock_ es la relación entre los almacenes y los SKU disponibles para la venta. Para visualizar los SKU registrados en el [catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) y los respectivos almacenes, accede al Admin VTEX y haz clic en **Catálogo > Stock > Gestión del stock**.
 
-Otras acciones disponibles en la página **Gestión del stock** son:
-
-* [Hacer seguimiento del historial de movimientos del stock](https://help.vtex.com/es/tutorial/historial-de-movimientos-del-stock--5AM7xbmMzmKSEQewakamc2).
-* [Comprobar que los SKU tienen unidades reservadas](https://help.vtex.com/es/tutorial/como-se-maneja-la-reserva--tutorials_92).
-* [Actualizar la cantidad de SKU que están disponibles para la venta](https://help.vtex.com/es/tutorial/actualization-de-la-cantidad-de-items-en-stock--2MDwYV1COA6YuoiY22AyGo). 
-
-<div class="alert alert-info"> 
-Recuerda que <b>almacén</b> es la identificación de las ubicaciones físicas de almacenamiento de productos de la tienda y <b><i>stock</i></b> es la relación entre los almacenes y los SKU disponibles para la venta.
-</div>
-
-Este artículo detalla la información del _stock_ en VTEX Admin utilizando la página **Gestión del stock**. Aprende cómo:
+Este artículo detalla la información de la página **Gestión del stock**. Aprende cómo:
 
 * [Los datos del _stock_ están divididos](#datos-del-stock).
 * [Los filtros de búsqueda están dispuestos para facilitar la búsqueda de SKU específicos](#filtros).
@@ -36,34 +26,39 @@ Este artículo detalla la información del _stock_ en VTEX Admin utilizando la p
 Para acceder al <i>stock</i> utilizando SKU, muelles o almacenes a través de API, utiliza la <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-"> Inventory API</a>.
 </div>
 
-## Datos del stock
+Otras acciones disponibles en la página **Gestión del stock** son:
 
-En el Admin VTEX, accede a **Catálogo > Stock > Gestión de stock**, o escribe **Gestión de stock** en la barra de búsqueda en la parte superior de la página.
+* [Hacer seguimiento del historial de movimientos del stock](https://help.vtex.com/es/tutorial/historial-de-movimientos-del-stock--5AM7xbmMzmKSEQewakamc2).
+* [Comprobar que los SKU tienen unidades reservadas](https://help.vtex.com/es/tutorial/como-se-maneja-la-reserva--tutorials_92).
+* [Actualizar la cantidad de SKU que están disponibles para la venta](https://help.vtex.com/es/tutorial/actualization-de-la-cantidad-de-items-en-stock--2MDwYV1COA6YuoiY22AyGo). 
 
-Aparecerá una tabla con los SKU y sus respectivos almacenes. La tabla está organizada de la siguiente manera:
+## Datos del stock
+
+En el Admin VTEX, accede a **Catálogo > Stock > Gestión de stock**, o escribe **Gestión de stock** en la barra de búsqueda en la parte superior de la página. Aparecerá una tabla con los SKU y sus respectivos almacenes. La tabla está organizada de la siguiente manera:
 
 * **Filas**: cada fila contiene la información de un SKU y un almacén. Esto te permite comprobar los detalles de cada SKU por almacén. 
 * **Columnas**: identifican diferentes aspectos del SKU en un almacén y se dividen en:
     * **Productos**: el nombre del producto.
     * **Almacén**: indica el almacén de la tienda en el que se encuentra el SKU.
     * **ID del SKU**: código que identifica el SKU.
-    * **Última actualización**: número de unidades del SKU más reciente registrado en la plataforma VTEX. <p>Puedes hacer clic en los valores de este campo para comprobar el **Registro de actualizaciones** y ver los datos de los usuarios que actualizaron el campo, las fechas en que se hicieron los cambios y las cantidades antes y después de las actualizaciones.</p>
+    * **Última actualización**: número de unidades del SKU más reciente registrado en la plataforma VTEX.<p><div class = "alert alert-info">Al hacer clic en cualquier valor en la columna <b>Última actualización</b>, se abrirá la ventana <a href="https://help.vtex.com/es/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2">Registro de actualizaciones</a> con datos de cambios. Cada fila corresponde a una actualización, y las columnas contienen el usuario que realizó el cambio, la fecha de la última actualización y la cantidad de ítems antes y después de la actualización. Solo puedes consultar las últimas 50 actualizaciones en el registro de un SKU.</div></p>
     * **Reservado**: unidades de ítems del SKU reservadas. Los pedidos de las reservas aún no tienen el pago aprobado. 
     Haz clic en los valores de esta columna para ver los detalles de los datos de las reservas del SKU y se te redirigirá a la gestión de pedidos. Para saber más sobre cómo consultar una reserva, consulta [Cómo seguir el status de la reserva](https://help.vtex.com/es/tutorial/how-does-reservation-work--tutorials_92#como-seguir-el-status-de-la-reserva).
     * **Enviados**: unidades del SKU enviadas. Los ítems de esta columna provienen de pedidos con status `Pago aprobado`, `Preparando entrega` o `Facturado`. <p>Al hacer clic en los ítems de la columna para ver los detalles de los SKU enviados, se te redirigirá a la gestión de pedidos.</p>
     * **Disponibles**: unidades del SKU disponibles para la venta.
     * **Actualizar recuento**: campo para actualizar manualmente la cantidad disponible de ítems del SKU. Para saber más sobre cómo actualizar el recuento, consulta el artículo [Cómo actualizar stock](https://help.vtex.com/es/tutorial/como-atualizar-estoque--2MDwYV1COA6YuoiY22AyGo).
     * **Stock infinito**: permite registrar unidades infinitas del SKU para que siempre esté disponible en el _checkout_ de tu tienda. Esto elimina la necesidad de actualizar el recuento del SKU.
+    * **Lead time (días):** configuración opcional del tiempo de envío al nivel de SKU. Al definir un tiempo para el SKU de un almacén, él se agregará al [cálculo de tiempo total de envío](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) del pedido. Por defecto, el [lead time](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) está definido como zero días y su contaje se realiza en días laborables. Puedes [alterarlo para días naturales](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional) y, si quieres configurar periodos en horas, minutos y segundos, puedes utilizar el endpoint [Update inventory by SKU and warehouse endpoint](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 <div class="alert alert-danger">
 Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el <a href="url">ID del SKU</a> no debe contener <b>el número cero a la izquierda</b>. Por ejemplo, el sistema no reconoce ID con el formato <code>01</code>, <code>02</code> , <code>021</code>, ya que espera el formato <code>1</code>, <code>2</code>, <code>21</code>.
 </div>
 
-### Filtros
+La cantidad total de ítems en la página **Gestión de stock** se actualiza en tiempo real, pero puede haber un retraso de hasta 1 hora para que la información aparezca en el [historial de movimientos](https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2).
 
-En la página **Gestión del stock**, puedes buscar los SKU en la barra de búsqueda y también aplicar filtros.
+### Filtros
 
-Para realizar una búsqueda en la barra, simplemente escribe el nombre o el ID de SKU y haz clic en <i class="fa-solid fa-magnifying-glass"></i> la lupa. Para utilizar los filtros, consulta los filtros disponibles:
+En la página **Gestión del stock**, para realizar una búsqueda en la barra, simplemente escribe el nombre o el ID de SKU y haz clic en <i class="fa-solid fa-magnifying-glass"></i> la lupa. Para utilizar los filtros, consulta los filtros disponibles:
 
 *   **Última actualización**: devuelve la cantidad actualizada de ítems en _stock_. Puedes ingresar un valor `Mayor o igual que`, `Menor o igual que` o `Entre` un rango de ítems. Si no ingresas ningún valor, `Todos` los ítems se muestran en la tabla.
 
diff --git a/docs/tutorials/es/managing-url-redirects.md b/docs/tutorials/es/managing-url-redirects.md
index f869fa542..fa3a17dfd 100644
--- a/docs/tutorials/es/managing-url-redirects.md
+++ b/docs/tutorials/es/managing-url-redirects.md
@@ -3,8 +3,8 @@ title: 'Gestión de redirecciones de URL'
 id: 3UJuFrU8imSVWg134mkvJV
 status: PUBLISHED
 createdAt: 2022-02-03T13:17:46.873Z
-updatedAt: 2023-03-24T22:07:21.230Z
-publishedAt: 2023-03-24T22:07:21.230Z
+updatedAt: 2023-11-14T18:03:08.019Z
+publishedAt: 2023-11-14T18:03:08.019Z
 firstPublishedAt: 2022-02-03T14:42:10.000Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,6 +15,10 @@ legacySlug: gestion-de-redirecciones-de-url
 subcategory: 1znnjA17XqaUNdNFr42PW5
 ---
 
+<div class="alert alert-warning" role="alert">
+Para crear, editar o eliminar redirecciones, el usuario del Admin VTEX debe tener un rol de acceso con el <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso de License Manager</a> <strong>CMS Settings</strong>. Puedes asignar al usuario un rol de acceso con el recurso siguiendo las instrucciones del artículo <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512#editando-usuarios">Gestionar usuarios</a>, o crear un nuevo rol de acceso que incluya dicho recurso consultando las instrucciones del artículo <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol">Roles</a>.
+</div>
+
 1. En el Admin VTEX, haz clic en **Storefront** > **Redirecciones**.
 2. Haz clic en `Nueva redirección`.
 3. Rellena los siguientes campos:
@@ -23,15 +27,21 @@ subcategory: 1znnjA17XqaUNdNFr42PW5
 4. En la casilla de selección, indica si la redirección es temporal o permanente. Si es temporal, debes definir la fecha de fin.
 5. Haz clic en `Guardar` para finalizar.
 
-![gerenciando redirecionamentos es 1](https://images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/ca2f417ea225d8d6875f37c31d0847a7/image5.png)
+![gerenciando redirecionamentos es 1](//images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/ca2f417ea225d8d6875f37c31d0847a7/image5.png)
+
 ## Importar redirección
 Para importar una redirección, sigue los pasos a continuación.
 
 1. Haz clic en <i class="fas fa-upload"></i> `Importar`.
-2. Selecciona el archivo CSV en tu computadora.
+2. Selecciona el archivo CSV en tu computadora, asegurándote de que utilice un punto y coma como separador (`;`).
 3. Haz clic en `Importar archivo`.
 4. Haz clic en  `Guardar` para finalizar.
 
+<div class="alert alert-warning" role="alert">
+Ten en cuenta que algunos editores pueden modificar automáticamente el separador. Por lo tanto, antes de importar un archivo, verifica que el formato del mismo sea CSV, y que el punto y coma (<code>;</code>) se utiliza como separador de valores. No se aceptarán archivos que utilicen otros separadores como comas (<code>,</code>) o espacio de tabulación (<code>&nbsp;&nbsp;</code>).<br><br>
+Algunos editores, como Google Sheets, exportan los archivos CSV con la coma (<code>,</code>) como separador predeterminado y es posible que no permitan el uso del punto y coma (<code>;</code>). En esos casos, se recomienda utilizar otros editores que permitan sustituir los separadores o guardar el archivo con el punto y coma (<code>;</code>) como separador.
+</div>
+
 ## Exportar redirección
 
 Si deseas exportar tus redirecciones, haz clic en <i class="fas fa-download"></i> `Exportar` y se descargarán a tu computadora.
diff --git a/docs/tutorials/es/managing-users-in-b2b-organizations.md b/docs/tutorials/es/managing-users-in-b2b-organizations.md
new file mode 100644
index 000000000..529a4d1d6
--- /dev/null
+++ b/docs/tutorials/es/managing-users-in-b2b-organizations.md
@@ -0,0 +1,68 @@
+---
+title: 'Gestión de usuarios en organizaciones B2B'
+id: 659ESiB9rjsR6Tg9KLl5He
+status: PUBLISHED
+createdAt: 2024-07-05T11:36:43.947Z
+updatedAt: 2024-07-05T13:50:41.743Z
+publishedAt: 2024-07-05T13:50:41.743Z
+firstPublishedAt: 2024-07-05T13:47:56.220Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gestion-de-usuarios-en-organizaciones-b2b
+locale: es
+legacySlug: gestion-de-usuarios-en-organizaciones-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+En una operación B2B en VTEX, los usuarios son personas autorizadas a acceder a la plataforma dentro de una organización B2B para:
+- Realizar pedidos.
+- Gestionar información.
+- Ejecutar tareas administrativas.
+
+La pestaña Usuarios en el Admin VTEX es clave para la gestión del acceso y operación de la plataforma en nombre de una organización. Definir a los usuarios y sus permisos garantiza operaciones seguras, alineadas con las responsabilidades y funciones específicas de cada miembro de la organización.
+
+En este artículo se describe cómo gestionar los usuarios:
+- [Agregar nuevos usuarios a la organización](#agregar-nuevos-usuarios-a-la-organización.).
+- [Editar usuarios](#editar-usuarios).
+- [Remover usuarios](#remover-usuarios).
+
+## Agregar nuevos usuarios a la organización
+Para agregar un nuevo usuario a la organización, sigue estos pasos:
+
+<ol>
+    <li>En el Admin VTEX, accede a <strong>Apps &gt; Organizaciones y centros de costos B2B &gt; Organizaciones</strong> o escribe <strong>Organizaciones</strong> en la barra de búsqueda en la parte superior de la página.</li>
+    <li>Haz clic en el nombre de la organización deseada para acceder a la página de Información de la organización.</li>
+    <li>Haz clic en la pestaña <strong>Usuarios</strong>.</li>
+    <li>Haz clic en <code>Nuevo</code>.</li>
+    <li>Rellena los datos del usuario según se detalla a continuación:
+        <ul>
+            <li><strong>Nombre:</strong> nombre completo del usuario.</li>
+            <li><strong>Email:</strong> email del usuario.</li>
+            <li><strong>Organización:</strong> nombre de la organización.</li>
+            <li><strong>Centro de costos:</strong> centro de costo al que se asociará el usuario.</li>
+            <li><strong>Rol:</strong> rol del usuario en la tienda virtual. Consulta más detalles sobre los roles disponibles en <a href="https://help.vtex.com/es/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA" target="_blank">Gestionar permisos en B2B Suite</a>.</li>
+        </ul>
+    </li>
+    <li>Haz clic en <code>Guardar</code>.</li>
+</ol>
+
+## Editar usuarios
+Para editar la información de un usuario existente, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones** o escribe **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de Información de la organización.
+3. Haz clic en la pestaña **Usuarios**.
+4. Haz clic en el usuario que deseas editar.
+5. Edita el **Rol**.
+6. Haz clic en `Guardar`.
+
+## Remover usuarios
+Para remover un usuario, sigue estos pasos:
+
+1. En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones** o escribe **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de Información de la organización.
+3. Haz clic en la pestaña **Usuarios**.
+4. Haz clic en el usuario que deseas remover.
+5. Haz clic en `Remover usuario`.
+
diff --git a/docs/tutorials/es/managing-users.md b/docs/tutorials/es/managing-users.md
index 138a954df..cb697aa1d 100644
--- a/docs/tutorials/es/managing-users.md
+++ b/docs/tutorials/es/managing-users.md
@@ -3,8 +3,8 @@ title: 'Gestionar usuarios'
 id: tutorials_512
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:09.608Z
-updatedAt: 2022-08-24T14:24:37.685Z
-publishedAt: 2022-08-24T14:24:37.685Z
+updatedAt: 2024-06-10T18:24:36.901Z
+publishedAt: 2024-06-10T18:24:36.901Z
 firstPublishedAt: 2017-04-27T23:03:28.211Z
 contentType: tutorial
 productTeam: Identity
@@ -15,25 +15,27 @@ legacySlug: creando-usuarios, gestionar-usuarios
 subcategory: 63DHe3VQEEE6Uuua8gIs2M
 ---
 
-La gestión de los usuarios con acceso al ambiente administrativo de su tienda VTEX se realiza a través de la [Gestión de la cuenta](/es/tutorial/visao-geral-do-modulo-license-manager/), en la sección de **Usuarios**. Para acceder a esta sección, vaya a __Gestión de la cuenta__ > __Usuarios__ en el panel izquierdo del Admin.
-![Menú Usuarios](https://images.ctfassets.net/alneenqid6w5/4ufKrojjLZwb8zBdD5xz7f/9c7276322c2b64435565f664830dbd89/Men___Usuarios.png)
+La gestión de los usuarios con acceso al ambiente administrativo de su tienda VTEX se realiza a través de la [Configuración de la cuenta](https://help.vtex.com/es/tutorial/vision-general-configuraciones-de-la-cuenta--6USYxLuzNt4uAkvjdPF7I8), en la página de **Usuarios**. Para acceder a esta sección, en la barra superior de VTEX Admin, haz clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
 
 En esta sección, se mostrará la lista de usuarios con sus respectivos __Nombre__, __Email__ y configuración de __MFA__. También pueden verse las presentes opciones de búsqueda, exportación y creación de nuevos usuarios, así como editar y eliminar usuarios.
-![Lista Usuários User Management ES](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
+
+![Lista Usuários User Management ES](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
+
+<div class="alert alert-warning">
+Cualquier usuario que desee gestionar usuarios o claves de aplicación debe tener un perfil que contenga el <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <b>Save User</b>. Puedes utilizar, por ejemplo, el perfil predeterminado <a href="https://help.vtex.com/es/tutorial/roles-de-usuario-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>.
+</div>
 
 ## Creando un nuevo usuario
 
-1. Acceda al módulo __Gestión de la cuenta__.
-2. Haga clic en la pestaña __Usuarios__.  
-![Menú Usuarios](https://images.ctfassets.net/alneenqid6w5/4ufKrojjLZwb8zBdD5xz7f/9c7276322c2b64435565f664830dbd89/Men___Usuarios.png)
-3. Haga clic en el botón __(+) Nuevo __.  
-![Botão Novo Usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/2MzlIdrqPecPcrnjeSMTTx/a677d46ec25ae71c650f4839c870a169/Bot__o_Novo_Usu__rio_User_Management_ES.png)
-4. Rellene el campo **Email**.  
-![Cadastro Novo usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/c25703eb8635123358251772d94e147a/Cadastro_Novo_usu__rio_User_Management_ES.png)
-5. Agregue los [roles](/es/tutorial/como-criar-perfil-de-acesso/) deseados.  
-![Selecionar perfis User Management ES](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/dc315c780a29a71e12efa19bdaaa8995/Selecionar_perfis_User_Management__ES.png)
-6. Haga clic en el botón **Guardar**.  
-![Botão Salvar Usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/707TZ7u4fRaSVGVDfaLcMC/624a61dd96c3bc51ebd92a09c07385b2/Bot__o_Salvar_Usu__rio_User_Management_ES.png)
+1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
+2. Haga clic en el botón `+ Nuevo`.  
+3. Rellene el campo **Email**.  
+  ![Cadastro Novo usuário User Management ES](//images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/c25703eb8635123358251772d94e147a/Cadastro_Novo_usu__rio_User_Management_ES.png)
+4. Haga clic en `+ Agregar roles`.
+5. Seleccione los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) deseados, como se muestra en la imagen: 
+  ![Selecionar perfis User Management ES](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/fed2df535522db7b5d7288845497b8d4/seleccionar-roles.PNG)
+6. Haga clic en `Agregar rol` para confirmar la selección.
+7. Haga clic en `Guardar`.  
 
 El usuario recibirá un email confirmando la creación, con un link para registrar una nueva contraseña de acceso.
 
@@ -41,13 +43,14 @@ La contraseña debe tener al menos 8 caracteres, incluyendo un número, una letr
 
 ## Editando usuarios
 
-Para editar un usuario ya registrado, solamente se debe hacer clic en su nombre. Esto también es posible haciendo clic en los tres puntos al lado derecho del usuario en la lista y luego en la opción **Editar**.
-![Botão Editar Usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/6063958f0625ce0beabac99f407a3b87/Bot__o_Editar_Usu__rio_User_Management_ES.png)
-
-El email no puede ser cambiado. Si desea hacer esto, se deberá realizar un nuevo registro.
-
-En la pantalla de edición, se pueden agregar o eliminar los [roles](/es/tutorial/como-criar-perfil-de-acesso/) de los usuarios.  
-![Selecionar perfis User Management ES](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/dc315c780a29a71e12efa19bdaaa8995/Selecionar_perfis_User_Management__ES.png)
+1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
+2. Para editar un usuario ya registrado, haga clic en su nombre. Esto también es posible haciendo clic en los tres puntos al lado derecho del usuario en la lista y luego en la opción **Editar**.
+  ![Botão Editar Usuário User Management ES](//images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/6063958f0625ce0beabac99f407a3b87/Bot__o_Editar_Usu__rio_User_Management_ES.png)
+  <div class="alert alert-warning" role="alert">El email no puede ser cambiado. Si desea hacer esto, se deberá realizar un nuevo registro.</div>
+3. En la pantalla de edición, se pueden agregar o eliminar los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) de los usuarios.  
+  ![Selecionar perfis User Management ES](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/fed2df535522db7b5d7288845497b8d4/seleccionar-roles.PNG)
+4. Haga clic en `Agregar rol` para confirmar la selección.
+5. Haga clic en `Guardar`.
 
 <div class="alert alert-info" role="alert">Aparecerá una alerta al agregar nuevos roles para un usuario que no utiliza autenticación de múltiples factores (MFA). El artículo <a href="https://help.vtex.com/es/tutorial/habilitar-login-por-autenticacao-de-2-fatores--4Ae1fcQi12g8u4SkQKCqWQ">Habilitar login por autenticación de 2 factores</a> muestra como habilitar esta configuración.</div>
 
@@ -55,17 +58,15 @@ En la pantalla de edición, se pueden agregar o eliminar los [roles](/es/tutoria
 
 ## Eliminando un usuario
 
-1. Para remover el acceso de un usuario, haga clic en botón con tres puntos al lado del usuario que desea eliminar.
-2. Haga clic en la opción **Eliminar**.  
-![Botão Excluir Usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/fe34b8820154abc988ee1317cf75da3a/Bot__o_Excluir_Usu__rio_User_Management_ES.png)
-3. Confirme haciendo clic en **SÍ, ELIMINAR TODO ACCESO**.  
-![Confirmar Remover Acesso User Management ES](https://images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/2e0ecc32f578b0da6f0698fb136a8a21/Confirmar_Remover_Acesso_User_Management_ES.png)
-
-<div class="alert alert-info">
-A pesar de que aparecen tokens de integración en la lista de usuarios, los mismos no pueden ser eliminados. Para desactivarlos, acceda a <em>Configuración de la cuenta> Gestión de la cuenta> Cuenta</em>, y desactive el campo <strong>Estado de los Tokens</strong>.
-</div>
+1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
+2. Para remover el acceso de un usuario, haga clic en botón con tres puntos <i class="fas fa-ellipsis-v"></i> al lado del usuario que desea eliminar.
+3. Haga clic en la opción **Eliminar**.  
+  ![Botão Excluir Usuário User Management ES](//images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/fe34b8820154abc988ee1317cf75da3a/Bot__o_Excluir_Usu__rio_User_Management_ES.png)
+4. Confirme haciendo clic en `SÍ, ELIMINAR TODO ACCESO`.  
+  ![Confirmar Remover Acesso User Management ES](//images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/2e0ecc32f578b0da6f0698fb136a8a21/Confirmar_Remover_Acesso_User_Management_ES.png)
 
-## Exportando datos de usuario
+## Exportando datos de usuarios
 
-1. Para exportar datos de usuario, haga clic en el botón **EXPORTAR**.
-2. Guarde el archivo csv en su dispositivo. El archivo contiene el id, el email y el nombre de cada usuario.
+1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
+2. Para exportar datos de usuarios, haga clic en el botón <i class="fas fa-download"></i> `Exportar`.
+3. Guarde el archivo CSV en su dispositivo. El archivo contiene el ID, el email y el nombre de cada usuario.
diff --git a/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md b/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
index d45c39f55..1b05e373f 100644
--- a/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
+++ b/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
@@ -172,7 +172,7 @@ Al concluir las etapas para rellenar la plantilla de mapeo, usted debe seguir lo
 1. Acceda al Admin.
 2. En el módulo Marketplace, haga clic en Integraciones.
 3. Seleccione la opción Configuración.
-4. En la integración Mercado Libre, haga clic en el engranaje<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />
+4. En la integración Mercado Libre, haga clic en el engranaje<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />
 5. Elija la opción **Carga de mapeo**.
 6. Seleccione la opción **Elegir un archivo**.
 7. Ahora, seleccione la plantilla de mapeo de categorías, atributos y variaciones de Mercado Libre.
diff --git a/docs/tutorials/es/marketplace-invited-sellers.md b/docs/tutorials/es/marketplace-invited-sellers.md
index 1ef9726a6..1a31e6290 100644
--- a/docs/tutorials/es/marketplace-invited-sellers.md
+++ b/docs/tutorials/es/marketplace-invited-sellers.md
@@ -27,7 +27,7 @@ Además de permitir enviar invitaciones, la página tiene una lista de sellers,
 
 Para que nuevos sellers se integren en su marketplace, es necesario realizar algunas acciones en su entorno VTEX: [Invitar](#invitar-seller) y [Conectar](#conectar-seller).
 
-![ES Seller invite](https://images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/7c9dd1931913f57b7bef76df6faad117/ES_seller_invite.jpg)
+![ES Seller invite](//images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/7c9dd1931913f57b7bef76df6faad117/ES_seller_invite.jpg)
 
 ## Invitar Seller
 
diff --git a/docs/tutorials/es/marketplace-overview.md b/docs/tutorials/es/marketplace-overview.md
index fec42fa5a..1223306a6 100644
--- a/docs/tutorials/es/marketplace-overview.md
+++ b/docs/tutorials/es/marketplace-overview.md
@@ -3,8 +3,8 @@ title: 'Visión General Marketplace'
 id: 40Zd0z9h2RXsM9uMUp3kEb
 status: PUBLISHED
 createdAt: 2023-03-31T19:13:35.911Z
-updatedAt: 2023-03-31T19:18:29.348Z
-publishedAt: 2023-03-31T19:18:29.348Z
+updatedAt: 2023-09-13T22:33:02.149Z
+publishedAt: 2023-09-13T22:33:02.149Z
 firstPublishedAt: 2023-03-31T19:18:29.348Z
 contentType: tutorial
 productTeam: Channels
@@ -21,8 +21,6 @@ Un _marketplace_ es una plataforma virtual a través de la cual diferentes vende
 
 Hemos agrupado todas las funcionalidades relacionadas con estas operaciones en el menú __Marketplace__ del Admin v4. 
 
-![Admin v4 marketplace menu ES](https://images.ctfassets.net/alneenqid6w5/5y304Ab4DxbE2GRKVihDjJ/388a33ea9aa96d9c3df4cb457342caec/Admin_v4_marketplace_menu_ES.jpg)
-
 A continuación, encontrarás más detalles sobre las diferentes secciones y páginas de este menú.
 
 ## Sellers
diff --git a/docs/tutorials/es/marketplace-strategies-at-vtex.md b/docs/tutorials/es/marketplace-strategies-at-vtex.md
index b76f22b69..df4821402 100644
--- a/docs/tutorials/es/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/es/marketplace-strategies-at-vtex.md
@@ -3,171 +3,185 @@ title: 'Estrategias de marketplace en VTEX'
 id: tutorials_402
 status: PUBLISHED
 createdAt: 2017-04-27T22:06:47.209Z
-updatedAt: 2023-04-20T20:53:42.948Z
-publishedAt: 2023-04-20T20:53:42.948Z
+updatedAt: 2024-06-20T20:13:23.276Z
+publishedAt: 2024-06-20T20:13:23.276Z
 firstPublishedAt: 2017-04-27T23:03:23.819Z
 contentType: tutorial
 productTeam: Channels
-author: 5l9ZQjiivHzkEVjafL4O6v
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: estrategias-de-marketplace-en-vtex
 locale: es
 legacySlug: integrando-con-marketplace
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-Un _marketplace_ es una plataforma virtual a través de la cual diferentes vendedores anuncian sus productos. Estos vendedores se denominan _sellers_; y, además de ser propietarios de los productos, son responsables por la entrega del producto al comprador.
+Un marketplace es una plataforma virtual en la que diferentes vendedores anuncian sus productos. Estos vendedores se denominan sellers y, además, de ser propietarios de los productos, muchas veces también son los responsables del [proceso de fulfillment del producto](https://help.vtex.com/es/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP).  
 
-<img src="https://drive.google.com/uc?export=download&id=1qT3lLaKflfnWyHknf7IgjNbRNCki9FuQ"/>
+![Estrategias de marketplace](//images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/9558d99b892b53aa723f408d29734435/Ecommerce_web_page-pana.png)
 
-[VTEX promueve la colaboración digital](https://vtex.com/ar-es/marketplace/) en diferentes escenarios. Usted no solo puede vender sus productos en otros _marketplaces_, sino que también puede vender productos de otros _sellers_ en su ambiente, convirtiéndose en un _marketplace_.
+[VTEX promueve la colaboración digital](https://vtex.com/ar-es/marketplace/) en diferentes escenarios: no solo tienes la posibilidad de vender tus productos en otros marketplaces, sino que también puedes ofrecer los productos de otros sellers en tu propio entorno, convirtiéndote así en un marketplace.  
 
-Además, VTEX permite gestionar todo desde un solo lugar mediante el concepto que llamamos «dashboard único». A través de la gestión unificada, puedes controlar el catálogo, precio, stock de tu B2C y varios canales para los que VTEX ofrece integración.
+Además, VTEX permite gestionar todo desde un único lugar mediante el concepto denominado one-single-panel. A través de la gestión unificada, puedes controlar el catálogo, precio, stock de tu B2C y varios canales para los que VTEX ofrece integración.  
 
-Algunas de las principales operaciones relacionadas con la venta de productos en los _marketplaces_ son:
+Algunas de las principales operaciones relacionadas con la venta de productos en marketplaces son:  
 
-- Control de_ stock_ en los múltiples canales.
-- Sincronización de promociones.
-- Procesamiento de pedidos.  
-- Gestión de los canales.
+- Control de stock en los múltiples canales  
+- Sincronización de promociones  
+- Procesamiento de pedidos  
+- Gestión de los canales  
 
-En VTEX, no hay ninguna tarifa adicional para la integración con los _marketplaces_. Tampoco hay ningún costo adicional para que una tienda VTEX anuncie productos de otros _sellers_ en su ambiente, o venda sus productos en otra tienda VTEX.
+La selección de productos enviados a un marketplace se define al elegir [la política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).  
+
+La [contratación de políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) se realiza a través de la apertura de un ticket en nuestro servicio de soporte, seleccionando la opción __Comercial__ y el tipo de solicitud “Creación de política comercial”. Se cobra una tarifa mensual por cada política comercial adicional, independientemente de si se utiliza para la integración con marketplaces certificados, partners, externos o VTEX.  
 
 <div class="alert alert-info">
-Los pedidos aprobados en los <i/>marketplaces</i> están sujetos a las mismas <a href="https://help.vtex.com/es/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">normas contractuales</a> de los pedidos realizados a través de otros canales.
+Los pedidos aprobados en los marketplaces están sujetos a las mismas <a href="https://help.vtex.com/es/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">normas contractuales</a> de pedidos realizados a través de otros canales.  
 </div>
 
-El surtido de productos enviados a un _marketplace_ se define al elegir su [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)* seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`.
+A continuación, abordaremos los siguientes escenarios:  
 
-La contratación de políticas comerciales adicionales para integración con un conector certificado, un conector partner u otras tiendas VTEX está exenta de la cuota mensual.
+- [Actuar como marketplace](#actuar-como-marketplace)
+- [Vender en un marketplace](#vender-en-un-marketplace)
+- [Seller Portal](#seller-portal)
 
-A continuación, abordaremos los siguientes escenarios:
+## Actuar como marketplace  
 
-- [Vender en un marketplace](#vender-en-un-marketplace)
-- [Actuar como un _marketplace_](#actuar-como-un-marketplace)
+La arquitectura de VTEX permite que las tiendas alojadas en su plataforma puedan anunciar productos de otras tiendas, ya sean de VTEX o no. Cuando una tienda de VTEX comienza a vender productos de sellers, se convierte en un marketplace VTEX.  
 
-## Vender en un marketplace
+Cuando tu tienda es el entorno donde otros sellers anuncian sus productos, te beneficias de esta relación. A continuación, se mencionan algunas de las principales ventajas de operar como un marketplace:  
 
-Los _marketplaces_ son espacios de venta donde los _sellers_ anuncian sus productos. Hay varias razones por las que vender en un _marketplace_ puede ser una ventaja estratégica, algunas de las principales son:
+- __Aumento de los ingresos:__ hay diferentes formas de monetización en un marketplace; la más común es recibir una comisión sobre las ventas realizadas en tu entorno.  
+- __Mayor surtido de productos:__ hay un aumento en la variedad de productos ofrecidos en tu tienda.  
+- __Alcance de nuevos clientes:__ los sellers atraen a nuevos clientes al marketplace y promueven así un mayor alcance de mercado y más visibilidad para tu marca.  
+- __Mejora de la experiencia de compra:__ al diversificar y ampliar tu variedad de productos, proporcionas una experiencia completa al cliente. Este puede comprar todo lo que necesita en un solo lugar (one-stop-shop).  
+- __Bajo costo:__ este proceso de colaboración no representa un aumento en tus costos. Es un modelo escalable que no requiere inversiones en áreas como stock, estructura o equipo porque la entrega de los productos es responsabilidad de los sellers.  
+- __Valorización de la reputación de tu marca:__ si tu tienda es reconocida en el mercado, significa que los productos ofrecidos en tu entorno cuentan con la confianza de los clientes. Puedes aumentar tus ganancias ofreciendo a los sellers un valor agregado para sus productos.  
 
-- **Visibilidad de su tienda:** la centralización de diversos _sellers_ y una gran variedad de productos en un _marketplace_ atrae un tráfico de usuarios elevado, y al anunciar sus productos en diferentes canales, usted permite que su marca gane visibilidad y sea conocida por nuevos públicos.
-- **Bajo costo:** cada _marketplace_ tiene sus propias contrapartidas financieras, la más practicada es el cobro de una comisión sobre las ventas. Es decir, si su tienda no vende, no tiene que pagar ninguna tarifa.
-- **Aumento de las ventas:** la estrategia de actuar en múltiples canales diversifica su fuente de ingresos y aumenta las oportunidades de conversión.
-- **Diversificación de nicho:** usted puede definir un surtido de productos específico para cada _marketplace_ y, a partir de eso, crear estrategias de validación de mercado o realizar ventas de temporada.
-- **Valor agregado al producto:** si el público no está familiarizado con su marca, resulta especialmente ventajoso aprovechar la relación de confianza que un _marketplace_ construyó con el cliente. Esto agrega valor a su producto y aumenta sus oportunidades de conversión.
+Una tienda VTEX puede vender productos de otros sellers en los siguientes casos:  
 
-En VTEX, usted puede vender en otros canales en las siguientes situaciones:
+- [Integrado con un seller externo](#integrado-con-un-seller-externo)  
+- [Ser un marketplace VTEX](#ser-un-marketplace-vtex)  
 
-- [Como seller VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#como-seller-vtex)
-- [Integrado con un Marketplace certificado](#integrado-con-un-marketplace-certificado)
-- [Integrado con un Marketplace partner](#integrado-con-un-marketplace-partner)
-- [Integrado con un marketplace externo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-marketplace-externo)
+### Integrado con un seller externo
 
-<div class="alert alert-info">
-Una tienda VTEX puede actuar simultáneamente como <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#como-seller-vtex">seller VTEX</a> e <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex">marketplace VTEX</a>.
-</div>
+Es posible que un seller que no está integrado con VTEX quiera vender productos en un marketplace VTEX. En este caso, podrían desarrollar un conector personalizado para esta integración. VTEX proporciona un conjunto de API e instrucciones para facilitar el proceso. Consulta más información en la [guía de integración con sellers externos](https://developers.vtex.com/vtex-developer-docs/docs/external-seller-integration-guide).
 
-<div class = "alert alert-info">
-La plataforma VTEX tiene diferentes funcionalidades de fulfillment, que se pueden combinar para escenarios como el <i>dropshipping</i>, cuando el seller recibe y envía el pedido del cliente a un tercero, que estará a cargo del fulfillment. La solución <a href="https://help.vtex.com/es/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP">logística</a> más adecuada para el seller dependerá de la arquitectura y su modelo de negocio, y puede realizarse a través de la <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integración de Back office (ERP/PIM/WMS)</a>.
-</div>
+### Como marketplace VTEX
 
-### Como seller VTEX
+La configuración para [convertirse en un marketplace VTEX](https://help.vtex.com/es/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) elimina algunos de los pasos requeridos en otras integraciones. Una vez configurado tu marketplace, consulta las [acciones para la operación de marketplaces VTEX](https://help.vtex.com/es/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev).  
 
-La arquitectura de VTEX permite que una tienda hospedada en su ambiente pueda anunciar sus productos en otras tiendas VTEX. Cuando una tienda VTEX vende sus productos en otra tienda VTEX, se denomina _seller_ VTEX. Más adelante veremos más información sobre una tienda que actúa como un [marketplace VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex), es decir, un ambiente que anuncia los productos de los sellers VTEX.
+A continuación, se presentan los principales marketplaces VTEX:  
+![mkt br](//images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
 
-La configuración de la [integración entre tiendas VTEX](https://help.vtex.com/es/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP) es sencilla y prescinde de algunos de los pasos requeridos en otras integraciones. Además, puede utilizar la página __Marketplaces e integraciones__, que reúne una especie de catálogo de interesados en alianzas, lo que facilita el contacto entre los _sellers_, _marketplaces_ de VTEX y conectores certificados (partners).
+Además, la página __Marketplaces e integraciones__ promueve y facilita el contacto entre marketplaces VTEX y marketplace certificados con sellers VTEX interesados en colaboraciones.  
 
-[Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) es una edición de la plataforma VTEX destinada a que los sellers se conecten y vendan sus productos en los marketplaces hospedados en VTEX. Con el portal, los sellers acceden a todas las funcionalidades esenciales para la operación del ecommerce en grandes vitrinas, aportando visibilidad y conversión de ventas.
+## Vender en un marketplace
 
-<div class = "alert alert-info">
-En VTEX, es posible actuar como un <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>, un seller no identificado por el consumidor en la experiencia de compra. Este tipo de seller es el estándar para las <a href="https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a>, por ejemplo, y puede ser estratégico para determinados modelos de negocio. Para más información, consulte el artículo <a href="https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Elegir entre cuenta estándar, cuenta franquicia o Seller Portal</a>.
-</div>
+Hay varias razones por las que vender en un marketplace puede ser una ventaja estratégica, algunas de las principales son:  
 
-### Integrado con un Marketplace certificado
-
-Existen _marketplaces_ de actuación nacional e internacional que son excelentes espacios para que promueva sus productos y potencie sus ventas. VTEX desarrolló sus propios conectores para la integración con algunos de los principales _marketplaces_, como Amazon, B2W y Magazine Luiza.
-
-En la actualidad, la plataforma VTEX cuenta con los siguientes conectores certificados:
-
-- [Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP)  
-- [Mercado Livre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq)
-- [Magazine Luiza](https://help.vtex.com/es/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y)
-- [Carrefour](https://help.vtex.com/es/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2)
-- [Centauro](https://help.vtex.com/es/tracks/integracao-com-a-centauro--D8Qnjbr5lfLkUfMRhsfbj)
-- [Facebook](https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc)
-- [Google Shopping](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw)
-- [Google Shopping Ads](https://help.vtex.com/es/tracks/como-fazer-campanhas-atraves-do-google-ads--47kz5PRQPK0IEaqGqiIuA)  
-- [Dafiti](https://help.vtex.com/es/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i)
-- [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm)
-- [Tik Tok](https://help.vtex.com/es/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd)
-- - [CSU (Opte+)](https://help.vtex.com/es/tutorial/integrando-com-csu-opte-2--tutorials_4258)
-- Zoom
-- Kabum
-- GPA
-- MadeiraMadeira
-- Riachuelo
-- Camicado
-- Renner
-- Loopi
-- GrupoLTM
-- TudoAzul
-- Webcontinental
-- Farfetch
+__- Visibilidad de tu tienda:__ al centralizar a diversos sellers y ofrecer una amplia variedad de productos en un marketplace, atraes un flujo constante de usuarios, y al promocionar tus productos en distintos canales, aumentas la visibilidad de tu marca y la das a conocer a nuevos públicos.  
+- __Bajo costo:__ cada marketplace tiene sus propias contrapartidas financieras, la más practicada es el cobro de una comisión sobre las ventas. Es decir, si no vendes, no tienes que pagar ninguna tarifa al marketplace.  
+- __Aumento de las ventas:__ la estrategia de actuar en múltiples canales diversifica tu fuente de ingresos y aumenta las oportunidades de conversión.  
+- __Diversificación de nicho:__ puedes definir un surtido de productos específico para cada marketplace, y a continuación crear estrategias de validación de mercado o realizar ventas de temporada.  
+- __Valor agregado al producto:__ si el público no está familiarizado con tu marca, resulta especialmente ventajoso aprovechar la relación de confianza que un marketplace construyó con el cliente. Esto agrega valor a tu producto y aumenta tus oportunidades de conversión.  
 
-<div class="alert alert-info">
-  Aunque Facebook, Google Shopping, Google Shopping Ads y TikTok no son <i>marketplaces</i>, incluimos sus conectores en esta lista porque ofrecen una experiencia similar de envío de productos desde las tiendas VTEX.
-</div>  
+### Tipos de marketplaces
+
+Existen marketplaces tanto a nivel nacional como internacional que son excelentes plataformas para promocionar tus productos y aumentar tus ventas.  
 
-Para realizar la integración del conector, puedes obtener ayuda en el material que guía el proceso de configuración y también, como cliente VTEX, tienes a tu disposición nuestro soporte en caso de dificultades.
+Actuando como seller en VTEX, puedes realizar la integración con cuatro tipos diferentes de marketplaces: certificados, partners, externos y de VTEX.  
 
-Para obtener información sobre cómo un _marketplace_ externo se puede unir al [plan comercial](https://vtex.com/ar-es/partner/) y obtener la certificación de partner, consulte el artículo [Convertirse en un conector certificado (partner)](https://help.vtex.com/es/tutorial/tornar-se-um-conector-certificado-parceiro--66mnclLFVFolMBGNtZbKzt).
+Para realizar la integración con un marketplace y recibir orientación en el proceso de configuración, consulta los contenidos mencionados anteriormente. Además, como cliente VTEX, dispones de nuestro soporte en caso de enfrentar alguna dificultad.  
 
-### Integrado con un Marketplace partner
+En VTEX, puedes vender en otros canales en las siguientes situaciones:  
 
-Hay integraciones externas que fueron desarrolladas en conjunto con hubs partners. 
+- [Integrado con un marketplace externo](#integrado-con-un-marketplace-externo)  
+- [Integrado con un marketplace certificado](#integrado-con-un-marketplace-certificado)  
+- [Integrado con un marketplace partner](#integrado-con-un-marketplace-partner)
+- [Como seller VTEX](#como-seller-vtex)  
 
-- Americanas
-- Via Varejo
-- Shopee
-- [Wish](https://help.vtex.com/es/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4)  
-- Olist
-- Conecta Lá
-- Anymarket
-- TudoAzul
-- Easy Live
-- Mimo
-- Wap Store
-- Plugg.to
-- Fast Shop
-- Hubplus
+<div class="alert alert-info">
+Una tienda VTEX puede actuar simultáneamente como <a href="#vender-en-un-marketplace">seller VTEX</a> y <a href="#actuar-como-marketplace">marketplace VTEX</a>.
+La plataforma VTEX tiene diferentes funcionalidades de fulfillment que se pueden combinar para escenarios como el dropshipping, es decir, cuando el seller recibe y envía el pedido del cliente a un tercero que estará a cargo del fulfillment. La solución logística más adecuada para el seller dependerá de la arquitectura y su modelo de negocio, y puede realizarse a través de la <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integración de Back office (ERP/PIM/WMS)</a>.
+</div>
 
 ### Integrado con un marketplace externo
 
-En caso de que su tienda desee vender en un _marketplace_ que no tiene conexión con VTEX, puede desarrollar un conector personalizado para la integración. VTEX proporciona un conjunto de API e instrucciones para facilitar el proceso. Para saber más, consulte la [guía de integración con marketplaces externos](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide).
+En caso de que tu tienda desee vender en un marketplace que no tiene conexión con VTEX, puedes desarrollar un conector personalizado para la integración. VTEX proporciona un conjunto de API e instrucciones para facilitar el proceso. Para saber más, consulta la [guía de integración con marketplaces externos](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide).  
 
-## Actuar como un marketplace
+### Integrado con un marketplace certificado
 
-Además de los beneficios descritos en el contexto de la venta en un _marketplace_, existe la posibilidad de que su tienda sea el ambiente donde los _sellers_ anuncian sus productos. Algunas de las principales ventajas de actuar como un _marketplace_ son:
+Los marketplaces certificados son aquellos cuya integración ha sido desarrollada por el equipo de desarrolladores de VTEX. Con la política comercial adicional contratada para este tipo de integración, estás exento de la tarifa mensual si hay pedidos asociados a dicha política a través del marketplace certificado. En este caso, solo pagarás la comisión por pedidos (take rate).  
 
-- **Aumento de los ingresos:** hay diferentes formas de monetización en un _marketplace_, la más común es recibir una comisión sobre las ventas realizadas en su ambiente. 
-- **Mayor surtido de productos:** hay un aumento en la variedad de productos ofrecidos en su tienda.
-- **Alcance de nuevos clientes:** los _sellers_ atraen a nuevos clientes al _marketplace_ y promueven así un mayor alcance de mercado y más visibilidad para su marca.
-- **Mejora de la experiencia de compra:** al diversificar y ampliar su variedad de productos, usted proporciona una experiencia completa al cliente. Este puede comprar todo lo que necesita en un solo lugar _(one-stop-shop)_.
-- **Bajo costo:** el proceso de colaboración no representa un aumento en sus costos. Es un modelo escalable que no requiere inversiones en áreas como _stock_, estructura o equipo, porque la entrega de los productos es responsabilidad de los _sellers_.
-- **Valorización de la reputación de su marca:** si su tienda es reconocida en el mercado, significa que los productos ofrecidos en su ambiente cuentan con la confianza de los clientes. Usted puede aumentar sus lucros ofreciendo a los _sellers_ un valor agregado para sus productos.
+<div class="alert alert-warning">
+Las políticas comerciales adicionales contratadas para la integración con marketplaces certificados que también se utilicen en la integración con otros tipos de marketplaces estarán sujetas al cobro de la tarifa mensual.
+</div>
 
-Una tienda VTEX puede vender productos de otros _sellers_ en los siguientes casos:
+Actualmente, la plataforma VTEX cuenta con los siguientes marketplaces certificados:  
+
+- [Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP)  
+- [Mercado Libre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq)  
+- [Magazine Luiza](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y)  
+- [Carrefour](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2)  
+- [Centauro](https://help.vtex.com/pt/tracks/integracao-com-a-centauro--D8Qnjbr5lfLkUfMRhsfbj)  
+- [Dafiti](https://help.vtex.com/pt/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i)  
+- [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm)  
+- [Zoom](https://help.vtex.com/pt/tutorial/integrando-com-zoom--2OoQjigCVOIEWWkgOqwCK6?&utm_source=autocomplete)  
+- [CSU (Opte+)](https://help.vtex.com/pt/tutorial/integrando-com-csu-opte-2--tutorials_4258)  
+- [MadeiraMadeira](https://help.vtex.com/pt/tutorial/integracao-com-madeiramadeira--J4QCENKiz4urYNfaMuE0i)  
+- [Riachuelo](https://help.vtex.com/pt/tutorial/integracao-com-riachuelo--kpfxAgwEcANihHLT4iW81)  
+- [Camicado](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)  
+- [Renner](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)  
+- [Enjoei](https://help.vtex.com/tutorial/integracao-com-enjoei--3mV9uhw1AdqFol8K2tfwly)  
+- [Wish](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4)  
+- Kabum  
+- Grupo LTM  
+- TudoAzul  
+- GPA  
+- Climario  
+- Juntoz  
+- SMPlaces  
+- Farfetch  
+- Falabella  
+- Linio  
+
+### Integrado con un marketplace partner
+
+Los marketplaces partners son aquellos cuya integración ha sido desarrollada por un grupo de desarrolladores partners de VTEX. La política comercial adicional contratada para este tipo de integración está sujeta a una tarifa mensual y a la comisión por pedidos (take rate).  
+
+Consulta a continuación los marketplaces partners disponibles en el catálogo de VTEX:  
+
+- Americanas  
+- Via Varejo  
+- [Shopee](https://help.vtex.com/pt/tutorial/integracao-com-a-shopee-beta--5OV9idUY6fHu3P8grnCnqj)  
+- [Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc)  
+- [Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw)  
+- [Google Shopping Ads](https://help.vtex.com/pt/tracks/como-fazer-campanhas-atraves-do-google-ads--47kz5PRQPK0IEaqGqiIuA)  
+- [Tik Tok](https://help.vtex.com/pt/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd)  
+- [Livelo](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/5rhGcaM0SedoK7lDMBkVFD)  
+- Olist  
+- Anymarket  
+- Easy Live  
+- Mimo  
+- Wap Store  
+- Plugg.to  
+- Fast Shop  
+- Hubplus  
 
-- [Ser un marketplace VTEX](#ser-un-marketplace-vtex)
-- [Integrado con un seller externo](#integrado-con-un-seller-externo)
+<div class="alert alert-info">
+Aunque Facebook, Google Shopping, Google Shopping Ads y TikTok no son marketplaces, ofrecen una experiencia similar de envío de productos desde las tiendas VTEX.
+</div>
 
-### Ser un marketplace VTEX
+### Como seller VTEX
 
-La arquitectura de VTEX permite que las tiendas hospedadas en su plataforma anuncien productos de otras tiendas, tanto de VTEX como externas. Cuando una tienda VTEX comienza a vender productos de los _sellers_, se convierte en un marketplace VTEX.
+La arquitectura de VTEX permite que una tienda alojada en tu plataforma anuncie sus productos en otras tiendas VTEX. Se denomina seller VTEX a una tienda VTEX que vende sus productos en otra tienda VTEX. En puntos anteriores proporcionamos información sobre [marketplaces VTEX](#actuar-como-marketplace), aquellas tiendas que actúan como el entorno donde se anuncian los productos de sellers VTEX.  
 
-La [configuración de marketplaces VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) es sencilla y prescinde de algunos de los pasos necesarios en otras integraciones. Una vez hecha la configuración necesária, sepa más en [Acciones para la operación de marketplaces VTEX](https://help.vtex.com/es/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev#gerenciar-pedidos).
+La configuración de la [integración entre tiendas VTEX](https://help.vtex.com/es/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP) es sencilla y elimina algunos  pasos requeridos en otras integraciones. Además, puedes hacer uso del módulo de __Marketplaces e integraciones__, que ofrece un catálogo de marketplaces interesados en colaboraciones, facilitando el contacto entre sellers VTEX, marketplaces VTEX y marketplaces certificados.  
 
-Además, existe una página denominada __Marketplaces e integraciones__, que promueve y facilita el contacto entre los _marketplaces_ y _sellers_ de VTEX y los conectores certificados interesados en las colaboraciones.
+## Seller Portal
 
-### Integrado con un seller externo
+[Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) es una edición de la plataforma VTEX destinada a que los sellers se conecten y vendan sus productos en marketplaces alojados en VTEX. A través de este portal, los sellers acceden a todas las funcionalidades esenciales para la operación del ecommerce en grandes vitrinas, aportando visibilidad y conversión de ventas.  
 
-Es posible que un _seller_ que no está integrado con VTEX quiera vender productos en un marketplace VTEX. En este caso, ellos podrían desarrollar un conector personalizado para esta integración. VTEX proporciona un conjunto de APIs e instrucciones para facilitar el proceso. Vea más información en la [guía de integración con sellers externos](https://developers.vtex.com/vtex-developer-docs/docs/external-seller-integration-guide).
+<div class="alert alert-info">
+En VTEX, es posible actuar como un <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>, un seller no identificado por el consumidor en la experiencia de compra. Este tipo de seller es el estándar para las <a href="https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a>, por ejemplo, y puede ser estratégico para determinados modelos de negocio. Para más información, consulta el artículo <a href="https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Elegir entre cuenta estándar, cuenta franquicia o Seller Portal</a>.
+</div>
diff --git a/docs/tutorials/es/marketplaces-and-integrations.md b/docs/tutorials/es/marketplaces-and-integrations.md
index 49684b5e1..511214931 100644
--- a/docs/tutorials/es/marketplaces-and-integrations.md
+++ b/docs/tutorials/es/marketplaces-and-integrations.md
@@ -3,8 +3,8 @@ title: 'Marketplaces e integraciones'
 id: 5AcBO1t29nhq7rBHas9b6V
 status: PUBLISHED
 createdAt: 2023-04-18T13:51:54.217Z
-updatedAt: 2023-05-04T18:59:04.105Z
-publishedAt: 2023-05-04T18:59:04.105Z
+updatedAt: 2024-02-19T20:19:40.774Z
+publishedAt: 2024-02-19T20:19:40.774Z
 firstPublishedAt: 2023-05-03T17:09:07.242Z
 contentType: tutorial
 productTeam: Channels
@@ -33,7 +33,7 @@ Si quieres actuar como marketplace VTEX, lee el artículo <a href="https://help.
 
 Para acceder a la página, en el Admin VTEX haz clic en *__Marketplace > Conexiones > Marketplaces e integraciones__*. Esta página, además de ofrecer sugerencias de marketplaces a los que conectarse, muestra la lista completa de todos los marketplaces disponibles o ya conectados.  
 
-![Marketplaces e integraciones](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
+![Marketplaces e integraciones](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
 
 La tabla donde figuran los marketplaces consta de las siguientes columnas:  
 
diff --git a/docs/tutorials/es/master-data.md b/docs/tutorials/es/master-data.md
index 646f60998..6342d05db 100644
--- a/docs/tutorials/es/master-data.md
+++ b/docs/tutorials/es/master-data.md
@@ -3,8 +3,8 @@ title: 'Master Data'
 id: 4otjBnR27u4WUIciQsmkAw
 status: PUBLISHED
 createdAt: 2018-04-02T19:01:38.026Z
-updatedAt: 2023-05-23T14:24:05.123Z
-publishedAt: 2023-05-23T14:24:05.123Z
+updatedAt: 2024-06-07T20:19:30.086Z
+publishedAt: 2024-06-07T20:19:30.086Z
 firstPublishedAt: 2018-04-02T20:54:18.272Z
 contentType: tutorial
 productTeam: Master Data
@@ -19,7 +19,7 @@ Master Data es una solución de la plataforma VTEX para el banco de datos que no
 
 Por defecto, Master Data se usa para almacenar y organizar los datos de los clientes de tu tienda. Cuenta con un potente motor de búsqueda que te permite almacenar, buscar, expandir y personalizar datos.
 
-En este artículo, encontrarás más detalles sobre cada versión disponible del Master Data, así como conceptos importantes y cómo utilizarlo.
+En este artículo, encontrarás más detalles sobre cada versión disponible de Master Data, así como conceptos importantes y cómo utilizarlo.
 
 <div class="alert alert-info">
 Ten en cuenta que, según la funcionalidad y la versión que desees utilizar, se recomienda ponerse en contacto con el equipo de desarrollo de tu operación.
@@ -27,135 +27,216 @@ Ten en cuenta que, según la funcionalidad y la versión que desees utilizar, se
 
 ## Versiones disponibles
 
-Actualmente existen dos versiones disponibles y puedes elegir la que mejor se adapte a las necesidades de tu operación. La principal diferencia entre ambas es que la v2 no incluye interfaz gráfica, por lo que se puede usar solo a través de la [API del Master Data v2]](https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview), pero sí tiene otras funcionalidades importantes, por ejemplo, [esquemas JSON](https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema).
+Actualmente existen dos versiones disponibles y puedes elegir la que mejor se adapte a las necesidades de tu operación. La principal diferencia entre ambas es que la v2 no incluye interfaz gráfica, por lo que se puede usar solo a través de la [API del Master Data v2](https://developers.vtex.com/docs/api-reference/master-data-api-v2), pero sí tiene otras funcionalidades importantes, por ejemplo, [esquemas JSON](https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema).
 
 <div class = "alert alert-info">
-a plataforma VTEX guarda de forma nativa los datos de los clientes de tu tienda en Master Data v1.
+La plataforma VTEX guarda de forma nativa los datos de los clientes de tu tienda en Master Data v1.
 </div>
 
 En la tabla a continuación, obtendrás más información sobre las diferencias en las funcionalidades de cada versión.
 
+<div style="overflow: auto;">
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><b>Funcionalidad</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>v1</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>v2</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>Más información</b>
-   </td>
+  <thead class="bb b--muted-3">
+    <tr>
+    <th class="t-body fw5 pa5" style="min-width: 10rem;">Funcionalidad
+    </th>
+    <th class="t-body fw5 pa5" style="min-width: 10rem;">v1
+    </th>
+    <th class="t-body fw5 pa5" style="min-width: 10rem;">v2
+    </th>
+    <th class="t-body fw5 pa5" style="min-width: 10rem;">Más información
+    </th>
   </tr>
+</thead>
+<tbody>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Interfaz gráfica
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">-
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Interfaz gráfica
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">-
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">API
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v1-overview">Master Data v1 API</a></li> 
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview">Master Data v2 API</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">API
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="https://developers.vtex.com/docs/api-reference/masterdata-api" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Master Data v1
+            API</a></li>
+        <li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Master Data v2
+            API</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Importing and exporting spreadsheets
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Yes
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"> <ul><li><a href="https://help.vtex.com/en/tutorial/importing-data-into-master-data--tutorials_1135#"> Importar datos en Master Data</a></li><li><a href="https://help.vtex.com/es/tutorial/exporting-data--tutorials_1125#">Exportar datos de Master Data</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Importar y exportar plantillas
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Yes
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="https://help.vtex.com/es/tutorial/importing-data-into-master-data--tutorials_1135" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer"> Importar datos
+            en Master Data</a></li>
+        <li><a href="https://help.vtex.com/es/tutorial/exporting-data--tutorials_1125" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Exportar datos de Master
+            Data</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"> Anexos (imágenes)
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">-
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;"> Anexos (imágenes)
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">-
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Triggers
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#triggers”>Triggers</a></li><li><a href="https://help.vtex.com/es/tutorial/creating-trigger-in-master-data--tutorials_1270#">Crear trigger en Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2">Crear trigger en Master Data v2</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Triggers
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="#triggers" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Triggers</a></li>
+        <li><a href="https://help.vtex.com/es/tutorial/creating-trigger-in-master-data--tutorials_1270" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Crear trigger
+            en Master Data v1</a></li>
+        <li><a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Crear trigger
+            en Master Data v2</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Esquemas JSON
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="http://json-schema.org/">Esquemas JSON</a></li><li><a href="https://spacetelescope.github.io/understanding-json-schema">Qué son los esquemas JSON</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema">Comienza a trabajar con los esquemas JSON en el Master Data</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/master-data-schema-lifecycle">Ciclo de vida del esquema en el Master Data</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Esquemas JSON
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="http://json-schema.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Esquemas JSON</a></li>
+        <li><a href="https://json-schema.org/understanding-json-schema" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Qué son los esquemas JSON</a></li>
+        <li><a
+            href="https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+            target="_blank" rel="noopener noreferrer">Empieza
+            a trabajar con los esquemas JSON en Master Data</a></li>
+        <li><a href="https://developers.vtex.com/vtex-rest-api/docs/master-data-schema-lifecycle" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Ciclo de vida del
+            esquema en Master Data</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Propiedades anidadas
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#nested-properties”>Propiedades anidadas</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Propiedades anidadas
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="#nested-properties" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Propiedades anidadas</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Entidades de datos
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Se nombran con acrónimos compuestos de dos letras mayúsculas. Por ejemplo, la entidad `CL` almacena los datos de los clientes de la tienda, y la `AD`, los domicilios. No se puede crear con de API.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Se los llama por sus nombres. Por ejemplo, `Client` y `Address`. Solo se puede crear con de API.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#data-entities”>Entidades de datos</a></li><li><a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265">Entidades de datos en Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/creating-relationships-between-data-entities-using-api">Crear relaciones entre entidades de datos del Master Data v2</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Entidades de datos
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Se nombran con acrónimos compuestos de dos letras mayúsculas. Por
+      ejemplo, la entidad `CL` almacena los datos de los clientes de la tienda, y la `AD`, los domicilios. No se puede
+      crear con de API.
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Se los llama por sus nombres. Por ejemplo, `Notification`.
+      Solo se puede crear con de API.
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="#data-entities" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Entidades de datos</a></li>
+        <li><a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Entidades de datos en
+            Master Data v1</a></li>
+        <li><a
+            href="https://developers.vtex.com/vtex-rest-api/docs/creating-relationships-between-data-entities-using-api" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+            target="_blank" rel="noopener noreferrer">Crear
+            relaciones entre entidades de datos de Master Data v2</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Campos
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Se deben rellenar en el formato específico configurado en la entidad de datos.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No hay restricción de campos y formatos. La validación del formato se hace a través de los esquemas JSON.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos">Tipos de campos en Master Data v1</a></li><li><a href=”#v2-esquemas”>Esquemas JSON</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Campos
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Se deben rellenar en el formato específico configurado en la
+      entidad de datos.
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No hay restricción de campos y formatos. La validación del formato
+      se hace a través de los esquemas JSON.
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a
+            href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+            target="_blank" rel="noopener noreferrer">Tipos
+            de campos en Master Data v1</a></li>
+        <li><a href="#v2-esquemas" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Esquemas JSON</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Índices
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://help.vtex.com/es/tutorial/setting-up-an-index-on-master-data--tutorials_785">Configurar índices en Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/reference/putindices">Configurar índices con la API de Master Data v2</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Índices
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="https://help.vtex.com/es/tutorial/setting-up-an-index-on-master-data--tutorials_785" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Configurar
+            índices en Master Data v1</a></li>
+        <li><a href="https://developers.vtex.com/vtex-rest-api/reference/putindices" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">Configurar índices con la API de Master Data v2</a></li>
+      </ul>
+    </td>
   </tr>
   <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">VTable
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">No
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sí
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://developers.vtex.com/vtex-rest-api/docs/vtable">VTable</a></li></ul>
-   </td>
+    <td class="t-body pa5" style="min-width: 10rem;">VTable
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">No
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">Sí
+    </td>
+    <td class="t-body pa5" style="min-width: 10rem;">
+      <ul style="padding-inline-start: 0px;">
+        <li><a href="https://developers.vtex.com/vtex-rest-api/docs/vtable" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+          target="_blank" rel="noopener noreferrer">VTable</a></li>
+      </ul>
+    </td>
   </tr>
 </table>
 
@@ -165,7 +246,7 @@ Las entidades de datos de ambas versiones son independientes, aunque algunas pue
 
 ## Componentes básicos
 
-Ambas versiones del Master Data usan algunos componentes básicos que pueden ser iguales a conceptos encontrados en otras soluciones de base de datos con otros nombres, por ejemplo, registro o tabla. A continuación, encontrarás más detalles sobre:
+Ambas versiones de Master Data usan algunos componentes básicos que pueden ser iguales a conceptos encontrados en otras soluciones de base de datos con otros nombres, por ejemplo, registro o tabla. A continuación, encontrarás más detalles sobre:
 - [Entidades de datos](#entidades-de-datos)
 - [Documentos](#documentos)
 - [Campos](#campos)
@@ -175,7 +256,7 @@ Ambas versiones del Master Data usan algunos componentes básicos que pueden ser
 
 Las entidades de datos son como tablas donde se registran documentos y campos.
 
-Se hace referencia a las entidades de datos del Master Data v1 con acrónimos compuestos de dos letras mayúsculas. En la v2, puedes usar el nombre de la entidad de datos. Por ejemplo, en la v1, la entidad `CL` almacena los datos de los clientes de la tienda, y la entidad `AD` guarda datos de los domicilios de los clientes. En la v2, las entidades equivalentes se llaman `Client` y `Address`.
+Se hace referencia a las entidades de datos en Master Data v1 con acrónimos compuestos de dos letras mayúsculas. En la v2 puedes usar el nombre de la entidad de datos. Por ejemplo, en la v1, la entidad `CL` almacena los datos de los clientes de la tienda, y la entidad `AD` guarda datos de los domicilios de los clientes. En la v2, las entidades equivalentes se llaman `Client` y `Address`.
 
 En una entidad de datos, la información se estructura en [documentos] (#documentos) y [campos](#campos).
 
@@ -189,17 +270,17 @@ Cada documento tiene un ID que la plataforma genera automáticamente durante la
 
 ### Campos
 
-Se denomina «campos» a los atributos que componen los documentos del Master Data. Si comparamos las entidades de datos con tablas, podríamos imaginar que los campos son las columnas de la tabla.
+Se denomina «campos» a los atributos que componen los documentos de Master Data. Si comparamos las entidades de datos con tablas, podríamos imaginar que los campos son las columnas de la tabla.
 
 Por ejemplo, en una entidad donde se guardan datos de clientes de la tienda, por ejemplo, `CL` o `Client`, podemos rellenar los campos como **nombre**, **email**, **fecha de nacimiento** y **documento**.
 
-En el Master Data v1, los campos se deben rellenar en el formato específico configurado en la entidad de datos. Obtén más información sobre los [tipos de campo en Master Data v1](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos).
+En Master Data v1, los campos se deben rellenar en el formato específico configurado en la entidad de datos. Obtén más información sobre los [tipos de campo en Master Data v1](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265).
 
 En la v2, no hay restricción de campos ni formatos. La validación del formato se hace a través de [esquemas JSON](#v2-schemas).
 
 ### Propiedades anidadas
 
-La v2 del Master Data te permite estructurar los datos con propiedades anidadas, una estructura que se suele encontrar en el formato [JSON](https://www.json.org/json-en.html). Este concepto consiste en la posibilidad de crear campos compuestos a partir de otros campos para una mejor estructuración de los datos. Por ejemplo, un perfil de cliente puede tener el campo `Documento` que, a la vez, incluye las propiedades `Tipo` y `Número`. También puedes crear [triggers](#triggers) anidados.
+La v2 de Master Data te permite estructurar los datos con propiedades anidadas, una estructura que se suele encontrar en el formato [JSON](https://www.json.org/json-en.html). Este concepto consiste en la posibilidad de crear campos compuestos a partir de otros campos para una mejor estructuración de los datos. Por ejemplo, un perfil de cliente puede tener el campo `Documento` que, a la vez, incluye las propiedades `Tipo` y `Número`. También puedes crear [triggers](#triggers) anidados.
 
 ### Índices
 
@@ -210,7 +291,7 @@ Como se dijo anteriormente, cada documento tiene un ID que la plataforma genera
 Por ejemplo, puedes consultar un documento con información de un cliente especificando el valor del campo `email` del cliente.
 
 <div class = "alert alert-info">
-Obtén más información sobre cómo <a href=”https://help.vtex.com/es/tutorial/setting-up-an-index-on-master-data--tutorials_785”>configurar índices en el Master Data v1</a> o <a href=”https://developers.vtex.com/vtex-rest-api/reference/putindices”>configurar índices con la API del Master Data v2</a>.
+Obtén más información sobre cómo <a href=https://help.vtex.com/es/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices en Master Data v1</a> o <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>configurar índices con la API del Master Data v2</a>.
 </div>
 
 ## Triggers
@@ -220,19 +301,19 @@ Un trigger del Master Data es un mecanismo que ejecuta una acción después de l
 - Enviar email.
 - Guardar documento en otra entidad de datos.
 
-Obtén más información sobre cómo [configurar triggers en el Master Data v1] (https://help.vtex.com/pt/tutorial/criando-trigger-no-master-data--tutorials_1270) o cómo [configurar triggers con la API de Master Data v2](https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2)
+Obtén más información sobre cómo [configurar triggers en el Master Data v1] (https://help.vtex.com/es/tutorial/criando-trigger-no-master-data--tutorials_1270) o cómo [configurar triggers con la API de Master Data v2](https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2)
 
 ## v2 esquemas
 
-Con la v2 del Master Data, puedes definir formatos de datos con esquemas JSON. Este formato indica cómo el Master Data debe validar e indexar los documentos.
+Con la v2 de Master Data puedes definir formatos de datos con esquemas JSON. Este formato indica cómo Master Data debe validar e indexar los documentos.
 
 <div class = "alert alert-info">
-Obtén más información en <a href=”https://json-schema.org/”>esquemas JSON</a>.
+Obtén más información en <a href=https://json-schema.org/>esquemas JSON</a>.
 </div>
 
 Puedes guardar un documento en cualquier entidad de datos si el contenido es un JSON válido. Una entidad de datos puede tener asociados o no varios esquemas JSON.
 
-![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/3b032813aed32ec745e01d4d32cf4e87/schemas_es.jpg)
+![Master Data schemas](//images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/3b032813aed32ec745e01d4d32cf4e87/schemas_es.jpg)
 
 <div class = "alert alert-info">
 Un documento puede ser compatible con varios esquemas JSON, o con ninguno.
@@ -240,7 +321,7 @@ Un documento puede ser compatible con varios esquemas JSON, o con ninguno.
 
 ## Aplicaciones
 
-Ambas versiones del Master Data son extremadamente flexibles, lo cual te permite cubrir diversas necesidades de tu tienda. A continuación, puedes ver algunos ejemplos de cómo se aplican las funcionalidades del Master Data.
+Ambas versiones de Master Data son extremadamente flexibles, lo cual te permite cubrir diversas necesidades de tu tienda. A continuación, puedes ver algunos ejemplos de cómo se aplican las funcionalidades de Master Data.
 
 ### Pruebas A/B
 
@@ -250,7 +331,7 @@ Cómo configurar [pruebas A/B con Master Data v2](https://developers.vtex.com/vt
 
 ### Carrito abandonado
 
-El Master Data también puede usarse para crear integraciones de carrito abandonado. Es decir, la realización de acciones automáticas cuando un cliente agrega productos al carrito de tu tienda y termina su sesión sin finalizar la compra.
+Master Data también puede usarse para crear integraciones de carrito abandonado. Es decir, la realización de acciones automáticas cuando un cliente agrega productos al carrito de tu tienda y termina su sesión sin finalizar la compra.
 
-Para obtener más información, consulta esta guía sobre [configuración de carrito abandonado](https://help.vtex.com/pt/tutorial/configurar-carrinho-abandonado--tutorials_740)
+Para obtener más información, consulta esta guía sobre [configuración de carrito abandonado](https://help.vtex.com/es/tutorial/configurar-carrinho-abandonado--tutorials_740)
 
diff --git a/docs/tutorials/es/match-offers-mercado-livre.md b/docs/tutorials/es/match-offers-mercado-livre.md
new file mode 100644
index 000000000..8698d53e0
--- /dev/null
+++ b/docs/tutorials/es/match-offers-mercado-livre.md
@@ -0,0 +1,131 @@
+---
+title: 'Match de anuncios de Mercado Libre'
+id: 1C4HjNLbNk2Y6evD0luXMr
+status: PUBLISHED
+createdAt: 2024-05-06T21:14:40.722Z
+updatedAt: 2024-06-20T21:30:01.461Z
+publishedAt: 2024-06-20T21:30:01.461Z
+firstPublishedAt: 2024-05-06T21:49:40.831Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: match-de-anuncios-de-mercado-libre
+locale: es
+legacySlug: match-de-anuncios-mercado-livre
+subcategory: 
+---
+
+<div class="alert alert-info">
+Esta funcionalidad está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro equipo de <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">soporte</a>
+</div>  
+
+Al realizar la [integración con Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), el seller envía al marketplace los anuncios que desea vender en la plataforma. De este modo, Mercado Libre ofrece al seller oportunidades de match con anuncios de tipo **catálogo**, que pueden ocupar un espacio resaltado en el marketplace.
+
+Antes de continuar, es importante familiarizarse con las definiciones específicas de la funcionalidad **Match de anuncios de Mercado Libre** descritas a continuación:  
+
+| **Término** | **Significado** |
+|:---:|:---:|
+| **Anuncios** | Un anuncio es un [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) de un seller enviado al marketplace con precio y stock configurados. |
+| **Canal de ventas** | Marketplace en el que el seller anuncia sus productos. |
+| **Catálogo Mercado Libre** | Anuncio preexistente en Mercado Libre que permite al seller vincular su producto y mejorar su visibilidad. |
+| **Oportunidades** | Una **oportunidad** es un producto del seller que se puede vincular a un producto del catálogo de Mercado Libre. El objetivo de la oportunidad es proporcionar al seller una herramienta que pueda realizar la asociación entre los productos. |
+
+En este artículo, puedes explorar los siguientes temas:  
+
+- [Estructura de la página](#estructura-de-la-pagina)  
+- [Tipos de oportunidades](#tipos-de-oportunidades)  
+- [Analizar oportunidades](#analizar-oportunidad)  
+
+![overview-match-anuncios-meli](//images.ctfassets.net/alneenqid6w5/1H13oiY7fPnalkV6rn7fY2/9f50b70e2f52e4f14fa70104b085c6cc/overview-match-anuncios-meli-pt.png)
+
+## Estructura de la página
+
+La página **Match de anuncios Mercado Libre** tiene dos pestañas: [Oportunidades](#pestana-oportunidades) y [Catálogos activos](#pestana-catalogos-activos). A continuación se describen los datos disponibles en cada una.  
+
+### Pestaña Oportunidades
+
+En esta pestaña, se muestra una lista de los anuncios elegibles para el catálogo de Mercado Libre y las oportunidades se pueden filtrar por tipo y canal de ventas, si utilizas la integración **Mercado Livre Classic** y **Mercado Livre Premium**. También puedes buscar oportunidades ingresando el nombre del producto o el ID de SKU en la barra de búsqueda.  
+
+Cada fila de la lista corresponde a un anuncio y presenta la siguiente información en columnas:  
+
+- **Casilla de selección:** casilla utilizada para seleccionar los anuncios deseados y realizar la acción `Aceptar sugerencia`.  
+- **Tu anuncio:** producto del catálogo VTEX configurado por el seller y enviado al marketplace.  
+- **Sugerencia de catálogo:** producto del catálogo sugerido por Mercado Libre.  
+- **Oportunidad:** tipo de acción para el anuncio del seller indicada por Mercado Libre.  
+- **Analizar oportunidad:** botón que redirige al seller a la página [Analizar oportunidad](#analizar-oportunidad).  
+
+### Pestaña Catálogos activos
+
+En esta pestaña se muestra una lista de los anuncios actualmente vinculados al catálogo de Mercado Libre y permite filtrar anuncios por su status de relevancia y buscar por nombre de producto o ID de SKU.  
+
+En la lista de catálogos activos, cada fila corresponde a un anuncio y presenta la siguiente información en columnas:  
+
+- **Anuncio:** nombre y especificaciones del producto.  
+- **SKU ID:** ID de SKU del producto.  
+- **Status:** relevancia del anuncio en el catálogo de Mercado Libre.  
+- **Analizar oportunidad:** botón que redirige al seller a la página [Analizar oportunidad](#analizar-oportunidad).  
+
+En la parte superior de la pantalla, se muestra el número de catálogos activos que están en cada status de relevancia.  
+
+![relevancia](//images.ctfassets.net/alneenqid6w5/4ktn7U1Dbqt7AhwdK1gtGn/3749ff23cf3e871dd8ae50941f806ae1/relevancia-pt.png)
+
+<div class=”alert alert-info>
+Los anuncios adquieren relevancia cuando ofrecen mejores precios y condiciones logísticas.
+</div>
+
+La relevancia de un anuncio registra si la oferta del seller se muestra como la primera oferta del catálogo en el marketplace. Los posibles status de una oferta son:  
+
+- **Ganando relevancia:** el anuncio del seller está en primer lugar o en empate con el primero.  
+- **Perdiendo relevancia:** el anuncio del seller no está en primer lugar en la búsqueda de ese producto.  
+- **Procesando relevancia:** Mercado Libre está evaluando la información del anuncio.  
+
+## Tipos de oportunidades
+
+Los tres tipos de oportunidades que pueden mostrarse para los anuncios de un seller son: **Preaviso, Requerido** y **Opcional**. En todas las oportunidades listadas por Mercado Libre, el seller puede vincular el producto a un anuncio. Si el anuncio del seller no tiene una correspondencia con una oferta del catálogo, debe abrirse un ticket con el equipo de soporte de Mercado Libre.  
+
+- **Preaviso:** este tipo de oportunidades son obligatorias y tienen un plazo para ser vinculadas. Esto quiere decir que el seller deberá asociar el producto a una oferta del catálogo de Mercado Libre. Si no se realiza la asociación en el plazo determinado por Mercado Libre, el marketplace moderará el anuncio del seller.  
+![aviso](//images.ctfassets.net/alneenqid6w5/ZuWyKDvUpqIS4BEUzdnnd/3cc4b009ff17e214ac5f6914b680ae2c/Captura_de_tela_2024-04-30_184708.png)
+
+- **Requerido:** este tipo de oportunidades son obligatorias, pero no tienen un plazo para asociarlas. Si no se vincula el anuncio, Mercado Libre puede moderar el anuncio del seller en el marketplace.  
+![anuncio obligatorio](//images.ctfassets.net/alneenqid6w5/62kOh7xJ7zOxc8StS33BA/b12e5711b67e4597a5161cf676e69c15/obrigatorio-pt.png)
+
+- **Opcional:** este tipo de oportunidades son opcionales. Si no se realiza la asociación, el anuncio del seller no pierde relevancia ni será moderado por el marketplace.  
+![anuncio opcional](//images.ctfassets.net/alneenqid6w5/3Df2PgW8zBl7GKh32W0L07/c6ef9e482d18a074a5e93dc9e9e93204/opcional-pt.png)
+
+## Analizar oportunidad
+
+En la pestaña **Oportunidades**, se pueden analizar y vincular las oportunidades independientemente del tipo. La asociación se puede realizar [individualmente](#asociacion-individual) o en [masa](#asociacion-en-masa).
+
+Para analizar una oportunidad, el seller utiliza la página **Match de anuncios**, a la que se puede acceder a través del ***Admin VTEX > Marketplace > Mercado Libre > Match de anuncios** o escribiendo **Match de anuncios** en la barra de búsqueda del Admin VTEX.  
+
+La pantalla **Analizar oportunidad** se muestra cuando el seller hace clic en el botón `Analizar oportunidad` de uno de los anuncios disponibles en la pestaña **Oportunidades**.  
+En el lado izquierdo de esta pantalla se muestra el producto registrado del seller en el catálogo VTEX y en el lado derecho el producto del catálogo de Mercado Libre sugerido para la asociación.  
+![análisis de anuncios](//images.ctfassets.net/alneenqid6w5/3hEW8BHsxqSQ6DZFsyn29n/566860d4c95d6ea12073abdcf838ecb2/sugestao-individual-ii-pt.png)
+
+### Asociación individual
+
+Para asociar las oportunidades individualmente, sigue los pasos a continuación desde la página **Match de anuncios**:  
+
+1. En la oportunidad deseada, haz clic en el botón **`Analizar oportunidad`**.  
+2. Comprueba que los datos del anuncio sugerido por Mercado Libre sean compatibles con los datos de tu producto.  
+3. Haz clic en el botón `Aceptar sugerencia`.  
+4. Haz clic en el botón `Confirmar`.  
+![aceptar sugerencia individual](//images.ctfassets.net/alneenqid6w5/1QKVIvkdadoicf7TsjfhRQ/b5de58ececcf925df1090c4b96f8d081/sugestao-individual-pt.png)
+
+Después de realizar la asociación, el anuncio se publica en el catálogo de Mercado Libre y se envía a la pestaña **Catálogos activos** con el status **Procesando relevancia**.  
+
+Si los productos no coinciden, el seller debe buscar un anuncio del catálogo de Mercado Libre que corresponda a su producto para asociarlo.  
+
+Para buscar otros anuncios en el catálogo de Mercado Libre, el seller debe ingresar el nombre de su producto en la barra de búsqueda que está debajo de la foto principal del producto en la página **`Analizar oportunidad`**.  
+![búsqueda de anuncios](//images.ctfassets.net/alneenqid6w5/2T5bvbMUTF9BeOGdIYtJ58/829ebd40c08e4ecdfde73902f32e917a/Captura_de_tela_2024-04-30_194057.png)
+
+### Asociación en masa
+
+Para asociar las oportunidades en masa, sigue los pasos a continuación desde la página **Match de anuncios**:  
+
+1. Selecciona las oportunidades que deseas asociar. En la parte inferior de la pantalla se muestra un panel con el número de oportunidades seleccionadas.  
+2. Haz clic en el botón `Aceptar sugerencias`.  
+3. Haz clic en el botón `Confirmar`.  
+![sugerencia-masiva](//images.ctfassets.net/alneenqid6w5/52VZCcnHAOMdyA1GWrFpH/982157da7e94b3b5dd80e171d5090c61/sugestao-massiva-pt.png)
+
+Después de realizar la asociación, los anuncios se publican en el catálogo de Mercado Libre y se envían a la pestaña **Catálogos activos** con el status **Procesando relevancia**.  
diff --git a/docs/tutorials/es/media-overview.md b/docs/tutorials/es/media-overview.md
index 671d2ab43..8a223d74b 100644
--- a/docs/tutorials/es/media-overview.md
+++ b/docs/tutorials/es/media-overview.md
@@ -3,8 +3,8 @@ title: 'Multimedia - Visión general'
 id: 31fhjHTt4TBoo50AmGQ9b2
 status: PUBLISHED
 createdAt: 2023-05-29T23:26:35.354Z
-updatedAt: 2023-05-31T12:29:38.226Z
-publishedAt: 2023-05-31T12:29:38.226Z
+updatedAt: 2024-07-03T19:28:25.937Z
+publishedAt: 2024-07-03T19:28:25.937Z
 firstPublishedAt: 2023-05-30T18:01:54.161Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,10 +15,15 @@ legacySlug: multimedia-vision-general
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-En el módulo Multimedia puedes gestionar los archivos multimedia de tu tienda, como imágenes y gifs. Puedes cargar y organizar archivos multimedia en los siguientes formatos: `PNG`, `JPG`, `GIF`, `SVG` y `WEBP`.
-![Multimedia Visión general](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4b7fca26bb4f3b1f72d3a6fff9eca887/es-multimedia-overview.png)
+En la página Multimedia puedes gestionar los archivos multimedia de tu tienda, tales como imágenes y videos. Para las imágenes puedes cargar y organizar archivos de hasta 5 MB en los siguientes formatos: `png`, `jpg`, `gif`, `svg` y `webp`, mientras que para los videos puedes agregar una URL del proveedor de videos hospedado externamente como YouTube o Vimeo.
 
-Además, Multimedia está integrado con **Site Editor** y **Headless CMS**. Esta integración te permite acceder y gestionar Multimedia directamente a través de las soluciones de CMS de VTEX.
+<div class="alert alert-warning">
+Para cargar, los archivos deben tener una extensión en minúsculas, por ejemplo, <code>store.png</code>, y el límite de tamaño de archivo para cargar en Multimedia es de <b>5 MB</b>.
+</div>
+
+![Multimedia Visión general](//images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4b7fca26bb4f3b1f72d3a6fff9eca887/es-multimedia-overview.png)
+
+demás, Multimedia está integrada con **Site Editor** y **Headless CMS**. Esta integración te permite acceder y gestionar archivos multimedia directamente a través de las soluciones de CMS de VTEX.
 
 En esta guía aprenderás a:
 
@@ -28,48 +33,102 @@ En esta guía aprenderás a:
 ## Acceder a Multimedia
 Hay tres formas de acceder al módulo Multimedia:
 
-- **Multimedia**: En el Admin VTEX, haz clic en **Storefront > Multimedia**. 
+- **Multimedia**: en el Admin VTEX, haz clic en **Storefront > Multimedia**. 
 
-- **Site Editor** (para tiendas que utilizan Store Framework): en el Admin VTEX, ve a **Storefront > Site Editor**, elige un bloque que contenga una imagen (por ejemplo, Carrusel) y haz clic en `Agregar`.  Se abrirá un modal.
+- **Site Editor** (para tiendas que utilizan Store Framework): en el Admin VTEX, ve a **Storefront > Site Editor**, elige un bloque que contenga una imagen (por ejemplo, Carrusel) y haz clic en `Agregar nuevo`.  Se abrirá un panel.
 
-- **Headless CMS**: en el Admin VTEX, entra en **Storefront > Headless CMS** y elige una de las páginas creadas, como una página de producto. De las secciones disponibles, selecciona una en la que puedas agregar una imagen (por ejemplo, Hero). Haz clic en el componente de imagen de Hero y se abrirá un modal.
+- **Headless CMS**: en el Admin VTEX, accede a **Storefront > Headless CMS** y elige una de las páginas creadas, como una página de producto. De las secciones disponibles, selecciona una en la que puedas agregar una imagen, como por ejemplo, [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero). Haz clic en el componente de imagen Hero y se abrirá un panel de Multimedia.
 
-En la siguiente imagen tendrás acceso a una visión general de la interfaz Multimedia y las acciones disponibles para gestionar tus archivos multimedia:
+<div class="alert alert-warning">
+Ten en cuenta que la sección debe utilizar la <a href="https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms">media-gallery</a> para beneficiarse de Multimedia. Para proyectos de <a href="https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore">FastStore</a>, las secciones que utilizan el widget media-gallery son <a href="https://developers.vtex.com/docs/guides/faststore/organisms-navbar">Navbar</a> y <a href="https://developers.vtex.com/docs/guides/faststore/organisms-hero">Hero</a>.
+</div>
 
-![Multimedia Features](https://images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/db95f45451326e0664992cefa1cd8a6f/es-multimedia-features.png)
+En la siguiente imagen se muestra una visión general de la interfaz de Multimedia y las acciones disponibles para gestionar tus archivos multimedia:
+
+![Multimedia Features](//images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/db95f45451326e0664992cefa1cd8a6f/es-multimedia-features.png)
 
 | Campo | Descripción |
 | ---------- | ------------- |
 | **I - Campo de búsqueda** | Encuentra los archivos disponibles en Multimedia. |
-| **II - Ordenar por** | clasifica cómo se muestran los archivos en la interfaz en función de los filtros: `Más recientes`, `Más antiguos`, `Nombre (A-Z)` y `Nombre (Z-A)`. |
+| **II - Ordenar por** | Clasifica cómo se muestran los archivos en la interfaz en función de los filtros: `Más reciente`, `Más antiguo`, `Nombre (A-Z)` y `Nombre (Z-A)`. |
 | **III - Paginación** | Navega por las páginas de archivos disponibles. |
-| **IV - Modo de visualización** |	Elige el modo de visualización de los archivos: `Ver en lista` o `Ver en cuadrícula`. |
-| **V - Agregar imagen** | carga un nuevo archivo desde tu dispositivo. |
+| **IV - Modo de vista** |	Elige el modo de visualización de los archivos: `Ver en lista` o `Ver en cuadrícula`. |
+| **V - Agregar nuevo** | Carga un nuevo archivo desde tu dispositivo. |
 
 ## Gestión de archivos en Multimedia
 Consulta las secciones a continuación sobre las acciones disponibles para gestionar archivos en Multimedia:
 
-### Cargar archivos en Multimedia
-1. En la página **Multimedia**, haz clic en `Agregar nuevo`.
+### Agregar imágenes
+
+En Multimedia puedes cargar imágenes en los siguientes formatos: `png`, `jpg`, `gif`, `svg` y `webp`. El límite de tamaño de los archivos es 5 MB. Para cargar una imagen a tu tienda, sigue los pasos a continuación:
+
+1. En la página o panel de **Multimedia**, haz clic en `Agregar nuevo` y luego en `Imagen`.
+
+<div class="alert alert-warning">
+  <p>En el panel de Multimedia de Headless CMS y en Site Editor, puedes arrastrar y soltar imágenes.</p>
+</div>
+
 2. Elige en tu dispositivo la imagen que deseas agregar y haz clic en `Abrir`.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Recuerda que en Multimedia se admiten los siguientes formatos: <i>PNG</i>, <i>JPG</i>, <i>GIF</i>, <i>SVG</i>, and <i>WEBP</i>.
+<div class="alert alert-warning">
+Recuerda que en Multimedia se admiten los siguientes formatos: <code>png</code>, <code>jpg</code>, <code>gif</code>, <code>svg</code>, y <code>webp</code>, en minúsculas y con un límite de tamaño de archivo de 5 MB.
 </div>
 
-3. Una vez cargada la imagen, aparecerá un mensaje de éxito. Ahora, puedes realizar otras operaciones haciendo clic en `Más acciones` (tres puntos verticales) en la imagen en miniatura y eligiendo una de las siguientes acciones:
+3. Una vez cargada la imagen, aparecerá un mensaje de éxito. 
+
+Ahora, puedes realizar otras operaciones haciendo clic en `Más acciones` (tres puntos verticales) en la imagen en miniatura y eligiendo una de las siguientes acciones:
 
 | Campo | Descripción |
 | ---------- | ------------- |
-| **Ver** | Abre la imagen en una nueva página. |
+| **Vista previa** | Abre la imagen en una nueva página. |
 | **Copiar URL** | Copia la URL de la imagen para poder utilizarla en otras secciones de tu tienda. |
 | **Descargar** | Descarga la imagen en tu computadora. |
 | **Eliminar** |	Elimina la imagen del repositorio. |
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Si eliminas la imagen solo se borrará del repositorio de Multimedia. Si agregaste la imagen a un componente Hero, por ejemplo, seguirá utilizándose para este componente,  pero no podrá utilizarse en otros.
+<div class="alert alert-warning">
+Si eliminas la imagen solo se borrará del repositorio de Multimedia. Si agregaste la imagen a un componente Hero, por ejemplo, seguirá utilizándose en ese componente, pero no podrá utilizarse en otros.
 </div>
 
-### Cancelar una carga en Multimedia
+### Agregar videos
+Además de imágenes, Multimedia te permite almacenar videos que puedes utilizar en tu sitio web para crear un atractivo visual para los usuarios que naveguen por la tienda.
+
+1. En la página **Multimedia**, haz clic en `Agregar nuevo` y luego en `Video`.
+2. En la ventana modal, rellena el nombre y la URL del video según corresponda.
+
+- **Nombre del video:** ingresa un nombre para el video que te ayude a identificarlo en la galería.
+- **URL del video:** ingresa la URL del video
+
+3. Haz clic en `Agregar video`.
+
+Una vez agregado el video, puedes decidir cómo deseas utilizarlo haciendo clic en el menú `⋮` en la miniatura del video:
+
+- **Copiar URL:** obtén la dirección URL del video que se debe utilizar en la tienda a través de Headless CMS.
+- **Abrir video:** abre una vista previa del video en una nueva pestaña del navegador.
+- **Eliminar:** elimina el video de tu galería.
+
+### Agregar un video al contenido en Headless CMS
+
+Integrar contenido multimedia, como videos, en Headless CMS puede optimizar la experiencia del usuario en tu sitio web. Sigue los pasos a continuación para agregar videos a tu tienda.
+
+1. En el Admin VTEX, accede a **Storefront > Headless CMS**.
+2. Selecciona el [proyecto](https://help.vtex.com/es/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) al que deseas agregar el video.
+3. Selecciona la página a la que deseas agregar el video. Por ejemplo: **Inicio**.
+4. Con la página **Inicio** abierta, en la pestaña **Secciones**, agrega (`+`) una sección que tenga el widget media-gallery, como por ejemplo, **Hero**.
+5. Escoge una **Sección** que tenga el widget `media-gallery`. Por ejemplo, Hero.
+6. En Hero, rellena los siguientes campos:
+
+- **Dirección URL:** pega la URL que copiaste en Multimedia.
+- **Descripción del video:** descripción del video por accesibilidad.
+
+7. Haz clic en `Guardar`.
+8. Si deseas verificar tus cambios antes de publicarlos, haz clic en `Vista previa`.
+
+### Cancelar una carga
+
+- **Imágenes**
+
 Si estás cargando una nueva imagen y no deseas continuar, puedes cancelar haciendo clic en la `X` superpuesta a la imagen en miniatura.
 
+- **Videos**
+
+Después de cargar un video, pasa el mouse sobre la miniatura del video, haz clic en el menú (`⋮`) y selecciona **Eliminar**. Si el video ya se está siendo utilizado en alguna parte de tu tienda, seguirá disponible ahí, pero no estará disponible para uso futuro.
diff --git a/docs/tutorials/es/mercado-libre-promotions.md b/docs/tutorials/es/mercado-libre-promotions.md
index cf84bfeb5..c4d805f4e 100644
--- a/docs/tutorials/es/mercado-libre-promotions.md
+++ b/docs/tutorials/es/mercado-libre-promotions.md
@@ -21,7 +21,7 @@ Para proporcionar mayor agilidad a la operación del seller, en la barra de bús
 
 Para acceder a la página de promociones disponibles en el Admin VTEX, debes ir a __Marketplace > Mercado Libre > Promociones.__  
 
-![Promociones de Mercado Libre](https://images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
+![Promociones de Mercado Libre](//images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
 
 ## Tipos de promociones
 
diff --git a/docs/tutorials/es/mercado-libre-size-chart.md b/docs/tutorials/es/mercado-libre-size-chart.md
new file mode 100644
index 000000000..08627acfd
--- /dev/null
+++ b/docs/tutorials/es/mercado-libre-size-chart.md
@@ -0,0 +1,132 @@
+---
+title: 'Tabla de tallas de Mercado Libre'
+id: 5dCc9IJ83SjllG75BVCWnr
+status: PUBLISHED
+createdAt: 2024-07-23T20:28:35.058Z
+updatedAt: 2024-07-23T21:11:23.954Z
+publishedAt: 2024-07-23T21:11:23.954Z
+firstPublishedAt: 2024-07-23T21:11:23.954Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: tabla-de-tallas-de-mercado-libre
+locale: es
+legacySlug: tabla-de-tallas-de-mercado-libre
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+La tabla de tallas permite a los clientes saber el tamaño aproximado del producto que desean comprar, brindándoles así una mejor experiencia al momento de seleccionar el tamaño de un producto. Al informar detalladamente las tallas del producto, evitas devoluciones y reclamos por tamaño incorrecto.  
+
+Al recibir menos devoluciones, tu reputación en Mercado Libre mejora junto con la exposición de tus productos. La tabla de tallas está disponible para los productos de las categorías **calzado, top clothes** y **bottom clothes**. Las tallas aparecen en centímetros (cm).  
+
+La tabla de tallas es personalizable, lo que significa que puedes seleccionar opciones de tabla que se ajusten a tus necesidades, que incluyen las tallas de cada tamaño del producto disponible.  
+
+## Agregar tabla personalizada
+
+Para agregar una tabla de tallas personalizada, debes seguir los pasos a continuación:  
+
+1. Accede al Admin VTEX y ve a **Marketplace > Conexiones > Marketplace e integraciones**.  
+2. Selecciona la integración con **Mercado Libre**.  
+3. Selecciona la opción `Realizar mapeo`. Se abrirá una nueva ventana con la interfaz de mapeo.  
+4. En la sección **Tabla de medidas**, haz clic en el ícono +.  
+5. Selecciona la opción **Tabla personalizada**.  
+6. Ingresa un nombre válido para tu tabla en el campo **Nombre de la tabla**.  
+7. En el campo **Dominio**, selecciona la opción para tu tabla personalizada.  
+8. En el campo **Género**, selecciona la opción correspondiente al género del producto. Existen siete tipos de géneros:  
+   - **Femenino**  
+   - **Masculino**  
+   - **Niñas**  
+   - **Niños**  
+   - **Bebés**  
+   - **Sin género**  
+   - **Sin género infantil**  
+9. En el campo **Tamaño principal**, escoge la opción de modelo de tabla. Hay cinco modelos diferentes:  
+   - **BR:** utiliza las tallas estándar en Brasil.  
+   - **Tamaño de la marca:** utiliza las tallas estándar de la marca del producto seleccionado.  
+   - **US:** utiliza las tallas estándar de los tamaños en Estados Unidos. Las tallas pueden variar según el género.  
+   - **EU:** utiliza las tallas estándar de los tamaños en la Unión Europea.  
+   - **UK:** utiliza las tallas estándar de los tamaños en el Reino Unido.  
+10. En el campo **Template**, haz clic en CSV. Se descargará una plantilla de la tabla que deberás completar según las instrucciones de la sección [Completar la plantilla de la tabla de tallas](#completar-la-plantilla-de-la-tabla-de-tallas).
+
+## Completar la plantilla de la tabla de tallas
+
+Debes enviar una **tabla de tallas** para cada categoría mapeada. Todas las columnas de la tabla deben estar rellenadas. Si decides no utilizar algunas tallas estándar, rellena el valor con un `-`.  
+En esta plantilla debes configurar las columnas y completarlas con los valores de los tamaños y medidas en centímetros de los respectivos tamaños.  
+
+Para configurar la plantilla automáticamente, accede a **Datos> Texto en columnas** en el menú de Excel, selecciona la opción **Delimitado** y haz clic en Siguiente. En el campo **Delimitadores**, selecciona la opción **Coma**, haz clic en __Siguiente__, y termina haciendo clic en __Finalizar__.  
+
+### Tabla de calzado
+
+La plantilla de la tabla de tallas para calzado tiene las siguientes columnas:  
+
+| Columna | Descripción | Contenido |
+| :---- | :---- | :---- |
+| **Foot Length** | Medida en centímetros del tamaño del pie. | Completa cada fila con la medida en centímetros de las tallas que rellenarás en las siguientes columnas. Ejemplo: 45 cm. |
+| **Foot Length to** | Medida en centímetros del tamaño máximo que debe tener el pie para acomodar la talla respectiva. | Completa cada fila con las medidas máximas en centímetros de las tallas que rellenarás en las siguientes columnas. Ejemplo: 50 cm. |
+| **Manufacturer Size** | Se refiere al tamaño estándar de un producto según las especificaciones del fabricante.. | Rellena cada fila con la medida estándar de la marca del producto. |
+| **BR Size** | Número de la medida estándar de la talla en Brasil. | Rellena cada fila con la talla correspondiente seguido de BR. Ejemplo: 38 BR. |
+| **US Size** | Número de la medida estándar de la talla en Estados Unidos. Las medidas pueden variar según el género. | Rellena cada fila con la talla correspondiente seguido de US. Ejemplo: 24 US. |
+| **EU Size** | Número de la medida estándar del tamaño en la Unión Europea. | Rellena cada fila con la talla correspondiente seguido de EU. Ejemplo: 38 EU. |
+| **UK Size** | Número de la medida estándar de la talla en el Reino Unido. | Rellena cada fila con la talla correspondiente seguido de UK. Ejemplo: 12 UK. |  
+
+### Tabla de top clothes
+
+La plantilla de la tabla de tallas para ropa de la parte superior tiene las siguientes columnas:  
+
+| Columna | Descripción | Contenido |
+| :---: | ----- | ----- |
+| **Size** | Talla de la ropa. | Rellena cada fila con las tallas de la ropa. Ejemplo: L. |
+| **Filtrable_size** | Talla filtrable disponible para la categoría. | Rellena cada fila con la talla disponible para filtrar. Ejemplo: XL.  |
+| **Chest_circumference_from** | Circunferencia del pecho (tórax). Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima del tórax para la talla en centímetros. Ejemplo: 80 cm. |
+| **Chest_circumference_to** | Circunferencia del pecho (tórax). Fin del intervalo de medidas. | Rellena cada fila con la medida máxima del tórax para la talla en centímetros. Ejemplo: 88 cm. |
+| **Waist_circumference_from** | Circunferencia de la cintura. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la anchura de la cintura en centímetros. Ejemplo: 70 cm. |
+| **Waist_circumference_to** | Circunferencia de la cintura. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la anchura de la cintura en centímetros. Ejemplo: 77 cm. |
+| **Person_height_from** | Altura de la persona. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la altura de una persona en centímetros. Ejemplo: 168 cm. |
+| **Person_height_to** | Altura de la persona. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la altura de una persona en centímetros. Ejemplo: 178 cm. |
+| **Hip_circumference_from** | Circunferencia de la cadera. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la anchura de la cadera en centímetros. Ejemplo: 109 cm. |
+| **Hip_circumference_to** | Circunferencia de la cadera. Fin del intervalo de medidas. | Rellena cada fila con la medida mínima de la anchura de la cadera en centímetros. Ejemplo: 119 cm. |
+| **Neck_circumference_from** | Circunferencia del cuello. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la anchura del cuello. Ejemplo: 35 cm. |
+| **Neck_circumference_to** | Circunferencia del cuello. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la anchura del cuello. Ejemplo: 38 cm. |
+
+### Tabla de top clothes
+
+La plantilla de la tabla de medidas para ropa de la parte inferior tiene las siguientes columnas:  
+
+| Columna | Descripción | Contenido |
+| :---: | ----- | ----- |
+| **Size** | Talla de la ropa. | Rellena cada fila con las tallas de la ropa. Ejemplo: L. |
+| **Filtrable_size** | Talla filtrable disponible para la categoría. | Rellena cada fila con la talla disponible para filtrar. Ejemplo: 44\.  |
+| **Waist_circumference_from** | Circunferencia de la cintura. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la anchura de la cintura en centímetros. Ejemplo: 70 cm. |
+| **Waist_circumference_to** | Circunferencia de la cintura. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la anchura de la cintura en centímetros. Ejemplo: 77 cm. |
+| **Hip_circumference_from** | Circunferencia de la cadera. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la anchura de la cadera para la talla en centímetros. Ejemplo: 109 cm. |
+| **Hip_circumference_to** | Circunferencia de la cadera. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la anchura de la cadera para la talla en centímetros. Ejemplo: 115 cm. |
+| **Length_from_inseam_to_ankle_from** | Largo de la pierna medido desde la entrepierna al tobillo. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima del tamaño de la pierna en centímetros. Ejemplo: 75 cm. |
+| **Length_from_inseam_to_ankle_to** | Largo de la pierna medido desde la entrepierna al tobillo. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima del tamaño de la pierna en centímetros. Ejemplo: 85 cm. |
+| **Length_from_waist_to_ankle_from** | Largo de la pierna medido desde la cintura al tobillo. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima del tamaño de la pierna en centímetros. Ejemplo: 80 cm. |
+| **Length_from_waist_to_ankle_to**  | Largo de la pierna medido desde la cintura al tobillo. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima del tamaño de la pierna en centímetros. Ejemplo: 88 cm. |
+| **Thigh_circumference_from** | Circunferencia del muslo. Inicio del intervalo de medidas. | Rellena cada fila de la columna con la medida mínima del tamaño del muslo en centímetros. Ejemplo: 50 cm. |
+| **Thigh_circumference_to** | Circunferencia del muslo. Fin del intervalo de medidas. | Rellena cada fila de la columna con la medida máxima del tamaño del muslo en centímetros. Ejemplo: 58 cm. |
+| **Person_height_from** | Altura de la persona. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la altura de una persona en centímetros. Ejemplo: 188 cm. |
+| **Person_height_to** | Altura de la persona. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la altura de una persona en centímetros. Ejemplo: 193 cm. |
+
+<div class="alert alert-info">
+Es importante reforzar la necesidad de usar espacio entre el número y la medida (cm), separar los números con puntos (.), rellenar todas las columnas y verificar si los campos <b>Género</b> y <b>Tamaño</b> fueron seleccionados correctamente.
+  </div>
+
+## Cargar la tabla de medidas
+
+Luego de completar la plantilla de mapeo, debes cargarla. Para hacerlo, accede al **Admin VTEX > Marketplace > Conexiones > Marketplace e integraciones** o ingresa **Marketplace e integraciones** en la barra de búsqueda en la parte superior del Admin y sigue los pasos a continuación:  
+
+1. Busca la integración de **Mercado Libre**.  
+2. Selecciona la opción `Realizar mapeo`. Se abrirá una nueva ventana con la página de mapeo.  
+3. En la sección **Tabla de medidas**, haz clic en el ícono `+`.  
+4. Selecciona la opción Tabla personalizada.  
+5. Haz clic en `Selecciona un archivo`.  
+6. Selecciona el archivo de la plantilla.  
+7. Haz clic en `Agregar`.
+
+Al terminar, habrás creado tu tabla de medidas personalizada con éxito.  
+
+<div class="alert alert-info">
+Si ocurre un error en la tabla, se indicará el problema en la pantalla de carga. Debes resolver el error y cargar la plantilla nuevamente.
+</div>
diff --git a/docs/tutorials/es/mercado-livre-automobilist-compatibility.md b/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
index 3d6be0520..e5d0ed24c 100644
--- a/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
+++ b/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
@@ -29,7 +29,7 @@ En los anuncios enviados a Mercado Libre, se pueden identificar los que tengan e
 Los anuncios que tengan error no se envían a Mercado Libre hasta que se corrijan.
 </div>  
 
-![Mercado Libre: compatibilidad de autopartes](https://images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/df37ddb666928a86c4199ce98bfe7af6/comp_automobilistica.png) 
+![Mercado Libre: compatibilidad de autopartes](//images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/df37ddb666928a86c4199ce98bfe7af6/comp_automobilistica.png) 
 
 Para acceder al módulo Gestión de anuncios, en el Admin VTEX, ve a __Marketplace > Integraciones > Gestión de anuncios.__ En esta página puedes filtrar por canal, marca, categoría o status.  
 
@@ -39,7 +39,7 @@ Para corregir los errores de `Compatibilidad con MELI` sigue los pasos a continu
 2.	Haz clic en __Error de asociación de autopartes.__  
 3.	Haz clic en __Gestionar compatibilidad.__  
 4.	Rellena los campos __Marca, Modelo, Año, Versión__ según la compatibilidad del accesorio.  
-![Mercado Libre: compatibilidad de autopartes 2](https://images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/73b751561077eb819e5044443f184f2d/compatibilidad_automobilistica_2.png)  
+![Mercado Libre: compatibilidad de autopartes 2](//images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/73b751561077eb819e5044443f184f2d/compatibilidad_automobilistica_2.png)  
 5.	Agrega todos los modelos de vehículos compatibles haciendo clic en +.  
 6.	Haz clic en el botón __Agregar excepción__ y espera el mensaje «Excepción enviada con éxito».  
 7.	Haz clic en Confirmar y aparecerá el mensaje "Compatibilidad asociada con éxito" en la pantalla.  
diff --git a/docs/tutorials/es/mercado-livre-faq.md b/docs/tutorials/es/mercado-livre-faq.md
index 97027eb7d..f8f309611 100644
--- a/docs/tutorials/es/mercado-livre-faq.md
+++ b/docs/tutorials/es/mercado-livre-faq.md
@@ -96,7 +96,7 @@ Al registrar un producto, es necesario establecer una cantidad mínima de stock
 
 La categoría en cuestión exige el mapeo de marca y modelo. Esta información debe estar presente en la plantilla de mapeo. Formato de ejemplo:
 
-![mercadolivre faq erro](https://images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
+![mercadolivre faq erro](//images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
 
 ## ¿Por qué mi anuncio está desactivado en Mercado Libre?
 
@@ -136,12 +136,12 @@ Sin embargo, estos atributos son bastante claros (Color principal, Color secunda
 
 Si alguno de estos atributos se completa de forma incorrecta (por ejemplo, si se asignó un código relativo a Talla de cinturón para un zapato), Integraciones va a mostrar un error con el siguiente formato:
 
-![mercadolivre faq erro2](https://images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
+![mercadolivre faq erro2](//images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
 
 En este caso, tenemos dos ejemplos de errores en el mismo mensaje.
 El primero de estos indica que el atributo cuyo código comienza con el número `113000` es necesario para la categoría escogida y no fue ingresado en la plantilla de mapeo. Vea la plantilla a continuación:
 
-![mercadolivre faq erro3](https://images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
+![mercadolivre faq erro3](//images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
 
 El segundo error muestra que el atributo cuyo código empieza con el número `63000`, ingresado en la última columna de la plantilla anterior, es inválido para la categoría escogida.
 
@@ -186,7 +186,7 @@ Existe el elemento principal del anuncio y este contiene las variaciones (que so
 
 Cada categoría tiene su propia especificación de cuántas imágenes pueden ser añadidas, en la categoría MLA3697 solo se permite 12 imágenes para este elemento principal. Vea en el enlace las condiciones de esta [categoría](https://api.mercadolibre.com/categories/MLA3697)
 
-![mercadolivre faq erro4](https://images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
+![mercadolivre faq erro4](//images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
 
 `SKU no integrado, pues el mismo no posee descripción`
 
@@ -220,7 +220,7 @@ Dicho esto, el primer paso es acceder al registro de esta integración:
 1. Acceda al módulo __Marketplace__
 2. Haga clic en __Integraciones__ 
 3. Busque el __panel__ de Mercado Libre
-4. Haga clic en el __engranaje__ <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
+4. Haga clic en el __engranaje__ <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
 5. Haga clic en __Editar configuración__
 
 A partir de ahí, tenemos que rehacer el proceso de integración.
diff --git a/docs/tutorials/es/merchandising-rule-conditions.md b/docs/tutorials/es/merchandising-rule-conditions.md
new file mode 100644
index 000000000..12a4d6adf
--- /dev/null
+++ b/docs/tutorials/es/merchandising-rule-conditions.md
@@ -0,0 +1,66 @@
+---
+title: 'Condiciones de las reglas de merchandising'
+id: 4K9WCBiQ4ndU396ZygDpc2
+status: PUBLISHED
+createdAt: 2024-06-27T17:17:15.295Z
+updatedAt: 2024-06-27T17:19:47.360Z
+publishedAt: 2024-06-27T17:19:47.360Z
+firstPublishedAt: 2024-06-27T17:18:32.359Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: condiciones-de-las-reglas-de-merchandising
+locale: es
+legacySlug: condiciones-de-las-reglas-de-merchandising
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Las condiciones de las reglas de merchandising del [Editor manual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) y el [Editor visual (Beta)](https://help.vtex.com/es/tutorial/crear-regla-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3) siguen el formato `{criterio} {operador} {valor}`. Por ejemplo, una condición puede tener la estructura `marca es athletic`, donde `marca` corresponde al criterio, `es` corresponde al operador y `athletic `corresponde al valor.
+
+Conoce los criterios y los operadores posibles para cada forma de edición en las siguientes tablas:
+
+## Criterios
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"><thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nombre</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descripción</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operadores</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tipo de edición</th> </tr></thead><tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span></td> <td rowspan="2" class="t-body pa5">Palabra que el cliente busca y estará relacionada con la regla. Campo para rellenar libremente.</td> <td class="t-body pa5">es</td> <td rowspan="2" class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br>Reglas de personalización</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">contiene</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Busca el ID exacto de algún ítem del catálogo que estará relacionado con la regla. Los ID posibles son: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong> y <strong>EAN</strong>. Campo para rellenar libremente.</td> <td class="t-body pa5">es</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de personalización</td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">categoría</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una categoría registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">departamento</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa un departamento registrado en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">marca</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una marca registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">nombresclusterproductos</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una colección registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoción</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que valida si existe al menos una promoción vinculada al ítem (sí).</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solamente </td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">nombreseller</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa el nombre de un seller.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategoría</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una subcategoría registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{especificación}}</span></td> <td rowspan="2" class="t-body pa5">Cualquier especificación activa del Catálogo aparece como un criterio personalizado, con los mismos valores posibles. El nombre del criterio es igual al nombre de la especificación registrada. Por ejemplo, si hay una especificación activa llamada <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>, el criterio mostrado será <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr></tbody></table>
+
+<div class="alert alert-warning">
+  <p>Los criterios <code>departamento</code>, <code>categoría</code> y <code>subcategoría</code> solo aparecen como opciones para componer las Reglas de merchandising si los tres niveles de categorías ya están configurados en el <strong>Catálogo</strong>.</p>
+</div>
+
+## Operadores
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+<thead>
+  <tr class="bb b--muted-3">
+    <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nombre</th>
+    <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descripción</th>
+    <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Criterios</th>
+    <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Ejemplo</th>
+  </tr>
+</thead>
+<tbody>
+  <tr class="bb b--muted-3">
+    <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">es</span></td>
+    <td class="t-body pa5">Si utilizas la función <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span> como criterio para crear una regla en el Editor manual, se crea una búsqueda con palabras exactas.</td>
+    <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span></td>
+    <td class="t-body pa5">Si registras <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> y un cliente busca <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span>, se activará la regla de merchandising. Sin embargo, si el cliente busca <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoción black friday</span>, la regla no se activará.</td>
+  </tr>
+  <tr class="bb b--muted-3">
+    <td class="t-body pa5">En otros escenarios de edición, permite aplicar también otras condiciones diferentes de la actual.</td>
+    <td class="t-body pa5">Todos (excepto <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span>)</td>
+    <td class="t-body pa5">Si la condición es marca es <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>, la regla de merchandising también se activará aunque el cliente incluya <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">hotsport</span>, sportist y <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span> en la búsqueda.</td>
+  </tr>
+  <tr class="bb b--muted-3">
+    <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contiene</span></td>
+    <td class="t-body pa5">Si utilizas la función <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span> como criterio para crear una regla en el Editor manual, se configura una búsqueda que no se limita únicamente a las palabras exactas.</td>
+    <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span></td>
+    <td class="t-body pa5">Si registras <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> y un cliente busca black friday o frases similares como <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoción black friday</span> se activará la regla de merchandising.</td>
+  </tr>
+  <tr class="bb b--muted-3">
+    <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">solo</span></td>
+    <td class="t-body pa5">Limita la búsqueda solo al filtro registrado.</td>
+    <td class="t-body pa5">Todos (excepto <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span>)</td>
+    <td class="t-body pa5">Si la condición es marca es <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span> y el cliente selecciona <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">hotsport</span> en primer lugar en la búsqueda, la regla de merchandising no se activará incluso si después selecciona <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>.  Solo funcionará si el primer filtro seleccionado para la marca es <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>.</td>
+  </tr>
+</tbody>
+</table>
diff --git a/docs/tutorials/es/merchandising-rules-list.md b/docs/tutorials/es/merchandising-rules-list.md
new file mode 100644
index 000000000..0f0cc6e3e
--- /dev/null
+++ b/docs/tutorials/es/merchandising-rules-list.md
@@ -0,0 +1,70 @@
+---
+title: 'Lista de Reglas de merchandising'
+id: 3CZOjyie1LZVOhzeviVCgu
+status: PUBLISHED
+createdAt: 2024-07-03T17:08:55.426Z
+updatedAt: 2024-07-03T17:10:24.720Z
+publishedAt: 2024-07-03T17:10:24.720Z
+firstPublishedAt: 2024-07-03T17:10:24.720Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: lista-de-reglas-de-merchandising
+locale: es
+legacySlug: lista-de-reglas-de-merchandising
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+En el Admin VTEX, la página **Storefront** > **Intelligent Search** > **Reglas de merchandising** permite realizar las siguientes acciones:
+
+* [Crear](#crear-reglas-de-merchandising)
+* [Buscar](#buscar-reglas-de-merchandising)
+* [Editar](#editar-reglas-de-merchandising)
+* [Eliminar](#eliminar-reglas-de-merchandising)
+
+![reglas-merch-es](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/4624acb4cd7dbe4e2a4d858e570f1f92/reglas-merch-es.PNG)
+
+La página contiene la siguiente información: 
+
+| Campos de la columna | Descripción |
+| - | - |
+| __Nombre__ | Nombre que identifica la regla de merchandising definida en la etapa [Crear reglas de merchandising](#crear-reglas-de-merchandising). |
+| __Fecha de inicio__ | Fecha en la que la regla de merchandising comenzará a estar disponible. |
+| __Fecha de fin__ | Fecha en la que la regla de merchandising dejará de estar disponible. |
+| __Tipo__ | Indica el [tipo de edición](#tipos-de-edicion) utilizado en la regla de merchandising. |
+| __Activa__ | Opción para activar o desactivar una regla de merchandising. |
+| __Acciones__ <i class="fas fa-ellipsis-v"></i> | Menú con acciones para `Editar` o `Eliminar` una regla de merchandising. |
+
+### Crear reglas de merchandising
+
+Para configurar una regla de merchandising, haga clic en `+ Agregar`. Más información sobre toda la información necesaria para crear una regla de merchandising en las siguientes secciones.
+
+### Tipos de edición
+
+Existen dos tipos de editor para Reglas de merchandising: el [Editor manual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) y el [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr).
+
+A continuación, te mostramos cuáles son las funcionalidades en cada una de estas opciones:
+
+| Funcionalidad | Descripción | Editor manual | Editor visual |
+|---|---|---|---|---|
+| Reglas de activación  | Define las condiciones para la activación de la regla de merchandising. | Sí | Sí |
+| Reglas de personalización | Controla los resultados de la búsqueda a partir de condiciones específicas. | Sí | No |
+| Vista previa | Ofrece una vista previa de cómo los clientes verán los resultados de la búsqueda mientras navegan por la tienda. | No | Sí |
+| Reordenar los resultados de búsqueda | Modifica el orden de los artículos incluidos en la lista de los resultados de la búsqueda. | No | Sí |
+| Fijar productos en las primeras posiciones | Determina que un determinado elemento de un resultado de búsqueda se muestre siempre en la primera posición entre los resultados de búsqueda. | No | Sí |
+
+## Buscar reglas de merchandising
+
+Para buscar una regla de merchandising, escribe el nombre de la regla de comercialización en la barra de búsqueda.
+
+## Editar reglas de merchandising
+
+Puedes editar la información de una regla de merchandising siguiendo los pasos a continuación.
+
+1. Haz clic en el menú <i class="fas fa-ellipsis-v"></i> de la línea de la regla de merchandising y, a continuación, en el botón <i class="fas fa-pencil-alt"></i> `Editar`.
+2. Edita la información deseada en la regla de merchandising.
+3. Haz clic en `Guardar`.
+
+## Eliminar reglas de merchandising
+
+Puedes eliminar una regla haciendo clic en el menú <i class="fas fa-ellipsis-v"></i> de la línea de la regla de merchandising y, a continuación, en el botón <i class="fas fa-trash"></i> `Eliminar`.
diff --git a/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md b/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md
new file mode 100644
index 000000000..6ee406e97
--- /dev/null
+++ b/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md
@@ -0,0 +1,43 @@
+---
+title: 'No puedo ver las métricas en el dashboard de pedidos'
+id: 1B5OAicmK3AvnwPzs4iq7Z
+status: PUBLISHED
+createdAt: 2024-06-10T11:28:08.507Z
+updatedAt: 2024-06-10T17:15:44.616Z
+publishedAt: 2024-06-10T17:15:44.616Z
+firstPublishedAt: 2024-06-10T17:15:44.616Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: no-puedo-ver-las-metricas-en-el-dashboard-de-pedidos
+locale: es
+legacySlug: no-puedo-ver-las-metricas-en-el-dashboard-de-pedidos
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palabras clave:** *dashboard, panel administrativo, vista general, actualización, rol.*
+
+Al acceder al Admin, es posible que tu tienda no cargue las métricas presentes en Dashboards > **Vista general**, mostrando íconos de advertencia y un mensaje de error. Esto puede deberse a:
+
+- **Demora en la actualización de datos:** puede haber un retraso en la actualización de la información mostrada en el dashboard.
+- **Periodo de comparación inadecuado:** es posible que el periodo seleccionado en la esquina superior derecha del dashboard no contenga suficientes datos de pedidos para realizar la comparación.
+- **Permisos de acceso limitados:** es posible que no dispongas del rol necesario para ver determinada información en el dashboard.
+
+![Visão geral - ES](//images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/ab4d1113340d7b941580edc9dc7dacc5/Vis_o_geral_-_ES.png)
+
+## Solución
+Para resolver inconsistencias en el dashboard inicial del panel administrativo, prueba a realizar las acciones que se describen a continuación:
+
+### Ajustar periodo de comparación
+Ajustar correctamente el periodo de comparación puede resolver el problema, ya que se mostrarían métricas relevantes. Para comprobar si el periodo seleccionado en Dashboard > **Vista general** contiene datos de pedido válidos, sigue los pasos a continuación:
+
+1. En el VTEX Admin, accede a **Dashboard > Vista general**.
+2. En la esquina superior derecha selecciona el periodo de comparación.
+
+![Dashboard - ES](//images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/352e042a451953fe735d06b1160ae2d9/Dashboard_-_ES.png)
+
+### Esperar a que la información se actualice
+El tiempo de espera para la actualización de la información del dashboard puede variar entre 10 y 80 minutos. Este periodo es necesario para que los datos se procesen y se muestren correctamente. Para más información sobre el tiempo de espera, accede a [Comparar periodos](https://help.vtex.com/es/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ?&utm_source=autocomplete#comparacao-de-periodos).
+
+### Comprobar permisos de acceso
+Para ver la información en el dashboard, asegúrate de tener un rol que incluya el [recurso](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) **Insights metrics**. Para más información sobre roles y cómo configurarlos, consulta el artículo [Roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/tutorials/es/minimum-stock-control-for-integrations.md b/docs/tutorials/es/minimum-stock-control-for-integrations.md
index f1bbfc5ea..1864502a1 100644
--- a/docs/tutorials/es/minimum-stock-control-for-integrations.md
+++ b/docs/tutorials/es/minimum-stock-control-for-integrations.md
@@ -40,7 +40,7 @@ Para configurar el stock mínimo en su integración, realice los siguientes paso
 2. En el menú Marketplace > Conexiones, haga clic en **Integraciones**.
 3. Seleccione la opción **Configuración**.
 4. Elija la integración que desea configurar.
-5. Cuando elija la integración, haga clic en el engranaje<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+5. Cuando elija la integración, haga clic en el engranaje<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 6. Seleccione la opción **Editar configuración**.
 7. En el campo **Stock mínimo**, ingrese en valor deseado.
 8. Finalmente, haga clic en el botón **Guardar configuración**.
diff --git a/docs/tutorials/es/mode-off-faq.md b/docs/tutorials/es/mode-off-faq.md
index b6f3716a0..7b153d337 100644
--- a/docs/tutorials/es/mode-off-faq.md
+++ b/docs/tutorials/es/mode-off-faq.md
@@ -1,10 +1,10 @@
 ---
 title: 'Mode-Off: FAQ'
 id: 6hbd7PuvoxuRbPCvTqjxeB
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-01-21T17:29:10.793Z
-updatedAt: 2021-04-06T20:20:55.582Z
-publishedAt: 2021-04-06T20:20:55.581Z
+updatedAt: 2024-04-11T19:26:47.407Z
+publishedAt: 2024-04-11T19:22:34.569Z
 firstPublishedAt: 2021-01-21T17:54:12.941Z
 contentType: tutorial
 productTeam: Financial
@@ -55,9 +55,10 @@ Las transacciones se liberarán normalmente cuando el partner deje de presentar
 
 ## ¿Por cuánto tiempo VTEX intenta procesar de nuevo las transacciones retenidas?
 
-El tiempo de reintento lo define cada partner en el momento de la integración con Payment Provider Protocol.
+El partner puede definir el tiempo entre los reintentos de procesamiento de transacciones (_retries_) al enviar la información de pago. Al configurar el tiempo de cancelación de pago (campo delayToCancel) por un período inferior a 1 día, los reintentos se realizarán cada 1 hora. Si el tiempo para cancelar el pago se establece como igual o mayor a 1 día, los reintentos se realizarán cada 4 horas. Para obtener más información, visite [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol?endpoint=post-/payments).
 
-Si este período no se ha definido previamente, el tiempo estándar es de __cuatro horas__.
+<div class="alerta alerta-info">
+ Si el pago se realiza mediante <a href="https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf">PIX (Método de pago instantáneo brasileño)</a> o el tiempo de cancelación de pago se configura entre 5 minutos y 1 hora, los reintentos se realizarán cada 5 minutos.</div>
 
 ## ¿Cómo identificar mode-off y qué hacer cuando esté activo?
 
diff --git a/docs/tutorials/es/moving-order-to-start-handling-shipping.md b/docs/tutorials/es/moving-order-to-start-handling-shipping.md
index 3836686a9..cc16ca4a4 100644
--- a/docs/tutorials/es/moving-order-to-start-handling-shipping.md
+++ b/docs/tutorials/es/moving-order-to-start-handling-shipping.md
@@ -3,8 +3,8 @@ title: 'Enviar pedido al status a Preparar la Entrega'
 id: tutorials_198
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:17.090Z
-updatedAt: 2023-03-31T14:47:04.890Z
-publishedAt: 2023-03-31T14:47:04.890Z
+updatedAt: 2023-06-15T13:32:59.728Z
+publishedAt: 2023-06-15T13:32:59.728Z
 firstPublishedAt: 2017-04-27T23:02:47.756Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,10 +21,12 @@ La baja en la reserva no ocurre automáticamente, esto debe ser controlado por s
 
 A continuación se indican las posibles maneras de actualizar este status.
 
-## Por integración
+## Por integración y API
 
 Las integraciones automatizan este proceso. Ocurren cuando otros sistemas consultan los pedidos de VTEX para seguir con el flujo de envío. Esta integración se puede hacer a través de API REST, según nuestro [guía de integración de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing).
 
+Después de hacerlo, puedes usar la API [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
+
 ## Por el Admin VTEX
 
 Si la tienda no tiene ERP o algún sistema que integre los pedidos, usted puede realizar la continuación del flujo manualmente. El paso a paso para esta tarea se describe a continuación:
diff --git a/docs/tutorials/es/multilevel-omnichannel-inventory.md b/docs/tutorials/es/multilevel-omnichannel-inventory.md
index 85daf1c00..6887cbfe0 100644
--- a/docs/tutorials/es/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/es/multilevel-omnichannel-inventory.md
@@ -3,34 +3,34 @@ title: 'Multilevel Omnichannel Inventory'
 id: 7M1xyCZWUyCB7PcjNtOyw4
 status: PUBLISHED
 createdAt: 2020-11-30T19:44:58.255Z
-updatedAt: 2023-04-19T00:59:40.265Z
-publishedAt: 2023-04-19T00:59:40.265Z
+updatedAt: 2024-07-24T14:21:41.092Z
+publishedAt: 2024-07-24T14:21:41.092Z
 firstPublishedAt: 2020-12-08T19:12:43.325Z
 contentType: tutorial
-productTeam: Shopping
-author: 127RQ7SUoFfyTh5gbXUpdM
+productTeam: Channels
+author: 0QBQws7rk0t5Mnu8fgfUv
 slug: multilevel-omnichannel-inventory
 locale: es
 legacySlug: marketplace-recursivo-v2
-subcategory: 6riYYNZCpO8wyksi8Ksgyq
+subcategory: 5RAUzLD6X9Wa1maenj1eGA
 ---
 
-_Multilevel omnichannel inventory _(antes llamado _Marketplace_ recursivo) es la configuración de VTEX que permite que una cuenta principal ofrezca el _stock_ de [sellers white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) y de [cuentas franquicia](https://help.vtex.com/es/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) para la venta en los _marketplaces_. Este artículo incluye la siguiente información sobre la funcionalidad:
+__Multilevel omnichannel inventory__ es la configuración de VTEX que permite que una cuenta principal ofrezca el _stock_ de [sellers white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) y de [cuentas franquicia](https://help.vtex.com/es/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) para la venta en los _marketplaces_. Este artículo incluye la siguiente información sobre la funcionalidad:  
 
-- [Arquitectura de cuentas](#arquitectura-de-cuentas)
-- [Beneficios](#beneficios)
-- [Restricciones](#restricciones)
-- [Cómo configurar](#como-configurar)
+- [Arquitectura de cuentas](#arquitectura-de-cuentas)  
+- [Beneficios](#beneficios)  
+- [Restricciones](#restricciones)  
+- [Cómo configurar](#como-configurar)  
 
 <div class="alert alert-info">
-Para más información sobre la arquitectura de los pedidos de Multilevel omnichannel inventory y cómo realizar la configuración a través de la API REST, consulta nuestro artículo de <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory">Developer Portal</a>.
+Para obtener más información sobre la arquitectura de los pedidos de tipo Multilevel Omnichannel Inventory y aprender a realizar la configuración a través de la API REST, consulta nuestro artículo en el <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory">Developer Portal</a>.
 </div>
 
 ## Arquitectura de cuentas
 
-El [marketplace](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) es el entorno donde se vende el producto, también llamado vitrina, y el [seller](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#selling-on-marketplaces) es el propietario del _stock_ y el responsable del envío del pedido.
+El [marketplace](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) es el entorno donde se vende el producto, también llamado vitrina, y el [seller](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#selling-on-marketplaces) es el propietario del envío del producto.
 
-Cuando una tienda vende sus productos en un _marketplace_, tenemos una relación de un solo nivel entre el _seller_ y el _marketplace_. Sin embargo, la arquitectura de VTEX permite que las tiendas actúen tanto como _marketplaces_ como _sellers_, ampliando el número de combinaciones posibles.
+Cuando una tienda vende sus productos en un _marketplace_, tenemos una relación de dos niveles. Sin embargo, la arquitectura de VTEX permite que las tiendas actúen tanto como _marketplaces_ como _sellers_, ampliando el número de combinaciones posibles.
 
 Es posible que un _seller_ de una cuenta principal actúe como _marketplace_ para [sellers white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa). Este es el caso de las redes de tiendas configuradas como [cuentas franquicia](https://help.vtex.com/es/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) y de las tiendas físicas, que son por definición _sellers_ en otra tienda VTEX.
 
@@ -38,11 +38,9 @@ También es posible que este _seller_ principal venda sus productos en un _marke
 
 Cuando esto ocurre, tenemos una arquitectura de tres niveles entre el _marketplace_, el _seller_ principal y sus _sellers white label_, como se ilustra en la imagen de abajo.
 
-![Arquitetura Multilevel omichannel inventory](https://images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/abf2341444442ee6ef770afdfd044a06/Screen_Shot_2022-09-30_at_18.57.26.png)
+![Arquitetura Multilevel omichannel inventory](//images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/abf2341444442ee6ef770afdfd044a06/Screen_Shot_2022-09-30_at_18.57.26.png)
 
-Por defecto, los productos de las tiendas físicas, o _sellers white label_ (nivel 3 en la imagen), no están disponibles para ser vendidos por el _marketplace_ de nivel 1. Pero puedes hacer que estén disponibles con la funcionalidad _Multilevel omnichannel inventory._
-
-> __Multilevel Omnichannel Inventory__ es la configuración en VTEX que permite que el _stock_ de los _sellers white label_ y de las cuentas franquicia esté disponible para su venta en los _marketplaces_ en los que está conectada la cuenta principal del _seller_ directo.
+De forma predeterminada, los productos de las tiendas físicas, o _sellers white label_ (nivel 3 en la imagen), no están disponibles para ser vendidos por el _marketplace_ de nivel 1, pero con la funcionalidad _Multilevel Omnichannel Inventory_ puedes disponibilizarlos.
 
 De este modo, es posible que un _marketplace_ venda los productos de sus _sellers_ directos, así como de las tiendas físicas y de los _sellers white label_ vinculados a estos _sellers_.
 
@@ -54,14 +52,14 @@ Actualmente, solo se permite un nivel de recursión. En otras palabras, el marke
 
 ## Beneficios
 
-Esta funcionalidad aporta ventajas competitivas al _marketplace_, como:
+Esta funcionalidad aporta ventajas competitivas al _marketplace_, como:  
 
-- Mayor diversidad de productos ofrecidos al cliente final.
-- Menos problemas de _stock_ insuficiente al incluir más tiendas que ofrecen productos.
-- La opción de ofrecer todo el _stock_ de una operación omnichannel a otros _marketplaces_, aumentando la oferta de puntos de recogida, por ejemplo.
-- La posibilidad de trabajar con nuevos modelos de negocio y conectar diferentes marcas con relaciones de colaboración entre el _marketplace_ y el _seller_.
-- Acceso a nuevos mercados y nichos de consumidores.
-- Orquestar los pedidos de múltiples canales con visibilidad sobre toda la cadena.
+- Mayor diversidad de productos ofrecidos al cliente final.  
+- Menos problemas de _stock_ insuficiente al incluir más tiendas que ofrecen productos.  
+- La opción de ofrecer todo el _stock_ de una operación omnichannel a otros _marketplaces_, aumentando la oferta de puntos de recogida, por ejemplo.  
+- La posibilidad de trabajar con nuevos modelos de negocio y conectar diferentes marcas con relaciones de colaboración entre el _marketplace_ y el _seller_.  
+- Acceso a nuevos mercados y nichos de consumidores.  
+- Orquestar los pedidos de múltiples canales con visibilidad sobre toda la cadena.  
 
 Para más información sobre la arquitectura de pedidos aplicada en Multilevel omnichannel inventory, consulta nuestro [artículo para desarrolladores](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
 
@@ -69,17 +67,13 @@ Para más información sobre la arquitectura de pedidos aplicada en Multilevel o
 
 Algunas de las funcionalidades que forman parte del modelo tradicional de _marketplace_ no están disponibles para un escenario de _Multilevel omnichannel inventory_. Es importante conocer estas restricciones antes de habilitar la configuración.
 
-### Marketplaces externos
-
-Esta funcionalidad puede configurarse en [marketplaces VTEX](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-un-marketplace-vtex), [conectores nativos](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex) y [partners certificados](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrado-con-un-conector-certificado-partner). Además,[Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) ya permite la integración del _stock_ de la tienda física.
-
-Aunque los _marketplaces_ soporten la funcionalidad, no está disponible automáticamente para ellos. Es necesario configurar y adaptar la integración para cada uno. Esto se aplica a los _marketplaces_ integrados por primera vez y a los que ya utilizaban la API de _fulfillment_, que está restringida a dos niveles. Obtén más información en [Cómo configurar](#como-configurar) y en nuestro artículo en el [Developer portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
+### Disponibilidad
 
-Multilevel omnichannel inventory puede causar errores de integración cuando se aplica a _marketplaces_ externos a VTEX. En estos escenarios, el ID del pedido cambiará, por ejemplo. Te aconsejamos que consultes con tu equipo de desarrollo para asegurarte de que la transición se realice problemas. Obtén más información en nuestro [artículo en el Developer portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
+La funcionalidad Multilevel Omnichannel Inventory está disponible únicamente para [marketplaces VTEX](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-un-marketplace-vtex). Para utilizar la funcionalidad, el marketplace (nivel 1) debe realizar la configuración para cada seller directo (nivel 2) deseado. Puedes hacerlo al registrar nuevos sellers o al editar la configuración de sellers existentes en tu tienda. Consulta más información accediendo a [Configurar](#configuracion) y al [Developer portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
 
 ### Distribución de cuentas por cobrar
 
-No es posible distribuir las cuentas por cobrar en toda la cadena (_marketplace_, _seller_ directo y _sellers white label_). Los pagos de los pedidos de Multilevel omnichannel inventory solo pueden realizarse en el _marketplace_. La conciliación y la transferencia de valores a los _sellers_ de nivel 3 deben realizarse fuera de VTEX, ya que no hay soporte nativo para esta etapa.
+No es posible distribuir las cuentas por cobrar en toda la cadena (_marketplace, seller directo y sellers white label_). Los pagos de los pedidos de _Multilevel Omnichannel Inventory_ solo pueden realizarse en el _marketplace._ La conciliación y la transferencia de valores a los _sellers_ de nivel 3 deben realizarse fuera de VTEX, ya que no hay soporte nativo para esta etapa.
 
 Puedes utilizar la solución de [split de pagos](https://help.vtex.com/es/tracks/split-de-pagamentos--1ouDg8q56Kuz1AgtJUY9nv/4EOhp8cdVXaHl68KykPG6) solo para dividir las cuentas por cobrar entre los niveles _marketplace_ y _seller directo_ (nivel 2). En este caso, se recomienda utilizar el [split de cobros](https://help.vtex.com/es/tutorial/split-payment#split-de-recebiveis).
 
@@ -91,7 +85,11 @@ Es importante destacar que cuando el _seller directo_ no es responsable de las c
 
 ### Medios de pago
 
-Una vez realizada la configuración, solo los medios de pago del _marketplace_ aparecerán como opción en el _checkout_. Los medios de pago de los _sellers_ directos (nivel 2) y de los _sellers white label_ (nivel 3) no se importan a la arquitectura de las cuentas. Por lo tanto, el _checkout_ solo muestra los medios de pago del _marketplace_, incluso si el afiliado del _seller_ directo está configurado para utilizar sus medios de pago. El[ afiliado](https://help.vtex.com/es/tutorial/como-configurar-afiliado--tutorials_187) de la cuenta franquicia debe tener siempre desmarcada la opción de usar los medios de pago.
+Una vez realizada la configuración, solo los medios de pago del _marketplace_ aparecerán como opción en el _checkout_. Los medios de pago de los _sellers_ directos (nivel 2) y de los _sellers white label_ (nivel 3) no se importan a la arquitectura de las cuentas. Por lo tanto, el _checkout_ solo muestra los medios de pago del _marketplace_, incluso si el afiliado del _seller_ directo está configurado para utilizar sus medios de pago. 
+
+<div class="alert alert-warning">
+  El <a href="https://help.vtex.com/es/tutorial/como-configurar-afiliado--tutorials_187">afiliado</a> de la cuenta franquicia debe tener siempre desmarcada la opción de usar los medios de pago.
+</div>
 
 ### Cambio de seller
 
@@ -99,22 +97,18 @@ Si un _seller white label_ (nivel 3) recibe un pedido y lo rechaza, este pedido
 
 ### Modificación de los pedidos finalizados por la tienda
 
-Una tienda VTEX no puede modificar los pedidos finalizados en un marketplace VTEX en un escenario de Multilevel omnichannel inventory. Por lo tanto, debe cancelar el pedido y crear uno nuevo.
-
-Sin embargo, es posible cambiar pedidos de tiendas VTEX en marketplaces externos. Sepa más en [Change chain orders in external marketplaces](https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces).
+La tienda no puede modificar los pedidos finalizados en un escenario de Multilevel Omnichannel Inventory. Por lo tanto, debe cancelar el pedido y crear uno nuevo. Consulta más información en [Change chain orders in external marketplaces](https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces).
 
 ### Modificación de los pedidos finalizados por el cliente
 
-El cliente no puede modificar los pedidos en la sección _Mis pedidos_ del _storefront_ del _marketplace_. Cualquier cambio en los pedidos debe realizarse a través del servicio de soporte al cliente o a través de API.
+El cliente no puede modificar los pedidos en la sección _Mis pedidos_ del _storefront_ del _marketplace_. Cualquier cambio en los pedidos debe realizarse a través del servicio de soporte al cliente o vía API.
 
 ### Manual price
 
-La funcionalidad _Manual price_ no se aplica al Multilevel omnichannel inventory. Por lo tanto, no es posible modificar manualmente los precios en el carrito. Es necesario actualizar el precio a través de:
-
-- [Integración con el ERP](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide)
-
-- [Pricing API REST](https://developers.vtex.com/vtex-rest-api/reference/createupdatepriceorfixedprice)
+La funcionalidad _Manual price_ no se aplica al _Multilevel omnichannel inventory._ Por lo tanto, no es posible modificar manualmente los precios en el carrito. Es necesario actualizar el precio a través de:
 
+- [Integración con el ERP](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide)  
+- [Pricing API REST](https://developers.vtex.com/vtex-rest-api/reference/createupdatepriceorfixedprice)  
 - [Página de precios en el Admin VTEX](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)
 
 ### Información de usuario
@@ -129,9 +123,13 @@ Un _marketplace_ no puede configurar la exhibición de los precios y la disponib
 
 La aplicación de [cupones](https://help.vtex.com/es/tutorial/cupons-beta--1aAEN3ADpz19ss5JCIEBdL),[tarjetas de regalo (vales)](https://help.vtex.com/es/tutorial/gift-card--tutorials_995) y beneficios vinculados a los [UTM](https://help.vtex.com/es/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) está restringido a _marketplaces_ nivel 1. No se aplicarán los configurados en _sellers_ directos (nivel 2) ni en cuentas franquicia o _sellers white label_ (nivel 3).
 
-## Cómo configurar
+### Tablas de precios
+
+No es posible crear tablas de precios mediante la funcionalidad [Tablas de precios](https://help.vtex.com/es/tutorial/criar-tabelas-de-precos--58YmY2Iwggyw4WeSCGg24S). Los precios deben registrarse vía integración con ERP o a través de plantillas.
 
-La configuración de la funcionalidad _Multilevel omnichannel inventory_ debe ser realizada por el _marketplace_ en tu Admin VTEX o a través de la [API Rest](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). Esta configuración puede realizarse tanto para los _sellers_ ya integrados como para los _sellers_ agregados por primera vez.
+## Configuracíon
+
+La configuración de la funcionalidad __Multilevel omnichannel inventory__ debe ser realizada por el _marketplace_ en tu Admin VTEX o a través de la [API Rest](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). Esta configuración puede realizarse tanto para los _sellers_ ya integrados como para los _sellers_ agregados por primera vez.
 
 <div class="alert alert-info">
 Ten en cuenta que la configuración debe realizarse para cada seller directo (nivel 2) al que quieras aplicar la funcionalidad, pero no para cada cuenta de seller white label o cuenta franquicia (nivel 3).
@@ -141,31 +139,31 @@ Ten en cuenta que la configuración debe realizarse para cada seller directo (ni
 
 Para configurarla en los _sellers_ que se han integrado previamente, el _marketplace_ debe seguir los pasos a continuación.
 
-   1. En la sección _Marketplace_ de tu Admin VTEX, ve a la pestaña **Sellers**.  
-   2. Haz clic en **Gestión de sellers**.  
-   3. En la fila correspondiente al _seller_ a cuyos _sellers white label_ deseas acceder, haz clic en `Editar`.
-   4. Rellena el campo **Fulfillment endpoint** siguiendo el ejemplo:
-`https://{{sellerAccount}}.vtexcommercestable.com.br/api/checkout?affiliateid={{affiliateId}}&sc={{tradePolicyId}}`
-   5. Sustituye los campos que están entre llaves por los valores que se describen a continuación, eliminando las llaves:
-
-    - **sellerAccount**: [el nombre de la cuenta](https://help.vtex.com/es/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) del seller en VTEX.
-    - **affiliateId**: el código de tres dígitos correspondiente al[ afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) creado por el _seller_. El _seller_ debe informar este valor al _marketplace_.
-    - **tradePolicyId**: ID de la[ política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) creada por el _seller_ en su propio entorno VTEX para vender en su _marketplace_. El _seller_ debe informar este valor al _marketplace_.
+1. En el Admin VTEX, ve a **Marketplace > Gestión.**  
+2. En la fila correspondiente al seller cuyos sellers white label deseas acceder, haz clic en <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Haz clic en Datos del seller.  
+4. Rellena el campo **Fulfillment endpoint** siguiendo el ejemplo:
+`https://{{sellerAccount}}.vtexcommercestable.com.br/api/checkout?affiliateid={{affiliateId}}&sc={{tradePolicyId}}`  
+5. Sustituye los campos que están entre llaves por los valores que se describen a continuación, eliminando las llaves:  
 
-   6. Haz clic en ` Guardar`.
+    - **sellerAccount**: [el nombre de la cuenta](https://help.vtex.com/es/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) del seller en VTEX.  
+    - **affiliateId**: el código de tres dígitos correspondiente al[ afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) creado por el _seller_. El _seller_ debe informar este valor al _marketplace_.  
+    - **tradePolicyId**: ID de la[ política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) creada por el _seller_ en su propio entorno VTEX para vender en su _marketplace_. El _seller_ debe informar este valor al _marketplace_.  
+6. Haz clic en ` Guardar`.  
 
 ### Sellers integrados por primera vez
 
 Si el _marketplace_ desea agregar un nuevo _seller_ con _Multilevel omnichannel inventory_ configurado desde cero, debe seguir las instrucciones en [Agregar seller](https://help.vtex.com/es/tutorial/adicionar-seller--tutorials_392) y rellenar el campo `Fulfillment endpoint` siguiendo los paso 4 y 5 del tutorial en _Sellers_ ya integrados.
 
 ### Ejemplo
-Supongamos que tu _marketplace_ ya está integrado con el _seller_ «_Tienda ABC»_ y quieres vender productos de _sellers white label_ integrados con ese _seller_.
 
-Actualmente, el valor del campo _Fulfillment endpoint_ del _seller_ tiene el siguiente formato y se puede identificar accediendo a **Marketplace > Sellers > Gestión de sellers**:
+Supongamos que tu _marketplace_ ya está integrado con el _seller_ _"Tienda ABC"_ y quieres vender productos de _sellers white label_ integrados con ese _seller_.
+
+Actualmente, el valor del campo _Fulfillment endpoint_ del _seller_ tiene el siguiente formato y se puede identificar accediendo a **Marketplace > Sellers > Gestión de sellers**:  
 
 `https://storeabc.vtexcommercestable.com.br/api/fulfillment?affiliateId=mkp&sc=2`
 
-Para habilitar la funcionalidad Multilevel omnichannel inventory, el nuevo valor del campo debe contener el _endpoint_ de **_checkout_, **en lugar del _endpoint_ de _fulfillment_:
+Para habilitar la funcionalidad Multilevel omnichannel inventory, el nuevo valor del campo debe contener el _endpoint_ de **_checkout_, **en lugar del _endpoint_ de _fulfillment_:  
 
 `https://storeabc.vtexcommercestable.com.br/api/checkout?affiliateid=mkp&sc=2`
 
diff --git a/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md b/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md
new file mode 100644
index 000000000..c4f3ea92f
--- /dev/null
+++ b/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md
@@ -0,0 +1,60 @@
+---
+title: 'Mi anuncio no aparece en Mercado Libre'
+id: 2UpudfowEvG97e2lstj4qc
+status: PUBLISHED
+createdAt: 2024-06-13T16:38:00.931Z
+updatedAt: 2024-06-13T18:11:28.836Z
+publishedAt: 2024-06-13T18:11:28.836Z
+firstPublishedAt: 2024-06-13T18:01:04.982Z
+contentType: tutorial
+productTeam: Channels
+author: YRJ73j8mt38D5TUleocQB
+slug: mi-anuncio-no-aparece-en-mercado-libre
+locale: es
+legacySlug: mi-anuncio-no-aparece-en-mercado-libre
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palabras clave:__ *marketplace, catálogo, integración, Mercado Libre, anuncio pausado.*
+
+Cuando se remueve o desactiva un producto de la política comercial utilizada en la integración de Mercado Libre, la actualización de esos detalles se envía automáticamente al marketplace, que a su vez deja de mostrar el producto.
+
+Otro caso es cuando la cantidad del producto cae por debajo del [stock mínimo](https://help.vtex.com/es/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D) establecido en la configuración de la integración con el marketplace. Si el stock de un producto es menor que el valor configurado, se pausa el anuncio para evitar la venta de productos sin stock.
+
+## Solución
+
+Hay dos posibles soluciones para resolver este problema: [verificar la política comercial del producto](#verificar-la-politica-comercial-del-producto) y [verificar la configuración del stock mínimo](#verificar-el-stock-minimo).
+### Verificar la política comercial
+
+La [política comercial](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/15NZiQstCET8zyQUIa7nhw) establece la configuración que se aplica a los productos enviados a Mercado Libre.
+
+Para comprobar que la política comercial esté configurada correctamente en el producto, accede a Catálogo > Todos los productos en el Admin VTEX o escribe Todos los productos en la barra de búsqueda en la parte superior de la página. Luego sigue los pasos a continuación:
+
+1. Haz clic en Filtrar resultados o realizar una búsqueda y [busca el producto](https://help.vtex.com/es/tutorial/produtos-e-skus-beta--2ig7TmROlirWirZjFWZ3By#buscar-productos) cuyo anuncio no está disponible en Mercado Libre.
+2. En la fila del producto deseado, haz clic en `Modificar`.
+3. En la página de registro del producto, comprueba que la política comercial que se utiliza para Mercado Libre esté seleccionada.
+4. Si no lo está, marca la casilla de la política comercial.
+
+  ![politicas-comerciales-es](//images.ctfassets.net/alneenqid6w5/dRDUjjHbk3Ui0ZQEX7SYd/0840562553e4b05d584a9d0a0d453c4b/politicas-comerciales-es.png)
+
+ 5. Haz clic en el botón `Guardar`.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Si tu tienda utiliza el <a href="https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">nuevo Admin VTEX</a>, consulta el artículo <a href="https://help.vtex.com/es/tutorial/produtos-e-skus-beta--2ig7TmROlirWirZjFWZ3By">Productos y SKUs</a> para más información sobre cómo ver y gestionar el catálogo, incluyendo la configuración de las políticas comerciales.
+</div>
+
+### Verificar stock mínimo
+
+Para comprobar la configuración del stock mínimo, accede a Marketplace > Conexiones > Marketplace e integraciones en el Admin VTEX o escribe Marketplaces e integraciones en la barra de búsqueda en el parte superior de la página. Luego sigue los pasos a continuación:
+
+1. [Busca la integración](https://help.vtex.com/es/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V#buscar-e-filtrar) de Mercado Libre.
+2. En la fila de la integración deseada, haz clic en `Editar`.
+3. En `Configuración`, comprueba que el campo Stock mínimo tenga un valor.
+
+  ![inventario-minimo-es](//images.ctfassets.net/alneenqid6w5/wy7Bz5Dcm2pt24HNVHYdZ/bb8666c71a6e0e52f4b6317e14f49ed7/inventario-minimo-es.png)
+
+ 4. Asegúrate de que este campo esté configurado correctamente según se explica en el artículo [Control de stock mínimo para integraciones](https://help.vtex.com/es/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D).
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Si las soluciones propuestas no resuelven el problema, abre un ticket con el <a href="https://help.vtex.com/es/support">soporte VTEX</a>.
+</div>
diff --git a/docs/tutorials/es/my-inventory-is-negative.md b/docs/tutorials/es/my-inventory-is-negative.md
new file mode 100644
index 000000000..7a6370034
--- /dev/null
+++ b/docs/tutorials/es/my-inventory-is-negative.md
@@ -0,0 +1,34 @@
+---
+title: 'Mi stock está negativo'
+id: JSFHaWsASXbnrX9dgNEeP
+status: PUBLISHED
+createdAt: 2024-06-10T11:08:39.990Z
+updatedAt: 2024-06-10T17:21:47.755Z
+publishedAt: 2024-06-10T17:21:47.755Z
+firstPublishedAt: 2024-06-10T17:21:47.755Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: mi-stock-esta-negativo
+locale: es
+legacySlug: mi-stock-esta-negativo
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palabras clave:** *stock, reserva, política comercial, admin VTEX, gestión de stock.*
+
+Cuando la cantidad disponible de un producto se muestra negativa, es posible que haya más ítems [reservados](https://help.vtex.com/es/tutorial/como-a-reserva-funciona--tutorials_92) de la cantidad indicada para el total de stock. Generalmente, este problema ocurre al registrar (dar de baja) un ítem en un pedido que todavía no está reservado por el sistema.
+
+## Solución
+
+La información de stock del ítem debe actualizarse en función de la cantidad de ítems físicos disponibles en el stock. Así, el valor registrado de los ítems en stock deberá ser igual a la suma de los ítems disponibles más los ítems reservados pero que aún no tienen el status **Preparando envío**.
+
+Para actualizar la cantidad correcta en el stock, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Catálogo > Stock > Gestión del stock**, o ingresa **Gestión del stock** en la barra de búsqueda de la parte superior de la página.
+2. Haz clic en **Gestión del stock**.
+3. Busca el SKU deseado.
+4. En la columna **Actualizar recuento**, ingresa la cantidad correcta de ítems físicos en el stock, considerando la suma de los ítems disponibles más los ítems reservados.
+5. Haz clic en **Guardar**.
+
+Cuando dos o más stocks utilizan la misma [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y uno de ellos presenta una cantidad negativa de unidades, el SKU no se mostrará como disponible para la venta, independientemente de que el otro stock tenga unidades disponibles en el [inventario](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
diff --git a/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md b/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md
new file mode 100644
index 000000000..9a84397aa
--- /dev/null
+++ b/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md
@@ -0,0 +1,61 @@
+---
+title: 'Errores en mis pedidos de Mercado Libre'
+id: 170njWgSw9UQ5DG6NRl14d
+status: PUBLISHED
+createdAt: 2024-06-28T15:03:26.959Z
+updatedAt: 2024-06-28T16:08:10.242Z
+publishedAt: 2024-06-28T16:08:10.242Z
+firstPublishedAt: 2024-06-28T16:04:14.266Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: errores-en-mis-pedidos-de-mercado-libre
+locale: es
+legacySlug: errores-en-mis-pedidos-de-mercado-libre
+subcategory: 2LcLWCYaEm5qPmOuYUiKIS
+---
+
+**Tags:** marketplace, catálogo, productos
+**Palabras clave:** integración, Mercado Libre, envío de productos, pedidos
+
+Cuando se produce un error de integración en pedidos entre un marketplace y Mercado Libre, se muestra un mensaje de error en cada pedido. 
+
+Los pedidos presentan errores de integración por dos motivos: **ID de tienda oficial en Mercado Libre** incorrectamente registrado o **Categorías inexistentes en Mercado Libre**. Para comprobar si un pedido contiene errores de integración, en el Admin VTEX accede a **Marketplace > Conexiones > Pedidos o ingresa Pedidos en la barra de búsqueda.**
+
+## Solución
+Considera las siguientes opciones para corregir los errores de integración en los pedidos de Mercado Libre: [verificar el ID de la tienda oficial en Mercado Libre](#comprobar-id-de-la-tienda-oficial-en-mercado-libre) y [verificar la correspondencia de categorías](#comprobar-correspondencia-de-categorías) para errores de integración de pedidos.
+
+### Verificar el ID de la tienda oficial en Mercado Libre 
+Si tu tienda tiene el status de [Tienda Oficial](https://www.mercadolibre.com.mx/tiendas-oficiales/catalogo) en Mercado Libre, debes introducir el ID proporcionado por Mercado Libre en el [registro del conector](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4YvYdgICMosaEgISOYogsi).
+
+Para validar si el ID ingresado es correcto, ve a **Marketplace > Conexiones > Marketplaces e integraciones**  y sigue los pasos que se indican a continuación:
+
+Busca el conector de **Mercado Libre.**
+Haz clic en `Editar`.
+Verifica el ID registrado en el campo `ID de tienda oficial de Mercado Libre`.
+Si el campo está vacío o contiene un ID incorrecto, ingresa la información correcta.
+Haz clic en `Guardar`.
+
+### Verificar correspondencias de categorías
+
+Al realizar el [mapeo de categorías y atributos](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA) con Mercado Libre, es necesario que los atributos de cada categoría registrada en VTEX correspondan con los atributos de las categorías existentes en Mercado Libre. 
+Si alguno de los atributos se rellena incorrectamente, la integración devolverá un error con el siguiente formato:
+`La categoría seleccionada en el atributo category_meli no existe en Mercado Libre.`
+
+Para comprobar las categorías y atributos enviados, accede a **Marketplace > Conexiones > Marketplaces e integraciones**  y sigue los pasos que se indican a continuación:
+
+Busca el conector de **Mercado Libre.**
+Haz clic en `Editar`.
+Haz clic en `Realizar mapeo`.
+Haz clic en la categoría que presenta error.
+Realiza nuevamente el mapeo de acuerdo con las categorías y atributos existentes en Mercado Libre.
+
+<div class="alert alert-info">
+Para identificar el atributo indicado en el mensaje de error, consulta el número inicial de los códigos determinados por Mercado Libre. Haz clic en el nombre de tu país para descargar la plantilla de referencia:
+<p><ul>
+<p><a href="https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip">Brasil</a></p>
+<p><a href="https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar">Argentina</a></p> 
+<p><a href="https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar">Colombia</a></p> 
+<p><a href="https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar">México</a></p>
+</ul></p></div>
+
diff --git a/docs/tutorials/es/my-store-order-was-not-created.md b/docs/tutorials/es/my-store-order-was-not-created.md
new file mode 100644
index 000000000..ab62bb0ff
--- /dev/null
+++ b/docs/tutorials/es/my-store-order-was-not-created.md
@@ -0,0 +1,64 @@
+---
+title: 'No se ha creado el pedido de mi tienda'
+id: 7xQZqkMHXkHCEEZl5UlX8I
+status: PUBLISHED
+createdAt: 2024-07-18T20:10:20.933Z
+updatedAt: 2024-07-18T20:56:20.706Z
+publishedAt: 2024-07-18T20:56:20.706Z
+firstPublishedAt: 2024-07-18T20:56:20.706Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: no-se-ha-creado-el-pedido-de-mi-tienda
+locale: es
+legacySlug: no-se-ha-creado-el-pedido-de-mi-tienda
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palabras clave:** pedido, integración de pedidos, integración XML, configuración de productos, stock negativo, sku sin stock, sku agotado.
+
+Cuando un cliente intenta realizar una compra y se produce un error al crear el pedido, esto puede deberse a varias razones, como problemas relacionados con el pago, logística o [integración del backend](https://help.vtex.com/es/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) con sistemas ERP (sistemas de planificación de recursos empresariales).
+
+Antes de considerar razones complejas para errores en pedidos no creados, aplica los procesos de resolución de problemas (troubleshooting) presentados en este artículo. Algunos de los escenarios de error más comunes son:
+
+* El ítem no estaba disponible en el [stock](https://help.vtex.com/es/tutorial/inventory-management--tutorials_139) y la tienda no estaba configurada para vender productos sin stock (agotados).
+* La integración XML no estaba configurada para enviar información sobre productos sin stock (agotados).
+
+## Soluciones
+
+Considera los siguientes procesos de solución de problemas para errores en la creación de pedidos:
+
+* [Gestionar el stock](#gestionar-el-stock): si no tienes ítems en stock y tu tienda no está configurada para vender productos sin stock (agotados).
+* [Revisar integración XML](#revisar-integracion-xml): si tu integración XML no está configurada para enviar información sobre productos sin stock (agotados).
+
+### Gestionar stock
+
+Hay dos formas de gestionar el [stock](https://help.vtex.com/es/tutorial/inventory-management--tutorials_139):
+
+* **Vía API:** utilizando el endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
+* **Vía Admin VTEX:** accediendo a _Catálogo > Stock > Gestión del stock_.
+
+Las siguientes soluciones se centran en la gestión del stock a través del Admin VTEX:
+
+* **Actualizar recuento de stock:** en la fila correspondiente al SKU y almacén deseados, en la columna _Actualizar recuento_, ingresa el número de ítems disponibles para la venta y haz clic en `Guardar`. Este número debe ser positivo; lo contrario resultaría en un [stock negativo](https://help.vtex.com/es/faq/why-is-my-stock-negative--frequentlyAskedQuestions_159).
+* **Configurar stock ilimitado:** en la fila correspondiente al SKU y almacén deseados, en la columna Stock infinito, haz clic en el botón de activación y después en `Guardar`. Cuando se activa esta configuración, el ítem se considera siempre disponible para la venta y la tienda nunca presentará productos sin stock (agotados).
+
+<div class = "alert alert-info">
+Para realizar la configuración y que los productos sin stock (agotados) se muestren en tu storefront, accede al <b>Admin VTEX > Catálogo > Todos los productos</b> y en la página de configuración del producto, en la pestaña <b>Producto</b>, marca la opción <b>Sí</b> en el campo <i>Mostrar producto sin stock (agotado)</i>.
+</div>
+
+### Revisar la integración XML
+
+XML es un lenguaje de marcado que define y almacena datos de forma compatible. Si la [integración XML de tu tienda](https://help.vtex.com/es/tutorial/configurando-xml--tutorials_242) no tiene definidas ciertas configuraciones, es posible que no pueda exportarse la información del producto.
+
+Puede ocurrir un error debido a la falta de información del producto cuando no hay stock de ese producto y la integración no está configurada para enviar productos _sin stock (agotados)_. Para activar la configuración, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Canales > Integración XML** o ingresa **Integración XML** en la barra de búsqueda de la parte superior de la página.
+2. En la fila de la integración XML deseada, haz clic en `Editar`.
+3. En la pestaña `Editar XML`, en la opción **Mostrar SKU no disponibles,** selecciona la casilla `Mostrar SKU sin stock (agotados) en los resultados`.
+4. Haz clic en `Guardar`.
+
+<div class="alert alert-warning">
+Pueden ocurrir errores al intentar facturar un pedido si hay información XML incorrecta o faltante.
+</div>
+
diff --git a/docs/tutorials/es/navigation.md b/docs/tutorials/es/navigation.md
new file mode 100644
index 000000000..a5ca2b245
--- /dev/null
+++ b/docs/tutorials/es/navigation.md
@@ -0,0 +1,210 @@
+---
+title: 'Navegación Data Pipeline (Beta)'
+id: 4X4hK0zdIHN0Xn5x2MLYYd
+status: PUBLISHED
+createdAt: 2024-02-02T17:48:16.639Z
+updatedAt: 2024-06-21T16:24:13.980Z
+publishedAt: 2024-06-21T16:24:13.980Z
+firstPublishedAt: 2024-05-27T19:26:59.542Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: navegacion
+locale: es
+legacySlug: navegacion
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+El conjunto de datos de navegación opera con dos tablas principales: `pageviews` y `sessions`. `Pageview` se refiere a cada nueva página a la que accede el usuario mientras navega por la tienda, mientras que `session` se define como el conjunto de todas las pageviews realizadas por un usuario en una única visita.
+Cada `session` permanece activa si no se produce una nueva `pageview` durante un periodo de 30 minutos.
+
+<div class="alert alert-warning">
+El conjunto de datos de navegación no captura todos los tipos de eventos que ocurren durante la navegación. Por ejemplo, no se registran clics específicos, eventos especiales ni interacciones con el minicarrito.
+</div>  
+
+En esta sección puedes consultar la siguiente información:
+
+- [Características de los datos de navegación](#caracteristicas-de-los-datos)
+- [Tabla sessions](#tabla-sessions)
+- [Tabla pageviews](#tabla-pageviews)
+- [Análisis con datos de navegación](#analisis-con-datos-de-navegacion)
+- [Correlaciones con otros datos](#correlaciones-con-otros-datos)
+
+## Características de los datos
+
+| **Característica** | **Descripción** |
+|:---:|:---:|
+| **Origen** | El conjunto de datos tiene lugar desde un script ejecutado en el frontend de la tienda, que registra información sobre las sesiones y actividades de los usuarios. |
+| **Disponibilidad** | Puedes acceder a los datos de navegación de dos formas: a través del dashboard Vista general en el Admin VTEX, donde se concentran el total de sesiones y el embudo de conversión, o a través de herramientas de terceros como Google Analytics. |
+| **Historial** | Los datos se conservan durante dos años, a partir de 2022 para los clientes que ya utilizan la plataforma VTEX. |
+| **Intervalo mínimo de actualización** | Una hora. |
+
+<div class="alert alert-warning">
+Data Pipeline solo proporciona datos de sesiones originadas en las soluciones de <i>storefront</i> de VTEX: CMS Legado, Store Framework y FastStore. VTEX no tiene acceso a sesiones originadas en marketplaces de terceros o storefronts de tiendas propietarias. Además, las personalizaciones realizadas en el <i>frontend</i> de la tienda pueden interferir o incluso desactivar el <i>script,</i> provocando que algunas sesiones no se registren o que la tasa de conversión observada en el dashboard no sea precisa.
+<p>Para minimizar el impacto en el desempeño de la tienda, el <i>script</i> está configurado para ser el último elemento en cargarse en la página. Esto significa que es posible que no se capturen sesiones muy breves.</p>
+  </div>  
+
+## Tabla sessions  
+
+Esta tabla contiene solo las sesiones finalizadas, ya sea por inactividad o porque culminaron en una compra. Se ordena por `session_id`, `session_end_time` y `store_name`. Por este motivo, evita filtrar grandes intervalos de datos por columnas que no están relacionados con esta estrategia de ordenación.   
+Consulta a continuación los campos que componen la tabla.  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | ID de control de ingesta de datos. |
+| **session_id** | character varying(127) | UUID (identificador único universal) de la sesión, correspondiente a la cookie VtexRCSessionIdv7. |
+| **store_name** | character varying(127) | Nombre de la tienda que originó las vistas de página durante esta sesión. |
+| **account_name** | character varying(127) | Cuenta VTEX de la tienda que está generando esta sesión. |
+| **economic_group_id** | character varying(127) | Identificador del grupo económico para facturación. |
+| **economic_group_name** | character varying(1024) | Nombre del grupo económico para facturación. |
+| **company_id** | character varying(127) | Identificador de la empresa para facturación. |
+| **company_name** | character varying(1024) | Nombre de la empresa para facturación. |
+| **main_account_name** | character varying(127) | Nombre de la cuenta VTEX principal relacionada con la tienda que generó esta sesión. |
+| **os_family** | character varying(1023) | Familia del sistema operativo, extraída del user_agent. |
+| **os_major** | character varying(1023) | Versión principal del sistema operativo, extraída del user_agent. |
+| **os_minor** | character varying(1023) | Versión menor del sistema operativo, extraída del user_agent. |
+| **os_patch** | character varying(1023) | Parche del sistema operativo, extraído del user_agent. |
+| **os_patch_minor** | character varying(1023) | Parche menor del sistema operativo, extraído del user_agent. |
+| **device_brand** | character varying(1023) | Marca del dispositivo, extraída del user_agent. |
+| **device_family** | character varying(1023) | Familia del dispositivo, extraída del user_agent. |
+| **device_model** | character varying(1023) | Modelo del dispositivo, extraído del user_agent. |
+| **browser_family** | character varying(1023) | Familia del navegador, extraída de user_agent. |
+| **browser_major** | character varying(1023) | Versión principal del navegador, extraída del user_agent. |
+| **browser_minor** | character varying(1023) | Versión menor del navegador, extraída del user_agent. |
+| **browser_patch** | character varying(1023) | Parche del navegador, extraído del user_agent. |
+| **user_id** | character varying(16383) | Identificador único del comprador, mapeado por la cookie VtexRCMacIdv7. |
+| **pageviews_count** | integer | Recuento de páginas vistas en esta sesión. |
+| **views_home** | integer | Recuento de páginas de inicio vistas en esta sesión. |
+| **views_category** | integer | Recuento de vistas de páginas de [categoría](https://help.vtex.com/es/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) en esta sesión. |
+| **views_department** | integer | Recuento de páginas de [departamento](https://help.vtex.com/es/tutorial/o-que-e-um-departamento--22rKjmYWVmmKAK8CWa8yKw) vistas en esta sesión. |
+| **views_search** | integer | Recuento de páginas de búsqueda vistas en esta sesión. |
+| **views_product** | integer | Recuento de páginas de producto vistas en esta sesión. |
+| **views_checkout** | integer | Recuento de páginas de checkout vistas en esta sesión. |
+| **views_other** | integer | Recuento de páginas vistas que no sean de [producto](https://help.vtex.com/es/tutorial/o-que-e-um-produto--2zrB2gFCHyQokCKKE8kuAw), búsqueda, [categoría](https://help.vtex.com/es/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg), [departamento](https://help.vtex.com/es/tutorial/o-que-e-um-departamento--22rKjmYWVmmKAK8CWa8yKw) o checkout en esta sesión. |
+| **views_checkout_cart** | integer | Recuento de páginas de checkout vistas en la fase de carrito. |
+| **views_checkout_payment** | integer | Recuento de páginas de checkout vistas en la fase de pago. |
+| **views_checkout_shipping** | integer | Recuento de páginas de checkout vistas en la fase de envío. |
+| **views_checkout_profile** | integer | Recuento de páginas de checkout vistas en la fase de perfil. |
+| **views_checkout_orderplaced** | integer | Recuento de páginas de checkout vistas en la fase de pedido realizado. |
+| **views_checkout_email** | integer | Recuento de páginas de checkout vistas en la fase de email. |
+| **workspace** | character varying(16383) | Workspace de VTEX. |
+| **user_agent** | character varying(16383) | String de user_agent extraída del servidor del request. |
+| **is_first_visit** | boolean | Indica si es la primera visita del usuario. No cuenta para visitantes recurrentes en diferentes navegadores. |
+| **session_start_time** | timestamp without time zone | Fecha y hora de inicio de sesión. |
+| **entrance_page_url** | character varying(16383) | URL de la primera página vista en esta sesión. |
+| **entrance_page_type** | character varying(16383) | Tipo de página de la primera página vista en esta sesión. |
+| **entrance_page_checkout_step** | character varying(16383) | Fase de checkout de la primera página vista en esta sesión. |
+| **session_end_time** | timestamp without time zone | Fecha y hora de fin de sesión. |
+| **exit_page_url** | character varying(16383) | URL de la última página vista en esta sesión. |
+| **exit_page_type** | character varying(16383) | Tipo de página de la última página vista en esta sesión. |
+| **exit_page_checkout_step** | character varying(16383) | Fase de checkout de la última página vista en esta sesión. |  
+
+## Tabla pageviews  
+
+Cada ítem de esta tabla corresponde a una página vista por el comprador, como la página de inicio, la página de producto y la fase de checkout.
+Una página vista se cuenta después de que el navegador del comprador haya cargado la página. Cada página tiene atributos específicos y, como esta tabla lo reúne todo en un único esquema, aparecerán muchos valores nulos. Por ejemplo, se espera que los atributos de las páginas de producto sean nulos cuando la vista de la página corresponde a una fase de carrito.  
+Consulta a continuación los campos que componen la tabla.  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **client_date** | timestamp without time zone | Fecha y hora de la página vista. |
+| **session_id** | character varying(127) | Identificador único de una sesión, que se mapea directamente a la cookie VtexRCSessionIdv7. |
+| **page_type** | character varying(127) | Tipo da página visitada, con valores predefinidos como 'home', 'category', 'product', entre otros. |
+| **checkout_step** | character varying(127) | Fase de checkout de la página, válida cuando page_type es 'checkout'. |
+| **economic_group_id** | character varying(127) | Identificador del grupo económico para facturación. |
+| **economic_group_name** | character varying(1024) | Nombre del grupo económico para facturación. |
+| **company_id** | character varying(127) | Identificador de la empresa para facturación. |
+| **company_name** | character varying(1024) | Nombre de la empresa para facturación. |
+| **main_account_name** | character varying(127) | Cuenta principal de Licence Manager a la que la tienda está asociada. |
+| **account_name** | character varying(127) | Cuenta de Licence Manager a la que la tienda está asociada. |
+| **store_name** | character varying(127) | Nombre de la tienda que produjo el evento de página vista. |
+| **url** | character varying(16383) | URL completa de la página vista. |
+| **store_host** | character varying(127) | Nombre de host extraído de la URL. |
+| **page_url** | character varying(16383) | URL limpia de la página vista, sin parámetros de consulta. |
+| **ref** | character varying(16383) | URL de la página que remitió al comprador a esta página. |
+| **workspace** | character varying(127) | Workspace de VTEX, generalmente 'master'. |
+| **workspace_ab_test_id** | character varying(127) | ID de prueba AB extraído del nombre del workspace. |
+| **user_agent** | character varying(16383) | String del User-Agent extraída del lado del servidor. |
+| **os_family** | character varying(1023) | Familia de SO extraída del user_agent. |
+| **os_major** | character varying(1023) | Versión principal del SO, extraída del user_agent. |
+| **os_minor** | character varying(1023) | Versión menor del SO, extraída del user_agent. |
+| **os_patch** | character varying(1023) | Parche del SO extraído del user_agent. |
+| **os_patch_minor** | character varying(1023) | Parche menor del SO extraído del user_agent. |
+| **device_brand** | character varying(1023) | Marca del dispositivo extraída del user_agent. |
+| **device_family** | character varying(1023) | Familia del dispositivo, extraída del user_agent. |
+| **device_model** | character varying(1023) | Modelo del dispositivo, extraído del user_agent. |
+| **browser_family** | character varying(1023) | Familia del navegador, extraída de user_agent. |
+| **browser_major** | character varying(1023) | Versión principal del navegador, extraída del user_agent. |
+| **browser_minor** | character varying(1023) | Versión menor del navegador, extraída del user_agent. |
+| **browser_patch** | character varying(1023) | Parche del navegador, extraído del user_agent. |
+| **user_id** | character varying(127) | Identificador único del comprador. |
+| **is_first_visit** | boolean | Indica si es la primera visita del usuario. |
+| **category_id** | character varying(127) | Identificador de la categoría. |
+| **nombre_categoría** | character varying(16383) | Nombre de la categoría. |
+| **department_id** | character varying(127) | Identificador del departamento. |
+| **department_name** | character varying(16383) | Nombre del departamento. |
+| **product_id** | character varying(127) | Identificador del producto. |
+| **product_reference_id** | character varying(1024) | Referencia del producto. |
+| **product_name** | character varying(16383) | Nombre del producto. |
+| **product_brand_id** | integer | Identificador de la marca del producto. |
+| **product_brand_name** | character varying(1024) | Nombre de la marca del producto. |
+| **product_department_id** | integer | Identificador del departamento del producto. |
+| **product_department_name** | character varying(1024) | Nombre del departamento del producto. |
+| **product_category_id** | integer | Identificador de la categoría del producto. |
+| **product_category_name** | character varying(1024) | Nombre de la categoría del producto. |
+| **product_list_price** | numeric(22,4) | Precio de lista del producto. |
+| **product_price** | numeric(22,4) | Precio del producto. |
+| **seller_id** | character varying(127) | Identificador del seller. |
+| **seller_ids** | character varying(16383) | Identificadores del seller. |
+| **site_search_term** | character varying(16383) | Término de búsqueda en el sitio web. |
+| **site_search_form** | character varying(16383) | Formulario de búsqueda en el sitio web. |
+| **site_search_category** | character varying(127) | Categoría de búsqueda en el sitio web. |
+| **site_search_results** | integer | Resultados de búsqueda en el sitio web. |
+| **sales_channel** | character varying(10) | Canal de ventas. |
+| **order_form_id** | character varying(127) | Identificador del formulario de pedido. |
+| **order_form_shipping** | numeric(22,4) | Costo de envío en el formulario de pedido. |
+| **order_form_total** | numeric(22,4) | Total en el formulario de pedido. |
+| **order_form_tax** | numeric(22,4) | Impuesto en el formulario de pedido. |
+| **campaign_name** | character varying(16383) | Nombre de la campaña. |
+| **campaign_source** | character varying(16383) | Fuente de la campaña. |
+| **campaign_medium** | character varying(16383) | Medio de la campaña. |
+| **internal_campaign_name** | character varying(16383) | Nombre de la campaña interna. |
+| **internal_campaign_part** | character varying(16383) | Parte de la campaña interna. |
+| **order_form_payment_type** | character varying(127) | Tipo de pago en el formulario de pedido. |
+| **order_group** | character varying(127) | Grupo de pedido. |
+| **transaction_id** | character varying(127) | Identificador de la transacción. |
+| **visitor_login_state** | character varying(16383) | Status de inicio de sesión del visitante. |
+| **visitor_type** | character varying(16383) | Tipo de visitante. |
+| **visitor_optin_newsletter** | boolean | Consentimiento del visitante para recibir newsletter. |
+| **profile_id** | character varying(127) | ID del perfil de comprador, recibido del sistema VTEX Profile. |
+| **batch_id** | character varying(13) | ID de control de ingesta de datos. |
+| **id** | character varying(36) | UUID generado durante la ingesta de datos. |
+| **transaction_products** | super | Productos en la transacción. |
+| **transaction_total** | numeric(22,4) | Total de la transacción. |  
+
+## Análisis con datos de navegación  
+
+Los datos de navegación pueden utilizarse para los siguientes análisis:
+
+- **Tasa de conversión general:** calcula la proporción de sesiones que resultaron en una compra con relación al total de sesiones, para evaluar la eficacia general del sitio web para convertir visitantes en compradores.  
+- **Análisis del embudo de conversión:** agrupa las páginas vistas por etapas del embudo (página de inicio, búsqueda, producto, carrito, checkout) y cuenta cuántas sesiones pasaron por cada etapa, identificando dónde abandonan los usuarios.  
+- **Páginas más visitadas:** cuenta el número de páginas vistas para cada tipo de página (página de inicio, categoría, producto) para identificar las páginas que más captan la atención y optimizarlas para la conversión.  
+- **Seguimiento de rutas del usuario:** hace un seguimiento de la secuencia de las páginas vistas en cada sesión para comprender la trayectoria del usuario y descubrir patrones de navegación comunes.  
+- **Fuente del tráfico:** analiza la URL de referencia de cada sesión para determinar el origen del tráfico y conocer los canales de marketing que son más eficaces.  
+- **Tasa de rebote por tipo de página:** identifica las sesiones que finalizan tras una única pageview y calcula la tasa de rebote por tipo de página para mejorar el contenido o el diseño de esas páginas.  
+
+## Correlaciones con otros datos
+
+En los datos de navegación de VTEX observamos importantes interacciones con otros conjuntos de datos que enriquecen el análisis del comportamiento de los usuarios, por ejemplo:  
+
+- **Interacción con datos de pedidos:** el análisis comparativo entre navegación y conversiones de pedidos revela el impacto de las jornadas de usuario en las decisiones de compra.  
+- **Relación con los SKU:** la interacción de los usuarios con páginas de producto y categorías ofrece insights sobre la popularidad y eficacia de la presentación de los productos.  
+- **Datos de marketing y campañas:** la correlación entre la navegación y las campañas de marketing ayuda a evaluar la eficiencia de estas campañas a la hora de atraer tráfico y generar conversiones.  
+
+### Descubra otros conjuntos de datos
+
+- [Stock](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Pagos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Precios](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promociones](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/es/new-integration-with-erede-erederest.md b/docs/tutorials/es/new-integration-with-erede-erederest.md
index c8965dc5a..0df73a2b4 100644
--- a/docs/tutorials/es/new-integration-with-erede-erederest.md
+++ b/docs/tutorials/es/new-integration-with-erede-erederest.md
@@ -25,11 +25,11 @@ Para configurar la nueva versión, primero usted debe solicitar a Rede la activa
 
 Una vez notificado, acceda al menú __e.Rede > Ajustes > Generar token__.
 
-![GerarToken](https://images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
+![GerarToken](//images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
 
 A continuación, basta con hacer clic en el botón de __Gerar Token__.
 
-![GerarToken Click](https://images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
+![GerarToken Click](//images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
 
 Con eso, usted podrá ver el token que deberá ser informado en el formulario de configuración de la afiliación de gateway ERedeRest. Además del token, usted también necesitará informar el PV, que es el número de identificación del establecimiento en el sitio de Rede.
 
@@ -39,10 +39,10 @@ Para hacer esta configuración en VTEX,
 2. En __Configuración__, acceda __Afiliaciones__;
 3. Haga clic en el botón verde __+__ _Quiero recibir pagos por este conector..._ y busque el conector __ERedeRest.__
 
-![erederestES](https://images.ctfassets.net/alneenqid6w5/33o1Nwlo0geAy2yIUkUuG4/92c3a9d28f7bc35ca9f5652dc2679fe9/erederestES.jpg) 
+![erederestES](//images.ctfassets.net/alneenqid6w5/33o1Nwlo0geAy2yIUkUuG4/92c3a9d28f7bc35ca9f5652dc2679fe9/erederestES.jpg) 
 
-![erederestES-config](https://images.ctfassets.net/alneenqid6w5/tTuJ0rmx44aggkAssQSsi/63f9539d9db6bdf6bb73276be63c5fa8/erederestES-config.jpg)
+![erederestES-config](//images.ctfassets.net/alneenqid6w5/tTuJ0rmx44aggkAssQSsi/63f9539d9db6bdf6bb73276be63c5fa8/erederestES-config.jpg)
 
-![PegarPV](https://images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
+![PegarPV](//images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
 
 Este nuevo conector ofrece una serie de opciones de configuración, entre ellas está el soporte al ApplePay.
diff --git a/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md b/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
index 092337415..d95afcb15 100644
--- a/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
+++ b/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
@@ -1,10 +1,10 @@
 ---
 title: 'Registros del Newsletter con control <vtex.cmc:newsletterOptIn/>'
 id: xqKrRRHBscEI8O6UKi8eE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-07T18:35:59.237Z
-updatedAt: 2023-03-31T11:24:39.916Z
-publishedAt: 2023-03-31T11:24:39.916Z
+updatedAt: 2023-12-08T18:44:28.114Z
+publishedAt: 
 firstPublishedAt: 2019-01-25T17:16:54.823Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/es/offer-details.md b/docs/tutorials/es/offer-details.md
index 806f63d50..db0d9d5ee 100644
--- a/docs/tutorials/es/offer-details.md
+++ b/docs/tutorials/es/offer-details.md
@@ -1,10 +1,10 @@
 ---
 title: 'Gestión de anuncios: detalles del anuncio'
 id: 4FF9QYAewqAn610mDHwb0P
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T01:07:12.412Z
-updatedAt: 2023-03-31T04:51:33.756Z
-publishedAt: 2023-03-31T04:51:33.756Z
+updatedAt: 2024-06-20T21:34:45.076Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:13:19.773Z
 contentType: tutorial
 productTeam: Channels
@@ -15,6 +15,13 @@ legacySlug: detalles-del-anuncio
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
+<div class="alert alert-info">
+Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
+Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
+ </div>  
+
 Un anuncio es un SKU cuyo precio y stock fueron configurados por un seller y que fue enviado a diferentes canales de venta. En el módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE), los sellers supervisan el envío de sus anuncios a marketplaces y su sincronización.
 
 La página de **Detalles del anuncio** es donde se puede visualizar toda la información sobre un anuncio específico. A través de esta, el seller visualiza las interacciones que se produjeron con un anuncio, los [detalles de cada interacción](https://help.vtex.com/es/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf) y los errores detectados. Detalles de la interacción estarán disponibles durante diez días después del registro.
@@ -36,7 +43,7 @@ La página **Detalles del anuncio** incluye las siguientes secciones:
 
 ## Encabezado
 
-![Offer details ES cabecalho](https://images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/7daa6c6a14fa3f1bdb959526d5f33157/Offer_details_ES_cabecalho.jpg)
+![Offer details ES cabecalho](//images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/7daa6c6a14fa3f1bdb959526d5f33157/Offer_details_ES_cabecalho.jpg)
 
 El encabezado presenta la información principal del anuncio para su rápida visualización, como imagen, nombre del canal, status, ID en VTEX e ID en el canal. También permite realizar las siguientes interacciones mediante el botón `Editar`:
 
@@ -52,13 +59,13 @@ En este bloque, se presenta información sobre los status posibles para un  dete
 
 ### Status: sincronizado
 
-![Offer details PT status sucesso](https://images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/f9aae1830daa0fe200e2f7ec5b470d7e/Offer_details_ES_status_sucesso.jpg)
+![Offer details PT status sucesso](//images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/f9aae1830daa0fe200e2f7ec5b470d7e/Offer_details_ES_status_sucesso.jpg)
 
 El status *Sincronizado* significa que el anuncio ha sido recibido con éxito en un canal y está siendo actualizado tanto por el marketplace como por el seller, en tiempo real.   
 
 ### Status: error
 
-![Offer details PT status erro](https://images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/cba423c498f0003a3990768c22a993a4/Offer_details_ES_status_erro.jpg)
+![Offer details PT status erro](//images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/cba423c498f0003a3990768c22a993a4/Offer_details_ES_status_erro.jpg)
 
 El status *Error* significa que el sistema ha encontrado un problema que impide el envío o la actualización de un anuncio en un canal, de modo que se requiere que el seller lo solucione. Los errores pueden originarse tanto del lado del seller VTEX, como descripciones de productos que exceden el límite de caracteres, como del lado del marketplace, como llamadas de API con errores.   
 
@@ -76,19 +83,19 @@ Si todavía hay errores por corregir, o si están todos corregidos pero se está
 
 ### Status: indisponible
 
-![Offer details PT status indisponivel](https://images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/3fcfa6c8636db3979e7e23b4af740da4/Offer_details_ES_status_indisponivel.jpg)
+![Offer details PT status indisponivel](//images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/3fcfa6c8636db3979e7e23b4af740da4/Offer_details_ES_status_indisponivel.jpg)
 
 El status *Indisponible* se produce cuando el anuncio es descartado, por estar inactivo o no estar incluido en la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) determinada para el canal.
 
 ### Status: enviando
 
-![Offer details PT status enviando](https://images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1a7b65d75c2fe5ca1025663298f97970/Offer_details_ES_status_enviando.jpg)
+![Offer details PT status enviando](//images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1a7b65d75c2fe5ca1025663298f97970/Offer_details_ES_status_enviando.jpg)
 
 El status *Enviando* es un estado intermedio, cuando los anuncios aún están en proceso de ser enviados al canal. Este status comprende anuncios que se envían al marketplace por primera vez, que están migrando a un nuevo canal o que han sido reenviados después de haber sido descartados en un canal.   
 
 ## Lista de interacciones
 
-![Offer details PT lista interacoes](https://images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/3b825866f07b646c065df4004c802ff3/Offer_details_ES_lista_interacoes.jpg)
+![Offer details PT lista interacoes](//images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/3b825866f07b646c065df4004c802ff3/Offer_details_ES_lista_interacoes.jpg)
 
 La pestaña *Interacciones* de la página **Detalles del anuncio** muestra todas las actualizaciones de `stock`, `precio` o `catálogo` que sufrió el SKU. Cada fila corresponde a una interacción producida en el anuncio, e incluye los siguientes datos:
 
diff --git a/docs/tutorials/es/offer-management-moderation-and-quality-of-mercado-libre.md b/docs/tutorials/es/offer-management-moderation-and-quality-of-mercado-libre.md
index 5ac274547..d6136a41a 100644
--- a/docs/tutorials/es/offer-management-moderation-and-quality-of-mercado-libre.md
+++ b/docs/tutorials/es/offer-management-moderation-and-quality-of-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Gestión de anuncios: moderación y calidad de los anuncios en Mercado L
 id: xSbPzA41jiWPAorlBCEA4
 status: PUBLISHED
 createdAt: 2022-10-24T16:38:07.914Z
-updatedAt: 2022-10-24T17:03:57.020Z
-publishedAt: 2022-10-24T17:03:57.020Z
+updatedAt: 2024-06-20T21:41:34.703Z
+publishedAt: 2024-06-20T21:41:34.703Z
 firstPublishedAt: 2022-10-24T17:03:57.020Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/offer-management.md b/docs/tutorials/es/offer-management.md
index 07e5afc85..8865b8335 100644
--- a/docs/tutorials/es/offer-management.md
+++ b/docs/tutorials/es/offer-management.md
@@ -1,10 +1,10 @@
 ---
 title: 'Módulo Gestión de anuncios'
 id: 7MRb9S78aBdZjFGpbuffpE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T00:44:49.452Z
-updatedAt: 2023-03-31T04:39:55.235Z
-publishedAt: 2023-03-31T04:39:55.235Z
+updatedAt: 2024-06-20T21:34:27.585Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:05:49.343Z
 contentType: tutorial
 productTeam: Channels
@@ -15,19 +15,26 @@ legacySlug: lista-de-anuncios
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
+<div class="alert alert-info">
+Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
+Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
+ </div>  
+
 El módulo **Gestión de anuncios** permite a los _sellers_ hacer el seguimiento del envío y la sincronización de los anuncios de las integraciones con los canales de venta. En VTEX, un anuncio es un SKU cuyo precio y stock fueron configurados por un _seller_ y que fue enviado a un canal de ventas.
 
-![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 **Gestión de anuncios** permite hacer un seguimiento de los anuncios con [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic y Premium), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y marketplaces VTEX. Para los conectores que desean integrarse a través de API, existe la [Guía de integración de Gestión de anuncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 Para acceder al módulo, en el Admin VTEX, ingresa en **Marketplace > Conexiones > Gestión de anuncios**. Una vez hecho esto, aparecerá la siguiente interfaz:
 
-![sent-offers-es_2](https://images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/a4b532bd1367cc8f15e25afe1ce78fa0/sent-offers-es_2.png)
+![sent-offers-es_2](//images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/a4b532bd1367cc8f15e25afe1ce78fa0/sent-offers-es_2.png)
 
 La interfaz de **Gestión de anuncios** mostrará una lista con tus anuncios y podrás hacer clic sobre cada uno de ellos para acceder a los [detalles del anuncio](https://help.vtex.com/es/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) y verificar los [detalles de la interacción](https://help.vtex.com/es/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf). Las interacciones son los registros del anuncio durante todo el proceso de sincronización y el envío al canal de ventas. Los registros de los detalles de la interacción están disponibles durante diez días para consulta.
 
-![diagrama ju meyer sent offers es](https://images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/a3cae86d4d8a5126d448471e37b037b1/diagrama_ju_meyer_sent_offers_es.png)
+![diagrama ju meyer sent offers es](//images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/a3cae86d4d8a5126d448471e37b037b1/diagrama_ju_meyer_sent_offers_es.png)
 
 En la página **Gestión de anuncios**, puedes realizar las siguientes acciones:
 
diff --git a/docs/tutorials/es/offer-quality-filters.md b/docs/tutorials/es/offer-quality-filters.md
index 944514561..5c1940d90 100644
--- a/docs/tutorials/es/offer-quality-filters.md
+++ b/docs/tutorials/es/offer-quality-filters.md
@@ -1,10 +1,10 @@
 ---
 title: 'Filtros de calidad de anuncios'
 id: 4xm0gi8leCyxHj8YdgHSJH
-status: CHANGED
+status: PUBLISHED
 createdAt: 2023-02-27T12:15:26.682Z
-updatedAt: 2023-05-30T21:12:51.762Z
-publishedAt: 2023-02-28T13:45:44.808Z
+updatedAt: 2024-06-20T21:38:38.621Z
+publishedAt: 2024-06-20T21:38:38.621Z
 firstPublishedAt: 2023-02-27T19:32:00.584Z
 contentType: tutorial
 productTeam: Channels
@@ -12,7 +12,7 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: calidad-de-anuncios
 locale: es
 legacySlug: calidad-de-anuncios
-subcategory: 4hU8QWlzhxWg711Kz7Gmib
+subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
 Los [marketplaces](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex) tienen que revisar y aprobar anuncios enviados por los sellers para agregar los productos al catálogo. En el Admin VTEX, este [proceso de catalogación](https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus--tutorials_396) se realiza a través de la página «SKU recibidos».
@@ -21,7 +21,7 @@ Es importante para la operación del marketplace que haya criterios de calidad p
 
 **Calidad de anuncios** es la página donde los marketplaces registran y gestionan los grupos de requisitos aplicados al proceso de catalogación de SKU recibidos. Para accederla, en su VTEX Admin, haz clic en **Marketplace > Calidad de anuncios**, o escriba __"Calidad del anuncio"__ en la barra de búsqueda.
 
-![ES offer quality](https://images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/890bb24504e8f6b809cd318fb85ed53a/ES_offer_quality.png)
+![ES offer quality](//images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/890bb24504e8f6b809cd318fb85ed53a/ES_offer_quality.png)
 
 Con este tutorial, sepa cómo:
 
@@ -46,7 +46,7 @@ La funcionalidad permite que el operador del marketplace pueda realizar una seri
 | Aportar más transparencia a los criterios de catalogación de anuncios recibidos y a la medida en que los sellers y anuncios los cumplen.                                                            | Permite identificar los sellers y los tipos de anuncios que no cumplen los requisitos, lo que acelera la corrección de problemas.                 |
 
 ## Ver "Default requirements" 
-![ESDefault requirements](https://images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/b86fb58a9c6b454c31fb0bf0829adf4f/ESDefault_requirements.png)
+![ESDefault requirements](//images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/b86fb58a9c6b454c31fb0bf0829adf4f/ESDefault_requirements.png)
 
 La página estándar tiene algunos requisitos preestablecidos que se aplicarán a todas las categorías, sellers y marcas, conocidas como «Default requirements». Algunos de estos criterios se configuran de forma nativa en [VTEX Matcher](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), la herramienta aplicada a los marketplaces VTEX para ayudar en el proceso de catalogación de los anuncios recibidos.
 
diff --git a/docs/tutorials/es/offer-status.md b/docs/tutorials/es/offer-status.md
new file mode 100644
index 000000000..8e1fb66e3
--- /dev/null
+++ b/docs/tutorials/es/offer-status.md
@@ -0,0 +1,247 @@
+---
+title: 'Status de los anuncios'
+id: 2OE87wU26F7lApl99OdwvJ
+status: PUBLISHED
+createdAt: 2023-09-29T19:16:05.771Z
+updatedAt: 2024-03-04T20:03:00.144Z
+publishedAt: 2024-03-04T20:03:00.144Z
+firstPublishedAt: 2023-09-29T20:07:16.003Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: status-de-los-anuncios
+locale: es
+legacySlug: estado-del-anuncio-beta
+subcategory: 2zVauFUkYn8vgS0y0MfWeK
+---
+
+El módulo **Status de los anuncios** permite a los sellers realizar un seguimiento del envío y la sincronización de los anuncios de las integraciones con los canales de venta. En VTEX, un anuncio es un SKU activo de un seller que ha configurado su precio y stock, y lo ha enviado a un canal de ventas.  
+
+En **Status de los anuncios** se puede llevar a cabo un seguimiento de los anuncios enviados únicamente a los marketplaces VTEX. Para acceder al módulo en el Admin VTEX, ve a **Marketplace > Conexiones > Status de los anuncios,** o ingresa **Status de los anuncios** en la barra de búsqueda.  
+
+![Pantalla de estado de la oferta](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/91b3ae83719e933617324f74223d736b/-ES-_Offer_Status_-_GIF.gif)
+
+La página **Status de los anuncios** está compuesta por tres pestañas: **[Publicados](#pestana-publicados)**, **[Problemas](#pestana-problemas)** y **[A la espera de finalización.](#pestana-a-la-espera-de-finalizacion)** Todas ellas presentan una lista de tus anuncios de acuerdo con su status actual. Accede y consulta los detalles de cada anuncio, como status, stock, precio, fecha de actualización y los motivos de rechazo en el marketplace.
+
+![Estado de los anuncios shcema](//images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/9e17eeb599bb0d5e3dec1933097d4af0/offer-status-schema-es.png)
+
+## Pestaña Publicados
+
+En la pestaña **Publicados**, el seller puede hacer un seguimiento de los anuncios enviados que ya han sido aprobados por el marketplace. En esta pestaña están disponibles las siguientes acciones:
+
+- [Buscar y filtrar anuncios](#buscar-y-filtrar-anuncios)
+- [Ver información de los anuncios](#ver-informacion-de-los-anuncios)
+- [Editar información de los anuncios](#editar-informacion-de-los-anuncios)
+- [Exportar la lista de anuncios publicados](#exportar-la-lista-de-anuncios-publicados)
+
+### Buscar y filtrar anuncios
+
+En la parte superior derecha de la página hay una barra de búsqueda con el ícono de una lupa<i class="fas fa-search"></i>, en la que puedes buscar un anuncio por el **ID del SKU y el nombre del anuncio.**
+
+Además, los resultados de la búsqueda pueden filtrarse según los siguientes criterios:
+
+- **Marketplace:** canal de ventas al que se envió el anuncio.
+- **Stock:** cantidad de stock de un producto, que puede ser:
+  - Mínimo: número mínimo de ítems en stock de un producto.
+  - Máximo: número máximo de ítems en stock de un producto.
+- **Actualización:** status de actualización de precios y stock de los anuncios ya publicados.
+
+Para filtrar los anuncios por **Marketplace**, haz clic en la flecha hacia abajo situada junto al término, marca en la casilla de selección los marketplaces deseados y, a continuación, haz clic en **Aplicar**.
+
+Para filtrar los anuncios por **Stock**, haz clic en la flecha hacia abajo situada junto al filtro, ingresa el número de stock mínimo, stock máximo, o ambos, y haz clic en **Aplicar**.
+
+![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/0cc494ba4b34b71a2aaf21cfb3ed1a21/inventario-offer-status.png)
+
+Para filtrar los anuncios por **Actualización**, haz clic en la flecha hacia abajo situada junto al filtro, selecciona una de las opciones y haz clic en **Aplicar.**
+
+Consulta a continuación las opciones disponibles para este filtro:
+
+- **Actualizados**: son anuncios cuyo precio y/o stock han sido actualizados por el seller y se procesaron con éxito.
+- **Error al actualizar:** anuncios que presentaban inconsistencias y, por lo tanto, no pudieron ser actualizados.
+
+![Filtro atualizado offer status](//images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/fa8829e63abbb196a93296e24d12a960/actualizaci_n-offer-status.png)
+
+Puedes utilizar un único filtro o combinarlos en una misma búsqueda. Los filtros no vienen preseleccionados de manera predeterminada, lo que significa que la página inicial mostrará la cantidad total de anuncios existentes.
+
+### Ver información de los anuncios
+
+En la parte superior de la página **Status de los anuncios** se muestran los anuncios del seller con la siguiente información:
+
+- Número de anuncios publicados en relación con los anuncios enviados.
+- Número de anuncios con status **Actualizado.**
+- Número de anuncios con status **Error al actualizar.**
+
+En la lista de anuncios se muestran columnas con la siguiente información:
+
+| **Columna** | **Descripción** |
+|---|---|
+| **Nombre** | Muestra la imagen del SKU, el título del anuncio en el canal de ventas y el ID del SKU en VTEX. |
+| **Marketplace** | Canal de ventas al que se envió el anuncio. |
+| **Precio** | Precio del SKU del anuncio. |
+| **Stock** | Cantidad de items en  <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">stock</a> para el SKU del anuncio. |
+| **Actualización** | Estado del proceso de la actualización, pudiendo ser Actualizados <i class="far fa-check-circle"></i> o Error al actualizar<div class="error-icon"></div>. |
+
+Para ordenar los anuncios en orden ascendente o descendente haz clic en los nombres de las columnas. Por ejemplo, al hacer clic en la columna **Precio**, la lista se organiza por el precio del anuncio, ya sea de menor a mayor o de mayor a menor.
+
+### Editar información de los anuncios
+
+Al hacer clic en un anuncio se abrirá una ventana con barras informativas con los siguientes datos:
+
+- **Precio:** muestra el precio actual del anuncio, cuándo se produjo la última actualización y si se realizó correctamente o no.
+- **Stock:** cuál es el stock actual del ítem anunciado, cuándo se produjo la última actualización y si se realizó correctamente o no.
+- **Contenido:** cuándo se actualizó el contenido por última vez y si la actualización se realizó correctamente o no.
+
+Para actualizar la información de un anuncio ya publicado el seller debe realizar los siguientes pasos:
+
+1. En la pestaña **Publicados** haz clic en el anuncio deseado.
+2. Haz clic en el <i class="fas fa-ellipsis-v"></i> ícono de tres puntos de la esquina superior derecha.
+3. Haz clic en una de las opciones:
+    - **Editar precio**
+    - **Editar stock**
+    - **Editar contenido**
+
+Serás redirigido a la página correspondiente para realizar los cambios necesarios.
+
+![Ações offer status](//images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/b17744a4b3b202fc28490eda7ff16663/a__es-offer-status.png)
+
+### Exportar la lista de anuncios publicados
+
+Para exportar la lista de anuncios publicados en formato XLSX, haz clic sobre el ícono flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
+
+<div class="alert alert-info">
+El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
+  </div>
+
+## Pestaña Problemas
+
+En la pestaña **Problemas** el seller puede hacer un seguimiento de los anuncios enviados que no fueron aprobados por el marketplace. En esta pestaña también puedes realizar las siguientes acciones:
+
+- [Buscar y filtrar anuncios](#buscar-y-filtrar-anuncios)
+- [Ver detalles del problema](#ver-detalles-del-problema)
+- [Editar información de los anuncios](#editar-informacion-de-los-anuncios)
+- [Exportar la lista de anuncios con problemas](#exportar-la-lista-de-anuncios-con-problemas)
+
+### Buscar y filtrar anuncios con problemas
+
+En la parte superior derecha de la página hay una barra de búsqueda con un ícono de lupa <i class="fas fa-search"></i>, en la que puedes buscar un anuncio por:
+
+- Nombre del anuncio
+- ID del SKU
+
+Además, los resultados de la búsqueda pueden filtrarse según los siguientes criterios:
+
+- **Marketplace:** canal de venta al que se envió el anuncio.
+- **Enviados:** pueden consultarse tres periodos predeterminados desde que el anuncio se envió al marketplace; *Hoy***,** *Últimos 7 días* y *El mes pasado*.
+- **Stock:** cantidad de stock de un producto, que puede ser:
+    - `Mínimo:` número mínimo de ítems en stock de un producto.
+    - `Máximo:` número máximo de ítems en stock de un producto.
+
+Para filtrar los anuncios por **Marketplace**, haz clic en la flecha hacia abajo situada junto al término, marca en la casilla de selección los marketplaces deseados y, a continuación, haz clic en **Aplicar**.
+
+Para filtrar los anuncios por **Enviados**, haz clic en la flecha hacia abajo situada junto al filtro, selecciona una de las opciones y haz clic en **Aplicar.**
+
+Para filtrar los anuncios por **Stock**, haz clic en la flecha hacia abajo situada junto al filtro, ingresa el número de stock mínimo, stock máximo, o ambos, y haz clic en **Aplicar**.
+
+![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/0cc494ba4b34b71a2aaf21cfb3ed1a21/inventario-offer-status.png)
+
+Puedes utilizar un único filtro o combinarlos en una misma búsqueda. Los filtros no vienen preseleccionados de manera predeterminada, lo que significa que la página inicial mostrará la cantidad total de anuncios existentes.
+
+### Ver detalles del problema**
+
+En la pestaña **Problemas** puedes ver la lista de anuncios junto con la siguiente información presentada en columnas:
+
+| **Columna** | **Descripción** |
+|---|---|
+| **Nombre** | Muestra la imagen del SKU, el título del anuncio en el canal de ventas y el ID del SKU en VTEX. |
+| **Marketplace** | Canal de ventas al que se envió el anuncio. |
+| **Precio** | Precio del SKU del anuncio. |
+| **Stock** | Cantidad de items en  <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">stock</a> para el SKU del anuncio. |
+| **Problemas** | Número de problemas identificados en el anuncio. |
+| **Enviados** | Fecha en la que el anuncio se envió al marketplace.|
+
+Para ordenar los anuncios en orden ascendente o descendente haz clic en los nombres de las columnas.
+
+### Editar información de los anuncios
+
+Al hacer clic en un anuncio se abrirá una ventana con una barra que te informará de los errores encontrados en el anuncio, enumerados a continuación:
+
+- **Posibles errores**
+  - **Anuncio rechazado por el marketplace:** este mensaje informa que el marketplace no aceptó el anuncio debido a que no cumple con los requisitos establecidos.
+  - **Es necesario actualizar el stock:** cuando el SKU del ítem anunciado no tiene stock configurado.
+  - **Es necesario actualizar el precio:** cuando no se ha configurado el precio de un anuncio.
+
+Para actualizar cualquier información de un anuncio con problemas el seller debe realizar los siguientes pasos:
+
+1. En la pestaña **Problemas**, haz clic en el anuncio deseado.  
+2. Haz clic en el ícono <i class="fas fa-ellipsis-v"></i> de tres puntos de la esquina superior derecha.  
+3. Haz clic en una de las opciones:  
+  - **Editar precio**  
+  - **Editar stock**  
+  - **Editar contenido**  
+
+Serás redirigido a la página correspondiente para realizar los cambios necesarios.
+
+### Exportar la lista de anuncios con problemas
+
+Para exportar la lista de anuncios con problemas en formato XLSX, haz clic sobre el ícono flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
+
+<div class="alert alert-info">
+El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
+  </div>
+
+## Pestaña A la espera de finalización
+
+En la pestaña **A la espera de finalización** el seller puede realizar un seguimiento de los anuncios que están pendientes de ser analizados por el marketplace. En esta pestaña también puedes realizar las siguientes acciones:
+
+- [Buscar y filtrar anuncios](#buscar-y-filtrar)
+- [Editar información de los anuncios](#editar-informacion-de-los-anuncios)
+- [Exportar la lista de anuncios en espera de finalización](#exportar-la-lista-de-anuncios-en-espera-de-finalizacion)
+
+### Buscar y filtrar anuncios en análisis
+
+En la parte superior derecha de la página hay una barra de búsqueda con el ícono de una lupa <i class="fas fa-search"></i>, en la que puedes buscar un anuncio por:
+
+- Nombre del anuncio
+- ID del SKU
+
+Además, los resultados de la búsqueda pueden filtrarse según los siguientes criterios:
+
+- **Marketplace** canal de ventas al que se envió el anuncio.
+- **Enviados:** pueden consultarse tres periodos predeterminados desde que el anuncio se envió al marketplace: **Hoy, Últimos 7 días** y **El mes pasado**.
+
+Para filtrar los anuncios por **Marketplace**, haz clic en la flecha hacia abajo situada junto al término, marca en la casilla de selección los marketplaces deseados y, a continuación, haz clic en **Aplicar**.
+
+Para filtrar los anuncios por **Enviados**, haz clic en la flecha hacia abajo situada junto al filtro, selecciona una de las opciones y haz clic en **Aplicar.**
+
+Puedes utilizar un único filtro o combinarlos en una misma búsqueda. Los filtros no vienen preseleccionados de manera predeterminada, lo que significa que la página inicial mostrará la cantidad total de anuncios existentes.
+
+### Editar información de los anuncios
+
+En la pestaña **A la espera de finalización** puedes consultar la lista de anuncios junto con la siguiente información presentada en columnas:
+
+| **Columna** | **Descripción** |
+|---|---|
+| **Nombre** | Muestra la imagen del SKU, el título del anuncio en el canal de ventas y el ID del SKU en VTEX. |
+| **Marketplace** | Canal de ventas al que se envió el anuncio. |
+| **Enviados** | Fecha en la que el anuncio se envió al marketplace.|
+
+Para ordenar los anuncios en orden ascendente o descendente haz clic en los nombres de las columnas.
+
+Para actualizar la información de un anuncio en análisis deben seguirse los pasos a continuación:
+
+1. En la pestaña **A la espera de finalización**, haz clic en el anuncio deseado.
+2. Haz clic en el ícono <i class="fas fa-ellipsis-v"></i> de tres puntos de la esquina superior derecha.
+3. Haz clic en una de las opciones:
+    - **Editar precio**
+    - **Editar stock**
+    - **Editar contenido**
+
+Serás redirigido a la página correspondiente para realizar los cambios necesarios.
+
+### Exportar la lista de anuncios en espera de finalización
+
+Para exportar la lista de anuncios en espera de finalización en formato XLSX, haz clic sobre el ícono flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
+
+<div class="alert alert-info">
+El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
+  </div>
diff --git a/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md b/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
index 5c74cde91..4a6bf51bc 100644
--- a/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
+++ b/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
@@ -23,7 +23,7 @@ Por defecto, es necesario que, en el marketplace, haya [stock](https://help.vtex
 
 En la imagen que aparece a continuación se muestra un ejemplo en el cual el seller A envió un producto al marketplace A. Si el marketplace A tiene en stock el mismo producto que recibió del seller A, puede enviar ese ítem al marketplace B.
 
-![erro-envio-skus-sellers-marketplaces-docnovo](https://images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
+![erro-envio-skus-sellers-marketplaces-docnovo](//images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
 
 Los marketplaces que cuentan con este modelo de negocio se ven beneficiados porque pueden ofrecer su gama de productos en canales de venta de terceros y así generar más oportunidades de venta.
 
diff --git a/docs/tutorials/es/oms-page-structure.md b/docs/tutorials/es/oms-page-structure.md
index e8dfd81ba..6d3d84759 100644
--- a/docs/tutorials/es/oms-page-structure.md
+++ b/docs/tutorials/es/oms-page-structure.md
@@ -37,7 +37,7 @@ Para todos los datos de variaciones de pedidos, y también para los números de
 Importante: si la comparación de pedidos se realiza en base a 0 pedidos en el pasado, la variación es de 0%.
 </div>
 
-![barra-status-oms es](https://images.ctfassets.net/alneenqid6w5/6fv6Fd07ra6KMOwS0ecgUm/02d1b532b5fb183d420ced0ecbb6d235/barra_de_status.png)
+![barra-status-oms es](//images.ctfassets.net/alneenqid6w5/6fv6Fd07ra6KMOwS0ecgUm/02d1b532b5fb183d420ced0ecbb6d235/barra_de_status.png)
 
 ### Filtros
 
@@ -45,7 +45,7 @@ Permiten aplicar varios filtros para ver sólo la lista de pedidos deseados. El
 
 - [Cómo filtrar pedidos](/es/tutorial/como-filtrar-pedidos/)
 
-![botão-filtro-oms es](https://images.ctfassets.net/alneenqid6w5/4NsNMVbov66KmWuM4cuYaw/d041c92d257680f6904b9e51f1a49e07/filtro_esp.png)
+![botão-filtro-oms es](//images.ctfassets.net/alneenqid6w5/4NsNMVbov66KmWuM4cuYaw/d041c92d257680f6904b9e51f1a49e07/filtro_esp.png)
 
 ### Barra de búsqueda
 
@@ -53,7 +53,7 @@ Se utiliza para realizar búsquedas sobre los términos encontrados en el pedido
 
 - [Cómo buscar pedidos](/es/tutorial/como-buscar-el-pedido/)
 
-![barra-busca-oms es](https://images.ctfassets.net/alneenqid6w5/4NQi3UjfPiqsS00AgyaMAO/528adcb5032b6e613bd7eef6e6251826/barra_de_busca_esp.png)
+![barra-busca-oms es](//images.ctfassets.net/alneenqid6w5/4NQi3UjfPiqsS00AgyaMAO/528adcb5032b6e613bd7eef6e6251826/barra_de_busca_esp.png)
 
 ### Barra de información
 
@@ -63,7 +63,7 @@ También trae el ranking de ventas de la tienda en relación a todas las otras t
 
 - [Interpretando los datos de la barra de pedidos en la pantalla de Todos los Pedidos.](http://help.vtex.com/es/tutorial/interpretando-los-datos-de-la-barra-de-pedidos-del-oms)
 
-![barra-info-oms es](https://images.ctfassets.net/alneenqid6w5/5Z5H9agm9qewyOGqCg0Cim/e535b7690c3d21ff1803981fbf0feff2/barra_de_info.png)
+![barra-info-oms es](//images.ctfassets.net/alneenqid6w5/5Z5H9agm9qewyOGqCg0Cim/e535b7690c3d21ff1803981fbf0feff2/barra_de_info.png)
 
 ### Botón de exportación
 
@@ -71,7 +71,7 @@ Utilizado para exportar los pedidos que trae la búsqueda, considerando los filt
 
 - [Exportar pedidos en Gestión de pedidos. ](http://help.vtex.com/es/tutorial/exportacion-de-pedidos-en-oms)
 
-![botão-exportar-oms es](https://images.ctfassets.net/alneenqid6w5/4sL2BuR5LO4Qamsgwsagss/47a5f99522b5f16b5fe57c487fa31fd9/botao_de_exportar_es.png)
+![botão-exportar-oms es](//images.ctfassets.net/alneenqid6w5/4sL2BuR5LO4Qamsgwsagss/47a5f99522b5f16b5fe57c487fa31fd9/botao_de_exportar_es.png)
 
 ### Lista de pedidos
 
@@ -79,7 +79,7 @@ Principal área de Gestión de pedidos. Trae los últimos pedidos realizados en
 
 - [Lista de pedidos](/es/tutorial/listado-de-pedidos)
 
-![todos-pedidos-oms es](https://images.ctfassets.net/alneenqid6w5/54hTspElLOKW2m4oi46ceU/ed5cd9c6b3b7272108f2c317533bfc11/orders_list_esp.png)
+![todos-pedidos-oms es](//images.ctfassets.net/alneenqid6w5/54hTspElLOKW2m4oi46ceU/ed5cd9c6b3b7272108f2c317533bfc11/orders_list_esp.png)
 
 ### VTEX DO
 
@@ -87,7 +87,7 @@ Reúne tareas pendientes para la tienda, generadas por los diferentes módulos d
 
 -[ Cómo funciona el listado de tareas del VTEX DO.](http://help.vtex.com/es/tutorial/vtex-do)
 
-![vtex-do-exemplo-oms es](https://images.ctfassets.net/alneenqid6w5/73Jca1gQ00a8e0gE8iAwCE/1380b478cd1836eac15289825de2b8e9/vtex_do_es.png)
+![vtex-do-exemplo-oms es](//images.ctfassets.net/alneenqid6w5/73Jca1gQ00a8e0gE8iAwCE/1380b478cd1836eac15289825de2b8e9/vtex_do_es.png)
 
 ## Suscripciones
 
@@ -105,5 +105,5 @@ La segunda pestaña, **Afiliados**, está destinada para configuraciones de afil
 
 - [Configurar afiliado.](http://help.vtex.com/es/tutorial/como-configurar-afiliado/)
 
-![configurações-oms es](https://images.ctfassets.net/alneenqid6w5/1j5ORpKc6MEa4GSIGcC2q4/75e49a2d0e6572047f10acc1c82f3900/configuracion_esp_OMS.png)
+![configurações-oms es](//images.ctfassets.net/alneenqid6w5/1j5ORpKc6MEa4GSIGcC2q4/75e49a2d0e6572047f10acc1c82f3900/configuracion_esp_OMS.png)
 
diff --git a/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
index 48cc5d7ed..a52b356b1 100644
--- a/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
@@ -1,10 +1,10 @@
 ---
 title: 'Abrir tikets para el soporte financiero de VTEX'
 id: 1ad3TguXzCSKq4yuYSK80c
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-04-04T13:58:56.872Z
-updatedAt: 2020-11-27T19:40:27.285Z
-publishedAt: 2020-03-09T18:09:31.386Z
+updatedAt: 2024-07-29T22:02:21.897Z
+publishedAt: 2024-07-29T22:02:21.897Z
 firstPublishedAt: 2018-04-04T19:53:34.588Z
 contentType: tutorial
 productTeam: Billing
@@ -35,16 +35,17 @@ Una vez que se haya autenticado por el método elegido, usted accederá al panel
 
 Para abrir un ticket, simplemente haga clic en el botón __Enviar una solicitud__.
 
-![chamado financeiro1 ES](https://images.ctfassets.net/alneenqid6w5/5yMKtmj6Hm4IiIuwmW0yiw/ae68f5d5b54c92aa65e57774501e6c26/chamado_financeiro1_ES.png)
+![chamado financeiro1 ES](//images.ctfassets.net/alneenqid6w5/5yMKtmj6Hm4IiIuwmW0yiw/ae68f5d5b54c92aa65e57774501e6c26/chamado_financeiro1_ES.png)
 
 Usted será llevado al formulario de envío de ticket, donde debe llenar:
 - Su nombre.
 - La cuenta VTEX a la que se refiere el ticket (el formulario carga una lista con las cuentas a las que tiene acceso. Si no tiene acceso a ninguna cuenta de VTEX, no puede abrir tickets).
+- El número de registro de su negocio (por ejemplo: CUIT en Argentina).
 - Que tu pregunta es financiera.
 - El tema.
 - La descripción de la pregunta o del problema.
 
-![chamado financeiro2 ES](https://images.ctfassets.net/alneenqid6w5/yV71aHHNYskkeWUWA8UIO/9be3291fa9596dd9ab9479093798a8d6/chamado_financeiro2_ES.png)
+![chamado financeiro2 ES](//images.ctfassets.net/alneenqid6w5/yV71aHHNYskkeWUWA8UIO/9be3291fa9596dd9ab9479093798a8d6/chamado_financeiro2_ES.png)
 
 Usted también puede incluir adjuntos, como capturas de pantallas o gifs animados que ayuden a describir el contexto de su solicitud.
 
@@ -84,7 +85,7 @@ Al hacer clic en __Mis solicitudes__, usted verá el historial de tickets abiert
 
 Si hace clic en __Todas las solicitudes__, puede ver el historial de tickets abiertos por cualquier empleado de su tienda.
 
-![chamado financeiro3 ES](https://images.ctfassets.net/alneenqid6w5/319yZLbjOgCeKiUU6kEakE/93c02c46b8b85358eb2942243f8f3ba1/chamado_financeiro3_ES.png)
+![chamado financeiro3 ES](//images.ctfassets.net/alneenqid6w5/319yZLbjOgCeKiUU6kEakE/93c02c46b8b85358eb2942243f8f3ba1/chamado_financeiro3_ES.png)
 
 ## Los status de los tickets
 
@@ -99,4 +100,4 @@ Después, el ticket pasa por los status `Esperando respuesta`, `Resuelto` y `Cer
 
 En su panel de soporte, usted puede filtrar la búsqueda de tickets por status. Para ello, simplemente utilice la casilla de verificación debajo del botón de envío de solicitud.
 
-![chamado financeiro4 ES](https://images.ctfassets.net/alneenqid6w5/2gyz4xXSessueWkkoUwwQG/fa8bbe2215456264f86e80735a38ac50/chamado_financeiro4_ES.png)
+![chamado financeiro4 ES](//images.ctfassets.net/alneenqid6w5/2gyz4xXSessueWkkoUwwQG/fa8bbe2215456264f86e80735a38ac50/chamado_financeiro4_ES.png)
diff --git a/docs/tutorials/es/opening-tickets-to-vtex-support.md b/docs/tutorials/es/opening-tickets-to-vtex-support.md
index f777bccf8..0270c29e7 100644
--- a/docs/tutorials/es/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/es/opening-tickets-to-vtex-support.md
@@ -1,10 +1,10 @@
 ---
 title: 'Abrir tickets para el soporte VTEX'
 id: 16yOEqpO32UQYygSmMSSAM
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-11-21T22:18:13.507Z
-updatedAt: 2022-12-16T19:09:29.363Z
-publishedAt: 2022-05-31T21:10:30.601Z
+updatedAt: 2023-12-01T18:51:22.803Z
+publishedAt: 2023-12-01T18:51:22.803Z
 firstPublishedAt: 2017-11-22T02:37:19.330Z
 contentType: tutorial
 productTeam: Others
@@ -65,7 +65,7 @@ Al seleccionar esta opción de soporte, deberás rellenar la información que se
    * *Tengo una duda y quisiera hacer una pregunta*
    * *Quisiera solicitar una configuración*
 2. En el campo **Asunto de la solicitud**, rellena con la información relacionada con el tipo de problema para el que necesitas ayuda. En base a la descripción de tu problema, te indicaremos algunos artículos del [Centro de Ayuda](https://help.vtex.com/es/) que podrían serte útiles para solucionar tu problema. Si crees que ninguno de los artículos puede ayudarte a resolver el problema, avanza al paso siguiente.
-![https help.vtex.com es support](https://images.ctfassets.net/alneenqid6w5/6th3vu5w61nnzp8NE1Xiza/e1e53143d8559adad86d03e8550ba258/https___help.vtex.com_es_support.gif)
+![https help.vtex.com es support](//images.ctfassets.net/alneenqid6w5/6th3vu5w61nnzp8NE1Xiza/e1e53143d8559adad86d03e8550ba258/https___help.vtex.com_es_support.gif)
 3. Haz clic en el botón `Seguir`.
 Serás direccionado a otra página.
 4. .En el campo **Impacto del problema**, selecciona la opción que mejor se adapte al impacto del problema:
diff --git a/docs/tutorials/es/operational-capacity-beta.md b/docs/tutorials/es/operational-capacity-beta.md
new file mode 100644
index 000000000..33910c4c2
--- /dev/null
+++ b/docs/tutorials/es/operational-capacity-beta.md
@@ -0,0 +1,198 @@
+---
+title: 'Capacidad operativa (Beta)'
+id: 2thSYLMAS8KAd8V4XuBLSy
+status: PUBLISHED
+createdAt: 2023-05-08T18:03:07.644Z
+updatedAt: 2024-04-08T18:59:56.706Z
+publishedAt: 2024-04-08T18:59:56.706Z
+firstPublishedAt: 2023-05-09T17:22:57.861Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: capacidad-operacional-beta
+locale: es
+legacySlug: modulo-localidades
+subcategory: 13sVE3TApOK1C8jMVLTJRh
+---
+
+<div class = "alert alert-info">
+Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar la <b>Capacidad operativa (Beta)</b>, completa el <a href="https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform">formulario de contacto</a>. El requisito para usar la funcionalidad es tener <a href="https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a> asociadas a la <a href="https://help.vtex.com/es/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-cuenta-vtex">cuenta principal</a>.
+</div>
+
+La página **Capacidad operativa** permite gestionar la capacidad de los sellers para recibir y preparar pedidos de la tienda, lo que te permite optimizar tu red logística. Puedes monitorear la distribución de pedidos entre los sellers y realizar [acciones](https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#acciones-en-la-pagina-de-detalles-del-seller) para mejorarla.
+
+Una buena gestión de la capacidad operativa de los sellers tiene los siguientes beneficios:
+
+- Mejor redistribución de la demanda de productos entre los stocks de diferentes sellers.
+- Optimización del plazo de envío de pedidos evitando sobrecargar sellers.
+- Mejor experiencia de compra para los clientes, ya que reciben sus pedidos en el plazo prometido.
+
+Al acceder a **Envío > Capacidad operativa** en el Admin VTEX, verás una página según se ilustra a continuación:
+
+![operational_capacity_image1_ES](//images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/defaa51c729689fdd70aa1e00e018d40/operational_capacity_image1_ES.png)
+
+<div class="alert alert-warning">
+Los sellers que aparecen en la interfaz son los sellers de tu operación, configurados previamente por nuestro equipo. Para agregar un nuevo seller, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro soporte</a>.
+</div>
+
+El gráfico muestra los siguientes datos:
+
+- **Total de sellers:** número total de sellers de tu operación.
+- **Activos:** número de sellers recibiendo nuevos pedidos.
+- **Pausados:** número de sellers pausados, es decir, que no están recibiendo nuevos pedidos.
+- **Número de sellers que excedieron la capacidad:** número de sellers que recibieron más pedidos de lo que su límite configurado permite. Puedes seleccionar los resultados de los últimos `7 días` o `28 días`.
+
+La página **Capacidad operativa** contiene la siguiente información:
+
+| **Columna** | **Descripción** |
+| :----------: | :---------- |
+| Nombre | Identificación del <a href="https://help.vtex.com/es/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w">seller</a> referido en la capacidad operativa. |
+| Capacidad de operación | <p>Porcentaje de capacidad operativa utilizada en el día.</p><p><b>Ejemplo:</b> un seller con capacidad para preparar 100 pedidos tiene un 80 % de su capacidad operativa del día utilizada. Esto significa que solo puede recibir 20 pedidos nuevos ese día.</p><p>En esta columna, se muestra un ícono de alerta cuando el seller alcanza el 100 % de su capacidad y no puede recibir nuevos pedidos ese día.</p><p>Puedes <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#editar-la-capacidad-operativa-del-seller">editar la capacidad operativa de los sellers</a> individualmente o en masa, según se describe en Editar capacidad operativa del seller.</p> |
+| Status | <p>Status de la capacidad operativa del seller, que pueden ser dos:</p><p><ul><li><i class="fas fa-toggle-on" aria-hidden="true"></i> <b>Activo:</b> el botón de alternancia está activado y el seller puede recibir nuevos pedidos.</li><li><i class="fas fa-toggle-off" aria-hidden="true"></i><b>Pausado:</b> el botón de alternancia está desactivado y el seller no puede recibir nuevos pedidos.</li></ul></p><p>Para decidir cuándo pausar un seller, consulta la sección <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#pausar-o-aumentar-la-capacidad-operativa">Pausar o aumentar la capacidad operativa</a>.</p> |
+
+Al hacer clic en un seller, se te redirige a la [página de detalles del seller](#acciones-en-la-pagina-de-detalles-del-seller), que describiremos más adelante.
+
+## Acciones en Capacidad operativa
+
+En la página **Envío > Capacidad operativa** del Admin VTEX, puedes realizar las siguientes acciones:
+
+- [Buscar seller](#buscar-seller)
+- [Filtrar sellers](#filtrar-sellers)
+- [Activar y pausar capacidad operativa de sellers](#activar-y-pausar-la-capacidad-operativa-de-sellers)
+- [Editar unidad de capacidad operativa del seller](#editar-unidad-de-capacidad-operativa-del-seller)
+
+### Buscar seller
+
+En la barra de búsqueda puedes escribir el nombre de un seller para encontrarlo.
+
+<div class = "alert alert-info">
+Puedes asociar la búsqueda de sellers con el <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtrar-sellers">filtro de status</a>. Si no se devuelve ningún resultado, comprueba que no haya ningún filtro activo.
+</div>
+
+### Filtrar sellers
+
+Puedes filtrar los sellers de la lista por status haciendo clic en `Status` y seleccionando `Activos` o `En pausa`. Luego, haz clic en `Aplicar`.
+
+Para limpiar los filtros aplicados, haz clic en **Status > Limpiar**.
+
+### Activar y pausar la capacidad operativa de sellers
+
+Un seller tiene status <i class="fas fa-toggle-on" aria-hidden="true"></i> `Activo` si el botón de alternancia está activado y <i class="fas fa-toggle-off" aria-hidden="true"></i> `Pausado` si está desactivado. Para cambiar el status de la capacidad operativa de un solo seller, haz clic en el botón de alternancia de la línea correspondiente al seller y confirma la acción haciendo clic en `Pausar`/`Activar`. 
+
+Para activar o pausar la capacidad operativa de varios sellers, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Envío > Capacidad operativa**, o escribe **Capacidad operativa** en la barra de búsqueda en la parte superior de la página.
+2. Selecciona los sellers deseados marcando las casillas de selección al lado del nombre. Puedes seleccionar todos los sellers marcando cualquier casilla de selección y luego haciendo clic en `Seleccionar todo`.
+3. Haz clic en `Más acciones`.
+4. Luego, haz clic en `Activar` o `Pausar`, según corresponda.
+5. Confirma la acción haciendo clic en `Activar` o `Pausar`, según corresponda.
+
+### Editar unidad de capacidad operativa del seller
+
+La capacidad operativa del seller puede medirse por número de pedidos o ítems de pedidos. Para editar la capacidad operativa de uno o varios sellers, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Envío > Capacidad operativa**, o escribe **Capacidad operativa** en la barra de búsqueda en la parte superior de la página.
+2. Selecciona los sellers deseados marcando las casillas de selección al lado del nombre. Puedes seleccionar todos los sellers marcando cualquier casilla de selección y luego haciendo clic en `Seleccionar todo`.
+3. Haz clic en `Editar capacidad`.
+4. Escoge la **Unidad de capacidad operativa**:
+    - **Cantidad de pedidos:** la capacidad operativa del seller se medirá por número de pedidos.
+    - **Cantidad de ítems:** la capacidad del seller se medirá por número de ítems del pedido.
+5. Haz clic en `Guardar cambios`.
+
+<div class="alert alert-warning">
+La plataforma tiene algunas restricciones con respecto a <a href="https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers de extensa cobertura</a>. La sección <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidad-operativa-de-sellers-de-extensa-cobertura">Capacidad operativa de sellers de extensa cobertura</a> contiene más información.
+</div>
+
+## Acciones en la página de detalles del seller
+
+En la página **Envío > Capacidad operativa** del Admin VTEX, si haces clic en un seller, se te redirige a la página de detalles del seller donde puedes realizar las siguientes acciones:
+
+- [Pausar y activar la capacidad operativa del seller](#pausar-y-activar-la-capacidad-operativa-del-seller)
+- [Monitorear la capacidad utilizada](#monitorear-la-capacidad-utilizada)
+- [Editar la dirección del seller](#editar-la-direccion-del-seller)
+- [Editar la capacidad operativa del seller](#editar-la-capacidad-operativa-del-seller)
+
+### Pausar y activar la capacidad operativa del seller
+
+En la esquina superior derecha de la página de detalles del seller, hay un botón de alternancia para activar o desactivar la capacidad operativa:
+
+- **Activar:** habilita el botón de alternancia para que el status esté `Activo` y haz clic en `Activar`.
+- **Desactivar:** inhabilita el botón de alternancia para que el status esté `Pausado` y haz clic en `Pausar`.
+
+<div class="alert alert-warning">
+La plataforma tiene algunas restricciones en relación con <a href="https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers de extensa cobertura</a>. La sección <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidad-operativa-de-sellers-de-extensa-cobertura">Capacidad operativa de sellers de extensa cobertura</a> contiene más información.
+</div>
+
+### Monitorear la capacidad utilizada
+
+El gráfico **Status de la capacidad operativa** muestra en tiempo real el porcentaje utilizado de la capacidad del seller, como se ilustra a continuación:
+
+![operational_capacity_image2_ES](//images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/1c6046c4c098cca52060888b61f53fa9/operational_capacity_image2_ES.png)
+
+El gráfico muestra los siguientes periodos:
+
+- Hoy
+- Mañana
+- Datos de los próximos dos días
+
+Si configuras el seller para que utilice la [regla](#iii-regla) _Continuar recibiendo pedidos consumiendo la capacidad de los siguientes días_, el gráfico mostrará el porcentaje de la capacidad operativa de los siguientes días que ya fue consumida por los pedidos de los días anteriores. Puedes consultar más información en [Editar la capacidad operativa del seller](#editar-la-capacidad-operativa-del-seller).
+
+### Editar la dirección del seller
+
+Para editar la dirección o el nombre de identificación del seller en **Capacidad operativa**, sigue los pasos a continuación:
+
+1. En la sección **Información básica**, haz clic en `Editar información básica`.
+2. Modifica la información deseada.
+3. Haz clic en `Guardar cambios`.
+
+### Editar la capacidad operativa del seller
+
+En la sección **Capacidad operativa**, puedes ver la configuración actual de la capacidad operativa del seller para cada día de la semana, como se muestra a continuación:
+
+![operational_capacity_image3_ES](//images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/d4019f9c94ab752050d6387e48b88a5c/operational_capacity_image3_ES.png)
+
+Para modificar la configuración, sigue estos pasos:
+
+1. En la sección **Capacidad operativa**, haz clic en `Editar`.
+2. Cambia las opciones deseadas, que pueden ser:
+    - [I - Unidad de capacidad operativa](#i-unidad-de-capacidad-operativa)
+    - [II - Capacidad](#ii-capacidad)
+    - [III - Regla](#iii-regla)
+3. Haz clic en `Guardar cambios`.
+
+A continuación, se detallan las descripciones de los campos mencionados en los pasos anteriores.
+
+#### I - Unidad de capacidad operativa
+
+Define si la capacidad operativa se medirá por el número de _pedidos_ o de _ítems_. El número de ítems considera los ítems de todos los pedidos realizados en un día.
+
+#### II - Capacidad
+
+Establece el límite de la capacidad operativa del seller para cada día de la semana. El sistema no tiene un límite máximo establecido.
+
+Cuando se alcanza el límite configurado, tu tienda sigue recibiendo nuevos pedidos, que pueden distribuirse entre otros sellers o asignarse al mismo seller, pero consumiendo la capacidad de los próximos días dependiendo de la regla que selecciones. 
+
+#### III - Regla
+
+Selecciona la regla que se aplicará cuando el seller alcance la capacidad máxima del día:
+
+- **Continuar recibiendo pedidos consumiendo la capacidad de los siguientes días:** el seller sigue recibiendo nuevos pedidos después de alcanzar la capacidad. Dichos pedidos se asignan a la capacidad de los próximos días y se ajusta la promesa de envío a los clientes en el checkout. Este periodo no se puede configurar en horas, ya que se ajustará automáticamente al número de días siguientes al que fue asignado.
+  - Si seleccionas esta regla, debes establecer el número de días siguientes para asignar los pedidos que excedan la capacidad del día actual.
+  > **Ejemplo:** un seller vende chocolates y su capacidad del día actual ya alcanzó el 100 %. El seller continúa recibiendo pedidos, pero los preparará mañana porque su equipo no tiene la capacidad de preparar más pedidos de los que ya están programados para hoy. En el checkout, la promesa de envío de nuevos pedidos incluirá un día adicional en el plazo, ya que se prepararán mañana. Si la capacidad de mañana se consume completamente hoy, los nuevos pedidos se asignarán a pasado mañana y se prepararán dos días después porque la tienda configuró tres días en Continuar recibiendo pedidos consumiendo la capacidad de los siguientes días.
+- **Pausar este seller hasta el final del día:** si el seller alcanza el límite de su capacidad diaria, ya no podrá recibir más pedidos ese día y los nuevos pedidos se asignan a otros sellers.
+
+## Pausar o aumentar la capacidad operativa
+
+Para decidir si la mejor estrategia para tu negocio es [editar la capacidad operativa](#editar-la-capacidad-operativa-del-seller) de un seller o [pausarlo](#activar-y-pausar-la-capacidad-operativa-de-sellers), es importante entender lo siguiente:
+
+- **Seller pausado:** el seller deja de recibir nuevos pedidos hasta que lo reactives. Aun si se configura la regla _Continuar recibiendo pedidos consumiendo la capacidad de los siguientes días_, no aceptará nuevos pedidos.
+  > **Ejemplo:** la tienda del seller tuvo problemas en las instalaciones y se comprometió la preparación de nuevos pedidos. En este caso, pausar el seller y activarlo después de que pueda preparar pedidos nuevamente es una decisión estratégica.
+- **Seller alcanzó el límite máximo:** el seller deja de recibir pedidos ese día al alcanzar el 100 % de su capacidad. La capacidad operativa del seller se liberará al día siguiente y recibirá pedidos automáticamente.
+  > **Ejemplo:** el día de Nochebuena, el seller alcanzó el máximo de su capacidad y no puede preparar más pedidos. No valdría la pena [aumentar la capacidad operativa del seller](#editar-la-capacidad-operativa-del-seller). Al día siguiente el seller podrá preparar nuevos pedidos. Por lo tanto, sería preferible no editar el seller, ya que su capacidad se liberará al día siguiente y recibirá nuevos pedidos.
+
+### Capacidad operativa de sellers de extensa cobertura
+
+Cuando el cliente informa su ubicación en el sitio web de la tienda, se muestran los productos de tu tienda (seller 1) y de los [sellers de extensa cobertura](https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI). 
+
+Debido a una limitación de la plataforma, cuando desactivas la capacidad operativa de un seller de extensa cobertura, sus productos siguen apareciendo como disponibles en la vitrina, aunque el cliente no puede comprarlos. Por esta razón, recomendamos mantener siempre activa la capacidad operativa de sellers de extensa cobertura.
+
diff --git a/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
index 813cac91f..78b3caddf 100644
--- a/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
@@ -53,7 +53,7 @@ Para deshabilitar la función __Opciones de entrega optimizadas__, siga los paso
 3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Checkout__.
 4. En __Opciones de entrega optimizadas__, haga clic en el botón <i class="fas fa-toggle-off"></i> para deshabilitar la opción de visualización de las __Opciones de entrega optimizadas__.
 
-![Opciones de entrega optimizadas](https://images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/94ea6b1f59944005c687713e08d86962/Opciones_de_entrega_optimizadas.PNG)
+![Opciones de entrega optimizadas](//images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/94ea6b1f59944005c687713e08d86962/Opciones_de_entrega_optimizadas.PNG)
 
 <ul>
   5. Haga clic en <b>Guardar</b>.
diff --git a/docs/tutorials/es/order-allocation-algorithm-beta.md b/docs/tutorials/es/order-allocation-algorithm-beta.md
index b3ced287a..e0c9fa4e5 100644
--- a/docs/tutorials/es/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/es/order-allocation-algorithm-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Order Allocation Algorithm (Beta)'
 id: 1zLCAyEdnVe3EsE9Kz88xA
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-07-12T23:39:25.008Z
-updatedAt: 2023-03-21T17:27:34.101Z
-publishedAt: 2023-03-21T17:27:34.101Z
+updatedAt: 2023-08-14T17:29:11.705Z
+publishedAt: 
 firstPublishedAt: 2022-07-12T23:51:23.186Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/order-cancellation-requested-by-the-customer.md b/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
index 7776f8705..694778537 100644
--- a/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
@@ -3,8 +3,8 @@ title: 'Cancelación del pedido solicitada por el cliente'
 id: 3wEI6DUNtecooG2Ki4Akqo
 status: PUBLISHED
 createdAt: 2019-01-24T21:42:57.276Z
-updatedAt: 2023-04-28T00:40:54.949Z
-publishedAt: 2023-04-28T00:40:54.949Z
+updatedAt: 2024-04-01T15:51:58.098Z
+publishedAt: 2024-04-01T15:51:58.098Z
 firstPublishedAt: 2019-01-24T21:42:57.707Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,6 +21,10 @@ Hay situaciones en las que los clientes pueden solicitar la cancelación de un p
 Después que se cancela el pedido, no se le puede cambiar el status.
 </div>
 
+<div class = "alert alert-warning">
+No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
+</div>
+
 ## Cancelación en la ventana de cancelación
 
 Cuando el cliente solicita la cancelación durante la [ventana de cancelación](https://help.vtex.com/es/tutorial/configurar-el-tiempo-de-espera-para-cancelar-el-pedido--jYFdnPDtNm4WCEkYWqqC), el pedido se cancela automáticamente sin necesidad de autorización de la tienda. Hasta ese momento, según el [flujo del pedido](https://help.vtex.com/es/tutorial/flujo-de-pedido-en-el-oms--tutorials_196), el administrador de la tienda aún no ha realizado ninguna acción sobre ese pedido.
diff --git a/docs/tutorials/es/order-details-page.md b/docs/tutorials/es/order-details-page.md
index 7478d45ae..0a03fd9ae 100644
--- a/docs/tutorials/es/order-details-page.md
+++ b/docs/tutorials/es/order-details-page.md
@@ -3,8 +3,8 @@ title: 'Página de detalles del pedido'
 id: 2Y75n54Cc9VizrlG1N6ZNl
 status: PUBLISHED
 createdAt: 2020-12-28T15:51:29.428Z
-updatedAt: 2023-03-23T19:27:38.026Z
-publishedAt: 2023-03-23T19:27:38.026Z
+updatedAt: 2023-12-21T14:06:02.509Z
+publishedAt: 2023-12-21T14:06:02.509Z
 firstPublishedAt: 2020-12-28T19:33:51.059Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,20 @@ legacySlug: pagina-de-detalles-del-pedido-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
+<div class = "alert alert-info">
+Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
+</div>
+
 La página **Detalles del pedido** permite ver toda la información sobre un pedido y gestionarlo en un solo lugar. Para ver la página, haz clic en **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-los-pedidos--2QTduKHAJMFIZ3BAsi6Pi)** y selecciona un pedido de la lista.
 
-En esta página puedes:
+Puedes también buscar pedidos desde cualquier página del Admin VTEX utilizando la barra de búsqueda global en la parte superior de la página. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
+En la página de detalles del pedido, puedes:
 
 * Consultar en qué etapa del flujo de pedidos se encuentra el pedido (status del pedido).
 * Acceder a todo el historial de cambios del pedido.
@@ -39,7 +50,7 @@ A continuación, se detallan todas las secciones posibles de la página <b>Detal
 
 ## Barra superior
 
-![BarrasuperiorES](https://images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/a5a4369cfa3231a289e6e40e606b53b8/BarrasuperiorES.jpg)
+![BarrasuperiorES](//images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/a5a4369cfa3231a289e6e40e606b53b8/BarrasuperiorES.jpg)
 
 La barra superior de la página contiene la siguiente información y acciones:
 
@@ -53,7 +64,7 @@ La barra superior de la página contiene la siguiente información y acciones:
 
 ## Información general 
 
-![Informacao geraisES](https://images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/08c3f4586217f281477c87b60ac10520/Informacao_geraisES.jpg)
+![Informacao geraisES](//images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/08c3f4586217f281477c87b60ac10520/Informacao_geraisES.jpg)
 
 La información general del pedido se muestra en la parte superior de la página, debajo de la barra superior, e incluye:
 
@@ -75,7 +86,7 @@ Este bloque muestra el status actual del pedido en el [flujo de pedidos](https:/
 
 ### Ítems a facturar
 
-![Itens faturarES](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
+![Itens faturarES](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
 
 El bloque **Ítems a facturar** contiene paquetes con ítems cuyo pago ha sido aprobado pero que aún no han sido [facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), es decir, sus facturas no se no se emitieron a la plataforma.
 
@@ -88,7 +99,7 @@ En la esquina superior izquierda aparecen las siguientes acciones:
 
 ### Facturas
 
-![FaturaES](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
+![FaturaES](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
 
 Este bloque muestra los ítems facturados con sus respectivas facturas y los paquetes que componen las entregas. En este bloque tú puedes:
 
@@ -99,7 +110,7 @@ Este bloque muestra los ítems facturados con sus respectivas facturas y los paq
 
 ### Ítems devueltos
 
-![Itens devolvidosES](https://images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/2c0eeac373646a73f4f79686d5f8d55f/Itens_devolvidosES__1_.png)
+![Itens devolvidosES](//images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/2c0eeac373646a73f4f79686d5f8d55f/Itens_devolvidosES__1_.png)
 
 El bloque de **Ítems devueltos** se muestra cuando se devuelven ítems del pedido. Mira qué información y acciones están disponibles en este bloque:
 
@@ -113,7 +124,7 @@ El bloque de **Ítems devueltos** se muestra cuando se devuelven ítems del pedi
 
 ### Historial de ítems modificados
 
-![Historico Itens alteradosES](https://images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/52ab970237d69819a43c8c40621dd712/Historico_Itens_alteradosES.png)
+![Historico Itens alteradosES](//images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/52ab970237d69819a43c8c40621dd712/Historico_Itens_alteradosES.png)
 
 Este bloque está disponible cuando hay un cambio de ítems en el pedido. El **Historial de ítems modificados** contiene los detalles del cambio: qué ítems se añadieron o eliminaron, la fecha en que se produjo el cambio y los valores de los productos (el precio del ítem devuelto, el precio del ítem agregado y la diferencia entre los dos).
 
@@ -121,7 +132,7 @@ Si hay cambios en el valor final del pedido, la diferencia de valor se mostrará
 
 ## Historial del pedido
 
-![Historico pedidoES](https://images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/0e9e5ab253e4b902fa99438c725deb56/Historico_pedidoES.jpg)
+![Historico pedidoES](//images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/0e9e5ab253e4b902fa99438c725deb56/Historico_pedidoES.jpg)
 
 Este bloque muestra las interaciones dentro del pedido, con sus respectivas fechas y horas. 
 
@@ -135,7 +146,7 @@ También puedes ver los detalles de las notificaciones enviadas por email al cli
 
 ## Comentarios
 
-![ComentariosES](https://images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/e8b25905f968644d3346d14109b528d0/ComentariosES.png)
+![ComentariosES](//images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/e8b25905f968644d3346d14109b528d0/ComentariosES.png)
 
 Esta sección te permite añadir comentarios internos con observaciones sobre el pedido. Para ello, escribe en la caja de texto y haz clic en `Enviar`.
 
@@ -143,7 +154,7 @@ Los comentarios enviados se registran en la página de detalles del pedido con l
 
 ## Detalles financieros
 
-![LateralES](https://images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/cb09b4e443df18a1f4af4971718e568a/LateralES.png)
+![LateralES](//images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/cb09b4e443df18a1f4af4971718e568a/LateralES.png)
 
 En la parte derecha de la página, puedes consultar los detalles financieros del pedido. Esta información se actualiza automáticamente a medida que avanza el pedido. 
 
diff --git a/docs/tutorials/es/order-errors-in-the-mercado-livre-integration.md b/docs/tutorials/es/order-errors-in-the-mercado-livre-integration.md
index 89e59831b..ce3453352 100644
--- a/docs/tutorials/es/order-errors-in-the-mercado-livre-integration.md
+++ b/docs/tutorials/es/order-errors-in-the-mercado-livre-integration.md
@@ -3,8 +3,8 @@ title: 'Errores de integración de pedidos de Mercado Libre'
 id: 4w4jAIWUy3OELgu3HFmGgh
 status: PUBLISHED
 createdAt: 2021-08-30T18:04:27.780Z
-updatedAt: 2023-03-29T23:44:08.721Z
-publishedAt: 2023-03-29T23:44:08.721Z
+updatedAt: 2023-08-04T18:43:32.189Z
+publishedAt: 2023-08-04T18:43:32.189Z
 firstPublishedAt: 2021-08-30T18:37:05.901Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/order-flow-and-status.md b/docs/tutorials/es/order-flow-and-status.md
index abfcfd366..0da50e538 100644
--- a/docs/tutorials/es/order-flow-and-status.md
+++ b/docs/tutorials/es/order-flow-and-status.md
@@ -3,8 +3,8 @@ title: 'Flujo y status de pedidos'
 id: tutorials_196
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:33.518Z
-updatedAt: 2023-02-28T16:04:19.511Z
-publishedAt: 2023-02-28T16:04:19.511Z
+updatedAt: 2024-04-01T15:37:30.788Z
+publishedAt: 2024-04-01T15:37:30.788Z
 firstPublishedAt: 2017-04-27T23:02:47.616Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -40,7 +40,7 @@ Para los casos de pedidos incompletos, consulta el artículo <a href="https://he
 
 ### Flujo de marketplace
 
-![pedido_marketplace_es](https://images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/390a09b29e0385c23be5ce5228e8b9f4/pedido_marketplace_es.png)
+![pedido_marketplace_es](//images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/390a09b29e0385c23be5ce5228e8b9f4/pedido_marketplace_es.png)
 
 El flujo del _marketplace_ está integrado con el flujo del _seller_. Cuando se finaliza un pedido que será enviado por un _seller_ externo (que no es el _seller_ principal), el flujo visto por el _marketplace_ es el siguiente: 
 
@@ -57,7 +57,7 @@ Para saber cómo identificar pedidos que provienen de _marketplaces_, consulta e
 
 ### Flujo de seller
 
-![pedido_fluxo_seller_es](https://images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/51c2f48ff1629813b469311d8c867ec9/pedido_fluxo_seller_es.png)
+![pedido_fluxo_seller_es](//images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/51c2f48ff1629813b469311d8c867ec9/pedido_fluxo_seller_es.png)
 
 Este es el flujo del pedido visto por la tienda responsable de enviar los productos que componen el pedido. El pedido se realiza a través de otra tienda (o _marketplace_) y el flujo del _seller_ se inicia después de la confirmación del pedido.
 
@@ -96,7 +96,7 @@ Ten en cuenta que:
 
 ### Flujo completo
 
-![pedido_fluxo_completo_es_2](https://images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/ccb76d6a281ae006d08b4d060866073a/pedido_fluxo_completo_es.png)
+![pedido_fluxo_completo_es_2](//images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/ccb76d6a281ae006d08b4d060866073a/pedido_fluxo_completo_es.png)
 
 El flujo completo del pedido es visto por la tienda que realiza la venta y el envío del pedido. El flujo completo está compuesto por el flujo del _marketplace_ y el flujo del _seller_ de forma secuencial.
 
@@ -126,7 +126,9 @@ La cancelación de un pedido se inicia en varios escenarios. Para cada tipo de c
 - **[Solicitud de cancelación por parte del cliente](https://help.vtex.com/es/tutorial/como-funciona-o-cancelamento-de-pedido-por-parte-do-cliente--3wEI6DUNtecooG2Ki4Akqo):** el cliente realiza la cancelación durante el periodo de cancelación o solicita la cancelación a la tienda. Cuando la cancelación ocurre dentro del periodo de cancelación, los ítems del pedido no se reservan. Pero, si la cancelación se produce después de la preparación del pedido (después del status `Iniciar preparación`), los ítems han sido reservados.
 - **[Cancelación por parte de la tienda](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/4ts2ItvjYo8wm5gg76miS3):** el _seller_ o _marketplace_ renunció a la venta y canceló el pedido.
 
-Cuando se solicita la cancelación de un pedido, la plataforma procesa automáticamente la cancelación del pedido. El reembolso del pago al cliente depende de la etapa en la que se encuentre el pago y del medio de pago utilizado. 
+Cuando se solicita la cancelación de un pedido, la plataforma procesa automáticamente la cancelación del pedido. El reembolso del pago al cliente depende de la etapa en la que se encuentre el pago y del medio de pago utilizado.
+
+No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 <div class = "alert alert-info">
 Ve más información sobre la cancelación y el reembolso en los artículos <a href="https://help.vtex.com/pt/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente">¿Por qué se cobró en la factura del cliente mi pedido cancelado?</a> y <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento">Reembolso o cancelación</a>.
@@ -142,7 +144,7 @@ Para saber más sobre la cancelación de pedidos, consulta el artículo [¿Por q
 
 ### Flujo de cadena
 
-![pedido_fluxo_chain_es](https://images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/86fb6d87fbe872f1f81aa5219a7f92d6/pedido_fluxo_chain_es.png)
+![pedido_fluxo_chain_es](//images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/86fb6d87fbe872f1f81aa5219a7f92d6/pedido_fluxo_chain_es.png)
 
 El flujo de pedidos visto por la tienda intermediaria en una venta [Multinivel Omnichannel Inventory](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) es similar al flujo de pedidos del _marketplace_, excepto al recibir el pago de los pedidos. En la etapa de `Pago pendiente`, en lugar de la cadena recibir el pago directamente del _gateway_, el _marketplace_ informa a la cadena que recibió la confirmación del pago. 
 
@@ -294,7 +296,7 @@ Ten en cuenta que los status del flujo de pedido completo (flujo visto por las t
     <td class="tg-zr06"><span style="font-weight:400">Autorizar fulfillment</span></td>
     <td class="tg-zr06"><span style="font-weight:400">authorize-fulfillment</span></td>
     <td class="tg-1547"><span style="font-style:italic">Seller</span><span style="font-weight:400">, flujo completo</span></td>
-    <td class="tg-zr06"><span style="font-weight:400">Proceso interno de liberación a preparación. Aquí se realiza la</span> <a href="https://help.vtex.com/es/tutorial/como-a-reserva-funciona--tutorials_92#reserva-confirmada"><span style="font-weight:400;color:#F71963;background-color:transparent">confirmación de la reserva</span></a><span style="font-weight:400">.</span></td>
+    <td class="tg-zr06"><span style="font-weight:400">Proceso interno de liberación a preparación. Aquí se realiza la</span> <a href="https://help.vtex.com/es/tutorial/como-a-reserva-funciona--tutorials_92#reserva-confirmada"><span style="font-weight:400;color:#F71963;background-color:transparent">confirmación de la reserva</span></a><span style="font-weight:400">. Cuando el marketplace no autoriza al seller el fulfillment del pedido dentro de 30 días, la plataforma cancela el pedido automáticamente.</span></td>
   </tr>
   <tr>
     <td class="tg-zr06"><span style="font-weight:400">Periodo de cancelación</span></td>
diff --git a/docs/tutorials/es/order-replacement.md b/docs/tutorials/es/order-replacement.md
index dfa4330c7..dff0392cd 100644
--- a/docs/tutorials/es/order-replacement.md
+++ b/docs/tutorials/es/order-replacement.md
@@ -3,8 +3,8 @@ title: 'Cambio de pedido'
 id: 2IK9mwQjBKseQmE8K8saO8
 status: PUBLISHED
 createdAt: 2018-02-20T19:29:21.502Z
-updatedAt: 2023-03-29T15:54:02.723Z
-publishedAt: 2023-03-29T15:54:02.723Z
+updatedAt: 2024-07-08T14:22:27.104Z
+publishedAt: 2024-07-08T14:22:27.104Z
 firstPublishedAt: 2018-02-20T20:24:08.083Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -60,7 +60,7 @@ Los datos que se pueden modificar con el cambio de pedidos son:
 El cambio de pedidos no es posible en los casos de:
 
 * [Pedidos incompletos](https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos--tutorials_294): cuando el pedido no contiene toda la información necesaria para ser finalizado en la plataforma.
-* Transacción compartida: pedidos con más de un _seller_ y pago realizado al _marketplace_.
+* Transacción compartida: pedidos con un o más _sellers_ y pago realizado al _marketplace_.
 * Pedidos ya modificados por la tienda.
 * Pedidos con los siguientes status:
     * Verificando factura
diff --git a/docs/tutorials/es/order-report.md b/docs/tutorials/es/order-report.md
index 3bf8fe642..5574d4bce 100644
--- a/docs/tutorials/es/order-report.md
+++ b/docs/tutorials/es/order-report.md
@@ -3,8 +3,8 @@ title: 'Informe de pedidos'
 id: 31m1ewsmsEe0WS4So2aGMY
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:42.311Z
-updatedAt: 2023-05-31T15:43:26.524Z
-publishedAt: 2023-05-31T15:43:26.524Z
+updatedAt: 2024-03-01T01:28:57.258Z
+publishedAt: 2024-03-01T01:28:57.258Z
 firstPublishedAt: 2019-01-24T22:03:18.967Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -114,7 +114,7 @@ Las columnas corresponden a información específica sobre el pedido, conforme s
 *   **Taxes**: es el resultado de la suma entre Tax y CustomTax, las tarifas asignadas al SKU. Si ambos valores no existen, la columna estará vacía.
 *   **Invoice Number**: es el número de factura del pedido.
 *   **Country**: es el país en el que se realizó el pedido.
-*   **Input Invoices Numbers:** son los números de la factura de entrada, referente a una devolución.
-*   **Output Invoices Numbers:** son los números de la factura referente a una compra.
+*   **Input Invoices Numbers:** son los números de la factura de tipo Output, referente a una compra.
+*   **Output Invoices Numbers:** son los números de la factura de tipo Input, referente a una devolución.
 *   **Status raw value (temporary)**: es el valor del _status_ de un pedido sin ningún tratamiento específico, es decir, el _status_ de un pedido como una _string_ que no ha sido tratada. Por ejemplo: el _status_ de un pedido puede aparecer en la interfaz como `preparando` y en este campo sería `handling`.
 *   **Cancellation Data**: motivo de la cancelación del pedido indicado por el cliente final, de acuerdo con lo que se muestra en el campo `Reason` del objeto `cancellationData` exhibido en la [API de Orders](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/cancel). En caso de que el usuario no complete este campo cuando realice la cancelación, dicha columna estará vacía en el informe.
diff --git a/docs/tutorials/es/order-split-and-delivery-split.md b/docs/tutorials/es/order-split-and-delivery-split.md
index 038dcc267..bf0a69a65 100644
--- a/docs/tutorials/es/order-split-and-delivery-split.md
+++ b/docs/tutorials/es/order-split-and-delivery-split.md
@@ -3,8 +3,8 @@ title: 'División de pedidos y división de entregas'
 id: jQvzA6QgSd51e2p6bthoV
 status: PUBLISHED
 createdAt: 2021-09-27T21:06:59.520Z
-updatedAt: 2023-01-13T18:53:14.386Z
-publishedAt: 2023-01-13T18:53:14.386Z
+updatedAt: 2023-09-23T01:00:23.558Z
+publishedAt: 2023-09-23T01:00:23.558Z
 firstPublishedAt: 2021-09-27T21:12:55.418Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -58,4 +58,4 @@ El pedido lo atiende un solo _seller_, pero es necesario realizar más de una en
   No recomendamos operar la tienda con el campo <code>allowMultipleDeliveries</code> indicado como <i>false</i>. En esta configuración, cuando hay artículos en el carrito que no tienen ningún método de entrega en común, es decir, los SLAID son diferentes y el carrito tiene un punto de recogida, no será posible completar el pedido.
 </div>
 
-* **Almacenes diferentes:** una misma tienda ofrece todos los ítems de un pedido, pero estos se encuentran en diferentes almacenes. Entonces hay que _dividir los paquetes de entrega_, pero sin dividir el pedido entre diferentes tiendas. La plataforma lo hace automáticamente.
+* **Muelles diferentes:** una misma tienda ofrece todos los ítems de un pedido, pero en el cálculo de la ruta logística están asociados a diferentes muelles. Entonces hay que _dividir los paquetes de entrega_, pero sin dividir el pedido entre diferentes tiendas. La plataforma lo hace automáticamente.
diff --git a/docs/tutorials/es/order-transactional-email-templates.md b/docs/tutorials/es/order-transactional-email-templates.md
index bf4cdd2f9..5e98c6bfc 100644
--- a/docs/tutorials/es/order-transactional-email-templates.md
+++ b/docs/tutorials/es/order-transactional-email-templates.md
@@ -3,8 +3,8 @@ title: 'Plantillas de emails transaccionales del pedido'
 id: 3g2S2kqBOoSGcCaqMYK2my
 status: PUBLISHED
 createdAt: 2018-11-06T21:01:19.818Z
-updatedAt: 2023-02-28T01:10:27.048Z
-publishedAt: 2023-02-28T01:10:27.048Z
+updatedAt: 2024-03-01T01:15:49.954Z
+publishedAt: 2024-03-01T01:15:49.954Z
 firstPublishedAt: 2018-11-07T18:11:42.445Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -27,19 +27,19 @@ Para acceder a las plantillas, siga los siguientes pasos:
 2. Haga clic en __Templates__.
 3. En la barra de búsqueda, escriba el nombre o la clave de la plantilla que desea buscar. Consulte la lista a continuación para obtener más información.
 
-| Template   | Clave        | Descripción | Gatillo    |
+| Template | Clave | Descripción | Gatillo |
 | ---------- | ---------- | ---------- | ---------- |
-| Order confirmation | vtexcommerce-new-order | Correo electrónico se envía cuando se completa el pedido | Checkout realiza un nuevo pedido |
-| Replace Order | vtexcommerce-replace-order | Se envía un correo electrónico cuando el pedido fue reemplazado con éxito | Checkout realiza un nuevo pedido e informa a __Gestión de pedidos__ sobre el reemplazo |
-| Order change payment | vtexcommerce-order-change-payment | Notifica que el pago ha sido modificado | El cliente cambia el pago y Checkout notifica a __Gestión de pedidos__ que el pago se ha modificado |
-| Payment pending | vtexcommerce-payment-pending | Notifica de pago pendiente | __Gestión de pedidos__ envía el correo electrónico 2 días antes de que caduque el boleto |
-| Payment approved | vtexcommerce-payment-approved | Notifica que el pago fue aprobado | Cambios en el estado del pedido a __Pago aprobado__ |
-| Change of information order | vtexcommerce-order-changed | Notifica que el [pedido ha sido modificado](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) | Checkout notifica el evento de cambio de pedido (descuento, agregar artículo o eliminar artículo) |
-| Order invoiced | vtexcommerce-order-invoiced | Notifica que el pedido fue facturado | El estado del pedido cambia a __Invoiced__ |
-| Cancel billed request | vtexcommerce-order-invoiced-with-cancel-request | Notifica que el pedido no puede ser cancelado después de ser facturado | El vendedor niega una solicitud de cancelación cuando el pedido tiene el estado Manejo de envío |
-| Cancel shipped order | vtexcommerce-order-shipped-with-cancel-request | Notifica que el pedido no se puede cancelar después de que se haya enviado | El vendedor niega una solicitud de cancelación cuando el pedido ha recibido un número de seguimiento o datos de URL de seguimiento. |
-| Order shipped | vtexcommerce-order-shipped | Notifica que el pedido fue enviado | El pedido recibe la factura con número de seguimiento o datos de URL de seguimiento |
+| Order confirmation | vtexcommerce-new-order | Correo electrónico se envía cuando se completa el pedido. | Checkout realiza un nuevo pedido. |
+| Replace Order | vtexcommerce-replace-order | Se envía un correo electrónico cuando el pedido fue reemplazado con éxito. | Checkout realiza un nuevo pedido e informa a __Gestión de pedidos__ sobre el reemplazo. |
+| Order change payment | vtexcommerce-order-change-payment | Notifica que el pago ha sido modificado. | El cliente cambia el pago y Checkout notifica a __Gestión de pedidos__ que el pago se ha modificado. |
+| Payment pending | vtexcommerce-payment-pending | Notifica de pago pendiente. | __Gestión de pedidos__ envía el correo electrónico 48 horas después de realizar el pedido. |
+| Payment approved | vtexcommerce-payment-approved | Notifica que el pago fue aprobado. | Cambios en el estado del pedido a __Pago aprobado__. |
+| Change of information order | vtexcommerce-order-changed | Notifica que el [pedido ha sido modificado](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190). | Checkout notifica el evento de cambio de pedido (descuento, agregar artículo o eliminar artículo). |
+| Order invoiced | vtexcommerce-order-invoiced | Notifica que el pedido fue facturado. | El estado del pedido cambia a __Invoiced__. |
+| Cancel billed request | vtexcommerce-order-invoiced-with-cancel-request | Notifica que el pedido no puede ser cancelado después de ser facturado. | El vendedor niega una solicitud de cancelación cuando el pedido tiene el estado Manejo de envío. |
+| Cancel shipped order | vtexcommerce-order-shipped-with-cancel-request | Notifica que el pedido no se puede cancelar después de que se haya enviado. | El vendedor niega una solicitud de cancelación cuando el pedido ha recibido un número de seguimiento o datos de URL de seguimiento. |
+| Order shipped | vtexcommerce-order-shipped | Notifica que el pedido fue enviado. | El pedido recibe la factura con número de seguimiento o datos de URL de seguimiento. Si realiza el envío por primera vez, deberá completar ambas informaciones: `trackingNumber` y `trackingURL`. |
 | Shipping Update | vtexcommerce-order-shipping-update | Notificación de eventos de envío, como "recogido por la transportadoras", por ejemplo. | El pedido debe tener la factura y un número de rastreo o una URL de rastreo vinculada a la factura. Además, debe tener los eventos de entrega, que es la información principal de esta plantilla. |
 | Order delivered | vtexcommerce-order-shipping-finished | Notifica que el envío se ha completado. El pedido debe tener la factura y un número de rastreo o una URL de rastreo vinculada a la factura. | El vendedor confirma la entrega. Esta acción cambia el valor del campo `isDelivered` a `true` en el json del pedido. |
-| Order cancelled | vtexcommerce-order-cancelled | Notificación de cancelación de pedido | El estado del pedido cambia a __Cancelado__ |
-| [Order refund](https://help.vtex.com/es/tutorial/template-de-e-mail-transacional-para-pedido-estornado--5uy6FCBb6DLyIJlSDeM10G) | vtexcommerce-order-refunded | Notificación de reembolso de pedido | El vendedor inserta la factura con el valor reembolsado por la API [Order Invoice Notification](https://developers.vtex.com/reference/invoice#invoicenotification), con el valor `input` en el campo `type`. En el Administrador, este evento se activa cuando se hace clic en el botón **Hacer devolución de ítems** en la pantalla de detalles del pedido.|
+| Order cancelled | vtexcommerce-order-cancelled | Notificación de cancelación de pedido | El estado del pedido cambia a __Cancelado__. |
+| [Order refund](https://help.vtex.com/es/tutorial/template-de-e-mail-transacional-para-pedido-estornado--5uy6FCBb6DLyIJlSDeM10G) | vtexcommerce-order-refunded | Notificación de reembolso de pedido. | El vendedor inserta la factura con el valor reembolsado por la API [Order Invoice Notification](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice), con el valor `input` en el campo `type`. En el Administrador, este evento se activa cuando se hace clic en el botón **Hacer devolución de ítems** en la pantalla de detalles del pedido. |
diff --git a/docs/tutorials/es/orderform-settings.md b/docs/tutorials/es/orderform-settings.md
new file mode 100644
index 000000000..bc18c1c89
--- /dev/null
+++ b/docs/tutorials/es/orderform-settings.md
@@ -0,0 +1,40 @@
+---
+title: 'Configuración de orderForm'
+id: 7EAqNk48KP2QHnCxu856jT
+status: DRAFT
+createdAt: 2024-06-18T13:34:07.902Z
+updatedAt: 2024-06-18T13:44:46.612Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Shopping
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configuracion-de-orderform
+locale: es
+legacySlug: configuracion-de-orderform
+subcategory: 
+---
+
+# Configuración de orderForm
+
+En las secciones a continuación, describimos algunos ajustes de seguridad disponibles en Checkout que se pueden activar mediante el endpoint[ Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
+
+## Exigir inicio de sesión al completar una compra
+
+Al declarar el campo `requiresLoginToPlaceOrder` como `true` se determina que solamente aquellos clientes que hayan pasado por el proceso de autenticación puedan realizar compras. El cliente debe tener una sesión iniciada con el email que proporcionó cuando agregó los productos al carrito.
+
+Cuando activas este campo, [SmartCheckout](https://help.vtex.com/es/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB) será desactivado para todos los clientes de la tienda.
+
+## Tiempo mínimo entre pedidos
+
+Al definir un valor numérico para el campo `minimumPurchaseDowntimeSeconds`, puedes determinar el tiempo mínimo en segundos que un comprador debe esperar antes de realizar otra compra. Este ajuste evita que los clientes creen múltiples pedidos en un breve periodo de tiempo.
+
+Recomendamos configurar el valor de este campo como 90 segundos y utilizar este ajuste junto con [Exigir inicio de sesión al completar una compra](#exigir-inicio-de-sesion-al-completar-una-compra).
+
+## Tiempo mínimo de existencia de un carrito para permitir el uso de una nueva tarjeta de crédito
+
+La definición de un valor numérico en el campo `cartAgeToUseNewCardSeconds` determina el tiempo en segundos que un nuevo carrito debe existir antes de que sea posible autorizar y aplicar una nueva tarjeta de crédito.
+
+Esta configuración reduce la probabilidad de creación de varios carritos simultáneamente y evita que se agreguen nuevas tarjetas de crédito. La activación de este campo no afecta las compras realizadas con tarjetas ya guardadas en la cuenta del cliente.
+
+Recomendamos configurar este campo con un valor de 30 segundos.
diff --git a/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md b/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
index e0470eb1b..e06572106 100644
--- a/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
+++ b/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
@@ -29,6 +29,6 @@ Entre las imágenes del SKU, la principal será aquella flechada en el registro
 
 Vea, en nuestro ejemplo, que aunque no sea la primera imagen registrada, la imagen definida como principal es la que se asume en la página de producto al seleccionar el SKU.
 
-![sku_imagem_principal es](https://images.ctfassets.net/alneenqid6w5/4NAI7uGKy4aYq6qeKW6I6y/a3290a6d910a321c57ac58349a9d78b1/ex_3_es.png)
+![sku_imagem_principal es](//images.ctfassets.net/alneenqid6w5/4NAI7uGKy4aYq6qeKW6I6y/a3290a6d910a321c57ac58349a9d78b1/ex_3_es.png)
 
 - Al subir la planilla de imágenes, la plataforma considera línea a línea luego la primera línea de un sku será considerada la principal y así sucesivamente.
diff --git a/docs/tutorials/es/orders-list.md b/docs/tutorials/es/orders-list.md
index 18feb41d6..575cadecf 100644
--- a/docs/tutorials/es/orders-list.md
+++ b/docs/tutorials/es/orders-list.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Es a través de la lista de pedidos de Gestión de Pedidos que el administrador de la tienda puede acompañar las compras concretadas en su tienda. La lista está disponible en la primera pantalla del módulo de __Gestión de pedidos__.
 
-![todosospedidos.es](https://images.ctfassets.net/alneenqid6w5/61CuVQRq34KRRF3snvvKaE/f0fefc688ca00abd418c042d01a655da/todosospedidos.es.png)
+![todosospedidos.es](//images.ctfassets.net/alneenqid6w5/61CuVQRq34KRRF3snvvKaE/f0fefc688ca00abd418c042d01a655da/todosospedidos.es.png)
 
 En la vista predeterminada se muestran todos los pedidos de la tienda desde el más reciente. Usted puede cambiar el orden haciendo clic en el nombre de las columnas, así como buscar o filtrar los pedidos por datos específicos, y también exportar estos datos.
 
@@ -30,7 +30,7 @@ Al hacer clic en cualquier pedido, el usuario es dirigido a la página de detall
 
 Siempre que el módulo de Gestión de Pedidos esté abierto y se hayan realizado nuevos pedidos, se mostrará una indicación, permitiendo que se haga clic para actualizar la lista de pedidos.
 
-![novopedido.es](https://images.ctfassets.net/alneenqid6w5/2xSXOyFF91NG1U1T0jlu32/75b80899d88f814136f28e80d070015a/novopedido.es.png)
+![novopedido.es](//images.ctfassets.net/alneenqid6w5/2xSXOyFF91NG1U1T0jlu32/75b80899d88f814136f28e80d070015a/novopedido.es.png)
 
 A continuación, se muestran más detalles sobre las columnas de la lista:
 
@@ -38,7 +38,7 @@ A continuación, se muestran más detalles sobre las columnas de la lista:
 
 No es nada más que el número de pedido (mostrado al cliente), el sufijo y el código secuencial de la transacción (para uso interno).
 
-![nsequecial.es](https://images.ctfassets.net/alneenqid6w5/X5TM9ww79vrqUWk8NaJPG/f45cba83a8faeb03c1ecadc1c7d24e19/nsequecial.es.png)
+![nsequecial.es](//images.ctfassets.net/alneenqid6w5/X5TM9ww79vrqUWk8NaJPG/f45cba83a8faeb03c1ecadc1c7d24e19/nsequecial.es.png)
 
 ### Número del pedido
 
diff --git a/docs/tutorials/es/orders-overview.md b/docs/tutorials/es/orders-overview.md
index d84dc9b51..df4a4ab74 100644
--- a/docs/tutorials/es/orders-overview.md
+++ b/docs/tutorials/es/orders-overview.md
@@ -3,8 +3,8 @@ title: 'Vista General Pedidos'
 id: tutorials_201
 status: PUBLISHED
 createdAt: 2017-04-27T22:13:42.525Z
-updatedAt: 2023-04-26T14:51:44.363Z
-publishedAt: 2023-04-26T14:51:44.363Z
+updatedAt: 2023-12-21T14:01:20.828Z
+publishedAt: 2023-12-21T14:01:20.828Z
 firstPublishedAt: 2017-04-27T23:03:03.051Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -30,6 +30,17 @@ Esta sección incluye las siguientes páginas:
 - [Transacciones](https://help.vtex.com/es/tutorial/how-to-view-transactions-on-pci-gateway--tutorials_461) 
 - [Conciliación bancaria](https://help.vtex.com/es/tutorial/bank-reconciliations--tutorials_453) 
 
+Además de buscar pedidos en **Pedidos > Todos los pedidos**, puede buscar pedidos desde cualquier página del Admin VTEX utilizando la barra de búsqueda global en la parte superior de la página. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
+<div class = "alert alert-info">
+Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
+</div>
+
 ## Suscripciones
 
 En la plataforma VTEX, puedes crear [suscripciones](https://help.vtex.com/es/tutorial/how-subscriptions-work--frequentlyAskedQuestions_4453), es decir, ofrecer a tus clientes la posibilidad de realizar pedidos recurrentes automáticamente, según la frecuencia establecida.
diff --git a/docs/tutorials/es/orders.md b/docs/tutorials/es/orders.md
new file mode 100644
index 000000000..c15a6cb83
--- /dev/null
+++ b/docs/tutorials/es/orders.md
@@ -0,0 +1,380 @@
+---
+title: 'Pedidos Data Pipeline (Beta)'
+id: 2f3GlRJ5L5IRGVIxOmzrFv
+status: PUBLISHED
+createdAt: 2024-02-02T17:58:53.962Z
+updatedAt: 2024-06-21T16:26:28.394Z
+publishedAt: 2024-06-21T16:26:28.394Z
+firstPublishedAt: 2024-05-27T19:26:59.238Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: pedidos
+locale: es
+legacySlug: pedidos
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+El conjunto de datos de pedidos se compone de dos tablas principales:
+
+`orders_historical` y `orders_latest`. Las tablas incluyen distintos campos `SUPER` que engloban información variada como ítems comprados, detalles de envío, sellers implicados y pagos, entre otros.
+
+Debido a la naturaleza de la relación 1 a N entre muchos de estos campos SUPER y los pedidos, y a la cantidad de información que contienen, hemos implementado tablas auxiliares especializadas, como `orders_shipping` y `orders_items`, para facilitar la gestión de estos datos.
+
+Para realizar análisis, es habitual hacer selecciones directas dentro de los campos SUPER, destacando partes concretas que queremos extraer. También podemos unir una de las tablas principales (`orders` o `latest`) con las tablas auxiliares, utilizando `orderid como clave.
+
+Este método permite extraer eficazmente información específica, lo que facilita analizar en detalle los pedidos y sus componentes asociados.
+
+En esta sección puedes consultar la siguiente información:
+
+- [Características de los datos de pedidos](#características-de-los-datos)
+- [Tabla orders_latest](#tabla-orders_latest)
+- [Tabla orders_historical](#tabla-orders_historical)
+- [Tabla orders_totals](#tabla-orders_totals)
+- [Tabla orders_shipping](#tabla-orders_shipping)
+- [Tabla orders_sellers](#tabla-orders_sellers)
+- [Tabla orders_rateandbenefitsidentifiers](#tabla-orders_rateandbenefitsidentifiers)
+- [Tabla orders_payments](#tabla-orders_payments)
+- [Tabla orders_packages](#tabla-orders_packages)
+- [Tabla orders_items](#tabla-orders_items)
+- [Análisis con datos de pedidos](#analisis-con-datos-de-pedidos)
+- [Correlaciones con otros datos](#correlacioines-con-otros-datos)
+
+## Características de los datos
+
+|**Característica**|**Descripción**|
+| - | - |
+|**Origen**|Los datos del conjunto de pedidos proceden del [OMS (Order Management System)](https://help.vtex.com/es/tutorial/gerenciamento-de-pedidos-visao-geral--tutorials_201).|
+|**Disponibilidad**|Se puede acceder a los datos de pedidos a través del [informe de pedidos](https://help.vtex.com/es/tutorial/exportacao-de-pedidos-no-modulo-pedidos--tutorials_6417) en el Admin VTEX y también por las [API de Orders](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders?endpoint=get-/api/oms/pvt/orders). Es importante tener en cuenta que los datos facilitados por la API pueden no estar estructurados exactamente de la misma manera que en este conjunto de datos de Data Pipeline.|
+|**Historial**|Los datos se conservan durante dos años, a partir de 2022 para los clientes que ya utilizan la plataforma VTEX.|
+|**Intervalo mínimo de actualización**|Una hora.|
+
+## Tabla orders_latest
+
+La tabla `latest` almacena el status más reciente de cada pedido, incluyendo detalles como fecha de actualización, ID del pedido y la información del cliente.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único de pedido. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido. |
+| **value** | double precision | Valor total del pedido. |
+| **totals** | super | Detalles adicionales sobre los totales del pedido, como subtotal, impuestos, descuentos, etc. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido. |
+| **items** | super | Información detallada sobre los ítems del pedido. |
+| **clientprofiledata_userprofileid** | character varying(65535) | ID del perfil de usuario en el sistema de gestión de clientes. |
+| **shippingdata_address_city** | character varying(65535) | Ciudad de envío del pedido. |
+| **shippingdata_address_state** | character varying(65535) | Estado de envío del pedido. |
+| **shippingdata_address_country** | character varying(65535) | País de envío del pedido. |
+| **shippingdata_logisticsinfo** | super | Información logística sobre el envío del pedido. |
+| **sellers** | super | Datos de los sellers asociados al pedido. |
+| **storepreferencesdata_countrycode** | character varying(65535) | Código de país de la tienda. |
+| **storepreferencesdata_timezone** | character varying(65535) | Zona horaria de la tienda. |
+| **storepreferencesdata_currencycode** | character varying(65535) | Código de la moneda utilizada en la tienda. |
+| **packages** | super | Detalles sobre el embalaje de los ítems del pedido. |
+| **origin** | character varying(16383) | Origen del pedido. |
+| **iscompleted** | boolean | Indica si el pedido está completo. |
+| **affiliateid** | character varying(16383) | ID de afiliado asociado al pedido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **authorizeddate** | timestamp with time zone | Fecha y hora de autorización del pedido. |
+| **invoiceddate** | timestamp with time zone | Fecha y hora de emisión de la factura del pedido. |
+| **marketplaceorderid** | character varying(16383) | ID del pedido en el marketplace. |
+| **marketplaceserviciosendpoint** | character varying(16383) | Endpoint de servicios del marketplace. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación en el pedido. |
+| **marketingdata_utmsource** | character varying(65535) | Fuente UTM para fines de marketing. |
+| **marketing_data_output_media** | character varying(65535) | Medio UTM para fines de marketing. |
+| **marketingdata_utmcampaign** | character varying(65535) | Campaña UTM para fines de marketing. |
+| **marketingdata_utmpartner** | character varying(65535) | Partner UTM para fines de marketing. |
+| **marketing_data_outmipage** | character varying(65535) | Página UTM para fines de marketing. |
+| **marketingdata_outmipart** | character varying(65535) | Parte UTM para fines de marketing. |
+| **marketingdata_utmicampaign** | character varying(65535) | Campaña UTM alternativa para fines de marketing. |
+| **marketingdata_coupon** | character varying(65535) | Código del cupón de descuento aplicado al pedido. |
+| **marketingdata_marketingtags** | super | Tags de marketing asociadas al pedido. |
+| **marketplace_name** | character varying(65535) | Nombre del marketplace asociado al pedido. |
+| **marketplace_iscertified** | super | Indica si el marketplace está certificado. |
+| **marketplace_baseurl** | character varying(65535) | URL base del marketplace. |
+| **contextdata_loggedin** | super | Indica si el usuario había iniciado sesión durante la realización del pedido. |
+| **contextdata_useragent** | character varying(65535) | User-agent utilizado durante la realización del pedido. |
+| **contextdata_userid** | character varying(65535) | ID del usuario que realizó el pedido. |
+| **rateandbenefitsidentifiers** | super | Identificadores de cargos y promociones aplicados al pedido. |
+| **transactions** | super | Detalles de las transacciones financieras del pedido. |
+| **giftcards** | super | Información sobre las tarjetas de regalo utilizadas en el pedido. |
+| **saleschannel** | character varying(16383) | Canal de venta a través del cual se realizó el pedido. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+| **sellerorderid** | character varying(16383) | ID de pedido asignado por el seller. |
+| **ordergroup** | character varying(16383) | Grupo de pedidos al que pertenece este pedido. |
+| **workflowisinerror** | boolean | Indica si se ha producido un error en el flujo de trabajo del pedido. |
+| **clientprofiledata_email** | character varying(256) | Email del perfil de cliente asociado al pedido. |
+| **changesattachment_id** | character varying(256) | ID del anexo de personalización del pedido. |
+| **changesattachment_changesdata** | super | Datos de los cambios realizados en el pedido. |
+| **shippingdata_postal_code** | character varying(256) | Código postal de la dirección de envío del pedido. |  
+
+## Tabla orders_historical
+
+La tabla `historical` almacena un registro completo de todas las actualizaciones de pedidos.  
+Consulta a continuación los campos que componen la tabla:
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido, normalmente utilizado como clave primaria. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido, indicando el servidor o dominio que gestiona el pedido. |
+| **value** | double precision | Valor monetario total del pedido. Puede incluir impuestos, descuentos y costos de envío. |
+| **totals** | super | Detalles adicionales sobre los totales del pedido, que pueden incluir información desglosada en subtotal, impuestos, descuentos, entre otros. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **items** | super | Información detallada sobre ítems del pedido, que puede incluir SKU, cantidad, precio y descuentos específicos de los ítems. |
+| **clientprofiledata_userprofileid** | character varying(65535) | Identificador del perfil de usuario del cliente que ha realizado el pedido. |
+| **shippingdata_address_city** | character varying(65535) | Parte de la dirección referida a la ciudad de envío del pedido. |
+| **shippingdata_address_state** | character varying(65535) | Parte de la dirección referida al estado o región de envío del pedido. |
+| **shippingdata_address_country** | character varying(65535) | Parte de la dirección referida al país de envío del pedido. |
+| **shippingdata_logisticsinfo** | super | Información logística relativa al envío del pedido, que puede incluir datos de la transportadora e información de seguimiento. |
+| **sellers** | super | Información de los sellers asociados al pedido. Puede incluir los ID y los nombres de los sellers. |
+| **storepreferencesdata_countrycode** | character varying(65535) | Código de país de la tienda donde se realizó el pedido. |
+| **storepreferencesdata_timezone** | character varying(65535) | Zona horaria de la tienda donde se realizó el pedido. |
+| **storepreferencesdata_currencycode** | character varying(65535) | Código de la moneda utilizada en la transacción del pedido. |
+| **packages** | super | Detalles sobre el embalaje de los ítems del pedido, que pueden incluir tipos de embalaje y dimensiones. |
+| **origin** | character varying(16383) | Origen del pedido, que indica dónde y cómo se inició. |
+| **iscompleted** | boolean | Indica si se completó el pedido. |
+| **affiliateid** | character varying(16383) | Identificador de un afiliado o fuente de referencia asociada al pedido. |
+| **status** | character varying(16383) | Status actual del pedido, como 'pendiente', 'enviado' o 'completado'. |
+| **authorizeddate** | timestamp with time zone | Fecha y hora en que se autorizó el pedido. |
+| **invoiceddate** | timestamp with time zone | Fecha y hora de emisión de la factura del pedido. |
+| **marketplaceorderid** | character varying(16383) | Identificador del pedido en un marketplace, si procede. |
+| **marketplaceserviciosendpoint** | character varying(16383) | Endpoint o URL para servicios de marketplace relacionados con el pedido. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación realizada en el pedido. |
+| **marketingdata_utmsource** | character varying(65535) | Parámetro de origen UTM en datos de marketing, que indica el origen del tráfico o de la campaña. |
+| **marketing_data_output_media** | character varying(65535) | Parámetro UTM de medio en datos de marketing, indicando el medio utilizado en la campaña (por ejemplo, email o redes sociales). |
+| **marketingdata_utmcampaign** | character varying(65535) | Parámetro UTM de campaña en datos de marketing, que especifica el nombre o código concreto de la campaña. |
+| **marketingdata_utmpartner** | character varying(65535) | Parámetro UTM de partner, que indica una asociación o colaboración en esfuerzos de marketing. |
+| **marketing_data_outmipage** | character varying(65535) | Parámetro UTM de página, que puede indicar la página específica o ubicación de la campaña. |
+| **marketingdata_outmipart** | character varying(65535) | Parámetro UTM de parte, que puede indicar un componente o sección específica de la campaña de marketing. |
+| **marketingdata_utmicampaign** | character varying(65535) | Parámetro UTM de campaña alternativo para un seguimiento adicional de la campaña. |
+| **marketingdata_coupon** | character varying(65535) | Código de cupón utilizado, en su caso, para descuentos en el pedido. |
+| **marketingdata_marketingtags** | super | Tags o palabras clave asociadas a los esfuerzos de marketing del pedido. |
+| **marketplace_name** | character varying(65535) | Nombre del marketplace en el que se realizó el pedido, si procede. |
+| **marketplace_iscertified** | super | Indica si el marketplace en el que se realizó el pedido está certificado o es reconocido. |
+| **marketplace_baseurl** | character varying(65535) | URL base del marketplace donde se realizó el pedido. |
+| **contextdata_loggedin** | super | Indica si el usuario tenía una sesión iniciada al realizar el pedido. |
+| **contextdata_useragent** | character varying(65535) | String de user-agent del navegador o dispositivo utilizado al realizar el pedido. |
+| **contextdata_userid** | character varying(65535) | ID del usuario que realizó el pedido. |
+| **rateandbenefitsidentifiers** | super | Identificadores de cargos y promociones aplicadas al pedido, como valor de fidelidad o descuentos para socios. |
+| **transactions** | super | Información detallada sobre las transacciones financieras asociadas al pedido. |
+| **giftcards** | super | Información sobre las tarjetas de regalo utilizadas en el pedido. |
+| **saleschannel** | character varying(16383) | Canal de venta a través del cual se realizó el pedido (tienda online, tienda física u otras). |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+| **sellerorderid** | character varying(16383) | Un ID de pedido asignado por el seller, diferente del ID principal de pedido. |
+| **ordergroup** | character varying(16383) | El grupo de pedidos al que este pedido pertenece, utilizado para agrupar varios pedidos. |
+| **workflowisinerror** | boolean | Indica si se produjo un error en el flujo de trabajo de procesamiento del pedido. |
+| **clientprofiledata_email** | character varying(256) | La dirección de email del cliente asociado al pedido. |
+| **changesattachment_id** | character varying(256) | Identificador único para una operación de cambio asociada al pedido. |
+| **changesattachment_changesdata** | super | Detalles de los cambios realizados en el pedido, como agregar o remover ítems, así como otras modificaciones. |
+| **shippingdata_postal_code** | character varying(256) | Código postal de la dirección de envío del pedido. |
+
+## Tabla orders_totals
+
+La tabla `totals` proporciona un resumen de los valores totales asociados a cada pedido, incluido el valor total del pedido, descuentos aplicados e impuestos.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. Suele estar unido a la columna 'orderid' de la tabla 'vtex.orders_latest' para realizar análisis cruzados. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido, indicando el servidor o dominio que gestiona el pedido. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación realizada en el pedido, que refleja la actualización más reciente de status o contenido. |
+| **status** | character varying(16383) | Status actual del pedido. Suele estar unido a la columna 'status' de la tabla 'vtex.orders_latest' para realizar un seguimiento de los cambios de status. |
+| **totals_id** | character varying(65535) | Identificador único para los totales de pedido, utilizado para hacer referencia a detalles específicos del total de pedido. |
+| **totals_name** | character varying(65535) | Nombre o descripción de los totales de pedido, proporcionando una visión general de lo que representa el total (por ejemplo, subtotal, impuestos, descuentos). |
+| **totals_value** | double precision | Valor numérico asociado a los totales de pedido, como valor total, subtotal, impuestos, descuentos, etc. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |  
+
+## Tabla orders_shipping  
+
+En la tabla `shipping` se detalla la información de envío de pedidos, como dirección de entrega, gastos de envío y proveedores de servicios logísticos.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido. Suele estar unido a 'hostname' de la tabla 'vtex.client_registry_gold'. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación en el pedido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **shippingdata_address_city** | character varying(65535) | Ciudad en la dirección de envío del pedido. |
+| **shippingdata_address_state** | character varying(65535) | Estado en la dirección de envío del pedido. |
+| **shippingdata_address_country** | character varying(65535) | País en la dirección de envío del pedido. |
+| **deliveryids** | super | Identificadores asociados al envío del pedido. |
+| **shippingestimate** | character varying(65535) | Tiempo estimado de envío del pedido. |
+| **pickupstoreinfo_ispickupstore** | boolean | Indica si el punto de recogida es una tienda física. |
+| **pickupstoreinfo_friendlyname** | character varying(65535) | Nombre descriptivo del punto de recogida. |
+| **pickupstoreinfo_dockid** | character varying(65535) | Identificador del punto de recogida. |
+| **deliverychannel** | character varying(65535) | Canal de entrega utilizado para el pedido. |
+| **deliverywindow** | character varying(65535) | Plazo estimado de entrega. |
+| **sellingprice** | double precision | Precio de venta del ítem en el pedido. |
+| **listprice** | double precision | Precio de lista del ítem en el pedido. |
+| **price** | double precision | Precio final del ítem en el pedido. |
+| **shippingestimatedate** | timestamp with time zone | Fecha estimada de envío del pedido. |
+| **selecteddeliverychannel** | character varying(65535) | Canal de entrega seleccionado para el pedido. |
+| **selectedsla** | character varying(65535) | Acuerdo de nivel de servicio (SLA) seleccionado para el pedido. |
+| **deliverychannels** | super | Canales de entrega disponibles para el pedido. |
+| **slas** | super | SLA disponibles para el pedido. |
+| **pickupdistance** | double precision | Distancia al punto de recogida del pedido. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+| **shippingdata_postal_code** | character varying(256) | Código postal de la dirección de envío del pedido. |
+
+## Tabla orders_sellers  
+
+La tabla `sellers` almacena la lista de sellers relacionados con cada pedido. Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. Suele estar unido a la columna 'orderid' de la tabla 'vtex.orders_historical' para realizar análisis cruzados. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido, indicando el servidor o dominio que gestiona el pedido. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora del último cambio realizado en el pedido, que refleja la actualización más reciente de status o contenido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **id** | character varying(65535) | Identificador único, generalmente utilizado para referirse a un elemento específico dentro de un contexto más amplio. |
+| **name** | character varying(65535) | Nombre o título del elemento referenciado, que proporciona una identificación legible por humanos. |
+| **logo** | character varying(65535) | Ruta o URL al logotipo asociado, a menudo utilizado en contextos de branding o identificación visual. |
+| **fulfillmentendpoint** | character varying(65535) | Endpoint o URL de los servicios de fulfillment, que indica dónde se gestionan las operaciones de cumplimiento de pedidos. |
+| **subsellerid** | character varying(65535) | Identificador de un subseller o seller secundario asociado al pedido u operación. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+
+## Tabla orders_rateandbenefitsidentifiers  
+
+La tabla `rateandbenefitsidentifiers` contiene datos sobre promociones aplicadas a los pedidos.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido, indicando el servidor o dominio que gestiona el pedido. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación realizada en el pedido, que refleja la actualización más reciente de status o contenido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **rateandbenefitsidentifiers_id** | character varying(65535) | Identificador único para identificadores de cargos y promociones asociados al pedido. |
+| **rateandbenefitsidentifiers_name** | character varying(65535) | Nombre o título de los identificadores de cargos y promociones, para proporcionar una identificación precisa del cargo o promoción. |
+| **rateandbenefitsidentifiers_featured** | boolean | Indica si los identificadores de cargos y promociones están destacados o tienen una característica especial. |
+| **rateandbenefitsidentifiers_description** | character varying(65535) | Descripción detallada de los identificadores de cargos y promociones, explicando sus recursos o beneficios. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+
+## Tabla orders_payments
+
+La tabla `payments` registra los detalles de los medios de pago utilizados.   Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. Suele estar unido a la columna 'orderid' de la tabla 'vtex.orders_latest'. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido, indicando el servidor o dominio que gestiona el pedido. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación realizada en el pedido, que refleja la actualización más reciente de status o contenido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **transactions_merchantname** | character varying(65535) | Nombre del retailer asociado a la transacción del pedido. |
+| **group** | character varying(65535) | Grupo o categoría a la que pertenece el pedido o elemento. |
+| **installments** | integer | Número de cuotas para el pago del pedido. |
+| **value** | double precision | Valor monetario asociado a la transacción o elemento del pedido. |
+| **transactions_paymentsystemname** | character varying(65535) | Nombre del sistema de pago utilizado en la transacción. |
+| **transactions_paymentsystem** | character varying(65535) | Identificador del sistema de pago utilizado en la transacción. |
+| **giftcards_id** | character varying(65535) | Identificador único de la tarjeta de regalo utilizada en el pedido. |
+| **giftcards_name** | character varying(65535) | Nombre de la tarjeta de regalo utilizada. |
+| **giftcards_caption** | character varying(65535) | Descripción o leyenda de la tarjeta de regalo utilizada. |
+| **giftcards_value** | double precision | Valor monetario de la tarjeta de regalo. |
+| **giftcards_balance** | double precision | Saldo remanente en la tarjeta de regalo después de utilizarla. |
+| **giftcards_provider** | character varying(65535) | Proveedor o emisor de la tarjeta de regalo. |
+| **giftcards_groupname** | character varying(65535) | Nombre del grupo o categoría a la que pertenece la tarjeta de regalo. |
+| **giftcards_inuse** | boolean | Indica si la tarjeta de regalo está en uso o ha sido utilizada en el pedido. |
+| **giftcards_isspecialcard** | boolean | Indica si la tarjeta de regalo es especial o promocional. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+| **transactions_transactionid** | character varying(65535) | Identificador único de la transacción financiera asociada al pedido. |
+| **transactions_referencevalue** | double precision | Valor de referencia de la transacción. Puede reflejar el valor total antes de descuentos o cargos. |  
+
+## Tabla orders_packages  
+
+La tabla `packages` almacena información sobre embalaje y envío de productos.   
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido, indicando el servidor o dominio que lo gestiona. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora del último cambio realizado en el pedido, que refleja la actualización más reciente de status o contenido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **courier** | character varying(65535) | Nombre de la empresa transportadora o del servicio de envío asociado al pedido. |
+| **invoicenumber** | character varying(65535) | Número de factura asociado al pedido. |
+| **invoicevalue** | double precision | Valor total indicado en la factura del pedido. |
+| **invoiceurl** | character varying(65535) | URL para acceder a la factura electrónica del pedido. |
+| **issuancedate** | timestamp with time zone | Fecha de emisión de la factura del pedido. |
+| **trackingnumber** | character varying(65535) | Número de seguimiento asociado al envío del pedido. |
+| **invoicekey** | character varying(65535) | Clave única que identifica la factura del pedido. |
+| **trackingurl** | character varying(65535) | URL para el seguimiento del envío del pedido. |
+| **embeddedinvoice** | character varying(65535) | Información insertada o detalles de la factura del pedido. |
+| **type** | character varying(65535) | Tipo o categoría del elemento o servicio asociado al pedido. |
+| **courierstatus_delivereddate** | timestamp with time zone | Fecha de envío del pedido registrada por el servicio de la transportadora. |
+| **courierstatus_status** | character varying(65535) | Status actual del envío registrado por el servicio de la transportadora. |
+| **courierstatus_finished** | boolean | Indica si se ha completado el proceso de envío. |
+| **courierstatus_data** | super | Datos detallados sobre el status de envío facilitados por el servicio de la transportadora. |
+| **cfop** | character varying(65535) | Código Fiscal de Operações e Prestações (CFOP) asociado a la transacción del pedido en Brasil. |
+| **packages_lastchange** | timestamp with time zone | Fecha y hora de la última modificación registrada en los paquetes del pedido. |
+| **volumes** | integer | Número total de paquetes en el pedido. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+
+## Tabla orders_items  
+
+La tabla `items` almacena detalles de ítems individuales en cada pedido, incluyendo SKU, cantidad, precio y descuentos.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **orderid** | character varying(16383) | Identificador único para cada pedido. Suele estar unido a la columna 'orderid' de la tabla 'vtex.orders_latest'. |
+| **hostname** | character varying(16383) | Nombre del host asociado al pedido; suele estar unido a columnas de otras tablas como 'vtex.client_registry_gold.hostname'. |
+| **creationdate** | timestamp with time zone | Fecha y hora de creación del pedido, incluida la zona horaria. |
+| **lastchange** | timestamp with time zone | Fecha y hora de la última modificación realizada en el pedido. |
+| **status** | character varying(16383) | Status actual del pedido. |
+| **tax** | double precision | Valor del impuesto aplicado al pedido. |
+| **id** | character varying(65535) | Identificador único; suele estar unido a 'sku_id' de la tabla 'vtex.fulfilment_simulations_ca_silver'. |
+| **productid** | character varying(65535) | Identificador del producto asociado al pedido. |
+| **quantity** | integer | Cantidad del producto en el pedido. |
+| **seller** | character varying(65535) | Identificador o nombre del seller del producto. |
+| **sellersku** | character varying(65535) | SKU del producto como figura en la lista del seller. |
+| **pricevaliduntil** | timestamp with time zone | Fecha y hora de vigencia del precio del producto. |
+| **name** | character varying(65535) | Nombre del producto. |
+| **additionalinfo_brandname** | character varying(65535) | Marca del producto. |
+| **additionalinfo_brandid** | character varying(65535) | Identificador de la marca del producto. |
+| **additionalinfo_caregoriesid** | character varying(65535) | Identificadores de las categorías asociadas al producto. |
+| **additionalinfo_dimension_cubicweight** | double precision | Peso cúbico del producto a efectos de envío. |
+| **additionalinfo_dimension_height** | double precision | Altura del producto. |
+| **additionalinfo_dimension_length** | double precision | Longitud del producto. |
+| **peso_dimension_adicional** | double precision | Peso del producto. |
+| **additionalinfo_dimension_width** | double precision | Anchura del producto. |
+| **price** | double precision | Precio del producto. |
+| **pricetags** | super | Tags de precios asociados al producto. Pueden incluir descuentos y ofertas. |
+| **sellingprice** | double precision | Precio de venta del producto. |
+| **listprice** | double precision | Precio de lista del producto. |
+| **imageurl** | character varying(65535) | URL de la imagen del producto. |
+| **unidad de medida** | character varying(65535) | Unidad de medida del producto. |
+| **unitmultiplier** | double precision | Multiplicador unitario del producto, utilizado en cálculos de precio y cantidad. |
+| **batch_id** | character varying(13) | Identificador referente a la carga de datos en la tabla para control de calidad de la ingesta de datos. |
+
+## Análisis con datos de pedidos  
+
+Los datos de los pedidos pueden utilizarse en los siguientes análisis:  
+
+- **Análisis de ventas de ecommerce:** evaluar volumen de ventas, identificar productos más vendidos, analizar tendencias estacionales y comprender el comportamiento de los consumidores.  
+- **Análisis de la tasa de cancelación de pedidos:** investigar los motivos de las cancelaciones, identificar patrones relacionados con productos específicos o problemas logísticos y desarrollar estrategias para reducir las tasas de cancelación.  
+- **Desempeño de SKU**: analizar el desempeño de SKU individuales, comprender la demanda del mercado y realizar ajustes en el stock y en las estrategias de marketing.  
+
+## Correlaciones con otros datos  
+
+El conjunto de datos de pedidos se correlaciona con los siguientes conjuntos del ecosistema de datos de VTEX:  
+
+- **Navegación:** los datos de navegación pueden correlacionarse con los pedidos para analizar el comportamiento del consumidor y la jornada de compra, lo que ayuda a optimizar la experiencia del usuario.  
+- **Promociones:** la interacción con datos de promociones es fundamental para evaluar la eficacia de las campañas promocionales en el volumen y tipos de pedidos.  
+- **Transacciones:** el análisis conjunto con datos de transacciones puede revelar patrones de pago, preferencias de los consumidores y eficiencia en el procesamiento de pagos.  
+
+### Descubra otros conjuntos de datos
+
+- [Stock](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Precios](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promociones](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
+
diff --git a/docs/tutorials/es/overview-of-b2b-orders-history.md b/docs/tutorials/es/overview-of-b2b-orders-history.md
new file mode 100644
index 000000000..5d64bd3a7
--- /dev/null
+++ b/docs/tutorials/es/overview-of-b2b-orders-history.md
@@ -0,0 +1,31 @@
+---
+title: 'Vista general de B2B Orders History'
+id: C2i93MZmjSrqhEx16YYuA
+status: PUBLISHED
+createdAt: 2024-07-26T13:17:45.094Z
+updatedAt: 2024-07-26T14:02:09.115Z
+publishedAt: 2024-07-26T14:02:09.115Z
+firstPublishedAt: 2024-07-26T14:02:09.115Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: vista-general-de-b2b-orders-history
+locale: es
+legacySlug: vista-general-de-b2b-orders-history
+subcategory: 2LaAukjQB4QEbqSYdgjq7l
+---
+
+En una [operación B2B](https://help.vtex.com/es/tutorial/b2b-visao-geral--5vb9SNXhX2bZnkpAh7ADdC), varios usuarios de una misma organización realizan pedidos en nombre de la empresa. La aplicación **B2B Orders History** atiende estas necesidades específicas, permitiendo que los usuarios vean y gestionen pedidos de forma integrada y colaborativa.
+
+## Funcionalidad
+La aplicación **B2B Orders History** sustituye la página Pedidos predeterminada en [Mi cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) con una versión más adaptada al entorno B2B. Esta personalización permite que los [usuarios](https://help.vtex.com/es/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA) de una organización que hayan iniciado sesión, además de ver sus propios pedidos, también tengan acceso a los pedidos realizados por otros miembros de la misma organización o centro de costo, siempre y cuando tengan los permisos necesarios.
+
+## Beneficios
+La vista centralizada de pedidos ese importante para:
+
+- Permitir que todos los miembros autorizados de la organización den seguimiento a los pedidos realizados para evitar duplicados y errores.
+- Facilitar la gestión de compras, garantizando que todas las adquisiciones cumplan las políticas de la empresa.
+- Facilitar un acceso rápido y sencillo a los pedidos para optimizar la eficiencia operativa y agilizar la toma de decisiones.
+
+Para más información, accede a [B2B Orders History](https://developers.vtex.com/docs/apps/vtex.b2b-orders-history).
+
diff --git a/docs/tutorials/es/overview-pricing-module.md b/docs/tutorials/es/overview-pricing-module.md
index 2f27d5dc4..5976d4771 100644
--- a/docs/tutorials/es/overview-pricing-module.md
+++ b/docs/tutorials/es/overview-pricing-module.md
@@ -21,7 +21,7 @@ Hay tres departamentos dentro del módulo que son responsables de la configuraci
 
 ## Audiencia de Campañas
 
-![campanha-es](https://images.ctfassets.net/alneenqid6w5/78eGGuLQ9U5X8nJd21K46T/16b42ea9ae089696a8fab6986cf078ee/campanha-es.png)
+![campanha-es](//images.ctfassets.net/alneenqid6w5/78eGGuLQ9U5X8nJd21K46T/16b42ea9ae089696a8fab6986cf078ee/campanha-es.png)
 
 La audiencia de campañas es una forma de definir el público objetivo al que una promoción puede ser aplicada. Es decir, usted puede crear segmentos de clientes basados en la definición de algunos criterios que serán elegibles para una determinada audiencia de campaña y consecuentemente a una o más promociones. Una audiencia de campaña puede asociarse a una o más [promociones de audiencias de campañas](https:///tutorial/promocao-de-campanha?locale=es "Crear promoción de campaña").
 
@@ -29,7 +29,7 @@ La audiencia de campañas es una forma de definir el público objetivo al que un
 
 ## Promociones
 
-![promoções.es](https://images.ctfassets.net/alneenqid6w5/1zFONiDeeUvKA1Cyj5zY1c/dc438c0f2f3a786b3efceb8665ecde57/promo____es.es.png)
+![promoções.es](//images.ctfassets.net/alneenqid6w5/1zFONiDeeUvKA1Cyj5zY1c/dc438c0f2f3a786b3efceb8665ecde57/promo____es.es.png)
 
 Aquí es donde los descuentos que su tienda va a ofrecer se crean. Usted también puede ver, filtrar, buscar y archivar todas las promociones. De acuerdo con la configuración de cada tienda, existe un límite de promociones que pueden estar activas al mismo tiempo. 
 
@@ -44,12 +44,12 @@ Para comprobar esta cantidad, observe el mensaje que aparece en la esquina super
 
 ## Cupones
 
-![cupons.es](https://images.ctfassets.net/alneenqid6w5/6DMoadJ7T4npiiWir48bCQ/ce25ad3832e5098993ed05eb06cb7d84/cupons.es.png)
+![cupons.es](//images.ctfassets.net/alneenqid6w5/6DMoadJ7T4npiiWir48bCQ/ce25ad3832e5098993ed05eb06cb7d84/cupons.es.png)
 
 Es en esta sección que se crean los cupones. Usted también puede recogerlos y archivarlos. [Aprenda cómo crear cupones](/es/tutorial/crear-cupon-de-descuento).
 
 ## Impuestos
 
-![taxas.es](https://images.ctfassets.net/alneenqid6w5/2pHx00EwpCj3fatVpnfPui/83121098980fd0f608d9d808a4acd417/taxas.es.png)
+![taxas.es](//images.ctfassets.net/alneenqid6w5/2pHx00EwpCj3fatVpnfPui/83121098980fd0f608d9d808a4acd417/taxas.es.png)
 
 En esta área se crearán los impuestos que inciden sobre sus productos. También se permite filtrar, buscar y archivar las tasas. [Entienda mejor las particularidades de esta configuración en el artículo sobre tasas](/es/tutorial/creando-la-tasaimpuesto).
diff --git a/docs/tutorials/es/pages-overview.md b/docs/tutorials/es/pages-overview.md
index 3ab0431ba..640011cd1 100644
--- a/docs/tutorials/es/pages-overview.md
+++ b/docs/tutorials/es/pages-overview.md
@@ -25,7 +25,7 @@ En Páginas, también puedes crear redirecciones de URL para redirigir a los vis
 
 En el Admin VTEX, accede **Storefront > Páginas** y descubre las principales herramientas disponibles en la interfaz.
 
-![Páginas UI - ES](https://images.ctfassets.net/alneenqid6w5/p6829cewqlsLC0XfCnHsC/dc75d5dcbe1d3ff9d02d710718961fba/pages-ui-es.png)
+![Páginas UI - ES](//images.ctfassets.net/alneenqid6w5/p6829cewqlsLC0XfCnHsC/dc75d5dcbe1d3ff9d02d710718961fba/pages-ui-es.png)
 
 | **Herramienta** | **Descripción** |
 | ---------- | ---------- |
diff --git a/docs/tutorials/es/payment-provider-protocol.md b/docs/tutorials/es/payment-provider-protocol.md
index 4b8536a9c..0f1a03705 100644
--- a/docs/tutorials/es/payment-provider-protocol.md
+++ b/docs/tutorials/es/payment-provider-protocol.md
@@ -3,8 +3,8 @@ title: 'Payment Provider Protocol '
 id: RdsT2spdq80MMwwOeEq0m
 status: PUBLISHED
 createdAt: 2018-01-02T15:40:00.920Z
-updatedAt: 2023-05-31T14:44:41.300Z
-publishedAt: 2023-05-31T14:44:41.300Z
+updatedAt: 2024-07-24T13:58:10.009Z
+publishedAt: 2024-07-24T13:58:10.009Z
 firstPublishedAt: 2018-01-02T17:53:48.934Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,6 @@ legacySlug: payment-provider-protocol
 subcategory: 2Xay1NOZKE2CSqKMwckOm8
 ---
 
-## ¿Qué es el Payment Provider Protocol?
 Payment Provider Protocol es el protocolo de integración entre VTEX y otras empresas que procesan pagos.
 
 Por medio de él, VTEX ofrece un contrato público disponible para todos los proveedores que desean integrarse a nuestra plataforma. Así, los proveedores obtienen mayor autonomía en relación a la integración.
@@ -43,9 +42,10 @@ __Oauth:__ protocolo de autorización para API web diseñado para permitir que l
 __Adquirente:__ empresa especializada en procesar pagos. Se encarga de transferir a la cuenta de tu tienda los valores cobrados al cliente por el banco emisor.
 
 ## Requisitos previos
+
 ### Firma de un contrato de asociación comercial para servicios financieros
 
-Para implementación, publicación y actualización de un conector de pagos en VTEX se requiere celebrar un contrato de asociación __específico para servicios financieros__ que cubra los detalles del tema y las regulaciones dentro de la plataforma. Si aún no tienes un acuerdo de colaboración, pero estás interesado en convertirte en proveedor de pagos, ponte en contacto con nuestro equipo a través de nuestro [sitio web](https://vtex.com/es-es/partner/).
+La implementación, publicación y actualización de un conector de pagos en VTEX requiere la celebración un contrato de asociación específico para servicios financieros que cubra los detalles del tema y las regulaciones dentro de la plataforma. Si aún no tienes un contrato de colaboración, pero estás interesado en convertirte en proveedor de pagos, ponte en contacto con nuestro equipo a través de nuestro [sitio web](https://vtex.com/ar-es/partner).
 
 ### Acceso a un entorno VTEX
 
@@ -59,7 +59,7 @@ Si el _partner_ es un SI (Service Implementer) que desarrolla integraciones para
 Para ser un proveedor VTEX integrado, debes usar una de las siguientes soluciones:
 
 - La infraestructura donde estará el conector debe contar con un certificado PCI-DSS firmado por un asesor de seguridad calificado o QSA (Qualified Security Assessor, por sus siglas en inglés). Más información sobre el [Consejo de normas de seguridad de PCI](https://www.pcisecuritystandards.org/).
-- Si no tienes el certificado, puedes implementar al proveedor usando el [Secure Proxy](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-secure-proxy).
+- Si no tienes el certificado, puedes implementar al proveedor usando el [Secure Proxy](https://developers.vtex.com/docs/guides/payments-integration-secure-proxy).
 
 Si el proveedor se ha certificado o ha iniciado el proceso de certificación, puede ponerse en contacto con el equipo comercial de VTEX para iniciar la integración.
 
@@ -74,7 +74,7 @@ Los documentos SAQ (Self-Assessment Questionnaire) y AOC (Attestation of Complia
 </div>
 <br>
 
-#### Proveedores de pagos offline o tarjeta private label (o tarjetas en general, pero que implican soluciones con redirect
+#### Proveedores de pagos offline o tarjeta private label (o tarjetas en general), pero que implican soluciones con redirect
 
 Para estes tipo de proveedores, VTEX no requiere comprobación de certificación PCI DSS. Sólo tienes que ponerse en contacto con el equipo comercial de VTEX para iniciar la integración.
 
@@ -87,110 +87,113 @@ Antes de configurar el ambiente VTEX, el proveedor debe implementar el servicio
 ### 2. Casos de uso específicos
 Hay casos en que se pueden crear conectores para atender alguna solución específica. A continuación, se presentan las referencias de nuestra documentación que contienen información sobre estos casos:
 
-- [Payment Provider Framework (PPF)](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework): es una solución para la implementación de conectores a través de VTEX IO con base en un _boilerplate_. El _boilerplate_ ya viene con una gran parte del trabajo realizado, incluyendo los _endpoints_ del protocolo. La utilización de VTEX IO también acelera el proceso de desarrollo y pruebas de la tienda.
+- [Payment Provider Framework (PPF)](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework): es una solución para la implementación de conectores a través de VTEX IO con base en un _boilerplate_. El _boilerplate_ ya viene con una gran parte del trabajo realizado, incluyendo los _endpoints_ del protocolo. La utilización de VTEX IO también acelera el proceso de desarrollo y pruebas de la tienda.
 
-- [Payment Provider Protocol (PPP) aplicado a los pagos con POS](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-ppp-applied-to-pos): es la aplicación del PPP a pagos en tiendas físicas utilizando un terminal de pago (POS). Se puede utilizar con tarjetas de crédito o débito. El flujo del pago se inicia con una compra realizada en [inStore](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf), después de lo cual se establece la comunicación con el POS, donde el cliente inserta la tarjeta.
+- [Payment Provider Protocol (PPP) aplicado a los pagos con POS](https://developers.vtex.com/docs/guides/payments-integration-ppp-applied-to-pos): es la aplicación del PPP a pagos en tiendas físicas utilizando un terminal de pago (POS). Se puede utilizar con tarjetas de crédito o débito. El flujo del pago se inicia con una compra realizada en [inStore](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf), después de lo cual se establece la comunicación con el POS, donde el cliente inserta la tarjeta.
 
 ### 3. Homologación de Payment Provider
-Después de recibir los datos de acceso e implementar el back-end, el proveedor debe instalar la aplicación Payment Provider Test Suite para acceder a la herramienta de pruebas. La instalación se hace en [VTEX App Store](https://apps.vtex.com/vtex-payment-provider-test-suite/p "VTEX App Store.").
 
-![print1](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d9d72ca9a6fa585f959fa932412930d7/print1.png)
+Después de recibir los datos de acceso e implementar el backend, el proveedor debe instalar la aplicación Payment Provider Test Suite para acceder a la herramienta de pruebas. La instalación se realiza a través de la VTEX App Store.
+
+![ppp-vtex-store-es](//images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/aa2d1e30c83c7d35c7313c112a5b69d1/image.png)
 
 <div class="alert alert-warning">
-Toda comunicación con los servidores, tanto durante el proceso de homologación como en producción, debe ocurrir vía HTTPS que por defecto usa el puerto 443. Es importante recordar que toda la comunicación HTTPS debe ser exclusivamente sobre <strong>TLS 1.2</strong>.
+<p>
+Para completar el proceso de homologación, se debe implementar una lógica específica para abordar los requisitos de la prueba. En los requests enviados a Test Suite, utiliza el encabezado adicional <code>X-VTEX-API-Is-TestSuite = true</code> para identificarlos y enmascarar cualquier escenario requerido.<br><br> Toda comunicación con los servidores, ya sea durante el proceso de homologación o en producción, debe llevarse a cabo a través de HTTPS, que utiliza el puerto 443 de forma predeterminada. Es importante recordar que toda comunicación HTTPS debe usar exclusivamente TLS 1.2.
+</p>
 </div> 
 
-Después de la instalación, basta con verificar el módulo Otros en el menú lateral de la izquierda del  Admin. Luego, seleccione la opción Payment Provider para configurarla correctamente.
+<!-----
 
-De esta manera, usted verá dos formularios: Service Information y Tests.
+Yay, no errors, warnings, or alerts!
 
-Rellene los campos de cada uno de acuerdo con las siguientes indicaciones:
+Conversion time: 0.518 seconds.
 
-#### Service Information
-- __Service URL__: defina la URL de su proveedor de servicios. Esta URL será la dirección base del protocolo y debe seguir el formato determinado por este. Por ejemplo, si la URL del servicio es *http://10.10.10.10*, la URL completa para el endpoint */payments* será *http://10.10.10.10/payments*.
-- __Connector Name__: rellene el nombre que desea dar a su conector dentro de VTEX. Señalamos que el nombre apenas puede contener letras minúsculas, números y guión. 
-- __X-VTEX-API-AppKey__: introduzca el valor "PROVIDER-API-AppKey" del header del request de su proveedor para fines de prueba.
-- __X-VTEX-API-AppToken__: introduzca el valor de "PROVIDER-API-AppToken" del header del request de su proveedor para fines de prueba.
+Using this Markdown file:
 
-<div class="alert alert-warning">
-  Su proveedor debe esperar los headers: <strong>X-VTEX-API-AppKey</strong> y <strong>X-VTEX-API-AppToken</strong>. Estas combinaciones son las credenciales que identifican al administrador de la tienda. El gateway almacena las credenciales de los administradores de las tiendas y otros parámetros que se usan en la configuración de la afiliación, los cuales se enviarán al proveedor en las transacciones.
-</div>
+1. Paste this output into your source file.
+2. See the notes and action items below regarding this conversion run.
+3. Check the rendered output (headings, lists, code blocks, tables) for proper
+   formatting and use a linkchecker before you publish this page.
 
-![Payment Provider Test Suite 0](https://images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
+Conversion notes:
 
-#### Tests
+* Docs to Markdown version 1.0β34
+* Fri Jun 30 2023 14:24:00 GMT-0700 (PDT)
+* Source doc: [EDU-8223] Atualizações do Test Suite
+* This is a partial selection. Check to make sure intra-doc links work.
+----->
 
-Después de revisar todos los campos, haga clic en el botón __CHECK URL__.
+Tras la instalación, haz clic en Apps, en el panel lateral izquierdo del Admin. A continuación, selecciona la aplicación Payment Provider Test Suite para configurarla correctamente.
 
-El sistema verificará los métodos de pago por medio de una llamada al endpoint __/manifest__ de su proveedor. Vea la referencia de la API [aquí](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#get-/manifest).
+Dependiendo de la versión del Admin utilizada en la cuenta de la tienda, la aplicación estará disponible en la lista de aplicaciones. Para acceder a ella, utiliza la dirección [https://{{accountName}}.myvtex.com/admin/test-suite](about:blank)/payment-provider, sustituyendo {{accountName}} por el nombre de cuenta de tu tienda.
 
-Tras la llamada, se identificarán los endpoints de las operaciones disponibles en el proveedor y se habilitarán automáticamente las pruebas respectivas de cada operación.
+Luego, verás un formulario que tiene tres secciones: Información de servicio, Medio de pago y Casos de prueba. Rellena los campos según las instrucciones a continuación.
 
-Puedes seleccionar qué pruebas realizar, pero  para que nuestro equipo apruebe el análisis de la integración, __se deben realizar todas las pruebas habilitadas automáticamente__. Por lo tanto, recomendamos que se mantengan seleccionadas todas las pruebas.
+#### Información de servicio
 
-![Payment Provider Test Suite 1](https://images.ctfassets.net/alneenqid6w5/5LROAprSeFd1O64M2WCisC/af4e2408feb2d1e5dfb9b9bac7067f6d/Payment_Provider_Test_Suite_1.jpg)
+* **URL de servicio:** define la URL del servicio de tu proveedor. Esta URL será la dirección base del protocolo y debe seguir el formato determinado por el proveedor. Por ejemplo, si la URL del servicio es [https://example.com/](https://example.com/), la URL completa del endpoint /payments será [https://example.com/payments](https://example.com/payments).
+* **Clave de aplicación y token de aplicación:** el botón de alternancia con clave de aplicación y token de aplicación te permite escoger si se configuran estos campos o no, lo que puede facilitar las pruebas durante la etapa de desarrollo. Si no se activa esta opción, las credenciales se enviarán en los encabezados como una string vacía.
 
-### 4. Pruebas
-Al hacer clic en el botón __RUN TESTS__, el proveedor de pagos aplicará las pruebas en su integración para los diferentes escenarios posibles. Es importante recordar que, para ejecutarlas, su servicio debe estar en HTTPS. Las pruebas son:
+<div class="alert alert-info">
+  <p>
+El gateway almacena las credenciales de las tiendas configuradas en la afiliación y las envía en los encabezados X-VTEX-API-AppKey y X-VTEX-API-AppToken. La excepción son las integraciones desarrolladas con VTEX IO, en cuyo caso, los encabezados se envían como x-provider-api-appKey y x-provider-api-appToken. Si estás desarrollando usando <a href="https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework">Payment Provider Framework (IO)</a>, esto lo define la opción usesProviderHeadersName. Consulta los ajustes disponibles <a href="https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework#available-configurable-options">aquí</a>.
+</p>
+  </div>
 
-- __Authorize__: esta prueba se divide en tres etapas. En la primera, enviamos un pedido de _Create Payments_ a `{{ServiceURL}}/payments`, esperando como respuesta el status _approved_. En la segunda, un request de _Settle Payment_ se envía a `/payments/{PAYMENT_ID}/settlements` y esperamos una respuesta con el _settleId_ rellenado. Por último, enviamos un request de _Refund Payment_ a `/payments/{PAYMENT_ID}/refunds`, esperando una respuesta con _refundId_ rellenado.
+#### Medio de pago
 
-- __Denied__: En esta prueba, enviamos un pedido de _Create Payments_ a `{{SERVICEURL}}/payments`, esperando como respuesta el status _denied_.
+Después de rellenar URL de servicio, Test Suite validará el  [Endpoint Manifest](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#get-/manifest) y verificará los medios de pago declarados, que aparecerán en este campo. Selecciona los medios de pago en los que deseas ejecutar las pruebas.
 
-- __Cancel__: para esta prueba, primero necesitamos el status _approved_ como respuesta al request de _Create Payments_ a `{{ServiceURL}}/payments`. Luego enviamos un request de _Cancel Payment_ a `/payments/{PAYMENT_ID}/cancellations` y esperamos una respuesta con el status _cancelled_.
+#### Casos de prueba
 
-- __AsyncApproved__: esta prueba se divide en dos etapas. En la primera, enviamos un pedido de _Create Payments_ a `{{ServiceURL}}/payments`, esperando como respuesta el status _undefined_. Entonces, esperamos recibir en hasta 15 segundos la misma respuesta, pero con status _approved_ en un POST en la URL enviada en el campo _callbackUrl_. Una vez que la integración está en producción, esta última llamada hecha por callbackUrl se autentifica con las claves del ambiente del socio: _vtex-app-key_ y _vtex-app-token_.
+En esta sección, debes seleccionar los casos que deseas probar. Si estás probando un medio de tarjeta de crédito, tu integración debe pasar los casos Aprobado, Denegado, Cancelación, Aprobado asíncrono y Denegado asíncrono. Los medios de pago con [redirección](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows#redirect) solo necesitan el Flujo de redirección.
 
-- __AsyncDenied__: a ejemplo del anterior, esta prueba también se divide en dos etapas. En la primera, enviamos un pedido de _Create Payments_ a `{{ServiceURL}}/payments`, esperando como respuesta el status _undefined_. Entonces, esperamos recibir en hasta 15 segundos la misma respuesta, pero con status _denied_ en un POST en la URL enviada en el campo _callbackUrl_. Una vez que la integración está en producción, esta última llamada hecha por callbackUrl se autentifica con las claves del ambiente del socio: _vtex-app-key_ y _vtex-app-token_.
+![ppp-config-es](//images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/f15364fc9a837883d8d1f022fe646014/image.png)
 
-- __BankInvoice__: En esta prueba, enviamos un request de _Create Payments_ a `{{SERVICE}}/paid`, esperando que la respuesta venga con el status _undefined_ y el campo `bankIssueInvoiceUrl` venga rellenado con la URL del boleto. Después, esperamos recibir en hasta 15 segundos la misma respuesta, pero con status _approved_ en un POST en la URL enviada en el campo _callbackUrl_. Cuando la integración está en producción, esta última llamada hecha por callbackUrl será autenticada con las claves del ambiente del socio: _vtex-app-key_ y _vtex-app-token_.
+### 4. Pruebas
+Cuando haces clic en el botón `Ejecutar prueba`, Test Suite llama la URL de servicio proporcionada y ejecuta los casos de prueba seleccionados. Las pruebas son:
 
-- __Redirect__: esta prueba se divide en dos etapas. En la primera, enviamos una petición de _Create Payments_ a `{{ServiceURL}}/payments`, esperando que la respuesta venga con el status _undefined_ y el campo `redirectUrl` sea rellenado con la URL que va a ser usada para redirigir el cliente. Entonces, esperamos recibir en hasta 15 segundos la misma respuesta, pero con status _approved_ en un POST en la URL enviada en el campo _callbackUrl_. Cuando la integración está en producción, esta última llamada hecha por callbackUrl será autenticada con las claves del ambiente del socio: _vtex-app-key_ y _vtex-app-token_. Para el conector que usará Redirect, no es necesario pasar todas las pruebas de Test Suit, solo la Redirect.
+* **Flujo aprobado:** esta prueba se divide en tres etapas. En la primera, se envía un request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera el status aprobado como respuesta. En la segunda, se envía un request [Settle Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/settlements) a {{ServiceURL}}/payments/{paymentId}/settlements y se espera la respuesta con el settleId rellenado. Y en la última, se envía un request [Refund Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/refunds) a {{ServiceURL}}/payments/{paymentId}/refunds y se espera una respuesta con refundId rellenado.
+* **Flujo denegado:** en esta prueba, se envía un request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera el status denegado como respuesta.
+* **Flujo de cancelación:** para esta prueba, primero se necesita el status approved como respuesta del request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) de {{ServiceURL}}/payments. Luego, se envía un request [Cancel Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/cancellations) a {{ServiceURL}}/payments/{paymentId}/cancellations y se espera una respuesta con el status cancelado.
+* **Flujo aprobado asíncrono:** esta prueba se divide en dos pasos. Primero, se envía un request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera el status undefined como respuesta. Después de 15 segundos, se espera otra respuesta en el mismo formato mediante un POST de la URL enviada en el campo callbackUrl y con el status approved. Con la integración en producción, esta última llamada realizada por callbackUrl se autentica con las claves de entorno del partner: vtex-app-key y vtex-app-token. Para más información sobre el flujo de callback consulta la sección [Autorización del pago](#autorizacion-de-pago).
+* **Flujo denegado asíncrono:** como la anterior, esta prueba se divide en dos pasos. Primero, se envía un request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera el status undefined como respuesta. Después de 15 segundos, se espera otra respuesta en el mismo formato mediante un POST de la URL enviada en el campo callbackUrl y con el status denied. Con la integración producción, esta última llamada realizada por callbackUrl se autentica con las claves de entorno del partner: vtex-app-key y vtex-app-token. Para más información sobre el flujo de callback consulta la sección [Autorización del pago](#autorizacion-de-pago).
+* **Flujo de boleto:** en esta prueba, se envía un request[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera una respuesta con status undefined y el campo `bankIssueInvoiceUrl` rellenado con la URL del ticket. Después de 15 segundos, se espera otra respuesta en el mismo formato mediante un POST de la URL enviada en el campo callbackUrl y con el status approved. Con la integración en producción, esta última llamada realizada por callbackUrl se autentica con las claves de entorno del partner: vtex-app-key y vtex-app-token. Para más información sobre el flujo de callback consulta la sección [Autorización del pago](#autorizacion-de-pago).
+* **Flujo de redirección:** esta prueba se divide en dos pasos. Primero, se envía un request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera una respuesta con status undefined y el campo redirectUrl rellenado con la URL que se utilizará para redirigir al cliente. Después de 15 segundos, se espera otra respuesta en el mismo formato mediante un POST de la URL enviada en el campo callbackUrl y con el status approved. Con la integración en producción, esta última llamada realizada por callbackUrl se autentica con las claves de entorno del partner: vtex-app-key y vtex-app-token. Para más información sobre el flujo de callback consulta la sección [Autorización del pago](#autorizacion-de-pago). El conector que utilizará redirección no tiene que pasar todas las pruebas de Test Suite, solo la prueba de Redirección.
 
 <div class="alert alert-warning">
-En el caso de las tarjetas de crédito, las pruebas obligatorias son: <strong>Authorize</strong>, <strong>Denied</strong>, <strong>Cancel</strong>, <strong>AsyncApproved</strong> y <strong>AsyncDenied</strong>.
-</div>
+  En el caso de las tarjetas de crédito, las pruebas obligatorias son: Autorizar, Denegado, Cancelar, Aprobado asíncrono y Denegado asíncrono.
+  </div>
 
-<div class="alert alert-info">
-Para cada prueba con tarjetas de crédito, enviamos un número específico para devolver la respuesta esperada. Son ellos:<br>
-<strong>Respuesta con status approved:</strong> tarjeta numero 4444333322221111<br>
-<strong>Respuesta con status denied:</strong> tarjeta numero 4444333322221112<br>
-<strong>Respuesta con status undefined y retorno en el callbackUrl con status approved:</strong> tarjeta numero 4222222222222224<br>
-<strong>Respuesta con status undefined y retorno en callbackUrl con status denied:</strong> tarjeta numero 4222222222222225<br>
-</div>
+Para identificar cómo responder a cada una de las pruebas con tarjetas de crédito, utiliza los siguientes números específicos:
 
-### 5. Resultados
-Después de ejecutar las pruebas, el sistema devuelve los resultados, tanto positivos como negativos. El sistema también trae la información de los resultados esperados para cada prueba. Así, usted tiene más visibilidad de lo que debe ser ajustado en caso de error.
+| Número de tarjeta | Status de la respuesta                     |
+| ----------------- | ------------------------------------------ |
+| 4444333322221111  | __approved__                                   |
+| 4444333322221112  | __denied__                                     |
+| 4222222222222224  | __undefined__, `callbackUrl` con status __approved__ |
+| 4222222222222225  | __undefined__, `callbackUrl` con status __denied__   |
 
-![Payment Provider Test Suite 2](https://images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/38e5f5d1391d10ca831eba5682c5544b/Payment_Provider_Test_Suite_2.jpg)
-
-Para visualizar de forma detallada cada acción realizada por la integración (y, así, identificar posibles errores), basta con hacer clic en el botón __TRY LOADING AGAIN?__. Una lista con la información completa de los eventos que ocurrieron durante la prueba se mostrará por debajo de los resultados.
+### 5. Resultados
 
-![Payment Provider Test Suite Logs](https://images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/12a0a237d1c8725b8eeb9bb61eb48fbc/Payment_Provider_Test_Suite_Logs.jpg)
+Después de ejecutar las pruebas, el sistema mostrará el Informe de prueba que presenta los resultados detallados de cada caso de prueba. De este modo, tendrás más visibilidad sobre lo que debes ajustar si se produce un error.
 
-![Payment Provider Test Suite 3](https://images.ctfassets.net/alneenqid6w5/7svc9sEJaMiwsYK0ykU0SS/590453ef17cda1dab3b1bb4342f1d9d1/Payment_Provider_Test_Suite_3.jpg)
+![Payment Provider Test Suite 2_ES](//images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/6d5d097d5f50587f6a69d8932a81f78f/Payment_Provider_Test_Suite_2_ES.JPG)
 
-Cuando su integración ha pasado todas las pruebas con éxito, sólo tiene que abrir un ticket en el [help de VTEX](/es/support "VTEX Help") informando la conclusión. Sin embargo, antes de abrir el ticket, asegúrese de tener la siguiente información:
+Para ver los mensajes transmitidos entre Test Suite y la implementación de tu proveedor de pagos, haz clic en el botón Inspeccionar logs. Se abrirá una ventana modal que muestra la lista de mensajes transmitidos y la carga de cada request y respuesta. El botón situado en la esquina superior derecha de la sección de código facilita la copia del código al portapapeles.
 
-- __Connector Name__: una descripción del proveedor. Utilice un máximo de 16 caracteres alfanuméricos. Este nombre no se puede cambiar una vez publicado.
-- __Partner contact__: correo electrónico del partner en caso de que sea necesario comunicar cambios y novedades de nuestro protocol.
-- __Production Service Provider Endpoint__: la ruta base que se utilizará para las llamadas API al proveedor, por ejemplo, _https://vtex.pagseguro.com_. Debe responder a la ruta `{{serviceUrl}}/manifest`. Este endpoint debe estar disponible públicamente. 
-- __Sandbox Service Provider Endpoint__: la ruta base que se utilizará en el modo de prueba para las llamadas API al proveedor. Por ejemplo: _https://sandboxserviceproviderendpoint.com_. 
-- __Owner account__: el nombre de la cuenta VTEX que se utilizará en las solicitudes de devolución de llamada. Esta cuenta debe estar disponible en _{account}.myvtex.com_. 
-- __Allowed Accounts__: informar qué cuentas VTEX de este proveedor estarán disponibles (todas las cuentas o cuentas específicas).
-- __New Payment methods__: informar si este conector admite un método de pago que aún no está disponible en VTEX Admin. 
-- __New Payment method purchase flow__: si se admite un "Nuevo método de pago", indique si funciona con el Redirect o Payment App. Para más información acceda [Purchase Flows](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-purchase-flows).
-
-<div class="alert alert-warning">
-El SLA requerido para que el equipo de pagos realice la homologación es de 30 días. Este plazo comenzará solo después de la presentación del documento <b>Master Partner Agreement for Financial Services (MPA)</b>. Para las solicitudes de aprobación sin utilizar el MPA, el plazo del SLA puede extenderse debido a la necesidad de un análisis adicional por parte del equipo de pago.
-</div>
+![Payment Provider Test Suite Logs_ES](//images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/9f1a6c56c4c53d51a3e403b4665338dc/Payment_Provider_Test_Suite_Logs_ES.JPG)
 
 ## Flujo del protocolo de pago
 Aquí vamos a explicar el flujo de pago integrado en detalle. La siguiente imagen muestra todo el flujo, mostrando VTEX Payments y las responsabilidades de su proveedor.
 
 Todo comienza con la solicitud de un nuevo pago, después de la creación de un nuevo pedido. VTEX crea una nueva representación del pago y avanza para el procesamiento de los pagos.
 
-![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+![fluxo-atualizado-ppp](//images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+
+<div class="alert alert-info">
+  El período predeterminado de 7 días para reintentos (retries) de pago asíncronos solo se aplica cuando el usuario no especifica un valor en el campo <code>delayToCancel</code> del endpoint <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> o al enviar la URL de devolución de llamada.</div>
 
 ### Autorización de pago
 En este punto, VTEX llama al endpoint __*/payments*__ y envía un payload con los datos de pago para su proveedor. El proveedor debe procesar estos datos y enviar la respuesta, que debe contener uno de los valores de status: __approved__, __denied__ o __undefined__.
@@ -204,7 +207,7 @@ En cualquiera de los casos, una vez que termine el procesamiento y el proveedor
 
 El flujo completo con status undefined y uso de notificación se puede ver a continuación:
 
-![Payment authorization callback notification flow](https://images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/39a8e76973fe6127741c1a34b9230c82/image1.png)
+![Payment authorization callback notification flow](//images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/39a8e76973fe6127741c1a34b9230c82/image1.png)
 
 1. La autorización del pago se inicia cuando el _gateway_ hace una llamada al endpoint Create Payment (__/payment__) para el proveedor. El campo `callbackUrl` se envía dentro del cuerpo del _request_ y contiene la URL para hacer la notificación.
 2. El pago se produce de forma asíncrona (no genera el status definitivo cuando se inicia la transacción). A continuación, el _gateway_ recibe la respuesta con status __undefined__ y espera a que se complete el procesamiento del pago. Más adelante, el pago se completará y el _gateway_ recibirá el status definitivo (__approved__ o __denied__).
@@ -213,7 +216,7 @@ El flujo completo con status undefined y uso de notificación se puede ver a con
 
 El flujo completo con status __undefined__ y uso del __retry__ se puede ver a continuación:
 
-![Payment authorization callback retry flow](https://images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/b78e54e17e7971aa4385f025b8eca4a4/image2.png)
+![Payment authorization callback retry flow](//images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/b78e54e17e7971aa4385f025b8eca4a4/image2.png)
 
 1. La autorización del pago se inicia cuando el _gateway_ hace una llamada al _endpoint_ Create Payment (__/payment__) para el proveedor. El campo `callbackUrl` se envía dentro del cuerpo del _request_ y contiene la URL del endpoint __retry__.
 2. El pago se produce de forma asíncrona (no genera el status definitivo cuando se inicia la transacción). A continuación, el _gateway_ recibe la respuesta con status __undefined__ y espera a que se complete el procesamiento del pago. Más adelante, el pago se completará y el _gateway_ recibirá el status definitivo (__approved__ o __denied__).
@@ -233,6 +236,20 @@ https://gatewayqa.vtexpayments.com.br/api/pvt/payment-provider/transactions/8FB0
 
 En la [página de Transacciones del Admin](https://help.vtex.com/es/tutorial/como-visualizar-detalle-del-pedido--tutorials_452), el token de firma se muestra enmascarado por razones de seguridad, como en este ejemplo: `X-VTEX-signature=Rj******tk`.
 
+Vea a continuación, um ejemplo de payload enviada junto con la callback URL:
+
+```json
+{"paymentId":"8B3BA2F4352545A8B1C5A215F356A01C","status":"approved","authorizationId":"184520","nsu":"21705348","tid":"21705348","acquirer":"pagarme","code":"0000","message":"Transação aprovada com sucesso","delayToAutoSettle":1200, "delayToAutoSettleAfterAntifraud":1200, "delayToCancel":86400,"cardBrand":"Mastercard","firstDigits":"534696","lastDigits":"6921","maxValue":16.6}
+```
+
+<div class="alert alert-info">
+  Los valores de los parámetros enviados en el payload de callback reemplazan los valores originales informados en la llamada de <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a>.  
+</div>
+
+<div class="alert alert-warning">
+  Si los parámetros de tiempo de espera (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) no se envían con la URL de devolución de llamada, los valores se establecerán automáticamente en 24 horas.
+</div>
+
 Al realizar el request de _callback_, recomendamos que los proveedores de pago utilicen la URL de _callback_ exactamente como la recibieron, lo que garantiza que se incluyan todos los parámetros.
 
 Al llamar a CallbackURL, su proveedor debe enviar en el request los headers *X-VTEX-API-AppKey* y *X-VTEX-API-AppToken*. Más información sobre esto en la [sección de credenciales VTEX](/es/tutorial/payment-provider-protocol#credenciales-vtex).
diff --git a/docs/tutorials/es/payments.md b/docs/tutorials/es/payments.md
new file mode 100644
index 000000000..e6e42501c
--- /dev/null
+++ b/docs/tutorials/es/payments.md
@@ -0,0 +1,99 @@
+---
+title: 'Pagos Data Pipeline (Beta)'
+id: 7LWkFaA1jPabzc5JAt1rGs
+status: PUBLISHED
+createdAt: 2024-02-02T17:53:35.949Z
+updatedAt: 2024-06-21T16:28:44.958Z
+publishedAt: 2024-06-21T16:28:44.958Z
+firstPublishedAt: 2024-05-27T19:26:59.478Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: pagos
+locale: es
+legacySlug: pagos
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+El conjunto de datos de pagos se compone de dos tablas principales: `payments_transitions` y `transaction_transitions`.
+
+En esta sección puedes consultar la siguiente información:
+
+- [Características de los datos de pagos](#caracteristicas-de-los-datos)
+- [Tabla payments_transitions](#tabla-payments_transitions)
+- [Tabla transaction_transitions](#tabla-transaction_transitions)
+- [Análisis con datos de pagos](#analisis-con-datos-de-pagos)
+- [Correlaciones con otros datos](#correlaciones-con-otros-datos)
+
+## Características de los datos
+
+|**Característica**|**Descripción**|
+| - | - |
+|**Origen**|Los datos de este conjunto proceden del [módulo Pagos de VTEX](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB). Se recopilan y organizan para reflejar las transacciones y pagos realizados en la plataforma.|
+|**Disponibilidad**|Solo se puede acceder a los datos de navegación en el Admin VTEX.|
+|**Historial**|Los datos se conservan durante dos años, a partir de 2023 para clientes que ya utilizan la plataforma VTEX. Los datos en la tabla `transaction_interactions` solo tienen historial desde el 07/05/24 (dd/mm/aa).|
+|**Intervalo mínimo de actualización**|Una hora.|
+
+## Tabla payments_transitions
+
+La tabla `payments_transitions` almacena información detallada sobre los pagos, incluido el proveedor y el medio de pago utilizados en cada transacción.  
+Consulta a continuación los campos que componen la tabla:
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | ID de control del lote de ingesta de datos. |
+| **event_date_time** | timestamp with time zone | Fecha y hora de la transición, con información sobre la zona horaria. |
+| **account** | character varying(128) | Nombre de cuenta, mapeado a 'account_name' en VTEX License Manager. |
+| **account_id** | character varying(36) | Identificador de la cuenta, mapeado a 'id' en VTEX License Manager tras eliminar los guiones. |
+| **connector** | character varying(1024) | Proveedor que procesa el pago. |
+| **delta_value** | double precision | Tiempo en milisegundos empleado en la transición 'from_transition'. |
+| **from_transition** | character varying(64) | Status del pago hasta la fecha y hora del evento. |
+| **to_transition** | character varying(64) | Nuevo status de la transacción a partir de la fecha y hora del evento. |
+| **payment_id** | character varying(32) | Identificador único de pago. |
+| **payment_system** | character varying(1024) | Tipo de pago: tarjeta de crédito, débito, etc. |
+| **transaction_id** | character varying(36) | Identificador único de la transacción a la que pertenece este pago. |
+| **tid** | character varying(1024) | Código externo proporcionado por el operador, que funciona como número de identificación para una transacción de ecommerce. |
+| **nsu** | character varying(1024) | NSU (Número Sequencial Único) es un número secuencial único utilizado en Brasil para identificar una transacción de venta con tarjeta y está asociado a cada factura creada. |
+| **currency_code** | character varying(1024) | Código de moneda representado por tres letras mayúsculas. |
+| **value** | integer | Valor del pago multiplicado por 100, lo que significa que para un pago de $2.35 el valor será 235. |  
+
+## Tabla transaction_transitions
+
+La tabla `transaction_transitions` almacena las transacciones vinculadas a pedidos realizados. Cada transacción contiene un conjunto de pagos y cambia de status conforme a un flujo predefinido.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de campo** | **Descripción** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | ID de control del lote de ingesta de datos. |
+| **event_date_time** | timestamp with time zone | Fecha y hora de la transición, con información sobre la zona horaria. |
+| **account** | character varying(128) | Mapea a un 'account_name' en el sistema de gestión de licencias de VTEX. |
+| **account_id** | character varying(36) | Mapea a un 'id' en el sistema de gestión de licencias de VTEX tras eliminar los guiones. |
+| **delta_value** | double precision | Tiempo en milisegundos empleado en la transición 'from_transition'. |
+| **from_transition** | character varying(64) | Status de la transacción hasta la fecha y hora del evento. |
+| **to_transition** | character varying(64) | Nuevo status de la transacción a partir de la fecha y hora del evento. |
+| **transaction_id** | character varying(36) | Identificador único de la transacción. |  
+
+## Análisis con datos de pagos
+
+El conjunto de datos de pagos puede utilizarse para llevar a cabo los siguientes análisis:  
+
+- **Análisis de eficiencia del procesador de pago:** evaluar el rendimiento de distintos proveedores de pago mediante el análisis del tiempo promedio empleado en cada transición para identificar los más eficientes y confiables.  
+- **Monitoreo de las transiciones del status de los pagos:** seguimiento de los cambios de status de los pagos a lo largo del tiempo para comprender patrones e identificar posibles problemas en el flujo de pagos.  
+- **Análisis del volumen de transacciones por cuenta:** determinar el volumen de transacciones procesadas por cada cuenta, lo que ayuda a comprender la demanda de servicios de pago en las distintas cuentas.  
+- **Distribución del tipo de pago:** analiza la distribución del uso de diferentes sistemas de pago para evaluar las preferencias de los clientes por los distintos medios de pago.  
+
+## Correlaciones con otros datos
+
+Los datos de pago de la plataforma VTEX muestran correlaciones con otros conjuntos de datos, ampliando la comprensión del ciclo de compra:
+
+- **Interacción con datos de [pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv):** el análisis conjunto de los datos de pago y los pedidos proporciona información sobre cómo influyen los medios de pago en las conversiones de pedidos, revelando tendencias en el comportamiento de compra de los clientes.  
+- **Análisis financieros y contables:** integrar datos de pago con análisis financieros contribuye a una gestión más eficiente del flujo de caja y permite realizar previsiones financieras más precisas, impulsando la salud financiera de la empresa.  
+
+### Descubra otros conjuntos de datos
+
+- [Stock](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Precios](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promociones](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
+
diff --git a/docs/tutorials/es/payu-romania-refund-details.md b/docs/tutorials/es/payu-romania-refund-details.md
index da0c201d6..0898c1626 100644
--- a/docs/tutorials/es/payu-romania-refund-details.md
+++ b/docs/tutorials/es/payu-romania-refund-details.md
@@ -38,7 +38,7 @@ Si el botón Eliminar no está activo y el tiempo de espera no ha caducado, pued
 
 Si el sistema ya ha enviado la solicitud de reembolso o anulación al banco emisor, ya no podremos eliminarlo / detenerlo de ninguna manera.
 
-![PayU Romania](https://images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
+![PayU Romania](//images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
 
 Una vez que PayU haya enviado la solicitud de cancelación o reembolso al banco emisor, el estado de la orden se actualizará en el panel de PayU como "REVERSE" (para anulaciones) o "REFUND". Y VTEX va a recibir un webhook de PaymentsOS, por lo que el estado del pedido también puede actualizarse en la plataforma (en Pagos y, por lo tanto, reflejado en el OMS).
 
diff --git a/docs/tutorials/es/pci-gateway-overview.md b/docs/tutorials/es/pci-gateway-overview.md
index 37d16130f..4610e9e3c 100644
--- a/docs/tutorials/es/pci-gateway-overview.md
+++ b/docs/tutorials/es/pci-gateway-overview.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 **Pagos** es el módulo responsable por intermediar y gestionar todas las transacciones y pagos entre su tienda VTEX, operadoras financieras y sus clientes. En él usted hace consultas como status de las transacciones, extornos, cancelaciones, liquidaciones y también configuraciones como condiciones para las formas de pago.
 
-![new-admin-pagos](https://images.ctfassets.net/alneenqid6w5/CPFZboq2pqOUSI0CAuQgW/bb254d7dd631b1983cb4fb6e7d01f244/NEW_ADMIN_PAGAMENTOS_ES.png)
+![new-admin-pagos](//images.ctfassets.net/alneenqid6w5/CPFZboq2pqOUSI0CAuQgW/bb254d7dd631b1983cb4fb6e7d01f244/NEW_ADMIN_PAGAMENTOS_ES.png)
 
 # Empezando a usar
 
diff --git a/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md b/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md
index 5dc408a8d..5bbb88c0d 100644
--- a/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md
+++ b/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md
@@ -1,52 +1,159 @@
 ---
-title: 'Pruebas de penetración y advertencia de vulnerabilidad'
+title: 'Pruebas de penetración y avisos de vulnerabilidad'
 id: 6jodF6s1I50Fg84ZwutOCb
 status: PUBLISHED
 createdAt: 2022-11-30T14:20:37.453Z
-updatedAt: 2023-05-22T14:22:24.398Z
-publishedAt: 2023-05-22T14:22:24.398Z
+updatedAt: 2024-04-25T03:01:48.522Z
+publishedAt: 2024-04-25T03:01:48.522Z
 firstPublishedAt: 2022-11-30T14:42:44.449Z
 contentType: tutorial
 productTeam: Others
-author: 2Gy429C47ie3tL9XUEjeFL
+author: 1malnhMX0vPThsaJaZMYm2
 slug: pruebas-de-penetracion-y-advertencia-de-vulnerabilidad
 locale: es
 legacySlug: evaluaciones-de-seguridad-e-informes-de-vulnerabilidad
 subcategory: vONCJSxwN5qZiElOEtKkH
 ---
 
-VTEX evalúa rigurosamente los recursos de la plataforma, probando e identificando vulnerabilidades a través de escaneos y pruebas de penetración recurrentes. Estas comprobaciones de vulnerabilidad se ejecutan periódicamente.
+<div class="alert alert-info">
+  <p>Esta funcionalidad es parte de <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>.  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
 
-Si deseas realizar tu propia prueba de penetración en el entorno de tu tienda, VTEX evaluará tu solicitud y verificará la posibilidad de llevarla a cabo. A continuación te indicamos los pasos a seguir.
+<div class="alert alert-warning">
+  <p>Si requiere un análisis de tu informe de prueba de penetración por parte del equipo de Seguridad de VTEX, es necesario contar con VTEX Shield. Además, todas las pruebas de penetración deben <a href="#programar-prueba-de-penetracion">programarse previamente con VTEX</a>. Se considerará un intento de acción no autorizada cualquier prueba realizada de forma autónoma sin notificación previa a VTEX.</p>
+</div>
 
-## Pruebas de penetración
+VTEX evalúa rigurosamente los recursos de la plataforma, probando e identificando vulnerabilidades mediante escaneos y pruebas de penetración recurrentes. Las verificaciones de vulnerabilidad se realizan de forma continua.
 
-Para solicitar y programar una prueba de penetración, debes:
+Además de las comprobaciones estándar, las tiendas que utilizan [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) pueden realizar pruebas de penetración e informar sobre las vulnerabilidades encontradas, siempre que la programen con VTEX con antelación.
 
-1. Abrir un ticket con el [soporte VTEX](https://help.vtex.com/es/support), solicitando la programación de una prueba de penetración.
-2. Si VTEX la aprueba, nuestro equipo solicitará la información necesaria para agendar y firmar el acuerdo de confidencialidad. Si contratas a una empresa externa para realizar la prueba, esta también deberá firmar el acuerdo de confidencialidad.
-3. Actualiza tu ticket adjuntando el acuerdo de confidencialidad y la información solicitada por VTEX.
-4. Guarda el número de ticket. Lo necesitarás para futuras comunicaciones.
+Las pruebas de penetración, o pentest, son un ataque simulado a un sistema informático, red o aplicación web para identificar y corregir vulnerabilidades de seguridad. Estas pruebas se realizan de forma ética para evaluar la seguridad de un sistema sin causar ningún daño real.
 
-Después de recibir la información, el equipo VTEX entrará en contacto para confirmar la ejecución de la prueba de penetración.
+Consulta en esta guía el procedimiento para programar una prueba de penetración e informar una posible vulnerabilidad en la plataforma:
 
-## Informe de vulnerabilidad
+- [Programar prueba de penetración](#programar-prueba-de-penetracion)
+  - [Informes de pruebas de penetración](#informes-de-pruebas-de-penetracion)
+  - [Procedimientos no permitidos](#procedimientos-no-permitidos)
+- [Informar vulnerabilidad](#informar-vulnerabilidad)
+  - [Definición de vulnerabilidad](#definicion-de-vulnerabilidad)
+  - [Respuesta de VTEX](#respuesta-de-vtex)
 
-Después de la [solicitud](#como-solicitar-una-evaluación-de-seguridad) y de la realización de la evaluación de seguridad, si hay hallazgos, sigue estos pasos:
+## Programar prueba de penetración
 
-1. Revisa y valida todos los hallazgos de la evaluación. Esto requerirá un recurso de seguridad de tu parte, especialmente para informes de escaneo automatizados.
-2. Redacta un informe que especifique, para cada vulnerabilidad descubierta, la siguiente información:
-    - Qué URL y flujos de funcionalidad se vieron afectados.
-    - Cómo se detectó el problema.
-    - Cuál es el impacto de esta vulnerabilidad en la aplicación objetivo si fuese explotada, se debe incluir qué ventajas podría obtener un atacante.
-    - Los criterios de priorización y clasificación utilizados. Considera el uso de un marco reconocido o describe el documento que detalla la metodología de clasificación de criticidad de la vulnerabilidad.
-    - Describe el problema y detalla el procedimiento para reproducir la falla. Incluye imágenes de ser posible.
-    - Si decides incluir en el informe una sección para informar de un ataque, describe las vulnerabilidades que fueron explotadas. En este caso, incluye evidencias de imagen (video es opcional).
-3. Abre un ticket con el [equipo de soporte de VTEX](https://help.vtex.com/es/support) e incluye la siguiente información:
-    - Número de ticket de la [solicitud de evaluación de seguridad](#como-solicitar-una-evaluacion-de-seguridad) correspondiente a la prueba.
-    - Informe de vulnerabilidad producido según se describe en el punto 2.
+<div class="alert alert-warning">
+  <p>Únicamente las tiendas con <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a> pueden programar pruebas de penetración y recibir una respuesta por parte del equipo de seguridad, que incluye acceso a un análisis detallado del informe de la prueba, como se describe en los procedimientos de esta guía.</p>
+</div>
 
-## Acuerdo de confidencialidad
+Para realizar una prueba de penetración en el entorno de tu tienda es necesario programar una fecha con VTEX, para la organización interna y la planificación por parte del equipo de Seguridad. Sigue las instrucciones a continuación:
 
-Aquí puedes descargar el [acuerdo de confidencialidad relativo a las pruebas de seguridad](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+1. Abre un ticket con el [soporte de VTEX](https://help.vtex.com/es/support), para informar de que desea programar una prueba de penetración.
+2. Nuestro equipo solicitará la información necesaria para su programación. Si la tienda contrata a una empresa tercera para realizar la prueba, esta debe firmar el [acuerdo de confidencialidad](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
 
+    VTEX recomienda a los clientes realizar sus pruebas de penetración con partners que dispongan de equipos con un nivel mínimo de certificación, prestando atención a los [procedimientos no permitidos](https://docs.google.com/document/d/1rQKXS8G2GWUwxxz9uwDFfFJLoYvkWD4L/edit#bookmark=id.2s8eyo1).
+
+    Las empresas con profesionales certificados en programas como [Certified Ethical Hacker](https://www.eccouncil.org/train-certify/certified-ethical-hacker-ceh/) de EC-Council, [CompTIA PenTest+](https://www.comptia.org/pt/certificacoes/pentest) y [GIAC Exploit Researcher and Advanced Penetration Tester](https://www.giac.org/certifications/exploit-researcher-advanced-penetration-tester-gxpn/) suelen entregar informes más detallados y estandarizados, lo que mejora la comunicación y la calidad de la evaluación.
+3. Actualiza tu ticket adjuntando el [acuerdo de confidencialidad](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip) firmado por la empresa contratada para realizar la prueba junto con la información solicitada por VTEX.
+4. Guarda el número de ticket, lo necesitarás para futuras comunicaciones.
+5. Tras recibir la información, el equipo de VTEX se pondrá en contacto contigo para confirmar la realización de la prueba de penetración en hasta dos días útiles.
+6. Realiza la prueba en la fecha programada (sujeta a la autorización de VTEX).
+7. Envía un informe con los resultados en el mismo ticket al [soporte VTEX](https://help.vtex.com/es/support).
+
+   <div class="alert alert-warning">
+  <p>Para garantizar el cumplimiento del plazo de análisis por parte de VTEX, es obligatorio seguir las pautas descritas en <a href="#informes-de-pruebas-de-penetracion">Informes de pruebas de penetración</a>.</p>
+   </div>
+
+   Designa a un miembro de tu equipo de seguridad como punto de contacto del equipo de seguridad de VTEX durante el proceso de análisis del informe de la prueba.
+
+El equipo de seguridad de VTEX tiene como cometido realizar un análisis completo de todos los hallazgos reportados por el cliente durante las pruebas de penetración previamente autorizadas y programadas por VTEX.
+
+En un plazo de 10 días laborables desde la recepción del [informe](https://docs.google.com/document/d/1rQKXS8G2GWUwxxz9uwDFfFJLoYvkWD4L/edit#bookmark=id.17dp8vu), el equipo identificará los falsos positivos y reclasificará la gravedad de las amenazas identificadas según sea necesario, siguiendo las prácticas recomendadas de VTEX. Cada decisión de este proceso estará justificada detalladamente para garantizar su total transparencia y comprensión.
+
+<div class="alert alert-warning">
+  <p>Las tiendas que se están preparando para el go live y desean realizar una prueba de penetración también deben programarlo con anticipación. En este caso, es obligatorio enviar el informe con los resultados al <a href="https://help.vtex.com/es/support">soporte VTEX</a> por lo menos <strong>45 días</strong> antes de la fecha prevista para el go live. Durante este periodo, VTEX analizará el resultado y abordará cualquier vulnerabilidad detectada en el proceso.</p>
+</div>
+
+### Informes de pruebas de penetración
+
+Para que VTEX cumpla con el plazo de 10 días laborables de análisis del informe, es necesario seguir estas directrices al crear el informe de la prueba de penetración:
+
+* **Descripción del punto afectado**
+
+    Proporciona información sobre la ubicación del problema detectado (URL, flujo de funcionalidades, entre otros).
+
+* **Descripción del impacto en los negocios**
+
+    Describe lo que ese problema de seguridad causa y cuáles son las ventajas del atacante.
+
+* **Descripción de los criterios para clasificar la vulnerabilidad**
+
+    Utiliza una estructura o documento que detalle los criterios utilizados para clasificar la gravedad de la supuesta vulnerabilidad identificada. 
+
+* **Descripción del problema** 
+
+    Añade imágenes para ilustrar el problema.
+
+* **Descripción de los pasos para reproducir o prueba de concepto**
+
+ Detalla los procedimientos para replicar el problema de seguridad, de ser posible, incluyendo imágenes.
+
+* **Descripción del ataque** (opcional)
+
+ Si se reporta un ataque en el informe, incluye una explicación de los problemas de seguridad utilizados para fomentar el ataque, junto con imágenes de las pruebas (los videos son opcionales).
+
+### Procedimientos no permitidos
+
+Recomendamos utilizar únicamente pruebas autorizadas para identificar vulnerabilidades. Los siguientes procedimientos no están permitidos:
+
+* Realizar de pruebas de penetración sin programación previa con VTEX.
+* Realizar acciones que puedan afectar negativamente a VTEX, sus productos o usuarios. Por ejemplo, spam, ataques de fuerza bruta, de denegación de servicio y otras acciones relativas a pruebas de seguridad informadas en el [acuerdo de confidencialidad](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+* Acceder o intentar acceder a datos o información que no pertenecen a tu cuenta.
+* Destruir o intentar corromper datos o información pertenecientes a VTEX.
+* Realizar cualquier tipo de ataque físico o electrónico contra el personal o propiedades de VTEX.
+* Técnicas de ingeniería social.
+* Infringir cualquier ley y reglamento o incumplir cualquier acuerdo para descubrir vulnerabilidades.
+
+## Informar vulnerabilidad
+
+Animamos a nuestros clientes a que informen responsablemente de cualquier vulnerabilidad de seguridad que crean haber encontrado durante las pruebas autorizadas.
+
+Quienes deseen informar una vulnerabilidad deben trabajar primero con sus propios equipos de seguridad y desarrollo para realizar una evaluación de seguridad y eliminar falsos positivos o problemas derivados de configuraciones personalizadas. Se analizarán únicamente los casos que sean compatibles con la [definición de vulnerabilidad](#definicion-de-vulnerabilidad).
+
+<div class="alert alert-warning">
+  <p>Consulta el documento <a href="https://vtex.com/mx-es/security/security-practices/">Prácticas de seguridad de VTEX</a> y nuestras <a href="https://help.vtex.com/es/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX">Preguntas frecuentes sobre seguridad</a> antes de informar cualquier vulnerabilidad. Estos documentos aclaran nuestros procesos y ayudan a eliminar los falsos positivos.</p>
+</div>
+
+Después de este procedimiento, si existe una vulnerabilidad, sigue los pasos a continuación para reportarla:
+
+1. Descarga el [modelo de informe de vulnerabilidades](https://assets.ctfassets.net/alneenqid6w5/7FNzoEpl67wH6crmW98If2/3e2fd05877617f746294ecacb8ace8e6/Modelo_-_Comunicaci__n_de_vulnerabilidad_-_ES.pdf).
+2. Rellena el modelo con los detalles de cada vulnerabilidad encontrada. Agrega todos los datos posibles sobre las vulnerabilidades encontradas para explicar la sospecha identificada, proporcionando pruebas e imágenes que nos ayuden a comprender, reproducir y validar el problema.
+
+    Las vulnerabilidades se deben informar de manera individual según el modelo establecido. Si encontraste más de una vulnerabilidad en tu prueba, rellena varios modelos y adjúntalos a tu ticket.
+
+  <div class="alert alert-warning">
+    <p>Toda la información solicitada debe rellenarse, dado que es importante para la evaluación. El equipo de Seguridad de VTEX no atenderá vulnerabilidades que no sigan el patrón establecido.</p>
+  </div>
+
+3. Abre un ticket para nuestro [Soporte](https://help.vtex.com/support?/cultureInfo=es-419) para registrar el aviso de vulnerabilidad de seguridad. No olvides adjuntar el modelo de comunicación de vulnerabilidades y rellena todos los datos solicitados en el ticket de soporte.
+4. Guarda tu número de ticket, ya que puedes necesitarlo en futuras comunicaciones.
+
+### Definición de vulnerabilidad
+
+VTEX considera una vulnerabilidad de seguridad cualquier falla en uno de nuestros componentes que pudiera permitir que la confidencialidad, integridad o disponibilidad del producto o de la infraestructura se vean comprometidas de algún modo.
+
+No se consideran vulnerabilidad los siguientes casos: 
+
+* Presencia o ausencia de encabezados HTTP (como por ejemplo X-Frame-Options, CSP o nosniff).
+* Ausencia de atributos de seguridad en cookies.
+* Problemas relacionados con la caché.
+* Mensajes de error de seguimiento de pila (stack trace).
+* Inyección de contenidos por usuarios administrativos.
+* Partes personalizadas de la tienda.
+* Autocompletar activado.
+
+### Respuesta de VTEX
+
+VTEX no se compromete a responder a informes en masa generados por verificadores automáticos. Si tu análisis se basa en un proceso automático de identificación de vulnerabilidades, recomendamos que los informes sean analizados por un profesional de seguridad para garantizar la validez de la vulnerabilidad encontrada antes de comunicarse con VTEX.
+
+VTEX se compromete a responder a los tickets que reciba el equipo de [Soporte](https://help.vtex.com/support?/cultureInfo=es-419) lo antes posible, notificando la corrección de la vulnerabilidad o proporcionando motivos coherentes por los que los análisis o las correcciones puedan no llevarse a cabo.
+
+VTEX pone todos los esfuerzos a su alcance para analizar, verificar y solucionar cualquier vulnerabilidad que se nos comunique y que pueda comprometer tu seguridad.
diff --git a/docs/tutorials/es/permissions-management-in-b2b-suite.md b/docs/tutorials/es/permissions-management-in-b2b-suite.md
new file mode 100644
index 000000000..94bf1c50c
--- /dev/null
+++ b/docs/tutorials/es/permissions-management-in-b2b-suite.md
@@ -0,0 +1,66 @@
+---
+title: 'Gestionar permisos en B2B Suite'
+id: 2PLR7mIFxgbmsGq84paLeA
+status: PUBLISHED
+createdAt: 2024-06-05T18:01:03.375Z
+updatedAt: 2024-06-07T13:37:21.121Z
+publishedAt: 2024-06-07T13:37:21.121Z
+firstPublishedAt: 2024-06-06T10:57:21.290Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gestionar-permisos-en-b2b-suite
+locale: es
+legacySlug: gestionar-permisos-en-b2b-suite
+subcategory: 1qGLxbxcX8kwKSWESbLZca
+---
+
+En una organización, el Organization Admin (usuario principal) gestiona el acceso de diferentes personas en una tienda B2B utilizando el sistema de permisos de B2B Suite.
+
+Esta aplicación permite:
+
+- **Configuración inicial:** el administrador establece las características de los roles predefinidos y los permisos asociados a los mismos.
+
+- **Asociación de roles y permisos:** los roles predefinidos se asocian a las diferentes funciones y responsabilidades dentro de la organización. Cada rol tiene sus propios permisos específicos.
+
+- **Sincronización automática de la información:** la aplicación se comunica automáticamente con otras aplicaciones de B2B Suite, como [B2B Organizations](https://developers.vtex.com/docs/apps/vtex.b2b-organizations), para habilitar diferentes funciones de gestión de organización según el rol de cada usuario.
+
+- **Verificación de permisos:** cuando un usuario realiza una acción en la tienda, como realizar un pedido o acceder a una determinada funcionalidad, la aplicación comprueba si ese usuario tiene los permisos necesarios para llevar a cabo esa acción en función del rol que se le haya asignado previamente.
+
+- **Gestión de permisos:** la aplicación opera en segundo plano (background), almacenando los roles predefinidos.
+
+## Roles y permisos
+
+La aplicación Storefront Permissions permite que cada usuario dentro de una organización pueda tener roles distintos, como el de comprador, quien realiza pedidos dentro de límites presupuestarios establecidos para un centro de costos específico, o el de gestor, encargado de revisar y aprobar pedidos. Estos roles pueden estar asociados a múltiples permisos, dependiendo de las acciones que el usuario necesite desempeñar.
+
+Roles
+
+La siguiente tabla muestra los roles disponibles, sus claves y descripciones.
+
+| Rol                   | Clave                | Descripción                                                                                                                                                                                    |
+|-----------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Store Admin           | store-admin          | Usuario administrador que accede al Admin VTEX y gestiona la tienda.                                                                                                                           |
+| Sales Admin           | sales-admin          | Usuario administrador que puede gestionar todos los usuarios de ventas.                                                                                                                        |
+| Sales Manager         | sales-manager        | Usuario gerente de ventas que puede gestionar usuarios de ventas de la misma organización, así como asistir a compradores y simular compras en una tienda.                                     |
+| Sales Representative  | sales-representative | Usuario representante que puede ayudar en las compras o simular compras en una tienda.                                                                                                         |
+| Organization Admin    | customer-admin       | Usuario principal de la organización que gestiona la información de la empresa, así como sus miembros y centros de costos.                                                                     |
+| Organization Approver | customer-approver    | Usuario de la organización que puede recuperar un carrito o cotización previamente guardada por un comprador de la organización y crear un nuevo pedido.                                       |
+| Organization Buyer    | customer-buyer       | Usuario de la organización que puede agregar ítems al carrito. Si la aplicación [B2B Quotes & Carts](https://developers.vtex.com/docs/apps/vtex.b2b-quotes) está instalada, también puede guardar el carrito para un uso futuro o crear una cotización. |
+
+## Configuración o gestión de roles
+
+Para gestionar roles y permisos de aplicaciones, configura los permisos siguiendo los pasos que se indican a continuación en la interfaz Permisos del storefront.
+
+1. Accede al Admin VTEX > Apps > Apps Instaladas > Permisos del storefront, o ingresa Permisos del storefront en la barra de búsqueda de la parte superior de la página.
+
+2. Haz clic en uno de los roles disponibles.
+
+3. Haz clic en una de las aplicaciones de la lista.
+
+4. Selecciona los permisos que deseas activar para ese rol.
+
+5. Haz clic en `Guardar`.
+
+![Gerenciamento de permissões - ES](//images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/fdf3c362f0300198da41af04681d3239/Gerenciamento_de_permiss_es_-_ES.gif)
+
+Después de asociar los perfiles con los roles deseados, puedes atribuir funciones a los usuarios. Para más información, consulta [B2B Organizations](https://developers.vtex.com/docs/guides/vtex-b2b-organizations#users).
diff --git a/docs/tutorials/es/physical-store-instore-beta.md b/docs/tutorials/es/physical-store-instore-beta.md
index 31c8835b3..82695406e 100644
--- a/docs/tutorials/es/physical-store-instore-beta.md
+++ b/docs/tutorials/es/physical-store-instore-beta.md
@@ -28,7 +28,7 @@ Esta página te permite realizar las siguientes acciones:
 * [Editar](#editar-tienda)
 * [Eliminar](#eliminar-tienda)
 
-![loja-fisica-ES](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
+![loja-fisica-ES](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
 
 La página contiene la siguiente información:
 
@@ -53,7 +53,7 @@ Puedes crear una tienda física siguiendo los pasos a continuación:
 
 ### Campos de registro de la tienda física
 
-![loja-fisica2-es](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
+![loja-fisica2-es](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
 
 #### Identificación
 
diff --git a/docs/tutorials/es/pickup-points-for-subscription-orders.md b/docs/tutorials/es/pickup-points-for-subscription-orders.md
new file mode 100644
index 000000000..e61f200ca
--- /dev/null
+++ b/docs/tutorials/es/pickup-points-for-subscription-orders.md
@@ -0,0 +1,54 @@
+---
+title: 'Puntos de recogida para pedidos de suscripción'
+id: csIqB6iBh4QNIFdEj0nVv
+status: PUBLISHED
+createdAt: 2021-05-17T12:45:21.450Z
+updatedAt: 2023-11-16T15:59:51.093Z
+publishedAt: 2023-11-16T15:59:51.093Z
+firstPublishedAt: 2021-05-17T20:55:05.477Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 1malnhMX0vPThsaJaZMYm2
+slug: puntos-de-recogida-para-pedidos-de-suscripcion
+locale: es
+legacySlug: puntos-de-recogida-para-pedidos-de-suscripcion-beta
+subcategory: 1rA9wuuskW3PpjvMrhatAM
+---
+
+Un punto de recogida es un lugar físico donde el cliente tiene la opción de recoger su pedido, en vez de recibirlo en casa. Un ejemplo de escenario para esta funcionalidad es la recogida en la tienda.
+
+Además de los pedidos habituales, puede habilitar puntos de recogida para los pedidos de suscripción, si utiliza el [módulo Suscripciones](https://help.vtex.com/es/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj).
+
+A continuación, vea lo que se requiere para habilitar esta funcionalidad.
+
+- [Requisitos](#requisitos)
+- [Eligir puntos de recogida](#eligir-puntos-de-recogida)
+
+<div class="alert alert-info">
+  <p>La funcionalidad de puntos de recogida solo está disponible para las cuentas que ya tienen acceso a <a href="https://help.vtex.com/es/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH">Checkout V6</a>.</p>
+</div>
+
+## Requisitos
+
+Para habilitar los puntos de recogida para los pedidos de suscripción, se deben cumplir la lista de requisitos logísticos que se indica a continuación.
+
+*   Debe tener el [módulo Suscripciones](https://help.vtex.com/es/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj) instalado y la opción «Puntos de recogida» habilitada. Para eso, contacte a [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
+*   Necesita configurar los puntos de recogida en su tienda. Solo se pueden utilizar puntos de recogida de la tienda principal o de franquicias (Sellers White Label) para los pedidos de suscripción. Para saber cómo efectuar la configuración, lea el artículo [Configurar Puntos de recogida (Pickup Points)](https://help.vtex.com/es/tutorial/adding-pickup-points--2R5ClQiwe4KoSQgsuiOw4E).
+*   Las transportadoras asociadas a los puntos de recogida para pedidos de suscripción **no** pueden tener [ventanas de entrega](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) configuradas.
+*   Los ítems deben contar con _stock_ en la fecha del ciclo de suscripción, es decir, cuando se crean los pedidos recurrentes.
+
+## Elegir puntos de recogida
+
+El cliente final puede elegir los puntos de recogida para ítems de un pedido de suscripción cuando realiza el _checkout_, como se muestra en la siguiente imagen.
+
+![subscriptionspickup ES](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
+
+También puede asignar puntos de recogida al [crear nuevas suscripciones](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#post_api-rns-pub-subscriptions) a través de la [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1). En el caso de las suscripciones existentes, puede modificar la dirección de entrega a través de la [ruta de actualización de suscripciones de la API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#patch_api-rns-pub-subscriptions-id) para empezar a utilizar un punto de recogida.
+
+Para descubrir los puntos de recogida disponibles cerca de un código postal o de determinadas coordenadas geográficas, puede utilizar la [API de Checkout](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview).
+
+## Artículos relacionados
+
+*   [Cómo configurar Suscripciones en su tienda](https://help.vtex.com/es/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj)
+*   [Configurar Puntos de recogida (Pickup Points)](https://help.vtex.com/es/tutorial/configurar-pontos-de-retirada-pickup-points--2R5ClQiwe4KoSQgsuiOw4E)
+*   [Configurar Seller White Label como punto de recogida (Pickup Point)](https://help.vtex.com/es/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e)
diff --git a/docs/tutorials/es/pickup-points.md b/docs/tutorials/es/pickup-points.md
index 4fdead19d..d56f3dc3a 100644
--- a/docs/tutorials/es/pickup-points.md
+++ b/docs/tutorials/es/pickup-points.md
@@ -3,8 +3,8 @@ title: 'Puntos de recogida'
 id: 2fljn6wLjn8M4lJHA6HP3R
 status: PUBLISHED
 createdAt: 2020-07-01T19:16:21.675Z
-updatedAt: 2023-03-29T19:48:10.418Z
-publishedAt: 2023-03-29T19:48:10.418Z
+updatedAt: 2023-07-25T16:53:09.640Z
+publishedAt: 2023-07-25T16:53:09.640Z
 firstPublishedAt: 2020-07-01T19:25:40.136Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -68,7 +68,7 @@ VTEX considera que el punto de recogida es una forma de envío. Es por eso que l
     - Paso 2: Haz clic en la pestaña **Políticas de envío**, selecciona la política de envío creada para el punto de recogida.
     - Paso 3: En la columna **Acciones**, haz clic en el ícono <i class="fas fa-pen"></i> para editar.
     - Paso 4: Activa el botón <i class="fas fa-toggle-on"></i> del campo **Asociar puntos de recogida**.
-    - Paso 5: Selecciona el punto de recogida mediante los campos disponibles.![relacionarpontosretiradaES](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/d72f0278d6fdbb3041d883fa4685f436/relacionarpontosretiradaES.png) <div class = "alert alert-info">Para las tiendas que tienen más de 50 puntos de recogida, recomendamos utilizar el campo Tags de <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140#registrar-politica-de-envio">los puntos de recogida al crear un punto de recogida</a>. Utilizar tags facilita la búsqueda de los puntos de recogida al asociarlos con la política de envío.También recuerda que la política de envío que está asociada a un punto de recogida no estará disponible para otros tipos de envíos. Recomendamos crear una política de envío dedicada al punto de recogida.</div>
+    - Paso 5: Selecciona el punto de recogida mediante los campos disponibles.![relacionarpontosretiradaES](//images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/d72f0278d6fdbb3041d883fa4685f436/relacionarpontosretiradaES.png) <div class = "alert alert-info">Para las tiendas que tienen más de 50 puntos de recogida, recomendamos utilizar el campo Tags de <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140#registrar-politica-de-envio">los puntos de recogida al crear un punto de recogida</a>. Utilizar tags facilita la búsqueda de los puntos de recogida al asociarlos con la política de envío.También recuerda que la política de envío que está asociada a un punto de recogida no estará disponible para otros tipos de envíos. Recomendamos crear una política de envío dedicada al punto de recogida.</div>
 
 4. [Registrar la geolocalización](https://help.vtex.com/es/tutorial/gestionar-geolocalizacion--tutorials_138): para una mayor precisión de la ubicación de los puntos de recogida en el _checkout_.<div class = "alert alert-info">La visualización de los puntos de recogida con el mapa y la hora en el checkout solo está disponible para Checkout V6.</div>
 
@@ -76,8 +76,8 @@ VTEX considera que el punto de recogida es una forma de envío. Es por eso que l
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Checkout**, o escribe *Checkout* en la barra de búsqueda en la parte superior de la página.  
     - Paso 2: Selecciona la configuración utilizada en la tienda y haz clic en el ícono <i class="fas fa-cog"></i>.
     - Paso 3: Haz clic en la pestaña **Checkout** en la barra superior.
-    - Paso 4: Selecciona el botón <i class="fas fa-toggle-on"></i> del campo **Dirección de la factura para recogida en la tienda**. ![NFpontoretiradaES](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/c81afd5e90d05deec1684dba401f569e/NFpontoretiradaES.png)<div class="alert alert-warning">La opción de <b>Dirección en la factura para recogida en la tienda</b> debe estar habilitada en todas las tiendas en Brasil, ya que es requisito que la factura emitida contenga la información de la dirección del cliente, incluso si la opción de entrega de el pedido está en el punto de recogida. La dirección ingresada por el cliente se registrará en el campo `invoiceData` del <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - Paso 4: Selecciona el botón <i class="fas fa-toggle-on"></i> del campo **Dirección de la factura para recogida en la tienda**. ![NFpontoretiradaES](//images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/c81afd5e90d05deec1684dba401f569e/NFpontoretiradaES.png)<div class="alert alert-warning">La opción de <b>Dirección en la factura para recogida en la tienda</b> debe estar habilitada en todas las tiendas en Brasil, ya que es requisito que la factura emitida contenga la información de la dirección del cliente, incluso si la opción de entrega de el pedido está en el punto de recogida. La dirección ingresada por el cliente se registrará en el campo `invoiceData` del <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
 
 6. Para configurar la cantidad de puntos de recogida que se muestran en el checkout:
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Envío > Configuración**, o escribe *Envío* en la barra de búsqueda en la parte superior de la página, y haga clic en *Configuración de la tienda / Envío*.    
-    - Paso 2: Cambia el campo **Configuración de los puntos de recogida**. Utiliza los botones <i class="far fa-caret-square-up"></i> y <i class="far fa-caret-square-down"></i> y selecciona los puntos de recogida que estarán disponibles en la lista de búsqueda (mostrada en el checkout).
+    - Paso 2: Cambia el campo **Configuración de los puntos de recogida**. Utiliza los botones <i class="far fa-caret-square-up"></i> y <i class="far fa-caret-square-down"></i> y selecciona la cantidad de puntos de recogida que estarán disponibles en la lista de búsqueda (mostrada en el checkout).
diff --git a/docs/tutorials/es/plan-your-project.md b/docs/tutorials/es/plan-your-project.md
index 7d1649347..86f4f937d 100644
--- a/docs/tutorials/es/plan-your-project.md
+++ b/docs/tutorials/es/plan-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Planifique su proyecto'
 id: tutorials_2546
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:54:42.370Z
-updatedAt: 2019-12-31T15:20:45.999Z
-publishedAt: 2019-12-31T15:20:45.999Z
+updatedAt: 2024-03-11T13:20:06.594Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:51.704Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/planner-calendar-page-beta.md b/docs/tutorials/es/planner-calendar-page-beta.md
index 56355e857..d03773b09 100644
--- a/docs/tutorials/es/planner-calendar-page-beta.md
+++ b/docs/tutorials/es/planner-calendar-page-beta.md
@@ -38,7 +38,7 @@ El **Calendario** muestra solamente [releases programados](https://help.vtex.com
 
 La imagen a continuación muestra la vista por mes y señala qué puedes hacer en esta interfaz:
 
-![releases-calendar-monthly-view-es](https://images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/8b589697f708bf34d7eac2b15c832b67/releases-calendar-monthly-view-es.png)
+![releases-calendar-monthly-view-es](//images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/8b589697f708bf34d7eac2b15c832b67/releases-calendar-monthly-view-es.png)
 
 En esta pantalla, puedes:
 
@@ -56,7 +56,7 @@ En esta pantalla, puedes:
 
 La imagen a continuación muestra la vista por semana y señala qué puedes hacer en esta interfaz:
 
-![releases-calendar-weekly-view-es](https://images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/56000b0f86260f9e461695eab592be75/releases-calendar-weekly-view-es.png)
+![releases-calendar-weekly-view-es](//images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/56000b0f86260f9e461695eab592be75/releases-calendar-weekly-view-es.png)
 
 En esta pantalla, puedes:
 
@@ -74,7 +74,7 @@ En esta pantalla, puedes:
 
 La imagen a continuación muestra la vista por día y señala qué puedes hacer en esta interfaz:
 
-![daily view v2 es](https://images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/91fa4db8315a31fdf1187edf74e19d61/daily_view_v2_es.png)
+![daily view v2 es](//images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/91fa4db8315a31fdf1187edf74e19d61/daily_view_v2_es.png)
 
 Además de ver información sobre el release, en esta pantalla, puedes:
 
diff --git a/docs/tutorials/es/planner-releases-page-beta.md b/docs/tutorials/es/planner-releases-page-beta.md
index 45307a25a..20bf05ceb 100644
--- a/docs/tutorials/es/planner-releases-page-beta.md
+++ b/docs/tutorials/es/planner-releases-page-beta.md
@@ -36,7 +36,7 @@ El orden de los releases programados se basa en la fecha de publicación: cuanto
 
 Para acceder a la página **Releases** en el Admin VTEX, dirígete al menú de navegación del **Releases**. La imagen a continuación muestra la interfaz e identifica qué puedes hacer en ella:
 
-![Releases list view v3 - ES](https://images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/94f9712e23df3f3e28c126acd4367d8f/Releases_list_view_v3_-_ES.png)
+![Releases list view v3 - ES](//images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/94f9712e23df3f3e28c126acd4367d8f/Releases_list_view_v3_-_ES.png)
 
 | **Campo** | **Descripción** |
 |---|---|
diff --git a/docs/tutorials/es/predefined-roles.md b/docs/tutorials/es/predefined-roles.md
index 148acd02e..b3ba518c1 100644
--- a/docs/tutorials/es/predefined-roles.md
+++ b/docs/tutorials/es/predefined-roles.md
@@ -3,8 +3,8 @@ title: 'Roles de usuario predefinidos'
 id: jGDurZKJHvHJS13LnO7Dy
 status: PUBLISHED
 createdAt: 2022-04-07T21:34:06.385Z
-updatedAt: 2023-06-06T21:37:23.798Z
-publishedAt: 2023-06-06T21:37:23.798Z
+updatedAt: 2024-05-22T17:50:31.567Z
+publishedAt: 2024-05-22T17:50:31.567Z
 firstPublishedAt: 2022-04-07T21:48:28.951Z
 contentType: tutorial
 productTeam: Identity
@@ -15,14 +15,20 @@ legacySlug: perfiles-de-acceso-predefinidos
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-En este documento haremos una lista de los [roles de usuario](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#) que están predeterminados para las nuevas tiendas VTEX. Para acceder a estos de forma directa utilice la siguiente lista:
+[Roles de usuario](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#) agrupan los [recursos del License Manager](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#), siendo que cada recurso representa una permisión en la plataforma VTEX.
+
+En este documento, se enumeran roles que están predefinidos para las nuevas tiendas VTEX y sus respectivos recursos. Para acceder a ellos directamente, utilice la lista a continuación.
+
+<div class="alert alert-info">
+<p>Para obtener más información sobre cada recurso listado en los perfiles a continuación, consulte el artículo <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">Recursos del License Manager</a>.</p>
+</div>
 
 * [Admin - Start page only](#admin-start-page-only)
 * [Checkout Admin](#checkout-admin)
 * [Call center operator](#call-center-operator)
 * [Finance](#finance)
 * [Finance - Full access](#finance-full-access)
-* [VTEX Sales App Sales Person](#instore-sales-person)
+* [Sales App - Sales Associate](#sales-app-sales-associate)
 * [IntegrationProfile - Fulfillment](#integrationprofile-fulfillment)
 * [IntegrationProfile - Fulfillment Gateway](#integrationprofile-fulfillment-gateway)
 * [IntegrationProfile - Fulfillment Gateway GetOrder](#integrationprofile-fulfillment-gateway-getorder)
@@ -45,1144 +51,287 @@ En este documento haremos una lista de los [roles de usuario](https://help.vtex.
 rol básico que da acceso a la página de inicio del ambiente administrativo.
 Mínimo requerido para que un usuario no sea recibido con un mensaje de error al entrar en el ambiente administrativo.  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página de ayuda inicial</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Home-page | Catalog | Administración | Página inicial |
+| Help-page | Catalog | Administración | Página de ayuda inicial |
 
 ## Checkout Admin
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Shopping Cart Full Access</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Full Access</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td>Acceso a todos los pedidos</td>
-  </tr>
-  <tr>
-    <td>Order Cancelation</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td></td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Shopping Cart Full Access | Checkout | CheckoutResources |
+| Orders Full Access | Checkout | CheckoutResources | Acceso a todos los pedidos |
+| Order Cancelation | Checkout | CheckoutResources |
 
 ## Call center operator
 
-Este es un rol que tiene características especiales. El recurso **Assisted sales** hace que el usuario sea redirigido automáticamente a la tienda,  con lo cual el usuario que inicie sesión en una cuenta con este rol no tiene acceso a recursos importantes del menú administrativo. Recomendamos el uso de dos cuentas para los usuarios de televentas. Una cuenta separada para el rol **Call center operator** y otra para otras operaciones que el usuario pueda necesitar realizar en el menú administrativo.  
+Se trata de un rol dedicado a los teleoperadores, ya que permite acceder a las funcionalidades de televenta de VTEX y consultar los pedidos.
+
+El recurso __Assisted Sales__ hace que el usuario sea redirigido automáticamente a la página de televenta de la tienda, lo que dejará al usuario que acceda a una cuenta con este perfil sin acceso a importantes funcionalidades del menú administrativo.
+
+Por lo tanto, recomendamos utilizar dos cuentas separadas (con correos electrónicos separados) para los usuarios de televenta: una cuenta para el rol de __Call center operator__ (con los recursos *Assisted Sales* y *View order*) y otra cuenta para realizar operaciones en Admin, si es necesario.
 
 <div class="alert alert-warning">Al crear un <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">rol</a>, evita incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televentas junto con otros recursos. De lo contrario, puede que el rol no funcione de forma esperada.
 </div>
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Assisted Sales</td>
-    <td>Catalog</td>
-    <td>Televentas</td>
-    <td>Después de iniciar sesión, el usuario es redirigido al sitio de televentas www.sutienda.com/a/televentas. De esta manera, el operador puede hacer operaciones en la tienda en nombre del cliente. Aparecerá una barra en la parte superior de la pantalla.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de pedidos en el OMS.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Assisted Sales | Catalog | Televentas | Funcionalidades de televenta. Tras iniciar sesión, el usuario es redirigido al sitio web de televenta www.{nombredetienda}.com.br/a/televendas. De esta forma, el operador puede utilizar las funcionalidades de televenta, como navegar por la tienda en nombre del cliente.Como este recurso provoca la redirección automática a la tienda, el usuario que entre en una cuenta con un perfil con este recurso no tendrá acceso a importantes funcionalidades del Admin. |
+| View order | OMS | AccesoOMS | Permite la visualización de pedidos en el OMS. |
 
 ## Finance  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>UI - Account list</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-  <tr>
-    <td>Invoices List</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso. Permite la visualización de las facturas.</td>
-  </tr>
-  <tr>
-    <td>Edit Company Information</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite editar datos de una Company.</td>
-  </tr>
-  <tr>
-    <td>Contracts List</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso.  Visualización  de todos los contratos (activos e inactivos) de una Company.</td>
-  </tr>
-  <tr>
-    <td>Display Company info</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso.  Permite visualizar datos de una Company.</td>
-  </tr>
-  <tr>
-    <td>Contacts List</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso.  Permite a visualización de la lista de Contactos que reciben notificación por correo electrónico del cobro generado.</td>
-  </tr>
-  <tr>
-    <td>Edit Contacts</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite editar contactos que reciben la notificación del cobro generado.</td>
-  </tr>
-  <tr>
-    <td>Generate new Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. El sector financiero puede generar un cobro en la Factura manualmente a través de los contratos.</td>
-  </tr>
-  <tr>
-    <td>Recalc Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Generar nuevo cobro con interés. Sí, con interés.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| UI - Account list | License Manager | Control de Acceso Web |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| View store sales stats | OMS | AccesoOMS | Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos. |
+| Invoices List | Billing | Invoice | Clientes, responsables de billing y financiero tienen acceso. Permite la visualización de las facturas. |
+| Edit Company Information | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite editar datos de una Company. |
+| Contracts List | Billing | Contracts | Clientes, responsables de billing y financiero tienen acceso.  Visualización  de todos los contratos (activos e inactivos) de una Company. |
+| Display Company info | Billing | Company | Clientes, responsables de billing y financiero tienen acceso.  Permite visualizar datos de una Company. |
+| Contacts List | Billing | Contacts | Clientes, responsables de billing y financiero tienen acceso.  Permite a visualización de la lista de Contactos que reciben notificación por correo electrónico del cobro generado. |
+| Edit Contacts | Billing | Contacts | Solamente responsables de billing y financiero tienen acceso. Permite editar contactos que reciben la notificación del cobro generado. |
+| Generate new Invoice | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. El sector financiero puede generar un cobro en la Factura manualmente a través de los contratos. |
+| Recalc Invoice | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Generar nuevo cobro con interés. Sí, con interés. |
 
 ## Finance - Full access  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Save account</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Servicios</td>
-    <td>Guarda una cuenta</td>
-  </tr>
-  <tr>
-    <td>Get account by identifier</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Servicios</td>
-    <td>Consulta que devuelve cuenta por el identificador, que puede ser el id de la cuenta o el host de la aplicación de la cuenta.</td>
-  </tr>
-  <tr>
-    <td>UI - Account list</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>UI - Edit account</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>UI - Edit role</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-  <tr>
-    <td>Invoices List</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso. Permite la visualización de facturas.</td>
-  </tr>
-  <tr>
-    <td>Edit Company Information</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite editar datos de una Company.</td>
-  </tr>
-  <tr>
-    <td>Contracts List</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso. Visualización de todos los contratos (activos e inactivos) de una Company.</td>
-  </tr>
-  <tr>
-    <td>Display Company info</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso.  Permite visualizar datos de una Company.</td>
-  </tr>
-  <tr>
-    <td>Contacts List</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Clientes, responsables de billing y financiero tienen acceso.  Permite la visualización de la lista de contactos que reciben notificación por correo electrónico del cobro generado.</td>
-  </tr>
-  <tr>
-    <td>Edit Contacts</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite editar contactos que reciben notificación del cobro generado.</td>
-  </tr>
-  <tr>
-    <td>Generate new Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Sector financiero puede generar un cobro en la Factura manualmente a través de los  contratos.</td>
-  </tr>
-  <tr>
-    <td>Edit Company's Document</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite editar los datos de documento (CNPJ o CPF) de la Company, para donde se generará la factura.</td>
-  </tr>
-  <tr>
-    <td>Add Account</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite agregar cuenta (account) para agrupar otras cuentas ya vinculadas con este cliente en un único billing.</td>
-  </tr>
-  <tr>
-    <td>Delete Account</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite eliminar cuenta asociada con una Company. Company es la entidad creada para englobar diversas cuentas de la misma tienda.</td>
-  </tr>
-  <tr>
-    <td>Save contracts</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Solamente responsables de billing, sales operations/growth y financiero tienen acceso. Permite crear nuevo contrato.</td>
-  </tr>
-  <tr>
-    <td>Cancel Invoice Document</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Cancelar documento fiscal en las prefecturas, permite cancelar un documento fiscal aunque la factura ya se haya generado.</td>
-  </tr>
-  <tr>
-    <td>Issue Invoice Document</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Se utiliza en casos específicos de países donde aún no existe la generación automática de documentos fiscales, dependiendo del sistema financiero. En este caso, puede ser generado manualmente.</td>
-  </tr>
-  <tr>
-    <td>Conciliate Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. El default es marcar como pagado automáticamente, pero el cliente puede pagar aparte, dependiendo de la negociación. En este caso, el sector financiero tiene la facultad de marcar como pagado manualmente, conciliando las facturas.</td>
-  </tr>
-  <tr>
-    <td>Generate Invoice Overdue without Interest</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Generar nuevo cobro con interés. Sí, con interés.</td>
-  </tr>
-  <tr>
-    <td>Cancel Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Cancelar cobro en billing, permite cancelar una factura aunque ya haya sido generada.
-   </td>
-  </tr>
-  <tr>
-    <td>Change payment status</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. El sector financiero tiene la facultad de cambiar el status de pago de una Company, dependiendo de la negociación que haga con el cliente.</td>
-  </tr>
-  <tr>
-    <td>Recalc Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Generar nuevo cobro con interés. Sí, con interés.</td>
-  </tr>
-  <tr>
-    <td>Get Unscrewed Dashboard Charges</td>
-    <td>Billing</td>
-    <td>Dashboard</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Acceso a dashboard externo al Admin, que visualiza facturas emitidas en ese momento, y qué cuentas son provisionadas en ese momento.</td>
-  </tr>
-  <tr>
-    <td>Merge companies</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite la fusión entre dos Companies, unificando su billing.</td>
-  </tr>
-  <tr>
-    <td>Split companies</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. Permite separar una Company única en Companies diferentes.</td>
-  </tr>
-  <tr>
-    <td>Unpaid invoices</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Solamente responsables de billing y financiero tienen acceso. El sector financiero puede cancelar el pago de un cobro manualmente, en caso de que no se haya realizado o se haya realizado de manera equivocada.</td>
-  </tr>
-  <tr>
-    <td>Get App</td>
-    <td>Log</td>
-    <td>Log Admin</td>
-    <td>Uso interno de VTEX.</td>
-  </tr>
-  <tr>
-    <td>Create Table</td>
-    <td>Log</td>
-    <td>Log Admin</td>
-    <td>Uso interno de VTEX.</td>
-  </tr>
-</table>
-
-## VTEX Sales App Sales Person  
-
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Product Form</td>
-    <td>Catalog</td>
-    <td>Contenido</td>
-    <td>Acceso a la pantalla del producto.</td>
-  </tr>
-  <tr>
-    <td>Store Texts</td>
-    <td>Catalog</td>
-    <td>Configuraciones</td>
-    <td>Herramienta del desarrollador con todos los textos base de la tienda.</td>
-  </tr>
-  <tr>
-    <td>Assisted Sales</td>
-    <td>Catalog</td>
-    <td>Televentas</td>
-    <td>Después de iniciar sesión, el usuario es redirigido a la tienda (accountname.myvtex.com).</td>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página de ayuda inicial</td>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Representa las operaciones transaccionales del gateway de pagos.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera una transacción.</td>
-  </tr>
-  <tr>
-    <td>Manage Store</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ManageStore</td>
-    <td>Permite modificar los ajustes de la configuración.</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite informar facturas (NF) y datos para rastreo manualmente en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite Cancelar pedido en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Full access in all documents</td>
-    <td>Dynamic Storage</td>
-    <td>Recursos genéricos para Dynamic Storage</td>
-    <td>Recurso registrado automáticamente por Dynamic Storage.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Save account | License Manager | Control de Acceso Servicios | Guarda una cuenta |
+| Get account by identifier | License Manager | Control de Acceso Servicios | Consulta que devuelve cuenta por el identificador, que puede ser el id de la cuenta o el host de la aplicación de la cuenta. |
+| UI - Account list | License Manager | Control de Acceso Web |
+| UI - Edit account | License Manager | Control de Acceso Web |
+| UI - Edit role | License Manager | Control de Acceso Web |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| View store sales stats | OMS | AccesoOMS | Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de pedidos. Muestra total de ventas, además de los detalles de los pedidos. |
+| Invoices List | Billing | Invoice | Clientes, responsables de billing y financiero tienen acceso. Permite la visualización de facturas. |
+| Edit Company Information | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite editar datos de una Company. |
+| Contracts List | Billing | Contracts | Clientes, responsables de billing y financiero tienen acceso. Visualización de todos los contratos (activos e inactivos) de una Company. |
+| Display Company info | Billing | Company | Clientes, responsables de billing y financiero tienen acceso.  Permite visualizar datos de una Company. |
+| Contacts List | Billing | Contacts | Clientes, responsables de billing y financiero tienen acceso.  Permite la visualización de la lista de contactos que reciben notificación por correo electrónico del cobro generado. |
+| Edit Contacts | Billing | Contacts | Solamente responsables de billing y financiero tienen acceso. Permite editar contactos que reciben notificación del cobro generado. |
+| Generate new Invoice | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Sector financiero puede generar un cobro en la Factura manualmente a través de los  contratos. |
+| Edit Company's Document | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite editar los datos de documento (CNPJ o CPF) de la Company, para donde se generará la factura. |
+| Add Account | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite agregar cuenta (account) para agrupar otras cuentas ya vinculadas con este cliente en un único billing. |
+| Delete Account | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite eliminar cuenta asociada con una Company. Company es la entidad creada para englobar diversas cuentas de la misma tienda. |
+| Save contracts | Billing | Contracts | Solamente responsables de billing, sales operations/growth y financiero tienen acceso. Permite crear nuevo contrato. |
+| Cancel Invoice Document | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Cancelar documento fiscal en las prefecturas, permite cancelar un documento fiscal aunque la factura ya se haya generado. |
+| Issue Invoice Document | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Se utiliza en casos específicos de países donde aún no existe la generación automática de documentos fiscales, dependiendo del sistema financiero. En este caso, puede ser generado manualmente. |
+| Conciliate Invoice | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. El default es marcar como pagado automáticamente, pero el cliente puede pagar aparte, dependiendo de la negociación. En este caso, el sector financiero tiene la facultad de marcar como pagado manualmente, conciliando las facturas. |
+| Generate Invoice Overdue without Interest | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Generar nuevo cobro con interés. Sí, con interés. |
+| Cancel Invoice | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Cancelar cobro en billing, permite cancelar una factura aunque ya haya sido generada. |
+| Change payment status | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. El sector financiero tiene la facultad de cambiar el status de pago de una Company, dependiendo de la negociación que haga con el cliente. |
+| Recalc Invoice | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. Generar nuevo cobro con interés. Sí, con interés. |
+| Get Unscrewed Dashboard Charges | Billing | Dashboard | Solamente responsables de billing y financiero tienen acceso. Acceso a dashboard externo al Admin, que visualiza facturas emitidas en ese momento, y qué cuentas son provisionadas en ese momento. |
+| Merge companies | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite la fusión entre dos Companies, unificando su billing. |
+| Split companies | Billing | Company | Solamente responsables de billing y financiero tienen acceso. Permite separar una Company única en Companies diferentes. |
+| Unpaid invoices | Billing | Invoice | Solamente responsables de billing y financiero tienen acceso. El sector financiero puede cancelar el pago de un cobro manualmente, en caso de que no se haya realizado o se haya realizado de manera equivocada. |
+| Get App | Log | Log Admin | Uso interno de VTEX. |
+| Create Table | Log | Log Admin | Uso interno de VTEX. |
+
+## Sales App - Sales Associate
+
+<div class="alert alert-warning">
+  <p>Los vendedores registrados en Sales App no tienen acceso a VTEX Admin, sólo a Sales App.</p>
+</div>
+
+Tabla de recursos:
+
+| Resource name | Product | Category | Description |
+|---|---|---|---|
+| Assisted Sales | Catalog | Televendas | Después de iniciar sesión, el usuario es redirigido a la tienda (accountname.myvtex.com). |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera una transacción. |
+| View order | OMS | AcessoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| Cancel order | OMS | AcessoOMS | Permite Cancelar pedido en el OMS. |
 
 ## IntegrationProfile - Fulfillment
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
 
 ## IntegrationProfile - Fulfillment Gateway
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Representa las operaciones transaccionales del gateway de pagos.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera una transacción.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite Cancelar pedido en el OMS.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Representa las operaciones transaccionales del gateway de pagos. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera una transacción. |
+| Notify payment | OMS | AccesoOMS | Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido. |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Cancel order | OMS | AccesoOMS | Permite Cancelar pedido en el OMS. |
 
 ## IntegrationProfile - Fulfillment Gateway GetOrder
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Representa las operaciones transaccionales del gateway de pagos.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera una transacción.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Representa las operaciones transaccionales del gateway de pagos. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera una transacción. |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
 
 ## IntegrationProfile - Fulfillment Gateway Oms
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Representa las operaciones transaccionales del gateway de pagos.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera una transacción.</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite informar facturas (NF) y datos para rastreo manualmente en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Notify reemburse</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite notificar una factura de entrada, indicando la entrada de nuevo de algo que ha sido reembolsado. Permite el input de una factura de devolución.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite Cancelar pedido en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite que el usuario se inscriba para recibir actualizaciones de los status de los pedidos en el Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite registrar alteraciones en el pedido (descuentos y/o cambios).</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Representa las operaciones transaccionales del gateway de pagos. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera una transacción. |
+| Change order workflow status | OMS | AccesoOMS | Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow. |
+| Notify payment | OMS | AccesoOMS | Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido. |
+| Notify invoice | OMS | AccesoOMS | Permite informar facturas (NF) y datos para rastreo manualmente en el OMS. |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Notify reemburse | OMS | AccesoOMS | Permite notificar una factura de entrada, indicando la entrada de nuevo de algo que ha sido reembolsado. Permite el input de una factura de devolución. |
+| Cancel order | OMS | AccesoOMS | Permite Cancelar pedido en el OMS. |
+| Order feed subscription | OMS | AccesoOMS | Permite que el usuario se inscriba para recibir actualizaciones de los status de los pedidos en el Order Feed. |
+| Change order | OMS | AccesoOMS | Permite registrar alteraciones en el pedido (descuentos y/o cambios). |
+| View store sales stats | OMS | AccesoOMS | Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos. |
 
 ## IntegrationProfile - Fulfillment Oms
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite informar facturas (NF) y datos para rastreo manualmente en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Notify reemburse</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite notificar una factura de entrada, indicando la entrada de nuevo de algo que ha sido reembolsado. Permite el input de una factura de devolución.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite Cancelar pedido en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite que el usuario se inscriba para recibir actualizaciones de los status de los pedidos en Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite registrar alteraciones en el pedido (descuentos y/o cambios).</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Change order workflow status | OMS | AccesoOMS | Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow. |
+| Notify payment | OMS | AccesoOMS | Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido. |
+| Notify invoice | OMS | AccesoOMS | Permite informar facturas (NF) y datos para rastreo manualmente en el OMS. |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| List Orders | OMS | AcessoOMS | Permite listar todos los pedidos de la cuenta. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Notify reemburse | OMS | AccesoOMS | Permite notificar una factura de entrada, indicando la entrada de nuevo de algo que ha sido reembolsado. Permite el input de una factura de devolución. |
+| Cancel order | OMS | AccesoOMS | Permite Cancelar pedido en el OMS. |
+| Order feed subscription | OMS | AccesoOMS | Permite que el usuario se inscriba para recibir actualizaciones de los status de los pedidos en Order Feed. |
+| Change order | OMS | AccesoOMS | Permite registrar alteraciones en el pedido (descuentos y/o cambios). |
+| View store sales stats | OMS | AccesoOMS | Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos. |
 
 ## IntegrationProfile - OrderSimulation
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
 
 ## Logistics - Full access
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página de ayuda inicial</td>
-  </tr>
-  <tr>
-    <td>Logistics full access</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite acceso pleno a todos los recursos de logística (visualización, creación, edición y cancelación de configuraciones).</td>
-  </tr>
-  <tr>
-    <td>Logistics viewer</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permiso de visualización del área inicial del módulo de logística.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory full access</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite el acceso pleno al inventario logístico (visualización, creación, edición y cancelación de configuraciones).</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory read only</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite solo la visualización del módulo de inventario.</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping full access</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite el acceso pleno a todas las funciones de envío del módulo de logística (creación, edición y cancelación de configuraciones).</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping read only</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Probar</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Home-page | Catalog | Administración | Página inicial |
+| Help-page | Catalog | Administración | Página de ayuda inicial |
+| Logistics full access | Logistics | Acceso a Logistics | Permite acceso pleno a todos los recursos de logística (visualización, creación, edición y cancelación de configuraciones). |
+| Logistics viewer | Logistics | Acceso a Logistics | Permiso de visualización del área inicial del módulo de logística. |
+| Logistics inventory full access | Logistics | Acceso a Logistics | Permite el acceso pleno al inventario logístico (visualización, creación, edición y cancelación de configuraciones). |
+| Logistics inventory read only | Logistics | Acceso a Logistics | Permite solo la visualización del módulo de inventario. |
+| Logistics shipping full access | Logistics | Acceso a Logistics | Permite el acceso pleno a todas las funciones de envío del módulo de logística (creación, edición y cancelación de configuraciones). |
+| Logistics shipping read only | Logistics | Acceso a Logistics | Probar |
 
 ## Logistics - Read only
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Logistics viewer</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permiso de visualización del área inicial del módulo de logística.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory read only</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite solo la visualización del módulo de inventario.</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping read only</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Probar</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Logistics viewer | Logistics | Acceso a Logistics | Permiso de visualización del área inicial del módulo de logística. |
+| Logistics inventory read only | Logistics | Acceso a Logistics | Permite solo la visualización del módulo de inventario. |
+| Logistics shipping read only | Logistics | Acceso a Logistics | Probar |
 
 ## OMS - Full access
 
 Tabla de recursos:
 
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administración</td>
-    <td>Página de ayuda inicial</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite informar facturas (NF) y datos para rastreo manualmente en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Logistics full access</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite acceso pleno a todos los recursos de logística (visualización, creación, edición y cancelación de configuraciones).</td>
-  </tr>
-  <tr>
-    <td>Notify reemburse</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite notificar una factura de entrada, indicando la entrada de nuevo de algo que ha sido reembolsado. Permite el input de una factura de devolución.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite Cancelar pedido en el OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite que el usuario se inscriba para recibir actualizaciones de los status de los pedidos en el Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite registrar alteraciones en el pedido (descuentos y/o cambios).</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory full access</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite acceso pleno al inventario logístico (visualización, creación, edición y cancelación de configuraciones).</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping full access</td>
-    <td>Logistics</td>
-    <td>Acceso a Logistics</td>
-    <td>Permite acceso pleno a todas las funciones de envío del módulo de logística (creación, edición y cancelación de configuraciones).</td>
-  </tr>
-</table>
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Home-page | Catalog | Administración | Página inicial |
+| Help-page | Catalog | Administración | Página de ayuda inicial |
+| Change order workflow status | OMS | AccesoOMS | Permite el acceso a las acciones dentro del workflow para cambiar el status del pedido, a través del botón de acciones en el workflow. |
+| Notify payment | OMS | AccesoOMS | Acceso al botón que notifica el pago al gateway manualmente en el área de pago dentro del pedido. |
+| Notify invoice | OMS | AccesoOMS | Permite informar facturas (NF) y datos para rastreo manualmente en el OMS. |
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| Logistics full access | Logistics | Acceso a Logistics | Permite acceso pleno a todos los recursos de logística (visualización, creación, edición y cancelación de configuraciones). |
+| Notify reemburse | OMS | AccesoOMS | Permite notificar una factura de entrada, indicando la entrada de nuevo de algo que ha sido reembolsado. Permite el input de una factura de devolución. |
+| Cancel order | OMS | AccesoOMS | Permite Cancelar pedido en el OMS. |
+| Order feed subscription | OMS | AccesoOMS | Permite que el usuario se inscriba para recibir actualizaciones de los status de los pedidos en el Order Feed. |
+| Change order | OMS | AccesoOMS | Permite registrar alteraciones en el pedido (descuentos y/o cambios). |
+| View store sales stats | OMS | AccesoOMS | Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos. |
+| Logistics inventory full access | Logistics | Acceso a Logistics | Permite acceso pleno al inventario logístico (visualización, creación, edición y cancelación de configuraciones). |
+| Logistics shipping full access | Logistics | Acceso a Logistics | Permite acceso pleno a todas las funciones de envío del módulo de logística (creación, edición y cancelación de configuraciones). |
 
 ## OMS - Read only
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Permite la visualización de todos los pedidos en el OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AccesoOMS</td>
-    <td>Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| View order | OMS | AccesoOMS | Permite la visualización de todos los pedidos en el OMS. |
+| View store sales stats | OMS | AccesoOMS | Muestra totalizadores dentro de la sección Todos los pedidos de Gestión de Pedidos. Muestra total de ventas, además de los detalles de los pedidos. |
 
 ## Seller Manager
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>View Seller</td>
-    <td>Seller Register</td>
-    <td>Seller Administration</td>
-    <td>Permite visualizar todos los sellers de la cuenta.</td>
-  </tr>
-  <tr>
-    <td>Save Seller</td>
-    <td>Seller Register</td>
-    <td>Seller Administration</td>
-    <td>Permite crear y editar todos los sellers de la cuenta.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| View Seller | Seller Register | Seller Administration | Permite visualizar todos los sellers de la cuenta. |
+| Save Seller | Seller Register | Seller Administration | Permite crear y editar todos los sellers de la cuenta. |
 
 ## User Administrator - RESTRICTED
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Save user</td>
-    <td>License Manager</td>
-    <td>Services access control</td>
-    <td>Cree usuarios, agregue o elimine roles de usuarios, edite datos de usuario, cree y cambie claves de aplicación.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Save user | License Manager | Services access control | Cree usuarios, agregue o elimine roles de usuarios, edite datos de usuario, cree y cambie claves de aplicación. |
 
 ## VTEX IO Admin
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Get resource by key</td>
-    <td>License Manager</td>
-    <td>Control de Acceso Servicios</td>
-    <td>Verifica permisos de acceso.</td>
-  </tr>
-  <tr>
-    <td>Read Workspace Apps</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite leer las apps instaladas en el workspace y sus dependencias directas e indirectas.</td>
-  </tr>
-  <tr>
-    <td>Link App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite listar los enlaces existentes y vincular y desvincular apps.</td>
-  </tr>
-  <tr>
-    <td>Install App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite la instalación y desinstalación de apps.</td>
-  </tr>
-  <tr>
-    <td>Vbase Read Only</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Acceso de solo lectura a vbase.</td>
-  </tr>
-  <tr>
-    <td>Vbase Read Write</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Acceso de lectura y escritura a vbase.</td>
-  </tr>
-  <tr>
-    <td>Read Workspace Services</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite leer las apps de infraestructura en el workspace.</td>
-  </tr>
-  <tr>
-    <td>Install Service</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite la instalación y desinstalación de apps.</td>
-  </tr>
-  <tr>
-    <td>Log Access - Read-only</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite leer logs de todas las aplicaciones.</td>
-  </tr>
-  <tr>
-    <td>Read Published Service</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite leer los datos de los servicios del registro de infraestructura.</td>
-  </tr>
-  <tr>
-    <td>Debug App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite conectar un debugger a una app vinculada.</td>
-  </tr>
-  <tr>
-    <td>Workspace CRUD</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite crear, eliminar y modificar workspaces.</td>
-  </tr>
-  <tr>
-    <td>Import Redirects</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Permite al usuario gestionar redirecciones con la interfaz de línea de comando de VTEX IO.</td>
-  </tr>
-  <tr>
-    <td>Manage A/B Test</td>
-    <td>VTEX IO</td>
-    <td>A/B Test
-    </td>
-    <td>Permite iniciar, terminar u obtener status de una prueba A/B.</td>
-  </tr>
-  <tr>
-    <td>Read logs</td>
-    <td>Application Logs Stream</td>
-    <td>Logs</td>
-    <td>Leer logs de apps de VTEX IO que pertenecen a esta cuenta.</td>
-  </tr>
-</table>
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Get resource by key | License Manager | Control de Acceso Servicios | Verifica permisos de acceso. |
+| Read Workspace Apps | VTEX IO | Infrastructure | Permite leer las apps instaladas en el workspace y sus dependencias directas e indirectas. |
+| Link App | VTEX IO | Infrastructure | Permite listar los enlaces existentes y vincular y desvincular apps. |
+| Install App | VTEX IO | Infrastructure | Permite la instalación y desinstalación de apps. |
+| Vbase Read Only | VTEX IO | Infrastructure | Acceso de solo lectura a vbase. |
+| Vbase Read Write | VTEX IO | Infrastructure | Acceso de lectura y escritura a vbase. |
+| Read Workspace Services | VTEX IO | Infrastructure | Permite leer las apps de infraestructura en el workspace. |
+| Install Service | VTEX IO | Infrastructure | Permite la instalación y desinstalación de apps. |
+| Log Access - Read-only | VTEX IO | Infrastructure | Permite leer logs de todas las aplicaciones. |
+| Read Published Service | VTEX IO | Infrastructure | Permite leer los datos de los servicios del registro de infraestructura. |
+| Debug App | VTEX IO | Infrastructure | Permite conectar un debugger a una app vinculada. |
+| Workspace CRUD | VTEX IO | Infrastructure | Permite crear, eliminar y modificar workspaces. |
+| Import Redirects | VTEX IO | Infrastructure | Permite al usuario gestionar redirecciones con la interfaz de línea de comando de VTEX IO. |
+| Manage A/B Test | VTEX IO | A/B Test | Permite iniciar, terminar u obtener status de una prueba A/B. |
+| Read logs | Application Logs Stream | Logs | Leer logs de apps de VTEX IO que pertenecen a esta cuenta. |
 
 ## VTEX Payment - Account Holder
 
@@ -1194,19 +343,9 @@ Este rol permite la lectura de información sobre la operación de VTEX Payment.
 
 ## Webservice - Full access
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabla de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nombre del recurso</th>
-    <th bgcolor="#efefef" >Producto</th>
-    <th bgcolor="#efefef" >Categoría</th>
-    <th bgcolor="#efefef" >Descripción</th>
-  </tr>
-  <tr>
-    <td>Webservice access</td>
-    <td>WebService</td>
-    <td>webservice</td>
-    <td>Permiso para utilizar cualquier request de SOAP.</td>
-  </tr>
-</table>    
+Tabla de recursos:
+
+| Nombre del recurso | Producto | Categoría | Descripción |
+|---|---|---|---|
+| Webservice access | WebService | webservice | Permiso para utilizar cualquier request de SOAP. |
+
diff --git a/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md b/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md
index c7bcb7871..9fa79e55d 100644
--- a/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md
+++ b/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md
@@ -3,8 +3,8 @@ title: '¿Cómo impedir que un transportista atienda cierto rango de códigos po
 id: 6GEYG5p9E4MOEy2qmY4uGa
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:39.807Z
-updatedAt: 2023-03-29T14:15:58.885Z
-publishedAt: 2023-03-29T14:15:58.885Z
+updatedAt: 2024-03-01T01:07:45.930Z
+publishedAt: 2024-03-01T01:07:45.930Z
 firstPublishedAt: 2019-01-24T22:03:33.994Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -33,3 +33,7 @@ Para ello, siga estos pasos:
 4. Cada una de estas líneas debe ser transformada en dos, de modo que el código postal 45920-000 sea ignorado. Por lo tanto, usted pasaría a tener: `ZipCodeStart` = __37900-001__ y `ZipCodeEnd` = __45919-999__ / `ZipCodeStart` = __45920-001__ y `ZipCodeEnd` = __97904-999__.
 
 Con ello, la planilla de flete pasaría a "saltar" el código postal 45920-000. Por lo tanto, ya no se consideraría como una opción de dirección atendida por ese transportista.
+
+<div class = "alert alert-info">
+Los ejemplos de códigos postales de este artículo se refieren a Brasil, cada país tiene su propio formato de código postal.
+</div>
diff --git a/docs/tutorials/es/price-divergence-rule.md b/docs/tutorials/es/price-divergence-rule.md
index fd3024536..dd749f188 100644
--- a/docs/tutorials/es/price-divergence-rule.md
+++ b/docs/tutorials/es/price-divergence-rule.md
@@ -3,8 +3,8 @@ title: 'Regla de Divergencia de precios'
 id: 6RlFLhD1rIRRshl83KnCjW
 status: PUBLISHED
 createdAt: 2021-12-25T20:10:25.853Z
-updatedAt: 2023-03-29T21:53:14.071Z
-publishedAt: 2023-03-29T21:53:14.071Z
+updatedAt: 2024-03-22T15:11:31.300Z
+publishedAt: 2024-03-22T15:11:31.300Z
 firstPublishedAt: 2021-12-25T21:05:20.600Z
 contentType: tutorial
 productTeam: Channels
@@ -29,7 +29,7 @@ La regla de Divergencia de precios se compone de una o varias reglas de autoriza
 - **Negar automáticamente:** los pedidos con una diferencia de precio dentro del rango definido se rechazan automáticamente y no se integran.
 - **Crear una tarea en VTEX DO para aprobación:** para diferencias de precio dentro del rango configurado, el pedido se integra pero queda pendiente de [autorización manual](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#autorizar-pedidos-manualmente) por parte de un usuario autorizado.
 
-![print_1_ES](https://drive.google.com/uc?export=download&id=1Ix_a3t24wvio_7BrSuxbzCC92J24iQZb)
+![price_divergence_rules_ES](//images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/8563ada94d5218580e946f92f1f7b210/price_divergence_rules_ES.png)
 
 Cuando no se ha [configurado la regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), los pedidos con errores de divergencia de precios se aprueban automáticamente. Esto se aplica a los _marketplaces_ VTEX, a los _marketplaces_ externos y a los conectores certificados (_partners_), pero no a los [conectores nativos](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex).
 
diff --git a/docs/tutorials/es/price-divergence-rules-beta.md b/docs/tutorials/es/price-divergence-rules-beta.md
index b59b5083a..eef1906c5 100644
--- a/docs/tutorials/es/price-divergence-rules-beta.md
+++ b/docs/tutorials/es/price-divergence-rules-beta.md
@@ -58,7 +58,7 @@ Para crear las reglas, realice los siguientes pasos:
    * Se crea una regla configurada automáticamente con un porcentaje de divergencia del 0% al 30%, la cual corresponde a la barra celeste.
 6. Para aumentar o disminuir el porcentaje de divergencia, haga clic en la barra y arrástrela desde los extremos, a menos " < " o a más " > ".
 7. Elija entre las siguientes acciones de reglas para pedidos: `Autorizar automáticamente`, `Negar automáticamente` o `Crear una tarea en VTEX DO para aprobar`.
-8. Para crear más reglas, haga clic en el icono <img class="shadow-4" src="https://https://images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> y repita los pasos 6 y 7.
+8. Para crear más reglas, haga clic en el icono <img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> y repita los pasos 6 y 7.
 9. Haga clic en `Guardar reglas`.
 
 Durante el proceso de creación de reglas, se muestran las siguientes pestañas: 
diff --git a/docs/tutorials/es/price-table-management-in-b2b-organizations.md b/docs/tutorials/es/price-table-management-in-b2b-organizations.md
new file mode 100644
index 000000000..6871eac37
--- /dev/null
+++ b/docs/tutorials/es/price-table-management-in-b2b-organizations.md
@@ -0,0 +1,47 @@
+---
+title: 'Gestionar tablas de precios en organizaciones B2B'
+id: 1iNpulqvLT2KJ2fnznpN4L
+status: PUBLISHED
+createdAt: 2024-06-25T18:44:58.230Z
+updatedAt: 2024-06-25T19:14:38.840Z
+publishedAt: 2024-06-25T19:14:38.840Z
+firstPublishedAt: 2024-06-25T19:14:38.840Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gestionar-tablas-de-precios-en-organizaciones-b2b
+locale: es
+legacySlug: gestionar-tablas-de-precios-en-organizaciones-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Las [tablas de precios](https://help.vtex.com/es/tutorial/criar-tabelas-de-precos?locale=pt) son fundamentales para una operación B2B en VTEX, ya que permiten personalizar las condiciones comerciales que se ofrecen a diferentes organizaciones al:
+
+- Definir los precios específicos de los productos.
+- Crear y gestionar varias tablas de precios.
+- Garantizar que cada cliente vea el valor correcto según la categoría.
+
+En las secciones a continuación se explica cómo gestionar las tablas de precios.
+- [Asociar tablas de precios a la organización](#asociar-tablas-de-precios-a-la-organización)
+- [Remover la asociación de tablas de precios](#remover-la-asociación-de-tablas-de-precios)
+
+## Asociar tablas de precios a la organización
+En VTEX, una organización es una entidad que representa una empresa. Para asociar tablas de precios a una organización sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Organizaciones** o escribe **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de Información de la organización.
+3. En esta página, haz clic en la pestaña **Tablas de precios**.
+4. Selecciona las tablas de precios deseadas en la lista **Disponible**.
+5. Haz clic en `Agregar a la org.` para incluirla en tu organización.
+6. Haz clic en `Guardar` en la parte superior derecha de la página.
+
+## Remover la asociación de tablas de precios
+Para remover la asociación de una tabla de precios de una organización, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Apps > Organizaciones y centros de costo B2B > Organizaciones** o escribe **Organizaciones** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el nombre de la organización deseada para acceder a la página de Información de la organización.
+3. En esta página, haz clic en la pestaña **Tablas de precios**.
+4. Selecciona las tablas de precios deseadas de la lista **Asignado a la organización**.
+5. Haz clic en `Remover de la org`.
+6. Haz clic en `Guardar` en la parte superior derecha de la página.
+
diff --git a/docs/tutorials/es/price-waterfall.md b/docs/tutorials/es/price-waterfall.md
index b131acdeb..024510eff 100644
--- a/docs/tutorials/es/price-waterfall.md
+++ b/docs/tutorials/es/price-waterfall.md
@@ -21,7 +21,7 @@ Con esta nueva feature, tenemos ahora una nueva entidad de precio llamada *Preci
 
 El siguiente gráfico explica cómo funciona la cascada de precios:
 
-![tabelapreco.es](https://images.ctfassets.net/alneenqid6w5/2rzzOs9CVogu74GM8Sih9s/9d095bddd449170787604aa602c9bb64/tabelapreco.es.png)
+![tabelapreco.es](//images.ctfassets.net/alneenqid6w5/2rzzOs9CVogu74GM8Sih9s/9d095bddd449170787604aa602c9bb64/tabelapreco.es.png)
 
 Cuando un precio para un SKU se solicita al módulo de precios:
 1. Un *Precio fijo* se selecciona segun sus criterios como **programación** y **cantidad mínima**.
diff --git a/docs/tutorials/es/prices-data-pipeline-beta.md b/docs/tutorials/es/prices-data-pipeline-beta.md
new file mode 100644
index 000000000..1bb804824
--- /dev/null
+++ b/docs/tutorials/es/prices-data-pipeline-beta.md
@@ -0,0 +1,92 @@
+---
+title: 'Precios Data Pipeline (beta)'
+id: 3NMGJ8dtv73Bwvo9PSz1fz
+status: PUBLISHED
+createdAt: 2024-06-21T14:58:43.084Z
+updatedAt: 2024-06-21T16:20:22.452Z
+publishedAt: 2024-06-21T16:20:22.452Z
+firstPublishedAt: 2024-06-21T15:27:43.768Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: precios-data-pipeline-beta
+locale: es
+legacySlug: precios-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+El conjunto de datos de precios incluye información histórica de los precios de cada SKU de la tienda de un retailer, lo que permite analizar los valores de markup y las tendencias mensuales de los precios.  
+
+En este artículo puedes consultar la siguiente información:  
+
+- [Características de los datos](#caracteristicas-de-los-datos)  
+- [Tabla pricing_latest](#tabla-pricing-latest)  
+- [Tabla pricing_historical](#tabla-pricing-historical)  
+- [Análisis con datos de precios](#analisis-con-datos-de-precios)  
+- [Correlaciones con otros datos](#correlaciones-con-otros-datos)  
+
+## Características de los datos
+
+| **Característica** | **Descripción**	|
+|:---------:|:-----:|
+| Origen del dato | Módulo Precios. |
+| Disponibilidad | Admin VTEX y APIs de precios. Es importante tener en cuenta que los datos facilitados por la API pueden no estar estructurados exactamente de la misma manera que en este conjunto de datos de Data Pipeline. |
+| Historial  | El historial de datos comienza en agosto de 2023. Para clientes que ya utilizan la plataforma VTEX, los datos se conservan durante dos años a partir de 2024. 	|
+| Menor intervalo de actualización posible | 1 hora. | 
+
+## Tabla pricing_latest  
+
+La tabla `pricing_latest` contiene datos correspondientes a los precios actuales de los productos de la tienda. Consulta a continuación los campos que componen la tabla.  
+
+| **Nombre de la columna**  | **Tipo de columna** | **Descripción de la columna** |
+|:----------:|:------------:|:-----------:|
+| account_name | character varying(255) | Nombre de la cuenta asociada al ítem. |
+| last_date  | date 	| Fecha y hora de la última modificación en el precio. |
+| sku_id | character varying(255)| Identificador del SKU.	|
+| batch_id  | character varying(255) 	| Identificador utilizado cuando los datos se cargan en la tabla para control de calidad de la ingesta de datos. |
+| listPrice | double precision | Precio de lista del SKU.|
+| costPrice | double precision  | Precio de costo del SKU. |
+| markup  | double precision | Markup del SKU. |
+| basePrice | double precision | Precio base del SKU.|
+| fixedPrices | super | Precio fijo.|
+
+## Tabla pricing_historical
+
+La tabla `pricing_historical` muestra un registro histórico de los precios de tu tienda. Consulta a continuación los campos que componen la tabla.  
+
+| **Nombre de la columna**  | **Tipo de columna** | **Descripción de la columna** |
+|:--------:|:---------:|:--------:|
+| account_name  | character varying(255) 	| Nombre de la cuenta asociada al ítem. |
+| date | date  | Fecha y hora de la última modificación en el precio.|
+| sku_id  | character varying(255) 	| Identificador del SKU. |
+| author_id | character varying(255) 	|Identificación del usuario que realizó modificaciones en el precio. |
+| batch_id | character varying(255) | Identificador utilizado cuando los datos se cargan en la tabla para control de calidad de la ingesta de datos. |
+| id  | character varying(255) 	| ID de la modificación de precio. |
+| listPrice | double precision  | Precio de lista del SKU. |
+| costPrice | double precision  | Precio de costo del SKU. |
+| markup    | double precision  | Markup del SKU.   |
+| basePrice | double precision  | Precio base del SKU.   |
+| fixedPrices| super  | Precio fijo. |
+
+## Análisis con datos de precios  
+
+Los datos de precios pueden utilizarse en los siguientes análisis:  
+- __Precio actual del SKU:__ evalúa el precio actual de un SKU específico o para toda una gama de productos.  
+- __Historial de precios de SKU:__ analiza el historial de precios de un SKU específico o de toda una gama de productos.  
+- __Precio del SKU por cuenta:__ para tiendas con varias cuentas VTEX, estos datos ayudan a comparar precios en varias tiendas.  
+
+## Correlaciones con otros datos  
+
+El conjunto de datos de precios se correlaciona con los siguientes conjuntos del ecosistema de datos de VTEX:  
+
+- **Interacción con datos de pedidos:** el análisis conjunto de los datos de pedidos proporciona información valiosa sobre las ventas de un producto en función del precio, lo que permite analizar su elasticidad.  
+- **Relación con el stock:** la integración con los datos del stock permite evaluar con precisión el valor total de tus activos.  
+- **Impacto en la tasa de conversión:** mediante el análisis de los datos de navegación y del embudo de conversión, se adquiere una comprensión más clara del impacto del precio en las tasas de conversión.  
+
+### Descubra otros conjuntos de datos
+
+- [Inventario](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Promociones](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/es/prices-settings.md b/docs/tutorials/es/prices-settings.md
index 272888719..a3c10b537 100644
--- a/docs/tutorials/es/prices-settings.md
+++ b/docs/tutorials/es/prices-settings.md
@@ -3,8 +3,8 @@ title: 'Configuración de precios'
 id: 3hbBtCzNUBrj8GaWgCtSWN
 status: PUBLISHED
 createdAt: 2020-10-14T18:43:49.750Z
-updatedAt: 2023-03-29T20:45:21.665Z
-publishedAt: 2023-03-29T20:45:21.665Z
+updatedAt: 2023-08-21T17:13:42.982Z
+publishedAt: 2023-08-21T17:13:42.982Z
 firstPublishedAt: 2020-10-22T19:38:48.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: configuracion-de-precios
 subcategory: 3O1NvPgBPqE0qU88MSQaie
 ---
 
-La página _Configuración de la tienda > Productos > Configuración__ en el Admin VTEX le permite cambiar la configuración general de los precios de forma rápida y sencilla.
+La página **Configuración de la tienda > Productos > Configuración de precios** en el Admin VTEX le permite cambiar la configuración general de los precios de forma rápida y sencilla.
 
 Usted puede definir el markup estándar y el límite de variación de precio de su tienda. También puede heredar los precios de la cuenta padre y sobrescribir los precios de sellers con los de su cuenta. 
 
diff --git a/docs/tutorials/es/prices.md b/docs/tutorials/es/prices.md
index b9f933ec4..eee7ddbce 100644
--- a/docs/tutorials/es/prices.md
+++ b/docs/tutorials/es/prices.md
@@ -3,8 +3,8 @@ title: 'Precios'
 id: tutorials_4393
 status: PUBLISHED
 createdAt: 2017-04-27T21:50:28.982Z
-updatedAt: 2021-12-20T21:12:57.515Z
-publishedAt: 2021-12-20T21:12:57.515Z
+updatedAt: 2023-08-21T17:24:39.459Z
+publishedAt: 2023-08-21T17:24:39.459Z
 firstPublishedAt: 2017-04-27T23:11:16.737Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 3pGCbMh80UueoeSqoAgSuS
 ---
 
 La gestión de los precios se realiza a través del módulo Pricing. 
-Impuestos y promociones en la plataforma VTEX se administran en el módulo *Tasas y Promociones*.
+Impuestos y promociones en la plataforma VTEX se administran en el módulo Promociones.
 
 Algunas ventajas de la nueva lista de precios son:
 
diff --git a/docs/tutorials/es/product-list.md b/docs/tutorials/es/product-list.md
index 27b028120..6aa6e1027 100644
--- a/docs/tutorials/es/product-list.md
+++ b/docs/tutorials/es/product-list.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Productos'
 id: 49vxWqoaWRZC4atwLz6cMg
 status: PUBLISHED
 createdAt: 2021-04-12T15:21:30.529Z
-updatedAt: 2023-03-24T14:24:33.863Z
-publishedAt: 2023-03-24T14:24:33.863Z
+updatedAt: 2023-11-22T13:59:30.669Z
+publishedAt: 2023-11-22T13:59:30.669Z
 firstPublishedAt: 2021-04-12T18:21:27.025Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 La página **Productos** le permite ver y gestionar la lista completa de productos registrados en su tienda, lo que simplifica la gestión del catálogo en Seller Portal. Puede acceder a la página a través del menú **Catálogo** en el Admin VTEX.
 
-![product-list-es](https://images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/2ae859a5052ac86fee7b4938ead9a6a8/product-list-es.png)
+![product-list-es](//images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/2ae859a5052ac86fee7b4938ead9a6a8/product-list-es.png)
 
 Desde la lista de productos puede llevar a cabo varias acciones:
 
@@ -30,6 +30,8 @@ Desde la lista de productos puede llevar a cabo varias acciones:
 
 Al hacer clic en el botón **CREAR PRODUCTO**, se abrirá la página para registrar un nuevo producto en el catálogo. Consulte el artículo [Cómo crear un producto](https://help.vtex.com/es/tutorial/como-crear-un-producto-beta--671zAWe0B9eCikzDu7kB1G) para obtener información sobre cómo realizar este procedimiento.
 
+<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+
 ## Buscar productos
 
 Para encontrar un producto específico, puede ingresar el ID o el nombre del producto en la barra de búsqueda en la parte superior de la lista de productos. Los resultados de la búsqueda se actualizan en tiempo real, es decir, a medida que escribe, la lista de productos mostrados se actualiza de acuerdo con el término de búsqueda.
diff --git a/docs/tutorials/es/products-and-skus-beta.md b/docs/tutorials/es/products-and-skus-beta.md
index 1e5d3ba2f..505caa7c2 100644
--- a/docs/tutorials/es/products-and-skus-beta.md
+++ b/docs/tutorials/es/products-and-skus-beta.md
@@ -3,8 +3,8 @@ title: 'Productos y SKUs (Beta)'
 id: 2ig7TmROlirWirZjFWZ3By
 status: PUBLISHED
 createdAt: 2022-11-30T17:55:25.970Z
-updatedAt: 2023-05-09T22:11:41.664Z
-publishedAt: 2023-05-09T22:11:41.664Z
+updatedAt: 2023-07-11T15:12:54.179Z
+publishedAt: 2023-07-11T15:12:54.179Z
 firstPublishedAt: 2022-11-30T19:04:31.183Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -21,7 +21,7 @@ subcategory: 6XPsLadoT3moZ7eTduCg3c
 
 La página **Productos y SKUs** permite ver y gestionar toda la lista de productos registrados en la tienda, incluyendo la información de los SKU, fecha de actualización y status. Para acceder a la página, ve a **Catálogo > Productos y SKUs**. 
 
-![produtos-skus-es](https://images.ctfassets.net/alneenqid6w5/1XLBRg7olhbAUmgkD6kb7K/12e3ea99b06515dd3b943ff0db2aff6d/produtos-skus-es.PNG)
+![products-skus-es](//images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/1d07f47ff5411ae7b264cd9c74fbb21a/products-skus-es.png)
 
 <div class="alert alert-info">
   <p>Esta página solo está disponible para las tiendas que operan con el <a href="https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">nuevo Admin VTEX</a>. Para acceder a esta página y formar parte de una nueva experiencia, únete al <a href="https://content.vtex.com/participe-do-programa-beta-es/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> del nuevo Admin VTEX.</p>
@@ -42,10 +42,8 @@ En la lista de productos, puedes ver la siguiente información:
 
 | **Columna** | **Descripción** |
 |----|----|
-| **Nombre** | Nombre que identifica el producto, definido al crearlo. Debajo del nombre, la página muestra el ID, es decir, el código identificador del producto. |
-| **SKU** | Muestra la opción `Ver SKUs` y, entre paréntesis, la cantidad de SKU registrados para el producto. Para más detalles sobre esta opción, consulta la sección [Ver la lista de SKUs](#ver-la-lista-de-skus). <br/><br/> Para dejar de ver los SKU referentes a un producto, haz clic en el botón `Ocultar SKUs`. |
+| **Nombre** | Nombre que identifica el producto, definido al crearlo. Debajo del nombre, la página muestra el ID, es decir, el código identificador del producto. <br/><br/> Junto al nombre, cada fila muestra una flecha <i class="fas fa-chevron-right"></i> para [ver la lista de SKUs](#ver-la-lista-de-skus) asociada al producto, un icono que representa [el status del producto](#monitorear-el-status-de-los-productos) y la imagen registrada para el producto. |
 | **Última actualización** | Fecha de [indexación](https://help.vtex.com/es/tutorial/entendendo-o-funcionamento-da-indexacao--tutorials_256) más reciente del producto. Para ver los detalles de este proceso, consulta la sección [Ver detalles de indexación](#ver-detalles-de-indexacion). |
-| **Status** | Estado actual del producto. Consulta los posibles status en la sección [Monitorear el status de los productos](#monitorear-el-status-de-los-productos). |
 
 ## Crear producto
 
@@ -65,7 +63,7 @@ Para encontrar un producto específico, puedes ingresar uno de los siguientes da
 
 A continuación, haga clic en los criterios que desea utilizar para la búsqueda, como se ilustra en la imagen siguiente:
 
-![facelift-product-search-es](https://images.ctfassets.net/alneenqid6w5/PCBjrNpVcVr5Z4x3RdTgW/28d533d52dc826a1c30af973c8d0470c/facelift-product-search-es.gif)
+![products-skus-search-es](//images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/e533bd234ce131fe2b6eb8f6705f77ba/search-es.gif)
 
 La lista de productos mostrados se actualizará en función de su búsqueda. 
 
@@ -103,9 +101,9 @@ Para ver el status de los SKU de un producto, consulta la sección [Ver la lista
 
 ## Ver la lista de SKUs
 
-Al hacer clic en `Ver SKUs` en la fila de un producto de la lista, la plataforma muestra una lista con todos los SKU registrados para ese producto.
+Al hacer clic en la flecha <i class="fas fa-chevron-right"></i> en la fila de un producto de la lista, la plataforma muestra una lista con todos los SKU registrados para ese producto.
 
-![sku-quick-actions-es](https://images.ctfassets.net/alneenqid6w5/71pxP9DeCFZ9UrQdl67r9X/969ed548f9c8991955e35317ab81f05f/sku-quick-actions-es.gif)
+![sku-actions-es](//images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/5e99e7874f909914f6c489f40f336152/sku-actions-es.gif)
 
 En la lista de SKU, se puede ver la siguiente información:
 
@@ -118,6 +116,8 @@ En la lista de SKU, se puede ver la siguiente información:
 * **Nombre:** nombre del SKU.
 * <svg xmlns="http://www.w3.org/2000/svg" width="1.25rem" height="1.25rem" fill="currentColor" viewBox="0 0 256 256" class=" admin-ui-c-dnTJPl"><rect width="16rem" height="16rem" fill="none"></rect><path d="M224,177.32117V78.67873a8,8,0,0,0-4.07791-6.9726l-88-49.5a8,8,0,0,0-7.84418,0l-88,49.5A8,8,0,0,0,32,78.67873v98.64244a8,8,0,0,0,4.07791,6.97261l88,49.5a8,8,0,0,0,7.84418,0l88-49.5A8,8,0,0,0,224,177.32117Z" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></path><polyline points="222.897 74.626 128.949 128 33.108 74.617" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></polyline><line x1="128.94915" y1="127.99996" x2="128.01036" y2="234.82127" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line></svg> &nbsp; <strong>Editar stock:</strong> dirige a la pantalla de gestión de stock en el Admin VTEX para editar la cantidad del SKU disponible para la venta en stock. Consulta el artículo [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) para más información.
 * <svg xmlns="http://www.w3.org/2000/svg" width="1.25rem" height="1.25rem" fill="currentColor" viewBox="0 0 256 256" class=" admin-ui-c-dnTJPl"><rect width="16rem" height="16rem" fill="none"></rect><line x1="128" y1="72" x2="128" y2="88" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line><line x1="128" y1="168" x2="128" y2="184" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line><circle cx="128" cy="128" r="96" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></circle><path d="M104,168h36a20,20,0,0,0,0-40H116a20,20,0,0,1,0-40h36" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></path></svg> &nbsp;<strong>Editar precios:</strong> dirige a la **Lista de precios** en el Admin VTEX para editar los precios registrados para el SKU.
+* <i class="far fa-clone"></i> __Copiar código del SKU:__ copia el ID del SKU al portapapeles.
+* <i class="far fa-eye"></i> __Activar__ / <i class="far fa-eye-slash"></i> __Desativar:__ activa o desactiva el SKU en la tienda.
 
 ## Editar productos
 
@@ -148,7 +148,7 @@ Al hacer clic en el menú  de la fila de un producto y seleccionar **Ver detalle
 
 Esta pestaña de la ventana modal muestra la lista de SKU asociados al producto y sus detalles de indexación.
 
-![catalog-price-inventory-es](https://images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/5c7748263994690cfb4ab39922ca19a9/preco-inventario-es.PNG)
+![catalog-price-inventory-es](//images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/5c7748263994690cfb4ab39922ca19a9/preco-inventario-es.PNG)
 
 Al hacer clic en la flecha `>` en la fila de cada SKU, puedes ver una tabla con la siguiente información:
 
@@ -163,7 +163,7 @@ Al hacer clic en la flecha `>` en la fila de cada SKU, puedes ver una tabla con
 
 Esta pestaña de la ventana modal muestra el log, es decir, el registro técnico que detalla la indexación referente al producto y los SKU relacionados.
 
-![indexed-log-es](https://images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/f1925d2f1b8ed02bae5b34254e8f7a39/log-indexacao-es.PNG)
+![indexed-log-es](//images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/f1925d2f1b8ed02bae5b34254e8f7a39/log-indexacao-es.PNG)
 
 ## Más información
 
diff --git a/docs/tutorials/es/promotion-alerts-beta.md b/docs/tutorials/es/promotion-alerts-beta.md
index 6606c4d1c..301af1db5 100644
--- a/docs/tutorials/es/promotion-alerts-beta.md
+++ b/docs/tutorials/es/promotion-alerts-beta.md
@@ -29,7 +29,7 @@ Si solo se configura la acción de alerta por email, es posible que se realicen
 
 Para acceder a la página en el Admin VTEX, ve a *Promociones > Alerta de promociones*. Se mostrará la interfaz a continuación:
 
-![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
+![simuladordepromocoes gerenciar](//images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
 
 La siguiente tabla proporciona la descripción de las columnas de la lista de promociones:
 
diff --git a/docs/tutorials/es/promotion-list-beta.md b/docs/tutorials/es/promotion-list-beta.md
index 866840ed7..bb933ebb0 100644
--- a/docs/tutorials/es/promotion-list-beta.md
+++ b/docs/tutorials/es/promotion-list-beta.md
@@ -3,8 +3,8 @@ title: 'Lista de Promociones'
 id: 4yB7nNdliiFxBTXE19GCIi
 status: PUBLISHED
 createdAt: 2022-05-05T13:39:53.273Z
-updatedAt: 2023-03-02T15:34:23.200Z
-publishedAt: 2023-03-02T15:34:23.200Z
+updatedAt: 2023-07-24T13:34:09.177Z
+publishedAt: 2023-07-24T13:34:09.177Z
 firstPublishedAt: 2022-05-05T13:52:17.590Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -30,7 +30,7 @@ La página muestra la lista con las promociones registradas en tu tienda y su in
 | `Hasta` | Fecha de fin de la promoción.  |
 | `Status` | Status de la promoción, que puede ser: <p> __Activa:__ la promoción está activada.</p> <p>__Programada:__ la promoción está programada.</p> <p>__Pausada:__ la promoción está pausada. <p>__Completada:__ la promoción ha finalizado.</p> |
 
-![listadepromocoes es](https://images.ctfassets.net/alneenqid6w5/223hOuKKb0a23uFeYIr7UU/ae1fa5b782b350cdda3458e28459d51e/listadepromocoes_es.gif)
+![listadepromocoes es](//images.ctfassets.net/alneenqid6w5/223hOuKKb0a23uFeYIr7UU/ae1fa5b782b350cdda3458e28459d51e/listadepromocoes_es.gif)
 
 Puedes ordernar la lista de promociones por nombre, fechas o status. Para ordenarlas, haz clic en el título de la columna que tiene la información que deseas utilizar como criterio de ordenación.
 
@@ -82,7 +82,7 @@ El archivo contiene la siguiente información sobre cada promoción:
 
 ## Uso de las promociones
 
-![usodaspromoções en](https://images.ctfassets.net/alneenqid6w5/51IiIaxilx3SqfVdRtiX1A/15a27215629ed81ae47e6582bd6d9261/usodaspromo____es_en.JPG)
+![usodaspromoções en](//images.ctfassets.net/alneenqid6w5/51IiIaxilx3SqfVdRtiX1A/15a27215629ed81ae47e6582bd6d9261/usodaspromo____es_en.JPG)
 
 Para ver el total de promociones activas en tu tienda y el espacio restante para nuevas promociones, haz clic en <i class="fas fa-chart-line"></i> `Uso de las promociones`.
 
@@ -90,7 +90,7 @@ El número máximo de promociones activas por defecto es de 100. Si necesitas au
 
 ## Filtrar promociones
 
-![filtrodepromocoes es](https://images.ctfassets.net/alneenqid6w5/6EuQui1lZ8MfnkvdvXh87S/2e90d2071d83698429988c2124acf67f/filtrodepromocoes_es.gif)
+![filtrodepromocoes es](//images.ctfassets.net/alneenqid6w5/6EuQui1lZ8MfnkvdvXh87S/2e90d2071d83698429988c2124acf67f/filtrodepromocoes_es.gif)
 
 La lista de promociones se puede filtrar según tus necesidades, utilizando los siguientes filtros:  
 
diff --git a/docs/tutorials/es/promotion-summary.md b/docs/tutorials/es/promotion-summary.md
index e64807207..438aa84cb 100644
--- a/docs/tutorials/es/promotion-summary.md
+++ b/docs/tutorials/es/promotion-summary.md
@@ -63,17 +63,17 @@ El resumen de la promoción puede mostrar tres tipos diferentes de alertas. Mira
 Las alertas de riesgo alto indican configuraciones o errores de registro importantes que deben ser revisados, ya que pueden comprometer el rendimiento de la promoción y, en consecuencia, el margen de la operación de la tienda.
 
 Ejemplo:
-![alert-alto-risco-ES](https://images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/380a8e538396c9210c5b741a8cc3bc38/image.png)
+![alert-alto-risco-ES](//images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/380a8e538396c9210c5b741a8cc3bc38/image.png)
 
 ### Riesgo medio
 Las alertas de riesgo medio muestran avisos de configuraciones que pueden causar efectos no deseados en la promoción.
 
 Ejemplo:
-![alert-medio-risco-ES](https://images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/7b21608671db91c4e1bc0a00f9ccfa31/image.png)
+![alert-medio-risco-ES](//images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/7b21608671db91c4e1bc0a00f9ccfa31/image.png)
 
 ### Riesgo bajo 
 Las alertas de riesgo bajo presentan información relevante sobre la configuración de la promoción, lo que puede contribuir a mejorar el rendimiento.
 
 Ejemplo:
-![alert-baixo-risco-ES](https://images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/b5c1d499a549c2c56f84a4b286ce1a84/image.png)
+![alert-baixo-risco-ES](//images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/b5c1d499a549c2c56f84a4b286ce1a84/image.png)
 
diff --git a/docs/tutorials/es/promotions-beta.md b/docs/tutorials/es/promotions-beta.md
index 8e7812ce7..48460ed9a 100644
--- a/docs/tutorials/es/promotions-beta.md
+++ b/docs/tutorials/es/promotions-beta.md
@@ -32,20 +32,20 @@ La página de inicio presenta la lista de promociones en una malla que permite v
 - Duplicar o archivar promociones a través del botón <i class="fas fa-ellipsis-v"></i>
 - Gestionar las condiciones de la promoción haciendo clic en cualquier lugar de la línea de la malla (consulte la sección [Nueva promoción](#nueva-promocion) para obtener detalles sobre las condiciones de la promoción).
 
-![promobeta1 acoes lista promocoes ES](https://images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b8b32c9c2d6f39763ade1630fc34023f/promobeta1_acoes_lista_promocoes_ES.gif)
+![promobeta1 acoes lista promocoes ES](//images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b8b32c9c2d6f39763ade1630fc34023f/promobeta1_acoes_lista_promocoes_ES.gif)
 
 La lista de promociones se puede filtrar y ordenar según sus necesidades. Es posible filtrar por *Efecto*, *Estado*, *Fecha de inicio*, *Fecha de caducidad* o *Política comercial*.
 
-![promobeta2 filtros lista promocoes ES](https://images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/28326256cde9d433ece9b634ceab8205/promobeta2_filtros_lista_promocoes_ES.gif)
+![promobeta2 filtros lista promocoes ES](//images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/28326256cde9d433ece9b634ceab8205/promobeta2_filtros_lista_promocoes_ES.gif)
 
 El orden puede ser ascendente o descendente a partir de la información básica de la promoción, simplemente haciendo clic en el título.
 
-![promobeta3 ordenacao lista promocoes ES](https://images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5660b538ad60cc95faa676c4aa724d76/promobeta3_ordenacao_lista_promocoes_ES.gif)
+![promobeta3 ordenacao lista promocoes ES](//images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5660b538ad60cc95faa676c4aa724d76/promobeta3_ordenacao_lista_promocoes_ES.gif)
 
 ## Nueva promoción
 Las variedades de condiciones para crear promociones se traducen en campos presentes en la pantalla de __Nueva Promoción__. La creación de una promoción que se ajuste a los estándares deseados se realiza de forma sencilla, rellenando los campos en una única pantalla a la que se accede a través del botón __NUEVA PROMOCIÓN__ de la página de inicio.
 
-![promobeta4 botao novapromocao ES](https://images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/cf5363e79041f050f0b164735e8244cd/promobeta4_botao_novapromocao_ES.png)
+![promobeta4 botao novapromocao ES](//images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/cf5363e79041f050f0b164735e8244cd/promobeta4_botao_novapromocao_ES.png)
 
 Tanto las condiciones de la nueva promoción como los campos de la pantalla están separados por grupos, que son:
 
diff --git a/docs/tutorials/es/promotions-overview.md b/docs/tutorials/es/promotions-overview.md
index 005c3190c..34cb500d1 100644
--- a/docs/tutorials/es/promotions-overview.md
+++ b/docs/tutorials/es/promotions-overview.md
@@ -3,8 +3,8 @@ title: 'Visión General Promociones'
 id: 3PeHVYcooLIDmA33IAnjhm
 status: PUBLISHED
 createdAt: 2023-03-29T19:29:50.947Z
-updatedAt: 2023-03-29T19:33:24.646Z
-publishedAt: 2023-03-29T19:33:24.646Z
+updatedAt: 2023-09-13T22:35:44.331Z
+publishedAt: 2023-09-13T22:35:44.331Z
 firstPublishedAt: 2023-03-29T19:31:43.053Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,8 +19,6 @@ Una promoción es un descuento que se concede al cliente, asociado a uno o vario
 
 En el menú **Promociones** de su Admin, puedes configurar una promoción con restricciones de listas de productos, listas de clientes, rangos de códigos postales, valor mínimo del carrito, entre otros.
 
-![visao-geral-promo-ES](https://images.ctfassets.net/alneenqid6w5/6FHow2OrXNqAoiKaJngwPU/b042023b3d3624f98bde582d8817b41d/image.png)
-
 A continuación, encontrarás más detalles sobre las diferentes secciones y páginas de este menú.
 
 ## Promociones
diff --git a/docs/tutorials/es/promotions-simulator-beta.md b/docs/tutorials/es/promotions-simulator-beta.md
index 2947b23d6..eab4a279b 100644
--- a/docs/tutorials/es/promotions-simulator-beta.md
+++ b/docs/tutorials/es/promotions-simulator-beta.md
@@ -1,10 +1,10 @@
 ---
-title: 'Simulador de Promociones (Beta)'
+title: 'Simulador de Promociones '
 id: 4zc8SNqjqeIJ0ZRMhjlnvy
 status: PUBLISHED
 createdAt: 2022-09-13T21:22:59.620Z
-updatedAt: 2022-09-27T19:37:29.437Z
-publishedAt: 2022-09-27T19:37:29.437Z
+updatedAt: 2024-03-13T19:31:16.281Z
+publishedAt: 2024-03-13T19:31:16.281Z
 firstPublishedAt: 2022-09-13T22:59:58.058Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -12,96 +12,90 @@ author: 46G4yHIZerH7B9Jo0Iw5KI
 slug: simulador-de-promociones-beta
 locale: es
 legacySlug: simulador-de-promociones-beta
-subcategory: 6iTRZiMeCGXYiO2ckABFZi
+subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-<div class = "alert alert-info">
-Este módulo se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Si tienes alguna duda, ponte en contacto <a href="https://help.vtex.com/es/support">con nuestro Soporte. </a>
+<div class="alert alert-warning">
+  <p>Los usuarios deben tener un <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol</a> con permisos para ver el módulo <strong>Promociones</strong> en el Admin VTEX para poder acceder al <strong>Simulador de promociones</strong>.</p>
 </div>
 
-<div class = "alert alert-warning">
-Los usuarios deben tener un <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">rol</a> con permisos para ver el módulo Promociones en el Admin VTEX para poder acceder al Simulador de promociones.
-</div>
+El **Simulador de promociones** es una herramienta que permite ver las promociones creadas en tu tienda VTEX que se aplicaron al carrito y sus condiciones de activación. También puedes probar la aplicación de promociones antes de activarlas, incluyendo promociones inactivas y programadas.
 
-El **Simulador de promociones** es una herramienta que permite ver las promociones creadas en la plataforma VTEX que se aplicaron al carrito y sus condiciones de activación. Como las promociones pueden configurarse de diversas maneras, es importante poder ver la [competencia](https://help.vtex.com/es/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270), la acumulación de promociones durante la compra y las causas de activación de dichas promociones.
+Como las promociones pueden configurarse de diversas maneras, es importante poder ver la [competencia](https://help.vtex.com/es/tutorial/como-funciona-la-competencia-de-promociones--tutorials_2270) y la acumulación de promociones durante la compra y los activadores de dichas promociones.
 
-Al usar el simulador, tendrás autonomía para gestionar las promociones de tu tienda y dirigirlas según tu estrategia de negocio.
+El **Simulador de promociones** está disponible para todas las tiendas VTEX mediante [Cartman](https://help.vtex.com/es/tutorial/configurar-cartman--1ACMTStZYkMqB0lTgwg451), una herramienta para los administradores de la tienda en la etapa de checkout. Para acceder al simulador, sigue los pasos a continuación:
 
-También puedes [gestionar promociones]((#gestionar-promociones)) qque estén activas o inactivas, haciendo clic en el botón `Gestionar promociones`.
+1. En la barra superior del Admin VTEX, haz clic en el botón `Vista previa `para abrir la página de acceso restringido de tu tienda.
 
-La interfaz del simulador cuenta con cinco columnas:
+   Si lo prefieres, puedes acceder a la página directamente utilizando la URL `https://{nombredelacuenta}.myvtex.com/`, sustituyendo `{nombredelacuenta}` por el nombre de tu cuenta VTEX.
 
-| **Columnas** |**Descripción**| 
-| ----------- | ------------- |
-| **Producto** | Lista de los productos en el carrito |
-| **Preceio** | Precio anterior (De) y precio final (Por) de la promoción aplicada |
-| **Cantidad** | Cantidad de ítems en el carrito |
-| **Total** | Precio total que se cobrará por el producto, considerando los descuentos de la promoción y la cantidad de ítems |
-| **Descuento** | Status del descuento en el carrito, el cual puede ser: `Aplicado` ou `No aplicado`. El status `Aplicado` indica que al menos una promoción fue aplicada al producto |
+2. Agrega productos al carrito y accede al checkout mediante `https://{nombredelacuenta}.myvtex.com/checkout/#/cart`.
 
-<div class = "alert alert-info">
-En la esquina derecha de la pantalla, encontrarás un botón megáfono <i class="fas fa-bullhorn"></i> que te permitirá enviar tu opinión sobre tu experiencia usando el <b>Simulador de promociones</b>.
-</div>
+3. Haz clic en el botón azul <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> en la parte inferior derecha de la página para iniciar Cartman.
+4. Haz clic en **Simulador de promociones**.
 
-Para aprovechar los beneficios de esta funcionalidad, dividimos este artículo en dos partes:
+   En la nueva ventana, verás una lista de los productos que están en tu carrito. Podrás ver todas las promociones aplicadas y aplicables a cada uno de los ítems.
 
-- [Acceder al Simulador de promociones](#acceder-al-simulador-de-promociones)
-- [Gestionar promociones](#gestionar-promociones)
+![Simulator-promo-es-gif-1](//images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/61187eee812b80ec80769704578aad35/simulador-promo-es-230706.gif)
 
-## Acceder al Simulador de promociones
+La interfaz del **Simulador de promociones** presenta la siguiente información:
 
-Para acceder a esta funcionalidad, primero debes [configurar Cartman](https://help.vtex.com/es/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451), una herramienta que simula, comparte e investiga carritos de tiendas VTEX.
+| Columna | Descripción |
+|---|---|
+| **Producto** | Lista de los productos en el carrito. |
+| **Precio** | Precio anterior a las promociones (**De**) y precio final (**Por**) con las promociones aplicadas. |
+| **Cantidad** | Cantidad de ítems en el carrito. |
+| **Total** | Precio total que se cobrará por el producto, considerando los descuentos de la promoción y la cantidad de ítems. |
+| **Descuento** | Status del descuento en el carrito, el cual puede ser: `Aplicado` o `No aplicado`. El status `Aplicado` indica que al menos una promoción fue aplicada al producto. |
 
-Al entrar al simulador, verás una lista con los productos en tu carrito. Podrás ver todas las promociones que pueden aplicarse en cada uno de los ítems, junto con una casilla de selección <i class="fas fa-check-square"></i> en la promoción aplicada.
+<div class="alert alert-info">
+  <p>En la esquina derecha de la pantalla, encontrarás un botón de megáfono que te permitirá enviar tu opinión sobre tu experiencia usando el <strong>Simulador de promociones</strong>.</p>
+</div>
 
-La herramienta cuenta con una barra de búsqueda para encontrar promociones por nombre de producto o por nombre de promoción. Además, puedes filtrar las promociones por **Tipo de promoción** y **Descuento**.
+### Actualizar el simulador
 
-Al hacer clic en cada producto, podrás ver más información sobre las promociones que se pueden aplicar, detalles de tu selección y la condición para activarlas.
+Si necesitas agregar o remover ítems del carrito, puedes mantener la ventana del simulador abierta. Después de editar el carrito, haz clic en `Actualizar` en el **Simulador de promociones** para analizar las promociones aplicadas al carrito.
 
-![simuladordepromocoes acessar](https://images.ctfassets.net/alneenqid6w5/7piR33ciR1x0givnQyxbk7/cdb47a1c812d3fa244aeb6127be100ee/simuladordepromocoes_acessar.gif)
+### Buscar y filtrar promociones
 
-Una vez configurado Cartman, sigue los pasos a continuación para acceder al Simulador de promociones:
+La herramienta tiene una barra de búsqueda que permite buscar promociones por nombre del producto o nombre de la promoción. Además, puedes filtrar las promociones por **Tipo de promoción** ([Regular](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), [Comprar juntos](https://help.vtex.com/es/tutorial/comprar-juntos-registro-de-promocion--tutorials_323), [Más por menos](https://help.vtex.com/es/tutorial/mas-por-menos--tutorials_3255), [Descuento progresivo](https://help.vtex.com/es/tutorial/descuento-progresivo--tutorials_324), [Compra y gana](https://help.vtex.com/es/tutorial/como-funciona-la-promocion-compre-y-gane--tutorials_322) o [Promoción de campaña](https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume)) y **Descuento** (Aplicado o No aplicado).
 
-1. Accede al carrito de compras de tu tienda VTEX.
-2. Agrega los productos que deseas probar.
-3. En el carrito de compras, abre `Cartman`. 
-4. Haz clic en la opción **Ver detalles de la promoción**.
-5. Se mostrarán las promociones aplicadas en el carrito. Para obtener más detalles de las promociones, haz clic en `Ver detalles.`.
-  > Serás redireccionado al **Simulador de promociones**. Al entrar al simulador, verás una lista con los productos en tu carrito. Podrás ver todas las promociones que pueden aplicarse en cada uno de los ítems, junto con una casilla de selección en la promoción aplicada.
-6. Si cambias los productos en el carrito, haz clic en `Actualizar` para cargar la nueva información.
+### Ver detalles de las promociones aplicadas
 
-### Editar promoções
+Al hacer clic en cada producto, puedes ver más información sobre las promociones aplicadas, detalles sobre sus efectos y por qué se activaron. También puedes ver las promociones no aplicadas y los motivos por los que no se aplicaron.
+
+### Editar promociones
 
 Para editar una promoción, sigue los pasos a continuación:
 
-1. En el **Simulador de promociones**, selecciona un producto.
-2. Haz clic en el nombre de la promoción que deseas editar.
-  > Serás redireccionado al formulario de la promoción.
-3. Edita los [campos de la promoción](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#quais-os-dados-gerais-desta-promocao).
+1. En el **Simulador de promociones**, haz clic en la línea del producto o en la flecha <i class="fas fa-chevron-right"></i>.
+2. Haz clic en el nombre de la promoción que deseas editar. Se te redirigirá al formulario de la promoción.
+3. Edita los [campos de la promoción](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#1-cuales-son-los-datos-generales-de-la-promocion).
 4. Al terminar de realizar los cambios, haz clic en `Guardar`.
 
-## Gestionar promociones
+### Simular promociones
+
+El **Simulador de promociones** permite probar la aplicación de otra promoción o simular lo que sucedería al desactivar promociones aplicadas. Para utilizarlo, haz clic en el botón `Seleccionar promociones` en la parte superior derecha de la página según se muestra en la imagen a continuación.
 
-Si deseas simular una nueva promoción o gestionar las promociones existentes, debes hacer clic en el botón `Gestionar promociones`, ubicado en la esquina superior derecha de la página.
+![ui-Simulator-promo-es-gif-2](//images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/488e9025886fa184fa38c06b55129139/ui-simulador-promo-es-230706.gif)
 
-Podrás ver todas las promociones activas, pausadas, programadas o completadas en el carrito. De esta manera, podrás probar un estado futuro de la tienda.
+Para ejecutar una simulación, sigue estos pasos:
 
-![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/6J3Bp4YcEZ6V5cgVj4dnhM/c0a6896fcec1bb0cf3bbc6ea3362d19f/simuladordepromocoes_gerenciar.gif)
+1. En el **Simulador de promociones**, haz clic en `Seleccionar promociones` en la parte superior derecha de la página.
 
-Para probar una promoción, sigue los pasos a continuación:
+   Verás una lista de todas las promociones registradas en tu tienda, incluyendo las activas, pausadas, programadas y finalizadas.
 
-1. En el **Simulador de promociones**, haz clic en `Gestionar promociones`.
-2. Selecciona una o más promociones, sin importar su status.
-3. Haz clic en el botón `Probar`.
+2. Selecciona una o más promociones para simular su aplicación al carrito. También puedes desmarcar promociones activas si deseas simular el desactivarlas.
+3. Haz clic en el botón `Simular`.
 
-Para ver si se aplicó la promoción que probaste, mira el status de la columna **Descuento** o haz clic en el producto para obtener más detalles.
+   Verás el resultado de la simulación a partir de las promociones seleccionadas. Para ver si las promociones probadas se aplicaron a los ítems del carrito en la simulación, fíjate en el status de la columna **Descuento** o haz clic en el producto.
 
-<div class = "alert alert-info">
-Se pueden aplicar promociones en productos que ya tienen una promoción activa. A pesar del conflicto que se genera entre las promociones, el sistema de VTEX siempre elegirá la promoción más beneficiosa para los clientes de tu tienda, considerando el precio total de los ítems o el envío.
+<div class="alert alert-info">
+  <p>Se pueden aplicar promociones en productos que ya tienen una promoción activa. A pesar del conflicto que se genera entre las promociones, el sistema de VTEX siempre elegirá la promoción más beneficiosa para los clientes de tu tienda, tomando en consideración el precio total de los ítems o el envío.</p>
 </div>
 
-### Learn more
+### Más información
 
- * [Cómo funcionan las promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR)
- * [Promociones para escenarios específicos](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy)
- * [Configure Cartman](https://help.vtex.com/es/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451)
+* [Cómo funcionan las promociones](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR)
+* [Promociones para escenarios específicos](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy)
+* [Configurar Cartman](https://help.vtex.com/es/tutorial/configurar-cartman--1ACMTStZYkMqB0lTgwg451)
diff --git a/docs/tutorials/es/promotions-simulator.md b/docs/tutorials/es/promotions-simulator.md
index d8af37dc6..5d5a66131 100644
--- a/docs/tutorials/es/promotions-simulator.md
+++ b/docs/tutorials/es/promotions-simulator.md
@@ -24,12 +24,12 @@ El **Simulador de promociones** te permite ver las promociones aplicadas a tu ca
 Para utilizar esta funcionalidad, primero debes [configurar Cartman](https://help.vtex.com/es/tutorial/configurar-cartman--1ACMTStZYkMqB0lTgwg451), una herramienta que simula, comparte e investiga los carritos. Con Cartman configurado, sigue los pasos a continuación para acceder al **Simulador de Promociones**.
 
 1. Añade a tu carrito los productos incluidos en las promociones de la tienda.
-2. En el carrito, haz clic en el botón <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para abrir Cartman.
+2. En el carrito, haz clic en el botón <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para abrir Cartman.
 3. Haz clic en la opción `Ver detalles de la promoción`.
 4. Esta ventana muestra las promociones aplicadas al carrito. Para más detalles, haz clic en <i class="fas fa-search"></i>`Ver detalles`.
-![cartman-analisador-promoção-ES](https://images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/f4cd037dc329105e0dd0cc2a08bfb75c/Screen_Shot_2022-03-07_at_11.14.14.png)
+![cartman-analisador-promoção-ES](//images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/f4cd037dc329105e0dd0cc2a08bfb75c/Screen_Shot_2022-03-07_at_11.14.14.png)
 5. Luego se mostrará la ventana **Simulador de Promociones**.
-![analisador-promoção-ES](https://images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/37b6391ca94a73ffaed7618a5b15dcb6/image.png)
+![analisador-promoção-ES](//images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/37b6391ca94a73ffaed7618a5b15dcb6/image.png)
 
 En esta ventana, puedes consultar la siguiente información:
 
diff --git a/docs/tutorials/es/promotions.md b/docs/tutorials/es/promotions.md
new file mode 100644
index 000000000..c0b3793b0
--- /dev/null
+++ b/docs/tutorials/es/promotions.md
@@ -0,0 +1,112 @@
+---
+title: 'Promociones Data Pipeline (Beta)'
+id: 3WZ1syNucDFdvVhfKtA6Qd
+status: PUBLISHED
+createdAt: 2024-02-02T18:02:01.395Z
+updatedAt: 2024-06-21T16:25:25.745Z
+publishedAt: 2024-06-21T16:25:25.745Z
+firstPublishedAt: 2024-05-27T19:26:59.739Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: promociones
+locale: es
+legacySlug: promociones
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+El conjunto de datos de promociones está constituido por cuatro tablas: `promotion_archived`, `promotion_created`, `promotion_removed` y `promotion_unarchived`. Estas cuatro tablas abarcan todo el ciclo de vida de las campañas promocionales, desde su lanzamiento hasta su archivo, reactivación o remoción, proporcionando una visión integral de las estrategias promocionales de la tienda.
+
+En esta sección puedes consultar la siguiente información:
+
+- [Características de los datos](#características-de-los-datos)
+- [Tabla promotion_archived](#tabla-promotion_archived)
+- [Tabla promotion_created](#tabla-promotion_created)
+- [Tabla promotion_removed](#tabla-promotion_removed)
+- [Tabla promotion_unarchived](#tabla-promotion_unarchived)
+- [Análisis con datos de promociones](#analisis-con-datos-de-promociones)
+- [Correlaciones con otros datos](#correlaciones-con-otros-datos)
+
+## Características de los datos
+
+|**Característica**|**Descripción**|
+| - | - |
+|**Origen**|Proceden del [módulo Promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR) en el Admin VTEX.|
+|**Disponibilidad**|Se puede acceder a los datos de promociones a través del Admin VTEX y también a través de las [API de Promotions](https://developers.vtex.com/docs/guides/promotions-overview).|
+|**Historial**|Los datos se conservan durante dos años, a partir de 2024 para clientes que ya utilizan la plataforma VTEX.|
+|**Intervalo mínimo de actualización**|Una hora.|
+
+## Tabla promotion_archived
+
+La tabla `promotion_archived` registra todas las promociones archivadas. Incluye detalles de las promociones removidas temporal o permanentemente del uso activo, lo que permite un historial y análisis de las campañas anteriores.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de columna** | **Descripción de la columna** |
+|:---:|:---:|:---:|
+| **version** | character varying(16383) | Versión de los datos de la tabla, útil para control de versiones y compatibilidad. |
+| **ingestion_time** | timestamp without time zone | Fecha y hora de inserción de los datos en la tabla. |
+| **payload** | super | Conjunto de datos efectivamente almacenados en la tabla, abarcando información diversa. |
+| **batch_id** | character varying(13) | Identificador de lote de datos, utilizado para realizar un seguimiento de la ingesta y gestión de los datos. |  
+
+## Tabla promotion_created  
+
+La tabla `promotion_created` contiene información sobre nuevas promociones creadas. Es esencial para realizar un seguimiento del lanzamiento de nuevas campañas promocionales, ofreciendo insights sobre estrategias e iniciativas de marketing actuales.  
+Consulta a continuación los campos que componen la tabla:
+
+| **Nombre de la columna** | **Tipo de columna** | **Descripción de la columna** |
+|:---:|:---:|:---:|
+| **version** | character varying(16383) | Indica la versión de los datos presentes en la tabla. |
+| **ingestion_time** | timestamp without time zone | Representa el momento en que se insertaron los datos en la tabla. |
+| **payload** | super | Contiene el conjunto de datos o información efectivamente cargados en la tabla. |
+| **batch_id** | character varying(13) | Identificador único del lote de datos, utilizado para hacer seguimiento y gestionar la ingesta de datos. |  
+
+## Tabla promotion_removed  
+
+La tabla `promotion_removed` registra las promociones eliminadas o desactivadas, proporcionando un análisis de aquellas que fueron descontinuadas y permitiendo comprender los motivos detrás de esas decisiones.  
+Consulta a continuación los campos que componen la tabla:  
+
+| **Nombre de la columna** | **Tipo de columna** | **Descripción de la columna** |
+|:---:|:---:|:---:|
+| **version** | character varying(16383) | Versión de los datos. |
+| **ingestion_time** | timestamp without time zone | Fecha y hora de la ingesta de datos. |
+| **payload** | super | Contenido de los datos insertados. |
+| **batch_id** | character varying(13) | ID de control del lote de datos. |  
+
+## Tabla promotion_unarchived  
+
+La tabla `promotion_unarchived` almacena promociones que han sido reactivadas o eliminadas del archivo. Proporciona información sobre campañas reintroducidas, lo que ofrece perspectivas sobre estrategias para reutilización o revisión de promociones anteriores.  
+Consulta a continuación los campos que componen la tabla:
+
+| **Nombre de la columna** | **Tipo de columna** | **Descripción de la columna** |
+|:---:|:---:|:---:|
+| **version** | character varying(16383) | Versión de los datos de la tabla. |
+| **ingestion_time** | timestamp without time zone | Fecha y hora de inserción de los datos en la tabla. |
+| **payload** | super | Conjunto de datos efectivamente almacenados en la tabla. |
+| **batch_id** | character varying(13) | Identificador del lote de datos insertados en la tabla. |  
+
+## Análisis con datos de promociones
+
+El conjunto de datos de promociones puede utilizarse para realizar los siguientes análisis:  
+
+- **Análisis del ciclo de vida de la promoción:** comparar la frecuencia y duración de las promociones para evaluar la longevidad y el éxito de las campañas.  
+- **Tasa de reactivación de promociones:** analizar el número de promociones reactivadas para evaluar la eficacia de reutilizar o revisar campañas anteriores.  
+- **Tendencias de remoción de promociones:** realizar un seguimiento del número y tipos de promociones descontinuadas para comprender las razones de su remoción y ajustar las estrategias futuras.  
+- **Impacto de nuevas promociones:** comparar los lanzamientos de promociones con las ventas y el tráfico para evaluar su impacto inmediato.  
+
+## Correlaciones con otros datos
+
+La relación entre el conjunto de datos de promociones y otros conjuntos de datos es esencial. A continuación, se muestran algunos ejemplos:  
+
+- **Datos de [pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv):** analizar la influencia de las promociones en los pedidos ayuda a comprender su impacto sobre las ventas.  
+- **Datos de [stock](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2):** la correlación con el stock es fundamental para garantizar la disponibilidad de los productos promocionados.  
+- **Análisis de marketing y publicidad**: la integración con estos datos permite medir la efectividad de las promociones para atraer tráfico y engagement.  
+- **Datos de [navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) en el sitio web:** analizar el efecto de las promociones en la navegación permite obtener insights sobre el comportamiento de los clientes y la eficacia de la exhibición de las promociones.  
+
+### Descubra otros conjuntos de datos
+
+- [Stock](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navegación](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Precios](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+
diff --git a/docs/tutorials/es/protection-against-transaction-attacks.md b/docs/tutorials/es/protection-against-transaction-attacks.md
index d4a77c4a5..b39797e22 100644
--- a/docs/tutorials/es/protection-against-transaction-attacks.md
+++ b/docs/tutorials/es/protection-against-transaction-attacks.md
@@ -3,7 +3,7 @@ title: 'Protección contra los ataques a las transacciones'
 id: 62oQBmi7UZlYlgb0Ha1hZ3
 status: DRAFT
 createdAt: 2021-10-25T19:02:59.690Z
-updatedAt: 2021-12-10T13:52:07.652Z
+updatedAt: 2024-03-01T15:58:16.139Z
 publishedAt: 
 firstPublishedAt: 
 contentType: tutorial
@@ -36,9 +36,9 @@ Para activar la protección, mira el paso a paso que se muestra a continuación.
 4. En la esquina superior derecha, haz clic en el ícono de configuración;
 5. En __Protección contra ataques__, haz clic en el botón para activarla (el color verde indica "activada").
 
-![proteção-botao-configurações](https://images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
+![proteção-botao-configurações](//images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
 
-![opción-de-protección-habilitada1](https://images.ctfassets.net/alneenqid6w5/6svPWoUMebewsgVcBGkig5/c5aa662b0d3f17f6131e1bf702f0e49a/opci__n-de-protecci__n-habilitada1.png)
+![opción-de-protección-habilitada1](//images.ctfassets.net/alneenqid6w5/6svPWoUMebewsgVcBGkig5/c5aa662b0d3f17f6131e1bf702f0e49a/opci__n-de-protecci__n-habilitada1.png)
 
 ### ¿Cómo desactivar la protección contra los ataques a las transacciones?
 
@@ -69,13 +69,13 @@ Para acceder a esta información, mira el paso a paso que se muestra a continuac
 6. Para seleccionar __Amenazas detectadas__ o __Amenazas neutralizadas__, haga clic en una de las flechas de la derecha. 
 7. Verifica los detalles de los eventos en la ventana emergente que aparece.
 
-![opción-protección-histórico1](https://images.ctfassets.net/alneenqid6w5/49x3IUoxJ7uydixZWsrzAJ/250619d85b728b32e7d8db8faaa1cfbe/opci__n-protecci__n-hist__rico1.png)
+![opción-protección-histórico1](//images.ctfassets.net/alneenqid6w5/49x3IUoxJ7uydixZWsrzAJ/250619d85b728b32e7d8db8faaa1cfbe/opci__n-protecci__n-hist__rico1.png)
 
-![pantalla-protección-histórico1](https://images.ctfassets.net/alneenqid6w5/7pybJ37CWRAnquFaSHXtYE/1f2e631ac9836dd9ef0f239a262ba205/pantalla-protecci__n-hist__rico1.png)
+![pantalla-protección-histórico1](//images.ctfassets.net/alneenqid6w5/7pybJ37CWRAnquFaSHXtYE/1f2e631ac9836dd9ef0f239a262ba205/pantalla-protecci__n-hist__rico1.png)
 
-![pantalla-amenaza-potencial1](https://images.ctfassets.net/alneenqid6w5/78mfTPLB4MFJfpJ7EAkJtY/0a00d39504db054aa5961d856b86a342/pantalla-amenaza-potencial1.png)
+![pantalla-amenaza-potencial1](//images.ctfassets.net/alneenqid6w5/78mfTPLB4MFJfpJ7EAkJtY/0a00d39504db054aa5961d856b86a342/pantalla-amenaza-potencial1.png)
 
-![pantalla-amenaza-neutralizada1](https://images.ctfassets.net/alneenqid6w5/1TAQRzC5ef1bmdZ3CFEIMa/384388f887f08d882df4da136ba34dd8/pantalla-amenaza-neutralizada1.png)
+![pantalla-amenaza-neutralizada1](//images.ctfassets.net/alneenqid6w5/1TAQRzC5ef1bmdZ3CFEIMa/384388f887f08d882df4da136ba34dd8/pantalla-amenaza-neutralizada1.png)
 
 ### Artículos relacionados
 - [¿Qué es una solución antifraude?](https://help.vtex.com/es/tutorial/o-que-e-antifraude)
diff --git a/docs/tutorials/es/ready-to-dispatch.md b/docs/tutorials/es/ready-to-dispatch.md
index 6a9e1bcfa..4e76818b2 100644
--- a/docs/tutorials/es/ready-to-dispatch.md
+++ b/docs/tutorials/es/ready-to-dispatch.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Listos para despacho'
 id: 5YOZV7Aotv3pap0fGNESDs
 status: PUBLISHED
 createdAt: 2021-11-11T20:13:17.128Z
-updatedAt: 2023-06-09T12:57:15.077Z
-publishedAt: 2023-06-09T12:57:15.077Z
+updatedAt: 2024-02-29T19:44:25.837Z
+publishedAt: 2024-02-29T19:44:25.837Z
 firstPublishedAt: 2021-11-11T20:44:13.846Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/received-skus-beta.md b/docs/tutorials/es/received-skus-beta.md
new file mode 100644
index 000000000..b7ce9a9d8
--- /dev/null
+++ b/docs/tutorials/es/received-skus-beta.md
@@ -0,0 +1,222 @@
+---
+title: 'SKUs recebidos'
+id: 4hxDUmbgOEVFSTU2Eqi8DK
+status: PUBLISHED
+createdAt: 2024-04-29T13:48:12.818Z
+updatedAt: 2024-06-25T19:27:37.735Z
+publishedAt: 2024-06-25T19:27:37.735Z
+firstPublishedAt: 2024-04-29T14:16:25.091Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: skus-recebidos-beta
+locale: es
+legacySlug: anuncios-recebidos
+subcategory: 
+---
+
+La página SKUs recibidos permite al [marketplace](https://help.vtex.com/es/tutorial/visao-geral-marketplace--40Zd0z9h2RXsM9uMUp3kEb) ver, priorizar y catalogar los ítems enviados por sus sellers. Esto posibilita la creación de nuevos productos y su asociación con SKU o productos ya existentes para ponerlos a disposición para la venta. Accede a la página a través del Admin VTEX en __Marketplace > SKUs recibidos__  o ingresa __SKUs recibidos__ en la barra de búsqueda del Admin.  
+
+La catalogación puede realizarse de forma manual o automática, [mediante uno o varios matchers](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt), y también mediante [autoApprove](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions/#put-/suggestions/configuration/autoapproval/toggle). También existe la posibilidad de utilizar herramientas externas para realizar esta operación.  
+
+En este artículo encontrarás una visión general sobre la [Estructura de la página](#estructura-de-la-pagina), [Priorizar la catalogación](#priorizar-la-catalogacion) y [Catalogación de ítems](#catalogacion-de-items).  
+
+## Estructura de la página
+
+La página SKUs recibidos se organiza en pestañas correspondientes a los distintos status posibles de un anuncio:  
+
+- [Pendientes](#pendientes)  
+- [Problemas](#problemas)  
+- [Aprobados](#aprobados)  
+- [Procesando](#procesando)  
+- [Bloqueados](#bloqueados)  
+
+Dentro de cada pestaña, además de visualizar la lista de SKU, es posible filtrar anuncios, revisar las especificaciones de cada uno y verificar el porcentaje de SKUs recibidos que se encuentran en ese status específico.  
+
+![skus-recibidos-pestanas-es](//images.ctfassets.net/alneenqid6w5/4jNrRvJsZgja1LuSz204P1/3757c1f533031f535b2c233eb55f3d08/skus-recibidos-pestanas-es.png)
+
+### Pendientes
+
+En la pestaña __Pendientes__, el marketplace puede consultar la lista de todos los anuncios enviados por un seller y que aún no han sido aprobados. Los anuncios se pueden filtrar por __seller, categoría, marca y stock.__ También pueden llevarse a cabo las siguientes acciones en anuncios de esta pestaña: __Crear nuevo producto, Asociar con producto o SKU, Rechazar para corrección o Rechazar y bloquear.__
+
+Cada fila de la lista representa un producto con la siguiente información:  
+
+- __Anuncio:__ muestra el nombre del producto.  
+- __ID del SKU:__ número que identifica el producto.  
+- __Seller:__ nombre del seller que envió el anuncio.  
+- __Categoría:__ categoría en la que el producto está registrado, si ya se realizó el mapeo. Si el mapeo de categoría aún no se ha realizado, se mostrará el mensaje No mapeada.  
+- __Precio:__ precio del producto enviado por el seller.  
+- __Stock:__ cantidad disponible de ese producto.  
+
+Para consultar todas las especificaciones de un producto, haz clic en el nombre del producto deseado y se abrirá una nueva ventana con toda la información.  
+
+![skus-recibidos-analisis-es](//images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/d789b0d0ad6be43a7eb75ee0b6a0c637/skus-recibidos-analisis-es.png)
+
+### Problemas
+
+En la pestaña __Problemas__ están disponibles todos los anuncios que aún no se aprobaron debido a problemas que requieren corrección por parte del seller. Los filtros, acciones y campos de identificación disponibles en la pestaña **[Pendientes](#pendientes)** son similares a los de la pestaña Problemas.  
+
+<div class="alert alert-info">
+La acción de solicitar corrección no está disponible en la pestaña <b>Problemas.</b>
+</div>  
+
+Para identificar el problema de un anuncio solo hay que hacer clic en el nombre del producto deseado. Se mostrará una nueva ventana con la información del producto, el mensaje de error y el revisor del anuncio.  
+
+![skus-recibidos-problemas-analisis-es](//images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/9209d4817cfdb057283cb12a6bdb99a6/skus-recibidos-problemas-analisis-es.png)
+
+### Aprobados
+
+En la pestaña __Aprobados__ se muestran los SKUs recibidos y aprobados. En esta pestaña puedes __Editar el producto, Ver la página del producto__ y __filtrar anuncios por seller, categoría y marca.__
+
+Cada fila de la lista representa un producto con la siguiente información:   
+
+- __Anuncio:__ muestra el nombre del producto.  
+- __ID del SKU:__ número que identifica el producto.  
+- __Seller:__ nombre del seller que envió el anuncio.  
+- __Categoría:__ indica la categoría a la que pertenece el producto.  
+
+### Procesando  
+
+En la pestaña __Procesando__ se encuentran los SKUs recibidos que están siendo evaluados por el sistema VTEX.  En esta pestaña solo se puede visualizar la información, con opciones de filtros por __seller__ y __fecha de envío__ del producto.  
+
+Cada fila de la lista representa un producto con la siguiente información:  
+
+- __Anuncio:__ muestra el nombre del producto.  
+- __ID de SKU:__ número que identifica el producto.  
+- __Seller:__ nombre del seller que envió el anuncio.  
+- __Fecha de envío:__ muestra la fecha en que se envió el anuncio al marketplace.  
+
+<div class="alert alert-info">
+Los anuncios aquí listados están siendo evaluados por Matcher y por Offer Quality o autoApprove, en caso de que se hayan configurado. Tras la evaluación, el anuncio puede pasar a las pestañas <b>Pendientes, Problemas, Aprobados o Bloqueados</b>, dependiendo del cumplimiento de los requisitos establecidos.
+</div>  
+
+### Bloqueados
+
+En la pestaña __Bloqueados__ pueden consultarse los anuncios enviados por el seller que han sido bloqueados por el marketplace. En esta pestaña puedes __desbloquear__ un anuncio y también filtrar anuncios por __seller__ y __revisor.__
+
+Cada fila de la lista representa un producto con la siguiente información:  
+
+- __Anuncio:__ muestra el nombre del producto.  
+- __ID del SKU:__ número que identifica el producto.  
+- __Seller:__ nombre del seller que envió el anuncio.  
+- __Revisor:__ nombre del agente que realiza la revisión del anuncio.  
+
+## Priorizar la catalogación 
+
+La lista de SKUs recibidos se ha desarrollado para priorizar y agilizar la catalogación de los ítems que la componen. Al hacer clic en cualquier SKU de la lista, accedes a un resumen de la información principal del SKU por medio de una barra lateral, sin salir de la página del listado. En la barra lateral también se muestra el porcentaje de match asignado al SKU por el matcher instalado en tu tienda.  
+
+Algunas de las funcionalidades que ayudan en el proceso de priorización son:  
+
+### Filtros  
+
+En cada una de las pestañas presentadas en la sección anterior es posible combinar diferentes filtros para configurar la visualización deseada de SKU.  
+
+Por ejemplo, si se selecciona la marca ABC y la categoría Medias, en la vista se mostrarán todos los SKU de la marca ABC que pertenezcan a la categoría Medias.  
+
+Cabe señalar que las opciones de filtros se basan en los SKU disponibles en la lista. Ejemplo: un marketplace está conectado a los sellers A, B y C, pero solo existen SKU pendientes de los sellers B y C. Esto significa que la selección del filtro en la pestaña [Pendientes](#pendientes) solo mostrará los resultados de los sellers B y C.  
+
+### Orden  
+
+De manera predeterminada, los ítems más recientemente agregados se muestran primero en la lista. Sin embargo, el orden también puede determinarse por __Precio__ y __Stock.__   
+
+En este caso, los ítems se ordenarán de forma ascendente o descendente al hacer clic en __Precio__ o __Stock.__
+
+![skus-recibidos-ord-es](//images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/a44da25a3176f26b0ab2e318ef171375/skus-recibidos-ord-es.png)
+
+## Catalogación de ítems  
+
+Todos los SKU que se muestran en la lista ya están disponibles para catalogación. No obstante, se recomienda realizar el [mapeo de categorías y marcas](https://help.vtex.com/es/tutorial/mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta--6NU8LwR6i0tTb8nk30bnbE) antes de este paso para agilizar el proceso de catalogación.  
+
+<div class="alert alert-warning">
+Los anuncios de la pestaña Pendientes permanecen disponibles solamente durante 30 días. Pasado este periodo, expiran automáticamente y el seller tendrá que volver a enviarlos.
+</div>
+
+### Opciones de catalogación  
+
+Para catalogar un anuncio, accede a la página __SKUs recibidos__ en el Admin VTEX haciendo clic en __Marketplace > SKUs recibidos__ o ingresando __SKUs recibidos__ en la barra de búsqueda del Admin.  
+<div class="alert alert-info">
+Todos los anuncios de la pestaña Pendientes se pueden catalogar individualmente o en masa.
+</div>
+
+Las acciones disponibles para la catalogación son:  
+
+- __Crear nuevo producto:__ crea un nuevo SKU en el catálogo, lo que a su vez crea un nuevo producto. Recomendamos utilizar esta opción cuando un determinado producto aún no existe en el catálogo del marketplace. Para llevar a cabo esta acción, sigue los pasos a continuación:
+
+1. Selecciona los SKU deseados.  
+2. Haz clic en el botón <i class="fas fa-plus" aria-hidden="true"></i> `Crear nuevo producto`.  
+3. Completa los campos __Categoría__ y __Marca__ para cada producto. Si el mapeo ya se ha realizado previamente, estos campos ya estarán completados.  
+4. Haz clic en `Aprobar`.  
+
+<div class="alert alert-info">
+Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
+</div>
+
+![skus-recibidos-crear-nuevo-producto-es](//images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/4b686bea24c2df091c8739ecc398a645/skus-recibidos-crear-nuevo-producto-es.png)
+
+- __Asociar a un producto existente:__ crea una relación entre el producto del seller y un producto que ya existe en el catálogo del marketplace. Para llevar a cabo esta acción, sigue los pasos a continuación:  
+
+1. Selecciona los SKU deseados.  
+2. Haz clic en el botón <i class="fas fa-link" aria-hidden="true"></i> `Asociar al producto`.  
+3. Ingresa el ID del producto al que se asociará.  
+4. Haz clic en `Aprobar`.  
+
+#### Caso de uso  
+
+Imagina el siguiente escenario: el marketplace ya tiene el SKU Camisa blanca en las tallas S, M y L. Pero recientemente, el seller ha agregado al stock las tallas XS y XL del mismo producto, Camisa blanca.  
+
+Al crear una nueva asociación, las nuevas tallas se agrupan con las demás que ya estaban previamente registradas. Por lo tanto, el producto estará disponible en las tallas XS, S, M, L y XL.  
+
+<div class="alert alert-info">
+Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
+</div>
+
+![skus-recibidos-vincular-al-producto-es](//images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/7bf8dee7e2b09fa4c36aefa485a461c8/skus-recibidos-vincular-al-producto-es.png)
+
+- __Asociar a un SKU existente:__ crea una relación entre el SKU del seller y un SKU que ya existe en el catálogo del marketplace. Para llevar a cabo esta acción, sigue los pasos a continuación:  
+
+1. Selecciona los productos deseados.  
+2. Haz clic en el botón <i class="fas fa-link" aria-hidden="true"></i> Asociar al SKU.  
+3. Ingresa el ID del SKU que se asociará a cada SKU que se está aprobando.  
+4. Haz clic en Aprobar.  
+
+#### Caso de uso  
+
+Imagina el siguiente escenario: un marketplace tiene el smartphone XYZ con 128 GB de memoria del Seller 1.  
+
+No obstante, es posible que este marketplace reciba el mismo SKU de 128 GB del Seller 2. Para evitar duplicar el catálogo, el marketplace debe asociar estos SKU.  
+
+<div class="alert-info">
+Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
+</div>
+
+![skus-recibidos-vincular-al-sku-es](//images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/5d8fc3e9ba0d93b2c2f9186d73f4f69b/skus-recibidos-vincular-al-sku-es.png)
+
+- __Bloquear:__ esta acción bloquea los anuncios seleccionados, impidiendo su reprocesamiento automático. Para llevar a cabo esta acción, sigue los pasos a continuación:  
+
+1. Selecciona los productos deseados.  
+2. Haz clic en el botón `Rechazar y bloquear `.  
+3. Rellena el campo __Motivo del bloqueo__ (opcional). O preenchimento é opcional.  
+4. Haz clic en `Rechazar`.  
+
+Cuando el marketplace bloquea un SKU, significa que la próxima vez que el seller envíe sus productos, aquellos que hayan sido bloqueados ya no serán incluidos entre los enviados. Es posible desbloquear un SKU a través de la API REST, si el marketplace desea volver a recibirlo como sugerencia del seller. Para más información sobre la aprobación de SKU, consulta nuestra documentación [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).  
+
+<div class="alert alert-info">
+Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>. Los anuncios bloqueados se mostrarán en la pestaña <b>Bloqueados</b>.
+</div>
+
+![skus-recibidos-rechazar-y-bloquear-es](//images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/bb22e0cfd4ff98513d5da66696b2e5d5/skus-recibidos-rechazar-y-bloquear-es.png)
+
+- Rechazar para corrección: rechaza el anuncio y envía al seller una solicitud para corregir la información. Para llevar a cabo esta acción, sigue los pasos a continuación:  
+
+1. Selecciona los SKU deseados.  
+2. Haz clic en el botón `Rechazar para corrección`.  
+3. Completa el campo __Correcciones__ con la información que el seller debe corregir.  
+4. Haz clic en `Rechazar`.  
+
+<div class="alert alert-info">
+Esta acción puede realizarse en la pestaña <b>Pendientes</b>. Los anuncios que necesitan corrección se mostrarán en la pestaña <b>Problemas</b>.
+</div>  
+
+![skus-recibidos-rechazar-para-correccion-es](//images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/bc526e9f64a729781f5ebebcd6a62ee0/skus-recibidos-rechazar-para-correccion-es.png)
+
+- __Aprobación automática:__ también puedes configurar la aprobación automática de SKU de un seller específico, independientemente de la puntuación asignada por Matcher. Esta acción solo puede realizarse a través de la API REST. Para saber más, consulta la documentación de [Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions).  
diff --git a/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
new file mode 100644
index 000000000..aeaf3e84d
--- /dev/null
+++ b/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -0,0 +1,117 @@
+---
+title: 'Recupera checkouts abandonados con WhatsApp AI Campaigns'
+id: 20i0zLQHt72LKzVEmk1CRZ
+status: PUBLISHED
+createdAt: 2024-06-25T11:27:41.160Z
+updatedAt: 2024-06-25T16:27:45.935Z
+publishedAt: 2024-06-25T16:27:45.935Z
+firstPublishedAt: 2024-06-25T15:29:15.011Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: recupera-checkouts-abandonados-con-whatsapp-ai-campaigns
+locale: es
+legacySlug: recupera-checkouts-abandonados-con-whatsapp-ai-campaigns
+subcategory: 4SC2gPmUH3cHD5HjGfQ5Vg
+---
+
+
+WhatsApp AI Campaigns es una funcionalidad desarrollada por VTEX para recuperar checkouts abandonados. 
+
+Cuando un usuario abandona la página de checkout de la compra, la plataforma identifica esta acción. Si el usuario no regresa para completar la compra en el plazo de una hora, la funcionalidad le envía un recordatorio a través de WhatsApp.
+
+Los principales beneficios de la funcionalidad son:
+
+- **Mejora de la experiencia del cliente:** los mensajes pueden personalizarse para aumentar la relevancia y reforzar la relación con la marca.
+
+**Aumento de las tasas de conversión y ventas:** incentiva a los clientes a volver a la página de checkout para finalizar su compra, aumentando así las ventas y las tasas de conversión de los retailers.
+
+<div class = "alert alert-info">
+WhatsApp AI Campaigns solamente está disponible para tiendas que utilizan <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> y no tienen personalizaciones en Checkout.
+</div>
+
+## Activar WhatsApp AI Campaigns
+
+Para activar la funcionalidad WhatsApp AI Campaigns debes [instalar la aplicación Connectly](#installing-app-conectly) y luego [configurar un número de WhatsApp en la aplicación](#configurar-nuevo-numero-de-whatsapp).
+
+### Instalar la aplicación Connectly
+
+Para instalar la aplicación Connectly sigue los pasos que se indican a continuación:
+
+1. Accede a la [App Store](https://apps.vtex.com/) de VTEX.
+
+2. Ingresa Connectly en la barra de búsqueda.
+
+3. Haz clic en la aplicación Connectly y, a continuación, en `Obtener app`.
+
+4. Haz clic en `Finalizar compra`.
+
+5. Haz clic en `Ir a la página de instalación`, y serás redirigido a la sección **Mis Apps** en el Admin VTEX.
+
+6. En la página de instalación de la app Connectlyvtex, haz clic en `Instalar`.
+
+7. Haz clic en `Guardar`.
+
+### Configurar un nuevo número de WhatsApp
+
+Para configurar un nuevo número de WhatsApp necesitarás acceso de administrador a tu perfil de Meta. Sigue las instrucciones para configurar un nuevo número y completar la asociación:
+
+<div class = "alert alert-info">
+Se recomienda crear un nuevo número de teléfono exclusivamente para vincularlo a WhatsApp Business. Esto ayuda a evitar pérdidas de acceso a números utilizados anteriormente para otros fines.
+</div>
+
+<ol start="1">
+  <li>En el Admin VTEX, ve a <strong>Promociones &gt; Campañas de WhatsApp &gt; Vista general</strong>, o ingresa <strong>Vista general de Campañas de WhatsApp</strong> en la barra de búsqueda de la parte superior de la página.</li>
+  <li>Haz clic en <code>Configurar cuenta</code>.</li>
+  <li>Selecciona <strong>Sí, quiero un número gratuito</strong> y haz clic en <code>Siguiente</code>.</li>
+  <li>Copia el número de teléfono proporcionado y haz clic en <code>Conectar</code> para vincular este número a tu cuenta de Meta for business.</li>
+  <li>Haz clic en <code>Continuar como usuario</code>.</li>
+  <li>Haz clic en <code>Comenzar</code>.</li>
+  <li>Confirma que la información de <strong>Porfolio empresarial, Nombre de la empresa</strong>, <strong>Sitio web</strong> o <strong>Perfil comercial de la empresa</strong> y <strong>País</strong> son correctos.</li>
+  <li>Haz clic en <code>Continuar</code>.</li>
+</ol>
+
+<p>Crear una cuenta de WhatsApp Business:</p>
+
+<ol start="9">
+  <li>Selecciona <strong>Crear una cuenta de WhatsApp Business</strong> y <strong>Crear un nuevo perfil de empresa</strong>.</li>
+  <li>Haz clic en <code>Continuar</code>.</li>
+  <li>Rellena los campos que se indican a continuación:
+    <ul>
+      <li><strong>Nombre de la cuenta de WhatsApp Business (interno)</strong>, ejemplo: Nombre de la tienda VTEX.</li>
+      <li><strong>Nombre para mostrar (visible para los clientes)</strong>, ejemplo: nombre de la tienda.</li>
+      <li><strong>Categoría</strong>.</li>
+      <li>Haz clic en <code>Continuar</code>.</li>
+    </ul>
+  </li>
+  <li>Pega el número de teléfono que has copiado en la etapa anterior y selecciona la opción <strong>SMS</strong>. Haz clic en <code>Continuar</code>.</li>
+</ol>
+
+<div class="alert alert-warning">
+  El número generado puede ser estadounidense, pero si tu página de Meta está verificada, tus clientes verán el nombre de tu empresa. Si no está verificada, recomendamos seguir el <a href="https://www.facebook.com/business/help/2058515294227817?id=180505742745347">proceso de verificación con Meta</a>.
+</div>
+
+<ol start="13">
+  <li>Copia el código de verificación que se muestra en el Admin VTEX.</li>
+  <li>Pega el código de verificación en el campo de la ventana emergente de Meta y haz clic en <code>Continuar</code>.</li>
+  <li>Haz clic en <code>Continuar</code>.</li>
+  <li>Haz clic en <code>Finalizar</code>.</li>
+  <li>Elige un logotipo de 400x400 px para tu nuevo número de WhatsApp. No es necesario que la imagen esté en alta resolución.</li>
+</ol>
+
+<p>Aceptar los términos y condiciones:</p>
+
+<ol start="18">
+  <li>Revisa los Términos y condiciones.</li>
+  <li>Haz clic en <code>Acepto</code>.</li>
+  <li>Haz clic en <code>Finalizar</code>.</li>
+</ol>
+
+<div class="alert alert-warning">
+Una vez que se ha activado una campaña de recuperación de checkout abandonado pueden transcurrir hasta 48 horas para que comiencen a mostrarse las métricas de análisis.
+</div>
+
+<div class = "alert alert-info">
+Aprende más sobre <a href="https://help.vtex.com/es/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">Gestión y detalles de WhatsApp AI Campaigns</a>.
+</div>
+
diff --git a/docs/tutorials/es/redirect-from-other-addresses.md b/docs/tutorials/es/redirect-from-other-addresses.md
new file mode 100644
index 000000000..78eb61fcf
--- /dev/null
+++ b/docs/tutorials/es/redirect-from-other-addresses.md
@@ -0,0 +1,81 @@
+---
+title: 'Redirección de otras direcciones'
+id: 3Xi2AeLUx2QpJQu8DTX8KQ
+status: PUBLISHED
+createdAt: 2022-09-19T21:21:24.455Z
+updatedAt: 2024-01-23T18:16:55.386Z
+publishedAt: 2024-01-23T18:16:55.386Z
+firstPublishedAt: 2022-09-19T21:40:22.913Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: redireccion-de-otras-direcciones
+locale: es
+legacySlug: 
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+Una tienda online debe tener una única dirección principal, que [apuntará a los servidores de VTEX](https://help.vtex.com/es/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ) antes del lanzamiento oficial de la tienda. Consulta [Configuración del dominio de tu tienda](https://help.vtex.com/es/tutorial/configurar-dominio-de-la-tienda--tutorials_2450) para conocer las reglas que debe cumplir la dirección y obtener instrucciones sobre cómo registrarla.
+
+Para posibilitar el acceso a la tienda desde otras direcciones y versiones sin subdominio, es necesario configurar la redirección de estas direcciones a la dirección principal de la tienda registrada en **Configuración de la cuenta > Cuenta > Tiendas** en el Admin VTEX. Observa los ejemplos a continuación:
+
+| Dirección | Tipo |
+|---|---|
+| `www.mitienda.com` | Dominio principal |
+| `www.direccionantigua.com` | Redirección |
+| `mitienda.com` | Redirección |
+
+## Configurar redirecciones
+
+Existen diversas formas de configurar las redirecciones, y una de las más conocidas es mediante el uso de <code>[htaccess](https://developer.mozilla.org/en-US/docs/Learn/Server-side/Apache_Configuration_htaccess)</code> en el servidor. Además, puedes utilizar una redirección DNS, proporcionada por varios servicios, incluidos proveedores de dominios como [domain.com](https://www.domain.com/).
+
+Consulta a continuación instrucciones para configurar redirecciones a la dirección principal de tu tienda utilizando esta sencilla herramienta: [Redirect Center](http://redirect.center/).
+
+<div class="alert alert-warning">
+  <p><a href="http://redirect.center/">Redirect Center</a> no es un servicio de VTEX y no funciona con HTTPS. Existen otros servicios similares, y VTEX no recomienda ninguno en particular. VTEX no se hace responsable de los problemas causados por servicios externos de redirección.</p>
+</div>
+
+### Redirección de direcciones sin subdominio (como www)
+
+Para acceder a tu tienda desde una dirección sin subdominios, como `www`, necesitas crear una redirección a la dirección principal de tu tienda. Por ejemplo, para poder acceder a `http://www.misitioweb.com` desde la dirección sin subdominio `http://misitioweb.com`, debes crear una redirección en tu proveedor de DNS siguiendo las instrucciones que se indican a continuación:
+
+1. Crea un registro de tipo A para la raíz del dominio, generalmente representada por `. `, `@` o simplemente por `misitioweb.com`, apuntando a `54.84.55.102` (IP de [Redirect Center](http://redirect.center/)).
+
+   |   |   |   |
+   |---|---|---|
+   | Host Record: <dejar-vacío\> | Type: A | To: 54.84.55.102 |
+
+2. Crea un registro de tipo CNAME de `redirect` (o `redirect.misitioweb.com`), apuntando a `www.misitioweb.com.redirect.center.com`.
+
+  |   |   |   |
+  |---|---|---|
+  | Host Record: redirect | Type: CNAME | To: www.misitioweb.com.redirect.center.com |
+
+Consulta más información sobre escenarios como este en [Mejores prácticas para acceder a la tienda sin www](https://help.vtex.com/es/tutorial/mejores-practicas-para-acceder-a-tienda-sin-www--tutorials_4278).
+
+Dependiendo del proveedor de DNS, la propagación de la redirección puede tardar unos minutos en completarse.
+
+### Redirección de una dirección a otra
+
+Para redirigir de una dirección a otra que no comparta la misma raíz del dominio, crea una entrada CNAME en la dirección antigua (origen del acceso), siguiendo el patrón `{nuevaDireccion}.opts-uri.redirect.center.com`.
+
+Por ejemplo, para redireccionar de `www.dominioantiguo.com` a `www.nuevodominio.com`:
+
+* Crea una entrada `www` en el dominio `dominioantiguo.com` con el CNAME `www.nuevodominio.com.opts-uri.redirect.center.com`.
+
+Para redireccionar de `tienda.unadireccion.com` a `www.site.com`:
+
+* Crea una entrada de `tienda` en el dominio `unadireccion.com` con el CNAME `www.site.com.opts-uri.redirect.center.com`.
+
+### Redirección de acceso con HTTPS
+
+VTEX redirige automáticamente las direcciones `http://` a `https://`. Aun así, puede ser necesario redirigir una dirección `https://` (como una versión de la dirección sin subdominio o con otro dominio) a una dirección con `https://`.
+
+Cuando se accede a una página con HTTPS, es necesario que el servidor asociado a esa dirección tenga instalado un certificado SSL. La ausencia de este certificado hace que el navegador interprete la conexión como no segura, lo que provoca el bloqueo de la solicitud. Esto impide el acceso a la página deseada y, en consecuencia, imposibilita la redirección a otra dirección.
+
+En [Redirect Center](http://redirect.center/) no es posible instalar un certificado SSL para cada dominio al que apuntas. Por lo tanto, no redirige los accesos provenientes de HTTPS.
+
+Para superar esta limitación ten en cuenta los siguientes puntos:
+
+1. En el caso de que el dominio de origen no cuente con un subdominio, como `site.com`, dirígelo hacia un servidor gestionado directamente por la tienda, ya sea un servidor físico o virtual administrado por el propio usuario o empresa. Este servidor debe tener un **certificado SSL instalado para el dominio de origen**, lo que permite el acceso seguro a través de HTTPS. Consulta [Certificado de seguridad (SSL)](https://help.vtex.com/es/tutorial/certificado-de-seguridad-ssl--tutorials_1308) para más información.
+2. Define una **regla de redirección**. Si desas utilizar un servidor de gestión propia para redirigir el acceso con HTTPS, debes definir una regla de redirección en el servidor, que puede variar en función del tipo de servidor utilizado (Apache, ASP, nginx). Por lo tanto, para configurar esta regla, debes saber qué tipo de servidor se está utilizando y aplicar la configuración correspondiente.
diff --git a/docs/tutorials/es/redirects.md b/docs/tutorials/es/redirects.md
new file mode 100644
index 000000000..eb6245f27
--- /dev/null
+++ b/docs/tutorials/es/redirects.md
@@ -0,0 +1,42 @@
+---
+title: 'Redireccionamientos'
+id: 3okF84cImJwKzcc8hxmZ2r
+status: PUBLISHED
+createdAt: 2024-06-27T17:04:44.975Z
+updatedAt: 2024-06-27T17:05:31.676Z
+publishedAt: 2024-06-27T17:05:31.676Z
+firstPublishedAt: 2024-06-27T17:05:31.676Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: redireccionamientos
+locale: es
+legacySlug: redireccionamientos
+subcategory: 1wvyJwJhKgewxGeAGCVmM6
+---
+
+La funcionalidad de **Redireccionamientos** direcciona al cliente a cualquier otra página, ya sea interna o externa a la tienda. Los redireccionamientos se hacen en el área de búsqueda de tu storefront, utilizando términos o filtros que el cliente haya seleccionado. De este modo, una de las ventajas de los redireccionamientos es contemplar escenarios de comunicación que la búsqueda en el catálogo de la tienda no cubre, como por ejemplo redirigir la búsqueda de una marca a su página promocional.
+
+<div class="alert alert-warning">
+<p>Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lee nuestro artículo VTEX Intelligent Search: configuración Multidioma (Beta) para obtener más información.</p>
+</div>
+
+## Cómo funciona un redireccionamiento
+
+Al crear un redireccionamiento, también es necesario crear condiciones - llamadas reglas. Estas deben contener un conjunto tanto de términos como de filtros registrados. La cantidad de reglas es ilimitada por redireccionamiento.
+
+Mediante la funcionalidad de Redireccionamientos se pueden crear reglas que contemplen los intereses del gestor y del cliente final simultáneamente. Otros beneficios son:
+
+- Aumentar las posibilidades de búsqueda del sitio. Las búsquedas sin resultados generan estadísticamente Tasa de Rechazo (Bounce Rate) - el porcentaje de visitantes que entran en el sitio y salen sin ver otras páginas - para el comercio electrónico.
+- Facilitar la usabilidad del cliente final, como en situaciones de poscompra o en acciones promocionales.
+
+Después de que el cliente haya realizado una búsqueda, VTEX Intelligent Search captura el término de búsqueda y comprueba si hay alguna regla de redireccionamiento registrada relacionada con esta búsqueda.
+
+El término de búsqueda es elegible cuando ya existe, por lo menos, una regla relacionada con este. Así, el cliente es redireccionado a la URL registrada.
+
+Puedes crear un redireccionamiento que, si el cliente busca “Mis pedidos” o “Pedidos”, lo dirija a los pedidos de la cuenta en lugar de ver una página de búsqueda vacía.
+
+Además, también puedes configurar la funcionalidad para dirigir al cliente a una landing page de promociones específicas. En este caso, el cliente que busque "Black Friday" será dirigido a esta promoción.
+
+En otro escenario, si el cliente busca "Zapatilla de correr" y filtra la marca Nike, será llevado a una página específica de la marca.
+
diff --git a/docs/tutorials/es/registering-a-category.md b/docs/tutorials/es/registering-a-category.md
index 31cdc354b..ebedc81fc 100644
--- a/docs/tutorials/es/registering-a-category.md
+++ b/docs/tutorials/es/registering-a-category.md
@@ -3,8 +3,8 @@ title: 'Registrar categoría'
 id: tutorials_206
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:39.383Z
-updatedAt: 2023-03-29T17:45:06.786Z
-publishedAt: 2023-03-29T17:45:06.786Z
+updatedAt: 2023-11-29T19:10:35.853Z
+publishedAt: 2023-11-29T19:10:35.853Z
 firstPublishedAt: 2017-04-27T23:00:46.516Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -38,4 +38,4 @@ Siga el paso a paso abajo para configurar una categoría:
 - [Llenar campos de registro de categoría](/es/tutorial/campos-de-registro-de-categoria)
 - [Limpiar base de datos de la tienda](/es/tutorial/limpiar-base-de-datos-de-la-tienda)
 - [Registrar un producto](https://help.vtex.com/es/tutorial/cadastrando-produtos--tutorials_2567)
-- [Registrar un SKU](/es/tutorial/registrar-un-sku)
+- [Registrar un SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ)
diff --git a/docs/tutorials/es/registering-brands.md b/docs/tutorials/es/registering-brands.md
index 6fbce62c1..a43c4563e 100644
--- a/docs/tutorials/es/registering-brands.md
+++ b/docs/tutorials/es/registering-brands.md
@@ -23,4 +23,4 @@ Para registrar una marca, siga los pasos abajo:
 4. Llene los [Campos de registro de marca](https://help.vtex.com/es/tutorial/campos-de-registro-de-marca--37Ky7lTbEkiWIAYA80EMyI).
 5. Haga clic en el botón `Guardar`.
 
-![ENcadastrarmarcas3.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
+![ENcadastrarmarcas3.PNG?h=250](//images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
diff --git a/docs/tutorials/es/registering-gateway-affiliations.md b/docs/tutorials/es/registering-gateway-affiliations.md
index df2a93eff..ed3b62b7e 100644
--- a/docs/tutorials/es/registering-gateway-affiliations.md
+++ b/docs/tutorials/es/registering-gateway-affiliations.md
@@ -1,10 +1,10 @@
 ---
-title: 'Registrar afiliaciones de gateway'
+title: 'Registrar proveedores de pagos y antifraude'
 id: tutorials_444
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:18.209Z
-updatedAt: 2023-03-21T20:55:24.198Z
-publishedAt: 2023-03-21T20:55:24.198Z
+updatedAt: 2024-01-22T20:37:11.273Z
+publishedAt: 2024-01-22T20:37:11.273Z
 firstPublishedAt: 2017-04-27T23:03:24.823Z
 contentType: tutorial
 productTeam: Financial
@@ -15,27 +15,79 @@ legacySlug: afiliaciones-de-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Una afiliación de gateway es un conjunto de configuraciones que representa su contrato con un proveedor de pago (gateway, adquirente o subadquirente).
+En VTEX puedes configurar diversos proveedores como gateways, adquirentes, subadquirentes, [orquestadores](https://www.y.uno/en) o [PSP](https://en.wikipedia.org/wiki/Payment_service_provider) que te permiten ofrecer diferentes medios y condiciones de pago a tus clientes, así como servicios de protección antifraude. Antes, estas configuraciones eran conocidas como "afiliaciones de gateway" en nuestro sistema.
 
-En VTEX, puede configurar varios proveedores de pago y ofrecer diferentes métodos y condiciones de pago a sus clientes.
+En la página de gestión de proveedores puedes:
 
-Para configurar una afiliación de gateway, siga los pasos a continuación:
+- [Registrar un nuevo proveedor](#registrar-proveedor)
+- [Ver los provedores registrados](#ver-proveedores-registrados)
+- [Editar la configuración de proveedores](#editar-configuracion-de-un-proveedor)  
+![interface_provedor_ES_1](//images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/776404f95b88a2baef59270471016a6d/interface_provedor_ES_1.JPG)
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en su proveedor de pago preferido.
-4. Rellene los campos de registro __Application Key__ y __Application Token__ con la información proporcionada por el proveedor de pago.
-5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón __Instalar aplicación__ y siga las instrucciones de instalación. Este mensaje solo se muestra para algunos tipos de afiliaciones de pgateway. 
-6. Haga clic en el botón **Guardar**.
+## Registrar proveedor
+
+Para agregar un nuevo proveedor de pago o antifraude a tu tienda, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pagos > Proveedores__ o ingresa __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en `Nuevo proveedor`.
+3. Haz clic en el proveedor de pago de tu preferencia.
+4. Rellena los campos __Clave de aplicación__ y __Token de aplicación__ con la información indicada por el proveedor de pagos.
+5. Si aparece un mensaje de alerta que diga que se debe instalar la aplicación, haz clic en el botón __Instalar aplicación__ y sigue las instrucciones de instalación. El mensaje solo se muestra en algunos tipos de proveedores de gateway.
+6. Haz clic en `Guardar`.
 
 <div class = "alert alert-info">
-  <p>Si hay otros campos para completar además de la <b>Application Key</b> y <b>Application Token</b> (Paso 6), la afiliación de gateway debe configurarse de acuerdo con el tutorial específico. Para más información, consulte la subsección <a href="https://help.vtex.com/es/subcategory/configuracoes-de-pagamentos--3tDGibM2tqMyqIyukqmmMw">Configuración de Pagos</a>.</p>
+  <p>Si hay otros campos que rellenar además de Clave de aplicación y Token de aplicación (paso 6), la configuración del proveedor de gateway se debe llevar a cabo siguiendo el tutorial correspondiente. Para más información, consulta la subsección <a href="https://help.vtex.com/es/subcategory/configuracion-de-pagos--3tDGibM2tqMyqIyukqmmMw">Configuración de Pagos</a>.</p>
 </div>
 
 <div class = "alert alert-danger">
-Las credenciales utilizadas para rellenar los campos <strong>Clave de aplicación</strong> y <strong>Token de aplicación</strong> deben ser proporcionadas por el proveedor de pagos para identificar la tienda. No se deben utilizar las credenciales <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet">generadas en el Admin</a>, que empiezan por <code>vtexappkey-</code>.
+Las credenciales utilizadas para rellenar los campos Clave de aplicación y Token de aplicación las debe informar el proveedor de pago para identificar la tienda. No se deben utilizar las credenciales <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet">generadas en el Admin</a>, que empiezan por <code>vtexappkey-</code>.
 </div>
 
-Para configurar los métodos de pago que procesará su proveedor de pago elegido, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento). 
+Para configurar los medios de pago que el proveedor escogido procesará, accede a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455). 
+
+Para definir condiciones especiales para los medios de pago, accede a [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+
+![interface_provedor_ES_2](//images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/eb61a668aee146f72207b08ff3f93b3a/artigo_interface_provedor_ES_2.JPG)
+
+## Ver proveedores registrados
+
+La pantalla principal de gestión de proveedores, disponible en __Configuración de la tienda > Pagos > Proveedores__ en el Admin VTEX, muestra todos los proveedores de pago o antifraude registrados en la tienda. Para acceder rápidamente a la información de proveedores específicos, puedes realizar una búsqueda o utilizar un filtro.
+
+### Buscar proveedores
+
+Para buscar proveedores por nombre, accede a la página de gestión de proveedores e ingresa el nombre del proveedor deseado.
+
+![interface_provedor_ES_3](//images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/f8ab3035ab037e74c6b08e5f4054f686/interface_provedor_ES_3.JPG)
+
+### Filtrar proveedores
+
+Para cambiar la lista de proveedores usando filtros, accede a la página de gestión de proveedores y aplica uno o más de los filtros indicados a continuación, según el resultado deseado.
+
+- __Nombre__: filtra la lista de proveedores de pago por el nombre al marcar la casilla o ingresándolo en la barra de búsqueda del menú.
 
-Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete).
+![interface_provedor_ES_4](//images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/966cf9c4d726bb4e3fe3f140b4205472/interface_provedor_ES_4.JPG)
+
+- __Tipo__: filtra la lista de proveedores por tipo, ya sea antifraude o de pago, o ambos.
+
+![interface_provedor_ES_5](//images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/76411e11c78028aac232b9b8d8a79534/interface_provedor_ES_5.JPG)
+
+- __Entorno__: filtra la lista de proveedores por tipo de entorno de operación registrado (producción o prueba).
+
+![interface_provedor_ES_6](//images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/5aae0659cf9128a58fe3ce02d03a6023/interface_provedor_ES_6.JPG)
+
+<div class = "alert alert-danger">
+Para remover los filtros aplicados y ver todos los proveedores registrados en la tienda, haz clic en el botón <code>Limpiar todo</code>.</div>
+
+## Editar configuración de un proveedor
+
+Para editar la configuración de un proveedor de pago o antifraude registrado en la tienda, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pagos > Proveedores__ o ingresa __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en el proveedor de pago o antifraude deseado.
+3. En la pantalla de configuración del proveedor, haz clic en `Editar`.
+4. Realiza los cambios necesarios y haz clic en `Guardar`.
+
+![interface_provedor_ES_7](//images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/4931462bfe35657876f4a5e6c63d5386/artigo_interface_provedor_ES_7.JPG)
+
+<div class = "alert alert-danger">
+Antes de editar la configuración de un proveedor, como datos de autorización, modo de procesamiento o tipo de reembolso, asegúrate de verificar que la nueva información no afecte el rendimiento operativo de la tienda.</div>
diff --git a/docs/tutorials/es/registering-geolocation.md b/docs/tutorials/es/registering-geolocation.md
index 21a051c7f..270d2d4db 100644
--- a/docs/tutorials/es/registering-geolocation.md
+++ b/docs/tutorials/es/registering-geolocation.md
@@ -3,8 +3,8 @@ title: 'Gestionar Geolocalización'
 id: tutorials_138
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:36.462Z
-updatedAt: 2023-03-29T13:25:16.724Z
-publishedAt: 2023-03-29T13:25:16.724Z
+updatedAt: 2023-08-25T14:52:20.340Z
+publishedAt: 2023-08-25T14:52:20.340Z
 firstPublishedAt: 2017-04-27T23:00:44.871Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -32,6 +32,10 @@ Accediendo a través del enlace [Genere sus polígonos con geojson.io](http://ge
 
 Usted usará ese JSon para añadir el polígono en la plataforma, que comprenderá a partir de ese lenguaje cuáles códigos postales están incluidos en esa área.
 
+<div class="alert alert-danger">
+En la configuración de un polígono, no es posible delimitar áreas superpuestas, o sea, no es posible superponer coordenadas geográficas.
+</div>
+
 ## Cómo añadir un Polígono
 
 Cuando se añade un polígono, usted lo nombra para que se pueda identificarlo en la plantilla de flete para su consulta a través del código postal. Para añadir el polígono, siga los pasos abajo:
diff --git a/docs/tutorials/es/registering-the-skus-barcode-for-vtex-sales-app.md b/docs/tutorials/es/registering-the-skus-barcode-for-vtex-sales-app.md
index 91a74329b..b8730baaf 100644
--- a/docs/tutorials/es/registering-the-skus-barcode-for-vtex-sales-app.md
+++ b/docs/tutorials/es/registering-the-skus-barcode-for-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Registrar los códigos de barras de los SKUs para el VTEX Sales App'
 id: 2jkOdRB4XSMG2ke0uUQIKS
 status: PUBLISHED
 createdAt: 2018-03-12T17:23:32.837Z
-updatedAt: 2023-05-31T16:11:54.350Z
-publishedAt: 2023-05-31T16:11:54.350Z
+updatedAt: 2023-07-26T19:04:52.107Z
+publishedAt: 2023-07-26T19:04:52.107Z
 firstPublishedAt: 2018-03-12T17:27:18.421Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
index 3a6f455ae..a485f382d 100644
--- a/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -19,7 +19,7 @@ Al crear una [promoción regular](https://help.vtex.com/es/tutorial/registro-pro
 
 Al seleccionar este tipo de descuento, deberás crear una fórmula para definir cuál será el cálculo del descuento que se aplicará. En este artículo, explicaremos cómo crear una fórmula que cumpla con los objetivos de tu promoción.
 
-![tipo-descuento-formula](https://images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/cb74d4e22b46f159aee6f51a09fe4646/desc-es.PNG)
+![tipo-descuento-formula](//images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/cb74d4e22b46f159aee6f51a09fe4646/desc-es.PNG)
 
 En general, la fórmula para calcular el descuento nominal de la promoción sigue la misma lógica que las [fórmulas de Microsoft Excel](https://support.microsoft.com/pt-br/office/f%C3%B3rmulas-e-fun%C3%A7%C3%B5es-294d9486-b332-48ed-b489-abe7d0f9eda9), es decir que puedes usar [variables](#variables) (`total`, ` freight` y `quantity`), hacer [operaciones](#operaciones) (suma, resta, multiplicación y división) y aplicar [funciones](#funciones) (`min` y `max`).
 
@@ -78,19 +78,19 @@ De esta manera, la promoción aplicará el valor de descuento más bajo en cada
 
 Un cliente agregó al carrito un ítem cuyo precio es $ 45. Al calcular el 20% del total del precio, el resultado es 9, ya que `total * 0.2 = 9.` Como 9 está por debajo del valor límite de descuento, el descuento que se aplicará será de $ 9.
 
-![scenario1-es](https://images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/d85aee72b0ba9e25aa9174d1adfa8bd6/scenario1-es.png)
+![scenario1-es](//images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/d85aee72b0ba9e25aa9174d1adfa8bd6/scenario1-es.png)
 
 #### Escenario 2
 
 Otro cliente agregó al carrito un ítem cuyo precio es de $ 2600. Al calcular el 20% de ese valor, el resultado es 520, ya que `total * 0.2 = 520.` Como este valor está por encima del límite ($ 10), el descuento aplicado será de $ 10.
 
-![scenario2-es](https://images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/281dfb618c4116d64023a38182f775ae/scenario2-es.png)
+![scenario2-es](//images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/281dfb618c4116d64023a38182f775ae/scenario2-es.png)
 
 #### Escenario 3
 
 Un tercer cliente agregó dos ítems al carrito: un ítem tiene un precio de $ 100, y el otro, $ 2600. La suma de estos valores da como resultado $ 2700, por lo tanto, `total = 2700`. Al calcular el 20% del valor total, obtenemos un resultado de 540, ya que `total * 0.2 =  540`. Como este valor está por encima del límite ($ 10), el descuento total aplicado será de $ 10.
 
-![scenario3-es](https://images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/bc0bd5ef72252b31779b9b6df92fbdf4/scenario3-es.png)
+![scenario3-es](//images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/bc0bd5ef72252b31779b9b6df92fbdf4/scenario3-es.png)
 
 El descuento total de $ 10 se distribuye proporcionalmente entre los ítems, teniendo en cuenta el precio y la cantidad de cada uno. Esta distribución la realiza la plataforma de manera automática, siguiendo la lógica que se explica a continuación:
 
diff --git a/docs/tutorials/es/regular-promotion-with-reward-value.md b/docs/tutorials/es/regular-promotion-with-reward-value.md
index 5a5e44372..5a2eddb71 100644
--- a/docs/tutorials/es/regular-promotion-with-reward-value.md
+++ b/docs/tutorials/es/regular-promotion-with-reward-value.md
@@ -38,7 +38,7 @@ El **valor de fidelidad nominal** agrega un valor fijo como crédito a la cuenta
 
 En el ejemplo que se muestra a continuación, los clientes obtendrán un crédito de USD 10 en la tienda cuando el status del pedido cambie a **Facturado**.
 
-![vf-nominal-es](https://images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/e281a28760551bfc2a2b2b270f61de9e/vf-nominal-es.png)
+![vf-nominal-es](//images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/e281a28760551bfc2a2b2b270f61de9e/vf-nominal-es.png)
 
 ### Valor de fidelidad porcentual
 
@@ -49,7 +49,7 @@ El **valor de fidelidad porcentual** agrega un valor porcentual como crédito de
 
 En el ejemplo a continuación, los clientes obtendrán un crédito del 20 % del valor de la compra cuando el status del pedido cambie a **Pago aprobado**.
 
-![vf-percentual-es](https://images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/68508961c6c3efc9495e79062c73a343/vf-percentual-es.png)
+![vf-percentual-es](//images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/68508961c6c3efc9495e79062c73a343/vf-percentual-es.png)
 
 ## Configuración de las restricciones
 
@@ -85,17 +85,17 @@ Cuando un cliente realiza un pedido apto para obtener crédito por fidelidad, pu
 
 En la sección **Ventas y marketing**, aparece el nombre de la promoción que se aplicó al pedido:
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/3a84036866c5ed37f964e79a36f8bcd4/detalhes-oms-es.png" alt="detalles-del-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/3a84036866c5ed37f964e79a36f8bcd4/detalhes-oms-es.png" alt="detalles-del-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/35b752b315cc8578199647fe535677fa/detalhes-neworders-en__1_.png" alt="detalles-del-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido (Beta)</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/35b752b315cc8578199647fe535677fa/detalhes-neworders-en__1_.png" alt="detalles-del-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalles del pedido (Beta)</em></figcaption></figure>
 
 En la sección **Flujo del pedido**, puedes verificar el valor de fidelidad otorgado:
 
-![fluxo-oms-es](https://images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/b9c7949cb68192d24c61ff0b855c751e/fluxo-oms-es.png)
+![fluxo-oms-es](//images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/b9c7949cb68192d24c61ff0b855c751e/fluxo-oms-es.png)
 
 Si utilizas la nueva interfaz de [Detalles del pedido (Beta)](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido-beta--2Y75n54Cc9VizrlG1N6ZNl), accede a `Ver interacciones` para verificar el valor otorgado:
 
-![interacoes-neworders-es](https://images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/c99a1b288b2d25931d695c19865731dd/interacoes-neworders-es.png)
+![interacoes-neworders-es](//images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/c99a1b288b2d25931d695c19865731dd/interacoes-neworders-es.png)
 
 Ten en cuenta que la promoción aplicada en el pedido del ejemplo brinda un **valor de fidelidad porcentual** del **50 %**. Gracias a esto, el cliente obtuvo un crédito de `R$ 54,28` para las próximas compras en la tienda, lo cual equivale al **50 %** de `R$ 108,55`, que es el valor total del pedido.
 
@@ -103,13 +103,13 @@ Ten en cuenta que la promoción aplicada en el pedido del ejemplo brinda un **va
 
 Los clientes de tu tienda ven el valor de fidelidad disponible para usar en la etapa de **Pago** durante el _checkout_, tal como se muestra a continuación.
 
-![checkout-pt (1)](https://images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
+![checkout-pt (1)](//images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
 
 El valor otorgado se puede usar como parte de pago. Para hacerlo, el cliente debe hacer clic en `Utilizar crédito` e ingresar el valor que desea usar.
 
 El valor se descontará de la otra forma de pago seleccionada. En el ejemplo a continuación, la factura pasó a tener un valor de `R$ 113,50`, que corresponde a `R$ 167,80` menos el valor de fidelidad utilizado (`R$ 54,30`).
 
-![checkout-2-pt (1)](https://images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
+![checkout-2-pt (1)](//images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
 
 ## Más información
 
diff --git a/docs/tutorials/es/regular-promotion.md b/docs/tutorials/es/regular-promotion.md
index e79f40797..34a4d90b5 100644
--- a/docs/tutorials/es/regular-promotion.md
+++ b/docs/tutorials/es/regular-promotion.md
@@ -1,10 +1,10 @@
 ---
 title: 'Promoción Regular'
 id: tutorials_327
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-04-27T22:07:59.690Z
-updatedAt: 2022-12-08T19:33:36.098Z
-publishedAt: 2022-08-23T19:50:18.784Z
+updatedAt: 2024-05-15T16:38:18.730Z
+publishedAt: 2024-05-15T16:38:18.730Z
 firstPublishedAt: 2017-04-27T23:03:15.647Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -89,7 +89,7 @@ Para que la promoción sea válida para todas las políticas comerciales, deje l
 
 En esta sección, debe elegir si la promoción se aplicará a todos los productos registrados en su tienda o solo a productos específicos, como se ilustra a continuación.
 
-![promocoes-restricao-es](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/83e378ce4788febd839ee10395e02f9f/image.png)
+![promocoes-restricao-es](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/83e378ce4788febd839ee10395e02f9f/image.png)
 
 Si desea aplicar la promoción a todo su catálogo, seleccione la opción **Aplicar a todos los productos.**
 
@@ -99,7 +99,7 @@ Puede incluir o excluir **categorías, marcas, colecciones**, **productos** y **
 
 Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en la promoción todos los productos de la categoría **Vestido **cuya marca es **Farm**, con la excepción del producto **Vestido Rosas**.
 
-![exemplo-es](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/89c3e52e137f7856cb49628954217ff9/image.png)
+![exemplo-es](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/89c3e52e137f7856cb49628954217ff9/image.png)
 
 En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
 
@@ -113,12 +113,12 @@ Para ser válidos en la promoción, los productos deben cumplir todas las condic
 
 El pedido del cliente debe cumplir las condiciones registradas en esta sección para ser válido en la promoción.
 
-- **Valor mínimo y máximo del pedido:** la promoción se aplicará teniendo en cuenta el valor "bruto" del carrito, sin considerar otras promociones o el flete.
+- **Valor mínimo y máximo del pedido:** para las promociones de precio que ajustan directamente el valor de los ítems en el carrito, la activación de la promoción se basa en el precio original de los ítems. Y para las promociones que ofrecen otros beneficios, como envío gratuito o regalos, el precio considerado para activar la promoción es el precio ya descontado.
 - **Valor acumulado de las compras:** se concederá el descuento si el total de todas las compras ya realizadas por el cliente alcanza el valor ingresado.
 - **Valor del ítem entre:** se concederá el descuento si el valor del ítem cumple el intervalo de valores ingresados.
 - **Precio "de" y "a" son iguales** o **Precio "de" y "a" son diferentes:** se refiere al precio del producto. Solo se puede seleccionar una opción.
 - **Restricción de promoción por BIN:** se concederá el descuento si el BIN de la tarjeta está entre los ingresados.
-- **Marketing Tags:** campo utilizado para restringir la activación de la promoción si la compra es realizada por el [módulo de Suscripciones de VTEX](https://help.vtex.com/es/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#)
+- **Marketing Tags:** campo utilizado para restringir la activación de la promoción. 
 - **Afiliados:** identificador de pedidos del Marketplace. Se aplicará el descuento a los afiliados seleccionados. Vea el artículo [Qué es afiliado](https://help.vtex.com/es/tutorial/que-es-afiliado--4bN3e1YarSEammk2yOeMc0?locale=es) para más información.
 - **Clúster de clientes:** se concederá el descuento si el cliente está registrado en el clúster seleccionado. Es importante destacar que el nombre del clúster debe ser exactamente como se ha registrado, cualquier error ortográfico impedirá el correcto funcionamiento de la configuración.
 - **Países de entrega:** se concederá el descuento a los países seleccionados en este campo. 
diff --git a/docs/tutorials/es/releases-module-beta.md b/docs/tutorials/es/releases-module-beta.md
index 4e81def91..8959239ff 100644
--- a/docs/tutorials/es/releases-module-beta.md
+++ b/docs/tutorials/es/releases-module-beta.md
@@ -72,7 +72,7 @@ En esta etapa, no es obligatorio rellenar los campos <b>Día de publicación</b>
 
 8. Haz clic en `Crear`.
 
-![print_cms_beta_es](https://images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/ed3b5cf5eb3020123112b9d7aee2d34a/print_cms_beta_es.png)
+![print_cms_beta_es](//images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/ed3b5cf5eb3020123112b9d7aee2d34a/print_cms_beta_es.png)
 
 ### Crear lanzamiento a través del módulo Lanzamientos
 
@@ -92,7 +92,7 @@ En esta etapa, no es obligatorio rellenar los campos Día de publicación y Hora
 
 Todos los lanzamientos creados aparecen en una lista en el Admin VTEX en **Configuración de la tienda > Lanzamientos**. La página muestra dos pestañas, `PROGRAMADOS` y `NO PROGRAMADOS`, dependiendo de si el lanzamiento se creó con una fecha de publicación o no. 
 
-![print_releases_es](https://images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/687594e054953398b1e1973375e00709/print_releases_es.png)
+![print_releases_es](//images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/687594e054953398b1e1973375e00709/print_releases_es.png)
 
 En la pestaña `PROGRAMADOS`, la descripción de cada columna es la siguiente:
 
diff --git a/docs/tutorials/es/releasing-the-store-for-production.md b/docs/tutorials/es/releasing-the-store-for-production.md
index c71fe1826..924579b11 100644
--- a/docs/tutorials/es/releasing-the-store-for-production.md
+++ b/docs/tutorials/es/releasing-the-store-for-production.md
@@ -30,7 +30,7 @@ Luego, será necesario poner la tienda con un estado de producción en el Licens
 4. En la opción **Está en producción**, clic en el botón **No**, y quedará como **Si**;
 5. Clic en el botón **Guardar**.
 
-![cuentas.es](https://images.ctfassets.net/alneenqid6w5/4UvPtCEjci7qcSWAnq9Zb2/28637e20f24ddaa9c34c717fc5fbecbe/cuentas.es.png)
+![cuentas.es](//images.ctfassets.net/alneenqid6w5/4UvPtCEjci7qcSWAnq9Zb2/28637e20f24ddaa9c34c717fc5fbecbe/cuentas.es.png)
 
 Después de esa configuración, al acceder la UL final de la tienda, la misma ya va a ser direccionada para su e-commerce!
 
diff --git a/docs/tutorials/es/relevance-rules.md b/docs/tutorials/es/relevance-rules.md
new file mode 100644
index 000000000..8b550355c
--- /dev/null
+++ b/docs/tutorials/es/relevance-rules.md
@@ -0,0 +1,114 @@
+---
+title: 'Reglas de relevancia'
+id: 1o9jtVGjSIiptbqdNXIlNK
+status: PUBLISHED
+createdAt: 2024-06-27T17:12:27.900Z
+updatedAt: 2024-06-27T17:13:52.839Z
+publishedAt: 2024-06-27T17:13:52.839Z
+firstPublishedAt: 2024-06-27T17:13:52.839Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: reglas-de-relevancia
+locale: es
+legacySlug: reglas-de-relevancia
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Las **Reglas de relevancia** definen el orden de los productos en los resultados de la búsqueda en las páginas de listado de productos (PLP). La disposición de los productos es alterada por la configuración de criterios y prioridades con datos predeterminados utilizados por el Motor de Búsqueda.
+
+Las Reglas de relevancia solo se aplican en los resultados de búsqueda cuando el orden de los se define por relevancia al realizar una búsqueda en la tienda. Por ejemplo, si un cliente selecciona ordenar los resultados por precio, los ajustes de relevancia no tienen efecto en el orden de los resultados.
+
+Hay dos posibles escenarios de configuración de relevancia:
+
+- **Criterios de prioridad:** es la forma de forzar que uno o más criterios tengan mayor prioridad entre los demás. En esta situación no hay pesos, porque todos los productos que tienen esta característica se presentarán primero en el resultado de la búsqueda.
+- **Composición de criterios:** es la forma de distribuir los pesos de cada opción, que van de 0 a 10. Aquí no hay un orden entre los criterios, serán los pesos los que definan la relevancia.
+
+![criterios-es](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/0b54c302ffac20ed831392a3c7d5135d/criterios-es.png)
+
+La información aplicada para establecer la relevancia es:
+
+- **Descuento:** criterio que compara el [Precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#precio-de-lista) y el [Precio base](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicion) registrados para determinar si el producto califica para un descuento.
+- **Fecha de release:** este criterio asigna un valor decreciente automático (entre 1 y 0) a partir de la fecha de registro del producto en la tienda, considerando un intervalo de 90 días. Los productos registrados hoy tendrían un valor de 1 y ese valor disminuiría cada día, hasta convertirse en 0 a partir del día 90. Este valor se multiplica por el peso que introduzca para el criterio **Fecha de release** para establecer la relevancia.
+- **Más vendidos:** número de pedidos del producto en los últimos 90 días.
+- **Más vendidos por ingresos:** total de ganancia adquirida por el producto en los últimos 90 días.
+- **Popularidad:** número de clics de un producto en los últimos 90 días.
+- **Promoción:** criterio que comprueba si existen [Audiencias de las campañas](https://help.vtex.com/es/tutorial/overview-2--tutorials_326#audiencia-de-campanas) o [Promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N) vinculadas al artículo para determinar si el producto clasifica como promoción.
+- **Puntuación del catálogo:** criterio de desempate del orden basado en el valor del campo **Puntuación** registrado en el producto. A efectos de la composición de la relevancia, cuanto mayor sea la puntuación, mayor será el peso, es decir, el comportamiento es descendente: se da prioridad a los productos con una puntuación más alta. Más información sobre el campo y su comportamiento en la guía [¿Cómo funciona el campo Puntuación?](https://help.vtex.com/es/tutorial/como-funciona-el-campo-puntuacion--1BUZC0mBYEEIUgeQYAKcae).
+- **Variedad de matriz disponible:** la relevancia se basa en el porcentaje de SKU disponibles por producto. En un escenario donde el _Producto A_ tiene 3 SKU y 3 de ellos están disponibles, y el _Producto B_ tiene 5 SKU y 2 de ellos están disponibles, el _Producto A_ se destaca sobre _Producto B_ porque el porcentaje de SKU es mayor.
+
+El conjunto de distribución de pesos y criterios genera una puntuación para el producto, lo que ayuda a su posicionamiento en el orden del resultado de la búsqueda.
+
+<div class="alert alert-warning">
+  <p>Si deseas utilizar los criterios de prioridad, recomendamos agregar solo un criterio en este campo. Agregar más criterios compromete la ordenación de los resultados de búsqueda, ya que solo se considerará el primer criterio.</p>
+</div>
+
+De esta manera, es posible adaptar el comportamiento del resultado de búsqueda a una estrategia específica.
+
+## Ejemplo
+
+Una tienda de moda a menudo recibe nuevas colecciones. El administrador de la tienda opta por priorizar artículos de lanzamiento a productos promocionales. Configura la herramienta de la siguiente manera:
+
+> **Criterios de prioridad:**
+> 
+> - Vacío
+> 
+> **Composición de criterios:**
+> 
+> - Popularidad: 7
+> - Fecha de release: 10
+> - Más vendidos: 6
+> - Más vendidos por ingresos: 6
+> - Promoción: 0
+> - Descuento: 0
+> - Variedad de matriz disponible: 10
+> - Puntuación del catálogo: 0 
+
+Si el administrador de la tienda quiere que el lanzamiento sea siempre la prioridad, puede ajustar la Reglas de relevancia de dos maneras:
+
+> **Manera A**:
+> 
+> **Criterios de prioridad:**
+> 
+> - Fecha de release
+> 
+> **Composición de criterios:**
+> 
+> - Popularidad: 7
+> - Más vendidos: 6
+> - Más vendidos por ingresos: 6
+> - Promoción: 0
+> - Descuento: 0
+> - Variedad de matriz disponible: 10
+> - Puntuación del catálogo: 0
+
+> **Manera B**:
+> 
+> **Criterios de prioridad:**
+> 
+> - Vacío
+> 
+> **Composición de criterios:**
+> 
+> - Popularidad: 0
+> - Fecha de release: 10
+> - Más vendidos: 0
+> - Más vendidos por ingresos: 0
+> - Promoción: 0
+> - Descuento: 0
+> - Variedad de matriz disponible: 0
+> - Puntuación del catálogo: 0
+
+## Configurar Reglas de relevancia
+
+Para cambiar la configuración de Reglas de relevancia, sigue los pasos a continuación.
+
+1. En el Admin, haz clic en el módulo **Storefront**.
+2. En **Intelligent Search**, haz clic en **Reglas de relevancia**.
+3. Escoge el criterio cuyo peso deseas cambiar.
+4. Haz clic en los íconos flecha abajo <i class="fas fa-chevron-down"></i> o flecha arriba <i class="fas fa-chevron-up"></i> para definir el número deseado.
+
+   Si deseas cambiar la posición de un criterio de **Composición de criterios** a **Criterios de prioridad**, solo tienes que arrastrarlo por el ícono <i class="fas fa-grip-vertical"></i> a la parte superior según se muestra aquí. Ten en cuenta que cuando el criterio cambia a criterio de prioridad, no se le puede cambiar el peso.
+
+   ![criterios-prioritarios-es](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/1bdaef8e82e1e1801a439a45acb2e4e3/criterios-prioritarios-es.gif)
+5. Para terminar, haz clic en  `Guardar`.
diff --git a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
new file mode 100644
index 000000000..b3dcaa9aa
--- /dev/null
+++ b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -0,0 +1,91 @@
+---
+title: 'Cómo remover el mensaje de error "Request headers must contain only ASCII characters"'
+id: 19psKZvLXrBqqK1bPaTIHG
+status: PUBLISHED
+createdAt: 2024-07-25T16:54:41.663Z
+updatedAt: 2024-07-25T21:25:10.665Z
+publishedAt: 2024-07-25T21:25:10.665Z
+firstPublishedAt: 2024-07-25T21:21:03.197Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: eliminando-mensaje-de-error-request-headers-must-contain-only-ascii
+locale: es
+legacySlug: eliminando-mensaje-de-error-request-headers-must-contain-only-ascii
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras clave__: *request headers, ascii, caracteres especiales, devtools, headers, utm, javascript personalizado, script.*
+
+El mensaje "__Request headers must contain only ASCII characters__" puede mostrarse en el navegador del usuario cuando esté navegando por la tienda e intente acceder a una nueva página o realizar una acción en el sitio web, como por ejemplo, agregar ítems al carrito.
+
+Este escenario se produce si la página o funcionalidad solicitada contiene una cookie con caracteres especiales (no ASCII).
+
+![ascii_1](//images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/2018e90b25b45797270e5daa28032eab/ascii_1.png)
+
+Según las normas de la [IETF](https://www.ietf.org/) (Internet Engineering Task Force), institución responsable de documentar los estándares utilizados en internet, las cookies deben estar compuestas únicamente por caracteres ASCII estándar y deben evitar incluir caracteres especiales (no ASCII). Para más información sobre los caracteres aceptados en cookies y encabezados, accede a [IETF - Request for Comments 7230 - Section 3.2.6 - Field Value Components](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6). 
+
+## Soluciones
+
+Para remover el mensaje de error y permitir que el usuario vuelva a acceder a la página o funcionalidad, deben realizarse las siguientes acciones:
+
+- [Identificar cookies con caracteres especiales](#identificar-cookies-con-caracteres-especiales)
+- [Desactivar cookies con caracteres especiales](#desactivar-cookies-con-caracteres-especiales)
+- [Crear script para limpiar la caché](#crear-script-para-remover-cookies)
+
+### Identificar cookies con caracteres especiales
+
+En la página en la que se muestra el mensaje "__Request headers must contain only ASCII characters__", sigue los pasos a continuación para identificar la cookie que contiene caracteres especiales:
+
+<blockquote><ui>1. Accede al <a href="https://help.vtex.com/pt/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">DevTools</a> en tu navegador pulsando <b>F12</b> o haciendo clic con el botón derecho del mouse y eligiendo la opción <b>Inspect</b>.</ui>
+
+  <blockquote><ui>2. En la barra superior de la pantalla, accede a la pestaña <b>Network</b> y ordena los requests haciendo clic en <b>Status</b>. La información <b>400</b> en el estado indica que la solicitud no se procesó correctamente, lo que puede deberse a errores como cookies incorrectas.</ui>  
+
+![ascii 2ascii_2](//images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/b3e881fcbf68abf42df7b6f45d8cf103/ascii_2.png) 
+
+<blockquote><ui>3. Haz clic en un request y después en la pestaña <b>Preview</b> para identificar si el error encontrado se refiere al mensaje "<b>Request headers must contain only ASCII characters</b>".</ui>
+
+![ascii 3](//images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/06de7bb790b762dbd6b720e45a09e0ab/ascii_3.png)
+
+<blockquote><ui>4. Haz clic en la pestaña <b>Headers</b> y copia los datos de la cookie.</ui>  
+
+![ascii 4](//images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/5b2bfeb184598aa2c32af65f14e4a058/ascii_4.png)
+
+<blockquote><ui>5. Accede a un <a href="https://pages.cs.wisc.edu/~markm/ascii.html">validador online de caracteres ASCII</a> e ingresa la información de la cookie. Si se identifican uno o varios caracteres especiales, los tipos y posiciones se mostrarán en la parte inferior del validador de caracteres.</ui>     
+
+![ascii 5](//images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/86447a853ffa7bd68e097831acdbf1e5/ascii_5.png)
+
+<blockquote><ui>6. Repite los pasos 3 a 5 con todos los requests de error para identificar los que contienen cookies con caracteres especiales.</ui>      
+
+### Desactivar cookies con caracteres especiales
+
+Una vez identificadas las cookies que contienen caracteres especiales, debe verificarse su origen para removerlas de la página. Las fuentes más comunes de cookies incorrectas son:
+
+- [Parámetros UTMs](https://help.vtex.com/es/tutorial/que-son-las-utms-internas--5Pvo8ufYWs00AUeCCEY68a) creados en tu tienda o en campañas de anuncios de Google, Meta, entre otros, que contengan caracteres acentuados. Ejemplo de parámetro UTM utilizado en una fecha conmemorativa: `www.site.com?utm_source=día-de-la-madre`.
+- Javascripts personalizados, donde las implementaciones de frontend utilizadas para almacenar datos u otros tipos de funciones pueden contener caracteres especiales.
+- Scripts de clientes partners que crean cookies con caracteres especiales.
+
+Una vez identifiques el origen de la cookie, realiza los procedimientos necesarios para removerla de la página o solicita al cliente partner que interrumpa el envío de la cookie a tu tienda.
+
+### Crear script para remover cookies  
+
+Al remover la cookie con caracteres especiales, la página o funcionalidad debería restaurarse y ya no se mostrará el mensaje "__Request headers must contain only ASCII characters__". Sin embargo, este escenario solo afectará a los nuevos usuarios de la página, es decir, aquellos clientes que aún no hayan accedido durante el tiempo en que la cookie incorrecta estuvo activa.
+
+Los usuarios que accedieron a la página o funcionalidad mientras la cookie incorrecta estaba activa seguirán viendo en su navegador el mensaje de error "Request headers must contain only ASCII characters". Esto se debe a que la cookie se almacenó en la memoria caché del navegador del usuario.
+
+Para resolver este problema y permitir que todos los usuarios accedan correctamente a la tienda, es necesario crear un script en la página que se ejecute en el navegador del usuario (lado del cliente) para que la cookie incorrecta expire.
+
+El script debe configurar la cookie para que expire en una fecha previa (cualquier fecha anterior a la creación del script). Observa el ejemplo a continuación:
+
+`document.cookie = "cookiename= ; expires = Thu, 01 Jan 1970 00:00:00 GMT"`  
+
+Si lo deseas, también puedes incluir las siguientes funciones en el script:
+- Interceptar valores de cookies durante el request de la página
+- Validar caracteres ASCII en las cookies
+- Hacer que las cookies que contengan caracteres especiales expiren automáticamente
+- Activar la recarga de la página mediante la función `window.location.reload()`  
+
+<div class="alert alert-warning">
+  Remover las cookies mediante script no es una solución definitiva. Como se describe en la sección <b>Desactivar cookies con caracteres especiales</b>, es necesario identificar su origen e interrumpir el proceso de envío de cookies con caracteres especiales.
+</div>
+
diff --git a/docs/tutorials/es/requesting-a-new-organization.md b/docs/tutorials/es/requesting-a-new-organization.md
new file mode 100644
index 000000000..b217bbc4b
--- /dev/null
+++ b/docs/tutorials/es/requesting-a-new-organization.md
@@ -0,0 +1,104 @@
+---
+title: 'Registrar una nueva organización'
+id: 4bTIDPay4fNz39l5XHijAh
+status: PUBLISHED
+createdAt: 2024-06-06T16:21:26.266Z
+updatedAt: 2024-06-07T10:55:22.825Z
+publishedAt: 2024-06-07T10:55:22.825Z
+firstPublishedAt: 2024-06-06T16:27:05.446Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: registrar-una-nueva-organizacion
+locale: es
+legacySlug: registrar-una-nueva-organizacion
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+Para que una empresa se registre en la tienda, debe rellenar el formulario Solicitar una nueva organización de la siguiente manera:
+
+1. Accede al formulario de registro agregando `/organization-request` al final de la URL de tu tienda.
+
+2. Rellena el formulario de solicitud con los datos de la empresa descritos en este documento.
+
+3. Haz clic en el botón `Enviar`.
+
+Una vez enviado el formulario, el equipo de la tienda debe revisar la solicitud en el Admin VTEX y aprobarla.
+
+## Formulario de solicitud
+
+El formulario para crear una nueva organización consta de las siguientes secciones:
+
+- [Solicitar nueva organización](#solicitar-nueva-organización)
+- [Usuario administrador de la organización](#usuario-administrador-de-la-organización)
+- [Centro de costos predeterminado](#centro-de-costos-predeterminado)
+
+### Solicitar nueva organización
+
+La empresa solicitante facilita los datos para realizar el registro, incluidos los campos personalizados.
+
+El formulario incluye los siguientes campos:
+
+- **Nombre de la organización:** nombre de la organización que deseas registrar.
+- **Nombre comercial:** nombre comercial que la empresa utiliza.
+
+### Usuario administrador de la organización
+
+Información sobre el usuario que será designado administrador de la nueva organización.
+
+El formulario incluye los siguientes campos:
+
+- **Nombre:** nombre del usuario.
+- **Apellido:** apellido del usuario.
+- **Email:** email del usuario.
+
+### Centro de costos predeterminado
+
+Información sobre el centro de costos al que se asociará esta organización.
+
+El formulario incluye los siguientes campos:
+
+- **Nombre del centro de costos:** nombre del centro de costos inicial asociado a la organización.
+
+- **Teléfono:** número de teléfono para ponerse en contacto con la organización.
+
+- **Documento empresarial:**  puedes utilizar el número de registro corporativo, el número de identificación fiscal, el número de IVA u otro documento.
+
+- **Inscripción estatal:** número de registro de la empresa.
+
+- **País:** país donde se encuentra el centro de costos.
+
+- **Código postal:** código postal del centro de costos.
+
+- **Dirección:** nombre de la calle donde se ubica el centro de costos.
+
+- **Número:** número de la dirección donde se encuentra el centro de costos.
+
+- **Información adicional:** información que puede complementar la dirección del centro de costos.
+
+- **Barrio:** nombre del barrio donde se ubica el centro de costos.
+
+- **Ciudad:** ciudad donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.
+
+- **Estado:** estado donde se encuentra el centro de costos. Se rellena automáticamente en función del código postal informado.
+
+- **Destinatario:** nombre de la persona que recibirá los pedidos en la dirección informada.
+
+## Verificar solicitudes de organizaciones
+
+Tras realizar la solicitud, el equipo de la tienda debe revisarla en el Admin VTEX en **Apps > Organizaciones B2B y centros de costos > Organizaciones** o escribiendo **Organizaciones** en la barra de búsqueda de la parte superior de la página.
+
+En esta página se muestra una lista de todas las solicitudes de organización realizadas en tu tienda.
+
+Cada organización puede presentar los siguientes status: pendiente, aprobada o rechazada. Las solicitudes pendientes son aquellas que deben ser revisadas.
+
+Para revisar una solicitud sigue los pasos a continuación:
+
+- Haz clic en la organización de la lista o en el ícono <i class="fas fa-ellipsis-v" aria-hidden="true"></i> para verla.
+
+- Si fuera necesario, ingresa un comentario en el campo Agregar observación.
+
+- Haz clic en el botón `Aprobar` o `Rechazar`.
+
+El administrador de la organización recibirá una notificación de la aprobación por email.
+
diff --git a/docs/tutorials/es/requesting-an-additional-trade-policy.md b/docs/tutorials/es/requesting-an-additional-trade-policy.md
index ccebb9156..6cfca02c4 100644
--- a/docs/tutorials/es/requesting-an-additional-trade-policy.md
+++ b/docs/tutorials/es/requesting-an-additional-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Contratación de políticas comerciales adicionales'
 id: 61vuFOw4yGh6nwSmkLJL1X
 status: PUBLISHED
 createdAt: 2021-12-06T23:25:42.650Z
-updatedAt: 2022-12-08T20:01:23.876Z
-publishedAt: 2022-12-08T20:01:23.876Z
+updatedAt: 2024-06-20T23:00:50.418Z
+publishedAt: 2024-06-20T23:00:50.418Z
 firstPublishedAt: 2021-12-06T23:51:25.043Z
 contentType: tutorial
 productTeam: Channels
@@ -19,16 +19,9 @@ En VTEX, el concepto de [política comercial](https://help.vtex.com/es/tutorial/
 
 Mediante las políticas comerciales se determinan las configuraciones de catálogo, precios, promociones, pagos, _stock_, logística y segmentación del público en los canales de venta. Sin embargo, no es necesario [crear una política comercial](https://help.vtex.com/es/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) diferente para cada canal. La misma política comercial puede utilizarse en múltiples canales de venta.
 
-La contratación de políticas comerciales adicionales para integración con conectores certificados (_partners_), conectores nativos u otras tiendas VTEX es gratuita. Obtén más información en el artículo [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
+La contratación de políticas comerciales adicionales para integración con marketplaces certificados y otras tiendas VTEX es gratuita. Obtén más información en el artículo [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
-Para adquirir una política comercial destinada a un canal de ventas externo al ecosistema VTEX, como un _marketplace_ para el que no existe un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), hay dos flujos posibles:
-
-- [Contratar una política comercial para el mercado brasileño](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X#contratar-una-politica-comercial-para-el-mercado-brasileno)
-- [Contratar una política comercial para el mercado internacional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X#contratar-una-politica-comercial-para-el-mercado-internacional)
-
-## Contratar una política comercial para el mercado brasileño
-
-Para contratar una política comercial adicional destinada a operar en el mercado brasileño, tiene que rellenar el [formulario de política comercial adicional](https://docs.google.com/forms/d/e/1FAIpQLSe9qCGB_KM_xsV5e9uNe06JE8tMZrWcv6EuHUOmqTiM8oRW7w/viewform). Si tiene alguna duda, póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)*, seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`.
+Para adquirir una política comercial destinada a un canal de ventas externo al ecosistema VTEX, como un _marketplace_ para el que no existe un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), siga el flujo [Contratar una política comercial para el mercado internacional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X#contratar-una-politica-comercial-para-el-mercado-internacional)
 
 ## Contratar una política comercial para el mercado internacional
 
diff --git a/docs/tutorials/es/resetting-your-two-factor-authentication-app-configuration.md b/docs/tutorials/es/resetting-your-two-factor-authentication-app-configuration.md
index ffd3a93aa..86b64fdf2 100644
--- a/docs/tutorials/es/resetting-your-two-factor-authentication-app-configuration.md
+++ b/docs/tutorials/es/resetting-your-two-factor-authentication-app-configuration.md
@@ -3,8 +3,8 @@ title: 'Restablecer la configuración de la aplicación de autenticación de dos
 id: 4ftaOCZono1MiQia2hxbTy
 status: PUBLISHED
 createdAt: 2023-02-08T13:55:25.623Z
-updatedAt: 2023-02-08T14:26:33.141Z
-publishedAt: 2023-02-08T14:26:33.141Z
+updatedAt: 2024-03-12T18:52:44.442Z
+publishedAt: 2024-03-12T18:52:44.442Z
 firstPublishedAt: 2023-02-08T14:26:33.141Z
 contentType: tutorial
 productTeam: Identity
@@ -17,11 +17,11 @@ subcategory: 4sY1T2qdFehvVmC0tL5xW3
 
 Si ya has [activado el inicio de sesión mediante autenticación de dos factores](https://help.vtex.com/pt/tutorial/enabling-2-factor-authentication-login--4Ae1fcQi12g8u4SkQKCqWQ), pero cometiste algún error durante la configuración o perdiste el acceso a tu aplicación de autenticación de dos factores, es posible que no puedas acceder a tu cuenta VTEX.
 
+## Retomar el acceso al VTEX Admin
+
 Para recuperar el acceso a tu cuenta, sigue estos pasos:
-1. Accede a esta dirección para ver la página de inicio de sesión de tu cuenta:
-```
-https://{nombreDeCuenta}.myvtex.com/admin
-```
+
+1. Accede al VTEX Admin para ver la página de inicio de sesión de tu cuenta.
 2. Rellena tu dirección de email.
 3. Haz clic en `Continuar`.
 4. Haz clic en **Olvidé mi contraseña**.
@@ -32,12 +32,13 @@ https://{nombreDeCuenta}.myvtex.com/admin
 
 Una vez que hayas recuperado el acceso a tu cuenta como se ha descrito anteriormente, puedes restablecer la aplicación de verificación en dos pasos como sigue:
 
-1. Accede a la página de configuración de verificación en dos pasos de tu cuenta en esta dirección:
-```
-https://{nombreDeCuenta}.myvtex.com/admin/myuser/twostepverification
-```
-2. Haz clic en **Configurar** en la sección **Aplicación Google Authenticator**.
-3. Si no tienes la aplicación Google Authenticator instalada, instálala en tu dispositivo móvil.
-4. Escanea el código QR utilizando la aplicación Google Authenticator.
-5. Ingresa el código que aparece en el campo indicado en la página.
-
+1. En la barra superior del Admin VTEX, haz clic en el avatar de tu perfil que tiene la inicial de tu email.
+2. Haz clic en **Configuración del usuario**.
+3. En la sección **Autenticación**, haz clic en **Verificación en 2 pasos**.
+4. Seleccione **App Google Authenticator**.
+5. Haz clic en `Configurar` o en `Modificar' si ya tienes configurada una aplicación de autenticación.
+6. Si no dispone de la aplicación __Google Authenticator__ ([App Store](https://itunes.apple.com/mx/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2)), instálela en su dispositivo móvil.
+7. Escanea el código QR utilizando la aplicación Google Authenticator.
+8. Haz clic en `Siguiente`.
+9. Ingresa el código que aparece en el campo indicado en la página.
+10. Haz clic en `Confirmar`.
diff --git a/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
new file mode 100644
index 000000000..a1bbd645e
--- /dev/null
+++ b/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
@@ -0,0 +1,202 @@
+---
+title: 'Responsabilidades en el ecosistema VTEX'
+id: 3vL9aWICDr3WR64DYi1fJ3
+status: PUBLISHED
+createdAt: 2024-01-31T17:08:24.444Z
+updatedAt: 2024-02-16T17:22:16.507Z
+publishedAt: 2024-02-16T17:22:16.507Z
+firstPublishedAt: 2024-01-31T23:11:13.804Z
+contentType: tutorial
+productTeam: Billing
+author: 1malnhMX0vPThsaJaZMYm2
+slug: responsabilidades-en-el-ecosistema-vtex
+locale: es
+legacySlug: responsabilidades-en-el-ecosistema-vtex
+subcategory: 1VvCpaa8NCA6a0MK6W6oWg
+---
+
+VTEX considera que la colaboración es fundamental para el futuro del ecommerce, y sostiene que las asociaciones son imprescindibles para el éxito en la operación del retailer. Durante la operación de la tienda es habitual que surjan dudas sobre las funciones y responsabilidades de cada player del ecosistema.
+
+Para optimizar la operación de tu tienda y garantizar una comunicación eficaz entre el retailer y el soporte de VTEX, este artículo presenta las responsabilidades de los principales players implicados en una operación de ecommerce. Consulta a continuación las responsabilidades en cada escenario:
+
+- [Integraciones back office (ERP / PIM / WMS)](#integraciones-back-office-erp-pim-wms)
+- [Integraciones con proveedores de pago](#integraciones-con-proveedores-de-pago)
+- [Agencias implementadoras](#agencias-implementadoras)
+- [Integraciones con marketplaces](#integraciones-con-marketplaces)
+
+## Integraciones back office (ERP / PIM / WMS)
+
+Durante la configuración inicial de VTEX, si tu tienda utiliza [integraciones externas con ERP/PIM/WMS](https://developers.vtex.com/docs/guides/erp-integration-guide), es responsabilidad de estos sistemas enviar los productos, precios y stock de tu tienda a VTEX. A continuación, es necesario desarrollar un middleware, que será responsable de enviar y recibir información de VTEX en función de los eventos rutinarios de tu operación.
+
+Después de configurar la integración de productos, precios y stock, así como de desarrollar el middleware, el flujo de información se dará como se ilustra en el diagrama a continuación.
+
+![back-office-en](//images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/0a0be8f8112538def94277ec0e3f176a/integracoes-es-1.PNG)
+
+Durante las operaciones rutinarias, las responsabilidades se dividen de la siguiente manera:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <tr>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Player</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Responsabilidades</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>ERP / PIM / WMS</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">Envío de la siguiente información a VTEX a través de la integración:
+        <ul>
+          <li>Modificaciones en el registro de productos</li>
+          <li>Precios</li>
+          <li>Stock</li>
+          <li>Factura</li>
+          <li>Información de seguimiento del pedido</li>
+          <li>Modificaciones en el pedido</li>
+          <li>Cancelaciones</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>VTEX</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">Envío de la siguiente información al ERP, según lo configurado por la tienda a través de <a href="https://developers.vtex.com/docs/guides/orders-feed" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Orders Feed</a> o <a href="https://developers.vtex.com/docs/guides/orders-feed" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Hook</a>:
+        <ul>
+          <li>Notificaciones de un nuevo pedido creado.</li>
+          <li>Notificaciones sobre el progreso de un pedido.</li>
+        </td>
+    </tr>
+  </tbody>
+</table>
+
+## Integraciones con proveedores de pago
+
+Para procesar los pagos de los pedidos en una tienda VTEX, los integrantes de la infraestructura de pago dividen sus responsabilidades de la siguiente manera:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <tr>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Player</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Responsabilidades</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Retailer</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Contratar el servicio de un proveedor de pago (gateways, adquirentes o subadquirentes).</li>
+          <li>Contratar los servicios de un proveedor de servicios antifraude (opcional).</li>
+          <li>Configurar en la tienda los proveedores de pago y antifraude con los cuales se ha formalizado contrato.</li>
+          <li>Configurar en la tienda los medios y condiciones de pago de acuerdo con las especificaciones de cada contrato establecido con los proveedores de servicios de pago y antifraude.</li>
+          <li>Efectuar manualmente la cancelación o contracargo de un pago cuando este no sea realizado automáticamente por el proveedor de pago o en casos específicos en los que se requiera la intervención manual del retailer.</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Proveedores de pago (gateways, adquirentes o subadquirentes)</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Desarrollar la integración del proveedor de pago según las instrucciones disponibles en <a href="https://developers.vtex.com/docs/guides/integrating-a-new-payment-provider-on-vtex" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Integrating a new payment provider on VTEX</a>.</li>
+          <li>Obtener la certificación <a href="https://developers.vtex.com/docs/guides/payments-integration-pci-dss-compliance" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">PCI-DSS</a> o desarrollar la integración con VTEX utilizando <a href="https://developers.vtex.com/docs/guides/payments-integration-secure-proxy" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Secure Proxy</a> para procesar transacciones de pago que contengan datos sensibles, como tarjetas de crédito, débito y tarjeta de tienda (cobranded).
+          </li>
+          <li>Procesar las transacciones financieras de forma segura y eficaz, permitiendo:
+            <ul>
+              <li>Aprobar o denegar pagos, de conformidad con las políticas internas.</li>
+              <li>Capturar o reembolsar pagos.</li>
+              <li>Adquirente: procesar pagos efectuados con tarjetas de crédito y débito.</li>
+              <li>Subadquirente: intermediar pagos entre adquirentes, proveedores antifraude y retailers.</li>
+              <li>Transmitir información sobre el status de las transacciones de pago al gateway de VTEX.</li>
+            </ul>
+          </li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Proveedor de antifraude</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Realizar análisis de riesgos sobre actividades fraudulentas en transacciones con tarjetas de crédito, débito y tarjetas de tienda (cobranded).</li>
+          <li>Transmitir la información de los análisis al gateway VTEX.</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Gateway VTEX</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Crear transacciones de pago para nuevos pedidos.</li>
+          <li>Enviar información sobre transacciones y pedidos a los partners responsables por procesar o analizar datos de pago (proveedores de pago y antifraude).</li>
+          <li>Registrar todas las acciones que tienen lugar en el flujo de una operación de pago, como la creación, aprobación, cancelación, etc.</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Al detectar cualquier inconsistencia o error durante la operación de pago de un pedido, el retailer deberá:
+
+1. Entrar en contacto con los responsables de la respectiva transacción (proveedores de pago y antifraude).
+
+2. Si la incidencia no se resuelve, ponerse en contacto con el [soporte VTEX](https://help.vtex.com/es/faq/como-funciona-el-suporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe) indicando los detalles de la misma.
+
+## Agencias implementadoras
+
+En el caso de las soluciones CMS nativas, es habitual que el retailer cuente con la colaboración de una agencia de implementación para personalizar la apariencia y la experiencia del cliente en el storefront.
+
+VTEX ofrece las siguientes posibilidades nativas de CMS: [Layout](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj#layout) para tiendas que utilizan [Portal CMS Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj), [Site Editor](https://help.vtex.com/es/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) para las que utilizan [Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) y [Headless CMS](https://help.vtex.com/es/tutorial/headless-cms-visao-geral--3U5gvhHdQL0jczYH8gjX09) para aquellas que usan [FastStore](https://www.faststore.dev/). También es posible integrar tu CMS externo con las API de VTEX basadas en [headless](https://developers.vtex.com/docs/guides/headless-commerce).
+
+Los problemas relacionados con la apariencia del contenido para el usuario final siempre deben tratarse inicialmente con el soporte de la agencia. Algunos ejemplos de estos problemas son:
+
+* Imágenes, títulos o banners incorrectos u obsoletos.
+* Productos no disponibles en el storefront.
+* Páginas en blanco.
+* Menú de categorías incorrecto o desactualizado.
+* Resultados de búsqueda o de colecciones incorrectos o incompletos.
+* Botones de CTA (llamada a la acción), como Comprar, Avísame, Agregar al carrito que presentan un comportamiento inesperado.
+* Precios de productos o valor de envío que no coincidan con lo registrado en la plataforma.
+
+Si la agencia descubre que el problema está en los controles, aplicaciones o componentes nativos de VTEX, ponte en contacto con el [soporte VTEX](https://help.vtex.com/es/faq/como-funciona-el-suporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe), incluyendo todas las pruebas sobre el caso recopiladas por la agencia. Si tienes dudas, consulta el siguiente artículo. 
+
+## Integraciones con marketplaces externos
+
+VTEX tiene una arquitectura multiseller nativa que permite a las tiendas VTEX convertirse en marketplaces o sellers en otras tiendas VTEX. La plataforma también dispone de integraciones nativas con marketplaces externos para ofrecer sus productos sin necesidad de desarrollo. Los marketplaces con integraciones nativas se encuentran en la guía [Marketplaces e integraciones](https://help.vtex.com/es/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V).
+
+Aun así, pueden existir tiendas partner estratégicas para tu empresa que operen fuera de esta red de colaboración nativa. Para casos como este, VTEX permite el desarrollo de [integraciones con marketplaces externos](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide) con conectores externos (hubs) encargados de la comunicación entre una tienda VTEX y un marketplace externo no nativo.
+
+Respecto al soporte a una operación en este contexto, es importante que el retailer comprenda las responsabilidades de cada participante en la operación, que se detallan a continuación.
+
+<div class="alert alert-warning">
+  <p>Las secciones siguientes contemplan una tienda en operación integrada con un marketplace externo vía conector externo. Para saber cómo integrar por primera vez tu catálogo de VTEX con un conector externo, consulta el tutorial <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Catalog Integration</a>.</p>
+</div>
+
+### Actualización o envío de nuevos productos y SKU
+
+Estas son las responsabilidades que conlleva la actualización o el envío de nuevos productos y SKU a un marketplace externo:
+
+| **Player** | **Responsabilidades** |
+|---|---|
+| **VTEX** | Enviar notificación de un nuevo producto o SKU creado o actualizado al endpoint del proveedor proporcionado por el hub y registrado en la plataforma VTEX. |
+| **Conector partner (hub de integración)** | Procesar la notificación y enviar el producto o SKU actualizado al marketplace. <br /><br />Este procesamiento engloba diversas fases, como comprobar si ese SKU ya existe en el marketplace y registrarlo como nuevo si es necesario, validar si el producto está activo y asociado a la política comercial del marketplace, ejecutar una simulación de pedido para comprobar el precio y stock del SKU actualizados, entre otras. |
+| **Marketplace externo no nativo** | Proporcionar los endpoints necesarios para que el hub envíe el SKU actualizado, registre el SKU recibido e informe el status al conector. |
+
+### Actualización o creación de nuevos pedidos
+
+Consulta las responsabilidades que conlleva la actualización o creación de pedidos según el flujo de pedidos:
+
+1. El **marketplace** disponibiliza los productos y el checkout para que el pedido sea realizado y notifica al conector sobre un nuevo pedido creado.
+2. El **conector** se encarga de crear el pedido en VTEX.
+3. VTEX responde al conector con el status de creación del pedido, que puede ser éxito o error. En esta fase, si se produce un fallo en la creación del pedido en VTEX, o si el pedido se crea con el status **Cancelado**, es necesario ponerse en contacto con el soporte del conector.
+4. Una vez creado el pedido en VTEX, la responsabilidad de actualizar su status en el OMS depende de la fase del proceso:
+* Si el status del pedido es Preparando envío o Facturado, por ejemplo, es responsabilidad del **ERP **notificarlo a VTEX.
+* Si el pedido fue cancelado en el marketplace, la responsabilidad recae en el **conector**.
+
+Para más información sobre quién es responsable de cada fase del flujo de pedidos en un escenario de marketplace externo, consulta [Flujo y status de pedidos - Flujo de sellers](https://help.vtex.com/es/tutorial/flujo-y-status-de-pedidos--tutorials_196#flujo-de-seller).
+
+Sigue los pasos que se indican a continuación para identificar al soporte con el que debes ponerte en contacto si hay un problema en la actualización del status del pedido:
+
+1. En el Admin VTEX, accede a **Pedidos > Todos los pedidos**.
+2. Haz clic en el pedido deseado para acceder a la [página de detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl).
+3. En la sección **Historial de pedidos**, haz clic en `Ver interacciones` (botón ilustrado a continuación), y comprueba si hay algún mensaje de error. 
+
+![ver-interacciones-es](//images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/6608d46e87166eda8f12b46e69986260/ver-interacciones-es.png)
+
+Si el mensaje de error no es autoexplicativo, el retailer puede ponerse en contacto con el [equipo de soporte VTEX](https://help.vtex.com/es/faq/como-funciona-el-suporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe) adjuntando capturas de pantalla de las interacciones y el ID del pedido, y el equipo de expertos lo ayudará a identificar el origen del problema.
diff --git a/docs/tutorials/es/responsive-vs-mobile-version.md b/docs/tutorials/es/responsive-vs-mobile-version.md
index d1fc3ba88..d51fa8fba 100644
--- a/docs/tutorials/es/responsive-vs-mobile-version.md
+++ b/docs/tutorials/es/responsive-vs-mobile-version.md
@@ -55,7 +55,7 @@ Principales pantallas mobile utilizadas (puede haber variaciones según el dispo
 
 #### Principales elementos visuales reconocidos en los dispositivos móviles
 
-![menu_mobile_version es](https://images.ctfassets.net/alneenqid6w5/4mispPtTBC2yCoAWQcMQkw/cd547422d5bba04fb7ed04e744229625/modelo_menu_ESPANHOL.png)
+![menu_mobile_version es](//images.ctfassets.net/alneenqid6w5/4mispPtTBC2yCoAWQcMQkw/cd547422d5bba04fb7ed04e744229625/modelo_menu_ESPANHOL.png)
 
 #### ¡La calidad es indiferente al tamaño!
 
diff --git a/docs/tutorials/es/restrict-public-access-to-master-data-fields.md b/docs/tutorials/es/restrict-public-access-to-master-data-fields.md
new file mode 100644
index 000000000..8dffe1c36
--- /dev/null
+++ b/docs/tutorials/es/restrict-public-access-to-master-data-fields.md
@@ -0,0 +1,57 @@
+---
+title: 'Restringir el acceso público a los campos de Master Data'
+id: 5eu1N1h4Vqe8GY1yHXUsvz
+status: PUBLISHED
+createdAt: 2024-06-25T12:54:28.672Z
+updatedAt: 2024-06-25T13:28:43.112Z
+publishedAt: 2024-06-25T13:28:43.112Z
+firstPublishedAt: 2024-06-25T13:28:43.112Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: restringir-el-acceso-publico-a-los-campos-de-master-data
+locale: es
+legacySlug: restringir-el-acceso-publico-a-los-campos-de-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+En [Master Data v1](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw), puedes [crear entidades de datos](https://help.vtex.com/es/tutorial/entidade-de-datos--tutorials_1265#crear-entidad-de-datos) con diferentes restricciones de acceso para cada campo:
+
+* Permitir la lectura sin credenciales
+* Permitir editar sin credenciales
+* Permitir filtrar sin credenciales
+
+Dependiendo de los datos almacenados, el acceso público sin autenticación puede suponer un riesgo para tu negocio. Para aplicar la autenticación y restringir el acceso público a los campos que contienen datos confidenciales, sigue las instrucciones abajo.
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data.**
+2. En Master Data, haz clic en **Aplicaciones**.
+3. Haz clic en el engranaje <i class="fas fa-cog"></i> al lado de **Profile System**:
+
+   ![1-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/74b070908ad01d2f304ef85b3336d90a/1-master-data-confidential-data-es.png)
+4. En **Configuración**, haz clic en **Estructura de datos**.
+
+   ![2-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/af70a12de57c62150baa2889bfcbbeb3/2-master-data-confidential-data-es.png)
+5. Haz clic en la pestaña **Entidades de datos**.
+6. En la fila de la entidad de datos, haz clic en el botón de edición <i class="fas fa-edit"></i>.
+
+   ![3-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/7807d93ab778a6f4634f7e1a5eb7a38d/3-master-data-confidential-data-es.png)
+7. En la fila del campo que contiene datos personales (o que, cuando se utiliza junto con otros campos, constituye datos personales) haz clic en el engranaje <i class="fas fa-cog"></i>. 
+
+   ![4-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/a6f2536154ec9a8dba14d237a00da7db/4-master-data-confidential-data-es.png)
+8. Desmarca las siguientes opciones:
+
+   * **Permitir la lectura sin credenciales**
+   * **Permitir editar sin credenciales**
+   * **Permitir filtrar sin credenciales**
+
+   ![5-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/d59c8ed7478226d25f870226b421068c/5-master-data-confidential-data-es.png)
+9. Haz clic en `Guardar`.
+10. En la fila de la entidad de datos modificada, haz clic en el botón Publicar <i class="fas fa-save"></i> para que se publique la configuración guardada.
+11. Haz clic en `OK`.
+
+## Permisos necesarios
+
+Después de seguir las instrucciones anteriores, es obligatorio disponer de un [rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) con los [permisos](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) necesarios para acceder a la información:
+
+* Al menos un recurso de la categoría **Generic resources** en el producto **Master Data**: **READONLY_USER_CRM**, **POWER_USER_CRM**, **NOREMOVE_USER_CRM** o **ADMIN_CRM**.
+* Al menos un recurso de la categoría **Dynamic storage generic resources** en el producto **Dynamic Storage**:** READONLY_USER_DS**, **NOREMOVE_USER_DS**, **POWER_USER_DS** o **ADMIN_DS**.
diff --git a/docs/tutorials/es/risk-assessment.md b/docs/tutorials/es/risk-assessment.md
new file mode 100644
index 000000000..29f50bafe
--- /dev/null
+++ b/docs/tutorials/es/risk-assessment.md
@@ -0,0 +1,382 @@
+---
+title: 'Evaluación de riesgos'
+id: 4K97IpqkpCpDYsZOSxtfkX
+status: PUBLISHED
+createdAt: 2022-05-26T13:08:53.479Z
+updatedAt: 2024-05-28T16:54:14.044Z
+publishedAt: 2024-05-28T16:54:14.044Z
+firstPublishedAt: 2022-05-26T13:17:48.374Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: evaluacion-de-riesgos
+locale: es
+legacySlug: el-proceso-de-risk-assessment
+subcategory: vONCJSxwN5qZiElOEtKkH
+---
+
+El proceso de evaluación de riesgos (risk assessment) es fundamental para el correcto funcionamiento de un programa de gestión de riesgos de proveedores. Este proceso se compone de cuestionarios de evaluación de riesgos de terceros diseñados para ayudar a una organización a identificar potenciales riesgos entre sus proveedores y partners terceros.
+
+Los cuestionarios se envían a VTEX con el fin de:
+* Evaluar si VTEX cumple los requisitos de seguridad establecidos por el cliente.
+* Registrar detalles técnicos sobre la arquitectura de seguridad.
+* Evaluar los posibles riesgos de la plataforma.
+
+Para proporcionar más información acerca de las evaluaciones de riesgo realizadas por los clientes, VTEX ofrece páginas de preguntas frecuentes que responden las preguntas más comunes sobre la estructura y la seguridad de la plataforma.
+
+Haz clic en los puntos a continuación para acceder a las FAQ de cada tema:
+* [Políticas y compliance](#políticas-y-compliance)
+* [Educación y concienciación sobre seguridad](#educación-y-concienciación-sobre-seguridad)
+* [Gestión de activos](#gestión-de-activos)
+* [Datos y privacidad](#datos-y-privacidad)
+* [Cifrado](#cifrado)
+* [Control de acceso, identificación y autenticación](#control-de-acceso-identificación-y-autenticación)
+* [Seguridad de la plataforma](#seguridad-de-la-plataforma)
+* [Auditoría de logs](#auditoría-de-logs)
+* [Desarrollo seguro](#desarrollo-seguro)
+* [Seguridad física y centros de datos](#seguridad-física-y-centros-de-datos)
+* [Gestión de vulnerabilidades](#gestión-de-vulnerabilidades)
+* [Respuesta y mitigación de incidentes](#respuesta-y-mitigación-de-incidentes)
+* [Recuperación ante desastres y continuidad de negocios](#recuperación-ante-desastres-y-continuidad-de-negocios)
+
+Parte de la información sobre seguridad está restringida a usuarios con acceso al Admin VTEX, por lo que no está presente en el Help Center de VTEX. Para consultar esa información, ingresa a continuación el nombre de tu cuenta VTEX:
+
+Ingrese su [nombre de cuenta](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) VTEX para acceder a la documentación.
+<iframe src="https://help.vtex.com/insertaccountname?id=1ayXEtqawI9yuxFXutiITh" title="Ingrese su nombre de cuenta y haz click en el botón." frameBorder="0" width="400" height="50"></iframe>
+
+<div class="alert alert-warning">Si tiene dificultades para acceder a las preguntas frecuentes, intente instalar la última versión de la aplicación <code>vtex.admin-docs</code> usando la <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">CLI de VTEX</a> y repetir el proceso.</div>
+
+## Preguntas frecuentes - Seguridad
+
+### Políticas y compliance
+
+#### ¿Dispone VTEX de una política de seguridad de la información? ¿Con qué frecuencia se revisa? ¿Esta política se ha distribuido y comunicado a toda la empresa?
+VTEX adopta un enfoque riguroso en materia de seguridad de la información, revisando anualmente su política de seguridad de la información mediante un proceso de gestión de documentos. Todos los empleados aceptan formalmente esta política, que se comunica a toda la empresa a través de nuestros canales internos. La política se basa en las mejores prácticas de seguridad que están alineadas con la norma ISO/IEC 27001 y marcos de referencia reconocidos por el mercado. Además, cumple con los requisitos de las leyes de protección de datos y otras obligaciones de VTEX.
+
+#### ¿Los controles de seguridad de la información de VTEX se someten a auditorías realizas por empresas terceras? ¿Qué certificaciones tiene VTEX?
+VTEX, comprometida con la transparencia y la excelencia en sus prácticas, somete periódicamente sus controles de seguridad de la información a auditorías realizadas por profesionales independientes. Estos auditores actúan con imparcialidad y objetividad, garantizando una evaluación rigurosa y sin sesgos de las medidas aplicadas por VTEX. La importancia de esta práctica radica en la validación externa de las políticas y procedimientos, garantizando que se ajustan a las normas, marcos de gestión y mejores prácticas de seguridad. La auditoría realizada por profesionales independientes refuerza la confianza de clientes, partners y otras partes interesadas, demostrando el compromiso de VTEX con el mantenimiento de altos estándares de seguridad de la información. Actualmente contamos con las siguientes certificaciones:
+* SOC 1 - Tipo 2: informe de control interno sobre sistemas de información financiera.
+* SOC 2 - Tipo 2: informe que abarca la seguridad, disponibilidad, integridad, confidencialidad y privacidad.
+* PCI DSS: validación de controles para proteger los datos del titular de la tarjeta y reducir el fraude de tarjetas de crédito.
+
+Todas estas certificaciones están disponibles en la página [Compliance](https://vtex.com/mx-es/compliance/) en [Trust Hub](https://vtex.com/mx-es/trust/). Además, en calidad de empresa de capital abierto, VTEX aplica los controles exigidos por la ley SOX (Sarbanes-Oxley).
+
+#### ¿Quién es el responsable de gestionar el programa de seguridad de la información de VTEX?
+En nuestra organización, tenemos líderes ejecutivos a cargo del programa de seguridad de la información, así como un delegado de protección de datos (DPO) encargado de coordinar el programa de privacidad. Los equipos, formados por ingenieros y analistas altamente especializados en seguridad de la información, están estructurados de forma específica para brindar soporte a los procesos clave de seguridad.
+
+#### En materia de ciberseguridad, ¿las políticas de seguridad de la información se analizan críticamente y se mantienen para que las obligaciones legales, reglamentarias o contractuales aplicables se cumplan? ¿Con qué frecuencia se revisan?
+Nuestras políticas y procedimientos de seguridad de la información se han elaborado sobre la base de las mejores prácticas y directrices del mercado, como la norma ISO/IEC 27001. Utilizamos herramientas internas de VTEX para gestionar estos instrumentos, y garantizamos su idoneidad a través de revisiones anuales llevadas a cabo por líderes y especialistas en seguridad.
+
+#### ¿Cómo se gestiona el calendario de auditorías y certificaciones de VTEX?
+VTEX cuenta con un equipo especializado en seguridad dedicado a gestionar las certificaciones, garantizando el cumplimiento de todos los requisitos necesarios. Este equipo trabaja para garantizar que todas las certificaciones aplicables se obtengan y renueven de manera eficaz, reforzando el compromiso de la empresa con los más altos estándares de seguridad.
+
+#### ¿Cuántas personas forman el equipo de seguridad de la información?
+VTEX cuenta con un equipo formado por gerentes, ingenieros y analistas altamente especializados en seguridad de la información. Nuestro equipo está estructurado de manera organizada y se compromete a brindar soporte en los procesos principales de seguridad. El equipo de seguridad opera en régimen de disponibilidad 24 horas al día, los 7 días de la semana, y con presencia en diferentes zonas horarias, garantizando una cobertura continua que va más allá del horario comercial.
+
+Además del equipo de seguridad de la información, otros equipos de VTEX también cuentan con personas específicamente asignadas para actuar en los procesos de seguridad, lo que demuestra el compromiso global de la organización con la integridad y protección de los datos.
+
+#### ¿Las políticas y controles de seguridad de la información se aplican contractualmente a los proveedores terceros?
+Todos los proveedores y partners que participan en el procesamiento de nuestros datos o los de nuestros clientes están sujetos a acuerdos contractuales que incluyen cláusulas de seguridad. Estos contratos establecen directrices y requisitos específicos para garantizar una adecuada protección de datos, asegurando el compromiso de todas las partes con los más altos estándares de seguridad de la información. Aprende más sobre nuestros [proveedores terceros de infraestructura](https://vtex.com/mx-es/privacy-and-agreements/subprocessors/).
+
+### Educación y concienciación sobre seguridad
+
+#### ¿Dispone VTEX de procesos y procedimientos de concienciación de seguridad informática?
+VTEX cuenta con varios programas de capacitación recurrentes en seguridad de la información:
+* Onboarding de seguridad para todos los nuevos empleados, que abarca temas como la estructura del equipo de seguridad, canales de comunicación, documentos normativos, políticas, herramientas aprobadas y obligaciones externas, buenas prácticas de seguridad, contraseñas seguras, ingeniería social y gestión de documentos.
+* Capacitación mensual sobre las mejores prácticas de seguridad y sugerencias para las actividades del día a día.
+* Reuniones globales que se repiten mensualmente sobre temas emergentes de seguridad de la información, actualizaciones e información sobre controles de seguridad y buenas prácticas de seguridad de la información.
+* Envío periódico de phishing simulado, herramienta para reportar phishing y capacitación para todos los empleados que hagan clic en la simulación de phishing.
+* Iniciativas presenciales sobre buenas prácticas de seguridad, controles físicos y técnicos.
+
+También contamos con un documento con directrices sobre seguridad de la información y concienciación que describe las iniciativas mencionadas anteriormente.
+
+#### ¿Hay capacitación técnica para el equipo de seguridad?
+Se imparte capacitación interna sobre prácticas de desarrollo seguro, controles de seguridad de la información, respuesta a incidentes y otras capacitaciones que abordan el contexto técnico de la seguridad y la privacidad.
+
+#### ¿Cuenta VTEX con un programa de concienciación enfocado en la reducción de impacto y protección contra el malware? ¿Reciben los empleados capacitación sobre este tema?
+La empresa cuenta con programas internos de concienciación sobre el malware y sus posibles consecuencias. A través de comunicaciones internas y sesiones de capacitación, VTEX mantiene a todos sus empleados al tanto de los riesgos asociados al malware, cómo puede afectar a sus dispositivos y cómo identificar posibles señales de infección. Ante cualquier sospecha de presencia de malware, se ha instruido a los empleados para que contacten al equipo responsable.
+
+Además, mantenemos la protección contra el malware mediante un monitoreo constante utilizando nuestras herramientas de seguridad. Las instancias cuentan con software antimalware que realiza un monitoreo activo del malware en los entornos de producción. Si se detecta malware, la instancia afectada se detiene para permitir que los procesos de escalado automático creen una nueva instancia limpia desde cero.
+
+### Gestión de activos
+
+#### ¿Cómo gestiona VTEX los activos más críticos de la organización?
+Los activos se gestionan de forma centralizada a través de un sistema de gestión de inventario que almacena y monitorea el propietario, la ubicación, el status, el mantenimiento y la información descriptiva de los activos propiedad de AWS. Después de su adquisición, los activos son escaneados y rastreados y se comprueba y monitorea la propiedad, status y resolución de los activos en proceso de mantenimiento.
+
+#### ¿Cómo realiza VTEX el inventario de los activos dentro de la empresa?
+VTEX opera 100 % en la nube y es el mayor socio de AWS en América Latina. Por lo tanto, no es necesario realizar un inventario físico de los activos. Para el inventario de software utilizamos el inventario de AWS Systems Manager, que proporciona visibilidad en nuestro entorno informático de AWS. En el entorno corporativo, empleamos una solución especializada gestionar los endpoints y aplicar reglas de seguridad.
+
+#### ¿Cómo lleva a cabo VTEX la destrucción y eliminación de sus activos (medios extraíbles, almacenamiento flash, etc.)?
+Los dispositivos de almacenamiento de multimedia utilizados para almacenar los datos de los clientes se clasifican como críticos y se tratan adecuadamente, como de alto impacto, a lo largo de su ciclo de vida. Existen normas rigurosas sobre cómo instalar, mantener y finalmente destruir los dispositivos cuando ya no son útiles. Cuando un dispositivo de almacenamiento llega al final de su vida útil, se desactiva utilizando las técnicas detalladas en NIST 800-88.
+
+### Datos y privacidad
+
+#### ¿La empresa dispone de una política de privacidad y protección de datos? ¿Con qué frecuencia se revisa? ¿Esta política se ha distribuido y comunicado a toda la empresa?
+Sí, VTEX dispone de políticas de privacidad y protección de datos, que se revisan anualmente. Las políticas de privacidad interna y externa han sido distribuidas y comunicadas a toda la empresa a través de nuestro canal de anuncios internos. La política de privacidad interna se encuentra alojada en nuestra herramienta de documentos corporativos internos para que todos los empleados puedan consultarla. Accede a la [Política de Privacidad Externa](https://vtex.com/mx-es/privacy-and-agreements/external-notice/) (External Privacy Notice).
+
+#### ¿La organización cuenta con un DPO (Data Protection Officer) o delegado de protección de datos?
+Sí, VTEX cuenta con una DPO encargada de coordinar el programa de privacidad: Angela Fonseca (dpo@vtex.com).
+
+#### ¿Qué tipo de datos personales trata VTEX en nombre de sus clientes?
+VTEX, como encargada del tratamiento, procesa los datos personales de los compradores solo cuando es necesario, de acuerdo con los requisitos de cada módulo de la plataforma para llevar a cabo las operaciones de ecommerce. Consulta a continuación la lista de los datos personales que pueden ser tratados por VTEX:
+* Nombre
+* Email
+* Dirección IP
+* Información de navegación ([cookies](https://vtex.com/mx-es/privacy-and-agreements/vtex-platform-cookies-information/))
+* Información del carrito
+* Información e historial de pedidos
+* Dirección de envío
+* Número de documento de identidad (cuando lo exija el país en el que opera la tienda)
+* Historial de tarjeta de regalo
+* Carrito abandonado
+* Conversaciones de [Conversation Tracker](https://help.vtex.com/es/tutorial/comprendiendo-el-conversation-tracker--tutorials_195)
+* Contraseñas de sesión (cifradas)
+* Tokens generados
+
+La lista de datos anterior se encuentra detallada en el [Data Processing Addendum (DPA)](https://help.vtex.com/es/tracks/datos-y-privacidad--4Lc0i0an0DgnEtB0AUwlcq/5f8hTEw3xOALgqzus9VXKd#data-processing-addendum-dpa).
+
+#### ¿Cómo asegura VTEX el cumplimiento del Reglamento General de Protección de Datos (RGPD) y de la Ley General de Protección de Datos de Brasil (LGPD)?
+VTEX se compromete a cumplir toda la normativa aplicable en materia de protección de datos, incluidos el RGPD y la LGPD. Puedes obtener más información sobre nuestras políticas, contratos y compromiso con el cumplimiento de la protección de datos en nuestro sitio web, en la página [Privacidad y Contratos](https://vtex.com/mx-es/privacy-and-agreements/).
+
+Consulta nuestro [Data Processing Addendum (DPA)](https://vtex.com/mx-es/privacy-and-agreements/data-processing-addendum/) para entender cómo tratamos los datos personales en VTEX.
+
+#### ¿Qué derechos de los titulares garantiza la plataforma VTEX?
+VTEX actúa como encargada del tratamiento de los datos de los consumidores finales procesados por nuestros clientes (retailers). Por este motivo, VTEX no podrá responder directamente a las solicitudes de los titulares. Si el titular de datos (o sus representantes) envía una solicitud, VTEX se lo comunicará al retailer, según lo indique el propio titular.
+
+Como responsable del tratamiento, el retailer define las bases jurídicas y los fines del tratamiento de datos. Si por razones técnicas, contractuales o legales no puedes atender la solicitud, es posible justificar el motivo de la negativa.
+
+Si necesitas ayuda para ejercer los derechos de titulares de datos de alguno de los clientes de tu tienda, consulta [Eliminación de los datos de clientes](https://help.vtex.com/es/tutorial/exclusao-de-dados-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU).
+
+#### ¿Dispone VTEX de una política de clasificación de la información?
+VTEX ha establecido una política de clasificación de la información con el objetivo de orientar a sus empleados sobre la correcta categorización de la información, en función de su nivel de criticidad. Nuestra política tiene como objetivo garantizar la seguridad, integridad y confidencialidad de los datos de VTEX, así como ayudar a gestionar el acceso a esta información de manera apropiada. La política establece los siguientes niveles de clasificación: público, interno y confidencial, y especifica las medidas de seguridad asociadas a cada categoría.
+
+#### ¿De qué manera los datos entran en contacto con terceros, proyectos tercerizados o subcontratados y cómo se protegen y monitorean estas interacciones?
+La infraestructura de VTEX depende enteramente de proveedores terceros, lo que garantiza que los partners externos no tienen acceso a los datos de los inquilinos (tenants). Consulta la lista completa de nuestros subencargados en [Subencargados VTEX](https://vtex.com/mx-es/privacy-and-agreements/subprocessors/).
+
+La seguridad del tratamiento y envío de datos a terceros es una prioridad fundamental para VTEX. Contamos con un enfoque integral que combina tecnología avanzada, procesos de seguridad rigurosos y capacitación continua para empleados. Utilizamos medidas tecnológicas, como el cifrado sólido, para proteger los datos durante su envío y procesamiento. Además, hemos implementado estrictos procesos de seguridad de la información y controles de acceso para garantizar que solamente tengan acceso a los datos personas autorizadas. Como parte de nuestras acciones, también realizamos inversiones continuas en actualizaciones y optimizaciones para garantizar una protección efectiva de los datos compartidos con partners terceros. Consulta [Prácticas de seguridad](https://vtex.com/mx-es/security/security-practices/) para saber más sobre nuestras medidas de seguridad vigentes.
+
+#### ¿Se puede garantizar que los datos no migren más allá de una región geográfica definida?
+Actualmente, la mayoría de los datos almacenados por VTEX se basan en AWS us-east-1. Esto significa que el cliente no puede definir la región geográfica, pero también significa que VTEX no migrará los datos fuera de esa región a menos que el cliente lo autorice.
+
+#### ¿Utiliza VTEX la anonimización de datos?
+En cuanto a la anonimización de los datos, VTEX ha estado utilizando la tokenización como mecanismo para sustituir cualquier dato sensible por otro valor. Básicamente, los datos originales son completamente irrecuperables.
+
+#### ¿Qué puertos y protocolos utiliza VTEX para transferir datos? ¿Cómo se protegen?
+VTEX no transfiere datos a través de servidores, por lo que todos nuestros datos se transfieren vía HTTPS a través del puerto 443. Todos los datos sensibles se almacenan cifrados. Los datos en tránsito se cifran con TLS 1.2 y los datos en reposo lo hacen utilizando los algoritmos AES-256 o RSA con claves de al menos 2048 bits.
+
+### Cifrado
+
+#### ¿Cuáles son las opciones de cifrado en tránsito y en reposo?
+VTEX cuenta con estándares de criptografía definidos para todos sus clientes, tanto para datos en reposo como en tránsito. Para cumplir los requisitos de certificaciones como PCI y SOC 2, VTEX mantiene los datos de los usuarios cifrados en todo momento, tanto en almacenamiento como en tránsito.
+
+Los datos en tránsito están protegidos por el estándar de seguridad del protocolo TLS 1.2 y cualquier conexión que intente utilizar métodos de cifrado obsoletos y poco seguros será denegada.
+
+Al trabajar con el almacenamiento o los datos en reposo, VTEX puede utilizar uno de los siguientes algoritmos para operar con las aplicaciones que necesitan cifrar datos:
+* Cifrado bidireccional
+    * RSA con claves de 2048 bits o más
+    * AES-256
+* Cifrado unidireccional
+    * PBKDF2 basado en SHA-256
+
+Todos los sistemas relevantes realizan copias de seguridad automáticas, con frecuencia predeterminada diaria, pero puede ajustarse según sea necesario para garantizar la integridad y disponibilidad de los datos.
+
+#### ¿Las claves de cifrado se guardan en un lugar seguro?
+Para garantizar un alto nivel de seguridad, las claves de cifrado las proporciona el servicio AWS, reconocido por su fiabilidad y solidez en términos de seguridad. Además, las claves de acceso se almacenan en un área segregada con la adecuada protección de cifrado, garantizando la confidencialidad e integridad de la información.
+
+Las contraseñas de inicio de sesión son un buen ejemplo: antes de almacenarse, las contraseñas pasan por un proceso de hash utilizando el algoritmo PBKDF2 basado en SHA-256. En este proceso solo se almacena el valor hash resultante, lo que garantiza que las contraseñas originales permanezcan seguras y no sean accesibles directamente. Estas medidas de seguridad adicionales garantizan la protección de datos sensibles y dan tranquilidad a los usuarios sobre la confidencialidad de su información.
+
+### Control de acceso, identificación y autenticación
+
+#### ¿Dispone VTEX de una política de gestión de acceso lógico?
+VTEX gestiona eficazmente el acceso lógico, garantizando un control y monitoreo adecuados de los permisos de acceso a sistemas y datos. Nuestras prácticas garantizan el cumplimiento de las políticas de seguridad, aplicando medidas como el principio de privilegio mínimo y la segregación de funciones para garantizar que los usuarios solo tengan acceso a la información necesaria para desempeñar sus funciones específicas, en función de sus necesidades legítimas.
+
+Nuestro procedimiento de revocación de accesos se activa inmediatamente, con la participación directa del equipo de seguridad de VTEX.
+
+En el entorno corporativo contamos con una política de gestión de accesos que sigue las mejores prácticas del mercado. Esto incluye la implementación de la autenticación de dos factores para acceder a nuestros servidores y el uso de VPN cuando sea necesario.
+
+#### ¿Cómo se gestiona la concesión de accesos a los sistemas internos de VTEX?
+En el entorno empresarial, un equipo centralizado se encarga de la gestión de accesos, desde la concesión hasta la revocación, estableciendo métricas y ejecutando procedimientos de concesión de acceso.
+
+Dentro de este equipo, hay grupos específicos encargados de gestionar los sistemas críticos de la empresa. De este modo, cuando un empleado necesita acceso, inicia el proceso a través de nuestro canal de servicio digital, centralizado y automatizado.
+
+A continuación, la solicitud de acceso se evalúa para garantizar que el empleado en cuestión necesita y debe recibir el acceso solicitado. Antes de que el acceso se conceda, el flujo pasa por varias etapas de autenticación, validación y aprobación formal de la solicitud.
+
+#### ¿Limita VTEX el acceso de acuerdo con el principio de mínimo privilegio?
+Sí, VTEX restringe el acceso de acuerdo con el principio de mínimo privilegio. Esto significa que los usuarios reciben [permisos de acceso](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) solo para lo estrictamente necesario en el desempeño de sus funciones, lo que minimiza el riesgo de exposición indebida de información sensible y fortalece la seguridad de los sistemas y datos.
+
+#### ¿Cómo se estructura la arquitectura de autenticación y la gestión de identidades disponible en la plataforma VTEX?
+La plataforma VTEX cuenta con una solución de identidad lista para usar llamada VTEX ID. También brindamos soporte para la integración de [proveedores de identidad SSO](https://developers.vtex.com/docs/guides/login-integration-guide) en el Admin y en el sitio web de la tienda.
+
+El Admin usa [SAML 2.0](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) como protocolo de autenticación, y los clientes de VTEX pueden integrar un proveedor de identidad existente utilizando SAML 2.0 como estándar. El sitio web de la tienda puede integrarse con proveedores de identidad externos a través del protocolo [OAuth 2.0](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2).
+
+Disponemos de un proceso de [gestión de accesos](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) que incluye el acceso a los entornos de producción y otros entornos relacionados.
+
+A continuación, incluimos links a contenido técnico más detallado sobre nuestros controles de autenticación:
+* [Login integration guide](https://developers.vtex.com/docs/guides/login-integration-guide)
+* [SAML 2 integration](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2)
+* [OAuth 2.0 integration](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2)
+
+#### ¿Qué recursos de seguridad en la autenticación y gestión de identidades están disponibles en la plataforma?
+Las contraseñas en VTEX ID deben cumplir con los siguientes requisitos:
+* Longitud mínima de 8 caracteres + token MFA de 6 dígitos.
+* Mínimo de 1 carácter en mayúscula.
+* Mínimo de 1 carácter numérico.
+* Mínimo de 1 carácter especial.
+* No se pueden repetir las últimas 4 contraseñas utilizadas.
+
+Los retailers pueden optar por aplicar la opción [vencimiento de la contraseña](https://help.vtex.com/es/tutorial/autenticacao--21CkKHLKP1o41lUpGhuRUs#aplicar-expiracao-de-senha) a los usuarios del Admin tras un periodo específico, que puede ser de 15, 30 o 90 días.
+
+Además, tienen la opción de integrar un proveedor de identidad externo, lo que les permitiría definir sus propias políticas de contraseña personalizadas. Para más información, consulta [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide).
+
+Si una cuenta se bloquea debido a que el usuario ingresa incorrectamente la contraseña (medida de seguridad), el usuario legítimo aún puede iniciar sesión a través de otros métodos, como recibir un token por email o usar un[ inicio de sesión social integrado](https://help.vtex.com/es/tutorial/configurar-login-com-facebook-e-google--tutorials_513) (Google o Facebook), lo que evita posibles ataques de fuerza bruta contra contraseñas débiles.
+
+#### ¿Ofrece la plataforma VTEX inicio de sesión único (SSO)?
+Como capa adicional de seguridad, proporcionamos el recurso de inicio de sesión único (SSO), disponible tanto en el Admin VTEX de la tienda (entorno administrativo) como en el storefront para los clientes.
+
+El lenguaje de marcado para confirmaciones de seguridad (SAML) es un estándar para el intercambio de datos de autenticación y autorización entre dominios. SAML 2.0, protocolo basado en XML, facilita el SSO en navegadores web. Este protocolo utiliza tokens seguros firmados digitalmente y mensajes cifrados para transmitir datos entre partes de confianza.
+
+Para más información, consulta la guía de integración [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2).
+
+#### ¿Dispone la plataforma de identificación, control de acceso y segregación de los datos de los clientes mediante controles físicos o lógicos?
+VTEX mantiene la segregación de los datos de los clientes mediante sólidos controles lógicos. Todas nuestras aplicaciones son multiinquilino (multitenant) y exigen identificar la tienda de origen en cada request, registrando toda la información específica de cada tienda con su identificador correspondiente. De este modo, toda nuestra infraestructura de servidores se comparte con nuestros clientes.
+
+Es importante destacar que no existe un método de acceso integrado; cada cliente tiene acceso exclusivo a su propia información, lo que garantiza la seguridad y privacidad de los datos.
+
+Este enfoque nos brinda agilidad en las mejoras y correcciones de bugs, mientras posibilita una escalabilidad eficiente para satisfacer las necesidades específicas de cada cliente, manteniendo siempre la seguridad y la resiliencia.
+
+#### ¿Cómo se gestiona el acceso de usuario en la plataforma, incluyendo la transferencia, adición, edición y eliminación de cuentas?
+La gestión de usuarios administrativos se realiza directamente a través del Admin VTEX. A los usuarios administrativos se les asignan perfiles de acceso que pueden contener uno o varios [permisos](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3), establecidos por el [usuario titular](https://help.vtex.com/es/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy) de la cuenta o por usuarios con roles User Administrator - RESTRICTED o con un rol personalizado que contenga el [recurso](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) Save User. Para más información, consulta [Gestionar usuarios](https://help.vtex.com/es/tutorial/managing-users--tutorials_512).
+
+#### ¿Dispone la plataforma de funcionalidades para gestionar, organizar y personalizar los permisos de gestión de la tienda?
+Cada acción en VTEX, como acceder a una página en el Admin o hacer una llamada de API, implica un request a nuestra infraestructura. Para garantizar la seguridad de estas operaciones contamos con License Manager, el sistema encargado de comprobar si un usuario tiene los permisos adecuados para realizar una acción en la plataforma. Para facilitar la gestión de estos permisos, License Manager se basa en recursos y roles.
+
+Un recurso es una entidad asociada a una acción o información dentro de nuestra infraestructura. Por ejemplo, el recurso Product management permite a un usuario acceder y editar el formulario de registro de productos en el Catálogo. Para obtener más detalles sobre cada recurso disponible, consulta [Recursos del License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3).
+
+Los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) determinan el conjunto de recursos a los que un grupo de usuarios puede acceder en VTEX. Cada usuario administrativo puede ser asociado a uno o varios roles. Al crear un nuevo rol, tienes la opción de utilizar uno de los [Roles de usuario predefinidos](https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy) que proporciona VTEX o crear [uno personalizado](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc), seleccionando cada recurso necesario.
+
+### Seguridad de la plataforma
+
+#### ¿La plataforma utiliza certificados SSL (Secure Sockets Layer)?
+SSL (Secure Sockets Layer) es un protocolo desarrollado para aumentar la seguridad de los datos transmitidos por internet. Las conexiones vía SSL son especialmente recomendables para enviar información como números de tarjetas de crédito, contraseñas y cualquier otra información confidencial a través de Internet.
+
+No es necesario solicitar la compra del certificado SSL, ya que VTEX genera uno para tu tienda y garantiza su renovación automática. El certificado se emite a través de Let's Encrypt y su creación es responsabilidad de VTEX en el momento del go live de la tienda. Aprende más en [Certificado de seguridad (SSL)](https://help.vtex.com/es/tutorial/certificado-de-seguridad-ssl--tutorials_1308).
+
+#### ¿Cómo se gestionan los parches de seguridad?
+Nuestros clientes no son responsables de aplicar los parches, ya que VTEX realiza un proceso de gestión de parches que asegura que todos los inquilinos utilicen la misma versión de software.
+
+VTEX gestiona los releases de software en actualizaciones principales, secundarias y parches. Los parches y las actualizaciones secundarias no afectan a los contratos de API y pueden extenderse a todos los clientes sin afectar la funcionalidad de la tienda. Los componentes del sistema operativo y de las aplicaciones, como bibliotecas, se actualizan periódicamente y se someten a rigurosos controles de seguridad.
+
+#### ¿Se monitorea la plataforma para evaluar su desempeño? ¿Cuáles son las variables que definen la escalabilidad de la plataforma?
+La plataforma VTEX es una solución SaaS (Software as a Service) y se puede acceder a ella mediante cualquier navegador de internet. VTEX se encarga de proporcionar y actualizar periódicamente la solución con nuevas funcionalidades y de monitorear por completo su funcionamiento. Además, hay equipos especializados que garantizan la escalabilidad de la plataforma monitoreando constantemente el desempeño de cada tienda.
+
+#### ¿Restringe la plataforma el acceso a IP públicas en internet?
+Es posible bloquear el acceso al entorno administrativo de la tienda (VTEX Admin) para IP específicas. No obstante, el sitio web de la tienda permanece abierto al público en general. Para solicitar bloqueos específicos, ponte en contacto con nuestro [soporte](https://help.vtex.com/es/support).
+
+#### ¿Funciona la solución con un protocolo seguro (HTTPS)?
+La plataforma VTEX funciona con el protocolo seguro HTTPS. Este protocolo garantiza que la comunicación entre los componentes del sistema se mantenga protegida y los datos se transporten de modo seguro.
+
+#### ¿La solución utiliza WAF?
+Contamos con una solución de WAF como parte del producto add-on [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). Consulta la documentación de [WAF](https://help.vtex.com/es/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn) para más información.
+
+#### ¿Utiliza la plataforma VTEX el concepto API first?
+VTEX prioriza el desarrollo de API first, donde todos los datos que se manejan en la plataforma pueden ser manipulados a través de API. Aprende más sobre las [API de VTEX](https://developers.vtex.com/docs/api-reference).
+
+VTEX segrega las capas de backend, API, frontend y componentes, garantizando que cada responsable solo interactúa con la capa que le compete. Accede a la documentación para desarrolladores en el [Developer Portal](https://developers.vtex.com/).
+
+#### ¿Proporciona la solución detección de anomalías, es decir, tiene la capacidad de detectar comportamientos inusuales y posibles tráficos maliciosos, además de los comportamientos de cuentas de usuario?
+La plataforma VTEX está constantemente monitoreada por un sistema de monitoreo gestionado por el equipo de seguridad de VTEX. Disponemos de un conjunto integral de controles que abarca toda la plataforma y se encuentra conectado a los sistemas en todo momento para detectar una amplia gama de anomalías. Este monitoreo es un esfuerzo continuo y gradual, y nuestro equipo responsable trabaja constantemente para agregar nuevas reglas y alertas.
+
+Algunas de estas alertas se reenvían a nuestros equipos internos, mientras que otras se envían directamente a los administradores de cada tienda. También hay alertas que solo se registran y no generan notificaciones. Por ejemplo, los intentos fallidos de inicio de sesión se limitan y registran, pero no generan alertas. Sin embargo, el propietario de la cuenta recibirá un email si un usuario intenta modificar las credenciales administrativas.
+
+El producto add-on [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) genera algunas alertas adicionales para reforzar aún más la seguridad y ofrece a los retailers más independencia para realizar su propio monitoreo.
+
+#### ¿Cómo se monitorea la plataforma para evaluar su desempeño? ¿Cuáles son las variables que definen la escalabilidad de la solución?
+Nuestra plataforma está equipada con varios indicadores de rendimiento que nos alertan de posibles problemas. Los indicadores incluyen métricas de CPU y memoria de los servidores, tiempo de respuesta de cada request y volumen promedio de ventas. Mantenemos un monitoreo continuo de estos y otros indicadores, con el soporte de una inteligencia artificial (IA) basada en una heurística propia. Esta IA identifica y notifica a nuestro equipo cada vez que se produce una desviación del estándar previsto.
+
+Para atender estas alertas, contamos con un equipo de ingenieros disponible las 24 horas del día, 7 días a la semana. Este equipo está siempre de guardia y listo para intervenir en caso de que ocurran problemas técnicos, garantizando así la estabilidad y el buen funcionamiento de nuestra plataforma.
+
+### Auditoría de logs
+
+#### ¿Cuál es el contenido mínimo de logs que registra la plataforma?
+Todas las operaciones sensibles que tienen lugar en la plataforma se registran automáticamente en logs y esta funcionalidad no puede ser desactivada. VTEX almacena todos los logs de errores de la plataforma VTEX en un software SIEM (Security Information and Event Management), cuyos datos están disponibles para el equipo de VTEX con el fin de analizar y mejorar el producto. Además, VTEX monitorea determinados patrones en los logs de la aplicación y la infraestructura que sugieren riesgos potenciales para la seguridad del sistema. En caso de identificarlos, se emiten alertas o incluso se aplican contramedidas automáticas.
+
+Asimismo, VTEX también registra diversas operaciones, incluyendo autores y marcas de tiempo en [Audit](https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA), un módulo disponible en el Admin VTEX que permite buscar e investigar el historial de logs mediante el uso de filtros. Cada módulo de la plataforma cuenta con un equipo de desarrollo específico que analiza y decide la información que se registra en ese módulo. Consulta la lista de[ Eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
+
+#### ¿Cómo pueden los clientes de VTEX acceder en tiempo real a todos los logs de la plataforma?
+VTEX no permite el acceso a sus sistemas internos, con el fin de preservar la privacidad y seguridad de nuestros clientes, así como para garantizar el cumplimiento de la normativa y legislación vigente.
+
+Sin embargo, disponibilizamos logs de diversos [eventos](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ) en [Audit](https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA) y permitimos que nuestros clientes soliciten logs de eventos específicos abriendo un ticket vía [soporte](https://help.vtex.com/es/support). Además, pueden implementar una capa de proxy inverso antes de VTEX, lo que proporciona una mayor visibilidad de los requests que llegan a su entorno. Este enfoque permite a los clientes tener un control más detallado y personalizado del flujo de datos en su infraestructura, manteniendo al mismo tiempo la seguridad y privacidad necesarias.
+
+### Desarrollo seguro
+
+#### ¿Cuáles son las mejores prácticas de seguridad en desarrollo que utiliza la empresa?
+El proceso de desarrollo de software sigue etapas automatizadas para garantizar su eficiencia. Cuando un equipo de desarrollo finaliza una pieza del software, esta se marca con una identificación en el sistema de control de versiones. Esto activa automáticamente su implementación en un entorno de prueba denominado `BETA` o en producción real, conocido como STABLE.
+
+Además de las pruebas realizadas por especialistas o incluso por los propios clientes en el entorno BETA, existen pruebas automáticas que se actualizan para ajustarse a cambios en el software o su infraestructura. Estas pruebas son esenciales para detectar problemas que puedan surgir en la nueva versión o debido a cuestiones técnicas. Este enfoque garantiza la estabilidad y calidad del software durante todo su ciclo de vida.
+
+#### ¿Están los entornos de desarrollo, staging/QA y producción totalmente segregados? ¿Tienen los desarrolladores de la empresa acceso al entorno de producción?
+Sí, todos los entornos están totalmente segregados. El entorno de producción solo puede implementarse mediante el proceso de gestión de cambios, que está automatizado.
+
+#### ¿Existen pautas y estándares de codificación de seguridad para el desarrollo de aplicaciones?
+Los desarrolladores de VTEX siguen los principios OWASP para garantizar la calidad y la seguridad del código. La revisión por pares es obligatoria, proporcionando un nivel adicional de garantía de calidad y seguridad. Además, cada código de producción es aprobado por al menos dos desarrolladores que tienen conocimientos de seguridad.
+
+Los ingenieros de VTEX adoptan los métodos descritos en OWASP Top 10 para evitar la inserción de código malicioso. Para reforzar aún más la seguridad, VTEX ha implementado un sistema de escaneo de código en el repositorio, revisado minuciosamente por especialistas en seguridad.
+
+Todos los miembros del equipo han recibido capacitación en desarrollo seguro, y estos conocimientos se optimizan continuamente mediante capacitación y pruebas periódicas.
+
+#### ¿VTEX realiza análisis de vulnerabilidad en bibliotecas y paquetes de software?
+Sí, VTEX cuenta con un proceso de análisis de vulnerabilidades en bibliotecas y paquetes de software como parte de sus prácticas de seguridad. Este análisis se realiza periódicamente para identificar cualquier vulnerabilidad o fallo de seguridad presente en las bibliotecas y paquetes utilizados en el desarrollo de software. Este enfoque proactivo ayuda a garantizar que solo se integren en los sistemas de la empresa componentes seguros y libres de vulnerabilidades, reforzando así la seguridad de sus soluciones y protegiendo los datos de los clientes.
+
+### Seguridad física y centros de datos
+
+#### ¿Dispone VTEX de medidas de seguridad para la protección física de los dispositivos y equipos de red?
+La plataforma VTEX es una solución SaaS (Software as a Service) alojada en un entorno altamente controlado y seguro. Como parte de nuestra política de gestión de riesgos, los proveedores son reevaluados periódicamente en relación con sus prácticas de seguridad y compliance. Es importante destacar que VTEX es una empresa 100% cloud commerce, que opera exclusivamente en la infraestructura de Amazon Web Services (AWS). No tenemos servidores físicos propios para prestar servicios.
+
+Tanto nuestros datos como los de nuestros clientes se encuentran alojados en AWS, uno de los principales proveedores a nivel mundial de servicios de infraestructura en la nube pública. Tenemos acuerdos con AWS para garantizar una línea base de seguridad física y protección del entorno para la ejecución de nuestros servicios. Sugerimos a nuestros clientes que revisen los [controles de seguridad física proporcionados por AWS](https://aws.amazon.com/es/compliance/data-center/controls/?nc1=h_ls) como parte de su debida diligencia al considerar la seguridad de los datos en la plataforma VTEX.
+
+#### ¿Cómo aplica VTEX las medidas de seguridad física para proteger el centro de datos?
+VTEX es una empresa basada íntegramente en cloud commerce, que utiliza Amazon Web Services (AWS) como proveedor de sus centros de datos. AWS opera sus centros de datos de acuerdo con las [directrices de Tier III+](https://aws.amazon.com/es/compliance/uptimeinstitute/?nc1=h_ls), asegurando así un alto estándar de confiabilidad y seguridad.
+
+En cuanto a la seguridad de nuestras oficinas, VTEX mantiene oficinas en diversas partes del mundo y aplica estrictos controles de seguridad física en todas sus instalaciones. Esto incluye monitoreo y control de acceso en todas las oficinas, supervisados por un equipo de seguridad profesional. El acceso físico está estrictamente controlado en los puntos de entrada de los edificios, mediante sistemas de vigilancia como torniquetes y otros dispositivos electrónicos. Todos los accesos autorizados se registran para garantizar un control total de las entradas y salidas.
+
+Además, nuestras oficinas están equipadas con sistemas de circuito cerrado de cámaras de televisión (CCTV), que garantizan la vigilancia continua y la grabación de imágenes de acuerdo con los requisitos legales y de cumplimiento de la normativa. También implementamos controles avanzados de energía y supresión de incendios, en línea con las mejores prácticas del sector, para evitar fallos y sobretensiones eléctricas, garantizando la seguridad e integridad de nuestras instalaciones físicas.
+
+#### ¿En qué países y ubicaciones se encuentran los centros de datos?
+Principalmente, VTEX utiliza las siguientes regiones de datos de AWS para los propósitos descritos:
+* AWS Norte de Virginia: almacenamiento de datos primario.
+* AWS Norte de California: local de backup
+
+### Gestión de vulnerabilidades
+
+#### ¿Con qué frecuencia realiza VTEX escaneos de vulnerabilidad?
+Las evaluaciones de vulnerabilidad se realizan de forma continua. Cada verificación debe ser realizada nuevamente hasta que sea aprobada sin encontrar problemas. Un auditor las aceptará durante los periodos de recertificación.
+
+#### ¿Las personalizaciones o configuraciones del producto realizadas por los clientes podrían introducir vulnerabilidades de seguridad en la plataforma? En caso afirmativo, ¿cómo se gestionan estas eventualidades?
+Los retailers y cualquier agencia implementadora que estos contraten tienen la libertad de realizar personalizaciones y ajustes en la plataforma dentro de sus propios entornos. En caso de que se detecten vulnerabilidades en los sistemas de VTEX, nuestro equipo de seguridad y desarrollo actúa con rapidez para solucionar estos problemas. Debido a la naturaleza personalizable de la plataforma, es responsabilidad del retailer y de la agencia implementadora hacer frente a las vulnerabilidades que puedan surgir como resultado de las personalizaciones realizadas durante el desarrollo. Para más información, consulta[ Responsabilidades en el ecosistema VTEX](https://help.vtex.com/es/tutorial/responsabilidades-en-el-ecosistema-vtex--3vL9aWICDr3WR64DYi1fJ3#agencias-implementadoras).
+
+### Respuesta y mitigación de incidentes
+
+#### ¿Dispone VTEX de un plan formal de respuesta a incidentes?
+Sí, VTEX cuenta con un protocolo formal de respuesta a incidentes de seguridad que abarca las fases clave del proceso: preparación, identificación de amenazas, contención, eliminación, recuperación y restauración. Este procedimiento también incluye un plan de comunicación integrado que se aplica en todas las fases de la respuesta. Además, contamos con manuales detallados para orientar al equipo de servicio. También realizamos pruebas de penetración de caja gris (gray box) anualmente para evaluar y aumentar continuamente nuestras medidas de seguridad.
+
+#### ¿Dispone VTEX de un calendario de pruebas de penetración? ¿Con qué frecuencia se realizan las pruebas?
+Las pruebas de penetración (pentest) se realizan cada seis meses en VTEX. Los retailers que deseen realizar pruebas de penetración y análisis de vulnerabilidades en sus entornos necesitan contratar el producto add-on [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) y se les alienta a compartir los resultados con VTEX, posibilitando que nuestro equipo de seguridad aborde cualquier posible problema identificado.
+
+#### ¿Cuenta VTEX con un procedimiento de respuesta a incidentes para fuga de datos que cumpla con las leyes de protección de datos personales?
+Sí, el plan de respuesta a incidentes de seguridad de VTEX prevé incidentes relacionados con fugas de datos y cumple con las leyes de protección de datos personales. Abarca las etapas esenciales del proceso: preparación, identificación de amenazas, contención, eliminación, recuperación y restauración. Este procedimiento también incluye un plan de comunicación integrado que se aplica en todas las fases de la respuesta.
+
+#### ¿Qué controles utiliza VTEX para mitigar los ataques de ransomware?
+VTEX utiliza un enfoque integral para mitigar los ataques de ransomware, empleando medidas como antivirus avanzados, firewalls y filtros de contenido para bloquear el malware. Además, mantenemos copias de seguridad periódicas de los datos críticos, lo que garantiza la capacidad de restaurarlos sin ceder a las exigencias de los atacantes. Las actualizaciones de seguridad y la capacitación para concienciar a los empleados son prioritarias, junto con el monitoreo constante de las actividades para detectar comportamientos sospechosos. Estas medidas combinadas forman una sólida defensa contra la creciente amenaza del ransomware.
+
+### Recuperación ante desastres y continuidad de negocio
+
+#### ¿Dispone VTEX de un plan de continuidad de negocio?
+VTEX cuenta con un plan de continuidad de negocio cuidadosamente diseñado para hacer frente a los problemas derivados de las emergencias. Este plan pretende establecer una base sólida para la reanudación rápida y eficaz de las operaciones habituales, independientemente de la naturaleza de la emergencia, garantizando así una transición fluida y minimizando los posibles impactos.
+
+#### ¿Dispone VTEX de un plan de recuperación ante desastres?
+VTEX ha adoptado un plan de recuperación ante desastres centrado en garantizar la continuidad operativa y la disponibilidad de recursos críticos en situaciones de emergencia. Este plan abarca directrices detalladas sobre cómo actuar ante incidentes imprevistos, caracterizados como crisis, que pueden surgir de catástrofes naturales, ciberataques o cualquier otro suceso disruptivo. Incorporamos etapas cruciales de recuperación, incluida la definición de objetivos RPO (Recovery Point Objective) y RTO (Recovery Time Objective), así como la realización de pruebas de copia de seguridad, garantizando la eficacia y una rápida aplicación del plan en escenarios reales.
+
+#### ¿Prueba VTEX periódicamente el plan de recuperación ante desastres?
+El plan de recuperación ante desastres se prueba al menos una vez al año para garantizar su eficacia. No probamos todo el plan en un solo evento; los distintos componentes o procesos con ciclos de vida independientes se prueban en función de su relevancia y la frecuencia requerida. En cualquier caso, cada pieza se somete a pruebas anuales.
+
+Si alguna parte del plan resulta ineficaz, deberá elaborarse una nueva versión del proceso para solucionar el problema. Tradicionalmente, los eventos previos al Black Friday y al Cyber Monday ofrecen la oportunidad ideal para realizar pruebas de recuperación ante desastres.
diff --git a/docs/tutorials/es/roles.md b/docs/tutorials/es/roles.md
index eaf89cb3e..f2afd70ac 100644
--- a/docs/tutorials/es/roles.md
+++ b/docs/tutorials/es/roles.md
@@ -1,105 +1,68 @@
 ---
 title: 'Roles'
 id: 7HKK5Uau2H6wxE1rH5oRbc
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-04-08T15:21:05.110Z
-updatedAt: 2022-10-04T19:58:47.622Z
-publishedAt: 2022-10-04T19:58:47.622Z
+updatedAt: 2023-11-30T21:36:49.415Z
+publishedAt: 2023-09-26T13:32:10.280Z
 firstPublishedAt: 2020-04-08T20:52:12.334Z
 contentType: tutorial
 productTeam: Identity
-author: 127RQ7SUoFfyTh5gbXUpdM
+author: 1malnhMX0vPThsaJaZMYm2
 slug: roles
 locale: es
 legacySlug: como-crear-perfil-de-acceso, perfiles-de-acceso
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-Toda acción en la plataforma VTEX, como acceder a una página en la interfaz administrativa, pulsar un botón o hacer una llamada a una de nuestras APIs, implica un request a nuestra infraestructura. Como es común que las interfaces administrativas sean compartidas por los diversos colaboradores de una empresa, es importante poder limitar el acceso a las acciones críticas dentro de una cuenta. De este modo, se minimiza la posibilidad de disrupciones en la operación de una tienda y se garantiza que cada usuario tenga acceso apenas a lo que le compete.
+La página **Roles** en el Admin VTEX permite gestionar los [roles](https://help.vtex.com/es/tutorial/control-de-acceso--4rM3gyiWqtkim4Q8hOvLTC#roles) registrados en tu tienda y los usuarios asociados a los mismos. Accede desde la barra superior del Admin VTEX haciendo clic en el avatar de tu perfil, marcado por la inicial de tu email, y luego en **Configuración de la cuenta** > **Roles de usuario**.
 
-## ¿Qué es un rol?
+En la página **Roles** puedes realizar las siguientes acciones:
 
-En VTEX, utilizamos un sistema basado en **recursos** para obtener mayor precisión en el control de acceso. Un **recurso** es una entidad asociada a una acción o información dentro de nuestra infraestructura. Cada vez que nuestros sistemas reciben un request, se realiza un análisis de seguridad para asegurar que el usuario responsable de la llamada tiene el permiso necesario. Para que el request tenga éxito, el usuario debe tener en su cuenta los recursos asociados a ese request.  
+* [Crear rol](#crear-rol)
+* [Buscar rol](#buscar-rol)
+* [Editar rol](#editar-rol)
+* [Eliminar rol](#eliminar-rol)
 
-Actualmente trabajamos con unos cientos de recursos diferentes en los productos VTEX. Para facilitar la gestión de acceso de usuarios por parte de los administradores de una cuenta, existe el concepto de **Rol de usuario**. Para más detalles, lea [Recursos del License Managerr](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
+![roles-es](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/61435c94a6654fd066e3b0f5f8cd2fd0/roles-es.png)
 
-Un **Rol de usuario** es un conjunto de recursos creados para satisfacer un tipo común de usuario. Por ejemplo, los operadores de call center suelen realizar un conjunto bien definido de tareas. Entendiendo esto, un administrador de cuenta, teniendo acceso a los [recursos](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) necesarios, puede crear un **rol** personalizado con todos los permisos necesarios para aquellos colaboradores y controlar el acceso de todos ellos al mismo tiempo.
+La página muestra en formato de tabla una lista con todos los roles registrados en la cuenta y su respectiva información: 
 
-### Tipos de roles
+| **Columna** | **Descripción** |
+|---|---|
+| **Nombre** | Nombre del rol. |
+| **Usuarios** | Número de usuarios asociados al rol. |
+| **Tipo de rol** | Tipo de rol, que puede ser __Predefinido__ o __Personalizado__. Para más información sobre cada uno de ellos, consulta [Tipos de rol](https://help.vtex.com/es/tutorial/control-de-acceso--4rM3gyiWqtkim4Q8hOvLTC#tipos-de-rol). |
+| **Productos** | Productos de License Manager incluidos en el rol. Consulta los productos disponibles en la columna __Producto__ de la tabla en [Recursos de License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3). |
+| **Fecha de creación** | Fecha de creación del rol personalizado. Los roles predefinidos o creados antes de diciembre de 2023 carecen de información de fecha en esta columna. |
 
-Al crear un nuevo **rol de usuario** para su tienda, puedes crear un perfil personalizado, seleccionando cada recurso necesario, o uno de los roles predefinidos. Vea aquí todos los [roles predefinidos](https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#).
-
-Para crear roles personalizados, lea más detalles en [Recursos del License Manager](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
-
-## Creando un rol
-
-Los roles de acceso pueden ser gestionados a través del panel administrativo de su cuenta VTEX. En el menú lateral del [Admin](https://help.vtex.com/es/subcategory/visao-do-geral-do-admin--Se4oi5LroIII2Ei0uGAoE), basta acceder a **Configuraciones de la cuenta > Configuración de la cuenta > Roles de usuario**.
-
-![Lista roles](https://images.ctfassets.net/alneenqid6w5/5SsjVcIztKJQ3yxY1udwOH/1b6a2abc5a10006d758e31806564d378/last_with_shadow_Wed_Apr__8_16_55_01_-03_2020.png)
-
-Esta pantalla muestra una lista de todos los **roles** registrados para la cuenta. En una cuenta recién creada, apenas el rol de *Owner (Admin Super)* se listará. Este perfil da al usuario acceso sin restricciones a todos los **recursos** de la plataforma.
+En una cuenta recién creada, solo aparecerá en la lista el rol _Owner (Admin Super)_. Dicho rol permite al usuario acceder sin restricciones a todos los recursos nativos de la plataforma.
 
 <div class="alert alert-warning">
-Algunos productos, como <a href="https://help.vtex.com/es/tracks/vtex-payment--7iCCIoIZFmd9OabU6QlmXu/1lZWKCGdy7xpYjukTLfFJL">VTEX Payment</a>, son contratados por separado. Los recursos asociados a estos productos no vienen incluidos en el rol de <i>Owner (Admin Super)</i>. Para activar los recursos asociados a estos productos, debes utilizar los roles correspondientes.
+  <p>El número de usuarios con el rol <em>Owner (Admin Super)</em> debe ser el menor posible. También hay que asegurarse de que haya visibilidad y control sobre quién recibe este acceso.</p>
 </div>
 
-La cantidad de usuarios con el rol *Owner (Admin Super)* debe ser la menor posible. Además, debe asegurarse de tener visibilidad y control sobre quién recibe este acceso.
+## Crear rol
 
-<table>
-  <tr>
-    <td style="border-left: 4px solid #F71963;" bgcolor="#FFE6E6"> <b>¡Atención!</b> El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas por la fuga de credenciales de acceso.</td>
-  </tr>
-</table>
+Para registrar un nuevo rol, haz clic en `+ Crear rol`. Para más detalles sobre cómo rellenar el formulario, consulta el artículo [Crear nuevo rol](https://help.vtex.com/pt/tutorial/crear-nuevo-rol--qGtNQpKSSAduX94l2WZBW).
 
-En el caso de los usuarios que no deben tener acceso sin restricciones a la plataforma, es importante crear **roles** que limiten los recursos disponibles solo a los estrictamente necesarios para aquel tipo de usuario. Esto es posible haciendo clic en **Nuevo rol**.
+## Buscar rol
 
-![Nuevo perfil de acceso](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/377d5de0c9b4af5667a4e8f10c171ae0/last_with_shadow_Wed_Apr__8_17_06_18_-03_2020.png)
+Puedes buscar un rol ingresando parte de su nombre en la barra de búsqueda. Los resultados se actualizarán en tiempo real en la lista.
 
-Esta pantalla le permite crear un nuevo rol. Esto puede hacerse en base a formatos ya definidos, creados por el equipo de VTEX para atender escenarios comunes en las operaciones, o de forma personalizada, seleccionando a qué recursos de cada producto deben tener acceso todos aquellos que tengan este rol asociado a su usuario.
+## Editar rol
 
-Haciendo clic en **Elegir rol**, el menú *desplegable* presenta una lista de roles predefinidos.  
+Puedes editar los recursos y usuarios relacionados con un determinado rol; solo hay que hacer clic en el ícono de `⫶` en la fila del rol que deseas editar y a continuación en <i class="fas fa-pencil-alt"></i> `Editar`.
 
-![Menú roles predefinidos](https://images.ctfassets.net/alneenqid6w5/4XGZb5WvW216z8RfX5Vp3c/f4a7c9ba96cdf8f522b9fe60f6fcba3d/last_with_shadow_Wed_Apr__8_17_01_46_-03_2020.png)
+## Eliminar rol
 
-Seleccionar uno de los roles listados permite inspeccionar qué recursos están incluidos en este rol, separados por producto.
+Para eliminar un rol, haz clic en el ícono de ⫶ en la fila del rol que deseas eliminar y a continuación en <i class="far fa-trash-alt"></i> `Eliminar`.
 
-<div class="alert alert-info">
-  Vea aquí todos los <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy">Roles de usuario predefinidos</a>.
+<div class="alert alert-warning">
+  <p>Al eliminar un rol, los usuarios asociados al mismo perderán el acceso a los <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recursos del License Manager</a> relacionados con él, a menos que tengan otros roles con los mismos permisos.</p>
 </div>
 
-![Nuevo rol salvo](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/377d5de0c9b4af5667a4e8f10c171ae0/last_with_shadow_Wed_Apr__8_17_06_18_-03_2020.png)
-
-El rol **Call center operator**, por ejemplo, contiene un recurso del producto *Catálogo* que le permite ejecutar operaciones en una tienda en nombre de un cliente y un recurso de *OMS* que permite verificar el status de un pedido.
-
-Para crear un rol personalizado, el administrador puede elegir la opción **Custom** del menú desplegable **Elegir rol.** Al hacer clic en el menú desplegable en **Elija un producto**, se listan todos los recursos asociados a cada producto.
-
-![Configurando producto](https://images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/8a2512bebc4fa0ac44731d6a2ecfac6b/last_with_shadow_Wed_Apr__8_17_11_58_-03_2020.png)
-
-Se puede añadir al rol tantos productos como se necesiten. Basta con hacer clic en el botón **Configure otro producto** al final de la lista de productos y recursos.
-
-![Configurar otro producto](https://images.ctfassets.net/alneenqid6w5/Dsc2k29SxUDKB8t6VXScn/6669a063adc5974cc1441e5764a69c41/last_with_shadow_Wed_Apr__8_17_12_07_-03_2020.png)
-
-Al terminar la configuración de los productos y recursos, el administrador puede elegir un nombre para el perfil en **Nombre del rol** si se trata de una configuración personalizada.
-
-![Nombre del rol](https://images.ctfassets.net/alneenqid6w5/gTuv92HFXKn4jklYX0Hzj/2478849865fe4e5041eb97b7d3dd5dce/last_with_shadow_Wed_Apr__8_17_17_02_-03_2020.png)
-
-<table>
-  <tr>
-    <td style="border-left: 4px solid #F71963;" bgcolor="#FFE6E6"> <b>¡Atención!</b> Es importante elegir nombres descriptivos para los roles de acceso, para dejar claro qué tipo de usuario debe tener ese acceso. Lo ideal sería indicar la posición en la empresa o la actividad dentro del producto.</td>
-  </tr>
-</table>
-
-Las buenas prácticas en la gestión de los roles de usuario aumentan la seguridad de una operación y refuerzan la atención de todos los involucrados en los datos sensibles de una tienda y de sus clientes. Recomendamos la creación de roles análogos a las estructuras jerárquicas de la organización administradora. De esta manera, cada uno es responsable de la información a la que puede acceder.
-
-También es posible añadir usuarios al rol, personalizado o predefinido, completando el correo electrónico del usuario que se incluirá en **Agregar usuarios a este rol**. Si el usuario no existe, se creará un nuevo usuario utilizando el correo electrónico como nombre también (el nombre y el correo electrónico serán iguales).
-
-![Usuarios](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/bfbc7ba812a8d8e306eb9adca5f53e31/last_with_shadow_Wed_Apr__8_17_25_47_-03_2020.png)
-
-Cuando haya terminado de configurar el rol, debe guardar el nuevo rol haciendo clic en el botón azul en la parte inferior de la página.
-
-![Guardar rol](https://images.ctfassets.net/alneenqid6w5/68NycUF3T52sg96R6HDIna/89a4b047d9eecbfb65c4078e16adaa5a/last_with_shadow_Wed_Apr__8_17_32_59_-03_2020.png)
-
-Una vez creado, el nuevo rol se listará junto con los otros roles de usuario. Para verlo, vaya a **Configuraciones de la cuenta > Gestión de la cuenta > Roles de usuario** en el menú lateral del Admin.
-
-![Nueva lista roles de usuario](https://images.ctfassets.net/alneenqid6w5/3uQ5SvsqjpFCSJimcg9naY/845ea841f71c1d74d2467cc782fd935e/last_with_shadow_Wed_Apr__8_17_43_02_-03_2020.png)
+## Más información
 
+* [Control de acceso](https://help.vtex.com/es/tutorial/control-de-acceso--4rM3gyiWqtkim4Q8hOvLTC)
+* [Crear rol](https://help.vtex.com/es/tutorial/crear-nuevo-rol--qGtNQpKSSAduX94l2WZBW)
diff --git a/docs/tutorials/es/rounding-rules.md b/docs/tutorials/es/rounding-rules.md
index a1f342e1a..aeeaabf63 100644
--- a/docs/tutorials/es/rounding-rules.md
+++ b/docs/tutorials/es/rounding-rules.md
@@ -60,16 +60,16 @@ Debajo se muestran ejemplos de los flujos de inclusión, edición y exclusión d
 
 *Flujo de creación de una regla*
 
-![config-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/7wgWLaW6Dkkbzv5TwcRmkB/e03d3e914bc8d0caa79b9f01cceabf6a/config-arrendodamento-ES.gif)
+![config-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/7wgWLaW6Dkkbzv5TwcRmkB/e03d3e914bc8d0caa79b9f01cceabf6a/config-arrendodamento-ES.gif)
 
 *Flujo de alteración de una regla*
 
-![editar-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/pISHBzFVs6U43naiHWtBl/2565b7cbb0c125bd06d7f794fb143e45/editar-arrendodamento-ES.gif)
+![editar-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/pISHBzFVs6U43naiHWtBl/2565b7cbb0c125bd06d7f794fb143e45/editar-arrendodamento-ES.gif)
 
 *Flujo de exclusión de una regla*
 
-![deletar-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/5r2727EBpFCZTdCWf37pX5/94da5c889815498eba18317d8917b696/deletar-arrendodamento-ES.gif)
+![deletar-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/5r2727EBpFCZTdCWf37pX5/94da5c889815498eba18317d8917b696/deletar-arrendodamento-ES.gif)
 
 *Simulación de precio para una regla*
 
-![teste-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/7reSTtuZZ5YNJOhynvGhFo/d8669c171fd5e5fd0d2e75eb49582fff/teste-arrendodamento-ES.gif)
+![teste-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/7reSTtuZZ5YNJOhynvGhFo/d8669c171fd5e5fd0d2e75eb49582fff/teste-arrendodamento-ES.gif)
diff --git a/docs/tutorials/es/sales-app-sales-performance.md b/docs/tutorials/es/sales-app-sales-performance.md
index 4e321b93b..61ffa0584 100644
--- a/docs/tutorials/es/sales-app-sales-performance.md
+++ b/docs/tutorials/es/sales-app-sales-performance.md
@@ -23,7 +23,7 @@ Puedes acceder a las métricas de ventas de tu tienda que indican el desempeño
 2. Haz clic en el botón <i class="fas fa-bars"></i>.
 3. Después, en **Desempeño de ventas**.
 
-![Sales Performance (Store)](https://images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/befba785d99d38ac7ae16e4a045ab32a/analytics_en.png)
+![Sales Performance (Store)](//images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/befba785d99d38ac7ae16e4a045ab32a/analytics_en.png)
 
 En esa página, tendrás acceso a las siguientes métricas:
 
@@ -37,7 +37,7 @@ En esa página, tendrás acceso a las siguientes métricas:
 
 Para acceder a las métricas específicas de un vendedor, sigue los pasos a continuación:
 
-![Ventas de Bruna - VTEX Sales App](https://images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/0742350774cffb176c09e1597d24270d/Ventas_de_bruna_-.png)
+![Ventas de Bruna - VTEX Sales App](//images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/0742350774cffb176c09e1597d24270d/Ventas_de_bruna_-.png)
 
 1. Haz clic en el ícono <i class="far fa-id-badge"></i>.
 2. Selecciona el perfil de un vendedor e introduce la contraseña.
diff --git a/docs/tutorials/es/sales-associate-code-field-at-checkout.md b/docs/tutorials/es/sales-associate-code-field-at-checkout.md
new file mode 100644
index 000000000..3363b31ff
--- /dev/null
+++ b/docs/tutorials/es/sales-associate-code-field-at-checkout.md
@@ -0,0 +1,96 @@
+---
+title: 'Campo Código de vendedor en el Checkout'
+id: 6hiRCXt5Cz250o7hBnN2Tp
+status: PUBLISHED
+createdAt: 2023-06-20T12:18:18.542Z
+updatedAt: 2023-06-20T21:50:57.120Z
+publishedAt: 2023-06-20T21:50:57.120Z
+firstPublishedAt: 2023-06-20T15:04:21.346Z
+contentType: tutorial
+productTeam: Shopping
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: campo-codigo-de-vendedor-en-el-checkout
+locale: es
+legacySlug: campo-codigo-de-vendedor-en-el-checkout
+subcategory: 
+---
+
+En VTEX, puedes crear un campo para registrar el código de vendedor en el Checkout. Este campo te permite:
+- Asociar un determinado pedido de compra a un vendedor.
+- Ofrecer descuentos exclusivos al consumidor.
+- Gestionar el desempeño de tus vendedores, extrayendo datos como número de ventas o ticket promedio por vendedor y ranking para comisiones de ventas, entre otros.
+
+<div class="alert alert-warning">
+  El campo <b>Código de vendedor</b> no sustituye el campo <b>Cupón de descuento</b> (que es nativo en la plataforma VTEX). Al realizar la configuración que se describe en este artículo, puedes utilizar los dos para ofrecer descuentos.
+</div>
+
+Para crear el campo y agregarlo a la pantalla del Checkout de tu tienda, debes completar tres pasos:
+
+1. [Crear una nueva entidad de datos](#crear-una-nueva-entidad-de-datos)
+2. [Crear una promoción Código de vendedor](#crear-una-promocion-codigo-de-vendedor)
+3. [Personalizar la pantalla del Checkout](#personalizar-la-pantalla-del-checkout)
+
+## Crear una nueva entidad de datos
+
+El campo **Código de Vendedor** se debe registrar en [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) como una nueva entidad. Para crear la entidad de datos, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Master Data** o escribe **Master Data** en la barra de búsqueda en la parte superior de la página.
+2. Crea una nueva [entidad de datos](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar) con el nombre *codigovendedor*.
+3. Dentro da nova entidade de dados, crie os seguintes campos:
+    - **Código do vendedor**: código con un valor máximo de 10 caracteres (tipo Varchar10).
+    - **Email**: dirección de email del vendedor (tipo Email).
+    - **Nombre**: nombre del vendedor (tipo Text).
+    - **Status**: indica si el vendedor está activo o inactivo (tipo Boolean).
+    - **Tienda**: identificación de la tienda en la que el vendedor trabaja (tipo Text).
+    - Otros campos (según sea necesario).
+
+<blockquote><ui>4. Registra la información de cada vendedor en los campos creados en el paso anterior.</ui>
+
+<blockquote><ui>5. Crea un <a href="https://help.vtex.com/es/tutorial/creando-formulario-en-master-data--tutorials_1047">formulario</a> para acceder a la información de la nueva entidad <i>codigovendedor</i> a través de la interfaz de Master Data.</ui>
+
+## Crear una promoción Código de vendedor
+
+Después de crear la entidad *codigovendedor*, debes asociarla a una promoción. Para crear una promoción, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Promociones > Promociones**, o escribe **Promociones** en la barra de búsqueda en la parte superior de la página.
+2. Crea una nueva [promoción regular](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N). Rellena la información de **Resumen de la promoción** y **¿A qué ítems se aplicará esta promoción?** según lo desees.
+
+<div class="alert alert-info">
+ Si deseas utilizar el campo Código de vendedor para ofrecer un descuento en el valor de la compra, rellena la información de <b>¿Cuál es el tipo y valor del descuento?</b>.
+</div>
+
+<blockquote><ui>3. En <b>¿Cuáles son las condiciones para que la promoción sea válida?</b>, haz clic en la opción <b>utm_campaign</b> e ingresa <i>codigovendedor</i> en el campo.</ui>
+
+![utm campaign codigovendedor](//images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/5fac14ad4842791589bab32d955f480f/UTM_Campaign_codigovendedor.PNG)
+
+<blockquote><ui>4. En <b>Restricciones y limitaciones de uso</b>, agrega las demás restricciones disponibles, si así lo deseas. Selecciona la opción <b>Aplicar con otras promociones</b>.</ui>
+
+<blockquote><ui>5. Haz clic en <b>Guardar</b>.</ui>
+
+## Personalizar la pantalla del Checkout
+
+El último paso es configurar la pantalla del Checkout para permitir que se muestre el campo **Código de vendedor**.
+
+Para realizar la personalización, debes ponerte en contacto con la agencia partner responsable de la creación de tu tienda y solicitar que agreguen el nuevo campo para que el cliente pueda añadir el código del vendedor y se muestre el nombre.
+
+También debes completar los siguientes pasos:
+
+1. Al simular una compra e ingresar el código del vendedor en la pantalla del Checkout, asegúrate de que la llamada GET [Search Documents](https://developers.vtex.com/docs/api-reference/master-data-api-v2#get-/api/dataentities/-dataEntityName-/search) realice la búsqueda en la entidad `codigovendedor` y devuelva toda la información registrada de dicho vendedor. Ejemplo de llamada: https://{accountName}.{environment}.com.br/api/dataentities/codigovendedor/search?codigovendedor=12345.
+
+<div class="alert alert-warning">
+  El campo <b>status</b> debe devolver el valor <b>true</b> para indicar que el código del vendedor es válido.
+</div>
+
+<blockquote><ui>2. Realiza la llamada POST <a href="https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm">Update orderForm configuration</a> para incluir la siguiente información en el <a href="https://developers.vtex.com/docs/guides/orderform-fields">orderForm</a> de tu tienda</ui>:
+
+<blockquote><blockquote>- <b>marketingData</b>: ingresa <i>"codigovendedor"</i> en <i>"utmCampaign"</i>. Si no se describe esta información, la promoción (código de vendedor) no se aplicará al carrito y no se mostrará el campo.
+
+  <blockquote><blockquote>- <b>openTextField</b> (opcional): ingresa observaciones o comentarios como, por ejemplo, información para filtros de comisiones.
+
+<div class="alert alert-warning">
+  En la pantalla del Checkout solo debe aparecer el nombre del vendedor.
+</div>
+
+Después de ejecutar todos los pasos descritos anteriormente, el campo **Código de vendedor** estará disponible en la pantalla del Checkout.
+
+![Código de vendedor](//images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/8f7156a46e01ad6715f446aad5e2bd7e/Checkout_UI_-_ES_2.png)
diff --git a/docs/tutorials/es/sales-associates-instore-beta.md b/docs/tutorials/es/sales-associates-instore-beta.md
index 56bca92b5..b01ec5640 100644
--- a/docs/tutorials/es/sales-associates-instore-beta.md
+++ b/docs/tutorials/es/sales-associates-instore-beta.md
@@ -31,7 +31,7 @@ Esta página te permite gestionar tus vendedores a través de las siguientes acc
 * [Editar](#editar-vendedor)
 * [Eliminar](#eliminar-vendedor)
 
-![vendedores-es](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
+![vendedores-es](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
 
 La página contiene la siguiente información:
 
@@ -54,7 +54,7 @@ Puedes crear un vendedor siguiendo los pasos a continuación:
 
 Después de registrado, el vendedor recibirá un email de confirmación y se le redirigirá a la opción de inicio de sesión del vendedor en la aplicación inStore.
 
-![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+![email-vendedor-pt](//images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
 <div class ="alert alert-warning">
 <p>Los vendedores registrados en inStore no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.</p> 
diff --git a/docs/tutorials/es/sales-performance.md b/docs/tutorials/es/sales-performance.md
index 88e71d933..00d51d64f 100644
--- a/docs/tutorials/es/sales-performance.md
+++ b/docs/tutorials/es/sales-performance.md
@@ -3,8 +3,8 @@ title: 'Desempeño de Ventas'
 id: 3DMube0sEsK9vPcRYGas72
 status: PUBLISHED
 createdAt: 2021-10-19T12:49:42.165Z
-updatedAt: 2022-12-20T14:05:11.128Z
-publishedAt: 2022-12-20T14:05:11.128Z
+updatedAt: 2023-11-09T19:56:56.074Z
+publishedAt: 2023-11-09T19:56:56.074Z
 firstPublishedAt: 2021-10-19T12:55:27.227Z
 contentType: tutorial
 productTeam: Others
@@ -26,7 +26,7 @@ Para acceder a la pagina, en __Dashboards__, haz clic en __Desempeño de Ventas_
 
 Puedes personalizar la visualización de los datos del gráfico y de la lista filtrando por periodo, dimensiones y métricas. 
 
-![Sales Perf Dash ES](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
+![Sales Perf Dash ES](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
 
 ## Datos 
 Los datos de la página proceden del [sistema de Gestión de pedidos](https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa) de VTEX. El Desempeño de Ventas es una solución analítica, que utiliza heurística y fórmulas creadas a partir de nuestra experiencia, llevando a nuestros clientes de ecommerce al siguiente nivel para calcular sus métricas. La página no debe utilizarse como un sustituto de los datos del OMS, sino como una herramienta de análisis y de insights de negocio.
@@ -35,7 +35,9 @@ Para asegurarte de que tienes acceso tanto a los últimos datos actualizados com
 
 Estos grupos también son procesados por sistemas diferentes, lo que puede provocar una diferencia entre los datos del OMS y los del Desempeño de las Ventas, aunque nuestro objetivo es presentar una divergencia máxima del 3%.
 
+<div class ="alert alert-warning">
 Por ejemplo, puede que haya diferencias entre las métricas de ingresos y ticket promedio registradas en el OMS y Desempeño de Ventas. Esto se debe a que Desempeño de Ventas considera el valor de los ítems, mientras que el OMS también toma en cuenta descuentos, valor de envío, impuestos y promociones en el pedido, lo que puede aumentar o disminuir el valor final.
+</div>
 
 ## Periodo
 
@@ -151,7 +153,7 @@ Además de aplicar filtros, también puedes realizar las acciones a continuació
 
 ## Vistas
 
-![Sales perf update ES](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
+![Sales perf update ES](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
 
 El *dashboard* Desempeño de Ventas se puede personalizar aplicando diferentes filtros y seleccionando las métricas que aparecerán en el gráfico y la lista. Para facilitar la exploración diaria de los datos, hemos creado vistas que registran los filtros y las métricas aplicadas en la página para tu visualización directa. Puedes guardar, editar y compartir las diferentes vistas del dashboard. La página viene con las siguientes vistas configuradas por defecto:
 
diff --git a/docs/tutorials/es/scheduled-delivery.md b/docs/tutorials/es/scheduled-delivery.md
index 7344fdf90..d4d644b3c 100644
--- a/docs/tutorials/es/scheduled-delivery.md
+++ b/docs/tutorials/es/scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'Entrega programada'
 id: 22g3HAVCGLFiU7xugShOBi
 status: PUBLISHED
 createdAt: 2021-04-19T13:26:44.564Z
-updatedAt: 2021-10-27T16:49:43.778Z
-publishedAt: 2021-10-27T16:49:43.778Z
+updatedAt: 2024-03-25T19:12:45.519Z
+publishedAt: 2024-03-25T19:12:45.519Z
 firstPublishedAt: 2021-05-24T17:01:23.885Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,13 +15,16 @@ legacySlug: entrega-programada, como-se-maneja-la-entrega-programada
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
-
 La funcionalidad de entrega programada permite que defina periodos de entrega para que el consumidor pueda elegir el mejor día y horario para recibir los productos adquiridos.
 
 Los periodos de entrega que están disponibles para los clientes se denominan ventanas de entrega y están directamente relacionados con las políticas de envío de su tienda. Es decir, para ofrecer el servicio de entregas programadas, debe considerar si la política de envío lo incluye.
 
 En caso de que la política de envío ofrezca el servicio, puede habilitar la entrega programada configurando las ventanas de entrega y estableciendo la capacidad de realización de entregas para cada ventana, si así lo desea.
 
+<div class="alert alert-warning">
+Para que la <a href="https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> y la <a href="https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidad de entrega</a> funcionen correctamente, debes tener en cuenta que:<p><ul><li>La suma de {<a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID de la política de envío} no puede exceder los 60 caracteres.</li><li>No se debe utilizar espacio en el ID de la <a href="https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">política de envío</a>.</li></ul></p>
+</div>
+
 La entrega programada se habilita a través del campo Entrega programada que se muestra en la pantalla de creación o edición de [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140). 
 
 Una vez que habilite la funcionalidad __Entrega programada__ en Política de envío, puede configurar los campos que determinarán cómo esta funcionará. Estos campos definen el [tiempo máximo de entrega](#tiempo-maximo-de-entrega), el [periodo de entrega](#periodo-de-entrega) y el [límite de la capacidad de entrega](#capacidad-de-entrega).
diff --git a/docs/tutorials/es/scheduling-features-for-special-events.md b/docs/tutorials/es/scheduling-features-for-special-events.md
index e074f9f4d..5ea4582ed 100644
--- a/docs/tutorials/es/scheduling-features-for-special-events.md
+++ b/docs/tutorials/es/scheduling-features-for-special-events.md
@@ -70,7 +70,7 @@ Para programar un contenido, siga los pasos a continuación:
 3. Utilice el campo de la URL en la esquina superior para navegar a la página que muestra el bloque cuyo contenido será sobrescrito.
 4. Seleccione el bloque para el que desea crear un nuevo contenido. Puede seleccionarlo en lista de la derecha o en la interfaz:
 
-![seta-interface](https://images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
+![seta-interface](//images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
 
 5. Haga clic en `Configuración` en la esquina superior derecha.
 6. Haga clic en el botón `Nuevo contenido`.
diff --git a/docs/tutorials/es/search-behavior.md b/docs/tutorials/es/search-behavior.md
new file mode 100644
index 000000000..db2a47cc4
--- /dev/null
+++ b/docs/tutorials/es/search-behavior.md
@@ -0,0 +1,134 @@
+---
+title: 'Comportamiento de búsqueda'
+id: B9o3JbV6utAinBJ1ETujs
+status: PUBLISHED
+createdAt: 2024-06-27T17:30:43.356Z
+updatedAt: 2024-06-27T17:33:21.153Z
+publishedAt: 2024-06-27T17:33:21.153Z
+firstPublishedAt: 2024-06-27T17:33:21.153Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: comportamiento-de-busqueda
+locale: es
+legacySlug: comportamiento-de-busqueda
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+El motor de búsqueda es el centro de la inteligencia de VTEX Intelligent Search. Interpreta el término buscado y muestra la lista de productos filtrada y ordenada. Esta herramienta permite una búsqueda más objetiva, a través de la indexación y el tratamiento de los datos del catálogo.
+
+Esta es una funcionalidad predeterminada de VTEX Intelligent Search y cubre a la mayoría de los escenarios. Sin embargo, el motor de búsqueda también presenta algunos ajustes para perfeccionar el resultado de la búsqueda. En esta guía describimos:
+
+* [Comportamiento predeterminado de la búsqueda](#comportamiento-predeterminado-de-la-busqueda)
+* [Configuración del comportamiento de la búsqueda](#configuracion-del-comportamiento-de-la-busqueda)
+* [Formas de búsqueda alternativas](#formas-de-busqueda-alternativas)
+
+## Comportamiento predeterminado de la búsqueda
+
+A continuación se describe el comportamiento predeterminado de Intelligent Search.
+
+### Autocorrección
+
+El usuario puede cometer errores ortográficos al realizar una búsqueda. La herramienta interpreta los errores y muestra como resultados productos que se aproximen a la búsqueda realizada.
+
+Para lograrlo, el motor de búsqueda intenta corregir las palabras ingresadas por el usuario de acuerdo con los ítems registrados en el catálogo. Para cada término de búsqueda se permite una cantidad específica de caracteres erróneos. Esta cantidad de errores aceptados se denomina _fuzzy_.
+
+El _fuzzy_ varía según el tamaño del término buscado. De forma predeterminada, si el término tiene de 3 a 5 caracteres, se aplica un _fuzzy_ de 1, es decir, se permite 1 carácter erróneo. A los términos de 6 caracteres o más, se aplica un _fuzzy_ de 2.
+
+Los errores previstos para los que se considera *fuzzy* = 1 son:
+
+* Insertar 1 carácter demás.
+* Remover 1 carácter.
+* Cambiar 1 carácter.
+* Intercambiar 2 caracteres que estén una al lado del otro.
+
+Ejemplo: un cliente desea buscar el término `bola`. Siguiendo la configuración predeterminada (*fuzzy* = 1 para términos de 3 a 5 caracteres), el motor de búsqueda muestra los resultados de `bola` para cualquier búsqueda que contenga los errores aceptados según se muestra a continuación:
+
+* `bolla` (insertar 1 carácter de más)
+* `boa` (remover 1 carácter)
+* `bora` (cambiar 1 carácter)
+* `obla` (intercambiar 2 caracteres que estén uno al lado del otro)
+
+<div class ="alert alert-info">
+	<p>El <em>fuzzy</em> no considera los espacios en blanco. Esto quiere decir que, por ejemplo, <code>base ball</code> no se corregiría a <code>baseball</code>. Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinónimos</a> en estos casos.</p>
+</div>
+
+### Resultado mínimo
+
+La cantidad mínima de resultados mostrados para cualquier búsqueda realizada es 1. Si no se encuentra el número mínimo de resultados, se aplica [autocorrección](#autocorreccion).
+
+En las búsquedas que contienen varios términos, se aplica la siguiente lógica:
+
+Si no se devuelve la cantidad mínima de resultados con la autocorrección inicial, la búsqueda comienza a incluir resultados más amplios que contengan cualquiera de los términos buscados. Por ejemplo, cuando un usuario busca “zapatilla nike” pero el catálogo no tiene ningún producto con ese nombre, la búsqueda puede mostrar como resultado un producto que contenga solo “zapatilla” en el nombre.
+Si la búsqueda más amplia no devuelve la cantidad de resultados mínima, se repetirá la autocorrección nuevamente en cada uno de los términos.
+
+<div class= "alert alert-warning">
+<p>Las búsquedas que contienen varios términos son más eficientes cuando el cliente ordena los resultados por relevancia, ya que pueden devolver un número mayor de resultados más allá del contexto de búsqueda inicial. En el orden por relevancia también pueden priorizarse ítems relacionados con cada término. Por otro lado, cuando se aplican otros criterios, como precio o más vendidos, el orden de los resultados depende de los valores numéricos y no necesariamente prioriza ítems que contienen más palabras.</p>
+</div>
+
+### Límite de paginación
+
+VTEX Intelligent Search limita los resultados de búsqueda a 50 páginas. Este límite incentiva el uso de filtros para hacer que la navegación sea más relevante y enfocada para el usuario.
+
+## Configuración del comportamiento de la búsqueda
+
+Hay un conjunto de ajustes que alteran la lista y el orden de los productos mostrados en el resultado de la búsqueda. En las siguientes secciones se presentan las principales definiciones que afectan el comportamiento de la búsqueda.
+
+### Definición de los campos de búsqueda
+
+Determina la información de producto que se puede buscar. A partir de la configuración, toda búsqueda realizada en la barra de búsqueda verifica el contenido de este campo para generar resultados de búsqueda. Consulta la tabla a continuación para saber qué información permite la realización de búsquedas de forma predeterminada y ver las otras opciones de configuración:
+
+| Información | Configuración |
+| - | - |
+| Nombre del producto, marca, ID de producto (`ProductID`), código de referencia del producto (`ProductRefID`), ID del SKU (`SKUID`), código de referencia del SKU (`SKURefID`) y EAN | Se pueden realizar búsquedas en estos datos de forma predeterminada en VTEX Intelligent Search. Para remover alguno de ellos, ponte en contacto con nuestro [Soporte](https://help.vtex.com/es/support). |
+| Especificaciones de producto y SKU | Para incluir las especificaciones deseadas como campos que se pueden buscar, debes configurar la opción __Especificaciones buscables__ en el Admin VTEX a través de __Configuración de la tienda__ > __Intelligent Search__ > __Configuración de la búsqueda__. <br /><br /> Por ejemplo, si una camisa no tiene el color en el nombre del producto o del SKU, de forma predeterminada, Intelligent Search no identifica ese atributo cuando se busque “camisa azul” y devolverá como resultado camisas de diferentes colores. Sin embargo, si la especificación de color se configura de manera que se pueden realizar búsquedas sobre la especificación de color, la búsqueda podrá devolver camisas azules en las primeras posiciones. <br /><br /> Para más detalles sobre la definición de especificaciones buscables, accede a la guía [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#configuracion-general). Puedes ver más información sobre especificaciones en [Especificaciones de producto y SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP). |
+| Código del fabricante (`ManufactureID`) | Ponte en contacto con nuestro [Soporte](https://help.vtex.com/es/support) para configurar la realización de búsquedas en este campo. |
+
+Ejemplo: se configuró que la especificación “color” se puede buscar y el producto está registrado con el nombre “Zapatilla Nike Total 90” y con el color “negro”. Si un cliente busca “Zapatilla Negra”, la herramienta devolverá productos que tengan el término “zapatilla” y el color “negra” en la parte superior del resultado de búsqueda.
+
+Se puede encontrar un producto realizando una búsqueda por caracteres especiales (`-` y `/`).
+
+<div class="alert alert-warning">
+	<p>La selección de los campos de búsqueda afecta las posibilidades de las <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">reglas de merchandising</a>, ya que solo se pueden utilizar los campos que permiten búsquedas para configurar reglas. Por ejemplo, al definir solo el campo <code>SKUID</code> para búsquedas, no se podrá promover un <code>ProductID</code> o un <code>ProductRefID</code> utilizando reglas de merchandising.</p>
+</div>
+
+### Definición y orden de los campos de filtro
+
+En todos los resultados de búsqueda se muestran filtros que el usuario puede seleccionar. De forma predeterminada, algunos filtros ya están predefinidos, pero es posible crearlos según la necesidad de la tienda. Otro aspecto personalizable es el orden de visualización. Ejemplo: en una lista de resultados de búsqueda puede incluir filtros como Precio, Categorías y Marca.
+
+### Configuración de relevancia
+
+La relevancia es la funcionalidad que define el orden de los productos en el resultado de búsqueda. Esta configuración permite asignar pesos y priorizar determinados criterios utilizados por el motor de búsqueda, como popularidad, fecha de lanzamiento del producto y participación en promociones. La relevancia de un producto está compuesta por la combinación de los pesos y prioridades definidos por cada administrador de la tienda.
+
+Ejemplo: un administrador de la tienda configuró que el criterio “promoción” tiene una mayor relevancia que otros criterios. Así, cuando un cliente busca “camiseta” en la búsqueda interna de la tienda, las camisetas incluidas en las promociones tienden a aparecer en primer lugar en los resultados, dependiendo del peso asignado a los demás criterios.
+
+Para obtener más información sobre cómo personalizar el orden de los resultados de acuerdo con las necesidades de tu tienda, consulta el artículo [Configuración de relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+<div class="alert alert-info">
+	<p>Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Si utilizas el comando <code>map=productClusterIds</code>, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con su propio criterio de relevancia. Si eliges utilizar <code>productClusterNames</code>, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search.</p>
+</div>
+
+## Formas alternativas de búsqueda
+
+Es posible buscar el ID de uno o varios artículos en la barra de búsqueda o añadiendo parámetros de consulta (*query*) a la URL de la tienda.
+
+### Coincidencia parcial
+
+Al ingresar únicamente los primeros dígitos exactos del ID del producto (`ProductID`), código de referencia del producto (`ProductRefID`), ID del SKU (`SKUID`), código de referencia del SKU (`SKURefID`) o EAN en la barra de búsqueda, Intelligent Search hará un match parcial con productos y SKU activos en la tienda, incluyéndolos en los resultados de la búsqueda.
+
+Por ejemplo, si el ID del producto es `123456789` y la búsqueda realizada es `123`, ese producto se mostrará entre los resultados; sin embargo, si la búsqueda es `234`, sin alguno de los primeros dígitos del ID, este producto no se mostrará.
+
+### URL
+
+Para buscar desde la URL de tu tienda, añade parámetros de búsqueda (_query_) al final de la URL de la tienda, respetando una de las siguientes estructuras:
+
+* Ejemplo de búsqueda de un ítem: `[dirección de la cuenta]/[tipo de id]:[id_1]?q=[tipo de id]&map=ft`
+* Ejemplo de búsqueda de lista: `[dirección de la cuenta]/[tipo de id]:[id_1];[id_2];[id_3]?q=[tipo de id]:[id_1];[id_2];[id_3]&map=ft`
+
+Los posibles tipos de valores para el campo “tipo de ID” son `product.id`, `sku.id`, `sku.ean`, `sku.reference` o `id` (ProductID, ProductRefID, SKUID, SKURefID y EAN). Cabe resaltar que todos los ID deben ser del mismo tipo.
+
+* **Búsqueda por ID de SKU:** `?q=sku.id:<id>` o `?q=sku:<id>`
+* **Búsqueda por EAN:** `?q=sku.ean:<id>`
+* **Búsqueda por ID de referencia:** `?q=sku.reference:<id>`
+* **Búsqueda por slug:** `?q=product.link:<link>`
+* **Búsqueda por ID de producto:** `?q=product:<id>` o `?q=product.id:<id>`
diff --git a/docs/tutorials/es/search-configuration.md b/docs/tutorials/es/search-configuration.md
new file mode 100644
index 000000000..dc414e742
--- /dev/null
+++ b/docs/tutorials/es/search-configuration.md
@@ -0,0 +1,52 @@
+---
+title: 'Configuración de la búsqueda'
+id: 1yNCDwz0k77ovSGqkTbZMv
+status: PUBLISHED
+createdAt: 2024-06-17T14:08:59.824Z
+updatedAt: 2024-06-17T14:10:20.364Z
+publishedAt: 2024-06-17T14:10:20.364Z
+firstPublishedAt: 2024-06-17T14:10:20.364Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configuracion-de-la-busqueda
+locale: es
+legacySlug: configuracion-de-la-busqueda
+subcategory: 1EmKjP83dy0RWD9GzZkYsG
+---
+
+La página **Configuración de la búsqueda** comprende la configuración global de VTEX Intelligent Search. Para acceder, en el VTEX Admin ve a **Configuración de la tienda > Intelligent Search > Configuración de la búsqueda**. Esta consta de dos secciones: [Configuración general](#configuracion-general) y [Configuración de filtros](#configuracion-de-filtros).
+
+## Configuración general
+
+La configuración general presenta las siguientes opciones relativas a [las especificaciones de productos y SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP):
+
+* **Utiliza las especificaciones de SKU para mostrar productos individuales en los resultados de búsqueda**: establece las características que determinarán el orden de los SKU en los resultados de búsqueda.
+
+    Supongamos que tienes un producto con los colores rojo y azul como SKU. Si seleccionas el atributo "color" en este campo, el resultado de la búsqueda devolverá dos productos (uno azul y otro rojo) en lugar de uno solo.
+
+    Para agregar una especificación, haz clic en la barra del menú desplegable y selecciona la especificación deseada.
+
+    Consulta la guía [Separar SKUs por especificación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE) para obtener más detalles sobre esta configuración. 
+
+* **Especificaciones buscables:** determina las especificaciones de producto que pueden ser buscadas por el motor de búsqueda.
+
+    Por ejemplo, si una camisa no contiene un color en el nombre del producto o en el SKU, de manera predeterminada, Intelligent Search no identificará este atributo en una búsqueda de "camisa azul", lo que dará como resultado camisas de diferentes colores. Sin embargo, si la especificación de color está configurada como buscable, la búsqueda puede hacer que aparezcan camisas azules en las primeras posiciones.
+
+## Configuración de filtros
+
+La configuración de facetas presenta ajustes relacionados con las [facetas](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) mostradas a los clientes de tu tienda durante la búsqueda:
+
+![Configuracion del filtro](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
+
+* **Orden de las facetas:** orden en el que se mostrarán las facetas en la tienda. Si no hay ninguna faceta seleccionada en la sección, el orden predeterminado es alfabético.
+
+    Para agregar una faceta, haz clic en `Agregar`, selecciona la faceta deseada y haz clic en `Guardar`.
+
+    Puedes cambiar la clasificación arrastrando el ícono de puntos <i class="fas fa-grip-vertical"></i> de cada faceta a la posición deseada.
+
+    Para eliminar una faceta, haz clic en el ícono de la papelera <i class="fas fa-trash-alt"></i>.
+
+* **Ocultar facetas:** selección que permite que determinadas facetas no se muestren en la tienda. Para ocultar una faceta, haz clic en el menú desplegable, y a continuación en el nombre de la faceta. 
+
+    Para volver a mostrar una faceta, haz clic en la X situada junto a su nombre. Si deseas volver a mostrar todas las facetas anteriormente ocultas, haz clic en la X situada a la derecha del campo.
diff --git a/docs/tutorials/es/search-navigator-control.md b/docs/tutorials/es/search-navigator-control.md
index 23bfa0cfa..29ad86568 100644
--- a/docs/tutorials/es/search-navigator-control.md
+++ b/docs/tutorials/es/search-navigator-control.md
@@ -52,7 +52,7 @@ Para que una categoría sea exhibida por acción de ese control, debe estar con
 
 Este flag está en la pantalla de registro de la categoría.
 
-![Cómo funciona el control Search Navigator ES 2](https://images.ctfassets.net/alneenqid6w5/5Qg0LcxqSc6e2UuEo2M0me/457a81b3196c932f1d3f157582598599/2018-10-23_22-41-18_ES_2.png)
+![Cómo funciona el control Search Navigator ES 2](//images.ctfassets.net/alneenqid6w5/5Qg0LcxqSc6e2UuEo2M0me/457a81b3196c932f1d3f157582598599/2018-10-23_22-41-18_ES_2.png)
 
 <div class="alert alert-info">
   <strong>Importante</strong>: El control  <code>&lt;vtex.cmc:searchNavigator/&gt;</code> exhibe, por estándar, apenas la categoría base (primer nivel) y la subcategoría más específica (último nivel) dentro del contexto actual. Se omiten las divisiones intermedias en el árbol de categorías. Además, el control solo funciona en los primeros tres niveles, que son tradicionalmente Departamento, Categoría y Subcategoría. Si su  <a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">arquitectura de catálogo</a> contiene subdivisiones más allá del tercer nivel, no se mostrarán con el control nativo.
@@ -85,7 +85,7 @@ Para que un campo de producto o un campo de SKU se muestre en el menú por el co
 
 Ambos se encuentran en la pantalla de registro del campo.
 
-![Cómo funciona el control Search Navigator ES 3](https://images.ctfassets.net/alneenqid6w5/25TT9lYqHamqoaS6iIeQKk/a5bf18a4d4779df84dc68a40742fd55e/2018-10-23_2243_ES_3.png)
+![Cómo funciona el control Search Navigator ES 3](//images.ctfassets.net/alneenqid6w5/25TT9lYqHamqoaS6iIeQKk/a5bf18a4d4779df84dc68a40742fd55e/2018-10-23_2243_ES_3.png)
 
 ## Rangos de precio
 
diff --git a/docs/tutorials/es/searching-for-old-orders.md b/docs/tutorials/es/searching-for-old-orders.md
index a289c1566..8aa2cf5fb 100644
--- a/docs/tutorials/es/searching-for-old-orders.md
+++ b/docs/tutorials/es/searching-for-old-orders.md
@@ -18,7 +18,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 Para buscar sus pedidos antiguos, siga los pasos a continuación:
 1. En el menú lateral del admin, haga clic en __Gestión de pedidos__.
 2. Haga clic en __Todos los pedidos__.
-3. Haga clic en el botón de filtro ![filter](https://images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png).
+3. Haga clic en el botón de filtro ![filter](//images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png).
 4. Escoja un filtro *por periodos*: __Fecha de factura__, __Fecha de pedido__, __Fecha de autorización__ o **Fecha de entrega**.
 5. En el filtro escogido, haga clic en el __ícono de calendario__, al lado del texto __Todas las fechas__.
 6. Escoja una fecha/hora inicial y una fecha/hora final. 
diff --git a/docs/tutorials/es/searching-for-transactions-on-payments.md b/docs/tutorials/es/searching-for-transactions-on-payments.md
index 687ed0e6a..10bb2b81a 100644
--- a/docs/tutorials/es/searching-for-transactions-on-payments.md
+++ b/docs/tutorials/es/searching-for-transactions-on-payments.md
@@ -35,13 +35,13 @@ Para volver a la lista original de las transacciones, basta apagar el valor ante
 
 Al hacer clic en una solicitud en el Gestión de Pedidos, usted va a la página que trae un resumen sobre él. Las principales informaciones están ahí, pero usted puede ver aún más detalles si hace clic en el enlace _Ver detalles de la transacción_:
 
-![Link transação OMS (ES)](https://images.ctfassets.net/alneenqid6w5/4lCG7cxc8MacMYQgmecqG6/33669bc2490b6732d50b1e9769129c33/Link_transa____o_OMS__ES_.png)
+![Link transação OMS (ES)](//images.ctfassets.net/alneenqid6w5/4lCG7cxc8MacMYQgmecqG6/33669bc2490b6732d50b1e9769129c33/Link_transa____o_OMS__ES_.png)
 
 ## TID del Pago e ID del Pago
 
 La búsqueda utilizando esos códigos necesariamente necesita contener todos los dígitos, o su búsqueda regresará vacía. Vea abajo como encontrarlo:
 
-![Códigos ES](https://images.ctfassets.net/alneenqid6w5/X1c6jZ4yomYGoE8U4o86u/d68575f5fa61a6b38517920f247cc460/C__digos_ES.png)
+![Códigos ES](//images.ctfassets.net/alneenqid6w5/X1c6jZ4yomYGoE8U4o86u/d68575f5fa61a6b38517920f247cc460/C__digos_ES.png)
 
 Estos valores, dentro del detalle de la transacción representarán la comunicación junto al respectivo conector. En los Eventos de la transacción será posible validar cada contacto hecho utilizando estos como identificador.
 
diff --git a/docs/tutorials/es/security-certificate-ssl.md b/docs/tutorials/es/security-certificate-ssl.md
new file mode 100644
index 000000000..756340c4d
--- /dev/null
+++ b/docs/tutorials/es/security-certificate-ssl.md
@@ -0,0 +1,26 @@
+---
+title: 'Certificado de seguridad (SSL)'
+id: tutorials_1308
+status: PUBLISHED
+createdAt: 2017-04-27T21:56:41.946Z
+updatedAt: 2023-11-16T17:44:04.092Z
+publishedAt: 2023-11-16T17:44:04.092Z
+firstPublishedAt: 2017-04-27T23:03:50.121Z
+contentType: tutorial
+productTeam: Identity
+author: authors_84
+slug: certificado-de-seguridad-ssl
+locale: es
+legacySlug: como-contratar-el-certificado-de-seguridad
+subcategory: 2TNXiKzLZOPxjMTyGiEeJu
+---
+
+El SSL (Secure Socket Layer) es un protocolo desarrollado para elevar el nivel de seguridad de los dados transmitidos en la internet. Las conexiones por SSL son indicados para envío de informaciones como números de tarjetas de crédito, contraseñas y cualquier otra información confidencial vía internet.
+
+Siempre que tu accedes una página segura, que sea protegida por un certificado SSL, es presentada una “clave” o un “candado” en la barra de estado para indicar la comunicación segura. Los certificados tradicionales exigen que tu clic en la clave o candado para poder acceder a informaciones del titular del certificado SSL.
+
+No es necesario solicitar la compra de un certificado SSL. VTEX genera un certificado SSL para tu tienda y garantiza su renovación automática. El certificado se emite a través de Let's Encrypt y su creación es responsabilidad de VTEX en [el momento del Go-Live de la tienda](https://help.vtex.com/es/tutorial/configurando-el-apuntamiento-del-dns-para-vtex--tutorials_4280).
+
+<div class="alert alert-warning">
+<p>No recomendamos instalar otros certificados. No obstante, si es necesario, póngase en contacto con nuestro <a href="https://help.vtex.com/es/support">soporte</a>.</p>
+</div>
diff --git a/docs/tutorials/es/security-education-and-awareness.md b/docs/tutorials/es/security-education-and-awareness.md
index e559bfb19..4b6bc06bd 100644
--- a/docs/tutorials/es/security-education-and-awareness.md
+++ b/docs/tutorials/es/security-education-and-awareness.md
@@ -3,7 +3,7 @@ title: 'Educación y concienciación sobre seguridad'
 id: 5t6HaGHiHFVrCIvePJKkV6
 status: DRAFT
 createdAt: 2022-05-26T13:50:41.046Z
-updatedAt: 2022-08-18T20:43:54.577Z
+updatedAt: 2023-07-19T23:57:15.726Z
 publishedAt: 
 firstPublishedAt: 
 contentType: tutorial
@@ -15,4 +15,4 @@ legacySlug: educacion-y-concienciacion-sobre-seguridad
 subcategory: 
 ---
 
-
+test
diff --git a/docs/tutorials/es/security-monitor.md b/docs/tutorials/es/security-monitor.md
new file mode 100644
index 000000000..298e85b54
--- /dev/null
+++ b/docs/tutorials/es/security-monitor.md
@@ -0,0 +1,131 @@
+---
+title: 'Security Monitor'
+id: 5LOVNLrrtmgSj99pM1NS4x
+status: PUBLISHED
+createdAt: 2024-04-25T00:42:30.944Z
+updatedAt: 2024-04-25T03:01:13.448Z
+publishedAt: 2024-04-25T03:01:13.448Z
+firstPublishedAt: 2024-04-25T02:41:44.798Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: security-monitor
+locale: es
+legacySlug: security-monitor
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad es parte de <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>.  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+Security Monitor es un dashboard que ayuda a los retailers a identificar y gestionar riesgos potenciales en su entorno en tiempo real. La herramienta identifica y notifica por email a los retailers sobre riesgos relacionados con la configuración y el comportamiento de los usuarios administrativos, lo que permite tomar medidas preventivas contra las vulnerabilidades de seguridad.
+
+Para acceder al dashboard sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Dashboards**, o ingresa **Dashboards** en la barra de búsqueda.
+2. En **Security Monitor**, haz clic en **Security Monitor Dashboard**.
+
+![1-security-monitor-es](//images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/fb2b0e5a7758c15f7a85a28d6092e119/1-security-monitor-es__2_.png)
+
+Security Monitor presenta los resultados en tres pestañas, divididas por status:
+
+* [Abiertos](#abiertos)
+* [Pospuestos](#pospuestos)
+* [Cerrados](#cerrados)
+
+En todas las pestañas pueden realizarse las siguientes acciones:
+
+* [Buscar hallazgos](#buscar-hallazgos)
+* [Filtrar hallazgos por tipo](#filtrar-hallazgos-por-tipo)
+* [Editar configuración de las notificaciones](#editar-configuracion-de-las-notificaciones)
+
+Consulta a continuación información específica sobre la información disponible en cada pestaña y las acciones relacionadas.
+
+## Abiertos
+
+La pestaña **Abiertos** muestra las amenazas identificadas por Security Monitor que aún no han sido gestionadas o pospuestas.
+
+La barra superior muestra el número total de hallazgos y el número de amenazas por nivel de gravedad (alto, medio o bajo).
+
+![2-findings-es](//images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/630a7a558c2c57d07e6b8b68de359a4b/2-findings-es.png)
+
+La pestaña muestra la lista completa de hallazgos abiertos en una tabla, del más reciente al más antiguo: 
+
+| Columnas | Descripción |
+| --- | --- |
+| Hallazgo | Email de usuario o clave de la aplicación relacionado con el hallazgo. |
+| Tipo | Tipo de hallazgo detectado:<br/><ul><li><strong>Claves de aplicación antiguas:</strong> <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">claves de aplicación</a> que se crearon hace más de 6 meses.</li><li><strong>Excesivos Admin Super:</strong> usuarios o claves de aplicación con el <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">rol</a> <strong>Owner (Admin Super)</strong>.</li><li><strong>Claves de aplicación filtradas:</strong> <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">claves de aplicación</a> expuestas en la web, identificadas por el equipo de seguridad de VTEX.</li><li><strong>Usuarios inactivos:</strong> usuarios que no han accedido al Admin en los últimos 30 días.</li></ul> |
+| Detectado | Fecha en que se detectó el hallazgo. |
+| Sensor | Sensor que detectó la amenaza: <br/><ul><li><strong>VTEX Identity</strong></li></ul> |
+| Gravedad | Nivel de gravedad de la amenaza, determinado por el impacto o riesgo potencial: <br /><ul><li><strong>Alta</strong></li><li><strong>Media</strong></li><li><strong>Baja</strong></li></ul> |
+| Menú de acciones ⋮ | Opciones disponibles para abordar el hallazgo: <br/><ul><li><a href="#gestionar-hallazgo" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Gestionar</a></li><li><a href="#posponer-hallazgo" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Posponer</a></li></ul> |
+
+### Gestionar hallazgo
+
+Para gestionar un hallazgo sigue las instrucciones a continuación:
+
+1. En la fila del hallazgo, haz clic en el menú ⋮ .
+2. Después, en `Gestionar`.
+
+   Serás redirigido a la pantalla de **Usuarios** en **Configuración de la cuenta** para editar los roles asociados al usuario o a la clave de aplicación en cuestión.
+
+### Posponer hallazgo
+
+Para mover un hallazgo a la pestaña **Pospuestos**, es decir, removerlo de la pestaña **Abiertos**, sigue las instrucciones a continuación:
+
+1. En la fila del hallazgo, haz clic en el menú ⋮ .
+2. Después, en `Posponer`.
+3. Elige el periodo de tiempo, en días, durante el cual deseas mantener este hallazgo en la pestaña **Pospuestos**. Las opciones disponibles son: **7**, **90** o **120** días.
+4. Haz clic en `Posponer`.
+
+![3-snooze-finding-es](//images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/38af2109f1f98bfcb771fbb654b4113b/3-snooze-finding-es.png)
+
+## Pospuestos
+
+La pestaña **Pospuestos** presenta en una tabla los hallazgos que se pospusieron, con la misma información descrita en la pestaña [Abiertos](#abiertos).
+
+En la pestaña **Pospuestos**, el menú de acciones de cada hallazgo presenta únicamente la opción `Reactivar alerta`, la cual te permite revertir la acción de posponer y devolver el hallazgo a la pestaña **Abiertos**.
+
+## Cerrados
+
+La pestaña **Cerrados** contiene la lista de hallazgos ya gestionados, es decir, finalizados. Esta información se presenta en forma de tabla y contiene: 
+
+| Columnas | Descripción |
+| --- | --- |
+| Hallazgo | Email de usuario o clave de la aplicación relacionado con el hallazgo. |
+| Tipo | Tipo de hallazgo detectado:<br/><ul><li><strong>Claves de aplicación antiguas:</strong> <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">claves de aplicación</a> que se crearon hace más de 6 meses.</li><li><strong>Excesivos Admin Super:</strong> usuarios o claves de aplicación con el <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">rol</a> <strong>Owner (Admin Super)</strong>.</li><li><strong>Claves de aplicación filtradas:</strong> <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">claves de aplicación</a> expuestas en la web, identificadas por el equipo de seguridad de VTEX.</li><li><strong>Usuarios inactivos:</strong> usuarios que no han accedido al Admin en los últimos 30 días.</li></ul> |
+| Detectado | Fecha en que se detectó el hallazgo. |
+| Cerrado | Fecha en que se cerró el hallazgo. |
+| Cerrado por | Indica que el hallazgo se cerró automáticamente tras ser gestionado por un usuario administrativo. |
+| Gravedad | Nivel de gravedad de la amenaza, determinado por el impacto o riesgo potencial: <br /><ul><li><strong>Alta</strong></li><li><strong>Media</strong></li><li><strong>Baja</strong></li></ul> |
+
+## Buscar hallazgos
+
+En la barra de búsqueda, ingresa la dirección de email del usuario o el nombre de la clave de la aplicación para encontrar hallazgos relacionados.
+
+## Filtrar hallazgos por tipo
+
+Al hacer clic en `Tipo` <i class="fas fa-chevron-down"></i>, puedes elegir uno de los tipos de hallazgo para filtrar los resultados mostrados en la lista. Haz clic en `Aplicar` para confirmar el filtro elegido y la lista se actualizará.
+
+![4-filter-findings-es](//images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/9718adf02a9fe3d71842848d87dca37c/4-filter-findings-es.png)
+
+## Editar configuración de las notificaciones
+
+Para editar aquellos usuarios administrativos que recibirán notificaciones en caso de hallazgos, sigue los pasos a continuación:
+
+1. Haz clic en el engranaje de la esquina superior derecha de la pantalla. 
+2. Ingresa el email del usuario a notificar y pulsa `Enter`. Repite este paso para agregar tantos usuarios como sea necesario.
+
+   Para remover un usuario, haz clic en la `X` junto al email relacionado.
+3. Haz clic en `Guardar`.
+
+![5-edit-notifications-es](//images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/b68c5dab3fabde1021d0c41db8ba2673/5-edit-notifications-es__1_.png)
+
+## Más información
+
+* [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh)
+* [Roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+* [Usuarios](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512)
+* [Claves de aplicación](https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet)
+
diff --git a/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md b/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md
index 60da3c4c0..e4eb1b7d5 100644
--- a/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md
+++ b/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md
@@ -27,8 +27,8 @@ Cuando el stock esté registrado, realice los siguientes pasos:
 2. En el módulo **Inventario y envío**, haga clic en **Estrategia de envío**.
 3. En **Estrategia de envío**, seleccione la pestaña **Almacenes** y copie el ID del stock que desea utilizar. 
 4. Luego, vaya al módulo **Marketplace**, seleccione la opción **Integraciones** y haga clic en **Configuración**.
-5. En la integración de Mercado Libre, haga clic en el ícono de engranaje <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" /> y seleccione la opción **Editar configuración**.
+5. En la integración de Mercado Libre, haga clic en el ícono de engranaje <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" /> y seleccione la opción **Editar configuración**.
 6. Ingrese el ID del stock seleccionado en el campo **Almacén Mercado Full**.
 7. Para finalizar, haga clic en **Guardar Configuración**.
 
-![Início (3)](https://images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
+![Início (3)](//images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
diff --git a/docs/tutorials/es/seller-management.md b/docs/tutorials/es/seller-management.md
index e12b6914e..168d32164 100644
--- a/docs/tutorials/es/seller-management.md
+++ b/docs/tutorials/es/seller-management.md
@@ -17,7 +17,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 **Gestión de sellers** es la página donde los operadores del marketplace [agregan sellers](https://help.vtex.com/es/tutorial/adicionar-seller--tutorials_392), registran su información y gestionan sus status. La página incluye métricas para que los marketplaces evalúen su operación. También pueden aplicar filtros a los resultados de la lista de sellers y agruparlos a través de la opción Grupos, tags que le permiten filtrar los resultados más fácilmente.  
 
-![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 ## Métricas
 La página muestra las métricas generales de los sellers:
@@ -46,7 +46,7 @@ Esta funcionalidad permite a los marketplaces optimizar los escenarios de seguim
 
 Los grupos se crean manualmente en __Agregar seller__ o al hacer clic en __Gestionar grupos.__ También se puede editar o eliminar los grupos después de crearlos.  
 
-![Gestión de seller](https://images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/c74c7c6069bb8e6e4908a10c4e208827/gestionador_de_seller_es.png)  
+![Gestión de seller](//images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/c74c7c6069bb8e6e4908a10c4e208827/gestionador_de_seller_es.png)  
 
 ## Gestionar grupos  
 
diff --git a/docs/tutorials/es/seller-monitoring.md b/docs/tutorials/es/seller-monitoring.md
new file mode 100644
index 000000000..38adf21aa
--- /dev/null
+++ b/docs/tutorials/es/seller-monitoring.md
@@ -0,0 +1,60 @@
+---
+title: 'Monitoreo de seller'
+id: 3Gt3Zu7BPFAaTRRehi27ez
+status: DRAFT
+createdAt: 2023-07-18T19:35:09.684Z
+updatedAt: 2023-07-19T13:53:51.474Z
+publishedAt: 
+firstPublishedAt: 2023-07-18T19:55:46.688Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: monitoreo-de-seller
+locale: es
+legacySlug: monitoreo-de-seller
+subcategory: 2xWRgEIlR2ookieEmm4KQu
+---
+
+El **Monitoreo de seller** es una herramienta del módulo [Gestión de sellers](https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv) que permite que el *marketplace* mida el desempeño de los *sellers* que venden a través de su tienda. Si deseas acceder a esta página,en el Admin VTEX,ve a **Marketplace > Sellers > Gestión de sellers > y haz clic en el botón Configurar métrica**. En la página de inicio,encontrarás las siguientes secciones:
+
+- **Integridad de la operación**: En esta sección,verás la información de todos los *sellers* que venden en tu tienda,entre la que se incluye:
+  - Total de sellers activos
+  - Tiempo promedio de facturación
+- **Resumen**: Aquí podrás ver la métrica detallada con información pormenorizada de la infracción que resultó en un status ⚠ **Aceptable** o ❌ **Insatisfactorio** del *seller*. Si haces clic en el botón (incluir símbolo del botón), puedes filtrar por *seller* y seleccionar solo los *sellers* que deseas.
+
+Al hacer clic en el botón **Ver pedidos,** se abrirá una ventana emergente con el **ID del pedido**, el **Tiempo** y el botón **Ver.**
+
+|**Campo**|**Descripción**|
+| - | - |
+|**ID del pedido**|Código que se genera automáticamente para cada pedido realizado en el *marketplace*.|
+|**Tiempo**|Tiempo que tarda en facturarse el pedido.|
+|**Ver**| Botón de direccionamiento. Al hacer clic en este botón, el *marketplace* te direccionará a la información detallada del pedido en el OMS.|
+
+Si es la primera vez que accedes a la herramienta,deberás configurar la métrica **Tiempo de facturación**. Aquí definirás el tiempo máximo y el tiempo de preferencia para que se facturen los pedidos de los *sellers*. A continuación, se muestra cómo realizar la configuración.
+
+## Cómo configurar las métricas
+
+Si deseas configurar las métricas, sigue estas instrucciones.
+
+1. En tu Admin VTEX, ve a **Marketplace >  Sellers > Gestión de sellers > Configurar métrica.**
+2. Haz clic en **Tiempo de facturación** y rellena los campos que aparecen.
+3. Haz clic en **+ Agregar variación** y rellena los campos requeridos para configurar las variaciones de un segmento o grupo de *sellers*.
+4. Haz clic en **Guardar**.
+
+Al hacer clic en **`Guardar`**, recibirás notificaciones en el Admin sobre el desempeño de la operación de los *sellers* y podrás ver a los *sellers* que no cumplen los plazos previstos.
+
+|**Campo( * obligatorio)**|**Descripción**|
+| - | - |
+|**Valor límite*** |Valor máximo que se define para medir si el *seller* cumple o no los estándares de tu *marketplace*.|
+|**Segmentación*** |Definirás cuáles son los *sellers* o el grupo de *sellers* que estarán sujetos a un valor definido en **Valor límite.**|
+|**Límite preferido**|Valor que se define para alertar al *seller* que se está acercando al **Valor límite.**|
+
+Cuando hayas configurado una variación en una métrica, el orden establecido es el que define la prioridad. En los casos en que solo hay una segmentación por grupo y otra por excepción, el único conflicto que existe está relacionado con la clasificación.
+
+## Editar una métrica
+
+Puedes editar la métrica después de haberla configurado. Para hacerlo, sigue estos pasos:
+
+1. Haz clic en el botón **Editar métrica.**
+2. Cambia los valores de los campos que se mostrarán.
+3. Haz clic en el botón **Guardar**.
diff --git a/docs/tutorials/es/seller-portal-creating-a-promotion.md b/docs/tutorials/es/seller-portal-creating-a-promotion.md
new file mode 100644
index 000000000..2b37bd7a4
--- /dev/null
+++ b/docs/tutorials/es/seller-portal-creating-a-promotion.md
@@ -0,0 +1,102 @@
+---
+title: 'Seller portal: crear una promoción'
+id: kzNPEaiJE8EWkDzO9dbBI
+status: PUBLISHED
+createdAt: 2023-09-01T15:28:13.875Z
+updatedAt: 2023-11-16T18:06:30.499Z
+publishedAt: 2023-11-16T18:06:30.499Z
+firstPublishedAt: 2023-09-01T16:58:54.457Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: seller-portal-crear-una-promocion
+locale: es
+legacySlug: seller-portal-crear-una-promocion
+subcategory: 4hisB47iAVZk4r3SEmMoG
+---
+
+Para crear una nueva promoción como seller en el Seller Portal, sigue los pasos que se indican a continuación.
+
+1. En el Admin VTEX Admin, ve a **Productos > Promociones > Promociones** o ingresa **Promociones** en la barra de búsqueda de la parte superior de la página.
+2. Haz clic en `Crear promoción.`
+3. Rellena los datos solicitados en los [Campos de registro de la promoción](#campos-de-registro-de-la-promocion).
+4. Haz clic en `Guardar`
+5. Revisa la configuración de tu promoción antes de publicarla.
+![seller-portal-promo-revisao-es](//images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/29c086e5c167c63b97438bec6410a865/image.png)
+6. Haz clic en `Confirmar`.
+
+Después, se activará la promoción y se aplicará a tu tienda.
+
+<div class = "alert alert-info">
+Las promociones que puedan aplicarse a los mismos ítems del carrito se comparan por su valor de descuento. A este respecto, el módulo Promociones intenta siempre aplicar la promoción más ventajosa para el comprador.
+</div>
+
+## Campos de registro de la promoción
+
+### General
+
+En esta sección, debes configurar la información general de la promoción.
+
+![seller-portal-promo-geral-es](//images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/23a283361433a809c30668b5143f6fc6/image.png)
+
+* **Nombre:** nombre de la promoción.
+* **Status:** botón de alternancia que define si la promoción está activa <i class="fas-toggle-on"></i> o inactiva <i class="fas-toggle-off"></i>.
+* **Descripción:** descripción interna de la promoción. Este campo se utiliza para la comunicación interna de tu tienda, para dejar claro si la promoción se debe a alguna campaña o liquidación de stock, por ejemplo.
+* **Fecha de inicio:** fecha de inicio de la promoción. Se puede seleccionar una fecha y hora futuras para que la promoción comience a aplicarse en el sitio web. Si se configura de esta forma, la promoción tendrá el status de **programada** hasta que se alcance la fecha. 
+* **Fecha de fin:** fecha de finalización de la promoción. Mientras la fecha de finalización no se alcance, la promoción tendrá el status de activa, pero al llegar el día estipulado para su finalización, el descuento se desactivará automáticamente.
+* **Hora de inicio:** hora en que la promoción empieza.
+* **Hora de fin:** hora en que la promoción termina.
+
+### Tipo de descuento
+
+Sección que define el tipo y valor del descuento que se aplicará en la promoción. Consulta las opciones de descuento a continuación:
+
+![seller-portal-promo-tipo-desconto-es](//images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/f74488e8864f4b7a0134835dc4fe114e/image.png)
+
+#### Precio
+
+* **Porcentaje:** porcentaje de descuento que se concederá al valor del producto.
+* **Precio máximo por ítem:** el precio máximo para cada ítem elegible de la compra será el precio anteriormente configurado. Esta opción solo se aplicará a los productos cuyo precio sea superior al valor configurado.
+
+#### Envío
+
+* **Envío gratis:** descuento en el valor total de envío de los ítems elegibles de la promoción.
+* **Porcentaje:** porcentaje de descuento que se concederá al valor del envío. 
+* **Precio máximo de envío:** valor máximo del envío. Si hay un método de envío más barato que el valor máximo configurado, se aplicará el de menor precio.
+
+### Productos elegibles
+
+En esta sección, debes seleccionar si la promoción se aplicará a todos los productos registrados en tu tienda o solo a productos específicos, como se ilustra a continuación.
+
+![seller-portal-promo-produtos-elegiveis-es](//images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/c281d0d00239a39cb1411e8fc88d73af/image.png)
+
+* **Todos los productos:** aplica la promoción a todo tu catálogo.
+* **Productos que cumplan las siguientes reglas:** limita la aplicación de la promoción a productos específicos respecto a las siguientes reglas de selección:
+  * **Categoría, Marca, Producto, SKU:** opción que define el criterio de selección de los productos.
+      * `Es uno de`: incluye los criterios de selección de productos.
+      * `No es uno de`: excluye los criterios de selección de productos.
+
+Una vez definidos los criterios de selección, ingresa el nombre de los ítems que deseas incluir o excluir.
+
+Para agregar más de una regla de selección, haz clic en `+ Agregar regla`. Si se configura más de una regla, solo los ítems que cumplan ambas reglas recibirán el descuento.
+
+Para eliminar una regla, haz clic en <i class="fas-trash-can"></i> `Remover regla`.
+
+### Condiciones
+
+El pedido del cliente debe cumplir todas las condiciones registradas en esta sección para que la promoción pueda aplicarse.
+
+![seller-portal-promo-condicoes-es](//images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/72e08a40feda1f058cf41f733062adc8/image.png)
+
+* **Precio del ítem:** el descuento solo se concederá a los ítems dentro del rango de precios establecido. 
+* **Tipo de envío:** el descuento se concederá si el tipo de envío elegido por el cliente es el mismo que el registrado en la promoción. 
+* **País de entrega:** el descuento se concederá a los ítems que se entreguen en los países seleccionados en este campo.
+* **Código postal de entrega:** el descuento se concederá si el código postal de entrega cumple la regla configurada. Es posible agregar más de un rango de códigos postales para incluir o excluir más zonas.
+
+### Restricciones
+
+La acción de la promoción estará limitada por el siguiente criterio:
+
+![seller-portal-promo-restricoes-es](//images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/b3c27968580ad91841f76bcffa707eee/image.png)
+
+* **Limitar el número de ítems elegibles por carrito: **define el número máximo de ítems del carrito a los que puede aplicarse la promoción. Si el carrito contiene más ítems que los estipulados en el límite, el descuento solo se aplicará a la cantidad configurada en este campo.
diff --git a/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
index d84e11b26..212d8ab4c 100644
--- a/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
@@ -27,7 +27,7 @@ A través del *Seller Portal*, los *marketplaces* pueden:
 - Reducir el tiempo de conversión de las ventas con una incorporación self-service de nuevos sellers ahora más rápida y sin fricciones.  
 - Compartir el surtido de productos con el seller de forma sencilla y gestionar rápidamente los anuncios de productos compartidos.  
 
-![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
 
 ## Interacción entre el seller y el marketplace en el Seller Portal
 
diff --git a/docs/tutorials/es/seller-portal-product-details.md b/docs/tutorials/es/seller-portal-product-details.md
index 6c3986794..f511f673b 100644
--- a/docs/tutorials/es/seller-portal-product-details.md
+++ b/docs/tutorials/es/seller-portal-product-details.md
@@ -15,7 +15,7 @@ legacySlug: seller-portal-detalles-del-producto
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
-![Shared products product details ES](https://images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/03a548e0bc52ff9953b51621583da3c9/Shared_products_product_details_ES.jpg)
+![Shared products product details ES](//images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/03a548e0bc52ff9953b51621583da3c9/Shared_products_product_details_ES.jpg)
 
 En la página «Detalles del producto» en la funcionalidad [Produtos Compartidos](https://help.vtex.com/es/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) se puede ver toda la información sobre un producto específico. A partir de ella el seller puede: 
 
diff --git a/docs/tutorials/es/seller-portal-promotions.md b/docs/tutorials/es/seller-portal-promotions.md
new file mode 100644
index 000000000..64d3be4d9
--- /dev/null
+++ b/docs/tutorials/es/seller-portal-promotions.md
@@ -0,0 +1,96 @@
+---
+title: 'Seller Portal: Promociones'
+id: 73LL7Ja0P4JbD77AH0jHwu
+status: PUBLISHED
+createdAt: 2023-10-03T16:07:24.166Z
+updatedAt: 2023-10-03T21:29:14.851Z
+publishedAt: 2023-10-03T21:29:14.851Z
+firstPublishedAt: 2023-10-03T21:26:29.611Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: seller-portal-promociones
+locale: es
+legacySlug: seller-portal-promociones
+subcategory: 4hisB47iAVZk4r3SEmMoG
+---
+
+La página **Promociones** del Seller Portal permite ver y gestionar la lista completa de promociones registradas, simplificando la gestión de las promociones del seller. Puedes acceder a la página a través del menú **Promociones > Promociones **en el Admin VTEX.
+
+A partir de la lista de promociones del Seller Portal puedes llevar a cabo diversas acciones:
+
+* [Crear nueva promoción](#crear-nueva-promocion)
+* [Buscar promociones](#buscar-promociones)
+* [Filtrar promociones](#filtrar-promociones)
+* [Exportar promociones](#exportar-promociones)
+* [Verificar datos de uso de las promociones](#verificar-datos-de-uso-de-las-promociones)
+* [Acceder al menú de acciones de la promoción](#acceder-al-menu-de-acciones-de-la-promocion)
+* [Acceder a promociones archivadas](#acceder-a-promociones-archivadas)
+
+![seller-portal-promo-es](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/a65cab7ea0ee0983f80894668ca050d0/image.png)
+
+En la siguiente tabla puedes consultar la información de la página **Promociones**: 
+
+| Columna         | Descripción          |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Nombre          | Nombre y descripción de la promoción.       |
+| Fecha de inicio | Fecha a partir de la cual se aplicará la promoción.                    |
+| Fecha de fin    | Fecha de término de la promoción.       |
+| Status          | Status de la promoción, que puede ser:<br><br>- **Activa:** cuando la promoción está activa y aplicándose en la tienda.<br>- **Programado:** cuando la promoción ha sido programada.<br>- **En pausa:** cuando la promoción está en pausa.<br>- **Completada:** cuando la promoción ha finalizado. |
+
+## Crear nueva promoción
+
+Para registrar una nueva promoción, haz clic en el botón `Crear promoción`. Para más información, consulta el tutorial [Seller Portal: crear una promoción](https://help.vtex.com/es/tutorial/seller-portal-crear-una-promocion--kzNPEaiJE8EWkDzO9dbBI).
+
+## Buscar promociones
+
+Para buscar una promoción específica en la lista puedes utilizar la barra de búsqueda,  ingresando nombre o descripción.
+
+## Filtrar promociones
+
+Puedes filtrar las promociones de la lista a partir de la siguiente información:
+
+* **Status:** status de la promoción. Las opciones son `Activa`, `Programada`, `Pausada` y `Completada`.
+* **Última edición:** filtra las ediciones más recientes realizadas en los últimos 12 meses, 3 meses, 30 días, 7 días o el día anterior a la consulta.
+
+Selecciona los filtros deseados y haz clic en `Aplicar` para filtrar las promociones. Para cancelar la selección, haz clic en `Limpiar` en los filtros deseados.
+
+## Exportar promociones
+
+Puedes descargar un archivo CSV con las promociones registradas en tu tienda y su respectiva información. Para hacerlo, pulsa el botón `Exportar` situado junto a la barra de búsqueda. El archivo exportado considera los filtros aplicados a la lista y no incluye las promociones archivadas.
+
+El archivo contiene la siguiente información sobre cada promoción:
+
+| Columna         | Descripción                                                                              |
+| --------------- | ---------------------------------------------------------------------------------------- |
+| ID              | ID de la promoción.                                                                      |
+| Nombre          | Nombre de la promoción.                                                                  |
+| Fecha de inicio | Fecha de inicio de la promoción.                                                         |
+| Fecha de fin    | Fecha de término de la promoción.                                                        |
+| Status          | Status actual de la promoción, que puede estar **Activa**, **Programada**, **Pausada** o **Completada**. |
+
+## Verificar datos de uso de las promociones
+
+![seller-portal-promo-es](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/a65cab7ea0ee0983f80894668ca050d0/image.png)
+
+Para ver el total de promociones activas en tu tienda y la cuota restante para nuevas promociones, haz clic en `Uso de las promociones`.
+
+De forma predeterminada, el número máximo de promociones activas es 100. Si necesitas aumentar este límite, ponte en contacto con nuestro [soporte](https://support.vtex.com/hc/pt-br/requests).
+
+## Acceder al menú de acciones de la promoción
+
+Al hacer clic en el ícono de menú <i class="fas fa-ellipsis-v"></i> de una promoción puedes realizar las siguientes acciones:
+
+*  <i class="fas fa-pencil-alt"></i> **Editar:** editar la promoción.
+*  <i class="far fa-clone"></i> **Duplicar:** crear una nueva promoción a partir de la información de la promoción seleccionada.
+* <i class="fas fa-archive"></i> **Archivar:** archivar la promoción. La promoción se trasladará automáticamente a la página [Promociones archivadas](#acceder-a-promociones-archivadas).
+
+## Acceder a promociones archivadas
+
+Para acceder a la página **Promociones archivadas**, haz clic en el ícono <i class="fas fa-ellipsis-v"></i> y a continuación en <i class="fas fa-box"></i>.
+
+Puedes desarchivar o duplicar promociones archivadas haciendo clic en el ícono <i class="fas fa-ellipsis-v"></i>. 
+
+ <div class="alert alert-info">
+  <p>Al desarchivar una promoción, su status cambiará a <code>Pausada</code>.</p>
+  </div>
diff --git a/docs/tutorials/es/seller-portal-shared-products.md b/docs/tutorials/es/seller-portal-shared-products.md
index f8e4267eb..0a4fc8dc9 100644
--- a/docs/tutorials/es/seller-portal-shared-products.md
+++ b/docs/tutorials/es/seller-portal-shared-products.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Productos Compartidos'
 id: 6vUGj2UmOuLzQTK9pj04lu
 status: PUBLISHED
 createdAt: 2021-02-02T20:31:40.476Z
-updatedAt: 2023-03-31T15:18:11.408Z
-publishedAt: 2023-03-31T15:18:11.408Z
+updatedAt: 2023-11-22T14:00:41.976Z
+publishedAt: 2023-11-22T14:00:41.976Z
 firstPublishedAt: 2021-09-15T20:52:51.767Z
 contentType: tutorial
 productTeam: Channels
@@ -15,6 +15,9 @@ legacySlug: seller-portal-productos-compartidos
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
+
+<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+
 **Productos compartidos** es el módulo donde usted gestiona los productos en común entre su catálogo y lo que ya se oferta en el marketplace. El panel de productos compartidos informa todos los productos que el marketplace ha puesto a disposición de su tienda para venta. Son productos sincronizados con el catálogo del marketplace. 
 
 La funcionalidad «Productos compartidos» reduce la complejidad de vender productos que el marketplace ya tiene disponibles en su propio catálogo, lo que permite al seller empezar a vender más rápido y con menos fricción. La funcionalidad tiene diferentes pestañas:
@@ -26,7 +29,7 @@ Para acceder a la funcionalidad «Productos compartidos», acceda a la pestaña
 
 ## Importados
 
-![Shared products Importados EN](https://images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/cde09ee87d8f119009fbc0b8cb8c5fef/Shared_products_Importados_ES.jpg)
+![Shared products Importados EN](//images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/cde09ee87d8f119009fbc0b8cb8c5fef/Shared_products_Importados_ES.jpg)
 
 La pestaña «Importados» reúne los productos del catálogo del marketplace que ya han sido importados por el seller, es decir, que ya pueden convertirse en anuncios. La lista contiene una barra de búsqueda que permite buscar productos por nombre o SKU. А través de esta pestaña se activan los productos.  
 
@@ -36,7 +39,7 @@ Al hacer clic en un producto de la lista, accederá a la página [Detalles del P
 
 ## Disponibles
 
-![Shared products Disponíveis ES](https://images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/0568df604b5d3754bd8f3b802dd646b1/Shared_products_Dispon__veis_ES.jpg)
+![Shared products Disponíveis ES](//images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/0568df604b5d3754bd8f3b802dd646b1/Shared_products_Dispon__veis_ES.jpg)
 
 La pestaña «Disponibles» reúne los productos del catálogo del marketplace que se han puesto a disposición del seller para su venta y que aún no se han incorporado a su catálogo. Puede filtrar los productos disponibles por marca o categoría para agilizar el proceso de importación de los productos seleccionados. 
 
diff --git a/docs/tutorials/es/send-item-price-with-tax-shown-separately.md b/docs/tutorials/es/send-item-price-with-tax-shown-separately.md
index 74ea49eb9..2e43ebf88 100644
--- a/docs/tutorials/es/send-item-price-with-tax-shown-separately.md
+++ b/docs/tutorials/es/send-item-price-with-tax-shown-separately.md
@@ -3,8 +3,8 @@ title: 'Enviar al Gateway o al ERP el precio del item ya con el impuesto separad
 id: 77O1rBSLHqW8eWWsE6IEii
 status: PUBLISHED
 createdAt: 2017-08-14T15:30:39.027Z
-updatedAt: 2019-12-31T15:21:46.929Z
-publishedAt: 2019-12-31T15:21:46.929Z
+updatedAt: 2024-04-17T14:38:57.929Z
+publishedAt: 2024-04-17T14:38:57.929Z
 firstPublishedAt: 2017-08-16T17:43:33.301Z
 contentType: tutorial
 productTeam: Others
@@ -23,10 +23,10 @@ En este artículo vamos a mostrar como el sistema funciona para estos casos.
 
 **Escenario 1**: Mi ERP envía el precio ya con IVA a VTEX, entonces no necesito hacer el cálculo.
 
-1. Página de Categoría![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
-2. Página de Producto![PRODUCTOSINIVA](https://images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
-3. Carrito![CARRITOSINIVA](https://images.ctfassets.net/alneenqid6w5/3khmyZuLjWycCs6eSgUmci/0f466b0981d5f982db6ee79ed9a1f2a0/3_CART_E.png)
-4. Checkout![CHECKOUTSINIVA](https://images.ctfassets.net/alneenqid6w5/6CAjPrEJG0Gm2oGwoekYW4/a5281e57a934b1845357a2af9725e48c/4_CHECK_E.png)
+1. Página de Categoría![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
+2. Página de Producto![PRODUCTOSINIVA](//images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
+3. Carrito![CARRITOSINIVA](//images.ctfassets.net/alneenqid6w5/3khmyZuLjWycCs6eSgUmci/0f466b0981d5f982db6ee79ed9a1f2a0/3_CART_E.png)
+4. Checkout![CHECKOUTSINIVA](//images.ctfassets.net/alneenqid6w5/6CAjPrEJG0Gm2oGwoekYW4/a5281e57a934b1845357a2af9725e48c/4_CHECK_E.png)
 
 **Escenario 2**: Mi ERP envía el precio *sin* IVA a VTEX.
 
@@ -34,11 +34,11 @@ Para indicar en las vitrinas el precio sumando las tasas aplicadas, utilice el a
 
 O entonces para crear un JS y sumar el valor del impuesto en las vitrinas, también si puede utilizar el control `$product.Tax` ( El indica las tasas registradas para el producto).
 
-[Vea la documentación sobre controles aquí](/es/tutorial/controles-do-template-de-prateleira)
+[Vea la documentación sobre controles aquí](https://developers.vtex.com/docs/guides/shelf-template-controls)
 
 __Atención__: En la pagina de producto es necesario poner un JavaScript para hacer la suma del valor.
 
-1. Página de Categoría![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
-2. Página de Producto![PRODUCTOCONIVA](https://images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
-3. Carrito![CARRITOCONIVA](https://images.ctfassets.net/alneenqid6w5/2Vqy71JAUMEKKMi6agQA6G/182ba9783f0a47e07e0ce9c91c7dec50/3A_CART_E.png)
-4. Checkout![CHECKOUTCONIVA](https://images.ctfassets.net/alneenqid6w5/6rsFbUYg4Ee0sKIyai6Ooy/199adee53185253d4248d8a279fbbbf9/4A_CHECK_E.png)
+1. Página de Categoría![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
+2. Página de Producto![PRODUCTOCONIVA](//images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
+3. Carrito![CARRITOCONIVA](//images.ctfassets.net/alneenqid6w5/2Vqy71JAUMEKKMi6agQA6G/182ba9783f0a47e07e0ce9c91c7dec50/3A_CART_E.png)
+4. Checkout![CHECKOUTCONIVA](//images.ctfassets.net/alneenqid6w5/6rsFbUYg4Ee0sKIyai6Ooy/199adee53185253d4248d8a279fbbbf9/4A_CHECK_E.png)
diff --git a/docs/tutorials/es/sending-sku-attributes-to-amazon.md b/docs/tutorials/es/sending-sku-attributes-to-amazon.md
index fabe5fd80..671d09d91 100644
--- a/docs/tutorials/es/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/es/sending-sku-attributes-to-amazon.md
@@ -19,7 +19,7 @@ Hechas las configuraciones iniciales para la [integración con Amazon](/es/tutor
 
 La asignación sólo se realizará una vez para cada categoría. De esta forma, incluso ya habiendo hecho un mapeo, cuando nuevos productos sean creados, ellos serán integrados directamente. Se hará un __de/para__ de los atributos registrados en VTEX con los atributos aceptados por Amazon.
 
-1. Cree una __planilla de upload__ en el formato `.xlsx` y rellene el título de las columnas según la imagen abajo.![Modelo Atributos Amazon](https://images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
+1. Cree una __planilla de upload__ en el formato `.xlsx` y rellene el título de las columnas según la imagen abajo.![Modelo Atributos Amazon](//images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
 
 2. Rellene los campos de la hoja de asignación de acuerdo con las indicaciones siguientes:
 
@@ -45,7 +45,7 @@ Nota: si <strong>ningún</strong> de los atributos de su categoría es requerido
 
 Planilla de ejemplo usando la categoría Clothing & Accessories:
 
-![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
+![Amazon Mapeamento ](//images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
 <div class="alert alert-danger">
 Recuerde que estos valores deben estar de acuerdo con los valores acceptados por Amazon. Consulte los términos permitidos y haga el De/Para entre lo que está registrado en su campo SKU en VTEX y los valores acceptador por Amazon.
diff --git a/docs/tutorials/es/sent-offers-beta.md b/docs/tutorials/es/sent-offers-beta.md
index c232e7f3c..25802dbc2 100644
--- a/docs/tutorials/es/sent-offers-beta.md
+++ b/docs/tutorials/es/sent-offers-beta.md
@@ -21,7 +21,7 @@ El módulo «Anuncios enviados» permite a los sellers supervisar el envío de a
 - [Anúncios](https://help.vtex.com/es/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#anuncios)            
 - [Canales](https://help.vtex.com/es/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#canales) 
 
-![Anuncios enviados Home ES](https://images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/b75456e0477b7025707752d87438b49a/Anuncios_enviados_Home_ES.jpg)
+![Anuncios enviados Home ES](//images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/b75456e0477b7025707752d87438b49a/Anuncios_enviados_Home_ES.jpg)
 
 ## Anuncios
 Cuando un seller configura condiciones de precios y stock, prepara su producto para que se convierta en un anuncio y se venda en el estante del marketplace. En el componente *Anuncios*, se puede ver el número total de anuncios, y los status:
diff --git a/docs/tutorials/es/sent-offers-buybox-opportunities.md b/docs/tutorials/es/sent-offers-buybox-opportunities.md
index 91da8edbd..2091699b7 100644
--- a/docs/tutorials/es/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/es/sent-offers-buybox-opportunities.md
@@ -1,10 +1,10 @@
 ---
-title: 'Gestión de anuncios: oportunidades de Buybox'
+title: 'Gestión de anuncios: oportunidades de Catálogo MeLi'
 id: 1hO9eI1th47EGxQoTzGewC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-07-29T19:59:30.988Z
-updatedAt: 2022-10-20T01:38:56.059Z
-publishedAt: 2022-10-20T01:38:56.059Z
+updatedAt: 2024-06-20T21:42:56.304Z
+publishedAt: 
 firstPublishedAt: 2021-07-29T20:20:39.780Z
 contentType: tutorial
 productTeam: Channels
@@ -12,14 +12,21 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: anuncios-enviados-oportunidades-de
 locale: es
 legacySlug: anuncios-enviados-oportunidades-de
-subcategory: 2zVauFUkYn8vgS0y0MfWeK
+subcategory: 
 ---
 
+<div class="alert alert-info">
+Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
+Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
+ </div>  
+
 Un Anuncio es un SKU cuyo precio y stock fueron configurados por un seller y que fue enviado a diferentes canales de venta. El módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) del Admin VTEX permite a los sellers supervisar el envío y la sincronización de sus productos a los marketplaces y también brinda oportunidades para obtener más ventas con sus anuncios. 
 
 La funcionalidad llamada *Oportunidades* identifica los anuncios del seller que pueden tener mayor éxito en los canales en los que se venden y dirige acciones para que las oportunidades se realicen. 
 
-Un ejemplo de oportunidad es la función de *Buybox* de Mercado Libre. La Buybox es un recurso del checkout de Mercado Libre que selecciona anuncios de sellers diferentes como opciones de compra para un mismo producto. El módulo **Gestión de anuncios** evalúa los anuncios compatibles con productos que ya están presentes en Mercado Libre para añadirlos a su Buybox.
+Un ejemplo de oportunidad es la función de Catálogo MeLi de Mercado Libre. Lo Catálogo MeLi es un recurso del checkout de Mercado Libre que selecciona anuncios de sellers diferentes como opciones de compra para un mismo producto. El módulo **Gestión de anuncios** evalúa los anuncios compatibles con productos que ya están presentes en Mercado Libre para añadirlos a su Catálogo MeLi.
 
 Las *Oportunidades* acompañan la presencia de un anuncio en las diferentes páginas del módulo **Gestión de anuncios**, como se muestra en las imágenes de la sección siguiente.
 
@@ -29,50 +36,54 @@ Las *Oportunidades* acompañan la presencia de un anuncio en las diferentes pág
 
 ## Lista de anuncios
 
-En la página [Gestión de anuncios](https://help.vtex.com/es/tutorial/offers-listing--7MRb9S78aBdZjFGpbuffpE), los anuncios con oportunidades de Buybox abiertas tendrán un ícono de rayo <i class="fas fa-bolt"></i> en el título. Al hacer clic en una `Oportunidad`, será redirigido a la siguiente página.
+En la página [Gestión de anuncios](https://help.vtex.com/es/tutorial/offers-listing--7MRb9S78aBdZjFGpbuffpE), los anuncios con oportunidades de __Catálogo MeLi__ abiertas tendrán un ícono de rayo <i class="fas fa-bolt"></i> en el título. Al hacer clic en una `Oportunidad`, será redirigido a la siguiente página.
 
 ## Detalles del anuncio
 
-![ES Oportunidades Offer details](https://images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/b27410f2f77ff4b0f4e2faa689cc2cf6/ES_Oportunidades_Offer_details.jpg)
+![ES Oportunidades Offer details](//images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/b27410f2f77ff4b0f4e2faa689cc2cf6/ES_Oportunidades_Offer_details.jpg)
 
 La página [Detalles del anuncio](https://help.vtex.com/es/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) presenta una tarjeta de `Oportunidad` en la parte superior de la página. Al hacer clic en `Ver oportunidad`, será redirigido a la siguiente página.
 
 ## Oportunidades del anuncio
 
-![ES Oportunidades oportunidades do anúncio](https://images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/1a9aa381135ca8eb4298195fd7140ad9/ES_Oportunidades_oportunidades_do_an__ncio.jpg)
+![ES Oportunidades oportunidades do anúncio](//images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/1a9aa381135ca8eb4298195fd7140ad9/ES_Oportunidades_oportunidades_do_an__ncio.jpg)
+
+La página **Oportunidades del anuncio** presenta el anuncio elegible para la Catálogo MeLi al lado del anuncio que está presente en el marketplace. La página le permite comparar los datos de los dos anuncios, incluida la información de la marca, especificaciones y dimensiones.
+
+Además de la oportunidad de agregar anuncios, existe __Auto Optin (creación automática de anuncios de Catálogo MeLi)__, en esta opción el Mercado Livre evaluará las publicaciones de los vendedores, si cumple con todos los requisitos para convertirse en un anuncio de Catálogo MeLi, será hecho automáticamente y el vendedor verá el siguiente mensaje.
 
-La página **Oportunidades del anuncio** presenta el anuncio elegible para la Buybox al lado del anuncio que está presente en el marketplace. La página le permite comparar los datos de los dos anuncios, incluida la información de la marca, especificaciones y dimensiones.
+![Auto Optin MELI](//images.ctfassets.net/alneenqid6w5/2Hiw11uUW5n5QHvwIlpo0C/a0866adadfae08101dcb84cdfcc87ef7/Captura_de_tela_2023-06-27_175316.png)
 
-## Añadir anuncios a la Buybox
+## Añadir anuncios a la Catálogo MeLi
 
-Siga los pasos a continuación para añadir su anuncio a la Buybox:
+Siga los pasos a continuación para añadir su anuncio a la Catálogo MeLi:
 
 1. En el Admin VTEX, ingresa en **Marketplace > Interaciones**.
 > Si su tienda utiliza el [Nuevo Admin VTEX](https://content.vtex.com/join-new-admin-beta-program-es/), acceda a **Marketplace > Conexiones**.
 2. Seleccione el anuncio deseado que tenga el ícono de rayo <i class="fas fa-bolt"></i>.
 3. En la página **Detalles del anuncio**, haga clic en `Ver oportunidad`.
-4. En la página **Oportunidad del anuncio**, evalúe si su anuncio es compatible con el anuncio que ya está en el *marketplace*. Si son compatibles, haga clic en `Agregar a la Buybox`. 
+4. En la página **Oportunidad del anuncio**, evalúe si su anuncio es compatible con el anuncio que ya está en el *marketplace*. Si son compatibles, haga clic en `Agregar a lo Catálogo MeLi`. 
 5. Haga clic en `Agregar`. 
 
 <div class="alert alert-warning">
-Esta acción no se puede deshacer, así que debe asegurarse de que los anuncios sean compatibles. Si un anuncio no es compatible con el producto que ya está presente en el marketplace, no lo añada a la Buybox. Añadir anuncios que no son parte del producto puede perjudicar su reputación como seller en el marketplace. 
+Esta acción no se puede deshacer, así que debe asegurarse de que los anuncios sean compatibles. Si un anuncio no es compatible con el producto que ya está presente en el marketplace, no lo añada a lo Catálogo MeLi. Añadir anuncios que no son parte del producto puede perjudicar su reputación como seller en el marketplace. 
 </div>
 
-Para que su anuncio esté bien posicionado en la Buybox, finalice los ajustes indicados en la sección de este artículo [Ganando y perdiendo en la Buybox](#ganando-y-perdiendo-en-la-buybox).
+Para que su anuncio esté bien posicionado en lo Catálogo MeLi, finalice los ajustes indicados en la sección de este artículo [Ganando y perdiendo en la Buybox](#ganando-y-perdiendo-en-la-buybox).
 
-## Ganando y perdiendo en la Buybox
-Después de [añadir el anuncio a la Buybox](#anadir-anuncios-a-la-buybox), su anuncio se activará en la Buybox de ese producto, pero no necesariamente será el primer artículo que aparecerá para comprar en el marketplace. Los anuncios pueden tener uno de los status a continuación:
+## Ganando y perdiendo en lo Catálogo MeLi
+Después de añadir el anuncio a lo Catálogo MeLi, su anuncio se activará en la Buybox de ese producto, pero no necesariamente será el primer artículo que aparecerá para comprar en el marketplace. Los anuncios pueden tener uno de los status a continuación:
 
-- **Ganando:** después de activar la oportunidad, su anuncio está en el primer lugar de la Buybox. 
+- **Ganando:** después de activar la oportunidad, su anuncio está en el primer lugar de lo Catálogo MeLi. 
 - **Perdiendo:** activó la oportunidad, pero no completó la configuración necesaria para hacer que el anuncio sea lo suficientemente atractivo para estar en primer lugar.
 
 Para que su anuncio tenga el status ganando, siga las instrucciones a continuación:
 
 1. En la página **Oportunidad del anuncio**, haga clic en `Ver detalles del anuncio`. 
 2. Acceda a la sección **Oportunidades activas**. 
-3. Siga las instrucciones que aparecen en la sección para completar la configuración del anuncio y activarlo en la Buybox.
+3. Siga las instrucciones que aparecen en la sección para completar la configuración del anuncio y activarlo en lo Catálogo MeLi.
 
 La sección *Oportunidades activas* de la página [Detalles del anuncio](https://help.vtex.com/es/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) contiene:   
-- **Datos de la Buybox:** información sobre las Buyboxes en las que se ha añadido el anuncio.  
+- **Datos de lo Catálogo MeLi:** información sobre lo Catálogo MeLi en los que se ha añadido el anuncio.  
 - **Status de la oportunidad:** incluye `Ganando` o `Perdiendo`.  
-- **Lista de configuraciones:** acciones necesarias para que el anuncio esté ganando en la Buybox. Algunas de las instrucciones que aparecen son cambiar el precio, promover envío gratis, entrega rápida u ofrecer pago con cuotas sin intereses. Cada ítem de la lista muestra una sugerencia de configuración que hará el anuncio más atractivo y lo posicionará en el primer lugar de la Buybox.   
+- **Lista de configuraciones:** acciones necesarias para que el anuncio esté ganando en lo Catálogo MeLi. Algunas de las instrucciones que aparecen son cambiar el precio, promover envío gratis, entrega rápida u ofrecer pago con cuotas sin intereses. Cada ítem de la lista muestra una sugerencia de configuración que hará el anuncio más atractivo y lo posicionará en el primer lugar de lo Catálogo MeLi.   
diff --git a/docs/tutorials/es/set-up-mundi-gateway.md b/docs/tutorials/es/set-up-mundi-gateway.md
index 2b763e5be..90fe738cd 100644
--- a/docs/tutorials/es/set-up-mundi-gateway.md
+++ b/docs/tutorials/es/set-up-mundi-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway Mundi '
 id: 2yn9dKzvZOF5tn4RCX2Nbq
 status: PUBLISHED
 createdAt: 2019-04-04T21:12:48.808Z
-updatedAt: 2023-03-26T21:57:24.882Z
-publishedAt: 2023-03-26T21:57:24.882Z
+updatedAt: 2024-01-23T19:02:29.463Z
+publishedAt: 2024-01-23T19:02:29.463Z
 firstPublishedAt: 2019-04-04T21:20:22.149Z
 contentType: tutorial
 productTeam: Financial
@@ -23,11 +23,11 @@ Si también desea utilizar el antifraude de Mundi, la configuración de esta fun
 
 Para configurar la afiliación Mundi, siga los pasos a continuación:
 
-<ui>1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.</ui>
+<ui>1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.</ui>
 
-<ui>2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.</ui>
+<ui>2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.</ui>
 
-<ui>3. Haga clic en el conector __Mundi__.</ui>
+<ui>3. Escriba el nombre __Mundi__ en la barra de búsqueda y haga clic en el nombre del proveedor.</ui>
 
 <ui>4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Mundi.</ui>
 
diff --git a/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md b/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md
index 22b2ab7f8..d98f83a23 100644
--- a/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md
+++ b/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md
@@ -27,6 +27,6 @@ Para configurar esta autenticación, siga los pasos abajo.
 2. Acceda **Configuración**
 3. Active la flag __Exigir autenticación del usuario para los pagos autorizados automáticamente__
 
-![autenticação-usuario-pagamento-recorrencia es](https://images.ctfassets.net/alneenqid6w5/1W670r1zO4EQOUUqY2MmAs/1644f9c9e1fe370662ad9c2dfedea2f4/autentica____o-usuario-pagamento-recorrencia_es.png)
+![autenticação-usuario-pagamento-recorrencia es](//images.ctfassets.net/alneenqid6w5/1W670r1zO4EQOUUqY2MmAs/1644f9c9e1fe370662ad9c2dfedea2f4/autentica____o-usuario-pagamento-recorrencia_es.png)
 
 4. Haga clic en el botón __Guardar__.
diff --git a/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md b/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md
index 885b782c3..35ff934cc 100644
--- a/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md
+++ b/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md
@@ -3,8 +3,8 @@ title: 'Configurar producto similar, sugerencias, accesorios y genéricos'
 id: tutorials_280
 status: PUBLISHED
 createdAt: 2017-04-27T22:10:17.727Z
-updatedAt: 2023-03-29T14:45:42.789Z
-publishedAt: 2023-03-29T14:45:42.789Z
+updatedAt: 2024-07-25T21:19:12.871Z
+publishedAt: 2024-07-25T21:19:12.871Z
 firstPublishedAt: 2017-04-27T23:03:13.377Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -35,7 +35,7 @@ Para ayudarlo a utilizar las técnicas arriba, podemos usar los campos en el reg
 4. Rellene los campos, como indicado abajo.
 5. Haga clic en el botón `Guardar`.
 
-![produto-similar-sugestão-acessório-exemplo es](https://images.ctfassets.net/alneenqid6w5/5ZqMyFekmcoAggmAww44w6/a6bbabc539865f8b82fdc583469864d5/produto-simular-sugest__o-acess__rio-exemplo_es.png)
+![produto-similar-sugestão-acessório-exemplo es](//images.ctfassets.net/alneenqid6w5/5ZqMyFekmcoAggmAww44w6/a6bbabc539865f8b82fdc583469864d5/produto-simular-sugest__o-acess__rio-exemplo_es.png)
 
 **Accesorios:** En este campo registramos los productos que deben venderse como complemento de otro producto. En esta opción, los productos registrados como accesorios se muestran como opción de compra con el checkbox de selección habilitado (función hecha en el layout).
 
@@ -45,6 +45,4 @@ Para ayudarlo a utilizar las técnicas arriba, podemos usar los campos en el reg
 
 **Mostrar junto**: Muestra los SKUs de los productos sugeridos para la compra en conjunto.
 
-Otras opciones de Cross Selling se pueden habilitar en la construcción del layout de la tienda como por medio de las opciónes de templates de estantes como “Quién compró compró también”, “Quien vio compró también” y "Quien vio vio también". Para más informaciones, acceda nuestro tutorial sobre [controles del template de estante](https://help.vtex.com/es/tutorial/lista-de-controles-para-plantillas--tutorials_563). 
-
 La opción de Up Selling se puede trabajar usando la promoción [Compre Junto](http://help.vtex.com/es/tutorial/comprar-juntos-registro-de-promocion).
diff --git a/docs/tutorials/es/setting-up-abandoned-carts.md b/docs/tutorials/es/setting-up-abandoned-carts.md
index 6c54aae77..44d3a57a5 100644
--- a/docs/tutorials/es/setting-up-abandoned-carts.md
+++ b/docs/tutorials/es/setting-up-abandoned-carts.md
@@ -3,8 +3,8 @@ title: 'Configurar carrito abandonado'
 id: tutorials_740
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:05.882Z
-updatedAt: 2023-04-28T14:50:21.362Z
-publishedAt: 2023-04-28T14:50:21.362Z
+updatedAt: 2024-06-24T14:49:04.124Z
+publishedAt: 2024-06-24T14:49:04.124Z
 firstPublishedAt: 2017-04-27T23:03:41.572Z
 contentType: tutorial
 productTeam: Shopping
@@ -40,7 +40,7 @@ Puede crear su propio template de email personalizado o utilizar la opción de e
 4. Rellene el campo __Template XHTML__ con los códigos de template.
 5. Haga clic en `Save Template`.
 
-![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
+![template xhtml](//images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
 
 <div class="alert alert-warning">
 Recomendamos que lo realicen profesionales familiarizados con el módulo CMS, que ya hayan realizado la configuración de otros templates de página y expositor.
@@ -50,7 +50,7 @@ Recomendamos que lo realicen profesionales familiarizados con el módulo CMS, qu
 2. En __CMS > HTML Templates__, haga clic en el icono `CEM-Abandoned-Cart`.
 3. Verifique la información de los códigos de template presentes en el campo __Template XHTML__.
 
-![CEM-Abandoned-Cart](https://images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
+![CEM-Abandoned-Cart](//images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
 
 #### Configurar modelo de email en el Centro de mensajes
 
@@ -69,7 +69,7 @@ Una vez que se haya creado el nuevo template de email o se hayan utilizado los d
 El campo JSON Data no debe completarse ni sus datos deben usarse en el template de email. Solo contiene información para permitir una vista previa del formato en el que se verán los datos en el email.
 </div>
 
-![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
+![New template - message center](//images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
 
 #### Liberación del SPF
 
@@ -77,7 +77,7 @@ La liberación del SPF es fundamental para evitar problemas de entregabilidad de
 
 Como buena práctica para configurar DNS para un dominio genérico (no obligatorio), siga el siguiente ejemplo:
 
-![Hostnames - SPF](https://images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
+![Hostnames - SPF](//images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
 
 Para obtener más información sobre este asunto, consulte [Configurar el apuntamiento del DNS para VTEX](https://help.vtex.com/es/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280#).
 
@@ -126,7 +126,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><blockquote><ui>-> Último Carrinho - Não está nulo</ui> 
 
-![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/d6c7e5d4e84c5d2b8b870de4ee0db4bc/Filter_Master_Data.PNG)
+![Filter master data 2](//images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/d6c7e5d4e84c5d2b8b870de4ee0db4bc/Filter_Master_Data.PNG)
 
 <div class="alert alert-warning">
   Además de los filtros indicados anteriormente, se recomienda insertar otro filtro en el siguiente formato: <code>Receives newsletter? - Equal to - True</code>. Esto garantiza el cumplimiento de los <a href="https://help.vtex.com/es/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">derechos de los titulares de datos</a>, ya que solo los clientes suscritos al boletín recibirán correos electrónicos de carritos abandonados. La suscripción al boletín de su tienda se puede realizar en el momento de la compra o en la sección <a href="https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">Mi Cuenta</a> de su tienda.
@@ -134,7 +134,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><ui> 10. Haga clic en pestaña <b>Schedule</b> (Programación) y seleccione si desea enviar el correo electrónico en una fecha específica o en una fecha dinámica.</ui>
 
-![Schedule date](https://images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/840f17bdc08c9703fdc972b2c8793668/Schedule_date.PNG)
+![Schedule date](//images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/840f17bdc08c9703fdc972b2c8793668/Schedule_date.PNG)
 
 <blockquote><ui>11. En la pestaña <b>If positive</b> (Si es positivo):</ui>
 
@@ -157,7 +157,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><blockquote><ui>h. En <b>URL</b>, ingrese la dirección de su tienda con las carpetas en las que el layout del carrito abandonado fue configurado, con el tag del carrito después (?refs={!carttag_SCORE}). Ex.: nomedaloja.com.br/CEM/Abandoned-Cart?refs={!carttag_SCORE}.</ui>
 
-  ![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)
+  ![PastasCarrinhoAbandonado](//images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)
 
 <div class="alert alert-warning">Esta URL debe ser la final de la tienda, y no la URL con vtexcommercestable.
 </div>
@@ -171,7 +171,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 <div class="alert alert-warning">La sesión de una página expira en 30 minutos. Solamente después de ese tiempo consideramos la programación del disparo de trigger de Carrito Abandonado. Es decir, el tiempo a ser considerado es el tiempo de la sesión + la programación de trigger. 
 </div>
 
-![If positive tab](https://images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/d863f83956f876035351cd222a0482ad/If_positive_Tab.PNG)
+![If positive tab](//images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/d863f83956f876035351cd222a0482ad/If_positive_Tab.PNG)
 
 ### Configuración para tiendas VTEX IO
 
@@ -182,7 +182,7 @@ Para configurar la funcionalidad de carrito abandonado en las tiendas VTEX IO, s
 3. Realice la [liberación del SPF](#liberacion-del-spf).
 4. [Configure el trigger](#configuracion-de-trigger) de la misma manera que en las tiendas Legacy hasta el Paso 10. A partir del Paso 11 (pestaña __Si es positivo__), siga las instrucciones disponibles en [Trigger configuration information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#trigger-configuration-information).
 
-![If positive tab IO](https://images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/ce32f7997824f648690edefe77ad03c0/If_positive_Tab_IO.PNG)
+![If positive tab IO](//images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/ce32f7997824f648690edefe77ad03c0/If_positive_Tab_IO.PNG)
 
 ## Dudas frecuentes
 
diff --git a/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
index 193bdaf91..58a4cef79 100644
--- a/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
@@ -17,7 +17,7 @@ subcategory:
 
 Este artículo tiene como objetivo explicar cómo la aplicación de inStore configura el AppLinking para las acciones de `payment` y `payment-reversal` con las apps de los adquirentes.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuración
 
diff --git a/docs/tutorials/es/setting-up-bradesco-registered-ticket.md b/docs/tutorials/es/setting-up-bradesco-registered-ticket.md
index 1963557c3..732f04286 100644
--- a/docs/tutorials/es/setting-up-bradesco-registered-ticket.md
+++ b/docs/tutorials/es/setting-up-bradesco-registered-ticket.md
@@ -3,7 +3,7 @@ title: 'Configurar boleto registrado Bradesco'
 id: bbnXBjvKOkWYiOosmASiA
 status: DRAFT
 createdAt: 2018-03-20T22:08:43.187Z
-updatedAt: 2022-12-23T20:13:39.299Z
+updatedAt: 2024-03-18T18:04:46.311Z
 publishedAt: 
 firstPublishedAt: 2018-03-21T17:27:23.026Z
 contentType: tutorial
diff --git a/docs/tutorials/es/setting-up-braspag-gateway.md b/docs/tutorials/es/setting-up-braspag-gateway.md
index ff245e0a0..e9a81f5e7 100644
--- a/docs/tutorials/es/setting-up-braspag-gateway.md
+++ b/docs/tutorials/es/setting-up-braspag-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar el gateway Braspag'
 id: 7tQmfLMvtYEsWoaaAaeKSC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-27T18:21:37.603Z
-updatedAt: 2023-03-29T01:03:06.303Z
-publishedAt: 2023-03-29T01:03:06.303Z
+updatedAt: 2023-09-19T14:26:39.079Z
+publishedAt: 
 firstPublishedAt: 2018-02-27T18:52:38.519Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-conductor-gateway.md b/docs/tutorials/es/setting-up-conductor-gateway.md
index d672e8baf..19e517d05 100644
--- a/docs/tutorials/es/setting-up-conductor-gateway.md
+++ b/docs/tutorials/es/setting-up-conductor-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Conductor'
 id: Q5Ezi95TSEyE2GCQSs8ak
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-05-02T17:09:15.090Z
-updatedAt: 2023-03-29T00:55:20.862Z
-publishedAt: 2023-03-29T00:55:20.862Z
+updatedAt: 2024-03-18T18:11:12.675Z
+publishedAt: 
 firstPublishedAt: 2018-05-02T18:38:56.879Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-conductor
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Conductor es un [gateway de pagos](/es/tutorial/que-es-un-gateway-de-pagos) con certificación [PCI](/es/faq/que-es-el-pci-ssc) que actúa desde hace más de 20 años con el procesamiento de pagos. En VTEX, se puede configurar para procesar pagos realizados con __tarjetas de crédito con bandera propia__.
 
 Para habilitar al Conductor en su tienda, siga los pasos abajo:
 
-## Configurar la afiliación de gateway Conductor
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Conductor__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Conductor__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __External Service Url__, configure la URL externa que va a estar asociada a `/pvt/payments?an={AccoutName}`.
 5. Rellene los campos de registro con los datos proporcionados por Conductor (campos _appKey_ y _appToken_).
 6. En __Implements Installments Service__, elija si desea utilizar servicios externos de parcelación o el que está configurado en el portal. Si elige la opción _yes_, el sistema utilizará la URL configurada en el campo __Installments Service Url__.
diff --git a/docs/tutorials/es/setting-up-cybersource-antifraud.md b/docs/tutorials/es/setting-up-cybersource-antifraud.md
index df03e72b3..3760516c8 100644
--- a/docs/tutorials/es/setting-up-cybersource-antifraud.md
+++ b/docs/tutorials/es/setting-up-cybersource-antifraud.md
@@ -3,8 +3,8 @@ title: 'Configurar antifraude CyberSource'
 id: 2Z88QmpRAsWmI0qaCo4aQg
 status: PUBLISHED
 createdAt: 2018-04-30T18:08:44.396Z
-updatedAt: 2023-03-26T21:48:46.023Z
-publishedAt: 2023-03-26T21:48:46.023Z
+updatedAt: 2024-03-15T15:29:09.166Z
+publishedAt: 2024-03-15T15:29:09.166Z
 firstPublishedAt: 2018-04-30T20:25:40.199Z
 contentType: tutorial
 productTeam: Financial
@@ -24,30 +24,32 @@ Si usted está buscando más detalles sobre el __gateway__ CyberSource, lea [est
 <div class="alert alert-info">
 Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de realizar el Paso 6. de esta sección.
 </div>
-1. 
-2. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-3. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-4. Haga clic en el conector __CyberSource__ que se encuentra en la sección _ANTIFRAUDES_.
+
+1. En el Admin VTEX, accede a  __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba __Cybersource__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Si desea modificar el nombre de identificación que se mostrará para el antifraude Cybersource en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
 5. Configure la URL `https://{store}.vtexpayments.com.br/api/pub/cybersource/antifraud/notification` en el sitio web de CyberSource, sustituyendo `{store}` por el nombre de su tienda. Esto habilitará las notificaciones cuando haya cambio de status de un pedido.
 6. Configure el device fingerprint en Google Tag Manager usando [este artículo del Help](/es/faq/como-configurar-el-device-finger-print-para-braspag-cybersource).
-7. Rellene los campos de registro con los datos proporcionados por CyberSource (campos _Identificación de la tienda en CyberSource_, _Nombre de usuario en CyberSource_ y _Su contraseña en CyberSource_).
-8. En el campo __Nombre de su empresa__, informe la razón social de su tienda.
+7. Rellene los campos __Id de merchant en CyberSource__, __Nombre de usuario en CyberSource__ y __Tu contraseña en CyberSource__ según datos proporcionados por CyberSource.
+8. En __Nombre de tu empresa__, informe la razón social de su tienda.
 9. En __Identificación fiscal de tu empresa__, informe el número del CNPJ de su tienda.
 10. En __Certificado privado (.p12)__, cargue un certificado privado válido (generado por usted, utilizando una empresa certificadora o un software especializado), con extensión .p12 y clave.
-11. En el campo __Contraseña del certificado privado__, introduzca la contraseña creada para acceder al certificado.
+11. En __Contraseña del certificado privado__, introduzca la contraseña creada para acceder al certificado.
 12. En __Merchant Key ID__ y __Merchant Secret Key__, informe los dados proporcionados por CyberSource para acceder a la API de informes.
 13. En __Documento Opcional__, seleccione si desea envial el documento para el análisis de fraude.
 14. En __Enviar transacciones autenticadas?__, seleccione si desea enviar para análisis del antifraude todas las transacciones o sólo aquellas que no autenticadas.
-15. Haga clic en __Salva__.
+15. Haga clic en `Guardar`.
 
 ## Asociar antifraude a una condición de pago
 Después de configurar el antifraude de CyberSource, estará disponible para uso en su tienda. Para ello, usted debe asociarlo a las condiciones de pago, ya sean las que ya están configuradas o las que ya estén disponibles.
 
-1. Dentro de __Configuración__ en el módulo Pagos, haga clic en la pestaña __Planes de Pago__.
-2. Haga clic en la condición deseada o [cree una nueva condición de pago](/es/tutorial/condiciones-de-pago).
-3. Marque la opción __Usar antifraude__.
-4. Seleccione __CyberSource__.
-5. Haga clic en el botón __Salva__.
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de Pago__, haga clic en el botón `+`.
+3. Haga clic en la condición deseada o [cree una nueva condición de pago](/es/tutorial/condiciones-de-pago).
+5. Marque la opción __Utilizar antifraude__.
+6. Seleccione CyberSource.
+7. Haga clic en `Guardar`.
 
 <div class="alert alert-warning">
 Para que una transacción pase por el análisis del antifraude, <strong>la condición de pago utilizada por el cliente debe estar asociada a él</strong>.
diff --git a/docs/tutorials/es/setting-up-cybersource-gateway.md b/docs/tutorials/es/setting-up-cybersource-gateway.md
index 9113fd2d3..2dcd38cbd 100644
--- a/docs/tutorials/es/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/es/setting-up-cybersource-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar gateway CyberSource'
+title: 'Configurar gateway CyberSource IO'
 id: 6nhvUTrLxeacsoYG6GkGM
 status: PUBLISHED
 createdAt: 2018-04-30T17:34:57.517Z
-updatedAt: 2023-03-29T00:33:54.554Z
-publishedAt: 2023-03-29T00:33:54.554Z
+updatedAt: 2024-04-22T14:35:34.191Z
+publishedAt: 2024-04-22T14:35:34.191Z
 firstPublishedAt: 2018-04-30T20:20:44.704Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,213 @@ legacySlug: configurar-gateway-cybersource
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-CyberSource es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que ofrece diversas soluciones para ayudar a su tienda a administrar pagos. Entre ellas está un __gateway__ de pagos, que ofrece integración con la plataforma VTEX. Si usted está buscando más detalles sobre el __antifraude__ CyberSource, lea [este artículo del Help](/es/tutorial/configurar-antifraude-cybersource).
+Cybersource es una empresa que ofrece varias soluciones para ayudar a gestionar los pagos en su tienda. Entre ellos se encuentran un [gateway](https://help.vtex.com/es/tutorial/que-es-un-gateway-de-pagos--2KH9Wdi7F6swOU4amECSOk) y un [antifraude](https://help.vtex.com/es/tutorial/que-es-antifraude--69SjFCc4rC6Ii0OMAeYAsG), ambos con integraciones disponibles en VTEX.
 
-Para configurar el __gateway__ de CyberSource, siga los pasos abajo:
+Si desea obtener más información sobre cómo integrar Cybersource antifraude en su tienda, vaya a [Configurar antifraude CyberSource](https://help.vtex.com/es/tutorial/configurar-antifraude-cybersource--2Z88QmpRAsWmI0qaCo4aQg).
 
-## Configurar la afiliación de gateway CyberSource
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __CyberSource__ que se encuentra en la sección _OTROS_.
-4. Rellene los campos de registro con los datos proporcionados por CyberSource (_Identificacion de la tienda en Cybersource/ Id del comercio en CyberSource_, _Nombre de usuario / Nombre del Usuario utilizado en el painel de Cybersource_ y _Contraseña / contraseña utilizada en el painel de Cybersource_).
-5. En el campo __Nombre de su empresa__, informe la razón social de su tienda.
-6. En __CNPJ de su Empresa__, informe el número del CNPJ de su tienda.
-7. En el campo __Moneda__, elija la moneda que se utilizará en las transacciones de su tienda.
-8. En __Certificado privado (.p12)__ , cargue un certificado privado válido (generado por usted, utilizando una empresa certificadora o un software especializado), con extensión .p12 y clave.
-9. En el campo __Contraseña del certificado privado__, introduzca la contraseña (ese es tu _Identificacion de la tienda en Cybersource/ Id del comercio en CyberSource_).
+Para utilizar el gateway Cybersource IO en su tienda, se requieren las siguientes acciones:
+
+1. [Instalar aplicaciones Cybersource IO (VTEX IO CLI)](#instalacion-de-aplicaciones-cybersource)
+2. [Crear claves de autenticación en Cybersource (entorno Cybersource)](#crear-claves-de-autenticacion-en-cybersource)
+3. [Realizar la configuración de la aplicación Cybersource (Admin VTEX)](#configuracion-de-la-aplicacion-cybersource-io)
+4. [Configurar el Cybersource gateway (Admin VTEX)](#configuracion-del-gateway-cybersource)
+5. [Configurar condiciones de pago (Admin VTEX)](#configurar-condicion-de-pago)
+6. [Configurar o Device Fingerprint (opcional)](#configurar-cybersource-io-device-fingerprint-opcional)
+7. [Configurar campos de comerciante (opcional)](#configurar-campos-de-comerciante-opcional)
+
+## Instalación de aplicaciones Cybersource
+
+Las siguientes aplicaciones Cybersource deben estar instaladas en su cuenta de tienda:
+
+- __vtex.cybersource-ui__
+- __vtex.cybersource__
+- __vtex.cybersource-payer-auth__
+
+<div class="alert alert-warning">
+Si tiene la intención de utilizar el sistema antifraude de Cybersource, pero desea realizar transacciones de pagos en un gateway que no sea de Cybersource, deberá instalar la aplicación <b>vtex.cybersource-fraud</b>.
+  </div>
+
+Conozca más sobre la instalación de aplicaciones en una cuenta VTEX en [Installing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app). 
+
+## Crear claves de autenticación en Cybersource 
+
+Después de instalar las aplicaciones, debe crear claves de autenticación en el entorno Cybersource.
+
+<div class="alert alert-warning">
+  Las configuraciones realizadas en un ambiente externo a VTEX podrán ser discontinuadas o modificadas sin previo aviso. Consulte su cuenta Cybersource para obtener información actualizada.
+  </div>
+
+Siga los pasos a continuación:
+
+1. Accede al [panel Cybersource EBC](https://businesscenter.cybersource.com/ebc2/) (Enterprise Business Center) con tus datos.
+2. En el panel de navegación lateral, seleccione __Payment Configuration > Key Management__.
+3. Haga clic en __Generate Key__.
+4. En __REST APIs__, seleccione la opción __REST - Shared Secret__.
+5. Haga clic en __Generate Key__.
+6. Haga clic en __Download key__ o copie la información clave usando la función de copia ubicada frente a los campos __Key__ y __Shared Secret__.
+
+## Configuración de la aplicación Cybersource IO
+
+Con las claves de autenticación disponibles, es hora de configurar la aplicación Cybersource IO en el Admin. 
+
+![Cybersource Admin settings ES](//images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/ea8ae3e57058eb5c6da45af22a652ebd/Cybersource_Admin_settings_ES.JPG)
+
+Siga los pasos a continuación para configurar la aplicación Cybersource IO:
+
+1. En el Admin VTEX, accede a  __Apps > Apps Instaladas > Cybersource__, o escribe __Cybersource__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Admin Settings__, complete o seleccione los campos a continuación:
+<br>
+<ul>
+<br>
+    	<li><b>Identificación del comerciante</b>: su ID de comerciante en Cybersource.</li>
+    	<li><b>Clave de comerciante</b> y <b>Clave secreta compartida</b>: las dos claves obtenidas en el entorno Cybersource.</li>
+  <li><b>Processor</b>: seleccione la empresa que procesará el pago o haga clic en <b>Other</b> si no está en la lista.</li>
+  <li><b>Region</b>: seleccione una de las regiones o haga clic en <b>Other</b> si la región deseada no está en la lista.</li>
+    	<li><b>Sufijo de referencia (opcional)</b>: por defecto, los pedidos en el sistema Cybersource se asociarán con el ID del grupo de pedidos de VTEX, pero esta configuración se puede utilizar para agregar un sufijo como "-01".</li>
+    	<li><b>NSU personalizado (opcional)</b>: anular la NSU predeterminada con un valor personalizado.</li>
+    	<li><b>Utilice el ID de pedido para la huella digital del dispositivo</b>: seleccione si desea utilizar el ID del pedido en lugar del ID de la sesión para la toma de huellas digitales del dispositivo.</li>
+    	<li><b>Habilitar cálculos de impuestos</b>: seleccione si desea utilizar Cybersource al finalizar la compra como su proveedor de cálculo de impuestos.</li>
+    	<li><b>Habilitar la publicación de transacciones</b>: seleccione si desea habilitar la publicación de transacciones completadas para cuestiones de declaración de impuestos.</li>
+    	<li><b>Canales de venta para excluir de Cybersource (opcional)</b>: ingrese a cualquier canal de ventas en el que no desee utilizar transacciones de Cybersource.</li>
+    	<li><b>Código de producto de envío (opcional)</b>: ingrese un código de producto para fines de cálculo del impuesto de envío.</li>
+    	<li><b>Regiones de nexo fiscal (opcional)</b>: ingrese una lista de regiones donde se deben recaudar impuestos.</li>
+</ul>
+3. Haga clic en __Guardar ajustes__.
+
+## Configuración del gateway Cybersource
+
+Para configurarel gateway Cybersource, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a  __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba __Cybersource IO__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, No es necesario completar los campos __Clave de aplicación__ y __Token de aplicación__.
+5. Si desea modificar el nombre de identificación que se mostrará para el gateway Cybersource en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el gateway en un entorno de prueba haciendo clic __Activar modo de prueba__.
+7. En el campo __Liquidación automática__, selecciona una de las siguientes opciones::
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: la captura no es automática, sino que está programada para realizarse a los 4 días (o si el pedido está facturado, lo que ocurra primero).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>      
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. En __Campos del proveedor__, complete o seleccione los campos a continuación:
+<ul>
+<br>
+    	<li><b>Company Name</b>: nombre de la compania.</li>
+      <li><b>Company Tax id</b>: número de identificación de la empresa.</li>
+  <li><b>Capture Setting</b>: seleccione <b>Delayed Capture</b> para seguir el procedimiento estándar de la plataforma VTEX (llamadas separadas para autenticación y captura) o <b>Immediate Capture</b>, donde se enviará una única llamada de autenticación y captura a CyberSource cuando se realice el pedido.
+</li>
+    	<li><b>Payer Authentication</b>: si desea habilitar esta opción, <a href="https://www.cybersource.com/en/solutions/fraud-and-risk-management/payer-authentication-for-3d-secure.html">3-D Secure Payer Authentication da Cybersource</a> debe ser usado.</li>
+    	<li><b>Capture Delay</b> y <b>Capture Delay Interval</b>: determine el período antes de la captura automática.</li>
+    	<li><b>Using Decision Manager</b>: seleccione si <a href="https://www.cybersource.com/apac/en/solutions/fraud-and-risk-management/decision-manager.html">CyberSource Decision Manager</a> estará activo en su cuenta.</li>
+      <li><b>Authorized Payments Flagged by Decision Manager</b>: Cuando el estado Authorized, Fraud Reject, seleccione las siguientes opciones:</li>
+      <blockquote><li><b>Treat as Successful Authorizations</b>: aceptar el pedido.</li></blockquote>
+      <blockquote><li><b>Treat as Failed Authorizations</b>: negar el pedido.</li></blockquote>
+      <blockquote><li><b>Treat as Pending Authorizations</b>: mantener el pedido en espera de una decisión final.</li></blockquote>  
+</ul>
+9. Los campos __Merchant Id__, __Merchant Key__ y __Shared Secret Key__ debe dejarse en blanco, ya que se utilizarán los valores definidos en el paso 2 de la sección [Configuración de la aplicación Cybersource IO](#configuracion-de-la-aplicacion-cybersource-io).Si los campos se completan con un valor, sobrescribirán la información ingresada en el paso 2.
 10. Haga clic en __Guardar__.
 
-## Configurar la condición de pago
-Después de seguir los pasos indicados arriba, el gateway de CyberSource estará configurado en su tienda. Así, cuando se registre una condición de pago, estará disponible en el campo __Procesar con la afiliación__ (siempre que el medio de pago sea compatible con CyberSource). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+## Configurar condición de pago
+
+Para procesar pagos con tarjeta de crédito a través de Cybersource, siga los pasos a continuación:
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón +.
+3. Haga clic en el nombre de la tarjeta de crédito deseada.
+4. Complete el campo __Nombre de la condición__ con un nombre de su elección para identificación.
+5. Active la condición en el campo __Status__.
+6. En __Procesar con proveedor__ selecciona la opción __Cybersource - IO__.
+7. Si desea utilizar un sistema antifraude, seleccione la opción __Usar antifraude__ y elija su proveedor preferido.
+8. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456). 
+9. Haga clic en __Guardar__.
+
+<div class="alert alert-warning">
+  Si anteriormente creó condiciones de pago con tarjeta de crédito para otros gateways (incluido el proveedor Cybersource legado), puede establecer esas condiciones en <b>Inactivas</b>. Las transacciones en curso iniciadas desde ese proveedor seguirán siendo procesadas por ese proveedor, incluso si está inactivo. El nuevo proveedor de Cybersource IO solo procesará las transacciones nuevas. Si necesita volver a su proveedor anterior por algún motivo, simplemente establezca sus condiciones de pago en <b>Activas</b> y las condiciones de pago de Cybersource IO en <b>Inactivas</b>.</div>
+
+## Configurar Cybersource IO Device Fingerprint (opcional)
+
+Device Fingerprint es un identificador que actúa en el procesamiento de un pago, con el objetivo de mejorar el análisis del riesgo de fraude en cada transacción. 
+
+Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
+
+<div class="alert alert-info">
+Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
+</div>
+
+Para configurar Device Fingerprint Cybersource IO, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Storefront > Checkout__, o escribe __Checkout__ en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en el icono <i class="fas fa-cog" alt="blue gear"></i> del sitio deseado.
+3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Código__.
+4. En __Archivos__, haga clic en __checkout5.custom.js__.
+5. Ingrese el código a continuación en el campo de texto y haga clic en "Guardar".
+
+    function addsDeviceFingerPrint() {
+      if (!window.vtex) return;
+      if (window.vtex.deviceFingerprint) return;
+      $.ajax({
+type: 'get',
+async: true,
+url: rootPath() + '/api/sessions?items=*'
+      }).then(function(response) {
+var ORG_ID = "{{ORG_ID}}";
+var MERCHANT_ID = "{{MERCHANT_ID}}";
+console.log('session', response);
+window.vtex.deviceFingerprint = response.id;
+var sessionId = response.id || "CYBERSOURCE";
+var script = document.createElement("script");
+script.type = "text/javascript";
+script.src = `https://h.online-metrix.net/fp/tags.js?org_id=${ORG_ID}&session_id=${MERCHANT_ID}${sessionId}`;
+document.head.appendChild(script);
+var noScript = document.createElement("noscript");
+var iframe = document.createElement("iframe");
+iframe.style = "width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;";
+iframe.src = `https://h.online-metrix.net/fp/tags?org_id=${ORG_ID}&session_id=${MERCHANT_ID}${sessionId}`;
+noScript.appendChild(iframe);
+document.body.appendChild(noScript);
+      })
+    }
+
+## Configurar campos de comerciante (opcional)
+
+Además, puede definir campos personalizados que se incluirán en los pedidos enviados desde VTEX a Cybersource. 
+
+![Cybersource Admin merchant define fields ES](//images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/b9aa1888660f6fb63c77923243821125/Cybersource_Admin_merchant_define_fields_ES.JPG)
+
+Vea a continuación cómo crear estos campos:
+
+1. En el Admin de VTEX, acceda a __Apps > Apps Instaladas > Cybersource__, o escriba __Cybersource__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Campos definidos por el comerciante__, en __Información definida por el comerciante__, puede insertar campos siguiendo las siguientes reglas:
+<ul>
+<br>
+    	<li>Cualquier valor fuera de las claves <b>{{}}</b> se considerará como un valor directo.</li>
+      <li>Cualquier valor entre <b>{{}}</b> debe tener el siguiente formato <i>Palabra de referencia|Palabra de modificación|Valores</i>.</li>
+      <li>Todas las <b>palabras de referencia</b> se pueden encontrar en el menú desplegable <b>Mostrar todas las palabras referenciables</b>:</li>
+  <blockquote><li><b>Palabras de referencia</b> se pueden dejar en blanco si la <b>Palabra de modificación</b> y <b>Valuores</b> están presentes.</li></blockquote>
+  <blockquote><li>La <b>palabra de referencia</b> 
+distingue entre mayúsculas y minúsculas.</li></blockquote>
+    	<li><b>Palabras de modificación</b> deben ser <b>Pad</b>, <b>Date</b>, <b>Trim</b>, <b>Age</b>, o <b>Equals</b>. Vea a continuación las características al registrar cada uno de ellos:</li>
+      <blockquote><li><b>Pad</b>: los <b>Valores</b> deben tener el formato <b>desired length:fill character</b>.</li></blockquote>
+      <blockquote><blockquote><li>El <b>filled character</b> debe ser un valor único. Por ejemplo, <i>9:x</i> dará como resultado una longitud deseada de 9 y llenará los espacios con x.</li></blockquote></blockquote>
+  <blockquote><blockquote><li>Si el valor del campo excede el <b>desired length</b>, el campo se recortará.</li></blockquote></blockquote>         
+<br>       
+      <blockquote><li><b>Date</b>: <b>Valores</b> debe tener el formato dd/MM/aaaa o cualquier combinación de los mismos.</li></blockquote>
+      <blockquote><blockquote><li><b>M</b> por mes debe estar en mayúscula. Este formato se puede pedir como se desee, como por ejemplo <b>aaaa/MM</b> o <b>aaaa</b> o <b>dd/aaaa/MM</b>.</li></blockquote></blockquote>
+      <blockquote><li><b>Trim</b>: limitará la longitud máxima del valor del campo sin agregar caracteres de relleno.</li></blockquote>
+      <blockquote><li><b>Age</b>: devolverá la diferencia entre la fecha actual y el valor del campo usando el formato Timespan.</li></blockquote>
+      <blockquote><li><b>Equals</b>: devolverá el valor booleano de una comparación de cadena entre el valor del campo y el valor de comparación.</li></blockquote>
+<br>
+    	<li>Cada nueva línea se considera un nuevo campo definido por el comerciante.</li>
+
+Ejemplos:
+
+| Valor ingresado en Admin em `Campos definidos por el comerciante`    | Escenario simulado     | Resultado     |
+| ---------- | ---------- | ---------- |
+| `969{{Reference|PAD|9:0}}`       | Cuando `Reference` es 6023       | 969602300000       |
+| `{{OrderId}}-01`       | Donde `OrderId` es 124578       | 124578-01       |
+| `{{MiniCart.Buyer.LastName}},{{MiniCart.Buyer.FirstName}}`       | Donde el comprador (`Buyer`) es John Doe       | Doe,John       |     
+
diff --git a/docs/tutorials/es/setting-up-firstdata-acquirer.md b/docs/tutorials/es/setting-up-firstdata-acquirer.md
index 08279d4a9..673c4a69a 100644
--- a/docs/tutorials/es/setting-up-firstdata-acquirer.md
+++ b/docs/tutorials/es/setting-up-firstdata-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar adquirente FirstData'
 id: 4mW6gU343eWY6c8m6ocO0i
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-26T21:04:20.319Z
-updatedAt: 2023-03-21T18:04:57.904Z
-publishedAt: 2023-03-21T18:04:57.904Z
+updatedAt: 2024-03-18T18:23:46.570Z
+publishedAt: 
 firstPublishedAt: 2018-04-26T22:08:51.029Z
 contentType: tutorial
 productTeam: Financial
@@ -15,47 +15,48 @@ legacySlug: configurar-adquirente-firstdata
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-FirstData, es un adquirente que está disponible exclusivamente para el mercado brasileño y argentino.
-
-Para configurar la solución, realice los siguientes pasos:
-
-1. Acceda al __Admin__ VTEX.
-2. En el módulo __Pagos__, haga clic en __Configuración__.
-3. Acceda a __Afiliaciones__ y haga clic en el botón verde “__+__”
-4. Busque __FirstData__ y seleccione el conector.
-5. Complete los campos solicitados con la siguiente información:
-
-- __Nombre de usuario:__ ID del usuario que tiene permiso para acceder a la API de Web Service. Esta información es necesaria para realizar la autorización básica
-- __Contraseña para autorización básica:__ Contraseña general del usuario de FirstData (la misma que fue citada en el campo «Nombre de usuario»), que se utilizará en la autorización.
-- __Store ID:__ Código que se envía en el archivo .XML de las llamadas. 
-- __País:__ País de origen de la cuenta.
-- __Moeda:__ Moneda del país de origen.
-- __Soft Descriptor:__ Texto que identificará la compra en el extracto de su cliente.
-- __Contraseña del certificado privado:__ Contraseña del certificado en su tienda.
-- __Certificado privado (.p12):__ Realice la carga de un certificado privado válido (generado por usted, utilizando un certificador o un software especializado), con extensión .p12 y clave.
-- __Plan Ahora:__ Si activó las opciones de plan de gobierno Ahora con FirstData, elija «True», de lo contrario, elija «False». Para más detalles sobre el plan Ahora, [haga clic aquí](http://planesahora.gob.fiservargentina.com/).
-  -   __Plan Ahora 3:__ Para los descuentos de pago en 3 cuotas.
-  -   __Plan Ahora 6:__ Para los descuentos de pago en 6 cuotas.
-  -   __Plan Ahora 10:__ Para los descuentos de pago en 10 cuotas.
-  -   __Plan Ahora 12:__ Para los descuentos de pago en 12 cuotas.
-  -   __Plan Ahora 18:__ Para los descuentos de pago en 18 cuotas.
-  -   __Plan Ahora 24:__ Para los descuentos de pago en 24 cuotas.
-  -   __Plan Ahora 30:__ Para los descuentos de pago en 30 cuotas.
-
-- __Auto Settle:__ Configure esta opción para definir cuándo se realizará la captura automática del pago.
-
-  -  __Inmediatamente:__ La captura se realizará tras la autorización del pago.
-  -  __1 - 30 días:__ La captura se realizará después de la autorización del pago, teniendo en cuenta el número de días seleccionado.
-  -  __Desactivado:__ La captura automática estará desactivada y no tendrá el comportamiento estándar de la plataforma (4 días para la captura). De esta forma, el pedido solo se captará en el momento en que se factura, o si la [captura manual](https://developers.vtex.com/docs/api-reference/payments-gateway-api#post-/api/pvt/transactions/-transactionId-/settlement-request) se habilita.
-
-- __Change Margin:__ Defina el margen porcentual para que un pago se modifique a un valor superior al autorizado inicialmente. Por ejemplo, si la compra se cerró y autorizó por USD 100, pero hay un [cambio en el pedido](https://help.vtex.com/es/tutorial/como-fazer-a-alteracao-de-itens--tutorials_190) a un valor superior antes de la captura, este conector permite que el aumento sea de hasta un 20% del valor que se autorizó inicialmente.
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
+En VTEX es posible la integración con FirstData. Con este proveedor tu comercio podrá realizar ventas mediante tarjetas de crédito, débito y Plan Ahora (sistema de pagos argentino).
+
+Para configurar FirstData, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __FirstData__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Complete los campos solicitados con la siguiente información:
+
+- __UserName__: ID del usuario que tiene permiso para acceder a la API de Web Service. Esta información es necesaria para realizar la autorización básica.
+- __Contraseña para autorización básica__: Contraseña general del usuario de FirstData (la misma que fue citada en el campo «Nombre de usuario»), que se utilizará en la autorización.
+- __ID de tienda__: Código que se envía en el archivo .XML de las llamadas. 
+- __País__: País de origen de la cuenta.
+- __Moneda__: Moneda del país de origen.
+- __Descripción de la transacción__: Texto que identificará la compra en el extracto de su cliente.
+- __Contraseña del certificado privado__: Contraseña del certificado en su tienda.
+- __Certificado privado (.p12)__: Realice la carga de un certificado privado válido (generado por usted, utilizando un certificador o un software especializado), con extensión .p12 y clave.
+- __Plan Ahora__: Si activó las opciones de plan de gobierno Ahora con FirstData, elija «True», de lo contrario, elija «False». Para más detalles sobre el plan Ahora, [haga clic aquí](http://planesahora.gob.fiservargentina.com/).
+  -   __Plan Ahora 3__: Para los descuentos de pago en 3 cuotas.
+  -   __Plan Ahora 6__: Para los descuentos de pago en 6 cuotas.
+  -   __Plan Ahora 10__: Para los descuentos de pago en 10 cuotas.
+  -   __Plan Ahora 12__: Para los descuentos de pago en 12 cuotas.
+  -   __Plan Ahora 18__: Para los descuentos de pago en 18 cuotas.
+  -   __Plan Ahora 24__: Para los descuentos de pago en 24 cuotas.
+  -   __Plan Ahora 30__: Para los descuentos de pago en 30 cuotas.
+
+- __Auto Settle__: Configure esta opción para definir cuándo se realizará la captura automática del pago.
+
+  -  __Inmediatamente__: La captura se realizará tras la autorización del pago.
+  -  __1 - 30 días__: La captura se realizará después de la autorización del pago, teniendo en cuenta el número de días seleccionado.
+  -  __Desactivado__: La captura automática estará desactivada y no tendrá el comportamiento estándar de la plataforma (4 días para la captura). De esta forma, el pedido solo se captará en el momento en que se factura, o si la [captura manual](https://developers.vtex.com/docs/api-reference/payments-gateway-api#post-/api/pvt/transactions/-transactionId-/settlement-request) se habilita.
+
+- __Change Margin__: Defina el margen porcentual para que un pago se modifique a un valor superior al autorizado inicialmente. Por ejemplo, si la compra se cerró y autorizó por USD 100, pero hay un [cambio en el pedido](https://help.vtex.com/es/tutorial/como-fazer-a-alteracao-de-itens--tutorials_190) a un valor superior antes de la captura, este conector permite que el aumento sea de hasta un 20% del valor que se autorizó inicialmente.
 
 <ul>
-6. Guarde la configuración realizada.
+5. Guarde la configuración realizada.
   </ul>
 
-### Configurar condiciones de pago
+Para configurar los métodos de pago a procesar por FirstData, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials).
 
-Después de realizar todos los pasos, FirstData estará configurada y lista para utilizarse en su tienda.
+Para definir condiciones especiales sobre los métodos de pago, acceda a [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorial).
 
-Para asociarla a una condición de pago, lea el artículo [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento).
+Después de seguir los pasos indicados, el conector FirstData puede tardar hasta 10 minutos en aparecer en la caja de tu tienda como opción de pago.
diff --git a/docs/tutorials/es/setting-up-getnet-acquirer-with-egetnet-connector.md b/docs/tutorials/es/setting-up-getnet-acquirer-with-egetnet-connector.md
index 52fa0cefc..84ff76c79 100644
--- a/docs/tutorials/es/setting-up-getnet-acquirer-with-egetnet-connector.md
+++ b/docs/tutorials/es/setting-up-getnet-acquirer-with-egetnet-connector.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar adquirente Getnet con el conector Egetnet'
+title: 'Configurar pago con Egetnet'
 id: 75kwGKPKnK8mwiEmQGYiWq
 status: PUBLISHED
 createdAt: 2018-04-27T13:55:54.133Z
-updatedAt: 2023-03-29T00:59:42.828Z
-publishedAt: 2023-03-29T00:59:42.828Z
+updatedAt: 2024-03-14T18:03:01.948Z
+publishedAt: 2024-03-14T18:03:01.948Z
 firstPublishedAt: 2018-04-27T16:07:30.586Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,19 @@ legacySlug: configurar-adquirente-getnet-con-el-conector-egetnet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Getnet, uno de los mayores [adquirentes](/es/tutorial/que-es-un-adquirente) de Brasil, puede ser configurado en su tienda usando el conector Egetnet. Recomendamos que utilice este conector para tener acceso a la integración más actual y a las nuevas features de Getnet.
+En VTEX es posible la integración con el proveedor de pagos Egetnet. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito y débito, boleto y PIX.
 
-Para configurar Getnet con el conector Egetnet, siga estos pasos:
+Para configurar Egetnet, siga los pasos a continuación:
 
-## Configurar la afiliación de gateway Egetnet
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Egetnet__.
-4. En el campo __Application Key__, introduzca la clave de la aplicación, proporcionada por Getnet.
-5. En __Application Token__, rellene el campo con el token proporcionado por Getnet.
-6. Haga clic en __Guardar__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Egetnet__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por Egetnet.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Egetnet en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
 
-## Configurar la condición de pago
-Después de seguir los pasos indicados, el conector Egetnet estará configurado en su tienda. Así, cuando se registre una condición de pago, estará disponible en el campo __Procesar con la afiliación__ (siempre que el medio de pago sea compatible con Egetnet). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+Para configurar los métodos de pago a procesar por Egetnet, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Egetnet puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md b/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md
new file mode 100644
index 000000000..843feb6ed
--- /dev/null
+++ b/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md
@@ -0,0 +1,30 @@
+---
+title: 'Configurar la integración de Intelligent Search con el Catálogo'
+id: 3Nt5cIdwISSlzVtnYfLeIH
+status: PUBLISHED
+createdAt: 2024-06-27T16:56:47.833Z
+updatedAt: 2024-06-27T17:01:32.662Z
+publishedAt: 2024-06-27T17:01:32.662Z
+firstPublishedAt: 2024-06-27T16:57:41.295Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configurar-la-integracion-de-intelligent-search-con-el-catalogo
+locale: es
+legacySlug: integraciones
+subcategory: 1EmKjP83dy0RWD9GzZkYsG
+---
+
+ En el Admin VTEX, la página **Configuración de la tienda** > **Intelligent Search** > **Integraciones** es responsable de la indexación inicial del catálogo con VTEX Intelligent Search. Luego de instalar la aplicación, la indexación constituye el primer paso para realizar la integración con el catálogo.
+
+Sigue las instrucciones a continuación para iniciar el proceso de integración:
+
+1. En el Admin de VTEX, accede a **Configuración de la tienda**, o ingresa **Configuración de la tienda** en la barra de búsqueda en la parte superior de la página.
+2. En **Intelligent Search**, haz clic en **Integraciones**.
+4. Haz clic en `Iniciar la integración`.
+
+Se dará inicio al proceso de indexación. Una vez completado, se mostrará la siguiente pantalla:
+
+![integracoes-es](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/0e53cf7952ac60b089bbcb5f6441640e/integracoes-es.PNG)
+
+No es necesario repetir este proceso. Una vez iniciada la integración, puedes realizar un seguimiento del status de indexación en la página [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md b/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md
index 11366161b..fdf54ee33 100644
--- a/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md
+++ b/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto registrado Itaú (Itaú Registrado)'
 id: 6MEHf1oDTOkuWM2CaYi4gu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-11-30T18:23:45.696Z
-updatedAt: 2021-07-08T19:14:45.697Z
-publishedAt: 2021-07-08T19:14:45.697Z
+updatedAt: 2024-03-18T18:01:00.472Z
+publishedAt: 
 firstPublishedAt: 2018-12-11T17:59:44.827Z
 contentType: tutorial
 productTeam: Financial
@@ -15,28 +15,30 @@ legacySlug: configurar-boleto-registrado-itau-itau-registrado
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Para configurar el boleto registrado de Itaú, usted puede elegir entre dos conectores diferentes: __Invoice Itaú__ (también conocido como Itaú Registrado o Boleto Itaú, que vas a aprender a configurar en este artículo) o el [ItauShopline](https://help.vtex.com/es/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq). En el caso del __Invoice Itaú__, la generación del boleto es hecha de forma transparente (sin redireccionamiento para el sitio del Itaú), pero la conciliación es hecha a través de archivos.
 
 Después de registrar una de estas afiliaciones de gateway, debe configurar la condición de pago de boleto bancario. De esta forma, los boletos emitidos serán registrados por Itaú.
 
 ## Configurar la afiliación de gateway de Invoice Itaú (Itaú Registrado)
-1. En el menú lateral, haga clic en __Pagos__, en la sección __Transacciones__.
-2. En las opciones que se abren, haga clic en __Configuración__.
-3. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-4. Haga clic en el conector __Invoice Itaú__.
-5. Introduzca el nombre de su empresa en el campo __Nombre de la empresa__ (Nome da Empresa). Recuerde que esa es la información que va a venir en el campo _Beneficiario_ del boleto.
-6. En el campo __CNPJ__, llene el número de registro de su empresa, sin puntuación.
-7. Rellene los datos bancarios de su empresa en los campos __Agencia__ y __Número de Cuenta__.
-8. En __Validad del boleto en días__, elija la cantidad de días (contados a partir de la generación del boleto) que su cliente tendrá para hacer el pago.
-9. En el campo __Instrucciones en el boleto al Cajero__ (Instruções no boleto ao Caixa), escriba las instrucciones que se imprimir en el boleto.
-10. Rellene los campos de registro con los datos proporcionados por Itaú: _Cartera_ (Portfólio ou Carteira), _Convenio_ y _Código del Cedente_.
-11. En __Dirección del Beneficiario__ (Endereço do Beneficiário), introduzca la dirección comercial de su empresa (respetando el límite de hasta _200 caracteres_).
-12. En el campo __¿Registrado?__, seleccione la opción _Si_. Al hacer esto, nuevos campos van a surgir para que usted llene.
-13. En __Ambiente de Autenticación__, introduzca el valor `beta`.
-14. En el campo __Tipo de Ambiente__, introduzca el valor `2`.
-15. Rellene los campos de registro con los datos proporcionados por Itaú: _Id del cliente_, _Secret del cliente_ y _Chave del itau_.
-16. En el campo __Días hasta que expire la transacción del boleto__, defina en cuántos días, después del vencimiento del boleto, expira la propia transacción. 
-17. Haga clic en el botón __Salva__.
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __BankInvoiceItau__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Introduzca el nombre de su empresa en el campo __Nombre de la empresa__ (Nome da Empresa). Recuerde que esa es la información que va a venir en el campo _Beneficiario_ del boleto.
+5. En el campo __CNPJ__, llene el número de registro de su empresa, sin puntuación.
+6. Rellene los datos bancarios de su empresa en los campos __Agencia__ y __Número de Cuenta__.
+7. En __Validad del boleto en días__, elija la cantidad de días (contados a partir de la generación del boleto) que su cliente tendrá para hacer el pago.
+8. En el campo __Instrucciones en el boleto al Cajero__ (Instruções no boleto ao Caixa), escriba las instrucciones que se imprimir en el boleto.
+9.  Rellene los campos de registro con los datos proporcionados por Itaú: _Cartera_ (Portfólio ou Carteira), _Convenio_ y _Código del Cedente_.
+10. En __Dirección del Beneficiario__ (Endereço do Beneficiário), introduzca la dirección comercial de su empresa (respetando el límite de hasta _200 caracteres_).
+11. En el campo __¿Registrado?__, seleccione la opción _Si_. Al hacer esto, nuevos campos van a surgir para que usted llene.
+12. En __Ambiente de Autenticación__, introduzca el valor `beta`.
+13. En el campo __Tipo de Ambiente__, introduzca el valor `2`.
+14. Rellene los campos de registro con los datos proporcionados por Itaú: _Id del cliente_, _Secret del cliente_ y _Chave del itau_.
+15. En el campo __Días hasta que expire la transacción del boleto__, defina en cuántos días, después del vencimiento del boleto, expira la propia transacción. 
+16. Haga clic en el botón __Salva__.
 
 ## Configurar la condición de pago Boleto Bancario
 1. Después de configurar la afiliación de gateway __Invoice Itaú__, haga clic en la pestaña __Planes de Pago__.
diff --git a/docs/tutorials/es/setting-up-itau-registered-ticket.md b/docs/tutorials/es/setting-up-itau-registered-ticket.md
index 2d27d403d..a17bd63a2 100644
--- a/docs/tutorials/es/setting-up-itau-registered-ticket.md
+++ b/docs/tutorials/es/setting-up-itau-registered-ticket.md
@@ -3,8 +3,8 @@ title: 'Configurar boleto registrado Itaú (ItauShopline)'
 id: 3TqzCHPU7KIYGsOKuUeQcq
 status: PUBLISHED
 createdAt: 2018-02-28T15:50:53.154Z
-updatedAt: 2023-03-29T01:19:04.085Z
-publishedAt: 2023-03-29T01:19:04.085Z
+updatedAt: 2024-03-18T18:27:01.365Z
+publishedAt: 2024-03-18T18:27:01.365Z
 firstPublishedAt: 2018-02-28T19:38:07.445Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-lendico-boleto-in-installments-as-a-payment-method.md b/docs/tutorials/es/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
index f793bab97..bacc1223e 100644
--- a/docs/tutorials/es/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
+++ b/docs/tutorials/es/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto en plazos Provu (Lendico) como medio de pago (medio de pago brasileño)'
 id: 1pRpPlkppLDEc1TVXTgrcu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-12-02T10:58:09.076Z
-updatedAt: 2023-03-26T21:47:26.770Z
-publishedAt: 2023-03-26T21:47:26.770Z
+updatedAt: 2024-07-23T18:06:34.554Z
+publishedAt: 
 firstPublishedAt: 2020-12-02T12:54:57.731Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md b/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md
index e519a635a..ad81a5078 100644
--- a/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md
+++ b/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar el subadquirente MercadoPagoV1'
 id: 6wTlR3UTJe6YMAsEuquO26
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-08T13:05:57.452Z
-updatedAt: 2023-03-22T18:05:53.962Z
-publishedAt: 2023-03-22T18:05:53.962Z
+updatedAt: 2024-03-18T18:35:39.248Z
+publishedAt: 
 firstPublishedAt: 2018-03-08T19:45:23.370Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,21 @@ legacySlug: configurar-el-subadquirente-mercadopagov1
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 En el Gateway de VTEX, puede configurar el [subadquirente](/es/tutorial/que-es-un-subadquirente) MercadoPago para operar de varias formas. El __MercadoPagoV1__ permite que su tienda reciba pagos con tarjetas de débito y crédito, además de la [cartera digital](/es/faq/que-es-una-billetera-digital-e-wallet) Mercado Pago.
 
 <div class="alert alert-warning">
-La afiliación <strong>MercadoPagoV1</strong> no admite pagos por boleto bancario.
+La integración <strong>MercadoPagoV1</strong> no admite pagos por boleto bancario.
 </div>
 
 Para configurar MercadoPagoV1, siga los siguientes pasos:
 
-## Configurar afiliación de gateway MercadoPagoV1
+## Configurar MercadoPagoV1
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones de Gateways__, haga clic en el botón __+__.
-3. Haga clic en el conector __MercadoPagoV1__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __MercadoPagoV1__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. El campo __OAuth login__ no se utiliza. Déjelo como está.
 5. Rellene los campos de registro __PublicKey__ y __AccessToken__ con los datos proporcionados por MercadoPago.
 6. Deje los campos __RefreshToken__, __ExpiredTokenIn__ y __Merchant Account Id__ en blanco.
diff --git a/docs/tutorials/es/setting-up-mercadopagov2-sub-acquirer.md b/docs/tutorials/es/setting-up-mercadopagov2-sub-acquirer.md
index 02c1a5c56..940aa4e2a 100644
--- a/docs/tutorials/es/setting-up-mercadopagov2-sub-acquirer.md
+++ b/docs/tutorials/es/setting-up-mercadopagov2-sub-acquirer.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar el subadquirente MercadoPagoV2'
+title: 'Configurar pago con MercadoPagoV2'
 id: 1y6k8lCSzJYfPs2yObNFo4
 status: PUBLISHED
 createdAt: 2021-11-30T18:49:42.837Z
-updatedAt: 2023-03-22T18:35:39.911Z
-publishedAt: 2023-03-22T18:35:39.911Z
+updatedAt: 2024-03-11T18:11:39.540Z
+publishedAt: 2024-03-11T18:11:39.540Z
 firstPublishedAt: 2021-11-30T19:32:27.420Z
 contentType: tutorial
 productTeam: Financial
@@ -15,35 +15,39 @@ legacySlug: configurar-el-subadquirente-mercadopagov2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En el Gateway de VTEX, se puede configurar el [subadquirente](https://help.vtex.com/es/tutorial/o-que-e-um-subadquirente#) MercadoPagoV2. A través de él, su tienda puede recibir pagos a través de métodos tradicionales como: boleto, PIX, tarjetas de débito y crédito, así como métodos exclusivos de Mercado Pago, como: MercadoPagoOff, MercadoPagoPro y MercadoPagoWallet.
-
-<div class="alert alert-warning">
-  Los subadquirentes <strong>MercadoPago</strong> y <strong>MercadoPagoV1</strong> no permiten lá recepción a través del PIX. Esta es una característica exclusiva de <strong>MercadoPagoV2</strong>.
-</div>
-
-## Configurar afiliación de gateway MercadoPagoV2
-
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el __botón “+”__.
-3. Haga clic en el conector __MercadoPagoV2__.
-4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Mercado Pago.
-5. En __Periodo de vencimiento__ del ticket, elija el número de días (contados desde la creación del boleto) que tendrá su cliente para realizar el pago.
-6. Ingrese el nombre de su tienda en el campo __Nombre para resúmenes__. Recuerde que esta es la información que se describirá en el campo Beneficiário en el boleto o en la factura de la tarjeta del cliente.
-7. En __Cuotas máximas__, escoja la cantidad máxima de cuotas enviadas a  Mercado Pago.
-8. En __Categoría principal de la tienda__, escoja la categoría que más se encaja con su tienda.
-9. En la opción __Reembolso automático / manual__, elija si se reembolsará al cliente automáticamente o manualmente en caso de cancelación del pedido.
-10. En __Modo binario__, seleccione “Sí” o “No”. Seleccionar “Sí”, indica que el proceso de aprobación del pago ocurre instantáneamente y pude ser aprobado o rechazado. Sellecionar “No”, indica que el pago puede estar en estado “pendiente” (si requiere alguna acción por parte del cliente) o “en proceso” (si se requiere revisión manual).
-11. En __Métodos de pago excluidos__, describe los métodos de pago que no deseas utilizar a través de MercadoPagoV2 (opcional). Si opta por dejar este campo en blanco, todos los métodos de pago disponibles de MercadoPagoV2 estarán disponibles en su tienda.
-12. En __Tipos de pago excluidos__,  describe las banderas específicas de crédito y débito (Visa, Mastercard, etc) que no deseas utilizar a través de MercadoPagoV2 (opcional). Si opta por dejar este campo en blanco, todos los tipos de pago disponibles de MercadoPagoV2 estarán disponibles en su tienda.
-13. En __Modo de procesamiento__, escoja cómo quiere usar MercadoPagoV2: como subadquirente o gateway. Para más información, visite [¿Qué es un subadquirente?](https://help.vtex.com/es/tutorial/o-que-e-um-subadquirente--64aX6PeRQQ66O8uCqo0W4q) y [¿Qué es un gateway de pagos?](https://help.vtex.com/es/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk). 
-14. En la opción __Integrator ID__, indique el código identificador del desarrollador o agencia que realiza la configuración de Mercado Pago.
-15. En la opción __Moneda__, elija si la moneda utilizada para el pago será "Local" (cada país) o "Dólar estadounidense" (USD).
-16. Haga clic en __Salvar__ (“Guardar”).
-
-## Configurar condición de pago
-Después de seguir los pasos indicados, MercadoPagoV2 estará configurado en su tienda. Así, cuando vaya a registrar una condición de pago, va a estar disponible en el campo __Procesar con la afiliación__ (desde que el medio de pago sea compatible con MercadoPagoV2).
-
-Para saber cómo definir condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
+En VTEX es posible integrarse con el proveedor de pagos MercadoPagoV2. A través de él, tu tienda podrá recibir pagos mediante métodos tradicionales, como: boleto, PIX, tarjetas de débito y crédito, así como a través de métodos exclusivos de Mercado Pago, como: MercadoPagoOff, MercadoPagoPro y MercadoPagoWallet.
+
+Para configurar MercadoPagoV2 sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __MercadoPagoV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta MercadoPagoV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor MercadoPagoV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Periodo de vencimiento__ del ticket, elija el número de días (contados desde la creación del boleto) que tendrá su cliente para realizar el pago.
+8. En __Nombre de la tienda__, ingrese el nombre de su empresa.Recuerde que esta es la información que se describirá en el campo Beneficiário en el boleto o en la factura de la tarjeta del cliente.
+9. En __Cuotas máximas__, escoja la cantidad máxima de cuotas enviadas a  Mercado Pago.
+10. En __Soporte 3DS 2.0__, seleccione "Sí" si desea habilitar la validación de seguridad 3DS. Para que este protocolo funcione correctamente, asegúrese de que la __Mercado Pago Payment app__ ya esté instalada en su tienda y que el campo __Binario__ (paso 14) esté seleccionado como __No__.
+11. En __Categoría principal de la tienda__, elija la categoría de la industria de su tienda.
+12. En __Categoría (tienda o producto) compartida por transacción__, selecciona si deseas compartir datos de tienda o categoría de producto con Mercado Pago en cada transacción.
+13. En la opción __Reembolso automático / manual__, elija si se reembolsará al cliente automáticamente o manualmente en caso de cancelación del pedido.
+14. En __Modo binario__, indicar si la tienda debe aceptar pagos pendientes. Seleccionar "Sí" indica que el proceso de aprobación del pago se produce instantáneamente y puede aprobarse o rechazarse. Seleccionar "No" define que el pago puede permanecer en estado "pendiente" (si requiere alguna acción por parte del comprador) o "en proceso" (si se requiere revisión manual).
+15. En __Métodos de pago excluidos__, describe los métodos de pago que no deseas utilizar a través de MercadoPagoV2 (opcional). Si opta por dejar este campo en blanco, todos los métodos de pago disponibles de MercadoPagoV2 estarán disponibles en su tienda.
+16. En __Tipos de pago excluidos__,  describe las banderas específicas de crédito y débito (Visa, Mastercard, etc) que no deseas utilizar a través de MercadoPagoV2 (opcional). Si opta por dejar este campo en blanco, todos los tipos de pago disponibles de MercadoPagoV2 estarán disponibles en su tienda.
+17. En __Modo de procesamiento__, escoja cómo quiere usar MercadoPagoV2: como subadquirente o gateway. Para más información, visite [¿Qué es un subadquirente?](https://help.vtex.com/es/tutorial/que-es-un-subadquirente--64aX6PeRQQ66O8uCqo0W4q) y [¿Qué es un gateway de pagos?](https://help.vtex.com/es/tutorial/que-es-un-gateway-de-pagos--2KH9Wdi7F6swOU4amECSOk). 
+18. En la opción __Integrator ID__, indique el código identificador del desarrollador o agencia que realiza la configuración de Mercado Pago.
+19. En la opción __Moneda__, elija si la moneda utilizada para el pago será "Local" (cada país) o "Dólar estadounidense" (USD).
+20. El campo __Merchant Account ID__ identifica la cuenta del merchant. No es necesario llenarlo.
+21. En __Plazo de captura de pagos aprobado__, seleccione la fecha límite deseada para la captura de pago.
+22. En __Fecha para cancelar compras de un carrito abandonado__, la cantidad de tiempo que se debe esperar hasta que los métodos de pago habilitados ya no estén disponibles para realizar la compra.
+23. Haga clic en __Guardar__.
+
+## Configurar condiciones de pago
+
+Para configurar los métodos de pago predeterminados a procesar por MercadoPagoV2, acceda a [Configurar condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
 
 ## Configurar métodos de pago únicos
 
diff --git a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
index 1e010b856..41c9f467a 100644
--- a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
@@ -36,18 +36,18 @@ Dicho esto, verifique el siguiente procedimiento:
 
 1. Acceda a su __cuenta de desarrollador__ Apple en `https://developer.apple.com/account/#/overview/`.
 2. Seleccione la opción __Certificates, ID & Profiles__.
-![AP1](https://images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
+![AP1](//images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
 3. Haga clic en __ Identifiers__.
- ![AP2](https://images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
+ ![AP2](//images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
 4. Al lado de Identifiers, haga clic en __botón azul +__.
-![AP3](https://images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
+![AP3](//images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
 5. Seleccione la opción __Merchant IDs__.
 6. Haga clic en el botón azul __Continue__.
-![AP4](https://images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
+![AP4](//images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
 7. Rellene el campo __Description__.
 8. Rellene el campo __Identifier__.
 9. Haga clic en el botón __Continue__.
-![AP5](https://images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
+![AP5](//images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
 
 De este modo, se creará el __Merchant ID__. 
 
@@ -62,14 +62,14 @@ En seguida, el administrador de la tienda puede enviarlo al sistema Apple Pay.
 Para comenzar esta etapa, continúe con las instrucciones:
 
 1. En el menú del lado izquierdo, seleccione __Certificates__.
-![AP6](https://images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
+![AP6](//images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
 2. Digite su __Merchant ID__ creado recientemente en la barra de búsqueda.
 3. Seleccione el __Merchant ID__ deseado.
-![AP7](https://images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
+![AP7](//images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
 4. En el ítem __ Apple Pay Payment Processing Certificate__, haga clic en el botón __Create Certificate__.
-![AP8](https://images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
+![AP8](//images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
 5. Asegúrese de que la pregunta *"Will payments associated with this Merchant ID be processed exclusively in China?"* esté marcada con __la opción default (No)__.
-![AP9](https://images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
+![AP9](//images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
 
 En seguida, será redirigido a una pantalla con instrucciones sobre la creación del CRS (Certificate Signing Request). 
 
@@ -82,9 +82,9 @@ Con el {{merchantID}}.csr. que recibió, finalice:
 1. Haga clic en __Choose File__.
 2. Seleccione el __archivo CSR__ deseado.
 3. Haga clic en el botón __Continue__.
-![AP10](https://images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
+![AP10](//images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
 4. Haga clic en __Download__.
-![AP11](https://images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
+![AP11](//images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
 5. Haga clic en __Done__.
 
 ## Registrando dominios en el Merchant ID
@@ -101,17 +101,17 @@ Finalmente, es necesario importar este archivo al sistema de VTEX a través de P
 Verifique las instrucciones:
 
 1. Digite el __Merchant ID__ creado recientemente en la barra de búsqueda.
-![AP12](https://images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
+![AP12](//images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
 2. Haga clic en el __Merchant ID__ deseado.
 3. En el módulo __Merchant Domains__, haga clic en el botón __Add Domain__.
-![AP13](https://images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
+![AP13](//images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
 4. Agregue el dominio en el campo __Enter the domain you wish to register__.
 5. Haga clic en __Save__.
 
 Ahora, para hacer upload del archivo `.txt` por medio de la API, prosiga con las instrucciones:   
 
 1. Haga clic en __Download__ y no realice ninguna alteración en el archivo.  
-![AP14](https://images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
+![AP14](//images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
 2. Abra el archivo `.txt` y __copie__ todo el contenido.
 
 En seguida, inicie una sesión en el Postman. Usted realizará una llamada vía POST para la CDN de VTEX:  
@@ -123,7 +123,7 @@ En seguida, inicie una sesión en el Postman. Usted realizará una llamada vía
 Al realizar la llamada *POST*, la respuesta debe informar que el certificado se guardará durante 60 minutos. Durante este tiempo, debe completar la validación del dominio.
 
 Ahora, regrese al sitio web de Apple. En la misma pantalla donde descargó el archivo `.txt`, haga clic en __Verify__.
-![AP15](https://images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
+![AP15](//images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
 
 Así, si el procedimiento se realiza correctamente, el dominio se registrará con el estado __Verified__. Si lo desea, puede repetir todo el proceso para registrar más dominios utilizando el botón __Add Domain__ en la sección __Merchant Domains__.
 
@@ -140,15 +140,15 @@ Atención: Recomendamos que la contraseña sea fácil de recordar, ya que se ing
 1. Acceda al módulo __Certificates, Identifiers & Profilers__.
 2. En el menú del lado izquierdo, haga clic en __Identifiers__.
 3. En la esquina superior derecha, filtre por __Merchant IDs__.
-![AP16](https://images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
+![AP16](//images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
 4. Seleccione el __Merchant Identifier__ deseado.
 5. Haga clic en __Create Certificate__.
-![AP17](https://images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
+![AP17](//images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
 6. Siga las __instrucciones__ que se muestran en la pantalla para crear un certificado. 
 7. Haga clic en el botón __Continue__.
-![AP18](https://images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
+![AP18](//images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
 8. Haga clic en __Download__.    
-![AP19](https://images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
+![AP19](//images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
 
 Ahora, cuando se descargué el archivo, haga doble clic para instalarlo en Keychain Access.
 
@@ -156,7 +156,7 @@ Luego, continúe con el procedimiento:
 
 1. Abra el __Keychain Access__.
 2. Localice el __certificado__ creado en el paso cuatro anterior.
-3. Haga clic derecho en el ícono __llave__. ![AP20](https://images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
+3. Haga clic derecho en el ícono __llave__. ![AP20](//images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
 4. Haga clic en __Export__.
 5. Nombre el __certificado__.
 6. Seleccione el formato de exportación __.p12__.
diff --git a/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md b/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md
index 220eed97f..71ca35aa3 100644
--- a/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md
+++ b/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Mundipagg Fraud Prevention'
 id: yFbysX42GW2wawu82q6QA
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-04-18T21:01:40.512Z
-updatedAt: 2023-03-29T00:39:20.112Z
-publishedAt: 2023-03-29T00:39:20.112Z
+updatedAt: 2024-03-18T18:40:56.708Z
+publishedAt: 2024-02-16T12:17:04.418Z
 firstPublishedAt: 2018-04-18T21:23:11.844Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-mundipagg-fraud-prevention
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Mundipagg ofrece una versión de su [gateway](/es/tutorial/que-es-un-gateway-de-pagos) con la funcionalidad de antifraude. El Mundipagg Fraud Prevention trae aún más seguridad para el procesamiento de compras hechas con boletos, transferencias bancarias y las principales banderas de tarjetas de crédito.
 
 Para configurar Mundipagg Fraud Prevention, siga los pasos abajo:
 
-## Configurar la afiliación de gateway Mundipagg Fraud Prevention
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Mundipagg Fraud Prevention__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Mundipagg Fraud Prevention__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene el campo __Merchant Key__ ("Llave de la tienda") con la clave registrada en Mundipagg. Se compone de 36 caracteres, entre letras, números y guiones.
 5. En __País__, elija el país de su tienda.
 6. El campo __Registro Url Post Notification em Mundipagg__ trae una dirección para configurar la recepción de notificaciones sobre el status del pago. En el link `https://{sellerhost}.vtexpayments.com.br/mundipagg/payment/statusnotification`, sustituya `{sellerhost}` por el nombre de su tienda. Entonces, envíe la URL final a Mundipagg para completar el registro.
diff --git a/docs/tutorials/es/setting-up-mundipagg-gateway.md b/docs/tutorials/es/setting-up-mundipagg-gateway.md
index 6279bdd91..df302be45 100644
--- a/docs/tutorials/es/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/es/setting-up-mundipagg-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Mundipagg'
 id: 6C9412jePCUMGguq0YWU8M
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T18:01:44.533Z
-updatedAt: 2023-03-29T00:36:17.690Z
-publishedAt: 2023-03-29T00:36:17.690Z
+updatedAt: 2024-03-18T18:39:56.272Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T20:58:03.675Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-mundipagg
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Mundipagg es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que procesa pagos hechos con boletos, transferencias bancarias y las principales banderas de tarjetas de crédito.
 
 Para configurar Mundipagg, siga estos pasos:
 
-## Configurar la afiliación de gateway Mundipagg
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Mundipagg__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Mundipagg__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene el campo __Merchant Key__ ("Llave de la tienda")con la clave registrada en Mundipagg. Se compone de 36 caracteres, entre letras, números y guiones.
 5. En __País__, elija el país de su tienda.
 6. El campo __Registro Url Post Notification en Mundipagg__ trae una dirección para configurar la recepción de notificaciones sobre el status de pago. En el enlace `https://{sellerhost}.vtexpayments.com.br/mundipagg/payment/statusnotification`, sustituya `{sellerhost}` por el nombre de su tienda. Entonces, envíe la URL final a Mundipagg para completar el registro.
diff --git a/docs/tutorials/es/setting-up-my-account.md b/docs/tutorials/es/setting-up-my-account.md
index b4908575a..2e96fccf0 100644
--- a/docs/tutorials/es/setting-up-my-account.md
+++ b/docs/tutorials/es/setting-up-my-account.md
@@ -3,8 +3,8 @@ title: 'Configuración de My Account'
 id: 23Ayv5D6b86UBnYfoXqZL1
 status: PUBLISHED
 createdAt: 2019-02-19T21:35:31.855Z
-updatedAt: 2021-05-24T18:07:48.662Z
-publishedAt: 2021-05-24T18:07:48.662Z
+updatedAt: 2023-12-21T14:12:18.587Z
+publishedAt: 2023-12-21T14:12:18.587Z
 firstPublishedAt: 2019-02-19T21:37:25.249Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: configuración-de-my-account
 subcategory: 1RWR7qSyaREbD5RfgCjdYG
 ---
 
+<div class = "alert alert-info">
+En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
+</div>
+
 El nuevo [My Account](https://help.vtex.com/es/tutorial/como-funciona-el-my-account--2BQ3GiqhqGJTXsWVuio3Xh) ya está instalado en todas las cuentas VTEX en un <strong>ambiente de prueba</strong>, permitiendo ajustes en la nueva página sin impactos en la experiencia de usuario.
 
 Esto quiere decir que My Account ya está disponible para que su tienda realice las personalizaciones necesarias, antes de la migración masiva del aplicativo para producción, a través del siguiente link:
diff --git a/docs/tutorials/es/setting-up-nexxpago-gateway.md b/docs/tutorials/es/setting-up-nexxpago-gateway.md
index 2eb6af52e..03057d3e0 100644
--- a/docs/tutorials/es/setting-up-nexxpago-gateway.md
+++ b/docs/tutorials/es/setting-up-nexxpago-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Nexxpago'
 id: 28Fgmof1WYEeAcM8MkOcWm
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T15:46:11.611Z
-updatedAt: 2023-03-29T01:08:32.601Z
-publishedAt: 2023-03-29T01:08:32.601Z
+updatedAt: 2024-03-18T18:58:03.614Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T16:05:40.588Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-nexxpago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Nexxpago es una empresa con certificación [PCI](/es/faq/que-es-el-pci-ssc) que ofrece diversas soluciones de pago. La principal de ellas es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que permite el procesamiento de pagos por medio de boletos bancarios y tarjetas de crédito.
 
 Para configurar Nexxpago, siga estos pasos:
 
-## Configurar la afiliación de gateway Nexxpago
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Nexxpago__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Nexxpago__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __External Service Url__ ("URL de servicio externo"), configure la URL externa que va a estar asociada a `/pvt/payments?an={AccountName}`.
 5. Rellene los campos de registro con los datos proporcionados por Nexxpago (campos _appKey_ y _appToken_).
 6. En __Implements Installments Service__ ("Servicio de implementacion de cuotas"), usted debe elegir si desea utilizar servicios externos de parcelación o lo que está configurado en el portal. Si elige la opción _yes_, el sistema utilizará la URL configurada en el campo __Installments Service Url__ ("URL de servicio para cuotas").
@@ -31,7 +32,10 @@ Para configurar Nexxpago, siga estos pasos:
 9. En __SoftDescriptor__ ("Descripcion"), indique el texto que va a aparecer para identificar las transacciones realizadas en su tienda.
 10. En el campo __Captura de seguridad anticipada__, escoja en cuánto tiempo desea que la captura sea realizada (después de la aprobación de la transacción y del análisis del antifraude). También es posible desactivar esta función.
 11. En __Usa Antifraude__, informe si desea usar un antifraude.
-12. Haga clic en __Guardar__.
+12. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Nexxpago, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
-## Configurar la condición de pago
-Después de seguir los pasos indicados, Nexxpago estará configurado en su tienda. Por lo tanto, cuando se registre una condición de pago, estará disponible en el campo __Procesar con la afiliación__ (siempre que el medio de pago sea compatible con Nexxpago). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+Después de seguir los pasos indicados, Nexxpago puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-nps-gateway.md b/docs/tutorials/es/setting-up-nps-gateway.md
index 545dc7539..0a2260380 100644
--- a/docs/tutorials/es/setting-up-nps-gateway.md
+++ b/docs/tutorials/es/setting-up-nps-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Ingenico ePayments (NPS)'
 id: 4DtjieyNQIQeI2O2kymEgq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T13:22:00.721Z
-updatedAt: 2023-03-29T01:15:32.462Z
-publishedAt: 2023-03-29T01:15:32.462Z
+updatedAt: 2024-03-18T19:00:20.612Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T15:09:45.694Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-gateway-nps
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Ingenico ePayments (NPS) es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) con fuerte actuación en América Latina y que permite que su tienda acepte diversas condiciones de pago.
 
 Para configurar NPS, siga estos pasos:
diff --git a/docs/tutorials/es/setting-up-pagar-me-gateway.md b/docs/tutorials/es/setting-up-pagar-me-gateway.md
index e9b1e3b33..68b547a87 100644
--- a/docs/tutorials/es/setting-up-pagar-me-gateway.md
+++ b/docs/tutorials/es/setting-up-pagar-me-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway Pagar.me'
 id: egFyDkXjfa80wkSkUWsmc
 status: PUBLISHED
 createdAt: 2018-04-10T17:54:18.410Z
-updatedAt: 2023-03-26T21:05:35.943Z
-publishedAt: 2023-03-26T21:05:35.943Z
+updatedAt: 2024-01-23T19:17:28.562Z
+publishedAt: 2024-01-23T19:17:28.562Z
 firstPublishedAt: 2018-04-10T18:10:52.337Z
 contentType: tutorial
 productTeam: Financial
@@ -19,10 +19,9 @@ Pagar.me es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que ofrece div
 
 Para configurar Pagar.me, siga estos pasos:
 
-## Configurar la afiliación de gateway Pagar.me
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __PagarMe__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Pagar.me__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __External Service Url__, configure la URL externa que va a estar asociada a `/pvt/payments?an={AccountName}`.
 5. Rellene los campos de registro con los datos proporcionados por Pagar.me (campos __appKey__ y __appToken__).
 6. En __Implements Installments Service__, usted debe elegir si desea utilizar servicios externos de parcelación o lo que está configurado en el portal. Si elige la opción _yes_, el sistema utilizará la URL configurada en el campo __Installments Service Url__.
diff --git a/docs/tutorials/es/setting-up-pagarmev2-gateway.md b/docs/tutorials/es/setting-up-pagarmev2-gateway.md
index 26556d3c9..63f1bd72b 100644
--- a/docs/tutorials/es/setting-up-pagarmev2-gateway.md
+++ b/docs/tutorials/es/setting-up-pagarmev2-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway PagarMeV2'
 id: 5TugxXNMOs0Ocyg4uqussM
 status: PUBLISHED
 createdAt: 2018-04-10T18:50:48.932Z
-updatedAt: 2023-03-26T21:04:07.182Z
-publishedAt: 2023-03-26T21:04:07.182Z
+updatedAt: 2024-01-23T19:19:58.174Z
+publishedAt: 2024-01-23T19:19:58.174Z
 firstPublishedAt: 2018-04-11T21:51:25.333Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,21 @@ legacySlug: configurar-gateway-pagarmev2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-PagarMeV2 es la versión más reciente de la [afiliación de gateway](https://help.vtex.com/es/tutorial/o-que-e-um-gateway-de-pagamentos) Pagar.me. Para configurarla, siga los pasos a continuación:
+En VTEX es posible procesar pagos con el proveedor PagarMe a través de integraciones V2 y V3.
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En Afiliaciones, haga clic en el botón verde «__+__».
-3. Busque y haga clic en __Pagarmev2__.
+<div class="alert alert-warning">
+Si quieres configurar la versión V3 de Pagarme en tu tienda, accede a <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-pagarmev3--5PMavdamrVijwIrHas9ndE">Configurar pago con PagarMeV3</a>.
+</div>
+
+Para configurar PagarMeV2, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagarMeV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos indicados con la siguiente información:<br>
 <ul>
-<li><b>Application Key</b> e <b>Application Token</b>: ingrese la información proporcionada por Pagar.me.</li>
+<li><b>Clave de aplicación</b> y <b>Token de aplicación
+</b>: ingrese la información proporcionada por Pagar.me.</li>
 <li><b>Captura de pago automática:</b>: seleccione una de las opciones a continuación:<br><br>
     <ul>
     	<li><b>Utilizar el comportamiento recomendado del procesador de pagos</b>: la captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
diff --git a/docs/tutorials/es/setting-up-pagbrasil-gateway.md b/docs/tutorials/es/setting-up-pagbrasil-gateway.md
index 94aaea68e..f78c448d5 100644
--- a/docs/tutorials/es/setting-up-pagbrasil-gateway.md
+++ b/docs/tutorials/es/setting-up-pagbrasil-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway PagBrasil'
 id: 2vzj6MkFRuKm4KQAOOmWaa
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-10T12:40:34.957Z
-updatedAt: 2023-03-29T01:00:48.970Z
-publishedAt: 2023-03-29T01:00:48.970Z
+updatedAt: 2024-03-18T19:02:31.069Z
+publishedAt: 
 firstPublishedAt: 2018-04-10T12:50:24.707Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-pagbrasil
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 PagBrasil es un gateway de pagos especializada en medios de pago brasileños, principalmente tarjetas de crédito y débito, transferencias en línea y boletos bancarios.
 
 Para configurar PagBrasil, siga los pasos abajo:
 
-## Configurar la afiliación de gateway PagBrasil
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __PagBrasil__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagBrasil__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __External Service Url__ ("URL de servicio externo"), configure la URL externa que va a estar asociada a `/pvt/payments?an={AccountName}`.
 5. Rellene los campos de registro con los datos proporcionados por PagBrasil (campos _appKey_ y _appToken_).
 6. En __Implements Installments Service__ ("Servicio de implementacion de cuotas"), usted debe elegir si desea utilizar servicios externos de parcelación o lo que está configurado en el portal. Si elige la opción _yes_, el sistema utilizará la URL configurada en el campo __Installments Service Url__ ("URL de servicio para cuotas").
diff --git a/docs/tutorials/es/setting-up-paghiper-gateway.md b/docs/tutorials/es/setting-up-paghiper-gateway.md
index 4698b9499..d89296e8c 100644
--- a/docs/tutorials/es/setting-up-paghiper-gateway.md
+++ b/docs/tutorials/es/setting-up-paghiper-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway PagHiper'
 id: I3KXAIIJG0oyyg4A4MykE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-09T22:06:11.621Z
-updatedAt: 2023-03-29T01:13:11.291Z
-publishedAt: 2023-03-29T01:13:11.291Z
+updatedAt: 2024-03-18T19:04:40.079Z
+publishedAt: 
 firstPublishedAt: 2018-04-09T22:43:35.309Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-paghiper
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 PagHiper es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que se dedica al procesamiento de compras realizadas por boletos bancarios.
 
 Para configurar PagHiper, siga los pasos abajo:
 
-## Configurar la afiliación de gateway Paghiper
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __PagHiper__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagHiper__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __External Service Url__, usted debe configurar la URL externa que va a estar asociada a `/pvt/payments?an={AccountName}`.
 5. Rellene los campos de registro con los datos proporcionados por PagHiper (campos _appKey_ y _appToken_).
 6. En __Implements Installments Service__, usted debe elegir si desea utilizar servicios externos de parcelación o el que está configurado en el portal. Si elige la opción _yes_, el sistema utilizará la URL configurada en el campo __Installments Service Url__.
diff --git a/docs/tutorials/es/setting-up-pagseguro-v3.md b/docs/tutorials/es/setting-up-pagseguro-v3.md
index 3f707b7f6..043fa4ba6 100644
--- a/docs/tutorials/es/setting-up-pagseguro-v3.md
+++ b/docs/tutorials/es/setting-up-pagseguro-v3.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar el PagSeguro V3'
+title: 'Configurar pago con PagBankV3'
 id: 5Noi1mUbBQ6CyqdeDQtWfw
 status: PUBLISHED
 createdAt: 2021-12-02T12:14:58.698Z
-updatedAt: 2023-03-23T15:40:31.170Z
-publishedAt: 2023-03-23T15:40:31.170Z
+updatedAt: 2024-03-14T18:59:12.645Z
+publishedAt: 2024-03-14T18:59:12.645Z
 firstPublishedAt: 2021-12-02T19:18:21.251Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,30 @@ legacySlug: configurar-el-pagseguro-v3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Si tiene una cuenta PagSeguro, puede configurar PagSeguroV3 en el gateway de VTEX para recibir pagos mediante: boleto, PIX, tarjetas de débito y crédito.
+En VTEX es posible la integración con el proveedor de pagos PagBankV3. A través de este proveedor, su tienda puede realizar ventas mediante boleto, PIX, tarjetas de débito y crédito.
 
-## Configurar afiliación de gateway PagseguroV3
+Para configurar PagBankV3, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el __botón “+”__.
-3. Haga clic en el conector __PagSeguroV3__.
-4. En __Click to authorize VTEX to make payments__, haga clic en __Autorizar__. En este momento, será redirigido a la página de PagSeguro, donde deberá acceder a sua cuenta, y autorizar la conexión de VTEX en su cuenta de PagSeguro.
-5. Después de autorizar, regresará automáticamente al Admin VTEX, y los campos __Application Key__, __Application Token__ y __Application Id__ fya estarán completados.
-6. Haga clic en __Salva__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagBankV3__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, haga clic en __Autorizar com OAuth__. En este punto, serás redirigido a la página de PagBank, donde deberás acceder a tu cuenta y autorizar la conexión de VTEX a tu cuenta de PagBank. Luego del proceso de autorización, regresará automáticamente al VTEX Admin.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagBankV3 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, en el campo __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+7. Si desea utilizar [Split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx) en su tienda, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
+8. En __Campos deL proveedor__, en el campo __Prazo para captura do pagamento__, seleccione el período deseado para capturar el pago.
+9. Haga clic en __Guardar__.
 
-## Configurar condición de pago
-Después de seguir los pasos indicados, PagSeguroV3 estará configurado en su tienda. Así, cuando vaya a registrar una condición de pago, va a estar disponible en el campo __Procesar con la afiliación__ (desde que el medio de pago sea compatible con PagSeguroV3).
+Para configurar los métodos de pago a procesar por PagBankV3, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
-Para saber cómo definir condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PagBankV3 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payment-with-paypal.md b/docs/tutorials/es/setting-up-payment-with-paypal.md
index bbff7966e..b67b18c44 100644
--- a/docs/tutorials/es/setting-up-payment-with-paypal.md
+++ b/docs/tutorials/es/setting-up-payment-with-paypal.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pago con PayPal'
 id: 4p3sD9u1moq2Aya2oc684w
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-21T17:15:53.516Z
-updatedAt: 2023-03-21T20:46:52.481Z
-publishedAt: 2023-03-21T20:46:52.481Z
+updatedAt: 2024-03-18T20:29:36.504Z
+publishedAt: 
 firstPublishedAt: 2018-02-21T17:54:19.079Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pago-con-paypal
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 En el gateway de VTEX, usted puede configurar el subadquirente de PayPal para recibir sus pagos. En esta modalidad, su cliente elige el pago de PayPal y realiza su autenticación en el ambiente de PayPal.
 
 Para realizar la configuración, siga los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-paymentez-gateway.md b/docs/tutorials/es/setting-up-paymentez-gateway.md
index 044dd0fea..b912d8c65 100644
--- a/docs/tutorials/es/setting-up-paymentez-gateway.md
+++ b/docs/tutorials/es/setting-up-paymentez-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Paymentez'
 id: 7zmH2WCtVuAoUUQWyU2qgO
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-28T17:47:41.909Z
-updatedAt: 2023-03-26T22:08:53.622Z
-publishedAt: 2023-03-26T22:08:53.622Z
+updatedAt: 2024-03-18T19:16:05.956Z
+publishedAt: 
 firstPublishedAt: 2018-03-28T18:18:57.206Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-paymentez
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Paymentez es un [gateway de pago](/es/tutorial/que-es-un-gateway-de-pagos) con [certificación PCI](/es/faq/que-es-el-pci-ssc) nivel 2 y tiene su actuación concentrada en América Latina.
 
 Para configurar Paymentez, siga estos pasos:
 
-## Configurar la afiliación de gateway Paymentez
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Paymentez__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Paymentez__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __External Service Url__, configure la URL externa que va a estar asociada a `/pvt/payments?an={AccountName}`.
 5. Rellene los campos de registro con los datos proporcionados por Paymentez (campos _appKey_ y _appToken_).
 6. En __Implements Installments Service__, usted debe elegir si desea utilizar servicios externos de parcelación o el que está configurado en el portal. Si elige la opción _yes_, el sistema utilizará la URL configurada en el campo __Installments Service Url__.
@@ -31,7 +32,10 @@ Para configurar Paymentez, siga estos pasos:
 9. En __SoftDescriptor__, indique el texto que va a aparecer para identificar las transacciones realizadas en su tienda.
 10. En el campo __Captura de seguridad anticipada__, escoja en cuánto tiempo desea que la captura sea realizada después de la aprobación de la transacción y del análisis del antifraude. También es posible desactivar esta función.
 11. En __¿Tiene un antifraude contratado con esa afiliación?__, informe si desea usar un antifraude.
-12. Haga clic en __Guardar__.
+12. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Paymentez, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
-## Configurar la condición de pago
-Después de seguir los pasos indicados arriba, Paymentez estará configurada en su tienda. Por lo tanto, cuando se registre una condición de pago, ella estará disponible en el campo __Procesar con la afiliación__ (siempre que el medio de pago sea compatible con Paymentez). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+Después de seguir los pasos indicados, Paymentez puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-55pay.md b/docs/tutorials/es/setting-up-payments-with-55pay.md
index 971f98b8d..24a458592 100644
--- a/docs/tutorials/es/setting-up-payments-with-55pay.md
+++ b/docs/tutorials/es/setting-up-payments-with-55pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con 55PAY'
 id: 4ktYG4reu5T6taEj2pKjvZ
 status: PUBLISHED
 createdAt: 2022-05-05T13:22:59.869Z
-updatedAt: 2023-03-26T21:43:11.110Z
-publishedAt: 2023-03-26T21:43:11.110Z
+updatedAt: 2024-01-23T18:31:36.516Z
+publishedAt: 2024-01-23T18:31:36.516Z
 firstPublishedAt: 2022-05-05T13:44:32.122Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-99pay.md b/docs/tutorials/es/setting-up-payments-with-99pay.md
index 43d3f3823..00ade9568 100644
--- a/docs/tutorials/es/setting-up-payments-with-99pay.md
+++ b/docs/tutorials/es/setting-up-payments-with-99pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con 99Pay'
 id: QIStxPsGb6LoIwFBfcTfb
 status: PUBLISHED
 createdAt: 2023-04-06T19:37:06.116Z
-updatedAt: 2023-04-06T19:41:32.060Z
-publishedAt: 2023-04-06T19:41:32.060Z
+updatedAt: 2024-01-23T18:31:10.050Z
+publishedAt: 2024-01-23T18:31:10.050Z
 firstPublishedAt: 2023-04-06T19:41:32.060Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-99pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos 99Pay. Con este conector, tu tienda puede realizar ventas a través de 99Pay.
+En VTEX es posible la integración con el proveedor de pagos 99Pay. Con este proveedor, tu tienda puede realizar ventas a través de 99Pay.
 
-Para configurar la afiliación 99Pay, siga los pasos a continuación:
+Para configurar 99Pay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __99Pay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __99Pay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__  con los datos proporcionados por 99Pay. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-aarin.md b/docs/tutorials/es/setting-up-payments-with-aarin.md
index 71dd22db9..aa9879daa 100644
--- a/docs/tutorials/es/setting-up-payments-with-aarin.md
+++ b/docs/tutorials/es/setting-up-payments-with-aarin.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Aarin'
 id: 2kVQVFqutbZYK3I6XBVgLp
 status: PUBLISHED
 createdAt: 2022-06-22T12:45:29.082Z
-updatedAt: 2023-03-26T21:42:40.807Z
-publishedAt: 2023-03-26T21:42:40.807Z
+updatedAt: 2024-01-23T18:32:06.337Z
+publishedAt: 2024-01-23T18:32:06.337Z
 firstPublishedAt: 2022-06-22T13:00:38.494Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-addi.md b/docs/tutorials/es/setting-up-payments-with-addi.md
index 07ee3c696..d888b5fd5 100644
--- a/docs/tutorials/es/setting-up-payments-with-addi.md
+++ b/docs/tutorials/es/setting-up-payments-with-addi.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Addi'
 id: 7FhMbT3hN2i5je74lqx6QI
 status: PUBLISHED
 createdAt: 2022-02-14T12:22:11.957Z
-updatedAt: 2023-03-27T12:46:46.989Z
-publishedAt: 2023-03-27T12:46:46.989Z
+updatedAt: 2024-01-23T18:29:23.380Z
+publishedAt: 2024-01-23T18:29:23.380Z
 firstPublishedAt: 2022-02-14T15:04:37.219Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-addi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Addi. Con este conector, tu tienda puede realizar ventas a plazos sin tarjeta de crédito.
+En VTEX es posible la integración con el proveedor de pagos Addi. Con este proveedor, tu tienda puede realizar ventas a plazos sin tarjeta de crédito.
 
-Para configurar la afiliación Addi, siga los pasos a continuación:
+Para configurar Addi, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en el conector __Addi__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Addi__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Addi.
 5. En __Country of Operation__, seleccione el país donde operará el conector.
 6. Haga clic en __Guardar__.
diff --git a/docs/tutorials/es/setting-up-payments-with-alignet.md b/docs/tutorials/es/setting-up-payments-with-alignet.md
index 0de6ba537..3a14751d7 100644
--- a/docs/tutorials/es/setting-up-payments-with-alignet.md
+++ b/docs/tutorials/es/setting-up-payments-with-alignet.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagos com Alignet'
 id: 4qfl6jgDyMGA0IuM0siEii
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-28T20:48:01.728Z
-updatedAt: 2023-03-29T01:04:08.516Z
-publishedAt: 2023-03-29T01:04:08.516Z
+updatedAt: 2024-03-18T17:48:35.669Z
+publishedAt: 
 firstPublishedAt: 2018-03-28T23:00:56.209Z
 contentType: tutorial
 productTeam: Financial
@@ -15,30 +15,32 @@ legacySlug: configurar-pagos-com-alignet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 En la plataforma VTEX, es posible configurar el [subadquirente](/es/tutorial/que-es-un-subadquirente) Alignet para recibir pagos en su tienda. En esta modalidad, el cliente escoge el __medio de pago__ Alignet y se redirige a la autenticación en el ambiente del subadquirente.
 
-Para realizar la configuración, siga los pasos abajo:
+Para configurar Alignet, siga los pasos abajo:
 
-## Configurar la afiliación de gateway Alignet
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Alignet__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Alignet__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __Acquirer__, elija el adquirente que se utilizará en la integración.
 5. Rellene los campos de registro con los datos proporcionados por Alignet (campos _Código Adquirente_, _CodigoComercio_, _CodigoMall_, _CodigoTerminal_ _ChavePrivadaAssinatura_, _ChavePrivadaCriptografia_, _ChavePublicaAssinaturaAlignet_ y _ChavePublicaCriptografiaAlignet_).
 6. En el campo __CodigoMoeda__, rellene con el código [ISO 4217](https://es.wikipedia.org/wiki/ISO_4217) de la moneda que se utilizará en los pagos.
 7. En __Idioma__ ("Lengua"), elija entre español e inglés.
 8. En el campo __Vector__, rellene la secuencia de hasta 16 caracteres (sólo letras y números) generada por su tienda.
-9. Haga clic en __Guardar__.
+9. Haga clic en `Guardar`.
 
 ## Configurar la condición de pago Alignet
+
 1. En los __Configuración__ del módulo Pagos, haga clic en la pestaña __Planes de pago__.
 2. Haga clic en el botón __+__.
 3. Haga clic en el medio de pago __Alignet__.
 4. Haga clic en el botón __Status__ para activar esta condición de pago.
 5. Si su tienda tiene un antifraude configurado, usted puede activarlo marcando la casilla __Usar Antifraude__.
 6. Si lo desea, también puede añadir una [condición especial de pago](/es/tutorial/condiciones-especiales).
-8. Haga clic en __Guardar__.
+8. Haga clic en `Guardar`.
 
 Después de seguir los pasos indicados arriba, Alignet aparecerá en el checkout de su tienda como una opción de pago. Después de hacer clic en __Finalizar Compra__, su cliente será redirigido para autenticación en el ambiente de Alignet. 
 
-Otra opción para habilitar esta condición de pago es utilizar el [conector Pay-me](/es/tutorial/configurar-gateway-pay-me).
+También puede habilitar esta condición de pago utilizando el [PayMee](https://help.vtex.com/es/tutorial/configurar-el-gateway-paymee--3fsilRdrBS6GOAy622soWy).
diff --git a/docs/tutorials/es/setting-up-payments-with-alignetv2.md b/docs/tutorials/es/setting-up-payments-with-alignetv2.md
new file mode 100644
index 000000000..e995d54a4
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-alignetv2.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pago con AlignetV2'
+id: 1rZU7cexTYdzB4SHWjr3eJ
+status: PUBLISHED
+createdAt: 2024-03-07T16:37:07.030Z
+updatedAt: 2024-03-07T16:56:11.973Z
+publishedAt: 2024-03-07T16:56:11.973Z
+firstPublishedAt: 2024-03-07T16:56:11.973Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-alignetv2
+locale: es
+legacySlug: configurar-pago-con-alignetv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos AlignetV2. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito.
+
+Para configurar AlignetV2 siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __AlignetV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta AlignetV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor AlignetV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en el nombre de la marca de tarjeta de crédito deseada.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, AlignetV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-ame-digital.md b/docs/tutorials/es/setting-up-payments-with-ame-digital.md
index 974f5ba73..0e6e166a5 100644
--- a/docs/tutorials/es/setting-up-payments-with-ame-digital.md
+++ b/docs/tutorials/es/setting-up-payments-with-ame-digital.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Ame Digital'
 id: 4oEhDjLM4uk95X8omwLEG2
 status: PUBLISHED
 createdAt: 2022-02-14T17:02:38.944Z
-updatedAt: 2023-03-26T21:42:08.346Z
-publishedAt: 2023-03-26T21:42:08.346Z
+updatedAt: 2024-01-23T18:28:00.633Z
+publishedAt: 2024-01-23T18:28:00.633Z
 firstPublishedAt: 2022-02-14T17:35:18.865Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-ame-digital
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Ame Digital. Con este conector, tu tienda puede realizar ventas en efectivo o en cuotas, con QR Code o link de pago. Además, tus clientes pueden tener acceso a cashback durante las compras.
+En VTEX es posible la integración con el proveedor de pagos Ame Digital. Con este proveedor, tu tienda puede realizar ventas en efectivo o en cuotas, con QR Code o link de pago. Además, tus clientes pueden tener acceso a cashback durante las compras.
 
-Para configurar la afiliación Ame Digital, siga los pasos a continuación:
+Para configurar Ame Digital, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en el conector __AmeDigital__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __AmeDigital__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Ame Digital.
 5. Haga clic en __Guardar__.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-apple-pay.md b/docs/tutorials/es/setting-up-payments-with-apple-pay.md
index 188060d06..ac342fa81 100644
--- a/docs/tutorials/es/setting-up-payments-with-apple-pay.md
+++ b/docs/tutorials/es/setting-up-payments-with-apple-pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagos con Apple Pay'
 id: 5L3NWMgvdKswWQa6eIc008
 status: PUBLISHED
 createdAt: 2018-04-12T20:38:42.521Z
-updatedAt: 2023-03-26T21:54:30.284Z
-publishedAt: 2023-03-26T21:54:30.284Z
+updatedAt: 2024-06-25T21:20:56.252Z
+publishedAt: 2024-06-25T21:20:56.252Z
 firstPublishedAt: 2018-05-23T19:26:11.000Z
 contentType: tutorial
 productTeam: Financial
@@ -24,40 +24,32 @@ Sus clientes pueden comprar con Apple Pay, la [cartera digital](/es/faq/que-es-u
   Actualmente, Apple Pay solo funciona en los sistemas operativos MacOs e IOS, y en el navegador Safari. Para obtener más información, vaya a <a href="https://support.apple.com/es-es/HT208531">Dispositivos compatibles con Apple Pay</a>.
 </div>
 
-Con los requisitos cumplidos, basta con seguir los pasos abajo para ofrecer esta condición de pago en su tienda:
+## Configurar proveedor de pago
 
-## Configurar la afiliación de gateway
-Ofrecer condiciones de pago a los clientes de su tienda depende de afiliaciones de gateway capaces de procesarlas. En la plataforma VTEX, las afiliaciones actualmente compatibles con el __Apple Pay__ son la __ERedeREST__ (integración de la adquirente Rede), __Adyen__ y __Stripe__.
+En primer lugar, debes configurar un proveedor en el Admin de tu tienda que procese transacciones con Apple Pay, como [Adyen](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3--7xAz67E2Eg63LWCQNjVdwv) y [Stripe](https://help.vtex.com/es/tutorial/configurar-la-afiliacion-stripe--fwF2wk2FQKrODrWWkvSLO).
 
-Estos artículos muestran cómo configurar [ERedeREST](/es/tutorial/configurar-adquirente-rede-con-erederest), [Adyen](/es/tutorial/como-configurar-el-gateway-adyen-en-vtex) y [Stripe](https://help.vtex.com/es/tutorial/configuring-stripe-gateway-affiliation--fwF2wk2FQKrODrWWkvSLO).   
+Para consultar todas las opciones de proveedores disponibles para este método de pago, acceda a la lista como se describe en el Paso 5 de la sección [Configurar el pago con Apple Pay](#configurar-el-pago-con-apple-pay).
 
-Pero recuerde: es fundamental [registrar el Merchant ID en Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay) antes de configurar la afiliación de gateway.
+<div class="alerta alerta-advertencia">
+  Antes de comenzar a configurar el proveedor, debe <a href="register your Merchant ID with Apple Pay">registrar su Merchant ID con Apple Pay</a>.
+</div>
 
-## Descargar e instalar la aplicación de VTEX App Store
-1. En el menú lateral del Admin, haga clic en __Apps__.
-2. Acceda al enlace __VTEX App Store__ o utilice la URL `https://apps.vtex.com/?an={{AccountName}}` directo en el navegador, cambiando `{{AccountName}}` por el nombre de la tienda en que desea ofrecer el Apple Pay.
-3. Busque la aplicación __Apple Pay__ y haga clic en __Get__.
-4. Se dirigirá a una pantalla de revisión de pedido. Compruebe los datos y haga clic en el botón __Confirm order and begin installation__.
-5. Usted llegará a la pantalla de instalación. Allí, puede revisar los permisos de la aplicación e iniciar la descarga (haciendo clic en __Instalar__).
-6. La aplicación se instalará en su workspace, pero usted tendrá que rellenar el __Merchant ID__ (en el campo __Merchant Identifier__) para aplicar en su tienda.
-7. Haga clic en __Guardar__.
+## Configurar el pago con Apple Pay
 
-## Configurar la condición de pago de Apple Pay
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
 2. Haga clic en la pestaña __Planes de pago__ y, a continuación, en el botón __+__.
 3. Seleccione el medio de pago __Apple Pay__.
-4. Haga clic en el botón __Status__ para activar esta condición de pago.
-5. En el campo __Procesar con la afiliación__, seleccione la opción que se va a utilizar para procesar los pagos.
-6. Si hay un antifraude configurado en su tienda, usted puede activarlo para esta condición de pago marcando la casilla __Usar Antifraude__.
+4. Haga clic en el botón `Status` para activar esta condición de pago.
+5. En el campo __Procesar con proveedor__, seleccione el proveedor que se va a utilizar para procesar los pagos.
+6. Si hay un antifraude configurado en su tienda, usted puede activarlo para esta condición de pago marcando la casilla __Utilizar antifraude__.
 7. Elija si desea que los pagos se realicen en efectivo o parcelados.
 8. Si lo desea, también puede optar por una [condición especial de pago](/es/tutorial/condiciones-especiales).
-9. Haga clic en __Guardar__.
+9. Haga clic en `Guardar`.
 
-Después de seguir los pasos indicados, __Apple Pay__ aparecerá en el checkout de su tienda como una opción de pago para sus clientes.
+Después de seguir los pasos indicados, Apple Pay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
 
 ### Artículos relacionados
-- [Configurar adquirente Rede con ERedeRest](/es/tutorial/configurar-adquirente-rede-con-erederest)
-- [Configurar el gateway Adyen en VTEX](/es/tutorial/como-configurar-el-gateway-adyen-en-vtex)
+
 - [Configurar Merchant ID en Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay)
-- [Configurar condiciones especiales de pago](/es/tutorial/condiciones-especiales)
-- [¿Qué es una cartera digital (e-wallet)?](/es/faq/que-es-una-cartera-digital)
+- [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456)
+- [¿Qué es una cartera digital (ewallet)?](https://help.vtex.com/es/tutorial/que-es-una-cartera-digital--4v5wcOe4A0SiaimWM2cU60)
diff --git a/docs/tutorials/es/setting-up-payments-with-appmax.md b/docs/tutorials/es/setting-up-payments-with-appmax.md
new file mode 100644
index 000000000..20b6d3470
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-appmax.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pago con Appmax'
+id: 6IIo8dyXKtdmXykBOhYmi0
+status: PUBLISHED
+createdAt: 2023-12-18T14:21:48.704Z
+updatedAt: 2024-01-23T18:26:05.083Z
+publishedAt: 2024-01-23T18:26:05.083Z
+firstPublishedAt: 2023-12-18T14:32:23.030Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-appmax
+locale: es
+legacySlug: configurar-pago-con-appmax
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Appmax. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito, boleto bancario y Pix (método de pago brasileño).
+
+Para configurar Appmax, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Appmax__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Click to authorize VTEX to make payments__, haga clic en __Autorizar__. En este momento, será redirigido a la página de Appmax, donde deberá acceder a sua cuenta, y autorizar la conexión de VTEX en su cuenta de Appmax.
+5. Después de autorizar, regresará automáticamente al Admin VTEX, y los campos __Application Key__, __Application Token__ y __Application Id__ fya estarán completados.
+6. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Appmax, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Appmax puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-argonpay.md b/docs/tutorials/es/setting-up-payments-with-argonpay.md
new file mode 100644
index 000000000..ce541b694
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-argonpay.md
@@ -0,0 +1,50 @@
+---
+title: 'Configurar pago con argonPAY'
+id: 6Pktml6MJpdc7dNvJ4zwzI
+status: PUBLISHED
+createdAt: 2023-12-18T14:51:00.261Z
+updatedAt: 2023-12-18T15:02:08.524Z
+publishedAt: 2023-12-18T15:02:08.524Z
+firstPublishedAt: 2023-12-18T15:02:08.524Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-argonpay
+locale: es
+legacySlug: configurar-pago-con-argonpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos argonPAY. Con este conector, su tienda puede realizar ventas a través de diferentes de argonPAY.
+
+Para configurar el proveedor argonPAY, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda__ > __Pago__ > __Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Afiliaciones__, haga clic en el botón `+`.
+3. Haga clic en el conector __ArgonPay__.
+4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por el argonPAY.
+5. En el campo __Captura automática de pago__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza El Comportamiento Recomendado Por El Procesador de Pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Imediatamente: Captura Automática Al Autorizar El Pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Imediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Captura automática al autorizar el pago").</li>
+   		<li><b>Programado: Establece Cuándo Se Realizará La Captura Automática</b>: al seleccionar esta opción, se mostrará el campo <b>Periodo de tiempo programado en horas para la captura automática</b>, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.</li>        
+   		<li><b>Desactivado: No Capturado Automáticamente</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+
+6.  En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+7. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda__ > __Pago__ > __Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Elige la condición de pago __ArgonPay__.
+4. Rellene el campo __Nombre de la regla__ con un nombre de su elección para su identificación.
+5. Active la condición en el campo __Status__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, argonPAY puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-astropay.md b/docs/tutorials/es/setting-up-payments-with-astropay.md
index c802ff023..b3785d7c8 100644
--- a/docs/tutorials/es/setting-up-payments-with-astropay.md
+++ b/docs/tutorials/es/setting-up-payments-with-astropay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Astropay'
 id: 1A5hrnp3wLTlkUkYLlielB
 status: PUBLISHED
 createdAt: 2022-08-15T18:20:38.640Z
-updatedAt: 2023-03-26T21:21:01.948Z
-publishedAt: 2023-03-26T21:21:01.948Z
+updatedAt: 2024-01-25T19:07:17.927Z
+publishedAt: 2024-01-25T19:07:17.927Z
 firstPublishedAt: 2022-08-15T18:39:51.774Z
 contentType: tutorial
 productTeam: Financial
@@ -15,9 +15,9 @@ legacySlug: configurar-pago-con-astropay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Astropay. Con este conector, tu tienda puede realizar ventas a través de Astropay.
+En VTEX es posible la integración con el proveedor de pagos Astropay. Con este proveedor, tu tienda puede realizar ventas a través de Astropay.
 
-Para configurar la afiliación Astropay, siga los pasos a continuación:
+Para configurar Astropay, siga los pasos a continuación:
 
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
diff --git a/docs/tutorials/es/setting-up-payments-with-bamboo.md b/docs/tutorials/es/setting-up-payments-with-bamboo.md
index 5433e00b8..91621e475 100644
--- a/docs/tutorials/es/setting-up-payments-with-bamboo.md
+++ b/docs/tutorials/es/setting-up-payments-with-bamboo.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Bamboo'
 id: 33TDZBp1wmgzJdiZtvu1xY
 status: PUBLISHED
 createdAt: 2022-08-12T20:06:37.117Z
-updatedAt: 2022-08-12T20:13:31.863Z
-publishedAt: 2022-08-12T20:13:31.863Z
+updatedAt: 2024-01-25T19:18:30.701Z
+publishedAt: 2024-01-25T19:18:30.701Z
 firstPublishedAt: 2022-08-12T20:13:31.863Z
 contentType: tutorial
 productTeam: Financial
@@ -15,9 +15,9 @@ legacySlug: configurar-pago-con-bamboo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Bamboo. Con este conector, su tienda puede realizar ventas a través de tarjetas de credito, debito, private y cobranded labels, y boletos.
+En VTEX es posible la integración con el proveedor de pagos Bamboo. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de credito, debito, private y cobranded labels, y boletos.
 
-Para configurar tu afiliación Bamboo, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para configurar Bamboo, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
 
diff --git a/docs/tutorials/es/setting-up-payments-with-bancolombia-bnpl.md b/docs/tutorials/es/setting-up-payments-with-bancolombia-bnpl.md
index a14318052..95e42a70a 100644
--- a/docs/tutorials/es/setting-up-payments-with-bancolombia-bnpl.md
+++ b/docs/tutorials/es/setting-up-payments-with-bancolombia-bnpl.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Bancolombia BNPL'
 id: 16iFxjwsOPwmBwmjhb17WN
 status: PUBLISHED
 createdAt: 2023-03-30T16:25:46.370Z
-updatedAt: 2023-03-30T17:24:01.279Z
-publishedAt: 2023-03-30T17:24:01.279Z
+updatedAt: 2024-01-24T21:15:43.651Z
+publishedAt: 2024-01-24T21:15:43.651Z
 firstPublishedAt: 2023-03-30T17:24:01.279Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-bancolombia-bnpl
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Bancolombia BNPL. Con este conector, su tienda puede realizar ventas a través de Bancolombia BNPL (Buy Now Pay Later).
+En VTEX es posible la integración con el proveedor de pagos Bancolombia BNPL. Con este proveedor, su tienda puede realizar ventas a través de Bancolombia BNPL (Buy Now Pay Later).
 
-Para configurar la afiliación Bancolombia BNPL, siga los pasos a continuación:
+Para configurar Bancolombia BNPL, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __BancolombiaBNPL__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __BancolombiaBNPL__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta Bancolombia.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-banqi.md b/docs/tutorials/es/setting-up-payments-with-banqi.md
index cdb050bfc..c463482f5 100644
--- a/docs/tutorials/es/setting-up-payments-with-banqi.md
+++ b/docs/tutorials/es/setting-up-payments-with-banqi.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con banQi'
 id: 41rk9E7JUmCl683MJ9p52P
 status: PUBLISHED
 createdAt: 2023-03-30T12:31:49.459Z
-updatedAt: 2023-03-30T19:51:34.281Z
-publishedAt: 2023-03-30T19:51:34.281Z
+updatedAt: 2024-01-23T18:25:15.982Z
+publishedAt: 2024-01-23T18:25:15.982Z
 firstPublishedAt: 2023-03-30T13:04:03.008Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,19 @@ legacySlug: configurar-pago-con-banqi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos banQi. Con este conector, su tienda puede realizar ventas a través del libro de pago banQi.
+En VTEX es posible la integración con el proveedor de pagos banQi. Con este proveedor, su tienda puede realizar ventas a través del libro de pago banQi.
 
-Para configurar la afiliación banQi, siga los pasos a continuación:
+Para configurar banQi, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __banQi__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __banQi__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta banQi.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
 
 ## Configurar condición de pago
+
 1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
 3. Haga clic en __carnê banQi__.
diff --git a/docs/tutorials/es/setting-up-payments-with-bitfy.md b/docs/tutorials/es/setting-up-payments-with-bitfy.md
index c99fe60c1..e8da43967 100644
--- a/docs/tutorials/es/setting-up-payments-with-bitfy.md
+++ b/docs/tutorials/es/setting-up-payments-with-bitfy.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Bitfy'
 id: 2PSTfW4PsMh19K9y3DkQec
 status: PUBLISHED
 createdAt: 2022-08-15T17:30:29.886Z
-updatedAt: 2023-03-24T15:05:15.559Z
-publishedAt: 2023-03-24T15:05:15.559Z
+updatedAt: 2024-01-23T18:24:11.153Z
+publishedAt: 2024-01-23T18:24:11.153Z
 firstPublishedAt: 2022-08-15T17:41:45.501Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-bitfy
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Bitfy. Con este conector, tu tienda puede realizar ventas a través de Bitfy.
+En VTEX es posible la integración con el proveedor de pagos Bitfy. Con este proveedor, tu tienda puede realizar ventas a través de Bitfy.
 
-Para configurar la afiliación Bitfy, siga los pasos a continuación:
+Para configurar Bitfy, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __BitfyBr__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __BitfyBr__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Haga clic en el botón __Install App__ y siga las instrucciones de instalación.
 5. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Bitfy.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-bluepay.md b/docs/tutorials/es/setting-up-payments-with-bluepay.md
index 108b2f7d0..845e25de1 100644
--- a/docs/tutorials/es/setting-up-payments-with-bluepay.md
+++ b/docs/tutorials/es/setting-up-payments-with-bluepay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con BluePay'
 id: 26gzpfmEiwgpE8yhkaFS16
 status: PUBLISHED
 createdAt: 2023-04-03T14:55:51.576Z
-updatedAt: 2023-04-03T15:04:37.336Z
-publishedAt: 2023-04-03T15:04:37.336Z
+updatedAt: 2024-07-24T13:29:26.700Z
+publishedAt: 2024-07-24T13:29:26.700Z
 firstPublishedAt: 2023-04-03T15:04:37.336Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-bluepay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos BluePay. Con este conector, su tienda puede realizar ventas a través de PIX.
+En VTEX es posible la integración con el proveedor de pagos BluePay. Con este proveedor, su tienda puede realizar ventas a través de PIX.
 
-Para configurar la afiliación BluePay, siga los pasos a continuación:
+Para configurar BluePay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __BluePay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __BluePay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta BluePay.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
@@ -33,6 +33,6 @@ Para configurar la afiliación BluePay, siga los pasos a continuación:
 4. En __Procesar con afiliación__, seleccione el conector __bluepaypartnerbr-bluepay-v0__.
 5. Active la condición en el campo __Status__.
 6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
-8. Haga clic en `Guardar`.
+7. Haga clic en `Guardar`.
 
 Después de seguir los pasos indicados, BluePay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-boletoflex.md b/docs/tutorials/es/setting-up-payments-with-boletoflex.md
index 9938f2860..0978d7bc4 100644
--- a/docs/tutorials/es/setting-up-payments-with-boletoflex.md
+++ b/docs/tutorials/es/setting-up-payments-with-boletoflex.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con BoletoFlex'
 id: 3ikLbJGXMI6bkAm6YiglOx
 status: PUBLISHED
 createdAt: 2022-01-10T17:36:39.512Z
-updatedAt: 2023-03-22T19:10:38.069Z
-publishedAt: 2023-03-22T19:10:38.069Z
+updatedAt: 2024-01-23T15:50:34.329Z
+publishedAt: 2024-01-23T15:50:34.329Z
 firstPublishedAt: 2022-01-10T20:19:23.317Z
 contentType: tutorial
 productTeam: Financial
@@ -18,9 +18,10 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 BoletoFlex es un medio de pago donde los usuarios pueden pagar sus compras en cuotas utilizando el boleto, con tasas de interés predeterminadas y sin necesidad de utilizar una tarjeta de crédito.
 
 ## Configurar afiliación de gateway BoletoFlex
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en el conector __BoletoFlex__.
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __BoletoFlex__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por BoletoFlex.
 5. Haga clic en __Guardar__.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-bom-pra-credito.md b/docs/tutorials/es/setting-up-payments-with-bom-pra-credito.md
index ca8d96f1d..72e6fc0b7 100644
--- a/docs/tutorials/es/setting-up-payments-with-bom-pra-credito.md
+++ b/docs/tutorials/es/setting-up-payments-with-bom-pra-credito.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Bom Pra Credito'
 id: 2arjSmF9ksov6IXTEMaGkl
 status: PUBLISHED
 createdAt: 2022-08-10T19:47:21.251Z
-updatedAt: 2023-03-26T21:24:13.881Z
-publishedAt: 2023-03-26T21:24:13.881Z
+updatedAt: 2024-01-23T18:19:59.534Z
+publishedAt: 2024-01-23T18:19:59.534Z
 firstPublishedAt: 2022-08-10T19:52:22.782Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-braintree.md b/docs/tutorials/es/setting-up-payments-with-braintree.md
new file mode 100644
index 000000000..718fa09c7
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-braintree.md
@@ -0,0 +1,49 @@
+---
+title: 'Configurar pago con Braintree'
+id: 3Is3N2MmTldXPa2FtiV8xy
+status: PUBLISHED
+createdAt: 2022-08-11T12:01:04.231Z
+updatedAt: 2024-03-18T11:55:35.217Z
+publishedAt: 2024-03-18T11:55:35.217Z
+firstPublishedAt: 2022-08-11T12:27:01.656Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-braintree
+locale: es
+legacySlug: configurar-pago-con-braintree
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Braintree.
+A través de este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y débito.
+
+Para configurar Braintree-DCC, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Braintree-DCC__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Braintree.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Braintree en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. En __Campos del proveedor__, seleccione o complete los campos a continuación con la información de su cuenta Braintree:
+   - __Change Order Single Charge__
+   - __PayPal Secret (opcional)__
+   - __PayPal Client ID (opcional)__
+   - __PayPal Merchant ID (opcional)__
+   - __Merchant Account Id (opcional)__
+   - __Merchant Id (Braintree)__
+9. Haga clic en `Guardar`.
+
+Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
+
+Después de seguir los pasos indicados, Braintree-DCC puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-braspagv2.md b/docs/tutorials/es/setting-up-payments-with-braspagv2.md
index 825b92291..8c0cf5b7f 100644
--- a/docs/tutorials/es/setting-up-payments-with-braspagv2.md
+++ b/docs/tutorials/es/setting-up-payments-with-braspagv2.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pago con BraspagV2'
 id: 6gaw7zu9wlItgjfDVndRPn
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-01-20T19:41:22.154Z
-updatedAt: 2023-03-22T19:03:11.096Z
-publishedAt: 2023-03-22T19:03:11.096Z
+updatedAt: 2023-09-19T14:27:03.358Z
+publishedAt: 
 firstPublishedAt: 2022-01-21T16:38:10.049Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-brinks-cash-ecommerce.md b/docs/tutorials/es/setting-up-payments-with-brinks-cash-ecommerce.md
index 56322d07c..6d2e23e20 100644
--- a/docs/tutorials/es/setting-up-payments-with-brinks-cash-ecommerce.md
+++ b/docs/tutorials/es/setting-up-payments-with-brinks-cash-ecommerce.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Brinks Cash Ecommerce'
 id: 5Zoex6NXtyzUFOCctdGjlZ
 status: PUBLISHED
 createdAt: 2022-08-15T17:49:34.660Z
-updatedAt: 2023-03-26T21:22:32.556Z
-publishedAt: 2023-03-26T21:22:32.556Z
+updatedAt: 2024-01-24T21:18:37.297Z
+publishedAt: 2024-01-24T21:18:37.297Z
 firstPublishedAt: 2022-08-15T18:04:15.733Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-brinks-cash-ecommerce
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Brinks Cash Ecommerce. Con este conector, tu tienda puede realizar ventas a través de Recaudo Efectivo en Colombia.
+En VTEX es posible la integración con el proveedor de pagos Brinks Cash Ecommerce. Con este proveedor, tu tienda puede realizar ventas a través de Recaudo Efectivo en Colombia.
 
-Para configurar la afiliación Brinks Cash Ecommerce, siga los pasos a continuación:
+Para configurar Brinks Cash Ecommerce, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Brinks Cash Ecommerce__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Brinks Cash Ecommerce__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Haga clic en el botón __Install App__ y siga las instrucciones de instalación.
 5. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Brinks Cash Ecommerce.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md b/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md
new file mode 100644
index 000000000..a4390ef37
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md
@@ -0,0 +1,67 @@
+---
+title: 'Configurar pago con CieloEcommerce'
+id: 6zuELBqEo0QzApbU4l7L4
+status: PUBLISHED
+createdAt: 2023-09-18T14:07:22.540Z
+updatedAt: 2024-03-27T17:13:40.793Z
+publishedAt: 2024-03-27T17:13:40.793Z
+firstPublishedAt: 2023-09-18T15:29:57.321Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-cieloecommerce
+locale: es
+legacySlug: configurar-pago-con-cieloecommerce
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el CieloEcommerce. Con esta integración, su tienda puede rrealizar ventas a través de tarjetas de credito, debito, private y cobranded labels, boletos, PIX, entre otros. 
+
+Para configurar CieloEcommerce, siga los siguientes pasos:
+
+<blockquote><ui>1. En el Admin VTEX, accede a <b>Configuración de la tienda > Pago > Proveedores</b>, o escribe <b>Proveedores</b> en la barra de búsqueda en la parte superior de la página.</ui>
+
+<blockquote><ui>2. En la pantalla de proveedores, haga clic en el botón <b>Nuevo proveedor</b>.</ui>
+
+<blockquote><ui>3. Escriba el nombre <b>CieloEcommerce</b> en la barra de búsqueda y haga clic en el nombre del proveedor.</ui>
+
+<blockquote><ui>4. En <b>Autorización del proveedor</b>, rellene los campos de registro <b>Clave de aplicación</b> y <b>Token de aplicación</b> con los <b>MerchantID</b> y <b>MerchantKey</b> proporcionados por su cuenta CieloEcommerce.</ui>
+
+<blockquote><ui>5. Si desea modificar el nombre de identificación que se mostrará para el proveedor CieloEcommerce en la pantalla VTEX Admin, ingrese la información en el campo <b>Nombre</b> en <b>Información general</b>.</ui>
+
+<blockquote><ui>6. En <b>Control de pago</b>, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en <b>Activar modo de prueba</b>.</ui>
+
+<blockquote><ui>7. Si desea utilizar <a href="https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx">Split de pagos</a> en su tienda, seleccione la opción <b>Activar split de cobros y enviar destinatarios de pago</b> e indique el <b>Responsable de cargos de procesamiento de pagos</b> y el <b>Responsable de contracargos</b> (marketplace, sellers o marketplace y sellers).</ui>
+
+<blockquote><ui>8. En <b>Integration</b>, seleccione si el conector se utilizará como <b>Adquirencia</b> o <b>Gateway</b>.</ui>
+
+<blockquote><ui>9. En <b>Provider</b>, seleccione el adquiriente que se utilizará con el conector CieloEcommerce.</ui>
+
+<blockquote><ui>10. En <b>IsSplit</b>, elija si la opción de split estará disponible.</ui>
+
+<blockquote><ui>11. En <b>UseMpi</b>, elija si autenticarán las transacciones (3DS 2.0). Este campo es obligatorio para el tipo de pago débito. Si selecciona "True", vaya al Paso 12. Si selecciona "False", vaya al Paso 13.</ui>
+
+<blockquote><ui>12. Rellene los campos <b>MpiClientId</b>, <b>MpiClientSecret</b>, <b>MpiMerchantName</b>, <b>MpiMCC</b> y <b>MpiEstablishmentCode</b> con tus datos de acceso a Mpi.</ui>
+
+<blockquote><ui>13. En <b>SoftDescriptor</b>, indicar la información que se mostrará para identificar la transacción realizada en su tienda.</ui>
+
+<blockquote><ui>14. En <b>AntifraudProvider</b>, seleccione el proveedor antifraude que desea utilizar con CieloEcommerce.</ui>
+
+<blockquote><div class="alert alert-warning">
+  Consulte con Cielo si las opciones antifraude en CieloEcommerce ya están disponibles para su uso. Si aún está en desarrollo, ambos campos descritos en el paso 15 deben dejarse en blanco. Para obtener más información sobre el uso de opciones antifraude en su tienda, visite <a href="https://help.vtex.com/es/tutorial/como-configurar-antifraude">Configurar el antifraude</a>.
+  </div></blockquote>
+<br>
+
+<blockquote><ui>15. En <b>Antifraud</b> y <b>AntifraudSequenceCriteria</b>, seleccione las opciones según información de CieloEcommerce antifraude. Consulta con CieloEcommerce si el antifraude ya está disponible para su uso, si aún está en desarrollo debes dejar ambos campos en blanco.</ui>
+
+<blockquote><ui>16. Em <b>Captura</b>, seleccione el período en el que se debe solicitar la captura de pago. El horario estándar se realizará cuatro días después de la autorización.</ui>
+
+<blockquote><ui>17. Seleccione los campos <b>UseVerifyCard</b>, <b>AcceptInternationalCard</b>, <b>AcceptPrePaidCard</b>, <b>SaveCard</b> y <b>CancelRefundType</b> según su configuración en CieloEcommerce.</ui>
+
+<blockquote><ui>18. Haga clic en <b>Guardar</b>.</ui>
+
+Para configurar los métodos de pago a procesar por CieloEcommerce, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, CieloEcommerce puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-cielov4.md b/docs/tutorials/es/setting-up-payments-with-cielov4.md
index cabe65c71..c534f52ea 100644
--- a/docs/tutorials/es/setting-up-payments-with-cielov4.md
+++ b/docs/tutorials/es/setting-up-payments-with-cielov4.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pago con CieloV4'
 id: 7M2CqJxprwpDtbgLZHBoiI
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-07-20T14:25:28.188Z
-updatedAt: 2023-03-26T21:25:12.482Z
-publishedAt: 2023-03-26T21:25:12.482Z
+updatedAt: 2023-09-19T14:27:43.425Z
+publishedAt: 
 firstPublishedAt: 2022-07-20T17:07:25.186Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-conekta.md b/docs/tutorials/es/setting-up-payments-with-conekta.md
index 21e17b3d2..c82496f07 100644
--- a/docs/tutorials/es/setting-up-payments-with-conekta.md
+++ b/docs/tutorials/es/setting-up-payments-with-conekta.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Conekta'
 id: 7kiAD3SlnABF75xLSL3eSA
 status: PUBLISHED
 createdAt: 2022-08-11T12:41:42.110Z
-updatedAt: 2023-03-26T21:16:15.989Z
-publishedAt: 2023-03-26T21:16:15.989Z
+updatedAt: 2024-01-25T17:54:14.697Z
+publishedAt: 2024-01-25T17:54:14.697Z
 firstPublishedAt: 2022-08-11T12:54:43.579Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-conekta
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Conekta. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito,  débito, OXXO y pagarés.
+En VTEX es posible la integración con el proveedor de pagos Conekta. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito,  débito, OXXO y pagarés.
 
-Para configurar la afiliación Conekta, siga los pasos a continuación:
+Para configurar Conekta, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Conekta__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Conekta__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Complete los campos debajo de la información de su cuenta Conekta:
    - __Application Key__
    - __Application Token__
@@ -33,6 +33,8 @@ Para configurar la afiliación Conekta, siga los pasos a continuación:
    - __Metadata 5__ 
 5. Haga clic en `Guardar`.
 
-Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete).
+Para configurar los métodos de pago a procesar por Conekta, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
 Después de seguir los pasos indicados, Conekta puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-crecoscorp.md b/docs/tutorials/es/setting-up-payments-with-crecoscorp.md
index 9831926f2..4a78c9d2c 100644
--- a/docs/tutorials/es/setting-up-payments-with-crecoscorp.md
+++ b/docs/tutorials/es/setting-up-payments-with-crecoscorp.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con CrecosCorp'
 id: 2NNAhG7ugxXhyk7U45hIeZ
 status: PUBLISHED
 createdAt: 2022-08-15T18:54:07.978Z
-updatedAt: 2022-08-15T18:59:46.828Z
-publishedAt: 2022-08-15T18:59:46.828Z
+updatedAt: 2024-01-25T17:37:02.016Z
+publishedAt: 2024-01-25T17:37:02.016Z
 firstPublishedAt: 2022-08-15T18:59:46.828Z
 contentType: tutorial
 productTeam: Financial
@@ -15,9 +15,9 @@ legacySlug: configurar-pago-con-crecoscorp
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos CrecosCorp. Con este conector, tu tienda puede realizar ventas a través de tarjetas private labels.
+En VTEX es posible la integración con el proveedor de pagos CrecosCorp. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas private labels.
 
-Para configurar tu afiliación CrecosCorp, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para configurar CrecosCorp, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 Para configurar el pago con tarjetas private labels, acceda a [Configurar pagos con Private Label](https://help.vtex.com/es/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4#).
 
diff --git a/docs/tutorials/es/setting-up-payments-with-credimarcas.md b/docs/tutorials/es/setting-up-payments-with-credimarcas.md
new file mode 100644
index 000000000..815115af5
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-credimarcas.md
@@ -0,0 +1,60 @@
+---
+title: 'Configurar pago con Credimarcas'
+id: 78855lTT6A1vX2wFURmxV
+status: PUBLISHED
+createdAt: 2023-12-18T13:12:50.542Z
+updatedAt: 2023-12-18T14:09:15.538Z
+publishedAt: 2023-12-18T14:09:15.538Z
+firstPublishedAt: 2023-12-18T14:09:15.538Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-credimarcas
+locale: es
+legacySlug: configurar-pago-con-credimarcas
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Credimarcas. Con este conector, tu tienda puede realizar ventas a través de pagarés y tarjetas private labels.
+
+Para configurar la afiliación Credimarcas, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
+3. Haga clic en el conector __credimarcas__.
+4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Credimarcas. 
+5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
+
+    - __Utiliza El Comportamiento Recomendado Por El Procesador De Pagos__: la captura de pagos no ocurre automáticamente. En esta opción, el proveedor de pago indica si el pago ha sido autorizado y puede determinar o recomendar un número de días para la captura a partir de la autorización del pago.
+    - __Inmediatamente: Captura Automática Al Autorizar El Pago__: la captura se realiza automáticamente inmediatamente después de que se autoriza el pago, incluso si la transacción requiere un análisis antifraude.
+    - __Inmediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude__: la captura se realiza automáticamente inmediatamente después de la autorización del pago y el análisis antifraude. Si desea utilizar esta opción y no hay que realizar un análisis antifraude, el sistema seguirá el mismo flujo que la opción __Inmediatamente: Captura Automática Al Autorizar El Pagamento__.
+    - __Programado: Establece Cuándo Se Realizará La Captura Automática__: al seleccionar esta opción, se mostrará el campo __Periodo de tiempo programado en horas para la captura automática__, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.
+    - __Desactivado: No Capturado Automáticamente__: la captura se produce sólo cuando se factura el pedido. Si desea utilizar esta opción, es importante prestar atención al momento de la facturación, ya que si el pedido se factura por un período mayor al acordado con el proveedor para capturar el pago, la transacción puede cancelarse.
+
+<ui>  6. En <b>Type Payment</b>, seleccione si el pago se realizará a través de "Payment App" o "Redirect".</ui>
+
+<ui>  7. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón <b>Instalar aplicación</b> y siga las instrucciones de instalación.</ui>
+
+<ui>  8. Haga clic en <b>Guardar.</b></ui>
+
+## Configurar Pagaré
+
+<div class="alert alert-warning">
+  <p>Si aún no has configurado el pagaré como método de pago en otros conectores de tu tienda, accede a <a href="https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ">Configurar pagos con Pagaré</a>.</p>
+</div>
+
+Para utilizar Credimarcas con pagarés, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. En __Pago personalizado__, haga clic en el botón correspondiente al nombre utilizado para el método de pago del pagaré previamente configurado).
+4. Active la condición en el campo __Status__.
+5. En __Procesar con afiliación__, seleccione __confepartnerco-credimarcas-v0__.
+6. Si lo desea, también puede configurar [condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+7. Haga clic en `Guardar`.
+
+## Configurar Private label
+
+Para utilizar Credimarcas con tarjetas private labels, acceda a [Configurar pagos con Private Label](https://help.vtex.com/es/tutorial/configurar-pagos-con-private-label--428FgVdSGQUeAOoogkaIw4).
+
+Después de seguir los pasos indicados, Credimarcas puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-credit-key.md b/docs/tutorials/es/setting-up-payments-with-credit-key.md
index 03a39b36f..8ae05875e 100644
--- a/docs/tutorials/es/setting-up-payments-with-credit-key.md
+++ b/docs/tutorials/es/setting-up-payments-with-credit-key.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Credit Key'
 id: 4TtmhhkcXQYnkaCPUa9adB
 status: PUBLISHED
 createdAt: 2023-04-20T14:33:42.988Z
-updatedAt: 2023-04-20T14:51:31.849Z
-publishedAt: 2023-04-20T14:51:31.849Z
+updatedAt: 2024-01-25T17:48:48.188Z
+publishedAt: 2024-01-25T17:48:48.188Z
 firstPublishedAt: 2023-04-20T14:51:31.849Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-credit-key
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Credit Key. Con este conector, tu tienda puede realizar ventas a través de Credit Key.
+En VTEX es posible la integración con el proveedor de pagos Credit Key. Con este proveedor, tu tienda puede realizar ventas a través de Credit Key.
 
 Para configurar la afiliación Credit Key, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __CreditKey__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __CreditKey__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__  con los datos proporcionados por Credit Key. 
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón __Instalar aplicación__ y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-culqi.md b/docs/tutorials/es/setting-up-payments-with-culqi.md
new file mode 100644
index 000000000..342415723
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-culqi.md
@@ -0,0 +1,58 @@
+---
+title: 'Configurar pago con Culqi'
+id: 6LUOpYBpg48XSL8X0Le6e3
+status: PUBLISHED
+createdAt: 2023-11-16T13:31:38.132Z
+updatedAt: 2024-01-25T19:01:02.616Z
+publishedAt: 2024-01-25T19:01:02.616Z
+firstPublishedAt: 2023-11-16T14:54:41.647Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-culqi
+locale: es
+legacySlug: configurar-pago-con-culqi
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Culqi. Con este proveedor, su tienda puede realizar ventas a través de diferentes de Culqi.
+
+Para configurar Culqi, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Culqi__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__ y __Public key__ con los datos proporcionados por el Culqi.
+5. En el campo __Captura automática de pago__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza El Comportamiento Recomendado Por El Procesador de Pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Imediatamente: Captura Automática Al Autorizar El Pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Imediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Captura automática al autorizar el pago").</li>
+   		<li><b>Programado: Establece Cuándo Se Realizará La Captura Automática</b>: al seleccionar esta opción, se mostrará el campo <b>Periodo de tiempo programado en horas para la captura automática</b>, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.</li>        
+   		<li><b>Desactivado: No Capturado Automáticamente</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+6. En __Aceptar tarjetas de crédito__, seleccione si desea aceptar tarjetas de crédito como medio de pago.
+7. En __Aceptar YAPE__, seleccione si deseas aceptar [YAPE](https://www.yape.com.pe/) como medio de pago.
+8. En __Aceptar billeteras móviles__, seleccione si desea aceptar billeteras digitales como medio de pago.
+9. En __Aceptar banca móvil o internet__, Seleccione si desea aceptar pagos a través de dispositivos móviles y banca por Internet.
+10. En __Aceptar agentes y bodegas__, seleccione si desea aceptar pagos a través de agentes y bodegas.
+11. En __Aceptar cuotéalo BCP__, seleccione si desea aceptar pagos en cuotas vía [cuotéalo BCP](https://www.viabcp.com/cuotealo).
+12. En __Tiempo de vencimiento del pago__, seleccione el período (en días) para que venzan los pagos.
+13. En los campos __URL de logo__, __Tema elegido__, __RSA Id__, __Llave pública RSA__, __Usuario Webhook__ y __Password Webhook__, ingrese la información proporcionada por Culqi.
+14. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+15. Haga clic en `Salvar`.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda__ > __Pago__ > __Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Elige la condición de pago __Culqi__.
+4. Rellene el campo __Nombre de la regla__ con un nombre de su elección para su identificación.
+5. Active la condición en el campo __Status__.
+6. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+7. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Culqi puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-dapp.md b/docs/tutorials/es/setting-up-payments-with-dapp.md
new file mode 100644
index 000000000..88f5a6c29
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-dapp.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pago con Dapp'
+id: 1p0FGViQcgCinPyi0GNXYM
+status: PUBLISHED
+createdAt: 2023-09-08T17:59:03.453Z
+updatedAt: 2024-01-25T18:09:29.307Z
+publishedAt: 2024-01-25T18:09:29.307Z
+firstPublishedAt: 2023-09-08T18:08:01.746Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-dapp
+locale: es
+legacySlug: configurar-pago-con-dapp
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Dapp. Con este proveedor, su tienda puede realizar ventas a través de Dapp.
+
+Para configurar Dapp, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Dapp__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Token__, __Application Token__, __Clave 1 - Dapp__, y __Clave 2 - Dapp__ con los datos proporcionados por su cuenta Dapp.
+5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Dapp__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Dapp puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-deuna.md b/docs/tutorials/es/setting-up-payments-with-deuna.md
new file mode 100644
index 000000000..85fe163e3
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-deuna.md
@@ -0,0 +1,48 @@
+---
+title: 'Configurar pago con Deuna'
+id: 5Y4BfCdbQWraZAyoSm0Zzr
+status: PUBLISHED
+createdAt: 2023-04-06T18:37:58.919Z
+updatedAt: 2024-01-23T18:11:08.945Z
+publishedAt: 2024-01-23T18:11:08.945Z
+firstPublishedAt: 2023-04-06T18:42:52.173Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-deuna
+locale: es
+legacySlug: configurar-pago-con-deuna
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Deuna. Con este proveedor, tu tienda puede realizar ventas a través de Deuna.
+
+Para configurar Deuna, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __DEUNA__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Deuna. 
+5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
+
+    - __Utiliza El Comportamiento Recomendado Por El Procesador De Pagos__: la captura de pagos no ocurre automáticamente. En esta opción, el proveedor de pago indica si el pago ha sido autorizado y puede determinar o recomendar un número de días para la captura a partir de la autorización del pago.
+    - __Inmediatamente: Captura Automática Al Autorizar El Pago__: la captura se realiza automáticamente inmediatamente después de que se autoriza el pago, incluso si la transacción requiere un análisis antifraude.
+    - __Inmediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude__: la captura se realiza automáticamente inmediatamente después de la autorización del pago y el análisis antifraude. Si desea utilizar esta opción y no hay que realizar un análisis antifraude, el sistema seguirá el mismo flujo que la opción __Inmediatamente: Captura Automática Al Autorizar El Pagamento__.
+    - __Programado: Establece Cuándo Se Realizará La Captura Automática__: al seleccionar esta opción, se mostrará el campo __Periodo de tiempo programado en horas para la captura automática__, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.
+    - __Desactivado: No Capturado Automáticamente__: la captura se produce sólo cuando se factura el pedido. Si desea utilizar esta opción, es importante prestar atención al momento de la facturación, ya que si el pedido se factura por un período mayor al acordado con el proveedor para capturar el pago, la transacción puede cancelarse.
+
+<ui>  6. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón <b>Instalar aplicación</b> y siga las instrucciones de instalación.</ui>
+
+<ui>  7. Haga clic en <b>Guardar.</b></ui>
+
+## Configurar la condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en el método de pago __DEUNA__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si lo desea, también puede configurar [condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Deuna puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-digital-river-v2.md b/docs/tutorials/es/setting-up-payments-with-digital-river-v2.md
index 21f9ceef0..2e81f8454 100644
--- a/docs/tutorials/es/setting-up-payments-with-digital-river-v2.md
+++ b/docs/tutorials/es/setting-up-payments-with-digital-river-v2.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Digital River V2'
 id: 5dlXHutd9Ik6vtN3WP7GRP
 status: PUBLISHED
 createdAt: 2022-02-17T12:11:27.726Z
-updatedAt: 2023-03-26T21:59:25.157Z
-publishedAt: 2023-03-26T21:59:25.157Z
+updatedAt: 2024-01-24T17:19:19.577Z
+publishedAt: 2024-01-24T17:19:19.577Z
 firstPublishedAt: 2022-02-17T13:44:17.095Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-pago-con-digital-river-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Digital River V2. Con este conector, su tienda puede realizar ventas a través de diferentes [métodos de pagos](https://www.digitalriver.com/payment-method-guide/).
+En VTEX es posible la integración con el proveedor de pagos Digital River V2. Con este proveedor, su tienda puede realizar ventas a través de diferentes [métodos de pagos](https://www.digitalriver.com/payment-method-guide/).
 
-Para configurar la afiliación Digital River V2, siga los pasos a continuación:
+Para configurar Digital River V2, siga los pasos a continuación:
 
-<ui>1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.</ui>
+<ui>1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Proveedores**, o escribe **Proveedores** en la barra de búsqueda en la parte superior de la página.</ui>
 
-<ui>2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.</ui>
+<ui>2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.</ui>
 
-<ui>3. Haga clic en el conector __DigitalRiverV2__.</ui>
+<ui>3. Escriba el nombre __DigitalRiverV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.</ui>
 
 <ui>4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Digital River V2.</ui>
 
diff --git a/docs/tutorials/es/setting-up-payments-with-dlocal-payments.md b/docs/tutorials/es/setting-up-payments-with-dlocal-payments.md
index 5915fa4df..429de82c8 100644
--- a/docs/tutorials/es/setting-up-payments-with-dlocal-payments.md
+++ b/docs/tutorials/es/setting-up-payments-with-dlocal-payments.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con DLocal Payments'
 id: 50DpZAd6td8oJaAIzHfQB5
 status: PUBLISHED
 createdAt: 2023-04-03T13:40:15.432Z
-updatedAt: 2023-04-03T14:03:12.910Z
-publishedAt: 2023-04-03T14:03:12.910Z
+updatedAt: 2024-01-23T18:09:56.316Z
+publishedAt: 2024-01-23T18:09:56.316Z
 firstPublishedAt: 2023-04-03T14:03:12.910Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-dlocal-payments
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos DLocal Payments. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito/débito y boletos bancarios.
+En VTEX es posible la integración con el proveedor de pagos DLocal Payments. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito/débito y boletos bancarios.
 
-Para configurar la afiliación DLocal Payments, siga los pasos a continuación:
+Para configurar DLocal Payments, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __DLocalPayments__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __DLocalPayments__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por DLocal Payments. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-dock.md b/docs/tutorials/es/setting-up-payments-with-dock.md
index 594d76ffd..7805de076 100644
--- a/docs/tutorials/es/setting-up-payments-with-dock.md
+++ b/docs/tutorials/es/setting-up-payments-with-dock.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Dock'
 id: 3Y0tLnXjBcG9qxHwAHGbHn
 status: PUBLISHED
 createdAt: 2022-07-19T19:58:56.608Z
-updatedAt: 2023-03-26T21:25:49.936Z
-publishedAt: 2023-03-26T21:25:49.936Z
+updatedAt: 2024-01-23T18:08:45.414Z
+publishedAt: 2024-01-23T18:08:45.414Z
 firstPublishedAt: 2022-07-19T20:12:07.212Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-e-sitef.md b/docs/tutorials/es/setting-up-payments-with-e-sitef.md
new file mode 100644
index 000000000..357cc4ddc
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-e-sitef.md
@@ -0,0 +1,48 @@
+---
+title: 'Configurar pago con e-Sitef'
+id: 6UEi0QAlU6BXz5RgWj34Ac
+status: PUBLISHED
+createdAt: 2021-12-06T14:51:20.250Z
+updatedAt: 2024-03-14T16:59:21.753Z
+publishedAt: 2024-03-14T16:59:21.753Z
+firstPublishedAt: 2021-12-06T17:37:55.667Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-e-sitef
+locale: es
+legacySlug: configurar-pago-con-e-sitef
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos e-Sitef. Con este proveedor, su tienda puede realizar ventas a través tarjetas de credito, debito, private y cobranded, y PIX.
+
+Para configurar e-Sitef, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __ESITEF__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por EVO Payments.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor EVO Payments en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. En el campo __Captura antecipada (em horas)__, elija cuánto tiempo desea que se realice la captura (después de que se apruebe la transacción). También puede desactivar la función.
+9. En __Alterar tempo máximo para captura automática (em dias)__, complete el período máximo de días en los que debe tener lugar la captura automática.
+10. En __Soft Descriptor__, puede ingresar una string personalizada (caracteres) que se imprimirá en la factura del cliente.
+11. En __Habilitar Pré-autorização__, seleccione si desea que las compras realizadas con tarjeta de crédito tengan el monto reservado (captura preautorizada después de la aprobación de la transacción).
+12. En el campo __Captura antecipada após anti-fraude (em horas)__, elija durante cuánto tiempo desea que se lleve a cabo la captura (después del análisis contra el fraude). También puede desactivar la función.
+13. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por e-Sitef, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, e-Sitef puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-easypay-marketplace.md b/docs/tutorials/es/setting-up-payments-with-easypay-marketplace.md
new file mode 100644
index 000000000..0b17f668f
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-easypay-marketplace.md
@@ -0,0 +1,18 @@
+---
+title: 'Configurar pago con easypay marketplace'
+id: 7EbImm3pJ8xCVRNxF06chN
+status: DRAFT
+createdAt: 2023-09-18T19:52:45.357Z
+updatedAt: 2023-09-19T12:04:40.833Z
+publishedAt: 
+firstPublishedAt: 2023-09-19T00:11:57.369Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-easypay-marketplace
+locale: es
+legacySlug: configurar-pago-con-easypay-marketplace
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Contenido bajo traducción.
diff --git a/docs/tutorials/es/setting-up-payments-with-easypay-seller.md b/docs/tutorials/es/setting-up-payments-with-easypay-seller.md
new file mode 100644
index 000000000..dabcc7020
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-easypay-seller.md
@@ -0,0 +1,51 @@
+---
+title: 'Configurar pago con easypay seller'
+id: 5mYMCM1tiRiZO6PozuUncE
+status: PUBLISHED
+createdAt: 2023-09-19T00:16:47.408Z
+updatedAt: 2023-09-28T11:36:30.237Z
+publishedAt: 2023-09-28T11:36:30.237Z
+firstPublishedAt: 2023-09-19T00:26:38.480Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-easypay-seller
+locale: es
+legacySlug: configurar-pago-con-seller
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX, los sellers pueden integrar sus productos en un marketplace integrado con el proveedor de servicios de pago easypay. A través de este conector, tu tienda puede vender utilizando easypay, MB Way y Multibanco.
+
+Para utilizar la afiliación easypay en tu marketplace, es necesario:
+
+- [Instalar la aplicación easypay seller account](#instalar-la-aplicacion-easypay-seller-account)
+- [Configurar la aplicación easypay seller account](#configurar-la-aplicacion-easypay-seller-account)
+
+<div class="alert alert-warning" role="alert">Si deseas configurar easypay para un contexto distinto al de seller, consulta los artículos <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-easypay--3xJQqjMIn0ARDI1HcwK88J">Configurar pago con easypay</a> o <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configurar pago con easypay marketplace</a>.</div>
+
+## Instalar la aplicación easypay seller account
+
+Para instalar o app Easypay Seller Account, siga os passos abaixo:
+
+1. En [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), ejecuta el comando `vtex login nombredelacuenta` para iniciar sesión.
+2. Instala la aplicación easypay ingresando el comando `vtex install easypaypartnerpt.easypay-seller`. 
+
+## Configurar la aplicación easypay seller account
+
+Después de instalar la aplicación easypay seller account, debes configurarla. Para acceder a la pantalla de configuración, sigue estos pasos:
+
+<blockquote><ui>1. En el Admin VTEX, ve a <b>Hub de extensiones > Gestión de aplicaciones</b>, o ingresa <b>Gestión de aplicaciones</b> en la barra de búsqueda de la parte superior de la página.</ui>
+
+<blockquote><ui>2. Busca la aplicación <b>Easypay Seller Account</b> y haz clic en <b>Configuración</b>.</ui>
+
+<blockquote><ui>3. En la pantalla <b>Easypay Seller Account</b>, rellena los siguientes campos::</ui>
+
+<blockquote><ui>- <b>VTEX Marketplace Account</b>: URL de la cuenta VTEX a la que estás vinculado. Ejemplo: https://{nombre-de-tu-cuenta}.myvtex.com/admin</ui> 
+
+<blockquote><ui>- <b>Easypay Account UID</b>: identificación de la cuenta seller en la que se abonarán los valores de la compra de productos adquiridos en la tienda. Para obtener esta información, accede al <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la esquina superior de la pantalla y, a continuación, en la cuenta deseada. Copia y guarda la información <b>Account UID</b>.</ui> 
+
+![easypay_pt_18](//images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/e9218fcccf92ed76e45024aa1c4c2285/easypay_pt_18.PNG)
+
+<blockquote><ui>4. Haz clic en <b>Guardar</b>.</ui>
+
diff --git a/docs/tutorials/es/setting-up-payments-with-easypay.md b/docs/tutorials/es/setting-up-payments-with-easypay.md
new file mode 100644
index 000000000..af54e40ef
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-easypay.md
@@ -0,0 +1,210 @@
+---
+title: 'Configurar pago con easypay'
+id: 3xJQqjMIn0ARDI1HcwK88J
+status: PUBLISHED
+createdAt: 2023-09-18T16:48:21.184Z
+updatedAt: 2024-06-17T15:38:51.146Z
+publishedAt: 2024-06-17T15:38:51.146Z
+firstPublishedAt: 2023-09-18T18:53:57.235Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-easypay
+locale: es
+legacySlug: configurar-pago-con-easypay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX, puedes realizar la integración con el proveedor de servicios de pago easypay. A través de este proveedor, tu tienda puede vender utilizando easypay, MB Way y Multibanco.
+
+Para utilizar easypay, debes:
+
+- [Instalar la aplicación easypay](#instalar-la-aplicacion-easypay)
+- [Configurar la aplicación easypay](#configurar-la-aplicacion-easypay)
+- [Configurar el webhook de easypay](#configurar-el-webhook-de-easypay)
+- [Configurar la afiliación de easypay](#configurar-la-afiliacion-de-easypay)
+- [Configurar el pago con Apple Pay en easypay (opcional)](#configurar-el-pago-con-apple-pay-en-easypay-opcional)    
+
+<div class="alert alert-warning" role="alert">Si eres marketplace o seller, consulta los artículos <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configurar pago con easypay en marketplace</a> o <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-easypay-seller--5mYMCM1tiRiZO6PozuUncE">Configurar pago con easypay seller account</a>.</div>
+
+## Instalar la aplicación easypay
+
+Para instalar la aplicación easypay, sigue los pasos que se indican a continuación:
+
+1. En [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), ejecuta el comando `vtex login nombredelacuenta` para iniciar sesión.
+2. Instala la aplicación easypay ingresando el comando `vtex install easypaypartnerpt.payment-provider-easypay`. 
+
+## Configurar la aplicación easypay
+
+Una vez instalada la aplicación easypay, debes configurarla. Para acceder a la pantalla de configuración, sigue estos pasos:
+
+1. En el Admin VTEX, accede a __Hub de extensiones > Gestión de aplicaciones__, o ingresa __Gestión de aplicaciones__ en la barra de búsqueda en la parte superior de la página. 
+2. Busca la aplicación __Easypay Payment Provider__ y haz clic en __Configuración__.
+
+La información de configuración se divide en cuatro secciones:
+
+- [Credenciales de easypay (obligatorio)](#Credenciales-de-easypay)
+- [Pago (obligatorio)](#pago)
+- [Personalización del checkout de easypay (opcional)](#personalizacion-del-checkout-de-easypay)
+- [Modo sandbox](#modo-sandbox)
+
+![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+
+<div class="alert alert-warning" role="alert">Debes realizar la configuración en <a href="https://backoffice.easypay.pt/">el entorno easypay</a>. El control de estas configuraciones es responsabilidad de easypay, por lo tanto, VTEX no garantiza que los pasos a continuación estén siempre actualizados. Utiliza este documento como referencia y consulta tu cuenta en el <a href="https://backoffice.easypay.pt/">entorno de easypay</a> para obtener información actualizada.</div>
+
+### Credenciales de easypay
+
+La información solicitada en esta sección es obligatoria.
+
+__Key ID y Key Value__: valor e ID de la clave easypay.
+
+<blockquote><ui>1. En el <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la parte superior izquierda de la pantalla, y en el ícono de la flecha que señala la cuenta deseada.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+<blockquote><ui>2. Accede a <b>Web Services > Configuración API 2.0 > Keys</b>.</ui>
+
+![easypay_es_3](//images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/b52af6fe6df6694a8ee073bd0561167f/easypay_en_3.png)
+
+<blockquote><ui>3. Copia y guarda la información <b>ID</b> y <b>Key</b>.</ui>
+
+![easypay_es_4](//images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/57f61df73ca3ea38e4cb3d9234e5e3c6/easypay_en_4.png)
+
+__Merchant account UID__: identificación de la cuenta del comerciante en la que se abonarán los valores de la compra de productos adquiridos en la tienda. Si no dispones de una cuenta comerciante independiente, puedes utilizar el "Account UID" de la cuenta donde recibirás los pagos.
+
+<blockquote><ui>1. En el <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la esquina superior izquierda de la pantalla y, a continuación, en la cuenta "COMERCIANTE 1", haz clic en la flecha.</ui>
+
+![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+
+<blockquote><ui>2. Copia y guarda la información del <b>Account UID</b>.</ui>
+
+![easypay_es_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/ca21af021e53fe89b50f0f650ecb0db1/easypay_en_6.png)
+
+__Margin account UID__: identificación de la cuenta de margen.
+
+<div class="alert alert-info" role="alert">Este campo solo debe rellenarse cuando la tienda es un marketplace y realiza split de pagos. Para más información, consulta el artículo <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configurar pago con easypay en marketplaces</a>.</div>
+
+__Refund account ID e Refund account key__: si no existe una cuenta específica para reembolso, el valor de __Key ID__ deberá rellenarse en el campo __Refund account ID__, y el valor de __Key value__ en __Refund account key__.
+
+### Pago
+
+En esta sección, debes indicar si tu tienda utilizará pagos asíncronos, síncronos o ambos. Accede a la documentación de easypay para consultar los [medios de pagos](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) disponibles y sus respectivas [siglas](https://docs.quality-utility.aws.easypay.pt/checkout/reference) de identificación.
+
+![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+
+__Tipos de pago asíncronos aceptados__: medios de pago asíncronos disponibles para el cliente. Ingresa solamente las siglas de los tipos de asíncronos, separadas por comas, sin puntos ni espacios.
+
+Ejemplo:
+
+| Correcto | Incorrecto |
+| ---------------- | ---------------- |
+| mb,dd,vi,sc | mb, dd, vi, sc |
+
+<div class="alert alert-warning" role="alert">Si se rellena este campo, también será obligatorio rellenar el campo <b>Días para que expiren los pagos asíncronos</b>.</div>
+
+__Tipos de pago síncronos aceptados__: medios de pago síncronos disponibles para el cliente. Ingresa solamente las siglas de los tipos de pago síncronos, separados por comas, sin puntos ni espacios.
+
+Ejemplo:
+
+| Correcto | Incorrecto |
+| ---------------- | ---------------- |
+| cc,mbw,uf | cc, mbw, uf |
+
+__Días de expiración de los pagos asíncronos__: tiempo de vencimiento (en días) de los pagos asíncronos. Ingresa solo el número de días deseados. 
+
+Ejemplo:
+
+| Correcto | Incorrecto |
+| ---------------- | ---------------- |
+| 10 | 10 días, Dic o 10/05/2023 |
+
+### Personalización del checkout de easypay
+
+easypay tiene un diseño de checkout nativo configurado en la aplicación, como se muestra a continuación:
+
+![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+
+Si deseas realizar algún tipo de personalización en el checkout nativo de easypay, rellena uno o más campos de esta sección:
+
+- __Checkout logo URL__: ogotipo que debe mostrarse en el checkout de easypay. Ingresa el link con la dirección de la imagen que deseas utilizar.
+- __Checkout background color__: color del fondo. Ingresa el código HEX del color deseado. Predeterminado nativo: #ffffff.
+- __Checkout accent color__: color de los elementos destacados, botones predeterminados y bordes de los inputs. Ingresa el código HEX del color deseado. Predeterminado nativo: #0d71f9.
+- __Checkout error color__: color de los mensajes de error. Ingresa el código HEX del color deseado. Predeterminado nativo: #ff151f.
+- __Checkout input background color__: color de fondo de los inputs. Ingresa el código HEX del color deseado. Predeterminado nativo: transparente.
+- __Checkout input border color__: color del borde de los inputs. Ingresa el código HEX del color deseado. Predeterminado nativo: el mismo color utilizado en __accent color__.
+- __Checkout input border radius__: permite definir el redondeado de los bordes de los inputs. Ingresa el valor deseado en píxeles (solo números). Predeterminado nativo: 50 píxeles.
+
+Ejemplo:
+
+| Correcto | Incorrecto |
+| ---------------- | ---------------- |
+| 35 | 35px |
+
+- __Checkout button background color__: color de fondo de los botones. Ingresa el código HEX del color deseado. Predeterminado nativo: el mismo color utilizado en __accent color__.
+- __Checkout button border radius__: permite definir el redondeado de los bordes de los botones. Ingresa el valor deseado en píxeles (solo números). Predeterminado nativo: 50 píxeles.
+
+Ejemplo:
+
+| Correcto | Incorrecto |
+| ---------------- | ---------------- |
+| 30 | 30px |
+
+- __Checkout button box shadow__: opción que permite activar o desactivar la sombra de los botones.
+- __Checkout font family__: fuentes utilizadas en textos. Ingresa el _generic family name_, _web safe font_ o link de la fuente. Predeterminado nativo: Overpass. Ejemplo correcto: sans-serif, verdana, ou https://fonts.gstatic.com/s/overpass/v12/qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PPbM5qKl8Kuo8AzesE.woff2
+
+- __Checkout base font size__: permite definir el tamaño de la fuente en el elemento raíz. Ingresa el valor deseado en píxeles (solo números). Predeterminado nativo: 10 píxeles.
+
+Ejemplo:
+
+| Correcto | Incorrecto |
+| ---------------- | ---------------- |
+| 11 | 11px |
+
+<div class="alert alert-warning" role="alert">No utilices fuentes de más de 12 píxeles, ya que pueden distorsionar la visualización del layout.</b></div>
+
+### Modo Sandbox
+
+Para activar el entorno de pruebas de desarrollo, selecciona la opción __Enable sandbox mode__. Debes utilizar credenciales de prueba.
+
+Una vez rellenados los campos de configuración, haz clic en __Save__.
+
+## Configurar el webhook de easypay
+
+Para configurar el webhook de easypay, sigue los pasos que se indican a continuación:
+
+<blockquote><ui>1. En el <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la parte superior izquierda de la pantalla, y en el ícono de la flecha que señala la cuenta deseada.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+<blockquote><ui>2. Accede a <b>Web Services > URL Configuration</b>.</ui>
+
+<blockquote><ui>3. En <b>URL: Notify</b>, ingresa el link a continuación, modificando solamente la información del nombre real de tu tienda marketplace.</ui>
+
+`https://{nombre-de-tu-cuenta}.myvtex.com/_v/easypaypartnerpt.payment-provider-easypay/webhook`
+
+![easypay_es_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/82c01b7233e55da18bd664f274dba813/easypay_en_9.png)
+
+<blockquote><ui>4. Haz clic en <b>Submit</b>.</ui>
+
+## Configurar la afiliación easypay
+
+Para configurar la afiliación easypay, sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __easypay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellena los campos __Application Key__ y __Application Token__ con los datos de tu cuenta easypay.
+5. En __Captura automática de pago__, selecciona la opción __Utiliza el comportamiento recomendado por el procesador de pagos__.
+6. En __¿Activar split y enviar receptores?__, selecciona la opción __Sí__.
+7. Haz clic en `Guardar`.
+
+## Configurar el pago con Apple Pay en easypay (opcional) 
+
+Para procesar pagos con Apple Pay en easypay, primero debes realizar configuraciones para habilitar tu tienda en el entorno de Apple Pay. Obtenga más información en [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/docs/guides/setting-up-merchant-id-in-apple-pay).  
+
+Para configurar otros medios de pago que easypay procesará, accede a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago).
+
+Para establecer condiciones especiales en los medios de pago, accede a [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+
+as seguir los pasos indicados, el conector easypay puede demorar hasta 10 minutos en aparecer en el checkout de tu tienda como medio de pago.
+
diff --git a/docs/tutorials/es/setting-up-payments-with-ebanx-local.md b/docs/tutorials/es/setting-up-payments-with-ebanx-local.md
index ece784110..b977024cd 100644
--- a/docs/tutorials/es/setting-up-payments-with-ebanx-local.md
+++ b/docs/tutorials/es/setting-up-payments-with-ebanx-local.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Ebanx-Local'
 id: 6vVYppbwct3B4j8KuCAvUR
 status: PUBLISHED
 createdAt: 2023-03-22T17:09:50.665Z
-updatedAt: 2023-03-23T12:45:48.284Z
-publishedAt: 2023-03-23T12:45:48.284Z
+updatedAt: 2024-01-23T18:06:33.564Z
+publishedAt: 2024-01-23T18:06:33.564Z
 firstPublishedAt: 2023-03-22T17:34:38.586Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-ebanx-local
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Ebanx-Local. Con este conector, su tienda puede realizar ventas a través de boletos bancarios, tarjetas de crédito y PIX.
+En VTEX es posible la integración con el proveedor de pagos Ebanx-Local. Con este proveedor, su tienda puede realizar ventas a través de boletos bancarios, tarjetas de crédito y PIX.
 
-Para configurar la afiliación Ebanx-Local, siga los pasos a continuación:
+Para configurar Ebanx-Local, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __EBANX-Local__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __EBANX-Local__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta Ebanx.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-ebanx.md b/docs/tutorials/es/setting-up-payments-with-ebanx.md
index 48d3719e4..22f73c930 100644
--- a/docs/tutorials/es/setting-up-payments-with-ebanx.md
+++ b/docs/tutorials/es/setting-up-payments-with-ebanx.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Ebanx'
 id: 4yKdQrt57AW7aElfHH4QKM
 status: PUBLISHED
 createdAt: 2023-03-22T14:27:42.440Z
-updatedAt: 2023-03-23T12:45:53.859Z
-publishedAt: 2023-03-23T12:45:53.859Z
+updatedAt: 2024-01-23T18:07:19.598Z
+publishedAt: 2024-01-23T18:07:19.598Z
 firstPublishedAt: 2023-03-22T17:04:49.283Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,14 @@ legacySlug: configurar-pago-con-ebanx
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Ebanx. Con este conector, su tienda puede realizar ventas a través de boletos bancarios, tarjetas de crédito y PIX.
+En VTEX es posible la integración con el proveedor de pagos Ebanx. Con este proveedor, su tienda puede realizar ventas a través de boletos bancarios, tarjetas de crédito y PIX.
 
-Para configurar la afiliación Ebanx, siga los pasos a continuación:
+Para configurar Ebanx, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Ebanx__.
-4. Haga clic en __Autorizar__. Usted será redirigido al entorno de __Ebanx__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Ebanx__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Haga clic en __Autorizar__. Usted será redirigido al entorno de Ebanx.
 5. En el entorno de Ebanx, ingrese el nombre de usuario y ça contraseña de su cuenta de Ebanx. Siga las instrucciones indicadas para completar la vinculación de la cuenta Ebanx con VTEX.
 6. Al regresar a __Admin VTEX__, haga clic en `Guardar`.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-egetnetv2.md b/docs/tutorials/es/setting-up-payments-with-egetnetv2.md
index eefddf14e..91f52a523 100644
--- a/docs/tutorials/es/setting-up-payments-with-egetnetv2.md
+++ b/docs/tutorials/es/setting-up-payments-with-egetnetv2.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con EgetnetV2'
 id: 6jfBE8ocN5T0xQo8BTGH31
 status: PUBLISHED
 createdAt: 2023-02-13T13:55:05.519Z
-updatedAt: 2023-02-13T14:12:54.200Z
-publishedAt: 2023-02-13T14:12:54.200Z
+updatedAt: 2024-03-14T18:21:39.711Z
+publishedAt: 2024-03-14T18:21:39.711Z
 firstPublishedAt: 2023-02-13T14:12:54.200Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,21 @@ legacySlug: configurar-pago-con-egetnetv2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos EgetnetV2. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y PIX.
+En VTEX es posible la integración con el proveedor de pagos EgetnetV2. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y PIX.
 
-Para configurar la afiliación EgetnetV2, siga los pasos a continuación:
+Para configurar EgetnetV2, siga los pasos a continuación:
 
-1. Acceda al __Admin__ VTEX.
-2. Haga clic en __Pagos__.
-3. Después, haga clic en __Configuración__.
-4. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-5. Haga clic en el conector __EgetnetV2__.
-6. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por EgetnetV2.
-7. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __EgetnetV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por EgetnetV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor EgetnetV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Si desea utilizar [Split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx) en su tienda, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
 8. Haga clic en `Guardar`.
 
-Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
+Para configurar los métodos de pago a procesar por EgetnetV2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
 Después de seguir los pasos indicados, EgetnetV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-etpay.md b/docs/tutorials/es/setting-up-payments-with-etpay.md
index 2665cfb09..9c5834ded 100644
--- a/docs/tutorials/es/setting-up-payments-with-etpay.md
+++ b/docs/tutorials/es/setting-up-payments-with-etpay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con ETpay'
 id: 1vYO022oVj4MdVKP5fCMNx
 status: PUBLISHED
 createdAt: 2022-10-18T17:45:32.139Z
-updatedAt: 2023-03-21T20:54:12.646Z
-publishedAt: 2023-03-21T20:54:12.646Z
+updatedAt: 2024-01-24T17:24:23.326Z
+publishedAt: 2024-01-24T17:24:23.326Z
 firstPublishedAt: 2022-10-18T17:56:29.587Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-etpay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos ETpay. Con este conector, tu tienda puede realizar ventas a través de ETpay.
+En VTEX es posible la integración con el proveedor de pagos ETpay. Con este proveedor, tu tienda puede realizar ventas a través de ETpay.
 
-Para configurar la afiliación ETpay, siga los pasos a continuación:
+Para configurar ETpay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __EtPayment__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __EtPayment__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por ETpay.
 5. Haga clic en `Guardar`.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-evopayments.md b/docs/tutorials/es/setting-up-payments-with-evopayments.md
new file mode 100644
index 000000000..293ba54ed
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-evopayments.md
@@ -0,0 +1,46 @@
+---
+title: 'Configurar pago con EvoPayments'
+id: 7CxSgoftps0DHsfR8otQMf
+status: PUBLISHED
+createdAt: 2024-03-11T17:36:12.910Z
+updatedAt: 2024-03-14T16:37:46.611Z
+publishedAt: 2024-03-14T16:37:46.611Z
+firstPublishedAt: 2024-03-11T18:19:00.757Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-evopayments
+locale: es
+legacySlug: configurar-pago-con-evopayments
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos EVO Payments. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito, débito, private y cobranded labels, y boletos.
+
+Para configurar EVO Payments, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __EvoPayments__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por EVO Payments.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor EVO Payments en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. En __Habilitar autenticación 3DS__, seleccione si habilitar la validación de seguridad 3DS.
+9. En __Habilitar autorización y captura__, seleccione si desea activar esta función.
+10. En __Habilitar plan Iphone For Life__, selecciona si deseas activar esta opción.
+11. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por EVO Payments, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, EVO Payments puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-fcamara-payment-initiator.md b/docs/tutorials/es/setting-up-payments-with-fcamara-payment-initiator.md
index 317e9c189..5681bb7ae 100644
--- a/docs/tutorials/es/setting-up-payments-with-fcamara-payment-initiator.md
+++ b/docs/tutorials/es/setting-up-payments-with-fcamara-payment-initiator.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con FCamara (Iniciador de pagos)'
 id: 4p5E3jc9J5xHkOI6AbnhTV
 status: PUBLISHED
 createdAt: 2023-04-03T15:12:23.123Z
-updatedAt: 2023-04-03T16:42:01.758Z
-publishedAt: 2023-04-03T16:42:01.758Z
+updatedAt: 2024-01-23T18:01:44.039Z
+publishedAt: 2024-01-23T18:01:44.039Z
 firstPublishedAt: 2023-04-03T16:42:01.758Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,19 @@ legacySlug: configurar-pago-con-fcamara-iniciador-de-pagos
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el iniciador de pagos FCamara. Con este conector, su tienda puede realizar ventas a través de PIX.
+En VTEX es posible la integración con el iniciador de pagos FCamara. A traves de, su tienda puede realizar ventas a través de PIX.
 
-Para configurar la afiliación FCamara, siga los pasos a continuación:
+Para configurar FCamara, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __iniciadorfcamara__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __iniciadorfcamara__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta FCamara.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
 
 ## Configurar condición de pago
+
 1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
 3. Seleccione el conector __FCamara - Iniciador de pagamentos__.
diff --git a/docs/tutorials/es/setting-up-payments-with-fintoc.md b/docs/tutorials/es/setting-up-payments-with-fintoc.md
new file mode 100644
index 000000000..d4b0552cd
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-fintoc.md
@@ -0,0 +1,38 @@
+---
+title: 'Configurar pago con Fintoc'
+id: 3TIz2oxbNtzhypWiypqrOZ
+status: PUBLISHED
+createdAt: 2023-07-14T17:06:16.055Z
+updatedAt: 2024-01-24T17:39:34.960Z
+publishedAt: 2024-01-24T17:39:34.960Z
+firstPublishedAt: 2023-07-14T17:49:20.115Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-fintoc
+locale: es
+legacySlug: configurar-pago-con-fintoc
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Fintoc. Con este proveedor, su tienda puede realizar ventas a través de Fintoc.
+
+Para configurar Fintoc, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Fintoc__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__ y __Secret Key__ con los datos proporcionados por su cuenta Fintoc.
+5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
+3. Haga clic en __Fintoc__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Fintoc puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-flywire.md b/docs/tutorials/es/setting-up-payments-with-flywire.md
index 22cac417f..360f4daa5 100644
--- a/docs/tutorials/es/setting-up-payments-with-flywire.md
+++ b/docs/tutorials/es/setting-up-payments-with-flywire.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Flywire'
 id: 12nQ0teCWM1UUtd2Fo6lzO
 status: PUBLISHED
 createdAt: 2023-04-03T13:05:10.955Z
-updatedAt: 2023-04-03T13:32:26.361Z
-publishedAt: 2023-04-03T13:32:26.361Z
+updatedAt: 2024-01-25T18:15:31.540Z
+publishedAt: 2024-01-25T18:15:31.540Z
 firstPublishedAt: 2023-04-03T13:32:26.361Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-flywire
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Flywire. Con este conector, tu tienda puede realizar ventas a través de pagarés y Flywire.
+En VTEX es posible la integración con el proveedor de pagos Flywire. Con este proveedor, tu tienda puede realizar ventas a través de pagarés y Flywire.
 
-Para configurar la afiliación Flywire, siga los pasos a continuación:
+Para configurar Flywire, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Flywire__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Flywire__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__, __Application Token__, __Recipient__, __Locale__, __Provider__ y __Callback version__ con los datos proporcionados por Flywire. 
 5. En __Environment__, elija una de dos opciones: __Demo__ o __Production__.
 6. En __Display Payer Information__, elija una de dos opciones: __True_ o __False__.
diff --git a/docs/tutorials/es/setting-up-payments-with-fpay.md b/docs/tutorials/es/setting-up-payments-with-fpay.md
index 992b4343e..7606085e5 100644
--- a/docs/tutorials/es/setting-up-payments-with-fpay.md
+++ b/docs/tutorials/es/setting-up-payments-with-fpay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Fpay'
 id: 6BaLIO2R7tOh6E1MmNoDXj
 status: PUBLISHED
 createdAt: 2022-10-18T19:13:32.326Z
-updatedAt: 2023-03-21T20:52:34.889Z
-publishedAt: 2023-03-21T20:52:34.889Z
+updatedAt: 2024-01-24T17:26:52.492Z
+publishedAt: 2024-01-24T17:26:52.492Z
 firstPublishedAt: 2022-10-18T19:42:03.523Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-fpay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Fpay. Con este conector, tu tienda puede realizar ventas a través de pagarés.
+En VTEX es posible la integración con el proveedor de pagos Fpay. Con este proveedor, tu tienda puede realizar ventas a través de pagarés.
 
-Para configurar la afiliación Fpay, siga los pasos a continuación:
+Para configurar Fpay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Fpay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Fpay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Fpay. 
 5. Haga clic en `Guardar`.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-geru.md b/docs/tutorials/es/setting-up-payments-with-geru.md
new file mode 100644
index 000000000..8a34e920b
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-geru.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pago con Geru'
+id: 2XmYp4Uh1Yulv3a9puRgwm
+status: PUBLISHED
+createdAt: 2024-02-05T11:49:37.163Z
+updatedAt: 2024-03-13T14:10:42.303Z
+publishedAt: 2024-03-13T14:10:42.303Z
+firstPublishedAt: 2024-02-05T13:45:07.728Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-geru
+locale: es
+legacySlug: configurar-pago-con-geru
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Geru. Con este proveedor, su tienda puede realizar ventas a través de Geru y BNPL.
+
+Para configurar Geru siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Geru__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Geru.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Geru en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Geru__ o __BNPL__.
+4. Active la condición en el campo __Status__. Para utilizar __BNPL__, en __Proceso con afiliación__, seleccione la opción __boletoflex-geru-v0__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Geru puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-gocuotas.md b/docs/tutorials/es/setting-up-payments-with-gocuotas.md
new file mode 100644
index 000000000..baabc35ff
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-gocuotas.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pago con GOcuotas'
+id: 6oGcugCc3pXIJEhbOZ5YmV
+status: PUBLISHED
+createdAt: 2023-09-29T11:30:25.004Z
+updatedAt: 2024-02-05T13:42:55.988Z
+publishedAt: 2024-02-05T13:42:55.988Z
+firstPublishedAt: 2023-09-29T11:39:03.239Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-gocuotas
+locale: es
+legacySlug: configurar-pago-con-gocuotas
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos GOcuotas. Con este proveedor, su tienda puede realizar ventas a través de GOcuotas.
+
+Para configurar GOcuotas, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __GOcuotas__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta GOcuotas.
+5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Crear proveedor`.
+3. Escriba el nombre __GOcuotas__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, GOcuotas puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-guatapay.md b/docs/tutorials/es/setting-up-payments-with-guatapay.md
new file mode 100644
index 000000000..e533f273b
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-guatapay.md
@@ -0,0 +1,38 @@
+---
+title: 'Configurar pago con Guatapay'
+id: 57ilA6k1VKZjy0dgwSs7pu
+status: PUBLISHED
+createdAt: 2023-09-18T15:35:35.188Z
+updatedAt: 2024-01-25T17:04:24.009Z
+publishedAt: 2024-01-25T17:04:24.009Z
+firstPublishedAt: 2023-09-18T16:33:40.921Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-guatapay
+locale: es
+legacySlug: configurar-pago-con-guatapay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Guatapay. Con este proveedor, su tienda puede realizar ventas a través de Guatapay.
+
+Para configurar Guatapay, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Guatapay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__, __Client ID - Guatapay__ y __Client Secret - Guatapay__ con los datos proporcionados por su cuenta Guatapay.
+5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Guatapay.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Guatapay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-inswitch.md b/docs/tutorials/es/setting-up-payments-with-inswitch.md
new file mode 100644
index 000000000..b9b1b37dc
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-inswitch.md
@@ -0,0 +1,49 @@
+---
+title: 'Configurar pago con Inswitch'
+id: XxY7tbpg4GMrexGQfto6Q
+status: PUBLISHED
+createdAt: 2023-07-14T17:56:24.581Z
+updatedAt: 2024-01-24T17:44:57.275Z
+publishedAt: 2024-01-24T17:44:57.275Z
+firstPublishedAt: 2023-07-14T18:11:24.293Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-inswitch
+locale: es
+legacySlug: configurar-pago-con-inswitch
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Inswitch. Con este proveedor, su tienda puede realizar ventas a través de diferentes de Inswitch.
+
+Para configurar Inswitch, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Inswitch__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por el Inswitch.
+5. En el campo __Captura automática de pago__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza El Comportamiento Recomendado Por El Procesador de Pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Imediatamente: Captura Automática Al Autorizar El Pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Imediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Captura automática al autorizar el pago").</li>
+   		<li><b>Programado: Establece Cuándo Se Realizará La Captura Automática</b>: al seleccionar esta opción, se mostrará el campo <b>Periodo de tiempo programado en horas para la captura automática</b>, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.</li>        
+   		<li><b>Desactivado: No Capturado Automáticamente</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda__ > __Pago__ > __Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Elige la condición de pago __Inswitch__.
+4. Rellene el campo __Nombre de la regla__ con un nombre de su elección para su identificación.
+5. Active la condición en el campo __Status__.
+6. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+7. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Inswitch puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-itau-rede.md b/docs/tutorials/es/setting-up-payments-with-itau-rede.md
new file mode 100644
index 000000000..90426548a
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-itau-rede.md
@@ -0,0 +1,91 @@
+---
+title: 'Configurar pago con Itaú Rede'
+id: 77BYOKxVzONWulAf8dTVSX
+status: PUBLISHED
+createdAt: 2024-04-18T15:03:32.890Z
+updatedAt: 2024-04-25T15:26:44.454Z
+publishedAt: 2024-04-25T15:26:44.454Z
+firstPublishedAt: 2024-04-25T14:54:53.085Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-itau-rede
+locale: es
+legacySlug: configurar-pago-con-itau-rede
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Itaú Rede. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito.
+
+Para utilizar Itaú Rede, debes:
+
+- [Obtener credenciales en el entorno de Userede](#obtener-credenciales-en-el-entorno-de-userede)
+- [Configurar Itaú Rede en VTEX](#configurar-itau-rede-en-vtex)
+- [Configurar condición de pago](#configurar-condicion-de-pago)  
+
+## Obtener credenciales en el entorno de Userede
+
+<div class="alert alert-warning">
+Las configuraciones realizadas en un entorno externo a VTEX podrán ser discontinuadas o modificadas sin previo aviso. Consulta tu cuenta de Itaú Rede para obtener información actualizada.
+</div>
+
+Para obtener las credenciales __Clave de aplicación__ y __Token de aplicación__ necesarias para configurar Itaú Rede en VTEX, siga los pasos a continuación:
+
+<blockquote><ui>1. Acceda al <a href="https://meu.userede.com.br/login">Portal Userede</a> con los datos de su cuenta Itaú Rede.</ui>
+
+<blockquote><ui>2. Seleccione la cuenta en la que desea realizar pagos en VTEX y haga clic en <b>Aplicar</b>. Guarde el número de cuenta, ya que debe ser utilizado en el campo <b>Clave de aplicación</b> de la sección <a href="#configurar-itau-rede-en-vtex">Configurar Itaú Rede en VTEX</a>.</ui>
+
+![Itaú Rede_1](//images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
+
+<blockquote><ui>3. Después de que la pantalla se actualice a la cuenta deseada, en el menú <b>para vender</b>, seleccione la opción <b>e-commerce</b>.</ui>
+
+![Itaú Rede_2](//images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
+
+<blockquote><ui>4. En la página <b>e-commerce</b>, haga clic en la tarjeta <b>chave de integração</b>.</ui>
+
+![Itaú Rede_3](//images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
+
+<blockquote><ui>5. Después de leer la información de la "chave de integração", haga clic en <b>li, estou ciente</b>.</ui>
+
+![Itaú Rede_4](//images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
+
+<blockquote><ui>6. Haga clic en el botón <b>gerar nova chave</b>.</ui>
+
+![Itaú Rede_5](//images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
+
+<blockquote><ui>7. Verifique la información descrita en la ventana <b>gerar nova chave de integração</b> y haga clic en <b>gerar nova chave</b>.</ui>
+
+![Itaú Rede_6](//images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
+
+<blockquote><ui>8. Después de crear la nueva clave, haga clic en <b>copiar</b> y conserve la información en un lugar seguro. Esta clave debe ser utilizada en el campo <b>Token de aplicación</b> de la sección <a href="#configurar-itau-rede-en-vtex">Configurar Itaú Rede en VTEX</a>.</ui>
+
+<blockquote><ui><div class="alert alert-warning">
+Una vez que se crea una "chave de integração" en el entorno de red, no se puede volver a acceder a ella desde otras ubicaciones. Registre la información de la clave en una ubicación protegida y, si se pierde, repita el proceso para generar una nueva clave.
+  </div></ui></blockquote>
+
+## Configurar Itaú Rede en VTEX
+
+Para configurar Itaú Rede siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __ItauRede__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ obtenidas en los pasos 2 y 8 de la sección [Obtener credenciales en el entorno de Userede](#obtener-credenciales-en-el-entorno-de-userede).
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Itaú Rede en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __merchantName__, ingresa el nombre de tu tienda.
+8. En __SoftDescriptor__, describe el mensaje de identificación que se mostrará en la transacción realizada en tu tienda.
+9. En el campo __delayToAutoSettle__, escoja en cuánto tiempo desea que la captura sea realizada (después de la aprobación de la transacción y del análisis del antifraude).
+10. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en el nombre de la marca de tarjeta de crédito deseada.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Itaú Rede puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-iugu.md b/docs/tutorials/es/setting-up-payments-with-iugu.md
index 6103f7d06..e468d3cfc 100644
--- a/docs/tutorials/es/setting-up-payments-with-iugu.md
+++ b/docs/tutorials/es/setting-up-payments-with-iugu.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar pago con Iugu'
+title: 'Configurar pago con iugu'
 id: 2c1nAo5iR6jG1UySzRB89t
 status: PUBLISHED
 createdAt: 2022-03-31T18:58:08.146Z
-updatedAt: 2022-03-31T19:22:31.835Z
-publishedAt: 2022-03-31T19:22:31.835Z
+updatedAt: 2024-03-13T11:53:59.094Z
+publishedAt: 2024-03-13T11:53:59.094Z
 firstPublishedAt: 2022-03-31T19:22:31.835Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,69 @@ legacySlug: configurar-pago-con-iugu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Iugu. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y PIX.
+[iugu](https://partnerportal.vtex.com/iugu-156/p) es una solución en asociación con VTEX que proporciona las siguientes opciones de pago a través de [checkout transparente](https://help.vtex.com/es/tutorial/que-es-el-checkout-transparente--2Y4ECegUmcYUggmck2GOwe): tarjeta de crédito, pix y boleto bancario. Además, es posible realizar [operaciones de recurrencia](https://help.vtex.com/es/tutorial/configurar-recurrencia-en-condiciones-de-pago--6EGuoAytLqU2CqUuaI2GUW) y [split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx) (cobros y transacción) entre marketplaces.
 
-Para configurar tu afiliación Iugu, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para agregar iugu a tu tienda, sigue los pasos a continuación:
 
-Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __iugu__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En los campos __Clave de aplicación__ y __Token de aplicación__, ingrese la información proporcionada por iugu ([ID da conta y Chave API](https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#localizando-id-da-conta-e-chave-api-no-painel-da-iugu)).
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor iugu en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Si desea utilizar el boleto bancario como medio de pago, en __Campos del proveedor__, complete el campo __Prazo de vencimento do boleto(em dias)__ con el mismo valor configurado en su área de clientes en el portal iugu.
+8. Haga clic en `Guardar`.
 
-Después de seguir los pasos indicados, Iugu puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
+## Configurar condiciones de pago
+
+Para procesar métodos de pago con tarjeta de crédito, pix y boleto bancario con iugu en su tienda, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en el método de pago deseado (bandera de la tarjeta de crédito, pix o boleto bancario).
+4. Complete el campo __Nombre de la condición__ con un nombre de su elección para identificación.
+5. Active la condición en el campo __Status__.
+6. En __Procesar con proveedor__ seleccione la opción iugu.
+7. Para pagos con tarjeta de crédito, seleccione si desea utilizar un sistema antifraude seleccionando la opción __Utilizar antifraude__. También es posible configurar si se deben realizar pagos con tarjeta de crédito [a vista o en cuotas (con o sin interéss)](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#a-vista).
+8. Si desea, puede configurar [condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+9. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, el proveedor iugu puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
+
+<div class="alert alert-warning">
+  Antes de realizar transacciones con tarjeta de crédito, pix o boleto bancario con iugu en tu tienda, verifica si estos métodos de pago ya están habilitados en <a href="https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento">tu área de clientes en el portal iugu</a>.
+  </div>
+
+## Configurar el split de pago en marketplace con iugu
+
+Para procesar pagos en [marketplace con split de pago](https://help.vtex.com/es/tutorial/pagos-en-los-marketplaces-vtex--2kYOfWCZYweJkYl18bw9yD#split-de-pagos) en iugu es necesario registrar sellers de tu tienda con el mismo CNPJ (número de identificación del vendedor) en el VTEX Admin y en tu área de clientes en el portal iugu. 
+
+Obtenga más información sobre cómo crear sellers en VTEX en [Agregar seller](https://help.vtex.com/es/tutorial/agregar-seller--tutorials_392) y acceda a la documentación de iugu para crear subcuentas (sellers) a través de [área de cliente ](https://support.iugu.com/hc/pt-br/articles/4411276874779-Como-criar-uma-subconta-pelo-painel-iugu-) o [API](https://dev.iugu.com/docs/configurar-subconta-por-api). 
+
+### Habilitar split de cobros con iugu
+
+Para habilitar el split de cobros con iugu en su tienda, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. Escriba el nombre __iugu__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+3. En __Detalles__, haga clic en el botón `Editar`.
+4. En __Control de pago__, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
+5. Haga clic en `Guardar`.
+
+<div class="alert alert-warning">
+  La opción de split de cobros no está disponible para su uso en un entorno de prueba.
+  </div>
+
+Luego de seguir los pasos indicados, la funcionalidad de split de cobros con el proveedor iugu puede tardar hasta 10 minutos en activarse en tu tienda.
+
+<div class="alert alert-warning">
+  Para definir comisiones específicas para cada seller de su tienda, acceda a  <b>Marketplace > Sellers> Gestión</b> en el Admin de VTEX, seleccione el vendedor deseado e ingrese los valores de las comisiones en <b>Comisiones</b>.
+  </div>
+
+## Configurar la recurrencia con iugu
+
+Para que [recurrencia](https://help.vtex.com/es/tutorial/configurar-recurrencia-en-condiciones-de-pago--6EGuoAytLqU2CqUuaI2GUW) esté disponible como condición especial de pago a través de iugu, es necesario:
+
+- Habilite el modo recurrencia en el VTEX Admin.
+- Configurar métodos de pago con tarjeta de crédito o boelto bancario en VTEX Admin e iugu.
+- Configura la funcionalidad [suscripciones](https://help.vtex.com/es/tutorial/como-configurar-suscripciones--1FA9dfE7vJqxBna9Nft5Sj) en tu tienda.
diff --git a/docs/tutorials/es/setting-up-payments-with-k8bank.md b/docs/tutorials/es/setting-up-payments-with-k8bank.md
new file mode 100644
index 000000000..cd7881675
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-k8bank.md
@@ -0,0 +1,44 @@
+---
+title: 'Configurar pago con K8Bank'
+id: 1ewZll1fwjClvp5Wl1uES1
+status: PUBLISHED
+createdAt: 2023-09-18T13:14:17.375Z
+updatedAt: 2024-01-23T17:56:32.780Z
+publishedAt: 2024-01-23T17:56:32.780Z
+firstPublishedAt: 2023-09-18T13:48:29.694Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-k8bank
+locale: es
+legacySlug: configurar-pago-con-k8bank
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos K8Bank. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de credito, debito, private y cobranded labels, boletos y PIX.
+
+Para configurar K8Bank, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __K8Bank__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__, __cnpj__ y __CobrancasClientId__ con los datos proporcionados por el K8Bank.
+5. En el campo __Captura automática de pago__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza El Comportamiento Recomendado Por El Procesador de Pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Imediatamente: Captura Automática Al Autorizar El Pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Imediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Captura automática al autorizar el pago").</li>
+   		<li><b>Programado: Establece Cuándo Se Realizará La Captura Automática</b>: al seleccionar esta opción, se mostrará el campo <b>Periodo de tiempo programado en horas para la captura automática</b>, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.</li>        
+   		<li><b>Desactivado: No Capturado Automáticamente</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+6. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+
+7. Haga clic en `Salvar`.
+
+Para configurar los métodos de pago a procesar por K8Bank, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, K8Bank puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-kaiowa.md b/docs/tutorials/es/setting-up-payments-with-kaiowa.md
index f9c4a4fcb..e47517f4a 100644
--- a/docs/tutorials/es/setting-up-payments-with-kaiowa.md
+++ b/docs/tutorials/es/setting-up-payments-with-kaiowa.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Kaiowa'
 id: 1QfsSpAF0CHQFVd9qSGcA5
 status: PUBLISHED
 createdAt: 2023-04-06T18:20:04.972Z
-updatedAt: 2023-04-06T18:26:07.966Z
-publishedAt: 2023-04-06T18:26:07.966Z
+updatedAt: 2024-01-23T17:58:45.045Z
+publishedAt: 2024-01-23T17:58:45.045Z
 firstPublishedAt: 2023-04-06T18:26:07.966Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-kaiowa
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Kaiowa. Con este conector, su tienda puede realizar ventas a través de Kaiowa.
+En VTEX es posible la integración con el proveedor de pagos Kaiowa. Con este proveedor, su tienda puede realizar ventas a través de Kaiowa.
 
-Para configurar la afiliación Kaiowa, siga los pasos a continuación:
+Para configurar Kaiowa, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Kaiowa__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Kaiowa__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta Kaiowa.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-khipu.md b/docs/tutorials/es/setting-up-payments-with-khipu.md
index 0603768cc..feb34bf1d 100644
--- a/docs/tutorials/es/setting-up-payments-with-khipu.md
+++ b/docs/tutorials/es/setting-up-payments-with-khipu.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Khipu'
 id: RcHQjURWDXa0doL15DiUj
 status: PUBLISHED
 createdAt: 2023-03-24T19:34:06.675Z
-updatedAt: 2023-03-30T14:08:54.819Z
-publishedAt: 2023-03-30T14:08:54.819Z
+updatedAt: 2024-01-24T17:53:53.676Z
+publishedAt: 2024-01-24T17:53:53.676Z
 firstPublishedAt: 2023-03-30T14:08:54.819Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-khipu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Khipu. Con este conector, tu tienda puede realizar ventas a través de pagarés.
+En VTEX es posible la integración con el proveedor de pagos Khipu. Con este proveedor, tu tienda puede realizar ventas a través de pagarés.
 
-Para configurar la afiliación Khipu, siga los pasos a continuación:
+Para configurar Khipu, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Khipu__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Khipu__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Khipu. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-koin-payments.md b/docs/tutorials/es/setting-up-payments-with-koin-payments.md
index 51d73302e..1ccb425a2 100644
--- a/docs/tutorials/es/setting-up-payments-with-koin-payments.md
+++ b/docs/tutorials/es/setting-up-payments-with-koin-payments.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Koin-Payments'
 id: 5nTQFgTLGkPcJrqi7PKlO1
 status: PUBLISHED
 createdAt: 2022-08-18T12:40:14.512Z
-updatedAt: 2023-03-21T21:02:35.479Z
-publishedAt: 2023-03-21T21:02:35.479Z
+updatedAt: 2024-03-11T17:58:22.260Z
+publishedAt: 2024-03-11T17:58:22.260Z
 firstPublishedAt: 2022-08-18T12:56:36.170Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,17 @@ legacySlug: configurar-pago-con-koin-payments
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Koin-Payments. Con este conector, su tienda puede realizar ventas a través de tarjetas de crédito y débito, PIX y BoletoParceladoKoin.
+En VTEX es posible la integración con el proveedor de pagos Koin-Payments. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito y débito, PIX y BoletoParceladoKoin.
 
-Para configurar la afiliación Koin-Payments, siga los pasos a continuación:
+Para configurar Koin-Payments, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Koin-Payments__.
-4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Koin-Payments.
-5. Haga clic en `Guardar`.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Koin-Payments__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por Koin-Payments.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Koin-Payments en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en__ Activar modo de prueba__.
+7. Haga clic en `Guardar`.
 
 Para configurar los métodos de pago a procesar por Koin-Payments, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
diff --git a/docs/tutorials/es/setting-up-payments-with-koin.md b/docs/tutorials/es/setting-up-payments-with-koin.md
index 610ee9744..f8ad36790 100644
--- a/docs/tutorials/es/setting-up-payments-with-koin.md
+++ b/docs/tutorials/es/setting-up-payments-with-koin.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagos con Koin'
 id: 415vLlrVSUgeYYwycCaGiQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-24T19:48:39.401Z
-updatedAt: 2023-03-29T00:51:56.272Z
-publishedAt: 2023-03-29T00:51:56.272Z
+updatedAt: 2024-03-18T18:30:25.798Z
+publishedAt: 
 firstPublishedAt: 2018-04-24T21:17:23.835Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,8 @@ legacySlug: configurar-pagos-con-koin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Usted puede configurar Koin para recibir pagos en su tienda. En esta modalidad, su cliente escoge el __medio de pago__ Koin Pospago para efectuar la compra.
 
 Para configurar los pagos con Koin, siga estos pasos:
diff --git a/docs/tutorials/es/setting-up-payments-with-kueski-pay.md b/docs/tutorials/es/setting-up-payments-with-kueski-pay.md
index e42be6edc..3d6e4a7c9 100644
--- a/docs/tutorials/es/setting-up-payments-with-kueski-pay.md
+++ b/docs/tutorials/es/setting-up-payments-with-kueski-pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Kueski Pay'
 id: 3jDfBFi33tMC12Ifi8M6X7
 status: PUBLISHED
 createdAt: 2022-08-10T17:09:57.124Z
-updatedAt: 2022-08-10T17:13:39.881Z
-publishedAt: 2022-08-10T17:13:39.881Z
+updatedAt: 2024-01-25T18:14:41.859Z
+publishedAt: 2024-01-25T18:14:41.859Z
 firstPublishedAt: 2022-08-10T17:13:39.881Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: configurar-pago-con-kueski-pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Kueski Pay. Con este conector, tu tienda puede realizar ventas a través de pagarés.
+En VTEX es posible la integración con el proveedor de pagos Kueski Pay. Con este proveedor, tu tienda puede realizar ventas a través de pagarés.
 
-Para configurar tu afiliación Kueski Pay, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para configurar Kueski Pay, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
-Para configurar las condiciones de pago a través de pagarés, acceda a [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare#).
+Para configurar las condiciones de pago a través de pagarés, acceda a [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare).
 
 Después de seguir los pasos indicados, Kueski Pay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-liquido-payment.md b/docs/tutorials/es/setting-up-payments-with-liquido-payment.md
new file mode 100644
index 000000000..2ed371565
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-liquido-payment.md
@@ -0,0 +1,32 @@
+---
+title: 'Configurar pago con Liquido Payment'
+id: 1GKtFlkdwLqabKAyK6pa3J
+status: PUBLISHED
+createdAt: 2023-09-08T20:08:53.120Z
+updatedAt: 2024-01-23T18:36:25.367Z
+publishedAt: 2024-01-23T18:36:25.367Z
+firstPublishedAt: 2023-09-08T20:28:25.462Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-liquido-payment
+locale: es
+legacySlug: configurar-pago-con-liquido-payment
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Liquido Payment. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de credito y PIX.
+
+Para configurar Liquido Payment, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __LiquidoPayment__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__ y __Client ID__ con los datos proporcionados por el Liquido Payment.
+5. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Liquido Payment, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Liquido Payment puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-mach.md b/docs/tutorials/es/setting-up-payments-with-mach.md
index 7390fde97..7b5e6d105 100644
--- a/docs/tutorials/es/setting-up-payments-with-mach.md
+++ b/docs/tutorials/es/setting-up-payments-with-mach.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con MACH'
 id: 7h2NpL6p94NSkNFoOhVG4q
 status: PUBLISHED
 createdAt: 2022-10-18T17:01:32.912Z
-updatedAt: 2023-03-21T20:50:53.363Z
-publishedAt: 2023-03-21T20:50:53.363Z
+updatedAt: 2024-01-24T17:56:37.977Z
+publishedAt: 2024-01-24T17:56:37.977Z
 firstPublishedAt: 2022-10-18T17:19:40.370Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-mach
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos MACH. Con este conector, tu tienda puede realizar ventas a través de MACH.
+En VTEX es posible la integración con el proveedor de pagos MACH. Con esta integración, tu tienda puede realizar ventas a través de MACH.
 
-Para configurar la afiliación MACH, siga los pasos a continuación:
+Para configurar MACH, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Mach-PayBot__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Mach-PayBot__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por MACH.
 5. Haga clic en `Guardar`.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-meliuz.md b/docs/tutorials/es/setting-up-payments-with-meliuz.md
index 742092cbf..bd0773027 100644
--- a/docs/tutorials/es/setting-up-payments-with-meliuz.md
+++ b/docs/tutorials/es/setting-up-payments-with-meliuz.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Méliuz'
 id: 6ajsvgOtRWnKhmgZjnOmZN
 status: PUBLISHED
 createdAt: 2022-07-19T12:45:45.247Z
-updatedAt: 2023-03-26T21:35:11.618Z
-publishedAt: 2023-03-26T21:35:11.618Z
+updatedAt: 2024-01-23T18:53:00.570Z
+publishedAt: 2024-01-23T18:53:00.570Z
 firstPublishedAt: 2022-07-19T13:15:41.771Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-mercado-pago.md b/docs/tutorials/es/setting-up-payments-with-mercado-pago.md
index 18758650a..d88a919b0 100644
--- a/docs/tutorials/es/setting-up-payments-with-mercado-pago.md
+++ b/docs/tutorials/es/setting-up-payments-with-mercado-pago.md
@@ -3,8 +3,8 @@ title: 'Configurar pagos con Mercado Pago'
 id: 2FPdhTma6QywUmwEcEUGoS
 status: PUBLISHED
 createdAt: 2018-03-08T21:11:28.158Z
-updatedAt: 2023-03-23T16:02:38.696Z
-publishedAt: 2023-03-23T16:02:38.696Z
+updatedAt: 2024-01-23T11:46:52.226Z
+publishedAt: 2024-01-23T11:46:52.226Z
 firstPublishedAt: 2018-03-08T22:43:32.092Z
 contentType: tutorial
 productTeam: Financial
@@ -23,10 +23,11 @@ Además de un subadquirente para procesar transacciones realizadas con diversas
 
 A continuación se muestran las configuraciones para el conector __Mercado Pago__.
 
-## Configurar la afiliación de gateway MercadoPago
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración > Afiliaciones**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. Haga clic en el botón __+__.
-3. Haga clic en el conector __MercadoPago__.
+## Configurar gateway MercadoPago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __MercadoPago__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro con las credenciales proporcionadas por MercadoPago (campos _Client id_ y _Client secret_), recordando que no deben comenzar con __APP\_USR__.
 5. En el campo __País__, seleccione el país de su tienda.
 6. En __Time Zone__, indique la región que define su horario local.
diff --git a/docs/tutorials/es/setting-up-payments-with-mobbex.md b/docs/tutorials/es/setting-up-payments-with-mobbex.md
new file mode 100644
index 000000000..965444aaf
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-mobbex.md
@@ -0,0 +1,34 @@
+---
+title: 'Configurar pago con Mobbex'
+id: 2pgHFFeRRe7LRJOTCWigmh
+status: PUBLISHED
+createdAt: 2023-09-29T12:02:01.214Z
+updatedAt: 2024-01-24T13:31:18.969Z
+publishedAt: 2024-01-24T13:31:18.969Z
+firstPublishedAt: 2023-09-29T12:27:46.314Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-mobbex
+locale: es
+legacySlug: configurar-pago-con-mobbex
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Mobbex. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y débito, y Mobbex.
+
+Para configurar Mobbex, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Mobbex__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Click to authorize VTEX to make payments__, haga clic en __Autorizar__. En este momento, será redirigido a la página de Mobbex, donde deberá acceder a sua cuenta, y autorizar la conexión de VTEX en su cuenta de Mobbex.
+5. Después de autorizar, regresará automáticamente al Admin VTEX, y los campos __Application Key__, __Application Token__ y __Application Id__ fya estarán completados.
+6. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+7. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Mobbex, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Mobbex puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-msc-payment.md b/docs/tutorials/es/setting-up-payments-with-msc-payment.md
new file mode 100644
index 000000000..fb7e35a9f
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-msc-payment.md
@@ -0,0 +1,51 @@
+---
+title: 'Configurar pago con MSC Payment'
+id: 6hPTXSe57DSCuo7i2r3cjV
+status: PUBLISHED
+createdAt: 2023-09-11T14:04:54.926Z
+updatedAt: 2024-01-25T17:06:19.483Z
+publishedAt: 2024-01-25T17:06:19.483Z
+firstPublishedAt: 2023-09-11T14:17:31.484Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-msc-payment
+locale: es
+legacySlug: configurar-pago-con-msc-payment
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos MSC Payment. Con este proveedor, su tienda puede realizar ventas a través de diferentes de MSC Payment.
+
+Para configurar MSC Payment, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __MSC-Payment__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__ y __tasaCambio__ con los datos proporcionados por el MSC Payment.
+5. En el campo __Captura automática de pago__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza El Comportamiento Recomendado Por El Procesador de Pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Imediatamente: Captura Automática Al Autorizar El Pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Imediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Captura automática al autorizar el pago").</li>
+   		<li><b>Programado: Establece Cuándo Se Realizará La Captura Automática</b>: al seleccionar esta opción, se mostrará el campo <b>Periodo de tiempo programado en horas para la captura automática</b>, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.</li>        
+   		<li><b>Desactivado: No Capturado Automáticamente</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+
+6. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+
+7. Haga clic en __Salvar__.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda__ > __Pago__ > __Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
+3. Elige la condición de pago __MSC Payment__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en __Guardar__.
+
+Después de seguir los pasos indicados, MSC Payment puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-netpay-and-netpay-checkout.md b/docs/tutorials/es/setting-up-payments-with-netpay-and-netpay-checkout.md
index 49c3b2544..fffc07a87 100644
--- a/docs/tutorials/es/setting-up-payments-with-netpay-and-netpay-checkout.md
+++ b/docs/tutorials/es/setting-up-payments-with-netpay-and-netpay-checkout.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con NetPay y NetPay Checkout'
 id: 4x03ZhET2ocg9jzx6y482Y
 status: PUBLISHED
 createdAt: 2023-03-02T12:01:13.847Z
-updatedAt: 2023-03-22T17:33:39.076Z
-publishedAt: 2023-03-22T17:33:39.076Z
+updatedAt: 2024-01-25T18:29:38.914Z
+publishedAt: 2024-01-25T18:29:38.914Z
 firstPublishedAt: 2023-03-02T12:47:50.707Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,16 @@ legacySlug: configurar-pago-con-netpay-y-netpay-checkout
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos NetPay. Con este conector, su tienda puede realizar ventas a través de boletos bancarios, tarjetas de crédito y redirect.
+En VTEX es posible la integración con el proveedor de pagos NetPay. Con este proveedor, su tienda puede realizar ventas a través de boletos bancarios, tarjetas de crédito y redirect.
 
-Para configurar la afiliación NetPay, siga los pasos a continuación:
+Para configurar NetPay, siga los pasos a continuación:
 
-1. Acceda al __Admin__ VTEX.
-2. Haga clic en __Pagos__.
-3. Después, haga clic en __Configuración__.
-4. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-5. Haga clic en uno de los conectores: __NetPay__ o __NetPayCheckout__.
-6. Rellene los campos de registro __Application Token__, __Application Token__ y __Numero del comercio__ con los datos proporcionados por NetPay.
-7. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
-8. Haga clic en `Guardar`.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __NetPay__ o __NetPayCheckout__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Token__, __Application Token__ y __Numero del comercio__ con los datos proporcionados por NetPay.
+5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+6. Haga clic en `Guardar`.
 
 Para configurar los métodos de pago a procesar por NetPay, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
diff --git a/docs/tutorials/es/setting-up-payments-with-notes-payable.md b/docs/tutorials/es/setting-up-payments-with-notes-payable.md
new file mode 100644
index 000000000..007027b52
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-notes-payable.md
@@ -0,0 +1,58 @@
+---
+title: 'Configurar pagos con Pagaré'
+id: 5pW7avTwtyQcMu4uiW8quQ
+status: PUBLISHED
+createdAt: 2018-06-21T20:20:24.484Z
+updatedAt: 2023-10-18T11:58:23.708Z
+publishedAt: 2023-10-18T11:58:23.708Z
+firstPublishedAt: 2018-06-25T15:42:31.515Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: configurar-pagos-con-pagare
+locale: es
+legacySlug: configurar-pagos-con-pagare
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX, su tienda puede recibir pagos a través de pagarés. Para habilitar esta opción, debe realizar los siguientes pasos:
+
+1. [Configurar la afiliación de gateway](#configurar-la-afiliacion-de-gateway)
+2. [Configurar Pagaré](#configurar-pagare)
+3. [Configurar las condiciones de pago](#configurar-las-condiciones-de-pago)
+
+## Configurar la afiliación de gateway
+
+Para configurar una afiliación de gateway, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
+
+<div class="alert alert-warning">
+Verifique que la afiliación de gateway deseada admita el procesamiento de pagos de pagarés.
+</div>
+
+## Configurar Pagaré
+
+Después de configurar una de las afiliaciones de gateway indicadas, debe configurar el pago personalizado del __Pagaré__.
+
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en la pestaña __Pagos Personalizados__. 
+3. En __Pagarés__, haga clic en una de las 5 cajas de configuración de pago.
+4. Rellene los siguientes campos con la información correspondiente:
+
+- __Nombre:__ es el nombre que se utilizará para identificar el pago.
+- __Descripción:__ ingrese los detalles de la condición de pago.
+- __Validez del pagaré:__ Plazo límite que su cliente tendrá para pagar el pagaré antes de que caduque.
+- __Autorización automática:__ seleccione si desea autorizar los pagos automáticamente. Recomendamos esta opción solo en casos en los que el pago que se realiza durante la entrega o recogida del pedido en la tienda. Si selecciona «Yes», el status del pedido cambia automáticamente a Preparando entrega sin pasar por ninguna verificación de pago.
+- __Modificar margen:__ es el margen porcentual permitido para la modificación del importe del pago realizado con un pagaré. Para algunos clientes, puede ser importante permitir [cambios en los pedidos](https://help.vtex.com/es/tutorial/cambiar-items-de-un-pedido-finalizado--tutorials_190). En este caso, debe rellenar el campo Modificar margen para determinar el porcentaje de margen de cambio permitido.
+- __Activar split de pago:__ indique si utilizará la solución de [split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx). Si selecciona esta opción, cuando la venta involucre tiendas del marketplace, el pagaré se dividirá entre los sellers y el marketplace.
+- __Facturación automática:__ Número de días para la facturación automática del pagaré después de la autorización. 
+Los pagarés se facturan en el momento de la autorización del pago. Al configurar este campo, la facturación no se producirá al momento de la autorización, sino después del número de días que establezca.<br>
+
+<ul>
+5. Haga clic en <b>Salvar</b> para guardar los cambios.
+  </ul>
+
+## Configurar las condiciones de pago
+
+Después de completar todos los pasos, el pago con pagaré está configurado y listo para ser utilizado en su tienda.
+
+Para asociarlo a una condición de pago, siga el artículo [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago).
diff --git a/docs/tutorials/es/setting-up-payments-with-nupay.md b/docs/tutorials/es/setting-up-payments-with-nupay.md
index 7c37a0c87..f7b01ba78 100644
--- a/docs/tutorials/es/setting-up-payments-with-nupay.md
+++ b/docs/tutorials/es/setting-up-payments-with-nupay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Nubank (NuPay)'
 id: 4nVjWfJw7PwraBHCoS45tc
 status: PUBLISHED
 createdAt: 2022-07-19T17:39:57.710Z
-updatedAt: 2023-03-26T21:17:16.116Z
-publishedAt: 2023-03-26T21:17:16.116Z
+updatedAt: 2024-01-23T19:13:04.800Z
+publishedAt: 2024-01-23T19:13:04.800Z
 firstPublishedAt: 2022-07-19T18:24:09.993Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-nuvei.md b/docs/tutorials/es/setting-up-payments-with-nuvei.md
new file mode 100644
index 000000000..61274fb23
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-nuvei.md
@@ -0,0 +1,72 @@
+---
+title: 'Configurar pago con Nuvei'
+id: 67DjdrpIaZZmhXv9Iwa6Ev
+status: DRAFT
+createdAt: 2024-03-27T12:55:27.016Z
+updatedAt: 2024-03-27T17:47:53.436Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-nuvei
+locale: es
+legacySlug: configurar-pago-con-nuvei
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con Nuvei. A través de este proveedor, tu tienda puede realizar ventas con tarjetas de crédito y débito.
+
+Para utilizar Nuvei, siga los pasos a continuación:
+
+- [Configurar Nuvei en VTEX](#configurar-proveedor-nuvei-en-vtex)
+- [Configurar la URL DMN en Nuvei](#configurar-la-URL-DMN-en-Nuvei)
+
+## Configurar proveedor Nuvei en VTEX
+
+<blockquote><ui>1. En el Admin VTEX, accede a <b>Configuración de la tienda > Pago > Proveedores</b>, o escribe <b>Proveedores</b> en la barra de búsqueda en la parte superior de la página.</ui>
+
+<blockquote><ui>2. En la pantalla de proveedores, haga clic en el botón <b>Nuevo proveedor</b>.</ui>
+
+<blockquote><ui>3. Escriba el nombre <b>nuvei-payment-provider</b> en la barra de búsqueda y haga clic en el nombre del proveedor.</ui>
+
+<blockquote><ui>4. En <b>Autorización del proveedor</b>, rellene los campos de registro <b>Clave de aplicación</b> y <b>Token de aplicación</b> con la información de su cuenta Nuvei.</ui>
+
+<blockquote><ui>5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Nuvei en la pantalla VTEX Admin, ingrese la información en el campo <b>Nombre</b> en <b>Información general</b>.</ui>
+
+<blockquote><ui>6. En <b>Control de pago</b>, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en <b>Activar modo de prueba</b>.</ui>
+
+<blockquote><ui>7. Para rellenar los campos <b>Merchant Id</b>, <b>Merchant Site Id</b> y <b>Client Secret</b> (Secret Key), 
+acceder a la información disponible en <b>Settings > My Integration Settings</b> dentro del panel de control de su cuenta en el entorno Nuvei.</ui>
+
+<blockquote><ui><div class="alert alert-warning">
+ Nuvei tiene credenciales (Merchant Id, Merchant Site Id e Client Secret) específicas para cada tipo de entorno. Acceder a entornos de prueba <a href="sandbox.nuvei.com">(Integration)</a> y <a href="cpanel.nuvei.com">Live</a> 
+identificar las credenciales relativas a cada uno de ellos.
+  </div></blockquote>
+<br>  
+<blockquote><ui>8. En <b>Environment</b>, seleccione si desea configurar el proveedor Nuvei en el entorno <b>Integration</b> o <b>Live</b>.</ui>
+
+<blockquote><ui>9. En <b>Test 3ds challenge Integration only</b>, si ha seleccionado el entorno de prueba (<b>Integration</b>) es posible realizar pruebas de seguridad 3DS a través de las opciones <b>Force 3ds Challenge</b>, <b>Force 3ds Frictionless</b> o <b>User cardHolder name</b>. 
+Para más información sobre las pruebas accede a la documentación <a href="https://docs.nuvei.com/documentation/integration/testing/testing-cards/?highlight=test%20cards#3d-secure-v2-test-scenarios">Nuvei</a>.</ui>
+
+ <blockquote><ui><div class="alert alert-warning">
+   Siempre que el <b>Environment</b> del proveedor esté configurado como <b>Live</b>, la opción seleccionada para el campo <b>Test 3ds challenge Integration only</b> debe ser <b>User cardHolder name</b>.
+  </div></blockquote>
+<br>  
+<blockquote><ui>10. Haga clic en <b>Guardar</b>.</ui>
+
+## Configurar la URL DMN en Nuvei
+
+Para configurar la información de la URL DMN en Nuvei, siga los pasos a continuación:
+
+1. Acceda a su entorno de nube de prueba ([Integración](sandbox.nuvei.com)) o [Life](cpanel.nuvei.com).
+2. En el menú __Configuración__, haga clic en __Mis configuraciones de integración__.
+3. En __DMN URL__, reemplace el campo __{nombre-cuenta}__ con el nombre de su cuenta VTEX.
+
+`https://master--{nombre-de-cuenta}.myvtex.com/_v/api/nuvei-paid-provider/v0/dmn` 
+
+Para configurar los métodos de pago a procesar por Nuvei, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Nuvei puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-pagaleve.md b/docs/tutorials/es/setting-up-payments-with-pagaleve.md
index 9bea64adb..04b2bb087 100644
--- a/docs/tutorials/es/setting-up-payments-with-pagaleve.md
+++ b/docs/tutorials/es/setting-up-payments-with-pagaleve.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Pagaleve'
 id: 3ro5eb99noG7T4QpoQaJI5
 status: PUBLISHED
 createdAt: 2022-06-22T16:26:18.290Z
-updatedAt: 2023-03-26T21:40:42.801Z
-publishedAt: 2023-03-26T21:40:42.801Z
+updatedAt: 2024-01-23T19:14:42.547Z
+publishedAt: 2024-01-23T19:14:42.547Z
 firstPublishedAt: 2022-06-22T16:33:24.266Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-pagarmev3.md b/docs/tutorials/es/setting-up-payments-with-pagarmev3.md
index ce0e4ad07..c34c32b16 100644
--- a/docs/tutorials/es/setting-up-payments-with-pagarmev3.md
+++ b/docs/tutorials/es/setting-up-payments-with-pagarmev3.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con PagarMeV3'
 id: 5PMavdamrVijwIrHas9ndE
 status: PUBLISHED
 createdAt: 2022-06-22T17:05:12.930Z
-updatedAt: 2023-03-26T21:02:02.940Z
-publishedAt: 2023-03-26T21:02:02.940Z
+updatedAt: 2024-03-11T14:27:05.534Z
+publishedAt: 2024-03-11T14:27:05.534Z
 firstPublishedAt: 2022-06-22T17:51:37.670Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,21 @@ legacySlug: configurar-pago-con-pagarmev3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos PagarMeV3. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito y débito, boletos bancarios y PIX.
+En VTEX es posible la integración con el proveedor de pagos PagarMeV3. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y débito, boletos bancarios y PIX.
 
-Para configurar la afiliación PagarMeV3, siga los pasos a continuación:
+Para configurar PagarMeV3, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __PagarMeV3__.
-4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por PagarMeV3.
-5. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
-6. Haga clic en `Guardar`.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagarMeV3__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por PagarMeV3.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagarMeV3 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Si desea utilizar [Split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx) en su tienda, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
+8. Haga clic en `Guardar`.
 
-Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
+Para configurar los métodos de pago a procesar por PagarMeV3, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
 Después de seguir los pasos indicados, PagarMeV3 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-pagbrasilv2.md b/docs/tutorials/es/setting-up-payments-with-pagbrasilv2.md
new file mode 100644
index 000000000..1baf9ce4e
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-pagbrasilv2.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pago con PagBrasilV2'
+id: 5ONHAWmRbZpNIDPXCkNJXD
+status: PUBLISHED
+createdAt: 2024-03-13T16:31:07.244Z
+updatedAt: 2024-03-13T22:24:02.876Z
+publishedAt: 2024-03-13T22:24:02.876Z
+firstPublishedAt: 2024-03-13T22:21:24.967Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: configurar-pago-con-pagbrasilv2
+locale: es
+legacySlug: configurar-pago-con-pagbrasilv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PagBrasilV2. A través de este proveedor, su tienda puede realizar ventas utilizando tarjetas de débito y crédito, boleto, pagarés y PIX.
+
+Para configurar PagBrasilV2, siga los pasos a continuación:
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pagos > Proveedores__, o escriba __Provedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón "Nuevo proveedor".
+3. Escriba el nombre __PagBrasil-v2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, complete los campos __Clave de aplicación__ y __Token de aplicación__ con la información de su cuenta PagBrasilV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagBrasilV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información Básica__.
+6. En __External Service Url__ (URL de servicio externo), ingrese la URL externa que se asociará con `/pvt/paids?an={AccountName}`.
+7. En __Implements Installments Service__ (Implementa el servicio de cuotas), seleccione si desea utilizar servicios de cuotas externos o lo que está configurado en el portal. Si elige la opción __Sim__, el sistema utilizará la URL configurada en el campo __Url del servicio de cuotas__ (URL del servicio de cuotas).
+8. En __External Cancellation Service__ (Servicio de cancelación externo), seleccione si se debe utilizar un servicio de cancelación externo. Si elige la opción __Sim__, el sistema accederá a la URL configurada en el campo __External Service Url__ (URL de servicio externo).
+9. En __Installments Service Url__ (URL del servicio de cuotas), ingrese la URL externa que se asociará con `/options`.
+10. En __SoftDescriptor__ (Descripción de la transacción), indica qué información debe aparecer para identificar la transacción realizada en tu tienda.
+11. En __Captura antecipada__, elija durante cuánto tiempo desea que se realice la captura (después de la aprobación de la transacción y el análisis antifraude). Esta función también se puede desactivar.
+12. En __Tem um antifraude contratado com essa afiliação?__ (¿Tiene contratado un agente antifraude con esta afiliación?), indique si desea utilizar un agente antifraude.
+13. Haga clic en __Guardar__.
+
+Para configurar los métodos de pago a procesar por PagBrasilV2, acceda al [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PagBrasilV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-paghiperv2.md b/docs/tutorials/es/setting-up-payments-with-paghiperv2.md
new file mode 100644
index 000000000..af7c98f21
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-paghiperv2.md
@@ -0,0 +1,36 @@
+---
+title: 'Configurar pago con PagHiperV2'
+id: 131E6zBcTTkzZtL82cZh1x
+status: PUBLISHED
+createdAt: 2024-03-14T12:01:07.521Z
+updatedAt: 2024-03-14T12:18:12.256Z
+publishedAt: 2024-03-14T12:18:12.256Z
+firstPublishedAt: 2024-03-14T12:18:12.256Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-paghiperv2
+locale: es
+legacySlug: configurar-pago-con-paghiperv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PagHiperV2. Con este proveedor, su tienda puede realizar ventas a través de boletos y PIX.
+
+Para configurar PagHiperV2, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagHiperV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por PagHiperV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagHiperV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Limite Vencimento__, ingrese cuántos días permanecerá abierta el boleto después de su fecha de vencimiento.
+7. En __Exibir Frase fixa__, seleccione si desea incluir una frase para que se muestre en las facturas emitidas.
+8. En __Frase variável do vendedor__, si lo desea, configure la frase que se mostrará para cada boleto específico.
+9. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por PagHiperV2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PagHiperV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-paghiperv3.md b/docs/tutorials/es/setting-up-payments-with-paghiperv3.md
new file mode 100644
index 000000000..f90f3320d
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-paghiperv3.md
@@ -0,0 +1,38 @@
+---
+title: 'Configurar pago con PagHiperV3'
+id: 1dYVbSK0yHNY5vp0gJj4fC
+status: PUBLISHED
+createdAt: 2024-03-14T12:27:03.520Z
+updatedAt: 2024-03-14T12:39:32.791Z
+publishedAt: 2024-03-14T12:39:32.791Z
+firstPublishedAt: 2024-03-14T12:39:32.791Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-paghiperv3
+locale: es
+legacySlug: configurar-pago-con-paghiperv3
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PagHiperV3. Con este proveedor, su tienda puede realizar ventas a través de boletos y PIX.
+
+Para configurar PagHiperV3, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagHiperV3__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por PagHiperV3.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagHiperV3 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Limite Vencimento__, ingrese cuántos días permanecerá abierta el boleto después de su fecha de vencimiento.
+8. En __Dias corridos até o vencimento__, ingrese la fecha máxima de vencimiento de los boletos. Para los pagos PIX, no es posible cambiar el período de vencimiento, el período predeterminado es de 15 minutos.
+9. En __Exibir Frase fixa__, seleccione si desea incluir una frase para que se muestre en las facturas emitidas.
+10. En __Frase variável do vendedor__, si lo desea, configure la frase que se mostrará para cada boleto específico.
+11. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por PagHiperV3, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PagHiperV3 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md b/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md
index 4b9f745be..321c1bbf5 100644
--- a/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md
+++ b/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagos con PagoEfectivo'
 id: 1GGyNqZSYE2a8ga4UemYyw
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-09T20:26:14.388Z
-updatedAt: 2021-06-17T18:59:09.202Z
-publishedAt: 2021-06-17T18:59:09.202Z
+updatedAt: 2024-03-18T19:11:11.066Z
+publishedAt: 
 firstPublishedAt: 2018-04-09T21:57:41.363Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagos-con-pagoefectivo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Usted puede configurar PagoEfectivo para recibir pagos en su tienda. En esta modalidad, su cliente escoge el __medio de pago__ PagoEfectivo para efectuar la compra.
 
 Para habilitar pagos con PagoEfectivo, siga los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-payments-with-pagoefectivov2.md b/docs/tutorials/es/setting-up-payments-with-pagoefectivov2.md
new file mode 100644
index 000000000..bf16bee1e
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-pagoefectivov2.md
@@ -0,0 +1,55 @@
+---
+title: 'Configurar pago con PagoEfectivoV2'
+id: 63Raoh7hlWoWbMJOAacfMV
+status: PUBLISHED
+createdAt: 2024-02-06T11:22:25.720Z
+updatedAt: 2024-03-13T15:08:00.716Z
+publishedAt: 2024-03-13T15:08:00.716Z
+firstPublishedAt: 2024-02-06T11:40:45.294Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-pagoefectivov2
+locale: es
+legacySlug: configurar-pago-con-pagoefectivov2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PagoEfectivoV2. Con este proveedor, su tienda puede realizar ventas a través de PagoEfectivoV2.
+
+Para configurar PagoEfectivoV2 siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagoEfectivoV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta PagoEfectivoV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagoEfectivoV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. En __Campos del Proveedor__, ingrese la información __TradeID__, __TradeName__, __TradeEmail__ y __MaxActiveCipTime__ según la información de su cuenta PagoEfectivoV2.
+
+9. En __Country__, seleccione el país donde se realizará la transacción de pago.
+
+10. En __Currency__, seleccione la moneda que se utilizará en la transacción de pago.
+
+11. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __PagoEfectivo__ o __Cuotealo__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, PagoEfectivoV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-pagoexpress.md b/docs/tutorials/es/setting-up-payments-with-pagoexpress.md
new file mode 100644
index 000000000..ce8f563b1
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-pagoexpress.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pago con PagoExpress'
+id: 4VmPz20GbXZ1gMKPaJ09l0
+status: PUBLISHED
+createdAt: 2024-02-05T19:13:06.972Z
+updatedAt: 2024-03-13T15:13:51.485Z
+publishedAt: 2024-03-13T15:13:51.485Z
+firstPublishedAt: 2024-02-05T20:10:35.385Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-pagoexpress
+locale: es
+legacySlug: configurar-pago-con-pagoexpress
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PagoExpress. Con este proveedor, su tienda puede realizar ventas a través de PIX.
+
+Para configurar PagoExpress siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PagoExpress__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta PagoExpress.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PagoExpress en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __PIX__.
+4. Active la condición en el campo __Status__.
+5. En __Procesar con afiliación__, seleccione la opción __pagoexpresspartnerbr-pagoexpress-v0__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, PagoExpress puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-pagosweb.md b/docs/tutorials/es/setting-up-payments-with-pagosweb.md
index 0473501ab..3ac9f4a22 100644
--- a/docs/tutorials/es/setting-up-payments-with-pagosweb.md
+++ b/docs/tutorials/es/setting-up-payments-with-pagosweb.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagos con PagosWEB'
 id: 2qKIeEPUBKqEGo2OyikyQw
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-05T15:48:50.151Z
-updatedAt: 2023-03-29T01:06:09.900Z
-publishedAt: 2023-03-29T01:06:09.900Z
+updatedAt: 2024-03-18T19:12:24.950Z
+publishedAt: 
 firstPublishedAt: 2018-04-05T22:01:49.141Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagos-con-pagosweb
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Usted puede configurar PagosWEB para recibir pagos en su tienda. En esta modalidad, su cliente escoge el __meio de pago__ PagosWEB para efectuar la compra.
 
 Para habilitar pagos con PagosWEB, siga estos pasos:
diff --git a/docs/tutorials/es/setting-up-payments-with-parcelex.md b/docs/tutorials/es/setting-up-payments-with-parcelex.md
index 52c8e3e49..a495645c2 100644
--- a/docs/tutorials/es/setting-up-payments-with-parcelex.md
+++ b/docs/tutorials/es/setting-up-payments-with-parcelex.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Parcelex'
 id: 2CqB2f1A8pxaAFyk8lxbzy
 status: PUBLISHED
 createdAt: 2022-06-22T19:16:08.714Z
-updatedAt: 2023-03-26T21:40:05.111Z
-publishedAt: 2023-03-26T21:40:05.111Z
+updatedAt: 2024-01-23T21:03:35.230Z
+publishedAt: 2024-01-23T21:03:35.230Z
 firstPublishedAt: 2022-06-22T19:19:11.694Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-pay4fun.md b/docs/tutorials/es/setting-up-payments-with-pay4fun.md
new file mode 100644
index 000000000..7e668526d
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-pay4fun.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pago con Pay4Fun'
+id: 7xCpO35RMDRcp1UCvOGZX3
+status: PUBLISHED
+createdAt: 2024-02-05T14:53:57.694Z
+updatedAt: 2024-03-13T15:15:38.399Z
+publishedAt: 2024-03-13T15:15:38.399Z
+firstPublishedAt: 2024-02-05T15:29:05.357Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-pay4fun
+locale: es
+legacySlug: configurar-pago-con-pay4fun
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Pay4Fun. Con este proveedor, su tienda puede realizar ventas a través de PIX.
+
+Para configurar Pay4Fun siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Pay4Fun__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Pay4Fun.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Pay4Fun en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __PIX__.
+4. Active la condición en el campo __Status__.
+5. En __Procesar con afiliación__, seleccione la opción __p4fpartnerbr-pay4fun-v0__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Pay4Fun puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-paycash.md b/docs/tutorials/es/setting-up-payments-with-paycash.md
index 496bca3b6..9c0992a2c 100644
--- a/docs/tutorials/es/setting-up-payments-with-paycash.md
+++ b/docs/tutorials/es/setting-up-payments-with-paycash.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Paycash'
 id: 5gxrb0YlEhq0JnprN2uaOf
 status: PUBLISHED
 createdAt: 2023-04-06T17:19:09.254Z
-updatedAt: 2023-04-06T17:57:16.146Z
-publishedAt: 2023-04-06T17:57:16.146Z
+updatedAt: 2024-01-23T21:05:57.921Z
+publishedAt: 2024-01-23T21:05:57.921Z
 firstPublishedAt: 2023-04-06T17:40:32.746Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-paycash
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Paycash. Con este conector, tu tienda puede realizar ventas a través de Paycash.
+En VTEX es posible la integración con el proveedor de pagos Paycash. Con este proveedor, tu tienda puede realizar ventas a través de Paycash.
 
-Para configurar la afiliación Paycash, siga los pasos a continuación:
+Para configurar Paycash, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Paycash__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Paycash__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__, __Application Token__ y __Paycash Production Api Key__ con los datos proporcionados por Paycash. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-payclub.md b/docs/tutorials/es/setting-up-payments-with-payclub.md
index 95b1aead0..cdc536c4a 100644
--- a/docs/tutorials/es/setting-up-payments-with-payclub.md
+++ b/docs/tutorials/es/setting-up-payments-with-payclub.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagos con PayClub'
 id: 3C3bDia3Tyq48MOuMomcUW
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-03T13:12:17.337Z
-updatedAt: 2023-03-28T00:07:06.076Z
-publishedAt: 2023-03-28T00:07:06.076Z
+updatedAt: 2024-03-18T19:14:09.539Z
+publishedAt: 
 firstPublishedAt: 2018-04-03T15:07:32.416Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagos-con-payclub
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Usted puede configurar el [subadquirente](/es/tutorial/que-es-un-subadquirente) PayClub para recibir pagos en su tienda. En esta modalidad, su cliente elige el __medio de pago__ PayClub y realiza la autenticación en el ambiente externo de la solución de pagos.
 
 Para habilitar los pagos con PayClub, siga los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-payments-with-paymentezv2.md b/docs/tutorials/es/setting-up-payments-with-paymentezv2.md
new file mode 100644
index 000000000..526a799c8
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-paymentezv2.md
@@ -0,0 +1,34 @@
+---
+title: 'Configurar pago con PaymentezV2'
+id: 6MQiFTLnSaQoCswRUN1SVe
+status: PUBLISHED
+createdAt: 2024-03-14T12:48:31.013Z
+updatedAt: 2024-03-14T13:10:44.458Z
+publishedAt: 2024-03-14T13:10:44.458Z
+firstPublishedAt: 2024-03-14T13:10:44.458Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-paymentezv2
+locale: es
+legacySlug: configurar-pago-con-paymentezv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PaymentezV2. Con este proveedor, su tienda puede realizar ventas a través de TuyaPay, tarjetas (crédito, tienda cobranded, tienda red propia) y pagarés.
+
+Para configurar PaymentezV2, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PaymentezV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por PaymentezV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PaymentezV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por PaymentezV2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PaymentezV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-paypalv2.md b/docs/tutorials/es/setting-up-payments-with-paypalv2.md
new file mode 100644
index 000000000..666b0a705
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-paypalv2.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurar pago con PayPalV2'
+id: 2nGiQVk3YKvOAu8Zg4RKFr
+status: PUBLISHED
+createdAt: 2024-03-14T18:53:09.449Z
+updatedAt: 2024-07-24T19:40:23.978Z
+publishedAt: 2024-07-24T19:40:23.978Z
+firstPublishedAt: 2024-03-14T19:02:53.958Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-paypalv2
+locale: es
+legacySlug: configurar-pago-con-paypalv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PayPalV2. A través de este proveedor, su tienda puede realizar ventas mediante PayPalCP y PayPal.
+
+Para configurar PayPalV2, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __paypal-v2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por PayPalV2. En el entorno de Paypal, la __Clave de aplicación__ corresponde al __Client ID__ y el __Token de aplicación__ se refiere al __Secret__.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PayPalV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. Haga clic en __Guardar__.
+
+Para configurar los métodos de pago a procesar por PayPalV2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PayPalV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-payu-india.md b/docs/tutorials/es/setting-up-payments-with-payu-india.md
index fcece6f40..fcf4f804a 100644
--- a/docs/tutorials/es/setting-up-payments-with-payu-india.md
+++ b/docs/tutorials/es/setting-up-payments-with-payu-india.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pago con PayU India'
 id: 7JFaP3jBukdZHWel9p7dKX
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-08-15T12:33:46.519Z
-updatedAt: 2023-03-21T20:56:57.589Z
-publishedAt: 2023-03-21T20:56:44.797Z
+updatedAt: 2024-01-25T19:21:08.479Z
+publishedAt: 2024-01-25T19:21:08.479Z
 firstPublishedAt: 2022-08-15T14:38:06.151Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,17 @@ legacySlug: configurar-pago-con-payu-india
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos PayU India. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito y pagarés.
+En VTEX es posible la integración con el proveedor de pagos PayU India. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y pagarés.
 
-Para configurar la afiliación PayU India, siga los pasos a continuación:
+Para configurar PayU India, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en el conector __PayuIndia__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PayuIndia__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__, __Application Token__, __Public API Key__, __Soft descriptor__ y __Type of refund__ con los datos proporcionados por PayU India.
 >7. En el campo __Early capture<__, elija cuánto tiempo desea que se produzca la captura (después de que la transacción haya sido aprobada y el análisis antifraude). También puede desactivar la función.
 6. En __¿Have an anti-fraud deal with this affiliation?__, seleccione si su tienda utilizará un acuerdo antifraude con este conector.
-7. Haga clic en __Guardar__.
+7. Haga clic en `Guardar`.
 
 Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#).
 
diff --git a/docs/tutorials/es/setting-up-payments-with-payuv2.md b/docs/tutorials/es/setting-up-payments-with-payuv2.md
new file mode 100644
index 000000000..3769141ea
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-payuv2.md
@@ -0,0 +1,48 @@
+---
+title: 'Configurar pago con PayUv2'
+id: 7twMgKUZZtJGmR72wS1k3n
+status: PUBLISHED
+createdAt: 2024-03-08T18:30:40.587Z
+updatedAt: 2024-03-13T15:35:06.533Z
+publishedAt: 2024-03-13T15:35:06.533Z
+firstPublishedAt: 2024-03-08T18:47:05.125Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-payuv2
+locale: es
+legacySlug: configurar-pago-con-payuv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PayUv2. Con este proveedor, su tienda puede realizar ventas a través de tarjetas (crédito, débito, tienda cobranded, tienda red propia), pagarés y boletos.
+
+Para configurar PayUv2 siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PayUv2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta PayUv2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PayUv2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. Si desea utilizar [Split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx) en su tienda, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
+9. En __Campos de proveedor__, en el campo __Tipo Autorizacion__, seleccione si sus transacciones de pago se ejecutan en flujos de uno o dos pasos. Para flujos de un solo paso, seleccione __Autorización y Captura__. Para flujos de dos pasos, seleccione __Pre-Autorizacion__.
+10. En __Public Key__, ingresa tu clave API de PayU.
+11. En __Idioma__, seleccione qué idioma se debe utilizar en el sistema PayU.
+12. En __Expiración pago (días)__, seleccione el período en el que desea configurar el vencimiento de los pagos realizados mediante pagarés.
+13. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por PayUv2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PayUv2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-payway.md b/docs/tutorials/es/setting-up-payments-with-payway.md
new file mode 100644
index 000000000..9c3204e0d
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-payway.md
@@ -0,0 +1,37 @@
+---
+title: 'Configurar pago con Payway'
+id: wHkvX7olfPPsAdeFq7obp
+status: PUBLISHED
+createdAt: 2024-03-07T17:04:59.563Z
+updatedAt: 2024-03-13T15:29:48.955Z
+publishedAt: 2024-03-13T15:29:48.955Z
+firstPublishedAt: 2024-03-07T19:10:55.092Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-payway
+locale: es
+legacySlug: configurar-pago-con-payway
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Payway. Con este proveedor, su tienda puede realizar ventas a través de PayWay, tarjetas (crédito, débito, tienda cobranded, tienda red propia), pagarés y boletos.
+
+Para configurar Payway siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Payway__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Payway.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Payway en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Campos del Proveedor__, ingrese la información __User ID__, __Consume Username (PUBLIC)__ y __Consume Username (PRIVATE)__ según la información de su cuenta Payway.
+8. En __Payment type__, seleccione la opción __Simple Payment__ o __Two Steps Payment__.
+9. En __Do you use Cybersource?__, seleccione si desea utilizar Cybersource como su proveedor antifraude.
+10. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Payway, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Payway puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-picpay.md b/docs/tutorials/es/setting-up-payments-with-picpay.md
index 1bd6c5c81..7bf33d45e 100644
--- a/docs/tutorials/es/setting-up-payments-with-picpay.md
+++ b/docs/tutorials/es/setting-up-payments-with-picpay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con PicPay'
 id: 5jd6wgPCaWm8IcguyCyaY2
 status: PUBLISHED
 createdAt: 2018-03-13T15:53:25.279Z
-updatedAt: 2023-03-29T01:02:29.955Z
-publishedAt: 2023-03-29T01:02:29.955Z
+updatedAt: 2024-01-23T21:16:28.952Z
+publishedAt: 2024-01-23T21:16:28.952Z
 firstPublishedAt: 2018-03-13T19:36:37.769Z
 contentType: tutorial
 productTeam: Financial
@@ -17,16 +17,16 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 PicPay es una [cartera digital](/es/faq/que-es-una-cartera-digital) que permite la transferencia de valores entre usuarios, incluyendo establecimientos comerciales. Su cliente elige pagar con ella y recibe un código para escanear usando la aplicación para smartphones.
 
-Para configurar pagos con esta cartera digital, primero usted debe registrar la afiliación de gateway __PicPay__ siguiendo los pasos abajo:
+Para configurar PicPay, siga los pasos a continuación:
 
-## Configurar la afiliación de gateway PicPay
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __PicPay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PicPay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos _Application Key_ y _Application Token_ con la información de su cuenta __PicPay__.
-5. Haga clic en __Guardar__.
+5. Haga clic en `Guardar`.
 
 ## Configurar la condición de pago
+
 1. Dentro de los __Configuración__ del módulo Pagos, haga clic en la pestaña __Planes de pago__.
 2. Haga clic en el botón __+__.
 3. Seleccione el medio de pago __PicPay__.
diff --git a/docs/tutorials/es/setting-up-payments-with-pine-labs.md b/docs/tutorials/es/setting-up-payments-with-pine-labs.md
index 49dac51d7..027866473 100644
--- a/docs/tutorials/es/setting-up-payments-with-pine-labs.md
+++ b/docs/tutorials/es/setting-up-payments-with-pine-labs.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Pine Labs'
 id: 6cmZ0Qs9HUpN7AUBZQDmc0
 status: PUBLISHED
 createdAt: 2023-04-03T17:01:53.868Z
-updatedAt: 2023-04-14T12:48:59.843Z
-publishedAt: 2023-04-14T12:48:59.843Z
+updatedAt: 2024-01-25T19:11:09.123Z
+publishedAt: 2024-01-25T19:11:09.123Z
 firstPublishedAt: 2023-04-03T17:17:06.240Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-pine-labs
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Pine Labs. Con este conector, su tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y pagarés.
+En VTEX es posible la integración con el proveedor de pagos Pine Labs. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y pagarés.
 
-Para configurar la afiliación Pine Labs, siga los pasos a continuación:
+Para configurar Pine Labs, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Pinelabs connector__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Pinelabs connector__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta Pine Labs.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-poolpay.md b/docs/tutorials/es/setting-up-payments-with-poolpay.md
new file mode 100644
index 000000000..fea09a0f3
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-poolpay.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pago con PoolPay'
+id: 5N3llK2tpVPKdfJvOIJmQ0
+status: PUBLISHED
+createdAt: 2023-09-11T14:36:06.412Z
+updatedAt: 2024-01-25T17:26:19.086Z
+publishedAt: 2024-01-25T17:26:19.086Z
+firstPublishedAt: 2023-09-11T14:58:37.086Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-poolpay
+locale: es
+legacySlug: configurar-pago-con-poolpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos PoolPay. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de credito, PIX, ITP (Iniciador de transacciones de pago brasileño) y BNPL (Buy Now Pay Later).
+
+Para configurar PoolPay, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PoolPay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__ and __Application Token__ con los datos proporcionados por el PoolPay.
+5. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+6. Haga clic en `Salvar`.
+
+Para configurar los métodos de pago a procesar por PoolPay, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, PoolPay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-powerpay.md b/docs/tutorials/es/setting-up-payments-with-powerpay.md
new file mode 100644
index 000000000..b8b5bac68
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-powerpay.md
@@ -0,0 +1,50 @@
+---
+title: 'Configurar pago con Powerpay'
+id: 4v3ohBfSTxIyi06aqvlrPp
+status: PUBLISHED
+createdAt: 2023-09-08T18:31:43.851Z
+updatedAt: 2024-01-23T21:22:03.339Z
+publishedAt: 2024-01-23T21:22:03.339Z
+firstPublishedAt: 2023-09-08T19:50:37.486Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-powerpay
+locale: es
+legacySlug: configurar-pago-con-powerpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Powerpay. Con este proveedor, su tienda puede realizar ventas a través de diferentes de Powerpay.
+
+Para configurar Powerpay, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Powerpay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__, __Application Token__, __secretKey__ y __merchant_id__ con los datos proporcionados por el Powerpay.
+5. En el campo __Captura automática de pago__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza El Comportamiento Recomendado Por El Procesador de Pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Imediatamente: Captura Automática Al Autorizar El Pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Imediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Captura automática al autorizar el pago").</li>
+   		<li><b>Programado: Establece Cuándo Se Realizará La Captura Automática</b>: al seleccionar esta opción, se mostrará el campo <b>Periodo de tiempo programado en horas para la captura automática</b>, que deberá rellenarse con el periodo en el que se realizará la captura automática. Este periodo debe respetar los límites permitidos por el proveedor de pagos.</li>        
+   		<li><b>Desactivado: No Capturado Automáticamente</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+6. En __¿Activar split y enviar receptores?__, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.
+
+7. Haga clic en __Salvar__.
+
+## Configurar condición de pago
+
+1. En el Admin VTEX, accede a __Configuración de la tienda__ > __Pago__ > __Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
+3. Elige la condición de pago __Powerpay__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en __Guardar__.
+
+Después de seguir los pasos indicados, Powerpay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-puntos-colombia.md b/docs/tutorials/es/setting-up-payments-with-puntos-colombia.md
index c8957fbe6..61dbbfce8 100644
--- a/docs/tutorials/es/setting-up-payments-with-puntos-colombia.md
+++ b/docs/tutorials/es/setting-up-payments-with-puntos-colombia.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Puntos Colombia'
 id: 5lj66uK0w5XxfzfncEyhP6
 status: PUBLISHED
 createdAt: 2022-03-17T14:14:06.885Z
-updatedAt: 2023-03-26T21:55:55.409Z
-publishedAt: 2023-03-26T21:55:55.409Z
+updatedAt: 2024-01-25T17:08:21.898Z
+publishedAt: 2024-01-25T17:08:21.898Z
 firstPublishedAt: 2022-03-17T14:23:01.073Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-puntos-colombia
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Puntos Colombia. Con este conector tu tienda podrá realizar ventas a través del programa de fidelización Puntos Colombia.
+En VTEX es posible la integración con el proveedor de pagos Puntos Colombia. Con este proveedor, tu tienda podrá realizar ventas a través del programa de fidelización Puntos Colombia.
 
-Para configurar la afiliación Puntos Colombia, siga los pasos a continuación:
+Para configurar Puntos Colombia, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
-3. Haga clic en el conector __PuntosColombia__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PuntosColombia__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Puntos Colombia.
 5. Haga clic en __Guardar__.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-qhantuy.md b/docs/tutorials/es/setting-up-payments-with-qhantuy.md
index 5b6b3979b..a7f4c13e0 100644
--- a/docs/tutorials/es/setting-up-payments-with-qhantuy.md
+++ b/docs/tutorials/es/setting-up-payments-with-qhantuy.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Qhantuy'
 id: 4KO2beK0scqVy4lrrs3Myq
 status: PUBLISHED
 createdAt: 2023-04-20T13:44:39.377Z
-updatedAt: 2023-04-20T17:36:03.040Z
-publishedAt: 2023-04-20T17:36:03.040Z
+updatedAt: 2024-01-24T17:10:50.292Z
+publishedAt: 2024-01-24T17:10:50.292Z
 firstPublishedAt: 2023-04-20T14:12:44.589Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-qhantuy
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Qhantuy. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito y Qhantuy.
+En VTEX es posible la integración con el proveedor de pagos Qhantuy. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y Qhantuy.
 
-Para configurar la afiliación Qhantuy, siga los pasos a continuación:
+Para configurar Qhantuy, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Qhantuy__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Qhantuy__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Qhantuy. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-retrypay.md b/docs/tutorials/es/setting-up-payments-with-retrypay.md
index 688eb64ce..2d478aa49 100644
--- a/docs/tutorials/es/setting-up-payments-with-retrypay.md
+++ b/docs/tutorials/es/setting-up-payments-with-retrypay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Retrypay'
 id: 3QGioVKVI1Qnk3JbbJlJVY
 status: PUBLISHED
 createdAt: 2023-03-30T19:35:06.661Z
-updatedAt: 2023-03-30T20:01:51.283Z
-publishedAt: 2023-03-30T20:01:51.283Z
+updatedAt: 2024-02-08T14:23:02.038Z
+publishedAt: 2024-02-08T14:23:02.038Z
 firstPublishedAt: 2023-03-30T20:01:51.283Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-retrypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Retrypay. Con este conector, tu tienda puede realizar ventas a través de pagarés y Retrypay.
+En VTEX es posible la integración con el proveedor de pagos Retrypay. Con este proveedor, tu tienda puede realizar ventas a través de pagarés y Retrypay.
 
-Para configurar la afiliación Retrypay, siga los pasos a continuación:
+Para configurar Retrypay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __RetryPay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __RetryPay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__, __Application Token__, __Tenant__, __Retripay Merchant API Key__ y __Retripay Hook Token__ con los datos proporcionados por Retrypay. 
 5. En __Payment Method__, elija una de dos opciones: __Redirect__ o __Payment App__.
 6. En __Environment__, elija una de dos opciones: __Demo__ o __Production__.
@@ -29,7 +29,7 @@ Para configurar la afiliación Retrypay, siga los pasos a continuación:
 
 ## Configurar la condición de pago Pagaré
 
-Si quieres utilizar Retrypay con pagaré y no has configurado el pagaré como método de pago en otros conectores de tu tienda, accede a [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ).
+Si quieres utilizar Retrypay con pagaré y no has configurado el pagaré como método de pago en otros proveedores de tu tienda, accede a [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare).
 
 Luego siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-safetypayv2.md b/docs/tutorials/es/setting-up-payments-with-safetypayv2.md
new file mode 100644
index 000000000..c69fa99d4
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-safetypayv2.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pago con SafetyPayV2'
+id: 5VBwbJODDKJ6zIW5a23l8V
+status: PUBLISHED
+createdAt: 2024-03-14T17:24:16.678Z
+updatedAt: 2024-03-14T17:44:09.769Z
+publishedAt: 2024-03-14T17:44:09.769Z
+firstPublishedAt: 2024-03-14T17:41:17.188Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-safetypayv2
+locale: es
+legacySlug: configurar-pago-con-safetypayv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos SafetyPayV2. Con este proveedor, su tienda puede realizar ventas a través de SafetyPayV2 y lotería.
+
+Para configurar SafetyPayV2, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __SafetyPayV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por SafetyPayV2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor SafetyPayV2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por SafetyPayV2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, SafetyPayV2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-scalapay.md b/docs/tutorials/es/setting-up-payments-with-scalapay.md
index 7a1fa2a2a..97effe0b0 100644
--- a/docs/tutorials/es/setting-up-payments-with-scalapay.md
+++ b/docs/tutorials/es/setting-up-payments-with-scalapay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Scalapay'
 id: 6SCh3WUqjeqIrOl209MENA
 status: PUBLISHED
 createdAt: 2022-08-12T19:31:38.569Z
-updatedAt: 2023-05-09T14:07:50.542Z
-publishedAt: 2023-05-09T14:07:50.542Z
+updatedAt: 2024-01-25T18:03:45.856Z
+publishedAt: 2024-01-25T18:03:45.856Z
 firstPublishedAt: 2022-08-12T19:39:58.598Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-pago-con-scalapay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Scalapay. Con este conector, tu tienda puede realizar ventas a través de tarjeta de crédito y Scalapay.
+En VTEX es posible la integración con el proveedor de pagos Scalapay. Con este proveedor, tu tienda puede realizar ventas a través de tarjeta de crédito y Scalapay.
 
-Para configurar la afiliación Scalapay, siga los pasos a continuación:
+Para configurar Scalapay, siga los pasos a continuación:
 
-<ui>1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.</ui>
+<ui>1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.</ui>
 
-<ui>2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.</ui>
+<ui>2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.</ui>
 
-<ui>3. Haga clic en el conector __Scalapay__.</ui>
+<ui>3. Escriba el nombre __Scalapay__ en la barra de búsqueda y haga clic en el nombre del proveedor.</ui>
 
 <ui>4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Scalapay.</ui>
 
@@ -34,7 +34,7 @@ Para configurar la afiliación Scalapay, siga los pasos a continuación:
  - __Inmediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude__: la captura se realiza automáticamente inmediatamente después de la autorización del pago y el análisis antifraude. Si desea utilizar esta opción y no hay que realizar un análisis antifraude, el sistema seguirá el mismo flujo que la opción __Inmediatamente: Captura Automática Al Autorizar El Pagamento__. 
  - __Desactivado: No Capturado Automáticamente__: la captura se produce sólo cuando se factura el pedido. Si desea utilizar esta opción, es importante prestar atención al momento de la facturación, ya que si el pedido se factura por un período mayor al acordado con el proveedor para capturar el pago, la transacción puede cancelarse.
 
-<ui>6. Haga clic en __Guardar__.</ui>
+<ui>6. Haga clic en `Guardar`.</ui>
 
 Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condicoes-de-pagamento#). Para la opción de tarjeta de crédito, seleccione la afiliación __vtex-integration-scalapay-v0__.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-shipay.md b/docs/tutorials/es/setting-up-payments-with-shipay.md
index 178da9f9e..834fb2023 100644
--- a/docs/tutorials/es/setting-up-payments-with-shipay.md
+++ b/docs/tutorials/es/setting-up-payments-with-shipay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Shipay'
 id: 2GVBCDdxZPexI2TikFf9Au
 status: PUBLISHED
 createdAt: 2023-03-27T14:40:05.161Z
-updatedAt: 2023-03-27T16:15:57.347Z
-publishedAt: 2023-03-27T16:15:57.347Z
+updatedAt: 2024-01-23T21:27:19.732Z
+publishedAt: 2024-01-23T21:27:19.732Z
 firstPublishedAt: 2023-03-27T14:44:22.502Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-shipay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Shipay. Con este conector, su tienda puede realizar ventas a través de PIX.
+En VTEX es posible la integración con el proveedor de pagos Shipay. Con este proveedor, su tienda puede realizar ventas a través de PIX.
 
-Para configurar la afiliación Shipay, siga los pasos a continuación:
+Para configurar Shipay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Shipay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Shipay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta Shipay.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
diff --git a/docs/tutorials/es/setting-up-payments-with-sibs.md b/docs/tutorials/es/setting-up-payments-with-sibs.md
index ac4bdaff2..aab21c329 100644
--- a/docs/tutorials/es/setting-up-payments-with-sibs.md
+++ b/docs/tutorials/es/setting-up-payments-with-sibs.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con SIBS'
 id: sNLPtJlAMnDpq40CCPKNo
 status: PUBLISHED
 createdAt: 2023-04-06T18:57:27.591Z
-updatedAt: 2023-04-06T19:07:28.327Z
-publishedAt: 2023-04-06T19:07:28.327Z
+updatedAt: 2024-01-25T19:05:01.739Z
+publishedAt: 2024-01-25T19:05:01.739Z
 firstPublishedAt: 2023-04-06T19:07:28.327Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-sibs
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos SIBS. Con este conector, tu tienda puede realizar ventas a través de tarjeta de crédito SIBS, pagarés, MBWay y MultiBanco.
+En VTEX es posible la integración con el proveedor de pagos SIBS. Con este proveedor, tu tienda puede realizar ventas a través de tarjeta de crédito SIBS, pagarés, MBWay y MultiBanco.
 
-Para configurar la afiliación SIBS, siga los pasos a continuación:
+Para configurar SIBS, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __SIBS__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __SIBS__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por SIBS. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-stark-bank.md b/docs/tutorials/es/setting-up-payments-with-stark-bank.md
new file mode 100644
index 000000000..bb5fb8ba9
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-stark-bank.md
@@ -0,0 +1,34 @@
+---
+title: 'Configurar pago con Stark Bank'
+id: 19pwHHVuEGN743WOGXcbUM
+status: PUBLISHED
+createdAt: 2023-09-08T15:29:02.297Z
+updatedAt: 2024-01-23T21:44:38.751Z
+publishedAt: 2024-01-23T21:44:38.751Z
+firstPublishedAt: 2023-09-08T15:45:11.373Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-stark-bank
+locale: es
+legacySlug: configurar-pago-con-stark-bank
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Stark Bank. Con este proveedor, su tienda puede realizar ventas a través de boletos bancarios y PIX.
+
+Para configurar Stark Bank, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __StarkBank__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Si aparece un mensaje de alerta indicando la necesidad de instalar la aplicación, haz clic en el botón __Instalar aplicación__ y sigue las instrucciones para hacerlo.
+5. Haga clic en __Autorizar__. Usted será redirigido al entorno de Stark Bank.
+6. En el entorno de Stark Bank, ingrese el nombre de usuario y ça contraseña de su cuenta de Stark Bank. Siga las instrucciones indicadas para completar la vinculación de la cuenta Stark Bank con VTEX.
+7. Al regresar a __Admin VTEX__, haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Stark Bank, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Stark Bank puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-stelo.md b/docs/tutorials/es/setting-up-payments-with-stelo.md
index 747568902..31f89d0d9 100644
--- a/docs/tutorials/es/setting-up-payments-with-stelo.md
+++ b/docs/tutorials/es/setting-up-payments-with-stelo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagos con Stelo'
 id: 6c16nRhAGWaA2mSUOOuC00
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T20:20:44.376Z
-updatedAt: 2023-03-29T01:07:31.337Z
-publishedAt: 2023-03-29T01:07:31.337Z
+updatedAt: 2024-03-18T20:21:28.181Z
+publishedAt: 
 firstPublishedAt: 2018-03-05T19:08:32.807Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagos-con-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Además de un [subadquirente](/es/tutorial/configurar-subadquirente-stelo) para procesar transacciones realizadas con diversas condiciones de pago, Stelo también ofrece un servicio de [cartera digital](/es/faq/que-es-una-cartera-digital). Su cliente elige pagar con ella y se redirige a la autenticación en el ambiente de Stelo.
 
 Para configurar pagos con la cartera digital Stelo en su tienda, primero usted debe registrar la afiliación de gateway __Stelo Redirect__.
diff --git a/docs/tutorials/es/setting-up-payments-with-stelom1v2.md b/docs/tutorials/es/setting-up-payments-with-stelom1v2.md
new file mode 100644
index 000000000..13f884a02
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-stelom1v2.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pago con SteloM1V2'
+id: 1lO9Rn87U0iyBTCpgBlqYD
+status: PUBLISHED
+createdAt: 2024-03-14T13:56:38.010Z
+updatedAt: 2024-03-14T14:05:14.839Z
+publishedAt: 2024-03-14T14:05:14.839Z
+firstPublishedAt: 2024-03-14T14:05:14.839Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-stelom1v2
+locale: es
+legacySlug: configurar-pago-con-stelom1v2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos SteloM1V2. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito y boletos.
+
+Para configurar SteloM1V2, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __SteloM1V2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por SteloM1V2.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor SteloM1V2 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por SteloM1V2, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, SteloM1V2 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md b/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md
index 0c166ca54..352caadf4 100644
--- a/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md
+++ b/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md
@@ -3,8 +3,8 @@ title: 'Configurar pagos con Tarjeta de Tienda (cobranded)'
 id: jrkLK41IjuquUmyKUi86Q
 status: PUBLISHED
 createdAt: 2018-06-25T15:48:13.031Z
-updatedAt: 2023-03-22T19:19:30.029Z
-publishedAt: 2023-03-22T19:19:30.029Z
+updatedAt: 2023-09-22T21:25:38.666Z
+publishedAt: 2023-09-22T21:25:38.666Z
 firstPublishedAt: 2018-06-27T20:17:05.882Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,11 +26,18 @@ El primer paso de configuración será la creación del pago personalizado  __ta
 3. En __tarjetas de tienda (cobranded)__, haga clic en una de las 5 cajas de configuración de pago.
 4. En __Nombre__, rellene el nombre de la tarjeta.
 5. En __Descripción__, escriba el texto que dará más detalles sobre la condición de pago.
-6. En __Bandera de la tarjeta__, escoja la franquicia a la cual la tarjeta de su tienda está vinculada. Actualmente, las franquicias posibles son: American Express, Cabal, Diners, Elo, Mastercard y Visa.
-7. En __Pistas de Bin__ informe los códigos BIN de las tarjetas para que sean validados por el sistema. Usted puede ingresar un rango de BINs (ingresando el primer y último código de la secuencia, separados por un guion) o varios (separando cada rango por coma y sin espacios). Si lo prefiere, usted puede usar el validador de la tarjeta co-branded, rellenando los valores `100000-999999`.
-8. En el campo __Código de pago del adquiriente (opcional)__, indique el código a ser enviado y procesado por el adquiriente contratado por usted.
-9. En __Activar split de pago__, si eliges usar esta opción, cuando la venta se produzca en tiendas del marketplace, el pagaré se dividirá entre los sellers y el marketplace.
-10. Haga clic en __Salva__.
+6. En __Red de la tarjeta__, escoja la franquicia a la cual la tarjeta de su tienda está vinculada. Actualmente, las franquicias posibles son: American Express, Cabal, Diners, Elo, Mastercard y Visa.
+7. En __Rangos de Bin (opcional)__, puedes ingresar un rango de BIN (ingresando el primer y último código de la secuencia, separados por un guión) o varios (separando cada rango por una coma y sin espacios).
+
+<div class="alert alert-warning">
+  Cuando el cliente ingresa un número de contenedor fuera del rango especificado en este campo, se mostrará el siguiente mensaje "Verifique los dígitos impresos en su tarjeta. No pudimos confirmar si el número de la tarjeta es correcto". Si no hay ningún error en el número ingresado, podrán hacer clic en "SÍ, EL NÚMERO DE LA TARJETA ES CORRECTO" para continuar completando el pedido.
+</div>
+
+<blockquote><ui>8. En el campo <b>Código de pago del adquiriente (opcional)</b>, indique el código a ser enviado y procesado por el adquiriente contratado por usted.</ui>
+
+<blockquote><ui>9. En <b>Activar split de pago</b>, si eliges usar esta opción, cuando la venta se produzca en tiendas del marketplace, el pagaré se dividirá entre los sellers y el marketplace.</ui>
+
+<blockquote><ui>10. Haga clic en __Guardar__.</ui>
 
 ## Configurar condición de pago
 Después de configurar la tarjeta, deberá configurar la condición de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-transfero-crypto-checkout.md b/docs/tutorials/es/setting-up-payments-with-transfero-crypto-checkout.md
new file mode 100644
index 000000000..4e2faa48d
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-transfero-crypto-checkout.md
@@ -0,0 +1,49 @@
+---
+title: 'Configurar pago con Transfero Crypto Checkout'
+id: 29ZW22EW09zQDWZlPdyZ1T
+status: PUBLISHED
+createdAt: 2024-04-17T18:14:15.873Z
+updatedAt: 2024-04-17T18:44:01.978Z
+publishedAt: 2024-04-17T18:44:01.978Z
+firstPublishedAt: 2024-04-17T18:44:01.978Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-transfero-crypto-checkout
+locale: es
+legacySlug: configurar-pago-con-transfero-crypto-checkout
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el procesador de pagos Transfero Crypto Checkout. A través de él, tu tienda podrá realizar ventas a través de criptomonedas y PIX, y recibir en [dinero Fíat](https://es.wikipedia.org/wiki/Dinero_por_decreto).
+
+Para configurar Transfero Crypto Checkout, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __CryptoCheckout__ en la barra de búsqueda y haga clic en el nombre del procesador.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta [Transfero Crypto Checkout](https://onboarding.transfero.com/).
+5. Si desea modificar el nombre de identificación que se mostrará para el procesador Transfero Crypto Checkout en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el procesador en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Transfero Checkout__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, el procesador Transfero Crypto Checkout puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-tyendacrypto.md b/docs/tutorials/es/setting-up-payments-with-tyendacrypto.md
index 4c5d6e72d..fdf8f2ebd 100644
--- a/docs/tutorials/es/setting-up-payments-with-tyendacrypto.md
+++ b/docs/tutorials/es/setting-up-payments-with-tyendacrypto.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con TiendaCrypto'
 id: 7qC52v2j7q7B0YUtLnW2I9
 status: PUBLISHED
 createdAt: 2023-05-26T18:19:21.462Z
-updatedAt: 2023-05-26T22:40:14.439Z
-publishedAt: 2023-05-26T22:40:14.439Z
+updatedAt: 2024-01-24T13:32:40.359Z
+publishedAt: 2024-01-24T13:32:40.359Z
 firstPublishedAt: 2023-05-26T18:43:41.573Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-tyendacrypto
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos TiendaCrypto. Con este conector, tu tienda puede realizar ventas a través de criptomonedas.
+En VTEX es posible la integración con el proveedor de pagos TiendaCrypto. Con este proveedor, tu tienda puede realizar ventas a través de criptomonedas.
 
-Para configurar la afiliación TiendaCrypto, siga los pasos a continuación:
+Para configurar TiendaCrypto, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __TiendaCrypto__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __TiendaCrypto__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Haga clic en Autorizar. Usted será redirigido al entorno de TiendaCrypto. 
 5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-unlimit.md b/docs/tutorials/es/setting-up-payments-with-unlimit.md
new file mode 100644
index 000000000..6ffe48b94
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-unlimit.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurar pago con Unlimit'
+id: 5emdjkgQOEQruDinUrfXY8
+status: PUBLISHED
+createdAt: 2024-06-05T15:41:23.584Z
+updatedAt: 2024-07-29T15:08:14.122Z
+publishedAt: 2024-07-29T15:08:14.122Z
+firstPublishedAt: 2024-06-06T15:38:46.103Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-unlimit
+locale: es
+legacySlug: configurar-pago-con-unlimit
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Unlimit. A través de este proveedor, tu tienda puede realizar ventas utilizando diferentes métodos de pago, como: tarjetas (crédito, débito, tienda cobranded, tienda red propia), boletos y PIX.
+
+Para configurar Unlimit siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Unlimit__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Unlimit.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Unlimit en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. Haga clic en `Guardar`.
+
+Para configurar los métodos de pago a procesar por Unlimit, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, Unlimit puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-ventipay.md b/docs/tutorials/es/setting-up-payments-with-ventipay.md
index fdc4f44fb..f303cab9f 100644
--- a/docs/tutorials/es/setting-up-payments-with-ventipay.md
+++ b/docs/tutorials/es/setting-up-payments-with-ventipay.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con VentiPay'
 id: 11n076tXgeLa1wDT3n2hyZ
 status: PUBLISHED
 createdAt: 2022-10-18T18:04:20.082Z
-updatedAt: 2023-03-21T20:49:01.107Z
-publishedAt: 2023-03-21T20:49:01.107Z
+updatedAt: 2024-01-24T18:08:16.663Z
+publishedAt: 2024-01-24T18:08:16.663Z
 firstPublishedAt: 2022-10-18T18:28:35.755Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-ventipay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos VentiPay. Con este conector, tu tienda puede realizar ventas a través de VentiPay.
+En VTEX es posible la integración con el proveedor de pagos VentiPay. Con este proveedor, tu tienda puede realizar ventas a través de VentiPay.
 
 Para configurar la afiliación VentiPay, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Ventipay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Ventipay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por VentiPay. 
 5. Haga clic en `Guardar`.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-virtuspay.md b/docs/tutorials/es/setting-up-payments-with-virtuspay.md
index 623912864..53859b598 100644
--- a/docs/tutorials/es/setting-up-payments-with-virtuspay.md
+++ b/docs/tutorials/es/setting-up-payments-with-virtuspay.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pago con VirtusPay'
 id: 2Agqwp19cwyIbxuHErVG8I
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-08-11T15:02:59.728Z
-updatedAt: 2023-03-27T12:42:29.231Z
-publishedAt: 2023-03-26T21:15:04.050Z
+updatedAt: 2024-01-23T21:50:25.883Z
+publishedAt: 2024-01-23T21:50:25.883Z
 firstPublishedAt: 2022-08-11T16:38:04.718Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-payments-with-virtuspayv2.md b/docs/tutorials/es/setting-up-payments-with-virtuspayv2.md
index 0d64f0275..254f1b2cb 100644
--- a/docs/tutorials/es/setting-up-payments-with-virtuspayv2.md
+++ b/docs/tutorials/es/setting-up-payments-with-virtuspayv2.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con VirtusPayV2'
 id: 1tbcLRNIB5Bz0oWl8LnayB
 status: PUBLISHED
 createdAt: 2023-03-27T12:14:53.392Z
-updatedAt: 2023-03-27T12:56:49.578Z
-publishedAt: 2023-03-27T12:56:49.578Z
+updatedAt: 2024-01-23T21:52:05.259Z
+publishedAt: 2024-01-23T21:52:05.259Z
 firstPublishedAt: 2023-03-27T12:56:49.578Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,19 @@ legacySlug: configurar-pago-con-virtuspayv2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos VirtusPayV2. Con este conector, su tienda puede realizar ventas a través de VirtusPay y VirtusPay Transparente.
+En VTEX es posible la integración con el proveedor de pagos VirtusPayV2. Con este proveedor, su tienda puede realizar ventas a través de VirtusPay y VirtusPay Transparente.
 
-Para configurar la afiliación VirtusPayV2, siga los pasos a continuación:
+Para configurar VirtusPayV2, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __VirtusPayV2__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __VirtusPayV2__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__ y __Application Token__ con los datos proporcionados por su cuenta VirtusPay.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
 
 ## Configurar condición de pago
+
 1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
 3. Haga clic en una de las dos condiciones de pago: __VirtusPay__ o __VirtusPay Transparente__.
diff --git a/docs/tutorials/es/setting-up-payments-with-webpayoneclick.md b/docs/tutorials/es/setting-up-payments-with-webpayoneclick.md
new file mode 100644
index 000000000..d3aa81b18
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-webpayoneclick.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pago con WebpayOneClick'
+id: 7jIwDOcBbF3cxIyHKaj4LF
+status: PUBLISHED
+createdAt: 2024-03-07T14:01:33.652Z
+updatedAt: 2024-03-07T15:06:06.370Z
+publishedAt: 2024-03-07T15:06:06.370Z
+firstPublishedAt: 2024-03-07T15:06:06.370Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-webpayoneclick
+locale: es
+legacySlug: configurar-pago-con-webpayoneclick
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos WebpayOneClick. Con este proveedor, su tienda puede realizar ventas a través de Transbank Oneclick.
+
+Para configurar WebpayOneClick siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __WebpayOneClick__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta WebpayOneClick.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor WebpayOneClick en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Transbank Oneclick__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, WebpayOneClick puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-wepay4u.md b/docs/tutorials/es/setting-up-payments-with-wepay4u.md
new file mode 100644
index 000000000..415689dba
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-wepay4u.md
@@ -0,0 +1,52 @@
+---
+title: 'Configurar pago con Wepay4u'
+id: 7xbyIPpU7PAXQNCfpVBqGC
+status: PUBLISHED
+createdAt: 2024-02-05T20:19:10.668Z
+updatedAt: 2024-03-13T15:09:57.098Z
+publishedAt: 2024-03-13T15:09:57.098Z
+firstPublishedAt: 2024-02-05T20:29:59.689Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-wepay4u
+locale: es
+legacySlug: configurar-pago-con-wepay4u
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Wepay4u. Con este proveedor, su tienda puede realizar ventas a través de Wepay4u.
+
+Para configurar Wepay4u siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Wepay4u__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Wepay4u.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Wepay4u en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. En __Campos del proveedor__, ingrese la información __MerchantCode__ y __SecretKey__ según la información de su cuenta Wepay4u.
+
+9. En __Currency__, seleccione la moneda que se utilizará en la transacción de pago.
+
+10. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Wepay4u__.
+4. Active la condición en el campo __Status__.
+5. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+6. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Wepay4u puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-wompi.md b/docs/tutorials/es/setting-up-payments-with-wompi.md
index 9b407c0c0..e75bec62c 100644
--- a/docs/tutorials/es/setting-up-payments-with-wompi.md
+++ b/docs/tutorials/es/setting-up-payments-with-wompi.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Wompi'
 id: 40d6lWEyzLViHS7aYvcsqV
 status: PUBLISHED
 createdAt: 2022-02-21T18:22:13.804Z
-updatedAt: 2023-03-26T22:00:59.701Z
-publishedAt: 2023-03-26T22:00:59.701Z
+updatedAt: 2024-01-24T13:49:31.304Z
+publishedAt: 2024-01-24T13:49:31.304Z
 firstPublishedAt: 2022-02-21T19:06:12.105Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: configurar-pago-con-wompi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Wompi. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito y débito, transacciones bancarias, Nequi y PSE (sistemas de pago colombianos) y corresponsales bancarios.
+En VTEX es posible la integración con el proveedor de pagos Wompi. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y débito, transacciones bancarias, Nequi y PSE (sistemas de pago colombianos) y corresponsales bancarios.
 
-Para configurar la afiliación Wompi, siga los pasos a continuación:
+Para configurar Wompi, siga los pasos a continuación:
 
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón __+__.
 3. Haga clic en el conector __WompiCo__.
 4. Haga clic en __Autorizar__. Usted será redirigido al entorno de Wompi. 
 5. En el entorno de Wompi, ingrese el nombre de usuario y ça contraseña de su cuenta de Wompi y haga clic en __Vincular cuenta__. Siga las instrucciones indicadas para completar la vinculación de la cuenta Wompi con VTEX.
-6. Al regresar a VTEX Admin, haga clic en __Guardar__.
+6. Al regresar a VTEX Admin, haga clic en `Guardar`.
 
 ## Configurar condición de pago
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
diff --git a/docs/tutorials/es/setting-up-payments-with-wompicov2.md b/docs/tutorials/es/setting-up-payments-with-wompicov2.md
index 88a5b8509..b83ac6004 100644
--- a/docs/tutorials/es/setting-up-payments-with-wompicov2.md
+++ b/docs/tutorials/es/setting-up-payments-with-wompicov2.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con WompiCoV2'
 id: SnkXNUXkESqKxfFZu0LS4
 status: PUBLISHED
 createdAt: 2023-04-14T13:55:18.776Z
-updatedAt: 2023-04-14T14:23:30.858Z
-publishedAt: 2023-04-14T14:23:30.858Z
+updatedAt: 2024-01-24T13:54:46.662Z
+publishedAt: 2024-01-24T13:54:46.662Z
 firstPublishedAt: 2023-04-14T14:23:30.858Z
 contentType: tutorial
 productTeam: Financial
@@ -15,9 +15,9 @@ legacySlug: configurar-pago-con-wompicov2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos WompiCoV2. Con este conector, su tienda puede realizar ventas a través de tarjetas de crédito y debito.
+En VTEX es posible la integración con el proveedor de pagos WompiCoV2. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito y debito.
 
-Para configurar la afiliación WompiCoV2, siga los pasos a continuación:
+Para configurar WompiCoV2, siga los pasos a continuación:
 
 1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
diff --git a/docs/tutorials/es/setting-up-payments-with-woovi.md b/docs/tutorials/es/setting-up-payments-with-woovi.md
new file mode 100644
index 000000000..072a60997
--- /dev/null
+++ b/docs/tutorials/es/setting-up-payments-with-woovi.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pago con Woovi'
+id: a61xxlOLJTQRrPx2MrVfs
+status: PUBLISHED
+createdAt: 2023-09-08T17:29:33.321Z
+updatedAt: 2024-01-23T21:54:32.467Z
+publishedAt: 2024-01-23T21:54:32.467Z
+firstPublishedAt: 2023-09-08T17:49:01.961Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pago-con-woovi
+locale: es
+legacySlug: configurar-pago-con-woovi
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+En VTEX es posible la integración con el proveedor de pagos Woovi. Con este proveedor, su tienda puede realizar ventas a través de Woovi y Woovi Parcelado.
+
+Para configurar Woovi, siga los pasos a continuación:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __WooviConnector__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Token__, __Application Token__ y __App ID__ con los datos proporcionados por su cuenta Woovi.
+5. En __Method__, seleccione __Pix__ o __Woovi Parcelado__.
+6. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
+7. Haga clic en `Guardar`.
+
+## Configurar condición de pago
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestana __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __Woovi__ o __Woovi Parcelado__.
+4. Active la condición en el campo __Status__.
+5. Si desea utilizar un sistema antifraude, seleccione la opción __Utilizar antifraude__.
+6. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, Woovi puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payments-with-yuno.md b/docs/tutorials/es/setting-up-payments-with-yuno.md
index 6037bb1ab..cd5ce3b30 100644
--- a/docs/tutorials/es/setting-up-payments-with-yuno.md
+++ b/docs/tutorials/es/setting-up-payments-with-yuno.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Yuno'
 id: h7PS0vDJJokqI9axZPNzE
 status: PUBLISHED
 createdAt: 2023-04-14T12:42:43.736Z
-updatedAt: 2023-04-14T13:21:45.782Z
-publishedAt: 2023-04-14T13:21:45.782Z
+updatedAt: 2024-01-23T21:56:16.050Z
+publishedAt: 2024-01-23T21:56:16.050Z
 firstPublishedAt: 2023-04-14T13:21:45.782Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pago-con-yuno
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Yuno. Con este conector, su tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y pagarés.
+En VTEX es posible la integración con el proveedor de pagos Yuno. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y pagarés.
 
-Para configurar la afiliación Yuno, siga los pasos a continuación:
+Para configurar Yuno, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Yuno__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Yuno__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Token__, __Application Token__ y __Account ID__ con los datos proporcionados por su cuenta Yuno.
 5. En __Auto Capture__, seleccione si la captura del pago será automática después de la autorización.
 6. En __Delay To Capture (in days) Default 1 day, max 7 days__, indique el período (en días) que debe esperar para que se realice la captura del pago. El valor predeterminado es 1 día y el máximo es 7 días.
diff --git a/docs/tutorials/es/setting-up-payments-with-zenki.md b/docs/tutorials/es/setting-up-payments-with-zenki.md
index 89ee2e0f2..f40d58c6d 100644
--- a/docs/tutorials/es/setting-up-payments-with-zenki.md
+++ b/docs/tutorials/es/setting-up-payments-with-zenki.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Zenki'
 id: 6LK7wMg0OB39UQKoZILoNL
 status: PUBLISHED
 createdAt: 2023-03-30T17:34:01.758Z
-updatedAt: 2023-03-30T18:04:59.870Z
-publishedAt: 2023-03-30T18:04:59.870Z
+updatedAt: 2024-01-25T18:50:47.590Z
+publishedAt: 2024-01-25T18:50:47.590Z
 firstPublishedAt: 2023-03-30T18:02:25.796Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,19 @@ legacySlug: configurar-pago-con-zenki
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Zenki. Con este conector, su tienda puede realizar ventas a través de bitcoins.
+En VTEX es posible la integración con el proveedor de pagos Zenki. Con este proveedor, su tienda puede realizar ventas a través de bitcoins.
 
-Para configurar la afiliación Zenki, siga los pasos a continuación:
+Para configurar Zenki, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
-2. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-3. Haga clic en el conector __Zenki__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Zenki__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro __Application Key__, __Application Token__, __API key__, __Secret Key__ y __Webhook signing secret__ con los datos proporcionados por su cuenta Zenki.
 5. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 6. Haga clic en `Guardar`.
 
 ## Configurar condición de pago
+
 1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Configuración__, o escribe __Configuración__ en la barra de búsqueda en la parte superior de la página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
 3. Haga clic en __Bitcoin__.
diff --git a/docs/tutorials/es/setting-up-payments-with-zoop.md b/docs/tutorials/es/setting-up-payments-with-zoop.md
index b5f7c77c7..1c351ea4a 100644
--- a/docs/tutorials/es/setting-up-payments-with-zoop.md
+++ b/docs/tutorials/es/setting-up-payments-with-zoop.md
@@ -3,8 +3,8 @@ title: 'Configurar pago con Zoop'
 id: 5bRYiUjX1sewZuON8HA6Ld
 status: PUBLISHED
 createdAt: 2023-02-13T18:17:14.240Z
-updatedAt: 2023-02-13T18:57:07.275Z
-publishedAt: 2023-02-13T18:57:07.275Z
+updatedAt: 2024-01-23T21:58:29.652Z
+publishedAt: 2024-01-23T21:58:29.652Z
 firstPublishedAt: 2023-02-13T18:50:09.746Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,24 @@ legacySlug: configurar-pago-con-zoop
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX es posible la integración con el proveedor de pagos Zoop. Con este conector, tu tienda puede realizar ventas a través de tarjetas de crédito y  boletos bancarios.
+En VTEX es posible la integración con el proveedor de pagos Zoop. Con este proveedor, tu tienda puede realizar ventas a través de tarjetas de crédito y  boletos bancarios.
 
-Para configurar la afiliación Zoop, siga los pasos a continuación:
+Para configurar Zoop, siga los pasos a continuación:
 
-1. Acceda al __Admin__ VTEX.
-2. Haga clic en __Pagos__.
-3. Después, haga clic en __Configuración__.
-4. En la pestana __Afiliaciones de Gateway__, haga clic en el botón `+`.
-5. Haga clic en el conector __Zoop__.
-6. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Zoop.
-7. En __Captura automática de pago__, seleccione una de las opciones disponibles:
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Zoop__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__ y __Application Token__ con los datos proporcionados por Zoop.
+5. En __Captura automática de pago__, seleccione una de las opciones disponibles:
 
     - __Utiliza El Comportamiento Recomendado Por El Procesador De Pagos__: la captura de pagos no ocurre automáticamente. En esta opción, el proveedor de pago indica si el pago ha sido autorizado y puede determinar o recomendar un número de días para la captura a partir de la autorización del pago.
     - __Inmediatamente: Captura Automática Al Autorizar El Pago__: la captura se realiza automáticamente inmediatamente después de que se autoriza el pago, incluso si la transacción requiere un análisis antifraude.
     - __Inmediatamente: Captura Automática Al Pasar El Análisis De Riesgo De Fraude__: la captura se realiza automáticamente inmediatamente después de la autorización del pago y el análisis antifraude. Si desea utilizar esta opción y no hay que realizar un análisis antifraude, el sistema seguirá el mismo flujo que la opción __Inmediatamente: Captura Automática Al Autorizar El Pagamento__.
     - __Desactivado: No Capturado Automáticamente__: la captura se produce sólo cuando se factura el pedido. Si desea utilizar esta opción, es importante prestar atención al momento de la facturación, ya que si el pedido se factura por un período mayor al acordado con el proveedor para capturar el pago, la transacción puede cancelarse.
 
-<ui>  8. En <b>¿Activar split y enviar receptores?</b>, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.</ui>
+<ui>  6. En <b>¿Activar split y enviar receptores?</b>, seleccione si los pagos divididos estarán disponibles para el marketplace y sellers.</ui>
 
-<ui>  9. Haga clic en <b>Guardar.</b></ui>
+<ui>  7. Haga clic en <b>Guardar.</b></ui>
 
 Para configurar las condiciones de pago, acceda a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago#).
 
diff --git a/docs/tutorials/es/setting-up-paypal-plus.md b/docs/tutorials/es/setting-up-paypal-plus.md
index ba23de7fc..5182c5f9c 100644
--- a/docs/tutorials/es/setting-up-paypal-plus.md
+++ b/docs/tutorials/es/setting-up-paypal-plus.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar PayPal Plus (PayPal Transparente)'
 id: 2akxq3I92k8A4kymIYOiWy
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-20T20:15:36.950Z
-updatedAt: 2023-03-29T01:12:02.453Z
-publishedAt: 2023-03-29T01:12:02.453Z
+updatedAt: 2024-03-18T20:30:56.156Z
+publishedAt: 
 firstPublishedAt: 2018-02-20T22:56:13.192Z
 contentType: tutorial
 productTeam: Financial
@@ -15,38 +15,44 @@ legacySlug: configurar-paypal-plus-paypal-transparente
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En el gateway de VTEX, usted puede configurar el subadquirente PayPal Plus, el checkout transparente de PayPal. En esta modalidad, basta con que el cliente introduzca la información de __tarjeta de crédito__ y finalice la compra normalmente. El pago se realiza directamente en su sitio, sin redirigir a sus clientes.
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
+En el gateway de VTEX, usted puede configurar el subadquirente PayPal Plus, el checkout transparente de PayPal. En esta modalidad, basta con que el cliente introduzca la información de tarjeta de crédito y finalice la compra normalmente. El pago se realiza directamente en su sitio, sin redirigir a sus clientes.
 
 Para realizar la configuración, siga los pasos abajo:
 
-## Configurar la afiliación de gateway PayPal Plus
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PayPalPlus__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Si desea modificar el nombre de identificación que se mostrará para el proveedor iugu en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+5. En __Control de pago__, seleccione si desea activar PayPal Plus en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+6. Rellena los siguientes campos según los datos proporcionados por PayPal:
+    - Em __ID do cliente__ insira o _clientId_.
+    - Em __Secret__ insira o _secret_.
+    - Em __Nombre do usuario__ insira o _userName_.
+    - Em __Contraseña__ insira o _password_.
+    - Em __Firma__ insira o _signature_.
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __PayPalPlus__.
+<blockquote><ui>  7. En <b>Guardar tarjetas</b>, seleccione <b>Sí</b> para que el cliente pueda seleccionar la opción de guardar la tarjeta al finalizar la compra. Si no desea habilitar esta opción, seleccione <b>No</b>.</ui>
 
-Rellene los campos de registro con los datos proporcionados por PayPal, como abajo.
-- El *clientId* debe insertarse en el campo __ID de cliente__.
-- El *secret* debe insertarse en el campo __Secret__.
-- El *userName* debe insertarse en el campo __Nombre de usuario__.
-- La *password* debe insertarse en el campo __Contraseña__.
-- La *signature* debe insertarse en el campo __Firma__.
+<blockquote><ui>  8. En <b>Moneda</b>, elija la moneda de la transacción.</ui>
 
-Después, siga estos pasos:
-1. En el campo __Recordar tarjetas__, seleccione __Sí__ para que el cliente pueda elegir la opción de guardar la tarjeta en el momento del checkout. Si no desea habilitar esta opción, seleccione __No__.
-2. En __Moneda__, elija la moneda de la transacción.
-3. En __Lugar de la transacción__, seleccione la ubicación de la transacción.
-4. Haga clic en __Guardar__.
+<blockquote><ui>  9. En <b>Lugar de la transacción</b>, seleccione el país de la transacción.</ui>
 
-## Configurar la condición de pago PayPal Plus
+<blockquote><ui>  10. En <b>Activar API de riesgo (STC)</b>, seleccione la opción según su configuración de PayPal.</ui>
 
-1. Dentro de los __Ajustes__ del módulo Pagos, haga clic en la pestaña __Planes de pago__.
-2. Haga clic en el botón __+__.
-3. Haga clic en el medio de pago __PayPalPlus__.
-4. Haga clic en el botón __Status__ para activar esta condición de pago.
-5. Si lo desea, marque la casilla __Usando Antifraude__ para activar el antifraude básico.
-6. Como el pago con PayPal Plus es un pago con tarjeta de crédito, usted puede elegir [configurar la condición de pago en efectivo o parcelado](/es/tutorial/condiciones-de-pago).
-7. Si lo desea, también puede configurar [condiciones especiales de pago](/es/tutorial/condiciones-especiales).
-8. Después de realizar la configuración, haga clic en __Guardar__.
+<blockquote><ui>  11. Haga clic en <b>Guardar</b>.</ui>
+
+## Configurar la condición de pago PayPal Plus
 
-Listo! Ahora aparecerá en el checkout la opción de pago por __tarjeta de crédito__ utilizando [PayPal como subadquirente](/es/tutorial/que-es-un-subadquirente).
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __PayPalPlus__.
+4. Complete el campo __Nombre de la condición__ con un nombre de su elección para identificación.
+5. Active la condición en el campo __Status__.
+6. Seleccione si desea utilizar un sistema antifraude seleccionando la opción __Utilizar antifraude__.
+7. Indique si los pagos con tarjeta de crédito deben realizarse [al contado o en cuotas (con y sin intereses)](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455).
+8. Si lo deseas, también puedes configurar [condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
+9. Haga clic en `Guardar`.
+
+Después de seguir los pasos indicados, PayPal Plus puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-payu-gateway.md b/docs/tutorials/es/setting-up-payu-gateway.md
index 3aa89ee2c..79ee1f48c 100644
--- a/docs/tutorials/es/setting-up-payu-gateway.md
+++ b/docs/tutorials/es/setting-up-payu-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway PayU'
 id: 36zWOAFHmwIAoWIEU2Y08q
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-27T15:25:04.654Z
-updatedAt: 2023-03-21T20:17:16.717Z
-publishedAt: 2023-03-21T20:17:16.717Z
+updatedAt: 2024-03-18T20:27:28.378Z
+publishedAt: 
 firstPublishedAt: 2018-03-27T22:13:40.899Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-payu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 PayU es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que ofrece una serie de soluciones para facilitar (y dejar más seguras) las transacciones realizadas en su tienda. Con certificación [PCI](/es/faq/que-es-el-pci-ssc), esta solución es exclusiva para Argentina, Brasil, Chile, Colombia, México, Panamá y Perú.
 
 Para configurar el PayU, siga los pasos abajo:
 
-## Configurar la afiliación de gateway PayU
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __PayU__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PayU__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro con los datos proporcionados por PayU (campos _API Login_, _API Key_, _Account Id_ y _Merchant Id_).
 5. En el campo __Forma de Autorización__, elija el modo en que desea autorizar las transacciones.
 6. En __Moneda__, seleccione la moneda que se utilizará en las transacciones.
diff --git a/docs/tutorials/es/setting-up-payzen-gateway.md b/docs/tutorials/es/setting-up-payzen-gateway.md
index c7d0c1a54..9d3b917d4 100644
--- a/docs/tutorials/es/setting-up-payzen-gateway.md
+++ b/docs/tutorials/es/setting-up-payzen-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar el gateway PayZen'
 id: 3v3n5eQvxem8MQOCkugk24
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-13T19:39:04.093Z
-updatedAt: 2023-03-29T00:56:10.654Z
-publishedAt: 2023-03-29T00:56:10.654Z
+updatedAt: 2024-03-18T19:50:54.475Z
+publishedAt: 
 firstPublishedAt: 2018-03-13T22:27:11.198Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-el-gateway-payzen
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 En VTEX, usted puede configurar el [gateway PayZen](/es/tutorial/que-es-un-gateway-de-pagos) en su tienda. De fácil integración, sigue los estándares de seguridad definidos por [Pagos](/es/faq/que-es-el-pci-ssc).
 
 Para configurar PayZen, siga los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md b/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md
index 06dae3ddd..acf33ae30 100644
--- a/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md
+++ b/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md
@@ -21,21 +21,21 @@ Para acceder a esta, siga los pasos a continuación:
 
 1. En la barra superior del Admin, en la esquina derecha, haga clic en el botón con la inicial de su nombre.
 2. Haga clic en la opción __Ajustes de usuario__.  
-![Opção Configurações de usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/78a9966c5f845964155876b5eaaad046/Op____o_Configura____es_de_usu__rio_User_Management_ES.png)
+![Opção Configurações de usuário User Management ES](//images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/78a9966c5f845964155876b5eaaad046/Op____o_Configura____es_de_usu__rio_User_Management_ES.png)
 
 Hay dos opciones en el menú:
 
 - En __Personal__, usted puede ver su nombre, su email y su número de teléfono registrado en el Admin.  
-![Configuração Pessoal User Management ES](https://images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/f4de16a2eac3bcd839457bb27b3a6600/Configura____o_Pessoal_User_Management_ES.png)
+![Configuração Pessoal User Management ES](//images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/f4de16a2eac3bcd839457bb27b3a6600/Configura____o_Pessoal_User_Management_ES.png)
 
 - Al hacer clic en __Nombre__, tendrá la opción de editar su nombre y apellido.  
-![Configuração Nome User Management ES](https://images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/497b4fda29df1738e4e82443746cff93/Configura____o_Nome_User_Management_ES.png)
+![Configuração Nome User Management ES](//images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/497b4fda29df1738e4e82443746cff93/Configura____o_Nome_User_Management_ES.png)
 
 - Al hacer clic en __Número de celular__, tendrá la opción de editar su número de celular con el código del país.  
-![Configuração Celular User Management ES](https://images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/216dedc0b6cd726ffcc0842662d24cab/Configura____o_Celular_User_Management_ES.png)
+![Configuração Celular User Management ES](//images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/216dedc0b6cd726ffcc0842662d24cab/Configura____o_Celular_User_Management_ES.png)
 
 - En __Autenticación__, usted encuentra las opciones de cambio de contraseña, gestión de la verificación en 2 pasos (2FA) para su inicio de sesión en el Admin VTEX y gestión de sesiones. A continuación, vea cuáles son esas opciones.  
-![Configuração Autenticação User Management ES](https://images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/3612591bcfcf2283125311c8defad942/Configura____o_Autentica____o_User_Management_ES.png)
+![Configuração Autenticação User Management ES](//images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/3612591bcfcf2283125311c8defad942/Configura____o_Autentica____o_User_Management_ES.png)
 
 ## Verificación en 2 pasos
 
@@ -53,5 +53,5 @@ Aquí, usted debe configurar la aplicación que proporcionará la clave de auten
 
 Vea en detalle cómo configurar la aplicación en el artículo [Habilitar inicio de sesión por autenticación de 2 factores](https://help.vtex.com/es/tutorial/habilitar-login-por-autenticacao-de-2-fatores).
 
-![Configuração Verificação em 2 passos User Management ES](https://images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2977fce5188bebcc443d4bed4b58afb3/Configura____o_Verifica____o_em_2_passos_User_Management_ES.png)
+![Configuração Verificação em 2 passos User Management ES](//images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2977fce5188bebcc443d4bed4b58afb3/Configura____o_Verifica____o_em_2_passos_User_Management_ES.png)
 
diff --git a/docs/tutorials/es/setting-up-place2pay-gateway.md b/docs/tutorials/es/setting-up-place2pay-gateway.md
index c8d06fe65..64bcbfb61 100644
--- a/docs/tutorials/es/setting-up-place2pay-gateway.md
+++ b/docs/tutorials/es/setting-up-place2pay-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Place2Pay'
 id: 2NmmnLpUPY0A8aMi0oyiQq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-07T21:45:23.671Z
-updatedAt: 2023-03-29T01:09:24.503Z
-publishedAt: 2023-03-29T01:09:24.503Z
+updatedAt: 2024-03-18T19:53:38.738Z
+publishedAt: 
 firstPublishedAt: 2018-03-07T22:13:43.326Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-gateway-place2pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Place2Pay es la versión con redirect del gateway PlaceToPay, que ofrece soluciones para grandes y pequeñas tiendas.
 
 Para configurar Place2Pay, siga los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-price-tables-for-specific-users.md b/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
index dd2316c21..e0be9d526 100644
--- a/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
@@ -92,7 +92,7 @@ Cuando un usuario de su tienda no ha iniciado sesión, los precios que se le mue
 Si el usuario ha iniciado sesión, verá los precios correspondientes a la tabla de precios a la que está asociado su e-mail.
 
 Por ejemplo, estos dos clientes están vinculados a tablas de precios diferentes:
-![Clients](https://images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
+![Clients](//images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
 
 Cuando el cliente Daniel, que está vinculado a la tabla Silver, inicie sesión en la tienda, verá los precios establecidos en dicha tabla. La mochila del ejemplo anterior aparecerá a USD 50.
 En cambio, el cliente Breno, que está vinculado a la tabla Gold, verá los precios definidos en esta otra tabla. Para él, la mochila costará USD 60,50.
diff --git a/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md b/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md
index f06db4fa8..73bb70ee4 100644
--- a/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md
+++ b/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar adquirente Rede con ERedeRest'
 id: 5TD6Ap9kiIUSiAMUsgYmcY
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-12T15:47:44.783Z
-updatedAt: 2023-03-29T01:11:21.243Z
-publishedAt: 2023-03-29T01:11:21.243Z
+updatedAt: 2024-03-18T18:22:35.227Z
+publishedAt: 
 firstPublishedAt: 2018-04-13T15:41:42.879Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-adquirente-rede-con-erederest
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 En VTEX, usted puede hacer la integración con el [adquirente](/es/tutorial/que-es-un-adquirente) Rede usando el conector ERedeREST. Este conector trae una serie de mejoras, entre ellas el soporte a medios de pago con pre-autorización (__Visa__, __Mastercard__, __American Express__, __Diners__, __Hipercard__, __JCB__ y __Credz__).
 
 <div class="alert alert-warning">
diff --git a/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md b/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md
index 49967383d..924cc9d84 100644
--- a/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md
+++ b/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar Seller White Label como punto de recogida (Pickup Point)'
 id: 6fSUE2O0taaoKieAaiuc4e
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-09-04T14:22:05.290Z
-updatedAt: 2023-03-29T18:58:34.411Z
-publishedAt: 2023-03-29T18:58:34.411Z
+updatedAt: 2023-07-26T21:33:59.946Z
+publishedAt: 
 firstPublishedAt: 2018-09-05T20:38:04.270Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -28,6 +28,7 @@ Las configuraciones se deben realizar en la cuenta del seller White Label. Los 
 </div>
 
 ## Configuración inicial
+
 Para configurar Seller White Label como punto de recogida, es necesario crear en el Admin VTEX:
 
 - [Pickup point](https://help.vtex.com/es/tutorial/creating-pickup-points--2R5ClQiwe4KoSQgsuiOw4E): con la dirección del seller white label.    
@@ -47,6 +48,10 @@ Para saber en detalle cómo llenar los campos de la plantilla, ingrese a nuestro
 
 Si la configuración del punto de recogida se ha efectuado correctamente en la Cuenta Franquicia, los SKUs con __stock disponible y precio__ podrán venderse en la Cuenta Principal, donde la Cuenta Franquicia actuará como un __Seller White Label__ y la Cuenta Principal funcionará como un __Marketplace__.
 
+<div class="alert alert-warning">
+Asegúrese de que el seller white label esté activo. Acceda a el Admin VTEX, en <b>Marketplace > Sellers > Gestión de sellers</b>, y en la línea del seller y la columna <i>Status</i>, haga clic en <code>Activo</code>.
+</div>
+
 ### Seller White Label/Cuenta Franquicia
 
 Para validar si el seller white label está realizando la entrega de un SKU a través del punto de recogida registrado, usted debe hacer un `POST` en la ruta de fulfillment: 
diff --git a/docs/tutorials/es/setting-up-shipment.md b/docs/tutorials/es/setting-up-shipment.md
index 9b43e4118..db168a712 100644
--- a/docs/tutorials/es/setting-up-shipment.md
+++ b/docs/tutorials/es/setting-up-shipment.md
@@ -27,7 +27,7 @@ La primera caja con tiempo total de __2 días__ esperará el item representado p
 
 El período considera T = 0 como la fecha del pedido.
 
-![Configuração em estoque e entrega ES](https://images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/79aa792b4179662cb5e55a00b1523851/Configura____o_em_estoque_e_entrega_ES.png)
+![Configuração em estoque e entrega ES](//images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/79aa792b4179662cb5e55a00b1523851/Configura____o_em_estoque_e_entrega_ES.png)
 
 ## Cómo configurar el envío en grupo
 
diff --git a/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md b/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md
index 162a5a9fb..39db9f330 100644
--- a/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md
+++ b/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Sitef con pre-auth'
 id: 2ZH4DLmZpKw022aSGcGYag
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-05T21:07:59.629Z
-updatedAt: 2023-03-29T01:21:24.445Z
-publishedAt: 2023-03-29T01:21:24.445Z
+updatedAt: 2024-03-18T20:04:33.165Z
+publishedAt: 
 firstPublishedAt: 2018-03-06T14:09:56.654Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-gateway-sitef-con-pre-auth
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Para permitir que las compras realizadas con tarjeta de crédito tengan el valor reservado, usted puede configurar el gateway __Sitef con pre-auth__ (pre-autorización) en su tienda.
 
 Para ello, basta con seguir los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-sitef-gateway.md b/docs/tutorials/es/setting-up-sitef-gateway.md
index 1ae08d634..8a712057a 100644
--- a/docs/tutorials/es/setting-up-sitef-gateway.md
+++ b/docs/tutorials/es/setting-up-sitef-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Sitef'
 id: 1y3gqmbb6wgwscW8yeccAc
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-05T17:07:51.846Z
-updatedAt: 2023-03-29T01:01:36.029Z
-publishedAt: 2023-03-29T01:01:36.029Z
+updatedAt: 2024-03-18T20:02:31.580Z
+publishedAt: 
 firstPublishedAt: 2018-03-05T17:35:10.870Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,17 @@ legacySlug: configurar-gateway-sitef
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX, usted puede configurar el gateway __Sitef__. Si desea recibir pagos por Sitef, siga los pasos abajo:
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
 
-## Configurar la afiliación de gateway Sitef
+En VTEX, usted puede configurar el gateway Sitef. Para configurarlo, siga los pasos a continuación:
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Sitef__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Sitef__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. En el campo __ID de la tienda__ , rellene con los datos de su MerchantId en Sitef.
 5. En __Clave de acceso__ , rellene con el MerchantKey proporcionado por Sitef.
 6. En el campo __Captura de seguridad anticipada__ , seleccione en cuánto tiempo debe realizarse la captura del valor después de la aprobación de la transacción.
-7. Haga clic en __Guardar__.
+7. Haga clic en `Guardar`.
 
 ## Configurar la condición de pago
 
diff --git a/docs/tutorials/es/setting-up-sms-password-recovery.md b/docs/tutorials/es/setting-up-sms-password-recovery.md
index 7f56a9094..81415f034 100644
--- a/docs/tutorials/es/setting-up-sms-password-recovery.md
+++ b/docs/tutorials/es/setting-up-sms-password-recovery.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar recuperación de contraseña por SMS'
 id: 4MBZmPN2GSBNFooa9la555
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-03-07T21:02:11.023Z
-updatedAt: 2020-09-17T21:00:30.654Z
-publishedAt: 2020-09-17T21:00:30.654Z
+updatedAt: 2024-05-22T13:29:09.953Z
+publishedAt: 
 firstPublishedAt: 2019-03-07T21:04:24.196Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,13 +26,13 @@ Dicho esto, eche un vistazo al paso a paso de cómo configurar esta modalidad:
 1. Acceda a la __Central de Mensajes__.
 2. Haga clic en __Templates__.
 
-  ![5NrtBpFRTxInFl4aY2FrVz-es](https://images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/afff0b3f7b7b84e4379f55bd2cc05d7e/5NrtBpFRTxInFl4aY2FrVz-es.png)
+  ![5NrtBpFRTxInFl4aY2FrVz-es](//images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/afff0b3f7b7b84e4379f55bd2cc05d7e/5NrtBpFRTxInFl4aY2FrVz-es.png)
 
 3. Haga clic en el template __Password Recovery__.
 4. Haga clic en la pestaña __SMS__;
 5. Seleccione la opción __"Activar envío de SMS?"__.
 
-  ![password-recovery-sms-tab-es](https://images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/3d53d4e4586a14e5e7b34b5f9c8df84b/password-recovery-sms-tab-es.gif)
+  ![password-recovery-sms-tab-es](//images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/3d53d4e4586a14e5e7b34b5f9c8df84b/password-recovery-sms-tab-es.gif)
 
   *En el momento en que el usuario hace clic en "Activar envío de SMS", la plataforma muestra las demás configuraciones de envío.*
 
@@ -40,7 +40,7 @@ Dicho esto, eche un vistazo al paso a paso de cómo configurar esta modalidad:
 7. Rellene el campo __Destination__ con la variable `{{_accountInfo.Telephone}}`.
 8. Rellene el campo __Message Text__ con el contenido del mensaje. Las informaciones `Nombre: {{nombre}}`, `Login: {{login}}` y `Contraseña: {{contraseña}}` son esenciales.
 
-  ![password-recovery-sms-fields-es](https://images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/46e9fa31dd9a4be8bdd3840ddd51eb92/password-recovery-sms-fields-es.png)
+  ![password-recovery-sms-fields-es](//images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/46e9fa31dd9a4be8bdd3840ddd51eb92/password-recovery-sms-fields-es.png)
 
 9. Revise el contenido del SMS en __Preview__.
 10. Haga clic en __Guardar__.
diff --git a/docs/tutorials/es/setting-up-sub-acquirer-stelo.md b/docs/tutorials/es/setting-up-sub-acquirer-stelo.md
index 542eadace..56ee8cc38 100644
--- a/docs/tutorials/es/setting-up-sub-acquirer-stelo.md
+++ b/docs/tutorials/es/setting-up-sub-acquirer-stelo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar subadquirente Stelo'
 id: 3gHWiaK9wQg08wOsoysciQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T17:43:45.957Z
-updatedAt: 2023-03-29T01:10:18.026Z
-publishedAt: 2023-03-29T01:10:18.026Z
+updatedAt: 2024-03-18T20:16:43.458Z
+publishedAt: 
 firstPublishedAt: 2018-03-02T20:17:14.474Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-subadquirente-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 Stelo es un [subadquirente](/es/tutorial/que-es-un-subadquirente) que facilita la integración de medios de pago a su tienda.
 
 Para configurarlo, siga estos pasos:
diff --git a/docs/tutorials/es/setting-up-the-critical-stock-alert.md b/docs/tutorials/es/setting-up-the-critical-stock-alert.md
index e70a737e7..718cf7bef 100644
--- a/docs/tutorials/es/setting-up-the-critical-stock-alert.md
+++ b/docs/tutorials/es/setting-up-the-critical-stock-alert.md
@@ -23,7 +23,7 @@ La alerta de inventario crítico es una funcionalidad de logística que tiene el
 2. En **Configuración**, rellena lo campo de **Alerta de inventario crítico**.  
 3. Haga clic en **Salvar**.
 
-![alerta-estoque-critico es](https://images.ctfassets.net/alneenqid6w5/3sIAJKB8AogSyQeEqYokCe/f696e3e2cc5ab214eeda18b7ce5f7098/alerta-estoque-critico_es.png)
+![alerta-estoque-critico es](//images.ctfassets.net/alneenqid6w5/3sIAJKB8AogSyQeEqYokCe/f696e3e2cc5ab214eeda18b7ce5f7098/alerta-estoque-critico_es.png)
 
 Como usted puede ver por la imagen, ella puede ser marcada con flecha por cantidad de ítems o por porcentual.
 
diff --git a/docs/tutorials/es/setting-up-the-notes-payable-conector.md b/docs/tutorials/es/setting-up-the-notes-payable-conector.md
new file mode 100644
index 000000000..79c045d69
--- /dev/null
+++ b/docs/tutorials/es/setting-up-the-notes-payable-conector.md
@@ -0,0 +1,31 @@
+---
+title: 'Configurar el conector Pagarés'
+id: 7Gy0SJRVS0Qi2CuWMAqQc0
+status: CHANGED
+createdAt: 2018-06-22T15:15:02.946Z
+updatedAt: 2024-01-19T19:28:16.938Z
+publishedAt: 2023-10-18T17:29:11.714Z
+firstPublishedAt: 2018-06-22T19:10:55.195Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: configurar-conector-pagares
+locale: es
+legacySlug: configurar-conector-pagares
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+El conector __Pagarés__, como su propio nombre sugiere, permite que su tienda pase a aceptar pagarés como método de pago.
+
+Para configurarlo, siga los pasos a continuación:
+
+## Configurar la afiliación de gateway
+1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Afiliaciones de Gateway__, haga clic en el botón `+`.
+3. Haga clic en el conector __Pagarés__.
+4. En el campo __Validez del pagaré en días, máx (180)__, defina cuántos días su cliente tendrá que pagar el pagaré antes de que deje de ser válido.
+5. En __Autorizar automáticamente__, informe si desea aprobar el pago de inmediato. Sólo recomendamos la elección de esta opción para los casos en que el pago se realiza en la entrega o en la retirada del pedido en la tienda. Al elegir _Yes_, el pedido pasa automáticamente al status _Preparando Entrega_, sin pasar por ninguna verificación de pago.
+6. Haga clic en `Guardar`.
+
+## Configurar la condición de pago
+Después de seguir los pasos indicados arriba, el conector Pagarés estará configurado en su tienda. Por lo tanto, cuando se registre un Pagaré (en la pestaña __Pagos personalizados__ de la página de __Configuración__ de Pagos), estará disponible en el campo __Procesar con la afiliación__. Para saber cómo registrar pagos personalizados, acceda a [Configurar pago personalizado](https://help.vtex.com/es/tutorial/como-configurar-pagamento-personalizado).
diff --git a/docs/tutorials/es/setting-up-the-notify-me-option.md b/docs/tutorials/es/setting-up-the-notify-me-option.md
index 45ba498de..c08d945e8 100644
--- a/docs/tutorials/es/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/es/setting-up-the-notify-me-option.md
@@ -23,7 +23,7 @@ Cuando no hay [stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inven
 
 A continuación, puedes ver un ejemplo de cómo se visualiza la opción **Avísame** en una tienda. Para recibir una notificación cuando el ítem esté disponible para la venta, el cliente debe ingresar su nombre e email en los campos resaltados y luego hacer clic en el botón `Enviar`.
 
-![aviseme-es](https://images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/a00bc93c8475050d5861859016a8915c/Group_2__2_.png)
+![aviseme-es](//images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/a00bc93c8475050d5861859016a8915c/Group_2__2_.png)
 
 En cuanto el ítem ingrese de nuevo al stock de la tienda, el sistema envía automáticamente un email al cliente informándo le que el producto ya está disponible para la compra. 
 
diff --git a/docs/tutorials/es/setting-up-the-paymee-gateway.md b/docs/tutorials/es/setting-up-the-paymee-gateway.md
index 14e6422e2..5941d6893 100644
--- a/docs/tutorials/es/setting-up-the-paymee-gateway.md
+++ b/docs/tutorials/es/setting-up-the-paymee-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar el gateway PayMee'
 id: 3fsilRdrBS6GOAy622soWy
 status: PUBLISHED
 createdAt: 2018-02-28T21:29:08.666Z
-updatedAt: 2019-12-31T15:20:50.800Z
-publishedAt: 2019-12-31T15:20:50.800Z
+updatedAt: 2024-03-14T17:02:16.884Z
+publishedAt: 2024-03-14T17:02:16.884Z
 firstPublishedAt: 2018-03-01T21:53:29.140Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,19 @@ legacySlug: configurar-el-gateway-paymee
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-En VTEX, usted puede configurar el gateway de pagos PayMee. Con este conector, su tienda puede recibir pagos por transferencia bancaria o dinero.
+En VTEX es posible la integración con el proveedor de pagos PayMee. Con este proveedor, su tienda puede realizar ventas a través PayMee y PIX.
 
-Para realizar la configuración, siga los pasos abajo:
+Para configurar PayMee, siga los pasos a continuación:
 
-## Configurar la afiliación de gateway PayMee
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __PayMee__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta PayMee.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor PayMee en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
 
-1. Acceda al módulo __Pagos__.
-2. Haga clic en __Configuración__.
-3. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-4. Haga clic en el conector __PayMee__.
-5. Rellene los campos de __Application Key__ y __Application Token__ con los datos proporcionados por PayMee.
-6. Haga clic en __Guardar__.
+Para configurar los métodos de pago a procesar por PayMee, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
-## Configurar la condición de pago PayMee
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
-1. Dentro de los __Configuración__ del módulo Pagos, haga clic en la pestaña __Planes de pago__.
-2. Haga clic en el botón __+__.
-3. Haga clic en el medio de pago __PayMee__.
-4. Haga clic en el botón __Status__ para activar esta condición de pago.
-5. Si lo desea, marque la casilla __Usar Antifraude__ para activar el antifraude básico.
-6. Haga clic en __Guardar__.
-
-Listo. Ahora aparecerá en el checkout la opción de pago a través del __PayMee__.
+Después de seguir los pasos indicados, PayMee puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-the-price-range-filter.md b/docs/tutorials/es/setting-up-the-price-range-filter.md
index 55e22c170..24750617d 100644
--- a/docs/tutorials/es/setting-up-the-price-range-filter.md
+++ b/docs/tutorials/es/setting-up-the-price-range-filter.md
@@ -20,7 +20,7 @@ Importantísimas para navegación y búsqueda de los productos deseados en la ti
 
 El registro es sencillo y se pueden determinar diferentes rangos de precios para categorías, conforme a la imagen abajo:
 
-![faixa-de-preço es](https://images.ctfassets.net/alneenqid6w5/2j45MP5kMsA02YeMgMCy2y/9fa923fbae98e90882fabff0e2f7cf17/faixa-de-pre__o_es.png)
+![faixa-de-preço es](//images.ctfassets.net/alneenqid6w5/2j45MP5kMsA02YeMgMCy2y/9fa923fbae98e90882fabff0e2f7cf17/faixa-de-pre__o_es.png)
 
 Dentro de Fajas de Precio, haga clic en “Nuevo rango de precio” y rellene los campos:
 
diff --git a/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
index e02454f26..d008c6d60 100644
--- a/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
@@ -25,23 +25,23 @@ Para facilitar, toda la configuración que se muestra en este artículo se puede
 
 Para la configuración manual o la edición de una meta existente, el primer paso es acceder a Analytics y hacer clic en el botón __Administrador__ en la esquina inferior izquierda. A continuación, vaya a la opción __Metas__, de la columna "Vista".
 
-![image](https://images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
 
 En la pantalla de administración de metas, opte por crear una nueva o editar una ya existente.
 
 __En el paso 1__ usted puede seguir con una meta de tipo personalizado:
 
-![image](https://images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
 
 __En el paso 2__ usted puede definir el nombre que prefiera para su meta y un código de posición (de uso interno de Google Analytics). En el tipo, vamos a usar "Destino":
 
-![image](https://images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
 
 __En el paso 3__ tenemos las configuraciones más sensibles. En él configuramos la página que determina la conclusión de la meta y el camino que los clientes van a recorrer para alcanzarla.
 
 En el campo "Destino" seleccione la opción de expresión regular e introduzca la dirección URL de la página de pedido completa: `^/checkout/orderPlaced`
 
-![image](https://images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
 
 Luego configure la ruta que el cliente va a recorrer hasta que finalice un pedido. En este caso, tenemos en cuenta que el proceso de compra se inicia en la pantalla del producto; entonces mi embudo servirá para medir la cantidad de clientes que accede a esa pantalla, cuántos pedidos se han finalizado y en qué paso los clientes están desistiendo de la compra.
 
@@ -54,7 +54,7 @@ Aún en el paso 3, active la opción __Embudo__ con los siguientes pasos:
  - __Envío__ = `^/checkout/(\?.*)?#/shipping$`
  - __Pago__ =  `^/checkout/(\?.*)?#/payment$`
 
-![image](https://images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
 
 Una forma de comprobar si la meta está configurada correctamente es usar el enlace "Compruebe esta meta". Google va a generar una simulación de la conversión de la meta en los últimos 7 días.
 
diff --git a/docs/tutorials/es/setting-up-the-tnspay-gateway.md b/docs/tutorials/es/setting-up-the-tnspay-gateway.md
index 49092e09d..873bf5f76 100644
--- a/docs/tutorials/es/setting-up-the-tnspay-gateway.md
+++ b/docs/tutorials/es/setting-up-the-tnspay-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar el gateway TNSPay'
 id: 6jIUr6Va00QyEuMEGAmQA6
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T12:43:42.795Z
-updatedAt: 2023-03-29T01:14:08.864Z
-publishedAt: 2023-03-29T01:14:08.864Z
+updatedAt: 2024-03-18T20:23:20.750Z
+publishedAt: 
 firstPublishedAt: 2018-03-02T15:56:49.389Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-el-gateway-tnspay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 TNSPay es un [gateway de pago](/es/tutorial/que-es-un-gateway-de-pagos) con certificación PCI que proporciona una serie de features de seguridad para facilitar el procesamiento de [compras recurrentes](/es/faq/como-funciona-la-compra-recurrente).
 
 Para configurar TNSPay, siga los pasos abajo:
diff --git a/docs/tutorials/es/setting-up-the-voucher-list.md b/docs/tutorials/es/setting-up-the-voucher-list.md
index 5e70cef16..fc9584987 100644
--- a/docs/tutorials/es/setting-up-the-voucher-list.md
+++ b/docs/tutorials/es/setting-up-the-voucher-list.md
@@ -26,13 +26,13 @@ Es necesaria una configuración de SKU con las siguientes características para
 - El SKU debe tener el precio de R$0,01.
 - El SKU debe ser configurado para generar crédito en vale.
 
-![sku-opção-credito-vale es](https://images.ctfassets.net/alneenqid6w5/5jtCFBYaME4muoOKg8eWQE/9f8da92008fd49aa99fc123b8141a0fc/sku-op____o-credito-vale_es.png)
+![sku-opção-credito-vale es](//images.ctfassets.net/alneenqid6w5/5jtCFBYaME4muoOKg8eWQE/9f8da92008fd49aa99fc123b8141a0fc/sku-op____o-credito-vale_es.png)
 
 ## Configuraciones en el Tipos de Lista
 
 La creación de este tipo de lista pide, en las configuraciones, que la entrega se marque como "Valor de los productos comprados será convertido en un vale de compras". Vea la imagen de ejemplo:
 
-![entrega-tipos-lista ew](https://images.ctfassets.net/alneenqid6w5/5vtZiXaAPS0iWow2EgA4OE/6cf83c7a2402bdf95233cfe0729f54e7/entrega-tipos-lista_ew.png)
+![entrega-tipos-lista ew](//images.ctfassets.net/alneenqid6w5/5vtZiXaAPS0iWow2EgA4OE/6cf83c7a2402bdf95233cfe0729f54e7/entrega-tipos-lista_ew.png)
 
 Grabe su lista después de realizar las demás configuraciones deseadas.
 
diff --git a/docs/tutorials/es/setting-up-the-worldpay-acquirer.md b/docs/tutorials/es/setting-up-the-worldpay-acquirer.md
index dd84f6fb1..cc6728cda 100644
--- a/docs/tutorials/es/setting-up-the-worldpay-acquirer.md
+++ b/docs/tutorials/es/setting-up-the-worldpay-acquirer.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar el adquirente Worldpay '
+title: 'Configurar pago con Worldpay-Payments-Via-WPG'
 id: 7GCtigwhNYMi604UM0KeO6
 status: PUBLISHED
 createdAt: 2018-02-28T22:09:45.321Z
-updatedAt: 2023-03-29T00:47:52.166Z
-publishedAt: 2023-03-29T00:47:52.166Z
+updatedAt: 2024-03-18T17:20:43.467Z
+publishedAt: 2024-03-18T17:20:43.467Z
 firstPublishedAt: 2018-02-28T22:38:14.737Z
 contentType: tutorial
 productTeam: Financial
@@ -17,18 +17,31 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Worldpay es un [adquirente](/es/tutorial/que-es-un-adquirente) de actuación global, capaz de procesar pagos en los más diversos tipos de monedas y tarjetas.
 
-Para configurar Worldpay, siga estos pasos:
+Para configurar Worldpay, siga los pasos a continuación:
 
-## Configurar la afiliación de gateway Worldpay
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Worldpay-Payments-Via-WPG__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por su cuenta Worldpay.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor Worldpay en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. En __Control de pago__, seleccione si desea activar el proveedor en un entorno de prueba haciendo clic en __Activar modo de prueba__.
+7. En __Liquidación automática__, seleccione una de las siguientes opciones:
+<br>
+<ul>
+<br>
+    	<li><b>Utiliza comportamiento recomendado por el procesador de pagos</b>: a captura no es automática, sino programada de acuerdo con el plazo especificado por el adquirente que, además de indicar si el pago ha sido autorizado, puede especificar o recomendar un número de días para la captura en el momento de la respuesta a la autorización de pago (este es el comportamiento predeterminado de la plataforma).</li>
+    	<li><b>Liquidación automática inmediatamente después de la autorización del pago</b>: la captura es automática y se produce inmediatamente después de la autorización, incluso si la transacción tiene un análisis antifraude.</li>
+   		<li><b>Liquidación automática inmediatamente después del análisis antifraude</b>: la captura es automática y se realiza inmediatamente después de la autorización y el análisis antifraude (si seleccionas este comportamiento y no tienes análisis antifraude, la captura de pago se realizará de la misma manera que en el comportamiento "Liquidación automática inmediatamente después de la autorización del pago").</li>
+   		<li><b>Desactivado</b>: la captura se realiza solo cuando se factura el pedido. Si se opta por este comportamiento de captura, es importante estar atento al tiempo de facturación, ya que puede exceder el tiempo de captura acordado con el proveedor de pagos y provocar la cancelación de la transacción.</li>
+</ul>
+8. Si desea utilizar [Split de pagos](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx) en su tienda, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
 
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Worldpay__.
-4. Rellene los campos de registro con la información de su cuenta en Worldpay (campos _UserName_, _Password_, _Version_, _MerchantCode_).
-5. En el campo __Currency__, elija la moneda de las transacciones.
-6. En el campo __Captura de segurança antecipada__, escoja en cuánto tiempo desea que la captura se realice después de la aprobación de la transacción y del análisis del antifraude. Usted también puede desactivar esta función.
-7. Haga clic en __Guardar__.
+9. Si aparece un mensaje de alerta que indica la necesidad de instalar la aplicación, haga clic en el botón `Instalar aplicación` y siga las instrucciones de instalación.
 
-## Configurar la condición de pago
+10. Haga clic en `Guardar`.
 
-Después de seguir estos pasos, Worldpay estará configurada en su tienda. Por lo tanto, cuando se registre una condición de pago, ella estará disponible en el campo __Procesar con afiliación__ (siempre que el medio de pago forme parte de la red de adquisición de Worldpay). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+Para configurar los métodos de pago a procesar por WorldPay, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
+
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, WorldPay puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-the-yamisplitmoipv1-gateway.md b/docs/tutorials/es/setting-up-the-yamisplitmoipv1-gateway.md
index 83b0e5863..75dabd5bb 100644
--- a/docs/tutorials/es/setting-up-the-yamisplitmoipv1-gateway.md
+++ b/docs/tutorials/es/setting-up-the-yamisplitmoipv1-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar el gateway YamiSplitMoipV1'
 id: 5qrjr9yukwsk4oaMMAisSK
 status: PUBLISHED
 createdAt: 2018-02-28T16:56:41.540Z
-updatedAt: 2023-03-29T00:48:49.159Z
-publishedAt: 2023-03-29T00:48:49.159Z
+updatedAt: 2024-03-12T21:02:38.695Z
+publishedAt: 2024-03-12T21:02:38.695Z
 firstPublishedAt: 2018-02-28T21:48:56.044Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,19 @@ legacySlug: configurar-el-gateway-yamisplitmoipv1
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-YamiSplitMoipV1 es un gateway dedicado que extiende las features de Moip. Con él, es posible realizar splits de pago en los marketplaces (solución para el usuario hacer un solo pago, incluso comprando productos de sellers diferentes) usando el subadquirente.
+En VTEX es posible la integración con el proveedor de pagos YamiSplitMoipV1. A través de este proveedor, su tienda puede realizar ventas con tarjetas de crédito y comprobantes bancarios.
 
-## Configurar la afiliación de gateway YamiSplitMoipV1
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __YamiSplitMoipV1__.
-4. Rellene los campos _Application Key_ y _Application Token_ con la información de su cuenta __Moip__.
-5. Haga clic en __Gardar__.
+Para configurar YamiSplitMoipV1, siga los pasos a continuación:
 
-## Configurar la condición de pago
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __YamiSplitMoipV1__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. En __Autorización del proveedor__, rellene los campos de registro __Clave de aplicación__ y __Token de aplicación__ con los datos proporcionados por Moip.
+5. Si desea modificar el nombre de identificación que se mostrará para el proveedor YamiSplitMoipV1 en la pantalla VTEX Admin, ingrese la información en el campo __Nombre__ en __Información general__.
+6. Haga clic en `Guardar`.
 
-Después de seguir los pasos indicados, YamiSplitMoipV1 estará configurado en su tienda. Por lo tanto, cuando se registre una condición de pago para uso en un marketplace, estará disponible en el campo __Procesar con afiliación__.
+Para configurar los métodos de pago a procesar por YamiSplitMoipV1, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
-Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
+
+Después de seguir los pasos indicados, YamiSplitMoipV1 puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-vcmais-gateway.md b/docs/tutorials/es/setting-up-vcmais-gateway.md
index 48f100f35..6561acbf5 100644
--- a/docs/tutorials/es/setting-up-vcmais-gateway.md
+++ b/docs/tutorials/es/setting-up-vcmais-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway vcmais'
 id: 28nAmwnfxWSoQEIO8EYYaI
 status: PUBLISHED
 createdAt: 2018-04-17T21:48:38.248Z
-updatedAt: 2023-03-29T00:43:23.712Z
-publishedAt: 2023-03-29T00:43:23.712Z
+updatedAt: 2023-10-18T12:07:58.261Z
+publishedAt: 2023-10-18T12:07:58.261Z
 firstPublishedAt: 2018-04-18T21:26:18.172Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/setting-up-vindi-gateway.md b/docs/tutorials/es/setting-up-vindi-gateway.md
index c670ed201..1af9429a8 100644
--- a/docs/tutorials/es/setting-up-vindi-gateway.md
+++ b/docs/tutorials/es/setting-up-vindi-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar el gateway Vindi'
+title: 'Configurar pago con Vindi'
 id: 61EXzfrBZYIgGU26EGcaMo
-status: DRAFT
+status: PUBLISHED
 createdAt: 2018-03-01T15:25:39.368Z
-updatedAt: 2022-12-23T20:47:23.110Z
-publishedAt: 
+updatedAt: 2024-01-23T21:49:28.618Z
+publishedAt: 2024-01-23T21:49:28.618Z
 firstPublishedAt: 2018-03-01T16:21:19.864Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,18 @@ legacySlug: configurar-el-gateway-vindi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Vindi es un gateway de pagos con certificación PCI, lo que garantiza la seguridad de los datos transaccionados por él. Actualmente, procesa pagos realizados por tarjetas de crédito, boletos bancarios y Paypal.
+En VTEX es posible la integración con el proveedor de pagos Vindi. Con este proveedor, su tienda puede realizar ventas a través de tarjetas de crédito, boletos bancarios y Paypal.
 
-Para configurar Vindi, siga estos pasos:
+Para configurar Vindi, siga los pasos a continuación:
 
-## Configurar la afiliación de gateway Vindi
-1. Acceda al módulo __Pagos__.
-2. Haga clic en __Configuración__.
-3. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-4. Haga clic en el conector __Vindi__.
-5. Rellene los campos de registro con los datos proporcionados por Vindi (campos _Application Key_ y _Application Token_).
-6. Haga clic en __Guardar__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __Vindi__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos de registro __Application Key__ y __Application Token__  con los datos proporcionados por el Vindi.
+5. Haga clic en `Guardar`.
 
-## Configurar la condición de pago
+Para configurar los métodos de pago a procesar por Vindi, acceda al [Configurar Condiciones de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455#).
 
-Después de seguir los pasos indicados arriba, Vindi estará configurada en su tienda. Por lo tanto, cuando se registre una condición de pago, este gateway estará disponible en el campo __Procesar con la afiliación__ (siempre que los medios de pago sean compatibles con Vindi).
+Para establecer condiciones especiales en los métodos de pago, acceda al [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456#).
 
-Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
+Después de seguir los pasos indicados, Vindi puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
diff --git a/docs/tutorials/es/setting-up-webpay2p-gateway.md b/docs/tutorials/es/setting-up-webpay2p-gateway.md
index 8e71dbf01..527acf14a 100644
--- a/docs/tutorials/es/setting-up-webpay2p-gateway.md
+++ b/docs/tutorials/es/setting-up-webpay2p-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway WebPay2P'
 id: 34Bn1nOoVO6iesWAgSEQQA
 status: PUBLISHED
 createdAt: 2018-04-02T19:30:48.720Z
-updatedAt: 2021-07-07T17:45:55.414Z
-publishedAt: 2021-07-07T17:45:55.414Z
+updatedAt: 2024-03-07T13:50:16.754Z
+publishedAt: 2024-03-07T13:50:16.754Z
 firstPublishedAt: 2018-04-02T19:46:03.221Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,16 @@ legacySlug: configurar-gateway-webpay2p
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 [WebPay](https://publico.transbank.cl/productos-y-servicios/soluciones-para-ventas-internet/webpay.cl) es una [afiliación](https://help.vtex.com/es/tutorial/o-que-e-um-gateway-de-pagamentos) exclusiva para los clientes chilenos.  Para configurar la solución y procesar sus pagos con WebPay, realice los siguientes pasos:
 
 Para configurar el WebPay como gateway, siga estos pasos:
 
-1. Acceda al __Admin__ VTEX.
-2. Haga clic en __Pagos > Configuración__.
-3. En la pestaña de __Afiliaciones__, haga clic en el botón __+__.
-4. Haga clic en el conector __WebPay2P__ y rellene los campos solicitados con la siguiente información:
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __WebPay2P__ en la barra de búsqueda y haga clic en el nombre del proveedor.
+4. Rellene los campos solicitados con la siguiente información:
 
     - __Código Comercio T. Crédito__: El código de su tienda para el uso de tarjetas de crédito.
     - __Periodo de Gracia__: Rellene este campo solo si va a ofrecer pagos en efectivo.
diff --git a/docs/tutorials/es/setup-safetypay.md b/docs/tutorials/es/setup-safetypay.md
index 818caed05..fb8e48498 100644
--- a/docs/tutorials/es/setup-safetypay.md
+++ b/docs/tutorials/es/setup-safetypay.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway SafetyPay'
 id: lf89DOdeveuMOI4Q0CwgC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-22T13:57:16.523Z
-updatedAt: 2023-03-29T00:44:35.344Z
-publishedAt: 2023-03-29T00:44:35.344Z
+updatedAt: 2024-03-18T19:57:00.504Z
+publishedAt: 
 firstPublishedAt: 2018-02-22T15:12:57.862Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-safetypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+
 SafetyPay es una solución de pago que conecta directamente el checkout de su tienda al banco de su cliente. En esta solución, su cliente elige SafetyPay como medio de pago y es *redireccionado* para el ambiente seguro de Internet banking elegido. Una vez redireccionado, el cliente puede hacer una transferencia bancaria y realizar el pago del pedido.
 
 Para configurar SafetyPay, siga los pasos abajo:
 
-## Configurar la afiliación de gateway SafetyPay
-
-1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
-2. En la pestaña __Afiliaciones__, haga clic en el botón __+__.
-3. Haga clic en el conector __Safety Pay__.
+1. En el Admin VTEX, accede a __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
+2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
+3. Escriba el nombre __SafetyPay__ en la barra de búsqueda y haga clic en el nombre del proveedor.
 4. Rellene los campos de registro con los datos proporcionados por SafetyPay (Campos *ApiKey, SignatureKey, Custom Merchant Name*).
 5. El campo __Tracking Code__ es opcional. Se puede utilizar para realizar análisis de marketing.
 6. En el campo __Product ID__, rellene con el medio de pago que quiera: __Express__ para transferencia bancaria o __Cash__ para pago en efectivo.
@@ -31,7 +31,7 @@ Para configurar SafetyPay, siga los pasos abajo:
 8. En __Language__, elija el idioma que se utilizará en la interfaz de usuario.
 9. En el campo __Time To Expire (in hours)__, elija el tiempo de vencimiento del pago.
 10. En el campo __Time To Expire for Lottery Payment (in days)__, elija el tiempo de expiración de pagos a ser realizados en loterías (se aplica solamente a Brasil).
-11. Haga clic en __Guardar__.
+11. Haga clic en `Guardar`.
 
 ## Configurar condición de pago SafetyPay
 
diff --git a/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md b/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
index f202d6f21..ca6844ee7 100644
--- a/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
+++ b/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
@@ -3,8 +3,8 @@ title: 'Información compartida entre el marketplace y el seller en VTEX'
 id: 3o7WGiBtfnKKZ3Ddug26k3
 status: PUBLISHED
 createdAt: 2022-04-07T13:32:06.199Z
-updatedAt: 2023-04-17T21:51:10.740Z
-publishedAt: 2023-04-17T21:51:10.740Z
+updatedAt: 2023-10-31T19:54:13.803Z
+publishedAt: 2023-10-31T19:54:13.803Z
 firstPublishedAt: 2022-04-07T14:23:25.578Z
 contentType: tutorial
 productTeam: Channels
@@ -44,7 +44,7 @@ Además, para [agregar al seller](https://help.vtex.com/es/tutorial/configurando
 El _marketplace_ VTEX se puede integrar tanto con un _seller_ VTEX como con un _seller_ externo, ya sea a través del Admin VTEX o de una API. En ambos casos, los datos que compartirán el _marketplace_ y el _seller_ serán los mismos.
 
 <div class = "alert alert-info">
-Para obtener más información sobre cómo conectar un marketplace VTEX con un seller VTEX o con un seller externo a través del Admin VTEX, consulta el artículo <a href="https://help.vtex.com/es/tutorial/configurando-seller">Agregar seller</a>. Para realizar la integración a través de una API, usa la llamada <a href="https://developers.vtex.com/vtex-rest-api/reference/upsertsellerrequest">Configure Seller Account</a>. Si se trata de un seller externo, consulta la <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">guía de integración con un <i>seller</i> externo</a>.
+Para obtener más información sobre cómo conectar un marketplace VTEX con un seller VTEX o con un seller externo a través del Admin VTEX, consulta el artículo <a href="https://help.vtex.com/es/tutorial/configurando-seller">Agregar seller</a>. Para realizar la integración a través de una API, usa la llamada <a href="https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers">Configure Seller Account</a>. Si se trata de un seller externo, consulta la <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">guía de integración con un <i>seller</i> externo</a>.
 </div>
 
 ### Conectar un marketplace VTEX con un seller VTEX
@@ -75,14 +75,14 @@ Si el _seller_ es externo, es decir, no está hospedado en el entorno VTEX, se d
 
 Una vez que el _marketplace_ VTEX y el _seller_ VTEX o el _seller_ externo están conectados,  el _marketplace_ puede acceder a la información guardada sobre el _seller_ a través del Admin VTEX en **MARKETPLACE > Gestión**.
 
-A través de la API, se puede usar la llamada [Get Seller data by ID](https://developers.vtex.com/vtex-rest-api/reference/getretrieveseller) para consultar la información que brinda el _seller_, ya sea que se trate de un _seller_ VTEX o externo.
+A través de la API, se puede usar la llamada [Get Seller data by ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-) para consultar la información que brinda el _seller_, ya sea que se trate de un _seller_ VTEX o externo.
 
 ## Intercambio de emails de clientes
 
 El _marketplace_ puede otorgar al _seller_ un acceso parcial a los emails de su base de clientes para que esos emails se utilicen en las consultas sobre las condiciones comerciales de los ítems y en la creación de pedidos. Esta configuración no está predeterminada y la información se administra mediante API, a través del campo `TrustPolicy`, usando las siguientes llamadas:
 
-- [Configure Seller Account](https://developers.vtex.com/vtex-rest-api/reference/upsertsellerrequest): permite configurar la cuenta del _seller_, ya sea un _seller_ VTEX o externo.
-- [Update Seller by Seller ID](https://developers.vtex.com/vtex-rest-api/reference/updateseller): permite actualizar los datos del _seller_, ya sea un _seller_ VTEX o externo.
+- [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers): permite configurar la cuenta del _seller_, ya sea un _seller_ VTEX o externo.
+- [Update Seller by Seller ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#patch-/seller-register/pvt/sellers/-sellerId-): permite actualizar los datos del _seller_, ya sea un _seller_ VTEX o externo.
 
 <div class = "alert alert-info">
 En los pedidos que se realizan a través del <i>marketplace</i>, el <i>seller</i> no puede ver el email del cliente. El cliente establece una relación con el <i>marketplace</i> y, por lo tanto, se necesitaría su consentimiento para compartir sus datos.
diff --git a/docs/tutorials/es/shipping-options-beta.md b/docs/tutorials/es/shipping-options-beta.md
index b5d97bf6e..27ce05e5a 100644
--- a/docs/tutorials/es/shipping-options-beta.md
+++ b/docs/tutorials/es/shipping-options-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Shipping Options (Beta)'
 id: 7gsdck3519Z3VPqzwFFHJL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-05-27T15:35:44.505Z
-updatedAt: 2023-03-21T17:44:07.634Z
-publishedAt: 2023-03-21T17:44:07.634Z
+updatedAt: 2023-08-14T17:28:57.629Z
+publishedAt: 
 firstPublishedAt: 2022-05-31T18:53:28.695Z
 contentType: tutorial
 productTeam: Others
@@ -93,7 +93,7 @@ Para agregar una opción de envío, sigue los pasos a continuación:
     - **Envío gratis:** libre de costo para el consumidor y no requiere configuración adicional.
 8. Haz clic en el botón `Guardar`.
 
-![opcoes_envio_criacao_es](https://images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/0ef83d6a102d79c74a7d87c42c53c5eb/opcoes_envio_criacao_es.png)
+![opcoes_envio_criacao_es](//images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/0ef83d6a102d79c74a7d87c42c53c5eb/opcoes_envio_criacao_es.png)
 
 ## Editar opción de envío
 
@@ -117,7 +117,7 @@ Además de editar una opción de envío, desde el ícono de menú <i class="fas
 
 Después de configurar las opciones de envío, aparecerán en una lista en **Configuración de la tienda > Envío > Opciones de envío**, según se muestra en la siguiente imagen:
 
-![opcoes_envio_listagem_es](https://images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/eda44ef73871de786a4c6fc8d106923a/opcoes_envio_listagem_es.png)
+![opcoes_envio_listagem_es](//images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/eda44ef73871de786a4c6fc8d106923a/opcoes_envio_listagem_es.png)
 
 La tabla siguiente contiene la descripción de las columnas mostradas:
 
diff --git a/docs/tutorials/es/shipping-policy.md b/docs/tutorials/es/shipping-policy.md
index 4012f5bc6..d1a87ccad 100644
--- a/docs/tutorials/es/shipping-policy.md
+++ b/docs/tutorials/es/shipping-policy.md
@@ -3,8 +3,8 @@ title: 'Política de envío'
 id: tutorials_140
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:12.502Z
-updatedAt: 2023-03-29T18:19:38.883Z
-publishedAt: 2023-03-29T18:19:38.883Z
+updatedAt: 2024-01-31T01:24:50.628Z
+publishedAt: 2024-01-31T01:24:50.628Z
 firstPublishedAt: 2017-04-27T23:00:45.247Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,69 +15,44 @@ legacySlug: registrar-una-transportadora, administrar-operador
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
+La [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) en una tienda VTEX engloba las configuraciones [logísticas](https://help.vtex.com/es/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) esenciales y define la relación entre los siguientes elementos:
 
-Política de envío es un conjunto de reglas que definen las opciones y condiciones de envío que se presentarán al consumidor en el momento de la compra. Las condiciones de envío incluyen la configuración de horario de atención de la transportadora, plazos de entrega, valores adicionales del envío, tipos de productos que pueden entregarse (modalidades) y las ventanas de entrega.
+1. Política de envío
+2. [Almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+3. [Muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
 
-Todos estos ajustes se basan principalmente en el contrato que su tienda tiene con una [transportadora](https://help.vtex.com/es/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE), un prestador de servicios o cualquier otro tipo de contrato de servicio de envío que su tienda ofrece a los consumidores.
+La siguiente imagen muestra cómo se relacionan estos conceptos entre sí:
 
-<div class="alert alert-info">
-Es posible que una misma transportadora sea la base de varias políticas de envío, cada una con sus particularidades. A continuación, se explica cómo crear, editar y eliminar políticas de envío
-</div>
+![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
 
-A través de la plataforma VTEX es posible: 
+La **política de envío** es un conjunto de reglas y ajustes que definen las opciones de envío que se mostrarán a los clientes en el checkout. Al [calcular el tiempo de envío](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) del pedido, la plataforma VTEX toma en consideración los ajustes establecidos en las políticas de envío, entre los que destacan:
 
-*   [Registrar Política de Envío](#registrar-politica-de-envio)
-*   [Editar Política de Envío](#editar-politica-de-envio)
-*   [Excluir Política de Envío](#excluir-politica-de-envio)
+* [Transportadora](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE)
+* [Horario laboral de la transportadora](https://help.vtex.com/es/tutorial/horario-de-funcionamento-das-transportadoras--2oGpbInIgdxSWUi3TZjdCS)
+* [Feriados](https://help.vtex.com/es/tutorial/cadastrar-feriados--2ItOthSEAoyAmcwsuiO6Yk)
+* [Adicionales de envío](https://help.vtex.com/es/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV)
+* [Entrega programada](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)
+* [Puntos de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R)
 
-## Registrar Política de Envío
+Para más información sobre cómo crear una política de envío, consulta [Crear una política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT). Para más información sobre gestión, consulta [Gestionar políticas de envío](https://help.vtex.com/es/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE).
 
-1. En el Admin VTEX, accede a **Envío > Estrategia de Envío > Políticas de Envío**, o escribe *Estrategia de Envío* en la barra de búsqueda en la parte superior de la página.  
-2. Haga clic en el botón `Crear Política de Envío`.
-3. Complete los campos que se muestran y haga clic en `Guardar` al terminar.
-*   **Nombre:** nombre interno de la política de envío.
-*   **ID:** identificador interno y para integradores. Debe rellenarse solo con letras y números. Si no se rellena, se creará un ID automáticamente.
-*   **[Método de envío](https://help.vtex.com/es/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126):** nombre del tipo de entrega. Sirve para separar los diferentes servicios de entrega. Es el nombre que se mostrará al cliente al finalizar la compra. Por ejemplo, expreso vs. regular. 
-*   **Cargar [tarifas de envío](https://help.vtex.com/es/tutorial/como-montar-a-planilha-de-frete--tutorials_127):** tabla con los valores y plazos de envío asumidos por la política de envío.
-*   **[Dimensiones del paquete](https://help.vtex.com/es/tutorial/como-funciona-o-empilhamento--tutorials_124):**
-    *   **Suma de dimensiones:** límites máximos de las aristas del paquete, aceptados. Al llegar a este valor, la entrega se divide en paquetes o no se realiza por esta política de envío. Son datos que se pasan al cerrar el contrato con la política de envío. 
-    *   **Longitud máxima:** máxima medida aceptada. Cuando se alcanza este valor, la entrega se divide en paquetes o no se realiza por esta política de envío. Si un ítem tiene una arista con un tamaño superior a la longitud máxima, nunca se entregará por la política de envío.
-    *   **[Factor de peso volumétrico](https://help.vtex.com/es/tutorial/como-o-peso-cubado-e-calculado--tutorials_128):** factor que se utilizará para calcular el peso volumétrico. Suma de las medidas, dividida por el factor de conversión. 
-    *   **Factor de peso mínimo:** utilice el peso volumétrico solo si supera este valor. Límite de peso donde, a partir de este, se considerará el cálculo del peso volumétrico para el envío.
-    *   **Fines de semana y feriados:** días de la semana para las entregas. Marque los flags para activar la entrega en los siguientes escenarios: `entrega sábados`, `entrega domingos`, `entrega feriados`.
-*   **Fines de semana y feriados:**  para entregas en fines de semana o feriados. Marque los flags para habilitar la entrega en los siguientes escenarios: `entrega sábados`, `entrega domingos`, `entrega feriados`.
-*   **[Modalidades activas](https://help.vtex.com/es/tutorial/como-funciona-o-modal--tutorials_125):** especificaciones de productos que requieren una entrega especial. Estas son las limitaciones de envío del producto que permite la política de envío. Entender más sobre las modalidades. Marque los flags para habilitar la entrega en los siguientes escenarios: `productos químicos`, `electrónicos`, `muebles`, `vidrio`, `líquidos`, `colchones`, `productos refrigerados`, `llantas`, `electrodomésticos` y `armas de fuego`.
-*   **Ítems del paquete: **cantidad mínima de ítems aceptados por envío, de acuerdo con la política de envío.
-    *   **Valor mínimo:** valor mínimo aceptado por la política de envío para realizar el servicio.
-    *   **Mínimo de ítems:** múltiplo mínimo de la cantidad de ítems aceptados por la transportadora. Por ejemplo, si se rellena con el valor **3**, significa que la transportadora solo hace entregas con cantidades de ítems múltiplos de tres (3, 6, 9, 21...).
-    *   **Valor máximo:** valor máximo aceptado por la política de envío para realizar el servicio.
-*   **Relacionar puntos de recogida:** marque este flag, para abrir la opción de Puntos de Recogida. Haga clic en el menú desplegable y seleccione entre `Tags de los puntos de recogida`, `Nombres de los puntos de recogida` y `Importar puntos de recogida de los sellers` previamente registrados.
-*   **Configuración de tiempo:** seleccione el día y la hora de apertura y cierre en los siguientes escenarios. Puede añadir más de un plazo por escenario.
-*   **[Horario de atención:](https://help.vtex.com/es/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS)** horarios en los que la política de envío hace recolecciones o los periodos de envío en los que envía los ítems a los clientes. Estos ajustes influyen en el cálculo del plazo de entrega:
-    *   **Periodo de envío:** es donde se registran los periodos de atención de la política de envío, es decir, los horarios en los es posible recibir pedidos. Para configurar, seleccione la opción `Periodo de envío`:
-        *   Habilite `Aceptar compras fuera del horario de atención` si la política de envío acepta compras fuera del horario de atención. Ahora bien, aunque la política de envío acepte pedidos fuera del horario de atención, el tiempo hasta el próximo periodo disponible se añadirá al SLA final.
-        *   Seleccione `Día de la semana`, y rellene la hora de `inicio` y `fin`.
-        *   Para añadir más días de la semana, haga clic en `Nuevo periodo de envío`.
-    *   **Horario de recolección:** es donde se registran los horarios en que la política de envío recolecta los paquetes en su almacén o centro de distribución, para luego enviarlos a los clientes finales. Es importante destacar que si el pedido se realiza antes de la hora de recolección del mismo día, no se agregará tiempo adicional al SLA final, si se realiza después de la hora de recolección, el tiempo hasta el próximo horario de recolección se agregará al SLA.  
-        *   Seleccione `Día de la semana` y rellene el `Horario de recolección`. 
-        *   Para añadir más días de la semana, haga clic en `Nuevo horario de recolección`.
-*   **[Entrega programada](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)**: esta funcionalidad puede habilitarse si la política de envío ofrece un servicio de entrega programada. Aquí es donde debe añadir las ventanas de entrega que estarán disponibles para el cliente al final de la compra. Para utilizarla, habilite `entrega programada` y rellene:
-    *   **Tiempo máximo de entrega:** define el tiempo máximo de entrega, debe ser completado con el tiempo en días.
-    *   **Periodo de entrega:** define las ventanas de entrega de la política de entrega. Debe añadir los días de la semana, las horas de `inicio` y `fin` de la ventana de entrega y el valor adicional. Haga clic en `Nuevo periodo de entrega` para añadir más ventanas de entrega. 
-    *   **Capacidad de entrega:** le permite limitar el número de ítems/pedidos que pueden entregarse para cada ventana de entrega. Esta funcionalidad puede habilitarse o no. El uso o no de esta funcionalidad no interfiere con el funcionamiento de la plataforma. Para saber más sobre estos recursos, consulte [Entrega programada](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) y [Gestionar capacidad de entrega](https://help.vtex.com/es/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz). Si está habilitada debe: 
-        *   Elija la unidad de la capacidad de entrega entre `ítems` y `pedidos`.
-        *   Verifique las ventanas de entrega.
-        *   Definir el número de la `capacidad de entrega`. Recomendamos tener especial cuidado a la hora de elegir la unidad de capacidad de entrega porque el sistema no calcula la disponibilidad de la capacidad de entrega teniendo en cuenta la cantidad de ítems que se compran. Así, si la ventana de entrega todavía tiene capacidad para 2 ítems y su cliente está comprando 4 ítems, aún tendrá la opción de seleccionar la ventana de entrega disponible.
+## Política de envío y plantilla de envío
 
-## Editar Política de Envío 
+Cada política de envío está vinculada a una [plantilla de envío](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127), donde se registran detalles como:
 
-1. En el Admin VTEX, accede a **Envío > Estrategia de Envío > Políticas de Envío**, o escribe *Estrategia de Envío* en la barra de búsqueda en la parte superior de la página.  
-2. Haga clic en la `Política de Envío` que desee editar.  
-3. Altere `los campos de` [Registro de la Política de Envío](#registrar-politica-de-envio) y guarde los cambios.  
+* Identificación de la transportadora
+* Valor de envío cobrado por la transportadora
+* Rangos de códigos postales o [polígonos](https://help.vtex.com/es/tutorial/gerenciar-geolocalizacao--tutorials_138) válidos para envíos
 
-## Excluir Política de Envío
+Después de que se vincula la plantilla de envío a la política de envío, los datos pasan a formar parte de tu operación logística en VTEX.
+
+## Primeras configuraciones logísticas
+
+Las configuraciones se pueden realizar a través del Admin VTEX o API. Si estás empezando a configurar tu [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), sugerimos el siguiente orden de configuración:
+
+| **Tema** | **Configuración en el Admin VTEX** | **Configuración por API** |
+| :--- | :--- | :--- |
+| 1. Política de envío | [Crear una política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| 2. [Almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) | [Gestionar almacenes](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| 3. [Muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) | [Gestionar muelle](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
 
-1. En el Admin VTEX, accede a **Envío > Estrategia de Envío > Políticas de Envío**, o escribe *Estrategia de Envío* en la barra de búsqueda en la parte superior de la página.  
-2. Pase el cursor sobre la política de envío que desea excluir.
-3. Haga clic en el ícono de papelera.  
-5. Haga clic en el botón `Eliminar`.  
diff --git a/docs/tutorials/es/shipping-rate-template.md b/docs/tutorials/es/shipping-rate-template.md
index 52d5a564d..442081d51 100644
--- a/docs/tutorials/es/shipping-rate-template.md
+++ b/docs/tutorials/es/shipping-rate-template.md
@@ -3,8 +3,8 @@ title: 'Plantilla de flete'
 id: tutorials_127
 status: PUBLISHED
 createdAt: 2019-02-22T19:36:18.509Z
-updatedAt: 2023-03-29T18:18:59.537Z
-publishedAt: 2023-03-29T18:18:59.537Z
+updatedAt: 2023-10-10T13:26:19.271Z
+publishedAt: 2023-10-10T13:26:19.271Z
 firstPublishedAt: 2019-02-22T19:36:22.375Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -122,7 +122,7 @@ Vea la siguiente tabla para entender cada campo en detalle.
             <td class="t-body pa5" style="min-width: 15rem;">
                 <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">PricePercent</span>
             </td>
-            <td class="t-body pa5" style="min-width: 15rem;"> <a href="https://help.vtex.com/es/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV"> Adicional de precio</a>, calculado según el precio del carrito, expresado en número decimal. Para rellenar la tabla, utilice el valor en porcentaje (por ejemplo, para un 10% adicional, complete la tabla con el número 10).
+            <td class="t-body pa5" style="min-width: 15rem;"> <a href="https://help.vtex.com/es/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV"> Adicional de precio</a>, calculado según el precio de los productos en el carrito y expresado en número decimal. Para rellenar la tabla, utilice el valor en porcentaje. Por ejemplo, para un 10% adicional, complete la tabla con el número 10.
             </td>
             <td class="t-body pa5" style="min-width: 15rem;"> Utilice este campo en los casos en que haya un costo adicional en el precio de la entrega. Los <a href="https://help.vtex.com/es/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV"> adicionales de flete </a> se suman al valor fijo.
             </td>
@@ -181,11 +181,7 @@ Para facilitar el uso de los términos en nuestra documentación utilizamos «pe
 
 Vea el siguiente ejemplo de cómo rellenar los campos, teniendo en cuenta el formato aceptado en cada columna. 
 
-![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
-
-### Plantilla para Correios
-
-Si desea ofrecer la entrega por correo en Brasil, puede generar una plantilla automática con el estándar de VTEX. Acceda al integrador Correios, y genere la plantilla a través de la herramienta ofrecida por XP Agência en el link [XP planilhas](http://planilha.xpagencia.com.br/).
+![modelo_planilhanumerica](//images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
 
 ## Enviar el archivo por el Admin VTEX
 
@@ -198,7 +194,7 @@ El envío de la plantilla se realiza en el registro o en la edición de la _Pol
 3. Después de descargar la plantilla modelo y [completar los campos](#completar-los-campos-de-la-plantilla), cargue el archivo en la sección Cargar tarifas de envío, como se ilustra en la siguiente imagen. 
 4. Al finalizar, haga clic en `Guardar cambios`.
 
-  ![upload tarifas envioES](https://images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/b788e6926bffa8aa5a70db06ca1ccba7/upload_tarifas_envioES.png)
+  ![upload tarifas envioES](//images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/b788e6926bffa8aa5a70db06ca1ccba7/upload_tarifas_envioES.png)
 
 <div class="alert alert-warning">
 Para registrar una <b>nueva</b> Política de envío se debe completar otros campos además de la plantilla de flete.  Aprenda cómo crear, editar y completar todos los campos necesarios en el artículo <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">Política de envío</a>.
diff --git a/docs/tutorials/es/shipping-rates.md b/docs/tutorials/es/shipping-rates.md
index ea8346772..f319c1ddb 100644
--- a/docs/tutorials/es/shipping-rates.md
+++ b/docs/tutorials/es/shipping-rates.md
@@ -22,7 +22,7 @@ Las tarifas de envío son los costos de envío que su tienda ofrece a los client
 El <a href="https://help.vtex.com/es/tutorial/costo-final-del-envio--5bwhIO108VA5Y2YOpef9lV">costo final del envío</a> para el cliente incluye la tarifa de envío, los <a href="https://help.vtex.com/es/tutorial/adicionales-de-flete--2vqGwMn0LabkOHY6zSHYNV">adicionales de flete</a> y el costo del muelle con stock.
 </div>
 
-![Tarifa envio ES](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
+![Tarifa envio ES](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
 
 En el Admin VTEX, hay dos maneras de registrar las tarifas de envío:
 
diff --git a/docs/tutorials/es/shipping-simulation.md b/docs/tutorials/es/shipping-simulation.md
index d598a3ef4..575689f96 100644
--- a/docs/tutorials/es/shipping-simulation.md
+++ b/docs/tutorials/es/shipping-simulation.md
@@ -3,8 +3,8 @@ title: 'Simulador de envío'
 id: tutorials_144
 status: PUBLISHED
 createdAt: 2017-04-27T22:16:36.879Z
-updatedAt: 2023-03-29T19:24:17.032Z
-publishedAt: 2023-03-29T19:24:17.032Z
+updatedAt: 2024-06-18T19:48:13.737Z
+publishedAt: 2024-06-18T19:48:13.737Z
 firstPublishedAt: 2017-04-27T23:00:45.450Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -41,7 +41,7 @@ Puede haber una divergencia entre el precio final indicado por el simulador y el
  6. Seleccione la `cantidad` del SKU.  
  7. Determine el `Precio`. Este campo es abierto y opcional. 	  
 
- > El simulador no tiene en cuenta el precio registrado en el módulo Catálogo. Por lo tanto, el costo indicado por el simulador no considera ninguna promoción vigente para aquellos SKUs, y puede indicar un costo diferente del valor real en su tienda. Sugerimos que ingrese manualmente el valor exacto del SKU con las promociones aplicadas, para que el simulador devuelva un cálculo preciso.*
+ > El simulador no tiene en cuenta el precio registrado en el módulo Catálogo. Por lo tanto, el costo indicado por el simulador no considera ninguna promoción vigente para aquellos SKUs, y tampoco considera acréscimos de flete en el carrito, se los hay. Eso puede resultar en un costo diferente del valor real del producto en su tienda. Sugerimos que ingrese manualmente el valor exacto del SKU con las promociones aplicadas, para que el simulador devuelva un cálculo preciso.
 
  8. Haga clic en el ícono `+` para agregar más de un producto en la simulación. 
 Si lo desea, puede seleccionar la casilla `Simular ítems individualmente`.  
@@ -60,7 +60,7 @@ En el resultado de la simulación, las medidas del ítem aparecen en centímetro
 
 ## Detalles de la simulación
 
-La simulación de flete indica todas las posibilidades de envío y la disponibilidad de los ítems incluidos en la simulación y describe los [detalles de entrega de un pedido](https://help.vtex.com/es/tutorial/ver-detalhes-de-entrega-de-um-pedido?locale=pt), el valor del flete y el tiempo de entrega tomando en cuenta las particularidades que se indican a continuación.
+La simulación de flete indica todas las posibilidades de envío y la disponibilidad de los ítems incluidos en la simulación y describe los [detalles de entrega de un pedido](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl), el valor del flete y el tiempo de entrega tomando en cuenta las particularidades que se indican a continuación.
 
 * **Transportadoras desconsideradas**: al realizar la simulación, algunas transportadoras pueden estar indisponibles porque no cumplen los criterios de la [ Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) (vea 
 [transportadoras desconsideradas](#transportadoras-desconsideradas) para más información)
diff --git a/docs/tutorials/es/shipping-strategy.md b/docs/tutorials/es/shipping-strategy.md
index 05aa1d1a5..92fbfa1f0 100644
--- a/docs/tutorials/es/shipping-strategy.md
+++ b/docs/tutorials/es/shipping-strategy.md
@@ -3,8 +3,8 @@ title: 'Estrategia de envío'
 id: 58vLBDbjYVQzJ6rRc5QNz3
 status: PUBLISHED
 createdAt: 2021-07-15T17:04:23.563Z
-updatedAt: 2021-09-23T22:21:40.782Z
-publishedAt: 2021-09-23T22:21:40.782Z
+updatedAt: 2024-01-31T15:00:05.216Z
+publishedAt: 2024-01-31T15:00:05.216Z
 firstPublishedAt: 2021-07-15T17:27:37.590Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Estrategia de envío es la relación entre stock, muelle y política de envío; es decir, la forma en que se comunican el stock, el muelle y la política de envío definirá la coordinación de la estructura de entrega de los pedidos de la tienda. 
 
-![EstrategiaEnvio_ES](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/ed9784e5cbc67a42358ad4f37c3baa00/Frame_2__2_.svg)
+![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
    <tr class="bb b--muted-3">
@@ -42,15 +42,13 @@ Estrategia de envío es la relación entre stock, muelle y política de envío;
             </td>
     </tr>
 </table>
-<div class="alert alert-warning">
-Como el almacén forma parte del sistema logístico de su tienda, le sugerimos que registre los módulos relacionados con la operación logística en el siguiente orden:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
-</a></li>
-  <li><a href="https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj">Muelle;</a></li>
-  <li><a href="https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Stock.</li></a>
- </ol>
-</body>
-</div>
+
+## Primeras configuraciones logísticas
+
+Las configuraciones se pueden realizar a través del Admin VTEX o API. Si estás empezando a configurar tu estrategia de envío, sugerimos el siguiente orden de configuración:
+
+| **Tema** | **Configuración en el Admin VTEX** | **Configuración por API** |
+| :--- | :--- | :--- |
+| 1. [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) | [Crear una política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| 2. [Almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) | [Gestionar almacenes](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| 3. [Muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) | [Gestionar muelle](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
diff --git a/docs/tutorials/es/shopee-integration.md b/docs/tutorials/es/shopee-integration.md
index d888cc6c0..61ad4f163 100644
--- a/docs/tutorials/es/shopee-integration.md
+++ b/docs/tutorials/es/shopee-integration.md
@@ -3,8 +3,8 @@ title: 'Integración con Shopee'
 id: 5OV9idUY6fHu3P8grnCnqj
 status: PUBLISHED
 createdAt: 2022-09-05T19:33:02.717Z
-updatedAt: 2022-12-08T20:41:49.398Z
-publishedAt: 2022-12-08T20:41:49.398Z
+updatedAt: 2024-04-17T16:10:43.661Z
+publishedAt: 2024-04-17T16:10:43.661Z
 firstPublishedAt: 2022-09-06T01:42:40.106Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/site-editor-overview.md b/docs/tutorials/es/site-editor-overview.md
index c3b863489..d5791d237 100644
--- a/docs/tutorials/es/site-editor-overview.md
+++ b/docs/tutorials/es/site-editor-overview.md
@@ -23,7 +23,7 @@ El Site Editor es una interfaz gráfica para la gestión de contenidos de tu sto
 
 En el Admin VTEX, accede **Storefront > Site Editor** y verifica las principales herramientas disponibles en la interfaz gráfica.
 
-![Site Editor - ES](https://images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/2c015dae64ff236deade75f75990f9bc/site-editor-ui-es.png)
+![Site Editor - ES](//images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/2c015dae64ff236deade75f75990f9bc/site-editor-ui-es.png)
 
 | **Herramienta**    | **Descripción** |
 | ----------        | ----------    |
diff --git a/docs/tutorials/es/sku-bindings.md b/docs/tutorials/es/sku-bindings.md
index 3b17d0e23..c59791aed 100644
--- a/docs/tutorials/es/sku-bindings.md
+++ b/docs/tutorials/es/sku-bindings.md
@@ -1,10 +1,10 @@
 ---
 title: 'Vínculos de SKU'
 id: 1SmrVgNwjJX17hdqwLa0TX
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-27T17:27:26.963Z
-updatedAt: 2023-05-25T15:51:50.053Z
-publishedAt: 2023-03-31T19:05:52.334Z
+updatedAt: 2024-01-23T15:50:13.022Z
+publishedAt: 2024-01-23T15:50:13.022Z
 firstPublishedAt: 2022-05-31T17:14:23.589Z
 contentType: tutorial
 productTeam: Channels
@@ -27,7 +27,7 @@ Por defecto, para los <a href="https://help.vtex.com/es/tutorial/seller-white-la
 
 La página **Vínculos de SKU** le permite al _marketplace_ seguir y gestionar la vinculación entre los SKU del _seller_ y los del _marketplace_. Para acceder a la página, en el Admin VTEX, ingresa a **Marketplace > Sellers > Vínculos de SKU**. Aparecerá la siguiente interfaz:
 
-![sku-bindings-es](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/fcca860e97e41d512f9f88d53d6d09fd/sku-bindings-es.png)
+![sku-bindings-es](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/fcca860e97e41d512f9f88d53d6d09fd/sku-bindings-es.png)
 
 La tabla a continuación contiene la descripción de las columnas de la lista de vínculos de SKU:
 
diff --git a/docs/tutorials/es/sku-price-change.md b/docs/tutorials/es/sku-price-change.md
index a978d4f61..4b3a813c7 100644
--- a/docs/tutorials/es/sku-price-change.md
+++ b/docs/tutorials/es/sku-price-change.md
@@ -3,8 +3,8 @@ title: 'Alterar precio de SKU'
 id: tutorials_95
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:48.759Z
-updatedAt: 2023-03-30T16:36:10.950Z
-publishedAt: 2023-03-30T16:36:10.950Z
+updatedAt: 2024-01-05T17:59:41.793Z
+publishedAt: 2024-01-05T17:59:41.793Z
 firstPublishedAt: 2017-04-27T23:00:42.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -45,8 +45,8 @@ Esas casillas representan las informaciones que son alteradas en cualquier una d
 
 La diferencia es que, manualmente, quien rellena visualiza ese formulario, vía importación por plantilla están dispuestos en columnas y vía integración son casillas en la estructura de request en formato JSon.
 
-- **ID:** código del SKU que accedió
-- **Sku:** nombre del SKU
+- **ID:** código del SKU que accedió.
+- **Sku:** nombre del SKU.
 - **Aliado (utm_source):** Casilla opcional. Se trata de un parámetro para condicionar una colocación de precio diferenciada, a partir del uso en el sitio web de la utm source que se catastre aquí.
 - **Audiencia de Campaña (utm_campaign):** Casilla opcional. Se trata de un parámetro para condicionar una colocación de precio diferenciada, a partir del uso en el sitio web de la utm campaign que se catastre aquí, la cual también puede ser utilizada en enlaces de mail marketing.
 - **Audiencia de Campaña interna (utmi_cp):** Casilla opcional. Se trata de un parámetro para condicionar una colocación de precio diferenciada, a partir del uso en el sitio web de la utm source que se catastre aquí. Utilizada usualmente para empleados de la tienda, cuando es el caso de tener condiciones de compra diferenciada.
@@ -68,7 +68,7 @@ Se utiliza esa herramienta usualmente para actualización de precios en masa, qu
 5. Después en el enlace __Exportar/importar valores__.
 6. Seleccione la pestaña __Exportar__ y haga clic en el botón __Exportar para Excel__. 
 7. El sistema procesará la solicitación internamente y, cuando esté listo, enviará para el correo electrónico que digite en la casilla __E-mail para notificação__. Por defecto, viene rellenado con el correo electrónico del usuario que accedió el Admin.
-8. Este paso es importante, pues garantiza que el formato de su plantilla sea el correcto y minimiza problemas en el momento de la importación;
+8. Este paso es importante, pues garantiza que el formato de su plantilla sea el correcto y minimiza problemas en el momento de la importación.
 
 Después que llegue el correo electrónico y haga la descarga, altere solamente aquellos SKUs que realmente necesitarán de actualización, los demás pueden ser excluidos de la plantilla, así la importación llevará menos tiempo y evitará reindexación desnecesaria de los productos que no se modificaron. Es importante destacar que el formato aceptado por la plataforma para importar la plantilla es el .xls. Teniendo en cuenta que no cerró la página del admin, siga los pasos abajo:
 
@@ -83,26 +83,23 @@ Después que llegue el correo electrónico y haga la descarga, altere solamente
 
 Esas son las columnas de la plantilla que llega en el correo electrónico del usuario, cuando hace la exportación conforme mencionado en el paso a paso más arriba. Abajo está escrito exactamente como está en la plantilla. La obligatoriedad de relleno de cada columna sigue el mismo estándar de las casillas del formulario descrito en el referido tópico más arriba.
 
-- **StockKeepingUnitId:** id del SKU;
-- **Source:** utm\_source;
-- **Price:** precio de venta del producto;
-- **Id:** id del precio. No altere ese valor, sino el sistema creará una nueva línea en el cuadro de precio y quedarán dos precios catastrados para el SKU;
-- **StoreId:** id de la política comercial donde se aplicará el precio. Caso tenga duda de cuál es el código de identificación de alguna política, acceda el módulo de E-Commerce &gt; Marketplace &gt; Política Comercial. Verifique el número que aparece en la columna “Id &#8211; Nombre”, ese es el código que deberá utilizar aquí;
-- **Medium (Desconsiderar):** Casilla descontinuada;
-- **Campaign:** utm\_campaign;
-- **InternalCampaign:** utmi\_cp;
+- **StockKeepingUnitId:** id del SKU.
+- **Source:** utm\_source.
+- **Price:** precio de venta del producto.
+- **Id:** id del precio. No altere ese valor, sino el sistema creará una nueva línea en el cuadro de precio y quedarán dos precios catastrados para el SKU.
+- **StoreId:** id de la política comercial donde se aplicará el precio. Caso tenga duda de cuál es el código de identificación de alguna política, acceda el módulo de E-Commerce &gt; Marketplace &gt; Política Comercial. Verifique el número que aparece en la columna “Id &#8211; Nombre”, ese es el código que deberá utilizar aquí.
+- **Medium (Desconsiderar):** Casilla descontinuada.
+- **Campaign:** utm\_campaign.
+- **InternalCampaign:** utmi\_cp.
 - **DateFrom:** fecha del inicio de la vigencia del precio. Rellenar en el formato dd/mm/aaaa.
 - **DateTo:** fecha del final de la vigencia del precio. Rellenar en el formato dd/mm/aaaa.
-- **ListPrice:** precio de, también conocido como precio de lista. Es aquél que aparece tachado (ej.: De: R$ 10,00) en el sitio web;
-- **RefId (No alterable):** código de referencia de producto, conforme catastro del producto. No alterar ese valor;
-- **Ean13Default (No alterable):** ean del producto, conforme catastro del producto. No alterar ese valor;
-- **BrandName (No alterable):** marca del producto, conforme catastro del producto. No alterar ese valor;
-- **StockKeepingUnitName (No alterable):** nombre del SKU, conforme catastro del producto. No alterar ese valor;
+- **ListPrice:** precio de, también conocido como precio de lista. Es aquél que aparece tachado (ej.: De: R$ 10,00) en el sitio web.
+- **RefId (No alterable):** código de referencia de producto, conforme catastro del producto. No alterar ese valor.
+- **Ean13Default (No alterable):** ean del producto, conforme catastro del producto. No alterar ese valor.
+- **BrandName (No alterable):** marca del producto, conforme catastro del producto. No alterar ese valor.
+- **StockKeepingUnitName (No alterable):** nombre del SKU, conforme catastro del producto. No alterar ese valor.
 - **SellerId:** id del seller dueño del producto. Solamente vendrá rellenado caso su tienda sea marketplace de otra tienda.
 
 ## A través de la integración con ERP
 
-Se la configura normalmente en el momento de la puesta en marcha de su tienda y se debe seguir el manual de integración junto a su equipo técnico, para evitar integraciones inconsistentes o cualquier problema que pueda perjudicar la información que alimentará la plataforma. Tiene lugar la actualización de precio vía REST, a través del método POST con body en el estándar JSon.
-
-Lea la documentación de la API en nuestros Developer Docs:
-https://developers.vtex.com/reference/pricing-api-overview#listorders
+Se la configura normalmente en el momento de la puesta en marcha de su tienda y se debe seguir el manual de integración junto a su equipo técnico, para evitar integraciones inconsistentes o cualquier problema que pueda perjudicar la información que alimentará la plataforma. La actualización de precios se realiza vía API, para información acceder [API de precios](https://developers.vtex.com/docs/api-reference/pricing-api#overview).
diff --git a/docs/tutorials/es/sku-registration-fields.md b/docs/tutorials/es/sku-registration-fields.md
index 5a8f29700..0a2a43d74 100644
--- a/docs/tutorials/es/sku-registration-fields.md
+++ b/docs/tutorials/es/sku-registration-fields.md
@@ -3,8 +3,8 @@ title: 'Rellenar campos de registro de SKU'
 id: 21DDItuEQc6mseiW8EakcY
 status: PUBLISHED
 createdAt: 2017-09-22T00:20:45.920Z
-updatedAt: 2022-12-19T18:03:03.864Z
-publishedAt: 2022-12-19T18:03:03.864Z
+updatedAt: 2023-07-14T20:59:40.541Z
+publishedAt: 2023-07-14T20:59:40.541Z
 firstPublishedAt: 2017-09-22T00:40:16.232Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Para entender mejor el significado de cada campo del registro, vea la descripci
 
 __Nombre del Producto:__ ya está completado con el nombre del producto al que pertenecerá el SKU.
 
-__Nombre:__ debe contener el nombre del SKU, es decir, la variación del producto, que ya ha sido registrada anteriormente. Producto - Heladera, SKU -110 voltios.
+__Nombre:__ debe contener el nombre del SKU, es decir, la variación del producto, que ya ha sido registrada anteriormente. Ejemplo: Producto - Heladera, SKU - 110 voltios.  El nombre del SKU está limitado a 200 caracteres.
 
 __Valor de Fidelidad:__ crédito que el cliente recibe al realizar la compra de 1 unidad de un determinado SKU. Poniendo "1,00" en este campo, el cliente gana un crédito de $ 1,00 en el sitio web.
 
diff --git a/docs/tutorials/es/skus.md b/docs/tutorials/es/skus.md
new file mode 100644
index 000000000..a782a0582
--- /dev/null
+++ b/docs/tutorials/es/skus.md
@@ -0,0 +1,130 @@
+---
+title: 'SKUs'
+id: 4zkfF1asM3ayvIigsySevw
+status: DRAFT
+createdAt: 2024-02-02T18:06:58.601Z
+updatedAt: 2024-05-27T20:55:21.862Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: skus
+locale: es
+legacySlug: skus
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+# SKU
+
+El conjunto de datos de SKU se encuentra en la tabla `products_sku`. Esta tabla centraliza información detallada de los productos, incluidos identificadores, descripciones y datos de marca, lo que facilita la gestión y el análisis de los catálogos de productos.  
+
+En esta sección puedes consultar la siguiente información:
+
+- [Características de los datos de SKU](#características-de-los-datos)  
+- [Tabla products_sku](#tabla-products-sku)  
+- [Análisis con products_sku](#analisis-con-products-sku)  
+- [Correlaciones con otros datos](#correlaciones-con-otros-datos)  
+
+## Características de los datos
+
+|**Característica**|**Descripción**|
+| - | - |
+|**Origen**|Procedentes del **catálogo de productos**.|
+|**Disponibilidad**|Se puede acceder a los datos del catálogo a través del informe del Admin VTEX y también a través de [API de catálogo](https://developers.vtex.com/docs/api-reference/catalog-api/).|
+|**Historial**|Los datos se conservan durante dos años, a partir de 2024 para clientes que ya utilizan la plataforma VTEX.|
+|**Intervalo mínimo de actualización**|Una hora.|
+
+## Tabla products_sku
+
+Además de la información ya mencionada sobre los datos de catálogo, la tabla centraliza información de identificación de producto, como descripción, marca y especificaciones.  
+Estos son los campos que componen la tabla.  
+
+| **Nombre de la columna** | **Tipo de columna** | **Descripción de la columna** |
+|:---:|:---:|:---:|
+| **id** | integer | Identificador único del producto. |
+| **product_id** | integer | Identificador único del producto en el sistema. |
+| **name_complete** | character varying(255) | Nombre completo del producto. |
+| **complement_name** | character varying(255) | Nombre adicional del producto. |
+| **product_name** | character varying(255) | Nombre del producto. |
+| **product_description** | character varying(1000) | Descripción detallada del producto. |
+| **sku_name** | character varying(255) | Nombre del SKU del producto. |
+| **producto_ref_id** | character varying(255) | Referencia externa o interna del producto. |
+| **tax_code** | character varying(255) | Código fiscal asociado al producto. |
+| **is_active** | boolean | Indica si el producto está activo. |
+| **is_transported** | boolean | Indica si el producto es transportable. |
+| **is_inventoried** | boolean | Indica si el producto está sujeto a stock. |
+| **is_gift_card_recharge** | boolean | Indica si el producto es una recarga de tarjeta de regalo. |
+| **image_url** | character varying(1024) | URL de la imagen del producto. |
+| **image_url** | character varying(1024) | URL de detalles de producto. |
+| **csc_identification** | character varying(255) | Identificación CSC del producto. |
+| **brand_id** | character varying(255) | Identificador de la marca del producto. |
+| **brand_name** | character varying(255) | Marca del producto. |
+| **is_brand_active** | boolean | Indica si la marca del producto está activa. |
+| **dimension** | super | Dimensiones del producto. |
+| **real_dimension** | super | Dimensiones reales del producto. |
+| **manufacturer_code** | character varying(255) | Código de fabricante del producto. |
+| **is_kit** | boolean | Indica si el producto es un kit. |
+| **kit_items** | super | Ítems incluidos en el kit del producto. |
+| **services** | super | Servicios asociados al producto. |
+| **categories** | super | Categorías a las que pertenece el producto. |
+| **categories_full_path** | super | Ruta completa de las categorías del producto. |
+| **attachments** | super | Anexos asociados al producto. |
+| **collections** | super | Colecciones a las que pertenece el producto. |
+| **sku_sellers** | super | Sellers del SKU del producto. |
+| **sales_channels** | super | Canales de venta del producto. |
+| **images** | super | Imágenes del producto. |
+| **videos** | super | Videos del producto. |
+| **sku_specifications** | super | Especificaciones de SKU del producto. |
+| **product_specifications** | super | Especificaciones del producto. |
+| **product_clusters_ids** | character varying(255) | ID de clústeres de productos. |
+| **positions_in_clusters** | super | Posiciones en los clústeres de productos. |
+| **product_cluster_names** | super | Nombre de los clústeres de productos. |
+| **product_cluster_highlights** | super | Puntos destacados de los clústeres de productos. |
+| **product_category_ids** | character varying(255) | ID de las categorías de producto. |
+| **is_direct_category_active** | boolean | Indica si la categoría directa del producto está activa. |
+| **product_global_category_id** | integer | ID de categoría global del producto. |
+| **product_categories** | super | Categorías del producto. |
+| **commercial_condition_id** | integer | ID de la condición comercial del producto. |
+| **reward_value** | double precision | Valor de recompensa asociado al producto. |
+| **alternate_ids** | super | ID alternativos del producto. |
+| **alternate_id_values** | super | Valores de los ID alternativos del producto. |
+| **estimated_date_arrival** | character varying(255) | Fecha estimada de llegada del producto. |
+| **measurement_unit** | character varying(255) | Unidad de medida del producto. |
+| **unit_multiplier** | double precision | Multiplicador de la unidad del producto. |
+| **information_source** | character varying(255) | Fuente de información del producto. |
+| **modal_type** | character varying(255) | Tipo de modal de producto. |
+| **key_words** | character varying(1000) | Palabras clave asociadas al producto. |
+| **release_date** | character varying(255) | Fecha de lanzamiento del producto. |
+| **product_is_visible** | boolean | Indica si el producto es visible. |
+| **show_if_not_available** | boolean | Indica si el producto debe mostrarse aunque no esté disponible. |
+| **is_product_active** | boolean | Indica si el producto está activo. |
+| **product_final_score** | integer | Puntuación final del producto. |
+| **account_name** | character varying(255) | Nombre de la cuenta asociada al producto. |
+| **batch_id** | character varying(13) | ID de control del lote de ingesta de datos. |  
+
+## Análisis con products_sku
+
+Consulta a continuación algunos de los distintos análisis posibles con la tabla del catálogo:  
+
+- **Análisis de desempeño de producto:** calcula las ventas por SKU para identificar los productos más populares, orientando las estrategias de marketing y reposición.  
+- **Tendencias de categoría de producto:** agrupa los SKU por categoría para analizar las tendencias de ventas en diferentes segmentos, ajustando el enfoque del catálogo según sea necesario.  
+- **Análisis de precios y promociones:** examina los precios y las condiciones comerciales de cada SKU para identificar oportunidades de promociones y ajustes de precios.  
+- **Monitoreo de stock:** comprueba la disponibilidad de cada SKU con respecto a las tendencias de ventas para gestionar el stock de manera eficiente.  
+
+## Correlaciones con otros datos
+
+Las correlaciones de datos de catálogo con otros conjuntos de datos son esenciales para realizar análisis en profundidad.  
+Consulta a continuación algunos ejemplos de correlaciones:  
+
+- **Interacción con datos de stock:** la correlación entre los SKU y el stock es clave para gestionar las operaciones de ventas y stock, alineando la disponibilidad de los productos con la demanda.  
+- **Datos de pedidos:** el análisis conjunto del catálogo con datos de pedidos revela insights sobre las preferencias de compra, lo que ayuda a optimizar el catálogo.  
+- **Datos de navegación:** la interacción con datos de navegación ofrece una visión de cómo los clientes exploran el catálogo, indicando los productos que captan más atención y guiando las estrategias de marketing y promoción.  
+
+### Descubra otros conjuntos de datos
+
+- [Stock](2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navegación](4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagos](7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Promociones](3WZ1syNucDFdvVhfKtA6Qd)  
diff --git a/docs/tutorials/es/smartcheckout-v5-general-characteristics.md b/docs/tutorials/es/smartcheckout-v5-general-characteristics.md
new file mode 100644
index 000000000..76acfa084
--- /dev/null
+++ b/docs/tutorials/es/smartcheckout-v5-general-characteristics.md
@@ -0,0 +1,69 @@
+---
+title: 'Características generales de SmartCheckout ™ V5'
+id: tutorials_3811
+status: PUBLISHED
+createdAt: 2017-04-27T21:51:49.943Z
+updatedAt: 2024-02-08T15:03:13.491Z
+publishedAt: 2024-02-08T15:03:13.491Z
+firstPublishedAt: 2017-04-27T23:11:15.321Z
+contentType: tutorial
+productTeam: Shopping
+author: authors_65
+slug: caracteristicas-generales-smartcheckout-v5
+locale: es
+legacySlug: cambio-la-nueva-version-de-smart-checkout
+subcategory: 8AGXmtpbTqUE2KQu0Swwk
+---
+
+SmartCheckout™ V5 permite la compra sin login y contraseña de VTEX (one-click-buy checkout). Listamos aquí sus principales características y ventajas.
+
+### Iframe para pagos con tarjeta
+
+Las formas de pago con tarjeta de crédito, débito y private label (tarjetas emitidas por su marca y aceptadas sólo dentro de su red de tiendas) ahora están aislados en un iframe. Esto hace que la personalización de JavaScript sea imposible, lo que aumenta la seguridad de su tienda. Para obtener más información sobre la protección de datos, visite [Seguridad de SmartCheckout](https://help.vtex.com/es/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB#).
+
+Tenga en cuenta que, a pesar de estar en un iframe, todavía es posible aplicar CSS normalmente en el campo. Pero es importante prestar atención al selector CSS utilizado porque, por ser un iframe, debe comenzar con elementos que estén dentro de `#app-container .App` sin, por ejemplo, `#payment-data` o `.payment-group` (que están fuera del iframe).
+
+En el ejemplo práctico, para ocultar la opción "Pagar usando dos tarjetas", sólo se debe utilizar `.ChangeNumberOfPayments {display: none}`.
+
+### Nueva opción de cálculo de flete por geocoordenada
+
+A través de esta función, se puede establecer regiones de entrega utilizando como base un punto geográfico (latitud y longitud) en lugar de un código postal.
+
+Para conocer el detalle de cómo utilizar esta función, lea el artículo de [Geolocalización en el checkout](/es/tutorial/geolocalizacion-en-el-checkout).
+
+__Atención:__ Una vez que la API key sea informada en las configuraciones del checkout, la geolocalización ya estará visible en el checkout de su tienda, independiente de la activación de la nueva versión del SmartCheckout.
+
+### Título de la página
+
+El título de la página de SmartCheckout™, que aparece en la barra o en la pestaña del navegador, se puede personalizar. Para saber cómo hacerlo, sólo tienes que seguir los siguientes pasos:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Storefront > Checkout__, o escribe __Checkout__ en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en el icono <i class="fas fa-cog" alt="blue gear"></i> del sitio deseado.
+3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Checkout__.
+4. En el campo __Título del sitio web__, escriba el título deseado y verifique el resultado en el cuadro VISTA PREVIA.
+5. Haga clic en `Guardar`.
+
+### JavaScript personalizado
+
+Usted puede utilizar los archivos `checkout5-custom.js` y `orderplaced2-custom.js` para insertar sus personalizaciones de JavaScript en el Checkout y en la pantalla de pedido terminado, respectivamente. Para acceder a ellos, siga los siguientes pasos:
+
+1. En el Admin VTEX, accede a __Configuración de la tienda > Storefront > Checkout__, o escribe __Checkout__ en la barra de búsqueda en la parte superior de la página.
+2. Haga clic en el icono <i class="fas fa-cog" alt="blue gear"></i> del sitio deseado.
+3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Código__.
+4. En el menú __Archivos__, ubicado en el lado derecho de la página, haga clic en los que desea realizar ajustes en el código.
+5. Haga clic en `Guardar`
+
+<div class="alert alert-warning">
+  Personalizar archivos de JavaScript puede ser dañino para su Checkout. VTEX <b>no recomienda</b> personalizaciones y no es responsable de los daños causados por este código.
+</div>
+
+__IMPORTANTE:__ no utilize estos archivos para insertar tags de marketing e integraciones. Si las necesita, utilize Google Tag Manager.
+
+### PayPal Plus
+
+El SmartCheckout™ V5 soporta el método de pago PayPal Plus, que permite que el pago se realize directamente en su website, sin redirigir sus clientes (checkout transparente).
+
+### Google Enhanced Ecommerce
+
+El SmartCheckout™ V5 suma al data layer informaciones para utilización de Google Enhanced Ecommerce. Para aprender a crear estas tags, acceda a la documentación de Google: https://developers.google.com/tag-manager/enhanced-ecommerce.
+
diff --git a/docs/tutorials/es/special-conditions.md b/docs/tutorials/es/special-conditions.md
index 55d3e2a00..341b05b32 100644
--- a/docs/tutorials/es/special-conditions.md
+++ b/docs/tutorials/es/special-conditions.md
@@ -3,8 +3,8 @@ title: 'Configurar condiciones especiales de pago'
 id: tutorials_456
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:58.783Z
-updatedAt: 2023-02-24T20:54:02.331Z
-publishedAt: 2023-02-24T20:54:02.331Z
+updatedAt: 2023-07-27T16:59:12.708Z
+publishedAt: 2023-07-27T16:59:12.708Z
 firstPublishedAt: 2017-04-27T23:03:26.753Z
 contentType: tutorial
 productTeam: Financial
@@ -19,11 +19,7 @@ Las condiciones especiales forman parte de la configuración de las condiciones
 
 Para identificar las condiciones especiales aplicables a cada método de pago, en VTEX Admin, acceda a __Pago > Configuraçión > Condiciones de Pago__, seleccione el método de pago deseado y verifique las opciones como se muestra en la siguiente ilustración.
 
-![condiciones especiales de pago](https://images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/1f9aaa7975a61f40c575db834c163a6b/Condiciones_especiales_de_pago.png)
-
-<div class = "alert alert-info">
-  <p>Las condiciones especiales de las reglas de pago se aplican solo al número de cuotas. El método de pago sigue siendo el mismo.</p>
-</div>
+![condiciones especiales de pago](//images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/1f9aaa7975a61f40c575db834c163a6b/Condiciones_especiales_de_pago.png)
 
 ## Condición Comercial
 
@@ -33,7 +29,7 @@ Para saber cómo catastrar una nueva condición comercial y asociarla a un SKU,
 
 ## Cómo configurar la condición comercial en la condición de pago
 
-![condicao-comercial es](https://images.ctfassets.net/alneenqid6w5/4Cgc0FUB6oumYi88MOgsYY/359a21a1aa8610eded88339b0ea45f62/condicion-comercial.png)
+![condicao-comercial es](//images.ctfassets.net/alneenqid6w5/4Cgc0FUB6oumYi88MOgsYY/359a21a1aa8610eded88339b0ea45f62/condicion-comercial.png)
 
 1. Dentro de la condición de pago, haga clic en `Añadir condición especial`.
 3. A continuación, haga clic en `Condición Comercial`.
@@ -93,7 +89,7 @@ Permite poner a disposición una condición de pago para una política comercial
 
 Cómo configurar la política comercial en la condición de pago
 
-![politica-comercial es](https://images.ctfassets.net/alneenqid6w5/kfa8VsYOR26c2kkuumcCY/5a94b3b98926e993bd9914eb39deb0d6/venta-politica.png)
+![politica-comercial es](//images.ctfassets.net/alneenqid6w5/kfa8VsYOR26c2kkuumcCY/5a94b3b98926e993bd9914eb39deb0d6/venta-politica.png)
 
 1. Dentro de la condición de pago, haga clic en `Añadir condición especial`.
 2. A continuación, haga clic en `Política Comercial (Canal de Ventas)`.
@@ -118,7 +114,7 @@ Cómo configurar el banco emisor en la condición de pago:
 6. Si desea segmentar por co-brand, seleccione la opción deseada en Co-brand (esta casilla de selección solo aparecerá si su tienda ha informado a VTEX la lista de tarjetas con co-brand).
 7. Guarde los cambios.
 
-![banco-emissor es](https://images.ctfassets.net/alneenqid6w5/2mgaZy8JoY0O06UIGAsAoy/4000a63524a0ce2e2f86bdb3b0902511/banco-emisor.png)
+![banco-emissor es](//images.ctfassets.net/alneenqid6w5/2mgaZy8JoY0O06UIGAsAoy/4000a63524a0ce2e2f86bdb3b0902511/banco-emisor.png)
 
 ### Ejemplos
 
@@ -150,7 +146,7 @@ Permite configurar una validez en la condición de pago, para que deje de ser ap
 
 Cómo configurar el período en la condición de pago
 
-![periodo es](https://images.ctfassets.net/alneenqid6w5/6NORGuNOZUegEc0sm6YOQC/788aedda7526d5b7395aa504a15a5b48/periodo-es.png)
+![periodo es](//images.ctfassets.net/alneenqid6w5/6NORGuNOZUegEc0sm6YOQC/788aedda7526d5b7395aa504a15a5b48/periodo-es.png)
 
 1. Dentro de la condición de pago, haga clic en `Añadir condición especial`.
 3. A continuación, haga clic en `Período`.
diff --git a/docs/tutorials/es/split-payment.md b/docs/tutorials/es/split-payment.md
index 85f0027d5..b37ac31bc 100644
--- a/docs/tutorials/es/split-payment.md
+++ b/docs/tutorials/es/split-payment.md
@@ -3,8 +3,8 @@ title: 'Split de pagos'
 id: 6k5JidhYRUxileNolY2VLx
 status: PUBLISHED
 createdAt: 2021-04-06T20:03:53.443Z
-updatedAt: 2023-04-24T19:09:31.016Z
-publishedAt: 2023-04-24T19:09:31.016Z
+updatedAt: 2024-06-18T17:50:44.146Z
+publishedAt: 2024-06-18T17:50:44.146Z
 firstPublishedAt: 2021-04-07T18:57:19.713Z
 contentType: tutorial
 productTeam: Financial
@@ -19,55 +19,52 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 Esta es una solución de pagos para marketplace.
 </div>
 
-Para garantizar que nuestros clientes de *marketplace* automáticamente dividan el pago entre todos los *sellers*, establezcan comisiones basadas en un porcentaje fijo y cumplan con las regulaciones vigentes, VTEX ofrece la solución de __*split* de pagos__.
+Para garantizar que nuestros clientes de [marketplace](https://help.vtex.com/es/tutorial/que-es-un-marketplace--680lLJTnmEAmekcC0MIea8) automáticamente dividan el pago entre todos los [sellers](https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w), establezcan comisiones basadas en un porcentaje fijo y permanece operando de acuerdo con las regulaciones vigentes, VTEX ofrece el __Split de pagos__.
 
-Cuando un comprador añade varios productos de diferentes *sellers* al carrito de compra y realiza el pago mediante una experiencia de *checkout* unificada, VTEX automáticamente divide el pago para que cada parte pueda recibir la porción que le corresponde directamente en su cuenta de banco.
+A continuación se muestran dos ejemplos de escenarios de aplicación de split de pagos en los que un consumidor agrega productos de diferentes vendedores al mismo carrito:
 
-Sin embargo, esta cantidad no siempre se divide por igual entre las partes. La distribución se realiza de acuerdo con las condiciones predefinidas por el *seller* y las comisiones del *marketplace*. La configuración de *split* de pagos permite que la cantidad que se paga por el pedido automáticamente se divida entre los [*sellers*](https://help.vtex.com/es/tutorial/what-is-a-seller) y los [*marketplaces*](https://help.vtex.com/es/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8).
+1. Cuando el marketplace es responsable de procesar el pago de la compra, VTEX automáticamente divide este pago para que cada beneficiario reciba su parte directamente en su propia cuenta bancaria, realizando así el [Split de cobros](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx#split-de-cobros).
+2. Cuando el carrito involucra sellers que son responsables de procesar su propio método de pago (sin depender del marketplace), VTEX crea diferentes transacciones de pago para el marketplace y los sellers, realizando el [Split de transacción](https://help.vtex.com/es/tutorial/split-de-pagos--6k5JidhYRUxileNolY2VLx#split-de-transaccion).
 
-Puede configurar el *split* de pagos de dos maneras diferentes: [*split* de cobros](https://help.vtex.com/en/tutorial/split-payment#split-de-cobros) y [*split* de transacción](https://help.vtex.com/en/tutorial/split-payment#split-de-transaccion). Hay algunas diferencias entre los dos tipos de *split* de pagos que debe tomar en consideración antes de elegir cuál utilizará.
+<div class="alerta alerta-advertencia">
+La distribución de los importes de las compras siempre se lleva a cabo de acuerdo con acuerdos de porcentaje de comisión predefinidos entre el marketplace y los sellers.
+</div>
+
+Consulte a continuación para obtener más detalles sobre cada uno de los modelos de split de pagos:
 
-| Características    | *Split* de cobros     | *Split* de transacción     |
+| Características    | Split de cobros     | Split de transacción     |
 | ---------- | ---------- | ---------- |
-| __Proveedor de pagos__       | Proveedor de pagos del *marketplace*.       | Proveedor de pagos del *seller*.       |
-| __Cantidad de transacciones__       | Solo una transacción.       | Una transacción por cada *seller*.       |
-| __Cantidad de compras en el estado de cuenta de la tarjeta de crédito del consumidor__       | Solo una.       | Una compra por cada *seller*. <li>*Esta manera de procesamiento puede ocasionar malentendidos y aumentar las disputas y contracargos*.</li>       |
-| __Negociación de cuotas__  | El *marketplace* es responsable de negociar todas las cuotas. <li>Al escalar, esto puede ser una ventaja pues se tiene mayor capacidad de negociación.</li>       | Cada parte escoge su proveedor de pagos y negocia sus cuotas.       |
+| __Proveedor de pagos__       | Proveedor de pagos del *marketplace*.       | Proveedor de pagos del seller.       |
+| __Cantidad de transacciones__       | Solo una transacción.       | Una transacción por cada seller.       |
+| __Cantidad de compras en el estado de cuenta de la tarjeta de crédito del consumidor__       | Solo una.       | Una compra por cada seller. <li>Esta manera de procesamiento puede ocasionar malentendidos y aumentar las disputas y contracargos.</li>       |
+| __Negociación de cuotas__  | El marketplace es responsable de negociar todas las cuotas. <li>Al escalar, esto puede ser una ventaja pues se tiene mayor capacidad de negociación.</li>       | Cada parte escoge su proveedor de pagos y negocia sus cuotas.       |
 | __Evaluación antifraude__      | Como solo se genera una transacción, el pedido entero lo analiza un solo antifraude.       | Como se generan varias transacciones, cada una ejecuta un análisis diferente. Si se deniega una transacción, todas las demás también se deniegan automáticamente.       |
-| __Proveedores de pagos integrados__       | Información disponible en la [Lista de Proveedores de Pago por País](https://help.vtex.com/es/tutorial/lista-de-proveedores-de-pago-por-pais--2im3BEGXxSAcRuxEaIHPvp) | Todos los proveedores de pago con integración en VTEX.       |
-| __Costo__       |Los costos dependen de la cuota negociada. <ul><li>Usualmente cuesta más que las transacciones que no se dividen.</li><li>Los carritos que contengan productos del *marketplace* solamente también se procesan según la cuota negociada, lo que podría aumentar el costo.</li></ul>       | No hay costos adicionales. Los clientes de VTEX solo serán responsables por las cuotas habituales de los proveedores de pago.       |
-| __Experiencia de checkout__       | No hay limitaciones con respecto a los medios de pago y las condiciones de pago. Serán definidos por el *marketplace*.  <ul><li>El proveedor de pagos debe admitir *split* para medios de pagos específicos (Pix, por ejemplo). Actualmente, nuestros partners admiten *split* con una o dos tarjetas de crédito, tarjetas de débito y boleto (Brasil).</li></ul>      | Solo muestra los métodos de pago aceptados por todos los vendedores que completan el pedido. Es decir, los pagos con tarjeta de crédito, efectivo o card promissory (pagaré que acepta el pago a plazos), solo estarán disponibles si todos los vendedores involucrados en el pedido los aceptan. Incompatible con:<ul><li>Boleto (Brasil).</li><li>Pix (Brasil).</li></ul><ul><li>Tarjetas con 3DS2 o cualquier autenticación.</li></ul> |
-| __Ideal para__       | <ul><li>Los *marketplaces* que desean cobrar comisiones automáticas y evitar el riesgo de morosidad.</li><li>Los *marketplaces* cuyos *sellers* no tengan un proveedor de pagos.</li></ul><ul><li>Los *marketplaces* que deseen tener más control del flujo de pago de los sellers.</li><li>  Los *marketplaces* que deseen procesar las transacciones con Pix (Brasil), boleto (Brasil) y tarjetas de crédito con 3DS2 u otra autenticación.</li></ul>       | <ul><li> Los *marketplaces* que no deseen ser comerciantes registrados (común para empresas B2B de Europa y Estados Unidos).</li><li> Casos en los que el *seller* tiene más poder de decisión que el marketplace y solo acepta que el pago se procese a través de su proveedor de pagos.</li></ul><ul><li> Los *marketplaces* que tienen urgencia de implementar split y no tengan partners que acepten *split* en su país.</li><li>Los *marketplaces* que no quieran asumir todos los riesgos de contracargos.</li></ul>       |
-| __Beneficios__ | <ul><li>Los *marketplaces* automáticamente definen las comisiones.</li><li>Experiencia optimizada: solo una compra en el estado de cuenta de la tarjeta de crédito.</li></ul><ul><li>El *marketplace* tiene más control sobre el flujo de pago.</li><li>Compatible con Pix (Brasil), boleto (Brasil) y tarjetas con 3DS2 o cualquier autenticación.</li></ul><ul><li>El *marketplace* puede definir medios de pago aplicables a cualquier pedido, independientemente de los *sellers* involucrados.</li></ul>       | <ul><li>Mayor flexibilidad para que cada *seller* escoja su proveedor antifraude.</li></ul><ul><li>La liquidación de pagos puede ocurrir en diferentes momentos para cada participante.</li><li>El *marketplace* no es responsable de los contracargos.</li></ul>|
+| __Proveedores de pagos integrados__       | Verifique qué proveedores de pago usan Split de cobros en la [Lista de Proveedores de Pago por País](https://help.vtex.com/es/tutorial/lista-de-proveedores-de-pago-por-pais--2im3BEGXxSAcRuxEaIHPvp) | Todos los proveedores de pago con integración en VTEX.       |
+| __Costo__       |Los costos dependen de la cuota negociada. <ul><li>Usualmente cuesta más que las transacciones que no se dividen.</li><li>Los carritos que contengan productos del marketplace solamente también se procesan según la cuota negociada, lo que podría aumentar el costo.</li></ul>       | No hay costos adicionales. Los clientes de VTEX solo serán responsables por las cuotas habituales de los proveedores de pago.       |
+| __Experiencia de checkout__       | No hay limitaciones con respecto a los medios de pago y las condiciones de pago. Serán definidos por el marketplace.  <ul><li>El proveedor de pagos debe admitir split para medios de pagos específicos (Pix, por ejemplo). Actualmente, nuestros partners admiten split con una o dos tarjetas de crédito, tarjetas de débito y boleto (Brasil).</li></ul>      | Solo muestra los métodos de pago aceptados por todos los vendedores que completan el pedido. Es decir, los pagos con tarjeta de crédito, efectivo o card promissory (pagaré que acepta el pago a plazos), solo estarán disponibles si todos los vendedores involucrados en el pedido los aceptan. Incompatible con:<ul><li>Boleto (Brasil).</li><li>Pix (Brasil).</li></ul><ul><li>Tarjetas con 3DS2 o cualquier autenticación.</li></ul> |
+| __Ideal para__       | <ul><li>Los marketplaces que desean cobrar comisiones automáticas y evitar el riesgo de morosidad.</li><li>Los marketplaces cuyos sellers no tengan un proveedor de pagos.</li></ul><ul><li>Los marketplaces que deseen tener más control del flujo de pago de los sellers.</li><li>  Los marketplaces que deseen procesar las transacciones con Pix (Brasil), boleto (Brasil) y tarjetas de crédito con 3DS2 u otra autenticación.</li></ul>       | <ul><li> Los marketplaces que no deseen ser comerciantes registrados (común para empresas B2B de Europa y Estados Unidos).</li><li> Casos en los que el seller tiene más poder de decisión que el marketplace y solo acepta que el pago se procese a través de su proveedor de pagos.</li></ul><ul><li> Los marketplaces que tienen urgencia de implementar split y no tengan partners que acepten split en su país.</li><li>Los *marketplaces* que no quieran asumir todos los riesgos de contracargos.</li></ul>       |
+| __Beneficios__ | <ul><li>Los marketplaces automáticamente definen las comisiones.</li><li>Experiencia optimizada: solo una compra en el estado de cuenta de la tarjeta de crédito.</li></ul><ul><li>El marketplace tiene más control sobre el flujo de pago.</li><li>Compatible con Pix (Brasil), boleto (Brasil) y tarjetas con 3DS2 o cualquier autenticación.</li></ul><ul><li>El marketplace puede definir medios de pago aplicables a cualquier pedido, independientemente de los sellers involucrados.</li></ul>       | <ul><li>Mayor flexibilidad para que cada seller escoja su proveedor antifraude.</li></ul><ul><li>La liquidación de pagos puede ocurrir en diferentes momentos para cada participante.</li><li>El marketplace no es responsable de los contracargos.</li></ul>|
 
 ## Split de cobros
 
-Este modelo de split de pagos permite a los clientes de *marketplace* tener más control y visibilidad sobre los cobros y comisiones. Además, le da más control sobre el flujo de pago, ya que VTEX retiene el pago del *seller* hasta que se factura el pedido.
+Este modelo de split de pagos permite a los clientes de marketplace tener más control y visibilidad sobre los cobros y comisiones. Además, le da más control sobre el flujo de pago, ya que VTEX retiene el pago del seller hasta que se factura el pedido.
 
-Los *marketplaces* pueden indicar cómo se debe dividir el importe de compra y qué porcentaje está reservado para el propio marketplace al definir comisiones automáticas por costo total de productos, flete o categoría de SKU para cada seller. En este caso, la transacción solo la procesa el proveedor de pagos del marketplace que será responsable de pagarle a cada seller.
+Los marketplaces pueden indicar cómo se debe dividir el importe de compra y qué porcentaje está reservado para el propio marketplace al definir comisiones automáticas por costo total de productos, flete o categoría de SKU para cada seller. En este caso, la transacción solo la procesa el proveedor de pagos del marketplace que será responsable de pagarle a cada seller.
 
 Por ejemplo, un comprador agrega dos productos al mismo carrito de compras. El marketplace entregará uno de ellos mientras que el otro pertenece a un seller llamado Seller A. Sin embargo, solo se genera una transacción, lo que significa que el consumidor solo verá una línea en el estado de cuenta de la tarjeta de crédito. 
 
 El pago se distribuye de la siguiente manera.
 
-![Split de cobros](https://images.ctfassets.net/alneenqid6w5/Vz2aNof4GnIVftr4EYDQy/a0545942f5605403edc0dba83a170963/Split_de_cobros.png)
-
-Como puede ver, nuestro *gateway* calcula y distribuye los cobros de cada parte cuando se factura el pedido y se envía la información al proveedor de pagos. La distribución se realiza según la cantidad destinada a cada comerciante en el pedido y la comisión del *marketplace*.
-
-![Afiliaciones](https://images.ctfassets.net/alneenqid6w5/4BE5K8TxKtGxDGgs1UwPHk/1b919ccf365965f061df91798e0ed869/Afiliaciones.png)
+![Split de cobros](//images.ctfassets.net/alneenqid6w5/Vz2aNof4GnIVftr4EYDQy/a0545942f5605403edc0dba83a170963/Split_de_cobros.png)
 
-En este modelo, nuestros clientes de *marketplace* también tienen acceso a un «Informe de comisiones» y mediante esta funcionalidad pueden consultar la lista de pedidos facturados por cada uno de sus *sellers* y las respectivas comisiones retenidas.
+Como puede ver, nuestro gateway calcula y distribuye los cobros de cada parte cuando se factura el pedido y se envía la información al proveedor de pagos. La distribución se realiza según la cantidad destinada a cada comerciante en el pedido y la comisión del marketplace.
 
-El «Informe de comisiones» proporciona transparencia a los importes que se le deben a cada *seller* y a las comisiones que los pedidos generaron al *marketplace*.
-
-<div class="alert alert-warning">
-Actualmente, nuestro informe de comisiones solo está disponible para ciertos clientes que son parte de nuestra prueba beta.
-</div>
+![Afiliaciones](//images.ctfassets.net/alneenqid6w5/4BE5K8TxKtGxDGgs1UwPHk/1b919ccf365965f061df91798e0ed869/Afiliaciones.png)
 
 Nuestra solución de split de cobros tiene algunas limitaciones que se deben tener en cuenta:
 
 - __Medios de pago combinados:__ no es compatible cuando uno de los dos no admite split. Ejemplo: tarjeta de regalo + tarjeta de crédito (la tarjeta de regalo no es compatible con split).  Actualmente, solo se puede utilizar el split de pagos cuando los medios combinados son dos tarjetas de crédito debido a una limitación de checkout.
-- __Cambios al pedido:__ no funciona cuando se cambian los valores o los ítems después de que se completa el pedido. Esto también significa que no se puede cancelar parcialmente un pedido que tiene split.
+- __Cambios al pedido:__ no funciona cuando se cambian los valores o los ítems después de que se completa el pedido. Los pedidos que contengan split se pueden reembolsar parcialmente, pero no cancelar.
 - __Suscripciones VTEX:__ no admite pedidos de marketplace.
 - __ID de seller:__ el nro. de registro de persona jurídica es la clave principal para realizar el split, por lo que las dos partes (marketplaces y sellers) deben ser entidades jurídicas.
 - __Mismo nro. de registro de persona jurídica:__ ya que el nro. de registro de persona jurídica es la clave principal para realizar el split, no es posible reconocer a dos o más beneficiarios/participantes de la venta que tengan el mismo número de registro como «entidades» distintas. 
@@ -75,35 +72,37 @@ Nuestra solución de split de cobros tiene algunas limitaciones que se deben ten
 - __Partes involucradas:__ no se permite dividir el pago con beneficiarios que no vendan alguno de los productos que estén en el carrito. Por ejemplo: dividir el flete directamente con la transportadora.
 - __Cuotas nominales:__ no permite cuotas nominales. Actualmente, solo es posible aplicar comisiones porcentuales en productos y/o fletes.
 - __Asignar transacciones al proveedor:__ actualmente, solo es posible asignar una afiliación preferida en el gateway para procesar el split utilizando condiciones comerciales para los SKU que el seller vende. Sin embargo, hay algunas limitaciones:
-        - Si el seller y el marketplace tienen el mismo SKU, el carrito siempre se procesará con el método de split de pagos.
-        - La lista de SKU debe actualizarse constantemente.
+    - Si el seller y el marketplace tienen el mismo SKU, el carrito siempre se procesará con el método de split de pagos.
+    - La lista de SKU debe actualizarse constantemente.
+
+- __Interés de la transacción:__ no es posible seleccionar quién recibirá la información de intereses (marketplace o seller). Todas las transacciones en las que el cliente realizó pagos de intereses se envían automáticamente al marketplace.
 
 ## Split de transacción
 
-En el *split* de transacción, el *marketplace* no centraliza los cobros. Justo después de que el comprador completa la compra, nuestro sistema de *checkout* crea la transacción o transacciones (una por *seller*). 
+En el split de transacción, el marketplace no centraliza los cobros. Justo después de que el comprador completa la compra, nuestro sistema de checkout crea la transacción o transacciones (una por seller). 
 
-El pago no siempre lo procesa el proveedor de pagos del *marketplace*, sino que lo procesan los proveedores de cada comerciante (el proveedor de pagos de cada *seller* es responsable de procesar su porción de la transacción).
+El pago no siempre lo procesa el proveedor de pagos del marketplace, sino que lo procesan los proveedores de cada comerciante (el proveedor de pagos de cada *seller* es responsable de procesar su porción de la transacción).
 
-Lo que significa que el *marketplace* tiene menos control sobre el flujo de pago. A diferencia del otro modelo, VTEX no mantiene el pago hasta que se factura el pedido, cada porción se envía automáticamente al participante respectivo justo después del *checkout*.
+Lo que significa que el marketplace tiene menos control sobre el flujo de pago. A diferencia del otro modelo, VTEX no mantiene el pago hasta que se factura el pedido, cada porción se envía automáticamente al participante respectivo justo después del checkout.
 
-Por ejemplo, un comprador agrega dos productos al mismo carrito de compras. El marketplace entregará uno de ellos y el otro le pertenece al *seller* llamado Seller A.
+Por ejemplo, un comprador agrega dos productos al mismo carrito de compras. El marketplace entregará uno de ellos y el otro le pertenece al seller llamado Seller A.
 
-![Transacción](https://images.ctfassets.net/alneenqid6w5/2uC4hZkbbq4w5WuxZS5LaP/33d5406e2d18da8290edaa3621edc7c6/Transacci__n.png)
+![Transacción](//images.ctfassets.net/alneenqid6w5/2uC4hZkbbq4w5WuxZS5LaP/33d5406e2d18da8290edaa3621edc7c6/Transacci__n.png)
 
-En el *split* de transacción, el *marketplace* no tiene que realizar ninguna configuración. El *seller* es el que tiene que configurar su medio de pago en la afiliación con un determinado *marketplace*. Para más detalles, consulte nuestra documentación [Enviar los medios de pago del Seller White Label al Marketplace](https://help.vtex.com/es/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW).
+En el split de transacción, el marketplace no tiene que realizar ninguna configuración. El seller es el que tiene que configurar su medio de pago en la afiliación con un determinado marketplace. Para más detalles, consulte nuestra documentación [Enviar los medios de pago del Seller White Label al Marketplace](https://help.vtex.com/es/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW).
 
-![Afiliación1](https://images.ctfassets.net/alneenqid6w5/4e8047JCOgEoswkj280gI5/421b393c522456e882ceaed27f73cb8c/Afiliados2.png)
+![Afiliación1](//images.ctfassets.net/alneenqid6w5/4e8047JCOgEoswkj280gI5/421b393c522456e882ceaed27f73cb8c/Afiliados2.png)
 
 El split de transacción tiene algunas limitaciones que deben tomarse en cuenta.
 
-- __Establecer comisiones:__ en este modelo, los *marketplaces* no pueden recibir comisiones automáticamente porque la transacción no la procesa su proveedor de pagos. Los *marketplaces* tienen que manualmente cobrar sus comisiones a los *sellers*, lo que podría aumentar el riesgo de incumplimiento para el *marketplace*.
+- __Establecer comisiones:__ en este modelo, los marketplaces no pueden recibir comisiones automáticamente porque la transacción no la procesa su proveedor de pagos. Los marketplaces tienen que manualmente cobrar sus comisiones a los sellers, lo que podría aumentar el riesgo de incumplimiento para el marketplace.
 - __Medios de pago:__ no es compatible con boleto (Brasil), Pix (Brasil), Payment Apps y tarjetas de crédito con 3DS2 o cualquier medio de pago que tenga autenticación.
 - __Filtrar los medios de pago:__ filtra los medios de pago, es decir, solo muestra pagos con tarjeta de crédito, efectivo y pagaré si todos los comerciantes los aceptan.
 - __Mitigación de fraude:__ cada comerciante tiene que analizar el riesgo de fraude independientemente. Si uno de los proveedores de protección de fraude de los comerciantes deniega una transacción, todas las demás transacciones también serán rechazadas.
-- __Sellers externos a VTEX:__ si el *seller* es externo a VTEX, tiene que utilizar una cuenta de *gateway*, un tipo de cuenta que le permite al *seller* configurar medios de pago. 
-- __Suscripciones VTEX:__ No permite pedidos del *marketplace*.
+- __Sellers externos a VTEX:__ si el seller es externo a VTEX, tiene que utilizar una cuenta de gateway, un tipo de cuenta que le permite al seller configurar medios de pago. 
+- __Suscripciones VTEX:__ No permite pedidos del marketplace.
 - __Partes involucradas:__ no se permite dividir el pago con beneficiarios que no vendan alguno de los productos que estén en el carrito. Por ejemplo: dividir el flete directamente con la transportadora.
-- __Combinar modelos de *split*:__ cuando se combina con el otro modelo (*split* de cobros), el *split* de transacción tomará prioridad. Es decir, para los *sellers* que decidan utilizar su medio de pago, su porción de la transacción se procesará en su propio *gateway* mientras que los valores de los demás participantes de la venta los procesará el *marketplace*.
+- __Combinar modelos de split:__ cuando se combina con el otro modelo (split de cobros), el split de transacción tomará prioridad. Es decir, para los sellers que decidan utilizar su medio de pago, su porción de la transacción se procesará en su propio gateway mientras que los valores de los demás participantes de la venta los procesará el marketplace.
 
 ## Combinar modelos de split
 
@@ -111,7 +110,5 @@ Cuando el modelo de split de transacción se combina con el modelo de split de c
 
 ### Más información
 
-- [Configurar split de cobros - PagarMeV2](https://help.vtex.com/es/tutorial/setting-up-pagarmev2-gateway--5TugxXNMOs0Ocyg4uqussM?&utm_source=autocomplete)
-- [Configurar split de cobros - VTEX Payment](https://help.vtex.com/es/tracks/vtex-payment--7iCCIoIZFmd9OabU6QlmXu/1lZWKCGdy7xpYjukTLfFJL)
 - [Enviar los medios de pago del Seller White Label al Marketplace](https://help.vtex.com/es/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW) (para más información sobre cómo configurar el split de transacción).
 
diff --git a/docs/tutorials/es/store-access-permission.md b/docs/tutorials/es/store-access-permission.md
index 72b1ae852..24e42dbdb 100644
--- a/docs/tutorials/es/store-access-permission.md
+++ b/docs/tutorials/es/store-access-permission.md
@@ -25,4 +25,4 @@ Para realizar esta configuración, en el panel administrativo (Admin) de la cuen
 4. Seleccione la opción __VTEX Store__.
 5. Marque la casilla de selección __“Enables B2B behaviour”__ y guarde las alteraciones.
 
-![Habilitar escenario B2B](https://images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
+![Habilitar escenario B2B](//images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
diff --git a/docs/tutorials/es/store-overview-beta.md b/docs/tutorials/es/store-overview-beta.md
new file mode 100644
index 000000000..6c728cfa2
--- /dev/null
+++ b/docs/tutorials/es/store-overview-beta.md
@@ -0,0 +1,161 @@
+---
+title: 'Vista General de la Tienda (Beta)'
+id: 7i8wNsQQgbbFhYMYbQ5X46
+status: PUBLISHED
+createdAt: 2023-06-14T17:43:51.256Z
+updatedAt: 2023-11-09T19:56:54.060Z
+publishedAt: 2023-11-09T19:56:54.060Z
+firstPublishedAt: 2023-06-15T14:16:58.510Z
+contentType: tutorial
+productTeam: Management
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: vista-general-de-la-tienda-beta
+locale: es
+legacySlug: vista-general-de-la-tienda-beta
+subcategory: QPnz120TdtLcXSh65c4Gs
+---
+
+<div class="alert alert-info"> 
+La versión actualizada de la página Vista general de la tienda (Beta) está disponible para uso gratuito en el Admin VTEX durante su periodo beta, o hasta que VTEX lo decida. Es importante tener en cuenta que en el futuro podrían aplicarse tarifas adicionales. Además, la página de Vista general, actualmente presente en el VTEX Admin, seguirá estando disponible para su uso por el momento.
+</div>
+
+La página Vista general (Beta) de tu Admin VTEX proporciona un seguimiento en tiempo real de tu operación en el día actual, ofreciendo visibilidad en las métricas para que tu equipo y tú tengan un rápido feedback sobre las acciones realizadas en la tienda y puedan actuar con prontitud para implementar mejoras. 
+
+Esta herramienta está disponible en el Admin VTEX, en la página de inicio. Para acceder, haz clic en **Dashboards > Vista general** en el menú de navegación, o escribe _Vista general_ en la barra de búsqueda de la parte superior de la página.
+
+![ES Visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/5b97a2cf1346f1c95fc32512c95da972/ES_Visa__o_geral_beta.png)
+
+En este artículo, presentamos las principales secciones y acciones presentes en la página. Aquí verás más información sobre:
+
+* [Datos disponibles en la página](#datos-disponibles-en-la-pagina)
+* [Analizar los resultados y el estado de la operación](#analizar-los-resultados-y-el-estado-de-la-operacion)
+* [Comparar periodos](#comparar-periodos)
+* [Vista](#vista)
+* [Monitoreo](#monitoreo)
+* [Métricas](#metricas)  
+
+## Datos disponibles en la página
+
+Las métricas de la página incluyen datos sobre los pedidos y la navegación, que se obtienen de distintos sistemas.
+
+<div class ="alert alert-warning">
+Por ejemplo, puede que haya diferencias entre las métricas de ingresos y ticket promedio registradas en el OMS y Desempeño de Ventas. Esto se debe a que Desempeño de Ventas considera el valor de los ítems, mientras que el OMS también toma en cuenta descuentos, valor de envío, impuestos y promociones en el pedido, lo que puede aumentar o disminuir el valor final.
+</div>
+
+* **Pedidos e ingresos:** los datos sobre pedidos e ingresos proceden del OMS, el Sistema de Gestión de Pedidos de VTEX, e incluyen los pedidos realizados a través de todos tus canales de venta.
+* **Sesiones:** los datos de navegación proceden del sistema interno de la plataforma que captura las sesiones de los usuarios en el storefront de las tiendas VTEX. Las sesiones están representadas por el conjunto de páginas vistas a las que accede un mismo usuario cuando navega por tu tienda online, sin tener en cuenta marketplaces, aplicaciones, VTEX Sales App y cualquier otro canal de venta.
+
+### Restricciones de datos
+
+No recopilamos datos de navegación de storefronts que no son de VTEX ni de sellers que únicamente anuncian productos en marketplaces externos. Por este motivo, los tipos de gráficos presentes en el [Monitoreo](#monitoreo) pueden no estar disponibles, dependiendo de si recopilamos los datos de navegación de tu tienda, o no.
+
+Aunque nuestro objetivo es presentar como máximo un 3 % de divergencia en los datos del OMS de VTEX, a veces puedes encontrar discrepancias entre los datos que aparecen en Vista general y el OMS. 
+
+### Actualización de datos
+
+Los datos provenientes de páginas diferentes presentan frecuencias de actualización distintas. Los gráficos de la sección [Monitoreo](#monitoreo) se actualizan en hasta tres minutos, según la [Vista](#vista), mientras que las demás secciones de la página se actualizan cada 15 minutos. La etiqueta <i class='fas fa-circle-notch blue-color'></i> 1 min muestra la última vez que se actualizaron los datos de la página. 
+
+## Analizar los resultados y el estado de la operación
+
+Puedes utilizar diferentes  [métricas](#metricas) y gráficos de [monitoreo](#monitoreo) para analizar resultados, en función del aspecto que desees explorar. La siguiente tabla puede orientar tu análisis. Haz clic en cada una de las métricas de la tabla para obtener más información sobre su cálculo y funcionamiento. 
+
+| Objetivo                | Métricas y gráficos a analizar                                                                                                                                                                                                                                                                |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Engagement de la acción | - [Nuevas sesiones](#monitoreo)<br>- [Productos más vendidos](#metricas)                                                                                                                                                                                                                                                 |
+| Resultados financieros  | - [Ingresos capturados](#monitoreo) <br>- [Ticket promedio](#metricas) <br>- [Productos con mayores ingresos](#metricas)                                                                                                                                                                                                               |
+| Conversión              | - [Tasa de conversión](#metricas) <br>- [Embudo de ventas](#embudo-de-ventas) <br>- [Pedidos capturados](#monitoreo), comparado con el número de Pedidos cancelados. Los resultados obtenidos pueden guiar a tu equipo a identificar aquellos problemas operativos en el fulfillment o atención al cliente que causaron los pedidos cancelados. |
+
+<div class="alert alert-info"> 
+Importante: mientras que los gráficos de Monitoreo se actualizan en hasta tres minutos, las Métricas se actualizan cada quince minutos, lo que puede influir en tu análisis de resultados. Más información en <a href="#atualizacion-de-datos">Actualización de datos</a>.
+</div>
+
+### Analizar resultados de campañas
+
+Si deseas analizar los resultados de campañas, promociones o lanzamientos de nuevos productos que tuvieron lugar en una fecha pasada, sigue las instrucciones que se indican a continuación: 
+
+1. Selecciona la **Tienda** donde se produjo la acción.
+2. Selecciona la fecha de la campaña para [comparar el periodo](#comparar-el-periodo) con la fecha de hoy.
+3. Selecciona la [vista](#vista) `Acumulado`.
+4. Haz un seguimiento de las métricas hora a hora.
+
+![ES Visão geral beta acumulado](//images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/610b38ec888e48078998c5f51a9ade4e/ES_Visa__o_geral_beta_acumulado.png)
+
+### Monitorear impactos de cambios en la tienda
+
+Para mantener la estabilidad de tu operación es importante identificar si las implementaciones realizadas (deploys), campañas o cambios en la configuración impactaron negativamente sobre el número de pedidos, sesiones o conversión de clientes en los momentos inmediatamente posteriores a su aplicación.
+
+Si deseas ver el impacto de los cambios realizados en tu tienda, para identificar un posible impacto negativo o cambios en la salud del negocio, sigue las instrucciones a continuación. 
+
+1. Selecciona la **Tienda** donde se produjo la acción.
+2. Selecciona la [visualización](#visualizacion) `Últimas horas`.
+3. Evalúa el pulso en las métricas, o puntos de inflexión en el gráfico, que se han producido en las dos últimas horas. 
+4. Compara los horarios de los puntos de inflexión con los cambios generados para identificar su causa e impacto. 
+
+![ES Visão geral beta ultimas duas horas](//images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/e0cd80f9405e7736ee1c53ada5c8f97c/ES_Visa__o_geral_beta_ultimas_duas_horas.png)
+
+## Comparar periodos
+
+Puedes filtrar datos en función del periodo seleccionado y comparar métricas de la tienda con fechas pasadas. Para comparar datos entre distintos periodos, en la parte superior de la página, selecciona la fecha junto a `Comparar hoy con:`, y luego elige una de las siguientes opciones:
+
+| Periodo       | Inicio                                                                                         | Fin                                  |
+|---------------|------------------------------------------------------------------------------------------------|--------------------------------------|
+| Ayer          | 00:00 del día anterior                                                                         | 23:59 del día anterior               |
+| Hace 7 días   | 00:00 de los ocho días anteriores a hoy                                                        | 23:59 del día anterior al día de hoy |
+| Hace 28 días  | 00:00 del 29º día antes del día actual                                                         | 23:59 del día anterior al día de hoy |
+| Personalizado | Marca en el calendario la Fecha de comparación deseada, con un límite de 13 meses en el pasado | 23:59 del día anterior al día de hoy |
+
+## Vista
+
+Al hacer clic en el botón `Vista:` dentro de la sección [Monitoreo](#monitoreo), es posible alternar entre las siguientes opciones:
+
+* **Acumulado:** valor total acumulado en el día para cada métrica de monitoreo, desde las 00:00 hasta la última actualización. Los datos de esta vista se actualizan cada tres minutos. 
+* **Últimas horas:** valor recibido durante las últimas dos horas para cada métrica de monitoreo. Esta vista no muestra la comparación con otros periodos ni el porcentaje de crecimiento o disminución de la métrica. Los datos de esta vista se actualizan cada minuto. 
+
+También puedes filtrar por tienda si lo seleccionas en el menú desplegable.  
+
+## Monitoreo
+
+Cada gráfico contiene los siguientes elementos:
+
+* El eje X muestra el horario, mientras que el eje Y muestra el valor de la métrica de monitoreo.
+* Número absoluto de cada métrica, que puede ser `Acumulado` o `Últimas horas`. Más información en [Vista](#vista). 
+* La línea azul más gruesa indica la evolución de los valores en el día de hoy. 
+* La línea gris de puntos indica la tasa correspondiente al periodo comparado. 
+* Al pasar el cursor por encima, el gráfico muestra el valor absoluto de cada periodo comparado.
+
+La siguiente tabla describe los gráficos incluidos en la sección _Monitoreo_ de la página. 
+
+| Métrica             | Descripción                                                                                                                                                                                          |
+|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Ingresos capturados | Valor total determinado por el valor final de los pedidos capturados, indicando la cantidad que la tienda ha recibido en ingresos y comparando el día de hoy con un periodo específico seleccionado. |
+| Pedidos capturados  | Número de pedidos que tu tienda recibió en el día de hoy respecto al periodo seleccionado.                                                                                                           |
+| Ticket promedio     | Promedio de los ingresos por pedido capturado hoy en comparación con el periodo seleccionado.                                                                                                        |
+| Nuevas sesiones     | Número de nuevas visitas o interacciones en tu tienda, en función del tipo de [Vista](#vista) seleccionada. Esta métrica solo está disponible para tiendas que [recopilan datos de navegación](#restricciones-de-datos).                  |
+
+## Métricas
+
+![ES Visão geral beta metricas](//images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/91ced2dd646ee9cdc9c1869f523ad1fd/ES_Visa__o_geral_beta_metricas.png)
+
+La siguiente tabla describe las métricas disponibles en el panel de la página de inicio. Todas las métricas se refieren a flujos de compra realizados en tiendas VTEX en el periodo seleccionado.
+
+| Métrica                         | Descripción                                                                                                                                                                                                                                                                                                                                                          |
+|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Ticket promedio                 | Promedio del valor pagado en los pedidos capturados durante el periodo seleccionado. Esta métrica muestra, a través del ícono hacia arriba <i class='fa fa-caret-up'></i> y el ícono hacia abajo <i class='fa fa-caret-down'></i>, el porcentaje de aumento o disminución del ticket promedio.                                                                       |
+| Tasa de conversión              | Se calcula dividiendo el número total de pedidos por el número total de sesiones en tu tienda. Al hacer clic en el ícono de la flecha <i class='fa fa-chevron-down'></i>, se expande el Embudo de ventas.                                                                                                                                                            |
+| Productos con mayores ingresos  | Productos que generaron más ingresos en el periodo seleccionado. Indica el valor recibido en ingresos y un porcentaje que indica un aumento o disminución de los ingresos, comparando los periodos seleccionados. Al hacer clic en el ícono de la flecha <i class='fa fa-chevron-down'></i>, alternas esta métrica con la de Productos más vendidos.                 |
+| Productos más vendidos          | Productos que vendieron más unidades en el periodo seleccionado. Refiere la cantidad de ítems vendidos y un porcentaje que indica un aumento o disminución de los ítems vendidos, comparando los periodos seleccionados. Al hacer clic en el ícono de la flecha <i class='fa fa-chevron-down'></i>, alternas esta métrica con la de Productos con mayores ingresos.  |
+
+### Embudo de ventas
+
+En la métrica _Tasa de conversión_, al hacer clic en el ícono de la flecha <i class='fa fa-chevron-down'></i>,, se expande el **Embudo de ventas**. Este gráfico muestra un seguimiento del volumen de sesiones en etapas intermedias del flujo de compra e identifica oportunidades para optimizar la tasa de conversión de la tienda. La siguiente tabla describe las etapas intermedias del flujo de compra.
+
+| Etapa    | Descripción                                                        |
+|----------|--------------------------------------------------------------------|
+| Sesiones | Número total de visitas a tu tienda                                |
+| Producto | El usuario ha accedido a una página de producto durante la sesión  |
+| Carrito  | El usuario ha añadido un producto al carrito durante la sesión     |
+| Envío    | El usuario rellenó la información sobre el envío durante la sesión |
+| Pago     | Los datos de pago se rellenaron durante la sesión                  |
+| Pedidos  | Pedidos que se realizaron durante la sesión                        |
+
+Cada barra azul del gráfico representa el volumen de sesiones que han alcanzado una determinada etapa del flujo de compra. Este volumen se representa como un valor absoluto y como un porcentaje del número de sesiones, junto con los puntos porcentuales de aumento o disminución en el embudo de ventas. 
diff --git a/docs/tutorials/es/store-overview.md b/docs/tutorials/es/store-overview.md
index 08c61069e..0f774b767 100644
--- a/docs/tutorials/es/store-overview.md
+++ b/docs/tutorials/es/store-overview.md
@@ -17,7 +17,7 @@ subcategory: 1TIJqw8kV2Yok4iQe4SAkq
 
 En la página de Vista general del Admin VTEX los propietarios de las tiendas pueden obtener una rápida visión general de las métricas clave que afectan a sus ingresos. A través de este panel, puedes seguir la evolución de tus ventas mediante el análisis de tendencia de pedidos, la tasa de conversión y los gráficos de embudo de ventas. Puedes acceder a esta herramienta en el Admin VTEX, haciendo clic en **Dashboards > Vista general** en el menú de navegación, o escribe *Vista general* en la barra de búsqueda en la parte superior de la página.
 
-![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 La página Vista General proporciona un resumen de su negocio con VTEX. Para un análisis más profundo de las métricas de su tienda, visite [Desenpeño de ventas](https://help.vtex.com/es/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp).
 
@@ -54,7 +54,7 @@ Para comparar datos de diferentes periodos, en la parte superior de la página s
 | Últimos 28 días | 00:00 del 29º día anterior al día actual    | 23:59 del día anterior al día actual                                                                                         |
 
 ## Métricas
-![Store overview Métricas ES](https://images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/fa0a742830add36b15347a667b46a740/Me__tricas_ES.png)
+![Store overview Métricas ES](//images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/fa0a742830add36b15347a667b46a740/Me__tricas_ES.png)
 La siguiente tabla describe las métricas clave disponibles en el panel de la página de inicio. Todas las métricas se refieren a los flujos de compra realizados en tiendas VTEX en un periodo de tiempo determinado.
 
 | Métrica                          | Descripción                                                                                                                                                                                                                                                                             |
@@ -69,7 +69,7 @@ La siguiente tabla describe las métricas clave disponibles en el panel de la p
 
 ## Productos con mayores ingresos / Productos con más unidades vendidas
 
-![Store overview Growing products ES](https://images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/71288c48523af26b98d46501a1822105/Store_overview_Growing_products_ES.jpg)
+![Store overview Growing products ES](//images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/71288c48523af26b98d46501a1822105/Store_overview_Growing_products_ES.jpg)
 
 Este componente muestra tus productos más rentables y los productos con mayor número de unidades vendidas en el periodo seleccionado. 
 
@@ -79,18 +79,18 @@ Puedes alternar entre estas dos opciones haciendo clic en el título o en el íc
 - **Productos con más unidades vendidas:** los productos con más unidades vendidas en el periodo seleccionado. Indica la cantidad de ítems vendidos y un porcentaje que muestra el aumento o la disminución de los ítems vendidos, comparando los periodos seleccionados.
 
 ## Pedidos realizados
-![Store overview Pedidos realizados EN](https://images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/fab0eca29780027e7eef5a53ccdc803b/Pedidos_realizados_EN.png)
+![Store overview Pedidos realizados EN](//images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/fab0eca29780027e7eef5a53ccdc803b/Pedidos_realizados_EN.png)
 
 Este gráfico muestra el número de pedidos que recibió la tienda en el periodo seleccionado. La línea azul más gruesa indica los pedidos que se realizaron en el periodo más reciente. La línea gris más delgada indica los pedidos que se realizaron en el periodo que estás comparando. Al pasar el *mouse* sobre las líneas, el gráfico muestra el número de pedidos captados en cada fecha.
 
 ## Pedidos cancelados
-![Store overview Pedidos cancelados PT](https://images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/5a3f4d78000475bae4d2a62ec1c7c4bd/Pedidos_cancelados_PT.png)
+![Store overview Pedidos cancelados PT](//images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/5a3f4d78000475bae4d2a62ec1c7c4bd/Pedidos_cancelados_PT.png)
 
 Este gráfico muestra el número de pedidos cancelados en la tienda en el periodo seleccionado. La línea azul más gruesa indica los pedidos cancelados en el periodo más reciente. La línea gris más delgada indica los pedidos cancelados en el periodo que estás comparando. Al pasar el *mouse* sobre las líneas, el gráfico muestra el número de pedidos cancelados en cada fecha.
 
 ## Análisis de tendencia de pedidos
 
-![Store overview Order trend ES](https://images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/0eafd1eeb6423749827c8cfec524858a/Store_overview_Order_trend_ES.jpg)
+![Store overview Order trend ES](//images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/0eafd1eeb6423749827c8cfec524858a/Store_overview_Order_trend_ES.jpg)
 
 Este gráfico muestra la tendencia de pedidos de tu tienda, indicando el número de pedidos realizados por los compradores en el periodo seleccionado.
 
@@ -100,13 +100,13 @@ El número que aparece en la parte superior del gráfico se refiere a los pedido
 
 ## Tasa de conversión
 
-![Store overview Conversion rate ES](https://images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/92756d2a2a7f4165f4312f2c81bc08e6/Store_overview_Conversion_rate_ES.jpg)
+![Store overview Conversion rate ES](//images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/92756d2a2a7f4165f4312f2c81bc08e6/Store_overview_Conversion_rate_ES.jpg)
 
 Este gráfico muestra la tasa de conversión de tu tienda en los períodos seleccionados que quieres comparar. La tasa de conversión se calcula dividiendo el número total de pedidos por el número total de sesiones en tu tienda. La línea azul más gruesa indica la tasa de conversión para el periodo más reciente. La línea gris más delgada indica la tasa para el periodo que estás comparando. Al pasar el mouse por encima del gráfico, se visualiza la tasa de conversión para cada periodo comparado. El gráfico también indica el porcentaje (%) y los puntos porcentuales (p.p) de aumento o reducción de esta métrica. Al pasar el mouse por encima del gráfico, puedes ver el valor de esa métrica en momentos específicos. 
 
 ## Embudo de ventas
 
-![Store overview sales funnel ES](https://images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/d767479ae6fd2f51af5327b80527d883/Store_overview_sales_funnel_ES.jpg)
+![Store overview sales funnel ES](//images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/d767479ae6fd2f51af5327b80527d883/Store_overview_sales_funnel_ES.jpg)
 
 Este gráfico permite seguir el volumen de sesiones en las etapas intermedias del flujo de compra y ver oportunidades para optimizar la tasa de conversión de la tienda. La siguiente tabla describe las etapas intermedias del flujo de compra.
 
@@ -122,7 +122,7 @@ Este gráfico permite seguir el volumen de sesiones en las etapas intermedias de
 Cada barra azul del gráfico representa el volumen de sesiones que han alcanzado una determinada etapa del flujo de compra. Este volumen se representa como valor absoluto (arriba), y como porcentaje del número de sesiones (abajo), junto con los puntos porcentuales (p.p) de aumento o reducción en el embudo de ventas. Al pasar el mouse por encima del porcentaje, puedes ver más detalles sobre esa etapa intermedia.
 
 ## Categorías con mayores ingresos
-![Categorias PT](https://images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/7cf1e540189c28ec0d3286179d0d2774/Categorias_PT.png)
+![Categorias PT](//images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/7cf1e540189c28ec0d3286179d0d2774/Categorias_PT.png)
 
 Este gráfico muestra las diez categorías de tu tienda que más ingresos generaron en el periodo seleccionado. La barra azul indica los ingresos generados en la fecha más reciente y la barra gris indica los ingresos generados en el periodo comparado. Al pasar el mouse sobre el gráfico, se visualiza la tasa de conversión para cada periodo comparado. Al hacer clic en el título del gráfico, es posible cambiar la vista a las __Categorías más vendidas por pedido__.
 
diff --git a/docs/tutorials/es/store-profile.md b/docs/tutorials/es/store-profile.md
new file mode 100644
index 000000000..04cdee9f8
--- /dev/null
+++ b/docs/tutorials/es/store-profile.md
@@ -0,0 +1,88 @@
+---
+title: 'Perfil de la tienda'
+id: 72qjh4BIc9ppKsbEpdBKoo
+status: PUBLISHED
+createdAt: 2023-07-19T21:17:55.736Z
+updatedAt: 2023-07-19T21:29:37.370Z
+publishedAt: 2023-07-19T21:29:37.370Z
+firstPublishedAt: 2023-07-19T21:29:37.370Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: perfil-de-la-tienda
+locale: es
+legacySlug: perfil-de-la-tienda
+subcategory: 6riYYNZCpO8wyksi8Ksgyq
+---
+
+VTEX proporciona en el Admin las páginas **[Encontrar sellers](https://help.vtex.com/tutorial/encontrar-sellers--6kkZaxIgfDyvN5trgIuwBl)** y **[Marketplaces e integraciones](https://help.vtex.com/es/tutorial/marketplaces-and-integrations--5AcBO1t29nhq7rBHas9b6V).** Dichas páginas tienen como objetivo poner a disposición y facilitar el encuentro y la comunicación entre sellers y marketplaces que operan en el ecosistema VTEX, abriendo la posibilidad de nuevos negocios y crecimiento mutuo para todos los participantes.  
+
+Para ponerte en contacto con partners potenciales presentes en esa lista, debes activar el perfil de tu tienda como marketplace, seller, o ambos. Esto se lleva a cabo en la página Perfil de la tienda, accediendo a **Marketplace > Perfil de la tienda** o ingresando **Perfil de la tienda** en la barra de búsqueda.  
+
+## <a name="informacion-de-la-tienda"></a>Información de la tienda  
+
+Los datos introducidos en la sección Información de la tienda no se aplicarán en tu storefront, sino en las páginas *Encontrar sellers* y *Marketplaces e integraciones.*  
+
+- **Logotipo**: imagen del logotipo de tu tienda, tamaño máximo 500 kB.  
+- **Nombre de la tienda:** nombre comercial de tu tienda.  
+- **Segmento de negocio:** el mercado en el que actúa la tienda, seleccionado
+entre las opciones de la lista.  
+- **País**: país donde se encuentra la sede social, o la operación principal de la tienda.  
+- **Link del ecommerce:** URL del sitio web oficial de la marca.  
+- **Selecciona los estados donde tu tienda realiza entregas:** casillas de verificación para cada estado.  
+
+## Activar Perfil de seller  
+
+Si deseas actuar únicamente como seller y hacer que tus productos estén disponibles en otros marketplaces, activa tu perfil de seller siguiendo los pasos y recomendaciones que se indican a continuación:  
+
+1. En la sección Marketplace de tu Admin VTEX, haz clic en **Perfil de la tienda** o ingresa **Perfil de la tienda** en la barra de búsqueda.  
+2. Rellena el formulario con la **[información de la tienda](#informacion-de-la-tienda)**.  
+3. Ingresa los datos solicitados en la sección **[Perfil de seller](#rellenar-perfil-de-seller)**.  
+4. Haz clic en **Términos y condiciones de uso de Marketplace Network**.  
+5. Desliza hacia abajo para leer el texto completo.  
+6. En la esquina superior derecha, haz clic en `Guardar cambios`.  
+
+### <a name="rellenar-perfil-de-seller"></a>Rellenar Perfil de seller  
+
+Para iniciar el proceso de completar los datos solicitados en el Perfil de seller, debes hacer clic en el ícono <i class="fas fa-toggle-on"></i>. Cuando hayas terminado, haz clic en `Guardar cambios` y tu tienda se mostrará visible u oculta para los marketplaces en la página **Encontrar sellers.**  
+
+Consulta a continuación los campos y las directrices para rellenar la sección con los datos requeridos:  
+
+- **Descripción del perfil público**: texto de hasta 1200 caracteres que aparecerá en tu perfil donde debes describir tu tienda y su operación. Te sugerimos que incluyas detalles tales como SLA de entrega, cobertura logística, o cuáles son las principales categorías de tus productos.  
+- **Nombre del contacto:** nombre de la persona encargada de contactar a los partners potenciales. Sugerimos que sea la persona de tu equipo que ya tiene atribuida la tarea de atraer posibles socios comerciales.  
+- **Email**: dirección de email de la persona responsable de contactar a los partners potenciales. Asegúrate de que la dirección de email es válida, ya que es ahí donde llegarán los mensajes enviados a tu tienda.  
+- **Teléfono**: teléfono de la persona responsable de contactar con los partners potenciales.  
+- **Utiliza un mensaje estándar:** mensaje predeterminado creado por la tienda para las comunicaciones que los marketplaces verán en el campo `Enviar un mensaje` al hacer clic en tu perfil. Incluso activando esta opción, es posible editar el mensaje antes de enviárselo al partner potencial.  
+
+## Activar Perfil de marketplace  
+
+Si deseas actuar únicamente como marketplace y vender productos de otros sellers en tu entorno de ventas, debes activar tu perfil de marketplace siguiendo los pasos que se indican a continuación:  
+
+1. En la sección Marketplace de tu Admin VTEX, haz clic en **Perfil de la tienda** o escribe **Perfil de la tienda** en la barra de búsqueda.  
+2. Rellena el formulario con la **[información de la tienda](#informacion-de-la-tienda)**.  
+3. Ingresa los datos solicitados en la sección **[Perfil de marketplace](#rellenar-perfil-de-marketplace)**.  
+4. Haz clic en **Términos y condiciones de uso de Marketplace Network**.  
+5. Desliza hacia abajo para leer el texto completo.  
+6. En la esquina superior derecha, haz clic en `Guardar cambios`.  
+
+### <a name="rellenar-perfil-de-marketplace"></a>Rellenar Perfil de marketplace  
+
+Para completar los datos solicitados en el Perfil de marketplace, debes hacer clic en el ícono <i class="fas fa-toggle-on"></i>. Cuando hayas terminado, haz clic en `Guardar cambios` y tu tienda se mostrará visible u oculta para los sellers en la página **Marketplace e integraciones.**  
+
+Consulta a continuación los campos y las directrices para rellenar la sección con los datos requeridos:  
+
+- **Descripción del perfil público**: texto de hasta 1200 caracteres que aparecerá en tu perfil donde debes describir tu tienda y su operación. Te sugerimos que incluyas detalles de tu operación, como categorías con mayores ingresos, políticas de facturación, comisión sobre productos, si permites que el seller procese el pago, entre otros.  
+- **Nombre del contacto:** nombre de la persona responsable de contactar con los partners potenciales. Sugerimos que sea la persona de tu equipo que ya tiene atribuida la tarea de atraerlos.  
+- **Email**: dirección de email de la persona responsable de contactar a los partners potenciales. Asegúrate de que la dirección de email es válida, ya que es ahí donde llegarán los mensajes enviados a tu tienda.  
+- **Teléfono**: teléfono de la persona responsable de contactar a los partners potenciales.  
+- **Utiliza un mensaje estándar:** mensaje personalizado que los sellers verán como predeterminado en el campo Enviar mensaje al hacer clic en tu perfil. Incluso activando esta opción, es posible editar el mensaje antes de enviárselo al partner potencial.  
+
+## Recomendaciones  
+
+Cuando interactúes con las páginas **Encontrar sellers** y **Marketplaces e integraciones**, no pierdas de vista las siguientes recomendaciones para aprovechar al máximo la funcionalidad:  
+
+- Cuando rellenes el perfil de tu tienda, pon el sitio web oficial de la marca.  
+- Sugerimos facilitar los datos de contacto del personal ya especializado y encargado de captar socios comerciales.  
+- Asegúrate de que el email y el número de teléfono registrados son válidos y están actualizados.  
+- Mantén tu perfil siempre actualizado con los links e información sobre la empresa.  
+- Proporciona una descripción completa y atractiva sobre tu tienda. Tu perfil es el que aparece en la lista de **[Encontrar sellers](https://help.vtex.com/tutorial/encontrar-sellers--6kkZaxIgfDyvN5trgIuwBl)** y **[Marketplaces e integraciones](https://help.vtex.com/es/tutorial/marketplaces-and-integrations--5AcBO1t29nhq7rBHas9b6V)**, así que es importante dar contexto y señalar aquello que te hace único.
diff --git a/docs/tutorials/es/store-settings-overview.md b/docs/tutorials/es/store-settings-overview.md
index ab5925920..6522eee11 100644
--- a/docs/tutorials/es/store-settings-overview.md
+++ b/docs/tutorials/es/store-settings-overview.md
@@ -3,8 +3,8 @@ title: 'Visión General Configuraciones de la Tienda'
 id: 6VtlMoid6iM9dP14X1CopT
 status: PUBLISHED
 createdAt: 2023-03-29T23:00:51.439Z
-updatedAt: 2023-03-29T23:07:38.446Z
-publishedAt: 2023-03-29T23:07:38.446Z
+updatedAt: 2023-09-13T22:38:50.560Z
+publishedAt: 2023-09-13T22:38:50.560Z
 firstPublishedAt: 2023-03-29T23:07:38.446Z
 contentType: tutorial
 productTeam: Management
@@ -17,14 +17,12 @@ subcategory: 5RAUzLD6X9Wa1maenj1eGA
 
 La configuración de la tienda se aplica a tu tienda y a tu *storefront*, y está relacionada con la forma en que tus clientes interactúan con tu ecommerce. Hemos agrupado todas estas configuraciones en la sección **Configuración de la tienda** en el menú de navegación a la izquierda del Admin v4. Allí puedes acceder a las configuraciones de Pagos, Pedidos, Plantillas de email, Envío, Productos, Storefront, Canales e Intelligent Search. 
 
-Para acceder a esta funcionalidad, haz clic en el ícono de **Configuración de la tienda** en el menú de navegación a la izquierda y luego en la sección deseada.
+Para acceder a esta funcionalidad, haz clic en **Configuración de la tienda** en el menú de navegación a la izquierda y luego en la sección deseada.
 
 <div class="alert alert-warning" role="alert">
 Ten en cuenta que las páginas y los ajustes configurados en el ambiente anterior no han cambiado, sino que se han reorganizado en la barra lateral del Admin, con lo que se ha cambiado la forma de acceder a ellos. 
 </div>
 
-![Admin v4 Store settings menu ES](https://images.ctfassets.net/alneenqid6w5/2EIX54YHzIivbQjreHGV4B/2abc0cab685c0421df6fe5d50f9e3162/Admin_v4_Store_settings_menu_ES.jpg)
-
 A continuación encontrarás más detalles sobre las diferentes secciones y páginas de este menú. 
 
 ## Pago
diff --git a/docs/tutorials/es/storefront-overview.md b/docs/tutorials/es/storefront-overview.md
index 00ab12cdc..31484c573 100644
--- a/docs/tutorials/es/storefront-overview.md
+++ b/docs/tutorials/es/storefront-overview.md
@@ -21,7 +21,7 @@ El _storefront_ también incluye VTEX Intelligent Search, una herramienta que ay
 
 Estas operaciones se realizan en el menú _Storefront_ de tu Admin VTEX. 
 
-![Storefront overview menu ES](https://images.ctfassets.net/alneenqid6w5/2vIJXsLuEsAOqgOxb9umYZ/b950fe38232e7fdb3603c1c344830d8a/Storefront_overview_menu_ES.jpg)
+![Storefront overview menu ES](//images.ctfassets.net/alneenqid6w5/2vIJXsLuEsAOqgOxb9umYZ/b950fe38232e7fdb3603c1c344830d8a/Storefront_overview_menu_ES.jpg)
 
 A continuación, encontrarás más detalles sobre las diferentes secciones y páginas de este menú.
 
diff --git a/docs/tutorials/es/styles-overview.md b/docs/tutorials/es/styles-overview.md
index bd61aa043..f644a77f4 100644
--- a/docs/tutorials/es/styles-overview.md
+++ b/docs/tutorials/es/styles-overview.md
@@ -19,7 +19,7 @@ La página **Estilos** te permite definir la tipografía y la paleta de colores
 
 Para acceder a Estilos, inicia sesión en el Admin VTEX, accede a **Storefront > Estilos** y descubre las principales herramientas disponibles en la interfaz.
 
-![Estilos - Visión general](https://images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/7b916baa31c3fe37cb946ac9afacd908/ES.png)
+![Estilos - Visión general](//images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/7b916baa31c3fe37cb946ac9afacd908/ES.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Para aplicar y obtener una vista previa de los cambios en los estilos de tu tienda, asegúrate de utilizar un espacio de trabajo que soporte el tráfico de producción, por ejemplo, <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">espacios de trabajo de producción</a>. 
diff --git a/docs/tutorials/es/subscription-plans.md b/docs/tutorials/es/subscription-plans.md
index 20dda4ffd..7a53da8d3 100644
--- a/docs/tutorials/es/subscription-plans.md
+++ b/docs/tutorials/es/subscription-plans.md
@@ -21,7 +21,7 @@ Para que los planes de suscripción estén disponibles, primero debe instalar la
 
 En la página de **Planes**, puede ver y gestionar los planes de suscripción disponibles para los clientes de su tienda, según se ilustra a continuación.
 
-![planslist ES](https://images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/d5e90eb8a6d31b3d0b66d01f0a9839e8/planslist_ES.png)
+![planslist ES](//images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/d5e90eb8a6d31b3d0b66d01f0a9839e8/planslist_ES.png)
 
 Las principales funcionalidades de esta página son:
 
diff --git a/docs/tutorials/es/synonym-list.md b/docs/tutorials/es/synonym-list.md
new file mode 100644
index 000000000..02a4a20d6
--- /dev/null
+++ b/docs/tutorials/es/synonym-list.md
@@ -0,0 +1,112 @@
+---
+title: 'Lista de sinónimos'
+id: 3E1fi0C6tVrR0klMFXAaU8
+status: PUBLISHED
+createdAt: 2024-06-07T13:18:30.251Z
+updatedAt: 2024-06-17T13:55:16.006Z
+publishedAt: 2024-06-17T13:55:16.006Z
+firstPublishedAt: 2024-06-17T13:43:23.975Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: lista-de-sinonimos
+locale: es
+legacySlug: lista-de-sinonimos
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+La página **Sinónimos** te permite ver y gestionar todos los [sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de Intelligent Search registrados en tu tienda. Accede a través del Admin VTEX, haciendo clic en **Storefront > Intelligent Search > Sinónimos**.
+
+![lista-sinonimos-es](//images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/7dcff1482a82ff95a77a3aa783157069/lista-sinonimos-es.PNG)
+
+La página presenta la siguiente información en forma de tabla:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Columnas</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descripción</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Términos</td>
+      <td class="t-body pa5">
+        Términos definidos como sinónimos e indicación del tipo de sinónimo:
+        <ul>
+          <li><i class="fas fa-exchange-alt"></i> Bidireccional</li>
+          <li><i class="fas fa-long-arrow-alt-right"></i> Unidireccional</li>
+        </ul>
+        Aprende más sobre cada uno en
+        <a
+          href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos"
+          target="_blank"
+          rel="noopener noreferrer"
+          >Tipos de sinónimos</a>.
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Fecha de creación</td>
+      <td class="t-body pa5">Fecha de creación del sinónimo.</td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Status</td>
+      <td class="t-body pa5">
+        Situación de los sinónimos, que puede ser:
+        <ul>
+          <li>Activo</li>
+          <li>Inactivo</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Esta página te permite realizar las siguientes acciones:
+
+* [Crear sinónimos](#crear-sinonimos)
+* [Importar sinónimos](#importar-sinonimos)
+* [Buscar sinónimos](#buscar-sinonimos)
+* [Filtrar sinónimos](#filtrar-sinonimos)
+* [Editar sinónimos](#editar-sinonimos)
+* [Eliminar sinónimos](#eliminar-sinonimos)
+
+## Crear sinónimos
+
+Puedes crear sinónimos individualmente haciendo clic en el botón `Crear sinónimo`. Sigue las instrucciones descritas en [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#criar-sinonimos-individualmente).
+
+## Importar sinónimos
+
+También es posible crear sinónimos en masa a partir de la importación de un archivo CSV, haciendo clic en el botón `Importar`. Consulta las instrucciones descritas en [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#importar-csv) para entender el modelo de la plantilla y cómo cargarla.
+
+## Buscar sinónimos
+
+La página **Sinónimos **permite buscar cualquier término configurado como sinónimo mediante la barra de búsqueda. Los sinónimos listados se actualizan automáticamente.
+
+## Filtrar sinónimos
+
+Puede filtrar la lista de sinónimos entre las siguientes opciones:
+
+* **Status**
+    * Activo
+    * Inactivo
+* **Fecha de creación**
+    * Hoy
+    * Ayer
+    * Últimos 7 días
+    * Últimos 15 días
+    * Últimos 30 días
+    * Últimos 3 meses
+    * Últimos 12 meses
+
+## Editar sinónimo
+
+Para editar un sinónimo registrado, haz clic en la fila correspondiente en la lista de sinónimos. Consulta más información sobre los campos editables en [Configurar sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#criar-sinonimos-individualmente).
+
+## Eliminar sinónimo
+
+Para eliminar un sinónimo, sigue los pasos a continuación:
+
+1. Pasa el mouse sobre la fila del sinónimo
+2. Haz clic en el ícono de la papelera <i class="fas fa-trash-alt"></i>.
+3. Haz clic en `Eliminar` para confirmar.
diff --git a/docs/tutorials/es/table-of-base-prices.md b/docs/tutorials/es/table-of-base-prices.md
index f34f310d8..24c069b3a 100644
--- a/docs/tutorials/es/table-of-base-prices.md
+++ b/docs/tutorials/es/table-of-base-prices.md
@@ -44,7 +44,7 @@ Los siguientes campos son opcionales en la plantilla, se exportan solo para exhi
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/2XX0xwgVreVnFb6U2rjJR7/900c3bc9557aabaa87811369ce785581/baseprices_table.png" style="display: block; margin-left: auto; margin-right: auto;" alt="base prices table" title="base prices table">
+    <img src="https://images.ctfassets.net/alneenqid6w5/2XX0xwgVreVnFb6U2rjJR7/900c3bc9557aabaa87811369ce785581/baseprices_table.png" style="display: block; margin-left: auto; margin-right: auto;" alt="base prices table" title="base prices table">
    </td>
   </tr>
   <tr>
diff --git a/docs/tutorials/es/telesales-features.md b/docs/tutorials/es/telesales-features.md
index 08aa43c27..f2be915ea 100644
--- a/docs/tutorials/es/telesales-features.md
+++ b/docs/tutorials/es/telesales-features.md
@@ -1,10 +1,10 @@
 ---
 title: 'Funcionalidades de televentas'
 id: UqhiccIRIK2KD0OqkzJaS
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-05-13T18:26:51.189Z
-updatedAt: 2023-03-07T00:19:05.776Z
-publishedAt: 2023-03-07T00:19:05.776Z
+updatedAt: 2023-12-20T16:58:46.983Z
+publishedAt: 2023-10-18T17:09:06.185Z
 firstPublishedAt: 2021-05-17T12:07:02.897Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/es/telesales-toolbar.md b/docs/tutorials/es/telesales-toolbar.md
index 944295d1c..3fcb04d3d 100644
--- a/docs/tutorials/es/telesales-toolbar.md
+++ b/docs/tutorials/es/telesales-toolbar.md
@@ -3,8 +3,8 @@ title: 'Barra de herramientas de televentas'
 id: tutorials_5500
 status: PUBLISHED
 createdAt: 2017-04-27T21:48:31.368Z
-updatedAt: 2023-03-29T19:50:13.858Z
-publishedAt: 2023-03-29T19:50:13.858Z
+updatedAt: 2023-12-07T15:29:46.537Z
+publishedAt: 2023-12-07T15:29:46.537Z
 firstPublishedAt: 2017-04-27T23:11:19.311Z
 contentType: tutorial
 productTeam: Shopping
@@ -19,7 +19,7 @@ La barra de herramientas de televentas es una barra superior que se muestra en e
 
 La barra de herramientas aparece una vez que el operador registrado inicia sesión en el ambiente de la tienda y esta se muestra en todas las áreas del sitio web.
 
-![toolbartelevendas ES](https://images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ac84e4fa98ca225195dae8890f04333b/toolbartelevendas_ES.png)
+![toolbartelevendas ES](//images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ac84e4fa98ca225195dae8890f04333b/toolbartelevendas_ES.png)
 
 Estos son los principales recursos de la barra de herramientas:
 *   [Entrar como cliente](#entrar-como-cliente)
@@ -57,7 +57,8 @@ Al hacer clic en el nombre del cliente, el operador puede ver la siguiente infor
 
 ## Artículos relacionados
 
-*   [Roles de usuario - televentas](https://help.vtex.com/es/tutorial/como-criar-um-usuario-de-televendas--frequentlyAskedQuestions_4227)
+*   [Roles de usuario predefinidos - Call center operator](https://help.vtex.com/es/tutorial/roles-de-usuario-predefinidos--jGDurZKJHvHJS13LnO7Dy#call-center-operator)
+*   [Crear usuario de televentas](https://help.vtex.com/es/tutorial/como-creo-un-usuario-de-televentas--frequentlyAskedQuestions_4227)
 *   [Personalizar la barra de herramientas de televentas](https://help.vtex.com/es/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg)
 *   [Pedidos](https://help.vtex.com/es/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#pedidos)
 *   [Funcionalidades de televentas](https://help.vtex.com/es/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS)
diff --git a/docs/tutorials/es/test-kr1.md b/docs/tutorials/es/test-kr1.md
new file mode 100644
index 000000000..dcfd3563b
--- /dev/null
+++ b/docs/tutorials/es/test-kr1.md
@@ -0,0 +1,18 @@
+---
+title: 'Test KR1'
+id: 4IbRozfaZJHar1adTlr1yq
+status: DRAFT
+createdAt: 2024-06-07T18:51:10.051Z
+updatedAt: 2024-06-07T18:52:10.590Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: VTEX IO
+author: 
+slug: test-kr1
+locale: es
+legacySlug: test-kr1
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+
diff --git a/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md b/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md
new file mode 100644
index 000000000..8daa841e3
--- /dev/null
+++ b/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md
@@ -0,0 +1,46 @@
+---
+title: 'El pedido se dividió en paquetes con envíos separados'
+id: 3OCOC82543vOsc3Ex32XTY
+status: PUBLISHED
+createdAt: 2024-06-19T15:03:37.373Z
+updatedAt: 2024-06-19T15:13:11.172Z
+publishedAt: 2024-06-19T15:13:11.172Z
+firstPublishedAt: 2024-06-19T15:13:11.172Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: el-pedido-se-dividio-en-paquetes-con-envios-separados
+locale: es
+legacySlug: el-pedido-se-dividio-en-paquetes-con-envios-separados
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palabras clave:** envíos separados, split de pedidos, paquetes, envío, productos de preventa.
+
+En VTEX, los clientes pueden recibir su pedido dividido en varios paquetes, independientemente de si [la división del pedido](https://help.vtex.com/es/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV) se reflejó en la plataforma. El cliente puede recibir los ítems del pedido en paquetes separados en los siguientes casos:
+
+* **Pedido con sellers diferentes:** se genera un pedido para cada seller y tendrá al menos un paquete para el envío de cada seller.
+* **Selección de sellers white label:** cuando se trata de [sellers white label](https://help.vtex.com/es/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) el envío puede realizarse en paquetes diferentes.
+* **Seller con diferentes SLA para el envío de los ítems:** aunque sea un único seller, si los ítems tienen SLA distintos, el pedido puede enviarse en paquetes separados.
+* **Productos de preventa:** cuando el pedido incluye [productos de preventa](https://help.vtex.com/es/tutorial/cadastrar-um-produto-para-pre-venda--4o6cUJ4gIg0MQWW8WfN34K) y productos normales, el envío se realizará en paquetes separados.
+
+Si el pedido incluye productos de preventa, todos los productos, tanto los de preventa como los normales, se muestran con la misma fecha de entrega en el checkout cuando se genera el pedido. Sin embargo, esa fecha es solo un cálculo de entrega. Tras la aprobación del pago, el pedido se divide en paquetes separados: uno que incluye los productos de preventa y otro con los productos normales.
+
+La fecha de entrega de cada paquete se modifica en función del valor de `shippingEstimateDate` de cada producto. Este campo se puede verificar mediante el endpoint [Get order](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-).
+
+## Solución
+
+Para evitar que se dividan los paquetes de pedidos que incluyen productos de preventa, puedes configurar [grupos de envío](https://help.vtex.com/es/tutorial/como-funciona-a-remessa). De este modo, puedes agrupar en un solo conjunto todos los paquetes que serán entregados por la misma transportadora y provenientes del mismo [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
+
+<div class="alert alert-danger">
+Configurar los grupos de envío aplicará este comportamiento a todos los pedidos con fechas de entrega diferentes y no solo a los que tengan productos de preventa.
+</div>
+
+### Configurar grupos de envío
+
+Para configurar grupos de envío en tu tienda sigue los pasos a continuación:
+
+1. En el Admin VTEX, accede a **Configuración de la tienda > Envío > Configuración** o ingresa **Envío** en la barra de búsqueda en la parte superior de la página y selecciona **Configuración de la tienda / Envío**.
+2. En la sección **Grupo de entrega** de la página **Configuración general**, rellena el campo _Crear grupos de envío con intervalos de {X} día(s)_ con el número de días que deseas definir para el [envío](https://help.vtex.com/es/tutorial/como-funciona-a-remessa).
+3. Haz clic en **Guardar**.
+
diff --git a/docs/tutorials/es/the-price-in-the-search-result-is-different-from-the-product-page.md b/docs/tutorials/es/the-price-in-the-search-result-is-different-from-the-product-page.md
index c185032e2..b35a2a3e5 100644
--- a/docs/tutorials/es/the-price-in-the-search-result-is-different-from-the-product-page.md
+++ b/docs/tutorials/es/the-price-in-the-search-result-is-different-from-the-product-page.md
@@ -3,8 +3,8 @@ title: 'El precio del resultado de búsqueda es diferente de la página de produ
 id: 1108Xha3zw6ZvVUINfY7HR
 status: PUBLISHED
 createdAt: 2022-11-22T14:26:20.489Z
-updatedAt: 2022-11-22T14:42:50.738Z
-publishedAt: 2022-11-22T14:42:50.738Z
+updatedAt: 2024-06-04T12:45:41.670Z
+publishedAt: 2024-06-04T12:45:41.670Z
 firstPublishedAt: 2022-11-22T14:42:50.738Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -12,7 +12,7 @@ author: 2o8pvz6z9hvxvhSoKAiZzg
 slug: el-precio-del-resultado-de-busqueda-es-diferente-de-la-pagina-de-producto
 locale: es
 legacySlug: el-precio-del-resultado-de-busqueda-es-diferente-de-la-pagina-de-producto
-subcategory: 4tkE7m5rJisNuhJisIxWHD
+subcategory: 23NGhMgqA1eCYad7kzRFGu
 ---
 
 Durante la [actualización de precio de un SKU](https://help.vtex.com/es/tutorial/alteracao-de-preco-de-sku--tutorials_95), puede que el precio del resultado de búsqueda diverja del precio o stock de la página de producto si la tienda utiliza [Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb).
diff --git a/docs/tutorials/es/tools-to-help-the-performance-of-your-e-commerce.md b/docs/tutorials/es/tools-to-help-the-performance-of-your-e-commerce.md
index 1647c2f89..03fa97f13 100644
--- a/docs/tutorials/es/tools-to-help-the-performance-of-your-e-commerce.md
+++ b/docs/tutorials/es/tools-to-help-the-performance-of-your-e-commerce.md
@@ -1,10 +1,10 @@
 ---
 title: 'Herramientas para mejorar la performance de la tienda'
 id: tutorials_4852
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:49:27.344Z
-updatedAt: 2020-07-26T15:27:37.237Z
-publishedAt: 2020-07-26T15:27:37.237Z
+updatedAt: 2024-03-11T13:20:56.413Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:11:17.373Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/total-shipping-cost.md b/docs/tutorials/es/total-shipping-cost.md
index 61bc5e138..a169d6bea 100644
--- a/docs/tutorials/es/total-shipping-cost.md
+++ b/docs/tutorials/es/total-shipping-cost.md
@@ -31,7 +31,7 @@ Vea cómo se calcula cada tarifa:
 
 Así que, en general, el costo final del envío puede calcularse así:
 
-![Custo-final-envio-ES](https://images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/48b3d941065ab47cb55c7b4590b993bd/Custo-final-envio-ES.svg)
+![Custo-final-envio-ES](//images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/48b3d941065ab47cb55c7b4590b993bd/Custo-final-envio-ES.svg)
 
 <div class="alert alert-danger">
 Si el <b>adicional de precio</b> es inferior al <b>adicional de seguro,</b> la tarifa considerada es el adicional de seguro. El adicional de precio no se tomará en cuenta en el cálculo de la tarifa final.<p>
diff --git a/docs/tutorials/es/tracking-your-sales-analytics.md b/docs/tutorials/es/tracking-your-sales-analytics.md
index 8cbb0b417..bd532ba04 100644
--- a/docs/tutorials/es/tracking-your-sales-analytics.md
+++ b/docs/tutorials/es/tracking-your-sales-analytics.md
@@ -1,10 +1,10 @@
 ---
 title: 'Siguiendo la evolución de sus ventas'
 id: 5QtyTR0jFy9gDnr4EYCjdq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-09-10T13:32:39.637Z
-updatedAt: 2020-09-11T00:16:35.791Z
-publishedAt: 2020-09-11T00:16:35.791Z
+updatedAt: 2023-10-18T15:24:34.576Z
+publishedAt: 
 firstPublishedAt: 2020-09-10T17:37:50.007Z
 contentType: tutorial
 productTeam: Management
@@ -38,7 +38,7 @@ La hora de referencia de los datos se indica en la interfaz con un retraso de un
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/2f8tj5XokKtnZOvjfgmFVf/19eb434db4421da2c0b461268cec80f9/Insights_-_Conhecendo_a_interface__1_.png?h=250" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Conhecendo a interface" title="Insights - Conhecendo a interface">
+    <img src="https://images.ctfassets.net/alneenqid6w5/2f8tj5XokKtnZOvjfgmFVf/19eb434db4421da2c0b461268cec80f9/Insights_-_Conhecendo_a_interface__1_.png?h=250" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Conhecendo a interface" title="Insights - Conhecendo a interface">
    </td>
   </tr>
   <tr>
@@ -57,7 +57,7 @@ Este panel permite comparar el valor consolidado de las métricas entre los día
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/5lKQrdbytYWAaMV3tHnOi4/727c2229447881d0ae905c20995ca0f7/Insights_-_Visa__o_Geral__1_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Visão Geral" title="Insights - Visão Geral">
+    <img src="https://images.ctfassets.net/alneenqid6w5/5lKQrdbytYWAaMV3tHnOi4/727c2229447881d0ae905c20995ca0f7/Insights_-_Visa__o_Geral__1_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Visão Geral" title="Insights - Visão Geral">
    </td>
   </tr>
   <tr>
@@ -76,7 +76,7 @@ Este panel permite seguir la evolución de las métricas a lo largo del día. Al
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/L43eNghJLlakmOFcGmKiM/3741dfa1b1837a51d3437c9d5cfbd5e0/Insights_-_Detalhes__1_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 1" title="Insights - Detalhes 1">
+    <img src="https://images.ctfassets.net/alneenqid6w5/L43eNghJLlakmOFcGmKiM/3741dfa1b1837a51d3437c9d5cfbd5e0/Insights_-_Detalhes__1_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 1" title="Insights - Detalhes 1">
    </td>
   </tr>
   <tr>
@@ -91,7 +91,7 @@ Este panel permite seguir la evolución de las métricas a lo largo del día. Al
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/1TExoNJjCZInwh3LGQrkzO/d425b2c7c83551decd7f2edddf1026cc/image13.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 2" title="Insights - Detalhes 2">
+    <img src="https://images.ctfassets.net/alneenqid6w5/1TExoNJjCZInwh3LGQrkzO/d425b2c7c83551decd7f2edddf1026cc/image13.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 2" title="Insights - Detalhes 2">
    </td>
   </tr>
   <tr>
@@ -117,7 +117,7 @@ Este panel permite seguir el volumen de sesiones en las etapas intermedias del f
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/4DdN3hdCz7CdoukLu3H0Ea/6e7d8add7116d6334148fec85878b993/Insights_-_Funil_de_conversa__o__1_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Funil de conversão" title="Insights - Funil de conversão">
+    <img src="https://images.ctfassets.net/alneenqid6w5/4DdN3hdCz7CdoukLu3H0Ea/6e7d8add7116d6334148fec85878b993/Insights_-_Funil_de_conversa__o__1_.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Funil de conversão" title="Insights - Funil de conversão">
    </td>
   </tr>
   <tr>
diff --git a/docs/tutorials/es/transactional-emails-for-subscription-orders.md b/docs/tutorials/es/transactional-emails-for-subscription-orders.md
index b8ab2bd48..c45362578 100644
--- a/docs/tutorials/es/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/es/transactional-emails-for-subscription-orders.md
@@ -3,8 +3,8 @@ title: 'Correos Electrónicos Transaccionales para Pedidos de Suscripción'
 id: 2NYHqHMRqZ43Cn6s84ZCB5
 status: PUBLISHED
 createdAt: 2020-02-11T15:13:38.504Z
-updatedAt: 2021-11-30T18:14:37.654Z
-publishedAt: 2021-11-30T18:14:37.654Z
+updatedAt: 2023-12-21T14:14:10.536Z
+publishedAt: 2023-12-21T14:14:10.536Z
 firstPublishedAt: 2020-02-17T21:15:14.903Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -28,6 +28,10 @@ También puede crear su propia plantilla de correo electrónico. Entienda mejor
 
 ## Cómo su cliente acompaña sus pedidos de suscripción
 
+<div class = "alert alert-info">
+En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
+</div>
+
 Cada acción, que ocurre dentro del flujo de pedidos de Suscripción, contiene un gatillo que dispara un correo electrónico notificando a su cliente.  Una vez activada la suscripción, el cliente recibirá correos electrónicos con detalles del status de cada pedido de suscripción cada vez que realice una acción. 
 
 No es necesario activar el envío de correos electrónicos manualmente, pues se envían automáticamente según cada escenario incluido en el Centro de Mensajes. Sin embargo, si lo desea, puede desactivar el envío de determinados correos electrónicos:
@@ -39,7 +43,7 @@ No es necesario activar el envío de correos electrónicos manualmente, pues se
 5. Desactive la casilla `¿Activar envío de e-mail?`, que por defecto está marcada como activa.
 6. Haga clic en **Guardar**.
 
-![PT Subscription Message Center](https://images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
+![PT Subscription Message Center](//images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
 
 ## Plantillas Estándar del Centro de Mensajes 
 
diff --git a/docs/tutorials/es/transactions-events.md b/docs/tutorials/es/transactions-events.md
index cca21bd00..664e515c8 100644
--- a/docs/tutorials/es/transactions-events.md
+++ b/docs/tutorials/es/transactions-events.md
@@ -75,5 +75,5 @@ Generalmente, las afiliaciones permiten configurar una fecha programada de captu
 
 Aquí se logra visualizar la fecha de la programación de la captura automática:
 
-![captura-auto-agendada es](https://images.ctfassets.net/alneenqid6w5/6aACu6LopG4OUC6AWIAMuC/957305614367791a46fe152d021b3430/transa____o_programada_cap_auto_es.png)
+![captura-auto-agendada es](//images.ctfassets.net/alneenqid6w5/6aACu6LopG4OUC6AWIAMuC/957305614367791a46fe152d021b3430/transa____o_programada_cap_auto_es.png)
 
diff --git a/docs/tutorials/es/transferring-store-ownership.md b/docs/tutorials/es/transferring-store-ownership.md
index 1d91a7b0c..9700d1c84 100644
--- a/docs/tutorials/es/transferring-store-ownership.md
+++ b/docs/tutorials/es/transferring-store-ownership.md
@@ -25,7 +25,7 @@ La página de «Gestión de titular» le permite identificar al usuario titular
 
 Debe ver una pantalla similar a la imagen a continuación que tiene la información del usuario titular actual, un descargo de responsabilidad que indica los riesgos asociados a la transferencia de la propiedad de la tienda y un botón para aceptar los riesgos y transferir la propiedad de todas maneras.
 
-![Panel de gestión de titular](https://images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/8220a9866df4786fcff4fb3b5a29f6ca/Sponsor_Management_es.png)
+![Panel de gestión de titular](//images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/8220a9866df4786fcff4fb3b5a29f6ca/Sponsor_Management_es.png)
 
 ## Pasos de la transferencia de propiedad
 
@@ -51,7 +51,7 @@ Esto completa la transferencia de propiedad y ya no se podrá cancelar la invita
 
 El usuario titular es responsable de importantes acciones de mantenimiento y autorización, y los errores cometidos por él pueden tener consecuencias graves. Por lo tanto, es esencial seguir los cambios relacionados con este rol de usuario. Para monitorizar y auditar las transferencias de propiedad de la cuenta, puede acceder al registro de actividades haciendo clic en el botón Registro de Actividades en la página Gestión de Titular.
 
-![Registro de Actividades](https://images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/65400ca2fe5cf04983b4b774327de310/Activity_Log_es.gif)
+![Registro de Actividades](//images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/65400ca2fe5cf04983b4b774327de310/Activity_Log_es.gif)
 
 Todos los eventos relacionados con la transferencia de propiedad de la cuenta se registran en el registro de actividades con la fecha en que se produjeron y el usuario asociado al evento.
 
diff --git a/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
index c4b94b771..cfe033d09 100644
--- a/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
@@ -3,8 +3,8 @@ title: 'Cómo solucionar errores en pedidos de suscripción'
 id: uLL8AYBGdtAmbbdL5gRCf
 status: PUBLISHED
 createdAt: 2020-02-05T14:32:49.763Z
-updatedAt: 2022-12-05T17:09:40.639Z
-publishedAt: 2022-12-05T17:09:40.639Z
+updatedAt: 2023-12-21T14:07:42.772Z
+publishedAt: 2023-12-21T14:07:42.772Z
 firstPublishedAt: 2020-02-11T15:00:00.666Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: como-resolver-pedidos-de-suscripcion-con-errores
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
+<div class = "alert alert-info">
+Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
+</div>
+
 Es posible identificar y gestionar errores en pedidos de suscripción a través del módulo **Suscripciones** > **Dashboards** > **Pedidos de suscripción** en el Admin.
 
 Hay dos tipos de errores que pueden ocurrir con los pedidos de suscripción:
@@ -28,7 +32,7 @@ Los problemas en ciclos de suscripción se producen cuando hay un impedimento pa
 
 La pestaña **Ciclos con un problema**, que se ilustra en la siguiente imagen, recoge los pedidos de suscripción que tienen este tipo de problemas.
 
-![pedidos_assinaturas_print_es](https://images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
+![pedidos_assinaturas_print_es](//images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
 
 Desde esta pestaña se puede gestionar los pedidos que presentan ciclos con un problema y realizar reintentos manuales de creación de pedidos. Por ejemplo, cuando un producto no está disponible, puede ajustar el stock y volver a intentarlo.
 
@@ -185,7 +189,7 @@ Los errores de pago se producen durante el flujo de aprobación del pago, como e
 
 Los pedidos con este tipo de error pueden visualizarse en la pestaña **Error de pago**, ilustrada en la siguiente imagen.
 
-![pedidos_assinaturas_print_erro_pagamento_es](https://images.ctfassets.net/alneenqid6w5/2Cc9hhcSr6CjeU3tDIerqo/adfef0d0054bb88ef52d32d6ce7d81fd/pedidos_assinaturas_print_erro_pagamento_es.png)
+![pedidos_assinaturas_print_erro_pagamento_es](//images.ctfassets.net/alneenqid6w5/2Cc9hhcSr6CjeU3tDIerqo/adfef0d0054bb88ef52d32d6ce7d81fd/pedidos_assinaturas_print_erro_pagamento_es.png)
 
 Para analizar errores de pago, realice el siguiente procedimiento.
 
diff --git a/docs/tutorials/es/understanding-b2b-orders.md b/docs/tutorials/es/understanding-b2b-orders.md
index 3f04e8b27..87f3a0a83 100644
--- a/docs/tutorials/es/understanding-b2b-orders.md
+++ b/docs/tutorials/es/understanding-b2b-orders.md
@@ -19,7 +19,7 @@ En una operación de comercio electrónico B2B, habitualmente se necesita inform
 
 La app **Pedidos B2B** simplifica este proceso y permite que cualquier colaborador de la empresa que realizó la compra  pueda consultar los pedidos realizados accediendo a la tienda virtual.
 
-![orders VTEX B2B](https://images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
+![orders VTEX B2B](//images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
 
 Esa experiencia de autoservicio es posible gracias a una integración vía API con el ERP. De esta forma, el colaborador puede buscar pedidos por: 
 
diff --git a/docs/tutorials/es/understanding-how-indexation-works.md b/docs/tutorials/es/understanding-how-indexation-works.md
index ea61a9d0a..29d308466 100644
--- a/docs/tutorials/es/understanding-how-indexation-works.md
+++ b/docs/tutorials/es/understanding-how-indexation-works.md
@@ -3,8 +3,8 @@ title: 'Cómo funciona la indexación'
 id: tutorials_256
 status: PUBLISHED
 createdAt: 2017-04-27T22:11:43.688Z
-updatedAt: 2023-03-29T19:50:49.722Z
-publishedAt: 2023-03-29T19:50:49.722Z
+updatedAt: 2024-03-04T16:39:16.578Z
+publishedAt: 2024-03-04T16:39:16.578Z
 firstPublishedAt: 2017-04-27T23:03:11.322Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,6 +15,11 @@ legacySlug: entendiendo-el-funcionamento-de-la-indexacion
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
+<div class="alert alert-warning">
+<p>Este tutorial sólo es válido para las tiendas que utilizan la búsqueda del <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>.</p>
+<p>Si su tienda utiliza el <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>, consulte la página <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Historial de indexación</a> para seguir el proceso de indexación.</p>
+</div>
+
 La indexación es un proceso que prepara los datos generales del SKU, tales como datos de catálogo, de precio y de stock y actualiza la información para servir de base para búsquedas y montajes de las estantes del sitio.
 
 Cada vez que se modifican los datos del listado de productos como se muestra a continuación, la base de datos se vuelve a indexar.
@@ -27,7 +32,7 @@ Cada vez que se modifican los datos del listado de productos como se muestra a c
 
 Una vez que el producto esté marcado para reindexar, éste queda con el texto _indexação pendente_ en el listado de productos del admin. El indexador toma esos productos y los coloca en una fila, con un tiempo de espera de 2 minutos, para que sean procesados. Pasados los 2 minutos el producto queda disponible para el consumo de la indexación. En ese proceso, todos los módulos de VTEX son consultados, actualizando precio y disponibilidad para cada política comercial. El tempo medio hasta finalizar este proceso es de 4 minutos.
 
-![diagramaespanhol](https://images.ctfassets.net/alneenqid6w5/SR9YuOnYK2Ku0CW2K2iEO/26f0b18db9ec54d5055cc377d911c2b0/diagramaespanhol.png)
+![diagramaespanhol](//images.ctfassets.net/alneenqid6w5/SR9YuOnYK2Ku0CW2K2iEO/26f0b18db9ec54d5055cc377d911c2b0/diagramaespanhol.png)
 
 ## Informe de Indexación
 
@@ -42,7 +47,7 @@ En él, se dividen los productos en cada paso del proceso de indexación y en pe
 - **Total Indexado**, **Aún no en la fila** y **Total en la fila**: : se refiere a las etapas del producto dentro del proceso &#8211; Ainda não enfileirado son los productos que se modificaron en menos de 2 minutos y Total na fila son aquellos que ya entraron en proceso de indexación, tras esos 2 minutos.
 - **En la fila recientemente**, **En la fila entre 1 y 2 hs**, **En la fila de 2 a 4 hs** y **En la fila de 4 a 8 hs**: son los períodos en que los productos están en el proceso de indexación.
 
-![productosindexados](https://images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
+![productosindexados](//images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
 
 En el informe de indexación, también existe el tiempo que el último ítem tardó para ser re indexado. Queda al lado derecho superior del informe, conforme a la imagen arriba.
 
diff --git a/docs/tutorials/es/understanding-how-the-cache-works.md b/docs/tutorials/es/understanding-how-the-cache-works.md
index 3ca896d46..7d59ffded 100644
--- a/docs/tutorials/es/understanding-how-the-cache-works.md
+++ b/docs/tutorials/es/understanding-how-the-cache-works.md
@@ -19,11 +19,11 @@ El concepto de cache es bastante difundido como siendo un dispositivo de acceso
 
 Cuando una página o archivo inicia su carga, a través de la URL, el browser realiza una solicitud para el servidor que, por su parte, tiene la función de responder con información relevante para aquella solicitud. La solicitud del browser se conoce como **request** y la respuesta del servidor como **response**. Esos términos serán bastante utilizados en el transcurso de este artículo. Vea el esquema abajo:
 
-![Como o cache funciona - comunicação entre servidor e navegador](https://images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/1d05717d54faede0fc00d75716d7def4/1_ES.png)
+![Como o cache funciona - comunicação entre servidor e navegador](//images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/1d05717d54faede0fc00d75716d7def4/1_ES.png)
 
 El cache está representado a través de una capa entre el browser y el servidor y, así, cuando un **request** ocurre, en vez del sistema ir a buscar la información directamente en el servidor, primero va a esa capa, lo que vuelve mucho más ágil a la respuesta. Vea el esquema abajo:
 
-![Cómo funciona el caché: comunicación con el caché (sin caducar)](https://images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/3d375c19c114eecdbe75decac28e2df3/2_PT.png)
+![Cómo funciona el caché: comunicación con el caché (sin caducar)](//images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/3d375c19c114eecdbe75decac28e2df3/2_PT.png)
 
 Sin embargo, como el dato actualizado está en el servidor, de tiempo en tiempo es necesario actualizar el cache. Ese tiempo varía de acuerdo al tipo de **request, **o sea, si el **request** es una página, el tiempo es uno, si es un archivo javascript o CSS, es otro y aún, si es una imagen, será otro.
 
@@ -50,7 +50,7 @@ Como ya se ha dicho, tempo de duração del cache varía para cada tipo de **req
 
 Cuando el cache de un **request** (página o archivo) expira, al realizar una nueva solicitud, o sea, al cargar nuevamente la URL, el sistema va al servidor, rescata la información actualizada para aquella solicitud y actualiza el contenido de aquella URL en el cache. Después de actualizada, la versión cacheada vuelve a ser retornada para nuevas solicitudes de URL. Vea el esquema ilustrando ese caso:
 
-![Cómo funciona la caché: comunicación con la caché (caducada)](https://images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/36d452de8975e10cbb847787bddaf1e1/3_ES.png)
+![Cómo funciona la caché: comunicación con la caché (caducada)](//images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/36d452de8975e10cbb847787bddaf1e1/3_ES.png)
 
 En ese aspecto, podemos separar las respuestas en dos grupos: Cacheadas y no cacheadas.
 
diff --git a/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md b/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md
index 32a220f4c..a5723ce3d 100644
--- a/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md
+++ b/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md
@@ -15,7 +15,7 @@ legacySlug: conociendo-el-storebuilder-y-el-stylesbuilder
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-![UI Blocks Voando.mp4](https://images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
+![UI Blocks Voando.mp4](//images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
 
 Esta documentación se ha estructurado para explicar los conceptos detrás del StoreBuilder y StyleBuilder de la Store 2.xx. Durante toda la documentación, utilizaremos la DreamStore (una tienda template que utiliza la `Store 2.xx`) para entender los principales conceptos que le permitirán estructurar y estilizar su tienda.
 
@@ -39,7 +39,7 @@ La Store 2 hace grandes cambios de paradigma en la Store 1, introduciendo el con
 
 Vamos a mirar dentro del `/manifest.json` de DreamStore para ver lo que nuestra aplicación necesita para funcionar correctamente:
 
-![Screen Shot 2019-01-25 at 16.40.06](https://images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
+![Screen Shot 2019-01-25 at 16.40.06](//images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
 
 Observe cómo tenemos dos builders especificados:
 
@@ -59,7 +59,7 @@ Como cualquier theme app (una tienda) hace uso de la aplicación `Store` (a trav
 
 Ejecute "vtex link" y envie la app DreamStore a un workspace para que podamos estudiarla.
 
-![Screen Shot 2019-01-27 at 22.24.47](https://images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
+![Screen Shot 2019-01-27 at 22.24.47](//images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
 
 Si está familiarizado con React o otros frameworks modernos de Javascript, usted estará familiarizado con el concepto de componentes en una página web. Como podemos observar, nuestra página web tiene un "header", un "carrusel" y un "estante". ¿Cómo se insertaron estos componentes?
 
@@ -97,7 +97,7 @@ _Tenga en cuenta que usted no estará desarrollando en la aplicación Store 2, p
 
 Vamos a mirar dentro del archivo `/manifest.json` de la Store2.xx para ver lo que importa la aplicación.
 
-![Screen Shot 2019-01-25 at 17.18.56](https://images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
+![Screen Shot 2019-01-25 at 17.18.56](//images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
 
 Podemos ver que es una estructura similar a la del `manifest.json` de la `Dreamstore`.
 
@@ -142,7 +142,7 @@ __Como cada página es definida por bloques y organizada por interfaces__, es ho
 Abra la carpeta `store` y después el archivo `interfaces.json`.
 
 ### Interfaces
-![Screen Shot 2019-01-25 at 17.35.10](https://images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
+![Screen Shot 2019-01-25 at 17.35.10](//images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
 
 Una interfaz es un conjunto de `blocks` y existe exclusivamente dentro de la `Store2.xx`. Sirve como un contrato entre los bloques y determina cómo van a trabajar juntos.
 
@@ -199,7 +199,7 @@ Vamos a seguir analizando el `store.home`. Tenga atención a los comentarios inl
 ```
 
 Si descendemos podemos ver los mismos objetos JSON definiendo y configurando la organización de la página. Otro ejemplo es la página de resultados de la búsqueda:
-![Screen Shot 2019-01-25 at 18.22.12](https://images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
+![Screen Shot 2019-01-25 at 18.22.12](//images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
 
 La información describe la siguiente información de interfaz:
 
@@ -221,7 +221,7 @@ Es hora de visitar el archivo blocks.json de Dreamstore y entender cómo todo el
 
 ### Estructurando y configurando nuestra tienda con el `StoreBuilder`
 
-![Codigo voando blocks.mp4](https://images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
+![Codigo voando blocks.mp4](//images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
 
 Abra `/ blocks.json` y encuentre nuestro ya conocido `store.home`. Vamos a empezar analizando el primer bloque dentro de `store.home : carrossel#home`.
 
@@ -244,12 +244,12 @@ Es fácil ver cuán poderoso el constructor de tiendas puede ser cuando añadimo
   ```
 
 ### Estilizando nuestra tienda con el `StylesBuilder`
-![StyleBuilder.mp4](https://images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
+![StyleBuilder.mp4](//images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
 
 
 El StylesBuilder es simple de entender porque toma su archivo styles.json durante el build y utiliza el generador de [Tachyons](https://tachyons.io/) para producir el CSS de su tienda.
 
 Diseñamos el StylesBuilder para ser extremadamente intuitivo y autoexplicativo. Es tan simple como ajustar los códigos hexadecimales adecuadamente y ver los resultados en toda la tienda.
 
-![Screen Shot 2019-01-28 at 00.40.17](https://images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
+![Screen Shot 2019-01-28 at 00.40.17](//images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
 
diff --git a/docs/tutorials/es/understanding-the-additional-shipping-cost.md b/docs/tutorials/es/understanding-the-additional-shipping-cost.md
index 1d8148448..960517ad1 100644
--- a/docs/tutorials/es/understanding-the-additional-shipping-cost.md
+++ b/docs/tutorials/es/understanding-the-additional-shipping-cost.md
@@ -28,7 +28,7 @@ Existen tres formas de agregar un valor extra sobre el flete: valor adicional po
 
 El valor adicional por precio se calcula a partir del precio del producto. Se define un porcentaje que se aplicará al precio de este, y ese valor resultante se agrega al valor del flete inicialmente calculado.
 
-![adicionalfrete1 ES](https://images.ctfassets.net/alneenqid6w5/7iLxQxdxAWMcm22yieiyc0/310afec9d0940032a726e33b47e490d4/adicionalfrete1_ES.png)
+![adicionalfrete1 ES](//images.ctfassets.net/alneenqid6w5/7iLxQxdxAWMcm22yieiyc0/310afec9d0940032a726e33b47e490d4/adicionalfrete1_ES.png)
 
 En el caso anterior, el valor de los productos totaliza $ 80,00 y el valor registrado como __Valor adicional__ es de 10%. Es así que, el valor calculado que se agrega al valor del flete es de $ 8,00. La suma del valor final del flete y el valor adicional es de $18,00.
 
@@ -44,7 +44,7 @@ El valor adicional por peso se calcula con base en el peso del producto. Este ca
 
 El cálculo es el siguiente:
 
-![adicionalfrete2 ES](https://images.ctfassets.net/alneenqid6w5/2bPpmLHucko8eGOEMUKEsQ/52029655a5f69fd3f358f780a3f89cc3/adicionalfrete2_ES.png)
+![adicionalfrete2 ES](//images.ctfassets.net/alneenqid6w5/2bPpmLHucko8eGOEMUKEsQ/52029655a5f69fd3f358f780a3f89cc3/adicionalfrete2_ES.png)
 
 Es decir, en el ejemplo, la diferencia del valor mínimo del rango de peso registrado y el peso del producto es de 100 gramos. El valor registrado en el campo __Valor adicional por peso__ es de 0,1. Entonces, el valor que debe agregarse al cálculo es de 14,00. El valor final sería $ 24,00.
 
@@ -58,7 +58,7 @@ Revise nuestra documentación sobre [cómo montar la plantilla de flete](https:/
 
 Este valor adicional se calcula sobre el valor final del flete, y no sobre el valor del producto. El valor porcentual es lo último que se calcula en el flete.
 
-![adicionalfrete3 ES](https://images.ctfassets.net/alneenqid6w5/7oQJz0N7qMuqyCWWm02KS6/3d1fceaaae7a96a930b81fa304dcc128/adicionalfrete3_ES.png)
+![adicionalfrete3 ES](//images.ctfassets.net/alneenqid6w5/7oQJz0N7qMuqyCWWm02KS6/3d1fceaaae7a96a930b81fa304dcc128/adicionalfrete3_ES.png)
 
 En ese caso, el valor ingresado en el campo __Valor adicional__ será el valor porcentual que debe sumarse al valor final calculado del flete. Por ejemplo: si el flete, con todos sus valores adicionales ya calculados totaliza $20,00 y el valor registrado en el campo Adicional en los Fletes es 10, significa que se añadirán $2,00 a los $20,00 del flete, totalizando $ 22,00 que se cobrarán al cliente por el flete. Esa es una manera simple de lograr un margen sobre los fletes de las compras.
 
diff --git a/docs/tutorials/es/understanding-the-cubic-weight-factor.md b/docs/tutorials/es/understanding-the-cubic-weight-factor.md
index b19d9c580..ae0aca52a 100644
--- a/docs/tutorials/es/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/es/understanding-the-cubic-weight-factor.md
@@ -1,10 +1,10 @@
 ---
-title: 'Calcular el factor cúbico de peso'
+title: 'Calcular el factor volumétrico de peso'
 id: tutorials_128
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:52.970Z
-updatedAt: 2022-11-08T19:15:57.550Z
-publishedAt: 2022-11-08T19:15:57.550Z
+updatedAt: 2023-12-19T17:17:26.713Z
+publishedAt: 2023-12-19T17:17:26.713Z
 firstPublishedAt: 2017-04-27T23:00:44.419Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,7 +15,7 @@ legacySlug: como-se-calcula-el-peso-cubico
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-El factor cúbico servirá para calcular un nuevo peso del paquete. Este nuevo peso tomará en consideración además del peso de los productos, su volumen. Esto es necesario para que el precio a ser cobrado por el flete tenga una relación justa entre peso y volumen ocupados.
+El factor de peso volumétrico servirá para calcular un nuevo peso del paquete. Este nuevo peso tomará en consideración además del peso de los productos, su volumen. Esto es necesario para que el precio a ser cobrado por el flete tenga una relación justa entre peso y volumen ocupados.
 
 ## Cubicación
 
@@ -23,42 +23,42 @@ El cubicación es la relación existente entre el volumen y el peso de la mercan
 
 La función de la cubicación en el transporte es evitar que se ocupe todo el espacio físico del vehículo sin utilizar toda su capacidad en peso o viceversa. De esta forma, el concepto de cubicación está ligado a la capacidad de llenar la carga de un vehículo utilizando todo su volumen disponible para carga y capacidad de peso o tonelaje.
 
-- __Peso real:__ es el indicado en la balanza.
-- __Peso Cúbico:__ es la forma de cálculo que determina el espacio efectivamente ocupado por el paquete en el vehículo de transporte.
+- __Peso mínimo:__ es el indicado en la balanza.
+- __Peso volumétrico:__ es la forma de cálculo que determina el espacio efectivamente ocupado por el paquete en el vehículo de transporte.
 
-## Factor Cúbico
+## Factor volumétrico
 
 Es el coeficiente resultante de la relación entre peso y volumen más adecuada y comercialmente justa al cubaje de aeronaves, según lo recomendado por la IATA (entidad internacional que congrega a las compañías aéreas).
 
 ## Cálculo
 
-El cálculo del peso cúbico se realiza efectuando la multiplicación de la Longitud x Anchura X Altura y división por el factor cúbico proporcionado por la trasportadora.
+El cálculo del peso volumétrico se realiza efectuando la multiplicación de la Longitud x Anchura X Altura y división por el factor volumétrico proporcionado por la trasportadora.
+
+<div class="alert alert-warning">
+Al calcular el factor de peso volumétrico, la plataforma VTEX no utiliza unidades de medida y los números generados son absolutos. Por lo tanto, los números y medidas que tengas en cuenta serán los del resultado final. Vale la pena señalar que la unidad de medida utilizada en su cálculo debe ser la misma utilizada por la transportadora.
+</div>
 
 Vea el ejemplo siguiente:
 
-![](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
+![example_cubic_weight_es](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
 
 - __Dimensiones del paquete:__ `50cm x 60cm x 15cm`
-- __Peso real del paquete:__ `9kg`
-- __Factor cúbico:__ `6.000`
-- __Peso cúbico:__ `50cm * 60cm * 15cm / 6.000 = 7,5kg`
+- __Peso mínimo del paquete:__ `9kg`
+- __Factor volumétrico:__ `6.000`
+- __Peso volumétrico:__ `50cm * 60cm * 15cm / 6.000 = 7,5kg`
 
-Al comparar el peso real con el peso cúbico del paquete, el transportista hará el cobro por el peso real, pues es mayor que el peso cubierto.
+Al comparar el peso mínimo con el peso volumétrico del paquete, el transportista hará el cobro por el peso mínimo, pues es mayor que el peso cubierto.
 
-Sin embargo, el cálculo anterior es sólo ilustrativo. En el transportista, el valor registrado como factor cúbico será multiplicado al producto de `Longitud x Anchura x Altura`. Es decir, el cálculo a realizar será `Longitud x Anchura x Altura x Factor Cúbico`
+Sin embargo, el cálculo anterior es sólo ilustrativo. En el transportista, el valor registrado como factor volumétrico será multiplicado al producto de `Longitud x Anchura x Altura`. Es decir, el cálculo a realizar será `Longitud x Anchura x Altura x Factor volumétrico`
 
-O sea, si el valor ofrecido por su compañía es `6.000`, es necesario realizar el cálculo donde este valor dividirá 1.000: Ejemplo: `1.000 / 6.000 = 0,167`.
+O sea, si el valor ofrecido por su compañía es `6.000`, es necesario realizar el cálculo donde este valor dividirá 1.000: Ejemplo: `1000g/6000 cm³ = 0,167`.
 
-Al realizar el registro de su transportista, ese es el valor que usted debe llenar en el campo __Factor Cúbico de Peso__:
+Ese es el valor que usted debe llenar en el campo Factor de peso volumétrico en su [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![peso cubico es](//images.contentful.com/alneenqid6w5/4Z0zLrnCHuKSKyoE8wGgMa/6239feb2d9610b12d19747732fae508e/peso_cubico_es.png)
+![cubic_weight_ES](//images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/034836d577be3c7f920c2b195b255adb/cubic_weight_ES.png)
 
 Por lo tanto, el cálculo final sería:
 
 - __Dimensiones del paquete:__ `50cm x 60cm x 15cm`
-- __Peso real del paquete:__ `9kg`
-- __Peso cúbico:__ `50cm x 60cm x 15cm x 0,167 = 7.515kg`
-
-<div class="alert alert-info">
-  <p>Compruebe con su transportista si la unidad de medida está en gramos, que es la unidad utilizada en VTEX.</p>
-</div>
+- __Peso mínimo del paquete:__ `9kg`
+- __Peso volumétrico:__ `50cm x 60cm x 15cm x 0,167 = 7.515kg`
diff --git a/docs/tutorials/es/understanding-the-message-center.md b/docs/tutorials/es/understanding-the-message-center.md
index 950b98c0d..e5dd14eba 100644
--- a/docs/tutorials/es/understanding-the-message-center.md
+++ b/docs/tutorials/es/understanding-the-message-center.md
@@ -31,7 +31,7 @@ Entienda la información que trae cada _card_ de plantilla :
 
 Para facilitar la navegación, la interfaz pone a disposición, además del campo de búsqueda por texto libre, filtros por aplicaciones (módulos) y tipo (mensaje estándar o personalizado/modificado).
 
-![busca-templates-central-mensagens es](https://images.ctfassets.net/alneenqid6w5/7LOOmw6SWIaY0SQO28Oc2k/b5b9e138dd014e087d34d75a57c96bf2/busca-templates-central-mensagens_es.png)
+![busca-templates-central-mensagens es](//images.ctfassets.net/alneenqid6w5/7LOOmw6SWIaY0SQO28Oc2k/b5b9e138dd014e087d34d75a57c96bf2/busca-templates-central-mensagens_es.png)
 
 Después de entender lo básico sobre los templates, usted ya puede ver cómo editarlos. Este paso no es obligatorio, pues VTEX suministra un layout básico y responsivo para todos los mensajes, con los datos necesarios para una buena comunicación con su cliente, pero es natural que las tiendas los adapten al estándar de comunicación ya usado para la marca.
 
diff --git a/docs/tutorials/es/understanding-the-price-change-rule.md b/docs/tutorials/es/understanding-the-price-change-rule.md
index 0809587ac..f484d4ad2 100644
--- a/docs/tutorials/es/understanding-the-price-change-rule.md
+++ b/docs/tutorials/es/understanding-the-price-change-rule.md
@@ -26,6 +26,6 @@ Este bloqueo se realiza también para todas las demás formas de alteración del
 
 El porcentaje de limite de precio puede ser retirado o reformulado en la pestaña __Configuración__ del módulo __Precios__. 
 
-![trava-variação-preço es](https://images.ctfassets.net/alneenqid6w5/7Gl4ECosVim4Si8GweU00e/6344add1a28b426b43f8af0219473fb0/trava-varia____o-pre__o_es.png)
+![trava-variação-preço es](//images.ctfassets.net/alneenqid6w5/7Gl4ECosVim4Si8GweU00e/6344add1a28b426b43f8af0219473fb0/trava-varia____o-pre__o_es.png)
 
 Algunos marketplaces también utilizan este límite de variación de precios. Si desea cambiar los precios más allá de los límites configurados, basta ponerse en contacto con el marketplace solicitando el cambio.
diff --git a/docs/tutorials/es/understanding-the-security-report.md b/docs/tutorials/es/understanding-the-security-report.md
index aec905227..9c6096acd 100644
--- a/docs/tutorials/es/understanding-the-security-report.md
+++ b/docs/tutorials/es/understanding-the-security-report.md
@@ -31,7 +31,7 @@ Es posible filtrarlo de diversas formas, a partir de las casillas abajo, conside
 
 En el ejemplo abajo hago el filtro para una alteración (ya sea creación o actualización) de precio de un SKU. Para eso, utilicé las casillas “Datos” con el Id del SKU, “Pantalla” con el lugar de la plataforma donde ocurre esa alteración y un período de tiempo específico. De acuerdo con el informe que se desea, puede ser necesario utilizar otras casillas en conjunto o en sustitución a esos que utilizo en el ejemplo.
 
-![relatorioseguran aPT.gif h 250?h=250](https://images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/bfa1170fd5dbf3fe62f736a136db18b5/relatorio-seguranca-es.gif)
+![relatorioseguran aPT.gif h 250?h=250](//images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/bfa1170fd5dbf3fe62f736a136db18b5/relatorio-seguranca-es.gif)
 
 ## Campos disponibles para el filtro
 
diff --git a/docs/tutorials/es/understanding-the-topbar.md b/docs/tutorials/es/understanding-the-topbar.md
index 751f00ba6..91b3f0e95 100644
--- a/docs/tutorials/es/understanding-the-topbar.md
+++ b/docs/tutorials/es/understanding-the-topbar.md
@@ -19,17 +19,17 @@ La topbar es el punto de partida para todas las áreas del admin VTEX. A continu
 
 **Navegue entre los módulos**: Para ir a uno de los módulos, basta hacer clci sobre él en la sidebar del Admin.
 
-![paginainicial.es](https://images.ctfassets.net/alneenqid6w5/207OIMwxY2Ilv2GgkiYWEj/05adb8d83d4038462a72912363e3ccd2/paginainicial.es.png)
+![paginainicial.es](//images.ctfassets.net/alneenqid6w5/207OIMwxY2Ilv2GgkiYWEj/05adb8d83d4038462a72912363e3ccd2/paginainicial.es.png)
 
 **Navegue entre los sub-dominios**: Para navegar entre los sub-dominios de su tienda, basta hacer clic sobre el dominio actual. Usted visualizará todas las opciones. Para ir al admin de uno de los sub-dominios, basta hacer clic sobre él en el menú.
 
-![subdominios.es](https://images.ctfassets.net/alneenqid6w5/61YQjUjUfJWRKgjHmnkpUc/883631d0aeadce6b51dc08d537d9ce70/subdominios.es.png)
+![subdominios.es](//images.ctfassets.net/alneenqid6w5/61YQjUjUfJWRKgjHmnkpUc/883631d0aeadce6b51dc08d537d9ce70/subdominios.es.png)
 
 **Seleccione el idioma de admin**: Para seleccionar el idioma, basta hacer clic sobre el icono de idioma y seleccionar el idioma deseado.
-![idioma.es](https://images.ctfassets.net/alneenqid6w5/axPKcMoKDJRxAqIn0QF8J/7d30ce95cfd5211a8db2dd606e4e737b/idioma.es.png)
+![idioma.es](//images.ctfassets.net/alneenqid6w5/axPKcMoKDJRxAqIn0QF8J/7d30ce95cfd5211a8db2dd606e4e737b/idioma.es.png)
 
 **Acceda a nuestras bases de conocimiento**: Para acceder a una de nuestras bases, haga clic sobre su perfil de soporte y seleccione el lugar al que desea acceder, haciendo clic sobre él.
-![support.es](https://images.ctfassets.net/alneenqid6w5/4M9na7OVRQqq68D9AUeV80/12751ce1d4656b7081e4be98bd7ea1c7/support.es.png)
+![support.es](//images.ctfassets.net/alneenqid6w5/4M9na7OVRQqq68D9AUeV80/12751ce1d4656b7081e4be98bd7ea1c7/support.es.png)
 
 
 **Haga el logoff**: Para realizar el logoff, basta hacer clic sobre su nombre y hacer clic sobre el link **Sair**.
diff --git a/docs/tutorials/es/understanding-the-updating-of-the-xml.md b/docs/tutorials/es/understanding-the-updating-of-the-xml.md
index 556988c6d..f7aa1130b 100644
--- a/docs/tutorials/es/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/es/understanding-the-updating-of-the-xml.md
@@ -3,8 +3,8 @@ title: 'Cómo se hace la actualización del XML'
 id: tutorials_297
 status: PUBLISHED
 createdAt: 2017-04-27T22:09:31.811Z
-updatedAt: 2019-12-31T15:28:59.361Z
-publishedAt: 2019-12-31T15:28:59.361Z
+updatedAt: 2024-02-29T14:57:59.233Z
+publishedAt: 2024-02-29T14:57:59.233Z
 firstPublishedAt: 2017-04-27T23:03:14.354Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/es/understanding-vtexs-email-capture-system.md b/docs/tutorials/es/understanding-vtexs-email-capture-system.md
index af53021b1..52012a368 100644
--- a/docs/tutorials/es/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/es/understanding-vtexs-email-capture-system.md
@@ -3,8 +3,8 @@ title: 'Captura de email'
 id: 15oNhcDa7HA8ztfJnpvhmJ
 status: PUBLISHED
 createdAt: 2022-10-17T19:51:45.533Z
-updatedAt: 2022-10-17T19:55:21.831Z
-publishedAt: 2022-10-17T19:55:21.831Z
+updatedAt: 2023-07-20T17:49:29.730Z
+publishedAt: 2023-07-20T17:49:29.730Z
 firstPublishedAt: 2022-10-17T19:53:55.523Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: entendiendo-el-sistema-de-captura-de-email-de-vtex
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
-El propósito de este artículo es mostrar cómo se recibe el correo electrónico de un usuario en el [Master Data CRM](https://help.vtex.com/es/subcategory/visao-geral-do-master-data--5gtjaqCG7eIseyCI0aSqc2#). Para ello, se demostrará cómo **Checkout**, **RC.JS** y **Master Data** trabajan en conjunto para capturar la información de correo electrónico de un nuevo usuario.
+El propósito de este artículo es mostrar cómo se recibe el correo electrónico de un usuario en el [Master Data CRM](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). Para ello, se demostrará cómo **Checkout**, **RC.JS** y **Master Data** trabajan en conjunto para capturar la información de correo electrónico de un nuevo usuario.
 
 Para una mejor comprensión, presentaremos un escenario (dividido en 3 pasos), donde el usuario completa con éxito su compra y el pedido se reenvía a OMS, mientras que su correo electrónico se transmite de forma segura a Master Data. En este contexto, las acciones del usuario y el flujo de la plataforma ocurren en el siguiente orden:
 
@@ -51,5 +51,5 @@ Para que se pueda utilizar la función <a href="https://help.vtex.com/es/tutoria
 Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
 </div>
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/tutorials/es/untitled-entry-2024-03-13-at-16-25-15.md b/docs/tutorials/es/untitled-entry-2024-03-13-at-16-25-15.md
new file mode 100644
index 000000000..4663c7cf3
--- /dev/null
+++ b/docs/tutorials/es/untitled-entry-2024-03-13-at-16-25-15.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 4GN2eQe58qKvEaLA4u7Cl8
+status: DRAFT
+createdAt: 2024-03-13T16:25:15.804Z
+updatedAt: 2024-03-13T16:25:21.748Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: 
+author: 
+slug: untitled-entry-2024-03-13-at-16-25-15
+locale: es
+legacySlug: untitled-entry-2024-03-13-at-16-25-15
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/es/untitled-entry-2024-07-25-at-21-25-31.md b/docs/tutorials/es/untitled-entry-2024-07-25-at-21-25-31.md
new file mode 100644
index 000000000..8a6c1e44a
--- /dev/null
+++ b/docs/tutorials/es/untitled-entry-2024-07-25-at-21-25-31.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 3eu2vU8e9uMF7eNHJMHcYU
+status: DRAFT
+createdAt: 2024-07-25T21:25:31.372Z
+updatedAt: 2024-07-25T21:25:33.666Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: 
+author: 
+slug: untitled-entry-2024-07-25-at-21-25-31
+locale: es
+legacySlug: untitled-entry-2024-07-25-at-21-25-31
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md b/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md
index 5f2dd6afa..c6cb9209c 100644
--- a/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md
+++ b/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md
@@ -45,7 +45,7 @@ _Unidades disponibles = unidades de la última actualización - unidades reserva
 
 El stock negativo suele producirse cuando se cancela el SKU de un pedido que ya tiene una reserva.  Para evitar esta situación, es importante que la actualización de la cantidad de SKU se realice en pedidos con _status_ posterior a `Preparando entrega`. De este modo, la [reserva ya habrá sido reconocida](https://help.vtex.com/es/tutorial/como-se-maneja-la-reserva--tutorials_92#reserva-reconocida) y no habrá conflicto entre los ítems en stock y los ítems que realmente están disponibles para la venta.
 
-![gerenciar inventarioES](https://images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/51be4f67a41cec8ee04d4772d94a735e/gerenciar_inventarioES.gif)
+![gerenciar inventarioES](//images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/51be4f67a41cec8ee04d4772d94a735e/gerenciar_inventarioES.gif)
 
 ## Artículos relacionados
 
diff --git a/docs/tutorials/es/using-recaptcha-at-checkout.md b/docs/tutorials/es/using-recaptcha-at-checkout.md
index 3307ffb34..f18b1f8a9 100644
--- a/docs/tutorials/es/using-recaptcha-at-checkout.md
+++ b/docs/tutorials/es/using-recaptcha-at-checkout.md
@@ -3,8 +3,8 @@ title: 'reCAPTCHA en el checkout'
 id: 18Te3oDd7f4qcjKu9jhNzP
 status: PUBLISHED
 createdAt: 2021-08-03T12:53:12.155Z
-updatedAt: 2023-03-21T17:52:28.440Z
-publishedAt: 2023-03-21T17:52:28.440Z
+updatedAt: 2023-12-11T22:07:06.233Z
+publishedAt: 2023-12-11T22:07:06.233Z
 firstPublishedAt: 2021-08-03T13:51:19.441Z
 contentType: tutorial
 productTeam: Others
@@ -17,15 +17,15 @@ subcategory: 3shmvletqbB206RqbY2vYQ
 
 reCAPTCHA es una solución utilizada para la validación de usuarios reales en pedidos que se pagarán con tarjetas de crédito o débito. Prevé situaciones en que se utilizan programas maliciosos para cometer fraude, ya que impide el acceso de usuarios falsos. 
 
-Para proporcionar mayor seguridad, VTEX proporciona [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) checkbox e indica a los clientes que lo habiliten para proteger la creación y el pago de pedidos. Esta versión de reCAPTCHA está optimizada y el usuario solo tiene que hacer clic en la casilla; solo verá el desafío de validación si Google desconfía del usuario.
+Recomendamos su activación para proteger la creación y el pago de pedidos en tu tienda.
 
- El requisito de reCAPTCHA seguirá la opción configurada por la tienda a través de la [API de configuración del checkout](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm)_<span style="text-decoration:underline;">.</span>_ Para saber más sobre la activación, consulte este artículo sobre el [uso de reCAPTCHA para integraciones](https://developers.vtex.com/vtex-rest-api/docs/recaptcha).
+El requisito de reCAPTCHA seguirá la opción configurada por la tienda a través de la [API de configuración del checkout](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm). Para saber más sobre la activación, consulte este artículo sobre el [uso de reCAPTCHA para integraciones](https://developers.vtex.com/vtex-rest-api/docs/recaptcha).
 
 Antes de la activación, es importante tener en cuenta lo siguiente:
 
 * **Adaptación de la interfaz:** al activar la funcionalidad es necesario adaptar la interfaz (web y móvil) que crea pedidos en la cuenta de su tienda (si no realiza este paso, la creación de pedidos se verá afectada). Vea más información sobre cómo adaptar la interfaz con la [guía de reCAPTCHA para integraciones](https://developers.vtex.com/vtex-rest-api/docs/recaptcha).
 * **Consecuencias para la cuenta:** habilitar la funcionalidad implica el uso en la cuenta completa, esto incluye el uso en todas las tiendas y subcuentas.
-* **Pruebas:** para probar la funcionalidad debe utilizar un [entorno beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) y utilizar [Checkout v6](https://help.vtex.com/es/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH). 
+* **Pruebas:** para probar la funcionalidad sin afectar tu tienda en producción debe utilizar un [entorno beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) con [Checkout v6](https://help.vtex.com/es/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH). 
 
 ## Regla de aplicación
 
@@ -35,20 +35,51 @@ La opción recomendada por VTEX es [VTEX Criteria](https://developers.vtex.com/d
 
 La intención es minimizar el uso del desafío (para optimizar la experiencia del usuario) y al mismo tiempo aplicar la protección necesaria. Las sesiones que se consideran confiables están exentas de reCAPTCHA. Por lo tanto, reCAPTCHA solo se activa en sesiones potencialmente maliciosas.
 
-## Experiencia de compra con VTEX Criteria
+## Versiones de reCAPTCHA
+
+VTEX está integrado con reCAPTCHA enterprise, que ofrece dos enfoques de validación: checkbox (equivalente a [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display)) y basada en puntuación (equivalente a [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3)). Consulta la siguiente tabla para saber qué versión se aplica a tu operación.
+
+| **Características de la tienda**        | **Versión de reCAPTCHA** |
+|-----------------------------------------|--------------------------|
+| Storefront nativo VTEX                  | Checkbox (v2)                       |
+| Storefront propio para web              | Checkbox (v2) o Basada en puntuación (v3)                  |
+| Storefront propio para aplicación móvil | Basada en puntuación (v3)                         |
+
+## reCAPTCHA v2
+
+Puedes utilizar reCAPTCHA checkbox (v2). Es decir, cuando corresponda, el usuario únicamente deberá hacer clic en la <i class="far fa-check-square"></i> _(casilla de verificación),_ y solo se le presentará el desafío de validación si Google sospecha del usuario. A continuación puedes consultar más información sobre la experiencia de compra.
+
+### Experiencia de compra con VTEX Criteria y reCAPTCHA v2
 
 Teniendo en cuenta los factores mencionados anteriormente, la experiencia de compra con tarjeta de débito o crédito suele seguir el flujo a continuación. Esto minimiza la incidencia de algunos tipos de fraude y ataques con una fricción mínima para el usuario.
 
-![reCAPTCHA scenariosES](https://images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/596d96e2fd5ba06a1c390dc9d8d0ca68/reCAPTCHA_scenarios__2_.jpg)
+![reCAPTCHA scenariosES](//images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/596d96e2fd5ba06a1c390dc9d8d0ca68/reCAPTCHA_scenarios__2_.jpg)
 Como se ilustra en la imagen anterior, hay varios resultados posibles en este flujo:
 
 1. Si el algoritmo de VTEX Criteria no clasifica la sesión como sospechosa, la plataforma sigue con la compra de forma normal.
 
 2. De lo contrario, la interfaz debe mostrar la casilla de reCAPTCHA, que el cliente debe marcar. Si el reCAPTCHA no clasifica el comportamiento al marcar la casilla como sospechoso, la compra sigue de forma normal.
 
-![newCaptchaAnchor](https://images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/9b8cf067c590a48d2560e9a170fa2022/newCaptchaAnchor.gif)
+![newCaptchaAnchor](//images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/9b8cf067c590a48d2560e9a170fa2022/newCaptchaAnchor.gif)
 3. Si el reCAPTCHA clasifica el comportamiento como sospechoso, la interfaz mostrará el desafío.
 
-![desafio recaptcha](https://images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/e820adf7252e86a94e79fc72eae1f536/desafio_recaptcha.png)
+![desafio recaptcha](//images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/e820adf7252e86a94e79fc72eae1f536/desafio_recaptcha.png)
 4. Si el desafío se resuelve con éxito, la plataforma sigue con la compra. Si no, el comportamiento se clasifica como compatible con un _bot_ y la plataforma no finaliza la compra.
 
+## reCAPTCHA v3
+
+reCAPTCHA basada en puntuación ([v3](https://developers.google.com/recaptcha/docs/v3)) no interrumpe la experiencia del usuario en tu tienda. Analiza si las interacciones en el sitio web son sospechosas y devuelve una puntuación entre `1.0` (lo más probable es que se trate de una interacción normal) y `0.0` (lo más probable es que sea un bot).
+
+Al configurar reCAPTCHA v3 para tu tienda VTEX, tienes la opción de establecer una puntuación mínima para [cada clave registrada](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#getting-the-recaptcha-key-for-mobile-implementations) y una [puntuación mínima para tu tienda](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#recaptcha-v3-score). Los valores posibles son `0.1`, `0.3`, `0.7` y`0.9`. 
+
+La prioridad de aplicación de la puntuación mínima para una compra determinada es:
+
+```
+Puntuación de la clave > Puntuación de la cuenta > Puntuación predeterminada VTEX (0.7)
+```
+
+Esto significa que si estableces puntuaciones mínimas para tu clave y tu cuenta, se aplicará la puntuación de la clave. Sin embargo, si no estableces ninguna puntuación, VTEX aplicará el valor predeterminado `0.7`.
+
+Las interacciones que devuelvan un valor inferior al mínimo aplicable no podrán finalizar la compra.
+
+Para configurar reCAPTCHA y establecer puntuaciones mínimas de claves o cuentas, ponte en contacto con tu equipo de desarrolladores y consulta la guía [integración con reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
diff --git a/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index be09dedba..9e11469bc 100644
--- a/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -43,7 +43,7 @@ Apps que tienen una dependencia de sesión monitorean cambios en sus entradas y
 
 Transforms frecuentemente disparan otros transforms, repitiendo hasta que ninguna actualización de parámetro adicional sea enviada por apps. Esta operación es, por supuesto, cuidadosamente monitoreada para evitar condiciones de loop. El siguiente diagrama ilustra un ejemplo de un ciclo de transform:
 
-![EN - Session Manager](https://images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
+![EN - Session Manager](//images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
 
 1. Se realizó un cambio en el parámetro de sesión X
 2. App A monitoreaba el parámetro de sesión X, lo que disparó el Transform 1
diff --git a/docs/tutorials/es/using-the-project-task-timeline.md b/docs/tutorials/es/using-the-project-task-timeline.md
index e415b11f5..8d044061e 100644
--- a/docs/tutorials/es/using-the-project-task-timeline.md
+++ b/docs/tutorials/es/using-the-project-task-timeline.md
@@ -1,10 +1,10 @@
 ---
 title: 'Utilizar el cronograma de tareas en su proyecto'
 id: tutorials_1864
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:55:58.397Z
-updatedAt: 2019-12-31T15:21:08.316Z
-publishedAt: 2019-12-31T15:21:08.316Z
+updatedAt: 2024-03-11T13:20:50.510Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:51.067Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/validating-your-store-and-uploading-it-for-production.md b/docs/tutorials/es/validating-your-store-and-uploading-it-for-production.md
index c977cbf0b..38ec7d7e2 100644
--- a/docs/tutorials/es/validating-your-store-and-uploading-it-for-production.md
+++ b/docs/tutorials/es/validating-your-store-and-uploading-it-for-production.md
@@ -1,10 +1,10 @@
 ---
 title: 'Validar la tienda para subir para producción'
 id: tutorials_1419
-status: CHANGED
+status: DRAFT
 createdAt: 2017-04-27T21:56:14.582Z
-updatedAt: 2022-06-01T20:06:41.976Z
-publishedAt: 2019-12-31T15:29:01.968Z
+updatedAt: 2023-07-25T21:07:26.780Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:49.725Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/es/via-inventory-integration-errors.md b/docs/tutorials/es/via-inventory-integration-errors.md
index a4d84443d..06d11bdb3 100644
--- a/docs/tutorials/es/via-inventory-integration-errors.md
+++ b/docs/tutorials/es/via-inventory-integration-errors.md
@@ -3,8 +3,8 @@ title: 'Errores de integración de stock con Via'
 id: 2jzz4Ip0M2BDzwslEtCzPc
 status: PUBLISHED
 createdAt: 2021-10-26T23:55:47.528Z
-updatedAt: 2023-03-29T14:41:26.271Z
-publishedAt: 2023-03-29T14:41:26.271Z
+updatedAt: 2023-11-30T21:50:54.362Z
+publishedAt: 2023-11-30T21:50:54.362Z
 firstPublishedAt: 2021-10-27T00:08:05.224Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md b/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md
index 419115717..d5c964ae0 100644
--- a/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md
+++ b/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md
@@ -17,7 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 La *Configuración del usuario* es el conjunto de configuraciones aplicadas a tu perfil personal en el Admin, y no están relacionadas con tu tienda o la cuenta de tu negocio en VTEX. Para acceder a esta página, haz clic en tu **avatar de perfil**, marcado con la inicial de tu email, y luego haz clic en el botón **Configuración del usuario**. 
 
-![Admin v4 User settings menu ES](https://images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/906a71481f7c64887b63187e9a1f2952/Admin_v4_User_settings_menu_ES.jpg)
+![Admin v4 User settings menu ES](//images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/906a71481f7c64887b63187e9a1f2952/Admin_v4_User_settings_menu_ES.jpg)
 
 En esta página, que pronto se incluirá en el diseño del Admin v4, puedes realizar las siguientes acciones:
 
diff --git a/docs/tutorials/es/vtex-ad-network-beta.md b/docs/tutorials/es/vtex-ad-network-beta.md
new file mode 100644
index 000000000..f7470595b
--- /dev/null
+++ b/docs/tutorials/es/vtex-ad-network-beta.md
@@ -0,0 +1,124 @@
+---
+title: 'VTEX Ad Network (Beta)'
+id: 2cgqXcBuJmXN2livQvClur
+status: CHANGED
+createdAt: 2024-04-23T17:38:07.378Z
+updatedAt: 2024-07-05T13:14:45.135Z
+publishedAt: 2024-07-05T13:13:03.955Z
+firstPublishedAt: 2024-04-23T19:11:42.313Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: vtex-ad-network-beta
+locale: es
+legacySlug: vtex-ad-network-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+**VTEX Ad Network** conecta a retailers VTEX con marcas interesadas en anunciar sus productos. Con esta conexión, anunciantes y retailers VTEX pueden impulsar su negocio:
+
+- **Anunciantes:** marcas que pueden crear campañas de anuncios para promocionar productos en storefronts de tiendas VTEX que tengan esos mismos productos en sus catálogos, incrementando las ventas.
+- **Retailers:** son retailers que tienen tiendas VTEX que pueden ofrecer espacios en sus storefronts para que los anunciantes promocionen sus productos. Estos retailers recibirán una valor por cada clic recibido en anuncios de su tienda.
+
+## Campañas
+
+Una campaña de **VTEX Ad Network** tiene las siguientes características:
+
+- Productos promocionados.
+- Presupuesto total.
+- Oferta, que es el costo por clic (CPC), es decir, el valor que el anunciante está dispuesto a pagar por cada clic recibido en el anuncio. Este valor también determina la [prioridad de diferentes anuncios](#priorizacion-de-anuncios) para el mismo espacio de visualización. Este valor se define por producto.
+- Duración.
+- Cobertura, que determina si la campaña se desarrollará en toda la red de Ad Network o en tiendas específicas.
+
+Al crear una campaña, el anunciante define uno o varios códigos EAN (códigos de barras) asociados a los productos que desea promocionar. De esta forma, VTEX podrá mostrar estos anuncios en todas las tiendas que vendan ese producto y que se hayan adherido a **VTEX Ad Network**. O, si lo prefiere, el anunciante puede seleccionar en qué tiendas desea mostrar su campaña, de entre las posibles.
+
+## Formato del anuncio
+
+Actualmente, VTEX ofrece un único formato de anuncio: productos patrocinados. Esto significa que los productos promocionados por los anunciantes pueden aparecer en un lugar destacado en algunos contextos en los que hay listas de productos:
+
+- Resultados de búsqueda.
+- Páginas de categorías.
+
+Consulta a continuación un ejemplo del modo de exhibición de este formato:
+
+![vtex_ad_network_sponsored_ES](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/bfec823e3960cac69bf878395437cdec/vtex_ad_network_sponsored.png)
+
+Los retailers participantes en **VTEX Ad Network** podrán [configurar la cantidad de espacios para anuncios](https://help.vtex.com/es/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse#crear-campana) que disponibilizarán en cada uno de estos contextos en la tienda.
+
+## Priorización de anuncios
+
+Cada vez que un cliente navega a una página de una tienda que tiene espacio de anuncios disponible, **VTEX Ad Network** determina los anuncios que se mostrarán.
+
+Este proceso de priorización se desarrolla en tres etapas:
+
+#### 1. Selección
+
+- **VTEX Ad Network** tiene en cuenta el contexto de navegación del cliente, es decir, término de búsqueda, categoría o vitrina, y selecciona campañas que contienen productos que se ajustan a este contexto. La plataforma también considera una puntuación mínima de relevancia, para garantizar que solo se muestren anuncios que puedan interesar al cliente.
+- En esta etapa, VTEX también tiene en cuenta la compatibilidad desde el punto de vista de la [configuración de la campaña](#campanas), como cobertura y términos de búsqueda negativos.
+
+#### 2. Definición del presupuesto diario promedio
+
+- En esta etapa, VTEX pondera el presupuesto de las campañas, excluyendo las que no tienen presupuesto disponible y optimizando gastos en función de la probabilidad de clics y conversión.
+
+#### 3. Subasta
+
+- A partir de los candidatos seleccionados en las etapas anteriores, **VTEX Ad Network** determina los productos promocionados para ocupar los espacios disponibles.
+- La plataforma clasifica los anuncios en función de su oferta de costo por clic (CPC) y [nivel de calidad](#nivel-de-calidad).
+- También hay un factor aleatorio en el cálculo de la subasta para evitar sesgos. Por lo tanto, a medida que aumenta el valor del CPC y el nivel de calidad, aumenta la probabilidad de que un anuncio obtenga una mejor clasificación, aunque no hay garantía de que siempre sea así.
+
+Una vez determinados los anuncios que se muestran en la página, se determina el valor de las ofertas. La oferta ganadora de la subasta tendrá el valor final de la segunda mayor oferta más USD 0.01.
+
+<div class="alert alert-danger">
+Puede ocurrir que no se seleccione ningún anuncio con el proceso de priorización si no hay productos promocionados que se ajusten al contexto de navegación, a la cobertura de la tienda o que no tienen presupuesto disponible.
+</div>
+
+### Nivel de calidad
+
+El nivel de calidad de los anuncios es una medida que tiene en cuenta distintos criterios de evaluación e influye en la etapa de subasta en el proceso de [Priorización de anuncios](#priorizacion-de-anuncios). Cuanto más alto sea el nivel de calidad, más probabilidades habrá de que un determinado anuncio obtenga una buena clasificación en la subasta.
+
+### Ejemplo de priorización
+
+Considera los siguientes anuncios, de campañas diferentes, que compiten en una misma tienda.
+
+| **Anuncio** | **Producto** | **Nivel de calidad** | **Oferta** | **Presupuesto** |
+| :---: | :---: | :---: | :---: | :---: |
+| 1 | Perfume A | 10 % | 1.00 USD | 0 USD |
+| 2 | Perfume B | 1 % | 2.00 USD | 10 USD |
+| 3 | Perfume C | 10 % | 0.90 USD | 10 USD |
+| 4 | Champú A | 5 % | 0.50 USD | 10 USD |
+
+Por ejemplo, si un cliente de esta tienda accede a la página de la categoría **Perfumes**, que contiene 300 productos, el proceso de priorización sería el siguiente:
+
+1. En la etapa de redirección, la plataforma descarta el anuncio 4 porque no se ajusta al contexto de navegación del cliente.
+2. Al evaluar el ritmo, la plataforma descarta el anuncio 1, ya que este no tiene presupuesto disponible.
+3. En la subasta, el producto 3 tiene más posibilidades de ocupar el primer puesto, teniendo en cuenta la **Oferta** y el **Porcentaje de conversiones**.
+
+## Ventana de atribución
+
+La ventana de atribución de **VTEX Ad Network** es de 15 días. Esto significa que si un cliente hace clic en un anuncio de un producto y compra ese producto en los 15 días siguientes al clic, VTEX Ad Network atribuye esta venta al anuncio.
+
+Sin embargo, en caso de que el cliente lo compre después de este periodo, la venta no se atribuirá al anuncio.
+
+## Cómo formar parte de VTEX Ad Network
+
+Consulta a continuación cómo puedes formar parte de **VTEX Ad Network** ya sea como [retailer](#retailers) que muestra anuncios o como [anunciante](#anunciantes).
+
+### Retailers
+
+<div class="alert alert-warning">
+Por el momento, solamente tiendas desarrolladas con <a href="https://help.vtex.com/es/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> pueden ofrecer espacios para anuncios.
+</div>
+
+Para disponibilizar espacios para anuncios en tu tienda, debe ponerse en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar la instalación de la aplicación VTEX Ad Network para tiendas en su cuenta VTEX.
+
+Para saber más sobre las funcionalidades para tiendas, consulta el artículo [Mostrar anuncios con VTEX Ad Network en tu tienda (Beta)](https://help.vtex.com/es/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA).
+
+### Anunciantes
+
+Cualquier anunciante interesado en promocionar productos que ya se venden en las tiendas VTEX puede anunciar utilizando **VTEX Ad Network**. Para ello, debes ponerte en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar la instalación de la aplicación __VTEX Ad Network__ en tu cuenta VTEX.
+
+Aprende más sobre las funcionalidades disponibles para los anunciantes en el artículo [Anunciar con VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/advertising-with-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse).
diff --git a/docs/tutorials/es/vtex-admin-start-here.md b/docs/tutorials/es/vtex-admin-start-here.md
index f04f98e1d..c8ae6504e 100644
--- a/docs/tutorials/es/vtex-admin-start-here.md
+++ b/docs/tutorials/es/vtex-admin-start-here.md
@@ -3,8 +3,8 @@ title: 'Admin VTEX: Comience Aquí'
 id: 531cHtUCUi3puRXNDmKziw
 status: PUBLISHED
 createdAt: 2019-02-04T15:41:26.380Z
-updatedAt: 2023-05-24T18:06:55.015Z
-publishedAt: 2023-05-24T18:06:55.015Z
+updatedAt: 2024-07-03T11:18:48.914Z
+publishedAt: 2024-07-03T11:18:48.914Z
 firstPublishedAt: 2019-02-04T15:51:04.667Z
 contentType: tutorial
 productTeam: Others
@@ -12,13 +12,13 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: admin-vtex-comience-aqui
 locale: es
 legacySlug: encuentra-aqui-todas-las-respuestas-que-necesitas
-subcategory: 
+subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 ---
 
 El Admin VTEX permite a los administradores de la tienda gestionar todas sus experiencias de comercio digital en un solo lugar, de forma sencilla e inteligente. Aquí dan seguimiento a los pedidos, registran productos, configuran fulfillment y llevan a cabo los demás aspectos de una operación de comercio unificado.
 
 ## Página de inicio
-![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 La página de inicio proporciona una vista de alto nivel de tu tienda, como una cabina de mando para tus operaciones de comercio digital, y por eso se llama [Vista general](https://help.vtex.com/es/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -26,10 +26,17 @@ Una vez que accedas al Admin, verás métricas y gráficos útiles para monitore
 
 ## Menu de navegación  
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/6b08cbf42beadbe9f8d58e345285b93b/New_Admin_Shell__1_.png)
-
 Nuestros menús laterales de navegación y la barra superior agrupan categorías similares de forma más clara para reducir las distracciones y ayudar a tu equipo a encontrar lo que necesita más rápidamente. 
 
+![menu de navegación admin SEP2023](//images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/76b32915010a0dc372fe94ba378e690e/admin-navigation.png)
+
+Puede utilizar la barra de búsqueda global para buscar páginas en el Admin VTEX o pedidos de su tienda. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
+
+- ID del pedido
+- Nombre del cliente
+- Email del cliente
+- Documento del cliente
+
 Consulta nuestros artículos sobre la vista general de cada menú del Admin VTEX para conocer más sobre su función y las páginas que incluye:
 
 - [Dashboards](https://help.vtex.com/es/v4/docs/visao-geral-dashboards--3FA56jDSTQjuSDwJRYQihm)      
@@ -40,7 +47,7 @@ Consulta nuestros artículos sobre la vista general de cada menú del Admin VTEX
 - [Envío](https://help.vtex.com/es/v4/docs/visao-geral-envio--1hw1otLpTkIjQh4WiBTFYv)  
 - [Marketplace](https://help.vtex.com/es/v4/docs/visao-geral-marketplace--1MwABSIGjYSrFPUXhnUXiV)  
 - [Apps](https://help.vtex.com/es/v4/docs/apps-overview--Abz99oney4PUmrf7QcHc9)  
-- [Configuración de la tienda](https://help.vtex.com/es/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4)  
+- [Configuración de la tienda](https://help.vtex.com/es/tutorial/visao-geral-configuracoes-da-loja--6VtlMoid6iM9dP14X1CopT)  
 - [Configuración de la cuenta](https://help.vtex.com/es/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r)  
 - [Configuración del usuario](https://help.vtex.com/es/v4/docs/visao-geral-configuracoes-usuario--1qYAvOTZBVYMosJ7tQm3Ry)  
 - [Facturas](https://help.vtex.com/es/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC)  
@@ -51,13 +58,46 @@ También puedes utilizar la barra de búsqueda en la parte superior del Admin VT
 
 ### Centro de información
 
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/2a2b0054854d4b726fa4a502b6e3db52/Information_center.gif)
+![centro de información admin SEP2023](//images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/b1146f7ef7eec57f4f2a9c7a5f3e25c1/Information_center.gif)
 
 Allí hemos reunido todos los enlaces útiles de nuestro ecosistema VTEX para ayudarte a sacar el máximo partido a nuestra plataforma. Haciendo clic en el botón <i class='fa fa-question-circle-o'></i>  en la barra superior, puedes acceder a nuestro [Help Center](https://help.vtex.com), [Developer Portal](https://developers.vtex.com/), [Plataform Status](https://status.vtex.com/), [blog](https://vtex.com/es/blog/) y a las páginas de soporte.
 
+### Feedback en el Admin VTEX
+El botón Dar feedback permite al usuario compartir su opinión sobre su experiencia en la plataforma a través del Admin VTEX. Para hacerlo, sigue los pasos a continuación:
+1. Haz clic en el botón Centro de Información en la esquina superior derecha del Admin VTEX.
+2. Haz clic en la opción **Dar feedback**.
+
+Se abrirá un formulario de Google donde podrás enviar tus comentarios. Tras el envío, recibirás un email de confirmación.
+![Botão feedback - ES](//images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/38ed137e7d5d226361bee4ecd98a1f18/Bot_o_feedback_-_ES.gif)
+
+#### Formulario de feedback
+El objetivo principal de las preguntas presentes en el formulario de feedback es obtener información detallada sobre la experiencia y las percepciones con respecto al producto en el Admin VTEX.
+
+Esta información nos permite dirigir nuestros esfuerzos de desarrollo y soporte para satisfacer de manera más efectiva las necesidades de los usuarios.
+
+##### Descripción de los campos del formulario
+- **Email:** ingresa tu dirección de email.
+- **URL de la página del Admin:** ingresa la URL de la página del Admin relacionada con el feedback.
+
+Tipo de feedback (marca una o varias casillas): 
+- **Experiencia general:** describe la experiencia general con el producto.
+- **Funcionalidades:** proporciona comentarios sobre las funcionalidades del producto.
+- **Interfaz y usabilidad:** analiza la interfaz y la usabilidad.
+- **Traducción:** evalúa la traducción del contenido.
+- **Tiempo de carga:** evalúa el desempeño en términos de velocidad de carga.
+- **Otro:** campo disponible para agregar otro tipo de comentario no contemplado anteriormente.
+
+**Feedback:** comparte en este campo tu opinión sobre los productos y tipos de feedback seleccionados en las casillas anteriores del formulario.
+
+**Agregar captura de pantalla para ayudarnos a comprender mejor tu opinión:** campo opcional para adjuntar capturas de pantalla u otros documentos que faciliten la comprensión.
+
+<div class = "alert alert-info">
+Este proceso de feedback no debe utilizarse para abrir un ticket o solicitud de soporte técnico en VTEX.
+</div>
+
 ### Configuración de la cuenta y del usuario
 
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/c560ccf053bfcf4f127db55ec088f7f9/Avatar_settings.gif)
+![configuraciones de avatar admin SEP2023](//images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/bd3df394bdf8c173763d8df481cf3a52/Avatar_settings2.gif)
 
 El avatar de tu perfil reúne todas las configuraciones relacionadas con tu usuario y tu cuenta. A través del avatar, puedes acceder a la [Configuración del usuario](https://help.vtex.com/es/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), a la [Configuración de la cuenta](https://help.vtex.com/es/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), y a la información de las [Facturas](https://help.vtex.com/es/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC).  También puedes cambiar el idioma del Admin y cerrar la sesión.
 
@@ -77,7 +117,6 @@ El Admin VTEX ahora ofrece una experiencia localizada, que incluye las siguiente
 - Búlgaro
 
 ### Configuración de la tienda
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/b96a55b9faaffc3b604c74fa5a128d61/Store_settings.gif)
 
 Para esta experiencia, hemos reunido las configuraciones de todas las secciones del Admin en una pestaña específica: [Configuración de la tienda](https://help.vtex.com/es/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Gracias a esta mejora, puedes acceder fácilmente a todas las configuraciones que afectan a cada servicio de tu cuenta.
 
diff --git a/docs/tutorials/es/vtex-admin-start-here1.md b/docs/tutorials/es/vtex-admin-start-here1.md
index 67cb41ca0..9b17b7d58 100644
--- a/docs/tutorials/es/vtex-admin-start-here1.md
+++ b/docs/tutorials/es/vtex-admin-start-here1.md
@@ -18,7 +18,7 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 El Admin renovado permite a los comerciantes gestionar todas sus experiencias de comercio digital en un solo lugar, de forma sencilla e inteligente.
 
 ## Página de inicio
-![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 La página de inicio del admin ha sido rediseñada para proporcionar una visión general de alto nivel de tu tienda, como una cabina de mando para tus operaciones de comercio digital, y ahora se llama [Vista general](https://help.vtex.com/es/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -26,24 +26,24 @@ Una vez que accedas al Admin, verás métricas y gráficos útiles para monitore
 
 ## Navegación mejorada 
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/6b08cbf42beadbe9f8d58e345285b93b/New_Admin_Shell__1_.png)
+![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/6b08cbf42beadbe9f8d58e345285b93b/New_Admin_Shell__1_.png)
 
 Todo lo que necesitas para gestionar tu tienda VTEX sigue estando disponible en el Admin, pero ahora con una organización más sencilla. Nuestros menús laterales de navegación y la barra superior han sido completamente rediseñados, y ahora agrupan categorías similares de forma más clara para reducir las distracciones y ayudar a tu equipo a encontrar lo que necesita más rápidamente. También puedes utilizar la barra de búsqueda para encontrar secciones específicas en el menú lateral.
 
 ### Centro de información
 
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/2a2b0054854d4b726fa4a502b6e3db52/Information_center.gif)
+![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/2a2b0054854d4b726fa4a502b6e3db52/Information_center.gif)
 
 Allí hemos reunido todos los enlaces útiles de nuestro ecosistema VTEX para ayudarte a sacar el máximo partido a nuestra plataforma. Haciendo clic en el botón `?` en la barra superior, puedes acceder a nuestro Centro de ayuda, al Portal del desarrollador, al Status de la plataforma, al blog y a las páginas de soporte.
 
 ## Configuración de la tienda
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/b96a55b9faaffc3b604c74fa5a128d61/Store_settings.gif)
+![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/b96a55b9faaffc3b604c74fa5a128d61/Store_settings.gif)
 
 Para esta experiencia, hemos reunido las configuraciones de todas las secciones del Admin en una pestaña específica: [Configuración de la tienda](https://help.vtex.com/es/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Gracias a esta mejora, puedes acceder fácilmente a todas las configuraciones que afectan a cada servicio de tu cuenta.
 
 ### Configuración de la cuenta y del usuario
 
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/c560ccf053bfcf4f127db55ec088f7f9/Avatar_settings.gif)
+![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/c560ccf053bfcf4f127db55ec088f7f9/Avatar_settings.gif)
 
 El avatar de tu perfil, en la esquina superior derecha, reúne ahora todas las configuraciones relacionadas con tu usuario y tu cuenta. A través del avatar, puedes acceder a la [Configuración del usuario](https://help.vtex.com/es/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), a la [Configuración de la cuenta](https://help.vtex.com/es/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), y a la información de las [Facturas](https://help.vtex.com/es/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC).  También puedes cambiar el idioma de tu Admin y cerrar la sesión.
 
diff --git a/docs/tutorials/es/vtex-agreement.md b/docs/tutorials/es/vtex-agreement.md
new file mode 100644
index 000000000..a5f9cdc69
--- /dev/null
+++ b/docs/tutorials/es/vtex-agreement.md
@@ -0,0 +1,35 @@
+---
+title: 'Contrato VTEX'
+id: gjJL5j4zZuiC2qAuSuoG4
+status: PUBLISHED
+createdAt: 2019-01-24T20:45:47.050Z
+updatedAt: 2024-02-20T18:14:26.057Z
+publishedAt: 2024-02-20T18:14:26.057Z
+firstPublishedAt: 2019-01-24T22:07:46.230Z
+contentType: tutorial
+productTeam: Billing
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: contrato-vtex
+locale: es
+legacySlug: por-que-no-recibi-el-contrato-firmado-de-vtex
+subcategory: 22TaEgFhwE6a6CG2KASYkC
+---
+
+El contrato VTEX o acuerdo comercial consta de dos partes, el [MSA (Master Service Agreement)](https://vtex.com/mx-es/privacy-and-agreements/agreements/) y el **Anexo 1 Order Form** para la prestación de servicios a empresas o [MPA (Master Partner Agreement)](https://vtex.com/mx-es/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) y **Términos y condiciones específicos de la asociación**.
+
+![Contrato VTEX](//images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/8c31246d19b7238ab6c87db7e2521ffe/es.png)
+
+El [Master Services Agreement](https://vtex.com/mx-es/privacy-and-agreements/agreements/) y el [Master Partner Agreement](https://vtex.com/mx-es/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) son los contratos marco de servicio y de asociación, respectivamente, que regulan la relación entre VTEX y el cliente o VTEX y el partner. Ambos varían en función de la región en la que se encuentra la empresa o el partner. 
+
+El **Anexo 1 Order Form** y los **Términos y condiciones específicos de asociaciones** son documentos que recogen todas las condiciones comerciales negociadas para cada empresa o partner, incluyendo las disposiciones legales del contrato.
+
+## ¿Dónde puedo encontrar mi contrato con VTEX?
+
+El Master Agreement aplicable está disponible en la sección **Política de privacidad > Archivo de contratos > [Master Agreements](https://vtex.com/mx-es/privacy-and-agreements/agreements-archive/#:~:text=Master%20Agreements,September%2006%2C%202020%5D)** para clientes y **Política de privacidad > Archivo de contratos > [Partner Agreement](https://vtex.com/mx-es/privacy-and-agreements/agreements-archive/#:~:text=Contratos%20Anteriores,Partner%20Agreement)** para partners, dependiendo de la región y de la fecha en que se firmó el **Anexo 1** o los **Términos y condiciones específicos de la asociación**. El **Anexo 1** y los **Términos y condiciones** firmados con VTEX pueden solicitarse directamente al CS de tu cuenta poniéndote en contacto con el [soporte VTEX](https://help.vtex.com/support?/cultureInfo=pt-br).
+
+También puedes encontrar los Master Agreements más actualizados, es decir, los aplicables a nuevos clientes y partners, en la página [Contratos VTEX](https://vtex.com/mx-es/privacy-and-agreements/agreements/).
+
+<div class="alert alert-info">
+Si el <b>MSA, MPA, Anexo 1</b> o los <b>Términos y condiciones específicos de la asociación</b> firmados con VTEX incluyen información que difiere de lo descrito en esta documentación, prioriza tu documento firmado con VTEX.
+</div>
+
diff --git a/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
new file mode 100644
index 000000000..efe82d340
--- /dev/null
+++ b/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
@@ -0,0 +1,200 @@
+---
+title: 'Guía de los dashboards VTEX para la Black Week: FAQ'
+id: 6O3CiGiZctVIgIrpIcko9h
+status: PUBLISHED
+createdAt: 2023-11-17T17:09:40.720Z
+updatedAt: 2023-11-21T16:06:22.017Z
+publishedAt: 2023-11-21T16:06:22.017Z
+firstPublishedAt: 2023-11-20T18:30:27.790Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: guia-de-los-dashboards-vtex-para-la-black-week-faq
+locale: es
+legacySlug: guia-de-los-dashboards-vtex-para-la-black-week-faq
+subcategory: 1TIJqw8kV2Yok4iQe4SAkq
+---
+
+Esta guía tiene como objetivo responder las preguntas más frecuentes sobre cómo utilizar los [dashboards en el Admin VTEX](https://help.vtex.com/es/subcategory/visao-geral-do-insights--1TIJqw8kV2Yok4iQe4SAkq) durante la Black Week.  
+
+- [¿Cuál es la mejor manera de hacer un seguimiento de mi tienda online durante la Black Week en el Admin VTEX?](#cual-es-la-mejor-manera-de-hacer-un-seguimiento-de-mi-tienda-online-durante-la-black-week-en-el-admin-vtex)
+- [¿Cómo puedo monitorear los datos de mi tienda online más allá del día de hoy?](#como-puedo-monitorear-los-datos-de-mi-tienda-online-mas-alla-del-dia-de-hoy)
+- [¿Por qué mis métricas son diferentes de las del menú Pedidos del Admin?](#por-que-mis-metricas-son-diferentes-de-las-del-menu-pedidos-del-admin)
+- [¿Por qué no tengo datos de sesiones o tasas de conversión?](#por-que-no-tengo-datos-de-sesiones-o-tasas-de-conversion)
+- [¿Por qué mis métricas de tasa de conversión, nuevas sesiones o embudo de ventas no coinciden con los números de mis herramientas internas?](#por-que-mis-metricas-de-tasa-de-conversion-nuevas-sesiones-o-embudo-de-ventas-no-coinciden-con-los-numeros-de-mis-herramientas-internas)
+- [¿Por qué mis métricas de ingresos se muestran solo en una moneda, cuando opero con más de una?](#por-que-mis-metricas-de-ingresos-se-muestran-solo-en-una-moneda-cuando-opero-con-mas-de-una)
+- [¿Por qué el número de pedidos en el análisis del embudo de ventas no coincide con el de la sección Monitoreo?](#por-que-el-numero-de-pedidos-en-el-analisis-del-embudo-de-ventas-no-coincide-con-el-de-la-seccion-monitoreo)
+- [¿Por qué la nueva Vista general se encuentra en una URL separada?](#por-que-la-nueva-vista-general-se-encuentra-en-una-url-separada)
+
+## ¿Cuál es la mejor manera de hacer un seguimiento de mi tienda online durante la Black Week en el Admin VTEX?  
+
+Durante un periodo de intensa actividad y volatilidad en las ventas, la herramienta ideal para monitoreo es la nueva Vista general en tiempo real de VTEX. Para acceder a esta página, haz clic en **Dashboards > Vista general** en el menú de la izquierda, o ingresa **Vista general** en la barra de búsqueda situada en la parte superior de la página.  
+
+A continuación puedes consultar algunos consejos para aprovechar al máximo esta funcionalidad:  
+
+Empieza ajustando la zona horaria deseada y selecciona la tienda que deseas monitorear en Vista general en tiempo real.  
+
+![zona-horaria-es](//images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/7d760ad2226fec81b75c0e524b6a8220/zona-horaria-es.png)
+
+### Filtro de referencia  
+
+El filtro **Comparar hoy con** muestra una evaluación de tu desempeño actual con relación a un período específico.  
+
+Para configurar la referencia sigue los pasos a continuación:  
+
+1. Haz clic en **`Comparar hoy con`.**
+2. Selecciona `Personalizado`.
+3. Define una fecha.
+4. Haz clic en **`Aplicar`.**  
+
+<div class="alert alert-warning">
+Una comparación valiosa durante la Black Week se realiza al contrastar datos con la misma fecha del año anterior. En la configuración de referencia, se recomienda establecer preferiblemente una fecha entre el 21/11/2022 y el 27/11/2022, preferentemente los mismos días de la semana. <br>Esta opción está dirigida a clientes que utilizaron el Admin VTEX durante ese periodo el año pasado.</br>
+</div>  
+
+![referencia-es](//images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/4466f9301343f19f0ff79d89f5c44821/referencia-es.png)  
+
+### Filtro de vista  
+
+- **Realiza un seguimiento del desempeño del día con la Vista Acumulado:** esta vista muestra el monitoreo del desempeño de ventas de tu tienda online minuto a minuto, proporcionando insights para ajustes rápidos en la operación.  
+Para seleccionar el modo **Acumulado** en el dashboard, haz clic en **Vista<i class="fas fa-angle-down"></i> > Acumulado.**   
+
+![acumulado-es](//images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/754d3fdb3071c9daef2acd282b8d3733/acumulado-es.png)  
+
+- **Monitorea el desempeño de las últimas horas:** la **vista Últimas 2 horas** presenta las métricas minuto a minuto, importante para garantizar la estabilidad operacional de tu tienda durante el evento.  
+Para seleccionar el modo **Últimas 2 Horas** en el dashboard, haz clic en **Vista<i class="fas fa-angle-down"></i> > Últimas 2 horas.**
+
+![horas-es](//images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/368a2857ec9b9636011031ae989f8bb9/horas-es.png)  
+
+### Métricas  
+
+La **Vista general en tiempo real** otorga insights importantes sobre tu estrategia de ventas. Por ejemplo, puedes utilizar los datos presentes en Productos más vendidos como referencia para impulsar campañas y potenciar aún más tus resultados.  
+Para consultar los productos más vendidos, en la sección **Métricas**  haz clic en  <i class="fas fa-ellipsis-v"></i> y selecciona **Productos más vendidos.**  
+
+![mas-vendidos-es](//images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/22b06efc2dd15dded404a1c4b1f23f2c/mas-vendidos-es.png)   
+
+<div class="alert alert-danger">
+Para análisis o seguimientos de periodos más extensos, recomendamos el uso de nuestro dashboard Desempeño de ventas, que se detalla en la siguiente pregunta.
+</div>
+
+## ¿Cómo puedo monitorear los datos de mi tienda online más allá del día de hoy?  
+
+Para un seguimiento efectivo de tu tienda online más allá del día actual, el [dashboard Desempeño de ventas de VTEX](https://help.vtex.com/es/tutorial/performance-de-vendas--3DMube0sEsK9vPcRYGas72) es la herramienta ideal. Su tasa de actualización es de, aproximadamente, 90 minutos, y ofrece un historial de datos más extenso. Aquí te explicamos cómo aprovecharlo al máximo:  
+
+### Filtros  
+
+- **Fecha**  
+Al acceder al dashboard, el primer paso es definir el **Periodo principal** y **Comparar con.** Si estás realizando el análisis una vez finalizada la Black Week, selecciona Semana pasada para comparar con la Black Week del año anterior (opción disponible si ya eras cliente de VTEX). Durante la Black Week, elige Personalizar y selecciona los días específicos para el análisis.  
+![ventas-fecha-es](//images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/2b20340d6c7237d5d9b1056ea3371896/ventas-fecha-es.png)   
+
+- **Filtros combinados**  
+La información proporcionada en el dashboard de ventas se puede segmentar mediante filtros combinados, como, por ejemplo, el filtro Categorías. Si deseas agregar un nuevo filtro, sigue los pasos que se detallan a continuación:  
+1. En el dashboard Desempeño de ventas, haz clic en **Filtros.**  
+2. Haz clic en <i class="fas fa-plus"></i> Agregar Filtro.  
+3. Selecciona las categorías deseadas.  
+4. Haz clic en **`Aplicar`.**  
+
+Puedes explorar diferentes filtros de acuerdo con las necesidades y aspectos específicos de tu tienda online.  
+
+![agregar-filtro-es](//images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/ddc34564c2379083779ead2e8eb36f9f/agregar-filtro-es.png)   
+
+### Métricas  
+
+Las métricas exhibidas pueden personalizarse para su visualización según las necesidades del análisis. Cada métrica puede ajustarse haciendo clic en el botón <i class="fas fa-ellipsis-v"></i> que aparece al lado de su nombre.  
+
+Durante la Black Week, este dashboard es una herramienta clave para analizar las siguientes métricas del desempeño de tu operación:  
+
+- Ingresos (recibidos)  
+- Pedidos (aprobados)   
+- Pedidos (facturados)   
+- Ticket promedio (aprobado)  
+- Pedidos (cancelados)  
+
+![cambio-de-metrica-es](//images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/10826d203b100064613c3c8df5cecd07/cambio-de-metrica-es.png)  
+
+- **Desempeño de la semana**   
+Después de realizar los ajustes, compara el desempeño de la semana actual con la Black Week del año pasado para identificar tendencias y oportunidades.  
+
+![desenpeno-de-la-semana-es](//images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/6e7b2320f5a89ea5f1873d5655e60ea9/desenpeno-de-la-semana-es.png)  
+
+- **Análisis de la tabla**   
+Analiza los datos de la tabla para obtener insights más profundos. Por ejemplo, el análisis por SKU puede revelar qué productos deben destacarse en futuras campañas.  
+
+![analisis-de-la-tabla-es](//images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/d584956e1fb744a7a006a3128ecd0fb4/analisis-de-la-tabla-es.png)  
+
+- **Guarda la vista de tu interés**  
+Guarda la configuración de tu dashboard para futuras consultas. Haz clic en **Gestión de ventas > <i class="fas fa-plus"></i>  > Nombre de la vista > `Crear`,** para guardar tu vista personalizada.  
+
+![crear-vista-es](//images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/635dfd2f1cb8b7f6f31e95e36704baa3/crear-vista-es.png)    
+
+## ¿Por qué mis métricas son diferentes de las del menú Pedidos del Admin?  
+
+Hay varias razones por las cuales las métricas de la Vista general en tiempo real pueden diferir de las del menú Pedidos del Admin:  
+
+- **Vista general:** las métricas que se muestran en los dashboards del Admin VTEX se centran exclusivamente en las ventas de una tienda por vez. Por lo tanto, todas las métricas presentadas estarán vinculadas a la tienda seleccionada en el filtro del dashboard.  
+- **Pedidos:** las métricas presentes en Pedidos consideran todas las ventas realizadas en el periodo en cuestión.  
+- **Tiempo de actualización diferente:** la pantalla Vista general en tiempo real puede demorar en actualizarse de 1 a 3 minutos. Por lo tanto, es normal que haya una pequeña discrepancia (de 1 a 3 % del total) entre ambas pantallas.  
+- **Fórmula de cálculo de ingresos:** las métricas en Vista general en tiempo real no consideran descuentos, envíos, tarifas ni promociones en el cálculo de ingresos, mientras que las métricas presentes en Pedidos sí que tienen en cuenta esos factores.  
+
+![selecion-de-tiendas-es](//images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/6921089644b0d5821da2692011534c9e/selecion-de-tiendas-es.png)  
+
+Para obtener una visión completa de las métricas combinadas de todas las tiendas, te recomendamos acceder al dashboard Desempeño de ventas. Este dashboard ofrece datos agregados con una tasa de actualización de aproximadamente 90 minutos.  
+
+<div class="alert alert-danger">
+Si tu tienda online opera con más de una moneda puedes consultar los pedidos en el <b>dashboard Vista general;</b> el total de los mismos se presentan sumados en la moneda más utilizada en tus ventas. <br>Para comparar con la pantalla <b>Pedidos,</b> debes sumar el total de pedidos en todas las monedas.</br>
+</div>    
+
+![todos-los-pedidos-es](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
+
+- **Zona horaria:** este filtro puede aplicarse en el dashboard **Vista general** en tiempo real; en caso de que la zona horaria sea diferente a la definida en la pantalla Pedidos (que es tu zona horaria actual), las métricas no serán iguales. Ajusta la zona horaria si fuera necesario.  
+
+![ventas-zona-horaria](//images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/26a44df390eaf73e4e16889540dd46ab/ventas-zona-horaria.png)   
+
+## ¿Por qué no tengo datos de sesiones o tasas de conversión?  
+
+Los análisis de tasa de conversión, sesiones y embudo de ventas en VTEX se basan en datos capturados por nuestra base de navegación, que dependen de un script propio ejecutado dentro de la tienda online del cliente. Este script es esencial para registrar la información necesaria para dichos análisis.  
+
+Sin embargo, es importante saber que nuestro script no captura datos de sesiones que provienen de marketplaces, aplicaciones o de implementaciones headless, donde no gestionamos el frontend. Además, las personalizaciones en el frontend de la tienda pueden interferir o incluso desactivar nuestro script. Esto significa que, en algunos casos, estas sesiones y actividades no se registran, lo que resulta en la falta de datos de sesiones o tasas de conversión en tu dashboard.  
+
+Si percibes la ausencia de estos datos, podría deberse a una de las limitaciones anteriormente mencionadas. Recomendamos verificar las configuraciones del script y cualquier personalización en el frontend que pueda estar afectando la captura de datos.  
+
+![vision-general-es](//images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/ac409a2e6f8df8dd575f67aea6cac85c/vision-general-es.png)
+
+## ¿Por qué mis métricas de tasa de conversión, nuevas sesiones o embudo de ventas no coinciden con los números de mis herramientas internas?  
+
+Herramientas de análisis como Google Analytics suelen instalarse de manera personalizada y con alta prioridad, lo que les permite capturar un espectro más amplio de datos. Esto a menudo resulta en discrepancias en comparación con nuestros números.  
+
+Por otro lado, la captura de datos de navegación en VTEX se realiza mediante nuestro propio script, ejecutado dentro de la tienda online del cliente. Dado que el script se carga en último lugar en la página para minimizar impactos en el desempeño, es posible que no se registren sesiones muy breves.  
+
+Es importante destacar que nuestro script no recopila datos de sesiones provenientes de marketplaces, aplicaciones o implementaciones headless. Además, las personalizaciones realizadas por el cliente en el frontend pueden interferir o incluso desactivar nuestro script, impactando la recopilación de datos.  
+
+## ¿Por qué mis métricas de ingresos se muestran solo en una moneda, cuando opero con más de una?  
+
+En VTEX, para simplificar la visualización del gráfico de ingresos en la sección de monitoreo de la Vista general en tiempo real, optamos por mostrar el valor en una sola moneda. Esta decisión se toma para proporcionar una visión clara y directa de los ingresos, sin la complejidad adicional de múltiplas monedas.  
+
+Para determinar qué moneda mostrar, evaluamos cuál es la moneda más utilizada en las ventas de tu tienda online y convertimos todos los demás valores a esa moneda. Esto se hace para ofrecer una comprensión más sencilla y directa del desempeño de ventas.  
+
+Como resultado, si operas con más de una moneda, es importante sumar el total de pedidos de la sección Pedidos del Admin en todas tus monedas para que coincida con los datos mostrados en los pedidos dentro de Vista general en tiempo real.  
+
+![todos-los-pedidos-es](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
+
+![monitoreo-es](//images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/03430c27c5ed46f970ad711c18b8042a/monitoreo-es.png)    
+
+## ¿Por qué el número de pedidos en el análisis del embudo de ventas no coincide con el de la sección Monitoreo?  
+
+Para entender esta discrepancia, es esencial saber que las métricas de monitoreo mostradas en Vista general en tiempo real se generan a partir de nuestro Sistema de Gestión de Pedidos (OMS). El OMS contiene información sobre los diferentes tipos de pedidos de la tienda, incluyendo ventas en marketplaces, ventas directas, ventas en aplicaciones, etc.  
+
+Por otro lado, los datos del embudo de ventas se recopilan de la base de navegación del sitio web, que captura exclusivamente los datos de ventas realizadas dentro de la tienda online del cliente. Esto significa que las ventas realizadas en marketplaces o en otras tiendas que no utilizan el storefront de VTEX no se incluyen en este embudo.  
+
+Como resultado, es común que el número de pedidos en el embudo de ventas sea menor que en la sección Monitoreo, que proporciona una visión más amplia de las ventas de la tienda, incluyendo canales externos a la plataforma VTEX.  
+
+![tasa-de-conversion-es](//images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/43cf092b352a825a20d12692909c6f1c/tasa-de-conversion-es.png)  
+![nuevas-sesiones-es](//images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/8b3df33b3054de0743e95db323eeefd2/nuevas-sesiones-es.png)  
+
+## ¿Por qué la nueva Vista general se encuentra en una URL separada?  
+
+En VTEX decidimos mantener temporalmente la antigua Vista general mientras introducimos la nueva Vista general en tiempo real. Para garantizar una transición libre de problemas y un acceso ininterrumpido a la versión anterior, la nueva Vista general se alojó en un entorno separado. Esto significa que, al acceder a la nueva Vista general, es posible que debas iniciar sesión nuevamente en el Admin VTEX.  
+
+Es importante señalar que, ocasionalmente, podrías encontrar errores al intentar cargar la página de la nueva Vista general. Estos errores suelen estar relacionados con la necesidad de reautenticación en el sistema, debido al entorno separado en el que se aloja la nueva página.  
+
+Estamos trabajando para integrar la Vista general en tiempo real en el entorno original del Admin VTEX. Una vez que se complete esta integración, la antigua pantalla será descontinuada, simplificando el proceso y mejorando la experiencia del usuario. Hasta entonces, agradecemos tu paciencia y comprensión.  
+
diff --git a/docs/tutorials/es/vtex-do-interface.md b/docs/tutorials/es/vtex-do-interface.md
index 8de97b2cf..6758afe52 100644
--- a/docs/tutorials/es/vtex-do-interface.md
+++ b/docs/tutorials/es/vtex-do-interface.md
@@ -3,8 +3,8 @@ title: 'VTEX DO'
 id: 7KMbRL4OslN8DTX9oiuCiu
 status: PUBLISHED
 createdAt: 2022-04-04T21:12:30.592Z
-updatedAt: 2023-03-29T14:50:36.206Z
-publishedAt: 2023-03-29T14:50:36.206Z
+updatedAt: 2023-11-06T14:21:27.706Z
+publishedAt: 2023-11-06T14:21:27.706Z
 firstPublishedAt: 2022-04-04T21:58:08.236Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,10 +17,10 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 VTEX DO es un gestor de tareas creadas automáticamente por el Admin VTEX para que el equipo de _ecommerce_ de tu tienda las realice manualmente. Para acceder a VTEX DO, en el menú del Admin VTEX, ve a **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/lista-de-pedidos--2QTduKHAJMFIZ3BAsi6Pi)** y haz clic en el ícono de bandeja de entrada, ubicado en la esquina inferior derecha de la página. Al hacer clic en el ícono, se abrirá un modal con la lista de tareas relacionadas con los pedidos de la tienda.
 
-![VTEX Do overview ES](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
+![VTEX Do overview ES](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
 
 <div class = "alert alert-info">
-Solo los usuarios con el recurso <a href = "https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> registrado en su <a href = "https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acceso</a> pueden realizar tareas a través de VTEX DO.
+Solo los usuarios con el perfil de acceso <a href = "https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> pueden realizar tareas a través de VTEX DO.
 </div>
 
 Las tareas aparecen en dos pestañas:
@@ -115,7 +115,7 @@ Las tareas gestionadas a través de VTEX DO pueden incluir mensajes de todos los
 
 ## Detalles de la tarea
 
-![VTEX Do details ES](https://images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/d72c3000996192d5f687c6adf8b0b381/VTEX_Do_details_ES.jpg)
+![VTEX Do details ES](//images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/d72c3000996192d5f687c6adf8b0b381/VTEX_Do_details_ES.jpg)
 
 Al hacer clic en el nombre de una tarea de la lista, se te redirige al modal de detalles de la tarea que presenta más información sobre la misma y las acciones para resolverla. Se muestran los siguientes campos:
 
diff --git a/docs/tutorials/es/vtex-insurance.md b/docs/tutorials/es/vtex-insurance.md
index c1041139d..aa6b4e8e7 100644
--- a/docs/tutorials/es/vtex-insurance.md
+++ b/docs/tutorials/es/vtex-insurance.md
@@ -1,10 +1,10 @@
 ---
 title: 'VTEX Insurance'
 id: 2aF3SDIj5t2qGe3bWKCjLD
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-05-23T20:15:25.639Z
-updatedAt: 2023-05-26T18:43:28.958Z
-publishedAt: 2023-05-26T18:43:28.958Z
+updatedAt: 2024-01-11T20:01:57.317Z
+publishedAt: 
 firstPublishedAt: 2023-05-26T17:46:59.436Z
 contentType: tutorial
 productTeam: B2B
@@ -15,4 +15,106 @@ legacySlug: vtex-insurance
 subcategory: 
 ---
 
-<div class="alert alert-warning" role="alert">Contenido en proceso de traducción.</div>
+**VTEX Insurance** es una aplicación que permite al administrador de la tienda vincular los productos que vende con ofertas de seguros de la aseguradora partner [Assurant] (https://www.assurant.com.br/). Esta funcionalidad permite que tu tienda ofrezca a tu cliente un seguro personalizado, que le brinda protección financiera en caso de fallos o defectos en el producto o servicio adquirido. Al adquirir una garantía extendida, el consumidor puede optar por una capa adicional de seguridad. 
+
+Una vez aprobado el pago, tu cliente recibirá un email de nuestro equipo de soporte con el documento del seguro adquirido. Este documento es el comprobante de que el producto está asegurado y contiene toda la información que describe el seguro contratado, así como las instrucciones para ponerse en contacto con la aseguradora.
+
+Consulta en la siguiente tabla los tipos de seguros que ofrece VTEX Insurance.
+
+Código   | Tipo de seguro
+--------- | ------
+EW | Garantía extendida
+TH | Robo y hurto agravado
+RQ | Robo y daño accidental
+QA | Daño accidental
+
+Para configurar VTEX Insurance en tu tienda, debes:
+
+1. <a href="#prerrequisitos-para-vtex-insurance">Instalar la aplicacion VTEX Insurance.</a>
+2. <a href="#preparar-el-catalogo">Preparar el catálogo de la tienda para incluir los tipos de seguros disponibles.</a>
+3. <a href="#configurar-insurance">Configurar Insurance.</a>
+
+## Prerrequisitos para VTEX Insurance
+Para empezar a configurar VTEX Insurance sigue los pasos a continuación:
+
+1. En el Admin VTEX, haz clic en **Configuración de la cuenta> Usuarios** o ingresa **Usuarios** en la barra de búsqueda en la parte superior de la página.
+2. Haz clic en `Nuevo`. 
+Introduce el email de la tienda responsable de la instalación de VTEX Insurance en el campo **Email**.
+En caso de que el email introducido no sea identificado, haz clic en `Agregar roles`. En esta página debes seleccionar un rol predeterminado como **Owner** o **Desarrollador** (en caso de que el perfil no exista, deberá crearse).
+3. Haz clic en `Guardar`. 
+
+El email registrado recibirá un mensaje de nuestro soporte con el acceso a la aplicación VTEX Insurance.
+
+## Preparar el catálogo
+Después de instalar VTEX Insurance, necesitas preparar el catálogo para incluir los planes de seguros y vincularlos a tus productos. Para realizar la configuración, sigue los pasos a continuación:
+
+1. Registra [Assurant como un seller de tu tienda](https://help.vtex.com/es/tutorial/agregar-seller--tutorials_392).
+2. [Crea una colección](https://help.vtex.com/es/tutorial/registrar-colecciones-beta--yJBHqNMViOAnnnq4fyOye) y agrupa un conjunto de productos a los que vincular los seguros. Es necesario crear una colección específica para cada tipo de seguro, ya que dicha colección se utilizará para definir en qué póliza se encuadran los productos.
+3. [Crea un grupo de especificaciones (campos) en una categoría](https://help.vtex.com/es/tutorial/crear-grupo-de-especificaciones-en-una-categoria--tutorials_246) para incluir las garantías del fabricante en tu catálogo, como Garantía, por ejemplo. 
+4. [Crea una especificación de producto](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-producto--tutorials_106) con la información del seguro que deseas ofrecer, como por ejemplo, Garantía extendida.
+5. Después de crear el campo **Garantía del fabricante**, establece el período de garantía deseado. En el campo **Valor predeterminado**, se recomienda el valor 12, que representa un rango de 12 meses.
+6. [Crea una categoría]https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1) específica para el producto del seguro. 
+7. [Crea el producto](https://help.vtex.com/es/tutorial/productos-y-skus-beta--2ig7TmROlirWirZjFWZ3B) del seguro.
+8. [Crea los SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY) del seguro. Se recomienda crear más de tres SKU para cada seguro.![Valores Permitidos](//images.ctfassets.net/alneenqid6w5/7DTx1xSHfrWWPCCvVHjJ8z/db89bae8fd2b247707a557c9aa253285/image1.png)
+9. [Vincula los SKU](https://help.vtex.com/es/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX) creados con el seller de Assurant.
+10. [Vincula el seguro con el producto](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-producto--tutorials_106) deseado.
+
+<div class="alert alert-info" role="alert">
+<p> Este proceso debe repetirse en todas las categorías y productos en los que se ofrezca algún tipo de seguro. </p>
+</div>
+
+## Configurar Insurance
+
+Una vez preparado el catálogo, los productos de tu tienda ya estarán vinculados con el seguro. En **Seguros** > **Configuración**, realizarás la configuración del registro de VTEX Insurance. 
+
+Sigue los pasos a continuación para configurar la aplicación VTEX Insurance.
+
+### Información de la empresa
+![Insurance Configuration](//images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/1158b7f84241410fbd3edc81400ff5a5/image5.png)
+1. Rellena los siguientes campos:
+- **Email**: email de la tienda
+- **Nombre**: nombre de la tienda
+- **Teléfono**: teléfono de la tienda
+- **Valor del markup**: margen de beneficio a obtener. Debe rellenarse con el valor 0 (cero) 
+- **Nombre de la calle**: calle de la tienda u oficina
+- **Ciudad**: ciudad de la tienda u oficina
+- **Estado o provincia**: dependiendo del país, estado o provincia donde se encuentra la tienda u oficina
+- **Código postal**: código postal de la tienda u oficina
+- **País**: país de la tienda u oficina
+2. Haz clic en `Enviar`.
+
+### Ítems vinculados a seguros
+![Items Bound to Source Items](//images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/7fd57ef26b0320e745bb81736d76707e/image2.png)
+
+1. Selecciona los códigos que representan los tipos de seguro deseados para la colección creada. 
+
+2. Vincula los SKU creados con los tipos del seguro: debes incluir el tipo de seguro seguido del SKU ID. Ejemplo: al vincular el tipo de seguro **Garantía extendida** (Código **EW**) con el SKU creado para ese mismo tipo de seguro (ID **357**), el vínculo se representará de la siguiente forma:EW|357** (sin espacios).
+Si deseas vincular más de un tipo de seguro, como el de **Robo y hurto agravado** (Código **TH**) al SKU creado (ID **358**), vínculo **TH|358**, el campo se rellenará como sigue: **EW|357, TH|358**
+3. Haz clic en `Enviar`.
+
+### Nombre del campo de la garantía
+![Warranty Field Name](//images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/90a5985112d73bbd552e553353790899/image8.png)
+
+1. En el campo de garantía del fabricante ingresa el nombre de la garantía utilizado en el catálogo.
+2. Haz clic en `Enviar`.
+
+### Configuración de anexos VTEX Insurance 
+![Attachement Setup](//images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/853b158cfce470f32cceb2489564ac54/insurance_attachement_setup.png)
+
+1. [Crea un anexo](https://help.vtex.com/es/tutorial/registrar-un-anexo--7zHMUpuoQE4cAskqEUWScU) para Assurant con la información enviada por el equipo de soporte al contratar el servicio.
+
+2. En **Seguros> Configuración**, haz clic en `Adjuntar anexo` en la sección **Seguros** **Configuración de anexos**.
+
+3. En la página **Anexos**, haz clic en el botón `Editar` referente al anexo **assurant.seguro**.
+
+4. Para cada elemento de la tabla, haz clic en `Editar` y elimina todos los valores del campo **Valores permitidos**.
+
+5. Haz clic en `Guardar`.
+
+### Configuración de precios manual
+
+![Manual Pricing](//images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/fa85e9cdf6064218cf182242475056c8/image11.png)
+
+1. [Activa la configuración de precios manual](https://help.vtex.com/es/tutorial/cambiar-el-precio-de-un-item-en-el-carrito-de-compras--7Cd37aCAmtL1qmoZJJvjNf) en tu tienda.
+2. Haz clic en `Continuar`.
+
diff --git a/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
index ccf43029f..5cc09c836 100644
--- a/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -3,8 +3,8 @@ title: 'VTEX Intelligent Search: configuración Multidioma (Beta)'
 id: 2WahlTESLXIJ9XBdQMdTYO
 status: PUBLISHED
 createdAt: 2021-03-09T22:44:16.513Z
-updatedAt: 2023-03-30T17:45:54.079Z
-publishedAt: 2023-03-30T17:45:54.079Z
+updatedAt: 2023-07-26T19:15:24.855Z
+publishedAt: 2023-07-26T19:15:24.855Z
 firstPublishedAt: 2021-03-10T21:13:35.816Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,11 +27,7 @@ VTEX Intelligent Search Multidioma expande las funcionalidades de [Intelligent S
 <p> En caso de que desee expandir su ecommerce a otro idioma, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a> para que el equipo de VTEX realice las configuraciones necesarias.</p>
 </div>
 
-Cuando tiene VTEX Intelligent Search Multidioma instalada, la información del Catálogo de su tienda es traducida por la aplicación [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization), si la misma está registrada como términos traducibles de los siguientes campos: Nombre, Marca (solo si hay una traducción registrada por el administrador de la tienda), Descripción, Categorías, CategoryTrees, metadata, metadataKeyword, Especificaciones, SKU {name}.
-
-<div class="alert alert-warning">
-<p> Si un término no tiene una traducción registrada en Messages, es traducido por un servicio automático. Por eso, es importante <a href="https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization">registrar la traducción de todos los campos</a> para evitar efectos no deseados, como las traducciones literales que no reflejen la lengua que se utiliza en una región determinada. Si el término correcto no está registrado, el nombre de un producto como «whole milk», por ejemplo, corre el riesgo de ser traducido automáticamente como «leche entera» en lugar de «leche integral».</p>
-</div>
+Cuando tiene VTEX Intelligent Search Multidioma instalada, la información del Catálogo de su tienda es traducida por la aplicación [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization). Para eso, es importante registrar la traducción de los siguientes campos: Nombre, Marca (solo si hay una traducción registrada por el administrador de la tienda), Descripción, Categorías, CategoryTrees, metadata, metadataKeyword, Especificaciones, SKU {name}. Lea la guía para desarrolladores [Traducción del contenido del catálogo](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) para obtener más información.
 
 A través de [Multi-Tenant API](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-multi-language-stores), VTEX Intelligent Search Multidioma obtiene todos los lugares y respectivos idiomas (ej.: pt-br, en-GB) registrados en la tienda. Cada lugar posee una URL propia.
 
@@ -47,7 +43,7 @@ VTEX Intelligent Search Multidioma permite que personalice la experiencia de bú
 ### Reglas de merchandising
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la página de edición o creación de Reglas de merchandising — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Reglas de merchandising__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará la regla de merchandising mediante la selección de los idiomas deseados, como se muestra en la siguiente imagen.  
 
-![img regrasmerch intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/a0f959bcd8d52fe586e7b4ab4d91c63a/01-merchrules-es.png)
+![img regrasmerch intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/a0f959bcd8d52fe586e7b4ab4d91c63a/01-merchrules-es.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Reglas de merchandising en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8).
 
@@ -61,7 +57,7 @@ Hay dos formas de configurar Sinónimos en una tienda multidioma en el Admin: co
 #### Crear Sinónimos vía formulario
 Cuando tiene VTEX Intelligent Search Multidioma instalada,  la página de edición o creación de Sinónimos — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Sinónimos__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará los sinónimos registrados, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
 
-![img sinonimos intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/3fe16ea17b2f435094c2cb823831e57b/image_4.png)
+![img sinonimos intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/3fe16ea17b2f435094c2cb823831e57b/image_4.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Sinónimos en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
@@ -85,7 +81,7 @@ Para saber más sobre la importación de una plantilla de Sinónimos, lea nuestr
 
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la página de edición o creación de Redireccionamientos  — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Redireccionamientos__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará las redirecciones registradas, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
 
-![img redirecionamentos intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/84213b8bd9f82c318b08f54813358fa4/03-redirecionamento-en.png)
+![img redirecionamentos intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/84213b8bd9f82c318b08f54813358fa4/03-redirecionamento-en.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Redireccionamientos en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4Gd2wLQFbCwTsh8RUDwSoL).
 
@@ -93,6 +89,6 @@ Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar
 
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la página de edición o creación de Banners — que se accede en el Admin VTEX en __Storefront__ > __Banners__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará los banners registrados, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
 
-![img banner intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8231d24b62009bf4afeb9ce8299650a7/image_9.png)
+![img banner intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8231d24b62009bf4afeb9ce8299650a7/image_9.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Banners en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
diff --git a/docs/tutorials/es/vtex-invoice-notifier.md b/docs/tutorials/es/vtex-invoice-notifier.md
index 8f613fb0c..bfa6dcdcf 100644
--- a/docs/tutorials/es/vtex-invoice-notifier.md
+++ b/docs/tutorials/es/vtex-invoice-notifier.md
@@ -29,9 +29,9 @@ Con el endpoint registrado en el APP, el OMS comienza a reconocer que se habilit
 
 El operador debe, en el pedido, seleccionar el paquete o los ítems que desea facturar y generar una nueva notificación:
 
-![notify-invoicer1](https://images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
+![notify-invoicer1](//images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
 
-![notify-invoicer2](https://images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
+![notify-invoicer2](//images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
 
 Cuando el usuario del OMS presione el botón __Request Invoice__, el app realizará un request POST en el endpoint registrado en el APP con el siguiente BODY, ejemplo:
 
diff --git a/docs/tutorials/es/vtex-operation-service-level-agreement-sla.md b/docs/tutorials/es/vtex-operation-service-level-agreement-sla.md
new file mode 100644
index 000000000..b087c3c3d
--- /dev/null
+++ b/docs/tutorials/es/vtex-operation-service-level-agreement-sla.md
@@ -0,0 +1,26 @@
+---
+title: 'Acuerdo de nivel de servicio (SLA) para la operación de VTEX'
+id: 2cIFrsY5S8usk84OU4QOKm
+status: PUBLISHED
+createdAt: 2019-01-24T20:45:48.688Z
+updatedAt: 2024-03-11T22:27:09.058Z
+publishedAt: 2024-03-11T22:27:09.058Z
+firstPublishedAt: 2019-01-24T22:13:57.539Z
+contentType: tutorial
+productTeam: Reliability
+author: 7FpKZ0rc6k4WqeymES80cw
+slug: acuerdo-de-nivel-de-servicio-sla-para-la-operacion-de-vtex
+locale: es
+legacySlug: que-es-el-sla-de-operacion-de-la-plataforma
+subcategory: 5PYkoNDZyo2G80yiiqG2YW
+---
+
+El [Service Level Agreement (SLA)](https://vtex.com/mx-es/privacy-and-agreements/agreements/) es un acuerdo de nivel de servicio, es decir, una política que rige el uso de la plataforma VTEX bajo los términos del contrato firmado entre VTEX y el cliente, que es el contratista. Este documento especifica todos los servicios que un contratista puede esperar de VTEX.
+
+El SLA expresa el nivel de servicio de la infraestructura de la plataforma y aclara técnicamente su tiempo de funcionamiento y de inactividad, así como todos los eventos que se contabilizan o no como incidentes.
+
+Consulte nuestro SLA en [VTEX Commerce - SLA Agreement](https://vtex.com/mx-es/privacy-and-agreements/agreements/).
+
+## Más información
+
+- [¿Cómo se comprueba el SLA de operación de la plataforma?](https://help.vtex.com/es/tutorial/como-se-comprueba-el-sla-de-operacion-de-la-plataforma--frequentlyAskedQuestions_662)
diff --git a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
index a993c2fdd..445dc2bcc 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack: Fulfillment'
 id: 1zGUEItEEVsal6cuBEBNcA
 status: PUBLISHED
 createdAt: 2023-04-10T15:43:59.687Z
-updatedAt: 2023-04-20T15:41:30.789Z
-publishedAt: 2023-04-20T15:41:30.789Z
+updatedAt: 2023-08-31T19:52:23.529Z
+publishedAt: 2023-08-31T19:52:23.529Z
 firstPublishedAt: 2023-04-10T17:57:34.714Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,625 +15,464 @@ legacySlug: vtex-pick-and-pack-fulfillment
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-[VTEX Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU) es una solución para agilizar los procesos de fulfillment de las tiendas, optimizando la recolección y el empaquetado de los pedidos y la entrega last mile. La solución está compuesta por las páginas [Last Mile](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) y **VTEX Pick and Pack Fulfillment**, y está disponible en tu VTEX Admin en **Apps**.
-
-El módulo **VTEX Pick and Pack Fulfillment** está relacionado con el proceso de gestión de pedidos y cuenta con las siguientes secciones:
-
-- [Recolección y empaquetado](#recoleccion-y-empaquetado)
-- [Insights](#insights)
-- [Configuración](#configuracion)
-- [Usuarios](#usuarios)
-
-<div class="alert alert-danger">
-<b>VTEX Pick and Pack</b> no es un sistema de facturación. Tras la recolección y el empaquetado, el pedido debe ser facturado y actualizado como <code>Facturado</code> en OMS, para que <b>VTEX Fulfillment</b> pueda finalizar el flujo de recolección y empaquetado y proceder al envío.
+<div class = "alert alert-info">
+Si tienes interés en implementarla en tu negocio, rellena nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> indicando en el campo <code>Comentarios</code> el nombre del producto deseado.
 </div>
 
-## Recolección y empaquetado
-
-Esta es la interfaz de gestión de pedidos, con dos páginas principales:
-
-- [Lista de recolección y empaquetado](#lista-de-recoleccion-y-empaquetado)
-- [Detalles de recolección y empaquetado](#detalles-de-recoleccion-y-empaquetado)
-
-### Lista de recolección y empaquetado
+- [Ingreso a la aplicación](#ingreso-a-la-aplicacion)
+    - [Página de inicio](#pagina-de-inicio)
+- [Proceso de alistamiento](#proceso-de-alistamiento)
+    - [Creación de hojas de trabajo](#creacion-de-hojas-de-trabajo)
+    - [Alistamiento de ítems](#alistamiento-de-items)
+    - [Rechazar ítems](#rechazar-items)
+    - [Reemplazar ítems](#reemplazar-items)
+    - [Observaciones al ítem o al pedido](#observaciones-al-item-o-al-pedido)
+    - [Opciones de la hoja de trabajo dentro del menú](#opciones-de-la-hoja-de-trabajo-dentro-del-menu)
+- [Proceso de empaquetado](#proceso-de-empaquetado)
+    - [Empaquetado en masa o individual](#empaquetado-en-masa-o-individual)
+        - [Empaquetado en masa](#empaquetado-en-masa)
+        - [Empaquetado individual](#empaquetado-individual)
+- [Proceso de envío](#proceso-de-envio)
+- [Sección Pedidos - Admin](#seccion-pedidos---admin)
+- [Sección Hojas de trabajo - Admin](#seccion-hojas-de-trabajo---admin)
+- [Configuración de la aplicación](#configuracion-de-la-aplicacion)
+    - [Configuración y alistamiento](#configuracion-y-alistamiento)
+    - [Cambios en los pedidos](#cambios-en-los-pedidos)
+    - [Motivos de rechazo y motivos de cambios de precio](#motivos-de-rechazo-y-motivos-de-cambios-de-precio)
+        - [Límite de cambios](#limite-de-cambios)
+        - [Hojas de trabajo para habilitar o deshabilitar funciones](#hojas-de-trabajo-para-habilitar-o-deshabilitar-funciones)
+        - [Tags de hojas de trabajo](#tags-de-hojas-de-trabajo)
+        - [Activar códigos EAN dinámicos](#activar-codigos-ean-dinamicos)
+    - [Configuración de categorías](#configuracion-de-categorias)
+    - [Configuración de empaquetado](#configuracion-de-empaquetado)
+    - [Configuración de pedidos](#configuracion-de-pedidos)
+    - [Configuración de automatización](#configuracion-de-automatizacion)
+    - [Configuración de instalaciones](#configuracion-de-instalaciones)
+    - [Configuración de catálogo](#configuracion-de-catalogo)
 
-Al acceder a **Fulfillment > Recolección y empaquetado**, encontrarás una página en la que se enumeran todos los pedidos con pago confirmado con [status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) `Listo para recolección`, como en la imagen de abajo.
+## Ingreso a la aplicación
 
-La tabla siguiente contiene la descripción de las columnas mostradas:
+Para empezar a utilizar Pick and Pack, es necesario tener acceso a la [aplicación](https://picking.pickingnpacking.com/login) como alistador. Como alistador podrás acceder a tu cuenta, iniciar sesión y encontrar pedidos. [Ir a la aplicación](https://picking.pickingnpacking.com/login).
 
-| **Columna** | **Descripción** |
-| ----------- | ---------- |
-| Fecha de creación | Fecha y hora de realización del pedido. |
-| Fecha de entrega | El plazo de entrega de los pedidos, definido en el acuerdo de nivel de servicio (SLA) entre la tienda y el cliente. |
-| Forma de entrega | El tipo de envío del pedido, que puede ser entrega, envío a la dirección del cliente o recogida en un [punto de recogida](https://help.vtex.com/es/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). |
-| Número del pedido | ID único que identifica un pedido, el mismo que se utiliza en el sistema de gestión de pedidos (OMS). |
-| Entregador | Nombre del _entregador_ asignado al pedido. El _entregador_ es la persona responsable del proceso de recolecc ión. El valor predeterminado es `No asignado` hasta que se asigne un _entregador_. |
-| Status | El status del pedido, que puede ser:<ul><li><b>Listo para preparación:</b> los pedidos están listos para su preparación, pero aún no se han asignado a un recolector.</li><li><b>Listo para recolección:</b> el pedido fue asignado a un recolector y depende de su confirmación para pasar al siguiente status.</li><li><b>Recolectando:</b> se están recogiendo los ítems del pedido.</li><li><b>Listo para empaquetar:</b> el proceso de recolección ha finalizado y el pedido está listo para ser empaquetado.</li><li><b>Empaquetando:</b> los ítems del pedido se están empaquetando en bolsas o paquetes determinados por la tienda.</li><li><b>Listo para facturar:</b> el pedido puede ser facturado. La solución VTEX Pick and Pack no factura los pedidos.</li><li><b>Facturado:</b> el pedido fue facturado.</li><li><b>Preparando servicios:</b> los servicios de envío están listos para ser creados.</li><li><b>Listo para envío:</b> el pedido está listo para envío.</li><li><b>Entregado:</b> el pedido fue entregado a la dirección del cliente o punto de recogida.</li><li><b>Inactivo:</b> el pedido era de fulfillment externo, y VTEX Pick and Pack no podrá procesarlo. Si el pedido se factura en OMS en un status distinto a <code>Listo para facturar</code>, el sistema también lo considerará un caso de fulfillment externo y cambiará el status del pedido a <code>Inactivo</code>.</li><li><b>Cancelado:</b> el pedido estaba listo para preparación, pero fue cancelado.</li></ul> | 
+Ingresa tu usuario debidamente registrado, contraseña y haz clic en  **iniciar sesión**.
 
-Para ver más detalles sobre un pedido, selecciona uno de la lista y la información siguiente aparecerá:
-
-| **Columna** | **Descripción** |
-| ---------- | ---------- |
-| Información del cliente | El nombre, email y número de contacto del cliente. |
-| Información de entrega | La dirección de entrega del cliente o la dirección del punto de recogida, cuando el cliente elige la opción de recogida en tienda. |
-| Ventana de entrega | Muestra la fecha en que se realizó el pedido y la fecha prevista en que el cliente lo recibirá. |
-| Ítems del pedido | El número de ítems y sus categorías. |
-| Medio de pago | El valor total del pedido y el [medio de pago](https://help.vtex.com/es/tutorial/difference-between-payment-methods-and-payment-conditions--3azJenhGFyUy2gsocms42Q) utilizado, como tarjetas de crédito o débito. |
-
-Puedes realizar las siguientes acciones en la página de Recolección y empaquetado:
-
-- [Buscar](#buscar)
-- [Filtrar](#filtrar)
-- [Importar](#importar)
-- [Exportar](#exportar)
-- [Imprimir recibos](#imprimir-recibos)
-- [Asignar/reasignar entregador](#asignar-reasignar-entregador)
-
-#### Buscar
-
-En la parte superior de la página, hay un cuadro de búsqueda con el ícono de lupa <i class="fas fa-search"></i> en el que puedes buscar pedidos utilizando los siguientes criterios:
-
-- ID del pedido
-- Nombre del cliente
-- Operador de la tienda responsable del pedido
+![pick and pack 1](//images.ctfassets.net/alneenqid6w5/3tIH46Q7spSVEa1nDMBaHU/6c9cf04d64fe02a4a4e27c0cbcfe9ea2/image26.png)
 
-#### Filtrar
+## Página de inicio
 
-Puedes filtrar los pedidos utilizando diferentes criterios. Al hacer clic en `Filtros`, un modal muestra estas opciones:
+Al acceder, se habilita el dashboard del alistador, que te permitirá monitorizar, analizar y visualizar los indicadores clave de desempeño del alistador.
 
-- **Orden ascendente/descendente:** al seleccionar orden ascendente, se muestran primero los pedidos con la fecha y hora de entrega más recientes, según lo establecido por los clientes al realizar el pago. En orden descendente, los pedidos se muestran de forma inversa.
-- **Fecha del pedido:** define un rango para filtrar los pedidos creados entre las fechas de inicio y fin elegidas.
-- **Fecha de vencimiento:** los plazos de entrega ocurren dentro de la fecha de inicio y fin elegidas.
-- **Status:** selecciona uno o varios [status de pedido](#lista-de-recoleccion-y-empaquetado).
-- **Total del pedido:** el rango de costo del pedido, que puede ir de USD 0 a 5 millones.
-- **Número de ítems:** el número de ítems del pedido, que puede ir de 0 a 99.
-- **Transportadora:** la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) responsable de la entrega.
-- **Medio de pago:** el [medio de pago](https://help.vtex.com/es/tutorial/difference-between-payment-methods-and-payment-conditions--3azJenhGFyUy2gsocms42Q) utilizado por el cliente, como tarjetas de crédito o débito.
-- **Entregador:** el entregador asignado para el proceso de recolección del pedido. Utiliza los emails de los entregadores disponibles.
-- **Categorías:** las categorías de los ítems de los pedidos. Por ejemplo, _Bebidas_ o _Ropas_. Depende del árbol de categorías de la tienda configurado en el Catálogo.
+![pick and pack 2](//images.ctfassets.net/alneenqid6w5/3Hx3ir28gfSdv60DupqIpj/d169addf3e5162f53fd4ffae4fabf172/image3.png)
 
-Si deseas eliminar los filtros seleccionados, haz clic en `Filtros` y luego en `Borrar filtros`.
+- Permite visualizar de manera gráfica la cantidad de pedidos alistados durante los últimos días.
+- Puedes consultar la cantidad de pedidos con alistamiento finalizado.
+- Puedes consultar el tiempo total invertido en cada ítem de los pedidos procesados.
+- Permite conocer la cantidad de hojas de trabajo con el proceso de alistamiento finalizado y las que están pendientes de realizar el proceso de empaquetado.
+- - Permite conocer los pedidos pendientes que aún no han iniciado el proceso de alistamiento.
 
-#### Importar
+En la sección superior de la aplicación podrás encontrar las siguientes funcionalidades.
 
-Por defecto, los pedidos con status `Listo para preparación` deben ser importados automáticamente de OMS a Recolección y empaquetado. Si un pedido no aparece en el módulo de fulfillment, a pesar de estar `Listo para separación`, puede deberse a cambios manuales en el status del pedido en OMS, y puedes importarlo manualmente.
+- **Selección de instalación,** ubicada a la derecha del ícono del usuario alistador. Al tocar, indica las instalaciones asociadas al usuario.
 
-Para importar un pedido manualmente, sigue los pasos a continuación.
+![pick and pack 3](//images.ctfassets.net/alneenqid6w5/7KTcPX2RJjmo7QMfZxsxx8/b5b10100395ac08bc6cb78575e3eeaed/image15.png)
 
-1. Haz clic en `Importar`.
-2. Introduce el ID del pedido.
-3. Selecciona la casilla `Solo se importarán los pedidos que no se hayan descargado automáticamente`.
-4. Haz clic en `Importar`.
+- **Menú**, donde figuran los accesos directos a las funcionalidades principales de la aplicación.
 
-#### Exportar
+![pick and pack 4](//images.ctfassets.net/alneenqid6w5/2633eMzDne2LCpYWqksCUm/e09e4962d5a17b8b68993387b2fcb719/image17.png)
 
-Puedes exportar una lista de pedidos siguiendo los pasos a continuación.
+## Proceso de alistamiento
 
-1. Haz clic en `Exportar`.
-2. Aplica los filtros deseados.
-    > No se pueden exportar todos los pedidos. Puedes duplicar o eliminar filtros en el menú <i class="fas fa-ellipsis-v"></i>. Los filtros disponibles son:
-    - Entregador
-    - Categorías
-    - Transportadora
-    - Fecha de inicio
-    - Fecha de fin
-    - Ciudad
-3. Haz clic en `Exportar`.
+### Creación de hojas de trabajo
 
-#### Imprimir recibo
+Desde la página de inicio, toca la opción **Sin asignar.** 
 
-El recibo es un informe que contiene lo que recogió el entregador y el valor total del pedido. Puede funcionar como factura en algunos países, pero no es la norma.
+Al ingresar, encontrarás pedidos que están listos para preparación, organizados por fecha de entrega de forma descendiente.
 
-Para imprimir un recibo de pedido, haz clic en el menú <i class="fas fa-ellipsis-v"></i> de la fila correspondiente al pedido y selecciona `Imprimir recibo`.
+Los pedidos en color rojo son aquellos que llevan mucho tiempo sin ser gestionados y el verde representa aquellos más recientes.
 
-#### Asignar/reasignar entregador
-
-Para asignar o reasignar un entregador, en la fila del pedido deseado, haz clic en el menú <i class="fas fa-ellipsis-v"></i> y selecciona `Asignar` o `Reasignar`. Se abrirá un modal donde elegirás el nombre del entregador.
-
-También puedes asignar o reasignar un entregador en la página [Detalles de Recolección y empaquetado](#detalles-de-recoleccion-y-empaquetado), haciendo clic en el icono del lápiz <i class="fas fa-pencil-alt"></i> y seleccionando el entregador.
-
-### Detalles de recolección y empaquetado
-
-Para acceder a la página de detalles de un pedido, en la **página de la lista de recolección y empaquetado**, haz clic en el botón de menú <i class="fas fa-ellipsis-v"></i> de la fila del pedido sobre el que deseas ver más información y selecciona `Ver detalles`. Se te redirigirá a la siguiente página:
+<div class = "alert alert-info">
+Las hojas de trabajo permitirán combinar varios pedidos, de modo que todos los ítems puedan ser alistados.
+</div>
 
-En la página de detalles, puedes realizar las acciones a continuación. Las acciones disponibles en la **página de detalles de Recolección y empaquetado** cambiarán en función del status del pedido mostrado en la [página de lista de Recolección y empaquetado](#recoleccion-y-empaquetado).
+Elige los pedidos que deseas gestionar y haz clic en la opción  **Empezar a alistar.** En ese momento el sistema crea las hojas de trabajo, con su respectivo número de identificación, que estarán compuestas por los ítems de los pedidos seleccionados.
 
-- [Recolectar](#recolectar)*
-- [Agregar ítem](#agregar-item)*
-- [Crear producto personalizado](#crear-producto-personalizado)
-- [Reemplazar ítem (Buscar)](#buscar-reemplazar-item)*
-- [Reemplazar por ítem recomendado (Sugerencias)](#sugerencias-sustituir-por-un-item-recomendado)*
-- [Cambiar precio](#cambiar-precio)*
-- [Eliminar ítem](#eliminar-item)*
-- [Finalizar recolección/confirmar recolección](#finalizar-recoleccion-confirmar-recoleccion)*
-- [Empaquetar](#empaquetar)*
-- [Imprimir recibo y comprobante](#imprimir-recibo-y-comprobante)
-- [Agregar servicio de envío](#agregar-servicio-de-envio)
-- [Seguir pedido](#seguir-pedido)
+![pick and pack 5](//images.ctfassets.net/alneenqid6w5/3ibz0RB8PSB3NdQnfVmXny/dc584f577881dbe47ff343a05ea0c528/image43.png)
 
-<div class="alert alert-danger">
-Aunque las acciones anteriores pueden ser realizadas por <a href="https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios">usuarios</a> con acceso al Admin, típicamente las acciones con un <b>*</b> (asterisco) deben ser ejecutadas únicamente por entregadores utilizando sus dispositivos móviles, sin ningún acceso al Admin de la tienda.
-</div>
+![pick and pack 6](//images.ctfassets.net/alneenqid6w5/79AdZNyZkpj3dK8uLfFUnz/ee0bd30e3073345a515d46c7e0de1019/image11.png)
 
-#### Recolectar
+De igual manera, se  habilitarán las acciones de alistamiento para cada producto que compone los pedidos asociados a las hojas de trabajo.
 
-En el flujo natural, la recolección la realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+### Alistamiento de ítems
 
-En la fila del producto, como en la imagen de abajo, puedes elegir un producto y realizar otras acciones.
+Hay varias formas de iniciar el alistamiento de los productos: 
 
-Para recolectar un producto, sigue los pasos que a continuación.
+Sitúate sobre el producto que deses alistar, y desliza hacia la izquierda.
 
-1. En la columna **Cantidad**, selecciona el número deseado de ítems.
-2. Haz clic en el símbolo <i class="far fa-check-circle"></i> al final de la fila.
-3. Haz clic en `Confirmar`.
+![pick and pack 7](//images.ctfassets.net/alneenqid6w5/1hGlv0xBZbzSxviLzKXHTW/05f428c28ca4faff07d563b48a8e60e6/image39.png)
 
-En caso de que necesites deshacer la recolección, haz clic en el menú <i class="fas fa-ellipsis-v"></i> en la fila del producto y selecciona `Restaurar`.
+Si se pulsa una vez sobre el producto, solo será alistada una unidad. Si se pulsa dos veces, se alistarán todas las unidades.
 
-#### Agregar ítem
+### Rechazar ítems
 
-En el flujo natural, la adición de los ítems la realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+Existen varias formas de rechazar un producto:
 
-Puedes agregar otro producto siguiendo los pasos a continuación.
+Sitúate en el producto que deseas alistar, y desliza hacia el lado derecho.
 
-1. En el menú <i class="fas fa-ellipsis-v"></i>, en la misma fila del ID del pedido, haz clic en `+Agregar ítem`.
-2. Busca el producto deseado.
-3. Haz clic en `Seleccionar`.
-4. Haz clic en `Agregar productos`
+![pick and pack 8](//images.ctfassets.net/alneenqid6w5/57QUYlKaUtl360QlxWC4kt/af1d8ca336a5f911568f9ec948461bf4/image7.png)
 
-#### Crear producto personalizado
+Mantén pulsado el producto y se desplegará un menú, donde puedes seleccionar Descartar ítem.
 
-Puedes crear un producto personalizado siguiendo los pasos a continuación.
+![pick and pack 9](//images.ctfassets.net/alneenqid6w5/2zRTW81m8FsoFpvNl70O4/b6b7f8ebe0d37d6439a348ed0735a5f0/image25.png)
 
-1. En el menú <i class="fas fa-ellipsis-v"></i>, en la misma fila del ID del pedido, haz clic en `+Agregar ítem`.
-2. Haz clic en el ícono con el signo <i class="fas fa-plus"></i> más.
-3. Rellena los siguientes campos:
-    - Nombre
-    - Precio
-    - RefID
-    - EAN
-4. Selecciona una categoría.
-5. Haz clic en `Agregar`.
-6. Haz clic en `Agregar productos`.
+Después, debe incluirse el motivo del rechazo. Si lo deseas, puedes rechazar una cantidad específica, ingresando la cifra para después pulsar la opción Descartar unidades. También puedes descartarlas todas, como se muestra en la captura de pantalla a continuación.
 
-#### Buscar: reemplazar ítem
+![pick and pack 10](//images.ctfassets.net/alneenqid6w5/78Ghr0v7Dp1PkKqLF1Q4pZ/2fc6d278277e1aa09c19ffad4c05935d/image23.png)
 
-En el flujo natural, el reemplazo de los ítems lo realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+### Reemplazar ítems
 
-Puedes reemplazar un producto siguiendo los pasos a continuación.
+La opción **Reemplazar ítem** se encuentra en el menú que se despliega al tocar cada producto.
 
-1. En la fila de un producto no recolectado, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
-2. Haz clic en `Buscar`.
-3. Busca el producto deseado.
-4. Haz clic en `Seleccionar`.
-5. Haz clic en `Confirmar`.
-6. En el modal que se abre, selecciona un motivo para el reemplazo.
-    > Es necesario configurar los motivos, como se explica en la sección [Configuración de recolección](#configuracion-de-recoleccion).
-7. Rellena el campo **Observaciones** con una breve explicación para el reemplazo (obligatorio).
-8. Haz clic en `Confirmar`.
+Si se accede a **Reemplaza ítem**, el sistema valida los pedidos a los que pertenece el producto. Si existen pedidos que comparten productos el sistema habilita el listado de los pedidos asociados.
 
-#### Sugerencias: sustituir por un ítem recomendado
+![pick and pack 11](//images.ctfassets.net/alneenqid6w5/2fFFzKLeIp6dNgknXAYuC/efdcba4627eadd592938dc8d4419218c/image21.png)
 
-En el flujo natural, el reemplazo de los ítems lo realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+Selecciona los pedidos deseados y toca la opción **Reemplazar en los pedidos seleccionados.** Después, el sistema habilitará la pantalla **Reemplazar ítem.**
 
-Puedes reemplazar un ítem por otro basándote en una recomendación. La opción mostrada depende de cuál sea tu configuración en [Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb).
+La pantalla Reemplazar ítem habilita los productos asociados al producto a reemplazar. Puedes utilizar el filtro de búsqueda.
 
-Para reemplazar un ítem por una recomendación, sigue los pasos a continuación.
+![pick and pack 12](//images.ctfassets.net/alneenqid6w5/3lGf61iDMk0nXqPtpIjTvM/3ff3f40f5609d481d8ee1d844a586a5a/image57.png)
 
-1. En la fila correspondiente a un producto no recolectado, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
-2. Haz clic en `Sugerencias`.
-3. Agrega el producto mostrado haciendo clic en `Seleccionar`.
-4. Haz clic en `Confirmar`.
-5. En el modal que se abre, selecciona un motivo para el reemplazo.
-    > Es necesario configurar los motivos, como se explica en la sección [Configuración de recolección] (#configuración-recolección).
-6. Rellena el campo **Observaciones** con una breve explicación para el reemplazo (obligatorio).
-7. Haz clic en `Confirmar`.
+Selecciona el producto deseado y haz clic en  la opción Reemplazar ítem: el sistema habilitará los campos de reemplazo.
 
-Para buscar un producto manualmente, sigue los pasos a continuación.
+![pick and pack 13](//images.ctfassets.net/alneenqid6w5/1pYNdI9Az53pRgdg1cYTnm/aef41d13dbcfa7534c36fe94de3733ff/image35.png)
 
-1. En el menú <i class="fas fa-ellipsis-v"></i>, haz clic en `Sugerencias`.
-2. Haz clic en `Buscar manualmente`.
-3. Busca el producto deseado.
-4. Haz clic en `Seleccionar`.
-5. Haz clic en `Confirmar`.
-6. En el modal que se abre, selecciona un motivo para el reemplazo.
-    > Es necesario configurar los motivos, como se explica en la sección [Configuración de recolección] (#configuración-recolección).
-7. Rellena el campo **Observaciones** con una breve explicación para el reemplazo (obligatorio).
-8. Haz clic en `Confirmar`.
+Se pueden ingresar los siguientes datos:
+- Precio.
+- Cantidad.
+- Seleccionar el motivo de rechazo.
+- Ingresar la descripción del rechazo.
+- Modificar el precio.
 
-#### Cambiar precio
+Toca la opción **Confirmar reemplazo.**
 
-En el flujo natural, el cambio de precio lo realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+### Observaciones al ítem o al pedido
 
-Para cambiar el precio de un ítem, sigue los pasos a continuación.
+Para ingresar observaciones sobre el producto, accede al menú del ítem y después a la opción **Agregar observaciones.**
 
-1. En la fila correspondiente a un producto no recolectado, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
-2. Haz clic en `Cambiar precio`.
-3. En el modal que se abre, rellena los campos:
-    - Nuevo precio
-    - Motivo
-    - Observaciones
-4. Haz clic en `Cambiar precio`.
+![pick and pack 14](//images.ctfassets.net/alneenqid6w5/1r3yi390cfL6GxMcbEAWyj/1f8138ce000a1408441d5f77dbed2d2b/image31.png)
 
-#### Eliminar ítem
+Si existen pedidos que comparten producto, selecciona el pedido al que debe asociarse la observación. Ingresa la observación y toca la opción **Agregar observación.**
 
-En el flujo natural, la eliminación de los ítems lo realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+Para ingresar observaciones a la hoja de trabajo, nos ubicamos en el menú y seleccionamos la opción **Agregar observaciones.** Ingresamos las observaciones y tocamos en **Agregar observación.**
 
-Puedes rechazar un producto siguiendo los pasos a continuación.
+### Opciones de la hoja de trabajo dentro del menú
 
-1. En el menú <i class="fas fa-ellipsis-v"></i>, haz clic en `Eliminar ítem`.
-2. En el modal que se abre, selecciona un motivo para el rechazo.
-3. Rellena el campo **Observaciones** con una breve explicación para el reemplazo (obligatorio).
-4. Haz clic en `Confirmar`.
+- **Listo para empaquetar:** permite alistar o rechazar todos los ítems asociados a la hoja de trabajo.
+- **Pausar alistamiento:** al hacer clic sobre esta opción, la hoja de trabajo queda en estado de pausa para no afectar el rendimiento del alistador.
+- **Imprimir lista de alistamiento:** disponibiliza un documento que enumera los ítems alistados de cada pedido.
 
-En caso de que necesites restaurar el producto, haz clic en el menú <i class="fas fa-ellipsis-v"></i> y selecciona `Restaurar`.
+![pick and pack 15](//images.ctfassets.net/alneenqid6w5/7D4oZ5bWzb5BPeN43xH7HV/002a586863b4e1044aeac477b165cc2e/image45.png)
 
-#### Finalizar recolección/confirmar recolección
+## Proceso de empaquetado
 
-En el flujo natural, este paso lo realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+Al terminar con el alistamiento del pedido el status pasa a ser Listo para empaquetar, permitiendo realizar el proceso de empaquetado.
 
-Dependiendo del status del pedido que aparezca en la [página de la lista de recolección y empaquetado](#lista-de-recoleccion-y-empaquetado), en la sección **Status**, encontrarás diferentes botones para acciones específicas, como `Finalizar recolección` en la imagen de abajo:
+Existen varias formas de iniciar el empaque.
 
-Puedes realizar las siguientes acciones haciendo clic en los botones disponibles:
+En el dashboard se encuentra la opción **Para empaquetar;** al acceder, nos redirige a la lista de hojas de trabajo pendientes por empacar. Desde el menú, accedemos a la lista de **Empaquetado** ubicada dentro de la opción **Pendiente.**
 
-- `Finalizar recolección`: todos los ítems fueron recogidos y finalizas la recolección, pasando al proceso de empaquetado.
-- `Confirmar recogida`: si se trata de una entrega, confirmas la recogida cuando los paquetes están listos para ser entregados, y una transportadora los ha recogido. Si el cliente va a recibir el pedido en un punto de recogida, confirma la recogida después de que el cliente reciba los paquetes.
+![pick and pack 15](//images.ctfassets.net/alneenqid6w5/5wiF37YnG1uwyR3j3SjB50/f3634ddeab5a581319b18252955ae4b3/image9.png)
 
-#### Empaquetar 
+Dentro de la pestaña **Empaquetado** seleccionamos la hoja de trabajo que se encuentre en estado Listo para empaquetar o Empaquetado para iniciar o continuar el proceso de empaque.
 
-En el flujo natural, el empaquetado lo realizan los recolectores en sus dispositivos móviles. Esta sección muestra cómo hacerlo a través del Admin, por si [otros usuarios](#usuarios) necesitan realizar esta acción.
+Al acceder encontramos la lista de productos, donde podemos realizar un empaque individual o en masa.
 
-Una vez finalizado el proceso de recolección, debes crear los paquetes e indicar qué ítem va en cada paquete. La [configuración de los paquetes](#configuracion-de-paquetes) sobre cómo configurar las bolsas y cualquier tipo de paquetes se verá en las próximas secciones.
+![pick and pack 16](//images.ctfassets.net/alneenqid6w5/76b06UUuKR7apFSGFXfetA/2a2b5bdfd1377b631e33102676adc9d3/image14.png)
 
-Para crear un nuevo paquete, sigue los pasos a continuación.
+### Empaquetado individual o en masa
 
-1. Haz clic en el icono de la sección **Lista de paquetes**.
-2. Selecciona el tipo de paquete.
-3. Haz clic en `Crear paquete`.
+#### Empaquetado en masa
 
-Puedes agregar un solo producto a un paquete o todos los productos a la vez. Una vez empaquetados todos los productos, haz clic en `Cerrar paquetes`. Una vez que cierres los paquetes, ya no podrás agregar ítems ni realizar ningún tipo de cambio.
+Para realizar un empaquetado en masa, dirígete al icono en forma de caja ubicado al lado derecho del campo de búsqueda.
 
-<div class="alert alert-danger">
-<b>VTEX Pick and Pack</b> no es un sistema de facturación. Una vez que el pedido pasa al status <code>Listo para facturar</code>, debe facturarse y actualizarse como <code>Facturado</code> en OMS. Solo después <b>VTEX Fulfillment</b> finalizará el flujo de recolección y empaquetado y procederá al envío. Si el pedido se factura en un status distinto a <code>Listo para facturar</code>, el sistema lo considerará un caso de fulfillment externo y cambiará el status del pedido a <code>Inactivo</code> y no permitirá que <b>VTEX Pick and Pack</b> lo procese.
-</div>
+Al tocar, se abre una ventana donde seleccionar el pedido para hacer el empaque masivo. Elige el embalaje que deseas utilizar.
 
-#### Imprimir recibo y comprobante
+Verifica los productos del pedido que seleccionaste y toca la opción Empaquetar producto.
 
-En la parte superior de la página de detalles, a la izquierda de **Status**, encontrarás un menú <i class="fas fa-ellipsis-v"></i>. Al hacer clic en él, se muestran las siguientes opciones:
+![pick and pack 17](//images.ctfassets.net/alneenqid6w5/4cTjjNy4p1dcFjTFklDhhi/ccb4a42627f2d3e78a3ef26f23f9ee28/image5.png)
 
-- **Recibo:** imprimir el recibo del pedido con una lista de todos los ítems.
-- **Comprobante:** imprime el comprobante, un informe para los clientes que contiene información general y que puede ser firmado por ellos.
-- **Recibo de los ítems recogidos:** imprime el recibo del pedido relacionado solo con los ítems ya recolectados.
-- **Comprobante de los ítems recogidos:** imprime el comprobante del pedido relacionado solo con los ítems ya recolectados.
-- **+ Agregar ítem:** [agrega un nuevo producto](#agregar-item) o crea un [producto personalizado](#crear-producto-personalizado).
+#### Empaquetado individual
 
-#### Agregar servicio de envío
+Para realizar un empaquetado individual, selecciona el producto que necesitas empaquetar.
 
-Cuando la recolección, el empaquetado y la facturación del pedido hayan finalizado y el pedido se encuentre en el status `Preparando servicios`, puedes agregar un servicio de envío siguiendo los pasos a continuación.
+Si el producto está asociado a más de un pedido, el sistema lista los pedidos que puedes empaquetar; elige el pedido deseado.
 
-1. Haz clic en el botón `Agregar servicio`.
-2. Selecciona el **día** y **hora** en que el pedido estará listo para recolección.
-3. Selecciona el **día** y **hora** en que se enviará el pedido.
-4. Selecciona la transportadora.
-5. Selecciona el tipo de servicio.
-6. Selecciona el medio de pago.
-7. Selecciona los paquetes que se enviarán.
-8. Haz clic en `Confirmar envíos`.
+Haz clic en **Nuevo Paquete** y selecciona el embalaje que deseas utilizar. 
 
-Recibirás un mensaje de éxito y el pedido pasará al status _Listo para envío_.
+Agrega las unidades y selecciona la opción **Empaquetar producto.**
 
-#### Seguir pedido
+## Proceso de envío
 
-Una vez que el pedido pase al status _Listo para envío _o _Entregado_, aparecerá el botón `Ir al seguimiento` en la [página de detalles de Recolección y empaquetado](#detalles-de-recoleccion-y-empaquetado). Al hacer clic en él, se te redirigirá a la [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) para realizar el seguimiento del pedido.
+Una vez alistados todos los ítems, debes realizar el proceso de envío seleccionando desde el menú la opción **Para enviar.**
 
-O puedes ir a **Last Mile** directamente en el Admin de la tienda, accediendo a **Apps > Last Mile > Servicios de envío**.
+![pick and pack 18](//images.ctfassets.net/alneenqid6w5/3JqIlsCpWHul7ou3md1N4h/8307b7628684191dfa7f712ca4293808/image18.png)
 
-## Insights
+Se abrirá el listado de pedidos que se encuentran listos para envío, organizados por fecha de empaque. Haz clic sobre el pedido que deseas enviar.
 
-En **VTEX Pick and Pack**, la página **Insights** proporciona datos y análisis sobre tus pedidos durante el proceso de fulfillment. En esta página, verás dos pestañas:
+Si el pedido contiene más de un paquete, se deben seleccionar los paquetes para crear el servicio de envío. Después, haz clic en **Siguiente.**
 
-- [Recolección y empaquetado](#insights-recoleccion-y-empaquetado)
-- [Operación](#insights-operacion)
+Para crear el servicio de envío, deben proporcionarse los siguientes datos:
 
-<div class="alert alert-warning">
-Para poder acceder a <b>Insights</b>, es necesario tener un perfil de usuario de administrador en VTEX Fulfillment Admin, que es diferente de los <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a>. Para más información, consulta la sección <a href="https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios">Usuarios</a>.
-</div>
+- Fecha de recolección.
+- Fecha de entrega.
+- Seleccionar transportadora.
 
-### Insights: Recolección y empaquetado
+Al terminar, toca en la opción **Seleccionar y continuar.**
 
-El **Total de pedidos** es una métrica actualizada en tiempo real que proporciona información sobre todos los pedidos de un determinado periodo en comparación con otro. Puedes utilizar varios [filtros](#insights-filtros) para obtener diferentes resultados.
+![pick and pack 18](//images.ctfassets.net/alneenqid6w5/7mvhayvPfwyNkHgq5DMCWk/24ad3596a5d163694abc38f6b858a226/image16.png)
 
-#### Insights: Filtros
+Verifica los datos del servicio y haz clic en la opción **Crear servicio.**
 
-Puedes combinar varios filtros para filtrar la información que deseas ver en las métricas, accediendo a `Filtros` en la parte superior de la página. Puedes filtrar por los siguientes criterios:
+## Sección pedidos - Admin
 
-- Entregador
-- Forma de entrega
-- Transportadora
-- Ciudad
-- Seller
+Al entrar como Administrador tendrás acceso a la opción **Pedidos** desde el panel de Pick and Pack.
 
-<div class = "alert alert-info">
-El filtro <b>Seller</b> solo está disponible para las cuentas que operan como marketplace. Los <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">sellers white label</a> no tienen esta opción de filtro <b>Insights</b>.
-</div>
+En esta sección se muestra la distribución de pedidos según el estado en el que se encuentre actualmente:
 
-Además del **Total de pedidos**, hay una secuencia de métricas para obtener datos sobre _medios de pago_ y pedidos:
-
-- Recolectados
-- Enviados
+- Todos
+- Pendiente
+- Para enviar
 - Entregados
-- Cancelados
+- Cancelado
+- Rechazado
+- Exportar
 
-Puedes aplicar varios filtros para obtener diferentes resultados.
+Posee un filtro de búsqueda configurable según la necesidad de resultado del usuario. Se puede filtrar por:
 
-#### Insights: Rendimiento de categorías y productos
+- Fecha de creación
+- Fecha de entrega
+- Categorías
+- Medios de pago
+- Estrategia de envío
 
-Debajo del **Total de pedidos**, encontrarás métricas sobre el número de pedidos, las unidades compradas y a qué categoría pertenecen. Puedes elegir agrupar por `Categorías` o `Productos`.
+Cuenta con un botón para **cerrar** ventana, o en su defecto, para **borrar todos** los filtros seleccionados.
 
-### Insights: Operación
+![pick and pack 20](//images.ctfassets.net/alneenqid6w5/2cCfB2KdjWyRdvD8q9z4BF/3710266548a474dff6516120945ed626/image4.png)
 
-En la pestaña **Operación**, verás el **flujo de pedidos** de Recolección y empaquetado, que mostrará la cantidad total de pedidos distribuidos por día en los últimos siete días. Cuanto más oscuro sea el tono de azul, más pedirás; cuanto más claro, menos.
+La  sección Pedidos muestra la tabla de datos sin filtrar, con las opciones:
 
-<div class = "alert alert-info">
-El flujo de <b>Recolección y empaquetado</b> se calcula considerando todos los pedidos de los últimos 7 días y los distribuye en horas, de 0 a 23. Aunque cambies el periodo a 15 días, por ejemplo, la visualización permanecerá fija considerando 7 días.
-</div>
+- ID del pedido
+- Facturas
+- Ítem(s)
+- Envío
+- Pago
+- Tags
+- Fecha de vencimiento
+- Status
 
-Debajo del **flujo de pedidos**, hay una métrica con pedidos filtrados por entregador. Verás información sobre:
+El usuario tendrá acceso a toda la información necesaria que corresponde al pedido.
 
-- Pedidos
-- Productos
-- Productos rechazados
-- Tasa de fulfillment
-- Tiempo promedio
+Al seleccionar un pedido, se abrirá una ventana adicional en la cual se muestra el estado del pedido.
 
-La página también proporciona métricas relacionadas con los siguientes temas:
+- Además se puede comprobar el tiempo de preparación y la fecha de entrega prevista.
+- Las facturas del pedido.
+- Los ítem(s): se observarán los ítems ya alistados, rechazados, reemplazados y otras acciones realizadas desde la aplicación.
+- Las observaciones del pedido.
+- La información de envío.
+- La información del pago.
+- La información adicional.
+- Inicios de sesión.
 
-- **Pedidos recolectados:** el número de pedidos recolectados en el periodo seleccionado.
-- **Tasa de fulfillment:** el porcentaje de pedidos recolectados dentro del plazo mínimo de entrega.
-- **Tiempo:** el tiempo promedio del proceso de recolección.
-- **Motivos de rechazo:** la explicación de por qué se ha rechazado un producto.
-- **Motivos de rechazo:** la explicación de por qué se ha reemplazado un producto.
-- **Motivo del cambio de precio:** la explicación de por qué un producto ha sufrido un cambio de precio.
+## Sección hojas de trabajo - Admin
 
-## Configuración
+Al acceder como administrador, se podrá hacer un seguimiento de los pedidos y los flujos de datos de todas las acciones realizadas en la aplicación.
 
-Para configurar **VTEX Pick y Pack** para su tienda, en tu Admin ve a **Apps > Fulfillment > Configuración.** Verás una página con las siguientes pestañas:
+En la opción **Hojas de trabajo** se muestran las  siguientes secciones:
 
-- [General](#configuracion-general)
-- [Recolección](#configuracion-de-recoleccion)
-- [Categorías](#configuracion-de-categorias)
-- [Paquetes](#configuracion-de-paquetes)
-- [Envío](#configuracion-de-envio)
-- [Impresión](#configuracion-de-impresion)
-- [Webhooks](#configuracion-de-webhook)
+### Tiempo real
 
-<div class="alert alert-warning">
-Para poder acceder a <b>Configuración</b>, debes ser un <a href="https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios">usuario administrador de VTEX Fulfillment</a> o un usuario de atención al cliente.
-</div>
+Muestra la cantidad de pedidos realizados y su porcentaje.
 
-### Configuración general
+### Pedidos no asignados
 
-En esta pestaña, puedes configurar la tienda a la que vas a agregar **VTEX Pick and Pack**. Puedes elegir una tienda haciendo clic en el lápiz <i class="fas fa-pencil-alt"></i> en la parte superior de la página y seleccionando la tienda deseada.
+En esta sección se encuentran los pedidos que aún no han sido asignados a ningún alistador; los pedidos en color rojo son los que llevan más tiempo y los que están en verde son los más recientes.
 
-Para configurar una tienda, sigue los pasos a continuación.
+### Hojas de trabajo
 
-1. Rellena los campos junto al mapa con la información de la dirección de la tienda.
-2. En **Información de contacto**, rellena los datos de la persona de contacto, si es necesario.
-3. En **Horario laboral**, configura la hora de inicio y fin de los días de la semana en los que se puede realizar la recolección en la tienda.
-4. En **Unidades de medida**, selecciona qué unidad será la predeterminada para medir la longitud de los ítems y paquetes, por ejemplo.
-5. Haz clic en el botón `Guardar`.
+En esta opción se podrán encontrar los pedidos que ya han iniciado un proceso de alistamiento desde la aplicación.
 
-### Configuración de recolección
+Al ingresar se muestra una tabla con las opciones:
 
-En esta pestaña se configuran algunos de los principales aspectos y preferencias del proceso de recolección, como los motivos de rechazo y los [entregadores](#usuarios-y-license-manager-en-vtex-fulfillment).
+- Todos
+- Alistando
+- Empaquetando
+- Completado
+- Cancelado
 
-Para ajustar la configuración de recolección, sigue los pasos a continuación.
+También posee la opción de Fijado, donde el usuario puede acceder a los pedidos en los que está trabajando actualmente.
 
-1. En **Asignación de entregadores**, selecciona si la tienda asignará los entregadores manualmente (`manual`), por un [usuario administrador](#usuarios-y-license-manager-en-vtex-fulfillment) o automáticamente (`automático`), en función de la disponibilidad de los entregadores.
-2. En **Ruta de empaquetado**, selecciona el momento en el que deseas que se inicie el proceso de empaquetado, que puede ser:
-    - Después de la recolección
-    - Después de la facturación
-    - A partir de la facturación
-3. En la **aplicación de recolección**, activa los botones relacionados con las preferencias de las actividades que los entregadores podrán ver y realizar a través de la aplicación móvil. No es obligatorio activarlos. Las opciones son:
-    - Mostrar información del cliente
-    - Permitir el cambio de precio
-    - Permitir el reemplazo de productos
-    - Permitir el rechazo de productos
-    - Limitar la cantidad de recolección de ítems
-    - Permitir el empaquetado
-4. En **Motivos**, en _Motivos de reemplazo_, rellena el campo con el nombre de la opción que identificará un motivo de reemplazo válido y pulsa `Entrar`. Repite el proceso para agregar tantas etiquetas como quieras.
-5. En _Motivos de cambio de precio_, rellena el campo con el nombre de la opción que identificará el motivo de los cambios y pulsa `Entrar`. Repite el proceso para agregar tantas etiquetas como quieras.
-6. Rellena el campo _Límite de cambios_ con el número de cambios que se pueden realizar por pedido.
-7. En **Orden de prioridad**, elige el nivel de prioridad en el nivel del árbol de categorías para ordenar los ítems en el proceso de recolección. Puedes elegir entre `1` (categorías principales) o `2` (categorías secundarias).
-8. Haz clic en el botón `Guardar`.
+### Filtro de Búsqueda
 
-### Configuración de categorías
+Además, cuenta con un filtro de búsqueda que permite encontrar los pedidos según la necesidad del usuario.
 
-En esta pestaña, encontrarás categorías y subcategorías que deben enumerarse según las prioridades del modelo de negocio de la tienda.
+![pick and pack 21](//images.ctfassets.net/alneenqid6w5/T6d3roLMCvoOMi52X7KMJ/3faf3580c22a2c289ff7aeef7c2ffc7f/image59.png)
 
-Las acciones que puedes realizar son:
+## Configuración de la aplicación
 
-- **Cambiar prioridad:** haz clic en la categoría y arrástrala a la posición deseada.
-- **Eliminar categoría:** haz clic en el ícono de la papelera &lt;insert_icon> y luego en `Sí, eliminar`. Esta acción hará que la categoría desaparezca de la lista y aparezca junto a ella, bajo _Prioridad de la categoría/recolección_.
-- **Agregar categoría:** si se ha eliminado una categoría, aparecerá en _Prioridad de la categoría/recolección_, y podrás agregarla a la lista haciendo clic sobre ella.
+Entra al panel de administrador de tu tienda VTEX utilizando tus credenciales de acceso. Después, en el menú **Pick and Pack,** haz clic en la opción **Configuración.**
 
-Después de cambiar la lista de prioridades, haz clic en `Guardar`.
+Una vez dentro, encontrarás varias opciones que te permitirán personalizar los siguientes procesos:
 
-### Configuración de paquetes
+- Alistamiento
+- Categorías de los productos
+- Empaquetado
+- Pedidos
+- Automatización
+- Usuarios
+- Catálogo
+- Instalaciones
 
-En esta pestaña, controlas los paquetes utilizados para entregar el pedido y puedes crear o eliminar un paquete.
+### Configuración y alistamiento
 
-Para crear un paquete, haz lo siguiente:
+La estrategia de alistamiento está estructurada por olas, e incluye:
 
-1. Haz clic en `Agregar nuevo`.
-2. Introduce el nombre que identificará el paquete.
-3. Rellena las medidas del paquete: altura, anchura y longitud, utilizando solo números.
+- Cambios en los pedidos.
+- Motivos de reemplazo y rechazo.
+- Motivos de cambio de precio.
+- Límite de cambios de cantidad de ítems en el pedido.
+- Límite de cambios de precio en ítems del pedido.
+- Límite total de cambios en los pedidos.
+- Hojas de trabajo.
+- Tags de hojas de trabajo.
+- Activar códigos EAN dinámicos.
 
-  <div class = "alert alert-info">
-La unidad de medida es la configurada en la pestaña General, en <b>Unidades de medida</b>.
+<div class = "alert alert-info">
+Alistamiento por olas significa que a medida que van llegando los pedidos estos pueden alistarse.
 </div>
 
-4. Haz clic en `Agregar`.
-
-Para eliminar un paquete, haz clic en la fila de ese paquete y, a continuación, haz clic en `Sí, eliminar`.
-
-### Configuración de envío
-
-En esta pestaña, asocias un servicio [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) a tu tienda, lo que te permite seguir el status y la ubicación con actualizaciones en tiempo real, mientras tu flota interna de entregadores entrega los pedidos a los clientes.
+### Cambios en los pedidos
 
-Si el botón **Last Mile** está desactivado, no hay opciones de configuración. Para empezar a utilizar Last Mile, sigue los pasos a continuación.
+Activar o desactivar las siguientes funciones:
 
-1. Activa el botón haciendo clic sobre él.
-2. En **Transportadora asociada**, selecciona el nombre de la transportadora.
-3. Si no deseas activar la asignación automática de entregadores al crear servicios de envío, deja el botón desactiva y haz clic en `Guardar`.
-4. Si deseas activar la asignación automática de entregadores, activa el interruptor `Asignación automática de entregadores`.
-5. En _Tipo de asignación_, selecciona la regla de asignación para elegir los entregadores, que puede ser:
-    - **Uno a la vez:** la notificación de servicio se envía al entregador que esté más cerca del punto de recogida. Si el primer entregador no acepta el servicio dentro del plazo de la solicitud, el servicio se enviará al siguiente entregador más cercano, y así sucesivamente. Si ningún entregador acepta la tarea, permanece sin asignar.
-    - **Enviar a todos:** todos los entregadores disponibles y en la zona horaria del servicio reciben la notificación, con un límite de 500 entregadores. El servicio se asigna al primer entregador que lo acepte, y permanece sin asignar hasta que alguien lo acepte.
-    - **Round robin:** dentro de un radio determinado, se realiza una asignación por turnos rotativos, o round robin — un algoritmo para programar y asignar recursos — al entregador. Puedes elegir las siguientes opciones:
-        - Asignar servicios a usuarios desconectados
-        - Reiniciar asignación si el servicio es rechazado
-        - Priorizar entregadores sin servicios
-        - Dar prioridad a los repartidores con plazos de entrega más cortos
-    - **El más cercano:** se asigna la tarea al entregador disponible más cercano al punto donde se recogerá el pedido.
-6. Rellena el campo _Expira en (segundos)_ con x, utilizando solo números.
-7. Rellene el campo _Número de reintentos_ con x, utilizando solo números.
-8. Haz clic en `Guardar`.
+- Enviar cambios al OMS
+- Permitir cambiar el precio de los ítems
+- Permitir reemplazo de ítems
+- Permitir rechazar ítems
+- Permitir editar las cantidades de los ítems
+- Permitir agregar observaciones en el pedido
+- Permitir agregar observaciones en los ítems
 
-### Configuración de impresión
+### Motivos de rechazo y motivos de cambios de precio
 
-En esta pestaña se configuran las preferencias de [impresión](#imprimir-recibo-y-comprobante), organizadas en las siguientes secciones:
+Permiten configurar las opciones que el sistema va a habilitar dentro de la aplicación Pick and Pack. Solo debes hacer clic sobre los campos para crearlos o eliminarlos del listado.
 
-- **Recibo:** el recibo del pedido.
-- **Etiqueta del paquete:** la etiqueta que aparece en los productos y que se puede escanear en el proceso de recolección.
-- **Etiqueta de envío:** la etiqueta con la dirección de envío.
+#### Límite de cambios
 
-En cada una de esas secciones, hay un botón <i class="fas fa-toggle-off"></i> `Desactivado` que debe estar <i class="fas fa-toggle-on"></i> `Activado` para que la configuración sea válida.
+Los límites de cambios de cantidad y precio de ítems en el pedido te permiten configurar el porcentaje (%) aceptado por cada tienda.
 
-Una vez que hayas terminado de definir la configuración de impresión, haz clic en `Guardar`.
+#### Hojas de trabajo para habilitar o deshabilitar las siguientes funciones:
 
-### Configuración de webhook
+- Permitir varios pedidos en una hoja de trabajo
+- Activar alistamiento rápido
+- Activar express fulfillment
+- Permitir mover pedidos una vez iniciado el alistamiento
+- Permitir mover pedidos entre hojas de trabajo
 
-En esta pestaña, puedes configurar un webhook para recibir notificaciones sobre los cambios dl status de los pedidos y obtener información sobre un pedido determinado.
+#### Tags de hojas de trabajo
 
-<div class = "alert alert-info">
-Para más información, consulta nuestra documentación de <a href="https://developers.vtex.com/docs/guides/vtex-pick-and-pack">VTEX Pick and Pack</a> para desarrolladores.
+<div class="alert alert-warning">
+Solo debes hacer clic sobre el campo para crearlo o eliminarlo del listado.
 </div>
 
-## Usuarios
+Las tags ayudan como identificadores de las hojas de trabajo para poder realizar configuraciones, filtros o asignaciones  necesarias dentro del sistema.
 
-En **VTEX Pick and Pack**, la página **Usuarios** permite gestionar los perfiles implicados en el proceso de fulfillment, denominados _usuarios_. Hay tres tipos de usuarios:
+#### Activar códigos EAN dinámicos
 
-| **Usuario** | **Descripción** | **Permiso** |
-| ---------- | ---------- | ---------- |
-| Entregador | La persona responsable de la recolección. | <ul><li>Acceso a la aplicación, ya sea en versión móvil o web (no funciona sin conexión).</li><li>No tiene acceso al Admin.</li></ul> |
-| Atención al cliente | El operador de la tienda que es responsable del pedido y tiene acceso al Admin. | <ul><li>Acceso a todos los pedidos en el Admin.</li><li>Seguir pedidos.</li><li>Comunicarse con los entregadores.</li></ul> |
-| Admin | El rol de administrador permite comprobar los entregadores, gestionar todas las configuraciones y el flujo de pedidos, incluida la cancelación de pedidos, si es necesario. | Todos los permisos concedidos al usuario de atención al cliente, excepto: <ul><li>Gestionar todas las configuraciones.</li><li>Gestionar el flujo de pedidos, incluida la cancelación de pedidos.</li></ul> |
+Existen tres tipos: precio, peso y cantidad. La configuración se compone de:
 
-### Usuarios y License Manager en VTEX Fulfillment
+- **Prefijo:** corresponde al identificador que el sistema va a tomar en el momento de asociar los EAN dinámicos.
+- **Identificador del ítem:** corresponde al tipo de identificador que el sistema va a tomar (RefID o SKU) para los identificadores.
+- **Decimales:** cantidad de decimales que soporta.
+- **Prueba:** permite verificar que la configuración esté correcta.
 
-El concepto de _usuario_ en **VTEX Pick and Pack** es diferente del significado común del término en VTEX. En **VTEX Fulfillment**, hay tres tipos de usuarios que participan en el proceso de fulfillment: entregador, atención al cliente y administrador. Generalmente, en VTEX, los usuarios están relacionados con [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) y [características de License Manager](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
-
-Para acceder a **VTEX Fulfillment**, los usuarios administradores y de atención al cliente deben tener permisos relacionados con las funciones de License Manager. Recomendamos [crear un rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) identificado como «_Admin de fulfillment», _que debe tener al menos los siguientes productos y recursos asociados:
+<div class = "alert alert-info">
+Puedes seleccionar los tres tipos de configuraciones para la tienda.
+</div>
 
-| **Producto** | **Recursos asociados** |
-| ---------- | ---------- |
-| Insights | <ul><li>Insights metrics</li></ul> |
-| License Manager | <ul><li>Get account by identifier</li><li>Obtener aplicaciones</li><li>Find user by email</li><li>View users with account access</li><li>View all admin users</li><li>Get resource by key</li><li>Get role</li><li>Get paged roles</li><li>Get paged users</li><li>Get admin status</li><li>Get accounts</li><li>Get accounts by host</li></ul> |
+<div class = "alert alert-info">
+Si quieres eliminar un tipo puedes hacerlo dentro del campo haciendo clic sobre la X que lo acompaña.
+</div>
 
-### Acciones en la página Usuarios
+<div class="alert alert-danger">
+EAN dinámico es un código que se genera con el peso del producto para calcular el precio.
+</div>
 
-En la página **Usuarios**, puedes realizar las siguientes acciones:
+### Configuración de categorías
 
-- [Agregar un usuario entregador](#agregar-un-usuario-entregador)
-- [Agregar un usuario de atención al cliente](#agregar-un-usuario-de-atencion-al-cliente)
-- [Agregar un usuario administrador](#agregar-un-usuario-admin)
-- [Editar usuario](#editar-usuario)
-- [Generar clave API](#generar-clave-api)
-- [Eliminar usuario](#eliminar-usuario)
+Aquí puedes realizar la configuración de las categorías que van a estar disponibles en la tienda, permitiendo importarlas y exportarlas. Esta configuración se realiza por Instalación.
 
-#### Agregar un usuario entregador
+También puedes definir el orden de alistamiento preferido para cada instalación. Este orden de alistamiento se aplica a todas las hojas de trabajo de una instalación específica.
 
-Para crear un nuevo _entregador_, sigue los pasos a continuación:
+La opción **Configuración rápida** replica la configuración de todas las Instalaciones asociadas a la tienda.
 
-1. En tu Admin VTEX, ve a **Apps > Fulfillment > Usuarios**.
-2. En el menú superior <i class="fas fa-ellipsis-v"></i>, haz clic en `Agregar entregador`.
-3. Rellena la siguiente información:
-    - **Nombre:** el nombre completo del entregador.
-    - **Email:** email del entregador.
-    - **Usuario:** nombre de usuario que identificará el entregador.
-    - **Contraseña:** la contraseña que necesitará el entregador para identificarse y autenticarse en la aplicación. La contraseña debe tener al menos:
-        - Una letra mayúscula
-        - Una letra minúscula
-        - Un número
-    - **Tiendas:** selecciona el entorno al que se asociará el entregador. Cada entorno puede tener múltiples [sellers white label](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) asociados.
-    - **Categorías:** selecciona hasta cuatro categorías relacionadas con los productos que recogerá el entregador.
+### Configuración de empaquetado
 
-  <div class = "alert alert-info">
-Las categorías relacionadas con el entregador optimizan el algoritmo a la hora de determinar qué entregador recibirá el pedido. Sin embargo, no es una limitación: cualquier entregador puede ser asignado a servicios relacionados con todas las categorías.
-</div>
+La configuración de empaquetado e impresión incluye: 
 
-4. Haz clic en `Guardar usuario`.
+- Permitir informes sobre paquetes.
+- Permitir empaquetado automático.
+- Configuración de impresión de etiquetas de paquetes.
+- Configuración de impresión de recibos.
+- Sobres.
 
-#### Agregar un usuario de atención al cliente
+La configuración de impresión de etiquetas de los paquetes te permite realizar los ajustes de la hoja de impresión: 
 
-Solo los [usuarios administradores](#usuarios-y-license-manager-en-vtex-fulfillment) pueden crear nuevos _usuarios de atención al cliente_. Para ello, sigue los pasos a continuación:
+- Formato
+- Tamaño de la fuente
+- Márgenes
+- Dimensiones
 
-1. En tu Admin VTEX, ve a **Apps > Fulfillment > Usuarios**.
-2. En el menú superior <i class="fas fa-ellipsis-v"></i>, haz clic en `Agregar usuario de atención al cliente`.
-3. En el campo de búsqueda, busca introduciendo el nombre, email o ID del usuario.
-4. Haz clic en `Confirmar`.
+La configuración de sobres te permite crear el tipo de empaque de la tienda.
 
-#### Agregar un usuario Admin
+En el momento de crearlos, el sistema proporciona los campos de configuración del paquete, que incluyen: 
 
-Solo un [usuario administrador](#usuarios-y-license-manager-en-vtex-fulfillment) puede crear nuevos _usuarios de atención al cliente_. Para ello, sigue los pasos a continuación:
+- **Nombre.**
+- **Tipo:* permite seleccionar si son bolsas, cajas, sobres, etc.
+- **Código:** corresponde a la identificación que maneja la tienda.
+- **Medidas.**
 
-1. En tu Admin VTEX, ve a **Apps > Fulfillment > Usuarios**.
-2. En el menú superior <i class="fas fa-ellipsis-v"></i>, haz clic en `Agregar administrador`.
-3. En el campo de búsqueda, busca introduciendo el nombre, email o ID del usuario.
-4. Haz clic en `Confirmar`.
+### Configuración de pedidos
 
-#### Editar usuarios
+La configuración de pedidos te permite habilitar la descarga de pedidos del OMS, teniendo en cuenta las siguientes configuraciones:
 
-Puedes editar cualquier tipo de usuario para cambiar la información a continuación.
+- Medios de pago.
+- Métodos de envío.
+- Tipo de envío.
+- Tags del pedido.
 
-- Nombre
-- Contraseña
-- Categorías
-- Tienda
+### Configuración de automatización
 
-Para editar un usuario, sigue los pasos a continuación:
+Esta configuración permite crear, editar y eliminar usuarios de Pick and Pack.
 
-1. En tu Admin VTEX, ve a **Apps > Fulfillment > Usuarios**.
-2. En la fila correspondiente al usuario que deseas editar, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
-3. Selecciona la opción `Editar`.
-4. Cambia los campos deseados.
-5. Introduce la contraseña.
-6. Haz clic en `Guardar`.
+Podemos asignar el rol Admin a los usuarios que se encuentran habitados.
 
-#### Generar clave API
+También podemos crear usuarios Alistadores, asignarles instalaciones, realizar el proceso de empaquetado y asignación de categorías.
 
-Los [usuarios administradores](#usuarios-y-license-manager-en-vtex-fulfillment) pueden generar claves API para utilizar las API de **VTEX Pick and Pack**. Para más información, consulta nuestra [documentación para desarrolladores](https://developers.vtex.com/docs/guides/vtex-pick-and-pack).
+### Configuración de instalaciones
 
-Para generar una clave API, sigue los pasos a continuación:
+Para la gestión del usuario alistador, es importante la asignación de instalaciones (facilities), debido a que esto le permitirá ver los pedidos asociados y así podrá realizar la gestión del alistamiento.
 
-1. En tu Admin VTEX, ve a **Apps > Fulfillment > Usuarios**.
-2. En la fila correspondiente a un usuario administrador, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
-3. Selecciona la opción `Editar`.
-4. Haz clic en `Generar`.
-5. Guarda la clave API en un lugar seguro.
+Los alistadores pueden vincularse a una o varias instalaciones.
 
-  <div class="alert alert-danger">
-La clave API solo se mostrará una vez. No podrás volver a acceder a esta información, así que debes asegurarte de guardarla en un lugar seguro.
+<div class = "alert alert-info">
+Instalación: es el lugar físico donde existen alistadores recolectando productos.
 </div>
 
-6. Introduce la contraseña.
-7. Haz clic en `Guardar`.
+### Configuración de catálogo
+
+Te permite tener sincronizado el catálogo de VTEX con el de Pick and Pack.
 
- #### Eliminar usuarios
+Si existen nuevos productos dentro del catálogo se debe indexar el catálogo.
 
-Solo los usuarios administradores pueden eliminar otros usuarios. Esto se puede hacer siguiendo los pasos a continuación:
+Además, incluimos la opción de agregar más EAN a los productos e indicar si son productos que deben mantenerse a temperatura ambiente, fríos o congelados.
 
-1. En tu Admin VTEX, ve a **Apps > Fulfillment > Usuarios**.
-2. En la fila correspondiente al usuario que deseas editar, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
-3. Selecciona la opción `Eliminar`.
-4. Haz clic en `Guardar`.
diff --git a/docs/tutorials/es/vtex-pick-and-pack-insights.md b/docs/tutorials/es/vtex-pick-and-pack-insights.md
new file mode 100644
index 000000000..4196670b0
--- /dev/null
+++ b/docs/tutorials/es/vtex-pick-and-pack-insights.md
@@ -0,0 +1,66 @@
+---
+title: 'VTEX Pick and Pack: Análisis'
+id: 5C4wXYmbbHTnMAUO0o11rn
+status: PUBLISHED
+createdAt: 2024-01-05T17:27:08.558Z
+updatedAt: 2024-01-05T20:28:40.388Z
+publishedAt: 2024-01-05T20:28:40.388Z
+firstPublishedAt: 2024-01-05T20:24:02.931Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-analisis
+locale: es
+legacySlug: vtex-pick-and-pack-analisis
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
+</div>
+
+**Análisis** es una página del Admin VTEX que muestra información sobre el desempeño de tu tienda en relación con VTEX Pick and Pack.
+
+![pick-pack-insights-es](//images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/acdc7944f550df2f4aef7ed7102deb7a/image.png)
+
+La página presenta las siguientes secciones:
+
+* [Pedidos - Total en el periodo actual](#pedidos-total-en-el-periodo-actual)
+* [Tiempo de las etapas](#tiempo-de-las-etapas)
+* [Pedidos - Desempeño de pedidos](#pedidos-desempeno-de-pedidos)
+* [Ítems](#items)
+
+## Pedidos - Total en el período actual
+
+En esta sección puedes consultar el número total de pedidos y hojas de trabajo para un periodo determinado y en unas instalaciones determinadas. Puedes seleccionar los siguientes periodos:
+
+* Último día
+* Últimos siete días
+* Mes pasado
+* Últimos tres meses
+* Últimos seis meses
+
+![pick-pack-insights-2-es](//images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/53d44d3093593ddea822acdeffd09776/image.png)
+
+## Tiempo de las etapas
+
+En esta sección puedes consultar información sobre la duración de cada etapa del proceso de preparación de pedidos. Puedes ver el tiempo empleado en cada una de las siguientes etapas:
+
+* Tiempo de alistamiento
+* Tiempo de empaque
+* Tiempo de envío
+
+![pick-pack-insights-3-es](//images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/e30499f47212c9a0019715c6d9dfb927/image.png)
+
+## Pedidos - Desempeño de pedidos
+
+En esta sección tendrás acceso a información sobre el rendimiento global de los pedidos y el tiempo promedio de fulfillment de cada uno.
+
+![pick-pack-insights-4-es](//images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/5bd9362932a056895c1c10b6973ce6a8/image.png)
+
+## Ítems
+
+En esta sección puedes consultar información sobre los ítems de pedidos gestionados en VTEX Pick and Pack, el tiempo promedio de alistamiento por ítem, el número de ítems seleccionados por alistador y la tasa de fulfillment de pedidos.
+
+![pick-pack-insights-5-es](//images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/d81f53b9f063002e607e358ac645d3f3/image.png)
+
diff --git a/docs/tutorials/es/vtex-pick-and-pack-last-mile.md b/docs/tutorials/es/vtex-pick-and-pack-last-mile.md
index c3d1e8026..3f977efd6 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-last-mile.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack: Last Mile'
 id: HN7WKV0xoq2ssVjsJlfzr
 status: PUBLISHED
 createdAt: 2023-04-10T16:01:14.613Z
-updatedAt: 2023-04-20T15:46:42.209Z
-publishedAt: 2023-04-20T15:46:42.209Z
+updatedAt: 2023-08-25T15:52:19.799Z
+publishedAt: 2023-08-25T15:52:19.799Z
 firstPublishedAt: 2023-04-10T16:35:43.623Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -16,3 +16,8 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
 <div class="alert alert-warning" role="alert">Contenido bajo traducción.</div>
+
+<div class = "alert alert-info">
+Si tienes interés en implementarla en tu negocio, rellena nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> indicando en el campo <code>Comentarios</code> el nombre del producto deseado.
+</div>
+
diff --git a/docs/tutorials/es/vtex-pick-and-pack-mobile.md b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
new file mode 100644
index 000000000..fd26c9de1
--- /dev/null
+++ b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
@@ -0,0 +1,224 @@
+---
+title: 'VTEX Pick and Pack Mobile'
+id: 3i1K01CQlDBFYYp42WFOet
+status: PUBLISHED
+createdAt: 2024-04-04T20:42:46.548Z
+updatedAt: 2024-04-06T02:45:49.741Z
+publishedAt: 2024-04-06T02:45:49.741Z
+firstPublishedAt: 2024-04-06T01:59:46.300Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-mobile
+locale: es
+legacySlug: vtex-pick-and-pack-mobile
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+<p>Si ya es cliente de VTEX y desea adoptar esta funcionalidad para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+La aplicación móvil de [VTEX Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) ayuda al alistador (profesional responsable de seleccionar y empacar los ítems en la instalación) en la preparación de los pedidos, desde el alistamiento de los ítems hasta el envío. Esto hace que el flujo de alistamiento y envío de los pedidos de la tienda sea más organizado y fluido.
+
+![pickpack-mobile-es](//images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/b4c69a98c2576d0f90e9b676d41b7ac6/image.png)
+
+La preparación de pedidos se divide en cuatro etapas, que siguen el flujo habitual de los pedidos en la tienda:
+
+- [Crear hoja de trabajo](#crear-hoja-de-trabajo)
+- [Alistamiento de productos](#alistamiento-de-productos)
+- [Empaque del pedido](#empaque-del-pedido)
+- [Envío de los paquetes](#envio-de-los-paquetes)
+
+## Hojas de trabajo
+
+Una hoja de trabajo consiste en un conjunto de pedidos que serán procesados por el flujo de Pick and Pack simultáneamente. Este enfoque permite una gestión eficiente, agilizando el procesamiento simultáneo de múltiples pedidos.
+
+Por ejemplo, considera una hoja de trabajo que incluya solamente tres pedidos:
+
+- Pedido 1: una camiseta roja y una falda rosa.
+- Pedido 2: dos camisetas rojas y un sombrero blanco.
+- Pedido 3: una falda rosa y un sombrero blanco.
+
+Al seleccionar esta hoja de trabajo para su preparación, la aplicación indicará el alistamiento de:
+
+- Tres camisetas rojas.
+- Dos faldas rosas.
+- Dos sombreros blancos.
+
+A continuación, la aplicación dará soporte para el empaque de cada pedido con sus respectivos ítems.
+
+<div class="alert alert-warning">
+Las hojas de trabajo solo se aplican a las etapas de alistamiento y empaque de los pedidos. Los envíos de cada pedido deben realizarse por separado.
+</div>
+
+## Crear hoja de trabajo
+
+La pestaña Sin asignar muestra en una lista los pedidos que deben seleccionarse para agregarlos a las hojas de trabajo. 
+
+![pickpack-ordemservico-es](//images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/d09cf0ea6e858d28afebb79b55999e31/image.png)
+
+Para agregar una hoja de trabajo sigue los pasos a continuación:
+
+En la pantalla de inicio, haz clic en Sin asignar <i class="fas fa-arrow-right"></i>.
+Selecciona los pedidos que deseas incluir en la hoja de trabajo. Para crear una hoja de trabajo con todos los pedidos, haz clic en <i class="fas fa-square"></i> `Seleccionar todos`.
+Haz clic en `Empezar a alistar`.
+
+## Alistar productos
+
+La etapa de alistamiento consiste en seleccionar físicamente los ítems de una [hoja de trabajo](#hojas-de-trabajo) y llevarlos a la zona adecuada de tu instalación para su posterior empaque.
+
+### Hojas de trabajo pendientes
+
+La pestaña __Pendientes__ muestra la lista de hojas de trabajo cuyo alistamiento no ha finalizado.
+
+![pickpack-pendente-es](//images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/ff9f1a49db76f2032e7021971bf15cad/image.png)
+
+En esta pestaña, puedes seleccionar por el ID de una hoja de trabajo si deseas que se muestren solamente los ítems ya alistados de ese pedido.
+
+Si hay hojas de trabajo asignadas al alistador, puedes acceder a ellas desde la pantalla de alistamiento siguiendo estos pasos:
+
+1. En la pantalla de inicio de la aplicación, haz clic en **Continuar alistando**. Aparecerá una lista con las [hojas de trabajo](#hojasdetrabajo) asignadas al alistador que están en fase de alistamiento.
+2. Haz clic en la hoja de trabajo que deseas alistar.
+
+Al hacer clic en una hoja de trabajo se mostrará la siguiente información:
+
+- __Ítems:__ productos que deben alistarse de la hoja de trabajo.
+- __Información:__ información general sobre la hoja de trabajo y el pedido.
+- __Resumen:__ productos ya alistados por el alistador.
+
+![pickpack-em-separacao-es](//images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/acafdfb2d52a575eb150dbd8ad3e4bc8/image.png)
+
+Al hacer clic en el menú <i class="fas fa-ellipsis-v"></i>, se mostrarán las siguientes acciones:
+
+- **Agregar observación:** agrega una observación a la hoja de trabajo.
+- **Listo para empaque:** utilizado para alistar o rechazar pedidos en masa.
+- **Pausar alistamiento:** pausa la cuenta atrás del tiempo disponible para el alistamiento de la hoja de trabajo.
+- **Abrir lector de código de barras:** utiliza la cámara del dispositivo para leer los códigos de barras de los productos.
+- **Imprimir lista de alistamiento:** disponibiliza un documento con la lista de ítems de la hoja de trabajo para impresión.
+- **Cerrar menú:** cierra el menú y vuelve a la pantalla de alistamiento. 
+
+Para alistar un producto sigue estos pasos:
+
+1. En la pantalla de __Alistamiento__, accede a la pestaña __Ítems__.
+2. Haz clic en el producto que deseas alistar o desliza el producto hacia la derecha. Si el producto tiene más de una unidad, haz clic en la cantidad de unidades del producto. Para productos que contienen peso o volumen, debes confirmar la medida y, a continuación, confirmar la selección, como en el ejemplo a seguir:
+![pickpack-item-es](//images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/efdd37c986299e346a325606885a1218/image.png)
+
+## Para alistar todos los productos de la hoja de trabajo de una sola vez, sigue estos pasos:
+
+1. Haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
+2. Haz clic en la opción **Listo para empaque.** 
+3. Haz clic en **Alistar todos los ítems disponibles.**
+
+Una vez alistados, los productos aparecen en la pestaña __Resumen__.
+
+## Rechazar ítems
+
+Hay situaciones en las que puede ser necesario rechazar productos debido a la configuración de la tienda y a la disponibilidad de ítems en stock. 
+
+<div class="alert alert-warning">
+La opción Rechazar ítems puede no estar disponible. En caso de duda, ponte en contacto con la gerencia de la tienda.
+</div>
+
+Para rechazar un producto de la hoja de trabajo sigue los pasos que se indican a continuación:
+
+1. Accede a la pestaña __Ítems__.
+2. Haz clic y desliza hacia la izquierda el producto que deseas descartar.
+3. Selecciona el motivo del rechazo en la lista **Motivos de rechazo**.
+4. Selecciona el número de unidades que deseas rechazar o haz clic en `Confirmar y descartar todas las unidades`.
+5. Haz clic en `Descartar unidades`.
+
+Para descartar todos los productos de la hoja de trabajo de una sola vez, sigue estos pasos:
+
+1. Haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
+2. Haz clic en la opción **Listo para empaque.** 
+3. Haz clic en **Descartar todos los ítems disponibles.**
+
+<div class="alert alert-danger">
+Si se descartan todos los ítems de un pedido, el pedido se completará automáticamente.
+</div>
+
+## Reemplazar ítems
+
+Otra opción para ítems no disponibles es sustituirlos por otros, dependiendo de la configuración de la tienda y de la disponibilidad de los ítems en stock.
+
+<div class="alert alert-warning">
+La opción Rechazar ítems puede no estar disponible. En caso de duda, ponte en contacto con la gerencia de la tienda.
+</div>
+
+Para reemplazar ítems de la hoja de trabajo sigue los pasos que se indican a continuación:
+
+1. Accede a la pestaña __Ítems__.
+2. Pulsa sobre el producto que deseas sustituir.
+3. Haz clic en la opción **Reemplazar ítem**.
+4. Busca o selecciona el ítem que sustituirá al producto en el pedido y haz clic en la casilla de selección <i class="fas fa-check-square"></i>. 
+5. Selecciona el número de unidades que deseas reemplazar.
+6. Selecciona el motivo de reemplazo en la lista de opciones.
+7. Rellena el campo **Descripción** para agregar más información sobre el reemplazo.
+8. Pulsa el botón `Confirmar reemplazo`.
+
+## Finalizar alistamiento
+
+Una vez alistados, rechazados o reemplazados todos los ítems de la hoja de trabajo, haz clic en el botón `Iniciar empaque` para que la hoja de trabajo pase a la etapa [empaque](#empaque).
+
+## Empaque
+
+En la etapa de empaque, el alistador selecciona los ítems de cada pedido en los respectivos embalajes de envío. La aplicación móvil de Pick and Pack permite la organización de todos los paquetes necesarios para los diversos pedidos de manera rápida y sencilla.
+
+![pickpack-empacotamento-es](//images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/282dc96e07df744684a5775a4c711d92/image.png)
+
+Puedes acceder a la página Empaque al [concluir el alistamiento](#finalizar-alistamiento) de una hoja de trabajo o siguiendo los pasos a continuación:
+
+1. En la pantalla de inicio de la aplicación, haz clic en **Empaque **. Aparecerá una lista con las [hojas de trabajo](#hojas-de-trabajo) asignadas al alistador que están en la etapa de empaque.
+2. Haz clic en la hoja de trabajo cuyos productos deseas empacar. 
+
+![pickpack-item-pendente-es](//images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/d1a0dff72b963012706819c39a88d8c3/image.png)
+
+Sigue los pasos que se indican a continuación para empacar ítems:
+
+1. En __Empaque__, haz clic en el pedido que deseas empacar. 
+2. Haz clic en el botón <i class="fas fa-plus"></i> del producto que deseas agregar al paquete o haz clic en <i class="fas fa-box"></i> para agregar todos los productos a la vez.
+<div class="alert alert-warning">
+Si optas por empacar todos los ítems del pedido, los productos que aún no se hayan empacado se registrarán en un único nuevo empaque.
+</div>
+5. Selecciona un tipo de paquete ya registrado o agrega uno nuevo haciendo clic en `+ Crear paquete`. 
+6. Selecciona el tipo de paquete que deseas agregar.
+7. Selecciona cuántas unidades del producto deseas agregar a ese paquete.
+8. Haz clic en el botón `Empacar producto`.
+
+Repite este procedimiento tantas veces como sea necesario para empacar todos los ítems de una hoja de trabajo.
+
+Los ítems ya empacados están disponibles en la pestaña **Ítems empacados**. Puedes alternar la vista de los ítems entre una lista de ítems o de pedidos y empaques haciendo clic en <i class="fas fa-toggle-on"></i>.
+
+__Lista de ítems__
+![pickpack-item-empacotado-es](//images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/bc3bfe853b3fe8c2f2e7f728f71a67f5/image.png)
+
+__Pedidos y paquetes__
+![pickpack-item-empacotado-2-es](//images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/9d3600f0ac99fe235eb017d0879e0a4a/image.png)
+
+Una vez empacados todos los ítems de la hoja de trabajo, puedes finalizar el empaque en la pestaña __Ítems empacados__ haciendo clic en el botón `Confirmar empaque`.
+
+A continuación, se finalizará el pedido en la aplicación. Dependiendo de la configuración de tu tienda, el alistador puede pasar a la etapa de envío. 
+
+## Envío
+
+La fase de envío permite crear servicios de envío para los pedidos alistados y empacados.
+
+<div class="alert alert-warning">
+El envío es una etapa opcional de la aplicación, dependiendo de tu operación y de la configuración realizada por el administrador de la tienda.
+</div>
+
+Para enviar paquetes desde la aplicación Pick and Pack, sigue los pasos que se indican a continuación:
+
+1. En la pantalla inicial, haz clic en el menú <i class="fas fa-ellipsis-v"></i>.
+2. Haz clic en la opción **A enviar.**
+3. Selecciona el paquete que deseas enviar. Solo puedes seleccionar pedidos con status `Preparando envío`.
+4. Rellena los datos de envío:
+    - **Fecha prevista de recolección**
+    - **Fecha prevista de entrega**
+    ![pickpack-envio-es](//images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/bf144c5d0a68fef03cab3c2a7db92d33/image.png)
+5. Selecciona una transportadora disponible.
+6. Haz clic en `Seleccionar y continuar`.
+7. Confirma la información de envío. Si no es necesario hacer correcciones, haz clic en el botón `Crear servicio`. En caso contrario, haz clic en `Atrás` y vuelve al paso 5. 
+
+Una vez completado el registro, la información sobre el envío aparecerá en la siguiente pantalla de la aplicación. Los pedidos enviados están disponibles a través del menú <i class="fas fa-ellipsis-v"></i> __> Finalizado__. 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-orders.md b/docs/tutorials/es/vtex-pick-and-pack-orders.md
new file mode 100644
index 000000000..9505fc371
--- /dev/null
+++ b/docs/tutorials/es/vtex-pick-and-pack-orders.md
@@ -0,0 +1,95 @@
+---
+title: 'VTEX Pick and Pack: Pedidos'
+id: 3rGbJlyedHdbWjvZ52p95b
+status: PUBLISHED
+createdAt: 2023-12-14T17:26:02.135Z
+updatedAt: 2024-01-05T17:31:16.218Z
+publishedAt: 2024-01-05T17:31:16.218Z
+firstPublishedAt: 2023-12-19T15:00:12.093Z
+contentType: tutorial
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-pedidos
+locale: es
+legacySlug: vtex-pick-and-pack-pedidos
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
+</div>
+
+**Pedidos** es una página del Admin VTEX que muestra información sobre los pedidos realizados y gestionados por [VTEX Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU).
+
+Esta página te permite realizar las siguientes acciones:
+
+* [Consultar pedidos](#consultar-pedido) 
+* [Buscar pedidos](#buscar-pedido) 
+* [Filtrar pedidos](#filtrar-pedidos) 
+* [Exportar pedidos](#exportar-pedidos)
+
+![pick-and-pack-pedidos-ES](//images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/0b19e96e2057462deca476086792e17d/image.png)
+
+La página presenta la siguiente información en forma de tabla: 
+
+| Campo de la tabla | Descripción                                                                                            |
+| ----------------- | ------------------------------------------------------------------------------------------------------ |
+| ID del pedido     | Número de identificación del pedido. También indica la fecha en que fue creado.                        |
+| Facturas          | Status de facturación del pedido, con los siguientes valores posibles: **Facturado** y **No facturado**.       |
+| Items             | Número de ítems que componen el pedido.                                                                |
+| Envío             | Tipo de envío del pedido, con los siguientes valores posibles **Entrega al cliente** y **Recogida en tienda**. |
+| Pago              | Medio de pago utilizado para realizar el pedido.                                                       |
+| Tags              | Tags relacionadas con el pedido, como UTM o uso de cupones.                                            |
+| Fecha de entrega  | Fecha de entrega o recogida del pedido.                                                                |
+| Status            | Etapa del proceso de fulfillment del pedido.                                                           |
+
+## Consultar pedido
+
+Puedes optimizar la consulta de pedidos desde las siguientes secciones: 
+
+* **Todos:** todos los pedidos realizados.
+* **Pendientes:** pedidos pendientes, ítems listos para alistar y en preparación.
+* **A enviar:** pedidos listos para envío.
+* **Entregados:** pedidos que han sido entregados al cliente, ya sea por recogida en tienda o por la transportadora.
+* **Cancelados:** pedidos cancelados.
+* **Rechazados:** pedidos rechazados.
+
+También puedes acceder a información más detallada sobre cada pedido haciendo clic en el pedido en la tabla.
+
+![pick-and-pack-pedidos-2-ES](//images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/8307fcdea5832aa1a653f812c0eaba02/image.png)
+
+Al seleccionar el pedido deseado, se mostrará la siguiente información:
+
+* **Ítems:** lista de ítems que componen el pedido. Puedes buscar un ítem ingresando el ID del SKU o el nombre del ítem en la barra de búsqueda. También puedes hacer clic en el ítem para acceder a información más detallada.
+* **Observaciones del pedido:** observaciones que el retailer agregó al pedido.
+* **Información de envío:** información sobre el envío del pedido, incluido el status del envío.
+* **Información de pago:** información sobre el pago del pedido.
+* **Información adicional:** información adicional del pedido.
+* **Logs:** línea de tiempo con el historial de actualizaciones del pedido.
+
+## Buscar pedido
+
+Puedes buscar un pedido utilizando la barra de búsqueda. Ingresa el ID del pedido en la barra de búsqueda, como en este ejemplo: `SLR-1341470502250-01`. 
+
+## Filtrar pedidos
+
+Puedes refinar la búsqueda y visualización de pedidos seleccionando la opción **Filtrar**. Filtra los pedidos utilizando las siguientes opciones:
+
+* **Fecha de creación:** selecciona la fecha de creación del pedido.
+* **Fecha de entrega:** selecciona la fecha en que se entregó el pedido.
+* **Categorías:** selecciona la categoría de los ítems del pedido.
+* **Medios de pago:** selecciona el medio de pago utilizado en el pedido.
+* **Estrategia de envío:** selecciona la estrategia de envío utilizada en el pedido.
+* **Método de envío:** selecciona el método de envío utilizado en el pedido.
+
+Haz clic en `Limpiar filtros` para remover los filtros seleccionados.
+
+## Exportar pedidos
+
+Puedes exportar pedidos siguiendo los pasos a continuación:
+
+1. Haz clic en `Exportar`.
+2. Selecciona los datos que deseas exportar: `Informe de paquetes` o `Informe de pedidos`.
+    - En el caso de `Informe de paquetes`, debes seleccionar el periodo que deseas exportar, el tipo y el método de envío.
+    ![pick-and-pack-pedidos-3-ES](//images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/ab4c8bcb38a8ab892c57aeeec869dac8/image.png)
+3.  Haz clic en `Exportar`.
diff --git a/docs/tutorials/es/vtex-pick-and-pack-settings.md b/docs/tutorials/es/vtex-pick-and-pack-settings.md
new file mode 100644
index 000000000..425899098
--- /dev/null
+++ b/docs/tutorials/es/vtex-pick-and-pack-settings.md
@@ -0,0 +1,269 @@
+---
+title: 'VTEX Pick and Pack: Configuración'
+id: 16cs3e7hWk7c4cSZqe10O9
+status: PUBLISHED
+createdAt: 2024-01-05T20:43:38.480Z
+updatedAt: 2024-01-09T18:30:22.578Z
+publishedAt: 2024-01-09T18:30:22.578Z
+firstPublishedAt: 2024-01-09T16:30:00.192Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-configuracion
+locale: es
+legacySlug: vtex-pick-and-pack-configuracion
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
+</div>
+
+__Configuración__ es una página del Admin VTEX donde puedes realizar los ajustes de VTEX Pick and Pack para tu tienda. Los ajustes se distribuyen en las siguientes secciones:
+
+* [Alistamiento](#alistamiento)
+* [Categorías](#categorias)
+* [Empaque](#empaque)
+* [Pedidos](#pedidos)
+* [Automatización](#automatizacion)
+* [Usuarios](#usuarios)
+* [Catálogo](#catalogo)
+* [Instalaciones](#instalaciones)
+
+## Alistamiento
+
+En esta sección se encuentran los ajustes relativos a la etapa de alistamiento, donde puedes definir las acciones que el alistador puede realizar durante el proceso de alistamiento, incluyendo la notificación de la falta de disponibilidad de un ítem del pedido y la sugerencia de otro para su sustitución.
+
+![pick-and-pack-separacao-es](//images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/c9c4916113ccf7f6252cb17d736a0ba9/image.png)
+
+### Estrategia de alistamiento
+
+En esta sección puedes definir el tipo de estrategia de alistamiento que deseas que realicen los alistadores.
+
+<div class = "alert alert-info">
+  Actualmente solo está disponible la estrategia <strong>Alistamiento por olas</strong>.
+</div>
+
+#### Cambios en el pedido
+
+En esta sección puedes definir acciones relativas a cambios en el pedido, como por ejemplo, debido a ítems fuera de stock.
+
+* **Enviar cambios al OMS:** permite enviar los cambios realizados por el alistador al [OMS de VTEX](https://help.vtex.com/es/tutorial/gerenciamento-de-pedidos-visao-geral--tutorials_201). Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir cambiar el precio de los ítems:** permite que el alistador cambie los precios de los ítems de un pedido. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir reemplazo de ítems:** permite que el alistador sustituya los ítems del pedido que no estaban disponibles. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir rechazar ítems:** permite que el alistador rechace los ítems del pedido que no estén disponibles. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir cambiar las cantidades de los ítems:** permite que el alistador cambie la cantidad de ítems del pedido. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir agregar observaciones en los pedidos:** permite que el alistador añada comentarios en los pedidos, como indicar el motivo de un cambio de precio, por ejemplo. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir agregar observaciones en los ítems:** permite que el alistador añada comentarios en los ítems, como indicar el motivo de rechazo de un ítem, por ejemplo. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Motivos de rechazo:** indica las opciones que el alistador puede seleccionar para justificar el rechazo de ítems del pedido. El alistador puede introducir tantas opciones como desee.
+* **Motivos de cambios de precio:** indica las opciones que el alistador puede seleccionar para justificar el cambio de precio de los ítems del pedido. El alistador puede introducir tantas opciones como desee.
+* **Límite de cambios de cantidad en los ítems del pedido:** porcentaje que limita cuántos ítems se pueden modificar en un pedido. 
+* **Límite de cambios de precio en los ítems del pedido:** porcentaje que limita cuántos precios de ítems se pueden modificar en un pedido. 
+* **Límite total de cambios en los pedidos:** porcentaje que limita la cantidad total de pedidos que se pueden modificar. 
+
+### Hojas de trabajo
+
+En esta sección puedes definir las opciones que se aplicarán a las hojas de trabajo de tu tienda. 
+
+* **Permitir varios pedidos en una hoja de trabajo:** permite añadir varios pedidos a una hoja de trabajo. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Activar alistamiento rápido:** permite activar el alistamiento rápido, confirmando automáticamente la cantidad y el precio de los productos evitando la necesidad de confirmación manual por parte del alistador. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Activar fulfillment express:** activa la opción de fulfillment express, que permite el alistamiento y empaque del pedido simultáneamente. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir mover pedidos una vez iniciado el alistamiento:** permite editar hojas de trabajo incluso una vez iniciado el proceso de alistamiento. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir mover pedidos entre hojas de trabajo:** permite editar las hojas de trabajo moviendo los pedidos agregados entre ellas. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Tags de hojas de trabajo:** permite añadir tags personalizadas para automatizar el proceso de alistamiento de pedidos.
+* **Activar códigos EAN dinámicos:** permite activar códigos de barras dinámicos, que pueden cambiar en función de las características del producto, como el peso. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+
+#### Onboarding
+
+Puedes activar el proceso de configuración de la aplicación VTEX Pick and Pack siguiendo los pasos que se indican a continuación:
+
+1. Haz clic en `Onboarding`.
+2. Haz clic en `Empezar`.
+3. Selecciona las opciones que deseas configurar para la aplicación. Estos ajustes solo se aplicarán en la cuenta principal.
+4. Haz clic en `Siguiente`.
+5. Selecciona las hojas de trabajo que se van a gestionar en la aplicación y el número de alistadores que deseas crear.
+6. Haz clic en `Siguiente`.
+7. Activa <i class="fas fa-toggle-on"></i> los vendedores a los que deseas aplicar los ajustes.
+8. Haz clic en `Finalizado`.
+9. Haz clic en `Cerrar` para finalizar.
+
+Haz clic en `Guardar` para registrar los cambios realizados.
+
+## Categorías
+
+En esta sección puedes configurar el orden de las categorías en las que se alistarán los pedidos. De este modo, el alistador puede organizar el flujo de alistamiento de productos para completar los pedidos con eficacia.
+
+![pick-pack-categorias-es](//images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/2bfcf15ac98f4a83428b918bee4b609b/image.png)
+
+* **Configuración rápida:** los ajustes se aplican en todas las instalaciones. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Instalación**: determina a qué instalación se aplicarán los ajustes de las categorías.
+
+Para agregar una categoría a la lista, haz clic en la categoría que desees. Para reordenar, arrastra la categoría de la lista a la posición deseada.
+
+Puedes importar un archivo CSV o exportar la lista que ya está configurada.
+
+## Empaque
+
+En esta sección se encuentran los ajustes relativos a la etapa de empaque de los ítems del pedido. 
+
+![pick-pack-empacotamento-es](//images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/22169dfbbb7de2d7cb7303533322b609/image.png)
+
+* **Permitir informe de paquetes:** permite la visualización de informe de paquetes. El informe se mostrará en la pantalla **Pedidos**. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+* **Permitir empaque automático:** permite el empaque automático. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
+
+### Configuración de impresión de etiquetas de paquetes
+
+En esta sección puedes configurar las características de la etiqueta que se adjuntará al paquete del pedido. Consulta a continuación las características disponibles: 
+
+* **Configuración de impresión de etiquetas de paquetes activa:** activa o desactiva la posibilidad de editar las características de las etiquetas.
+* **Formato:** determina el formato de la etiqueta.
+* **Tamaño de fuente (px):** determina el tamaño de la fuente en que se imprimirá la etiqueta, en píxeles.
+
+#### Márgenes
+
+* **Izquierdo:** tamaño del margen izquierdo de la etiqueta en milímetros.
+* **Derecho:** tamaño del margen derecho de la etiqueta en milímetros.
+* **Superior:** tamaño del margen superior de la etiqueta en milímetros.
+* **Inferior:** tamaño del margen inferior de la etiqueta en milímetros.
+
+#### Dimensiones
+
+* **Anchura:** anchura de la etiqueta en milímetros.
+* **Altura:** altura de la etiqueta en milímetros.
+
+### Configuración de impresión de recibos
+
+En esta sección puedes configurar las características de la impresión de recibos de los pedidos. Consulta a continuación las características disponibles: 
+
+* **Configuración de impresión de recibos activa:** activa o desactiva la posibilidad de editar las características de los recibos.
+* **Formato:** determina el formato del recibo.
+* **Tamaño de fuente (px):** determina el tamaño de la fuente en que se imprimirá el recibo, en píxeles.
+
+#### Márgenes
+
+* **Izquierdo:** tamaño del margen izquierdo del recibo.
+* **Derecho:** tamaño del margen derecho del recibo.
+* **Superior:** tamaño del margen superior del recibo.
+* **Inferior:** tamaño del margen inferior del recibo.
+
+#### Dimensiones
+
+* **Anchura:** anchura del recibo.
+* **Altura:** altura del recibo.
+
+### Empaques
+
+En esta sección debes registrar los tipos de empaque que utilizará tu tienda para empaquetar y enviar los pedidos. Para registrar un nuevo empaque sigue estos pasos:
+
+1. Haz clic en `Crear`.
+2. Rellena el formulario a continuación:
+   * **Nombre:** nombre asignado al empaque.
+   * **Tipo:** tipo de empaque. Las opciones son **Caja, Bolsa, Paquete, Cinta, Papel, Otros**.
+   * **Descripción:** descripción del empaque para uso interno.
+   * **Código:** código identificador del empaque.
+   * **Peso cúbico:** [peso cúbico](https://help.vtex.com/es/tutorial/como-o-peso-cubado-e-calculado--tutorials_128) del empaque. 
+   * **Altura:** altura del empaque en milímetros. 
+   * **Longitud:** longitud del empaque en milímetros.
+   * **Peso:** peso del empaque en milímetros.
+   * **Anchura:** anchura del empaque en milímetros.
+3. Haz clic en `Guardar` para finalizar.
+
+Haz clic en `Guardar` para registrar los cambios realizados.
+
+## Pedidos
+
+En esta sección puedes configurar los ajustes relacionados con los pedidos procesados por VTEX Pick and Pack.
+
+![pick-pack-config-pedidos-es](//images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/0be9f8f989de78cff2f46369bd1aaa1d/image.png)
+
+* **Descargar pedidos del OMS:** permite exportar pedidos desde el OMS.
+* **Medios de pago:** medios de pago utilizados en los pedidos a exportar.
+* **Métodos de envío:** métodos de envío utilizados en los pedidos a exportar.
+* **Tipo de envío:** tipos de envío utilizados en los pedidos a exportar.
+* **Tags de pedidos:** tags utilizadas en los pedidos a exportar.
+
+Haz clic en `Guardar` para registrar los cambios realizados.
+
+## Automatización
+
+En esta sección puedes configurar los ajustes de automatización de procesos de VTEX Pick and Pack.
+
+![pick-pack-automacao-es](//images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/4bb00e8ac0cbbf07c676b744771372d6/image.png)
+
+Sigue los pasos a continuación para crear una nueva automatización:
+
+1. Haz clic en `Crear`.
+2. Rellena el campo **Nombre** con el nombre de la automatización y **Automatización para** con la opción que deseas automatizar.
+3. Haz clic en `Guardar` para finalizar.
+
+## Usuarios
+
+En esta sección puedes realizar la gestión de usuarios, admins y alistadores de tu operación en VTEX Pick and Pack. Los usuarios con el permiso **Admin** tendrán acceso al Admin VTEX y podrán realizar cambios en la herramienta. Los usuarios con el permiso **Alistador** solo tendrán acceso a la aplicación VTEX Pick and Pack. 
+
+![pick-pack-usuarios-es](//images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/cd858240c58bc74387f052d3fc7fd983/image.png)
+
+Para crear un nuevo usuario sigue los pasos a continuación:
+
+1. Haz clic en `Crear`.
+2. Selecciona el tipo de permiso que deseas para tu nuevo usuario, __Admin__ o __Alistador__.
+3. Registra al usuario seleccionando el permiso que desees: 
+  - Permiso de __Admin__
+    1. De la lista, selecciona al usuario que deseas registrar como Admin.
+    2. Haz clic en Crear.
+    ![pick-pack-usuarios-2-es](//images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/17eeb5d76b1d00afcee928845e3ee0b8/image.png)
+  - Permiso de __Alistador__
+    1. Rellena los siguientes campos del formulario:
+       * Nombre de usuario
+       * Nombre
+       * Email (campo obligatorio)
+       * Contraseña (campo obligatorio)
+       * Instalaciones
+       * Permitir el envío de paquetes
+       * Categorías
+    2. Haz clic en `Crear`.
+    ![pick-pack-usuarios-3-es](//images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/b5cac2035cbd75270e61a8dcbf7a32ae/image.png)
+
+## Catálogo
+
+En esta sección puedes consultar la información de ítems de pedidos que se encuentran en la etapa de entrega al cliente.
+
+![pick-pack-catalogo-es](//images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/a7ba2ed1eb52f8e6f8ad1616679564b9/image.png)
+
+La página presenta la siguiente información en forma de tabla:
+
+| Campos de la columna | Descripción                                                                                                      |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------- |
+| Ítem                 | Nombre del producto.                                                                                             |
+| ID del producto      | Número de identificación del producto.                                                                           |
+| SKU                  | Número de identificación del SKU del producto.                                                                   |
+| EAN                  | Número EAN del producto.                                                                                         |
+| Categorías           | Categorías en las que está registrado el producto.                                                               |
+| Dimensiones          | Dimensiones del producto.                                                                                        |
+| Peso                 | Peso del producto.                                                                                               |
+| Pesable              | Productos que necesitan pesarse para indicar su unidad de medida en kilogramos o gramos, según la configuración. |
+| Temperatura          | Productos que deben almacenarse a una temperatura mínima para evitar su deterioro.                               |
+| Activo               | Si el producto está o no disponible para los clientes.                                                           |
+
+Puedes agregar ID de SKU y EAN de tus productos masivamente, a través de un archivo CSV. Para hacerlo, sigue los pasos a continuación:
+
+1. Haz clic en el botón `Carga masiva de códigos SKU/EAN`.
+2. Agrega el archivo que deseas cargar.
+3. Haz clic en `Continuar`.
+
+También puedes indexar el catálogo para actualizar la lista de productos. Para hacerlo, haz clic en `Indexar catálogo` y después en `Continuar`.
+
+<div class = "alert alert-danger">
+  La indexación del catálogo borrará y recreará todo su contenido, lo que significa que puedes perder todos tus códigos EAN y SKU personalizados.
+</div>
+
+## Instalaciones
+
+En esta sección podrás agregar y consultar las instalaciones de tu tienda.
+
+![pick-pack-instalacoes-es](//images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/eb4cd39623ec2363f3c21a2624480fac/image.png)
+
+Para crear una nueva instalación sigue los pasos a continuación:
+
+1. Haz clic en `Crear`.
+2. Rellena el formulario con la dirección de tu instalación. Es obligatorio completar los campos **Calle**, **Ciudad** y **Estado**.
+3. Haz clic en `Guardar` para finalizar.
diff --git a/docs/tutorials/es/vtex-pick-and-pack-worksheets.md b/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
new file mode 100644
index 000000000..b3754408e
--- /dev/null
+++ b/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
@@ -0,0 +1,79 @@
+---
+title: 'VTEX Pick and Pack: Hojas de trabajo'
+id: 7bUwvmTY6eOqxzhyMIIzvz
+status: PUBLISHED
+createdAt: 2024-01-03T18:38:05.781Z
+updatedAt: 2024-01-03T20:13:50.986Z
+publishedAt: 2024-01-03T20:13:50.986Z
+firstPublishedAt: 2024-01-03T19:55:03.094Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-hojas-de-trabajo
+locale: es
+legacySlug: vtex-pick-and-pack-hojas-de-trabajo
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
+</div>
+
+**Hojas de trabajo** es una sección del Admin que gestiona, en tiempo real, las hojas de trabajo que utilizan los alistadores para agrupar y alistar los ítems de cada pedido. El alistador puede agrupar tantos pedidos como desee en cada hoja de trabajo. 
+
+Esta página te permite realizar las siguientes acciones: 
+
+* [Crear hoja de trabajo](#crear-hoja-de-trabajo)
+* [Buscar hoja de trabajo](#buscar-hoja-de-trabajo)
+* [Filtrar hojas de trabajo](#filtrar-hojas-de-trabajo)
+
+![pick-pack-ordem-servico-es](//images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/2f8d4456ad29068827c6eea06c74792a/image.png)
+
+Los pedidos se presentan en tarjetas que contienen la siguiente información:
+
+![pick-pack-ordem-servico-2-es](//images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/a1ae5432062574530f6cd465a35c752a/image.png)
+
+* ID de la hoja de trabajo.
+* Número de pedidos en la hoja de trabajo.
+* Cantidad de ítems en la hoja de trabajo.
+* Nombre del alistador responsable de la hoja de trabajo.
+* Nombre de la instalación.
+* Status de las hojas de trabajo.
+
+## Crear hoja de trabajo
+
+Puedes crear una nueva hoja de trabajo siguiendo los pasos que se indican a continuación:
+
+1. En el menú **Pedidos no asignados**, selecciona los pedidos deseados para incluirlos en la hoja de trabajo. No hay un límite establecido para cantidad de pedidos por hoja de trabajo.
+2. Haz clic en `Asignar a`.
+3. Haz clic en la pestaña **Manual** para crear manualmente la hoja de trabajo.
+4. Haz clic en `+` para crear una hoja de trabajo. Puedes crear más de una hoja de trabajo.
+5. Arrastra los pedidos que desees a la hoja de trabajo.
+  ![pick-pack-ordem-servico-3-es](//images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/f828572d27ac5915b8561762e0be1210/image.png)
+6. Haz clic en `Crear` para finalizar.
+
+## Consultar hojas de trabajo
+
+Puedes optimizar la consulta de las hojas de trabajo desde las siguientes secciones: 
+
+* **Todos:** todas las hojas de trabajo creadas.
+* **Alistando:** hojas de trabajo en curso, con el alistamiento de ítems en proceso.
+* **Empacando:** hojas de trabajo esperando envío.
+* **Completados:** hojas de trabajo de pedidos finalizados.
+* **Cancelados:** hojas de trabajo de pedidos cancelados.
+
+También puedes acceder a más información sobre cada hoja de trabajo particular haciendo clic en el botón <i class="fas fa-chevron-down"></i> en la tarjeta.
+
+![pick-pack-ordem-servico-4-es](//images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/8070f319c3af85bbc61babfd5fb1014a/image.png)
+
+## Buscar hoja de trabajo
+
+Puedes buscar una hoja de trabajo utilizando la barra de búsqueda; solo tienes que introducir el ID de la hoja de trabajo o el ID del pedido que deseas encontrar.
+
+## Filtrar hojas de trabajo
+
+Puedes refinar la búsqueda y visualización de hojas de trabajo seleccionando la opción **Filtros**. Filtra las hojas de trabajo por las siguientes opciones: 
+
+* **Categorías:** categorías de los ítems de los pedidos.
+* **Alistadores disponibles:** muestra los alistadores disponibles.
+* **Instalaciones:** para las instalaciones registradas, que pueden ser todas o específicas.
diff --git a/docs/tutorials/es/vtex-pick-and-pack.md b/docs/tutorials/es/vtex-pick-and-pack.md
index 6db537057..08fd64744 100644
--- a/docs/tutorials/es/vtex-pick-and-pack.md
+++ b/docs/tutorials/es/vtex-pick-and-pack.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack'
 id: 1OOops3WrUyz7e0bnhkfXU
 status: PUBLISHED
 createdAt: 2023-04-10T15:22:56.572Z
-updatedAt: 2023-04-20T00:55:31.302Z
-publishedAt: 2023-04-20T00:55:31.302Z
+updatedAt: 2023-08-25T15:48:44.351Z
+publishedAt: 2023-08-25T15:48:44.351Z
 firstPublishedAt: 2023-04-10T15:42:38.221Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: vtex-pick-and-pack
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
+<div class = "alert alert-info">
+Si tienes interés en implementarla en tu negocio, rellena nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> indicando en el campo <code>Comentarios</code> el nombre del producto deseado.
+</div>
+
 **VTEX Pick and Pack** es la solución que permite a los comerciantes gestionar la recolección, el empaquetado y la entrega de pedidos desde tiendas físicas y almacenes a las direcciones de los clientes o [puntos de recogida](https://help.vtex.com/es/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). Toda la gestión se realiza en un único lugar, lo que proporciona visibilidad y control a los comerciantes durante todo el proceso de fulfillment.
 
 ## Funcionalidades
diff --git a/docs/tutorials/es/vtex-shield.md b/docs/tutorials/es/vtex-shield.md
new file mode 100644
index 000000000..1ce579ee8
--- /dev/null
+++ b/docs/tutorials/es/vtex-shield.md
@@ -0,0 +1,63 @@
+---
+title: 'VTEX Shield'
+id: 2CVk6H9eY2CBtHjtDI7BFh
+status: PUBLISHED
+createdAt: 2024-04-25T00:31:01.895Z
+updatedAt: 2024-07-09T13:39:54.272Z
+publishedAt: 2024-07-09T13:39:54.272Z
+firstPublishedAt: 2024-04-25T01:19:00.025Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-shield
+locale: es
+legacySlug: vtex-shield
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+VTEX Shield ofrece capas de protección adicionales y personalizables para tiendas que priorizan la resiliencia de la plataforma, además de los estándares de seguridad garantizados por las certificaciones y [prácticas de seguridad](https://vtex.com/mx-es/security/security-practices/) existentes en VTEX.
+
+La solución cuenta con recursos de seguridad avanzados que permiten detectar riesgos potenciales y realizar acciones preventivas. Así, puedes proteger tu tienda contra interrupciones inesperadas, garantizando la operatividad y confiabilidad de la misma.
+
+Al contratar VTEX Shield tienes la opción de elegir entre las siguientes funcionalidades:
+
+* [Security Monitor](#security-monitor)
+* [Pruebas de penetración](#pruebas-de-penetracion)
+* [Web Application Firewall (WAF)](#web-application-firewall-waf)
+* [Data Protection Plus](#data-protection-plus)
+
+## Security Monitor
+
+Security Monitor es un dashboard del Admin VTEX que detecta amenazas de seguridad relacionadas con el comportamiento de usuarios administrativos y configuraciones inapropiadas. Los riesgos potenciales incluyen [claves de aplicación](https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet) antiguas o expuestas en la web, usuarios o credenciales con permisos excesivos y usuarios inactivos. La herramienta ofrece una visión general de las amenazas y soluciones, con la opción de notificar al retailer por email de cada hallazgo detectado.
+
+Security Monitor está disponible en el Admin VTEX solo para tiendas con VTEX Shield que opten por este recurso. Para obtener más información, consulta la guía [Security Monitor](https://help.vtex.com/es/tutorial/security-monitor--5LOVNLrrtmgSj99pM1NS4x).
+
+## Pruebas de penetración
+
+Las pruebas de penetración o pentests son simulaciones de ataques a un sistema informático, red o aplicación web con el fin de evaluar la seguridad, permitiendo identificar y corregir vulnerabilidades.
+
+Solo las tiendas con VTEX Shield que opten por este recurso tienen permiso para realizar pruebas de penetración, según los procedimientos indicados en [Pruebas de penetración y avisos de vulnerabilidad](https://help.vtex.com/es/tutorial/pruebas-de-penetracion-y-advertencia-de-vulnerabilidad--6jodF6s1I50Fg84ZwutOCb).
+
+## Web Application Firewall (WAF)
+
+Web Application Firewall (WAF) es una herramienta para proteger aplicaciones web mediante monitoreo y filtrado del tráfico de internet.
+
+Este recurso de seguridad desempeña un papel clave en la protección de servicios online, aplicaciones y sitios web frente a diversos ataques, como la inyección SQL, XSS (cross-site scripting) y otras vulnerabilidades web comunes.
+
+Solo las tiendas con VTEX Shield que opten por este recurso pueden solicitar la activación de WAF. Más información sobre su funcionamiento y los tipos de amenazas que combate en [Web Application Firewall (WAF)](https://help.vtex.com/es/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn).
+
+## Data Protection Plus
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad se encuentra en fase beta cerrada y está disponible solo en algunas regiones. Si tienes alguna duda, ponte en contacto con <a href="https://help.vtex.com/es/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">nuestro soporte</a>.</p>
+</div>
+
+[Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) es una arquitectura de datos que proporciona una capa adicional de protección para datos personales. En esta arquitectura, todos los datos de información de identificación personal (PII, Personally Identifiable Information) se almacenan en [Profile System](https://developers.vtex.com/docs/guides/profile-system), un servicio desarrollado específicamente para procesar PII siguiendo un [conjunto de reglas y procesos](https://developers.vtex.com/docs/guides/pii-data-architecture-specifications) apropiado para este objetivo.
+
+Otros módulos de la plataforma, como Pedidos y Checkout, solamente almacenan datos anonimizados asociados con un token de Profile System, lo que aumenta la seguridad de esta información.
+
+Consulta el conjunto de guías de la categoría [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) en el Developer Portal para obtener más detalles y especificaciones sobre esta arquitectura.
diff --git a/docs/tutorials/es/vtex-shipping-network-correios-activation.md b/docs/tutorials/es/vtex-shipping-network-correios-activation.md
new file mode 100644
index 000000000..041563c05
--- /dev/null
+++ b/docs/tutorials/es/vtex-shipping-network-correios-activation.md
@@ -0,0 +1,20 @@
+---
+title: 'VTEX Shipping Network Correios: activación'
+id: 57opHihFbRAwrjQjCTymTa
+status: PUBLISHED
+createdAt: 2023-08-31T13:25:47.887Z
+updatedAt: 2023-08-31T14:48:48.682Z
+publishedAt: 2023-08-31T14:48:48.682Z
+firstPublishedAt: 2023-08-31T14:36:56.281Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: vtex-shipping-network-correios-activacion
+locale: es
+legacySlug: vtex-shipping-network-correios-activacion
+subcategory: 5n5MnINzWTQUX1I2EZl4Ib
+---
+
+<div class="alert alert-warning" role="alert">
+Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
+</div>
diff --git a/docs/tutorials/es/vtex-shipping-network-correios-faq.md b/docs/tutorials/es/vtex-shipping-network-correios-faq.md
index 1d6bb9675..dbc8fdec7 100644
--- a/docs/tutorials/es/vtex-shipping-network-correios-faq.md
+++ b/docs/tutorials/es/vtex-shipping-network-correios-faq.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network Correios: FAQ'
 id: 2Wavf7Wie5GEUAEHKtn5oC
 status: PUBLISHED
 createdAt: 2023-06-01T13:24:23.895Z
-updatedAt: 2023-06-09T12:55:42.194Z
-publishedAt: 2023-06-09T12:55:42.194Z
+updatedAt: 2023-08-25T15:32:25.418Z
+publishedAt: 2023-08-25T15:32:25.418Z
 firstPublishedAt: 2023-06-01T14:47:24.289Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/es/vtex-shipping-network-dashboard.md b/docs/tutorials/es/vtex-shipping-network-dashboard.md
index 9d30a28d4..96e835acc 100644
--- a/docs/tutorials/es/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/es/vtex-shipping-network-dashboard.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Panel '
 id: 51e8tx1IehiN4ZtURRWU92
 status: PUBLISHED
 createdAt: 2020-04-06T20:01:00.909Z
-updatedAt: 2023-06-09T12:56:22.175Z
-publishedAt: 2023-06-09T12:56:22.175Z
+updatedAt: 2024-02-29T19:20:49.152Z
+publishedAt: 2024-02-29T19:20:49.152Z
 firstPublishedAt: 2020-04-16T21:37:18.831Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -48,8 +48,9 @@ Esta pestaña está destinada al seguimiento y supervisión del resultado financ
 | **Ingresos Facturados VTEX Shipping Network**    | Suma de todos los fletes pagados en el checkout. Cuánto de hecho su cliente pagó por el flete, filtrando apenas por transportadoras VTEX Shipping Network; es decir, se considera si tuvo un descuento en el flete o si fue flete gratis, por ejemplo.                                                                                                                                                                                                             |
 | **Costo Proyectado General**        | Independientemente de ser VTEX Shipping Network o no, es la suma de los valores de flete estimados por el módulo de Inventario y Envío para todos los pedidos. Tiene flechas que indican el porcentaje de crecimiento o reducción de costos. La disminución de costos en este card (flecha hacia abajo) es una medida positiva para los resultados de una tienda.                                                                                                                                |
 | **Costo Proyectado VTEX Shipping Network**     | Suma de los valores de flete estimados por el módulo de Inventario y Envío para todos los pedidos, filtrando apenas a transportadoras VTEX Shipping Network. Tiene flechas que indican el porcentaje de crecimiento o reducción de costos.  La disminución de costos en este card (flecha hacia abajo) es una medida positiva para los resultados de una tienda.                                                                                                                           |
-| **Costo Emitido vía CTE**        | Costo que proveniente de CONEMB para todos estos pedidos. VTEX recibe esta información a través del envío de archivos CONEMB, que las transportadoras nos envían. Este archivo indica en detalle cuánto gastó la transportadora, y el número de la factura del pedido.  Tiene flechas que indican el porcentaje de crecimiento o reducción de costos.  La disminución de costos en este card (flecha hacia abajo) es una medida positiva para los resultados de una tienda.                                                                                                            |
-|  **Diferencia de costos señalada** | Diferencia entre el costo proyectado y el costo emitido vía CTE.  CTE es el archivo recibido de las transportadoras VTEX Shipping Network, que indica en detalle cuánto gastó la transportadora, y el número de factura del pedido.  Tiene flechas que indican el porcentaje de crecimiento o reducción de costos.  El aumento entre la diferencia de costos en este card es una medida positiva para los resultados de una tienda.                                                                                                          |
+
+* Estamos mejorando el **Costo Emitido vía CTE** y la **Diferencia de costos señalada** y actualmente no están disponibles.
+
 ## Rendimiento 
 
 Es posible hacer seguimiento del rendimiento de las transportadoras configuradas en la logística de su tienda a través de una herramienta analítica. En la herramienta, puede ver la evolución del rendimiento de cada transportadora en particular y de las transportadoras VTEX Shipping Network en general.
@@ -58,7 +59,7 @@ En el cálculo del rendimiento, se consideran todos los paquetes que forman part
 
 El rendimiento es el resultado porcentual del cálculo entre la relación de paquetes entregados a tiempo y el total de paquetes entregados. Por lo tanto, el cálculo del rendimiento solo toma en cuenta los paquetes entregados. Veamos:
 
-![equation ES performance](https://images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/a7c32e054f2b328ee9cbbf83a54a4c09/equation_ES_performance.gif)
+![equation ES performance](//images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/a7c32e054f2b328ee9cbbf83a54a4c09/equation_ES_performance.gif)
 
  La herramienta de rendimiento de VTEX Shipping Network permite:
 
@@ -82,9 +83,9 @@ Todas las transportadoras VTEX Shipping Network tienen un sello de verificación
 
 Es importante saber que si no se calculó el rendimiento de una transportadora en la plataforma significa que los datos de seguimiento no están integrados con VTEX Shipping Network. 
 
-Para que se realice el cálculo de las transportadoras que no son VTEX Shipping Network, el _seller_ debe enviar los datos a través de una API de seguimiento proporcionada por la solución VTEX Shipping Network. 
+Para que se realice el cálculo de las transportadoras que no son VTEX Shipping Network, el _seller_ debe enviar los datos a través de una API de seguimiento proporcionada por la solución VTEX Shipping Network. En estos casos, cabe señalar que los datos del panel pueden ser inexactos, al no realizarse una validación de la entrega en el plazo indicado.
 
-Para saber más sobre cómo realizar la integración, consulte la información en [Overview VTEX Shipping Network](https://developers.vtex.com/vtex-rest-api/reference/vtex-log-api-overview) de nuestras API. 
+Para saber más sobre cómo realizar la integración, consulte la información en [Overview VTEX Shipping Network](https://developers.vtex.com/docs/api-reference/vtex-shipping-network-api) de nuestras API. 
 
 ### Exportar informe
 
@@ -94,4 +95,4 @@ Puede descargar el informe con los datos de las transportadoras y las entregas d
 2. Espere hasta recibir la plantilla por email.
 3. Descargue la plantilla.
 
-![Resumo de performance ES](https://images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/4d3875da23f323f9d03a5eb6139fd0c1/Resumo_de_performance_ES.png)
+![Resumo de performance ES](//images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/4d3875da23f323f9d03a5eb6139fd0c1/Resumo_de_performance_ES.png)
diff --git a/docs/tutorials/es/vtex-status-page.md b/docs/tutorials/es/vtex-status-page.md
new file mode 100644
index 000000000..d359b754b
--- /dev/null
+++ b/docs/tutorials/es/vtex-status-page.md
@@ -0,0 +1,169 @@
+---
+title: 'Página VTEX Status'
+id: gPhqDn9IQ3c67wbJEX3JJ
+status: PUBLISHED
+createdAt: 2019-01-14T19:58:58.431Z
+updatedAt: 2023-12-21T17:10:08.895Z
+publishedAt: 2023-12-21T17:10:08.895Z
+firstPublishedAt: 2019-01-14T20:01:43.663Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: pagina-vtex-status
+locale: es
+legacySlug: untitled-entry-2019-01-14-at-07-58-58, status-vtex-entienda-como-funciona-el-status-de-la-plataforma, pagina-de-status-de-la-plataforma
+subcategory: 5PYkoNDZyo2G80yiiqG2YW
+---
+
+La página [VTEX Status](https://status.vtex.com/) te permite monitorear la estabilidad de la plataforma en tiempo real y acceder al historial completo de incidentes.
+
+Nuestro equipo informa los eventos cada vez que nuestro sistema de monitoreo automático identifica una inestabilidad en los módulos de la plataforma. Cualquier mantenimiento programado también se comunica en detalle.
+
+![statuspage-1](//images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/59648457b075dea1768cb9c76f0be1f5/statuspage-1.png)
+
+En este artículo, se describen los elementos de la página de status de la plataforma VTEX, desarrollada con la herramienta [incident.io](https://incident.io/):
+
+* [Informar un problema](#informar-un-problema)
+* [Notificaciones](#notificaciones)
+* [Status general](#status-general)
+* [Status de los sistemas](#status-de-los-sistemas)
+* [Calendario](#calendario)
+* [Registro de incidentes](#registro-de-incidentes)
+* [Registro de mantenimiento programado](#registro-de-mantenimiento-programado)
+
+## Informar un problema
+
+Al hacer clic en el botón `Report a problem` en la parte superior derecha de la página, puedes ponerte en contacto con [nuestro equipo de soporte](https://support.vtex.com/hc/es-es) para informar alguna instabilidad en la plataforma.
+
+## Notificaciones
+
+El botón `Subscribe to updates` en la parte superior derecha de la página te da la opción de suscribirte para recibir actualizaciones a través de email, [feed RSS](https://rss.com/blog/how-do-rss-feeds-work/) o [Slack](https://slack.com/).
+
+La opción de inscripción por email te permite decidir los componentes específicos para los que deseas recibir notificaciones. Solo tienes que marcar la opción **Subscribe to specific components** y, luego, los componentes que deseas monitorear.
+
+![statuspage-2](//images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/bfdc48e6aa471800a4655b4bea99f87e/statuspage-2.png)
+
+## Status general
+
+Esta sección te permite ver el status general de la plataforma: fully operational (completamente operativa), experiencing issues (experimentando problemas) o undergoing maintenance (mantenimiento en curso).
+
+Cuando algún problema o mantenimiento está afectando un componente, se indica dicho componente y se incluye una explicación del evento.  A continuación se muestran algunos ejemplos.
+
+![statuspage-3](//images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/889faae502219e1a0da31bdb3c2f00c6/statuspage-3.png)
+
+![statuspage-4](//images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/89ea44b8e93b93ed7d45fa19767de9eb/statuspage-4.png)
+
+![statuspage-5](//images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/38b3b92371b0a04090f912e2598c21a6/statuspage-5.png)
+
+## Status de los sistemas
+
+Esta sección te permite verificar en tiempo real el status de cada sistema de la plataforma y de sus componentes.
+
+![statuspage-6](//images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/1df94b99be002d4ecb574c9e4bb59d4c/statuspage-6.png)
+
+Al hacer clic en la flecha <i class="fas fa-chevron-down"></i> al lado del número de componentes, verás el status de los componentes específicos de cada sistema.
+
+Si se trata de un mantenimiento programado para una fecha futura, también verás el botón `Upcoming maintenance scheduled`, como se ilustra a continuación. Al pasar el mouse sobre el botón, se mostrará el evento de mantenimiento programado. Puedes hacer clic en el evento para ver su registro.
+
+![statuspage-7](//images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/ce633e4e4728d717c14c0f2daa1eddf8/statuspage-7.png)
+
+Los posibles status para cada componente son:
+
+* **Operational:** funcionamiento estable.
+* **Degraded performance:** funcionamiento con rendimiento inferior al esperado.
+* **Partial outage:** funcionamiento parcial de las funcionalidades.
+* **Full outage:** funcionamiento completamente impactado.
+* **Under maintenance:** mantenimiento en curso en el sistema.
+
+A continuación, se describen los componentes mostrados en la página.
+
+### Storefront
+
+Problemas de navegación en el storefront.
+
+* **Portal/CMS:** inestabilidad observada en tiendas desarrolladas con la tecnología de storefront [Portal CMS Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
+* **Store Framework:** inestabilidad observada en tiendas desarrolladas con la tecnología de storefront[ Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework).
+* **FastStore:** inestabilidad observada en tiendas desarrolladas con la tecnología de storefront[ FastStore](https://www.faststore.dev/).
+* **Sales App:** inestabilidad observada en [Sales App](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc), la solución de VTEX para ventas asistidas en tiendas físicas.
+* **3rd Party Apps:** inestabilidad observada en extensiones mantenidas por terceros.
+
+### Checkout
+
+Problemas en funcionalidades relacionadas con el flujo de creación de pedidos, es decir, en el checkout y sus dependencias.
+
+* **Order Placement:** interrupciones en el flujo de ventas.
+* **Shipping Calculation:** inconsistencias en las condiciones de envío.
+* **Pricing Calculation:** inconsistencias en los precios, promociones o cargos.
+* **Payments Gateway:** inconsistencias en las transacciones de pago.
+* **Payment Connectors:** inestabilidad observada en proveedores de pago específicos.
+
+### Admin
+
+Problemas en la navegación del Admin VTEX y sus módulos, como por ejemplo gestión de pedidos, configuración de precio y logística.
+
+* **Catalog Management:** interrupciones en la actualización del contenido del catálogo (detalles del producto, imágenes, precios, stock, indexación de búsqueda, etc.).
+* **Content Management:** interrupciones en la actualización de contenido no relacionado con productos (banners, landing pages, promociones, cupones, tarjetas de regalo, etc.).
+* **Order Management:** interrupciones en el fulfillment de pedidos.
+* **Marketplace Connectors:** instabilidad observada en conectores de marketplace específicos.
+* **Admin Operations:** otros impactos a la experiencia de los retailers, fuera del ámbito de otros componentes del Admin.
+
+### Developer Tools
+
+Problemas relacionados con el desarrollo de aplicaciones, integraciones y temas de tiendas.
+
+* **VTEX IO:** inestabilidad observada en aplicaciones desarrolladas en VTEX IO.
+* **Master Data:** inestabilidad observada en integraciones que dependen de Master Data.
+* **API Integrations:** otros impactos en el uso de las API de VTEX.
+
+## Calendario
+
+La sección del calendario muestra el registro de incidentes y mantenimientos programados que ocurrieron cada día del mes actual.
+
+Para navegar a meses anteriores, haz clic en la flecha `<`.
+
+Para ver los eventos ocurridos en un día específico, pasa el mouse sobre la fecha. Para acceder a la página que contiene el registro completo del evento, haz clic en el incidente o el mantenimiento indicado en la fecha.
+
+![statuspage-8](//images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/0fff21b4393a61f149857c0bb353ef4a/statuspage-8.png)
+
+<div class="alert alert-warning">
+  <p>Si un mantenimiento programado dura más de un día, solo se marcará la fecha de inicio en el calendario. Debes abrir el <a href="#registro-de-mantenimiento-programado">registro de mantenimiento</a> para ver la fecha de inicio y la fecha de fin.</p>
+</div>
+
+A continueación, describimos la información disponible en el registro del incidente y en el registro de mantenimiento programado.
+
+## Registro de incidentes
+
+La página de detalles del incidente contiene la siguiente información:
+
+![status-page-9-es](//images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/7d7565c3a5baaf600033d9ad096bb0a2/status-page-9-es.png)
+
+* **Título:** título que describe el incidente.
+* **Status:** cada incidente tiene un ciclo definido en que nuestro equipo trabaja para identificar y solucionar los problemas. Las etapas del ciclo son:
+    * **Investigating:** la primera etapa de un incidente consiste en a analizar el impacto, servicios relacionados e identificar la causa raíz.
+    * **Identified:** luego de que el error es debidamente identificado, el equipo de desarrollo empieza a ejecutar acciones para solucionar el comportamiento.
+    * **Monitoring:** una vez concluidas las acciones de estabilización del sistema y normalizados los indicadores de operación, continuamos en estado de alerta y monitoreamos de cerca el rendimiento del servicio o módulo impactado.
+    * **Resolved:** cuando el rendimiento de la plataforma está estabilizado, volvemos a nuestro monitoreo normal y consideramos que la plataforma funciona como se espera.
+* **Duración:** periodo de resolución del incidente.
+* **Resumen:** texto que resume el incidente.
+* **Componentes afectados:** los componentes de la plataforma que fueron afectados por el incidente. Al hacer clic en la flecha al lado del número de componentes, puedes ver el impacto en componentes más específicos.
+* **Actualizaciones:** línea de tiempo con las actualizaciones y cambios de status del incidente.
+
+Al hacer clic en el botón `Subscribe to updates` en el registro de un incidente, te da la opción de inscribirte para recibir actualizaciones sobre ese incidente específico a través de email, feed RSS o Slack.
+
+## Registro de mantenimiento programado
+
+Continuamente se realizan actualizaciones en la plataforma y, en general, dichas actualizaciones no impactan la operación de nuestros clientes. Sin embargo, algunas actualizaciones requieren interrumpir temporalmente la disponibilidad de un servicio.
+
+En situaciones en que la estabilidad de la plataforma se vea afectada, empleamos la página de status de VTEX para comunicar todos los detalles: fecha de ejecución del mantenimiento, duración e impacto.
+
+El registro de mantenimiento programado muestra la misma información que el registro de incidente. Los posibles status de mantenimiento programado son:
+
+* **Scheduled:** evento de mantenimiento programado.
+* **In progress:** evento de mantenimiento en curso.
+* **Complete:** evento de mantenimiento completado.
+
+A continuación, se muestran ejemplos del status y la línea de tiempo de un mantenimiento programado.
+
+![statuspage-10](//images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/25713a87ae2dc76ac750dff3d5bc078b/statuspage-10.png)
+
+![statuspage-11](//images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/c71e1785f62f7e32db69fc23eb951200/statuspage-11.png)
diff --git a/docs/tutorials/es/vtex-support-apac.md b/docs/tutorials/es/vtex-support-apac.md
new file mode 100644
index 000000000..f22b1914e
--- /dev/null
+++ b/docs/tutorials/es/vtex-support-apac.md
@@ -0,0 +1,18 @@
+---
+title: 'Soporte VTEX - APAC'
+id: 4tHKlUwXgjW8ebnCxd6COc
+status: PUBLISHED
+createdAt: 2024-04-29T23:32:23.667Z
+updatedAt: 2024-04-30T11:02:29.768Z
+publishedAt: 2024-04-30T11:02:29.768Z
+firstPublishedAt: 2024-04-29T23:36:32.127Z
+contentType: tutorial
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: soporte-vtex-apac
+locale: es
+legacySlug: soporte-vtex-apac
+subcategory: 
+---
+
+Este contenido está disponible solo en inglés. [Haga clic aquí](https://help.vtex.com/es/faq/como-funciona-el-soporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe#support-plans) para acceder.
diff --git a/docs/tutorials/es/warehouse.md b/docs/tutorials/es/warehouse.md
index 6fa067952..3fc536d8c 100644
--- a/docs/tutorials/es/warehouse.md
+++ b/docs/tutorials/es/warehouse.md
@@ -20,7 +20,7 @@ Para la plataforma VTEX, el almacén es la identificación del espacio de almace
 
 Es importante prestar atención a la etapa logística del almacén y al modo en que la configuración de la plataforma VTEX influye en la entrega de los pedidos. Del almacén salen los pedidos a los muelles, y en los muelles los recogen las transportadoras. 
 
-![EstrategiaEnvio_ES](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/ed9784e5cbc67a42358ad4f37c3baa00/Frame_2__2_.svg)
+![EstrategiaEnvio_ES](//images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/ed9784e5cbc67a42358ad4f37c3baa00/Frame_2__2_.svg)
 
 <div class="alert alert-info">
 La transportadora que llevará a cabo la entrega de un determinado pedido es definida por la <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">política de envío</a>. Para que una transportadora sea elegida para efectuar la entrega del pedido, es necesario que la política de envío de esa transportadora cumpla con las condiciones necesarias para la entrega del pedido. La política de envío está vinculada al almacén por el muelle.
diff --git a/docs/tutorials/es/web-application-firewall-waf.md b/docs/tutorials/es/web-application-firewall-waf.md
new file mode 100644
index 000000000..9802c8f0d
--- /dev/null
+++ b/docs/tutorials/es/web-application-firewall-waf.md
@@ -0,0 +1,58 @@
+---
+title: 'Web Application Firewall (WAF)'
+id: 6BZYLlU03ws72iqIFF6jdn
+status: PUBLISHED
+createdAt: 2024-04-25T00:17:16.172Z
+updatedAt: 2024-04-30T15:03:41.186Z
+publishedAt: 2024-04-30T15:03:41.186Z
+firstPublishedAt: 2024-04-25T01:16:27.468Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: web-application-firewall-waf
+locale: es
+legacySlug: web-application-firewall-waf
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidad es parte de <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>.  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
+</div>
+
+Web Application Firewall (WAF) es una capa de seguridad diseñada para proteger aplicaciones web mediante monitoreo y filtrado del tráfico de internet.
+
+WAF se enfoca en las comunicaciones que se llevan a cabo a través de los protocolos HTTP (Hypertext Transfer Protocol) y HTTPS (HTTP Secure), analizando los datos de entrada y salida para detectar y bloquear posibles amenazas.
+
+![waf-es](//images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/c54a99dcdc86451d6cfcd72bc7b9cf07/waf-es.png)
+
+WAF opera a partir de la configuración de [reglas de seguridad](#reglas-de-seguridad) definidas por el equipo de seguridad de VTEX basándose en el análisis de patrones de circulación de datos. Dichas reglas sirven para que WAF monitoree constantemente el tráfico web y cuando detecte una actividad potencialmente perjudicial, pueda bloquear el tráfico, impidiendo que los atacantes aprovechen las vulnerabilidades en la aplicación web.
+
+## Reglas de seguridad
+
+Las tiendas que utilizan VTEX Shield y deciden usar WAF cuentan con las siguientes reglas de seguridad contra amenazas en el sitio web:
+
+| Amenaza | Regla de seguridad |
+|---|---|
+| Remote File Inclusions (RFI) | Detecta tentativas de incluir archivos, normalmente a través de scripts en el servidor web. |
+| Directory Traversal | Comprueba y valida los nombres de archivo proporcionados por los usuarios, previniendo el acceso no autorizado a archivos y carpetas sensibles.   |
+| Cross-Site Scripting (XSS) | Impide la inyección de scripts del lado del cliente en las páginas vistas por los visitantes.   |
+| Carga de archivos | Detecta intentos de carga de archivos al servidor web.   |
+| Trucos de evasión | Protege contra algunos trucos de codificación utilizados para intentar eludir los mecanismos de protección.   |
+| Acceso no deseado | Detecta intentos de acceso a páginas administrativas o vulnerables, a bots y a herramientas de escaneo de seguridad.   |
+| Ataques identificados | Previene varios tipos de ataques comunes y vulnerabilidades conocidas que deberían bloquearse.   |
+| Filtro de IP | Consulta una lista de direcciones IP que tienen permiso o bloqueo de acceso.   |
+| Bloqueo de la red Tor | Impide el acceso al sitio web utilizando el navegador Tor.   |
+
+## Solicitar activación de WAF
+
+Para solicitar la activación de WAF en tu tienda, ponte en contacto con el[ soporte VTEX](https://help.vtex.com/es/support). Incluya la siguiente información en el ticket:
+
+* URL que se añadirán a WAF.
+* Nombre y datos de contacto de la persona que será el punto de contacto con el equipo de seguridad de VTEX durante el proceso de activación.
+* Proveedor: para tener acceso a WAF, todo el tráfico de URL de la tienda debe pasar por [Azion](https://www.azion.com/es/), el proveedor que VTEX utiliza actualmente. De no ser ese el caso, debes llevar a cabo un procedimiento con el equipo de tráfico de VTEX que puede durar entre una y dos semanas.
+
+Después de la solicitud, el plazo de activación de WAF en las URL de la tienda es de cuatro semanas, además del plazo necesario para la migración a [Azion](https://www.azion.com/es/), de ser necesario.
+
+## Más información
+
+* [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh)
diff --git a/docs/tutorials/es/web-page-performance.md b/docs/tutorials/es/web-page-performance.md
index 3c91d137b..da26252a7 100644
--- a/docs/tutorials/es/web-page-performance.md
+++ b/docs/tutorials/es/web-page-performance.md
@@ -25,7 +25,7 @@ El dashboard Rendimiento de las páginas web incorpora la herramienta [PageSpeed
 
 Aunque el _dashboard_ Rendimiento de las páginas web ofrece las mismas funcionalidades que PageSpeed Insights de Google, los comerciantes pueden agregar varias URL y hacerles un seguimiento constante únicamente en el Admin VTEX. 
 
-![Web page performance Dash ES](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
+![Web page performance Dash ES](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
 
 ## ¿Por qué deberías hacer un seguimiento del rendimiento de una página web?
 
@@ -104,7 +104,7 @@ Ten en cuenta que no podrás eliminar las 10 páginas más visitadas de tu _ecom
 
 ## Métricas web principales
 
-![Core web vitals ES](https://images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/16028a64c956d2461f1fc1f5c924beda/Screen_Shot_2022-06-29_at_15.47.45.png)
+![Core web vitals ES](//images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/16028a64c956d2461f1fc1f5c924beda/Screen_Shot_2022-06-29_at_15.47.45.png)
 
 Para cada URL, la página Rendimiento de las páginas web muestra la puntuación de las [Métricas web principales de Google](https://web.dev/vitals/#core-web-vitals) para esa página web. 
 
diff --git a/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md b/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
index f8d77bd50..0ac209ab3 100644
--- a/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
+++ b/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
@@ -19,7 +19,7 @@ Al acceder la sección __Todos los pedidos__, en __Gestión de pedidos__, es pos
 
 La columna __Origin__ indica de dónde proviene los pedidos, distinguiéndo ellos entre en dos posibles orígenes: __Marketplace__ y __Fulfillment__.
 
-![orders-list-origin-es](https://images.ctfassets.net/alneenqid6w5/1rflCsjI1vIGnb7juYOJJa/8e060cea0849e422a060526bf2fe81e2/oders-list-origin-es.png)
+![orders-list-origin-es](//images.ctfassets.net/alneenqid6w5/1rflCsjI1vIGnb7juYOJJa/8e060cea0849e422a060526bf2fe81e2/oders-list-origin-es.png)
 
 ## Marketplace
 
diff --git a/docs/tutorials/es/what-are-templates.md b/docs/tutorials/es/what-are-templates.md
index 949292530..7f27165e6 100644
--- a/docs/tutorials/es/what-are-templates.md
+++ b/docs/tutorials/es/what-are-templates.md
@@ -32,7 +32,7 @@ Además de estos dos tipos básicos, todavía hay una subdivisión de los __temp
 
 Y hablando en organización, usted encuentra todos los templates en el **Storefront > Layout > CMS**, reunidos en carpetas de acuerdo a su tipo (HTML o Shelves). Los __Sub Templates__ están en la carpeta del mismo nombre, que se encuentra dentro del directorio __HTML Templates__. En estos lugares, usted podrá crear nuevos templates y editar los que ya existen.
 
-![cms](https://images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
+![cms](//images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
 
 ### Artículos relacionados
 - [¿Qué es el CMS?](/es/tutorial/que-es-el-cms)
diff --git a/docs/tutorials/es/what-customized-payments-are-available-in-latin-america.md b/docs/tutorials/es/what-customized-payments-are-available-in-latin-america.md
index 5b0dc9d7e..f779bdefc 100644
--- a/docs/tutorials/es/what-customized-payments-are-available-in-latin-america.md
+++ b/docs/tutorials/es/what-customized-payments-are-available-in-latin-america.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Qué pagos personalizados están disponibles en América Latina?'
 id: 6plXudxQJiwaE0key20Yoe
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.217Z
-updatedAt: 2019-12-31T15:29:09.442Z
-publishedAt: 2019-12-31T15:29:09.442Z
+updatedAt: 2024-03-19T12:09:37.330Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T21:58:52.021Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md b/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
index db152fa55..e586c22ef 100644
--- a/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
+++ b/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
@@ -24,4 +24,4 @@ Al configurar una promoción **Comprar y obtener**, es posible **Activar multipl
 Para ambos escenarios, se necesita rellenar la cantidad máxima de seleccionable. Con el multiplicador de regalos **activado**, determine la **cantidad máxima** de regalos para la condición. Para el multiplicador de regalos **desactivado**, la cantidad es **siempre 1**.
 
 
-![ativar-multiplicador-brinde es](https://images.ctfassets.net/alneenqid6w5/23jsNGW0DCc6CEmgGYmOms/ad3128579334e186a434b21b04455ee6/gift_multi_es.png)
+![ativar-multiplicador-brinde es](//images.ctfassets.net/alneenqid6w5/23jsNGW0DCc6CEmgGYmOms/ad3128579334e186a434b21b04455ee6/gift_multi_es.png)
diff --git a/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md b/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
index b08be812b..57f42977c 100644
--- a/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
+++ b/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
@@ -33,7 +33,7 @@ Para saber cómo acceder a los pedidos que se consideraron en el cálculo de los
 Para facilitar su visualización, todos los pedidos aprobados financieramente estarán marcados de esta forma, que se puede ver en el módulo de gestión de pedidos. 
 
 
-![image (4)](https://images.ctfassets.net/alneenqid6w5/6HOwNB7DXzMr3pCPmeZkGS/4088a657730d190f8e4e2388295fd827/image__4_.png)
+![image (4)](//images.ctfassets.net/alneenqid6w5/6HOwNB7DXzMr3pCPmeZkGS/4088a657730d190f8e4e2388295fd827/image__4_.png)
 
 
 Para acceder al módulo, realice el siguiente procedimiento:
diff --git a/docs/tutorials/es/what-is-a-franchise-account.md b/docs/tutorials/es/what-is-a-franchise-account.md
index c06991f36..8901e3521 100644
--- a/docs/tutorials/es/what-is-a-franchise-account.md
+++ b/docs/tutorials/es/what-is-a-franchise-account.md
@@ -3,8 +3,8 @@ title: '¿Qué es una cuenta franquicia?'
 id: kWQC6RkFSCUFGgY5gSjdl
 status: PUBLISHED
 createdAt: 2021-10-13T20:38:07.014Z
-updatedAt: 2023-05-31T15:20:29.177Z
-publishedAt: 2023-05-31T15:20:29.177Z
+updatedAt: 2024-05-24T16:38:26.710Z
+publishedAt: 2024-05-24T16:38:26.710Z
 firstPublishedAt: 2021-10-13T20:57:01.457Z
 contentType: tutorial
 productTeam: Shopping
@@ -19,7 +19,7 @@ En la plataforma VTEX, tienes la opción de registrar tiendas físicas, franquic
 
 La cuenta franquicia está asociada a una cuenta principal. En el caso de una marca que tenga varias tiendas físicas, franquiciados o representantes, cada uno de ellos puede tener una cuenta franquicia vinculada a la cuenta principal de la marca. Esto les permite entregar los productos vendidos por el ecommerce de la marca.
 
-![diagrama contas v2 - es](https://images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/38f2bac55f9150f6049aaa20193aa97e/diagrama_contas_v2_-_es.png)
+![diagrama contas v2 - es](//images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/38f2bac55f9150f6049aaa20193aa97e/diagrama_contas_v2_-_es.png)
 
 En este artículo, trataremos los siguientes temas:
 
@@ -38,7 +38,7 @@ Además, utilizando la cuenta franquicia, puedes gestionar precios y medios de p
 
 Una cuenta franquicia no tiene su propio sitio web. Los consumidores navegan directamente en el sitio web de la cuenta principal, que funciona como un _marketplace_ en esta situación. Los datos de los clientes se almacenan en el Master Data de la cuenta principal.
 
-![diagrama admin contas - es](https://images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/b30710b00e3a9a898fe2cd1fb5dd96c5/diagrama_admin_contas_-_es.png)
+![diagrama admin contas - es](//images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/b30710b00e3a9a898fe2cd1fb5dd96c5/diagrama_admin_contas_-_es.png)
 
 ## Relación entre la cuenta franquicia y el _Seller White Label_
 
@@ -71,6 +71,11 @@ Para que la cuenta franquicia utilice los precios configurados en la cuenta prin
 
 Para configurar precios propios de la cuenta franquicia, es necesario quitar la marca de la casilla **Heredar precios de la cuenta padre** en la Configuración del módulo de **Precios** de la cuenta franquicia, como se describe en [este artículo](https://help.vtex.com/es/tutorial/price-configuration--3hbBtCzNUBrj8GaWgCtSWN). Además, es necesario configurar los precios deseados en el [módulo de Precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) o mediante la [API de Pricing](https://developers.vtex.com/vtex-rest-api/reference/pricing-api-overview).
 
+Para garantizar una experiencia de compra uniforme, es importante [configurar la regionalización](https://help.vtex.com/pt/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw?&utm_source=autocomplete) cuando cada cuenta franquicia tiene precios diferentes.
+La adopción de la regionalización posibilita solicitar el código postal del cliente antes de que este inicie la navegación, lo que a su vez permite mostrar los productos y precios correspondientes a la cuenta franquicia antes de continuar al checkout.
+Si la regionalización no está activa, puede haber casos en los que el consumidor vea un determinado valor de producto al navegar por la tienda, pero al llegar al checkout e ingresar el código postal se determine que la cuenta franquicia que debe atender el pedido es otra y, por lo tanto, el precio sea diferente.
+Esto ocurre porque el catálogo de menor precio es priorizado durante la navegación por la tienda. Sin embargo, en el checkout, si la cuenta franquicia de menor precio no tiene stock disponible, se seleccionará el catálogo de otro seller que tenga stock del producto disponible y se actualizará el precio al valor utilizado por dicho seller.
+
 ### Pagos
 
 #### Utilizar los medios de pago de la cuenta principal
@@ -92,7 +97,7 @@ VTEX ofrece soluciones de _split_ de pagos que pueden hacer que la distribución
 Existen varios tipos de configuración posibles para los precios y medios de pago relacionados con las cuentas franquicia en VTEX, que se indican a continuación. Puedes elegir la forma de uso que mejor se adecue a tu negocio.
 
 <div class="alert alert-warning">
-<p>Si deseas implementar inStore en tus tiendas físicas, no te recomendamos que configures medios de pago propios para las cuentas franquicia. Lo ideal es que las cuentas franquicia utilicen los medios de pago de la cuenta principal, para evitar conflictos de pago.</p>
+<p>Si deseas implementar la aplicación VTEX Sales App, es necesario que las tiendas físicas utilicen los medios de pago de la cuenta principal.</p>
 </div>
 
 ## Solicitar la creación de una cuenta franquicia
diff --git a/docs/tutorials/es/what-is-a-service.md b/docs/tutorials/es/what-is-a-service.md
index 0b4380f17..330a35e97 100644
--- a/docs/tutorials/es/what-is-a-service.md
+++ b/docs/tutorials/es/what-is-a-service.md
@@ -3,8 +3,8 @@ title: '¿Qué es un Servicio?'
 id: 46Ha8CEEQoC6Y40i6akG0y
 status: PUBLISHED
 createdAt: 2018-02-16T13:35:47.291Z
-updatedAt: 2020-09-10T14:25:34.223Z
-publishedAt: 2020-09-10T14:25:34.223Z
+updatedAt: 2023-11-16T17:24:14.877Z
+publishedAt: 2023-11-16T17:24:14.877Z
 firstPublishedAt: 2018-02-16T17:24:14.979Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,5 +25,5 @@ Si su producto comprado es una Camisa de la Selección Brasileña, el nombre de
 
 ### Artículos relacionados
 - [¿Qué es un anexo?](/es/tutorial/que-es-un-anexo)
-- [Registrar un anexo](/es/tutorial/registrar-un-anexo)
+- [Registrar un anexo](/es/tutorial/registrar-un-anexo--7zHMUpuoQE4cAskqEUWScU)
 - [Crear servicio para un SKU](/es/tutorial/criando-servico-para-um-sku)
diff --git a/docs/tutorials/es/what-is-a-transaction.md b/docs/tutorials/es/what-is-a-transaction.md
index f2642f6df..3cd5bfda7 100644
--- a/docs/tutorials/es/what-is-a-transaction.md
+++ b/docs/tutorials/es/what-is-a-transaction.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Qué es una transacción?'
 id: 36vMP5PES4oUWMWQuskIQ6
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-02-23T16:09:38.585Z
-updatedAt: 2020-11-27T19:39:37.153Z
-publishedAt: 2020-04-28T19:07:01.620Z
+updatedAt: 2023-09-28T16:00:07.059Z
+publishedAt: 2023-09-28T16:00:07.059Z
 firstPublishedAt: 2018-02-26T20:24:17.085Z
 contentType: tutorial
 productTeam: Financial
@@ -17,13 +17,13 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 El movimiento que el dinero hace al ser cambiado por un producto o servicio es lo que llamamos __transación__. Así, el pago es sólo una etapa de un proceso que implica un intenso flujo de intercambio de información entre varias partes: [gateways](/es/tutorial/que-es-un-gateway-de-pagos), [subadquirentes](/es/tutorial/que-es-un-subadquirente) y/o [adquirentes](/es/tutorial/que-es-un-adquirente), [banderas](/es/tutorial/que-es-una-bandera-de-tarjeta-de-credito) y [bancos emisores](/es/tutorial/que-es-el-banco-emisor).
 
-En una tienda VTEX, una transacción se inicia cada vez que un usuario elige una [condición de pago](/es/tutorial/diferencia-entre-medios-de-pago-y-condiciones-de-pago) y cierra su pedido. A partir de ahí, los datos de la compra se envían para validación de cada uno de los integrantes del proceso. Usted puede realizar un seguimiento de cada paso del [flujo de la transacción](/es/faq/flujo-de-la-transaccion-en-pci-gateway) en Pagos. En él, usted visualiza exactamente la situación de un pago a través del status mostrado.
+En una tienda VTEX, una transacción se inicia cada vez que un usuario elige una [condición de pago](/es/tutorial/diferencia-entre-medios-de-pago-y-condiciones-de-pago) y cierra su pedido. A partir de ahí, los datos de la compra se envían para validación de cada uno de los integrantes del proceso. Usted puede realizar un seguimiento de cada paso del [flujo de la transacción](/es/tutorial/flujo-de-la-transaccion-en-pagos) en Pagos. En él, usted visualiza exactamente la situación de un pago a través del status mostrado.
 
 ### Artículos relacionados
 - [¿Qué es un gateway de pagos?](/es/tutorial/que-es-un-gateway-de-pagos)
 - [¿Qué es un subadquirente?](/es/tutorial/que-es-un-subadquirente)
 - [¿Qué es un adquirente?](/es/tutorial/que-es-un-adquirente)
-- [¿Qué es una bandera de tarjeta de crédito?] (/es/tutorial/que-es-una-bandera-de-tarjeta-de-credito)
+- [¿Qué es una bandera de tarjeta de crédito?](/es/tutorial/que-es-una-bandera-de-tarjeta-de-credito)
 - [¿Qué es el banco emisor?](/es/tutorial/que-es-el-banco-emisor)
 - [Diferencia entre medios de pago y condiciones de pago](/es/tutorial/diferencia-entre-medios-de-pago-y-condiciones-de-pago)
 - [Flujo de transacción en Pagos](https://help.vtex.com/es/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ "Flujo de transacción en Pagos")
diff --git a/docs/tutorials/es/what-is-an-affiliate.md b/docs/tutorials/es/what-is-an-affiliate.md
index 32a4e0b12..7b91df18a 100644
--- a/docs/tutorials/es/what-is-an-affiliate.md
+++ b/docs/tutorials/es/what-is-an-affiliate.md
@@ -3,8 +3,8 @@ title: 'Qué es afiliado'
 id: 4bN3e1YarSEammk2yOeMc0
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:48.620Z
-updatedAt: 2022-10-05T18:24:46.905Z
-publishedAt: 2022-10-05T18:24:46.905Z
+updatedAt: 2024-05-23T16:09:45.545Z
+publishedAt: 2024-05-23T16:09:45.545Z
 firstPublishedAt: 2019-01-24T22:01:57.938Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/es/what-is-an-e-wallet.md b/docs/tutorials/es/what-is-an-e-wallet.md
index 9c0963e6c..40a0359f6 100644
--- a/docs/tutorials/es/what-is-an-e-wallet.md
+++ b/docs/tutorials/es/what-is-an-e-wallet.md
@@ -1,10 +1,10 @@
 ---
-title: '¿Qué es una cartera digital (e-wallet)?'
+title: '¿Qué es una cartera digital (ewallet)?'
 id: 4v5wcOe4A0SiaimWM2cU60
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:38.294Z
-updatedAt: 2019-12-31T15:26:35.284Z
-publishedAt: 2019-12-31T15:26:35.284Z
+updatedAt: 2023-09-26T15:16:20.294Z
+publishedAt: 2023-09-26T15:16:20.294Z
 firstPublishedAt: 2019-01-24T22:05:07.777Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: que-es-una-cartera-digital
 subcategory: 2Xay1NOZKE2CSqKMwckOm8
 ---
 
-Una cartera digital (también llamada e-wallet) es un ambiente seguro donde se pueden almacenar datos bancarios y/o de tarjeta de crédito. Esta información se cifra en el sistema y, cuando es accedida por su dueño, puede usarse para realizar compras en internet.
+Una cartera digital (también llamada ewallet) es un ambiente seguro donde se pueden almacenar datos bancarios y/o de tarjeta de crédito. Esta información se cifra en el sistema y, cuando es accedida por su dueño, puede usarse para realizar compras en internet.
 
 Comprar con una cartera digital ofrece más seguridad para el usuario, ya que no necesita informar sus datos de pago en el momento de la compra. En vez de eso, el usuario se redirige al ambiente de la cartera digital, donde deberá pasar por etapas de autenticación.
 
diff --git a/docs/tutorials/es/what-is-deposit-slip.md b/docs/tutorials/es/what-is-deposit-slip.md
index 77e0bc885..55e4f48d5 100644
--- a/docs/tutorials/es/what-is-deposit-slip.md
+++ b/docs/tutorials/es/what-is-deposit-slip.md
@@ -3,8 +3,8 @@ title: 'Qué es Ficha de Depósito'
 id: 5zcak00O9G2KqoysQggus6
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:35.451Z
-updatedAt: 2019-12-31T15:25:20.325Z
-publishedAt: 2019-12-31T15:25:20.325Z
+updatedAt: 2024-03-18T13:03:11.449Z
+publishedAt: 2024-03-18T13:03:11.449Z
 firstPublishedAt: 2019-01-24T22:10:45.867Z
 contentType: tutorial
 productTeam: Financial
@@ -23,6 +23,12 @@ Para pagar con Ficha de Depósito, el usuario debe elegir esta condición de pag
 Para efectuar la compra, el usuario debe ir a uno de los puntos acreditados y pagar el valor del documento. Este pago puede hacerse en efectivo o con tarjetas de crédito.
 
 ## Cómo aceptar Ficha de Depósito en su tienda
-Su tienda VTEX puede aceptar pagos con Ficha de Depósito, siempre que actúe en México y tenga registro en Citibanamex. Este banco mexicano tiene integración con nuestra plataforma y puede ser configurado en su tienda.
 
-Para saber cómo configurar el conector Banamex (responsable de la comunicación con Citibanamex), acceda a [este artículo del Help](/es/tutorial/configurar-gateway-banamex).
+Para consultar los proveedores que realizan transacciones con Ficha Depósito y configurarlos en tu tienda, sigue los pasos a continuación:
+
+1. En el Admin de VTEX, acceda a __Configuración de la Tienda > Pago > Configuración__, o escriba __Configuración__ en la barra de búsqueda en la parte superior de la página.
+2. En la pestaña __Condiciones de pago__, haga clic en el botón `+`.
+3. Haga clic en __FichaDepósito__.
+4. Active la condición en el campo __Status__.
+5. Seleccione las opciones de proveedor disponibles y realice las configuraciones necesarias para cada una de ellas.
+6. Haga clic en "Guardar".
diff --git a/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md b/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
index 934c25096..b093b7140 100644
--- a/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
+++ b/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Cuál es el papel de los agentes financieros en el flujo de pago de un pedido en Brasil?'
 id: 1dyPJ3gQCCO4ea2o6OMgCi
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-10-11T19:08:49.654Z
-updatedAt: 2020-11-27T19:40:35.496Z
-publishedAt: 2019-12-31T15:27:52.279Z
+updatedAt: 2024-03-18T18:55:40.724Z
+publishedAt: 2024-03-18T18:55:40.724Z
 firstPublishedAt: 2017-10-11T19:34:43.203Z
 contentType: tutorial
 productTeam: Financial
@@ -21,7 +21,7 @@ En este artículo, aclararemos los conceptos de adquirente, subadquirente, gatew
 
 ## Gateway
 
-Un gateway (también llamado gateway de pago) es un __sistema que efectúa la transmisión de los datos de las compras realizadas en su tienda en el momento del checkout__, como las empresas Braspag y Mundipagg.
+Un gateway (también llamado gateway de pago) es un __sistema que efectúa la transmisión de los datos de las compras realizadas en su tienda en el momento del checkout__.
 
 Como primer player del flujo, es responsable de enviar la información del pago recibida en el checkout a los adquirentes, banderas y [bancos emisores](https://help.vtex.com/es/tutorial/que-es-banco-emissor--7aVIVGwgtU4SWuqowSQksg) para, entonces, obtener una respuesta sobre la continuación del flujo de compra o de su cancelación. En otras palabras, el gateway envía los datos de pago y recibe respuestas para que usted sepa si una determinada compra debe o no ser confirmada, es decir, si el pago ha sido aprobado o no. 
 
@@ -29,17 +29,16 @@ Como agentes intermediarios entre un  e-commerce y sus medios de pago, los gatew
 
 Activando los [conectores](https://help.vtex.com/es/tutorial/que-es-el-conector--3lze0Cu0bmyC6u2o2iaeEA "¿Qué es el conector?") y registrando [afiliaciones de  gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444 " Registrar afiliaciones de gateway"), los datos de las compras de sus clientes podrán ser enviados a los adquirentes u otros gateways y, así, seguir el flujo de aprobación en las instituciones financieras.
 
-
 La plataforma VTEX tiene un gateway propio con certificación [PCI](https://help.vtex.com/es/tutorial/que-es-el-pci-ssc--4jo3Vkox3amSO2w4qIWa0E "Qué es el PCI SSC"), lo que significa que los datos de todos los pagos realizados en su tienda están protegidos de acuerdo con los más altos estándares de seguridad.
 
 ## Adquirente
 
 Un adquirente (también llamado de acreditador) __es una empresa especializada en procesar pagos__. A través de su red de socios acreditados (o red de adquirencia), permite que una tienda ofrezca diversas condiciones de pago a sus clientes.
- 
+
 El adquirente recibe la información del pago, la procesa y la transmite a la [bandera](https://help.vtex.com/es/tutorial/que-es-una-bandera-de-tarjeta-de-credito?locale=es "¿Qué es una bandera de tarjeta de crédito?") (cuando el medio de pago es tarjeta de crédito) y al [banco emisor](https://help.vtex.com/es/tutorial/que-es-el-banco-emisor?locale=es "¿Qué es el Banco Emisor?"). Son ejemplos de adquirente empresas como: Rede, Cielo, Elavon, GetNet y Stone. 
- 
+
 Para que su tienda VTEX pueda recibir pagos, usted necesita habilitar su comunicación con un adquirente. Esto se realiza a través de un [gateway](https://help.vtex.com/es/tutorial/que-es-un-gateway-de-pagos?locale=es "¿Qué es un gateway de pagos?"), que debe configurarse para procesar las [condiciones de pago deseadas](https://help.vtex.com/es/tutorial/condiciones-de-pago?locale=es "Configurar condiciones de pago"). Así, las compras pueden seguir el flujo de aprobación normalmente.
- 
+
 Cuando todo está en orden y una compra es autorizada por los otros players, el adquirente es responsable de transferir los valores (cobrados del cliente por el banco emisor) a la cuenta de su tienda.
 
 ## Subadquirente
@@ -57,23 +56,22 @@ Banderas son empresas responsables de definir las reglas de negocio para compras
 Las banderas mantienen una relación cercana con los adquirentes para garantizar la aceptación de sus tarjetas de crédito en los establecimientos. Así, estas promueven su uso y amplían la base de usuarios.
 
 En el [flujo de pago por tarjeta de crédito](https://help.vtex.com/es/tutorial/tarjeta-de-credito-flujo-basico-de-un-pago "Tarjeta de crédito - Flujo básico de un pago"), la bandera recibe del adquirente la información de la compra realizada en su tienda. Entonces, valida las condiciones (como el número de cuotas) y envía los datos al [banco emisor](https://help.vtex.com/es/tutorial/que-es-el-banco-emisor?locale=es "¿Qué es el Banco Emisor?"), que comprueba si el comprador tiene límite disponible. De esta forma, la bandera sirve tanto para regular el uso de la tarjeta como para servir de puente entre la adquirente y el banco del consumidor. 
- 
 
 ## Banco Emisor
 
 El Banco Emisor es la institución financiera responsable de los medios de pago, ya sean boletos bancarios, tarjetas de débito o de crédito. Es este quien, al recibir los datos de una compra hecha en su tienda, va a autorizar o no la venta (dependiendo del límite de crédito o del dinero disponible en la cuenta del usuario). Con todo correcto, el banco efectúa el cobro del valor
- 
-Este concepto es importante porque le permite configurar [condiciones especiales](https://help.vtex.com/es/tutorial/condiciones-especiales?locale=es "Configurar condiciones especiales de pago") para pagos realizados a través de bancos específicos. Además, en el caso de los boletos registrados, cada banco tiene su propia forma de emisión. Y, para hacer esta configuración, usted necesita saber cómo es el proceso del banco emisor elegido y seguir las instrucciones de [este artículo](https://help.vtex.com/es/tutorial/como-configurar-boleto-registrado?locale=es "Configurar boleto registrado"). Son ejemplos de Bancos Emisores: Itaú, Santander, Bradesco y Citibank.
 
+Este concepto es importante porque le permite configurar [condiciones especiales](https://help.vtex.com/es/tutorial/condiciones-especiales?locale=es "Configurar condiciones especiales de pago") para pagos realizados a través de bancos específicos. Además, en el caso de los boletos registrados, cada banco tiene su propia forma de emisión. Y, para hacer esta configuración, usted necesita saber cómo es el proceso del banco emisor elegido y seguir las instrucciones de [este artículo](https://help.vtex.com/es/tutorial/como-configurar-boleto-registrado?locale=es "Configurar boleto registrado"). Son ejemplos de Bancos Emisores: Itaú, Santander, Bradesco y Citibank.
 
 ## Antifraude
 
 El antifraude es un sistema especializado en analizar las compras realizadas en los sitios web, con el objetivo de identificar operaciones fraudulentas.
- 
+
 Recolecta datos sobre el comportamiento de los usuarios y los compara con patrones sospechosos para aprobar o no el pedido. Así pues, el antifraude añade una capa más de seguridad para su tienda.
- 
-En VTEX, primero el operador del pago aprueba la compra y, a continuación, el antifraude evalúa el pedido. Con todo en orden, el sistema sigue su flujo normal. Son ejemplos de antifraude: ClearSale y Konduto. 
 
----
+En VTEX, primero el operador del pago aprueba la compra y, a continuación, el antifraude evalúa el pedido. Con todo en orden, el sistema sigue su flujo normal. Son ejemplos de antifraude: ClearSale y Konduto. 
 
+<div class="alert alert-info">
 Es importante resaltar que cada negocio depende de factores específicos que influencian en la decisión sobre qué modalidad usar. Son varias las variables que pueden determinar la elección del medio de pago y cuál será su flujo financiero. Es fundamental, por lo tanto, tener en mente las necesidades y los propósitos reales del comerciante y del proyecto deseado.
+</div>
+
diff --git a/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md b/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md
index 44c427767..bbbe6e302 100644
--- a/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md
+++ b/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md
@@ -25,7 +25,7 @@ __Las tres etapas de la logística se representan por la siguiente estructura: _
 
 __Pueden ser ilustradas por el flujo abajo: __
 
-![ES Conceitos Logistics](https://images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/b610da20dede4d2536abe9b3a7f07890/ES_Conceitos_Logistics.png)
+![ES Conceitos Logistics](//images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/b610da20dede4d2536abe9b3a7f07890/ES_Conceitos_Logistics.png)
 
 ## Almacene
 Es el espacio físico utilizado para el almacenamiento de los productos de un e-commerce, funcionando como el repositorio de los ítems de su tienda.
diff --git a/docs/tutorials/es/what-is-the-difference-between-product-and-sku.md b/docs/tutorials/es/what-is-the-difference-between-product-and-sku.md
index aaf311759..fcc6f68dc 100644
--- a/docs/tutorials/es/what-is-the-difference-between-product-and-sku.md
+++ b/docs/tutorials/es/what-is-the-difference-between-product-and-sku.md
@@ -3,8 +3,8 @@ title: '¿Cuál es la diferencia entre producto y SKU?'
 id: 5yhABFDOpyiUcicce2W4CM
 status: PUBLISHED
 createdAt: 2018-01-26T17:49:48.383Z
-updatedAt: 2022-06-08T15:45:08.032Z
-publishedAt: 2022-06-08T15:45:08.032Z
+updatedAt: 2023-07-17T13:15:51.969Z
+publishedAt: 2023-07-17T13:15:51.969Z
 firstPublishedAt: 2018-01-26T18:00:17.827Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,6 +27,4 @@ Estructuralmente, primero se define la información del producto para luego crea
 
 ## Más información
 
-- [Registrar un producto](/es/tutorial/registrando-producto)
-
-- [Registrar un SKU](/es/tutorial/registrando-sku)
+- [Registrar un producto](https://help.vtex.com/es/tutorial/registrar-productos--tutorials_2567)
diff --git a/docs/tutorials/es/what-is-the-maximum-limit-of-promotions.md b/docs/tutorials/es/what-is-the-maximum-limit-of-promotions.md
index e4b7a262d..49d0fed67 100644
--- a/docs/tutorials/es/what-is-the-maximum-limit-of-promotions.md
+++ b/docs/tutorials/es/what-is-the-maximum-limit-of-promotions.md
@@ -3,8 +3,8 @@ title: '¿Cuantos cupones, tasas y promociones puedo tener en mi tienda?'
 id: frequentlyAskedQuestions_352
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:52.883Z
-updatedAt: 2021-02-01T15:43:04.116Z
-publishedAt: 2021-02-01T15:43:04.116Z
+updatedAt: 2023-07-10T18:00:19.469Z
+publishedAt: 2023-07-10T18:00:19.469Z
 firstPublishedAt: 2019-01-24T22:05:32.884Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,12 +15,12 @@ legacySlug: cual-es-el-limite-máximo-de-promociones
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-Hoy tenemos una limitación en la cantidad de promociones, tasas y cupones activos.
+Hay un límite en la cantidad de promociones, tasas y cupones activos:
 
 - [Promociones](/es/tutorial/como-criar-promocoes--tutorials_320): 100
 - [Tasas](/es/tutorial/creando-la-tasaimpuesto/): 100
 - [Cupones:](/es/tutorial/crear-cupon-de-descuento/) 50.000
 
-_Se contabilizarán solamente las promociones, tasas o cupones activos, es decir, las promociones, tasas o cupones archivados no se contabilizarán._
+Para calcular este límite sólo se tienen en cuenta las promociones, tasas o cupones activos, es decir, no se consideran las promociones, tasas o cupones archivados.
 
-Entre en contacto con VTEX si necesita modificar alguno de esos límites.
+Si necesita cambiar alguno de estos límites, póngase en contacto con nuestro [Soporte](https://help.vtex.com/en/support) para analizar la viabilidad del cambio.
diff --git a/docs/tutorials/es/what-is-the-pci-ssc.md b/docs/tutorials/es/what-is-the-pci-ssc.md
index ee85a2161..b713b2c4f 100644
--- a/docs/tutorials/es/what-is-the-pci-ssc.md
+++ b/docs/tutorials/es/what-is-the-pci-ssc.md
@@ -3,8 +3,8 @@ title: 'Qué es el PCI SSC'
 id: 4jo3Vkox3amSO2w4qIWa0E
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:48.373Z
-updatedAt: 2021-09-22T12:32:07.193Z
-publishedAt: 2021-09-22T12:32:07.193Z
+updatedAt: 2024-07-23T15:26:30.020Z
+publishedAt: 2024-07-23T15:26:30.020Z
 firstPublishedAt: 2019-01-24T22:12:41.627Z
 contentType: tutorial
 productTeam: Financial
@@ -21,4 +21,4 @@ Fue fundado por las empresas American Express, Discover Financial Services, JCB
 
 Es una certificación que VTEX tiene para sus servicios, dada por esa instituición, y que trae informaciones de seguridad disponibilizadas para las tiendas y sus consumidores. 
 
-Para obtener más información, consulte la [categoría de certificación VTEX PCI SSC](https://secure.vtex.com/?an=VTEX).
+Para obtener más información, consulte la [categoría de certificación VTEX PCI SSC](https://vtex.com/mx-es/compliance/certifications/).
diff --git a/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
index fa1dbf2d1..408bcd8f9 100644
--- a/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
@@ -35,7 +35,7 @@ Estos tipos son:
 
 Para crear una tag de control personalizado, basta hacer clic en __Add__, registrar un nombre y una tag, luego seleccionar el tipo.
 
-![cms-custom-elements EN / ES](https://images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
+![cms-custom-elements EN / ES](//images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
 
 <div class="alert alert-warning">
   <p><b>Atención:</b> no cree un control del tipo HTML con un elemento <code>title</code>. Esto puede interferir con el buen funcionamiento de su tienda.</p>
diff --git a/docs/tutorials/es/what-is-transparent-checkout.md b/docs/tutorials/es/what-is-transparent-checkout.md
index 0ee1230f5..d4f193f7f 100644
--- a/docs/tutorials/es/what-is-transparent-checkout.md
+++ b/docs/tutorials/es/what-is-transparent-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Qué es el checkout transparente?'
 id: 2Y4ECegUmcYUggmck2GOwe
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-02-27T18:58:12.252Z
-updatedAt: 2020-11-27T19:39:49.137Z
-publishedAt: 2020-05-31T14:34:28.895Z
+updatedAt: 2023-07-20T18:06:08.385Z
+publishedAt: 2023-07-20T18:06:08.385Z
 firstPublishedAt: 2018-02-27T20:40:08.480Z
 contentType: tutorial
 productTeam: Shopping
diff --git a/docs/tutorials/es/what-offline-payment-conditions-are-available-in-latin-america.md b/docs/tutorials/es/what-offline-payment-conditions-are-available-in-latin-america.md
index 1e9b4d9e7..7b826ff06 100644
--- a/docs/tutorials/es/what-offline-payment-conditions-are-available-in-latin-america.md
+++ b/docs/tutorials/es/what-offline-payment-conditions-are-available-in-latin-america.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Qué condiciones de pago offline están disponibles en América Latina?'
 id: 2lXPwiH6KcsSMuWaoigueq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.602Z
-updatedAt: 2019-12-31T15:19:41.744Z
-publishedAt: 2019-12-31T15:19:41.744Z
+updatedAt: 2024-03-19T12:05:40.449Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:19.092Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md b/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md
index 196389294..92258dee6 100644
--- a/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md
+++ b/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md
@@ -3,8 +3,8 @@ title: '¿Qué hacer cuando mi informe de exportaciones no llega al email?'
 id: 1zUBgmgkgMZyHyy0veR7Oj
 status: PUBLISHED
 createdAt: 2022-10-17T19:56:25.618Z
-updatedAt: 2023-03-28T23:24:48.040Z
-publishedAt: 2023-03-28T23:24:48.040Z
+updatedAt: 2024-06-11T16:48:56.974Z
+publishedAt: 2024-06-11T16:48:56.974Z
 firstPublishedAt: 2022-10-17T19:59:15.174Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: que-hacer-cuando-mi-informe-de-exportaciones-no-llega-al-email
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-En VTEX, todas las tiendas pueden acceder a un informe sobre las [exportaciones de datos](/tutorial/exportando-dados?locale=es) del [Master Data](/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw) - módulo que reúne información de los clientes de una tienda.
+En VTEX, todas las tiendas pueden acceder a un informe sobre las [exportaciones de datos](https://help.vtex.com/es/tutorial/exportacion-de-datos--tutorials_1125) del [Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) - módulo que reúne información de los clientes de una tienda.
 
 Estos informes se envían al correo electrónico del solicitante de la acción. Sin embargo, por motivos externos a VTEX, es posible que ese contenido demore más de lo esperado para llegar a la caja de entrada del solicitante.
 
@@ -24,10 +24,9 @@ Pero existe una manera de extraer manualmente este informe accediendo al Master
 A continuación, entienda el paso a paso para hacerlo:
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
-2. Haga clic en __Exportations__.
-![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
-3. Asegúrese de que la pestaña abierta es la de __"Applications"__.
-![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
-4. En __"Status de exportaciones"__, haga clic en el informe que desea descargar.
+2. Haga clic en __Exportaciones__. ![exportaciones-md](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/b47b9d6d497864bf45547f77c3bdd927/exportaciones.png)
+3. Asegúrese de que la pestaña abierta es la de __Aplicaciones__.
+4. En __Status de las exportaciones__, identifique la línea del informe que desea descargar.
+5. Si el __Status__ es __Realizado - Descargar__, haga clic en **Descargar** para descargar el archivo.
 
 De esta forma, es posible acceder a este material aunque el email original no haya llegado al solicitante.
diff --git a/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md b/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md
new file mode 100644
index 000000000..c38251318
--- /dev/null
+++ b/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md
@@ -0,0 +1,96 @@
+---
+title: 'Gestión y detalles de WhatsApp AI Campaigns'
+id: q9JqDErMqGV4zvsYqkD4s
+status: PUBLISHED
+createdAt: 2024-06-25T11:58:05.514Z
+updatedAt: 2024-06-25T16:28:52.542Z
+publishedAt: 2024-06-25T16:28:52.542Z
+firstPublishedAt: 2024-06-25T16:11:51.825Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gestion-y-detalles-de-whatsapp-ai-campaigns
+locale: es
+legacySlug: gestion-y-detalles-de-whatsapp-ai-campaigns
+subcategory: 4SC2gPmUH3cHD5HjGfQ5Vg
+---
+
+Esta página ofrece una descripción completa de la gestión y las características de WhatsApp AI Campaigns en la plataforma VTEX, cubriendo desde la configuración hasta el seguimiento de métricas de desempeño para optimizar la efectividad de tus campañas y maximizar las conversiones.
+
+Consulta este artículo para aprender a gestionar y supervisar tus campañas:
+
+- [Seleccionar fechas](#seleccionar-fechas)
+- [Enviar informes](#enviar-informes)
+- [Editar campaña](#editar-campaña)
+- [Pausar campaña](#pausar-campaña)
+- [Consultar detalles en el dashboard Análisis](#consultar-detalles-en-el-dashboard-analisis)
+
+## Gestión de WhatsApp AI Campaigns
+
+La página de WhatsApp AI Campaigns permite consultar información sobre análisis y campañas activas.
+
+### Seleccionar fechas
+
+Navega por días concretos para ver los mensajes enviados durante cada periodo.
+
+1. En el Admin VTEX, accede a **Promociones > Campañas de WhatsApp > Vista general**.
+2. Haz clic en el selector de fechas.
+3. Selecciona la fecha en la que deseas consultar datos de los análisis.
+
+### Enviar informes
+
+1. En el Admin VTEX, accede a **Promociones > Campañas de WhatsApp > Vista general**.
+2. Haz clic en `Enviar informe` en la esquina superior derecha de la sección.
+3. Indica el email que recibirá el informe.
+4. Haz clic en `Enviar informe`.
+
+El informe enviado por correo electrónico será un archivo `csv` con la siguiente información:
+
+- **userId:** identificador único del usuario que realizó la compra.
+- **deliveredReminderAt:** fecha y hora en que se envió un recordatorio sobre la compra al usuario.
+- **readReminderAt:** fecha y hora en que el usuario visualizó el recordatorio enviado.
+- **orderCreatedAt:** fecha y hora en que se creó el pedido en el sistema.
+- **hasClickedOnReminder:** indica si el usuario hizo clic o no en el recordatorio enviado.
+- **checkoutItems:** lista de artículos que el usuario añadió al carrito durante el proceso de compra.
+- **orderItems:** lista de artículos que fueron efectivamente comprados por el usuario.
+- **orderTotal:** valor total del pedido, sumando el precio de todos los artículos comprados.
+- **currency:** moneda utilizada para el pago del pedido.
+- **orderFormId:** identificador único del formulario de pedido utilizado durante la compra.
+
+### Editar campaña
+
+Una vez configurada la campaña, puedes editar el idioma o el tipo de mensaje que deseas personalizar.
+
+1. En el Admin VTEX, accede a Promociones > Campañas de WhatsApp > Vista general.
+2. Haz clic en el ícono <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Haz clic en `Editar`.
+4. Cambia la información que desees.
+5. Haz clic en `Confirmar`.
+
+### Pausar campaña
+
+Para pausar el envío de mensajes de una campaña:
+
+1. En el Admin VTEX, accede a Promociones > Campañas de WhatsApp > Vista general.
+2. Haz clic en el ícono <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Haz clic en Pausar.
+4. Haz clic en `Confirmar`.
+
+## Consultar detalles en el dashboard Análisis
+
+Puedes encontrar información sobre tus campañas en curso en el Admin VTEX.
+
+![Visão geral-ES](//images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/27df78b45cdda1fd0aa89bde051172a3/Vis_o_geral-ES.png)
+
+A continuación se detallan las métricas disponibles:
+
+- **Mensajes entregados:** número total de mensajes que llegaron correctamente a los destinatarios previstos.
+- **Mensajes leídos:** número total de mensajes abiertos por los destinatarios; esto indica el engagement del público.
+- **Clics únicos:** número de usuarios que han hecho clic en los links de los mensajes.
+- **Total de clics:** número total de interacciones con los botones de respuesta en los mensajes, lo que proporciona una medida cuantitativa del engagement.
+- **Total de conversiones:** el número total de conversiones que ocurren después de la entrega exitosa de un mensaje a un destinatario. El total de conversiones es la suma de las dos métricas siguientes:
+      - **Conversiones asistidas:** conversiones que ocurren dentro de los 3 días posteriores a la recepción del mensaje.
+      - **Conversiones por Clic (CTC):** conversiones que ocurren cuando los usuarios hacen clic en el enlace del mensaje y realizan una compra dentro de los 15 días.
+- **Valor total de conversiones:** valor total de pedidos proveniente de conversiones.
+- **Valor total de las conversiones por clic:** valor total del pedido proveniente de las conversiones por clic.
+
diff --git a/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md b/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md
index 69ff3ddf1..3c56714c6 100644
--- a/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md
+++ b/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md
@@ -22,4 +22,4 @@ Pero recuerde: la suscripción sólo aparece en las propiedades después de que
 1. Acceda al __Gestión de Pedidos__.
 2. Haga clic en la pestaña __Assinaturas__.
 
-![subscription ES](https://images.ctfassets.net/alneenqid6w5/2ujHgxMGUwiuWCq4kaKc4C/def14c61a1d2f5ec940db40a6062a540/subscription_ES.png)
+![subscription ES](//images.ctfassets.net/alneenqid6w5/2ujHgxMGUwiuWCq4kaKc4C/def14c61a1d2f5ec940db40a6062a540/subscription_ES.png)
diff --git a/docs/tutorials/es/which-security-certificates-may-be-added-to-my-store.md b/docs/tutorials/es/which-security-certificates-may-be-added-to-my-store.md
index 382077b8a..a5653abbc 100644
--- a/docs/tutorials/es/which-security-certificates-may-be-added-to-my-store.md
+++ b/docs/tutorials/es/which-security-certificates-may-be-added-to-my-store.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Cuales certificados de seguridad pueden ser añadidos a mi tienda?'
 id: 29ivkiHbXqMIa8QMKCSQ2K
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:48.223Z
-updatedAt: 2019-12-31T15:23:12.479Z
-publishedAt: 2019-12-31T15:23:12.479Z
+updatedAt: 2024-03-11T13:21:15.878Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:15:04.845Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/es/white-label-seller.md b/docs/tutorials/es/white-label-seller.md
index 0e01c9760..7e6bc80bb 100644
--- a/docs/tutorials/es/white-label-seller.md
+++ b/docs/tutorials/es/white-label-seller.md
@@ -3,8 +3,8 @@ title: 'Seller white label'
 id: 5orlGHyDHGAYciQ64oEgKa
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:34.034Z
-updatedAt: 2022-10-17T17:52:42.676Z
-publishedAt: 2022-10-17T17:52:42.676Z
+updatedAt: 2023-07-14T15:15:56.338Z
+publishedAt: 2023-07-14T15:15:56.338Z
 firstPublishedAt: 2019-01-24T22:03:52.175Z
 contentType: tutorial
 productTeam: Channels
@@ -48,3 +48,4 @@ Para agregar un seller white label, es necesario tener este modelo previsto en e
 - [Selección de sellers white label](https://help.vtex.com/es/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa)
 - [Configurar marketplaces VTEX](https://help.vtex.com/es/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb)
 - [Agregar seller](https://help.vtex.com/es/tutorial/adicionar-seller--tutorials_392)
+- [Elegir entre cuenta estándar, cuenta franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78)
diff --git a/docs/tutorials/es/white-label-sellers-selection.md b/docs/tutorials/es/white-label-sellers-selection.md
index 1c613de59..6e565b270 100644
--- a/docs/tutorials/es/white-label-sellers-selection.md
+++ b/docs/tutorials/es/white-label-sellers-selection.md
@@ -112,13 +112,13 @@ Si hay un empate entre los _sellers_ con los criterios de menor costo o mejor pl
 
 Un cliente agregó cinco SKU al carrito. Cada uno de los _sellers_ que ofrece la opción de entrega en su región (_sellers_ A, B, C y D) tiene en su [inventario](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) solo una parte de los _ítems_, tal como se muestra en la imagen a continuación:
 
-![print_selecao_seller_white_label_1](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
+![print_selecao_seller_white_label_1](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
 
 La plataforma VTEX selecciona al _seller_ que tiene disponible en su _stock_ el número máximo de SKU del carrito. En este caso, el _seller_ B es el único que entrega tres SKU. 
 
 Luego de seleccionar al _seller_ B, aún quedan dos SKU sin entregar. Si un único _seller_ enviara ambos, ese sería el factor decisivo para la selección, ya que el objetivo es reunir la menor cantidad de _sellers_ para cubrir el carrito. Sin embargo, y de acuerdo con la imagen a continuación, se necesitan a los _sellers_ A y C para entregar los SKU 1 y 4:
 
-![print_selecao_seller_white_label_2](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
+![print_selecao_seller_white_label_2](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
 
 En la primera imagen, el _seller_ C podía entregar los SKU 3 y 4, y el _seller_ D entregaría el SKU 5. No obstante, se seleccionó al _seller_ B para entregar esos _ítems_, entonces, no se tienen en cuenta esos SKU en las otras etapas de selección. Esto se representó eliminando la flecha del _seller_ C hacia el SKU 3, y la flecha del _seller_ D hacia el SKU 5.
 
@@ -128,7 +128,7 @@ El resultado de la selección para la entrega es una combinación entre los _sel
 
 Un cliente agregó cinco SKU al carrito y hay cuatro _sellers_ (A, B, C y D) que entregan los pedidos en su región. Ninguno de ellos tiene en su [inventario](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) todos los _ítems_, tal como se muestra en la imagen a continuación:
 
-![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+![print_selecao_seller_white_label_3](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
 
 La plataforma VTEX selecciona al _seller_ que tiene disponible en su _stock_ el mayor número de los SKU del carrito. Tanto el _seller_ B como el _seller_ D pueden entregar tres _ítems_, y como ambos entregan el SKU 3, compiten entre ellos.
 
@@ -141,11 +141,11 @@ Supongamos que el _seller_ B tiene la entrega más económica, y que el _seller_
 
 - **Entrega más rápida:** cuando se selecciona al _seller_ D, quedan sin entregar los SKU 3 y 4. El _seller_ C puede entregar ambos, por lo que resulta elegido y el resultado de la selección es la combinación de los _sellers_ D y C.
 
-![print_selecao_seller_white_label_4](https://images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
+![print_selecao_seller_white_label_4](//images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
 
 - **Entrega más económica:** cuando se selecciona al _seller_ B, quedan sin entregar los SKU 1 y 4. Como solo el _seller_ A entrega el SKU 1, y solo el _seller_ C entrega el SKU 4, el resultado de la selección es una combinación de los _sellers_ A, B y C. 
 
-![print_selecao_seller_white_label_5](https://images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
+![print_selecao_seller_white_label_5](//images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
 
 Las flechas repetidas de los _sellers_ que entregaban los SKU ya cubiertos por los _sellers_ B y D se eliminaron de las imágenes que contemplaban las opciones de entrega más económica y más rápida. Esto se debe a que en las etapas de selección sucesivas, los SKU ya cubiertos no se tienen en cuenta.
 
diff --git a/docs/tutorials/es/why-dont-marketplace-orders-integrate-with-my-store.md b/docs/tutorials/es/why-dont-marketplace-orders-integrate-with-my-store.md
new file mode 100644
index 000000000..fc4100ccb
--- /dev/null
+++ b/docs/tutorials/es/why-dont-marketplace-orders-integrate-with-my-store.md
@@ -0,0 +1,44 @@
+---
+title: '¿Por qué los pedidos del marketplace no se integran con mi tienda?'
+id: 275YvF8dyry5KmfY9epoET
+status: PUBLISHED
+createdAt: 2024-06-21T14:24:48.621Z
+updatedAt: 2024-06-21T14:50:25.468Z
+publishedAt: 2024-06-21T14:50:25.468Z
+firstPublishedAt: 2024-06-21T14:48:49.434Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: por-que-los-pedidos-del-marketplace-no-se-integran-con-mi-tienda
+locale: es
+legacySlug: por-que-los-pedidos-del-marketplace-no-se-integran-con-mi-tienda
+subcategory: 2LcLWCYaEm5qPmOuYUiKIS
+---
+
+**Tags:** pedidos, marketplace  
+**Palabras clave:** integración, marketplace, pedidos, SKU, stock  
+
+Cuando se producen errores de integración de pedidos entre un marketplace y tu tienda, se muestran mensajes en la página de cada pedido, informando el error ocurrido. Los posibles errores de integración de pedido son los siguientes:  
+
+- Información de envío incompleta.  
+- Divergencia de precios.  
+- ID de SKU no válido.  
+- Indisponibilidad de stock.  
+- Status de indisponibilidad.  
+- Transportadora no registrada en el ERP (Enterprise Resource Planning).  
+
+Comprueba tanto el status de la integración de pedidos como los mensajes accediendo al Admin VTEX. **Marketplace > Conexiones > Pedidos** o ingresa **Pedidos** en la barra de búsqueda.   
+
+## Solución
+
+Consulta la tabla a continuación para comprender el significado del error y corregirlo:  
+
+| **Tipo de error** | **Significado** | **Acción requerida** |
+|:---:|:---:|:---:|
+| **Información de envío incompleta** | Los datos de envío están incompletos o rellenados incorrectamente. | Corregir o rellenar los datos solicitados como se indica en [Flujo y status de pedidos.](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196) |
+| <br>**Divergencia de precios** | <br>El valor total del pedido pagado en el marketplace difiere del valor esperado por la tienda VTEX, y esta diferencia de precios supera el porcentaje aceptado por la tienda VTEX o la regla de divergencia de precios no está configurada.<br>**Ejemplo**<br>El valor total pagado por el pedido en el marketplace es de 311.77 USD, el valor esperado por la tienda es de 313.61 USD. Es decir, hay una diferencia de 1.84 USD. | [Reprocesar pedido](https://help.vtex.com/es/tutorial/verificando-integracao-no-bridge#pedidos) o Configurar la [Regla de divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW). |
+| **ID de SKU no válido** | Los ID de los productos registrados en la política comercial son diferentes de los ID registrados en el marketplace. | Cambiar los ID de los SKU en el marketplace para que tengan los mismos códigos que los productos en la política comercial. |
+| **Indisponibilidad de stock** | El SKU no se muestra en el marketplace.<br>Consulta la lista completa de [Errores de integración de stock con marketplaces.](https://help.vtex.com/es/tutorial/erros-de-integracao-de-estoque-com-marketplaces--32bcsv9Dx1Dtl0YQOwWDpc) | Aplicar la corrección requerida según el error identificado en [Errores de integración de stock con marketplaces.](https://help.vtex.com/es/tutorial/erros-de-integracao-de-estoque-com-marketplaces--32bcsv9Dx1Dtl0YQOwWDpc)<br>  |
+| **Status de Indisponibilidad** | El producto está disponible en tu tienda, pero el marketplace ha bloqueado el ítem en tu storefront. El status del pedido será **Unavailable.** | Ponte en contacto con el marketplace para liberar el pedido. |
+| **Transportadora no registrada en el ERP (Enterprise Resource Planning)** | La transportadora seleccionada para el envío del producto no está registrada en el ERP.<br>**Ejemplo**<br>Se registró una nueva transportadora en VTEX, pero no en el ERP. | Actualizar el registro de transportadoras en el ERP de acuerdo con las registradas en VTEX. |
+
diff --git a/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 6bc4257a1..b6d4ce5b1 100644
--- a/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -1,10 +1,10 @@
 ---
 title: '¿Por qué un cliente logró registrar un CPF en un campo de CNPJ?'
 id: K6zJn8JFOKk5ON1XFB6ZJ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-10-17T19:22:31.749Z
-updatedAt: 2023-03-28T22:55:52.032Z
-publishedAt: 2023-03-28T22:55:52.032Z
+updatedAt: 2024-07-11T19:21:58.380Z
+publishedAt: 
 firstPublishedAt: 2022-10-17T19:43:17.176Z
 contentType: tutorial
 productTeam: Master Data
@@ -37,7 +37,7 @@ Siga estos pasos para validar la información:
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
 2. En el cuadro __Profile System__, haga clic en __Clientes__.
-3. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+3. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 4. Haga clic en el registro del cliente para acceder a los detalles del perfil.
 
 En la sección __Contato__, usted verá que la opción `Es Empresa?` Se llena con el valor `No`. Al mismo tiempo, en la sección __Datos de la empresa__, usted verá que el campo `Tipo documento` tiene el valor `cnpj`.
diff --git a/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md b/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md
index 34ee4a245..5d99ffc31 100644
--- a/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md
+++ b/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md
@@ -1,10 +1,10 @@
 ---
-title: 'Cómo escribir un ticket completo para Soporte VTEX'
+title: 'Buenas prácticas para abrir un ticket con el soporte VTEX'
 id: 6u4ehk6F0ksuDgYuCbFDRX
 status: PUBLISHED
 createdAt: 2023-03-23T22:00:24.560Z
-updatedAt: 2023-03-24T18:24:48.580Z
-publishedAt: 2023-03-24T18:24:48.580Z
+updatedAt: 2024-04-22T23:02:06.481Z
+publishedAt: 2024-04-22T23:02:06.481Z
 firstPublishedAt: 2023-03-23T22:57:50.828Z
 contentType: tutorial
 productTeam: Others
@@ -23,12 +23,55 @@ Recuerda que mientras más contexto los especialistas tengan, más rápido podr
 
 Este artículo es una guía para que los clientes y partners abran los tickets con información pertinente para agilizar el proceso de investigación de nuestros especialistas. Se divide en las siguientes secciones:
 
-- [Guías generales](#guias-generales)
-- [Información pertinente por escenario](#informacion-pertinente-por-escenario)
+- [Antes de abrir un ticket](#antes-de-abrir-un-ticket)
+- [Rellenar un ticket](#rellenar-un-ticket)
 
-## Guías generales
+Para aprender a abrir un ticket en VTEX, consulta el artículo [Abrir tickets para el soporte VTEX](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-Para rellenar un ticket de forma completa, se deben seguir algunas guías:
+## Antes de abrir un ticket
+
+Antes de abrir un ticket, verifica si el problema está relacionado con las personalizaciones de la tienda. Si el origen del problema es una personalización, debes ponerte en contacto con el equipo responsable de la misma. De lo contrario, abre un ticket con el equipo de soporte de VTEX.
+
+### Carrito y Checkout y Tiendas en CMS
+
+Es importante comprobar que el problema se produce sin personalizaciones activas en la tienda. Para realizar esta prueba, desactiva las personalizaciones (JS y CSS) e intenta reproducir el error según se explica en el artículo [Cómo bloquear personalizaciones para investigar problemas en el frontend de la tienda](https://help.vtex.com/es/faq/como-bloquear-customizacoes-para-investigar-problemas-no-front-end-da-loja--5c1a4bvVK8rAvKLczhkCnY). Si el error continúa, ponte en contacto con [nuestro equipo de soporte](https://help.vtex.com/es/support).
+
+### Store Framework
+Para comprobar si el problema está asociado a IO, sigue los pasos a a continuación:
+
+1.	Abre la línea de comandos e inicia sesión en tu tienda utilizando VTEX IO CLI.
+2. Accede a un workspace de desarrollo ejecutando el siguiente comando:
+    ```
+    vtex use {workspace}
+    ```
+3.	Si tu tienda tiene un tema de Store Framework instalado, desinstálalo utilizando el siguiente comando:
+    ```
+    vtex uninstall {tema}
+    ```
+    <div class="alert alert-info">
+    Puedes comprobar si hay algún tema instalado utilizando el comando <code>vtex list</code>, que muestra una lista de todas las aplicaciones instaladas en la tienda.
+    </div>
+4.	Clona el tema predeterminado de Store Framework en tu computadora.
+5.	En la línea de comandos, accede a la carpeta del tema predeterminado.
+6.	Ejecuta el comando:
+
+    ```
+    vtex link
+    ```
+
+    <div class="alert alert-warning">Si tu tienda no tiene la aplicación Reviews and Ratings instalada, puede aparecer un error al intentar establecer el vínculo. Para evitar este problema, remueve esta aplicación de la lista de `peer dependencies` del archivo `manifest.json` del tema predeterminado. </div>
+
+7.	Accede al storefront de tu workspace mediante la URL:
+    ```
+    https://{workspace}--{nombreDeLaCuenta}.myvtex.com
+    ```
+8.	Intenta reproducir el error.
+
+Si el error no se produce después del bloqueo de los archivos o en el tema predeterminado de Store Framework, el error está asociado a las personalizaciones del sitio web. Para solucionarlo, debes ponerte en contacto con el equipo responsable del frontend de tu tienda.
+
+## Rellenar un ticket
+
+Para rellenar un ticket de forma completa, sigue estas guías:  
 
 | Información | Guías |
 | ----------- | ----------- |
@@ -37,9 +80,12 @@ Para rellenar un ticket de forma completa, se deben seguir algunas guías:
 | Escenario esperado | Proporciona los detalles del escenario esperado, en comparación con lo que está ocurriendo. |
 | Pruebas y validaciones | Si ya intentaste solucionar el problema, detalla las acciones que ya hayas realizado, qué documentación consultaste y los resultados. |
 | Alcance del ticket | <p> - No abordes más de un problema en un mismo ticket. </p> <p> - No crees más de un ticket para el mismo problema. </p> |
-| Prioridad | Comprueba la prioridad correcta según la naturaleza del problema para que se aplique el SLA correcto. |
+| Prioridad | 
+Comprueba la [prioridad](https://help.vtex.com/es/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9#prioridade-de-chamados) según la naturaleza del problema. Lea mas en [¿Como funciona el soporte de VTEX?](https://help.vtex.com/es/faq/como-funciona-el-soporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe?&utm_source=autocomplete)|
+ | Información pertinente sobre el producto | 
+Consulta la siguiente tabla para ver la información pertinente dependiendo del producto en el que se produzca el error.
 
-## Información pertinente por escenario
+### Información pertinente sobre el producto
 
 Hay varios escenarios que pueden dar lugar a la apertura de un ticket. En esta sección, se enumeran los escenarios más comunes y la información básica necesaria para abrir un ticket en cada uno.
 
diff --git a/docs/tutorials/pt/ab-testing-how-where-when-and-why.md b/docs/tutorials/pt/ab-testing-how-where-when-and-why.md
index 19706aa98..66ed30fc7 100644
--- a/docs/tutorials/pt/ab-testing-how-where-when-and-why.md
+++ b/docs/tutorials/pt/ab-testing-how-where-when-and-why.md
@@ -1,10 +1,10 @@
 ---
-title: 'Teste AB: como, onde, quando e por quê'
+title: 'Teste A/B para lojas no CMS Portal Legado'
 id: tutorials_581
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:39.133Z
-updatedAt: 2019-12-31T17:00:44.367Z
-publishedAt: 2019-12-31T17:00:44.367Z
+updatedAt: 2024-04-04T17:00:10.270Z
+publishedAt: 2024-04-04T17:00:10.270Z
 firstPublishedAt: 2017-04-27T23:03:41.601Z
 contentType: tutorial
 productTeam: Others
@@ -15,65 +15,24 @@ legacySlug: teste-ab-como-onde-quando-e-porque
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-Ultimamente, tem aumentado a procura de informações sobre teste AB. Basta participar de qualquer evento sobre o mercado de e-commerce e lá está o assunto nas rodas de especialistas. Mas por que tanto interesse em saber mais sobre o assunto? Simples: esse interesse é reflexo da evolução do e-commerce nacional.
+O teste A/B é um método para comparar duas versões de um site e determinar qual delas tem um melhor desempenho em relação ao engajamento do usuário, conversões e outras métricas relevantes. O objetivo do teste A/B é avaliar qual versão (A ou B) apresenta taxas de sucesso mais altas e resultados aprimorados.
 
-Em primeiro lugar, é importante esclarecer a diferença entre Teste AB e Teste Multivariável:
+No contexto das lojas no CMS - Portal Legado, ferramentas nativas de teste A/B não estão disponíveis. No entanto, você ainda pode aproveitar soluções de terceiros como [Optimizely](https://docs.developers.optimizely.com/full-stack-experimentation/docs/welcome) e sua [solução de teste A/B](https://docs.developers.optimizely.com/full-stack-experimentation/docs/run-a-b-tests). Essa ferramenta permite que você crie e gerencie testes A/B, possibilitando a análise do desempenho de diferentes versões do site em um ambiente controlado.
 
-- __Teste AB__: nada mais é do que duas (ou mais) versões de uma mesma página criadas com um elemento diferente para testar qual versão apresenta um melhor resultado. Esses testes são realizados ao mesmo tempo, ou seja, as duas versões vão ao ar simultaneamente para atingir o mesmo perfil de público em um mesmo período de tempo:
+## Casos de uso para teste A/B
+Na VTEX o teste A/B pode ser realizado entre as seguintes tecnologias de desenvolvimento de loja:
 
-![Botão de cor verde e botão de cor azul lado a lado](//images.contentful.com/alneenqid6w5/5bq3VDpgakg8CMMKIyU2kw/54a21a6a88e9d173b16207922e8a0cc8/testando-cor-do-botao.jpg)
+| Tecnologia     | É possível teste A/B nativo entre elas?     | Referência     |
+| ---------- | ---------- | ---------- |
+| CMS Portal Legado - VTEX IO (Store Framework)       | Sim       | [A/B testing Legacy and IO store versions](https://developers.vtex.com/docs/guides/vtex-io-documentation-performing-ab-testing-between-legacy-and-io)       |
+| CMS Portal Legado - FastStore       | Não       | -       |
+| VTEX IO (Store Framework) - VTEX IO (Store Framework)       | Não      | -      |
+| VTEX IO (Store Framework) - FastStore      | Não      | -       |
+| FastStore - FastStore       | Não       | -       |
 
-_No exemplo acima estamos testando o elemento “cor do botão”_. 
+## Teste A/B entre CMS — Portal Legado e as versões da loja VTEX IO
 
-- __Teste Multivariável__: parecido com o Teste AB, o Teste Multivariável também tem o propósito de testar versões diferentes de uma mesma tela, porém são testadas mais de uma alteração por versão criada.
+Se você está considerando migrar sua loja para o VTEX IO e deseja comparar o desempenho por meio de testes A/B, consulte o [guia A/B testing Legacy and IO store versions](https://developers.vtex.com/docs/guides/vtex-io-documentation-performing-ab-testing-between-legacy-and-io). Este guia fornece instruções sobre como realizar testes A/B entre os espaços de trabalho da loja no CMS - Portal Legado e no VTEX IO.
 
-![Botão de cor verde e botão de cor vermelha com fonte grande e texto diferente lado a lado](//images.contentful.com/alneenqid6w5/3Mxf275gXuuywK8m8a88wu/edc0f9b93ff479f51b5b4335148f7c8b/testando-cor-texto-fonte.jpg)
-
-_Neste exemplo, estamos testando o elemento “cor do botão”, o elemento “texto” e o elemento “tamanho da fonte”_
-
-Explicadas as diferenças, nos basta saber por que os profissionais especialistas em conversão defendem o uso do Teste AB muito mais do que o Teste Multivariável.
-
-É óbvio! Com o Teste AB você sabe exatamente o que gerou a variação nos resultados e pode aprender com isso. Já com o Teste Multivariável fica impossível dizer se a variação foi causada pela cor do botão ou pela alteração do texto.
-
-Existem sites específicos para a divulgação de resultados de Teste AB. Mas apesar de muito úteis, eles devem ser vistos com cuidado, pois nem tudo que funciona para o público A vai funcionar para o público B. Além disso, o perfil do consumidor brasileiro é bastante diferente do perfil do consumidor estrangeiro.
-
-Vale dar uma olhada nos sites whichtestwon.com e abtests.com pra conhecer um pouco do que outros lojistas andam testando.
-
-Sabendo disso, surgem algumas dúvidas comuns:
-
-- Como realizar um teste destes?
-- Onde posso testar? Em que parte da página?
-- Quando posso começar a testar?
-- Por que devo gastar recurso testando minha loja?
-
-### Como?
-
-Hoje existem diversas ferramentas no mercado (pagas e gratuitas) para realizar Teste AB. Eu recomendo o uso do Google Analytics, que ganhou recursos do extinto Google Optimizer para realizar Testes AB de forma simples e rápida. Basta acessar sua conta no Analytics e procurar a aba **Content > Experiments** (Conteúdo > Experiências). Tem um passo a passo simples de ser seguido e você não encontrará grandes dificuldades pra rodar um teste.
-
-Também recomendo a ferramenta Visual Website Optimizer. Ela é paga, mas oferece recursos mais avançados para realização dos testes, inclusive com a capacidade de alterar algumas coisas na página sem a necessidade de contatar o desenvolvedor front-end. Vale a pena dar uma olhada na versão de teste da ferramenta para conhecer um pouco mais.
-
-Qualquer teste deve ser aplicado por um período mínimo de uma semana, pois usuários de final de semana possuem o perfil de navegação diferente dos usuários que navegam durante a semana. Os testes devem ser aplicados no mínimo 1.000 impressões por versão criada, ou seja, se você criou duas versões de uma mesma página, não tire nenhuma conclusão enquanto o teste não for exibido pelo menos 2.000 vezes.
-
-### Onde
-
-Todas as páginas do seu site podem participar de Testes AB. Os testes farão com que você entenda melhor como o usuário pensa, o que funciona e o que não funciona na internet.
-
-Os testes podem ser aplicados em todos os elementos da página como cores de botões, textos, cores de texto, tamanho de fontes, disposição de um elemento, diagramação da página, inserção de ícones, tamanho de imagens, tipo de imagem, etc.
-
-Quanto mais você testar, maior será o conhecimento adquirido sobre o perfil do usuário.
-
-Mesmo os testes que não resultarem em um aumento nas suas taxas de conversão ou até os que representarem uma queda significativa nos resultados podem ser usados pra melhorar todas as outras páginas e fazer sua conversão decolar.
-
-### Quando?
-
-A grande vantagem dos Testes AB é que o usuário final não tem noção de que participou de algum teste, pois ele verá apenas uma das versões criadas e terá a certeza de que aquela é a sua página original independente de qual for apresentada.
-Sendo assim, não há limites de quantos testes podem ser criados e aplicados, por isso, teste o tempo todo; todo o tempo.
-
-### Por quê?
-
-Essa é uma pergunta que eu poderia dar dezenas de justificativas, mas vou focar nas mais importantes:
-
-1. Apenas com o Teste AB você vai entender quais as melhores decisões a tomar na sua loja baseado em dados mensuráveis sobre o seu público específico. Nem tudo o que funciona pro seu concorrente vai funcionar pra você;
-2. Apostar as suas fichas em um layout puramente baseado no instinto do designer é perigoso e pode dar muito prejuízo. Gosto pessoal é um perigo;
-3. Não adianta investir toda a sua verba em trazer tráfego para a sua loja se ela não estiver preparada para receber seus visitantes e convertê-los em compradores. Somente com a aplicação destes testes você saberá o que deve ser feito DENTRO da sua loja para aumentar a sua taxa de conversão e tirar muito mais proveito da verba investida em anúncios aumentando seu lucro, ROI, faturamento, etc.
+A execução de um teste A/B entre essas duas versões de loja ajuda você a analisar o impacto da transição para o VTEX IO no engajamento do usuário, conversões e desempenho geral.
 
diff --git a/docs/tutorials/pt/access-control.md b/docs/tutorials/pt/access-control.md
new file mode 100644
index 000000000..37d6c30f7
--- /dev/null
+++ b/docs/tutorials/pt/access-control.md
@@ -0,0 +1,62 @@
+---
+title: 'Controle de acesso'
+id: 4rM3gyiWqtkim4Q8hOvLTC
+status: DRAFT
+createdAt: 2023-11-30T16:29:30.077Z
+updatedAt: 2023-11-30T21:42:00.250Z
+publishedAt: 
+firstPublishedAt: 2023-11-30T21:40:59.550Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: controle-de-acesso
+locale: pt
+legacySlug: controle-de-acesso
+subcategory: 1HSqkejwuYcQSMC400uY84
+---
+
+Toda ação na VTEX, como acessar uma página no Admin ou fazer uma chamada de API, envolve uma requisição à nossa infraestrutura. Para garantir a segurança dessas operações, existe o **License Manager**, um sistema responsável por verificar se um usuário possui as permissões adequadas para realizar uma ação na plataforma.
+
+Para facilitar o gerenciamento dessas permissões, o License Manager é baseado em [recursos](#recursos) e [perfis de acesso](#perfis-de-acesso). Confira a seguir mais detalhes sobre esses conceitos.
+
+## Recursos
+
+Um **recurso** é uma entidade associada a uma ação ou informação dentro de nossa infraestrutura. Por exemplo, o recurso _Product management_ permite que um usuário acesse e edite o formulário de cadastro de produtos no Catálogo. Para detalhes sobre cada recurso disponível, veja [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3).
+
+Cada requisição passa por uma análise de segurança para verificar se o usuário possui os recursos necessários, ou seja, a permissão necessária para realizar aquela ação. Sem os recursos necessários, uma requisição não será bem-sucedida.
+
+## Perfis de acesso
+
+Um **perfil de acesso** determina o conjunto de recursos que um grupo de usuários pode acessar na VTEX. Cada usuário administrativo pode ser associado a um ou mais perfis de acesso.
+
+Como diversos colaboradores costumam acessar o Admin, é importante limitar o acesso a ações críticas dentro de uma conta para minimizar disrupções na operação da loja e garantir que cada usuário tenha acesso apenas às ações necessárias para o seu papel.
+
+Por exemplo, uma equipe de operadores de televendas precisa de acesso apenas a informações de pedidos, então não deve ter acesso a outras configurações da plataforma. Nesse caso, o perfil de acesso pode conter somente recursos relacionados à leitura de informações de pedidos.
+
+Para gerenciar os perfis de acesso cadastrados na sua loja e os usuários associados a eles, acesse a [lista de perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
+
+Confira a seguir os diferentes tipos de perfis de acesso que você pode cadastrar na loja.
+
+### Tipos de perfis de acesso
+
+Ao [criar um novo perfil de acesso](https://help.vtex.com/pt/tutorial/criar-perfil-de-acesso--qGtNQpKSSAduX94l2WZBW), você tem a opção de utilizar um dos perfis predefinidos disponibilizados pela VTEX ou de criar um perfil customizado, selecionando cada recurso necessário.
+
+O administrador precisa ter um perfil de acesso com o [recurso](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) _Save access profile_ para criar perfis de acesso no License Manager.
+
+#### Predefinidos
+
+Perfis de acesso predefinidos são conjuntos de recursos pré-determinados pela VTEX que cobrem os casos de uso mais comuns. Confira a lista completa de [perfis predefinidos](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy) e as respectivas permissões associadas.
+
+#### Personalizados
+
+Além de utilizar perfis de acesso predefinidos, você pode [criar perfis de acesso personalizados](https://help.vtex.com/pt/tutorial/criar-perfil-de-acesso--qGtNQpKSSAduX94l2WZBW#criar-perfil-de-acesso-personalizado), reunindo os recursos necessários para um grupo de usuários administrativos da sua loja.
+
+Por exemplo, uma equipe responsável por manter o Catálogo da loja atualizado costuma realizar um conjunto bem definido de tarefas, como cadastrar e editar produtos, categorias e marcas. Nesse caso, um administrador da conta pode criar um perfil de acesso personalizado com todos os recursos necessários para esses colaboradores.
+
+Confira a lista completa de [recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) que podem ser utilizados.
+
+## Saiba mais
+
+* [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc)
+* [Criar perfil de acesso](https://help.vtex.com/pt/tutorial/criar-perfil-de-acesso--qGtNQpKSSAduX94l2WZBW)
+
diff --git a/docs/tutorials/pt/accessing-a-client-abandoned-cart.md b/docs/tutorials/pt/accessing-a-client-abandoned-cart.md
index cd34967e4..a35f7a64e 100644
--- a/docs/tutorials/pt/accessing-a-client-abandoned-cart.md
+++ b/docs/tutorials/pt/accessing-a-client-abandoned-cart.md
@@ -29,26 +29,26 @@ Visualizar esses campos é bem simples. Uma vez logado no Admin da sua loja, bas
 
 1. Clique em __Master Data__
 
-  ![Carrinho Abandonado - 1 - PT](https://images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/deed48c41ae2ab64a4aa53c1b53d1962/4GdZSkwtm9f76BIVFnC65D_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 1 - PT](//images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/deed48c41ae2ab64a4aa53c1b53d1962/4GdZSkwtm9f76BIVFnC65D_Masterdata_PT.jpg)
 
 2. Clique no ícone de Configurações (engrenagem) de __Profile System__
 
-  ![Carrinho Abandonado - 2 - PT](https://images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/e7911e88ba6acba63e50fc8689e25c09/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
+  ![Carrinho Abandonado - 2 - PT](//images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/e7911e88ba6acba63e50fc8689e25c09/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
 
 3. Certifique-se que você está na aba __Aplicações__
 
-  ![Carrinho Abandonado - 3 - PT](https://images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/48cf309c46a6484afaa40896e519e5ee/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
+  ![Carrinho Abandonado - 3 - PT](//images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/48cf309c46a6484afaa40896e519e5ee/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
 
 4. Acesse Editar (Lápis) na categoria __Clientes__ 
 
-  ![Carrinho Abandonado - 4 - PT](https://images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/20e963f2ee94ba72e2124b063b9a7a02/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
+  ![Carrinho Abandonado - 4 - PT](//images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/20e963f2ee94ba72e2124b063b9a7a02/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
 
 5. Selecione as opções __“Último carrinho”__ e __“Carrinho”__ dentre as opções de __Campos de Listagens__
 
-  ![Carrinho Abandonado - 5 - PT](https://images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/fc241bda582d78cd43bda4b7384976ca/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 5 - PT](//images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/fc241bda582d78cd43bda4b7384976ca/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
 
 6. Clique em __Salvar__
 
-  ![Carrinho Abandonado - 6 - PT](https://images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/7bc0ae209e1075586c29571998b23e5a/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
+  ![Carrinho Abandonado - 6 - PT](//images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/7bc0ae209e1075586c29571998b23e5a/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
 
 Assim, você poderá conferir os parâmetros do carrinhos abandonados de seus clientes.
diff --git a/docs/tutorials/pt/accessing-the-beta-environment.md b/docs/tutorials/pt/accessing-the-beta-environment.md
index e857f32a1..5e78fa421 100644
--- a/docs/tutorials/pt/accessing-the-beta-environment.md
+++ b/docs/tutorials/pt/accessing-the-beta-environment.md
@@ -1,10 +1,10 @@
 ---
 title: 'Acessar o ambiente beta pelo domínio myvtex.com'
 id: 3BHM289568gcSwk2O80Asu
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-07-26T18:09:29.968Z
-updatedAt: 2019-12-31T15:26:39.674Z
-publishedAt: 2019-12-31T15:26:39.674Z
+updatedAt: 2024-03-13T12:00:57.622Z
+publishedAt: 2024-03-12T19:18:51.136Z
 firstPublishedAt: 2018-07-26T18:43:10.906Z
 contentType: tutorial
 productTeam: Reliability
@@ -15,26 +15,32 @@ legacySlug: acessar-o-ambiente-beta-pelo-dominio-myvtex-com
 subcategory: Se4oi5LroIII2Ei0uGAoE
 ---
 
-Na VTEX, todas as lojas possuem um ambiente beta. 
+Na VTEX, todas as lojas possuem um ambiente beta. Neste local, o usuário da plataforma (lojista, desenvolvedor ou outra pessoa com acesso) pode realizar testes para validar novas configurações  ou versões de aplicações/serviços antes de promover as mudanças no ambiente em que os clientes realizam as compras, também conhecido como ambiente de produção (stable).
 
-Este ambiente é um local de testes para que o usuário da plataforma possa validar alterações numa loja antes de promover as mudanças para o ambiente principal.
-
-## Como funciona o ambiente beta
+<div class = "alert alert-info">
+O ambiente beta é uma reprodução exata do ambiente de produção (stable), incluindo dados e configurações da loja.
+</div>
 
-O ambiente beta funciona como um ambiente de testes para diferentes versões de aplicações/serviços da VTEX na sua loja. Ele é um ambiente que reproduz todas as informações do ambiente principal (`stable`). Assim, os dados da loja são os mesmos, tanto em beta quanto em stable. Dessa forma, __a alteração de dados no ambiente beta afeta os dados no ambiente stable__.
+Dessa forma, **a alteração de dados no ambiente beta afeta os dados no ambiente stable**.
 
 ## Acessar o ambiente beta
 
-O acesso ao ambiente beta se localiza no final do menu lateral do admin. Basta clicar em `Usar beta` para ter acesso ao ambiente de testes.
-
-![usar-beta-pt-br](https://images.ctfassets.net/alneenqid6w5/6FhvL9s66QsKuYIwsy0Kkm/29dcc61ec07d4322c9ced983bd0c82e2/usar-beta-pt-br.png)
-
-<div class="alert alert-info">
-Para retornar ao ambiente principal, clique em <code>Usar stable</code>, também localizado no final do menu lateral do admin.
+Para acessar o ambiente beta em sua loja, é necessário habilitar o cookie `vtex-commerce-env` da seguinte forma:
+
+<ol start="1">
+  <li>Dentro do Admin VTEX, acesse a tela Dev.Tools em seu navegador pressionando a tecla <code>F12</code> ou clicando com o botão direito, e escolhendo a opção <b>Inspecionar</b>.</li>
+  <li>Na barra superior da tela, acesse a aba <b>Aplicativo</b>, e na barra lateral esquerda em Cookies, clique na URL de sua loja.
+</li>
+  <li>Na tabela, insira as informações abaixo na células da última linha:</li>
+  <ul>
+<li>Nome: <code>vtex-commerce-env</code></li>
+<li>Valor: <code>beta</code>
+</li>
+</ul>
+<img src="https://images.ctfassets.net/alneenqid6w5/3g8wintA1heJbzdV8J0s45/8eb6f5917e2d9d8a134b81231dc42728/Ambiente_beta_.png" alt="beta">
+<li>Atualize a página pressionando a tecla <code>F5</code> ou o botão de atualizar do seu navegador. Após o carregamento da página, o Admin da loja já estará em ambiente Beta.</li>
+</ol>
+
+<div class = "alert alert-info">
+Para voltar à loja em seu ambiente principal, acesse novamente a tela Dev. Tools do seu navegador e remova o cookie <code>vtex-commerce-env</code> inserido. Atualize novamente a página para retornar ao ambiente de produção <b>stable</b>.
 </div>
-
-## Verificar mudanças no ambiente beta
- 
-Para acessar sua loja em modo beta e verificar como as mudanças feitas afetaram o front da sua loja, basta clicar no botão `VISITE A LOJA` depois de ter realizado o acesso ao ambiente beta descrito no passo acima.
-
-![visite-a-loja-beta-pt](https://images.ctfassets.net/alneenqid6w5/1ROmY3DdHSkSoeoMYwMkg2/7ca0f31551fa9b45a14b784ed84503eb/visite-a-loja-beta-pt.png) 
diff --git a/docs/tutorials/pt/account-management.md b/docs/tutorials/pt/account-management.md
index f6c14d009..b02d942f7 100644
--- a/docs/tutorials/pt/account-management.md
+++ b/docs/tutorials/pt/account-management.md
@@ -84,84 +84,10 @@ Depois que um usuário preenche e salva **Nome** e **E-mail**, nos campos de co
 O template deste e-mail automático pode ser alterado na <a href="https://help.vtex.com/pt/tutorial/understanding-the-message-center--tutorials_84">Central de mensagens</a> modificando o template <i>account registration</i>.
 </div>
 
-![cadastro de conta](https://images.ctfassets.net/alneenqid6w5/5tBCNxqBxeWkqOgiIcEaQw/4e044e1f46911db85da4e5ea0a195226/cadastro_de_conta.jpg)
+![cadastro de conta](//images.ctfassets.net/alneenqid6w5/5tBCNxqBxeWkqOgiIcEaQw/4e044e1f46911db85da4e5ea0a195226/cadastro_de_conta.jpg)
 
 ## Segurança
 
 Nessa área são criados os [appKeys e appTokens](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao) usados para autenticar integrações com a sua loja.
 
 Apenas o usuário Titular tem permissão para criar appKeys e appTokens, uma vez que estes dão acesso à sua loja por API, o que pode ser crítico se não utilizado por profissionais habilitados.
- lojas](#lojas).
-- [Adicionar nova loja](#criar-loja).
-- [Editar loja](#editar-loja).
-- [Excluir loja](#excluir-loja).
-
-Ao clicar na aba **Lojas**, na parte superior da tela, você verá uma lista com as informações de todas as lojas criadas na sua conta VTEX. 
-
-![Página de detalhes da conta - Lojas](https://images.ctfassets.net/alneenqid6w5/rAFyEsEDLBDqj3UBGufrb/70dea056a37a7cffd997803160605978/2pt.png)
-
-Para cada loja, você pode visualizar os seguintes detalhes:
-
-- **Nome da loja:** identificador interno da loja.
-- **Nome comercial:** nome utilizado comercialmente.
-- **Hosts:** domínios associados à loja.
-
-Você pode usar a caixa de busca para filtrar as lojas exibidas na lista por qualquer um dos atributos.
-
-Além disso, você poderá [criar uma nova loja](#criar-loja), [editar uma loja](#editar-loja) ou [excluir](#excluir-loja) lojas existentes.
-
-### Criar loja
-
-Para criar uma nova loja, siga os passos:
-
-1. Acesse a página de **Conta**, clicando no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Conta**.
-2. Clique na aba **Loja** na parte superior da tela.
-3. Clique no botão `+ Nova loja`.
-4. Preencha as informações básicas da loja:
-    - **Nome da loja:**  identificador interno da loja.
-    - **Nome comercial:** nome utilizado comercialmente.
-    - **Localidade:** idioma predefinido associado a esta loja.
-    - **Canal de vendas:** [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#) que deseja associar à nova loja.
-5. Se deseja iniciar o processo de [go-live](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM) da sua loja, preencha o campo **Hosts** com o domínio da sua loja. Caso contrário, deixe este campo em branco.
-6. Clique no botão `Criar`.
-
-<div class = "alert alert-info">
-  Para saber mais sobre a configuração de <b>Hosts</b> da sua loja, confira o artigo  <a href="https://help.vtex.com/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450">Configurando o domínio da sua loja</a>.
-</div>
-
-<div class="alert alert-warning">
-Não utilize um domínio do tipo ".com" no campo Nome da Loja. Esse tipo de entrada só pode existir nos campos Hosts.
-</div>
-
-### Editar loja
-
-Você pode editar informações de uma loja existente com estes passos:
-
-1. Acesse a página de **Conta**, clicando no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Conta**.
-2. Clique na aba **Loja** na parte superior da tela.
-3. Clique no botão de ações <i class="fas fa-ellipsis-v"></i> correspondente à loja que deseja editar.
-4. Clique em `Editar`.
-5. Você verá a página de edição de conta. Edite as informações que deseja.
-6. Clique em `Salvar`.
-
-### Excluir loja
-
-Para excluir uma loja, siga estes passos:
-
-1. Acesse a página de **Conta**, clicando no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Conta**.
-2. Clique na aba **Loja** na parte superior da tela.
-3. Clique no botão de ações <i class="fas fa-ellipsis-v"></i> correspondente à loja que deseja excluir.
-4. Clique em `Excluir`.
-5. Você verá um modal de confirmação. Clique em `Excluir`.
-
-<div class="alert alert-warning">
-Note que a loja principal, sinalizada com uma estrela ao lado do nome na lista de lojas, não pode ser excluída.
-</div>
-
-Saiba mais:
-- [O que é nome de conta?](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)
-- [Usuário titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy)
-- [Transferir a propriedade da loja](https://help.vtex.com/pt/tutorial/transferencia-de-propriedade-da-loja)
-- [Configurando o domínio da sua loja](https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450)
-- [Go-live](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM)
-
diff --git a/docs/tutorials/pt/account-settings-overview.md b/docs/tutorials/pt/account-settings-overview.md
index 06f21d5e8..eb61ff971 100644
--- a/docs/tutorials/pt/account-settings-overview.md
+++ b/docs/tutorials/pt/account-settings-overview.md
@@ -20,7 +20,7 @@ Todo contratante da VTEX recebe uma conta que dá acesso ao Admin, onde é poss
 Nas **Configurações da conta,** é possível controlar  o acesso ao Admin e alterar outras configurações relacionadas à conta, como editar informações de contato e vincular lojas à sua conta.
 
 Para acessar as _Configurações da conta_, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e clique no botão **Configurações da conta**.  
-![Admin v4 account settings menu PT](https://images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/09a38ba629307a07ac8a37bb79d8c812/Admin_v4_account_settings_menu_PT.jpg)
+![Admin v4 account settings menu PT](//images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/09a38ba629307a07ac8a37bb79d8c812/Admin_v4_account_settings_menu_PT.jpg)
 
 A seção inclui as seguintes páginas, em breve no design do Admin v4.
 
diff --git a/docs/tutorials/pt/account-summary.md b/docs/tutorials/pt/account-summary.md
index 39ced09d2..e8f805c92 100644
--- a/docs/tutorials/pt/account-summary.md
+++ b/docs/tutorials/pt/account-summary.md
@@ -36,23 +36,23 @@ Por fim, o lojista pode conferir os próximos recebíveis e suas últimas movime
 
 Esta seção é dividida em duas partes: a de recebíveis consolidados - para recebimentos já liquidados - e a de lançamentos futuros, para compras que ainda serão liquidadas. 
 
-![extrato_financeiro_vtex_payment](https://images.ctfassets.net/alneenqid6w5/ylj1J2TQfTs24IyrxKJrI/884f3d2ad018b1d2888465818565a2f8/image.png)
+![extrato_financeiro_vtex_payment](//images.ctfassets.net/alneenqid6w5/ylj1J2TQfTs24IyrxKJrI/884f3d2ad018b1d2888465818565a2f8/image.png)
 
 Vale ressaltar que a aba Lançamentos Futuros oferece a conciliação entre os recebíveis e seus respectivos pedidos. Caso o lojista clique em um dos recebimentos, uma tela contendo todas as transações referentes àquela movimentação financeira será exibida. 
 
-![tela_extrato-financeiro](https://images.ctfassets.net/alneenqid6w5/5vpMPvl2dz4fT8OvgjYrAC/a9a8e07e94b40dffd714c3b317d35111/image.png)
+![tela_extrato-financeiro](//images.ctfassets.net/alneenqid6w5/5vpMPvl2dz4fT8OvgjYrAC/a9a8e07e94b40dffd714c3b317d35111/image.png)
 
 Além disso, para consultar os detalhes do pedido que compõe a transação, basta clicar na linha correspondente. Assim, a tela apresentará dados como: produto vendido, data e número de parcelas, por exemplo.
 
-![tela_extrato_financeiro](https://images.ctfassets.net/alneenqid6w5/3OjfgHkS4kMDX7zEhoaHMF/27d2fabc1014e9371475b8aea1c0f2ba/image.png)
+![tela_extrato_financeiro](//images.ctfassets.net/alneenqid6w5/3OjfgHkS4kMDX7zEhoaHMF/27d2fabc1014e9371475b8aea1c0f2ba/image.png)
 
 O lojista pode ainda consultar o pedido diretamente no módulo Gerenciamento de Pedidos, caso clique em "Ver detalhes do pedido".
 
-![items_pedido](https://images.ctfassets.net/alneenqid6w5/1IiebFvYL9GfppgW77E6op/0df3ba415c65662c08d6ff329970555b/image.png)
+![items_pedido](//images.ctfassets.net/alneenqid6w5/1IiebFvYL9GfppgW77E6op/0df3ba415c65662c08d6ff329970555b/image.png)
 
 Por fim, ainda nessa tela, o lojista pode baixar dois relatórios: extrato financeiro e recebimentos de vendas. Para isso, basta clicar no botão "Exportar", selecionar o documento e o mês desejado.
 
-![image](https://images.ctfassets.net/alneenqid6w5/I8zH7rdrRmiDoFYzSEgMh/5bcc566709369dc12904e7e95c31a725/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/I8zH7rdrRmiDoFYzSEgMh/5bcc566709369dc12904e7e95c31a725/image.png)
 
 Os dados são:
 
@@ -65,13 +65,13 @@ Por mais que em “Resumo de Contas” a plataforma apresente uma pequena sínte
 
 Ao clicar nessa seção, o lojista pode conferir suas disputas em aberto. Contudo, ao clicar em uma transação específica, a plataforma o direciona para uma página que mostra o extrato do pedido.
 
-![tela_disputas](https://images.ctfassets.net/alneenqid6w5/1SdbVyFFMPrsn5IvCeGK7T/aa82183f3bfadbd9aa5a450cf903512c/image.png)
+![tela_disputas](//images.ctfassets.net/alneenqid6w5/1SdbVyFFMPrsn5IvCeGK7T/aa82183f3bfadbd9aa5a450cf903512c/image.png)
 
 São quatro quadros que detalham o recebível em disputa. Em “Transação”, o lojista confere os dados da compra. Assim como acessa a descrição do pedido em si no quadro logo abaixo, “Itens do Pedido”.
 
 Do lado esquerdo, temos os quadros “Recebíveis”, que apresentam os detalhes das parcelas daquela transação, e “Valor Total”. Este último detalha o histórico, assim como a soma de todos os recebíveis que compõem o pedido.
 
-![disputa_extrato](https://images.ctfassets.net/alneenqid6w5/7x3zwBsaDR6VEItmoSzWhy/21b909bf626e7a1e17c97d32957cf86f/image.png)
+![disputa_extrato](//images.ctfassets.net/alneenqid6w5/7x3zwBsaDR6VEItmoSzWhy/21b909bf626e7a1e17c97d32957cf86f/image.png)
 
 ## Antecipação avulsa de recebíveis
 
diff --git a/docs/tutorials/pt/accounts-payable-brazil.md b/docs/tutorials/pt/accounts-payable-brazil.md
index 0aa36050d..469a11598 100644
--- a/docs/tutorials/pt/accounts-payable-brazil.md
+++ b/docs/tutorials/pt/accounts-payable-brazil.md
@@ -3,8 +3,8 @@ title: 'Contas a Pagar - Brasil'
 id: tutorials_660
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:25.003Z
-updatedAt: 2023-01-24T21:41:37.901Z
-publishedAt: 2023-01-24T21:41:37.901Z
+updatedAt: 2024-02-23T15:08:20.685Z
+publishedAt: 2024-02-23T15:08:20.685Z
 firstPublishedAt: 2017-04-27T23:03:40.609Z
 contentType: tutorial
 productTeam: Billing
diff --git a/docs/tutorials/pt/activating-new-vtex-cdn.md b/docs/tutorials/pt/activating-new-vtex-cdn.md
index 80627df52..bf9f93383 100644
--- a/docs/tutorials/pt/activating-new-vtex-cdn.md
+++ b/docs/tutorials/pt/activating-new-vtex-cdn.md
@@ -1,10 +1,10 @@
 ---
 title: 'Ativar nova CDN da VTEX'
 id: 400JfRm4VGgsKgqgOw4WWA
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-10-02T23:12:05.096Z
-updatedAt: 2019-12-31T15:25:39.216Z
-publishedAt: 2019-12-31T15:25:39.216Z
+updatedAt: 2023-08-09T20:43:20.267Z
+publishedAt: 
 firstPublishedAt: 2017-10-03T02:09:58.361Z
 contentType: tutorial
 productTeam: Reliability
diff --git a/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md b/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md
index 3eadd730b..5dea36bbe 100644
--- a/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md
+++ b/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md
@@ -20,7 +20,7 @@ O link de **Lista Completa** no menu de categorias é muito usado em lojas que
 
 Como, por exemplo, no caso abaixo, o "Departamento 2" :
 
-![categoria.pt](https://images.ctfassets.net/alneenqid6w5/Z4sxAcNhnYK8zHQ46Viti/809614206fc51a87a108432c546ce5a3/categoria.pt.png)
+![categoria.pt](//images.ctfassets.net/alneenqid6w5/Z4sxAcNhnYK8zHQ46Viti/809614206fc51a87a108432c546ce5a3/categoria.pt.png)
 
 De todas as categorias, a loja preferiu exibir no menu somente algumas.
 
@@ -29,5 +29,5 @@ Esta configuração é feita no cadastro de categoria, na opção **Menu com lin
 - Se tiver marcada, a categoria aparece no menu.
 - Se não tiver marcada, a categoria não aparece e é mostrado opção  Lista Completa no site.
 
-![categoria2.pt](https://images.ctfassets.net/alneenqid6w5/3zMivOdJB2tn6E8qE7I43M/9a9f35f14c56b8082723a63c7ba2f7bd/categoria2.pt.png)
+![categoria2.pt](//images.ctfassets.net/alneenqid6w5/3zMivOdJB2tn6E8qE7I43M/9a9f35f14c56b8082723a63c7ba2f7bd/categoria2.pt.png)
 
diff --git a/docs/tutorials/pt/active-campaign-suiteshare.md b/docs/tutorials/pt/active-campaign-suiteshare.md
index 33238333a..9310eebc3 100644
--- a/docs/tutorials/pt/active-campaign-suiteshare.md
+++ b/docs/tutorials/pt/active-campaign-suiteshare.md
@@ -21,23 +21,23 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Active Campaign**.
 
-   ![CRM Zen_1](https://images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
+   ![CRM Zen_1](//images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
 
 2. Acesse **Configurações > Integrações > Active Campaign > Integrar**.
 
-![Active Campaign_1](https://images.ctfassets.net/alneenqid6w5/2O2PvYfjd1TnhPH4vqvmSB/3f102059931a13e25ff64b32c339e0dc/Active_Campaign_1.png)
+![Active Campaign_1](//images.ctfassets.net/alneenqid6w5/2O2PvYfjd1TnhPH4vqvmSB/3f102059931a13e25ff64b32c339e0dc/Active_Campaign_1.png)
 
 Selecione o [Formulário de captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseja conectar.
 
-![Active Campaign_2](https://images.ctfassets.net/alneenqid6w5/1yOIZh4WgIcRbSqPcN4VZd/4e01f427e104b683be8e69f395db7d55/Active_Campaign_2.png)
+![Active Campaign_2](//images.ctfassets.net/alneenqid6w5/1yOIZh4WgIcRbSqPcN4VZd/4e01f427e104b683be8e69f395db7d55/Active_Campaign_2.png)
 
 Dentro do painel admin da Active Campaing, acesse **Configurações > Desenvolvedor**. 
 
-![Active Campaign_3](https://images.ctfassets.net/alneenqid6w5/1deHM7z9nXPAUfXBqHCeyV/3d0359ed82be742cca273d7c9365aa80/Active_Campaign_3.png)
+![Active Campaign_3](//images.ctfassets.net/alneenqid6w5/1deHM7z9nXPAUfXBqHCeyV/3d0359ed82be742cca273d7c9365aa80/Active_Campaign_3.png)
 
 Copie a URL e a chave dentro da VTEX Assisted Sales (SuiteShare). 
 
-![Active Campaign_4](https://images.ctfassets.net/alneenqid6w5/1ViCB3Aj2mQZ9KS1ofuUgk/b4d8237d53c86d75cc9a2e61f298b4ed/Active_Campaign_4.png)
+![Active Campaign_4](//images.ctfassets.net/alneenqid6w5/1ViCB3Aj2mQZ9KS1ofuUgk/b4d8237d53c86d75cc9a2e61f298b4ed/Active_Campaign_4.png)
 
 Clique em **Salvar**.
 
diff --git a/docs/tutorials/pt/adapting-your-integration-for-change-order-beta.md b/docs/tutorials/pt/adapting-your-integration-for-change-order-beta.md
new file mode 100644
index 000000000..fa558669f
--- /dev/null
+++ b/docs/tutorials/pt/adapting-your-integration-for-change-order-beta.md
@@ -0,0 +1,304 @@
+---
+title: 'Adaptando sua integração para a Alterar pedido (Beta)'
+id: 6kGQWs0IvpwIZoyeoLMjlp
+status: PUBLISHED
+createdAt: 2024-06-03T18:54:30.094Z
+updatedAt: 2024-07-09T17:18:19.900Z
+publishedAt: 2024-07-09T17:18:19.900Z
+firstPublishedAt: 2024-06-03T20:02:10.248Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: adaptando-sua-integracao-para-a-alterar-pedido-beta
+locale: pt
+legacySlug: adaptando-sua-integracao-para-a-alterar-pedido-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+Para evoluir a plataforma VTEX com relação a mudanças em pedidos, estamos lançando a [Alterar pedido (Beta)](https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ), uma solução muito mais completa, versátil e que proporciona uma [nova experiência no Admin VTEX](https://help.vtex.com/pt/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw).
+
+Após as interações entre nosso time de engenharia e clientes e parceiros que já aderiram à versão beta, elaboramos este conteúdo com boas práticas de implementação e dúvidas frequentes. O objetivo é que os próximos clientes e parceiros disponham deste material de apoio ao começarem a usar a **Alterar pedido (Beta)**.
+
+Este artigo está organizado da seguinte forma:
+
+* [Adaptação para diferentes casos de uso](#adaptacao-para-diferentes-casos-de-uso)
+* [Alterações no request body das requisições](#alteracoes-no-request-body-das-requisicoes)
+* [Requisições com erros e falhas](#requisicoes-com-erros-e-falhas)
+* [Perguntas frequentes (FAQ)](#perguntas-frequentes-faq)
+
+## Adaptação para diferentes casos de uso
+
+As seções a seguir apresentam os principais casos de uso da **Alterar pedido (Beta)** e respectivas recomendações.
+
+### Comunicação com cliente via email transacional
+
+A **Alterar pedido (Beta)** utiliza novos templates para [emails transacionais](https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my) (Message Center), de forma a contemplar as funcionalidades inovadoras da solução. 
+
+Para customizar um template de email no Admin VTEX, copie e cole o link abaixo no seu navegador, substituindo o `{accountName}` pelo [nome de conta](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) da sua loja, e depois clique em `enter`:
+
+`https://{accountName}.myvtex.com/admin/message-center/#/templates/vtexcommerce-order-changed-v2`
+
+### Gerenciamento da alteração do pedido via Admin VTEX
+
+Para as lojas que utilizam a versão atual para alterar pedidos via Admin VTEX, após a instalação da nova solução pela equipe da VTEX, as interfaces atualizadas estarão imediatamente disponíveis para você usar a **Alterar pedido (Beta)** via Admin VTEX. Isso inclui novo gerenciamento e comunicação do [Minha conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#pedidos) e de [templates de emails transacionais](https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my).
+
+### Gerenciamento da alteração do pedido via API
+
+Para as lojas que utilizam nossas APIs, é necessário que a implementação na integração obedeça à nova arquitetura da funcionalidade. 
+
+Na **Alterar pedido (Beta)**, o endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) funciona de forma assíncrona e o [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) ou integração que faz a requisição recebe da plataforma um `requestId`, que é um identificador único para acompanhar a operação para alterar o pedido. Este identificador posteriormente será utilizado em determinados endpoints. Todos os endpoints da **Alterar pedido (Beta)** são:
+
+* [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes)
+* [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview)
+* [Get order change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-)
+* [Get order change history](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes)
+* [Retry order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry)
+* [Cancel order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel)
+
+Após alterar o pedido usando o endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), para novas requisições aos endpoints da **Alterar pedido (Beta)** existem as seguintes alternativas para o integrador:
+
+* **Polling:** complexidade baixa.
+* **Preview:** complexidade média.
+
+A tabela a seguir apresenta cada uma:
+
+| **Tipo de fluxo** | **Funcionamento** |
+| :---: | :--- |
+| **Polling**<p>Complexidade baixa</p> | <p>Após a operação de alteração do pedido é gerado um código único que identifica a alteração do pedido, o `requestId`, e com ele você pode acompanhar os detalhes da requisição pelo endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change details</a>. Neste endpoint, após a alteração do pedido, a propriedade do response body `finished` passa a ter o valor `true`.</p><p>Além disso, o <a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change details</a> também pode ser utilizado para obter informações sobre falhas e erros que resultaram no eventual cancelamento da operação de alteração do pedido, como será visto na seção <a href="#requisicoes-com-erros-e-falhas">Requisições com erros e falhas</a>.</p> |
+| **Preview** <p>Complexidade média</p> | <p>Antes de fazer uma requisição ao <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a>, a integração tem a opção de fazer uma visualização prévia que vai resultar em um response body exatamente igual à requisição de alteração. Para isso, basta usar o mesmo request body no requisição ao endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a>.</p><p>Essa pré-visualização é uma simulação da alteração e não gera efeitos reais de alteração no pedido. O uso do <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a> é útil para você obter os valores totais associados à alteração do pedido sendo feita, e também para validar os detalhes da requisição com um request body válido.</p><p>Após uma resposta de sucesso `200 OK` para obter uma visualização prévia da alteração, a integração pode prosseguir com a requisição a <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> para alterar o pedido.</p><p>Posteriormente, sua integração pode ser adaptada a cenários como:<ul><li><b>Criação otimista:</b> os dados das validações obtidas com a simulação da alteração cobrem a maior parte dos cenários de sucesso `200 OK`.</li><li><b>Implementação do Polling:</b> mencionado anteriormente.</li></ul></p> |
+
+## Alterações no request body das requisições
+
+A **Alterar pedido (Beta)** mantém alguns atributos da solução anterior, mas há outros que foram criados ou transformados, tanto em nomenclatura quanto em funcionamento. As principais mudanças foram organizadas da seguinte forma:
+
+* [Valores manuais](#valores-manuais)
+* [Adição e remoção de itens](#adicao-e-remocao-de-itens)
+* [Atributos de itens obrigatórios e opcionais](#atributos-de-itens-obrigatorios-e-opcionais)
+* [Responsabilidade do usuário na automatização do sistema](#responsabilidade-do-usuario-na-automatizacao-do-sistema)
+
+### Valores manuais
+
+* **Antes:** os campos `discountValue` e `incrementValue` definiam o valor da alteração sendo feita no pedido, respectivamente para o decréscimo ou o acréscimo de um valor. O usuário calculava o valor da alteração e o resultado era acrescido ou decrescido no valor total do pedido por meio destes campos.
+  > **Exemplo:** em um pedido de 100 reais a ser alterado para se adicionar um item de 50 reais, o usuário enviava o `incrementValue` com valor de 50 reais e o sistema calculava o total do pedido como 150 reais. Se o usuário quisesse dar ao cliente um desconto de 30 reais na alteração, ele precisava enviar o `discountValue` com valor de 30 reais para que o total do pedido fosse 120 reais.
+* **Agora:** os novos campos `manualDiscountValue` e `manualIncrementValue` definem valores manuais adicionais sendo acrescidos ou decrescidos do custo total do pedido independentemente das alterações sendo feitas. Como o sistema calcula de forma automática o resultado das alterações (considerando o preço e condições do fechamento da compra), o usuário pode realizar o acréscimo ou decréscimo de valores usando os campos mencionados.
+  > **Exemplo:** em um pedido de 100 reais a ser alterado para se adicionar um item de 50 reais, ao se adicionar o item, o sistema calcula automaticamente o acréscimo do valor de 50 reais e o usuário não precisa enviá-lo manualmente, sendo o resultado total do pedido igual a 150 reais. Caso o usuário queira dar ao cliente um desconto de 30 reais na alteração, basta enviar o campo `manualDiscountValue` com valor de 30 reais que o total do pedido será 120 reais.
+
+### Adição e remoção de itens
+
+* **Antes:** os atributos utilizados para adicionar e remover itens do pedido eram os arrays `itemsAdded` e `itemsRemoved` e eles continham objetos de itens com os campos `id`, `price` e `quantity`.  
+* **Agora:** os atributos para adicionar e remover itens do pedido são os objetos `add` e `remove` e eles contém um novo nível que define um objeto para cada item por meio do array `items`.
+
+Exemplo de remoção de itens na **Alterar pedido (Beta)**:
+
+```
+{
+    "remove": {
+        "items": [
+            {
+                "id": "1",
+                "quantity": 1
+            }
+        ]
+    }
+}
+```
+
+<br>
+
+### Atributos de itens obrigatórios e opcionais
+
+Os itens no request body das requisições precisam de menos atributos obrigatórios do que antes, são eles: `id` e `quantity`. Os demais atributos são obtidos a partir do pedido ou do sistema Catálogo.
+
+Há outros campos que podem ser modificados para sobrepor as informações de um item sendo alterado, caso seja necessário adicionar ou alterar itens existentes. Os campos opcionais são `price`, `unitMultiplier` e `measurementUnit`. Quaisquer outros campos enviados na requisição são desconsiderados pelo sistema.
+
+### Responsabilidade do usuário na automatização do sistema
+
+* **Antes:** era responsabilidade do usuário calcular o valor a ser alterado no pedido. Ele enviava esse valor pelo atributo `discountValue` ou `incrementValue`, dependendo se era um acréscimo ou decréscimo no preço.
+* **Agora:** o sistema é responsável pelo fornecimento de informações sobre os itens e calcula, de forma automática, o valor final do pedido com a alteração. Ou seja, o usuário agora informa o mínimo necessário e não mais calcula o valor final do pedido, o que diminui cenários de erros.
+
+## Requisições com erros e falhas
+
+Quando ocorre erro ou falha na requisição da **Alterar pedido (Beta)**, as informações sobre o processamento podem ser obtidas pelo endpoint [Get order change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-) pelo atributo `logs`. 
+
+Exemplo de `logs` com erro de processamento:
+
+```
+{
+    "requestId": "de88ad2b-a927-47ad-b5af-a6fab4d2a22f",
+    "workflowId": "418827ee-0efd-4127-87c0-6d881358b750",
+    "status": "preparing",
+    "finished": false,
+    "reason": "test",
+    "manualDiscountValue": 1000,
+    "manualIncrementValue": 0,
+    "totalChangeValue": 0,
+    "totals": [],
+    "add": {
+        ...
+    },
+    "logs": [
+       {
+            "date": "2024-05-13T21:35:00.1952066Z",
+            "message": "Automatic transition failed. Current retry counter is 1. Failed with message: Failure to run the action 'preparing'. Content: '{\"error\":{\"code\":\"001\",\"message\":\"An error has occurred\"},\"operationId\":\"f69e8934-5f93-4ba2-9ebe-408080c6733b\",\"fields\":{}}'",
+            "source": "Workflow Engine",
+            "status": "preparing"
+        },
+        {
+            "date": "2024-05-13T21:35:00.1481754Z",
+            "message": "OperationId:f69e8934-5f93-4ba2-9ebe-408080c6733b\nSystem.NullReferenceException: Object reference not set to an instance of an object.\n   at VTEX.SOS.Services.OrderService.OrderServiceCapabilities.ChangeOrderV2.ChangeOrderMerger.MergeWithEnrichedItemMetadata(Seller seller, OrderItem itemToEnrich, OrderItem enrichedItem)\n   at VTEX.SOS.Services.OrderService.OrderService.FillAddedItemMetadataAsync(IContext context, IEnumerable`1 enrichedOrderItems, Seller seller, OrderItem addedItem, String salesChannel, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 284\n   at VTEX.SOS.Services.OrderService.OrderService.FillAddedItemInfoAsync(IContext context, OrderSource orderOrigin, IEnumerable`1 enrichedOrderItems, Seller seller, OrderItem addedItem, String salesChannel, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 273\n   at VTEX.SOS.Services.OrderService.OrderService.EnrichItemsOnlyAsync(IContext context, Order order, ChangeOrderInput changeOrderInput, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 238\n   at VTEX.SOS.Services.OrderService.OrderService.PrepareChangeOrderAsync(IContext context, Order order, ChangeOrderInput changeOrderInput, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Steps/ChangeOrderV2.Prepare.cs:line 38\n   at VTEX.SOS.Services.OrderService.ChangeOrderService.PrepareChangeInternalAsync(String orderId, String changeRequestId, IContext context, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Service/ChangeOrderService.cs:line 288\n   at VTEX.SOS.Services.OrderService.ChangeOrderService.PrepareChangeInternalAsync(String orderId, String changeRequestId, IContext context, CancellationToken cancellationToken) in /app/VTEX.SOS/Services/OrderService/OrderServiceCapabilities/ChangeOrderV2/Service/ChangeOrderService.cs:line 288",
+            "source": "ChangeOrderService:PrepareChangeInternalAsync",
+            "status": "preparing"
+        }
+    ]
+}
+```
+
+<br>
+
+Para cada falha no sistema (erros não tratados), o sistema realiza de forma automática novas tentativas de processamento. Se as novas tentativas não funcionarem, a requisição de alteração será cancelada e o motivo do erro pode ser encontrado usando a  [Get order change details](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-) pelo atributo `cancellationData`.
+
+Caso a origem do erro seja por inobservância do usuário às regras de validação da requisição, a operação será cancelada automaticamente e não serão feitas novas tentativas de processamento. Neste caso, o motivo do erro é também comunicado pelo `cancellationData`. 
+
+Exemplo do objeto `cancellationData`: _a mudança de preço solicitada na requisição ultrapassa o valor limite configurado para cancelamento de pedidos._
+
+```
+{
+    "requestId": "29004325-e2b8-4b7e-a82c-f588e6d3c07f",
+    "workflowId": "ea392ae2-1db5-432c-97d3-adc4436ca4aa",
+    "status": "canceled",
+    "finished": false,
+    "reason": "test",
+    "manualDiscountValue": 37500,
+    "manualIncrementValue": 0,
+    "totalChangeValue": 0,
+    "totals": [],
+    "remove": {
+        ...
+    },
+    "cancellationData": {
+        "requestedByUser": false,
+        "reason": "The value of the change exceed the order's price",
+        "cancellationDate": "2024-05-13T21:31:38.8596Z"
+    }
+}
+```
+
+<br>
+
+## Perguntas frequentes (FAQ)
+
+Esta seção reúne dúvidas comuns de clientes e parceiros que utilizam a **Alterar pedido (Beta)**:
+
+[1 - Como sobrescrevo o preço de um item específico?](#1-como-sobrescrevo-o-preco-de-um-item)
+
+[2 - Como descubro e mudo o valor total do pedido antes que ele seja alterado?](#2-como-descubro-e-mudo-o-valor-total-do-pedido-antes-que-ele-seja-alterado)
+
+[3 - Preciso informar o preço do frete ou ele é recalculado automaticamente?](#3-preciso-informar-o-preco-do-frete-ou-ele-e-recalculado-automaticamente)
+
+[4 - Como funcionam as promoções na Alterar pedidos (Beta)?](#4-como-funcionam-as-promocoes-na-alterar-pedidos-beta)
+
+[5 - O que devo fazer quando a requisição resulta no status canceling ou canceled?](#5-o-que-devo-fazer-quando-a-requisicao-resulta-no-status-canceling-ou-canceled)
+
+### 1 - Como sobrescrevo o preço de um item?
+
+Para sobrescrever o preço de um item específico, é possível aplicar um valor manual ao item ao mesmo tempo em que sua quantidade é alterada.
+
+No endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), o atributo `price` tem a mesma função do fluxo de fechamento de pedidos e se refere ao preço nominal do item. Por exemplo, em um pedido com um item pesável, como uma maçã, o `price` é referente ao preço do quilo da maçã.
+
+Exemplo de sobrescrita de preço em um item pesável:
+
+```
+{
+    "reason": "the client wanted to change",
+    "add": {
+        "items": [
+            {
+                "id": "1",
+                "quantity": 1,
+                "price": 150,
+            }
+        ]
+}
+```
+
+<br>
+
+### 2 - Como descubro e mudo o valor total do pedido antes que ele seja alterado? 
+
+O endpoint [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) permite ao usuário simular qual será o resultado da alteração do pedido a ser feita com o [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), pois utiliza o mesmo request body e fornece o mesmo response body, mas sem alterar o pedido. O `totalChangeValue` é o atributo que informa qual o valor total sendo alterado no pedido, seja para um valor maior (ex: taxa ou adição de itens) ou menor (ex: redução manual do valor ou remoção de itens).
+
+Se for desejável que a integração manipule a variação no valor do pedido alterado, é possível utilizar o mesmo request body utilizado na [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview) e utilizá-lo em uma requisição ao [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), manipulando para mais ou para menos, respectivamente, o valor dos campos `manualIncrementValue` e `manualDiscountValue`.
+
+### 3 - Preciso informar o preço do frete ou ele é recalculado automaticamente?
+
+Quando há mudanças na quantidade, tamanho ou peso de itens, o custo do frete é recalculado automaticamente e o valor é somado ao novo valor total do pedido. 
+
+A regra de cálculo do novo custo do frete obedece às mesmas condições aplicadas no fechamento do pedido.
+
+### 4 - Como funcionam as promoções na Alterar pedidos (Beta)?
+
+A alteração do pedido aplica de forma automática as mesmas promoções e taxas que eram válidas para os itens no fechamento da compra, mas somente replicando as condições de então. Novas promoções e taxas não são recalculadas nas condições do pedido alterado.
+
+> **Exemplo:** em uma loja havia uma promoção "leve 3 itens e pague 2", mas o cliente comprou somente 2 itens e não foi elegível para o desconto. Quando o cliente solicitou que ao seu pedido fosse adicionado mais um item, ele passou a adquirir 3 itens, mas a promoção não seria aplicada, pois não constava no pedido original.
+
+É possível informar a promoção de um item no momento da alteração do pedido. Isso é feito manualmente com a [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) pelo atributo `priceTags`. Este já é o comportamento padrão da plataforma. 
+
+Exemplo de item com promoções aplicadas no pedido original:
+
+```
+{
+    "reason": "teste",
+    "replace": [
+        {
+            "from": {
+                "items": [
+                    {
+                        "id": "16",
+                        "quantity": 1,
+                        "measurementUnit": "kg",
+                        "unitMultiplier": 0.5
+                    }
+                ]
+            },
+            "to": {
+                "items": [
+                    {
+                        "id": "16",
+                        "quantity": 1,
+                        "measurementUnit": "kg",
+                        "unitMultiplier": 0.750,
+                        "price": 530,
+                        "priceTags": [
+                            {
+                                "name": "DISCOUNT@MANUALPRICE",
+                                "value": -50,
+                                "isPercentual": false
+                            }
+                        ]
+                    }
+                ]
+            }
+        }
+    ]
+}
+```
+<br>
+
+Neste exemplo, a tag utilizada foi de desconto manual `DISCOUNT@MANUALPRICE`. A equivalente para taxas manuais seria a `TAX@MANUALPRICE`. O endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) também permite utilizar o atributo `priceTag` de uma promoção existente e mudar seu valor na alteração do pedido.
+
+### 5 - O que devo fazer quando a requisição resulta no status canceling ou canceled?
+
+Os status `canceling` e `canceled` significam que a alteração do pedido não foi processada corretamente, as mudanças não foram aplicadas ao pedido e o usuário pode desconsiderar a tentativa. As falhas e erros podem ocorrer por:
+
+* Inobservância do usuário às regras de validação da requisição.
+* Número excedido de tentativas de reprocessamento automático pelo sistema.
+* Outras falhas de processamento do sistema.
+
+A recomendação geral é investigar a origem do erro e checar o request body sendo enviado pelo endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) ou [Preview order change](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview). Mais informações na seção [Requisições com erros e falhas](#requisicoes-com-erros-e-falhas).
+
+## Saiba mais
+
+| **Help Center** | **Developer Portal** |
+| :--- | :--- |
+| <p>Alterar pedidos via Admin VTEX: <ul><li><a href="https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Como funciona a Alterar pedido (Beta)</a></li><li><a href="https://help.vtex.com/pt/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw">Como alterar pedidos (Beta)</a></li></ul></p> | <p>Alterar pedidos via API:<ul><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change details</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes">Get order change history</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry">Retry order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel">Cancel order change</a></li></ul></p> |
+
diff --git a/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md b/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md
index 00d94f6e7..a99dd90c5 100644
--- a/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md
+++ b/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md
@@ -3,8 +3,8 @@ title: 'Adicionar suporte a 3DS na integração com a Adyen'
 id: 3DNZeC9qJaC2GMIw4mawYk
 status: PUBLISHED
 createdAt: 2017-07-25T18:20:05.681Z
-updatedAt: 2023-03-26T22:04:52.559Z
-publishedAt: 2023-03-26T22:04:52.559Z
+updatedAt: 2024-06-13T21:44:14.602Z
+publishedAt: 2024-06-13T21:44:14.602Z
 firstPublishedAt: 2017-08-01T16:58:04.306Z
 contentType: tutorial
 productTeam: Financial
@@ -20,10 +20,10 @@ Para adicionar suporte ao [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-sec
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Acesse a aba **Afiliações de Gateways**.
 3. Clique no card da afiliação da Adyen.
-4. Vá até __Live Endpoint URL Prefix__ e siga [este tutorial](https://www.adyen.help/hc/pt-br/articles/360014322079-Como-posso-encontrar-a-URL-do-endpoint-da-minha-conta-LIVE-) da Adyen para obter a informação.
+4. Vá até __Live Endpoint URL Prefix__ e siga [este tutorial](https://help.adyen.com/pt_BR/knowledge/ecommerce-integrations/integrations-basics/how-can-i-find-the-endpoint-url-for-my-live-account) da Adyen para obter a informação.
 5. No campo __Ativar 3d Secure?__, selecione __Sim__.
 6. Escolha o modo do 3DS (3DS, 3DS2 ou 3DS2 Data only) que foi acordado no momento da parceria comercial junto à Adyen.
-7. Finalize o preenchimento dos campos seguintes de acordo com [este tutorial](https://help.vtex.com/pt/tutorial/como-configurar-o-gateway-adyen-na-vtex--tutorials_2337?&utm_source=autocomplete).
+7. Finalize o preenchimento dos campos seguintes de acordo com [este tutorial](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3--7xAz67E2Eg63LWCQNjVdwv).
 8. Clique em __Salvar__
 
 ### Habilitar as respostas do 3DS
diff --git a/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md b/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md
index fcffc6286..44bcc7a4d 100644
--- a/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md
+++ b/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md
@@ -26,4 +26,4 @@ A estrutura do arquivo deve ser a seguinte:
 - Coluna D: Data Inicial (Formato: DD/MM/AAAA)
 - Coluna E: Data Final (Formato: DD/MM/AAAA)
 
-![urlbuilder1](https://images.ctfassets.net/alneenqid6w5/5lgNG0muqcMmS2coOkyKgw/f96b218bfbe58e04ae16869a11f174e8/urlbuilder1.png)
+![urlbuilder1](//images.ctfassets.net/alneenqid6w5/5lgNG0muqcMmS2coOkyKgw/f96b218bfbe58e04ae16869a11f174e8/urlbuilder1.png)
diff --git a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
index 9f3463463..e7504c37a 100644
--- a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
+++ b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
@@ -1,69 +1,87 @@
 ---
-title: 'Cadastrar Client Id e Client Secret para login com Facebook'
+title: 'Cadastrar Client Id e Segredo do cliente para login com Facebook'
 id: 3R7rzXWG1GswWOIkYyy8SO
 status: PUBLISHED
 createdAt: 2017-08-29T17:46:04.080Z
-updatedAt: 2023-02-08T14:33:31.750Z
-publishedAt: 2023-02-08T14:33:31.750Z
+updatedAt: 2023-10-20T21:29:11.632Z
+publishedAt: 2023-10-20T21:29:11.632Z
 firstPublishedAt: 2017-08-29T17:51:41.650Z
 contentType: tutorial
 productTeam: Identity
 author: authors_84
-slug: cadastrar-client-id-e-client-secret-para-login-com-facebook
+slug: cadastrar-client-id-e-segredo-do-cliente-para-login-com-facebook
 locale: pt
 legacySlug: cadastrar-client-id-e-client-secret-para-login-com-facebook
 subcategory: 14V5ezEX0cewOMg0o0cYM6
 ---
 
+Para ativar o login via Facebook, é necessário acessar **Configurações da conta > Autenticação** pelo Admin VTEX e preencher os campos **Client ID** e **Segredo do cliente**, conforme detalhado no artigo [Configurar login com Facebook e Google](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
 
-Para ativar o funcionamento de login por OAuth2 via Facebook, é necessário acessar o VTEX ID pelo seu admin e preencher os campos `Client ID` e `Client Secret`, conforme detalhado [neste artigo](/pt/tutorial/integracao-google-e-facebook-para-login).
-
-![Facebook OAuth PT](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/c07c9d4160e7273a0f5ad2a0cabd1bec/facebook_PT.png)
-
-Para obter esses valores, siga os passos abaixo:
-
-1. Entre no link [`https://developers.facebook.com/`](https://developers.facebook.com/);
-2. Crie uma conta de desenvolvedor do Facebook;
-3. Crie uma aplicação de Login do Facebook;
-4. Na parte superior direita, clique em __Meus aplicativos__;
-    ![Meus Aplicativos Facebook PT](https://images.ctfassets.net/alneenqid6w5/2XUFbJ20Z1Op022DLzNru7/e98c304648607f968847d01d7b568539/Meus_Aplicativos_Facebook_PT.png)
-5. Clique em adicionar um novo aplicativo
-6. Escolha __Gerenciar integrações comerciais__;
-    ![Criar ID Aplicativo Facebook PT](https://images.ctfassets.net/alneenqid6w5/4nEHH7m3rzaIjNyXCS7jwQ/b40ec36cd9b8e722f08fe1f14ed403c5/Facebook_Login_App_Type_PT.png)
-7. Em __Nome de exibição do aplicativo__, preencha com um nome correspondente à sua loja;
-8. Escolha uma das opções em __Finalidade do aplicativo__ que melhor atenda às necessidades da sua loja;
-9. Clique em __Criar ID do aplicativo__;
-    ![Configurar Criação ID Aplicativo Facebook PT](https://images.ctfassets.net/alneenqid6w5/aJ4qEYEBdQXp3IkQwcwBe/63c7c22747ed891ddb126a7ef71126f7/App_details_PT.png)
-10. Selecione __Configurar__ no campo __Login__ do Facebook;
-    ![Adicionar Configuração Login Facebook PT](https://images.ctfassets.net/alneenqid6w5/4Kz42ev7FSm0uEYIYwQ8C8/f1797d7b1ee574d6d191b8a3182d6b99/add_products_PT.png)
-
-11. Em __Produtos__, no painel lateral esquerdo, clique em __Login do Facebook > Configurações__.
-    ![Login Configurações Menu Facebook PT](https://images.ctfassets.net/alneenqid6w5/7CosZB53qkywCS1NG3Cj0r/96e6a6ccb2ed479f4802d96a2cf5195b/menu_configura____es_PT.png)
-    Defina os estados como na imagem abaixo:
-    ![Configuração URI OAuth Facebook PT](https://images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/8aeaa64b10c388f9ac5aec145bcc3055/configuracoes_Oauth_PT.png)
-    Insira as URLs abaixo em __URIs de redirecionamento do OAuth válidos__, substituindo `{{HOST_URL}}` pela URL base de sua loja e `{{accountName}}` pelo nome da sua conta como descrito no menu administrativo da loja:
-    - `https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx` 
-    - `https://{{HOST_URL}}/api/vtexid/pub/authentication/oauth/authorizationcode`
-    - `https://{{accountName}}.myvtex.com/api/vtexid/pub/authentication/oauth/authorizationcode`
-
-12. No final da página, clique no botão __Salvar alterações__.
-    ![Salvar Alterações PT](https://images.ctfassets.net/alneenqid6w5/6xrSjyVnjTdpMwK6mmg7qQ/71a97a5273c0113c6cff64681297f262/Salvar_Altera____es_PT.png)
-
-13. Na aba lateral, vá em __Configurações__ e clique em __Básico__:
-    ![Menu Configurações Aplicativo Facebook PT](https://images.ctfassets.net/alneenqid6w5/2hW7fOAt85ErH30RUI9KLA/6258527e8e1fcf22fd86e1a40739ddcd/menu_configura____es_b__sica_PT.png)
-
-14. Em __Chave Secreta do Aplicativo__, clique no botão __Mostrar__.
-    - Copie o campo __ID do Aplicativo__ e cole no campo `Client Id` no admin do VTEX ID.
-    - Copie o campo __Chave Secreta do Aplicativo__ do Aplicativo do Facebook e cole no campo `Client Secret` no admin do VTEX ID.
-    ![ID Chave Facebook PT](https://images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/ae15499ad9a86bc2adc92ec7907d30f6/ID_Chave_Facebook_PT.png)
-
-15. Insira um ícone para seu aplicativo de exatamente 1024x1024 pixels e fundo transparente;
-16. Adicione a __URL da Política de Privacidade__ da sua loja;
-    ![Configuração Básica Facebook PT](https://images.ctfassets.net/alneenqid6w5/66rxFKyvG7eCptwC7BdSWT/3c78ad5242e5b9c36f80db936c956261/Configura____o_B__sica_Facebook_PT.png)
-17. Selecione uma __Categoria__. Para lojas, a sugestão é utilizar __Compras__;
-    ![Categoria Facebook PT](https://images.ctfassets.net/alneenqid6w5/20X5DqI7WEuGwksOO6cMS2/c6fe1d2fc360de572e3cd91f372077ed/Categoria_Facebook_PT.png)
-18. Abaixo neste formulário, preencha as __Informações de contato do encarregado da proteção dos dados__ com os dados da empresa responsável pela loja;
-    ![Endereço Facebook PT](https://images.ctfassets.net/alneenqid6w5/3TenJ8YunJ6gFRs0aZQkp7/dca08831d4d92a0962a86e5a312e5ea8/Endere__o_Facebook_PT.png)
-19. No final da página, clique em __Salvar alterações__;
-    ![Salvar Alterações PT](https://images.ctfassets.net/alneenqid6w5/6xrSjyVnjTdpMwK6mmg7qQ/71a97a5273c0113c6cff64681297f262/Salvar_Altera____es_PT.png)
+![Facebook OAuth PT](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/1dcbc9286c0245740194026e19ba5c9b/1-login-fb-pt.png)
 
+Para obter essas credenciais, siga as instruções de cada etapa abaixo:
+
+1. [Criar aplicativo](#1-criar-aplicativo)
+2. [Configurar Login do Facebook no aplicativo](#2-configurar-login-do-facebook-no-aplicativo)
+3. [Realizar configurações básicas do aplicativo](#3-realizar-configuracoes-basicas-do-aplicativo)
+
+## 1. Criar aplicativo
+
+Para começar, você precisa cadastrar um aplicativo no Facebook, seguindo os passos abaixo:
+
+1. Entre no [Meta for Developers](https://developers.facebook.com/).
+2. Crie uma conta de desenvolvedor do Facebook.
+3. Na barra superior, clique em **Meus aplicativos**.
+4. Clique em `Criar aplicativo`.
+5. Clique em **Permitir que as pessoas entrem com a própria conta do Facebook**, dentre as opções ilustradas abaixo.
+
+   ![2-login-fb-pt](//images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/c5d74282b8459d40d3a0ac9026591787/2-login-fb-pt.png)
+
+6. Clique em `Avançar`.
+7. Preencha o nome do app e o email de contato do responsável pelo aplicativo, nos campos ilustrados abaixo.
+
+   ![3-login-fb-pt](//images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/2cf04b1ea40c6e4e4ed2d843296bb256/3-login-fb-pt.png)
+
+8. Clique em `Criar aplicativo`.
+
+## 2. Configurar Login do Facebook no aplicativo
+
+O próximo passo é configurar o produto Login do Facebook no aplicativo que você criou. Para isso, siga as instruções abaixo:
+
+1. Clique em **Produtos** no menu lateral ou no **Painel **do Meta for Developers, destacado a seguir.
+
+   ![4-login-fb-pt](//images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/9b7ff04d05523c1d9ec09f5b3f563d34/4-login-fb-pt.png)
+
+2. Clique em `Configurar` e, em seguida, na opção `Configurações`.
+
+   ![5-login-fb-pt](//images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/f64b512f3583de4ab35032ec1f3dcb23/5-login-fb-pt.png)
+
+3. Defina os estados como na imagem abaixo:
+
+   ![Configuração URI OAuth Facebook PT](//images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/8aeaa64b10c388f9ac5aec145bcc3055/configuracoes_Oauth_PT.png)
+
+   Insira as URLs abaixo em **URIs de redirecionamento do OAuth válidos**, substituindo `{{HOST_URL}}` pela URL base de sua loja e `{{accountName}}` pelo nome da sua conta VTEX como descrito no Admin:
+
+      * `https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
+      * `https://{{HOST_URL}}/api/vtexid/pub/authentication/oauth/authorizationcode`
+      * `https://{{accountName}}.myvtex.com/api/vtexid/pub/authentication/oauth/authorizationcode`
+
+4. No final da página, clique no botão `Salvar alterações`.
+
+## 3. Realizar configurações básicas do aplicativo
+
+Por fim, você precisa preencher algumas informações sobre o app para concluir o processo de cadastro. Nesta etapa, você vai obter o **Client Id** e o **Segredo do cliente** que serão utilizados nas configurações do login com o Facebook realizadas no Admin VTEX. Siga os passos abaixo:
+
+1. No menu lateral do Meta for Developers, vá em **Configurações do app** e clique em **Básico:**
+
+   ![7-login-fb-pt](//images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/e0a0037af04e1e1d8b465520f804d9a0/7-login-fb-pt.png)
+
+2. Copie o valor do campo **ID do Aplicativo**. Você deverá informar este valor no campo **Client ID** ao [configurar o login com Facebook no Admin VTEX](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
+3. Em **Chave Secreta do Aplicativo**, clique no botão **Mostrar** e, em seguida, copie o valor do campo. Você deverá informar este valor no campo **Segredo do cliente** ao [configurar o login com Facebook no Admin VTEX](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
+4. No campo **URL da Política de Privacidade**, adicione o link para a política de privacidade da sua loja.
+5. Em **Ícone do aplicativo (1024 x 1024)**, insira um ícone para seu aplicativo de exatamente 1024x1024 pixels e fundo transparente.
+6. Selecione uma **Categoria**. Para lojas, a sugestão é utilizar **Compras**.
+7. Abaixo neste formulário, preencha as **Informações de contato do encarregado da proteção dos dados** com os dados da empresa responsável pela loja.
+8. No final da página, clique em `Salvar alterações`.
+
+Após concluir todas essas etapas, você pode utilizar o **Client ID** e o **Segredo do cliente** obtidos para configurar o login com Facebook na sua loja, conforme detalhado no artigo [Configurar login com Facebook e Google](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
diff --git a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
index 5fab72078..e81a38547 100644
--- a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
+++ b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Para ativar o funcionamento de login por OAuth2 via Google, é necessário acessar o VTEX ID pelo seu admin e preencher os campos `Client ID` e `Client Secret`, conforme detalhado [neste artigo](/pt/tutorial/integracao-google-e-facebook-para-login).
 
-![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
+![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
 
 Esses valores são obtidos a partir de um projeto que precisa ser criado no serviço de APIs do Google Cloud Platform.
 
@@ -30,18 +30,18 @@ Os passos abaixo descrevem procedimentos em uma plataforma externa e podem estar
 1. Entrar no link [`https://console.developers.google.com/`](https://console.developers.google.com/);
 2. Clicar em __Credenciais__, na aba lateral;
 3. Clique em __Criar Projeto__;
-    ![Criar Projeto Google PT](https://images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/15e9e1be0ef0b9bfd4f6cd23833f52a6/Criar_Projeto_Google_PT.png)
+    ![Criar Projeto Google PT](//images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/15e9e1be0ef0b9bfd4f6cd23833f52a6/Criar_Projeto_Google_PT.png)
 
 4. Dê um nome ao projeto e clique em __Criar__;
-    ![Novo Projeto Google PT](https://images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/dcb58074e3fb0668c4ea336bee08870a/Novo_Projeto_Google_PT.png)
+    ![Novo Projeto Google PT](//images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/dcb58074e3fb0668c4ea336bee08870a/Novo_Projeto_Google_PT.png)
 5. No topo da página, clicar no botão __Criar credenciais__;
-    ![Criar Credenciais Google PT](https://images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/e5cbd9523888845caa07211cdec356cf/Criar_Credenciais_Google_PT.png)
+    ![Criar Credenciais Google PT](//images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/e5cbd9523888845caa07211cdec356cf/Criar_Credenciais_Google_PT.png)
 6. Clicar na opção __ID do cliente OAuth__;
-    ![ID cliente OAuth Google PT](https://images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/68b13531dab5020ea4e40f69f34a58e2/ID_cliente_OAuth_Google_PT.png)
+    ![ID cliente OAuth Google PT](//images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/68b13531dab5020ea4e40f69f34a58e2/ID_cliente_OAuth_Google_PT.png)
 7. Clicar no botão __Configurar tela de consentimento__;
-    ![Configurar Tela Consentimento Google PT](https://images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/2c7660f7dea9b320ca24df57e89910a2/Configurar_Tela_Consentimento_Google_PT.png)
+    ![Configurar Tela Consentimento Google PT](//images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/2c7660f7dea9b320ca24df57e89910a2/Configurar_Tela_Consentimento_Google_PT.png)
 8. Escolha o tipo de usuário desejado para a sua loja (__Interno__ ou __Externo__) e clique no botão __Criar__;
-    ![Tipo usuário Google PT](https://images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/7579b27f325d7e2c31444ba21a29a017/Tipo_usu__rio_PT.png)
+    ![Tipo usuário Google PT](//images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/7579b27f325d7e2c31444ba21a29a017/Tipo_usu__rio_PT.png)
 9.  __Nome do app__: será exibido aos seus clientes no momento do login;
 10. __E-mail para suporte do usuário__: para que os usuários contatem você com perguntas sobre o consentimento;
 11. __Logotipo do app__: corresponde ao logotipo da sua loja;
@@ -50,21 +50,21 @@ Os passos abaixo descrevem procedimentos em uma plataforma externa e podem estar
     - `vtex.com.br`, relativo aos nossos servidores de backend
 13. __Dados de contato do desenvolvedor__: o Google usa esses endereços de e-mail para notificar você sore todas as alterações do projeto;
 14. Clicar no botão __Salvar e continuar__;
-    ![Configurações Tela Consentimento PT](https://images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/db5c3ff4f9ca43f8a50e51bfb49376ac/Configura____es_Tela_Consentimento_PT.png)
+    ![Configurações Tela Consentimento PT](//images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/db5c3ff4f9ca43f8a50e51bfb49376ac/Configura____es_Tela_Consentimento_PT.png)
 13. Clicar no item do menu lateral esquerdo __Credenciais__;
 14. Escolher __Aplicativo da Web__, em Tipo de aplicativo;
-    ![Credenciais Aplicativo Web Google PT](https://images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/1b63eaf43364a7d6f1ebe2330b396a72/Credenciais_Aplicativo_Web_Google_PT.png)
+    ![Credenciais Aplicativo Web Google PT](//images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/1b63eaf43364a7d6f1ebe2330b396a72/Credenciais_Aplicativo_Web_Google_PT.png)
 15. __Nome__: para identificação interna;
 16. __Origens JavaScript autorizadas__: cadastrar os endereços exatos que poderão usar este método de autenticação, o que corresponde ao seu site; exemplo `https://www.loja.com`. Também é recomendado cadastrar o endereço `https://{{accountName}}.myvtex.com` de sua conta, onde `{{accountName}}` é o nome da sua conta como descrito no menu administrativo da loja;
 17. __URIs de redirecionamento autorizados__: cadastrar a URL de serviço da VTEX:
 
     -`https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
 
-    ![Configurações Aplicativo Web Google PT](https://images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/91105aa43df17443cfecdcad79acc3a4/Configura____es_Aplicativo_Web_PT.png)
+    ![Configurações Aplicativo Web Google PT](//images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/91105aa43df17443cfecdcad79acc3a4/Configura____es_Aplicativo_Web_PT.png)
 
 18. Após concluído, serão apresentadas suas credenciais:
-    ![Cliente OAuth criado Google PT](https://images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/2aea225da796a27ea6974766b984a493/Cliente_OAuth_criado_Google_PT.png)
+    ![Cliente OAuth criado Google PT](//images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/2aea225da796a27ea6974766b984a493/Cliente_OAuth_criado_Google_PT.png)
     - Copie o __ID do cliente__ do Google e cole no campo `Client Id` no admin do VTEX ID.
     - Copie a __chave secreta do cliente__ do Google e cole no campo `Client Secret` no admin do VTEX ID.
-    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
+    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
     Depois de cumprir esses passos, salve as alterações.    
diff --git a/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md b/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md
new file mode 100644
index 000000000..52b539937
--- /dev/null
+++ b/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md
@@ -0,0 +1,48 @@
+---
+title: 'Incluir um registro em um formulário do Master Data'
+id: tutorials_6264
+status: PUBLISHED
+createdAt: 2017-04-27T21:48:37.277Z
+updatedAt: 2024-07-17T21:25:51.382Z
+publishedAt: 2024-07-17T21:25:51.382Z
+firstPublishedAt: 2017-04-27T23:11:18.994Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: incluir-um-registro-em-um-formulario-do-master-data
+locale: pt
+legacySlug: como-incluir-um-registro-em-um-formulario-do-master-data
+subcategory: 42hDtnYXHw5ExG6l19RP1l
+---
+
+Para incluir um registro em um formulário do Master Data, é necessário acessar o Master Data e escolher a aplicação que você deseja visualizar. Para isso, siga as instruções das seções abaixo.
+
+Os campos podem ser configurados como editáveis ou não diretamente na entidade de dados. Saiba mais em [Entidade de dados](https://help.vtex.com/pt/tutorial/entidade-de-dados--tutorials_1265).
+
+<div class="alert alert-warning">
+Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+ <ul>
+  <li><a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">Características das versões do Master Data</a></li>
+  <li><a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">Master Data v2</a></li>
+</ul>
+</div>
+
+## Adicionar um registro
+
+Para salvar um novo registro, como o perfil de um novo cliente, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Na aplicação, encontre a linha do formulário ao qual deseja adicionar um registro e clique no ícone de adição <i class="fas fa-plus-circle"></i>.
+3. Preencha os campos presentes no formulário.
+4. Clique em `Salvar`.
+
+## Editar um registro
+
+Para modificar um registro existente, como as informações de um cliente da sua loja, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Na aplicação, encontre a linha do formulário que contém o registro que você deseja editar e clique no ícone de menu <i class="fas fa-bars"></i>.
+3. Se desejar, busque o registro por algum campo definido na entidade de dados como buscável.
+4. Clique no ícone de edição <i class="fas fa-edit"></i> na linha do registro que deseja editar.
+5. Realize as modificações desejadas.
+6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/adding-an-attachment.md b/docs/tutorials/pt/adding-an-attachment.md
index bbadea97b..c342d7afd 100644
--- a/docs/tutorials/pt/adding-an-attachment.md
+++ b/docs/tutorials/pt/adding-an-attachment.md
@@ -3,8 +3,8 @@ title: 'Cadastrar um anexo'
 id: 7zHMUpuoQE4cAskqEUWScU
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:42.901Z
-updatedAt: 2023-03-29T15:07:58.328Z
-publishedAt: 2023-03-29T15:07:58.328Z
+updatedAt: 2023-11-16T17:23:31.034Z
+publishedAt: 2023-11-16T17:23:31.034Z
 firstPublishedAt: 2019-01-24T22:06:25.639Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -31,7 +31,7 @@ O objetivo de um anexo é [complementar o produto com uma informação personali
 Após realizar o cadastro inicial do anexo, você precisa adicionar as chaves e os **Valores Permitidos** relacionados ao anexo criado. Você pode adicionar quantas chaves desejar. Para adicionar as chaves e os **Valores Permitidos**, siga os passos a seguir.
 
 1. Na página **Campos personalizados**, identifique a linha do anexo criado e clique em `Alterar`, conforme ilustrado na imagem abaixo.
-   ![anexos.pt](https://images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/cfb0a116c7f139d84ba256cab5b649cd/anexos.pt.png)
+   ![anexos.pt](//images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/cfb0a116c7f139d84ba256cab5b649cd/anexos.pt.png)
 2. Preencha os campos listados a seguir.
     * **Nome da Chave:** nome da informação personalizada. Este campo é obrigatório e não pode conter caracteres especiais, apenas letras, números ou pontos. Exemplo: se o produto personalizável for uma Camisa da Seleção Brasileira, os nomes das suas chaves podem ser `Nome` e `Numero`.
     * **Máximo de Caracteres:** máximo de caracteres que o cliente pode digitar para inserir uma informação personalizada no produto. Este campo é obrigatório. Exemplo: neste campo você poderia estipular o limite de caracteres para o nome que será impresso em uma camisa.
diff --git a/docs/tutorials/pt/adding-bin-information.md b/docs/tutorials/pt/adding-bin-information.md
new file mode 100644
index 000000000..bd0d44ac7
--- /dev/null
+++ b/docs/tutorials/pt/adding-bin-information.md
@@ -0,0 +1,43 @@
+---
+title: 'Cadastrar informações de BINs'
+id: 7xvo4JJ53WM7aLzufdC4au
+status: PUBLISHED
+createdAt: 2024-05-02T19:11:00.734Z
+updatedAt: 2024-05-03T13:40:32.363Z
+publishedAt: 2024-05-03T13:40:32.363Z
+firstPublishedAt: 2024-05-02T19:44:35.388Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: cadastrar-informacoes-de-bins
+locale: pt
+legacySlug: cadastrar-informacoes-de-bins
+subcategory: 2Xay1NOZKE2CSqKMwckOm8
+---
+
+O Número de Identificação Bancária (BIN) é composto pelos primeiros seis ou oito dígitos de um cartão de crédito ou débito e caracteriza a instituição responsável pela emissão do cartão.  
+
+![BIN_image_digits_PT_2](//images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/7ea68dacd8491fba2022ccb608efd3fd/BIN_image_digits_PT_2.png)
+
+Quando a instituição bancária deseja criar novos perfis de cartões ou emitir novos cartões para um modelo já existente, é necessário criar novos BINs. Isso também se aplica quando uma [bandeira](https://help.vtex.com/pt/tutorial/o-que-e-uma-bandeira-de-cartao-de-credito--4bNba5QYuIwKEmac88KwyI) é comprada por outra.
+
+Nestas situações, a VTEX precisa ser notificada para permitir que os novos cartões possam ser validados de forma correta no processo de pagamento em uma compra realizada na plataforma.
+
+## Solicitar a inclusão de BINs
+
+Para adicionar um novo BIN ou atualizar informações de um BIN já existente na VTEX, é necessário abrir um ticket no [Suporte VTEX](https://help.vtex.com/pt/support). 
+
+No ticket, você deve encaminhar em anexo uma planilha preenchida com as seguintes informações:
+
+- __code__: novo BIN a ser adicionado ou BIN já existente que deverá ser atualizado.
+- __cardBrand__: bandeira do cartão correspondente ao BIN.
+- __cardType__: tipo de cartão (Crédito ou Débito).
+- __country__: país de utilização do cartão.
+- __bank__: banco responsável pela emissão do cartão.
+- __cvvSize__: quantidade de caracteres do CVV (Card Verification Value).
+- __cardLevel__: classificação do cartão (Gold, Platinum, Black, entre outros). 
+
+Modelo de planilha preenchida:
+
+![Bin_spreadsheet](//images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/f28a04568922f6e08425ae177b26b0fe/Bin_spreadsheet.PNG)
+
diff --git a/docs/tutorials/pt/adding-collections-cms.md b/docs/tutorials/pt/adding-collections-cms.md
index dedb8c959..38db87410 100644
--- a/docs/tutorials/pt/adding-collections-cms.md
+++ b/docs/tutorials/pt/adding-collections-cms.md
@@ -33,7 +33,7 @@ Siga o passo a passo abaixo para cadastrar uma nova coleção:
 
 A escolha dos produtos que vão compor uma coleção é feita através da criação de um __grupo__. Para isso, basta clicar em __New Group__ dentro da coleção desejada. 
 
-![2019-06-06 16 22 46-Layout](https://images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
+![2019-06-06 16 22 46-Layout](//images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
 
 Antes de escolher quais produtos farão parte do grupo, como veremos a seguir, é necessário atribuir um nome e especificar o tipo de grupo criado. 
 
@@ -75,17 +75,17 @@ Por exemplo: ao selecionar a categoria `A` e a marca `B`, apenas os produtos que
 
 Para adicionar todos os produtos de um determinado Departamento a um grupo, basta selecionar o Departamento desejado e clicar em __Save Group__, como mostra a imagem abaixo. 
 
-![selecionar-departamento-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/577w3KpNuahKOiY0iQTYrp/6f036e35d347f1f9dbf66e347e151ca6/selecionar-departamento-colecoes-cms_PT.png)
+![selecionar-departamento-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/577w3KpNuahKOiY0iQTYrp/6f036e35d347f1f9dbf66e347e151ca6/selecionar-departamento-colecoes-cms_PT.png)
 
 O mesmo se aplica aos produtos de uma determinada Categoria ou Subcategoria.
 
-![selecionar-categoria-subcategoria-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/6bV3ick7BunjS5QOnMVpED/d5f4b348b405f6e05248f088cba664c5/selecionar-categoria-subcategoria-colecoes-cms_PT.png)
+![selecionar-categoria-subcategoria-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/6bV3ick7BunjS5QOnMVpED/d5f4b348b405f6e05248f088cba664c5/selecionar-categoria-subcategoria-colecoes-cms_PT.png)
 
 ## Produtos por Marca
 
 Para criar um grupo com produtos de uma ou mais marcas, basta selecionar a marca desejada na lista correspondente. 
 
-![selecionar-marcas-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/2f4nqqF2CWFbw5Cgjmc32f/d6c7c8ce8f198255cd744e5e60668962/selecionar-marcas-colecoes-cms_PT.png)
+![selecionar-marcas-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/2f4nqqF2CWFbw5Cgjmc32f/d6c7c8ce8f198255cd744e5e60668962/selecionar-marcas-colecoes-cms_PT.png)
 
 As marcas encontram-se dispostas em ordem alfabética. Ao clicar na letra correspondente à inicial da marca desejada, a lista se expande e exibe as marcas existentes.
 
@@ -95,7 +95,7 @@ As marcas encontram-se dispostas em ordem alfabética. Ao clicar na letra corres
 
 Ao adicionar um SKU a um grupo, o produto ao qual ele está vinculado também será adicionado. Em um cenário em que um produto tenha mais de um SKU atribuido a ele, a adição de um único SKU fará com que todos os outros também sejam adicionados ao grupo.
 
-![add-skus-manualmente-coleção-cms](https://images.ctfassets.net/alneenqid6w5/4DWiR2pUd1U40fWTAqmwG1/96f1f747f2250c98cec87b6d7e02e6d3/add-skus-manualmente-cole____o-cms.png)
+![add-skus-manualmente-coleção-cms](//images.ctfassets.net/alneenqid6w5/4DWiR2pUd1U40fWTAqmwG1/96f1f747f2250c98cec87b6d7e02e6d3/add-skus-manualmente-cole____o-cms.png)
 
 No campo __Find SKUs__, é possível digitar o ID de quantos SKUs forem desejados, escrevendo os valores entre vírgulas. 
 
@@ -117,21 +117,21 @@ Obtenha o modelo de arquivo para a inclusão e exclusão de SKUs da coleção <a
 
 No campo __Bulk Insert SKUs__, é possível inserir por planilha (formato `.xls`) uma listagem de SKUs que farão parte do grupo.
 
-![add-skus-manualmente-planilha-coleção-cms](https://images.ctfassets.net/alneenqid6w5/46dZS1m8ISWP68SMNZrMlm/2b733ea38c3f62d7c503a44c6f55fb56/add-skus-manualmente-planilha-cole____o-cms.png)
+![add-skus-manualmente-planilha-coleção-cms](//images.ctfassets.net/alneenqid6w5/46dZS1m8ISWP68SMNZrMlm/2b733ea38c3f62d7c503a44c6f55fb56/add-skus-manualmente-planilha-cole____o-cms.png)
 
 Na planilha, todos os IDs dos SKUs devem estar dispostos na primeira coluna, com o cabeçalho, como exemplifica a figura abaixo:
 
-![exemplo-planilha-seleção-sku-coleção](https://images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
+![exemplo-planilha-seleção-sku-coleção](//images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
 
 Depois de selecionar a planilha desejada, clique na opção de __Import skus__ para enviar as informações.
 
-![Import SKUs](https://images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
+![Import SKUs](//images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
 
 #### Exclusão massiva
 
 Para evitar a exclusão manual de um SKU por vez, também é possível usar o recurso de importação de planilha para a exclusão massiva. 
 
-![exclusao-skus-manualmente-planilha-coleção-cms](https://images.ctfassets.net/alneenqid6w5/2LVbuzlmh0nmgY4z21i9Be/f55707ea917364ed1732a4050b98a7a3/exclusao-skus-manualmente-planilha-cole____o-cms.png)
+![exclusao-skus-manualmente-planilha-coleção-cms](//images.ctfassets.net/alneenqid6w5/2LVbuzlmh0nmgY4z21i9Be/f55707ea917364ed1732a4050b98a7a3/exclusao-skus-manualmente-planilha-cole____o-cms.png)
 
 Nesse caso em específico, os SKUs listados na planilha importada serão excluídos do grupo. Para isso, clique na opção __excluir skus__ depois que o arquivo for carregado.
 
@@ -147,7 +147,7 @@ Na seção de <strong>Other options</strong>, as opções <strong>Pre-sales</str
 
 Note que apenas é possível selecionar uma das duas opções. Caso queira que ambos os cenários sejam contemplados, crie dois grupos e configure cada um deles com a respectiva opção.
 
-![selecionar-other-options-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/2SrWIT3WZdqgYe2m6NUvhP/c0b4a98dd766dc27c63f706f4592ec40/selecionar-other-options-colecoes-cms_PT.png)
+![selecionar-other-options-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/2SrWIT3WZdqgYe2m6NUvhP/c0b4a98dd766dc27c63f706f4592ec40/selecionar-other-options-colecoes-cms_PT.png)
 
 ### Pre-sales
 
diff --git a/docs/tutorials/pt/adding-sku-specifications-or-fields.md b/docs/tutorials/pt/adding-sku-specifications-or-fields.md
index 86f30e58b..8bdc2453d 100644
--- a/docs/tutorials/pt/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/pt/adding-sku-specifications-or-fields.md
@@ -3,8 +3,8 @@ title: 'Cadastrar especificações ou campos de SKU'
 id: tutorials_119
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:08.662Z
-updatedAt: 2023-03-29T17:31:34.699Z
-publishedAt: 2023-03-29T17:31:34.699Z
+updatedAt: 2023-11-30T12:05:25.945Z
+publishedAt: 2023-11-30T12:05:25.945Z
 firstPublishedAt: 2017-04-27T23:00:44.181Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: criando-campo-de-sku
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-A especificação de SKU é um campo no cadastro de SKU onde se inserem as características específicas de cada variação do produto.
+A especificação de SKU é um campo obrigatório no cadastro de SKU onde se inserem as características específicas de cada variação do produto.
 
 Na VTEX, uma especificação sempre faz parte de um [grupo de especificações](https://help.vtex.com/pt/tutorial/criando-grupo-de-categoria), que é associado a uma [categoria](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2gkZDjXRqfsq62TlAkj4uf). Por isso, para criar uma especificação (campo) de SKU, é necessário ter cadastrado previamente pelo menos uma categoria e um grupo de especificações.
 
@@ -43,7 +43,7 @@ Antes de criar especificações, é importante compreender que elas seguem uma l
 
 Exemplo: considere o produto **Camisa Masculina**. Em __Catálogo > Produtos e SKUs > SKU > Especificações__, página ilustrada a seguir, podemos ver que o grupo de especificações chamado **Características** está associado à categoria da camisa. Esse grupo inclui um campo de nome **Cor** e um campo de nome **Tamanho**.
 
-![heranca-especificacoes-sku-pt](https://images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/559bba5b55428ce03d7f1cda2c943b3a/image5.png)
+![heranca-especificacoes-sku-pt](//images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/559bba5b55428ce03d7f1cda2c943b3a/image5.png)
 
 Por se tratar de uma especificação de SKU, as informações selecionadas nessa página valerão somente para essa variação do produto **Camisa Masculina**. Todos os SKUs cadastrados no produto **Camisa Masculina** e todos os SKUs de produtos da mesma categoria devem ter essas especificações preenchidas também.
 
@@ -85,7 +85,7 @@ Para criar um campo de SKU, siga as instruções abaixo:
     * **Ativo**: insere ou remove este campo no cadastro do SKU.
 7. Clique em `Salvar`.
 
-![sku-spec-1](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/f79bf71a242604110e96e435c58d1170/pt-sku-spec-1.gif)
+![sku-spec-1](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/f79bf71a242604110e96e435c58d1170/pt-sku-spec-1.gif)
 
 #### Tipos de campo de SKU
 
@@ -130,13 +130,13 @@ Os **Valores** dos campos de SKU irão variar de acordo com o tipo do campo esco
 
     Insira um valor por linha e tecle `Enter` entre cada valor, conforme ilustrado na imagem a seguir.
 
-    ![valores-campo-sku-pt](https://images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/c513840f0f21b2f76ec2215b239f3395/image9.png)
+    ![valores-campo-sku-pt](//images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/c513840f0f21b2f76ec2215b239f3395/image9.png)
 
 8. Clique em `Salvar`.
 
     Os valores cadastrados serão exibidos na [interface do cadastro de SKU](#preencher-especificacoes-de-sku).
 
-![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/066317aa51dbd5521e83f85d9923782f/pt-sku-spec-2.gif)
+![sku-spec-2](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/066317aa51dbd5521e83f85d9923782f/pt-sku-spec-2.gif)
 
 <div class = "alert alert-info">
   <p>Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção <strong>Ativo</strong>.</p>
@@ -181,7 +181,7 @@ Para preencher as especificações de cada SKU de forma individual, siga as inst
 
 8. Clique em `Salvar`.
 
-![sku-spec-3](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/448631dcf3653ce0af8373b24e353a5a/pt-sku-spec-3.gif)
+![sku-spec-3](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/448631dcf3653ce0af8373b24e353a5a/pt-sku-spec-3.gif)
 
 #### Planilha
 
@@ -204,7 +204,7 @@ Para preencher especificações de SKUs em massa por planilha, você precisa exp
 9. Clique em **Selecionar** para selecionar o arquivo com a planilha preenchida no seu computador.
 10. Clique em `Importar`.
 
-![sku-spec-4](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/d71e8d6726d70416fa50bba58fcb1cfc/pt-sku-spec-4.gif)
+![sku-spec-4](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/d71e8d6726d70416fa50bba58fcb1cfc/pt-sku-spec-4.gif)
 
 ## Saiba mais
 - [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106)
diff --git a/docs/tutorials/pt/adding-specifications-or-product-fields.md b/docs/tutorials/pt/adding-specifications-or-product-fields.md
index c285561c4..483c63aab 100644
--- a/docs/tutorials/pt/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/pt/adding-specifications-or-product-fields.md
@@ -43,7 +43,7 @@ Antes de criar especificações, é importante compreender que as especificaçõ
 
 Considere o produto **Televisão** como exemplo. Em **Catálogo > Todos os produtos > Alterar > Especificações**, página ilustrada a seguir, podemos ver que o grupo de especificações chamado **Características** está associado à categoria da televisão. Esse grupo inclui um campo de nome **Polegadas** e um campo de nome **Faixa etária**, que são obrigatórios.
 
-![especificacoes-caracteristicas-pt](https://images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/ac89c8d88e3188da9d6af758d0e6992a/image6.png)
+![especificacoes-caracteristicas-pt](//images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/ac89c8d88e3188da9d6af758d0e6992a/image6.png)
 
 Por se tratar de uma especificação de produto, as informações selecionadas nessa página valerão para todas as variações do produto __Televisão__. Todos os produtos cadastrados na mesma categoria da televisão precisam ter essas especificações preenchidas também, visto que os campos são obrigatórios.
 
@@ -80,7 +80,7 @@ Para criar um campo de produto, siga os passos abaixo:
     * **Ativo**: insere ou remove este campo no cadastro do produto (aba **Especificações**).
 7. Clique em `Salvar`. 
 
-![product-spec-1](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/7d508a1ad7465143efe1465d19275e19/PT_ProdutoGif_1_Alterado.gif)
+![product-spec-1](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/7d508a1ad7465143efe1465d19275e19/PT_ProdutoGif_1_Alterado.gif)
 
 #### Tipos de campo de produto
 
@@ -146,7 +146,7 @@ Já para os campos de tipo **Combo**, **Radio** e **CheckBox**, é necessário c
 
     Os valores criados serão exibidos na aba **Especificação** no cadastro de Produto.
 
-![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/283b1aca04c1790b548ee51438fe132f/PT_ProdutoGif_2_Alterado.gif)
+![product-spec-2](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/283b1aca04c1790b548ee51438fe132f/PT_ProdutoGif_2_Alterado.gif)
 
 <div class = "alert alert-info">
   <p>Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção <strong>Ativo</strong>.</p>
@@ -188,7 +188,7 @@ Para preencher as especificações de cada produto de forma individual, siga as
 
 6. Clique em `Salvar`.
 
-![product-spec-3](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/f54f61f82531c5be837a8516278103df/PT_ProdutoGif_3_Alterado.gif)
+![product-spec-3](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/f54f61f82531c5be837a8516278103df/PT_ProdutoGif_3_Alterado.gif)
 
 #### Planilha
 
@@ -211,7 +211,7 @@ Para preencher especificações de produtos em massa por planilha, é necessári
 9. Clique em **Select** para selecionar o arquivo com a planilha preenchida no seu computador.
 10. Clique em `Importar`.
 
-![product-spec-4](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/e25821cf11d4b27e9142389fbd207d85/PT_ProdutoGif_4_Alterado.gif)
+![product-spec-4](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/e25821cf11d4b27e9142389fbd207d85/PT_ProdutoGif_4_Alterado.gif)
 
 ## Saiba mais
 - [Cadastrar especificações ou campos de SKU](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119)
diff --git a/docs/tutorials/pt/additional-shipping-costs.md b/docs/tutorials/pt/additional-shipping-costs.md
index 74840d90d..52aedea1e 100644
--- a/docs/tutorials/pt/additional-shipping-costs.md
+++ b/docs/tutorials/pt/additional-shipping-costs.md
@@ -18,7 +18,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Os adicionais de frete são valores extras adicionados ao custo de envio pelas [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Então, ao configurar um valor de custo para a entrega dos itens da sua loja, é possível configurar uma tarifa fixa e incluir valores adicionais. O custo fixo de entrega somado aos adicionais compõem os custos da [tarifa de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM).
 
-![Tarifa envio PT](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
+![Tarifa envio PT](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
 
 Os valores adicionais podem ser configurados conforme:
 
diff --git a/docs/tutorials/pt/admin-redirect-search-returns-no-results.md b/docs/tutorials/pt/admin-redirect-search-returns-no-results.md
new file mode 100644
index 000000000..08fbe2e66
--- /dev/null
+++ b/docs/tutorials/pt/admin-redirect-search-returns-no-results.md
@@ -0,0 +1,111 @@
+---
+title: 'Busca de redirects no Admin não retorna resultados'
+id: 2u5cJhUSVM6bbEAFkgUww7
+status: PUBLISHED
+createdAt: 2024-07-24T13:41:02.016Z
+updatedAt: 2024-07-24T14:33:50.131Z
+publishedAt: 2024-07-24T14:33:50.131Z
+firstPublishedAt: 2024-07-24T14:13:11.586Z
+contentType: tutorial
+productTeam: Others
+author: 4ubliktPJIsvyl1hq91RdK
+slug: busca-de-redirects-no-admin-nao-retorna-resultados
+locale: pt
+legacySlug: busca-de-redirects-no-admin-nao-retorna-resultados
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palavras-chave:** redirect
+
+Quando o número de redirects é muito grande, a página Redirecionamentos no Admin não consegue processar a busca. Então, ao tentar realizar a busca, ela não retorna resultados. Para mais detalhes sobre a página Redirecionamentos, veja o artigo [Gerenciando redirecionamentos de URL por binding](https://help.vtex.com/pt/tutorial/gerenciando-redirecionamentos-de-url-por-binding--67GAK2TCQgjvmtPXxAqREb).
+
+## Solução
+
+Siga estes passos para obter os redirects:
+
+1. Acesse a **GraphQL IDE** pela página `{nome_da_conta}.myvtex.com/admin/graphql-ide`. Substitua `{nome_da_conta}` pelo nome da sua conta VTEX.
+2. Selecione o app `vtex.rewriter@x`, sendo `x` a versão do app. Por exemplo, `vtex.rewriter@1.62.0`.
+3. Use a seguinte query GraphQL para listar os redirects da loja:
+
+  ```
+  query {
+    redirect{
+      listRedirects{
+        routes{
+          from
+          to
+          endDate
+          type
+          binding
+        }
+      }
+    }
+  }
+  ```
+
+  O resultado esperado aparecerá no seguinte formato:
+
+  ```json
+  {
+    "data": {
+      "redirect": {
+        "listRedirects": {
+          "routes": [
+            {
+              "from": "/hello",
+              "to": "hola",
+              "endDate": null,
+              "type": "PERMANENT",
+              "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+            },
+            {
+              "from": "/v/*",
+              "to": "https://masrefacciones.backend.verbolia.com",
+              "endDate": null,
+              "type": "PERMANENT",
+              "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+            }
+          ]
+        }
+      }
+    }
+  }
+  ```
+
+4. De forma alternativa, caso o caminho do redirect que deseja encontrar seja conhecido, utilize a seguinte query GraphQL substituindo `/hello` pelo caminho do redirect desejado:
+
+  ```
+  query {
+    redirect{
+      get(path:"/hello"){
+        from
+        to
+        endDate
+        type
+        binding
+      }
+    }
+  }
+  ```
+
+  O resultado esperado aparecerá no seguinte formato:
+
+  ```json
+  {
+    "data": {
+      "redirect": {
+        "get": {
+          "from": "/hello",
+          "to": "hola",
+          "endDate": null,
+          "type": "PERMANENT",
+          "binding": "56bc9434-7b8a-4ab1-a693-36271595a27d"
+        }
+      }
+    }
+  }
+  ```
+
+Caso os redirects não estejam como esperado, o app Rewriter permite fazer outras operações com redirects, como apagar os existentes e criar novos. Para detalhes sobre essas operações, veja o guia [Rewriter GraphQL API](https://developers.vtex.com/docs/apps/vtex.rewriter/rewriter-graphql-api).
+
+Além disso, é possível exportar e importar redirects com arquivos `.csv` utilizando a página Redirecionamentos ou o [plugin](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-plugins) `redirects` do VTEX IO CLI. Para detalhes sobre importar e exportar redirects, veja o artigo [Gerenciando redirecionamentos de URL por binding](https://help.vtex.com/pt/tutorial/gerenciando-redirecionamentos-de-url-por-binding--67GAK2TCQgjvmtPXxAqREb#importando-e-exportando-redirecionamentos) e a [referência de comandos do VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-command-reference#redirects-delete).
diff --git a/docs/tutorials/pt/admin-v4-getting-started.md b/docs/tutorials/pt/admin-v4-getting-started.md
index d541e261a..479fe5f1a 100644
--- a/docs/tutorials/pt/admin-v4-getting-started.md
+++ b/docs/tutorials/pt/admin-v4-getting-started.md
@@ -26,29 +26,29 @@ Enquanto ainda estamos migrando as páginas para o Admin v4, você pode encontra
 ## Navegação aprimorada 
 Tudo que você precisa para administrar sua loja VTEX continua disponível no Admin v4, mas agora com uma organização mais simples. Nossos menus de navegação lateral e barra superior foram reformulados do zero, agrupando categorias similares de forma mais clara para reduzir as distrações e ajudar a sua equipe a encontrar o que precisa mais rapidamente. Também é possível utilizar a barra de busca para encontrar seções específicas no menu lateral.
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Central de Informações
 É aqui que reunimos todos os links úteis do nosso ecossistema VTEX, para ajudá-lo a aproveitar a nossa plataforma ao máximo. Clicando no botão `?` na barra superior, você pode acessar nosso Help Center, Developer Portal, Status da Plataforma, blog e páginas de suporte.
 
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Configurações da Loja
 Para esta nova experiência, reunimos todas as configurações de todas as seções do seu Admin em uma guia específica: Configurações da Loja. Através dessa melhoria, você pode acessar facilmente todas as configurações que afetam cada serviço da sua conta.
 
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Configurações de Perfil
 Seu avatar de perfil, no canto superior direito, agora reúne todas as configurações relacionadas ao seu usuário e à sua conta. Através do avatar, você pode acessar as configurações do usuário, as configurações da conta, as informações de faturas, alterar o idioma do seu Admin, voltar para a versão anterior do Admin e encerrar a sessão. Com essa melhoria, separamos as configurações do seu perfil das configurações que afetam a sua loja em si. Agora você tem mais controle e visibilidade sobre as ações que afetam o seu negócio e as que afetam o seu perfil.
 
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 ## Página inicial renovada
 A página inicial do nosso admin foi redesenhada para oferecer uma visão geral de alto nível da sua loja, como uma cabine de comando para as suas operações de comércio digital. Por isso, ela agora se chama **Dashboard**.
 
 Assim que você fizer login no Admin v4, verá métricas e gráficos úteis para monitorar o desempenho da sua loja, como a receita gerada e o número de pedidos, o funil de vendas e a taxa de conversão, além dos 10 produtos que geraram maior receita. Veja todos os componentes do novo Dashboard e aprenda como eles funcionam na lista abaixo.
 
-![Dashboard v4](https://images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
+![Dashboard v4](//images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
 
 - **Pedidos:** número de pedidos realizados. Todos os dados sobre pedidos e receita vêm do Sistema de Gerenciamento de Pedidos da VTEX.
 - **Sessões:** número de visitas à loja.  
diff --git a/docs/tutorials/pt/ads-from-vtex-sales-app.md b/docs/tutorials/pt/ads-from-vtex-sales-app.md
index cb5afb510..172e92662 100644
--- a/docs/tutorials/pt/ads-from-vtex-sales-app.md
+++ b/docs/tutorials/pt/ads-from-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Anúncios do VTEX Sales App'
 id: 3UtOFwbwD4muz3p72RBPmC
 status: PUBLISHED
 createdAt: 2023-05-25T17:16:06.902Z
-updatedAt: 2023-05-30T15:53:49.413Z
-publishedAt: 2023-05-30T15:53:49.413Z
+updatedAt: 2024-06-26T18:31:53.389Z
+publishedAt: 2024-06-26T18:31:53.389Z
 firstPublishedAt: 2023-05-26T22:11:51.769Z
 contentType: tutorial
 productTeam: Shopping
@@ -17,6 +17,8 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 
 A nova área de anúncios no VTEX Sales App conta com dois tipos principais de anúncios: produtos específicos ou resultados de busca. Essa flexibilidade permite que os merchants adaptem suas estratégias de marketing de acordo com suas necessidades e objetivos específicos, promovendo produtos individuais ou grupos de produtos relacionados.
 
+Para customizar a vitrine de uma loja, os lojistas podem adicionar uma página de `Anúncio por loja` especificando o ID da loja no [Master Data](https://developers.vtex.com/docs/guides/master-data-introduction) ao qual o anúncio será vinculado, permitindo criar anúncios personalizados para cada loja.
+
 Neste documento, forneceremos instruções detalhadas sobre como instalar, configurar e utilizar a nova área de anúncios. Siga os passos descritos abaixo para configurar esta ferramenta e impulsionar suas vendas online.
 
 * [Instalar as dependências da VTEX](#instalar-as-dependencias-da-vtex)
@@ -29,31 +31,31 @@ Neste documento, forneceremos instruções detalhadas sobre como instalar, confi
 
 Antes de instalar as dependências, você deve possuir o [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install) instalado. Com o VTEX IO CLI instalado, execute os seguintes comandos no prompt do seu computador para instalar as dependências necessárias:
 
-```
-vtex login {account}
-
-vtex install vtex.admin-cms@1.x vtex.admin-cms-graphql@0.x 
-vtex.admin-cms-graphql-rc@1.x vtex.admin-releases@0.x 
-vtex.cms-builder-sf-jamstack@1.x
-```
+1.
+    ```
+    vtex login {account}  
+    ```
+2.
+    ```
+    vtex install vtex.admin-cms@1.x vtex.admin-cms-graphql@0.x vtex.admin-cms-graphql-rc@1.x vtex.admin-releases@0.x vtex.cms-builder-sf-jamstack@1.x
+    ```
 
 ## Configurar o aplicativo Headless CMS
 
 1. No Admin VTEX, acesse  **Aplicativos > Meus Aplicativos**, ou digite **Meus Aplicativos** na barra de busca no topo da página.
 2. Clique em `Configurações` do item **CMS (alpha)**.
 3. Clique em `Add More`.
-4. No campo **Project ID**, digite `instore`.
+4. No campo **Project ID**, digite `assisted-sales-app`.
 5. No campo **Sections URL**, digite `https://instore--instore.vtex.app/assisted-sales/cms/sections.json`.
 6. No campo **Content types URL**, digite `https://instore--instore.vtex.app/assisted-sales/cms/content-types.json`.
-7. No campo **Translation keys URL**, digite `https://instore--instore.vtex.app/assisted-sales/cms/translation-keys.json`.
-8. Clique em `Save`.
+7. Clique em `Save`.
 
 ## Criar página de anúncios
 
 Para criar uma página de anúncios para o VTEX Sales App, siga os passos abaixo:
 
 1. Acesse a URL do VTEX Admin: 
-```https://{conta_principal}.myvtex.com/admin/new-cms/instore```
+```https://{conta_principal}.myvtex.com/admin/new-cms/assisted-sales-app```
 2. Clique em **Criar Novo** e selecione **Anúncios**.
 3. Clique em **Untitled** para editar e incluir o nome que desejar. Recomendamos o nome **Anúncios**.
 4. Na aba **Seções**, clique no botão `+` para adicionar uma nova seção. Cada seção é um uma coleção de produtos ou termos de busca. Cada seção será exibida como uma vitrine no formato de carrossel. Você pode ordernar as vitrines clicando nos botões `Mover para baixo` ou `Mover para cima`. 
@@ -62,21 +64,24 @@ Para criar uma página de anúncios para o VTEX Sales App, siga os passos abaixo
     * **Título da vitrine:** nome da vitrine que  será exibido na página.
     * **ID do produto:** número identificador do produto que você deseja exibir. Campo obrigatório.
     * **SKU ID do produto:** número identificador do  SKU do produto que você deseja exibir. Campo opcional.
-![vitrine-produto-pt](https://images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/6a0001784a5ba632dfa4a39078e5293a/image.png)
+![vitrine-produto-pt](//images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/6a0001784a5ba632dfa4a39078e5293a/image.png)
 Após preencher os campos, será exibido a imagem do produto com o preço com a "partir de". Caso você inclua o SKU, será exibido o preço e promoção do SKU indicado. Você pode incluir mais produtos clicando em `+ NOVO PRODUTO`. É possível adicionar até 10 produtos em cada vitrine. 
 O resultado da vitrine de produtos será exibido conforme imagem abaixo.
-![vitrine-produto-2-pt](https://images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/df73bbed63b08096c0d2269918d11731/image.png)
+![vitrine-produto-2-pt](//images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/df73bbed63b08096c0d2269918d11731/image.png)
   - **Vitrine de resultado de buscas:** exibirá produtos de um resultado de busca que você definir. Adicione as  seguintes informações:
     * **Título da vitrine:** nome da vitrine que  será exibido na página.
     * **Imagem da busca:** imagem que representará a seleção de produtos na vitrine.
     * **Nome da busca:** nome da busca que será exibido na página.
     * **Termo de busca:** termo de busca que será referência dos produtos.
-![vitrine-busca-pt](https://images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/5c7a481b24a5639cb70fbfc91df13a5d/image.png)
+![vitrine-busca-pt](//images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/5c7a481b24a5639cb70fbfc91df13a5d/image.png)
 Quando o vendedor clicar no termo de busca, ele será direcionado para o resultado de buscas que foi determinado em **Termo de busca**. Você também poderá incluir até 10 buscas em cada vitrine. Veja o resultado na imagem abaixo:
-![vitrine-busca-2-pt](https://images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/ed37b9e0861094d9b2b74c3f28e1a41b/image.png)
+![vitrine-busca-2-pt](//images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/ed37b9e0861094d9b2b74c3f28e1a41b/image.png)
 <ol start="6">
   <li>Depois de criar as seções, clique em <code>Salvar</code>, em seguida, clique em <code>Publicar</code> e <code>Publicar agora</code> para finalizar.</li>
 </ol> 
+- **Vitrine de coleção:** exibirá produtos da coleção que você definir. Adicione as seguintes informações: **Título da vitrine:** nome da vitrine que será exibido na página. **ID da coleção:** número do identificador da coleção que será exibido na página.
+
+![Vitrine-PT](//images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/d83fcc5ea60cc763f33f1cc3bab74c6f/Vitrine-PT.png)
 
 A publicação da vitrine entrará na fila de indexação e estará publicada em torno de alguns  segundos.
 
@@ -87,13 +92,13 @@ A publicação da vitrine entrará na fila de indexação e estará publicada em
 2. Clique no botão <i class="fas fa-cog"></i>. 
 3. Selecione a aba **Código**.
 4. Selecione na aba lateral o arquivo `checkout-instore-custom-js`.
-![checkout-instore-custom-js-file](https://images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/5a409dc3b01459cb8957e398f79a8c42/image.png)
-5. No objeto `window.INSTORE_CONFIG`, adicione a flag `enableExplore: true`.
-![window.INSTORE_CONFIG](https://images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/08b22d0623a7e72a032872e838c114f6/image.png)
+![checkout-instore-custom-js-file](//images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/5a409dc3b01459cb8957e398f79a8c42/image.png)
+5. No objeto `window.INSTORE_CONFIG`, adicione a flag `enableExplore: true,`.
+![window.INSTORE_CONFIG](//images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/08b22d0623a7e72a032872e838c114f6/image.png)
 6. Clique em <i class="fas fa-save"></i> `Salvar`. 
-7. Opcionalmente, você pode determinar que a página inicial do vendedor seja a página de anúncios. Para isso, adicione a flag `initialPage : advertisements` no objeto `window.INSTORE_CONFIG`.
+7. Opcionalmente, você pode determinar que a página inicial do vendedor seja a página de anúncios. Para isso, adicione a flag `initialPage : 'advertisements',` no objeto `window.INSTORE_CONFIG`.
 
-![initialPage : advertisements](https://images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/eaac77cd87a26f72436209229c733fa4/image.png)
+![initialPage : advertisements](//images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/eaac77cd87a26f72436209229c733fa4/image.png)
 
 ## Acessar os anúncios no VTEX Sales App
 
@@ -102,4 +107,4 @@ No VTEX Sales App, o vendedor terá a possibilidade de acessar a página de anú
 * **Página inicial:** se o administrador da loja cadastrou previamente a página de anúncios como a página inicial do vendedor, ao efetuar login na plataforma, o vendedor será direcionado diretamente para a página de anúncios. Essa configuração garante que os vendedores estejam sempre atualizados sobre os anúncios e promoções relevantes, assim que acessarem o sistema.
 * **Menu Explorar:** caso a página de anúncios não seja a página inicial do vendedor, ela ainda pode ser facilmente acessada por meio do menu **Explorar**. Para acessar a página de anúncios, o vendedor deve clicar no menu **Explorar**. Isso levará o vendedor diretamente à página de anúncios, onde poderá visualizar e interagir com os produtos e promoções disponíveis.
 
-![vitrine-sale-app-pt](https://images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/40b0fd419c940ec568889b2cb4f004eb/image.png)
+![vitrine-sale-app-pt](//images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/40b0fd419c940ec568889b2cb4f004eb/image.png)
diff --git a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
new file mode 100644
index 000000000..6b16f7591
--- /dev/null
+++ b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
@@ -0,0 +1,165 @@
+---
+title: 'Anunciar com VTEX Ad Network (Beta)'
+id: 5WoXcJzHc7EQElpPjziqse
+status: PUBLISHED
+createdAt: 2024-04-23T18:57:14.559Z
+updatedAt: 2024-07-30T15:01:46.734Z
+publishedAt: 2024-07-30T15:01:46.734Z
+firstPublishedAt: 2024-04-23T19:16:43.333Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: anunciar-com-vtex-ad-network-beta
+locale: pt
+legacySlug: anunciando-com-vtex-ad-network-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+Com [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), você pode anunciar produtos da sua marca em frentes de lojas VTEX que possuem seu produto no catálogo.
+
+Para começar a anunciar no VTEX Ad Network, você deve entrar em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar a instalação do app __VTEX Ad Network__ na sua conta VTEX.
+
+Se você já é um anunciante do **VTEX Ad Network**, confira neste artigo como você pode gerenciar e acompanhar suas campanhas.
+
+- [Criar uma campanha](#criar-uma-campanha)
+- [Editar uma campanha](#editar-uma-campanha)
+- [Pausar uma campanha](#pausar-uma-campanha)
+- [Pausar um produto](#pausar-um-produto)
+- [Acompanhar suas campanhas](#acompanhar-suas-campanhas)
+- [Visualizar mais detalhes por campanha e produto](#visualizar-mais-detalhes-por-campanha-e-produto)
+
+## Criar uma campanha
+
+Para criar uma [campanha](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanhas), siga os passos abaixo:
+
+<div class = "alert alert-info">
+Atualmente a VTEX disponibiliza um único formato de anúncio: resultados de pesquisa. Saiba mais sobre este <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#formato-de-anuncio">formato de anúncio</a>.
+</div>
+
+1. No Admin VTEX, acesse **Storefront > Ad Network > Campanhas**.
+2. Clique em `Criar Campanha`.
+3. Na seção *Nome da campanha* section, clique no botão de editar <i class="fas fa-pencil-alt"></i>.
+4. Insira o nome que deseja para sua campanha e clique em `Salvar`.
+5. Na seção *Produtos*, clique no botão de editar <i class="fas fa-pencil-alt"></i>.
+6. Selecione os produtos que deseja anunciar por meio de uma das opções a seguir:
+
+   * __Procurar produtos por EAN:__ buscar produtos do seu catálogo por EAN.
+   * __Carregar arquivo:__ enviar um arquivo CSV com uma lista de códigos EAN e lances, conforme [este exemplo](//assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/ca7ebe3a7ac8cc99bd8f9e843a7bdf98/teste-ads.csv). Os EANs são obrigatórios e os lances opcionais no arquivo.
+
+7. Clique em `Salvar`.
+8. Na seção *Orçamento, bid e cronograma*, clique no botão de editar <i class="fas fa-pencil-alt"></i>.
+9. Defina os valores dos lances para cada produto. Você pode definir cada valor individualmente.
+
+  <div class="alert alert-info">
+O lance de um produto é o custo por clique (CPC), valor gasto quando um usuário clica em um anúcio. Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanhas">campanhas</a> e como fuciona o <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#priorizacao-de-anuncios">leilão</a>.
+</div>
+
+10. Clique em `Salvar`.
+11. Defina o orçamento total e a data final da campanha.
+12. Clique em `Salvar`.
+13. Na seção *Cobertura de anúncios*, clique no botão de editar <i class="fas fa-pencil-alt"></i>.
+14. Selecione a cobertura da sua campanha, ou seja, em que lojas deseja exibir os anúncios.
+
+   Por padrão, a VTEX exibe seus anúncios em todas as lojas participantes do VTEX Ad Network que vendem os produtos selecionados na sua campanha.
+
+   Caso não deseje exibir em todas as lojas, marque a opção **Ou escolha seus publishers** e selecione as lojas em que deseja exibir anúncios desta campanha. 
+
+16. Clique em `Salvar`. 
+17. Clique em `Publicar`.
+
+Em alguns minutos, os produtos escolhidos começarão a ser anunciados em locais de destaque de lojas VTEX.
+
+## Editar uma campanha
+
+Uma vez que criou uma campanha, você pode editar todas as suas características. Para fazer isso, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Storefront > Ad Network > Campanhas**.
+2. Clique na linha da tabela correspondente à campanha que deseja editar.
+3. Clique no ícone <i class="fas fa-pencil-alt"></i>.
+4. Altere as informações que deseja.
+5. Clique no ícone <i class="fa-solid fa-check"></i>.
+
+## Pausar uma campanha
+
+Você pode pausar campanhas, fazendo com que os anúncios correspondentes parem de ser exibidos. Caso deseje pausar uma de suas campanhas, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Storefront > Ad Network > Campanhas**.
+2. Na linha correspondente à campanha que deseja pausar, clique em <i class="fas fa-ellipsis-v"></i>.
+3. Clique em `Pausar`.
+
+## Pausar um produto
+
+Você pode pausar um produto específico da sua campanha. Desta forma, o anúncio correspondente deixará de ser exibido. Caso deseje pausar um produto específico em uma de suas campanhas, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Storefront > Ad Network > Campanhas**.
+2. Clique na linha correspondente à campanha que contém o produto que deseja pausar.
+3. Na linha correspondente ao produto que deseja pausar, clique em <i class="fas fa-ellipsis-v"></i>.
+4. Clique em `Pausar`.
+
+## Acompanhar suas campanhas
+
+Na tela inicial do app [VTEX Ad Network](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), você também encontra informações relativas às suas campanhas em andamento.
+
+![vtex_ad_network_create_campaign_PT](//images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/93a50fdced1479a4deea8072a6a9ca6b/vtex_ad_network_create_campaign.png)
+
+Na parte superior, estão dados agregados:
+
+- **Orçamento total:** orçamento total designado para as suas campanhas.
+- **Orçamento gasto:** valor gasto até o momento.
+- **ROAS médio:** média do retorno do investimento em publicidade.
+- **Vendas de anúncios:** receita total das vendas provenientes de anúncios.
+
+Abaixo você encontra uma tabela com informações de cada campanha:
+
+- **Duração:** duração da campanha até o momento.
+- **Impressões:** número de vezes em que anúncios foram impressos na página.
+- **Visualizações:** número de vezes em que anúncios foram de fato visualizados. O VTEX Ad Network considera uma visualização quando há uma impressão de anúncio e, se necessário, o usuário rola a página o suficiente para visualizar 50% da área do anúncio por um segundo.
+- **Cliques:** número de cliques em anúncios. O VTEX Ad Network descarta cliques no mesmo produto caso ocorram em um período menor que um minuto entre si.
+- **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações. 
+- **Pedidos:** número de pedidos provenientes de cliques em anúncios.
+- **Unidades vendidas:** número de unidades de produtos vendidas a partir de anúncios daquela campanha.
+- **Vendas:** receita total de vendas.
+- **ROAS:** retorno sobre investimento em publicidade. 
+- **Orçamento:** orçamento total.
+- **Orçamento restante:** orçamento ainda disponível até o momento.
+
+<div class = "alert alert-info">
+Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#janela-de-atribuicao">atribuição de vendas a anúncios</a>.
+</div>
+
+Você pode filtrar os dados da tabela de acordo com estes filtros:
+
+- **Buscar campanha:** filtre campanhas pelo nome.
+- **Status:** selecione se deseja ver apenas campanhas ativas ou desativadas.
+
+### Visualizar mais detalhes por campanha e produto
+
+Na tabela da tela inicial do app [VTEX Ad Network](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), você também pode clicar na linha referente a uma de suas campanhas para ver dados mais específicos.
+
+- **Visualizações / Cliques:** Visualizações de anúncios e cliques em anúncios.
+- **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações.
+- **Orçamento gasto:** valor gasto até o momento.
+- **ROAS:** retorno do investimento em publicidade.
+- **Receita:** receita das vendas provenientes de anúncios.
+
+Abaixo dos dados agregados você encontra uma tabela com informações sobre o desempenho de cada produto naquela campanha:
+
+- **CPC:** valor gasto quando um usuário clica em um anúcio.
+- **Impressões:** número de vezes em que anúncios foram impressos na página.
+- **Visualizações:** número de vezes em que anúncios foram de fato visualizados. VTEX Ad Network considera uma visualização quando há uma impressão de anúncio e, se necessário, o usuário rola a página o suficiente para visualizar o anúncio.
+- **Cliques:** número de cliques em anúncios.
+- **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações. 
+- **Pedidos:** número de pedidos provenientes de cliques em anúncios.
+- **Unidades vendidas:** número de unidades do produto vendidas a partir de anúncios desta campanha.
+- **Vendas:** receita total de vendas.
+- **ROAS:** retorno sobre investimento em publicidade.
+- **Orçamento restante:** orçamento ainda disponível até o momento.
+
+<div class = "alert alert-info">
+Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#janela-de-atribuicao">atribuição de vendas a anúncios</a>.
+</div>
+
diff --git a/docs/tutorials/pt/affiliates-program-app.md b/docs/tutorials/pt/affiliates-program-app.md
index db8b7c58d..ad2d0a429 100644
--- a/docs/tutorials/pt/affiliates-program-app.md
+++ b/docs/tutorials/pt/affiliates-program-app.md
@@ -40,11 +40,11 @@ O aplicativo cria três tipos de páginas para os afiliados, que dispõem delas
 
 A **página do afiliado** é a URL da loja VTEX que ele compartilha com os clientes. Veja um exemplo na imagem a seguir:
 
-![print_affiliates_url_pt](https://images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/1e1373a555c8f61b2e4b4af691f4246c/affiliate-url.png)
+![print_affiliates_url_pt](//images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/1e1373a555c8f61b2e4b4af691f4246c/affiliate-url.png)
 
 A **página de perfil do afiliado** é uma interface pela qual ele pode acompanhar e gerenciar seus pedidos e comissões. Veja um exemplo na imagem a seguir:
 
-![affiliate_profile_page_pt](https://images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/1d8a0e06794d7ea915fcb3c12154f3a3/affiliate-profile-page.png)
+![affiliate_profile_page_pt](//images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/1d8a0e06794d7ea915fcb3c12154f3a3/affiliate-profile-page.png)
 
 A **página de cadastro** permite que os próprios interessados em se tornar afiliados preencham seus dados para solicitar registro junto a sua loja VTEX.
 
@@ -72,7 +72,7 @@ A página **Gerenciamento de afiliados **permite realizar as seguintes ações:
 - [Visualizar detalhes do afiliado](#visualizar-detalhes-do-afiliado)
 - [Editar afiliado](#editar-afiliado)
 
-![affiliates_management_page_pt](https://images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6bf53421511963ec9f96265646c3c0e5/affiliates_management_page_pt.jpg)
+![affiliates_management_page_pt](//images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6bf53421511963ec9f96265646c3c0e5/affiliates_management_page_pt.jpg)
 
 ### Adicionar afiliado
 
@@ -119,7 +119,7 @@ A página **Gerenciamento de pedidos** permite realizar as seguintes ações:
 - [Exportar lista de pedidos](#exportar-lista-de-pedidos)
 - [Visualizar detalhes do pedido](#visualizar-detalhes-do-pedido)
 
-![orders_management_page_pt](https://images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/ef737b1a333add24b39bad8a1b75d12e/orders_management_page_pt.jpg)
+![orders_management_page_pt](//images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/ef737b1a333add24b39bad8a1b75d12e/orders_management_page_pt.jpg)
 
 ### Acompanhar dashboard
 
@@ -172,7 +172,7 @@ A página **Gerenciamento de comissões** permite realizar as seguintes ações:
 - [Importar comissões](#importar-comissoes)
 - [Fazer o download da última importação](#fazer-o-download-da-ultima-importacao)
 
-![commissions_ management_page_pt](https://images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/edebf47b68608fb0c12200421c79b770/commissions__management_page_pt.jpg)
+![commissions_ management_page_pt](//images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/edebf47b68608fb0c12200421c79b770/commissions__management_page_pt.jpg)
 
 ### Pesquisar comissões
 
diff --git a/docs/tutorials/pt/all-orders.md b/docs/tutorials/pt/all-orders.md
index ba356c4d6..c6d043d15 100644
--- a/docs/tutorials/pt/all-orders.md
+++ b/docs/tutorials/pt/all-orders.md
@@ -3,8 +3,8 @@ title: 'Todos os pedidos'
 id: 2QTduKHAJMFIZ3BAsi6Pi
 status: PUBLISHED
 createdAt: 2022-04-04T21:50:53.330Z
-updatedAt: 2023-03-23T16:27:45.086Z
-publishedAt: 2023-03-23T16:27:45.086Z
+updatedAt: 2023-12-21T14:05:13.862Z
+publishedAt: 2023-12-21T14:05:13.862Z
 firstPublishedAt: 2022-04-04T22:39:11.450Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: lista-de-pedidos-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
+<div class = "alert alert-info">
+É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
+</div>
+
 A página **Todos os Pedidos** permite que lojistas acompanhem os pedidos da sua loja e extraiam informação para uma gestão inteligente do seu negócio. Para acessar a página, no menu do seu Admin VTEX, clique em **Pedidos > Todos os Pedidos**. Nesta página, você pode:
 
 - Conferir métricas de pedidos e vendas.
@@ -24,7 +28,14 @@ A página **Todos os Pedidos** permite que lojistas acompanhem os pedidos da sua
 
 A seguir exploraremos os componentes e ações incluídos na página.
 
-![Order Listing EN](https://images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/90dad9da099d53164009d4a428d2f731/Order_Listing_EN.gif)
+![Order Listing EN](//images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/90dad9da099d53164009d4a428d2f731/Order_Listing_EN.gif)
+
+Além de pesquisar pedidos em **Pedidos > Todos os pedidos**, você pode buscar pedidos a partir de qualquer página no Admin VTEX usando a barra de busca global no topo da página. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
 
 ## Barra superior
 
@@ -153,7 +164,7 @@ Confira a seguir mais detalhes sobre cada coluna:
 
 ## VTEX DO
 
-![VTEX Do overview PT](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
+![VTEX Do overview PT](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
 
 O [VTEX DO](https://help.vtex.com/pt/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu) é um gerenciador de tarefas criadas automaticamente pelo Admin VTEX, que requerem uma ação manual da equipe de ecommerce. 
 
diff --git a/docs/tutorials/pt/amaro-integration.md b/docs/tutorials/pt/amaro-integration.md
new file mode 100644
index 000000000..67bcb3a5b
--- /dev/null
+++ b/docs/tutorials/pt/amaro-integration.md
@@ -0,0 +1,107 @@
+---
+title: 'Integração com a AMARO'
+id: 7615C3U8EHbxbVw82D9pH8
+status: PUBLISHED
+createdAt: 2023-09-20T21:43:42.533Z
+updatedAt: 2024-01-05T19:46:36.030Z
+publishedAt: 2024-01-05T19:46:36.030Z
+firstPublishedAt: 2023-09-20T22:13:13.268Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: integracao-com-a-amaro
+locale: pt
+legacySlug: integracao-com-a-amaro
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+Fundada em 2012, a [AMARO](https://amaro.com/br/pt/) é uma marca brasileira de varejo digital especializada em moda feminina. Desde 2020, a empresa atua como marketplace por meio de uma curadoria de marcas da própria empresa.
+
+![Integração AMARO](//images.ctfassets.net/alneenqid6w5/2hQ76hgXTPOwEuP4Upq1vO/125a089a5f04ad2f910a6ff3c3f69f7b/Amaro_Logo.png)
+
+A Amaro é agora [conector certificado](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro), disponível para parceria com clientes VTEX. Este guia orienta o seller a configurar a integração, sendo parte do processo no Admin VTEX e parte da AMARO. Para isso, as etapas são as seguintes:
+
+- Configurações de conta na AMARO  
+- Configurações no Admin VTEX   
+- Envio de informações para AMARO  
+
+## Configurações de conta na AMARO
+
+Para vender seus produtos na AMARO, o seller deve cumprir os seguintes pré-requisitos:  
+
+- Ter uma empresa legalmente constituída.  
+- Ter todos os funcionários registrados.  
+- Ter capacidade produtiva interna ou por meio de contratação de terceiros identificados.  
+- Atender aos requisitos do Código de Conduta da AMARO.  
+
+Cumprindo os requisitos citados, o seller deverá entrar em contato com o time de Marcas Parcerias AMARO cadastrando-se no [formulário](https://nocodb.amaro.pro/dashboard/?utm_source=vtex&utm_medium=logo&utm_campaign=hunting#/nc/form/a54bc346-95a0-4497-aceb-5137df1b09c8), ou através do email [sellers@amaro.com](sellers@amaro.com). Com isso, os departamentos de Marcas Parceiras e Compliance avaliarão a solicitação.  
+
+Uma vez aprovada a parceria, o time AMARO disponibilizará a URL do Seller Center AMARO.  
+
+## Configurações no Admin VTEX  
+
+No Admin VTEX, é necessário realizar as seguintes etapas:  
+
+- Definir política comercial  
+- Criar novo AppKey e AppToken  
+- Criar ID do afiliado  
+
+### Definir política comercial  
+
+A [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) é o que determina o sortimento de produtos, preços e estratégia de envio da sua loja VTEX em um canal de venda. Para vender na AMARO, o seller deverá [configurar uma política comercial](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/) para marketplace com um sortimento inicial de produtos, contendo o mínimo de cinco itens com fotografia, preços e estoque disponíveis. 
+Não existe cobrança para a contratação de [políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) para integrar sua loja VTEX com conectores nativos, conectores certificados, tais como a AMARO, ou outras lojas VTEX.  
+
+### Criar novo AppKey e AppToken  
+
+A chave de integração, chamada de AppKey, é o que possibilita o fluxo de envio e atualização de informações entre sua loja VTEX e a AMARO. Somente o [usuário Titular da conta (owner)](https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA?&utm_source=autocomplete) tem permissão para [criar um AppKey e AppToken](https://developers.vtex.com/vtex-rest-api/docs/getting-started-authentication), e a opção só é visível no Admin VTEX para este usuário.  
+
+Para configurar uma nova chave, siga os passos abaixo:  
+
+1. No Admin VTEX, em Configurações da conta, clique em Chaves de aplicação.  
+2. Clique em Gerenciar minhas chaves.  
+3. Clique em Gerar chave.  
+4. Preencha o campo Rótulo com um nome para o novo AppKey.  
+5. Clique em Adicionar perfis e selecione os perfis desejados.  
+6. Clique em Gerar.  
+
+<div class="alert alert-danger">
+  O <i>AppToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
+</div>
+
+### Criar ID do afiliado  
+
+O [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) é o identificador de um seller VTEX em um marketplace, sendo necessário que o seller tenha um ID do afiliado diferente para cada marketplace onde venda seus produtos. Isso significa que, para integrar com a AMARO, é preciso [configurar um afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187) exclusivo.   
+
+Para criar um novo ID do afiliado, siga os passos abaixo:  
+
+1. No Admin VTEX, acesse __Configurações da loja > Pedidos > Configurações__, ou digite __Pedidos__ na barra de busca no topo da página e selecione *Configurações da loja / Pedidos*.  
+2. Na aba Afiliados, clique em +Novo afiliado.
+3. Preencha os campos da tela, descritos abaixo, e em seguida clique em Salvar.
+  - __Nome:__ designação do novo afiliado.  
+  - __ID:__ código identificador do afiliado, deve ser composto de três consoantes, sejam elas repetidas ou não. Vogais não são aceitas. A sugestão é usar MRR para a AMARO.  
+  -__Política Comercial:__ número da política comercial que definirá o sortimento de catálogo, preço e estratégia de envio dos itens utilizados na integração com a AMARO.  
+  - __E-mail de Follow Up:__ endereço eletrônico que receberá notificações sobre a integração.  
+  - __Endpoint de Search:__ URL da aplicação que receberá notificações de produtos, preço, estoque, dentre outras. O seller será informado sobre este dado pela AMARO.  
+  - __Versão do Endpoint de Search:__ só existe a opção padrão 1.x.x.
+Deixe desmarcada a flag Usar meu meio de pagamento.  
+
+## Envio de informações para AMARO  
+
+Uma vez concluídas as configurações na plataforma VTEX, para dar continuidade à integração é necessário enviar os dados de Informações do Admin VTEX para a AMARO. O contato para onde essas informações devem ser enviadas é fornecido pelos próprios parceiros.  
+
+### Informações do Admin VTEX  
+
+Alguns dos dados a serem enviados são encontrados no seu Admin VTEX, são eles:  
+
+-__Nome da conta:__ identificador da sua empresa no sistema da VTEX. Para encontrá-lo, acesse o Admin VTEX em Configurações da conta > Conta > Geral.
+-__Dados de autenticação do sistema:__ *appToken e appKey* definidos na etapa [Criar novo *AppKey e AppToken*](#criar-novo-appkey-e-apptoken).
+-__ID do afiliado:__ identificador configurado na etapa [Criar ID do afiliado](#criar-id-do-afiliado).
+__- Política comercial:__ número da política comercial determinada na etapa [Definir política comercial](#definir-politica-comercial).
+-__ID do Seller:__ o valor a ser informado é o número 1. Para encontrá-lo, acesse o Admin no módulo *Marketplace > Sellers > Gerenciamento > ID do Seller*.  
+
+Uma vez que o seller tenha reunido esses dados, deverá enviá-los para o contato informado pelo time de Marcas Parceiras da AMARO. Desta forma,a integração será concluída pelo marketplace.  
+
+<div class="alert alert-info">
+Após a primeira conexão com o seller center AMARO e verificação inicial do sucesso da integração, o time de Marcas Parceiras AMARO irá orientar o seller a adicionar os demais produtos na política comercial para a etapa final de curadoria e exibição dos itens no amaro.com e aplicativos AMARO.
+</div>
+
diff --git a/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
index 2d85f99d8..9782e35d7 100644
--- a/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
@@ -111,7 +111,7 @@ Para instalar o aplicativo, acesse a App Store VTEX:
 As configurações feitas no campo Automatic Invoice serão aplicadas a todos os pedidos.
 </div>
 
-![MCF](https://images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/7e61a4ea7adc5595f583f55dd644b99d/Amazon_MCF_PT.PNG)
+![MCF](//images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/7e61a4ea7adc5595f583f55dd644b99d/Amazon_MCF_PT.PNG)
 
 ### Integração do catálogo
 
diff --git a/docs/tutorials/pt/amazon-offer-matching.md b/docs/tutorials/pt/amazon-offer-matching.md
index a6bd5a89f..151206b0a 100644
--- a/docs/tutorials/pt/amazon-offer-matching.md
+++ b/docs/tutorials/pt/amazon-offer-matching.md
@@ -1,10 +1,10 @@
 ---
-title: 'Match de anúncios Amazon (Beta)'
+title: 'Match de anúncios Amazon'
 id: 7fRfoP69kYgg8znImMhyQ0
 status: PUBLISHED
 createdAt: 2023-05-29T15:07:38.220Z
-updatedAt: 2023-05-29T16:59:25.926Z
-publishedAt: 2023-05-29T16:59:25.926Z
+updatedAt: 2023-07-27T21:32:07.360Z
+publishedAt: 2023-07-27T21:32:07.360Z
 firstPublishedAt: 2023-05-29T16:38:11.840Z
 contentType: tutorial
 productTeam: Channels
@@ -12,14 +12,14 @@ author: 2p7evLfTcDrhc5qtrzbLWD
 slug: match-de-anuncios-amazon
 locale: pt
 legacySlug: match-de-anuncios-amazon
-subcategory: 4YvjazdRUhQzjHJ53FCYJM
+subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
 Toda vez que um [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) com [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) cadastrado na VTEX é enviado para a Amazon, o marketplace realiza um processo chamado *matching*, que consiste em unificar anúncios de um mesmo produto através do seu EAN.  
 
 O EAN cadastrado na VTEX é utilizado para fazer a equivalência com os [ASINs](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (*Amazon Standard Identification Number, ou, Número de Identificação Padrão da Amazon*) correspondentes na Amazon. Para realizar o pareamento entre o EAN e o ASIN, é necessário realizar o matching manual. A correspondência entre EAN e ASINs precisa ser exata para que os anúncios sejam vinculados corretamente.   
 
-![Match Amazon PT](https://images.ctfassets.net/alneenqid6w5/2w6NrOhlTwsknC27Soe0pr/a3a3da7039a2bbbaff057380c368a124/https___daniel--grocery1.myvtex.com_admin_vtex_integration-amazon-sku-matcher.gif)
+![Overview match de anúncios](//images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/61c986c2318575171d6f248e70aa7f15/Match-an__ncios-Amazon.gif)
 
 ## Aba Oportunidade  
 Na aba __Oportunidade__, o seller pode realizar o match dos produtos enviados à Amazon individualmente ou em massa, realizar busca por nome do produto e clicando no ícone <i class="fas fa-ellipsis-v"></i> o seller poderá escolher entre `ver detalhes` dos produtos e `ver anúncio` do produto correspondente na Amazon. 
@@ -56,22 +56,42 @@ Conheça abaixo a estrutura da aba.
   - Nome do produto  
   - Marca  
 
-## Como realizar o matching manual dos produtos  
+## Fazendo matching manual dos produtos  
 
 Após o [envio](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD), os produtos estarão disponíveis na página __Match de anúncios Amazon__. Para visualizar os anúncios não aprovados, acesse o Admin VTEX, clique em *Marketplace >*__Match de anúncios Amazon__ ou use a barra de busca no topo da página.  
 
+### Match individual de anúncios  
+
+Na aba de `Oportunidade`, cada produto listado apresenta o ícone <i class="fas fa-ellipsis-v"></i>, ao clicar nele, o seller verá dois botões, `ver detalhes` e `ver anúncio sugerido`, em ambos, ele será redirecionado a novas páginas, uma para o match individual do produto e outra para ver o anúncio sugerido publicado no site da Amazon respectivamente. 
+Veja os botões disponíveis em cada uma das páginas e suas ações.  
+
+- **Botão `Rejeitar`:** esse botão irá excluir a sugestão de match e o seller deverá enviar novamente o seu produto caso queira, seguindo o [tutorial de envio de produtos](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD).  
+- **Botão `Rejeitar e solicitar revisão`:** se o seller não concorda com a sugestão de match e quer pedir revisão à Amazon, deverá escolher essa opção. Ao clicar nesse botão o seller será enviado para a página de abertura de chamados na Amazon e a sugestão de match irá sair da lista de oportunidade.
+O acompanhamento dessa revisão deve ser realizado pelo painel de chamados da Amazon.  
+- **Botão `Publicar`:** Se o seller está de acordo com a sugestão proposta pela Amazon, basta clicar no botão `Publicar`.  
+
+Para aprovar a correspondência o seller deve seguir os passos abaixo.
+
+1. Na aba `Oportunidade`, clique no ícone <i class="fas fa-ellipsis-v"></i>. 
+2. Clique no botão `Ver detalhes`.  
+3. Confira as informações que aparecerão na página.  
+![Match individual de anúncios](//images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/1ecb1d4de4389b5a6794d7e899fa4712/Match_individual_AMZ.png)  
+4. Conforme a análise das informações, clique em um dos botões disponíveis, `Publicar`, `Rejeitar e solicitar revisão` ou `Rejeitar`.
+
+### Match massivo de anúncios  
+
 Na aba de `Oportunidade`, todos os produtos listados que possuem equivalência entre Seu anúncio e Sugestão Amazon, precisam ser aprovados manualmente. Para aprovar as correspondências de SKU e ASIN, siga os passos abaixo.  
 
 1. Na aba `Oportunidade`, marque a caixa de seleção ao lado do título dos anúncios com equivalência SKU <> ASIN.  
 Ao selecionar os produtos, aparecerá na tela o seguinte pop-up mostrando quantos produtos foram selecionados.
 
-![popup seleção mtach Amazon](https://images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/7cf1452afbaa25640210af435d2e0f8b/popup_sele____o_PT.png)
+![popup seleção mtach Amazon](//images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/7cf1452afbaa25640210af435d2e0f8b/popup_sele____o_PT.png)
 
 2. Ao finalizar a seleção de produtos, clique em  `Publicar selecionados`.  
 
 3. No pop-up de confirmação do *matching*, confira os anúncios selecionados e clique em `Confirmar publicação`.  
 
-![confirmação do matching Amazon](https://images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4a3cd9f22575382fb03d4c8aab476048/confirma____o_do_matching_PT.png)
+![confirmação do matching Amazon](//images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4a3cd9f22575382fb03d4c8aab476048/confirma____o_do_matching_PT.png)
 
 Quando confirmado, os seus anúncios serão enviados e enfileirados para processamento. Após aprovado, o anúncio aparecerá na aba __Anúncios__, onde você pode __“ver detalhes do seu anúncio”__, __“ver anúncio sugerido pela Amazon”__ e __pesquisar anúncios__ na barra de busca.  
 
diff --git a/docs/tutorials/pt/analytics.md b/docs/tutorials/pt/analytics.md
new file mode 100644
index 000000000..d70b6f16a
--- /dev/null
+++ b/docs/tutorials/pt/analytics.md
@@ -0,0 +1,87 @@
+---
+title: 'Analytics'
+id: 6qRMAHDL9hvv3oE0bh8mA1
+status: PUBLISHED
+createdAt: 2024-06-27T16:53:32.304Z
+updatedAt: 2024-06-27T16:54:23.587Z
+publishedAt: 2024-06-27T16:54:23.587Z
+firstPublishedAt: 2024-06-27T16:54:23.587Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: analytics
+locale: pt
+legacySlug: analytics
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+**Analytics** é uma página do VTEX Intelligent Search que organiza os dados relacionados às pesquisas realizadas na loja e possibilita exportar esses dados em um arquivo CSV.
+
+A partir dessas informações, você tem visibilidade sobre o desempenho dos resultados de busca e dos termos de pesquisa do [Autocomplete](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4gXFsEWjF7QF7UtI2GAvhL?&utm_source=autocomplete) e poderá realizar ações para melhorar o desempenho, como criar um redirecionamento ou cadastrar um novo sinônimo.
+
+Siga os passos abaixo para acessar a página:
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Em __Intelligent Search__, clique em __Analytics__. 
+
+<div class = "alert alert-info">
+<p>A página de <strong>Analytics</strong> é nativa no VTEX Intelligent Search. Não é possível desabilitá-la no Admin.</p>
+</div>
+
+## Dados
+
+Os dados que compõem o relatório são atualizados a cada quatro horas e contêm as seguintes informações:
+
+* **Termos**: conteúdo das buscas realizadas.
+* **Buscas**: número de buscas realizadas para um termo específico. Quando o cliente pesquisa um termo na loja e clica em outra página ou atualiza a página, também é contabilizada uma busca.
+* **Cliques**: quantidade total de cliques em resultados de busca por um termo.
+* **Cliques únicos**: quantidade de cliques em resultados de busca por um termo, excluindo cliques repetidos de um único usuário. Indica a quantidade de pessoas que clicaram em determinado resultado a partir da busca.
+* **CTR**: significa Click-Through Rate, ou seja, a taxa de cliques em razão do total de buscas. O cálculo dessa taxa é feito da seguinte forma: `(Cliques/Buscas) * 100`
+* **Conversão**: taxa de conversão dos termos pesquisados. O cálculo da conversão segue a fórmula: `(Pedidos/Cliques únicos) * 100`. É possível que a taxa de conversão seja acima de 100%, pois é levada em consideração a quantidade de pedidos efetuados entre cliques, por exemplo, é possível que o usuário faça mais de um pedido utilizando o termo camiseta, dessa forma, a conversão seria maior do que 100%.
+* **Pedidos**: quantidades de pedidos realizados a partir da busca. Para calcular essa métrica, consideramos que a busca gera um pedido sempre que, após buscar por um termo, o cliente clica em algum produto que aparece nos resultados e depois compra um produto qualquer (não necessariamente o que ele clicou).
+* **Vendas**: valor total de receitas geradas por pedidos realizados a partir da busca. O cálculo segue a mesma lógica da métrica de **Pedidos**, a diferença é que o resultado reflete as receitas em vez da quantidade de pedidos.
+
+<div class="alert alert-info">
+  <p>Os dados exibidos no relatório são limitados aos 10 mil termos mais pesquisados. Caso deseje os dados completos da busca da sua loja, é necessário <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacao">exportar o relatório</a>.</p>
+</div>
+
+Quando você optar por [exportar um relatório](#exportacao), existe também a possibilidade de gerá-lo **Com métricas de funil**. Caso essa opção seja selecionada, quatro novas colunas serão adicionadas ao arquivo:
+
+*   **ProductClicks**: dado um termo pesquisado, essa coluna mostra as IDs dos produtos clicados e o número de cliques que ocorreram, respectivamente. Por exemplo:`3378|1`; `3659|2`; `4038|3` significa que o produto cuja ID é 3378 foi clicado 1 vez, o produto com ID 3659 foi clicado 2 vezes e o produto com ID 4038 foi clicado 3 vezes.
+*   **PositionClickAverage**: dado um termo pesquisado, essa coluna apresenta as IDs dos produtos que foram clicados e sua posição média na lista de resultados, respectivamente. Por exemplo: `4321|1` significa que o produto cuja ID é 4321 tem o primeiro lugar como posição média na lista de resultados de busca.
+*   **ProductsAddToCart**: dado um termo pesquisado, essa coluna apresenta as IDs dos produtos que foram adicionados ao carrinho e a quantidade adicionada, respectivamente. Por exemplo: `3380|1`; `3910|2` significa que 1 unidade do produto cuja ID é 3380 foi adicionada ao carrinho e que 2 unidades do produto com ID 3910 foram adicionadas ao carrinho.
+*   **ProductsSold**: dado um termo pesquisado, essa coluna apresenta as IDs dos produtos que foram vendidos e a quantidade vendida, respectivamente. Por exemplo: `3500|1` significa que 1 unidade do produto cuja ID é 3500 foi vendida.
+
+## Filtros
+
+Como opção para restringir os dados, a tela **Analytics** permite uma combinação de critérios. Veja abaixo quais são as opções de filtros disponíveis:
+
+* **Busca** ou **Autocomplete**
+* **Com resultados** ou **Sem resultados**: optar entre buscas que obtiveram resultados ou não.
+* **Todos**, **Celular** ou **Computador**: limitar os dispositivos em que as buscas foram realizadas.
+* **Hoje**, **Ontem**, **Últimos 7 dias**, **Últimos 30 dias** e **Personalizar**: selecionar o período para análise. A opção **Personalizar** permite inserir datas de início e fim a serem consideradas.
+
+A página **Analytics** exibe apenas informações de um intervalo de um mês. Caso deseje acessar dados de um período de até 6 meses, é preciso [exportá-los em um arquivo no formato CSV](#exportacao).
+
+## Exportação
+
+Para exportar um relatório no formato CSV, você deve seguir os passos abaixo.
+
+1. Na página **Storefront** > **Intelligent Search** > **Analytics**, clique no botão `Exportar`.
+2. Configure os filtros do relatório a ser gerado.
+3. Escolha se deseja marcar a opção **Com métricas de funil** ou não. Caso selecionada, essa opção acrescenta as [colunas **ProductsClick**, **PositionClickAverage**, **ProductsAddToCart** e **ProductsSold**](#dados) ao arquivo, correlacionando informações sobre quantidades de cliques e vendas às IDs dos produtos buscados.
+4. Em seguida, clique em `Exportar`.
+5. Espere o arquivo estar disponível para download. Sair desta página não interrompe o processo.
+6. Clique em `Baixar`.
+
+<div class = "alert alert-info">
+<p>O arquivo permanece disponível para download por 48 horas.</p>
+</div>
+
+O relatório CSV baixado apresenta duas tabelas. A primeira tabela, ilustrada abaixo, contém informações sobre termos pesquisados e as métricas de funil (da coluna **ProductsClick** até a coluna **ProductsSold**), caso essa opção tenha sido selecionada.
+
+![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
+
+A segunda tabela, ilustrada abaixo, mostra dados referentes ao período selecionado, exibindo a coluna Date, que informa a data da busca.
+
+![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
diff --git a/docs/tutorials/pt/analyze-suiteshare.md b/docs/tutorials/pt/analyze-suiteshare.md
index 5a15f4b3f..750cb1f6e 100644
--- a/docs/tutorials/pt/analyze-suiteshare.md
+++ b/docs/tutorials/pt/analyze-suiteshare.md
@@ -23,11 +23,11 @@ Para começar a utilizar o “**Analisar**” você precisa ter pelo menos um li
 
 Acesse dentro do painel da **VTEX Assisted Sales (SuiteShare)** a opção de _**“Analisar”**_. 
 
-![Analisar 1](https://images.ctfassets.net/alneenqid6w5/XOt7xPapUQ3iYaRLYsQQK/c3c07991814af5cc1e22cebabae6fe87/image.png)
+![Analisar 1](//images.ctfassets.net/alneenqid6w5/XOt7xPapUQ3iYaRLYsQQK/c3c07991814af5cc1e22cebabae6fe87/image.png)
 
 Acessando o painel, você terá as seguintes opções:
 
-![Analisar 2](https://images.ctfassets.net/alneenqid6w5/48TT5uIth5qpUc2DG9cVWV/be55b7a75b930988a13125ca54337577/image.png)
+![Analisar 2](//images.ctfassets.net/alneenqid6w5/48TT5uIth5qpUc2DG9cVWV/be55b7a75b930988a13125ca54337577/image.png)
 
 **1 Geral:** Uma análise geral de todos os links criados na sua conta sem diferenciar por links.
 
@@ -43,30 +43,30 @@ Clicando em geral ou no link você terá o seguinte relatório: 
 
 ## Opção de filtrar por período
 
-![Analisar 3](https://images.ctfassets.net/alneenqid6w5/1tMhqp6iaxzBHrB6PBJdKH/3532a9535d8592409b681ea22af5a06a/Screenshot_2022-08-30_at_15-49-58_Analisar.png)
+![Analisar 3](//images.ctfassets.net/alneenqid6w5/1tMhqp6iaxzBHrB6PBJdKH/3532a9535d8592409b681ea22af5a06a/Screenshot_2022-08-30_at_15-49-58_Analisar.png)
 
 **Estatísticas total, mês, semana e dia.** 
 
-![Analisar 4](https://images.ctfassets.net/alneenqid6w5/2DZluzvUBtUoMY9wUdjwUF/0c2e372fdf47e2dc242a8b9d0eed8cc0/Screenshot_2022-08-30_at_15-50-06_Analisar.png)
+![Analisar 4](//images.ctfassets.net/alneenqid6w5/2DZluzvUBtUoMY9wUdjwUF/0c2e372fdf47e2dc242a8b9d0eed8cc0/Screenshot_2022-08-30_at_15-50-06_Analisar.png)
 
 E o Tracking que está relacionado aos períodos. Você mudando os períodos altera o gráfico abaixo.
 
-![Analisar 5](https://images.ctfassets.net/alneenqid6w5/3rX7ajgRqtwoN4nOUHSRDq/55f816b883428504ef08f0d6a0037c07/Screenshot_2022-08-30_at_15-50-11_Analisar.png)
+![Analisar 5](//images.ctfassets.net/alneenqid6w5/3rX7ajgRqtwoN4nOUHSRDq/55f816b883428504ef08f0d6a0037c07/Screenshot_2022-08-30_at_15-50-11_Analisar.png)
 
 **Você também tem o relatório geográfico dividido por Países, Estados e Cidades.** 
 
-![Analisar 6](https://images.ctfassets.net/alneenqid6w5/5RfLQis64rfCy3ANOqhJPP/48f8adc0ecf35cffb1f5f692bb61142b/Screenshot_2022-08-30_at_15-50-15_Analisar.png)
+![Analisar 6](//images.ctfassets.net/alneenqid6w5/5RfLQis64rfCy3ANOqhJPP/48f8adc0ecf35cffb1f5f692bb61142b/Screenshot_2022-08-30_at_15-50-15_Analisar.png)
 
 **Referência de onde veio os cliques** - Sites (domínios) onde os seus clientes viram seus links e clicaram (aqui você descobrirá qual rede social ou canal de aquisição que você compartilhou os seus link ou utiliza seu chat e está tendo melhor conversão). Agora também é possível monitorar os acessos via QRcode.
 
-![Analisar 7](https://images.ctfassets.net/alneenqid6w5/1a0BpP3gTuD31CCkWLP5tJ/033e1a5fcc4df17b3fb1eee67eac5c7d/Screenshot_2022-08-30_at_15-50-21_Analisar.png)
+![Analisar 7](//images.ctfassets.net/alneenqid6w5/1a0BpP3gTuD31CCkWLP5tJ/033e1a5fcc4df17b3fb1eee67eac5c7d/Screenshot_2022-08-30_at_15-50-21_Analisar.png)
 
 **Páginas URL de onde vieram os acessos** - Inclusive os QRcodes. 
 
-![Analisar 8](https://images.ctfassets.net/alneenqid6w5/4aoekMLr0yXq1ip706jHbm/1c014e91910e44276d0722b0b86b7fe4/Screenshot_2022-08-30_at_15-50-25_Analisar.png)
+![Analisar 8](//images.ctfassets.net/alneenqid6w5/4aoekMLr0yXq1ip706jHbm/1c014e91910e44276d0722b0b86b7fe4/Screenshot_2022-08-30_at_15-50-25_Analisar.png)
 
 - **Navegadores** (Chrome, Firefox, Safari e etc) e **Dispositivos** (Desktop - Windows, Macbook, Mobile - Android e IOS) utilizados pelos usuários.
 
-![Analisar 9](https://images.ctfassets.net/alneenqid6w5/1kIISQHtXhbUYfzARwmUvP/55d79bc433500613da6dc478969de56f/Screenshot_2022-08-30_at_15-50-29_Analisar.png)
+![Analisar 9](//images.ctfassets.net/alneenqid6w5/1kIISQHtXhbUYfzARwmUvP/55d79bc433500613da6dc478969de56f/Screenshot_2022-08-30_at_15-50-29_Analisar.png)
 
 Pronto, agora você já sabe analisar os seus dados.
diff --git a/docs/tutorials/pt/anapro-suiteshare.md b/docs/tutorials/pt/anapro-suiteshare.md
index 065b94eb9..6b3bc0f9e 100644
--- a/docs/tutorials/pt/anapro-suiteshare.md
+++ b/docs/tutorials/pt/anapro-suiteshare.md
@@ -21,7 +21,7 @@ Para realizar a integração acesse no seu painel da Suiteshare as integrações
 
 Na dashboard em **“Integrações”**.
 
-![Anapro 1](https://images.ctfassets.net/alneenqid6w5/5Rx0RJ9BWA8p57KcBZcUSL/0c3e8ca37ea8e9cea03e89393101d19a/Screenshot_2022-08-31_at_14-42-19_Anapro.png)
+![Anapro 1](//images.ctfassets.net/alneenqid6w5/5Rx0RJ9BWA8p57KcBZcUSL/0c3e8ca37ea8e9cea03e89393101d19a/Screenshot_2022-08-31_at_14-42-19_Anapro.png)
 
 Ou clique em _**"configurações > Integrações"**_.
 
@@ -29,15 +29,15 @@ Em vendas, selecione **Anapro CRM** e clique em **“habilitar"**.
 
 O próximo passo é acessar sua conta da **Anapro** e fazer login:
 
-![Anapro 2](https://images.ctfassets.net/alneenqid6w5/27nMiiFZJwLcoZnKWUwrLc/7e2684133221c84007617fea997561d3/Screenshot_2022-08-31_at_14-42-30_Anapro.png)
+![Anapro 2](//images.ctfassets.net/alneenqid6w5/27nMiiFZJwLcoZnKWUwrLc/7e2684133221c84007617fea997561d3/Screenshot_2022-08-31_at_14-42-30_Anapro.png)
 
 Agora, acesse o menu  **_"Configurações>Campanhas"_**.
 
-![Anapro 3](https://images.ctfassets.net/alneenqid6w5/5xLCEcL4Edbf0X6wVo8k9E/d56c880d56fb273673d9899cd9cead2d/Screenshot_2022-08-31_at_14-42-35_Anapro.png)
+![Anapro 3](//images.ctfassets.net/alneenqid6w5/5xLCEcL4Edbf0X6wVo8k9E/d56c880d56fb273673d9899cd9cead2d/Screenshot_2022-08-31_at_14-42-35_Anapro.png)
 
 Escolha a campanha da qual deseja gerar os links , clique em **"Editar"** e vá na aba **"Integração"**.
 
-![Anapro 4](https://images.ctfassets.net/alneenqid6w5/SN8dBsn48blUAbY3D5A8E/840181abb9bb1a35961329dcb94248b9/Screenshot_2022-08-31_at_14-42-41_Anapro.png)
+![Anapro 4](//images.ctfassets.net/alneenqid6w5/SN8dBsn48blUAbY3D5A8E/840181abb9bb1a35961329dcb94248b9/Screenshot_2022-08-31_at_14-42-41_Anapro.png)
 
 Na tela de **integração**, selecione a Empresa integradora e a Agência (Agente responsável pela geração do lead. Pode ser a própria incorporadora ou a Agência de marketing).
 
@@ -51,6 +51,6 @@ Agora que você tem acesso aos chaves, basta selecionar o link que deseja integr
 
 Selecione o link de captura que deseja integrar com o CRM:
 
-![Anapro 5](https://images.ctfassets.net/alneenqid6w5/4oxPYJKk1ZwYJ55JOHB4JE/171a1bdd5065e46a69addcd3eabf2c66/Screenshot_2022-08-31_at_14-42-47_Anapro.png)
+![Anapro 5](//images.ctfassets.net/alneenqid6w5/4oxPYJKk1ZwYJ55JOHB4JE/171a1bdd5065e46a69addcd3eabf2c66/Screenshot_2022-08-31_at_14-42-47_Anapro.png)
 
 Agora preencha todos os outros campos, e pronto, aproveite a integração!
diff --git a/docs/tutorials/pt/antifraud-provider.md b/docs/tutorials/pt/antifraud-provider.md
index 1aff25212..27ae1778a 100644
--- a/docs/tutorials/pt/antifraud-provider.md
+++ b/docs/tutorials/pt/antifraud-provider.md
@@ -46,14 +46,14 @@ Antes de configurar o ambiente VTEX, o provedor deve implementar o serviço back
 ### 3. Portal de administração do Antifraud Provider
 Depois de receber os dados de acesso e implementar o back-end, o provedor pode acessar a ferramenta de aprovação por meio do Admin da VTEX. Para fazer isso, você deve intalar a App do Antifraud Provider no menu Apps:
 
-![print5](https://images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
+![print5](//images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
 
 Clique na App instalada ou acesse `https://{{AccountName}}.myvtex.com/admin/antifraud-provider`, substituindo `{{AccountName}}` pelo nome da sua conta na plataforma. Nesse ambiente, é possível registrar os dados de configuração do back-end do provedor e fazer testes de integração.
 
-![print6](https://images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
+![print6](//images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
 
 ### 4. Configurações iniciais
-![print1](https://images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
+![print1](//images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
 
 Ao acessar  o ambiente pelo link descrito no item anterior, você verá um formulário. Preencha os campos de acordo com as indicações abaixo:
 
@@ -77,7 +77,7 @@ Depois de preencher os campos corretamente, o sistema vai verificar as transaç
 
 Os testes que deverão ser feitos na sua integração antes de mandá-la para a avaliação da VTEX são exibidos no módulo seguinte. Você pode selecionar quais testes deseja rodar, mas para que sua integração passe pela análise da nossa equipe, __todos eles precisam ser realizados__. Portanto, recomendamos que todos eles permaneçam selecionados.
 
-![print2](https://images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
+![print2](//images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
 
 ### 5. Testes
 Ao clicar no botão __Execute tests__, o Antifraud Provider vai aplicar os testes na sua integração para os diferentes cenários possíveis. É importante lembrar que __todos eles são obrigatórios__ e, para executá-los, seu serviço precisa estar em HTTPS. Os testes são:
@@ -107,11 +107,11 @@ Para cada teste do Antifraud Provider Protocol, enviamos um final de ID específ
 ### 6. Resultados
 Depois de executar os testes, o sistema retorna os resultados, tanto positivos quanto negativos. O sistema também traz a informação dos resultados esperados para cada teste. Assim, você tem mais visibilidade do que deve ser ajustado em caso de erro.
 
-![print3](https://images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
+![print3](//images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
 
 Para visualizar de forma detalhada cada ação realizada pela integração (e, assim, identificar possíveis erros), basta clicar no link __Show logs__. Uma lista com as informações completas dos eventos que aconteceram durante o teste vai ser exibida abaixo dos resultados.
 
-![print4](https://images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
+![print4](//images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
 
 Quando sua integração tiver passado em todos os testes com sucesso, basta abrir um ticket no [Help da VTEX](https://help.vtex.com/pt/support "VTEX Help") informando a conclusão. Porém, antes de abrir o ticket, certifique-se que você possui as seguintes informações:
 
@@ -135,7 +135,7 @@ Use a URL `https://{{AccountName}}.myvtex.com/admin/license-manager/#/home`, sub
 Depois que a integração com seu antifraude estiver aprovada, um conector será disponibilizado para que os lojistas VTEX o configurem em seus respectivos websites. Para fazer isso, além do contrato com sua empresa, o lojista vai precisar ter em mãos duas chaves: "X-PROVIDER-API-AppKey" e "X-PROVIDER-API-AppToken". 
 
 Um exemplo de como vai ficar a tela de configuração do antifraude para o lojista VTEX:
-![print8](https://images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
+![print8](//images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
 
 Essas chaves devem ser disponibilizadas por você e vão servir para identificar a loja que contratou e está usando seu serviço de antifraude.
 
diff --git a/docs/tutorials/pt/application-keys.md b/docs/tutorials/pt/application-keys.md
index 5a84465b5..07266f570 100644
--- a/docs/tutorials/pt/application-keys.md
+++ b/docs/tutorials/pt/application-keys.md
@@ -3,134 +3,169 @@ title: 'Chaves de aplicação'
 id: 2iffYzlvvz4BDMr6WGUtet
 status: PUBLISHED
 createdAt: 2021-08-19T17:45:31.084Z
-updatedAt: 2022-11-25T18:39:48.683Z
-publishedAt: 2022-11-25T18:39:48.683Z
+updatedAt: 2023-10-17T20:17:39.441Z
+publishedAt: 2023-10-17T20:17:39.441Z
 firstPublishedAt: 2021-08-19T18:08:07.096Z
 contentType: tutorial
 productTeam: Identity
-author: 56yU9Wz6mLwmzo82TjgAHy
+author: 1malnhMX0vPThsaJaZMYm2
 slug: chaves-de-aplicacao
 locale: pt
 legacySlug: chaves-de-aplicacao
 subcategory: 5GYFjiMQg0qIKpnnQY2qjh
 ---
 
-Para cada integração via API utilizada para conectar sua conta VTEX com sistemas externos, será necessária a criação de uma chave de aplicação (também conhecida em inglês como _application key_ ou _app key_). Estas credenciais de [autenticação](https://developers.vtex.com/vtex-rest-api/docs/getting-started-authentication) são usadas para garantir o acesso seguro aos dados que você deseja compartilhar com as integrações, sem expor sua conta a aplicações ou usuários não autorizados.
+Para cada integração via API utilizada para conectar sua conta VTEX com sistemas externos, será necessária a criação de uma chave de aplicação (também conhecida em inglês como _application key_ ou _app key_).
 
-Na página  **Chaves de aplicação** você pode gerenciar as chaves de aplicação [internas](#chaves-de-aplicacao-internas) e [externas](#chaves-de-aplicacao-externas) que têm acesso à sua conta, inclusive:
+Estas credenciais de [autenticação](https://developers.vtex.com/docs/guides/authentication) são usadas para garantir o acesso seguro aos dados que você deseja compartilhar com as integrações, sem expor sua conta a aplicações ou usuários não autorizados.
 
-- [Gerar chaves de aplicação na sua conta](#gerar-chaves-de-aplicacao-na-sua-conta)
+## Tipos de chaves de aplicação
+
+Existem dois tipos de chaves de aplicação: [internas](#chaves-de-aplicacao-internas) ou [externas](#chaves-de-aplicacao-externas). Essa definição depende de qual conta cria, gerencia e utiliza a credencial.
+
+### Chaves de aplicação internas
+
+As chaves de aplicação internas são credenciais geradas e administradas por sua conta VTEX. Isso significa que você deve ter acesso a todos os pares de chaves e tokens de aplicação — o equivalente a nomes de usuário e senhas para integrações de API.
+
+### Chaves de aplicação externas
+
+As chaves de aplicação externas são credenciais geradas e administradas por outras contas VTEX. Ao adicionar [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) às chaves de aplicação — o equivalente a nomes de usuário — fornecidas por terceiros, você pode permitir que eles acessem recursos específicos na sua conta.
+
+## Gerenciar chaves de aplicação
+
+<div class="alert alert-warning">
+  <p>É necessário ter um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> com o <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <strong>Save User</strong> para gerenciar usuários e chaves de aplicação. O perfil predefinido para essa finalidade é o <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, mas também é possível <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso">criar um perfil de acesso customizado</a> com esse recurso.</p>  
+</div>
+
+Na página **Chaves de aplicação**, você pode gerenciar as chaves de aplicação [internas](#chaves-de-aplicacao-internas) e [externas](#chaves-de-aplicacao-externas) que têm acesso à sua conta, inclusive:
+
+- [Gerar chaves de aplicação internas](#gerar-chaves-de-aplicacao-internas)
+- [Adicionar chaves de aplicação externas](#adicionar-chaves-de-aplicacao-externas)
 - [Gerenciar permissões das chaves de aplicação](#gerenciar-permissoes-de-chaves-de-aplicacao)
 - [Ativar ou desativar chaves de aplicação](#ativar-ou-desativar-chaves-de-aplicacao)
 - [Exportar chaves de aplicação com acesso à sua conta](#exportar-chaves-de-aplicacao-com-acesso-a-sua-conta)
 
-Para visualizar essa página, acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_.
+Para visualizar essa página, na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
 
 <div class = "alert alert-info">
-  Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/best-practices-application-keys--7b6nD1VMHa49aI5brlOvJm">Boas práticas na utilização de chaves de aplicação</a>.
+<p>Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm">Boas práticas na utilização de chaves de aplicação</a>.</p>
 </div>
 
-## Tipos de chaves de aplicação
-
-### Chaves de aplicação internas
+## Gerar chaves de aplicação internas
 
-As chaves de aplicação internas são credenciais geradas e administradas por sua conta VTEX. Isso significa que você deve ter acesso a todos os pares de chaves e tokens de aplicação — o equivalente a nomes de usuário e senhas para integrações de API.
+Como as chaves de aplicação permitem que sistemas externos acessem sua conta, elas só podem ser criadas por usuários que tenham o recurso `License Manager / Services access control / Save user` em seus [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
 
-### Chaves de aplicação externas
+Para criar chaves de aplicação internas na sua conta, siga os passos abaixo.
 
-As chaves de aplicação externas são credenciais geradas e administradas por outras contas VTEX. Ao adicionar [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) às chaves de aplicação — o equivalente a nomes de usuário — fornecidas por terceiros, você pode permitir que eles acessem recursos específicos na sua conta.
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
+2. Clique no botão `Gerenciar minhas chaves`.
 
-## Gerar chaves de aplicação na sua conta
+    Você será redirecionado(a) para a página **Minhas chaves**, ilustrada abaixo. Essa página lista todas as [chaves de aplicação internas](#chaves-de-aplicacao-internas).
 
-Para criar chaves de aplicação na sua conta, acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_ e clique no botão **Gerenciar minhas chaves**. Você será redirecionado para a página **Minhas chaves**, que lista todas as [chaves de aplicação internas](#chaves-de-aplicacao-internas).
+    ![Minhas chaves](//images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/56384e78cd25d545b8bfb8ee603a4c59/minhas-chaves-pt.png)
 
-![My Keys](//images.contentful.com/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/1c98224b6f50673c4567f21e22de4978/image3.png)
+    Estes são os campos visíveis na página **Minhas chaves**:
 
-Estes são os campos visíveis na página **Minhas chaves**:
+    - **Rótulo:** texto que descreve a finalidade da chave de aplicação.
+    - **Chave:** identificador único para a chave de aplicação.
+    - **Status:** estado atual da chave de aplicação, que pode estar ativa ou inativa.
 
-- **Rótulo:** campo de texto que descreve a finalidade da chave de aplicação.
-- **Chave:** campo de texto que contém o identificador único para a chave de aplicação.
-- **Status:** campo booleano que indica se a chave de aplicação está ativa ou inativa.
+3. Clique no botão `+ Gerar chave`.
+2. (Opcional) Preencha o **Rótulo** com uma descrição da finalidade da chave de aplicação. Este campo é imutável e só pode ser definido durante a criação da chave de aplicação. Se ficar vazio, será automaticamente preenchido com o valor do campo **Chave** da chave de aplicação.
+3. (Opcional) Clique em `+ Adicionar perfis` para [gerenciar as permissões da chave de aplicação](#gerenciar-permissoes-das-chaves-de-aplicacao).
+4. Clique no botão `Gerar`.
+5. Clique em <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> para copiar o **Token de aplicação**. _Esse segredo será exibido apenas uma vez. Salve-o em um local seguro._
 
-Como as chaves de aplicação permitem que sistemas externos acessem sua conta, elas só podem ser criadas por usuários que tenham o recurso `License Manager / Services access control / Save user` em seus [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
+<div class="alert alert-warning">
+  <p>Proteja os seus pares de chaves e tokens de aplicação do mesmo modo que faria com outras credenciais, como nomes de usuário e senhas. Se você suspeitar que uma chave de aplicação esteja comprometida, desative imediatamente a chave em sua conta. Para mais detalhes, confira a seção <a href="#ativar-ou-desativar-chaves-de-aplicacao">Ativar ou desativar chaves de aplicação</a> deste artigo.</p>
+</div>
 
-Para gerar uma nova chave de aplicação, siga os passos abaixo:
+## Adicionar chaves de aplicação externas
 
-1. Clique no botão **⊕ Gerar chave**.
-2. (Opcional) Preencha o **Rótulo** com uma descrição da finalidade da chave de aplicação. Este campo é imutável e só pode ser definido quando a chave de aplicação estiver sendo gerada. Se ficar vazio, será automaticamente preenchido com o valor do campo **Chave** da chave de aplicação.
-3. (Opcional) Clique em **+ Adicionar perfis** para [gerenciar as permissões da chave de aplicação](#gerenciar-permissoes-das-chaves-de-aplicacao).
-4. Clique no botão **Gerar**.
-5. Clique em <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> para copiar o **Token de aplicação** _Esse segredo será exibido apenas uma vez. Salve-o em um local seguro._
+Para adicionar chaves de aplicação de terceiros, siga os passos abaixo:
 
-<div class="alert alert-warning">Proteja os seus pares de chaves e tokens de aplicação do mesmo modo que faria com outras credenciais, como nomes de usuário e senhas. Se você suspeitar que uma chave de aplicação esteja comprometida, desative imediatamente a chave em sua conta. Para mais detalhes, confira a seção <a href="#ativar-ou-desativar-chaves-de-aplicacao">Ativar ou desativar chaves de aplicação</a> deste artigo.</div>
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
+2. Clique no botão `+ Adicionar chave de terceiros`.
+3. Preencha o campo **Chave** com a chave de aplicação fornecida pelo terceiro.
+4. Clique em `+ Adicionar perfis` para [gerenciar as permissões da chave de aplicação](#gerenciar-permissoes-das-chaves-de-aplicacao). Adicione perfis de acesso para que eles tenham acesso aos recursos que você deseja.
+5. Clique em `Salvar`.
 
 ## Gerenciar permissões de chaves de aplicação
 
 Para que uma chave de aplicação faça solicitações de API à sua conta com sucesso, ela precisa estar ativa e ter [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) especificando os recursos da conta que tem permissão para acessar. 
 
 <div class="alert alert-danger">
-<b>Atenção!</b> O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas por vazamento de credenciais de login.
+<p>O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas por vazamento de credenciais de login.</p>
 </div>
 
 As chaves de aplicação são criadas, por padrão, sem permissão de acesso a quaisquer recursos da conta.
 
 Há três caminhos para chegar à página de edição dos perfis de acesso de uma chave de aplicação:
 
-- Usar o botão **+ Adicionar perfis** ao [gerar chaves de aplicação](#gerar-chaves-de-aplicacao-na-sua-conta) na sua conta.
-- Usar o botão **⊕ Adicionar** na página **Chaves de aplicação**.
-- Usar o botão **፧** e selecionar a opção **Editar** nas páginas **Chaves de aplicação** ou **Minhas chaves**.
+- Usar o botão `+ Adicionar perfis` ao [gerar chaves de aplicação](#gerar-chaves-de-aplicacao-na-sua-conta) na sua conta.
+- Usar o botão `+ Adicionar chave de terceiros` na página **Chaves de aplicação**.
+- Usar o botão `፧` e selecionar a opção **Editar** nas páginas **Chaves de aplicação** ou **Minhas chaves**.
 
 Ao editar uma chave de aplicação, você pode: 
 
-- Adicionar perfis de acesso clicando no botão **+ Adicionar perfis**, selecionando um ou mais perfis de acesso e clicando no botão **Adicionar perfis**. 
-- Remover perfis de acesso usando as caixas de seleção e clicando no botão **Remover perfis**.
-- Salvar clicando no botão **Salvar**.
+- Adicionar perfis de acesso clicando no botão `+ Adicionar perfis`, selecionando um ou mais perfis de acesso e clicando no botão `Adicionar perfis`. 
+- Remover perfis de acesso usando as caixas de seleção e clicando no botão `Remover perfis`.
+- Salvar as alterações clicando no botão `Salvar`.
 
 Após ter adicionado perfis de acesso à chave de aplicação, ela será exibida na página **Chaves de aplicação**.
 
-![Application Keys](//images.contentful.com/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/da66ebc249dd18cbc709d872ce78719c/image2.png)
+![Chaves de aplicação](//images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/b21ce0058da588e889f23ef46582b91c/appkeys-pt.png)
 
 Estes são os campos visíveis na página **Chaves de aplicação**:
 
-- **Chave:** campo de texto que contém o identificador único para a chave de aplicação.
-- **Conta:** campo de texto que indica a conta VTEX responsável por gerenciar a chave de aplicação.
-- **Status:** campo booleano que indica se a chave de aplicação está ativa ou inativa.
+- **Chave:** identificador único para a chave de aplicação.
+- **Conta:** conta VTEX responsável por gerenciar a chave de aplicação.
+- **Status:** estado atual da chave de aplicação, que pode estar ativa ou inativa.
 
-<div class="alert alert-info">Observe que o campo <strong>Rótulo</strong> não é exibido na página <strong>Chaves de aplicação</strong>. Para ver a descrição da finalidade de uma chave de aplicação interna, use o valor da <strong>Chave</strong> e busque por ela na página <strong>Minhas chaves</strong>. Não é possível adicionar rótulos a chaves de aplicação externas.</div>
+<div class="alert alert-info">
+  <p>Observe que o campo <strong>Rótulo</strong> não é exibido na página <strong>Chaves de aplicação</strong>. Para ver a descrição da finalidade de uma chave de aplicação interna, use o valor da <strong>Chave</strong> e busque por ela na página <strong>Minhas chaves</strong>. Não é possível adicionar rótulos a chaves de aplicação externas.</p>
+</div>
 
 ## Ativar ou desativar chaves de aplicação
 
 Se uma chave de aplicação que tenha acesso à sua conta for comprometida, você deve revogar imediatamente o acesso dela à sua conta. Caso cometa algum erro, é possível reabilitá-la para restabelecer a integração impactada. O modo como você fará isso dependerá do [tipo de chave de aplicação](#tipos-de-chaves-de-aplicacao).
 
-<div class="alert alert-warning">Apenas reative a chave de aplicação se tiver certeza de que ela não foi comprometida. Qualquer pessoa com o token de aplicação associado recuperará o acesso privilegiado à sua conta.</div>
+<div class="alert alert-warning">
+  <p>Apenas reative a chave de aplicação se tiver certeza de que ela não foi comprometida. Qualquer pessoa com o token de aplicação associado recuperará o acesso privilegiado à sua conta.</p>
+</div>
+
+### Desativar chave de aplicação interna
 
 Para desativar uma chave de aplicação interna, siga os passos abaixo: 
 
-1. Acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_.
-2. Clique no botão **Gerenciar minhas chaves**.
-3. Encontre a chave de aplicação que você deseja desativar na lista e clique no botão **፧**.
-4. Selecione a opção **Desativar**.
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
+2. Clique no botão `Gerenciar minhas chaves`.
+3. Encontre a chave de aplicação que você deseja desativar na lista e clique no botão `፧`.
+4. Clique na opção **Desativar**.
+
+### Desativar chave de aplicação externa
 
 Para desativar uma chave de aplicação externa, siga os passos abaixo: 
 
-1. Acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_.
-2. Encontre a chave de aplicação que você deseja desativar na lista e clique no botão **፧**.
-3. Selecione a opção **Remover**.
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
+2. Encontre a chave de aplicação que você deseja desativar na lista e clique no botão `፧`.
+3. Clique na opção **Remover**.
+
+### Ativar chave de aplicação interna
 
 Para reativar chaves de aplicação internas que tenham sido desativadas anteriormente, siga os passos abaixo:
 
-1. Acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_.
-2. Clique no botão **Gerenciar minhas chaves**.
-3. Encontre a chave de aplicação que você deseja reativar na lista e clique no botão **፧**.
-4. Selecione a opção **Ativar**.
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
+2. Clique no botão `Gerenciar minhas chaves`.
+3. Encontre a chave de aplicação que você deseja reativar na lista e clique no botão `፧`.
+4. Clique na opção **Ativar**.
 
-Para reativar chaves de aplicação externas que tenham sido desativadas anteriormente, siga os passos abaixo:
+### Ativar chave de aplicação externa
 
-1. Acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_.
-2. Clique no botão **⊕ Adicionar**.
-3. Preencha o campo **Chave** com a chave de aplicação fornecida pelo terceiro.
-4. Adicione perfis de acesso para que eles tenham acesso aos recursos que você deseja.
+Para reativar chaves de aplicação externas que tenham sido desativadas anteriormente, será necessário refazer as instruções descritas para [adicionar chaves de aplicação externas](#adicionar-chaves-de-aplicacao-externas).
 
 ## Exportar chaves de aplicação com acesso à sua conta
 
-Se necessário para uma auditoria de segurança, você pode exportar um arquivo CSV contendo os valores da **Chave** para todas as chaves de aplicação internas e externas que atualmente têm acesso à sua conta — ou seja, que têm perfis de acesso associadas a elas. Para exportar as chaves, acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_ e clique no botão <span style="display: inline-block;"><img src="//images.contentful.com/alneenqid6w5/25JqGWNUZPZattDX6ORXX6/742e99e17042024b9cae641564909171/image4.png" alt="export-button"/> <strong>Exportar</strong></span>.
+Se necessário para uma auditoria de segurança, você pode exportar um arquivo CSV contendo os valores da **Chave** para todas as chaves de aplicação internas e externas que atualmente têm acesso à sua conta — ou seja, que têm perfis de acesso associadas a elas.
+
+Para exportar as chaves, acesse _Configurações da conta > Gerenciamento da conta > Chaves de aplicação_ e clique no botão <span style="display: inline-block;"><img src="//images.contentful.com/alneenqid6w5/25JqGWNUZPZattDX6ORXX6/742e99e17042024b9cae641564909171/image4.png" alt="export-button"/> <strong>Exportar</strong></span>.
diff --git a/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
index 47300158d..b6999c991 100644
--- a/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
@@ -3,8 +3,8 @@ title: 'Aprovar pagamento de boleto'
 id: tutorials_184
 status: PUBLISHED
 createdAt: 2017-04-27T22:16:19.919Z
-updatedAt: 2023-03-26T21:44:48.077Z
-publishedAt: 2023-03-26T21:44:48.077Z
+updatedAt: 2024-06-03T20:36:09.927Z
+publishedAt: 2024-06-03T20:36:09.927Z
 firstPublishedAt: 2017-04-27T23:00:46.699Z
 contentType: tutorial
 productTeam: Financial
@@ -25,7 +25,7 @@ Essa aprovação pode ser feita manualmente no módulo Pedidos, conforme abaixo.
 2. Clique sobre a transação desejada.
 3. Clique no botão **Notificar Pagamento**.
 
-![NotificarPT](https://images.ctfassets.net/alneenqid6w5/6jQnmZtHygY4csKym2kC0e/f48943b3a025d87ab59a724e17188df3/NotificarPT.png)
+![NotificarPT](//images.ctfassets.net/alneenqid6w5/6jQnmZtHygY4csKym2kC0e/f48943b3a025d87ab59a724e17188df3/NotificarPT.png)
 
 **Após a aprovação do pagamento, o pedido entrará no fluxo normal de compra.**
 
@@ -33,7 +33,7 @@ Essa aprovação pode ser feita manualmente no módulo Pedidos, conforme abaixo.
 No módulo de Gerenciamento da Conta, o usuário precisa ter um perfil de acesso que inclua a permissão <code>Notify payment</code> para ser capaz de aprovar pagamentos.
 </div>
 
-Para aprovar o pagamento por API, veja a [documentação da chamada de notificação de pagamento](https://developers.vtex.com/reference/payment#getorder).
+Para aprovar o pagamento por API, veja a [documentação da chamada de notificação de pagamento](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/payments/-paymentId-/payment-notification).
 
 <div class="alert alert-warning">
 Como <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integrações com ERPs</a> são regidas pelo <a href="https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#">fluxo de pedidos</a>, a aprovação manual de um pagamento dará continuidade à integração deste pedido com o back office da loja normalmente. Portanto recomenda-se cautela ao aprovar pagamentos manualmente, de modo a garantir o recebimento por cada pedido que é processado e enviado.
diff --git a/docs/tutorials/pt/apps-overview.md b/docs/tutorials/pt/apps-overview.md
index f66d35b0f..34a2d550b 100644
--- a/docs/tutorials/pt/apps-overview.md
+++ b/docs/tutorials/pt/apps-overview.md
@@ -36,7 +36,7 @@ O menu Aplicativos permite que os comerciantes baixem novos aplicativos diretame
 
 Essas operações podem ser realizadas no menu Aplicativos do seu Admin repaginado.
 
-![Apps Overview menu PT](https://images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/46e4dce503c39c70978460a967bd34b0/Apps_Overview_menu_PT.jpg)
+![Apps Overview menu PT](//images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/46e4dce503c39c70978460a967bd34b0/Apps_Overview_menu_PT.jpg)
 
 Veja abaixo mais detalhes sobre as diferentes seções e páginas deste recurso, que em breve estará disponível no Admin repaginado.
 
diff --git a/docs/tutorials/pt/assembly-options-app.md b/docs/tutorials/pt/assembly-options-app.md
index 06964b494..a11ba47d6 100644
--- a/docs/tutorials/pt/assembly-options-app.md
+++ b/docs/tutorials/pt/assembly-options-app.md
@@ -37,7 +37,7 @@ Após a instalação, a página **Catálogo > Assembly Options** se torna dispon
 
 No Admin VTEX, em **Catálogo > Assembly options**, você tem acesso a uma lista com todas as Assembly Options cadastradas na sua loja utilizando o aplicativo.
 
-![assembly-options-app](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
+![assembly-options-app](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
 
 As informações exibidas na lista são:
 
diff --git a/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md b/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md
new file mode 100644
index 000000000..b28787f6c
--- /dev/null
+++ b/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md
@@ -0,0 +1,62 @@
+---
+title: 'Assembly Options no VTEX Sales App'
+id: 4fTfqOMcXyhAhWXkl935lr
+status: PUBLISHED
+createdAt: 2024-04-30T11:16:48.636Z
+updatedAt: 2024-04-30T17:04:30.041Z
+publishedAt: 2024-04-30T17:04:30.041Z
+firstPublishedAt: 2024-04-30T14:58:57.024Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: assembly-options-no-vtex-sales-app
+locale: pt
+legacySlug: assembly-options-no-vtex-sales-app
+subcategory: 4T6qfa6gNO6g4sAUIa6s2G
+---
+
+O [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) é um aplicativo que permite a integração entre os canais de vendas online e físicos. Por meio dele, os vendedores das lojas físicas podem oferecer atendimento personalizado aos clientes, e realizar o processo de venda de maneira completa e presencial, desde a escolha dos produtos, até a seleção do melhor meio de pagamento e entrega.
+
+Para mais informações sobre a instalação do VTEX Sales App, acesse [VTEX Sales App - Configurações Básicas](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO).
+
+O [Assembly Options](https://help.vtex.com/pt/tutorial/assembly-options-app), disponível na VTEX  [App Store](https://apps.vtex.com/vtex-admin-assembly-options/p), é a funcionalidade que permite aos vendedores oferecer serviços adicionais durante o processo de venda, como garantia estendida e seguro. Além disso, proporciona a montagem de conjuntos compostos por diversos SKUs, como cestas de natal ou café da manhã, kits de maquiagem, entre outros.
+
+## Instalando o Assembly Options
+
+Para utilizar o Assembly Options, é necessário ter o [VTEX Sales App](https://apps.vtex.com/vtex-assisted-sales-admin/p) e o [Assembly Options App](https://help.vtex.com/pt/tutorial/assembly-options-app--54mWg37mojrqOgCA79iqqk) instalados em sua loja. O aplicativo Assembly Options App está disponível somente para lojas VTEX IO.
+
+## Cenários de aplicação do Assembly options no VTEX Sales App
+
+Existem dois cenários nos quais é possível adicionar serviços a produtos presentes em um único carrinho:
+
+**Cenário 1:**  Seleção de um único serviço.
+
+1. Adicione ao carrinho um produto que possui uma Assembly Options de serviços associados.
+
+2. Selecione a opção do serviço oferecido que deseja, e clique no botão **Continuar para o carrinho** .
+
+3. Após finalizar o processo, é possível visualizar em seu carrinho o serviço que foi selecionado, com o valor total do pedido.
+
+![Garantia estendida - PT](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/d7ed484879b2e99209db45d784227559/Cen_rio_1__T1__PT.png)
+
+![Carrinho - PT](//images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/c208432eab7761f4b3ace4cd75ef30db/Cen_rio_1__T2__PT.png)
+
+**Cenário 2:** Seleção de múltiplos serviços
+
+1. Adicione ao carrinho um produto que tem mais de uma Assembly Option de serviços associados.
+
+2. É permitido realizar a escolha de mais de um serviço, basta selecionar a opção do serviço oferecido que deseja e clique no botão **Avançar**.
+
+3. Escolha outro serviço oferecido que deseja adicionar e clique no botão **Continuar para o carrinho**.
+
+4. Após o processo finalizado, é possível visualizar em seu carrinho os serviços que foram selecionados com o valor total do pedido.
+
+5. Clique no botão **Continuar**. Caso algum dos serviços exija informação adicional,  preencha os campos necessários para vincular estas informações ao serviço adquirido.
+
+6. Clique no botão **Aplicar**.
+
+![Garantia estendida - PT](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/d7ed484879b2e99209db45d784227559/Cen_rio_1__T1__PT.png)
+
+![Seguro - PT](//images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/be5cd06bb77bb828040cb44b8604b10b/Cen_rio_2__T2__-_PT.png)
+
+![Ordem pedido - PT](//images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/e7f7178cf8f4c30faf5cca4bda49dcc2/Cen_rio_2__T3__-_PT.png)
diff --git a/docs/tutorials/pt/assembly-options.md b/docs/tutorials/pt/assembly-options.md
index 326bbbc88..70726da16 100644
--- a/docs/tutorials/pt/assembly-options.md
+++ b/docs/tutorials/pt/assembly-options.md
@@ -3,8 +3,8 @@ title: 'Assembly Options'
 id: 5x5FhNr4f5RUGDEGWzV1nH
 status: PUBLISHED
 createdAt: 2021-10-25T20:22:43.094Z
-updatedAt: 2023-03-29T17:55:49.763Z
-publishedAt: 2023-03-29T17:55:49.763Z
+updatedAt: 2024-06-06T19:38:13.881Z
+publishedAt: 2024-06-06T19:38:13.881Z
 firstPublishedAt: 2021-10-25T21:39:46.746Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Uma Assembly Option é um [anexo](https://help.vtex.com/pt/tutorial/o-que-e-um-a
 
 No exemplo abaixo, uma loja oferece várias Assembly Options para o produto _Custom Bell_. Essas opções são mostradas na página do produto, onde o cliente pode selecionar as opções desejadas. Dependendo das escolhas, pode haver um custo adicional.
 
-![assembly-option-PT](https://images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/4d0d0db168c8a984a69fb6462ccc9084/image.png)
+![assembly-option-PT](//images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/4d0d0db168c8a984a69fb6462ccc9084/image.png)
 
 Você pode combinar [SKUs](https://help.vtex.com/pt/tutorial/o-que-e-um-sku--1K75s4RXAQyOuGUYKMM68u) para oferecer Assembly Options, como o _Bells add-ons Roman_ ou o _Bells add-ons 1-3 lines_ no exemplo acima. Se um item estiver esgotado, ele será exibido como indisponível.
 
@@ -61,7 +61,7 @@ O primeiro trecho`[x-y]` se refere às regras aplicadas ao grupo, e entre cada `
 |\[0-3\]#10000\[1-2\]**\[1\]**pricetable1;#20000\[0-2\]**\[0\]**pricetable2;#30000\[0-2\]**\[0\]**pricetable3 | Esse segmento define a quantidade padrão selecionada para cada SKU.                                    |
 | \[0-3\]#10000\[1-2\]\[1\]**pricetable1**;#20000\[0-2\]\[0\]**pricetable2**;#30000\[0-2\]\[0\]**pricetable3** | O segmento final indica a tabela de preços para cada item. |
 
-![assembly-option-exemplo-PT](https://images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/ff463ce52bf53d528a1127d81a36eb38/image.png)
+![assembly-option-exemplo-PT](//images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/ff463ce52bf53d528a1127d81a36eb38/image.png)
 
 #### Configuração do Anexo
 
diff --git a/docs/tutorials/pt/associate-a-sku-to-a-trade-policy.md b/docs/tutorials/pt/associate-a-sku-to-a-trade-policy.md
index 06db9f0f0..8dbe582c6 100644
--- a/docs/tutorials/pt/associate-a-sku-to-a-trade-policy.md
+++ b/docs/tutorials/pt/associate-a-sku-to-a-trade-policy.md
@@ -1,10 +1,10 @@
 ---
 title: 'Associação de SKU à Política Comercial'
 id: 1qFAiybogHCStRO65sy4vb
-status: CHANGED
+status: PUBLISHED
 createdAt: 2021-03-30T17:18:09.088Z
-updatedAt: 2023-03-29T18:27:48.036Z
-publishedAt: 2021-08-04T18:13:54.928Z
+updatedAt: 2024-05-31T22:32:04.940Z
+publishedAt: 2024-05-31T22:32:04.940Z
 firstPublishedAt: 2021-03-30T17:34:49.644Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -29,4 +29,8 @@ Na página de configuração de cada SKU existe a opção de associar apenas aqu
 6. Marque a caixa de seleção correspondente à Política Comercial desejada.
 7. No final da página, clique no botão `Salvar` para registrar as alterações.
 
+<div class="alert alert-warning" role="alert">
+  <p>Se nenhuma política comercial específica for selecionada na configuração do SKU, todas as políticas comerciais terão acesso ao SKU.</p>
+</div>
+
 Toda alteração realizada em um SKU leva um tempo até ser totalmente processada, inclusive associações a Políticas Comerciais. Confira mais detalhes no artigo [Como funciona a indexação](https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao--tutorials_256).
diff --git a/docs/tutorials/pt/associating-a-template-with-a-layout.md b/docs/tutorials/pt/associating-a-template-with-a-layout.md
index 6f4a3f1e6..1f99e0475 100644
--- a/docs/tutorials/pt/associating-a-template-with-a-layout.md
+++ b/docs/tutorials/pt/associating-a-template-with-a-layout.md
@@ -35,4 +35,4 @@ Essa associação é feita na configuração de propriedades do layout. Para che
 6. Selecione o template que você deseja associar a esse layout.
 7. Digite `yes` para confirmar a mudança. (Este passo é necessário porque esta é uma alteração crítica para o site, já que o front-end da página será substituído.) 
 
-![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tutorials/pt/audit.md b/docs/tutorials/pt/audit.md
new file mode 100644
index 000000000..8a6776649
--- /dev/null
+++ b/docs/tutorials/pt/audit.md
@@ -0,0 +1,136 @@
+---
+title: 'Audit'
+id: 5RXf9WJ5YLFBcS8q8KcxTA
+status: PUBLISHED
+createdAt: 2021-10-21T16:51:06.108Z
+updatedAt: 2024-04-18T14:03:48.943Z
+publishedAt: 2024-04-18T14:03:48.943Z
+firstPublishedAt: 2021-10-21T21:55:42.939Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: audit
+locale: pt
+legacySlug: como-encontrar-eventos-no-audit
+subcategory: 2TNXiKzLZOPxjMTyGiEeJu
+---
+
+Para aumentar a transparência e a confiança entre os usuários administrativos da sua loja, a VTEX registra diversas operações, seus autores e os horários em que elas ocorreram no **Audit**, um módulo utilizado para pesquisar e investigar este histórico com o auxílio de filtros.
+
+Para acessar a página do Audit no Admin VTEX, acesse **Apps > Apps instalados > Audit**, ou digite **Audit** na barra de busca. Nessa página, é possível realizar as seguintes ações:
+
+* [Buscar eventos no Audit](#buscar-eventos-no-audit)
+* [Verificar últimas buscas realizadas no Audit](#verificar-ultimas-buscas-realizadas-no-audit)
+
+<div class="alert alert-info">
+  <p>Para visualizar os eventos do Audit, é necessário ter um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> associado ao <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <em>Insights Metrics</em>.</p>
+</div>
+
+![audit-ui-pt 1](//images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/42032a1aa1700f58ffaf92b1e00ecfd2/audit-ui-pt_1.png)
+
+## Buscar eventos no Audit
+
+O Audit possibilita realizar buscas por eventos a partir de filtros relacionados às informações a seguir: aplicação, data, ação, autor e detalhes do evento. A seguir, explicamos como utilizar os [filtros](#filtros) do Audit e como os [resultados](#resultados) são apresentados. Também demonstramos o uso de filtros com [exemplos](#exemplos-de-buscas) práticos.
+
+### Filtros
+
+Confira o passo a passo para buscar por um evento utilizando os filtros disponíveis no Audit:
+
+1. No Admin VTEX, acesse **Apps > Apps instalados > Audit**, ou digite _Audit_ na barra de busca. Você será conduzido(a) para a aba **Eventos de auditoria** do Audit.
+2. Em **Filtros**, no menu **Aplicação**, selecione a aplicação relacionada à busca.
+3. No menu **Data**, escolha uma data pré-definida para a busca. Se preferir definir o exato intervalo de datas para a busca, ative a opção **Personalizada** e determine as datas de **Início** e **Fim** para a busca.
+
+   <div class= "alert alert-info">
+     <p>Apenas registros dos últimos três meses são armazenados.</p>
+   </div>
+
+4. Se desejar, inclua um filtro por Ação. Para isso, no campo ao lado de `Ação deve ser`, digite o nome da ação e tecle `Enter`. Você pode inserir mais de um valor teclando `Enter` após cada seleção. Confira o nome de cada ação em [Eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
+5. Se necessário, você pode adicionar filtros mais específicos para realizar a busca por eventos com mais precisão. Para isso, clique no botão `Adicionar Filtro`.
+6. Selecione o parâmetro de filtragem (_Autor_ ou _Detalhe do evento_) e informe a qual valor o parâmetro deve ser comparado. Você pode inserir mais de um valor teclando `Enter` após cada seleção.
+
+    Ao adicionar filtros com o mesmo parâmetro (exemplo: um filtro definindo que a ação deve ser `Change Promotion Configuration` ou `Change Coupon Configuration`), os resultados incluem eventos que se igualam a qualquer um dos valores inseridos. Ao adicionar filtros com parâmetros distintos (exemplo: `Ação = Change Coupon Configuration `e `Autor = email@email.com`), os critérios são somados. É possível repetir os passos 4 e 5 para adicionar mais filtros.
+
+    Por exemplo, a busca correspondente à figura abaixo encontra resultados cujas ações são _Change Promotion Configuration_ ou _Change Coupon Configuration_ e cujo autor é `email@email.com`.
+
+    ![filtros-pt](//images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/3f1ad9727d1f0eb54168e9e68895533b/filtros-pt.png)
+
+7. Clique no botão `Aplicar` para obter os eventos que foram encontrados.
+
+    Confira [Resultados](#resultados) para entender como os eventos são apresentados.
+
+<div class= "alert alert-warning">
+  <p>Os resultados da busca correspondem exatamente ao conteúdo escrito no tópico do filtro. Para evitar resultados inesperados, certifique-se de que você não digitou espaços desnecessários nos termos da busca.</p>
+</div>
+
+Se desejar, você pode compartilhar uma busca com outro usuário. Para isso, clique em `Compartilhar busca`, no canto superior direito da página. O link para a busca no Audit será copiado para a sua área de transferência.
+
+### Resultados
+
+A seção **Resultados** lista cada evento encontrado na busca e exibe as informações de cada evento, apresentadas na tabela a seguir.
+
+| Coluna | Descrição |
+|---|---|
+| __Copiar__ | Botão para copiar as informações do evento exibidas na tabela para a área de transferência. |
+| __Hora do evento__ | Data e horário em que o evento ocorreu, no fuso horário do navegador ou do sistema operacional. |
+| __Ação__ | Ação realizada na aplicação selecionada para a busca. Confira as ações possíveis na [lista de eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ). |
+| __Detalhe do evento__ | Informações complementares sobre o evento. Confira os detalhes exibidos para cada evento na [lista de eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ). |
+| __Autor__ | Email, ID ou token do usuário que realizou o evento. |
+| __Mais detalhes__ | Botão que abre um modal com mais informações sobre o evento, quando aplicável. Os detalhes exibidos podem incluir: <ul><li class="t-body mb5 lh-copy"><strong>Nome da entidade:</strong> ID da entidade modificada.</li><li class="t-body mb5 lh-copy"><strong>Entidade antes da ação:</strong> dados da entidade antes do evento, em formato <a href="http://www.json.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" rel="noopener noreferrer" target="_blank">JSON</a>.</li><li class="t-body mb5 lh-copy"><strong>Entidade após a ação:</strong> dados da entidade após o evento, em formato <a href="http://www.json.org/" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word" rel="noopener noreferrer" target="_blank">JSON</a>.</li></ul>A depender do evento, nem todas as informações citadas acima são exibidas. Por exemplo, um evento de exclusão de uma informação mostra apenas a entidade antes da ação. Por outro lado, um evento de criação de uma informação apresenta apenas a entidade após a ação. <br /><br /> Alguns eventos não apresentam nenhuma informação complementar. Nesses casos, o modal aparece vazio. |
+
+### Exemplos de buscas
+
+A seguir, listamos alguns cenários de busca comuns para ilustrar como os filtros devem ser compostos dependendo do que se deseja buscar.
+
+#### Ativação de produto
+
+Para buscar se um produto foi ativado no Catálogo em determinada data:
+
+1. Selecione a data desejada.
+2. No menu **Aplicação**, selecione _Catálogo (Admin)_.
+3. Adicione um filtro cuja **Ação** deve ser `Product Activation`.
+4. Adicione um filtro cujo **Detalhe do evento **deve ser `product id "X" activated`, onde `X` precisa ser substituído pelo ID do produto buscado.
+
+#### Alteração de preço
+
+Para buscar se o preço de um SKU foi alterado em determinada data:
+
+1. Selecione a data desejada.
+2. No menu **Aplicação**, selecione _Preços_.
+3. Adicione um filtro cuja **Ação** deve ser `Put Price`.
+4. Adicione um filtro cujo **Detalhe do evento **deve ser o ID do SKU do item procurado.
+
+#### Exclusão de estoque
+
+Para buscar se um estoque foi deletado em determinada data:
+
+1. Selecione a data desejada.
+2. No menu **Aplicação**, selecione _Estoque & Entrega_.
+3. Adicione um filtro cuja **Ação** deve ser `Warehouse Delete`.
+4. Adicione um filtro cujo **Detalhe do evento **deve ser o ID do item procurado.
+
+#### Exclusão de transportadora
+
+Para buscar se uma transportadora foi deletada em determinada data:
+
+5. Selecione a data desejada.
+6. No menu **Aplicação**, selecione _Estoque & Entrega_.
+7. Adicione um filtro cuja **Ação** deve ser `Carrier Delete`.
+8. Adicione um filtro cujo **Detalhe do evento** deve ser o ID da transportadora buscada.
+
+## Verificar últimas buscas realizadas no Audit
+
+Toda busca realizada no Audit é salva na aba **Últimas buscas**. Para refazer uma busca nessa aba, clique no botão <img src="//images.ctfassets.net/alneenqid6w5/4gWsOnbLMOUeWh0r5YRDz/9b7148d995c03ca84b39473f266b46a9/refresh.png" width="15"> correspondente à busca que você deseja refazer.
+
+Confira a seguir as informações disponíveis nesta aba:
+
+| Coluna | Descrição |
+|---|---|
+| Buscado em | Data e horário em que a busca foi realizada no Audit. |
+| Aplicação | Aplicação da VTEX em que os eventos foram buscados. |
+| Termos buscados | Filtros utilizados na busca. |
+| Período buscado | Data de início e fim do período selecionado para a busca. |
+| Refazer busca | Botão que permite repetir a busca. |
+
+<div class= "alert alert-warning">
+  <p>Apenas 50 buscas ficam gravadas na aba <b>Últimas buscas</b>. Se quiser salvar uma busca além desse limite, adicione-a aos favoritos do seu browser.</p>
+</div>
diff --git a/docs/tutorials/pt/authentication.md b/docs/tutorials/pt/authentication.md
new file mode 100644
index 000000000..6372a6b65
--- /dev/null
+++ b/docs/tutorials/pt/authentication.md
@@ -0,0 +1,87 @@
+---
+title: 'Autenticação'
+id: 21CkKHLKP1o41lUpGhuRUs
+status: PUBLISHED
+createdAt: 2021-10-25T19:06:37.982Z
+updatedAt: 2024-02-26T20:32:47.823Z
+publishedAt: 2024-02-26T20:32:47.823Z
+firstPublishedAt: 2021-11-08T18:39:50.432Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: autenticacao
+locale: pt
+legacySlug: pagina-de-autenticacao
+subcategory: 14V5ezEX0cewOMg0o0cYM6
+---
+
+A autenticação é o procedimento para validar a identidade de usuários. Na VTEX, esse processo ocorre em três situações diferentes:
+
+* [Login](#login): responsável por verificar e validar a identidade dos usuários que desejam acessar uma loja virtual ou o Admin da VTEX.
+* [Desenvolvimento de Integrações](#desenvolvimento-de-integracoes): responsável por autenticar solicitações realizadas às APIs da VTEX a partir de integrações com serviços externos. Essa validação geralmente é realizada através de chaves de API ou tokens de usuário.
+* [Desenvolvimento de apps](#desenvolvimento-de-apps): responsável por garantir a legitimidade da comunicação entre os aplicativos desenvolvidos com VTEX IO e as APIs da VTEX. Essa validação geralmente é realizada através de tokens de autenticação.
+
+## Login
+
+Na VTEX, a autenticação por login ocorre em dois contextos: na loja virtual, quando clientes realizam login para acessar seu perfil ou para realizar uma compra, e no Admin, quando usuários administrativos realizam login para operar o ambiente administrativo da loja.
+
+É necessário configurar qual método de autenticação será ofertado em cada contexto. Confira as opções disponíveis na tabela a seguir:
+
+| Forma de login | Descrição | Loja virtual | Admin |
+|---|---|---|---|
+| Código de acesso | Um código numérico aleatório é enviado para o email do usuário, que informa o código para realizar o login. | Pode ser habilitada | Sempre habilitada |
+| Senha | O usuário pode registrar uma senha e efetuar o login usando o email e a senha cadastrados. Lojistas podem optar por [aplicar a expiração de senha](#aplicar-expiracao-de-senha) após um período específico para usuários do Admin. | Pode ser habilitada | Sempre habilitada. A expiração de senha pode ser habilitada. |
+| Facebook | O usuário faz login usando sua conta do Facebook. Confira o guia [Configurar login com Facebook e Google](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513) para mais detalhes. | Pode ser habilitada | Indisponível |
+| Google | O usuário faz login usando sua conta do Google. Confira o guia [Configurar login com Facebook e Google](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513) para mais detalhes. | Pode ser habilitada | Pode ser habilitada |
+| Integração com outros provedores de identidades | O usuário pode fazer login usando sua conta de outros provedores de identidades externos, a partir de uma integração. Confira o guia para desenvolvedores [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) para mais detalhes. | Pode ser habilitada, utilizando o protocolo OAuth.  Confira o guia para desenvolvedores [Webstore (OAuth 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) para mais detalhes. | Pode ser habilitada, utilizando o protocolo SAML. Confira o guia para desenvolvedores [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) para mais detalhes. |
+
+<div class="alert alert-info">
+  <p>Pelo menos uma das formas de login da tabela acima deve estar habilitada para a loja virtual.</p>
+</div>
+
+<div class="alert alert-warning">
+  <p>Para logar no Admin VTEX, é preciso ter um <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512">usuário</a> administrativo cadastrado. Os <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfis de acesso</a> relacionados ao usuário e as permissões incluídas no perfil determinam quais <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos</a> ele pode utilizar no Admin.</p>
+</div>
+
+### Habilitar formas de login
+
+Na página **Autenticação**, é possível escolher quais formas de login você deseja oferecer aos clientes da sua loja e aos usuários administrativos que terão acesso ao Admin da sua conta.
+
+![Página de autenticação](//images.contentful.com/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/986b144c0704f780d774f8f3790ba8e6/Tela_de_Autentica____o_PT.png)
+
+Confira o passo a passo a seguir para habilitar os métodos de login desejados:
+
+1. Na barra superior do Admin VTEX, clique no avatar do seu perfil, marcado pela inicial do seu email.
+2. Clique em **Configurações da conta > Autenticação**.
+
+    Você será direcionado(a) para a aba **Loja virtual**, que lista os métodos de login disponíveis na sua loja virtual. Nesta aba, é possível habilitar os métodos desejados para o login de clientes.
+
+    Para configurar formas de login no Admin para usuários administrativos, clique na aba **Admin**.
+
+    Consulte a tabela na seção [Login](#login) para entender os métodos de login disponíveis e acessar a documentação que explica como configurá-los.
+
+### Aplicar expiração de senha para usuários do Admin
+
+Se a opção de login com senha estiver habilitada, é possível determinar que senhas de usuários do Admin devem expirar após uma quantidade determinada de dias. Para isso, siga as instruções abaixo:
+
+1. Na barra superior do Admin VTEX, clique no avatar do seu perfil, marcado pela inicial do seu email.
+2. Clique em **Configurações da conta > Autenticação**.
+3. Clique na aba **Admin**.
+4. Na linha **Senha**, clique em `Editar`.
+5. Marque a opção **Aplicar expiração de senha**.
+6. Selecione um período após o qual a senha dos usuários administrativos se tornará inválida. É possível escolher **15**, **30** ou **90 dias**.
+7. Clique em `Salvar`.
+
+Após o período definido, ao realizar uma tentativa de login, o usuário precisará redefinir a senha.
+
+## Desenvolvimento de integrações
+
+Ao desenvolver integrações utilizando as [APIs](https://developers.vtex.com/docs/guides/getting-started) da VTEX, é preciso fornecer parâmetros de autenticação para realizar as operações desejadas. Veja a seguir os métodos disponíveis:
+
+* **Chaves de aplicação (appKeys):** as [chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) são utilizadas para autenticar solicitações às APIs da VTEX. Os administradores da loja podem criar chaves e associá-las a [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete), com permissão para utilizar determinados [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) da plataforma. Mais informações estão disponíveis no guia para desenvolvedores [API authentication using application keys](https://developers.vtex.com/docs/guides/api-authentication-using-application-keys).
+* **Tokens de usuário:** os tokens de usuário são usados para autenticar solicitações de API, especialmente para aplicativos [frontend](https://help.vtex.com/pt/tracks/desenvolvimento-de-loja--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl) desenvolvidos com VTEX IO. Veja como usar no guia para desenvolvedores [API authentication using user tokens](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens).
+
+## Desenvolvimento de apps
+
+O uso de tokens de autenticação (auth tokens) é necessário para autenticação no desenvolvimento de apps em VTEX IO. Mais detalhes estão disponíveis no guia para desenvolvedores [App authentication using auth tokens](https://developers.vtex.com/docs/guides/app-authentication-using-auth-tokens).
+
diff --git a/docs/tutorials/pt/autocomplete.md b/docs/tutorials/pt/autocomplete.md
new file mode 100644
index 000000000..7ab448830
--- /dev/null
+++ b/docs/tutorials/pt/autocomplete.md
@@ -0,0 +1,74 @@
+---
+title: 'Autocomplete'
+id: 6qhP0ZQ4JqUBdgFnbnxS4a
+status: PUBLISHED
+createdAt: 2024-06-27T16:42:03.645Z
+updatedAt: 2024-06-27T16:42:56.071Z
+publishedAt: 2024-06-27T16:42:56.071Z
+firstPublishedAt: 2024-06-27T16:42:56.071Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: autocomplete
+locale: pt
+legacySlug: autocomplete
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+<div class = "alert alert-warning">
+O Autocomplete é uma ferramenta já ativa no VTEX Intelligent Search. Não é possível desligá-la no Admin.
+    </div>
+
+O Autocomplete funciona com base nas informações obtidas por meio do histórico de busca de termos relacionados ao Catálogo. Esses resultados são apresentados em quatro listas diferentes, que podem estar juntas ou separadas, dependendo da interação com o cliente. As seções existentes são:
+
+- Últimas buscas efetuadas.
+- Sugestão de busca.
+- Sugestão de produtos.
+- Termos mais buscados.
+
+<div class="alert alert-warning" role="alert">
+<p>Ao pesquisar um termo não cadastrado, o Autocomplete não encontrará produtos com as especificações desejadas e não exibirá nenhuma sugestão.
+</p>
+</div>
+
+Durante a interação com a barra de busca, o VTEX Intelligent Search exibe imediatamente o conjunto de _Termos mais buscados_ e _Últimas pesquisas_, caso o cliente já tenha feito alguma.
+
+Quando o usuário começa a digitar, o sistema mostra as _Sugestões de busca_ e _Sugestões de produtos_ e remove as listas anteriores.
+
+<div class = "alert alert-info">
+  <p>As informações das seções <b>Termos mais buscados</b> e <b>Sugestão de busca</b> são atualizadas diariamente. Para isso, são utilizados os dados dos últimos 14 dias da interação dos clientes com a busca.</p>
+  </div>
+
+Dessa forma, é possível proporcionar ao cliente uma experiência de pesquisa mais fluida e personalizada. Ele consegue visualizar o resultado de maneira rápida, além de receber sugestões baseadas na sua busca.
+
+Outra vantagem para o gestor da loja é o aumento de conversão, resultado dessa dinâmica de usabilidade e experiência.
+
+<div class = "alert alert-info">
+  <p> O Autocomplete oferece sugestões de pesquisa mesmo quando a loja é totalmente nova e ainda não dispõe de dados de interações com clientes, como cliques e buscas.
+    Nesse caso, a funcionalidade gera sugestões de busca a partir de um algoritmo que extrai palavras-chave do catálogo, dos produtos, das marcas e das categorias registradas na loja.
+</p>
+  </div>
+
+## Termos mais buscados
+
+Essa seção exibe os termos mais buscados por outros clientes dentro do site.
+
+![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+
+## Últimas buscas efetuadas
+
+Essa seção exibe as últimas buscas efetuadas pelo cliente. Assim, é possível  iniciar a interação com a busca instantaneamente.
+
+![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+
+## Sugestão de buscas
+
+Essa seção apresenta os termos pesquisados por outros usuários que se relacionam com a busca efetuada naquele momento. Além de termos, também são sugeridas categorias que estejam relacionadas com a busca.
+
+![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+
+## Sugestão de produtos
+
+Essa seção apresenta os produtos que correspondem a busca efetuada naquele momento. Dessa forma, ao mostrar produtos relacionados a sua busca durante a sua digitação, diminui as desistências e dá a possibilidade do usuário efetuar uma compra mais dinâmica.
+
+![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tutorials/pt/availability.md b/docs/tutorials/pt/availability.md
new file mode 100644
index 000000000..ddf209e18
--- /dev/null
+++ b/docs/tutorials/pt/availability.md
@@ -0,0 +1,32 @@
+---
+title: 'Disponibilidade'
+id: 3ZcZOzTSr2RdauUbn7qTa9
+status: PUBLISHED
+createdAt: 2024-06-24T17:51:07.903Z
+updatedAt: 2024-06-24T18:00:08.767Z
+publishedAt: 2024-06-24T18:00:08.767Z
+firstPublishedAt: 2024-06-24T18:00:08.767Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: disponibilidade
+locale: pt
+legacySlug: disponibilidade
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Para montar um resultado de busca, o VTEX Intelligent Search considera a disponibilidade de cada produto encontrado na pesquisa. Produtos disponíveis serão sempre priorizados em relação a produtos sem disponibilidade nos resultados de busca. 
+
+Ao verificar a disponibilidade do produto, o VTEX Intelligent Search utiliza o campo **Mostrar produto esgotado** cadastrado no [Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ) para verificar quais produtos serão exibidos mesmo quando indisponíveis. Se a configuração do produto determinar que ele não deve ser exibido quando estiver fora de estoque, a plataforma não apresentará o produto. No entanto, se a configuração indicar que o produto deve ser exibido mesmo quando estiver sem estoque, a plataforma o colocará no final dos resultados de busca.
+
+Além da exibição do produto sem estoque, o VTEX Intelligent Search também verifica se:
+
+- O produto em questão está ativo.
+- Pelo menos um SKU do produto está ativo.
+- A categoria do produto está ativa.
+- A marca do produto está ativa.
+- O campo **Exibir no site** do produto está configurado como ativo.
+
+Após checar a disponibilidade, o sistema combina itens da sua loja, do catálogo de [sellers](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) e as configurações de [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) cadastradas para chegar ao preço e ao estoque finais. Se algum desses itens possuir preço e estoque, o produto está disponível. Sempre que o estoque e o preço do produto são alterados, uma nova [indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) é agendada e essas informações são atualizadas.
+
+É possível adicionar outros fatores, como [Relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) e [Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), para incrementar o resultado. Contudo, a disponibilidade ainda será o critério mais importante para o resultado da busca. 
diff --git a/docs/tutorials/pt/b2b-checkout-settings.md b/docs/tutorials/pt/b2b-checkout-settings.md
new file mode 100644
index 000000000..282c9d80e
--- /dev/null
+++ b/docs/tutorials/pt/b2b-checkout-settings.md
@@ -0,0 +1,71 @@
+---
+title: 'Configurações de Checkout no B2B'
+id: u7wG1SjmeCqXCSF2UsVok
+status: PUBLISHED
+createdAt: 2024-07-26T14:09:31.973Z
+updatedAt: 2024-07-26T19:06:26.485Z
+publishedAt: 2024-07-26T19:06:26.485Z
+firstPublishedAt: 2024-07-26T18:46:07.935Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configuracoes-de-checkout-no-b2b
+locale: pt
+legacySlug: configuracoes-de-checkout-no-b2b
+subcategory: 6sgdAY3pCuZ7qNws6gnzDX
+---
+
+O aplicativo Configurações de Checkout no B2B faz parte da solução [B2B Suite](https://help.vtex.com/pt/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3) da VTEX, uma coleção de aplicativos que permitem às lojas gerenciar organizações, papéis e permissões de storefront, além das configurações de checkout para relações comerciais B2B.
+
+As transações B2B (business-to-business) são mais complexas do que as transações B2C (business-to-consumer). Empresas B2B lidam frequentemente com:
+
+- Pedidos de grande volume.
+- Contratos personalizados.
+- Condições de pagamento específicos.
+- Uma gama diversificada de clientes.
+
+No comércio B2B, é necessário fornecer opções personalizadas durante o checkout, essas personalizações incluem:
+
+- Disponibilizar meios de pagamento para cada organização ou centro de custo.
+- Predefinir endereços.
+- Adicionar um campo para inserção do número de pedido de compra.
+- Oferecer a opção de criar uma cotação de pedido antes de fazer uma compra real.
+
+O aplicativo Configurações de Checkout no B2B funciona em conjunto com outros aplicativos da [B2B Suite](https://help.vtex.com/pt/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3) para estender a experiência de checkout para usuários que são membros de uma organização.
+
+## Perfis de acesso ao Checkout
+Este aplicativo verifica automaticamente os perfis dos usuários que fazem parte da organização e se comunica com o aplicativo [Organizações B2B](https://help.vtex.com/pt/tutorial/b2b-suite-overview--5eG6UfveWrai7looK0kVG3#aplicativo-organizacoes-b2b). Ele também confirma se os usuários possuem as [permissões](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) necessárias para acessar o checkout ao interagir com o aplicativo [*Storefront Permissions*](https://help.vtex.com/pt/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA).
+
+Por padrão, qualquer usuário com perfil que permite acesso ao storefront pode acessar o checkout, exceto aqueles com o perfil de Comprador da Organização. Se um usuário tentar prosseguir para o checkout sem a permissão necessária, ele receberá uma notificação com a mensagem: *Você não tem acesso ao checkout*.
+
+## Endereços do centro de custos
+O aplicativo Configurações de Checkout no B2B se comunica com o aplicativo [Organizações B2B](https://help.vtex.com/pt/tutorial/b2b-suite-visao-geral--5eG6UfveWrai7looK0kVG3#aplicativo-organizacoes-b2b) e lista automaticamente os endereços do centro de custos associados ao usuário durante a etapa do checkout.
+
+## Campo de número de ordem de compra
+Uma ordem de compra (PO) é um acordo comercial entre uma empresa compradora e uma loja B2B autorizando o pagamento por produtos ou serviços a serem entregues no futuro, dentro de um prazo específico.
+
+Ter um número de ordem de compra permite que os clientes B2B paguem por compras autorizadas referenciando esse número. A ordem de compra é autorizada e emitida antecipadamente pela empresa que está fazendo a compra.
+
+Usando as **Configurações de Checkout no B2B**, é possível habilitar um campo opcional de Número de Referência ou ordem de compra para que os clientes insiram essa informação durante a etapa do checkout.
+
+## Configurações de Checkout personalizadas para B2B
+As lojas B2B exigem personalizações específicas no processo de checkout. Por isso, as Configurações de Checkout no B2B oferecem uma página de checkout personalizada, ideal para esses cenários. Esse recurso permite que você personalize sua página de checkout conforme as necessidades da sua loja.
+
+Na seção abaixo, veremos como configurar o aplicativo Checkout B2B.
+
+### Configurando o aplicativo Checkout B2B
+Siga as instruções abaixo para personalizar o processo de checkout B2B na sua loja:
+
+<ol start="1">
+<li>No Admin VTEX, acesse <strong>Configurações da loja > Storefront > Configurações de checkout B2B</strong>, ou digite <strong>Configurações de checkout B2B</strong> na barra de busca no topo da página.</li>
+<li>Ao habilitar <code>Mostrar campo do número da ordem de compra (OC)</code>, será incluído à página de compra na etapa do checkout, um campo para preenchimento do número da ordem de compra.</li>
+<li>Ao habilitar <code>Mostrar botão Criar uma cotação</code>, será adicionado o botão <code>Criar uma cotação</code> no checkout, que permite criar um orçamento usando o conteúdo atual do carrinho.</li>
+</ol>
+
+<div class = "alert alert-info">
+Você deve habilitar o botão <code>Criar uma Cotação</code> somente se sua loja tiver o aplicativo Cotações B2B instalado. Para mais informações acesse <a href="https://developers.vtex.com/docs/apps/vtex.b2b-quotes">B2B Quotes & Carts</a>.
+</div>
+
+<ol start="4">
+<li>Clique em <code>Salvar</code>.</li>
+</ol>
diff --git a/docs/tutorials/pt/b2b-cost-center-management.md b/docs/tutorials/pt/b2b-cost-center-management.md
new file mode 100644
index 000000000..cff8f8322
--- /dev/null
+++ b/docs/tutorials/pt/b2b-cost-center-management.md
@@ -0,0 +1,101 @@
+---
+title: 'Gerenciamento de centro de custo no B2B'
+id: 2fjt1Layng8iKdvEEzRhuk
+status: PUBLISHED
+createdAt: 2024-07-25T10:55:43.882Z
+updatedAt: 2024-07-25T16:15:44.248Z
+publishedAt: 2024-07-25T16:15:44.248Z
+firstPublishedAt: 2024-07-25T13:38:42.344Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gerenciamento-de-centro-de-custo-no-b2b
+locale: pt
+legacySlug: gerenciamento-de-centro-de-custo-no-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+No contexto das organizações B2B, os centros de custos representam unidades de negócios ou departamentos que estão vinculados a uma organização específica. A funcionalidade permite o gerenciamento e a associação de centros de custos relevantes à sua organização, o que facilita a atribuição e análise de despesas financeiras.
+
+## Adicionando um centro de custo
+Para adicionar um centro de custo por meio do Admin VTEX, acesse **Aplicativos > Organizações e Centros de Custo B2B > Organizações** ou digite **Organizações** na barra de busca no topo da página.
+
+Para adicionar um novo centro de custo, siga estes passos:
+
+<ol>
+  <li>Clique sobre o nome da organização.</li>
+  <li>Clique na aba Centros de Custo.</li>
+  <li>Clique em <code>Novo</code>.</li>
+  <li>
+    Preencha os campos necessários sobre o centro de custo, conforme as informações abaixo:
+    <ul>
+      <li><strong>Nome</strong>: nome do centro de custo associado à organização.</li>
+      <li><strong>Número de telefone</strong>: número de telefone para contato com a organização.</li>
+      <li><strong>Documento comercial</strong>: CNPJ, número de identificação fiscal, número do IVA ou outro documento.</li>
+      <li><strong>Inscrição estadual</strong>: número de registro da empresa.</li>
+      <li><strong>País</strong>: país onde o centro de custo está localizado.</li>
+      <li><strong>CEP</strong>: código postal do endereço do centro de custo.</li>
+      <li><strong>Endereço</strong>: nome da rua onde o centro de custo está localizado.</li>
+      <li><strong>Número</strong>: número do endereço onde o centro de custo está localizado.</li>
+      <li><strong>Complemento e referência</strong>: informação que possa complementar o endereço do centro de custo.</li>
+      <li><strong>Bairro</strong>: nome do bairro onde o centro de custo está localizado.</li>
+      <li><strong>Cidade</strong>: cidade onde o centro de custo está localizado. Esse campo é preenchido automaticamente com base no CEP informado.</li>
+      <li><strong>Estado</strong>: estado onde o centro de custo está localizado. Isso é preenchido automaticamente com base no CEP informado.</li>
+      <li><strong>Destinatário</strong>: nome da pessoa que receberá os pedidos no endereço informado.</li>
+    </ul>
+  </li>
+  <li>Clique no botão <code>Adicionar</code>.</li>
+  <li>Clique em <code>Salvar</code> no canto superior direito da página após realizar qualquer alteração.</li>
+</ol>
+
+## Detalhes do centro de custo
+Para visualizar, adicionar ou editar os detalhes de um centro de custo no Admin VTEX, acesse **Aplicativos > Organizações e Centros de Custo B2B > Organizações** ou digite **Organizações** na barra de busca no topo da página.
+
+Para adicionar um centro de custo, siga as informações abaixo:
+
+1. Clique sobre o nome da organização.
+2. Clique na aba **Centros de custo**.
+3. Clique em `Novo` e preencha os campos do formulário.
+4. Para adicionar informações, clique no centro de custo e preencha os campos.
+5. Clique em `Adicionar`. 
+
+### Formulário do centro de custo
+O formulário para visualizar ou editar o centro de custo está dividido nas seguintes sessões:
+- [Campos de informações](#campos-de-informacoes)
+- [Endereços](#enderecos)
+- [Campos personalizados](#campos-personalizados)
+
+#### Campos de informações
+Nesta página de detalhes, você pode visualizar ou editar os seguintes campos:
+- **Nome:** nome do centro de custo associado à organização.
+- **Número do telefone:** número de telefone para contato com a organização.
+- **Documento comercial:**  CNPJ, número de identificação fiscal, número do IVA ou outro documento.
+- **Inscrição estadual:** número de registro da empresa.
+
+#### Endereços
+Para editar ou excluir um endereço existente, clique nos <i class="fas fa-ellipsis-v" aria-hidden="true"></i> e selecione `Editar` ou `Excluir`.
+
+Se deseja adicionar um novo endereço de entrega relacionado a esse centro de custo, siga estas instruções:
+
+<ol>
+  <li>Clique no botão <code>Adicionar novo endereço</code>.</li>
+  <li>
+    Preencha as informações necessárias sobre o novo endereço:
+    <ul>
+      <li><strong>País</strong>: país onde o centro de custo está localizado.</li>
+      <li><strong>CEP</strong>: código postal do endereço do centro de custo.</li>
+      <li><strong>Endereço</strong>: nome da rua onde o centro de custo está localizado.</li>
+      <li><strong>Complemento e referência</strong>: informação que possa complementar o endereço do centro de custo.</li>
+      <li><strong>Cidade</strong>: cidade onde o centro de custo está localizado. Isso é preenchido automaticamente com base no código postal informado.</li>
+      <li><strong>Estado</strong>: estado onde o centro de custo está localizado. Isso é preenchido automaticamente com base no código postal informado.</li>
+      <li><strong>Destinatário</strong>: nome da pessoa que receberá os pedidos no endereço informado.</li>
+    </ul>
+  </li>
+  <li>Clique no botão <code>Adicionar</code>.</li>
+  <li>Clique em <code>Salvar</code> no canto superior direito da página após realizar qualquer alteração.</li>
+  <li>Clique em <code>Excluir</code> para remover o centro de custo.</li>
+</ol>
+
+#### Campos personalizados
+Os campos personalizados permitem que os usuários adicionem informações relevantes para a empresa. Para mais informações, acesse [Campos personalizados no cadastro de organização](https://help.vtex.com/pt/tutorial/campos-personalizados-no-cadastro-de-organizacao--2MqEVusOvcbqagNwOuHA7f).
+
diff --git a/docs/tutorials/pt/b2b-organization-general-settings.md b/docs/tutorials/pt/b2b-organization-general-settings.md
new file mode 100644
index 000000000..0119bd7ae
--- /dev/null
+++ b/docs/tutorials/pt/b2b-organization-general-settings.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurações gerais da organização B2B'
+id: 6OSJHuiJJ7beRZaflNtzx5
+status: PUBLISHED
+createdAt: 2024-06-07T11:34:25.125Z
+updatedAt: 2024-06-07T11:45:51.047Z
+publishedAt: 2024-06-07T11:45:51.047Z
+firstPublishedAt: 2024-06-07T11:44:14.228Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configuracoes-gerais-da-organizacao-b2b
+locale: pt
+legacySlug: configuracoes-gerais-da-organizacao-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+A página de configurações gerais permite que o usuário cadastre as informações básicas de cada organização B2B integrada na VTEX.
+
+No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+
+1. Clique sobre o nome da Organização.
+2. Clique na aba Gerais.
+3. Preencha as informações necessárias:
+
+    - **Nome da organização:** nome da organização inserida no momento do cadastro.
+    - **Nome fantasia:** nome fantasia utilizado pela empresa.
+    - **Status:** indica se o cadastro desta organização compradora está ativa.
+    - **Campos personalizados:** contém campos adicionais de uma organização.
+
+![Configurações gerais organizações - PT](//images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/a430fb63e7953d706e1a2a60bdd4a339/Configura__es_gerais_organiza__es_-_PT.gif)
+
+Certifique-se de clicar em `Salvar` no canto superior direito da página após realizar qualquer alteração.
diff --git a/docs/tutorials/pt/b2b-overview.md b/docs/tutorials/pt/b2b-overview.md
index 960fe8ce4..9130e3e44 100644
--- a/docs/tutorials/pt/b2b-overview.md
+++ b/docs/tutorials/pt/b2b-overview.md
@@ -3,8 +3,8 @@ title: 'B2B – Visão Geral '
 id: 5vb9SNXhX2bZnkpAh7ADdC
 status: PUBLISHED
 createdAt: 2021-03-30T12:31:10.644Z
-updatedAt: 2021-05-11T17:43:13.209Z
-publishedAt: 2021-05-11T17:43:13.209Z
+updatedAt: 2024-05-10T13:56:48.012Z
+publishedAt: 2024-05-10T13:56:48.012Z
 firstPublishedAt: 2021-03-30T18:43:45.812Z
 contentType: tutorial
 productTeam: B2B
@@ -12,7 +12,7 @@ author: 7qy2DBsUp8U5P9lqV0JHfR
 slug: b2b-visao-geral
 locale: pt
 legacySlug: visao-geral
-subcategory: 5N5GjDrKSycIQMeoS7CLtj
+subcategory: 1PSq4adEARlFaK5Mdv74Y7
 ---
 
 É comum separar o ecommerce em dois tipos de modelo de negócios: B2C (Business to Consumer) e B2B (Business to Business).
diff --git a/docs/tutorials/pt/b2b-store-settings.md b/docs/tutorials/pt/b2b-store-settings.md
new file mode 100644
index 000000000..e2c7759ca
--- /dev/null
+++ b/docs/tutorials/pt/b2b-store-settings.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurando lojas B2B'
+id: 7riBcnrOv4Cz7qMeACyVLm
+status: PUBLISHED
+createdAt: 2023-10-11T15:17:39.003Z
+updatedAt: 2024-06-06T16:33:44.798Z
+publishedAt: 2024-06-06T16:33:44.798Z
+firstPublishedAt: 2023-10-19T13:27:04.087Z
+contentType: tutorial
+productTeam: B2B
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: configurando-lojas-b2b
+locale: pt
+legacySlug: configurando-lojas-b2b
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+Nesta página, você verá o passo a passo de como realizar as configurações gerais de sua loja B2B. 
+
+1. No seu Admin, acesse Apps > B2B Organizations & Cost Centers > Organizations e clique na aba de Settings, ou pesquise por Settings na barra de busca do seu admin.
+2. Defina as configurações gerais.
+
+- **Auto approve new organizations:** selecionando essa opção, você ativará a função de aprovar automaticamente novas organizações;
+- **Make business document ready only:**  selecionando esta opção, o comprador não poderá alterar o campo de business document.
+- **Make state registration ready only:** selecionando esta opção, o comprador não poderá alterar o campo de state registration.
+- **Use modal to switch company:** esta opção melhorará a experiência de usuário, facilitando a manutenção de lojas. 
+- **Clear cart when switching company or logging in:** ao selecionar essa configuração, o carrinho será limpo automaticamente em situações de mudança de loja ou login em contas.
+
+## Condições de pagamento
+É possível adicionar métodos de pagamento que façam sentido para o seu negócio. Basta selecionar os métodos que deseja incluir em sua loja. 
+
+__Exemplo:__ Boleto, Cartão de Débito e Crédito, Crédito da loja. 
+![Configurando lojas B2B - General Settings + Payment Terms](//images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/96c225444f6aec8c294d0cf836c1ead1/image1.jpg)
+## Tabelas de preço
+Você poderá adicionar um padrão de preços das lojas adicionadas. Os valores serão default. Para entender mais sobre a criação de tabelas, acesse [Pricing](https://developers.vtex.com/docs/guides/pricing-overview).
+
+## Políticas Comerciais
+
+É possível vincular sua loja diretamente a políticas comerciais e canais de vendas.
+1. Na tabela **Políticas comerciais disponíveis**, clique no vínculo que deseja incluir em sua loja e depois clique em `Adicionar Política Comercial`, e ela aparecerá na tabela **Políticas comerciais Selecionadas**.
+![Configurando lojas B2B -  Políticas comerciais ](//images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/632b5c714318cf0d613393c2d39083dd/image2.jpg)
+2. Ao finalizar as configurações, clique em `Salvar`.
+
diff --git a/docs/tutorials/pt/b2b-suite-overview.md b/docs/tutorials/pt/b2b-suite-overview.md
new file mode 100644
index 000000000..fd8dfb3e5
--- /dev/null
+++ b/docs/tutorials/pt/b2b-suite-overview.md
@@ -0,0 +1,89 @@
+---
+title: 'B2B Suite - Visão geral'
+id: 5eG6UfveWrai7looK0kVG3
+status: PUBLISHED
+createdAt: 2024-05-09T10:31:51.517Z
+updatedAt: 2024-05-10T18:37:56.917Z
+publishedAt: 2024-05-10T18:37:56.917Z
+firstPublishedAt: 2024-05-10T11:07:09.230Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: b2b-suite-visao-geral
+locale: pt
+legacySlug: b2b-suite-visao-geral
+subcategory: 1PSq4adEARlFaK5Mdv74Y7
+---
+
+
+O **B2B Suite** é uma coleção de aplicativos [VTEX IO](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-io) que permite às lojas gerenciarem organizações, permissões de acesso e configurações de checkout para relações comerciais B2B, entre outras funções. Esses recursos são importantes para simplificar o fluxo de compra, reduzir custos e fornecer uma experiência de compra personalizada.
+
+Clientes B2B têm papéis diferentes dentro de sua organização, como compradores, gerentes ou supervisores. Cada papel está associado a um conjunto diferente de permissões de loja, dependendo das ações que o usuário precisa realizar.
+
+O B2B atende a algumas necessidades essenciais, incluindo:
+
+- **Agrupamento de usuários:** centralização de diferentes usuários da mesma empresa em uma única organização, promovendo uma gestão unificada.
+
+- **Métodos de pagamento personalizado:** configuração de métodos de pagamento específicos para cada cliente, atendendo às suas necessidades particulares.
+
+- **Seleção e precificação de produtos:** adaptação das seleções de produtos e estruturação de preços individualizados para cada cliente, essencial para transações B2B.
+
+Durante o processo de checkout, é importante oferecer opções personalizadas para atender às necessidades específicas dos clientes B2B. Essas personalizações incluem:
+
+- **Seleção de Métodos de Pagamento:** permite a escolha de métodos de pagamento específicos por organização ou centro de custo.
+- **Endereços pré-preenchidos:** automatiza o preenchimento de endereços para agilizar o processo de checkout.
+- **Números de pedido de compra:** facilitar a inclusão de números de pedido de compra, essenciais para a rastreabilidade e controle.
+- **Cotações de pedidos:** oferece a possibilidade de obter cotações para pedidos durante o Checkout.
+
+## Instalando o B2B Suite em sua loja
+
+Para instalar o B2B Suite, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Aplicativos > App Store** ou digite **App Store** na barra de busca no topo da página.
+2. Na página do App Store, localize o **B2B Suite** na lista de Apps exibidos ou digite **B2B Suite** na barra de busca da página.
+3. Em seguida, clique para instalar o App.
+
+![Instalação B2B Suite - PT](//images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/26332dc3085e6ff753cb644524a0ec61/Instala__o_B2B_Suite_-_PT.gif)
+
+## Conjunto de aplicativos do B2B Suite
+
+Os aplicativos essenciais que compõem o **B2B Suite** foram desenvolvidos para impulsionar as operações de negócios B2B, e serão apresentados a seguir.
+
+### Aplicativo Permissões da loja
+
+Armazena um conjunto predefinido de perfis e permissões relacionadas ao que os usuários B2B podem acessar e fazer na loja online. É útil para operações que desejam definir permissões específicas para usuários com diferentes funções organizacionais.
+
+### Aplicativo Interface de permissões da loja
+
+É o aplicativo responsável por gerar uma interface para o app permissões da loja, permitindo que os usuários do Admin VTEX gerenciem funções B2B e permissões de aplicativos associadas por meio do próprio Admin.
+
+### Aplicativo Organizações B2B
+
+Permite agrupar usuários B2B em organizações às quais podem ser atribuídas métodos de pagamento específicos, tabelas de preços e coleções de produtos. Isso possibilita que todos os usuários da organização compartilhem as mesmas condições comerciais.
+
+Cada organização pode ser segmentada em um ou mais centros de custos, com seus próprios endereços de entrega, que estarão disponíveis para os usuários do centro de custos no momento do Checkout.
+
+#### **Estrutura Organizacional**
+
+- **Organização compradora:** representa uma empresa ou organização que realiza compras por meio da plataforma, podendo ter múltiplos usuários associados e acessar recursos específicos relacionados às suas necessidades comerciais.
+
+- **Usuários:** são membros ou colaboradores de uma organização B2B que possuem autorização para acessar e operar a plataforma B2B Suite em nome da organização. Eles desempenham papéis específicos no processo de compra, como realizar pedidos, gerenciar catálogos de produtos ou aprovar transações. Cada usuário tem acesso controlado aos recursos da plataforma com base em suas atribuições e permissões específicas.
+
+- **Centro de custos:** é uma categoria ou setor dentro de uma organização B2B designada a rastrear e atribuir custos associados a atividades específicas ou departamentos da empresa. Ele permite que a empresa acompanhe de forma mais detalhada e precisa os gastos relacionados a diferentes áreas de negócio, proporcionando uma gestão eficiente das despesas corporativas.
+
+### Aplicativo Cotações e carrinhos B2B
+
+Permite que os usuários B2B criem cotações e carrinhos salvos, que são compartilhados com outros membros de sua organização. Os usuários com as permissões apropriadas da loja podem modificar cotações para aplicar descontos ou alterar a quantidade de itens, para que a cotação resultante possa ser usada para fazer um pedido.
+
+### Aplicativo Configurações de Checkout B2B
+
+Amplia a experiência de checkout para usuários que são membros de organizações B2B. Com este aplicativo, você pode permitir métodos de pagamento específicos para a organização do usuário, fornecer endereços pré-preenchidos com base no centro de custos de cada usuário, adicionar um número de ordem de compra ao pedido e permitir que os clientes criem uma cotação de pedido antes de fazer o pedido.
+
+### Aplicativo Histórico de pedidos B2B
+
+Fornece uma nova página de Pedidos no [Minha Conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh) para que os usuários B2B possam visualizar todos os pedidos anteriores feitos por usuários em sua organização ou centro de custos, dependendo de sua função.
+
+### Aplicativo B2B Clientes
+
+Fornece capacidades adicionais de gerenciamento de informações do cliente no Admin VTEX, permitindo que os administradores da loja criem, editem e pesquisem clientes.
+
diff --git a/docs/tutorials/pt/b2b-trade-policies-overview.md b/docs/tutorials/pt/b2b-trade-policies-overview.md
new file mode 100644
index 000000000..aab372778
--- /dev/null
+++ b/docs/tutorials/pt/b2b-trade-policies-overview.md
@@ -0,0 +1,32 @@
+---
+title: 'Visão geral da política comercial no B2B'
+id: sKrYjDJPBChgIxzYFpUvu
+status: PUBLISHED
+createdAt: 2024-07-05T11:20:38.780Z
+updatedAt: 2024-07-05T11:34:04.566Z
+publishedAt: 2024-07-05T11:34:04.566Z
+firstPublishedAt: 2024-07-05T11:34:04.566Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: visao-geral-da-politica-comercial-no-b2b
+locale: pt
+legacySlug: visao-geral-da-politica-comercial-no-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Associar uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) à organização é essencial para uma operação B2B. Isso permite a aplicação de regras específicas de preços, descontos e condições de pagamento, proporcionando um gerenciamento personalizado das relações comerciais.
+
+O principal objetivo das políticas comerciais no B2B é garantir que todas as transações sigam as condições comerciais definidas pela empresa, proporcionando uma experiência de compra consistente e alinhada com as estratégias de negócios. Isso inclui:
+- Estabelecer preços específicos para produtos ou grupos de produtos, ajustando conforme necessário para diferentes clientes ou segmentos de mercado.
+- Configurar condições, prazos e meios de pagamento de forma customizada.
+- Implementar regras específicas para cálculo de frete e aplicação de impostos, conforme a localização e o perfil do cliente.
+
+Implementar e gerenciar corretamente essas políticas é importante para garantir uma operação B2B eficiente e alinhada com os objetivos estratégicos da empresa.
+
+## Associando uma política comercial
+1. No Admin VTEX, acesse **Aplicativos > Organizações > Organizações e centros de custo B2B > Organizações** ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar a página de detalhes.
+3. Clique na aba **Política comercial**.
+4. Selecione a política comercial que deseja associar à organização.
+5. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/bank-reconciliations.md b/docs/tutorials/pt/bank-reconciliations.md
index f4e53b749..5f274baff 100644
--- a/docs/tutorials/pt/bank-reconciliations.md
+++ b/docs/tutorials/pt/bank-reconciliations.md
@@ -36,7 +36,7 @@ Após receber o arquivo do banco e salvá-lo em sua máquina, conforme citado ac
 
 Assim que selecionar o arquivo, a plataforma começará a processá-lo e registrará no histórico quantos pagamentos foram conciliados com sucesso ou erro. Os pagamentos que forem conciliados com sucesso, atualizarão os status dos pedidos para Pagamento Aprovado.
 
-![upload-arquivo-ret](https://images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/73a25815cf3bd17cb7c92f6f01407f7e/uploadret.JPG)
+![upload-arquivo-ret](//images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/73a25815cf3bd17cb7c92f6f01407f7e/uploadret.JPG)
 
 ## Visualizar o histórico
 
@@ -48,7 +48,7 @@ Dentre os detalhes, é possível saber: o banco ao qual o boleto pertence, o tot
 2. Em **Histórico**, clique em uma das datas das operações de conciliação bancária realizadas.
 3. Em **Mais detalhes dos pagamentos**, clique em **Conciliados com Sucesso** ou **Não conciliados** para verificar os detalhes das operações realizadas em um determinado banco. 
 
-![historico-conciliacao](https://images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/f349ccb45ed613af59dca2de908fa01a/historico_conciliacao.jpg)
+![historico-conciliacao](//images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/f349ccb45ed613af59dca2de908fa01a/historico_conciliacao.jpg)
 
 ## Payclub
 
@@ -59,4 +59,4 @@ Aqui é possível fazer o download dos pagamentos do dia que foram feitos atrav
 3. Selecione a data que desejar no calendário.
 4. Clique em **Baixar arquivo**.
 
-![donwload-arquivo-conciliação](https://images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/61af99bfe4978eea981dfe694308f8f4/Download_Concilia____o.JPG)
+![donwload-arquivo-conciliação](//images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/61af99bfe4978eea981dfe694308f8f4/Download_Concilia____o.JPG)
diff --git a/docs/tutorials/pt/banners.md b/docs/tutorials/pt/banners.md
new file mode 100644
index 000000000..2ec153c42
--- /dev/null
+++ b/docs/tutorials/pt/banners.md
@@ -0,0 +1,69 @@
+---
+title: 'Banners'
+id: 72XytEoeqOAOiH05oVF0pH
+status: PUBLISHED
+createdAt: 2024-06-27T16:30:55.610Z
+updatedAt: 2024-06-27T16:31:52.889Z
+publishedAt: 2024-06-27T16:31:52.889Z
+firstPublishedAt: 2024-06-27T16:31:52.889Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: banners
+locale: pt
+legacySlug: banners
+subcategory: z6qcw06Z38YDu1fOcu9Jn
+---
+
+Banners é a funcionalidade do Intelligent Search responsável por exibir banners, como ações promocionais, na página de resultado de busca do cliente. A exibição do banner é baseada na análise do contexto de busca - incluindo termos e filtros selecionados - na jornada de compra do cliente. Também é possível configurar banners para cada uma das categorias existentes no seu catálogo, assim como para os departamentos e subcategorias.
+
+Com perfis diferentes, cada grupo de clientes da sua loja tem o seu próprio interesse. E as suas campanhas de marketing precisam levar isso em consideração para que sejam efetivas e consigam aumentar as taxas de conversão em vendas. A flexibilidade de configuração dos banners permite a criação de campanhas de marketing mais criativas, trabalhando o relacionamento da sua marca com o público de maneira individualizada.
+
+Vale ressaltar que essas configurações podem ser feitas tanto pelos termos quanto pelos filtros utilizados durante a busca. O cliente pesquisa por "tênis de corrida" e, ao cair no resultado de busca, ele pode filtrar por diversos atributos (“tamanho”, “tipo” e “marca”). Ao selecionar o filtro “nike”, caso tenha um banner da marca na loja, ele pode ser exibido para o cliente (filtro). 
+
+A partir da captura de contexto realizada pelo Intelligent Search, o sistema seleciona qual o conteúdo, previamente cadastrado, mais relevante para aquele cenário. 
+
+Por exemplo, se o cliente pesquisa por "tênis de corrida" e, ao cair no resultado de busca, ele pode filtrar por diversos atributos (“tamanho”, “tipo” e “marca”). Ao selecionar o filtro “nike”, caso tenha uma campanha da marca na loja, ela pode ser exibida para o cliente (filtro). O cliente também pode ser direcionado para uma promoção mais específica de tênis de corrida Nike (termo e filtro), caso tenha criado uma campanha e a relacionado com o banner.
+
+## Listagem de Banners
+
+No Admin VTEX, a página **Storefront** > **Banners** exibe a listagem dos banners cadastrados e permite que você realize as seguintes ações:
+
+* [Criar um banner](#criar-banner)
+* [Buscar por banners](#buscar-banner)
+* [Editar um banner](#editar-banner)
+* [Deletar um banner](#deletar-banner) 
+
+![banners-intro-pt](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
+
+A página apresenta as seguintes informações: 
+
+| Coluna | Descrição                |
+| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Nome             | Nome que identifica o banner, definido na etapa [Criar banner](#criar-banner). |
+| Posição          | Área que o banner aparecerá na página de resultado de busca.                                                                                                                 |
+| Data de início   | Data que define o início da disponibilidade do banner.                                                                                                                       |
+| Data de término  | Data que define o término da disponibilidade do banner.                                                                                                                      |
+| Ativo            | Opção que ativa ou desativa um banner.                                                                                                                                       |
+| Ações            | Ação de deletar ou editar um banner.                                                                                                                                         |
+
+### Criar banner
+
+Para configurar um banner, clique em `Novo`. Saiba mais sobre todas as informações necessárias para criar um Banner em [Configurar Banners](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
+
+### Buscar banner
+
+Para pesquisar um banner, digite o nome do banner na barra de busca.
+
+### Editar banner
+
+Você pode editar as informações um banner seguindo os passos abaixo.
+
+1. Clique no botão de lápis <i class="fa-solid fa-pencil"></i>.
+2. Altere a informação desejada do banner.
+3. Clique em `Salvar`.
+
+### Deletar banner
+
+Você pode deletar um banner clicando no botão de lixeira <i class="fa-solid fa-trash-can"></i>.
+
diff --git a/docs/tutorials/pt/best-practices-against-virtual-attacks.md b/docs/tutorials/pt/best-practices-against-virtual-attacks.md
index 0c0d9acd2..47edd3e57 100644
--- a/docs/tutorials/pt/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/pt/best-practices-against-virtual-attacks.md
@@ -3,8 +3,8 @@ title: 'Boas práticas contra ataques virtuais'
 id: 191rpbF7UgrKapVCi1PCDE
 status: PUBLISHED
 createdAt: 2022-04-06T19:04:13.387Z
-updatedAt: 2022-06-10T14:24:42.121Z
-publishedAt: 2022-06-10T14:24:42.121Z
+updatedAt: 2024-06-18T20:41:01.987Z
+publishedAt: 2024-06-18T20:41:01.987Z
 firstPublishedAt: 2022-04-06T19:23:22.326Z
 contentType: tutorial
 productTeam: Reliability
@@ -17,45 +17,56 @@ subcategory: 6uJgdHqWf1Mo0rUfgxseTn
 
 A VTEX dispõe de diversas proteções contra possíveis ataques a lojas. Ainda sim, há configurações e produtos terceiros que podem maximizar a segurança da sua operação. Este artigo descreve alguns destes recursos:
 
-- [Antifraude](#antifraude)
-- [Proteção contra ataques de transações](#protecao-contra-ataques-de-transacoes)
-- [reCAPTCHA no checkout](#recaptcha-no-checkout)
-- [Desabilitar login por senha](#desabilitar-login-por-senha)
+* [Antifraude](#antifraude)
+* [Proteção contra ataques de transações](#protecao-contra-ataques-de-transacoes)
+* [reCAPTCHA v3 no Checkout](#recaptcha-v3-no-checkout)
+* [Configurações do orderForm](#configuracoes-do-orderform)
+* [Desabilitar login por senha](#desabilitar-login-por-senha)
 
 <div class = "alert alert-info">
-As medidas citadas aqui não eliminam por completo a possibilidade de ataques, mas podem reduzir bastante a probabilidade, caso empregadas adequadamente.
+  <p>As medidas citadas neste guia não eliminam por completo a possibilidade de ataques, mas podem reduzir bastante a probabilidade deles acontecerem, caso empregadas adequadamente.</p>
 </div>
 
 ## Antifraude
 
-Antifraude é um sistema especializado em analisar compras de ecommerces, com o intuito de identificar operações fraudulentas. Este sistema analisa dados comportamentais dos compradores de um ecommerce e impede que compras suspeitas sejam realizadas.
+Sistemas antifraude são especializados em analisar compras de ecommerces com o intuito de identificar operações fraudulentas. Eles analisam dados comportamentais dos compradores e impedem que compras suspeitas sejam realizadas.
 
-Saiba mais sobre [sistemas antifraude](https://help.vtex.com/pt/tutorial/what-is-anti-fraud#) e como integrar à plataforma VTEX.
+Saiba mais sobre [sistemas antifraude](https://help.vtex.com/pt/tutorial/what-is-anti-fraud) e como utilizá-los na VTEX.
 
 <div class="alert alert-warning"> 
-Para aumentar a segurança, configure seu antifraude para todos os métodos de pagamento disponíveis na sua loja.
+  <p>Para aumentar a segurança, configure seu antifraude para todos os métodos de pagamento disponíveis na sua loja.</p>
 </div>
 
 ## Proteção contra ataques de transações
 
-Para acessar a documentação sobre este assunto, insira abaixo seu [nome de conta](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) VTEX, clique no botão e faça login no Admin.
+Para acessar a documentação sobre este assunto, insira abaixo seu [nome de conta](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) VTEX, clique no botão e faça login no Admin.
+
 <iframe src="https://help.vtex.com/insertaccountname?id=62oQBmi7UZlYlgb0Ha1hZ3" title="Insira seu nome de conta e clique no botão." frameBorder="0" width="400" height="50"></iframe>
 
-## reCAPTCHA no checkout
+## reCAPTCHA v3 no Checkout
 
 O reCAPTCHA é uma solução utilizada para validação de usuário real em pedidos que serão pagos com cartão de crédito ou débito. Ele previne cenários em que programas maliciosos são utilizados para fraudes.
 
-Saiba mais sobre como configurar esta validação no Checkout da sua loja em [reCAPTCHA no Checkout](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#).
+Recomendamos o uso do [reCAPTCHA v3](https://help.vtex.com/en/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-v3), que utiliza uma pontuação de qualidade em vez de uma validação via pop-up e, portanto, é mais difícil de ser burlado em tais cenários.
+
+Saiba mais sobre como configurar esta validação no Checkout da sua loja em [reCAPTCHA no Checkout](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#). Para a implementação do reCAPTCHA V3 em uma loja VTEX, consulte o guia para desenvolvedores [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
 
 <div class = "alert alert-info">
-A validação por reCAPTCHA também está ativa por padrão no fluxo de <a href=tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes>cadastro de cartões</a> dos clientes da loja, sem a necessidade de configuração por parte da loja.
+  <p>No fluxo de <a href="https://help.vtex.com/pt/tutorial/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes">cadastro de cartões</a> dos clientes da loja na página <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, a validação por reCAPTCHA está ativa por padrão, sem a necessidade de configuração por parte dos lojistas.</p>
 </div>
 
+## Configurações do orderForm
+
+Para acessar a documentação sobre este assunto, insira abaixo seu [nome de conta](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) VTEX, clique no botão e faça login no Admin.
+
+<iframe src="https://help.vtex.com/insertaccountname?id=7EAqNk48KP2QHnCxu856jT" title="Insira seu nome de conta e clique no botão." frameBorder="0" width="400" height="50"></iframe>
+
 ## Desabilitar login por senha
 
 Se sua loja está sofre ataques mesmo com a aplicação dos recursos citados acima, recomendamos desabilitar o login por senha. Essa medida pode ser aplicada temporariamente ou não, com o intuito de quebrar o fluxo da automação do ataque.
 
 Para realizar esta configuração:
+
 1. Acesse *Configurações da conta* > *Autenticação*.
 2. Desabilite o campo *senha*.
 
diff --git a/docs/tutorials/pt/best-practices-application-keys.md b/docs/tutorials/pt/best-practices-application-keys.md
index fccd496ba..3cf6ba4dd 100644
--- a/docs/tutorials/pt/best-practices-application-keys.md
+++ b/docs/tutorials/pt/best-practices-application-keys.md
@@ -1,9 +1,9 @@
 ---
 title: 'Boas práticas na utilização de chaves de aplicação'
 id: 7b6nD1VMHa49aI5brlOvJm
-status: PUBLISHED
+status: CHANGED
 createdAt: 2022-10-04T21:36:57.185Z
-updatedAt: 2022-10-04T21:41:08.638Z
+updatedAt: 2024-03-19T14:22:43.610Z
 publishedAt: 2022-10-04T21:41:08.638Z
 firstPublishedAt: 2022-10-04T21:41:08.638Z
 contentType: tutorial
@@ -22,6 +22,7 @@ Este tipo de credencial é utilizado para autenticação de identidade via API.
 </div>
 
 O manuseio inadequado de [chaves de aplicação](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) pode gerar vazamentos e, consequentemente, situações de acesso indevido. Conheça abaixo boas práticas que recomendamos para o gerenciamento destas credenciais, as quais você pode implementar para aumentar a segurança da sua loja.
+
 ## Rotacione chaves periodicamente
 
 É aconselhável que você desative chaves antigas e crie novas ao longo do tempo. Assim você garante que suas [chaves de aplicação](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) tenham duração determinada.
diff --git a/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md b/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md
new file mode 100644
index 000000000..87465342e
--- /dev/null
+++ b/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md
@@ -0,0 +1,73 @@
+---
+title: 'Melhores práticas para acessar a loja sem www'
+id: tutorials_4278
+status: PUBLISHED
+createdAt: 2017-04-27T21:51:11.002Z
+updatedAt: 2024-01-23T17:50:54.783Z
+publishedAt: 2024-01-23T17:50:54.783Z
+firstPublishedAt: 2017-04-27T23:11:15.960Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: melhores-praticas-para-acessar-a-loja-sem-www
+locale: pt
+legacySlug: configurando-acesso-sem-www
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+O [domínio principal](https://help.vtex.com/pt/tutorial/configurar-o-dominio-da-loja--tutorials_2450) de uma loja precisa ter um subdomínio, como `www` ou outro. Para acessar a loja utilizando um domínio puro – como `minhaloja.com`, que não tem um subdomínio – é preciso fazer um [redirecionamento](https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ). Neste guia, explicamos os motivos para essa necessidade e como realizar o redirecionamento. Confira as seções a seguir:
+
+* [Antes de começar](#antes-de-comecar)
+* [Desafios de domínios sem subdomínio](#desafios-de-dominios-sem-subdominio)
+* [Solução recomendada: Redirecionamento](#solucao-recomendada-redirecionamento)
+* [Solução alternativa: CNAME Flattening](#solucao-alternativa-cname-flattening)
+
+## Antes de começar
+
+Recomendamos a leitura dos seguintes guias para entender como funcionam domínios e a configuração de DNS na VTEX:
+
+* [Configurar o domínio da loja](https://help.vtex.com/pt/tutorial/configurar-o-dominio-da-loja--tutorials_2450)
+* [Como funciona a configuração de DNS na VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-configuracao-de-dns-na-vtex--2P5k3oMYOj7TgSK4Mrxmgy)
+
+## Limitações na configuração de DNS para domínios puros
+
+Nesta seção, exploramos a complexidade e os desafios relacionados à configuração do sistema de DNS para domínios puros. A gestão de domínios sem subdomínios demanda atenção especial, sobretudo para preservar a funcionalidade e a integridade do site, sem comprometer aspectos cruciais, como e-mails, segurança e certificados.
+
+### Redirecionamentos tipo A para domínios puros 
+
+A [configuração de DNS na VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-configuracao-de-dns-na-vtex--2P5k3oMYOj7TgSK4Mrxmgy) deve ser feita para o [domínio principal](https://help.vtex.com/pt/tutorial/configurar-o-dominio-da-loja--tutorials_2450) da loja, não sendo recomendado o uso de domínios puros. Um domínio puro, sem subdomínio, também conhecido como _naked domain_ (por exemplo, `minhaloja.com`, sem o `www`), implica na criação de uma configuração de tipo A (Address Record) no DNS. O registro A é usado para apontar diretamente o domínio para um endereço IP específico.
+
+No entanto, esse tipo de configuração não é recomendado. Não é possível usar configurações A que apontam diretamente para um endereço IP, pelos motivos a seguir:
+
+* **Risco de site inacessível:** Se um domínio puro estiver configurado com um registro A apontando para um endereço IP específico e esse endereço IP mudar, o site pode ficar inacessível até que o novo IP seja atualizado no registro A.
+* **Desempenho prejudicado:** Se o domínio puro apontar diretamente para um único endereço IP, os visitantes de todo o mundo seriam forçados a se conectar a esse único servidor, independentemente de sua localização. Isso pode levar a uma degradação do desempenho, pois os visitantes distantes teriam uma experiência mais lenta.
+
+### Redirecionamentos tipo CNAME para domínios puros
+
+O redirecionamento do tipo CNAME para domínios puros deve ser evitado. Um CNAME tem um comportamento parecido com um redirecionamento no contexto do DNS: quando alguém acessa `www.minhaloja.com`, o DNS encaminha automaticamente para `www.minhaloja.com.cdn.vtex.com`. Porém, de acordo com as regras do protocolo DNS, um CNAME não pode coexistir com outras configurações de DNS no mesmo domínio. Isso significa que, se usarmos um CNAME para redirecionar um site, todas as configurações desse site precisam seguir esse redirecionamento. Não é possível redirecionar apenas parte das configurações. 
+
+Esse comportamento cria um conflito direto com domínios puros, pois lojistas geralmente desejam configurar outras funcionalidades, como registros MX para e-mails, registros TXT para segurança, registros CAA para certificados e registros NS e SOA para provar que eles controlam o domínio puro.
+
+## Lidando com domínios puros
+
+Em vista das [limitações na configuração de DNS para domínios puros](https://help.vtex.com/pt/tutorial/como-funciona-a-configuracao-de-dns-na-vtex--2P5k3oMYOj7TgSK4Mrxmgy), essa seção apresenta as práticas recomendadas para garantir que a loja seja acessível sem a necessidade do prefixo `www`.
+
+### Solução recomendada: Redirecionamentos
+
+A VTEX recomenda sempre usar o `www` ou outro subdomínio ao [configurar o domínio principal](https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450) da loja, visando conciliar a necessidade de utilizar CNAMEs e outras configurações. Neste cenário, recomenda-se usar redirecionamentos para acessar o endereço sem `www` ou outros subdomínios. Para saber como configurar redirecionamentos, leia [Redirecionamento de outros endereços](https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ).
+
+Alguns provedores de DNS suportam CNAMEs no domínio puro ([CNAME Flattening](#solucao-alternativa-cname-flattening)). No entanto, essa opção pode não ser oferecida por todos os provedores. Portanto, recomendamos o uso obrigatório do  subdomínio para garantir que todas as funcionalidades necessárias possam coexistir.
+
+### Solução alternativa: CNAME Flattening
+
+A VTEX recomenda, por padrão, usar um subdomínio `www` para evitar problemas relacionados à dinamicidade dos IPs no CDN. Porém, algumas empresas de hospedagem e serviços de DNS oferecem uma solução alternativa para contornar esse problema, chamada [CNAME Flattening](https://developers.cloudflare.com/dns/cname-flattening/).
+
+O CNAME Flattening é uma técnica que permite associar um domínio puro diretamente a um CNAME, em vez de um registro A. Com isso, você pode configurar um domínio puro (sem subdomínio) para funcionar em conjunto com um CDN, mesmo quando os IPs sofrem alterações. No entanto, essa funcionalidade não é suportada por todos os provedores de DNS.
+
+Alguns provedores de DNS, como o [Cloudflare](https://www.cloudflare.com/pt-br/), oferecem suporte para o CNAME Flattening. Nesse caso, é possível configurar o domínio puro com um CNAME que aponte para o serviço de CDN da VTEX. Isso permite que o domínio puro funcione de maneira semelhante ao subdomínio `www` e ainda se alavanque dos benefícios do CDN.
+
+Portanto, se você deseja usar um domínio puro com um CDN em uma configuração específica, a primeira etapa é verificar se o seu provedor de DNS suporta o CNAME Flattening. Se sim, você poderá configurar o domínio puro dessa forma.
+
+<div class="alert alert-warning">
+  <p>Quando utilizada, a solução de DNS Flattening implica o mesmo comportamento de um <a href="https://help.vtex.com/pt/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir">proxy-reverso</a>. Nesse caso, é necessário configurar uma entrada TXT de verificação.</p>
+</div>
diff --git a/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md b/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md
new file mode 100644
index 000000000..deef4e709
--- /dev/null
+++ b/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md
@@ -0,0 +1,171 @@
+---
+title: 'Boas práticas para o sucesso da sua loja VTEX'
+id: ItKyLqcRl9wNADMhYH8O4
+status: PUBLISHED
+createdAt: 2024-05-24T21:33:12.690Z
+updatedAt: 2024-05-24T22:42:51.899Z
+publishedAt: 2024-05-24T22:42:51.899Z
+firstPublishedAt: 2024-05-24T22:42:51.899Z
+contentType: tutorial
+productTeam: Others
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: boas-praticas-para-o-sucesso-da-sua-loja-vtex
+locale: pt
+legacySlug: boas-praticas-para-o-sucesso-da-sua-loja-vtex
+subcategory: 4PeX73EGpmULh9Ip5F4XER
+---
+
+Este artigo apresenta algumas das principais práticas para você gerenciar sua loja VTEX com eficiência e facilidade, e promover a escalabilidade da sua operação. O conteúdo está organizado da seguinte forma:
+
+* **[Performance e segurança](#performance-e-seguranca)**
+    * [Mantenha a arquitetura da sua loja documentada](#mantenha-a-arquitetura-da-sua-loja-documentada)
+    * [Siga as orientações de segurança do checkout](#siga-as-orientacoes-de-seguranca-do-checkout)
+    * [Controle o nível de permissão de acessos](#controle-o-nivel-de-permissao-de-acessos)
+    * [Conheça nossos marketplaces certificados e parceiros](#conheca-nossos-marketplaces-certificados-e-parceiros)
+* **[Atualizações e novidades](#atualizacoes-e-novidades)**
+    * [Acompanhe nossos lançamentos e novidades](#acompanhe-nossos-lancamentos-e-novidades)
+    * [Receba notificações de status da plataforma](#receba-notificacoes-de-status-da-plataforma)
+    * [Conheça nossos conteúdos de onboarding](#conheca-nossos-conteudos-de-onboarding)
+* **[Comunidade e suporte](#comunidade-e-suporte)**
+    * [Participe da VTEX Community](#participe-da-vtex-community)
+    * [Conheça boas práticas em solicitações do Suporte VTEX](#conheca-boas-praticas-em-solicitacoes-do-suporte-vtex)
+
+<div class = "alert alert-info">
+<b>Agências parceiras</b><p>Existem diversas agências e parceiros de implementação que foram certificados pela VTEX por terem demonstrado excelência e confiabilidade em projetos com a plataforma. Portanto, seja para uma implementação eficiente, uma arquitetura de loja personalizada ou para obter apoio contínuo na infraestrutura, recomendamos a contratação de agências parceiras. Para conferir nossos parceiros, acesse o <a href="https://partnerportal.vtex.com/parceiros">Partner Portal</a> (somente português) ou acesse <a href="http://VTEX.com">VTEX.com</a> (demais idiomas).</p>
+</div>
+
+## Performance e segurança
+
+Nesta seção, conheça boas práticas para promover a eficiência da performance e a segurança da sua operação.
+
+### Mantenha a arquitetura da sua loja documentada
+
+Uma operação de ecommerce muitas vezes envolve a integração de diferentes sistemas e tecnologias. Manter uma documentação atualizada da [arquitetura da loja](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#arquitetura-da-loja) é estratégico para garantir a melhor performance da estrutura e dos profissionais envolvidos.
+
+Os principais benefícios em criar uma documentação da arquitetura da sua operação e mantê-la atualizada são:
+
+* **Eficiência na implementação e manutenção:** a fase inicial do desenvolvimento da loja se torna mais rápida e a manutenção da operação é feita com mais facilidade. Manter a documentação da arquitetura diminui a dependência de profissionais com contexto prévio e otimiza a colaboração entre as partes envolvidas.
+* **Facilidade para evoluir:** a documentação da arquitetura da loja diminui a fricção para realizar mudanças, contribuindo para a capacidade do seu negócio de inovar.
+* **Decisões bem informadas:** entender o funcionamento da loja permite que os líderes executivos tomem decisões bem informadas sobre infraestrutura.
+* **Atuação rápida em questões de segurança:** a correção de problemas ou vulnerabilidades de segurança são mais rápidas quando a documentação da arquitetura é compartilhada.
+* **Otimização do suporte:** quando é necessário apoio do nosso suporte ou de terceiros, compartilhar a documentação da arquitetura facilita a comunicação entre as partes e a eficácia de sua atuação.
+
+<div class = "alert alert-info">
+Com relação a documentar a arquitetura da loja, veja a página <a href="https://developers.vtex.com/docs/guides">Get started</a> no nosso portal para desenvolvedores, e conheça o <a href="https://assets.vtex.com/4524045/">framework interativo</a> da plataforma VTEX.
+</div>
+
+### Siga as orientações gerais de segurança
+
+Existem estratégias para prevenir e reduzir a exposição da sua loja ao risco de ataques maliciosos. Algumas das principais são:
+
+* **Antifraude:** configure um sistema [antifraude](https://help.vtex.com/pt/tutorial/what-is-anti-fraud) para todos os métodos de pagamento da sua loja.  
+* **reCAPTCHA:** use o [reCAPTCHA](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#) para se prevenir de fraudes com falsos usuários criados por programas maliciosos.
+* **Autenticação:** caso sua loja esteja sofrendo ataques recorrentes, considere desabilitar o login por senha e optar por outra forma de [autenticação](https://help.vtex.com/pt/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) para os clientes da sua loja.
+
+<div class = "alert alert-info">
+Para mais informações sobre ações preventivas, veja o artigo <a href="https://help.vtex.com/pt/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE">Boas práticas contra ataques virtuais</a> e este <a href="https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470">post na VTEX Community</a>.
+</div>
+
+### Controle o nível de permissão de acessos
+
+Com relação à [segurança de lojas VTEX](https://help.vtex.com/pt/subcategory/seguranca-para-lojistas--6uJgdHqWf1Mo0rUfgxseTn), existem medidas preventivas e [boas práticas](https://help.vtex.com/pt/tutorial/boas-praticas-para-evitar-golpes-que-utilizam-a-marca-da-vtex--6uPwUr2Fnj2m3TM4hAj2Ec) que aumentam o nível de segurança do seu negócio, sendo que uma das principais é o gerenciamento de perfis de acesso ao seu Admin VTEX. 
+
+Algumas das mais importantes recomendações sobre [perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) na VTEX são:
+
+* **Conceda o mínimo nível de permissão necessário:** crie os perfis de forma que o nível de acesso a informações e configurações seja somente o necessário para a realização da atividade prevista. Além dos [perfis de acesso predefinidos](https://help.vtex.com/pt/tutorial/perfis-de-acesso), você pode criar [perfis de acesso customizados](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso). Diminuir o nível de permissão de terceiros a conteúdos críticos é diminuir sua exposição ao risco de acessos indesejados, vazamento de dados ou outros cenários danosos. 
+* **Reavalie perfis de acesso:** [gerencie usuários](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) periodicamente e mantenha atualizado o nível adequado de permissão de cada usuário. É fundamental excluir o perfil de acesso de funcionários ou fornecedores que deixaram de participar do seu negócio. A revisão proativa e periódica de usuários evita violações de segurança por acesso indevido.
+* **Controle a permissão de chaves de aplicação:** além de pessoas, o acesso à sua loja VTEX pode ser feito pelas [chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) utilizadas em integrações. É importante seguir nossas recomendações de [boas práticas na utilização de chaves de aplicação](https://help.vtex.com/pt/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm).
+* **Restrinja o acesso ao Admin VTEX a domínios corporativos:** utilizar um domínio corporativo cria uma barreira adicional para que pessoas e sistemas indesejados não acessem sua loja. Limitar o acesso somente a emails corporativos ajuda a mitigar riscos de vazamento de dados (intencionais ou acidentais), aumenta a proteção contra phishing e facilita a rastreabilidade de atividades de auditoria.
+* **Habilite a autenticação de 2 fatores:** com a [autenticação de 2 fatores (2FA)](https://help.vtex.com/pt/tutorial/habilitar-login-por-autenticacao-de-2-fatores--4Ae1fcQi12g8u4SkQKCqWQ) você adiciona uma camada extra de segurança à sua operação e protege o acesso à loja, caso o sigilo da sua senha seja comprometido. Habilitar essa autenticação é ainda mais importante para usuários com acesso a informações e configurações de níveis críticos.
+
+### Conheça nossos marketplaces certificados e parceiros
+
+A arquitetura da plataforma VTEX permite que as lojas se tornem [marketplaces e sellers entre si](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402), e a página [Marketplaces e Integrações](https://help.vtex.com/pt/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V) possibilita a descoberta e comunicação entre marketplaces e sellers VTEX. Além disso, a VTEX disponibiliza integrações nativas com diversos [marketplaces certificados](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-certificados) e [parceiros](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros) (como a Amazon e o Mercado Livre).
+
+Caso você queira desenvolver uma integração com um marketplace externo, veja o artigo [External Marketplace](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide).
+
+## Atualizações e novidades
+
+Nesta seção, conheça boas práticas para acompanhar o status da plataforma e as inovações dos produtos VTEX.
+
+### Acompanhe nossos lançamentos e novidades
+
+A plataforma VTEX está em constante evolução, uma boa forma para você e sua equipe estarem a par dos lançamentos é acompanhando nossos portais de documentação, apresentados a seguir:
+
+| **Portal de documentação** | **Onde encontrar** |
+| :---: | :---: |
+| Help Center | Página: [Novidades](https://help.vtex.com/pt/announcements) |
+| Developer Portal | Página: [Release Notes](https://developers.vtex.com/updates/release-notes) |
+
+Alguns dos principais benefícios em se manter informado são:
+
+* Manter a sua operação atualizada com os últimos lançamentos, utilizando a plataforma em todo o seu potencial e mantendo a sua vantagem competitiva no mercado.
+* Conhecer o funcionamento dos novos recursos, garantindo maior agilidade na implementação.
+* Configurar as atualizações para aumentar a segurança da sua loja, pois inovamos continuamente visando a proteção do seu negócio.
+* Caso seja necessário contatar o suporte, conhecer o funcionamento dos novos recursos permite uma interação mais eficiente com o suporte, o que resulta em resoluções mais rápidas.
+
+<div class = "alert alert-info">
+Os anúncios da página <b>Novidades</b> do Help Center também são disponibilizados pelo seu Admin VTEX. Para acessar o conteúdo, basta clicar no ícone de sino no topo da página.
+</div>
+
+### Receba notificações de status da plataforma
+
+Quando ocorre algum incidente na plataforma, a VTEX busca atuar da forma mais transparente e informativa possível. 
+
+Para isso, a VTEX disponibiliza a [página de status da plataforma](https://status.vtex.com/). Além de acompanhar a estabilidade da plataforma em tempo real, o conteúdo da página permite visualizar quando há manutenções programadas. Você pode se inscrever na página para receber notificações via:
+
+* Email
+* [Feed RSS](https://rss.com/blog/how-do-rss-feeds-work/)
+* [Slack](https://slack.com/)
+
+<div class = "alert alert-info">
+Para entender os detalhes da página de status da plataforma, acesse o artigo <a href="https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ">Página de status da VTEX</a>.
+</div>
+
+### Conheça nossos conteúdos de onboarding
+
+A  VTEX oferece inúmeras funcionalidades e produtos, e é importante conhecê-los para saber quais são os recursos mais adequados ao perfil do seu negócio.
+
+Para isso, disponibilizamos uma série de conteúdos de onboarding sobre a plataforma, apresentados a seguir:
+
+| **Formato** | **Onde encontrar** | **Língua** |
+| :---: | :--- | :--- |
+| Documentação | Help Center: [Guia de onboarding](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) | Português, inglês e espanhol. |
+| Vídeos | Site: [Onboarding VTEX](https://sites.google.com/vtex.com.br/onboardingvtex/trilha) | Somente português. |
+| Demos e ebooks | Site: [VTEX.com](https://vtex.com/br-pt/resources) | Cada conteúdo é disponibilizado somente em português, inglês ou espanhol. |
+
+## Comunidade e suporte
+
+Nesta seção, conheça boas práticas para otimizar sua rede de apoio no ecossistema VTEX.
+
+### Participe da VTEX Community
+
+A [VTEX Community](https://community.vtex.com/) é um espaço acessível ao público em geral, onde nossos especialistas, clientes, parceiros de implementação e todo o ecossistema VTEX compartilham conhecimento e se apoiam mutuamente. 
+
+A abordagem colaborativa da nossa comunidade é uma importante fonte de suporte na VTEX, e algumas de suas principais vantagens são:
+
+* **Rapidez de respostas:** a VTEX Community está ativa 24 horas por dia durante todos os dias da semana, e conta com a participação de membros de diversos países. Quando você faz uma pergunta, ela pode ser respondida a qualquer momento e, além dos profissionais da VTEX, outras pessoas podem ter vivenciado situações semelhantes e saibam como apoiar.
+* **Visões diferentes:** ao interagir com os diversos membros da comunidade, você acessa perspectivas e abordagens diferentes para a resolução de problemas, e essa diversidade de experiências muitas vezes resulta em soluções inovadoras.
+* **Compartilhamento de informação:** nossa comunidade se tornou uma espécie de biblioteca virtual e nela você encontra dicas, sugestões de boas práticas e vários conteúdos práticos para operar sua loja VTEX da melhor forma.
+* **Contatos profissionais e comerciais:** a presença ativa na comunidade contribui para a evolução da sua rede de contatos profissionais.
+
+### Conheça boas práticas em solicitações do Suporte VTEX
+
+Existem alguns casos em que o apoio via ticket do Suporte VTEX se faz necessário. Por exemplo, situações que envolvem informação sigilosa ou cenários urgentes. 
+
+Nossos especialistas estão preparados para resolver a sua demanda e proporcionar a você uma boa experiência ao longo do processo, mas você pode contribuir para que a atuação do suporte seja a mais rápida e eficaz possível. 
+
+Existem [boas práticas para abrir um ticket para o Suporte VTEX](https://help.vtex.com/pt/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX), de forma a obter um atendimento mais rápido e objetivo, algumas das principais são:
+
+* Fornecer informações detalhadas sobre o motivo da abertura do chamado.
+* Descrever a situação ou problema de forma clara, precisa e objetiva (especialmente para questões urgentes).
+* Manter uma comunicação clara e proativa ao longo do seu atendimento.
+* Quando possível, anexar capturas de tela e incluir registros (logs) relevantes.
+* Quando possível, explicar como reproduzir os cenários de erro e problemas.
+
+Estas recomendações são algumas das mais importantes. Para mais informações, veja o artigo [Boas práticas para a abertura de um Ticket para o Suporte VTEX](https://help.vtex.com/pt/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX).
+
+<div class = "alert alert-info">
+Para obter uma visão geral do nosso suporte via ticket, veja a trilha <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">Suporte na VTEX</a>, que compõe o <b>Guia de onboarding</b>.
+</div>
+
diff --git a/docs/tutorials/pt/best-practices-for-using-images-in-the-catalog.md b/docs/tutorials/pt/best-practices-for-using-images-in-the-catalog.md
index e84d0bda2..9c5814c8f 100644
--- a/docs/tutorials/pt/best-practices-for-using-images-in-the-catalog.md
+++ b/docs/tutorials/pt/best-practices-for-using-images-in-the-catalog.md
@@ -3,8 +3,8 @@ title: 'Boas práticas para o uso de imagens no Catálogo'
 id: 738K2yfq5U86kUI2k4AQIk
 status: PUBLISHED
 createdAt: 2018-01-30T14:45:53.934Z
-updatedAt: 2022-07-07T15:32:57.069Z
-publishedAt: 2022-07-07T15:32:57.069Z
+updatedAt: 2024-01-23T15:54:22.159Z
+publishedAt: 2024-01-23T15:54:22.159Z
 firstPublishedAt: 2018-01-31T18:36:10.087Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -29,7 +29,7 @@ Este artigo tem como objetivo enunciar algumas boas práticas em relação ao us
 - Não recomendamos esticar a imagem para não afetar sua qualidade.
 
 ## Saiba mais
-- [Cadastrar Producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL)
-- [Cadastrar SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ)
+- [Cadastrar Producto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1ROhz3Y7mfSMmCO1I1GxEL)
+- [Cadastrar SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ)
 - [Importar imagens por planilha](https://help.vtex.com/pt/tutorial/importando-imagens-por-planilha--tutorials_262)
 
diff --git a/docs/tutorials/pt/best-practices-on-spf.md b/docs/tutorials/pt/best-practices-on-spf.md
index cc7b24a7d..6fe87965f 100644
--- a/docs/tutorials/pt/best-practices-on-spf.md
+++ b/docs/tutorials/pt/best-practices-on-spf.md
@@ -3,8 +3,8 @@ title: 'Boas práticas de SPF (Sender Policy Framework)'
 id: 42t0lkl2VyC6Yewc4wA6wI
 status: PUBLISHED
 createdAt: 2017-08-09T16:58:00.716Z
-updatedAt: 2023-03-10T18:49:18.935Z
-publishedAt: 2023-03-10T18:49:18.935Z
+updatedAt: 2024-02-22T18:11:49.023Z
+publishedAt: 2024-02-22T18:11:49.023Z
 firstPublishedAt: 2017-08-10T00:04:19.239Z
 contentType: tutorial
 productTeam: Reliability
@@ -25,13 +25,13 @@ Para mais detalhes da sintaxe, recomendamos a documentação [Sender Policy Fram
 
 No gerenciador de DNS, o SPF será uma entrada TXT na raíz do domínio (ex: site.com), com o seguinte formato:
 
-`site.com. IN TXT “v=spf1 a mx ip4:192.0.2.32/27 include:provedor.com -all”`
+`site.com. IN TXT “v=spf1 a mx ip4:192.0.2.32/27 include:provedor.com ~all”`
 
 Podemos dividir a política acima nas seguintes seções:
 
 - `v=spf1`: prefixo obrigatório.
 - `a mx ip4:192.0.2.32/27 include:provedor.com`: remetentes permitidos.
-- `-all`: condição de inclusão ou exclusão de remetentes fora dos declarados anteriormente.
+- `~all`: condição de inclusão ou exclusão de remetentes fora dos declarados anteriormente.
 
 Dentro do elemento de remetentes permitidos, as regras acima significam que um servidor pode enviar mensagens em nome do domínio em questão (site.com) quando:
 
@@ -44,12 +44,13 @@ A condição de inclusão ou exclusão pode apresentar os seguintes valores:
 
 - `+all`: será permitido qualquer remetente fora dos declarados.
 - `-all`: será recusado qualquer remetente fora dos declarados.
-- `~all`: será necessária outra etapa de verificação para recusar os remetentes não autorizados.
+- `~all`: será necessária outra etapa de verificação para recusar os remetentes não autorizados. (Recomendado)
 - `?all`: será desconsiderada a verificação dos remetentes não autorizados.
 
-É recomendado a utilização de -all, que apresenta melhor taxa de entregabilidade. Contudo, é preciso garantir que todos os domínios que enviam mensagens em seu nome estejam devidamente configurados, caso contrário as mensagens não serão entregues.
+Recomendamos a utilização de `~all`, que apresenta melhor taxa de entregabilidade. Se houver um remetente não autorizado, essa opção não trava o envio do email, mas informa que a validação do SPF falhou.
 
 ## SPF no contexto VTEX
+
 A VTEX faz uso do SPF `include:amazonses.com`. É o serviço de envio de emails transacionais da Amazon, utilizado no remetente padrão (tipo VTEX) do Message Center.
 
 Veja nosso artigo de [configuração do SPF](https://developers.vtex.com/vtex-rest-api/docs/setting-up-the-spf) para mais detalhes.
diff --git a/docs/tutorials/pt/best-practices-to-avoid-scams-using-the-vtex-brand.md b/docs/tutorials/pt/best-practices-to-avoid-scams-using-the-vtex-brand.md
new file mode 100644
index 000000000..edfffa291
--- /dev/null
+++ b/docs/tutorials/pt/best-practices-to-avoid-scams-using-the-vtex-brand.md
@@ -0,0 +1,54 @@
+---
+title: 'Boas práticas para evitar golpes que utilizam a marca da VTEX'
+id: 6uPwUr2Fnj2m3TM4hAj2Ec
+status: PUBLISHED
+createdAt: 2024-03-19T14:09:14.448Z
+updatedAt: 2024-03-19T14:21:08.209Z
+publishedAt: 2024-03-19T14:21:08.209Z
+firstPublishedAt: 2024-03-19T14:21:08.209Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: boas-praticas-para-evitar-golpes-que-utilizam-a-marca-da-vtex
+locale: pt
+legacySlug: boas-praticas-para-evitar-golpes-que-utilizam-a-marca-da-vtex
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+Como lojista, é crucial estar atento aos golpes que podem utilizar a marca da VTEX de forma fraudulenta. Neste artigo, compartilharemos algumas recomendações para ajudar a identificar e evitar esses golpes.
+
+Proteger sua loja online contra golpes que utilizam a marca da VTEX requer vigilância constante e cautela. Ao seguir as orientações deste guia e permanecer atento(a) às ameaças potenciais, você estará contribuindo para a segurança e a integridade do seu negócio online.
+
+## Verificar a autenticidade da comunicação
+
+A VTEX geralmente se comunica com seus clientes por meio de canais oficiais:
+
+* Mensagens dentro do Admin VTEX
+* E-mails corporativos
+* Comunicados no [Help Center](https://help.vtex.com/) ou no [Developer Portal](https://developers.vtex.com/)
+* Publicações no [site](https://vtex.com/br-pt/) ou nas redes sociais oficiais da VTEX
+
+Desconfie de qualquer comunicação que solicite informações confidenciais ou ações suspeitas, especialmente se vier de fontes não verificadas.
+
+É comum que golpistas tentem te convencer a agir de maneira imediata, informando um prazo curto ou um possível risco envolvido. Por isso, mantenha a calma e sempre pense antes de clicar ou fornecer alguma informação. 
+
+## Proteger credenciais de login
+
+Mantenha em segurança as [chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet), os [tokens de usuário](https://developers.vtex.com/docs/guides/api-authentication-using-user-tokens) e as credenciais de [login](https://help.vtex.com/pt/tutorial/autenticacao--21CkKHLKP1o41lUpGhuRUs#login) na VTEX, como email, senha e códigos de acesso. Nunca compartilhe com terceiros dados pessoais e confidenciais, informações sobre a loja, códigos, entre outras informações sensíveis.
+
+Golpistas podem tentar obter acesso à sua conta para realizar atividades fraudulentas em nome da sua empresa. Antes de agir ou de fornecer qualquer informação, confirme se é realmente a VTEX que está se comunicando com você.
+
+## Identificar ofertas enganosas
+
+Se você receber ofertas no nome da VTEX que afirmam ser parte de programas de incentivo, não siga as instruções do remetente. A VTEX não oferece programa de incentivo e não solicita pagamentos de pessoas físicas ou jurídicas fora do contrato de prestação de serviços da plataforma.
+
+Sempre verifique a URL de destino antes de clicar em um link ou acessar uma página e confirme se é um dos [canais oficiais](#verificar-a-autenticidade-da-comunicacao) de comunicação da VTEX. Em caso de dúvidas, acione o nosso [Suporte](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9). 
+
+## Consultar os recursos de segurança da VTEX
+
+A VTEX oferece recursos de segurança e orientações para ajudar seus clientes a proteger suas lojas online contra fraudes e golpes. Familiarize-se com esses recursos e utilize-os para fortalecer a segurança da sua loja. Saiba mais sobre as nossas práticas de segurança em [Segurança - VTEX](https://vtex.com/br-pt/security/).
+
+## Relatar atividades suspeitas
+
+Se você suspeitar de atividades fraudulentas que utilizam a marca da VTEX, reporte-as imediatamente ao [Suporte](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9). A partir disso, a equipe de Segurança da VTEX irá investigar a situação e realizar as ações necessárias para prevenir e combater possíveis fraudes.
+
diff --git a/docs/tutorials/pt/beta-price-configuration.md b/docs/tutorials/pt/beta-price-configuration.md
index fbf546876..3b94d1c91 100644
--- a/docs/tutorials/pt/beta-price-configuration.md
+++ b/docs/tutorials/pt/beta-price-configuration.md
@@ -72,11 +72,11 @@ Para criar uma nova regra, siga os passos a seguir:
 
   b. **Ativar em condições específicas:** a tabela de preço será ativada segundo as condições configuradas na regra. Veja as possibilidades de configuração com as imagens a seguir:
 
-  ![config-preco-PT](https://images.ctfassets.net/alneenqid6w5/4U3RNX4VaQm3EPUO3JX0Pu/d8ef577cd574c3bf765b38c63f08bd7b/config-preco-PT.png)
+  ![config-preco-PT](//images.ctfassets.net/alneenqid6w5/4U3RNX4VaQm3EPUO3JX0Pu/d8ef577cd574c3bf765b38c63f08bd7b/config-preco-PT.png)
 
-  ![config-preco2-PT](https://images.ctfassets.net/alneenqid6w5/3RYREfiFKxAPqodf8uCAy6/3500e92785edeef7184e5f4f273f1f38/config-preco2-PT.png)
+  ![config-preco2-PT](//images.ctfassets.net/alneenqid6w5/3RYREfiFKxAPqodf8uCAy6/3500e92785edeef7184e5f4f273f1f38/config-preco2-PT.png)
 
-  ![config-preco3-PT](https://images.ctfassets.net/alneenqid6w5/56mqdIxfxQMDOzzod8Juc5/e14da5f91d1b77a354ee9319ab5d6470/config-preco3-PT.png)
+  ![config-preco3-PT](//images.ctfassets.net/alneenqid6w5/56mqdIxfxQMDOzzod8Juc5/e14da5f91d1b77a354ee9319ab5d6470/config-preco3-PT.png)
 
 7. Clique em **Confirmar**. 
 
diff --git a/docs/tutorials/pt/billing-module-overview.md b/docs/tutorials/pt/billing-module-overview.md
index 72bf0c224..af16c2237 100644
--- a/docs/tutorials/pt/billing-module-overview.md
+++ b/docs/tutorials/pt/billing-module-overview.md
@@ -23,7 +23,7 @@ Para acessar essa página, clique no seu **avatar**, que pode ser identificado p
 Somente usuários com o perfil de acesso <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> ou com recursos de <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> vinculados ao seu perfil de acesso terão acesso a essa seção do Admin VTEX.
             </div>
 
-![Admin v4 Faturas menu PT](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/3102e348f966683a32c36512bdf2ba16/Admin_v4_Faturas_menu_PT.jpg)
+![Admin v4 Faturas menu PT](//images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/3102e348f966683a32c36512bdf2ba16/Admin_v4_Faturas_menu_PT.jpg)
 
 Veja abaixo mais detalhes sobre as diferentes seções e páginas deste recurso.
 
diff --git a/docs/tutorials/pt/bitrix24.md b/docs/tutorials/pt/bitrix24.md
index 789b0e35c..9993acd58 100644
--- a/docs/tutorials/pt/bitrix24.md
+++ b/docs/tutorials/pt/bitrix24.md
@@ -21,38 +21,38 @@ Para realizar a integração acesse no seu painel da VTEX Assisted Sales (Suite
 
 Na dashboard em **Integrações”**, clique em **Ver todas as integrações**. Ou clique em _**Configurações > Integrações**_.
 
-![Bitrix24_1](https://images.ctfassets.net/alneenqid6w5/1FNycssXpEsblACNCy0eJx/5c5a7b399d4c6051e312e1b3b897a257/Bitrix24_1.png)
+![Bitrix24_1](//images.ctfassets.net/alneenqid6w5/1FNycssXpEsblACNCy0eJx/5c5a7b399d4c6051e312e1b3b897a257/Bitrix24_1.png)
 
 Selecione o Bitrix24 sales e clique em **Integrar**.
 
 Selecione o [formulário de captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseja conectar.
 
-![Bitrix24_2](https://images.ctfassets.net/alneenqid6w5/12eiYCSAdxKWQnXnG5TAGT/d2f2331416d7815b2ebb4cf6441637b6/Bitrix24_2.png)
+![Bitrix24_2](//images.ctfassets.net/alneenqid6w5/12eiYCSAdxKWQnXnG5TAGT/d2f2331416d7815b2ebb4cf6441637b6/Bitrix24_2.png)
 
 Dentro do Bitrix24, no menu a esquerda, clique em _**Aplicativos > Market**_.
 
-![Bitrix24_3](https://images.ctfassets.net/alneenqid6w5/2fy2TlaXC9OJ4x9m8OT7Fw/a78dc1307d0865f1f05bc9c134d650d3/Bitrix24_3.png)
+![Bitrix24_3](//images.ctfassets.net/alneenqid6w5/2fy2TlaXC9OJ4x9m8OT7Fw/a78dc1307d0865f1f05bc9c134d650d3/Bitrix24_3.png)
 
 No menu superior, clique em **Recursos para desenvolvedores**.
 
-![Bitrix24_4](https://images.ctfassets.net/alneenqid6w5/5ICON3qpUxJ6gvoJWrmWC6/82d44a2fb708c421aa4b05a5095ae5f6/Bitrix24_4.png)
+![Bitrix24_4](//images.ctfassets.net/alneenqid6w5/5ICON3qpUxJ6gvoJWrmWC6/82d44a2fb708c421aa4b05a5095ae5f6/Bitrix24_4.png)
 
 Na página a seguir, clique em **Outro**.
 
-![Bitrix24_5](https://images.ctfassets.net/alneenqid6w5/1gUel7t9l6x8DleZL10MFI/9afa3e49bf93432d0417b87621ff23d8/Bitrix24_5.png)
+![Bitrix24_5](//images.ctfassets.net/alneenqid6w5/1gUel7t9l6x8DleZL10MFI/9afa3e49bf93432d0417b87621ff23d8/Bitrix24_5.png)
 
 Na página a seguir, clique em **Webhook de entrada**.
 
-![Bitrix24_6](https://images.ctfassets.net/alneenqid6w5/6hUYhcVQE2qC2NclWfRXR7/0a2e1bfeca200c8efd6d5b10a7f0e5a5/Bitrix24_6.png)
+![Bitrix24_6](//images.ctfassets.net/alneenqid6w5/6hUYhcVQE2qC2NclWfRXR7/0a2e1bfeca200c8efd6d5b10a7f0e5a5/Bitrix24_6.png)
 
 Na página a seguir, troque o **Criador de pedido** para `crm.lead.add`.
 
-![Bitrix24_7](https://images.ctfassets.net/alneenqid6w5/4HUNOCnKRZQPS0HfB5cTR9/0aeae79037ae3093e2f1cef6623cd124/Bitrix24_7.png)
+![Bitrix24_7](//images.ctfassets.net/alneenqid6w5/4HUNOCnKRZQPS0HfB5cTR9/0aeae79037ae3093e2f1cef6623cd124/Bitrix24_7.png)
 
 Copie a URL gerada no campo URL e clique em salvar. 
 
 A URL copiada deve ser colada no campo **URL do Webhook** painel da VTEX Assisted Sales (SuiteShare) para cada um dos links que deseja integrar:
 
-![Bitrix24_8](https://images.ctfassets.net/alneenqid6w5/5ApW3fkTAHVrbhrbmbPqf8/8e04b9411b8cba3be9a26b51a26bfeda/Bitrix24_8.png)
+![Bitrix24_8](//images.ctfassets.net/alneenqid6w5/5ApW3fkTAHVrbhrbmbPqf8/8e04b9411b8cba3be9a26b51a26bfeda/Bitrix24_8.png)
 
 Pronto, integração finalizada!
diff --git a/docs/tutorials/pt/black-week.md b/docs/tutorials/pt/black-week.md
index f8b6626f0..1c09f26e1 100644
--- a/docs/tutorials/pt/black-week.md
+++ b/docs/tutorials/pt/black-week.md
@@ -29,7 +29,7 @@ Caso você utilize o novo Admin VTEX, para acessá-la, vá para **Dashboards > B
 
 Para ter acesso à pagina, é necessário conter o [recurso](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) *Insights Metrics* com a chave `view_metrics` em seu [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Sem esse recurso configurado em seu perfil de acesso, você receberá um erro *403 - Não autorizado* ao tentar visualizar a página. 
 
-![Black Week](https://images.ctfassets.net/alneenqid6w5/3IM9M6IwfycwTmUzJDEzem/2ce38a00422d16e12016eb0ba58edd9b/Screen_Shot_2022-11-18_at_16.11.09.png)
+![Black Week](//images.ctfassets.net/alneenqid6w5/3IM9M6IwfycwTmUzJDEzem/2ce38a00422d16e12016eb0ba58edd9b/Screen_Shot_2022-11-18_at_16.11.09.png)
 
 Este artigo inclui as seguintes seções:
 
@@ -93,7 +93,7 @@ A Black Week inclui os seguintes gráficos para a análise dos resultados do seu
 
 ### Total de pedidos
 
-![Total de pedidos](https://images.ctfassets.net/alneenqid6w5/7mYLy1HXJVjiBm923PRQmm/d6eaef3b046627bca6fa55147221b1d2/Screen_Shot_2022-11-18_at_16.00.21.png)
+![Total de pedidos](//images.ctfassets.net/alneenqid6w5/7mYLy1HXJVjiBm923PRQmm/d6eaef3b046627bca6fa55147221b1d2/Screen_Shot_2022-11-18_at_16.00.21.png)
 
 O gráfico _Total de Pedidos_ apresenta a quantidade de pedidos captados pela loja, agregado por dia e comparado com os anos anteriores selecionados. Saiba mais em [Dados](#dados).
 
@@ -123,7 +123,7 @@ Para ler os gráficos, note que:
 
 #### Total do dia 
 
-![Total do dia](https://images.ctfassets.net/alneenqid6w5/3PMiZmAt84euZIrmu7gy35/77de595d36fab0672ba75d626acae658/Screen_Shot_2022-11-18_at_16.00.40.png)
+![Total do dia](//images.ctfassets.net/alneenqid6w5/3PMiZmAt84euZIrmu7gy35/77de595d36fab0672ba75d626acae658/Screen_Shot_2022-11-18_at_16.00.40.png)
 
 A visualização _Total do Dia_ indica na tela:
 
@@ -134,7 +134,7 @@ Essa visualização é útil para acompanhar o somatório de vendas no dia, send
 
 #### Últimas 2 horas
 
-![Últimas 2 horas](https://images.ctfassets.net/alneenqid6w5/7tBr0SR2wP9lD9SvJF6jpj/5be2166e0dd369b2a3b980ccfb90cf47/Screen_Shot_2022-11-18_at_16.00.54.png)
+![Últimas 2 horas](//images.ctfassets.net/alneenqid6w5/7tBr0SR2wP9lD9SvJF6jpj/5be2166e0dd369b2a3b980ccfb90cf47/Screen_Shot_2022-11-18_at_16.00.54.png)
 
 A visualização _Últimas 2 horas_ indica na tela:
 
diff --git a/docs/tutorials/pt/brands.md b/docs/tutorials/pt/brands.md
index bafb98f20..88366f218 100644
--- a/docs/tutorials/pt/brands.md
+++ b/docs/tutorials/pt/brands.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 A página **Marcas** permite visualizar, gerenciar e cadastrar marcas no Seller Portal. Você pode acessar a página no Admin VTEX em **Catálogo** > **Marcas**.
 
-![brands-pt](https://images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/4556bc8cc6f367453b4bf4ccbe2bf145/brands-pt.PNG)
+![brands-pt](//images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/4556bc8cc6f367453b4bf4ccbe2bf145/brands-pt.PNG)
 
 ## Criar marca 
 Para cadastrar uma nova marca, clique no botão `Criar marca`. Veja abaixo como preencher os campos da tela __Nova marca__.
diff --git a/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md b/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md
index c79582a4f..b7e1cef38 100644
--- a/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md
+++ b/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md
@@ -25,13 +25,13 @@ Navegue até o projeto e abra o arquivo `pages.json`.
 
 Adicionamos o `“admin/“` ao nome da página, assim como à rota. É importante também adicionar `“admin/“` ao início do nome de todas as extensoes que serão usadas. Seu `pages.json` deve ficar assim:
 
-![2 pages](https://images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
+![2 pages](//images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
 
 ## Atualizar as dependências para usar o vtex.admin
 
 Agora precisamos atualizar o arquivo manifest.json para listar o `vtex.admin` como dependência. Lembre-se que no VTEX IO sempre especificamos a versão que será ultilizada. O manifest.json deve ficar assim:
 
-![3 manifest](https://images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
+![3 manifest](//images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
 
 ## Os toques finais
 
@@ -43,5 +43,5 @@ Usaremos o `componentDidMount()` para verificar que a string renderizou corretam
 
 Basta navegar até `index.js` e adicionar o `componentDidMount()` acima do nosso render. Vai ficar assim:
 
-![4 final touches](https://images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
-![5 completo](https://images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
+![4 final touches](//images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
+![5 completo](//images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
diff --git a/docs/tutorials/pt/buy-one-get-one.md b/docs/tutorials/pt/buy-one-get-one.md
index bb5c91197..fb3ba1213 100644
--- a/docs/tutorials/pt/buy-one-get-one.md
+++ b/docs/tutorials/pt/buy-one-get-one.md
@@ -3,8 +3,8 @@ title: 'Como funciona a promoção Compre e ganhe'
 id: tutorials_322
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:41.148Z
-updatedAt: 2021-12-13T17:23:17.182Z
-publishedAt: 2021-12-13T17:23:17.182Z
+updatedAt: 2024-02-19T11:48:37.254Z
+publishedAt: 2024-02-19T11:48:37.254Z
 firstPublishedAt: 2017-04-27T23:03:14.992Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,47 +15,112 @@ legacySlug: compre-e-ganhe
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-Esse tipo de promoção é utilizado para oferecer frete grátis ou um brinde caso determinado produto seja comprado. Por exemplo, “compre uma televisão e não pague o frete”, ou ainda “compre um video game e ganhe um jogo”.
+A promoção do tipo Compre e ganhe é utilizada para oferecer frete grátis ou um brinde caso determinado produto seja comprado. Por exemplo, “compre uma televisão e não pague o frete”, ou ainda “compre um video game e ganhe um jogo”.
 
-## Quais são os dados gerais desta promoção?
+Neste artigo, detalharemos os passos necessários para configurar uma promoção Compre e Ganhe:
 
-- __Nome__
-- __Nome da promoção__
-- __Status__
-- __Ativa ou Inativa a promoção__
-- __Descrição interna da promoção__: o objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a promoção é devido à alguma campanha, queima de estoque etc.
-- __Validade__: data e hora de início e de fim da promoção. (Pode ser usada uma data e/ou horário futuros, para que a promoção comece a ser aplicada no site. Caso seja configurada dessa forma, a promoção terá o status de agendada até que a data e horário sejam atingidos. Enquanto a promoção estiver válida, esta terá o status de ativa e ao término da data e hora definidos, o status será alterado para inativo automaticamente.)
-- __Especificar dias da semana para ativação__: essa opção é do tipo caixa de seleção, que quando marcado disponibiliza sete outras caixas de seleção, para que sejam selecionados os dias da semana em que a promoção será aplicada. Se deseja que a promoção seja aplicada em qualquer dia da semana, não selecione essa opção.
-- __Qual tipo é o valor do desconto?__:
+1. [Quais os dados gerais desta promocao?](#1-quais-os-dados-gerais-desta-promoção)
+    - [Restringir esta promoção a produtos dos sellers](#restringir-esta-promoção-a-produtos-dos-sellers)
+    - [Política Comercial](#política-comercial)
+2. [Compre e ganhe](#2-compre-e-ganhe)
+3. [Quais as condições para a promoção ser válida?](#3-quais-as-condicoes-para-a-promocao-ser-valida)
+4. [Restrições e limitações de uso](#4-restricoes-e-limitaçoes-de-uso)
 
-  1. __Preço Máximo por Item__: define o preço máximo para cada item da compra.
-  2. __Frete grátis__: desconto total sobre o valor do frete.
-  3. __Brinde__: desconto total sobre o valor do produto definido como brinde. Ao selecionar essa opção abrem os campos para inserir um SKU, a caixa para ativar o multiplicador de brindes e a quantidade de produtos diferentes que serão dados de brinde. O SKU pode ser inserido pelo nome ou Id, podendo ser incluído mais de um. Para aprender a configurar esse tipo de desconto, leia o artigo [Configurar promoção Compre e ganhe para um SKU específico](/pt/tutorial/configurar-promocao-compre-e-ganhe-para-um-sku-especifico).
-- __Destaque nos produtos__: insere uma tag com o nome da promoção. Utilizado na vitrine e na página de produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template. <vtex.cmc:discountHightLight>;
-- __Seller__: selecione o seller que oferecerá o desconto. Se possui multiloja, aparecerão aqui todos os sellers que tiver cadastrado em sua conta. Essa opção possibilita criar condicionar um desconto diferente para cada seller.
-- __Política Comercial__: selecione as Políticas Comerciais que oferecerão o desconto. Serão listadas aqui todas as políticas que tiver cadastrada em: `E-Commerce > Marketplace > Políticas Comercias`. Essa opção disponibiliza criar uma promoção específica para uma, ou mais de uma, política comercial.
+# Criar a promoção
 
-## Compre e Ganhe
+No Admin VTEX, acesse **Promoções > Promoções** ou digite **Promoções** na barra de busca no topo da página.
 
-- __Coleções__: digite o nome da coleção de produtos que deseja oferecer esse tipo de desconto. Pode ser inserida mais de uma. A promoção será aplicada somente aos produtos que estejam nas coleções cadastradas nesse campo.
-- __SKUs__: pode inserir o nome ou Id dos SKUs que deseja que o desconto seja aplicado. Pode fazer a importação de uma lista de SKUs, que deve estar salvo em um arquivo de texto (.txt) com cada Id em uma linha diferente. 
+1. Clique no botão `Criar promoção`.
+2. Selecione a opção **Compre e ganhe**.
+3. Preencha os campos da promoção.
+4. Clique em `Salvar`.
 
-__OBS__: se não forem limitados produtos por coleção ou SKU, a plataforma não permitirá a criação da promoção.
+# 1. Quais são os dados gerais desta promoção?
 
-__Atenção__: só é possível cadastrar, no máximo, 100 SKUs na promoção Compre e Ganhe. 
+Nesta seção, fornecemos informações detalhadas sobre os dados gerais desta promoção.
+- **Nome:** nome da promoção. Campo obrigatório.
+- **Status:** ativa ou inativa a promoção.
+- **Descrição**: o objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a promoção é devido à alguma campanha, queima de estoque, etc.
+- **Data de expiração:** data e hora de início e de fim da promoção. Pode ser usada uma data e/ou horário futuros, para que a promoção comece a ser aplicada no site. Caso seja configurada desta forma, o status da promoção será exibido das seguintes formas:
+    - Agendada: antes da data e horário de início selecionados.
+    - Ativa: durante o período programado para a promoção.
+    - Inativa: após a data e horário de término selecionados.
+- **Usar configurações de recorrência:** ao selecionar esta opção, é permitido realizar configurações de recorrência, por exemplo, dia da semana e horário.
+- **Tipo e valor do desconto:** permite selecionar uma das opções abaixo:
+    1. **Preço Máximo por Item:** define o preço máximo para cada item da compra.
+    2. **Frete grátis:** desconto total sobre o valor do frete.
+    3. **Brinde:** desconto total sobre o valor do produto definido como brinde. Ao selecionar essa opção, é possível indicar o SKU (por nome ou ID) que será considerado brinde, escolher se o [multiplicador de brindes](https://help.vtex.com/pt/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK) deve ser ativado e a quantidade máxima de produtos que poderão ser utilizados como brindes na promoção. Para mais informações sobre este tipo de desconto, acesse  [Configurar promoção Compre e ganhe para um SKU específico](https://help.vtex.com/pt/tutorial/configurar-promocao-compre-e-ganhe-para-um-sku-especifico).
+- **Informações adicionais (opcional):** permite incluir informações adicionais a promoção composto de um nome e valor.
+- **Destaque nos produtos:** insere uma tag com o nome da promoção. Utilizada na vitrine e na página do produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template. <vtex.cmc:discountHightLight>.
 
-- __Quantidade de produtos para o Benefício__: permite definir a quantidade de produtos que devem ser inseridos no carrinho, para que o desconto seja concedido. Esse campo é de preenchimento obrigatório.
+![Dados gerais da promoção](//images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/131b38791a109e9629dcbfd9b203e80f/Dados_gerais_da_promo__o-PT.png)
 
-## Quais condições para a promoção ser válida?
+## Restringir esta promoção a produtos dos sellers
 
-- __Restrição por BIN__: define para quais cartões de crédito a promoção estará ativa.
-- __Cluster de Clientes__: pode usar um campo existente na Entidade de Dados __CL__ para criar uma restrição. Exemplo: `idade=25`
-- __Tipo de frete__: o desconto será concedido caso o tipo de frete for o mesmo que o cadastrado.
-- __Utm\_source__: o desconto será concedido caso a navegação seja realizada com a utm\_source com o valor cadastrado.
-- __Utm\_campaign__: o desconto será concedido caso a navegação seja realizada com a utm\_campaign com o valor cadastrado.
-- Restrições e limitações de uso
+Nesta seção, é possível definir para quais sellers a promoção será aplicada. Você pode determinar quais sellers serão incluídos ou excluídos do desconto.
 
-## Restrições e Limitações de uso
+- Iguais a: selecione os nomes dos sellers desejados para incluí-los.
+- Diferentes de: selecione os nomes dos sellers desejados para excluí-los.
 
-- __Somente para itens iguais__: o desconto somente será aplicado por SKU, desde que cada um tenha a quantidade mínima cadastrada. Se não marcar essa opção, o desconto será aplicado aos produtos da coleção ou lista de SKU, sem que cada um deles tenha no carrinho necessariamente a quantidade cadastrada, sendo considerado o somatório das unidades desses produtos.
-- __Permitir acumular promoções__: permite que mais de uma promoção com o mesmo tipo de desconto seja concedida ao mesmo tempo.
+Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
+
+<div class = "alert alert-warning">
+  <p>Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
+</div>
+
+![Restringir esta promoção a produtos dos sellers](//images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/cf6fdde6e939077f04001cb3e76f02b5/Restringir_esta_promo__o_a_produtos_dos_sellers.png)
+
+## Política comercial
+
+Esta seção estabelece as políticas comerciais válidas para a promoção. Você pode incluir ou excluir políticas comerciais do desconto.
+
+- **Iguais a:** selecione as políticas comerciais desejadas incluí-las.
+- **Diferentes de:** selecione as políticas comerciais desejadas excluí-las.
+- **Fornecido por mim (Minha loja):** seleção de políticas comerciais com produtos da sua loja. Pode ser selecionada mais de uma política comercial.
+- **Entregue por mim (Lojas de terceiros):** seleção de políticas comerciais em que seus produtos estão de lojas de terceiros. Pode ser selecionada mais de uma política comercial.
+
+Para que a promoção seja válida para todas as políticas comerciais, deixe a seleção vazia.
+
+![Política comercial-PT](//images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/8810800a350cb0b9688d296e3f985fef/Politica_comerical-PT.png)
+
+# 2. Compre e Ganhe
+
+Esta seção define as coleções, SKUs e quantidade mínima que devem ser preenchidas.
+
+- **Coleções**: digite o nome de uma ou mais coleções de produtos que deseja oferecer esse tipo de desconto. A promoção será aplicada somente aos produtos que estejam nas coleções cadastradas nesse campo.
+- **SKUs**: permite inserir o nome ou ID dos SKUs nos quais deseja que o desconto seja aplicado. É possível realizar a  importação de uma lista de SKUs, que deve estar salvo em um arquivo de texto (**.txt**) com cada ID descrito em uma linha diferente.
+- **Quantidade mínima**: permite definir a quantidade mínima de produtos que devem ser inseridos no carrinho, para que o desconto seja concedido. Esse campo é de preenchimento obrigatório.
+
+<div class = "alert alert-warning">
+<p>A promoção não será criada caso os campos de Coleções ou SKUs não estejam preenchidos.</p>
+</div>
+
+<div class = "alert alert-warning">
+<p>Uma promoção Compre e Ganhe pode ser criada com o máximo de 100 SKUs diferentes ao mesmo tempo.</p>
+</div>
+
+![Compre e Ganhe](//images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/e818e8a1252f1b46032be2d043fa62cb/Compre_e_Ganhe.png)
+
+# 3. Quais condições para a promoção ser válida?
+
+Nesta seção, detalharemos as condições em que você deve aplicar para que uma promoção seja considerada válida.
+
+- **Usar BIN de restrição:** permite ativar ou desativar a restrição do BIN, limitando quais cartões de créditos poderão ser utilizados na promoção criada. É possível realizar a importação de uma lista de BINs, que deve estar salvo em um arquivo de texto (.txt) com cada BIN descrito em uma linha diferente.
+- **Cluster de Clientes:** permite ativar ou desativar a utilização do cluster de clientes. Quando ativado, é possível escolher um cluster de cliente criado por meio do [Master Data](https://help.vtex.com/pt/tutorial/como-criar-um-cluster-de-clientes).
+- **Tipo de frete:** permite escolher se a promoção será aplicada em um ou mais tipos de fretes selecionados**.**  Quando ativado, escolha um tipo de frete, e quando desativado, você terá a opção de escolher aplicar o desconto no frete mais barato.
+- **Meio de pagamento:** permite escolher se a promoção será aplicada em um ou mais tipos de meios de pagamento selecionados.
+- **Utm_source:** o desconto será concedido caso a navegação seja realizada com a utm_source com o valor cadastrado.
+- **Utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
+
+![Quais as condições para a promoção ser válida?](//images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/dfad1e2b79fbcc2381cb4474d2674ad6/Quais_as_condi__es_para_a_promo__o_ser_v_lida.png)
+
+# 4. Restrições e Limitações de uso
+
+Nesta seção você encontrará informações importantes sobre quais condições e restrições se aplicam à promoção.
+
+- **Quantas vezes essa promoção pode ser aplicada na sua loja:** permite restringir a aplicação da promoção na loja por um determinado número de vezes ou utilizá-la de forma ilimitada.
+- **Quantas vezes essa promoção pode ser aplicada na sua loja por clientes:** permite restringir a aplicação da promoção na loja a cada cliente por um determinado número de vezes ou utilizá-la de forma ilimitada.
+- **Somente para itens iguais:** Se esta opção estiver habilitada, a promoção é aplicada somente se a quantidade mínima de itens (cadastrados anteriormente) for atingida utilizando o mesmo SKU no carrinho. Caso a opção esteja desabilitada, a promoção será aplicada mesmo quando a quantidade mínima de itens for adicionada no carrinho, independentemente dos SKUs serem diferentes ou iguais.
+- **Permitir acumular promoções:** permite que essa promoção possa ser aplicada no carrinho em conjunto com outras promoções que ofereçam o mesmo tipo de desconto.
+
+![Restrições e limitações de uso](//images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/5d83ca212086a91d2f672e520e69e7e8/Restri__es_e_limita__es_de_uso.png)
diff --git a/docs/tutorials/pt/call-to-action-suiteshare.md b/docs/tutorials/pt/call-to-action-suiteshare.md
index 98ee5bff9..5e74d613f 100644
--- a/docs/tutorials/pt/call-to-action-suiteshare.md
+++ b/docs/tutorials/pt/call-to-action-suiteshare.md
@@ -19,29 +19,29 @@ Não perca clientes que acessam o seu site, ou sua página de vendas e tenha ale
 
 Para configurar, acesse seu painel do VTEX Assisted Sales (SuiteShare) e clique em Atrair > Call to Action.
 
-![Call to Action 1](https://images.ctfassets.net/alneenqid6w5/797KHplQqNwIEOwQLzPAO8/425cc4da8f450beb2543b27b65cfd817/Screenshot_2022-08-29_at_17-35-16_Call_to_Action.png)
+![Call to Action 1](//images.ctfassets.net/alneenqid6w5/797KHplQqNwIEOwQLzPAO8/425cc4da8f450beb2543b27b65cfd817/Screenshot_2022-08-29_at_17-35-16_Call_to_Action.png)
 
 Clique em _**“Novo”**_.
 
-![Call to Action 2](https://images.ctfassets.net/alneenqid6w5/2Ea8itxFI6MPKuI8jBcWLz/042d319264111791139e7c0f374643ca/Screenshot_2022-08-29_at_17-35-22_Call_to_Action.png)
+![Call to Action 2](//images.ctfassets.net/alneenqid6w5/2Ea8itxFI6MPKuI8jBcWLz/042d319264111791139e7c0f374643ca/Screenshot_2022-08-29_at_17-35-22_Call_to_Action.png)
 
 Selecione o modelo.
 
-![Call to Action 3](https://images.ctfassets.net/alneenqid6w5/48mDM3kOJj3WD78mbAG6Nh/8a9f405dbc19fc50d0e66bc8fd7b774a/Screenshot_2022-08-29_at_17-35-27_Call_to_Action.png)
+![Call to Action 3](//images.ctfassets.net/alneenqid6w5/48mDM3kOJj3WD78mbAG6Nh/8a9f405dbc19fc50d0e66bc8fd7b774a/Screenshot_2022-08-29_at_17-35-27_Call_to_Action.png)
 
 Clique na opção de selecionar o modelo e escolha uma das opções.
 
-![Call to Action 4](https://images.ctfassets.net/alneenqid6w5/4R7nYhIZUi1L0gD5oVOFEA/00d8afb7e4959e859085cc19b554925f/Screenshot_2022-08-29_at_17-35-31_Call_to_Action.png)
+![Call to Action 4](//images.ctfassets.net/alneenqid6w5/4R7nYhIZUi1L0gD5oVOFEA/00d8afb7e4959e859085cc19b554925f/Screenshot_2022-08-29_at_17-35-31_Call_to_Action.png)
 
 Defina o _**“Layout”**_.
 
-![Call to Action 5](https://images.ctfassets.net/alneenqid6w5/1LL2HrisybDEMXQbBaNHye/30bd353dda1aa5d18274262febc0334a/Screenshot_2022-08-29_at_17-35-37_Call_to_Action.png)
+![Call to Action 5](//images.ctfassets.net/alneenqid6w5/1LL2HrisybDEMXQbBaNHye/30bd353dda1aa5d18274262febc0334a/Screenshot_2022-08-29_at_17-35-37_Call_to_Action.png)
 
 **Imagem**: Você pode editar a imagem inserindo uma imagem com URL válida. Defina o **Título** que irá chamar o cliente e a **Descrição do CTA.** 
 
 Defina as configurações do **Botão**. 
 
-![Call to Action 6](https://images.ctfassets.net/alneenqid6w5/1s8LJePgvvseJLLi80C2lQ/47747ae384541680890ad9a451fb3bf0/Screenshot_2022-08-29_at_17-35-41_Call_to_Action.png)
+![Call to Action 6](//images.ctfassets.net/alneenqid6w5/1s8LJePgvvseJLLi80C2lQ/47747ae384541680890ad9a451fb3bf0/Screenshot_2022-08-29_at_17-35-41_Call_to_Action.png)
 
 Qual será o **link** que ele será encaminhado quando o cliente clicar. 
 
@@ -49,29 +49,29 @@ O **Texto do botão** que irá atrair o seu cliente. 
 
 Defina **configurações**, como por exemplo: Se o botão será centralizado ou não e também o tipo de animação.
 
-![Call to Action  7](https://images.ctfassets.net/alneenqid6w5/72uHGFMsaFZp8uqD4TzgFR/25681bd034fed264b34ddf688d1ba066/Screenshot_2022-08-29_at_17-35-46_Call_to_Action.png)
+![Call to Action  7](//images.ctfassets.net/alneenqid6w5/72uHGFMsaFZp8uqD4TzgFR/25681bd034fed264b34ddf688d1ba066/Screenshot_2022-08-29_at_17-35-46_Call_to_Action.png)
 
 Defina se irá habilitar o **Overlay** , ou seja , se vai sobressair a tela (deixando o restante da tela escura). 
 
-![Call to Action 8](https://images.ctfassets.net/alneenqid6w5/63cr6nJEmIWGbD52fAAiu/d285fd2fec06e4617da564d71eeb8afc/Screenshot_2022-08-29_at_17-35-49_Call_to_Action.png)
+![Call to Action 8](//images.ctfassets.net/alneenqid6w5/63cr6nJEmIWGbD52fAAiu/d285fd2fec06e4617da564d71eeb8afc/Screenshot_2022-08-29_at_17-35-49_Call_to_Action.png)
 
 Faça a configuração para **mobile**.
 
-![Call to Action 9](https://images.ctfassets.net/alneenqid6w5/2Eu4ZBzfPlJc4ixGq9rMiv/4115aa9f05f8139a8660015807fe6600/Screenshot_2022-08-29_at_17-35-53_Call_to_Action.png)
+![Call to Action 9](//images.ctfassets.net/alneenqid6w5/2Eu4ZBzfPlJc4ixGq9rMiv/4115aa9f05f8139a8660015807fe6600/Screenshot_2022-08-29_at_17-35-53_Call_to_Action.png)
 
 Defina os **gatilhos** de exibição do seu CTA.
 
-![Call to Action 10](https://images.ctfassets.net/alneenqid6w5/2syIIyZv2sUW261YP5i2Sr/3469c820d1784ab881e6934fe48536eb/Screenshot_2022-08-29_at_17-35-59_Call_to_Action.png)
+![Call to Action 10](//images.ctfassets.net/alneenqid6w5/2syIIyZv2sUW261YP5i2Sr/3469c820d1784ab881e6934fe48536eb/Screenshot_2022-08-29_at_17-35-59_Call_to_Action.png)
 
 Defina em quais locais do seu site irá aparecer a mensagem ou onde não irá aparecer: 
 
-![Call to Action 11](https://images.ctfassets.net/alneenqid6w5/6L5KjcTvz4DyPOKyuMI0i4/4e7b4f92f6394c984dd3fd9f7680ba22/Screenshot_2022-08-29_at_17-36-04_Call_to_Action.png)
+![Call to Action 11](//images.ctfassets.net/alneenqid6w5/6L5KjcTvz4DyPOKyuMI0i4/4e7b4f92f6394c984dd3fd9f7680ba22/Screenshot_2022-08-29_at_17-36-04_Call_to_Action.png)
 
 Antes de clicar em “_**Salvar**_” clique em “_**preview**_” para confirmar todas as alterações.
 
-![Call to Action 12](https://images.ctfassets.net/alneenqid6w5/5sCyq6lSK5nTONwckiQfV4/1fe29ac73a3edb8276dabd0a5756350f/Screenshot_2022-08-29_at_17-36-10_Call_to_Action.png)
+![Call to Action 12](//images.ctfassets.net/alneenqid6w5/5sCyq6lSK5nTONwckiQfV4/1fe29ac73a3edb8276dabd0a5756350f/Screenshot_2022-08-29_at_17-36-10_Call_to_Action.png)
 
-![Call to Action 13](https://images.ctfassets.net/alneenqid6w5/2lWYEhJyn43e4UElheF0Ga/909281d3af2ac2ad9f0449dc2a93149a/Screenshot_2022-08-29_at_17-36-18_Call_to_Action.png)
+![Call to Action 13](//images.ctfassets.net/alneenqid6w5/2lWYEhJyn43e4UElheF0Ga/909281d3af2ac2ad9f0449dc2a93149a/Screenshot_2022-08-29_at_17-36-18_Call_to_Action.png)
 
 Se não houver nenhuma alteração, clique em _**“Salvar”**_. 
 
diff --git a/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md b/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
index 7003b5f7f..d97b040d6 100644
--- a/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
+++ b/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
@@ -25,4 +25,4 @@ Para isso, siga os passos abaixo:
 
 Para casos de Sellers White Label  há um limite de 50 unidades com o mesmo SKU no carrinho. É possível alterar esse limite mediante uma solicitação no [suporte](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9).
 
-![Carrinho Max PT](https://images.ctfassets.net/alneenqid6w5/3SIx4hvYxGuUkcUs44Us0s/340ea46f5c1bdfd593dc0c87d3b5536a/Carrinho_Max_PT.png)
+![Carrinho Max PT](//images.ctfassets.net/alneenqid6w5/3SIx4hvYxGuUkcUs44Us0s/340ea46f5c1bdfd593dc0c87d3b5536a/Carrinho_Max_PT.png)
diff --git a/docs/tutorials/pt/campaign-audiences-list.md b/docs/tutorials/pt/campaign-audiences-list.md
index 4cb14ba63..52d7db0e0 100644
--- a/docs/tutorials/pt/campaign-audiences-list.md
+++ b/docs/tutorials/pt/campaign-audiences-list.md
@@ -17,7 +17,7 @@ subcategory: 2cI57eZ3ZiWSeaQs26Gwys
 
 A lista de audiências de campanhas cadastradas na sua loja está disponível no Admin VTEX, na página *Promoções > Audiências de campanhas*, ilustrada a seguir.
 
-![lista-audiencias-campanha-pt](https://images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/5c50543b3dc5698d0362a696b91302d2/lista-audiencias-campanha-pt.png)
+![lista-audiencias-campanha-pt](//images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/5c50543b3dc5698d0362a696b91302d2/lista-audiencias-campanha-pt.png)
 
 A partir desta página, você pode realizar as seguintes ações:
 
@@ -50,7 +50,7 @@ As audiências de campanhas são apresentadas em _cards_ com as seguintes inform
 
 Para visualizar as Audiências de campanhas que estão [arquivadas](#arquivar-audiencia-de-campanha), na opção **Exibir**, clique em **Arquivados**, conforme ilustrado a seguir:
 
-![toggle-audiencias-campanha-arquivadas-pt](https://images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/87dca32f5de3ef43c405cad2bda5894b/toggle-audiencias-campanha-arquivadas-pt.png)
+![toggle-audiencias-campanha-arquivadas-pt](//images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/87dca32f5de3ef43c405cad2bda5894b/toggle-audiencias-campanha-arquivadas-pt.png)
 
 Para voltar a visualizar as Audiências de campanhas não arquivadas, clique em **Não Arquivados**.
 
diff --git a/docs/tutorials/pt/campaign-audiences.md b/docs/tutorials/pt/campaign-audiences.md
index 4623a2371..c14510fb5 100644
--- a/docs/tutorials/pt/campaign-audiences.md
+++ b/docs/tutorials/pt/campaign-audiences.md
@@ -27,7 +27,7 @@ Exemplo: no segmento de moda, ao cadastrar uma audiência de campanha, é possí
 
 O público-alvo segmenta os usuários e condições elegíveis da audiência de campanha. Caso a audiência de campanha esteja ativa, ao atender todos os critérios definidos no público-alvo, as promoções associadas à audiência de campanha serão ativadas.
 
-![campanha-pt](https://images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/d8bfd2a4e7f082f2cd1b865bda2f85b0/campanha-pt.png)
+![campanha-pt](//images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/d8bfd2a4e7f082f2cd1b865bda2f85b0/campanha-pt.png)
 
 Quando todas as restrições da campanha forem atingidas e ela estiver ativada e elegível ao contexto de compra, não significa necessariamente que as promoções de audiências de campanhas associadas a ela serão aplicadas. Para isso, as restrições definidas na [promoção de campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) também devem ser atendidas.
 
diff --git a/docs/tutorials/pt/campaign-promotion.md b/docs/tutorials/pt/campaign-promotion.md
index 9d0aeddcd..2e6521433 100644
--- a/docs/tutorials/pt/campaign-promotion.md
+++ b/docs/tutorials/pt/campaign-promotion.md
@@ -122,7 +122,7 @@ Para que a promoção seja válida para todas as políticas comerciais, deixe a
 
 Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
 
-![promocoes-restricao-pt](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
+![promocoes-restricao-pt](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
 
 Caso deseje aplicar a promoção a todo o seu catálogo, selecione a opção **Aplicar a todos os produtos**.
 
@@ -132,7 +132,7 @@ Você pode incluir ou excluir **Categorias**, **Marcas**, **Coleções**, **Prod
 
 Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção todos os produtos da categoria **Home Appliances** cuja marca é **Brastemp**, com exceção do produto **Refrigerator 100**.
 
-![exemplo-pt](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/df98627884fc75e822e742473131299d/image.png)
+![exemplo-pt](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/df98627884fc75e822e742473131299d/image.png)
 
 Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
 
diff --git a/docs/tutorials/pt/canceling-orders.md b/docs/tutorials/pt/canceling-orders.md
index f77674e8b..31359d0c1 100644
--- a/docs/tutorials/pt/canceling-orders.md
+++ b/docs/tutorials/pt/canceling-orders.md
@@ -3,8 +3,8 @@ title: 'Cancelar pedido'
 id: tutorials_186
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:47.296Z
-updatedAt: 2023-03-31T00:26:08.605Z
-publishedAt: 2023-03-31T00:26:08.605Z
+updatedAt: 2024-04-01T17:34:46.564Z
+publishedAt: 2024-04-01T17:34:46.564Z
 firstPublishedAt: 2017-04-27T23:00:46.851Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,23 +17,28 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 O cancelamento de pedido na VTEX pode ser realizado em praticamente qualquer status de sua evolução. Cabe destacar que uma vez cancelado, não é possível alterar o status do pedido.
 
+<div class = "alert alert-warning">
+Não é possível cancelar pedidos que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
+</div>
+
 Há duas formas de fazer esta ação, pelo Admin VTEX e por API.
 
 ## Cancelamento pelo módulo Pedidos
 
 1. No Admin VTEX, acesse **Pedidos > Todos os pedidos**, ou digite *Todos os pedidos* na barra de busca no topo da página.  
-2. Em **Todos os pedidos**, acesse o pedido desejado;
-3. Clique na botão **Cancelar** junto ao card principal do status;
-4. Será solicitada a afirmação de ciência sobre esta ação.
+2. Em **Todos os pedidos**, acesse o pedido desejado.
+3. No topo da página, clique em `Cancelar pedido`.
+4. Preencha os campos apresentados.
+5. Clique em `Confirmar`.
 
 Quando o pedido está nos status **Pronto para Manuseio** ou **Preparando Entrega**, é preciso que o cancelamento seja feito duas vezes. Ao clicar pela primeira vez em "Cancelar", o status é alterado para **Cancelamento Solicitado**.
 Quando o pedido já se encontra no status **Cancelamento solicitado**, basta clicar novamente em **Cancelar** para que o pedido será alterado para **Cancelado**. Para continuar com esse pedido, basta inserir a nota fiscal.
 
-**Lembre-se!** Não é possível alterar um pedido quando o mesmo já está no status **Faturado**.
+Não é possível alterar um pedido quando o mesmo já está no status `Faturado`.
 
 ## Cancelamento pelo ERP
 
-O cancelamento de pedido por meio do ERP pode ser realizado pela nossa API REST, conforme nosso [guia de integração de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing).
+O cancelamento de pedido por meio do ERP pode ser realizado pela nossa API REST, conforme nosso [guia de integração de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing), usando o endpoint [Cancel order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/cancel). 
 
 ## Cancelamento solicitado pelo cliente
 
diff --git a/docs/tutorials/pt/capture-form-suiteshare.md b/docs/tutorials/pt/capture-form-suiteshare.md
index 123711c04..2a4cbb3ab 100644
--- a/docs/tutorials/pt/capture-form-suiteshare.md
+++ b/docs/tutorials/pt/capture-form-suiteshare.md
@@ -23,54 +23,54 @@ Para criar um formulário de Captura é preciso ter o link criado, se você não
 
 Acesse o painel do **VTEX Assisted Sales (SuiteShare)** e clique em _**“Capturar”**_.
 
-![Formulário de Captura 1](https://images.ctfassets.net/alneenqid6w5/a7m5uiN0a4g2Sp0o8oU5H/c7f814fde6c2497d9521b99c9e7cf10c/Screenshot_2022-08-31_at_12-47-31_Formul__rio_de_Captura.png)
+![Formulário de Captura 1](//images.ctfassets.net/alneenqid6w5/a7m5uiN0a4g2Sp0o8oU5H/c7f814fde6c2497d9521b99c9e7cf10c/Screenshot_2022-08-31_at_12-47-31_Formul__rio_de_Captura.png)
 
 Clique no botão _**“Novo”**_.
 
-![Formulário de Captura 2](https://images.ctfassets.net/alneenqid6w5/51nLM13T99dZrNJUZ0kiU7/7959f68fe647d4d88ae2823bcf3aab1e/Screenshot_2022-08-31_at_12-47-36_Formul__rio_de_Captura.png)
+![Formulário de Captura 2](//images.ctfassets.net/alneenqid6w5/51nLM13T99dZrNJUZ0kiU7/7959f68fe647d4d88ae2823bcf3aab1e/Screenshot_2022-08-31_at_12-47-36_Formul__rio_de_Captura.png)
 
 Na opção **Anchor link**, escolha qual é o link que os usuários deverão clicar para aparecer o formulário que eles devem preencher.
 
 **Atenção**:  Esse é o link que você irá compartilhar nas redes sociais e afins.
 
-![Formulário de Captura 3](https://images.ctfassets.net/alneenqid6w5/4om3BBLLz3GZTINDZvFGlK/097fc32cae90ac75da30317b24577ebc/Screenshot_2022-08-31_at_12-47-41_Formul__rio_de_Captura.png)
+![Formulário de Captura 3](//images.ctfassets.net/alneenqid6w5/4om3BBLLz3GZTINDZvFGlK/097fc32cae90ac75da30317b24577ebc/Screenshot_2022-08-31_at_12-47-41_Formul__rio_de_Captura.png)
 
 Após selecionar o link, clique em _**"avançar"**_.
 
-![Formulário de Captura 4](https://images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
+![Formulário de Captura 4](//images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
 
 Selecione o link de destino que os usuários serão direcionados após preencher o formulário. 
 
  **NOTA:** Você pode selecionar um link seletivo, sequencial ou geolocalizado, caso queira direcionar para mais de um atendente/número.
 
-![Formulário de Captura 5](https://images.ctfassets.net/alneenqid6w5/6brAJH7YJQpkR3QRUgYA3j/91b30663f009576bf5cd7ddead169f6a/Screenshot_2022-08-31_at_12-47-51_Formul__rio_de_Captura.png)
+![Formulário de Captura 5](//images.ctfassets.net/alneenqid6w5/6brAJH7YJQpkR3QRUgYA3j/91b30663f009576bf5cd7ddead169f6a/Screenshot_2022-08-31_at_12-47-51_Formul__rio_de_Captura.png)
 
 Se você não sabe como criar esse link de central seletiva, sequencial ou geolocalizado,acesse nossos artigos. 
 
 Clique no botão _**\\"avançar\\".**_
 
-![Formulário de Captura 4](https://images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
+![Formulário de Captura 4](//images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
 
 Selecione quais campos você quer capturar. Nesse caso selecionamos todos os campos: Nome, Telefone e Email.
 
-![Formulário de Captura 6](https://images.ctfassets.net/alneenqid6w5/2BLC4i3qKEsilm7c25H9oe/9088afbd85e94020dcf5050b7fe8a689/Screenshot_2022-08-31_at_12-48-00_Formul__rio_de_Captura.png)
+![Formulário de Captura 6](//images.ctfassets.net/alneenqid6w5/2BLC4i3qKEsilm7c25H9oe/9088afbd85e94020dcf5050b7fe8a689/Screenshot_2022-08-31_at_12-48-00_Formul__rio_de_Captura.png)
 
 Na opção **Modo Robô**, você pode tornar o formulário muito mais intuitivo para os clientes preencherem. Ao ativar essa função, você substitui os campos tradicionais do formulário por um robô que fará as mesmas perguntas. 
 
-![Formulário de Captura 7](https://images.ctfassets.net/alneenqid6w5/5NHkNYGVXMDMucRWB9aO4Y/c466e84c48104b7adfd0701e9e58c8f3/Screenshot_2022-08-31_at_12-48-22_Formul__rio_de_Captura.png)
+![Formulário de Captura 7](//images.ctfassets.net/alneenqid6w5/5NHkNYGVXMDMucRWB9aO4Y/c466e84c48104b7adfd0701e9e58c8f3/Screenshot_2022-08-31_at_12-48-22_Formul__rio_de_Captura.png)
 
 Clique em _**“avançar”**_.
 
 **Atenção!** Se sua captura for a tela inicial do seu chat, escolha o texto da tela do chat.
 
-![Formulário de Captura 8](https://images.ctfassets.net/alneenqid6w5/2ocbRZxxG9j4FGp53ekhO3/5b9c2951dd4b1eb4535677de1c2c2ef5/Screenshot_2022-08-31_at_12-48-29_Formul__rio_de_Captura.png)
+![Formulário de Captura 8](//images.ctfassets.net/alneenqid6w5/2ocbRZxxG9j4FGp53ekhO3/5b9c2951dd4b1eb4535677de1c2c2ef5/Screenshot_2022-08-31_at_12-48-29_Formul__rio_de_Captura.png)
 
 Clique em _**“Finalizar”**_.
 
-![Formulário de Captura 9](https://images.ctfassets.net/alneenqid6w5/VA68YLtSMCEcdytQjELR1/fc449d58ad97c893b882fbd57c76967f/Screenshot_2022-08-31_at_12-48-37_Formul__rio_de_Captura.png)
+![Formulário de Captura 9](//images.ctfassets.net/alneenqid6w5/VA68YLtSMCEcdytQjELR1/fc449d58ad97c893b882fbd57c76967f/Screenshot_2022-08-31_at_12-48-37_Formul__rio_de_Captura.png)
 
 Configure a [aparência](\https://help.vtex.com/pt/tutorial/personalizar--sG7FAksOsU1EW9vcbPgIe), você pode clicar no botão _**“Clique aqui”**_ ou acessar  **Configurações > Minha conta > Aparência**.
 
-![Formulário de Captura 10](https://images.ctfassets.net/alneenqid6w5/7KFaI3M4SiGc8MaOSGjdFM/92ad3df486fa395348cff8dc6056208a/Screenshot_2022-08-31_at_12-48-42_Formul__rio_de_Captura.png)
+![Formulário de Captura 10](//images.ctfassets.net/alneenqid6w5/7KFaI3M4SiGc8MaOSGjdFM/92ad3df486fa395348cff8dc6056208a/Screenshot_2022-08-31_at_12-48-42_Formul__rio_de_Captura.png)
 
 Pronto! Seu formulário de captura foi criado com sucesso e todos os dados preenchidos pelos clientes serão salvos e exibidos no botão Leads. 
diff --git a/docs/tutorials/pt/carrefour-inventory-integration-errors.md b/docs/tutorials/pt/carrefour-inventory-integration-errors.md
index 1cb1707ca..a4b87308f 100644
--- a/docs/tutorials/pt/carrefour-inventory-integration-errors.md
+++ b/docs/tutorials/pt/carrefour-inventory-integration-errors.md
@@ -3,8 +3,8 @@ title: 'Erros de integração de estoque com o Carrefour'
 id: 4oDrYCkrIvWETCW34I2CKF
 status: PUBLISHED
 createdAt: 2021-10-25T22:15:47.447Z
-updatedAt: 2023-03-29T14:40:33.949Z
-publishedAt: 2023-03-29T14:40:33.949Z
+updatedAt: 2024-06-17T15:05:00.226Z
+publishedAt: 2024-06-17T15:05:00.226Z
 firstPublishedAt: 2021-10-25T22:30:07.082Z
 contentType: tutorial
 productTeam: Channels
@@ -27,7 +27,7 @@ Seguem abaixo as mensagens mais comuns de erros de integração de estoque com o
 
 `Produto ainda não foi catalogado no Carrefour. Para reprocessar essa oferta, aguarde a confirmação do Carrefour de que o produto foi catalogado. Para mais detalhes verifique o portal do carrefour.`
 
-O tempo que o Carrefour leva para catalogar novos produtos não pode ser estimado com precisão, e pode levar desde horas a dias, dependendo de processos do marketplace. O estoque de uma loja VTEX só pode ser integrado ao Carrefour após essa catalogação, portanto, é necessário aguardar até que esse processo seja concluído. Uma vez que o produto tenha sido catalogado no Carrefour, a plataforma VTEX automaticamente processa o erro, neste caso não sendo necessário fazer o reprocessamento manual. Para acompanhar a situação junto ao Carrefour, entre em contato pelo [Portal Fornecedor](https://fornecedor.carrefour.com.br/login/).
+O tempo que o Carrefour leva para catalogar novos produtos não pode ser estimado com precisão, e pode levar desde horas a dias, dependendo de processos do marketplace. O estoque de uma loja VTEX só pode ser integrado ao Carrefour após essa catalogação, portanto, é necessário aguardar até que esse processo seja concluído. Uma vez que o produto tenha sido catalogado no Carrefour, a plataforma VTEX automaticamente processa o erro, neste caso não sendo necessário fazer o reprocessamento manual. Para acompanhar a situação junto ao Carrefour, entre em contato pelo [Portal Fornecedor](https://portalfornecedorcarrefour.qa.aevee.com.br/login).
 
 ____
 
@@ -35,7 +35,7 @@ ____
 
 `"status":401,"message":"Unauthorized"`
 
-Este erro indica a perda da autorização da sua integração com o Carrefour, ou seja, trata-se de um problema relacionado ao _token_, também chamado de _ShopKey_. Para o Carrefour, problemas de _token_ podem ocorrer por diferentes motivos, como prazo de validade expirado, ou suspeita de ameaça à segurança, por exemplo. Neste caso, é necessário entrar em contato com o Carrefour para validar o _token_, por meio do [Portal Fornecedor](https://fornecedor.carrefour.com.br/login/). Após essa validação, corrija as configurações do [cadastro do conector da integração](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2/2AhqcmRN1mseCsGuGIe6GK). No seu Admin VTEX, vá em **MARKETPLACE > Conexões > Integrações**. No _card_ do Carrefour, clique sobre o ícone <i class="fas fa-cog"></i> engrenagem, e escolha a opção **Editar configuração**. Preencha o campo _ShopKey_ com o novo _token_ e clique em **Salvar configuração**.
+Este erro indica a perda da autorização da sua integração com o Carrefour, ou seja, trata-se de um problema relacionado ao _token_, também chamado de _ShopKey_. Para o Carrefour, problemas de _token_ podem ocorrer por diferentes motivos, como prazo de validade expirado, ou suspeita de ameaça à segurança, por exemplo. Neste caso, é necessário entrar em contato com o Carrefour para validar o _token_, por meio do [Portal Fornecedor](https://portalfornecedorcarrefour.qa.aevee.com.br/login). Após essa validação, corrija as configurações do [cadastro do conector da integração](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2/2AhqcmRN1mseCsGuGIe6GK). No seu Admin VTEX, vá em **MARKETPLACE > Conexões > Integrações**. No _card_ do Carrefour, clique sobre o ícone <i class="fas fa-cog"></i> engrenagem, e escolha a opção **Editar configuração**. Preencha o campo _ShopKey_ com o novo _token_ e clique em **Salvar configuração**.
 
 <br></br>
 ### Saiba mais
diff --git a/docs/tutorials/pt/carrier-working-hours.md b/docs/tutorials/pt/carrier-working-hours.md
index 008139cd0..0571d6099 100644
--- a/docs/tutorials/pt/carrier-working-hours.md
+++ b/docs/tutorials/pt/carrier-working-hours.md
@@ -3,8 +3,8 @@ title: 'Horário de funcionamento das transportadoras'
 id: 2oGpbInIgdxSWUi3TZjdCS
 status: PUBLISHED
 createdAt: 2019-02-06T16:21:24.412Z
-updatedAt: 2021-08-11T17:43:41.414Z
-publishedAt: 2021-08-11T17:43:41.414Z
+updatedAt: 2024-04-11T00:33:50.619Z
+publishedAt: 2024-04-11T00:33:50.619Z
 firstPublishedAt: 2019-02-06T18:25:37.545Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,32 +15,39 @@ legacySlug: configurar-horario-de-funcionamento-para-transportadoras, configurar
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-Na plataforma VTEX, é possível determinar o horário de funcionamento das transportadoras da sua loja através da configuração de horários de coleta e períodos de envio nos quais você define a disponibilidade das entregas da sua loja.
+Na VTEX, é possível determinar o horário de funcionamento das [transportadoras](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) da sua loja através de configurações na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), na qual você define os períodos válidos para a transportadora coletar e enviar pedidos.
 
-Para configurar o horário de funcionamento, vá em **Estoque & Entrega > Estratégia de envio** e crie uma nova [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) ou edite uma existente. 
+Para configurar o horário de funcionamento, no seu Admin VTEX, acesse **Envio > Estratégia de envio** e crie uma [nova política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) ou [edite](https://help.vtex.com/pt/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE) uma existente. 
 
 As configurações de horário de funcionamento influenciam o cálculo do tempo de entrega e estão ao final da página de detalhes da política de envio selecionada com as seguintes opções:
 
-* **[Período de Envio](#periodo-de-envio)**: períodos em que a transportadora envia itens para os clientes.
-* **[Horário de Coleta](#horario-de-coleta)**: horários em que a transportadora faz a coleta de itens para envio.
+* **[Janela de envio](#janela-de-envio)**: períodos em que a transportadora envia itens para os clientes.
+* **[Horário de coleta](#horario-de-coleta)**: horários em que a transportadora faz a coleta de itens para envio.
 
-## Período de Envio
+## Janela de envio
 
-1. Clique em `Período de Envio`;
-2. Habilite ou não o item `Aceitar compras fora do horário de funcionamento`:
+1. Na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), na seção **Horário de funcionamento**, clique em `Janela de envio`.
+2. Se você deseja ativar a opção `Aceitar compras fora do horário de funcionamento`, ative o toggle. Caso contrário, deixe-o desativado.
 
-    Ative se a transportadora aceitar receber vendas fora do seu horário de funcionamento. Ao deixar esse item como `ATIVA`, o cálculo do tempo de entrega será influenciado (o intervalo de tempo do momento da realização do pedido até o horário de início da transportadora será somado ao tempo total da entrega);
+  <div class="alert alert-danger">
+Para autorizar a transportadora a receber pedidos nos finais de semana, este toggle deve ser marcado como <code>Ativo</code>. Mesmo se sábados e domingos estiverem configurados como janelas válidas, a ativação do toggle é obrigatória para autorizar a transportadora a receber pedidos fora do horário de funcionamento.
+</div>
 
-3. Selecione o `Dia da semana` e respectivamente o `Horário de início` e `Horário de fim` da envio, sendo:
-    * **Dia da semana:** os dias da semana que a transportadora faz as entregas;
-    * **Horário de início:** o horário que começa o período de envio;
-    * **Horário de fim:** o horário que termina o período de envio.
-4. Clique em `Adicionar período de envio` para adicionar um novo período;
-5. Ao final clique no botão `Salvar alterações`.
+  <div class = "alert alert-info">
+Quando esta opção está habilitada, o <a href="https://help.vtex.com/pt/tutorial/how-shipping-calculation-works--tutorials_116">cálculo de envio</a> do pedido é influenciado, e o tempo desde a realização do pedido até o horário de início de funcionamento da transportadora é somado ao tempo de envio total de envio.
+</div>
 
-## Horário de Coleta
+3. Selecione o `Dia da semana` e respectivamente o `Horário de início` e `Horário de término` do envio, sendo:
+    * **Dia da semana:** os dias da semana que a transportadora faz as entregas.
+    * **Horário de início:** o horário que começa o período de envio.
+    * **Horário de término:** o horário que termina o período de envio.
+4. Para adicionar um novo período, clique em `Adicionar janela de envio`.
+5. Clique em `Salvar alterações`.
 
-1. Clique na janela `Horário de Coleta`;
-2. Selecione `Dia da semana` e `Horário de coleta`; 
-3. Clique em `Adicionar horário de coleta` para adicionar um novo horário;
-4. Ao final clique no botão `Salvar alterações`.
+## Horário de coleta
+
+1. Na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), na seção **Horário de funcionamento**, clique na janela `Horário de coleta`.
+2. Selecione um `Dia da semana`.
+3. Selecione um `Horário de coleta`. 
+4. Para adicionar um novo horário, clique em `Adicionar horário de coleta`.
+5. Clique em `Salvar alterações`.
diff --git a/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
index 03c859255..4fe6823a1 100644
--- a/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -24,7 +24,7 @@ O módulo *Estoque & Entrega* é onde você faz todo o gerenciamento da logísti
 Algumas seções da página de cadastro de **Política de Envio** mudaram, para te dar mais flexibilidade ao configurar sua estratégia de entrega. Na versão anterior, havia uma seção chamada *Configuração de Tempo*, na qual era possível selecionar *Horário de Funcionamento*, *Horário de Corte* ou *Entrega Agendada* para cada transportadora. 
 
 **Versão anterior**
-![PT Configurações de tempo versão antiga](https://images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/853e5c8125a87076697643bbb62848a0/PT_Configura____es_de_tempo_vers__o_antiga.jpg)
+![PT Configurações de tempo versão antiga](//images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/853e5c8125a87076697643bbb62848a0/PT_Configura____es_de_tempo_vers__o_antiga.jpg)
 
 Na nova versão:
 - Mudamos os nomes das opções para facilitar seu entendimento.   
@@ -32,7 +32,7 @@ Na nova versão:
 - Adicionamos a opção de configurar capacidade de entrega, para que a entrega agendada seja feita com base na realidade da sua operação.   
 
 **Versão Beta**
-![PT Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![PT Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 ## Horário de coleta
 
@@ -49,7 +49,7 @@ Assim como na versão anterior, não é possível configurar as opções de *Per
 Antes só era possível optar pela funcionalidade de *Entrega Agendada* abrindo mão do *Horário de Funcionamento*. Agora é possível configurar a opção de *Entrega Agendada* juntamente com o *Horário de Funcionamento* para que seu cliente opte por esse método de entrega durante o checkout de seu pedido. Confira os campos de preenchimento para configurar essa opção.
 
 **Versão Beta**
-![PT entrega agendada](https://images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/2de3b092c9265fce7aa6d5478f2de5dd/PT_entrega_agendada.jpg)
+![PT entrega agendada](//images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/2de3b092c9265fce7aa6d5478f2de5dd/PT_entrega_agendada.jpg)
 
 - **Tempo máximo de entrega**: esse campo deve ser preenchido de acordo com a sua operação logística. Defina qual é o maior período de tempo que aquela transportadora gasta para realizar uma entrega agendada, entre a confirmação do pedido e a confirmação da entrega.
 - **Configurar capacidade de entrega**: dependendo das características da sua operação, e de como a transportadora envia os seus produtos, pode fazer mais sentido definir uma capacidade de entrega em número de itens, ou em número de pedidos. Se sua loja for do segmento de supermercado, por exemplo, e o meio de transporte para a entrega agendada for por moto, existe um número limite de itens que cabem na armazenagem daquele veículo, portanto sugerimos que selecione `itens` como unidade. Já se sua operação tiver poucos itens por pedido, fará mais sentido determinar `pedidos` como unidade, por exemplo.
diff --git a/docs/tutorials/pt/carries-on-vtex.md b/docs/tutorials/pt/carries-on-vtex.md
index acd988e1c..2775696ba 100644
--- a/docs/tutorials/pt/carries-on-vtex.md
+++ b/docs/tutorials/pt/carries-on-vtex.md
@@ -3,8 +3,8 @@ title: 'Transportadoras na VTEX'
 id: 7u9duMD5UQa2QQwukAWMcE
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:39.775Z
-updatedAt: 2023-03-31T01:00:22.710Z
-publishedAt: 2023-03-31T01:00:22.710Z
+updatedAt: 2023-07-31T22:14:54.618Z
+publishedAt: 2023-07-31T22:14:54.618Z
 firstPublishedAt: 2019-01-24T22:14:26.579Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/pt/catalog-overview-2.md b/docs/tutorials/pt/catalog-overview-2.md
index 77ca7cf3f..468862d19 100644
--- a/docs/tutorials/pt/catalog-overview-2.md
+++ b/docs/tutorials/pt/catalog-overview-2.md
@@ -1,10 +1,10 @@
 ---
 title: 'Visão Geral Catálogo'
 id: FFrumKPYFpvIWKRXfhQYp
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-28T17:25:52.296Z
-updatedAt: 2023-03-28T17:31:02.205Z
-publishedAt: 2023-03-28T17:31:02.205Z
+updatedAt: 2024-03-14T16:38:37.477Z
+publishedAt: 
 firstPublishedAt: 2023-03-28T17:31:02.205Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -24,8 +24,6 @@ O menu **Catálogo** contém as funcionalidades referentes ao sortimento de prod
 
 O menu **Catálogo** do Admin VTEX reúne as páginas onde você gerencia catálogo, preços e inventário do seu ecommerce.
 
-![visao-geral-produto-PT](//images.contentful.com/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/e5cf20175dc73345dbf7c9330fcf29e4/image.png)
-
 Confira abaixo mais detalhes sobre as diferentes seções e páginas deste menu.
 
 ## Catálogo
diff --git a/docs/tutorials/pt/catalog-overview.md b/docs/tutorials/pt/catalog-overview.md
index 814f67e0b..9f86babf7 100644
--- a/docs/tutorials/pt/catalog-overview.md
+++ b/docs/tutorials/pt/catalog-overview.md
@@ -15,27 +15,25 @@ legacySlug: catalogo-visao-geral
 subcategory: 
 ---
 
-![Overview do catálogo (capa)](https://raw.githubusercontent.com/vtexdocs/help-center-content/main/images/pt/catalogo-visao-geral-0.jpg)
-Catálogo é o módulo de administração da sua loja que possibilita configurar as funcionalidades referentes aos produtos do seu ecommerce. Para que o seu cliente veja os produtos no site, você precisa cadastrá-los neste módulo.
+![Overview do catálogo (capa)](//images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/381c53d2f596018d117c044d38d70ab4/image1.jpg)
+Catálogo é o módulo de administração da sua loja que possibilita configurar as funcionalidades referentes aos produtos do seu ecommerce. Para que o seu cliente veja os produtos no site, você precisa cadastrá-los neste módulo. 
 
 Neste artigo você encontrará uma visão geral dos itens do catálogo e suas funcionalidades.
 
 ## Categorias
-
 A Categoria é o segundo nível de categorização da sua loja, logo abaixo do nível [Departamentos](https://help.vtex.com/pt/tutorial/o-que-e-um-departamento--22rKjmYWVmmKAK8CWa8yKw?&utm_source=autocomplete), que são seções ou setores que classificam as áreas do seu negócio. Ela é essencial para o cadastro de produtos.
 
 O módulo **Categorias** permite visualizar e gerenciar a árvore de categorias cadastradas na sua loja, como mostrado no exemplo abaixo.
 
-![Estrutura do catálogo](https://raw.githubusercontent.com/vtexdocs/help-center-content/main/images/pt/catalogo-visao-geral-1.png)
+![Estrutura do catálogo](//images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/66d1260822745c13cc2771f79289a131/image3.png)
 
 Você pode cadastrar uma categoria seguindo o tutorial [Cadastrar uma Categoria](https://help.vtex.com/pt/tutorial/cadastrando-categoria--tutorials_206). Se deseja gerenciar ou inativar uma categoria, siga os passos do tutorial [Inativar e reorganizar categorias](https://help.vtex.com/pt/tutorial/inativando-e-reorganizando-categorias--tutorials_264).
 
 Dentro do módulo Categorias, existem as [Subcategorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-subcategoria--2cb0aRkG3i6AeiAMM24iwY), terceiro nível de categorização da loja. Elas garantem que os usuários encontrem rapidamente os produtos que procuram.
 
-As  [Categorias similares](https://help.vtex.com/pt/tutorial/configurando-categoria-similar--tutorials_204?&utm_source=autocomplete) possibilitam que um produto esteja em mais de uma categoria ao mesmo tempo, e as [Categorias globais](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188?&utm_source=autocomplete) são utilizadas para integrações externas, como, por exemplo, com marketplaces ou demais canais de venda.
+As  [Categorias similares](https://help.vtex.com/pt/tutorial/configurando-categoria-similar--tutorials_204?&utm_source=autocomplete) possibilitam que um produto esteja em mais de uma categoria ao mesmo tempo, e as [Categorias globais](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188?&utm_source=autocomplete) são utilizadas para integrações externas, como, por exemplo, com marketplaces ou demais canais de venda. 
 
 ## Marcas
-
 A Marca é um campo obrigatório para a criação de um produto, pois sem ela não é possível cadastrá-lo. Na VTEX, existe uma seção específica para você cadastrar as marcas dos produtos disponibilizados na sua loja.
 
 Ao associar uma marca aos seus produtos, você poderá criar uma navegação utilizando esse atributo como filtro na sua loja. É bem comum que os clientes busquem produtos utilizando uma marca como palavra-chave.
@@ -45,7 +43,6 @@ Ao associar uma marca aos seus produtos, você poderá criar uma navegação uti
 É possível cadastrar uma marca seguindo o tutorial  [Cadastrar marcas](https://help.vtex.com/pt/tutorial/cadastrando-marcas--tutorials_1414).
 
 ## Produtos e SKUs
-
 O produto é a definição mais genérica de algo que é disponibilizado na sua loja, como "Camisa". Já os SKUs são variações deste produto, como cor e tamanho, por exemplo.
 
 É possível ter a mesma Camisa (produto) nos tamanhos P, M ou G , que são as especificações. A combinação de especificações de um produto é um SKU, como Camisa P. É obrigatório que um produto tenha pelo menos um SKU.
@@ -63,25 +60,21 @@ A especificação de SKU é utilizada para criar filtros de navegação no site
 Para cadastrar uma especificação, acesse os tutoriais [Criar um campo de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106?&utm_source=autocomplete), [Configurar tipo de especificação](https://help.vtex.com/pt/tutorial/configurando-tipo-de-campo-de-categoria--tutorials_286) e [Criar grupo de categoria](https://help.vtex.com/pt/tutorial/criando-grupo-de-categoria--tutorials_246).
 
 ## Importação e exportação
-
-Essa funcionalidade permite que o usuário do Admin importe [Imagens](https://help.vtex.com/pt/tutorial/importando-imagens-por-planilha--tutorials_262?&utm_source=autocomplete), [Produtos](https://help.vtex.com/pt/tutorial/como-exportar-planilha-de-produtos--2sIroGeqZqaN3NAvaSGwWV?&utm_source=autocomplete), [SKUs](https://help.vtex.com/pt/tutorial/importando-e-exportando-especificacao-de-produto-e-sku--tutorials_274?&utm_source=autocomplete), Marcas e [Planilhas de estoque](https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034?&utm_source=autocomplete) para a sua loja através de planilhas, facilitando o preenchimento em massa.
+Essa funcionalidade permite que o usuário do Admin importe [Imagens](https://help.vtex.com/pt/tutorial/importando-imagens-por-planilha--tutorials_262?&utm_source=autocomplete), [Produtos](https://help.vtex.com/pt/tutorial/como-exportar-planilha-de-produtos--2sIroGeqZqaN3NAvaSGwWV?&utm_source=autocomplete), [SKUs](https://help.vtex.com/pt/tutorial/importando-e-exportando-especificacao-de-produto-e-sku--tutorials_274?&utm_source=autocomplete), Marcas e [Planilhas de estoque](https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034?&utm_source=autocomplete) para a sua loja através de planilhas, facilitando o preenchimento em massa. 
 
 Para entender melhor como utilizar essa funcionalidade, leia o artigo [Preencher campos da planilha de importação](https://help.vtex.com/pt/tutorial/preencher-campos-da-planilha-de-importacao--4nYhx63Q5yokQWaMguaIgI).
 
 ## Tipos de lista
-
-Listas são agrupamentos de produtos que você pode disponibilizar na sua loja para seus clientes. Elas podem ter diversos tipos e estar associadas a eventos, como casamentos, chás de panela, aniversários ou qualquer outra ocasião que seu consumidor queira criar.
+Listas são agrupamentos de produtos que você pode disponibilizar na sua loja para seus clientes. Elas podem ter diversos tipos e estar associadas a eventos, como casamentos, chás de panela, aniversários ou qualquer outra ocasião que seu consumidor queira criar. 
 
 Essa seção é responsável pela configuração das listas que estarão disponíveis no site. Para saber como criar uma lista, siga o tutorial [Criar tipo de lista](https://help.vtex.com/pt/tutorial/criando-tipo-de-lista--tutorials_254?&utm_source=autocomplete).
 
 ## Anexos
-
 Um anexo é uma customização opcional com objetivo de complementar o produto com uma especificação personalizada. Ele pode ser relacionado a um serviço ou ao próprio item comprado, e pode ou não ter um custo adicional.
 
 Para cadastrar um anexo, siga os passos do tutorial [Cadastrar um anexo](https://help.vtex.com/pt/tutorial/cadastrar-um-anexo). Para cenários complexos, é possível configurar um [Assembly Option](https://help.vtex.com/es/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH).
 
 ## Integração XML
-
 XML é uma linguagem de marcação que permite a comunicação entre computadores e aplicações. Sua principal característica é a estrutura hierarquicamente organizada para a criação de textos e banco de dados.
 
 Na VTEX, a funcionalidade de configuração do XML utiliza combinações entre diferentes padrões. Isso possibilita que outros bancos de dados leiam as estruturas criadas pelo banco de dados da VTEX.
@@ -89,43 +82,40 @@ Na VTEX, a funcionalidade de configuração do XML utiliza combinações entre d
 Para entender como configurar um XML, siga os passos do tutorial [Configurando XML](https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242?&utm_source=autocomplete).
 
 ## Relatórios
-
 É possível obter relatórios sobre movimentações na sua loja. Os relatórios disponíveis na loja são:
 
-- [Relatório de segurança](https://help.vtex.com/pt/tutorial/entendendo-o-relatorio-de-seguranca--tutorials_282?&utm_source=autocomplete)
-- [Relatório de indexação](https://help.vtex.com/pt/tutorial/utilizar-o-relatorio-de-indexa%C3%A7%C3%A3o--4ikVpMhwByyS8sysaeOIm4?&utm_source=autocomplete)
-- Relatório de lista de compras
-- Relatório do Avise-me
-- Relatório de newsletter
-- [Relatório de avaliação](https://help.vtex.com/pt/tutorial/acessar-as-avaliacoes-de-produtos--139sIVny6fyXK0Nk60L1NF)
-- Relatório de downloads
+ - [Relatório de segurança](https://help.vtex.com/pt/tutorial/entendendo-o-relatorio-de-seguranca--tutorials_282?&utm_source=autocomplete)
+ - [Relatório de indexação](https://help.vtex.com/pt/tutorial/utilizar-o-relatorio-de-indexa%C3%A7%C3%A3o--4ikVpMhwByyS8sysaeOIm4?&utm_source=autocomplete)
+ - Relatório de lista de compras
+ - Relatório do Avise-me
+ - Relatório de newsletter
+ - [Relatório de avaliação](https://help.vtex.com/pt/tutorial/acessar-as-avaliacoes-de-produtos--139sIVny6fyXK0Nk60L1NF)
+ - Relatório de downloads
 
 ## Condições comerciais
-
 A condição comercial é um agrupador de SKUs que serve para criar diferentes cenários de pagamento. Um exemplo dessa configuração é possibilitar o parcelamento em 12 vezes no cartão de crédito apenas para eletrônicos da sua loja.
 
 Para cadastrar uma condição comercial, siga o tutorial [Cadastrar condições comerciais](https://help.vtex.com/pt/tutorial/como-cadastrar-condicao-comercial--tutorials_445).
 
 ## Fornecedores
-
 Essa funcionalidade permite o cadastro de fornecedores para sua loja ou marketplace. Para cadastrar um fornecedor, siga os passos abaixo.
 
 No Admin, clique em **Catálogo** >  **Fornecedores**.
 Clique em `Novo Fornecedor`.
 Preencha os campos de cadastro a seguir:
 
-- **Nome:** Preencha com o nome do fornecedor. Este é um campo obrigatório.
-- **Razão Social:** Este campo deverá ser preenchido com a Razão Social do fornecedor.
-- **Inscrição Estadual:** Este campo deve ser preenchido com o registro do fornecedor no cadastro de ICMS.
-- **CNPJ:** Este campo deve ser preenchido com o CNPJ do fornecedor.
-- Preencha os dados de contato do fornecedor.
-- Clique em `Salvar`.
+ - **Nome:** Preencha com o nome do fornecedor. Este é um campo obrigatório.
+ - **Razão Social:** Este campo deverá ser preenchido com a Razão Social do fornecedor. 
+ - **Inscrição Estadual:** Este campo deve ser preenchido com o registro do fornecedor no cadastro de ICMS.
+ - **CNPJ:** Este campo deve ser preenchido com o CNPJ do fornecedor.
+ - Preencha os dados de contato do fornecedor.
+ - Clique em `Salvar`.
 
 ## Coleções
-
 Coleção é o agrupamento de dois ou mais SKUs que podem ou não ter características em comum para serem apresentados em páginas de produtos da sua loja.
 
 As coleções podem ser criadas para associar SKUs utilizando outros critérios de agrupamento como datas comemorativas, lançamentos ou produtos mais vendidos.
 
 Você pode, por exemplo, criar uma página em comemoração ao Dia dos Namorados e fazer com que ela liste presentes recomendados para a ocasião, criando uma coleção de “presentes”.
 Para criar uma coleção, siga o tutorial [Criar coleções.](https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye)
+
diff --git a/docs/tutorials/pt/categories.md b/docs/tutorials/pt/categories.md
index 6eeb47ae1..959aca637 100644
--- a/docs/tutorials/pt/categories.md
+++ b/docs/tutorials/pt/categories.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 A página **Categorias** permite visualizar e gerenciar a árvore de categorias cadastradas no Seller Portal. Você pode acessar a página no Admin VTEX em **Catálogo** > **Categorias**.
 
-![categorias-pt](https://images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/8bbda2aa615c249815bae0424ead68c7/categorias-pt.PNG)
+![categorias-pt](//images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/8bbda2aa615c249815bae0424ead68c7/categorias-pt.PNG)
 
 A partir da árvore de categorias, você pode realizar uma variedade de ações:
 
diff --git a/docs/tutorials/pt/category-registration-fields.md b/docs/tutorials/pt/category-registration-fields.md
index bacd4e894..5258df30f 100644
--- a/docs/tutorials/pt/category-registration-fields.md
+++ b/docs/tutorials/pt/category-registration-fields.md
@@ -3,8 +3,8 @@ title: 'Preencher campos de cadastro de Categoria'
 id: 5Z7RrvW41yumyQCmk2iqoG
 status: PUBLISHED
 createdAt: 2017-09-20T14:44:06.897Z
-updatedAt: 2022-08-01T18:47:26.486Z
-publishedAt: 2022-08-01T18:47:26.486Z
+updatedAt: 2024-01-04T14:40:33.174Z
+publishedAt: 2024-01-04T14:40:33.174Z
 firstPublishedAt: 2017-09-20T14:58:27.420Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -43,8 +43,8 @@ Para entender melhor o significado de cada campo do cadastro de categoria, veja
 - __Score (usado para ordenação de busca):__ valor utilizado para definir a prioridade na página de resultado de busca. Para entender mais sobre Score, acesse o nosso artigo [Como funciona o campo score](https://help.vtex.com/pt/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae).
 - __Modo de exibição dos produtos:__ define como os SKUs serão exibidos na página do produto. Veja abaixo as opções de preenchimento deste campo:
   - __Lista de SKUs:__ todos os SKUs do departamento ou categoria em questão serão exibidos no formato de lista. Cada um com seu botão Comprar do lado.
-  ![1Lista.pt](https://images.ctfassets.net/alneenqid6w5/6mWjVoqS6SVTNngaDC2s0f/833590ef9a7ca23a80ca3064158eacf4/Lista.pt.png)
+  ![1Lista.pt](//images.ctfassets.net/alneenqid6w5/6mWjVoqS6SVTNngaDC2s0f/833590ef9a7ca23a80ca3064158eacf4/Lista.pt.png)
   - __Ícones de seleção de radio (radioBox):__ todos os SKUs do departamento ou categoria em questão precisarão ser selecionados através de seleção de radio.
-  ![RadioBox.pt](https://images.ctfassets.net/alneenqid6w5/6KPwMsYzYcdbLSaxuaXujO/da99f6ea4f3c41846d7370bd334e67d9/RadioBox.pt.png)
+  ![RadioBox.pt](//images.ctfassets.net/alneenqid6w5/6KPwMsYzYcdbLSaxuaXujO/da99f6ea4f3c41846d7370bd334e67d9/RadioBox.pt.png)
   - __Segue definição da especificação do SKU:__ todos os SKUs do departamento ou categoria em questão serão selecionados de acordo com a aba Especificação, no formulário de SKU. As opções pré-configuradas são Combo ou Radio.
-  ![Campos.pt](https://images.ctfassets.net/alneenqid6w5/U6fp5beQoHb9N8NFfbzJE/737de2d0a29e27ca99e8e3199e6cc4cd/Campos.pt.png)
+  ![Campos.pt](//images.ctfassets.net/alneenqid6w5/U6fp5beQoHb9N8NFfbzJE/737de2d0a29e27ca99e8e3199e6cc4cd/Campos.pt.png)
diff --git a/docs/tutorials/pt/change-a-placeholder-title.md b/docs/tutorials/pt/change-a-placeholder-title.md
index dc428e4c9..71976c8bc 100644
--- a/docs/tutorials/pt/change-a-placeholder-title.md
+++ b/docs/tutorials/pt/change-a-placeholder-title.md
@@ -17,20 +17,20 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 O título de um placeholder é o que aparece no canto direito do objeto, como indica a imagem abaixo.
 
-![cms-placeholder pt](https://images.ctfassets.net/alneenqid6w5/2B81NqQBPqi6MgEAawOU4I/00578c25664eab1bded200712d574959/placeholder_destaque.png)
+![cms-placeholder pt](//images.ctfassets.net/alneenqid6w5/2B81NqQBPqi6MgEAawOU4I/00578c25664eab1bded200712d574959/placeholder_destaque.png)
 
 O texto que for inserido nesse campo é o que será exibido como título do placeholder no site da loja.
 
 Seguindo o exemplo acima, teríamos o seguinte na loja:
 
-![exemplo-placeholder pt](https://images.ctfassets.net/alneenqid6w5/3J1Xr0TrkQU8EoYsss26Ke/84287c72e31c8246e5c3f2d96a1ab740/loja_pedro_exemplo_placeholder.png)
+![exemplo-placeholder pt](//images.ctfassets.net/alneenqid6w5/3J1Xr0TrkQU8EoYsss26Ke/84287c72e31c8246e5c3f2d96a1ab740/loja_pedro_exemplo_placeholder.png)
 
 Para alterar o título de um placeholder, basta seguir os passos abaixo:
 
 1. Clique no título.
 
 2. Insira o novo título.
-![placeholder-change-name pt](https://images.ctfassets.net/alneenqid6w5/59J7ZEZe4w8uAS2kGa4qIW/9f8adbf11d44c3ffe54d9178fbb363dc/change_name_pt.png)
+![placeholder-change-name pt](//images.ctfassets.net/alneenqid6w5/59J7ZEZe4w8uAS2kGa4qIW/9f8adbf11d44c3ffe54d9178fbb363dc/change_name_pt.png)
 
 3. Clique em __Rename__.
 
diff --git a/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md b/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
index 061290260..8e22e69d5 100644
--- a/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
+++ b/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
@@ -34,7 +34,7 @@ Existem duas possibilidades de troca de seller:
 
 | **Ativo** | **Desativo** |
 |----|
-| ![Recusar](https://images.ctfassets.net/alneenqid6w5/3ko5d7jnhUZh4HDxx3hr6d/3acaa50706a0938f0cbd30446cfebff1/Recusar.png) | ![Cancelar](https://images.ctfassets.net/alneenqid6w5/2ZS1DTLiKFlHJYBVyuYMhQ/4f13f9c482acaa7e7baddb7b4c0070eb/Cancelar.png) |
+| ![Recusar](//images.ctfassets.net/alneenqid6w5/3ko5d7jnhUZh4HDxx3hr6d/3acaa50706a0938f0cbd30446cfebff1/Recusar.png) | ![Cancelar](//images.ctfassets.net/alneenqid6w5/2ZS1DTLiKFlHJYBVyuYMhQ/4f13f9c482acaa7e7baddb7b4c0070eb/Cancelar.png) |
 
 ## Troca automática de seller
 
@@ -42,7 +42,7 @@ Após a recusa de um pedido no VTEX Sales App, o sistema irá procurar automatic
 
 Recomendamos que, caso um seller não seja encontrado automaticamente, seja realizada a [troca de seller manualmente](#troca-manual-de-seller). Para habilitar essa funcionalidade, entre em contato com o [Suporte da VTEX](https://support.vtex.com/hc/pt-br/requests). 
 
-![pedidos recusados PT](https://images.ctfassets.net/alneenqid6w5/5goolXgsNzyW6iIomwQViD/8dc2cf8b5ed5e14ef4df62d71d290514/image.png)
+![pedidos recusados PT](//images.ctfassets.net/alneenqid6w5/5goolXgsNzyW6iIomwQViD/8dc2cf8b5ed5e14ef4df62d71d290514/image.png)
 
 ## Troca manual de seller
 
@@ -52,10 +52,10 @@ Para trocar manualmente o seller de um pedido no VTEX Sales App, siga os passos
 2. Na seção **Pedidos recusados**, clique no pedido que deseja trocar o seller. Caso a sua loja não tenha nenhum pedido recusado, essa seção ficará oculta.
 3. Na página do pedido, clique em `Trocar seller`.
 4. Selecione o seller desejado para o pedido. Na janela será apresentado o prazo de entrega e preço do frete de cada seller, além de indicar qual seller apresenta menor prazo.
-![trocar seller PT](https://images.ctfassets.net/alneenqid6w5/5qXGxdwH7F6uJfpL1jVSiT/d88d155df80d7664e3afe56c0fc9e709/image.png)
+![trocar seller PT](//images.ctfassets.net/alneenqid6w5/5qXGxdwH7F6uJfpL1jVSiT/d88d155df80d7664e3afe56c0fc9e709/image.png)
 5. Após selecionar o seller, clique em `Continuar`.
 6. Confira as informações da troca de seller e clique em `Confirmar` para finalizar.
-![trocar seller 2 PT](https://images.ctfassets.net/alneenqid6w5/7DLR4MFL58OoL4tmQNAgJf/6ff588942b260ec8585a7fc7350dcaa3/image.png)
+![trocar seller 2 PT](//images.ctfassets.net/alneenqid6w5/7DLR4MFL58OoL4tmQNAgJf/6ff588942b260ec8585a7fc7350dcaa3/image.png)
 
 <div class ="alert alert-info">
 <p>O cliente só será notificado da troca de seller por email caso o prazo de entrega seja diferente do que o original.</p>
diff --git a/docs/tutorials/pt/change-seller.md b/docs/tutorials/pt/change-seller.md
index 8c6701eac..9cb6d7dd2 100644
--- a/docs/tutorials/pt/change-seller.md
+++ b/docs/tutorials/pt/change-seller.md
@@ -26,13 +26,13 @@ A troca de seller pode ocorrer em duas situações:
 - Seller cancela o pedido.
 - Marketplace decide trocar o seller.
 
-![seller_cancela_pedido_PT](https://images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/ec1baf2bf28bddace01121efce7c05a8/seller_cancela_pedido_PT.png)
+![seller_cancela_pedido_PT](//images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/ec1baf2bf28bddace01121efce7c05a8/seller_cancela_pedido_PT.png)
 
 Você pode [configurar a janela de tempo para mudar seller de 0 a 30 dias](https://developers.vtex.com/vtex-rest-api/reference/updatewindowtochangeseller), sendo que, por padrão, são dois dias. Ao configurar a janela em 0 dias, não existe um período efetivo para a troca de sellers e a feature, apesar de configurada, não funciona na prática, fazendo com que o pedido siga para cancelamento.
 
 Ao ser notificado pelo seller sobre o cancelamento, o marketplace pode configurar quantos dias deseja para tomar uma ação e decidir entre cancelar a compra ou mudar de seller. Mas atenção: caso escolha pela troca, é de responsabilidade do próprio marketplace a decisão de informar a mudança ao cliente final.
 
-![mkt_cancela_seller_PT](https://images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/55e6407af7ab3ffc3adec059e393f45c/mkt_cancela_seller_PT.png)
+![mkt_cancela_seller_PT](//images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/55e6407af7ab3ffc3adec059e393f45c/mkt_cancela_seller_PT.png)
 
 ## Limitações
 
diff --git a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
index d930f0e51..20d0f0c96 100644
--- a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -34,7 +34,7 @@ Após [habilitar a funcionalidade](https://developers.vtex.com/vtex-rest-api/doc
 3. Modifique o preço para o valor desejado e aperte `ENTER`.
 4. Clique em `Fechar pedido`.
 
-![manualprice](https://images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/286bde9df13e523ada732e2d89d70101/manualprice.gif)
+![manualprice](//images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/286bde9df13e523ada732e2d89d70101/manualprice.gif)
 
 Além da configuração na tela do Checkout, o preço de um produto também pode ser modificado por meio da API [Change Price](https://developers.vtex.com/vtex-rest-api/reference/pricechange), saiba mais em [Setting the price of an item manually](https://developers.vtex.com/vtex-rest-api/docs/enable-the-manual-price#setting-the-price-of-an-item-manually).
 
diff --git a/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
index aef809a91..3a0891ae9 100644
--- a/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
@@ -51,9 +51,9 @@ Ou seja, estou usando as variáveis `preposicaonomeloja2` e `nomeloja`.
 Ao usar variáveis para compor um texto, substitua o símbolo <code>#</code> por <code>@</code>. Ou seja, <b>#variavel#</b> torna-se <b>@variavel@</b>.
 </div>
 
-![textos-importante pt](https://images.ctfassets.net/alneenqid6w5/6B5XvqyDYI4G4eaC8OGEUw/8e55774262373bc01757e12736fe8f39/textos_importantes_pt.png)
+![textos-importante pt](//images.ctfassets.net/alneenqid6w5/6B5XvqyDYI4G4eaC8OGEUw/8e55774262373bc01757e12736fe8f39/textos_importantes_pt.png)
 
-![exemplo-texto-importante pt ](https://images.ctfassets.net/alneenqid6w5/3cyb4MfQGIu0kc424oYSqo/4d0e1d3bc0bb4af90feaad9398c6a807/3_pt.png)
+![exemplo-texto-importante pt ](//images.ctfassets.net/alneenqid6w5/3cyb4MfQGIu0kc424oYSqo/4d0e1d3bc0bb4af90feaad9398c6a807/3_pt.png)
 
 Como defini que o conteúdo da primeira variável é "à" e o da segunda é "Loja Exemplo", o texto final renderizado no site será "Seja bem-vindo à Loja Exemplo".
 
diff --git a/docs/tutorials/pt/changing-items-from-a-complete-order.md b/docs/tutorials/pt/changing-items-from-a-complete-order.md
index ae75c9b03..ad11278eb 100644
--- a/docs/tutorials/pt/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/pt/changing-items-from-a-complete-order.md
@@ -3,8 +3,8 @@ title: 'Alteração de itens de um pedido finalizado'
 id: tutorials_190
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:22.411Z
-updatedAt: 2023-05-03T14:22:00.584Z
-publishedAt: 2023-05-03T14:22:00.584Z
+updatedAt: 2024-04-01T17:40:33.284Z
+publishedAt: 2024-04-01T17:40:33.284Z
 firstPublishedAt: 2017-04-27T23:00:47.264Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -40,6 +40,7 @@ Antes de realizar as alterações no pedido, fique atento às restrições da fu
 * É preciso que o [adquirente](https://help.vtex.com/pt/tutorial/o-que-e-um-adquirente--7N1oRTG8dGmOiIugC0cs4E) aceite o novo valor da operação para que a alteração ocorra.
 * O acréscimo de valores só é permitido se pedido foi pago por [Promissória de Crédito](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ), [dinheiro](https://help.vtex.com/pt/tutorial/como-configurar-pagamento-customizado--tutorials_451) ou [controle de crédito](https://help.vtex.com/pt/tutorial/customer-credit-visao-geral--1uIqTjWxIIIEW0COMg4uE0). Além disso, o [adquirente ](https://help.vtex.com/pt/tutorial/o-que-e-um-adquirente--7N1oRTG8dGmOiIugC0cs4E)deve permitir a operação sem o uso de CVV e duas operações de cobrança em um mesmo pedido.
 * A [reserva](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92)dos itens no inventário não é automática. É preciso atualizar manualmente a quantidade de itens que ainda estão disponíveis no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+* Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível alterar o pedido.
 * Não é possível alterar um pedido com a transação finalizada. Para alterações no valor do pedido com desconto, por exemplo, o OMS leva em considera que ainda é possível alterar o valor da transação se o status mostrado em Detalhes da transação é diferente de `Finished`, mesmo se o valor já tenha sido liquidado.  
 * Não é possível fazer alterações em pedidos vindos de [marketplaces integrados com a VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) (tanto conectores nativos ou conectores de parceiros).
 * É possível alterar apenas pedidos que foram para manuseio, no status *Preparando entrega*.
diff --git a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
index 2f908bcb0..85327ff55 100644
--- a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
@@ -28,12 +28,12 @@ Para fazer a alteração, siga os passos abaixo:
 3. Clique no pedido para acessar a página de **Detalhes do pedido**.   
 4. Vá à seção **Valor total do pedido**, localizada no lado direito da página Detalhes do pedido.
 5. Clique em `Alterar valor final`. A página **Alterar valor** ficará disponível
-![valorfinal](https://images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/9165c911db34e8067f90734077f67080/valorfinal__2_.png)
+![valorfinal](//images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/9165c911db34e8067f90734077f67080/valorfinal__2_.png)
 6. Preencha os campos obrigatórios: 
     *  **Valor:** Selecione entre Desconto e Aumento, e insira o valor correspondente ao que deseja alterar.  
     * **Motivo:** escreva as razões para a mudança.  
 7. Clique em `Enviar`.
-![Alterar valor](https://images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/5bd41102367f310c7c5e70626496d8cb/Alterar_valor__1_.png)
+![Alterar valor](//images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/5bd41102367f310c7c5e70626496d8cb/Alterar_valor__1_.png)
 
 As alterações no pedido serão atualizadas na seção *Itens para Faturar, e Histórico do pedido*. Note que o valor total do pedido também será alterado.
 
diff --git a/docs/tutorials/pt/changing-tracking-data.md b/docs/tutorials/pt/changing-tracking-data.md
index 4722a024a..b4320f9eb 100644
--- a/docs/tutorials/pt/changing-tracking-data.md
+++ b/docs/tutorials/pt/changing-tracking-data.md
@@ -38,4 +38,4 @@ Para alterar os dados de um pedido manualmente, siga os passos abaixo:
     * **Selecionar transportadora:** selecione qual transportadora realizará a entrega.
 7. Clique em `Salvar`.
 
-![Fatura](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
+![Fatura](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
diff --git a/docs/tutorials/pt/chat.md b/docs/tutorials/pt/chat.md
index f68c923a5..322eb1e3a 100644
--- a/docs/tutorials/pt/chat.md
+++ b/docs/tutorials/pt/chat.md
@@ -25,46 +25,46 @@ Para começar você [deve ter criado os links](https://help.vtex.com/pt/tutoria
 
 Acesse “_**Atrair**_” > “_**Chat**_”  
 
-![Chat 1](https://images.ctfassets.net/alneenqid6w5/7QkjjcJQEBynDhVtqSQHi/4a33ad632ba4d0c0913d2778e852cd6d/Screenshot_2022-08-29_at_17-02-02_Chat.png)
+![Chat 1](//images.ctfassets.net/alneenqid6w5/7QkjjcJQEBynDhVtqSQHi/4a33ad632ba4d0c0913d2778e852cd6d/Screenshot_2022-08-29_at_17-02-02_Chat.png)
 
 Clique em “_**Novo**_”
 
-![Chat  2](https://images.ctfassets.net/alneenqid6w5/3i0wj6QgqLwd1mqpIrN9Cj/e1951a2c9a93477b4c96f1b4afee0cc3/Screenshot_2022-08-29_at_17-02-07_Chat.png)
+![Chat  2](//images.ctfassets.net/alneenqid6w5/3i0wj6QgqLwd1mqpIrN9Cj/e1951a2c9a93477b4c96f1b4afee0cc3/Screenshot_2022-08-29_at_17-02-07_Chat.png)
 
 Selecione qual será o **_link_** do seu chat :
 
-![Chat 3](https://images.ctfassets.net/alneenqid6w5/5lcQyorVcU4ZFXsKJlerd5/7bb744985853675460e4775b1019d4d8/Screenshot_2022-08-29_at_17-02-12_Chat.png)
+![Chat 3](//images.ctfassets.net/alneenqid6w5/5lcQyorVcU4ZFXsKJlerd5/7bb744985853675460e4775b1019d4d8/Screenshot_2022-08-29_at_17-02-12_Chat.png)
 
 **Lembre-se**: Ele pode ser uma _**Captura**_ ou um _**Seletivo**_.
 
 Defina o _Layout_: 
 
-![Chat 4](https://images.ctfassets.net/alneenqid6w5/45MgsdFohomYzP2atFignF/0bfab8a649f076cead3547d17957890d/Screenshot_2022-08-29_at_17-02-19_Chat.png)
+![Chat 4](//images.ctfassets.net/alneenqid6w5/45MgsdFohomYzP2atFignF/0bfab8a649f076cead3547d17957890d/Screenshot_2022-08-29_at_17-02-19_Chat.png)
 
 Você pode escolher as cores, mensagens e ir visualizando todas as alterações simultaneamente.
 
-![Chat 5](https://images.ctfassets.net/alneenqid6w5/6v1BUpIM5UsdYmDisRjrLF/043369a7399ffd66dc76a97a088e570b/Screenshot_2022-08-29_at_17-02-28_Chat.png)
+![Chat 5](//images.ctfassets.net/alneenqid6w5/6v1BUpIM5UsdYmDisRjrLF/043369a7399ffd66dc76a97a088e570b/Screenshot_2022-08-29_at_17-02-28_Chat.png)
 
 Você também pode configurar o CTAs do seu chat, ou seja, definir quando ele vai abrir automaticamente para o seu cliente. 
 
-![Chat 6](https://images.ctfassets.net/alneenqid6w5/fBbGQGQ0idJ21232uW63u/dc35acc6cac9ee80a7ba1d6d36552d50/Screenshot_2022-08-29_at_17-02-34_Chat.png)
+![Chat 6](//images.ctfassets.net/alneenqid6w5/fBbGQGQ0idJ21232uW63u/dc35acc6cac9ee80a7ba1d6d36552d50/Screenshot_2022-08-29_at_17-02-34_Chat.png)
 
 Veja um exemplo de “_Houver uma intenção de sair da página_” 
 
-![Chat 7](https://images.ctfassets.net/alneenqid6w5/4mhPnDPQXDhbBAGXb3mVyw/be5f484fcca61f4b2f9553e51bd9e4a6/Screenshot_2022-08-29_at_17-02-42_Chat.png)
+![Chat 7](//images.ctfassets.net/alneenqid6w5/4mhPnDPQXDhbBAGXb3mVyw/be5f484fcca61f4b2f9553e51bd9e4a6/Screenshot_2022-08-29_at_17-02-42_Chat.png)
 
 Defina onde mostrar o chat no seu site ou quando ele não irá aparecer: 
 
-![Chat 8](https://images.ctfassets.net/alneenqid6w5/2dodZaa9eN1w5OszTVRgxp/88cc53edda282f4c0954aaae18dc9915/Screenshot_2022-08-29_at_17-02-49_Chat.png)
+![Chat 8](//images.ctfassets.net/alneenqid6w5/2dodZaa9eN1w5OszTVRgxp/88cc53edda282f4c0954aaae18dc9915/Screenshot_2022-08-29_at_17-02-49_Chat.png)
 
 Depois de definir o layout e os gatilhos, clique em “**_Salvar_**”
 
 Para inserir o chat no seu site, acesse na aba “**_Chat_**” e clique no seletor e clique em “_**instruções de instalação**_” :
 
-![Chat 9](https://images.ctfassets.net/alneenqid6w5/6AOJ9KqJxYgGtIG8b856Bu/81d1968ccebbfb72e35193a4a12150b4/Screenshot_2022-08-29_at_17-02-57_Chat.png)
+![Chat 9](//images.ctfassets.net/alneenqid6w5/6AOJ9KqJxYgGtIG8b856Bu/81d1968ccebbfb72e35193a4a12150b4/Screenshot_2022-08-29_at_17-02-57_Chat.png)
 
 Basta copiar e colar o código fornecido no “**_Body_**” do painel administrativo do seu site:
 
-![Chat 10](https://images.ctfassets.net/alneenqid6w5/5VggBGuNNuPxGkNS6RtMQR/4b3b14a171a47d9aad8cf73cff31faac/Screenshot_2022-08-29_at_17-03-03_Chat.png)
+![Chat 10](//images.ctfassets.net/alneenqid6w5/5VggBGuNNuPxGkNS6RtMQR/4b3b14a171a47d9aad8cf73cff31faac/Screenshot_2022-08-29_at_17-03-03_Chat.png)
 
 E pronto, qualquer alteração feita no Chat dentro do painel da Suiteshare, já será alterado automaticamente no chat do seu site.
diff --git a/docs/tutorials/pt/check-order-delivery-details.md b/docs/tutorials/pt/check-order-delivery-details.md
index 86515f2c3..0f39f547f 100644
--- a/docs/tutorials/pt/check-order-delivery-details.md
+++ b/docs/tutorials/pt/check-order-delivery-details.md
@@ -45,7 +45,7 @@ Para ver esses detalhes, basta fazer uma [simulação de frete](/pt/tutorial/sim
 6. Informe o CEP do pedido.
 7. Clique em __Simular frete__.
 
-![simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/6TPVNOKh1uKmmMGGQAoeY2/e437d4fcd8f91d28f05813f936d30f4a/simular-frete-pt.png)
+![simular-frete-pt](//images.ctfassets.net/alneenqid6w5/6TPVNOKh1uKmmMGGQAoeY2/e437d4fcd8f91d28f05813f936d30f4a/simular-frete-pt.png)
 
 Para cada transportadora considerada na simulação, você pode ver os detalhes do pedido correspondente. Para isso, clique em __detalhar__.
 
diff --git a/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md b/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md
index a996691d8..7a6ecb4a4 100644
--- a/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md
+++ b/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md
@@ -23,7 +23,7 @@ Digamos que você deseja saber quais foram os critérios que a plataforma usou p
 
 Em primeiro lugar, vamos entrar no módulo __Todos os pedidos__ para ver o pedido.
 
-![2019-06-05 13 51 56-Todos os pedidos](https://images.ctfassets.net/alneenqid6w5/1v711UNCK6lLyGvqXkDkRs/046e6d1af8cb038a15bf1674ea86081c/2019-06-05_13_51_56-Todos_os_pedidos.png) 
+![2019-06-05 13 51 56-Todos os pedidos](//images.ctfassets.net/alneenqid6w5/1v711UNCK6lLyGvqXkDkRs/046e6d1af8cb038a15bf1674ea86081c/2019-06-05_13_51_56-Todos_os_pedidos.png) 
 
 >No canto superior direito, você vê a __data em que o pedido foi realizado__ (6 MAI 2019).
 >E na seção de Itens a Faturar em baixo, você vê o __prazo de entrega do pedido__ (22 MAI 2019).
@@ -33,25 +33,25 @@ Agora vamos entrar no módulo __Envio__ e simular o frete desse pedido.
 Para isso, siga os passos abaixo:
 
 1. No Admin VTEX, acesse **Envio > Simulação de Envio**, ou digite *Simulação de Envio* na barra de busca no topo da página.  
-2. Insira o nome ou o ID de cada SKU que estava no carrinho do pedido que você deseja investigar, incluindo a quantidade de cada um deles.![2019-06-05 14 07 20-Simulador de envio](https://images.ctfassets.net/alneenqid6w5/2AAUbA9NuAlLWW6tW2eFo8/8499c3f8f6185c2f1f8568fbada87d4e/2019-06-05_14_07_20-Simulador_de_envio.png)
+2. Insira o nome ou o ID de cada SKU que estava no carrinho do pedido que você deseja investigar, incluindo a quantidade de cada um deles.![2019-06-05 14 07 20-Simulador de envio](//images.ctfassets.net/alneenqid6w5/2AAUbA9NuAlLWW6tW2eFo8/8499c3f8f6185c2f1f8568fbada87d4e/2019-06-05_14_07_20-Simulador_de_envio.png)
 3. Insira o CEP do pedido.
 4. Clique em __Simular frete__.
 
 No exemplo abaixo, note que 4 transportadoras foram consideradas, e 12 foram desconsideradas.
 
-![2](https://images.ctfassets.net/alneenqid6w5/GFpG6fdmrpIubx6AClQIx/34d23cc1b849becdf34d0c10ed4d0c54/2.png)
+![2](//images.ctfassets.net/alneenqid6w5/GFpG6fdmrpIubx6AClQIx/34d23cc1b849becdf34d0c10ed4d0c54/2.png)
 
 Consultando mais uma vez a tela de detalhes do pedido, vemos que o tipo de entrega escolhido pelo cliente para esse pedido foi o __Expressa__, e que a transportadora escolhida pela plataforma para realizar esse pedido foi a __Expressa & CO__.
 
-![3](https://images.ctfassets.net/alneenqid6w5/5cfMvMBQJ2PH6MSXEPWC8E/42e5889646c37d4ee1595866e3a797f3/3.png)
+![3](//images.ctfassets.net/alneenqid6w5/5cfMvMBQJ2PH6MSXEPWC8E/42e5889646c37d4ee1595866e3a797f3/3.png)
 
 Portanto, voltando à simulação de frete, no módulo Envio, concluímos que a primeira opção foi a escolhida nesse pedido - e que, portanto, o prazo de entrega total do pedido foi de 12 dias.
 
-![4](https://images.ctfassets.net/alneenqid6w5/51uwhtB3nSKyMtXY2zVbic/a7d28ccb49dd18b1bb60d6e8d9bff73c/4.png)
+![4](//images.ctfassets.net/alneenqid6w5/51uwhtB3nSKyMtXY2zVbic/a7d28ccb49dd18b1bb60d6e8d9bff73c/4.png)
 
 Agora basta clicar em __detalhar__ para ver os tempos de custo que foram usados no cálculo desse prazo de entrega.
 
-![5](https://images.ctfassets.net/alneenqid6w5/3USKpGaWgl6qHuYqE7iqrY/6158faed327f8bafc30fee04e464f16c/5.png)
+![5](//images.ctfassets.net/alneenqid6w5/3USKpGaWgl6qHuYqE7iqrY/6158faed327f8bafc30fee04e464f16c/5.png)
 
 Cada um dos três tempos de custo corresponde ao que foi definido para as três etapas da rota de logística: estoque, doca e transportadora.
 
diff --git a/docs/tutorials/pt/checkout-vtex-overview.md b/docs/tutorials/pt/checkout-vtex-overview.md
index 87889095d..406a90f3a 100644
--- a/docs/tutorials/pt/checkout-vtex-overview.md
+++ b/docs/tutorials/pt/checkout-vtex-overview.md
@@ -35,7 +35,7 @@ Os passos abaixo demonstram a experiência de compra de um cliente e o papel do
 
 Sempre que o cliente realiza uma modificação no carrinho (adição ou remoção de itens), ou que a tela do Checkout é atualizada, a seguinte cadeia de processos internos no Checkout é executada.
 
-![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/c25d968b81626de55ab890ef67834bb8/Checkout_Overview_PT.png)
+![Checkout overview](//images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/c25d968b81626de55ab890ef67834bb8/Checkout_Overview_PT.png)
 
 <div class="alert alert-info">
 Caso um ou mais itens escolhidos pelo cliente sejam elegíveis para entrega por um <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#o-que-e-um-seller-white-label">Seller white label</a>, serão realizadas simulações (conforme exibido no lado direito da figura), de modo a determinar quais sellers serão responsáveis pela entrega dos itens. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Seleção de sellers white label</a>.
diff --git a/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md b/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
index 6beb15212..9671c4537 100644
--- a/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
+++ b/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
@@ -3,8 +3,8 @@ title: 'Escolhendo entre arquitetura multi-loja ou ambiente adicional'
 id: 4HRNpa1OCKZ5YzP8yiilBL
 status: PUBLISHED
 createdAt: 2023-05-25T16:33:11.450Z
-updatedAt: 2023-05-25T19:39:40.359Z
-publishedAt: 2023-05-25T19:39:40.359Z
+updatedAt: 2023-10-02T16:57:08.371Z
+publishedAt: 2023-10-02T16:57:08.371Z
 firstPublishedAt: 2023-05-25T19:35:27.925Z
 contentType: tutorial
 productTeam: Management
@@ -35,25 +35,25 @@ Para arquiteturas de marketplace, também é possível <a href="https://help.vte
 
 A tabela abaixo apresenta como as diferentes arquiteturas se relacionam com módulos e funcionalidades da plataforma VTEX.
 
-| Aspecto                           | Arquitetura multi-loja (store)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Arquitetura de ambientes adicionais                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Arquitetura                       | Um único Admin VTEX ([account](https://help.vtex.com/pt/tutorial/o-que-e-account-name)), com múltiplas sub-contas ([stores](https://help.vtex.com/pt/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Dois ambientes ([accounts](https://help.vtex.com/pt/tutorial/o-que-e-account-name)) separados do Admin VTEX.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| Segmentação de condições de venda | É possível segmentar as aplicações de catálogo, preços, pagamentos, promoções, entre outros módulos, usando [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) e [bindings](https://help.vtex.com/pt/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W).                                                                                                                                                                                                                                                                                                                                                                                                         | Pelo fato de serem dois ambientes separados, com configurações independentes, o lojista tem muito mais controle sobre as possibilidades de segmentação de condições de venda em diferentes cenários.                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| Tipo de equipe                    | Recomendado quando uma mesma empresa e mesma equipe gerencia dois ou mais ecommerces com catálogos similares e itens em comum, mas que desejam oferecer storefronts diferentes para seus compradores acessarem experiências com marcas diferentes.                                                                                                                                                                                                                                                                                                   | Recomendado quando equipes distintas da mesma empresa lidam com ecommerces diferentes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| Storefront                        | Storefronts são diferentes para cada store, mas gerenciado por um mesmo Admin VTEX.Caso a intenção seja somente mudar o idioma do site, mas a operação da loja for a mesma, é possível utilizar o [multibinding](https://help.vtex.com/pt/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) e [internacionalização do catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization) para configuração em um mesmo ambiente VTEX.<br>Note que essa arquitetura é diferente de uma [conta-franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), pois essa conta não possui um site próprio. Os consumidores navegam diretamente no site da conta principal, que atua como marketplace nessa situação.                                  | Cada account gerencia seus próprios storefronts em Admins VTEX separados, podendo utilizar todas as opções disponíveis de segmentação de storefronts.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| Performance do Admin VTEX         | A performance do Admin VTEX pode ser afetada quanto mais [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) forem associadas a uma mesma conta principal, ficando mais lento o uso das funcionalidades na plataforma, uma vez que a informação precisa ser atualizada em cada política comercial. <br>Impactos na performance do Admin também são esperadas se o catálogo de produtos for muito extenso, com mais de 2 milhões de produtos, aumentando o tempo de indexação.                                                                                                       | É possível criar múltiplas [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV), separadas para cada ambiente.<br>A performance do Admin VTEX pode ser afetada quanto mais políticas comerciais forem associadas a uma mesma conta principal, ficando mais lento o uso de certas funcionalidades na plataforma.<br>Porém, dado que são ambientes separados, a necessidade de cadastrar múltiplas políticas comerciais diminui.                                                                                                                                                                                                                                                                                                                                                      |
-| Custos                            | Apesar da adição de uma store não ter custo adicional, é necessário [contratar uma política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), caso deseje diferenciar o storefront dos sites. Saiba mais sobre políticas comerciais e segmentação das configurações disponíveis em [Como funciona uma política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?).                                                                                                                                                                                                                                                           | É necessário [contratar um ambiente adicional](https://help.vtex.com/pt/tutorial/contratar-novo-ambiente--tutorials_2542?&utm_source=autocomplete) com custo adicional previsto no contrato com a VTEX. <br>Caso deseje, também é possível [contratar uma política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), caso deseje segmentar as configurações de cada ambiente para condições diferentes. Saiba mais sobre políticas comerciais e segmentação das configurações disponíveis em [Como funciona uma política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?).                                                                                                                                                                                                                                                                                                                                                                |
-| Operação                          | Ao utilizar esse tipo de arquitetura, avalie a complexidade de gestão de catálogo, promoções, preços, estoque, pedidos e pagamentos pensando em diferentes stores, uma vez que todos os dados estarão no mesmo Admin. É possível configurar [internacionalização do catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization), para a venda em países diferentes.                                                                                                                                                                                                                                      | Recomendamos essa arquitetura em casos de operações em dois países distintos, quando há necessidade de separação de idiomas diretamente no catálogo, para facilitar a operação de equipes que se comunicam em idiomas diferentes também.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| Master Data                       | À medida que é criada uma subaccount, o [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) é criado de forma separada por default, ou seja, cada conta tem o seu. Contudo é possível unificá-los, solicitando via [ticket para o nosso time de Suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).                                                                                                                                                                                                                                                                                                                                      |  Cada account terá seu [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) independente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| Segurança da informação           | Todos os módulos são compartilhados entre as stores, como catálogo, promoções, preços, configurações de pagamento, etc. <br>É importante levar esse ponto em consideração ao lidar com diferentes times de uma mesma empresa tendo acesso ao Admin VTEX. Por exemplo, funcionários da Marca B poderão visualizar catálogo, preços e pedidos da Marca A - sendo Marca A e Marca B duas stores separadas.                                                                                                                                              | A separação de ambientes faz com que os dados e configurações de catálogo, promoções, preços, configurações de pagamento, entre outros módulos, não sejam acessados por funcionários de times diferentes.<br>Por exemplo, funcionários da Marca B não poderão visualizar catálogo, preços e pedidos da Marca A  - sendo Marca A e Marca B ambientes VTEX separados.                                                                                                                                                                                                                                                                                                                                                                                 |
-| License Manager                   | O mesmo [License Manager](https://help.vtex.com/pt/tutorial/visao-geral-do-modulo-license-manager) gerencia todos os usuários.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Cada Admin terá o seu próprio [License Manager](https://help.vtex.com/pt/tutorial/visao-geral-do-modulo-license-manager), com gerenciamento de usuários separados.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| Giftcard                          | As subaccounts terão acesso ao mesmo gerenciamento de giftcards, sendo possível usar os giftcards em storefronts diferentes.                                                                                                                                                                                                                                                                                                                                                                                                                         | Cada Admin terá o seu gerenciamento de Giftcard único, não sendo possível usar o giftcard gerado em um ambiente, no outro ambiente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| Estrutura de marketplace          | Uma estrutura de marketplace não se aplica entre as stores diferentes, uma vez que que já compartilham catálogo, preços e estoque. <br>                                                                                                                                                                                                                                                                                                                                                                                                              | É possível que um ambiente seja seller no outro ambiente e vice e versa, tendo os produtos sendo vendidos nos dois sites baseados na relação seller-marketplace. Saiba mais em [Configurar marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) e [Configurar seller para vender em marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP). <br>Também é possível criar contas-franquia, para que operem como sellers white label, já que possuem preços, estoques e logística diferentes. Saiba mais em [Escolher entre Conta Franquia, Seller Portal ou Conta Padrão](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).<br>Isso pode ser feito contratando ambiente adicional (caso tenham itens no catálogo em comum, mas não todos) ou conta-franquia (em casos de catálogos exatamente iguais). Saiba mais em Escolher entre Conta Franquia, Seller Portal ou Conta Padrão.   |
-| Sitemap                           | Haverá um [sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) único para a account principal, que será compartilhado entre as stores.                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Cada account possui seu [sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) independente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| B2B: Catálogo                     | Não é possível mudar a unidade de medida registrada no catálogo para cada [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#catalogo). Ex: lojas B2B vendem em atacado, enquanto B2Cs vendem por pequenas quantidades. <br>O storefront B2B com catálogo centralizado terá a página de produto com uma unidade apenas. Dependendo do negócio, será preciso customizar o storefront para permitir um mínimo de unidades daquele SKU. <br>É possível ampliar o catálogo com a criação de kits, mas seriam kits criados para a maioria dos produtos, gerando um catálogo praticamente duplicado. | Como os catálogos de cada ambiente são independentes, as restrições presentes no ambiente multi-loja não se aplicam.É possível adaptar um dos catálogos somente para vendas B2B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| B2B: configurações do orderForm   | Ao seguir por uma arquitetura multiloja, todas as stores compartilharão o mesmo [orderform configuration](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm), no Checkout.<br>Existem sistemas que podem ser integrados ao Admin da VTEX e dependem deste tipo de configuração para realizar a integração, como é o caso de Tax Providers por exemplo.<br>Na prática, na integração de um Tax provider, ele será chamado tanto no B2C quanto no B2B em um ambiente multiloja, o que é danoso para a operação do cliente.                                                                                  | É possível criar uma configuração distinta do [orderform](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) para cada ambiente, suprindo as necessidades de integrações externas no checkout de uma loja B2B.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| Aspecto | Arquitetura multi-loja (store) | Arquitetura de ambientes adicionais |
+| - | - | - |
+| Arquitetura | Um único Admin VTEX ([account](https://help.vtex.com/pt/tutorial/o-que-e-account-name)), com múltiplas sub-contas ([stores](https://help.vtex.com/pt/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK)). | Dois ambientes ([accounts](https://help.vtex.com/pt/tutorial/o-que-e-account-name)) separados do Admin VTEX. |
+| Segmentação de condições de venda | É possível segmentar as aplicações de catálogo, preços, pagamentos, promoções, entre outros módulos, usando [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) e [bindings](https://help.vtex.com/pt/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W). | Pelo fato de serem dois ambientes separados, com configurações independentes, o lojista tem muito mais controle sobre as possibilidades de segmentação de condições de venda em diferentes cenários. |
+| Tipo de equipe | Recomendado quando uma mesma empresa e mesma equipe gerencia dois ou mais ecommerces com catálogos similares e itens em comum, mas que desejam oferecer storefronts diferentes para seus compradores acessarem experiências com marcas diferentes. | Recomendado quando equipes distintas da mesma empresa lidam com ecommerces diferentes. |
+| Storefront | Storefronts são diferentes para cada store, mas gerenciado por um mesmo Admin VTEX.Caso a intenção seja somente mudar o idioma do site, mas a operação da loja for a mesma, é possível utilizar o [multibinding](https://help.vtex.com/pt/tutorial/gerenciando-conteudo-por-binding--5CZjZPMqi0ZNpuqzF6AUOn) e [internacionalização do catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization) para configuração em um mesmo ambiente VTEX.<br>Note que essa arquitetura é diferente de uma [conta-franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), pois essa conta não possui um site próprio. Os consumidores navegam diretamente no site da conta principal, que atua como marketplace nessa situação.               | Cada account gerencia seus próprios storefronts em Admins VTEX separados, podendo utilizar todas as opções disponíveis de segmentação de storefronts. |
+| Performance do Admin VTEX | A performance do Admin VTEX pode ser afetada quanto mais [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) forem associadas a uma mesma conta principal, ficando mais lento o uso das funcionalidades na plataforma, uma vez que a informação precisa ser atualizada em cada política comercial. <br>Impactos na performance do Admin também são esperadas se o catálogo de produtos for muito extenso, com mais de 2 milhões de produtos, aumentando o tempo de indexação. | É possível criar múltiplas [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV), separadas para cada ambiente.<br>A performance do Admin VTEX pode ser afetada quanto mais políticas comerciais forem associadas a uma mesma conta principal, ficando mais lento o uso de certas funcionalidades na plataforma.<br>Porém, dado que são ambientes separados, a necessidade de cadastrar múltiplas políticas comerciais diminui. |
+| Custos | Apesar da adição de uma store não ter custo adicional, é necessário [contratar uma política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), caso deseje diferenciar o storefront dos sites. Saiba mais sobre políticas comerciais e segmentação das configurações disponíveis em [Como funciona uma política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?). | É necessário [contratar um ambiente adicional](https://help.vtex.com/pt/tutorial/contratar-novo-ambiente--tutorials_2542?&utm_source=autocomplete) com custo adicional previsto no contrato com a VTEX. <br>Caso deseje, também é possível [contratar uma política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), caso deseje segmentar as configurações de cada ambiente para condições diferentes. Saiba mais sobre políticas comerciais e segmentação das configurações disponíveis em [Como funciona uma política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?). |
+| Operação | Ao utilizar esse tipo de arquitetura, avalie a complexidade de gestão de catálogo, promoções, preços, estoque, pedidos e pagamentos pensando em diferentes stores, uma vez que todos os dados estarão no mesmo Admin. É possível configurar [internacionalização do catálogo](https://developers.vtex.com/docs/guides/catalog-internationalization), para a venda em países diferentes. | Recomendamos essa arquitetura em casos de operações em dois países distintos, quando há necessidade de separação de idiomas diretamente no catálogo, para facilitar a operação de equipes que se comunicam em idiomas diferentes também. |
+| Master Data | Quando uma subconta é criada, o [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) é criado de forma separada por padrão, ou seja, cada conta tem o seu próprio Master Data. É possível replicar os dados de uma conta para a outra para popular as entidades padrão (CL, AD e OD), solicitando via [ticket para o nosso time de Suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). No entanto, entidades customizadas existem apenas na conta em que foram criadas e não podem ser replicadas para outras contas. |  Cada conta terá seu [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) independente. |
+| Segurança da informação | Todos os módulos são compartilhados entre as stores, como catálogo, promoções, preços, configurações de pagamento, etc. <br>É importante levar esse ponto em consideração ao lidar com diferentes times de uma mesma empresa tendo acesso ao Admin VTEX. Por exemplo, funcionários da Marca B poderão visualizar catálogo, preços e pedidos da Marca A - sendo Marca A e Marca B duas stores separadas. | A separação de ambientes faz com que os dados e configurações de catálogo, promoções, preços, configurações de pagamento, entre outros módulos, não sejam acessados por funcionários de times diferentes.<br>Por exemplo, funcionários da Marca B não poderão visualizar catálogo, preços e pedidos da Marca A  - sendo Marca A e Marca B ambientes VTEX separados.      |
+| License Manager | O mesmo [License Manager](https://help.vtex.com/pt/tutorial/visao-geral-do-modulo-license-manager) gerencia todos os usuários. | Cada Admin terá o seu próprio [License Manager](https://help.vtex.com/pt/tutorial/visao-geral-do-modulo-license-manager), com gerenciamento de usuários separados.    |
+| Giftcard | As subaccounts terão acesso ao mesmo gerenciamento de giftcards, sendo possível usar os giftcards em storefronts diferentes. | Cada Admin terá o seu gerenciamento de Giftcard único, não sendo possível usar o giftcard gerado em um ambiente, no outro ambiente. |
+| Estrutura de marketplace | Uma estrutura de marketplace não se aplica entre as stores diferentes, uma vez que que já compartilham catálogo, preços e estoque. | É possível que um ambiente seja seller no outro ambiente e vice e versa, tendo os produtos sendo vendidos nos dois sites baseados na relação seller-marketplace. Saiba mais em [Configurar marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) e [Configurar seller para vender em marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP). <br>Também é possível criar contas-franquia, para que operem como sellers white label, já que possuem preços, estoques e logística diferentes. Saiba mais em [Escolher entre Conta Franquia, Seller Portal ou Conta Padrão](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).<br>Isso pode ser feito contratando ambiente adicional (caso tenham itens no catálogo em comum, mas não todos) ou conta-franquia (em casos de catálogos exatamente iguais). Saiba mais em Escolher entre Conta Franquia, Seller Portal ou Conta Padrão. |
+| Sitemap | Haverá um [sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) único para a account principal, que será compartilhado entre as stores. | Cada account possui seu [sitemap](https://help.vtex.com/pt/tutorial/rastreamento-google-search-console-sitemap--tutorials_575) independente. |
+| B2B: Catálogo  | Não é possível mudar a unidade de medida registrada no catálogo para cada [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV#catalogo). Ex: lojas B2B vendem em atacado, enquanto B2Cs vendem por pequenas quantidades. <br>O storefront B2B com catálogo centralizado terá a página de produto com uma unidade apenas. Dependendo do negócio, será preciso customizar o storefront para permitir um mínimo de unidades daquele SKU. <br>É possível ampliar o catálogo com a criação de kits, mas seriam kits criados para a maioria dos produtos, gerando um catálogo praticamente duplicado. | Como os catálogos de cada ambiente são independentes, as restrições presentes no ambiente multi-loja não se aplicam.É possível adaptar um dos catálogos somente para vendas B2B. |
+| B2B: configurações do orderForm   | Ao seguir por uma arquitetura multiloja, todas as stores compartilharão o mesmo [orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm), no Checkout.<br>Existem sistemas que podem ser integrados ao Admin da VTEX e dependem deste tipo de configuração para realizar a integração, como é o caso de Tax Providers por exemplo.<br>Na prática, na integração de um Tax provider, ele será chamado tanto no B2C quanto no B2B em um ambiente multiloja, o que é danoso para a operação do cliente. | É possível criar uma configuração distinta do [orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#get-/api/checkout/pvt/configuration/orderForm) para cada ambiente, suprindo as necessidades de integrações externas no checkout de uma loja B2B. |
 
 ## Saiba mais
 
 - [Configurar marketplace para multiloja](https://help.vtex.com/pt/tutorial/como-configurar-bridge-para-multiloja--frequentlyAskedQuestions_672)    
-- [Criar multiloja / multidomínio](https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510)  
+- [Criar multiloja / multidomínio](https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510)
diff --git a/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
index 952bd19e1..e120fb9b0 100644
--- a/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -3,8 +3,8 @@ title: 'Escolher entre conta padrão, conta franquia ou Seller Portal'
 id: 4S90HzzhMyZESsHqrnUs78
 status: PUBLISHED
 createdAt: 2022-04-20T14:15:50.164Z
-updatedAt: 2022-06-22T21:39:18.954Z
-publishedAt: 2022-06-22T21:39:18.954Z
+updatedAt: 2023-11-22T14:09:05.122Z
+publishedAt: 2023-11-22T14:09:05.122Z
 firstPublishedAt: 2022-04-27T21:42:35.010Z
 contentType: tutorial
 productTeam: Channels
@@ -23,6 +23,8 @@ Na VTEX, existem três tipos de conta e cada uma permite atuar com um perfil de
 - **Conta franquia:** é criada associada a uma conta padrão, de quem ela herda o [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR), ou seja, categorias, produtos e especificações são importados para o ambiente da [conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), que não cria produtos próprios. No entanto, ela pode configurar logística, pagamento e preços próprios. A conta franquia dispõe parcialmente dos módulos da plataforma VTEX e atua como [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) da conta padrão.
 - **Seller Portal:** o [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é uma edição da plataforma VTEX que permite a sellers se conectarem e venderem produtos em marketplaces do ecossistema VTEX, independente do seller já ter ou não uma conta na VTEX. O Seller Portal permite acesso parcial aos módulos da plataforma e o seller pode ser do tipo normal ou [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 
+  <div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+
 A tabela a seguir apresenta os principais cenários de uso de cada tipo de conta:
 
 | **Seller Portal** | **Conta padrão** | **Conta franquia** |
@@ -61,7 +63,7 @@ A seguir, há uma série de comparativos de como Seller Portal, conta padrão e
 | **Aspecto** | **Seller Portal** | **Conta padrão** | **Conta franquia** |
 | ---------- | ---------- | ---------- | ---------- |
 | Herdar preço de outra conta | Quando o marketplace VTEX [convida](https://help.vtex.com/pt/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A) o seller para o Seller Portal escolhendo a opção [Seller White Label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa), os produtos do seller herdam os preços do marketplace. No entanto, o seller pode editar os preços. | A conta padrão não herda preços de outra conta, é necessário cadastrá-los no seu próprio ambiente. | A conta franquia pode herdar preços da conta principal. |
-| Marketplace VTEX poder sobrescrever preço do seller | Não, o marketplace VTEX pode apenas definir regras comerciais para o seller. | Sim. | Não, o marketplace VTEX pode apenas definir regras comerciais para a conta franquia. |
+| Marketplace VTEX poder sobrescrever preço do seller | Quando o seller criado via convite for um seller comum, o preço deste pode ser sobrescrito, mas se for Seller white label, o preço não pode ser sobrescrito. | Sim. | Não, o marketplace VTEX pode apenas definir regras comerciais para a conta franquia. |
 | Dispor de [Manual Pricing](https://help.vtex.com/pt/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS#inserir-preco-manual) | Sim. | Sim. | Sim. |
 
 ## Promoções
diff --git a/docs/tutorials/pt/cms-overview.md b/docs/tutorials/pt/cms-overview.md
index ebeac6ca6..bf51bc099 100644
--- a/docs/tutorials/pt/cms-overview.md
+++ b/docs/tutorials/pt/cms-overview.md
@@ -1,10 +1,10 @@
 ---
 title: 'CMS - Visão Geral'
 id: 2X1xWJi9WmtNylxmggn3ts
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-29T18:36:32.910Z
-updatedAt: 2023-03-29T19:34:13.250Z
-publishedAt: 2023-03-29T19:34:13.250Z
+updatedAt: 2023-07-18T18:36:27.273Z
+publishedAt: 
 firstPublishedAt: 2023-03-29T18:38:26.442Z
 contentType: tutorial
 productTeam: Others
@@ -15,7 +15,7 @@ legacySlug: cms-visao-geral
 subcategory: 3PNmhq67KMmGTBSfIWJdcQ
 ---
 
-![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System) é uma funcionalidade voltada para o gerenciamento de conteúdo de forma prática e constante.
 
diff --git a/docs/tutorials/pt/cms-store-overview.md b/docs/tutorials/pt/cms-store-overview.md
index 7dd0db1af..3aa5eff31 100644
--- a/docs/tutorials/pt/cms-store-overview.md
+++ b/docs/tutorials/pt/cms-store-overview.md
@@ -19,7 +19,7 @@ A página **Loja** permite que você realize configurações de SEO, habilite fl
 
 No Admin VTEX, acesse **Configurações da loja > Storefront > Loja*** e descubra as principais ferramentas disponíveis na interface.
 
-![CMS Loja](https://images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/40e653a93a4543bff834816c38ec018b/store-pt-overview.png)
+![CMS Loja](//images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/40e653a93a4543bff834816c38ec018b/store-pt-overview.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Antes de fazer alterações na aba <b>Avançado</b>, entre em contato com a sua equipe de desenvolvedores e consulte a nossa <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-best-practices-for-optimizing-performance#enabling-store-settings">documentação sobre a otimização de desempenho</a> para mais informações.
diff --git a/docs/tutorials/pt/collection-highlight-control.md b/docs/tutorials/pt/collection-highlight-control.md
index ab56ba004..68076bdc4 100644
--- a/docs/tutorials/pt/collection-highlight-control.md
+++ b/docs/tutorials/pt/collection-highlight-control.md
@@ -3,8 +3,8 @@ title: 'Controle de destaque de coleção'
 id: 1tGdb2ndjqy6yWsk2YwKMu
 status: PUBLISHED
 createdAt: 2018-02-21T19:12:49.216Z
-updatedAt: 2023-03-29T18:01:46.386Z
-publishedAt: 2023-03-29T18:01:46.386Z
+updatedAt: 2023-06-22T17:42:41.479Z
+publishedAt: 2023-06-22T17:42:41.479Z
 firstPublishedAt: 2018-02-21T20:51:49.939Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
 <div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
+  <p> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do Portal CMS Legado.</a>.</p>
 </div>
 
 O controle `<vtex.cmc:HightLight/>` (para páginas de produto) ou `$product.HightLight` (para prateleiras) renderiza um elemento HTML com uma classe específica no contexto dos produtos que fizerem parte de uma coleção marcada com a flag __Highlight__.
diff --git a/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md b/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
index aa052ecdc..4d52f0fbb 100644
--- a/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
+++ b/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
@@ -31,7 +31,7 @@ Agora que você já conferiu o saldo, é importante ter em mente que o valor mí
 
 Por exemplo, caso o seu menor recebível seja de R$10, esse é o valor mínimo que você pode antecipar. Já o valor máximo é informado no próprio Admin - o saldo que você acabou de conferir - na página de “Antecipar recebíveis”. 
 
-![anteciparpaymentPT](https://images.ctfassets.net/alneenqid6w5/25BWOQcUJ4RHHefod0IkFw/3d4ba6ba362db2362e870420dd3653a3/anteciparpaymentPT.png)
+![anteciparpaymentPT](//images.ctfassets.net/alneenqid6w5/25BWOQcUJ4RHHefod0IkFw/3d4ba6ba362db2362e870420dd3653a3/anteciparpaymentPT.png)
 
 <div class=”alert alert-info”>
 <strong>Atenção</strong>: recebíveis em disputa ou previstos para o próximo dia útil não podem ser antecipados.
diff --git a/docs/tutorials/pt/conditions-builder-usage-examples.md b/docs/tutorials/pt/conditions-builder-usage-examples.md
index 9b578ea90..1154c96b9 100644
--- a/docs/tutorials/pt/conditions-builder-usage-examples.md
+++ b/docs/tutorials/pt/conditions-builder-usage-examples.md
@@ -23,7 +23,7 @@ Para entender __para que__ criar condições, veja o artigo [Criar Preços Condi
 
 UTM (Marketing tag) é uma informação que diz respeito a origem do tráfego do cliente. Então, no app existe um bloco que verifica esse tipo de informação.    
 
-![utm_source_port](https://images.ctfassets.net/alneenqid6w5/1X8rOnz0wwOgMWKE2IccGe/97a3907728c129ec075f425c9e221230/utm_source_port.png)  
+![utm_source_port](//images.ctfassets.net/alneenqid6w5/1X8rOnz0wwOgMWKE2IccGe/97a3907728c129ec075f425c9e221230/utm_source_port.png)  
 
 <div class="alert alert-warning"><strong>Nota: </strong>
 É possível que sua loja utilize customização e por isso as informações de UTM contidas na URL não estão sendo passadas para o nosso sistema. Caso use customização de Javascript, leia o artigo <a href="https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho">Por que as utms não estão sendo aplicadas ao carrinho</a>
@@ -42,7 +42,7 @@ __utm_campaign__ informa em __qual campanha__ especificamente o seu cliente clic
 __utm_medium__ informa qual __canal de propaganda__ atingiu seu cliente que pode ser, por exemplo, Email ou Banner em um site. No caso da imagem, o bloco verifica se o canal foi o *email*.  
   
   
-![utmport](https://images.ctfassets.net/alneenqid6w5/6dRgQcTn68eU8gOIIeu42o/4563858ba898bde92103408d12a9403d/utmport.png)  
+![utmport](//images.ctfassets.net/alneenqid6w5/6dRgQcTn68eU8gOIIeu42o/4563858ba898bde92103408d12a9403d/utmport.png)  
   
 Para cada um desses blocos, você têm a opção de verificar se:  
 
@@ -57,7 +57,7 @@ Para cada um desses blocos, você têm a opção de verificar se:
 Vamos supor que você queira que, para um certo produto, o preço seja especial caso o seu cliente clicou no *banner* do dia das mães que recebeu por email.  
 Logo você tem que criar uma condição que verifica se o __utm_medium__ é `email` e se o __utm_campaign__ é `dia_das_maes`. Então vai parecer algo como isso :  
 
-![exemplo](https://images.ctfassets.net/alneenqid6w5/4MTxq9CBK0EooyyGo4uKck/b5de55ca5990655b855760ea9138d91a/exemplo.png)  
+![exemplo](//images.ctfassets.net/alneenqid6w5/4MTxq9CBK0EooyyGo4uKck/b5de55ca5990655b855760ea9138d91a/exemplo.png)  
 
 ## Condições pelo carrinho de compra
 
@@ -66,7 +66,7 @@ Há 3 blocos que dizem respeito aos itens contidos carrinho de compra do usuári
 ### Quantidade Total
 Esse bloco analisa a quantidade de itens no carrinho como um todo.
 
-![qtdItens](https://images.ctfassets.net/alneenqid6w5/5CG8dotStaeC628gCWCUGO/4fbc8f8b107c2725d671c63a999ad189/qntdItens.png)  
+![qtdItens](//images.ctfassets.net/alneenqid6w5/5CG8dotStaeC628gCWCUGO/4fbc8f8b107c2725d671c63a999ad189/qntdItens.png)  
 
 - __pelo menos__ -> verifica se no carrinho de compra do usuário existe __3 ou mais itens__.
 - __no máximo__ -> verifica se no carrinho de compra do usuário existe __3 ou menos itens__.
@@ -74,7 +74,7 @@ Esse bloco analisa a quantidade de itens no carrinho como um todo.
 ### Quantidade de um SKU específico
 Esse bloco analisa a quantidade do item específico ao qual ele será atrelado no [*Conditional Price*](http://help.vtex.com/pt/tutorial/como-criar-precos-condicionais)
 
-![itemEspecifico](https://images.ctfassets.net/alneenqid6w5/7Hi9CZ1as8Oi8YkawgIKcs/5a8f7e4f5b7b9a9af64a70735c14f7df/itemEspecifico.png)  
+![itemEspecifico](//images.ctfassets.net/alneenqid6w5/7Hi9CZ1as8Oi8YkawgIKcs/5a8f7e4f5b7b9a9af64a70735c14f7df/itemEspecifico.png)  
 
 - __pelo menos__ -> verifica se no carrinho de compra do usuário existe __3 ou mais daquele item__.
 - __no máximo__ -> verifica se no carrinho de compra do usuário existe __3 ou menos daquele item__.
@@ -84,7 +84,7 @@ Esse bloco analisa a quantidade do item específico ao qual ele será atrelado n
 ### Valor total
 Esse bloco analisa o valor total que existe no carrinho.
 
-![valorTotal](https://images.ctfassets.net/alneenqid6w5/1fWh5tYsxSC60Ii8EgUWwe/830305c6df9657768663588e5b660f5d/valorTotal.png)  
+![valorTotal](//images.ctfassets.net/alneenqid6w5/1fWh5tYsxSC60Ii8EgUWwe/830305c6df9657768663588e5b660f5d/valorTotal.png)  
 
 - __pelo menos__ -> verifica se a __soma dos valores__ dos itens no carrinho vale __100 reais ou mais__.
 - __no máximo__ -> verifica se a __soma dos valores__ dos itens existrrinho vale __100 reais ou menos__.
@@ -94,7 +94,7 @@ Esse bloco analisa o valor total que existe no carrinho.
 Vamos supor que você queira dar um preço mais barato a um shampoo caso o cliente esteja levando __exatamente 3 unidades__, mas além disso precisa estar levando __no mínimo 150 reais__ em compras.
 A condição a ser criada será : 
 
-![Exemplo2](https://images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
+![Exemplo2](//images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
 
 
 
diff --git a/docs/tutorials/pt/conecta-la-integration.md b/docs/tutorials/pt/conecta-la-integration.md
index a39fa6ec6..27584a02b 100644
--- a/docs/tutorials/pt/conecta-la-integration.md
+++ b/docs/tutorials/pt/conecta-la-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integração com Conecta Lá'
 id: 403fvPYdv2f6VeP0na3awP
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-06-08T17:54:34.361Z
-updatedAt: 2023-03-29T15:27:11.094Z
-publishedAt: 2023-03-29T15:27:11.094Z
+updatedAt: 2024-02-19T20:16:43.888Z
+publishedAt: 
 firstPublishedAt: 2021-06-08T18:36:46.591Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/pt/configuracao-de-precos.md b/docs/tutorials/pt/configuracao-de-precos.md
index 73c9f9797..1d2c054a9 100644
--- a/docs/tutorials/pt/configuracao-de-precos.md
+++ b/docs/tutorials/pt/configuracao-de-precos.md
@@ -54,11 +54,11 @@ Para criar uma nova regra, siga os passos a seguir:
     - **Sempre ativar:** a tabela de preço está constantemente ativada, independente de condições.
     - **Ativar em condições específicas:** a tabela de preço será ativada segundo as condições configuradas na regra. Veja as possibilidades de configuração com as imagens a seguir:
     
-    ![PT-regra-tabela-de-preco3](https://images.ctfassets.net/alneenqid6w5/45Vklz3dKi6SH0o1Rcz33I/93beeac027a6f9ab037f348a63d2ba03/PT-regra-tabela-de-preco3.png)
+    ![PT-regra-tabela-de-preco3](//images.ctfassets.net/alneenqid6w5/45Vklz3dKi6SH0o1Rcz33I/93beeac027a6f9ab037f348a63d2ba03/PT-regra-tabela-de-preco3.png)
     
-    ![PT-regra-tabela-de-preco](https://images.ctfassets.net/alneenqid6w5/3ClC00TNkMXFIgflRdepP/d46d2298cf13f37cbbbd71acca0d39ae/PT-regra-tabela-de-preco.png)
+    ![PT-regra-tabela-de-preco](//images.ctfassets.net/alneenqid6w5/3ClC00TNkMXFIgflRdepP/d46d2298cf13f37cbbbd71acca0d39ae/PT-regra-tabela-de-preco.png)
   
-    ![PT-regra-tabela-de-preco2](https://images.ctfassets.net/alneenqid6w5/3M4QVimY2pgh2NBuuO9u7s/3aa68e1602f16548be024f29448fa21a/PT-regra-tabela-de-preco2.png)
+    ![PT-regra-tabela-de-preco2](//images.ctfassets.net/alneenqid6w5/3M4QVimY2pgh2NBuuO9u7s/3aa68e1602f16548be024f29448fa21a/PT-regra-tabela-de-preco2.png)
     
 7. Clique em Confirmar.
 
diff --git a/docs/tutorials/pt/configurar-o-cartman.md b/docs/tutorials/pt/configurar-o-cartman.md
index f96d99408..6226878fb 100644
--- a/docs/tutorials/pt/configurar-o-cartman.md
+++ b/docs/tutorials/pt/configurar-o-cartman.md
@@ -26,9 +26,9 @@ Por padrão, o Cartman já vem habilitado e disponível para uso no Checkout de
 Para desabilitar o Cartman, siga o passo a passo a seguir:
 
 1. Clique no ícone azul no canto inferior direito da tela
-![cartmantuto1](https://images.ctfassets.net/alneenqid6w5/1DWwcldpXDu4fplLm6aLjD/6c588311f60b01e5cd1e76aceb257743/cartmantuto1.PNG)
+![cartmantuto1](//images.ctfassets.net/alneenqid6w5/1DWwcldpXDu4fplLm6aLjD/6c588311f60b01e5cd1e76aceb257743/cartmantuto1.PNG)
 2. Clique em `Desativar o Cartman` na parte inferior da janela
-![cartmantuto2](https://images.ctfassets.net/alneenqid6w5/pzjFEx27xjbsRc1rWCotI/504771d0251a952769b043d17412250f/cartmantuto2.PNG)
+![cartmantuto2](//images.ctfassets.net/alneenqid6w5/pzjFEx27xjbsRc1rWCotI/504771d0251a952769b043d17412250f/cartmantuto2.PNG)
 
 Desse modo, a ferramenta será interrompida. Porém, se for preciso habilitá-la novamente, o processo “reverso” é semelhante ao primeiro passo a passo.
 
@@ -38,7 +38,7 @@ Existem duas formas de “reabilitar” o Cartman.
 
 - Domínio de site
 Para que o Cartman seja reativado para o site inteiro, basta clicar em `Reativar Agora` na mesma janela de configuração. Automaticamente, a ferramenta retoma o seu funcionamento.
-![cartmantuto3](https://images.ctfassets.net/alneenqid6w5/2YR5bMxxzhMjsRDbmSHHsG/862261ed7433e068cbf2b19f2d8bb652/cartmantuto3.PNG)
+![cartmantuto3](//images.ctfassets.net/alneenqid6w5/2YR5bMxxzhMjsRDbmSHHsG/862261ed7433e068cbf2b19f2d8bb652/cartmantuto3.PNG)
 
 - Navegador de uso 
 Se o interesse for exibir o Cartman apenas no navegador do usuário de e-commerce, é preciso incluir a query string `?cartman=on` no final da URL desejada - `https://accountname.vtex.com/checkout?cartman=on` - e reiniciar o domínio. Desse modo, o ícone azul aparecerá novamente no canto inferior direito da página.
diff --git a/docs/tutorials/pt/configure-cartman.md b/docs/tutorials/pt/configure-cartman.md
index b5de73364..4f2adefb6 100644
--- a/docs/tutorials/pt/configure-cartman.md
+++ b/docs/tutorials/pt/configure-cartman.md
@@ -3,8 +3,8 @@ title: 'Configurar o Cartman'
 id: 1ACMTStZYkMqB0lTgwg451
 status: PUBLISHED
 createdAt: 2019-09-03T15:02:48.303Z
-updatedAt: 2022-06-15T23:16:07.805Z
-publishedAt: 2022-06-15T23:16:07.805Z
+updatedAt: 2024-03-13T18:18:17.017Z
+publishedAt: 2024-03-13T18:18:17.017Z
 firstPublishedAt: 2019-09-09T18:28:20.208Z
 contentType: tutorial
 productTeam: Shopping
@@ -27,6 +27,7 @@ Neste artigo serão abordados os seguintes tópicos:
 
 - [Ativar o Cartman manualmente](#ativar-o-cartman-manualmente)
 - [Funções do Cartman](#funcoes-do-cartman)
+  - [Simulador de promoções](#simulador-de-promocoes)
   - [Obter informações dos items no carrinho](#obter-as-informacoes-dos-items-no-carrinho)
   - [Adicionar itens específicos no carrinho](#adicionar-itens-especificos-no-carrinho)
   - [Adicionar itens aleatórios no carrinho](#adicionar-itens-aleatorios-no-carrinho)
@@ -43,15 +44,21 @@ Para ativar o Cartman manualmente, siga os passos abaixo:
 
 1. Acesse uma página de Checkout da sua loja (`https://{accountname}.myvtex.com/checkout/`).
 2. Insira a query string `?cartman=on` no final da URL (`https://accountname.myvtex.com/checkout?cartman=on`).
-3. No canto inferior direito da tela, clique no botão <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para acessar o Cartman.
+3. No canto inferior direito da tela, clique no botão <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para acessar o Cartman.
 
 ## Funções do Cartman
 
+### Simulador de promoções
+
+Ao acessar o **Simulador de Promoções**, você pode visualizar as promoções criadas na sua loja que foram aplicadas no carrinho de compras e os motivos para sua ativação. Também é possível testar a aplicação de promoções antes de ativá-las, incluindo promoções agendadas e inativas.
+
+Para saber usar essa ferramenta, leia o guia [Simulador de Promoções](https://help.vtex.com/pt/tutorial/simulador-de-promocoes-beta--4zc8SNqjqeIJ0ZRMhjlnvy).
+
 ### Obter as informações dos items no carrinho
 
 Ao acessar o menu **Ver detalhes do item**, é possível verificar as informações específicas de cada um dos produtos selecionados no carrinho.
 
-![Detalhes do item](https://images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/be488177768aa068425cd4fe3bfe9186/Detalhes_do_item.PNG)
+![Detalhes do item](//images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/be488177768aa068425cd4fe3bfe9186/Detalhes_do_item.PNG)
 
 ### Adicionar itens específicos no carrinho
 
@@ -61,7 +68,7 @@ Em **Adicionar itens pelo ID do SKU**, novos itens podem ser inseridos no carrin
 - **Quantidade de cada item**: indicação de quantas unidades do SKU serão adicionadas no carrinho.
 - **ID do seller**: número de identificação do seller que realizará a entrega do item.
 
-![Adicionar itens pelo ID do SKU](https://images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/d77dd07bcc3886f41bad702ac74da401/Adicionar_itens_pelo_ID_do_SKU.PNG)
+![Adicionar itens pelo ID do SKU](//images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/d77dd07bcc3886f41bad702ac74da401/Adicionar_itens_pelo_ID_do_SKU.PNG)
 
 ### Adicionar itens aleatórios no carrinho
 
@@ -75,7 +82,7 @@ Em **Adicionar itens aleatórios**, novos itens do catálogo da loja podem ser i
 - ID do seller
 - Faixa de preço (Preço de / Preço até)
 
-![Adicionar itens aleatórios](https://images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/805100572b36c043100c941fda45b732/Adicionar_itens_aleat__rios.PNG)
+![Adicionar itens aleatórios](//images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/805100572b36c043100c941fda45b732/Adicionar_itens_aleat__rios.PNG)
 
 ### Definir dados de marketing
 
@@ -87,7 +94,7 @@ Na opção **Definir dados de marketing**, é possível aplicar cupons de descon
 - **utmi_cp**: utm interna utilizada para definir quando será aplicada uma determinada promoção, de acordo com a utm descrita na URL do pedido. 
 - **Cupom**: código do cupom de desconto a ser adicionado no carrinho.
 
-![Definir dados de marketing](https://images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/ae8e80765f7ff1255f03e5f48a4b4edb/Definir_dados_de_marketing.PNG)
+![Definir dados de marketing](//images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/ae8e80765f7ff1255f03e5f48a4b4edb/Definir_dados_de_marketing.PNG)
 
 Para saber mais sobre UTMs e UTMIs , acesse [O que são utm_source, utm_campaign e utm_medium](https://help.vtex.com/pt/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii#) e [O que são as UTMs internas utmi_cp, utmi_pc e utmi_p](https://help.vtex.com/pt/tutorial/o-que-sao-as-utms-internas-utmi_cp-utmi_pc-e-utmi_p#).
 
@@ -96,7 +103,7 @@ Para saber mais sobre UTMs e UTMIs , acesse [O que são utm_source, utm_campaign
 O Cartman pode ser desativado a qualquer momento, conforme a necessidade do lojista. Para desativá-lo, siga os passos abaixo:
 
 1. Acesse uma página de Checkout da sua loja (`https://{accountname}.myvtex.com/checkout/`).
-2. No canto inferior direito da tela, clique no botão <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
+2. No canto inferior direito da tela, clique no botão <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
 3. Na parte inferior do menu do Cartman, clique em `Desativar o Cartman`.
 
 <div class="alert alert-info">
diff --git a/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md b/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md
index 81ffb3111..bf2278c37 100644
--- a/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md
+++ b/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md
@@ -3,8 +3,8 @@ title: 'Configurar crédito direto ao consumidor (CDC) da Losango'
 id: 4vfoIULHTs8S9t3WDyldCE
 status: PUBLISHED
 createdAt: 2020-11-23T20:29:21.353Z
-updatedAt: 2023-03-30T15:42:27.683Z
-publishedAt: 2023-03-30T15:42:27.683Z
+updatedAt: 2024-01-23T18:47:11.153Z
+publishedAt: 2024-01-23T18:47:11.153Z
 firstPublishedAt: 2020-11-23T21:04:18.389Z
 contentType: tutorial
 productTeam: Financial
@@ -43,16 +43,16 @@ Após a aprovação do seu cadastro, a Losango enviará um script pré-aprovado
 Tendo em mãos o script pré-aprovado de customização, siga as instruções abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Checkout**, ou digite **Checkout** na barra de busca no topo da página.
-2. Clique no ícone <img src="https:https://images.ctfassets.net/alneenqid6w5/3d4KBPLr2piZGC48KD3qgh/6f808efc5450f36faa773d4c7d848b68/CDC-Losango-1.png" style="width: 23px;" /> correspondente ao site que será customizado
-    ![CDC-Losango-2](https://images.ctfassets.net/alneenqid6w5/7iUE1B4xlYF96gMs0oMfUn/2a55fcd4cc8f0239a0785634e29a18df/CDC-Losango-2.png)
+2. Clique no ícone <img src="https://images.ctfassets.net/alneenqid6w5/3d4KBPLr2piZGC48KD3qgh/6f808efc5450f36faa773d4c7d848b68/CDC-Losango-1.png" style="width: 23px;" /> correspondente ao site que será customizado
+    ![CDC-Losango-2](//images.ctfassets.net/alneenqid6w5/7iUE1B4xlYF96gMs0oMfUn/2a55fcd4cc8f0239a0785634e29a18df/CDC-Losango-2.png)
 3. Clique na aba Código e selecione o arquivo `checkout6-custom.js`.
-    ![CDC-Losango-3](https://images.ctfassets.net/alneenqid6w5/248J5RJvoSq2olzQoPsNKn/3598c85f81649667f21d4d5fa40d71b4/CDC-Losango-3.png)
+    ![CDC-Losango-3](//images.ctfassets.net/alneenqid6w5/248J5RJvoSq2olzQoPsNKn/3598c85f81649667f21d4d5fa40d71b4/CDC-Losango-3.png)
 4. Cole o script pré-aprovado de customização __no fim do campo de texto__.
 5. Clique no botão __Salvar__ para confirmar as alterações.
 
 Com isso, a opção de pagamento __Losango em até 24x__ aparecerá corretamente no checkout, assim que as [condições de pagamento](#criar-condicoes-de-pagamento) associadas forem ativadas. A escolha do meio de pagamento na VTEX aparecerá como na imagem abaixo.
 
-![CDC-Losango-4](https:https://images.ctfassets.net/alneenqid6w5/5dzHuCYPxHpy88Q2RjfZeJ/4ad6d24322184f7f756a9d994ed63e94/CDC-Losango-4.png)
+![CDC-Losango-4](https://images.ctfassets.net/alneenqid6w5/5dzHuCYPxHpy88Q2RjfZeJ/4ad6d24322184f7f756a9d994ed63e94/CDC-Losango-4.png)
 
 <div class="alert alert-warning" role="alert"><strong>Atenção:</strong> Modificar de forma incorreta os scripts de customização do checkout podem quebrar sua loja ou parar as vendas. Em caso de erros, por favor, apague o conteúdo deste script.</div>
 
@@ -60,24 +60,21 @@ Com isso, a opção de pagamento __Losango em até 24x__ aparecerá corretamente
 
 Com os dados configurados na base de dados digital da Losango, siga as instruções abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página. 
-2. Acesse a aba **Afiliações de Gateways** e clique no ícone <img src="https:https://images.ctfassets.net/alneenqid6w5/3VXFXGXxCMc9cRMehCiuth/6ae901b40c89d05d4c252feb8df14f5a/CDC-Losango-5.png" style="width: 23px;" /> e escolha o conector __Losango-CDC__.
-
-    ![CDC-Losango-6](https:https://images.ctfassets.net/alneenqid6w5/790PjCjRzKrtrEIrr3kYWl/85e1b1132be72cc4766e18d869e2040b/CDC-Losango-6.png)
-
-3. Escolha o __Nome da afiliação__ e selecione o modo desejado (Teste / Produção).
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Losango-CDC__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com os dados fornecidos pela Losango. Não se esqueça de __Salvar__ ao concluir o preenchimento.
 
-![CDC-Losango-7](https:https://images.ctfassets.net/alneenqid6w5/50xjhDq3CwFR522i1k5sZS/982931d897d8739dc3950dda408c5e2a/CDC-Losango-7.png)
+![CDC-Losango-7](https://images.ctfassets.net/alneenqid6w5/50xjhDq3CwFR522i1k5sZS/982931d897d8739dc3950dda408c5e2a/CDC-Losango-7.png)
 
 ### Criar condições de pagamento
 
 Para finalizar a configuração do CDC Online Losango e disponibilizar este meio de pagamento na sua loja, siga as instruções abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página. 
-2. Acesse a aba **Condições de Pagamento**. Clique no ícone <img src="https:https://images.ctfassets.net/alneenqid6w5/3VXFXGXxCMc9cRMehCiuth/6ae901b40c89d05d4c252feb8df14f5a/CDC-Losango-5.png" style="width: 23px;" /> e escolha __Losango__.
+2. Acesse a aba **Condições de Pagamento**. Clique no ícone <img src="https://images.ctfassets.net/alneenqid6w5/3VXFXGXxCMc9cRMehCiuth/6ae901b40c89d05d4c252feb8df14f5a/CDC-Losango-5.png" style="width: 23px;" /> e escolha __Losango__.
 
-    ![CDC-Losango-8](https://images.ctfassets.net/alneenqid6w5/1sGB3vlu73A9Ms6EmbIeeG/e22c65c4e528e23f2c00caef0a930323/CDC-Losango-8.png)
+    ![CDC-Losango-8](//images.ctfassets.net/alneenqid6w5/1sGB3vlu73A9Ms6EmbIeeG/e22c65c4e528e23f2c00caef0a930323/CDC-Losango-8.png)
 
 3. Configure e ative a [condição de pagamento](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) com as regras desejadas. Não se esqueça de __Salvar__ ao concluir o preenchimento.
 
diff --git a/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
index 6a36a777d..a16e049fb 100644
--- a/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
@@ -45,7 +45,7 @@ Aqui, a propriedade comum dos clientes é que eles também são funcionários da
 Este artigo assume que os colaboradores estão devidamente registrados com um campo booleano `é funcionário` definido como verdadeiro em seus respectivos documentos para a entidade de dados CL, como demonstrado na figura abaixo. 
 
 Caso contrário, verifique o artigo [Criando um campo no Master Data](https://help.vtex.com/pt/tutorial/como-crio-um-campo-no-master-data--frequentlyAskedQuestions_1829) para criar um campo que identifique os funcionários e configure-o adequadamente para cada documento correspondente aos funcionários.
-![Campo do colaborador](https://images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
+![Campo do colaborador](//images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
 
 <div class="alert-info" role="alert">São muitos os detalhes para configurar uma promoção. Se você precisar de informações adicionais sobre este assunto, consulte o artigo <a href="https://help.vtex.com/pt/tutorial/como-criar-promocoes--tutorials_320">Criar promoções</a>.</div>
 
@@ -60,4 +60,4 @@ Com o campo configurado, a promoção pode ser criada seguindo os passos abaixo:
 7. No final da página, clique no botão **Salvar***.
 
 Depois disso, a promoção já funcionará conforme configurada. O desconto é mostrado apenas no carrinho de compras. A imagem abaixo mostra um exemplo com 99% de desconto.
-![carrinho de compras com desconto](https://images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
+![carrinho de compras com desconto](//images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
diff --git a/docs/tutorials/pt/configure-payment-with-pix-at-nubank.md b/docs/tutorials/pt/configure-payment-with-pix-at-nubank.md
index 5bd56ada7..79991b77e 100644
--- a/docs/tutorials/pt/configure-payment-with-pix-at-nubank.md
+++ b/docs/tutorials/pt/configure-payment-with-pix-at-nubank.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Pix no Nubank'
 id: 2pJBJdtkvyn645rL2sxyJy
 status: PUBLISHED
 createdAt: 2022-07-19T16:38:08.465Z
-updatedAt: 2023-03-24T15:03:05.135Z
-publishedAt: 2023-03-24T15:03:05.135Z
+updatedAt: 2024-01-23T19:11:23.258Z
+publishedAt: 2024-01-23T19:11:23.258Z
 firstPublishedAt: 2022-07-19T16:56:30.888Z
 contentType: tutorial
 productTeam: Financial
@@ -17,11 +17,11 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Na VTEX, sua loja pode realizar a integração com o gateway Nubank e receber por meio de Pix.
 
-Para configurar a afiliação do Nubank com recebimento via Pix, siga os passos abaixo:
+Para configurar o Nubank com recebimento via Pix, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __SpinPay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __SpinPay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Nubank.
 5. Clique em `Salvar`.
 
diff --git a/docs/tutorials/pt/configure-payment-with-shopfacil.md b/docs/tutorials/pt/configure-payment-with-shopfacil.md
new file mode 100644
index 000000000..e682db1e4
--- /dev/null
+++ b/docs/tutorials/pt/configure-payment-with-shopfacil.md
@@ -0,0 +1,41 @@
+---
+title: 'Configurar pagamento com ShopFácil'
+id: 4v3z3CLrgZ2bByMx7uoMeG
+status: PUBLISHED
+createdAt: 2023-07-14T16:49:07.504Z
+updatedAt: 2024-01-23T21:31:46.325Z
+publishedAt: 2024-01-23T21:31:46.325Z
+firstPublishedAt: 2023-07-14T16:57:55.320Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-shopfacil
+locale: pt
+legacySlug: configurar-pagamento-com-shopfacil
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, sua loja pode realizar a integração com o gateway ShopFácil e receber por meio de Pix.
+
+Para configurar ShopFácil, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __ShopfacilPayment__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta ShopFácil.
+5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
+2. Na aba __Condições de pagamento__, clique no botão `+`.
+3. Em __Pagamento Instantâneo__, selecione a opção __Pix__.
+4. Preencha o campo __Nome da regra__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Em __Processar com a afiliação__, selecione o conector __ShopfacilPayment__.
+7. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o conector ShopFácil pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+
diff --git a/docs/tutorials/pt/configure-seller-regionalization.md b/docs/tutorials/pt/configure-seller-regionalization.md
index 2387fb17d..b48ec7f6b 100644
--- a/docs/tutorials/pt/configure-seller-regionalization.md
+++ b/docs/tutorials/pt/configure-seller-regionalization.md
@@ -3,8 +3,8 @@ title: 'Configurar a regionalização de sellers'
 id: 32t6wLpQCEnumoh8TjT5fw
 status: PUBLISHED
 createdAt: 2022-08-26T13:58:10.648Z
-updatedAt: 2022-08-26T18:34:14.924Z
-publishedAt: 2022-08-26T18:34:14.924Z
+updatedAt: 2023-07-17T12:11:40.614Z
+publishedAt: 2023-07-17T12:11:40.614Z
 firstPublishedAt: 2022-08-26T18:34:14.924Z
 contentType: tutorial
 productTeam: Shopping
@@ -41,7 +41,7 @@ Com a utilização do **Region**, caso o cliente realize o login na loja ainda d
 Para ativar o **Region** em sua loja, é necessário realizar os seguintes passos:
 
 1. [Configurar preço e disponibilidade de SKUs por Region](https://help.vtex.com/pt/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc#)
-2. [Habilitar a funcionalidade Region](https://developers.vtex.com/vtex-rest-api/docs/how-to-configure-region-feature-sku)
+2. [Habilitar a funcionalidade Region](https://developers.vtex.com/docs/guides/enable-the-region-for-skus)
 
 <div class="alert alert-info">
   Atualmente, o <b>Region</b> está disponível para utilização em todas as lojas VTEX na versão v2. Saiba mais em <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
diff --git a/docs/tutorials/pt/configure-template-in-smartcheckout-update.md b/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
index 4e53ed120..07ff95dcf 100644
--- a/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
@@ -37,11 +37,11 @@ Cada site cadastrado corresponde a um multidomínio (caso a conta possua multido
 
 Criação do novo site: 
 
-![Novo Site](https://images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
+![Novo Site](//images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
 
 Acesso ao __Nome da Conta__: 
 
-![PT Configuração da Conta Nome Loja](https://images.ctfassets.net/alneenqid6w5/5SDjJWbYx8qiYMuvaKNEF/7c3b2eaa76035f0d2682fb07053dc3a1/PT_Paint_Nome_da_Conta.png)
+![PT Configuração da Conta Nome Loja](//images.ctfassets.net/alneenqid6w5/5SDjJWbYx8qiYMuvaKNEF/7c3b2eaa76035f0d2682fb07053dc3a1/PT_Paint_Nome_da_Conta.png)
 
 ## Editar e configurar site
 
@@ -56,13 +56,13 @@ Acesso ao __Nome da Conta__:
    - __Páginas__: exibir as páginas existentes para o site. 
 
 Exemplo de sites existentes em uma mesma conta:
-![PT Cards Portal](https://images.ctfassets.net/alneenqid6w5/3662yoC7zsRw8ME8bI7Efo/f3c845f13ea5586364b28b807cc3c3fa/PT_Cards_Portal.png)
+![PT Cards Portal](//images.ctfassets.net/alneenqid6w5/3662yoC7zsRw8ME8bI7Efo/f3c845f13ea5586364b28b807cc3c3fa/PT_Cards_Portal.png)
 
 Exemplo de páginas disponíveis para um site:
-![PT Paginas Cropped (2)](https://images.ctfassets.net/alneenqid6w5/4d5vICcJDiNZFR8fIpn9j0/fb8cf9adceae47b99eac9f352b1b912f/PT_Paginas_Cropped__2_.png)
+![PT Paginas Cropped (2)](//images.ctfassets.net/alneenqid6w5/4d5vICcJDiNZFR8fIpn9j0/fb8cf9adceae47b99eac9f352b1b912f/PT_Paginas_Cropped__2_.png)
 
 Caso deseje __excluir__ um site, clique no botão de exclusão do site desejado, como no exemplo indicado abaixo:
-![PT Card Croppped Delete](https://images.ctfassets.net/alneenqid6w5/2c4FWLHb0TLa8mEJXOdmg4/71a9f95969d7e8cfe6c9d1379b4e5071/PT_Card_Croppped_Delete.png)
+![PT Card Croppped Delete](//images.ctfassets.net/alneenqid6w5/2c4FWLHb0TLa8mEJXOdmg4/71a9f95969d7e8cfe6c9d1379b4e5071/PT_Card_Croppped_Delete.png)
 
 A seguir, vamos aprofundar o passo a passo da configuração das oções de menu: __Código__ e __Checkout__, sendo estas responsáveis por configurar as páginas de *Checkout* e *Order Placed*.
 
@@ -79,7 +79,7 @@ A seguir, vamos aprofundar o passo a passo da configuração das oções de menu
   <li><b>Cálculo das opções de Entrega (Beta e Stable)</b>: selecione se o cálculo do frete será feito a partir da planilha ou por geolocalização.</li>
   </ul>
 
-![PT Editar Checkout](https://images.ctfassets.net/alneenqid6w5/nzvyVXocA6pW8l9pBvRzg/1059880c29b9e57e4505b654c9a40013/PT_Editar_Checkout.png)
+![PT Editar Checkout](//images.ctfassets.net/alneenqid6w5/nzvyVXocA6pW8l9pBvRzg/1059880c29b9e57e4505b654c9a40013/PT_Editar_Checkout.png)
 
 ## Configurar código
 
@@ -87,7 +87,7 @@ A seguir, vamos aprofundar o passo a passo da configuração das oções de menu
 2. Clique no ícone <i class="fas fa-cog" alt="engrenagem azul"></i> do site desejado.
 3. No menu de opções azul localizado na parte superior da página, clique em __Código__. Será exibido, à direita, um menu de __Arquivos__ e __Templates__ com todos os templates de seu site, configurados pelo sistema.
 
-![PT Lista Código Templates](https://images.ctfassets.net/alneenqid6w5/57N9pQSWVF2e09URYV2avm/7cda1ca4cfe42d9c4fd503741121607d/PT_Lista_C__digo_Templates.PNG)
+![PT Lista Código Templates](//images.ctfassets.net/alneenqid6w5/57N9pQSWVF2e09URYV2avm/7cda1ca4cfe42d9c4fd503741121607d/PT_Lista_C__digo_Templates.PNG)
 
 ### Configurar templates do menu "Código"
 
@@ -107,27 +107,27 @@ Abaixo temos exemplos de como os códigos presentes nos templates do __checkout-
 
 - Template __checkout-header__ e cabeçalho da página do site:
 
-![checkout-header-codigo-pt](https://images.ctfassets.net/alneenqid6w5/4VRv3IKpL8ZOSpANmu0gTG/072b530037076e75f17ebd809de557e3/PT_C__digo_Checkout_Header_Preenchido.png)
+![checkout-header-codigo-pt](//images.ctfassets.net/alneenqid6w5/4VRv3IKpL8ZOSpANmu0gTG/072b530037076e75f17ebd809de557e3/PT_C__digo_Checkout_Header_Preenchido.png)
 
-![checkout-header-page-pt](https://images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/791259e534c7a081a5791b1e0c508df5/smartcheckout11.pt.png)
+![checkout-header-page-pt](//images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/791259e534c7a081a5791b1e0c508df5/smartcheckout11.pt.png)
 
 - Template __checkout-footer__ e rodapé da página do site:
 
-![checkout-footer-codigo-pt](https://images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
+![checkout-footer-codigo-pt](//images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
 
-![checkout-footer-page-pt](https://images.ctfassets.net/alneenqid6w5/7yiOKZsTi9n48HhTIj5pId/7784d3a57075f60888ba66acb5710ea9/checkout_footer.pt.png)
+![checkout-footer-page-pt](//images.ctfassets.net/alneenqid6w5/7yiOKZsTi9n48HhTIj5pId/7784d3a57075f60888ba66acb5710ea9/checkout_footer.pt.png)
 
 - Template __vtex-checkout__ e página do carrinho no Checkout:
 
-![smartcheckout16.pt](https://images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
+![smartcheckout16.pt](//images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
 
-![vtex-checkout-page-pt](https://images.ctfassets.net/alneenqid6w5/3X1KG01hUMDyVxvEAXDoeP/57e0e59e1dfd762cb8cea27de5b55c31/smartcheckout17.pt.png)
+![vtex-checkout-page-pt](//images.ctfassets.net/alneenqid6w5/3X1KG01hUMDyVxvEAXDoeP/57e0e59e1dfd762cb8cea27de5b55c31/smartcheckout17.pt.png)
 
 - Template __vtex-orderPlaced__ e página do pedido confirmado:
 
-![smartcheckout18.pt](https://images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) 
+![smartcheckout18.pt](//images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) 
 
-![vtex-orderplaced-page-pt](https://images.ctfassets.net/alneenqid6w5/6bJ25wGbKqO1KkFsJ5qtSF/291283a570adbe29b64c6076e2a197ec/smartcheckout19.pt.png)
+![vtex-orderplaced-page-pt](//images.ctfassets.net/alneenqid6w5/6bJ25wGbKqO1KkFsJ5qtSF/291283a570adbe29b64c6076e2a197ec/smartcheckout19.pt.png)
 
 ### Contas com multidomínio
 
diff --git a/docs/tutorials/pt/configure-template-in-the-smartcheckout.md b/docs/tutorials/pt/configure-template-in-the-smartcheckout.md
index 45266ada7..e2858f3b0 100644
--- a/docs/tutorials/pt/configure-template-in-the-smartcheckout.md
+++ b/docs/tutorials/pt/configure-template-in-the-smartcheckout.md
@@ -34,9 +34,9 @@ Agora, preencha os campos abaixo seguindo as instruções:
 
 Veja a imagem abaixo:
 
-![Novo Site](https://images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
+![Novo Site](//images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
 
-![smartcheckout2.pt](https://images.ctfassets.net/alneenqid6w5/6klkJKS7Jegp0YvISd4UFz/c84e643fa16420603a40a09f1942356f/smartcheckout2.pt.png)
+![smartcheckout2.pt](//images.ctfassets.net/alneenqid6w5/6klkJKS7Jegp0YvISd4UFz/c84e643fa16420603a40a09f1942356f/smartcheckout2.pt.png)
 
 Clique em __Salvar__ para concluir o cadastro do novo site.
 
@@ -51,17 +51,17 @@ Com isto, o sistema exibe todas as informações de configuração e permite nav
 - Código: Templates relacionados ao site.
 - Páginas: Exibe as páginas existentes para o site. Por padrão, são criadas duas páginas: **checkout **e **checkout/orderPlaced**. Como já dito, no inicio desse post, a página **checkout**corresponde às páginas de carrinho, dados pessoais, endereço e forma de pagamento. A página **checkout/orderPlaced** corresponde à página de Confirmação de Compra.
 
-![smartcheckout3.pt](https://images.ctfassets.net/alneenqid6w5/6j24QAEDzt7QdGc5wC5ENH/c0d27ea44a8cb300ed4c87755f6a940f/smartcheckout3.pt.png)
+![smartcheckout3.pt](//images.ctfassets.net/alneenqid6w5/6j24QAEDzt7QdGc5wC5ENH/c0d27ea44a8cb300ed4c87755f6a940f/smartcheckout3.pt.png)
 
 Em **Páginas** é possível **Criar** novas páginas, **Editar** e **Excluir** páginas existentes. Veja as duas imagens seguintes demonstrando **Edição** e **Exclusão**. A criação segue mesmas regras de edição.
 
 Edição de Página:
 
-![smartcheckout4.pt](https://images.ctfassets.net/alneenqid6w5/5CeBH7XHH2YZ73KORrJ5JA/0469b81979a8b9d1194294c6c6a0963d/smartcheckout4.pt.png)
+![smartcheckout4.pt](//images.ctfassets.net/alneenqid6w5/5CeBH7XHH2YZ73KORrJ5JA/0469b81979a8b9d1194294c6c6a0963d/smartcheckout4.pt.png)
 
 Exclusão de Página:
 
-![smartcheckout5.pt](https://images.ctfassets.net/alneenqid6w5/4Nk7FXMSfMGtez5YzSFi42/d0199266c1344098581d330982770b14/smartcheckout5.pt.png)
+![smartcheckout5.pt](//images.ctfassets.net/alneenqid6w5/4Nk7FXMSfMGtez5YzSFi42/d0199266c1344098581d330982770b14/smartcheckout5.pt.png)
 
 Em **Configurações** podemos editar os campos abaixo:
 
@@ -72,39 +72,39 @@ Em **Configurações** podemos editar os campos abaixo:
 
 Segue imagem exemplificando preenchimento desse formulário:
 
-![smartcheckout6.pt](https://images.ctfassets.net/alneenqid6w5/42MYGPJflf6kIhOvY05Mky/1e3354e60bc02de5ad0988e9a59d0928/smartcheckout6.pt.png)
+![smartcheckout6.pt](//images.ctfassets.net/alneenqid6w5/42MYGPJflf6kIhOvY05Mky/1e3354e60bc02de5ad0988e9a59d0928/smartcheckout6.pt.png)
 
 Em **Código**, serão exibidos, a direita, todos os templates relacionados ao Site. Por padrão, o sistema configura os templates exemplificados na imagem abaixo:
 
-![smartcheckout7.pt](https://images.ctfassets.net/alneenqid6w5/6bJ9cMwGj9dEoXFrm8M1hP/45f5c580f98366f6ed8eeb1ad6186a54/smartcheckout7.pt.png)
+![smartcheckout7.pt](//images.ctfassets.net/alneenqid6w5/6bJ9cMwGj9dEoXFrm8M1hP/45f5c580f98366f6ed8eeb1ad6186a54/smartcheckout7.pt.png)
 
 Desses templates, os únicos que não podem ser alterados são **vtex-checkout **e **vtex-orderPlaced**. Esses templates correspondem ao funcionamento nativo da plataforma, ou seja, são eles que renderizam o conteúdo principal dessas páginas, tanto o checkout quanto o orderPlaced.
 
 Na imagem seguinte, demonstramos a área afetada, no checkout, pela configuração do template **checkout-footer**. Esse é apenas um exemplo de template vazio.
 
-![smartcheckout8.pt](https://images.ctfassets.net/alneenqid6w5/5zOhjcWGREbNGMMQcByTQe/a10257507cc13def1c061de57f71abcc/smartcheckout8.pt.png) ![smartcheckout9.pt](https://images.ctfassets.net/alneenqid6w5/1cz4RwceNJi7fTgxTaYVkH/3ec8f3b5362a74b0ab25a3baf1fb0cd1/smartcheckout9.pt.png)
+![smartcheckout8.pt](//images.ctfassets.net/alneenqid6w5/5zOhjcWGREbNGMMQcByTQe/a10257507cc13def1c061de57f71abcc/smartcheckout8.pt.png) ![smartcheckout9.pt](//images.ctfassets.net/alneenqid6w5/1cz4RwceNJi7fTgxTaYVkH/3ec8f3b5362a74b0ab25a3baf1fb0cd1/smartcheckout9.pt.png)
 
 Na próxima imagem, temos um exemplo equivalente ao anterior, porém, dessa vez, com código HTML preenchido. Note que o código preenchido na esquerda corresponde a área superior da direita. Esse é o template **checkout-header**.
 
-![smartcheckout10.pt](https://images.ctfassets.net/alneenqid6w5/3Y0fVHj9U5zvSJAAtRQ3Nd/159735c9a5a79fa274bc0a3c63377f24/smartcheckout10.pt.png) ![smartcheckout11.pt](https://images.ctfassets.net/alneenqid6w5/16Ivg9yAPkvSRDzQ2JLG9h/bd1bb45eb3524f8312a82edc2da71656/smartcheckout11.pt.png)
+![smartcheckout10.pt](//images.ctfassets.net/alneenqid6w5/3Y0fVHj9U5zvSJAAtRQ3Nd/159735c9a5a79fa274bc0a3c63377f24/smartcheckout10.pt.png) ![smartcheckout11.pt](//images.ctfassets.net/alneenqid6w5/16Ivg9yAPkvSRDzQ2JLG9h/bd1bb45eb3524f8312a82edc2da71656/smartcheckout11.pt.png)
 
 Como podemos ver na próxima imagem, todos os templates que possuem o prefixo **checkout**serão utilizados em todas as páginas do Checkout. Nesse exemplo, já estamos na página Forma de Pagamento e note que o header carregado é o mesmo do exemplo anterior.
 
-![smartcheckout12.pt](https://images.ctfassets.net/alneenqid6w5/5To5Y80RxE0NNan0zocQiV/16e89c5e0b13175285dcfa59025bc061/smartcheckout12.pt.png) ![smartcheckout13.pt](https://images.ctfassets.net/alneenqid6w5/3FWj22GAEYMHzssrZxcgze/8c823c3f6df9f0cc15ee050028a1247e/smartcheckout13.pt.png)
+![smartcheckout12.pt](//images.ctfassets.net/alneenqid6w5/5To5Y80RxE0NNan0zocQiV/16e89c5e0b13175285dcfa59025bc061/smartcheckout12.pt.png) ![smartcheckout13.pt](//images.ctfassets.net/alneenqid6w5/3FWj22GAEYMHzssrZxcgze/8c823c3f6df9f0cc15ee050028a1247e/smartcheckout13.pt.png)
 
 Como nos templates do **checkout**, o mesmo acontece com os templates de orderPlaced. Ou seja, os templates com prefixo **orderPlaced** correspondem unicamente a página OrderPlaced (Confirmação de Compra).
 
-![smartcheckout14.pt](https://images.ctfassets.net/alneenqid6w5/1BKz1PqcVmyrmmxOJe3SW7/11badcd39ab3011e994ba7ef2f73c72b/smartcheckout14.pt.png) ![smartcheckout15.pt](https://images.ctfassets.net/alneenqid6w5/6eCGmlImxDRmGRpIyfvFDs/97ecf1e0821f9b33ca3a4764b456777c/smartcheckout15.pt.png)
+![smartcheckout14.pt](//images.ctfassets.net/alneenqid6w5/1BKz1PqcVmyrmmxOJe3SW7/11badcd39ab3011e994ba7ef2f73c72b/smartcheckout14.pt.png) ![smartcheckout15.pt](//images.ctfassets.net/alneenqid6w5/6eCGmlImxDRmGRpIyfvFDs/97ecf1e0821f9b33ca3a4764b456777c/smartcheckout15.pt.png)
 
 Como explicado acima, os únicos templates que não são permitidas alterações são **vtex-checkout** e **vtex-orderPlaced**. Esses templates renderizam ao conteúdo básico das páginas Checkout e OrderPlaced. A seguir, exemplos do conteúdo renderizado pelos templates.
 
 Template **vtex-checkout**:
 
-![smartcheckout16.pt](https://images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) ![smartcheckout17.pt](https://images.ctfassets.net/alneenqid6w5/qWTeYs6xpCvSSHJxRjOTq/df1d297f88bcabd7a31659bf8a615bd3/smartcheckout17.pt.png)
+![smartcheckout16.pt](//images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) ![smartcheckout17.pt](//images.ctfassets.net/alneenqid6w5/qWTeYs6xpCvSSHJxRjOTq/df1d297f88bcabd7a31659bf8a615bd3/smartcheckout17.pt.png)
 
 Template **vtex-orderPlaced**:
 
-![smartcheckout18.pt](https://images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) ![smartcheckout19.pt](https://images.ctfassets.net/alneenqid6w5/59SQfj6KKy9kWKKFla3YyV/e7625167d5ed26fe8394e5c6b559f8c5/smartcheckout19.pt.png)
+![smartcheckout18.pt](//images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) ![smartcheckout19.pt](//images.ctfassets.net/alneenqid6w5/59SQfj6KKy9kWKKFla3YyV/e7625167d5ed26fe8394e5c6b559f8c5/smartcheckout19.pt.png)
 
 As contas que possuem multi domínio podem usar apenas um site, se não houver necessidade de configurações específicas. Isso porque, ainda que exista apenas um Site, a plataforma inclui uma classe na tag &lt;body&gt; de acordo com o domínio acessado. Dessa forma, é simples aplicar layouts diferentes para o mesmo site.
 
diff --git a/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md b/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md
index bddedcb7c..c8f2fb333 100644
--- a/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md
+++ b/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md
@@ -33,7 +33,7 @@ Depois de determinar o desconto no Checkout, é preciso atrelar o SKU ao meio de
 3. Clique no template da sua página de produto na lista de templates.
 4. Na propriedade `skuPrice`, adicione a variável `paymentSystemId` com o ID do meio de pagamento desejado.
 
-![Screenshot 2020-12-18 Criar preço à vista](https://images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
+![Screenshot 2020-12-18 Criar preço à vista](//images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
 
 6. Após a alteração, clique em __Save Template__ no campo superior para salvar.
 
diff --git a/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md b/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
index 786a467f6..78338ee11 100644
--- a/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar política comercial para marketplace'
 id: tutorials_404
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T22:06:38.350Z
-updatedAt: 2022-12-08T17:30:09.288Z
-publishedAt: 2022-12-08T17:30:09.288Z
+updatedAt: 2024-06-14T14:19:35.130Z
+publishedAt: 2024-05-15T00:18:56.253Z
 firstPublishedAt: 2017-04-27T23:03:23.796Z
 contentType: tutorial
 productTeam: Channels
@@ -30,21 +30,24 @@ Confira como políticas comerciais podem ser configuradas nos seguintes módulos
 
 Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via ticket em [*Suporte*](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
 
-A contratação de política comercial adicional para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
+A contratação de política comercial adicional para integrar com um [conector certificado](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
+
+<div class=alert alert-warning>
+Se a mesma política comercial for usada em um conector certificado e em um conector parceiro, não há isenção de taxas.</div>
 
 ## Configurações da Loja 
 Criar uma nova política comercial é o primeiro passo para definir as condições aplicadas a cada marketplace em que um seller atua. Sellers podem criar múltiplas políticas comerciais, ou aplicar a mesma política em mais de um marketplace. 
 
 Essa configuração é feita no módulo Configurações da Loja, na aba Políticas comerciais. É necessário [criar uma nova política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) quando as configurações de catálogo, preços, promoções, logística e pagamentos forem diferentes entre os marketplaces em que os sellers vendem seus produtos. 
 
-![PT Add Politica comercial](https://images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/a9be66bd901619b68280ad8ceec4d552/PT_Add_Politica_comercial.jpg)
+![PT Add Politica comercial](//images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/a9be66bd901619b68280ad8ceec4d552/PT_Add_Politica_comercial.jpg)
 
 ## Gerenciamento de Pedidos
 Após a criação de uma política comercial, é preciso associá-la a cada marketplace em que o seller vende produtos ao cadastrar [afiliados](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). É assim que sellers identificam qual política comercial está atuando em cada marketplace. Se sua loja vende produtos em três marketplaces diferentes, é necessário criar três afiliados, cada um representando um marketplace. 
 
 Essa ação é feita na aba *Configurações* do módulo *Gerenciamento de Pedidos* da sua loja ao cadastrar afiliados. Mesmo criando várias, é importante notar que somente uma política comercial atuará no marketplace por vez. 
 
-![PT Afiliado](https://images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/3004320aeb44502e68cceac90c472d6c/PT_Afiliado.jpg)
+![PT Afiliado](//images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/3004320aeb44502e68cceac90c472d6c/PT_Afiliado.jpg)
 
 *No exemplo acima o afiliado "Amazon" está vinculado à política comercial "1".* 
 
@@ -58,7 +61,7 @@ Essa configuração é feita no módulo de *Promoções* em todas as [promoçõe
 
 Se nenhuma política comercial for selecionada, a promoção estará disponível em todos os canais de venda.
 
-![PT Promoções Politica Comercial](https://images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/8d011fccf8af4cf5bc088cbd77a7b914/PT_Promo____es_Politica_Comercial.jpg)
+![PT Promoções Politica Comercial](//images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/8d011fccf8af4cf5bc088cbd77a7b914/PT_Promo____es_Politica_Comercial.jpg)
 
 *No exemplo acima, a promoção será aplicada somente a pedidos das políticas comerciais "Marketplace-BRL" e "Argentina-ARS", onde a loja atua como seller. A promoção não estará disponível no storefront da loja VTEX.* 
 
@@ -67,7 +70,7 @@ Sellers que transacionam o pagamento das vendas de seus produtos em um marketpla
 
 Essa configuração é feita no módulo de *Pagamentos*, ao [criar uma condição especial](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456) e ao associá-la às políticas comerciais desejadas. Se nenhuma restrição é feita, a política comercial será aplicada em todos os canais de venda. 
 
-![PT Pagamento Politica comercial](https://images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/bd8e088166a9fa0f1fabc0c410f18409/PT_Pagamento_Politica_comercial.jpg)
+![PT Pagamento Politica comercial](//images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/bd8e088166a9fa0f1fabc0c410f18409/PT_Pagamento_Politica_comercial.jpg)
 
 *No exemplo acima, a condição de pagamento está associada à política comercial "Marketplace". Isso torna a condição de pagamento disponível apenas aos canais de venda associados a essa política comercial.*
 
@@ -80,7 +83,7 @@ Essa configuração é feita no *Catálogo* da VTEX, ao [cadastrar produtos](htt
 Não é recomendado vincular políticas comerciais a coleções, para determinar o sortimento de produtos, sobretudo em casos de marketplaces externos à VTEX. Quando um produto é retirado da coleção da política comercial, o sistema VTEX não avisa o marketplace dessa atualização, fazendo com que o produto continue disponível no marketplace. 
 </div>  
 
-![Pt Catálogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/63eea6b22e93fa4e94840a5c9a88db94/Pt_Cat__logo_Politica.jpg)
+![Pt Catálogo Politica](//images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/63eea6b22e93fa4e94840a5c9a88db94/Pt_Cat__logo_Politica.jpg)
 
 *No exemplo acima, o produto estará disponível apenas para canais de venda utilizando as políticas comerciais "Carrefour" e "Marketplace".* 
 
@@ -92,7 +95,7 @@ Essa configuração é feita no módulo de *Preços* da VTEX, utilizando políti
 - [Regras de preço](https://help.vtex.com/pt/tutorial/configurar-regra-de-preco-para-politica-comercial--5LQMLwcUcEGCWK6SMI6cEM): para determinar um markup para categorias e marcas específicas
 - [Preços fixos](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy): para diferenciar preços em produtos específicos
 
-![PT Regra de preço](https://images.ctfassets.net/alneenqid6w5/lBoM4E1z07YLbsZfJhP1V/6344b89e4698e8834febd6dcbc4374cc/PT_Regra_de_pre__o.jpg)
+![PT Regra de preço](//images.ctfassets.net/alneenqid6w5/lBoM4E1z07YLbsZfJhP1V/6344b89e4698e8834febd6dcbc4374cc/PT_Regra_de_pre__o.jpg)
 
 *No exemplo acima, a regra de preço aplicou um markup à política comercial "Marketplace" para produtos dentro da categoria "Fera-Fashion*. 
 
@@ -102,10 +105,10 @@ Sellers podem configurar [rotas logísticas](https://help.vtex.com/pt/tracks/log
 
 Ambas configurações são realizadas no módulo *Estratégia de Envio*. Ao criar uma [doca](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj), é preciso indicar quais políticas comerciais ela atenderá. Isso torna as políticas de envio associadas a essa doca disponíveis para as políticas comerciais vinculadas. Em seguida, é necessário relacionar o [estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque) desejado a uma doca, para tornar seu inventário disponível para todas as políticas comerciais associadas à doca. 
 
-![PT Doca Politica](https://images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/2f40ca4bb8723eff8218e24ad2b81c8f/PT_Doca_Politica.jpg)
+![PT Doca Politica](//images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/2f40ca4bb8723eff8218e24ad2b81c8f/PT_Doca_Politica.jpg)
 *No exemplo acima, a doca está associada à política comercial "Marketplace", que serão atendidas pela transportadora "Transportadora A".*
 
-![PT Estoque Politica](https://images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/634a9269e2b94cc8102fe4037f8b7136/PT_Estoque_Politica.jpg)
+![PT Estoque Politica](//images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/634a9269e2b94cc8102fe4037f8b7136/PT_Estoque_Politica.jpg)
 *No exemplo acima, o estoque está associado a "Doca A", portanto esse será o estoque que as políticas comerciais vinculadas à "Doca A" utilizarão.* 
 
 ## Integrações
@@ -113,7 +116,7 @@ As políticas comerciais também são aplicadas em todas as integrações em que
 
 Essas [integrações](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#vender-em-marketplace) são feitas na aba de *Configurações* do módulo *Integrações*. Cada canal costuma requerer condições comerciais específicas, porém, é possível que canais diferentes compartilhem da mesma política comercial. 
 
-![PT integracao politica](https://images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/50d0f55f7ed3ab4c1a776224151fb6bf/PT_integracao_politica.jpg)
+![PT integracao politica](//images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/50d0f55f7ed3ab4c1a776224151fb6bf/PT_integracao_politica.jpg)
 
 *No exemplo acima, a política comercial "Marketplace" está aplicada na integração com o Google Shopping.*
 
diff --git a/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md b/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md
index 84a909410..565ffc9af 100644
--- a/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md
+++ b/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md
@@ -3,8 +3,8 @@ title: 'Configurar regra de preço para política comercial'
 id: 5LQMLwcUcEGCWK6SMI6cEM
 status: PUBLISHED
 createdAt: 2018-03-19T17:49:25.791Z
-updatedAt: 2023-03-29T20:00:47.266Z
-publishedAt: 2023-03-29T20:00:47.266Z
+updatedAt: 2023-08-21T17:23:00.178Z
+publishedAt: 2023-08-21T17:23:00.178Z
 firstPublishedAt: 2018-03-19T18:26:04.279Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,7 +25,7 @@ Por padrão, o __preço base__ cadastrado para um produto é aplicado para todas
 
 Para criar uma regra de preço específica para uma política comercial, siga os passos abaixo:
 
-1. No Admin VTEX, acesse *Preços > Regras de preços*, ou digite *Regras de preços* na barra de busca no topo da página.
+1. No Admin VTEX, acesse **Preços > Regras de preços**, ou digite **Regras de preços** na barra de busca no topo da página.
 2. Clique em `Nova regra`.
 3. No campo __Política comercial__, escolha a política comercial desejada.
 4. Escolha se a regra será aplicada a __todos os produtos__ desta política ou __apenas a categorias e marcas escolhidas__.
diff --git a/docs/tutorials/pt/configuring-a-registered-boleto.md b/docs/tutorials/pt/configuring-a-registered-boleto.md
index d4ed65841..b65e4b4a8 100644
--- a/docs/tutorials/pt/configuring-a-registered-boleto.md
+++ b/docs/tutorials/pt/configuring-a-registered-boleto.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto registrado '
 id: frequentlyAskedQuestions_2867
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:46:00.197Z
-updatedAt: 2020-11-24T13:14:10.947Z
-publishedAt: 2020-11-24T13:14:10.947Z
+updatedAt: 2024-03-18T18:09:27.673Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:08:27.705Z
 contentType: tutorial
 productTeam: Financial
@@ -26,22 +26,13 @@ A VTEX se adequou a essa determinação e, atualmente, já existem algumas manei
 - [Boleto Santander](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-santander--67siNqkC7mcgy2GWUYimaa)
 - [Boleto Itaú](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-itau-itau-registrado--6MEHf1oDTOkuWM2CaYi4gu)
 - [Itaú Shopline](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq)
-- [Bradesco Registrado](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-bradesco--bbnXBjvKOkWYiOosmASiA)
+- [Boleto Bradesco Registrado](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-bradesco--bbnXBjvKOkWYiOosmASiA)
 
 Além disso, a VTEX tem integração automática para boletos registrados Bradesco e Itaú Shopline. Contudo, para boletos gerados sem uma adquirência, a conciliação é feita por meio de um arquivo (.RET). 
 
 Cada cliente deve conseguir os arquivos com seus respectivos bancos. Nesse caso específico, Itaú Registrado e Santander. Ressaltamos que esses arquivos precisam, necessariamente, seguir o padrão estabelecido pela Febraban. 
 
-Para outros bancos, é necessário usar um dos seguintes gateways:
-
-- Braspag
-- PagSeguro Transparente
-- Mundipagg
-- Moip
-- MercadoPago Transparente
-- Pagar.Me
-- CieloV3
-- Adyen
+Para outros bancos, é necessário usar um dos gateways disponíveis no Admin de sua loja (ex. Braspag, PagSeguro Transparente, CieloV3, entre outros).
 
 Os custos do boleto registrado são diferentes do boleto tradicional e variam de acordo com sua negociação junto ao banco. Fique atento para planejar e controlar sua margem.
 
@@ -54,5 +45,3 @@ A criação desse número pela VTEX garante a particularidade de cada boleto e d
 ## Artigos relacionados
 
 - [Como configurar afiliação de gateway](/pt/tutorial/afiliacoes-de-gateway/)
-- [Como configurar PagSeguro transparente](/pt/tutorial/como-configurar-o-pagseguro-sem-redirect-transparente/)
-- [Configurar boleto registrado Itaú](/pt/tutorial/configurar-boleto-registrado-itau)
diff --git a/docs/tutorials/pt/configuring-a-santander-registered-boleto.md b/docs/tutorials/pt/configuring-a-santander-registered-boleto.md
index ad43158db..4e92772c2 100644
--- a/docs/tutorials/pt/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/pt/configuring-a-santander-registered-boleto.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto registrado Santander'
 id: 67siNqkC7mcgy2GWUYimaa
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-12-04T19:04:02.215Z
-updatedAt: 2023-03-30T16:12:20.970Z
-publishedAt: 2023-03-30T16:12:20.970Z
+updatedAt: 2024-03-18T18:03:25.298Z
+publishedAt: 
 firstPublishedAt: 2019-01-25T17:15:35.225Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-boleto-registrado-santander
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 O boleto bancário é uma das formas de pagamento mais populares no Brasil. Apesar de não apresentar a mesma praticidade dos cartões de crédito, muitos compradores a consideram uma opção mais segura e acessível para adquirir bens de valor elevado. Dessa maneira, disponibilizar o boleto bancário é uma boa opção para aumentar as vendas no e-commerce.
 
 Para utilizar o Boleto Registrado Santander na sua loja, siga as instruções abaixo.
@@ -61,10 +63,11 @@ Após o recebimento do seu certificado digital, o Santander iniciará a próxima
 
 Para fazer a configuração na VTEX, tenha em mãos os dados fornecidos pelo banco na contratação do serviço, seu certificado digital no formato PFX e a senha do certificado e siga as instruções abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Acesse a aba **Afiliações de Gateways** e clique no ícone <img src="https:https://images.ctfassets.net/alneenqid6w5/4oUB04BWtdR3i6mYdYISFX/a47b099664e386416b0962c13ee00ddc/image1.png" alt="Botão verde de afiliação" style="width: 23px;" /> e escolha o conector __Boleto Santander__.
-3. Escolha o __Nome da afiliação__ que preferir e selecione o modo de __Teste__.
-4. Preencha as configurações da tabela abaixo com os dados da sua empresa, as configurações do boleto, os dados fornecidos pelo Santander e seu certificado digital. Não se esqueça de __Salvar__ ao concluir o preenchimento.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BankInvoiceSantander__ na barra de busca e clique sobre o nome do provedor.
+4. Escolha o __Nome da afiliação__ que preferir e selecione o modo de __Teste__.
+5. Preencha as configurações da tabela abaixo com os dados da sua empresa, as configurações do boleto, os dados fornecidos pelo Santander e seu certificado digital. Não se esqueça de __Salvar__ ao concluir o preenchimento.
 
     | | |
     |-------------------------|---------------------------------------------------------------------------------------------------|
@@ -83,10 +86,10 @@ Se a geração de boletos em ambiente de teste for validada pelo Santander, voc
 
 Para finalizar a configuração do boleto registrado Santander e disponibilizar este meio de pagamento na sua loja, você deve fazer um último teste:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Acesse a aba **Afiliações de Gateways** e escolha a afiliação configurada na etapa de homologação do __Boleto Santander__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Digite o nome __BankInvoiceSantander__ na barra de busca e clique sobre o nome do provedor. 
 3. Selecione o modo de __Live/Produção__ e clique no botão __Salvar__.
-4. Acesse *Condições de pagamento* e clique na condição configurada na etapa de homologação do __Boleto Santander__. Ative-a para que a opção de Boleto Bancário possa aparecer no checkout da sua loja
+4. Acesse *Condições de pagamento* e clique na condição configurada na etapa de homologação do __Boleto Santander__. Ative-a para que a opção de Boleto Bancário possa aparecer no checkout da sua loja.
 5. Faça uma compra de teste, escolhendo o Boleto Bancário no checkout da sua loja. __Não se esqueça de desativar a condição de pagamento quando terminar__.
 6. Pague o boleto da compra e verifique se o valor correspondente é creditado na sua conta, através do Internet Banking.
 
diff --git a/docs/tutorials/pt/configuring-affiliates.md b/docs/tutorials/pt/configuring-affiliates.md
index 6a4e0c89a..852a23545 100644
--- a/docs/tutorials/pt/configuring-affiliates.md
+++ b/docs/tutorials/pt/configuring-affiliates.md
@@ -3,8 +3,8 @@ title: 'Configurar afiliado'
 id: tutorials_187
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:31.422Z
-updatedAt: 2023-03-29T18:05:11.905Z
-publishedAt: 2023-03-29T18:05:11.905Z
+updatedAt: 2024-01-08T18:13:15.897Z
+publishedAt: 2024-01-08T18:13:15.897Z
 firstPublishedAt: 2017-04-27T23:00:46.992Z
 contentType: tutorial
 productTeam: Channels
@@ -15,9 +15,9 @@ legacySlug: como-configurar-afiliado
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-Só é necessário fazer o cadastro de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) se ele estiver atuando como seller de um marketplace, pois o seller cria um afiliado para identificar o marketplace.
+Na VTEX, o [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) é um código que identifica o marketplace para o seller. O [seller VTEX](https://help.vtex.com/pt/tutorial/integrating-with-marketplace/#sendo-seller-vtex) precisa configurar um código de afiliado para poder integrar com um [marketplace VTEX](https://help.vtex.com/pt/tutorial/integrating-with-marketplace/#ser-um-marketplace-vtex), e essa configuração só é necessária quando o marketplace e o seller integrados são ambos lojas VTEX. 
 
-Essa configuração só deve ser feita para integrações onde o marketplace e o seller são lojas VTEX ou [quando o marketplace não é loja VTEX e não possui configuração pelo módulo de Integrações](/pt/tutorial/integrando-com-marketplace/). Nesses casos, o afiliado é criado automaticamente.
+Quando o marketplace não é uma loja VTEX (como em [integrações externas](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplace-externo)), ou quando a loja integra com um [marketplace certificado](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-certificados) (como Amazon ou Mercado Livre), o código do afiliado é criado automaticamente pela plataforma.
 
 ## Como configurar
 
diff --git a/docs/tutorials/pt/configuring-banners.md b/docs/tutorials/pt/configuring-banners.md
new file mode 100644
index 000000000..708e9a6d2
--- /dev/null
+++ b/docs/tutorials/pt/configuring-banners.md
@@ -0,0 +1,70 @@
+---
+title: 'Configurar Banners'
+id: 3AdnZhxAhgmlxJjpa02Svc
+status: PUBLISHED
+createdAt: 2024-06-27T16:32:24.435Z
+updatedAt: 2024-06-27T16:33:49.674Z
+publishedAt: 2024-06-27T16:33:49.674Z
+firstPublishedAt: 2024-06-27T16:33:39.573Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configurar-banners
+locale: pt
+legacySlug: configurar-banners
+subcategory: z6qcw06Z38YDu1fOcu9Jn
+---
+
+Para configurar um banner, siga os seguintes passos:
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Clique em **Banners**.
+3. Clique em <i class="fas fa-plus"></i> `Novo`.
+4. Preencha os [campos referentes ao banner](#campos-de-cadastro-do-banner).
+5. Para finalizar, clique em `Salvar`.
+
+Depois de realizar as configurações do banner, você deve adicioná-lo a uma página da sua loja. Para isso, siga os passos do guia [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner).
+
+<div class = "alert alert-info">
+  <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
+</div>
+
+![banner-form-pt](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
+
+## Campos de cadastro do banner
+
+Para cadastrar o banner, é necessário preencher os seguintes campos:
+
+### Informações gerais
+
+* **Nome**: nome do banner cadastrado.
+* **Posição**: área que o banner aparecerá na página de resultado de busca. Os banners podem ser alocados em quatro áreas distintas na página do site. Essa disposição fica a critério do lojista, dependendo da opção selecionada nesse campo ou definido via [blocks no store-theme](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner#props).
+
+### Tipo
+
+* **Tipo do banner**: conteúdo do banner que será criado. O banner pode ser um HTML ou uma URL de imagem:
+    * **HTML**: o gestor pode adicionar no campo HTML mídias, vídeos do YouTube ou imagens, e linhas de código, como JavaScript.
+    * **Image**: o sistema pede a URL da imagem que será utilizada e o link de destino do banner.
+        * URL da imagem
+        * Link de destino
+* **Fuso horário**: fuso horário seguido pelos horários configurados no banner.
+* **Data de início**: data que define o início da disponibilidade do banner.
+* **Horário de início**: horário que define o início da disponibilidade do banner.
+* **Data de término**: data que define o término da disponibilidade do banner - o que permite o gestor agendar campanhas futuras, facilitando o seu controle.
+* **Horário de término**: horário que define o término da disponibilidade do banner.
+* **Idiomas:** idiomas aos quais o banner será aplicado. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+### Regras de ativação 
+
+**Regras de ativação** é um conjunto de condições de termos ou filtros que serão aplicados a cada pesquisa realizada. É necessário ter pelo menos uma condição cadastrada, seja por termo ou por filtro.
+
+Clique em <i class="fa-solid fa-link"></i> `Preencher a partir de uma URL` para adicionar a URL da página de busca em as regras de ativação serão aplicadas. 
+
+![banner-url-pt](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
+
+Clique em <i class="fas fa-plus"></i> `Adicionar condição` para criar uma regra. Elas podem ser dos seguintes tipos:
+
+* **Termo**: palavra pesquisada pelo cliente que será relacionada à regra.
+* **Filtro**: atributo selecionável já definido que restringe os resultados de busca. Aqui é possível selecionar categorias, departamentos e subcategorias.
+
+Clique em `Limpar Regras` para apagar todas as regras cadastradas.
diff --git a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
new file mode 100644
index 000000000..9701b8e30
--- /dev/null
+++ b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -0,0 +1,68 @@
+---
+title: 'Configurando a importação em massa de dados sobre organizações e centros de custos '
+id: 41FwcZHF3GctzKcgyKGaoF
+status: PUBLISHED
+createdAt: 2024-04-25T11:45:15.945Z
+updatedAt: 2024-05-21T14:04:56.238Z
+publishedAt: 2024-05-21T14:04:56.238Z
+firstPublishedAt: 2024-04-29T18:38:46.485Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configurando-a-importacao-em-massa-de-organizacoes-e-centros-de-custo
+locale: pt
+legacySlug: configurando-a-importacao-em-massa-de-organizacoes-e-centros-de-custo
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+A importação em massa de dados permite a simplificação do processo de atualização e manutenção de informações para organizações compradoras, seus usuários (membros) e centros de custo.
+
+<div class="alert alert-warning">
+Antes de configurar a funcionalidade de importação em massa, é necessário ter instalado em sua loja o aplicativo <a href="https://developers.vtex.com/docs/apps/vtex.b2b-suite">B2B Suite</a>. 
+</div>
+
+Veja abaixo como realizar a importação em massa de dados na plataforma VTEX:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+
+2. Na aba Organizações, clique no botão **Novo**, e selecione Importar em massa. Clique no botão **Enviar** e selecione seu arquivo **XLSX**, ou arraste e solte o arquivo na área tracejada. O arquivo importado deve ser menor que 50 MB.
+
+<div class = "alert alert-info">
+Caso necessário, baixe um arquivo modelo clicando em VTEX file template no rodapé da janela de importação e preencha os dados de importação.
+</div>
+
+<ol start="3">
+	<li>Após a plataforma realizar uma verificação no arquivo importado e não indicar erros, clique em Importar.</li>
+</ol>
+
+<div class = "alert alert-info">
+  Caso a plataforma encontre algum tipo de erro, verifique a seção <b>Erros de importação</b>.
+</div>
+
+<ol start="4">
+	<li>Após o processo de importação ser concluído, você pode clicar em  Exibir detalhes de importação para acessar o relatório de importação.</li>
+</ol>
+
+![Importação em massa - PT](//images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/5957afd8831ee93e55609e2b55b5b552/Bulk_import_vers_o_original-PT.gif)
+
+# Erros de importação
+
+Durante o processo de importação, o sistema realizará uma verificação do arquivo para evitar erros. Em caso de ocorrência de erros, você será notificado por e-mail e receberá um alerta na tela.
+
+Para obter uma visão detalhada dos problemas encontrados, siga os passos abaixo:
+
+1. Clique em Exibir detalhes de importação e acesse o relatório de erros correspondente.
+
+2. Faça o download da planilha revisada clicando no botão **Baixar XLSX revisado**. Nela você encontra os locais com os erros.
+
+3. Após corrigir os erros, você pode reiniciar o processo de importação, fazendo upload do arquivo corrigido novamente.
+
+<div class = "alert alert-info">
+ Certifique-se de carregar apenas o arquivo contendo as correções dos erros previamente identificados para garantir uma importação bem-sucedida.
+</div>
+
+![Bulk import - PT](//images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/4ebe7b4b5b1c0d5b2d7feb36134d9a5e/Bulk_import_vers_o_error-gif-PT.gif)
+
+# Importação via API
+
+A importação de informações também pode ser realizada por meio da [API Bulk import](https://developers.vtex.com/docs/api-reference/buyer-organizations?endpoint=overview), permitindo a realização das operações de validação e importação de arquivos, acompanhamento do progresso e resultado da importação.
diff --git a/docs/tutorials/pt/configuring-cargo-splitting.md b/docs/tutorials/pt/configuring-cargo-splitting.md
index 3ae6fabd2..5e49fe3a7 100644
--- a/docs/tutorials/pt/configuring-cargo-splitting.md
+++ b/docs/tutorials/pt/configuring-cargo-splitting.md
@@ -3,8 +3,8 @@ title: 'Configurando a divisão de carga'
 id: tutorials_109
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:24.631Z
-updatedAt: 2023-03-28T14:07:28.837Z
-publishedAt: 2023-03-28T14:07:28.837Z
+updatedAt: 2024-04-30T14:30:11.052Z
+publishedAt: 2024-04-30T14:30:11.052Z
 firstPublishedAt: 2017-04-27T23:00:42.951Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,9 @@ legacySlug: como-funciona-a-divisao-de-carga
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
-A divisão de carga é a configuração que permite que uma compra seja dividida em várias entregas quando o cálculo total de peso ultrapassar o limite da transportadora.
+A divisão de carga é a configuração que permite que uma compra seja dividida em várias entregas quando o cálculo total de peso ultrapassar o limite definido na política de envio.
 
-Essa configuração é muito importante pois, caso a divisão de carga não seja permitida, pode impossibilitar o fechamento de uma compra. Isso caso o a soma do peso de todos os produtos do carrinho for maior que o limite máximo de peso cadastrado nas transportadoras.
+Essa configuração é muito importante pois, caso a divisão de carga não seja permitida, pode impossibilitar o fechamento de uma compra se a soma do peso de todos os produtos do carrinho for maior que o limite máximo de peso cadastrado nas políticas de envio.
 
 ![](//images.contentful.com/alneenqid6w5/g0pDcU4oy4WaoQ0e8C0Im/d349266bd8ab36c137894b4b8cb0374d/divisaoCarga.png)
 
diff --git a/docs/tutorials/pt/configuring-cielo-acquirer.md b/docs/tutorials/pt/configuring-cielo-acquirer.md
index b884bbddb..9712c398a 100644
--- a/docs/tutorials/pt/configuring-cielo-acquirer.md
+++ b/docs/tutorials/pt/configuring-cielo-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar adquirente Cielo'
 id: 3avjZ7q65WcM02K8K0eeWu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-05-02T19:02:05.427Z
-updatedAt: 2023-03-21T18:55:28.551Z
-publishedAt: 2023-03-21T18:55:28.551Z
+updatedAt: 2023-09-19T14:27:20.410Z
+publishedAt: 
 firstPublishedAt: 2018-05-02T19:49:35.201Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md b/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
index 9fe2151c4..e695ff3c5 100644
--- a/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar antifraude ClearSale v3'
 id: 2pPORygesIqQOa6cIG6agg
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-10-30T14:10:20.822Z
-updatedAt: 2021-12-15T21:23:21.984Z
-publishedAt: 2021-12-15T21:23:21.984Z
+updatedAt: 2024-04-24T18:52:20.944Z
+publishedAt: 2024-04-24T18:49:44.223Z
 firstPublishedAt: 2017-10-30T14:26:53.089Z
 contentType: tutorial
 productTeam: Financial
@@ -15,22 +15,32 @@ legacySlug: configurar-antifraude-clearsale-v3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Para habilitar a afiliação do antifraude ClearSale v3, você precisa [adicionar a afiliação de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444) na seção de Pagamentos, escolhendo a opção **ClearSaleV3**. A configuração da afiliação do antifraude ClearSale v3 contém os seguintes campos:
-
-- **Login:** Login.
-- **Password:** Senha.
-- **Custom SLA em minutos (opcional):** O tempo que o ClearSale terá para processar a análise de fraude.
-- **Produto (opcional):** Valor numérico. Correspondente ao ID do produto contratado na ClearSale.
-- **Transaction currency**: Moeda.
-- **Observation (opcional):** Texto para enviar à ClearSale como observação.
-- **Enviar transações autenticadas?**: Possui as opções **Sim** e **Não**.  Transações autenticadas são aquelas onde todos os pagamentos foram autenticados com senha no programa 3DSecure.
+Na VTEX, é possível realizar a integração com o [antifraude](http://help.vtex.com/pt/tutorial/como-configurar-antifraude) ClearSaleV3. Por meio deste sistema, é possível aumentar o nível de segurança em transações de pagamento realizadas em sua loja utilizando análises de risco que identificam possíveis fraudes.
+
+Para configurar o ClearSaleV3, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __ClearSaleV3__ na barra de busca e clique sobre o nome do provedor.
+4. Caso deseje modificar o nome de identificação a ser exibido para o antifraude ClearSaleV3 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+5. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+6. Preencha as informações abaixo conforme suas configurações no ClearSale:
+<br>
+<ul>
+<br>
+  <li><b>Login</b>: login.</li>
+  <li><b>Password</b>: senha.</li>
+  <li><b>SLA personalizado em minutos (opcional)</b>: período em que o ClearSale terá para processar a análise de fraude.</li>
+  <li><b>Produto (opcional)</b>: valor numérico. Correspondente ao ID do produto contratado na ClearSale.</li>
+  <li><b>Transaction currency</b>: moeda na qual a transação é realizada.</li>
+  <li><b>Observation (opcional)</b>: texto para enviar ao ClearSale como observação.</li>
+  <li><b>Enviar transações autenticadas?</b>: indica se as transações de pagamento devem ser autenticadas com senha no programa 3DSecure.</li>
+</ul>
+7. Clique em `Salvar`.
 
 <div class="alert alert-info">
-A documentação da ClearSale sobre <a href="https://api.clearsale.com.br/docs/finger-print" target="_blank">FingerPrint</a> explica o script abaixo em detalhes.
-</div>
-
-<div class="alert alert-warning">
-Se você deseja configurar o antifraude <strong>ClearSale T</strong>, basta seguir <a href="http://help.vtex.com/pt/tutorial/como-configurar-antifraude">este passo a passo</a>.
+<p>Caso possua uma aplicação mobile que utilize as APIs da VTEX na finalização da compra é necessário realizar a implementação da coleta de dados do fingerprint a serem enviados para Clearsale, de acordo com a plataforma utilizada pelo aplicativo. Saiba mais em <a href="https://api.clearsale.com.br/docs/behavior-analytics" target="_blank">Clearsale Behavior Analytics</a>.</p>
+<p>Com a implementação do SDK é necessário coletar o valor de <span class="bg-muted-4">sessionId</span> e enviá-lo no campo <span class="bg-muted-4">deviceFingerprint</span> via <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">API na criação do pagamento</a>.</p>  
 </div>
 
 ## Criando a tag do Google Tag Manager
diff --git a/docs/tutorials/pt/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md b/docs/tutorials/pt/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
index f553bc33f..dbd1e0516 100644
--- a/docs/tutorials/pt/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
+++ b/docs/tutorials/pt/configuring-discounts-for-orders-prepaid-in-full-on-google-shopping.md
@@ -3,8 +3,8 @@ title: 'Configurar desconto de preço à vista para Google Shopping'
 id: 40K3R5d4NogMvCzIWdWt3e
 status: PUBLISHED
 createdAt: 2020-12-18T19:17:16.033Z
-updatedAt: 2023-03-30T16:56:23.457Z
-publishedAt: 2023-03-30T16:56:23.457Z
+updatedAt: 2024-01-19T16:37:47.493Z
+publishedAt: 2024-01-19T16:37:47.493Z
 firstPublishedAt: 2021-05-04T20:06:46.945Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,7 +25,12 @@ Para configurar o desconto de preço à vista para o Google Shopping é preciso
 4. Clique no template da sua página de produto na lista de templates.
 5. No componente `richSnippets`, você deve adicionar o parâmetro `paymentSystemId` com o valor do meio de pagamento desejado.
 
-![Screenshot 2020-12-18 Criar preço à vista para Google Shopping](https://images.ctfassets.net/alneenqid6w5/3cZKIpG2uAhDmFTJDslHZk/1bd7628049b5c5b7326df8044ac673f2/Screenshot_2020-12-18_Criar_pre__o____vista_para_Google_Shopping.png)
+```
+<body id="product-page">
+    <!--  Component: richSnippets -->
+    <vtex.cmc:productRichSnippets showGoogle="1" paymentSystemId="6"/>
+    <!-- /Component: richSnippets -->
+```
 
 6. Após a alteração, clique em __Save Template__ no campo superior para salvar.
 
diff --git a/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md b/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md
index 3e442dc83..8bc8a3e8e 100644
--- a/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md
+++ b/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md
@@ -35,7 +35,7 @@ _classe.atributo_ são obtidos do JSON. No MessageCenter exibimos o JSON espec
 **HTML do template**
 `<strong>{{_accountInfo.HostName}}</strong> => lojavirtual`
 
-![exemplohtml](https://images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
+![exemplohtml](//images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
 
 Para o exemplo acima, uma loja seller pode possuir um hostname diferente de uma loja marketplace. Sempre leve em conta as suas configurações!
 
diff --git a/docs/tutorials/pt/configuring-kushki-gateway.md b/docs/tutorials/pt/configuring-kushki-gateway.md
index 20baf822b..5bcb57079 100644
--- a/docs/tutorials/pt/configuring-kushki-gateway.md
+++ b/docs/tutorials/pt/configuring-kushki-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway Kushki'
 id: 69VC8nQMkEE0yu8oIyG2wG
 status: PUBLISHED
 createdAt: 2018-04-24T15:50:00.468Z
-updatedAt: 2023-03-29T00:41:16.269Z
-publishedAt: 2023-03-29T00:41:16.269Z
+updatedAt: 2024-01-23T17:48:58.465Z
+publishedAt: 2024-01-23T17:48:58.465Z
 firstPublishedAt: 2018-04-24T19:47:19.057Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,20 @@ legacySlug: configurar-gateway-kushki
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A Kushki é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) e atuação focada na América Latina.
+A Kushki é um [gateway](https://help.vtex.com/pt/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk) com certificação [PCI](https://help.vtex.com/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E) e atuação focada na América Latina.
 
 Para configurar a Kushki, siga os passos abaixo:
 
-## Configurar afiliação de gateway Kushki
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Kushkiv2__.
-4. Preencha os campos com os __dados__ fornecidos pela Kushki.
-5. O campo __Application Key__ será preenchido com a __chave privada__ da Kushki.
-6. O campo __Application Token__ será preenchido com a __chave pública__ da Kushki.
-7. Clique no botão __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Kushkiv2__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Chave de aplicação__ e __Token de aplicação__ insira as informações que foram fornecidas pela Kushki.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor iugu na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Clique em `Salvar`.
 
-Depois de concluir essa configuração, você deverá criar as credenciais da VTEX para configurar a afiliação Kushki na sua loja. Confira as instruções do [guia de autenticação](https://developers.vtex.com/docs/getting-started-authentication "guia de autenticação") no nosso Developer Portal.   
+Para configurar os métodos de pagamento a serem processados pela Kushki, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, a Kushki vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ela estará disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com a Kushki). Para saber como definir condições de pagamento, acesse [este artigo](/pt/tutorial/condicoes-de-pagamento).
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, Kushki pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento.
diff --git a/docs/tutorials/pt/configuring-login-with-facebook-and-google.md b/docs/tutorials/pt/configuring-login-with-facebook-and-google.md
index e33010571..2d137ccbf 100644
--- a/docs/tutorials/pt/configuring-login-with-facebook-and-google.md
+++ b/docs/tutorials/pt/configuring-login-with-facebook-and-google.md
@@ -3,42 +3,48 @@ title: 'Configurar login com Facebook e Google'
 id: tutorials_513
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:01.743Z
-updatedAt: 2023-02-08T14:32:57.255Z
-publishedAt: 2023-02-08T14:32:57.255Z
+updatedAt: 2023-10-20T19:35:59.221Z
+publishedAt: 2023-10-20T19:35:59.221Z
 firstPublishedAt: 2017-04-27T23:03:27.844Z
 contentType: tutorial
 productTeam: Identity
 author: authors_84
-slug: integracao-google-e-facebook-para-login
+slug: configurar-login-com-facebook-e-google
 locale: pt
 legacySlug: integracao-google-e-facebook-para-login
 subcategory: 14V5ezEX0cewOMg0o0cYM6
 ---
 
-Na VTEX, não é necessário criar uma conta ou logar para fazer uma compra. No entanto, caso o cliente queira efetuar alguma alteração nos dados informados durante a primeira compra, é necessário que ele  comprove a posse do e-mail em questão.
+Na VTEX, não é necessário criar uma conta ou fazer login para realizar uma compra. No entanto, caso o cliente queira efetuar alguma alteração nos dados informados durante a primeira compra, é necessário que ele comprove a posse do email em questão.
 
-Nativamente, a plataforma oferece opções de login com Email & Senha e, também, Login com Código de Acesso enviado para o email do cliente. Também oferecemos integrações opcionais nativas com Google e Facebook, que necessitam ser configuradas.
+Nativamente, a plataforma oferece opções de login com email e senha e login com código de acesso enviado para o email do cliente. Também oferecemos integrações opcionais nativas com Google e Facebook, que necessitam ser configuradas. Este guia explica como configurar esses provedores de login:
 
-## Faça o registro junto aos provedores
+1. [Obter credenciais junto aos provedores](#obter-credenciais-junto-aos-provedores)
+2. [Configurar login com provedores](#configurar-login-com-provedores)
+3. [Validar a configuração](#validar-a-configuracao)
+
+## Obter credenciais junto aos provedores
 
 Antes de configurar nossa integração de login com o Google e Facebook, é necessário criar credenciais de OAuth 2.0 (protocolo utilizado para integração) nesses serviços. Para fazer isso, siga as instruções nos artigos indicados abaixo:
 
-- [Facebook](/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-facebook)
-- [Google](/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google)
+- [Facebook](https://help.vtex.com/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-facebook--3R7rzXWG1GswWOIkYyy8SO)
+- [Google](https://help.vtex.com/pt/tutorial/cadastrar-client-id-e-client-secret-para-login-com-google--1lBgDmetUM4goie6mYEOK6)
 
-## Configure na sua loja
+## Configurar login com provedores
 
-Após a configuração no Facebook e/ou Google, é preciso configurar na sua loja a opção de login por esses dois provedores. Nos dois casos, você precisará ter em mãos o `Client ID` e o `Client Secret` cadastrados.
+Após a configuração no Facebook ou Google, é preciso configurar no Admin VTEX a opção de login pelo provedor desejado. Nos dois casos, você precisará ter em mãos o `Client ID` e o `Segredo do cliente` obtidos junto aos provedores.
 
-1. Acesse o módulo do VTEX ID pelo painel administrativo da loja no menu Configurações Da Conta > Autenticação;  
-![Lista Autenticação](https://images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/2fce3d14bc8d98ccf4586175791361ef/autenticacao_PT.png)
-2. Selecione o provedor e selecione **EDITAR**;
-3. Preencha o formulário com o `Client ID` e o `Client Secret` cadastrado;  
-![Facebook OAuth PT](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/c07c9d4160e7273a0f5ad2a0cabd1bec/facebook_PT.png)
-4. Ative o uso do provedor com o seu interruptor.  
-![Lista Autenticação Switch On Highlight](https://images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/c079f95b7833c2bdba7e5a86860f03cd/switch_On_highlight_PT.png)
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email.
+2. Clique em **Configurações da conta > Autenticação**.
 
-## Valide a configuração
+    Você será direcionado(a) para a aba **Loja virtual** da página **Autenticação**, que lista os métodos de login disponíveis na sua loja.
+    ![Lista Autenticação](//images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/5656de06dc15a094bea726c3d7f6e370/autenticacao-pt.png)
+3. Na linha do provedor de login desejado, clique em `Configurar`.
+4. Preencha o formulário com o `Client ID` e o `Segredo do cliente` cadastrado e clique em `Salvar`.
+    ![Facebook OAuth PT](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/1dcbc9286c0245740194026e19ba5c9b/1-login-fb-pt.png)
+5. Na página **Autenticação**, ative o uso do provedor clicando no interruptor.  
+    ![Lista Autenticação Switch On Highlight](//images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/c079f95b7833c2bdba7e5a86860f03cd/switch_On_highlight_PT.png)
 
-Com tudo configurado, você ja pode testar a sua configuração. Recomendamos que faça isso já através da URL final que seus usuários utilizarão para acessar sua loja. Ao tentar efetuar login, as opções referentes aos provedores ativos devem ser disponibilizadas e o processo deve poder ser efetuado sem maiores problemas.
+## Validar a configuração
 
+Após a configuração no Admin VTEX, recomendamos testar o login com o provedor escolhido através da URL final que seus usuários utilizarão para acessar sua loja. Ao tentar efetuar login, as opções referentes aos provedores ativos estarão disponíveis.
diff --git a/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
index 000367c5a..cdc4d53df 100644
--- a/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -58,7 +58,7 @@ Para configurar essa liquidação, siga o passo a passo:
 8. No campo __Captura antecipada__, selecione uma das opções de tempo disponíveis. 
 9. Preencha o campo __Alterar tempo máximo para captura__ com o período definido com a adquirente. __Caso você prefira deixar o campo em branco, o padrão de 4 dias será utilizado__.
 
-![captura_automatica_PT](https://images.ctfassets.net/alneenqid6w5/50rTz4DncUN9gOUZ9JWmMk/c5eb2f4759254eb1b8425bcee7267503/captura_automatica_atualizado_PT.png)
+![captura_automatica_PT](//images.ctfassets.net/alneenqid6w5/50rTz4DncUN9gOUZ9JWmMk/c5eb2f4759254eb1b8425bcee7267503/captura_automatica_atualizado_PT.png)
 10. Clique no __botão Salvar__. 
 
 Desse modo, o novo recurso de liquidação será implementado.
diff --git a/docs/tutorials/pt/configuring-my-account-conversational-commerce.md b/docs/tutorials/pt/configuring-my-account-conversational-commerce.md
index 14afaef4e..3fe4c5166 100644
--- a/docs/tutorials/pt/configuring-my-account-conversational-commerce.md
+++ b/docs/tutorials/pt/configuring-my-account-conversational-commerce.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar Minha conta (Conversational Commerce)'
 id: 42bnIdyC2c5dwz9KKT0UKc
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-03-07T19:10:12.107Z
-updatedAt: 2023-03-07T20:00:20.806Z
-publishedAt: 2023-03-07T20:00:20.806Z
+updatedAt: 2024-01-05T16:28:41.167Z
+publishedAt: 
 firstPublishedAt: 2023-03-07T19:58:45.529Z
 contentType: tutorial
 productTeam: Shopping
@@ -24,7 +24,7 @@ O [Conversational Commerce VTEX](https://help.vtex.com/pt/tracks/conversational-
 
 ## Campos das configurações de conversação
 
-![my account - conversational commerce - PT](https://images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/5e3c881eb854b74a4b36625ee3de43a7/image.png)
+![my account - conversational commerce - PT](//images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/5e3c881eb854b74a4b36625ee3de43a7/image.png)
 
 * **Idioma:** idioma que será o padrão para mensagens do bot com o cliente no Conversational Commerce VTEX. Campo obrigatório.
 * **Mensagem de boas-vindas:** primeira mensagem que o Conversational Commerce VTEX enviará em sua interação inicial com o cliente. Essa mensagem é seguida de mensagens explicativas do processo de compra e suporte humano da sua equipe de atendimento. Campo obrigatório. A sugestão de padrão é: 
diff --git a/docs/tutorials/pt/configuring-openpay-payment-gateway.md b/docs/tutorials/pt/configuring-openpay-payment-gateway.md
index d129d0253..5e9c28120 100644
--- a/docs/tutorials/pt/configuring-openpay-payment-gateway.md
+++ b/docs/tutorials/pt/configuring-openpay-payment-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar o gateway Openpay'
 id: 5vGj3UIFCU4GFFqVBlYKW2
 status: PUBLISHED
 createdAt: 2021-07-06T17:31:51.598Z
-updatedAt: 2021-07-06T18:01:16.234Z
-publishedAt: 2021-07-06T18:01:16.234Z
+updatedAt: 2024-01-25T18:44:58.747Z
+publishedAt: 2024-01-25T18:44:58.747Z
 firstPublishedAt: 2021-07-06T17:54:12.638Z
 contentType: tutorial
 productTeam: Financial
@@ -25,7 +25,7 @@ Para configurar o Openpay você precisará:
 
 1. [Configurar o Google Tag Manager](#configurar-o-google-tag-manager)
 2. [Configurar a Openpay](#configurar-a-openpay)
-3. [Associar a Openpay à uma condição de pagamento](#associar-uma-condicao-de-pagamento)
+3. [Configurar condições de pagamento](#configurar-condicoes-de-pagamento)
 
 ## Configurar o Google Tag Manager
 
@@ -35,18 +35,19 @@ Ao finalizar, passe para a etapa seguinte de configuração da Openpay no ambien
 
 ## Configurar a Openpay
 
-Ao finalizar a criação e ativação da Tag, no Google Tag Manager, é preciso instalar o conector do Openpay na sua loja. Siga as etapas abaixo:
+Ao finalizar a criação e ativação da Tag, no Google Tag Manager, é preciso instalar provedor Openpay na sua loja. Siga as etapas abaixo:
 
-1. Acesse o __Admin__ VTEX.
-2. No módulo __Pagamentos__, clique em __Configurações__.
-3. Em __Afiliações de gateway__, clique no sinal verde “__+__”.
-4. Busque e clique em __Open Pay.__
-5. Em __Nome da Afiliação__, nomeie __para Open Pay__.
-6. Preencha os __Application Key__ e __Application Token__. [Clique aqui](https://www.openpay.mx/en/docs/vtex.html) para acessar a documentação da Openpay com as instruções de como obter essas informações.
-7. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Openpay__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Nome da Afiliação__, nomeie para __Openpay__.
+5. Preencha os __Application Key__ e __Application Token__. [Clique aqui](https://www.openpay.mx/en/docs/vtex.html) para acessar a documentação da Openpay com as instruções de como obter essas informações.
+6. Clique em `Salvar`.
 
-## Associar uma condição de pagamento
+## Configurar condições de pagamento
 
-Depois de concluir todas as etapas, a Openpay estará configurada.
+Para configurar os métodos de pagamento a serem processados pela Openpay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
 
-Caso queira associá-la a uma condição de pagamento que seja compatível com o Openpay, siga o artigo [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, Openpay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md b/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md
new file mode 100644
index 000000000..97b740b20
--- /dev/null
+++ b/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurando condições de pagamento B2B'
+id: 6NMeukzx5H7n1YaePPS7pr
+status: PUBLISHED
+createdAt: 2024-07-25T16:31:16.186Z
+updatedAt: 2024-07-25T17:07:27.442Z
+publishedAt: 2024-07-25T17:07:27.442Z
+firstPublishedAt: 2024-07-25T17:07:27.442Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configurando-condicoes-de-pagamento-b2b
+locale: pt
+legacySlug: configurando-condicoes-de-pagamento-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Em uma operação B2B, as [condições de pagamento](https://help.vtex.com/pt/tutorial/how-to-configure-payment-conditions--tutorials_455?&utm_source=autocomplete) são atribuídas à organização compradora. Suas escolhas determinam quais opções de pagamento estão disponíveis para os usuários da organização durante o checkout.
+
+As opções de pagamento disponíveis podem ser personalizadas por centro de custo pelo usuário com perfil de administrador da organização. 
+
+<div class = "alert alert-info">
+Quando você configura uma condição de pagamento no módulo Pagamentos, ela aparece como um meio de pagamento na lista <b>Disponível</b>, dentro da aba <b>Condições de Pagamento</b>. Para visualizar essa lista, clique no nome da organização. Os métodos de pagamento listados são aqueles já atribuídos à organização.
+</div>
+
+## Associar condições de pagamento à organização
+Para associar uma condição de pagamento a uma organização compradora, siga as instruções abaixo:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custos B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar a página de detalhes.
+3. Na página de detalhes da organização, clique na aba **Condições de pagamento**.
+4. Selecione as opções de pagamentos desejadas na lista Disponível, e clique em `ADICIONAR À ORG`. 
+5. Clique em `Salvar` no canto superior direito.
+
+## Remover a associação das condições de pagamento
+Para desassociar condições de pagamento de uma organização compradora, siga as instruções abaixo:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custos B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar a página de detalhes.
+3. Na página de detalhes da organização, clique na aba **Condições de pagamento**.
+4. Selecione as opções desejadas na lista Atribuído à organização, e clique em `REMOVER DA ORG`.
+5. Clique em `Salvar` no canto superior direito.
+
diff --git a/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index e47554bb7..8447e03c2 100644
--- a/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com AdyenV3 no VTEX Sales App'
 id: 24yO6KloBn6DN6CbprHtgt
 status: PUBLISHED
 createdAt: 2023-05-09T14:12:03.567Z
-updatedAt: 2023-06-01T11:38:18.504Z
-publishedAt: 2023-06-01T11:38:18.504Z
+updatedAt: 2024-07-26T16:55:23.474Z
+publishedAt: 2024-07-26T16:55:23.474Z
 firstPublishedAt: 2023-05-11T20:30:50.460Z
 contentType: tutorial
 productTeam: Financial
@@ -51,12 +51,16 @@ Para habilitar o acesso da VTEX no ambiente Adyen, siga as instruções abaixo:
 2. Na barra lateral esquerda, copie e salve a informação descrita acima de **Company**. Esta é a sua Company Account.
 3. Na lista abaixo, busque o nome da Merchant Account a ser utilizada (ressaltada em branco). Copie e salve esta informação.
 
-![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtenha a POS Live URL
 
+Esta informação refere-se aos endpoints utilizados pelas APIs de terminais da Adyen em ambiente produtivo. Para mais informações, acesse a [documentação Adyen](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api#cloud).
+
+### Obtenha a Live URL prefix
+
 1. Na barra lateral, acesse **Developers > API URLs**.
-2. Clique em `Copy` no campo **Point of Sale** e anote a informação salva em um local seguro.
+2. Clique em `Copy` no campo **Prefix** e anote a informação salva em um local seguro. Este prefixo controla o seu endpoint na plataforma da Adyen.
 
 ### Obtenha a API Key
 
@@ -66,7 +70,7 @@ As informações abaixo consideram que a API Key já foi previamente gerada no a
 2. Selecione a sua credencial API.
 3. Em **Server Settings > Authentication**, selecione **API key**. 
 
-![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Clique em <b>Generate Key</b> e anote a informação criada em um local seguro.</ui>
 
@@ -82,7 +86,7 @@ Configure o webhook conforme os passos abaixo:
 4. Em **General > Description**, adicione uma descrição para o novo webhook. Exemplo: "Webhook Adyen Connector Provider v3".
 5. Em **General > Server configuration > URL**, preencha a URL da sua conta VTEX. Exemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Clique em <b>Apply</b>.</ui>
 
@@ -90,11 +94,11 @@ Configure o webhook conforme os passos abaixo:
 
 <blockquote><ui>8. Clique em <b>Save changes</b>.</ui>
 
-![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
@@ -102,22 +106,19 @@ Se você possui múltiplas lojas, é necessário realizar a configuração do we
 
 ## Configurar conector AdyenV3 (VTEX Sales App) na VTEX
 
-1. No Admin VTEX, acesse **Configurações da loja > Pagamentos > Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba **Afiliações de Gateways**, clique no botão `+`.
-3. Clique no conector **AdyenV3**.
-4. Preencha os seguintes campos com suas informações da Adyen:
-    - **Application Key**: o nome de sua Merchant account (passo 3 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account).
-    - **Application Token**: API Key (passo 4 da seção [Obtenha a API Key](#obtenha-a-api-key)).
-    - **Live URL prefix**: não é necessário preencher este campo (aplicável somente a outros canais de venda online).
-    - **Company account**: o nome de sua company account (passo 2 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account)).
-    - **Live POS URL**: URL prefix (passo 2 da seção [Obtenha a POS Live URL](#obtenha-a-pos-live-url). 
-    - **Client key**: não é necessário preencher este campo (aplicável somente a outros canais de venda online).
-
-<blockquote><ui>  5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão <b>Instalar app</b> e siga as instruções de instalação.</ui>
-
-<blockquote><ui>  6. Clique em <b>Salvar</b>.</ui>
-
-![Adyenv3_9](https://images.ctfassets.net/alneenqid6w5/SCflCIOFcwFro09YTxEZy/27b941b772a6afb021d0fa2fe25c9fa9/Adyenv3_9.PNG)
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __AdyenV3__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Chave de aplicação__, preencha o nome de sua Merchant account (passo 3 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account).
+5. Em __Token de aplicação__, insira o API Key (passo 4 da seção [Obtenha a API Key](#obtenha-a-api-key)).
+6. Caso deseje modificar o nome de identificação a ser exibido para o provedor AdyenV3 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+7. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+8. Em __Live URL prefix__, preencha o prefixo disponível na customer area da Adyen (passo 2 da seção [Obtenha a Live URL prefix](#obtenha-a-live-url-prefix)).
+9. Em __Company account__, insira o nome de sua company account (passo 2 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account)).
+10. Em __Live POS URL__, preencha com endpoints utilizados para acessar as APIs de terminais da Adyen. Saiba mais em [documentação Adyen](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api#cloud).
+11. O campo __Client Key__ não é necessário preencher, pois é aplicável somente a outros tipos de canais de venda online.
+12. Em __Auto Capture Settings__, selecione em que momento deseja realizar a captura do pagamento.
+13. Clique em `Salvar`.
 
 ## Configurar condição de pagamento
 
diff --git a/docs/tutorials/pt/configuring-payment-with-adyenv3.md b/docs/tutorials/pt/configuring-payment-with-adyenv3.md
index be39b92d3..c77087cbf 100644
--- a/docs/tutorials/pt/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/pt/configuring-payment-with-adyenv3.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com AdyenV3'
 id: 7xAz67E2Eg63LWCQNjVdwv
 status: PUBLISHED
 createdAt: 2023-05-08T20:00:38.610Z
-updatedAt: 2023-05-31T19:42:52.614Z
-publishedAt: 2023-05-31T19:42:52.614Z
+updatedAt: 2024-06-25T21:10:30.984Z
+publishedAt: 2024-06-25T21:10:30.984Z
 firstPublishedAt: 2023-05-11T20:32:21.638Z
 contentType: tutorial
 productTeam: Financial
@@ -39,15 +39,15 @@ Para habilitar o acesso da VTEX no ambiente Adyen, siga as instruções abaixo:
 ### Obtenha as credenciais Company e Merchant Account 
 
 1. Acesse a sua [Área do Cliente](https://ca-test.adyen.com/) na Adyen.
-2. Na barra lateral esquerda, copie e salve a informação descrita acima de **Company**. Esta é a sua Company Account.
+2. Na barra lateral esquerda, copie e salve a informação descrita acima de __Company__. Esta é a sua Company Account.
 3. Na lista abaixo, busque o nome da Merchant Account a ser utilizada (ressaltada em branco). Copie e salve esta informação.
 
-![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtenha a Live URL
 
-1. Na barra lateral, acesse **Developers > API URLs**.
-2. Clique em `Copy` no campo **Prefix** e anote a informação salva em um local seguro.
+1. Na barra lateral, acesse __Developers > API URLs__.
+2. Clique em `Copy` no campo __Prefix__ e anote a informação salva em um local seguro.
 
 ### Obtenha a API Key e Client Key
 
@@ -55,11 +55,11 @@ Para habilitar o acesso da VTEX no ambiente Adyen, siga as instruções abaixo:
 As informações abaixo consideram que a API Key e Client Key já foram previamente geradas no ambiente da Adyen. Caso seja necessário criá-las, consulte a documentação da <a href="https://docs.adyen.com/">Adyen</a>.
 </div>
 
-1. Clique em **Developers** na barra lateral e em seguida em **API credentials**.
+1. Clique em __Developers__ na barra lateral e em seguida em __API credentials__.
 2. Selecione a sua credencial API.
-3. Em **Server Settings > Authentication**, selecione **API key**. 
+3. Em __Server Settings > Authentication__, selecione __API key__. 
 
-![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Clique em <b>Generate Key</b> e anote a informação criada em um local seguro.</ui>
 
@@ -67,7 +67,7 @@ As informações abaixo consideram que a API Key e Client Key já foram previame
 
 <blockquote><ui>6. Clique em <b>Generate Client Key</b> e anote a informação criada em um local seguro.
 
-![Adyenv3_3](https://images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
+![Adyenv3_3](//images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
 
 ### Configure o webhook
 
@@ -75,13 +75,13 @@ A configuração do webhook é necessária para que a Adyen envie atualizações
 
 Configure o webhook conforme os passos abaixo:
 
-1. Na sua [Área do Cliente](https://ca-test.adyen.com/) na Adyen, acesse **Developers > Webhooks**.
+1. Na sua [Área do Cliente](https://ca-test.adyen.com/) na Adyen, acesse __Developers > Webhooks__.
 2. Clique no botão azul `+ Webhook`.
-3. Selecione a opção **Standard Webhook** clicando no botão **Add**.
-4. Em **General > Description**, adicione uma descrição para o novo webhook. Exemplo: "Webhook Adyen Connector Provider v3".
-5. Em **General > Server configuration > URL**, preencha a URL da sua conta VTEX. Exemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
+3. Selecione a opção __Standard Webhook__ clicando no botão __Add__.
+4. Em __General > Description__, adicione uma descrição para o novo webhook. Exemplo: "Webhook Adyen Connector Provider v3".
+5. Em __General > Server configuration > URL__, preencha a URL da sua conta VTEX. Exemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Clique em <b>Apply</b>.</ui>
 
@@ -89,11 +89,11 @@ Configure o webhook conforme os passos abaixo:
 
 <blockquote><ui>8. Clique em <b>Save changes</b>.</ui>
 
-![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
@@ -101,25 +101,35 @@ Se você possui múltiplas lojas, é necessário realizar a configuração do we
 
 ## Configurar conector AdyenV3 na VTEX
 
-1. No Admin VTEX, acesse **Configurações da loja > Pagamentos > Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba **Afiliações de Gateways**, clique no botão `+`.
-3. Clique no conector **AdyenV3**.
-4. Preencha os seguintes campos com suas informações da Adyen:
-    - **Application Key**: o nome de sua Merchant account (passo 3 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account).
-    - **Application Token**: API Key (passo 4 da seção [Obtenha a API Key e Client Key](#obtenha-a-api-key-e-client-key)).
-    - **Live URL prefix**: URL prefix (passo 2 da seção [Obtenha a Live URL](#obtenha-a-live-url)).
-    - **Company account**: o nome de sua company account (passo 2 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account).
-    - **Live POS URL**: não é necessário preencher este campo (aplicável somente ao VTEX Sales App). 
-    - **Client key**: Client key (passo 6 da seção [Obtenha a API Key e Client Key](#obtenha-a-api-key-e-client-key)).
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __AdyenV3__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Chave de aplicação__, preencha o nome de sua Merchant account (passo 3 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account).
+5. Em __Token de aplicação__, insira o API Key (passo 4 da seção [Obtenha a API Key e Client Key](#obtenha-a-api-key-e-client-key)).
+6. Caso deseje modificar o nome de identificação a ser exibido para o provedor AdyenV3 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+7. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+8. Em __Live URL prefix__, preencha o URL prefix (passo 2 da seção [Obtenha a Live URL](#obtenha-a-live-url)).
+9. Em __Company account__, insira o nome de sua company account (passo 2 da seção [Obtenha as credenciais Company e Merchant Account](#obtenha-as-credenciais-company-e-merchant-account)).
+10. Em__Live POS URL__, não é necessário preencher este campo (aplicável somente ao VTEX Sales App).
+11. Em __Client key__, insira o Client key (passo 6 da seção [Obtenha a API Key e Client Key](#obtenha-a-api-key-e-client-key)).
+12. Clique em `Salvar`.
 
-<blockquote><ui>  5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão <b>Instalar app</b> e siga as instruções de instalação.</ui>
+Para configurar os métodos de pagamento a serem processados pela AdyenV3, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). Caso deseje realizar vendas por meio do VTEX Sales App, acesse [Configurar pagamento com AdyenV3 no VTEX Sales App](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3-no-instore--24yO6KloBn6DN6CbprHtgt).
 
-<blockquote><ui>  6. Clique em <b>Salvar</b>.</ui>
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
 
-![Adyenv3_8](https://images.ctfassets.net/alneenqid6w5/6VHaDn8IejGCUoatLIyUtk/bb93a701e80a942064818a54ac401714/Adyenv3_8.PNG)
+## Configurar cartão de crédito
 
-Para configurar os métodos de pagamento a serem processados pela AdyenV3, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). Caso deseje realizar vendas por meio do VTEX Sales App, acesse [Configurar pagamento com AdyenV3 no VTEX Sales App](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3-no-instore--24yO6KloBn6DN6CbprHtgt).
+Se você deseja processar pagamentos com cartões de crédito em sua loja utilizando a AdyenV3, além de realizar as configurações anteriores descritas neste artigo, você deve abrir um ticket no [suporte da VTEX](https://help.vtex.com/pt/support), com a seguinte solicitação "Provider review - Add Endpoint SecureProxy - AdyenV3". 
 
-Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+No ticket você também deverá enviar a URL que será autorizada pela Adyen a realizar a transação no cartão de crédito em sua loja. O formato da URL deverá ser `https://{live URL prefix}-checkout-live.adyenpayments.com`, onde a informação "{live URL prefix}" deve ser a mesma inserida por você nas configurações da Adyen no Admin VTEX.
+
+<div class="alert alert-warning">
+O endereço completo da URL deve ser escrito somente em letras minúsculas, mesmo se o "Live URL prefix" configurado no Admin VTEX possuir alguma letra maíuscula.
+</div>    
+
+## Configurar pagamento com Apple Pay na Adyen (opcional) 
+
+Para processar pagamentos com Apple Pay na Adyen você precisa primeiramente realizar configurações para habilitar sua loja no ambiente da Apple Pay. Saiba mais em [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/docs/guides/setting-up-merchant-id-in-apple-pay).  
 
 Depois de seguir os passos indicados, o conector AdyenV3 pode demorar até 10 minutos para aparecer no checkout da sua loja como opção de pagamento.
diff --git a/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md b/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md
index 3654da069..24a548ccd 100644
--- a/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md
+++ b/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md
@@ -23,7 +23,7 @@ Existem duas modalidades de retirada em loja: **Pickup** e **Ship Store**. Nessa
 
 Os pedidos realizados e que utilizam a opção de retirada em loja, quando chegam à VTEX, são atribuídos à conta franquia que possui o ponto de retirada escolhido pelo cliente e o ponto de retirada terá seu estoque modificado.
 
-![fluxocriacaopup](https://images.ctfassets.net/alneenqid6w5/1ifP8Kk4uQQu3jW2vuZpPK/32e76d55a97a98461889c3a2d7ee26ec/fluxocriacaopup.JPG)
+![fluxocriacaopup](//images.ctfassets.net/alneenqid6w5/1ifP8Kk4uQQu3jW2vuZpPK/32e76d55a97a98461889c3a2d7ee26ec/fluxocriacaopup.JPG)
 
 Para criar os pontos de retirada, você vai precisar:
 
@@ -67,13 +67,13 @@ Para verificar se o ponto de retirada foi enviado a B2W:
 
 Na listagem dos pontos de retirada enviados, você conseguirá visualizar quais foram enviados com sucesso e quais possuem erro de configuração.
 
-![Início (4)](https://images.ctfassets.net/alneenqid6w5/NHUOSgg4hXhVapftBxIGJ/a6c17c27284c4220fcefc07ef47def2a/In__cio__4_.gif)
+![Início (4)](//images.ctfassets.net/alneenqid6w5/NHUOSgg4hXhVapftBxIGJ/a6c17c27284c4220fcefc07ef47def2a/In__cio__4_.gif)
 
 ## Confirmação da associação do ponto de retirada x anúncio 
 
 É possível confirmar se o ponto de retirada foi corretamente associado ao anúncio da B2W. O que define essa associação é a quantidade de estoque do produto, enviada para o ponto de retirada.
 
-![fluxoestoquepup](https://images.ctfassets.net/alneenqid6w5/120QcMpvS0nLSqPPor23ex/2d98326ca3f1d91bbf99fe97bb7f84c7/fluxoestoquepup.JPG)
+![fluxoestoquepup](//images.ctfassets.net/alneenqid6w5/120QcMpvS0nLSqPPor23ex/2d98326ca3f1d91bbf99fe97bb7f84c7/fluxoestoquepup.JPG)
 
 Para confirmar a associação, você deve verificar quais pontos de retirada estão sincronizados com o SKU e seus respectivos estoques. Siga os passos abaixo:
 
@@ -82,6 +82,6 @@ Para confirmar a associação, você deve verificar quais pontos de retirada est
 4. Filtre a listagem com a opção SkyHub/B2W.
 5. Localize o SKU desejado na caixa de pesquisa.
 
-![Início (5)](https://images.ctfassets.net/alneenqid6w5/7zVX7T1t17RWcNtJVsNXcd/768de551c0b4a955735fbbafcbf58a13/In__cio__5_.gif)
+![Início (5)](//images.ctfassets.net/alneenqid6w5/7zVX7T1t17RWcNtJVsNXcd/768de551c0b4a955735fbbafcbf58a13/In__cio__5_.gif)
 
 Os pontos de retirada estão sincronizados com o SKU e seus respectivos estoques serão apresentados na lista.
diff --git a/docs/tutorials/pt/configuring-price-divergence-rule.md b/docs/tutorials/pt/configuring-price-divergence-rule.md
index e11afa162..1b409da31 100644
--- a/docs/tutorials/pt/configuring-price-divergence-rule.md
+++ b/docs/tutorials/pt/configuring-price-divergence-rule.md
@@ -3,8 +3,8 @@ title: 'Configuração da regra de Divergência de valores'
 id: awAKP0sS5J8jgLs2g7pPe
 status: PUBLISHED
 createdAt: 2021-12-03T01:24:41.194Z
-updatedAt: 2023-03-29T19:19:25.326Z
-publishedAt: 2023-03-29T19:19:25.326Z
+updatedAt: 2024-03-27T21:10:37.241Z
+publishedAt: 2024-03-27T21:10:37.241Z
 firstPublishedAt: 2021-12-03T01:31:08.666Z
 contentType: tutorial
 productTeam: Channels
@@ -17,7 +17,13 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 Quando o preço definido por um seller é diferente do preço oferecido pelo marketplace, pedidos realizados em marketplaces podem não ser processados corretamente. Na VTEX, o fluxo de Autorização de pedidos permite o controle e a aprovação automática desses pedidos, a partir da configuração de uma [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW). Este artigo explica como o seller pode criar e editar uma regra de Divergência de valores, e autorizar pedidos manualmente.
 
-Quando nenhuma regra de Divergência de valores foi criada, por padrão, pedidos com divergência de preço são aprovados automaticamente. Isso vale para marketplaces VTEX, marketplaces externos, [conectores certificados (parceiros)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro), mas não para [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex). 
+Quando nenhuma regra de Divergência de preços for criada, a plataforma VTEX terá um comportamento específico para cada uma das situações abaixo:
+
+- **Pedidos criados pela interface de Marketplace:** Serão negados automaticamente.
+- **Pedidos criados via API:** Serão negados automaticamente, caso o campo `isCreatedAsync` não seja enviado.
+- **Pedidos com Divergência de preço relacionado a descontos manuais:** Serão aprovados automaticamente.
+
+Para utilizar o fluxo de Autorização de pedidos, em casos de divergência de preços é necessário enviar o campo `isCreatedAsync`  na API de [Place Fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders) , independentemente do tipo de conector utilizado. Esse cenário é válido para marketplaces VTEX, marketplaces externos, [conectores certificados](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) (parceiros), ou [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex)
 
 Quando um seller está integrado a um conector nativo, como o Mercado Livre ou a B2W, mas não configurou uma regra de Divergência de valores, pedidos com erro por diferença de preço ficam pendentes até a criação da regra. É possível acompanhá-los no seu Admin VTEX, em **MARKETPLACE > Conexões > Pedidos**.
 
@@ -35,17 +41,17 @@ Para criar uma regra de Divergência de valores, siga os passos abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja > Pedidos > Autorização de pedidos**, ou digite *Autorização de pedidos* na barra de busca no topo da página.
 2. Na seção _Divergência de valores_, clique em `CRIAR REGRAS`.
-3. Na nova página, clique em `CRIAR REGRAS`. 
+3. Na nova página, clique em `CRIAR REGRAS`.
 
 Você verá a seguinte tela:
 
-![print_01_PT](https://drive.google.com/uc?export=download&id=1VzNIIRjC4RoS9LGRY5-ux8QGwdSUpuxk)
+![print_01_PT](//images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/97a35d8b97cc9bd3a9ccd7c9db67b87a/print_01_PT.png)
 
-A aba **Todas** apresenta todas as regras de autorização configuradas. 
+A aba **Todas** apresenta todas as regras de autorização configuradas.
 
 Para criar a 1ª regra de autorização, clique em **CRIAR REGRAS**. A partir disso, será possível identificar uma nova aba, chamada **1ª regra**. Clique sobre ela e opções de configuração vão aparecer.
 
-![print_02_PT](https://drive.google.com/uc?export=download&id=1O_-p1ZP4hNZSYEtf_wwv40PXTbZkAg1Y)
+![print_02_PT](//images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/a8a96047fce4c061362d5a22ada0d2c0/print_02_PT.png)
 
 Para configurar a **1ª regra**, você pode aumentar ou diminuir o percentual de divergência, arrastando as extremidades da barra, sendo o sinal > para definir o início do intervalo, e < para determinar até onde ele vai. O intervalo percentual escolhido pode variar de 0% a 100%.
 
@@ -59,9 +65,9 @@ Uma vez definido o intervalo da regra de autorização, selecione uma das seguin
 
 Para configurar uma hierarquia de usuários responsáveis por aprovações de pedidos, é preciso inserir mais de um email e escolher a ordenação dos usuários cadastrados. É possível alterar esses usuários a qualquer momento, ao editar a regra de autorização de pedidos. Vale ressaltar que somente um usuário com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full pode editar a regra.
 
-Para criar a **2ª regra**, clique no <img class="shadow-4" src="https://https://images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> sinal de adição. Esse mesmo procedimento vale para criar uma terceira ou quarta regra, e assim por diante. Após clicar no ícone, aparece a seguinte interface:
+Para criar a **2ª regra**, clique no `<img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" />` sinal de adição. Esse mesmo procedimento vale para criar uma terceira ou quarta regra, e assim por diante. Após clicar no ícone, aparece a seguinte interface:
 
-![print_03_PT](https://drive.google.com/uc?export=download&id=1TNNvnvvX8wrFTNJswOXuWQGiaPzAINET)
+![print_03_PT](//images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/15b1a362d2184c3e8a09f65796ea9db2/print_03_PT.png)
 
 Configure a nova regra de autorização e, após definir todas as regras desejadas, clique no botão **SALVAR REGRAS**. Você verá a seguinte mensagem: _Após salvar, você ainda poderá editá-las ou excluí-las quando quiser_. Clique em **OK** para  confirmar. Feito isso, você terá concluído a criação da regra de Divergência de valores.
 
@@ -118,8 +124,9 @@ Para autorizar um pedido com Divergência de valores pelo VTEX DO, realize os se
 4. Clique em `Fechar`.
 5. A seguir, clique na opção `Authorize`.
 
-###  Saiba mais
+### Saiba mais
 
 - [Regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW)
 - [Todos os pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi)
 - [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402)
+
diff --git a/docs/tutorials/pt/configuring-product-visited.md b/docs/tutorials/pt/configuring-product-visited.md
index 0d1118557..94c2a7661 100644
--- a/docs/tutorials/pt/configuring-product-visited.md
+++ b/docs/tutorials/pt/configuring-product-visited.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar produto visitado'
 id: tutorials_3136
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T21:52:11.184Z
-updatedAt: 2023-03-28T23:34:22.351Z
-publishedAt: 2023-03-28T23:34:22.351Z
+updatedAt: 2024-06-18T21:19:01.080Z
+publishedAt: 2024-06-18T21:15:58.589Z
 firstPublishedAt: 2017-04-27T23:03:54.918Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,6 +15,10 @@ legacySlug: configurando-produto-visitado
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
+<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Tutorial válido apenas para lojas CMS Portal Legado.
+</div>
+
 O produto visitado é a funcionalidade que envia e-mails para os clientes que navegaram por um produto em seu site mas não finalizaram compra. Esse e-mail tem como objetivo a recuperação da venda, enviando, além do produto abandonado, sugestões de novos produtos. Tudo isso é possível através de seu Master Data.
 
 [![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
@@ -55,11 +59,11 @@ Após criar um campo na entidade, é preciso configurar para que o campo seja ex
 
 ### Crie o template de e-mail
 
-O template do e-mail que será enviado, assim como no Carrinho Abandonado, é configurado no módulo CMS. Para auxiliar a configuração, [use nosso template de exemplo](//assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "use nosso template de exemplo").
+O template do e-mail que será enviado, assim como no Carrinho Abandonado, é configurado no módulo CMS. Para auxiliar a configuração, [use nosso template de exemplo](//assets.ctfassets.net/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/90018592126fff6bd0d7a9a4ae8568d7/produtovisitadoexemplo.zip).
 
 1. Acesse o módulo **CMS**;
 2. Clique em **Portal**;
-3. [Clique aqui para baixar o template de exemplo](//assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "Clique aqui para baixar o template de exemplo");
+3. [Clique aqui para baixar o template de exemplo](//assets.ctfassets.net/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/90018592126fff6bd0d7a9a4ae8568d7/produtovisitadoexemplo.zip)
 4. Clique em **Templates de página**;
 5. Clique em **novo template**;
 6. Preencha o nome e cole o código de seu template. Atenção! Se estiver usando o template de exemplo, lembre-se de alterar o código `TEMPLATE_DE_PRATELEIRA` pelo id de seu template de prateleira e o código `NOME_DA_LOJA` pela URL de sua loja.
diff --git a/docs/tutorials/pt/configuring-promotions-for-marketplaces.md b/docs/tutorials/pt/configuring-promotions-for-marketplaces.md
index 3bb4d2c41..19ac0f80f 100644
--- a/docs/tutorials/pt/configuring-promotions-for-marketplaces.md
+++ b/docs/tutorials/pt/configuring-promotions-for-marketplaces.md
@@ -3,8 +3,8 @@ title: 'Configurar promoção para marketplace'
 id: tutorials_406
 status: PUBLISHED
 createdAt: 2017-04-27T22:06:28.854Z
-updatedAt: 2023-01-26T18:41:34.664Z
-publishedAt: 2023-01-26T18:41:34.664Z
+updatedAt: 2024-01-18T17:21:44.418Z
+publishedAt: 2024-01-18T17:21:44.418Z
 firstPublishedAt: 2017-04-27T23:03:23.902Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -24,6 +24,7 @@ Apenas [promoções regulares](https://help.vtex.com/pt/tracks/promocoes--6asfF1
 - Promoção de frete grátis
 - Promoção de frete percentual
 - Promoção de preço percentual
+- Tabela de preços
 
 As configurações disponíveis para marketplaces VTEX são distintas das oferecidas para marketplaces externos. Por isso, o comportamento das promoções em outros marketplaces é ligeiramente diferente do usual.
 
@@ -31,7 +32,7 @@ As configurações disponíveis para marketplaces VTEX são distintas das oferec
 
 Para este tipo de promoção, é importante ter em mente as seguintes informações:
 
-- Alguns marketplaces utilizam sua própria tabela de frete. Isso impede que uma promoção de frete seja aplicada a um pedido, já que o marketplace não consulta o valor do frete cadastrado na VTEX.
+- Uma vez que a promoção é criada e ativada pelo seller, ela não gera nenhum tipo de notificação para o marketplace. Cabe ao marketplace consultar o preço promocional.
 - Para a promoção ser aplicada ao valor do frete, o marketplace deve simular o frete usando o endpoint `POST` `https://{accountName}.vtexcommercestable.com.br/api/fulfillment/pvt/orderForms/simulation?sc={salesChannel}&affiliateId={affiliateId}`.
 - A promoção não será aplicada ao valor do produto se o marketplace utilizar o endpoint [List Freight Values](https://developers.vtex.com/docs/api-reference/logistics-api#get-/logistics/pvt/configuration/freights/-carrierId-/-cep-/values) da Logistics API para a consulta de fretes. Esse endpoint retorna apenas os fretes cadastrados na VTEX, sem considerar os efeitos promocionais.
 - Os sellers determinam os limites de redução de preço que o marketplace pode aplicar sobre o frete cobrado. Caso o valor de redução ultrapasse o limite estabelecido, o pedido não é realizado.
@@ -50,7 +51,7 @@ Para este tipo de promoção, é importante ter em mente as seguintes informaç
 Existem diferenças entre as configurações disponíveis para marketplaces VTEX e para marketplaces externos. Veja na tabela abaixo quais funcionalidades se aplicam a cada caso.
 
 <div class = "alert alert-warning">
-  <p><b>Importante:</b> no caso de integrações externas, as configurações são únicas de cada marketplace, e estes decidem quais funcionalidades vão utilizar.</p>
+  <p>No caso de integrações externas, as configurações são únicas de cada marketplace, e estes decidem quais funcionalidades vão utilizar.</p>
 </div>
 
 | Nome  | Descrição      | Disponível para marketplace VTEX? | Disponível para marketplace externo? |
@@ -73,7 +74,47 @@ Existem diferenças entre as configurações disponíveis para marketplaces VTEX
 | Canais de venda| A promoção será aplicada a uma lista de canais de venda.| Sim| Sim|
 | Valor do item entre| Estabelece as políticas comerciais válidas para a promoção.| Sim| Sim|
 
-## Definindo onde a promoção será aplicada
+## Promoções indisponíveis para marketplaces
+
+Verifique as promoções que não estão disponíveis para marketplaces:
+
+* Desconto nominal
+* Preço máximo por item
+* Frete nominal
+* Frete máximo
+* Brinde
+* Valor fidelidade
+* Compre Junto
+* Leve Mais Por Menos
+* Desconto Progressivo
+* Compre e Ganhe
+* Campanha
+
+### Configurações indisponíveis
+
+Veja abaixo as configurações que não estão disponíveis para marketplaces:
+
+| Nome | Descrição|
+| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Cluster de clientes                                                | Desconto concedido caso o cliente esteja cadastrado no [cluster](https://help.vtex.com/pt/tutorial/como-criar-um-cluster-de-clientes--frequentlyAskedQuestions_1724) selecionado.                                        |
+| Marketing tag                                                      | Utilizado para restringir a ativação da promoção caso a compra seja realizada pelo [módulo de Assinaturas da VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#).        |
+| UTMs                                                               | Desconto concedido a depender do valor de um dado [parâmetro UTM](https://help.vtex.com/pt/tutorial/o-que-sao-utm-source-utm-campaign-e-utm-medium--2wTz7QJ8KUG6skGAoAQuii).                                             |
+| Audiência de campanha                                              | Permite segmentar as promoções da sua loja a partir da definição de [públicos-alvo](https://help.vtex.com/pt/tutorial/audiencias-de-campanhas--3o7lhpNseXY2WmjZO0gQ6m#publico-alvo) que atendem a critérios específicos. |
+| Cupons                                                             | Código que permite aplicar promoções sobre o valor do carrinho.                                                                                                                                                          |
+| Valor mínimo ou máximo do carrinho                                 | Aplicada levando em conta o valor do carrinho sem considerar demais promoções ou frete.                                                                                                                                  |
+| Número de parcelas                                                 | Desconto concedido caso o número de parcelas selecionadas pelo cliente esteja no intervalo cadastrado.                                                                                                                   |
+| Restrição de BIN                                                   | Desconto concedido caso o BIN do cartão esteja entre os números preenchidos.                                                                                                                                             |
+| Meio de pagamento                                                  | Desconto concedido caso a forma de pagamento selecionada pelo cliente seja a mesma cadastrada na promoção.                                                                                                               |
+| Primeira compra                                                    | Desconto concedido na primeira compra do cliente.                                                                                                                                                                        |
+| Valor acumulado em compras                                         | Desconto concedido caso o total de todas as compras já realizadas pelo cliente esteja atendendo ao valor preenchido.                                                                                                     |
+| Permitir acumular com preços manuais                               | Permite que a promoção seja aplicada a produtos cujos preços foram manualmente inseridos pelo televendas.                                                                                                                |
+| Preço "de" e "por" são iguais ou Preço "de" e "por" são diferentes | Se refere aos valores do cadastro do produto.                                                                                                                                                                            |
+| Filtro de sellers                                                  | Define para quais sellers a promoção será aplicada.                                                                                                                                                                      |
+| Uso máximo da promoção por cliente                                 | Limita a quantidade de vezes que cada cliente poderá receber a promoção.                                                                                                                                                 |
+| Uso máximo da promoção por loja                                    | Limita a quantidade de vezes em que a promoção será aplicada.                                                                                                                                                            |
+| Uso máximo de cupom por produto                                    | Limita a quantidade de vezes em que o cupom será válido por produto.                                                                                                                                                     |
+
+## Definir o contexto que a promoção será aplicada
 
 Se necessário, é possível segmentar promoções para marketplaces específicos. Existem dois seletores que podem ser usados para obter este resultado:
 
@@ -85,15 +126,15 @@ Se necessário, é possível segmentar promoções para marketplaces específico
 1. Crie uma [promoção regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#).
 2. Na seção **Política Comercial**, selecione as opções **Iguais a** e **Entregue por mim (Lojas de terceiros)**.
 3. Em seguida, selecione as políticas comerciais desejadas.
-4. Clique em **Salvar**.
+4. Clique em `Salvar`.
 
 ### Seleção por afiliado
 
 1. Crie uma [promoção regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#).
 2. Preencha o campo **Afiliados** com o nome do afiliado relacionado ao marketplace desejado.
 3. Na seção **Política Comercial**, selecione as opções **Iguais a** e **Entregue por mim (Lojas de terceiros)**.
-4. Clique em **Salvar**.
+4. Clique em `Salvar`.
 
 <div class = "alert alert-warning">
-  <p>Uma vez que você crie a promoção, lembre-se de <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar os produtos afetados</a>. Dessa forma, os seus produtos terão os preços atualizados.</p>
+  <p>Uma vez que você crie a promoção, lembre-se de <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar os produtos afetados</a> no inicio e fim das promoções. Dessa forma, os seus produtos terão os preços atualizados.</p>
 </div>
diff --git a/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md b/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md
index a14f256d7..63509e9a1 100644
--- a/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md
+++ b/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md
@@ -3,8 +3,8 @@ title: 'Configurar promoção com destaque / flag'
 id: tutorials_2295
 status: PUBLISHED
 createdAt: 2017-04-27T21:55:19.949Z
-updatedAt: 2023-03-31T19:22:08.848Z
-publishedAt: 2023-03-31T19:22:08.848Z
+updatedAt: 2024-07-29T18:59:29.549Z
+publishedAt: 2024-07-29T18:59:29.549Z
 firstPublishedAt: 2017-04-27T23:03:51.539Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,6 +15,10 @@ legacySlug: configurando-promocao-com-destaque-flag
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
+<div class="alert alert-warning" role="alert">
+Tutorial válido apenas para lojas CMS Portal Legado.
+</div>
+
 O destaque na promoção é um aviso que pode ser inserido nas prateleiras e nas páginas de produto, informando que ele é elegível para uma promoção. Um exemplo bem comum é uma imagem abaixo da imagem do produto indicando frete grátis.
 
 ![ExemploPromocaoDestaque2](//images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
@@ -64,7 +68,7 @@ Essa configuração consiste da edição do template de página utilizado para o
 9. Na janela, clique na opção **New Layout**.
 10. No menu lateral, clique sobre o layout marcado em com um check vermelho e no campo __Template__, verifique qual o nome do template utilizado;
 
-![Layout com check - PT](https://images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
+![Layout com check - PT](//images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
 
 ![Template](//images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
 
diff --git a/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md b/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md
new file mode 100644
index 000000000..3411956b2
--- /dev/null
+++ b/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md
@@ -0,0 +1,73 @@
+---
+title: 'Configurando PWA em sua loja Store Framework'
+id: 1xWVQTONeROlSOXG8lSyKV
+status: PUBLISHED
+createdAt: 2024-06-18T14:58:53.804Z
+updatedAt: 2024-06-20T12:15:54.742Z
+publishedAt: 2024-06-20T12:15:54.742Z
+firstPublishedAt: 2024-06-18T15:49:26.862Z
+contentType: tutorial
+productTeam: Others
+author: YRJ73j8mt38D5TUleocQB
+slug: configurando-pwa-em-sua-loja-store-framework
+locale: pt
+legacySlug: configurando-pwa-em-sua-loja-store-framework
+subcategory: 7ogirQ8NClawO2X6xdgCKc
+---
+
+Lojas desenvolvidas com o VTEX IO Store Framework possuem nativamente um *Progressive Web App* (PWA), que é um tipo de aplicativo web que oferece uma experiência de usuário semelhante a de um aplicativo nativo, mas executada diretamente em um navegador da web.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Para lojas CMS Portal Legado, consulte o guia <a href="https://help.vtex.com/pt/tutorial/how-to-turn-my-store-website-into-a-pwa--3i8VmYeToAUGKgo2kKK6I2">Como transformar o site da minha loja em um PWA</a>.
+</div>
+
+Para configurar um PWA em sua loja, acesse Configurações da Loja > Storefront > Loja no Admin VTEX, e siga as etapas abaixo:
+
+1. Clique na aba **PWA**.
+2. Defina a **Cor do tema**, **Cor de fundo** e adicione o **Ícone de logotipo Android  (512x512, PNG)** e **Ícone de logotipo iOS (512x512, PNG)**. As cores devem ser especificadas em código hexadecimal (e.g., #F71963) e os ícones devem ter tamanho 512x512  px e extensão `.png`.
+
+  ![pwa-settings-1-pt](//images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/9bea6f91cd42a70bffb185f1037f43eb/pwa-settings-1-pt.png)
+
+3. Desça a página e vá para o campo **Outras configurações do PWA**. Clique na seta para mostrar as outras configurações.
+
+  ![pwa-settings-2-pt](//images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/faa642b4f2c82f837d6c60a319e63dd0/pwa-settings-2-pt.png)
+
+4. Em **Outras configurações de PWA**, preencha os campos conforme orientações abaixo:
+
+    - **URL inicial**: URL da página inicial do PWA.
+    - **Orientação da tela**: Formato como o conteúdo é exibido no PWA. Pode ser atribuído um dos seguintes valores: Todas, Natural, Horizontal, Horizontal (primária), Horizontal (secundária), Retrato, Vertical (primária), Vertical (secundária).
+
+    | **Orientação da tela**   | **Descrição** |
+    |--------------------------|---------------|
+    | Todas                    | A página pode ser visualizada em qualquer orientação, com o conteúdo se ajustando automaticamente para se adaptar à orientação atual do dispositivo. |
+    | Natural                  | Configuração padrão de fábrica do dispositivo. |
+    | Horizontal               | O conteúdo é exibido apenas na orientação horizontal. É útil para aplicativos ou jogos que são otimizados para uma visualização mais ampla. |
+    | Horizontal (primária)    | Orientação horizontal com a parte superior do dispositivo alinhada à esquerda. |
+    | Horizontal (secundária)  | Orientação horizontal com a parte superior do dispositivo alinhada à direita. |
+    | Retrato                  | O conteúdo é exibido apenas na orientação vertical. É a configuração padrão para a maioria dos aplicativos de telefonia móvel. |
+    | Vertical (primária)      | Orientação retrato com o botão `home` ou a parte inferior do dispositivo apontando para baixo. |
+    | Vertical (secundária)    | Orientação retrato invertida, com o botão `home` ou a parte inferior do dispositivo apontando para cima. É útil quando os dispositivos são usados de cabeça para baixo. |
+
+    - **Visualização**: Modos de visualização do conteúdo do PWA. Pode ser atribuído um dos seguintes valores: Tela cheia, Aplicativo (adicionar à tela inicial), Minimalista (não suportado pelo Chrome), Navegador.
+
+    | **Visualização** | **Descrição** |
+    |------------------|---------------|
+    | Tela cheia       | O PWA ocupa toda a tela do dispositivo, ocultando todos os elementos da interface do usuário do navegador, como a barra de endereços e outras notificações do sistema. É ideal para jogos ou aplicativos que necessitam de uma imersão completa, maximizando o espaço de tela disponível. |
+    | Aplicativo (adicionar à tela principal) | O PWA se comporta como um app nativo, pois é executado em uma janela separada do navegador e não mostra elementos comuns do navegador como a barra de endereços. Quando adicionado à tela inicial do dispositivo, a presença do PWA é quase indistinguível de um app nativo. |
+    | Minimalista (não suportado pelo Chrome) | O PWA mostra um mínimo de elementos de interface do usuário do navegador, como a barra de endereços e alguns controles adicionais. É um meio-termo entre o modo Aplicativo e o Navegador. |
+  | Navegador        | O PWA é aberto como uma página comum de navegador, com todas as características usuais do navegador visíveis, como a barra de endereços, abas e outros controles de interface. Não altera a maneira padrão de interação do usuário com o conteúdo web e é menos imersivo em comparação com os demais modos de visualização. |
+
+    - **Adicionar à tela inicial**: quando ativada, permite que o PWA seja instalado pelo usuário.
+    - **Exibir prompt “Adicionar à tela inicial”**: define o momento em que a instalação do PWA será sugerida ao usuário. Pode ser atribuído um dos seguintes valores: Na primeira visita, Ao adicionar o primeiro item ao carrinho, ou Ao finalizar a primeira compra. Esta opção é aplicável apenas quando **Adicionar à Tela Inicial** está ativada.
+
+   ![pwa-settings-3-pt](//images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/afb78e3e3a3ead92b334b459227ddb0a/pwa-settings-3-pt.png)
+
+ 5. Salve suas alterações clicando em `SALVAR`.
+
+## Utilizando um Service Worker personalizado
+
+Nosso service worker suporta os push nativos para instalar o app na primeira visita, no primeiro item adicionado ao carrinho ou na primeira compra. Você pode personalizar as notificações no PWA de sua loja usando um service worker próprio que funcionará junto ao nosso.
+
+Para saber como criar um Service Worker próprio, confira a documentação [Como instalar um Service Worker](https://help.vtex.com/pt/tutorial/como-instalar-um-service-worker--2H057iW0mQGguKAciwAuMe).
+
+Para aprender como aproveitar o Service Worker builder para agrupar vários services workers em sua loja, confira a documentação [Using several service workers in your store](https://developers.vtex.com/docs/guides/vtex-io-documentation-using-several-service-workers-in-your-store).
diff --git a/docs/tutorials/pt/configuring-redirects.md b/docs/tutorials/pt/configuring-redirects.md
new file mode 100644
index 000000000..365a53943
--- /dev/null
+++ b/docs/tutorials/pt/configuring-redirects.md
@@ -0,0 +1,81 @@
+---
+title: 'Configurar redirecionamentos'
+id: 35JPufOvunMHnAAVJA6azu
+status: PUBLISHED
+createdAt: 2024-06-27T17:05:37.927Z
+updatedAt: 2024-06-27T17:06:40.835Z
+publishedAt: 2024-06-27T17:06:40.835Z
+firstPublishedAt: 2024-06-27T17:06:40.835Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configurar-redirecionamentos
+locale: pt
+legacySlug: configurar-redirecionamentos
+subcategory: 
+---
+
+Para configurar um redirecionamento, você precisa seguir os passos a seguir:
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Redirecionamentos**.
+3. Clique no botão <i class="fas fa-plus"></i> `Adicionar`.
+4. Preencha os campos referentes às [informações gerais](#informacoes-gerais) do redirecionamento detalhadas na seção abaixo.
+5. Clique em <i class="fa-solid fa-plus"></i> `Adicionar condição`.
+6. Preencha os campos de [Regras de ativação](#regras-de-ativacao).
+7. Para finalizar, clique em `Aplicar`.
+
+Você deve preencher os seguintes campos:
+
+![redirecionamentos-adminv4-PT](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
+
+### Informações gerais
+
+Esta seção apresenta as seguintes informações gerais sobre o redirecionamento:
+
+- **Nome**: nome do conjunto de regras do redirecionamento criado.
+- **URL de redirecionamento**: endereço de destino que o cliente será encaminhado. Precisa ser cadastrado de forma absoluta - endereço completo - e não relativo. Exemplo: `https://www.loja.com.br/_secure/account/#/orders` ao invés de `_secure/account/#/orders`.
+- **Idiomas:** idiomas aos quais o redirecionamento será aplicado. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+
+### Regras de ativação
+
+Conjunto de condições de termos ou filtros que serão aplicados a cada pesquisa realizada. É necessário ter pelo menos uma condição cadastrada, seja por termo ou por filtro. 
+
+Selecione o tipo do escopo das regras, seja por termo ou por filtro.
+
+- **Termo**: palavra pesquisada pelo cliente que será relacionada à regra. O termo apresenta duas opções:
+    - `é`: precisa ser uma pesquisa com palavras exatas. Exemplo: se você cadastrar “black friday” e o cliente pesquisar por “black friday” o redirecionamento seria acionado. Caso ele pesquise por “promoção black friday”, ele não é ativado.
+    - `contém`: não precisa ser uma pesquisa com palavras exatas. Exemplo: se você cadastrar “black friday” e o cliente pesquisar por “black friday” o redirecionamento seria acionado. Caso ele pesquise por “promoção black friday”, ele também é ativado.
+- **Filtro**: atributo pesquisável já definido que restringe os resultados de busca. Apenas selecionar o filtro já cadastrado ativa o redirecionamento criado. O filtro apresenta duas opções:
+    - `é`: essa opção possibilita que não somente o filtro da regra seja selecionado. Exemplo: se a regra for ``é``: Filtro _marca_, valor Nike. Mesmo o cliente tendo selecionado também adidas, o redirecionamento seria acionado.
+    - `somente`: Essa opção possibilita apenas que o filtro cadastrado seja selecionado. Exemplo: se a regra for ``somente``: Filtro _marca_, valor Nike. Se o cliente já tiver selecionado adidas, o redirecionamento não seria acionado. Só funcionaria se o primeiro filtro de marca fosse Nike.
+
+Caso você deseje criar mais de uma regra, é preciso adicionar uma condição de interação entre as regras. Elas podem ser:
+
+- `ou`: qualquer uma das regras cadastradas ativam o redirecionamento.
+- `e`: é preciso atender a todas as regras juntas para ativar o redirecionamento.
+
+Ao clicar em <i class="fas fa-ellipsis-v"></i> você terá as seguintes opções:
+
+- <i class="fas fa-clone"></i> **Duplicar**: cria uma cópia da regra selecionada.
+- <i class="far fa-trash-alt"></i> **Deletar**: deleta a regra selecionada.
+
+Para apagar todas as regras configuradas, clique em `Limpar Regras`.
+
+### Importar CSV
+
+Caso existam muitos redirecionamentos a serem cadastrados, você pode fazer um arquivo CSV e depois importá-lo no Admin. O arquivo deve seguir o seguinte formato para cada redirecionamento criado: `<Nome>;<URL>;<Tipo>;<Ativo>;<Tópico>;<Verbo>;<Valor>`.
+
+- **Nome**: define o título do redirecionamento. Os possíveis valores são `termo` ou `filtro`.
+- **URL:** URL do redirecionamento.
+- **Tipo:**  regra de ativação. Os possíveis valores são `and` ou `or`.
+- **Ativo:** condição de ativação do redirecionamento. Os possíveis valores são `true` ou `false`.
+- **Tópico:** atributo pesquisável. Os possíveis valores são `term` para redirecionamento de termo ou `brand`, `category`, `department`, `sellername` e `subcategory` para redirecionamento de filtro.
+- **Verbo:** opção de inclusão do **Tópico**. Os possíveis valores são `is` ou `contains`.
+- **Valor:** valor do termo ou do filtro.
+
+Para importar o arquivo, siga as instruções abaixo.
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Redirecionamentos**.
+3. Clique no botão `Importar`.
diff --git a/docs/tutorials/pt/configuring-samsung-pay-as-a-payment-method.md b/docs/tutorials/pt/configuring-samsung-pay-as-a-payment-method.md
index 45ce2daa4..c350d439d 100644
--- a/docs/tutorials/pt/configuring-samsung-pay-as-a-payment-method.md
+++ b/docs/tutorials/pt/configuring-samsung-pay-as-a-payment-method.md
@@ -3,8 +3,8 @@ title: 'Configurar Samsung Pay como meio de pagamento '
 id: 5Yj9rgzOCVYuGmAumQlfpP
 status: PUBLISHED
 createdAt: 2020-08-26T13:40:16.356Z
-updatedAt: 2023-03-29T01:17:07.597Z
-publishedAt: 2023-03-29T01:17:07.597Z
+updatedAt: 2024-07-24T13:36:58.723Z
+publishedAt: 2024-07-24T13:36:58.723Z
 firstPublishedAt: 2020-08-26T16:30:52.180Z
 contentType: tutorial
 productTeam: Financial
@@ -15,27 +15,21 @@ legacySlug: configurar-samsung-pay-como-meio-de-pagamento
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Neste tutorial, ensinaremos como configurar a carteira digital Samsung Pay como meio de pagamento. 
+Na VTEX, é possível utilizar a carteira digital Samsung Pay como meio de pagamento em sua loja.
 
-O primeiro passo é configurar o conector da Adyen - afiliação de gateway que processa os pagamentos realizados com o Samsung Pay - na sua loja. Você pode conferir o passo a passo completo para realizar essa ação [aqui](https://help.vtex.com/pt/tutorial/como-configurar-o-gateway-adyen-na-vtex--tutorials_2337?locale=pt "aqui").
+Primeiramente é necessário configurar o provedor de pagamento da [Adyen](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3--7xAz67E2Eg63LWCQNjVdwv) em sua loja, pois ele será responsável por processar os pagamentos recebidos via Samsung Pay.
 
-Em seguida, você pode configurar o meio de pagamento em si.
+Depois será necessário configurar o Samsung Pay conforme as etapas abaixo:
 
-Siga as instruções:
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre a opção __Samsung Pay__.
+4. Ative a condição no campo __Status__.
+5. Em __Processar com o provedor__, selecione a opção __Adyen__.
+6. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+7. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+8. Clique em `Salvar`.
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Certifique-se que você está na aba __Condições de pagamento__.
-3. Ao lado da barra de busca, clique no __botão verde “+”__.
-4. Na seção “Outro”, clique na opção __Samsung Pay__.
-5. No topo da página, defina um __nome__ no campo __Nome da Regra__.
-6. Logo abaixo, clique no botão __Status__ para ativar a regra.
-7. Em Processar com afiliação, selecione a opção __Adyen__.
-8. Se for o caso, selecione o serviço de __Antifraude__ que será usado.
+Para definir condições especiais sobre o Samsung Pay, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Desse modo, você terá realizado a configuração mais básica do meio de pagamento. 
-
-Contudo, existe ainda a opção de __definir condições especiais de pagamento__ - regras específicas para o Samsung Pay que são aplicadas apenas em certos contextos definidos por período, país, política comercial (Canal de Vendas), condição comercial ou nome de uma conta. 
-
-Basta clicar no botão branco “__Adicionar condição especial__” e selecionar qual contexto você deseja especificar. Vale lembrar que é possível definir mais de uma condição especial por meio de pagamento. Para saber mais detalhes, confira o [tutorial sobre como configurar cada uma das condições especiais](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456?locale=pt "tutorial sobre como configurar cada uma das condições especiais").
-
-Se esse não for o caso, finalize a configuração clicando no botão __“Salvar”__.
+Depois de seguir os passos indicados, Samsung Pay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
new file mode 100644
index 000000000..648f6a3e3
--- /dev/null
+++ b/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
@@ -0,0 +1,52 @@
+---
+title: 'Configurando atribuição de sellers à organizações compradoras (B2B)'
+id: 3VJtKNbLpVAl71uVdaOqpE
+status: PUBLISHED
+createdAt: 2023-12-21T18:05:34.497Z
+updatedAt: 2024-06-06T16:46:09.065Z
+publishedAt: 2024-06-06T16:46:09.065Z
+firstPublishedAt: 2023-12-21T18:07:21.012Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: configurando-atribuicao-de-sellers-a-organizacoes-compradoras-b2b-xky
+locale: pt
+legacySlug: configurando-atribuicao-de-sellers-a-organizacoes-compradoras-b2b-xky
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+
+Fabricantes e distribuidores desempenham um papel fundamental no processo de compras entre empresas (B2B). Em determinados cenários, como o de marketplace, as características operacionais de cada um podem levar a conflitos de canais de compra. Veja alguns exemplos:
+
+* Fabricantes: possuem amplo conhecimento sobre seus produtos e gestão de portfólio, mas precisam criar portais de venda para gerenciar melhor os processos de 'sell-in' (venda de produtos do fabricante para o distribuidor) e 'sell-out' (venda do distribuidor para o consumidor final).
+* Distribuidores: são responsáveis por atuar diretamente com as organizações compradores, possuindo capacidades complementares, como o fornecimento de crédito, treinamento em massa e ampla rede de distribuição, mas optam por desenvolver múltiplos portais de venda próprios.
+
+Neste contexto, a organização compradora precisa acessar diferentes canais e o processo de compra torna-se fragmentado e ineficaz.
+
+Na VTEX, organizações compradoras (B2B) podem criar uma regra de atribuição que permita realizar compras de produtos de forma direcionada somente em sellers que atendam às suas necessidades operacionais ou de logística.
+
+Para atribuir sellers à uma determinada organização compradora, siga os passos abaixo:
+<ol>
+<li>No Admin VTEX, acesse <b>Aplicativos > Organizações e centros de custo B2B > Organizações</b>, ou digite <b>Organizações</b> na barra de busca no topo da página.</li>
+<li>Na aba <b>Organizações</b>, clique sobre o nome da organização compradora desejada.</li>
+
+![Organizações](//images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/b823f4c4377b5eee578e8d58ec9beb87/ORGANIZACOES.jpg)
+
+<li>Na aba <b>Sellers</b>, em <b>Disponível</b>, selecione os sellers desejados.</li>
+
+![Organizações Detalhes](//images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/002155ca14e5ad656741eff101ec5cbc/ORGANIZACOES-DETALHES.jpg)
+
+<li>Clique no botão <b>ADICIONAR À ORG</b>.</li>
+
+![Organizações Detalhes 2](//images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/d6152f123a128db9d6803b1899aff232/ORGANIZACOES-DETALHES2.jpg)
+
+<li>Clique no botão <b>Salvar</b>.</li>
+
+A partir deste momento, sempre que a organização realizar uma busca na plataforma VTEX, serão exibidos apenas os produtos dos sellers atribuídos a ela.
+</ol>
+
+<div class="alert alert-warning">
+Organizações compradoras que não criem atribuições de sellers poderão acessar informações e realizar compras de todos os sellers disponíveis no marketplace.</div>
+
+Para mais informações sobre como integrar um novo seller, acesse [Adicionar seller](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392).
+
diff --git a/docs/tutorials/pt/configuring-seo-in-your-store.md b/docs/tutorials/pt/configuring-seo-in-your-store.md
new file mode 100644
index 000000000..fa607886a
--- /dev/null
+++ b/docs/tutorials/pt/configuring-seo-in-your-store.md
@@ -0,0 +1,62 @@
+---
+title: 'Configurando SEO em sua loja'
+id: 1sKskEsjUSvgHyqM8oknVR
+status: PUBLISHED
+createdAt: 2024-04-29T19:07:56.533Z
+updatedAt: 2024-05-03T18:39:56.071Z
+publishedAt: 2024-05-03T18:39:56.071Z
+firstPublishedAt: 2024-04-29T19:26:31.511Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: YRJ73j8mt38D5TUleocQB
+slug: configurando-seo-em-sua-loja
+locale: pt
+legacySlug: configurando-seo-em-sua-loja
+subcategory: 7ogirQ8NClawO2X6xdgCKc
+---
+
+O SEO (Search Engine Optimization) é uma das mais importantes estratégias para que seu site alcance bons posicionamentos orgânicos nas páginas de resultados dos motores de busca. A configuração de tags, metatags e favicon faz parte desse conjunto de estratégias para otimizar a performance do seu site. 
+
+A tag de título ajuda a definir o assunto da página para os motores de busca e influencia diretamente no clique dos usuários nos resultados de pesquisa. A tag de descrição fornece aos usuários uma ideia do que podem encontrar no site. A metatag robots controla o comportamento de rastreamento e indexação dos mecanismos de pesquisa.
+
+Em todas as lojas VTEX IO é possível configurar esses parâmetros nativamente, seguindo as etapas abaixo.
+
+### Passo a passo
+
+#### Tag de título, tag de descrição e metatag robots
+
+1. No Admin VTEX, acesse **Configurações da loja > Storefront > Loja**.
+2. Clique na aba **Geral**.
+3. Preencha os campos conforme as orientações a seguir:
+  - **Nome da loja**: insira o nome da sua loja.
+  - **Habilitar configuração por vínculo**: essa configuração é válida somente para lojas que possuem múltiplos bindings. Ao habilitar essa opção, é possível realizar configurações específicas de tags e metatags para cada um dos bindings da loja. No caso de lojas com um único binding, basta manter essa opção desmarcada.
+  - **Tag de título padrão**: forneça uma descrição concisa e que inclua palavras-chave relevantes. O valor atribuído a esta tag aparece na parte superior da barra de título do navegador quando alguém visita uma página do site da sua loja.
+  - **Tag de descrição meta**: forneça uma breve descrição do conteúdo da página. Deve ser informativa e conter palavras-chave relevantes.
+  - **Metatag robots**: especifique como os motores de busca devem rastrear e indexar uma página específica. Os valores padrão são `index, follow`. Para saber quais outros valores compatíveis com o Google, consulte a [lista de regras válidas](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag?hl=pt-br#directives). 
+
+  ![seo-pt](//images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/538870f8a15ecac304f2c1093764f02d/seo-pt.png)
+
+### Favicons
+
+1. No Admin VTEX, acesse **Configurações da loja > Storefront > Loja**.
+2. Clique na aba **Geral**.
+3. Clique em **Adicionar**.
+
+  ![favicon-pt](//images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/52dc9e3efc6c9cac57f112a40b13158a/favicons-pt.png)
+
+4. Abrirá uma nova tela, que deve ser preenchida conforme as orientações a seguir:
+    - **Relação do favicon**: defina a relação entre a URL configurada no campo
+    - **href do favicon** e o favicon do site. Atribuir o valor `icon`, por exemplo, indica que a URL configurada está relacionada ao ícone do site.
+    - **Tipo de mídia do favicon** (Opcional): especifique o tipo do favicon, seguindo os padrões do HTML e da W3C. Consulte a documentação [HTML Favicon](https://www.w3schools.com/html/html_favicon.asp) para saber mais.
+    - **Tamanho do favicon** (Opcional): indique as dimensões do favicon no formato {largura}x{altura}, como, por exemplo, 180x180.
+    - **href do favicon**: insira a URL completa que aponta para o local onde está armazenado o arquivo do favicon.
+
+    Veja o exemplo a seguir:
+
+    ![relacao-favicon-pt](//images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/b0b372b4db26ab50def96346b04d028b/relacao-favicon-pt.png)
+
+5. Clique em **Aplicar** para que as configurações reflitam em sua loja, o que pode levar alguns minutos.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+O campo <strong>Caminho do termo de busca</strong> é uma configuração legada que era compatível com o <code>vtex.search-resolver@0.x</code>.
+</div>
diff --git a/docs/tutorials/pt/configuring-shipping-promotions.md b/docs/tutorials/pt/configuring-shipping-promotions.md
index bb26c0314..9321f3304 100644
--- a/docs/tutorials/pt/configuring-shipping-promotions.md
+++ b/docs/tutorials/pt/configuring-shipping-promotions.md
@@ -43,37 +43,37 @@ Caso você habilite a opção **Aplicar o desconto somente no frete mais barato*
 ![Aplicar o desconto somente no frete mais barato - PT](//images.contentful.com/alneenqid6w5/2Y0g5Ta6h4VL6uMRQouzjC/94aab036bb00a8162c934780cdfcb1c9/image.png)
 
 #### Resultado
-![saggincaso1.2](https://images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
+![saggincaso1.2](//images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
 
 ### Cenário 2
 
 Caso você desabilite a opção Aplicar o desconto somente no frete mais barato, o desconto do frete será aplicado em todos os fretes disponíveis.
 
 #### Configuração
-![Nenhum frete selecionado -PT](https://images.ctfassets.net/alneenqid6w5/bdzVVgf0w0vxQttjV5bYm/a3a7f5c6af2d23ac3af5a51ca33fe242/image.png)
+![Nenhum frete selecionado -PT](//images.ctfassets.net/alneenqid6w5/bdzVVgf0w0vxQttjV5bYm/a3a7f5c6af2d23ac3af5a51ca33fe242/image.png)
 
 #### Resultado
-![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Cenário 3
 
 Caso você habilite somente a opção **Tipo de Frete** e selecione os tipos de frete desejados, o desconto de frete será aplicado a todos os tipos de frete selecionados.
 
 #### Configuração
-![Tipo de Frete - PT](https://images.ctfassets.net/alneenqid6w5/4cyEZYLm8kQOhIDnB4lvN2/0ff11ad4ee57639a34f2260c40334eb7/image.png)
+![Tipo de Frete - PT](//images.ctfassets.net/alneenqid6w5/4cyEZYLm8kQOhIDnB4lvN2/0ff11ad4ee57639a34f2260c40334eb7/image.png)
 
 #### Resultado
-![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Cenário 4
 
 Caso você habilite as opções **Tipo de Frete** e **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente** e selecione os tipos de frete desejados, o desconto de frete será aplicado para todos os tipos de frete selecionados somente quando o cliente escolher o tipo de frete no checkout.
 
 #### Configuração
-![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - PT](https://images.ctfassets.net/alneenqid6w5/3lL3TwmFFxL8aOW4UvHFER/931f18d33e7c3147ff12a13620f83b45/image.png)
+![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - PT](//images.ctfassets.net/alneenqid6w5/3lL3TwmFFxL8aOW4UvHFER/931f18d33e7c3147ff12a13620f83b45/image.png)
 
 #### Resultado
-![saggincaso3.2](https://images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
+![saggincaso3.2](//images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
 
 Em resumo, a função do checkbox **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente** é de aplicar o desconto somente quando a Transportadora for selecionada.
 
diff --git a/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
new file mode 100644
index 000000000..19957addb
--- /dev/null
+++ b/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
@@ -0,0 +1,88 @@
+---
+title: 'Configurar login com Apple ID (Beta)'
+id: 5qprgEmHYfPTghnYwm0KrV
+status: PUBLISHED
+createdAt: 2023-09-05T17:38:23.553Z
+updatedAt: 2023-09-05T18:22:20.252Z
+publishedAt: 2023-09-05T18:22:20.252Z
+firstPublishedAt: 2023-09-05T18:22:20.252Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configurar-login-com-apple-id-beta
+locale: pt
+legacySlug: configurar-login-com-apple-id-beta
+subcategory: 5uXA9a0laSLMkfbv6jQRDS
+---
+
+<div class="alert alert-info">
+  <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br">nosso Suporte</a>.</p>
+</div>
+
+Na VTEX, não é necessário criar uma conta ou fazer login para realizar uma compra. No entanto, caso o cliente queira efetuar alguma alteração nos dados informados durante a primeira compra, é necessário que ele comprove a posse do email em questão.
+
+Nativamente, a plataforma oferece opções de login com email e senha e com código de acesso enviado para o email do cliente. Também oferecemos integrações opcionais nativas com Apple ID, [Google e Facebook](https://help.vtex.com/pt/tutorial/integracao-google-e-facebook-para-login--tutorials_513), que necessitam ser configuradas. Este guia explica as configurações necessárias para habilitar o login com [Apple ID](https://support.apple.com/pt-br/apple-id) na sua loja:
+
+* [Pré-requisitos](#pre-requisitos)
+* [Criar um registro na Apple](#criar-um-registro-na-apple)
+* [Preencher informações para autenticação](#preencher-informacoes-para-autenticacao)
+* [Validar a configuração](#validar-a-configuracao)
+* [Limitações](#limitacoes)
+
+## Pré-requisitos
+
+Antes de começar a configurar o login com Apple ID na sua loja, é necessário ter um [Apple ID](https://support.apple.com/pt-br/apple-id) e estar inscrito no [Apple Developer Program](https://developer.apple.com/programs/).
+
+## Criar um registro na Apple
+
+Para configurar a integração de login com a Apple, é necessário criar credenciais de OAuth 2.0 (protocolo utilizado para integração) nesse serviço. Para isso, siga as instruções do nosso guia para desenvolvedores [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login).
+
+## Preencher informações para autenticação
+
+Uma vez concluído o registro junto à Apple, você precisa habilitar na sua loja a opção de login por esse provedor, seguindo as instruções abaixo. Tenha em mãos as credenciais obtidas na etapa de registro.
+
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email.
+2. Clique em **Configurações da conta > Autenticação**.
+
+    Você será direcionado(a) para a aba **Loja virtual** da página **Autenticação**, que lista os métodos de login disponíveis na sua loja.
+
+3. Na linha **Apple**, clique em `Configurar`.
+4. Preencha os campos de configuração com as [credenciais previamente registradas na Apple](#criar-um-registro-na-apple):
+
+    * **Key ID:** identificação da chave privada gerada pela Apple que será utilizada pela VTEX para gerar o [OAuth client secret](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/).
+    * **Team ID:** identificação da sua equipe no [Apple Developer Portal](https://developer.apple.com/). 
+    * **Service ID:** identificação do seu serviço na Apple, que será usada como [OAuth client_id](https://www.oauth.com/oauth2-servers/client-registration/client-id-secret/).
+    * **P8 Certificate:** chave privada salva em um arquivo de texto no formato `.p8`, gerado somente uma vez pela Apple durante a criação da chave.
+
+    Para entender como obter essas credenciais, confira o guia para desenvolvedores [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login).
+
+    ![apple-id-setup-pt](//images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/35e10840c391c7f5abfde67cbc7acfa3/apple-id-setup-es.png)
+
+5. Clique em `Salvar`.
+6. Clique em `Provedores da loja virtual` para retornar para a página anterior.
+7. Clique no _switch_ <i class="fas fa-toggle-on"></i> para ativar o uso da Apple como provedor de login.
+
+## Testar login com Apple ID
+
+Com tudo configurado, você já pode testar o login. Recomendamos que faça isso já através da URL final que seus usuários utilizarão para acessar sua loja. Ao tentar efetuar login, a opção de utilizar a ID da Apple deve estar disponível.
+
+1. Acesse o site da sua loja e clique em `Entrar` para fazer login.
+2. Clique em `Entrar com Apple`. Você será conduzido(a) à tela de login da Apple.
+3. Insira seu ID e senha da Apple.
+4. Realize a autenticação de dois fatores, se solicitada.
+5. Escolha se deseja compartilhar seu email com o app ou [ocultar o seu email](https://support.apple.com/pt-br/HT210425) e clique em `Continuar`. Recomendamos compartilhar o email, porque existem [limitações](#limitacoes) com relação ao email oculto na VTEX.
+
+<div class="alert alert-info">
+  <p>A opção por compartilhar ou não o email só aparece no primeiro acesso à loja com o Apple ID. Nas demais vezes, é necessário apenas clicar em <code>Continuar</code>. Para redefinir a opção de compartilhamento do email, visite o <a href="https://appleid.apple.com/br/">gerenciamento de Apple ID</a>, revogue a autorização da loja e volte a fazer login.</p>
+</div>
+
+Feito isso, você estará autenticado(a) na loja.
+
+## Limitações
+
+Observe as limitações atuais do login com Apple ID em lojas VTEX:
+
+* O Message Center não é compatível com emails de usuários Apple, ou seja, os emails configurados na ferramenta não serão enviados para usuários que fizerem login com Apple ID.
+* Caso o usuário opte por usar o recurso de [Ocultar Meu E-mail](https://support.apple.com/pt-br/HT210425) da Apple, a VTEX irá gerar uma nova conta toda vez que o usuário fizer login.
+
+  Isso significa que se alguém fizer login inicialmente com um email e senha, realizar um pedido e posteriormente fizer login utilizando a Apple ID com o recurso de email oculto ativado, a VTEX criará uma conta separada. Essa nova conta não terá relação com a conta original e não permitirá acessar histórico de pedidos passados ou outras informações do usuário. Essa ação não pode ser desfeita.
diff --git a/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md b/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md
index 058df1089..0ac28ebf9 100644
--- a/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md
+++ b/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md
@@ -3,8 +3,8 @@ title: 'Configurar a afiliação de gateway Stripe'
 id: fwF2wk2FQKrODrWWkvSLO
 status: PUBLISHED
 createdAt: 2021-10-25T16:01:40.789Z
-updatedAt: 2023-03-22T19:17:05.286Z
-publishedAt: 2023-03-22T19:17:05.286Z
+updatedAt: 2024-04-25T12:58:35.923Z
+publishedAt: 2024-04-25T12:58:35.923Z
 firstPublishedAt: 2021-10-25T17:34:52.274Z
 contentType: tutorial
 productTeam: Financial
@@ -32,30 +32,40 @@ Para processar seus pagamentos com a Stripe, você precisa:
 
 Siga os passos abaixo para a configuração no ambiente VTEX.
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Em **Afiliações de gateway**, clique no ícone "**+**".
-3. Busque pelo conector **StripeConnector**, e clique sobre ele.
-4. Na página seguinte, preencha os campos abaixo com as seguintes informações:
-<ol><br/>
-  <li><strong>Application Key:</strong> Chave publicável que você obteve no <a href="https://dashboard.stripe.com/">dashboard da sua conta na Stripe</a>.
-  <li><strong>Application Token:</strong> Chave secreta que você obteve no <a href="https://dashboard.stripe.com/">dashboard da sua conta na Stripe</a>.
-</ol>
-5. Clique em **Salvar**.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __StripeConnector__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos abaixo com as seguintes informações:
+<br>
+<ul>
+<br>
+    	<li><b>Chave de aplicação</b>: Chave publicável que você obteve no <a href="https://dashboard.stripe.com">dashboard da sua conta na Stripe</a>.</li>
+    	<li><b>Token de aplicação</b>: Chave secreta que você obteve no <a href="https://dashboard.stripe.com">dashboard da sua conta na Stripe</a>.</li>
+</ul>
+5. Clique em __Salvar__.
 
 Após a configuração no ambiente VTEX, você também precisa configurar o Webhook na sua conta da Stripe.
 
 1. Acesse o [dashboard da sua conta na Stripe](https://dashboard.stripe.com/).
-2. Clique no botão **Desenvolvedores**.
-3. Clique na aba **Webhooks**.
-4. Clique no botão **Adicione um endpoint**.
-5. No campo **URL do endpoint**, adicione a URL de endpoint da sua loja VTEX no formato `https://{nome-da-conta}.myvtex.com/_v/notifications` substituindo `{nome-da-conta}` pelo nome da sua conta VTEX.
-6. Clique em **+ Selecionar eventos**.
-7. Adicione os eventos que devem ser escutados.
-8. Clique em **Adicionar endpoint**.
+2. Clique no botão __Desenvolvedores__.
+3. Clique na aba __Webhooks__.
+4. Clique no botão __Adicione um endpoint__.
+5. No campo __URL do endpoint__, adicione a URL de endpoint da sua loja VTEX no formato `https://{nome-da-conta}.myvtex.com/_v/notifications` substituindo `{nome-da-conta}` pelo nome da sua conta VTEX.
+6. Clique em __+ Selecionar eventos__.
+7. Clique nas categorias e selecione os eventos desejados. Caso não tenha certeza sobre quais eventos devem ser adicionados, entre em contato com o suporte da Stripe para que possam ajudá-lo neste tipo de configuração.
+8. Clique em __Adicionar eventos__.
+9. Clique em __Adicionar endpoint__.
+
+<div class="alert alert-info">
+  <p>Caso você deseje realizar transações com cartão de crédito na Stripe, é necessário abrir um ticket na própria Stripe da seguinte maneira:</p>
+  <p>- Solicitar a liberação da função "raw card data", indicando que a VTEX e a Stripe são parceiros de pagamento.</p>
+  <p>- Encaminhar em anexo o AOC (Attestation of Compliance for Onsite Assessments – Service Providers) da VTEX. Para verificar a versão mais recente do AOC VTEX, acesse a página de <a href="https://vtex.com/br-pt/compliance/certifications">certificações da VTEX</a> e baixe o arquivo na seção PCI.</p>
+  <p>As ações acima evitarão que erros relacionados a transmissão de dados sensíveis ocorram na integração entre a Stripe e a VTEX.</p>
+</div>
 
 ## Configurar condição de pagamento
 
-Ao concluir as etapas indicadas, a Stripe estará configurada na sua loja. Assim, ao cadastrar uma condição de pagamento, ela vai estar disponível no campo **Processar com a afiliação** (desde que o meio de pagamento seja compatível com a Stripe). 
+Ao concluir as etapas indicadas, a Stripe estará configurada na sua loja. Assim, ao cadastrar uma condição de pagamento, ela vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com a Stripe). 
 
 Para definir condições de pagamento, acesse o artigo [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455).
 
@@ -63,11 +73,12 @@ Para definir condições de pagamento, acesse o artigo [Configurar condições d
 
 O conector Stripe permite adicionar o Google Pay como método de pagamento no checkout da sua loja.Com o conector Stripe configurado, você pode adicionar o Google Pay com os seguintes passos:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Em **Condições de pagamento**, clique no ícone “**+**”.
-3. Busque pela condição **Google Pay**, e clique sobre ele.
-4. Clique no botão Status para ativar essa condição de pagamento.
-5. Clique em **Salvar**.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Em __Condições de pagamento__, clique no ícone `+`
+3. Clique sobre a opção __Google Pay__.
+4. Ative a condição no campo __Status__.
+5. Em __Processar com a afiliação__, selecione a opção __StripeConnector__.
+6. Clique em __Salvar__.
 
 Após esse procedimento, o Google Pay aparecerá no checkout da loja como um dos métodos de pagamento disponíveis.
 
@@ -82,24 +93,24 @@ O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e
 Com o conector Stripe configurado, você pode adicionar o Apple Pay com os seguintes passos:
 
 1. Acesse o [dashboard da sua conta na Stripe](https://dashboard.stripe.com/settings/payments) na seção de configuração de pagamentos.
-2. Em **Settings**, clique em **Payment Methods**.
-3. Clique em **Apple Pay > Configure** e depois em **Add to new domain**.
+2. Em __Settings__, clique em __Payment Methods__.
+3. Clique em __Apple Pay > Configure__ e depois em __Add to new domain__.
 4. Insira o domínio público do website da sua loja.
-5. Clique em **Baixar arquivo de verificação** para salvá-lo em seu dispositivo.
+5. Clique em __Baixar arquivo de verificação__ para salvá-lo em seu dispositivo.
 6. Crie as credenciais [appkey e apptoken](https://help.vtex.com/pt/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet#).
 7. Faça uma chamada ao endpoint para enviar o arquivo de verificação baixado anteriormente, adicionando no header as credenciais criadas e o endereço do seu domínio público (https://{{dominioPublicodoSite}}/well-known/raw/apple-developer-merchantid-domain-association).
-8. Clique em **Add**.
-9. Acesse o **Admin** VTEX.
-10. Clique em **Pagamentos**.
-11. Em seguida, clique em **Configurações**.
-12. Na aba **Condições de pagamento**, clique no botão **+**.
-13. Clique em **Apple Pay**.
-14. Preencha o campo **Nome da regra** com um nome de sua preferência para identificação.
-15. Clique no botão **Status** para ativar essa condição de pagamento.
-16. No campo **Processar com a afiliação**, selecione a opção Stripe.
-17. Se houver um antifraude configurado na sua loja, você pode ativá-lo para essa condição de pagamento marcando a caixa **Usar Antifraude**.
+8. Clique em __Add__.
+9. Acesse o __Admin VTEX__.
+10. Clique em __Pagamentos__.
+11. Em seguida, clique em __Configurações__.
+12. Na aba __Condições de pagamento__, clique no botão `+`.
+13. Clique em __Apple Pay__.
+14. Preencha o campo __Nome da regra__ com um nome de sua preferência para identificação.
+15. Clique no botão __Status__ para ativar essa condição de pagamento.
+16. No campo __Processar com a afiliação__, selecione a opção Stripe.
+17. Se houver um antifraude configurado na sua loja, você pode ativá-lo para essa condição de pagamento marcando a caixa __Usar Antifraude__.
 18. Escolha se os pagamentos serão à vista ou parcelados.
 19. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais).
-20. Clique em **Salvar**.
+20. Clique em __Salvar__.
 
 Após esse procedimento, o Apple Pay aparecerá no checkout da loja como um dos métodos de pagamento disponíveis.
diff --git a/docs/tutorials/pt/configuring-the-additional-freight.md b/docs/tutorials/pt/configuring-the-additional-freight.md
index db7999550..3def2edc2 100644
--- a/docs/tutorials/pt/configuring-the-additional-freight.md
+++ b/docs/tutorials/pt/configuring-the-additional-freight.md
@@ -22,7 +22,7 @@ O adicional no frete é calculado sobre o valor final do frete, e não sobre o v
 
 O valor da tabela de frete + os demais adicionais ([por peso ou por valor](https://help.vtex.com/pt/tutorial/como-funciona-o-adicional-de-frete)) * o valor cadastrado no campo.
 
-![adicionalfrete3 PT](https://images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
+![adicionalfrete3 PT](//images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
 
 Nesse caso, o valor inserido no campo __Valor adicional__, é o valor percentual que será somado ao valor final calculado do frete. Por exemplo: se o frete, com todos seus adicionais já calculados, der R$20,00 e o valor cadastrado no campo Adicional nos Fretes for 10, significa que será acrescentando R$2,00 aos R$20,00 do frete, totalizando R$ 22,00 a ser cobrado ao cliente pelo frete. Essa é uma maneira simples de conseguir uma margem sobre os fretes das compras.
 
diff --git a/docs/tutorials/pt/configuring-the-scheduled-delivery.md b/docs/tutorials/pt/configuring-the-scheduled-delivery.md
index 53640ca4f..9092f3b67 100644
--- a/docs/tutorials/pt/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/pt/configuring-the-scheduled-delivery.md
@@ -31,7 +31,7 @@ Em **Estoque & entrega**, acesse **Painéis** e escolha a **Transportadora** des
 
 Em **Tipo da entrega**, clique  **Entrega agendada**.
 
-![entrega-agendada pt](https://images.ctfassets.net/alneenqid6w5/6bbP1sy4xiKUSmYAWGWgMq/c6370ec0630605c537bea7e65e1d15a1/entrega-agendada_pt.png)
+![entrega-agendada pt](//images.ctfassets.net/alneenqid6w5/6bbP1sy4xiKUSmYAWGWgMq/c6370ec0630605c537bea7e65e1d15a1/entrega-agendada_pt.png)
 Para entender melhor como cadastrar os demais campos da transportadora, veja também nossa documentação sobre [cadastro de transportadora](http://help.vtex.com/pt/tutorial/gerenciar-transportadora).
 
 Nesta estrutura, temos os seguintes dados:
diff --git a/docs/tutorials/pt/configuring-the-store-domain.md b/docs/tutorials/pt/configuring-the-store-domain.md
new file mode 100644
index 000000000..c24fe8d9d
--- /dev/null
+++ b/docs/tutorials/pt/configuring-the-store-domain.md
@@ -0,0 +1,104 @@
+---
+title: 'Configurar o domínio da loja'
+id: tutorials_2450
+status: PUBLISHED
+createdAt: 2017-04-27T21:55:00.603Z
+updatedAt: 2024-03-12T19:53:14.012Z
+publishedAt: 2024-03-12T19:53:14.012Z
+firstPublishedAt: 2017-04-27T23:03:51.625Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configurar-o-dominio-da-loja
+locale: pt
+legacySlug: configurando-dominios-no-license-manager
+subcategory: yMp6sKDiJEi66CGAIQ4ma
+---
+
+As configurações relacionadas ao domínio são necessárias para que um endereço web seja corretamente direcionado a uma loja VTEX. Neste guia, explicamos:
+
+* [Estrutura do endereço da loja](#estrutura-do-endereco-da-loja)
+* [Regras para o host principal](#regras-para-o-host-principal)
+* [Como cadastrar um novo host](#cadastrar-um-novo-host)
+* [Como mudar o host de uma loja ativa](#mudar-o-host)
+
+## Estrutura do endereço da loja
+
+O endereço da loja é composto pelos elementos ilustrados a seguir:
+
+![url-diagram-pt (3)](//images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/4d3a9763fcd76907f3587f77d8cc9947/url-diagram-pt__3_.png)
+
+| Elemento | Descrição | Exemplo |
+|---|---|---|
+| Protocolo | Protocolo de comunicação utilizado na internet. | `https://` |
+| Subdomínio | Prefixo adicionado ao nome de domínio. | `www` |
+| Domínio | Nome exclusivo que serve para localizar e identificar sua loja na web. | `mystore` |
+| Domínio de nível superior (TLD) | Sufixo após o ponto final de um nome de domínio. | `com` |
+| Nome de domínio / Domínio puro / Domínio raiz | Domínio + domínio de nível superior. | `mystore.com` |
+| Host | Subdomínio + domínio + domínio de nível superior. | `www.mystore.com` |
+
+Uma vez definido o domínio da sua loja, você precisa configurar o host principal no Admin VTEX para realizar a comunicação entre o endereço e o conteúdo da loja.
+
+## Regras para o host principal
+
+Antes de prosseguir com a configuração dos endereços da sua loja, considere as seguintes práticas para garantir uma implementação bem-sucedida:
+
+* **Provedores de CDN:** A VTEX usa dois provedores de CDN nas lojas: **Cloudfront** e **Azion**. É importante que o domínio da sua loja não esteja cadastrado nestes serviços no momento do apontamento. Do contrário, haverá falha no provisionamento de CDN para sua loja e, consequentemente, no go-live. Portanto, se você tem o domínio da loja registrado na plataforma da Cloudfront ou Azion, remova este registro antes de realizar o apontamento de DNS para a VTEX.
+* **Endereço principal:** A loja deve ter um único host principal, que irá apontar para os servidores da VTEX. Este host **deve conter um subdomínio**, que pode ser `www` ou outros.
+* **Endereços adicionais:** Qualquer endereço adicional, seja com um domínio diferente ou uma versão sem subdomínios, deve ser redirecionado para o único host principal, conforme descrito em [Redirecionamentos](#redirecionamentos).
+
+### Exemplos de host
+
+Confira exemplos de host abaixo e observe quais podem ser utilizados como host principal:
+
+| Exemplo de host | Pode ser utilizado como host (✔️) ou não (❌) | Explicação |
+|---|---|---|
+| `www.minhaloja.com` | ✔️ | Contém o subdomínio `www`. |
+| `minhaloja.com` | ❌ | Não contém subdomínio. Para configurar o acesso por esse endereço, é necessário configurar um host com subdomínio como `www.minhaloja.com` e, em seguida, criar um redirecionamento. Leia [Melhores práticas para acessar a loja sem www](https://help.vtex.com/pt/tutorial/configuring-access-without-www--tutorials_4278) para mais detalhes. |
+| `loja.minhamarca.com` | ✔️ | Contém o subdomínio `loja`. |
+| `www.loja.minhamarca.com` | ✔️ | Contém dois subdomínios: `www` e `loja`. |
+
+### Redirecionamentos
+
+Para garantir que sua loja seja acessível por meio de diferentes URLs, tais como `www.minhaloja.com` e `minhaloja.com`, deve-se [configurar um único host principal](#cadastrar-um-novo-host) e redirecionar os endereços adicionais para o endereço principal. Saiba mais sobre redirecionamentos:
+
+* [Redirecionamento de outros endereços](https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ)
+* [Melhores práticas para acessar a loja sem www](https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278)
+
+Note que é recomendável implementar um único host na sua loja.
+
+## Cadastrar um novo host
+
+Para cadastrar um novo host, ele deve estar de acordo com as práticas apresentadas na seção [Regras para o host principal](#regras-para-o-host-principal). Siga as instruções abaixo:
+
+1. Na barra superior do Admin VTEX, clique no avatar do seu perfil, marcado pela inicial do seu email.
+2. Clique no botão **Configurações da conta**.
+3. Clique em **Conta**.
+4. Clique na aba **Lojas**.
+5. Clique no botão de ações correspondente à loja em que deseja cadastrar o host e clique em `Editar`.
+6. Insira o host no campo **Hosts**. Por exemplo,` www.minhaloja.com`.
+7. Clique no botão `Adicionar`.
+8. Clique no botão `Salvar`.
+
+Após essas etapas, será possível [configurar o apontamento de DNS para a VTEX](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
+
+<div class="alert alert-warning">
+  <p>Lojas <a href="https://www.faststore.dev/">FastStore</a> também precisam configurar um endereço com o subdomínio <code>secure</code>. Acesse o guia <a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns">Configuring external DNS for a custom domain</a> para mais detalhes.</p>
+</div>
+
+<div class="alert alert-danger">
+  <p>Caso a sua operação possua mais de uma conta VTEX ou <a href="https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510">subcontas</a>, não troque o host de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.</p>
+</div>
+
+## Mudar o host
+
+A plataforma VTEX é preparada para suportar mudanças de host sem impactos negativos. Caso seja necessário alterar o host da loja, siga o passo a passo abaixo:
+
+1. Crie novas entradas host para a loja desejada, seguindo o passo a passo descrito em [Cadastrar um novo host](#cadastrar-um-novo-host). Nesse momento, o DNS do novo domínio ainda não deve estar apontado para a VTEX.
+2. No Admin VTEX, verifique as configurações do Checkout em **Configurações da Loja > Storefront > Checkout**, conforme descrito em [Configurar template no Smartcheckout](https://help.vtex.com/pt/faq/configurar-template-no-smartcheckout/). Esse passo é fundamental para que o Checkout continue funcionando após a mudança. 
+
+    É necessário conferir se os sites configurados estão relacionados à conta cadastrada em **Configurações da conta > Contas**. Confira [Gerenciamento da conta](https://help.vtex.com/pt/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq) para mais detalhes.
+
+3. Aponte o DNS do novo domínio para a VTEX. Leia mais sobre [apontamento de DNS](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex/).
+4. Se a sua loja utiliza [VTEX IO - Store Framework](https://developers.vtex.com/docs/guides/storefront-implementation) ou [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), entre em contato com o [suporte VTEX](https://help.vtex.com/pt/support) e solicite apontamento interno, informando o novo domínio. Uma vez aberto o chamado, o time de suporte tem até três dias úteis para analisar as configurações e realizar o apontamento.
+5. Após a confirmação de apontamento interno e propagação de DNS do novo host, exclua os hosts antigos, mantendo apenas o novo.
diff --git a/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md b/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md
index 0f3c1bca9..6f0c984fa 100644
--- a/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md
+++ b/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md
@@ -3,8 +3,8 @@ title: 'Configurar a afiliação de gateway Tuna'
 id: 5Db0j4pE76ma9pUvYuAhfF
 status: PUBLISHED
 createdAt: 2021-07-07T14:47:34.162Z
-updatedAt: 2023-03-26T21:51:52.610Z
-publishedAt: 2023-03-26T21:51:52.610Z
+updatedAt: 2024-01-23T21:47:01.684Z
+publishedAt: 2024-01-23T21:47:01.684Z
 firstPublishedAt: 2021-07-07T14:57:45.358Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: configurar-a-afiliacao-de-gateway-tuna
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, você pode configurar a sua loja com a afiliação de gateway Tuna para receber pagamentos por meio de: boleto, cartões de débito, crédito, PIX e Bitcoin.
+Na VTEX, você pode configurar a sua loja com o gateway Tuna para receber pagamentos por meio de: boleto, cartões de débito, crédito, PIX e Bitcoin.
 
 <div class="alert alert-warning">
   A integração da sua loja com a Tuna é feita por meio de uma <b>Application Key</b> e <b>Application Token.</b> Os dados de acesso para obter essas informações e permitir as configurações na VTEX serão enviados após a criação da sua conta. Para isso, preencha <a href="https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform">este formulário</a> e aguarde o retorno da Tuna com mais detalhes.
@@ -23,9 +23,9 @@ Na VTEX, você pode configurar a sua loja com a afiliação de gateway Tuna para
 
 Após ter criado sua conta e obtido as __Application Key__ e __Token__, siga as etapas abaixo para configurar a Tuna na sua loja:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Tuna__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Tuna__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Tuna.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/configuring-vtex-marketplace.md b/docs/tutorials/pt/configuring-vtex-marketplace.md
index dbe6d0912..e59c75c90 100644
--- a/docs/tutorials/pt/configuring-vtex-marketplace.md
+++ b/docs/tutorials/pt/configuring-vtex-marketplace.md
@@ -3,12 +3,12 @@ title: 'Configurar marketplace VTEX'
 id: 7splyp5MqIyt2Iyz5jsNzb
 status: PUBLISHED
 createdAt: 2022-01-26T21:27:16.808Z
-updatedAt: 2023-04-17T22:04:41.917Z
-publishedAt: 2023-04-17T22:04:41.917Z
+updatedAt: 2024-05-23T15:18:17.648Z
+publishedAt: 2024-05-23T15:18:17.648Z
 firstPublishedAt: 2022-01-26T23:06:58.565Z
 contentType: tutorial
 productTeam: Channels
-author: 0QBQws7rk0t5Mnu8fgfUv
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: configurar-marketplace-vtex
 locale: pt
 legacySlug: configurar-marketplace-vtex
@@ -75,7 +75,7 @@ Sellers diferentes podem ser exibidos durante a experiência de compra no seu ma
 - **Seller identificável:** o seller é visível no *storefront* do seu marketplace e escolhido pelo consumidor durante a experiência de compra no buy box.  
 - **Seller não identificável (white label):** [sellers white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label) são contas franquia na VTEX, ocultos na experiência de compra e selecionados automaticamente pelo sistema do checkout para o fulfillment.  
 
-Para adicionar um seller não identificável (white label), é necessário ter esse modelo previsto no contrato com a VTEX. Uma vez ajustado o contrato com o representante comercial da VTEX responsável pelo seu marketplace, solicite a adição de uma conta franquia seguindo as instruções em [O que são conta franquia e seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#o-que-e-uma-conta-franquia). Toda conta franquia é criada como seller white label e não é possível mudar o tipo de seller após a sua criação. Saiba mais em [Adicionar sellers](https://help.vtex.com/pt/tutorial/adding-a-seller--tutorials_392). 
+Para adicionar um seller não identificável (white label), é necessário ter esse modelo previsto no contrato com a VTEX. solicite a adição de uma conta franquia seguindo as instruções em [Solicitar criação de conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl#solicitar-criacao-de-conta-franquia). Toda conta franquia é criada como seller white label e não é possível mudar o tipo de seller após a sua criação. Saiba mais em [Adicionar sellers](https://help.vtex.com/pt/tutorial/adding-a-seller--tutorials_392). 
 
 ### Localização
 
diff --git a/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md b/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md
index d1859c7b0..c520dd44b 100644
--- a/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md
+++ b/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md
@@ -25,7 +25,7 @@ Para isto, no Admin VTEX, acesse **Storefront > Layout > CMS** e clicar no layou
 
 O botão fica no canto superior direito, como mostra a imagem abaixo.
 
-!![copiar layout](https://images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
+!![copiar layout](//images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
 
 O sistema vai perguntar para qual web site você quer copiar o layout.
 
diff --git a/docs/tutorials/pt/coupons-list-beta.md b/docs/tutorials/pt/coupons-list-beta.md
index e9afa3892..2619a0203 100644
--- a/docs/tutorials/pt/coupons-list-beta.md
+++ b/docs/tutorials/pt/coupons-list-beta.md
@@ -31,7 +31,7 @@ A partir desta página, você pode:
 
 Para acessá-la no Admin VTEX, clique em **Promoções > Cupons**.
 
-![lista-cupons](https://images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/74d61d0b59d9b69728c62b5e1dc5bae7/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-28-18_42_26.png)
+![lista-cupons](//images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/74d61d0b59d9b69728c62b5e1dc5bae7/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-28-18_42_26.png)
 
 A seguir, confira a descrição dos componentes e ações incluídos na página.
 
@@ -83,7 +83,7 @@ O arquivo gerado contém as informações descritas a seguir.
 
 Veja um exemplo de arquivo CSV exportado a seguir:
 
-![cupons-exportados](https://images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
+![cupons-exportados](//images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
 
 #### Exportar códigos de um grupo de cupons
 
@@ -100,13 +100,13 @@ Para visualizar ou exportar todos os códigos de um grupo, é necessário seguir
     * <i class="far fa-clone"></i> **Copiar tudo:** permite copiar os códigos gerados para a sua área de transferência. Também é possível copiar cada código clicando sobre ele.
     * **Exportar:** permite exportar os códigos gerados para um arquivo CSV. O arquivo exportado contém uma coluna, com um código por linha.
 
-![exportar-cupons](https://images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/27a207fd3f7adc0ebe4493cd5ea15f0f/exportarcupons.PNG)
+![exportar-cupons](//images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/27a207fd3f7adc0ebe4493cd5ea15f0f/exportarcupons.PNG)
 
 ### Ver uso dos cupons
 
 Para visualizar o total de cupons ativos e a cota de espaço restante para novos cupons, clique em <i class="fas fa-chart-line"></i> `Uso dos cupons`.
 
-![uso-dos-cupons](https://images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7c4529a241f54d4e3203ce5c1237bdfc/usodoscupons.PNG)
+![uso-dos-cupons](//images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7c4529a241f54d4e3203ce5c1237bdfc/usodoscupons.PNG)
 
 O número máximo de cupons ativos que você pode ter é 5 mil. Para liberar espaço, você pode arquivar cupons a partir da [Lista de cupons](#lista-de-cupons). Caso precise aumentar o limite de cupons ativos, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
@@ -155,13 +155,13 @@ O modal **Ver detalhes de uso** apresenta os dados de utilização de cada cupom
 
     Esta seção também apresenta a lista de pedidos em que o código foi utilizado e permite buscar pelo número de um pedido. Ao clicar no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-![ver-detalhes-uso](https://images.ctfassets.net/alneenqid6w5/4dVuN6fKsu3WRsMSQbZT4e/648e8a2216470558beddea7e9fb0087b/Group_1__4_.png)
+![ver-detalhes-uso](//images.ctfassets.net/alneenqid6w5/4dVuN6fKsu3WRsMSQbZT4e/648e8a2216470558beddea7e9fb0087b/Group_1__4_.png)
 
 * **Uso geral dos códigos de cupom** (grupos de cupons): exibe a quantidade total de usos dos códigos de um grupo de cupons e a quantidade de usos restantes, caso você tenha limitado a quantidade de usos.
 
     Esta seção também apresenta a lista de códigos do grupo de cupons e permite buscar por um código específico. Ao clicar em um código, você tem acesso à lista de pedidos em que o código foi utilizado e pode buscar pelo número de um pedido. Ao clicar no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-![selecione-o-codigo-grupo-cupons](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png)
+![selecione-o-codigo-grupo-cupons](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/creating-a-campaign-audience.md b/docs/tutorials/pt/creating-a-campaign-audience.md
index d7b9c9f95..140099d23 100644
--- a/docs/tutorials/pt/creating-a-campaign-audience.md
+++ b/docs/tutorials/pt/creating-a-campaign-audience.md
@@ -3,8 +3,8 @@ title: 'Criar Audiência de campanha'
 id: 6cnuDZJzIkIeocewAQQK4K
 status: PUBLISHED
 createdAt: 2018-12-02T18:34:21.663Z
-updatedAt: 2023-03-31T13:38:38.613Z
-publishedAt: 2023-03-31T13:38:38.613Z
+updatedAt: 2023-10-31T19:23:55.713Z
+publishedAt: 2023-10-31T19:23:55.713Z
 firstPublishedAt: 2018-12-03T16:51:36.457Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -69,7 +69,7 @@ Após clicar em `Criar novo público-alvo`, você precisa seguir as instruções
     * **ou:** a audiência de campanha será composta por clientes que se encaixarem em qualquer um dos públicos-alvo.
     * **e:** a audiência de campanha será composta por clientes que se encaixarem em todos os públicos-alvos, somando seus critérios.
 
-![publico-alvo-e-ou-pt](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
+![publico-alvo-e-ou-pt](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
 
 ### Defina seu público-alvo
 
@@ -85,13 +85,12 @@ Após clicar em `Criar novo público-alvo`, você precisa seguir as instruções
 
 Exemplo: participam do público-alvo os itens cuja marca é __Nike__, conforme ilustrado a seguir. A configuração também indica que pelo menos 3 itens precisam se enquadrar nesses critérios. Portanto, um cliente precisa ter no carrinho pelo menos 3 itens que se encaixam nesse cenário para participar do público-alvo.
 
-![exemplo-marca-publico-alvo-pt](https://images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/e92e92a79b28abc9bbfe84f886c17c8d/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_12_45_1.png)
+![exemplo-marca-publico-alvo-pt](//images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/e92e92a79b28abc9bbfe84f886c17c8d/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_12_45_1.png)
 
 ### Condições para seu público-alvo ser aplicado
 
 * **Valor mínimo do pedido:** valor mínimo que o total de itens no carrinho do cliente precisa ter. Este total considera a soma do preço dos produtos no carrinho que atendem aos critérios da audiência de campanha.
 * **Valor máximo do pedido:** valor máximo que o total de itens no carrinho do cliente pode ter. Este total considera a soma dos preços dos produtos no carrinho que atendem aos critérios da audiência de campanha.
-* **Usar histórico em promoção:** permite que o histórico de compras do cliente seja considerado ao avaliar se ele faz parte do público-alvo ou não. Caso selecionada, essa opção exige que você escolha o período de tempo em que o histórico deve ser considerado. Você pode adicionar datas específicas ou contar dias a partir da data atual.
 * **Valor do item entre __ e __:** preço mínimo e máximo que cada item no carrinho pode ter. A audiência de campanha será ativada se o valor do item atender ao intervalo de valores preenchidos.
 * **Restrição de Promoção por BIN:** a audiência de campanha será ativada caso o _Bank Identification Number_ (BIN) do cartão de crédito esteja entre os caracteres preenchidos. O BIN corresponde aos 6 ou 8 números iniciais de um cartão e serve para identificar o banco e a bandeira do cartão.
 * **Marketing Tags:** campo utilizado para restringir a ativação da audiência de campanha caso a compra seja realizada pelo [módulo de Assinaturas da VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#).
diff --git a/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md b/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
index c72e9e966..0f9cc7491 100644
--- a/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
+++ b/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'Criar ponto de retirada de contingência para garanti-lo como opção no checkout '
 id: 3mowqWEfjyM2g6WoWgE0Ao
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-04-01T16:02:02.437Z
-updatedAt: 2020-06-20T04:56:48.306Z
-publishedAt: 2020-06-14T22:20:33.622Z
+updatedAt: 2023-08-01T21:35:48.449Z
+publishedAt: 2023-08-01T21:35:48.449Z
 firstPublishedAt: 2019-01-25T17:26:19.150Z
 contentType: tutorial
 productTeam: Shopping
@@ -21,15 +21,20 @@ Se seu cliente final compra um produto em qualquer dos seus canais (online ou lo
 
 No entanto, você pode preferir que essa loja funcione como ponto de retirada __mesmo se ela não tiver estoque__. Para isso, sua logística precisa garantir que o produto chegará a essa loja a partir de outro estoque - por exemplo, a partir do estoque do e-commerce. Neste caso, você precisa ter uma política de envio no e-commerce em que esteja configurado o ponto de retirada da loja física.
 
-![contingency pickup](https://images.ctfassets.net/alneenqid6w5/7sxWH5eDPpCmNlEPfHiZF1/7a10b60e1273d58d9c2ca7610a9ba888/contingency_pickup.png)
+![Criar ponto de retirada de contingência para garanti-lo como opção no checkout](//images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/53b839763aa9f25178d599d78eb73203/diagrama-como-criar-um-ponto-de_contigencia-pt.jpg)
 
 ## Como implementar um ponto de retirada de contingência
 
-Siga estes passos para implementar um estoque de contingência:
-- No painel administrativo do e-commerce ou da loja que você deseja usar como fallback - ou seja, a loja de cujo estoque sairão os produtos para abastecer o ponto de retirada -, configure um novo ponto de retirada com as informações da loja física desejada.
-- Ainda no e-commerce ou na loja de fallback, crie uma nova política de envio. Essa política de envio precisa ter exatamente o __mesmo tipo de entrega__ já configurado na logística de retirada que você utiliza na loja física onde os produtos serão retirados.
-- Associe o novo ponto de retirada criado a essa política de envio.
+Para implementar um ponto de retirada de contingência, é necessário configurar os seguintes passos:
+
+1. No Admin VTEX, [cadastre um novo ponto de retirada](https://help.vtex.com/pt/tutorial/cadastro-de-pontos-de-retirada--2R5ClQiwe4KoSQgsuiOw4E) na loja, que possua o estoque de onde sairão os produtos, para abastecer esse ponto de retirada.
+2. [Crie uma nova política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio), cujo o tipo de envio tenha o mesmo nome do tipo de envio já configurado na polítca utilizado na loja física, onde os produtos serão retirados.
+3. Associe esta nova política ao ponto de retirada recém-criado.
+
+Dessa forma, você terá duas rotas de logística de entrega: uma logística com o estoque da loja física, e uma logística diferente com o estoque de outra loja.
+
+Quando o cliente escolher esse ponto de retirada no checkout, o sistema irá proceder da seguinte forma:
+
+- Se houver estoque local, o prazo de entrega será mais currto. Nesse caso, será selecionado o ponto de retirada principal.
+- Caso não haja estoque local, a rota logística configurada como contingência será selecionada.
 
-<div class="alert alert-info">
-Com isso, você terá duas rotas logísticas com o mesmo pickup point: uma delas, com estoque local da loja física; a outra com o estoque de outro canal (e-commerce ou outra loja física). Quando um cliente escolher esse ponto de retirada no checkout, as duas rotas vão competir. Sempre que houver estoque local, seu SLA será mais vantajoso e por isso ele vencerá. Quando não houver estoque local, o pedido vai cair na rota que você configurou a partir deste artigo.
-</div>
diff --git a/docs/tutorials/pt/creating-a-coupon-beta.md b/docs/tutorials/pt/creating-a-coupon-beta.md
index 25281403f..554b5777e 100644
--- a/docs/tutorials/pt/creating-a-coupon-beta.md
+++ b/docs/tutorials/pt/creating-a-coupon-beta.md
@@ -40,7 +40,7 @@ O formulário para criar ou editar um cupom apresenta as seguintes seções:
 
 O painel superior do formulário de criação e edição de cupom, ilustrado abaixo, apresenta a quantidade de vezes em que o cupom foi utilizado e a quantidade de promoções vinculadas ao cupom.
 
-![usos-do-cupom-promocoes-vinculadas](https://images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/7642e6bfa91548c82c851d849fd34a87/criar-cupom-1.png)
+![usos-do-cupom-promocoes-vinculadas](//images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/7642e6bfa91548c82c851d849fd34a87/criar-cupom-1.png)
 
 Ao clicar em qualquer uma dessas informações no painel, você tem acesso ao modal **Ver detalhes de uso**, que apresenta os dados descritos a seguir:
 
@@ -52,11 +52,11 @@ Ao clicar em qualquer uma dessas informações no painel, você tem acesso ao mo
 
     Caso o cupom seja único, esta seção apresenta a lista de pedidos em que o cupom foi utilizado e permite buscar pelo número de um pedido. Ao clicar no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-  ![ver-detalhes-de-uso](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/bcd304169c9f0763693e8d85f54e3e01/ver-detalhes-de-uso.png "Detalhes de uso de um cupom único")
+  ![ver-detalhes-de-uso](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/bcd304169c9f0763693e8d85f54e3e01/ver-detalhes-de-uso.png "Detalhes de uso de um cupom único")
 
     Caso seja um grupo de cupons, esta seção apresenta a lista de códigos do grupo de cupons e permite buscar por um código específico. Ao clicar em um código, você tem acesso à lista de pedidos em que o código foi utilizado e pode buscar pelo número de um pedido. Clicando no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-  ![selecione-o-codigo-grupo-cupons](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png "Detalhes de uso de um grupo de cupons")
+  ![selecione-o-codigo-grupo-cupons](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png "Detalhes de uso de um grupo de cupons")
 
 ### Geral
 
@@ -92,7 +92,7 @@ Após salvar o novo cupom, se você tiver criado um [grupo de cupons](https://he
 * <i class="far fa-clone"></i> **Copiar tudo:** permite copiar os códigos gerados para a sua área de transferência. Posteriormente, se desejar, você pode colá-los em um editor de planilhas como o Excel ou o Google Sheets. Também é possível copiar cada código clicando sobre ele.
 * **Exportar:** permite exportar os códigos gerados para um arquivo CSV. O arquivo exportado contém uma coluna, com um código por linha.
 
-![cupons-gerados-pt](https://images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/094bd2aaca673c282bba6a95f688a1b4/cupons-gerados-pt.gif)
+![cupons-gerados-pt](//images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/094bd2aaca673c282bba6a95f688a1b4/cupons-gerados-pt.gif)
 
 ## Vincular o cupom a uma promoção
 
diff --git a/docs/tutorials/pt/creating-a-more-for-less-promotion.md b/docs/tutorials/pt/creating-a-more-for-less-promotion.md
index bf557f180..2f900769d 100644
--- a/docs/tutorials/pt/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/pt/creating-a-more-for-less-promotion.md
@@ -3,8 +3,8 @@ title: 'Criar promoção Leve Mais por Menos'
 id: tutorials_325
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:17.186Z
-updatedAt: 2023-03-31T19:57:42.646Z
-publishedAt: 2023-03-31T19:57:42.646Z
+updatedAt: 2024-03-28T15:36:24.222Z
+publishedAt: 2024-03-28T15:36:24.222Z
 firstPublishedAt: 2017-04-27T23:03:15.551Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 
 A promoção do tipo Leve Mais por Menos é usada para conceder desconto quando o cliente adiciona várias unidades do mesmo produto ao carrinho. Um exemplo clássico dessa promoção seria "Leve 3 e pague 2".
 
-Neste artigo, detalhamos o funcionamento de cada campo durante as etapas de configuração de uma promoção **Leve Mais por Menos** listadas abaixo.
+Neste artigo, detalharemos os passos necessários para configurar uma promoção Leve Mais por Menos:
 
 1. [Quais os dados gerais desta promoção?](#1-quais-os-dados-gerais-desta-promocao)
     - [Restringir esta promoção a produtos dos sellers](#restringir-esta-promocao-a-produtos-dos-sellers)
@@ -30,27 +30,33 @@ Para entender como funciona a implementação das promoções, leia nosso artigo
 
 ## Criar a promoção
 
-1. No Admin VTEX, acesse *Promoções > Promoções*, ou digite *Promoções* na barra de busca no topo da página.
-2. Clique no botão `Criar Promoção`.
+1. No Admin VTEX, acesse **Promoções** > **Promoções**, ou digite **Promoções** na barra de busca no topo da página.
+2. Clique no botão `Criar promoção`.
 3. Selecione a opção **Leve Mais Por Menos**.
 4. Preencha os campos da promoção.
 5. Clique em `Salvar`.
 
 ## 1. Quais os dados gerais desta promoção?
 
-- **Nome:** nome da promoção. Campo de preenchimento obrigatório.
-- **Status:** opção que define se a promoção está ativa ou inativa. Campo de preenchimento obrigatório.
+Nesta seção, fornecemos informações detalhadas sobre os dados gerais desta promoção.
+- **Nome:** nome da promoção. Campo obrigatório.
+- **Status:** Ativa ou inativa a promoção.
 - **Descrição:** descrição interna da promoção. O objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a promoção é devido à alguma campanha, queima de estoque.
-- **Validade:** data e hora de início e de fim da promoção. Pode ser usada uma data e horário futuros, para que a promoção comece a ser aplicada no site. Caso seja configurada dessa forma, a promoção terá o status de agendada até que a data e horário sejam atingidos. Enquanto a promoção estiver válida, esta terá o status de ativa, e ao término da data e hora definidos o status será alterado para inativo automaticamente. Campo de preenchimento obrigatório.
-- **Usar configurações de recorrência:** opção é do tipo caixa de seleção, que quando marcada disponibiliza sete outras caixas de seleção, para que sejam selecionados os dias da semana e as horas do dia em que a promoção será aplicada. Se deseja que a promoção seja aplicada em qualquer dia da semana, não selecione essa opção.
-- **Destaque nos produtos:** insere uma flag com o nome da promoção, utilizada na vitrine e na página de produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template: `<vtex.cmc:discountHightLight/>`. Campo de preenchimento obrigatório.
+- **Data de expiração:** data e hora de início e de fim da promoção. Pode ser usada uma data e/ou horário futuros, para que a promoção comece a ser aplicada no site. Caso seja configurada desta forma, o status da promoção será exibido das seguintes formas:
+    - **Agendada:** antes da data e horário de início selecionados.
+    - **Ativa:** durante o período programado para a promoção.
+    - **Inativa:** após a data e horário de término selecionados.
+- **Usar configurações de recorrência:** ao selecionar esta opção, é permitido realizar configurações de recorrência, por exemplo, dia da semana e horário.
+- **Informações adicionais (opcional):** permite  incluir informações adicionais a promoção composto de um nome e valor.
+- **Destaque nos produtos:** insere uma tag com o nome da promoção, utilizada na vitrine e na página do produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template: `<vtex.cmc:discountHightLight/>`. Campo de preenchimento obrigatório.
 
-### Restringir esta promoção a produtos dos sellers
+![Dados gerais 1 - PT](//images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/39c1ba28770bab08c1c8eebcdcf2c5a5/Dados_gerais_1_-_PT.png)
 
-Nesta seção, é possível definir para quais sellers a promoção será aplicada. Você pode determinar quais sellers serão incluídos ou excluídos do desconto. 
+### Restringir esta promoção a produtos dos sellers
 
-- **Iguais a:** selecione os nomes dos sellers desejados para inclui-los.
-- **Diferentes de:** selecione os nomes dos sellers desejados para exclui-los.
+Nesta seção, é possível definir para quais sellers a promoção será aplicada. Você pode determinar quais sellers serão incluídos ou excluídos do desconto.
+- **Iguais a:** selecione os nomes dos sellers desejados para incluí-los.
+- **Diferentes de:** selecione os nomes dos sellers desejados para excluí-los.
 
 Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
 
@@ -58,76 +64,82 @@ Para que a promoção seja válida para todos os sellers, deixe a seleção vazi
   <p>Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
 </div>
 
-### Política Comercial
+![Restringir - PT](//images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/6a43d51af7293cbfee1e0f9a2de2428a/Restringir_-_PT.png)
+
+### Política comercial
 
 Esta seção estabelece as políticas comerciais válidas para a promoção. Você pode incluir ou excluir políticas comerciais do desconto.
 
-- **Iguais a:** selecione as políticas comerciais desejadas inclui-las.
-- **Diferentes de:** selecione as políticas comerciais desejadas exclui-las.
+- **Iguais a:** selecione as políticas comerciais desejadas incluí-las.
+- **Diferentes de:** selecione as políticas comerciais desejadas excluí-las.
 - **Fornecido por mim (Minha loja):** seleção de políticas comerciais com produtos da sua loja. Pode ser selecionada mais de uma política comercial.
-- **Entregue por mim (Lojas de terceiros):** seleção de políticas comerciais em que seus produtos estão de lojas de terceiros. Pode ser selecionada mais de uma política comercial.
+- **Entregue por mim (Lojas de terceiros):** seleção de políticas comerciais em que seus produtos estão em lojas de terceiros. Pode ser selecionada mais de uma política comercial.
 
 Para que a promoção seja válida para todas as políticas comerciais, deixe a seleção vazia.
 
+![Politica - PT](//images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/15e5033e2d6b01b848e2d16c81762cb1/Politica_-_PT.png)
+
 ## 2. Leve mais por menos
 
 Esta seção define os produtos, a quantidade e o desconto que serão afetados pela promoção.
 
-- **O cliente compra** `quantidade` **dos seguintes produtos:** quantidade de unidades do mesmo produto que deve ser inserida no carrinho para a promoção ser aplicada. Campo de preenchimento obrigatório.
-- - **SKUs:** nomes ou IDs dos SKUs que terão o desconto aplicado. Você pode fazer a importação de uma lista de SKUs clicando no botão `Selecione um arquivo .txt`. O arquivo de texto (.txt) deve ter cada SKU ID em uma linha diferente. Você também pode baixar a lista de SKUs adicionada no campo clicando no botão `Download da lista de SKUs`.
+- **O cliente compra `quantidade` dos seguintes produtos:** quantidade de unidades do mesmo produto que deve ser inserida no carrinho para a promoção ser aplicada. Campo de preenchimento obrigatório.
+    - **SKUs:** nomes ou IDs dos SKUs que terão o desconto aplicado. Você pode fazer a importação de uma lista de SKUs clicando no botão `Selecione um arquivo .txt`. O arquivo de texto (.txt) deve ter cada SKU ID em uma linha diferente. Você também pode baixar a lista de SKUs adicionada no campo clicando no botão `Download da lista de SKUs`.
 - **Coleções:** seleção de coleções que serão incluídas na promoção. A promoção será aplicada somente aos produtos que estejam nas coleções cadastradas neste campo. Para isso, digite o nome da coleção de produtos que deseja oferecer esse tipo de desconto. É possível selecionar mais de uma coleção.
 
 <div class = "alert alert-info">
   <p>Se não forem informados produtos por coleção ou por SKU, a plataforma não permitirá a criação da promoção.</p>
 </div>
 
-- **E leva** `quantidade` **desses produtos:** quantidade de unidades do produto que receberá o desconto configurado. Campo de preenchimento obrigatório.
-   - **Com desconto de:** o cliente levará a quantidade selecionada de produtos com um desconto percentual definido no campo. 
-   - **Preço Máximo por Item:** o cliente levará a quantidade selecionada de produtos com um preço máximo por item definido no campo. 
+- **E leva `quantidade` desses produtos:** quantidade de unidades do produto que receberá o desconto configurado. Campo de preenchimento obrigatório.
+    - **Com desconto de:** o cliente levará a quantidade selecionada de produtos com um desconto percentual definido no campo.
+    - **Preço Máximo por Item:** o cliente levará a quantidade selecionada de produtos com um preço máximo por item definido no campo.
 
-|![Leve mais por menos 1 -PT](//images.contentful.com/alneenqid6w5/4LBVcysY2Fwkcp7yossEYg/bbdb2096b0dd90293e7b8bbbb99d5daf/image__37_.png)|
-|:--:|
-| _Exemplo de uma promoção Compre 3 e Pague 2_|
+ ![Leve Mais - PT](//images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/4007f36df438fc5192f131f39f624d02/Leve_Mais_-_PT.png)
 
 ### Configurações avançadas
-Nesta seção, é possível especificar a aplicação do desconto.
-
-#### O desconto deve ser aplicado
 
-- **Considerando:** 
-  - **Qualquer produto:** o desconto será aplicado aos produtos da coleção ou lista de SKUs, sem que o carrinho tenha necessariamente a quantidade cadastrada anteriormente. Assim, é considerado o somatório das unidades desses produtos.
-  - **Somente produtos iguais:** o desconto somente será aplicado ao SKU. Para a aplicação ser válida é preciso ter a quantidade mínima cadastrada anteriormente. 
+Nesta seção, é possível especificar a aplicação do desconto.
+O desconto deve ser aplicado:
 
-- **Aos produtos de valor:**
-  - **Mais barato:**  o desconto será aplicado aos itens mais baratos da promoção.
-  - **Mais caro:** o desconto será aplicado aos itens mais caros da promoção.
+- **Considerando:**
+    - **Qualquer produto:** o desconto será aplicado aos produtos da coleção ou lista de SKUs, sem que o carrinho tenha necessariamente a quantidade cadastrada anteriormente. Assim, é considerado o somatório das unidades desses produtos.
+    - **Somente produtos iguais:** o desconto somente será aplicado ao SKU. Para a aplicação ser válida é preciso ter a quantidade mínima cadastrada anteriormente.
+    - **Aos produtos:**
+        - **Mais baratos:** o desconto será aplicado aos itens mais baratos da promoção.
+        - **Mais caros:** o desconto será aplicado aos itens mais caros da promoção.
 
-![Leve mais por menos 2 - PT](//images.contentful.com/alneenqid6w5/6t9FwhVBSzxkvcz0jFZIrN/7f52bc1849fa228884af45a785703fce/image__38_.png)
+![Leve Mais por menos - PT](//images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/8e369e751ba27732e5c324c0cae7c7e1/Leve_Mais_por_menos_-_PT.png)
 
 #### Como o desconto deve ser distribuído?
-
-- **Apenas entre os** `Quantidade` **produtos que recebem desconto:** o desconto será aplicado integralmente à quantidade de produtos selecionada.
-- **Proporcionalmente entre os** `Quantidade` **produtos:** o desconto será distribuído igualmente entre a quantidade de produtos selecionada.
+- **Apenas entre as `quantidade` produtos que recebem desconto:** o desconto será aplicado integralmente à quantidade de produtos selecionada.
+- **Proporcionalmente entre os `quantidade` produtos:** o desconto será distribuído igualmente entre a quantidade de produtos selecionada.
 
 ## 3. Quais as condições para a promoção ser válida?
 
+Nesta seção, detalharemos as condições em que você deve aplicar para que uma promoção seja considerada válida.
+
 - **Valor mínimo e máximo do pedido:** a promoção será aplicada levando em conta o valor "bruto" do carrinho, sem considerar demais promoções ou frete.
-- **Preço "de" e "por" são iguais ou Preço "de" e "por" são diferentes**: Somente uma opção pode ser selecionada. Refere-se aos preços do cadastro do produto.
-- **Restrição de Promoção por BIN:** o desconto será concedido caso o BIN do cartão esteja entre os números preenchidos.
+- **Preço "de" e "por" são iguais ou Preço "de" e "por" são diferentes:** Somente uma opção pode ser selecionada. Refere-se aos preços do cadastro do produto.
+- **Usar BIN de restrição:** o desconto será concedido caso o BIN do cartão esteja entre os números preenchidos.
 - **Cluster de clientes:** o desconto será concedido caso o cliente esteja cadastrado no cluster selecionado. É importante destacar que o nome do cluster deve ser exatamente como cadastrado, qualquer erro de grafia impedirá o funcionamento correto da configuração.
 - **Utm_source:** o desconto será concedido caso a navegação seja realizada com as utm_source correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas um utm_source no checkout.
 - **Utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
 - **Criar cupom a partir das UTMs acima:** cria um cupom a partir das UTMs cadastradas para dar ao cliente acesso à essa promoção apenas com o código do cupom.
-- **Meio de pagamento:** o desconto será concedido caso a forma de pagamento selecionada pelo cliente seja a mesma cadastrada na promoção. Esse desconto somente será aplicado na finalização da compra, quando o cliente selecionar a mesma forma de pagamento cadastrada.
+- **Meio de pagamento:** permite escolher se a promoção será aplicada em um ou mais tipos de meios de pagamento selecionados.
 
-  <div class = "alert alert-info">
+ <div class = "alert alert-info">
   <p> Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
  </div>
 
-## 4. Restrições e limitações de uso
+![Condições de promoção - PT](//images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/d5a51e69868ee890a701dba2dfe8a1f2/Condi__es_de_promo__o_-_PT.png)
+
+ ## 4. Restrições e limitações de uso
+
+ - **Quantas vezes essa promoção será aplicada em sua loja:** limita a quantidade de vezes em que a promoção será aplicada. Quando a opção **ilimitada** é desmarcada, é disponibilizado um campo para cadastrar a quantidade de vezes que deseja limitar. Uma vez que a promoção já foi criada, essa condição só será aplicada a partir do dia em que foi configurada, não afetando os pedidos realizados anteriormente.
+ - **Quantas vezes essa promoção será aplicada em sua loja por cliente:** o valor incluído neste campo determina o número máximo de vezes que cada cliente pode se beneficiar da promoção. Consideremos, por exemplo, um limite estabelecido de três utilizações. Caso a promoção seja aplicada três vezes em um único pedido, isso será considerado como uma única utilização em relação ao limite total. Assim, o cliente ainda terá a oportunidade de utilizar a promoção em mais dois pedidos diferentes. É importante destacar que este cálculo é independente da quantidade de vezes que a promoção é utilizada em cada pedido individualmente.
+ - **Definir o número máximo de itens elegíveis por carrinho:** define quantos itens do carrinho serão afetados pela promoção. [Leia esse artigo](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para saber como configurar o campo.
+ - **Permitir acumular promoções:** permite que mais de uma promoção, independente do tipo de desconto, seja concedida ao mesmo tempo. Saiba mais sobre [como funciona a concorrência de promoções](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270).
+- **Permitir acumular com preços manuais:** permite que a promoção seja aplicada a produtos cujos preços foram manualmente inseridos pelo televendas. Para habilitar a funcionalidade de preços manuais, use o endpoint [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
 
-- **Quantas vezes essa promoção será aplicada em sua loja:** limita a quantidade de vezes  em que a promoção será aplicada. Quando a opção **ilimitada** é desmarcada, é disponibilizado um campo para cadastrar a quantidade de vezes que deseja limitar. Uma vez que a promoção já foi criada, essa condição só será aplicada a partir do dia em que foi configurada, não afetando os pedidos realizados anteriormente.
-- **Quantas vezes essa promoção será aplicada em sua loja por cliente:** habilita a quantidade cadastrada acima não mais para quantidade de uso total da promoção, e sim para a quantidade de vezes que cada cliente poderá receber a promoção. Caso o campo acima também esteja selecionado, ele terá uma prioridade maior de atuação que este limite.
-- **Definir quantidade máxima de itens afetados por carrinho**: define quantos itens do carrinho serão afetados pela promoção. Leia [esse artigo](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy#limite-de-itens-com-promocao-no-carrinho) para saber como configurar o campo.
-- **Permitir acumular promoções:** permite que mais de uma promoção, independente do tipo de desconto, seja concedida ao mesmo tempo. Saiba mais sobre [como funciona a concorrência de promoções](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270#).
-- **Permitir acumular com preços manuais:**  permite que a promoção seja aplicada a produtos cujos preços foram manualmente inseridos pelo televendas. Para habilitar a funcionalidade de preços manuais, use o endpoint [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration).
+![Restrições e limitações - PT](//images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/ea978a02b2454f97243b951981d0ff1b/Restri__es_e_limita__es_-_PT.png)
diff --git a/docs/tutorials/pt/creating-a-product-collection.md b/docs/tutorials/pt/creating-a-product-collection.md
index 40943285a..c6176f717 100644
--- a/docs/tutorials/pt/creating-a-product-collection.md
+++ b/docs/tutorials/pt/creating-a-product-collection.md
@@ -25,7 +25,7 @@ Para criar uma coleção, siga as instruções abaixo:
 2. Clique em **Layout**.
 3. Clique na pasta **Product Clusters (Collections)**.
 4. Clique no botão `new collection`, ilustrado a seguir.
-	![Layout 4](https://images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
+	![Layout 4](//images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
 5. Preencha as informações necessárias:
 	- **Product Cluster Id:** código identificador da coleção. Este campo não deve ser preenchido, pois é gerado automaticamente pelo sistema ao salvar.
 	- **Name:** nome da coleção.
@@ -51,9 +51,9 @@ Para criar um grupo por departamento, categoria ou subcategoria, siga as instru
 
 1. Clique no nome da coleção desejada em **Product Clusters (Collections)**.
 2. Clique no botão `new group`, conforme exemplifica a imagem a seguir.
-	![Layout 5](https://images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
+	![Layout 5](//images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
 3. Para acrescentar todos os produtos de um determinado departamento a um grupo, selecione o departamento em questão, como indica a figura a seguir. O mesmo se aplica aos produtos de uma determinada categoria ou subcategoria.
-	![Filtro_por_categoria](https://images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
+	![Filtro_por_categoria](//images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
 4. Clique em `Salvar Grupo`.
 
 ### Criar grupo por marca
@@ -63,7 +63,7 @@ Para criar um grupo com produtos de uma ou mais marcas, siga as instruções aba
 1. Clique no nome da coleção desejada em **Product Clusters (Collections)**.
 2. Clique no botão `new group`.
 3. Selecione uma ou mais marcas na lista correspondente. As marcas encontram-se dispostas em ordem alfabética. Ao clicar na letra correspondente à inicial da marca, a lista se expande e exibe as marcas existentes.
-  ![FIltro_por_marca](https://images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
+  ![FIltro_por_marca](//images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
 
 ### Definir grupo por produtos em pré-venda ou em período de lançamento
 
@@ -95,7 +95,7 @@ Quando o número de SKUs na listagem ultrapassar 10 itens, um controle de pagina
 
 Para excluir um SKU da lista, basta clicar no botão vermelho ao lado do SKU correspondente.
 
-  ![Inserir_sku_espec_fico](https://images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
+  ![Inserir_sku_espec_fico](//images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
 
 ### Importar uma lista de SKUs para o grupo
 
@@ -105,7 +105,7 @@ Apesar dos filtros de grupos serem muito práticos para criar agrupamentos de pr
 
 Depois que a planilha for importada pelo sistema, os SKUs são apresentados da seguinte maneira:
 
-![Importar_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
+![Importar_lista_de_skus](//images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
 
 SKUs que estiverem inativos não terão seus IDs importados mesmo que estejam incluídos na planilha.
 
@@ -117,7 +117,7 @@ SKUs que estiverem inativos não terão seus IDs importados mesmo que estejam in
 
 Para evitar que um administrador tenha que excluir manualmente diversos SKUs, um a um, é possível utilizar o recurso de importação de SKUs da mesma forma que foi exemplificada na seção anterior. Neste caso, depois que o arquivo for carregado, clique na opção `excluir skus`.
 
-![Excluir_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
+![Excluir_lista_de_skus](//images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
 
 Obtenha um modelo de arquivo para a importação tanto para inclusão quanto para exclusão de itens na coleção [aqui](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "aqui").
 
@@ -125,4 +125,4 @@ Obtenha um modelo de arquivo para a importação tanto para inclusão quanto par
 
 Quando a quantidade de coleções criadas exceder o limite de exibição, que é de 20 itens, as coleções poderão ser encontradas através do campo de pesquisa. A busca deve ser feita com base no nome da coleção.
 
-![Pesquisar_cole__o](https://images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
+![Pesquisar_cole__o](//images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
diff --git a/docs/tutorials/pt/creating-a-shipping-policy.md b/docs/tutorials/pt/creating-a-shipping-policy.md
new file mode 100644
index 000000000..4439b2c3c
--- /dev/null
+++ b/docs/tutorials/pt/creating-a-shipping-policy.md
@@ -0,0 +1,73 @@
+---
+title: 'Criar uma política de envio'
+id: 66rJO4LKBdyMJOH6Z3dsaT
+status: PUBLISHED
+createdAt: 2024-01-30T21:08:12.106Z
+updatedAt: 2024-06-11T19:05:19.723Z
+publishedAt: 2024-06-11T19:05:19.723Z
+firstPublishedAt: 2024-01-31T01:09:33.011Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: criar-uma-politica-de-envio
+locale: pt
+legacySlug: criar-uma-politica-de-envio
+subcategory: 7fTH6bP0C4IaM8qWi0kkQC
+---
+
+[Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) é um conjunto de regras e configurações que definem quais opções e condições de envio serão apresentadas aos clientes no checkout. A relação entre **política de envio**, [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) é o que compõe sua [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) na VTEX.
+
+Este artigo apresenta como você cria uma política de envio pelo Admin VTEX. Se você deseja acompanhar e gerenciar suas políticas, veja o artigo [Gerenciar políticas de envio](https://help.vtex.com/pt/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE).
+
+Para criar uma nova política de envio, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Envio > Estratégia de Envio > Políticas de Envio** ou digite **Estratégia de Envio** na barra de busca no topo da página.
+2. Clique no botão `Criar política de envio`.
+3. Preencha os campos da tela descritos abaixo e, em seguida, clique em `Salvar alterações`.
+
+*   **Ativa**: ativa ou desativa a política de envio.
+*   **Nome:** nome interno da política de envio.
+*   **ID:** identificador interno e para integradores. Deve ser preenchido apenas com letras e números, e não deve conter espaços. Caso não seja preenchido, será criado um ID automaticamente. 
+*   **[Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126):** nome do tipo de entrega. Serve para separar os diferentes serviços de entrega. É o nome que será exibido na finalização de compra para o cliente. Ex. expresso vs. normal. 
+*   **[Upload de tarifas de envio](https://help.vtex.com/pt/tutorial/como-montar-a-planilha-de-frete--tutorials_127)**: é a tabela com os valores e prazos de frete assumidos pela política de envio. 
+*   **[Dimensões do Pacote](https://help.vtex.com/pt/tutorial/como-funciona-o-empilhamento--tutorials_124):**
+    *   **Soma das dimensões:** limite de dimensão do pacote que leva em conta a soma da medida de todas as arestas do pacote. Ao atingir esse valor, ou a entrega é dividida em pacotes ou não é feita. Estes dados são passados pela transportadora no momento de fechamento do contrato com a mesma. 
+    *   **Maior aresta:** limite de tamanho da maior aresta do pacote. Ao atingir esse valor, ou a entrega é dividida em pacotes ou não é feita.
+    *   **[Fator de peso cúbico](https://help.vtex.com/pt/tutorial/como-o-peso-cubado-e-calculado--tutorials_128):** fator que será utilizado para cálculo do peso cubado. Soma das medidas, dividida pelo fator cúbico. 
+    *   **Fator de peso mínimo:** use o peso cúbico apenas se este passar deste valor. Limite de peso onde, a partir dele, será considerado o cálculo do peso cubado para o frete.
+*   **Fins de semana e feriados:** os dias da semana para entregas. Marque as flags, para ativar a entrega nos seguintes cenários: `Entrega nos sábados`, `Entrega nos domingos`, `Entrega nos feriados`.
+*   **[Modais ativos](https://help.vtex.com/pt/tutorial/como-funciona-o-modal--tutorials_125):** especificações de produtos que necessitam de uma entrega especial. São as limitações de envio do produto que a política de envio permite. Marque as flags para ativar a entrega nos seguintes cenários: `químicos`, `eletrônicos`, `móveis`, `vidro`, `líquidos`, `colchões`, `refrigerados`, `pneus`, `linha branca` e `armas de fogo`.
+*   **Itens do pacote:** descrição de valor e número de itens do pacote:
+    *   **Valor mínimo:** valor mínimo aceito pela política de envio, para realizar o frete.
+    *   **Mínimo de itens:**  múltiplo mínimo da quantidade de itens aceita pela transportadora. Por exemplo, se for preenchido com o valor **3**, significa que a transportadora só realiza  entregas que têm quantidades de itens múltiplos de  três (3, 6, 9, 21…).
+    *   **Valor máximo:** máximo valor aceito pela política de envio, para realizar o frete.
+*   **Relacionar pontos de retirada:** marque esta flag, para abrir a opção de Pontos de retirada. Clique no dropdown e selecione entre `Tags dos pontos de retirada`, `Nomes dos pontos de retirada` e `Importar ponto de retirada de sellers` previamente cadastrados.
+*   **[Horário de funcionamento:](https://help.vtex.com/pt/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS)** os horários em que a transportadora faz coletas e as janelas de tempo em que ela envia os itens para os clientes. Estas configurações influenciam o cálculo do tempo de entrega:
+    *   **Janela de envio:** é onde você cadastra os períodos de funcionamento da transportadora, ou seja, os horários em que ela aceita o recebimento do pedido. Para configurar selecione a janela `Janela de envio`:
+        *   `Aceitar compras fora do horário de funcionamento`: ativa ou inativa o recebimento de compras fora do horário de funcionamento. Quando ativo, o intervalo de tempo do momento do pedido até o início horário, será somado ao tempo total da entrega.
+        *   Selecione o `Dia da semana`, e preencha `Horário de início` e `Horário de término`.
+        *   Para adicionar mais dias da semana, clique em `Adicionar janela de envio`.
+    *   **Horário de coleta:** é onde você cadastra os horários em que a transportador coleta pacotes em seu estoque ou centro de distribuição, para em seguida enviá-los aos clientes finais. Caso o pedido seja feito antes do início do horário de coleta, nenhum tempo será adicionado ao tempo total da entrega. No entanto, se ele for feito após o horário de coleta, o intervalo de tempo do momento do pedido até o início horário, será somado ao tempo total da entrega.
+        *   Selecione o `Dia da semana` e preencha o `Horário da coleta`. 
+        *   Para adicionar mais dias da semana, clique em `Adicionar horário de coleta`.
+
+<div class="alert alert-warning">
+A <b>Janela de envio</b> e <b>Horário de coleta</b> são opções excludentes, pois um mesmo período não pode ser simultaneamente destinado a ações diferentes.
+</div>
+
+*   **[Entrega agendada:](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)** essa funcionalidade pode ser habilitada caso a política de envio ofereça o serviço de entrega agendada. É aqui que você deverá adicionar as janelas de entrega que ficarão disponíveis para o cliente ao final da compra. Para utilizar, habilite `entrega agendada` e preencha:
+    *   **Tempo máximo de entrega:** define o tempo máximo de entrega, deve ser preenchido com o tempo em dias.
+    *   **Período de entrega:** define as janelas de entrega que a política de entrega realiza. Você deve adicionar os dias da semana, horários de `Início` e `Fim` da janela de entrega, e valor adicional. Clique em `Adicionar novo período de entrega` para adicionar mais janelas de entrega. 
+    *   **Capacidade de entrega:** permite limitar quantos itens/pedidos podem ser entregues para cada janela de entrega. Essa funcionalidade pode ser habilitada, ou não. O uso ou não dessa funcionalidade não interfere no funcionamento da plataforma. Para saber mais sobre esses recursos consulte a [Entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) e [Gerenciar capacidade de entrega](https://help.vtex.com/pt/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz). Caso seja habilitada você deve:
+        *   Escolher a unidade da capacidade de entrega entre `itens` e `pedidos`.
+        *   Conferir as janelas de entrega.
+        *   Definir o número da capacidade de entrega. Recomendamos cuidado especial ao escolher a unidade e a quantidade da capacidade de entrega, pois o sistema não calcula a disponibilidade da `capacidade de entrega` levando em conta a quantidade de itens sendo comprada. Então, se a janela de entregas ainda tiver capacidade para 2 itens e seu cliente estiver comprando 4 itens, ele ainda terá a opção de selecionar a janela de entrega disponível.
+
+            É importante lembrar que as janelas de entrega deixam de ficar disponíveis aos clientes caso já tenham atingido o limite da `capacidade de entrega`. Para que uma janela fique novamente disponível aos clientes, é preciso aumentar a quantidade de itens/pedidos da capacidade de entrega da janela. 
+
+### Saiba mais
+
+* [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
+* [Gerenciar políticas de envio](https://help.vtex.com/pt/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE)
+* [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3)
+
diff --git a/docs/tutorials/pt/creating-a-subscription-plan.md b/docs/tutorials/pt/creating-a-subscription-plan.md
index cdc9b7482..85cb5fe84 100644
--- a/docs/tutorials/pt/creating-a-subscription-plan.md
+++ b/docs/tutorials/pt/creating-a-subscription-plan.md
@@ -92,7 +92,7 @@ Nesta tela, você pode realizar as seguintes ações:
 
 * **Selecionar:** ao clicar no <i class="far fa-square"></i> na linha de cada produto, você pode selecionar produtos ou SKUs individualmente. Outra opção é clicar no primeiro <i class="far fa-square"></i> e selecionar todos os produtos e SKUs exibidos na página para adicioná-los ao plano, conforme ilustrado na imagem abaixo.
 
-![selecionarskus PT](https://images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/d5166c26395bfd131c45fe27f51ec5a8/selecionarskus_PT.gif)
+![selecionarskus PT](//images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/d5166c26395bfd131c45fe27f51ec5a8/selecionarskus_PT.gif)
 
 * **Botão** <i class="fas fa-chevron-down"></i>: exibe os SKUs, ou seja, as variações do produto.
 * **Adicionar:** ao clicar neste botão, você adiciona o(s) produto(s) ou SKU(s) ao plano de assinatura.
diff --git a/docs/tutorials/pt/creating-a-subscription-promotion.md b/docs/tutorials/pt/creating-a-subscription-promotion.md
index bf6d7359d..b58b39bdf 100644
--- a/docs/tutorials/pt/creating-a-subscription-promotion.md
+++ b/docs/tutorials/pt/creating-a-subscription-promotion.md
@@ -22,7 +22,7 @@ Neste artigo, você encontrará o passo a passo para criar promoções de assina
 3. Clique no botão `Nova Promoção`.
 4. Selecione o botão `Promoção Regular`.
 5. Selecione o campo **É um pedido de assinatura** na seção **Quais as condições para a promoção ser válida?**. Essa opção define que a promoção será aplicada em pedidos de assinatura. Apenas os produtos com assinatura no carrinho receberão o desconto. Para entender as possibilidades de configuração, veja as condições a seguir:
- ![frequenciapt](https://images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/f4eb96b416f69ce48d712463b1d7bd16/image1__2_.png)
+ ![frequenciapt](//images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/f4eb96b416f69ce48d712463b1d7bd16/image1__2_.png)
 - **Pedido original**: pedidos que geram as assinaturas, mas ainda não fazem parte dos ciclos de assinatura.
 - **Pedidos recorrentes**: pedidos que fazem parte dos ciclos de assinatura.
 - **Filtrar por**: seleção que filtra quais pedidos de assinatura que serão válidos para a promoção.
diff --git a/docs/tutorials/pt/creating-a-trade-policy.md b/docs/tutorials/pt/creating-a-trade-policy.md
index e6f26a50f..6324acc52 100644
--- a/docs/tutorials/pt/creating-a-trade-policy.md
+++ b/docs/tutorials/pt/creating-a-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Criar uma política comercial'
 id: 563tbcL0TYKEKeOY4IAgAE
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:49.369Z
-updatedAt: 2022-12-08T14:40:14.268Z
-publishedAt: 2022-12-08T14:40:14.268Z
+updatedAt: 2024-04-15T21:21:00.376Z
+publishedAt: 2024-04-15T21:21:00.376Z
 firstPublishedAt: 2019-01-24T22:14:00.848Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,40 +15,32 @@ legacySlug: o-que-e-uma-politica-comercial
 subcategory: 6J3wx7KM4oysymsWuUACyY
 ---
 
-[Políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) são usadas na VTEX para agrupar configurações de catálogo, preços, promoções, inventário, logística, segmentação de clientes e pagamentos para diferentes canais de venda. Canais de venda podem incluir marketplaces, ecommerce próprio, lojas físicas, ou lojas B2B, por exemplo. 
+[Políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) são usadas na VTEX para agrupar configurações de catálogo, preços, promoções, inventário, logística, segmentação de clientes e pagamentos para diferentes canais de venda. Canais de venda podem incluir marketplaces, ecommerce próprio, lojas físicas, ou lojas B2B, por exemplo.
 
-A seção Políticas Comerciais do seu admin apresenta uma tabela com todas as políticas comerciais já cadastradas. Também é possível filtrar os resultados, fazer uma busca por palavra chave, e ordenar na tabela as políticas comerciais já cadastradas. O ID da política comercial é determinado automaticamente pelo sistema, a partir da ordem cronológica de criação de novas políticas. 
+<div class="alert alert-danger">
+Por padrão, novas políticas comerciais são aplicadas a todos os sellers ativos. Se desejar aplicar apenas a um grupo específico de sellers, por favor informe isto no ticket.
+</div>
+
+## Gerenciar políticas comerciais
+
+A seção Políticas Comerciais do seu admin apresenta uma tabela com todas as políticas comerciais já cadastradas. Também é possível filtrar os resultados, fazer uma busca por palavra chave, e ordenar na tabela as políticas comerciais já cadastradas. O ID da política comercial é determinado automaticamente pelo sistema, a partir da ordem cronológica de criação de novas políticas.
 
-Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via ticket em *[Suporte](https://help.vtex.com/pt/support)* selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
+Para definir as configurações de logística aplicadas a essa política comercial, é preciso [criar ou editar uma doca](https://help.vtex.com/pt/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW), relacionada às transportadoras desejadas, inserindo o ID da política comercial no formulário de cadastro.
 
-A contratação de política comercial adicional para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
+Para utilizar o mesmo catálogo em mais de uma política comercial, acesse a documentação [Associate Product with Trade Policy](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product/-productId-/salespolicy/-tradepolicyId-).
 
-1. Na seção *Configurações da Loja*, clique em **Políticas comerciais**.    
-2. Clique em **Nova Política Comercial**.    
-3. Preencha os campos.    
-4. Clique em **Salvar**.     
+## Contratar uma políica comercial
+
+Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via [suporte VTEX](https://help.vtex.com/pt/support) selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`. Ao solicitar a criação de uma política comercial via ticket, considere um tempo de resposta de até três dias úteis.
 
 <div class="alert alert-info">
-Para definir as configurações de logística aplicadas a essa política comercial, é preciso <a href="https://help.vtex.com/pt/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW">criar ou editar uma doca</a>, relacionada às transportadoras desejadas, inserindo o ID da política comercial no formulário de cadastro.
+Para que o uso de política comercial adicional para integrar com <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conector nativo</a>, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outras lojas VTEX seja isenta de taxas, é encessário que pedidos sejam associados a ela.
 </div>
 
-## Campos de preenchimento
-- **Nome:** nome que identifica sua política comercial em outros módulos do admin da VTEX.  
-- **Coleção**: coleção de produtos cadastrada no catálogo, válida para a política comercial.  
-- **Sellers:** caixa de seleção que associa sellers às regras da política comercial.    
-- **Código da moeda**: moeda que será aplicada no canal de vendas que segue essa política comercial.   
-- **Símbolo da moeda:** símbolo da moeda escolhida, que aparecerá nos preços de produtos no canal de vendas que segue essa política comercial. Este campo é opcional e se for deixado em branco assumirá o símbolo padrão da moeda escolhida.   
-- **Casas decimais da moeda:** quantidade de casas decimais que os preços dos produtos podem assumir. Este campo é opcional e se for deixado em branco assumirá o valor padrão da moeda escolhida.   
-- **Código do país:** código do país onde o canal de vendas se situa.    
-- **Culture info:** idioma selecionado para a política comercial, entre as opções disponíveis para o país selecionado.   
-- **TimeZone:** fuso horário aplicado à política comercial seguindo o padrão Tempo Universal Coordenado (UTC).   
-- **Ativo:** caixa de seleção para ativar ou inativar a política comercial no seu ambiente VTEX.   
-- **Regra condicional:** campo customizável onde é possível definir um critério adicional para a política comercial. Exemplos de regras condicionais incluem limitar o acesso à loja pela política comercial através de um [cluster de clientes](https://help.vtex.com/pt/tutorial/como-criar-um-cluster-de-clientes).  
-- **Herdar Catálogo da política comercial:** catálogo de uma política comercial já criada, que será aplicado na política comercial que está sendo cadastrada. Caso as políticas só se diferenciem nos outros campos, mas o catálogo seja o mesmo, sempre que possível marque esse campo para otimizar a performance do sistema.   
-
 ## Saiba mais
 
 - [Como funciona uma política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)    
 - [Política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)
+- [Contratação de política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X)
 - [Cadastrar doca](https://help.vtex.com/pt/tutorial/how-to-register-a-dock--7K3FultD8I2cuuA6iyGEiW)
 
diff --git a/docs/tutorials/pt/creating-a-type-of-list.md b/docs/tutorials/pt/creating-a-type-of-list.md
index f2c36a88a..57d5cf8c1 100644
--- a/docs/tutorials/pt/creating-a-type-of-list.md
+++ b/docs/tutorials/pt/creating-a-type-of-list.md
@@ -61,7 +61,7 @@ O lojista decide se a lista terá evento ou não. Uma vez salvo o tipo de lista
 
 Ao selecionar **POSSUI EVENTO**, o formulário disponibiliza outras opções de configuração para o evento, onde será possível configurar todas as datas limites para criação desse tipo de lista, conforme imagem abaixo.
 
-![eventos.pt](https://images.ctfassets.net/alneenqid6w5/KhcZ5meUIwnSqBaekhc9C/b8c2b20e083c529a5ae7b4fc63e8a6ab/eventos.pt.png)
+![eventos.pt](//images.ctfassets.net/alneenqid6w5/KhcZ5meUIwnSqBaekhc9C/b8c2b20e083c529a5ae7b4fc63e8a6ab/eventos.pt.png)
 
 A área de evento é responsável por definir se a lista criada possui ou não um período preestabelecido para a data do evento. Listas de desejo ou listas de compras não necessitam de um período determinado para ocorrência do evento. De forma contrária, listas de casamento ou de chá de bebe, precisam levar em conta a data do evento, para que assim, todos os produtos comprados sejam entregues ao dono em período hábil à data do evento.
 
@@ -79,7 +79,7 @@ As seguintes opções estão disponíveis:
 
 Após a criação do tipo de lista, você será redirecionado para a tela onde aparecem os tipos de listas já cadastrados na loja. Essa tela fornece as seguintes informações e funções:
 
-![listagem.pt](https://images.ctfassets.net/alneenqid6w5/5TBHW4MjIqIKMAroEqIKUA/8af47e1d4375b8550a70cb03098adbc0/listagem.pt.png)
+![listagem.pt](//images.ctfassets.net/alneenqid6w5/5TBHW4MjIqIKMAroEqIKUA/8af47e1d4375b8550a70cb03098adbc0/listagem.pt.png)
 
 - **Exportar para Excel**: Permite exportar os dados de tipos de listas para Excel.
 - **Versão**: Identificação de listas criadas na versão antiga da funcionalidade, com limitações. A versão mais atual é a “v2”.
diff --git a/docs/tutorials/pt/creating-an-application-in-master-data.md b/docs/tutorials/pt/creating-an-application-in-master-data.md
index 37397945b..c4ff420fb 100644
--- a/docs/tutorials/pt/creating-an-application-in-master-data.md
+++ b/docs/tutorials/pt/creating-an-application-in-master-data.md
@@ -3,44 +3,46 @@ title: 'Criar aplicação no Master Data'
 id: tutorials_1115
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:27.067Z
-updatedAt: 2023-03-28T23:26:06.249Z
-publishedAt: 2023-03-28T23:26:06.249Z
+updatedAt: 2024-06-25T20:45:29.002Z
+publishedAt: 2024-06-25T20:45:29.002Z
 firstPublishedAt: 2017-04-27T23:03:43.159Z
 contentType: tutorial
 productTeam: Master Data
 author: authors_3
-slug: criando-aplicacao-no-master-data
+slug: criar-aplicacao-no-master-data
 locale: pt
 legacySlug: criando-aplicacao-no-master-data
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-Aplicação é um agrupador de formulários. Ela tem a função de organizar, dividir e estabelecer acessos refinados por área. Ou seja, é criada uma aplicação e são criados formulários dentro desta aplicação, assim, facilitando a organização dos dados conforme necessidade. Exemplo: Aplicação Atendimento, formulários Cliente e Ticket.
+Uma aplicação é um agrupador de formulários que organiza, divide e estabelece acessos refinados por área no Master Data. Ao criar uma aplicação, você pode incluir vários formulários dentro dela, facilitando a organização dos dados conforme necessário. Por exemplo: na Aplicação "Atendimento", você pode ter os formulários "Cliente" e "Ticket".
 
-## Como criar a aplicação
+## Criar aplicação
 
-1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
-2. Clique na aba **Aplicações**.
-3. Clique no botão **Criar Aplicação**.
-4. Preencha o nome da **Aplicação**.
-5. Preencha o campo **Criar Cópia De** caso queira copiar os formulários de outra aplicação.
-6. Clique no botão **Salvar**.
-7. Ao carregar a página de aplicações, clique no botão **Recarregar Aplicações**.
+Siga as instruções abaixo para criar uma nova aplicação:
 
-<video class="wp-video-shortcode" id="video-1115-2" width="840" height="411" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4?_=2" />[//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4](//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4 "//assets.contentful.com/alneenqid6w5/7Ibn7u8xVYAUigYkaIQQYI/aa2ca7d7ad7abdc8e30b7f2a7f855da7/CriandoAplicacao.mp4")</video>
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Clique no botão `Criar aplicações`.
+4. Preencha o **Nome** da aplicação.
+5.Selecione uma opção no campo **Criar cópia de** caso deseje copiar os formulários de outra aplicação.
+6. Clique no botão `Salvar`.
 
-## Como editar a aplicação
+## Editar aplicação
 
-1. Acesse o módulo **Master Data**;
-2. Clique na aba **Aplicações**;
-3. Na Aplicação desejada, clique no ícone de engrenagem;
-4. Edite a aplicação;
-5. Clique em **Salvar**.
+Siga as instruções abaixo para alterar uma aplicação:
 
-## Como excluir a aplicação
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+3. Na aplicação desejada, clique no ícone de engrenagem <i class="fas fa-cog"></i>.
+4. Edite a aplicação.
+5. Clique em `Salvar`.
+
+## Excluir aplicação
+
+Siga as instruções abaixo para deletar uma aplicação:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Na aplicação desejada, clique no ícone de engrenagem <i class="fas fa-cog"></i>.
+4. Clique em **Aplicações**.
+5. Na linha da aplicação desejada, clique no botão de exclusão ⛔.
+6. Clique em `OK`.
 
-1. Acesse o módulo **Master Data**;
-2. Clique na aba **Aplicações**;
-3. Na Aplicação desejada, clique no ícone de engrenagem;
-4. Clique na opção **Aplicações**;
-5. Na Aplicação desejada, clique no botão **Excluir**, em vermelho.
diff --git a/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
index 97d89ab47..f293c3058 100644
--- a/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -22,7 +22,7 @@ Com o fim de aplicar um preço diferenciado a produtos pelo XML, é preciso asso
   2. Clique em `Alterar` no arquivo XML que deseja editar. Caso deseje criar um novo, leia nosso artigo [Configurar XML](https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242).
   3. Aqui, você deve checar se os campos relacionados ao preço do SKU (Menor Preço do Produto, Maior Preço do Produto, Preço Original do SKU, Preço Atual do SKU e Preço Atual do SKU + Taxas) estão preenchidos. Pelo menos um dos campos deve ser preenchido para a operação funcionar corretamente.
   4. Preencha o campo **Tabelas de Preços** com o nome da tabela de preços desejada. Em seguida, clique na caixa de seleção referente à tag na coluna **Exibe Conteúdo**. É necessário que a tabela de preços selecionada tenha preços fixos cadastrados. Caso contrário, a configuração não será realizada.
-![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
+![PT-tabela de precos](//images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
 <div class="alert alert-warning">
   <p>Uma vez que a tabela de preços seja incluída no XML, todos os campos de preço serão sobrescritos.</p>
 </div>
@@ -35,4 +35,4 @@ Após finalizar o cadastro do XML e salvar as alterações, você pode checar as
 
 Exemplo de XML atualizado:
 
-![XML-exemplo](https://images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
+![XML-exemplo](//images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
diff --git a/docs/tutorials/pt/creating-collections-beta.md b/docs/tutorials/pt/creating-collections-beta.md
index 7f7fed093..d2e9259e5 100644
--- a/docs/tutorials/pt/creating-collections-beta.md
+++ b/docs/tutorials/pt/creating-collections-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Cadastrar Coleções (Beta)'
 id: yJBHqNMViOAnnnq4fyOye
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-08-17T20:29:25.500Z
-updatedAt: 2023-03-29T14:50:46.438Z
-publishedAt: 2023-03-29T14:50:46.438Z
+updatedAt: 2024-03-04T20:48:30.215Z
+publishedAt: 2024-02-22T12:15:26.041Z
 firstPublishedAt: 2020-08-27T15:16:59.673Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -88,37 +88,39 @@ A seleção de produtos pelo Admin VTEX pode ser feita pela lista de produtos, p
 
 Há uma variedade de filtros que podem ser selecionados para reduzir a quantidade de produtos mostrados na lista.
 
-![Coleções-PT](https://images.ctfassets.net/alneenqid6w5/1z2kSTLCnZMCyYwaqeopOU/6e80254a130ea6ec1e4ed11663e91219/Screenshot_2020-08-04_Cole____es.png)
+![Coleções-PT](//images.ctfassets.net/alneenqid6w5/1z2kSTLCnZMCyYwaqeopOU/6e80254a130ea6ec1e4ed11663e91219/Screenshot_2020-08-04_Cole____es.png)
 
 Você pode criar novos filtros a partir de outros critérios que não são abordados nos filtros pré-determinados. As imagens abaixo exemplificam essas opções:
 
-![Novo filtro - PT](https://images.ctfassets.net/alneenqid6w5/7s94eqKdl8d3xCPI5wPfOK/d786e39f3886c90831907fc92466f640/Screenshot_14.png)
+![Novo filtro - PT](//images.ctfassets.net/alneenqid6w5/7s94eqKdl8d3xCPI5wPfOK/d786e39f3886c90831907fc92466f640/Screenshot_14.png)
 
-![Novo filtro detalhes - PT](https://images.ctfassets.net/alneenqid6w5/60i6UvQEcghy6zsku1hTia/c158886033e62d698bf043c18d27a659/Screenshot_2020-08-05_Cole____es.png)
+![Novo filtro detalhes - PT](//images.ctfassets.net/alneenqid6w5/60i6UvQEcghy6zsku1hTia/c158886033e62d698bf043c18d27a659/Screenshot_2020-08-05_Cole____es.png)
 
 Para adicionar um produto à coleção, basta clicar no ícone <i class="fas fa-plus-circle" title = "check em círculo"></i> referente ao produto. Assim, ele será salvo na coleção automaticamente.
 
 Caso deseje mais informações sobre o item, clique no ícone <i class="fas fa-external-link-alt" title = "link externo"></i> para abrir a página de produto ou clique na imagem para ampliá-la.
 
-![PT-colecao-adicionar](https://images.ctfassets.net/alneenqid6w5/68r7LGGksNkoM9oqjwStFM/a7ac4e3caea2639e7581bae747f2ee1f/PT-colecao-adicionar.gif)
+![PT-colecao-adicionar](//images.ctfassets.net/alneenqid6w5/68r7LGGksNkoM9oqjwStFM/a7ac4e3caea2639e7581bae747f2ee1f/PT-colecao-adicionar.gif)
 
 Caso você deseje realizar uma inclusão massiva, aplique pelo menos um dos filtros e clique no botão `Adicionar Todos`. Vale ressaltar que o produto precisa ter pelo menos um SKU cadastrado para ser incluído a uma coleção.
 
-![Coleções Adicionar Todos - PT](https://images.ctfassets.net/alneenqid6w5/7Bo9F9fU4sGW4FqBTBquD8/20fa966d9f2bb7339ad12140fc722d2b/Screenshot_22.png)
+![Coleções Adicionar Todos - PT](//images.ctfassets.net/alneenqid6w5/7Bo9F9fU4sGW4FqBTBquD8/20fa966d9f2bb7339ad12140fc722d2b/Screenshot_22.png)
 
 <div class = "alert alert-danger">
-  <p>Não adicione massivamente uma quantidade acima de 150 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.</p>
+  <p>Não adicione massivamente uma quantidade acima de 100 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.</p>
 </div>
 
 #### Por planilha
 
-Você também pode adicionar os itens em uma coleção por planilha. 
+Você também pode adicionar os itens em uma coleção por planilha.
+
+<div class = "alert alert-info">O limite máximo para importação e exportação é de 10 mil SKUs por operação.</div>
 
 Para isso, siga os passos a seguir:
 
   1. No painel da sua coleção, clique no botão `Importar`.  
   2. Clique na opção **Adicionar produtos à coleção** e, em seguida, no botão `Importar`.  
-  3. Clique em **Baixe o modelo** para ter o modelo correto da planilha, como o  exemplo abaixo: ![Coleção planilha - PT](https://images.ctfassets.net/alneenqid6w5/2qWba0T6YYLIiwH8vy2JOX/567b23d9479f9e5d8d2929590aa81779/colecao-planilha_-PT.png)
+  3. Clique em **Baixe o modelo** para ter o modelo correto da planilha, como o  exemplo abaixo: ![Coleção planilha - PT](//images.ctfassets.net/alneenqid6w5/2qWba0T6YYLIiwH8vy2JOX/567b23d9479f9e5d8d2929590aa81779/colecao-planilha_-PT.png)
   4. Preencha a planilha com os IDs ou RefIDs dos Produtos ou dos SKUs. Adicione apenas um ID em cada linha. Independente do ID que você preencher, todos os SKUs do produto selecionado serão adicionados à coleção depois da importação.  
   5. Depois de preencher a planilha, salve as alterações e importe o documento no Admin. Você pode soltar o arquivo na área indicada ou clicar em **Escolha um arquivo**. São aceitos arquivos em formato CSV ou XML. Em caso de um arquivo CSV, use `,` para delimitar os campos.
   6. Para finalizar, clique em `Importar`.
@@ -135,11 +137,11 @@ Os produtos podem ser removidos tanto pela seleção de itens na lista do módul
 
 Para remover um item da coleção, basta clicar no <i class="far fa-check-circle" title="check em círculo"></i> do produto.
 
-![PT-colecao-remover](https://images.ctfassets.net/alneenqid6w5/4C7mFX4v4gpVTNV1D9QL2h/e01f7dadd8cedea525b6545eb853a355/PT-colecao-remover.gif)
+![PT-colecao-remover](//images.ctfassets.net/alneenqid6w5/4C7mFX4v4gpVTNV1D9QL2h/e01f7dadd8cedea525b6545eb853a355/PT-colecao-remover.gif)
 
 Caso você deseje realizar uma remoção massiva, aplique um dos filtros e clique no botão `Remover Todos`.
 
-![Coleções remover filtrados - PT](https://images.ctfassets.net/alneenqid6w5/1Ahv25AQ16j2B6zIV7YJrO/0f7aff71f6a25c295315745a69561c1c/Screenshot_23.png)
+![Coleções remover filtrados - PT](//images.ctfassets.net/alneenqid6w5/1Ahv25AQ16j2B6zIV7YJrO/0f7aff71f6a25c295315745a69561c1c/Screenshot_23.png)
 
 Você também pode clicar no botão <i class="far fa-check-circle" title = "check em círculo"></i> (**Produtos nesta coleção**) na barra superior e depois selecionar `Remover Todos`.
 
@@ -172,7 +174,7 @@ Para alterar a ordem da sua coleção, siga os passos abaixo:
 
   b. Selecione a caixa dos produtos que deseja alterar e clique em `Mover de Posição`. Indique o número da nova posição e, para finalizar, clique em `Mover`. Aqui é possível reordenar massivamente os itens da lista.
 
-![Coleções mover - PT](https://images.ctfassets.net/alneenqid6w5/WHrP3DW5rGbyXY40Baixh/4291fbe93c0c64759ca44c07b213146d/Cole____es_mover_-_PT.PNG)
+![Coleções mover - PT](//images.ctfassets.net/alneenqid6w5/WHrP3DW5rGbyXY40Baixh/4291fbe93c0c64759ca44c07b213146d/Cole____es_mover_-_PT.PNG)
 
 ## Exportar planilha da coleção
 
diff --git a/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md b/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md
new file mode 100644
index 000000000..5fb85c7ff
--- /dev/null
+++ b/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md
@@ -0,0 +1,62 @@
+---
+title: 'Criar consulta personalizada no Master Data v1'
+id: tutorials_799
+status: PUBLISHED
+createdAt: 2017-04-27T21:57:44.496Z
+updatedAt: 2024-07-17T13:34:47.245Z
+publishedAt: 2024-07-17T13:34:47.245Z
+firstPublishedAt: 2017-04-27T23:03:43.119Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: criar-consulta-personalizada-no-master-data-v1
+locale: pt
+legacySlug: criando-uma-consulta-personalizada-no-master-data
+subcategory: 2AThnkEZAYbk4G4EIs53rL
+---
+
+Uma consulta personalizada no Master Data é um filtro ou combinação de filtros que pode ser salva e acessada diretamente na listagem de registros de um formulário. 
+
+## Pré-requisitos
+
+Antes de criar uma consulta, você precisa seguir os passos descritos em [Filtrar dados no Master Data](https://help.vtex.com/pt/tutorial/filtrando-dados-no-master-data--tutorials_778) para configurar um filtro na entidade de dados e no formulário.
+
+## Salvar uma consulta
+
+Siga o passo a passo abaixo para filtrar os registros de um formulário e salvar uma consulta personalizada.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Certifique-se de que você está na aba **Aplicações**.
+3. Na aplicação desejada, identifique o formulário que deseja visualizar e clique no ícone de listagem <i class="fas fa-bars"></i>.
+
+    Você será direcionado(a) para a listagem de registros desse formulário. Na lateral, você verá os filtros configurados. 
+
+4. Para filtrar, selecione o nome do filtro e seu valor e, em seguida, clique em `Filtrar`.
+
+    É possível filtrar por vários campos ao mesmo tempo e vários valores no mesmo campo. Para retirar um filtro, clique no `X` ao lado do valor.
+
+5. Clique no botão `Salvar consulta`.
+6. Nomeie a consulta personalizada.
+7. Clique em `OK`.
+8. Clique em `OK` novamente.
+9. Clique na aba **Aplicações**.
+10. Clique no botão `Recarregar aplicações`.
+
+Após seguir as instruções acima, a consulta vai aparecer como uma opção de visualização na listagem do formulário.
+
+![consultas-2-pt](//images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/e75d69f663b3042804ad5057c8e66025/consultas-2-pt.png)
+
+Você também pode acessar as consultas salvas clicando no botão Consultas, na listagem do formulário:
+
+![consultas-pt](//images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/85d44e1fe78c43a0e5f5f8d843de9783/consultas-pt.png)
+
+## Configurar uma consulta padrão
+
+Para determinar que um formulário sempre abra a listagem com uma consulta personalizada em vez de exibir todos os registros, você pode configurar uma consulta padrão. Para isso, siga o passo a passo:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Certifique-se de que você está na aba **Aplicações**.
+3. Na aplicação em que deseja alterar o formulário, clique no símbolo de engrenagem <i class="fas fa-cog"></i>.
+4. Clique no ícone de edição <i class="fas fa-edit"></i> na linha do formulário em que deseja adicionar a consulta padrão.
+5. Na opção **Consulta padrão**, selecione a consulta personalizada que deseja exibir sempre que abrir a lista de registros do formulário.
+6. Clique no botão `Salvar`.
diff --git a/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md b/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md
index 60a615f3a..5c42d203b 100644
--- a/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md
+++ b/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md
@@ -3,8 +3,8 @@ title: 'Criar formulários de Cliente e Endereço em novas lojas'
 id: 46ETfuaGogKwaMau4ESAAM
 status: PUBLISHED
 createdAt: 2017-08-16T16:57:24.708Z
-updatedAt: 2023-03-28T22:59:22.957Z
-publishedAt: 2023-03-28T22:59:22.957Z
+updatedAt: 2024-06-11T17:38:43.775Z
+publishedAt: 2024-06-11T17:38:43.775Z
 firstPublishedAt: 2017-08-16T17:21:19.815Z
 contentType: tutorial
 productTeam: Master Data
@@ -36,13 +36,12 @@ Master Data v2
 É possível criar estes formulários automaticamente, bastando seguir as instruções abaixo para cada loja que desejar.
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. Após autenticado, acesse a seguinte URL, de modo a fazer uma requisição (GET) à API: `meusegundosite.vtexcrm.com.br/api/crm/pvt/provisioning`.
-3. O resultado será uma tela em branco no navegador, mas que corresponde à uma resposta de status "200".
-4. Após alguns minutos, no Master Data, clique em **Área avançada**.
-6. Na opção **Deseja limpar o cache?** clique em **Sim**.
-7. Volte à página inicial do Master Data.
-8. Clique em **Recarregar Aplicações**.
+2. Após a autenticação, acesse a URL a seguir, de modo a fazer uma requisição (GET) à API: `{nomedaloja}.vtexcrm.com.br/api/crm/pvt/provisioning`. Substitua `{nomedaloja}` pelo nome da sua loja.
 
-Concluídos os passos acima, os formulários da aplicação **Profile System** já deverão estar disponíveis em seu Master Data.
+  O resultado será uma tela em branco no navegador, que corresponde a uma resposta de status __200 OK__.
+3. Após alguns minutos, no Master Data, clique em **Configurações avançadas**.
+4. Na opção **Deseja limpar o cache?**, clique em **Sim**.
+5. Clique na aba __Aplicações__ para voltar à página inicial do Master Data.
+6. Clique em **Recarregar aplicações**.
 
-![2017-08-16 141744](//images.contentful.com/alneenqid6w5/1RWM1vPsmwUiqOA6oSEE8w/8c9cf5d38049f2cc6f16b6cc285828b3/2017-08-16_141744.jpg)
+Concluídos os passos acima, os formulários da aplicação **Profile System** já deverão estar disponíveis em seu Master Data.
diff --git a/docs/tutorials/pt/creating-form-in-master-data.md b/docs/tutorials/pt/creating-form-in-master-data.md
index 6c7a30660..ad73db84b 100644
--- a/docs/tutorials/pt/creating-form-in-master-data.md
+++ b/docs/tutorials/pt/creating-form-in-master-data.md
@@ -3,8 +3,8 @@ title: 'Criar formulário no Master Data'
 id: tutorials_1047
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:35.614Z
-updatedAt: 2023-03-28T23:49:11.948Z
-publishedAt: 2023-03-28T23:49:11.948Z
+updatedAt: 2024-06-19T15:04:30.932Z
+publishedAt: 2024-06-19T15:04:30.932Z
 firstPublishedAt: 2017-04-27T23:03:43.083Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,37 +15,45 @@ legacySlug: criando-formulario-no-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-Formulário é a forma de exibição e manipulação de uma entidade de dados. Logo, formulário é um agrupador de campos. Apesar de sempre estar ligado a uma entidade, ele não precisa necessariamente ter todos os campos da entidade, podendo ser ajustado conforme a necessidade, ou seja, podem existir diferentes formulários para a mesma entidade. Ex.: Formulário compra com os campos Id, cliente e data.
+Um formulário serve como interface para visualização e manipulação de uma entidade de dados. Em essência, ele atua como um agrupador de campos.
 
-## Como criar
+Embora esteja sempre associado a uma entidade de dados, não é obrigatório que contenha todos os campos relacionados a ela, podendo ser personalizado conforme a demanda. Dessa forma, é possível criar diferentes formulários para uma mesma entidade, adaptando-se às distintas necessidades. Por exemplo, um formulário de compra pode incluir campos como ID, cliente e data.
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
-2. Clique na aba **Aplicações.**
-3. Na aplicação em que deseja criar o formulário, clique no símbolo de engrenagem.
-4. Abrirá a listagem de formulários, clique no botão **Novo.**
-5. Preencha os campos conforme abaixo (campos divididos por seção).
-6. Clique no botão **Salvar.**
+Para criar um formulário, siga os passos abaixo:
 
-## Entenda os campos
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Certifique-se que está na aba __Aplicações__.
+3. Na aplicação em que deseja criar o formulário, clique no ícone de engrenagem <i class="fas fa-cog"></i>.
+4. Na listagem de formulários, clique no botão `Novo`.
+5. Preencha os campos descritos na seção [Campos do formulário](#campos-do-novo-formulario).
+6. Clique no botão `Salvar`.
 
-- **Nome: **Nome do formulário
-- **Filtros: **Campos marcados como filtro da entidade, esses campos formarão os filtros laterais do formulário. Deve ser inserido o nome interno do campo. Para mais de um campo, separe-os por vírgulas. Exemplo: campo1,campo2.
-- **Entidade de Dados: **A entidade de dados para a qual o formulário vai salvar e exibir os dados. 
-- **Destaques de busca: **Os campos que serão listados nos resultados de busca. Deve ser inserido o nome interno do campo. Para mais de um campo, separe-os por vírgulas. Exemplo: se busco por cliente, quero que na listagem de resultado apareça o CPF do cliente e o nome, então, preencho o campo com cpf,nome.
-- **Consultas na visualização: **Habilita uma nova seção no formulário de exibição, com registros de uma entidade relacionada à entidade do formulário. As informações exibidas serão relacionadas ao registro que está sendo visualizado. Exemplo: Na entidade Atendimento existe um campo relacionado com a entidade Cliente. Então, no formulário Cliente, no campo Consultas na visualização, insira este campo de atendimento que faz referência à Cliente. Se a sigla da entidade Atendimento for AT e o nome do campo for cliente, deve ser inserido: “AT.Cliente”, que serão carregados os atendimentos do cliente que está sendo visualizado no formulário. ![registrosRelacionados2](//images.contentful.com/alneenqid6w5/2NrlYdzzR66Og4waCIekGe/e4d47ef3e257c749c09c0c9151383c45/registrosRelacionados2.png)![registrosRelacionados](//images.contentful.com/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/d80177bdf01586c97f1321c74c881ac3/registrosRelacionados-1.png)
+## Campos do novo formulário
 
-Após preencher os campos obrigatórios, aparecerão as abas disponíveis para configuração. Seguem abaixo os campos para cada uma delas.
+- **Nome:** Nome do formulário.
+- **Filtros:** Campos marcados como filtro da entidade, esses campos formarão os filtros laterais do formulário. Deve ser inserido o nome interno do campo. Para mais de um campo, separe-os por vírgulas. Exemplo: campo1,campo2.
+- **Entidade de dados:** A entidade de dados para a qual o formulário vai salvar e exibir os dados. 
+- **Destaques da busca:** Os campos que serão listados nos resultados de busca. Deve ser inserido o nome interno do campo. Para mais de um campo, separe-os por vírgulas. Exemplo: para buscar por cliente e fazer com que na listagem de resultado apareça o CPF do cliente e o nome, é necessário preencher o campo com CPF e nome.
+- **Consultas de visualização:** Habilita uma nova seção no formulário de exibição, com registros de uma entidade relacionada à entidade do formulário. As informações exibidas serão relacionadas ao registro que está sendo visualizado.
 
-- **Campos da Listagem: **Aqui, devem ser selecionados os campos que aparecerão na listagem de registros, ao clicar para visualizar o formulário. Para isso, basta selecionar as caixas de seleção ao lado dos campos que você deseja que apareçam na listagem. Além disso, é possível configurar a larguta do campo na listagem (a largura da coluna), a ordem de exibição e a ordenação. A ordem de exibição dos campos da listagem seguirá a ordem dessa tela, ou seja, para que um campo apareça na primeira coluna, clique na seta para cima, até que este seja o primeiro campo. A ordenação é definida por um campo, você deve selecioná-lo e escolher entre ordenação ascendente (Asc) ou descendente (Desc).
-- **Schemas de Layout: **No Schemas de layout, será feita a definição de como realmente os campos serão exibidos no formulário, tanto para visualização quanto para edição e criação. Ou seja, nesta parte que realmente será configurado onde cada campo ficará dentro do formulário e tudo pode ser dividido por seções.
+   Por exemplo, na entidade __Lista de compras__, existe um campo relacionado com a entidade __Cliente__. Então, no formulário __Cliente__, no campo __Consultas de visualização__, insira este campo de atendimento que faz referência à entidade __Cliente__.
 
-1. Clique no botão **Incluir nova seção**;
-2. Preencha o campo **Nome**;
-3. Arraste um campo da lista **Campos disponíveis** para a coluna **Campos da coluna 1**. O mesmo pode ser feito para a coluna **Campos da coluna 2**. 
+   Se a sigla da entidade __Lista de compras__ for __LC__ e o nome do campo for __Cliente__, deve ser inserido `LC.Cliente` para carregar os atendimentos do cliente que está sendo visualizado no formulário.
 
-Esses três passos podem ser repetidos até que se tenha o formulário no formato em que se deseja. É possível inserir vários campos na mesma coluna, assim como é possível criar várias seções. 
+   ![registrosRelacionados-pt](//images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/ce0d55331a7bbb03ce1213bb85b7efd0/image_3.png)
 
-- **Consultas: **Essa aba serve apenas para exibir as [consultas criadas na listagem](/pt/tutorial/criando-uma-consulta-personalizada-no-master-data/).
-- **Folha de Estilo: **Local para inserção de CSS para edição do front-end do formulário.
+Após preencher os campos obrigatórios, aparecerão as abas disponíveis para configuração. Confira abaixo os campos de cada uma delas.
 
-<video class="wp-video-shortcode" id="video-1047-3" width="840" height="411" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/7oRARnBsVamuk8iQ0mogQa/438e55214f38f7f16634da4fbc238d68/CriandoFormulario-1.mp4?_=3" />[//assets.contentful.com/alneenqid6w5/7oRARnBsVamuk8iQ0mogQa/438e55214f38f7f16634da4fbc238d68/CriandoFormulario-1.mp4](//assets.contentful.com/alneenqid6w5/7oRARnBsVamuk8iQ0mogQa/438e55214f38f7f16634da4fbc238d68/CriandoFormulario-1.mp4 "//assets.contentful.com/alneenqid6w5/7oRARnBsVamuk8iQ0mogQa/438e55214f38f7f16634da4fbc238d68/CriandoFormulario-1.mp4")</video>
+- **Campos da lista:** Aqui, devem ser selecionados os campos que aparecerão na listagem de registros, ao clicar para visualizar o formulário. Para isso, basta marcar as caixas de seleção ao lado dos campos que você deseja que apareçam na listagem. Além disso, é possível configurar a largura do campo na listagem (a largura da coluna), a ordem de exibição e a ordenação.
+
+   A ordem de exibição dos campos da listagem seguirá a ordem dessa tela, ou seja, para que um campo apareça na primeira coluna, clique na seta para cima, até que este seja o primeiro campo. A ordenação é definida por um campo, você deve selecioná-lo e escolher entre ordenação ascendente (Asc) ou descendente (Desc).
+- **Esquemas de layout:** neste campo, será feita a definição de como realmente os campos serão exibidos no formulário, tanto para visualização quanto para edição e criação. Ou seja, nesta parte você deve configurar onde cada campo ficará dentro do formulário e como os campos serão divididos por seções. Para isso, siga os passos abaixo:
+
+   1. Clique no botão `Adicionar nova seção`.
+   2. Preencha o campo **Nome** para nomear a seção.
+   3. Arraste um campo da lista **Campos disponíveis** para a coluna **Campos da coluna 1**. O mesmo pode ser feito para a coluna **Campos da coluna 2**. 
+
+  Esses três passos podem ser repetidos até que se tenha o formulário no formato em que se deseja. É possível inserir vários campos na mesma coluna, assim como é possível criar várias seções. 
+
+- **Consultas:** Essa aba serve apenas para exibir as [consultas criadas na listagem](https://help.vtex.com/pt/tutorial/criando-uma-consulta-personalizada-no-master-data--tutorials_799).
+- **Folha de estilo:** Local para inserção de CSS para edição do frontend do formulário.
diff --git a/docs/tutorials/pt/creating-landing-pages-per-binding.md b/docs/tutorials/pt/creating-landing-pages-per-binding.md
index 9200ac398..438bd5fe2 100644
--- a/docs/tutorials/pt/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/pt/creating-landing-pages-per-binding.md
@@ -23,7 +23,7 @@ No Admin, é possível criar *landing pages* customizadas por [*binding*](https:
 2. Selecione o *binding* no qual deseja criar a nova *landing page* no menu suspenso da página.
 3. Clique no botão `Criar nova`.
 
-  ![pt-landing-page-binding](https://images.ctfassets.net/alneenqid6w5/4o8DseduoS1fsMR98iRt1R/8c75f884af19cf8e61e4c4adb1e2a83f/pt-landing-page-binding.png)
+  ![pt-landing-page-binding](//images.ctfassets.net/alneenqid6w5/4o8DseduoS1fsMR98iRt1R/8c75f884af19cf8e61e4c4adb1e2a83f/pt-landing-page-binding.png)
 
 4. Na seção `Detalhes da página`, preencha os campos e defina os metadados para sua nova *landing page* de acordo com os valores esperados:
 
diff --git a/docs/tutorials/pt/creating-landing-pages.md b/docs/tutorials/pt/creating-landing-pages.md
index 7b5027aaa..a9cc47fe5 100644
--- a/docs/tutorials/pt/creating-landing-pages.md
+++ b/docs/tutorials/pt/creating-landing-pages.md
@@ -3,8 +3,8 @@ title: 'Criando landing pages'
 id: 2DqFleXKz0Vsg3KhHLuUEB
 status: PUBLISHED
 createdAt: 2022-02-02T13:57:03.484Z
-updatedAt: 2023-03-24T22:24:37.311Z
-publishedAt: 2023-03-24T22:24:37.311Z
+updatedAt: 2024-08-01T13:10:40.896Z
+publishedAt: 2024-08-01T13:10:40.896Z
 firstPublishedAt: 2022-02-02T14:41:53.952Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -28,7 +28,7 @@ No Admin, você pode criar landing pages personalizadas, como páginas para ofer
 
 2.Clique em **CRIAR PÁGINA**.
 
-![Criando Landing pages](https://images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/f9472895136b58039a0f1639a6877652/cms-pages-pt.png)
+![Criando Landing pages](//images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/f9472895136b58039a0f1639a6877652/cms-pages-pt.png)
 
 3.Na seção Detalhes da página, preencha os campos abaixo para definir os metadados da página:
 
@@ -40,6 +40,11 @@ No Admin, você pode criar landing pages personalizadas, como páginas para ofer
 | Descrição | Resumo da nova página que será exibida nas páginas de resultados dos mecanismos de busca. |
 | Palavras-chave | Tópicos que definem o conteúdo da página e ajudam a mostrar a página aos usuários interessados nos resultados dos mecanismos de busca. |
 
+<div class="alert alert-warning">
+<p>Para evitar conflitos e garantir a integridade do sistema, não é permitida a alteração da URL de uma rota já existente. Caso precise modificar uma URL, recomenda-se criar uma nova página com o caminho desejado e desativar a antiga, se necessário.
+</p>
+</div>
+
 <div class = "alert alert-info">
 <p>Os cinco campos acima têm um impacto direto nos acessos à loja e em seu posicionamento nos resultados dos mecanismos de busca. Ao preencher os metadados da página, considere as melhores práticas de SEO.
 </p>
diff --git a/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md b/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md
new file mode 100644
index 000000000..a4a868911
--- /dev/null
+++ b/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md
@@ -0,0 +1,97 @@
+---
+title: 'Criar Regra de merchandising - Editor manual'
+id: 3jrXB1MSvi14ezvKancorc
+status: PUBLISHED
+createdAt: 2024-06-27T17:14:53.957Z
+updatedAt: 2024-06-27T17:15:56.346Z
+publishedAt: 2024-06-27T17:15:56.346Z
+firstPublishedAt: 2024-06-27T17:15:56.346Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: criar-regra-de-merchandising-editor-manual
+locale: pt
+legacySlug: criar-regra-de-merchandising-editor-manual
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) no Editor manual do VTEX Intelligent Search, você precisa seguir os passos abaixo.
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca.
+2. Em **Intelligent Search**, clique em **Regras de merchandising**.
+3. Clique no botão  `Novo`.
+4. Preencha os seguintes campos:
+    * **Nome**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
+    * **Data de início (opcional)**: agendamento da data a partir da qual a regra de merchandising será aplicada. A data segue o fuso horário UTC-0.
+    * **Data de término (opcional)**: agendamento da data em que a regra de merchandising não será mais aplicada às buscas na loja. A data segue o fuso horário UTC-0.
+    * **Aplicar aos idiomas:** idiomas aos quais a regra de merchandising será aplicada. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Clique em **Editor manual**. Para mais informações sobre cada editor, confira [Tipos de edição](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
+6. Clique em `Próximo`.
+7. Se necessário, altere as informações básicas já definidas sobre a nova regra de merchandising na seção [Informação Geral](#informacao-geral).
+8. Defina as [Regras de ativação](#regras-de-ativacao), ou seja, o conjunto de condições que determinam quando a Regra de merchandising será aplicada.
+9. Defina as [Regras de customização](#regras-de-customizacao), ou seja, o conjunto de condições para controlar o resultado das buscas que se encaixarem nas regras de ativação definidas no passo 8.
+    Para aplicar o efeito de customização desejado, é necessário cadastrar uma ou mais condições nesta etapa. Para entender como funciona o cadastro de uma condição, leia [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+10. Clique em `Salvar`.
+
+<div class="alert alert-info">
+<p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
+</div>
+
+## Exemplo
+
+Considere o seguinte exemplo: você quer promover produtos da marca Beautyx durante a semana de Carnaval, ou seja, quando o cliente pesquisar por "sabonete" ou "shampoo", a busca precisa promover produtos da marca. Para isso, a configuração precisa ser feita da seguinte forma:
+
+* **Nome**: Promoção Carnaval
+* **Data de início**: selecionar o primeiro dia do Carnaval.
+* **Data de término**: selecionar o último dia do Carnaval.
+* **Regras de ativação:**
+        * `Termo é sabonete`
+        ou
+        * `Termo é shampoo`
+* **Regras de customização**:
+    * **Promover**
+        * `marca é beautyx`
+
+## Campos do Editor manual
+
+### Informação Geral
+
+* **Nome**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
+* **Data de início**: agendamento da data a partir da qual a regra de merchandising será aplicada. A data segue o fuso horário UTC-0.
+* **Data de término**: agendamento da data em que a regra de merchandising não será mais aplicada às buscas na loja. A data segue o fuso horário UTC-0.
+* **Idiomas:** idiomas aos quais a regra de merchandising será aplicada.
+
+### Regras de ativação
+
+* **Ativação global**: se você ativar esta opção, a regra de merchandising vai estar sempre ativa e englobar todos os termos e filtros da pesquisa, sem necessidade de configurar condições para regras de ativação. Isso permite adicionar, remover, promover e despromover produtos de todas as buscas da loja.
+
+    Por outro lado, se você optar por manter a ativação global desabilitada, será necessário cadastrar pelo menos uma condição para compor as regras de ativação. Para detalhes sobre o cadastro de uma condição, leia [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+
+* `Preencher a partir de uma URL`: adicione a URL da página de busca em que as regras de ativação serão aplicadas. A URL precisa incluir `map` e `query` para funcionar, respeitando o seguinte formato: `https://{accountName}.myvtex.com/busca/{termo}?map=ft&query={termo]`. É necessário substituir `{accountName}` pelo nome da conta VTEX e `{termo}` pelo termo de busca.
+* `Adicionar condição`: ao criar uma condição, a regra de merchandising só se aplicará aos casos que cumprirem com a combinação de condições estabelecidas.  Para entender como criar condições, leia [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+
+### Regras de customização
+
+* **Adicionar:** inclui as condições selecionadas no resultado, ou seja, adiciona produtos que não estariam no resultado de busca. A ordem dos produtos cadastrados não é levada em consideração no resultado da busca.
+
+    Produtos adicionados também são colocados nas primeiras posições, contudo, possuem um peso menor do que o **Promover**. Portanto, caso tenha um produto sendo adicionado e outro promovido, primeiro apareceria o promovido e depois o adicionado.
+
+* **Remover:** exclui as condições selecionadas do resultado, ou seja, remove produtos que estariam no resultado de busca.
+
+  <div class="alert alert-info">
+   <p><strong>Adicionar</strong> e <strong>Remover</strong> são compatíveis com outros tipos de ordenação que não são baseadas na relevância configurada. Ou seja, se você adicionar ou remover um produto através de uma regra de merchandising e o cliente da sua loja ordenar os resultados da busca por preço, por exemplo, os produtos serão ordenados por preço mas os produtos exibidos vão respeitar a regra de merchandising.</p>
+  </div>
+
+* **Promover:** oferece destaque às condições selecionadas no resultado. Isso concede maior relevância a um produto que já seria exibido no resultado de busca.
+
+    A ordem das condições influencia a prioridade em que elas serão apresentadas. Além disso, um produto incluído neste campo só é promovido em um único resultado.
+
+* **Despromover**: oculta as condições selecionadas no resultado. Isso permite despriorizar um produto que já seria exibido no resultado de busca.
+
+  <div class="alert alert-info">
+   <p><strong>Promover </strong>e <strong>Despromover </strong>funcionam somente quando o cliente da sua loja ordena os resultados da busca por relevância. Caso ele(a) ordene os resultados por preço, por exemplo, os produtos serão ordenados estritamente pelo preço e a regra de merchandising não será utilizada.</p>
+  </div>
+
+  <div class="alert alert-warning">
+   <p>Não configure condições que afetem os mesmos produtos nas seções <strong>Promover</strong> e <strong>Despromover</strong>, pois são efeitos contrários. Essa configuração equivocada influencia negativamente no comportamento da funcionalidade e não apresenta os resultados desejados.</p>
+  </div>
diff --git a/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
index 44eb37b13..c8376db34 100644
--- a/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Criar Regra de merchandising - Editor visual (Beta)'
 id: 6xteumx9MsDt0uEppbChu3
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-03T21:05:14.304Z
-updatedAt: 2023-04-11T22:34:40.303Z
-publishedAt: 2023-04-11T22:34:40.303Z
+updatedAt: 2024-01-29T17:17:03.584Z
+publishedAt: 
 firstPublishedAt: 2023-04-03T21:30:34.359Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,61 +19,77 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
   <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
 </div>
 
-O Editor visual (Beta) de [regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
-
-![visual-merch-rules-PT](https://images.ctfassets.net/alneenqid6w5/5Pah0D3Y9CfUyczqFR99bd/005f5072313e3587807cf0b334ce6177/visual-merch-rules-PT.png)
-
-<ol class="mv7" type="I">
-    <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir termos de busca para aplicação da regra de merchandising.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#adicionar-filtros-e-condicoes" rel="noopener noreferrer"
-            target="_self"
-            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a>
-        para aplicação da regra de merchandising.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por linha.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por página.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de busca.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Arrastar produto para a posição desejada nos resultados de busca. É
-        possível apenas arrastar produtos que foram fixados (ação IX).</li>
-    <li class="t-body c-on-base mb5 lh-copy">Ocultar produto nos resultados de busca. Esta ação não pode ser revertida,
-        por isso, para que um produto volte a aparecer nos resultados, é necessário criar outra regra de merchandising.
-    </li>
-    <li class="t-body c-on-base mb5 lh-copy">Fixar produto nas primeiras posições dos resultados de busca. Ao fixar o
-        produto A e, em seguida, fixar o produto B, eles aparecerão nesta ordem nos resultados de busca, antes dos
-        demais.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Ver detalhes do produto.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Cancelar edição.</li>
-    <li class="t-body c-on-base mb5 lh-copy">Salvar configurações.</li>
-</ol>
-
-## Configurar regra de merchandising
-
-Para configurar uma regra de merchandising no Editor visual, siga os passos abaixo.
+Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) do VTEX Intelligent Search utilizando o [Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), siga os passos abaixo.
 
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca.
 2. Em **Intelligent Search**, clique em **Regras de merchandising**.
-3. Clique no botão  `Novo`.
+3. Clique no botão `+ Adicionar`.
 4. Preencha os seguintes campos:
-    * **Nome**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
+    * **Nome da regra**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
     * **Data de início (opcional)**: agendamento da data a partir da qual a regra de merchandising será aplicada. A data segue o fuso horário UTC-0.
     * **Data de término (opcional)**: agendamento da data em que a regra de merchandising não será mais aplicada às buscas na loja. A data segue o fuso horário UTC-0.
-    * **Idiomas:** idiomas aos quais a regra de merchandising será aplicada.
+    * **Aplicar aos idiomas:** idiomas aos quais a regra de merchandising será aplicada. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
 5. Clique em **Editor visual**. Para mais informações sobre cada editor, confira [Tipos de edição](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
 6. Clique em `Próximo`.
-7. Para definir um termo de busca que determina a aplicação da regra de merchandising, digite o termo na barra de busca (item II na imagem anterior). É necessário definir ao menos um termo ou um filtro (passo 8) para a aplicação da regra.
-8. Para criar um filtro para aplicação da regra de merchandising (item III na imagem anterior), siga o passo a passo descrito na seção [Adicionar filtros e condições](#adicionar-filtros-e-condicoes). É necessário definir ao menos um filtro ou um termo (passo 7) para a aplicação da regra.
-9. Se desejar, realize as demais ações opcionais para customizar os resultados de busca (itens IV, V, VII, VIII, IX na imagem anterior).
-10. Clique em `Salvar`.
+7. Defina ao menos um termo de busca ou um filtro para a aplicação da regra de merchandising:
+    * Para definir um termo de busca, digite o termo na barra de busca (item **II** na seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual])).
+    * Para criar um filtro para aplicação da regra de merchandising (item **III** na seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual])), siga o passo a passo descrito na seção [Adicionar filtros e condições](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes).
+8. Se desejar, realize as ações opcionais citadas a seguir para customizar os resultados de busca:
+    * Definir quantidade de itens por linha nos resultados de busca.
+    * Definir quantidade de itens por página nos resultados de busca.
+    * Ocultar produto nos resultados de busca.
+    * Pinar produto, ou seja, fixá-lo nas primeiras posições dos resultados de busca.
+    * Arrastar produto pinado para a posição desejada nos resultados de busca.
+    * Editar configurações iniciais da regra de merchandising, que incluem o nome da regra, as datas de início e de término e, caso a loja utilize o [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO), os idiomas aos quais ela será aplicada.
+
+    Saiba mais sobre essas ações nos itens **IV, V, VI, VIII, IX** e **XI** da seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual]).
+9. Clique em `Salvar`.
 
 <div class="alert alert-info">
   <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
 </div>
 
+## Ações disponíveis no Editor visual
+
+O Editor visual de regras de merchandising do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
+
+![visual-merch-rules-PT-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir termos de busca para aplicação da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#adicionar-filtros-e-condicoes" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a>
+        para aplicação da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por linha nos resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por página nos resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ocultar produto nos resultados de busca. Produtos ocultos aparecem em cinza com o ícone de olho riscado <i class="far fa-eye-slash"></i> no Editor visual. Para voltar a exibir um produto oculto, passe o cursor sobre ele e clique no ícone de olho <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy"> Ver detalhes do produto. As informações exibidas são:<br /><br />
+	   <ul>
+		  <li class="t-body c-on-base mb5 lh-copy"><strong>Disponível:</strong> indica se o produto está disponível ou não na loja.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Cliques:</strong> quantidade de cliques nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Pedidos:</strong> quantidade de pedidos realizados que incluem o produto nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Receita:</strong> receita que o produto representou nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Data de lançamento:</strong> data de lançamento do produto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Promoção:</strong> indica se o produto faz parte ou não de uma promoção.</li> 
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Desconto:</strong> desconto aplicado sobre o produto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Variedade de matriz disponível: </strong>representa o percentual de SKUs disponíveis do produto. Por exemplo, se um produto tem cinco SKUs e somente três estão disponíveis, a variedade de matriz disponível será 60%, representada como 0.6 neste campo. Se todos os SKUs estiverem disponíveis, o valor do campo será 1.</li>
+	   </ul>
+    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Arrastar produto pinado para a posição desejada nos resultados de busca. É possível apenas arrastar produtos que foram pinados (ação <strong>IX</strong> nesta lista).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Pinar produto, ou seja, fixá-lo nas primeiras posições dos resultados de busca. Ao fixar o produto A e, em seguida, fixar o produto B, eles aparecerão nesta ordem nos resultados de busca, antes dos demais. Para despinar um produto, passe o cursor sobre ele e clique no ícone de alfinete riscado <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar configurações iniciais da regra de merchandising, que incluem o nome da regra, as datas de início e de término e, caso a loja utilize o <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Configurações Multi-idioma (Beta)</a>, os idiomas aos quais ela será aplicada.</li>
+     <li class="t-body c-on-base mb5 lh-copy">Cancelar edição.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Salvar configurações.</li>
+</ol>
+
 ### Adicionar filtros e condições
 
 O filtro é um atributo selecionável pré-definido que restringe os resultados da busca, por exemplo, possibilitando filtrar por todos os produtos de uma categoria ou marca, entre outras condições. Você pode adicionar uma ou mais condições a um filtro, conforme ilustrado a seguir.
 
-![filtros-merchrules-pt](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
+![filtros-merchrules-pt](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
 
 Para adicionar uma condição no Editor visual, siga o passo a passo abaixo. 
 
@@ -85,4 +101,3 @@ Para adicionar uma condição no Editor visual, siga o passo a passo abaixo.
 As condições definidas podem funcionar de forma conjunta (`e`) ou de forma alternativa (`ou`).
 
 No menu <i class="far fa-ellipsis-v"></i> de cada condição existente, é possível `Duplicar` ou `Excluir` a condição. Para desativar todas as condições criadas, clique em `Limpar filtros`.
-
diff --git a/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md b/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
new file mode 100644
index 000000000..1b1ed446a
--- /dev/null
+++ b/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
@@ -0,0 +1,99 @@
+---
+title: 'Criar Regra de merchandising - Editor visual'
+id: 3gPO5CMJ3Off0OtA3EPzow
+status: PUBLISHED
+createdAt: 2024-06-27T17:16:02.371Z
+updatedAt: 2024-06-27T17:16:43.289Z
+publishedAt: 2024-06-27T17:16:43.289Z
+firstPublishedAt: 2024-06-27T17:16:43.289Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: criar-regra-de-merchandising-editor-visual
+locale: pt
+legacySlug: criar-regra-de-merchandising-editor-visual
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) do VTEX Intelligent Search utilizando o [Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), siga os passos abaixo.
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca.
+2. Em **Intelligent Search**, clique em **Regras de merchandising**.
+3. Clique no botão `+ Adicionar`.
+4. Preencha os seguintes campos:
+    * **Nome da regra**: nome da regra de merchandising. Exemplo: promover o produto A quando a pesquisa for Biscoito de chocolate.
+    * **Data de início (opcional)**: agendamento da data a partir da qual a regra de merchandising será aplicada. A data segue o fuso horário UTC-0.
+    * **Data de término (opcional)**: agendamento da data em que a regra de merchandising não será mais aplicada às buscas na loja. A data segue o fuso horário UTC-0.
+    * **Aplicar aos idiomas:** idiomas aos quais a regra de merchandising será aplicada. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+5. Clique em **Editor visual**. Para mais informações sobre cada editor, confira [Tipos de edição](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao).
+6. Clique em `Próximo`.
+7. Defina ao menos um termo de busca ou um filtro para a aplicação da regra de merchandising:
+    * Para definir um termo de busca, digite o termo na barra de busca (item **II** na seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual])).
+    * Para criar um filtro para aplicação da regra de merchandising (item **III** na seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual])), siga o passo a passo descrito na seção [Adicionar filtros e condições](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3#adicionar-filtros-e-condicoes).
+8. Se desejar, realize as ações opcionais citadas a seguir para customizar os resultados de busca:
+    * Definir quantidade de itens por linha nos resultados de busca.
+    * Definir quantidade de itens por página nos resultados de busca.
+    * Ocultar produto nos resultados de busca.
+    * Pinar produto, ou seja, fixá-lo nas primeiras posições dos resultados de busca.
+    * Arrastar produto pinado para a posição desejada nos resultados de busca.
+    * Editar configurações iniciais da regra de merchandising, que incluem o nome da regra, as datas de início e de término e, caso a loja utilize o [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO), os idiomas aos quais ela será aplicada.
+
+    Saiba mais sobre essas ações nos itens **IV, V, VI, VIII, IX** e **XI** da seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual]).
+9. Clique em `Salvar`.
+
+<div class="alert alert-info">
+  <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
+</div>
+
+## Ações disponíveis no Editor visual
+
+O Editor visual de regras de merchandising do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
+
+![visual-merch-rules-PT-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
+
+<ol class="mv7" type="I">
+    <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir termos de busca para aplicação da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir <a href="#adicionar-filtros-e-condicoes" rel="noopener noreferrer"
+            target="_self"
+            class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">filtros</a>
+        para aplicação da regra de merchandising.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por linha nos resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Definir quantidade de itens por página nos resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Ocultar produto nos resultados de busca. Produtos ocultos aparecem em cinza com o ícone de olho riscado <i class="far fa-eye-slash"></i> no Editor visual. Para voltar a exibir um produto oculto, passe o cursor sobre ele e clique no ícone de olho <i class="far fa-eye"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy"> Ver detalhes do produto. As informações exibidas são:<br /><br />
+	   <ul>
+		  <li class="t-body c-on-base mb5 lh-copy"><strong>Disponível:</strong> indica se o produto está disponível ou não na loja.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Cliques:</strong> quantidade de cliques nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Pedidos:</strong> quantidade de pedidos realizados que incluem o produto nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Receita:</strong> receita que o produto representou nos últimos 90 dias.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Data de lançamento:</strong> data de lançamento do produto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Promoção:</strong> indica se o produto faz parte ou não de uma promoção.</li> 
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Desconto:</strong> desconto aplicado sobre o produto.</li>
+			<li class="t-body c-on-base mb5 lh-copy"><strong>Variedade de matriz disponível: </strong>representa o percentual de SKUs disponíveis do produto. Por exemplo, se um produto tem cinco SKUs e somente três estão disponíveis, a variedade de matriz disponível será 60%, representada como 0.6 neste campo. Se todos os SKUs estiverem disponíveis, o valor do campo será 1.</li>
+	   </ul>
+    </li>
+    <li class="t-body c-on-base mb5 lh-copy">Arrastar produto pinado para a posição desejada nos resultados de busca. É possível apenas arrastar produtos que foram pinados (ação <strong>IX</strong> nesta lista).</li>
+    <li class="t-body c-on-base mb5 lh-copy">Pinar produto, ou seja, fixá-lo nas primeiras posições dos resultados de busca. Ao fixar o produto A e, em seguida, fixar o produto B, eles aparecerão nesta ordem nos resultados de busca, antes dos demais. Para despinar um produto, passe o cursor sobre ele e clique no ícone de alfinete riscado <i class="fas fa-thumbtack"></i>.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Navegar entre páginas de resultados de busca.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Editar configurações iniciais da regra de merchandising, que incluem o nome da regra, as datas de início e de término e, caso a loja utilize o <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Configurações Multi-idioma (Beta)</a>, os idiomas aos quais ela será aplicada.</li>
+     <li class="t-body c-on-base mb5 lh-copy">Cancelar edição.</li>
+    <li class="t-body c-on-base mb5 lh-copy">Salvar configurações.</li>
+</ol>
+
+### Adicionar filtros e condições
+
+O filtro é um atributo selecionável pré-definido que restringe os resultados da busca, por exemplo, possibilitando filtrar por todos os produtos de uma categoria ou marca, entre outras condições. Você pode adicionar uma ou mais condições a um filtro, conforme ilustrado a seguir.
+
+![filtros-merchrules-pt](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
+
+Para adicionar uma condição no Editor visual, siga o passo a passo abaixo. 
+
+1. Clique em `Filtro`.
+2. Clique em `Adicionar condição`.
+3. Preencha as condições desejadas. As opções disponíveis estão descritas em [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
+4. Clique em `Salvar`.
+
+As condições definidas podem funcionar de forma conjunta (`e`) ou de forma alternativa (`ou`).
+
+No menu <i class="far fa-ellipsis-v"></i> de cada condição existente, é possível `Duplicar` ou `Excluir` a condição. Para desativar todas as condições criadas, clique em `Limpar filtros`.
diff --git a/docs/tutorials/pt/creating-price-tables.md b/docs/tutorials/pt/creating-price-tables.md
index 5fc61f27e..128c07767 100644
--- a/docs/tutorials/pt/creating-price-tables.md
+++ b/docs/tutorials/pt/creating-price-tables.md
@@ -1,10 +1,10 @@
 ---
 title: 'Criar tabelas de preços '
 id: 58YmY2Iwggyw4WeSCGg24S
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-12-02T21:35:14.220Z
-updatedAt: 2020-11-27T19:39:45.134Z
-publishedAt: 2019-12-31T15:26:59.677Z
+updatedAt: 2023-11-30T16:46:22.924Z
+publishedAt: 2023-11-30T16:46:22.924Z
 firstPublishedAt: 2018-12-02T21:36:28.350Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,19 +17,19 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Para criar uma Tabela de Preços siga os seguintes passos:
 
-1. Clique em **Preços** no menu esquerdo da página
-2. Clique em **Lista de Preços**
-3. Clique no botão **Tabela de Preços**
-4. Seleciona **Criar nova Tabela de Preços**
-5. Escolha o nome da tabela de preços que deseja criar e clique no botão azul **Criar tabela de preços**
+1. No Admin VTEX, acesse **Catálogo >** **Preços >** **Lista de preços**, ou digite **Lista de preços** na barra de busca no topo da página.
+2. Clique no botão **Tabela de preços**.
+3. Selecione **Criar nova tabela**.
+4. Escolha o nome da tabela de preços que deseja criar.
+5. Clique no botão **Criar tabela de preços**
+
+![criar-tabela-de-precos](//images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/9e1cb714619aad7cecfac327a7240277/criar-tabela-precos.gif)
 
-![TutorialPriceTablePT2 2806](https://images.ctfassets.net/alneenqid6w5/1mLQywsplJORnUU5uejl8z/2c9edb9697f8dabfbbe4375f0b064d5d/TutorialPriceTablePT2_2806.gif)
- 
  Para encontrar uma Tabela de Preço:
-  
+
  1. Clique em **Tabela de Preço**
  2. Digite o nome da tabela que deseja encontrar no campo **Buscar**
- 
+
 Para incluir preços na tabela de preços, você precisará cadastrar um preço base aos seus SKUs. Veja como fazer neste [tutorial](https://help.vtex.com/pt/tutorial/cadastrar-o-preco-base-de-um-produto--4S9SbPWlVmOAAWO6yq8wE6).
 
 <div class="alert alert-info">
diff --git a/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
index b59d3d213..0041b33d6 100644
--- a/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
@@ -62,9 +62,9 @@ Na configuração abaixo, por exemplo, apenas registros `funcionario` com o valo
 
 Dessa forma, você poderia configurar também `funcionario=false`, em que apenas registros `funcionario` com valor `false` no campo receberiam a promoção.
 
-![Campo funcionário Master Data PT](https://images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/06fd3f196a18b3d331742a01bb4ef2d6/Campo_funcion__rio_Master_Data_PT.png)
+![Campo funcionário Master Data PT](//images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/06fd3f196a18b3d331742a01bb4ef2d6/Campo_funcion__rio_Master_Data_PT.png)
 
-![Cluster de clientes PT](https://images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/c1d0536a53150d809b8c6c74b5a81b12/Cluster_de_clientes_PT.png)
+![Cluster de clientes PT](//images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/c1d0536a53150d809b8c6c74b5a81b12/Cluster_de_clientes_PT.png)
 
 Considerando um campo do tipo **[Varchar](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos)**, poderíamos configurar `funcionario="sim"` para que apenas clientes com valor `"sim"` no campo recebessem a promoção.
 
@@ -82,8 +82,8 @@ A expressão `{nomedapropriedade} contains {valor}` deve ser utilizada quando a
 
 Por exemplo, caso você queira criar um cluster apenas com clientes cujos emails contenham `@teste.com`, a configuração seria igual à representada na imagem abaixo.
 
-![Campo Email Master Data](https://images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
+![Campo Email Master Data](//images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
 
-![cluster email PT](https://images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/271cdcec5cdf081311215a57cfa2994c/cluster_email_PT.PNG)
+![cluster email PT](//images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/271cdcec5cdf081311215a57cfa2994c/cluster_email_PT.PNG)
 
 Nesse caso, `email contains test.com` será verdadeiro, por exemplo, quando o valor for `joao@test.com` e falso quando o valor for `joao@test.org`.
diff --git a/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
index 8949712f0..302ade034 100644
--- a/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
@@ -1,9 +1,9 @@
 ---
 title: 'Criar relacionamentos entre entidades do Master Data usando o Admin'
 id: 1qzbCit8SYXbKwrT5x2FfA
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-08-11T13:48:26.272Z
-updatedAt: 2022-10-17T19:11:39.513Z
+updatedAt: 2024-06-06T19:36:29.525Z
 publishedAt: 2022-10-17T19:11:39.513Z
 firstPublishedAt: 2020-08-18T19:47:29.772Z
 contentType: tutorial
@@ -15,85 +15,86 @@ legacySlug: criar-relacionamento-com-entidades-e-documentos-do-master-data-usand
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-## O que é um relacionamento entre entidades do Master Data?
 Um relacionamento entre entidades é uma referência entre documentos que pertencem a domínios distintos. Essa referência é definida por um campo em uma dessas entidades. Na prática, esse campo será preenchido com o ID de um documento da entidade relacionada, sendo este invisível para o usuário.
 
-Por exemplo, digamos que você tem uma entidade Clientes e outra Lista de Compras, e quer que cada cliente possa ter várias listas de compras. Basta criar um campo na entidade Lista de Compras para informar a qual cliente ela pertence. 
+Por exemplo, sua loja tem uma entidade **Clientes** e outra **Lista de Compras**, e você quer que cada cliente possa ter várias listas de compras. Para isso, é necessário criar um campo na entidade **Lista de Compras** para informar a qual cliente ela pertence. 
 
-Se você é familiarizado com SQL, pode pensar em um relacionamento como uma [foreign key](https://www.sqltutorial.org/sql-foreign-key/).
+<div class="alert alert-info">
+<p>O Master Data já possui por padrão alguns relacionamentos pré-definidos, como os de Cliente (CL) e Endereço (AD).</p>
+</div>
 
-O Master Data já possui por padrão alguns relacionamentos pré-definidos, como os de Cliente (CL) e Endereço (AD). 
+## Criar um relacionamento entre entidades de dados
 
-## Como criar um relacionamento entre entidades?
-Para criar um relacionamento, primeiro são necessárias duas entidades. Para saber como criá-las, consulte o guia [Criar entidade de dados](https://help.vtex.com/pt/tutorial/creating-data-entity--tutorials_1265). Também será necessário criar pelo menos um campo em uma entidade de dados e adicioná-lo ao formulário, o que pode ser visto no artigo [Criar um campo no Master Data](https://help.vtex.com/pt/tutorial/how-can-i-create-a-field-in-master-data--frequentlyAskedQuestions_1829).
+Para criar um relacionamento, é necessário ter duas entidades de dados. Se só tiver uma, você poderá criar outra durante o passo a passo a seguir. Para mais informações sobre entidades de dados, consulte o guia [Entidade de dados](https://help.vtex.com/pt/tutorial/entidade-de-dados--tutorials_1265).
 
-Neste exemplo, é criada uma entidade chamada `Lista de Compras` que se relacionará com a entidade `Cliente`. Esse relacionamento permitirá que um cliente possa ter várias listas de compras, porém uma lista de compras só pode pertencer a um único cliente.
+No exemplo citado na introdução, é necessário criar uma entidade de dados chamada **Lista de Compras** que se relacionará com a entidade **Cliente**. Esse relacionamento permitirá que um cliente possa ter várias listas de compras, porém uma lista de compras só pode pertencer a um único cliente.
 
-1. No Master Data, clique na aba **Aplicações**.
-2. Depois, clique no botão **Advanced settings** (Configurações avançadas).  
-![Configurações Avançadas](https://images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
-3. Selecione a opção **Estrutura de dados**. Isso abrirá uma nova aba para o Dynamic Storage (DS).  
-![Estrutura de dados](https://images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
-4. No Dynamic Storage, clique na aba **Data Entities** (Entidades de dados).
-5. Se deseja criar um relacionamento em uma nova entidade, clique no botão **Add new** (Adicionar nova) para criar uma nova entidade de dados. _Caso queira criar um relacionamento em uma entidade existente, localize-a e clique no botão **Edit** (Editar), e siga para o passo 7_.  
-![Adicionar nova entidade de dados](https://images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
-![Editar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
-6. Configure a entidade que será criada preenchendo os campos **Acronym** (Acrônimo) e **Name** (Nome) e adicionando os campos desejados. Neste exemplo, a entidade utilizará o nome `Lista de compras`, o acrônimo `LC` e o campo `compras` de tipo `Varchar 750`.
-7. Adicione um campo de tipo `Relationship` (Relacionamento) e defina seu nome. Neste exemplo, ele será chamado de `Cliente`.
-8. Então, clique no botão **Edit** (Editar, no ícone de engrenagem) do campo de relacionamento para configurá-lo.
-9. Na configuração **Custom field type settings** (Configurações de tipo de campo personalizado), selecione a entidade à qual se deseja fazer referência e o campo que será mostrado no relacionamento. Neste exemplo, o relacionamento será feito com a entidade "Cliente" e será exibido o campo "email".  
-![Relacionamento entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
-10. Clique no botão **Save**  (Salvar) para salvar as configurações.
-![Salvar entidade de dados](https://images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
-11. Volte para a lista de entidades. Lembre-se que a entidade com o relacionamento deve ser publicada clicando em seu botão **Publish** (Publicar, no ícone de disquete). Também pode ser necessário atualizar as aplicações para que sejam implementadas as modificações. Para isso, vá em **Aplicações** e clique no botão **Reload applications** (Recarregar aplicações).  
-![Publicar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png) 
+Confira o passo a passo a seguir, ilustrado com esse exemplo:
 
-![Master Data Reload applications](https://images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Clique em `Configurações avançadas`.  
+3. Clique em **Estrutura de dados**. Você será direcionado(a) a uma nova aba.
+4. Clique na aba **Entidades de dados**.
+5. Se deseja criar um relacionamento em uma nova entidade, clique no botão `Adicionar` para criar uma nova entidade de dados.
 
-## Como criar um relacionamento entre documentos?
+   Caso queira criar um relacionamento em uma entidade existente, localize-a e clique no botão de edição <i class="fas fa-edit"></i>, depois siga para o passo 7.  
 
-Os relacionamentos também podem ser aplicados a documentos específicos das entidades de dados. A entidade de relacionamento `Lista de Compras` será utilizada novamente como exemplo e também será considerado que alguns documentos foram criados nela. Além disso, será necessário modificar o formulário de uma entidade de dados, o que pode ser visto no artigo [Criar um campo no Master Data](https://help.vtex.com/pt/tutorial/como-crio-um-campo-no-master-data--frequentlyAskedQuestions_1829).
+6. Configure a entidade que será criada preenchendo os campos **Acrônimo** e **Nome** e adicionando os campos desejados. Saiba mais sobre campos no guia [Criar um campo no Master Data](https://help.vtex.com/pt/tutorial/como-crio-um-campo-no-master-data--frequentlyAskedQuestions_1829).
 
-1. Para relacionar os documentos, adicione o campo de relacionamento ao formulário da entidade que contém a referência. Para facilitar, você pode definir o campo como uma combo box para mostrar todos os valores disponíveis. Mais detalhes podem ser vistos no artigo [Criar um campo no Master Data](https://help.vtex.com/pt/tutorial/como-crio-um-campo-no-master-data--frequentlyAskedQuestions_1829#crm).
-2. Selecione o valor desejado (neste caso, o cliente que irá se relacionar com a lista de compras).
-![Selecionar relacionamento de documento Master Data](https://images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
-3. Clique em **Salvar**.
+   Neste exemplo, a entidade utilizará o nome `Lista de compras`, o acrônimo `LC` e, inicialmente, o campo `compras` de tipo `Varchar 750`.
 
-Ao adicionar o campo na tabela, observe os valores que foram definidos. 
-![Tabela de relacionamento de documentos Master Data](https://images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/5658949f4c0a72a5ed7bdd9af7819896/Tabela_de_relacionamento_de_documentos_Master_Data.png)
+   Para mais detalhes sobre o preenchimento, consulte o guia [Entidade de dados](https://help.vtex.com/pt/tutorial/entidade-de-dados--tutorials_1265). 
+7. Adicione um campo de tipo **Relacionamento** e defina seu nome. Neste exemplo, ele será chamado de `Cliente`.
+8. Clique no ícone de engrenagem <i class="fas fa-cog"></i> ao lado do campo de **Relacionamento** para configurá-lo.
+9. Em **Configurações de campo personalizado**, selecione a entidade à qual deseja fazer referência e o campo que será mostrado no relacionamento. Neste exemplo, o relacionamento será feito com a entidade **Cliente** e será exibido o campo **email**.
 
-## Como adicionar filtros aos campos de relacionamento?
+   ![Relacionamento entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
+
+10. Clique no botão `Salvar` para salvar as configurações.
+11. Clique no ícone de publicação <i class="fas fa-save"></i> para publicar a entidade.
+12. Também pode ser necessário atualizar as aplicações para que sejam implementadas as modificações. Para isso, vá em **Configurações da loja** > **Storefront** > **Master Data** e clique no botão `Recarregar aplicações`.
+
+## Criar um relacionamento entre documentos
+
+Os relacionamentos também podem ser aplicados a documentos, uma vez que houver um [relacionamento entre entidades de dados](#criar-um-relacionamento-entre-entidades-de-dados). Para isso, será necessário modificar o [formulário](https://help.vtex.com/pt/tutorial/criando-formulario-no-master-data--tutorials_1047) de uma entidade de dados.
+
+Confira o passo a passo a seguir:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Clique no ícone de engrenagem <i class="fas fa-cog"></i> ao lado do nome da aplicação.
+
+   Você será direcionado(a) para a listagem de formulários existentes nessa aplicação.
+3. Para criar um novo formulário, clique em `+ Novo`.
+4. Preencha o **Nome** do formulário.
+5. Selecione a **Entidade de dados** à qual o formulário será vinculado. Neste passo a passo, vamos utilizar a entidade Lista de Compras como exemplo.
+
+   Os campos da entidade serão exibidos em uma listagem na aba **Campos da lista** e podem ser selecionados para compor o formulário.
+6. Selecione o campo de relacionamento e quaisquer outros que desejar incluir no formulário. Seguindo o exemplo, vamos incluir o campo **Cliente** (relacionamento) e os campos **ID do documento** e **Compras**.
+7. Clique na aba **Esquemas de layout** para configurar o layout do formulário.
+8. Clique em `Adicionar nova seção` para criar uma seção no formulário.
+9. Nomeie a seção.
+10. Arraste o campo de relacionamento (nesse caso, **Cliente**) para a seção e os demais campos que desejar incluir no formulário.
+11. Clique em `Salvar`. Você será conduzido(a) para a listagem de formulários da aplicação, incluindo o novo formulário.
+12. Na linha do novo formulário, clique no ícone de edição <i class="fas fa-edit"></i>.
+13. Clique na aba **Esquemas de layout*.
+14. Ao lado do campo de relacionamento (no exemplo, **Cliente**) clique no ícone de edição <i class="fas fa-edit"></i>.
+15. Selecione a opção **Caixa de combinação** e clique em `OK`. Essa opção fará com que seja possível selecionar valores existentes do campo armazenados na entidade relacionada ao preencher o formulário.
+16. Clique em `Salvar`.
+17. Clique na aba **Aplicações**.
+18. Clique no botão `Recarregar aplicações`.
+
+Agora, ao criar um novo documento a partir do formulário, você pode selecionar o valor desejado (neste exemplo, o Cliente preexistente que irá se relacionar com a Lista de Compras):
+
+![Selecionar relacionamento de documento Master Data](//images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
+
+Além do relacionamento, é possível também visualizar os registros relacionados ao visualizar cada registro de uma entidade, por exemplo, visualizar as ‘Lista de compras’ criadas por um ‘Cliente’ ao consultar o registro do cliente.
+
+Para isso, você precisa adicionar ao formulário da entidade o valor `{acronimo_da_entidade_relacionada}.{nome_campo_relacionamento}` no campo **Consultas de visualização**. Exemplo de preenchimento: `LC.cliente`.
+
+## Adicionar filtros aos campos de relacionamento
 
 Os relacionamentos são mantidos através dos IDs dos documentos. Então, ao tentar inserir o valor do campo de relacionamento como filtro no formulário, obteremos apenas os valores dos IDs dos documentos referidos, e não os valores do campo escolhido para cada documento. As duas figuras abaixo mostram esse resultado. Veja mais informações no artigo [Filtrar dados no Master Data](https://help.vtex.com/pt/tutorial/filtrando-dados-no-master-data--tutorials_778).
 
-![Selecionar filtro relacionamento](https://images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
-
-![Filtro relacionamento ID](https://images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
-
-Caso queira ver os valores dos campos, e não seus IDs, a filtragem pode ser feita com um campo automático. Para isso:
-
-1. No Master Data, vá em **Aplicações** > **Advanced settings** (Configurações avançadas) > **Estrutura de dados** para acessar o Dynamic Storage.
-2. Depois, para ver as entidades de dados, selecione **Data Entities** (Entidades de dados).
-3. Na entidade que contém o relacionamento (neste caso é `Lista de Compras`), clique no botão **Editar**.  
-![Editar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/01edd05338b039279672d9cfc4a49164/Editar_entidade_Lista_de_Compras.png)
-4. Selecione a aba **Automatic fields** (Campos automáticos).
-5. Clique no botão **New Calculated Field** (Novo campo calculado).  
-![Relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
-6. Preencha os campos **Name** (Nome), **Display Name** (Nome de exibição) e **Type** (Tipo) conforme desejado. Neste exemplo, serão utilizados `emailCliente`, `E-mail cliente` e Varchar 50.
-7. Clique no ícone de engrenagem para inserir configurações adicionais.  
-![Nome automatic field](https://images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/c2c03a8312fecf60f203fca29aca8d3c/Nome_automatic_field.png)
-8. Insira as configurações desejadas e use a fórmula para escolher o campo da entidade relacionada que se deseja mostrar no filtro. Neste exemplo, será utilizado o email do cliente.
-![Configurar relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/8605aa25dbc22ba6d28674472fc80232/Configurar_relacionamento_automatic_fields.png)
-9. Clique no botão **Validate** (Validar).
-10. Na janela que abrirá, insira um email genérico e clique em **Ok**.  
-![Validar automatic field](https://images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/4855b244c37edd42b9c65398153b93a0/Validar_automatic_field.png)
-11. Em seguida, aparecerá um aviso indicando que a fórmula é válida, como mostrado na imagem abaixo. Clique em **Ok**.  
-![Fórmula válida automatic field](https://images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/2c91fa6856ae00b4ae824b25216a6a46/F__rmula_v__lida_automatic_field.png)
-12. Clique em **Save** (Salvar) para salvar as configurações.
-
-Depois de realizar os passos acima, o filtro será aplicado ao relacionamento. No formulário da entidade (`Lista de Compras`), adicione esse novo campo ao filtro após atualizar os registros.
-![Selecionar filtro relacionamento valor](https://images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/731c3fa19a7a8c3d9cf91a3733d86c7c/Selecionar_filtro_relacionamento_valor.png)
-
-Dessa forma, podemos ver o filtro com os valores no lugar dos IDs.
-![Filtro relacionamento valor](https://images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/5c63307856159af60995094fa6e99f42/Filtro_relacionamento_valor.png)
+![Selecionar filtro relacionamento](//images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
 
+![Filtro relacionamento ID](//images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
diff --git a/docs/tutorials/pt/creating-roles.md b/docs/tutorials/pt/creating-roles.md
new file mode 100644
index 000000000..2042365a1
--- /dev/null
+++ b/docs/tutorials/pt/creating-roles.md
@@ -0,0 +1,101 @@
+---
+title: 'Criar perfil de acesso'
+id: qGtNQpKSSAduX94l2WZBW
+status: DRAFT
+createdAt: 2023-11-30T16:42:01.373Z
+updatedAt: 2023-11-30T21:59:23.416Z
+publishedAt: 
+firstPublishedAt: 2023-11-30T17:12:45.125Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: criar-perfil-de-acesso
+locale: pt
+legacySlug: criar-perfil-de-acesso
+subcategory: 1HSqkejwuYcQSMC400uY84
+---
+
+Os perfis de acesso determinam o conjunto de recursos que um grupo de usuários pode acessar na VTEX. Você pode gerenciá-los por meio do Admin VTEX, onde é possível definir os [recursos](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) e usuários associados a cada perfil.
+
+Ao criar um perfil de acesso, você pode optar por utilizar um perfil de acesso [predefinido](https://help.vtex.com/pt/tutorial/controle-de-acesso--4rM3gyiWqtkim4Q8hOvLTC#predefinido), criado pela equipe da VTEX para atender a cenários comuns nas operações, ou por cadastrar um perfil de acesso [personalizado](https://help.vtex.com/pt/tutorial/controle-de-acesso--4rM3gyiWqtkim4Q8hOvLTC#personalizado), selecionando recursos específicos a que usuários com o perfil precisam ter acesso.
+
+Confira a seguir o passo a passo para cada uma dessas opções:
+
+* [Utilizar perfil de acesso predefinido](#utilizar-perfil-de-acesso-predefinido)
+* [Criar perfil de acesso personalizado](#criar-perfil-de-acesso-personalizado)
+
+Recomendamos a criação de perfis que sejam análogos às estruturas hierárquicas da loja. Desta forma, todos os colaboradores são responsáveis pelas informações a que podem ter acesso. Boas práticas de gerenciamento dos perfis de acesso aumentam a segurança de uma operação, além de se reforçar a atenção de todos os envolvidos com dados sensíveis de uma loja e de seus clientes. 
+
+<div class="alert alert-warning">
+  <p>O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas caso ocorra o vazamento de credenciais de login.</p>
+</div>
+
+## Utilizar perfil de acesso predefinido
+
+Para começar a utilizar um perfil de acesso predefinido, siga as instruções abaixo:
+
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Perfis de acesso**.
+
+    Você verá uma lista com todos os perfis de acesso cadastrados para a conta. Para mais informações sobre essa página, acesse o artigo [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
+
+2. Clique em `+ Criar perfil de acesso`.
+3. Clique em `Escolher perfil de acesso` e clique em um dos perfis predefinidos exibidos no menu dropdown. Não escolha a opção **Custom**, pois ela é dedicada a perfis personalizados.
+
+    Você verá quais são os recursos incluídos nesse perfil, separados por produto.
+
+    Por exemplo, o perfil **Call center operator** contém um recurso do produto _Catálogo_ que permite executar operações numa loja em nome de um cliente e um recurso do _OMS_ que permite checar o status de um pedido:
+
+    ![Novo perfil de acesso](//images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/1fe552a5c15c7c3dee8d54c88a60fafc/image_3.png)
+
+    Saiba mais sobre os perfis predefinidos disponíveis e os recursos associados em [Perfis de acesso predefinidos](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy).
+
+4. Adicione usuários administrativos ao perfil de acesso, preenchendo o email do usuário a ser inserido em **Adicionar usuários para este perfil de acesso** e clicando em `Adicionar`.
+
+    ![Usuários do perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/59aaf0ef06ddcb1a4b48c47647d68f2d/usuarios-es.PNG)
+
+    Se o usuário não existir, será criado um novo usuário usando o email como nome, ou seja, nome e email serão iguais.
+
+5. Clique em `Salvar`.
+
+## Criar perfil de acesso personalizado
+
+Para criar  um perfil de acesso personalizado para atender as necessidades de acesso de um grupo de usuários, siga as instruções abaixo:
+
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Perfis de acesso**.
+
+    Você verá uma lista com todos os perfis de acesso cadastrados para a conta. Para mais informações sobre essa página, acesse o artigo [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
+
+2. Clique em `+ Criar perfil de acesso`.
+3.  Para criar um perfil personalizado, clique em `Escolher perfil de acesso` e clique na opção **Custom** no menu dropdown.
+4. Clique no menu dropdown em **Escolha um produto** e, em seguida, clique em um produto exibido na lista.
+
+    Você verá a lista de todos os recursos disponíveis para o produto:
+
+    ![Configurando produto](//images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/39bc16eca81b8a13946f081c5a1454d3/image_4.png)
+
+5. Marque os recursos aos quais o perfil deve conceder acesso. Confira a lista completa de [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) para mais informações sobre cada um.
+6. Caso deseje adicionar recursos de outro produto, clique no botão **Configurar outro produto**, ao final da lista de produtos e recursos e repita os passos 4 e 5.
+
+    É possível adicionar recursos de quantos produtos forem necessários ao perfil.
+
+7. Escreva um nome para o perfil personalizado no campo **Nome do perfil**.
+
+  <div class="alert alert-warning">
+    <p>É importante escolher nomes descritivos para os perfis de acesso, deixando claro que tipo de usuário deve ter aquele acesso. Recomendamos indicar o cargo na empresa ou atividade a ser desempenhada na plataforma.</p>
+  </div>
+
+8. Adicione usuários administrativos ao perfil de acesso, preenchendo o email do usuário a ser inserido em **Adicionar usuários para este perfil de acesso** e clicando em `Adicionar`.
+
+    ![Usuários do perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/59aaf0ef06ddcb1a4b48c47647d68f2d/usuarios-es.PNG)
+
+    Se o usuário não existir, será criado um novo usuário usando o email como nome, ou seja, nome e email serão iguais.
+
+9. Clique em `Salvar`.
+
+    Após criado, o novo perfil será listado na página [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
+
+## Saiba mais
+
+* [Controle de acesso](https://help.vtex.com/pt/tutorial/controle-de-acesso--4rM3gyiWqtkim4Q8hOvLTC)
+* [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc)
+* [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3)
diff --git a/docs/tutorials/pt/creating-service-for-a-sku.md b/docs/tutorials/pt/creating-service-for-a-sku.md
index 69c3ae6ff..4a774310a 100644
--- a/docs/tutorials/pt/creating-service-for-a-sku.md
+++ b/docs/tutorials/pt/creating-service-for-a-sku.md
@@ -3,8 +3,8 @@ title: 'Criar serviço para um SKU'
 id: tutorials_252
 status: PUBLISHED
 createdAt: 2017-04-27T22:12:00.282Z
-updatedAt: 2023-05-04T13:15:14.224Z
-publishedAt: 2023-05-04T13:15:14.224Z
+updatedAt: 2024-03-04T22:36:04.117Z
+publishedAt: 2024-03-04T22:36:04.117Z
 firstPublishedAt: 2017-04-27T23:03:11.914Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -40,17 +40,10 @@ Para cadastrar um tipo de serviço, siga os passos abaixo:
 Nesta seção, você deve cadastrar um nome para seu tipo de serviço e configurar o comportamento conforme as opções abaixo.
 
 - **Nome:** nome do tipo de serviço.
-- **Exibe no Produto:** opção que exibe o tipo de serviço na página do produto.
-- **Exibe no Carrinho:** opção que exibe o tipo de serviço no carrinho.
-- **Exibe no Serviço:** opção que exibe o tipo de serviço na página de serviços.
 - **Cartão Presente:** opção que exibe o tipo de serviço no cartão presente.
 - **Serviço Obrigatório:** opção que torna o tipo de serviço obrigatório.
 - **Status:** opção que ativa ou desativa o tipo de serviço.
-- **Anexos:** seleção de anexos que serão adicionados no tipo de serviço. O anexo é utilizado para adicionar a informação personalizada do serviço. Para saber mais sobre anexos, leia nosso artigo O que é um Anexo?.
-
-<div class = "alert alert-warning">
-  <p>Para exibir o serviço na tela do produto é necessário habilitar  a opção   <b>Exibe o serviço na tela do produto</b> e adicionar o controle <code><vtex.cmc:stockKeepingUnitService/></code> na página do produto no CMS. Para mais informações sobre controles, leia nosso artigo <a href ="https://help.vtex.com/pt/tutorial/o-que-sao-controles--6e2qsk9zu8IQuyEysKweag" >O que são controles?</a></p> 
-</div>
+- **Anexos:** seleção de anexos que serão adicionados no tipo de serviço. O anexo é utilizado para adicionar a informação personalizada do serviço. Para saber mais sobre anexos, leia nosso artigo [O que é um Anexo?](https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete).
 
 ## Criar um valor de serviço e associar a um tipo de serviço
 Após cadastrar o tipo de serviço, é necessário atribuir um valor a ele. Para cadastrar o valor de um tipo de serviço, siga os passos abaixo:
@@ -87,7 +80,7 @@ Para vincular um serviço a um SKU, siga os passos abaixo:
   <p>O tamanho do arquivo da planilha não poderá exceder 4Mb (4096KB).</p>
 </div>
 8. Clique na barra ao lado do botão `Select`, destacada abaixo.
-  ![Anexos - PT](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/8581377e9a02b411cd383a85be145983/image.png)
+  ![Anexos - PT](//images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/8581377e9a02b411cd383a85be145983/image.png)
 9. Selecione a planilha CSV atualizada.
 10. Clique em `Vincular Valor(es) de Serviço(s) a SKU(s)` para finalizar.
 
diff --git a/docs/tutorials/pt/creating-subaccount-multi-store-multi-domain.md b/docs/tutorials/pt/creating-subaccount-multi-store-multi-domain.md
new file mode 100644
index 000000000..b2727963d
--- /dev/null
+++ b/docs/tutorials/pt/creating-subaccount-multi-store-multi-domain.md
@@ -0,0 +1,66 @@
+---
+title: 'Criar subconta / multiloja / multidomínio'
+id: tutorials_510
+status: PUBLISHED
+createdAt: 2017-04-27T22:03:17.733Z
+updatedAt: 2024-01-18T17:56:47.931Z
+publishedAt: 2024-01-18T17:56:47.931Z
+firstPublishedAt: 2017-04-27T23:03:27.832Z
+contentType: tutorial
+productTeam: Others
+author: authors_84
+slug: criar-subconta-multiloja-multidominio
+locale: pt
+legacySlug: como-criar-multiloja-multidominio
+subcategory: yMp6sKDiJEi66CGAIQ4ma
+---
+
+Subconta, multiloja ou multidomínio é uma segunda loja administrada dentro de um mesmo painel administrativo VTEX. Esse recurso geralmente é utilizado quando a loja tem outras marcas mas existe uma similaridade de logística e métodos de pagamento ou quando a loja precisa de outro ambiente, por exemplo para vendas B2B.
+
+A criação de multiloja é sem custos para o lojista. Porém, caso seja necessário [contratar uma política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), custos adicionais serão aplicados.
+
+Em um ambiente multidomínio é possível definir layouts distintos (além de produtos e/ou preços) para cada loja, variando de acordo com o domínio acessado. Exemplo: `accountname.com.br` e `b2baccountname.com.br`.
+
+## Configurar nova loja no Gerenciamento da conta
+
+O primeiro passo na configuração da multiloja é configurar uma nova loja na página de detalhes da conta. Saiba como fazer isso [na seção Criar loja do guia Gerenciamento de conta](https://help.vtex.com/pt/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq#criar-loja).
+
+Note que você também precisa especificar qual é o domínio da sua nova loja. Saiba mais com o guia [Configurando o domínio da sua loja](https://help.vtex.com/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450).
+
+## Configurar website no CMS - Portal Legado
+
+A configuração no CMS - Portal Legado irá de fato criar o ambiente que poderá ser acessado pelos clientes. O passo a passo abaixo demonstra como criar um website já copiando a estrutura de pastas do seu website principal, visando facilitar a criação de seu layout. Porém, essa configuração também pode ser feita criando um website novo.
+
+1. No Admin VTEX, acesse o módulo **Storefront > Layout**.
+2. Clique em **CMS**.
+3. Clique em **Sites and channels**.
+4. Clique em seu website principal.
+5. Clique no botão `Copiar Website`.
+6. Clique novamente em **Sites and channels**, na coluna lateral.
+7. Clique sobre o website criado.
+8. Altere o nome.
+9. Clique no botão `Salvar Website`.
+10. Na mesma tela, clique no botão `Adicionar`.
+11. Preencha o campo **Store name from License Manager** com o valor da loja criado no passo anterior no Gerenciamento da conta.
+12. Preencha o campo **Políticas comerciais disponíveis** selecionando as políticas comerciais que irá associar a esta loja.
+13. Clique no botão `Salvar Binding`.
+14. Clique no botão `Salvar Website`.
+
+Atente-se à ordenação de suas políticas comerciais. Elas sempre devem ser ordenadas de acordo com seu uso em websites, ou seja, primeiro as políticas comerciais que são usadas por websites (principal, b2b etc.) e depois as políticas comerciais que não estão associadas a nenhum website (políticas comerciais de marketplace, por exemplo). 
+
+Isto porque se existir uma política comercial não associada a nenhum website, ela está disponível a todos eles. E caso ela venha antes da política comercial associada ao website, este assumirá a política comercial incorreta. 
+
+Para saber mais detalhes sobre a relação entre websites e políticas comerciais, acesse [Como funciona a relação entre websites e políticas comerciais
+](https://help.vtex.com/pt/tutorial/como-funciona-a-relacao-entre-websites-e-politicas-comerciais--1VuakBcyNOgg4AM4cUeeQg).
+
+### Editar o dicionário
+
+Também é possível definir variáveis específicas para cada website utilizando o dicionário. Para isso, dentro do website, clique em **dicionário**.
+
+## Excluir subconta / multiloja / multidomínio
+
+Para excluir uma multiloja existente, siga os passos descritos [na seção Excluir loja do guia Gerenciamento de conta](https://help.vtex.com/pt/tutorial/account-details-page--2vhUVOKfCaswqLguT2F9xq#excluir-loja). O nome da subconta removida não poderá ser utilizado novamente.
+
+## Saiba mais
+
+- [Escolhendo entre arquitetura multi-loja ou ambiente adicional](https://help.vtex.com/pt/tutorial/escolhendo-entre-arquitetura-multi-loja-ou-ambiente-adicional--4HRNpa1OCKZ5YzP8yiilBL)
diff --git a/docs/tutorials/pt/creating-surchargestaxes.md b/docs/tutorials/pt/creating-surchargestaxes.md
index 5247a513a..deb52d66c 100644
--- a/docs/tutorials/pt/creating-surchargestaxes.md
+++ b/docs/tutorials/pt/creating-surchargestaxes.md
@@ -3,8 +3,8 @@ title: 'Criar taxa/imposto'
 id: tutorials_321
 status: PUBLISHED
 createdAt: 2017-04-27T22:08:49.745Z
-updatedAt: 2023-03-31T16:53:05.461Z
-publishedAt: 2023-03-31T16:53:05.461Z
+updatedAt: 2023-10-26T13:20:22.531Z
+publishedAt: 2023-10-26T13:20:22.531Z
 firstPublishedAt: 2017-04-27T23:03:14.603Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 Taxa é o contrário de promoção, ou seja, é um adicional percentual inserido no preço do produto, visando aumentar o valor. A taxa pode ser configurada considerando diversos tipos de condições, como faixa de CEP, departamento e marca dos produtos, cluster de cliente etc. A taxa é inserida somente no carrinho, na área denominada **Imposto**.
 
-A taxa é aplicada conforme o cadastro que é feito no seller. Então se no carrinho da sua loja tem um produto de outro seller, a taxa a ser aplicada nesse produto, será aquela que estiver cadastrada no admin do seller que é o dono do produto. Não será considerada a taxa cadastrada no módulo de Pricing do marketplace, ainda que essa taxa esteja associada a esse produto.
+A taxa é aplicada conforme o cadastro que é feito no seller. Então se no carrinho da sua loja tem um produto de outro seller, a taxa a ser aplicada a esse produto, será aquela que estiver cadastrada no Admin do seller dono do produto. Não será considerada a taxa cadastrada no módulo de Preço do marketplace, ainda que essa taxa esteja associada a esse produto.
 
 ## Como criar
 
@@ -30,31 +30,33 @@ A taxa é aplicada conforme o cadastro que é feito no seller. Então se no car
 
 ### Quais os dados gerais desta taxa?
 
-- **Nome**: Nome da taxa.
-- **Status**: Ativa ou Inativa a taxa.
-- **Descrição**: Descrição interna da taxa. O objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a taxa é devido à alguma regra especial, por exemplo.
-- **Validade**: Data e hora de início e de fim da taxa. Pode ser usada uma data e/ou horário futuros, para que a taxa comece a ser aplicada no site. Caso seja configurada dessa forma, a taxa terá o status de agendada até que a data e horário sejam atingidos. Enquanto a taxa estiver válida, esta terá o status de ativa e ao término da data e hora definidos, o status será alterado para inativo automaticamente.
+- **Nome**: nome da taxa.
+- **Status**: ativa ou Inativa a taxa.
+- **Descrição**: descrição interna da taxa. O objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a taxa é devido a alguma regra especial, por exemplo.
+- **Validade**: data e hora de início e de fim da taxa. Pode ser usada uma data e/ou horário futuros, para que a taxa comece a ser aplicada no site. Caso seja configurada dessa forma, a taxa terá o status de agendada até que a data e horário sejam atingidos. Enquanto a taxa estiver válida, esta terá o status de ativa e ao término da data e hora definidos, o status será alterado para inativo automaticamente.
 - **Qual o tipo e valor da Taxa?**:
-  - **Taxa Percentual**: Percentual sobre o valor do produto que será adicionado ao valor.
-  - **Taxa com base em fórmula**: Taxa seguirá o cálculo inserido no campo.
-  - **Taxa percentual sobre frete**: Acréscimo percentual em cima do valor do frete.
-- **Política Comercial**: Selecione as políticas comerciais onde a taxa será aplicada.
+  - **Taxa Percentual**: percentual sobre o valor do produto que será adicionado ao valor dele.
+  - **Taxa com base em fórmula**: esta taxa seguirá o cálculo inserido no campo.
+  - **Taxa percentual sobre frete**: acréscimo percentual em cima do valor do frete.
+  - **Taxa Nominal**: imposto adicional com valor predefinido.
 
-### Em quais itens esta taxa será aplicada?
+- **Política comercial**: selecione as políticas comerciais às quais a taxa será aplicada.
 
-- **Categorias, Marcas, Coleções e Produtos**: Deve atender a todas as condições cadastradas. Ex.: se for cadastrada uma categoria e uma marca, o produto deve atender a essas duas condições.
+### A quais itens esta taxa será aplicada?
+
+- **Categorias, Marcas, Coleções e Produtos**: deve atender a todas as condições cadastradas. Ex.: se for cadastrada uma categoria e uma marca, o produto deve atender a essas duas condições.
 
 ### Quais as condições para a taxa ser válida?
 
-- **Valor acumulado em compras**: A taxa será aplicada caso o total de todas as compras já realizadas pelo cliente esteja atendendo ao valor preenchido.
-- **Marketing Tags**: Campo utilizado para restringir a ativação da campanha caso a compra seja realizada pelo Sistema de Recorrência da VTEX. 
-- **Afiliados**: Identificador de pedidos do marketplace
-- **Cluster de clientes**: A taxa será aplicada caso o cliente esteja cadastrado no cluster selecionado.
-- **O CEP de entrega deve**: A taxa será aplicada caso o CEP esteja atendendo à regra configurada.
-- **Tipo de frete**: A taxa será aplicada caso o tipo de frete for o mesmo que o cadastrado.
+- **Valor acumulado em compras**: a taxa será aplicada caso o total de todas as compras já realizadas pelo cliente esteja atendendo ao valor preenchido.
+- **Marketing Tags**: campo utilizado para restringir a ativação da campanha caso a compra seja realizada pelo sistema de recorrência da VTEX.
+- **Afiliados**: identificador de pedidos do marketplace.
+- **Cluster de clientes**: a taxa será aplicada caso o cliente esteja cadastrado no cluster selecionado.
+- **O CEP de entrega deve**: a taxa será aplicada caso o CEP esteja atendendo à regra configurada.
+- **Tipo de frete**: a taxa será aplicada caso o tipo de frete for o mesmo que o cadastrado.
 
 ## Agendamento
 
 O agendamento de uma taxa ocorre quando é criada ou alterada com data e hora de validade com início posterior ao atual. Visualmente é possível identificar essas taxas na página principal do módulo de Taxas & Promoções, através de uma tarja laranja no canto superior direito do cartão da taxa, com a palavra agendada. Veja abaixo um exemplo de como fica o cartão de uma taxa quando agendada.
 
-![agendamento.pt](https://images.ctfassets.net/alneenqid6w5/79wklIdW9FLzJZb8e4rxc0/6214e94e10b4df0cc4b07b7cc81e52f9/agendamento.pt.png)
+![agendamento.pt](//images.ctfassets.net/alneenqid6w5/79wklIdW9FLzJZb8e4rxc0/6214e94e10b4df0cc4b07b7cc81e52f9/agendamento.pt.png)
diff --git a/docs/tutorials/pt/creating-synonyms.md b/docs/tutorials/pt/creating-synonyms.md
new file mode 100644
index 000000000..b5874aa8c
--- /dev/null
+++ b/docs/tutorials/pt/creating-synonyms.md
@@ -0,0 +1,95 @@
+---
+title: 'Criar sinônimos'
+id: 5IfjhvjxNAvJGEWNn0AhOA
+status: PUBLISHED
+createdAt: 2024-06-27T16:36:30.904Z
+updatedAt: 2024-06-27T16:39:00.981Z
+publishedAt: 2024-06-27T16:39:00.981Z
+firstPublishedAt: 2024-06-27T16:37:25.800Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: criar-sinonimos
+locale: pt
+legacySlug: configurar-sinonimos
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+<div class = "alert alert-info"> Para relacionar palavras ao produto, é recomendada a utilização da configuração de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV?&utm_source=autocomplete">Sinônimos</a> ao invés das <a href="https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palavras Substitutas</a>, uma vez que os sinônimos possibilitam uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.</div>
+
+Existem duas formas de configurar sinônimos no Admin VTEX: [individualmente](#criar-sinonimos-individualmente) ou por [importação de uma planilha em formato CSV](#importar-csv). Se você precisa cadastrar sinônimos em massa, recomendamos utilizar a planilha. Confira as instruções para cada forma de configuração nas seções a seguir.
+
+A configuração de sinônimos funciona de maneira recursiva. Isso significa que, ao adicionar um segundo sinônimo a outro já existente, ele também se tornará sinônimo do primeiro. 
+
+<div class="alert alert-info" role="alert">
+<p>Sinônimos não devem ser utilizados para resolver erros de grafia, de plural e singular ou mesmo de pronomes, de artigos e de proposições nos termos pesquisados. Em todos estes pontos, o VTEX Intelligent Search é capaz de interpretar, aprender e resolver automaticamente por meio de algoritmos.</p>
+</div>
+
+## Criar sinônimos individualmente
+
+Siga o passo a passo para configurar sinônimos individualmente no Admin VTEX:
+
+1. No Admin VTEX, acesse __Storefront__, ou digite __Storefront__ na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Sinônimos**.
+3. Clique em `Novo`.
+4. Preencha os campos referentes ao sinônimo:
+   - __Tipo:__ define o tipo de sinônimo. Confira [Tipos de sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) para mais informações.
+   - __Termos:__ palavras ou expressões a serem definidas como sinônimos. É necessário teclar `Enter` após cada termo para inserir um outro termo.
+   - **Idiomas:** idiomas aos quais o sinônimo será aplicado. Campo disponível apenas para lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO).
+   - __Status:__ define se o sinônimo estará ativo ou inativo.
+5. Para finalizar, clique em `Salvar`.
+
+A alteração pode demorar até duas horas para ser aplicada.
+
+<div class = "alert alert-info">
+  <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
+</div>
+
+## Importar CSV
+
+Caso existam muitos sinônimos a serem cadastrados, você pode fazer um arquivo .csv e depois importá-lo no Admin VTEX. 
+
+Para importar sinônimos por planilha, siga os passos abaixo:
+
+1. Crie um arquivo CSV no formato indicado em [Template da planilha de sinônimos](#template-da-planilha-de-sinonimos).
+2. No Admin VTEX, acesse __Storefront__, ou digite __Storefront__ na barra de busca no topo da página.
+3. Em **Intelligent Search**, clique em **Sinônimos**.
+4. Clique em <i class="fas fa-download"></i> `Importar`.
+5. Arraste o arquivo CSV para a área delimitada ou clique em `escolha um arquivo` para selecionar o arquivo no seu dispositivo.
+6. Clique em `Importar`.
+
+### Template da planilha de sinônimos
+
+O arquivo deve conter o seguinte formato, de acordo com os [tipos de sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos) escolhidos:
+
+ - **Unidirecional**: `{termos separados por vírgula};{termo equivalente};{status}`
+
+   __Exemplos:__
+
+    - `smartphone;iphone;true`: ao pesquisar por `smartphone`, os resultados para `iphone` serão exibidos. Contudo, ao pesquisar por `iphone`, os resultados para `smartphone` não serão exibidos.
+    - `tablet;ipad;true`: ao pesquisar por `tablet`, os resultados para `ipad` serão exibidos. Contudo, ao pesquisar por `ipad`, os resultados para `tablet` não serão exibidos.
+
+ - **Bidirecional**: `{termos separados por vírgula};{status}`
+
+   __Exemplos:__
+
+    - `tv,televisão,televisor;true`: ao pesquisar por qualquer um dos termos, qualquer produto que contenha um deles será exibido.
+    - `monitor,tela,display;true`: ao pesquisar por qualquer um dos termos, qualquer produto que contenha um deles será exibido.
+
+#### Lojas Multi-idioma (Beta)
+
+Lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO) devem seguir o template abaixo para fazer a importação de Sinônimos para idiomas específicos.
+
+- __Unidirecional__: `{termos separados por vírgula};{termo equivalente};{status};{locales separados por vírgula}`
+
+   __Exemplo:__
+   - `smartphone;iphone;true;en-GB`: ao pesquisar por `smartphone` na loja no idioma inglês (`locale = en-GB`), os resultados para `iphone` irão aparecer. Contudo, ao pesquisar por `iphone`, os resultados para `smartphone` não irão aparecer.
+
+- __Bidirecional__: `{termos separados por vírgula};{status};{locales separados por vírgula}`
+
+     __Exemplo:__
+     - `tv,smart tv;true;en-GB`: ao pesquisar por qualquer um dos termos na loja no idioma inglês (`locale = en-GB`), qualquer produto que contenha um desses termos irá aparecer nos resultados da busca.
+
+<div class="alert alert-warning">
+<p> Se o arquivo CSV importado não apresentar o <code>locale</code>, o sinônimo será válido para todos os idiomas disponíveis na loja.</p>
+</div>
diff --git a/docs/tutorials/pt/creating-trigger-in-master-data.md b/docs/tutorials/pt/creating-trigger-in-master-data.md
index 1c851e6bd..9741aa5f4 100644
--- a/docs/tutorials/pt/creating-trigger-in-master-data.md
+++ b/docs/tutorials/pt/creating-trigger-in-master-data.md
@@ -3,8 +3,8 @@ title: 'Criar trigger no Master Data v1'
 id: tutorials_1270
 status: PUBLISHED
 createdAt: 2017-04-27T21:56:49.666Z
-updatedAt: 2022-12-14T18:27:30.828Z
-publishedAt: 2022-12-14T18:27:30.828Z
+updatedAt: 2024-06-27T13:01:58.637Z
+publishedAt: 2024-06-27T13:01:58.637Z
 firstPublishedAt: 2017-04-27T23:03:50.015Z
 contentType: tutorial
 productTeam: Master Data
@@ -16,146 +16,158 @@ subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
 <div class="alert alert-info">
-Esse artigo se refere ao Master Data v1. Se você quiser utilizar o Master Data v2, veja os passos <a href="https://help.vtex.com/pt/tutorial/configurar-triggers--54eVOFGhS0EWyAUieoqKWo">deste artigo</a>.
+<p>Este artigo se refere ao Master Data v1. Se você quiser utilizar o Master Data v2, veja os passos do guia <a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2">Setting up triggers in Master Data v2</a>.</p>
 </div>
 
-Conceitualmente, **trigger** é um recurso de programação que executa determinada ação sempre que um evento associado ocorrer. No Master Data, um trigger é a configuração de um ou mais disparos (eventos) quando determinada situação ocorre. Essa situação é configurada com base em diversas variáveis.
+Conceitualmente, trigger é um recurso de programação que executa uma ação específica sempre que um evento associado ocorre. No Master Data, um trigger é a configuração de um ou mais disparos (eventos) que são acionados quando uma determinada situação ocorre, baseada em diversas variáveis.
 
-Isso possibilita diversas automatizações e controle de dados, aumentando a eficiência de seu gerenciamento de dados. Ou seja, de modo simples, trigger é uma funcionalidade que permite o agendamento de ações caso uma ação de disparo aconteça.
+Isso possibilita diversas automatizações e controle de dados, aumentando a eficiência de seu gerenciamento de dados. Simplificando, um trigger é uma funcionalidade que permite agendar ações a serem realizadas quando um evento disparador ocorre.
 
-1. Uma entidade de dados contém os dados de todas as suas lojas físicas
-2. Um novo registro é inserido nessa entidade
-3. Um trigger configurado envia para todos os clientes um e-mail contando a novidade
+Por exemplo:
 
-Imagine que são feitos agendamentos de determinadas ações para, quando uma condição for atendida, essas ações sejam realizadas. Então, qualquer informação cadastrada no MasterData pode ser uma ação que dispare outras inúmeras ações, de acordo com o que for desejado. O trigger possui algumas características importantes, descritas a seguir:
+1. Uma entidade de dados contém os dados de todas as suas lojas físicas.
+2. Um novo registro é inserido nessa entidade.
+3. Um trigger configurado envia para todos os clientes um email contando a novidade.
 
-- São associados a uma entidade de dados;
-- São chamados automaticamente;
-- Não podem ser chamados diretamente;
-- Dispara diversas ações;
-- Permite a criação de cenários de recursividade;
-- Pode impactar na manipulação de dados da entidade, devido à característica anterior.
+Os triggers permitem agendar ações para serem executadas quando certas condições são atendidas. Qualquer informação cadastrada no Master Data pode desencadear inúmeras outras ações, conforme desejado.
 
-A configuração se dá por 4 partes. Cada uma delas é detalhada abaixo:
+As principais características dos triggers são:
 
-1. Configuração da ação que vai disparar o trigger. Para isso, decida qual ação deve ser seguida por outra. E, essa configuração é separada em duas partes: a **condição** do trigger e os **filtros adicionais**. A condição é a ação que dispara o trigger, um cadastro por exemplo, enquanto os filtros são as especificações que aquela ação deve atender para a ação de resposta ser executada, como o cadastro ser feito pelo formulário de newsletter e não pela finalização de compra. Neste caso, a condição do trigger seria: “Sempre que um registro for inserido” e, nos filtros adicionais, existir um campo “origem” filtrando por “newsletter”. Assim, sempre que um novo cadastrado fosse realizado, o trigger verificaria se o cliente cadastrou-se pela newsletter e, somente neste caso, realizaria a ação configurada para este fim.
-2. Tempo para o disparo. É possível configurar vários envios separados por um intervalo de tempo. Ou, mais ainda, agendar o disparo de acordo com a data de outro campo. Exemplo: existe o campo “Data de Vencimento” no cadastro de uma entidade “Produto” e é desejado que, 1 mês antes dessa data, seja enviada uma notificação por API para outro sistema. Neste caso, o tempo de disparo será “Data de Vencimento” menos 1 mês.
+- São associados a uma entidade de dados.
+- São acionados automaticamente.
+- Não podem ser chamados diretamente.
+- Disparam diversas ações.
+- Permitem a criação de cenários de recursividade.
+- Podem impactar na manipulação de dados da entidade devido à característica anterior.
 
-Ações que serão executadas caso um registro atenda à condição do trigger e aos filtros. Aqui, são configuradas todas as ações que serão executadas quando o registro que atendeu as condições também atendeu aos filtros chegou na data definida no agendamento. Essas ações podem ser envio de e-mail, de comentário, alterar outro campo e outras possibilidades, detalhadas mais abaixo. Exemplo real:
+## Estrutura de um trigger
 
-- **Condição** - O atributo Checkout for alterado;
-- **Filtro adicional** - Checkout igual Finalizado;
-- **Ações em caso positivo** - Alterar o campo Bônus (tipo score), colocando a tag bônus com valor 10 e validade 30 dias.
+Antes de [criar um trigger](#configurar-um-trigger), é necessário compreender que a configuração de um trigger se dá por quatro partes, explicadas a seguir.
 
-Nesse caso, é um cenário onde se busca fazer a pontuação de um campo a cada nova compra do cliente. Ou seja, sempre que o cliente finaliza um pedido, é somado 10 pontos no campo “Bônus”. Supondo que o bônus seja concedido quando esse campo soma 40 pontos, existe a necessidade de um outro trigger que verifique esse bônus e dê a promoção. Para isso, o segundo trigger vai associar o cliente a um cluster que já está configurado em uma promoção. Veja a configuração do segundo trigger:
+![trigger](//images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/f093dfa7ef956882313f224afe0e4dd0/trigger.png)
 
-- **Condição** - O atributo Bônus for alterado
-- **Filtro adicional** - Bônus maior ou igual 40
-- **Ações em caso positivo** - Alterar o campo ClusterBônus para verdadeiro.
+### Ação que dispara o trigger
 
-Ações que serão executadas caso um registro atenda à condição do trigger mas não atenda  aos filtros. Essa opção é exatamente o contrário da opção acima. Só será executada caso o registro que passou pela condição da trigger **não** atenda aos filtros adicionais. Exemplo real:
+Para isso, é necessário decidir qual ação deve impulsionar uma outra ação. Essa configuração é separada em duas partes:
 
-- **Condição** - Um novo registro em Cadastro Estendido for inserido
-- **Filtro adicional** - Sexo igual feminino
-- **Ações em caso positivo** - Enviar um e-mail com ofertas do departamento feminino.
-- **Ações em caso negativo** - Enviar um e-mail com ofertas do departamento masculino.
+- **Regra**: ação que dispara o trigger. Exemplo: o cadastro de um novo cliente na loja.
+- **Filtros adicionais**: condições que aquela ação deve atender para a ação de resposta ser executada, como o cadastro ser feito pelo formulário de newsletter e não pela finalização de compra. Exemplo: para acionar o trigger, o cadastro precisa ser feito pelo formulário de newsletter e não pela finalização de compra.
 
-## Como configurar
+Neste exemplo, a condição do trigger seria **Sempre que um registro for inserido** e, nos filtros adicionais, deveria existir um campo "origem" filtrando por "newsletter". Assim, sempre que um novo cadastro fosse realizado, o trigger verificaria se o cliente se cadastrou pela newsletter e, somente neste caso, realizaria a ação configurada.
 
-1. Acesse o DynamicStorage (https://*SUALOJA*.ds.vtexcrm.com.br);
-2. Clique na aba **Trigger**;
-3. Clique no botão **Novo**;
-4. Insira o Nome da trigger;
-5. Preencha um e-mail que será notificado caso ocorra algum erro na execução;
-6. Selecione a [entidade de dados](/tutorial/criando-entidade-de-dados/ "entidade de dados") que irá disparar a ação do trigger;
-7. Após selecionar a entidade de dados, surgirão os demais campos de configuração;
-8. Selecione um status para a trigger;
-9. Siga na configuração de cada uma das abas conforme abaixo:
+### Tempo para o disparo
 
-### Condições
+É possível configurar vários envios separados por um intervalo de tempo. Ou, mais ainda, agendar o disparo de acordo com a data de outro campo. Exemplo: existe o campo **Data de Vencimento** no cadastro de uma entidade **Produto** e é desejado que, 1 mês antes dessa data, seja enviada uma notificação por API para outro sistema. Neste caso, o tempo de disparo será **Data de Vencimento** menos 1 mês.
 
-Aqui, são configuradas as condições que vão disparar o(s) evento(s) configurado(s) no trigger. A maneira de fazer essa configuração é descrita da seguinte forma:
+### Ações que serão executadas caso um registro atenda à regra do trigger e aos filtros
 
-#### Condição do trigger
+Aqui, você deve configurar todas as ações que serão executadas quando o registro que atendeu às condições também atendeu aos filtros. Essas ações podem ser envio de email, pontuar um campo do tipo Score2, entre outras possibilidades, detalhadas adiante.
 
-- **Se o valor de um atributo for alterado** - significa que, quando o valor do campo que for informado abaixo for alterado, em qualquer registro, este trigger será disparado.
-Deve ser informado o campo que será filtrado. Ex.: Quando o campo “Email” for alterado o trigger deve ser disparado &#8211; informe campo “Email” no campo “Informe o atributo”.
-- **Se um evento for levantado** - Este tipo foi descontinuado.
-- **Um registro for alterado** - significa que, quando um registro for alterado, em qualquer campo, este trigger será disparado.
-- **Um registro for comentado** - significa que, quando um registro for comentado, este trigger será disparado.
-- **Um registro for inserido** - significa que, quando um registro for inserido, este trigger será disparado.
-- **Um registro for removido** - significa que, quando um registro for removido, este trigger será disparado.
+Exemplo: um cenário onde se busca fazer a pontuação de um campo a cada nova compra do cliente. Sempre que o cliente finaliza um pedido, 10 pontos são somados ao valor atual do campo **Bônus**.
 
-#### Filtro adicional
+- **Regra**: quando o atributo Checkout for alterado.
+- **Filtro adicional**: Checkout igual Finalizado.
+- **Ações em caso positivo**: Alterar o campo Bônus (tipo Score2), colocando a tag bônus com valor 10 e validade 30 dias.
 
-**Adicionar grupo** - cria grupos que contém filtros. Cada um desses grupos pode se relacionar com os demais, formando camadas mais complexas de filtro.
-![relacaoGrupos](//images.contentful.com/alneenqid6w5/6n2ipjsapUYyG8quIucIke/1b789ceed1f6ea993096f0d3c857b114/relacaoGrupos.png)
+### Ações que serão executadas caso um registro atenda à regra do trigger mas não atenda aos filtros
 
-**Incluir filtro** - é possível criar dentro do último grupo criado ou sem a necessidade de grupos. Um filtro sempre interage com os demais, no modelo de conjunto, sendo as opções “E” e “OU” para cada um deles.
-Deve-se selecionar quais são os campos e quais os valores aceitos ou não para que o trigger seja disparado.
-![filtroTrigger](//images.contentful.com/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/cf6c5ef321a8d39e16a09d30c2ca1245/filtroTrigger.png)
+Nesta configuração, você deve definir ações que serão executadas somente se o registro que passou pela condição da trigger **não** atender aos filtros adicionais. Exemplo:
 
-<div class="alert alert-info">
-O Master Data v1 não permite configuração de retentativas de trigger, diferente do Master Data v2.
-</div>
+- **Regra**: um novo registro em Cadastro Estendido for inserido.
+- **Filtro adicional**: Gênero igual feminino.
+- **Ações em caso positivo**: Enviar um email com ofertas do departamento feminino.
+- **Ações em caso negativo**: Enviar um email com ofertas do departamento masculino.
 
-### Agendamento
+## Configurar trigger
 
-Aqui, é configurado quando o trigger deve ser disparado. Pode ser imediatamente, com a opção “Executar o mais rápido possível”, agendamento com uma data no calendário com  “Agendar para uma data específica” ou um valor no futuro, partindo da data atual ou da data de algum campo de data, podendo utilizar minutos, horas, dias, mês e anos com a opção “Agendar execução para uma data dinâmica”.
+Siga as instruções a seguir para criar um trigger no Master Data v1:
 
-### Ações em caso positivo
+1. Acesse o Master Data em `https://{nomedaconta}.ds.vtexcrm.com.br/`, substituindo `{nomedaconta}` pelo nome da sua conta VTEX.
+2. Clique na aba **Ativação**.
+3. Clique no botão `Adicionar`.
+4. Insira o **Nome** do trigger.
+5. Selecione a [entidade de dados](https://help.vtex.com/pt/tutorial/entidade-de-dados--tutorials_1265/ "entidade de dados") que irá disparar a ação do trigger.
 
-Serão configurados os eventos a serem disparados caso o registro que desencadeou o evento passe por todos os filtros adicionais.
+   Após selecionar a entidade de dados, surgirão os demais campos de configuração.
+7. Selecione um status para o trigger, que pode ser **Ativo** ou **Desativado**.
+8. Realize as configurações em cada uma das abas, conforme as seções:
 
-#### Alterar um atributo
+    - [Regras](#regras)
+    - [Agendar](#agendar)
+    - [Se positivo](#se-positivo)
+    - [Se negativo](#se-negativo)
 
-Esta ação altera um campo do registro que disparou a trigger. Deve ser informado qual o campo (atributo) deve ser alterado assim como qual a fórmula deve ser utilizada. O campo “Expressões dinâmica” exibe quais são os valores que devem ser inseridos na fórmula caso queira se usar valores contidos em campos do registro ou dos registros relacionados (se possuir). Entende-se como fórmula um código em C# que retorne algum valor do mesmo tipo definido na entidade de dados para o campo.
-![fórmula](//images.contentful.com/alneenqid6w5/F3qRfRkScKWAYoCas4GCe/36f27cb6e71425b80340e1221251d3d2/f_C3_B3rmula-1.png)
+9. Clique em `Salvar`.   
 
-O botão validar vai compilar o código no campo fórmula para verificar se está ou não válido e mostrará qual o valor que será retornado para o campo.
-![validacaoFormula](//images.contentful.com/alneenqid6w5/3Fjh4Q1hVCqkY0yAmMSmOM/67564a371055792fd5c0f40efed7670b/validacaoFormula.png)
+### Regras
 
-#### Incluir um comentário
+Aqui, você deve definir as condições que vão disparar o(s) evento(s) configurado(s) no trigger.
 
-Inclui um comentário no registro que disparou o trigger. Deve-se digitar o comentário que será inserido.
+#### Regra de ativação
 
-#### Enviar email
+- **O valor de um atributo é alterado**: quando o valor do campo que for informado abaixo for alterado, em qualquer registro, o trigger será disparado.
 
-Envia um e-mail para destinatários dinâmicos (contidos no registro) ou fixos. O E-mail a ser enviado é todo personalizado, podendo ser um texto, HTML ou até mesmo o conteúdo de uma URL. É possível inserir anexos e, o campo tag válidas, mostra como inserir valores de campos do registro.
-![email](//images.contentful.com/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/89d9d75e4cfdb2fd539dece5a542f8ce/email.png)
+   Na opção **Campo**, selecione o campo que será utilizado. Exemplo: se quando o campo **Email** for alterado, o trigger deva ser disparado, selecione o campo **Email**.
 
-#### Pontuar campo Score
+- **Um atributo de filtro é alterado**: quando um atributo de filtro for alterado, o trigger será disparado.
+- **Um registro é alterado**: quando um registro for alterado, em qualquer campo, o trigger será disparado.
+- **Um registro é inserido**: quando um registro for inserido, o trigger será disparado.
+- **Um registro é removido**: quando um registro for removido, o trigger será disparado.
+
+#### Filtro adicional
 
-Um campo score é um tipo especial de dado que guarda 3 informações: Chave, Pontos e Validade. Você pode definir um valor para cada um desses pontos e salvar em um campo do tipo Score. 
+- **Adicionar grupo**: cria grupos que contém filtros. Cada um desses grupos pode se relacionar com os demais, formando camadas mais complexas de filtro.
+- **Adicionar filtro**: é possível criar um filtro dentro do último grupo criado ou de maneira independente de grupos. Um filtro sempre interage com os demais, no modelo de conjunto, sendo as opções "E" e "OU" para cada um deles.
 
-#### Gerar um QRCode
+   Selecione quais são os campos e quais os valores aceitos ou não para que o trigger seja disparado.
+
+   ![filters-pt](//images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/34cbeea173c7f4944ee87c22eb406c02/filters-pt.png)
+
+<div class="alert alert-info">
+  <p>O Master Data v1 não permite configuração de retentativas de trigger, diferente do Master Data v2.</p>
+</div>
 
-Gera um QRCode com o conteúdo inserido. Este QRCode deve ser inserido em algum campo do tipo “file” do registro.
+### Agendar
 
-Podem ser configurados mais de uma ação, porém, é recomendado até 3 ações por trigger. Configure as ações conforme a prioridade, pois, caso haja algum erro na configuração de um evento, todos os eventos abaixo dele não serão disparados.
+Esta aba permite configurar quando o trigger deve ser disparado:
 
-#### Envie requisição HTTP
+- **Executar o mais rápido possível:** imediatamente.
+- **Agendar em uma data específica:** agendamento com uma data e hora no calendário.
+- **Agendar em uma data dinâmica:** definição de uma data no futuro, partindo da data atual ou da data de algum campo de data, podendo utilizar minutos, horas, dias, mês e anos.
 
-Envie uma requisição HTTP com a possibilidade de salvar informações da resposta no Master Data.
+### Se positivo
 
-Preencha a seção **Request data** com as informações da requisição a ser enviada. Na seção **Response action** você poderá indicar como as informações da resposta deverão ser salvas no Master Data.
+Nesta aba, você deve configurar os eventos a serem disparados caso o registro que desencadeou o evento passe por todos os filtros adicionais.
 
-![Master Data v1 enviar requisição http screenshot](https://images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/07197eb9ba3d6a3c298a8e27f6392c13/mdv1_trigger_http_request.PNG)
+#### Enviar um email
 
-Para configurar a **Response action** selecione a entidade de dados desejada e defina, para cada campo a ser salvo, o caminho JSON correspondente na resposta.
+Envia um email para destinatários dinâmicos (contidos no registro) ou estáticos. O email a ser enviado é  personalizado, podendo ser um texto, HTML ou até mesmo o conteúdo de uma URL. É possível inserir anexos e o campo **Tags válidas** mostra como inserir valores de campos do registro.
 
-### Ações em caso negativo
+![send-email-pt](//images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/9467386aa32cf4f3338e8d33f9a68fef/send-email-pt.png)
 
-Serão feitos os disparos de eventos para quando o registro não passar pelos filtros adicionais do trigger. Podem ser configurados os mesmos eventos das “Ações em caso positivo”.
+#### Enviar um email usando um modelo do VTEX Message Center
 
-<!--
-## Exemplo
+Envia um email utilizando um template existente no Message Center.
 
-Veja o vídeo a seguir com a configuração do seguinte cenário: Envio de um e-mail de Boas Vindas para cada novo cliente da loja. A não ser que o cliente faça parte de um cluster. Neste caso, a abordagem de boas vindas será feito por telefone, portanto, clientes do cluster “Cluster 1” não devem receber o e-mail.
+#### Adicionar pontuação ao campo Pontuação2
 
-<iframe width="840" height="473" src="https://www.youtube.com/embed/A6UrxcYIq5E?feature=oembed" frameborder="0" allowfullscreen></iframe>
--->
+Um campo do tipo Pontuação2 ou Score2 é um tipo especial de dado que guarda 3 informações: Chave, Pontos e Validade. Você pode definir um valor para cada um desses pontos e salvar em um campo desse tipo.
+
+#### Enviar uma solicitação HTTP
+
+Envia uma requisição HTTP com a possibilidade de salvar informações da resposta no Master Data.
+
+Preencha a seção **Informações da solicitação** com as informações da requisição a ser enviada. Na seção **Ação de resposta**, você poderá indicar como as informações da resposta deverão ser salvas no Master Data.
+
+![http-request-pt](//images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/7bbe43cc3c3e54a23ba82dca1e21ef19/http-request-pt.png)
+
+Para configurar a **Ação de resposta**, selecione a entidade de dados desejada e defina, para cada campo a ser salvo, o caminho JSON correspondente na resposta.
+
+### Se negativo
+
+Serão feitos os disparos de eventos para quando o registro não passar pelos filtros adicionais do trigger. Podem ser configurados os mesmos eventos das [ações em caso positivo](#se-positivo).
 
 ## Exemplos
 
 - [Configurar Carrinho Abandonado](https://help.vtex.com/pt/tutorial/configurando-carrinho-abandonado--tutorials_740)
+
diff --git a/docs/tutorials/pt/criar-um-produto-beta.md b/docs/tutorials/pt/criar-um-produto-beta.md
new file mode 100644
index 000000000..36673f385
--- /dev/null
+++ b/docs/tutorials/pt/criar-um-produto-beta.md
@@ -0,0 +1,172 @@
+---
+title: 'Criar um produto (Beta)'
+id: 2nkoy6RakJEVF7ug4ZP0bP
+status: PUBLISHED
+createdAt: 2023-10-31T13:43:19.226Z
+updatedAt: 2023-11-05T15:00:16.505Z
+publishedAt: 2023-11-05T15:00:16.505Z
+firstPublishedAt: 2023-11-05T14:13:41.744Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: criar-um-produto-beta
+locale: pt
+legacySlug: criar-um-produto-beta
+subcategory: 
+---
+
+<div class="alert alert-info"> Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso<a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.</div>
+
+A página **Adicionar produto (Beta)** possibilita criar e editar produtos e seus SKUs relacionados de forma completa no Admin VTEX. Para adicionar um novo produto, siga o passo a passo abaixo. 
+
+1. No Admin VTEX, acesse **Catálogo** > __Produtos e SKUs__ ou digite Produtos e SKUs na barra de busca no topo da página.
+2. Clique em `+ Adicionar produto`.
+3. Defina se o produto será criado como ativo na loja.
+Para que o produto seja criado como ativo na loja, você precisa selecionar a opção **Ativo** <i class="fas fa-toggle-on"></i> no canto superior direito da página.
+Caso você queira criar um produto no modo inativo, clique no botão <i class="fas fa-toggle-on"></i> e observe que a opção mudará para **Inativo**. É possível ativá-lo posteriormente pela página de edição do produto ou pela lista de produtos.
+4. Preencha as informações de cada aba. Abaixo você encontra mais informações sobre cada uma delas:
+- [Produto](https://docs.google.com/document/d/186UuyKqeTz8CNGGm8UTcw81kp18RoApX5zuXccZHylc/edit#produtos)
+- [Atributos](https://docs.google.com/document/d/186UuyKqeTz8CNGGm8UTcw81kp18RoApX5zuXccZHylc/edit#atributos)
+- [SKUs](https://docs.google.com/document/d/186UuyKqeTz8CNGGm8UTcw81kp18RoApX5zuXccZHylc/edit#skus)
+5. Selecione a opção **Ativo** <i class="fas fa-toggle-on"></i> no canto superior direito da página para ativar o SKU.
+6. Clique em `Salvar`.
+
+Feito isso, o produto será ativado e estará disponível na sua loja.
+
+<div class="alert alert-info">Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo  <a href="https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382">Por que o produto não aparece no site?</a> para entender como resolver esse problema.</div>
+
+# Produto
+Nesta aba, você vai realizar o cadastro do produto preenchendo os campos descritos abaixo com as características do item.
+
+## Informações gerais
+![image9](//images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
+
+- **Nome**: informe o título do produto na loja. Use palavras simples e evite outros idiomas ou escrita complexa. Esse campo é importante para SEO e deve respeitar o limite de 150 caracteres. Campo obrigatório. 
+**Exemplo**: Tênis Esportivo Ultralight.
+- **Palavras substitutas**: escreva sinônimos de termos relacionados ao nome dado para o produto, separados por vírgula (`,`). Esse campo é importante para tornar suas buscas mais abrangentes e deve respeitar o limite de 8000 caracteres. **Exemplo**: para o produto Tênis Esportivo Ultralight, as palavras similares podem ser Tênis Esporte Leve,Tênis Ultra Esportivo. Caso sua loja utilize o VTEX Intelligent Search não preencha este campo, leia o artigo Sinônimos.
+- **Marca**: selecione uma marca já cadastrada na loja para relacionar ao produto. Campo obrigatório. __Exemplo__: SportXtreme.
+- **Categoria**: selecione a categoria ou subcategoria relacionada ao produto. Campo obrigatório. __Exemplo__: Calçados Esportivos.
+- **Código de referência**: escreva o código de referência único do produto para facilitar a organização da sua loja. __Exemplo__: TXU1234.
+
+## Descrição
+
+Nesta etapa, você precisa escrever uma descrição das principais informações relacionadas ao produto. O texto deve ser um resumo simples e de fácil entendimento para o cliente. 
+
+**Exemplo**: "O Tênis Esportivo Ultralight é a escolha perfeita para os atletas que buscam alto desempenho e conforto. Com design inovador e materiais de alta tecnologia, este tênis proporciona máxima leveza e resistência durante as atividades físicas."
+
+O editor de texto da descrição é do tipo rich text, ou seja, você pode utilizar diversos recursos de formatação utilizando a barra de ferramentas desse campo, ilustrada abaixo.
+
+![image10](//images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
+Veja quais são os recursos disponíveis a partir da barra de ferramentas:
+
+- **Estilos**: define o estilo do texto selecionado. As opções são: Normal e Título 1 até Título 6.
+- **Tamanho da fonte**: altera o tamanho da fonte do texto selecionado. Você pode optar por um valor de 10 a 36 pts.
+- **Negrito**: formata o texto selecionado em negrito.
+- **Itálico**: formata o texto selecionado em itálico.
+- **Sublinhado**: sublinha o texto selecionado.
+- **Alinhar à esquerda**: alinha o texto selecionado à esquerda.
+- **Alinhar ao centro**: centraliza o texto selecionado.
+- **Alinhar à direita**: alinha o texto selecionado à direita.
+- **Lista com marcadores**: transforma o texto selecionado em um item de uma lista não ordenada, com marcadores.
+- **Lista numerada**: transforma o texto selecionado em um item de uma lista ordenada.
+- **Adicionar link**: insere um link no texto selecionado. Ao clicar neste botão, é necessário preencher as informações abaixo e, em seguida, clicar em `Salvar`.
+- **Título do link**: escreva o texto que vai conter o link.
+- **URL**: insira o link ao qual o texto vai direcionar o usuário.
+- **Abrir em uma nova aba**: selecione esta opção se você deseja que, ao clicar no link, o usuário abra a página em uma nova aba do navegador. Não selecione se o objetivo for que o usuário acesse o link na mesma aba.
+- **Código-fonte**: exibe o código fonte da descrição em HTML. Você pode editar a descrição diretamente pelo código-fonte, se desejar. Para retornar à visão anterior, é necessário clicar novamente no botão referente ao código-fonte.
+## SEO
+![image11](//images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
+-  **URL do produto**: insira a URL pela qual será possível acessar o produto na loja. Neste campo, você não pode utilizar espaço nem caracteres especiais. Caso a URL seja composta por mais de uma palavra, você precisa separá-las com um `-`. Campo obrigatório. **Exemplo**: tenis-esportivo-ultralight.
+
+- **Título da página**: escreva o título da página do produto. Para otimizar a classificação do seu produto nos resultados de busca, o ideal é não ultrapassar 60 caracteres. Campo obrigatório. **Exemplo**: Tênis Esportivo Ultralight.
+
+- **Meta descrição**: escreva o título da página do produto. Para otimizar a classificação do seu produto nos resultados de busca, o ideal é não ultrapassar 60 caracteres. Campo obrigatório. **Exemplo**: Conheça o Tênis Esportivo Ultralight da SportXtreme, perfeito para atletas que buscam leveza e desempenho máximo nas atividades esportivas.
+
+## Operação e logística
+![image7](//images.ctfassets.net/alneenqid6w5/7u4kwyRsDBKFi1WVu5nV2q/3372b498b4d49932670575ea0b8211ab/image7.png)
+
+- **Políticas comerciais**: selecione uma ou mais políticas comerciais a que o produto se destina, para definir a quais marketplaces o produto será disponibilizado. Caso nenhuma política comercial seja selecionada, o produto vai ser considerado para todas elas. **Exemplo**: B2C.
+- **Fornecedor**: selecione um fornecedor já cadastrado na loja para relacionar ao produto.
+- **Código fiscal**: informe o número de identificação fiscal do produto.
+
+## Visibilidade
+![image4](//images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)
+
+- **Mostrar no site**: ative ou desative a visibilidade do produto na sua loja. Caso o produto seja um brinde que não pode ser comprado, por exemplo, é importante desativar esta opção.
+- **Mostrar quando fora de estoque**: ative ou desative a opção de mostrar o produto na loja mesmo quando não houver quantidade em estoque. Se ativada, o produto esgotado aparece na sua loja no formato de [Avise-me](https://help.vtex.com/pt/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e) — campo em que o cliente informa seu email para ser avisado quando o produto estiver novamente disponível. Se essa opção for desativada, o produto não vai aparecer na loja quando estiver esgotado.
+- **Prioridade na ordenação de busca**: informe um valor numérico para definir a prioridade na página de resultado de busca. Para mais detalhes sobre este campo, leia [Como funciona o campo Score?](https://help.vtex.com/pt/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae). Caso sua loja utilize o VTEX Intelligent Search, leia [Como o VTEX Intelligent Search funciona?](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/23mytRDsEduqLO0Lo7yufy).
+
+## Atributos
+
+Dependendo da categoria do produto criado, podem aparecer campos para você preencher na aba Atributos. Esses campos são especificações que você pode adicionar aos seus SKUs para atribuir características aos produtos da sua loja.
+
+Se você tiver criado algum campo de produto obrigatório, o produto só poderá ser ativado após o preenchimento desta [especificação](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).
+
+Em Atributos, será exibido os [grupos de especificações](https://help.vtex.com/pt/tutorial/criando-grupo-de-especificacoes-em-uma-categoria--tutorials_246) com as especificações cadastradas abaixo. Na imagem a seguir, o grupo de especificação é **Características** e as especificações cadastradas nele são **Vídeo** e **Veja Mais**.
+
+![image3](//images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
+
+## SKUs
+
+Nesta aba, você fará o cadastro de SKUs que serão atrelados ao produto criado anteriormente. 
+
+Para um produto disponível na sua loja, ele deve ter pelo menos um SKU ativo. É obrigatório que o SKU tenha uma imagem adicionada a ele para que ele seja ativado.
+
+## Especificações
+
+Aqui serão exibidas as especificações criadas anteriormente para os SKUs. Se você tiver criado algum campo de SKU obrigatório, o SKU só poderá ser ativado após o preenchimento desta especificação. 
+
+## Informações básicas
+![image2](//images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
+- **Nome**: nome do SKU. Este nome será exibido na loja. Campo obrigatório.
+- **Código de referência**: código que será utilizado internamente pela loja para identificar o SKU. Campo obrigatório caso o SKU não tenha EAN/UPC preenchido.
+- **EAN/UPC**: campo que deve conter a informação do código de barras. Campo obrigatório caso o SKU não tenha o Código de referência preenchido.
+- **Código do fabricante**: fornecido pelo fabricante para identificar seu produto. Caso algum produto tenha um código específico, esse campo deve se preenchido.
+- **Condição comercial**: utilizado para definir promoções ou regras de parcelamento específicas para SKUs. Caso não exista uma condição específica, usar o valor padrão. Saiba mais no artigo [Cadastrar condição comercial](https://help.vtex.com/pt/tutorial/como-cadastrar-condicao-comercial--tutorials_445).  
+- **Modal**: campo que realciona um produto não usual (carne, vidro, colchão) a uma transportadora especializada na entrega desse tipo de produto. Saiba mais no artigo Como funciona o modal.
+
+## Imagens
+
+<div class="alert alert-warning">SKUs devem ter pelo menos uma imagem para estar ativo.</div>
+
+Para adicionar uma imagem a seu SKU, siga os passos abaixo:
+
+1. Clique no botão `+`.![image8](//images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
+2. Adicione o link da sua imagem no campo 🔗. Você pode adicionar mais de uma imagem ano seu SKU. Para isso, clique em + Adicionar imagem e adicione o novo link.![image6](//images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
+3. Clique em `Salvar`.
+
+<div class="alert alert-info"> A primeira imagem adicionada será a imagem principal do SKU que será exibida na loja e nos resultados de busca. </div>
+
+ Você pode editar os metadados de uma imagem clicando no botão <i class="fas fa-ellipsis-v"></i> e selecione <i class="fas fa-pencil-alt"></i> Editar metadados.
+
+Também é possível deletar uma imagem clicando no botão <i class="fas fa-ellipsis-v"></i> e selecione <i class="fas fa-trash-alt"></i> `Remover`. 
+
+## Pesos e medidas
+- **Peso e dimensões para frete**:
+ ![image1](//images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
+
+- **Peso do pacote**: peso do pacote vazio em quilos. Campo obrigatório.
+- **Largura do pacote**: largura do pacote em centímetros. Campo obrigatório.
+- **Altura do pacote**: altura do pacote em centímetros. Campo obrigatório.
+- **Comprimento do pacote**: comprimento do pacote em centímetros. Campo obrigatório.
+
+## Peso e dimensões reais
+
+- **Peso real**: peso do SKU em quilos.
+- **Largura real**: largura do SKU em centímetros. 
+- **Altura real**: altura do SKU em centímetros.
+- **Comprimento real**: comprimentoaltura do SKU em centímetros.
+
+ ## Sistema de medidas
+
+- **Unidade de medida**: utilizadao apenas em casos onde é necessário converter a unidade de medida para a venda. Por exemplo, se o produto é vendido em caixas, mas os clientes querem comprar por m². Nos casos comuns, utilizar “un”.
+
+- **Multiplicador de unidade**: unidade numérica que multiplica a quantidade selecionada do produto ao ser inserido no carrinho. Caso o multiplicador seja 5, o produto será adicionado em quantidades múltiplas de 5, ou seja 5, 10, 15, 20, e assim porem diante. 
+
+## Configurações avançadas
+![image5](//images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
+
+- **Ativar kit**: determina se os SKUs que compõem um kit só podem ser vendidos juntos. Você pode fazer com que o SKU faça parte de um kit <i class="fas fa-toggle-on"></i> ou não <i class="fas fa-toggle-off"></i>.
+
+- **Gerar crédito em valores**: determina se o cliente receberá [crédito](https://help.vtex.com/pt/tutorial/gift-card--tutorials_995) que o cliente recebe ao concluir uma compra de uma unidade de um determinado SKU. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> esta opção.
+
diff --git a/docs/tutorials/pt/crm-zen-suiteshare.md b/docs/tutorials/pt/crm-zen-suiteshare.md
index bb2bd0d16..a1868d800 100644
--- a/docs/tutorials/pt/crm-zen-suiteshare.md
+++ b/docs/tutorials/pt/crm-zen-suiteshare.md
@@ -21,17 +21,17 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **CRM Zen**.
 
-   ![CRM Zen_1](https://images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
+   ![CRM Zen_1](//images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
 
 2. Acesse **Configurações > Integrações > Vendas > CRM Zen > Habilitar**.
 
-   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
-   ![CRM Zen_3](https://images.ctfassets.net/alneenqid6w5/5r5pR9IWVJ38GAoO7q7YeR/d03a734f6b33423349984d6b762995a7/CRM_Zen_3.png)
+   ![CRM Zen_3](//images.ctfassets.net/alneenqid6w5/5r5pR9IWVJ38GAoO7q7YeR/d03a734f6b33423349984d6b762995a7/CRM_Zen_3.png)
 
 O próximo passo, é acessar o **CRM Zen** e realizar o login na sua conta.
 
-![CRM Zen_4](https://images.ctfassets.net/alneenqid6w5/zyC2JfLz9tZQfbqbkosuy/13fd076b9182d8236f5a314e4ec617dd/CRM_Zen_4.png)
+![CRM Zen_4](//images.ctfassets.net/alneenqid6w5/zyC2JfLz9tZQfbqbkosuy/13fd076b9182d8236f5a314e4ec617dd/CRM_Zen_4.png)
 
 Agora, dentro da plataforma CRM Zen localize os tokens, clicando no ícone de engrenagem e selecionando **Integração**.
 
@@ -39,7 +39,7 @@ Com as informações do **Token de integração** e/ou o de **notas** (e todos
 
 Após localizar o **CRM Zen** e acessar a opção **Habilitar**, é preciso configurar a integração para cada formulário de captura criado. Para isso, selecione o link de captura em **Selecione**.
 
-![CRM Zen_5](https://images.ctfassets.net/alneenqid6w5/4XA4qcTFMx1SzII6oqyTB7/2638f1e3b4e8903dd0fabe6bd0f3e932/CRM_Zen_5.png)
+![CRM Zen_5](//images.ctfassets.net/alneenqid6w5/4XA4qcTFMx1SzII6oqyTB7/2638f1e3b4e8903dd0fabe6bd0f3e932/CRM_Zen_5.png)
 
 O próximo passo, é configurar o **Tipo de integração**, preencher o **Token de integração** e configurar o **Compartilhamento (opcional)**, conforme a estratégia da sua Empresa.
 
diff --git a/docs/tutorials/pt/custom-fields-when-adding-an-organization.md b/docs/tutorials/pt/custom-fields-when-adding-an-organization.md
new file mode 100644
index 000000000..826dc0c82
--- /dev/null
+++ b/docs/tutorials/pt/custom-fields-when-adding-an-organization.md
@@ -0,0 +1,46 @@
+---
+title: 'Campos personalizados no cadastro de organização'
+id: 2MqEVusOvcbqagNwOuHA7f
+status: PUBLISHED
+createdAt: 2024-06-06T12:19:51.817Z
+updatedAt: 2024-07-03T17:35:29.850Z
+publishedAt: 2024-07-03T17:35:29.850Z
+firstPublishedAt: 2024-06-06T12:40:11.507Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: campos-personalizados-no-cadastro-de-organizacao
+locale: pt
+legacySlug: campos-personalizados-no-cadastro-de-organizacao
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+A plataforma VTEX permite que usuários de uma organização com perfil de administrador criem e gerenciem campos personalizados no processo de cadastro de novas organizações ou centros de custo. Este recurso facilita a inclusão de informações específicas e relevantes para a empresa.
+
+## Definição e gerenciamento de campos
+
+Os usuários da organização com perfil de administrador podem definir campos adicionais no Admin VTEX, que serão exibidos para preenchimento durante o cadastro de novas organizações ou centros de custo. Esses campos personalizados são projetados para capturar dados específicos e úteis para empresa e que não estão disponíveis no formulário de cadastro.
+
+## Cadastrando o campo personalizado
+
+Os campos personalizados permitem que os usuários adicionem informações específicas e personalizadas para organizações ou centros de custo. Esses campos podem ser adaptados de acordo com as necessidades da empresa, permitindo capturar informações relevantes para a empresa.
+
+Para cadastrar o campo personalizado, siga os seguintes passos abaixo:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+
+2. Clique na aba **Os campos personalizados**.
+
+3. Escolhe entre as opções Organizações ou Centros de custo na caixa de seleção.
+
+4. Clique em **Adicionar** campo. Uma linha vazia será adicionada na lista de campos personalizados.
+
+5. Sob a linha vazia, clique em <i class="fas fa-ellipsis-v" aria-hidden="true"></i> para editar.
+
+6. Preencha as informações necessárias:
+    - **Use no registro:** indica se o campo deve ser exibido no formulário de cadastro.
+    - **Tipo de campo:** determina se o campo exibido será um texto ou uma lista com valores a serem escolhidos pelo usuário.
+    - **Nome do campo personalizado:** nome do campo que deseja personalizar.
+7. Clique em `Atualizar`.
+
+Certifique-se de clicar em `Save Settings` no canto superior direito da página após qualquer alteração.
diff --git a/docs/tutorials/pt/custom-payment-information-for-argentina.md b/docs/tutorials/pt/custom-payment-information-for-argentina.md
index a4f549f3b..ab8ab61bf 100644
--- a/docs/tutorials/pt/custom-payment-information-for-argentina.md
+++ b/docs/tutorials/pt/custom-payment-information-for-argentina.md
@@ -1,10 +1,10 @@
 ---
 title: 'Informações dos pagamentos customizados da Argentina'
 id: jvDroisg0wu0sQMAW4qAs
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.320Z
-updatedAt: 2019-12-31T15:27:50.416Z
-publishedAt: 2019-12-31T15:27:50.416Z
+updatedAt: 2024-03-19T12:11:44.590Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:14:28.069Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/custom-product-fields.md b/docs/tutorials/pt/custom-product-fields.md
new file mode 100644
index 000000000..852e734e7
--- /dev/null
+++ b/docs/tutorials/pt/custom-product-fields.md
@@ -0,0 +1,90 @@
+---
+title: 'Campos customizáveis de produto'
+id: 6tJOSJ2o9phVIb8XXG6QSk
+status: PUBLISHED
+createdAt: 2024-07-23T19:44:34.554Z
+updatedAt: 2024-07-23T20:25:32.123Z
+publishedAt: 2024-07-23T20:25:32.123Z
+firstPublishedAt: 2024-07-23T20:17:01.358Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: campos-customizaveis-de-produto
+locale: pt
+legacySlug: campos-customizaveis-de-produto
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+Os campos customizáveis permitem adaptar os atributos do produto conforme necessário, melhorando as informações dos produtos enviados para o Mercado Livre.  
+Nessa documentação você encontra **quais campos podem ser customizados**, **como criar um novo campo** e **quais valores são aceitos**.  
+
+## Campos customizáveis
+
+Veja na tabela abaixo quais campos podem ser customizados e qual a descrição do campo:
+
+| **Nome do campo** | **Descrição** |
+|:---:|:---:|
+| meli_title | Envia o nome cadastrado neste campo ao invés do nome que consta no campo `title`. |
+| meli_shipping_mode | Define o [tipo logístico](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy) utilizado pelo seller: [me1](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy#mercado-envios-1-me1) ou [me2](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4551ZlEQI8qmiSWieigoKy#mercado-envios-2-me2). |
+| officialstoreid_meli | Define qual a loja oficial do seller no Mercado Livre. |
+| plaintext_description_meli | Envia a descrição de produto cadastrada neste campo ao invés da descrição que consta no campo `productDescription`. |
+| free_shipping | Informa ao Mercado Livre se o produto é oferecido com a opção de frete grátis.  |
+
+## Criando novo campo de produto 
+
+Para criar um campo de produto, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Catálogo**, ou digite **Catálogo** na barra de busca no topo da página.  
+2. Clique em **Categorias.**  
+3. Clique na categoria associada ao grupo de especificações em que você deseja criar um campo de produto.  
+  Observe que ao criar um campo em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela.  
+4. Clique em Ações<i class="fas fa-angle-down" aria-hidden="true"></i>.  
+5. Clique em **Campo (Produto).**  
+6. Clique em **Novo Campo.**  
+7. Preencha as informações referentes ao campo que está sendo criado:  
+<div class="alert alert-warning">
+O nome do campo deve ser preenchido exatamente como um dos nomes apresentados na tabela da seção <a href="#campos-customizaveis">Campos customizáveis</a>.
+</div>  
+
+  **Nome:** nome da especificação (campo) de produto.  
+  **Texto:** descrição sobre o campo.  
+  **Tipo:** tipo de campo, que pode variar entre **Texto, Texto Grande, Número, Combo, Radio, CheckBox, Texto Indexado e Texto Grande Indexado.** [Leia a seção Tipos de campo de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106#tipos-de-campo-de-produto) para mais informações sobre cada opção.  
+  **Valor Padrão:** valor de preenchimento já definido na criação do campo.  
+  **Grupo:** nome do [grupo de especificações](https://help.vtex.com/pt/tutorial/criando-grupo-de-categoria) criado anteriormente, do qual esse campo fará parte.  
+  **Filtro:** define se a especificação será utilizada como filtro na navegação do site.  
+  **Obrigatório:** define se o valor obrigatoriamente precisa ser preenchido no cadastro do produto ou não. Caso o campo seja obrigatório, o produto só poderá ser ativado após o preenchimento desta especificação.  
+  **Exibe Especificação:** define se o campo é mostrado na página de detalhes do produto, na aba **Especificações.**  
+  **Link no Menu Superior:** define se o link para os valores do campo é mostrado no menu principal do site.  
+  **Link no Menu Lateral:** define se o link para os valores do campo é mostrado no menu lateral do site.  
+  **Ativo:** insere ou remove este campo no cadastro do produto (aba Especificações).  
+8. Clique em **Salvar.**  
+
+## Cadastrar valores para o campo de produto
+
+Os valores dos campos de produto irão variar conforme o tipo do campo. Para os campos de tipo de **Texto** e **Número,** não há valores pré-definidos criados, os valores serão preenchidos livremente durante o cadastro do produto, na aba **Especificações.**  
+
+Já para os campos de tipo **Combo**, **Radio** e **CheckBox**, é necessário cadastrar valores pré-definidos para seleção durante o cadastro do produto. Confira na tabela abaixo os valores aceitos para cada campo customizável:  
+
+| **Nome do campo** | **Tipo do campo** | **Descrição do tipo de campo** | **Valor do campo** |
+|:-:|:--:|:----:|:--:|
+| meli_title | Texto grande | Preenchimento do conteúdo como texto livre, indicado para grandes estruturas de HTML. | Texto livre |
+| meli_shipping_mode | Combo | Conteúdo com dois ou mais valores pré-definidos, para seleção de uma opção em uma lista suspensa (dropdown). | me1 e me2 |
+| officialstoreid_meli | Texto | Preenchimento do conteúdo como texto livre, indicado para textos pequenos e de formatação simples. Não é indicado para grandes estruturas de HTML. | Texto alfanumérico. Ex: 8457 |
+| plaintext_description_meli | Texto grande | Preenchimento do conteúdo como texto livre, indicado para grandes estruturas de HTML. | Texto livre |
+| free_shipping | Checkbox | Opção que tem apenas valores equivalentes a verdadeiro ou falso. | Se a checkbox estiver marcada, o frete é grátis, se a checkbox estiver desmarcada, o frete não é grátis. |
+
+Confira as instruções a seguir:  
+
+1. No Admin VTEX, acesse **Catálogo**, ou digite **Catálogo** na barra de busca no topo da página.  
+2. Clique em **Categorias.**  
+3. Clique na categoria em que o campo de produto está salvo.  
+4. Clique no botão **Ações**<i class="fas fa-angle-down" aria-hidden="true"></i>.  
+5. Clique em **Campo (Produto)**.  
+6. Clique na seta para baixo <i class="fas fa-angle-down" aria-hidden="true"></i>.  
+7. Clique em **Valores**.  
+  Nesta página é possível criar um **Novo valor** ou **Editar** os valores estabelecidos anteriormente.  
+8. Preencha o campo **Nome** com os valores que você deseja criar para aquele campo. Insira um valor por linha e tecle `Enter` entre cada valor.  
+9. Clique em **Salvar**.  
+
+Os valores criados serão exibidos na aba **Especificação** no cadastro de Produto.  
+
diff --git a/docs/tutorials/pt/customer-approval.md b/docs/tutorials/pt/customer-approval.md
index 66440ddc6..e21f7fa79 100644
--- a/docs/tutorials/pt/customer-approval.md
+++ b/docs/tutorials/pt/customer-approval.md
@@ -3,8 +3,8 @@ title: 'Aprovação de clientes'
 id: 2fDHMMLJl00Pm6imiACU72
 status: PUBLISHED
 createdAt: 2021-03-30T16:54:48.752Z
-updatedAt: 2023-03-29T00:06:00.612Z
-publishedAt: 2023-03-29T00:06:00.612Z
+updatedAt: 2024-06-18T22:16:38.698Z
+publishedAt: 2024-06-18T22:16:38.698Z
 firstPublishedAt: 2021-03-30T17:14:26.769Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,25 +15,25 @@ legacySlug: aprovacao-clientes
 subcategory: 42hDtnYXHw5ExG6l19RP1l
 ---
 
-A aprovação de clientes é realizada no Master Data e pode ser realizada via Admin ou via API.
+A aprovação de clientes é realizada no Master Data e pode ser efetuada através do Admin ou via API. Confira a seguir as instruções para cada uma das duas formas de aprovação.
 
-## Aprovação de clientes via Admin
+## Aprovar clientes no Admin
 
-Para aprovar clientes no Admin:
+Para aprovar clientes no Admin, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
-2. Dentro do box __Profile System__, clique no ícone  <i class="fas fa-bars"></i>   ao lado de __Clientes.__
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Dentro do card __Profile System__, clique no ícone  <i class="fas fa-bars"></i>   ao lado de __Clientes__.
 3. Clique na linha correspondente ao cliente que deseja aprovar.
-4. No final da página, clique no botão azul __“Editar”.__
-5. Ao lado do campo “Aprovado”, marque a __caixa de seleção.__
-6. No final da página, clique no botão azul __“Salvar”.__
+4. No final da página, clique no botão `Editar`.
+5. Ao lado do campo **Aprovado**, marque a caixa de seleção.
+6. No final da página, clique no botão `Salvar`.
 
 Desse modo, o conteúdo da loja será exibido para os clientes selecionados. 
 
-## Aprovação de clientes via API
+## Aprovar clientes via API
 
-Você pode aprovar vários clientes de uma vez por meio de uma rota da [API do Master Data](https://developers.vtex.com/vtex-developer-docs/reference/master-data-api-v2-overview "API do Master Data").
+Você pode aprovar vários clientes de uma vez por meio de uma rota da [API do Master Data](https://developers.vtex.com/docs/api-reference/masterdata-api "API do Master Data").
 
-Todas as informações relacionadas a um cliente podem ser interpretadas como um documento na [entidade de dados “Cliente”](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265 "entidade de dados "Cliente""). Logo, a rota [PATCH Create or Update partial document](https://developers.vtex.com/vtex-developer-docs/reference/documents#createorupdatepartialdocument "PATCH Create or Update partial document") deve ser utilizada para alterar o valor relativo ao campo “Aprovado” de forma massiva.
+Todas as informações relacionadas a um cliente podem ser interpretadas como um documento na [entidade de dados](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265) __Cliente__. Logo, a rota [PATCH Update partial document](https://developers.vtex.com/docs/api-reference/masterdata-api#patch-/api/dataentities/-acronym-/documents/-id- "PATCH Update partial document") deve ser utilizada para alterar o valor relativo ao campo __Aprovado__ de forma massiva.
 
-Confira o artigo [Importar dados de clientes](https://help.vtex.com/pt/tutorial/importar-datos-de-clientes-brasil?locale=pt "Importar dados de clientes") para saber quais campos devem ser criados para um documento específico de pessoa física. 
+Confira o artigo [Importar dados de clientes](https://help.vtex.com/pt/tutorial/importando-dados-de-clientes-brasil--2zWYVOyj0sISYQmeUwCsI0 "Importar dados de clientes") para saber quais campos devem ser criados para um documento específico de pessoa física.
diff --git a/docs/tutorials/pt/customer-credit-overview.md b/docs/tutorials/pt/customer-credit-overview.md
index 4113b1b0d..3e22fed1d 100644
--- a/docs/tutorials/pt/customer-credit-overview.md
+++ b/docs/tutorials/pt/customer-credit-overview.md
@@ -3,8 +3,8 @@ title: 'Customer Credit - Visão Geral'
 id: 1uIqTjWxIIIEW0COMg4uE0
 status: PUBLISHED
 createdAt: 2018-11-08T17:11:28.486Z
-updatedAt: 2023-03-29T14:46:02.462Z
-publishedAt: 2023-03-29T14:46:02.462Z
+updatedAt: 2024-02-09T21:37:56.199Z
+publishedAt: 2024-02-09T21:37:56.199Z
 firstPublishedAt: 2018-11-08T19:14:39.491Z
 contentType: tutorial
 productTeam: Financial
@@ -15,85 +15,76 @@ legacySlug: credit-control-visao-geral
 subcategory: 7EWKfPIGfmI0G8iMYK8Aiy
 ---
 
-O Customer Credit é a app da VTEX que permite a loja oferecer crédito para os clientes de confiança. Com mais tempo para pagar o cliente tem maior poder de compra.
-
-Pela plataforma é possível configurar prazos e parcelamentos e gerenciar contas, definindo limites de crédito e acompanhando os  títulos de cobrança emitidos. Seus clientes têm visibilidade sobre o crédito disponível e os valores a pagar direto no site da sua loja.
+O Customer Credit é a app da VTEX que permite uma loja oferecer crédito exclusivo a seus clientes de confiança, aumentando o poder de compra ao permitir um prazo maior para pagamento dos pedidos.
 
 ## Quando utilizar
 
-Modelos de negócio que têm uma relação comercial com seus clientes costumam precisar de um sistema de gerenciamento de crédito para poder emitir boletos faturados sem pôr em risco o fluxo de caixa da empresa. 
+Modelos de negócio que possuem uma relação comercial consolidada com seus clientes geralmente necessitam de um sistema de gerenciamento de crédito que permita a emissão de boletos faturados sem comprometer o fluxo de caixa da empresa.
 
-A aprovação desses pagamentos em plataformas de e-commerce costumam demandar esforço manual de aprovação pedido a pedido, mesmo com clientes que possuem crédito disponível.
+A aprovação desses tipos de pagamentos em plataformas de ecommerce costumam demandar esforço manual de aprovação pedido a pedido, mesmo para aqueles clientes que já possuem crédito disponível.
 
-Lojas com relações B2B como distribuidores de redes varejistas, venda direta para revendedores, material de escritório para empresas ou insumos industriais podem utilizar o Customer Credit para oferecer uma experiência integrada à plataforma VTEX de compra e pagamento a prazo. 
+Lojas que realizam transações comerciais B2B, tais como, distribuidores de redes varejistas, venda direta para revendedores, materiais de escritório para empresas ou insumos industriais, podem utilizar o Customer Credit para oferecer uma experiência de compra e pagamento a prazo integrada à plataforma VTEX.
 
 ## Como funciona
 
-![Fluxo básico do Customer Credit](https://images.ctfassets.net/alneenqid6w5/uTJmG1ZC48mCQeQKMCQ4m/5c64e88daa90836eeeabb7903af91a0f/cc-flow_pt.gif)
-*Fluxo básico de como funciona o Customer Credit nas lojas VTEX.*
+Por meio do Admin VTEX ou da [API do Customer Credit](https://developers.vtex.com/docs/api-reference/customer-credit-api), você pode realizar as seguintes ações no app do Customer Credit:
 
-Por ter sido desenvolvido na VTEX, o Customer Credit está plenamente integrado ao SmartCheckout, o que significa que a experiência de compra dos seus clientes permanece a mesma.
-Você pode escolher os usuários que receberão crédito, definir o limite de crédito para cada um deles e gerenciar individualmente cada título.
+- Criar e gerenciar contas para os clientes escolhidos
+- Definir limites e tolerâncias de crédito para cada conta
+- Configurar prazos e parcelamentos de títulos de cobrança
+- Acompanhar e modificar o status dos títulos emitidos
 
-O Customer Credit pode ser utilizado tanto pela interface web do Admin quanto pela API.
+<div class="alert alert-info">
+Quando instalado, o Customer Credit aparece como uma opção de pagamento no Checkout somente para os clientes selecionados pelo lojista, exibindo o valor de crédito disponível para ser utilizado na compra.
+</div>
 
-## Conceitos
+Veja abaixo o fluxo básico de funcionamento do Customer Credit nas lojas VTEX:
 
-### Conta corrente
+![GIF_CC_PT](//images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/4aa3ae0434d69c91f827675128a5ae13/GIF_CC_PT.gif)
 
-Para conseguir ter acesso ao pagamento a prazo o usuário deve ter acesso a uma conta cadastrada no Customer Credit. Esta conta é composta por identificadores como e-mail e documento, assim como o limite de crédito definido.
+## Definições no Customer Credit
 
-### Limite de crédito
+### Conta (Customer Credit account)
 
-Para cada conta você deve definir um limite de crédito. Esse limite indica o valor máximo que a conta pode ter em títulos abertos ao mesmo tempo. 
-Quando títulos forem pagos ou cancelados, seus valores restauram o limite de crédito. O limite pode ser redefinido a qualquer momento pelo usuário com as permissões necessárias.
+Para utilizar o Customer Credit como meio de pagamento em uma compra, o cliente deve ter uma conta cadastrada pelo lojista no app do Customer Credit. Esta conta possui informações como, tipo e número de documento do titular, email, limite e tolerância de crédito.
 
-No momento da compra, o cliente tem visibilidade de quanto crédito tem disponível. Quando não é o suficiente para o valor total, não é possível utilizar seus créditos.
+### Limite de crédito
 
-O limite de crédito definido em uma conta também pode ser utilizado por mais de um dependente. 
+Cada conta possui um limite de crédito cadastrado no momento de sua abertura. Esse limite indica o valor máximo que o cliente pode utilizar para realizar uma ou mais compras  ao mesmo tempo via Customer Credit.
 
-### Título
+<div class="alert alert-warning">
+O limite de crédito de uma conta pode ser alterado pelo lojista a qualquer momento.
+</div>
 
-Título são referências de pagamentos futuros. Eles são automaticamente criados quando um pedido pago com Customer Credit é faturado. Ele é composto por data de vencimento, valor e descrição. 
+### Crédito disponível
 
-Um link de pagamento externo pode ser adicionado a cada título para facilitar sua liquidação.
+Valor que o cliente ainda tem disponível em sua conta para realizar compras por meio do Customer Credit.
 
-Há 3 estados possíveis para os títulos: **Aberto**, **Pago** e **Cancelado**. Na interface haverá um 4o estado, o **Vencido**, mas que é na realidade um título em *Aberto* cuja data de vencimento está expirada.
+Sempre que o cliente conclui uma compra e o pedido é faturado, o valor do crédito disponível diminui. Entretanto, após o cliente efetuar o pagamento do título emitido, o valor de crédito disponível retorna ao valor pré-compra.
 
-Um título é sempre criado com o status de Aberto, e dependendo de ações do Admin ou chamadas de API pode transitar para o estado de Pago ou Cancelado. 
+<div class="alert alert-warning">
+No momento de uma compra, o cliente tem visibilidade de quanto crédito é possível utilizar via Customer Credit. Caso o valor da compra seja maior que o crédito disponível, o pagamento não poderá ser realizado por meio do Customer Credit.
+</div>
 
-### Tolerância
+### Título
+
+Título é o documento gerado após o cliente realizar uma compra utilizando o Customer Credit como meio de pagamento e o pedido ser faturado.
 
-Permite que uma compra seja aprovada mesmo que ela ultrapasse o crédito disponível do usuário. Caso a funcionalidade seja ligada, uma porcentagem poderá ser configurada individualmente para cada conta cadastrada.
+Em casos de compras parceladas, os títulos são gerados de acordo com o número de parcelas. Por exemplo, uma compra efetuada com pagamento em 10x no Customer Credit irá gerar 10 títulos relacionados ao mesmo número do pedido.
 
 ### Prazos e parcelamentos
 
-O Customer Credit permite que você configure como quiser os prazos de parcelamentos que estarão disponíveis para seus clientes. Alguns exemplos comuns de prazos usados são de 7 dias, 28, 45, 30/60, 30/60/90, etc.
+O Customer Credit permite que o lojista configure diferentes cenários de prazos e parcelamentos de títulos para oferecer uma maior flexibilidade de pagamento aos clientes cadastrados.
 
 ### Pré-autorização e liquidação
 
-Após aprovado o pagamento com crédito, o sistema pré-autoriza o valor, reservando-o automaticamente após 5 dias úteis ou até que o pedido seja faturado. Nesse momento ocorre a liquidação do valor na conta e os títulos são gerados.
-
-O fluxo segue o mesmo padrão dos cartões de crédito: modificações feitas no pedido durante o período de pré-autorização alteram o valor de crédito reservado. 
-
-As modificações feitas após a liquidação, ou seja, após a emissão dos títulos, atualizam os títulos já emitidos caso o valor diminua e emitem novos títulos caso o valor do pedido aumente. 
+Após o cliente realizar a compra utilizando o Customer Credit, o pagamento é aprovado como um crédito e a plataforma pré-autoriza o valor, reservando-o automaticamente após 5 dias úteis ou até que o pedido seja faturado. Nesse momento ocorre a liquidação do valor na conta e os títulos de pagamento são gerados.
 
-## Pontos de contato
+O fluxo no Customer Credit é similar ao de cartões de crédito em relação a modificações no pedido. Quando uma alteração de valor no pedido ocorre durante o período de pré-autorização, o valor do crédito é alterado.
 
-### Admin
-
-A interface do Customer Credit no Admin da VTEX fornece visibilidade completa do sistema: títulos, contas e configurações gerais. A interface também permite você buscar, filtrar e ordenar dados, além de importá-los e exportá-los. 
-
-### Checkout
-
-É pelo Checkout da VTEX que o usuário poderá fechar compras usando o Customer Credit. O sistema irá verificar automaticamente se o usuário já possui uma conta com crédito e, caso positivo, permitirá que ele se autentique para visualizar o crédito disponível e as opções de prazos e parcelamentos para fechar a compra.
-
-### Meus Créditos
-
-É a interface pela qual o seu cliente terá acesso às informações de sua conta. Ela é muito similar à página de Contas do Admin da VTEX. Nela o usuário enxerga seus limites disponíveis, títulos pagos e em aberto, além do histórico da conta.
+<div class="alert alert-warning">
+Se for necessário alterar  uma ordem para diminuir o seu valor após o período de liquidação (emissão de títulos), o sistema irá atualizar os títulos para o novo valor. Caso o valor do pedido seja aumentado, o sistema criará novos títulos.
+</div>
 
 ## Instalação e configuração
-Preparamos um guia detalhado para você [começar a usar o Customer Credit na sua loja](/pt/tracks/customer-credit-como-comecar). Acesse e ofereça crédito exclusivo para seus melhores clientes agora mesmo.
-
-Para maiores informações sobre as APIs do Customer Credit, acesse [Customer Credit API - Overview](https://developers.vtex.com/docs/api-reference/customer-credit-api).
-
+Para instalar e configurar o Customer Credit em sua loja, acesse a Track [Customer Credit - Como começar](https://help.vtex.com/pt/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
diff --git a/docs/tutorials/pt/customize-suiteshare.md b/docs/tutorials/pt/customize-suiteshare.md
index fd9dfa0ca..0094e43ee 100644
--- a/docs/tutorials/pt/customize-suiteshare.md
+++ b/docs/tutorials/pt/customize-suiteshare.md
@@ -17,15 +17,15 @@ subcategory: 4y4ylvqceE6vVqEF8IWZix
 
 Além de definir os textos do seu chat e/ou captura é possível também personalizar a aparência.  Para acessar essas configurações, acesse dentro do seu painel admin do **VTEX Assisted Sales (SuiteShare)** o campo **Configurações > minha conta**.
 
-![Personalizar 1](https://images.ctfassets.net/alneenqid6w5/5FaGHXk7TYQh3ksA1d3V2y/13db76bc19548fee364bc5e0446f8a71/Screenshot_2022-08-31_at_15-05-25_Personalizar.png)
+![Personalizar 1](//images.ctfassets.net/alneenqid6w5/5FaGHXk7TYQh3ksA1d3V2y/13db76bc19548fee364bc5e0446f8a71/Screenshot_2022-08-31_at_15-05-25_Personalizar.png)
 
 Clique em **“Aparência”**.
 
-![Personalizar 2](https://images.ctfassets.net/alneenqid6w5/5BXY8UssL3Ad0IGZImI894/0202e3d65872d3d586c2c4a2c4de4add/Screenshot_2022-08-31_at_15-05-32_Personalizar.png)
+![Personalizar 2](//images.ctfassets.net/alneenqid6w5/5BXY8UssL3Ad0IGZImI894/0202e3d65872d3d586c2c4a2c4de4add/Screenshot_2022-08-31_at_15-05-32_Personalizar.png)
 
 Nesta tela é possível editar o logo, cor e fundo.
 
-![Personalizar 3](https://images.ctfassets.net/alneenqid6w5/6AjaiWD8IaEXvtSQuDZ7Eq/6b862f5a8fe54cf15d40a77a49cb8941/Screenshot_2022-08-31_at_15-05-37_Personalizar.png)
+![Personalizar 3](//images.ctfassets.net/alneenqid6w5/6AjaiWD8IaEXvtSQuDZ7Eq/6b862f5a8fe54cf15d40a77a49cb8941/Screenshot_2022-08-31_at_15-05-37_Personalizar.png)
 
 Recomendamos que o logo seja enviado em PNG e em tamanhos quadrados, como por exemplo 1:1.
 
@@ -33,21 +33,21 @@ Defina a cor que será o seu chat, você pode enviar diretamente o código das c
 
 Escolha a cor do texto.
 
-![Personalizar 4](https://images.ctfassets.net/alneenqid6w5/1cpsT10zhmEKWF5WmhIPwh/92d609f5942746ddb489e9777957e48c/Screenshot_2022-08-31_at_15-05-41_Personalizar.png)
+![Personalizar 4](//images.ctfassets.net/alneenqid6w5/1cpsT10zhmEKWF5WmhIPwh/92d609f5942746ddb489e9777957e48c/Screenshot_2022-08-31_at_15-05-41_Personalizar.png)
 
 Selecione o tema desejado.
 
-![Personalizar 5](https://images.ctfassets.net/alneenqid6w5/4sKPJCYclbPfNahy7hWP9g/28815a7fc765486b54efa6f18579780a/Screenshot_2022-08-31_at_15-05-45_Personalizar.png)
+![Personalizar 5](//images.ctfassets.net/alneenqid6w5/4sKPJCYclbPfNahy7hWP9g/28815a7fc765486b54efa6f18579780a/Screenshot_2022-08-31_at_15-05-45_Personalizar.png)
 
 Pronto!
 
 Essas alterações estarão disponivéis nos [**formulários de captura**](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo).
 
-![Personalizar 6](https://images.ctfassets.net/alneenqid6w5/6plXqoT7agynflbxaU5PaS/9d5ea2cb5a58fb03f382a209acd0a239/Screenshot_2022-08-31_at_15-05-49_Personalizar.png)
+![Personalizar 6](//images.ctfassets.net/alneenqid6w5/6plXqoT7agynflbxaU5PaS/9d5ea2cb5a58fb03f382a209acd0a239/Screenshot_2022-08-31_at_15-05-49_Personalizar.png)
 
 E no [**seletivo**](\"http://help.suiteshare.com/support/solutions/articles/67000214752-seletivo\"). 
 
-![Personalizar 7](https://images.ctfassets.net/alneenqid6w5/MA1CvcFrwxcIfbJIY1YTz/d670011df1acae80ce75b174e8f863d2/Screenshot_2022-08-31_at_15-05-54_Personalizar.png)
+![Personalizar 7](//images.ctfassets.net/alneenqid6w5/MA1CvcFrwxcIfbJIY1YTz/d670011df1acae80ce75b174e8f863d2/Screenshot_2022-08-31_at_15-05-54_Personalizar.png)
 
 Não esqueça de clicar em "_**Salvar"**_.
 
diff --git a/docs/tutorials/pt/customizing-your-stores-typography.md b/docs/tutorials/pt/customizing-your-stores-typography.md
index c3f650c3f..6f2c84ca6 100644
--- a/docs/tutorials/pt/customizing-your-stores-typography.md
+++ b/docs/tutorials/pt/customizing-your-stores-typography.md
@@ -27,7 +27,7 @@ No Admin, você tem flexibilidade para personalizar a tipografia da sua loja de
 1. No Admin VTEX, acesse **Storefront > Styles (Estilos)**.
 2. Selecione o ícone kebab (três pontos).
 
-![Styles - Mais opções](https://images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/e6f569468bccb9c85c309acd4b9fb066/styles-two-pt.png)
+![Styles - Mais opções](//images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/e6f569468bccb9c85c309acd4b9fb066/styles-two-pt.png)
 
 3. Clique em **Edit (Editar) > Typography (Tipografia) > Font Family (Família da fonte)**.
 
@@ -51,7 +51,7 @@ Consulte a seção [Tokens de tipo](#type-tokens) para obter mais informações
 2. Selecione o ícone kebab (três pontos).
 3. Clique em **Edit (Editar) > Typography (Tipografia) > Type Tokens (Tokens de tipo)**.
 
-![Styles - Type tokens PT](https://images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/13e59fcc04d2034ff8e2c9928c165354/styles-three-pt.gif)
+![Styles - Type tokens PT](//images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/13e59fcc04d2034ff8e2c9928c165354/styles-three-pt.gif)
 
 4. Escolha o tipo de ficha que você deseja personalizar como, por exemplo, **Heading 1** (Cabeçalho 1), e clique nele.
 
diff --git a/docs/tutorials/pt/dashboards-overview.md b/docs/tutorials/pt/dashboards-overview.md
index b09db245e..657408354 100644
--- a/docs/tutorials/pt/dashboards-overview.md
+++ b/docs/tutorials/pt/dashboards-overview.md
@@ -3,8 +3,8 @@ title: 'Visão Geral Dashboards'
 id: 1yn2nZUoXtDO3teTEJsCNl
 status: PUBLISHED
 createdAt: 2023-03-29T21:16:46.179Z
-updatedAt: 2023-03-29T21:18:04.195Z
-publishedAt: 2023-03-29T21:18:04.195Z
+updatedAt: 2024-06-19T15:30:06.441Z
+publishedAt: 2024-06-19T15:30:06.441Z
 firstPublishedAt: 2023-03-29T21:18:04.195Z
 contentType: tutorial
 productTeam: Others
@@ -23,4 +23,3 @@ A seção inclui as seguintes páginas, já em seu Admin:
 
 - [Visão Geral](https://help.vtex.com/pt/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy): onde lojistas têm acesso às principais métricas que impactam a receita de suas lojas. Nesse painel, você pode acompanhar a evolução das suas vendas através dos recursos de análise de tendências de pedidos, taxa de conversão e gráficos de funil de vendas.  
 - [Performance de Vendas](https://help.vtex.com/pt/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp): um painel de controle para comércio unificado, ajudando lojas a ampliarem seu negócio e tomarem decisões com mais precisão.  
-- [Performance de páginas Web](https://help.vtex.com/pt/v4/docs/performance-de-paginas-web--7DeyhX8cGtG9PtAGkL8zvc): disponibiliza a ferramenta PageSpeed Insights do Google em seu Admin VTEX, assim, é possível monitorar o desempenho das URLs do seu ecommerce.   
diff --git a/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md b/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md
new file mode 100644
index 000000000..592ef2096
--- /dev/null
+++ b/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md
@@ -0,0 +1,53 @@
+---
+title: 'Dicionário VTEX Data Pipeline (Beta)'
+id: 69hMoE2woVw14nWR3ujVto
+status: PUBLISHED
+createdAt: 2024-02-01T18:51:29.281Z
+updatedAt: 2024-06-25T14:23:40.720Z
+publishedAt: 2024-06-25T14:23:40.720Z
+firstPublishedAt: 2024-05-27T19:26:59.681Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: dicionario-vtex-data-pipeline-beta
+locale: pt
+legacySlug: catalogo-vtex-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+<div class="alert alert-info">
+Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">Suporte</a>.
+</div>  
+
+O **VTEX Data Pipeline** é uma ferramenta acessível exclusivamente aos clientes VTEX, que deve ser utilizada para exploração e análise dos dados do ecommerce que atualmente estão disponíveis em nossos servidores. O **Data Pipeline** é um produto add-on da VTEX que integra dados do seu ecommerce, de maneira limpa e segura ao *data warehouse* e às ferramentas de BI de sua preferência.  
+
+## Segurança e privacidade  
+
+O **VTEX Data Pipeline** aprimora a segurança dos dados do seu ecommerce, estabelecendo uma conexão direta e segura do nosso *data warehouse* para a ferramenta da sua infraestrutura de dados. Esta abordagem elimina a necessidade de dependência de processos de ETL (Extrair, Transformar e Carregar) realizados por ferramentas de terceiros, proporcionando um controle direto e seguro sobre o fluxo de dados. Além disso, um aspecto fundamental da nossa solução é a remoção proativa de todos os dados pessoalmente identificáveis (PII) dos usuários presentes nas tabelas, garantindo as melhores práticas de proteção de dados.
+
+## O que é o dicionário de dados?  
+
+Neste dicionário você encontra todos os conjuntos de dados que o **VTEX Data Pipeline** disponibiliza, detalhados em uma seção dedicada, destacando suas características.  
+
+Em cada seção, serão fornecidas informações como:  
+
+- Características dos dados  
+    - Origem do dado   
+    - Disponibilidade para o cliente  
+    - Histórico  
+    - Menor intervalo de atualização possível   
+- Tabelas do conjunto   
+- Análises com o conjunto de dados  
+- Correlações com outros dados  
+
+## Conjunto de dados  
+
+Nas seções a seguir, entenda como os dados se relacionam com o seu negócio e qual a relevância para o seu projeto.
+Os conjuntos de dados disponíveis são os seguintes:
+
+- [Inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navegação](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Pagamentos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs) 
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Preços](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promoção](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/pt/data-entity.md b/docs/tutorials/pt/data-entity.md
new file mode 100644
index 000000000..452960b55
--- /dev/null
+++ b/docs/tutorials/pt/data-entity.md
@@ -0,0 +1,109 @@
+---
+title: 'Entidade de dados'
+id: tutorials_1265
+status: PUBLISHED
+createdAt: 2017-04-27T21:56:57.118Z
+updatedAt: 2024-06-21T21:12:23.798Z
+publishedAt: 2024-06-21T21:12:23.798Z
+firstPublishedAt: 2017-04-27T23:03:49.803Z
+contentType: tutorial
+productTeam: Master Data
+author: authors_3
+slug: entidade-de-dados
+locale: pt
+legacySlug: criando-entidade-de-dados
+subcategory: 1l3IVVYwrrG5YOtdt7R2SN
+---
+
+Entidade de dados é uma representação de um conjunto de informações sobre um determinado conceito. Toda entidade possui campos, que são as informações que formam as entidades.
+
+Para exemplificar, imagine um sistema de controle de uma biblioteca. Esse sistema controla livros que podem ser alugados por clientes. Então, percebemos que esses 3 conceitos (livro, cliente, aluguel) são entidades que possuem informações sobre cada uma delas. Entidade de dados, portanto, é um grupo de informações sobre determinado conceito.
+
+![data-entity-pt](//images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/82f3ea4c99a28baa362e8698f24dc924/data-entity-pt.png)
+
+Com esses conceitos, é possível configurar os mais diversos cenários de controle de dados pelo Master Data. Por padrão, são inseridas as seguintes entidades de dados: Cliente, Endereço, Stores etc. É possível criar quantas mais entidades de dados desejar, possibilitando um ambiente personalizado, voltado às necessidade de cada loja.
+
+<div class="alert alert-warning">
+<p>Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:</p>
+    <ul>
+        <li><a href="https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versoes-disponiveis">Características das versões do Master Data</a></li>
+        <li><a href="https://developers.vtex.com/docs/guides/master-data-v2-basics">Master Data v2</a></li>
+    </ul>
+</div>
+
+## Tipos de dados
+
+A entidade de dados é composta por campos que, por sua vez, têm um tipo. Esse tipo identifica quais as características das informações que serão armazenadas no campo e realiza validações, filtros e cálculos de acordo com o valor selecionado.
+
+Na criação de um campo, são exibidos os tipos listados abaixo:
+
+| Tipo de campo | Descrição |
+| - | - |
+| **Auto Increment** | Armazena números inteiros e é incrementado automaticamente, ou seja, a cada novo registro, esse campo recebe o valor do registro anterior + 1. |
+| **Boolean** | Armazena a informação de verdadeiro ou falso, ou seja, sempre estará preenchido como `true` (verdadeiro) ou `false` (falso). |
+| **CEP** | Armazena um CEP. |
+| **CPF / CNPJ** | Armazena informações de CPF e CNPJ. |
+| **Currency** |  Armazena informações no formato de moeda. |
+| **Date** |  Armazena informações sobre data. |
+| **Date and Time** |  Armazena data e hora. |
+| **Decimal** |  Armazena números com a parte fracionária sempre configurada para 2. Ou seja, este campo armazena sempre 2 dígitos como decimais do valor inserido. |
+| **Email** |  Armazena um email. |
+| **File** |  Armazena um arquivo. O tamanho limite a ser aceito pode ser definido nas configurações do campo, acessadas a partir do botão com símbolo de engrenagem <i class="fas fa-cog"></i>. |
+| **Integer** |  Armazena números inteiros, ou seja, números sem a parte fracionária. Armazena os números inteiros entre `-2147483648` e `2147483647`. |
+| **Long** | É o mesmo tipo que **Integer**, porém, com possibilidade de armazenar mais números. Armazena de `-2⁶³` a `2⁶³-1`. |
+| **Percent** | Armazena informações em percentual. |
+| **Phone** |  Armazena informações no formato de um número de telefone. |
+| **Relationship** | Cria um relacionamento com outra entidade. Como relacionamento, entende-se a informação de uma entidade sendo exibida em outra. Por exemplo, em uma biblioteca, desejamos que o nome do **Cliente** aparecesse no registro de **Aluguel**.<br><br>Para isso, seria necessário fazer um relacionamento entre **Aluguel** e **Cliente**, usando o campo **Nome** Cadastrado em **Aluguel**. Então, no tipo **Relationship**, dentro da configuração, você precisaria selecionar o campo que deseja exibir (no caso, **Cliente**) para selecionar também o campo **Nome**. |
+| **Score2** | Campo composto por chave, valor e validade. Exemplo: uma possibilidade de uso é para controle de compra por cliente, guardando quanto o cliente comprou e quantas compras foram feitas. Este campo precisa ser preenchido por meio do endpoint [Update scores](https://developers.vtex.com/docs/api-reference/masterdata-api#put-/api/dataentities/-acronym-/documents/-id-/score) ou do endpoint [Update score by field](https://developers.vtex.com/docs/api-reference/masterdata-api#put-/api/dataentities/-acronym-/documents/-id-/score/-field-name-) da [Master Data API v1](https://developers.vtex.com/docs/api-reference/masterdata-api). |
+| **Text** | Armazena números, letras e caracteres especiais. Neste caso, não existe limitação de caracteres. |
+| **Time** |  Armazena informações de horário. |
+| **URL** |  Armazena uma URL. |
+| **User Login** | Seleciona automaticamente o usuário logado. É utilizado para cenários em que se deseja registrar o email do usuário que realizar alguma ação em um registro da entidade. |
+| **Varchar 10** |  Armazena números, letras e caracteres especiais. Neste caso, limita o número de caracteres em 10. |
+| **Varchar 100** |  Armazena números, letras e caracteres especiais. Neste caso, limita o número de caracteres em 100. |
+| **Varchar 50** |  Armazena números, letras e caracteres especiais. Neste caso, limita o número de caracteres em 50. |
+| **Varchar 750** |  Armazena números, letras e caracteres especiais. Neste caso, limita o número de caracteres em 750. |
+
+## Criar entidade de dados
+
+Siga o passo a passo abaixo para configurar uma nova entidade de dados.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
+2. No Master Data, clique em **Aplicações** > **Configurações avançadas** > **Estrutura de dados.**
+3. Clique na aba **Entidade de dados**.
+4. Clique no botão `Adicionar`.
+5. Preencha o campo **Acrônimo** com 2 letras que identifiquem a entidade de dados. Essas letras serão as iniciais do campo identificador do registro. Exemplo: Acrônimo SP, identificador SP-0001.
+6. Preencha o **Nome** da entidade de dados que deseja criar.
+7. Selecione o tipo de chave primária, que pode ser uma das seguintes opções:
+
+   - **GUID**: é uma sequência de números e caracteres que não se repetem, identificando um registro.
+   - **A chave primária será informada pelo cliente através do atributo "id"**: não cria automaticamente um campo identificador, este campo deve ser criado manualmente e deve ser dado o nome de **id**.
+8. Se for preciso consultar os registros sem filtro e sem autenticação, marque a opção **Permitir consultar todos os registros sem filtro**. Atenção: esta configuração é crítica, porque permite a listagem de todos os registros da base via API.
+9.  Preencha a aba **Campos** com os campos que deseja incluir na nova entidade de dados, conforme os passos a seguir.
+10. Preencha a coluna **Nome** com o valor de identificação do campo. Não é permitido inserir espaço nem caracteres especiais. Exemplo: NomeDoCliente.
+11. Preencha a coluna **Nome de exibição** com o nome que será exibido no formulário. Exemplo: Nome do Cliente.
+12. Selecione o tipo do campo, de acordo com as opções descritas na seção [Tipos de dados](#tipos-de-dados).
+13. Clique na engrenagem <i class="fas fa-cog"></i> para abrir as opções de configuração do campo.
+14. Preencha as **Configurações gerais**:
+
+     - **É anulável?**: marque esta opção caso seja possível a criação ou edição de um registro com o campo em branco (nulo). Caso essa opção fique desmarcada, não será possível criar um registro com o campo sem algum valor.
+     - **Permitir a leitura sem credencial:** marque esta opção se for possível realizar a leitura dos dados do campo sem a necessidade de autenticação, utilizando a Master Data API.
+     - **Permitir editar sem credencial:** marque esta opção se for possível realizar a inserção de dados no campo sem a necessidade de autenticação, utilizando a Master Data API.
+     - **Permitir filtrar sem credencial:** marque esta opção se for possível realizar o filtro de dados do campo sem a necessidade de autenticação, utilizando a Master Data API.
+
+15. Preencha as **Configurações de busca e filtro**:
+
+    - **É pesquisável?**: se esse campo for utilizado para busca no formulário e por API.
+    - **É filtrável?:** se esse campo for utilizado para filtro no formulário e por API.
+16. Escreva a descrição do campo.
+17. Para inserir mais campos, clique no botão `Novo campo` e repita os passos 10 a 16.
+18. Ao final da definição de campos, clique no botão `Salvar` para concluir ou `Salvar e criar` para seguir para a criação de uma nova entidade de dados.
+
+    Você será conduzido(a) novamente para a aba **Entidade de dados**.
+
+19. Na linha da nova entidade criada, clique no botão de disquete <i class="fas fa-save"></i> para publicar a entidade de dados criada.
+20. Clique em `OK`.
+
+<div class="alert alert-info">
+    <p>Após a criação da entidade de dados, é necessário <a href="https://help.vtex.com/pt/tutorial/criando-formulario-no-master-data--tutorials_1047">criar o formulário para a inserção, alteração e exibição de dados no Master Data</a>.</p>
+</div>
diff --git a/docs/tutorials/pt/data-subject-rights.md b/docs/tutorials/pt/data-subject-rights.md
index 4661aaa75..3a9784c31 100644
--- a/docs/tutorials/pt/data-subject-rights.md
+++ b/docs/tutorials/pt/data-subject-rights.md
@@ -3,8 +3,8 @@ title: 'Direitos dos titulares de dados pessoais'
 id: 6imchxTx09icupKMbzHVIM
 status: PUBLISHED
 createdAt: 2023-04-26T18:56:45.938Z
-updatedAt: 2023-04-27T12:43:48.560Z
-publishedAt: 2023-04-27T12:43:48.560Z
+updatedAt: 2023-06-22T21:47:26.569Z
+publishedAt: 2023-06-22T21:47:26.569Z
 firstPublishedAt: 2023-04-26T19:50:54.254Z
 contentType: tutorial
 productTeam: Others
@@ -50,7 +50,7 @@ Para exportar dados do Master Data v1 pelo painel Admin, siga estes passos:
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
 2. Clique na aba **Aplicações.**
 3. Clique em visualizar (ícone da direita) correspondente à entidade de dados desejada.
-![visualizar button master data](https://images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
+![visualizar button master data](//images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
 4. Use o [filtro do Master Data v1](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) para filtrar apenas os dados referentes ao usuário desejado. Use o `email` ou `ID do usuário` como campo do filtro.
 5. Clique no botão `Exportar XLS`.
 6. Selecione a opção `Selecionar todos os campos`.
diff --git a/docs/tutorials/pt/database-maintenance-full-cleanup.md b/docs/tutorials/pt/database-maintenance-full-cleanup.md
index 2564bd5e5..e6aa21d84 100644
--- a/docs/tutorials/pt/database-maintenance-full-cleanup.md
+++ b/docs/tutorials/pt/database-maintenance-full-cleanup.md
@@ -3,8 +3,8 @@ title: 'Manutenção de Base (Full Cleanup)'
 id: 34P9LGs7BCIQK6acQom802
 status: PUBLISHED
 createdAt: 2018-02-07T14:32:22.879Z
-updatedAt: 2022-12-08T22:26:21.443Z
-publishedAt: 2022-12-08T22:26:21.443Z
+updatedAt: 2023-08-02T16:15:41.168Z
+publishedAt: 2023-08-02T16:15:41.168Z
 firstPublishedAt: 2018-02-07T16:44:48.971Z
 contentType: tutorial
 productTeam: Others
@@ -40,10 +40,6 @@ Estas são as operações disponíveis:
 
 - __Apagar Categorias, Marcas, Campos e Itens relacionados:__ ao apagar esses elementos, Categorias, Marcas e Campos, além dos seus itens relacionados, serão removidos de forma definitiva da sua loja. Para que a exclusão possa acontecer, é necessário apagar produtos e SKUs antes. 
 
-  <div class="alert alert-info">
-    <p>Para os casos em que for realizada a operação <b>Apagar Produtos/Skus e itens relacionados</b> ou <b>Apagar Categorias, Marcas, Campos e Itens relacionados</b> e a loja utilize o <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a>, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a> para realizar a manutenção total da base de dados.</p>
-  </div>
-
 - __Apagar Sellers e Itens relacionados:__ ao apagar esse elemento, seus sellers, além dos seus itens relacionados, serão removidos de forma definitiva da sua loja.
 
 - __Agendar reindexação Completa:__ ao reindexar a base, você entra em uma fila para iniciar o processo de indexação dos seus produtos. Os produtos da loja continuam à venda durante o processo de indexação. Eles apenas entram em uma fila para atualização de dados e seguem disponíveis no site para venda. Após clicar em __Reindexar Base__, o processo é iniciado automaticamente.
diff --git a/docs/tutorials/pt/declining-order-cancelation.md b/docs/tutorials/pt/declining-order-cancelation.md
new file mode 100644
index 000000000..2117ec66c
--- /dev/null
+++ b/docs/tutorials/pt/declining-order-cancelation.md
@@ -0,0 +1,88 @@
+---
+title: 'Recusar solicitação de cancelamento do pedido'
+id: F2n0h1TeQ5td540Gjyff4
+status: PUBLISHED
+createdAt: 2023-09-21T02:29:56.663Z
+updatedAt: 2024-04-01T15:47:27.833Z
+publishedAt: 2024-04-01T15:47:27.833Z
+firstPublishedAt: 2023-09-21T16:08:07.567Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: recusar-solicitacao-de-cancelamento-do-pedido
+locale: pt
+legacySlug: negacao-de-cancelamento-de-pedido
+subcategory: 2t00bBkcAwIkgSCGKsMOwY
+---
+
+Há muitos cenários em que o cancelamento de um pedido é necessário, seja pelo seller, marketplace ou cliente. No entanto, em alguns casos o cancelamento de um pedido acarreta em uma perda financeira significativa para o seller, por isso ele pode recusar uma solicitação de cancelamento do pedido.
+
+O fluxo de pedidos tem uma[ janela para cancelamento](https://help.vtex.com/pt/tutorial/order-flow-and-status--tutorials_196) (carência) na qual o cliente pode cancelar automaticamente um pedido. Com exceção desse período, o seller pode recusar uma solicitação de cancelamento do pedido, independente se ela foi realizada pelo cliente ou pelo marketplace. 
+
+> **Exemplo:** um seller vende produtos personalizáveis em um marketplace.  Porém, depois de comprar um item e uma vez que o período de cancelamento tenha terminado, o cliente decide cancelar o pedido entrando em contato com o marketplace. Se o marketplace cancelar o pedido, o seller terá uma perda financeira, pois um produto personalizável dificilmente poderá ser vendido a outro cliente, por isso o seller decide recusar a solicitação de cancelamento.
+
+Para conferir nosso conteúdo para desenvolvedores, veja [Order canceling improvements](https://developers.vtex.com/docs/guides/order-canceling-improvements).
+
+<div class = "alert alert-info">
+Neste artigo, os termos marketplace e seller se referem ao <a href="https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-um-marketplace-vtex">marketplace VTEX</a> e ao <a href="https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#sendo-seller-vtex">seller VTEX</a>. A funcionalidade de recusar solicitação de cancelamento não está disponível para sellers e marketplaces externos.
+</div>
+
+<div class = "alert alert-warning">
+Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
+</div>
+
+## Diagrama de cancelamento de pedido recusado
+A imagem a seguir mostra o fluxo de recusa da solicitação de cancelamento de um pedido após a janela para cancelamento:
+
+![order cancel diagram](//images.ctfassets.net/alneenqid6w5/6cGkrOT0G5sEeA3VaHKm4e/8f44049006390f2ef6a699cac00bd9d0/cancel_api_improvements_help_center_PT.png)
+
+Segue a descrição de cada etapa:
+
+1. O cliente entra em contato com o marketplace para cancelar um pedido ou o faz através da [Minha Conta](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
+2. O marketplace envia uma solicitação de cancelamento ao seller. Nesta etapa, o [status do pedido](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) para o marketplace é `aguardando decisão do seller`. 
+3. Se o pedido estiver dentro da janela para cancelamento, ele será cancelado automaticamente, seguindo o comportamento padrão da plataforma. As próximas etapas se aplicam quando a janela para cancelamento termina.
+4. O seller recebe a solicitação de cancelamento do pedido e decide se vai aceitá-la ou não. As próximas etapas se aplicam quando o seller decide não cancelar o pedido.
+
+  <div class="alert alert-danger">
+Para recusar uma solicitação de cancelamento do pedido, o status do pedido para o marketplace e para o seller deve ser o seguinte:
+<ul>
+<li><b>Status do marketplace:</b> Aguardando decisão do seller.</li>
+<li><b>Status do seller:</b> Cancelamento solicitado.</li>
+</ul>
+</div>
+
+5. O seller recusa o cancelamento do pedido e notifica o marketplace.
+6. Depois que o marketplace recebe a solicitação recusada, o pedido progride no fluxo de pedidos.
+
+## Recusar uma solicitação de cancelamento do pedido
+
+A solicitação de cancelamento de um pedido pode ser feita pelo marketplace ou pelo cliente através da [Minha conta](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh). Quando feita diretamente pela **Minha conta,** o cliente recebe uma mensagem de confirmação de que a solicitação foi enviada com sucesso. 
+
+Depois disso, o pedido permanecerá com o [status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) de `cancelamento solicitado` para o marketplace e `aguardando decisão do seller` para o seller até que ele aceite ou não a solicitação. 
+
+<div class="alert alert-warning">
+Se, dentro de 30 dias, o seller não fizer nada em relação à solicitação de cancelamento do pedido, o pedido será cancelado automaticamente pela plataforma da VTEX.
+</div>
+
+Para recusar uma solicitação de cancelamento do pedido pelo Admin VTEX, siga os passos a seguir:
+
+1. No Admin VTEX, acesse **Pedidos > Todos os pedidos** ou digite [Todos os pedidos](https://help.vtex.com/en/tutorial/all-orders--2QTduKHAJMFIZ3BAsi6Pi) na barra de busca no topo da página.
+2. Selecione o pedido desejado para acessar a página [Detalhes do pedido](https://help.vtex.com/en/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl).
+3. Na parte superior da página, clique em Recusar. 
+
+  ![deny cancel request](//images.ctfassets.net/alneenqid6w5/53kKd5oNkEjeziq9XR4yvO/04d25b8c3cf508d489ca53687d2187c7/deny_cancel_request_PT.png)
+
+4. Preencha o pop-up **Solicitação de cancelamento** com o motivo da recusa da solicitação de cancelamento do pedido.
+
+  ![deny_cancel_request_reason_PT_v2](//images.ctfassets.net/alneenqid6w5/2j1DgDKBaWJFMeVfuxfwYL/08eae24f54f83caa4d8449a3dd465d31/deny_cancel_request_reason_PT_v2.png)
+
+  <div class="alert alert-warning">
+Lembre-se de que a mensagem contida nesse campo poderá ser exibida ao cliente pela <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha conta</a> ou enviada pelo marketplace.
+</div>
+
+5. Clique em `Recusar solicitação`.
+
+Em seguida, a solicitação de cancelamento do pedido é recusada e o pedido progride no fluxo para os seguintes status:
+
+- **Para o markatplace:** `Pagamento aprovado`.
+- **Para o seller:** `Pronto para manuseio` ou `Preparando entrega`, dependendo do status anterior à solicitação de cancelamento.
diff --git a/docs/tutorials/pt/defining-mandatory-fields-in-master-data-v1-forms.md b/docs/tutorials/pt/defining-mandatory-fields-in-master-data-v1-forms.md
new file mode 100644
index 000000000..f01518feb
--- /dev/null
+++ b/docs/tutorials/pt/defining-mandatory-fields-in-master-data-v1-forms.md
@@ -0,0 +1,30 @@
+---
+title: 'Definir campos obrigatórios em formulários do Master Data v1'
+id: 3ufvQPc02Aybg7K1r1HADV
+status: PUBLISHED
+createdAt: 2022-10-17T19:47:22.675Z
+updatedAt: 2024-07-04T13:15:32.435Z
+publishedAt: 2024-07-04T13:15:32.435Z
+firstPublishedAt: 2022-10-17T19:50:55.489Z
+contentType: tutorial
+productTeam: Master Data
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: definir-campos-obrigatorios-em-formularios-do-master-data-v1
+locale: pt
+legacySlug: nao-consigo-editar-um-campo-obrigatorio-do-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+Para alterar os campos que aparecem como obrigatórios no __Profile System__ do Master Data v1, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Certifique-se que está na aba __Aplicações__.
+3. Clique na engrenagem <i class="fas fa-cog"></i> em __Profile System__.
+4. Clique no ícone de edição <i class="far fa-edit"></i> ao lado do formulário que deseja configurar.
+5. Clique em __Esquemas de layout__.
+6. Clique no ícone de edição <i class="far fa-edit"></i> na linha do campo que deseja configurar.
+7. Em __Configurações avançadas do campo__, selecione __Campo obrigatório do formulário__.
+8. Clique em `OK`.
+9. Clique em `Salvar`.
+
+A opção pode ser alterada sempre que necessário.
diff --git a/docs/tutorials/pt/defining-window-displays.md b/docs/tutorials/pt/defining-window-displays.md
index 66497e19d..4d3492627 100644
--- a/docs/tutorials/pt/defining-window-displays.md
+++ b/docs/tutorials/pt/defining-window-displays.md
@@ -27,26 +27,26 @@ Realizadas as devidas definições, o vínculo da coleção com a vitrine é fei
 
 No exemplo abaixo, iremos definir a vitrine apresentada na Home, sendo assim, deve-se realizar a alteração no seguinte layout:
 
-![cms_layout_home ](https://images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
+![cms_layout_home ](//images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
 
 No layout selecionado, adicione o controle correspondente à vitrine onde deseja exibir a coleção clicando em **Add object**.
 Após selecionar o tipo de controle desejado, defina seu nome e clique em **Adicionar**.
 
 __Não se esqueça de salvar as configurações feitas para que seja possível posteriormente editar o controle criado.__
 
-![save settings cms](https://images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
+![save settings cms](//images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
 
 ### Edição do controle
 
 Para editar seus controles, clique no **símbolo de lápis**, conforme mostra a imagem exemplo abaixo: 
 
-![banner_edit_cms](https://images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
+![banner_edit_cms](//images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
 
 Ao editar o controle é necessário adicionar seus conteúdos, que representam cada conjunto de itens que serão exibidos.
 Para isso, clique em **Add content**
 
-![cadastro_conteudo_cms ](https://images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
-![cadastro_conteudo_cms 2](https://images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
+![cadastro_conteudo_cms ](//images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
+![cadastro_conteudo_cms 2](//images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
 
 - **"Adicionar arquivo":** para selecionar a coleção que será exibida nesse conteúdo. 
 - **Partner / Campaign / Source:**  define a exibição desse conteúdo caso o visitante possua alguma UTM correspondente em sua URL de origem. 
@@ -62,7 +62,7 @@ Deve-se marcar a opção **Active Content** e clicar em **Add content list**, sa
 
 Se caso depois de salvo o conteúdo for necessário editá-lo, basta clicar no segundo simbolo de lápis conforme mostra a imagem abaixo:
 
-![edit_content_cms](https://images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
+![edit_content_cms](//images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
 
 Deve-se realizar as mudanças desejadas, clicar em **Update Content List** e salvar todas as configurações feitas clicando em **Save Settings** depois. 
 
diff --git a/docs/tutorials/pt/deleting-a-category.md b/docs/tutorials/pt/deleting-a-category.md
index 8fa3f722f..e7f8f994a 100644
--- a/docs/tutorials/pt/deleting-a-category.md
+++ b/docs/tutorials/pt/deleting-a-category.md
@@ -26,7 +26,7 @@ Para que uma categoria não apareça para os clientes da loja, você pode torná
 3. Clique na categoria que você deseja inativar.
 4. Clique no botão `Ações`.
 5. Clique em `Alterar`.
-6. Desmarcar o campo __Ativo | Categoria está ativa no site__, conforme a imagem abaixo: ![img inativarcategoria PT](https://images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/c13fcfdbd38d3355b8541fff3f215890/img_inativarcategoria_PT.png)
+6. Desmarcar o campo __Ativo | Categoria está ativa no site__, conforme a imagem abaixo: ![img inativarcategoria PT](//images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/c13fcfdbd38d3355b8541fff3f215890/img_inativarcategoria_PT.png)
 7. Clique em `Salvar`.
 
 ## Apagar todas as categorias
diff --git a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
index f27cdbe3d..f1cbac289 100644
--- a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
+++ b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Entregas Correios'
 id: 5CZRA0lq60EecmwZpsjvfq
 status: PUBLISHED
 createdAt: 2022-03-04T13:12:38.617Z
-updatedAt: 2023-06-09T12:56:36.259Z
-publishedAt: 2023-06-09T12:56:36.259Z
+updatedAt: 2024-03-04T21:51:37.046Z
+publishedAt: 2024-03-04T21:51:37.046Z
 firstPublishedAt: 2022-03-04T13:17:13.380Z
 contentType: tutorial
 productTeam: Others
@@ -15,8 +15,12 @@ legacySlug: entregas-correios-vtex-log
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
+<div class="alert alert-info">
+Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>.
+</div>
+
 <div class="alert alert-warning">
-<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX dos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a></li><li><a href="https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92">Painel VTEX Shipping Network</a></li><li>Entregas Correios</li></ul></p>
+<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a></li><li><a href="https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92">Painel VTEX Shipping Network</a></li><li>Entregas Correios</li></ul></p>
 </div>
 
 **Entregas Correios** é a funcionalidade do [VTEX Shipping Network](https://vtex.com/br-pt/log/) que permite ao lojista acompanhar as informações e o andamento de pacotes postados nos [Correios](https://www.correios.com.br/). A solução permite solicitar um Pedido de Informação (PI) para entregas que estão atrasadas, extraviadas ou foram feitas indevidamente.
@@ -37,14 +41,14 @@ Além disso, ao final do artigo você vai encontrar informações sobre:
 * Serviço de Logística Reversa dos Correios
 
 <div class = "alert alert-info">
-Para imprimir etiquetas dos pacotes e notificar os Correios para realizar a coleta dos pacotes, no Admin VTEX, utilize a ferramenta <a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs"><b>Pronto para envio</b></a>. Você também pode fazer isso por API. Saiba  mais na nossa documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration">VTEX Shipping Network Labels Integration</a>.
+Para imprimir etiquetas dos pacotes no Admin VTEX, utilize a ferramenta <a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs"><b>Pronto para envio</b></a>. Você também pode fazer isso por API. Saiba  mais na nossa documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration">VTEX Shipping Network Labels Integration</a>.
 </div>
 
 ## Informações dos Pedidos
 
 No Admin VTEX, em **Envio > Entregas Correios**, a página **Informações dos Pedidos** apresenta uma listagem de todos os pacotes postados. Na lista, é possível acompanhar as seguintes informações:
 
-![entregas_correios_interface_PT](https://images.ctfassets.net/alneenqid6w5/6yRZTRg0D2HkJC5TeVLKSx/12386242428176b32fdfc8e7e6719ff8/entregas_correios_interface_PT.png)
+![order_information_shipping_network_PT](//images.ctfassets.net/alneenqid6w5/2B9Ofd5hFwPkSxl31szyzU/d348694f06824d1e46b995bc712406af/order_information_shipping_network_PT.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
     <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
@@ -131,7 +135,7 @@ Ainda na página **Informações dos Pedidos,** você pode:
 
 Para visualizar mais informações sobre os pacotes de um pedido enviado clique no menu <i class="fas fa-ellipsis-v"></i> na última coluna da lista, e então clique em <i class="fas fa-eye"></i> `Detalhes do pedido`.
 
-![entregas_correios_detalhes_pedidos_PT](https://images.ctfassets.net/alneenqid6w5/3vtixaxWaubVOeLuueXgMI/ad5ca210783876124a205ee551e41c8f/entregas_correios_detalhes_pedidos_PT.png)
+![entregas_correios_detalhes_pedidos_PT](//images.ctfassets.net/alneenqid6w5/3vtixaxWaubVOeLuueXgMI/ad5ca210783876124a205ee551e41c8f/entregas_correios_detalhes_pedidos_PT.png)
 
 Na nova página, você pode realizar as seguintes ações: 
 
diff --git a/docs/tutorials/pt/detaching-skus-by-specification.md b/docs/tutorials/pt/detaching-skus-by-specification.md
new file mode 100644
index 000000000..5736c0b62
--- /dev/null
+++ b/docs/tutorials/pt/detaching-skus-by-specification.md
@@ -0,0 +1,35 @@
+---
+title: 'Separar SKUs por especificação'
+id: 2q34xCKFuob941cOmz9Fx
+status: PUBLISHED
+createdAt: 2024-06-27T16:45:42.418Z
+updatedAt: 2024-06-27T16:47:01.429Z
+publishedAt: 2024-06-27T16:47:01.429Z
+firstPublishedAt: 2024-06-27T16:47:01.429Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: separar-skus-por-especificacao
+locale: pt
+legacySlug: separar-skus-por-especificacao
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Uma das funcionalidades do VTEX Intelligent Search é a **separação de SKUs por especificação**. Esse recurso permite que o lojista determine os diferentes SKUs que serão exibidos no resultado de busca.
+
+Antes, apenas os produtos, sem nenhuma distinção entre SKUs, eram exibidos no resultado de busca. Por conta disso, era necessário cadastrar cada SKU como um produto único para ser exibido separadamente no resultado de busca.
+
+Agora não é preciso fazer nenhuma alteração no Catálogo para que os SKUs sejam exibidos nos resultados de busca. No Admin, basta [configurar as especificações do SKU que deseja exibir na pesquisa](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
+
+Essa ferramenta é indicada, principalmente, para lojas de vestuários, pois é possível exibir os produtos por cor ou material.
+
+A seguir, confira um exemplo de separação de SKUs por cor. Na imagem abaixo, a sandália em destaque apresenta duas cores diferentes no resultado da pesquisa:
+
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+
+<div class="alert alert-info"><p>
+Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.</p></div>
+
+## Configuração
+Para configurar quais atributos serão usados para separar os SKUs, acesse nosso artigo de [Configurações da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
+
diff --git a/docs/tutorials/pt/determine-the-minimum-number-of-items-in-a-cart.md b/docs/tutorials/pt/determine-the-minimum-number-of-items-in-a-cart.md
index 716ab48a4..4aaa59c77 100644
--- a/docs/tutorials/pt/determine-the-minimum-number-of-items-in-a-cart.md
+++ b/docs/tutorials/pt/determine-the-minimum-number-of-items-in-a-cart.md
@@ -1,10 +1,10 @@
 ---
 title: 'É possível determinar o mínimo de itens em um carrinho?'
 id: 3rhoZXYon6aaGqusgOwukQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:41.366Z
-updatedAt: 2023-03-30T15:55:10.926Z
-publishedAt: 2023-03-30T15:55:10.926Z
+updatedAt: 2024-02-05T18:20:53.788Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:19.953Z
 contentType: tutorial
 productTeam: Shopping
@@ -12,16 +12,15 @@ author: 7FpKZ0rc6k4WqeymES80cw
 slug: e-possivel-determinar-o-minimo-de-itens-em-um-carrinho
 locale: pt
 legacySlug: e-possivel-determinar-o-minimo-de-itens-em-um-carrinho
-subcategory: 3tDGibM2tqMyqIyukqmmMw
+subcategory: 
 ---
 
-Sim. Por padrão, a quantidade mínima de itens no carrinho é de 1 item. No entanto, é possível alterar esse valor e especificar o número que a loja entender ser o ideal para o seu negócio.
+Por padrão, a quantidade mínima de itens no carrinho é de 1 item. Entretanto, é possível alterar esse valor e especificar o número que a loja entender ser o ideal para o seu negócio. 
 
-Se você alterar o número de 1 *(default)* para 2, isso irá impedir que o cliente feche a compra sem que esteja com, no mínimo, 2 itens no carrinho.
+Por exemplo, se você alterar o número de 1 *(default)* para 2, isso irá impedir que o cliente conclua a compra sem que tenha adicionado no mínimo 2 itens no carrinho.
 
-__Para alterar esse número, siga os passos abaixo:__
+Para alterar a quantidade mínima de items no carrinho, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Aplicativos** > **Afiliados** > **Gerenciamento de pedidos**, ou digite **Gerenciamento de pedidos** na barra de busca no topo da página.
-2. Clique em __Configurações__.
-3. Ajuste o valor do campo __Quantidade mínima de itens no carrinho__
-4. Clique no botão __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pedidos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Gerais__, seção __Carrinho__, ajuste o valor do campo __Quantidade mínima de itens no carrinho__ conforme desejado.
+3. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/direct-migration-magazine-luiza.md b/docs/tutorials/pt/direct-migration-magazine-luiza.md
new file mode 100644
index 000000000..2d6202120
--- /dev/null
+++ b/docs/tutorials/pt/direct-migration-magazine-luiza.md
@@ -0,0 +1,87 @@
+---
+title: 'Migração Direta Magazine Luiza'
+id: 6QRyRfi16YMVdPesThw3AA
+status: PUBLISHED
+createdAt: 2024-05-31T19:52:31.191Z
+updatedAt: 2024-05-31T21:02:13.878Z
+publishedAt: 2024-05-31T21:02:13.878Z
+firstPublishedAt: 2024-05-31T20:07:32.221Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: migracao-direta-magazine-luiza
+locale: pt
+legacySlug: migracao-direta-magazine-luiza
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+A **Migração Direta Magazine Luiza** foi desenvolvida para facilitar o processo de migração para o seller que utiliza uma integradora terceira para disponibilizar seus produtos no Magazine Luiza marketplace e agora deseja disponibilizar seus produtos e receber os pedidos do marketplace pela plataforma VTEX. 
+
+Utilizando a **Migração Direta,** a conta do seller no marketplace é reaproveitada e neste caso a relevância de vendas do seller é mantida.  
+
+![Fluxo da migração](//images.ctfassets.net/alneenqid6w5/7GdLQ0HFfZXJ7mxvqGgNeO/26fc293e4cf1592347635841669433b5/Fluxo_de_funcionamento_integra__o.png)
+
+## Integrando a loja VTEX com o Magazine Luiza marketplace
+
+A **Migração Direta** é executada nas etapas de [O que o seller precisa fazer](#o-que-o-seller-precisa-fazer) e [Testes](#testes). 
+
+### O que o seller precisa fazer
+
+Veja abaixo quais são os passos a serem seguidos nesta etapa:
+
+1. O seller deve abrir um ticket pelo [Portal do seller do Magazine Luiza](https://id-b2b.magazineluiza.com.br/auth/realms/B2B/protocol/openid-connect/auth?client_id=platform-seller-shell&redirect_uri=https%3A%2F%2Fseller.magalu.com%2F&state=1985744a-615b-428f-8d32-d9d2b03edf30&response_mode=fragment&response_type=code&scope=openid&nonce=5e1f25ae-d3b3-4cdf-85fd-d18183d99334) informando que deseja migrar da integração **A** para a VTEX.  
+2. O seller deve abrir um ticket com o time [suporte da VTEX](https://help.vtex.com/pt/support) informando o interesse em realizar a **Migração Direta.**  
+3. Realizar o mapeamento dos [produtos e SKUs](https://help.vtex.com/pt/tutorial/qual-a-diferenca-entre-produto-e-sku--5yhABFDOpyiUcicce2W4CM) no seu catálogo VTEX.  
+Para realizar o mapeamento acesse no Admin VTEX **Catálogo > Todos os produtos.**  
+
+<div class=”alert alert-danger”>
+O código de referência do SKU na VTEX deve ser igual ao ID do SKU no Magazine Luiza e o código de referência do produto na VTEX também deve ser igual ao ID do produto no Magazine Luiza. <p> Sem esse mapeamento de equivalência, a migração não funcionará.</p>
+</div>
+
+4. [Criar uma política comercial](https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) para utilizar na integração com o Magazine Luiza. Essa política não deve ter produtos associados.  
+5. Ativar o conector do Magazine Luiza conforme a [documentação de integração](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y/3tZ4qVuMDDsC2jx2DCmjdA) e autenticar a conta.  
+6. No seller center do Magazine Luiza, o seller deve zerar o estoque de todos os produtos.  
+7. Ao finalizar os passos anteriores, o seller deve informar nos tickets com a VTEX e com o Magazine Luiza qual a data e horário que deseja realizar a migração.   
+
+<div class=”alert alert-warning”>
+Na data e horário acordado entre o seller e a VTEX, o processo de migração será iniciado e os pedidos que estão pendentes no Portal do seller Magazine Luiza serão segmentados. Todos os pedidos pendentes anteriores à data definida, ficam sob responsabilidade do seller para atualização manual no Portal do seller e os pedidos posteriores à data definida ficam sob responsabilidade da VTEX.
+</div>
+
+![Data de migração](//images.ctfassets.net/alneenqid6w5/3TcYO5vYXIMqRqpGoY2sWV/3f23ceeb4116f807b2b65e075d42fe85/Fluxo_de_pedidos_na_migra__o.png)
+
+Após informar o dia e horário desejado para realizar a integração, o seller deve aguardar o retorno da VTEX confirmando a finalização da migração para seguir aos [testes](#testes).
+
+<div class=”alert alert-warning”>
+Durante o período de migração pedidos podem ser duplicados, chegando na integradora anterior e na VTEX. O seller deve ficar atento à situação para tratar corretamente esses pedidos.
+</div>
+
+### Testes
+
+Quando o seller receber a confirmação de que a migração foi finalizada, é necessário realizar os testes indicados abaixo:
+
+- **Teste 1**
+
+1. Adicione apenas três produtos na política comercial vinculada à integração.
+2. Verifique se os produtos aparecem no marketplace.  
+
+- **Teste 2**
+
+1. Atualize os preços dos produtos adicionados à política comercial.  
+2. Verifique se as informações foram alteradas também no marketplace.  
+
+- **Teste 3**
+
+1. [Atualize o estoque](https://help.vtex.com/pt/tutorial/atualizacao-da-quantidade-de-itens-em-estoque--2MDwYV1COA6YuoiY22AyGo) dos produtos adicionados à política comercial.  
+2. Verifique se as informações foram alteradas também no marketplace.  
+
+- **Teste 4**
+
+1. Simule um pedido para um dos produtos presentes na política comercial.  
+2. Verifique se o pedido foi integrado corretamente ao módulo **Pedidos** na VTEX.  
+
+- **Teste 5**
+
+1. Faça a [Simulação de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144) para os produtos adicionados à política comercial.  
+
+Caso todos os testes sejam executados com sucesso, o seller deve adicionar os demais produtos à política comercial utilizada na integração para finalizar o processo.
+
diff --git a/docs/tutorials/pt/displaying-the-store-in-another-language.md b/docs/tutorials/pt/displaying-the-store-in-another-language.md
index e738cf3c9..2236f5405 100644
--- a/docs/tutorials/pt/displaying-the-store-in-another-language.md
+++ b/docs/tutorials/pt/displaying-the-store-in-another-language.md
@@ -17,7 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 Para que seu site seja exibido em outra língua, deve-se [criar uma nova política comercial](/pt/tutorial/configurando-a-politica-comercial-para-marketplace/) e atribuir a ela o idioma desejado no campo __Culture Info__.
 
-![exibição-loja-idioma-diferente pt](https://images.ctfassets.net/alneenqid6w5/7BeeKmilag6wYaKGMkWwMW/2dab353b989d38047b1c92f342d6c37d/exibi____o-loja-outra-l__ngua_pt.png)
+![exibição-loja-idioma-diferente pt](//images.ctfassets.net/alneenqid6w5/7BeeKmilag6wYaKGMkWwMW/2dab353b989d38047b1c92f342d6c37d/exibi____o-loja-outra-l__ngua_pt.png)
 
 
 Após a configuração na política comercial, será necessário um ajuste no front-end da loja para que a mudança de idioma ocorra e, com ela, a mudança de políticas comerciais. 
diff --git a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
new file mode 100644
index 000000000..9bfabf668
--- /dev/null
+++ b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -0,0 +1,85 @@
+---
+title: 'Exibir anúncios do VTEX Ad Network na sua loja (Beta)'
+id: 6gWgZrMLcS5FDFFdl5LETA
+status: CHANGED
+createdAt: 2024-04-23T18:51:12.785Z
+updatedAt: 2024-07-05T13:10:03.749Z
+publishedAt: 2024-07-05T13:05:44.686Z
+firstPublishedAt: 2024-04-23T19:13:52.053Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: exibir-anuncios-do-vtex-ad-network-na-sua-loja-beta
+locale: pt
+legacySlug: exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+Com [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), lojas VTEX podem disponibilizar espaço publicitário para que marcas promovam seus produtos na sua loja. Desta forma, a VTEX selecionará anúncios de produtos que já compõem o seu catálogo e sua loja receberá um valor por cada clique em anúncios na sua frente de loja.
+
+Para aderir ao VTEX Ad Network e exibir anúncios na sua loja, basta instalar o aplicativo VTEX Ad Network para lojas.
+
+<div class="alert alert-warning">
+Por ora, lojas VTEX podem disponibilizar inventário de anúncios apenas em frentes de loja que utilizam <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
+</div>
+
+## Acompanhar resultados
+
+Na tela inicial do aplicativo [VTEX Ad Network para lojas](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#lojas), você pode acompanhar os resultados de anúncios na sua loja.
+
+![vtex_ad_network_admin_PT](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/c479a1adcfce1ab838edfa17aeb6aca7/vtex_ad_network_admin.png)
+
+Na parte superior, estão dados agregados:
+
+- **Gasto total em anúncios:** valor gasto por marcas em anúncios exibidos na sua loja.
+- **Vendas de anúncios:** receita total das vendas provenientes de anúncios exibidos na sua loja.
+- **Receita:** valor total recebido pela sua loja devido a anúncios.
+
+Abaixo você encontra uma tabela com informações de cada uma das campanhas que foram ou que podem ser exibidas na sua loja:
+
+- **Duração:** duração da campanha até o momento.
+- **Impressões:** número de vezes em que anúncios foram impressos na página.
+- **Visualizações:** número de vezes em que anúncios foram de fato visualizados. O VTEX Ad Network considera uma visualização quando há uma impressão de anúncio e, se necessário, o usuário rola a página o suficiente para visualizar o anúncio.
+- **Cliques:** número de cliques em anúncios.
+- **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações. 
+- **Pedidos:** número de pedidos provenientes de cliques em anúncios.
+- **Unidades vendidas:** número de unidades de produtos vendidas a partir de anúncios daquela campanha.
+- **Vendas de anúncios:** receita total das vendas provenientes de anúncios exibidos na sua loja.
+- **ROAS:** retorno sobre investimento em publicidade daquela campanha na sua loja.
+- **Orçamento gasto:** orçamento da campanha gasto na sua loja.
+
+Você também pode usar os filtros disponíveis acima da tabela:
+
+- **Buscar campanha:** filtre campanhas pelo nome.
+- **Status:** selecione se deseja ver apenas campanhas ativas ou desativadas.
+- **Anunciante:** veja dados relativos às campanhas de um anunciante específico.
+
+### Visualizar mais detalhes por campanha e produto
+
+Na tabela da tela inicial do app [VTEX Ad Network para lojas](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#lojas), você também pode clicar na linha referente a uma das campanhas para ver dados mais específicos.
+
+![vtex_ad_network_details_PT](//images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/50caa424b0c867189369d8071e5afcf0/vtex_ad_network_details.png)
+
+- **Visualizações / Cliques:** Visualizações de anúncios e cliques em anúncios.
+- **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações.
+- **Orçamento gasto:** valor gasto até o momento.
+- **ROAS:** retorno do investimento em publicidade.
+- **Receita:** receita das vendas provenientes de anúncios.
+
+Abaixo dos dados agregados você encontra uma tabela com informações sobre o desempenho de cada produto naquela campanha:
+
+- **CPC:** custo por clique. É o valor pago pelo anunciante por cada clique em um anúncio.
+- **Impressões:** número de vezes em que anúncios foram impressos na página.
+- **Visualizações:** número de vezes em que anúncios foram de fato visualizados. VTEX Ad Network considera uma visualização quando há uma impressão de anúncio e, se necessário, o usuário rola a página o suficiente para visualizar o anúncio.
+- **Cliques:** número de cliques em anúncios.
+- **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações. 
+- **Pedidos:** número de pedidos provenientes de cliques em anúncios.
+- **Unidades vendidas:** número de unidades do produto vendidas a partir de anúncios desta campanha.
+- **Vendas de anúncios:** receita total de vendas daquele produto provenientes de anúncios.
+- **ROAS:** retorno sobre investimento em publicidade.
+- **Orçamento gasto:** orçamento da campanha gasto com aquele produto na sua loja.
+
diff --git a/docs/tutorials/pt/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md b/docs/tutorials/pt/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
new file mode 100644
index 000000000..fff83ee17
--- /dev/null
+++ b/docs/tutorials/pt/dpan-and-fpan-understanding-security-in-the-online-tokenized-payment-flow.md
@@ -0,0 +1,40 @@
+---
+title: 'DPAN e FPAN: entendendo a segurança no fluxo de pagamentos tokenizados online'
+id: 3RM7RvhKZ057wja5xVEOqb
+status: PUBLISHED
+createdAt: 2023-06-19T16:55:51.107Z
+updatedAt: 2023-06-26T13:27:44.965Z
+publishedAt: 2023-06-26T13:27:44.965Z
+firstPublishedAt: 2023-06-19T17:10:43.124Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: dpan-e-fpan-entendendo-a-seguranca-no-fluxo-de-pagamentos-tokenizados-online
+locale: pt
+legacySlug: dpan-e-fpan-entendendo-a-seguranca-no-fluxo-de-pagamentos-tokenizados-online
+subcategory: 
+---
+
+Token é a representação digital de um ativo físico que possui valor comercial. No contexto de pagamentos, tokenização é um procedimento de segurança que permite proteger informações sensíveis dos clientes durante transações com cartões de crédito, débito ou carteiras digitais, como Apple Pay, Google Pay e Samsung Pay.
+
+Primeiramente, é necessário compreender as seguintes informações relacionadas a um cartão:
+
+- **PAN (Primary Account Number)**: número físico impresso na frente ou verso de um cartão de débito ou crédito, utilizado para identificar o titular de uma conta e a sua instituição financeira emissora. Contém entre 14 e 19 dígitos.
+
+- **DPAN (Device Primary Account Number)**: versão tokenizada do PAN, utilizada em pagamentos móveis ou carteiras digitais. Este número é vinculado ao dispositivo móvel do usuário (smartphone, smartwatch, tablet) e à conta do titular do cartão. 
+
+- **FPAN (Funding Primary Account Number)**: identificação da conta na qual será debitado o valor pago em uma transação de pagamento. Utilizado exclusivamente quando a compra é realizada por meio de carteiras digitais ou serviços que permitam a escolha de mais de uma forma de pagamento ao mesmo tempo, por exemplo, diferentes cartões de crédito, débito ou contas bancárias.
+
+Veja abaixo, um exemplo de fluxo de pagamento utilizando tokens:
+
+1. O cliente insere as informações do cartão em um site, aplicativo ou máquina, ou utiliza uma carteira digital como forma de pagamento em uma compra.
+
+2. O provedor de pagamento ou sistema de carteira digital faz uma requisição à instituição financeira que emitiu o cartão, solicitando que seja criado um token para representar o PAN.
+
+3. O banco gera o token (DPAN) e encaminha para o provedor de pagamento ou sistema de carteira digital. O PAN permanece registrado apenas no sistema do banco.
+
+4. Durante o processamento da transação, o provedor de pagamento envia o DPAN ao banco, solicitando a autorização da transação. Quando aplicável, o FPAN também é gerado e encaminhado para autorização da transação.
+
+5. O banco verifica a relação entre o DPAN e PAN, e autoriza o pagamento. No caso onde o FPAN é utilizado, o banco também irá verificar se o FPAN é válido e se a fonte de financiamento (conta) possui saldo suficiente, antes de autorizar o pagamento. 
+
+6. A transação é concluída e o lojista recebe a confirmação de pagamento. O dado físico do cartão (PAN) não é compartilhado com o lojista ou terceiros, reduzindo o risco de acesso a fraudes.
diff --git a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
new file mode 100644
index 000000000..fd607701f
--- /dev/null
+++ b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
@@ -0,0 +1,78 @@
+---
+title: 'Relevância dinâmica no Intelligent Search (Beta)'
+id: rFaW7JPnBKNDBFzMxpBn8
+status: PUBLISHED
+createdAt: 2023-09-01T17:14:43.241Z
+updatedAt: 2024-01-05T17:24:55.378Z
+publishedAt: 2024-01-05T17:24:55.378Z
+firstPublishedAt: 2023-09-01T18:59:54.853Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: relevancia-dinamica-no-intelligent-search-beta
+locale: pt
+legacySlug: relevancia-dinamica-no-intelligent-search-beta
+subcategory: 23WdCYqmn2V2Z7SDlc14DF
+---
+
+<div class="alert alert-info">
+  <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
+  <p>Para os clientes selecionados, a funcionalidade está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É possível que taxas extras se apliquem futuramente.</p>
+</div>
+
+O Intelligent Search é uma solução de busca da plataforma VTEX. Ele apresenta resultados relevantes com base no catálogo desde a primeira interação do usuário com a loja, seja por meio da barra de busca, navegando pelas categorias, ou mesmo pelas vitrines de produtos. 
+
+A relevância é a funcionalidade que define a ordem dos produtos no resultado de busca. Essa configuração permite que você atribua pesos e priorize determinados critérios, como popularidade, data de lançamento do produto e participação em promoções. O Intelligent Search determina a relevância de cada produto pela combinação dos pesos e prioridades definidos por cada lojista.
+
+No Intelligent Search, existem duas formas de configurar a relevância da sua busca:
+
+* [Manual](#manual)
+* [Dinâmica](#dinamica)
+
+Apenas uma delas é aplicada à sua loja por vez e você pode [alterar o tipo de relevância](#alterar-o-tipo-de-relevancia) configurado na sua loja. Caso você altere a relevância manual para dinâmica, todas as regras manuais já cadastradas continuam salvas.
+
+<div class = "alert alert-info">
+A relevância manual é configurada como padrão da loja.
+</div>
+
+## Manual 
+
+A relevância manual é configurada pela distribuição dos pesos realizada na página de **Regras de relevância**. Para ativar a relevância manual, siga os passos a seguir:
+
+1. No Admin VTEX, acesse **Storefront > Intelligent Search >** **Regras de relevância**  ou digite **Regras de relevância** na barra de busca no topo da página.
+2. Selecione a opção **Relevância manual**.
+![relevancia-manual-pt](//images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/1a0116cc71d5df6ffff2d2ac21854736/image.png)
+3. Clique em `Salvar`.
+
+Para configurar a relevância manual, confira o artigo [Relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+## Dinâmica
+
+A relevância dinâmica é um recurso da VTEX que usa inteligência artificial para encontrar tendências no comportamento dos seus usuários. Com base na consulta e na posição do resultado em que eles clicam ou realizam um pedido. Ela pode melhorar os resultados de busca aumentando a relevância dos produtos que estão crescendo em popularidade. 
+
+Por exemplo, em uma página de novidades, a relevância dinâmica pode identificar que produtos mais recentes aumentam a conversão sem a necessidade de que o lojista configure.
+
+Ela também pode reposicionar os resultados que não são relevantes para seus usuários no contexto de uma busca específica.
+
+Para ativar a relevância dinâmica, siga os seguintes passos:
+
+1. No Admin VTEX, acesse **Storefront > Intelligent Search > Regras de relevância**  ou digite **Regras de relevância** na barra de busca no topo da página.
+2. Leia as informações sobre a Relevância Dinâmicas e clique em `Próximo`.
+3. Selecione a opção **Relevância Dinâmica**.
+![relevancia-dinamica-pt](//images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/325dfbf15ee811133ae0a12a89959b43/image.png)
+4. Clique em `Salvar`.
+5. Aguarde a barra de carregamento atingir 100%. Esse processo pode demorar algumas horas. Você receberá um email notificando que o carregamento foi finalizado.
+6. Clique em `Ativar`.
+
+## Alterar o tipo de relevância
+
+Para alterar o tipo de relevância, siga os passos abaixo:
+
+<div class = "alert alert-warning">
+Não recomendamos a troca constante do tipo de relevância utilizado pela sua loja. O sistema precisa de uma semana para se estabelecer.
+</div>
+
+1. No Admin VTEX, acesse **Storefront > Intelligent Search > Regras de relevância**  ou digite **Regras de relevância** na barra de busca no topo da página.
+2. Clique em `Alterar` .
+3. Escolha o tipo de relevância que deseja aplicar.
+4. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md b/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md
index f38f32837..511a34ffe 100644
--- a/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md
+++ b/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md
@@ -1,10 +1,10 @@
 ---
-title: 'Edite um campo obrigatório no Profile System do Master Data'
+title: 'Editar um campo obrigatório no Profile System do Master Data'
 id: 3Kat18isG7ZQptlLusUKnj
 status: PUBLISHED
 createdAt: 2019-03-29T14:18:37.284Z
-updatedAt: 2023-03-28T23:00:24.414Z
-publishedAt: 2023-03-28T23:00:24.414Z
+updatedAt: 2024-06-19T14:27:27.495Z
+publishedAt: 2024-06-19T14:27:27.495Z
 firstPublishedAt: 2019-03-29T15:48:22.604Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: edite-um-campo-obrigatorio-no-profile-system-do-master-data
 subcategory: 42hDtnYXHw5ExG6l19RP1l
 ---
 
-O Master Data é um módulo dentro da plataforma VTEX utilizado para guardar e organizar dados dos clientes. Veja como editar um campo, tornando-o obrigatório ou não, utilizando a funcionalidade Profile System.
+O Master Data é um módulo da plataforma VTEX usado para armazenar e organizar documentos. Descubra como tornar obrigatório um campo de formulário no Master Data nas instruções abaixo.
 
 <div class="alert alert-warning">
 Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
@@ -36,13 +36,13 @@ Master Data v2
 Para selecionar um campo de preenchimento que deseja tornar obrigatório, siga os passos abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. Certifique-se que está na aba Aplicações, dentro de __Links Rápidos__.
-3. Clique na __engrenagem__ em __Profile System__. ![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
-4. Clique no __lápis__ ao lado do item que deseja configurar. ![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
-5. Clique em __Schemas de Layout__.
-6. Na __Seção 1__, escolha o item do campo que deseja configurar.
-7. Em __Configurações avançadas do campo__, selecione __Campo obrigatório__ no formulário. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
-8. Clique em __ok__.
-
-Pronto. A partir de agora, as opções selecionadas precisarão, obrigatoriamente, serem preenchidas na loja. A opção também pode ser alterada sempre que desejado.
+2. Certifique-se que está na aba __Aplicações__.
+3. Clique no ícone de engrenagem <i class="fas fa-cog"></i> em __Profile System__.
+4. Clique no ícone de lápis <i class="fas fa-edit"></i> ao lado do item que deseja configurar.
+5. Clique em __Esquemas de Layout__.
+6. Em uma das seções do formulário, localize o campo que deseja configurar e clique em <i class="fas fa-edit"></i> ao lado dele para abrir as __Configurações avançadas do campo__.
+7. Em __Configurações avançadas do campo__, selecione __Campo obrigatório do formulário__.
+8. Clique em `OK`.
+9. Clique em `Salvar`.
 
+A partir de agora, as opções selecionadas serão obrigatórias no formulário. As configurações acima podem ser alteradas, se necessário.
diff --git a/docs/tutorials/pt/editing-my-data-suiteshare.md b/docs/tutorials/pt/editing-my-data-suiteshare.md
index 43705df6f..c2aae8e19 100644
--- a/docs/tutorials/pt/editing-my-data-suiteshare.md
+++ b/docs/tutorials/pt/editing-my-data-suiteshare.md
@@ -17,18 +17,18 @@ subcategory: 4y4ylvqceE6vVqEF8IWZix
 
 Para editar os dados de acesso, você deve acessar _**Configurações > Minha conta**_. 
 
-![Editar_dados_Suitshare_1](https://images.ctfassets.net/alneenqid6w5/7GjD9aAHEpWeLMULbgIlN7/7373e8bfedf32a7c6c1fa965872b80a5/Editar_dados_1.png)
+![Editar_dados_Suitshare_1](//images.ctfassets.net/alneenqid6w5/7GjD9aAHEpWeLMULbgIlN7/7373e8bfedf32a7c6c1fa965872b80a5/Editar_dados_1.png)
 
 Em **Profile**, edite informações como **Nome** e **Empresa**. 
 
-![Editar_dados_suitshare_2](https://images.ctfassets.net/alneenqid6w5/1IytrpGXxE40bEdQ6eSLtg/4560182def1d9a3ee7b26b66c709f5fe/Editar_dados_suitshare_2.png)
+![Editar_dados_suitshare_2](//images.ctfassets.net/alneenqid6w5/1IytrpGXxE40bEdQ6eSLtg/4560182def1d9a3ee7b26b66c709f5fe/Editar_dados_suitshare_2.png)
 
 Em **Password**, edite sua senha. 
 
-![Editar_dados_suitshare_3](https://images.ctfassets.net/alneenqid6w5/1qcocpgUcO5nj9wqeDUJDW/048ec22ead339bb22b4779a22cad5cfd/Editar_dados_suitshare_3.png)
+![Editar_dados_suitshare_3](//images.ctfassets.net/alneenqid6w5/1qcocpgUcO5nj9wqeDUJDW/048ec22ead339bb22b4779a22cad5cfd/Editar_dados_suitshare_3.png)
 
 Em **Email**, edite as informações do seu e-mail. 
 
-![Editar_dados_suitshare_4](https://images.ctfassets.net/alneenqid6w5/7aNcHeEQPJ8Di0VALzxVXx/341143302118e8a7fad2ef91b26ca817/Editar_dados_suitshare_4.png)
+![Editar_dados_suitshare_4](//images.ctfassets.net/alneenqid6w5/7aNcHeEQPJ8Di0VALzxVXx/341143302118e8a7fad2ef91b26ca817/Editar_dados_suitshare_4.png)
 
 Para saber mais sobre sua conta, entre em contato conosco.
diff --git a/docs/tutorials/pt/enable-checkout-v6.md b/docs/tutorials/pt/enable-checkout-v6.md
index 05e633c59..4c89689b0 100644
--- a/docs/tutorials/pt/enable-checkout-v6.md
+++ b/docs/tutorials/pt/enable-checkout-v6.md
@@ -28,7 +28,7 @@ Para atualizar o checkout da sua loja para a versão mais recente (Checkout v6),
 5. Clique em __Salvar__. 
 6. [Acesse sua loja em ambiente beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) e realize os ajustes de estilo necessários. O Checkout v6 possui novas classes _CSS_ que devem ser levadas em consideração para customização do estilo.
 
-![Checkoutv6_box](https://images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/a1d6c6ab5e38fd7398ebc47b7ae32aa1/CheckoutV6_box_PT.png)
+![Checkoutv6_box](//images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/a1d6c6ab5e38fd7398ebc47b7ae32aa1/CheckoutV6_box_PT.png)
 
 ## Ativar o Checkout v6 em Ambiente de Produção
 
@@ -42,7 +42,7 @@ Após realizar os ajustes necessários em Ambiente de Teste, você pode ativar o
 
 Após este passo, o Checkout v6 estará instalado na sua loja.
 
-![checkoutv6_box_2](https://images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/671c0ec19bac97c07c97f3276150c30d/CheckoutV6_box2_PT.png)
+![checkoutv6_box_2](//images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/671c0ec19bac97c07c97f3276150c30d/CheckoutV6_box2_PT.png)
 
 ## Como checar se o Checkout v6 foi instalado corretamente?
 
diff --git a/docs/tutorials/pt/enabling-2-factor-authentication-login.md b/docs/tutorials/pt/enabling-2-factor-authentication-login.md
index daa7efc46..a1eb82966 100644
--- a/docs/tutorials/pt/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/pt/enabling-2-factor-authentication-login.md
@@ -3,8 +3,8 @@ title: 'Habilitar login por autenticação de dois fatores'
 id: 4Ae1fcQi12g8u4SkQKCqWQ
 status: PUBLISHED
 createdAt: 2017-11-09T00:46:29.023Z
-updatedAt: 2023-02-08T14:28:53.895Z
-publishedAt: 2023-02-08T14:28:53.895Z
+updatedAt: 2024-03-12T17:52:28.500Z
+publishedAt: 2024-03-12T17:52:28.500Z
 firstPublishedAt: 2017-11-09T13:09:54.237Z
 contentType: tutorial
 productTeam: Identity
@@ -17,8 +17,6 @@ subcategory: 4sY1T2qdFehvVmC0tL5xW3
 
 A autenticação de 2 fatores (2FA) é um método de autenticação que aumenta muito a segurança do login em sua loja.
 
-![PT-LoginAdmin](https://images.ctfassets.net/alneenqid6w5/1h4cAGRpOe2lvonqlZZgSk/b6e23c451f8506fccad78dbc7667229b/PT-LoginAdmin.png)
-
 Isto porque, no momento do login, além de exigir o e-mail e a senha, o sistema exige uma chave de acesso (que, no caso da VTEX, pode ser um código enviado por SMS ou gerado por aplicativo).
 
 Como essa chave é gerada no momento do login e tem prazo de validade curto, torna-se quase impossível que alguém entre em sua loja usando seus dados sem autorização. Sem o 2FA, basta que alguém saiba seu e-mail e sua senha para ter amplo acesso à conta da sua loja.
@@ -36,7 +34,7 @@ Há duas opções de autenticação:
 - Por chave gerada por um __aplicativo__ de autenticação.
 - Por chave enviada por mensagem de telefone (__SMS__).
 
-![2FA - Select - PT](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
+![2FA - Select - PT](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
 
 <div class="alert alert-danger">
 Recomendamos fortemente que você <strong>escolha a opção de autenticação por aplicativo</strong>, uma vez que na autenticação por SMS você depende de que não haja falhas na operadora de telefonia. Pelo aplicativo, a chave de acesso estará sempre à disposição quando for necessária.
@@ -51,13 +49,13 @@ Se você configurou o 2FA por SMS e o código está demorando a chegar, provavel
 Para usar uma chave gerada por aplicativo de autenticação:
 
 1. Baixe o aplicativo __Google Authenticator__ ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)).
-  ![2FA - App Download - PT](https:https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/c0bc298cb4c870e271da368bb765e146/2FA_-_App_Download_-_PT.png)
+  ![2FA - App Download - PT](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/c0bc298cb4c870e271da368bb765e146/2FA_-_App_Download_-_PT.png)
 2. Use o aplicativo para ler o QR Code com a câmera do seu celular.
-![mfa código](https://images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/42671df78ec718b7121b8d75379cf951/mfa_qr_code_correction_pt.jpg)
+![mfa código](//images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/42671df78ec718b7121b8d75379cf951/mfa_qr_code_correction_pt.jpg)
 3. Sua conta da VTEX será adicionada ao aplicativo, com um código de 6 dígitos. Insira o código para concluir seu login.
 
   *O código do app é atualizado periodicamente. Não será necessário memorizá-lo, basta consultar o aplicativo sempre que precisar.*
-  ![2FA - App Insert Code - PT](https:https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/58da9e3065ebec81f1528554808eee56/2FA_-_App_Insert_Code_-_PT.png)
+  ![2FA - App Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/58da9e3065ebec81f1528554808eee56/2FA_-_App_Insert_Code_-_PT.png)
 
 <div class="alert alert-info">
 Se você fizer login usando e-mail e senha no mesmo computador, a chave de acesso será solicitada <strong>a cada 3 dias</strong>. Quando isso acontecer, basta consultar o código no aplicativo.
@@ -69,11 +67,11 @@ Para usar uma chave enviada por mensagem de texto:
 
 1. Insira seu número de celular para enviarmos o código por SMS - não se esqueça de colocar o código de país e área.
 
-  ![2FA - SMS Insert Phone - PT](https:https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/d57d2ea05bb88182ab5b9df700fdadb2/2FA_-_SMS_Insert_Phone_-_PT.png)
+  ![2FA - SMS Insert Phone - PT](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/d57d2ea05bb88182ab5b9df700fdadb2/2FA_-_SMS_Insert_Phone_-_PT.png)
 
 2. Você receberá uma mensagem de texto da VTEX no celular indicado. Insira a chave de 6 dígitos para concluir seu login.
 
-   ![2FA - SMS Insert Code - PT](https:https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/bf998e866456c232965f4bd845b65db1/2FA_-_SMS_Insert_Code_-_PT.png)
+   ![2FA - SMS Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/bf998e866456c232965f4bd845b65db1/2FA_-_SMS_Insert_Code_-_PT.png)
 
 <div class="alert alert-warning">
 Não podemos garantir que sua operadora de telefonia conseguirá entregar a chave de acesso sempre que necessário. Caso a mensagem de texto da VTEX não chegue, tente reenviar o código ou <a href="#habilitar-o-2fa-por-aplicativo">habilitar o 2FA por aplicativo</a>.
@@ -89,10 +87,10 @@ Para modificar as configurações de verificação em duas etapas:
 
 1. Acesse suas configurações de usuário, clicando no círculo com suas iniciais no canto superior-direito do Admin.
 
-  ![2FA - User Initials - PT](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
+  ![2FA - User Initials - PT](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
 
 2. Clique em **Verificação em 2 passos** para visualizar suas configurações.
 
-  ![2FA - My User - PT](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
+  ![2FA - My User - PT](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
 
 3. Você poderá então alterar suas configurações seguindo passos similares aos apresentados nas seções acima para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) e [aplicativo](#habilitar-o-2fa-por-aplicativo). 
diff --git a/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
index 47a5e0a62..ace011170 100644
--- a/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
@@ -1,10 +1,10 @@
 ---
 title: 'Adicionar suporte a 3DS2 na integração com a Redsýs V2'
 id: 1ixji2XORg9p0UoW8gBtUG
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-08T14:53:08.780Z
-updatedAt: 2023-03-23T15:42:17.139Z
-publishedAt: 2023-03-23T15:42:17.139Z
+updatedAt: 2024-03-18T19:54:47.084Z
+publishedAt: 
 firstPublishedAt: 2021-03-08T16:29:32.443Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: adicionar-suporte-a-3ds2-na-integracao-com-a-redsys-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Agora, a funcionalidade 3DS2 também está disponível para pagamentos realizados via cartão de crédito e processados pelo gateway de pagamentos [Redsýs](https://help.vtex.com/pt/tutorial/configurar-gateway-redsys--7xRnMyzZS0kQoIG2ISagY8).
 
 3DS2 é uma solução de segurança que permite ao comprador ser autenticado no banco emissor, garantindo ainda mais segurança para suas transações on-line. 
@@ -33,6 +35,6 @@ Neste tutorial, explicaremos como realizar essa integração por meio do Admin d
 4. Desça a tela e habilite a opção __3DS Enabled__.  
 5. Clique em __Salvar__.
 
-![RedsysV2 PT](https://images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/803dff2f8664c2fef47143f6261a4463/Redsys_3DS2_-_PT.png)
+![RedsysV2 PT](//images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/803dff2f8664c2fef47143f6261a4463/Redsys_3DS2_-_PT.png)
 
 Feito isso, a solução estará habilitada para as transações da Redsýs com cartão de crédito.
diff --git a/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
index 6f2af423f..e9073a75a 100644
--- a/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -75,9 +75,9 @@ Para garantir que os vendedores da sua loja física tenham acesso correto ao est
 Para isso, escolha um vendedor cadastrado na loja em que deseja testar a Venda em Mãos e siga os passos descritos abaixo. 
 
 1. Com [o registro do vendedor escolhido](https://help.vtex.com/pt/tutorial/vendedores-instore-beta--4rzit1pzp28km4HSDEdrEC), acesse a aplicação do VTEX Sales App e faça o login.
-![instore-login-pt](https://images.ctfassets.net/alneenqid6w5/5vKzjuYAYKGIVZz5aOyuPV/9049d57cf49ca1e753b69896ea5f348f/image.png)
+![instore-login-pt](//images.ctfassets.net/alneenqid6w5/5vKzjuYAYKGIVZz5aOyuPV/9049d57cf49ca1e753b69896ea5f348f/image.png)
 2. Busque por um item que existe no estoque da conta franquia cadastrado. Este item deverá estar exibindo a quantidade disponível correspondente ao inventário do seller.
-![instore-pdp-pt](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/861791e5b4f8f2304ae1a5a7ae577ad8/image.png)
+![instore-pdp-pt](//images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/861791e5b4f8f2304ae1a5a7ae577ad8/image.png)
 
 <div class="alert alert-info">
 <p>Caso você tenha habilitado estoque infinito, o número exibido será uma quantidade acima de 1 milhão de itens e não será alterado ao realizar uma venda.</p> 
@@ -92,9 +92,9 @@ Você também pode configurar para que a Vendas em Mãos ignore a quantidade do
 2. Clique no botão <i class="fas fa-cog"></i> engrenagem para editar. 
 3. Selecione a aba **Código**.
 4. Selecione na aba lateral o arquivo `checkout-instore-custom-js`.
-![instore-custom-js-pt](https://images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/6521818abb09e4178491f4598f33c9a0/image.png)
+![instore-custom-js-pt](//images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/6521818abb09e4178491f4598f33c9a0/image.png)
 5. Na chave `window.INSTORE_CONFIG`, adicione a flag `sellWithoutStockInHands: true`.
-![sellWithoutStockInHands-pt](https://images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/14bef6c0a1cbdc5d216b17a49c438c76/image.png)
+![sellWithoutStockInHands-pt](//images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/14bef6c0a1cbdc5d216b17a49c438c76/image.png)
 6. Clique em <i class="fas fa-save"></i> `Salvar`. 
 
 ### Habilitar venda de carrinhos mistos (opcional)
diff --git a/docs/tutorials/pt/entering-tax-receipts-in-the-order.md b/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
index a97a94461..f3bae8e4c 100644
--- a/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
@@ -19,7 +19,7 @@ Inserir a nota fiscal no pedido é um passo obrigatório para que o status passe
 
 Para fazer manualmente pelo **Gerenciamento de pedidos**, basta clicar no botão `Faturar pacote`, como na imagem abaixo.
 
-![faturar-pedido-ex pt](https://images.ctfassets.net/alneenqid6w5/1IOORyWRjC4eEayM8iW6OG/0e49ae3568ea66ed18b5b8ab6f90d414/ex_1_pt.png)
+![faturar-pedido-ex pt](//images.ctfassets.net/alneenqid6w5/1IOORyWRjC4eEayM8iW6OG/0e49ae3568ea66ed18b5b8ab6f90d414/ex_1_pt.png)
 
 Com a inserção da nota fiscal com o valor completo do pedido, o mesmo passará para o status **Faturado**.
 
diff --git a/docs/tutorials/pt/erasing-customer-data.md b/docs/tutorials/pt/erasing-customer-data.md
new file mode 100644
index 000000000..c6556442f
--- /dev/null
+++ b/docs/tutorials/pt/erasing-customer-data.md
@@ -0,0 +1,64 @@
+---
+title: 'Exclusão de dados de clientes'
+id: 1R9Fn7A06Ifj4R9YD4JTKU
+status: PUBLISHED
+createdAt: 2022-04-14T13:28:53.209Z
+updatedAt: 2023-06-23T15:06:52.315Z
+publishedAt: 2023-06-23T15:06:52.315Z
+firstPublishedAt: 2022-04-14T13:50:08.688Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: exclusao-de-dados-de-clientes
+locale: pt
+legacySlug: exclusao-de-dados-de-clientes
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+De acordo com regulações de proteção de dados como [LGPD e GDPR](https://vtex.com/us-en/privacy-and-agreements/vtex-commitment/), empresas que utilizam dados pessoais de clientes devem aceitar seus pedidos de exclusão de cadastro. Portanto, a VTEX permite que você solicite a exclusão de dados dos clientes da sua loja.
+
+## Antes de solicitar a exclusão de dados
+
+Antes de [solicitar a exclusão via suporte](#solicitar-exclusao-via-suporte), é importante que você confira quais entidades de dados do Master Data armazenam dados de clientes na sua operação.
+
+Você deve ter cuidado para não excluir nenhuma informação das [entidades nativas do Master Data](#entidades-nativas-do-master-data). Entretanto, você deve ter excluir manualmente informações do cliente que estejam armazenadas em [outras entidades de dados](#outras-entidades-de-dados), caso sua loja tenha. Você pode encontrar mais detalhes sobre isso abaixo.
+
+### Entidades nativas do Master Data
+
+Com a sua [solicitação via suporte](#solicitar-exclusao-via-suporte), a VTEX excluirá os dados das entidades de dados nativas **CL** e **AD**. É importante que você não exclua dados destas entidades.
+
+### Outras entidades de dados
+
+Se a sua loja armazena informações de clientes em outras entidades de dados, você precisa fazer a exclusão manual destes dados antes de fazer a solicitação via suporte. Para fazer isso, use a API do Master Data:
+
+1. Busque o documento com o endpoint [Search document](https://developers.vtex.com/vtex-rest-api/reference/searchdocuments-1)
+
+2. Utilize a requisição [Delete document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1)
+
+<div class="alert alert-danger">
+Não realize esse processo para as entidades <b>CL</b> e <b>AD</b>.
+</div>
+
+## Solicitar exclusão via suporte
+
+Você deverá solicitar a extensão da exclusão de dados pessoais de seus clientes nos sistemas da VTEX via abertura de ticket no [Suporte VTEX](https://help.vtex.com/pt/support).
+
+Para formalizar o pedido, siga os passos:
+
+1. Acesse o [Suporte VTEX](https://help.vtex.com/pt/support).
+2. Preencha seu nome completo no campo **Nome** e selecione no campo **Loja** o nome da loja que deseja solicitar o chamado.
+3. Clique na opção `Continuar`.
+4. Selecione a opção `Técnico`.
+5. No campo **Tipos de problema**, selecione a opção `Gostaria de solicitar uma configuração`.
+6. No campo **Assunto da solicitação**, você deverá preencher as seguintes informações:
+   * Solicitação de Data Subject Request
+   * VTEX accounts
+   * Email vinculado a contas VTEX cujos dados devem ser excluídos.
+7. Selecione no campo **Sua experiência com a plataforma** a opção que corresponde à sua experiência como usuário da plataforma VTEX.
+8. Preencha o campo **Descreva o que aconteceu detalhadamente** com detalhes da sua solicitação.
+9. Clique em `Enviar`.
+
+<div class="alert alert-warning" role="alert">
+Solicite a exclusão de dados de apenas uma conta, ou seja, um email do shopper a ser excluído por ticket. Caso você inclua mais de um email, o ticket será retornado.</div>
+
+Sua solicitação será enviada à nossa equipe de suporte. Na conclusão do chamado, será emitido um certificado para o email em que o ticket foi aberto comprovando a veracidade da conclusão da exclusão dos dados.
diff --git a/docs/tutorials/pt/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md b/docs/tutorials/pt/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
new file mode 100644
index 000000000..f9ab1261b
--- /dev/null
+++ b/docs/tutorials/pt/error-when-trying-to-import-skus-via-spreadsheet-in-the-vtex-admin.md
@@ -0,0 +1,43 @@
+---
+title: 'Erro ao tentar importar SKUs por planilha no Admin VTEX'
+id: 1TDF87s7P1UJT1hNDGZsuk
+status: PUBLISHED
+createdAt: 2024-07-01T15:07:50.982Z
+updatedAt: 2024-07-22T18:56:05.856Z
+publishedAt: 2024-07-22T18:56:05.856Z
+firstPublishedAt: 2024-07-01T18:24:23.096Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: erro-ao-tentar-importar-skus-por-planilha-no-admin-vtex
+locale: pt
+legacySlug: erro-ao-tentar-importar-skus-por-planilha-no-admin-vtex
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags:** *Catálogo, SKU*
+
+**Palavras-chave:** *catálogo, sku, planilha, importação*
+
+Após a definição da árvore de categorias e o cadastro de [especificações de produtos e de SKUs](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) na sua loja, é necessário preencher os valores das especificações criadas. No Admin VTEX, esse processo pode ser realizado através de uma planilha ou de forma manual no cadastro do [produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106#cadastro-do-produto) e no cadastro do [SKU](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119#cadastro-do-sku).
+Se ao realizar a [importação de SKUs por planilha](https://help.vtex.com/pt/tutorial/exportar-e-importar-especificacoes-de-produto-e-de-sku--tutorials_274?&utm_source=autocomplete), aparecer a mensagem 
+`"An error occurred in the data writing process. Make sure your worksheet data is consistent with the instructions and try again."`, pode ser que:
+
+- [Especificações obrigatórias de SKU não estejam preenchidas.](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
+- O arquivo esteja na formatação errada.
+
+## Solução
+Para resolver esse problema, é possível:
+
+[Modificar o arquivo](#solucao-modificar-o-arquivo): O arquivo precisa seguir regras específicas de formatação e ser salvo como uma planilha XML no formato .xls.
+### Solução  - Modificar o arquivo
+
+1. Em **Catálogo > Importação e exportação > Todos os produtos > Exportação / Importação**, clique na aba **Importar**.
+2. Clique em `Clique aqui` para fazer o download da planilha de exemplo.
+3. Edite a planilha de exemplo com os SKUs desejados, seguindo todas as recomendações da página [Import and Export](https://cosmetics2.myvtex.com/admin/Site/Relatorio_Skus.aspx)
+4. Salvar a planilha no formato `.xls`.
+5. Na mesma página, em Upload de arquivo para importação, selecione o arquivo esse clique `Importar`.
+6. Cheque se a importação foi finalizada. 
+
+Caso o erro persista após a modificação do arquivo, entre em contato com o [Nosso Suporte](https://support.vtex.com/hc/pt-br/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests).
+
diff --git a/docs/tutorials/pt/events-available-in-audit.md b/docs/tutorials/pt/events-available-in-audit.md
index 7fd836f44..0d69b5c79 100644
--- a/docs/tutorials/pt/events-available-in-audit.md
+++ b/docs/tutorials/pt/events-available-in-audit.md
@@ -3,672 +3,243 @@ title: 'Eventos disponíveis no Audit'
 id: 6r1Mzcu5NmkmmDLJlz9CCZ
 status: PUBLISHED
 createdAt: 2022-06-22T16:05:16.214Z
-updatedAt: 2023-04-25T14:51:35.871Z
-publishedAt: 2023-04-25T14:51:35.871Z
+updatedAt: 2024-06-28T18:16:11.762Z
+publishedAt: 2024-06-28T18:16:11.762Z
 firstPublishedAt: 2022-06-22T16:28:52.801Z
 contentType: tutorial
 productTeam: Master Data
-author: 2Gy429C47ie3tL9XUEjeFL
+author: 1malnhMX0vPThsaJaZMYm2
 slug: eventos-disponiveis-no-audit
 locale: pt
 legacySlug: eventos-disponiveis-no-audit
 subcategory: 2TNXiKzLZOPxjMTyGiEeJu
 ---
 
-Veja, abaixo, a lista dos possíveis eventos disponíveis no [Audit](https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA#) por aplicação.
+Confira a seguir a lista dos possíveis eventos disponíveis no [Audit](https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA) por aplicação.
+
+* [OMS](#oms)
+* [Pedidos](#pedidos)
+* [Autorização de pedido](#autorizacao-de-pedido)
+* [Estoque e entrega](#estoque-e-entrega)
+* [Catálogo (Admin)](#catalogo-admin)
+* [Catálogo (API)](#catalogo-api)
+* [Preços](#precos)
+* [Promoções](#promocoes)
+* [Assinaturas](#assinaturas)
+* [Carteiras](#carteiras)
+* [Vale-presente](#vale-presente)
+* [Checkout](#checkout)
+* [Portal CMS](#portal-cms)
+* [License Manager](#license-manager)
+* [VTEX ID](#vtex-id)
+* [Headless CMS](#headless-cms)
+* [Gerenciamento de sellers](#gerenciamento-de-sellers)
 
 <div class = "alert alert-info">
-Se você vê no Audit algum evento que não está listado aqui, por favor indique mais informações usando a <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback de documentação</a>.
-</div>
+  <p>Caso você visualize no Audit algum evento que não esteja listado aqui, por favor nos informe usando a <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback de documentação</a>.</p>
+  </div>
 
 <div class="alert alert-warning">
-  Nas opções de filtros do Audit, você pode encontrar a opção <code>Profile System</code> além das aplicações citadas abaixo. Esta opção se refere a funcionalidades em fase de closed beta, portanto, a maior parte das contas não terão eventos associados.
+  <p>Nas opções de filtros do Audit, você pode encontrar <strong>Opções de envio</strong>, <strong>Profile System</strong> e <strong>Billing</strong> além das aplicações citadas abaixo. Essas opções se referem a recursos internos ou funcionalidades em fase beta fechada, portanto, a maior parte das contas não terão eventos associados.</p>
 </div>
 
-## Catalog admin
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Product Activation
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Ativação de produto.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do produto.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Product Commercial Condition Change
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Mudanças em condições comerciais de um produto.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do produto e lista de condições alteradas.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Attachment Association    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Associação de anexo a SKU.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do SKU, nome e ID do anexo.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Archive Upload    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Envio de arquivo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome do arquivo.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Field Activation    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Ativação de campo de catálogo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome, ID e status do campo.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Binding    
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Ligação de um SKU a um seller.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do seller, ID do SKU no catálogo do seller e ID do SKU no catálogo do marketplace.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Unbinding
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Remoção de ligação de um SKU a um seller.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do seller, ID do SKU no catálogo do seller e ID do SKU no catálogo do marketplace.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">SKU Seller Removal
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Remoção de SKU de seller.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do SKU no catálogo do seller.
-   </td>
-  </tr>
-</table>
-
-## Pricing
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Put Price
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação ou alteração de preço para um dado SKU.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do SKU.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Price Table
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação ou alteração de tabela de preços.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação da tabela criada ou alterada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Price Tables
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação ou alteração de múltiplas tabelas de preços.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação das tabelas criadas ou alteradas.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Price Deleted
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de preço para um dado SKU.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do SKU.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Config
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação ou alteração de configuração de preço.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação da configuração criada  ou alterada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Fixed Price Modified
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de preço fixo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação do preço fixo alterado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Put Catalog Step
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação ou alteração de uma regra de preço
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Regra de preço criada ou alterada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Deleted Fixed Prices From Table
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de preço fixo da respectiva tabela de preços.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação da tabela e do preço excluído.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Compatibility Post Prices
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de preço utilizando a API de compatibilidade com o contrato do PricingV1
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação do preço alterado.
-   </td>
-  </tr>
-</table>
-
-## Logistics
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de transportadora.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da transportadora.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Atualização de transportadora.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da transportadora.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Carrier Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de transportadora.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da transportadora.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de doca.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da doca.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Atualização de doca.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da doca.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Dock Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de doca.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da doca.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Create
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de estoque.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do estoque.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Atualização de estoque.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do estoque.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Warehouse Delete
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de estoque.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do estoque.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Pickup Point Save
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação ou alteração de ponto de retirada.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do ponto de retirada.
-   </td>
-  </tr>
-</table>
-
 ## OMS
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Start Handling
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Ação que sinaliza para a VTEX que a loja iniciou o manuseio de um dado pedido. Isso desencadeia a continuidade do fluxo deste pedido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do pedido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Status
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Mudança de status de um pedido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do pedido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Payment Notification
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Envio de notificação de pagamento para um dado pedido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do pedido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de configuração do módulo de pedidos.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Short description of the change.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resend Last Email
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Reenvio do último email relacionado àquele pedido no Message Center.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do pedido.
-   </td>
-  </tr>
-</table>
-
-## Promotions
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Rate Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de configuração de taxa.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da configuração da taxa.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Promotion Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de configuração de promoção.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da configuração da promoção.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Coupon Configuration
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração em coupom.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Código do cupom.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Unarchived Calculator
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Desarquivamento de promoção ou taxa.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID da configuração da promoção ou taxa.
-   </td>
-  </tr>
-</table>
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Start Handling | Ação que sinaliza para a VTEX que a loja iniciou o manuseio de um  dado pedido. Isso desencadeia a continuidade do fluxo deste pedido. | ID do pedido. |
+| Change Status | Mudança de status de um pedido. | ID do pedido. |
+| Shipping Notification | Notificação de envio para um dado pedido. | ID do pedido. |
+| Payment Notification | Envio de notificação de pagamento para um dado pedido. | ID do pedido. |
+| Save Configuration | Alteração de configuração do módulo de Pedidos. | Descrição curta da alteração. |
+| Resend Last Email | Reenvio do último email relacionado àquele pedido no Message Center. | ID do pedido. |
+
+## Pedidos
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Change State | Mudança de status do pedido. | ID do pedido. |
+| Order Cancellation | Cancelamento de pedido. | ID do pedido. |
+| Start Handling | Ação que sinaliza para a VTEX que a loja iniciou o manuseio de um dado pedido. Isso desencadeia a continuidade do fluxo deste pedido. | ID do pedido. |
+| Notify Payment | Envio de notificação de pagamento para um dado pedido. | ID do pedido. |
+
+## Autorização de pedido
+
+| Ação |  Descrição do evento |  Detalhes do evento |
+|---|---|---|
+| Create Rule |  Criação de regra de divergência de valores. | ID da regra. |
+| New Dimension |  Criação de dimensões para aprovações de pedidos, como intervalo do valor do pedido, lista de e-mails autorizados a executar a aprovação do pedido, entre outros. | ID da dimensão. |
+| Delete Dimension |  Exclusão de dimensões para aprovações de pedidos, como intervalo do valor do pedido, lista de e-mails autorizados a executar a aprovação do pedido, entre outros. | ID da dimensão. |
+| Update Dimension |  Atualização de dimensões para aprovações de pedidos, como intervalo do valor do pedido, lista de e-mails autorizados a executar a aprovação do pedido, entre outros. | ID da dimensão. |
+| Update Rule |  Edição de regra de divergência de valores. | ID da regra. |
+| Delete Rule |  Exclusão de regra de divergência de valores. | ID da regra. |
+
+## Estoque e entrega
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Carrier Create | Criação de transportadora. | ID da transportadora. |
+| Carrier Update | Atualização de transportadora. | ID da transportadora. |
+| Carrier Delete | Exclusão de transportadora. | ID da transportadora. |
+| Dock Create | Criação de doca. | ID da doca. |
+| Dock Update | Atualização de doca. | ID da doca. |
+| Dock Delete | Exclusão de doca. | ID da doca. |
+| Warehouse Create | Criação de estoque. | ID do estoque. |
+| Warehouse Update | Atualização de estoque. | ID do estoque. |
+| Warehouse Delete | Exclusão de estoque. | ID do estoque. |
+| Pickup Point Save | Criação ou alteração de ponto de retirada. | ID do ponto de retirada. |
+
+## Catálogo (Admin)
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Product Activation | Ativação de produto. Este evento é registrado somente quando a alteração acontece no Admin. Alterações por planilha não são registradas neste evento. | ID do produto. |
+| Product Commercial Condition Change | Mudanças em condições comerciais de um produto. | ID do produto e lista de condições alteradas. |
+| SKU Attachment Association  | Associação de anexo a SKU. | ID do SKU, nome e ID do anexo. |
+| Archive Upload  | Envio de arquivo. | Nome do arquivo. |
+| Field Activation  | Ativação de campo de catálogo. | Nome, ID e status do campo. |
+| SKU Seller Binding  | Ligação de um SKU a um seller. | ID do seller, ID do SKU no catálogo do seller e ID do SKU no catálogo do marketplace. |
+| SKU Seller Unbinding | Remoção de ligação de um SKU a um seller. | ID do seller, ID do SKU no catálogo do seller e ID do SKU no catálogo do marketplace. |
+| SKU Seller Removal | Remoção de SKU de seller. | ID do SKU no catálogo do seller. |
+
+## Catálogo (API)
+
+| Ação | Descrição | Detalhes do evento |
+|---|---|---|
+| SKU Seller Binding Removal | Remoção de vínculo de SKU. | ID do SKU no seller e ID do seller. |
+| Seller Update | Atualização de seller. | ID do seller. |
+| Seller Creation | Criação de seller. | ID do seller. |
+| SKU Seller Binding Activation | Ativação de vínculo de SKU. | ID do SKU no seller e ID do seller. |
+| SKU Seller Binding Inactivation | Inativação de vínculo de SKU. | ID do SKU no seller e ID do seller. |
+
+## Preços
+
+| Ação | Descrição | Detalhes do evento |
+|---|---|---|
+| Put Price | Criação ou alteração de preço para um dado SKU. | ID do SKU. |
+| Save Price Table | Criação ou alteração de tabela de preços. | Identificação da tabela criada ou alterada. |
+| Save Price Tables | Criação ou alteração de múltiplas tabelas de preços. | Identificação das tabelas criadas ou alteradas. |
+| Price Deleted | Exclusão de preço para um dado SKU. | ID do SKU. |
+| Save Config | Criação ou alteração de configuração de preço. | Identificação da configuração criada  ou alterada. |
+| Fixed Price Modified | Alteração de preço fixo. | Identificação do preço fixo alterado. |
+| Put Catalog Step | Criação ou alteração de uma regra de preço | Regra de preço criada ou alterada. |
+| Deleted Fixed Prices From Table | Exclusão de preço fixo da respectiva tabela de preços. | Identificação da tabela e do preço excluído. |
+| Compatibility Post Prices | Alteração de preço utilizando a API de compatibilidade com o contrato do PricingV1 | Identificação do preço alterado. |
+| Change Rnb Config  | Alteração de configuração de preços em novas contas. | Nome da conta que fez a alteração. |
+
+## Promoções
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Archive Coupon | Arquivamento de cupom. | Código do cupom. |
+| Unarchive Coupon | Desarquivamento de cupom. | Código do cupom. |
+| Change Rate Configuration | Alteração de configuração de taxa. | ID da configuração da taxa. |
+| Change Promotion Configuration | Alteração de configuração de promoção. | ID da configuração da promoção. |
+| Change Coupon Configuration | Alteração em coupom. | Código do cupom. |
+| Unarchived Calculator | Desarquivamento de promoção ou taxa. | ID da configuração da promoção ou taxa. |
+| Archived Calculator | Arquivamento de promoção ou taxa. | ID da configuração da promoção ou taxa. |
+
+## Assinaturas
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| SubscriptionGroup Update | Atualização de um grupo de assinatura. | ID do grupo de assinatura. |
+| Subscription Create | Criação de assinatura. | ID da assinatura. |
+| SubscriptionGroup Place Order | Criação de um pedido de assinatura dentro de um grupo de assinatura. | ID do grupo de assinatura. |
+| SubscriptionGroup Retry | Execução de uma retentativa de gerar um ciclo de assinatura. | ID do grupo de assinatura. |
+| Subscription Delete | Exclusão de assinatura. | ID da assinatura. |
+| Plan Create | Criação de um plano de assinatura, onde lojas podem associar itens e SKUs diferentes. | ID do plano de assinatura. |
+| Plan Update | Atualização de um plano de assinatura, onde lojas podem associar itens e SKUs diferentes. | ID do plano de assinatura. |
+| Subscriber Fetch By Email | Auditoria de quem pesquisou dados do perfil de um cliente da loja que realizou assinaturas, a partir do email do cliente. | ID do usuário que realizou a pesquisa. |
+| SubscriptionGroup Create For Order | Criação de um grupo de assinatura para um pedido existente. | ID do grupo de assinatura. |
+| Plan Delete | Exclusão de um plano de assinatura. | ID do plano de assinatura. |
+| Store Payments Update | Atualização das formas de pagamento que a loja aceita para fazer assinaturas. | Nome de conta. |
+
+## Carteiras
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| TOGGLE_WALLET | Ativar ou desativar uma carteira digital. | toggle-wallet-action |
+
+## Vale-presente
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| LIST_GIFT_CARD | Visualização da lista de vales-presente. | list-gift-card |
+| EXPORT_GIFT_CARD | Exportação de vale-presente. | export-gift-card |
+| EDIT_GIFT_CARD | Edição de valor de vale-presente. | add-gift-card-value |
+| CREATE_GIFT_CARD | Criação de vale-presente. | create-multiple-gift-cards |
 
 ## Checkout
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Configurated OrderForm
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de configurações do OrderForm, objeto que rege o funcionamento do checkout da loja.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Descrição da ação (”configurated OrderForm”)
-   </td>
-  </tr>
-</table>
-
-## Portal v2
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Configuration Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de configuração do portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">“*”
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Saved
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de arquivo do portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome do arquivo alterado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Site Created
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de site.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome do site criado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Template Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de template do portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome do template alterado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Page Updated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de página.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome da página
-   </td>
-  </tr>
-</table>
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| SaveOrderFormConfiguration | Alteração de configurações do OrderForm, objeto que rege o funcionamento do checkout da loja. | Descrição da ação ("configurated OrderForm") |
 
 ## Portal CMS
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Update
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Alteração de arquivo do portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome e ID do arquivo alterado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Upload
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Upload de arquivo do portal.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome do arquivo alterado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">File Deleted
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de arquivo.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Nome e ID do arquivo alterado.
-   </td>
-  </tr>
-</table>
-
-## Conditions
-
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-    <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PutCondition
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de condição
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Identificação da condição criada.
-   </td>
-  </tr>
-</table>
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| File Update | Alteração de arquivo do portal. | Nome e ID do arquivo alterado. |
+| File Upload | Upload de arquivo do portal. | Nome do arquivo alterado. |
+| File Deleted | Exclusão de arquivo. | Nome e ID do arquivo alterado. |
+
+## License Manager
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Block AppToken | Bloqueio de chave de aplicação. | Chave de aplicação bloqueada. |
+| Accept Sponsor Invite | Aceite de convite para se tornar usuário titular. | ID do usuário que aceitou o convite. |
+| Save User | Criação de usuário ou alteração de informações de usuário. | ID do usuário. |
+| Save Account | Criação de conta ou edição de informações de conta. | Conta criada ou alterada. |
+| Change Role | Edição de perfil de acesso. | Perfil de acesso editado. |
+| Delete Role | Exclusão perfil de acesso. | Perfil de acesso excluído. |
+| Unblock AppToken | Desbloqueio de chave de aplicação. | Chave de aplicação desbloqueada. |
+| Resource Access Allowed | Acesso a recurso permitido. | Chave do recurso e ID do usuário ao qual foi permitido. |
+| Cancel Sponsor Invite | Cancelamento de convite para usuário titular. | ID do usuário convidado. |
+| Delete User | Exclusão de usuário. | ID do usuário excluído. |
+| Update Binding | Atualização de binding. | Binding atualizado. |
+| Resource Access Denied | Acesso a recurso negado. | Chave do recurso e ID do usuário ao qual foi negado. |
+| Create New AppToken | Criação de chave de aplicação. | Chave de aplicação criada. |
+| Create Sponsor Invite | Criação de convite para usuário titular. | ID do usuário convidado. |
 
 ## VTEX ID
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PasswordCreated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Usuário registra uma senha pela primeira vez na loja ou no Admin VTEX.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">PasswordUpdated
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Usuário altera sua senha da loja ou do Admin VTEX.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">IdentityProviderChanged
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Mudança de configurações de provedor de identidade. Por exemplo: criação de integração OAuth customizada, alteração de informações em configuração de OAuth existente, entre outros.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Provedor de identidade.
-   </td>
-  </tr>
-</table>
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| PasswordCreated | Usuário registra uma senha pela primeira vez na loja ou no Admin VTEX. | ID do usuário. |
+| PasswordUpdated | Usuário altera sua senha da loja ou do Admin VTEX. | ID do usuário. |
+| IdentityProviderChanged | Mudança de configurações de provedor de identidade. Por exemplo: criação de integração OAuth customizada, alteração de informações em configuração de OAuth existente, entre outros. | Provedor de identidade. |
 
-## License Manager
+## Master Data
+
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| DeleteDocument | Exclusão de documento. | ID do documento. |
+
+## Headless CMS
+
+| Ação | Descrição | Detalhes do evento |
+|---|---|---|
+| TRY_PUBLISHING | Tentativa de publicar uma página. | ID do evento. |
+| TRY_PUBLISH_IN_RELEASE | Tentativa de publicar um lançamento. | ID do evento. |
+| TRY_UNPUBLISHING | Tentativa de publicar uma página. | ID do evento. |
+| RESTORE_CONTENT | Restauração de conteúdo. | ID do evento. |
+| TRY_UPDATING_DRAFT | Tentativa de atualizar um rascunho. | ID do evento. |
+| TRY_UNPUBLISHING_AND_OVERWRITING | Tentativa de despublicar e sobrescrever uma página. | ID do evento. |
+| done.invoke.deleteContent | Exclusão de conteúdo. | ID do evento. |
+| done.invoke.deleteContentVariant | Exclusão de uma versão do conteúdo. | ID do evento. |
+
+Na coluna **Ação**, todos os eventos do Headless CMS também apresentam as seguintes informações:
+
+* **CONTENT_ID:** código identificador único do conteúdo.
+* **VARIANT_ID:** código identificador único da versão do conteúdo.
+* **WORKSPACE:** workspace em que a alteração foi realizada.
+
+## Gerenciamento de sellers
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Ação</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Descrição do evento</strong>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><strong>Detalhes do evento</strong>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Block AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Bloqueio de chave de aplicação.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Chave de aplicação bloqueada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Accept Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Aceite de convite para se tornar usuário titular.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário que aceitou o convite.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save User
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de usuário ou alteração de informações de usuário.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Save Account
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de conta ou edição de informações de conta.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Conta criada ou alterada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Change Role
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Edição de perfil de acesso.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Perfil de acesso editado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Delete Role
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão perfil de acesso.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Perfil de acesso excluído.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Unblock AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Desbloqueio de chave de aplicação.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Chave de aplicação desbloqueada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resource Access Allowed
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Acesso a recurso permitido.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Chave do recurso e ID do usuário ao qual foi permitido.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Cancel Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Cancelamento de convite para usuário titular.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário convidado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Delete User
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Exclusão de usuário.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário excluído.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Update Binding
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Atualização de binding.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Binding atualizado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Resource Access Denied
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Acesso a recurso negado.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Chave do recurso e ID do usuário ao qual foi negado.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Create New AppToken
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de chave de aplicação.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Chave de aplicação criada.
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Create Sponsor Invite
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Criação de convite para usuário titular.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">ID do usuário convidado.
-   </td>
-  </tr>
-</table>
+| Ação | Descrição do evento | Detalhes do evento |
+|---|---|---|
+| Update Seller | Edição de um seller. | ID do seller. |
+| Save Seller | Criação de um novo seller. | ID do seller. |
 
diff --git a/docs/tutorials/pt/exact-sales-suiteshare.md b/docs/tutorials/pt/exact-sales-suiteshare.md
index 1bfde064e..56e224960 100644
--- a/docs/tutorials/pt/exact-sales-suiteshare.md
+++ b/docs/tutorials/pt/exact-sales-suiteshare.md
@@ -21,17 +21,17 @@ Para realizar a integração acesse as informações de integrações no seu pai
 
 No dashboard, em **Integrações**, clique em **Ver todas as integrações**. Ou clique em **Configurações > Integrações**.
 
-![Exact Sales_1](https://images.ctfassets.net/alneenqid6w5/4BIijO0GTioTrQTMcJ9RHK/43c3fa8faf82688d8b81349ffddb126e/Exact_Sales_1.png)
+![Exact Sales_1](//images.ctfassets.net/alneenqid6w5/4BIijO0GTioTrQTMcJ9RHK/43c3fa8faf82688d8b81349ffddb126e/Exact_Sales_1.png)
 
 Selecione o **Exact sales** e clique em **Integrar**.
 
 Selecione o [**Formulário de captura**](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseje conectar.
 
-![Exact Sales_2](https://images.ctfassets.net/alneenqid6w5/0GPE5ktROtM3W1vK8TXN1/06650c897c805a8fe61433efb6b37621/Exact_Sales_2.png)
+![Exact Sales_2](//images.ctfassets.net/alneenqid6w5/0GPE5ktROtM3W1vK8TXN1/06650c897c805a8fe61433efb6b37621/Exact_Sales_2.png)
 
 Dentro do Exact Sales, clique em **Configurações** e em [**“Integrações”**](https://app.exactsales.com.br/Configuracao/ConfiguracaoIntegracoes/Index).
 
-![Exact Sales_3](https://images.ctfassets.net/alneenqid6w5/36Q38y7U71P7DB6ZlomAi5/6421cdc93d6292958e5fddadf464dadc/Exact_Sales_3.png)
+![Exact Sales_3](//images.ctfassets.net/alneenqid6w5/36Q38y7U71P7DB6ZlomAi5/6421cdc93d6292958e5fddadf464dadc/Exact_Sales_3.png)
 
 Copie o token fornecido pela Exact Sales e cole dentro da VTEX Assisted Sales (SuiteShare). 
 
diff --git a/docs/tutorials/pt/explained-search.md b/docs/tutorials/pt/explained-search.md
new file mode 100644
index 000000000..b9cab31c9
--- /dev/null
+++ b/docs/tutorials/pt/explained-search.md
@@ -0,0 +1,31 @@
+---
+title: 'Explicação da busca'
+id: F2yxrRvTNt4aEZGC7HV65
+status: PUBLISHED
+createdAt: 2024-06-27T16:54:49.509Z
+updatedAt: 2024-06-27T16:55:37.629Z
+publishedAt: 2024-06-27T16:55:37.629Z
+firstPublishedAt: 2024-06-27T16:55:37.629Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: explicacao-da-busca
+locale: pt
+legacySlug: explicacao-da-busca
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+Explicação da busca é uma funcionalidade que interpreta um termo pesquisado e apresenta a lista de produtos como um resultado de pesquisa. Ela também exibe todas as referências que foram utilizadas para determinar a ordenação. São elas:
+
+  - Configurações e regras de busca (configurados no VTEX Intelligent Search).
+  - Informações dos produtos.
+
+Com a ferramenta, é possível visualizar quais dados impactam a ordenação final. Dessa forma, ao expor essas informações pode-se efetuar modificações para atingir o objetivo desejado da pesquisa.
+
+Para utilizá-la, siga o passo a passo abaixo:
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Explicação da busca**. 
+
+![Explicação da Busca](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
+
diff --git a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
index 318fb94f2..d9594108b 100644
--- a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
@@ -3,8 +3,8 @@ title: 'Exportar e importar especificações de produto e de SKU'
 id: tutorials_274
 status: PUBLISHED
 createdAt: 2017-04-27T22:10:43.787Z
-updatedAt: 2023-03-29T15:30:59.932Z
-publishedAt: 2023-03-29T15:30:59.932Z
+updatedAt: 2024-02-21T20:34:56.013Z
+publishedAt: 2024-02-21T20:34:56.013Z
 firstPublishedAt: 2017-04-27T23:03:12.428Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,17 +27,21 @@ Neste artigo, explicamos como funciona a exportação e importação de planilha
 
 Veja a seguir como exportar a planilha com as especificações de produto ou de SKU:
 
-1.No Admin VTEX, acesse __Catálogo__, ou digite __Catálogo__ na barra de busca no topo da página.
+1. No Admin VTEX, acesse __Catálogo__, ou digite __Catálogo__ na barra de busca no topo da página.
 2. Clique em __Importação e exportação__.
 3. Clique na aba __Especificações de produto__ ou __Especificações de SKU__, dependendo da sua necessidade.
-    ![skuexport.pt](https://images.ctfassets.net/alneenqid6w5/2GmGsYDBCUlq01JyLJF6q/63708fe7dece1cf9ec100eeaf0851674/skuexport.pt.png)
+    ![skuexport.pt](//images.ctfassets.net/alneenqid6w5/2GmGsYDBCUlq01JyLJF6q/63708fe7dece1cf9ec100eeaf0851674/skuexport.pt.png)
 4. Clique com o botão direito na categoria desejada.
     Não é possível exportar especificações de todas as categorias de uma só vez. É preciso escolher apenas uma categoria cujas especificações você deseja exportar.
 5. Clique na opção `Exportar`.
     Um retângulo verde aparecerá na tela.
 6. Clique em `Clique aqui para baixar o arquivo`.
 
-![skuexport2.pt](https://images.ctfassets.net/alneenqid6w5/32z4zfvN7GeKcfZsuVQsGA/cac3411fabd0a1d32cb85b4592d0a4dd/skuexport2.pt.png)
+![skuexport2.pt](//images.ctfassets.net/alneenqid6w5/32z4zfvN7GeKcfZsuVQsGA/cac3411fabd0a1d32cb85b4592d0a4dd/skuexport2.pt.png)
+
+<div class = "alert alert-info">
+  <p>A planilha exportada ficará disponível por uma semana no seu email. Caso exceda esse prazo, siga o passo a passo de exportação novamente para gerar uma nova planilha.</p>
+</div>
 
 ## Importar especificações de produto ou de SKU
 
@@ -57,7 +61,7 @@ Siga os passos abaixo para importar a planilha:
 2. Clique em __Selecionar__ para escolher o arquivo com a planilha preenchida no seu computador.
 3. Clique em `Importar`.
 
-![skuexport3.pt](https://images.ctfassets.net/alneenqid6w5/4KnRQf8W5vHakt5FNyHup0/0a7cbb37721b6110065c14599f0288d7/skuexport3.pt.png)
+![skuexport3.pt](//images.ctfassets.net/alneenqid6w5/4KnRQf8W5vHakt5FNyHup0/0a7cbb37721b6110065c14599f0288d7/skuexport3.pt.png)
 
 ## Saiba mais
 - [Especificações de produto e de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
diff --git a/docs/tutorials/pt/exporting-data.md b/docs/tutorials/pt/exporting-data.md
index c0555bdb1..f449fb7d3 100644
--- a/docs/tutorials/pt/exporting-data.md
+++ b/docs/tutorials/pt/exporting-data.md
@@ -3,8 +3,8 @@ title: 'Exportar dados do Master Data v1'
 id: tutorials_1125
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:19.601Z
-updatedAt: 2023-03-28T23:31:33.420Z
-publishedAt: 2023-03-28T23:31:33.420Z
+updatedAt: 2024-06-20T15:09:14.414Z
+publishedAt: 2024-06-20T15:09:14.414Z
 firstPublishedAt: 2017-04-27T23:03:43.216Z
 contentType: tutorial
 productTeam: Master Data
@@ -21,19 +21,19 @@ A exportação de dados em massa de registros no Master Data v1 pode ser feita t
 A operação de exportar dados do Master Data não é instantânea, e o tempo de execução dela depende da quantidade de dados no Master Data. Por isso, em lojas com muitos dados e com uma alta frequência de atualização, o arquivo exportado pode ficar desatualizado em relação aos novos dados. Caso isso ocorra, a solução deve ser exportar os dados novamente, de preferência quando não há muitas atualizações ocorrendo (por exemplo, fora do horário comercial ou em fins de semana).
 </div>
 
-## Como exportar
+## Exportar relatório com dados do Master Data v1
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
-2. Clique na aba **Aplicações**.
-3. Clique em visualizar (ícone da direita) no formulário desejado.
-![visualizar button master data](https://images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
-4. Isso irá carregar a listagem do formulário selecionado.
-5. Clique no botão **Exportar XLS.**
+Siga as instruções abaixo para exportar um relatório com dados de registros de um formulário no Master Data v1.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Certifique-se de que você está na aba **Aplicações**.
+3. Clique no ícone de lista <i class="fas fa-bars"></i> ao lado do formulário desejado.
+4. Clique no botão `Exportar .xls`.
 6. Selecione os campos que deseja receber no relatório.
 7. Preencha o e-mail para o qual deseja enviar o relatório (o campo virá preenchido automaticamente com o e-mail do usuário logado, mas pode ser alterado).
-8. Clique no botão **Exportar.**
+8. Clique no botão `Exportar`.
 
-## Dados exportados de clientes
+## Dados exportados de Clientes
 
 Veja abaixo a lista de campos de dados exportados de clientes da aba **Clientes** no Profile System (CRM) do Master Data v1.
 
@@ -72,4 +72,4 @@ Veja abaixo a lista de campos de dados exportados de clientes da aba **Clientes*
 | rclastcartvalue       | Valor do último carrinho	       | Script de Navegação       |
 | carttag       | Lista dos últimos IDs dos SKUs do Carrinho	       | Script de Navegação       |
 
-Lembrando que estes são os campos que vêm por default no formulário **Cliente**. Caso a loja tenha personalizado a entidade Cliente, podem haver outros campos criados.
+Lembrando que estes são os campos que vêm por padrão no formulário **Cliente**. Caso a loja tenha personalizado a entidade __Cliente__, podem haver outros campos criados.
diff --git a/docs/tutorials/pt/facebook-faq.md b/docs/tutorials/pt/facebook-faq.md
index 96285626a..820a3fbd0 100644
--- a/docs/tutorials/pt/facebook-faq.md
+++ b/docs/tutorials/pt/facebook-faq.md
@@ -36,7 +36,7 @@ O primeiro passo a se investigar nesse cenário é se realmente o SKU não possu
 
 Caso o SKU possua um preço, verifique o status desse SKU pois o erro também pode estar relacionado com a situação de ativo/inativo. A melhor forma de fazer isso é realizando uma simulação de checkout:
 
-![face faq01](https://images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
+![face faq01](//images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
 
 Nessa simulação é importante analisar os campos:
 
@@ -53,7 +53,7 @@ Esse processo é indicado quando a integração está com algum problema de aute
 
 #### Excluir o App de integração da VTEX no Facebook
 1. Acesse o Facebook usando sua conta vinculada à VTEX.
-2. No canto direito superior da tela, **clique no botão** <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/7bplP3pn7Pu5gpfYKGHUjQ/688fda65e48070afcf18f57e396c2b22/sua_conta_fb.JPG" />
+2. No canto direito superior da tela, **clique no botão** <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/7bplP3pn7Pu5gpfYKGHUjQ/688fda65e48070afcf18f57e396c2b22/sua_conta_fb.JPG" />
 3. Selecione a opção **Configurações e privacidade**, em seguida clique em **Configurações**.
 4. Clique em **Integrações comerciais**.
 5. Selecione a opção **VTEX Integration** e clique em **Remover**.
@@ -62,7 +62,7 @@ Esse processo é indicado quando a integração está com algum problema de aute
 1. Acesse a página do [Facebook Business Manager](https://business.facebook.com/).
 2. Selecione a opção **Configurações**. 
 3. Clique em **Configurações do Negócio**.
-4. Selecione o catálogo da VTEX que deseja excluir e clique na lixeira <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6zFRTeiTa9xkTlafUVBIcK/d2c5a40219dbee8084d22f76d0b88109/excluir_fb.JPG" />
+4. Selecione o catálogo da VTEX que deseja excluir e clique na lixeira <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6zFRTeiTa9xkTlafUVBIcK/d2c5a40219dbee8084d22f76d0b88109/excluir_fb.JPG" />
 5. Clique em **Confirmar**.
 
 #### Excluir a configuração de integração do Facebook na VTEX
diff --git a/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md b/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md
index ca61c914d..6a0917a85 100644
--- a/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md
+++ b/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md
@@ -20,7 +20,7 @@ Como o lançamento do iOS 14 da Apple pode afetar os seus anúncios e relatório
 Se você planeja veicular anúncios otimizados para eventos de conversão que ocorrem no site do VTEX Assisted Sales (SuiteShare), você deve nos informar o seu **número de identificação do Gerenciador de Negócios**, para isso bastar seguir os passos a seguir: 
 
 1. Você pode encontrar o seu Número de identificação do Gerenciador de Negócios, acessando `https://business.facebook.com/settings/info` conforme imagem abaixo:
-![facebook liberação de domínio](https://images.ctfassets.net/alneenqid6w5/8upBYK7kQ4JPmnchLkNfz/07b08fedc1d9d8863d0bca7ebc455d02/image.png)
+![facebook liberação de domínio](//images.ctfassets.net/alneenqid6w5/8upBYK7kQ4JPmnchLkNfz/07b08fedc1d9d8863d0bca7ebc455d02/image.png)
 2. Assim que obter o seu número de identificação, [CLIQUE AQUI](\"https://suit.sh/liberacao-de-dominio\") para realizar a solicitação de liberação. Dentro de um prazo de 48 horas você será notificado por email, informando sobre a finalização do processo de liberação.
 
 Saiba mais:
diff --git a/docs/tutorials/pt/facilitating-b2b-store-operation.md b/docs/tutorials/pt/facilitating-b2b-store-operation.md
index c2e428745..bfebac48d 100644
--- a/docs/tutorials/pt/facilitating-b2b-store-operation.md
+++ b/docs/tutorials/pt/facilitating-b2b-store-operation.md
@@ -1,9 +1,9 @@
 ---
 title: 'Facilitar a operação da loja B2B'
 id: 8t1f9FYBsSCopHHVujKWR
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-03-30T14:29:12.548Z
-updatedAt: 2021-05-20T18:17:16.108Z
+updatedAt: 2024-05-10T10:59:55.549Z
 publishedAt: 2021-05-20T18:17:16.108Z
 firstPublishedAt: 2021-03-30T19:54:13.259Z
 contentType: tutorial
@@ -12,7 +12,7 @@ author: 7qy2DBsUp8U5P9lqV0JHfR
 slug: facilitar-a-operacao-da-loja-b2b
 locale: pt
 legacySlug: facilitar-a-operacao-da-loja-b2b
-subcategory: 5N5GjDrKSycIQMeoS7CLtj
+subcategory: 2LrbEY7MFeKqmdfYLBCnfi
 ---
 
 Você pode facilitar a operação da sua loja através da instalação de aplicativos que buscam solucionar problemas de negócio relacionados a usabilidade da loja, vendas e pós-vendas.
@@ -91,7 +91,7 @@ Todas as lojas VTEX contam com o [My account](https://help.vtex.com/pt/tutorial/
 
 Essa ferramenta permite que o cliente acompanhe o status do seu pedido no fluxo do pós-venda, bem como faça algumas operações. Uma delas é a de “Pedir novamente”, na qual é possível repetir um pedido feito previamente.  
 
-![Pedir novamente reorder](https://images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
+![Pedir novamente reorder](//images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
 
 Para saber mais detalhes sobre o My Account, confira o tutorial sobre [como configurar esta funcionalidade](https://help.vtex.com/pt/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1 "como configurar esta funcionalidade").
 
diff --git a/docs/tutorials/pt/faq-security-2.md b/docs/tutorials/pt/faq-security-2.md
index 9408d4ee8..d629a9773 100644
--- a/docs/tutorials/pt/faq-security-2.md
+++ b/docs/tutorials/pt/faq-security-2.md
@@ -3,7 +3,7 @@ title: 'FAQ - Segurança 2'
 id: 1ayXEtqawI9yuxFXutiITh
 status: DRAFT
 createdAt: 2022-05-26T13:33:48.633Z
-updatedAt: 2022-08-22T12:33:50.220Z
+updatedAt: 2024-05-28T16:48:10.138Z
 publishedAt: 
 firstPublishedAt: 2022-06-09T22:09:20.893Z
 contentType: tutorial
diff --git a/docs/tutorials/pt/faq-security-restricted-content.md b/docs/tutorials/pt/faq-security-restricted-content.md
new file mode 100644
index 000000000..92388cb00
--- /dev/null
+++ b/docs/tutorials/pt/faq-security-restricted-content.md
@@ -0,0 +1,187 @@
+---
+title: 'FAQ - Segurança (conteúdo restrito)'
+id: 7AmPOGXykmE9SYyYDzdAZ4
+status: DRAFT
+createdAt: 2022-05-26T00:09:53.997Z
+updatedAt: 2024-05-28T16:45:09.328Z
+publishedAt: 
+firstPublishedAt: 2022-06-02T18:56:44.116Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: faq-seguranca-conteudo-restrito
+locale: pt
+legacySlug: faq-seguranca-conteudo-restrito
+subcategory: 
+---
+
+# FAQ - Segurança (conteúdo restrito)
+
+<div class="alert alert-danger">
+  <p>Não compartilhe as informações desta FAQ com usuários que não possuem acesso ao Admin VTEX.</p>
+</div>
+
+Para apoiar as avaliações de risco de seus clientes, a VTEX disponibiliza páginas de FAQ com as principais perguntas e respostas relacionadas à estrutura e à segurança da plataforma. Este conteúdo é restrito a usuários com acesso ao Admin VTEX. As perguntas e respostas de teor público estão disponíveis na [FAQ - Segurança](https://help.vtex.com/pt/tutorial/risk-assessment--4K97IpqkpCpDYsZOSxtfkX) no VTEX Help Center.
+
+Clique nos itens a seguir para acessar as perguntas e respostas referentes a cada assunto:
+
+* [Gestão de risco](#gestao-de-risco)
+* [Controle de acesso, identificação e autenticação](#controle-de-acesso-identificacao-e-autenticacao)
+* [Segurança da plataforma](#seguranca-da-plataforma)
+* [Segurança de dados](#seguranca-de-dados)
+* [Segurança de rede](#seguranca-de-rede)
+* [Gerenciamento de vulnerabilidades](#gerenciamento-de-vulnerabilidades)
+* [Monitoramento de segurança](#monitoramento-de-seguranca)
+* [Resposta e mitigação a incidentes](#resposta-e-mitigacao-a-incidentes)
+* [Disaster Recovery e continuidade de negócios](#disaster-recovery-e-continuidade-de-negocios)
+
+## Gestão de risco
+
+### Como a VTEX gerencia os riscos de segurança cibernética na plataforma e infraestrutura interna?
+
+A VTEX realiza análises regulares de ameaças e vulnerabilidades na plataforma, nos processos operacionais e no negócio. A identificação de riscos desencadeia o aprimoramento de nossos sistemas de monitoramento e notificação para lidar com sua eventual materialização, seja notificando as pessoas aptas a tratá-los, seja acionando ações automatizadas que possam mitigá-los ou eliminá-los.
+
+### A VTEX tem um programa de gerenciamento de risco do fornecedor?
+
+A VTEX possui um processo robusto de gestão de risco em relação a terceiros. Isso envolve uma avaliação criteriosa e contínua dos parceiros e fornecedores, visando identificar, analisar e mitigar potenciais riscos associados às atividades desempenhadas por essas partes externas. Esse processo tem o objetivo de garantir a segurança e conformidade em todas as interações com terceiros, fortalecendo a postura de gestão de riscos da organização.
+
+Para integrar-se ao nosso ecossistema, exigimos que terceiros adotem medidas de segurança adequadas. Essa condição visa assegurar que todas as partes envolvidas mantenham padrões elevados de Segurança da Informação, contribuindo para a integridade e confiabilidade do nosso ambiente operacional.
+
+Caso deseje conhecer nossos parceiros que atuam como subprocessadores em nossos processos operacionais, visite a página [Subprocessadores - VTEX](https://vtex.com/br-pt/privacy-and-agreements/subprocessors).
+
+## Controle de acesso, identificação e autenticação
+
+### A VTEX detém uma política de senha para funcionários? Se sim, quais são os critérios considerados?
+
+Adotamos configurações seguras e política de senha robusta para o acessos aos nossos sistemas internos, tais como quantidade mínima de caracteres e caracteres especiais, periodicidade para alteração das senhas, não utilização das últimas senhas, controle e inatividade de sessão. Confira exemplos a seguir:
+
+* Comprimento mínimo de dezesseis caracteres.
+* Devem ser formados a partir da combinação de caracteres alfabéticos, maiúsculos e minúsculos, numéricos e especiais (`%`, `#`, `$`, `@`, `&`, entre outros).
+* Não devem ser utilizados números ou letras repetidos, em sequência ou formando séries óbvias, como, por exemplo, `aaaabbbb`, `12345678`, `asdfghjk`.
+* A criptografia forte deve ser usada para tornar todas as credenciais de autenticação ilegíveis durante a transmissão e armazenamento em todos os componentes do sistema.
+* A opção de troca de senha no primeiro login deve estar habilitada.
+* As senhas usadas anteriormente não devem ser reutilizadas.
+
+### A plataforma efetua log off da sessão por inatividade?
+
+A plataforma VTEX possui mecanismo de logout por inatividade. Um cliente é desconectado do ambiente do checkout automaticamente caso haja 15 minutos de inatividade.
+
+## Segurança da plataforma
+
+### Como a plataforma armazena e mantém a base de usuários? Como as credenciais dos usuários são armazenadas e protegidas?
+
+As senhas da plataforma VTEX usam uma combinação de hash e salt - atualmente suportamos algoritmos de hash SHA1 e PBKDF2 e usaremos um salt pré ou pós para uma camada adicional de segurança. Os e-mails dos usuários são armazenados e separados logicamente com base em uma determinada conta da loja, e não podem ser acessados, mesmo por funcionários da VTEX, de forma cruzada. Os bancos de dados que contêm os e-mails e hashes são totalmente criptografados com AES-256.
+
+### Como funciona o processo de Hardening?
+
+A VTEX sempre cria seus ambientes usando a AMI (imagem de máquina da Amazon) mais recente fornecida pela AWS para cada serviço de implantação, seja Elastic Beanstalk, OpsWorks ou simples Cloud Formation. Ao fazer isso, aproveitamos nossa segurança na proteção que a AWS já oferece para instâncias implantadas por seus serviços e complementamos as configurações de segurança com nossos processos de hardenização específicos para cada tipo de ativo.
+
+### Quais são os recursos de segurança da infraestrutura que hospeda a plataforma?
+
+A plataforma VTEX é uma solução SaaS (Software as a Service) hospedada em um ambiente altamente controlado, com uma variedade de medidas de segurança implementadas. Isso inclui proteção de rede, com filtragem e proteção do tráfego de entrada e saída, bem como o uso de um Web Application Firewall (WAF) para proteger os ativos internos, monitoramento automatizado em tempo real e alertas de ambientes.
+
+Ademais, são realizadas ações como a implementação de baselines, a hardenização dos ativos e o estabelecimento de controles de acesso físico e lógico, entre outros procedimentos necessários. Essas medidas visam garantir que a plataforma esteja continuamente protegida e em conformidade com os mais elevados padrões de segurança da indústria.
+
+## Segurança de dados
+
+### Quais são as capacidades da VTEX para prevenção de vazamento de dados?
+
+Investimos em medidas preventivas e métodos que aumentem a segurança da nossa plataforma e a infraestrutura que suporta a plataforma. Além disso, constantemente reforçamos o gerenciamento dos acessos aos sistemas, principalmente aos que possuem que possuem dados sensíveis, adotando sempre o mínimo de privilégio possível. Também, existem diretrizes gerais que devem ser seguidas ao operar em um ambiente regulamentado, como com dados de cartões de pagamentos (PCI-DSS) e aos aplicáveis às leis de proteção de dados, etc.
+
+Analisamos a forma como as informações são tratadas de um ambiente para outro, seja interno ou externo, sempre focando na prevenção que pessoas que não precisam saber de algumas informações, continuem não cientes sobre, diminuindo o perímetro de segurança. Outras atuações bastante presente na nossa tentativa de previnir vazamentos de dados são: Estamos sempre conscientizando os profissionais com as boas práticas sobre segurança da informação, com treinamentos e capacitação constantes; Estamos sempre tentando automatizar os controles de processos, ou seja, os computadores são muito melhores em manter a uniformidade do que as pessoas; Por fim, consideramos o processo contra vazamento de dados como um organismo vivo, sendo continuamente atualizado conforme forem surgindo novos riscos, demandas tecnológicas ou estratégicas da empresa.
+
+## Segurança de rede
+
+### As redes internas de produção são segregadas de alguma forma, por exemplo, restringindo e/ou filtrando o tráfego entre as redes?
+
+As redes de produção na VTEX são totalmente isoladas das redes externas, garantindo um ambiente altamente seguro. Os funcionários responsáveis pela operação dos ambientes de produção podem ocasionalmente precisar de uma conexão VPN (Virtual Private Network) para acessar essa rede.
+
+Os Load Balancers são os únicos objetos acessados externamente através da DMZ (Demilitarized Zone), enquanto as camadas da plataforma e do banco de dados residem em sub-redes separadas da DMZ. Essas camadas são protegidas por medidas adicionais de segurança, garantindo que apenas usuários autorizados possam acessá-las. Essa estrutura de rede proporciona uma camada adicional de proteção, mantendo os dados sensíveis e os sistemas da VTEX seguros contra ameaças externas.
+
+### A VTEX utiliza proteção de acesso às redes através de firewalls implementados?
+
+A VTEX utiliza proteção de acesso às redes por meio de firewalls implementados. Além dos firewalls locais dos sistemas operacionais nos servidores, contamos com diversas camadas de segurança na infraestrutura da AWS.
+
+Utilizamos AWS Security Groups, configuração ELB (Elastic Load Balancing) e roteamento VPC (Virtual Private Cloud) para obter funcionalidades de firewall em nossos sistemas. Essas medidas garantem que apenas o tráfego autorizado seja permitido em nossa rede, reforçando a segurança dos dados e dos serviços.
+
+Como a implantação de nossos aplicativos é automatizada e todos os logs são centralizados, nossa equipe não precisa de acesso direto aos servidores diariamente. O acesso ao ambiente de produção é normalmente feito através do console AWS ou de nossos próprios aplicativos web e APIs.
+
+Para garantir uma camada adicional de segurança, configuramos nossos Security Groups e ELBs para permitir apenas acesso HTTP e HTTPS para ELBs que expõem recursos publicamente. Caso seja necessário acesso adicional para alguma tarefa específica, podemos solicitar e disponibilizar temporariamente esse acesso de forma controlada e segura. Essas práticas garantem a integridade e a segurança de nossa infraestrutura de rede.
+
+### Quais controles a VTEX utiliza para mitigar ataques DDoS (Distributed Denial of Service)?
+
+Para mitigar ataques de negação de serviço distribuído (DDoS), a VTEX utiliza uma abordagem em duas camadas para defesa. A primeira camada está no nível de CDN (Content Delivery Network), onde são implementadas medidas de segurança para filtrar e bloquear tráfego malicioso antes que ele alcance a infraestrutura principal.
+
+Além disso, uma regra de limitação adaptativa é implementada no proxy frontal que fica na frente de cada um dos microsserviços da VTEX. Essa regra ajuda a detectar e limitar o tráfego malicioso ou excessivo, reduzindo assim o impacto de possíveis ataques DDoS.
+
+Além dessas medidas internas, a VTEX também se beneficia das proteções oferecidas pelo [AWS Shield](https://aws.amazon.com/pt/shield/), um serviço fornecido pela Amazon Web Services para proteção contra ataques DDoS. Essa combinação de estratégias em várias camadas fortalece significativamente a capacidade da VTEX de mitigar e responder a ataques DDoS, garantindo assim a disponibilidade e a integridade de seus serviços.
+
+Além das medidas de proteção padrão implementadas pela VTEX para mitigar ataques DDoS e outras ameaças, os clientes têm a opção de reforçar a segurança de suas lojas contratando um [Web Application Firewall (WAF)](https://help.vtex.com/es/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn), através da aquisição do produto adicional [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). O WAF oferece uma camada adicional de proteção, ajudando a filtrar e bloquear tráfego malicioso antes que ele atinja a loja. Essa solução personalizada permite que os clientes adaptem as medidas de segurança de acordo com suas necessidades específicas e garantam uma proteção mais robusta contra possíveis ataques cibernéticos. Mediante a aquisição do VTEX Shield, os lojistas podem garantir uma defesa abrangente e proativa para suas lojas online, proporcionando maior tranquilidade e confiança aos seus negócios digitais.
+
+### A VTEX possui IDS (Intrusion Detection System) e IPS (Intrusion Prevention System)? Se sim, com que frequência as regras são revisadas?
+
+Sim, a solução da VTEX inclui IDS (Intrusion Detection System) e IPS (Intrusion Prevention System). Esses sistemas desempenham um papel fundamental na detecção e prevenção de atividades maliciosas em nossa infraestrutura de rede e sistemas.
+
+As regras IDS e IPS são revisadas regularmente para garantir que estejam alinhadas com as últimas ameaças e vulnerabilidades conhecidas. Essa revisão é realizada com uma frequência significativa e é parte integrante de nosso processo de segurança. O objetivo é manter nossos sistemas atualizados e protegidos contra as mais recentes técnicas de ataque e vulnerabilidades emergentes.
+
+Essa prática de revisão constante das regras IDS e IPS reflete nosso compromisso com a segurança e a proteção dos dados de nossos clientes, garantindo que estejamos sempre um passo à frente das ameaças cibernéticas em constante evolução.
+
+## Gerenciamento de vulnerabilidades
+
+### Qual é o tempo de correção de vulnerabilidades?
+
+Nosso procedimento de gestão de vulnerabilidades é cuidadosamente elaborado para garantir uma abordagem eficaz na correção de potenciais falhas de segurança. Estabelecemos políticas internas que definem o tempo para correção, levando em consideração a criticidade e complexidade de cada vulnerabilidade identificada. Esse tempo varia para garantir que as vulnerabilidades mais críticas e urgentes sejam abordadas com prioridade, enquanto as menos graves possam ser tratadas de forma adequada, sem comprometer a segurança do sistema. Essa abordagem nos permite gerenciar de maneira eficiente os riscos de segurança e manter nossos sistemas protegidos contra possíveis ameaças.
+
+### A VTEX permite que os clientes realizem verificações de vulnerabilidade através de scans, varreduras e pentest independentes pré-organizadas por um consultor independente?
+
+As instâncias da VTEX são hospedadas na infraestrutura da AWS, o que impede a realização de auditorias pessoais nos sistemas. A AWS mantém [programas de conformidade](https://aws.amazon.com/compliance/programs/) rigorosos para garantir a segurança das instâncias.
+
+A VTEX não autoriza o acesso às suas instalações ou arquivos para condução de auditorias nos sistemas e procedimentos internos. Em vez disso, a VTEX obtém relatórios de uma empresa de auditoria especializada e independente. Para demonstrar conformidade e comprometimento com a privacidade, segurança, conformidade e governança, a VTEX disponibiliza documentos, políticas e certificações em seu [portal de segurança](https://vtex.com/us-en/trust/). Como parte de seu compromisso contínuo com a segurança, a VTEX busca constantemente obter novas certificações.
+
+Quanto às [varreduras de vulnerabilidades](https://help.vtex.com/pt/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb#reportar-vulnerabilidade), os clientes têm permissão para realizar tais testes em seus próprios ambientes, desde que sigam duas condições: não realizar ataques reais que possam derrubar sistemas de produção e não tentar acessar dados que não lhes pertençam.
+
+### Como o gerenciamento de vulnerabilidades é realizado de forma concreta? O processo está documentado? Até que ponto as vulnerabilidades identificadas são gerenciadas e corrigidas?
+
+As varreduras de vulnerabilidade são conduzidas de forma contínua, restritas a um grupo autorizado de indivíduos e utilizando sistemas aprovados e dedicados. No caso de identificação de vulnerabilidades no sistema ou software, empregamos um processo de gerenciamento de patches para realizar as correções necessárias. Nossa equipe coordena efetivamente todos os desenvolvedores envolvidos, ajudando na reprodução e, quando necessário, no desenvolvimento de patches de segurança. Após a implementação das correções, conduzimos testes adicionais para garantir a eficácia das soluções. Caso os resultados sejam positivos, encerramos o caso e, se necessário, realizamos uma análise detalhada semelhante à fase de Gerenciamento de Problemas.
+
+## Monitoramento de segurança
+
+### Os logs dos sistemas são protegidos contra alterações, falsificações ou acessos indevidos?
+
+Nossas aplicações são equipadas com sistemas de registro de auditoria que capturam e armazenam logs relevantes, garantindo a conformidade com nossas normas internas e legislações aplicáveis. Esses registros abrangem uma variedade de eventos, incluindo autenticação (falhas de login, sucessos e bloqueios de contas), em conformidade com exigências regulatórias, de segurança e privacidade, além de serem fundamentais para nossas análises internas. Dessa forma, mantemos um registro completo e detalhado de todas as atividades relevantes na plataforma, garantindo transparência, segurança e conformidade em nossas operações.
+
+### A VTEX registra eventos de segurança?
+
+Nossa organização utiliza uma ferramenta para centralizar os registros de atividades, além de empregá-la para implementar recursos de SIEM (Security Information and Event Management). Os registros são geralmente mantidos por um período de 18 meses. Tanto soluções próprias quanto aquelas fornecidas pela AWS são utilizadas para análise contínua de segurança e para examinar vulnerabilidades na nuvem. Quando não ocorre de maneira contínua, a utilização dessas ferramentas é realizada no mínimo trimestralmente.
+
+A responsabilidade de disponibilizar e manter a solução atualizada com novas funcionalidades é da equipe da VTEX, que também é encarregada de monitorar integralmente o funcionamento da solução. Além disso, contamos com uma equipe especializada que garante a capacidade de expansão da solução em períodos sazonais ou diante de um aumento na demanda, juntamente com um monitoramento constante do desempenho da loja com base em uma heurística própria.
+
+### A VTEX protege seu servidor de e-mail contra spoofing?
+
+A VTEX emprega o Google Workspace como sua ferramenta de comunicação primária. Com o objetivo de fortalecer a segurança do nosso servidor de e-mail contra a falsificação, implementamos medidas como o SPF (Sender Policy Framework) e o DKIM (DomainKeys Identified Mail). O SPF estabelece uma lista de servidores e domínios autorizados a enviar e-mails em nome da nossa organização, enquanto o DKIM adiciona uma assinatura digital única a cada mensagem enviada. Essas medidas garantem que os servidores de destino possam autenticar a origem das mensagens, oferecendo uma camada adicional de proteção contra possíveis atividades fraudulentas. Essas configurações são gerenciadas exclusivamente pelo time de Segurança da VTEX.
+
+### Os endpoints são protegidos com antivírus?
+
+Contamos com uma robusta tecnologia antivírus que integramos em todos os nossos endpoints e servidores. Esta medida é crucial para fortalecer a segurança não apenas da nossa infraestrutura, mas também para proteger os dados e informações sensíveis dos nossos clientes. Ao exigir a obrigatoriedade da instalação do antivírus em todos os dispositivos e servidores, estamos proativamente mitigando potenciais ameaças cibernéticas, garantindo assim uma experiência segura e confiável para todos os envolvidos em nossas operações.
+
+## Resposta e mitigação a incidentes
+
+### O Plano de Resposta a Incidentes determina critérios para notificação?
+
+Sim, como parte de nossos protocolos operacionais, nos comprometemos a notificar os clientes afetados dentro de um prazo máximo de 24 horas após a confirmação de qualquer incidente de segurança. Esta medida é essencial para garantir transparência e fornecer aos nossos clientes as informações necessárias para que possam tomar as medidas apropriadas para proteger seus próprios dados e sistemas. Além disso, ao agir rapidamente na divulgação de informações sobre incidentes de segurança, demonstramos nosso compromisso contínuo com a segurança cibernética e a confiança dos nossos clientes.
+
+## Disaster Recovery e continuidade de negócios
+
+### Qual é RTO (Recovery Time Objective) e RPO (Recovery Point Objetive) para recuperação de desastres?
+
+O Recovery Point Objective (RPO) é a idade máxima dos dados de backup antes de se tornarem obsoletos, estando diretamente vinculado à política de retenção de backup. O RPO padrão para a VTEX é de 24 horas. No entanto, é importante ressaltar que este tempo refere-se à frequência de backup do Catálogo, sendo que sistemas transacionais, como o Checkout, adotam abordagens que podem reduzir o ponto de recuperação para a última transação salva.
+
+O Recovery Time Objective (RTO) é o tempo máximo permitido para que os serviços sejam restaurados. O tempo de inatividade de um serviço pode ser ocasionado por interrupção do aplicativo, corrupção ou perda de dados, falha do servidor ou interrupção na zona ou região de disponibilidade da AWS. Confira a seguir o RTO padrão por tipo de inatividade:
+
+| Tipo de inatividade | RTO padrão |
+|---|---|
+| Interrupção do aplicativo | 10 minutos |
+| Corrupção de dados ou perda de dados | 30 minutos |
+| Falha no servidor de dados | 1 hora |
+| Interrupção da zona de disponibilidade da AWS | 4 horas |
+| Interrupção na região da AWS | 24 horas |
diff --git a/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 474c1e0f1..2165748a7 100644
--- a/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -17,7 +17,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Para entender melhor o significado de cada campo da planilha de cadastro de preço fixo, veja a descrição completa dos itens abaixo.
 
-![tabela.preço.fixo](https://images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
+![tabela.preço.fixo](//images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
 
 - **SKU ID:** ID do SKU que deseja adicionar o preço fixo.
 - **Trade Policy:** nome ou ID da política comercial em que o preço fixo será aplicado.
diff --git a/docs/tutorials/pt/filtering-all-orders.md b/docs/tutorials/pt/filtering-all-orders.md
index e6a865d08..507294ba7 100644
--- a/docs/tutorials/pt/filtering-all-orders.md
+++ b/docs/tutorials/pt/filtering-all-orders.md
@@ -3,8 +3,8 @@ title: 'Filtrar pedidos em Todos os pedidos'
 id: tutorials_192
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:05.494Z
-updatedAt: 2023-05-31T14:45:05.491Z
-publishedAt: 2023-05-31T14:45:05.491Z
+updatedAt: 2023-12-21T14:06:54.896Z
+publishedAt: 2023-12-21T14:06:54.896Z
 firstPublishedAt: 2017-04-27T23:00:47.449Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,13 @@ legacySlug: como-filtrar-pedidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
+<div class = "alert alert-info">
+É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
+</div>
+
 No módulo **Pedidos**, a página **Todos os pedidos** permite a você acessar os pedidos da sua loja e pesquisar usando a barra de busca e filtros, como na imagem abaixo:
 
-![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Este artigo explica como utilizar estes recursos e se divide em:
 
@@ -26,6 +30,13 @@ Este artigo explica como utilizar estes recursos e se divide em:
 - [Filtrar por status](#filtrar-por-status)
 - [Criado](#criado)
 
+Além de pesquisar pedidos em **Pedidos > Todos os pedidos**, você pode buscar pedidos a partir de qualquer página no Admin VTEX usando a barra de busca global no topo da página. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
+
 ## Barra de busca
 
 Para realizar a pesquisa na barra de busca, digite o termo desejado e aperte a tecla `enter`. Você pode buscar utilizando os seguintes critérios:
@@ -52,7 +63,7 @@ Buscar em todos os pedidos retorna a totalidade de pedidos relacionados ao crit
 
 Para buscar em todos os pedidos, digite o termo desejado na caixa de busca. Isso fará com que a opção <i class="fas fa-toggle-on"></i> `Remover limite de datas` se torne visível. Depois basta ativá-la e isso dará início à busca.
 
-![search_bar_without_time_limit_PT](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c87949487d1e9ad947ea437c3f368431/search_bar_without_time_limit_PT.png)
+![search_bar_without_time_limit_PT](//images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c87949487d1e9ad947ea437c3f368431/search_bar_without_time_limit_PT.png)
 
 <div class="alert alert-danger">
 A busca em todos os pedidos não pode ser associada a outros filtros. Ou seja, ao remover o limite de datas da busca, qualquer filtro ativo se torna inativo. Se o termo da busca é removido ou o switch <i class="fas fa-toggle-off"></i> de busca em todos os pedidos é desativado, os filtros anteriormente configurados se tornam ativos novamente.
@@ -70,7 +81,7 @@ Realizar uma busca associada a filtros permite que você combine diferentes filt
 
 Na página **Pedidos > Todos os pedidos**, existe a opção `Filtros`, conforme a imagem abaixo:
 
-![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Ao clicar em `Filtros`, um modal é aberto e apresenta as seguintes opções:
 
@@ -186,7 +197,7 @@ Para utilizar esses filtros, clique em `Filtros` e selecione **Outros**. Você p
 
 Na página **Pedidos > Todos os pedidos**, existe a opção `Filtrar por status` <i class="fas fa-angle-down"></i>, conforme imagem abaixo:
 
-![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Ao clicar em `Filtrar por status` <i class="fas fa-angle-down"></i>, aparecem as opções de [status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196) da sua loja. Por exemplo, se entre todos os seus pedidos não houver pedidos cancelados, esta opção não estará visível.
 
@@ -198,7 +209,7 @@ Para mais opções de filtros de status, veja a seção <a href="https://help.vt
 
 Na página **Pedidos > Todos os pedidos**, existe a opção `Criado: Hoje` <i class="fas fa-angle-down"></i>, conforme imagem abaixo:
 
-![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Este filtro tem a data **Hoje** ativada de forma padrão, mas ao clicar nele aparecem as seguintes opções:
 
diff --git a/docs/tutorials/pt/filtering-data-on-master-data.md b/docs/tutorials/pt/filtering-data-on-master-data.md
index 3dec5ed59..cd198729d 100644
--- a/docs/tutorials/pt/filtering-data-on-master-data.md
+++ b/docs/tutorials/pt/filtering-data-on-master-data.md
@@ -3,8 +3,8 @@ title: 'Filtrar dados no Master Data'
 id: tutorials_778
 status: PUBLISHED
 createdAt: 2017-04-27T21:58:11.041Z
-updatedAt: 2023-03-28T23:42:30.477Z
-publishedAt: 2023-03-28T23:42:30.477Z
+updatedAt: 2024-06-27T00:07:07.554Z
+publishedAt: 2024-06-27T00:07:07.554Z
 firstPublishedAt: 2017-04-27T23:03:42.905Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,40 +15,54 @@ legacySlug: filtrando-dados-no-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-No Master Data, é possível criar filtros tanto para acesso por API quanto para a visualização nos formulários. A criação de filtros facilita a busca e consulta de dados, possibilitando um maior controle sobre seus dados. A criação de filtro deve  ser configurada primeiro na entidade de dados e posteriormente no formulário desejado. O requisito para que um campo seja configurado como filtro é que não sejam usados os tipos CEP, Text e File. Além disso, é uma boa prática colocar como filtro um campo que contenha poucas opções em seu preenchimento, como “Categoria”, por exemplo.
+No Master Data, é possível criar filtros tanto para acesso por API quanto para a visualização nos formulários. A criação de filtros facilita a busca e consulta de dados, possibilitando um maior controle sobre seus dados.
 
-## Como configurar filtro na Entidade de Dados
+A criação de filtro deve ser configurada primeiro na entidade de dados e posteriormente no formulário desejado, conforme os passos descritos nas seções a seguir.
+
+## Requisitos para filtros
+
+Siga as recomendações abaixo ao definir campos como filtros:
+
+- Não utilize campos dos tipos **CEP**, **Text** e **File** como filtros.
+- Adicione como filtro um campo que contenha poucas opções em seu preenchimento, como "Categoria", por exemplo.
+
+## Configurar filtro na entidade de dados
+
+Siga as instruções abaixo para definir um campo existente como filtro na entidade de dados:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. No Master Data, clique na engrenagem <i class="fas fa-cog"></i> ao lado de uma aplicação.
+3. Clique em **Estrutura de dados**.
+4. Acesse a aba **Entidades de dados.**
+5. Clique no botão de edição <i class="fas fa-edit"></i> na entidade em que deseja configurar o filtro.
+
+   Você será direcionado(a) para a listagem de campos da entidade.
+6. Clique no botão com símbolo de engrenagem <i class="fas fa-cog"></i> no campo que deseja configurar como filtro.
+7. Marque a opção **É filtrável?**.
+8. Clique no botão `Salvar`.
+9. Na listagem de entidades, clique no botão de disquete <i class="fas fa-save"></i> para publicar a entidade.
+10. Clique no botão de reindexação <i class="fas fa-expand-arrows-alt"></i> para indexar a entidade.
+
+## Configurar filtro no formulário
+
+Siga as instruções abaixo para configurar filtros no formulário:
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Na aplicação em que está o formulário onde deseja criar o filtro, clique no símbolo de engrenagem <i class="fas fa-cog"></i>.
+
+   Você será direcionado(a) para a listagem de formulários da aplicação.
+3. Clique no botão de edição <i class="fas fa-edit"></i> na linha do formulário que deseja editar.
+4. Preencha o campo **Filtros** com o nome interno do campo marcado como filtro. O nome interno corresponde ao valor do primeiro campo na criação e edição de entidade de dados, o nome do campo que não é possível alterar. Para inserir mais de um valor, separe-os por vírgula, sem espaço.
+5. Clique no botão `Salvar`.
+
+## Filtrar registros do formulário
+
+Após a criação do filtro, é possível utilizá-lo no formulário. Para isso, siga o passo a passo abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. No Master Data, clique em **Aplicações** > **Estrutura de dados**.
-3. Acesse a aba **Entidade de Dados.**
-4. Clique no botão **editar** na entidade que deseja configurar o filtro;
-5. Abrirá a listagem de campos.
-6. Clique no botão com símbolo de engrenagem no campo que deseja configurar;
-7. Marque a opção **É filtro.**
-8. Clique no botão **Salvar.**
-9. Na listagem de entidades, clique no botão **Publicar**, com símbolo de disquete.
-10. Aguarde a publicação e reindexação dos dados para visualizar o filtro.
-
-## Como configurar filtro no formulário
-
-1. Acesse o módulo **Master Data**;
-2. Clique na aba **Aplicações**;
-3. Na aplicação em que está o formulário onde deseja criar o filtro, clique no símbolo de engrenagem;
-4. Abrirá a listagem de formulários, clique no símbolo lápis no formulário que deseja editar;
-5. Preencha o campo **Filtros** com o nome interno do campo marcado como Filtro. Entende-se nome interno como a primeira coluna na criação e edição de entidade de dados, o nome que não é possível alterar. Para inserir mais de um valor, basta separá-los por vírgula, sem espaço;
-6. Clique no botão **Salvar**.
-
-## Como filtrar
-
-Após a criação do filtro é possível utilizá-lo no formulário. Para isso, siga o passo-a-passo abaixo.
-
-1. Acesse o módulo **Master Data**;
-2. Clique na aba **Aplicações**;
-3. Na aplicação desejada, identifique o formulário que deseja visualizar;
-4. No formulário desejado, clique no ícone de listagem;
-5. Abrirá a página com a listagem de registros desse formulário. Na lateral, você verá os filtros configurados. 
-6. Para filtrar, basta clicar no nome do filtro e em seu valor. 
-7. Para verificar o resultado no filtro, role a página para baixo e clique no botão **Filtrar**.
-8. É possível filtrar por vários campos ao mesmo tempo e vários valores no mesmo campo. Para retirar um filtro, basta clicar no símbolo **x** ao lado do valor.
+2. Na aplicação desejada, identifique o formulário que deseja visualizar e clique no ícone de listagem <i class="fas fa-bars"></i>.
+
+   Você será direcionado(a) para a listagem de registros desse formulário. Na lateral, você verá os filtros configurados. 
+3. Para filtrar, selecione o nome do filtro e seu valor e, em seguida, clique em `Filtrar`.
 
+   É possível filtrar por vários campos ao mesmo tempo e vários valores no mesmo campo. Para retirar um filtro, clique no `X` ao lado do valor.
diff --git a/docs/tutorials/pt/filtering-transactions-on-pci-gateway.md b/docs/tutorials/pt/filtering-transactions-on-pci-gateway.md
index 0c5642b52..3f938632f 100644
--- a/docs/tutorials/pt/filtering-transactions-on-pci-gateway.md
+++ b/docs/tutorials/pt/filtering-transactions-on-pci-gateway.md
@@ -3,8 +3,8 @@ title: 'Filtrar transações na seção de Pedidos'
 id: 6LUq65FqUgIKkKEeWa4IwC
 status: PUBLISHED
 createdAt: 2019-01-24T21:38:42.313Z
-updatedAt: 2023-03-26T21:29:36.950Z
-publishedAt: 2023-03-26T21:29:36.950Z
+updatedAt: 2023-10-18T16:58:56.709Z
+publishedAt: 2023-10-18T16:58:56.709Z
 firstPublishedAt: 2019-01-24T21:38:42.695Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/filters.md b/docs/tutorials/pt/filters.md
new file mode 100644
index 000000000..a66695dc5
--- /dev/null
+++ b/docs/tutorials/pt/filters.md
@@ -0,0 +1,51 @@
+---
+title: 'Filtros'
+id: k24mQQa9SjmhNWSwdqIMB
+status: PUBLISHED
+createdAt: 2024-06-27T16:43:43.811Z
+updatedAt: 2024-06-27T16:44:34.723Z
+publishedAt: 2024-06-27T16:44:34.723Z
+firstPublishedAt: 2024-06-27T16:44:34.723Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: filtros
+locale: pt
+legacySlug: filtros
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+Filtros é a funcionalidade que exibe, de forma agrupada, as especificações dos resultados de uma busca. Ela permite que o cliente explore características relevantes de um produto durante a experiência de busca, além de proporcionar cenários que facilitam a tomada de decisão do usuário.
+
+Quando um cliente seleciona um filtro (preço, cor, tamanho e marca), essa informação é utilizada para restringir tanto os itens apresentados no resultado de busca quanto os demais filtros existentes neste contexto de busca.
+
+O **VTEX Intelligent Search** usa o contexto dos produtos apresentados como resultados de busca para saber exatamente quais filtros devem ser exibidos para o cliente, seguindo as configurações do Catálogo.
+
+<div class="alert alert-info">
+  <p>A ordenação dos filtros de marca, departamento, categoria e subcategoria é determinada pela quantidade de produtos cadastrados em cada um dos filtros.</p>
+</div>
+
+Exemplo: considere que o filtro *Tamanho* está cadastrado no catálogo de uma loja e somente o produto *tênis* possui a especificação *Tamanho* preenchida. Em uma pesquisa pelo termo *tênis*, *Tamanho* vai aparecer como um filtro. Já em uma pesquisa por qualquer outro termo, como *boné*, essa especificação não vai ser exibida como filtro.
+
+O resultado de busca não vai exibir uma especificação quando só existe ela como filtro ou o cliente a tenha acessado pelo menu da loja. Exemplo: se um cliente seleciona o filtro  Eletrodomésticos diretamente do menu, não será exibido Departamentos como um filtro lateral.
+
+<div class="alert alert-info">
+  <p>Caso o resultado da busca retorne mais de 30 mil produtos, alguns valores de filtros serão omitidos, uma vez que somente as especificações de uma parte desses produtos serão consideradas.</p>
+</div>
+
+A funcionalidade de Filtros apresenta as seguintes funções:
+
+- Pesquisa que possibilita ao cliente buscar um termo dentro de um filtro.
+- Configurar e definir a quantidade máxima de opções em um filtro antes de gerar rolagem.
+- Configurar qual o layout em que um filtro será exibido. É possível escolher entre os seguintes formatos:
+
+   - Listagem vertical (formato padrão).
+   - Listagem horizontal: utilizada para exibir filtros como Tamanho e Cor.
+   - Barra deslizante: utilizada para alternar do preço mínimo para o máximo.
+   - Entrada de valores: permite ao cliente informar o preço “De” e “Até” que será usado para filtragem.
+
+Confira o guia [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) no Developer Portal para mais detalhes técnicos sobre a utilização de filtros.
+
+<div class="alert alert-warning">
+  <p>Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.</p>
+</div>
diff --git a/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
index 082277afe..6533869dc 100644
--- a/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -1,10 +1,10 @@
 ---
 title: 'Marketplace Network: encontre marketplaces e sellers no ecossistema VTEX'
 id: 2bzC7tXlVgLEEjxo4ixcAM
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-09-14T22:21:50.677Z
-updatedAt: 2022-04-07T14:44:29.576Z
-publishedAt: 2022-04-07T14:44:29.576Z
+updatedAt: 2023-07-19T21:34:02.498Z
+publishedAt: 
 firstPublishedAt: 2020-09-14T23:03:21.356Z
 contentType: tutorial
 productTeam: Apps
@@ -21,7 +21,7 @@ Note que o Marketplace Network é uma ferramenta que promove o contato entre pot
 
 ## Encontrar Sellers e Marketplaces
 
-![Marketplace network tour](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
+![Marketplace network tour](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
 
 Para acessar a listagem de marketplaces e sellers cadastrados navegue em *Marketplace > Marketplace Network > Encontrar Sellers / Encontrar Marketplaces*. Em ambas abas, é possível  buscar por palavras-chave e filtrar a lista para obter resultados mais precisos, além de entrar em contato com potenciais parceiros.
 
@@ -44,7 +44,7 @@ O potencial parceiro comercial receberá um e-mail com as informações preenchi
 </div>
 
 ## Perfil da loja
-![Network profile PT](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/3566eb996b94604d3449fa0ae773cf27/Marketplace_store_profile_PT.gif)
+![Network profile PT](//images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/3566eb996b94604d3449fa0ae773cf27/Marketplace_store_profile_PT.gif)
 
 1. Na seção *Marketplace* da sua loja, clique em __Marketplace Network__.  
 2. Clique na aba __Perfil da Loja__.  
diff --git a/docs/tutorials/pt/find-sellers.md b/docs/tutorials/pt/find-sellers.md
new file mode 100644
index 000000000..ab497c4dc
--- /dev/null
+++ b/docs/tutorials/pt/find-sellers.md
@@ -0,0 +1,56 @@
+---
+title: 'Encontrar Sellers'
+id: 6kkZaxIgfDyvN5trgIuwBl
+status: PUBLISHED
+createdAt: 2023-07-19T20:18:59.741Z
+updatedAt: 2023-07-19T20:46:01.656Z
+publishedAt: 2023-07-19T20:46:01.656Z
+firstPublishedAt: 2023-07-19T20:41:17.099Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: encontrar-sellers
+locale: pt
+legacySlug: encontrar-sellers
+subcategory: 6riYYNZCpO8wyksi8Ksgyq
+---
+
+Apágina **Encontrar sellers** disponibiliza e facilita o encontro e a comunicação com sellers que operam no ecossistema VTEX,abrindo a possibilidade de novos negócios e crescimento mútuo para todos os envolvidos. Apágina funciona como um catálogo de interessados em parcerias,permitindo o cadastro,consulta e contato entre marketplaces e sellers para firmarem seus acordos comerciais.
+
+Para utilizar a página,você precisa criar um **Perfil da loja,** saiba como acessando a documentação.
+
+<div class="alert alert-info">
+Note que a <b>Encontra sellers</b> é uma ferramenta que promove o contato entre potenciais parceiros,mas não é uma etapa obrigatória para atuar como Marketplace e seller na VTEX. Se você deseja atuar como marketplace e seller simultaneamente,leia a documentação <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace">Estratégias de marketplace na VTEX</a>.
+</div>
+
+Para acessar a listagem de sellers cadastrados navegue em **Marketplace > Encontrar Sellers** ou digite **Encontrar Sellers** na barra de busca.
+
+## Buscar e Filtrar
+
+Na página é possível utilizar a barra de busca da página para realizar buscas por nome do seller ou nome da conta VTEXe filtrar de maneira combinada ou individual a lista para obter resultados mais precisos e contactar potenciais parceiros.
+
+**Filtros fixos**
+
+- País
+- Segmento
+
+**Filtro condicionado**
+
+- Região
+
+## Contato
+
+Apágina **Encontrar Seller** permite o contato direto com potenciais parceiros. Clicando nos perfis da lista, é possível ter acesso ao cadastro detalhado do seller. Note que só é possível enviar uma mensagem após ativar o seu **Perfil de loja**.
+
+Ao enviar uma mensagem, considere todas as informações que aquele seller precisa saber para conectar-se ao seu negócio. Sugerimos também já adiantar as dúvidas, ou pontos a serem levantados em uma futura reunião, por exemplo.
+
+Para entrar em contato:
+
+1. Na seção Marketplace do seu Admin VTEX,clique em **Encontrar Sellers** ou digite **Encontrar Sellers** na barra busca.
+2. Na lista, clique no **perfil** de um potencial parceiro.
+3. Preencha o campo **Entrar em contato com o seller**.
+4. Clique no botão **Enviar**.
+
+<div class="alert alert-info">
+O potencial parceiro comercial receberá um e-mail com as informações preenchidas. Caso o interesse seja mútuo, o encarregado pelo seller ou marketplace poderá entrar em contato e negociar os termos do acordo entre marketplace e seller.
+<div>
diff --git a/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
index 44ae01702..280abdb25 100644
--- a/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
@@ -26,7 +26,7 @@ A partir de 1 de fevereiro de 2023, a nova interface será o padrão de todas as
 
 Você pode visualizar a correspondência de seções e campos entre a versão antiga da página **Detalhes do pedido** e a nova versão na imagem abaixo:
 
-![board_comparativo_interface_pedido_v2_pt](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
+![board_comparativo_interface_pedido_v2_pt](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
 
 ## O que aconteceu com o filtro de busca de seis meses?
 
@@ -38,17 +38,17 @@ A busca em todos os pedidos não pode ser associada a outros filtros, portanto,
 
 Para buscar em todos os pedidos, digite o termo desejado na caixa de busca. Isso fará com que a opção <i class="fas fa-toggle-off"></i> `Remover limite de datas` se torne visível. Depois basta ativá-la e isso dará início à busca.
 
-![busca_sem_limite_data_all_pt](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
+![busca_sem_limite_data_all_pt](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
 
 ## Como visualizar o diagrama de fluxo do pedido?
 
 Na nova interface, por padrão, o que é exibido é uma linha tempo com os eventos de **Status do pedido**, como na imagem abaixo:
 
-![timeline_pedido_pt](https://images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/c062ec0b49a67aaecd9856a5bbec865b/timeline_pedido_pt.png)
+![timeline_pedido_pt](//images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/c062ec0b49a67aaecd9856a5bbec865b/timeline_pedido_pt.png)
 
 Caso você deseje ver o **Diagrama do pedido** como na interface antiga, clique em `Ver diagrama` e um modal como o da imagem abaixo vai aparecer:
 
-![diagrama_pedido_pt](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
+![diagrama_pedido_pt](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
 
 ## Como faturar o pedido?
 
@@ -56,7 +56,7 @@ Na seção **Itens a faturar** da nova interface, todas as ações relacionadas
 
 * **Enviar nota fiscal referenciando itens:** esta opção é exclusiva da nova interface. Por meio dela, é possível emitir a nota fiscal total ou parcial de determinados itens, que são identificados por SKU, estoque e preço. Veja um exemplo na imagem a seguir:
 
-![faturar_referenciar_pedidos_final_pt](https://images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/cef5f7a10b488a14945a0f210d464aea/faturar_referenciar_pedidos_final_pt.png)
+![faturar_referenciar_pedidos_final_pt](//images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/cef5f7a10b488a14945a0f210d464aea/faturar_referenciar_pedidos_final_pt.png)
 
 * **Enviar nota fiscal avulsa:** a opção corresponde ao antigo _Enviar nota fiscal_ e permite faturar o valor total ou parcial do pedido. A apresentação da página é diferente, mas os campos permanecem os mesmos.
 
@@ -75,6 +75,6 @@ Na nova interface, dentro da seção **Histórico do pedido**, existe uma linha
 
 Para reenviar um email para o cliente, clique no evento de email enviado ou no ícone seta <i class="fas fa-angle-right"></i> para ver os detalhes do evento, que vão aparecer como na imagem a seguir:
 
-![enviar_email_pt](https://images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/f59d8a815163c889d8af29cd4e04ccbd/enviar_email_pt.png)
+![enviar_email_pt](//images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/f59d8a815163c889d8af29cd4e04ccbd/enviar_email_pt.png)
 
 Clique sobre o botão `Reenviar email` e o email será imediatamente enviado ao cliente, sendo que a seguinte mensagem de confirmação deve aparecer: _Email reenviado ao cliente com sucesso_.
diff --git a/docs/tutorials/pt/fulfillment-logistics-vtex.md b/docs/tutorials/pt/fulfillment-logistics-vtex.md
index 98a72a504..50205d747 100644
--- a/docs/tutorials/pt/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/pt/fulfillment-logistics-vtex.md
@@ -47,7 +47,7 @@ Para saber quais configurações logísticas são necessárias e como são reali
 Note que o processo de envio dependerá das configurações realizadas na plataforma. Aqui apresentamos  os cenários para cada tipo de envio (entrega e retirada), mas há outros fluxos possíveis no processo de envio. Por exemplo, quando o envio é por retirada e o estoque coincide com o ponto de retirada, não é necessário o transporte dos pacotes entre esses locais.
 </div>
 
-![Envio PT](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/186ee5138e0d5d412c9eb50890708241/Envio_PT.svg)
+![Envio PT](//images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/186ee5138e0d5d412c9eb50890708241/Envio_PT.svg)
 
 ## Configuração do processo logístico
 
diff --git a/docs/tutorials/pt/fulfillment-magalu.md b/docs/tutorials/pt/fulfillment-magalu.md
new file mode 100644
index 000000000..c9ecf24c1
--- /dev/null
+++ b/docs/tutorials/pt/fulfillment-magalu.md
@@ -0,0 +1,126 @@
+---
+title: 'Fulfillment Magalu'
+id: 7ckyEv4Z8HmiCRydo0a9P6
+status: PUBLISHED
+createdAt: 2023-12-19T19:09:47.849Z
+updatedAt: 2024-01-05T11:58:20.772Z
+publishedAt: 2024-01-05T11:58:20.772Z
+firstPublishedAt: 2023-12-19T19:44:22.896Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: fulfillment-magalu
+locale: pt
+legacySlug: fulfillment-magalu
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+Ao finalizar a [integração](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y/3tZ4qVuMDDsC2jx2DCmjdA) de uma loja VTEX com o Magalu, um seller poderá compartilhar produtos, gerenciar os pedidos realizados no marketplace, as atualizações de preços e produtos, pontos de retirada e o inventário dos produtos em um só lugar.
+
+Além da integração básica, lojistas VTEX podem integrar com o [**Fulfillment Magalu**](https://unimagalu.com.br/full/), que é um serviço disponível a lojistas que já vendem no Magalu Marketplace. Este serviço disponibiliza a operação de armazenamento e entrega do Magalu para seus produtos mais vendidos no marketplace. 
+
+<div class="alert alert-warning">
+Somente os produtos mais vendidos de uma loja, podem ser configurados com a opção de venda pelo Fulfillment Magalu.
+</div>
+
+Todos os pedidos do tipo __Fulfillment Magalu__ podem ser acompanhados na tela de [Pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi) do Admin VTEX. O status desses pedidos são atualizados pelo Magalu Marketplace.
+
+A integração do __Fulfillment Magalu__ é realizada em duas etapas. A primeira no [Portal do Magalu Marketplace](https://id-b2b.magazineluiza.com.br/auth/realms/B2B/protocol/openid-connect/auth?client_id=IntegraCommerceSellerAdmin&redirect_uri=https%3A%2F%2Fmarketplace.integracommerce.com.br%2Fsignin-oidc&response_type=code&scope=openid%20profile&code_challenge=LErEEj7Fo5Co8kOL4VDcRAeUVe2_hBSAf6XWp8Yi73Q&code_challenge_method=S256&response_mode=form_post&nonce=638370459880846758.NmY3MDExZTktZjNkYS00MzdkLWJhYTgtYzQ5NTkwODFmMWMzZTQwYTkzZmEtNmIwYS00YzY0LWI3OGUtMjU0N2UwZjY1ZjBm&state=CfDJ8DRkmEyrufZLvRHl0B2Huu7ARClKg-kKgAsabRC2I3CtY-Lj13FW-3H6S_acQCTyqkPti4gubm7t1KrgKRP1sXinoXungxBiDW13Zm6pVwAy4omo7a4HHmnptzufXd1mfk5_Srcu7MuRUNCjWBFuHadXUitLTldPanEbhMIHXgOBVjVdlvaZx8e7z2nomNUOGYLwbkNrLA2LeVDyvuEA9_8bGoMBgyyom4758NUzlG6Mx2CuQA3ZXnu83jDjikNyJXcGWHCLG6K8xqfptz9mIjoQeDzCDNxLolol3H0CikIh1O1rPxVHRNxL8-xT_3GhGtpL8w2ZjhwiPbn8frTZgaGvgyzGJq-dI9u49Uksbye6QLvesWt_uBXy9b-77BHbf7wlEDkG8dwtkkE3mzV_Ubc&x-client-SKU=ID_NETSTANDARD2_0&x-client-ver=6.8.0.0) e a segunda no Admin VTEX. Veja abaixo as etapas.
+
+## 1. Cadastro no Magalu
+
+Para o cadastro no Magalu Marketplace siga os seguintes passos:
+
+1. Acesse o [Portal do Magalu marketplace](https://id-b2b.magazineluiza.com.br/auth/realms/B2B/protocol/openid-connect/auth?client_id=IntegraCommerceSellerAdmin&redirect_uri=https%3A%2F%2Fmarketplace.integracommerce.com.br%2Fsignin-oidc&response_type=code&scope=openid%20profile&code_challenge=LErEEj7Fo5Co8kOL4VDcRAeUVe2_hBSAf6XWp8Yi73Q&code_challenge_method=S256&response_mode=form_post&nonce=638370459880846758.NmY3MDExZTktZjNkYS00MzdkLWJhYTgtYzQ5NTkwODFmMWMzZTQwYTkzZmEtNmIwYS00YzY0LWI3OGUtMjU0N2UwZjY1ZjBm&state=CfDJ8DRkmEyrufZLvRHl0B2Huu7ARClKg-kKgAsabRC2I3CtY-Lj13FW-3H6S_acQCTyqkPti4gubm7t1KrgKRP1sXinoXungxBiDW13Zm6pVwAy4omo7a4HHmnptzufXd1mfk5_Srcu7MuRUNCjWBFuHadXUitLTldPanEbhMIHXgOBVjVdlvaZx8e7z2nomNUOGYLwbkNrLA2LeVDyvuEA9_8bGoMBgyyom4758NUzlG6Mx2CuQA3ZXnu83jDjikNyJXcGWHCLG6K8xqfptz9mIjoQeDzCDNxLolol3H0CikIh1O1rPxVHRNxL8-xT_3GhGtpL8w2ZjhwiPbn8frTZgaGvgyzGJq-dI9u49Uksbye6QLvesWt_uBXy9b-77BHbf7wlEDkG8dwtkkE3mzV_Ubc&x-client-SKU=ID_NETSTANDARD2_0&x-client-ver=6.8.0.0).  
+2. No menu Fulfillment clique em `Quero aderir ao fulfillment`.  
+3. Preencha o formulário de adesão.  
+4. Clique em `Enviar`.  
+
+Após finalizar os passos indicados acima, aguarde o contato da equipe do Magalu para assinar o contrato e finalizar a configuração no Portal do Magalu Marketplace.  
+
+## 2. Cadastro no Admin VTEX
+Com a funcionalidade Fulfillment Magalu configurada no Portal do Magalu Marketplace, realize as seguintes configurações no Admin VTEX:
+
+1. [Configuração da loja](#configuracao-da-loja)
+2. [Configuração dos SKUs](#configuracao-dos-skus)
+3. [Configuração do conector](#configuracao-do-conector)
+
+### Configuração da loja
+
+Configure a loja conforme os passos abaixo:
+
+__1. Cadastre Política de Envio:__ a nova [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) deve cumprir os seguintes requisitos:
+
+- Ser exclusiva para o Fulfillment Magalu.  
+- Abranger todos os CEPs do país.  
+- Ser aplicável a todos os dias da semana.  
+
+Siga o tutorial para [Cadastrar uma Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio).  
+
+__2. Cadastre uma Doca:__ para cadastrar nova Doca, siga o tutorial [Gerenciar Doca](https://help.vtex.com/pt/tutorial/managing-loading-docks--7K3FultD8I2cuuA6iyGEiW#cadastrar).  
+__3. Cadastre um Estoque:__ o estoque dos produtos disponibilizados com a opção Fulfillment Magalu é gerenciado pela Magalu, mas o gerenciamento de inventário é realizado pelo seller. Siga o tutorial [Gerenciar Estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#cadastrar-estoque) para cadastrar um novo.  
+
+### Configuração dos SKUs
+
+Para disponibilizar produtos com Fulfillment Magalu, você deve aplicar uma especificação de produto. Siga o tutorial [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106#tipos-de-campo-de-produto) e preencha as informações conforme a tabela abaixo.
+
+| **Campo** | **Como preencher** |
+|:---:|:---:|
+| **Nome*** | `magalu_fulfillment` |
+| **Texto*** | Para produtos que serão ofertados via Fulfillment Magalu. |
+| **Tipo*** | É obrigatório que o tipo dessa especificação seja __Texto.__ |
+| **Valor Padrão** | Deixar o campo vazio. |
+| **Grupo*** | Especificações. |
+| **Filtro** | Não selecionar a caixa de seleção. |
+| **Obrigatório** | Não selecionar a caixa de seleção. |
+| **Exibe Especificação** | Não selecionar a caixa de seleção. |
+| **Link no Menu Superior** | Não selecionar a caixa de seleção. |
+| **Link no Menu Lateral** | Não selecionar a caixa de seleção. |
+| **Ativo** | Selecionar a caixa de seleção. |
+
+Por fim, é necessário preencher as especificações de cada produto a partir dos campos e valores que você criou. Você pode fazer isso individualmente pela página de cadastro do produto ou massivamente por planilha.
+
+#### Cadastro do produto  
+
+Para preencher as especificações de cada produto individualmente, siga as instruções abaixo:  
+
+1. No Admin VTEX, acesse Catálogo, ou digite Catálogo na barra de busca no topo da página.  
+2. Acesse __Todos os produtos.__  
+3. Na linha do produto, clique em `Alterar`.  
+4. Acesse a aba __Especificações.__  
+5. Preencha o campo que você criou com o valor `true`.  
+6. Clique em `Salvar`.  
+
+#### Planilha  
+
+Para preencher especificações de produtos em massa por planilha, é necessário exportar a planilha padrão VTEX, preenchê-la e importá-la na plataforma. Para fazer isso, siga as instruções abaixo:  
+
+1. No Admin VTEX, acesse __Catálogo,__ ou digite __Catálogo__ na barra de busca no topo da página.  
+3. Clique em __Importação e Exportação.__  
+4. Clique na aba __Especificações de produto.__  
+5. Clique com o botão direito na categoria desejada.  
+6. Clique em __Exportar.__ Um retângulo verde aparecerá na tela.  
+7. Clique em __Clique aqui para baixar o arquivo__ para exportar a planilha.  
+8. Para cada produto que deseja disponibilizar com o Fulfillment Magalu preencha a coluna `ValoreEspecificaCao` com o valor `true`. As demais colunas deverão permanecer inalteradas, pois seus valores serão utilizados para validação dos dados.  
+9. No Admin VTEX, ainda em __Catálogo > Importação e Exportação > Especificações de produto,__ desça a página até __Upload de Arquivo para Importação.__  
+10. Clique em __Select__ para selecionar o arquivo com a planilha preenchida no seu computador.  
+11. Clique em `Importar`.  
+
+<div class="alert alert-danger">
+  Os SKUs que estiverem com o valor da especificação <code> magalu_fulfillment</code> preenchida como <code> false </code> ou um valor diferente de <code> true</code>, não serão apresentados no Magalu marketplace com a opção de envio Fulfillment Magalu.
+</div>
+
+### Configuração do conector  
+
+Com as etapas de [Configuração da loja](#configuracao-da-loja) e [Configuração dos SKUs](#configuracao-dos-skus) finalizadas, você pode editar o conector da integração Loja VTEX e Magalu marketplace. Para esse processo siga os seguintes passos:  
+
+1. No Admin VTEX, acesse o módulo __Marketplace > Conexões > Marketplaces e integrações.__
+2. Clique no marketplace `Magazine Luiza`.
+3. No modal que aparecerá, clique em `Conectar`.
+4. Habilite a funcionalidade __Fulfillment Magalu.__
+5. Preencha o campo `Estoque do fulfillment` com o Id do estoque cadastrado em Configuração da loja.
+6. Clique em `Salvar`.
+
+![Fulfillment magalu](//images.ctfassets.net/alneenqid6w5/5boAjRcCbzyFflEolDZaFu/fc0e47a429a0ef940f5f20dd1c0db747/Screenshot_2023-12-08_at_13.26.50__1_.png)  
+
+Ao finalizar o processo de configuração do conector, os seus produtos configurados estarão disponíveis no Magalu Marketplace com a opção de envio __Fulfillment Magalu.__
diff --git a/docs/tutorials/pt/general-configurations-on-the-oms.md b/docs/tutorials/pt/general-configurations-on-the-oms.md
index cd14bad7d..ecc3a3f82 100644
--- a/docs/tutorials/pt/general-configurations-on-the-oms.md
+++ b/docs/tutorials/pt/general-configurations-on-the-oms.md
@@ -3,8 +3,8 @@ title: 'Configurações Gerais dos pedidos'
 id: tutorials_194
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:49.644Z
-updatedAt: 2023-03-29T16:11:56.900Z
-publishedAt: 2023-03-29T16:11:56.900Z
+updatedAt: 2024-07-02T19:07:22.178Z
+publishedAt: 2024-07-02T19:07:22.178Z
 firstPublishedAt: 2017-04-27T23:00:47.468Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -19,7 +19,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 No Admin VTEX, acesse **Configurações da loja > Pedidos > Configurações**, ou digite *Pedidos* na barra de busca no topo da página e e selecione *Configurações da loja / Pedidos*. 
 
-![configuracoes_pedidos_pt](https://images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/743fdbe79371cf6f3f7a43ca340102d2/configuracoes_pedidos_pt.png)
+![configuracoes_pedidos_pt](//images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/743fdbe79371cf6f3f7a43ca340102d2/configuracoes_pedidos_pt.png)
 
 ## Carrinho
 
diff --git a/docs/tutorials/pt/geolocalizado-suiteshare.md b/docs/tutorials/pt/geolocalizado-suiteshare.md
index e373de4f5..af1193ea7 100644
--- a/docs/tutorials/pt/geolocalizado-suiteshare.md
+++ b/docs/tutorials/pt/geolocalizado-suiteshare.md
@@ -27,17 +27,17 @@ Uma empresa que possui lojas em vários cidades (Ex: São Paulo, Rio de Janeiro,
 
 Para começar você deve ter [criado os links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB)  que serão utilizados no seu atendimento e um link âncora.  Depois de ter criado os links no painel do VTEX Assisted Sales (SuiteShare), acesse a opção _**Organizar > Geolocalização.**_
 
-![Geolocalizado 1](https://images.ctfassets.net/alneenqid6w5/4l9dgcmAdSNdgj0PUaKVC8/db334a7cdc6a13954e62d94fbd7ebb0a/Screenshot_2022-08-29_at_17-59-43_Geolocalizado.png)
+![Geolocalizado 1](//images.ctfassets.net/alneenqid6w5/4l9dgcmAdSNdgj0PUaKVC8/db334a7cdc6a13954e62d94fbd7ebb0a/Screenshot_2022-08-29_at_17-59-43_Geolocalizado.png)
 
 Clique em _**“Novo”**_.
 
-![Geolocalizado 2](https://images.ctfassets.net/alneenqid6w5/4Q7Q0Rnkz4UYR85akhHQAh/78deaaef0fc5a328b5bee90eb3a043fb/Screenshot_2022-08-29_at_17-59-47_Geolocalizado.png)
+![Geolocalizado 2](//images.ctfassets.net/alneenqid6w5/4Q7Q0Rnkz4UYR85akhHQAh/78deaaef0fc5a328b5bee90eb3a043fb/Screenshot_2022-08-29_at_17-59-47_Geolocalizado.png)
 
 Em **Link Âncora**, como o próprio nome já diz, você irá selecionar o link principal da central. Esse é o link que você irá divulgar e que os clientes irão clicar. 
 
 **Nota**: Esse será o link responsável por fazer a ligação com os demais atendentes.
 
-![Geolocalizado 3](https://images.ctfassets.net/alneenqid6w5/1VNj6ggD6sFyXtYDojXVKv/aacec6cba54332300bfc899de4c0fed5/Screenshot_2022-08-29_at_17-59-51_Geolocalizado.png)
+![Geolocalizado 3](//images.ctfassets.net/alneenqid6w5/1VNj6ggD6sFyXtYDojXVKv/aacec6cba54332300bfc899de4c0fed5/Screenshot_2022-08-29_at_17-59-51_Geolocalizado.png)
 
 O link whts.co/geolocalizado  sera o link principal. Nesse link está cadastrado o número de telefone da Matriz da Loja Teste que fica no Rio de Janeiro. 
 
@@ -47,11 +47,11 @@ O link whts.co/geolocalizado  sera o link principal. Nesse link está cadastrad
 
 Clique em _**“Avançar”**_.
 
-![Geolocalizado  4](https://images.ctfassets.net/alneenqid6w5/1KIRHBEqDhssJV76yEaszd/15f59999569923cc82a1dd06146190fb/Screenshot_2022-08-29_at_18-00-00_Geolocalizado.png)
+![Geolocalizado  4](//images.ctfassets.net/alneenqid6w5/1KIRHBEqDhssJV76yEaszd/15f59999569923cc82a1dd06146190fb/Screenshot_2022-08-29_at_18-00-00_Geolocalizado.png)
 
 Em Links Geolocalizados,selecione os vendedores ou números,  que irão participar da central. Clique em **_“Adicionar”_,** selecione o estado e a região e selecione o link para cada participante da central.
 
-![Geolocalizado 5](https://images.ctfassets.net/alneenqid6w5/5hq88ccviJz56OJpv9jJdi/1d32fa1d927326fe58fdcfd7cdbb0309/Screenshot_2022-08-29_at_18-00-04_Geolocalizado.png)
+![Geolocalizado 5](//images.ctfassets.net/alneenqid6w5/5hq88ccviJz56OJpv9jJdi/1d32fa1d927326fe58fdcfd7cdbb0309/Screenshot_2022-08-29_at_18-00-04_Geolocalizado.png)
 
 **IMPORTANTE:** No exemplo definimos por estados e não por cidades, mas você também pode definir somente por cidades.
 
diff --git a/docs/tutorials/pt/geolocation-at-checkout.md b/docs/tutorials/pt/geolocation-at-checkout.md
index 7afb57cd8..b4295183c 100644
--- a/docs/tutorials/pt/geolocation-at-checkout.md
+++ b/docs/tutorials/pt/geolocation-at-checkout.md
@@ -42,7 +42,7 @@ Com a API Key em mãos, siga os passos abaixo:
 1. No Admin VTEX, acesse __Configurações da loja > Envio > Envio por geolocalização__, ou digite __Envio por geolocalização__ na barra de busca no topo da página.
 2. Insira a API Key no campo disponível e clique em __Cadastrar chave__.
 
-![Geolocalizacao 1 PT](https://images.ctfassets.net/alneenqid6w5/1WnSV74cA82WY8kGscAiy2/68eeec258fd124695047187dc5e15b51/Geolocalizacao_1_PT.png)
+![Geolocalizacao 1 PT](//images.ctfassets.net/alneenqid6w5/1WnSV74cA82WY8kGscAiy2/68eeec258fd124695047187dc5e15b51/Geolocalizacao_1_PT.png)
 
 <div class="alert alert-info">
 Em alguns países, o Google Maps não realiza um mapping de alta qualidade. Com isso, pode acontecer de certos endereços serem mal escritos ou de o Google indicar um endereço incorreto. Nestes casos, deve-se corrigir o endereço diretamente no mapa.
@@ -63,7 +63,7 @@ Após criar o polígono e inserir seu ID na planilha de frete, você precisará
 3. No menu de opções azul localizado na parte superior da página, clique em __Checkout__.
 4. No campo __Google Maps API Key__, insira a mesma API Key informada na etapa de logística.
 
-![Google map keys](https://images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/31ccb9fd38c90109da5d9dfb9a825c71/google_maps_api_key_pt.PNG)
+![Google map keys](//images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/31ccb9fd38c90109da5d9dfb9a825c71/google_maps_api_key_pt.PNG)
 
 Assim que a API Key for informada nas configurações do Checkout, a geolocalização já estará visível no checkout da sua loja.
 
diff --git a/docs/tutorials/pt/gift-card.md b/docs/tutorials/pt/gift-card.md
index dd4c7cdda..c2b04b082 100644
--- a/docs/tutorials/pt/gift-card.md
+++ b/docs/tutorials/pt/gift-card.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar Vale-compra'
+title: 'Configurar Vale-presente'
 id: tutorials_995
-status: PUBLISHED
+status: CHANGED
 createdAt: 2017-04-27T21:57:54.816Z
-updatedAt: 2023-04-27T17:11:31.494Z
-publishedAt: 2023-04-27T17:11:31.494Z
+updatedAt: 2024-01-19T19:16:50.349Z
+publishedAt: 2024-01-12T12:46:20.978Z
 firstPublishedAt: 2017-04-27T23:03:42.674Z
 contentType: tutorial
 productTeam: Financial
@@ -15,42 +15,43 @@ legacySlug: gift-card
 subcategory: 3qWeS7abxCyC0G0GMq42gA
 ---
 
-O GiftCard, vale presente ou vale-compra é um dos recursos do módulo de Pagamentos que pode funcionar de duas formas:
+O GiftCard ou vale-presente é um dos recursos do módulo de Pagamentos que pode funcionar de duas formas:
 
 - Meio de pagamento para compras; 
 - Programa de fidelidade que o lojista pode conectar com o sistema VTEX. 
 
 Para saber mais detalhes sobre a segunda opção de uso, verifique nossa documentação técnica sobre [como integrar com o GiftCard](https://help.vtex.com/pt/tutorial/integrando-com-gift-card?locale=pt "como integrar com o GiftCard").   
 
-## Como criar o Vale-compras pelo Admin
+## Como criar o Vale-presente pelo Admin
 
-Por padrão VTEX, o vale-compras é considerado como uma forma de pagamento. Esse produto conta com um valor nominal que pode ser utilizado no ato da compra para abater parte do valor de um pedido.
+Por padrão VTEX, o vale-presente é considerado como uma forma de pagamento. Esse produto conta com um valor nominal que pode ser utilizado no ato da compra para abater parte do valor de um pedido.
 
-Para criar um novo vale-compra, confira o passo a passo:
+Para criar um novo vale-presente, confira o passo a passo:
 <ol>
   <li>No Admin VTEX, acesse <b>Promoções > Vales-presente</b>, ou digite <b>Vales-presente</b> na barra de busca no topo da página.</li> 
   <br>
   <li>Clique no botão azul <b>Criar vale</b>.</li>  
   <br>
 <div class = "alert alert-info">
-  <p>Na página de preenchimento, o campo <b>Vale-presente</b> corresponde ao ID do vale. Este é gerado automaticamente pelo sistema da VTEX e será exibido no SmartCheckout (para vales que não são associados a um CPF ou CNPJ exclusivo).</p>
+  <p>Na tela de criação do vale, o campo <b>Vale-presente</b> é automaticamente preenchido pelo sistema VTEX com o código ID do novo vale. Esse é o código a ser inserido pelo cliente na tela do checkout para aplicar o vale-presente no carrinho e reduzir o valor de pagamento do pedido.</p>
 </div>
 <br>
   <li>Preencha os demais campos apresentados conforme as orientações abaixo:</li>
   <br>
 <ul>
   <li><b>Valor</b>: valor nominal que será concedido para o uso do vale.</li>
+  <li><b>Código da moeda</b>: moeda na qual o vale será criado. As opções disponíveis para seleção são apresentadas de acordo com as políticas comerciais de cada loja.</li>
   <li><b>Data de expiração</b>: trata-se da data de vigência da utilização do vale.</li>
   <li><b>CPF/CNPJ Cliente</b>: dado que identifica e define o vale para um específico cliente.</li>
   <li><b>Coleção</b>: determina a coleção de produtos que define os itens em que o vale poderá ser aplicado.</li>
 </ul><br>
 
 <div class="alert alert-warning">
-<strong>Atenção</strong>: o preenchimento dos campos “Valor” e “Data de expiração” é <strong>obrigatório</strong>. Caso o contrário, o vale-compra não será salvo.
+<strong>Atenção</strong>: o preenchimento dos campos “Valor” e “Data de expiração” é <strong>obrigatório</strong>. Caso o contrário, o vale-presente não será salvo.
 </div>
 
 <div class="alert alert-danger">
-A funcionalidade de criação de vale-compras limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
+A funcionalidade de criação de vales-presente limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
 </div>
 
 Depois de preencher os campos corretamente, o usuário poderá assinalar até três opções de configuração: 
@@ -67,9 +68,9 @@ Não há limite para a criação de vales, porém apenas 8000 vales podem ser ex
 
 </ol>
 
-## Como criar um lote de Vale-compras pelo Admin
+## Como criar um lote de Vales-presente pelo Admin
 
-Para criar mais de um vale-compra ao mesmo tempo (um lote), confira o passo a passo:
+Para criar mais de um vale-presente ao mesmo tempo (um lote), confira o passo a passo:
 <ol>
   <li>No Admin VTEX, acesse <b>Promoções > Vales-presente</b>, ou digite <b>Vales-presente</b> na barra de busca no topo da página.</li> 
   <br>
@@ -78,17 +79,18 @@ Para criar mais de um vale-compra ao mesmo tempo (um lote), confira o passo a pa
   <li>Preencha os campos apresentados conforme as orientações abaixo:</li>  
 <br>
 <ul>
-  <li><b>Quantidade de vales-presente</b>: este é o número de vales que você deseja criar em um mesmo lote. Um número máximo de 500 (quinhentos) vales podem ser criados por lote;</li>
+  <li><b>Quantidade de vales-presente</b>: este é o número de vales que você deseja criar em um mesmo lote. Um número máximo de 500 (quinhentos) vales podem ser criados por lote.</li>
   <li><b>Valor</b>: valor nominal que será concedido para todos os vales do lote.</li>
+  <li><b>Código da moeda</b>: moeda na qual os vales serão criados em lote. As opções disponíveis para seleção são apresentadas de acordo com as políticas comerciais de cada loja.</li>
   <li><b>Data de expiração</b>: trata-se da data de vigência da utilização de todos os vales do lote.</li>
   <li><b>Coleção</b>: determina a coleção de produtos que define os itens em que os vales poderão ser aplicados.</li>
   <br>
   <div class="alert alert-warning">
-<strong>Atenção</strong>: o preenchimento dos campos “Quantidade de vales-presente”, “Valor” e “Data de Validade” é <strong>obrigatório</strong>. Caso o contrário, os vales-compra não serão salvos.
+<strong>Atenção</strong>: o preenchimento dos campos “Quantidade de vales-presente”, “Valor” e “Data de Validade” é <strong>obrigatório</strong>. Caso o contrário, os vales-presente não serão salvos.
 </div>
 <br>
   <div class="alert alert-danger">
-A funcionalidade de criação de vale-compras limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
+A funcionalidade de criação de vales-presente limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
 </div>
 <br>
   <li><b>Recarregável</b>: enquanto estes vales estiverem disponíveis, seus saldos poderão ser alterados.</li>
@@ -96,7 +98,7 @@ A funcionalidade de criação de vale-compras limitados por coleções de produt
 </ul><br>  
   <li>Clique no botão <b>Salvar</b>.</li>
 <br>
-Uma nova tela irá aparecer confirmando que foram gerados o número de vales-compras solicitados e os respectivos códigos de identificação serão apresentados.<br> 
+Uma nova tela irá aparecer confirmando que foram gerados o número de vales-presentes solicitados e os respectivos códigos de identificação serão apresentados.<br> 
 <br>
   <li>Por fim, clique no botão <b>Voltar</b>.</li>
 <br>
@@ -105,11 +107,11 @@ Não há limite para a criação de vales, porém apenas 8000 vales podem ser ex
 </div>
 </ol>
 
-## Como configurar o Vale-compra como meio de pagamento
+## Como configurar o Vale-presente como meio de pagamento
 
-Perfeito! Agora que o seu vale-compra foi criado, é preciso configurá-lo como meio de pagamento. Isso fará com que o Gift Card seja exibido no Checkout e, assim, seus clientes poderão finalizar pedidos usando o crédito do vale.
+Após a criação do vale-presente, é necessário configurá-lo como meio de pagamento. Desta forma, seus clientes poderão utilizá-lo no Checkout.
 
-Acompanhe as instruções:
+Siga os passos abaixo para configurar o vale-presente:
 
 1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
 2. Na aba __Condições de pagamento__, clique no botão `+`.
@@ -119,7 +121,7 @@ Acompanhe as instruções:
 6. Em __Processar com afiliação__, selecione o provedor de giftcard desejado.
 7. Clique em `Salvar`.
 
-Além disso, você ainda pode definir condições especiais de pagamento para o vale-compra. Não há limite de condições de podem ser aplicadas a um meio de pagamento e especificamos como configurar cada uma delas [aqui](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456?locale=pt "aqui."). 
+Além disso, você ainda pode definir condições especiais de pagamento para o vale-presente. Não há limite de condições de podem ser aplicadas a um meio de pagamento e especificamos como configurar cada uma delas [aqui](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456?locale=pt "aqui."). 
 
 Por fim, clique no botão azul Salvar.
 
diff --git a/docs/tutorials/pt/google-analytics-faq.md b/docs/tutorials/pt/google-analytics-faq.md
index d8358da82..ba75e6879 100644
--- a/docs/tutorials/pt/google-analytics-faq.md
+++ b/docs/tutorials/pt/google-analytics-faq.md
@@ -3,8 +3,8 @@ title: 'Google Analytics: FAQ'
 id: 2VRtB07muo3vwO6KEmMVn0
 status: PUBLISHED
 createdAt: 2021-12-17T18:41:26.175Z
-updatedAt: 2023-03-31T15:22:28.277Z
-publishedAt: 2023-03-31T15:22:28.277Z
+updatedAt: 2023-07-31T18:35:26.120Z
+publishedAt: 2023-07-31T18:35:26.120Z
 firstPublishedAt: 2021-12-17T18:53:43.536Z
 contentType: tutorial
 productTeam: Others
@@ -15,6 +15,8 @@ legacySlug: google-analytics-faq
 subcategory: 1luKrYptdi8WoMYckakUaM
 ---
 
+Confira abaixo algumas das dúvidas mais frequentes acerca de Google Analytics para lojas VTEX.
+
 ## Como instalar o Google Analytics na sua loja?
 
 A instalação é feita através do [Google Tag Manager](https://help.vtex.com/tutorial/integracao-com-o-google-tag-manager#), como descrita no artigo [Configurar Google Analytics em loja VTEX](https://help.vtex.com/pt/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG#).
@@ -33,32 +35,43 @@ Modelos de atribuição ditam a metodologia usada por uma plataforma para atribu
 
 Saiba mais sobre [modelos de atribuição no Google Analytics.](https://support.google.com/analytics/answer/1662518?hl=pt-br)
 
-## Por que existe divergência nas métricas exibidas na VTEX e no Google Analytics?
+## Por que as métricas exibidas na VTEX e no Google Analytics são diferentes?
 
 Há diferenças na forma como cada plataforma obtém os dados da sua loja e isso pode resultar em números diferentes na sua análise. Abaixo citamos alguns dos casos mais comuns e explicamos como interpretar essas diferenças.
 
 ### Transações
 
-Divergências no registro de transações costumam derivar de alguma irregularidade no disparo da [tag do Google Analytics](https://help.vtex.com/en/tutorial/how-to-setup-google-analytics-in-vtex-store--G2P0rmSrEiqCcmUMyUUwG#). Nesse caso, pode haver duplicidade ou falha de disparo.
+Como a VTEX é responsável por processar transações da sua loja, todas as transações são registradas na plataforma. Entretanto, no caso do Google Analytics, há casos que podem gerar irregularidade ou falha no disparo da tag correspondente. Exemplos incluem:
+
+- Navegadores com configurações rígidas de privacidade.
+- Navegadores com bloqueio de Javascript.
+- Bloqueadores de anúncios.
+- Erro de configuração da camada de dados do Google Analytics. Veja a documentação oficial do Google para saber mais sobre como seu time de desenvolvimento pode [configurar a camada de dados do Google Analytics 4](https://developers.google.com/tag-manager/ecommerce-ga4).
+- Tag de transação dispara mesmo com transações que não foram concluídas com sucesso.
+- Falha ou duplicidade na exibição da página de confirmação do pedido, caso a tag de transação esteja vinculada à exibição desta página.
+
+<div class = "alert alert-info">
+Considere também que há um atraso de até 48h no registro de dados de transações no Google Analytics.
+</div>
 
 Além disso, integrações podem ser construídas de modo que acabem não disparando certas tags na sua frente de loja. Por exemplo, há integrações que usam um [app de pagamento](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-app) e finalizam a compra sem direcionar o cliente à página de confirmação de pedido, como a integração desenvolvida pela AME Digital. Transações sempre serão registradas na VTEX, mas, nesse caso, é provável que não seja registrada no Google Analytics, gerando divergência.
 
 ### Atribuição de vendas
 
-É normal que existam diferenças entre a atribuição no módulo da VTEX de **Pedidos** e no Google Analytics, pois são ferramentas diferentes com modelos de atribuição diferentes e que captam informações através de cookies diferentes.
+É normal que existam diferenças entre a atribuição nas visualizações de dados da plataforma VTEX e no Google Analytics, pois são ferramentas diferentes com [modelos de atribuição](https://help.vtex.com/pt/tutorial/google-analytics-faq--2VRtB07muo3vwO6KEmMVn0#o-que-sao-modelos-de-atribuicao) diferentes e que captam informações através de cookies diferentes.
 
-As informações de UTM reconhecidas pela VTEX podem ser verificadas no painel de ferramentas de desenvolvedor do seu navegador, no objeto `marketingData` do [OrderForm.](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview#orderform-fields) Saiba mais neste artigo sobre [UTMs de marketing no Checkout.](https://help.vtex.com/pt/tutorial/identificar-se-utms-de-marketing-estao-sendo-passadas-para-o-checkout--6kjHHfOWIgeI26qcQSU4Wg#)
+As informações de UTM reconhecidas pela VTEX podem ser verificadas no painel de ferramentas de desenvolvedor do seu navegador, no objeto `marketingData` do [OrderForm](https://developers.vtex.com/docs/guides/orderform-fields). Saiba mais neste artigo sobre [UTMs de marketing no Checkout](https://help.vtex.com/pt/tutorial/identificar-se-utms-de-marketing-estao-sendo-passadas-para-o-checkout--6kjHHfOWIgeI26qcQSU4Wg#).
 
 Já o Google Analytics, usa, por padrão, o modelo de Última interação.
-Também é possível utilizar diferentes modelos, descritos na [documentação do Google Analytics sobre modelos de atribuição.](https://support.google.com/analytics/answer/1662518?hl=pt-br)
+Também é possível utilizar diferentes modelos, descritos na [documentação do Google Analytics sobre modelos de atribuição](https://support.google.com/analytics/answer/1662518?hl=pt-br).
 
-Se você também analisa dados de anúncios no Facebook, é possível encontrar outras divergências. Por exemplo, o Facebook levará em consideração clientes que viram o anúncio e compraram em algum momento posterior, mesmo que tenham chegado à loja por outro caminho no momento da compra.
+Se você também analisa dados de anúncios no Facebook, é possível encontrar outras divergências. Por exemplo, o Facebook leva em consideração clientes que viram o anúncio e compraram em algum momento posterior, mesmo que tenham chegado à loja por outro caminho no momento da compra.
 
 A diferença na forma de atribuição não afeta em nada a venda em si, apenas a interpretação de cada plataforma.
 
 ### Sessões
 
-Assim como há formas diferentes de atribuir a origem de eventos que ocorrem na sua loja, há diferentes formas de definir sessões. O conceito de sessão utilizado pela VTEX é pensado para se aproximar do [conceito de sessão do Google Analytics](https://support.google.com/analytics/answer/2731565?hl=pt-BR#time-based-expiration&zippy=%2Cneste-artigo), mas não é uma réplica.
+Assim como há formas diferentes de atribuir a origem de eventos que ocorrem na sua loja, há diferentes formas de definir sessões. O conceito de sessão utilizado pela VTEX é pensado para se aproximar do [conceito de sessão do Google Analytics](https://support.google.com/analytics/answer/12798876), mas não é uma réplica.
 
 Por isso, eventos que são interpretados como sessões na VTEX podem não ser interpretados da mesma forma no Google Analytics e vice-versa.
 
@@ -68,8 +81,11 @@ Apesar das diferenças, vale notar que ambas as plataformas consideram que uma s
 
 ### Funil de vendas
 
-Assim como sessões são registradas pela VTEX, há uma interpretação dos dados de navegação entre as páginas de produto e o fluxo do carrinho de compras. Com isso, a VTEX gera a visualização do funil de vendas.
+A VTEX gera uma visualização do funil de vendas da sua loja a partir dos registros de navegação que a plataforma gera, desde as páginas de produto até o fluxo de carrinho de compras e checkout.
+
+Já o Google Analytics disponibiliza um funil de vendas gerado automaticamente, baseado nas tags do Google, configuradas na sua frente de loja. Saiba mais sobre [como o Google gera esta visualização de funil](https://support.google.com/analytics/answer/6014872#zippy=%2Cin-this-article%2Cneste-artigo).
+
+Por serem baseados em informações diferentes, essas visualizações de funil podem apresentar divergências.
 
-Já o [Google Analytics tem um funil de vendas gerado automaticamente](https://support.google.com/analytics/answer/6014872#zippy=%2Cin-this-article%2Cneste-artigo), baseado nas tags do Google, configuradas na sua frente de loja.
+Você pode configurar um outro funil de vendas no Google Analytics, que possibilita uma visão customizada e melhor controle da jornada de compra. Confira este artigo sobre como [implementar este funil de vendas no Google Analytics](https://help.vtex.com/en/tutorial/configurar-funil-de-vendas-no-google-analytics#).
 
-Além disso, você pode configurar um outro funil de vendas no Google Analytics, que possibilita uma visão customizada e melhor controle da jornada de compra. Confira este artigo sobre como [implementar este funil de vendas no Google Analytics](https://help.vtex.com/en/tutorial/configurar-funil-de-vendas-no-google-analytics#).
diff --git a/docs/tutorials/pt/google-integration-warnings.md b/docs/tutorials/pt/google-integration-warnings.md
new file mode 100644
index 000000000..43141d966
--- /dev/null
+++ b/docs/tutorials/pt/google-integration-warnings.md
@@ -0,0 +1,92 @@
+---
+title: 'Avisos de integração com o Google'
+id: 4BC0Epit2hACKbkBSqDR2A
+status: PUBLISHED
+createdAt: 2024-07-01T15:16:46.324Z
+updatedAt: 2024-07-01T20:42:52.728Z
+publishedAt: 2024-07-01T20:42:52.728Z
+firstPublishedAt: 2024-07-01T16:13:33.089Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: avisos-de-integracao-com-o-google
+locale: pt
+legacySlug: avisos-de-integracao-com-o-google
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+Ao realizar a integração de uma loja VTEX com o Google shopping, o seller precisa cumprir o processo de [Envio de produtos para o Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/5L5LnccDCj5lJk8H95GQ82) e esses produtos podem ou não ser aprovados pelo Google. 
+
+## Status de integração do produto
+
+O status de integração é uma mensagem informativa sobre a situação dos produtos do seller com a integração do Google Shopping. É possível encontrar três categorias de mensagens, **mensagens de erro, mensagens de aviso e mensagens de sucesso.** 
+
+Para verificar o status de integração de um produto, acesse no Admin VTEX o menu **Marketplace > Produtos** ou digite **Produtos** na barra de busca.  
+
+Veja na tabela quais mensagens pertencem a qual status:  
+
+| **Status** | **Mensagem** | **Detalhes** | **Qual o impacto no anúncio** |
+|:---:|:---:|:---:|:---:|
+| **Processado com erro** | `SKU from accountName was not integrated` e `We noticed some problems`| `Product or SKU inactive`, `Invalid price` e `SKU out of stock`. |   Caso não sejam realizados os ajustes, os produtos não serão integrados. |
+| **Processado com aviso** | `SKU from accountName integrated`, `See offer` e `But we noticed some missing data` | `EAN/UPC and manufacturer code`, `Size`, `Color`, `Gender` e `Age Group`. |   Se aplicável ao produto e não preenchido os dados faltantes, o anúncio pode ficar com baixa visibilidade ou ser reprovado. |
+| **Processado com sucesso** | `SKU from accountName integrated`, `See offer` e `Add following data to increase offer visibility`. | [Product Highlights](https://support.google.com/merchants/answer/7052112?hl=pt-BR#zippy=%2Coutros-requisitos%2Ccomo-formatar-os-dados-do-produto:~:text=produtos%20s%C3%A3o%20veiculados.-,Opcional%3A,-envie%20o%20atributo) | Se aplicável e preenchido os atributos opcionais indicados pelo Google, o anúncio pode melhorar a  visibilidade. |
+
+## Preenchendo campos obrigatórios para o Google
+
+Quando um produto apresenta o status **Processado com erro ou Processado com aviso**, significa que um ou mais dos dados obrigatórios para a integração do catálogo com o Google shopping não foram preenchidos ou configurados.  
+
+A seguir saiba em que situação ele é obrigatório e como preencher cada campo:  
+
+- **Price:** é um campo obrigatório e deve ser preenchido informando com qual tipo de preço deseja apresentar no Google shopping.
+- Para identificar o erro de integração do preço do SKU com o Google, leia a documentação [Verificando integrações](https://help.vtex.com/pt/tutorial/verificando-integracao-no-bridge/#preco).   
+- **Availability ou Disponibilidade:** é um campo obrigatório. Caso a integração de um SKU apresente erro, confira as documentações de [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) e [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb).  
+- **EAN/UPC:** é um campo obrigatório, existente no [módulo de Catálogo](https://help.vtex.com/pt/tutorial/catalogo-visao-geral--77M8ItLhDXs6aBdQTqToVe) e deve ser preenchido com o código de identificação único do SKU (código de barras), aceita até 13 caracteres numéricos.  
+- **Manufacturer code ou Código do fabricante:** é um campo obrigatório, existente no [módulo de Catálogo](https://help.vtex.com/pt/tutorial/catalogo-visao-geral--77M8ItLhDXs6aBdQTqToVe) e deve ser preenchido com o código fornecido pelo fabricante para identificar seu produto. Caso algum produto tenha um código específico, esse campo deve se preenchido.  
+
+<div class="alert alert-info">
+Os códigos EAN/UPC e Código do fabricante são obrigatórios em venda de produtos manufaturados. Saiba quando aplicar o <a href="https://support.google.com/merchants/answer/6324461?hl=pt-BR&ref_topic=6324338&sjid=10867212756007821438-SA">EAN/UPC</a> ou o <a href="https://support.google.com/merchants/answer/6324482?hl=pt-BR&ref_topic=6324338&sjid=10867212756007821438-SA">Código do fabricante</a> a um produto. 
+</div>  
+
+- **Size:** é um campo obrigatório apenas para todos os produtos de vestuário que corresponde à categoria [ID1604](https://support.google.com/merchants/answer/6324492?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) e calçados que correspondem à categoria [ID187](https://support.google.com/merchants/answer/6324492?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) no Google. Se aplicável ao seu produto preencha com o tamanho referente ao SKU.  
+
+O campo Size ou Tamanho, é um [campo customizado](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106) que precisa ser criado pelo seller. Veja abaixo qual o nome e tipo do campo.  
+
+| **Nome do campo** | **Tipo do campo** |
+|:---:|:---:|
+| Tamanho | Texto |
+
+Campo desse tipo suporta o preenchimento de valores alfanuméricos como, **P,M,G, GG, 41,42,37,33**.  
+
+- **Color:** é um campo obrigatório apenas para todos os itens de vestuário e acessórios que corresponde à [categoria ID166](https://support.google.com/merchants/answer/6324487?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) no Google. Se aplicável ao seu produto preencha com a cor referente ao SKU.  
+
+O campo Color ou cor, é um [campo customizado](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106) e deve ser criado pelo seller. Veja abaixo qual o nome e tipo do campo.  
+
+| **Nome do campo** | **Tipo do campo** |
+|:---:|:---:|
+| Cor | Texto |
+
+Campo desse tipo suporta o preenchimento de valores alfanuméricos como, **Verde, Preto, Amarelo, Rosa**.
+
+<div class="alert alert-info">
+Cada SKU só permite uma cor.
+</div>  
+
+- **Gender:** é um campo obrigatório apenas para todos os itens de vestuário e acessórios que corresponde à [categoria ID166](https://support.google.com/merchants/answer/6324479?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) no Google. Se aplicável ao seu produto preencha com a cor referente ao SKU.  
+
+O campo Gender ou gênero, é um [campo customizado](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106) e deve ser criado pelo seller. Veja abaixo qual o nome e tipo do campo.  
+
+| **Nome do campo** | **Tipo do campo** | **Valor do campo** |
+|:---:|:---:|:---:|
+| Gênero | Combo |Masculino, Feminino e Unissex.|
+
+Campo desse tipo requer preenchimento de valores pré-definidos. Somente os valores listado em “valor do campo” será aceito pela integração com o Google.  
+
+- **Age Group:**  é um campo obrigatório para todos os itens de vestuário e acessórios que corresponde à [categoria ID166](https://support.google.com/merchants/answer/6324463?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1#:~:text=Veja%20a%20seguir%20os%20valores%20aceitos%20para%20este%20atributo%3A) no Google. Se aplicável ao seu produto preencha com a cor referente ao SKU.  
+
+O campo Age Group ou Faixa etária, é um [campo customizado](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106) e deve ser criado pelo seller. Veja abaixo qual o nome e tipo do campo.  
+
+| **Nome do campo** | **Tipo do campo** | **Valor do campo** |
+|:---:|:---:|:---:|
+| Faixa etária | Combo |Recém-nascido (até 3 meses), Bebê (de 3 meses a 12 meses), Criança pequena (de 1 ano a 5 anos),Criança (de 5 anos a 13 anos) e Adulto (a partir de 13 anos).|  
+
+Campo desse tipo requer preenchimento de valores pré-definidos. Somente os valores listado em “valor do campo” será aceito pela integração com o Google.  
diff --git a/docs/tutorials/pt/google-pay-beta.md b/docs/tutorials/pt/google-pay-beta.md
index 5a3c05695..48c95eb67 100644
--- a/docs/tutorials/pt/google-pay-beta.md
+++ b/docs/tutorials/pt/google-pay-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Google Pay (Beta)'
 id: 653pNFOw6L5CvGupLosJSq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-04-26T15:34:40.825Z
-updatedAt: 2023-06-14T19:34:39.943Z
-publishedAt: 2023-06-14T19:34:39.943Z
+updatedAt: 2023-06-27T21:56:34.229Z
+publishedAt: 
 firstPublishedAt: 2023-04-26T20:03:44.992Z
 contentType: tutorial
 productTeam: Shopping
@@ -40,7 +40,7 @@ Para ativar o Google Pay, siga o passo a passo abaixo.
 
 Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como nova forma de pagamento. É possível que demore em torno de 10 minutos para que a configuração apareça no Checkout.
 
-![google pay - PT](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/a8bca906bd64bf229ac9521848a7c029/image.png)
+![google pay - PT](//images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/a8bca906bd64bf229ac9521848a7c029/image.png)
 
 <div class="alert alert-warning">
 <p>Google Pay, neste momento, não vai suportar assinatura.</p>
diff --git a/docs/tutorials/pt/headless-cms-overview.md b/docs/tutorials/pt/headless-cms-overview.md
new file mode 100644
index 000000000..c61a90f6a
--- /dev/null
+++ b/docs/tutorials/pt/headless-cms-overview.md
@@ -0,0 +1,53 @@
+---
+title: 'Headless CMS - Visão geral'
+id: 3U5gvhHdQL0jczYH8gjX09
+status: PUBLISHED
+createdAt: 2023-12-15T20:27:39.404Z
+updatedAt: 2024-02-16T01:12:18.561Z
+publishedAt: 2024-02-16T01:12:18.561Z
+firstPublishedAt: 2023-12-18T13:33:50.044Z
+contentType: tutorial
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: headless-cms-visao-geral
+locale: pt
+legacySlug: headless-cms-visao-geral
+subcategory: 27t6x0lngvjI3bnUg5AgEO
+---
+
+O Headless CMS é um sistema de gerenciamento de conteúdo desenvolvido pela VTEX para proporcionar às empresas a flexibilidade de criar e disponibilizar conteúdo em diferentes canais, como sites e aplicativos móveis.
+
+O termo *Headless* refere-se à independência entre a interface que exibe o conteúdo para o usuário, o frontend, e o sistema responsável pelo gerenciamento e armazenamento desse conteúdo, o backend. Essa abordagem permite que o gerenciamento de conteúdo ocorra de forma independente da interface do usuário, proporcionando flexibilidade e escalabilidade. Por exemplo, uma loja pode atualizar uma página de produto pelo Headless CMS sem afetar a experiência do usuário no site. Isso simplifica a manutenção do conteúdo e permite a reutilização de dados.
+
+Para acessar o Headless CMS, entre no Admin VTEX e acesse **Storefront > Headless CMS**.
+
+<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+  Para o gerenciamento do Headless CMS, certifique-se de que os <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos</a> <i>See CMS menu on the top-bar</i>, <i>Settings</i> e <i>CMS GraphQL API</i> estão associados ao seu <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete">Perfil de acesso</a>. Do contrário, <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso"> crie um perfil de acesso</a> e adicione esses recursos a eles ou adicione esses recursos a um perfil de acesso existente.
+</div>
+
+Com o Headless CMS, você pode:
+
+- [Gerenciar projetos](#gerenciar-projetos)
+- [Gerenciar páginas](#gerenciar-páginas)
+- [Gerenciar content types do tipo Singleton](#gerenciar-content-types-do-tipo-singleton)
+
+## Gerenciar projetos
+
+[Projetos](https://help.vtex.com/pt/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) é uma funcionalidade do Headless CMS que permite criar e gerenciar vários projetos de frontend, como aplicativos móveis, sites e email marketing em um único painel de controle.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
+
+Para mais informações, acesse o artigo [Gerenciando Projetos](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM).
+
+## Gerenciar páginas
+Em cada projeto, você também pode gerenciar todas as rotas de URL e modelos de página para o site de sua loja, incluindo a página inicial, a página de produto (PDP) e outras. Para obter mais informações, consulte [Gerenciando Páginas no Headless CMS](https://help.vtex.com/en/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt).
+
+## Gerenciar content types do tipo Singleton
+Singleton é um tipo de conteúdo que simplifica o gerenciamento de conteúdo através da criação e do gerenciamento de uma única página, garantindo a existência de apenas uma versão desse tipo de conteúdo no Headless CMS. Essa abordagem aumenta a confiança no conteúdo e simplifica a criação e a manutenção do conteúdo em um ambiente Headless CMS.  Para obter mais informações, consulte [Gerenciando content types do tipo Singleton](https://help.vtex.com/en/tutorial/managing-singleton-content-types--VBibMN1BqV2OFmavUFCdo).
+
+## Próximos passos
+Confira os tutoriais a seguir para começar a gerenciar o conteúdo do seu storefront:
+
+- [Gerenciando Projetos](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM)
+- [Gerenciando Páginas no Headless CMS](https://help.vtex.com/en/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt)
+- [Gerenciando content types do tipo Singleton](https://help.vtex.com/en/tutorial/managing-singleton-content-types--VBibMN1BqV2OFmavUFCdo)
diff --git a/docs/tutorials/pt/how-and-when-do-i-receive-my-invoice.md b/docs/tutorials/pt/how-and-when-do-i-receive-my-invoice.md
index 982b2bfc0..dbf52a500 100644
--- a/docs/tutorials/pt/how-and-when-do-i-receive-my-invoice.md
+++ b/docs/tutorials/pt/how-and-when-do-i-receive-my-invoice.md
@@ -3,8 +3,8 @@ title: 'Como e quando recebo minha nota fiscal e meu boleto?'
 id: 4kRivWUH68iQ6AwI2QU6gm
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:47.627Z
-updatedAt: 2020-05-12T18:36:27.081Z
-publishedAt: 2020-05-12T18:36:27.081Z
+updatedAt: 2023-10-11T20:31:33.338Z
+publishedAt: 2023-10-11T20:31:33.338Z
 firstPublishedAt: 2019-01-24T22:08:59.617Z
 contentType: tutorial
 productTeam: Billing
@@ -15,15 +15,16 @@ legacySlug: como-e-quando-recebo-minha-nota-fiscal-e-meu-boleto
 subcategory: 5ZfsNR4ioEsIyu6wkyce0M
 ---
 
-<div class="alert alert-info" role="alert"><strong>ATENÇÃO: Esse procedimento é apenas para clientes faturados no Brasil.</strong></div>
+<div class="alert alert-warning" role="alert">
+  <p>Este procedimento se aplica apenas para clientes faturados no <strong>Brasil</strong>.</p>
+</div>
 
+O faturamento é disparado até o quinto dia útil do mês. Nota Fiscal e boleto ficam disponíveis no módulo __Faturas__ do Admin da sua loja. 
 
-O faturamento é disparado até o 5º dia útil do mês. Nota Fiscal e boleto ficam disponíveis no módulo __Faturas__ do Admin da sua loja. 
+Quando uma cobrança é feita, enviamos um email para os contatos cadastrados avisando de que a Nota Fiscal e boleto já estão disponíveis para pagamento ou consulta. 
 
-Quando uma cobrança é feita, enviamos um e-mail para os contatos cadastrados avisando de que a Nota Fiscal e boleto já estão disponíveis para pagamento ou consulta. 
-
-Caso não tenha recebido o aviso até o 5º dia útil do mês, [consulte seu painel administrativo](/pt/tutorial/como-baixar-boletos-e-notas-fiscais-da-vtex). Se identificar alguma divergência, [entre em contato](https://support.vtex.com/hc/pt-br/requests) com o Financeiro.
+Caso não tenha recebido o aviso até o 5º dia útil do mês, [consulte seu painel administrativo](https://help.vtex.com/pt/tutorial/como-fazer-download-faturas-da-vtex--tutorials_653). Se identificar alguma divergência, entre em contato com o [Financeiro](https://support.vtex.com/hc/pt-br/requests).
 
 Caso não consiga baixar seu boleto, é possível que você não tenha um perfil financeiro configurado na conta da loja, neste caso, solicite para o Super Admin da conta acrescentar.
 
-Se não estiver recebendo o e-mail informando que o boleto está dispoível para download na plataforma, é possível que o e-mail não esteja cadastrado como contato financeiro. Neste caso, abra um [ticket](https://help-tickets.vtex.com/smartlink/sso/login/zendesk) para solicitar inclusão do e-mail nos contatos financeiros da conta.
+Se não estiver recebendo o email informando que o boleto está disponível para download na plataforma, é possível que o email não esteja cadastrado como contato financeiro. Neste caso, abra um [ticket](https://support.vtex.com/hc/pt-br/requests) para solicitar inclusão do email nos contatos financeiros da conta.
diff --git a/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
index 2261d96f3..2a3f25f91 100644
--- a/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
@@ -26,7 +26,7 @@ A plataforma VTEX é preparada para suportar mudanças de domínios sem impactos
 No License Manager, em Contas, será necessário incluir o novo domínio como HOST da loja. Nesse momento, o DNS do novo domínio ainda não deve estar apontado para a VTEX. 
 
 Esta imagem exemplifica a inclusão de novos HOSTs que deve ser aplicada:
-![Mudar Domínio](https://images.ctfassets.net/alneenqid6w5/1AUt1cydWg2W04wc02EKKM/36c9a17ccee114cf38f48c5ba07973e7/626-pt.png)
+![Mudar Domínio](//images.ctfassets.net/alneenqid6w5/1AUt1cydWg2W04wc02EKKM/36c9a17ccee114cf38f48c5ba07973e7/626-pt.png)
 
 ### 2. Conferir configurações do novo Portal
 Esse passo é fundamental para que o Checkout continue funcionando após a mudança. É necessário conferir se os Sites configurados estão relacionados a algum Accoount Name inexistente no License Manager. [Leia mais sobre configurações do portal aqui](/pt/faq/configurar-template-no-smartcheckout/).
diff --git a/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
index 8d02dc86d..f5f3eb858 100644
--- a/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
@@ -45,7 +45,7 @@ Confira o passo a passo:
 
 <div class="alert alert-info">Mais informações sobre <strong>Configurações gerais</strong> e <strong>Configurações de busca e de filtro</strong> podem ser encontradas na sessão <strong>Como configurar</strong> do artigo <a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Criar entidade de dados</a>.</div>
 
-![criar campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
+![criar campo master data ds](//images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
 Desse modo, você retornará para a página de principal da aba Entidade de Dados. Para finalizar, você precisa publicar o campo. Basta localizar a linha da entidade em que o campo foi adicionado e clicar no ícone disquete.
 
@@ -70,6 +70,6 @@ Dito isso, prossiga com as instruções:
 7. Arraste o campo da lista Campos disponíveis para as colunas Campos da coluna 1 ou Campos da coluna 2;
 8. No canto inferior direito da tela, clique no botão azul Salvar.
 
-![criar campo master data CRM](https://images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
+![criar campo master data CRM](//images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
 
 Pronto! Assim, os campos serão exibidos no formulário.
diff --git a/docs/tutorials/pt/how-can-i-create-callcenter-user.md b/docs/tutorials/pt/how-can-i-create-callcenter-user.md
index ea7e9fcdc..b96a63b25 100644
--- a/docs/tutorials/pt/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/pt/how-can-i-create-callcenter-user.md
@@ -41,7 +41,7 @@ Para criar um usuário com perfil de televendas, siga os seguintes passos:
 
 7. Clique no botão **Salvar**.
 
-![GIF animado mostrando como criar usuário televendas](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/575304556410712f649e94cda1b3bdce/Adicionar_perfil.gif)
+![GIF animado mostrando como criar usuário televendas](//images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/575304556410712f649e94cda1b3bdce/Adicionar_perfil.gif)
 
 <div class="alert alert-warning">
   Ao criar um <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evite incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
diff --git a/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md b/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md
index 177a16072..25ff45b4e 100644
--- a/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md
+++ b/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md
@@ -3,8 +3,8 @@ title: 'Criar cluster de clientes'
 id: frequentlyAskedQuestions_1724
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:58.065Z
-updatedAt: 2022-10-17T21:24:38.123Z
-publishedAt: 2022-10-17T21:24:38.123Z
+updatedAt: 2024-05-24T19:15:04.156Z
+publishedAt: 2024-05-24T19:15:04.156Z
 firstPublishedAt: 2019-01-24T22:05:41.666Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -44,6 +44,6 @@ Ou seja, tecnicamente, um cluster no CRM nada mais é do que um campo.
 
 Para popular esse campo, você pode usar [planilha de importação](https://help.vtex.com/pt/tutorial/importando-dados-no-master-data/ "Importar dados no Master Data"), API ou fazer isso manualmente pelo formulário de Cliente dentro do CRM. Tudo vai depender da estratégia da loja sobre a clusterização de seus clientes.
 
-## Para saber mais
+## Saiba mais
 
-[Saiba como criar uma promoção para um cluster](/pt/tutorial/criando-promocao-para-um-cluster-de-clientes)
+- [Saiba como criar uma promoção para um cluster](/pt/tutorial/criando-promocao-para-um-cluster-de-clientes)
diff --git a/docs/tutorials/pt/how-can-i-direct-a-financial-doubt-to-vtex.md b/docs/tutorials/pt/how-can-i-direct-a-financial-doubt-to-vtex.md
index c440d99d1..ef9a218da 100644
--- a/docs/tutorials/pt/how-can-i-direct-a-financial-doubt-to-vtex.md
+++ b/docs/tutorials/pt/how-can-i-direct-a-financial-doubt-to-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'Como direcionar dúvida financeira à VTEX?'
 id: 5h8wQ6AqIEKYcU2mASqGEU
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:46.689Z
-updatedAt: 2020-03-09T17:25:45.988Z
-publishedAt: 2020-03-09T17:25:45.988Z
+updatedAt: 2024-07-29T22:06:40.466Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T21:58:53.151Z
 contentType: tutorial
 productTeam: Billing
diff --git a/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md b/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md
index 50f93ec0f..eced16281 100644
--- a/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md
+++ b/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md
@@ -3,8 +3,8 @@ title: 'Exportar a base de newsletter pelo Master Data'
 id: frequentlyAskedQuestions_1825
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:58.818Z
-updatedAt: 2023-03-28T23:50:45.779Z
-publishedAt: 2023-03-28T23:50:45.779Z
+updatedAt: 2024-05-24T18:56:12.924Z
+publishedAt: 2024-05-24T18:56:12.924Z
 firstPublishedAt: 2019-01-24T22:00:56.109Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,14 +15,17 @@ legacySlug: como-realizo-a-exportacao-da-base-de-newsletter-pelo-master-data
 subcategory: WpbGhubuRZaNZilJSXnqu
 ---
 
-Para exportar sua base de clientes que optaram por receber newsletter, siga o passo-a-passo abaixo:
+Para exportar sua base de clientes que optaram por receber newsletter, siga o passo a passo abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
-2. Acesse a aba **Clientes.**
-3. Clique em **Exportar XLS.**
+2. Acesse a aba **Clientes**.
+3. Clique em `Exportar XLS`.
 4. Selecione o filtro `Recebe Newsletter?`, além de outros que deseje (`Nome` e `e-mail`, por exemplo).
-5. Clique em **Exportar.**
-6. Aparecerá uma janela informando que a exportação foi programada com sucesso. Clique em **OK** para fechá-la.
-7. Na planilha que terá sido enviada para o seu e-mail haverá uma coluna entitulada `isNewsletterOptIn`, que atribui o valor **true** para os clientes que recebem newsletter e **false** para os que não recebem.
+5. Clique em `Exportar`.
+6. Aparecerá uma janela informando que a exportação foi programada com sucesso. Clique em `OK` para fechá-la.
 
-_Essa opção somente é válida para lojas que têm cadastro de newsletter pelo Master Data. Caso sua loja ainda não possua essa configuração e ela ainda seja feita pelo controle de página, leia o artigo [Configurar a captação de newsletter pelo Master Data](/pt/tutorial/como-configuro-a-captacao-de-newsletter-pelo-master-data--frequentlyAskedQuestions_1816) para saber como configurar._
+   Na planilha que terá sido enviada para o seu e-mail haverá uma coluna entitulada `isNewsletterOptIn`, que atribui o valor **true** para os clientes que recebem newsletter e **false** para os que não recebem.
+
+<div class="alert alert-warning">
+  <p>Essa opção somente é válida para lojas que têm cadastro de newsletter pelo Master Data. Caso sua loja ainda não possua essa configuração e ela ainda seja feita pelo controle de página, leia o artigo <a href="https://help.vtex.com/pt/tutorial/como-configuro-a-captacao-de-newsletter-pelo-master-data--frequentlyAskedQuestions_1816">Configurar a captação de newsletter pelo Master Data</a> para saber como configurar.</p>
+</div>
diff --git a/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md b/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md
index e9fb33d69..a4f64dda2 100644
--- a/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md
+++ b/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md
@@ -25,7 +25,7 @@ Eis algumas delas.
 
 Quando o usuário acessa a seção **Disputas**, os processos são exibidos em uma única tela. Contudo, as disputas deixam de ser apresentadas na seção **Disputas** quando se tornam chargeback (7 dias após serem abertas). Ou seja, uma vez que a devolução do dinheiro é feita para o cliente, a disputa é fechada e “some” da exibição.
 
-![disputa-vtex-payment](https://images.ctfassets.net/alneenqid6w5/5E3vzxX10nWod99okmR5Ey/5afc15fd3c9b3bfb57d9d55ddd51f4f8/image.png)
+![disputa-vtex-payment](//images.ctfassets.net/alneenqid6w5/5E3vzxX10nWod99okmR5Ey/5afc15fd3c9b3bfb57d9d55ddd51f4f8/image.png)
 
 ## Consulta de disputa única
 
diff --git a/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md b/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md
index 0308faa48..67b1f8bd9 100644
--- a/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md
+++ b/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md
@@ -28,7 +28,7 @@ O objetivo deste artigo é mostrar como o cliente da sua loja deve fazer login n
 
 Ao clicar em um link para se autenticar, o cliente verá a tela de login.
 
-![vtex-id-pt](https://images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/d7e784ef2c14aad7a01faef0e94f5c19/vtex-id-en.png)
+![vtex-id-pt](//images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/d7e784ef2c14aad7a01faef0e94f5c19/vtex-id-en.png)
 
 Existem três formas padrão de se fazer login numa loja VTEX:
 
@@ -43,9 +43,9 @@ Este tipo de login __envia um token de acesso para o e-mail do usuário__ para q
 Para o cliente fazer login por esse método, ele deve seguir os passos abaixo:
 
 1. Na tela de login, o usuário deve clicar em __Receber chave de acesso rápido por email__
-2. Na tela seguinte, o usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-3. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-4. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Entrar__ ![fill-access-token-pt](https://images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
+2. Na tela seguinte, o usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+3. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+4. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Entrar__ ![fill-access-token-pt](//images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
 
 ### Entrar com email e senha
 
@@ -56,11 +56,11 @@ Este tipo de login __solicita email e senha__ para que o cliente possa se autent
 - Caso o cliente precise __cadastrar uma senha__, ele deve seguir os passos abaixo:
 
 1. Na tela de login, o usuário deve clicar em __Entrar com email e senha__
-2. Na tela seguinte, o usuário deve clicar em  __Não tem uma senha? Cadastre agora__ ![register-password-pt](https://images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
-3. O usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-4. Na tela seguinte, o usuário deve escrever sua nova senha nos campos __Nova senha__ e __Confirmar nova senha__ e, então, clicar no botão __Cadastrar nova senha__ ![register-new-password-pt](https://images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
-5. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-6. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Alterar senha__ ![change-password-pt](https://images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)    
+2. Na tela seguinte, o usuário deve clicar em  __Não tem uma senha? Cadastre agora__ ![register-password-pt](//images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
+3. O usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+4. Na tela seguinte, o usuário deve escrever sua nova senha nos campos __Nova senha__ e __Confirmar nova senha__ e, então, clicar no botão __Cadastrar nova senha__ ![register-new-password-pt](//images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
+5. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+6. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Alterar senha__ ![change-password-pt](//images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)    
 
 ### Login por rede social
 
diff --git a/docs/tutorials/pt/how-change-order-works-beta.md b/docs/tutorials/pt/how-change-order-works-beta.md
new file mode 100644
index 000000000..4fb5057d4
--- /dev/null
+++ b/docs/tutorials/pt/how-change-order-works-beta.md
@@ -0,0 +1,77 @@
+---
+title: 'Como funciona a Alterar pedido (Beta)'
+id: 56TO0bOFXsfmpc7YZ3wIUZ
+status: PUBLISHED
+createdAt: 2023-11-27T14:51:09.723Z
+updatedAt: 2024-04-09T17:58:34.469Z
+publishedAt: 2024-04-09T17:58:34.469Z
+firstPublishedAt: 2023-11-27T22:39:50.675Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: como-funciona-a-alterar-pedido-beta
+locale: pt
+legacySlug: como-funciona-a-alterar-pedido-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+<div class="alert alert-info">
+Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a <b>Alterar pedido (Beta)</b>, entre em contato com <a href="https://help.vtex.com/pt/support">nosso Suporte</a> e informe o(s) <a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> nos quais deseja ativá-la.
+</div>
+
+A funcionalidade **Alterar pedido (beta)** permite que você mude um pedido de diversas maneiras, seja a mudança motivada pela vontade do cliente, pela indisponibilidade de produtos ou outros motivos. Os principais tipos de alteração de pedidos são: 
+
+* **Adicionar:** uma quantidade de itens ou novos produtos.
+* **Remover:** uma quantidade parcial ou total de itens.
+* **Alterar peso:** os itens podem passar a ter um peso maior ou menor.
+* **Substituir itens:** trocar itens por outros, incluindo itens precificados por peso.
+* **Alterar preço:** mudar valor total do pedido.
+
+Para ver o passo a passo completo de como realizar cada ação, veja a documentação [Como alterar pedidos (Beta)](https://help.vtex.com/pt/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw). O artigo atual aborda outros aspectos da **Alterar pedido (Beta)** e está organizado da seguinte forma:
+
+* [Alterações pelo Admin VTEX e API](#alteracoes-pelo-admin-vtex-e-api)
+* [Características gerais](#caracteristicas-gerais)
+* [Mudanças de preço](#mudancas-de-preco)
+
+## Alterações pelo Admin VTEX e API
+
+Existem duas vias pelas quais um pedido pode ser alterado, veja os detalhes na tabela a seguir:
+
+| **Como alterar** | **Descrição** | **Status que admite alteração** |
+|:---:|:--- |:--- |
+| Via Admin VTEX | <p>A alteração é feita pela <a href="https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl">página de detalhes do pedido</a>, que pode ser acessada em <b>Pedidos > Todos os pedidos</b>, selecionando o pedido desejado.</p><p>Também é possível acessar o pedido usando a barra de busca no topo do Admin VTEX. Para isso, clique sobre a barra, selecione a opção <b>Pedidos</b> e utilize algum dos seguintes critérios:</p><p><ul><li>ID do pedido</li><li>Nome do cliente</li><li>Email do cliente</li><li>Documento do cliente</li></ul></p><p><b>Artigo no Help Center:</b> <a href="https://help.vtex.com/pt/tutorial/como-alterar-pedidos-beta--7btlG91rb6sHpW1dkd2kBw">Como alterar pedidos (Beta)</a></p> | <p><ul><li><code>preparando entrega</code></li></ul></p> |
+| Via API | Altera pelos endpoints:<p><ul><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/preview">Preview order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-">Get order change detail</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes">Get order change history</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/retry">Retry order change</a></li><li><a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/order-system/orders/-changeOrderId-/changes/-changeRequestId-/cancel">Cancel order change</a></li></ul></p>| <p><ul><li><code>ready-for-handling</code></li><li><code>handling</code></li><li><code>waiting-for-fulfillment</code></li><li><code>ready for invoicing</code></li></ul></p> |
+
+O histórico de alterações do pedido fica registrado na sua [página de detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), na seção **Histórico de itens alterados**. Para consultar essa informação por API, utilize o endpoint [Get order change history](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/order-system/orders/-changeOrderId-/changes).
+
+## Características gerais
+
+A **Alterar pedidos (beta)** possui características específicas, como apresentado na tabela a seguir:
+
+| **Aspecto** | **Descrição** |
+| :---: | :--- |
+| Número de alterações do pedido | Não existe um limite para quantas vezes um pedido pode ser alterado. |
+| Pedidos incompletos | Não é possível alterar <a href="https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos--tutorials_294">pedidos incompletos</a>, aqueles que não têm todas as informações necessárias para serem processados pela plataforma VTEX. |
+| Contas franquia | É possível alterar pedidos nos quais o seller é um conta franquia. |
+| Marketplace VTEX, certificado, parceiro e externo | <p>A alteração de pedidos se comporta de forma diferente nos vários cenários de marketplace na VTEX:</p><p><ul><li>É possível alterar pedidos de lojas que atuam tanto como seller VTEX quanto como <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex">marketplace VTEX</a>.</li><li>É possível alterar pedidos de <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a> quando são realizados em <a href="https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces">marketplaces externos</a>.</li><li>Não é possível alterar pedidos realizados em <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-certificados">marketplaces certificados</a> e <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros">marketplaces parceiros</a>.</li></ul></p> |
+| Reserva | A <a href="https://help.vtex.com/pt/tutorial/how-does-reservation-work--tutorials_92">reserva</a> de itens em cenários de alteração de pedidos é automática. |
+| Atualização de inventário | Ao alterar um pedido, o <a href="https://help.vtex.com/pt/tutorial/inventory-management--tutorials_139">inventário</a> da loja não é atualizado automaticamente, isso precisa ser feito ela loja no Admin VTEX em <b>Catálogo > Estoque > Gerenciamento de inventário</b>, ou via API, usando o endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>. |
+| Permissão no Licence Manager | <p>Para um usuário ser capaz de alterar pedidos, o seu <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> precisa estar associado a pelo menos um dos seguintes <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos do Licence Manager</a>:</p><p><ul><li><code>Orders Full Access</code></li><li><code>Change order</code></li></ul></p> |
+
+## Mudanças de preço
+
+Quando a alteração de itens do pedido aumenta ou diminui o valor original da compra, a comunicação do módulo **Pedidos** é feita de forma automática com **Pagamentos** e acontece da seguinte forma:
+
+* **Preço menor após alteração:** uma notificação é enviada ao [gateway](https://help.vtex.com/pt/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#gateway) de pagamento para estornar o valor que deve ser devolvido ao cliente.
+* **Preço maior após alteração:** uma notificação é enviada ao gateway de pagamento para solicitar que o cliente pague o valor adicional.
+
+Veja na tabela abaixo mais informações sobre pagamento e fatura na alteração de pedidos:
+
+| **Aspecto** | **Informações** |
+|:---:|:--- |
+| Condições para aumentar preço do pedido | <p>Só é possível aumentar o preço de um pedido quando ele atende aos seguintes critérios:</p><p><ul><li>O pedido foi feito com cartão de crédito, <a href="https://help.vtex.com/pt/tutorial/setting-up-payments-notes--5pW7avTwtyQcMu4uiW8quQ">promissórias</a> ou <a href="https://help.vtex.com/pt/tutorial/customer-credit-overview--1uIqTjWxIIIEW0COMg4uE0">customer credit</a>.</li><li>O <a href="https://help.vtex.com/pt/tutorial/what-is-an-acquirer--7N1oRTG8dGmOiIugC0cs4E">adquirente</a> do pedido permite transações sem o código CVV.</li><li>O adquirente do pedido permite duas transações de cobrança no mesmo pedido.</li></ul></p><p>Se o <a href="https://help.vtex.com/pt/tutorial/o-que-e-conector--3lze0Cu0bmyC6u2o2iaeEA">conector</a> não permitir alterações para valores maiores, uma nova transação será realizada com o valor excedente, e a transação não terá vínculo com o pedido original.</p> |
+| Alteração de pedido liquidado | <p>No <a href="https://help.vtex.com/pt/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/1xjzgJZvqwaI1rfxLMCC3Y">fluxo de transação</a>, o pedido pode ser alterado no status `settled` (liquidado), desde que cumpra as seguintes condições:</p><p><ul><li>O pedido foi feito com um cartão de crédito.</li><li>A liquidação do pagamento ocorre antes do pedido ser faturado.</li><li>O conector de pagamento está configurado para permitir reembolsos parciais. Atualmente, a <a href="https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv">Adyen</a> é o único conector de pagamento que suporta essa operação.</li></ul><p><p>Pedidos em que a transação se encontra com status <code>finished</code> (concluído) não podem ser alterados.</p> |
+| Transação compartilhada entre sellers e marketplace | É possível alterar pedidos que envolvem mais um de seller e pagamentos no ambiente do marketplace, ou seja, cenários com <a href="https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx">split de pagamento</a>. |
+| Descontos | Não é possível alterar o pedido aplicando descontos maiores ou iguais ao valor total do pedido original. |
+| Fatura | <p>Com relação à <a href="https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT">fatura</a>, a alteração de pedidos se comporta da seguinte forma:</p><p><ul><li>Se o pedido já foi <a href="https://help.vtex.com/pt/tutorial/como-faturar-um-pedido--7p1h852V5t54KyscpgxE2v">faturado</a> por completo, ele não pode mais ser alterado.</li><li>Pedidos ainda não faturados ou apenas <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente faturados</a> podem sim ser alterados.</li><li>O valor das faturas parciais do pedido alterado precisa ser igual ou maior que o valor de uma fatura já emitida.</li><li>Se o valor total do pedido alterado for menor do que o valor de uma fatura já emitida, ele não pode ser alterado.</li></ul></p><p>Em geral, é o faturamento do pedido que deflagra a liquidação do pagamento. Este comportamento é diferente para lojas que configuraram a <a href="https://help.vtex.com/pt/tutorial/configuring-maximum-automatic-payment-settlement-time-frame--7dwcaxrcgcFJUk7umqPBw2">liquidação automática</a>.</p> |
+
diff --git a/docs/tutorials/pt/how-dns-configuration-works-on-vtex.md b/docs/tutorials/pt/how-dns-configuration-works-on-vtex.md
new file mode 100644
index 000000000..3eba1a673
--- /dev/null
+++ b/docs/tutorials/pt/how-dns-configuration-works-on-vtex.md
@@ -0,0 +1,37 @@
+---
+title: 'Como funciona a configuração de DNS na VTEX'
+id: 2P5k3oMYOj7TgSK4Mrxmgy
+status: PUBLISHED
+createdAt: 2024-01-23T16:53:52.076Z
+updatedAt: 2024-01-23T17:00:29.714Z
+publishedAt: 2024-01-23T17:00:29.714Z
+firstPublishedAt: 2024-01-23T16:58:57.454Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: como-funciona-a-configuracao-de-dns-na-vtex
+locale: pt
+legacySlug: como-funciona-a-configuracao-de-dns-na-vtex
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+A configuração do DNS é um passo essencial para realizar o go-live da sua loja. Na VTEX, é necessária uma configuração específica do sistema de DNS (_Domain Name System_) para que a loja funcione corretamente. O DNS é o sistema que traduz nomes de domínio (como `minhaloja.com`) em endereços IP de servidores que armazenam os arquivos necessários para exibir uma página da web.
+
+Para configurar o DNS, é preciso criar um [CNAME](https://www.cloudflare.com/pt-br/learning/dns/dns-records/dns-cname-record/) para o domínio principal da loja, direcionando-o para `{dominioPrincipal}.cdn.vtex.com`. Por exemplo, uma loja `www.minhaloja.com`  deve criar um CNAME que aponte para `www.minhaloja.com.cdn.vtex.com`.
+
+O funcionamento dos redirecionamentos ocorre em etapas:
+
+1. O CNAME criado pela sua equipe encaminha o tráfego da loja para um local específico na infraestrutura da VTEX.
+
+    `www.minhaloja.com` 🠖 `CNAME `🠖 `www.minhaloja.com.cdn.vtex.com`
+2. Internamente, a VTEX configura um segundo CNAME que direciona para o serviço da Azion ou CloudFront.
+
+    `www.minhaloja.com.cdn.vtex.com` 🠖 `CNAME` 🠖 `uug412qft7.map.azionedge.net`
+3. Finalmente, um redirecionamento do tipo A conduz a rota do serviço Azion/CloudFront para um endereço IP específico.
+
+    `uug412qft7.map.azionedge.net` 🠖 `A` (tipo de registro que contém um endereço IP) 🠖 `185.76.11.52`
+
+Essas configurações garantem que o endereço IP resolvido seja dinâmico, podendo mudar a qualquer momento. Isto acontece porque este endereço IP se adapta para corresponder ao servidor de CDN (_Content Delivery Network_) mais próximo da localização do visitante. Esta adaptação melhora o desempenho do site, já que os arquivos são entregues a partir de servidores mais próximos geograficamente do visitante.
+
+Para mais informações sobre configuração de DNS na VTEX, veja [Go-live](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj).
+
diff --git a/docs/tutorials/pt/how-do-i-terminate-my-contract-with-vtex.md b/docs/tutorials/pt/how-do-i-terminate-my-contract-with-vtex.md
index e63265ccd..cda9d88fa 100644
--- a/docs/tutorials/pt/how-do-i-terminate-my-contract-with-vtex.md
+++ b/docs/tutorials/pt/how-do-i-terminate-my-contract-with-vtex.md
@@ -3,19 +3,19 @@ title: 'Como faço para rescindir meu contrato com a VTEX?'
 id: HhPeg8EOismMSImoWwaI8
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:36.822Z
-updatedAt: 2019-12-31T15:22:44.073Z
-publishedAt: 2019-12-31T15:22:44.073Z
+updatedAt: 2024-01-18T16:03:47.790Z
+publishedAt: 2024-01-18T16:03:47.790Z
 firstPublishedAt: 2019-01-24T22:00:07.201Z
 contentType: tutorial
 productTeam: Financial
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: como-faco-para-rescindir-meu-contrato-com-a-vtex
 locale: pt
 legacySlug: como-faco-para-rescindir-meu-contrato-com-a-vtex
 subcategory: 6SJnrkKDjGwSqKkMuQMOmm
 ---
 
-Para efetuar o cancelamento do seu contrato e deixar de utilizar a plataforma VTEX, é necessário que você abra um [ticket](https://support.vtex.com/hc/pt-br/requests) comunicando sua decisão ao Financeiro.
+Para efetuar o cancelamento do seu contrato e deixar de utilizar a plataforma VTEX, é necessário que você abra um [ticket](https://help.vtex.com/pt/support ) comunicando sua decisão ao Financeiro.
 
 ## Certifique-se de que seu chamado contenha as seguintes informações:
 
@@ -25,4 +25,4 @@ Para efetuar o cancelamento do seu contrato e deixar de utilizar a plataforma VT
 
 Feito isso, o processo será iniciado internamente e em seguida um distrato para assinatura eletrônica será enviado via __Clicksign__.
 
-Caso seja confirmado o desejo do cliente em relação à rescisão, __não será cobrada nenhuma multa.__ A última cobrança feita será referente ao mês da solicitação da rescisão. Seu painel administrativo será __retirado do ar nos primeiros 5 dias do mês subsequente__ à solicitação.
+Caso se confirme o desejo de rescisão do cliente, __o aviso prévio e as cláusulas de multa serão verificados e cobrados no faturamento do cliente.__ Seu painel administrativo será __retirado do ar nos primeiros 5 dias do mês subsequente__ à solicitação.
diff --git a/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index 788ebc7f7..ed1f0d91f 100644
--- a/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -33,16 +33,16 @@ O módulo Layout abrange a home, catálogo (busca, categorias e produtos), landi
 2. Acesse **Sites and channels**.
 3. Acesse o website desejado.
 4. Abra a pasta raiz do website.
-![instrução CMS -pt](https://images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
+![instrução CMS -pt](//images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
 5. A tela que foi aberta apresenta todas as pastas que estão no primeiro nível do site. Para cada pasta pertinente, clique em **Edit** - para a home, considere o botão do topo;
-![CMS edit PT](https://images.ctfassets.net/alneenqid6w5/1kHZcohcNawW2AEU6sKAAC/834bb139945132df8e23bd0b8dc9360f/edit_CMS.png)
+![CMS edit PT](//images.ctfassets.net/alneenqid6w5/1kHZcohcNawW2AEU6sKAAC/834bb139945132df8e23bd0b8dc9360f/edit_CMS.png)
 6. Na caixa de seleção **Protocol**, selecione a opção **HTTPS**;
-![CMS: protocol HTTPS ](https://images.ctfassets.net/alneenqid6w5/4d64p6oOPuWgMcAmmeqiKY/062e9c9ec3423f8ed6344436c07f8544/HTTPS.png)
+![CMS: protocol HTTPS ](//images.ctfassets.net/alneenqid6w5/4d64p6oOPuWgMcAmmeqiKY/062e9c9ec3423f8ed6344436c07f8544/HTTPS.png)
 7. Clique em **Save Folder**.
 
 Atenção às pastas que possuem subpastas, como Departamento, Categoria, Produto e outras pastas, incluindo também as criadas para customização da loja. 
 
 No exemplo a seguir, a pasta dinâmica **@Categoria@**, contida em **Categoria**, que deve ser também editada: 
-![cms: subcategoria edit](https://images.ctfassets.net/alneenqid6w5/7GQxgjBhRKomoSSicuMMeE/530405e8da5a8f61ccdfb1ca3285ffdd/subcategoria_edit.png)
+![cms: subcategoria edit](//images.ctfassets.net/alneenqid6w5/7GQxgjBhRKomoSSicuMMeE/530405e8da5a8f61ccdfb1ca3285ffdd/subcategoria_edit.png)
 
 Após cache de até 10 minutos as alterções irão vigorar.
diff --git a/docs/tutorials/pt/how-do-reversals-work-when-an-item-is-returned.md b/docs/tutorials/pt/how-do-reversals-work-when-an-item-is-returned.md
index 88a31d9c5..47bf2cf31 100644
--- a/docs/tutorials/pt/how-do-reversals-work-when-an-item-is-returned.md
+++ b/docs/tutorials/pt/how-do-reversals-work-when-an-item-is-returned.md
@@ -3,8 +3,8 @@ title: 'Funcionamento do estorno quando há devolução do item'
 id: frequentlyAskedQuestions_298
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.904Z
-updatedAt: 2021-08-12T18:29:59.905Z
-publishedAt: 2021-08-12T18:29:59.905Z
+updatedAt: 2024-02-28T17:25:13.906Z
+publishedAt: 2024-02-28T17:25:13.906Z
 firstPublishedAt: 2019-01-24T21:55:16.859Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/how-does-reservation-work.md b/docs/tutorials/pt/how-does-reservation-work.md
index 118bad6bf..3b48b2422 100644
--- a/docs/tutorials/pt/how-does-reservation-work.md
+++ b/docs/tutorials/pt/how-does-reservation-work.md
@@ -3,8 +3,8 @@ title: 'Como a reserva funciona'
 id: tutorials_92
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:56.753Z
-updatedAt: 2023-04-28T22:58:58.294Z
-publishedAt: 2023-04-28T22:58:58.294Z
+updatedAt: 2023-10-18T17:20:21.911Z
+publishedAt: 2023-10-18T17:20:21.911Z
 firstPublishedAt: 2017-04-27T23:00:42.751Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index 3d0b16af3..f40475e0f 100644
--- a/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -31,7 +31,7 @@ Em vez de usar os IDs de cada item (o que geraria pedidos separados em nosso sis
 
 Você pode encontrar os dois IDs através do relatório enviado a partir do painel de integrações no Admin da VTEX.
 
-![Pedidos Mercado Livre](https://images.ctfassets.net/alneenqid6w5/2NFqrrWGlqQMYSOugYo8kQ/deba1c9f1ffb01e0db3f2874fb7ee8a3/Pedidos_Mercado_Livre.png)
+![Pedidos Mercado Livre](//images.ctfassets.net/alneenqid6w5/2NFqrrWGlqQMYSOugYo8kQ/deba1c9f1ffb01e0db3f2874fb7ee8a3/Pedidos_Mercado_Livre.png)
 
 <div class="alert alert-warning">
 Essa lógica de funcionamento se aplica a todos os tipos de entrega, com exceção daqueles que incluem pickup points. Nesses casos, a plataforma continua a utilizar o ID antigo.
diff --git a/docs/tutorials/pt/how-does-the-score-field-work.md b/docs/tutorials/pt/how-does-the-score-field-work.md
index 6eae008eb..7eeb403ca 100644
--- a/docs/tutorials/pt/how-does-the-score-field-work.md
+++ b/docs/tutorials/pt/how-does-the-score-field-work.md
@@ -3,37 +3,55 @@ title: 'Como funciona o campo Score?'
 id: 1BUZC0mBYEEIUgeQYAKcae
 status: PUBLISHED
 createdAt: 2018-02-16T16:17:51.610Z
-updatedAt: 2023-03-27T13:32:27.264Z
-publishedAt: 2023-03-27T13:32:27.264Z
+updatedAt: 2024-01-05T20:42:03.525Z
+publishedAt: 2024-01-05T20:42:03.525Z
 firstPublishedAt: 2018-02-16T18:09:11.291Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 1malnhMX0vPThsaJaZMYm2
 slug: como-funciona-o-campo-score
 locale: pt
 legacySlug: como-funciona-o-campo-score
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-O campo __Score__, disponível nos cadastros de __Produto__, __Categoria__ e __Marca__, é o valor utilizado para garantir a ordenação de produtos na sua loja e, também, como critério de desempate para outras ordenações comuns, como menor preço, melhor desconto etc. Ao preencher esse campo, é possível definir a prioridade de alguns produtos em relação a outros, tanto na vitrine quanto na página de resultado de busca.
+O campo **Score**, disponível nos formulários de cadastro de **Produto**, **Categoria** e **Marca**, é um valor utilizado para ordenar produtos na loja. Essa pontuação serve como critério de desempate para outras ordenações comuns, como menor preço, melhor desconto, entre outras. Ao preencher o campo **Score**, é possível definir a prioridade de alguns produtos em relação a outros, tanto na vitrine quanto na página de resultado de busca.
 
-O critério para enumerar o campo segue uma simples ordenação (1, 2, 3, 4…) e só precisa ser seguido para apresentar a sequência na vitrine da loja ou na página de resultado de busca. 
+O critério para enumerar o campo segue uma ordenação numérica para apresentar a sequência na vitrine da loja ou na página de resultado de busca. Por padrão, produtos sem um score cadastrado se comportam como se tivessem score igual a 0.
 
-No entanto, quando se trata de Score do Produto, é importante saber que ele é a soma do seu próprio score mais os de categoria e marca. Ou seja: `Score do produto + Score da Categoria + Score da Marca`.
+O score total de um produto é a soma do seu próprio score, mais os scores definidos para a categoria e para a marca: `score total do produto = score do produto + score da categoria + score da marca`.
 
-Você pode utilizar os parâmetros abaixo para implementar a ordenação:
+Recomendamos definir o score a nível de produto, já que o mais comum é que sua vitrine esteja sempre em constante mudança.
 
-- __Ordem ascendente:__ `?O=OrderByScoreASC`
-- __Ordem descendente:__ `?O=OrderByScoreDESC`
+Um exemplo para o uso do score pode ser em eventos pontuais, quando sua loja precisa colocar produtos específicos na frente de outros para que a visualização seja garantida.
 
-O mais apropriado é que você faça o input do score produto a produto, já que o mais comum é que sua vitrine esteja sempre em constante mudança.
+## Score na busca VTEX
 
-Um bom exemplo para o uso do Score pode ser em eventos pontuais, quando sua loja precisa colocar produtos específicos na frente de outros para que a visualização seja garantida.
+Se a loja utiliza a [busca VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-busca-da-vtex--tutorials_542), é possível utilizar os parâmetros abaixo para implementar a ordenação por score:
+
+* **Ordem ascendente** (produtos com score mais baixo aparecem primeiro): `?O=OrderByScoreASC`
+* **Ordem descendente** (produtos com score mais alto aparecem primeiro): `?O=OrderByScoreDESC`
+
+## Score no VTEX Intelligent Search
+
+Os parâmetros `OrderByScoreASC` e `OrderByScoreDESC` não são suportados pelo [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb), apenas pela [busca VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-busca-da-vtex--tutorials_542).
+
+O [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb) não permite uma ordenação direta dos produtos pela pontuação definida no campo **Score**. Ao utilizar um desses parâmetros no VTEX Intelligent Search, ocorre a ordenação padrão, que é por [relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+Por outro lado, o score do Catálogo consegue compor a [relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) do Intelligent Search em meio aos outros critérios, sendo possível atribuir um peso maior a ele ou até torná-lo prioritário. Para essa finalidade de compor relevância, quanto maior o score, maior o peso, ou seja, o comportamento é decrescente: produtos com score mais alto são priorizados.
+
+Ignorando a influência de outros critérios, ou mesmo considerando o uso de ordenação prioritária, no VTEX Intelligent Search, os produtos sem nenhum score cadastrado aparecem após os produtos com score cadastrado nos resultados de busca.
+
+É necessário ponderar se essa prática seria adequada ao seu caso de uso em relação a outros critérios calculados automaticamente pelo sistema, como popularidade e vendas. Tornar um critério prioritário sobrepõe todos os outros, inclusive atingindo o mesmo objetivo do `OrderByScore`, ignorando as demais configurações de relevância.
+
+Para realizar a ordenação manual de itens de forma isolada, recomendamos usar [Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), evitando efeitos indesejáveis e respeitando as configurações de relevância.
+
+## Editar o score de um produto
 
 Para adicionar ou alterar um score relacionado a um produto, siga estes passos:
 
-1. No Admin VTEX, acesse **Catálogo > Produtos e Skus**.
+1. No Admin VTEX, acesse **Catálogo > Produtos e SKUs**.
 2. Clique em `Adicionar Produto` para criar um novo produto ou clique em `Alterar` no produto que deseja editar.
 3. Insira o valor desejado do score no campo **Score (usado para ordenação de busca)**.
 
-![posicao-Score-PT](https://images.ctfassets.net/alneenqid6w5/6SGu9GBtxou7sLg5rM59vl/f02f302fc3de0346b7ec9d794c413da3/Screenshot_6.png)
+![posicao-Score-PT](//images.ctfassets.net/alneenqid6w5/6SGu9GBtxou7sLg5rM59vl/f02f302fc3de0346b7ec9d794c413da3/Screenshot_6.png)
diff --git a/docs/tutorials/pt/how-does-the-type-of-delivery-work.md b/docs/tutorials/pt/how-does-the-type-of-delivery-work.md
index 9eba703ac..c37123b41 100644
--- a/docs/tutorials/pt/how-does-the-type-of-delivery-work.md
+++ b/docs/tutorials/pt/how-does-the-type-of-delivery-work.md
@@ -1,37 +1,37 @@
 ---
-title: 'Como funciona o tipo de entrega'
+title: 'Como funciona o tipo de envio'
 id: tutorials_126
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:17.250Z
-updatedAt: 2023-05-31T14:45:20.914Z
-publishedAt: 2023-05-31T14:45:20.914Z
+updatedAt: 2023-11-13T15:00:10.346Z
+publishedAt: 2023-11-13T15:00:10.346Z
 firstPublishedAt: 2017-04-27T23:00:44.173Z
 contentType: tutorial
 productTeam: Post-purchase
 author: authors_84
-slug: como-funciona-o-tipo-de-entrega
+slug: como-funciona-o-tipo-de-envio
 locale: pt
 legacySlug: como-funciona-o-tipo-de-entrega
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-Tipo de entrega é um dado no cadastro de transportadora que fará o agrupamento de transportadores com o mesmo valor. Funciona como uma categoria e como uma identificação que será exibida no carrinho, na finalização de compra.
+Tipo de envio é um dado no cadastro de transportadora que fará o agrupamento de transportadores com o mesmo valor. Funciona como uma categoria e como uma identificação que será exibida no carrinho, na finalização de compra.
 
 ## Agrupar frete
 
-O tipo de frete como agrupador será usado quando mais de uma transportadora realiza o mesmo tipo de entrega. Ou seja, deve ser utilizado o mesmo tipo quando as transportadoras possuem características parecidas.
+O tipo de frete como agrupador será usado quando mais de uma transportadora realiza o mesmo tipo de envio. Ou seja, deve ser utilizado o mesmo tipo quando as transportadoras possuem características parecidas.
 
-> Exemplo: as transportadoras _EnglishGo_ e _Transportista_ fazem entregas do tipo **Normal**, a transportadora _TranspAgenda_ faz entrega do tipo **Agendado**, enquanto as transportadoras _Expressa_ e a _Ligeirinho_ realizam entregas do tipo **Expressa**.
+> Exemplo: as transportadoras _EnglishGo_ e _Transportista_ fazem envio do tipo **Normal**, a transportadora _TranspAgenda_ faz envio do tipo **Agendado**, enquanto as transportadoras _Expressa_ e a _Ligeirinho_ realizam envios do tipo **Expressa**.
 
 ## Exibir no fechamento de compra
 
-No carrinho, não são exibidos os nomes das transportadoras e sim os tipos de frete. Por isso, é importante que as designações sejam amigáveis, e que cada transportadora exibida tenha um tipo diferente. Do contrário, será exibida a transportadora com menor prazo e valor dentro do tipo.
+No carrinho, não são exibidos os nomes das transportadoras e sim os tipos de envio. Por isso, é importante que as designações sejam amigáveis, e que cada transportadora exibida tenha um tipo diferente. Do contrário, será exibida a transportadora com menor prazo e valor dentro do tipo.
 
 Segue uma imagem de como seriam exibidas as opções de frete no fechamento de compra de acordo com o exemplo citado:
 
-![Transportadoras Checkout](https://images.ctfassets.net/alneenqid6w5/1c85gOqY9uokEQ2UGI4YAI/87dd9e5eeb8d1a45233e80ce1b7b8de3/Transportadoras_Checkout.png)
+![Transportadoras Checkout](//images.ctfassets.net/alneenqid6w5/1c85gOqY9uokEQ2UGI4YAI/87dd9e5eeb8d1a45233e80ce1b7b8de3/Transportadoras_Checkout.png)
 
 Note que, mesmo tendo cinco transportadoras cadastradas, só aparecem duas opções de frete: **Agendado** e **Normal**. Isso acontece por dois motivos: 
 
-1. O produto escolhido pertence a um estoque associado apenas a transportadoras que fazem entregas do tipo **Normal** e **Agendado**.
-2. Mesmo que existam duas transportadoras cadastradas para entregas do tipo **Normal**, só é exibida aquela que faz o serviço com menor preço ou menor prazo.
+1. O produto escolhido pertence a um estoque associado apenas a transportadoras que fazem envio do tipo **Normal** e **Agendado**.
+2. Mesmo que existam duas transportadoras cadastradas para envios do tipo **Normal**, só é exibida aquela que faz o serviço com menor preço ou menor prazo.
diff --git a/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md b/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md
index f3f5ac5a4..401bd64d0 100644
--- a/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md
+++ b/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md
@@ -21,6 +21,6 @@ A conta do desconto é: `monthly fee dividido pelo número de dias do mês de co
 
 Então, se a sua mensalidade teve um valor de R$ 750 no mês de maio - 31 dias - e você contratou a VTEX no dia 06 de maio, serão descontados R$ 145,16 em sua próxima fatura.
 
-![prorata PT](https://images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
+![prorata PT](//images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
 
 A conta feita foi: `R$ 750/31 = R$ 24,19 x 3 (dias) = R$ 145,16`
diff --git a/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md b/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md
index 1e57af8c8..96603982c 100644
--- a/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md
+++ b/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md
@@ -3,8 +3,8 @@ title: 'Como é calculado o prazo de entrega do pedido'
 id: 1TOuKCIjGQmqOqQkEqCg82
 status: PUBLISHED
 createdAt: 2018-01-12T12:56:52.805Z
-updatedAt: 2023-03-29T14:09:06.429Z
-publishedAt: 2023-03-29T14:09:06.429Z
+updatedAt: 2023-09-23T00:34:19.034Z
+publishedAt: 2023-09-23T00:34:19.034Z
 firstPublishedAt: 2018-01-12T14:42:26.502Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,27 +15,22 @@ legacySlug: como-e-calculado-o-prazo-de-entrega-do-pedido
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-O prazo de entrega de um pedido leva em consideração os __tempos de custo__ definidos para as cinco etapas da rota de logística:
-- Estoque.
-- Doca.
-- Transportadora.
-- Feriados.
-- Horários de corte.
+O prazo de envio de um pedido leva em consideração os seguintes aspectos da logística:
 
-Ou seja, para cada uma dessas etapas você pode definir um tempo de custo - e o prazo de entrega que o seu cliente verá no checkout é a soma desses tempos de custo.
+- [Lead time](https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B)
+- [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+- [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
+- [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
 
-![deliveryCostTimes](//images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
+![lead_time_image_total_time_PT](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
 
-Os tempos de custo do __estoque__ e da __doca__ são definidos nas telas de configuração de cada uma dessas etapas, em **Envio > Estratégia de envio > Política de envio.**
+Você define um período para essas etapas e o prazo de envio que o seu cliente vê no checkout é uma soma desses períodos. 
 
-![calculoPrazoEntrega1](//images.contentful.com/alneenqid6w5/4QgQlroxxCK4iu6YoU2uIQ/a2df01bdbe2449e924a6380b5a39a19b/calculoPrazoEntrega1.png) 
+O tempo de envio da __transportadora__ é definido pela [tabela de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127), que precisa ser associada a sua estratégia de envio por meio de uma [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 
-![calculoPrazoEntrega2](//images.contentful.com/alneenqid6w5/6xAiBHXxwA2cMIaaK4AKm2/bfff8d81b7363121cc84de1149cfd587/calculoPrazoEntrega2.png)
+As configurações de política de envio, estoque e doca podem ser feitas pelo seu Admin VTEX, em **Envio > Estratégia de envio**, em abas diferentes. Já a configuração opcional do lead time pode ser realizada em **Catálogo > Gerenciamento de inventário**.
 
-O tempo de custo da __transportadora__ é definido na tabela de frete, enviada à VTEX por meio da tela de configuração da transportadora, também na página Estratégia de envio.
+### Saiba mais
 
-![calculoPrazoEntrega3](//images.contentful.com/alneenqid6w5/2bL9Gw0AeswGAeKSqYCYw4/57c492eb08239d61e463839a768101ad/calculoPrazoEntrega3.png)
-
-### Para saber mais
-
-Por meio da simulação de frete, você pode verificar como o prazo de entrega de um pedido específico foi calculado. Entenda como no artigo [Verificar como o prazo de entrega de um pedido foi calculado](/pt/tutorial/verificar-como-o-prazo-de-entrega-de-um-pedido-foi-calculado).
+- [Simulador de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144)
+- [Verificar como o prazo de entrega de um pedido foi calculado](https://help.vtex.com/pt/tutorial/verificar-como-o-prazo-de-entrega-de-um-pedido-foi-calculado).
diff --git a/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md b/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md
index 42429e7d9..dd2a02723 100644
--- a/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md
+++ b/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md
@@ -3,8 +3,8 @@ title: 'Como é apurado o SLA de operação da plataforma?'
 id: frequentlyAskedQuestions_662
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:57.436Z
-updatedAt: 2019-12-31T17:00:45.718Z
-publishedAt: 2019-12-31T17:00:45.718Z
+updatedAt: 2024-03-11T22:38:31.694Z
+publishedAt: 2024-03-11T22:38:31.694Z
 firstPublishedAt: 2019-01-24T22:11:03.028Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,26 +15,25 @@ legacySlug: como-e-apurado-o-sla-de-operacao-da-plataforma
 subcategory: 5PYkoNDZyo2G80yiiqG2YW
 ---
 
-Além dos prazos, é preciso identificar o que assumimos como violação do SLA. Ou seja, o que realmente contará como tempo de indisponibilidade.
+Qualquer minuto de interrupção pode custar muito, tanto para as lojas quanto para a VTEX. Assim, procuramos ser o mais transparente possível em relação à saúde da nossa plataforma. Disponibilizamos a página [Status VTEX](https://status.vtex.com), onde registramos todos os incidentes que impactaram nosso SLA.
 
-Como nosso modelo comercial é baseado no rendimento da loja, fica muito claro para todo o time VTEX que qualquer minuto de interrupção custa muito, tanto para as lojas quando para a própria VTEX. Desta forma, procuramos ser o mais transparente possível em relação a saúde da nossa plataforma. Disponibilizamos a [página de status](http://status.vtex.com "página de status") onde registramos todos incidentes que impactaram nosso SLA. Esses eventos são contabilizados conforme abaixo.
+Para apurar violações do SLA, ou seja, contabilizar tempo de indisponibilidade da plataforma, consideramos os eventos a seguir:
 
-### São contabilizados
+- Interrupções na loja virtual que estejam impactando significativamente o número de pedidos realizados, por exemplo: loja fora do ar, lentidão no acesso, erro no checkout.
+- Interrupções com duração de no mínimo 10 minutos.
 
-- Qualquer interrupção na loja virtual que esteja impactando significativamente o número de pedidos realizados. Ex: loja fora do ar, lentidão no acesso, erro no checkout.
-- Contabilizamos interrupções com duração de no mínimo 10 minutos.
+<div class="alert alert-warning">
+  <p>Não contabilizamos manutenções agendadas como tempo de indisponibilidade.</p>
+</div>
 
-### Não são contabilizados
+## Verificar o status da VTEX
 
-- Manutenções agendadas.
-- Interrupção de algum serviço no módulo administrativo.
+Para facilitar a identificação de cenários de instabilidade, recomendamos verificar a página [Status VTEX](https://status.vtex.com) em caso de suspeita de indisponibilidade da ferramenta. O status é atualizado quando o incidente passa do prazo mínimo de 10 minutos, com as informações a seguir:
 
-### Verificando no status
+- __Investigando/Identificado__: o time está investigando o incidente e realizando as ações necessárias para restabelecer o serviço.
+- __Monitorando__: o incidente foi resolvido e o serviço estabilizado. O ambiente está sob monitoramento.
+- __Resolvido__: caso encerrado, com tempo total de interrupção do SLA registrado. Na maioria dos casos, o tempo total de interrupção é o somatório do tempo de indisponibilidade do incidente.
 
-Para facilitar a identificação desses cenários, sempre recomendamos que o status seja verificado a cada suspeita de indisponibilidade da ferramenta. O status é atualizado quando o incidente passa do prazo mínimo de 10 minutos, com as seguintes informações:
+## Saiba mais
 
-- __Investigando/Identificado__: Incidente sendo investigado pelo time. Time está tomando ação necessário para restabelecimento do serviço.
-- __Monitorando__: Incidente resolvido, serviço estabilizado. Ambiente sob monitoramento.
-- __Resolvido__: Caso encerrado. Registrado tempo total de interrupção. Na maioria dos casos, o SLA é o somatório do tempo de indisponibilidade de cada incidente.
-
-![](//images.contentful.com/alneenqid6w5/2Le8koNu7YUoICaquSSuuY/134a3f2ca7cee4614a09c96397573dd9/Screen_Shot_2016-04-22_at_16.28.39.png)
+- [Página de status da VTEX](https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ)
diff --git a/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md b/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
index 294b0c8b7..13d0eb543 100644
--- a/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
+++ b/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
@@ -3,8 +3,8 @@ title: 'Em quanto tempo um pedido de boleto sem pagamento é cancelado?'
 id: frequentlyAskedQuestions_300
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.983Z
-updatedAt: 2021-10-28T11:55:41.026Z
-publishedAt: 2021-10-28T11:55:41.026Z
+updatedAt: 2024-06-11T21:26:30.893Z
+publishedAt: 2024-06-11T21:26:30.893Z
 firstPublishedAt: 2019-01-24T22:03:31.971Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,26 @@ legacySlug: em-quanto-tempo-um-pedido-de-boleto-sem-pagamento-e-cancelado
 subcategory: 3Gdgj9qfu8mO0c0S4Ukmsu
 ---
 
-O pedido com boleto envolve o cancelamento de três itens, que podem gerar dúvidas. Por isso, antes vamos separar essas três definições para seguirmos com os prazos de cada uma delas.
+Quando um boleto emitido referente a uma ordem não é pago, o pedido pode ser cancelado. Para calcular o tempo total necessário para realizar o cancelamento desse pedido é necessário considerar os seguintes prazos:
+
+- [Prazo de validade do boleto](#prazo-de-validade-do-boleto)
+- [Prazo para cancelamento da reserva dos produtos](#prazo-para-cancelamento-da-reserva-dos-produtos)
+- [Prazo para cancelamento do pedido](#prazo-para-cancelamento-do-pedido)
 
 ## Prazo de validade do boleto
 
-A validade do boleto é o prazo para o boleto não ser mais aceito para realizar o pagamento. Esse prazo sempre será configurado na aba de Pagamentos no Admin, na configuração da afiliação, conforme imagem abaixo.
+A validade de um boleto é o período estabelecido (em dias) para que um cliente realize o pagamento de uma compra após ele ter sido emitido. Uma vez ultrapassado este período de tempo, o boleto é considerado expirado e não pode mais ser pago.
+
+Alguns provedores de pagamento permitem que a validade de um boleto seja configurado no Admin VTEX. Para verificar se o seu provedor de pagamento disponibiliza esta opção, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, digite o nome do provedor desejado e clique sobre ele.
+3. Na tela de configuração do provedor, verifique se existe algum campo disponível para configurar a validade do boleto e preencha com o valor desejado (em dias) .
+4. Clique em `Salvar`.
 
-![PT - Prazo de validade do boleto](https://images.ctfassets.net/alneenqid6w5/40DsZm4Pg4syu00CI2WykQ/8553e08e76e0f4fd511d30c8e7e47ab9/Prazo_de_validade_do_boleto_PT.png)
+<div class="alert alert-warning">
+Caso o seu provedor de pagamento não permita modificar a validade de boleto no Admin VTEX, é necessário entrar em contato com o suporte técnico do provedor e verificar os procedimentos necessários para a configuração de validade do boleto.
+</div>
 
 ## Prazo para cancelamento da reserva dos produtos
 
@@ -30,35 +43,19 @@ Para isso, o prazo para a liberação da reserva é calculado da seguinte forma:
 
 O prazo de vencimento da reserva do estoque é o **prazo de expiração do boleto +  quatro, cinco ou seis dias corridos**, seguindo as regras abaixo:
 
-- Quatro dias para quando a data de expiração do boleto for domingo, segunda ou terça;
-- Cinco dias para quando a data de expiração do boleto for quarta, quinta ou sexta;
-- Seis dias para quando a data de expiração do boleto for sábado.
+- **Quatro dias corridos**: quando a data de expiração do boleto for domingo, segunda ou terça.
+- **Cinco dias corridos**: quando a data de expiração do boleto for quarta, quinta ou sexta.
+- **Seis dias corridos**: quando a data de expiração do boleto for sábado.
 
-Para mais informações sobre como funciona a reserva, [clique aqui](/pt/tutorial/como-a-reserva-funciona).
+Para mais informações sobre a reserva de produtos, acesse [Como a reserva funciona](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92).
 
 ## Prazo para cancelamento do pedido
 
-O cancelamento do pedido é realizado 20 dias após o prazo acima, ou seja, **20 dias + prazo de cancelamento da reserva**.
-Tomando como exemplo a imagem acima, o pedido feito em uma quinta-feira e não pago seria cancelado 30 dias após a data de finalização:
-Prazo de cancelamento do boleto = **5** dias.
-Prazo de expiração da reserva = **5** + **5** = **10** dias.
-Prazo para cancelamento do pedido = **20 + 10 = 30 dias**.
-Esse tempo, de aproximadamente um mês, permite que a compra seja recuperada junto ao cliente e se utilize o mesmo pedido para finalizar este processo caso o mesmo deseje.
-
-## Prazo para cancelamento de boleto registrado
-
-Existem dois tipos de boletos: aqueles cujo status de pagamento a VTEX consegue verificar por meio de uma URL e aqueles em que essa verificação não é realizada. 
-
-Essa diferença acontece por conta do posicionamento de cada banco. Existem algumas instituições financeiras que cedem à VTEX o endpoint necessário para essa verificação, enquanto outras ainda não implementaram esse tipo de solução. 
-
-Atualmente, apenas o __Itaú Shopline__ e o __Bradesco__ disponibilizam esse tipo de integração.
-
-Desse modo, para esses dois bancos o cancelamento é feito da seguinte forma: existe uma janela de tempo entre o momento em que o cliente finaliza a compra e o momento em que, de fato, paga o boleto. Durante esse período, a VTEX realiza múltiplas chamadas de verificação junto ao banco. Esse processo dura, em média, sete dias corridos.
-
-Se o cliente não realizar o pagamento durante esse período, o boleto é cancelado. 
+O cancelamento do pedido é realizado 20 dias após a reserva ser cancelada, ou seja, **20 dias + prazo de cancelamento da reserva**.
 
-Caso você utilize outros adquirentes para processar os pagamentos via boleto, recomendamos que entre em contato com eles para informações a respeito do prazo para cancelamento do boleto.
+Por exemplo, um pedido realizado em uma quinta-feira e não pago, seria cancelado 30 dias após a data de finalização:
 
-## Para saber mais
+- Prazo de cancelamento do boleto = 5 dias.
+- Prazo de expiração da reserva = 5 + 5 = 10 dias.
+- Prazo para cancelamento do pedido = 20 + 10 = 30 dias.
 
-[Entenda como configurar boleto registrado](/pt/faq/como-configurar-boleto-registrado/).
diff --git a/docs/tutorials/pt/how-my-account-works.md b/docs/tutorials/pt/how-my-account-works.md
index e4b11edf4..2a957143d 100644
--- a/docs/tutorials/pt/how-my-account-works.md
+++ b/docs/tutorials/pt/how-my-account-works.md
@@ -3,8 +3,8 @@ title: 'Como funciona a Minha Conta'
 id: 2BQ3GiqhqGJTXsWVuio3Xh
 status: PUBLISHED
 createdAt: 2019-04-11T21:14:26.117Z
-updatedAt: 2023-04-24T23:39:56.581Z
-publishedAt: 2023-04-24T23:39:56.581Z
+updatedAt: 2023-12-21T14:09:42.863Z
+publishedAt: 2023-12-21T14:09:42.863Z
 firstPublishedAt: 2019-05-21T19:48:15.019Z
 contentType: tutorial
 productTeam: Identity
@@ -77,6 +77,10 @@ O botão `Adicionar endereço` permite incluir endereços diferentes daqueles j
 
 ## Pedidos
 
+<div class = "alert alert-info">
+Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
+</div>
+
 Essa aba traz a listagem completa dos pedidos realizados pelo cliente na sua loja. A lista é ordenada por data de criação e exibe detalhes como data do pedido, valor total da compra, ID do pedido, status e itens adquiridos.
 
 ![orders PT](//images.contentful.com/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/6f7d63f0581419353f76bc20429cd339/orders_PT.png)
@@ -116,7 +120,12 @@ Esse botão permite ao cliente mudar informações do pedido, como endereço, fo
 
 ## Cartões
 
-Na aba **Cartões**, o cliente tem autonomia para gerenciar os cartões de crédito relacionados à sua conta.  É possível incluir e editar os dados dos cartões de crédito já registrados no checkout. Para adicionar novos cartões, siga os passos abaixo:
+Na aba **Cartões**, o cliente tem autonomia para gerenciar os cartões de crédito relacionados à sua conta por meio das seguintes ações:
+
+- Inclusão de novos cartões
+- Remoção de cartões com data de vencimento expirada
+
+Para adicionar novos cartões, siga os passos abaixo:
 
 1. Abra a **Minha Conta** na loja.
 2. Clique na aba **Cartões**.
@@ -148,7 +157,7 @@ Nesta aba, o cliente pode gerenciar todas as suas assinaturas cadastradas, assim
 
 Esta aba pode ser acessada no painel esquerdo pelo item **Autenticação** nas configurações de perfil do usuário. Na aba são encontradas opções para gerenciamento de senha e gerenciamento de sessões.
 
-![My Authentication app PT](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
+![My Authentication app PT](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
 
 ### Gerenciamento de senha
 
@@ -158,7 +167,7 @@ O componente **Senha** permite que o usuário crie uma senha (caso ainda não po
 2. No campo **Código**, insira o código de verificação recebido por email.
 3. No campo **Nova senha**, insira a nova senha que deseja atribuir à sua conta. Abaixo do campo aparecem os requisitos que a senha deve obedecer para ser válida. Conforme a senha é digitada, os símbolos de cada requisito se alteram de vermelho para verde. A senha será válida somente se todos os símbolos estiverem verdes.
 4. Após ter inserido uma senha válida, clique no botão `SALVAR SENHA` para concluir a criação da senha.  
-![My Authentication create password PT](https://images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/3f8b8b62a8722e515edc0eae6322ff6a/My_Authentication_create_password_PT.png)
+![My Authentication create password PT](//images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/3f8b8b62a8722e515edc0eae6322ff6a/My_Authentication_create_password_PT.png)
 
 Para mudar a senha atual:
 
@@ -166,7 +175,7 @@ Para mudar a senha atual:
 2. Digite a senha atual no campo correspondente.
 3. Digite a nova senha no campo correspondente, obedecendo todos os requisitos.
 4. Clique no botão `SALVAR SENHA` para concluir a mudança de senha.  
-![My Authentication change password PT](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/94f7323e8d97d28a4d5dac042c5c620b/My_Authentication_change_password_PT.png)
+![My Authentication change password PT](//images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/94f7323e8d97d28a4d5dac042c5c620b/My_Authentication_change_password_PT.png)
 
 <div class="alert alert-info">
 Caso você tenha esquecido a senha, não é possível recuperá-la pelo componente de gerenciamento de senha. Para isso você deve sair da sessão atual, fazer uma tentativa de login usando email e senha, e clicar no link <strong>Esqueci minha senha</strong>.
@@ -180,7 +189,7 @@ Para visualizar as sessões ativas, clique no botão `VER SESSÕES` e você ser
 
 Para revogar o acesso das outras sessões, clique no botão `DESLOGAR` da sessão desejada.
 
-![My Authentication Session Management PT](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
+![My Authentication Session Management PT](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
 
 ## Configurações básicas
 
@@ -191,7 +200,7 @@ No **My Orders**, você pode determinar quais seções estarão visíveis para o
 * Em **ORDERS**, a opção <a class="far fa-check-square"></a> _Visible_ determina se o cliente tem a seção [Pedidos](#pedidos) para acompanhar seus pedidos.
 * Em **ADDRESSES**, a opção <a class="far fa-check-square"></a> _Visible_ define se o cliente vai ter a seção [Endereços](#enderecos) com detalhes do seu endereço.
 
-![vtex-my-account_PT](https://images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/12452e82c19c105a9aae17c483531fe2/vtex-my-account_PT.png)
+![vtex-my-account_PT](//images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/12452e82c19c105a9aae17c483531fe2/vtex-my-account_PT.png)
 
 Por padrão, as opções **CARDS** e **ORDERS** vem configuradas como visíveis. Para alterá-las ou habilitar outras configurações, realize os passos abaixo: 
 
diff --git a/docs/tutorials/pt/how-order-authorization-works.md b/docs/tutorials/pt/how-order-authorization-works.md
index e7a027dbb..47cf21904 100644
--- a/docs/tutorials/pt/how-order-authorization-works.md
+++ b/docs/tutorials/pt/how-order-authorization-works.md
@@ -3,8 +3,8 @@ title: 'Como funciona a Autorização de pedidos'
 id: 3MBK6CmKHAuUjMBieDU0pn
 status: PUBLISHED
 createdAt: 2019-03-25T17:18:05.295Z
-updatedAt: 2023-03-29T22:05:18.017Z
-publishedAt: 2023-03-29T22:05:18.017Z
+updatedAt: 2024-07-08T17:06:56.254Z
+publishedAt: 2024-07-08T17:06:56.254Z
 firstPublishedAt: 2019-03-25T17:24:44.319Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,7 +17,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos**, é possível controlar a aprovação de pedidos com divergência de preços na sua loja.
 
-![print_autorizacao_pedidos_PT](https://drive.google.com/uc?export=download&id=1pFXhxGs4pbwC18b3kbAHKGY4tHhMVbse)
+![print_autorizacao_pedidos_PT](//images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/92157acf2f5d379f30136b846e28a37f/print_autorizacao_pedidos_PT.png)
 
 A divergência de preços de pedidos podem ser encontradas em dois principais cenários:
 
diff --git a/docs/tutorials/pt/how-order-authorization-workss.md b/docs/tutorials/pt/how-order-authorization-workss.md
index c56b6df26..a33a268e1 100644
--- a/docs/tutorials/pt/how-order-authorization-workss.md
+++ b/docs/tutorials/pt/how-order-authorization-workss.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 No módulo de Gerenciamento de pedidos, a seção __Autorização de pedidos__ permite o controle e a aprovação de pedidos com divergências de preços na sua loja.
 
-![autorização-de-pedidos PT](https://images.ctfassets.net/alneenqid6w5/2oP1np8C9Cv004b8NPk1Jn/a7694ae95272db05344bf35d93206e58/autoriza____o-de-pedidos__PT.png)
+![autorização-de-pedidos PT](//images.ctfassets.net/alneenqid6w5/2oP1np8C9Cv004b8NPk1Jn/a7694ae95272db05344bf35d93206e58/autoriza____o-de-pedidos__PT.png)
 
 As divergências de preços entre pedidos podem ser encontradas em dois principais cenários: 
 
@@ -35,15 +35,15 @@ As regras de autorização são atribuídas a uma faixa percentual à sua escolh
 
 - De 0% a 10% de variação de preço, o pedido será aprovado automaticamente
 
-![regra-1-autorização-de-pedidos PT](https://images.ctfassets.net/alneenqid6w5/1wohOoNoG0OrOU69zBxoPM/ff7ca27e0807785aae26bab5190271fc/regra-1-autoriza____o-de-pedidos_PT.png)
+![regra-1-autorização-de-pedidos PT](//images.ctfassets.net/alneenqid6w5/1wohOoNoG0OrOU69zBxoPM/ff7ca27e0807785aae26bab5190271fc/regra-1-autoriza____o-de-pedidos_PT.png)
 
 - De 10% a 20% de variação de preço, o pedido será enviado para o usuário `usuario@exemplo.com.br` aprovar através de uma tarefa no VTEX DO
 
-![regra2-autorização-de-pedidos PT](https://images.ctfassets.net/alneenqid6w5/XkBsErQYCMnQe4TQefwCL/b7cacd0f633c1768de1cb0b703785479/regra2-autoriza____o-de-pedidos_PT.png)
+![regra2-autorização-de-pedidos PT](//images.ctfassets.net/alneenqid6w5/XkBsErQYCMnQe4TQefwCL/b7cacd0f633c1768de1cb0b703785479/regra2-autoriza____o-de-pedidos_PT.png)
 
 - De 20% a 100% de variação de preço, o pedido será negado automaticamente
 
-![regra3-autorização-de-pedidos pt](https://images.ctfassets.net/alneenqid6w5/2t9asV03OYvCiscGKaws7m/2df3c008d6e802f0ecaf8d48b2b3d751/regra3-autoriza____o-de-pedidos_pt.png)
+![regra3-autorização-de-pedidos pt](//images.ctfassets.net/alneenqid6w5/2t9asV03OYvCiscGKaws7m/2df3c008d6e802f0ecaf8d48b2b3d751/regra3-autoriza____o-de-pedidos_pt.png)
 
 Para a configuração da segunda regra, será necessário o cadastro de usuários com [permissões](https://help.vtex.com/tutorial/como-criar-perfil-de-acesso--tutorials_526) para aprovação de pedidos. 
 
diff --git a/docs/tutorials/pt/how-promotion-competition-works.md b/docs/tutorials/pt/how-promotion-competition-works.md
new file mode 100644
index 000000000..139a7554b
--- /dev/null
+++ b/docs/tutorials/pt/how-promotion-competition-works.md
@@ -0,0 +1,215 @@
+---
+title: 'Como funciona a concorrência de promoções'
+id: tutorials_2270
+status: PUBLISHED
+createdAt: 2017-04-27T21:55:27.997Z
+updatedAt: 2023-11-14T16:52:38.320Z
+publishedAt: 2023-11-14T16:52:38.320Z
+firstPublishedAt: 2017-04-27T23:03:50.791Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 46G4yHIZerH7B9Jo0Iw5KI
+slug: como-funciona-a-concorrencia-de-promocoes
+locale: pt
+legacySlug: entendendo-a-concorrencia-de-promocoes
+subcategory: 1yTYB5p4b6iwMsUg8uieyq
+---
+
+O módulo de Promoções possui uma lógica para definir qual promoção será aplicada em uma compra, assim como o [Checkout](https://help.vtex.com/pt/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) precisa selecionar qual seller irá realizar o fullfilment do pedido. Essa lógica se chama concorrência de promoções.
+
+Os cenários em que acontece concorrência de promoções são:
+
+- Promoções com o mesmo tipo de desconto.
+- Aplicação de mais de uma promoção no mesmo item.
+- Promoções não [configuradas](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restricoes-e-limitacoes-de-uso) para permitir acumular promoções.
+
+Para entender como a seleção da promoção que será aplicada funciona, vamos entender alguns conceitos do módulo de Promoções.
+
+- [Classificação das promoções](#efeitos-de-promocoes)
+- [Ordenação de aplicação das promoções](#ordenacao-de-aplicacao-das-promocoes)
+- [Acumulação de promoções](#acumulacao-de-promocoes)
+- [Estratégias de concorrência de promoções](#estrategias-de-concorrencia-de-promocoes)
+
+## Efeitos de promoções
+
+Os efeitos de promoções são relacionados ao benefício que a promoção oferece. Existem quatro tipos:
+
+- **Desconto no preço**: são as promoções que aplicam um desconto percentual ou nominal sobre o valor do produto. Aqui, estão incluídos alguns descontos da [promoção regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), [desconto progressivo](https://help.vtex.com/pt/tutorial/desconto-progressivo--tutorials_324) e qualquer outra mecânica que incida sobre o preço de um item.
+- **Desconto no frete**: são as [promoções com desconto no frete](https://help.vtex.com/pt/tutorial/configurar-promocoes-de-frete--6Lo5BR61KMiUFAAHGCdgfW).
+- **Brinde**: são as promoções que concedem um brinde ao cliente.
+- **Fórmula**: são as promoções com tipo de desconto nominal baseado em [fórmula](https://help.vtex.com/pt/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV), que é uma das opções da promoção regular.
+
+## Ordenação de aplicação das promoções
+
+A ordenação é o processo que define em que ordem as promoções serão aplicadas no carrinho. Isso é importante para entender qual será o preço final dos itens do carrinho. Essa ordenação é baseada em dois critérios:
+
+- [Ordenação por tipo de promoção e desconto](#ordenacao-por-tipo-de-promocao-e-desconto)
+- [Ordenação por valor](#ordenacao-por-valor)
+
+### Ordenação por tipo de promoção e desconto
+
+As promoções inseridas no carrinho seguem a seguinte disposição:
+
+1. Percentual
+2. Nominal
+3. Preço Máximo
+4. Compre Junto (não é uma promoção regular)
+5. Frete Percentual
+6. Frete Nominal
+7. Brinde
+8. Fórmula
+
+### Ordenação por valor
+
+As promoções de um mesmo tipo inseridas no carrinho são comparadas pelo seu valor de desconto. Nesse momento, o módulo de Promoções procura sempre aplicar a promoção mais vantajosa para o comprador.
+
+Para promoções do tipo brinde, a ordenação se dá pelo maior número de brindes concedidos pela promoção. 
+
+Exemplo:
+
+- Promoção 1: desconto de 30% sobre o valor do produto.
+- Promoção 2: desconto de 50%.
+
+A prioridade é dada àquela promoção que conceder o maior desconto, ou seja, o carrinho irá aplicar a __Promoção 2__ e em seguida a __Promoção 1__.
+
+A **Promoção 1** será aplicada no valor do item já descontado pela **Promoção 2**.
+
+## Acumulação de promoções
+
+Quando as promoções são [configuradas](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restricoes-e-limitacoes-de-uso) no campo `Permitir acumular promoções` para acumularem, elas são sempre aplicadas, independente do tipo, desde que suas condições sejam atendidas. 
+
+Todavia, elas incidem no valor já descontado pela promoção que ganhou a concorrência de promoções não acumulativas. A ordem das promoções selecionadas seguirá a ordenação por tipo e valor, como descrito no item 1. 
+
+Logo, a sequência de aplicação é:
+
+![promocao3 PT](//images.ctfassets.net/alneenqid6w5/1LKDzbLkhua8Gk284SEwsk/997fdac9b6380c68a729bf4d48e20af8/promocao3_PT.png)
+
+<div class="alert alert-warning">
+Pedidos de origem <a href="https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> e Fulfillment não reconhecem acúmulo de promoção, uma vez que o uso de promoções em Marketplaces VTEX ou externos é restrito a alguns tipos específicos.</div>
+
+## Estratégias de concorrência de promoções
+
+Após entender como as promoções são ordenadas e acumuladas, você poderá compreender  como a concorrência de promoções não acumulativas é realizada.
+
+A seleção de cada promoção considera apenas as promoções do mesmo tipo de desconto (conforme descrito em [Efeitos de promoções](#efeitos-de-promocoes)) e que atendam, pelo menos, um produto em comum.
+
+Promoções de tipos diferentes ou de mesmo tipo que atendem a produtos diferentes não concorrem entre si, ou seja, elas automaticamente acumulam.
+
+Veja a seguir as duas estratégias de concorrência de promoções: 
+
+- [Concorrência por cenário](#concorrencia-por-cenario)
+- [Concorrência por item](#concorrencia-por-item)
+
+<div class="alert alert-info">
+Por padrão, todas as contas seguem a estratégia de concorrência por cenário. Caso o modelo de concorrência por item atenda melhor suas necessidades de negócio, <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abra um chamado com nosso time de suporte</a> e solicite a mudança.</div>
+
+### Concorrência por cenário
+
+A concorrência por cenário segue a lógica de agrupar as promoções que não competem com os mesmos produtos. Então, com cada grupo criado, é feita a comparação se o grupo ou alguma promoção individual oferece maior vantagem ao cliente. 
+
+O que conceder o melhor desconto será aplicado ao carrinho. Veja nos exemplos abaixo:
+
+#### Exemplo 1
+
+Pedrinho vai comprar uma camiseta de R$100, com frete de R$30. No pedido, podem ser aplicadas cinco promoções. Todas as promoções aplicáveis foram [configuradas](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#4-restricoes-e-limitacoes-de-uso) no campo `Permitir acumular promoções` para não acumularem promoções, exceto pela primeira:
+
+| Promoções acumulativas | Promoções não acumulativas |
+| ----------- | ----------- |
+| 10% off | Frete máximo de R$ 20 |
+| X | 80% off no frete |
+| X | Desconto nominal de R$50 |
+| X | Brinde ao comprar a camisa |
+
+O carrinho final terá os preços da camisa e do frete respectivamente iguais a R$45 e R$6. O sistema de promoções começa aplicando a lógica de concorrência de promoção:
+
+- Camiseta de **R$100**.
+   - Recebe desconto nominal de *R$50*. Novo valor: **R$50**. 
+
+- Frete de **R$30**.
+   - Recebe desconto de **80%**. Novo valor: **R$6**.
+   - Frete máximo de **R$20** é aplicado, mas não é válido, pois o valor já está abaixo disso.
+
+Em seguida, as promoções acumulativas são aplicadas:
+
+- Camiseta de ~~R$100~~. **R$50**.
+   - Recebe desconto percentual de **10%**. Novo valor: **R$45**.
+
+Assim, a compra final de Pedrinho ficaria: 
+
+- Camiseta por **R$45**.
+- Frete por **R$6**.
+- Brinde ao comprar a camisa.
+
+#### Exemplo 2
+
+Carla montou um carrinho com 1 camiseta e 1 sapato. Esses itens fazem parte de coleções:
+
+| Coleção | Itens | Valores |
+| ----------- | ----------- |  ----------- |
+| 1 | Camiseta | R$ 100 |
+| 1 | Sapato | R$ 500 |
+| 2 | Camiseta | R$ 100 |
+
+- Promoções:
+   1. **10%** na primeira coleção. Configurado para não acumular no campo `Permitir acumular promoções`.
+   2. **25%** na segunda coleção. Configurado para não acumular no campo `Permitir acumular promoções`.
+   3. **5%** no produto. Configurado para acumular no campo `Permitir acumular promoções`. Contempla todos os produtos do carrinho.
+
+Como as duas primeiras promoções são aplicadas no produto Camiseta e não estão marcadas para acumular, elas entram em concorrência. 
+
+Quando as promoções entram em concorrência, o módulo de promoções vai escolher a promoção que fornecerá o melhor desconto para o cliente. Veja abaixo um exemplo de concorrência por cenário.
+
+##### Cenário 1: Aplicando a promoção 1 de 10%
+
+| Itens | Promoções aplicadas | Valores |
+| ----------- | ----------- |  ----------- |
+| Camiseta | Promoção 1 e Promoção 3 | R$ 85,50 |
+| Sapato | Promoção 1 e Promoção 3 | R$ 427,50 |
+
+A camiseta ficaria com o preço de **R$ 85,50** com o desconto da *promoção de 10% e desconto de 5%* no produto. O sapato ficaria com o preço: **R$ 427,50** com *promoção 1 de 10% e o desconto de 5%* no produto.
+
+O valor total do pedido ficaria em **R$513**.
+
+##### Cenário 2: Aplicando a promoção 2 de 25%
+
+| Itens | Promoções aplicadas | Valores |
+| ----------- | ----------- |  ----------- |
+| Camiseta | Promoção 2 e Promoção 3 | R$ 71,25 |
+| Sapato | Promoção 2 e Promoção 3 | R$ 475,00 |
+
+A camiseta ficaria com o preço: **R$ 71,25** com o desconto da *promoção 2 de 25% e desconto de 5%* no produto. O sapato ficaria com o preço: **R$ 475,00**. Apenas aplicando o *desconto de 5%* no produto, pois ele não está na coleção da promoção 2.
+
+Neste cenário, o valor total do pedido ficaria em **R$ 542,50**.
+
+Resumindo, como no cenário 1 o valor final do pedido fica mais barato para o cliente da loja, ele se encaixa na premissa de ofertar o melhor desconto possível. Assim, a VTEX escolhe aplicar a promoção 1 de 10% para ambos os itens. Isso porque as promoções 1 e 2 não poderiam ser aplicadas já que estão marcadas para não acumular.
+
+### Concorrência por item
+
+O módulo de Promoções também pode considerar o maior desconto para o cliente da loja em cada item do carrinho. Para isso, o sistema considera as promoções aplicáveis em um item e seleciona a melhor entre elas, em vez de considerar uma combinação de promoções em nível de carrinho.
+
+Na concorrência por item, o que ocorreria seguindo os dados do exemplo anterior seria:
+
+| Coleção | Itens | Valores |
+| ----------- | ----------- |  ----------- |
+| 1 | Camiseta | R$ 100 |
+| 1 | Sapato | R$ 500 |
+
+- Promoções:
+   1. **10%** na primeira coleção. Configurado para não acumular no campo `Permitir acumular promoções`.
+   2. **25%** na segunda coleção. Configurado para não acumular no campo `Permitir acumular promoções`.
+   3. **5%** no produto. Configurado para acumular no campo `Permitir acumular promoções`. Contempla todos os produtos do carrinho.
+
+Aplicando a promoção, os valores seriam:
+
+| Itens | Promoção aplicada | Valores |
+| ----------- | ----------- |  ----------- |
+| Camiseta | Promoção 2  | R$ 75 |
+| Sapato | Promoção 1 | R$ 475 |
+
+A camiseta ficaria com o preço de **R$ 75,00** com o desconto da *promoção 2 de 25%*. O sapato ficaria com o preço de **R$ 450** com o desconto da *promoção 1 de 10%*.
+
+Neste cenário, o valor total do pedido ficaria em **R$ 525**.
+
+Essa opção ofereceria um desconto menor para o cliente que a seleção feita pela [concorrência por cenário](#concorrencia-por-cenario). Portanto, essa configuração depende do objetivo de negócio definido pela loja. 
+
+Caso o modelo de concorrência por item atenda melhor suas necessidades de negócio, [abra um chamado](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) com nosso time de suporte e solicite a mudança.
diff --git a/docs/tutorials/pt/how-recursive-marketplace-works.md b/docs/tutorials/pt/how-recursive-marketplace-works.md
index 6b5b6847e..1e62093ba 100644
--- a/docs/tutorials/pt/how-recursive-marketplace-works.md
+++ b/docs/tutorials/pt/how-recursive-marketplace-works.md
@@ -33,7 +33,7 @@ Dessa forma:
 
 - __Quando uma loja VTEX for intermediária no fluxo de um pedido__: pedido de cadeia com __Chain Workflow__:
 
-![marketplace-recursivo-chain-order-workflow](https://images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
+![marketplace-recursivo-chain-order-workflow](//images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
 
 
 ## Configuração
diff --git a/docs/tutorials/pt/how-shipping-calculation-works.md b/docs/tutorials/pt/how-shipping-calculation-works.md
index df2ee6ea8..a6600435e 100644
--- a/docs/tutorials/pt/how-shipping-calculation-works.md
+++ b/docs/tutorials/pt/how-shipping-calculation-works.md
@@ -3,8 +3,8 @@ title: 'Como funciona o cálculo de envio'
 id: tutorials_116
 status: PUBLISHED
 createdAt: 2017-04-27T22:18:59.694Z
-updatedAt: 2022-06-21T14:55:49.737Z
-publishedAt: 2022-06-21T14:55:49.737Z
+updatedAt: 2023-07-25T19:55:42.137Z
+publishedAt: 2023-07-25T19:55:42.137Z
 firstPublishedAt: 2017-04-27T23:00:43.230Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -83,8 +83,7 @@ No Admin VTEX, é possível configurar critérios e prioridades diferentes para
 - **Docas:** as prioridades são configuradas nos [campos de cadastro da doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW#campos-de-cadastro).
 - **Frete:** os preços de frete são configurados nas [tarifas de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM), com exceção da [tarifa de doca](https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV), que é um valor adicional opcional, configurado ao adicionar a doca a um estoque.
 - **Prazo:** o tempo para envio é configurado na [estimativa de SLA](#estimativa-de-tempo-de-envio).
-- **Divisão de pacotes:** os critérios adotados são configurados no módulo Checkout, saiba mais em [divisões de pacotes](https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV).
-- **Priorização do inventário:** configurar um critério diferente para priorização do inventário só pode ser feito por API, pela chamada [Create/update warehouse](https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse), ao acrescentar a propriedade `priority`. 
+- **Divisão de pacotes:** os critérios adotados são configurados no módulo Checkout, saiba mais em [divisões de pacotes](https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV). 
 
 ## Estimativa de tempo de envio
 
diff --git a/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md b/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
index c9213d6ce..e637f9516 100644
--- a/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
+++ b/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
@@ -3,8 +3,8 @@ title: 'Como funciona o frete quando a entrega é feita pelo marketplace (FOB)'
 id: EY1l6tYW3IUquwwwcQqwQ
 status: PUBLISHED
 createdAt: 2017-08-28T23:17:57.225Z
-updatedAt: 2021-08-11T17:11:00.299Z
-publishedAt: 2021-08-11T17:11:00.299Z
+updatedAt: 2024-02-05T15:48:24.006Z
+publishedAt: 2024-02-05T15:48:24.006Z
 firstPublishedAt: 2017-08-29T20:09:40.790Z
 contentType: tutorial
 productTeam: Channels
@@ -23,7 +23,8 @@ Esse fluxo evita validações desnecessárias do pedido, simplifica a configura
 
 A regra pela escolha do estoque que irá servir o SKU será feita sempre da seguinte maneira:
 
-1. Maior quantidade disponível do SKU.
+1. Menor quantidade disponível do SKU.
+    > _Para evitar que inventários com pequenas quantidades de itens fiquem represados._
 2. Menor tempo de rota entre estoque e doca.
 3. Menor preço de rota entre estoque e doca.
 
@@ -31,11 +32,11 @@ Caso exista mais de um estoque disponível seguindo estes critérios e prioridad
 
 Caso o pedido tenha várias unidades de um SKU, é necessário que algum dos estoques tenha a quantidade total, ou então o pedido será barrado pela VTEX, que acusará falta de estoque.
 
-## Gerenciamento de Pedidos
+## Pedidos
 
 Como a entrega será feita pelo marketplace, o OMS não trará o valor do frete, já que isso ficou acordado entre o marketplace e o comprador do produto, não trazendo ônus à loja. A informação de prazo que aparece no pedido não é a que o marketplace informou à VTEX, mas sim uma simulação de frete feita no momento de integrar o pedido.
 
-No lugar das identificações de transportadora e tipo de entrega é apresentada a informação `vtex:fob_1111`, sendo que `1111` será correspondente ao ID do estoque em que o SKU foi reservado.
+No lugar das identificações de transportadora e tipo de entrega é apresentada a informação `vtex:fob_1111`, sendo que `1111` será correspondente ao ID da doca.
 
 ## API
 
@@ -43,7 +44,7 @@ Assim como na interface do OMS, a API traz a informação `vtex:fob_1111` para o
 
 É importante que o ERP esteja adequado à recepção dos dados neste formato.
 
-![](https://images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
+![](//images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
 
 ## Etiqueta
 
@@ -51,6 +52,6 @@ O pedido é enviado em um contrato com os Correios do próprio marketplace. Nest
 
 É possível acessar a etiqueta diretamente pelo OMS, abaixo dos itens do pedido. Basta clicar no link e uma nova janela será aberta já com o PDF da etiqueta.
 
-![Etiqueta de entrega pelos Correios (BR) - Marketplace](https://images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/e49eff1715dd0b3018bb58a6521f5c0c/Screen_Shot_2020-03-25_at_11.43.27.png)
+![Etiqueta de entrega pelos Correios (BR) - Marketplace](//images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/e49eff1715dd0b3018bb58a6521f5c0c/Screen_Shot_2020-03-25_at_11.43.27.png)
 
-Caso queria aproveitar a etiqueta dentro do ERP, ela também está disponível na [API de Pedidos](https://developers.vtex.com/reference/orders#getorder), no array `trackingHints` que faz parte do objeto `shippingData`.
+Caso queria aproveitar a etiqueta dentro do ERP, ela também está disponível em [Marketplace Protocol API](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/order-integration/orders), saiba mais em [New Order Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-collect-orders#scenario-12-order-with-tracking-hints).
diff --git a/docs/tutorials/pt/how-subscriptions-work.md b/docs/tutorials/pt/how-subscriptions-work.md
index 7c38c73d9..ac2d38af6 100644
--- a/docs/tutorials/pt/how-subscriptions-work.md
+++ b/docs/tutorials/pt/how-subscriptions-work.md
@@ -3,8 +3,8 @@ title: 'Como funciona a assinatura'
 id: frequentlyAskedQuestions_4453
 status: PUBLISHED
 createdAt: 2019-01-24T20:46:00.886Z
-updatedAt: 2023-02-15T23:42:14.386Z
-publishedAt: 2023-02-15T23:42:14.386Z
+updatedAt: 2024-07-24T17:36:44.989Z
+publishedAt: 2024-07-24T17:36:44.989Z
 firstPublishedAt: 2019-01-24T22:14:56.290Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,13 +17,15 @@ subcategory: 1rA9wuuskW3PpjvMrhatAM
 
 O **Sistema de Assinaturas** é uma aplicação desenvolvida pela VTEX para facilitar as vendas recorrentes. Funciona como um agendador automático, realizando uma recompra na frequência solicitada pelo cliente da loja.
 
-Seu cliente indica a periodicidade que deseja repetir a compra de um determinado item, e o sistema refaz o pedido de compra. Essa compra é feita automaticamente, a cada período agendado, com as mesmas características configuradas no pedido original.
+Seu cliente indica a periodicidade que deseja repetir a compra de um determinado item, e o sistema refaz o pedido de compra. Essa compra é feita automaticamente, a cada período agendado, com as mesmas características configuradas no pedido original. A assinatura é uma forma simples de poupar o tempo de seu cliente, trazendo mais um fluxo programado de vendas para a sua loja. 
 
-A assinatura na VTEX consiste em uma lista de SKUs vinculada a uma certa configuração de compra. Todas as operações de gerenciamento giram em torno dessa entidade Assinatura, que contém toda a informação necessária para gerar um pedido recorrente. O diagrama abaixo demonstra o conceito de assinatura:
+A assinatura na VTEX consiste em uma lista de SKUs vinculada a uma certa configuração de compra. Todas as operações de gerenciamento giram em torno dessa entidade Assinatura, que contém toda a informação necessária para gerar um pedido recorrente, como:
 
-![img8 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/474f3170b2f10977be30172465ffd630/img8_subscriptions_PT.png)
-
-A assinatura é uma forma simples de poupar o tempo de seu cliente, trazendo mais um fluxo programado de vendas para a sua loja. 
+- Perfil de usuário
+- Endereço
+- Forma de pagamento
+- Frequência
+- Data de início do pedido de assinatura
 
 ## Como o cliente da sua loja cria um pedido com assinatura
 
@@ -45,6 +47,10 @@ Para isso, basta entrar na página **Minha Conta** no site da sua loja, acessar
 
 ## Como o cliente da sua loja visualiza suas Assinaturas
 
+<div class = "alert alert-info">
+Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
+</div>
+
 Após a finalização do pedido com Assinatura, o seu cliente visualiza na página **Minha Conta** a seção **Assinaturas**. Nessa seção, ele também pode encontrar a lista de assinaturas realizadas com os detalhes e estado individual. Seu cliente também receberá por e-mail uma confirmação da Assinatura e do pedido gerado.
 
 A comunicação com seu cliente sobre a assinatura será feita pelo módulo **Central de Mensagens**. Confira nosso artigo sobre [Emails Transacionais para Assinaturas](https://help.vtex.com/pt/tutorial/e-mails-transacionais-para-pedidos-de-assinatura--2NYHqHMRqZ43Cn6s84ZCB5). 
@@ -107,3 +113,4 @@ Sim, o preço que o cliente paga na assinatura é baseado no preço cadastrado p
 12. **Qual o horário no qual os pedidos de assinatura são gerados?**
 A criação de pedidos de assinatura ocorre entre 6:00 e 7:00 da manhã, com referência ao fuso horário do Brasil (GMT-3).
 
+13. **A funcionalidade Assinaturas funciona com o Seller Portal?** Não, Assinaturas não funciona com o [Seller Portal](https://help.vtex.com/pt/tutorial/how-to-set-up-your-store-on-seller-portal).
diff --git a/docs/tutorials/pt/how-the-carrefour-integration-works.md b/docs/tutorials/pt/how-the-carrefour-integration-works.md
index b0ca15909..4b2cd9395 100644
--- a/docs/tutorials/pt/how-the-carrefour-integration-works.md
+++ b/docs/tutorials/pt/how-the-carrefour-integration-works.md
@@ -3,8 +3,8 @@ title: 'Como funciona a integração com o Carrefour'
 id: UbtveAQnoQGKOkQIYG0uQ
 status: PUBLISHED
 createdAt: 2018-09-26T13:35:41.191Z
-updatedAt: 2021-07-09T19:05:35.482Z
-publishedAt: 2021-07-09T19:05:35.482Z
+updatedAt: 2023-09-22T20:09:43.231Z
+publishedAt: 2023-09-22T20:09:43.231Z
 firstPublishedAt: 2018-10-11T20:58:12.080Z
 contentType: tutorial
 productTeam: Channels
@@ -45,7 +45,7 @@ Para os produtos serem exibidos no Carrefour, a integração envia os seguintes
 | -       | Especificações       |
 
 _Legenda:_
-`*` Campos obrigatórios.<br />
+`*` Campos obrigatórios.<br /> 
 
 <div class="alert alert-warning">O Carrefour não aceita produtos com variação (mais de um SKU).</div>
 
diff --git a/docs/tutorials/pt/how-the-order-replacement-works.md b/docs/tutorials/pt/how-the-order-replacement-works.md
index 769879386..398962e77 100644
--- a/docs/tutorials/pt/how-the-order-replacement-works.md
+++ b/docs/tutorials/pt/how-the-order-replacement-works.md
@@ -64,7 +64,7 @@ Com essa funcionalidade, os usuários da sua loja ganham uma página de Meus Ped
 
 ![meu pedidos1 PT](//images.contentful.com/alneenqid6w5/3HQW2z7EfmokwYcWWCae8C/f0b0a251aecf8b2e140ad9a1ec2ee3c9/meu_pedidos1_PT.png)
 
-![meus pedidos3 PT](https://images.ctfassets.net/alneenqid6w5/Np1Rhp4HIsQ6ocyOcqG4i/291263f717dd3da2ef8a027b5a1534e6/meus_pedidos3_PT.png)
+![meus pedidos3 PT](//images.ctfassets.net/alneenqid6w5/Np1Rhp4HIsQ6ocyOcqG4i/291263f717dd3da2ef8a027b5a1534e6/meus_pedidos3_PT.png)
 
 Ao selecionar **Alterar pedido**, o cliente é levado para uma tela onde escolhe qual informação gostaria de substituir:
 
diff --git a/docs/tutorials/pt/how-the-seller-portal-catalog-works.md b/docs/tutorials/pt/how-the-seller-portal-catalog-works.md
index a6ce64822..eb8bcd484 100644
--- a/docs/tutorials/pt/how-the-seller-portal-catalog-works.md
+++ b/docs/tutorials/pt/how-the-seller-portal-catalog-works.md
@@ -21,7 +21,7 @@ O Catálogo do Seller Portal é o módulo onde você configura o sortimento de p
 
 A arquitetura do Catálogo do Seller Portal se baseia em alguns conceitos fundamentais distribuídos na seguinte hierarquia:
 
-![ilustra-catalogo](https://images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/95ac8458ebfd20bba03c8669a1e27fdf/ilustra-catalogo.png)
+![ilustra-catalogo](//images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/95ac8458ebfd20bba03c8669a1e27fdf/ilustra-catalogo.png)
 
 - **Categorias:**  formas de organizar os seus produtos. Não é possível adicionar suas próprias Categorias, o marketplace é quem define as categorias disponíveis para enquadrar seus produtos. Cada produto estará obrigatoriamente relacionado a uma categoria já criada pelo marketplace.   
 - **Marcas:**  fazem parte dos atributos que caracterizam os Produtos da sua loja. Desta maneira, seus clientes também podem encontrar o que buscam de forma mais específica. Não é possível adicionar suas próprias marcas, as marcas na aba `Marcas` já foram importadas do marketplace.    
diff --git a/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md b/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md
index f00d960de..605c78c50 100644
--- a/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md
+++ b/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 O app [Carrinho Compartilhável](https://apps.vtex.com/vtex-social-selling/p) permite que vendedores selecionem produtos para seus clientes e compartilhem o carrinho preenchido por canais como WhatsApp, Facebook Messenger e e-mail.
 
-![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artigo explica como instalar o app e configurar a funcionalidade na sua loja. Ao concluir os passos de ativação, seus vendedores poderão seguir as [instruções de uso](https://help.vtex.com/pt/tutorial/como-usar-o-app-carrinho-compartilhavel--3ePPpkmeZ96GXbeIoGZbTN) para iniciar suas estratégias de Social Selling.
 
@@ -83,7 +83,7 @@ Caso você queira customizar as cores dos botões da interface de compartilhamen
 
 Na imagem a seguir, a opção A apresenta as cores originais e a opção B uma customização possível.
 
-![shareable-cart-ui-customization](https://images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
+![shareable-cart-ui-customization](//images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
 
 O código abaixo deve ser adicionado no fim do arquivo `checkout5-custom.css` ou `checkout6-custom.css`, disponível para customização em *Configurações da Loja > Checkout > Código*. A escolha de qual deve ser editado depende da versão do Checkout utilizada pela sua loja.
 
diff --git a/docs/tutorials/pt/how-to-alter-a-banner.md b/docs/tutorials/pt/how-to-alter-a-banner.md
index 49059dbe4..ba79dab1c 100644
--- a/docs/tutorials/pt/how-to-alter-a-banner.md
+++ b/docs/tutorials/pt/how-to-alter-a-banner.md
@@ -22,14 +22,14 @@ Usaremos como exemplo um banner da Home no passo-a-passo. Porém, estas instruç
 3. Clique na pasta **Sites and Channels**.
 4. Clique no nome do website desejado.
 5. Clique na pasta **/**.
-![instrução CMS -pt](https://images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
+![instrução CMS -pt](//images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
 6. Clique no arquivo **Home**.
 7. Clique na aba **Settings**.
 8. Clique no ícone de lápis para editar.
-![cms-home-settings PT](https://images.ctfassets.net/alneenqid6w5/5yEek4apQ4KCoKeSAoCEAY/9d4008ac0a2852da8eaa7fe801d093b1/banner_home_settings_-_pt.png)
+![cms-home-settings PT](//images.ctfassets.net/alneenqid6w5/5yEek4apQ4KCoKeSAoCEAY/9d4008ac0a2852da8eaa7fe801d093b1/banner_home_settings_-_pt.png)
 9. Será aberta a janela de banners.
 10. Clique no ícone de lápis que aparecerá.
-![cms_home_settings_lapis pt](https://images.ctfassets.net/alneenqid6w5/2ab0An97IMUK82aACeS2e4/8ded803db11dfb6e478d4de78749f903/cms_settings_lapis_pt.png)
+![cms_home_settings_lapis pt](//images.ctfassets.net/alneenqid6w5/2ab0An97IMUK82aACeS2e4/8ded803db11dfb6e478d4de78749f903/cms_settings_lapis_pt.png)
 11. Será aberto o formulário de banner.
 
 **Altere o conteúdo do formulário:**
diff --git a/docs/tutorials/pt/how-to-archive-ratestaxes.md b/docs/tutorials/pt/how-to-archive-ratestaxes.md
index ea317d49b..0602769ea 100644
--- a/docs/tutorials/pt/how-to-archive-ratestaxes.md
+++ b/docs/tutorials/pt/how-to-archive-ratestaxes.md
@@ -17,7 +17,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 Caso queira que uma taxa criada não fique na lista principal por não ser mais utilizada, por exemplo, pode movê-la para a lista de arquivadas. Ao fazer isso, a taxa terá o status automaticamente alterado para inativo. Para fazer isso siga os passos abaixo:
 
-![exemplo1](https://images.ctfassets.net/alneenqid6w5/3jvCIvAkHCyocKewGWa0aG/92224b98c19d15e58b734e1332ff6b0f/exemplo1.png)
+![exemplo1](//images.ctfassets.net/alneenqid6w5/3jvCIvAkHCyocKewGWa0aG/92224b98c19d15e58b734e1332ff6b0f/exemplo1.png)
 
 1. No Admin VTEX, acesse *Promoções > Taxas*, ou digite *Taxas* na barra de busca no topo da página.
 3. Busque pela taxa que deseja arquivar.
diff --git a/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
index 58130741e..2fdd1ef35 100644
--- a/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
@@ -21,11 +21,11 @@ Para saber qual o IP de um cliente que realizou um pedido na sua loja, basta ana
 
 Ao abrir um pedido, clique em __"Ver detalhes da transação"__ na caixa de pagamento:
 
-![ip pedido1 PT](https://images.ctfassets.net/alneenqid6w5/6aXWqGSs9OSiaWaG4SYYcI/21acf3d8aa03a1d1133c776b85b76f09/ip_pedido1_PT.png)
+![ip pedido1 PT](//images.ctfassets.net/alneenqid6w5/6aXWqGSs9OSiaWaG4SYYcI/21acf3d8aa03a1d1133c776b85b76f09/ip_pedido1_PT.png)
 
 O IP pode ser visualizado na parte superior direita:
 
-![ip pedido2 PT](https://images.ctfassets.net/alneenqid6w5/5GWGCRtMWIMM0OwW86MeWG/4e4097ce9a8c5acdc388efac9ef38b9c/ip_pedido2_PT.png)
+![ip pedido2 PT](//images.ctfassets.net/alneenqid6w5/5GWGCRtMWIMM0OwW86MeWG/4e4097ce9a8c5acdc388efac9ef38b9c/ip_pedido2_PT.png)
 
 Veja mais detalhes em: [Como visualizar detalhe do pedido](/pt/tutorial/como-visualizar-detalhes-do-pedido)
 
diff --git a/docs/tutorials/pt/how-to-change-orders-beta.md b/docs/tutorials/pt/how-to-change-orders-beta.md
new file mode 100644
index 000000000..1a1267b18
--- /dev/null
+++ b/docs/tutorials/pt/how-to-change-orders-beta.md
@@ -0,0 +1,217 @@
+---
+title: 'Como alterar pedidos (Beta)'
+id: 7btlG91rb6sHpW1dkd2kBw
+status: PUBLISHED
+createdAt: 2023-11-27T22:40:33.769Z
+updatedAt: 2024-04-09T18:03:22.045Z
+publishedAt: 2024-04-09T18:03:22.045Z
+firstPublishedAt: 2023-11-28T15:16:50.272Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: como-alterar-pedidos-beta
+locale: pt
+legacySlug: como-alterar-pedidos-beta
+subcategory: 3LQ1Tl0u4frEOd45BkjFAm
+---
+
+<div class="alert alert-info">
+Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a <b>Alterar pedido (Beta)</b>, entre em contato com <a href="https://help.vtex.com/pt/support">nosso Suporte</a> e informe o(s) <a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> nos quais deseja ativá-la.
+</div>
+
+A funcionalidade [Alterar pedido (beta)](https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ) permite que você edite um pedido de diversas formas, seja a mudança motivada pela vontade do cliente, indisponibilidade de produtos ou outros motivos. 
+
+Este artigo apresenta de quais maneiras o pedido pode ser alterado e como realizar essas ações. As seções apresentadas neste artigo são as seguintes:
+
+- [Requisitos](#requisitos)
+- [Tipos de alteração de pedidos](#tipos-de-alteracao-de-pedidos)
+- [Aspectos comuns](#aspectos-comuns)
+- [Erros de processamento](#erros-de-processamento)
+
+<div class="alert alert-warning">
+Para saber sobre as <a href="https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#caracteristicas-gerais">características gerais</a> em cenários de alteração de pedidos, incluindo reserva, atualização de inventário e contas franquia, ou para entender questões de <a href="https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#mudancas-de-preco">preço, pagamento e fatura</a>, veja o artigo <a href="https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ">Como funciona a Alterar pedido (Beta)</a>.
+</div>
+
+## Requisitos
+
+Existem algumas condições para a alteração de pedidos relacionadas ao status do pedido. Veja os detalhes a seguir.
+
+### Status do pedido a ser alterado
+
+Durante o [fluxo do pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196), o único status no qual a **Alterar pedido (beta)** é válida pelo Admin VTEX é em `preparando entrega`. Para informações sobre alterações por API, veja o artigo [Como funciona a Alterar pedido (Beta)](https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ).
+
+### Permissão no Licence Manager
+
+Para um usuário ser capaz de alterar pedidos, o seu [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) precisa estar associado a pelo menos um dos seguintes [recursos do Licence Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3):
+
+* `Orders Full Access`
+* `Change order`
+
+## Tipos de alteração de pedidos
+
+As principais alterações de pedidos que podem ser realizados pelo Admin VTEX são: 
+
+* **Adicionar:** uma quantidade de itens ou novos produtos.
+* **Remover:** uma quantidade parcial ou total de itens.
+* **Alterar peso:** os itens podem passar a ter um peso maior ou menor.
+* **Substituir itens:** trocar itens por outros, incluindo itens precificados por peso.
+* **Alterar preço:** [mudar valor total do pedido](https://help.vtex.com/pt/tutorial/alterar-valor-total-do-pedido--2asq4BmxvSD8Tw9xpfZuMo).
+
+Todas estas ações são realizadas pela [página de detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) do pedido, que você acessar de duas formas, descritas a seguir.
+
+### Acessar pedido pela página Todos os pedidos
+
+No Admin VTEX, acesse **Pedidos >** [Todos os pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi) e clique no pedido desejado, ou digite **Todos os pedidos** na barra de busca no topo da página. Em seguida, clique no pedido desejado. Se necessário, você pode utilizar [filtros](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192) para refinar sua busca.
+
+### Acessar pedido usando a barra de busca global
+
+A partir de qualquer página do Admin VTEX, pesquise o pedido pela barra de busca no topo da página. Basta selecionar a opção `Pedidos`, no canto direito da barra, e utilizar algum dos seguintes critérios:
+
+* ID do pedido
+* Nome do cliente
+* Email do cliente
+* Documento do cliente 
+
+Uma vez na página de detalhes do pedido, você pode realizar as seguintes alterações:
+
+* [Adicionar itens](#adicionar-itens)
+* [Adicionar novo produto](#adicionar-novo-produto)
+* [Remover itens](#remover-itens)
+* [Excluir produto](#excluir-produto)
+* [Substituir itens](#substituir-itens)
+* [Alterar peso](#alterar-peso)
+
+<div class = "alert alert-info">
+É possível realizar uma única alteração no pedido ou combinar várias de uma só vez. Não existe um limite para quantas vezes um pedido pode ser alterado. Para mais informações, veja o artigo <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Como funciona a Alterar pedido (Beta)</a>.
+</div>
+
+### Adicionar itens
+
+Para adicionar um ou mais itens ao pedido, realize os seguintes passos:
+
+1. No Admin VTEX, acesse a página de detalhes do pedido em **Pedidos >** [Todos os pedidos](#acessar-pedido-pela-pagina-todos-os-pedidos) ou pela [barra de busca global](#acessar-pedido-usando-a-barra-de-busca-global).
+2. Na seção **A faturar**, clique em `Alterar itens`.
+3. Na página **Gerenciar itens do pedido**, clique na seta para cima <i class="fas fa-angle-up"></i> até o número da quantidade desejada, ou digite o número no campo. Feito isso, a página vai apresentar o preço e o número da quantidade anteriores tachados e vai aparecer a seguinte mensagem: _“Item editado”_.
+
+    ![change_order_adding_items_PT](//images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/ac1af94d506fdcd6be258f23cb51bd75/change_order_adding_items_PT.png)
+
+4. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
+5. Clique em `Revisar e aplicar`.
+6. No campo **Motivo das alterações**, escreva de forma breve o motivo pelo qual o pedido está sendo alterado. Se desejar, revise novamente as alterações a serem feitas.
+7. Clique em `Aplicar`. A seguinte mensagem de confirmação vai aparecer: _“Solicitação de alteração concluída”._
+
+Feito isso, você retorna à página de detalhes do pedido e, na seção **A faturar**, consegue ver a nova quantidade de itens.
+
+### Adicionar novo produto
+
+Para adicionar um ou mais produtos a um pedido, realize os seguintes passos:
+
+1. No Admin VTEX, acesse a página de detalhes do pedido em **Pedidos >** [Todos os pedidos](#acessar-pedido-pela-pagina-todos-os-pedidos) ou pela [barra de busca global](#acessar-pedido-usando-a-barra-de-busca-global).
+2. Na seção **A faturar**, clique em `Alterar itens`.
+3. Na página **Gerenciar itens do pedido**, clique em <i class="fas fa-plus"></i> `Adicionar item`.
+4. Na página **Adicionar itens**, na <i class="fas fa-search"></i> barra de busca, digite o nome do produto desejado.
+5. Clique em <i class="fas fa-plus"></i> `Selecionar`. Você pode adicionar quantos produtos quiser, basta repetir o procedimento. A cada nova adição, a seguinte mensagem aparece: _“Item selecionado”_.
+  > Se você clicar sobre o nome do produto, você será redirecionado para a página do produto no site da loja.
+6. A seguir, clique em `Adicionar itens selecionados`. A seguinte mensagem vai aparecer: _“Itens adicionados”_.
+
+    ![change_order_adding_product_PT](//images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/1107b86fb89f9e1a76268693807bf4db/change_order_adding_product_PT.png)
+
+7. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
+8. Clique em `Revisar e aplicar`.
+9. No campo **Motivo das alterações**, escreva de forma breve o motivo pelo qual o pedido está sendo alterado. Se desejar, revise novamente as alterações a serem feitas.
+10. Clique em `Aplicar`. A seguinte mensagem de confirmação vai aparecer: _“Solicitação de alteração concluída”._
+
+Feito isso, você retorna à página de detalhes do pedido e, na seção **A faturar,** consegue ver cada novo produto adicionado.
+
+### Remover itens
+
+Para remover um ou mais itens de um pedido, realize os seguintes passos:
+
+1. No Admin VTEX, acesse a página de detalhes do pedido em **Pedidos >** [Todos os pedidos](#acessar-pedido-pela-pagina-todos-os-pedidos) ou pela [barra de busca global](#acessar-pedido-usando-a-barra-de-busca-global).
+2. Na seção **A faturar**, clique em `Alterar itens`.
+3. Na página **Gerenciar itens do pedido**, clique na seta para baixo <i class="fas fa-angle-down"></i> até o número da quantidade desejada, ou digite o número no campo. Feito isso, a página apresenta o preço e o número da quantidade anteriores tachados e aparece a mensagem _“Item editado”_.
+
+    ![change_order_removing_items_PT](//images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/1ce6cbceb54dc71fe5da0bd37b2cd848/change_order_removing_items_PT.png)
+
+4. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
+5. A seguir, clique em `Revisar e aplicar`.
+6. No campo **Motivo das alterações**, escreva de forma breve o motivo pelo qual o pedido está sendo alterado. Se desejar, revise novamente as alterações a serem feitas.
+7. Clique em `Aplicar`. A seguinte mensagem de confirmação vai aparecer: _“Solicitação de alteração concluída”._
+
+Feito isso, você retorna à página de detalhes do pedido e, na seção **A faturar,** consegue ver a nova quantidade de itens após a remoção.
+
+### Excluir produto
+
+Para excluir um produto de um pedido, realize os seguintes passos:
+
+1. No Admin VTEX, acesse a página de detalhes do pedido em **Pedidos >** [Todos os pedidos](#acessar-pedido-pela-pagina-todos-os-pedidos) ou pela [barra de busca global](#acessar-pedido-usando-a-barra-de-busca-global).
+2. Na seção **A faturar**, clique em `Alterar itens`.
+3. Na página **Gerenciar itens do pedido**, clique no ícone lixeira <i class="far fa-trash-alt"></i> `Remover item`. A seguinte mensagem de confirmação vai aparecer: _“Item removido”._
+
+    ![change_order_removing_product_PT](//images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/9130a233b2492ba003f4a93415bf16e1/change_order_removing_product_PT.png)
+
+4. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [everter uma alteração](#reverter-acoes).
+5. A seguir, clique em `Revisar e aplicar`.
+6. No campo **Motivo das alterações**, escreva de forma breve o motivo pelo qual o pedido está sendo alterado. Se desejar, revise novamente as alterações a serem feitas.
+7. Clique em `Aplicar`. A seguinte mensagem de confirmação vai aparecer: _“Solicitação de alteração concluída”._
+
+Feito isso, você retorna à página de detalhes do pedido e, na seção **A faturar,** consegue ver o pedido sem o produto que foi excluído.
+
+### Substituir itens
+
+Para substituir itens do pedido, realize os seguintes passos:
+
+1. No Admin VTEX, acesse a página de detalhes do pedido em **Pedidos >** [Todos os pedidos](#acessar-pedido-pela-pagina-todos-os-pedidos) ou pela [barra de busca global](#acessar-pedido-usando-a-barra-de-busca-global).
+2. Na seção **A faturar**, clique em `Alterar itens`.
+3. Na página **Gerenciar itens do pedido**, na linha do produto que deseja substituir, clique no menu <i class="fas fa-ellipsis-v"></i> e selecione <i class="fas fa-pencil-alt"></i> `Substituir item`.
+4. Na página **Substituição de produtos**, na <i class="fas fa-search"></i> barra de busca, digite o nome do produto que vai substituir o anterior.
+5. Clique em <i class="fas fa-plus"></i> `Selecionar`. A seguinte mensagem vai aparecer: _“Item selecionado”_. Se você clicar sobre o nome do produto, você será redirecionado para a página do produto no site da loja.
+6. A seguir, clique em `Aplicar`. A seguinte mensagem vai aparecer: _“Alterações aplicadas”_.
+7. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
+8. Clique em `Revisar e aplicar`.
+9. No campo **Motivo das alterações**, escreva de forma breve o motivo pelo qual o pedido está sendo alterado. Se desejar, revise novamente as alterações a serem feitas.
+10. Clique em `Aplicar`. A seguinte mensagem de confirmação vai aparecer: _“Solicitação de alteração concluída”_.
+
+Feito isso, você retorna à página de detalhes do pedido e, na seção **A faturar**, consegue ver o item que substituiu o anterior.
+
+### Alterar peso
+
+Para alterar o peso de um item, realize os seguintes passos:
+
+1. No Admin VTEX, acesse a página de detalhes do pedido em **Pedidos >** [Todos os pedidos](#acessar-pedido-pela-pagina-todos-os-pedidos) ou pela [barra de busca global](#acessar-pedido-usando-a-barra-de-busca-global).
+2. Na seção **A faturar**, clique em `Alterar itens`.
+3. Na página **Gerenciar itens do pedido**, na linha do produto desejado, digite o novo número do peso no campo. A unidade de medida vai estar especificada de acordo com as configurações no Catálogo. 
+4. Feito isso, a página apresenta o preço e o peso anteriores tachados e a mensagem _“Item editado”_.
+
+    ![change_order_changing_weight_PT](//images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/a34686dc7fa270893387038e3472595e/change_order_changing_weight_PT.png)
+
+5. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
+6. Clique em `Revisar e aplicar`.
+7. No campo **Motivo das alterações**, escreva de forma breve o motivo pelo qual o pedido está sendo alterado. Se desejar, revise novamente as alterações a serem feitas.
+8. Clique em `Aplicar`. A seguinte mensagem de confirmação vai aparecer: _“Solicitação de alteração concluída”_.
+
+Feito isso, você retorna à página de detalhes do pedido e, na seção **A faturar**, consegue ver o peso do item atualizado.
+
+## Aspectos comuns
+
+Quando você está realizando algum [tipo de alteração](#tipos-de-alteracao-de-pedidos) do pedido, existem ações comuns e elas foram reunidas nesta seção.
+
+### Consultar detalhes dos valores da alteração
+
+Na página **Gerenciar itens do pedido**, enquanto você altera o pedido, o valor total vai sendo automaticamente atualizado em **Valor total**, no canto inferior da página. Além disso, é possível ver a variação de preço resultante de cada operação sendo realizada. Para ver detalhes dos valores, clique na seta <i class="fas fa-angle-up"></i> ao lado do preço total.
+
+### Reverter ações
+
+Na página **Gerenciar itens do pedido**, se você se arrepender de alguma alteração realizada, é possível desfazê-la. Para isso, clique no ícone seta curva `Desfazer ação`. Feito isso, uma mensagem de confirmação vai aparecer: _“Alteração desfeita”_, e a ação terá sido revertida.
+
+![change_order_undoing_actions_PT](//images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/049029b660f8db15b1846d3098a34ea6/change_order_undoing_actions_PT.png)
+
+## Erros de processamento
+
+Em qualquer tipo de [alteração de pedido](#tipos-de-alteracao-de-pedidos), na página **Gerenciar itens do pedido**, ao clicar em `Revisar e aplicar`, pode ser que a alteração não seja aprovada, o que te faz ser redirecionado de volta para a página de detalhes do pedido. Alguns dos motivos para alterações serem negadas são:
+
+* **Item indisponível:** o SKU pode [não aparecer no site da loja](https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382) ou estar indisponível devido a erro ou falta de configurações de catálogo, preço ou logística. 
+* **Inventário insuficiente:** a quantidade de itens adicionados ou substituídos na alteração pode ser maior do que a quantidade de itens disponíveis para venda no seu [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+
+Se as configurações de **Catálogo** e inventário estiverem corretas e ainda assim as tentativas de alteração de pedidos resultarem em erro, pode ser um problema de processamento da plataforma. Neste caso, recomendamos entrar em contato com [nosso suporte](https://support.vtex.com/hc/pt-br/requests).
+
diff --git a/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md b/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md
index aac2fd87b..c7f10f158 100644
--- a/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md
+++ b/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md
@@ -3,8 +3,8 @@ title: 'Modificar a ordem de meios de pagamento no checkout'
 id: frequentlyAskedQuestions_490
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:54.205Z
-updatedAt: 2022-04-25T15:09:37.985Z
-publishedAt: 2022-04-25T15:09:37.985Z
+updatedAt: 2023-10-31T17:27:08.660Z
+publishedAt: 2023-10-31T17:27:08.660Z
 firstPublishedAt: 2019-01-24T22:12:00.925Z
 contentType: tutorial
 productTeam: Shopping
diff --git a/docs/tutorials/pt/how-to-check-your-balance.md b/docs/tutorials/pt/how-to-check-your-balance.md
index e5847558f..96ef0a6bb 100644
--- a/docs/tutorials/pt/how-to-check-your-balance.md
+++ b/docs/tutorials/pt/how-to-check-your-balance.md
@@ -28,7 +28,7 @@ Para conferir o saldo da sua conta, siga o passo a passo:
 - Clique em __Resumo da Conta__;
 - Do lado esquerdo da tela, encontre o box de __Saldo__.
 
-![saldodisponivelPT](https://images.ctfassets.net/alneenqid6w5/wP9JUmFgAaH3svDApS1hi/0da1d892f79292d1c9fce55bfbc9c2f5/image.png)
+![saldodisponivelPT](//images.ctfassets.net/alneenqid6w5/wP9JUmFgAaH3svDApS1hi/0da1d892f79292d1c9fce55bfbc9c2f5/image.png)
 
 A box apresenta dois valores. O primeiro, __Disponível__, apresenta o saldo em conta livre para movimentações. Já o segundo, __Saldo a receber__, consta o soma dos futuros pagamentos que serão lançados na conta digital corporativa. 
 
diff --git a/docs/tutorials/pt/how-to-configure-a-bank-slip.md b/docs/tutorials/pt/how-to-configure-a-bank-slip.md
index 245e6cb68..f4c2d66d8 100644
--- a/docs/tutorials/pt/how-to-configure-a-bank-slip.md
+++ b/docs/tutorials/pt/how-to-configure-a-bank-slip.md
@@ -3,8 +3,8 @@ title: 'Configurar boleto bancário'
 id: tutorials_447
 status: PUBLISHED
 createdAt: 2017-04-27T22:04:55.249Z
-updatedAt: 2023-03-21T20:14:57.262Z
-publishedAt: 2023-03-21T20:14:57.262Z
+updatedAt: 2024-04-16T14:44:36.023Z
+publishedAt: 2024-04-16T14:44:36.023Z
 firstPublishedAt: 2017-04-27T23:03:25.766Z
 contentType: tutorial
 productTeam: Financial
@@ -15,43 +15,22 @@ legacySlug: como-configurar-boleto-bancario
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-O boleto bancário é um forma de pagamento em que é necessário ter uma conta bancária e contratar uma carteira de cobrança junto ao banco. 
+Na VTEX, é possível suas loja pode realizar vendar por meio do [Boleto Bancário](https://help.vtex.com/pt/tutorial/boleto-bancario-registrado-fluxo-basico-de-um-pagamento--1WlPkeueWQiykUwW8mcM4S). Para configurar o Boleto bancário, siga os passos abaixo:
 
-A partir daí, já é possível emitir boletos e receber diretamente em sua conta.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite na barra de busca o nome do provedor o qual irá processar o boleto bancário.
+4.  Preencha os campos do formulário de acordo com os dados informados pelo provedor/banco.
+5.  Clique em `Salvar`.
 
-Existem duas maneiras de configurar o boleto:
-- Diretamente na VTEX, sem um gateway de pagamento externo
-- Através de um gateway de pagamento, como PagSeguro.
+## Configurar condição de pagamento
 
-As duas formas de configuração estão descritas abaixo.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Em __Boleto__, selecione a opção __Boleto Bancário__.
+4. Ative a condição no campo __Status__.
+5. Em __Processar com o provedor__, selecione o provedor configurado anteriormente.
+6. Se desejar, você também pode [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+7. Clique em `Salvar`.
 
-## Como configurar sem gateway de pagamento externo
-
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Acesse a aba **Afiliações de Gateways**.
-3. Clique em **+**.
-4. Selecione uma das opções em **Boleto Bancário**.
-5. Preencha os campos do formulário de acordo com os dados informados pelo seu banco - para cada banco são necessárias informações diferentes. Por isso, sempre confirme com o banco quais são as informações obrigatórias.
-6. Clique em **Salvar**.
-
-## Como configurar com gateway de pagamento externo
-
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Acesse a aba **Afiliações de Gateways**.
-3. Clique em **+**.
-4. Selecione uma das opções em **Outros** (para a configuração por PagSeguro, selecione a opção PagSeguro sem redirect).
-5. Preencha os campos do formulário de acordo com os dados informados pelo seu gateway de pagamento - para cada gateway são necessárias informações diferentes. Por isso, sempre confirme com o gateway de pagamento quais são as informações obrigatórias.
-6. Clique em **Salvar**.
-
-Após as configurações de Afiliação de Gateway, tanto para gateway externo quanto para a configuração direta do boleto bancário, é preciso configurar  a condição de pagamento.
-
-## Como configurar a condição de pagamento
-
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Acesse a aba **Condições de Pagamento**.
-3. Clique no símbolo **+**.
-4. Em **Boleto**, selecione a opção **Boleto Bancário**.
-5. Preencha o nome, selecione a afiliação de gateway configurada acima e verifique se gostaria de usar a configuração por [condição especial](/pt/tutorial/condicoes-especiais/).
-6. Clique no botão **Salvar**.
-
-Após essa última configuração, a forma de pagamento já estará disponível no checkout da loja.
+Depois de seguir os passos indicados, o Boleto Bancário pode demorar até 10 minutos para aparecer no checkout da sua loja como opção de pagamento.
diff --git a/docs/tutorials/pt/how-to-configure-a-custom-payment.md b/docs/tutorials/pt/how-to-configure-a-custom-payment.md
index 1d0bfe15b..5fadb0f43 100644
--- a/docs/tutorials/pt/how-to-configure-a-custom-payment.md
+++ b/docs/tutorials/pt/how-to-configure-a-custom-payment.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento customizado'
 id: tutorials_451
 status: PUBLISHED
 createdAt: 2017-04-27T22:04:32.144Z
-updatedAt: 2021-07-08T19:02:18.536Z
-publishedAt: 2021-07-08T19:02:18.536Z
+updatedAt: 2023-10-18T14:42:25.244Z
+publishedAt: 2023-10-18T14:42:25.244Z
 firstPublishedAt: 2017-04-27T23:03:25.828Z
 contentType: tutorial
 productTeam: Financial
@@ -20,15 +20,15 @@ O meio de pagamento customizado é uma alternativa às opções oferecidas por p
 Esses meios de pagamento são separados em três categorias. Cada categoria permite cinco configurações.
 
 ## Promissórias
-Promissória é uma promessa de pagamento que precisa de aprovação manual do lojista para aprovar a transação. É frequentemente usada para disponibilizar o pagamento através de dinheiro. Para configurar Promissórias, acesse a documentação [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ?&utm_source=autocomplete).
+Promissória é uma promessa de pagamento que precisa de aprovação manual do lojista para aprovar a transação. É frequentemente usada para disponibilizar o pagamento através de dinheiro. Para configurar Promissórias, acesse a documentação [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria).
 
 ## Cartões da Loja (Bandeira Própria)
-Permite que utilize um cartão de crédito com bandeira própria da Loja. Para configurar esta forma de pagamento, acesse a documentação [Configurar pagamentos com Cartões de Loja (bandeira própria)](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4?&utm_source=autocomplete).
+Permite que utilize um cartão de crédito com bandeira própria da Loja. Para configurar esta forma de pagamento, acesse a documentação [Configurar pagamentos com Cartões de Loja (bandeira própria)](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria).
 
 ## Cartões da Loja (Co-Branded)
-Permite que você utilize um cartão de crédito da Loja com uma das seguintes bandeiras: Mastercard, Visa, Amex e Diners. Para configurar esta forma de pagamento, acesse a documentação [Configurar pagamentos com Cartões de Loja (co-branded)](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-cobranded--jrkLK41IjuquUmyKUi86Q?&utm_source=autocomplete).
+Permite que você utilize um cartão de crédito da Loja com uma das seguintes bandeiras: Mastercard, Visa, Amex e Diners. Para configurar esta forma de pagamento, acesse a documentação [Configurar pagamentos com Cartões de Loja (co-branded)](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-cobranded--jrkLK41IjuquUmyKUi86Q).
 
-Após essa configuração, será necessária a criação da [Condição de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455).
+Após essa configuração, será necessária a criação da [Condição de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
 <div class="alert alert-warning">
 Recomendamos o uso da aprovação automática apenas em casos em que o pagamento será realizado no momento da entrega ou da retirada na loja. Essa opção autoriza o pagamento do pedido, ou seja, o pedido passa automaticamente para o status de Preparando Entrega, sem a verificação do pagamento.
diff --git a/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index 05455d4fa..fe34c8015 100644
--- a/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -30,7 +30,7 @@ Já em operações B2B, há necessidade de se manter relações com os comprador
 2. Na aba __Gerais__, preencha o valor desejado no campo __Valor mínimo total do carrinho__.
 3. Clique em `Salvar`.
 
-![Minimum Order Value - PT](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/4b4ff920a4c1a9a98ad3450e00f47d6c/Minimum_Order_Value_-_PT.png)
+![Minimum Order Value - PT](//images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/4b4ff920a4c1a9a98ad3450e00f47d6c/Minimum_Order_Value_-_PT.png)
 
 <div class="alert alert-warning">
 Ao cliente é permitido montar um carrinho com um valor menor que o especificado na regra de "Valor mínimo total do carrinho". Entretanto, no momento de fechamento da compra, só serão concluídos os pedidos que estiverem com o valor igual ou acima do especificado.
@@ -42,7 +42,7 @@ Ao cliente é permitido montar um carrinho com um valor menor que o especificado
 2. Na aba __Gerais__, preencha o valor desejado no campo __Quantidade máxima de um mesmo SKU no Carrinho__.
 3. Clique em `Salvar`.
 
-![Quantidade Maxima de um mesmo SKU no carrinho](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/bb659e068dfde3a2e4d05480422a7113/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_PT.png)
+![Quantidade Maxima de um mesmo SKU no carrinho](//images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/bb659e068dfde3a2e4d05480422a7113/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_PT.png)
 
 <div class="alert alert-warning">
 Não existem limites para a quantidade máxima de itens do <b>mesmo SKU</b> por carrinho. A única restrição é referente a quantidade máxima de itens de <b>SKUs diferentes</b>, que devem ser no máximo de 300 itens por carrinho. 
diff --git a/docs/tutorials/pt/how-to-configure-payment-conditions.md b/docs/tutorials/pt/how-to-configure-payment-conditions.md
index 7f59b192a..2923b2d9c 100644
--- a/docs/tutorials/pt/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/pt/how-to-configure-payment-conditions.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar condições de pagamento'
 id: tutorials_455
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-04-27T22:04:07.105Z
-updatedAt: 2023-03-21T21:01:23.792Z
-publishedAt: 2023-03-21T21:01:12.557Z
+updatedAt: 2023-10-18T17:17:55.702Z
+publishedAt: 2023-10-18T17:17:55.702Z
 firstPublishedAt: 2017-04-27T23:03:26.687Z
 contentType: tutorial
 productTeam: Financial
@@ -38,7 +38,7 @@ Nas etapas abaixo, iremos utilizar o cartão de crédito como exemplo de condiç
 
 ### À vista
 
-![pagamento-a-vista pt](https://images.ctfassets.net/alneenqid6w5/16U7FyAeXiC88gWCwkKmSU/b07c00338cbbf59430ec4e5a322e0159/pagamento-a-vista.png)
+![pagamento-a-vista pt](//images.ctfassets.net/alneenqid6w5/16U7FyAeXiC88gWCwkKmSU/b07c00338cbbf59430ec4e5a322e0159/pagamento-a-vista.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __+__.
@@ -56,7 +56,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 
 ### Parcelado sem juros
 
-![parcelamento-sem-juros pt](https://images.ctfassets.net/alneenqid6w5/5UuCXeD07moeaQiqqmuCMe/05b2cdeeac157859c9ffadce866eaebf/parcelamento-sem-juros.png)
+![parcelamento-sem-juros pt](//images.ctfassets.net/alneenqid6w5/5UuCXeD07moeaQiqqmuCMe/05b2cdeeac157859c9ffadce866eaebf/parcelamento-sem-juros.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __+__.
@@ -73,7 +73,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 
 ### Parcelado com juros
 
-![parcelamento-com-juros pt](https://images.ctfassets.net/alneenqid6w5/46wBJ8tCUgCaWmAyOgkycY/cada24446ff801ebffdcf02c5aa4b0e7/parcelamento-com-juros.png)
+![parcelamento-com-juros pt](//images.ctfassets.net/alneenqid6w5/46wBJ8tCUgCaWmAyOgkycY/cada24446ff801ebffdcf02c5aa4b0e7/parcelamento-com-juros.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __+__.
@@ -91,7 +91,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 14. Para escolher entre juros compostos e juros simples, clique em __Juros compostos aplicados. Alterar__. Uma caixa de seleção vai aparecer oferecendo as duas opções.
 15. Clique em __Salvar__.
 
-![Juros - pt](https://images.ctfassets.net/alneenqid6w5/6LByLxJORIELFs7gTY3kmA/ce12cf0d03887377566de5eeadd0ed98/Juros_-_pt.png)
+![Juros - pt](//images.ctfassets.net/alneenqid6w5/6LByLxJORIELFs7gTY3kmA/ce12cf0d03887377566de5eeadd0ed98/Juros_-_pt.png)
 
 #### Juros Externos
 
@@ -107,5 +107,5 @@ Atenção: a funcionalidade de juros externos é válida apenas para algumas afi
 2. Na aba __Condições de Pagamentos__, clique sobre a condição de pagamento que deseja remover.
 3. Clique sobre o ícone de lixeira.
 
-![Remover condição de pagamento](https://images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/9486e6e1036228c2ad8dfa7d0685768e/remover_condi____o_pagamento.png)
+![Remover condição de pagamento](//images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/9486e6e1036228c2ad8dfa7d0685768e/remover_condi____o_pagamento.png)
 
diff --git a/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md b/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
index 0d1920157..206661231 100644
--- a/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
@@ -46,10 +46,10 @@ Estes controles, diferentes dos demais, necessitam de uma configuração impresc
 
 No cadastro de Categoria existe a opção de configurar a Avaliação, e normalmente esta configuração é feita na categoria raiz:
 
-![avaliação-categoria PT](https://images.ctfassets.net/alneenqid6w5/TtskX9FjmSS0C0UMAeIcM/36a5e64b42da3a23766d7256ade0d8c9/avalia____o_pt.png)
+![avaliação-categoria PT](//images.ctfassets.net/alneenqid6w5/TtskX9FjmSS0C0UMAeIcM/36a5e64b42da3a23766d7256ade0d8c9/avalia____o_pt.png)
 
 Clique em **Nova Avaliação** e preencha os dados Nome e Texto e depois salve.
 
-![nova-avaliação-categorias PT](https://images.ctfassets.net/alneenqid6w5/6ASmMpGULegqwGKYSm8MSW/10966c7137236f5e9b7d74feb266789c/Nova_avalia____o.png)
+![nova-avaliação-categorias PT](//images.ctfassets.net/alneenqid6w5/6ASmMpGULegqwGKYSm8MSW/10966c7137236f5e9b7d74feb266789c/Nova_avalia____o.png)
 
 Pronto seus controles de Resenha e Avaliação estão prontos para serem utilizados.
diff --git a/docs/tutorials/pt/how-to-configure-subscriptions.md b/docs/tutorials/pt/how-to-configure-subscriptions.md
index fd908c15f..a90a69be2 100644
--- a/docs/tutorials/pt/how-to-configure-subscriptions.md
+++ b/docs/tutorials/pt/how-to-configure-subscriptions.md
@@ -3,8 +3,8 @@ title: 'Como configurar Assinaturas na sua loja'
 id: 1FA9dfE7vJqxBna9Nft5Sj
 status: PUBLISHED
 createdAt: 2019-01-31T16:00:03.228Z
-updatedAt: 2023-04-11T00:33:27.310Z
-publishedAt: 2023-04-11T00:33:27.310Z
+updatedAt: 2024-07-09T14:27:30.778Z
+publishedAt: 2024-07-09T14:27:30.778Z
 firstPublishedAt: 2019-01-31T16:01:57.927Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -67,7 +67,7 @@ Atualmente, os seguintes meios de pagamento estão habilitados para pedidos de a
   <p>Para disponibilizar a opção de pagamento <strong>Cartão de Crédito</strong>, entre em contato com o adquirente da sua loja e certifique-se que ele aceita transações de compras recorrentes oriundas de cartões tokenizados (sem CVV). O sistema de <strong>Assinaturas</strong> utilizará os mesmos dados do cartão da primeira compra para realizar os pedidos seguintes da assinatura, garantindo a segurança de todo o processo.</p>
 </div>
 
-Para habilitar esse tipo de transação no conector, o gestor da loja deverá solicitar ao adquirente a liberação para transacionar pagamentos recorrentes. Confira o nosso artigo sobre [como configurar um gateway de pagamento na sua loja](https://help.vtex.com/pt/tutorial/pci-gateway-visao-geral/).
+Para habilitar esse tipo de transação no conector, o gestor da loja deverá solicitar ao adquirente a liberação para transacionar pagamentos recorrentes. Confira o nosso artigo sobre [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
 
 ## 3. Criar um plano de assinatura
 
@@ -94,11 +94,11 @@ Veja a tabela abaixo para saber quais são os recursos relacionados ao módulo d
 
 Para configurar os Perfis de acesso de Assinatura, siga as instruções abaixo.
 
-1. No módulo **Configurações da Conta**, acesse a aba **Perfis de Acesso**.
-2. Clique no botão `Novo Perfil`.  
-3. Preencha o **Nome do Perfil**.
-4. Em **Produtos e Recursos** selecione **OMS**.
-5. Marque as caixas dos **recursos de Assinatura** que deseja adicionar.
+1. No módulo **Configurações da conta**, acesse **Perfis de acesso**.
+2. Clique no botão `Novo perfil`.  
+3. Preencha o **Nome do perfil**.
+4. Em **Produtos e recursos** selecione `Subscriptions`.
+5. Marque as caixas dos recursos que deseja adicionar.
 6. Clique em `Salvar`. 
 
 Agora que as Assinaturas já estão configuradas em sua loja, acesse nosso artigo para conferir como [gerenciar assinaturas](https://help.vtex.com/pt/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x).
diff --git a/docs/tutorials/pt/how-to-configure-the-anti-fraud.md b/docs/tutorials/pt/how-to-configure-the-anti-fraud.md
index 267f8f1b4..bcd2660d5 100644
--- a/docs/tutorials/pt/how-to-configure-the-anti-fraud.md
+++ b/docs/tutorials/pt/how-to-configure-the-anti-fraud.md
@@ -3,8 +3,8 @@ title: 'Configurar o antifraude'
 id: tutorials_446
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:02.912Z
-updatedAt: 2023-03-29T00:57:28.767Z
-publishedAt: 2023-03-29T00:57:28.767Z
+updatedAt: 2024-03-13T12:04:32.047Z
+publishedAt: 2024-03-13T12:04:32.047Z
 firstPublishedAt: 2017-04-27T23:03:25.730Z
 contentType: tutorial
 productTeam: Financial
@@ -15,22 +15,24 @@ legacySlug: como-configurar-antifraude
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Antifraude é um sistema externo que identifica fraudes e dá mais segurança para as compras realizadas. Na VTEX, você pode escolher algumas opções de antifraude para usar em sua loja. E configurá-las é bem fácil.
+Antifraude é um sistema externo que identifica fraudes e permite aumentar a segurança em transações de pagamento realizadas em compras online. Na VTEX, você pode escolher algumas opções de provedores de antifraude para usar em sua loja. 
 
-## Como configurar
+Para configurar um provedor de antifraude, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Acesse a aba **Afiliações de Gateways**.
-3. Clique em **+**.
-4. Clique sobre o antifraude que deseja configurar.
-5. Preencha os campos do formulário com os dados indicados pelo antifraude (EntityCode).
-6. Clique no botão **Salvar**.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o provedor de antifraude desejado na barra de busca e clique sobre o seu nome.
+4. Preencha os campos do formulário com os dados indicados pelo provedor de antifraude.
+5. Clique em `Salvar`.
 
-Após a configuração em Afiliação de Gateways, é preciso entrar nas condições de pagamento e associar o antifraude em cada um deles.
+Após habilitar o provedor de antifraude, você precisa associá-lo a uma ou mais condições de pagamento. Para realizar esta operação, siga os passos abaixo:
 
-1. Acesse a aba **Condições de Pagamento**.
-2. Clique sobre a condição desejada ou [crie a condição de pagamento](/pt/tutorial/condicoes-de-pagamento).
-3. Selecione a opção **Usar antifraude**.
-4. Selecione qual antifraude deseja utilizar.
-5. Clique no botão **Salvar**.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre o meio de pagamento desejado.
+4. Preencha o campo __Nome da condição__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Em __Processar com o provedor__ selecione o provedor de pagamento desejado.
+7. Em __Usar solução antifraude__, selecione o provedor de antifraude habilitado anteriormente, caso o mesmo esteja disponível para utilização neste meio de pagamento.
+8. Clique em `Salvar`.
 
diff --git a/docs/tutorials/pt/how-to-configure-the-pagseguro-without-redirect-option-transparent.md b/docs/tutorials/pt/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
index d7b058888..4ca01285e 100644
--- a/docs/tutorials/pt/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
+++ b/docs/tutorials/pt/how-to-configure-the-pagseguro-without-redirect-option-transparent.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar o PagSeguro sem redirect (transparente)'
 id: tutorials_449
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T22:04:37.656Z
-updatedAt: 2023-03-29T01:24:00.848Z
-publishedAt: 2023-03-29T01:24:00.848Z
+updatedAt: 2024-07-24T12:05:55.438Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:25.912Z
 contentType: tutorial
 productTeam: Financial
@@ -19,24 +19,19 @@ _As configurações documentadas neste artigo são realizadas em um ambiente for
 
 Se você possui uma conta no PagSeguro e já utiliza a opção com redirect em sua loja, é possível habilitar a opção sem o redirect no Pagamentos. Isso significa que, na finalização de compra, o cliente não mais sairá de seu site para realizar o pagamento, mesmo transacionando pela PagSeguro. Isso ocorrerá de forma transparente.
 
-Essa opção está disponível como um novo conector na opção **Afiliações de Gateways**.
-
 Atenção: Caso o lojista tenha garantia de chargeback, é necessário configurar o antifraude do PagSeguro. Este processo exige uma etapa de configuração no Google Tag Manager. Para mais detalhes de como realizar essa ação, confira o [artigo na página do PagSeguro](https://dev.pagseguro.uol.com.br/v2/docs/configurando-device-fingerprint "artigo na página do PagSeguro").
 
 Para habilitá-la, confira o passo a passo a seguir:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-4. Clique em __Afiliações de Gateways__ e depois em __"+"__.
-5. Clique a afiliação __PagSeguroV2__.
-6. Salve a __afiliação__.
-7. Retorne para o __painel__ de afiliações.
-8. Selecione a afiliação __PagSeguroV2__ recém-criada.
-9. Clique em __Autorizar__.
-10. Selecione e envie a __regra desejada__.
-11. Clique em __Entre com seu email e senha__.
-12. Entre na __conta__ com seu e-mail e senha PagSeguro.
-13. Autorize a __aplicação__.
-14. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagSeguroV2__ na barra de busca e clique sobre o nome do provedor.
+4. Clique em __Authorize via OAuth__.
+5. Selecione e envie a __regra desejada__.
+6. Clique em __Entre com seu email e senha__.
+7. Entre na __conta__ com seu e-mail e senha PagSeguro.
+8. Autorize a __aplicação__.
+9. Clique em `Salvar`.
 
 ## Configurar condição de pagamento
 
diff --git a/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md b/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md
index 7ca4a83ad..77906b41c 100644
--- a/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md
+++ b/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md
@@ -36,7 +36,7 @@ Para desenvolver uma versão mobile com um novo WebSite, você deve seguir os se
 
   Storefront > Layout > Pasta CMS > Sites and Channels > New Website
 
-![cms-new-website](https://images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
+![cms-new-website](//images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
 
 3. Criar estrutura de pastas do WebSite Mobile: Nesse passo será necessário criar as pastas padrões do sistema que serão utilizadas na versão mobile (busca, departamento, categoria, marca, produto etc.)
 
diff --git a/docs/tutorials/pt/how-to-create-a-financial-access-profile.md b/docs/tutorials/pt/how-to-create-a-financial-access-profile.md
index 8e9c2c981..4e72120b8 100644
--- a/docs/tutorials/pt/how-to-create-a-financial-access-profile.md
+++ b/docs/tutorials/pt/how-to-create-a-financial-access-profile.md
@@ -31,7 +31,7 @@ Para criar um perfil de acesso financeiro:
 6. (Opcional) Antes de salvar, você pode **Adicionar usuários para este perfil de acesso**.
 7. Clique em **Salvar**.
 
-![gif perfil de acesso financeiro](https://images.ctfassets.net/alneenqid6w5/6fUKD0hvvh8rYapiH2sDit/205b3a066fe0fc456b6cf778ea2f3f40/gif_perfil_de_acesso_financeiro.gif)
+![gif perfil de acesso financeiro](//images.ctfassets.net/alneenqid6w5/6fUKD0hvvh8rYapiH2sDit/205b3a066fe0fc456b6cf778ea2f3f40/gif_perfil_de_acesso_financeiro.gif)
 
 Agora o perfil de acesso financeiro está criado e disponível para associação a usuários existentes.
 
@@ -45,9 +45,9 @@ Agora o perfil de acesso financeiro está criado e disponível para associação
 3. Clique na aba **Usuários**.
 4. Selecione o usuário que deseja associar.
 5. Agora, escolha o **perfil de acesso Financeiro**.
-6. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> ao lado do perfil selecionado para adicionar.
+6. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> ao lado do perfil selecionado para adicionar.
 7. Para finalizar, clique em **Salvar**.
 
-![gif usuário](https://images.ctfassets.net/alneenqid6w5/3HH5kuEBHEwYktRfC6aepQ/411e4398d285ac628f5691cb517638f8/gif_usu__rio.gif)
+![gif usuário](//images.ctfassets.net/alneenqid6w5/3HH5kuEBHEwYktRfC6aepQ/411e4398d285ac628f5691cb517638f8/gif_usu__rio.gif)
 
 Agora o usuário selecionado está associado ao perfil de acesso Financeiro e poderá acessar faturas, informações sobre o contrato, cobranças e outras informações financeiras.
diff --git a/docs/tutorials/pt/how-to-create-a-page-template.md b/docs/tutorials/pt/how-to-create-a-page-template.md
index a34d64bc3..5d06d08ee 100644
--- a/docs/tutorials/pt/how-to-create-a-page-template.md
+++ b/docs/tutorials/pt/how-to-create-a-page-template.md
@@ -3,8 +3,8 @@ title: 'Criar e editar um template de página'
 id: frequentlyAskedQuestions_1850
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:59.664Z
-updatedAt: 2023-03-27T14:56:34.174Z
-publishedAt: 2023-03-27T14:56:34.174Z
+updatedAt: 2023-11-01T20:27:09.646Z
+publishedAt: 2023-11-01T20:27:09.646Z
 firstPublishedAt: 2019-01-24T22:03:09.865Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -46,7 +46,7 @@ Confira o passo a passo a seguir:
 <li><code>app</code></li>
 </ul></p>
 </div>
-6. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+6. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. No canto superior direito, clique no botão __Save Template__.
 
 Para editar um template já existente, o processo é quase idêntico.
diff --git a/docs/tutorials/pt/how-to-create-a-product.md b/docs/tutorials/pt/how-to-create-a-product.md
index 30c43ba39..029e69b3e 100644
--- a/docs/tutorials/pt/how-to-create-a-product.md
+++ b/docs/tutorials/pt/how-to-create-a-product.md
@@ -167,7 +167,7 @@ Depois de realizar esse procedimento, as especificações criadas e suas respect
 
 Além disso, a partir da combinação das opções criadas, a lista de SKUs possíveis é gerada automaticamente e exibida na seção **[Variações](#variacoes)**.
 
-![variacoes PT](https://images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/4c28a11c44f7df5e108eb595b73a98bb/variations_PT_v2.png)
+![variacoes PT](//images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/4c28a11c44f7df5e108eb595b73a98bb/variations_PT_v2.png)
 
 ## Especificações
 
diff --git a/docs/tutorials/pt/how-to-create-a-store-name.md b/docs/tutorials/pt/how-to-create-a-store-name.md
index 3348aa04a..00bf6851e 100644
--- a/docs/tutorials/pt/how-to-create-a-store-name.md
+++ b/docs/tutorials/pt/how-to-create-a-store-name.md
@@ -22,7 +22,7 @@ Para criar ou editar um [nome de loja](https://help.vtex.com/pt/tutorial/o-que-e
 3. Clique em **Conta**.
 4. No painel Loja, você verá os nomes de loja que já existem na sua conta. Você pode editar as informações de cada loja, ou criar um novo nome de loja, clicando no botão **Configurar outra loja**.
 
-![Configuração de nome de loja](https://images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/b2bed2ce47001c83e3ea75e6896e7a28/PT.PNG)
+![Configuração de nome de loja](//images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/b2bed2ce47001c83e3ea75e6896e7a28/PT.PNG)
 
 Para saber como configurar o domínio de suas lojas, veja o artigo [Mudar o domínio da loja](https://help.vtex.com/pt/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
diff --git a/docs/tutorials/pt/how-to-create-a-subscription-attachment.md b/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
index 81c22184f..38331a742 100644
--- a/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
@@ -71,11 +71,11 @@ Siga o passo a passo abaixo para configurar as frequências e datas de ciclo de
 
         * **Semanalmente**: os valores possíveis de preenchimento deste campo são = `0`, `1`, `2`, `3`, `4`, `5`, e `6`, equivalentes aos dias da semana. Considere `0` = domingo , `1` = segunda, `2` = terça, e assim sucessivamente até `6` = sábado. Separe os  valores por `,`, conforme ilustrado abaixo.
 
-        ![PT Assinatura Exemplo Valores week](https://images.ctfassets.net/alneenqid6w5/20va8G0uiw3jpHKM2a99Al/7ef796fd84e1328bcc0b6f637bdc30f1/PT_Assinatura_Exemplo_Valores_week.png)
+        ![PT Assinatura Exemplo Valores week](//images.ctfassets.net/alneenqid6w5/20va8G0uiw3jpHKM2a99Al/7ef796fd84e1328bcc0b6f637bdc30f1/PT_Assinatura_Exemplo_Valores_week.png)
 
         * **Mensalmente**: os valores possíveis de preenchimento deste campo no checkout são = `1`, `2`, `3`, (...) até `28`, que são equivalentes aos dias do mês. Considere `1` = primeiro dia do mês, `2` = segundo dia do mês, e assim sucessivamente até `28` = vigésimo oitavo dia do mês. Separe os  valores por `,`, conforme ilustrado abaixo.
 
-        ![PT Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/3ogGjc6DLexe7YeL3qyiuI/748b3dd8e63870c539b58f3404521031/PT_Assinatura_Exemplo_Valores_month.png)
+        ![PT Assinatura Exemplo Valores month](//images.ctfassets.net/alneenqid6w5/3ogGjc6DLexe7YeL3qyiuI/748b3dd8e63870c539b58f3404521031/PT_Assinatura_Exemplo_Valores_month.png)
 
 <div class="alert alert-info">
   <p>Caso nenhum valor seja inserido no campo <strong>Valores Permitidos</strong>, a data do ciclo de assinatura será o mesmo dia da semana (caso a frequência seja semanal) ou dia do mês (caso a frequência seja mensal) do pedido original.</p>
diff --git a/docs/tutorials/pt/how-to-create-conditional-prices.md b/docs/tutorials/pt/how-to-create-conditional-prices.md
index e44c771c6..d1d6f9b77 100644
--- a/docs/tutorials/pt/how-to-create-conditional-prices.md
+++ b/docs/tutorials/pt/how-to-create-conditional-prices.md
@@ -34,4 +34,4 @@ Segue abaixo um passo a passo de como usar esses Preços Condicionais :
 6. Você pode definir uma pequena mensagem, chamada *Teaser*, pra promover essa condição ao seu cliente. (Para entender melhor, veja [Teasers - Em breve])
 7. Salve.
 
-![conditionalPrice](https://images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
+![conditionalPrice](//images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
diff --git a/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md b/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md
new file mode 100644
index 000000000..14f749997
--- /dev/null
+++ b/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md
@@ -0,0 +1,86 @@
+---
+title: 'Como customizar a interface personalizada do Checkout no Admin'
+id: 548aDBJciQu97Vh0BhEiWx
+status: PUBLISHED
+createdAt: 2024-01-04T13:27:04.734Z
+updatedAt: 2024-01-04T18:28:45.989Z
+publishedAt: 2024-01-04T18:28:45.989Z
+firstPublishedAt: 2024-01-04T18:28:45.989Z
+contentType: tutorial
+productTeam: Shopping
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: como-customizar-a-interface-personalizada-do-checkout-no-admin
+locale: pt
+legacySlug: como-customizar-a-interface-personalizada-do-checkout-no-admin
+subcategory: 6XAvmMxp7yyY06ewYMuggs
+---
+
+As customizações do Checkout descritas neste artigo são realizadas por meio do Checkout UI Custom app. Antes de iniciar as configurações, você deve verificar se o app está instalado na loja, ou realizar a instalação conforme o artigo [Checkout UI Custom](https://developers.vtex.com/docs/apps/vtex.checkout-ui-custom).
+
+## Customizando o Checkout
+
+No Admin VTEX, acesse **Configurações da loja > Storefront > Interface personalizada do checkout**, ou digite **Interface personalizada do checkout** na barra de busca no topo da página.
+
+As funcionalidades de customização do app podem ser acessadas por meio das seguintes abas no Admin:
+
+* [Interface](#interface)
+* [Cores](#cores)
+* [JavaScript](#javascript)
+* [CSS](#css)
+* [Histórico](#histórico)
+
+## Interface
+
+Nesta aba é possível realizar as seguintes configurações:
+
+1. **Opções de pagamento estilo sanfona:** ao habilitar o botão, os meios de pagamentos são exibidos em cascata (sanfona), se houver até cinco meios de pagamentos. Quando desabilitado, os meios de pagamentos são exibidos em abas laterais.
+
+2. **Data de entrega simplificada:** ao habilitar o botão você terá acesso à visualização da estimativa de entrega em formato de data, como por exemplo, segunda-feira,18/09/23.  Quando a opção estiver desabilitada, os dados fornecidos se limitarão a uma estimativa do prazo em dias, como por exemplo, Até 5 dias úteis.
+
+3. **Mostrar preço unitário do item:** ao habilitar o botão, o usuário irá visualizar o valor unitário de cada produto e o valor total somado, de acordo com a quantidade do mesmo produto. Quando a opção estiver desabilitada, é possível visualizar apenas o valor unitário de cada produto.
+
+4. **Exibir campo de anotações:** ao habilitar este botão é permitido visualizar uma caixa para incluir comentários adicionais ao pedido, como por exemplo uma mensagem de felicitações, caso o produto seja um presente ou alguma observação referente a entrega do produto. Quando desabilitado, não é exibido esta caixa de comentário.
+
+5. **Remover a etapa de email:** ao habilitar o botão, a opção de preenchimento automático de dados via inserção do email é desabilitada. Quando desativado, é necessário preencher manualmente suas informações de contato.
+
+6. **Formulário de endereço do Google:** esta é uma integração do formulário de endereço com o Google (em fase beta). Quando habilitado o botão, permite que ao digitar o endereço, seja oferecido sugestões de autopreenchimento, que quando selecionado realiza um preenchimento automático dos campos do endereço.
+
+7. **Tamanho do texto:** essa configuração possibilita alterar o tamanho da fonte (em pixels) no Checkout.
+
+8. **Arredondamento da borda:** essa configuração possibilita personalizar o formato de arredondamento da borda externa (em pixels) no Checkout.
+
+9. **Arredondamento da borda do botão:** esta configuração permite personalizar o formato de arredondamento da borda dos botões (em pixels) no Checkout.
+
+10. **Altura do campo de texto:** permite personalizar a espessura (em pixels) dos campos de texto no checkout.
+
+11. **Largura máxima do conteúdo:** permite configurar a largura máxima (em pixels) da exibição das informações no Checkout.
+
+12. **Borda do conteúdo:** permite configurar o [tipo de borda](https://www.w3schools.com/css/css_border.asp) das seções no Checkout.
+
+13. **Família de fontes:** permite configurar os tipos de fontes utilizadas no Checkout.
+
+## Cores
+
+A aba Cores permite personalizar as cores do checkout de sua loja, permitindo alterar cores de fundo, botões, texto entre outros. Essa padronização garante uma harmonia visual consistente.
+
+![Cores ](//images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/73b92d83429b6e2a0d61e2e7c1b4d20e/Cores_-_PT.png)
+
+## Javascript
+
+A aba JavaScript  adiciona uma camada adicional de personalização à interface permitindo a inclusão de scripts.
+
+![Java - PT](//images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/f71cb1f35775b2a770c12de7be5b9068/Java_-_PT.png)
+
+## CSS
+
+A aba CSS permite customizações visuais da loja com a inclusão de código CSS.
+
+![CSS - PT](//images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/ba9c09575f3ba303ad987f9001afb547/CSS_-_PT.png)
+
+## Histórico
+
+Permite visualizar e restaurar customizações criadas e publicadas anteriormente.
+
+![Histórico - PT](//images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/66f5b12a5417725a619895df98c4fa96/Hist_rico_-_PT.png)
+
+Para garantir que suas configurações sejam aplicadas com sucesso, basta realizar as configurações necessárias e clicar no botão `Publicar`.
diff --git a/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
index 3753bf6c3..c4853fe53 100644
--- a/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
@@ -23,7 +23,7 @@ Você pode alterar o **textLink** de um produto existente a qualquer momento pel
 
 Confira a seção [Regras de preenchimento](#regras-de-preenchimento) para entender as restrições desse campo.
 
-![textlink.pt](https://images.ctfassets.net/alneenqid6w5/3K8sFWVJYkESKC7EVWP4zZ/37e4b22a4f177d28c197042ad027c3de/textlink.pt.png)
+![textlink.pt](//images.ctfassets.net/alneenqid6w5/3K8sFWVJYkESKC7EVWP4zZ/37e4b22a4f177d28c197042ad027c3de/textlink.pt.png)
 
 <div class="alert alert-info">
   <p>Também é possível alterar a URL de um produto utilizando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview">API do Catálogo</a>. Nesse caso, o campo a ser alterado é o <code>LinkId</code>. Confira <a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product">Update Product</a> para mais informações.</p>
diff --git a/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md b/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md
index 300c65107..86ee0e4d7 100644
--- a/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md
+++ b/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md
@@ -19,4 +19,4 @@ Caso você necessite realizar um rollback da sua app, rode o comando `vtex depre
 
 Se você perceber em seguida que será necessario desfazer a deprecação, poderá realizar o comando `vtex undeprecate`
 
-![image (2)](https://images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
+![image (2)](//images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
diff --git a/docs/tutorials/pt/how-to-disable-a-transactional-email.md b/docs/tutorials/pt/how-to-disable-a-transactional-email.md
index d3e1af53f..031f43950 100644
--- a/docs/tutorials/pt/how-to-disable-a-transactional-email.md
+++ b/docs/tutorials/pt/how-to-disable-a-transactional-email.md
@@ -28,7 +28,7 @@ Confira o passo a passo a seguir:
 3. Pesquise por __Payment Pending__ na caixa de busca.
 4. Desmarque a opção __Ativar envio de e-mail__.
 
-  ![Message Center - Desativar - PT](https://images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/3ed63d224e34fc3b5a52540cc880ba4a/dlSCQPRLKf46SnYGl7X9a_PT_Payment_Pending.jpg)
+  ![Message Center - Desativar - PT](//images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/3ed63d224e34fc3b5a52540cc880ba4a/dlSCQPRLKf46SnYGl7X9a_PT_Payment_Pending.jpg)
 
 5. Clique em __Salvar__.
 
diff --git a/docs/tutorials/pt/how-to-download-the-vtex-invoices.md b/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
index 070897087..2772af4bb 100644
--- a/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
@@ -47,7 +47,7 @@ Para fazer o download da sua fatura, siga os passos abaixo:
 
 Feito isso, sua fatura estará disponível em outra aba.
 
-![baixar faturas pt](https://images.ctfassets.net/alneenqid6w5/2v9nnJfdYMrIw9DhYsV6oz/8acb4b8fe2db1b1cf36500cd2bff7b09/baixar_faturas_pt.gif)
+![baixar faturas pt](//images.ctfassets.net/alneenqid6w5/2v9nnJfdYMrIw9DhYsV6oz/8acb4b8fe2db1b1cf36500cd2bff7b09/baixar_faturas_pt.gif)
 
 ## Brasil
 
@@ -67,7 +67,7 @@ Para fazer o download de seu boleto, siga os passos abaixo:
 
 <div class="alert alert-info"> No Brasil, uma fatura roxa pode indicar que está atrasada mas com um novo boleto gerado para uma data próxima. Nesse caso, a fatura continuará em atraso até a quitação do pagamento. Caso não seja efetuado o pagamento do novo boleto, a fatura voltará a cor vermelha.</div>
 
-![baixar boletos pt](https://images.ctfassets.net/alneenqid6w5/3gRniiqHrpZZHNTsQC8Gfm/21d45f702de76ea5c866b61a3c80be8f/baixar_boletos_pt.gif)
+![baixar boletos pt](//images.ctfassets.net/alneenqid6w5/3gRniiqHrpZZHNTsQC8Gfm/21d45f702de76ea5c866b61a3c80be8f/baixar_boletos_pt.gif)
 
 ### Fazer download da Nota Fiscal
 
@@ -84,6 +84,6 @@ Desse modo, a Nota Fiscal será aberta em outra aba do seu navegador. Clique **I
 1. Em Destino, selecione a opção **Salvar em PDF**.
 2. Para finalizar, clique em **Salvar**.
 
-![baixar notafiscal pt](https://images.ctfassets.net/alneenqid6w5/5jKzvOnt2V3JtrvKfxJ9zU/8ce862d5a13587d72464d3a3efea907f/baixar_notafiscal_pt.gif)
+![baixar notafiscal pt](//images.ctfassets.net/alneenqid6w5/5jKzvOnt2V3JtrvKfxJ9zU/8ce862d5a13587d72464d3a3efea907f/baixar_notafiscal_pt.gif)
 
 Caso você tenha dúvidas sobre o valor cobrado na fatura, leia o artigo [Compreenda o valor da receita aprovada](https://help.vtex.com/pt/tutorial/como-acessar-o-valor-da-receita-aprovada--tutorials_4322) para entender o valor que foi cobrado.
diff --git a/docs/tutorials/pt/how-to-identify-a-page-template.md b/docs/tutorials/pt/how-to-identify-a-page-template.md
index 4a7d59b3a..77dcb5b50 100644
--- a/docs/tutorials/pt/how-to-identify-a-page-template.md
+++ b/docs/tutorials/pt/how-to-identify-a-page-template.md
@@ -27,7 +27,7 @@ A VTEX usa o mesmo princípio. O diretório (pasta) é onde deve ser guardada to
 
 Podemos criar inúmeros templates mas devemos especificar no diretório qual template será exibido. Usando a página de __Produto__ como exemplo:
 
-![cms-template-pagina PT](https://images.ctfassets.net/alneenqid6w5/5f0VY6nFAAecUce6SQq02m/266795c901433c282669bbb1af7ccb7e/Produto_CMS.png)
+![cms-template-pagina PT](//images.ctfassets.net/alneenqid6w5/5f0VY6nFAAecUce6SQq02m/266795c901433c282669bbb1af7ccb7e/Produto_CMS.png)
 
 Storefront > Layout > Pasta CMS > Sites and channels > Nome da Loja > Pasta raíz (/) > Produto (por exemplo) > Clicar no link que estiver com a setinha vermelha de "ok"
 
diff --git a/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md b/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md
index 75917f36c..2e39500f4 100644
--- a/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md
+++ b/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md
@@ -26,7 +26,7 @@ Para isso faça os seguintes passos :
 1. Para desabilitar o JS da página basta colocar o `/tools.html` no fim da URL. Ex: {AccountName}.myvtex.com/tools.html
 2. Clique em __Disable__ na aba __Client JavaScript is__.
 
-![javascript-disable ](https://images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png) 
+![javascript-disable ](//images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png) 
 
 3. Após isso, retire o `/tools.html` da URL e atualize a página.
 
diff --git a/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
index 15096ffde..271bb5c66 100644
--- a/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
@@ -28,9 +28,9 @@ Você pode fazer um pedido para teste na loja e, em seguida, verificar no **Gere
 
 Exemplo: imagine um pedido em que frete grátis foi aplicado, mas você não sabe o motivo. Ao clicar em um pedido no **Gerenciamento de pedidos**, você encontraria o nome da promoção registrada na seção **Promoções e parcerias**.
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/9b4ede20a2b910d2a4c2b117a4e0b7ec/detalhes-oms-pt__1_.png" alt="detalhes-do-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/9b4ede20a2b910d2a4c2b117a4e0b7ec/detalhes-oms-pt__1_.png" alt="detalhes-do-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/b9de1a7d07c48b49026ec6d3adba4d20/detalhes-neworders-pt__1_.png" alt="detalhes-do-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido (Beta)</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/b9de1a7d07c48b49026ec6d3adba4d20/detalhes-neworders-pt__1_.png" alt="detalhes-do-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido (Beta)</em></figcaption></figure>
 
 Se nenhuma promoção estiver listada, isso indica que o frete grátis não tem como causa uma promoção, ou seja, o cálculo de frete no módulo de **Estoque & entrega** teve como resultado zero. Nesse caso, seria necessário utilizar o **Simulador de envio** para entender por que razão o frete teve valor zero.
 
@@ -40,7 +40,7 @@ No carrinho, você pode passar o mouse sobre o ícone de interrogação que fica
 
 Porém, caso mais de uma promoção seja aplicada, o que aparecerá será apenas o somatório dos descontos, dificultando a análise do cenário.
 
-![example-cart](https://images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/58e4571f3ce7b0af86ecf17885799258/image6.png)
+![example-cart](//images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/58e4571f3ce7b0af86ecf17885799258/image6.png)
 
 ## orderForm
 
diff --git a/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md b/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md
index 310f13172..c46dc1b7f 100644
--- a/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md
+++ b/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md
@@ -29,7 +29,7 @@ Para enviar dados de pedidos para sistemas externos, como dashboards e data lake
 
 Quando um pedido é fechado no inStore, a identificação do usuário logado no aplicativo fica visível na parte superior da tela de detalhes do pedido no Admin. No exemplo abaixo, o nome do usuário é `A123456`.
 
-![PT - ID do vendedor inStore](https://images.ctfassets.net/alneenqid6w5/2VlKApkaFLzzxl6wRrcNkw/b46bb2740a82a8fab8988f7dd752f7ce/PT_-_ID_do_vendedor_inStore.png)
+![PT - ID do vendedor inStore](//images.ctfassets.net/alneenqid6w5/2VlKApkaFLzzxl6wRrcNkw/b46bb2740a82a8fab8988f7dd752f7ce/PT_-_ID_do_vendedor_inStore.png)
 
 Quando os detalhes do pedido são obtidos pela [Orders API](https://developers.vtex.com/vtex-developer-docs/reference/orders), o nome do usuário está disponível no campo `callCenterOperatorData.userName`. Também é possível acessar o e-mail deste usuário em  `callCenterOperatorData.email`.
 
@@ -43,7 +43,7 @@ Quando os detalhes do pedido são obtidos pela [Orders API](https://developers.v
 
 Caso o usuário logado no aplicativo seja compartilhado entre vendedores da mesma loja, é possível ainda incluir a identificação do vendedor no campo de observação do cliente.
 
-![PT - ID do vendedor inStore (alt)](https://images.ctfassets.net/alneenqid6w5/2VFGuKA7ZUgcO55TPgpDWU/ce44ee5a33db7284999dc2700d964f75/PT_-_ID_do_vendedor_inStore__alt_.png)
+![PT - ID do vendedor inStore (alt)](//images.ctfassets.net/alneenqid6w5/2VFGuKA7ZUgcO55TPgpDWU/ce44ee5a33db7284999dc2700d964f75/PT_-_ID_do_vendedor_inStore__alt_.png)
 
 Quando os detalhes do pedido são obtidos pela Orders API, esta informação fica disponível no campo `openTextField.value`.
 
@@ -57,7 +57,7 @@ Quando os detalhes do pedido são obtidos pela Orders API, esta informação fic
 
 Quando um pedido é fechado no inStore, a identificação da loja fica visível na seção de Promoções e Parcerias da tela de detalhes do pedido no Admin. No exemplo abaixo, o identificador da loja é `8b4d5ea1-2055-11ea-82fa-0ad725bc7b4f`.
 
-![PT - ID da loja inStore](https://images.ctfassets.net/alneenqid6w5/x0Czqfo4emIb8X6zgQgD2/e6867ef4cf7bd54cd471ee7d07ccd59c/PT_-_ID_da_loja_inStore.png)
+![PT - ID da loja inStore](//images.ctfassets.net/alneenqid6w5/x0Czqfo4emIb8X6zgQgD2/e6867ef4cf7bd54cd471ee7d07ccd59c/PT_-_ID_da_loja_inStore.png)
 
 Quando os detalhes do pedido são obtidos pela Orders API, esta informação fica disponível no campo `marketingData.utmSource`.
 
@@ -82,7 +82,7 @@ Quando os detalhes do pedido são obtidos pela Orders API, esta informação fic
 
 O identificador do vendedor e da loja podem ser usados para consultar os dados de cadastro em `https://{accountName}.myvtex.com/admin/vtable`. 
 
-![PT - Admin inStore](https://images.ctfassets.net/alneenqid6w5/4k1KmCEABh6BJBBCBh5B4F/fe249d924308d3d2f8b7fbfbec739f05/Screen_Shot_2020-11-09_at_15.20.50.png)
+![PT - Admin inStore](//images.ctfassets.net/alneenqid6w5/4k1KmCEABh6BJBBCBh5B4F/fe249d924308d3d2f8b7fbfbec739f05/Screen_Shot_2020-11-09_at_15.20.50.png)
 
 <div class="alert alert-info" role="alert">As instruções abaixo explicam como fazer essas consultas usando os identificadores que aparecem em um pedido. Se necessário, entretanto, é possível buscar usando qualquer campo do cadastro de lojas e vendedores.</div>
 
@@ -98,7 +98,7 @@ Para fazer essa busca, siga as instruções abaixo:
 
 Ao concluir o passo 4, a expressão do filtro de busca deve ficar no formato `Nome:=:A123456`. Assim será possível encontrar o vendedor na listagem de vendedores, como visto na imagem abaixo.
 
-![PT - Admin dos vendedores](https://images.ctfassets.net/alneenqid6w5/601CfGNUMAQyhhWyNcpJg6/67b8789e9b10570025613023fc8e1e30/PT_-_Admin_dos_vendedores.png)
+![PT - Admin dos vendedores](//images.ctfassets.net/alneenqid6w5/601CfGNUMAQyhhWyNcpJg6/67b8789e9b10570025613023fc8e1e30/PT_-_Admin_dos_vendedores.png)
 
 Caso prefira fazer essa consulta por API, basta usar o endpoint [Search Documents](https://developers.vtex.com/vtex-developer-docs/reference/search#searchdocuments) da [Master Data API - V2](https://developers.vtex.com/reference/master-data-api-v2-overview) para buscar pelo identificador da loja na entidade de dados `vendors`.
 
@@ -114,6 +114,6 @@ Para fazer essa busca, siga as instruções abaixo:
 
 Ao concluir o passo 4, a expressão do filtro de busca deve ficar no formato `Id do Documento:=:8b4d5ea1-2055-11ea-82fa-0ad725bc7b4f`. Assim será possível encontrar a loja na listagem de lojas, como visto na imagem abaixo.
 
-![PT - Admin das lojas](https://images.ctfassets.net/alneenqid6w5/ZORye3vSq6dVZ5aE4SRnl/dca845c2c8a16a01b75f9cca1b2b6d2a/PT_-_Admin_das_lojas.png)
+![PT - Admin das lojas](//images.ctfassets.net/alneenqid6w5/ZORye3vSq6dVZ5aE4SRnl/dca845c2c8a16a01b75f9cca1b2b6d2a/PT_-_Admin_das_lojas.png)
 
 Caso prefira fazer essa consulta por API, basta usar o endpoint [Search Documents](https://developers.vtex.com/vtex-developer-docs/reference/search#searchdocuments) da [Master Data API - V2](https://developers.vtex.com/reference/master-data-api-v2-overview) para buscar pelo identificador da loja na entidade de dados `stores`.
diff --git a/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
index 93c440ed5..dae42a7d7 100644
--- a/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
@@ -27,8 +27,8 @@ Um arquivo XLS de <strong>10 MB</strong> permite o cadastro de, aproximadamente,
 ## Como fazer o upload da planilha
 1. No menu lateral, clique em __Estoque & entrega__, na seção __Pedidos__.
 2. Nas opções que se abrem, clique em __Pontos de retirada__.
-3. Clique em __Subir um XLS__, localizado no canto superior direito da página. ![Subir XLS](https://images.ctfassets.net/alneenqid6w5/405kNpYa3mg6iSaS0UgQmq/4f544dfad6e5e7b95e63c5420c8884fe/Subir_XLS.png)
-4. Um modal vai surgir, permitindo que você envie seu arquivo (com extensão `.xls`) ou baixe a [planilha de exemplo](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Lembre-se de que ela vem com valores de exemplo preenchidos, que devem ser deletados e substituídos pelos dados dos seus próprios pontos de retirada. ![modal (PT)](https://images.ctfassets.net/alneenqid6w5/20X1H7Xla4WsqoG24UssK2/12a46b5171a72837f5ad6fb46287aae5/modal__PT_.png)
+3. Clique em __Subir um XLS__, localizado no canto superior direito da página. ![Subir XLS](//images.ctfassets.net/alneenqid6w5/405kNpYa3mg6iSaS0UgQmq/4f544dfad6e5e7b95e63c5420c8884fe/Subir_XLS.png)
+4. Um modal vai surgir, permitindo que você envie seu arquivo (com extensão `.xls`) ou baixe a [planilha de exemplo](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Lembre-se de que ela vem com valores de exemplo preenchidos, que devem ser deletados e substituídos pelos dados dos seus próprios pontos de retirada. ![modal (PT)](//images.ctfassets.net/alneenqid6w5/20X1H7Xla4WsqoG24UssK2/12a46b5171a72837f5ad6fb46287aae5/modal__PT_.png)
 5. Com tudo certo, os novos pontos de retirada vão estar configurados e disponíveis para seus clientes.
 
 
diff --git a/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
index 2b6c45ac0..6d1061aec 100644
--- a/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -27,31 +27,31 @@ Realizadas as devidas definições, o vínculo da coleção com a vitrine é fei
 
 No exemplo a seguir, iremos definir a vitrine apresentada na Home, para isso, selecione **Settings**, depois **add object**, conforme na imagem a seguir.
 
-![coleção2](https://images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
+![coleção2](//images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
 
 Esse comando irá abrir o **Visual Controls**, ou seja, o controle correspondente à vitrine em que se deseja exibir a coleção. Adicione uma _Coleção_, porém não se esqueça de definir um nome para ela.
 
-![coleção3](https://images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
+![coleção3](//images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
 
-![coleção4](https://images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
+![coleção4](//images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
 
 Para editar o controle criado, é necessário salvar as configurações primeiramente em **Save Settings**.
 
-![coleção5](https://images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
+![coleção5](//images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
 
-![coleção6](https://images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
+![coleção6](//images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
 
 Ao editar o controle é necessário adicionar seus conteúdos, que representam cada conjunto de itens que serão exibidos.
 São eles:
 _Layout_: Selecione o template de prateleira utilizado na vitrine.
 _Number of Columns, Number of Items,Show Unavailable, Ramdom ad Paged_: Definem a disposição, quantidade e qual o critério de exibição dos itens.
 
-![coleção7](https://images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
+![coleção7](//images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
 
 Lembre-se de salvar as alterações antes de efetuar uma busca ou mudar de página.
 
 O próximo passo é adicionar o conteúdo, selecionando **Add Content**.
-![coleção8](https://images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
+![coleção8](//images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
 
 É possível definir cada conteúdo utilizando coleções ou resultados de busca, utilizando parâmetros de busca (mais detalhes [aqui](/pt/tutorial/parametros-de-busca "aqui"))
 
@@ -61,7 +61,7 @@ _QueryString_: Os parâmetros preenchidos nesse campo definem o resultado de bus
 
 No campo **Product Cluster (Collection)**, é necessário selecionar a coleção que será exibida, para isso, siga o passo a seguir:
 
-![coleção10](https://images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
+![coleção10](//images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
 
 Os conteúdos a serem preenchidos na parte **Display Condition**:
 _Partner, Campaign_ e _Source_: Definem a exibição deste conteúdo, caso o visitante possua alguma UTM correspondente em sua URL de origem.
@@ -73,7 +73,7 @@ Após as definições, deve-se marcar a opção **Active Content** e adicionar n
 
 No exemplo abaixo temos uma vitrine padrão, sem condições de exibição, e outra exclusiva para as visitas oriundas das audiências de campanhas patrocinadas do Google (utm_source=**google**/utm_medium=**cpc**):
 
-![coleção9](https://images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
+![coleção9](//images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
 
 No cenário acima, caso o cliente tenha origem na audiência de campanha patrocinada serão exibidos na vitrine **Lançamentos**, localizada na Home, os produtos que correspondem ao resultado de uma busca pela Marca de ID 200000, caso contrário, serão exibidos os produtos da coleção de ID 8.
 
diff --git a/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md b/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
index 721fdf52c..40a5c95da 100644
--- a/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
+++ b/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
@@ -18,10 +18,10 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 Para incluir metadados ao exportar uma planilha de preços de SKUs siga os passos abaixo:
 
 1. Clique em **Preços**, no menu do lado esquerdo da página
-![refidplanilha1](https://images.ctfassets.net/alneenqid6w5/7rc4ppgcGNvFETJ2GxAQlt/32d2770ca9ecaaa693b49031d5bb4705/refidplanilha1.png)
+![refidplanilha1](//images.ctfassets.net/alneenqid6w5/7rc4ppgcGNvFETJ2GxAQlt/32d2770ca9ecaaa693b49031d5bb4705/refidplanilha1.png)
 2. Clique em **lista de preços**
 3.  Na parte superior da página, lado esquerdo, clique no ícone de **seta para baixo**
 4. Na aba lateral que se abrirá, escolha a opção de tabela que deseja exportar
 5. Clique em **incluir metadados nas tabelas exportadas**
 6. Clique no botão **Exportar tabela**
-![refidplanilha2](https://images.ctfassets.net/alneenqid6w5/4NgcVyUUruaf5sfR8cDpWP/93c4f35d46fe8c8ff5fccb372a072379/refidplanilha2.png)
+![refidplanilha2](//images.ctfassets.net/alneenqid6w5/4NgcVyUUruaf5sfR8cDpWP/93c4f35d46fe8c8ff5fccb372a072379/refidplanilha2.png)
diff --git a/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md b/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
index edd5c2f76..50b4fce8c 100644
--- a/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
+++ b/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
@@ -3,24 +3,26 @@ title: 'Como inserir um proxy reverso em frente aos serviços da VTEX'
 id: 4PFWsfRAKviNVPf1bYdiir
 status: PUBLISHED
 createdAt: 2019-09-20T14:11:30.301Z
-updatedAt: 2020-08-20T21:15:13.613Z
-publishedAt: 2020-08-20T21:15:13.613Z
+updatedAt: 2023-10-26T22:21:31.465Z
+publishedAt: 2023-10-26T22:21:31.465Z
 firstPublishedAt: 2019-09-23T12:22:50.056Z
 contentType: tutorial
 productTeam: Reliability
 author: authors_24
-slug: por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da
+slug: por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da-vtex
 locale: pt
 legacySlug: por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
 <div class="alert alert-danger">
-<strong>Atenção:</strong> as explicações deste artigo visam a atender a casos de extrema exceção. Não recomendamos que nenhuma loja utilize proxy reverso. Ao utilizar um proxy reverso, todo serviço de borda (CDN) gerenciado e otimizado pela VTEX será deixado de lado, de modo que o serviço da loja é quem ficará responsável pelo fornecimento efetivo do site, sendo este o responsável por fazer suas configurações, acompanhamento e gerenciamento de particularidades como repasse de cabeçalhos, cookies e gestão de cache. Não disponibilizamos documentação dessas especificidades.<br>
-A VTEX não se responsabiliza por problemas nesse sistema, seja um CDN próprio, serviço de WAF ou outro recurso que fique à frente de nossos servidores. Não teremos visão de quaisquer falhas, e, portanto, a solução <strong>não</strong> se enquadrará em nossos acordos de SLA.
+<p><strong>Atenção:</strong> as explicações deste artigo visam a atender a casos de extrema exceção. Não recomendamos que nenhuma loja utilize proxy reverso. Ao utilizar um proxy reverso, todo serviço de borda (CDN) gerenciado e otimizado pela VTEX será deixado de lado, de modo que o serviço da loja é quem ficará responsável pelo fornecimento efetivo do site, sendo este o responsável por fazer suas configurações, acompanhamento e gerenciamento de particularidades como repasse de cabeçalhos, cookies e gestão de cache. Não disponibilizamos documentação dessas especificidades.</p>
+<p>A VTEX não se responsabiliza por problemas nesse sistema, seja um CDN próprio, serviço de WAF ou outro recurso que fique à frente de nossos servidores. Não teremos visão de quaisquer falhas, e, portanto, a solução <strong>não</strong> se enquadrará em nossos acordos de SLA.</p>
 </div>
 
-Se mesmo após ler o alerta acima você deseja apontar sua própria CDN para a CDN da VTEX, será necessário inserir um proxy reverso em frente aos serviços da VTEX. Para isso, crie as entradas TXT indicadas abaixo. Elas vão servir como entrada de verificação para nos informar que o host de fato aponta para a VTEX. Sem isso, a VTEX não consegue prover navegação.
+Se mesmo após ler o alerta acima você deseja apontar sua própria CDN para a CDN da VTEX, será necessário inserir um proxy reverso em frente aos serviços da VTEX.
+
+Para isso, crie as entradas TXT indicadas abaixo. Elas vão servir como entrada de verificação para nos informar que o host de fato aponta para a VTEX. Sem isso, a VTEX não consegue prover navegação.
 
 1. Na zona de DNS do seu domínio, crie uma entrada do tipo TXT em `_{hostname}` com o mesmo valor que seria usado no CNAME.
 2. Direcione o tráfego da CDN/WAF para nossos servidores com o valor correspondente ao CNAME do domínio.
@@ -33,8 +35,10 @@ Portanto, a configuração deve ficar assim:
 Além disso, também será necessário que todo o tráfego de `/.well-known/acme-challenge/*` chegue até a VTEX. Alguns proxys reversos capturam essa rota, e, com isso, não conseguimos emitir ou renovar o certificado SSL.
 
 <div class="alert alert-warning">
-A VTEX somente provê navegação se:<br>
-- Conseguirmos enxergar que o host aponta para a VTEX (conforme nosso CNAME).<br>
-- Conseguirmos emitir/renovar certificados SSL para o host.<br>
-Se ambas as condições não forem atendidas, a VTEX deixa de entregar o site, pois fica caracterizado que ele está fora do ar.
+<p>A VTEX somente provê navegação se for possível:
+  <ul>
+    <li>Observar que o host aponta para a VTEX (conforme nosso CNAME).</li>
+    <li>Emitir e renovar certificados SSL para o host.</li>
+  </ul>
+Se ambas as condições não forem atendidas, a navegação não funciona, pois fica caracterizado que o site está fora do ar.</p>
 </div>
diff --git a/docs/tutorials/pt/how-to-install-a-service-worker.md b/docs/tutorials/pt/how-to-install-a-service-worker.md
index c3696e946..3b38e466a 100644
--- a/docs/tutorials/pt/how-to-install-a-service-worker.md
+++ b/docs/tutorials/pt/how-to-install-a-service-worker.md
@@ -3,34 +3,37 @@ title: 'Como instalar um Service Worker'
 id: 2H057iW0mQGguKAciwAuMe
 status: PUBLISHED
 createdAt: 2018-03-13T14:53:11.260Z
-updatedAt: 2023-04-05T17:55:03.904Z
-publishedAt: 2023-04-05T17:55:03.904Z
+updatedAt: 2024-01-19T12:54:32.525Z
+publishedAt: 2024-01-19T12:54:32.525Z
 firstPublishedAt: 2018-03-13T17:48:34.728Z
 contentType: tutorial
 productTeam: Financial
-author: 7FpKZ0rc6k4WqeymES80cw
+author: 2AhArvGNSPKwUAd8GOz0iU
 slug: como-instalar-um-service-worker
 locale: pt
 legacySlug: como-instalar-um-service-worker
-subcategory: 
+subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
-Service Worker é um script que seu navegador executa em segundo plano, separado da Web, possibilitando recursos como sincronização periódica, notificações push e até execução em modo off-line.
+
+Service Worker é um script que seu navegador executa em segundo plano, separado da Web, possibilitando recursos como sincronização periódica, notificações push e até execução em modo offline.
 
 Para criar o script, siga o passo a passo abaixo:
 
-1. No Admin VTEX, acesse o módulo __Portal__.
-2. Clique no ícone de __Configurações__.
-3. Depois, na aba __Código__.
-4. Clique em __Novo__ e em seguida em __Arquivo__.
-5. Inclua o nome do arquivo exatamente como: __service-worker.js__.
-6. Programe a __funcionalidade__.
-7. Para finalizar, clique em __Salvar__.
+1. No Admin VTEX, acesse **Configurações da loja > Storefront > Ckeckout**, ou digite **Checkout** na barra de busca no topo da página.
+2. Clique no ícone de <i class="fas fa-cog"></i> do site desejado.
+3. Na aba `Código`, clique no botão `Novo`.
+4. Em seguida, clique em `Arquivo`.
+5. Preencha o nome do arquivo exatamente como: `service-worker.js`.
+6. Clique  no botão `Criar`.
+7. Programe a funcionalidade.
+8. Clique em `Salvar`.
 
-Apesar do arquivo se encontrar em `/files/service-worker.js`, ele recebe o header `Service-Worker-Allowed` com valor `/`, o que permite interceptar requests da raiz do site.
+Apesar do arquivo se encontrar em `/arquivos/service-worker.js`, ele recebe o header `Service-Worker-Allowed` com valor `/`, o que permite interceptar requests da raiz do site.
 
-Para [maiores informações](https://developers.google.com/web/fundamentals/primers/service-workers/), consulte o Web Fundamentals, do Google Developers. 
+Para maiores informações, consulte o [Web Fundamentals](https://developers.google.com/web/fundamentals/primers/service-workers/), do Google Developers.
 
 ### Artigos relacionados
 
 - [Como transformar o site da minha loja em um PWA](https://help.vtex.com/pt/tutorial/como-transformar-o-site-da-minha-loja-em-um-pwa--3i8VmYeToAUGKgo2kKK6I2)
+
diff --git a/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md b/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md
index 19ffc72c0..f9a345fe5 100644
--- a/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md
+++ b/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md
@@ -38,7 +38,7 @@ Feito isso, sua plataforma VTEX terá a nova aba VTEX Tracking liberada no menu
 
 A integração entre sua loja no Admin da VTEX, e a app VTEX Tracking depende de algumas configurações. Confira abaixo as configurações necessárias para que seu serviço VTEX Tracking seja ativado, e o passo a passo para acessar o menu de Configurações. 
 
-![VTEX Tracking app install](https://images.ctfassets.net/alneenqid6w5/2TreUSwOkfK0VVTLxHLFpi/a6005d9583994252ea385c55bd1a35a6/VTEX_Tracking_app_install.jpg) 
+![VTEX Tracking app install](//images.ctfassets.net/alneenqid6w5/2TreUSwOkfK0VVTLxHLFpi/a6005d9583994252ea385c55bd1a35a6/VTEX_Tracking_app_install.jpg) 
 
 1. No Admin VTEX, acesse **Aplicativos > Apps instalados > VTEX Tracking**, ou digite **VTEX Tracking** na barra de busca no topo da página.
 2. Digite o **Token da API** na caixa de texto.  
diff --git a/docs/tutorials/pt/how-to-integrate-an-external-gift-card-provider-with-vtex.md b/docs/tutorials/pt/how-to-integrate-an-external-gift-card-provider-with-vtex.md
index 7edfdb927..307549195 100644
--- a/docs/tutorials/pt/how-to-integrate-an-external-gift-card-provider-with-vtex.md
+++ b/docs/tutorials/pt/how-to-integrate-an-external-gift-card-provider-with-vtex.md
@@ -3,8 +3,8 @@ title: 'Como integrar um provedor de Gift Card externo à VTEX'
 id: tutorials_450
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:26.566Z
-updatedAt: 2023-04-13T12:40:41.423Z
-publishedAt: 2023-04-13T12:40:41.423Z
+updatedAt: 2024-06-04T18:55:35.271Z
+publishedAt: 2024-06-04T18:55:35.271Z
 firstPublishedAt: 2017-04-27T23:03:24.938Z
 contentType: tutorial
 productTeam: Financial
@@ -15,22 +15,18 @@ legacySlug: integrando-com-gift-card
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, uma das opções de uso do Gift Card é ser utilizado como um programa de créditos. 
+Na VTEX, uma das opções de uso do gift card é ser utilizado como um programa de créditos. 
 
 Nesse contexto, existem alguns casos de clientes que já trabalham com um provedor próprio. Esse sistema gerencia sua relação de créditos ou pontos sob uma base de clientes participantes de um sistema de fidelidade, por exemplo.
 
-Dito isto, o cliente tem a opção de integrar a solução externa ao sistema da VTEX. Aqui, explicaremos o passo a passo para realizar essa integração.
+Caso o cliente deseje integrar um solução externa de gift card ao sistema da VTEX, é necessário utilizar o [Giftcard Provider Protocol](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol).
 
-## Desenvolvimento do provider
-A VTEX conta com Gift Card Provider Protocol. Ou seja, um guia de chamadas de API que serão feitas para se comunicar com o nosso sistema.
+## Desenvolvimento do provedor
 
-Desse modo, o cliente deve desenvolver um middleware - sistema que faz o intermédio entre dois sistemas diferentes-, no caso, o provedor externo e os sistemas da VTEX.
+Por meio do [Giftcard Provider Protocol](https://developers.vtex.com/docs/api-reference/giftcard-provider-protocol), o provedor externo de gift card deve desenvolver um [middleware](https://pt.wikipedia.org/wiki/Middleware) para transmitir as informações entre o seu sistema e a VTEX.
 
-Logo, uma vez implementado, será capaz de receber as chamadas da VTEX e interpretar as informações contidas em cada uma delas.
+Para mais informações sobre o sistema de gift card na VTEX, acesse [Giftcard Hub](https://developers.vtex.com/docs/api-reference/giftcard-hub-api).
 
-Para saber mais detalhes, consulte a nossa documentação técnica sobre o [Gift Card Provider Protocol](https://developers.vtex.com/docs/guides/giftcard-provider-protocol-overview). 
+## Envio de informações dos endpoints
+Após a conclusão do middleware, o provedor deve abrir um [ticket](https://help.vtex.com/pt/support) na VTEX informando os endpoints a serem utilizados para que os clientes realizem transações de pagamento utilizando o seu sistema de gift card.
 
-## Envio do endpoint
-Finalizada a primeira etapa, o cliente deve enviar para a VTEX o endpoint que será utilizado para realizar as chamadas. Essa rota funcionará como uma ponte entre os dois sistemas. 
-
-Por fim, a VTEX cadastra o endpoint do provedor no seu sistema. Assim, o sistema de Gift Card externo estará integrado à VTEX e será é utilizado em todo fechamento de compra em que o cliente utilizá-lo como meio de pagamento.
diff --git a/docs/tutorials/pt/how-to-manage-subscriptions.md b/docs/tutorials/pt/how-to-manage-subscriptions.md
index 1bdf5fd41..34fab6167 100644
--- a/docs/tutorials/pt/how-to-manage-subscriptions.md
+++ b/docs/tutorials/pt/how-to-manage-subscriptions.md
@@ -3,8 +3,8 @@ title: 'Como gerenciar Assinaturas'
 id: 6Jk50FPbv6iuz1OsFypv8x
 status: PUBLISHED
 createdAt: 2020-02-05T14:18:54.781Z
-updatedAt: 2022-12-05T16:48:31.127Z
-publishedAt: 2022-12-05T16:48:31.127Z
+updatedAt: 2023-12-21T14:08:39.725Z
+publishedAt: 2023-12-21T14:08:39.725Z
 firstPublishedAt: 2020-02-11T14:56:17.333Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -35,22 +35,26 @@ A seção **Assinaturas Únicas** permite:
 - Visualizar um **gráfico dinâmico** com a relação entre assinaturas ativas, canceladas e o total de assinaturas, dentro do período filtrado. Passando o cursor em cima das linhas do gráfico, é possível ver com detalhes a movimentação de assinaturas por dia.
 - **Exportar assinaturas** únicas dentro do período filtrado, pelo botão no canto superior direito da tela.
 
- ![PT Dashboard Assinatura única](https://images.ctfassets.net/alneenqid6w5/Dbqw5LPyrXvpT3tElkIXY/89e5fa3647a3e02e5b399e464ce03003/PT_Dashboard_Assinatura___nica.png)
+ ![PT Dashboard Assinatura única](//images.ctfassets.net/alneenqid6w5/Dbqw5LPyrXvpT3tElkIXY/89e5fa3647a3e02e5b399e464ce03003/PT_Dashboard_Assinatura___nica.png)
 
 ### Pedidos de Assinatura
 
+<div class = "alert alert-info">
+É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
+</div>
+
 A seção **Pedidos de Assinatura** permite:
 
 - Filtrar a visualização do **Funil de Pedidos de Assinatura** por período, podendo aplicar os seguintes filtros: `hoje`, `ontem`, `esta semana`, `este mês`, `este ano`, `semana passada`, `mês passado`, `ano passado`, ou um período `personalizado`, selecionando datas específicas.   
 - Acompanhar o número absoluto e porcentagem correspondente de Pedidos de Assinatura que foram agendados, processados, gerados e completos por período.  
 - Visualizar um gráfico com a porcentagem de pedidos pulados, ciclos com problema e erro de pagamento.  
 
-![PT Dashboard Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/20rYypV5vnYXo42CdCf0ms/3481a1af5bbee24d02b34a39ae03e723/PT_Dashboard_Pedidos_Assinatura.png)
+![PT Dashboard Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/20rYypV5vnYXo42CdCf0ms/3481a1af5bbee24d02b34a39ae03e723/PT_Dashboard_Pedidos_Assinatura.png)
 
 - Ao acessar cada aba do quadro **Pedidos de Assinatura**, é possível visualizar o fluxo e detalhes dos pedidos que foram Pulados, os que apresentaram Ciclos com problema, aqueles que contém um Erro de Pagamento e pedidos Completos.    
 - Além de listar detalhes dos erros que ocorreram durante  o fluxo de pedidos de Assinatura, também é possível realizar a **retentativa manual** dos pedidos com erros. Confira nosso artigo sobre a [Resolução de problemas de pedidos com Assinatura](https://help.vtex.com/pt/tutorial/como-solucionar-pedidos-de-assinatura-com-erros--uLL8AYBGdtAmbbdL5gRCf) para saber mais. 
 
-![PT Log Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/77DV2slShCKyXY0pKJyTl2/b1e8ed161f7be8bdbf417a68c058a268/PT_Log_Pedidos_Assinatura.png)
+![PT Log Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/77DV2slShCKyXY0pKJyTl2/b1e8ed161f7be8bdbf417a68c058a268/PT_Log_Pedidos_Assinatura.png)
 
 ### Assinantes
 
diff --git a/docs/tutorials/pt/how-to-manage-the-kit-stock.md b/docs/tutorials/pt/how-to-manage-the-kit-stock.md
index cedcbc3f2..918761068 100644
--- a/docs/tutorials/pt/how-to-manage-the-kit-stock.md
+++ b/docs/tutorials/pt/how-to-manage-the-kit-stock.md
@@ -3,8 +3,8 @@ title: 'Gerenciar estoque do kit'
 id: frequentlyAskedQuestions_156
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.252Z
-updatedAt: 2019-12-31T15:26:27.183Z
-publishedAt: 2019-12-31T15:26:27.183Z
+updatedAt: 2024-04-29T13:09:03.955Z
+publishedAt: 2024-04-29T13:09:03.955Z
 firstPublishedAt: 2019-01-24T22:03:46.311Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,12 +25,10 @@ Normalmente é um kit que no centro de distribuição da loja já encontra-se
 
 O Kit com componentes baseia-se em um produto kit que possui um SKU que é um “agrupamento” de outros SKUs. Este tipo normalmente é usado quando o kit é constituído de outros produtos que já encontram-se na loja e são vendidos separadamente por origem. Isto é, são selecionados os SKUs da loja e indicados quais serão o preço e o estoque necessários de cada SKU para compor 1 kit deste produto.
 
-![](//images.contentful.com/alneenqid6w5/42WZMhNkPSaq2mCkQSQI0G/4c411361196ea8d24a8a1a08aabfa783/kit.png)
-
-No exemplo acima, o produto kit de nome **Colorido** é composto por outros 10 SKUs. Cada um com sua quantidade necessária de 1 item de cada SKU para poder compor o KIT.
+Por exemplo, o produto kit de nome Colorido é composto por outros 10 SKUs. Cada um com sua quantidade necessária de 1 item de cada SKU para poder compor o KIT.
 
 ![](//images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
 
-Logo, se cada componente tiver 1 unidade em estoque, o kit estará em estoque, pois **depende do estoque cadastrado em cada um de seus componentes**.
+Se cada componente tiver 1 unidade em estoque, o kit estará em estoque, pois depende do estoque cadastrado em cada um de seus componentes.
 
 A quantidade em estoque do kit é a quantidade máxima possível que pode obtida com a quantidade de itens disponíveis.
diff --git a/docs/tutorials/pt/how-to-manually-invoice-an-order.md b/docs/tutorials/pt/how-to-manually-invoice-an-order.md
index b2982b93e..bba6ceada 100644
--- a/docs/tutorials/pt/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/pt/how-to-manually-invoice-an-order.md
@@ -3,8 +3,8 @@ title: 'Como faturar um pedido'
 id: 7p1h852V5t54KyscpgxE2v
 status: PUBLISHED
 createdAt: 2020-12-28T20:50:42.445Z
-updatedAt: 2023-05-31T14:44:54.458Z
-publishedAt: 2023-05-31T14:44:54.458Z
+updatedAt: 2024-04-01T17:55:58.671Z
+publishedAt: 2024-04-01T17:55:58.671Z
 firstPublishedAt: 2020-12-28T21:01:55.107Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,7 +21,7 @@ Faturar o pedido na plataforma VTEX significa inserir a nota fiscal dos itens no
 
 É preciso faturar o pedido para que a nota fiscal fique disponível para o cliente e o [fluxo do pedido](https://help.vtex.com/pt/tutorial/fluxo-de-pedido--tutorials_196) chegue ao fim. O envio da fatura pode ser feito:
 
-* Via [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice) de envio de fatura
+* Via [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice) de envio de fatura.
 * Via Admin VTEX.
 
 <div class = "alert alert-info">
@@ -34,7 +34,7 @@ Para enviar a fatura pelo Admin VTEX, realize os seguintes passos:
 2. Busque o pedido pela barra de busca ou [utilizando os filtros](https://help.vtex.com/pt/tutorial/como-filtrar-pedidos--tutorials_192).  
 3. Clique no pedido desejado.     
 4. Na seção **Itens para faturar,** clique no ícone de seta <i class="fas fa-chevron-right"></i> para expandir.
-![Itens faturar](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/21fe424a4a5bcb066384dc79f99cf953/Itens_faturar__3_.png)
+![Itens faturar](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/21fe424a4a5bcb066384dc79f99cf953/Itens_faturar__3_.png)
 5. Clique no botão `Faturar`.   
 6. Clique na opção de faturamento desejada:    
     * **Enviar fatura referenciando itens:** para faturar o pedido referenciando os itens do pacote.    
@@ -64,7 +64,8 @@ Para enviar a fatura pelo Admin VTEX, realize os seguintes passos:
 
 Depois do pedido `Faturado`, confira as notas fiscais inseridas na seção **Fatura**, como apresentado na figura abaixo:
 
-![Fatura](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
+![Fatura](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
 
 Em casos de envios de [faturas parciais](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe), ao [alterar ou remover itens](https://help.vtex.com/pt/tutorial/how-to-change-order-items--7jekq618QxgbsOxKkXBjE8) de um pedido, o valor total do pedido será atualizado após o faturamento, e corresponde ao que é captado pelo gateway de pagamentos da VTEX.
 
+Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
diff --git a/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md b/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md
index 3fb1b45ed..88f1b445f 100644
--- a/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md
+++ b/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md
@@ -3,8 +3,8 @@ title: 'Modificar as informações de endereço de clientes'
 id: 3IQsuOvkMgmuwWQMQoo8UM
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:49.820Z
-updatedAt: 2023-03-28T22:57:51.457Z
-publishedAt: 2023-03-28T22:57:51.457Z
+updatedAt: 2024-06-06T20:47:33.052Z
+publishedAt: 2024-06-06T20:47:33.052Z
 firstPublishedAt: 2019-01-24T22:10:21.264Z
 contentType: tutorial
 productTeam: Master Data
@@ -18,12 +18,12 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 Para editar as informações do cliente é necessário seguir os seguintes passos:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. Selecione a aba **Endereços**. Lá você vai encontrar todos os usuários que tenham registrado pelo menos um endereço.
+2. Clique na aba **Endereços**, onde você pode visualizar todos os usuários que tenham registrado pelo menos um endereço.
 3. Busque o cliente desejado.
-4. Na coluna **Ações** da tabela, clique na opção **Editar**.
+4. Na coluna **Ações** da tabela, clique no ícone de edição <i class="fas fa-edit"></i>.
 5. Crie ou edite as informações desejadas.
-6. Clique em **Salvar**.
-7. Em seguida, clique em **Voltar** para ver novamente a lista de endereços.
+6. Clique em `Salvar`.
+7. Em seguida, clique em `Voltar` para ver novamente a lista de endereços.
 
 <div class="alert alert-warning">
 Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
diff --git a/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
index 1460f9065..30e0ae5b2 100644
--- a/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
@@ -1,10 +1,10 @@
 ---
 title: 'Otimizar as buscas com palavras substitutas'
 id: 32FqSsl5VuQyiIMEc02Uwu
-status: PUBLISHED
+status: CHANGED
 createdAt: 2019-01-24T20:45:49.707Z
-updatedAt: 2021-09-14T19:00:59.249Z
-publishedAt: 2021-09-14T19:00:59.249Z
+updatedAt: 2024-02-28T22:28:58.551Z
+publishedAt: 2024-01-10T13:30:55.078Z
 firstPublishedAt: 2019-01-24T22:00:22.364Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 ---
 
 <div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
+As operações da configuração <a href="https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palavras Substitutas</a> não são recomendadas para a sua loja em caso de utilização do Intelligent Search. Para relacionar palavras ao produto, é recomendada a utilização da configuração de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Sinônimos</a>, que possibilita uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.
 </div>
 
 ## Como funciona o buscador
@@ -39,15 +39,15 @@ Um recurso muito utilizado para agilizar as buscas da equipe interna é colocar
 
 ### 1. Integração de produtos
 Integrar os produtos mediante o webservice ProductInsertUpdate permite agregar suas Palavras Substitutas e associá-las ao produto em questão:
-<http://help.vtex.com/pt/tutorial/manual-das-classes-e-metodos-usados-no-webservice>
+[](http://help.vtex.com/pt/tutorial/manual-das-classes-e-metodos-usados-no-webservice)
 
 ### 2. Importação por planilha
 Carregar as Palavras Substitutas diretamente por planilha de produto, de modo massivo:
-<https://help.vtex.com/pt/tutorial/cadastrando-produto#importacao-de-produtos-por-planilha>
+[](https://help.vtex.com/pt/tutorial/cadastrando-produto#importacao-de-produtos-por-planilha)
 
 ### 3. Editar um produto
 Carregar as Palavras Substitutas diretamente a cada produto individualmente no campo “Palavras Substitutas”:
-<https://help.vtex.com/pt/tutorial/cadastrando-produto#cadastrando-produto-pelo-admin>
+[](https://help.vtex.com/pt/tutorial/cadastrando-produto#cadastrando-produto-pelo-admin)
 
 ## Onde consigo palavras substitutas
 ### Google Trends
diff --git a/docs/tutorials/pt/how-to-request-receivables-anticipation.md b/docs/tutorials/pt/how-to-request-receivables-anticipation.md
index fd3877a04..7554f0f51 100644
--- a/docs/tutorials/pt/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/pt/how-to-request-receivables-anticipation.md
@@ -31,7 +31,7 @@ Agora que você já conferiu o saldo, é importante ter em mente que o valor mí
 
 Por exemplo, caso o seu menor recebível seja de R$10, esse é o valor mínimo que você pode antecipar. Já o valor máximo é informado no próprio Admin - o saldo que você acabou de conferir - na página de “Antecipar recebíveis”. 
 
-![image](https://images.ctfassets.net/alneenqid6w5/oWY3RyEekfyjuBEjI27m3/18aba6b309f1acb3f945100927d25ead/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/oWY3RyEekfyjuBEjI27m3/18aba6b309f1acb3f945100927d25ead/image.png)
 
 <div class="alert alert-info">
 <strong>Atenção</strong>: recebíveis em disputa ou previstos para o próximo dia útil não podem ser antecipados.
diff --git a/docs/tutorials/pt/how-to-return-order-items.md b/docs/tutorials/pt/how-to-return-order-items.md
index 5362e307a..375fe4bec 100644
--- a/docs/tutorials/pt/how-to-return-order-items.md
+++ b/docs/tutorials/pt/how-to-return-order-items.md
@@ -3,8 +3,8 @@ title: 'Como devolver itens do pedido'
 id: 2bSNWwD0g8fcUmuupLao9i
 status: PUBLISHED
 createdAt: 2020-12-28T21:23:42.045Z
-updatedAt: 2023-04-11T14:58:43.881Z
-publishedAt: 2023-04-11T14:58:43.881Z
+updatedAt: 2024-06-10T23:02:44.957Z
+publishedAt: 2024-06-10T23:02:44.957Z
 firstPublishedAt: 2020-12-28T21:27:16.332Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,7 +26,7 @@ A página de **Detalhes do Pedido** permite orquestrar essa operação, seguindo
 3. Na seção **Notas Fiscais**, clique em `Devolver Itens`.
 4. Selecione os itens que serão devolvidos marcando a caixa de seleção.  
 5. Defina o número de unidades a serem devolvidas de cada item.  
-6. Insira o valor adicional a ser cobrado do seu cliente no campo `Valor Adicional`. Esse valor é referente ao custo de envio do pedido devolvido.
+6. Insira o valor adicional a ser devolvido ao seu cliente no campo `Valor Adicional`. Esse valor é referente ao custo de envio do pedido devolvido.
     > Por exemplo, se um pedido teve o custo de frete de R$ 20,00, você deve preencher esse campo com R$20,00. Caso seja preenchido com um valor menor que o valor total do frete, o cliente recebe metade do valor preenchido (no campo `Valor adicional`) como estorno da compra, e a outra metade em giftcard. Seguindo o exemplo dado, suponha que ao invés de R$20,00 (que é o valor total de custo do envio) a loja tenha preenchido o `Valor Adicional` como R$12,00. O cliente receberá a devolução desse valor na forma de um estorno de R$6,00 mais um giftcard de R$6,00.
 
     > *Este campo é opcional, e deve ser preenchido caso o valor adicional faça parte da política de devolução da sua loja.*
@@ -34,8 +34,12 @@ A página de **Detalhes do Pedido** permite orquestrar essa operação, seguindo
 7. Insira o motivo do valor adicional, no campo `Referido a`.
     > *Este campo é opcional, e deve ser preenchido caso o valor adicional faça parte da política de devolução da sua loja.*    
 8. Insira o código da `nota fiscal de entrada`.
-    > *Se refere à nota fiscal de devolução, quando o item retorna ao seu estoque.*  
+    > *Se refere à nota fiscal de devolução, quando o item retorna ao seu estoque. É necessário que o número da nota fiscal da devolução seja diferente da nota fiscal anterior.*  
 9. Comente o `Motivo da Devolução`.  
 10. Clique em `Solicitar Reembolso`.  
 
 Após o reembolso ser processado pelo sistema, os itens devolvidos e suas informações aparecerão na seção **Itens Devolvidos**.
+
+<div class = "alert alert-info">
+A alteração de pedidos via API é feita pelo endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> e a emissão de faturas após alterações é feita pelo endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice">Order invoice notification</a>.
+</div>
diff --git a/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md b/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md
index 14cbaad59..4ef98772b 100644
--- a/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md
+++ b/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md
@@ -20,7 +20,7 @@ Na seção de __Gerenciamento de pedidos__ é possível filtrar os pedidos feito
 Se quiser ver os pedidos que foram fechados tendo uma promoção aplicada, basta seguir os passos abaixo:
 
 1. No menu do admin, clique em __Gerenciamento de pedidos__
-2. Clique no botão de filtro e, dentro da seção __Outros__, clique na opção __Promoções__![promo-filter-pt](https://images.ctfassets.net/alneenqid6w5/6LYRvwnDy08eWII6WqUqSC/dcd40f276c57870a2c91c47261d593ea/promo-filter-pt.png)
+2. Clique no botão de filtro e, dentro da seção __Outros__, clique na opção __Promoções__![promo-filter-pt](//images.ctfassets.net/alneenqid6w5/6LYRvwnDy08eWII6WqUqSC/dcd40f276c57870a2c91c47261d593ea/promo-filter-pt.png)
 3. Selecione a promoção desejada e clique em __Confirme__
 
 Na lista de pedidos, você verá todos os pedidos fechados com essa promoção.
diff --git a/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md b/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
index e6c42053b..865f60095 100644
--- a/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
+++ b/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
@@ -29,7 +29,7 @@ Basta incluir um atributo com o nome `salesChannel`, conforme ilustrado na rota
 
 A partir de então, os próximos pedidos serão criados com o canal de vendas configurado. Caso não tenha estoque para determinado item neste canal o item será excluido do pedido.   
 
-![posicao.pt](https://images.ctfassets.net/alneenqid6w5/7aFEnASwXi9emVUzKJr4pm/8c5f2727be50812817612850e19769cb/posicao.pt.png)
+![posicao.pt](//images.ctfassets.net/alneenqid6w5/7aFEnASwXi9emVUzKJr4pm/8c5f2727be50812817612850e19769cb/posicao.pt.png)
 
 *Tela onde se encontra o ID do salesChannel*
 
@@ -39,6 +39,6 @@ Basta incluir um atributo com o nome `defaultSLA`, conforme ilustrado na rota d
 
 A partir de então, SLA configurado terá precedência sobre o SLA mais barato para os próximos pedidos que serão criados - sendo que se este possuir uma janela de entrega, será selecionado o primeiro intervalo disponível.
 
-![transportadora.pt](https://images.ctfassets.net/alneenqid6w5/1NuCXhjhtIOiYBhtLev1ed/da96b6ce00fdc241f96d81e3184c194f/transportadora.pt.png)
+![transportadora.pt](//images.ctfassets.net/alneenqid6w5/1NuCXhjhtIOiYBhtLev1ed/da96b6ce00fdc241f96d81e3184c194f/transportadora.pt.png)
 
 *Tela onde se encontra o ID do SLA*
diff --git a/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
index 47f855ffa..00e8bbd7a 100644
--- a/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
@@ -91,7 +91,7 @@ Uma vez que já configuramos a etiqueta, temos que salvar o JS chamado a partir
 
 - Acessando o painel VTEX no menu CMS >> Layout >> Files Manager >> Gerenciamento de arquivo .js >> Add.
 
-![cms js](https://images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
+![cms js](//images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
 
 __Anexo__: [md5.js](//assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
 
diff --git a/docs/tutorials/pt/how-to-set-up-recurrence-in-payment-conditions.md b/docs/tutorials/pt/how-to-set-up-recurrence-in-payment-conditions.md
index dec6dd16a..83708d997 100644
--- a/docs/tutorials/pt/how-to-set-up-recurrence-in-payment-conditions.md
+++ b/docs/tutorials/pt/how-to-set-up-recurrence-in-payment-conditions.md
@@ -3,8 +3,8 @@ title: 'Configurar recorrência em condições de pagamento'
 id: 6EGuoAytLqU2CqUuaI2GUW
 status: PUBLISHED
 createdAt: 2017-06-29T20:56:04.718Z
-updatedAt: 2023-03-30T15:57:59.484Z
-publishedAt: 2023-03-30T15:57:59.484Z
+updatedAt: 2024-01-09T19:47:20.977Z
+publishedAt: 2024-01-09T19:47:20.977Z
 firstPublishedAt: 2017-07-03T15:16:40.562Z
 contentType: tutorial
 productTeam: Financial
@@ -26,7 +26,7 @@ Depois de realizar esta configuração podemos marcar as condições especiais e
 2. Clicar na aba **Condições de pagamento**.
 3. Clicar na condição de pagamento criada.
 4. Clicar em **Adicionar condição especial**.
-5. Escolher a opção **Período**.
+5. Escolher a opção **Data de vencimento**.
 6. Marcaremos a faixa de dias para a validade da condição de pagamento em **Apenas para o período**.
 7. Abaixo do período, vemos o campo **Recorrência**. Ali podemos selecionar **Todos os dias** ou (Desativando a opção “Todos os dias”) podemos selecionar **os dias da semana** desejados; também podemos configurar uma hora de início e uma hora de término.
 8. Se quisermos acrescentar outra **Recorrência** devemos clicar no botão `+`.
diff --git a/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 00e39f972..469818224 100644
--- a/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar o conector para aceitar pagamentos com Adyen na VTEX'
 id: tutorials_2337
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:55:10.101Z
-updatedAt: 2023-03-24T14:56:13.138Z
-publishedAt: 2023-03-24T14:56:13.138Z
+updatedAt: 2024-03-18T17:52:42.714Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:52.166Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: como-configurar-o-gateway-adyen-na-vtex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 <div class="alert alert-warning">As configurações documentadas neste artigo são realizadas em um ambiente externo à VTEX. Portanto, podem ser descontinuadas sem prévio aviso.</div>
 
 Caso o seu processador de pagamentos escolhido seja a Adyen, siga o passo a passo abaixo com a configuração necessária para que a comunicação entre VTEX e Adyen funcione perfeitamente.
@@ -75,7 +77,7 @@ Em seguida, é só recolher as informações da Adyen para cadastrar na VTEX. Ai
 
 7. Depois destes passos, seu usuário deverá ter sido criado com sucesso. O número 1 (indicado na imagem em vermelho) é o username. Já o número 2 é a senha (password) que deverá ser inserida no ambiente VTEX.
 
-    ![Adyen - Image 2](https://images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
+    ![Adyen - Image 2](//images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
 
 8. Envie um e-mail para o suporte da Adyen (suporte@adyen.com) solicitando as habilitações listadas no modelo abaixo:
 
@@ -102,16 +104,13 @@ Se você pretende usar a plataforma da Adyen para fazer análise antifraude com
 
 <ui>5. A configuração deverá parecer conforme abaixo. Não esqueça de clicar em **Save configuration** após concluir as alterações.</ui>
 
-![Adyen - Image 1](https://images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
+![Adyen - Image 1](//images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
 
 ## Configurações na VTEX
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-
-2. Clique em **Afiliações de Gateway**.
-
-3. Clique em **Adyen**.
-
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Adyen__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos do formulário com os dados obtidos na Adyen e clique no botão **Salvar**:
 
 - **username** - username Adyen (instrução 5 das **Configurações na Adyen**)
diff --git a/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
index 32186101e..b9b410d42 100644
--- a/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -68,6 +68,6 @@ Preencha com o seguinte código HTML:
 <script src="https://h.online-metrix.net/fp/check.js?org_id={{cs_orgId}}&amp;session_id={{cs_merchantId}}{{cs_sessionId}}" type="text/javascript"></script>
 ```
 
-![braspag fingerprint](https://images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/c023534e5c43d1f5fd06ebf9e13dcac6/image.png)
+![braspag fingerprint](//images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/c023534e5c43d1f5fd06ebf9e13dcac6/image.png)
 
 Por fim, publique as alterações.
diff --git a/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
index ccf676ca2..544e273e0 100644
--- a/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -31,7 +31,7 @@ O consumidor realiza o agendamento por meio de um formulário preparado pela Ind
 
 O fluxo de agendamento percorrido pelo cliente se inicia na escolha da loja física onde ele deseja ser atendido. Na imagem abaixo, vemos apenas uma loja cadastrada. Mas você pode cadastrar quantas lojas físicas desejar.
 
-![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
+![indeva1](//images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
 <div class="alert alert-info">
 É possível também fornecer ao cliente um link que conduz diretamente ao formulário de uma loja física específica. Basta adicionar o ID da loja ao final da URL. Dessa forma, o vendedor pode compartilhar o link de sua loja – por exemplo, por meio de um QR Code ou nas mídias sociais.
@@ -48,7 +48,7 @@ Ao clicar na loja desejada, o cliente é levado ao formulário. Ali, ele encontr
 
 Por fim, basta o cliente clicar em Agendar horário. Com isso, essa visita entrará na fila de agendamentos mostrados pelo aplicativo dos vendedores.
 
-![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
+![indeva2](//images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
 <div class=”alert alert-warning”>
 Por enquanto, a confirmação do agendamento deve ser feita manualmente pela loja. O cliente não receberá nenhuma mensagem automática.
@@ -58,13 +58,13 @@ Por enquanto, a confirmação do agendamento deve ser feita manualmente pela loj
 
 A app do Indeva Store organiza a fila de agendamentos realizados para cada loja física. Ele pode ser usado por vendedores ou gerentes para controle tanto dos próximos agendamentos quanto para visualização do histórico de visitas já atendidas.
 
-![indeva3](https://images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
+![indeva3](//images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
 
 Ao clicar em um agendamento específico, o vendedor tem acesso aos detalhes desse agendamento: data e horário da visita, nome do cliente, mensagem enviada por ele, quantidade de pessoas e o número de telefone do cliente.
 
 Se quiser entrar em contato com o cliente a partir dessa tela, o vendedor pode clicar no botão Abrir Whatsapp. Ele será levado diretamente para uma conversa com aquele cliente específico no aplicativo de mensagens.
 
-![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
+![indeva4](//images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
 <div class=”alert alert-info”>
 O aplicativo pode ser instalado em diversos dispositivos da mesma loja, mas recomendamos que sua equipe use um aplicativo por loja, e não por vendedor.
@@ -115,7 +115,7 @@ O app para os vendedores e gerentes da loja está disponível tanto para Android
 
 Após instalar e abrir o aplicativo, o vendedor deverá informar o token de 10 dígitos da loja para sincronizar o dispositivo e fazer o login.
 
-![indeva5](https://images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
+![indeva5](//images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
 
 Para receber o token, entre em contato com o time da Indeva pelos canais de suporte:
 - __Telefone__: (21)3609-2830
diff --git a/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index 1fb3a5a29..b9dbfad7d 100644
--- a/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -3,8 +3,8 @@ title: 'Como configurar o campo "Responsável pela retirada" no SmartCheckout™
 id: 2GsFnXUJxSOYEE6U2c4Syw
 status: PUBLISHED
 createdAt: 2018-11-09T12:18:14.596Z
-updatedAt: 2023-03-23T19:34:48.154Z
-publishedAt: 2023-03-23T19:34:48.154Z
+updatedAt: 2023-07-27T17:07:55.563Z
+publishedAt: 2023-07-27T17:07:55.563Z
 firstPublishedAt: 2018-11-26T14:43:00.552Z
 contentType: tutorial
 productTeam: Shopping
@@ -22,7 +22,7 @@ O campo <strong>Responsável pela retirada</strong> só está disponível para o
 Os [pontos de retirada](/pt/tutorial/configurar-pontos-de-retirada-pickup-points) dão mais uma opção aos seus clientes: ao invés de esperar a entrega, eles podem escolher ir até um ponto definido e buscar o item pessoalmente. Por default, essa ação está vinculada ao usuário cadastrado que efetuou a compra. No entanto, você pode habilitar o campo `Responsável pela retirada` no checkout da sua loja, para que seu cliente possa nomear outra pessoa para retirar o produto.
 
 <div class="alert alert-warning">
-Caso você possua o app <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> instalado em sua loja, o código CSS descrito no procedimento abaixo deverá ser inserido somente via o app. Os scripts inseridos via interface do Admin (aba <b>Código > Files</b>) não são reproduzidos em lojas que possuem o aplicativo instalado.
+Caso você possua o app <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> instalado em sua loja, o código CSS descrito no procedimento abaixo deverá ser inserido somente via o app. Os scripts inseridos via interface do Admin VTEX (aba <b>Código > Files</b>) não são reproduzidos em lojas que possuem o aplicativo instalado.
 </div>
 
 Para configurar o campo (que vem desativado por padrão), siga os passos abaixo:
@@ -36,7 +36,7 @@ Para configurar o campo (que vem desativado por padrão), siga os passos abaixo:
 
 ```
 .vtex-omnishipping-1-x-container.shp-pickup-receiver{
-    display: block;
+    display: block !important;
 }
 ```
 
diff --git a/docs/tutorials/pt/how-to-set-up-the-zoom.md b/docs/tutorials/pt/how-to-set-up-the-zoom.md
index 33873e074..de3868631 100644
--- a/docs/tutorials/pt/how-to-set-up-the-zoom.md
+++ b/docs/tutorials/pt/how-to-set-up-the-zoom.md
@@ -22,7 +22,7 @@ _Se você já possui essa configuração ativa mas está com alguns problemas ve
 
 Abaixo um passo-a-passo de como configurar e implementar esta funcionalidade.
 
-![zoom-configurações](https://images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
+![zoom-configurações](//images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
 
 ## Configurando o CSS
 
@@ -36,7 +36,7 @@ Abaixo reproduzimos um trecho de CSS que você pode utilizar como ponto de parti
 
 Em seguida, vamos enviar o arquivo CSS salvo para o servidor. Para isso, acesse no menu **CMS** > Acesse **Layout** > Entre na pasta **CMS** > Entre em **Files Manager** > Entre em **.css** > Na janela que se abrirá à direita, clique no botão **Add**.
 
-![add-cms-.css ](https://images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
+![add-cms-.css ](//images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
 
 Em seguida, localize o arquivo CSS salvo acima e envie-o para o servidor clicando no botão **Localizar** e em seguida no botão **Salvar arquivo**; dessa forma, seu arquivo aparecerá listado como mostra a imagem acima. 
 
@@ -54,4 +54,4 @@ Agora basta inserir `zoom="on"` na tag do produto, conforme abaixo:
 É necessário configurar o tamanho padrão da imagem de zoom. Você pode definir isso em **CMS** > **Configurações** > **Tipos de Arquivos**.
 Por padrão, esse tipo de imagem de zoom vem configurada com 1000×1000 pixels.
 
-![zoom-tiposdearquivo pt](https://images.ctfassets.net/alneenqid6w5/3kUqg5mLCUkewseUmA0yK2/cb469406f4cec605ed3e05d9ec487c23/zoom_tipos_de_arquivo.png)
+![zoom-tiposdearquivo pt](//images.ctfassets.net/alneenqid6w5/3kUqg5mLCUkewseUmA0yK2/cb469406f4cec605ed3e05d9ec487c23/zoom_tipos_de_arquivo.png)
diff --git a/docs/tutorials/pt/how-to-set-up-visa-debit.md b/docs/tutorials/pt/how-to-set-up-visa-debit.md
index 4dc9dd0b5..39c51b1f4 100644
--- a/docs/tutorials/pt/how-to-set-up-visa-debit.md
+++ b/docs/tutorials/pt/how-to-set-up-visa-debit.md
@@ -22,7 +22,7 @@ Para realizar a configuração o pagamento por Visa Débito em sua loja, no Admi
 Em primeiro lugar, devemos criar uma condição de pagamentos para habilitar o Visa Débito no Checkout.
 Para isso, em **Configurações** acesse o menu de opções de **Condições de pagamento**:
 
-![visa debito](https://images.ctfassets.net/alneenqid6w5/4oOYYq29TmER7mOldlakl2/ba1eefbd08406217ce0567d3dc18d21f/visa_debito.png)
+![visa debito](//images.ctfassets.net/alneenqid6w5/4oOYYq29TmER7mOldlakl2/ba1eefbd08406217ce0567d3dc18d21f/visa_debito.png)
 
 Selecione Visa Electron para criar a condição de pagamento:
 
@@ -32,7 +32,7 @@ Selecione Visa Electron para criar a condição de pagamento:
 
 Deve-se selecionar a afiliação desejada para transacionar os pagamentos, ativar a condição de pagamentos e finalmente salvar as mudanças:
 
-![visa debito.2](https://images.ctfassets.net/alneenqid6w5/3IC7m6dgtk2t7jjVKhQTkJ/330c8f3b81c16501f52a619874c84349/visa_debito.2.png)
+![visa debito.2](//images.ctfassets.net/alneenqid6w5/3IC7m6dgtk2t7jjVKhQTkJ/330c8f3b81c16501f52a619874c84349/visa_debito.2.png)
 
 ### Visualizando os cartões de débito no Checkout
 
diff --git a/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md b/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md
index 26261bbeb..02ebacc5b 100644
--- a/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md
+++ b/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Primeiros Passos do seller'
 id: 6w1vBdRH2uuBGmUqgNQjwK
 status: PUBLISHED
 createdAt: 2021-01-26T15:08:22.524Z
-updatedAt: 2023-03-02T21:29:12.945Z
-publishedAt: 2023-03-02T21:29:12.945Z
+updatedAt: 2024-05-30T22:41:41.434Z
+publishedAt: 2024-05-30T22:41:41.434Z
 firstPublishedAt: 2021-09-15T20:50:27.452Z
 contentType: tutorial
 productTeam: Channels
@@ -37,7 +37,6 @@ Por meio do Seller Portal, sellers conseguem:
 
 Saiba alguns detalhes sobre o Seller Portal:   
 
-- Somente marketplaces poderão criar e gerenciar promoções sobre produtos.  
 - A arquitetura do catálogo pode ser compartilhada entre marketplace e seller através do compartilhamento de produtos. O seller, no entanto, pode criar seus próprios produtos, definindo categorias, marcas e especificações.
 - Quando o seller escolhe compartilhar o catálogo com o marketplace, os produtos compartilhados têm as mesmas categorias, marcas e especificações definidos pelo marketplace. No entanto, somente as categorias são importadas para o ambiente do seller de forma completa. As marcas são importadas somente quando um produto é importado e as especificações não são importadas.
 - Se o marketplace processar pagamentos, o comissionamento e repasse do faturamento do seller deverá ser feito por fora da VTEX.  
@@ -45,6 +44,8 @@ Saiba alguns detalhes sobre o Seller Portal:
 
 ## Configurar sua loja
 
+<div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+
 Para começar a vender seus produtos no marketplace, é preciso configurar a sua loja no Seller Portal. Este artigo explica o fluxo completo dessa configuração inicial e indica outras documentações para que você acesse cada passo em mais detalhes. A configuração básica do Seller Portal inclui os passos listados abaixo.
 
 ### 1. Catálogo
@@ -136,7 +137,16 @@ Para saber mais, confira os artigos abaixo:
 
 - [Como funcionam Pedidos na VTEX](https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa)
 
-### 8. Acompanhar Gestão de anúncios
+### 8. Criar e gerenciar promoções
+
+A página **Promoções** no Seller Portal permite que sellers e marketplaaces, criem promoções e gerenciem a lista completa de promoções cadastradas, simplificando a gestão de promoções.
+
+Para saber mais, confira os seguintes artigos:
+
+ - [Seller Portal: Promoções](https://help.vtex.com/pt/tutorial/seller-portal-promocoes--73LL7Ja0P4JbD77AH0jHwu)  
+  - [Seller Portal: Criar uma promoção](https://help.vtex.com/pt/tutorial/seller-portal-criar-uma-promocao--kzNPEaiJE8EWkDzO9dbBI)  
+
+### 9. Acompanhar Gestão de anúncios
 
 O módulo _Gestão de anúncios_ permite que sellers supervisionem o envio e a sincronização de anúncios em todos os canais integrados à loja. A página retrata, em tempo real, o status dos anúncios e suas atualizações a partir dos dados vindos do marketplace e de outros módulos VTEX. É onde sellers podem acompanhar todas as interações do tipo Catálogo, Preço ou Estoque, ocorridas com seus anúncios, para identificar erros durante seu envio e sincronização. 
 
@@ -146,7 +156,7 @@ Para saber mais, confira os seguintes artigos:
 - [Gestão de anúncios: detalhes do anúncio](https://help.vtex.com/pt/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P)  
 - [Gestão de anúncios: detalhes da interação](https://help.vtex.com/pt/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf)
 
-### 9. Dashboard Performance de Vendas
+### 10. Dashboard Performance de Vendas
 
 O menu _Dashboards_ é o painel de controle dos dados do seu comércio unificado. As análises trazidas aqui informam decisões e ajudam a priorizar tarefas de diferentes profissionais, desde a operação, até o comercial e marketing. Os dashboards incluem dados atualizados de todos os canais de venda em que sua loja opera com a VTEX, incluindo as principais métricas que impactam a receita da sua loja.
 
diff --git a/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md b/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md
index 492a4542c..9af32d91d 100644
--- a/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md
+++ b/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md
@@ -3,8 +3,8 @@ title: 'Configurar Google Analytics 4 em loja VTEX'
 id: G2P0rmSrEiqCcmUMyUUwG
 status: PUBLISHED
 createdAt: 2017-07-30T22:53:46.285Z
-updatedAt: 2023-05-03T16:21:13.207Z
-publishedAt: 2023-05-03T16:21:13.207Z
+updatedAt: 2023-07-17T13:35:10.259Z
+publishedAt: 2023-07-17T13:35:10.259Z
 firstPublishedAt: 2017-07-30T23:24:21.394Z
 contentType: tutorial
 productTeam: Others
@@ -36,5 +36,5 @@ Em ambos os casos, armazene o código de identificação da propriedade no Googl
 
 Feitas as configurações necessárias na sua conta Google Analytics, será preciso alterar as configurações do Google Tag Manager para detectar os eventos da sua loja. Para isso, siga os passos descritos em [Configurar o Google Tag Manager](https://help.vtex.com/pt/tutorial/integracao-com-o-google-tag-manager).
 
-Se a sua loja utiliza [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), além da configuração, será necessário configurar uma nova versão do app Google Tag Manager. Para mais informações, acesse [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+Se a sua loja utiliza [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), além da configuração, será necessário configurar uma nova versão do app Google Tag Manager. Para mais informações, acesse [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
diff --git a/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md b/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md
index 57cc9d085..b48b816f2 100644
--- a/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md
+++ b/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md
@@ -1,10 +1,10 @@
 ---
 title: 'Como transformar o site da minha loja em um PWA'
 id: 3i8VmYeToAUGKgo2kKK6I2
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-03-19T18:20:25.794Z
-updatedAt: 2023-03-29T13:18:46.962Z
-publishedAt: 2023-03-29T13:18:46.962Z
+updatedAt: 2024-05-07T14:04:52.042Z
+publishedAt: 2023-07-10T14:28:55.813Z
 firstPublishedAt: 2018-03-20T14:54:55.189Z
 contentType: tutorial
 productTeam: Others
@@ -24,8 +24,7 @@ PWA é a abreviação em inglês de Progressive Web App - um conjunto de técnic
 Se você já tem um site ou uma aplicação web, pode implementar aos poucos as características que definem um PWA, como notificações, cache de arquivos, execução em modo off-line e outras possibilidades que fazem o usuário se sentir em um aplicativo nativo.
 
 <div class="alert alert-warning">
-A plataforma VTEX <strong>não</strong> possui features nativas para transformar sua loja em PWA. Ela apenas oferece as condições para que essa implementação seja feita. Lojas desenvolvidas com o VTEX IO Store Framework possue este recurso nativamente.
-</div>
+A plataforma VTEX <strong>não</strong> possui features nativas para transformar sua loja em PWA. Ela apenas oferece as condições para que essa implementação seja feita. Lojas desenvolvidas com o VTEX IO Store Framework possuem este recurso nativamente.</div>
 
 ## O Google define com exatidão o que é esperado de um PWA:
 
@@ -66,7 +65,7 @@ __Para criar o JSON, siga o passo a passo abaixo:__
 
 __Seu arquivo deve ser importado no index.html, assim:__
 
-`<link rel="manifest" href="/files/manifest.json">`
+`<link rel="manifest" href="/arquivos/manifest.json">`
 
 Depois disso, sua aplicação web poderá abrir um splash screen exatamente igual aos apps nativos.
 
@@ -83,7 +82,7 @@ __Para criar o script, siga o passo a passo abaixo:__
 6.  Programe a funcionalidade.
 7.  Para finalizar, clique em __Salvar__.
 
-Apesar de o arquivo se encontrar em `/files/service-worker.js`, ele recebe o header `Service-Worker-Allowed` com valor `/`, o que permite interceptar requests da raiz do site.
+Apesar de o arquivo se encontrar em `/arquivos/service-worker.js`, ele recebe o header `Service-Worker-Allowed` com valor `/`, o que permite interceptar requests da raiz do site.
 
 ### Terceiro passo
 A forma fácil de saber se você está no caminho certo na construção do seu PWA é usar alguma ferramenta de inspeção, como o Lighthouse do Google.
diff --git a/docs/tutorials/pt/how-to-use-conditions-builder-app.md b/docs/tutorials/pt/how-to-use-conditions-builder-app.md
index 382042549..68f97ef1c 100644
--- a/docs/tutorials/pt/how-to-use-conditions-builder-app.md
+++ b/docs/tutorials/pt/how-to-use-conditions-builder-app.md
@@ -36,12 +36,12 @@ Depois de instalar, você pode acessá-lo da barra lateral (seção de apps inst
 4. (Opcional) Escreva uma pequena descrição para sua condição. Essa descrição é apenas para controle interno, não será visível aos seus clientes.
 5. Clique em "Começar a construir".
 
-![criarCondicao](https://images.ctfassets.net/alneenqid6w5/628KQZeFhY2GsQsgcEMmIm/2610dde91708bfbd304ea52458be6137/criarCondicao.gif)  
+![criarCondicao](//images.ctfassets.net/alneenqid6w5/628KQZeFhY2GsQsgcEMmIm/2610dde91708bfbd304ea52458be6137/criarCondicao.gif)  
 
 
 Depois de apertar o botão "Começar a construir", você verá um editor e uma lista de blocos no lado esquerda da tela. Agora você só precisa arrastar os blocos para o editor e conectá-los, criando assim sua lógica. 
 
-![criando](https://images.ctfassets.net/alneenqid6w5/3wvd23x3WUK4IcSK6MMemU/3cffed6cac4c6398ee2c03fcd95973ba/criando.gif)
+![criando](//images.ctfassets.net/alneenqid6w5/3wvd23x3WUK4IcSK6MMemU/3cffed6cac4c6398ee2c03fcd95973ba/criando.gif)
 
 ### Editando uma condição
 
@@ -54,4 +54,4 @@ Caso você queira que uma condição não seja mais aplicada, você pode simples
 - Quando o botão ao lado da condição for azul -> está habilitada
 - Quando o botão ao lado da condição for cinza -> está desabilitada
 
-![enableDisable](https://images.ctfassets.net/alneenqid6w5/4MqAUcKUfmeakkG2KMyeyc/5874f8d693a49aebebb6b51de37194ae/enableDisable.gif)
+![enableDisable](//images.ctfassets.net/alneenqid6w5/4MqAUcKUfmeakkG2KMyeyc/5874f8d693a49aebebb6b51de37194ae/enableDisable.gif)
diff --git a/docs/tutorials/pt/how-to-use-the-index-report.md b/docs/tutorials/pt/how-to-use-the-index-report.md
index 5432ddef3..ba023ab71 100644
--- a/docs/tutorials/pt/how-to-use-the-index-report.md
+++ b/docs/tutorials/pt/how-to-use-the-index-report.md
@@ -1,10 +1,10 @@
 ---
 title: 'Utilizar o Relatório de Indexação'
 id: 4ikVpMhwByyS8sysaeOIm4
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-07-04T13:10:40.431Z
-updatedAt: 2023-03-29T19:04:52.988Z
-publishedAt: 2023-03-29T19:02:27.075Z
+updatedAt: 2023-07-13T19:45:25.468Z
+publishedAt: 2023-07-13T19:45:25.468Z
 firstPublishedAt: 2017-07-04T19:16:21.471Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/pt/how-to-use-the-meta-tags-control.md b/docs/tutorials/pt/how-to-use-the-meta-tags-control.md
index 9654bdc82..f7f2db61f 100644
--- a/docs/tutorials/pt/how-to-use-the-meta-tags-control.md
+++ b/docs/tutorials/pt/how-to-use-the-meta-tags-control.md
@@ -3,8 +3,8 @@ title: 'Como usar o controle de meta tags'
 id: 2OPiSPubgcEqIikAWsCouk
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:38.270Z
-updatedAt: 2023-03-29T17:49:39.799Z
-publishedAt: 2023-03-29T17:49:39.799Z
+updatedAt: 2023-10-17T14:24:54.898Z
+publishedAt: 2023-10-17T14:24:54.898Z
 firstPublishedAt: 2019-01-24T22:06:45.424Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -55,5 +55,5 @@ Veja abaixo um exemplo de meta tags inseridas pelo controle `<vtex:metaTags/>` p
 ```
 
 <div class="alert alert-info">
-Caso não queira usar a tag canonical (&lt;link rel="canonical"&gt;), você pode desabilitá-la por meio de um <a href="http://help.vtex.com/pt/faq/controle-para-desabilitar-a-tag-canonical">controle específico para isso</a>.
+Caso não queira usar a tag canonical (&lt;link rel="canonical"&gt;), você pode desabilitá-la por meio de um <a href="https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag">controle específico para isso</a>.
 </div>
diff --git a/docs/tutorials/pt/how-to-use-the-search-result-control.md b/docs/tutorials/pt/how-to-use-the-search-result-control.md
index dfa97bbd6..aeedad396 100644
--- a/docs/tutorials/pt/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/pt/how-to-use-the-search-result-control.md
@@ -46,14 +46,14 @@ Veja abaixo a lista de todos os atributos do controle Search Result:
 
 O código renderizado pelo controle Search Result tem, por padrão, a seguinte estrutura:
 
-![searchResult1](https://images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
+![searchResult1](//images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
 
 E os elementos correspondentes que são renderizados pelo controle em sua versão não customizada seguem o padrão abaixo:
 
-![searchResult2](https://images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
+![searchResult2](//images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
 
-![searchResult3](https://images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
+![searchResult3](//images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
 
-![searchResult4](https://images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
+![searchResult4](//images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
 
-![searchResult5](https://images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
+![searchResult5](//images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
diff --git a/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md b/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md
index 31e74abc7..a53dbb065 100644
--- a/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md
+++ b/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 O app [Carrinho Compartilhável](https://apps.vtex.com/vtex-social-selling/p) permite que vendedores selecionem produtos para seus clientes e compartilhem o carrinho preenchido por canais como WhatsApp, Facebook Messenger e e-mail (Social Selling).
 
-![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artigo explica todos os passos para usar esta funcionalidade: ativar app, escolher os produtos, adicionar o código do vendedor, compartilhar e criar um novo carrinho. Antes de começar, é preciso [ativar esta funcionalidade na sua loja](https://help.vtex.com/pt/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg).
 
@@ -31,25 +31,25 @@ Onde `{Endereço web da sua loja}` deve ser substituído pelo endereço do site
 
 A interface de compartilhamento de carrinho deve aparecer na tela, incluindo alguns dos ícones abaixo. As opções disponíveis dependem da configuração escolhida pela loja.
 
-![Screen Shot 2020-05-03 at 17.37.11](https://images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
+![Screen Shot 2020-05-03 at 17.37.11](//images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
 
 ## Escolher produtos
 
 Uma vez ativado o app, não é necessário fazer login para iniciar a navegação e selecionar os produtos. Basta navegar na loja normalmente, como se estivesse fazendo uma compra online. Depois de escolher todos produtos para o cliente, basta abrir o carrinho e seguir os próximos passos na interface de compartilhamento de carrinho.
 
-![shareable-cart-chooseproducts](https://images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
+![shareable-cart-chooseproducts](//images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
 
 ## Adicionar código de vendedor
 
-Após selecionar os produtos, clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> para adicionar o seu código de vendedor. Siga as instruções da loja para o preenchimento, já que cada loja pode escolher formas diferentes para identificar vendedores e descontos.
+Após selecionar os produtos, clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> para adicionar o seu código de vendedor. Siga as instruções da loja para o preenchimento, já que cada loja pode escolher formas diferentes para identificar vendedores e descontos.
 
-![shareable-cart-addcode](https://images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
+![shareable-cart-addcode](//images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
 
 ## Preencher dados pessoais e endereço (opcional)
 
 Conforme a preferência do cliente e as orientações da sua loja, você poderá preencher os dados pessoais e de entrega do pedido. __Já os dados de pagamentos devem ser sempre preenchidos pelo cliente.__
 
-![shareable-cart-customerdetails](https://images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
+![shareable-cart-customerdetails](//images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
 
 <div class="alert alert-danger" role="alert"><strong>Nunca peça dados de pagamento ao enviar o carrinho.</strong> Mesmo que o cliente insista, informe que é para a segurança de todos que o pagamento seja informado por ele.</div>
 
@@ -57,13 +57,13 @@ Conforme a preferência do cliente e as orientações da sua loja, você poderá
 
 Depois de adicionar seu código de vendedor, clique no botão correspondente à opção desejada. Detalhamos abaixo os passos para cada tipo de compartilhamento.
 
-![shareable-cart-sharecart](https://images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
+![shareable-cart-sharecart](//images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
 
 ### WhatsApp
 
 Para compartilhar o carrinho por WhatsApp:
 
-1. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/34fTsrnmu0yZKKAU2Kq9iR/a9e805534e6bc81434026357529be8a3/image11.png" />
+1. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/34fTsrnmu0yZKKAU2Kq9iR/a9e805534e6bc81434026357529be8a3/image11.png" />
 2. Digite o __número de telefone do cliente__ e clique em OK
 3. (Opcional) Customize a mensagem no WhatsApp
 4. Envie a mensagem pelo WhatsApp
@@ -74,7 +74,7 @@ Para compartilhar o carrinho por WhatsApp:
 
 Para compartilhar o carrinho por Facebook Messenger:
 
-1. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/513wjcWdQzEydkFpsdm2Kb/e6ffef11d724e6fc1b66bf00504c81bb/image1.png" />
+1. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/513wjcWdQzEydkFpsdm2Kb/e6ffef11d724e6fc1b66bf00504c81bb/image1.png" />
 2. Digite o __nome do perfil do cliente__ no Facebook Messenger
 3. Customize a mensagem no Facebook Messenger
 4. Envie a mensagem pelo Facebook Messenger
@@ -88,7 +88,7 @@ Não é possível compartilhar carrinhos no Messenger para perfis desconhecidos.
 
 Para compartilhar o carrinho por SMS: 
 
-1. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/aYyWKNKx0Fb4sSNT5yNJQ/34f7516d18c2f6efcb6c62c70ba8c04b/image7.png" />
+1. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/aYyWKNKx0Fb4sSNT5yNJQ/34f7516d18c2f6efcb6c62c70ba8c04b/image7.png" />
 2. Digite o __número de telefone do cliente__ e clique em OK
 3. (Opcional) Customize a mensagem no seu aplicativo de SMS
 4. Envie a mensagem pelo seu aplicativo de SMS
@@ -97,7 +97,7 @@ Para compartilhar o carrinho por SMS:
 
 Para compartilhar o carrinho por Link:
 
-1. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2GZp3YTXtUkh5KvG9BTFx6/0921f73c5c553a90ddd39056ab918202/image15.png" />
+1. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2GZp3YTXtUkh5KvG9BTFx6/0921f73c5c553a90ddd39056ab918202/image15.png" />
 2. Copie o link destacado em __Link para compartilhar__
 3. (Opcional) Escreva uma mensagem customizada com o link
 4. Envie o link para o cliente no seu canal de contato
@@ -106,7 +106,7 @@ Para compartilhar o carrinho por Link:
 
 Para compartilhar o carrinho por Gmail:
 
-1. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/1rQ6MAeLHDZZ4vnX2p3Gyq/17bcbb4ebb94ac94a34dffb6c3515663/image14.png" />
+1. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/1rQ6MAeLHDZZ4vnX2p3Gyq/17bcbb4ebb94ac94a34dffb6c3515663/image14.png" />
 2. Digite o __endereço de e-mail do cliente__ e clique em OK
 3. (Opcional) Customize a mensagem no Gmail
 4. Envie a mensagem pelo Gmail
@@ -117,7 +117,7 @@ Para compartilhar o carrinho por Gmail:
 
 Para compartilhar o carrinho por Email:
 
-1. Clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/1B5ehv90NAceay9z6PPr7R/70fd43fed7c4aaec4e5a902c01255072/image8.png" />
+1. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/1B5ehv90NAceay9z6PPr7R/70fd43fed7c4aaec4e5a902c01255072/image8.png" />
 2. Digite o __endereço de e-mail do cliente__ e clique em OK
 3. (Opcional) Customize a mensagem no seu aplicativo de e-mail
 4. Envie a mensagem pelo seu aplicativo de e-mail
@@ -126,7 +126,7 @@ Para compartilhar o carrinho por Email:
 
 ## Limpar carrinho
 
-Após concluir o atendimento de um cliente, clique no botão <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2fM6iuMfYNkTWlPA1vaSFM/c5c7c03611d846d609907d272b66684b/image5.png"/> para limpar seu carrinho e escolher novos produtos para outro cliente.
+Após concluir o atendimento de um cliente, clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2fM6iuMfYNkTWlPA1vaSFM/c5c7c03611d846d609907d272b66684b/image5.png"/> para limpar seu carrinho e escolher novos produtos para outro cliente.
 
 <div class="alert alert-info" role="alert"><strong>Cada vendedor pode trabalhar com vários clientes!</strong> Recomendamos guardar os links já compartilhados em uma planilha ou bloco de notas. Assim você mantém seus carrinhos organizados e poderá fazer alterações sempre que solicitado por um cliente.</div>
 
diff --git a/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md b/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md
index 9e7289e38..dbfe0f080 100644
--- a/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md
+++ b/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md
@@ -17,6 +17,6 @@ subcategory:
 
 Quando um produto é incluído no carrinho, serão destacados os valores cobrados dos impostos configurados anteriormente. Para o cálculo de imposto, é necessário o preenchimento dos dados do cliente e dos dados de entrega de compra. Na página de finalização da compra, os impostos estarão sempre destacados. O encarregado da loja também terá a informação destacada no Gerenciamento de Pedidos.
 
-![Screenshot 1](https://images.ctfassets.net/alneenqid6w5/h1utOUorGESswSg6QcSGu/1e1084773c4524bcefd6bb357443eb3e/Screenshot_1.png)
+![Screenshot 1](//images.ctfassets.net/alneenqid6w5/h1utOUorGESswSg6QcSGu/1e1084773c4524bcefd6bb357443eb3e/Screenshot_1.png)
 
 [Continue com o TaxHub lendo sobre sua estrutura de API REST](/pt/tutorial/como-e-a-estrutura-api-rest-do-taxhub)
diff --git a/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md b/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md
index b81c1aa75..80774aeb9 100644
--- a/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md
+++ b/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md
@@ -20,7 +20,7 @@ Todos os pedidos em que o pagamento é transacionado pela VTEX são registrados
 Na sua interface principal teremos as transações listadas em ordem da mais recente para a mais antiga.
 Na listagem já é indicado o status atual, o início (data e hora) da transação, o nome do cliente, o ID do pedido, qual o meio de pagamento utilizado para fechar o pedido e o valor transacionado no mesmo.
 
-![payment_pt](https://images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/5818a03e5c91a2497e788f6bf1b6e173/payment_pt.jpg)
+![payment_pt](//images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/5818a03e5c91a2497e788f6bf1b6e173/payment_pt.jpg)
 
 Cada registro de pedido terá seus dados restritos às condições de pagamento utilizadas para o seu fechamento. Isto é, códigos de autorização, transação, NSU, entre outros, [estão disponibilizados dentro de cada registro](http://help.vtex.com/tutorial/como-visualizar-detalhes-do-pedido/).
 
diff --git a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
index 7da10893d..a008d6cf3 100644
--- a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
@@ -37,7 +37,7 @@ Após isso, uma nova seção será disponibilizada e você poderá definir atrav
 
 É possível limitar a disponibilização do template para um período de tempo pré determinado nos campos __From__ e __To__ assim como definir em quais categorias, produtos, marcas e coleções o template será aplicado. 
 
-![template-condicionado-cms](https://images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
+![template-condicionado-cms](//images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
 
 Após preencher todos os campos, não se esqueça de salvar as mudanças feitas clicando em __Save Layout__.
 
diff --git a/docs/tutorials/pt/how-trade-policies-work.md b/docs/tutorials/pt/how-trade-policies-work.md
index 0d6a31221..c511cafd9 100644
--- a/docs/tutorials/pt/how-trade-policies-work.md
+++ b/docs/tutorials/pt/how-trade-policies-work.md
@@ -3,8 +3,8 @@ title: 'Como funciona uma Política Comercial'
 id: 6Xef8PZiFm40kg2STrMkMV
 status: PUBLISHED
 createdAt: 2021-05-25T20:05:42.155Z
-updatedAt: 2022-12-08T14:39:11.093Z
-publishedAt: 2022-12-08T14:39:11.093Z
+updatedAt: 2024-06-20T22:52:38.544Z
+publishedAt: 2024-06-20T22:52:38.544Z
 firstPublishedAt: 2021-05-25T20:17:12.408Z
 contentType: tutorial
 productTeam: Others
@@ -33,7 +33,12 @@ Confira como diferentes configurações da VTEX se relacionam com políticas com
 
 Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via ticket em [*Suporte*](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`, o tempo estimado de resposta (SLA) é de 48 horas úteis.
 
-A contratação de política comercial adicional para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?#integrado-a-conector-nativo-vtex), [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
+A contratação de política comercial adicional para integrar com [conector certificado](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
+
+Cada cliente na plataforma VTEX é regido por um contrato que define os parâmetros para a contratação de políticas comerciais. Essas políticas são projetadas para oferecer benefícios específicos, complementando a política comercial nativa incluída automaticamente em cada conta. A VTEX estabelece [Regras de Cobrança](#regras-de-cobranca) e [Regras de Isenção](#regras-de-isencao) para algumas políticas comerciais adicionais, promovendo o fortalecimento das integrações dentro do seu ecossistema.
+
+<div class=alert alert-warning>
+Se a mesma política comercial for usada em um conector certificado e em um conector parceiro, não há isenção de taxas.</div>
 
 ## Catálogo
 Ao [cadastrar produtos](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567) no catálogo, é possível restringir sua disponibilidade para determinadas políticas comerciais. Dessa forma, o catálogo é segmentado de acordo com diferentes estratégias de negócio. Essas estratégias podem incluir a segmentação de produtos por região, para um marketplace, ou para tipos específicos de clientes, como funcionários, por exemplo. Saiba mais sobre a configuração do [catálogo](https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ).
@@ -63,6 +68,14 @@ Para clientes com muitas subcontas, ou com operação de loja física que possib
 
 O excesso de políticas comerciais em um ambiente VTEX faz com que o processo de indexação de produtos na vitrine da loja e a simulação de frete no checkout fiquem mais lentos, possivelmente afetando a conversão de pedidos. Ao segmentar o catálogo por múltiplas políticas comerciais em vez de criar store names com inventário próprio, a loja também pode perder oportunidades de venda e melhores condições de entrega, ao restringir a oferta de produtos. Saiba mais sobre [como criar um store name](https://help.vtex.com/pt/tutorial/como-criar-um-store-name).
 
+## Regras de Cobrança
+Cada cliente VTEX possui valores estabelecidos em seu contrato para a contratação de políticas comerciais adicionais e essas possuem custo. Ressaltamos que cada conta na VTEX já possui uma [política comercial nativa](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?&amp;utm_source=autocomplete), que não se enquadra nessas regras de cobrança.
+
+A Política Comercial será passível de cobrança a partir do momento da sua criação mesmo que não haja pedidos sendo realizados. Caso seja totalmente utilizada para integrações diretas com lojas VTEX ou Marketplaces certificados, a bonificação ocorrerá automaticamente na fatura.
+
+## Regras de Isenção
+As regras de isenção das políticas comerciais são um benefício estratégico concedido pela VTEX, visando incentivar o fortalecimento das integrações dentro do nosso ecossistema. Essas regras podem ser atualizadas ao longo do tempo. Hoje a isenção é aplicada para as políticas que possuem pedidos em conector certificado ou integração direta com outras lojas VTEX.
+
 ## Saiba mais
 
 - [Políticas comerciais para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)  
diff --git a/docs/tutorials/pt/hubspot-suiteshare.md b/docs/tutorials/pt/hubspot-suiteshare.md
index fb7d28458..d3571e773 100644
--- a/docs/tutorials/pt/hubspot-suiteshare.md
+++ b/docs/tutorials/pt/hubspot-suiteshare.md
@@ -23,11 +23,11 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **HubSpot**.
 
-   ![HubSpot_Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
+   ![HubSpot_Suiteshare_1](//images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
 
 2. Acesse **Configurações > Integrações > HubSpot > Integrar**.
 
-   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
 Selecione a Hubspot e clique em _**“integrar”**_
 
diff --git a/docs/tutorials/pt/i-cant-import-the-price-table.md b/docs/tutorials/pt/i-cant-import-the-price-table.md
new file mode 100644
index 000000000..ea64a760c
--- /dev/null
+++ b/docs/tutorials/pt/i-cant-import-the-price-table.md
@@ -0,0 +1,67 @@
+---
+title: 'Não consigo importar a planilha de preços'
+id: bglrzs7gLKWf97q8qRdRm
+status: PUBLISHED
+createdAt: 2024-06-10T15:11:02.787Z
+updatedAt: 2024-06-10T19:44:11.614Z
+publishedAt: 2024-06-10T19:44:11.614Z
+firstPublishedAt: 2024-06-10T17:28:51.238Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: nao-consigo-importar-a-planilha-de-precos
+locale: pt
+legacySlug: nao-consigo-importar-a-planilha-de-precos
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras-chave__: *planilha de preços, importação de planilhas, células.*
+
+As [tabelas ou planilhas de preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) armazenam informações de SKUs que após serem aplicadas em determinados contextos, tais como políticas comerciais, promoções ou cluster de clientes, permitem calcular os valores de venda dos produtos em uma loja VTEX. Para mais informações, acesse [Preço base](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) e [Preço fixo](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy). 
+
+<div class ="alert alert-warning">
+  Não é possível importar uma planilha de <b>Preço calculado</b> no Admin VTEX. A função <b>Exportar</b> está disponível para esta planilha apenas para que o lojista possa conferir os valores de preço final de cada produto.
+</div>
+
+Após [importar uma planilha de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D), algumas mensagens de erro podem surgir em determinados SKUs, como nos exemplos abaixos: 
+
+- `"The resource you are looking for cannot be found: Price not found"`
+- `"Error occurred while converting spreadsheet: Object reference not set to an instance of an object."`
+- `"Import Fixed Table Error: Invalid headers - SKU ID"`
+
+Caso você identifique mensagens de erro, valores incorretos de preço ou outras dificuldades para importar uma planilha, examine as possíveis soluções abaixo para resolver esses problemas.
+
+## Solução
+
+Para corrigir dificuldades na importação de planilha de preços, considere verificar as seguintes soluções:
+
+### Modelo de planilha
+
+Planilhas criadas pelos próprios clientes ou customizadas após serem exportadas do Admin VTEX podem gerar erros de integração no momento da importação.
+
+Para evitar este tipo de cenário, utilize somente os modelos de planilha disponíveis (preço-base ou preço fixo) e não aplique nenhum tipo de customização. Saiba mais em [Exportação de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D#exportacao-de-precos).
+
+### Preenchimento de dados
+
+Planilhas preenchidas com informações incorretas, por exemplo, inserindo o ID do produto onde deveria ser utilizado o ID do SKU, ou [alterando o preço de um SKU](https://help.vtex.com/pt/tutorial/alteracao-de-preco-de-sku--tutorials_95#regra-para-alteracao-de-preco) cadastrado em mais de 70% ou diminuindo mais de 30% em relação ao valor atual, podem gerar inconsistências no momento de importá-las na loja.
+
+Confira se os campos de sua planilha estão devidamente preenchidos conforme as orientações dos artigos abaixo:
+
+- [Planilha de preço-base](https://help.vtex.com/pt/tutorial/preencher-campos-da-planilha-de-importacao-de-precos-base--4Jox8TeQ5feqAn78TZ0DNA)
+- [Planilha de preço fixo](https://help.vtex.com/pt/tutorial/preencher-campos-da-planilha-de-importacao-de-precos-fixo--50RFoH3ruV97FJgeBUCURh)
+
+<div class ="alert alert-warning">
+  Antes de importar a planilha no Admin VTEX, certifique-se de que a mesma não contenha colunas com informações de erro (<b>Error Code</b> e <b>Error Message</b>) ou que exista algum tipo de filtro aplicado nas células. Caso você tente importar a planilha nestas condições, podem ocorrer erros no processo de importação dos dados.
+</div>
+
+Exemplo de planilha com filtros aplicados e campos __Error Code__ e __Error Message__ presentes:
+
+![Planilha de preço](//images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/0109fb3de360f568c44f6e0e6c3a920e/Price_spreadsheet.PNG)
+
+#### Tamanho do arquivo
+
+Planilhas de preço devem possuir um limite máximo de tamanho de 1 megabyte (MB). Caso a sua planilha atual seja maior que este valor, divida as informações em planilhas de tamanho inferior a 1 megabyte (MB).
+
+<div class ="alert alert-warning">
+  Todos os dados de um SKU específico devem ser mantidos na mesma planilha, não sendo permitido o cadastro de informações do mesmo SKU em planilhas diferentes.
+</div>
diff --git a/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md b/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
new file mode 100644
index 000000000..c4cde5e4d
--- /dev/null
+++ b/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
@@ -0,0 +1,98 @@
+---
+title: 'Não consigo receber emails da VTEX'
+id: 4M2uVZdtrJzgyAySuZ4OLg
+status: PUBLISHED
+createdAt: 2024-05-28T17:21:01.400Z
+updatedAt: 2024-06-10T18:28:15.898Z
+publishedAt: 2024-06-10T18:28:15.898Z
+firstPublishedAt: 2024-05-29T13:14:04.884Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: nao-consigo-receber-emails-da-vtex
+locale: pt
+legacySlug: nao-consigo-receber-emails-da-vtex
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras-chave__: *central de mensagens, configurações da loja, templates de emails, exportação de dados, logs de erro, importação de planilhas, token de autenticação.*
+
+Por meio da [Central de mensagens](https://help.vtex.com/pt/tutorial/conhecendo-o-message-center--tutorials_84), a VTEX oferece aos lojistas a opção de personalizar templates de e-mail que serão encaminhados aos usuários. Estes emails podem ser utilizados para transmitir as seguintes informações:
+- Token de autenticação na loja
+- Notificação de criação e pagamento de pedidos
+- Confirmação de exportação de dados
+- Logs de erro de importação de planilhas
+
+Caso você identifique que os emails de sua loja não estão sendo encaminhados de maneira adequada, prejudicando assim a transmissão de informações importantes aos seus clientes, verifique abaixo as possíveis soluções para identificar a origem deste problema.
+
+## Solução
+
+Para corrigir interrupções no envio de emails da VTEX, considere verificar as seguintes soluções:
+
+- [Confirmar remetente](#confirmacao-de-remetente)
+- [Configurar servidor de email](#configuracao-de-servidor-de-email)
+- [Configurar notificação de pedido e pagamento](#configuracao-da-notificacao-de-pedido-e-pagamento)
+- [Remover email da lista de supressão AWS](#lista-de-supressao-da-aws)
+
+### Confirmação de remetente
+
+Se a sua loja possui um remetente customizado, além do remetente padrão __VTEX-DEFAULT__, realize um teste de envio de mensagens conforme os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Templates de email > Remetentes__.
+2. No box com o nome do seu remetente cadastrado, clique em `Testar`. Após alguns segundos uma mensagem de confirmação de envio de email será exibida.
+3. Verifique se um email da VTEX foi encaminhado para o endereço do usuário logado no Admin.
+4. Caso não tenha recebido o email da VTEX, prossiga para a próxima solução.
+
+### Configuração de servidor de email
+
+Na VTEX é possível utilizar o servidor nativo de emails ou [configurar um servidor SMTP externo](https://help.vtex.com/pt/tutorial/personalizando-o-smtp-da-vtex--tutorials_2733). Caso você esteja utilizando um servidor SMTP externo, verifique os cenários abaixo.
+
+#### Configuração SMTP no Admin VTEX
+
+1. No Admin VTEX, acesse __Configurações da loja > Templates de email > Remetentes__.
+2. Clique no box com o nome do seu remetente cadastrado.
+3. Em __Dados do SMTP__, verifique se todos os dados estão corretos.
+4. Clique em `Salvar`.
+5. No box com o nome do seu remetente cadastrado, clique em `Testar`. Após alguns segundos uma mensagem de confirmação de envio de email será exibida.
+6. Verifique se um email da VTEX foi encaminhado para o endereço do usuário logado no Admin.
+
+Após o teste, caso a mensagem da VTEX não tenha sido enviada para o email do usuário logado no Admin, recomendamos que utilize o remetente da VTEX (__VTEX-DEFAULT__) como padrão e realize o teste de envio de mensagem novamente. Se mesmo assim, não tenha recebido o email da VTEX, prossiga para a próxima solução.
+
+#### Configuração SPF (Sender Policy Framework)
+
+Confira se o servidor SMTP externo está devidamente configurado conforme o [sistema SPF](https://help.vtex.com/pt/tutorial/configuracao-de-spf--42t0lkl2VyC6Yewc4wA6wI), responsável por evitar que servidores não autorizados enviem emails em nome de um domínio específico. Caso necessário, você pode realizar a [configuração do SPF](https://developers.vtex.com/docs/guides/setting-up-the-spf) e da [DKIM](https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails) (DomainKeys Identified Mail) no servidor.
+
+<div class ="alert alert-warning">
+Acesse também a sua caixa de spam para garantir que os emails da VTEX não estão sendo enviados para este local. Isto pode ocorrer devido a regras internas de servidores de mail.
+</div>
+
+### Configuração da notificação de pedido e pagamento
+
+A VTEX encaminha emails para os usuários logo após um pedido ser criado ou pagamento ser realizado. Siga os passos abaixo para verificar as configurações de notificações de pagamento:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__.
+2. Clique na aba __Configurações__.
+3. Certifique-se de que o seu email está preenchido no campo correspondente a opção __Meu email VTEX__. Se desejar, insira um email secundário no campo __Outro email__ e realize o teste de envio de mensagem conforme a seção [Confirmação de remetente](#confirmacao-de-remetente).
+4. Verifique se um email da VTEX foi encaminhado para o endereço do usuário logado no Admin.
+5. Caso não tenha recebido o email da VTEX, prossiga para a próxima solução.
+
+### Lista de supressão da AWS
+
+A Amazon (AWS) possui uma plataforma de email chamada Amazon Simple Email Service ([Amazon SES](https://aws.amazon.com/pt/ses/)). Dentre as várias funcionalidades deste serviço, existe uma lista de supressão de endereços de email onde constam destinatários que podem ter apresentado algum tipo de comportamento suspeito que tenha afetado algum cliente da AWS.
+
+Em situações normais, um endereço de email pode ser incluído na lista de supressão da AWS e ser removido após aproximadamente 12 horas. Durante este período, emails enviados pela VTEX não serão recebidos pelo endereço de email incluído na lista.
+
+<div class ="alert alert-warning">
+A gestão da lista de supressão é de responsabilidade da AWS, e a VTEX não tem responsabilidade sobre a movimentação de entrada e saída de endereços na lista.
+</div>
+
+Caso desconfie que o seu endereço de email tenha sido bloqueado pela AWS, aguarde o período de 12 horas e tente reenviar novamente um email para o endereço bloqueado.
+
+Além disso, você também pode verificar se o endereço de email está cadastrado como cópia em algum dos templates de emails transacionais da loja. Para verificar esta informação, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Templates de email > Templates__.
+2. Clique sobre um card de template desejado.
+3. Verifique se o endereço de email não está presente nos campos __Cc:__ ou __Cco:__ do template. Caso esteja, remova a informação e clique em `Salvar`.
+4. Realize este procedimento para cada um dos cards de template da loja e realize um teste de envio de email para o endereço desejado.
+
+![copia_email_pt](//images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/51aaca3868dce4213bc7c9f9b447b6ca/copia_email_pt.png)
diff --git a/docs/tutorials/pt/i-cant-update-the-ean-of-my-skus-via-api.md b/docs/tutorials/pt/i-cant-update-the-ean-of-my-skus-via-api.md
new file mode 100644
index 000000000..c199c716c
--- /dev/null
+++ b/docs/tutorials/pt/i-cant-update-the-ean-of-my-skus-via-api.md
@@ -0,0 +1,50 @@
+---
+title: 'Não consigo atualizar o EAN dos meus SKUs por API'
+id: 1gHfGo3TpSTHqb5ZNzwq3m
+status: PUBLISHED
+createdAt: 2024-06-18T16:50:42.770Z
+updatedAt: 2024-06-18T17:29:20.394Z
+publishedAt: 2024-06-18T17:29:20.394Z
+firstPublishedAt: 2024-06-18T17:28:22.909Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: nao-consigo-atualizar-o-ean-dos-meus-skus-por-api
+locale: pt
+legacySlug: nao-consigo-atualizar-o-ean-dos-meus-skus-por-api
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags de produto:** Catálogo
+
+**Palavras-chave:** SKU, produto, EAN, catálogo
+
+Ao tentar atualizar o EAN (número de artigo europeu), que contém as informações do código de barras de um SKU, no Admin VTEX e na API, você pode encontrar problemas de sincronização do catálogo da loja, afetando o gerenciamento de estoque e a experiência do cliente.
+
+## Solução
+
+Para resolver esse problema, considere [deletar EAN do SKU](#deletar-ean-do-sku) para depois [adicionar um novo EAN](#etapa-1-adicionar-novo-ean-ao-sku).
+
+### Deletar EAN do SKU
+
+Para atualizar o atual EAN do SKU, é necessário primeiramente deletar todos os EANs associados ao SKU. 
+
+- [Delete SKU EAN](https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/stockkeepingunit/-skuId-/ean/-ean-): use o endpoint para deletar um EAN específico.
+- [Delete all SKU EAN values](https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/stockkeepingunit/-skuId-/ean): use o endpoint para deletar todos os EANs associados ao SKU.
+
+#### Etapa 1 - Adicionar novo EAN ao SKU
+
+Somente após deletar os EANs de um SKU, será possível adicionar um EAN novo. Para isso, use o endpoint [Create SKU EAN](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/ean/-ean-) para criar o novo valor do EAN.
+
+#### Etapa 2 - Consultar atualização de EAN do SKU
+
+Uma vez adicionado o novo valor do EAN, utilize o endpoint [Get SKU by EAN](https://developers.vtex.com/docs/api-reference/catalog-api#get-/api/catalog_system/pvt/sku/stockkeepingunitbyean/-ean-) para checar se a atualização. Os novos valores dos EANs serão exibidos no array `AlternateIdValues`.
+
+```json
+"AlternateIdValues":
+[
+"8781",
+"878181"
+]
+```
+
diff --git a/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
new file mode 100644
index 000000000..2ac9a0245
--- /dev/null
+++ b/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
@@ -0,0 +1,240 @@
+---
+title: 'Não consigo visualizar o produto na busca do site'
+id: 2Ry55Fh6JW8v7oKBiB2pH3
+status: PUBLISHED
+createdAt: 2024-07-24T16:39:50.379Z
+updatedAt: 2024-07-25T15:47:00.673Z
+publishedAt: 2024-07-25T15:47:00.673Z
+firstPublishedAt: 2024-07-24T18:55:15.925Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: nao-consigo-visualizar-o-produto-na-busca-do-site
+locale: pt
+legacySlug: nao-consigo-visualizar-o-produto-na-busca-do-site
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras-chave__: *produto, busca, catálogo, intelligent search, apps, rewriter, graphql, vtex io, redirect.*
+
+Quando o usuário realiza a pesquisa em uma loja VTEX por meio do [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG), é possível que o produto desejado não seja localizado, mesmo que o termo utilizado na busca esteja presente nas informações cadastradas do item.
+
+Cenário de exemplo: ao pesquisar no site da loja por produtos que contenham o termo "Pendleton", o resultado da busca exibe 6 produtos. Entretanto, quando acessamos o Admin VTEX (__Storefront > Intelligent Search > Explicação da busca__) e digitamos o mesmo termo, são apresentados 9 produtos.
+
+![Filter_1](//images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/d91a90067779eab00b0aefe3b40f889a/Filter_1.png)
+
+![Filter_2](//images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/eb0ef3af6e10a261b1e8176ca18ef04a/Filter_2.png)
+
+Este comportamento pode ocorrer devido aos seguintes cenários:
+
+1. Cadastro incorreto do produto no Catálogo.
+
+2. O termo utilizado não está presente em um dos campos pesquisáveis do produto. Saiba mais em [Configurações para o comportamento da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/23mytRDsEduqLO0Lo7yufy#configuracoes-para-o-comportamento-da-busca) e [Configuração da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx).
+
+3. Rota interna redirecionando o resultado da pesquisa para uma página de marca (brand).
+
+## Soluções
+
+Para permitir que os produtos pesquisados sejam exibidos corretamente no resultado da busca do site, considere verificar as seguintes soluções:
+
+- [Verificar campos de cadastro do produto](#verificacao-dos-campos-de-cadastro-do-produto)
+- [Modificar filtro de busca no Rewriter](#modificacao-do-filtro-da-busca-no-rewriter)
+- [Remover rota interna de busca no Rewriter](#remocao-da-rota-interna-de-busca-no-rewriter)
+
+### Verificação dos campos de cadastro do produto
+
+A ausência do produto em um resultado de busca pode ser atribuída ao preenchimento incorreto de alguns campos durante o processo de [cadastro do produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke). Siga os passos abaixo para verificar os campos __Marca, Exibir no site e Mostrar produto esgotado__:
+
+<blockquote><ui>1. No Admin VTEX, acesse </b>Catálogo > Todos os produtos</b>.</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Lojas que utilizam a página <b>Produtos e SKUS (Beta)</b>, devem verificar os campos de cadastro do produto acessando <b>Catálogo > Produtos e SKUS</b> no Admin VTEX. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">Produtos e SKUS (Beta)</a>.
+</div></blockquote>
+
+<blockquote><ui>2. Localize o produto desejado e clique em <b>EDITAR</b>.</ui>
+
+<blockquote><ui>3. No campo <b>Marca</b>, verifique se a informação está correta. Se necessário, adicione a marca correspondente ao produto. Somente é possível adicionar marcas que já tenham sido previamente <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7lEGOSpAlQJCs5eUc5XFmR">cadastradas na loja</a>.</ui>
+
+<blockquote><ui>4. Na opção <b>Exibir no site</b>, confirme se o campo está selecionado.</ui>
+
+<blockquote><ui>5. Na opção <b>Mostrar produto esgotado</b>, confirme se o campo está selecionado.</ui>
+
+<blockquote><ui>6. Clique em <i>Salvar</i>.</ui>
+
+<blockquote><ui>7. Acesse o site da loja, digite o termo desejado e verifique se os produtos exibidos no resultado da busca são iguais aos produtos disponíveis na página <b>Explicação da busca</b> do Intelligent Search (<b>Storefront > Intelligent Search > Explicação da busca</b>).</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Se o termo de busca estiver presente no nome ou descrição do produto, mas o produto for de uma marca diferente do termo especificado na busca, prossiga com as demais etapas para solucionar o problema.
+</div></blockquote>
+
+### Modificação do filtro da busca no Rewriter
+
+Outro fator que pode contribuir para um produto não ser exibido em um resultado de busca é o comportamento padrão que o app [Rewriter](https://developers.vtex.com/docs/apps/vtex.rewriter) apresenta ao exibir produtos.
+
+Se um termo for registrado no Rewriter como marca, o [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4uSFqyJVCMVMIvVrtz3lxZ) receberá a informação de que ele deverá ser exibido apenas quando estiver presente em uma marca.
+
+Para remover a restrição de busca por marca (*brand*) e permitir os produtos sejam localizados também por termos presentes no nome ou descrição (*full text*), siga os passos abaixo:
+
+  <blockquote><ui>1. No Admin VTEX, em <b>Storefront > Intelligent Search > Explicação da busca</b>, insira o termo desejado e verifique quantos produtos são retornados na busca.</ui>
+
+<blockquote><ui>2. Configure o app <a href="https://developers.vtex.com/docs/apps/vtex.rewriter">Rewriter</a>. Caso este app ainda não esteja instalado em sua loja, acesse a <a href="https://help.vtex.com/pt/tracks/hub-de-extensoes--AW7klkYMh557y5IUOgzco/2LDRvGujYsumxi7IlE7CEJ">App Store</a> para instalá-lo.</ui>
+
+<blockquote><ui>3. Acesse o <a href="https://developers.vtex.com/docs/guides/graphql-ide#graphql-basics">GraphQL IDE</a> em <b>Configurações da loja > Storefront > GraphQL IDE</b>.</ui>
+
+<blockquote><ui>4. Em <b>Selecione um app</b>, clique sobre a opção do app Rewriter (<b>vtex.rewriter@{app-version-number}</b>).</ui>
+
+![Graphql_ide_pt](//images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/2b1cf341f212c5ac6ea16e7314d3c048/Graphql_ide_pt.png)
+
+<blockquote><ui>5. No campo de preenchimento da query (abaixo de <b>GraphiQL</b>), insira os dados da função mutação <i>saveInternal</i>.<ui>
+
+```
+mutation saverInternal($route: InternalInput!) {
+internal {
+ save(route: $route) {
+   from
+   declarer
+   type
+   id
+   query
+   endDate
+   binding
+   resolveAs
+   origin
+   disableSitemapEntry
+ }
+}
+}
+```
+
+<blockquote><ui>6. Em <b>Query Variables</b>, insira as informações sobre a rota. Você deve substituir o valor <i>Pendleton</i> pelo termo desejado e o valor do campo <i>id</i> pela identificação do produto.<ui>
+
+```
+{
+"route": {
+ "from": "/Pendleton",
+ "declarer": "vtex.store@2.x",
+ "type": "fullText",
+ "id": "2000307",
+ "query": {
+     "map": "ft"
+ },
+   "origin": "user-canonical"
+ }
+}
+```
+
+<blockquote><ui><div class ="alert alert-warning">
+  O valor <i>ft</i> (full text) ao invés de <i>b</i> (brand) no parâmetro <i>map</i> indica que produtos em que o termo <i>Pendleton</i> esteja presente no nome ou na descrição também passarão a ser exibidos na busca.
+</div></blockquote>
+
+<blockquote><ui>7. Clique na seta do GraphiQL IDE (ao lado de <b>GraphiQL</b>) para realizar a atualização do filtro de busca. O novo padrão de filtro de busca para o termo será confirmada pela exibição da seguinte mensagem no campo de resultados do GraphiQL IDE.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "save": {
+        "from": "/Pendleton",
+        "declarer": "vtex.store@2.x",
+        "type": "fullText",
+        "id": "2000307",
+        "query": {
+          "map": "ft"
+        },
+        "endDate": null,
+        "binding": "0be568e5-52f5-44f0-9308-3ea701a9f847",
+        "resolveAs": null,
+        "origin": "user-canonical",
+        "disableSitemapEntry": null
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>8. Acesse o site da loja, digite o termo desejado e verifique se os produtos exibidos no resultado da busca são iguais aos produtos disponíveis na página <b>Explicação da busca</b> do Intelligent Search (<b>Storefront > Intelligent Search > Explicação da busca</b>).</ui>
+
+<blockquote><ui><div class ="alert alert-warning">
+  Se o termo de busca estiver relacionado a uma marca que não existe mais em seu site, será necessário remover a rota interna de busca dentro do app Rewriter conforme descrito na solução abaixo.</div></blockquote>
+
+### Remoção da rota interna de busca no Rewriter
+
+[Rotas internas](https://developers.vtex.com/docs/guides/vtex-io-documentation-routes#routes-in-rewriter) de busca no app [Rewriter](https://developers.vtex.com/docs/apps/vtex.rewriter) podem impedir que um produto seja exibido na busca caso este tenha sido cadastrado com uma marca que não esteja mais disponível na loja.
+
+Para voltar a exibir produtos que contenham os termos pesquisados apenas no nome ou descrição, é necessário deletar a respectiva rota de busca. 
+
+Para remover uma rota interna de busca do termo, siga os passos abaixo:
+
+<blockquote><ui>1. No Admin VTEX, acesse o <a href="https://developers.vtex.com/docs/guides/graphql-ide#graphql-basics">GraphQL IDE</a> em <b>Configurações da loja > Storefront > GraphQL IDE</b>.</ui>
+
+<blockquote><ui>2. Em <b>Selecione um app</b>, clique sobre a opção do app Rewriter (<b>vtex.rewriter@{app-version-number}</b>).</ui>
+
+<blockquote><ui>3. No campo de preenchimento da query (abaixo de <b>GraphiQL</b>), insira os dados da função <i>internal get</i>, substituindo <i>pendleton</i> pelo termo desejado.</ui> 
+
+```
+{
+  internal {
+    get(path: "/Pendleton") {
+      from
+      resolveAs
+      type
+    }
+  }
+}
+```
+
+<blockquote><ui>4. Clique na seta do GraphiQL IDE (ao lado de <b>GraphiQL</b>) e verifique no campo de resultados se a rota interna está descrita como <i>brand</i>.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "get": {
+        "from": "/Pendleton",
+        "resolveAs": "/Pendleton",
+        "type": "brand"
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>5. No campo de preenchimento da query (abaixo de <b>GraphiQL</b>), insira os dados da função <i>mutation</i>, substituindo <i>pendleton</i> pelo termo desejado.</ui> 
+
+```
+mutation {
+  internal {
+    delete(path: "/Pendleton"){
+      type
+    }
+  }
+}
+```
+
+<blockquote><ui>6. Clique na seta do GraphiQL IDE (ao lado de <b>GraphiQL</b>) para remover a rota interna de filtro por <i>brand</i> e confirme se a informação abaixo aparece no campo de resultados do GraphiQL IDE.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "delete": {
+        "type": "brand"
+      }
+    }
+  }
+}
+```
+
+<blockquote><ui>7. Repita os passos 3 e 4 para confirmar que a rota interna de redirecionamento do termo para brand foi deletada. Isto pode ser indicado pelo resultado <i>"get": null</i> no campo de resultados do GraphiQL IDE.</ui>
+
+```
+{
+  "data": {
+    "internal": {
+      "get": null
+    }
+  }
+}
+```
+
+<blockquote><ui>8. Acesse o site da loja, digite o termo desejado e verifique se os produtos exibidos no resultado da busca são iguais aos produtos disponíveis na página <b>Explicação da busca</b> do Intelligent Search (<b>Storefront > Intelligent Search > Explicação da busca</b>).</ui>
diff --git a/docs/tutorials/pt/i-forgot-my-password-suiteshare.md b/docs/tutorials/pt/i-forgot-my-password-suiteshare.md
index 0feb632ac..c12ba797d 100644
--- a/docs/tutorials/pt/i-forgot-my-password-suiteshare.md
+++ b/docs/tutorials/pt/i-forgot-my-password-suiteshare.md
@@ -17,14 +17,14 @@ subcategory: 4y4ylvqceE6vVqEF8IWZix
 
 Para recuperar sua senha, acesse o site do [VTEX Assisted Sales (SuiteShare)](https://suiteshare.com) e clique em **Entrar**. 
 
-![Senha_Suitshare_1](https://images.ctfassets.net/alneenqid6w5/4tYRuHpLYfRQNao1GV3Tix/dacb5d395c1e04aeaeb9fb438df56b27/Senha_Suitshare_1.png)
+![Senha_Suitshare_1](//images.ctfassets.net/alneenqid6w5/4tYRuHpLYfRQNao1GV3Tix/dacb5d395c1e04aeaeb9fb438df56b27/Senha_Suitshare_1.png)
 
 Clique em **Esqueci minha senha**.
 
-![Senha_Suitshare_2](https://images.ctfassets.net/alneenqid6w5/1F57gl3OYPJz4VxNghFIZM/d3af7ad7764de2b15dd3c305b2263597/Senha_Suitshare_2.png)
+![Senha_Suitshare_2](//images.ctfassets.net/alneenqid6w5/1F57gl3OYPJz4VxNghFIZM/d3af7ad7764de2b15dd3c305b2263597/Senha_Suitshare_2.png)
 
 Digite o seu email, para receber as informações de redefinição de senha.
 
-![Senha_Suitshare_3](https://images.ctfassets.net/alneenqid6w5/6K44Aat6Ad3HVg2wwCKsq2/ba3d2d6801e39cd0650cbed4c0fc30a1/Senha_Suitshare_3.png)
+![Senha_Suitshare_3](//images.ctfassets.net/alneenqid6w5/6K44Aat6Ad3HVg2wwCKsq2/ba3d2d6801e39cd0650cbed4c0fc30a1/Senha_Suitshare_3.png)
 
 Pronto! Basta adicionar a nova senha e realizar o login normalmente.
diff --git a/docs/tutorials/pt/image-compression.md b/docs/tutorials/pt/image-compression.md
new file mode 100644
index 000000000..0de7b81d8
--- /dev/null
+++ b/docs/tutorials/pt/image-compression.md
@@ -0,0 +1,62 @@
+---
+title: 'Compactação de imagens'
+id: 4klbgpsPksq44KcwqKeye8
+status: PUBLISHED
+createdAt: 2017-08-17T22:59:59.002Z
+updatedAt: 2024-04-15T14:59:26.688Z
+publishedAt: 2024-04-15T14:59:26.688Z
+firstPublishedAt: 2017-08-17T23:30:18.772Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: compactacao-de-imagens
+locale: pt
+legacySlug: compactacao-automatica-de-imagens
+subcategory: 2g6LxtasS4iSeGEqeYUuGW
+---
+
+A compactação ou compressão de imagens é um processo que reduz o tamanho dos arquivos de imagem para otimizá-las para a web, para garantir que as imagens sejam carregadas rapidamente enquanto um usuário navega em um site.
+
+O objetivo desse processo é aumentar a velocidade e a performance da loja, que têm impacto na experiência do usuário, no [SEO](https://developers.google.com/search/blog/2010/04/using-site-speed-in-web-search-ranking) e nas taxas de conversão.
+
+Existem dois tipos de compactação de imagens, descritos na tabela abaixo:
+
+| Tipo de compactação | Descrição |
+| - | - |
+| Lossy (com perdas) | Reduz o tamanho e a qualidade da imagem de forma a reter as informações mais significativas sem manter todos os pixels. | 
+| Lossless (sem perdas) | Reescreve um arquivo de imagem sem remover nenhuma informação. Apesar de manter a qualidade original, é menos eficaz do que a compactação lossy ao reduzir o arquivo. |
+
+Na VTEX, os arquivos são armazenados em seu formato original, mas compactados em tempo real durante a navegação na loja.
+
+Fazemos uma conversão automática para o formato [WebP](https://developers.google.com/speed/webp?hl=pt-br) sempre que for mais vantajoso, ou seja, sempre que o tamanho da imagem for menor, independentemente se a imagem original é no formato **PNG** ou **JPG / JPEG**.
+
+O uso do WebP pode gerar um ganho de 1 a 2 segundos no tempo de carregamento das páginas, variando conforme o layout. Confira a seguir como funciona a otimização de imagens em cada formato.
+
+<div class="alert alert-info">
+  <p>Navegadores que ainda não são <a href="https://developers.google.com/speed/webp/faq?hl=pt-br#which_web_browsers_natively_support_webp">compatíveis com o formato WebP</a> e serviços como integrações e marketplaces sempre recebem imagens não convertidas, em qualquer formato. Arquivos no formato GIF não passam pela conversão para WebP.</p>
+</div>
+
+## PNG
+
+Para imagens em formato PNG, indicado para cores sólidas, gráficos detalhados e alto contraste, a conversão para WebP é realizada com compressão lossless, para evitar perdas grandes de qualidade. As imagens WebP lossless podem ser até 26% menores em comparação com as imagens em PNG.
+
+Paralelamente, ocorre a otimização de imagens PNG utilizando [pngquant](https://pngquant.org/), mantendo o formato, mas reduzindo o tamanho da imagem em até 70%.
+
+Por fim, a VTEX entrega o menor arquivo, entre o WebP lossless e o PNG otimizado, conforme ilustrado no diagrama abaixo.
+
+![png-image-compression-pt](//images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/fc5d276c114827f9692cf4b4bf8fd31b/png-image-compression-pt.PNG)
+
+## JPG / JPEG
+
+Para imagens no formato **JPG / JPEG**, indicado para fotos, a conversão para WebP é realizada com compressão lossy, podendo haver perdas de qualidade, mas garantindo um tamanho otimizado. Imagens WebP lossy são de 25% a 34% menores que imagens similares com índice de qualidade [SSIM](https://ece.uwaterloo.ca/~z70wang/research/ssim/) equivalente.
+
+A VTEX entrega ao cliente a imagem com menor tamanho de arquivo, dentre a original e a convertida em WebP lossless, conforme ilustrado no diagrama abaixo.
+
+![webp-image-compression-pt](//images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/b22f2eea1c7d528e32932d58a537b36c/webp-image-compression-pt.PNG)
+
+## Artigos relacionados
+
+* [Boas práticas para o uso de imagens no Catálogo](https://help.vtex.com/pt/tutorial/boas-praticas-para-o-uso-de-imagens-no-catalogo--738K2yfq5U86kUI2k4AQIk)
+* [Adicionar imagem à descrição do produto](https://help.vtex.com/pt/tutorial/adicionar-imagem-a-descricao-do-produto--2hQGTAAiyUSoISGSyOK8Y4)
+* [Importar imagens por planilha](https://help.vtex.com/pt/tutorial/importando-imagens-por-planilha--tutorials_262)
+* [Como atualizar a imagem de um SKU?](https://help.vtex.com/pt/tutorial/como-atualizar-a-imagem-de-um-sku--5PMb54FnvUuWOq2qGyAosu)[Reutilizando imagens com o Image Widget](https://help.vtex.com/pt/tutorial/image-widget--7pRSVI2xXpQUzjUZj0m4ov)
diff --git a/docs/tutorials/pt/image-widget.md b/docs/tutorials/pt/image-widget.md
index 1cb736e9c..d67ea39ca 100644
--- a/docs/tutorials/pt/image-widget.md
+++ b/docs/tutorials/pt/image-widget.md
@@ -3,8 +3,8 @@ title: 'Reutilizando imagens com o Image Widget'
 id: 7pRSVI2xXpQUzjUZj0m4ov
 status: PUBLISHED
 createdAt: 2021-06-30T18:06:46.531Z
-updatedAt: 2023-03-28T13:24:31.101Z
-publishedAt: 2023-03-28T13:24:31.101Z
+updatedAt: 2024-03-27T14:07:43.190Z
+publishedAt: 2024-03-27T14:07:43.190Z
 firstPublishedAt: 2021-07-02T21:20:16.653Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -42,11 +42,11 @@ Agora que você sabe como acessar o Image Widget, verifique o que você pode faz
 
 Depois de [acessar Image Widget](#acessando-image-widget) e com ele aberto você consegue adicionar imagens:
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px">
+<div class="alert alert-warning">
 Ao adicionar novas imagens no modal Image Widget usando um <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">development workspace</a>, as configurações performadas serão salvas diretamente em master, ou seja, imediatamente refletirão no modal da sua loja.
 </div>
 <br>
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px">
+<div class="alert alert-warning">
   O tamanho máximo que o Image Widget suporta é 4 MB por arquivo.
 </div>
 
@@ -65,12 +65,13 @@ Dentro do modal, alguns dos recursos que você possui são um campo para busca d
 Além disso, [adicionando uma imagem](#adicionando-uma-imagem) em seu modal, agora você pode visualizar, copiar a URL de uma imagem, fazer o download e excluí-las de seu repositório.
 
 Com o modal aberto, clique em `mais ações` na miniatura de uma imagem.
-| Opções     | Descrição     |
-| ---------- | ---------- |
+
+| Opções     | Descrição                                          |
+| ---------- | -------------------------------------------------- |
 | __Antevisão__  | Abre uma nova página para mostrar uma prévia da imagem. |
 | __Copiar URL__ | Permite que você copie o URL da imagem e use-a em outras partes da sua loja.    |
-| __Baixar__ | Baixe a imagem para o seu computador. |
-| __Excluir__| Remove a imagem do repositório. |
+| __Baixar__     | Baixe a imagem para o seu computador.              |
+| __Excluir__    | Remove a imagem do repositório.                    |
 
 ### Substituindo uma imagem
 
@@ -85,7 +86,7 @@ No bloco que você deseja substituir uma imagem:
 
 Para remover uma imagem do bloco desejado, clique em `Mais ações` na miniatura de uma imagem e selecione __remover__. Após esse procedimento, a imagem não estará mais visível no bloco.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding-left: 5px; margin-bottom: 10px">
+<div class="alert alert-warning">
   Quando você remove uma imagem, isso não significa que ela seja excluída do repositório. Para isso, verifique a seção <a href="#recursos-dentro-do-image-widget">Recursos dentro do Image Widget</a>.
 </div>
 
diff --git a/docs/tutorials/pt/import-customer-data-brazil.md b/docs/tutorials/pt/import-customer-data-brazil.md
index f872d273f..d835eb732 100644
--- a/docs/tutorials/pt/import-customer-data-brazil.md
+++ b/docs/tutorials/pt/import-customer-data-brazil.md
@@ -3,8 +3,8 @@ title: 'Importar dados de clientes'
 id: 2zWYVOyj0sISYQmeUwCsI0
 status: PUBLISHED
 createdAt: 2017-06-22T20:55:49.745Z
-updatedAt: 2022-10-17T20:32:21.800Z
-publishedAt: 2022-10-17T20:32:21.800Z
+updatedAt: 2023-10-09T20:34:05.165Z
+publishedAt: 2023-10-09T20:34:05.165Z
 firstPublishedAt: 2017-06-27T14:40:29.106Z
 contentType: tutorial
 productTeam: Master Data
@@ -19,25 +19,25 @@ A importação de dados de clientes deve ser feita no Master Data. Para o envio
 
 <div class="alert alert-danger">
 <p>Este artigo se refere aos campos do Master Data v1 especificamente para as lojas do <strong>Brasil</strong>.</p>
-<p>Você também pode conferir o guia sobre como <a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2">importar dados de clientes programaticamente com a API do Master Data v2</a>.</p>
+<p>Você também pode conferir o guia sobre como <a href="https://developers.vtex.com/docs/guides/import-customer-data">importar dados de clientes programaticamente com a API do Master Data v2</a>.</p>
 </div>
 
 O checkout trabalha com os dados das entidades CL (cliente) e AD (endereço).
 
 Mas é importante notar que, para que o checkout já traga os dados do cliente no carrinho com base no e-mail, chave primária do Master Data, é fundamental garantir que todos os dados a seguir estejam corretamente cadastrados na plataforma.
 
-Dito isso, as tabelas a seguir representam os dados o formatos necessários para a importação.
+Dito isso, as tabelas a seguir representam os dados e os formatos necessários para a importação.
 
 ### Cliente
 
 | Nome do campo | Descrição | Formato |
 |---------------|-----------|---------|
-| firstName | nome | texto |
-| lastName | sobrenome | texto |
-| email | e-mail do cliente | email |
-| documentType | Tipo do documento | para Brasil deve ser "cpf" |
-| document | Documento (CPF) | 11 dígitos, sem máscara |
-| homePhone | Telefone | no formato "+5511999999999", sendo +55 para o país e sucedido   pelo telefone com DDD |
+| firstName | Nome do cliente | Texto |
+| lastName | Sobrenome | Texto |
+| email | Email do cliente | Email |
+| documentType | Tipo do documento | Para clientes do Brasil, deve ser "cpf". |
+| document | Documento (CPF, no caso do Brasil) | 11 dígitos, sem máscara. |
+| homePhone | Telefone | No formato "+5511999999999", sendo +55 para o país e sucedido pelo telefone com DDD. |
 
 O campo `id` é gerado pelo sistema logo após a importação, e será usado como `userId` na importação do endereço.
 
@@ -47,11 +47,11 @@ Se o cliente for **pessoa jurídica**, `document` e `documentType` deixam de ser
 
 | Nome do campo | Descrição | Formato |
 |---------------|-----------|---------|
-| isCorporate | define se o cliente é pessoa jurídica | deve ser "true" |
-| corporateName | razão social | texto |
-| tradeName | nome fantasia | texto |
-| stateRegistration | inscrição estadual | deve ser "Isento" ou texto/alfanumérico |
-| corporateDocument | CNPJ | 14 dígitos, sem máscara |
+| isCorporate | Define se o cliente é pessoa jurídica | Deve ser "true". |
+| corporateName | Razão social | Texto |
+| tradeName | Nome fantasia | Texto |
+| stateRegistration | Inscrição estadual | Deve ser "Isento" ou texto, valor alfanumérico. |
+| corporateDocument | CNPJ | 14 dígitos, sem máscara. |
 
 ### Endereço
 
@@ -59,20 +59,20 @@ Se o cliente for **pessoa jurídica**, `document` e `documentType` deixam de ser
 
 | Nome do campo | Descrição | Formato |
 |---------------|-----------|---------|
-| id | ID do endereço | em branco |
-| userId | ID do cliente | campo `id`, gerado após importação de clientes |
-| addressName | nome do endereço | texto/alfanumérico |
-| addressType | tipo do endereço | deve ser "residential" ou "commercial" |
-| country | país | "BRA" para Brasil |
-| state | estado (UF) | duas letras |
-| city | cidade | texto |
-| neighborhood | bairro | texto |
+| id | ID do endereço | Em branco |
+| userId | ID do cliente | Campo `id`, gerado após importação de clientes |
+| addressName | Nome do endereço | Texto/alfanumérico |
+| addressType | Tipo do endereço | Deve ser "residential" ou "commercial" |
+| country | Código do país | "BRA" para Brasil |
+| state | Estado (UF) | Duas letras |
+| city | Cidade | Texto |
+| neighborhood | Bairro | texto |
 | postalCode | CEP | 8 ou 9 dígitos, com hífen |
-| street | endereço | texto |
-| number | número | alfanumérico |
-| complement | Complemento e referência | texto |
-| reference | campo não usado | em branco |
-| receiverName | destinatário | texto |
+| street | Endereço | Texto |
+| number | Número | alfanumérico |
+| complement | Complemento e referência | Texto |
+| reference | Campo deprecado | Em branco |
+| receiverName | Destinatário | Texto |
 
 ---
 
diff --git a/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md b/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md
index f7253b657..b5825caa4 100644
--- a/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md
+++ b/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md
@@ -3,8 +3,8 @@ title: 'Importar e exportar planilha de estoque'
 id: tutorials_2034
 status: PUBLISHED
 createdAt: 2017-04-27T21:55:43.488Z
-updatedAt: 2023-03-29T14:51:46.368Z
-publishedAt: 2023-03-29T14:51:46.368Z
+updatedAt: 2023-07-24T15:03:49.647Z
+publishedAt: 2023-07-24T15:03:49.647Z
 firstPublishedAt: 2017-04-27T23:03:50.695Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/pt/importing-data-into-master-data.md b/docs/tutorials/pt/importing-data-into-master-data.md
index 522569eea..95153166f 100644
--- a/docs/tutorials/pt/importing-data-into-master-data.md
+++ b/docs/tutorials/pt/importing-data-into-master-data.md
@@ -3,8 +3,8 @@ title: 'Importar dados no Master Data'
 id: tutorials_1135
 status: PUBLISHED
 createdAt: 2017-04-27T21:57:12.437Z
-updatedAt: 2023-03-28T23:29:25.337Z
-publishedAt: 2023-03-28T23:29:25.337Z
+updatedAt: 2023-06-15T19:48:45.566Z
+publishedAt: 2023-06-15T19:48:45.566Z
 firstPublishedAt: 2017-04-27T23:03:43.488Z
 contentType: tutorial
 productTeam: Master Data
@@ -42,9 +42,9 @@ Após a exportação e edição da planilha exportada, é hora de realizar a imp
 Mantenha o mesmo formato da planilha (xls) para realizar a importação com sucesso.
 </div>
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. Clique na aba **Aplicações**.
-3. Clique no botão **Modo de Importação**.
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
+2. Clique na aba **Aplicações.**
+3. Clique no botão **Importar.**
 4. Selecione a entidade de dados que deseja inserir ou atualizar registros (Aqui, você deve inserir a entidade de dados do formulário onde estão os registros que deseja inserir ou atualizar).
 5. Escolha o arquivo.
 6. Clique no botão **Importar** no canto inferior da tela.
diff --git a/docs/tutorials/pt/importing-images-from-a-spreadsheet.md b/docs/tutorials/pt/importing-images-from-a-spreadsheet.md
index 0820da4ef..0277dba94 100644
--- a/docs/tutorials/pt/importing-images-from-a-spreadsheet.md
+++ b/docs/tutorials/pt/importing-images-from-a-spreadsheet.md
@@ -3,8 +3,8 @@ title: 'Importar imagens por planilha'
 id: tutorials_262
 status: PUBLISHED
 createdAt: 2017-04-27T22:11:24.581Z
-updatedAt: 2023-03-29T17:46:11.384Z
-publishedAt: 2023-03-29T17:46:11.384Z
+updatedAt: 2024-03-04T22:25:58.399Z
+publishedAt: 2024-03-04T22:25:58.399Z
 firstPublishedAt: 2017-04-27T23:03:11.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -57,11 +57,11 @@ A seguir, explicamos o preenchimento de cada campo da planilha de importação d
 <p>Este campo é obrigatório. Não é permitido o uso de caracteres especiais, pontos no nome da imagem ou acentos.</p>
 </div>
 
-Este campo precisa ser preenchido com a URL da imagem a ser associada ao SKU, que deve estar pública e hospedada em um servidor FTP, de onde se origina o link da imagem. A URL deve obrigatoriamente iniciar com o identificador de protocolo HTTPS (`https://`) e terminar com a extensão do arquivo (`.jpg`, `.png` ou `.gif`). Exemplo: `https://www.exemploimagem.com.br/imagem03/teste01/exemplo15.jpg`.
+Este campo precisa ser preenchido com a URL da imagem a ser associada ao SKU, que deve estar pública e hospedada em um servidor FTP, de onde se origina o link da imagem. A URL deve obrigatoriamente iniciar com o identificador de protocolo HTTP (`http://`) e terminar com a extensão do arquivo (`.jpg`, `.png` ou `.gif`). Exemplo: `http://www.exemploimagem.com.br/imagem03/teste01/exemplo15.jpg`.
 
-Para evitar erros, é importante verificar se a URL da imagem inserida na planilha está completa, incluindo desde o `https://` até a extensão do arquivo. Caso contrário, o sistema não conseguirá acessar a URL e a imagem não será importada.
+Para evitar erros, é importante verificar se a URL da imagem inserida na planilha está completa, incluindo desde o `http://` até a extensão do arquivo. Caso contrário, o sistema não conseguirá acessar a URL e a imagem não será importada.
 
-Você não precisa ter um servidor FTP próprio para enviar as URLs das imagens. É possível hospedar esses dados em sites gratuitos e em servidores FTP externos ou internos, desde que utilizem o protocolo de segurança HTTPS.
+Você não precisa ter um servidor FTP próprio para enviar as URLs das imagens. É possível hospedar esses dados em sites gratuitos e em servidores FTP externos ou internos, desde que utilizem o protocolo de segurança HTTP.
 
 Além disso, para verificar se as URLs estão corretas, você pode utilizar um serviço externo, o qual verifica se estas são válidas.
 
diff --git a/docs/tutorials/pt/indexes-in-master-data.md b/docs/tutorials/pt/indexes-in-master-data.md
new file mode 100644
index 000000000..c0f8f5d05
--- /dev/null
+++ b/docs/tutorials/pt/indexes-in-master-data.md
@@ -0,0 +1,86 @@
+---
+title: 'Índices no Master Data'
+id: tutorials_785
+status: PUBLISHED
+createdAt: 2017-04-27T21:58:03.173Z
+updatedAt: 2024-07-17T13:57:12.010Z
+publishedAt: 2024-07-17T13:57:12.010Z
+firstPublishedAt: 2017-04-27T23:03:42.760Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 1malnhMX0vPThsaJaZMYm2
+slug: indices-no-master-data
+locale: pt
+legacySlug: configurando-indice-no-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+Um índice no Master Data é uma referência a um ou mais campos, utilizada para otimização das consultas em uma entidade de dados. O uso de índices possibilita uma busca mais rápida de registros.
+
+Para ilustrar, imagine o índice de um livro, que contém a indicação dos temas contidos no livro e a página de cada tema. Para fazer uma pesquisa, em vez de ter que passar por todas as páginas do livro para encontrar o resultado desejado, é possível acessar o índice e ir direto ao tema que deseja. Da mesma forma, o índice no Master Data fornece um método mais eficiente para encontrar documentos.
+
+## Configurar índice
+
+Siga o passo a passo para definir um ou mais campos como índices no Master Data:
+
+1. No Admin VTEX, acesse **Configurações da loja > Storefront > Master Data**.
+2. Clique no ícone de engrenagem <i class="fas fa-cog"></i> na aplicação em que deseja adicionar o índice.
+3. Clique em **Estrutura de dados**.
+4. Clique na aba **Índice**.
+5. Clique em `Adicionar`.
+6. Preencha os campos a seguir:
+    * **Nome:** nome do índice.
+    * **Valores únicos:** opção que permite bloquear novos registros com valores repetidos para o(s) índice(s) criados. Leia a seção [Restrição de valores por documento (chave alternativa)](#restricao-de-valores-por-documento-chave-alternativa) para mais detalhes.
+    * **Entidade de dados:** nome da entidade de dados que contém os campos a serem configurados como índices.
+    * **Campos:** nome de um ou mais campos que serão configurados como índices. Se for adicionar mais de um nome de campo, separe-os por vírgula. Exemplo: `firstName,document`.
+7. Clique em `Salvar`.
+
+## Casos de uso
+
+Saiba mais sobre os principais cenários de uso de índices no Master Data nas seções a seguir.
+
+### Consultas de até mil documentos
+
+O uso de índices é recomendado para buscas com resultados de até mil documentos. Se as buscas por um índice frequentemente retornarem mais de mil documentos, você pode obter uma performance melhor na busca ao indexar o campo, isto é, [configurá-lo como um filtro na entidade de dados](https://help.vtex.com/pt/tutorial/filtrando-dados-no-master-data--tutorials_778).
+
+### Restrição de valores por documento (chave alternativa)
+
+A configuração de índices permite bloquear um ou mais campos para evitar registros com valores repetidos. Esses campos funcionam como chaves alternativas, ou seja, valores alternativos para identificar um registro.
+
+A chave alternativa é configurada pelo campo **Valores Únicos** na [configuração do índice](#configurar-indice) e funciona de maneiras diferentes dependendo da quantidade de campos inseridos no índice. Confira nas seções a seguir o funcionamento em cada caso.
+
+#### Um só campo no índice
+
+Se houver somente um campo configurado como índice, a chave alternativa não vai permitir que um valor que já foi cadastrado nesse campo seja cadastrado novamente.
+
+Por exemplo, a tabela **Cliente** possui duas colunas: **ID** e **Nome**. Para facilitar a busca, o campo **Nome** (`firstName`) pode ser configurado como índice e marcado como **Valores únicos**, conforme ilustrado a seguir:
+
+![indices-1-pt](//images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/cde79764d3fe7472eca9db660139a068/indices-1-pt.png)
+
+Com isso, não será possível inserir um nome que já tenha sido cadastrado em __Cliente__:
+
+![indices-2-pt](//images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/c7e27a54409119fa21c5ff4a137c7879/indices-2-pt.png)
+
+No exemplo acima, como já existe um registro com o **Nome** igual a **Maria**, não é possível cadastrar outro com o mesmo valor.
+
+<div class="alert alert-warning">
+  <p>Use a opção <strong>Valores Únicos</strong> com cautela. Se um valor que você deseja permitir se repetir for configurado como único, o sistema bloqueará a inserção de registros duplicados, impedindo seu cadastro.</p>
+</div>
+
+#### Vários campos no índice
+
+Se houver mais de um campo no índice, a chave alternativa vai impedir que um conjunto de valores se repita nos campos selecionados.
+
+Por exemplo, imagine que a entidade **Cliente **possui três campos: **ID**, **Nome** e **Documento**. Na configuração do índice, em **Campos**, foram inseridos Nome (`firstName`) e Documento (`document`), conforme ilustrado abaixo:
+
+![indices-3-pt](//images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/b4a19b8d53d100227895aeda8951718f/indices-3-pt.png)
+
+Nesse caso, o valor do **Nome** pode se repetir ou o valor do **Documento** pode se repetir. Porém, a combinação dos dois valores não pode se repetir, ou seja, não pode existir nenhum registro que repita o mesmo par (**Nome** e **Documento **iguais).
+
+![indices-4-pt](//images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/1d6132aa5f7eaadd2425530e5e536f9b/indices-4-pt.png)
+
+No exemplo acima, já existe um registro com o **Nome** igual a **Maria**. É possível incluir outro registro com o mesmo **Nome**, desde que o valor do **Documento** seja diferente.
+
+<div class="alert alert-warning">
+  <p>Se a mesma combinação de valores se repetir, o registro não será salvo. Utilize a opção <strong>Valores únicos</strong> somente quando não existir a possibilidade de um conjunto de valores se repetir em registros diferentes.</p>
+</div>
diff --git a/docs/tutorials/pt/indexing-history-beta.md b/docs/tutorials/pt/indexing-history-beta.md
index 29355545a..2f34231c7 100644
--- a/docs/tutorials/pt/indexing-history-beta.md
+++ b/docs/tutorials/pt/indexing-history-beta.md
@@ -21,12 +21,12 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 
 **Histórico da Indexação** é a página que monitora a situação de sincronização de todos os produtos do Catálogo enviados para o Intelligent Search. Ele permite visualizar de forma ampla o progresso da indexação da sua loja.
 
-![Histórico da Indexação 1 - PT](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
 
 A seção **Status da indexação** exibe as seguintes informações:
 
 * **Tempo médio de indexação:** tempo médio para a indexação dos produtos, a partir do momento em que o sistema recebeu a notificação de uma mudança até a atualização na loja. O desempenho do tempo de indexação é medido por um ponto verde (saudável) ou vermelho (ruim). 
-![Historico Indexação 2 - PT](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
+![Historico Indexação 2 - PT](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
 * **Produtos na loja:** quantidade de produtos com informações atualizadas exibidos atualmente na loja.
 * **Divisão dos status:** porcentagem de produtos em cada etapa de indexação. O desempenho da divisão dos status é medido por um ponto verde (saudável) ou vermelho (ruim). As etapas exibidas são:
     * **Atualizado:** a atualização mais recente do produto foi inserida na loja.
@@ -35,17 +35,17 @@ A seção **Status da indexação** exibe as seguintes informações:
 
 Você pode filtrar a lista de produtos indexados para uma visualização customizada. Importante destacar que o tempo médio de indexação e a divisão dos status serão recalculados a partir dos produtos filtrados. 
 
-Para filtrar a lista de produtos indexados clique em `Filtro` <img src="https://images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
+Para filtrar a lista de produtos indexados clique em `Filtro` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
 
-![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Status` você pode selecionar por qual status deseja filtrar, podendo ser `Atualizado`, `Atualizando`, `Erro`.
 
- ![Historico indexação 4 - PT](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+ ![Historico indexação 4 - PT](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Tempo de indexação` você pode selecionar se o intervelo de tempo `É maior que`, `É igual ou maior que`, `É menor que` ou `É igual ou menor que` um horário definido.
 
-![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
 
 Depois de definir o filtro, clique em `Aplicar` para ativá-lo. 
 
@@ -55,18 +55,18 @@ Você também pode filtrar os produtos exibidos na listagem por **ID**, **Últim
 
 Caso deseje obter mais informações sobre a indexação de um produto específico, você pode clicar na linha do produto na lista para acessar a janela com mais detalhes, ilustrada abaixo.
 
-![Historico indexação 6 - PT](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 6 - PT](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Além dos dados exibidos na lista de produtos, também é possível visualizar:
 
 * **Tempo de Indexação:** registro de quanto tempo durou a última atualização do produto, no formato `hh:mm:ss`.
 * **Linha do tempo da indexação:** registro de cada mudança de status com data e horário. Você pode vizualizar mais detalhes de cada etapa clicando no ícone <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - PT](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 7 - PT](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 É possível reindexar um produto manualmente sem a necessidade de realizar alguma atualização no seu cadastro. Para reidexar um produto, clique em <i class="fa-solid fa-arrows-rotate"></i> `Reindexar`. Apenas produtos no status **Atualizado** podem ser reindexados.
 
 Você pode acessar o **Histórico de indexação** do produto, uma lista com data e horário de cada atualização realizada. Dessa forma, é possível ter registro de toda alteração que foi realizada no produto. Para acessá-lo, clique em <i class="fa-solid fa-arrow-rotate-left"></i> `Histórico`. 
 
-![Histórico da Indexação 8 - PT](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 8 - PT](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
 
diff --git a/docs/tutorials/pt/indexing-history.md b/docs/tutorials/pt/indexing-history.md
new file mode 100644
index 000000000..dcaca3fa6
--- /dev/null
+++ b/docs/tutorials/pt/indexing-history.md
@@ -0,0 +1,68 @@
+---
+title: 'Histórico da indexação'
+id: 55SRQ79PXk5lTURF54DRyJ
+status: PUBLISHED
+createdAt: 2024-06-27T16:51:28.631Z
+updatedAt: 2024-06-27T16:52:45.090Z
+publishedAt: 2024-06-27T16:52:45.090Z
+firstPublishedAt: 2024-06-27T16:52:45.090Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: historico-da-indexacao
+locale: pt
+legacySlug: historico-da-indexacao
+subcategory: l3DubpOCHBfKyF2ueg2Vs
+---
+
+**Histórico da Indexação** é a página que monitora a situação de sincronização de todos os produtos do Catálogo enviados para o Intelligent Search. Ele permite visualizar de forma ampla o progresso da indexação da sua loja.
+
+![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+
+A seção **Status da indexação** exibe as seguintes informações:
+
+* **Tempo médio de indexação:** tempo médio para a indexação dos produtos, a partir do momento em que o sistema recebeu a notificação de uma mudança até a atualização na loja. O desempenho do tempo de indexação é medido por um ponto verde (saudável) ou vermelho (ruim). 
+![Historico Indexação 2 - PT](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
+* **Produtos na loja:** quantidade de produtos com informações atualizadas exibidos atualmente na loja.
+* **Divisão dos status:** porcentagem de produtos em cada etapa de indexação. O desempenho da divisão dos status é medido por um ponto verde (saudável) ou vermelho (ruim). As etapas exibidas são:
+    * **Atualizado:** a atualização mais recente do produto foi inserida na loja.
+    * **Atualizando:** as novas informações do produto estão sendo preparadas e inseridas na loja.
+    * **Erro**: indica que houve um erro na indexação. O produto apresenta um problema no cadastro e, por isso, não pode ser indexado. Caso seja um produto novo cadastrado, ele não estará disponível na loja.
+
+Você pode filtrar a lista de produtos indexados para uma visualização customizada. Importante destacar que o tempo médio de indexação e a divisão dos status serão recalculados a partir dos produtos filtrados. 
+
+Para filtrar a lista de produtos indexados clique em `Filtro` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
+
+![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+Caso filtre por `Status` você pode selecionar por qual status deseja filtrar, podendo ser `Atualizado`, `Atualizando`, `Erro`.
+
+ ![Historico indexação 4 - PT](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+Caso filtre por `Tempo de indexação` você pode selecionar se o intervelo de tempo `É maior que`, `É igual ou maior que`, `É menor que` ou `É igual ou menor que` um horário definido.
+
+![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
+
+Depois de definir o filtro, clique em `Aplicar` para ativá-lo. 
+
+Para adicionar um novo filtro, clique em <i class="fa-solid fa-plus"></i> `Adicionar filtro`. Para remover os filtros configurados, clique em `Limpar filtros`.
+
+Você também pode filtrar os produtos exibidos na listagem por **ID**, **Última atualização** e **Status**, clicando na coluna desejada. Para encontrar um produto específico na listagem, é possível pesquisar pelo ID na barra de busca.
+
+Caso deseje obter mais informações sobre a indexação de um produto específico, você pode clicar na linha do produto na lista para acessar a janela com mais detalhes, ilustrada abaixo.
+
+![Historico indexação 6 - PT](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+Além dos dados exibidos na lista de produtos, também é possível visualizar:
+
+* **Tempo de Indexação:** registro de quanto tempo durou a última atualização do produto, no formato `hh:mm:ss`.
+* **Linha do tempo da indexação:** registro de cada mudança de status com data e horário. Você pode vizualizar mais detalhes de cada etapa clicando no ícone <i class="fa-solid fa-chevron-down"></i>.
+
+![Historico indexação 7 - PT](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+
+É possível reindexar um produto manualmente sem a necessidade de realizar alguma atualização no seu cadastro. Para reidexar um produto, clique em <i class="fa-solid fa-arrows-rotate"></i> `Reindexar`. Apenas produtos no status **Atualizado** podem ser reindexados.
+
+Você pode acessar o **Histórico de indexação** do produto, uma lista com data e horário de cada atualização realizada. Dessa forma, é possível ter registro de toda alteração que foi realizada no produto. Para acessá-lo, clique em <i class="fa-solid fa-arrow-rotate-left"></i> `Histórico`. 
+
+![Histórico da Indexação 8 - PT](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
+
diff --git a/docs/tutorials/pt/indexing.md b/docs/tutorials/pt/indexing.md
new file mode 100644
index 000000000..ebb152d89
--- /dev/null
+++ b/docs/tutorials/pt/indexing.md
@@ -0,0 +1,28 @@
+---
+title: 'Indexação'
+id: 7J6tepFgD3wohCGEP2PqDB
+status: PUBLISHED
+createdAt: 2024-06-27T16:49:13.712Z
+updatedAt: 2024-06-27T16:50:18.969Z
+publishedAt: 2024-06-27T16:50:18.969Z
+firstPublishedAt: 2024-06-27T16:50:18.969Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: indexacao
+locale: pt
+legacySlug: indexacao
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+A Indexação é um processo de sincronia entre os catálogos da loja e da busca. Essa funcionalidade permite uma atualização contínua do índice de produtos. Além disso, ela também executa um tratamento de dados para serem utilizados na busca.
+
+Inicialmente, é feita uma sincronização com todos os produtos do catálogo VTEX do cliente. A partir disso, as futuras atualizações de dados – como nome e status do produto – serão recebidas em tempo real pelo indexador de busca.
+
+Nesse processo de sincronia, o sistema forma uma fila das informações que foram atualizadas para serem indexadas no catálogo de busca. Após a indexação de todas as mudanças, elas estarão disponíveis no site. 
+
+O processo de indexação é seguro e conta com regras de repescagem – caso um item não seja indexado na primeira tentativa, o sistema realiza outras tentativas. 
+
+A indexação também é muito importante para analisar, tratar e organizar os dados da melhor forma para serem exibidos nos resultados.
+
+Confira [Histórico da indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) para mais informações sobre como monitorar o processo de indexação.
diff --git a/docs/tutorials/pt/information-about-chile-custom-payments.md b/docs/tutorials/pt/information-about-chile-custom-payments.md
index 48cd1b82a..72d805e91 100644
--- a/docs/tutorials/pt/information-about-chile-custom-payments.md
+++ b/docs/tutorials/pt/information-about-chile-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Informações dos pagamentos customizados do Chile'
 id: 1cqQ4JInfcOGUwW2aMOoEK
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.205Z
-updatedAt: 2019-12-31T15:26:29.898Z
-publishedAt: 2019-12-31T15:26:29.898Z
+updatedAt: 2024-03-19T12:13:49.935Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:11:20.233Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/information-about-colombia-custom-payments.md b/docs/tutorials/pt/information-about-colombia-custom-payments.md
index 5812359e2..5ac07de86 100644
--- a/docs/tutorials/pt/information-about-colombia-custom-payments.md
+++ b/docs/tutorials/pt/information-about-colombia-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Informações dos pagamentos customizados da Colômbia'
 id: 3tcvqc6LBSKOqMWCumwyaq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:36.914Z
-updatedAt: 2019-12-31T15:22:34.694Z
-publishedAt: 2019-12-31T15:22:34.694Z
+updatedAt: 2024-03-19T12:16:11.844Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:11:29.228Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/information-about-uruguay-custom-payments.md b/docs/tutorials/pt/information-about-uruguay-custom-payments.md
index 2ac97fa4b..e526b7ce5 100644
--- a/docs/tutorials/pt/information-about-uruguay-custom-payments.md
+++ b/docs/tutorials/pt/information-about-uruguay-custom-payments.md
@@ -1,10 +1,10 @@
 ---
 title: 'Informações dos pagamentos customizados do Uruguai'
 id: 4cXMr3C5rqIkUkMWgCcWeU
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:36.816Z
-updatedAt: 2019-12-31T15:20:18.360Z
-publishedAt: 2019-12-31T15:20:18.360Z
+updatedAt: 2024-03-19T12:18:07.525Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:06.326Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/inserting-images-into-let-me-know-email.md b/docs/tutorials/pt/inserting-images-into-let-me-know-email.md
index 4843d6f4e..e1b72dda7 100644
--- a/docs/tutorials/pt/inserting-images-into-let-me-know-email.md
+++ b/docs/tutorials/pt/inserting-images-into-let-me-know-email.md
@@ -31,7 +31,7 @@ A seguir, saiba como realizar essa configuração:
 4. Selecione o template __Let me know__.  
 5. Vá para a caixa de __HTML__.    
 6. Digite o código das imagens que deseja inserir, conforme ilustrado abaixo.
-  ![Let me know - PT](https:https://images.ctfassets.net/alneenqid6w5/57IqVpUH7SZKkH8sRtlfSf/2d7da2f98c03744e39154825204a4b4a/57IqVpUH7SZKkH8sRtlfSf_Imagem_Message_Center_PT.jpg)  
+  ![Let me know - PT](https://images.ctfassets.net/alneenqid6w5/57IqVpUH7SZKkH8sRtlfSf/2d7da2f98c03744e39154825204a4b4a/57IqVpUH7SZKkH8sRtlfSf_Imagem_Message_Center_PT.jpg)  
 7. Clique em `Salvar`.  
 
 Uma vez salva, a configuração já valerá para os próximos emails.
diff --git a/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md b/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md
index 7849011c1..6df6b456a 100644
--- a/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md
+++ b/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md
@@ -19,7 +19,7 @@ Acompanhando a evolução da plataforma VTEX, a viewpart de __Meus Pedidos__ ago
 
 Para fazer sua instalação, é preciso que você acesse a [VTEX App Store.](https://extensions.vtex.com/)
 
-![app store1 PT](https://images.ctfassets.net/alneenqid6w5/2aqC9IvvUM6o6Ko4WusYYQ/87950d670a9ff9eaa858bd3d24186814/app_store1_PT.png)
+![app store1 PT](//images.ctfassets.net/alneenqid6w5/2aqC9IvvUM6o6Ko4WusYYQ/87950d670a9ff9eaa858bd3d24186814/app_store1_PT.png)
 
 __Ao instalar a app, você já conta com as seguintes atualizações:__
 
@@ -29,7 +29,7 @@ __Ao instalar a app, você já conta com as seguintes atualizações:__
 - Informações de rastreio para vários itens.
 - Correção de bugs menores.
 
-![app store2 PT](https://images.ctfassets.net/alneenqid6w5/6NFSN0UxEcQgSWK6UaU8OW/5db671b107a7f6bd248aa4940dc5a108/app_store2_PT.png)
+![app store2 PT](//images.ctfassets.net/alneenqid6w5/6NFSN0UxEcQgSWK6UaU8OW/5db671b107a7f6bd248aa4940dc5a108/app_store2_PT.png)
 
 Além disso, com o novo app você consegue, realizar testes de versões e atualizá-lo sempre que uma nova versão estiver disponível, recebendo melhorias contínuas e atualizações de novas features.
 
@@ -42,4 +42,4 @@ Para fazer os testes de customização na sua página, você pode trabalhar em u
 5. Pronto! Agora você vê, antes de subir sua página, como ela irá se comportar.
 6. Para mover o My Orders para o ambiente em produção (onde seus clientes podem de fato usá-lo), você precisa publicar a modificação. Para isso, basta clicar no botão __Publicar__.
 
-![app store3 PT](https://images.ctfassets.net/alneenqid6w5/6jIsBdBtfiiKgiW6saCcMS/c81ca0455ac08dacf4a4d1db44782a15/app_store3_PT.png)
+![app store3 PT](//images.ctfassets.net/alneenqid6w5/6jIsBdBtfiiKgiW6saCcMS/c81ca0455ac08dacf4a4d1db44782a15/app_store3_PT.png)
diff --git a/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md b/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md
index 62469511f..8d2f937a6 100644
--- a/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md
+++ b/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md
@@ -23,44 +23,44 @@ Para instalar o nosso widget no seu site, siga os passos abaixo:
 
 1. Em nosso CMS, acesse o menu **Widget** e depois em **Instalação**.
 
-   ![Widget_1](https://images.ctfassets.net/alneenqid6w5/PvBIqUXXoy0HKgG9kHYQF/861a7781882e3459c3e4446c53bf3f7c/Widget_1.png)
+   ![Widget_1](//images.ctfassets.net/alneenqid6w5/PvBIqUXXoy0HKgG9kHYQF/861a7781882e3459c3e4446c53bf3f7c/Widget_1.png)
 
 2. Clique no botão **COPIAR CÓDIGO** e salve esse código em um bloco de notas.
 
-   ![Widget_2](https://images.ctfassets.net/alneenqid6w5/5x9QKNU0tIYtoAzYv3JMGK/ee316a807d88dc202bb002217b780469/Widget_2.png)
+   ![Widget_2](//images.ctfassets.net/alneenqid6w5/5x9QKNU0tIYtoAzYv3JMGK/ee316a807d88dc202bb002217b780469/Widget_2.png)
 
 3. No GTM, clique no menu **Tags** e, após nisso, no botão **New**.
 
-   ![Widget_3](https://images.ctfassets.net/alneenqid6w5/5JEWuW29vUzuXxU1ZIE3T3/a0bba65a23153557b65776b870bd2ba3/Widget_3.png)
+   ![Widget_3](//images.ctfassets.net/alneenqid6w5/5JEWuW29vUzuXxU1ZIE3T3/a0bba65a23153557b65776b870bd2ba3/Widget_3.png)
 
 4. Na tela abaixo, defina um nome para a tag (ex: VTEX Assisted Sales (SuiteShare) - Widget) e clique em **Choose a tag type to begin setup** para configurar a tag.
 
-   ![Widget_4](https://images.ctfassets.net/alneenqid6w5/7LcqsWNdLni472pl8Xn85n/378cccd15c9139214cafb9491fd84c40/Widget_4.png)
+   ![Widget_4](//images.ctfassets.net/alneenqid6w5/7LcqsWNdLni472pl8Xn85n/378cccd15c9139214cafb9491fd84c40/Widget_4.png)
 
 5. Após clicar na opção acima, irá surgir um menu a direita. Nesse menu, selecione a opção **Custom HTML**.
 
-   ![Widget_5](https://images.ctfassets.net/alneenqid6w5/19ve1JVLWfVTHhz8lQg64t/14b851233c3bbbaced668fad02bfd8ca/Widget_5.png)
+   ![Widget_5](//images.ctfassets.net/alneenqid6w5/19ve1JVLWfVTHhz8lQg64t/14b851233c3bbbaced668fad02bfd8ca/Widget_5.png)
 
 6. No campo exibido, cole o código copiado no **item 1** desse artigo.
 
-   ![Widget_6](https://images.ctfassets.net/alneenqid6w5/5n3YOrNAiZt0bEdGgQrF7w/f26751fb2bc334254f173a16dac0fd32/Widget_6.png)
+   ![Widget_6](//images.ctfassets.net/alneenqid6w5/5n3YOrNAiZt0bEdGgQrF7w/f26751fb2bc334254f173a16dac0fd32/Widget_6.png)
 
 7. Ainda na tela acima, após colar o nosso código, clique em **Choose a trigger to make this tag fire...**. Será exibido um novo menu a direita, onde você deve selecionar a opção **All Pages**.
 
-   ![Widget_7](https://images.ctfassets.net/alneenqid6w5/7DW6UcnlaTC5fgWRnG1BsR/48063165c62c1550fb505f067b922966/Widget_7.png)
+   ![Widget_7](//images.ctfassets.net/alneenqid6w5/7DW6UcnlaTC5fgWRnG1BsR/48063165c62c1550fb505f067b922966/Widget_7.png)
 
 8. Após isso, o resultado será uma tela semelhante a abaixo.
 
-   ![Widget_8](https://images.ctfassets.net/alneenqid6w5/753LeeyLcq2EUuMMG4riJY/8663150797f41fe362867ab30d3c3178/Widget_8.png)
+   ![Widget_8](//images.ctfassets.net/alneenqid6w5/753LeeyLcq2EUuMMG4riJY/8663150797f41fe362867ab30d3c3178/Widget_8.png)
 
 9. Clique no botão **Save** a direita, para salvar sua tag de instalação do widget VTEX Assisted Sales (SuiteShare).
 
 10. Por fim, publique essa alteração do GTM: clique no menu **Submit** a direita.
 
-   ![Widget_9](https://images.ctfassets.net/alneenqid6w5/6QLTRqElrB59rchytvzNzI/b8eb90559fa7b9537b08d41b17a1bee2/Widget_9.png)
+   ![Widget_9](//images.ctfassets.net/alneenqid6w5/6QLTRqElrB59rchytvzNzI/b8eb90559fa7b9537b08d41b17a1bee2/Widget_9.png)
 
 11. Informe um título e descrição da versão do deploy e clique em **Publish**.
 
-   ![Widget_10](https://images.ctfassets.net/alneenqid6w5/gec4OU8KY7V5KCYCS1OUS/8758cda8e7ced08ee85a0948a80a419e/Widget_10.png)
+   ![Widget_10](//images.ctfassets.net/alneenqid6w5/gec4OU8KY7V5KCYCS1OUS/8758cda8e7ced08ee85a0948a80a419e/Widget_10.png)
 
 Pronto, a integração foi finalizada.
diff --git a/docs/tutorials/pt/integrating-with-enjoei.md b/docs/tutorials/pt/integrating-with-enjoei.md
index 622fc3147..f2025a4b2 100644
--- a/docs/tutorials/pt/integrating-with-enjoei.md
+++ b/docs/tutorials/pt/integrating-with-enjoei.md
@@ -3,8 +3,8 @@ title: 'Integração com Enjoei '
 id: 3mV9uhw1AdqFol8K2tfwly
 status: PUBLISHED
 createdAt: 2021-11-05T19:27:31.160Z
-updatedAt: 2023-03-29T15:54:34.785Z
-publishedAt: 2023-03-29T15:54:34.785Z
+updatedAt: 2024-02-19T20:17:35.239Z
+publishedAt: 2024-02-19T20:17:35.239Z
 firstPublishedAt: 2021-11-05T20:49:41.372Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/pt/integrating-with-madeiramadeira.md b/docs/tutorials/pt/integrating-with-madeiramadeira.md
index a0d4c6e45..8c423a815 100644
--- a/docs/tutorials/pt/integrating-with-madeiramadeira.md
+++ b/docs/tutorials/pt/integrating-with-madeiramadeira.md
@@ -3,8 +3,8 @@ title: 'Integração com MadeiraMadeira'
 id: J4QCENKiz4urYNfaMuE0i
 status: PUBLISHED
 createdAt: 2021-11-05T21:04:22.888Z
-updatedAt: 2023-06-07T21:22:36.808Z
-publishedAt: 2023-06-07T21:22:36.808Z
+updatedAt: 2024-02-19T20:17:16.961Z
+publishedAt: 2024-02-19T20:17:16.961Z
 firstPublishedAt: 2021-11-05T21:34:03.556Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/pt/integrating-with-renner-and-camicado.md b/docs/tutorials/pt/integrating-with-renner-and-camicado.md
index 8502794b7..f8bfab2b6 100644
--- a/docs/tutorials/pt/integrating-with-renner-and-camicado.md
+++ b/docs/tutorials/pt/integrating-with-renner-and-camicado.md
@@ -1,10 +1,10 @@
 ---
 title: 'Integração com Renner e Camicado'
 id: 5qf2wloosKlmIB8o2AitnT
-status: CHANGED
+status: PUBLISHED
 createdAt: 2021-07-02T19:25:31.689Z
-updatedAt: 2022-12-15T20:40:16.364Z
-publishedAt: 2022-12-15T20:38:45.121Z
+updatedAt: 2023-08-25T18:50:55.909Z
+publishedAt: 2023-08-25T18:50:55.909Z
 firstPublishedAt: 2021-07-02T21:07:36.096Z
 contentType: tutorial
 productTeam: Channels
@@ -38,7 +38,7 @@ Feito isso, você pode dar continuidade às etapas da integração, sendo que pa
 Para integrar com a Renner ou a Camicado, é necessário realizar as seguintes etapas:
 
 - [Definir política comercial](#definir-politica-comercial)
-- [Criar novo _access key_ e _secret_](#criar-novo-access-key-e-secret)
+- [Criar novo _AppKey_ e _AppToken_](#criar-novo-AppKey-e-AppToken)
 - [Criar ID do afiliado](#criar-id-do-afiliado)
 
 ### Definir política comercial
@@ -47,16 +47,18 @@ A [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-poli
 
 Caso seja do seu interesse ter configurações específicas para vender na Renner ou na Camicado, você pode [configurar uma política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/). Não existe cobrança para a contratação de políticas comerciais adicionais para integrar sua loja VTEX com conectores nativos, conectores certificados, tais como a Renner e a Camicado, ou outras lojas VTEX.
 
-### Criar novo access key e secret
+### Criar novo AppKey e AppToken
 
-A chave de integração, chamada de _access key_, é o que possibilita o fluxo de envio e atualização de informações entre sua loja VTEX e a Renner e Camicado. Somente o [usuário Titular da conta (_owner_)](https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA?&utm_source=autocomplete) tem permissão para [criar um _access key_ e _secret_](https://developers.vtex.com/vtex-rest-api/docs/getting-started-authentication), e a opção só é visível no Admin para este usuário. 
+A chave de integração, chamada de _access key_, é o que possibilita o fluxo de envio e atualização de informações entre sua loja VTEX e a Renner e Camicado. Somente o [usuário Titular da conta (_owner_)](https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA?&utm_source=autocomplete) tem permissão para [criar um *AppKey e AppToken*](https://developers.vtex.com/vtex-rest-api/docs/getting-started-authentication), e a opção só é visível no Admin para este usuário. 
 
-Se você for integrar com os dois parceiros, Renner e Camicado, será necessário criar um _access key_ e _secret_ para cada um deles. Para configurar uma nova chave, siga os passos abaixo:
+Se você for integrar com os dois parceiros, Renner e Camicado, será necessário criar um *AppKey e AppToken* para cada um deles. Para configurar uma nova chave, siga os passos abaixo:
 
-1. No Admin, no módulo _CONFIGURAÇÕES DA CONTA_, clique em `Gerenciamento da Conta`.
-2. Clique em `Conta`.
-3. Em _Segurança_, clique em `Gerar access key e secret`.
-4. Preencha com um nome para o novo _access key_ e clique em `Gerar novos secrets`.
+1. No Admin, no módulo __Configurações da conta__, clique em `Chaves de aplicação`. 
+2. Clique no botão `Gerenciar minhas chaves`.  
+3. Clique no botão `Gerar chave`.  
+4. Preencha o campo __Rótulo__ com um nome para o novo *AppKey*.  
+5. Clique em `Adicionar perfis` e selecione os perfis desejados.  
+6. Clique em `Gerar`.  
 
 <div class="alert alert-danger">
 O <i>secret</i> gerado, também chamado de <i>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
@@ -66,11 +68,9 @@ O <i>secret</i> gerado, também chamado de <i>appToken</i>, só aparece para o u
 
 O [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) é o identificador de uma loja VTEX em um marketplace, sendo necessário que o seller tenha um ID do afiliado diferente para cada marketplace onde venda seus produtos. Isso significa que, para integrar com a Renner ou a Camicado, é preciso [configurar um afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187) exclusivo. Para criar um novo ID do afiliado, siga os passos abaixo:
 
-1. No Admin, no módulo _PEDIDOS_, clique em `Gerenciamento de pedidos`.
-2. Clique em `Configurações`.
-3. No topo da página, selecione a opção `Afiliados`.
-4. Clique em `+Novo afiliado`.
-5. Preencha os campos da tela, descritos abaixo, e em seguida clique em `Salvar`.
+1. No Admin VTEX, acesse __Configurações da loja > Pedidos > Configurações__, ou digite Pedidos na barra de busca no topo da página e e selecione *Configurações da loja / Pedidos*.  
+2. Na aba __Afiliados__, Clique em `+Novo afiliado`.  
+3. Preencha os campos da tela, descritos abaixo, e em seguida clique em `Salvar`.  
 
    - **Nome:** designação do novo afiliado.
    - **ID:** código identificador do afiliado, deve ser composto de três consoantes, sejam elas repetidas ou não. Vogais não são aceitas. A sugestão é usar RNN para a Renner, e CMD para a Camicado.
@@ -116,7 +116,7 @@ A exigência é de que você informe no mínimo o contato de um responsável por
 Alguns dos dados a serem enviados são encontrados no seu Admin, são eles:
 
 - **Nome da conta:** identificador da sua empresa no sistema da VTEX. Para encontrá-lo, acesse o Admin no módulo _CONFIGURAÇÕES DA CONTA > Gerenciamento da conta > Conta > Dados da empresa_.
-- **Dados de autenticação do sistema:** _token_ e _appKey_ definidos na etapa [Criar novo access key e secret](#criar-novo-access-key-e-secret).
+- **Dados de autenticação do sistema:** _token_ e _appKey_ definidos na etapa [Criar novo AppKey e AppToken](#criar-novo-AppKey-e-AppToken).
 - **ID do afiliado:** identificador configurado na etapa [Criar ID do afiliado](#criar-id-do-afiliado).
 - **Política comercial:** número da política comercial determinada na etapa [Definir política comercial](#definir-politica-comercial).
 - **ID do Seller:** se você estiver integrando a partir da sua conta principal, o valor a ser informado é o número 1. Caso sua loja possua contas franquia e você esteja realizando a integração a partir de uma delas, é necessário enviar o ID do Seller dessa conta. Para encontrá-lo, acesse o Admin no módulo _MARKETPLACE > Sellers > Gerenciamento > ID do Seller_.
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md b/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md
index f0d437494..050c7cb9c 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md
@@ -1,10 +1,10 @@
 ---
 title: 'Guia de integração para marketplaces - Seller não VTEX'
 id: yMji0ow0rQuYgQsg26Kus
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-10-14T21:55:39.633Z
-updatedAt: 2021-08-10T18:51:48.080Z
-publishedAt: 2021-08-10T18:51:48.080Z
+updatedAt: 2023-08-18T19:03:38.625Z
+publishedAt: 
 firstPublishedAt: 2017-10-14T22:00:36.965Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/pt/integration-with-google-tag-manager.md b/docs/tutorials/pt/integration-with-google-tag-manager.md
index 5dcc16289..fa2576d0c 100644
--- a/docs/tutorials/pt/integration-with-google-tag-manager.md
+++ b/docs/tutorials/pt/integration-with-google-tag-manager.md
@@ -3,8 +3,8 @@ title: 'Configurar o Google Tag Manager'
 id: frequentlyAskedQuestions_616
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:56.745Z
-updatedAt: 2023-05-12T15:09:43.299Z
-publishedAt: 2023-05-12T15:09:43.299Z
+updatedAt: 2023-07-17T13:33:10.627Z
+publishedAt: 2023-07-17T13:33:10.627Z
 firstPublishedAt: 2019-01-24T22:13:48.493Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -16,7 +16,7 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
 <div class="alert alert-warning">
-Se sua loja é desenvolvida com base no <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, para fazer a integração funcionar em todas as páginas é necessário também instalar o aplicativo do pixel do Google Tag Manager. Veja como fazer isso na <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">documentação sobre a app</a>.
+Se sua loja é desenvolvida com base no <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">Store framework</a>, para fazer a integração funcionar em todas as páginas é necessário também instalar o aplicativo do pixel do Google Tag Manager. Veja como fazer isso na <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">documentação sobre a app</a>.
 </div>
 
 O Google Tag Manager é um sistema de gerenciamento de tags criado pelo Google para gerenciar tags JavaScript e HTML usadas para tracking e analytics de sites da web.
@@ -49,7 +49,7 @@ Depois, você deve configurar o código de identificação da loja no Tag Manage
 4. No campo __Google Tag Manager__, insira o código de identificação da loja, no formato `GTM-XXXX`, ilustrado na imagem abaixo.
 5. Clique em `Salvar`. 
 
-![Google Tag Manager](https://images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/193fa3039dd13eba99544247affae5a6/Google_Tag_Manager_-_PT.PNG)
+![Google Tag Manager](//images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/193fa3039dd13eba99544247affae5a6/Google_Tag_Manager_-_PT.PNG)
 
 Para verificar eventos (acionadores) e variáveis disponíveis nas páginas, que serão usados nas tags, você pode utilizar o modo de visualização do Google Tag Manager. Consulte a [documentação do Google Tag Manager](https://support.google.com/tagmanager/answer/6107056?hl=pt-BR) para mais detalhes.
 
@@ -59,7 +59,7 @@ Para verificar eventos (acionadores) e variáveis disponíveis nas páginas, que
 
 ## VTEX IO: instalar pixel app do Google Tag Manager
 
-Se a sua loja utiliza [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), além da configuração, será necessário instalar uma nova versão do app Google Tag Manager. Para mais informações, acesse [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
+Se a sua loja utiliza [VTEX IO - Store Framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), além da configuração, será necessário instalar uma nova versão do app Google Tag Manager. Para mais informações, acesse [Installing Google Tag Manager](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-google-tag-manager).
 
 Esta etapa não é necessária para lojas que utilizam [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
 
diff --git a/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
index 0d30a5754..0d9de45b6 100644
--- a/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
@@ -1,10 +1,10 @@
 ---
-title: 'Sugestões de Sinônimos do Intelligent Search (Beta)'
+title: 'Sinônimos Inteligentes'
 id: 18A9JTCPrMsHWpFntNoKEr
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-06-01T20:18:10.087Z
-updatedAt: 2023-06-01T20:44:40.993Z
-publishedAt: 2023-06-01T20:44:40.993Z
+updatedAt: 2024-04-02T13:08:36.724Z
+publishedAt: 
 firstPublishedAt: 2023-06-01T20:33:35.148Z
 contentType: tutorial
 productTeam: Others
@@ -16,21 +16,25 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
 <div class="alert alert-info">
-  <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-  <p>Para os clientes selecionados, a funcionalidade está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É possível que taxas extras se apliquem futuramente.</p>
+  <p>Esta funcionalidade está  disponível para contas que tenham uma quantidade mínima de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. É possível que taxas extras se apliquem futuramente.</p>
 </div>
 
 A funcionalidade de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) permite cadastrar palavras, ou expressões de mesmo sentido, para termos de busca utilizados pelos clientes ao realizar pesquisas na sua loja, aumentando a chance deles obterem resultados relevantes nas buscas.
 
-A página de **Sinônimos** no Admin VTEX agora apresenta sugestões inteligentes de termos para cadastro, além da configuração manual de sinônimos. A plataforma sugere sinônimos a partir de inteligência artificial, com base no comportamento de busca de clientes na sua loja.
+Com a funcionalidade de Sinônimos Inteligentes, a página de **Sinônimos** no Admin VTEX apresenta recomendações inteligentes de termos para cadastro, além da configuração manual de sinônimos. A plataforma sugere sinônimos a partir de Inteligência Artificial, com base no comportamento de busca de clientes na sua loja.
 
 Para isso, o VTEX Intelligent Search contabiliza quantas vezes nos últimos 30 dias os clientes pesquisaram por um termo que resultou em poucos ou nenhum resultado de busca e substituíram o termo original por outro. 
 
-> _Exemplo:_ imagine que cinco clientes escreveram `sabonete rosto` e, em seguida, alteraram a pesquisa para `sabão rosto`. O sistema registra esse comportamento e os termos mais reescritos vão aparecer como sugestão de sinônimos.
+Por exemplo, imagine que cinco clientes escreveram `sabonete rosto` e, em seguida, alteraram a pesquisa para `sabão rosto`. O sistema registra esse comportamento e os termos mais reescritos vão aparecer como sugestão de sinônimos.
 
-Você pode revisar as sugestões geradas e optar por uma das três ações: recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
+As sugestões são exibidas em duas categorias na listagem de sinônimos, conforme a ilustração abaixo:
 
-![syn-sug-pt](https://images.ctfassets.net/alneenqid6w5/3bDrkDw6O6d8mHvvBKwWGm/e9091f09b67349b79a829e31b9969392/syn-sug-pt.png)
+* **Novas sugestões:** sugestões geradas pela plataforma que ainda não foram visualizadas.
+* **Sugestões salvas:** sugestões salvas para depois, como descrito no passo 5 da seção [Revisar sugestões](#revisar-sugestoes).
+
+![synonym-suggestion-list-pt](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
+
+Você pode revisar as sugestões geradas e optar por salvar para depois, recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
 
 ## Revisar sugestões
 
@@ -38,13 +42,21 @@ Siga as instruções para visualizar as sugestões de sinônimos e definir se el
 
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
 2. Em **Intelligent Search**, clique em **Sinônimos**.
-    Se existirem sugestões para você revisar, um modal vai aparecer, indicando a quantidade de sugestões geradas.
-3. Clique em `Revisar` para continuar. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
-4. Para revisar a sugestão, escolha uma das ações a seguir:
+3. Ao acessar a página de **Sinônimos**, se existirem sugestões ainda não revisadas, um modal vai surgir, indicando a quantidade de sugestões geradas. Nesse caso, clique em `Revisar` para analisá-las.
+
+    Se optar por clicar em `Agora não`, essas sugestões são mantidas na caixa **Novas sugestões**, indicando a quantidade de sugestões geradas. Para revisá-las, clique em `Revisar`.
+
+4. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
+
+   ![synonym-suggestion-pt](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
+
+5. Para revisar cada sugestão, escolha uma das ações a seguir:
+
+    * <i class="fas fa-bookmark"></i> **Salvar para depois:** remove a sugestão da contagem de **Novas sugestões** e passa a armazená-la na caixa **Sugestões salvas**. Para analisar as sugestões salvas posteriormente, clique em `Revisar`.
     * <i class="fas fa-times-circle"></i> **Recusar**: descarta a sugestão proposta.
-    * <i class="fas fa-pencil"></i> **Editar**: altera campos da configuração dos sinônimos sugeridos. Depois de editar, é preciso clicar em <i class="fas fa-check-circle"></i> para salvar. Para mais informações sobre os campos disponíveis, leia [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
+    * <i class="fas fa-pencil-alt"></i> **Editar**: altera campos da configuração dos sinônimos sugeridos. Depois de editar, é preciso clicar em <i class="fas fa-check-circle"></i> para salvar. Para mais informações sobre os campos disponíveis, leia [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
     * <i class="fas fa-check-circle"></i> **Aprovar**: aplica e salva a sugestão proposta.
-5. Após revisar todas as sugestões, feche o modal para acessar a listagem de sinônimos configurados na sua loja.
+6. Após revisar todas as sugestões, feche o modal para acessar a listagem de sinônimos configurados na sua loja.
 
 <div class="alert alert-error">
   <p>Uma vez que uma ação é realizada, não é possível desfazê-la, pois a próxima sugestão disponível é exibida imediatamente.</p>
diff --git a/docs/tutorials/pt/intelligent-synonyms.md b/docs/tutorials/pt/intelligent-synonyms.md
new file mode 100644
index 000000000..e410ea991
--- /dev/null
+++ b/docs/tutorials/pt/intelligent-synonyms.md
@@ -0,0 +1,69 @@
+---
+title: 'Sinônimos Inteligentes'
+id: 1rR47Kk96UgFYwh8dkDG7i
+status: PUBLISHED
+createdAt: 2024-06-17T13:41:39.402Z
+updatedAt: 2024-06-17T13:42:26.751Z
+publishedAt: 2024-06-17T13:42:26.751Z
+firstPublishedAt: 2024-06-17T13:42:26.751Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: sinonimos-inteligentes
+locale: pt
+legacySlug: sinonimos-inteligentes
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidade está  disponível para contas que tenham um número mínimo de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. É possível que taxas extras se apliquem futuramente.</p>
+</div>
+
+A funcionalidade de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) permite cadastrar palavras, ou expressões de mesmo sentido, para termos de busca utilizados pelos clientes ao realizar pesquisas na sua loja, aumentando a chance deles obterem resultados relevantes nas buscas.
+
+Com a funcionalidade de Sinônimos Inteligentes, a página de **Sinônimos** no Admin VTEX apresenta recomendações inteligentes de termos para cadastro, além da configuração manual de sinônimos. A plataforma sugere sinônimos a partir de Inteligência Artificial, com base no comportamento de busca de clientes na sua loja.
+
+Para isso, o VTEX Intelligent Search contabiliza quantas vezes nos últimos 30 dias os clientes pesquisaram por um termo que resultou em poucos ou nenhum resultado de busca e substituíram o termo original por outro. 
+
+Por exemplo, imagine que cinco clientes escreveram `sabonete rosto` e, em seguida, alteraram a pesquisa para `sabão rosto`. O sistema registra esse comportamento e os termos mais reescritos vão aparecer como sugestão de sinônimos.
+
+As sugestões são exibidas em duas categorias na listagem de sinônimos, conforme a ilustração abaixo:
+
+* **Novas sugestões:** sugestões geradas pela plataforma que ainda não foram visualizadas.
+* **Sugestões salvas:** sugestões salvas para depois, como descrito no passo 5 da seção [Revisar sugestões](#revisar-sugestoes).
+
+![synonym-suggestion-list-pt](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
+
+Você pode revisar as sugestões geradas e optar por salvar para depois, recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
+
+## Revisar sugestões
+
+Siga as instruções para visualizar as sugestões de sinônimos e definir se elas serão recusadas, editadas ou aprovadas:
+
+1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Sinônimos**.
+3. Ao acessar a página de **Sinônimos**, se existirem sugestões ainda não revisadas, um modal vai surgir, indicando a quantidade de sugestões geradas. Nesse caso, clique em `Revisar` para analisá-las.
+
+    Se optar por clicar em `Agora não`, essas sugestões são mantidas na caixa **Novas sugestões**, indicando a quantidade de sugestões geradas. Para revisá-las, clique em `Revisar`.
+
+4. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
+
+   ![synonym-suggestion-pt](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
+
+5. Para revisar cada sugestão, escolha uma das ações a seguir:
+
+    * <i class="fas fa-bookmark"></i> **Salvar para depois:** remove a sugestão da contagem de **Novas sugestões** e passa a armazená-la na caixa **Sugestões salvas**. Para analisar as sugestões salvas posteriormente, clique em `Revisar`.
+    * <i class="fas fa-times-circle"></i> **Recusar**: descarta a sugestão proposta.
+    * <i class="fas fa-pencil-alt"></i> **Editar**: altera campos da configuração dos sinônimos sugeridos. Depois de editar, é preciso clicar em <i class="fas fa-check-circle"></i> para salvar. Para mais informações sobre os campos disponíveis, leia [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
+    * <i class="fas fa-check-circle"></i> **Aprovar**: aplica e salva a sugestão proposta.
+6. Após revisar todas as sugestões, feche o modal para acessar a listagem de sinônimos configurados na sua loja.
+
+<div class="alert alert-error">
+  <p>Uma vez que uma ação é realizada, não é possível desfazê-la, pois a próxima sugestão disponível é exibida imediatamente.</p>
+</div>
+
+## Saiba mais
+
+* [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV)
+* [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL)
+* [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)
diff --git a/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md b/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md
index a7085388f..dc515ddb3 100644
--- a/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md
+++ b/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md
@@ -25,7 +25,7 @@ Comece certificando-se de ter a versão mais recente do VTEX CLI e clonando o ap
 
 Execute o comando `vtex init` e selecione `graphql getting-started`.
 
-![Screen Shot 2019-01-16 at 15.00.29](https://images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
+![Screen Shot 2019-01-16 at 15.00.29](//images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
 
 Vamos usar sua estrutura básica para adaptá-la às nossas necessidades.
 
@@ -155,15 +155,15 @@ Abra o Postman e digite a seguinte pesquisa:
 
 Escolha um ID e copie-o. Vamos colá-lo em nossa consulta.
 
-![Screen Shot 2019-01-16 at 16.14.31](https://images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
+![Screen Shot 2019-01-16 at 16.14.31](//images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
 
-![Screen Shot 2019-01-16 at 17.34.04](https://images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
+![Screen Shot 2019-01-16 at 17.34.04](//images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
 
 Agora você deve ver a luz de output à direita.
 Parabéns! Você realizou sua primeira consulta simples em tempo recorde.
 
 Voltando ao terminal, você pode olhar sob o capô e perceber o GraphQL resolvendo as consultas, como normalmente você teria feito.
-![Screen Shot 2019-01-16 at 16.29.03](https://images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
+![Screen Shot 2019-01-16 at 16.29.03](//images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
 
 **Mas e se quisermos pesquisar usando todos os filtros possíveis?**
 Vamos seguir em frente para definir uma nova estrutura de consulta e criar um novo resolver para lidar com os novos parâmetros.
@@ -279,6 +279,6 @@ query{
 
 ```
 
-![Screen Shot 2019-01-16 at 17.23.00](https://images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
+![Screen Shot 2019-01-16 at 17.23.00](//images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
 
 E é isso :)  Happy coding!
diff --git a/docs/tutorials/pt/interaction-details.md b/docs/tutorials/pt/interaction-details.md
index c2e5201cc..12237072d 100644
--- a/docs/tutorials/pt/interaction-details.md
+++ b/docs/tutorials/pt/interaction-details.md
@@ -1,10 +1,10 @@
 ---
 title: 'Gerenciamento de anúncios: detalhes da interação'
 id: 5qC6XPkyUsYPd0dqKHQNlf
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T01:16:13.273Z
-updatedAt: 2023-03-31T04:45:50.134Z
-publishedAt: 2023-03-31T04:45:50.134Z
+updatedAt: 2024-06-20T21:43:33.011Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:20:58.901Z
 contentType: tutorial
 productTeam: Channels
@@ -12,9 +12,16 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: detalhes-da-interacao
 locale: pt
 legacySlug: detalhes-da-interacao
-subcategory: 2zVauFUkYn8vgS0y0MfWeK
+subcategory: 
 ---
 
+<div class="alert alert-info">
+Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
+Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
+</div>   
+
 A página de **Detalhes da interação**, do módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE), permite que sellers visualizem de forma mais completa as interações ocorridas a um anúncio durante seu processo de envio e sincronização com um canal. Cada interação do anúncio fica disponível por dez dias a partir do seu registro.
 
 Para acessar a página de **Detalhes da interação**:
@@ -33,7 +40,7 @@ O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="
 </div>
 
 ## Cabeçalho
-![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/13e23260eaabde52ec1c38246a05be68/Interaction_details_PT_cabe__alho.jpg)
+![Interaction details PT cabeçalho](//images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/13e23260eaabde52ec1c38246a05be68/Interaction_details_PT_cabe__alho.jpg)
 O *cabeçalho* traz informações principais do anúncio para rápida visualização, como nome do SKU, logo do canal para onde foi enviado, seu ID na VTEX e ID no canal.
 
 ## Resultado da Interação
@@ -43,26 +50,26 @@ As interações, ou atualizações de  um [anúncio](https://help.vtex.com/pt/tu
 O bloco de *Resultado da Interação* informa o efeito que a interação teve sobre o anúncio, calculado a partir da combinação de registros que formam a interação. O resultado de uma interação faz com o que o sistema determine o status daquele anúncio, indicando se foi possível enviá-lo e sincronizá-lo ao canal, ou não. Resultados das interações incluem: 
 
 ### Resultado: Sucesso
-![Interaction details PT resultado sucesso](https://images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/4c0f6f4dacc479647a334304f46156ba/Interaction_details_PT_resultado_sucesso.jpg)
+![Interaction details PT resultado sucesso](//images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/4c0f6f4dacc479647a334304f46156ba/Interaction_details_PT_resultado_sucesso.jpg)
 O status de uma interação é *Sucesso* quando interações cumprem com o seu efeito esperado. Isso significa que foi possível enviar o anúncio ao canal corretamente, ou que de fato geraram atualizações em um anúncio em termos de preço, estoque ou catálogo. 
 
 ### Resultado: Falha
-![Interaction details PT resultado falha](https://images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/3818ba5ecd25b3aed73ad7c8d27950b3/Interaction_details_PT_resultado_falha.jpg)
+![Interaction details PT resultado falha](//images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/3818ba5ecd25b3aed73ad7c8d27950b3/Interaction_details_PT_resultado_falha.jpg)
 O status de uma interação é *Falha* quando interações não são realizadas por causa de um erro identificado pelo sistema. Resultados desse tipo acabam gerando o status *Erro* em um anúncio, impedindo-o de ser enviado ou atualizado corretamente no canal. 
 
 Caso o resultado da interação seja *Falha*, o bloco aponta uma lista com as falhas detectadas, onde cada uma pode ser expandida para que o seller acesse mais informações sobre o que ocorreu.
 
 ### Resultado: Aviso
-![Interaction details PT resultado aviso](https://images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/6eb5baa530de97d609c827f07344eb38/Interaction_details_PT_resultado_aviso.jpg)
+![Interaction details PT resultado aviso](//images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/6eb5baa530de97d609c827f07344eb38/Interaction_details_PT_resultado_aviso.jpg)
 O status de uma interação é *Aviso* quando existem interações que trazem mais visibilidade para as etapas ocorridas no processo de envio e atualização de um anúncio, mas não geraram atualizações de fato.
 
 ### Resultado: Processando
-![Interaction details PT resultado processing](https://images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/754b810e1c0feaeed6f79203fab2bea1/Interaction_details_PT_resultado_processing.jpg)
+![Interaction details PT resultado processing](//images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/754b810e1c0feaeed6f79203fab2bea1/Interaction_details_PT_resultado_processing.jpg)
 O status de uma interação é *Processando* quando uma interação não foi concluída e ainda deve receber mais ações. Esse é um estado transitório, considerando que quando um evento é fechado, só pode terminar em `sucesso`, `falha`, ou `aviso` como seu resultado. 
 
 ## Linha do tempo
 
-![Interaction details PT linha do tempo](https://images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/13786eef8d2ec669080b995324c507d8/Interaction_details_PT_linha_do_tempo.jpg)
+![Interaction details PT linha do tempo](//images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/13786eef8d2ec669080b995324c507d8/Interaction_details_PT_linha_do_tempo.jpg)
 Uma interação é aberta pelo sistema para dar início a uma atualização e contém uma série de registros para realizar as ações necessárias para que isso aconteça. 
 
 A linha do tempo na **Detalhes da interação** organiza cronologicamente os registros que ocorreram dentro de cada interação, sendo que as informações ficam disponíveis para consulta por dez dias. A interação é fechada pelo sistema quando seu objetivo é concluído e não existem mais registros a serem feitos. A linha do tempo da apresenta os seguintes dados:
diff --git a/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
index 9bff065ff..d226502a3 100644
--- a/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
@@ -26,7 +26,7 @@ O seguinte conjunto de dados é apresentado na tela de __Todos os pedidos__ na s
 
 Ao lado de cada um desses valores, pode-se ver uma porcentagem que representa a variação relativa aos pedidos feitos no dia de hoje.
 
-![order-metric-pt](https://images.ctfassets.net/alneenqid6w5/4H6gLOi9RSYkUG2eIM6Oc2/d6de6b0c59982229df6b5ccc152dd83a/order-metric-pt.png)
+![order-metric-pt](//images.ctfassets.net/alneenqid6w5/4H6gLOi9RSYkUG2eIM6Oc2/d6de6b0c59982229df6b5ccc152dd83a/order-metric-pt.png)
 
 No screenshot das métricas acima, podemos ver as seguintes informações:
 
diff --git a/docs/tutorials/pt/introduction-to-vtex-apis.md b/docs/tutorials/pt/introduction-to-vtex-apis.md
index 65a56ce7e..9b6e40f54 100644
--- a/docs/tutorials/pt/introduction-to-vtex-apis.md
+++ b/docs/tutorials/pt/introduction-to-vtex-apis.md
@@ -114,7 +114,7 @@ Elas ficam divididas por módulo ou funcionalidade. Entrando em um destes, você
  
 À direita dessas indicações, o Postman exibe, para cada API, um Sample Request. De acordo com a linguagem escolhida na caixa de seleção acima dele, o Sample Request mostra como seria a aplicação da requisição no código.
 
-![sample request](https://images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
+![sample request](//images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
  
 Para algumas APIs, há também uma Sample Response, que é um exemplo de resposta àquele request.
 
diff --git a/docs/tutorials/pt/inventory-data-pipeline-beta.md b/docs/tutorials/pt/inventory-data-pipeline-beta.md
new file mode 100644
index 000000000..434f47ccd
--- /dev/null
+++ b/docs/tutorials/pt/inventory-data-pipeline-beta.md
@@ -0,0 +1,95 @@
+---
+title: 'Inventário Data Pipeline (Beta)'
+id: 2IvKMZV9SNrE6ipBRQr8h2
+status: PUBLISHED
+createdAt: 2024-02-02T17:41:24.979Z
+updatedAt: 2024-07-29T19:12:57.037Z
+publishedAt: 2024-07-29T19:12:57.037Z
+firstPublishedAt: 2024-05-27T19:26:59.588Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: inventario-data-pipeline-beta
+locale: pt
+legacySlug: inventario-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+O conjunto de dados composto pela tabela `item_inventory` fornece informações sobre a disponibilidade de itens no inventário. Ele detalha a quantidade total e disponível de itens, reservas ativas, possibilidade de estoque infinito, além de incluir identificações de SKU e estoque. A tabela também registra atualizações com registro de data e hora e IDs de controle.
+
+Nesta seção você encontra as seguintes informações:
+
+- [Características dos dados de inventário](#caracteristicas-dos-dados-de-inventario)
+- [Tabela item_update_latest](#tabela-item-update-latest)
+- [Tabela: item_update_historical](#tabela-item-update-historical)
+- [Análise com item_inventory](#analises-com-item_inventory)
+- [Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados de inventário
+
+| **Característica** | **Descrição** |
+|:---:|:---:|
+| **Origem do dado** | Alimentado por informações do **módulo de logística**. |
+| **Disponibilidade** | Admin da VTEX. |
+| **Histórico** | Os dados são mantidos por dois anos, a partir de 2024 para clientes que já utilizam a plataforma VTEX. |
+| **Menor intervalo de atualização possível** | Uma hora. |
+
+## Tabela item_update_latest
+
+Conheça a seguir os campos que constituem a tabela:  
+
+| **Nome da Coluna** | **Tipo da Coluna** | **Descrição da Coluna** |
+|:---:|:---:|:---:|
+| **batch_id** | character varying(13) | Identificador usado quando os dados são carregados na tabela para controle de qualidade da ingestão de dados. |
+| **last_date** | timestamp without time zone | Data e hora da última alteração no inventário. |
+| **item_availabilty_id** | character varying(65535) | ID do esquema de inventário do SKU. |
+| **item_id** | character varying(65535) | Identificador do item. |
+| **main_account_name** | character varying(65535) | Nome da conta principal associada ao item. |
+| **account_name** | character varying(65535) | Nome da conta relacionada ao item. |
+| **is_unlimited_quantity** | boolean | Indicador booleano que indica se um SKU está sempre disponível, independentemente de sua quantidade. |
+| **quantity** | integer | Quantidade de SKU em estoque. |
+| **reserved_quantity** | integer | Unidades de SKU reservadas. Pedidos para essas reservas ainda não foram aprovados para pagamento. |
+| **reservation_id** | character varying(65535) | Identificação de uma reserva para esse item. |
+
+## Tabela: item_update_historical
+
+| **Nome da Coluna**| **Tipo da Coluna** | **Descrição da Coluna**|
+|:----:|:---:|:---:|
+| **batch_id** | character varying(13) | Identificador usado quando os dados são carregados na tabela para controle de qualidade da ingestão de dados. |
+| **created_at** | timestamp without time zone  | Data e hora da alteração no inventário. |
+| **item_availabilty_id**| character varying(65535)| ID do esquema de inventário do SKU. |
+| **item_id** | character varying(65535)| Identificador do item. |
+| **main_account_name**| character varying(65535) | Nome da conta principal associada ao item. |
+| **account_name** | character varying(65535) | Nome da conta relacionada ao item.|
+| **author_id** | character varying(65535) | Autor da alteração no inventário. |
+| **event_type** | character varying(65535) | Tipo de alteração na disponibilidade (por exemplo, criação de reserva, cancelamento de reserva, atualização de disponibilidade do item). |
+| **metadata_created_at** | timestamp without time zone| Hora em que um evento foi gerado. |
+| **is_unlimited_quantity** | boolean | Indicador booleano que indica se um SKU está sempre disponível, independentemente de sua quantidade.|
+| **quantity** | integer | Quantidade de SKU em estoque.|
+| **reserved_quantity** | integer | Unidades de SKU reservadas. Pedidos para essas reservas ainda não foram aprovados para pagamento.|
+| **reservation_id** | character varying(65535)| Identificação de uma reserva para esse item. |
+
+## Análises com inventory
+
+Veja abaixo algumas das análises possíveis com a tabela de inventário:
+
+**- Análise de níveis de inventário:** avalie se o inventário atende à demanda e identificar itens com risco de esgotamento.  
+**- Tendências de reserva de inventário:** analise a quantidade de itens reservados ao longo do tempo para identificar padrões e ajustar estratégias de gestão de inventário.  
+**- Análise de distribuição de inventário por conta:** otimize a gestão de inventário em várias contas e entender como o inventário é distribuído.  
+
+## Correlações com outros dados
+
+Os dados de inventário se correlacionam com os conjuntos de pedidos e produtos, e proporcionam análises mais abrangentes para compras, vendas e marketing. Veja alguns exemplos:  
+
+**- Interação com dados de pedidos:** a análise conjunta com os dados de pedidos oferece insights sobre a eficiência em atender às demandas dos clientes e ajuda a prever necessidades de reabastecimento.  
+**- Relação com os SKUs:** a integração com os dados de SKUs ajuda a gerenciar o inventário com base na popularidade e disponibilidade dos produtos.  
+**- Dados de compras e fornecedores:** a coordenação com os dados de compras permite manter um equilíbrio ideal no inventário, evitando superlotação ou escassez.  
+**- Análises de vendas e marketing:** a compreensão do inventário impacta diretamente as estratégias de marketing e vendas, alinhando promoções e campanhas com a disponibilidade de produtos.  
+
+### Conheça outros Conjuntos de dados
+
+- [Navegação](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagamentos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Preços](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promoção](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/pt/inventory-update-history.md b/docs/tutorials/pt/inventory-update-history.md
index 3e9740755..fb0927a4d 100644
--- a/docs/tutorials/pt/inventory-update-history.md
+++ b/docs/tutorials/pt/inventory-update-history.md
@@ -3,8 +3,8 @@ title: 'Histórico de movimentações do inventário'
 id: 5AM7xbmMzmKSEQewakamc2
 status: PUBLISHED
 createdAt: 2017-08-01T15:03:08.876Z
-updatedAt: 2023-03-29T19:59:22.057Z
-publishedAt: 2023-03-29T19:59:22.057Z
+updatedAt: 2024-04-02T18:24:14.768Z
+publishedAt: 2024-04-02T18:24:14.768Z
 firstPublishedAt: 2017-08-01T15:06:58.792Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -31,10 +31,13 @@ Para visualizar as movimentações de um SKU:
 2. Selecione o SKU de que deseja conferir o histórico. Para saber como utilizar os filtros e realizar a busca, confira o artigo [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 3. Na coluna **Última atualização,** clique no número em azul.
 4. A janela **Registro de atualizações** ficará disponível com a tabela das alterações. Cada linha corresponde a um registro de atualização, e as colunas contêm:
-    * O usuário que realizou a alteração.
-    * A data e o horário em que a atualização foi feita.
-    * A quantidade de itens antes da atualização e a quantidade de itens após a atualização.
+  * O usuário que realizou a alteração.
+  * A data e o horário em que a atualização foi feita.
+  * A quantidade de itens antes da atualização.
+  * A quantidade de itens após a atualização.
 
- <div class="alert alert-warning">
- Só é possível consultar as últimas 50 movimentações no registro de atualizações de um determinado SKU.
+<div class="alert alert-warning">
+Só é possível consultar as últimas 50 movimentações no registro de atualizações de um determinado SKU.
 </div>
+
+A quantidade total de itens na página [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) é atualizada em tempo real, mas pode haver um atraso de até 1 hora para a informação aparecer no registro de atualizações.
diff --git a/docs/tutorials/pt/kit-registration.md b/docs/tutorials/pt/kit-registration.md
index 61fbb4f9e..3c19adcc7 100644
--- a/docs/tutorials/pt/kit-registration.md
+++ b/docs/tutorials/pt/kit-registration.md
@@ -3,8 +3,8 @@ title: 'Cadastrar kit'
 id: tutorials_215
 status: PUBLISHED
 createdAt: 2017-04-27T22:13:50.843Z
-updatedAt: 2023-03-29T14:48:43.077Z
-publishedAt: 2023-03-29T14:48:43.077Z
+updatedAt: 2024-05-06T14:40:12.311Z
+publishedAt: 2024-05-06T14:40:12.311Z
 firstPublishedAt: 2017-04-27T23:02:48.663Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -26,7 +26,7 @@ Um kit pode permitir ou não que seus componentes sejam vendidos separadamente,
 
 Para a configuração do kit é necessário que os produtos que irão fazer parte dele &#8211; seus componentes &#8211; já estejam criados. Confira o exemplo abaixo:
 
-![Componentes](https://images.ctfassets.net/alneenqid6w5/6k1lQeZ7AQ4qSQ80sWy0wg/24b2af0e0aa753077e69a3a0a8de7359/Screenshot_2018-10-24_11.05.54.png)
+![Componentes](//images.ctfassets.net/alneenqid6w5/6k1lQeZ7AQ4qSQ80sWy0wg/24b2af0e0aa753077e69a3a0a8de7359/Screenshot_2018-10-24_11.05.54.png)
 
 Após a criação dos produtos componentes, podemos seguir para a configuração do kit.
 
@@ -37,7 +37,7 @@ Após a criação dos produtos componentes, podemos seguir para a configuração
 5. Caso queira um kit look, clique na opção __Kit com itens vendidos separadamente__.
 6. Clique em `Salvar`.
 
-![kit](https://images.ctfassets.net/alneenqid6w5/2ELMh0gTCcSiag28qAsAmg/68fb75589fef19ed4001aec9b3cedfa1/02-kit_PT.png)
+![kit](//images.ctfassets.net/alneenqid6w5/2ELMh0gTCcSiag28qAsAmg/68fb75589fef19ed4001aec9b3cedfa1/02-kit_PT.png)
 
 ## Associar componentes
 
@@ -52,30 +52,26 @@ Depois de criar o produto que será o kit, você precisa associar os componentes
 7. Preencha o preço unitário do SKU dentro do KIT.
 6. Clique em `Salvar`.
 
-![Adicionar componente ao kit](https://images.ctfassets.net/alneenqid6w5/3Cza8qJSEoIK6I00wa2aAU/07caa35d542518e389b66eca48bdffbb/03-add_component_to_kit_PT.gif)
+![Adicionar componente ao kit](//images.ctfassets.net/alneenqid6w5/3Cza8qJSEoIK6I00wa2aAU/07caa35d542518e389b66eca48bdffbb/03-add_component_to_kit_PT.gif)
 
-![Kit no carrinho](https://images.ctfassets.net/alneenqid6w5/239UK8f3gEQi4IKc6YeyEI/0878bffc1325d9c3f79365f7aa479ef8/04-kit_in_cart_ALL.png)
+![Kit no carrinho](//images.ctfassets.net/alneenqid6w5/239UK8f3gEQi4IKc6YeyEI/0878bffc1325d9c3f79365f7aa479ef8/04-kit_in_cart_ALL.png)
 
 ## Peso do kit
 
 O peso do kit será formado pelo somatório do peso de seus componentes. Editar o peso diretamente no novo produto Kit não irá surtir efeitos na plataforma. O simulação de frete segue a mesma regra.
 
-## Estoque
+## Inventário
 
-O estoque do kit sempre será o estoque de seus componentes. Ou seja, não é possível inserir estoque apenas no kit, é preciso inserir estoque em cada um de seus componentes independentes, a fim de atualizar o estoque do kit. 
+O [inventário](https://help.vtex.com/pt/tutorial/inventory-management--tutorials_139) do kit sempre será o inventário de seus componentes. Ou seja, não é possível inserir inventário apenas no kit, é preciso inserir inventário em cada um de seus componentes independentes, a fim de atualizar o inventário do kit. Essa informação pode ser visualizada no Admin VTEX em **Catálogo > Inventário > Gerenciamento de inventário**.
 
-Essa informação pode ser visualizada em __Estoque &amp; entrega &gt; Inventário__:
+Como todos os SKUs componentes do kit só podem ser vendidos juntos, o inventário do kit será igual ao SKU com menos itens em inventário. Quando um dos componentes não possui mais inventário, o kit não pode ser comprado.
 
-![ Alterar inventário de componentes do kit](https://images.ctfassets.net/alneenqid6w5/5ZsH4tsHV6q6s4OAy6em8k/a57829903e61fa5b00bdd6becd992051/05-manage_inventory_by_kit_PS.gif)
-
-Como todos os SKUs componentes do kit só podem ser vendidos juntos, o estoque do kit será igual ao SKU com menos itens em estoque. Quando um dos componentes não possui mais estoque, o kit não pode ser comprado.
-
-Exemplo: um kit possui dois componentes. Considere que o componente 1 possui 30 unidades em estoque e o componente 2 possui 3 unidades em estoque. Logo, apenas 3 unidades do kit poderão ser vendidas.
+Exemplo: um kit possui dois componentes. Considere que o componente 1 possui 30 unidades em inventário e o componente 2 possui 3 unidades no inventário. Logo, apenas 3 unidades do kit poderão ser vendidas.
 
 Os componentes do kit podem estar em estoques diferentes, contanto que eles sejam enviados a partir da mesma doca. Se não saírem pela mesma doca, o kit inteiro se torna indisponível. 
 
 <div class="alert alert-info">
-<p>Este cenário não acontece com um kit look, pois o kit look pode ser vendido com os componentes que restaram em estoque, sem a necessidade de se ter todos os componentes do kit com estoque.</p>
+<p>Este cenário não acontece com um kit look, pois o kit look pode ser vendido com os componentes que restaram no inventário, sem a necessidade de se ter todos os componentes do kit no inventário.</p>
 </div>
 
 ## Preço
@@ -88,7 +84,7 @@ Mas note que alterar qualquer componente irá gerar um novo preço final, atuali
 
 Alterar somente o preço final não atualiza o preço dos componentes.
 
-![Lista de preços](https://images.ctfassets.net/alneenqid6w5/6eI3atVTvq0SgOw6c2uAqa/27af79495fd4de8860c36d214196246e/06-price_list_PT.png)
+![Lista de preços](//images.ctfassets.net/alneenqid6w5/6eI3atVTvq0SgOw6c2uAqa/27af79495fd4de8860c36d214196246e/06-price_list_PT.png)
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/kr1-test.md b/docs/tutorials/pt/kr1-test.md
new file mode 100644
index 000000000..3892cde73
--- /dev/null
+++ b/docs/tutorials/pt/kr1-test.md
@@ -0,0 +1,30 @@
+---
+title: 'KR1 - TEST'
+id: 4QvsXwhDJm778DgTsMZmGw
+status: DRAFT
+createdAt: 2024-05-07T02:16:58.777Z
+updatedAt: 2024-05-07T02:22:22.011Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Undefined
+author: 
+slug: kr1-test
+locale: pt
+legacySlug: kr1-test
+subcategory: 
+---
+
+<div class="row">
+  <div class="card" style="width: 48%; margin: 10px; padding: 20px; border: 1px solid #ccc; border-radius: 5px; box-shadow: 0 2px 5px rgba(0, 0, 0, 0.1);">
+    <h2>{{ title }}</h2>
+    <p>{{ description }}</p>
+  </div>
+  <div class="card" style="width: 48%; margin: 10px; padding: 20px; border: 1px solid #ccc; border-radius: 5px; box-shadow: 0 2px 5px rgba(0, 0, 0, 0.1);">
+    <h2>{{ title2 }}</h2>
+    <p>{{ description2 }}</p>
+  </div>
+</div>
+<div class="row">
+</div>
+
diff --git a/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
new file mode 100644
index 000000000..183a47239
--- /dev/null
+++ b/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
@@ -0,0 +1,104 @@
+---
+title: 'Lead time: tempo de envio a nível de SKU'
+id: 16yv5Mkj6bTyWR1hCN2f4B
+status: PUBLISHED
+createdAt: 2023-09-22T00:32:26.416Z
+updatedAt: 2023-09-22T13:32:38.292Z
+publishedAt: 2023-09-22T13:32:38.292Z
+firstPublishedAt: 2023-09-22T01:35:53.577Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: lead-time-tempo-de-envio-a-nivel-de-sku
+locale: pt
+legacySlug: lead-time-tempo-de-envio-a-nivel-de-sku
+subcategory: 3PQwnyOcNyYgawy06oe6gE
+---
+
+Lead time é a configuração opcional do tempo de envio a nível de SKU. Isso significa que você pode definir um período de envio para o SKU de um [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e este tempo será adicionado ao prazo total de envio do pedido.
+
+A configuração do lead time é feita no contexto da [gestão do seu inventário](https://help.vtex.com/pt/tutorial/gerenciar-inventario--tutorials_139), pois se relaciona a itens em estoque e disponíveis para venda.
+
+Este artigo aborda os seguintes aspectos:
+
+- [Tempo total de envio:](#tempo-total-de-envio) como o lead time compõe o prazo de envio do pedido.
+- [Principais casos de uso:](#principais-casos-de-uso) cenários especialmente beneficiados com o lead time.
+- [Inventário do SKU:](#inventario-do-sku) forma como a plataforma se comporta quando o SKU está ou não disponível para venda.
+- [Configurar lead time:](#configurar-lead-time) como realizar a configuração pelo Admin VTEX.
+- [Configurar a contagem do lead time em dias do calendário:](#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional) etapa opcional para que a contagem do lead time seja em dias corridos, e não dias úteis, que é o padrão.
+
+<div class = "alert alert-info">
+Para configurar o lead time por API, acesse <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## Tempo total de envio
+
+Quando configurado, o lead time é um tempo adicional que compõe o prazo de envio do pedido apresentado ao cliente no checkout. A imagem abaixo apresenta como esse prazo total é composto:
+
+![lead_time_image_total_time_PT](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
+
+* **Lead time:** quantidade de tempo configurável para o SKU de um estoque. Este período pode corresponder ao tempo de manipulação ou fabricação do item, por exemplo. Essa configuração é opcional e, por padrão, está definida como zero dias.
+* [Tempo de estoque:](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137) tempo que o SKU leva para sair de um estoque para uma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Essa configuração é obrigatória, mas você pode definir o tempo igual a zero.
+* [Tempo de doca:](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) tempo que o SKU leva para sair da doca, ponto intermediário entre o estoque e a [transportadora](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE), para ser enviado para o cliente. Essa configuração é obrigatória, mas você pode definir o tempo igual a zero.
+* [Política de envio:](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) agrupa as regras e condições apresentadas aos clientes no checkout, incluindo:
+    * [Taxas de envio](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127)
+    * Horário de funcionamento da transportadora
+    * Janelas de entrega
+    * Capacidade de entrega
+    * Tipos de produtos entregáveis (modais)
+
+## Principais casos de uso
+
+Confira a seguir alguns casos de uso em que a configuração do lead time é especialmente útil.
+
+### Fornecedores externos
+
+Gerenciar com mais facilidade o tempo que um fornecedor externo, tal como uma fábrica ou fabricante, leva para produzir, manipular, despachar ou entregar um produto.
+
+### Produtos grandes e personalizáveis
+
+Para operações que vendem produtos de grandes dimensões, como móveis, ou produtos personalizáveis, o lead time facilita administrar o tempo de manipulação do produto, contribuindo para a eficiência da gestão de estoques e docas.
+
+### Dropshipping
+
+Em _dropshipping_ — quando o fornecedor envia o produto diretamente para o cliente —, configurar tempo de envio a nível de SKU significa ter mais flexibilidade para definir prazos de manipulação e envio do produto por terceiros.
+
+## Inventário do SKU
+
+A plataforma VTEX vai apresentar comportamentos diferentes a depender da disponibilidade do SKU para vendas, e as situações possíveis são as seguintes:
+
+- <i class="far fa-check-circle"></i> **Inventário com SKU:** você configura o lead time do SKU, o período é considerado no cálculo de envio do pedido e o prazo total é apresentado para o cliente na etapa do checkout.
+- <i class="fas fa-times"></i> **Inventário sem SKU:** você configura o lead time do SKU, mas o SKU não é considerado válido, pois não existem unidades disponíveis para venda.
+- <i class="far fa-check-circle"></i> **Inventário infinito:** você configura o lead time do SKU, o período é considerado no cálculo de envio do pedido e o prazo total é apresentado para o cliente na etapa do checkout. Enquanto o inventário estiver habilitado como infinito, o SKU será sempre válido para vendas.
+
+## Configurar lead time
+
+O lead time vem configurado como zero dias, e o seu limite máximo é de 365 dias. Por padrão, a contagem é feita em dias úteis, considerando feriados e demais condições da sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), mas você pode [configurar a contagem para ser em dias corridos](#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional).
+
+Para configurar o lead time de um SKU, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Catálogo > Estoque > Gerenciamento de inventário**, ou digite **Gerenciamento de inventário** na barra de busca no topo da página.
+2. Selecione o SKU do estoque que você deseja configurar. Você pode usar a barra de pesquisa e os filtros de pesquisa.
+3. Na linha do SKU e na coluna **Lead time (dias)**, digite o número de dias desejado.
+  ![lead_time_inventory_management_PT](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
+4. No canto inferior da página, clique em `Salvar`.
+
+<div class = "alert alert-info">
+Pelo Admin VTEX, o lead time é sempre configurado em dias, mas é possível configurar períodos em horas, minutos e segundos, usando o endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
+</div>
+
+## Configurar a contagem do lead time em dias do calendário (opcional)
+
+Se você deseja que o tempo do lead time seja contado em dias corridos, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Envio > Estratégia de envio > Políticas de envio**, ou digite **Políticas de envio** na barra de busca no topo da página.
+2. Encontre a política de envio desejada. Você pode utilizar a barra de pesquisa e os filtros.
+    > Para criar uma nova política de envio, veja o artigo [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
+3. Na linha da política de envio, clique no ícone menu <i class="fas fa-ellipsis-v"></i> e selecione `Editar`.
+4. Na seção **Fins de Semana e feriados**, ative os toggles desejados:
+    * <i class="fas fa-toggle-on"></i> **Entrega aos sábados**
+    * <i class="fas fa-toggle-on"></i> **Entrega aos domingos**
+    * <i class="fas fa-toggle-on"></i> **Entrega em feriados**
+
+5. Clique em `Salvar alterações`.
+
diff --git a/docs/tutorials/pt/license-manager-resources.md b/docs/tutorials/pt/license-manager-resources.md
index 1d88db967..ea2a5b181 100644
--- a/docs/tutorials/pt/license-manager-resources.md
+++ b/docs/tutorials/pt/license-manager-resources.md
@@ -3,8 +3,8 @@ title: 'Recursos do License Manager'
 id: 3q6ztrC8YynQf6rdc6euk3
 status: PUBLISHED
 createdAt: 2022-02-14T17:53:22.572Z
-updatedAt: 2022-08-24T14:51:33.355Z
-publishedAt: 2022-08-24T14:51:33.355Z
+updatedAt: 2024-06-05T13:16:40.276Z
+publishedAt: 2024-06-05T13:16:40.276Z
 firstPublishedAt: 2022-02-14T19:56:27.935Z
 contentType: tutorial
 productTeam: Identity
@@ -15,24 +15,24 @@ legacySlug: recursos-do-license-manager
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-A VTEX disponibiliza vários [perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) pré-definidos para usuários administrativos. Isso permite que colaboradores da empresa exerçam suas funções acessando o mínimo necessário de recursos. No entanto, sabemos que cada ecommerce tem suas necessidades únicas e a flexibilidade é essencial para atender a problemas específicos de negócios. 
+A VTEX disponibiliza vários [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) pré-definidos para usuários administrativos. Isso permite que colaboradores da empresa exerçam suas funções acessando o mínimo necessário de recursos. No entanto, sabemos que cada ecommerce tem suas necessidades únicas e a flexibilidade é essencial para atender a problemas específicos de negócios. 
 
-Por isso, a plataforma VTEX oferece a possibilidade de criar perfis de acessos customizados, permitindo que você escolha precisamente quais recursos poderão ser acessados por um dado perfil customizado. Abaixo, você encontra links com a descrição dos recursos da VTEX disponíveis para cada produto.
+Por isso, a plataforma VTEX oferece a possibilidade de criar perfis de acessos customizados, permitindo que você escolha precisamente quais recursos poderão ser acessados por um dado perfil customizado. Abaixo, você encontra a descrição dos recursos da VTEX disponíveis para cada produto.
 
 <div class="alert alert-danger">
-O uso irrestrito de recursos aumenta o risco de ataques às lojas por vazamento de credenciais de login com acesso a recursos críticos.
-Caso haja dúvidas sobre a descrição de um recurso específico, não hesite em nos contatar.
+  <p>O uso irrestrito de recursos aumenta o risco de ataques às lojas por vazamento de credenciais de login com acesso a recursos críticos.
+    Caso haja dúvidas sobre a descrição de um recurso específico, não hesite em nos contatar.</p>
 </div>
 
-<iframe src="https://help.vtex.com/tables/resources/pt" title="Recursos do License Manager" frameBorder="0" width="800" height="850"></iframe>
+<iframe src="https://help.vtex.com/tables/resources/pt" title="Recursos do License Manager" frameBorder="0" width="100%" height="850"></iframe>
 
 <div class = "alert alert-info">
-No aplicativo <a href="https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a>, recursos do License Manager são identificados pelas respectivas chaves.
+  <p>No aplicativo <a href="https://help.vtex.com/pt/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a>, recursos do License Manager são identificados pelas respectivas chaves.</p>
 </div>
 
 ## Recursos internos ou deprecados
 
 Na interface do License Manager, você também encontra recursos deprecados ou de uso exclusivamente interno da VTEX. Estes não têm impacto para a sua loja. São eles:
 
-<iframe src="https://help.vtex.com/tables/internalresources/pt" title="Recursos internos e deprecados" frameBorder="0" width="800" height="700"></iframe>
+<iframe src="https://help.vtex.com/tables/internalresources/pt" title="Recursos internos e deprecados" frameBorder="0" width="100%" height="700"></iframe>
 
diff --git a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
new file mode 100644
index 000000000..3b3d316b1
--- /dev/null
+++ b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -0,0 +1,66 @@
+---
+title: 'Limitar acesso à loja pela política comercial'
+id: tutorials_3063
+status: PUBLISHED
+createdAt: 2017-04-27T21:52:28.228Z
+updatedAt: 2024-05-24T19:16:43.055Z
+publishedAt: 2024-05-24T19:16:43.055Z
+firstPublishedAt: 2017-04-27T23:03:54.732Z
+contentType: tutorial
+productTeam: Master Data
+author: authors_3
+slug: limitando-acesso-a-loja-pela-politica-comercial
+locale: pt
+legacySlug: limitando-acesso-a-loja-pela-politica-comercial
+subcategory: 42hDtnYXHw5ExG6l19RP1l
+---
+
+A limitação no acesso de uma loja pode ser implementado por diversos motivos, como quando a loja possui um site B2B em que só permite que empresas cadastradas e autorizadas realizem a navegação no site ou quando é um ambiente para clientes exclusivos, por exemplo.
+
+Esse cenário pode ser atendido através do uso do Master Data v1 e da política comercial utilizada na loja.
+
+<div class="alert alert-warning">
+Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+<ul>
+<li>
+<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+Características das versões do Master Data
+</a>
+</li>
+<li>
+<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+Master Data v2
+</a>
+</li>
+</ul>
+</div>
+
+## Criar cluster de clientes
+
+O primeiro passo é a criação de um cluster que fará a identificação de quais clientes poderão acessar a loja. [Para saber como criar um cluster de clientes, acesse nosso manual](/pt/faq/como-criar-um-cluster-de-clientes/).
+
+## Alterar a política comercial
+
+Após a criação do cluster, é preciso criar a regra na política comercial para que apenas clientes dentro daquele cluster possam acessar o site.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Canais** > **Políticas comerciais**.
+2. Na política comercial utilizada, clique em __Alterar__.
+3. No campo **Regra condicional**, preencha com o valor **{NomeDoCluster}=”true”**. O valor **{NomeDoCluster}** deve ser alterado pelo nome do campo na entidade de dados.
+4. Clique no botão **Salvar**.
+
+![Catálogo PT](//images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/739b47fa293440f94bb635d0d90cfbc0/pol__ticas_comerciais_pt.png)
+
+Na configuração acima, apenas o clientes com o valor true (utilizado um campo boolean – em que os valores são verdadeiro ou falso) acessarão o site.
+
+Porém, existem outras possibilidades de configuração. Pode ser configurado, por exemplo, **NomeDoCluster="false"** – onde apenas clientes com valor **false** no campo acessarão o site ou **NomeDoCluster="silva"** – onde apenas clientes com o valor **silva** no campo utilizado para o cluster acessarão o site.
+
+## Cadastrar os clientes que poderão acessar
+
+Para um caso de B2B, onde a loja ainda não conhece quais são os clientes que poderão acessar, será necessário criar um formulário onde as empresas cadastrarão seus dados. Então, pelo Master Data a loja fará a verificação dos dados e liberação ou não do acesso à loja. [Para realizar essa configuração, acesse nosso manual para lojas B2B](/pt/tutorial/configurando-b2b-na-vtex/).
+
+## Saiba mais
+
+- [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete)
+- [Como funciona uma Política Comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+- [Criar uma política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE)
+- [Configurar política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace--tutorials_404)
diff --git a/docs/tutorials/pt/links-suiteshare.md b/docs/tutorials/pt/links-suiteshare.md
index 918f53a11..c6fcee9e6 100644
--- a/docs/tutorials/pt/links-suiteshare.md
+++ b/docs/tutorials/pt/links-suiteshare.md
@@ -23,37 +23,37 @@ Pensando nisso e também em aumentar as suas vendas, o VTEX Assisted Sales (Suit
 
 Para criar seu link é muito fácil, acesse seu painel do VTEX Assisted Sales (SuiteShare) e clique em **Atrair** e depois em **Links**.
 
-![Links 1](https://images.ctfassets.net/alneenqid6w5/33OwHBb0Nhs6sIGzWSsni5/a2b02a88970460ae4f9864408623e93e/Screenshot_2022-08-26_at_12-51-46_Links.png)
+![Links 1](//images.ctfassets.net/alneenqid6w5/33OwHBb0Nhs6sIGzWSsni5/a2b02a88970460ae4f9864408623e93e/Screenshot_2022-08-26_at_12-51-46_Links.png)
 
 Clique no botão **Novo**.
 
-![Links 2](https://images.ctfassets.net/alneenqid6w5/4tfO1ztHOuGKRLfX3IRPrP/1d794be4a6f244c3a2a937a38a699624/Screenshot_2022-08-26_at_12-51-50_Links.png)
+![Links 2](//images.ctfassets.net/alneenqid6w5/4tfO1ztHOuGKRLfX3IRPrP/1d794be4a6f244c3a2a937a38a699624/Screenshot_2022-08-26_at_12-51-50_Links.png)
 
 Escolha o País e o DDD do número e insira o número do WhatsApp da sua empresa.
 
-![Links 3](https://images.ctfassets.net/alneenqid6w5/4yepQ824DfJ05kAV5na0Ry/1d2b8f92c7ace3f8dd2010243137d56c/Screenshot_2022-08-26_at_12-51-54_Links.png)
+![Links 3](//images.ctfassets.net/alneenqid6w5/4yepQ824DfJ05kAV5na0Ry/1d2b8f92c7ace3f8dd2010243137d56c/Screenshot_2022-08-26_at_12-51-54_Links.png)
 
 Escolha o endereço do link (URL), você poderá personalizar o domínio do seu link com o nome da sua empresa. Por exemplo: `whts.co/suaempresa`.
 
-![Links 4](https://images.ctfassets.net/alneenqid6w5/6YMrf9qg0TFRVWzXWSuSLR/1a88f4096f80889c2636e9e611b595d1/Screenshot_2022-08-26_at_12-52-00_Links.png)
+![Links 4](//images.ctfassets.net/alneenqid6w5/6YMrf9qg0TFRVWzXWSuSLR/1a88f4096f80889c2636e9e611b595d1/Screenshot_2022-08-26_at_12-52-00_Links.png)
 
 Em seguida, defina a mensagem que irá aparecer pré-digitado para o usuário ao clicar no seu link. Exemplo: _Olá, vi o seu anúncio no Facebook e gostaria de saber mais, meu nome é_.
 
-![Links 5](https://images.ctfassets.net/alneenqid6w5/6LwJhOFUAuu6A6UaEGhPN6/bb3682511657bcdf0d23d19d72ab3667/Screenshot_2022-08-26_at_12-52-04_Links.png)
+![Links 5](//images.ctfassets.net/alneenqid6w5/6LwJhOFUAuu6A6UaEGhPN6/bb3682511657bcdf0d23d19d72ab3667/Screenshot_2022-08-26_at_12-52-04_Links.png)
 
 Opção avançado de mensagem (Não disponível para o plano Free).
 
 Clique em avançado no campo **Mensagem**.
 
-![Links 6](https://images.ctfassets.net/alneenqid6w5/J7lvRR5r1pzM0DoV0bkSm/62f679adde4b862f35e84296e3933108/Screenshot_2022-08-26_at_12-54-58_Links.png)
+![Links 6](//images.ctfassets.net/alneenqid6w5/J7lvRR5r1pzM0DoV0bkSm/62f679adde4b862f35e84296e3933108/Screenshot_2022-08-26_at_12-54-58_Links.png)
 
 Irá abrir as instruções para as configurações avançadas. Tenha mais de uma mensagem no mesmo link. 
 
-![Links 7](https://images.ctfassets.net/alneenqid6w5/1jaJc5jFTtiBFL1oWSDkmT/7ca67b4e57b1737ca752ba7a6cd55691/Screenshot_2022-08-26_at_12-55-04_Links.png)
+![Links 7](//images.ctfassets.net/alneenqid6w5/1jaJc5jFTtiBFL1oWSDkmT/7ca67b4e57b1737ca752ba7a6cd55691/Screenshot_2022-08-26_at_12-55-04_Links.png)
 
 Defina um **Identificador** para localizar o link de forma prática e rápida:
 
-![Links 8](https://images.ctfassets.net/alneenqid6w5/1r5L9HK5R3yjE3PrUwlJVi/6b91ff9f4b3522d216bf95304887e767/Screenshot_2022-08-26_at_12-55-08_Links.png)
+![Links 8](//images.ctfassets.net/alneenqid6w5/1r5L9HK5R3yjE3PrUwlJVi/6b91ff9f4b3522d216bf95304887e767/Screenshot_2022-08-26_at_12-55-08_Links.png)
 
 Esse Identificador é apenas para fins de organização dentro do painel do VTEX Assisted Sales (SuiteShare). 
 
@@ -61,6 +61,6 @@ Feito todas as configurações, clique no botão `Finalizar`. 
 
 Seus links irão para a lista de links. 
 
-![Links 9](https://images.ctfassets.net/alneenqid6w5/309KnK9t3XlZihSsDcXOWA/ad95b291308ffa4f007b944c8e9b4685/Screenshot_2022-08-26_at_16-29-16_Links.png)
+![Links 9](//images.ctfassets.net/alneenqid6w5/309KnK9t3XlZihSsDcXOWA/ad95b291308ffa4f007b944c8e9b4685/Screenshot_2022-08-26_at_16-29-16_Links.png)
 
 [Quer saber onde utilizar os links criados? Criamos um artigo que vai te explicar tudo.](https://help.vtex.com/pt/faq/onde-utilizar-o-link-de-whatsapp--6VbyH573udBQJ3j7kfsWeJ)
diff --git a/docs/tutorials/pt/list-of-payment-providers-by-country.md b/docs/tutorials/pt/list-of-payment-providers-by-country.md
index 4d60ac03a..d5d1ea428 100644
--- a/docs/tutorials/pt/list-of-payment-providers-by-country.md
+++ b/docs/tutorials/pt/list-of-payment-providers-by-country.md
@@ -3,8 +3,8 @@ title: 'Lista de Provedores de Pagamento por País'
 id: 2im3BEGXxSAcRuxEaIHPvp
 status: PUBLISHED
 createdAt: 2022-02-01T18:37:56.763Z
-updatedAt: 2023-04-17T15:31:26.758Z
-publishedAt: 2023-04-17T15:31:26.758Z
+updatedAt: 2023-11-13T18:15:23.134Z
+publishedAt: 2023-11-13T18:15:23.134Z
 firstPublishedAt: 2022-02-01T18:39:26.915Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: lista-de-provedores-de-pagamento-por-pais
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A VTEX oferece a possibilidade de diversos [provedores de pagamento](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete) para o seu negócio em muitos países.
+A VTEX oferece a possibilidade de diversos [provedores de pagamento](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444) para o seu negócio em muitos países.
 
 Para identificar as opções disponíveis, clique em **Search** e digite o nome do país, provedor de pagamento ou disponibilidade do Split de Recebíveis (Sim/Não). Você também pode optar por exibir 10, 25, 50 ou 100 resultados por página, selecionando o campo **Show Entries**.
 
diff --git a/docs/tutorials/pt/lista-da-vez.md b/docs/tutorials/pt/lista-da-vez.md
index d358a427f..9d8a60731 100644
--- a/docs/tutorials/pt/lista-da-vez.md
+++ b/docs/tutorials/pt/lista-da-vez.md
@@ -30,7 +30,7 @@ O aplicativo **Lista da Vez** permite organizar a fila de atendimento dos vended
 
 A aba Lista da Vez gerencia a ordem de atendimento dos vendedores da loja. Além de ordenar a fila de atendimento, também é possível identificar a situação de cada vendedor: [Esperando a vez](#esperando-a-vez), [Em atendimento](#em-atendimento) e [Fora da loja](#fora-da-loja).
 
-![lista-da-vez-PT](https://images.ctfassets.net/alneenqid6w5/0hiWrn69rcSgwI8yHktBG/c13ca4d30a1c3aa36d7dbe117890dfcd/Screenshot_20220211-131959_DuckDuckGo.jpg)
+![lista-da-vez-PT](//images.ctfassets.net/alneenqid6w5/0hiWrn69rcSgwI8yHktBG/c13ca4d30a1c3aa36d7dbe117890dfcd/Screenshot_20220211-131959_DuckDuckGo.jpg)
 
 ### Esperando a vez
 Nesta seção, os vendedores da loja estarão listados em ordem de atendimento. Para adicionar um vendedor na fila, arraste o vendedor para a coluna **Esperando a vez**.
@@ -81,12 +81,12 @@ Clique em `Concluir` para finalizar.
 ## Campanhas
 Nesta aba você pode visualizar as campanhas configuradas na plataforma da Indeva. Uma campanha é um desafio de metas para os vendedores da loja. Nela será exibida a condição da campanha, a premiação para quem completá-la e a posição dos vendedores em relação à condição.
 
-![campanha-PT](https://images.ctfassets.net/alneenqid6w5/WDPAVhqCaRb5mzkNdH9Je/8dd97addafdff96674c48d74765b4f76/Screenshot_20220215-112922_Ecosia.jpg)
+![campanha-PT](//images.ctfassets.net/alneenqid6w5/WDPAVhqCaRb5mzkNdH9Je/8dd97addafdff96674c48d74765b4f76/Screenshot_20220215-112922_Ecosia.jpg)
 
 ## Rankings
 Nesta aba serão exibidos os rankings dos vendedores da loja configurados na plataforma  da Indeva. Um ranking é uma classificação a partir de uma condição definida pela loja, com regras para os vendedores participarem e uma premiação para o primeiro colocado. 
 
-![rankings-PT](https://images.ctfassets.net/alneenqid6w5/7sieBaz6E1RJHQLmr0TOIp/47259a247043f1806a98c465efd73f78/Screenshot_20220215-112727_Ecosia.jpg)
+![rankings-PT](//images.ctfassets.net/alneenqid6w5/7sieBaz6E1RJHQLmr0TOIp/47259a247043f1806a98c465efd73f78/Screenshot_20220215-112727_Ecosia.jpg)
 
 ## Metas
 A página de Metas exibe as metas e o desempenho de um vendedor, cadastradas na plataforma da Indeva. Para acessar uma meta individual, siga os passos abaixo.
@@ -96,7 +96,7 @@ A página de Metas exibe as metas e o desempenho de um vendedor, cadastradas na
 3. Insira a senha de acesso do vendedor.
 4. Clique em `Entrar`.
 
-![metas-PT](https://images.ctfassets.net/alneenqid6w5/eSRDRLRc6bkfoAylfMQLY/f8bdb99f379d377be82c8bd39464a08d/Screenshot_20220216-124454_Ecosia.jpg)
+![metas-PT](//images.ctfassets.net/alneenqid6w5/eSRDRLRc6bkfoAylfMQLY/f8bdb99f379d377be82c8bd39464a08d/Screenshot_20220216-124454_Ecosia.jpg)
 
 Nesta página você pode visualizar as seguintes informações:
 
diff --git a/docs/tutorials/pt/locations-details-page-beta.md b/docs/tutorials/pt/locations-details-page-beta.md
index b6129e0fd..1310aadfa 100644
--- a/docs/tutorials/pt/locations-details-page-beta.md
+++ b/docs/tutorials/pt/locations-details-page-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Página de detalhes da localidade (Beta)'
 id: 3se4QBRYsNCwC8Wo56J6zG
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-05-09T16:24:38.315Z
-updatedAt: 2023-05-10T00:53:18.368Z
-publishedAt: 2023-05-10T00:53:18.368Z
+updatedAt: 2023-11-10T14:44:21.843Z
+publishedAt: 
 firstPublishedAt: 2023-05-09T20:47:55.824Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,7 +21,7 @@ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando
 
 No [módulo Localidades](https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy) do seu Admin VTEX, em **Envio > Localidades**, ao clicar sobre uma localidade você é direcionado para sua página de detalhes, como a imagem a seguir:
 
-![pagina_detalhes_image_1_PT](https://images.ctfassets.net/alneenqid6w5/6fehx8bwcHLXGXZFALiGSR/4fe303ef087c40b1eb7147ac39a949de/pagina_detalhes_image_1_PT.png)
+![pagina_detalhes_image_1_PT](//images.ctfassets.net/alneenqid6w5/6fehx8bwcHLXGXZFALiGSR/4fe303ef087c40b1eb7147ac39a949de/pagina_detalhes_image_1_PT.png)
 
 No topo da página, existe o diagrama **Status da capacidade operacional**, que apresenta em tempo real a porcentagem da capacidade da localidade que já foi consumida. O diagrama apresenta os seguintes períodos:
 
@@ -47,11 +47,11 @@ Para ver todas as ações que você pode realizar com localidades, veja o artigo
 
 Nos detalhes da localidade, é possível acompanhar o registro de todas as ações executadas pelo sistema ou por um usuário. Para isso, no topo da página, clique em `Ver histórico`:
 
-![pagina_detalhes_image_2_PT](https://images.ctfassets.net/alneenqid6w5/31OXQKO48e7bRiNn5HptZF/610023d778dd4ae1442321f20365379c/pagina_detalhes_image_2_PT.png)
+![pagina_detalhes_image_2_PT](//images.ctfassets.net/alneenqid6w5/31OXQKO48e7bRiNn5HptZF/610023d778dd4ae1442321f20365379c/pagina_detalhes_image_2_PT.png)
 
 Você será redirecionado para o **Histórico da capacidade operacional** da localidade, conforme a imagem abaixo:
 
-![pagina_detalhes_image_3_PT](https://images.ctfassets.net/alneenqid6w5/6r91diwK9rP2LVMz1qOweq/007aa6776d06df12dd56a37269e53389/pagina_detalhes_image_3_PT.png)
+![pagina_detalhes_image_3_PT](//images.ctfassets.net/alneenqid6w5/6r91diwK9rP2LVMz1qOweq/007aa6776d06df12dd56a37269e53389/pagina_detalhes_image_3_PT.png)
 
 Nesta tela, você pode:
 
@@ -63,11 +63,11 @@ Nesta tela, você pode:
 
 Quando uma localidade atinge <i class="fas fa-exclamation-triangle"></i> 100% da sua capacidade, a página de detalhes oferece uma outra opção de como aumentar essa capacidade, clicando em `Aumentar capacidade`, conforme imagem abaixo:
 
-![pagina_detalhes_image_4_PT](https://images.ctfassets.net/alneenqid6w5/3AhCW3Psea1eTlcGMZ51im/eee4c4f097cd862b465cdf5fcf9b2e00/pagina_detalhes_image_4_PT.png)
+![pagina_detalhes_image_4_PT](//images.ctfassets.net/alneenqid6w5/3AhCW3Psea1eTlcGMZ51im/eee4c4f097cd862b465cdf5fcf9b2e00/pagina_detalhes_image_4_PT.png)
 
 Feito isso, será apresentado o modal **Aumentar capacidade**, como a imagem a seguir:
 
-![pagina_detalhes_image_5_PT](https://images.ctfassets.net/alneenqid6w5/625fjXiFlU5wtL9ySZnVT4/c397d8c8e496642061cbf880d7d1736f/pagina_detalhes_image_5_PT.png)
+![pagina_detalhes_image_5_PT](//images.ctfassets.net/alneenqid6w5/625fjXiFlU5wtL9ySZnVT4/c397d8c8e496642061cbf880d7d1736f/pagina_detalhes_image_5_PT.png)
 
 Você pode configurar qual será o valor da nova capacidade e definir o período para o qual deseja aplicar a mudança. As opções são as seguintes:
 
diff --git a/docs/tutorials/pt/logistics-module-overview.md b/docs/tutorials/pt/logistics-module-overview.md
index b323337f8..5e3b5bb51 100644
--- a/docs/tutorials/pt/logistics-module-overview.md
+++ b/docs/tutorials/pt/logistics-module-overview.md
@@ -27,7 +27,7 @@ Onde é possível cadastrar a relação de **[Estoque](https://help.vtex.com/pt
 
 Onde é cadastrada a definição de valores de preço e tempo de entrega para uma determinada faixa de CEP em relação ao peso cúbico do produto, dimensões, entre outros fatores.
 
-![tarifas-envioPT](https://images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/7a4f1f361c762cc7efa4f283f5e496e7/tarifas_envio.png)
+![tarifas-envioPT](//images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/7a4f1f361c762cc7efa4f283f5e496e7/tarifas_envio.png)
 - [Tarifas de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM)
 
 ## Simulador de envio
@@ -36,35 +36,35 @@ Aqui será possível realizar uma simulação de frete e reproduzir diversos ce
 
 Este retornará os valores e as transportadoras que atendem à entrega, as dimensões e pesos dos produtos, o preço da entrega e o tempo estimado para ser realizada. Além dos detalhes adicionais sobre os valores da faixa do CEP, percentuais que variam de acordo com a faixa de peso do produto, volume, valores adicionais por grama excedente, custo para a doca, fator cúbico e peso cubado.
 
-![simulador envio](https://images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/d3a55f4de664d821c427933224346b54/simulador_envio.png)
+![simulador envio](//images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/d3a55f4de664d821c427933224346b54/simulador_envio.png)
 - [Simulação de Frete](http://help.vtex.com/pt/tutorial/simulacao-de-frete)
 
 ## Inventário
 
 Local para gerenciar e acompanhar a movimentação de estoque realizada nos produtos da loja. Tanto quanto as reservas que o produto possui naquele momento e se já foram confirmadas ou não.
 
-![gerenciar inventario](https://images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/c455c47a1c937d068901baee81e7cfd3/gerenciar_inventario.png)
+![gerenciar inventario](//images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/c455c47a1c937d068901baee81e7cfd3/gerenciar_inventario.png)
 - [Gerenciar Inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139)
 
 ## Envio por geolocalização
 
 Geolocalização é o cadastro das localizações de entrega a partir da latitude e longitude dos endereços. Aqui é permitido criar “polígonos” para um atendimento logístico específico, normalmente utilizado em zonas rurais e industriais, onde se há a divisão por lotes, por exemplo, ou em áreas de risco, onde se faz necessário excluir determinados locais dentro de uma mesma região. 
 
-![geolocalizaçao](https://images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/f3596617d3f5ba0bc5219ddd7515074f/geolocaliza__ao.png)
+![geolocalizaçao](//images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/f3596617d3f5ba0bc5219ddd7515074f/geolocaliza__ao.png)
 - [Geolocalização](http://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao)
 
 ## Pontos de retirada
 
 Em Pontos de retirada é possível excluir, editar e cadastrar um *Pickup Point*. Junto ao tradicinal "delivery" (entrega em domicílio), a feature de Pontos de Retirada agrega maior flexibilidade e melhor experiência de compra para o cliente ao permitir a ele a retirada do pedido em um ponto físico. 
 
-![pontos retirada](https://images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/4437f547b06d579f64ec05cabdb32356/pontos_retirada.png)
+![pontos retirada](//images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/4437f547b06d579f64ec05cabdb32356/pontos_retirada.png)
 
 - [Configurar Pontos de Retirada](http://help.vtex.com/pt/tutorial/configurar-pontos-de-retirada-pickup-points) 
 ## Feriados
 
 Aqui é possivel cadastrar os dias que **não** serão considerados como úteis para a sua loja. O módulo irá considerar os feriado cadastrados no cálculo de entrega dos pedido e esses dias não serâo contabilizados no prazo de entrega. 
 
-![feriado](https://images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/89ac9ae473a1696eef05c80e214b3f66/feriado.png)
+![feriado](//images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/89ac9ae473a1696eef05c80e214b3f66/feriado.png)
 - [Cadastrar Feriado](http://help.vtex.com/pt/tutorial/cadastrar-feriados)
 
 ## Configurações
diff --git a/docs/tutorials/pt/magento-suiteshare.md b/docs/tutorials/pt/magento-suiteshare.md
index 7a58e919b..7f11985f0 100644
--- a/docs/tutorials/pt/magento-suiteshare.md
+++ b/docs/tutorials/pt/magento-suiteshare.md
@@ -21,7 +21,7 @@ No Painel de Controle do **Magento**, acesse o menu **Sistema** e clique em 
 
 Na página seguinte, selecione **Visual** (Design) e então clique em **Cabeçalho HTML**:
 
-![Magento_Suiteshare](https://images.ctfassets.net/alneenqid6w5/7DnzVtmv6u7rjlUD8iyVXJ/92ff4b0de0ffee721d9307ccdd991a3d/Magento_Suiteshare.png)
+![Magento_Suiteshare](//images.ctfassets.net/alneenqid6w5/7DnzVtmv6u7rjlUD8iyVXJ/92ff4b0de0ffee721d9307ccdd991a3d/Magento_Suiteshare.png)
 
 Desça na página até encontrar o campo **Outros Scripts** e cole o código do VTEX Assisted Sales (SuiteShare) dentro dele. Não se esqueça de salvar as mudanças clicando no botão **Salvar Configurações**.
 
diff --git a/docs/tutorials/pt/making-a-master-data-field-editable.md b/docs/tutorials/pt/making-a-master-data-field-editable.md
new file mode 100644
index 000000000..ccc5385cc
--- /dev/null
+++ b/docs/tutorials/pt/making-a-master-data-field-editable.md
@@ -0,0 +1,31 @@
+---
+title: 'Tornar um campo editável no Master Data'
+id: frequentlyAskedQuestions_3049
+status: PUBLISHED
+createdAt: 2019-01-24T20:46:00.411Z
+updatedAt: 2024-06-11T16:11:17.714Z
+publishedAt: 2024-06-11T16:11:17.714Z
+firstPublishedAt: 2019-01-24T22:15:32.298Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: tornar-um-campo-editavel-no-master-data
+locale: pt
+legacySlug: como-deixar-um-campo-do-master-data-editavel
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+Um campo editável é um campo em algum formulário do Master Data em que é possível editar ou inserir informação na edição ou criação de um registro. Ou seja, é um campo em que é possível alterar seu conteúdo.
+
+Por padrão, nem todos os campos são editáveis no Master Data. Para alterar essa configuração, siga os passos abaixo.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. Na aplicação desejada, clique no símbolo de engrenagem <i class="fas fa-cog"></i>.
+3. Clique no ícone de edição  <i class="fas fa-edit"></i>  no formulário que deseja alterar.
+4. Clique na aba **Esquemas de layout**.
+5. No campo desejado, clique no ícone de edição <i class="fas fa-edit"></i>. ![master-data-editar-campo-layout](//images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/27db047819bc08ee9d597da18aed6c7f/Group_3.png)
+6. Desmarque a opção **Exibir campos de somente leitura**.
+7. Clique no botão `OK`.
+8. Clique no botão `Salvar`.
+
+Os campos alterados estarão disponíveis para edição.
diff --git a/docs/tutorials/pt/manage-the-sales-comissions-report.md b/docs/tutorials/pt/manage-the-sales-comissions-report.md
index c2a5c0d81..c2963f688 100644
--- a/docs/tutorials/pt/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/pt/manage-the-sales-comissions-report.md
@@ -63,7 +63,7 @@ A criação do relatório pode demorar caso o volume de dados analisados seja ex
 Sair da página não afetará a operação.
 </div>
 
-![comissionamento PT](https://images.ctfassets.net/alneenqid6w5/7bWvI8TAgRPvtF4kr00TbC/6a3805d30656ad30c9afae6cb3079fce/comissionamento_PT.png)
+![comissionamento PT](//images.ctfassets.net/alneenqid6w5/7bWvI8TAgRPvtF4kr00TbC/6a3805d30656ad30c9afae6cb3079fce/comissionamento_PT.png)
 
 Posteriormente, você também pode baixar o relatório recém-gerado em um link para download disponibilizado na listagem de relatórios.  
 
diff --git a/docs/tutorials/pt/managing-b2b-organizations.md b/docs/tutorials/pt/managing-b2b-organizations.md
new file mode 100644
index 000000000..b04302e6a
--- /dev/null
+++ b/docs/tutorials/pt/managing-b2b-organizations.md
@@ -0,0 +1,101 @@
+---
+title: 'Gerenciamento de organizações B2B '
+id: 1UwNCWhML3BsV6anpoUvVZ
+status: PUBLISHED
+createdAt: 2024-06-12T17:24:48.991Z
+updatedAt: 2024-06-12T17:36:48.744Z
+publishedAt: 2024-06-12T17:36:48.744Z
+firstPublishedAt: 2024-06-12T17:36:48.744Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gerenciamento-de-organizacoes-b2b
+locale: pt
+legacySlug: gerenciamento-de-organizacoes-b2b
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+O aplicativo **Organizações B2B** permite agrupar usuários B2B em organizações. É possível atribuir meios de pagamento específicos, tabelas de preços e coleções de produtos a cada organização, permitindo que todos os usuários da organização compartilhem as mesmas condições comerciais. Cada organização é segmentada em um ou mais centros de custo, com seus próprios endereços de entrega.
+
+## Acesso à organização compradora
+
+Para acessar a organização compradora no Admin VTEX, acesse **Aplicativos > Organizações e Centros de Custo B2B > Organizações** ou digite **Organizações** na barra de busca no topo da página.
+
+Para acessar a organização, siga os seguintes passos:
+
+1. Clique na aba **Organizações**.
+
+2. Clique sobre o nome da organização compradora que deseja.
+
+As organizações compradoras inclui uma lista de todas as organizações criadas em sua loja e seus status, e permite que os administradores da loja:
+
+- Adicionem novas organizações.
+
+- Acessem a página de detalhes da organização, que inclui dados da organização, centros de custo, coleções, condições de pagamento, tabelas  de preços e usuários.
+
+## Status das organizações
+
+Na coluna Status da aba Organizações é permitido visualizar o status no qual essa organização se encontra.
+
+É possível usar a barra de pesquisa para encontrar uma organização pelo nome ou filtrar as organizações por status.
+
+Cada organização pode ter um dos seguintes status:
+
+- **Ativo:** a organização foi aprovada pelos administradores da loja e está atualmente ativa.
+
+- **Em espera:** a organização está atualmente pausada, o que significa que seus usuários não podem concluir compras no momento.
+
+- **Inativo:** a organização foi desativada pelos administradores da loja, portanto, seus usuários não poderão fazer login.
+
+![Status- PT](//images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/4e8ec550596a86988e076707f570dc6e/Status-_PT.gif)
+
+## Adicionar uma nova organização
+
+Para adicionar uma nova organização no Admin VTEX, acesse Aplicativos > Organizações e Centros de Custo B2B > Organizações ou digite Organizações na barra de busca no topo da página.
+
+Para adicionar uma nova organização, siga os passos abaixo:
+
+1. Clique na aba Organizações.
+
+2. Clique em `Novo`, e selecione a opção **Adicionar individualmente**.
+
+3. Preencha as informações necessárias sobre a nova organização:
+    - **Nome da organização:** nome da organização que você deseja criar.
+    - **Nome do centro de custo:** nome do centro de custo inicial associado à organização.
+    - **País:** país onde o centro de custo está localizado.
+    - **CEP:** código postal do endereço do centro de custo.
+    - **Endereço:** nome da rua onde o centro de custo está localizado.
+    - **Número:** número do endereço onde o centro de custo está localizado.
+    - **Complemento e referência:** informação que possa complementar o endereço do centro de custo.
+    - **Bairro:** nome do bairro onde o centro de custo está localizado.
+    - **Cidade:** cidade onde o centro de custo está localizado. Isso é preenchido automaticamente com base no CEP informado.
+    - **Estado:** estado onde o centro de custo está localizado. Isso é preenchido automaticamente com base no CEP informado.
+    - **Destinatário:** nome da pessoa que receberá os pedidos no endereço informado.
+4. Clique em `Adicionar`.
+
+![Adiconar organização- PT](//images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/c0e63411db1ab4a2fd44b4592d4aeffd/Adiconar_organiza__o-_PT.gif)
+
+## Notificações por emails
+
+O aplicativo **Organizações B2B** fornece um conjunto de modelos de email a serem enviados aos usuários da organização, os quais são acionados automaticamente com base em mudanças específicas.
+
+| Nome do Template            | Destinatário                             | Acionamento                                                                                                                           |
+|-----------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| Organization Created        | Usuário com perfil de Sales Admin        | Quando a organização é criada.                                                                                                        |
+| Organization Approved       | Usuário com perfil de Organization Admin | Quando a solicitação de criação de organização é aprovada.                                                                            |
+| Organization Declined       | Usuário com perfil de Organization Admin | Quando a solicitação de criação de organização é negada.                                                                              |
+| Organization Status Changed | Usuário com perfil de Organization Admin | Quando o status da organização foi alterado.                                                                                          |
+
+Para visualizar ou customizar algum desses modelos, siga as etapas abaixo:
+
+1. No Admin VTEX, acesse **Configurações da loja > Templates de Email > Templates**.
+
+2. Na barra de pesquisa, digite **Organization**.
+
+3. Clique no modelo que deseja visualizar ou editar.
+
+4. Faça as alterações desejadas no modelo.
+
+5. Clique em `Salvar`.
+
+Para saber mais sobre a edição de modelos do Email Template, acesse nosso artigo [Criar ou editar modelos de email transacional](https://help.vtex.com/pt/tracks/transactional-emails--6IkJwttMw5T84mlY9RifRP/335JZKUYgvYlGOJgvJYxRO).
diff --git a/docs/tutorials/pt/managing-credit-with-customer-credit.md b/docs/tutorials/pt/managing-credit-with-customer-credit.md
index 069998c52..99891702d 100644
--- a/docs/tutorials/pt/managing-credit-with-customer-credit.md
+++ b/docs/tutorials/pt/managing-credit-with-customer-credit.md
@@ -69,11 +69,11 @@ Para um número reduzido de cadastros, o cliente pode criar as contas uma a uma
 - E-mail
 - Limite de crédito
 
-![CustomerCredit1](https://images.ctfassets.net/alneenqid6w5/4qFEtQ96Ylr6isBrULX16Z/30921e212931852bc69c66e6d2cef62c/CustomerCredit1.png)
+![CustomerCredit1](//images.ctfassets.net/alneenqid6w5/4qFEtQ96Ylr6isBrULX16Z/30921e212931852bc69c66e6d2cef62c/CustomerCredit1.png)
 
 Se, por outro lado, a base tem um número grande de contas, o mais indicado é importar uma planilha em formato CSV. Você pode baixar um modelo desse documento na seção Contas e preenchê-lo com as informações necessárias. Para isso, clique no botão __Importar__.
 
-![CustomerCredit2](https://images.ctfassets.net/alneenqid6w5/3Gjxyu2UOkyg7T31tpEKcW/3387e9b15b3fe91842ea4db1a714c17a/CustomerCredit2.png)
+![CustomerCredit2](//images.ctfassets.net/alneenqid6w5/3Gjxyu2UOkyg7T31tpEKcW/3387e9b15b3fe91842ea4db1a714c17a/CustomerCredit2.png)
 
 ### Grandes bases
 
diff --git a/docs/tutorials/pt/managing-delivery-capacity.md b/docs/tutorials/pt/managing-delivery-capacity.md
index 3ee3392ec..867c02c4e 100644
--- a/docs/tutorials/pt/managing-delivery-capacity.md
+++ b/docs/tutorials/pt/managing-delivery-capacity.md
@@ -3,8 +3,8 @@ title: 'Gerenciar capacidade de entrega'
 id: 2y217FQZCjD0I1n62yxVcz
 status: PUBLISHED
 createdAt: 2021-04-19T14:43:24.606Z
-updatedAt: 2023-03-24T20:39:18.594Z
-publishedAt: 2023-03-24T20:39:18.594Z
+updatedAt: 2024-03-25T20:04:31.192Z
+publishedAt: 2024-03-25T20:04:31.192Z
 firstPublishedAt: 2021-05-24T17:00:14.134Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,25 +15,25 @@ legacySlug: gerenciar-capacidade-de-entrega
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
-Você pode acompanhar a disponibilidade de janelas de entrega e a quantidade de itens/pedidos que ainda podem ser realizados em cada janela de entrega através da página de Capacidade de entrega.
+Você pode acompanhar a disponibilidade de janelas de entrega e a quantidade de itens/pedidos que ainda podem ser realizados em cada janela de entrega através da página de **Capacidade de entrega**.
 
-<div class="alert alert-warning"> 
-Para gerenciar sua capacidade de entrega você precisa ter políticas de envio previamente cadastradas, entrega agendada habilitada e capacidade de entrega previamente configurada. Leia <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de envio</a> e <a href="https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> para saber como realizar este cadastro e configuração.
-</div>
+Para gerenciar sua **Capacidade de entrega**, você precisa ter [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) previamente cadastradas, [Entrega agendada](https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) habilitada e capacidade de entrega previamente configurada.
 
-O gerenciamento da capacidade de entrega é feito ao configurar uma [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) no Admin.
+<div class="alert alert-warning">
+Para que a <a href="https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> e a <a href="https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidade de entrega</a> funcionem corretamente, você deve observar que:<p><ul><li>A soma {<a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID da política de envio} não pode exceder 60 caracteres.</li><li>Não se deve utilizar espaçamento no ID de <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">políticas de envio</a>.</li></ul></p>
+</div>
 
-Ao clicar em Capacidade de entrega, você verá uma página que contém uma lista das janelas de entrega da sua loja. A lista apresentada se refere à política de envio selecionada no filtro Política de envio e ao período selecionado no filtro Data.
+No Admin VTEX, acesse **Envio > Capacidade de entrega** ou digite **Capacidade de entrega** na barra de busca no topo da página. A **Capacidade de entrega** contém uma lista das janelas de entrega da sua loja, sendo essa lista referente à política de envio selecionada no filtro `Política de envio` e ao período selecionado no filtro `Data`.
 
 Uma vez selecionada a política de envio e a data a serem apresentadas na lista, você tem acesso às janelas de entrega cadastradas. Cada linha da lista representa uma janela de entrega e apresenta os seguintes dados:
 
 *   **Data de entrega**: as datas disponíveis para entrega.
-*   **Janela de horário de entrega**: os horários disponíveis para entrega.
+*   **Horário de entrega**: os horários disponíveis para entrega.
 *   **Capacidade**: a capacidade de entrega.
 *   **Reservado**: itens/ pedidos já reservados (compra confirmada, não pagamento confirmado).
 *   **Disponível**: quantos itens/pedidos ainda estão disponíveis para agendamento (a quantidade de capacidade menos reservado)
 *   **Status**: pode ser visível ou não visível, dependendo da janela de entrega ainda está disponível. A janela ficará com status visível para seus clientes se ela ainda estiver disponível.
 
-<div class="alert alert-warning"> 
+<div class = "alert alert-info">
 Você pode clicar em <b>EDITAR POLÍTICA DE ENVIO</b> para ser redirecionado à tela de edição da política de envio selecionada no filtro Política de envio.
 </div>
diff --git a/docs/tutorials/pt/managing-http-headers.md b/docs/tutorials/pt/managing-http-headers.md
new file mode 100644
index 000000000..9c583049c
--- /dev/null
+++ b/docs/tutorials/pt/managing-http-headers.md
@@ -0,0 +1,65 @@
+---
+title: 'Gerenciar cabeçalhos HTTP'
+id: 2cCTvwQR3Z4ENVKMJU6NK3
+status: PUBLISHED
+createdAt: 2024-06-07T17:58:18.041Z
+updatedAt: 2024-06-07T18:40:52.927Z
+publishedAt: 2024-06-07T18:40:52.927Z
+firstPublishedAt: 2024-06-07T18:40:52.927Z
+contentType: tutorial
+productTeam: Reliability
+author: YRJ73j8mt38D5TUleocQB
+slug: gerenciar-cabecalhos-http
+locale: pt
+legacySlug: gerenciar-cabecalhos-http
+subcategory: 6uJgdHqWf1Mo0rUfgxseTn
+---
+
+O HTTP (Hypertext Transfer Protocol) é um protocolo de comunicação básica usado para transferir dados na World Wide Web (WWW). Ele opera no modelo cliente-servidor, em que clientes, como navegadores, solicitam recursos como páginas da web a servidores da web. Essas requisições são trocadas em formato de mensagem, seguindo um conjunto de regras e padrões definidos pelo protocolo.
+
+Os cabeçalhos desempenham um papel fundamental na comunicação HTTP, fornecendo informações adicionais sobre a operação em andamento. Há dois tipos principais de cabeçalhos:
+
+- **Cabeçalhos de requisição:** Enviados pelo cliente ao servidor. Eles contêm informações sobre a requisição feita, como o tipo de método HTTP usado, o tipo de conteúdo aceito, cookies, entre outros.
+- **Cabeçalhos de resposta:** Enviados pelo servidor para o cliente. Fornecem informações sobre a resposta enviada, como o status da resposta, o tipo de conteúdo retornado, cookies, entre outros.
+
+<div class = "alert alert-info">
+Para mais informações, leia o guia de MDN <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP">HTTP</a> e as documentações relacionadas.
+</div>
+
+Neste guia, você aprenderá a gerenciar os cabeçalhos de resposta de segurança na sua loja desenvolvida com Store Framework.
+
+## Cabeçalhos de resposta de segurança
+
+Nas lojas do Store Framework, se você precisar adicionar ou alterar o valor de um cabeçalho de resposta de segurança, abra um ticket para o [Suporte da VTEX](https://help.vtex.com/pt/support).
+
+Veja abaixo os cabeçalhos que aceitam edição:
+
+- [**X-Frame-Options**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options): permite o controle de como os sites podem ser incorporados a outros por meio do uso de frames. Esse cabeçalho é uma medida de segurança para proteger o usuário contra ataques de [clickjacking](https://developer.mozilla.org/en-US/docs/Web/Security/Types_of_attacks#click-jacking), que ocorrem quando um hacker induz o usuário a clicar em algo em uma página da web sem o consentimento dele.
+- [**X-Content-Type-Options**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options): protege contra vulnerabilidades [MIME](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types), que podem ocorrer quando um site permite que os usuários enviem conteúdo para um site.
+- [**Content-Security-Policy (CSP)**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy): permite controlar os recursos que o usuário pode carregar em uma determinada página, evitando ataques de [cross-site scripting](https://developer.mozilla.org/en-US/docs/Glossary/Cross-site_scripting).
+- [**Strict-Transport-Security (HSTS)**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security): informa aos navegadores que o site só deve ser acessado usando HTTPS.
+- [**X-XSS-Protection**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection): informa os navegadores sobre como lidar com ataques de XSS (cross-site scripting), ativando o filtro integrado para bloquear a execução de scripts maliciosos no navegador do usuário.
+- [**Referrer-Policy**](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy): determina quais informações da página de origem são compartilhadas com a página de destino em requisições HTTP. Isso é fundamental para proteger a privacidade do usuário e a segurança do site.
+
+## Cabeçalhos personalizados
+
+É possível configurar um cabeçalho personalizado, ou seja, um valor que não padronizado e é específico para os requisitos ou as funcionalidades específicas da loja.
+
+<div class="alert alert-warning">
+Cada conta só pode adicionar um único cabeçalho personalizado.
+</div>
+
+Se você precisar configurar um cabeçalho personalizado, abra um ticket para o Suporte da VTEX, fornecendo as chaves e os valores a serem definidos, pois você será totalmente responsável por essas informações. Consulte a documentação do MDN sobre [cabeçalhos](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers) para usar como guia.
+
+Veja abaixo um exemplo de um cabeçalho personalizado:
+
+```json
+"customHeader": {
+   "key": "Strict-Transport-Security",
+   "value": "max-age=31536000; includeSubdomains; preload"
+ }
+```
+
+O valor `max-age=31536000; includeSubdomains` em um contexto de cabeçalho Strict-Transport-Security (HSTS) representa a duração máxima, em segundos, que a política HSTS deve ser aplicada pelo navegador para um domínio específico e seus subdomínios.
+
+A diretiva `preload` indica que o domínio deve ser incluído na lista de pré-carregamento do HSTS, o que garante que os navegadores compatíveis só se conectarão via HTTPS, mesmo para a requisição inicial.
diff --git a/docs/tutorials/pt/managing-page-and-template-content.md b/docs/tutorials/pt/managing-page-and-template-content.md
index 2f787743f..297423d46 100644
--- a/docs/tutorials/pt/managing-page-and-template-content.md
+++ b/docs/tutorials/pt/managing-page-and-template-content.md
@@ -30,7 +30,7 @@ Exercite sua autonomia sobre o código e construa o cenário de loja desejado de
 
 1. Selecione o bloco para o qual deseja criar um novo conteúdo. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface-pt](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
+![seta-interface-pt](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
 
 2. Clique em `Versões` no canto superior direito.
 
@@ -58,7 +58,7 @@ O Site Editor aplica configurações de conteúdo de acordo com a hierarquia de
 
 1. Selecione o bloco desejado cujo conteúdo será sobrescrito. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface-pt](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
+![seta-interface-pt](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
 
 2. O conteúdo disponível é o ativo vigente. Edite os campos com os novos valores ou clique em `Versões` para editar as configurações de outros conteúdos.
 3. Salve suas alterações.
@@ -71,7 +71,7 @@ Os conteúdos derivados do Store Theme não podem ter sua visibilidade atualizad
 
 1. Selecione o bloco desejado cujo conteúdo será excluído ou redefinido. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface-pt](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
+![seta-interface-pt](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
 
 2. Clique em `Versões` no canto superior direito.
 3. Clique no menu kebab do conteúdo desejado (três pontos).
diff --git a/docs/tutorials/pt/managing-pages.md b/docs/tutorials/pt/managing-pages.md
index b6fcda344..1d5b407b2 100644
--- a/docs/tutorials/pt/managing-pages.md
+++ b/docs/tutorials/pt/managing-pages.md
@@ -3,8 +3,8 @@ title: 'Gerenciando Páginas no Headless CMS'
 id: 3DO6rBhZ1p3zndnFu5BgRt
 status: PUBLISHED
 createdAt: 2023-03-23T19:46:08.568Z
-updatedAt: 2023-04-25T19:19:08.542Z
-publishedAt: 2023-04-25T19:19:08.542Z
+updatedAt: 2024-06-17T12:55:20.070Z
+publishedAt: 2024-06-17T12:55:20.070Z
 firstPublishedAt: 2023-03-23T20:06:47.380Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,16 +15,36 @@ legacySlug: gerenciando-paginas-beta
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-Em **Headless CMS**, você pode encontrar todas as rotas de URL e os modelos de página do site da sua loja, sendo `Global Alert Page`, `Page` and `Product Page`. Você também pode criar e associar páginas personalizadas a modelos pré-definidos e gerenciar páginas criadas diretamente no código-fonte do seu projeto de storefront.
+No **Headless CMS**, você pode gerenciar todas as rotas de URL e modelos de página do site da sua loja, incluindo as páginas `Global Alert Page`, `Page` and `Product Page`. Você também pode criar e associar páginas personalizadas a modelos pré-definidos e gerenciar páginas criadas diretamente no código-fonte do seu projeto de storefront.
 
- ![Páginas](https://images.ctfassets.net/alneenqid6w5/6rzTf5xTBpR3P8sUonA0Ms/b5478b3e93c15f6199843b8210554d2c/paginas_um.png)
+## Visão geral
+
+![Novas páginas ](//images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/5e6068b5ae50645a857916be2d6e7caa/novas_pgs._pt.png)
+
+| Opção               | Descrição                                              |
+| ------------------- | ------------------------------------------------------ |
+| Criar documento   | Cria uma nova página baseada nas opções disponíveis, por exemplo, `Product Page` ou `Home`.  |
+| Configurações (⚙️) | Abre um modal com as configurações do projeto separadas em três abas: <ul><li>**Geral:** permite editar o ID do projeto e as configurações de API ou arquivar o projeto.</li> <li>**Content-Types:** Salva os content types criados no código da loja.</li><li>**Build:** permite conectar o projeto CMS ao código-fonte via webhooks, configurando os tipos de conteúdo e as seções.</li></ul> |
+| Pesquisar      | Pesquisa por páginas específicas dentro do projeto. |
+| Status      | Filtra as páginas de acordo com o seu status: <ul><li><code>Published</code>: Páginas publicadas e já disponíveis na loja.</li> <li><code>Draft</code>: Páginas que estão em rascunho, em desenvolvimento, e ainda não foram publicadas.</li></ul>|
+| Tipo      | Filtra as páginas de acordo com o tipo de conteúdo (content type). Os tipos de conteúdo são definidos no código da sua loja. Para obter mais informações, consulte [Adding Content Types to the Headless CMS](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-2-adding-content-types-to-the-headless-cms). |
+
+## Criar uma nova página
+
+Para criar e gerenciar uma página, siga estas etapas:
 
-É possível criar e gerenciar uma página seguindo as instruções abaixo:
 1. No Admin VTEX, acesse **Headless CMS**.
-2. Clique em `CRIAR NOVO` e selecione a página desejada. 
-3. Clique em <i class="fa-solid fa-circle-plus"></i> e selecione a seção desejada.
-![Gif - páginas disponíveis](https://images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/3934fab358660137fdd190830e77dc80/Portugu__s_gif_das_paginas.gif)
-4. Nomeie a página e preencha as seções.
-5. Clique em `Publicar`.
+<div class="alert alert-warning">
+  Certifique-se de estar no projeto correto. Caso contrário, vá até o menu <b>Projeto</b> no canto superior esquerdo, selecione o nome do projeto em que deseja criar a página e continue no passo 2.
+</div>
+2. Clique em `Criar documento` e selecione o tipo de página desejado. 
+
+3. Em `Untitled`, nomeie a página.
+
+4. Clique em **Seções** e selecione a seção desejada.
+![Gif - páginas disponíveis](//images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/3934fab358660137fdd190830e77dc80/Portugu__s_gif_das_paginas.gif)
+5. Adicione mais seções, se necessário, e preencha-as.
+
+6. Clique em `Publicar`.
 
-Clicando em <i class="fa-solid fa-ellipsis-vertical"></i>, você pode escolher `Duplicar` ou `Eliminar` sua página.
+Para duplicar `Duplicar` ou `Eliminar` a página,  clique no menu **Mais ações** (`⋮`) da página.
diff --git a/docs/tutorials/pt/managing-placeholders.md b/docs/tutorials/pt/managing-placeholders.md
index c94fc3a40..1354c3c87 100644
--- a/docs/tutorials/pt/managing-placeholders.md
+++ b/docs/tutorials/pt/managing-placeholders.md
@@ -35,7 +35,7 @@ O que ele faz é criar um elemento configurável no local do código onde for in
 
 É importante inserir um valor de `id`. Este será o identificador desse placeholder no sistema.
 
-![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando o placeholder
 
@@ -43,7 +43,7 @@ Agora que o controle de placeholder foi inserido no template, vamos configurá-l
 
 Isso é feito nas configurações do layout que usa esse template.
 
-1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para inserir um objeto, clique em **add object**. 
 3. Em seguida, escolha o tipo de objeto e clique em **Adicionar**.
 4. Por fim, clique no botão **Save Settings**, no alto da página.
@@ -52,7 +52,7 @@ Agora você já pode editar o objeto inserido no placeholder.
 
 Para isso, clique no lápis dentro do objeto e, em seguida, clique em **add content**.
 
-![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Agora você pode definir o nome desse objeto, subir imagens para ele e configurar as condições em que ele vai ser renderizado, tais como o período. 
 
diff --git a/docs/tutorials/pt/managing-projects.md b/docs/tutorials/pt/managing-projects.md
new file mode 100644
index 000000000..2d7425f62
--- /dev/null
+++ b/docs/tutorials/pt/managing-projects.md
@@ -0,0 +1,134 @@
+---
+title: 'Gerenciando Projetos'
+id: 42IpDFqTVTESH8DCypJMPM
+status: PUBLISHED
+createdAt: 2023-11-01T13:45:57.091Z
+updatedAt: 2024-06-21T14:14:20.212Z
+publishedAt: 2024-06-21T14:14:20.212Z
+firstPublishedAt: 2023-11-01T19:38:50.237Z
+contentType: tutorial
+productTeam: VTEX IO
+author: 4oTZzwYoyhy1tDBwLuemdG
+slug: gerenciando-projetos
+locale: pt
+legacySlug: gerenciando-projetos
+subcategory: 27t6x0lngvjI3bnUg5AgEO
+---
+
+Projetos é uma funcionalidade do VTEX Headless CMS que simplifica o gerenciamento de vários projetos de frontend, como aplicativos móveis, sites e email marketing em uma única tela.
+
+![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
+
+Cada projeto tem suas configurações, conteúdo e marca personalizados de acordo com públicos ou objetivos específicos.
+
+Neste guia, você aprenderá como gerenciar cada projeto de frontend da sua loja.
+
+<div class="alert alert-warning">
+  <a href="https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview"> FastStore WebOps usuários</a>:As alterações feitas pelo Headless CMS no VTEX Admin, como a criação de novos tipos de conteúdo (content types), a adição de seções ou a atualização de campos, podem não aparecer automaticamente na loja uma vez que você as publique. Isso é um problema conhecido, e você deve entrar em contato com sua equipe de desenvolvimento para implementar a solução necessária. Para instruções detalhadas, consulte o artigo de problema conhecido <a href="https://help.vtex.com/pt/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW"> O aplicativo WebOps não está totalmente integrado com o Headless CMS</a>.
+</div>
+
+## Antes de começar
+Certifique-se de que os [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar`, `Settings` e `CMS GraphQL API` estão associados ao seu [Perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete). Do contrário, [crie um perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso) e adicione esses recursos a eles ou adicione esses recursos a um perfil de acesso existente.
+
+## Visão geral
+Para acessar a página de **Projetos**, entre no VTEX Admin e clique em **Storefront > Headless CMS**.
+
+![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c5a1f1ba3077c11504d9f78c1712c59e/projects-two-pt.png)
+
+| Opção               | Descrição                                              |
+| ------------------- | ------------------------------------------------------ |
+| Cartão projeto      | Abre o projeto selecionado, para que você possa criar e editar páginas do conteúdo dele.       |
+| Configurações (⚙️) | abre um modal com as configurações do projeto separadas em três abas: <ul><li>**Geral:** permite editar o ID do projeto e as configurações de API ou arquivar o projeto.</li> <li>**Content-Types:** conecta o projeto no Headless CMS ao código da loja via webhooks, configurando os tipos de conteúdo (content types) e as seções.</li><li>**Build:**  inicia e gerencia compilações do site. Define uma URL de webhook para notificações de compilação e um endpoint para visualizar as versões da página.</li></ul> |
+| Criar novo       | Abre uma página para configurar um novo projeto.       |
+
+## Criar novo projeto
+
+Crie um novo projeto para sua loja definindo as configurações gerais, como **ID do projeto** e **URL base de produção**. Para conectar um projeto Headless CMS ao código-fonte do seu projeto, você também precisará definir webhooks e configurações de build, como *URL de build do webhook* e * URL de pré-visualização*.
+
+O webhook é um endpoint HTTP que permite a comunicação automatizada entre o VTEX Headless CMS e o código-fonte do projeto. Ele permite, por exemplo, que o CMS notifique um projeto FastStore sobre alterações de conteúdo ou outros eventos, desencadeando ações como a sincronização de conteúdo em tempo real.
+
+1. Na página **Projetos**, clique em `Criar novo`.
+
+2. Na página **Novo projeto**, preencha os campos de acordo com a seção [Configurações do projeto](#configurações-do-projeto).
+
+3. Depois de definir cada campo da página, clique em `Criar` e uma mensagem de sucesso será exibida na tela.
+
+Depois de criar um novo projeto, você poderá criar páginas para ele com todas as rotas de URL e modelos de página compatíveis com a sua loja, como páginas iniciais, de produtos e de login.
+
+Para criar uma nova página, siga os passos em [Gerenciando páginas no Headless CMS](https://help.vtex.com/tutorial/managing-pages--3DO6rBhZ1p3zndnFu5BgRt)
+
+## Configurações do projeto
+As configurações do projeto permitem que você o configure de acordo com três categorias principais:
+
+- [Geral](#geral): permite editar o ID do projeto e as configurações de API, além de arquivar o projeto.
+- [Content-Types](content-types): conecta o projeto no Headless CMS ao código da loja via webhooks, configurando os tipos de conteúdo (content types) e as seções.
+- [Build](#build): inicia e gerencia compilações do site. Define uma URL de webhook para notificações de compilação e um endpoint para visualizar as versões da página.
+
+### Geral
+
+| Nome do campo               | Descrição      | Exemplo de valor |
+| --------------------------- | -------------- | ---------------- |
+| ID do projeto (obrigatório) | ID do projeto. | `FastStore`      |
+| Storefront      | Define o storefront associado a sua conta (`FastStore` ou `Personalizado`) e sua finalidade.  | Veja a seção [Storefront](#storefront) para mais informações. |
+
+#### Storefront
+
+Este campo determina as configurações de [build](#build) com base no storefront escolhido. As opções incluem:
+
+- **VTEX Storefronts**:
+
+Escolha um storefront da sua conta (por exemplo, FastStore). Os campos de [Build](#build) se ajustam automaticamente de acordo como storefront escolhido. Você ainda poderá personalizá-los posteriormente.
+
+- **Personalizado**
+   Escolher um storefront `Personalizado` oferece a flexibilidade de definir suas próprias configurações de [build](#build).
+
+### Content-Types
+
+| Nome do campo               | Descrição      | Exemplo de valor |
+| ---------------------- | --------------------- | ----------------- |
+| URL das seções | URL do webhook para receber e salvar as seções criadas no código-fonte no Headless CMS.      | `https://infra.io.vtex.com/vbase/v0/{nomedaconta}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/sections`       |
+| URL dos tipos de conteúdo      | URL do webhook para receber e salvar os tipos de conteúdo criados no código-fonte no Headless CMS.       | `https://infra.io.vtex.com/vbase/v0/{nomedaconta}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/content-types`       |
+
+### Build
+
+| Nome do campo               | Descrição      | Exemplo de valor |
+| ---------- | ---------- | ---------- |
+| URL das seções | URL do webhook para receber e salvar as seções criadas no código-fonte no Headless CMS.      | `https://infra.io.vtex.com/vbase/v0/{nomedaconta}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/sections`       |
+| URL dos tipos de conteúdo      | URL do webhook para receber e salvar os tipos de conteúdo criados no código-fonte no Headless CMS.       | `https://infra.io.vtex.com/vbase/v0/{nomedaconta}/master/buckets/vtex.admin-cms-graphql-rc/store/files/{builderId}/content-types`       |
+| URL de build do webhook       | URL do webhook para iniciar um novo build no Headless CMS quando uma página ou conteúdo é adicionado ou editado.       | `https://app.io.vtex.com/vtex.cms-builder-sf-jamstack/v1/{nomedaconta}/{workspace}/build-releases`       |
+| Salvar URL do webhook       | URL do webhook para permitir pré-visualizações do projeto em tempo real, enviando uma notificação para que você atualize a página para refletir as alterações mais recentes no Headless CMS.       |  -       |
+| URL de pré-visualização       | URL do webhook que permite a pré-visualização de páginas no Headless CMS.       | `https://{nomedaconta}.vtex.app/api/preview`       |
+
+## Editar projeto
+Após criar o projeto, você também pode editar todas as informações que definiu durante a [criação do projeto](#criar-novo-projeto).
+Na página principal **Projetos**, clique em **Configurações** (⚙️). Em seguida, um modal aparecerá com três guias de configurações: [Geral](#geral), [Content-Types](#content-types) e [Build](#build).
+
+### Restaurando a URL padrão das seções
+
+Depois de [criar o projeto](#criar-novo-projeto) e desejar editar o campo [URL das seções](#content-types), clique em `Editar`, adicione a nova URL do webhook e clique em `Salvar`. Se desejar restaurar a URL padrão, clique em `Restaurar URL padrão`.
+
+## Arquivar projeto
+O arquivamento de um projeto desativa a API e o acesso ao seu conteúdo.
+Para arquivar um projeto, siga os passos abaixo:
+
+1. Acesse **Storefront > Projetos**.
+
+2. Escolha o projeto que deseja arquivar e clique em **Configurações** (⚙️). Isso abrirá um modal.
+
+3. No modal, clique em `Arquivar projeto` na página `Geral`. Uma mensagem pop-up aparecerá confirmando se você deseja arquivar o projeto.
+![Arquivar projeto](//images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/c7410dbcff84549da3a15720a0ce68ed/projects-three-pt.png)
+4. Clique em `Arquivar`. Em seguida, será exibida uma mensagem informando que o projeto foi arquivado com sucesso.
+
+Para restaurar um projeto arquivado, siga os passos em [Restaurar projeto](#restaurar-projeto).
+
+### Restaurar projeto
+Ao restaurar um projeto, sua API é reativada e o conteúdo do projeto pode ser acessado novamente. Para restaurar um projeto, siga os passos abaixo:
+
+1. Acesse **Storefront > Projetos**.
+
+2. Clique no cartão do projeto arquivado.
+
+3. Clique em `Restaurar projeto`. Uma mensagem pop-up aparecerá confirmando se você deseja restaurar o projeto.
+
+4. Clique em `Restaurar`. Em seguida, será exibida uma mensagem informando que o projeto foi restaurado com sucesso.
+
diff --git a/docs/tutorials/pt/managing-redirects-per-binding.md b/docs/tutorials/pt/managing-redirects-per-binding.md
index 027a4b8f7..a5bf9cbb9 100644
--- a/docs/tutorials/pt/managing-redirects-per-binding.md
+++ b/docs/tutorials/pt/managing-redirects-per-binding.md
@@ -3,8 +3,8 @@ title: 'Gerenciando redirecionamentos de URL por binding '
 id: 67GAK2TCQgjvmtPXxAqREb
 status: PUBLISHED
 createdAt: 2021-04-20T15:03:54.330Z
-updatedAt: 2023-03-24T22:20:43.304Z
-publishedAt: 2023-03-24T22:20:43.304Z
+updatedAt: 2023-09-04T12:42:32.729Z
+publishedAt: 2023-09-04T12:42:32.729Z
 firstPublishedAt: 2021-05-05T18:11:25.521Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -19,14 +19,18 @@ Redirecionamentos são ferramentas para encaminhar usuários e mecanismos de bus
 
 Lojas multi-domínio pedem gerenciamento de redirecionamento por [*binding*](https://help.vtex.com/pt/tutorial/what-is-binding--4NcN3NJd0IeYccgWCI8O2W) devido, principalmente, à complexidade apresentada pelas várias URLs disponíveis simultâneamente.
 
-Com isso em mente, a VTEX permite que você gerencie seus redirecionamentos de URL de acordo com os bindings da sua loja, por meio do painel de administração.
+Com isso em mente, a VTEX permite que você gerencie seus redirecionamentos de URL de acordo com os bindings da sua loja, por meio do painel de administração. 
+
+<div class="alert alert-warning" role="alert">
+Para criar, editar ou apagar redirecionamentos, o usuário do Admin precisa ter um perfil de acesso com o <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso do License Manager</a> <strong>CMS Settings</strong>. Você pode atribuir um perfil de acesso com o recurso ao usuário seguindo as instruções do artigo <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512#editar-usuarios">Gerenciando usuários</a>, ou criar um novo perfil de acesso que inclui o recurso seguindo as instruções do artigo <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso">Perfis de acesso</a>.
+</div>
 
 No Admin VTEX:
 
 1. Acesse **Storefront > Pages**.
 2. Clique na aba **Redirecionamentos**.
 
-![pt-redirecttab](https://images.ctfassets.net/alneenqid6w5/5L8GV385HAeTQqBjQ3uAS4/e3a177caafdb271ce78b94c86f9add4f/pt-redirecttab.png)
+![pt-redirecttab](//images.ctfassets.net/alneenqid6w5/5L8GV385HAeTQqBjQ3uAS4/e3a177caafdb271ce78b94c86f9add4f/pt-redirecttab.png)
 
 ## Criando redirecionamentos manualmente
 
@@ -36,7 +40,7 @@ No Admin VTEX:
 4. Defina se o seu redirecionamento será permanente ou temporário - caso o seu redirecionamento seja temporário, você pode selecionar o botão `Este redirecionamento tem uma data de término` para definir uma data de término para ele.
 5. Salve as suas alterações.
 
-![pt-newredirect](https://images.ctfassets.net/alneenqid6w5/1qnEjsKieoskStnq0Bvl2P/0d02ab19801b3c6fea8e8b2a78ae4ef9/pt-newredirect.png)
+![pt-newredirect](//images.ctfassets.net/alneenqid6w5/1qnEjsKieoskStnq0Bvl2P/0d02ab19801b3c6fea8e8b2a78ae4ef9/pt-newredirect.png)
 
 ## Excluindo redirecionamentos manualmente
 
@@ -44,7 +48,7 @@ No Admin VTEX:
 2. Clique no botão `Excluir`.
 3. Confirme sua ação.
 
-![pt-redirectdelete](https://images.ctfassets.net/alneenqid6w5/3dRsZxKTYJTaOPrm6rBU84/3e5a9c1f27986e34fa7fd7b32f1a636e/pt-redirectdelete.png)
+![pt-redirectdelete](//images.ctfassets.net/alneenqid6w5/3dRsZxKTYJTaOPrm6rBU84/3e5a9c1f27986e34fa7fd7b32f1a636e/pt-redirectdelete.png)
 
 <div class="alert alert-warning">
 Um <i>bug</i> pode ser encontrado ao tentar clicar em redirecionamentos com parâmetros de consulta na URL (<i>query strings</i>). O time de produto da VTEX já está ciente do comportamento inesperado e trabalhando na correção. Caso você não consiga clicar no redirecionamento desejado para excluí-lo, prefira fazê-lo por meio da importação da planilha enquanto o problema não é resolvido.
@@ -73,7 +77,7 @@ Os redirecionamentos listados na planilha serão obrigatoriamente criados ou exc
 4. Clique no botão `Importar`.
 5. Marque o botão `Salvar` ou` Excluir` de acordo com o seu cenário.
 
-![pt-planilharedirect](https://images.ctfassets.net/alneenqid6w5/1Vjku4KoOrCbO7mcdehcCt/e7979dca1ef4b2f159bb3c09a42d9716/pt-planilharedirect.png)
+![pt-planilharedirect](//images.ctfassets.net/alneenqid6w5/1Vjku4KoOrCbO7mcdehcCt/e7979dca1ef4b2f159bb3c09a42d9716/pt-planilharedirect.png)
 
 <div class="alert alert-warning">
 Ao clicar no botão <code>Salvar</code>, você criará todos os redirecionamentos listados em sua planilha, ao passo que clicar no botão <code>Excluir</couirde> removerá todos eles do banco de dados de redirecionamentos da sua loja.
diff --git a/docs/tutorials/pt/managing-shipping-policies.md b/docs/tutorials/pt/managing-shipping-policies.md
new file mode 100644
index 000000000..2cacc19f4
--- /dev/null
+++ b/docs/tutorials/pt/managing-shipping-policies.md
@@ -0,0 +1,116 @@
+---
+title: 'Gerenciar políticas de envio'
+id: 30nynylgbWieimhaMtGTIE
+status: PUBLISHED
+createdAt: 2024-01-30T16:15:33.582Z
+updatedAt: 2024-01-31T13:48:35.723Z
+publishedAt: 2024-01-31T13:48:35.723Z
+firstPublishedAt: 2024-01-31T00:54:58.302Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: gerenciar-politicas-de-envio
+locale: pt
+legacySlug: gerenciar-politicas-de-envio
+subcategory: 7fTH6bP0C4IaM8qWi0kkQC
+---
+
+[Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) é um conjunto de regras e configurações que definem quais opções de envio serão apresentadas aos clientes no checkout. A relação entre política de envio, [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) é o que compõe a sua [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) na VTEX, conforme a imagem abaixo:
+
+![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
+
+Este artigo apresenta como acompanhar e gerenciar suas políticas de envio. No Admin VTEX, em **Envio > Estratégia de envio**, a aba **Políticas de envio** é onde você realiza as seguintes ações:
+
+* [Visualizar lista de políticas de envio](#visualizar-lista-de-politicas-de-envio)
+* [Pesquisar política de envio](#pesquisar-politica-de-envio)
+* [Filtrar políticas de envio](#filtrar-politicas-de-envio)
+* [Ver Painel de Transportadoras](#ver-painel-de-transportadoras-opcional) (opcional)
+* [Editar política de envio](#editar-politica-de-envio)
+* [Ativar ou desativar política de envio](#ativar-ou-desativar-politica-de-envio)
+* [Excluir política de envio](#excluir-politica-de-envio)
+
+<div class = "alert alert-info">
+Também é possível criar políticas de envio, confira o passo a passo no artigo <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">Criar uma política de envio</a>.
+</div>
+
+## Visualizar lista de políticas de envio
+
+No Admin VTEX, ao acessar **Envio > Estratégia de envio**, na aba **Políticas de envio** você encontra uma lista como na imagem abaixo:
+
+![shipping_policy_PT](//images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/8f71ffc10c5e9e530c7f7d122de84005/shipping_policy_PT.png)
+
+As informações apresentadas nessa página estão descritas na tabela a seguir: 
+
+| **Coluna** | **Descrição** |
+| :---: | :--- |
+| Política de envio | Nome que identifica a sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) para usuários com acesso ao seu Admin VTEX. Saiba mais no artigo [Criar uma política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT). |
+| Tipo de envio | <p><a href="https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-envio--tutorials_126">Tipo de envio</a>, ou método de envio, é o nome que você configura na política de envio que aparece para os clientes no checkout. Por isso, é importante utilizar nomes intuitivos ao criar uma política de envio.</p><p>Exemplo: <code>Entrega expressa</code> e <code>Entrega normal</code>.</p> |
+| Docas | Identifica quais [docas](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) estão associadas à [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Ao passar o mouse sobre o número nesta coluna, você visualiza os nomes de todas as docas associadas à política de envio. |
+| Status | <p>Status de ativação da política de envio, que pode ser:</p><p><ul><li><b>Ativa:</b> a política de envio está ativada e é considerada válida no <a href="https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116">cálculo</a> para o envio de pedidos.</li><li><b>Inativa:</b> a política de envio está desativada e não é válida para envios.</li></ul></p> |
+| Transportadora (opcional) | Este campo aparece somente no Admin VTEX de lojas que ativaram o [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) ou que contrataram o [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs), e identifica exclusivamente os Correios. |
+| Contrato (opcional) | <p>Este campo aparece somente no Admin VTEX de lojas que ativaram o <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa">VTEX Shipping Network Correios</a>.</p><p>Os valores possíveis são:<ul><li><b>VTEX:</b> a loja contratou uma tabela dos Correios intermediada pela VTEX.</li><li><b>Próprio:</b> a loja contratou uma tabela por conta própria antes de ativar o VTEX Shipping Network Correios.</li></ul></p> |
+
+## Pesquisar política de envio
+
+Na caixa de busca com o ícone lupa <i class="fas fa-search"></i>, é possível buscar políticas de envio pelo nome. Ao digitar um caractere na barra de busca, a pesquisa é imediatamente realizada. Para limpar a busca, clique no ícone fechar <i class="far fa-times-circle"></i>.
+
+<div class = "alert alert-info">
+Caso não haja um resultado para a pesquisa, verifique a ortografia usada na busca e se existe algum filtro selecionado.
+</div>
+
+## Filtrar políticas de envio
+
+É possível filtrar políticas pelo seu status, que pode ser `Ativa` ou `Inativa`, veja a seguir o passo a passo:
+
+1. No Admin VTEX, acesse **Envio > Estratégia de Envio**, ou digite **Estratégia de envio** na barra de busca no topo da página.
+2. Na aba **Políticas de envio**, clique em `Status`.
+3. Selecione uma das opções de status, que pode ser:
+    * **Ativa:** a política de envio está ativada e é considerada válida no [cálculo](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) para o envio de pedidos.
+    * **Inativa:** a política de envio está desativada e não é válida para envios.
+4. Clique em `Aplicar`.
+
+Para remover o filtro aplicado, clique em `Status` e depois em `Limpar`.
+
+### Filtro para tipos de contrato (opcional)
+
+As lojas que contrataram o [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) ou ativaram o [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) podem pesquisar por tipo de contrato, os valores existentes são:
+
+* `VTEX`: a contratação da tabela dos Correios foi intermediada pela VTEX.
+* `Próprio`: a contratação da tabela dos Correios foi feita pela própria loja.
+
+## Ver Painel de Transportadoras (opcional)
+
+As lojas que contrataram o [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) ou ativaram o [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) têm na página de **Políticas de envio** o botão `Painel de Transportadoras`. Clicando nele, o usuário é redirecionado para o [Painel VTEX Shipping Network](https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92), onde gerencia a operação das transportadoras usadas nesses produtos.
+
+## Editar política de envio
+
+Para editar uma política de envio, realize os passos abaixo:
+
+1. No Admin VTEX, acesse **Envio > Estratégia de Envio**, ou digite **Estratégia de envio** na barra de busca no topo da página.
+2. Na aba **Políticas de envio**, na linha correspondente à política desejada, clique no ícone menu <i class="fas fa-ellipsis-v"></i>. Você pode [pesquisar](#pesquisar-politica-de-envio) ou [filtrar](#filtrar-politicas-de-envio) políticas.
+3. Clique em `Editar`.
+4. Realize as alterações desejadas. Para informações sobre os campos, veja o artigo [Criar uma política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
+5. Clique em `Salvar alterações`.
+
+## Ativar ou desativar política de envio
+
+Para ativar ou desativar uma política de envio, realize os passos abaixo:
+
+1. No Admin VTEX, acesse **Envio > Estratégia de Envio** ou digite **Estratégia de envio** na barra de busca no topo da página.
+2. Na aba **Políticas de envio**, na linha correspondente à política desejada, clique no ícone menu <i class="fas fa-ellipsis-v"></i>. Você pode [pesquisar](#pesquisar-politica-de-envio) ou [filtrar](#filtrar-politicas-de-envio) políticas.
+3. Clique em `Ativar` ou `Desativar`, conforme desejar.
+4. No modal aberto, clique novamente em `Ativar` ou `Desativar`.
+
+## Excluir política de envio
+
+Para excluir uma política de envio, realize os passos abaixo:
+
+<div class="alert alert-danger">
+A ação de excluir uma política de envio é permanente e não pode ser desfeita.
+</div>
+
+1. No Admin VTEX, acesse **Envio > Estratégia de Envio** ou digite **Estratégia de envio** na barra de busca no topo da página.
+2. Na aba **Políticas de envio**, na linha correspondente à política desejada, clique no ícone menu <i class="fas fa-ellipsis-v"></i>. Você pode [pesquisar](#pesquisar-politica-de-envio) ou [filtrar](#filtrar-politicas-de-envio) políticas.
+3. Clique em `Excluir`.
+4. No modal aberto, clique novamente em `Excluir`.
+
diff --git a/docs/tutorials/pt/managing-singleton-content-types.md b/docs/tutorials/pt/managing-singleton-content-types.md
index 3e4152714..e30cfea8e 100644
--- a/docs/tutorials/pt/managing-singleton-content-types.md
+++ b/docs/tutorials/pt/managing-singleton-content-types.md
@@ -3,8 +3,8 @@ title: 'Gerenciando content types do tipo Singleton'
 id: VBibMN1BqV2OFmavUFCdo
 status: PUBLISHED
 createdAt: 2023-04-05T17:55:26.748Z
-updatedAt: 2023-04-06T19:11:57.614Z
-publishedAt: 2023-04-06T19:11:57.614Z
+updatedAt: 2024-06-05T19:07:02.549Z
+publishedAt: 2024-06-05T19:07:02.549Z
 firstPublishedAt: 2023-04-06T19:11:57.614Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,13 +15,13 @@ legacySlug: gerenciando-content-types-do-tipo-singleton
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-Content types do tipo Singleton permite a criação e gerenciamento de uma única página, garantindo que apenas uma página desse content type exista no Headless CMS.
+Content types do tipo Singleton permitem a criação e o gerenciamento de uma única página, garantindo que apenas uma página desse content type exista no Headless CMS.
 
 Esse content type evita conflitos e inconsistências que podem ocorrer quando várias páginas do mesmo content type são criadas. Por exemplo, você poder usar o Singleton para a Página Inicial (Home) da sua loja, garantindo que exista apenas uma Página Inicial e todas as atualizações e solicitações feitas a essa página sempre retornem o mesmo resultado.
-![singleton-br](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
+![singleton-br](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Para criar um content type Singleton, verifique com o seu time de desenvolvimento se a propriedade <i>isSingleton</i> já está implementada ou peça para que o time siga as intruções em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using `isSingleton` in a content type</a> para adicioná-la ao content type desejado.
+<div class="alert alert-warning">
+Para criar um content type Singleton, verifique com o seu time de desenvolvimento se a propriedade <i>isSingleton</i> já está implementada ou peça para que o time siga as intruções em <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> para adicioná-la ao content type desejado.
 </div>
 
 ## Criando o Singleton
@@ -29,7 +29,7 @@ Para criar um content type Singleton, verifique com o seu time de desenvolviment
 2. Selecione `CRIAR NOVO` e escolha o nome do content type singleton, por exemplo, **Home**.
 3. Edite a página como desejar com novas seções.
 
-<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
 É possível criar o Singleton apenas uma vez. Se você já criou a página Singleton, ela não aparecerá mais na lista de content types.
 </div>
 
@@ -38,14 +38,27 @@ Para editar ou excluir um conteúdo, verifique as seções a seguir.
 
 ## Editando o Singleton
 1. Access the **Admin > Storefront > Headless CMS**.
-2. Selecione o Singleton criado, por exemplo **Home**.
-3. Na página **Home**, edite como desejar adicionando novas seções.
+2. Clique no projeto onde está o Singleton criado.
+3. Selecione o Singleton criado, por exemplo **Home**.
+4. Na página **Home**, edite como desejar adicionando novas seções.
+
+## Despublicando o Singleton
+1. Acesse **Admin > Storefront > Headless CMS**.
+2. Clique no projeto em que o Singleton foi criado.
+3. Clique em `Despublicar` > `Despublicar agora`.
+
+<div class="alert alert-warning">
+Antes de despublicar, certifique-se de que não há nenhum rascunho existente. Caso contrário, não será possível continuar. Se houver rascunhos, exclua-os ou agende-os para publicação.
+</div>
+
+4. Uma mensagem pop-up aparecerá para você confirmar a despublicação da página.
+5. Mantenha o botão `DESPUBLICAR` clicado para despublicar o conteúdo.
 
 ## Deletando o Singleton
 1. Na página do Singleton, selecione `mais`(menu kebab) e clique `Excluir`.
 2. Clique  `EXCLUIR` e, depois, clique em `VOLTAR PARA PÁGINAS`. 
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+<div class="alert alert-warning">
   Se você deseja restaurar a página e seu conteúdo, clique <i>RESTAURAR</i>.
 </div>
 
diff --git a/docs/tutorials/pt/managing-stock-items.md b/docs/tutorials/pt/managing-stock-items.md
index 37a80d924..075a46247 100644
--- a/docs/tutorials/pt/managing-stock-items.md
+++ b/docs/tutorials/pt/managing-stock-items.md
@@ -3,8 +3,8 @@ title: 'Gerenciar inventário'
 id: tutorials_139
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:21.085Z
-updatedAt: 2023-03-31T00:44:36.047Z
-publishedAt: 2023-03-31T00:44:36.047Z
+updatedAt: 2024-04-18T15:25:20.097Z
+publishedAt: 2024-04-18T15:25:20.097Z
 firstPublishedAt: 2017-04-27T23:00:44.889Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,55 +15,50 @@ legacySlug: gerenciar-itens-em-estoque
 subcategory: 3PQwnyOcNyYgawy06oe6gE
 ---
 
-Na VTEX, o inventário é a relação entre os itens de venda de uma loja e os locais onde esses itens estão armazenados. Acesse o Admin VTEX e clique em **Catálogo > Estoque > Gerenciamento de inventário** para visualizar os SKUs cadastrados no [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) e seus respectivos [estoques](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb). 
+Na VTEX, [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) é a identificação dos locais físicos de armazenamento de produtos da loja, e inventário é a relação dos estoques com os SKUs disponíveis para venda. Para visualizar os SKUs cadastrados no seu [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR) e respectivos estoques, acesse o Admin VTEX em **Catálogo > Inventário > Gerenciamento de inventário**.
 
-Outras ações possíveis na página **Gerenciamento de inventário** são:
-
-* [Acompanhar o histórico de movimentações do inventário](https://help.vtex.com/pt/tutorial/como-analisar-o-historico-de-movimentacoes-do-estoque--5AM7xbmMzmKSEQewakamc2).
-* Conferir se os SKUs têm [unidades reservadas](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#como-acompanhar-o-status-da-reserva).
-* [Atualizar a quantidade de SKUs que estão disponíveis para venda](https://help.vtex.com/pt/tutorial/atualizar-quantidade-de-skus-em-estoque--IKMWjOjMcMqKusSGko8c0). 
-
-<div class="alert alert-info"> 
-Lembre-se de que <b>estoque</b> é a identificação dos locais físicos de armazenamento de produtos da loja, e <b>inventário</b> é a relação dos estoques com os SKUs disponíveis para venda.
-</div>
-
-Esse artigo contém as informações do inventário no Admin VTEX utilizando a seção `Gerenciamento de inventário`. Entenda como:
+Este artigo contém informações sobre a página **Gerenciamento de inventário**. Aprenda como:
 
 * [As informações do inventário estão divididas](#informacoes-do-inventario).
-* [Os filtros de busca estão dispostos para facilitar a procura de SKUs específicos.](#filtros-de-busca).
+* [Os filtros de busca estão dispostos para facilitar a procura de SKUs específicos](#filtros-de-busca).
 
 <div class="alert alert-info"> 
 Para acessar o inventário utilizando SKUs, docas ou estoques via API, utilize a <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-"> Inventory API </a>.
 </div>
 
-## Informações do inventário
+Outras ações possíveis na página **Gerenciamento de inventário** são:
 
-No Admin VTEX, acesse **Catálogo > Estoque > Gerenciamento de inventário**, ou digite **Gerenciamento de inventário** na barra de busca no topo da página.
+* [Acompanhar o histórico de movimentações do inventário](https://help.vtex.com/pt/tutorial/como-analisar-o-historico-de-movimentacoes-do-estoque--5AM7xbmMzmKSEQewakamc2).
+* Conferir se os SKUs têm [unidades reservadas](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#como-acompanhar-o-status-da-reserva).
+* [Atualizar a quantidade de SKUs que estão disponíveis para venda](https://help.vtex.com/pt/tutorial/atualizar-quantidade-de-skus-em-estoque--IKMWjOjMcMqKusSGko8c0). 
 
-Uma tabela ficará disponível com os SKUs e seus respectivos estoques. A tabela está organizada da seguinte forma:
+## Informações do inventário
+
+No Admin VTEX, acesse **Catálogo > Inventário > Gerenciamento de inventário**, ou digite **Gerenciamento de inventário** na barra de busca no topo da página. Uma tabela ficará disponível com os SKUs e seus respectivos estoques. A tabela está organizada da seguinte forma:
 
 * **Linhas**: cada linha contém as informações de um SKU e de um estoque. Assim, é possível conferir os detalhes de cada SKU por estoque. 
 * **Colunas**: identificam diferentes aspectos do SKU em um estoque e estão dividas em:
     * **Produtos:** o nome do produto.
     * **Estoque**: em qual estoque da loja o SKU está.
     * **ID do SKU:** código identificador do SKU.
-    * **Última atualização**: número de unidades do SKU mais recente registrado na plataforma VTEX. <p>É possível clicar nos valores desse campo para conferir o **Registro de atualizações**, com informações sobre os usuários que atualizaram esse campo, as datas em que ocorreram as alterações, e as quantidades antes e depois das atualizações</p>
+    * **Última atualização**: número de unidades do SKU mais recente registrado na plataforma VTEX.<p><div class = "alert alert-info">Ao clicar em qualquer valor da coluna <b>Última atualização</b>, a janela <a href="https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2">Registro de atualizações</a> ficará disponível com a tabela das alterações. Cada linha corresponde a um registro de atualização, e as colunas contêm o usuário que realizou a alteração, a data da atualização e a quantidade de itens antes e depois da atualização. Só é possível consultar até as últimas 50 movimentações de um SKU.</div></p>
     * **Reservados:** unidades de itens do SKU reservados. Os pedidos dessas reservas ainda não estão com o pagamento aprovado. 
     Ao clicar nos valores dessa coluna para conferir detalhes sobre os dados das reservas do SKU,  você será redirecionado para o gerenciamento de pedidos. Para saber mais sobre como consultar uma reserva, veja [Como acompanhar o status da reserva](https://help.vtex.com/pt/tutorial/how-does-reservation-work--tutorials_92#como-acompanhar-o-status-da-reserva)
     * **Enviados:** unidades despachadas do SKU. Os itens desta coluna são de pedidos com status `Pagamento aprovado`, `Preparando entrega` ou `Faturado`. <p>Ao clicar nos itens da coluna para conferir detalhes de SKUs enviados, você será redirecionado para o gerenciamento de pedidos.</p>
     * **Disponíveis:** unidades do SKU disponíveis para venda.
     * **Atualizar contagem:** campo para atualização manual da quantidade disponível de itens do SKU. Para saber mais sobre como atualizar a contagem, confira o artigo [Atualizar quantidade de SKUs em estoque](https://help.vtex.com/pt/tutorial/atualizar-quantidade-de-skus-em-estoque--IKMWjOjMcMqKusSGko8c0)
     * **Estoque infinito:** permite registrar unidades infinitas do SKU, fazendo com que ele esteja sempre disponível para o checkout da sua loja. Isso descarta a necessidade de atualização da contagem desse SKU.
+    * **Lead time (dias):** configuração opcional do tempo de envio a nível de SKU. Defina um tempo para o SKU de um estoque e ele será considerado no [cálculo](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) do tempo de envio do pedido. Por padrão, o [lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) vem definido como zero dias e sua contagem é feita em dias úteis. Você pode alterar a [contagem para dias corridos](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional) e, se desejar configurar horas, minutos e segundos, pode usar o endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 <div class="alert alert-warning">
 Para garantir que os itens adicionados ao estoque fiquem disponíveis para venda na loja, o ID dos SKUs não deve conter o número zero à esquerda. O sistema não reconhece, por exemplo, IDs no formato <code>01, 02, 021,</code> pois é esperado o formato<code> 1, 2, 21</code>.
 </div>
 
-### Filtros de busca
+A quantidade total de itens na página **Gerenciamento de inventário** é atualizada em tempo real, mas pode haver um atraso de até 1 hora para a informação aparecer no [registro de atualizações](https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2).
 
-EM **Gerenciamento de inventário**, você pode pesquisar SKUs na barra de busca e também utilizar filtros de busca.
+### Filtros de busca
 
-Para realizar uma busca pela barra, basta digitar o nome ou o ID do SKU e clicar na lupa <i class="fa-solid fa-magnifying-glass"></i>. Para utilizar os filtros, veja os filtros disponíveis:
+Na **Gerenciamento de inventário**, para realizar uma busca pela barra, basta digitar o nome ou o ID do SKU e clicar na lupa <i class="fa-solid fa-magnifying-glass"></i>. Para utilizar os filtros, veja os filtros disponíveis:
 
 *   **Última atualização:** retorna a quantidade atualizada de itens em estoque. É possível inserir um valor `Maior que, ou igual a`, `Menor que, ou igual a` ou `Entre` uma faixa de itens. Quando nenhum valor é inserido, `Todos` os itens são mostrados na tabela.
 
diff --git a/docs/tutorials/pt/managing-url-redirects.md b/docs/tutorials/pt/managing-url-redirects.md
index e985e23ec..f9854b64d 100644
--- a/docs/tutorials/pt/managing-url-redirects.md
+++ b/docs/tutorials/pt/managing-url-redirects.md
@@ -3,8 +3,8 @@ title: 'Gerenciando redirecionamentos de URL'
 id: 3UJuFrU8imSVWg134mkvJV
 status: PUBLISHED
 createdAt: 2022-02-03T13:17:46.873Z
-updatedAt: 2023-03-24T22:07:21.230Z
-publishedAt: 2023-03-24T22:07:21.230Z
+updatedAt: 2023-11-14T18:03:08.019Z
+publishedAt: 2023-11-14T18:03:08.019Z
 firstPublishedAt: 2022-02-03T14:42:10.000Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -17,6 +17,10 @@ subcategory: 1znnjA17XqaUNdNFr42PW5
 
 **Redirecionamentos** é uma funcionalidade que direciona o cliente para qualquer outra página, seja interna, seja externa ao seu site. Esse redirecionamento é feito na área de busca, utilizando termos ou filtros selecionados. 
 
+<div class="alert alert-warning" role="alert">
+Para criar, editar ou apagar redirecionamentos, o usuário do Admin precisa ter um perfil de acesso com o <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso do License Manager</a> <strong>CMS Settings</strong>. Você pode atribuir um perfil de acesso com o recurso ao usuário seguindo as instruções do artigo <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512#editar-usuarios">Gerenciando usuários</a>, ou criar um novo perfil de acesso que inclui o recurso seguindo as instruções do artigo <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso">Perfis de acesso</a>.
+</div>
+
 É possível vários redirecionamentos em uma única URL. Para criar um redirecionamento, siga o tutorial abaixo. 
 
 1. No Admin VTEX, clique em **Storefront** >  **Redirecionamentos**.
@@ -27,16 +31,21 @@ subcategory: 1znnjA17XqaUNdNFr42PW5
 4. Na caixa de seleção, indique se esse redirecionamento é temporário ou permanente. Caso seja temporário, é preciso definir a data final.
 5. Clique em `Salvar` para finalizar.
 
-![gerenciando redirecionamentos pt 1](https://images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/1492276d15ccad0d3fb36ea59f712912/image4.png)
+![gerenciando redirecionamentos pt 1](//images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/1492276d15ccad0d3fb36ea59f712912/image4.png)
 ## Importar redirecionamento
 
 Para importar um redirecionamento, siga os passos abaixo.
 
 1. Clique em <i class="fas fa-upload"></i> `Importar`.
-2. Selecione o arquivo CSV do seu computador.
+2. Selecione o arquivo CSV do seu computador, garantindo que ele utilize ponto e vírgula (`;`) como separador.
 3. Clique em `Importar arquivo`.
 4. Clique em `Salvar` para finalizar.
 
+<div class="alert alert-warning" role="alert">
+Observe que alguns editores podem modificar automaticamente o separador. Portanto, antes de importar um arquivo, verifique se ele está formatado corretamente em CSV, utilizando o ponto e vírgula (<code>;</code>) como separador de valores. Não serão aceitos arquivos utilizando outros separadores como vírgula (<code>,</code>) e espaço de tabulação (<code>&nbsp;&nbsp;</code>).<br><br>
+Alguns editores, como o Google Sheets, exportam arquivos CSV utilizando vírgula (<code>,</code>) como separador por padrão, e podem não permitir o uso de ponto e vírgula (<code>;</code>). Para esses casos, é recomendado recorrer a outros editores que permitam substituir os separadores ou salvar o arquivo utilizando ponto e vírgula (<code>;</code>) como separador.
+</div>
+
 ## Exportar redirecionamento 
 
 Se deseja exportar seus redirecionamentos, clique em <i class="fas fa-download"></i> `Exportar` e eles serão baixados no seu computador. 
diff --git a/docs/tutorials/pt/managing-users-in-b2b-organizations.md b/docs/tutorials/pt/managing-users-in-b2b-organizations.md
new file mode 100644
index 000000000..efbe033ce
--- /dev/null
+++ b/docs/tutorials/pt/managing-users-in-b2b-organizations.md
@@ -0,0 +1,66 @@
+---
+title: 'Gerenciamento de Usuários em organizações B2B'
+id: 659ESiB9rjsR6Tg9KLl5He
+status: PUBLISHED
+createdAt: 2024-07-05T11:36:43.947Z
+updatedAt: 2024-07-05T13:50:41.743Z
+publishedAt: 2024-07-05T13:50:41.743Z
+firstPublishedAt: 2024-07-05T13:47:56.220Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gerenciamento-de-usuarios-em-organizacoes-b2b
+locale: pt
+legacySlug: gerenciamento-de-usuarios-em-organizacoes-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+Em uma operação B2B VTEX, usuários são pessoas autorizadas a acessar a plataforma dentro de uma organização B2B. Eles podem:
+- Realizar pedidos.
+- Gerenciar informações.
+- Executar tarefas administrativas.
+
+A página **Usuários** no Admin VTEX é essencial para gerenciar quem pode acessar e operar a plataforma em nome de uma organização. Definir os usuários e suas permissões garantem operações seguras, alinhadas com as responsabilidades e funções de cada membro da organização.
+
+Confira neste artigo como você pode gerenciar usuários:
+- [Adicionando novos usuários à organização](#adicionando-novos-usuários-à-organização.).
+- [Editando um usuário](#editando-um-usuário).
+- [Removendo um usuário](#removendo-um-usuário).
+
+## Adicionando um novo usuário à organização
+Para adicionar um novo usuário à organização, siga estas etapas:
+<ol>
+    <li>No Admin VTEX, acesse <strong>Aplicativos &gt; Organizações e centros de custo B2B &gt; Organizações</strong>, ou digite <strong>Organizações</strong> na barra de busca no topo da página.</li>
+    <li>Clique no nome da organização desejada para acessar a página de detalhes.</li>
+    <li>Clique na aba <strong>Usuários</strong>.</li>
+    <li>Clique em <code>Novo</code>.</li>
+    <li>Preencha os dados dos usuários, conforme as informações abaixo:
+        <ul>
+            <li><strong>Nome:</strong> nome completo do usuário.</li>
+            <li><strong>Email:</strong> email do usuário.</li>
+            <li><strong>Organização:</strong> nome da organização.</li>
+            <li><strong>Centro de custo:</strong> centro de custo ao qual o usuário estará associado.</li>
+            <li><strong>Perfil de acesso:</strong> papel que o usuário terá na loja virtual. Veja mais detalhes sobre as funções disponíveis na documentação de <a href="https://help.vtex.com/pt/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA" target="_blank">Gerenciamento de permissões no B2B Suite</a>.</li>
+        </ul>
+    </li>
+    <li>Clique em <code>Salvar</code>.</li>
+</ol>
+
+## Editando um usuário
+Para editar informações sobre um usuário existente, siga estas etapas:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar a página de detalhes.
+3. Clique na aba **Usuários**.
+4. Clique no usuário que deseja editar.
+5. Edite o **Perfil de acesso.**
+6. Clique em `Salvar`.
+
+## Removendo um usuário
+Para remover um usuário, siga estas etapas:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar a página de detalhes.
+3. Clique na aba **Usuários**.
+4. Clique no usuário que deseja remover.
+5. Clique em `REMOVER USUÁRIO`.
diff --git a/docs/tutorials/pt/managing-users.md b/docs/tutorials/pt/managing-users.md
index 918b06b40..fad35c6a7 100644
--- a/docs/tutorials/pt/managing-users.md
+++ b/docs/tutorials/pt/managing-users.md
@@ -3,8 +3,8 @@ title: 'Gerenciar usuários'
 id: tutorials_512
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:09.608Z
-updatedAt: 2022-08-24T14:24:37.685Z
-publishedAt: 2022-08-24T14:24:37.685Z
+updatedAt: 2024-06-10T18:24:36.901Z
+publishedAt: 2024-06-10T18:24:36.901Z
 firstPublishedAt: 2017-04-27T23:03:28.211Z
 contentType: tutorial
 productTeam: Identity
@@ -15,57 +15,59 @@ legacySlug: criando-usuarios
 subcategory: 63DHe3VQEEE6Uuua8gIs2M
 ---
 
-A gestão dos usuários com acesso ao ambiente administrativo da sua loja VTEX é feita pelo [Gerenciamento da conta](/pt/tutorial/visao-geral-do-modulo-license-manager/), na seção de **Usuários**. Para acessar a seção, no painel esquerdo do Admin vá em __Gerenciamento da conta__ > __Usuários__.  
-![Menu Usuários](https://images.ctfassets.net/alneenqid6w5/4ufKrojjLZwb8zBdD5xz7f/1ced4757cb7ffdac1e796831a072cee4/Menu_Usu__rios.png)
+A gestão dos usuários com acesso ao ambiente administrativo da sua loja VTEX é feita pelo [Gerenciamento da conta](https://help.vtex.com/pt/tutorial/visao-geral-configuracoes-da-conta--6USYxLuzNt4uAkvjdPF7I8), na página de **Usuários**. Para acessá-la, na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__. 
 
-Esta seção irá mostrar a lista de usuários com os respectivos __Nome__, __Email__ e configuração de __MFA__. Também estão presentes opções de busca de usuários, exportar usuários e criar novos usuários. Outras opções disponíveis por esta interface são de editar ou excluir cada usuário.  
-![Lista Usuários User Management PT](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
+Esta página mostra a lista de usuários com os respectivos __Nome__, __Email__ e configuração de __MFA__. Também estão presentes opções de busca de usuários, exportar usuários e criar novos usuários. Outras opções disponíveis por esta interface são de editar ou excluir cada usuário.
 
-## Criando um novo usuário
+![Lista Usuários User Management PT](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
 
-1. Acesse o módulo __Gerenciamento da conta__.
-2. Clique na aba __Usuários__.  
-![Menu Usuários](https://images.ctfassets.net/alneenqid6w5/4ufKrojjLZwb8zBdD5xz7f/1ced4757cb7ffdac1e796831a072cee4/Menu_Usu__rios.png)
-3. Clique no botão **(+) Novo**.  
-![Botão Novo Usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/2MzlIdrqPecPcrnjeSMTTx/2e22d8445ad59154fcf3a74143ba4e83/Bot__o_Novo_Usu__rio_User_Management_PT.png)
-4. Preencha o **Email**.  
-![Cadastro Novo usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/24b86a1bfa609e3a7df29a9d871bf92c/Cadastro_Novo_usu__rio_User_Management_PT.png)
-5. Adicione os [Perfis de acesso](/pt/tutorial/como-criar-perfil-de-acesso/) desejados.  
-![Selecionar perfis User Management PT](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png)
-6. Clique no botão **Salvar**.  
-![Botão Salvar Usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/707TZ7u4fRaSVGVDfaLcMC/d121f227059e530135daa14216055cf8/Bot__o_Salvar_Usu__rio_User_Management_PT.png)
+<div class="alert alert-warning">
+Qualquer usuário que deseje gerenciar usuários ou chaves de aplicação deve ter um perfil que contenha o <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recurso</a> <b>Save User</b>. Você pode usar, por exemplo, o perfil predefinido <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>.
+</div>
 
-O usuário irá receber um e-mail confirmando o cadastro e com um link para cadastrar a senha de acesso.
+## Criar um novo usuário
 
-A senha deverá ter pelo menos 8 caracteres e um número, uma letra maiúscula e uma letra minúscula. Após preenchê-las, uma chave de acesso será enviada por e-mail, para validar o cadastro.
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
+2. Clique no botão `+ Novo`.  
+3. Preencha o **Email**.
+  ![Cadastro Novo usuário User Management PT](//images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/24b86a1bfa609e3a7df29a9d871bf92c/Cadastro_Novo_usu__rio_User_Management_PT.png)
+4. Clique em `+ Adicionar perfis`.
+5. Selecione os [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) desejados, conforme ilustrado pela imagem:
+  ![Selecionar perfis User Management PT](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png)
+6. Clique em `Adicionar perfis` para confirmar a seleção.
+7. Clique em `Salvar`.  
 
-## Editando usuários
+O usuário irá receber um e-mail confirmando o cadastro, com um link para cadastrar a senha de acesso.
 
-Para editar um usuário já cadastrado bastará clicar em seu nome a partir da listagem de usuários. Outra possibilidade é clicar no botão com três pontos do usuário desejado e então em **Editar**.
-![Botão Editar Usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/4795fe5b550804de645180f2ce973cb0/Bot__o_Editar_Usu__rio_User_Management_PT.png)
+A senha deverá ter pelo menos oito caracteres e um número, uma letra maiúscula e uma letra minúscula. Após preenchê-las, uma chave de acesso será enviada por e-mail, para validar o cadastro.
 
-Não é possível alterar o e-mail. Neste caso, é necessário fazer um novo cadastro.
+## Editar usuários
 
-Na tela de edição é possível adicionar e remover os [Perfis de acesso](/pt/tutorial/como-criar-perfil-de-acesso/) do usuário.  
-![Selecionar perfis User Management PT](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png)
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
+2. Para editar um usuário já cadastrado, clique em seu nome a partir da listagem de usuários. Outra possibilidade é clicar no botão de menu <i class="fas fa-ellipsis-v"></i> na linha do usuário desejado e então em **Editar**.
+  ![Botão Editar Usuário User Management PT](//images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/4795fe5b550804de645180f2ce973cb0/Bot__o_Editar_Usu__rio_User_Management_PT.png)
+  <div class="alert alert-warning" role="alert">Não é possível alterar o email de um usuário cadastrado. Neste caso, é necessário excluir o cadastro anterior e fazer um novo cadastro.</div>
+3. Na tela de edição, é possível adicionar e remover [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) do usuário, conforme ilustrado a seguir.
+  ![Selecionar perfis User Management PT](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png) 
+4. Clique em `Adicionar perfis` para confirmar a seleção.
+5. Clique em `Salvar`.
 
 <div class="alert alert-info" role="alert">Um alerta irá aparecer ao adicionar perfis de acesso a um usuário que não utiliza autenticação de múltiplos fatores (MFA). O artigo <a href="https://help.vtex.com/pt/tutorial/habilitar-login-por-autenticacao-de-2-fatores--4Ae1fcQi12g8u4SkQKCqWQ">Habilitar login por autenticação de 2 fatores</a> mostra como habilitar essa configuração.</div>
 
-<div class="alert alert-warning" role="alert">Se todos os perfis de acesso forem removidos do usuário, ele também não conseguirá mais acessar o admin.</div>
-
-## Excluindo um usuário
+<div class="alert alert-warning" role="alert">Se todos os perfis de acesso forem removidos do usuário, ele também não conseguirá mais acessar o Admin VTEX.</div>
 
-1. Para remover o acesso de um usuário, na listagem de usuários clique no botão com três pontos do usuário que deseja remover.
-2. Clique no item **Excluir**.  
-![Botão Excluir Usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/211543a868c70430b56872901e1a834d/Bot__o_Excluir_Usu__rio_User_Management_PT.png)
-3. Aparecerá uma mensagem para confirmar a exclusão do usuário. Para confirmar, clique no botão **SIM, REMOVER O ACESSO**.  
-![Confirmar Remover Acesso User Management PT](https://images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/682ccb51fcb859c7f0f50f7914049718/Confirmar_Remover_Acesso_User_Management_PT.png)
+## Excluir um usuário
 
-<div class="alert alert-info">
-Embora tokens de integração apareçam na listagem de usuários, eles não podem ser excluídos. Para desativá-los, acesse <em>Configuração da conta > Gerenciamento da conta > Conta</em> e desmarque o campo <strong>Status dos Tokens</strong>.
-</div>
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
+2. Para remover o acesso de um usuário, na listagem de usuários, clique no botão de menu <i class="fas fa-ellipsis-v"></i> na linha do usuário que deseja remover.
+3. Clique no item **Excluir**.  
+  ![Botão Excluir Usuário User Management PT](//images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/211543a868c70430b56872901e1a834d/Bot__o_Excluir_Usu__rio_User_Management_PT.png)
+  Aparecerá uma mensagem para confirmar a exclusão do usuário.
+4. Para confirmar, clique no botão `SIM, REMOVER O ACESSO`.  
+  ![Confirmar Remover Acesso User Management PT](//images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/682ccb51fcb859c7f0f50f7914049718/Confirmar_Remover_Acesso_User_Management_PT.png)
 
-## Exportando dados de usuário
+## Exportar dados de usuários
 
-1. Para exportar os dados do usuário, clique no botão **EXPORTAR**.
-2. Salve o arquivo csv no seu dispositivo. O arquivo contém o id, o email e o nome de cada usuário.
+1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
+2. Para exportar os dados de usuários, clique no botão <i class="fas fa-download"></i> `Exportar`.
+3. Salve o arquivo CSV no seu dispositivo. O arquivo contém o ID, o email e o nome de cada usuário.
diff --git a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
index 5150e6bdf..8a0402116 100644
--- a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
+++ b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
@@ -65,9 +65,9 @@ O status do mapeamento de categorias no marketplace VTEX é indicado por ícones
 
 | **Ícone** | **Status** |
 | ---------- | ---------- |
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado:** o mapeamento da categoria foi concluído. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento:** houve um problema e o mapeamento não foi realizado. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado:** a categoria ainda não foi mapeada. |
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado:** o mapeamento da categoria foi concluído. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento:** houve um problema e o mapeamento não foi realizado. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado:** a categoria ainda não foi mapeada. |
 
 <div class = "alert alert-info">
 Não é possível excluir um mapeamento de categoria, mas você pode alterar as configurações a qualquer momento, seguindo os mesmos passos do primeiro mapeamento realizado.
@@ -90,9 +90,9 @@ O status do mapeamento de marcas no marketplace VTEX é indicado por ícones na
 
 | **Ícone** | **Status** |
 | ---------- | ---------- |
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado:** o mapeamento da categoria foi concluído. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento:** houve um problema e o mapeamento não foi realizado. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado:** a categoria ainda não foi mapeada. |
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado:** o mapeamento da categoria foi concluído. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento:** houve um problema e o mapeamento não foi realizado. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado:** a categoria ainda não foi mapeada. |
 
 <div class = "alert alert-info">
 Não é possível excluir um mapeamento de marca, mas você pode alterar as configurações a qualquer momento, seguindo os mesmos passos do primeiro mapeamento realizado.
diff --git a/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md b/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md
index 1818a5a89..4f08189da 100644
--- a/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md
+++ b/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md
@@ -176,7 +176,7 @@ Ao concluir as etapas de preenchimento da planilha de mapeamento, você deve seg
 1. Acesse o Admin.
 2. No módulo Marketplace, clique em Integrações.
 3. Selecione a opção Configurações.
-4. Na integração Mercado Livre, clique na engrenagem<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+4. Na integração Mercado Livre, clique na engrenagem<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 5. Escolha a opção **Upload do mapeamento**.
 6. Selecione a opção **Escolher um arquivo**.
 7. Agora, selecione a planilha de mapeamento de categorias, atributos e variações do Mercado Livre.
diff --git a/docs/tutorials/pt/marketplace-invited-sellers.md b/docs/tutorials/pt/marketplace-invited-sellers.md
index 15fce3d25..3c8bdb70a 100644
--- a/docs/tutorials/pt/marketplace-invited-sellers.md
+++ b/docs/tutorials/pt/marketplace-invited-sellers.md
@@ -28,7 +28,7 @@ Além de enviar convites, a página também conta com a lista de sellers, para q
 
 Para que novos sellers se integrem ao seu marketplace, algumas ações precisam ser feitas no seu ambiente VTEX: [Convidar](#convidar-seller) e [Conectar](#conectar-seller)
 
-![sellers convidados](https://images.ctfassets.net/alneenqid6w5/2y4yFpA7vo6BNjMdVyvZSU/bf18d2e0010e23be921ecb520a060725/sellers_convidados.JPG)
+![sellers convidados](//images.ctfassets.net/alneenqid6w5/2y4yFpA7vo6BNjMdVyvZSU/bf18d2e0010e23be921ecb520a060725/sellers_convidados.JPG)
 
 ## Convidar seller
 
diff --git a/docs/tutorials/pt/marketplace-overview.md b/docs/tutorials/pt/marketplace-overview.md
index 9fb278af9..593241972 100644
--- a/docs/tutorials/pt/marketplace-overview.md
+++ b/docs/tutorials/pt/marketplace-overview.md
@@ -3,8 +3,8 @@ title: 'Visão Geral Marketplace'
 id: 40Zd0z9h2RXsM9uMUp3kEb
 status: PUBLISHED
 createdAt: 2023-03-31T19:13:35.911Z
-updatedAt: 2023-03-31T19:18:29.348Z
-publishedAt: 2023-03-31T19:18:29.348Z
+updatedAt: 2023-09-13T22:33:02.149Z
+publishedAt: 2023-09-13T22:33:02.149Z
 firstPublishedAt: 2023-03-31T19:18:29.348Z
 contentType: tutorial
 productTeam: Channels
@@ -21,8 +21,6 @@ Um marketplace é uma plataforma virtual por meio da qual diferentes vendedores
 
 Agrupamos todas as funcionalidades relacionadas a essas operações no menu __Marketplace__, do seu Admin repaginado. 
 
-![Admin v4 marketplace menu PT](https://images.ctfassets.net/alneenqid6w5/5y304Ab4DxbE2GRKVihDjJ/c1a2edea75264dc54e73faf529f8a2c2/Admin_v4_marketplace_menu_PT.jpg)
-
 Confira abaixo mais detalhes sobre as diferentes seções e páginas deste menu.
 
 ## Sellers
diff --git a/docs/tutorials/pt/marketplace-strategies-at-vtex.md b/docs/tutorials/pt/marketplace-strategies-at-vtex.md
index 2118fcb61..228fd6920 100644
--- a/docs/tutorials/pt/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/pt/marketplace-strategies-at-vtex.md
@@ -3,21 +3,21 @@ title: 'Estratégias de marketplace na VTEX'
 id: tutorials_402
 status: PUBLISHED
 createdAt: 2017-04-27T22:06:47.209Z
-updatedAt: 2023-04-20T20:53:42.948Z
-publishedAt: 2023-04-20T20:53:42.948Z
+updatedAt: 2024-06-20T20:13:23.276Z
+publishedAt: 2024-06-20T20:13:23.276Z
 firstPublishedAt: 2017-04-27T23:03:23.819Z
 contentType: tutorial
 productTeam: Channels
-author: 5l9ZQjiivHzkEVjafL4O6v
+author: 2p7evLfTcDrhc5qtrzbLWD
 slug: estrategias-de-marketplace-na-vtex
 locale: pt
 legacySlug: integrando-com-marketplace
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-Um marketplace é uma plataforma virtual por meio da qual diferentes vendedores anunciam seus produtos. Esses vendedores são chamados de sellers, que além de serem os donos dos produtos, são também os responsáveis pela entrega do produto ao comprador.
+Um marketplace é uma plataforma virtual por meio da qual diferentes vendedores anunciam seus produtos. Esses vendedores são chamados de sellers, que além de serem os donos dos produtos, muitas vezes são também os responsáveis pelo [processo de fulfillment do produto](https://help.vtex.com/pt/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP).  
 
-<img src="https://drive.google.com/uc?export=download&id=1qT3lLaKflfnWyHknf7IgjNbRNCki9FuQ"/>
+![Estratégias de marketplace](//images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/a528c80c87b9e97b323f71f7608da296/Ecommerce_web_page-pana.png)
 
 [A VTEX promove a colaboração digital](https://vtex.com/br-pt/marketplace/) em diferentes cenários. Você pode não apenas vender seus produtos em outros marketplaces, mas também vender produtos de outros sellers no seu ambiente, tornando-se um marketplace.
 
@@ -26,150 +26,160 @@ Além disso, com a VTEX você pode gerenciar tudo no mesmo lugar, no conceito qu
 Algumas das principais operações envolvidas ao vender produtos em marketplaces são:
 
 - Controle de estoque nos diversos canais.
-- Sincronização de promoções.
-- Processamento de pedidos. 
-- Gerenciamento dos canais.
+- Sincronização de promoções.  
+- Processamento de pedidos.   
+- Gerenciamento dos canais.  
 
-Na VTEX, não há uma taxa extra para integrar com marketplaces. Também não existe cobrança adicional para uma loja VTEX anunciar em seu ambiente produtos de sellers, ou vender produtos em outra loja VTEX.
+O sortimento de produtos enviados para um marketplace é definido na escolha da sua [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV).  
+
+A [contratação de políticas comerciais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) adicionais é realizada via ticket em nosso [suporte](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação Criação de Política Comercial. Para cada política comercial adicional, é cobrado um valor mensal, seja ela utilizada para integração com marketplaces certificados, parceiros, externos ou VTEX.
 
 <div class="alert alert-info">
 Pedidos aprovados em marketplaces estão sujeitos às mesmas <a href="https://help.vtex.com/pt/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">regras contratuais</a> de pedidos efetuados por outros canais.
 </div>
 
-O sortimento de produtos enviados para um marketplace é definido na escolha da sua [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via ticket em nosso [Suporte](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
+Os próximos cenários abordados neste artigo são:  
 
-A [contratação de política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) para integrar com conector certificado, ou outras lojas VTEX é isenta de taxas.  
+- [Atuar como marketplace](#atuar-como-marketplace)  
+- [Vender em marketplace](#vender-em-marketplace)  
+- [Seller Portal](#seller-portal)  
 
-Os próximos cenários abordados neste artigo são:
+## Atuar como marketplace
 
-- [Vender em marketplace](#vender-em-marketplace)
-- [Atuar como marketplace](#atuar-como-marketplace)
+A arquitetura da VTEX permite que as lojas hospedadas em sua plataforma possam anunciar produtos de outras lojas, sejam elas VTEX, ou não. Quando uma loja VTEX passa a vender produtos de sellers, ela se torna um marketplace VTEX.
 
-## Vender em marketplace
+Quando sua loja é o ambiente onde outros sellers anunciam seus produtos, você se beneficia dessa relação. Veja abaixo algumas das principais vantagens de atuar como um marketplace:  
 
-Os marketplaces são espaços de venda nos quais os sellers anunciam seus produtos. Existem várias razões pelas quais pode ser estrategicamente vantajoso vender em um marketplace, algumas das principais são:
+- __Aumento da receita:__ existem diferentes formas de monetizar em um marketplace, sendo a mais comum receber uma comissão sobre as vendas realizadas no seu ambiente.  
+- __Maior diversidade de produtos:__ há um aumento na variedade de produtos ofertados na sua loja.  
+- __Alcance de novos clientes:__ sellers atraem novos clientes para o marketplace e, desta forma, promovem tanto um maior alcance de mercado, quanto mais visibilidade para sua marca.  
+- __Melhora da experiência de compra:__ ao diversificar e ampliar a variedade de produtos, você promove uma experiência completa para o cliente. Ele pode adquirir em um único local tudo o que precisa (one-stop-shop).  
+- __Baixo custo:__ esse processo de colaboração não representa um aumento nos seus custos. Ele é um modelo escalonável que dispensa a necessidade de investimentos em áreas como estoque, estrutura ou equipe, pois a entrega dos produtos é responsabilidade dos sellers.  
+- __Valorização da reputação da sua marca:__ se a sua loja é reconhecida no mercado, isso significa que os produtos ofertados no seu ambiente contam com a confiança do cliente. Você pode aumentar seus lucros ao oferecer aos vendedores valor agregado aos produtos deles.  
 
-- **Visibilidade para sua loja:** a centralização de diferentes sellers e grande variedade de produtos em um marketplace atrai o tráfego de usuários, e ao anunciar em vários canais, você faz com que sua marca ganhe visibilidade e seja apresentada a novos públicos.
-- **Baixo custo:** cada marketplace tem suas próprias contrapartidas financeiras, sendo que a mais praticada é a cobrança de uma comissão sobre vendas. Ou seja, se você não vender, não há taxas a serem pagas.
-- **Aumento das vendas:** a estratégia de atuar em vários canais diversifica sua fonte de faturamento e aumenta as chances de conversão.
-- **Diversificação de nicho:** você pode definir um sortimento de produtos específico para cada marketplace, e a partir disso montar estratégias de validação de mercado ou realizar vendas sazonais.
-- **Valor agregado ao produto:** especialmente se o público não estiver familiarizado com sua marca, é vantajoso se beneficiar da relação de confiança que um marketplace construiu com o cliente. Isso agrega valor ao seu produto e aumenta suas chances de conversão.
+Uma loja VTEX pode vender produtos de outros sellers nos seguintes casos:
 
-Na VTEX, você pode vender em outros canais nas seguintes situações:
+- [Integrado a seller externo](#integrado-a-seller-externo)  
+- [Sendo um marketplace VTEX](#ser-um-marketplace)  
 
-- [Sendo seller VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex)
-- [Integrado a marketplaces certificados](#integrado-a-marketplaces-certificados)
-- [Integrado a marketplaces parceiros](#integrado-a-marketplaces-parceiros)
-- [Integrado a marketplaces externos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplace-externo)
+### Integrado a seller externo
 
-<div class="alert alert-info">
-Uma loja VTEX pode atuar simultaneamente como <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex">seller VTEX</a> e <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex">marketplace VTEX</a>.
-</div>
+É possível que um seller não integrado à VTEX queira vender produtos em um marketplace VTEX. Neste caso, juntos eles poderiam desenvolver um conector customizado para essa integração. A VTEX disponibiliza um conjunto de APIs e instruções para facilitar o processo. Veja mais informações no [guia de integração com seller externo](https://developers.vtex.com/vtex-developer-docs/docs/external-seller-integration-guide).  
 
-<div class = "alert alert-info">
-A plataforma VTEX possui diferentes funcionalidades para fulfillment, que podem ser combinadas para cenários como <i>dropshipping</i>, quando o seller recebe e repassa o pedido do cliente a um terceiro, que será encarregado do fulfillment. A solução <a href="https://help.vtex.com/pt/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP">logística</a> mais adequada para o seller vai depender da arquitetura e do seu modelo de negócio, e pode ser feita por <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integração de Back office (ERP/PIM/WMS)</a>.
-</div>
+### Ser um marketplace VTEX
 
-### Sendo seller VTEX
+A configuração da para [se tornar um marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) dispensa alguns dos passos exigidos em outras integrações, e uma vez configurado o seu marketplace, confira [Ações para a operação de marketplaces VTEX](https://help.vtex.com/pt/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev).
 
-A arquitetura da VTEX permite que uma loja hospedada em seu ambiente tenha seus produtos anunciados em outras lojas VTEX. Quando uma loja VTEX vende seus produtos em outra loja VTEX, ela é chamada de seller VTEX. Adiante veremos mais informações sobre quando a loja é o ambiente que anuncia os produtos dos sellers VTEX, ou seja, um [marketplace VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex).
+Veja abaixo os principais marketplaces VTEX:  
 
-A configuração da [integração entre lojas VTEX](https://help.vtex.com/pt/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP) é simples e dispensa alguns dos passos exigidos em outras integrações. Além disso, você pode fazer uso do Marketplaces e integrações, que reúne uma espécie de catálogo de interessados em parcerias, o que facilita o contato entre sellers VTEX, marketplaces VTEX e conectores certificados.
+![mkt br](//images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
 
-O [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é uma edição da plataforma VTEX voltada para sellers se conectarem e venderem seus produtos em marketplaces hospedados na VTEX. Com o portal, sellers acessam todas as funcionalidades essenciais para a operação de ecommerce em grandes vitrines, trazendo visibilidade e conversão de vendas.
+Além disso, a página __Marketplaces e integrações__ promove e facilita o contato entre marketplaces VTEX e certificados com sellers VTEX interessados em colaborações.
 
-<div class = "alert alert-info">
-Na VTEX, é possível atuar como <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>, um seller não identificado pelo consumidor na experiência de compra. Este tipo de seller é o padrão para <a href="https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">contas franquia</a>, por exemplo, e pode ser estratégico para determinados modelos de negócio. Para saber mais, veja o artigo <a href="https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Escolher entre conta padrão, conta franquia ou Seller Portal</a>.
-</div>
+## Vender em marketplace
 
-### Integrado a Marketplaces Certificados
+Vender em um marketplace pode ser estrategicamente vantajoso pelos pontos a seguir:
 
-Existem marketplaces de atuação nacional e internacional que são excelentes espaços para você promover seus produtos e alavancar suas vendas.
+- __Visibilidade para sua loja:__ a centralização de diferentes sellers e grande variedade de produtos em um marketplace atrai o tráfego de usuários, e ao anunciar em vários canais, você faz com que sua marca ganhe visibilidade e seja apresentada a novos públicos.
+- __Baixo custo:__ cada marketplace tem suas próprias contrapartidas financeiras, sendo que a mais praticada é a cobrança de uma comissão sobre vendas. Ou seja, se você não vender, não há taxas a serem pagas para o marketplace.  
+- __Aumento das vendas:__ a estratégia de atuar em vários canais diversifica sua fonte de faturamento e aumenta as chances de conversão.  
+- __Diversificação de nicho:__ você pode definir um sortimento de produtos específico para cada marketplace, e a partir disso montar estratégias de validação de mercado ou realizar vendas sazonais.  
+- __Valor agregado ao produto:__ especialmente se o público não estiver familiarizado com sua marca, é vantajoso se beneficiar da relação de confiança que um marketplace construiu com o cliente. Isso agrega valor ao seu produto e aumenta suas chances de conversão.  
 
-Atualmente, na plataforma VTEX existem os seguintes conectores certificados:
-
-- [Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP)
-- [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq)
-- [Magazine Luiza](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y)
-- [Carrefour](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2)
-- [Centauro](https://help.vtex.com/pt/tracks/integracao-com-a-centauro--D8Qnjbr5lfLkUfMRhsfbj)
-- [Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc)
-- [Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw)
-- [Google Shopping Ads](https://help.vtex.com/pt/tracks/como-fazer-campanhas-atraves-do-google-ads--47kz5PRQPK0IEaqGqiIuA)
-- [Dafiti](https://help.vtex.com/pt/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i)
-- [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm)
-- [Tik Tok](https://help.vtex.com/pt/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd)
-- [Zoom](https://help.vtex.com/pt/tutorial/integrando-com-zoom--2OoQjigCVOIEWWkgOqwCK6?&utm_source=autocomplete)
-- [CSU (Opte+)](https://help.vtex.com/pt/tutorial/integrando-com-csu-opte-2--tutorials_4258)
-- [Kabum](https://help.vtex.com/pt/tutorial/integracao-com-o-kabum--DM0uQeFIXOk7CY9oAPrf0)
-- GPA
-- [MadeiraMadeira](https://help.vtex.com/pt/tutorial/integracao-com-madeiramadeira--J4QCENKiz4urYNfaMuE0i)
-- [Riachuelo](https://help.vtex.com/pt/tutorial/integracao-com-riachuelo--kpfxAgwEcANihHLT4iW81)
-- [Camicado](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)
-- [Renner](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)
-- [Loopi](https://help.vtex.com/pt/tutorial/integracao-com-loopi--2wmap3hWksLxJ0IYe7nYFP)
-- GrupoLTM
-- TudoAzul
-- Webcontinental
-- Farfetch
+### Tipos de marketplaces
 
-<div class="alert alert-info">
-Embora Facebook, Google Shopping, Google Shopping Ads e Tik Tok não sejam marketplaces, incluímos seus conectores nessa lista por oferecerem uma experiência similar de envio de produtos a partir de lojas VTEX.
-</div>
+Existem marketplaces de atuação nacional e internacional que são excelentes espaços para você promover seus produtos e alavancar suas vendas.
 
-Para realizar a integração com conector você encontra ajuda nos conteúdos que guiam o processo de configuração e, enquanto cliente VTEX, você conta com nosso suporte para eventuais dificuldades.
+Atuando como Seller VTEX, é possível você integrar com quatro tipos diferentes de marketplace, os certificados, os parceiros, os externos e os marketplaces VTEX. 
 
-### Integrado a Marketplaces parceiros
+Para realizar a integração com um marketplace você encontra apoio nos conteúdos linkados acima que guiam o processo de configuração e, enquanto cliente VTEX, você conta com nosso suporte para eventuais dificuldades.
+
+Na VTEX, você pode vender em outros canais nas seguintes situações:  
 
-Existem integrações externas, que foram desenvolvidas em conjunto com hubs parceiros.
-
-- Americanas
-- Via Varejo
-- [Shopee](https://help.vtex.com/pt/tutorial/integracao-com-a-shopee-beta--5OV9idUY6fHu3P8grnCnqj)
-- [Wish](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4)
-- Olist
-- [Conecta Lá](https://help.vtex.com/pt/tutorial/integracao-com-conecta-la--403fvPYdv2f6VeP0na3awP)  
-- Anymarket
-- TudoAzul
-- Easy Live
-- Mimo
-- Wap Store
-- Plugg.to
-- Fast Shop
-- Hubplus
+- [Integrado a marketplaces externos](#integrado-a-marketplace-externo)  
+- [Integrado a marketplaces certificados](#integrado-a-marketplace-certificados)  
+- [Integrado a marketplaces parceiros](integrado-a-marketplaces-parceiros)  
+- [Ser um seller VTEX](#ser-um-seller-vtex)  
 
 ### Integrado a marketplace externo
 
 Pode ser que sua loja queira vender em um marketplace que não possua conexão com a VTEX. Neste caso, você pode desenvolver um conector customizado para essa integração. A VTEX disponibiliza um conjunto de APIs e instruções para facilitar o processo. Saiba mais no [guia de integração com marketplace externo](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide).
 
-## Atuar como marketplace
-
-Além dos benefícios apresentados no contexto de se vender em um marketplace, existe a possibilidade da sua loja ser o próprio ambiente onde os sellers anunciam seus produtos. Algumas das principais vantagens de atuar como um marketplace são:
+### Integrado a marketplaces certificados
+
+Marketplaces certificados são aqueles cuja integração foi desenvolvida pelo time de desenvolvedores da VTEX. A política comercial adicional contratada para esse tipo de integração, está isenta da taxa mensal se houver pedidos atrelados à política através do marketplace certificado e pagará apenas o take rate dos pedidos.
+
+<div class="alert alert-warning">
+As políticas comerciais adicionais contratadas para integração com marketplaces certificados que forem utilizadas também em integração com outros tipos de marketplaces, está sujeita à cobrança da taxa mensal.
+</div>  
+
+Atualmente, na plataforma VTEX você encontra os seguintes marketplaces certificados:  
+
+- [Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP)  
+- [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq)  
+- [Magazine Luiza](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y)  
+- [Carrefour](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2)  
+- [Centauro](https://help.vtex.com/pt/tracks/integracao-com-a-centauro--D8Qnjbr5lfLkUfMRhsfbj)  
+- [Dafiti](https://help.vtex.com/pt/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i)  
+- [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm)  
+- [Zoom](https://help.vtex.com/pt/tutorial/integrando-com-zoom--2OoQjigCVOIEWWkgOqwCK6?&utm_source=autocomplete)  
+- [CSU (Opte+)](https://help.vtex.com/pt/tutorial/integrando-com-csu-opte-2--tutorials_4258)  
+- [MadeiraMadeira](https://help.vtex.com/pt/tutorial/integracao-com-madeiramadeira--J4QCENKiz4urYNfaMuE0i)  
+- [Riachuelo](https://help.vtex.com/pt/tutorial/integracao-com-riachuelo--kpfxAgwEcANihHLT4iW81)  
+- [Camicado](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)  
+- [Renner](https://help.vtex.com/pt/tutorial/integracao-com-renner-e-camicado--5qf2wloosKlmIB8o2AitnT)  
+- [Enjoei](https://help.vtex.com/tutorial/integracao-com-enjoei--3mV9uhw1AdqFol8K2tfwly)  
+- [Wish](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4)  
+- Kabum  
+- Grupo LTM  
+- TudoAzul  
+- GPA  
+- Climario  
+- Juntoz  
+- SMPlaces  
+- Wish  
+- Farfetch  
+- Falabella  
+- Linio  
 
-- **Aumento da receita:** existem diferentes formas de monetizar em um marketplace, sendo a mais comum receber uma comissão sobre as vendas realizadas no seu ambiente. 
-- **Maior diversidade de produtos:** há um aumento na variedade de produtos ofertados na sua loja.
-- **Alcance de novos clientes:** sellers atraem novos clientes para o marketplace e, desta forma, promovem tanto um maior alcance de mercado, quanto mais visibilidade para sua marca.
-- **Melhora da experiência de compra:** ao diversificar e ampliar a variedade de produtos, você promove uma experiência completa para o cliente. Ele pode adquirir em um único local tudo o que precisa (_one-stop-shop_).
-- **Baixo custo:** esse processo de colaboração não representa um aumento nos seus custos. Ele é um modelo escalonável que dispensa a necessidade de investimentos em áreas como estoque, estrutura ou equipe, pois a entrega dos produtos é responsabilidade dos sellers.
-- **Valorização da reputação da sua marca:** se a sua loja é reconhecida no mercado, isso significa que os produtos ofertados no seu ambiente contam com a confiança do cliente. Você pode aumentar seus lucros ao oferecer aos vendedores valor agregado aos produtos deles.
-
-Uma loja VTEX pode vender produtos de outros sellers nos seguintes casos:
+### Integrado a Marketplaces parceiros
 
-- [Sendo um marketplace VTEX](#ser-um-marketplace-vtex)
-- [Integrado a seller externo](#integrado-a-seller-externo)
+Marketplaces parceiros são aqueles cuja integração foi desenvolvida por um hub de desenvolvedores parceiros à VTEX. A política comercial adicional contratada para esse tipo de integração, está sujeita a taxa mensal e take rate dos pedidos.
+
+Abaixo você encontra os marketplaces parceiros disponíveis no catálogo da VTEX:
+
+- Americanas  
+- Via Varejo  
+- [Shopee](https://help.vtex.com/pt/tutorial/integracao-com-a-shopee-beta--5OV9idUY6fHu3P8grnCnqj)  
+- [Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc)  
+- [Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw)  
+- [Google Shopping Ads](https://help.vtex.com/pt/tracks/como-fazer-campanhas-atraves-do-google-ads--47kz5PRQPK0IEaqGqiIuA)  
+- [Tik Tok](https://help.vtex.com/pt/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd)  
+- [Livelo](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/5rhGcaM0SedoK7lDMBkVFD)  
+- Olist  
+- Anymarket  
+- Easy Live  
+- Mimo  
+- Wap Store  
+- Plugg.to  
+- Fast Shop  
+- Hubplus  
 
-### Ser um marketplace VTEX
+<div class="alert alert-info">
+O Facebook, Google Shopping, Google Shopping Ads e Tik Tok não são marketplaces, porém oferecerem uma experiência similar de envio de produtos a partir de lojas VTEX.
+</div>
 
-A arquitetura da VTEX permite que as lojas hospedadas em sua plataforma possam anunciar produtos de outras lojas, sejam elas VTEX, ou não. Quando uma loja VTEX passa a vender produtos de sellers, ela se torna um marketplace VTEX.
+### Ser um seller VTEX
 
-A configuração da para [se tornar um marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) dispensa alguns dos passos exigidos em outras integrações. Uma vez configurado o seu marketplace, confira [Ações para a operação de marketplaces VTEX](https://help.vtex.com/pt/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev).
+A arquitetura da VTEX permite que uma loja hospedada em sua plataforma tenha seus produtos anunciados em outras lojas VTEX. Quando uma loja VTEX vende seus produtos em outra loja VTEX, ela é chamada de seller VTEX. Adiante veremos mais informações sobre quando a loja é o ambiente que anuncia os produtos dos sellers VTEX, ou seja, um [marketplace VTEX](#ser-um-marketplace-vtex).
 
-Veja abaixo os principais marketplaces VTEX:
+A configuração da [integração entre lojas VTEX](https://help.vtex.com/pt/tutorial/configurar-seller-para-vender-em-marketplace-vtex--6g045OkRSjNpqhkExbQRlP) é simples e dispensa alguns dos passos exigidos em outras integrações. Além disso, você pode fazer uso do módulo Marketplaces e integrações, que fornece um catálogo de marketplaces interessados em parcerias, facilitando o contato entre sellers VTEX, marketplaces VTEX e marketplaces certificados.
 
-![mkt br](https://images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
+## Seller Portal
 
-Além disso, a página __Marketplaces e integrações__ promove e facilita o contato entre marketplaces VTEX, sellers VTEX e conectores certificados interessados em colaborações.
+O [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é uma edição da plataforma VTEX voltada para sellers se conectarem e venderem seus produtos em marketplaces hospedados na VTEX. Com o portal, sellers acessam todas as funcionalidades essenciais para a operação de ecommerce em grandes vitrines, trazendo visibilidade e conversão de vendas.
 
-### Integrado a seller externo
+<div class="alert alert-info">
+Na VTEX, é possível atuar como <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>, um seller não identificado pelo consumidor na experiência de compra. Este tipo de seller é o padrão para <a href="https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">contas franquia</a>, por exemplo, e pode ser estratégico para determinados modelos de negócio. Para saber mais, veja o artigo <a href="https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Escolher entre conta padrão, conta franquia ou Seller Portal</a>.
+</div>
 
-É possível que um seller não integrado à VTEX queira vender produtos em um marketplace VTEX. Neste caso, juntos eles poderiam desenvolver um conector customizado para essa integração. A VTEX disponibiliza um conjunto de APIs e instruções para facilitar o processo. Veja mais informações no [guia de integração com seller externo](https://developers.vtex.com/vtex-developer-docs/docs/external-seller-integration-guide).
diff --git a/docs/tutorials/pt/marketplaces-and-integrations.md b/docs/tutorials/pt/marketplaces-and-integrations.md
index dc07c3adf..058638f0d 100644
--- a/docs/tutorials/pt/marketplaces-and-integrations.md
+++ b/docs/tutorials/pt/marketplaces-and-integrations.md
@@ -3,8 +3,8 @@ title: 'Marketplaces e Integrações'
 id: 5AcBO1t29nhq7rBHas9b6V
 status: PUBLISHED
 createdAt: 2023-04-18T13:51:54.217Z
-updatedAt: 2023-05-04T18:59:04.105Z
-publishedAt: 2023-05-04T18:59:04.105Z
+updatedAt: 2024-02-19T20:19:40.774Z
+publishedAt: 2024-02-19T20:19:40.774Z
 firstPublishedAt: 2023-05-03T17:09:07.242Z
 contentType: tutorial
 productTeam: Channels
@@ -32,7 +32,7 @@ Note que a <b>Marketplaces e Integrações</b> é uma ferramenta que promove o c
 
 Para acessar a página, no Admin VTEX clique em __Marketplace > Conexões > Marketplaces e Integrações__. Na página será possível visualizar os marketplaces sugeridos para conexão e a lista completa de todos os marketplaces disponíveis ou já conectados.  
 
-![Marketplace e integrações](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png) 
+![Marketplace e integrações](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png) 
 
 A tabela que lista os marketplaces possui as seguintes colunas:  
 
@@ -122,4 +122,3 @@ Veja a lista de tutoriais disponíveis para a integração com os marketplaces:
 - [Farmácias App](https://help.vtex.com/pt/tutorial/integrando-com-farmacias-app--tutorials_6271)   
 - [Shopee](https://help.vtex.com/pt/tutorial/integracao-com-a-shopee-beta--5OV9idUY6fHu3P8grnCnqj)  
 - [Wish ](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4) 
-- [Conecta Lá](https://help.vtex.com/pt/tutorial/integracao-com-conecta-la--403fvPYdv2f6VeP0na3awP)  
diff --git a/docs/tutorials/pt/master-data.md b/docs/tutorials/pt/master-data.md
index af7df2280..0eb9189c5 100644
--- a/docs/tutorials/pt/master-data.md
+++ b/docs/tutorials/pt/master-data.md
@@ -3,8 +3,8 @@ title: 'Master Data'
 id: 4otjBnR27u4WUIciQsmkAw
 status: PUBLISHED
 createdAt: 2018-04-02T19:01:38.026Z
-updatedAt: 2023-05-23T14:24:05.123Z
-publishedAt: 2023-05-23T14:24:05.123Z
+updatedAt: 2024-06-07T20:19:30.086Z
+publishedAt: 2024-06-07T20:19:30.086Z
 firstPublishedAt: 2018-04-02T20:54:18.272Z
 contentType: tutorial
 productTeam: Master Data
@@ -27,7 +27,7 @@ Note que a depender da funcionalidade e versão que deseja utilizar, você dever
 
 ## Versões disponíveis
 
-Atualmente existem duas versões disponíveis e você pode escolher aquela que melhor se adequa às necessidades da sua operação. A principal diferença entre as duas é que a v2 não possui interface gráfica, podendo ser utilizada apenas por meio da [API do Master Data v2](https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview), ainda que possua outras funcionalidades relevantes, como o uso de [JSON schemas](https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema).
+Atualmente existem duas versões disponíveis e você pode escolher aquela que melhor se adequa às necessidades da sua operação. A principal diferença entre as duas é que a v2 não possui interface gráfica, podendo ser utilizada apenas por meio da [API do Master Data v2](https://developers.vtex.com/docs/api-reference/master-data-api-v2), ainda que possua outras funcionalidades relevantes, como o uso de [JSON schemas](https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema).
 
 <div class = "alert alert-info">
 Vale ressaltar a plataforma VTEX nativamente salva dados de clientes da sua loja no Master Data v1.
@@ -35,129 +35,179 @@ Vale ressaltar a plataforma VTEX nativamente salva dados de clientes da sua loja
 
 Confira a tabela abaixo para saber mais sobre as funcionalidades de cada versão versões se diferem.
 
-<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;"><b>Funcionalidade</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>v1</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>v2</b>
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><b>Saiba mais</b>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Interface gráfica
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">-
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">API
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v1-overview">Master Data API v1</a></li> 
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/master-data-api-v2-overview">Master Data API v2</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Importação e exportação de planilhas
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"> <ul><li><a href="https://help.vtex.com/en/tutorial/importing-data-into-master-data--tutorials_1135#"> Importar dados para o Master Data v1</a></li><li><a href="https://help.vtex.com/pt/tutorial/exporting-data--tutorials_1125#">Exportar dados do Master Data v1</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Anexos (imagens)
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">-
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Triggers
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#triggers”>Triggers</a></li><li><a href="https://help.vtex.com/en/tutorial/creating-trigger-in-master-data--tutorials_1270#">Criando triggers com Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/setting-up-triggers-in-master-data-v2">Criando triggers com Master Data v2</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">JSON Schemas
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="http://json-schema.org/">JSON Schemas</a></li><li><a href="https://spacetelescope.github.io/understanding-json-schema">Entendendo JSON schemas</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/starting-to-work-on-master-data-with-json-schema">Começando a trabalhar com JSON schemas no Master Data</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/master-data-schema-lifecycle">Ciclo de vida do schema no Master Data</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Propriedades aninhadas
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#propriedades-aninhadas”>Propriedades aninhadas</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Entidades de dados
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Referenciadas por acrônimos compostos de duas letras maiúsculas. Por exemplo, a entidade `CL` armazena dados de clientes da loja e a `AD` de endereços. Não podem ser criadas por API.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Referenciadas por seus nomes. Por exemplo, `Client` e `Address`. Só podem ser criadas por API.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href=”#entidades-de-dados”>Entidades de dados</a></li><li><a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265">Entidades de dados no Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/docs/creating-relationships-between-data-entities-using-api">Criando relações entre entidades de dados do Master Data v2</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Campos
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Devem ser preenchidos no formato específico configurado na entidade de dados.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não há restrição de campos e formatos a princípio. Validação de formato acontece por meio de JSON schemas.
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos">Tipos de campos no Master Data v1</a></li><li><a href=”#schemas-na-v2”>JSON schemas</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">Índices
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://help.vtex.com/pt/tutorial/setting-up-an-index-on-master-data--tutorials_785">Configurar índices no Master Data v1</a></li><li><a href="https://developers.vtex.com/vtex-rest-api/reference/putindices">Configurar índices com a API do Master Data v2</a></li></ul>
-   </td>
-  </tr>
-  <tr class="bb b--muted-3">
-   <td class="t-body pa5" style="min-width: 15rem;">VTable
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Não
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;">Sim
-   </td>
-   <td class="t-body pa5" style="min-width: 15rem;"><ul><li><a href="https://developers.vtex.com/vtex-rest-api/docs/vtable">VTable</a></li></ul>
-   </td>
-  </tr>
-</table>
+<div style="overflow: auto;">
+   <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+      <thead class="bb b--muted-3 tl">
+         <tr>
+            <th class="t-body fw5 pa5" style="min-width: 10rem;"><b>Funcionalidade</b></th>
+            <th class="t-body fw5 pa5" style="min-width: 10rem;"><b>v1</b></th>
+            <th class="t-body fw5 pa5" style="min-width: 10rem;"><b>v2</b></th>
+            <th class="t-body fw5 pa5" style="min-width: 10rem;"><b>Saiba mais</b></th>
+         </tr>
+      </thead>
+      <tbody>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Interface gráfica</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Não</td>
+            <td class="t-body pa5" style="min-width: 10rem;">-</td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">API</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="https://developers.vtex.com/docs/api-reference/masterdata-api"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Master Data API v1</a></li>
+                  <li><a href="https://developers.vtex.com/docs/api-reference/master-data-api-v2#overview"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Master Data API v2</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Importação e exportação de planilhas</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Não</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="https://help.vtex.com/pt/tutorial/importando-dados-no-master-data--tutorials_1135"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Importar dados para o Master Data v1</a></li>
+                  <li><a href="https://help.vtex.com/pt/tutorial/exportando-dados--tutorials_1125"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Exportar dados do Master Data v1</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Anexos (imagens)</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Não</td>
+            <td class="t-body pa5" style="min-width: 10rem;">-</td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Triggers</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="#triggers"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Triggers</a></li>
+                  <li><a href="https://help.vtex.com/en/tutorial/creating-trigger-in-master-data--tutorials_1270#"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Criando triggers com Master Data v1</a></li>
+                  <li><a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Criando triggers com Master Data v2</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">JSON Schemas</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Não</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="http://json-schema.org/"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">JSON Schemas</a></li>
+                  <li><a href="https://json-schema.org/understanding-json-schema"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Entendendo JSON schemas</a></li>
+                  <li><a href="https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Começando a trabalhar com JSON schemas no Master Data
+                        v2</a></li>
+                  <li><a href="https://developers.vtex.com/docs/guides/master-data-schema-lifecycle"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Ciclo de vida do schema no Master Data v2</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Propriedades aninhadas</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Não</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="#propriedades-aninhadas"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Propriedades aninhadas</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Entidades de dados</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Referenciadas por acrônimos compostos de duas letras
+               maiúsculas. Por exemplo, a entidade 'CL' armazena dados de clientes da loja e 'AD' de endereços. Não
+               podem ser criadas por API.</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Referenciadas por seus nomes. Por exemplo, 'Notification'. Só podem ser criadas por API.</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="#entidades-de-dados"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Entidades de dados</a></li>
+                  <li><a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Entidades de dados no Master Data v1</a></li>
+                  <li><a href="https://developers.vtex.com/docs/guides/creating-relationships-between-data-entities-using-api"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Criando relações entre entidades de dados do Master
+                        Data v2</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Campos</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Devem ser preenchidos no formato específico configurado na
+               entidade de dados.</td>
+            <td class="t-body pa5" style="min-width: 10rem;">A princípio, não há restrição de campos e formatos. A validação do formato acontece por meio de JSON schemas.</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Tipos de campos no Master Data v1</a></li>
+                  <li><a href="#v2-schemas"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">JSON schemas</a></li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">Índices</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="https://help.vtex.com/pt/tutorial/setting-up-an-index-on-master-data--tutorials_785"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Configurar índices no Master Data v1</a></li>
+                  <li><a href="https://developers.vtex.com/docs/api-reference/master-data-api-v2#put-/api/dataentities/-dataEntityName-/indices"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">Configurar índices com a API do Master Data v2</a>
+                  </li>
+               </ul>
+            </td>
+         </tr>
+         <tr class="bb b--muted-3">
+            <td class="t-body pa5" style="min-width: 10rem;">VTable</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Não</td>
+            <td class="t-body pa5" style="min-width: 10rem;">Sim</td>
+            <td class="t-body pa5" style="min-width: 10rem;">
+               <ul style="padding-inline-start: 0px;">
+                  <li><a href="https://developers.vtex.com/docs/guides/vtable"
+                        class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word"
+                        target="_blank" rel="noopener noreferrer">VTable</a></li>
+               </ul>
+            </td>
+         </tr>
+      </tbody>
+   </table>
+</div>
 
 <div class="alert alert-danger">
 Note que as entidades de dados das duas versões são independentes, mesmo que algumas possam ser análogas. Isso significa que um dado criado em uma entidade da v1 não pode ser consultado nem editado usando recursos da v2 e vice versa.
@@ -175,7 +225,7 @@ Ambas as versões do Master Data utilizam alguns componentes básicos, podendo s
 
 Entidades de dados são como tabelas onde são registrados documentos e campos.
 
-Entidades de dados do Master Data v1 são referenciadas por acrônimos compostos de duas letras maiúsculas. Na v2, você pode usar o nome da entidade de dados. Por exemplo, na v1 a entidade `CL` armazena dados de clientes da loja e a `AD` guarda dados dos endereços de clientes. Entidades equivalentes na v2 podem ser referenciadas com nomes como `Client` e `Address.
+Entidades de dados do Master Data v1 são referenciadas por acrônimos compostos de duas letras maiúsculas. Na v2, você pode usar o nome da entidade de dados. Por exemplo, na v1 a entidade `CL` armazena dados de clientes da loja e a `AD` guarda dados dos endereços de clientes. Entidades equivalentes na v2 podem ser referenciadas com nomes como `Client` e `Address`.
 
 Em uma data entidade de dados, as informações se estruturam em [documentos](#documentos) e [campos](#campos).
 
@@ -210,7 +260,7 @@ Como mencionado acima, cada documento tem um ID gerado automaticamente pela plat
 Por exemplo, é possível consultar um documento com informações de um cliente especificando o valor do campo `email` referente ao cliente.
 
 <div class = "alert alert-info">
-Saiba mais sobre como <a href=”https://help.vtex.com/pt/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices no Master Data v1</a> ou <a href=”https://developers.vtex.com/vtex-rest-api/reference/putindices”>configurar índices com a API do Master Data v2</a>.
+Saiba mais sobre como <a href=https://help.vtex.com/pt/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices no Master Data v1</a> ou <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>configurar índices com a API do Master Data v2</a>.
 </div>
 
 ## Triggers
@@ -227,12 +277,12 @@ Saiba mais sobre como [configurar triggers no Master Data v1](https://help.vtex.
 Com a v2 do Master Data, você pode definir formatos de dados com JSON schemas. Este formato indica como o Master Data deve validar e indexar documentos.
 
 <div class = "alert alert-info">
-  Saiba mais sobre <a href="https://json-schema.org/">JSON schemas</a>.
+  Saiba mais sobre <a href=https://json-schema.org/>JSON schemas</a>.
 </div>
 
 Você pode salvar um documento em qualquer entidade de dados se o conteúdo for um JSON válido. Uma entidade de dados pode ou não ter múltiplos JSON schemas associados.
 
-![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/908c8b04ea9e32271a494eeb0f2f7a56/schemas_pt.jpg)
+![Master Data schemas](//images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/908c8b04ea9e32271a494eeb0f2f7a56/schemas_pt.jpg)
 
 <div class = "alert alert-info">
 Um documento pode ser compatível com múltiplos JSON Schemas, mas também com nenhum.
diff --git a/docs/tutorials/pt/match-offers-mercado-livre.md b/docs/tutorials/pt/match-offers-mercado-livre.md
new file mode 100644
index 000000000..a5a809813
--- /dev/null
+++ b/docs/tutorials/pt/match-offers-mercado-livre.md
@@ -0,0 +1,134 @@
+---
+title: 'Match de anúncios Mercado Livre'
+id: 1C4HjNLbNk2Y6evD0luXMr
+status: PUBLISHED
+createdAt: 2024-05-06T21:14:40.722Z
+updatedAt: 2024-06-20T21:30:01.461Z
+publishedAt: 2024-06-20T21:30:01.461Z
+firstPublishedAt: 2024-05-06T21:49:40.831Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: match-de-anuncios-mercado-livre
+locale: pt
+legacySlug: match-de-anuncios-mercado-livre
+subcategory: 
+---
+
+<div class="alert alert-info">
+  Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">Suporte</a>.
+  </div>  
+
+Antes de iniciar a leitura do artigo, é importante a leitura da tabela abaixo para compreendimento de alguns termos de uso específico da funcionalidade **Match de anúncios Mercado Livre.**
+
+| **Termo**|**Significado** |
+|:-----:|:-----:|
+|**Anúncios**| Um anúncio é um [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) de um seller que foi enviado para um marketplace e teve seu preço e estoque configurados.|
+|**Canal de venda**| Marketplace que o seller anuncia seus produtos.|
+| **Catálogo Mercado Livre** | Oferta pré-existente no Mercado Livre, onde o seller tem espaço para vincular seu produto e melhorar a visibilidade de seus produtos.|
+|**Oportunidades**| Oportunidade é quando um produto do seller pode ser associado a um produto do catálogo Mercado Livre. O objetivo da oportunidade é fornecer ao seller uma ferramenta que possa fazer essa associação entre os produtos.|
+
+Ao realizar a integração com o Mercado Livre, o seller envia para o marketplace os anúncios que deseja vender na plataforma. Com os anúncios enviados, o Mercado Livre oferece ao seller oportunidades de match com anúncios do tipo **catálogo,** que é quando um anúncio pode estar em um espaço de destaque no marketplace.
+Nesse artigo você pode explorar os seguintes tópicos:
+[Estrutura da página](#estrutura-da-pagina)  
+[Tipos de oportunidades](#tipos-de-oportunidades)  
+[Analisar oportunidade](#analisar-oportunidade)  
+
+![overview-match-anuncios-meli-pt](//images.ctfassets.net/alneenqid6w5/3ve5RacaoRg0KNNEDzegGi/4bdce35a31296b74251777db678e7843/overview-match-anuncios-meli-pt.png)
+
+## Estrutura da página
+A página **Match de anúncios Mercado Livre** é composta por duas abas, [Oportunidades](#aba-oportunidades) e [catálogos ativos](#aba-anuncios-vinculados). Veja a seguir quais as informações e dados disponíveis em cada uma.
+
+### Aba Oportunidades
+
+Nessa aba, o seller visualiza uma lista dos anúncios elegíveis para o catálogo Mercado Livre, filtra as oportunidades por tipo e por canal de venda, caso utilize a integração **`Mercado Livre Classic`** e **` Mercado Livre Premium`,** também é possível buscar as oportunidades digitando o nome do produto ou o **SKU ID** na barra de busca.
+
+Cada linha da lista, representa um anúncio e cada linha é composta pelas seguintes informações dispostas em coluna:
+
+- **Caixa de seleção:** caixa utilizada para selecionar os anúncios desejados e realizar a ação de ` Aceitar sugestão`.  
+- **Seu anúncio:** produto do catálogo VTEX configurado pelo seller e enviado ao marketplace.  
+- **Sugestão de catálogo:** produto do catálogo sugerido pelo Mercado Livre.
+- **Oportunidade:** tipo de ação indicada pelo Mercado Livre para o anúncio do seller.  
+- **Analisar oportunidade:**  botão que leva o seller à página para [analisar oportunidade](#analisar-oportunidade).
+
+### Aba Catálogos ativos
+
+Nessa aba, o seller visualiza uma lista dos anúncios já vinculados ao catálogo Mercado Livre, filtra os anúncios pelo status da relevância e pesquisa os anúncios pelo nome do produto ou pelo **SKU ID.**  
+Na lista dos catálogos ativos, cada linha representa um anúncio e cada linha é composta pelas seguintes informações dispostas em colunas:
+
+- **Anúncio:** apresenta o nome e especificações do produto.  
+- **SKU ID:** SKU ID do produto.  
+- **Status:** qual a relevância daquele anúncio no catálogo Mercado Livre.  
+- **Analisar oportunidade:**  botão que leva o seller à página para [analisar oportunidade](#analisar-oportunidade).  
+
+No topo da tela é possível acompanhar quantos dos catálogos ativos estão em cada status de relevância.
+
+![relevancia-anuncio-pt](//images.ctfassets.net/alneenqid6w5/2Yye8ZNkakmcMBTPZP7QKH/c70be3ea5ca177806104ef47dec0c29b/Captura_de_tela_2024-04-30_181530.png)
+
+<div class=”alert alert-info>
+ Os anúncios ganham relevância quando ele merece o melhor preço e as melhores condições logísticas. 
+</div>
+
+A relevância de um anúncio mostra se a oferta do seller aparece como a primeira no anúncio do catálogo no marketplace ou se ele não é a primeira oferta. Os possíveis status para uma oferta são:
+
+- **Ganhando relevância:** quando o anúncio do seller está em primeiro lugar ou empatado em primeiro.  
+- **Perdendo relevância:** quando o anúncio do seller não está em primeiro lugar na busca por aquele produto.  
+- **Processando relevância:** quando as informações do anúncio estão sendo avaliadas pelo Mercado Livre.  
+
+## Tipos de oportunidades
+
+Três tipos de oportunidades podem ser disponibilizadas para os anúncios de um seller, **Aviso prévio, Obrigatório** e **Opcional.** Em todas as oportunidades listadas pelo Mercado Livre o seller tem a opção de vincular o produto a um anúncio e caso não tenha correspondência do anúncio do seller com uma oferta de catálogo, é necessário abrir um chamado no suporte do Mercado Livre.
+
+- **Aviso prévio:**  as oportunidades desse tipo são de caráter obrigatório e têm um prazo para serem vinculadas, ou seja, o seller precisa vincular o produto a uma oferta do catálogo Mercado Livre. Caso a vinculação não seja realizada no prazo determinado pelo Mercado Livre, o anúncio do seller será moderado pelo marketplace.  
+![oportunidade-avisoprevio-pt](//images.ctfassets.net/alneenqid6w5/wSTOwKrQ7AFCEtCNI2l5P/a0b2d2e0331096c95b082e72fc0ba9a0/Captura_de_tela_2024-04-30_184708.png)
+
+- **Obrigatória:** as oportunidades desse tipo são de caráter obrigatório, mas não têm um prazo para serem vinculadas, mas caso o anúncio não seja vinculado, o Mercado Livre poderá moderar o anúncio do seller no marketplace.  
+
+![oportunidade-obrigatoria-pt](//images.ctfassets.net/alneenqid6w5/3z59cnsyTgy1QGQdZ3OGyH/e00a9c162c596956e5eb1663b9802a67/Captura_de_tela_2024-04-30_185306.png)
+
+- **Opcional:** as oportunidades desse tipo não são de caráter obrigatório. Caso a vinculação não seja realizada, o anúncio do seller não perde relevância e nem é bloqueado pelo marketplace.  
+
+![oportunidade-opcional-pt](//images.ctfassets.net/alneenqid6w5/2vXdrBmj4ba5iXobKSv8B2/402b94780b58a9817413ab543cb6f544/Captura_de_tela_2024-04-30_185642.png)  
+
+## Analisar oportunidade
+
+Na aba **Oportunidades** é possível analisar e vincular as oportunidades, independente de seu tipo. As vinculações podem ser realizadas [individualmente](#vinculacao-individual) ou em [massa](#vinculacao-em-massa).
+
+Para analisar uma oportunidade, o seller utiliza a página **Match de anúncios**, que pode ser acessada em **Admin VTEX > Marketplace > Mercado Livre > Match de anúncios,** ou digitar **Match de anúncios** na barra de busca do Admin VTEX.
+
+A tela **Analisar oportunidade,** aparecerá quando o seller clicar no botão **`Analisar oportunidade`** em um dos anúncios disponíveis na aba **Oportunidades.**  
+Nessa tela o seller visualizará do lado esquerdo o seu produto cadastrado no catálogo VTEX e do lado direito o produto do catálogo Mercado Livre que foi sugerido para vinculação.
+
+![analisar-oportunidade-pt](//images.ctfassets.net/alneenqid6w5/79EgKpmRxwlWvMUzaERmk4/840d4be11a3b133042499ee3786b7227/Captura_de_tela_2024-04-30_193248.png)  
+
+### Vinculação individual
+
+Para vincular as oportunidades individualmente, após acessar a página **Match de anúncios** siga os seguintes passos:
+
+1. Na oportunidade desejada clique no botão **`Analisar oportunidade`.**  
+2. Confira se os dados do anúncio sugerido pelo Mercado Livre são compatíveis com os dados do seu produto.  
+3. Clique no botão **`Aceitar sugestão`.**   
+4. Clique no botão **`Confirmar`**.  
+
+![aceitar-sugestão-pt](//images.ctfassets.net/alneenqid6w5/7dH1vRXEHyXBMSOr3IaehY/254d43b67aa8f40b47247f15c909ed9e/Captura_de_tela_2024-04-30_192650.png)  
+
+Após vincular, o anúncio é publicado no catálogo Mercado Livre e enviado para a **Aba catálogos ativos** sob o status de **Processando relevância.**
+
+Caso os produtos não sejam correspondentes, o seller deve buscar um anúncio no catálogo Mercado Livre que seja correspondente ao seu produto para realizar a vinculação.
+
+Para procurar outros anúncios no catálogo Mercado Livre,  o seller deve digitar o nome de seu produto na barra de busca que está abaixo da foto principal do produto na página **`Analisar oportunidade`.** Veja na imagem abaixo:
+
+![buscar-anuncio-pt](//images.ctfassets.net/alneenqid6w5/5xdQ2BlXl6KgQq2Y6fvD2N/18b9333ef684e6cc478e1c08c17f237d/Captura_de_tela_2024-04-30_194057.png)  
+
+### Vinculação em massa
+
+Para vincular as oportunidades massivamente, após acessar a página **Match de anúncios** siga os seguintes passos:
+
+1. Selecione as oportunidades que deseja vincular. Um pop-up aparecerá na parte  inferior da tela.
+2. Clique no botão **`Aceitar sugestões`.**
+3. Clique no botão **`Confirmar`.**
+
+![aceitar-sugestão-bulk-pt](//images.ctfassets.net/alneenqid6w5/5Eq1eBQB2BgqO6xbtLByQr/0e4bdfc9f7b37ba8684dcb72ad7d6ae6/Captura_de_tela_2024-04-30_192556.png)  
+
+Após vincular, o anúncio é publicado no catálogo Mercado Livre e enviado para a **Aba catálogos ativos** sob o status de **Processando relevância.**
+
diff --git a/docs/tutorials/pt/media-overview.md b/docs/tutorials/pt/media-overview.md
index ae69fb6a3..17dc95ce9 100644
--- a/docs/tutorials/pt/media-overview.md
+++ b/docs/tutorials/pt/media-overview.md
@@ -3,8 +3,8 @@ title: 'Mídia - Visão geral'
 id: 31fhjHTt4TBoo50AmGQ9b2
 status: PUBLISHED
 createdAt: 2023-05-29T23:26:35.354Z
-updatedAt: 2023-05-31T12:29:38.226Z
-publishedAt: 2023-05-31T12:29:38.226Z
+updatedAt: 2024-07-03T19:28:25.937Z
+publishedAt: 2024-07-03T19:28:25.937Z
 firstPublishedAt: 2023-05-30T18:01:54.161Z
 contentType: tutorial
 productTeam: VTEX IO
@@ -15,61 +15,120 @@ legacySlug: midia-visao-geral
 subcategory: 27t6x0lngvjI3bnUg5AgEO
 ---
 
-O Mídia é responsável por gerenciar os arquivos de mídia da sua loja, como imagens e gifs. Você pode fazer o upload e organizar arquivos de mídia usando o Mídia nos seguintes formatos: `PNG`, `JPG`, `GIF`, `SVG` e `WEBP`.
-![Mídia Visão Geral](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/1daf233a39aa1f3e4bd5b42b1f4b8805/pt-m__dia-overview.png)
+O Mídia é uma funcionalidade responsável por gerenciar os arquivos de mídia da sua loja, como imagens e vídeos. Para imagens, você pode fazer o upload e organizar arquivos de mídia de até 5 MB usando o Mídia nos seguintes formatos: `png`, `jpg`, `gif`, `svg` e `webp`. Para vídeos, você pode adicionar uma URL para o provedor de vídeo hospedado externamente, como YouTube ou Vimeo.
 
-Além disso, o Mídia está integrado ao **Site Editor** e ao **Headless CMS**. Essa integração permite que você acesse e gerencie o Mídia diretamente através das soluções de CMS da VTEX.
+<div class="alert alert-warning">
+  Para upload, os arquivos devem ter uma extensão em minúsculo, por exemplo, <code>store.png</code>, e tamanho de até <b>5 MB</b>.
+</div>
+
+![Mídia Visão Geral](//images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/1daf233a39aa1f3e4bd5b42b1f4b8805/pt-m__dia-overview.png)
+
+Além disso, o Mídia está integrado ao **Site Editor** e ao **Headless CMS**, o que permite que ele seja acessado e gerenciado diretamente através de soluções de CMS da VTEX. 
 
 Neste guia, aprenda a:
 
 - [Acessar o Mídia no Admin](#acessando-o-midia)
 - [Gerenciar Arquivos no Mídia no Admin](#gerenciando-arquivos-no-midia)
 
-## Acessando o Mídia
+## Acessar o Mídia
 Há três maneiras de acessar o Mídia no Admin:
 
-- **Mídia**: No VTEX Admin, acesse **Storefront > Mídia**. 
+- **Mídia**: no VTEX Admin, acesse **Storefront > Mídia**. 
 
-- **Site Editor** (para lojas que usam o Store Framework): No VTEX Admin, acesse **Storefront > Site Editor**, escolha um bloco que contenha uma imagem (por exemplo, Carrossel), e clique em `Adicionar`.  Um modal do Mídia será aberto.
+- **Site Editor** (para lojas que usam o Store Framework): no VTEX Admin, acesse **Storefront > Site Editor**, escolha um bloco que contenha uma imagem (por exemplo, Carrossel), e clique em `Adicionar`.  Um painel do Mídia será aberto.
 
-- **Headless CMS**:  No VTEX Admin, acesse **Storefront > Headless CMS** e escolha uma das páginas criadas, por exemplo, uma Página de Produto. Nas seções disponíveis, selecione uma na qual você possa adicionar uma imagem (por exemplo, Hero), clique no componente de imagem do Hero e um modal do Mídia será aberto.
+- **Headless CMS**:  no VTEX Admin, acesse **Storefront > Headless CMS** e escolha uma das páginas criadas, por exemplo, uma Página de Produto. Nas seções disponíveis, selecione uma na qual você possa adicionar uma imagem, por exemplo, [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero). Clique no componente de imagem do Hero e um painel do Mídia será aberto.
+
+<div class="alert alert-warning">
+A seção disponível deve utilizar o <a href="https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms">media-gallery</a> para aproveitar o Mídia. Para projetos <a href="https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore">FastStore</a>, as seções que utilizam o widget  <i>media-gallery</i> são <a href="https://developers.vtex.com/docs/guides/faststore/organisms-navbar">Navbar</a> and <a href="https://developers.vtex.com/docs/guides/faststore/organisms-hero">Hero</a>.
+</div>
 
 Na imagem a seguir, confira a visão geral da interface do Mídia e as ações disponíveis para gerenciar seus arquivos de mídia:
 
-![Mídia Features](https://images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/4ffd0d22e2c3ce0173f5643177728be4/pt-m__dia-features.png)
+![Mídia Features](//images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/4ffd0d22e2c3ce0173f5643177728be4/pt-m__dia-features.png)
 
 | Campo | Descrição |
 | ---------- | ------------- |
-| **I - Campo de Busca** | Pesquise os arquivos disponíveis no Mídia. |
+| **I - Campo de busca** | Pesquise os arquivos disponíveis no Mídia. |
 | **II - Ordenar por** | Classifique como os arquivos são exibidos na interface com base nos filtros: `Mais recentes`, `Mais antigos`, `Nome (A-Z)` e `Nome (Z-A)`. |
 | **III - Paginação** | Navegue pelas páginas de arquivos disponíveis. |
-| **IV - Modo de visualização** |	Escolha o modo de visualização dos arquivos: `Visualizar em Lista` ou `Visualizar em Grade`. |
-| **V - Adicionar imagem** | Carregue um novo arquivo de sua máquina local. |
+| **IV - Modo de visualização** |	Escolha o modo de visualização dos arquivos: `Visualizar em lista` ou `Visualizar em grade`. |
+| **V - Adicionar nova imagem ou vídeo** | Carregue um novo arquivo de sua máquina local. |
 
-## Gerenciando arquivos no Mídia
+## Gerenciar arquivos no Mídia
 Veja nas seções abaixo as ações disponíveis para gerenciamento de arquivos no Mídia:
 
-### Fazendo upload de arquivos para o Mídia
-1. Na página **Mídia**, clique em `Adicionar novo`.
-2. Escolha a imagem em sua máquina que deseja adicionar e clique em `Abrir`.
+### Upload de imagens
+
+No Mídia, você pode fazer upload de imagens nos seguintes formatos: `png`, `jpg`, `gif`, `svg` e `webp`, com um limite de tamanho de arquivo de 5 MB. Para fazer o upload da imagem da sua loja, siga estes passos:
+
+1. Na página ou no painel **Mídia**, clique em `Adicionar novo(a)` e clique em `Imagem`.
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
- Lembre-se, o Mídia aceita os seguintes formatos: <i>PNG</i>, <i>JPG</i>, <i>GIF</i>, <i>SVG</i>, and <i>WEBP</i>.
+<div class="alert alert-warning">
+  <p>No painel Mídia disponível no Headless CMS e no Site Editor, você pode arrastar e soltar imagens.</p>
 </div>
 
-3. Depois que a imagem é carregada, uma mensagem de sucesso aparecerá. Agora, você pode executar outras ações clicando em `Mais ações` (três pontos verticais) na miniatura da imagem e escolhendo uma das seguintes ações:
+2. Escolha a imagem que deseja adicionar e clique em `Abrir`.
+
+<div class="alert alert-warning">
+ Lembre-se, o Mídia aceita os seguintes formatos: <code>png</code>, <code>jpg</code>, <code>gif</code>, <code>svg</code>, e <code>webp</code>, em minúsculo e com um limite de tamanho de arquivo de 5 MB.
+</div>
+
+3. Depois que a imagem é carregada, uma mensagem de sucesso será exibida. Agora, você pode executar outras ações clicando em `Mais ações` (três pontos verticais) na miniatura da imagem e escolhendo uma das seguintes ações:
 
 | Campo | Descrição |
 | ---------- | ------------- |
-| **Visualizar** | Abre a imagem em uma nova página. |
+| **Pré-visualizar** | Abre a imagem em uma nova página. |
 | **Copiar URL** | Copia a URL da imagem para que você possa utilizá-la em outras seções da sua loja. |
 | **Baixar** | Faz o download da imagem para o seu computador. |
 | **Excluir** |	Remove a imagem do repositório. |
 
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
- Excluir a imagem apenas a removerá do repositório do Mídia. Se você adicionou a imagem em um componente Hero, por exemplo, a imagem continuará sendo utilizada neste componente. Porém, você não poderá usá-la em outros componentes.
+<div class="alert alert-warning">
+Excluir a imagem apenas a removerá do repositório do Mídia. Se você adicionou a imagem em um componente Hero, por exemplo, a imagem continuará sendo utilizada neste componente. Porém, você não poderá usá-la em outros componentes.
 </div>
 
-### Cancelando um upload no Mídia
-Se você estiver carregando uma nova imagem e não quiser continuar, pode cancelá-la clicando no `X` sobreposto na miniatura da imagem.
+### Adicionar vídeos
+
+Além de imagens, no Mídia, você também pode armazenar vídeos e, em seguida, usá-los em sua loja para criar apelo visual para os usuários.
+
+1. Na página **Mídia**, clique em `Adicionar novo(a)` e escolha `Vídeo`.
+2. No modal, preencha o nome e a URL do vídeo conforme necessário.
+
+- **Nome do vídeo:** adicione um nome para o vídeo que o ajude a identificá-lo melhor na galeria.
+- **URL do vídeo:** adicione a URL do vídeo.
+
+3. Clique em `Adicionar vídeo`.
+
+Com o vídeo adicionado, você pode escolher o que fazer com ele clicando no menu `⋮` na miniatura do vídeo:
+
+- **Copiar URL:** obtenha o endereço URL do vídeo para usar em sua loja por meio do Headless CMS.
+- **Abrir vídeo:** veja uma prévia do vídeo em uma nova aba do navegador.
+- **Excluir:** exclua o vídeo da sua galeria.
+
+### Adicionar um vídeo ao conteúdo no Headless CMS
+
+Integrar conteúdo multimídia, como vídeos, no Headless CMS pode melhorar a experiência do usuário em seu site. Siga os passos abaixo para adicionar vídeos à sua loja.
+
+1. No VTEX Admin, acesse **Storefront > Headless CMS**.
+2. Selecione o [projeto](https://help.vtex.com/pt/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) ao qual você deseja adicionar o vídeo.
+3. Escolha uma página para adicionar o vídeo, por exemplo, **Página inicial**.
+4. Com a **Página inicial** aberta, na aba **Seções**, adicione (`+`) uma seção que tenha o widget `media-gallery`, ex.: Hero.
+5. No Hero, preencha os seguintes campos:
+
+- **Endereço URL:** cole a URL que você copiou do Mídia.
+- **Descrição do vídeo:** descrição do vídeo para acessibilidade.
+
+6. Clique em `Salvar`.
+7. Se desejar verificar suas alterações antes de publicá-las, clique em `Visualizar`.
+
+### Cancelar um upload
+
+- **Imagens**
+
+Se você estiver carregando uma nova imagem e não quiser continuar, clique no `X` sobreposto na miniatura da imagem para cancelar.
+
+- **Vídeos**
+
+Depois de ter feito o upload do vídeo, passe o mouse sobre a miniatura do vídeo e clique no menu (`⋮`). Selecione **Excluir**.
+Se este vídeo já estiver sendo usado em algum lugar da sua loja, ele permanecerá lá, mas não estará disponível para uso futuro.
 
diff --git a/docs/tutorials/pt/mercado-libre-promotions.md b/docs/tutorials/pt/mercado-libre-promotions.md
index 5fed2d8c9..b34c213e3 100644
--- a/docs/tutorials/pt/mercado-libre-promotions.md
+++ b/docs/tutorials/pt/mercado-libre-promotions.md
@@ -21,7 +21,7 @@ Para proporcionar maior agilidade à operação do seller, na barra de busca glo
 
 Para acessar a página de promoções disponíveis no Admin VTEX, você deve seguir o caminho __Marketplace > Mercado Livre > Promoções.__  
 
-![Promoções do mercado livre](https://images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
+![Promoções do mercado livre](//images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
 
 ## Tipos de promoções  
 
diff --git a/docs/tutorials/pt/mercado-libre-size-chart.md b/docs/tutorials/pt/mercado-libre-size-chart.md
new file mode 100644
index 000000000..d0ceb2334
--- /dev/null
+++ b/docs/tutorials/pt/mercado-libre-size-chart.md
@@ -0,0 +1,137 @@
+---
+title: 'Tabela de medidas do Mercado Livre'
+id: 5dCc9IJ83SjllG75BVCWnr
+status: PUBLISHED
+createdAt: 2024-07-23T20:28:35.058Z
+updatedAt: 2024-07-23T21:11:23.954Z
+publishedAt: 2024-07-23T21:11:23.954Z
+firstPublishedAt: 2024-07-23T21:11:23.954Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: tabela-de-medidas-do-mercado-livre
+locale: pt
+legacySlug: tabela-de-medidas-do-mercado-livre
+subcategory: 4uqMnZjwBO04uWgCom8QiA
+---
+
+A Tabela de medidas permite que os clientes saibam o tamanho aproximado do seu produto, proporcionando uma melhor experiência no momento de selecionar o tamanho de um produto. Ao informar detalhadamente as medidas do seu produto, você evita devoluções e reclamações por tamanho errado.  
+
+Ao receber menos devoluções de seus produtos, sua reputação no Mercado Livre melhora e exposição dos seus produtos. A tabela de medidas está disponível para produtos das categorias de __calçados, top clothes e bottom clothes.__ As medidas são feitas em centímetros (cm).  
+
+A tabela de medidas é personalizável, ou seja, é possível selecionar opções de tabelas conforme a sua necessidade, com as medidas aproximadas de cada tamanho do produto disponível.   
+
+## Adicionar tabela personalizada
+
+Para adicionar a tabela de medidas personalizada, você deve seguir os passos abaixo:  
+
+1. Acesse o Admin VTEX vá em  __Marketplace > Marketplaces e Integrações.__  
+2. Selecione a integração com o Mercado Livre.  
+3. Selecione a opção `Realizar mapeamento`. Uma nova janela será aberta com a interface de mapeamento.  
+4. Selecione a categoria que deseja enviar uma Tabela de medida.  
+5. Na seção __Tabela de medida,__ clique no ícone +.   
+6. Selecione a opção __Tabela personalizada.__  
+7. Preencha um nome válido para sua tabela no campo __Nome da tabela.__  
+8. No campo __Domínio,__ selecione a opção para sua tabela personalizada.  
+9. No campo __Gênero,__ selecione a opção correspondente ao gênero do produto.  
+  Existem cinco tipos de gêneros diferentes:
+    - __Feminino__  
+    - __Masculino__  
+    - __Meninas__  
+    - __Meninos__  
+    - __Bebês__ 
+    - __Sem gênero__  
+    - __Sem gênero infantil__  
+
+10. No campo __Tamanho principal,__ escolha uma opção de modelo de tabela. Existem cinco modelos diferentes:  
+    - __BR:__ utiliza os tamanhos padrões de tamanho no Brasil.  
+    - __Tamanho da marca:__ utiliza os tamanhos padrões da marca do produto selecionado.  
+    - __US:__ utiliza as medidas padrões de tamanho nos Estados Unidos. As medidas podem variar de acordo com o gênero.  
+    - __EU:__ utiliza as medidas padrões de tamanho na União Europeia.  
+    - __UK:__ utiliza as medidas padrões de tamanho no Reino Unido.  
+11. No campo __Template,__ clique em CSV. Você realizará o download de um template de tabela que precisa ser preenchido conforme as instruções da seção [Preencher o template da Tabela de Medidas](#preencher-o-template-da-tabela-de-medidas).  
+
+## Preencher o template da Tabela de medidas
+
+Para cada categoria mapeada, é necessário enviar uma __Tabela de medidas__ e todas as colunas da tabela devem ser preenchidas. Caso você opte por não informar ou utilizar algumas das medidas padrões, preencha com um `-`.  
+
+Nesse template, você deverá configurar as colunas e preencher com os valores dos tamanhos e medidas em centímetros dos respectivos tamanhos.  
+
+Para configurar automaticamente a planilha acesse __Dados > Texto para colunas,__ selecione a opção __Delimitado,__ clique em Avançar. No campo __Delimitadores,__ selecione a opção __Vírgula,__ clique em __Avançar,__ e finalize clicando em __Concluir.__
+
+### Tabela de calçados
+
+O template da tabela de medidas para calçados possui as seguintes colunas:  
+
+| **Coluna** | **Descrição** | **Preenchimento** |
+|:---:|:---:|:---:|
+| **Foot Length** | Medida em centímetros do tamanho do pé | Preencha cada linha com a medida em centímetros dos tamanhos que serão preenchidos nas próximas colunas. Por exemplo, 45 cm |
+| **Foot Length to** | Medida em centímetros do tamanho máximo que o pé deve ter para se acomodar no respectivo tamanho | Preencha cada linha com a medida em centímetros dos tamanhos máximos que serão preenchidos nas próximas colunas. Por exemplo, 50 cm.  |
+| **Manufacturer Size** | Número da medida padrão de tamanho da marca do produto selecionado | Preencha cada linha com a medida padrão da marca do produto |
+| **BR Size** | Número da medida padrão de tamanho no Brasil | Preencha cada linha com o tamanho correspondente seguido de BR. Por exemplo, 38 BR |
+| **US Size** | Número da medida padrão de tamanho nos Estados Unidos. As medidas podem variar de acordo com o gênero | Preencha cada linha com o tamanho correspondente seguido de US. Por exemplo, 24 US  |
+| **EU Size** | Número da medida padrão de tamanho na União Europeia | Preencha cada linha com o tamanho correspondente seguido de EU. Por exemplo, 40 EU |
+| **UK Size** | Número da medida padrão de tamanho no Reino Unido. | Preencha cada linha com o tamanho correspondente seguido de UK. Por exemplo, 12 UK |
+
+### Tabela top clothes
+
+O template da tabela de medidas para roupas da parte superior possui as seguintes colunas:  
+
+| **Coluna** | **Descrição** | **Preenchimento** |
+|:---:|:---:|:---:|
+| **Size** | Tamanho da roupa. | Preencha cada linha com os tamanhos da roupa. Por exemplo, GG. |
+| **Filtrable_size** | Tamanho filtrável disponível para a categoria. | Preencha cada linha com o tamanho disponível para filtro. Por exemplo, XG. |
+| **Chest_circumference_from** | Circunferência do peito (tórax) - início do intervalo de medidas. | Preencha cada linha com a medida mínima em centímetros do tamanho do tórax. Por exemplo, 80 cm. |
+| **Chest_circumference_to** | Circunferência do peito (tórax) - final do intervalo de medidas. | Preencha cada linha com a medida máxima em centímetros do tamanho do tórax. Por exemplo, 88 cm. |
+| **Waist_circumference_from** | Circunferência da cintura - início do intervalo de medidas. | Preencha cada linha com a medida mínima da largura da cintura em centímetros. Por exemplo, 70 cm. |
+| **Waist_circumference_to** | Circunferência da cintura - fim do intervalo de medidas. | Preencha cada linha com a medida máxima da largura da cintura em centímetros. Por exemplo, 77 cm. |
+| **Person_height_from** | Altura da pessoa - início do intervalo de medidas. | Preencha cada linha com a medida mínima da altura de uma pessoa em centímetros. Por exemplo, 168 cm. |
+| **Person_height_to** | Altura da pessoa - fim do intervalo de medidas. | Preencha cada linha com a medida mínima da altura de uma pessoa em centímetros. Por exemplo, 178 cm. |
+| **Hip_circumference_from** | Circunferência do quadril - início do intervalo de medidas. | Preencha cada linha com a medida mínima da largura do quadril em centímetros. Por exemplo, 109 cm. |
+| **Hip_circumference_to** | Circunferência do quadril - fim do intervalo de medidas. | Preencha cada linha com a medida máxima da largura do quadril em centímetros. Por exemplo, 119 cm. |
+| **Neck_circumference_from** | Circunferência do pescoço - início do intervalo de medidas. | Preencha cada linha com a medida mínima da largura do pescoço em centímetros. Por exemplo, 35 cm. |
+| **Neck_circumference_to** | Circunferência do pescoço - fim do intervalo de medidas. | Preencha cada linha com a medida mínima da largura do pescoço em centímetros. Por exemplo, 38 cm. |
+
+### Tabela bottom clothes
+
+O template da tabela de medidas para roupas da parte inferior possui as seguintes colunas:
+
+| **Coluna** | **Descrição** | **Preenchimento** |
+|:---:|:---:|:---:|
+| **Size** | Tamanho da roupa. | Preencha cada linha com os tamanhos da roupa. Por exemplo, GG. |
+| **Filtrable_size** | Tamanho filtrável disponível para a categoria. | Preencha cada linha com o tamanho disponível para filtro. Por exemplo, 44. |
+| **Waist_circumference_from** | Circunferência da cintura - início do intervalo de medida. | Preencha cada linha com a medida mínima da largura da cintura em centímetros. Por exemplo, 70 cm. |
+| **Waist_circumference_to** | Circunferência da cintura - fim do intervalo de medida. | Preencha cada linha com a medida máxima da largura da cintura em centímetros. Por exemplo, 77 cm. |
+| **Hip_circumference_from** | Circunferência do quadril - início do intervalo de medida. | Preencha cada linha com a medida mínima do tamanho do quadril em centímetros. Por exemplo, 109 cm. |
+| **Hip_circumference_to** | Circunferência do quadril - fim do intervalo de medida. | Preencha cada linha com a medida máxima do tamanho do quadril em centímetros. Por exemplo, 115 cm. |
+| **Length_from_inseam_to_ankle_from** | Comprimento da perna, medido a partir da virilha até o tornozelo - início do intervalo de medida. | Preencha cada linha com a medida mínima do tamanho da perna em centímetros. Por exemplo, 75 cm. |
+| **Length_from_inseam_to_ankle_to** | Comprimento da perna, medido a partir da virilha até o tornozelo - fim do intervalo de medida. | Preencha cada linha com a medida máxima do tamanho da perna em centímetros. Por exemplo, 85 cm. |
+| **Length_from_waist_to_ankle_from** | Comprimento da perna, medido a partir da cintura até o tornozelo - início do intervalo de medida. | Preencha cada linha com a medida mínima do tamanho da perna em centímetros. Por exemplo, 80 cm. |
+| **Length_from_waist_to_ankle_to** | Comprimento da perna, medido a partir da cintura até o tornozelo - fim do intervalo de medida. | Preencha cada linha com a medida máxima do tamanho da perna em centímetros. Por exemplo, 88 cm. |
+| **Thigh_circumference_from** | Circunferência da coxa - início do intervalo de medida. | Preencha cada linha da coluna com a medida mínima do tamanho da coxa em centímetros. Por exemplo, 50 cm. |
+| **Thigh_circumference_to** | Circunferência da coxa - fim do intervalo de medida. | Preencha cada linha da coluna com a medida máxima do tamanho da coxa em centímetros. Por exemplo, 58 cm. |
+| **Person_height_from** | Altura da pessoa - início do intervalo de medidas. | Preencha cada linha com a medida mínima da altura de uma pessoa em centímetros. Por exemplo, 188 cm. |
+| **Person_height_to** | Altura da pessoa - fim do intervalo de medidas. | Preencha cada linha com a medida mínima da altura de uma pessoa em centímetros. Por exemplo, 193 cm. |
+
+<div class="alert alert-info">
+  É necessário utilizar espaço entre o número e a medida (cm), separar os números utilizando pontos (.), preencher todas as colunas com o tamanho do corpo, e conferir se os campos <b>Gênero</b> e <b>Tamanho</b> foram selecionados corretamente.
+  </div>
+
+## Fazer upload da Tabela de medidas
+
+Após preencher a planilha de mapeamento, faça o seu upload:  
+
+1. Acesse o Admin VTEX > __Marketplace > Marketplaces e Integrações.__  
+2. Selecione a integração com o Mercado Livre.  
+3. Selecione a opção `Realizar mapeamento`. Uma nova janela será aberta com a interface de mapeamento.  
+4. Na seção __Tabela de medida,__ clique no ícone +.   
+5. Selecione a opção Tabela personalizada.  
+6. Clique em `Escolha um arquivo`.  
+7. Selecione o arquivo da planilha que você preencheu.  
+8. Clique em `Adicionar`.   
+
+Ao finalizar, sua tabela de medida personalizada terá sido criada com sucesso.  
+
+<div class="alert alert-info">
+  Caso ocorra algum erro, o problema será indicado na tela de upload. O erro deve ser resolvido e o upload deverá ser realizado novamente.
+  </div>
diff --git a/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md b/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
index 623b0afe3..be92cae86 100644
--- a/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
+++ b/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
@@ -29,7 +29,7 @@ Nos anúncios enviados ao Mercado Livre é possível identificar quais apresenta
 Os anúncios que apresentarem erro, não serão enviados ao Mercado Livre até que seja corrigido.
 </div>  
 
-![Mercado Livre: Compatibilidade Automobilística](https://images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/71bc2c07df8a14d172a0f58afb4e99f8/compatibilidade_automobilistica_1.png)  
+![Mercado Livre: Compatibilidade Automobilística](//images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/71bc2c07df8a14d172a0f58afb4e99f8/compatibilidade_automobilistica_1.png)  
 
 Para acessar o módulo de Gerenciamento de anúncios, no Admin VTEX vá em Marketplace > Integrações > Gerenciamento de anúncios. Nesta página você pode filtrar os anúncios por, canal, marca, categoria ou status.
 
@@ -39,7 +39,7 @@ Para corrigir os erros de `Compatibilidade com Meli`, siga o passo a passo abaix
 2. Clique em __Error de associação de autopeças.__  
 3. Clique em __Gerenciar compatibilidade.__  
 4. Preencha os campos, __marca, modelo, ano__ e __versão,__ conforme a compatibilidade do acessório.  
-![Mercado Livre: Compatibilidade Automobilística 2](https://images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/581cda2b20d2cccec1fc818a2a4153b7/comopatibilidade_automobilistica_2.png)  
+![Mercado Livre: Compatibilidade Automobilística 2](//images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/581cda2b20d2cccec1fc818a2a4153b7/comopatibilidade_automobilistica_2.png)  
 5. Adicione todos os modelos de veículos compatíveis clicando em +.
 6. Clique no botão __Adicionar exceção__ e aguarde a mensagem “exceção enviada com sucesso”.
 7. Clique em __Confirmar__ e a mensagem “compatibilidade associada com sucesso” aparecerá na tela.  
diff --git a/docs/tutorials/pt/mercado-livre-faq.md b/docs/tutorials/pt/mercado-livre-faq.md
index 993b875cc..cf0ec0adf 100644
--- a/docs/tutorials/pt/mercado-livre-faq.md
+++ b/docs/tutorials/pt/mercado-livre-faq.md
@@ -125,7 +125,7 @@ Ao cadastrar um produto, é necessário estabelecer uma quantidade mínima para
 
 A categoria em questão exige o mapeamento de marca e modelo. Essas informações devem estar presentes na planilha de mapeamento. Formato de exemplo:
 
-![mercadolivre faq erro](https://images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
+![mercadolivre faq erro](//images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
 
 ### Por que meu anúncio está desativado no Mercado Livre?
 
@@ -165,13 +165,13 @@ No entanto, esses atributos são bastante claros (Cor principal, Cor secundária
 
 Se algum desses atributos for preenchido incorretamente (por exemplo, se você atribuiu um código referente a Tamanho de cinto para um calçado), o Integrações vai retornar um erro com o seguinte formato:
 
-![mercadolivre faq erro2](https://images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
+![mercadolivre faq erro2](//images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
 
 Neste caso, temos dois exemplos de erros na mesma mensagem.
 
 O primeiro deles indica que o atributo cujo código se inicia com o número `113000` é necessário para a categoria escolhida e não foi inserido na planilha de mapeamento. Veja a planilha abaixo:
 
-![mercadolivre faq erro3](https://images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
+![mercadolivre faq erro3](//images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
 
 O segundo erro indica que o atributo cujo código se inicia com o número `63000`, inserido na última coluna da planilha acima, é inválido para a categoria escolhida.
 
@@ -216,7 +216,7 @@ Existe o elemento principal do anúncio e ele contém as variações (que são o
 
 Acontece que cada categoria tem sua especificação de quantidade de imagens que podem ser adicionadas, para o caso da categoria MLA3697 são somente 12 imagens permitidas para esse elemento principal. Veja [aqui](https://api.mercadolibre.com/categories/MLA3697) as condições dessa categoria. 
 
-![mercadolivre faq erro4](https://images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
+![mercadolivre faq erro4](//images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
 
 `Sku não integrado pois o mesmo não possui descrição`
 
@@ -252,7 +252,7 @@ Dito isso, o primeiro passo é acessar o cadastro dessa integração:
 1. Acesse o módulo __Marketplace__
 2. Clique em __Integrações__
 3. Procure o __painel__ do Mercado Livre
-4. Clique na __engrenagem__ <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
+4. Clique na __engrenagem__ <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3GKATZh3AUzyZ2LzqvXZSg/f1db9ae88c6bcf0ed632df42133213d4/gear.png" />
 5. Clique em __Editar configuração__
 
 A partir daí, é preciso refazer o processo de integração.
diff --git a/docs/tutorials/pt/merchandising-rule-conditions.md b/docs/tutorials/pt/merchandising-rule-conditions.md
new file mode 100644
index 000000000..1d677cc14
--- /dev/null
+++ b/docs/tutorials/pt/merchandising-rule-conditions.md
@@ -0,0 +1,32 @@
+---
+title: 'Condições de Regras de merchandising'
+id: 4K9WCBiQ4ndU396ZygDpc2
+status: PUBLISHED
+createdAt: 2024-06-27T17:17:15.295Z
+updatedAt: 2024-06-27T17:19:47.360Z
+publishedAt: 2024-06-27T17:19:47.360Z
+firstPublishedAt: 2024-06-27T17:18:32.359Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: condicoes-de-regras-de-merchandising
+locale: pt
+legacySlug: condicoes-de-regras-de-merchandising
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+As condições de regras de merchandising no [Editor manual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) e no [Editor visual (Beta)](https://help.vtex.com/pt/tutorial/criar-regra-de-merchandising-editor-visual-beta--6xteumx9MsDt0uEppbChu3) seguem o formato `{critério} {operador} {valor}`. Por exemplo, uma condição pode ter a estrutura `marca é athletic`, onde `marca` corresponde ao critério, `é` corresponde ao operador e `athletic `corresponde ao valor.
+
+Entenda os critérios e operadores possíveis para cada forma de edição nas tabelas a seguir:
+
+## Critérios
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"> <thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nome</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descrição</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operadores</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tipo de edição</th> </tr> </thead> <tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span></td> <td rowspan="2" class="t-body pa5">Palavra pesquisada pelo cliente que será relacionada à regra. Campo para preenchimento livre.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td rowspan="2" class="t-body pa5" ><strong>Editor manual:</strong><br>Regras de ativação<br>Regras de customização</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contém</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Pesquisa pelo exato ID de algum elemento do catálogo que será relacionado à regra. Os possíveis IDs são: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong> e <strong>EAN</strong>. Campo para preenchimento livre.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de customização</td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">categoria</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma categoria cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">departamento</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa um departamento cadastrado no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">marca</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma marca cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">product cluster names</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma coleção cadastrada no Catálogo da loja. A ordem dos produtos é determinada pela relevância do Intelligent Search.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promocao</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que valida se existe ao menos uma promoção vinculada ao item (<span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">yes</span>).</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sellername</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa o nome de um seller.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategoria</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma subcategoria cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{especificação}}</span></td> <td rowspan="2" class="t-body pa5" >Qualquer especificação ativa no Catálogo aparece como critério customizado, com os mesmos valores possíveis. O nome do critério é exatamente o nome da especificação cadastrada. Por exemplo, se houver uma especificação ativa chamada <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Cor</span>, o critério exibido será <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Cor</span>.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> </tbody> </table>
+
+<div class="alert alert-warning">
+  <p>Os critérios <code>departamento</code>, <code>categoria</code> e <code>subcategoria</code> só aparecem como opções para compor as Regras de merchandising se os três níveis de categoria estiverem previamente configurados no <strong>Catálogo</strong>.</p>
+</div>
+
+## Operadores
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"><thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nome</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descrição</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Critérios</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Exemplo</th> </tr></thead><tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">No caso de criação de uma regra no Editor manual utilizando o <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span> como critério, configura uma pesquisa com palavras exatas.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span></td> <td class="t-body pa5">Se você cadastrar <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> e um cliente pesquisar por <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span>, a regra de merchandising será acionada. Porém, se o cliente pesquisar por <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoção black friday</span>, a regra não será ativada.</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">Em outros cenários de edição, possibilita que outras condições além da atual também sejam aplicadas.</td> <td class="t-body pa5">Todos (com exceção de <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span>)</td> <td class="t-body pa5">Se a condição for marca é <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>, mesmo se o cliente selecionar na busca <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">hotsport</span>, <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sportist</span> e <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>, a regra de merchandising será acionada.</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contém</span></td> <td class="t-body pa5">No caso de criação de uma regra no Editor manual utilizando o <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span> como critério, configura uma pesquisa que não se restringe a palavras exatas.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span></td> <td class="t-body pa5">Se você cadastrar <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> e um cliente pesquisar por <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">black friday</span> ou expressões similares como <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoção black friday</span> a regra de merchandising será acionada.</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5">Restringe que apenas o filtro cadastrado seja selecionado.</td> <td class="t-body pa5">Todos (com exceção de <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span>)</td> <td class="t-body pa5">Se a condição for marca é <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>, e o cliente selecionar <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">hotsport</span> primeiro na busca, mesmo selecionando <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span> depois, a regra de merchandising não será acionada. Só funcionará se o primeiro filtro de marca selecionado for <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">athletic</span>.</td> </tr></tbody></table>
diff --git a/docs/tutorials/pt/merchandising-rules-list.md b/docs/tutorials/pt/merchandising-rules-list.md
new file mode 100644
index 000000000..d8bff694a
--- /dev/null
+++ b/docs/tutorials/pt/merchandising-rules-list.md
@@ -0,0 +1,69 @@
+---
+title: 'Lista de Regras de merchandising'
+id: 3CZOjyie1LZVOhzeviVCgu
+status: PUBLISHED
+createdAt: 2024-07-03T17:08:55.426Z
+updatedAt: 2024-07-03T17:10:24.720Z
+publishedAt: 2024-07-03T17:10:24.720Z
+firstPublishedAt: 2024-07-03T17:10:24.720Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: lista-de-regras-de-merchandising
+locale: pt
+legacySlug: lista-de-regras-de-merchandising
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+No Admin VTEX, a página **Storefront** > **Intelligent Search** > **Regras de merchandising** permite que você realize as seguintes ações: 
+
+* [Criar regra de merchandising](#criar-regras-de-merchandising)
+* [Buscar regra de merchandising](#buscar-regras-de-merchandising)
+* [Editar regra de merchandising](#editar-regras-de-merchandising)
+* [Excluir regra de merchandising](#excluir-regras-de-merchandising)
+
+![regras-merch-pt](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/725d7d991d98ca633d7efd56ec14a254/regras-merch-pt.PNG)
+
+| Coluna | Descrição |
+| - | - |
+| __Nome__ | Nome que identifica a regra de merchandising, definido na etapa [Criar regras de merchandising](#criar-regras-de-merchandising). |
+| __Data de início__ | Data que define o início da disponibilidade da regra de merchandising. |
+| __Data de término__ | Data que define o término da disponibilidade da regra de merchandising. |
+| __Tipo__ | Indica o [tipo de edição](#tipos-de-edicao) utilizado na regra de merchandising. |
+| __Ativo__ | Opção que ativa ou desativa uma regra de merchandising. |
+| __Ações__  <i class="fas fa-ellipsis-v"></i> | Menu com ações de `Editar` ou `Excluir` uma regra de merchandising. |
+
+### Criar regras de merchandising
+
+Para configurar uma regra de merchandising, clique em `+ Adicionar`. Saiba mais sobre todas as informações necessárias para criar uma regra de merchandising nas seções a seguir.
+
+#### Tipos de edição
+
+Existem dois tipos de edição para criar Regras de merchandising: o [Editor manual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8) e o [Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2ejly01m1w28RsZlCKowEr).
+
+Veja a seguir as funcionalidades de cada editor:
+
+| Funcionalidade | Descrição | Editor manual | Editor visual |
+|---|---|---|---|
+| Regras de ativação  | Definir condições para a Regra de merchandising ser ativada. | Sim | Sim |
+| Regras de customização | Controlar os resultados de busca a partir de condições específicas. | Sim | Não |
+| Pré-visualização | Visualizar uma prévia de como os resultados de busca aparecerão para os clientes durante a navegação na loja. | Não | Sim |
+| Reordenar resultados de busca | Alterar a ordem dos itens listados como resultados de busca. | Não | Sim |
+| Fixar produto nas primeiras posições | Definir que o produto sempre aparecerá nas primeiras posições dos resultados de busca. | Não | Sim |
+
+### Buscar regra de merchandising
+
+Para pesquisar uma regra de merchandising, digite o nome da regra de merchandising na barra de busca.
+
+### Editar regra de merchandising
+
+Você pode editar as informações uma regra de merchandising seguindo os passos abaixo.
+
+1. Clique no menu <i class="fas fa-ellipsis-v"></i> na linha da regra de merchandising e, em seguida, no botão <i class="fas fa-pencil-alt"></i> `Editar`.
+2. Altere a informação desejada da regra de merchandising.
+3. Clique em `Salvar`.
+
+### Excluir regra de merchandising
+
+Você pode deletar uma regra de merchandising clicando no menu <i class="fas fa-ellipsis-v"></i> na linha da regra der merchandising e, em seguida, no botão <i class="fas fa-trash"></i> `Excluir`.
+
diff --git a/docs/tutorials/pt/meta-tags-suiteshare.md b/docs/tutorials/pt/meta-tags-suiteshare.md
index 487a39ef5..95dadf254 100644
--- a/docs/tutorials/pt/meta-tags-suiteshare.md
+++ b/docs/tutorials/pt/meta-tags-suiteshare.md
@@ -19,11 +19,11 @@ Meta Tags são informações que são carregadas juntamente com o seu link, assi
 
 Meta tag no WhatsApp:
 
-![Meta Tags_Suitshare_1](https://images.ctfassets.net/alneenqid6w5/1vDto0Syulmk1FrMOc2i89/74ea4883a2c35c4149b76681f91f407d/Meta_Tags_Suitshare_1.png)
+![Meta Tags_Suitshare_1](//images.ctfassets.net/alneenqid6w5/1vDto0Syulmk1FrMOc2i89/74ea4883a2c35c4149b76681f91f407d/Meta_Tags_Suitshare_1.png)
 
 Meta tag no Facebook:
 
-![Meta Tags_Suitshare_2](https://images.ctfassets.net/alneenqid6w5/2q2emAMuyTEdQkG2vGoimB/6716bfd664b525f0557a99c676359bde/Meta_Tags_Suitshare_2.png)
+![Meta Tags_Suitshare_2](//images.ctfassets.net/alneenqid6w5/2q2emAMuyTEdQkG2vGoimB/6716bfd664b525f0557a99c676359bde/Meta_Tags_Suitshare_2.png)
 
 As Meta Tags servem como uma prévia do que o usuário irá encontrar quando clicar no seu link.
 
@@ -33,15 +33,15 @@ As Meta Tags servem como uma prévia do que o usuário irá encontrar quando cli
 
 No painel da VTEX Assisted Sales (SuiteShare), acesse a opção _**Atrair > Links**_.
 
-![Meta Tags_Suitshare_3](https://images.ctfassets.net/alneenqid6w5/1JG2XCOA4pYyJeQiWB2Hkv/fa3c65fd6506c7594b93f55e7b05fe8a/Meta_Tags_Suitshare_3.png)
+![Meta Tags_Suitshare_3](//images.ctfassets.net/alneenqid6w5/1JG2XCOA4pYyJeQiWB2Hkv/fa3c65fd6506c7594b93f55e7b05fe8a/Meta_Tags_Suitshare_3.png)
 
 Clique na seta para baixo, localizada no lado direito do link que você deseja editar as Meta Tags. Clique na opção **Meta tags**.
 
-![Meta Tags_Suitshare_4](https://images.ctfassets.net/alneenqid6w5/2mtMGJL5l7nE5w8GrPmfNm/6773c197d01eed56453f7d23b419211f/Meta_Tags_Suitshare_4.png)
+![Meta Tags_Suitshare_4](//images.ctfassets.net/alneenqid6w5/2mtMGJL5l7nE5w8GrPmfNm/6773c197d01eed56453f7d23b419211f/Meta_Tags_Suitshare_4.png)
 
 Em **Título**, você irá digitar o título do link. Nesse caso, utilizaremos um nome. Já na Descrição, você pode escrever um breve resumo do que você faz, de quem você é, o que a sua empresa vende, ou até mesmo, uma chamada para ação, como no exemplo. E por fim adicione uma imagem ao seu link. 
 
-![Meta Tags_Suitshare_5](https://images.ctfassets.net/alneenqid6w5/3voZYLGdaJE8BqWuHP40ix/7e55c30cfaf23bf4db1f84c63737d060/Meta_Tags_Suitshare_5.png)
+![Meta Tags_Suitshare_5](//images.ctfassets.net/alneenqid6w5/3voZYLGdaJE8BqWuHP40ix/7e55c30cfaf23bf4db1f84c63737d060/Meta_Tags_Suitshare_5.png)
 
 Clique no botão **Finalizar**.
 
diff --git a/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md b/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md
new file mode 100644
index 000000000..7892d3e26
--- /dev/null
+++ b/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md
@@ -0,0 +1,43 @@
+---
+title: 'Não consigo visualizar métricas no dashboard de pedidos'
+id: 1B5OAicmK3AvnwPzs4iq7Z
+status: PUBLISHED
+createdAt: 2024-06-10T11:28:08.507Z
+updatedAt: 2024-06-10T17:15:44.616Z
+publishedAt: 2024-06-10T17:15:44.616Z
+firstPublishedAt: 2024-06-10T17:15:44.616Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: nao-consigo-visualizar-metricas-no-dashboard-de-pedidos
+locale: pt
+legacySlug: nao-consigo-visualizar-metricas-no-dashboard-de-pedidos
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palavras-chave:** *dashboard, painel administrativo, visão geral, atualização, perfil de acesso.*
+
+Ao acessar o painel Admin, pode ser que sua loja não carregue métricas na **Visão geral** do dashboard, e vir acompanhadas de ícones de alerta e a mensagem "Ocorreu um problema". Isso pode ocorrer devido a:
+
+- **Atraso na atualização de dados:** pode haver um atraso na atualização das informações exibidas no dashboard.
+- **Período de comparação inadequado:** o período selecionado no canto superior direito do dashboard pode não conter dados de pedidos suficientes para a comparação.
+- **Permissões de acesso insuficientes:** você pode não ter o perfil de acesso necessário para visualizar determinadas informações no dashboard.
+
+![Visão geral - PT](//images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/466e5f7f843a9023750b32bb3397adbb/Vis_o_geral_-_PT.png)
+
+## Solução
+Para resolver inconsistências no dashboard inicial do painel administrativo, você pode testar as ações descritas abaixo:
+
+### Ajuste o período de comparação
+Ajustar o período de comparação pode resolver o problema ao exibir métricas que são relevantes.Para  verificar se o período selecionado em **Visão geral** do dashboard contém dados de pedidos válidos, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Dashboard > Visão geral**.
+2. No canto superior direito, selecione o período de comparação.
+
+![Dashboard- PT](//images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/77b35596da94175d044944a1f01de1b4/Dashboard-_PT.png)
+
+### Aguarde a atualização das informações
+Considere o tempo de espera de 10 a 80 minutos para a atualização das informações no painel. Este período é necessário para que os dados sejam processados e exibidos corretamente. Para mais informações sobre o tempo de espera, acesse  [Comparação de períodos](https://help.vtex.com/pt/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ?&utm_source=autocomplete#comparacao-de-periodos).
+
+### Verifique as permissões de acesso
+Para visualizar as informações no dashboard, certifique de que você possui um perfil de acesso que contenha o [recurso](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) Insights Metrics. Para mais informações sobre os perfis de acesso e como configurá-los, acesse o artigo [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/tutorials/pt/minimum-stock-control-for-integrations.md b/docs/tutorials/pt/minimum-stock-control-for-integrations.md
index 7ef6e3c38..e6a9166c6 100644
--- a/docs/tutorials/pt/minimum-stock-control-for-integrations.md
+++ b/docs/tutorials/pt/minimum-stock-control-for-integrations.md
@@ -40,7 +40,7 @@ Para configurar o estoque mínimo da sua integração, siga os passos abaixo:
 2. No menu Marketplace > Conexões, clique em **Integrações**.
 3. Selecione a opção **Configurações**.
 4. Escolha a integração que seja configurar.
-5. Ao escolher a integração, clique na engrenagem<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+5. Ao escolher a integração, clique na engrenagem<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 6. Selecione a opção **Editar Configurações**.
 7. No campo **Estoque mínimo**, digite o valor desejado.
 8. Clique em **Salvar**.
diff --git a/docs/tutorials/pt/mode-off-faq.md b/docs/tutorials/pt/mode-off-faq.md
index d81fac7d6..38295973d 100644
--- a/docs/tutorials/pt/mode-off-faq.md
+++ b/docs/tutorials/pt/mode-off-faq.md
@@ -1,10 +1,10 @@
 ---
 title: 'Mode-Off: FAQ'
 id: 6hbd7PuvoxuRbPCvTqjxeB
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-01-21T17:29:10.793Z
-updatedAt: 2021-04-06T20:20:55.582Z
-publishedAt: 2021-04-06T20:20:55.581Z
+updatedAt: 2024-04-11T19:26:47.407Z
+publishedAt: 2024-04-11T19:22:34.569Z
 firstPublishedAt: 2021-01-21T17:54:12.941Z
 contentType: tutorial
 productTeam: Financial
@@ -55,9 +55,10 @@ As transações serão liberadas normalmente quando o parceiro parar de apresent
 
 ## Por quanto tempo a VTEX faz a retentativa de processamento das transações represadas?
 
-O tempo de retry é definido por cada parceiro no momento da integração com o Payment Provider Protocol. 
+O tempo entre retentativas de processamento da transação (_retries_) pode ser definido pelo parceiro no momento do envio das informações de pagamento. Ao configurar o tempo para cancelamento do pagamento (campo `delayToCancel`) para um período menor que 1 dia, as retentativas serão realizadas a cada 1 hora. Se o tempo para cancelar o pagamento for definido como igual ou maior que 1 dia, as retentativas serão realizadas a cada 4 horas. Para mais informações, acesse [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol?endpoint=post-/payments).
 
-Caso esse período não tenha sido previamente definido, o tempo padrão é de __quatro horas__.
+<div class="alert alert-info">
+ Caso o pagamento seja realizado por <a href="https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf">PIX</a> ou o tempo para cancelamento do pagamento seja configurado entre 5 minutos e 1 hora, as chamadas de retry ocorrerão a cada 5 minutos.</div>
 
 ## Como identificar o mode-off e o que fazer quando ele estiver ligado?
 
diff --git a/docs/tutorials/pt/moskit-suiteshare.md b/docs/tutorials/pt/moskit-suiteshare.md
index 1e42db610..3d2f40f91 100644
--- a/docs/tutorials/pt/moskit-suiteshare.md
+++ b/docs/tutorials/pt/moskit-suiteshare.md
@@ -23,29 +23,29 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Moskit**.
 
-   ![HubSpot_Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
+   ![HubSpot_Suiteshare_1](//images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
 
 2. Acesse **Configurações > Integrações > Moskit > Integrar**.
 
-   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
 Selecione o [Formulário de captura](http://help.suiteshare.com/support/solutions/articles/67000192044-formul%C3%A1rio-de-captura) que irá integrar ao Moskit. 
 
-![Moskit_Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/7JgLdaJfPQDOVHvNe767sW/a4362f1e43b1cda42d00490f364deee5/Moskit_Suiteshare_1.png)
+![Moskit_Suiteshare_1](//images.ctfassets.net/alneenqid6w5/7JgLdaJfPQDOVHvNe767sW/a4362f1e43b1cda42d00490f364deee5/Moskit_Suiteshare_1.png)
 
 Para descobrir o seu ID, acesse dentro do Moskit: **Configurações > Usuários do sistema > Selecione o usuário desejado** e copie o número informado na URL.
 
-![Moskit_Suiteshare_2](https://images.ctfassets.net/alneenqid6w5/7H9cd7rbPyMUvFeQp0tQjq/8b863a0d3c950739c115b841040b8272/Moskit_Suiteshare_2.png)
+![Moskit_Suiteshare_2](//images.ctfassets.net/alneenqid6w5/7H9cd7rbPyMUvFeQp0tQjq/8b863a0d3c950739c115b841040b8272/Moskit_Suiteshare_2.png)
 
 Agora precisamos do token fornecido pela Moskit, no painel da Moskit clique em **Marketplace** e selecione a opção **API pública do Moskit CRM**, clique em **Ver mais**. 
 
 Clique em **Gerar nova key**.
 
-![Moskit_Suiteshare_3](https://images.ctfassets.net/alneenqid6w5/1S7dteXair1ffMZayzfbCE/96e40883c818c03ae778439390767696/Moskit_Suiteshare_3.png)
+![Moskit_Suiteshare_3](//images.ctfassets.net/alneenqid6w5/1S7dteXair1ffMZayzfbCE/96e40883c818c03ae778439390767696/Moskit_Suiteshare_3.png)
 
 Copie a Hash informada. 
 
-![Moskit_Suiteshare_4](https://images.ctfassets.net/alneenqid6w5/a07HZoQQxhOUULnleYwUN/3e1530d84adb5de0869324eb7c3790cb/Moskit_Suiteshare_4.png)
+![Moskit_Suiteshare_4](//images.ctfassets.net/alneenqid6w5/a07HZoQQxhOUULnleYwUN/3e1530d84adb5de0869324eb7c3790cb/Moskit_Suiteshare_4.png)
 
 Cole a informação dentro do painel do VTEX Assisted Sales (SuiteShare) no segundo campo. 
 
diff --git a/docs/tutorials/pt/moving-order-to-start-handling-shipping.md b/docs/tutorials/pt/moving-order-to-start-handling-shipping.md
index f628d0aa4..4fcf1d6b7 100644
--- a/docs/tutorials/pt/moving-order-to-start-handling-shipping.md
+++ b/docs/tutorials/pt/moving-order-to-start-handling-shipping.md
@@ -3,8 +3,8 @@ title: 'Passar pedido para o status Preparando Entrega'
 id: tutorials_198
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:17.090Z
-updatedAt: 2023-03-31T14:47:04.890Z
-publishedAt: 2023-03-31T14:47:04.890Z
+updatedAt: 2023-06-15T13:32:59.728Z
+publishedAt: 2023-06-15T13:32:59.728Z
 firstPublishedAt: 2017-04-27T23:02:47.756Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,9 +21,11 @@ A baixa na reserva não ocorre automaticamente, isso deve ser controlado pelo se
 
 Veja a seguir as maneiras possíveis de atualização desse status.
 
-## Por integração
+## Por integração e API
 
-As integrações automatizam esse processo. Elas acontecem quando outros sistemas consultam os pedidos da VTEX para seguir com o fluxo de expedição. Essa integração pode ser feita via API REST, conforme nosso [guia de integração de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing).
+As integrações automatizam esse processo. Elas acontecem quando outros sistemas consultam os pedidos da VTEX para seguir com o fluxo de expedição. Essa integração pode ser feita via API REST, conforme nosso [guia de integração de ERPs](https://developers.vtex.com/docs/erp-integration-set-up-order-processing). 
+
+Feito isso, você poderá usar a API [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
 
 ## Pelo Admin VTEX
 
diff --git a/docs/tutorials/pt/multilevel-omnichannel-inventory.md b/docs/tutorials/pt/multilevel-omnichannel-inventory.md
index 14b680a67..3235432b7 100644
--- a/docs/tutorials/pt/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/pt/multilevel-omnichannel-inventory.md
@@ -3,19 +3,19 @@ title: 'Multilevel Omnichannel Inventory'
 id: 7M1xyCZWUyCB7PcjNtOyw4
 status: PUBLISHED
 createdAt: 2020-11-30T19:44:58.255Z
-updatedAt: 2023-04-19T00:59:40.265Z
-publishedAt: 2023-04-19T00:59:40.265Z
+updatedAt: 2024-07-24T14:21:41.092Z
+publishedAt: 2024-07-24T14:21:41.092Z
 firstPublishedAt: 2020-12-08T19:12:43.325Z
 contentType: tutorial
-productTeam: Shopping
-author: 127RQ7SUoFfyTh5gbXUpdM
+productTeam: Channels
+author: 0QBQws7rk0t5Mnu8fgfUv
 slug: multilevel-omnichannel-inventory
 locale: pt
 legacySlug: marketplace-recursivo-v2
-subcategory: 6riYYNZCpO8wyksi8Ksgyq
+subcategory: 5RAUzLD6X9Wa1maenj1eGA
 ---
 
-_Multilevel Omnichannel Inventory_ (anteriormente chamada de Marketplace Recursivo) é a configuração na VTEX que permite uma conta principal disponibilizar o estoque de [sellers white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) e [contas-franquia](https://help.vtex.com/pt/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) para a venda em marketplaces. O artigo a seguir inclui as seguintes informações sobre a funcionalidade:
+__Multilevel Omnichannel Inventory__ é a configuração na VTEX que permite uma conta principal disponibilizar o estoque de [sellers white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) e [contas franquia](https://help.vtex.com/pt/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) para a venda em marketplaces. O artigo a seguir inclui as seguintes informações sobre a funcionalidade:
 
 * [Arquitetura de contas](#arquitetura-de-contas)
 * [Benefícios](#beneficios)
@@ -28,25 +28,23 @@ Para saber mais sobre a arquitetura dos pedidos do tipo Multilevel Omnichannel I
 
 ## Arquitetura de contas
 
-O [marketplace](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) é o ambiente onde o produto é vendido, também chamado de vitrine, e o [seller](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#sendo-seller-vtex) é o dono do estoque e o responsável pelo envio do pedido. 
+O [marketplace](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) é o ambiente onde o produto é vendido, também chamado de vitrine, e o [seller](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#sendo-seller-vtex) é o dono do inventário e o responsável pelo envio do produto. 
 
-Quando uma loja vende seus produtos em um marketplace, temos uma relação entre seller e marketplace de um nível só. Porém a arquitetura da VTEX permite que lojas atuem tanto como marketplaces quanto como sellers, expandindo o número de combinações possíveis. 
+Quando uma loja vende seus produtos em um marketplace, temos uma relação entre seller e marketplace de dois níveis. Porém a arquitetura da VTEX permite que lojas atuem tanto como marketplaces quanto como sellers, expandindo o número de combinações possíveis. 
 
-É possível que um seller de uma conta principal atue como marketplace de [sellers white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa). Esse é o caso de redes de lojas configuradas como [contas-franquia](https://help.vtex.com/pt/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa?&utm_source=help) e lojas físicas, que são por definição sellers em outra loja VTEX. 
+É possível que um seller de uma conta principal atue como marketplace de [sellers white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa). Esse é o caso de redes de lojas configuradas como [contas franquia](https://help.vtex.com/pt/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa?&utm_source=help) e lojas físicas, sendo por definição sellers em outra loja VTEX. 
 
 Também é possível que esse seller principal venda seus produtos em um marketplace.
 
 Quando isso ocorre, temos uma arquitetura de três níveis entre marketplace, seller principal,  e seus sellers white label, como ilustra a imagem abaixo.
 
-![Arquitetura Multilevel omichannel inventory](https://images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/b70689c18e55ad472f71176a283b9c17/Screen_Shot_2022-09-30_at_18.57.26.png)
+![Arquitetura Multilevel omichannel inventory](//images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/b70689c18e55ad472f71176a283b9c17/Screen_Shot_2022-09-30_at_18.57.26.png)
 
-Por padrão, os produtos das lojas físicas, ou sellers white label (nível 3, na imagem), não ficam disponíveis para serem vendidos pelo marketplace do nível 1. Mas é possível torná-los disponíveis com a funcionalidade Multilevel Omnichannel Inventory.
-
-> **Multilevel Omnichannel Inventory** é a configuração na VTEX que permite disponibilizar o estoque de sellers white label e contas-franquia para a venda nos marketplaces em que a conta principal do seller direto está conectada.
+Por padrão, os produtos das lojas físicas, ou sellers white label (nível 3, na imagem), não ficam disponíveis para serem vendidos pelo marketplace do nível 1. Mas é possível torná-los disponíveis com a funcionalidade **Multilevel Omnichannel Inventory.**
 
 Desta maneira, é possível que um marketplace venda os produtos dos seus sellers diretos e também das lojas físicas e sellers white label vinculados àqueles sellers. 
 
-Isso significa que, quando o seller com a conta principal configurar uma integração com um marketplace, as contas-franquias estarão automaticamente integradas a ele também, não sendo preciso gerenciar cada franquia individualmente para configurar sua integração ao marketplace.
+Isso significa que, quando o seller com a conta principal configurar uma integração com um marketplace, as contas franquia estarão automaticamente integradas a ele também, não sendo preciso gerenciar cada franquia individualmente para configurar sua integração ao marketplace.
 
 <div class="alert alert-info">
 Atualmente, só é permitido um nível de recursividade. Ou seja, o marketplace pode vender produtos dos sellers white label integrados a um seller direto.
@@ -70,16 +68,12 @@ Para saber mais detalhes sobre a arquitetura de pedidos aplicada em Multilevel O
 Algumas das funcionalidades que fazem parte do modelo tradicional de marketplace não estão disponíveis para um cenário _Multilevel Omnichannel Inventory_. É importante conhecer essas restrições antes de habilitar a configuração.
 
 <div class="alert alert-warning">
-Note que no Brasil, o Banco Central (BACEN) regulamenta a atuação de marketplaces varejistas como concentradores e repassadores de dinheiro. Dado essa restrição, recomendamos a implementação do Multilevel Omnichannel Marketplace em lojas que se adequam à circular 3.815 do BACEN. Saiba mais em <a href="https://vtex.com/pt-br/blog/estrategia/bacen-e-a-regulamentacao-para-marketplaces-no-brasil/"> BACEN e a regulamentação para marketplaces no Brasil - VTEX</a>.
-  </div>
-
-### Marketplaces externos
+Note que, no Brasil, o Banco Central (BACEN) regulamenta a atuação de marketplaces varejistas como concentradores e repassadores de dinheiro. Dado essa restrição, recomendamos a implementação do Multilevel Omnichannel Marketplace em lojas que se adequam à circular 3.815 do BACEN. Saiba mais em <a href="https://vtex.com/pt-br/blog/estrategia/bacen-e-a-regulamentacao-para-marketplaces-no-brasil/"> BACEN e a regulamentação para marketplaces no Brasil - VTEX</a>.
+ </div>
 
-Essa funcionalidade pode ser configurada para [marketplaces VTEX](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-um-marketplace-vtex), [conectores nativos](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrado-a-conector-nativo-vtex) e [parceiros certificados](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrado-a-conector-certificado-parceiro). Além disso, [B2W](https://help.vtex.com/pt/tracks/configurar-integracao-da-b2w--6w07SJBVqE020KIOOS8ygk), [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) e [Magazine Luiza](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y) já possibilitam a integração de estoque de lojas físicas.
+### Disponibilidade
 
-Apesar de suportarem a funcionalidade, ela não está disponível automaticamente para esses marketplaces, sendo necessário fazer a configuração para cada um. Isso se aplica em marketplaces integrados pela primeira vez, e naqueles que já utilizavam a API de fulfillment - que se restringe a dois níveis. Saiba mais em [Como configurar](#como-configurar) e em nosso [artigo no Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
-
-O Multilevel Omnichannel Inventory pode causar erros de integração quando aplicado a marketplaces externos à VTEX. Nesses cenários, o ID do pedido sofrerá alteração, por exemplo. Aconselhamos que cheque com sua equipe de desenvolvimento para ter certeza que a transição não terá problemas. Saiba mais em nosso [artigo no Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
+Essa funcionalidade _Multilevel Omnichannel Inventory_ está disponível apenas para [marketplaces VTEX](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-um-marketplace-vtex). Para usar a funcionalidade, o marketplace (nível 1) deve realizar a configuração para cada seller direto (nível 2) que desejar. Você pode fazer isso ao cadastrar novos sellers ou editando a configuração de sellers existentes na sua loja. Saiba mais em [Como configurar](#como-configurar) e em nosso [artigo no Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
 
 ### Distribuição de recebíveis
 
@@ -89,34 +83,37 @@ Não é possível distribuir recebíveis em toda a cadeia (marketplace, seller d
 
 Nesses casos, o seller direto se torna um recebedor dos itens de seus sellers white label e dos seus próprios itens, retirando as comissões configuradas na relação com o marketplace.
 
-A solução pode ser suficiente em casos em que o seller direto faz parte do mesmo grupo econômico que seus sellers white label, tornando possível concentrar todos os recebíveis em uma única conta bancária.
+A solução pode ser suficiente em casos em que o seller direto faz parte do mesmo grupo econômico que seus sellers white label, possibilitando concentrar todos os recebíveis em uma única conta bancária.
 
 É importante ressaltar que quando o _seller direto_ não é responsável pelos recebíveis dos sellers white label, a solução de split de recebíveis será limitada por não permitir a distribuição até os sellers white label.
 
 ### Meios de pagamento
 
-Uma vez que a configuração é feita, somente os meios de pagamento do marketplace aparecerão como opção no checkout. Os meios de pagamento dos sellers diretos (nível 2) e sellers white label (nível 3) não são importados na arquitetura de contas. Portanto, o checkout só mostra os meios de pagamento do marketplace, mesmo que o afiliado do seller direto esteja configurado para usar os meios de pagamento dele. O [afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187) da conta franquia sempre deve estar com a flag de usar os meios de pagamento desmarcada.
+Uma vez que a configuração é feita, somente os meios de pagamento do marketplace aparecerão como opção no checkout. Os meios de pagamento dos sellers diretos (nível 2) e sellers white label (nível 3) não são importados na arquitetura de contas. Portanto, o checkout só mostra os meios de pagamento do marketplace, mesmo que o afiliado do seller direto esteja configurado para usar os meios de pagamento dele.
 
-### Alteração de Seller
+<div class="alert alert-warning">
+  O <a href="https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187">afiliado</a> da conta franquia sempre deve estar com a configuração de usar os meios de pagamento desativada.
+</div>
+
+### Alteração de seller
 
 Caso um seller white Label (nível 3) receba um pedido e o rejeite, este pedido não será atribuído a outro seller white label. Consequentemente um novo pedido deverá ser criado pelo comprador, no storefront do marketplace. Saiba mais em [Change Seller](https://help.vtex.com/pt/tutorial/veja-como-utilizar-o-change-seller--5TBAwO2kOAMw44uyaaQMQO#limitacoes).
 
 ### Alteração de pedidos finalizados pela loja
 
-Uma loja VTEX não consegue alterar pedidos finalizados em um marketplace VTEX num cenário de Multilevel Omnichannel Inventory. Será necessário cancelar o pedido e criar um novo.
-
-No entanto, é possível alterar pedidos de lojas VTEX feitos em marketplaces externos. Saiba mais em [Change chain orders in external marketplaces](https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces).
+Uma loja VTEX não consegue alterar pedidos finalizados em um marketplace VTEX num cenário de _Multilevel Omnichannel Inventory._ Será necessário cancelar o pedido e criar um novo. Saiba mais em [Change chain orders in external marketplaces](https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces).
 
 ### Alteração de pedidos finalizados pelo cliente
 
-O cliente não consegue alterar pedidos na seção de _Meus Pedidos, _do storefront do marketplace. Qualquer alteração nos pedidos deverá ser realizada por meio do serviço de atendimento aos clientes ou via API.
+O cliente não consegue alterar pedidos na seção de _Meus Pedidos,_ do storefront do marketplace. Qualquer alteração nos pedidos deverá ser realizada por meio do Serviço de Atendimento ao Cliente ou via API.
 
 ### Manual Price
 
 A feature de Manual Price não se aplica ao Multilevel Omnichannel Inventory. Não é possível, portanto,  alterar preços manualmente no carrinho. É necessário atualizar o preço via:  
-- [Integração com o ERP](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) 
-- [Pricing API REST](https://developers.vtex.com/vtex-rest-api/reference/createupdatepriceorfixedprice) 
-- [Página de preços no Admin VTEX](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)
+
+- [Integração com o ERP](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide)  
+- [Pricing API REST](https://developers.vtex.com/vtex-rest-api/reference/createupdatepriceorfixedprice)  
+- [Página de preços no Admin VTEX](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)  
 
 ### Informação de usuário
 
@@ -128,7 +125,7 @@ Um marketplace não pode configurar exibição de preços e disponibilidade de p
 
 ### UTMs, cupons e gift cards
 
-A aplicação de [cupons](https://help.vtex.com/pt/tutorial/cupons-beta--1aAEN3ADpz19ss5JCIEBdL), [gift cards (vale-compras)](https://help.vtex.com/pt/tutorial/gift-card--tutorials_995) e benefícios vinculados a [UTMs](https://help.vtex.com/pt/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) estão restritos ao marketplace nível 1. Aqueles configurados no seller direto (nível 2) e contas-franquia ou seller white label (nível 3) não serão aplicados.
+A aplicação de [cupons](https://help.vtex.com/pt/tutorial/cupons-beta--1aAEN3ADpz19ss5JCIEBdL), [gift cards (vale-compras)](https://help.vtex.com/pt/tutorial/gift-card--tutorials_995) e benefícios vinculados a [UTMs](https://help.vtex.com/pt/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) estão restritos ao marketplace nível 1. Aqueles configurados no seller direto (nível 2) e contas franquia ou seller white label (nível 3) não serão aplicados.
 
 ### Pedidos integrados assincronamente com divergência de valores
 
@@ -140,7 +137,7 @@ Não é possível criar tabelas de preço por meio da funcionalidade [Price Tabl
 
 ## Como configurar
 
-A configuração da funcionalidade _Multilevel Omnichannel Inventory _deve ser feita pelo marketplace em seu Admin VTEX ou via [API Rest](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). Essa configuração pode ser feita tanto em sellers já integrados, quanto em sellers adicionados pela primeira vez. 
+A configuração da funcionalidade **Multilevel Omnichannel Inventory** deve ser feita pelo marketplace em seu Admin VTEX ou via [API Rest](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). Essa configuração pode ser feita tanto em sellers já integrados, quanto em sellers adicionados pela primeira vez. 
 
 <div class="alert alert-info">
 Note que a configuração deve ser feita para cada seller direto (nível 2) em que se deseja aplicar a funcionalidade, mas não em cada seller white label ou conta franquia (nível 3).
@@ -148,18 +145,17 @@ Note que a configuração deve ser feita para cada seller direto (nível 2) em q
 
 ### Sellers já integrados
 
-Para configurá-la em sellers que já foram integrados anteriormente, o marketplace deve seguir os passos abaixo:
+Para configurá-la em sellers que já foram integrados anteriormente, o marketplace deve seguir os passos abaixo:  
 
-  1. Na seção _Marketplace _de seu Admin VTEX, acesse a aba **Sellers**. 
-  2. Clique em **Gerenciamento de Sellers.**  
-  3. Na linha correspondente ao seller cujos sellers white label você deseja acessar, clique em `Alterar/Visualizar`.   
-  4. Preencha o campo **Fulfillment EndPoint** seguindo o exemplo:    
-`https://{{sellerAccount}}.vtexcommercestable.com.br/api/checkout?affiliateid={{affiliateId}}&sc={{tradePolicyId}}`  
-  5. Substitua os campos que estão entre chaves pelos valores descritos abaixo, removendo as chaves:   
+1. Na seção Marketplace de seu Admin VTEX, acesse a aba **Gerenciamento.**
+2. Na linha correspondente ao seller cujos sellers white label você deseja acessar, clique em <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Clique em  **Detalhes do seller.**
+4. Preencha o campo **Fulfillment EndPoint** seguindo o exemplo:  https://{{sellerAccount}}.vtexcommercestable.com.br/api/checkout?affiliateid={{affiliateId}}&sc={{tradePolicyId}}
+5. Substitua os campos que estão entre chaves pelos valores descritos abaixo, removendo as chaves:  
     - **sellerAccount**: [account name](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC) do seller na VTEX.   
     - **affiliateId**: código de três dígitos correspondente ao [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) criado pelo seller. O seller deve informar esse valor ao marketplace.   
     - **tradePolicyId**: ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) criada pelo seller em seu próprio ambiente VTEX, para vender em seu marketplace. O seller deve informar esse valor ao marketplace.  
-  6. Clique em `Salvar`.  
+  6. Clique em **Salvar.**   
 
 ### Sellers integrados pela primeira vez
 
diff --git a/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md b/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md
new file mode 100644
index 000000000..3d8bac096
--- /dev/null
+++ b/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md
@@ -0,0 +1,61 @@
+---
+title: 'Meu anúncio não é exibido no Mercado Livre'
+id: 2UpudfowEvG97e2lstj4qc
+status: PUBLISHED
+createdAt: 2024-06-13T16:38:00.931Z
+updatedAt: 2024-06-13T18:11:28.836Z
+publishedAt: 2024-06-13T18:11:28.836Z
+firstPublishedAt: 2024-06-13T18:01:04.982Z
+contentType: tutorial
+productTeam: Channels
+author: YRJ73j8mt38D5TUleocQB
+slug: meu-anuncio-nao-e-exibido-no-mercado-livre
+locale: pt
+legacySlug: meu-anuncio-nao-e-exibido-no-mercado-livre
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras-chave:__ *marketplace, catálogo, integração, Mercado Livre, anúncio pausado.* 
+
+Quando um produto é removido ou desativado da política comercial utilizada na integração do Mercado Livre, a atualização dessa informação é enviada automaticamente para o marketplace, que, por sua vez, para de exibir o anúncio do produto.
+
+Outra possibilidade é quando um produto atinge o [estoque mínimo](https://help.vtex.com/pt/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D) estabelecido na configuração da integração com o marketplace. Se o estoque de um produto estiver abaixo do valor atribuído, o anúncio será pausado para evitar vendas de produtos sem estoque.
+
+## Solução
+
+Para resolver esse problema, existem duas soluções que você pode considerar: [verificar a política comercial do produto](#verificando-a-politica-comercial) e a [configuração de estoque limite](#verificando-o-estoque-limite) para pausa de anúncio.
+
+### Verificando a política comercial
+
+É por meio da [política comercial](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/15NZiQstCET8zyQUIa7nhw) que são definidas as configurações aplicadas aos produtos enviados para o Mercado Livre. 
+
+Para validar se a política comercial está configurada corretamente no cadastro do produto, acesse __Catálogo > Todos os Produtos__ no Admin VTEX ou digite __Todos os Produtos__ na barra de busca no topo da página, e siga as instruções abaixo:
+
+1. Clique em __Buscar ou filtrar resultados__ e [busque pelo produto](https://help.vtex.com/pt/tutorial/produtos-e-skus-beta--2ig7TmROlirWirZjFWZ3By#buscar-produtos) cujo anúncio não está disponível no Mercado Livre.
+2. Na linha do produto desejado, clique em `Editar`.
+3. Na página de cadastro do produto, valide se a política comercial que atende o Mercado Livre está selecionada.
+4. Caso não esteja, marque a flag da política comercial.
+
+  ![politicas-comerciais-pt](//images.ctfassets.net/alneenqid6w5/dRDUjjHbk3Ui0ZQEX7SYd/973f3dd4441c0b4646d0139380d13666/politicas-comerciais-pt.png)
+
+ 5. Clique no botão `Salvar`.
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Se sua loja está operando com o <a href="https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">Novo Admin VTEX</a>, consulte o artigo <a href="https://help.vtex.com/pt/tutorial/produtos-e-skus-beta--2ig7TmROlirWirZjFWZ3By">Produtos e SKUs</a> para aprender como visualizar e gerenciar seu catálogo, incluindo a configuração de políticas comerciais.
+</div>
+
+### Verificando o estoque limite
+
+Para validar a configuração do estoque limite, acesse Marketplace > Conexões > Marketplaces e Integrações no Admin VTEX ou digite Marketplaces e integrações na barra de busca no topo da página, e siga as instruções abaixo:
+
+1. [Busque pelo card de integração](https://help.vtex.com/pt/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V#buscar-e-filtrar) do Mercado Livre.
+2. Na linha do card de integração desejado, clique em `Editar`.
+3. Em `Configurações`, verifique se há algum valor atribuído ao campo Estoque limite para pausa de anúncio.
+
+  ![estoque-limite-pt](//images.ctfassets.net/alneenqid6w5/wy7Bz5Dcm2pt24HNVHYdZ/4cf81a0315f7dbb465e1dd9a737d6ec9/estoque-limite-pt.png)
+
+ 4. Certifique-se de que a configuração deste campo está correta, de acordo com o artigo [Controle de estoque mínimo para integrações](https://help.vtex.com/pt/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D). 
+
+<div style="background-color:#DBEAFE; border-left: 2px solid ##1E3A8A; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
+Caso seu problema não seja resolvido por uma das soluções propostas, abra um ticket para o <a href="https://help.vtex.com/support?/cultureInfo=pt-br">suporte VTEX</a>.
+</div>
diff --git a/docs/tutorials/pt/my-inventory-is-negative.md b/docs/tutorials/pt/my-inventory-is-negative.md
new file mode 100644
index 000000000..1d360e9f5
--- /dev/null
+++ b/docs/tutorials/pt/my-inventory-is-negative.md
@@ -0,0 +1,34 @@
+---
+title: 'Meu estoque está negativo'
+id: JSFHaWsASXbnrX9dgNEeP
+status: PUBLISHED
+createdAt: 2024-06-10T11:08:39.990Z
+updatedAt: 2024-06-10T17:21:47.755Z
+publishedAt: 2024-06-10T17:21:47.755Z
+firstPublishedAt: 2024-06-10T17:21:47.755Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: meu-estoque-esta-negativo
+locale: pt
+legacySlug: meu-estoque-esta-negativo
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags/Palavras-chave:** *estoque, reserva, política comercial, admin VTEX, gerenciamento de inventário.*
+
+Quando a quantidade disponível de um produto é exibida como negativa, pode ser uma indicação de que há mais itens [reservados](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92) do que a quantidade total inserida em estoque. Este problema geralmente ocorre ao registrar (dar baixa) em um item de pedido que ainda está reservado pelo sistema.
+
+## Solução
+
+A informação de estoque do item deve ser atualizada de acordo com a quantidade de itens físicos disponíveis no estoque. Dessa maneira, o valor registrado dos itens em estoque deve ser a soma dos itens disponíveis mais os itens que estão reservados e que ainda não estão no status de **Preparando Entrega**.
+
+Para atualizar a quantidade correta em estoque, realize os seguintes passos abaixo:
+
+1. No Admin VTEX, acesse **Catálogo > Inventário > Gerenciamento de inventário** ou digite **Gerenciamento de inventário** na barra de busca no topo da página.
+2. Clique em **Gerenciamento de inventário**.
+3. Busque pelo SKU desejado.
+4. Na coluna **Atualizar contagem**, insira a quantidade correta de itens físicos no estoque, considerando a soma dos itens disponíveis mais os itens reservados.
+5. Clique em **Salvar**.
+
+Quando dois ou mais estoques utilizam a mesma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) e há uma quantidade negativa de unidades em um desses estoques, o SKU será indisponibilizado para venda, mesmo que exista uma quantidade disponível em um dos estoques no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
diff --git a/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md b/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md
new file mode 100644
index 000000000..4a24a7b30
--- /dev/null
+++ b/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md
@@ -0,0 +1,63 @@
+---
+title: 'Meus pedidos do Mercado Livre apresentam erros'
+id: 170njWgSw9UQ5DG6NRl14d
+status: PUBLISHED
+createdAt: 2024-06-28T15:03:26.959Z
+updatedAt: 2024-06-28T16:08:10.242Z
+publishedAt: 2024-06-28T16:08:10.242Z
+firstPublishedAt: 2024-06-28T16:04:14.266Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: meus-pedidos-do-mercado-livre-apresentam-erros
+locale: pt
+legacySlug: meus-pedidos-do-mercado-livre-apresentam-erros
+subcategory: 2LcLWCYaEm5qPmOuYUiKIS
+---
+
+**Tags:** marketplace, catálogo, produtos  
+**Palavras-chave:** integração, Mercado Livre, envio de produtos, pedidos  
+
+Quando ocorre um erro de integração em pedidos entre um marketplace e o Mercado Livre, uma mensagem de erro é informada em cada pedido.   
+
+Os pedidos apresentam erros de integração por **ID de Loja Oficial no Mercado Livre** cadastrado incorretamente ou por **Categorias inexistentes no Mercado Livre**. Para verificar se um pedido contém erros de integração, no Admin VTEX, acesse**Marketplace > Conexões > Pedidos ou digite Pedidos na barra de busca.**  
+
+## Solução
+
+Para corrigir erros de integração em pedidos do Mercado Livre, considere as seguintes opções: [verificar o ID da loja oficial no Mercado Livre](#verificando-o-id-da-loja-oficial-no-mercado-livre) e [verificar correspondência de categorias](#verificando-correspondencia-de-categorias) para erros de integração de pedidos.  
+
+### Verificando o ID da loja oficial no Mercado Livre 
+
+Caso sua loja tenha o status de [Loja Oficial](https://www.mercadolivre.com.br/lojas-oficiais/catalogo) no Mercado Livre, é necessário informar no [cadastro do conector](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/4YvYdgICMosaEgISOYogsi) o ID fornecido pelo Mercado Livre.  
+
+Para validar se foi inserido o ID correto, acesse **Marketplace > Conexões > Marketplaces e Integrações**  e siga os passos abaixo:  
+
+1. Busque pelo conector **Mercado Livre.**  
+2. Clique em `Editar`.  
+3. Verifique o ID cadastrado no campo `ID da Loja Oficial no Mercado Livre`.  
+4. Caso o campo esteja vazio ou com o ID incorreto, insira a informação correta.  
+5. Clique em `Salvar`.  
+
+### Verificando correspondências de categorias  
+
+Ao realizar o [mapeamento de categorias e atributos](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA) para o Mercado Livre, é necessário que os atributos de cada categoria cadastradas na VTEX correspondam aos atributos das categorias existentes no Mercado Livre.   
+Se algum dos atributos for preenchido incorretamente, a integração retornará um erro no seguinte formato:  
+`A categoria selecionada no atributo category_meli não existe no Mercado Livre.`
+
+Para verificar as categorias e atributos enviados, acesse **Marketplace > Conexões > Marketplaces e Integrações**  e siga os passos abaixo:  
+
+1. Busque pelo conector **Mercado Livre.**  
+2. Clique em `Editar`.  
+3. Clique em `Realizar mapeamento`.  
+4. Clique na categoria que apresenta o erro.  
+5. Realize novamente o mapeamento conforme as categorias e atributos existentes no Mercado Livre.  
+
+<div class="alert alert-info">
+Para identificar o atributo indicado na mensagem de erro, consulte o número inicial dos códigos determinados pelo Mercado Livre.<p> Clique no nome do seu país para fazer o download da planilha de referência:</p>
+<p><ul>
+<p><a href="https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip">Brasil</a></p>
+<p><a href="https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar">Argentina</a></p> 
+<p><a href="https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar">Colômbia</a></p> 
+<p><a href="https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar">México</a></p>
+</ul></p>
+</div>
diff --git a/docs/tutorials/pt/my-store-order-was-not-created.md b/docs/tutorials/pt/my-store-order-was-not-created.md
new file mode 100644
index 000000000..a5c44ef76
--- /dev/null
+++ b/docs/tutorials/pt/my-store-order-was-not-created.md
@@ -0,0 +1,64 @@
+---
+title: 'O pedido da minha loja não foi criado'
+id: 7xQZqkMHXkHCEEZl5UlX8I
+status: PUBLISHED
+createdAt: 2024-07-18T20:10:20.933Z
+updatedAt: 2024-07-18T20:56:20.706Z
+publishedAt: 2024-07-18T20:56:20.706Z
+firstPublishedAt: 2024-07-18T20:56:20.706Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: o-pedido-da-minha-loja-nao-foi-criado
+locale: pt
+legacySlug: o-pedido-da-minha-loja-nao-foi-criado
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags / Palavras-chave:** pedido, integração de pedidos, integração XML, configuração do produto, estoque negativo, sem estoque.
+
+Quando um cliente tenta realizar uma compra e ocorre um erro na criação do pedido, isso pode acontecer por diferentes razões, como problemas de pagamento, de logística ou de [integração do backend](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) com ERPs (Enterprise Resource Planning). 
+
+Antes de considerar motivos complexos para erros com pedidos não criados, aplique os processos de resolução de problemas (troubleshooting) apresentados neste artigo. Alguns dos cenários de erro mais comuns são:
+
+* O item não tinha [estoque](https://help.vtex.com/pt/tutorial/inventory-management--tutorials_139) disponível e a loja não estava configurada para vender produtos sem estoque. 
+* A integração XML não foi configurada para enviar informações sobre produtos sem estoque.
+
+## Soluções
+
+Considere os seguintes processos de resolução de problemas para erros na criação de pedidos:
+
+* [Gerenciar inventário](#gerenciar-inventario): se o produto não constar no inventário e a loja não estiver configurada para vender produtos sem estoque.
+* [Revisar integração XML](#revisar-integracao-xml): se a sua integração XML não estiver configurada para enviar informações sobre produtos sem estoque. 
+
+### Gerenciar inventário
+
+Há duas formas de gerenciar seu inventário:
+
+* **Via API:** utilizando o endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
+* **Via Admin VTEX:** acessando _Catálogo > Inventário > Gerenciamento de inventário_.
+
+As soluções abaixo são voltadas para o gerenciamento de inventário via Admin VTEX:
+
+* **Atualizar a contagem do inventário:** na linha correspondente ao SKU e estoque desejados, digite o número de itens disponíveis para venda na coluna Atualizar contagem e clique em `Salvar`. Este número não pode ser negativo, caso contrário o [estoque será negativo](https://help.vtex.com/pt/faq/why-is-my-stock-negative--frequentlyAskedQuestions_159).
+* **Configurar o estoque infinito:** na linha correspondente ao SKU e estoque desejados, na coluna Estoque infinito, clique no botão de ativação e depois em `Salvar`. Quando essa configuração é ativada, o item passa a ser considerado sempre disponível para vendas e a loja nunca fica sem estoque dele.
+
+<div class = "alert alert-info">
+Para configurar os produtos sem estoque a serem exibidos no seu storefront, acesse <b>Catálogo > Todos os produtos</b> no Admin VTEX e, na página de configuração do produto, na aba <b>Produto</b>, marque a opção <b>Sim</b> no campo <i>Mostrar produto esgotado</i>.
+</div>
+
+### Revisar integração XML
+
+O XML é uma linguagem de marcação que define e armazena dados de forma partilhável. Se a [integração XML da sua loja](https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242) não estiver definida para determinadas configurações, pode ser que não seja possível exportar as informações do produto. 
+
+Quando o produto não tem estoque e a integração não está configurada para enviar produtos sem estoque, pode ocorrer um erro com a falta de informações do produto. Para ativar a configuração, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Configurações da loja > Canais > Integração XML** ou digite **Integração XML** na barra de busca na parte superior da página.
+2. Na linha da integração XML desejada, clique em `Editar`.
+3. Na aba `Editar XML`, na opção **Exibir SKUs indisponíveis**, marque a caixa de seleção `Exibir SKUs fora de estoque (esgotados) entre os resultados`.
+4. Clique em `Salvar`. 
+
+<div class="alert alert-warning">
+Podem ocorrer erros ao tentar faturar um pedido com informações XML incorretas ou faltantes.
+</div>
+
diff --git a/docs/tutorials/pt/names-of-vtex-branches-worldwide.md b/docs/tutorials/pt/names-of-vtex-branches-worldwide.md
index 2dcf4c94b..3ac18758f 100644
--- a/docs/tutorials/pt/names-of-vtex-branches-worldwide.md
+++ b/docs/tutorials/pt/names-of-vtex-branches-worldwide.md
@@ -29,4 +29,4 @@ A VTEX se orgulha de possuir escritórios em países diferentes e vários client
 
 Para saber em qual país você é faturado, você pode consultar seu contrato ou [fazer download da sua fatura](https://help.vtex.com/pt/tutorial/como-fazer-download-faturas-da-VTEX--tutorials_653). Ao abrir a fatura, você encontrará no canto esquerdo da sua fatura, abaixo do logo da VTEX, o nome e endereço da companhia na qual sua loja está sendo faturada.
 
-![reconhecimento fatura](https://images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
+![reconhecimento fatura](//images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
diff --git a/docs/tutorials/pt/navigation.md b/docs/tutorials/pt/navigation.md
new file mode 100644
index 000000000..b4970649b
--- /dev/null
+++ b/docs/tutorials/pt/navigation.md
@@ -0,0 +1,208 @@
+---
+title: 'Navegação Data Pipeline (Beta)'
+id: 4X4hK0zdIHN0Xn5x2MLYYd
+status: PUBLISHED
+createdAt: 2024-02-02T17:48:16.639Z
+updatedAt: 2024-06-21T16:24:13.980Z
+publishedAt: 2024-06-21T16:24:13.980Z
+firstPublishedAt: 2024-05-27T19:26:59.542Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: navegacao-data-pipeline-beta
+locale: pt
+legacySlug: navegacao-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+O conjunto de dados de navegação opera com duas tabelas principais: `pageviews` e `sessions`. Uma `pageview` refere-se a cada nova página acessada pelo usuário durante a navegação na loja, enquanto uma `session` é definida como o conjunto de todos os `pageviews` realizados por um usuário em uma única visita.  
+Cada `session` permanece ativa até que não ocorra uma nova `pageview` por um período de 30 minutos.  
+
+<div class="alert alert-warning">
+O conjunto de dados de navegação não captura todos os tipos de eventos que ocorrem durante a navegação.</br>
+Ex: cliques específicos, eventos especiais e interações com o mini carrinho.</br></div>
+
+- [Características dos dados de navegação](#caracteristicas-dos-dados-de-navegacao)
+- [Tabela sessions](#tabela_sessions)
+- [Tabela pageviews](#tabela_pageviews)
+- [Análise com dados de navegação](#analises-com-dados-de-navegacao)
+- [Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados de navegação
+
+| **Característica** | **Descrição** |
+|:---:|:---:|
+| Origem do dado | O conjunto de dados se origina via <i>script</i> executado no <i>frontend</i> da loja, é ele quem registra as informações das sessões e atividades dos usuários. |
+| Disponibilidade | Os dados de navegação podem ser acessados no <a href="https://help.vtex.com/pt/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ#dados">dashboard Visão Geral</a> no Admin da VTEX, concentrando-se no total de sessões e no funil de conversão, ou por meio de ferramentas terceiras, como Google Analytics. |
+| Histórico | Os dados são mantidos por dois anos, a partir de 2022 para clientes que já utilizam a plataforma VTEX. |
+| Menor intervalo de atualização possível | Uma hora. |  
+
+<div class="alert alert-warning">
+  O <i>script</i> em um site não é capaz de capturar dados de sessões que se originam em marketplaces, aplicativos ou implementações <i>headless</i>, nas quais não gerenciamos o <i>frontend</i>. Além disso, personalizações realizadas no <i>frontend</i> da loja podem interferir ou mesmo inativar o <i>script</i> levando à falta de registro de algumas sessões, ou taxa de conversão observada no dashboard.</br>
+Para minimizar o impacto no desempenho da loja, o <i>script</i> é configurado para ser o último elemento a carregar na página, o que significa que sessões muito breves podem não ser capturadas.</br>
+</div>
+
+## Tabela sessions
+
+Esta tabela contém apenas sessões fechadas, seja por inatividade ou porque terminaram em uma compra. E é ordenada por `session_id`, `session_end_time` e `store_name`; portanto, evite filtrar grandes intervalos de dados por colunas que não estão nesta estratégia de ordenação. Veja os campos que compõem a tabela.  
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| batch_id | character varying(13) | ID de controle da ingestão de dados. |
+| session_id | character varying(127) | UUID único identificando esta sessão, correspondente ao cookie VtexRCSessionIdv7. |
+| store_name | character varying(127) | Nome da loja que produziu as visualizações de página desta sessão. |
+| account_name | character varying(127) | Conta do License Manager à qual a loja desta sessão pertence. |
+| economic_group_id | character varying(127) | Identificador do grupo econômico no contexto de cobrança. |
+| economic_group_name | character varying(1024) | Nome do grupo econômico no contexto de cobrança. |
+| company_id | character varying(127) | Identificador da empresa no contexto de cobrança. |
+| company_name | character varying(1024) | Nome da empresa no contexto de cobrança. |
+| main_account_name | character varying(127) | Nome da conta principal do License Manager relacionada à loja desta sessão. |
+| os_family | character varying(1023) | Família do sistema operacional, extraída do user_agent. |
+| os_major | character varying(1023) | Versão principal do sistema operacional, extraída do user_agent. |
+| os_minor | character varying(1023) | Versão secundária do sistema operacional, extraída do user_agent. |
+| os_patch | character varying(1023) | Patch do sistema operacional, extraído do user_agent. |
+| os_patch_minor | character varying(1023) | Patch menor do sistema operacional, extraído do user_agent. |
+| device_brand | character varying(1023) | Marca do dispositivo, extraída do user_agent. |
+| device_family | character varying(1023) | Família do dispositivo, extraída do user_agent. |
+| device_model | character varying(1023) | Modelo do dispositivo, extraído do user_agent. |
+| browser_family | character varying(1023) | Família do navegador, extraída do user_agent. |
+| browser_major | character varying(1023) | Versão principal do navegador, extraída do user_agent. |
+| browser_minor | character varying(1023) | Versão secundária do navegador, extraída do user_agent. |
+| browser_patch | character varying(1023) | Patch do navegador, extraído do user_agent. |
+| user_id | character varying(16383) | Identificador único do comprador, mapeado pelo cookie VtexRCMacIdv7. |
+| pageviews_count | integer | Contagem de visualizações de página nesta sessão. |
+| views_home | integer | Contagem de visualizações da página inicial nesta sessão. |
+| views_category | integer | Contagem de visualizações de páginas de categoria nesta sessão. |
+| views_department | integer | Contagem de visualizações de páginas de departamento nesta sessão. |
+| views_search | integer | Contagem de visualizações de páginas de busca nesta sessão. |
+| views_product | integer | Contagem de visualizações de páginas de produto nesta sessão. |
+| views_checkout | integer | Contagem de visualizações de páginas de checkout nesta sessão. |
+| views_other | integer | Contagem de visualizações de outras páginas nesta sessão. |
+| views_checkout_cart | integer | Contagem de visualizações de páginas de checkout no estágio do carrinho. |
+| views_checkout_payment | integer | Contagem de visualizações de páginas de checkout no estágio de pagamento. |
+| views_checkout_shipping | integer | Contagem de visualizações de páginas de checkout no estágio de envio. |
+| views_checkout_profile | integer | Contagem de visualizações de páginas de checkout no estágio de perfil. |
+| views_checkout_orderplaced | integer | Contagem de visualizações de páginas de checkout no estágio de pedido realizado. |
+| views_checkout_email | integer | Contagem de visualizações de páginas de checkout no estágio de email. |
+| workspace | character varying(16383) | Workspace da VTEX, geralmente o principal. |
+| user_agent | character varying(16383) | String do User-Agent extraída do lado do servidor da requisição. |
+| is_first_visit | boolean | Indica se é a primeira visita do usuário (não conta para visitantes recorrentes em diferentes navegadores). |
+| session_start_time | timestamp without time zone | Data e hora do início da sessão. |
+| entrance_page_url | character varying(16383) | URL da primeira visualização de página nesta sessão. |
+| entrance_page_type | character varying(16383) | Tipo de página da primeira visualização nesta sessão. |
+| entrance_page_checkout_step | character varying(16383) | Etapa de checkout da primeira visualização de página nesta sessão. |
+| session_end_time | timestamp without time zone | Data e hora do fim da sessão. |
+| exit_page_url | character varying(16383) | URL da última visualização de página nesta sessão. |
+| exit_page_type | character varying(16383) | Tipo de página da última visualização nesta sessão. |
+| exit_page_checkout_step | character varying(16383) | Etapa de checkout da última visualização de página nesta sessão. |
+
+## Tabela pageviews
+
+Cada item nesta tabela corresponde a uma página visualizada pelo comprador, como a página inicial, página de produto e etapa de checkout.  
+Uma visualização de página é contabilizada após o navegador do comprador carregar a página, em vez de quando o pedido ou clique acontece.  
+
+Cada página possui atributos específicos e, como esta tabela reúne tudo em um único esquema, muitos valores nulos aparecerão. Por exemplo, espera-se que os atributos das páginas de produtos sejam nulos quando a visualização da página corresponder a uma etapa do carrinho de compras. Veja a seguir os campos que compõem a tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| client_date | timestamp without time zone | Data e hora do servidor da visualização da página. |
+| session_id | character varying(127) | Identificador único de uma sessão, mapeando diretamente para o cookie VtexRCSessionIdv7. |
+| page_type | character varying(127) | Tipo da página acessada, com valores predefinidos como 'home', 'category', 'product', entre outros. |
+| checkout_step | character varying(127) | Etapa de checkout da página, válida quando page_type é 'checkout'. |
+| economic_group_id | character varying(127) | Identificador do grupo econômico no contexto de cobrança. |
+| economic_group_name | character varying(1024) | Nome do grupo econômico no contexto de cobrança. |
+| company_id | character varying(127) | Identificador da empresa no contexto de cobrança. |
+| company_name | character varying(1024) | Nome da empresa no contexto de cobrança. |
+| main_account_name | character varying(127) | Conta principal do License Manager à qual a loja pertence. |
+| account_name | character varying(127) | Conta do License Manager à qual a loja pertence. |
+| store_name | character varying(127) | Nome da loja que produziu o evento de visualização de página. |
+| url | character varying(16383) | URL completa da visualização da página. |
+| store_host | character varying(127) | Hostname extraído da URL. |
+| page_url | character varying(16383) | URL limpa da visualização da página, sem parâmetros de consulta. |
+| ref | character varying(16383) | URL da página que referenciou o comprador a esta página. |
+| workspace | character varying(127) | Workspace da VTEX, geralmente 'master'. |
+| workspace_ab_test_id | character varying(127) | ID de teste AB extraído do nome do workspace. |
+| user_agent | character varying(16383) | String do User-Agent extraída do lado do servidor. |
+| os_family | character varying(1023) | Família do SO extraída do user_agent. |
+| os_major | character varying(1023) | Versão principal do SO extraída do user_agent. |
+| os_minor | character varying(1023) | Versão secundária do SO extraída do user_agent. |
+| os_patch | character varying(1023) | Patch do SO extraído do user_agent. |
+| os_patch_minor | character varying(1023) | Patch menor do SO extraído do user_agent. |
+| device_brand | character varying(1023) | Marca do dispositivo extraída do user_agent. |
+| device_family | character varying(1023) | Família do dispositivo extraída do user_agent. |
+| device_model | character varying(1023) | Modelo do dispositivo extraído do user_agent. |
+| browser_family | character varying(1023) | Família do navegador extraída do user_agent. |
+| browser_major | character varying(1023) | Versão principal do navegador extraída do user_agent. |
+| browser_minor | character varying(1023) | Versão secundária do navegador extraída do user_agent. |
+| browser_patch | character varying(1023) | Patch do navegador extraído do user_agent. |
+| user_id | character varying(127) | Identificador único do comprador. |
+| is_first_visit | boolean | Indica se é a primeira visita do usuário. |
+| category_id | character varying(127) | Identificador da categoria. |
+| category_name | character varying(16383) | Nome da categoria. |
+| department_id | character varying(127) | Identificador do departamento. |
+| department_name | character varying(16383) | Nome do departamento. |
+| product_id | character varying(127) | Identificador do produto. |
+| product_reference_id | character varying(1024) | Referência do produto. |
+| product_name | character varying(16383) | Nome do produto. |
+| product_brand_id | integer | Identificador da marca do produto. |
+| product_brand_name | character varying(1024) | Nome da marca do produto. |
+| product_department_id | integer | Identificador do departamento do produto. |
+| product_department_name | character varying(1024) | Nome do departamento do produto. |
+| product_category_id | integer | Identificador da categoria do produto. |
+| product_category_name | character varying(1024) | Nome da categoria do produto. |
+| product_list_price | numeric(22,4) | Preço de lista do produto. |
+| product_price | numeric(22,4) | Preço do produto. |
+| seller_id | character varying(127) | Identificador do vendedor. |
+| seller_ids | character varying(16383) | Identificadores do vendedor. |
+| site_search_term | character varying(16383) | Termo de busca no site. |
+| site_search_form | character varying(16383) | Formulário de busca no site. |
+| site_search_category | character varying(127) | Categoria de busca no site. |
+| site_search_results | integer | Resultados da busca no site. |
+| sales_channel | character varying(10) | Canal de vendas. |
+| order_form_id | character varying(127) | Identificador do formulário de pedido. |
+| order_form_shipping | numeric(22,4) | Custo de envio no formulário de pedido. |
+| order_form_total | numeric(22,4) | Total no formulário de pedido. |
+| order_form_tax | numeric(22,4) | Imposto no formulário de pedido. |
+| campaign_name | character varying(16383) | Nome da campanha. |
+| campaign_source | character varying(16383) | Fonte da campanha. |
+| campaign_medium | character varying(16383) | Meio da campanha. |
+| internal_campaign_name | character varying(16383) | Nome da campanha interna. |
+| internal_campaign_part | character varying(16383) | Parte da campanha interna. |
+| order_form_payment_type | character varying(127) | Tipo de pagamento no formulário de pedido. |
+| order_group | character varying(127) | Grupo de pedido. |
+| transaction_id | character varying(127) | Identificador da transação. |
+| visitor_login_state | character varying(16383) | Estado de login do visitante. |
+| visitor_type | character varying(16383) | Tipo de visitante. |
+| visitor_optin_news_letter | boolean | Opt-in do visitante para newsletter. |
+| profile_id | character varying(127) | ID do perfil do comprador, recebido do sistema VTEX Profile. |
+| batch_id | character varying(13) | ID de controle da ingestão de dados. |
+| id | character varying(36) | UUID gerado na ingestão de dados. |
+| transaction_products | super | Produtos na transação. |
+| transaction_total | numeric(22,4) | Total da transação. |
+
+## Análises com dados de Navegação
+
+Os dados de navegação podem ser utilizados para as seguintes análises:  
+
+**- Taxa de conversão geral:** calcule a proporção de sessões que resultaram em uma compra em relação ao total de sessões para avaliar a eficácia geral do site em converter visitantes em compradores.  
+**- Análise de funil de conversão:** agrupe pageviews por etapas do funil (home, pesquisa, produto, carrinho, checkout) e conte quantas sessões passaram por cada etapa, identificando onde os usuários desistem.  
+**- Páginas mais visitadas:** conte o número de pageviews para cada tipo de página (home, categoria, produto) para identificar quais páginas atraem mais atenção e otimizá-las para conversão.  
+**- Rastreamento de caminhos do usuário:** sequencie as pageviews para cada sessão para entender o caminho percorrido pelo usuário e descobrir padrões de navegação comuns.  
+**- Origem do tráfego:** analise a URL de referência de cada sessão para determinar a fonte do tráfego e entender quais canais de marketing estão mais eficazes.  
+**- Taxa de rejeição por tipo de página:** identifique sessões que terminam após uma única pageview e calcule a taxa de rejeição por tipo de página para melhorar o conteúdo ou design dessas páginas.  
+
+## Correlações com outros dados
+
+Nos dados de navegação da VTEX, observamos interações significativas com outros conjuntos de dados que enriquecem a análise do comportamento do usuário, por exemplo:  
+
+**- Interação com fados de pedidos:** análise comparativa entre navegação e conversões de pedidos revela o impacto das jornadas do usuário nas decisões de compra.  
+**- Relação com os SKUs:** a interação dos usuários com as páginas de produtos e categorias oferece insights sobre a popularidade e eficácia da apresentação dos produtos.  
+**- Dados de marketing e campanhas:** a correlação entre a navegação e as campanhas de marketing ajuda a avaliar a eficiência dessas campanhas na atração de tráfego e na geração de conversões.  
+
+### Conheça outros Conjuntos de dados
+
+- [Inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)   
+- [Pagamentos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Preços](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)  
+- [Promoção](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/pt/new-integration-with-erede-erederest.md b/docs/tutorials/pt/new-integration-with-erede-erederest.md
index 2dde59cd7..971da63f4 100644
--- a/docs/tutorials/pt/new-integration-with-erede-erederest.md
+++ b/docs/tutorials/pt/new-integration-with-erede-erederest.md
@@ -25,11 +25,11 @@ Para configurar a nova versão, você precisa primeiro solicitar à Rede a ativa
 
 Uma vez notificado, acesse o menu __e.Rede > Configurações > Geração de token__.
 
-![GerarToken](https://images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
+![GerarToken](//images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
 
 Depois, basta clicar no botão __Gerar Token__.
 
-![GerarToken Click](https://images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
+![GerarToken Click](//images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
 
 Com isso, você vai poder visualizar o token que deverá ser informado no formulário de configuração da afiliação de gateway ERedeRest. Além do token, você também vai precisar informar o PV, que nada mais é do que o número de identificação do estabelecimento no site da Rede.
 
@@ -39,10 +39,10 @@ Para fazer essa configuração na VTEX, siga os passos abaixo:
 2. Em __Configurações__, acesse __Afiliações de Gateways__; 
 3. Clique no botão verde __+__ _Quero receber pagamento pelo conector..._ e procure o conector __ERedeRest.__
 
-![erederestPT](https://images.ctfassets.net/alneenqid6w5/3RvR1eS0FWKyS8ImoQOk4I/13563c566f5f599885fc2f7759c6d826/erederestPT.jpg)
+![erederestPT](//images.ctfassets.net/alneenqid6w5/3RvR1eS0FWKyS8ImoQOk4I/13563c566f5f599885fc2f7759c6d826/erederestPT.jpg)
 
-![erederestPT-config](https://images.ctfassets.net/alneenqid6w5/6ZD1t6RKfe468MASAycWEg/b38d8ecd1c455d09f82bceeb0317cfeb/erederestPT-config.jpg)
+![erederestPT-config](//images.ctfassets.net/alneenqid6w5/6ZD1t6RKfe468MASAycWEg/b38d8ecd1c455d09f82bceeb0317cfeb/erederestPT-config.jpg)
 
-![PegarPV](https://images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
+![PegarPV](//images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
 
 Este novo conector oferece uma série de opções de configuração, entre elas o suporte ao ApplePay.
diff --git a/docs/tutorials/pt/new-route.md b/docs/tutorials/pt/new-route.md
index 7f46b1b73..a23d46452 100644
--- a/docs/tutorials/pt/new-route.md
+++ b/docs/tutorials/pt/new-route.md
@@ -95,5 +95,5 @@ Remover entregas clicando  no __X__ à direta da entrega.
 Só é possível editar uma rota se ela ainda estiver no status Ativo. Não é indicado alterar uma rota se ela já foi iniciada - isso pode causar inconsistências na plataforma do VTEX Tracking e no aplicativo do portador.
 </div>
 
-![Cadastro de nova rota](https://images.ctfassets.net/alneenqid6w5/3m2JhopNd3vcscWEOYSnvn/f739888039df88f13fc7bcab16325253/Nova_Rota.gif)
+![Cadastro de nova rota](//images.ctfassets.net/alneenqid6w5/3m2JhopNd3vcscWEOYSnvn/f739888039df88f13fc7bcab16325253/Nova_Rota.gif)
 
diff --git a/docs/tutorials/pt/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md b/docs/tutorials/pt/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
index c37787f6a..082ddf95d 100644
--- a/docs/tutorials/pt/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
+++ b/docs/tutorials/pt/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
@@ -1,10 +1,10 @@
 ---
 title: 'Registros de Newsletter com controle <vtex.cmc:newsletterOptIn/>'
 id: xqKrRRHBscEI8O6UKi8eE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-06-07T18:35:59.237Z
-updatedAt: 2023-03-31T11:24:39.916Z
-publishedAt: 2023-03-31T11:24:39.916Z
+updatedAt: 2023-12-08T18:44:28.114Z
+publishedAt: 
 firstPublishedAt: 2019-01-25T17:16:54.823Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/pt/offer-details.md b/docs/tutorials/pt/offer-details.md
index deab20068..13789df2e 100644
--- a/docs/tutorials/pt/offer-details.md
+++ b/docs/tutorials/pt/offer-details.md
@@ -1,10 +1,10 @@
 ---
 title: 'Gerenciamento de anúncios: detalhes do anúncio '
 id: 4FF9QYAewqAn610mDHwb0P
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T01:07:12.412Z
-updatedAt: 2023-03-31T04:51:33.756Z
-publishedAt: 2023-03-31T04:51:33.756Z
+updatedAt: 2024-06-20T21:34:45.076Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:13:19.773Z
 contentType: tutorial
 productTeam: Channels
@@ -15,6 +15,13 @@ legacySlug: detalhes-do-anuncio
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
+<div class="alert alert-info">
+Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
+Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
+</div>  
+
 Anúncio é um SKU de um seller que teve seu  preço e estoque configurados e foi enviado para diferentes canais de venda. É no módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) que sellers supervisionam o envio e sincronização de seus anúncios para marketplaces.
 
 A página de **Detalhes do anúncio** é onde todas as informações sobre um anúncio específico são visualizadas. É a partir dela que o seller visualiza as interações ocorridas com um anúncio, os [detalhes de cada interação](https://help.vtex.com/pt/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf) o e os erros detectados. Cada interação do anúncio fica disponível por dez dias a partir do seu registro.
@@ -35,7 +42,7 @@ O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="
 
 ## Cabeçalho
 
-![Offer details PT cabecalho](https://images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/1d3d99d4aa6204871518904c7abbef2b/Offer_details_PT_cabecalho.jpg)
+![Offer details PT cabecalho](//images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/1d3d99d4aa6204871518904c7abbef2b/Offer_details_PT_cabecalho.jpg)
 
 O cabeçalho traz algumas informações principais do anúncio para rápida visualização, como imagem, canal nome, status, ID na VTEX e ID no canal. Permite também realizar as seguintes interações por meio do botão `Editar`:
 
@@ -51,13 +58,13 @@ O bloco de _Status do anúncio_ traz mais detalhes sobre o status do anúncio, q
 
 ### Status: Sincronizado
 
-![Offer details PT status sucesso](https://images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/ee786de0eeee54fd2f5ee39fbc4e9d2e/Offer_details_PT_status_sucesso.jpg)
+![Offer details PT status sucesso](//images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/ee786de0eeee54fd2f5ee39fbc4e9d2e/Offer_details_PT_status_sucesso.jpg)
 
 O status *Sincronizado* significa que o anúncio foi recebido com sucesso em um canal e está sendo atualizado tanto pelo marketplace quanto pelo seller, em tempo real.   
 
 ### Status: Erro
 
-![Offer details PT status erro](https://images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/99e44f5378b0fcec010e122d48c2ad12/Offer_details_PT_status_erro.jpg)
+![Offer details PT status erro](//images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/99e44f5378b0fcec010e122d48c2ad12/Offer_details_PT_status_erro.jpg)
 
 O status *Erro* significa que o sistema encontrou um problema que previne um anúncio de ser enviado ou atualizado em um canal, portanto é necessário que o seller o corrija. Erros podem originar do lado do seller VTEX, como descrições de produtos que excedem o limite de caracteres, e do lado do marketplace, como chamadas de API que falharam.   
 
@@ -75,19 +82,19 @@ Se ainda existirem erros para serem corrigidos, ou se todos forem corrigidos mas
 
 ### Status: Indisponível
 
-![Offer details PT status indisponivel](https://images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/89c9d4be9f3ce73bc9d39c462895588e/Offer_details_PT_status_indisponivel.jpg)
+![Offer details PT status indisponivel](//images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/89c9d4be9f3ce73bc9d39c462895588e/Offer_details_PT_status_indisponivel.jpg)
 
 O status *Indisponível* ocorre quando o anúncio é descartado, por estar inativo ou não incluído na [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) determinada para o canal.
 
 ### Status: Enviando
 
-![Offer details PT status enviando](https://images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/e0d021f8201b4188eb386d6de06bf4e5/Offer_details_PT_status_enviando.jpg)
+![Offer details PT status enviando](//images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/e0d021f8201b4188eb386d6de06bf4e5/Offer_details_PT_status_enviando.jpg)
 
 O status *Enviando* é um estado intermediário, quando anúncios ainda estão no processo de envio para o canal. Esse status envolve anúncios que estão sendo enviados pela primeira vez ao marketplace, estão migrando para um novo canal, ou foram reenviados após serem descartados em um canal.   
 
 ## Lista de Interações
 
-![Offer details PT lista interacoes](https://images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/323c0c9d2a17e850dca69cc70a4a00fb/Offer_details_PT_lista_interacoes.jpg)
+![Offer details PT lista interacoes](//images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/323c0c9d2a17e850dca69cc70a4a00fb/Offer_details_PT_lista_interacoes.jpg)
 
 A lista de *Interações* reúne todas as atualizações de `estoque`, `preço` ou `catálogo` que aquele SKU sofreu. É possível filtrar por origem e por status, além de ajustar quantos itens são mostrados por página. Cada linha corresponde a uma interação ocorrida àquele anúncio, e inclui os seguintes dados:
 
diff --git a/docs/tutorials/pt/offer-management-moderation-and-quality-of-mercado-libre.md b/docs/tutorials/pt/offer-management-moderation-and-quality-of-mercado-libre.md
index 92f4ac4ae..464d76064 100644
--- a/docs/tutorials/pt/offer-management-moderation-and-quality-of-mercado-libre.md
+++ b/docs/tutorials/pt/offer-management-moderation-and-quality-of-mercado-libre.md
@@ -3,8 +3,8 @@ title: 'Gerenciamento de Anúncios: moderação e qualidade dos anúncios do Mer
 id: xSbPzA41jiWPAorlBCEA4
 status: PUBLISHED
 createdAt: 2022-10-24T16:38:07.914Z
-updatedAt: 2022-10-24T17:03:57.020Z
-publishedAt: 2022-10-24T17:03:57.020Z
+updatedAt: 2024-06-20T21:41:34.703Z
+publishedAt: 2024-06-20T21:41:34.703Z
 firstPublishedAt: 2022-10-24T17:03:57.020Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/pt/offer-management.md b/docs/tutorials/pt/offer-management.md
index 40bc8a0bc..aa817520b 100644
--- a/docs/tutorials/pt/offer-management.md
+++ b/docs/tutorials/pt/offer-management.md
@@ -1,10 +1,10 @@
 ---
 title: 'Módulo Gerenciamento de anúncios'
 id: 7MRb9S78aBdZjFGpbuffpE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-03-17T00:44:49.452Z
-updatedAt: 2023-03-31T04:39:55.235Z
-publishedAt: 2023-03-31T04:39:55.235Z
+updatedAt: 2024-06-20T21:34:27.585Z
+publishedAt: 
 firstPublishedAt: 2021-03-17T01:05:49.343Z
 contentType: tutorial
 productTeam: Channels
@@ -15,19 +15,26 @@ legacySlug: listagem-de-anuncios
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
+<div class="alert alert-info">
+Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
+Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
+</div>  
+
 O módulo **Gerenciamento de anúncios** permite aos sellers acompanhar o envio e a sincronização de anúncios de integrações com canais de venda. Na VTEX, anúncio é um SKU de um seller que teve seu preço e estoque configurados e foi enviado para um canal de venda.
 
-![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 O **Gerenciamento de anúncios** permite acompanhar anúncios com o [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic e Premium), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e marketplaces VTEX. Para conectores que desejam integrar via API, existe o [Guia de integração do Gerenciamento de anúncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 Para acessar o módulo, no Admin VTEX, acesse **Marketplace > Conexões > Gerenciamento de anúncios**. Feito isso, a seguinte interface vai aparecer: 
 
-![gerenciamentodeanúncios front](https://images.ctfassets.net/alneenqid6w5/u8R35ILY4A5G79HWKj7cg/cf4fe5a5145955d4f8955faf3ae47dee/gerenciamentodean__ncios_front.JPG)
+![gerenciamentodeanúncios front](//images.ctfassets.net/alneenqid6w5/u8R35ILY4A5G79HWKj7cg/cf4fe5a5145955d4f8955faf3ae47dee/gerenciamentodean__ncios_front.JPG)
 
 A interface da **Gerenciamento de anúncios** apresenta uma listagem dos seus anúncios, sendo possível clicar sobre o anúncio para acessar [detalhes do anúncio](https://help.vtex.com/pt/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) e conferir [detalhes da interação](https://help.vtex.com/pt/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf). As interações são os registros do anúncio ao longo do processo de sincronização e envio para o canal de venda, e ficam disponíveis para consulta por dez dias.
 
-![diagrama ju meyer sent offers pt](https://images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/c87303d8811c779c9ae72e9ee97df409/diagrama_ju_meyer_sent_offers_pt.png)
+![diagrama ju meyer sent offers pt](//images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/c87303d8811c779c9ae72e9ee97df409/diagrama_ju_meyer_sent_offers_pt.png)
 
 Na página **Gerenciamento de anúncios**, é possível realizar as seguintes ações:
 
diff --git a/docs/tutorials/pt/offer-quality-filters.md b/docs/tutorials/pt/offer-quality-filters.md
index 770f5ab81..05cb4488d 100644
--- a/docs/tutorials/pt/offer-quality-filters.md
+++ b/docs/tutorials/pt/offer-quality-filters.md
@@ -1,10 +1,10 @@
 ---
 title: 'Filtros de qualidade dos anúncios'
 id: 4xm0gi8leCyxHj8YdgHSJH
-status: CHANGED
+status: PUBLISHED
 createdAt: 2023-02-27T12:15:26.682Z
-updatedAt: 2023-05-30T21:12:51.762Z
-publishedAt: 2023-02-28T13:45:44.808Z
+updatedAt: 2024-06-20T21:38:38.621Z
+publishedAt: 2024-06-20T21:38:38.621Z
 firstPublishedAt: 2023-02-27T19:32:00.584Z
 contentType: tutorial
 productTeam: Channels
@@ -12,7 +12,7 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: filtros-de-qualidade-dos-anuncios
 locale: pt
 legacySlug: filtros-de-qualidade-dos-anuncios
-subcategory: 4hU8QWlzhxWg711Kz7Gmib
+subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
 Marketplaces precisam revisar e aprovar anúncios enviados por sellers para que os produtos sejam adicionados ao catálogo. No Admin VTEX esse [processo de catalogação](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus--tutorials_396) é feito por meio da página SKUs Recebidos. 
@@ -21,7 +21,7 @@ Marketplaces precisam revisar e aprovar anúncios enviados por sellers para que
 
 **Filtros de qualidade dos anúncios** é a página onde marketplaces cadastram e gerenciam os grupos de requisitos aplicados ao processo de catalogação de SKUs recebidos. Para acessá-la, em seu Admin VTEX, vá para **Marketplace > Qualidade dos Anúncios** ou digite __“Qualidade dos anúncios”__ na barra de busca.
 
-![PT offer quality](https://images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/d51603a30cf92b54035d2229ae23792a/PT_offer_quality.png)
+![PT offer quality](//images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/d51603a30cf92b54035d2229ae23792a/PT_offer_quality.png)
 
 Nesse artigo, saiba como:
 
@@ -47,7 +47,7 @@ A funcionalidade permite ao operador de marketplace realizar uma série de açõ
 
 ## Visualizar "Default requirements"
 
-![PT Default requirements](https://images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/7b191f93fedb9f951939925e481c473b/PT_Default_requirements.png)
+![PT Default requirements](//images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/7b191f93fedb9f951939925e481c473b/PT_Default_requirements.png)
 
 A página já vem por padrão com alguns requisitos pré-cadastrados que serão aplicados a todas as categorias, sellers e marcas, chamados de "Default requirements", ou Regras padrão. Alguns desses critérios são configurados nativamente no [VTEX Matcher](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), a ferramenta aplicada aos marketplaces VTEX para auxiliar no processo de catalogação de anúncios recebidos. 
 
diff --git a/docs/tutorials/pt/offer-status.md b/docs/tutorials/pt/offer-status.md
new file mode 100644
index 000000000..91fab67dd
--- /dev/null
+++ b/docs/tutorials/pt/offer-status.md
@@ -0,0 +1,239 @@
+---
+title: 'Status de anúncios'
+id: 2OE87wU26F7lApl99OdwvJ
+status: PUBLISHED
+createdAt: 2023-09-29T19:16:05.771Z
+updatedAt: 2024-03-04T20:03:00.144Z
+publishedAt: 2024-03-04T20:03:00.144Z
+firstPublishedAt: 2023-09-29T20:07:16.003Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: status-de-anuncios
+locale: pt
+legacySlug: status-de-anuncios-beta
+subcategory: 2zVauFUkYn8vgS0y0MfWeK
+---
+
+ O módulo **Status de anúncios** permite aos sellers acompanhar o envio e a sincronização de anúncios de integrações com canais de venda. Na VTEX, um anúncio é um SKU ativo de um seller que teve seu preço e estoque configurados e foi enviado para um canal de venda.  
+
+O **Status de anúncios** permite acompanhar anúncios enviados somente a marketplaces VTEX. Para encontrar o módulo no Admin VTEX, acesse **Marketplace > Conexões > Status de anúncios,** ou digite **Status de anúncios** na barra de busca. Feito isso, a seguinte página aparecerá:  
+
+![Tela Offer Status](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/e007c56b38b37f10eb1765dcef3d4945/-PT-_Offer_Status_-_GIF.gif)
+
+A página **Status de anúncios** é composta por três abas, a [**aba Publicados**](#aba-publicados), a [**aba Problemas**](#aba-problemas) e a [**aba Aguardando conclusão**](#aba-aguardando-conclusao), todas apresentam uma listagem de seus anúncios conforme o status que ele se encontra. Em cada anúncio é possível acessar e conferir seus detalhes, que mostram o status, o estoque, preço, data de atualização e motivos de rejeição no marketplace.  
+
+![Fluxo offer status](//images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/bfc7e29ba2f46edfb6c795f5329ce349/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.002.png)  
+
+## Aba Publicados
+
+Na aba **Publicados**, o seller pode acompanhar os anúncios enviados que já foram aprovados pelo marketplace. Nesta aba, é possível realizar as seguintes ações:
+
+- [Buscar e filtrar anúncios](#buscar-e-filtrar-anuncios)
+- [Visualizar informações dos anúncios](#visualizar-informacoes-dos-anuncios)
+- [Editar informações de anúncios](#editar-informacoes-de-anuncios)  
+- [Exportar lista de anúncios publicados](#exportar-lista-de-anuncios-publicados)
+
+### Buscar e filtrar anúncios
+
+No topo direito da página, existe uma barra de busca com o ícone lupa <i class="fas fa-search"></i>. Na barra, você pode buscar um anúncio por **ID do SKU** e **nome do anúncio.**
+
+Além disso, é possível filtrar o resultado da busca pelos seguintes critérios:
+
+- **Marketplace:** canal de venda para o qual o anúncio foi enviado.
+- **Estoque:** quantidade de estoque de um produto, que pode ser:  
+  - `Mínimo:` número mínimo de itens em estoque de um produto.  
+  - `Máximo:` número máximo de itens em estoque de um produto.  
+- **Atualização:** status de atualização de preço e estoque dos anúncios já publicados.  
+
+Para filtrar os anúncios por **Marketplace**, clique na seta para baixo ao lado do termo, selecione a flag dos marketplaces desejados e, em seguida, clique em **APLICAR**.  
+
+Para filtrar os anúncios por **Estoque**, clique na seta para baixo ao lado do filtro, depois digite o número de estoque mínimo, estoque máximo, ou ambos, e clique em **APLICAR**.  
+
+![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/483a898afda9f9ec5121f7ff566de49e/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.003.png)
+
+Para filtrar os anúncios por **Atualização**, clique na seta para baixo ao lado do filtro, selecione uma das opções e clique em **APLICAR.**  
+
+Veja abaixo as opções disponíveis para esse filtro:  
+
+- **Atualizado**: são anúncios que tiveram seu preço e/ou estoque atualizados pelo seller e obtiveram sucesso no processamento.  
+- **Erro ao atualizar:** são anúncios processados após atualização e, tendo sido encontrada alguma inconsistência, ele apresenta erro para atualizar.  
+
+![Filtro atualizado offer status](//images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/715b713a9e23057cd281e869f5d33959/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.004.png)
+
+Você pode utilizar um único filtro ou combiná-los em uma mesma busca. Por padrão, os filtros não estarão selecionados, de forma que a página inicial apresenta a quantidade total de anúncios existentes.  
+
+### Visualizar informações dos anúncios
+
+Na parte superior da página **Status de anúncios**, há uma apresentação dos anúncios do seller com as seguintes informações:  
+
+- Número de anúncios publicados em relação aos anúncios enviados.  
+- Número de anúncios com status **Atualizado.**  
+- Número de anúncios com status **Erro ao atualizar.**  
+
+Na lista de anúncios, existem colunas com as seguintes informações:  
+
+| **Coluna** | **Descrição** |
+|---|---|
+| **Nome** | Apresenta a imagem do SKU, o título do anúncio no canal de venda e o ID do SKU na VTEX. |
+| **Marketplace** | Canal de venda para onde o anúncio foi enviado. |
+| **Preço** | Preço do SKU do anúncio. |
+| **Estoque** | Quantidade de itens em [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) para o SKU do anúncio. |
+| **Atualização** | Situação de processamento da atualização, que pode ser Atualizado <i class="far fa-check-circle"></i> ou Erro ao atualizar <div class="error-icon"></div>. |  
+
+É possível clicar sobre os nomes das colunas para ordenar os anúncios de forma crescente ou decrescente. Por exemplo, ao clicar sobre a coluna **Preço**, é possível ordenar a lista pelo menor preço do anúncio ou pelo maior.  
+
+### Editar informações de anúncios
+
+Ao clicar em um anúncio, se abrirá uma janela contendo barras informativas com os seguintes dados do anúncio:  
+
+- **Preço:** qual o preço atual do anúncio, quando ocorreu a última atualização e se a atualização foi bem sucedida ou não.  
+- **Estoque:** qual o estoque atual do item anunciado, quando ocorreu a última atualização e se a atualização foi bem sucedida ou não.  
+- **Conteúdo:** quando ocorreu a última atualização do conteúdo e se a atualização foi bem sucedida ou não.  
+
+Para atualizar qualquer informação de um anúncio já publicado, o seller deverá realizar os seguintes passos:  
+
+1. Na aba **Publicados,** clique no anúncio desejado.  
+1. Clique no ícone <i class="fas fa-ellipsis-v"></i>de ação no canto superior direito.  
+1. Clique em uma das opções:  
+- **Editar preço**
+- **Editar estoque**
+- **Editar conteúdo**
+
+Você será redirecionado à página correspondente para realizar as alterações necessárias.  
+
+![Ações offer status](//images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/7dc3f62846ca6a28768fe9bc6faddc9d/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.006.jpeg)
+
+### Exportar lista de anúncios publicados
+
+Para exportar a lista de anúncios publicados em formato XLSX, clique sobre o  ícone seta para baixo <i class="fas fa-download"></i>, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação dependerá do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX.
+
+<div class="alert alert-info">
+O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
+</div>
+
+## Aba Problemas
+
+Na aba **Problemas**, o seller pode acompanhar os anúncios enviados que foram reprovados pelo marketplace. Nesta aba, também é possível realizar as seguintes ações:  
+
+- [Buscar e filtrar anúncios](#buscar-e-filtrar-anuncios)
+- [Visualizar detalhes do problema](#visualizar-detalhes-do-problema)
+- [Editar informações de anúncios](#editar-informacoes-de-anuncios)
+- [Exportar anúncios com problemas](#exportar-anuncios-com-problemas)
+
+### Buscar e filtrar anúncios com problemas
+
+No topo direito da página, existe uma barra de busca com o ícone lupa <i class="fas fa-search"></i>, na qual você pode buscar um anúncio por nome do anúncio e ID do SKU.
+
+Além disso, é possível filtrar o resultado da busca pelos seguintes critérios:
+
+- **Marketplace:** canal de venda para o qual o anúncio foi enviado.  
+- **Envio:** períodos pré-definidos de *hoje***,** *últimos 7 dias* e *último mês* em que o anúncio foi enviado ao marketplace.  
+- **Estoque:** quantidade de estoque de um produto:  
+- `Mínimo:` número mínimo de itens em estoque de um produto.  
+- `Máximo:` número máximo de itens em estoque de um produto.  
+
+Para filtrar os anúncios por **Marketplace**, clique na seta para baixo ao lado do termo, selecione a flag dos marketplaces desejados e, em seguida, clique em **APLICAR**.  
+
+Para filtrar os anúncios por **Envio**, clique na seta para baixo ao lado do filtro, selecione uma das opções e clique em **APLICAR.**  
+
+Para filtrar os anúncios por **Estoque**, clique na seta para baixo ao lado do filtro, depois digite o número de estoque mínimo ou estoque máximo, ou, ambos e clique em **APLICAR**.  
+
+![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/483a898afda9f9ec5121f7ff566de49e/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.003.png)
+
+Você pode utilizar um único filtro ou combiná-los em uma mesma busca. Por padrão, os filtros não estarão selecionados, de forma que a página inicial apresenta a quantidade total de anúncios existentes.  
+
+### Visualizar detalhes do problema
+
+Na aba **Problemas**, a lista de anúncios é apresentada com as seguintes informações em colunas:
+
+| **Coluna** | **Descrição** |
+|---|---|
+| **Nome** | Apresenta a imagem do SKU, o título do anúncio no canal de venda e o ID do SKU na VTEX. |
+| **Marketplace** | Canal de venda para onde o anúncio foi enviado. |
+| **Preço** | Preço do SKU do anúncio. |
+| **Estoque** | Quantidade de itens em [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) para o SKU do anúncio. |
+| **Problemas** | Número de problemas identificados no anúncio. |
+| **Envio** | Data que o anúncio foi enviado ao marketplace. |
+
+### Editar informações de anúncios 
+
+Ao clicar em um anúncio, se abrirá uma janela contendo uma barra informativa dos erros encontrados no anúncio, listados abaixo:  
+
+- **Possíveis erros**  
+  - **Anúncio negado pelo marketplace:** quando o marketplace não aceita o anúncio por não atender os requisitos estabelecidos pelo marketplace.  
+  - **Atualização de estoque:** quando o SKU do anúncio não tem estoque configurado.  
+  - **Atualização de preço:** quando o preço de um anúncio não foi configurado.  
+
+Para atualizar qualquer informação de um anúncio com problemas, o seller deverá realizar os passos listados abaixo:  
+
+1. Na aba de anúncios com **Problemas**, clique no anúncio desejado.  
+2. Clique no ícone <i class="fas fa-ellipsis-v"></i> de ação no canto superior direito.  
+3. Clique em uma das opções:   
+- **Editar preço**  
+- **Editar inventário**  
+- **Editar conteúdo**  
+
+Você será redirecionado à página correspondente para realizar as alterações necessárias.
+
+### Exportar lista de anúncios com problemas 
+
+Para exportar a lista de anúncios com problemas em formato XLSX, clique sobre o  ícone seta para baixo <i class="fas fa-download"></i>, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação dependerá do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX. 
+
+<div class="alert alert-info">
+  O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
+  </div>
+
+## Aba Aguardando Conclusão
+
+Na aba **Aguardando conclusão**, o seller pode acompanhar os anúncios que estão aguardando análise do marketplace. Nesta aba, também é possível realizar as seguintes ações:  
+
+- [Buscar e filtrar anúncios em análise](#buscar-e-filtrar-anuncios-em-analise)  
+- [Editar informações de anúncios](#editar-informacoes-de-anuncios)
+- [Exportar lista de anúncios aguardando conclusão](#exportar-lista-de-anuncios-aguardando-conclusao)  
+
+### Buscar e filtrar anúncios em análise
+
+Na parte superior direita da página, existe uma barra de busca com o ícone lupa <i class="fas fa-search"></i>. Na barra, você pode buscar um anúncio por nome do anúncio e ID do SKU.  
+
+Além disso, é possível filtrar o resultado da busca pelos seguintes critérios:  
+
+- **Marketplace:** canal de venda para o qual o anúncio foi enviado.  
+- **Envio:** períodos pré-definidos de, **hoje, últimos 7 dias** e **último mês,** em que o anúncio foi enviado ao marketplace.  
+
+Para filtrar os anúncios por **Marketplace**, clique na seta para baixo ao lado do termo, selecione a flag dos marketplaces desejados e, em seguida, clique em **APLICAR**.  
+
+Para filtrar os anúncios por **Envio**, clique na seta para baixo ao lado do filtro, selecione uma das opções e clique em **APLICAR.**  
+
+Você pode utilizar um único filtro ou combiná-los em uma mesma busca. Por padrão, os filtros não estarão selecionados, de forma que a página inicial apresenta a quantidade total de anúncios existentes.  
+
+### Editar informações de anúncios
+
+Na aba **Aguardando conclusão,** a lista de anúncios é apresentada com as seguintes informações em colunas:  
+
+| **Coluna** | **Descrição** |
+|---|---|
+| **Nome** | Apresenta a imagem do SKU, o título do anúncio no canal de venda e o ID do SKU na VTEX. |
+| **Marketplace** | Canal de venda para onde o anúncio foi enviado. |
+| **Envio** | Data que o anúncio foi enviado ao marketplace. |
+
+É possível clicar sobre os nomes das colunas para ordenar os anúncios de forma crescente ou decrescente.  
+
+Para atualizar qualquer informação de um anúncio em análise, o seller deverá realizar os seguintes passos:  
+
+1. Na aba **Aguardando conclusão**, clique no anúncio desejado.  
+2. Clique no ícone <i class="fas fa-ellipsis-v"></i>de ação no canto superior direito.  
+3. Clique em uma das opções:  
+- **Editar preço**  
+- **Editar inventário**  
+- **Editar conteúdo**  
+
+Você será redirecionado à página correspondente para realizar as alterações necessárias. 
+
+### Exportar lista de anúncios aguardando conclusão
+
+Para exportar a lista de anúncios aguardando conclusão em formato XLSX, clique sobre o ícone seta para baixo <i class="fas fa-download"></i>, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação dependerá do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX.
+
+<div class="alert alert-info">
+O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
+</div>
diff --git a/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md b/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
index 8dfc6575c..7b108f79f 100644
--- a/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
+++ b/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
@@ -23,7 +23,7 @@ Por padrão, é necessário que o produto que será enviado do seller também po
 
 A imagem a seguir representa um exemplo, no qual o Seller A envia um produto para o Marketplace A. Caso o Marketplace A possua em seu próprio estoque o mesmo produto que o Seller A enviou, então ele poderá enviar esse item ao marketplace B.
 
-![erro-envio-skus-sellers-marketplaces-docnovo](https://images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
+![erro-envio-skus-sellers-marketplaces-docnovo](//images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
 
 Marketplaces com esse modelo de negócios são beneficiados porque poderão expandir seu sortimento em canais de vendas terceiros gerando mais oportunidades de vendas.
 
diff --git a/docs/tutorials/pt/oms-page-structure.md b/docs/tutorials/pt/oms-page-structure.md
index 7bb29494d..49b5ebfa9 100644
--- a/docs/tutorials/pt/oms-page-structure.md
+++ b/docs/tutorials/pt/oms-page-structure.md
@@ -37,7 +37,7 @@ Para todos os dados de variações de pedidos, e também para os números de evo
 Importante: se a comparação de pedidos é feita com base em 0 pedidos no passado, a variação é de 0%.
 </div>
 
-![barra-de-status-oms pt](https://images.ctfassets.net/alneenqid6w5/4LWth3g02ACyIe4kAAgaW4/375d254b73d0fe7a0b2ae42da0a35b12/barra_de_status_pt.png)
+![barra-de-status-oms pt](//images.ctfassets.net/alneenqid6w5/4LWth3g02ACyIe4kAAgaW4/375d254b73d0fe7a0b2ae42da0a35b12/barra_de_status_pt.png)
 
 ### Filtros
 
@@ -45,7 +45,7 @@ Permitem aplicar diversos filtros para ver somente a listagem de pedidos desejad
 
 - [Como filtrar pedidos](/pt/tutorial/como-filtrar-pedidos/)
 
-![botao-filtro-oms pt ](https://images.ctfassets.net/alneenqid6w5/5BeUtetKIoIOqqCeQqkwOe/7fcc082340475f487e58de9c5d162c27/filtro_pt.png)
+![botao-filtro-oms pt ](//images.ctfassets.net/alneenqid6w5/5BeUtetKIoIOqqCeQqkwOe/7fcc082340475f487e58de9c5d162c27/filtro_pt.png)
 
 ### Barra de busca
 
@@ -53,7 +53,7 @@ Utilizada para fazer buscas sobres os termos encontrados no pedido, como número
 
 - [Como buscar pedidos](/pt/tutorial/como-buscar-o-pedido/)
 
-![barra-de-busca-oms pt](https://images.ctfassets.net/alneenqid6w5/5n7vRoP7ws8ScEuukOG86G/0860905754f93c79af9d01ff1d8af114/barra_de_busca_pt.png)
+![barra-de-busca-oms pt](//images.ctfassets.net/alneenqid6w5/5n7vRoP7ws8ScEuukOG86G/0860905754f93c79af9d01ff1d8af114/barra_de_busca_pt.png)
 
 ### Barra de informações
 
@@ -63,7 +63,7 @@ Traz também o ranking de vendas da loja em relação a todas as outras lojas da
 
 - [Interpretando os dados da barra de pedidos na tela de Todos os Pedidos.](http://help.vtex.com/pt/tutorial/interpretando-os-dados-da-barra-de-pedidos-do-oms) 
 
-![barra-de-info-oms pt](https://images.ctfassets.net/alneenqid6w5/5yArBUQd9emIc0iA8e8Meq/74cc0ed8d9b7d6ab7b4dc48c44a79e96/barra_de_info_pt.png)
+![barra-de-info-oms pt](//images.ctfassets.net/alneenqid6w5/5yArBUQd9emIc0iA8e8Meq/74cc0ed8d9b7d6ab7b4dc48c44a79e96/barra_de_info_pt.png)
 
 ### Botão de exportação
 
@@ -71,7 +71,7 @@ Utilizado para exportar os pedidos retornados na busca, sempre considerando os f
 
 - [Exportar pedidos em Gerenciamento de pedidos](http://help.vtex.com/pt/tutorial/exportando-pedidos-no-oms-2) 
 
-![botao-exportação-oms pt ](https://images.ctfassets.net/alneenqid6w5/2GJezm4WzmIOig8mkmekAy/525184bd7f438e74e609feea092ec98e/botao_exporta____o_pt.png)
+![botao-exportação-oms pt ](//images.ctfassets.net/alneenqid6w5/2GJezm4WzmIOig8mkmekAy/525184bd7f438e74e609feea092ec98e/botao_exporta____o_pt.png)
 
 ### Lista de pedidos
 
@@ -79,7 +79,7 @@ Principal área de Gerenciamento de pedidos. Traz os últimos pedidos realizados
 
 - [Lista de pedidos](/pt/tutorial/lista-de-pedidos/)
 
-![todos-pedidos-oms pt](https://images.ctfassets.net/alneenqid6w5/VIquxEKz8kK4uEqOkWIUK/7fa197e58df4996da0f9e9b957bf0dcd/todos_os_pedidos_pt.png)
+![todos-pedidos-oms pt](//images.ctfassets.net/alneenqid6w5/VIquxEKz8kK4uEqOkWIUK/7fa197e58df4996da0f9e9b957bf0dcd/todos_os_pedidos_pt.png)
 
 ### VTEX DO
 
@@ -87,7 +87,7 @@ Reúne tarefas pendentes pela loja e são geradas pelos diferentes módulos da V
 
 - [Como funciona a lista de tarefas do VTEX DO](http://help.vtex.com/pt/tutorial/vtex-do)
 
-![vtex-do-oms pt](https://images.ctfassets.net/alneenqid6w5/JkifTR1dyCUC8SIASwmws/35a6dcac6626553ea08a4492c526f965/vtex_do_pt.png)
+![vtex-do-oms pt](//images.ctfassets.net/alneenqid6w5/JkifTR1dyCUC8SIASwmws/35a6dcac6626553ea08a4492c526f965/vtex_do_pt.png)
 
 ## Assinaturas
 
@@ -105,5 +105,5 @@ A segunda aba, **Afiliados**, é destinada para configurações de afiliados em
 
 - [Configurar Afiliado](http://help.vtex.com/pt/tutorial/como-configurar-afiliado/)
 
-![oms-configurações-gerais pt](https://images.ctfassets.net/alneenqid6w5/T2R9jSftMAa66ukO864Wy/235af9b18deb16fc1e187b1da5752318/oms_configura____es_pt.png)
+![oms-configurações-gerais pt](//images.ctfassets.net/alneenqid6w5/T2R9jSftMAa66ukO864Wy/235af9b18deb16fc1e187b1da5752318/oms_configura____es_pt.png)
 
diff --git a/docs/tutorials/pt/opening-hours-suiteshare.md b/docs/tutorials/pt/opening-hours-suiteshare.md
index 6c6c0aac0..32bfd0a95 100644
--- a/docs/tutorials/pt/opening-hours-suiteshare.md
+++ b/docs/tutorials/pt/opening-hours-suiteshare.md
@@ -24,7 +24,7 @@ Além de organizar e distribuir os atendimentos, você pode definir horários de
 - [**Sequencial**](https://help.vtex.com/pt/tutorial/sequencial--212r1PKHPGdpbbRlpf2gY3): o atendente não receberá clientes durante o período.  
 - [**Geolocalizado**](https://help.vtex.com/pt/tutorial/geolocalizado--6XIfgaqXaPe5exQa9oVp6D): o atendente ou loja não receberão clientes durante o período. 
 
-![horario_suitshare_1](https://images.ctfassets.net/alneenqid6w5/5SYhzGHjrNpxQbrJ93Op0b/388d8adf88bb0d50c43cccaa34bde610/horario_suitshare_1.png)
+![horario_suitshare_1](//images.ctfassets.net/alneenqid6w5/5SYhzGHjrNpxQbrJ93Op0b/388d8adf88bb0d50c43cccaa34bde610/horario_suitshare_1.png)
 
 <div class="alert alert-warning">
   <p><b>Nota</b>: Para configurar o horário de atendimento você deve ter organizado seu atendimento de forma seletiva, sequencial ou geolocalizado.</p>
@@ -32,13 +32,13 @@ Além de organizar e distribuir os atendimentos, você pode definir horários de
 
 Acesse o **link âncora** que irá distribuir os atendimentos. 
 
-![horario_suitshare_2](https://images.ctfassets.net/alneenqid6w5/1X3ZPHRxpt7z4KfnY9f7nn/e3e184e88340561d6df75955983ea705/horario_suitshare_2.png)
+![horario_suitshare_2](//images.ctfassets.net/alneenqid6w5/1X3ZPHRxpt7z4KfnY9f7nn/e3e184e88340561d6df75955983ea705/horario_suitshare_2.png)
 
 Defina o horário de atendimento clicando no **botão de relógio** localizado a frente do nome de cada um dos atendentes. 
 
-![horario_suitshare_3](https://images.ctfassets.net/alneenqid6w5/7376i6E6WK77Ic2yFQAB2L/39bb1a2795ff771b32c26e6dc7c7d4f3/horario_suitshare_3.png)
+![horario_suitshare_3](//images.ctfassets.net/alneenqid6w5/7376i6E6WK77Ic2yFQAB2L/39bb1a2795ff771b32c26e6dc7c7d4f3/horario_suitshare_3.png)
 
-![horario_suitshare_4](https://images.ctfassets.net/alneenqid6w5/4Wf7YIwXrwTE4InVBvoy4n/3a3961c1508758b73776cb7a071ab70a/horario_suitshare_4.png)
+![horario_suitshare_4](//images.ctfassets.net/alneenqid6w5/4Wf7YIwXrwTE4InVBvoy4n/3a3961c1508758b73776cb7a071ab70a/horario_suitshare_4.png)
 
 <div class="alert alert-danger">
   <p>A disponibilidade padrão de todos os atendentes está configurada para 24 horas. Dessa forma, qualquer modificação deve ser feita de forma individual.</p>
@@ -46,7 +46,7 @@ Defina o horário de atendimento clicando no **botão de relógio** localizado a
 
 Defina os dias disponíveis e horários de cada atendente. 
 
-![horario_suitshare_1](https://images.ctfassets.net/alneenqid6w5/7JZAm3Es0UcANnxWLFGX64/a6d41e127452b6b1f0cbb2e68810368c/horario_suitshare_gif.gif)
+![horario_suitshare_1](//images.ctfassets.net/alneenqid6w5/7JZAm3Es0UcANnxWLFGX64/a6d41e127452b6b1f0cbb2e68810368c/horario_suitshare_gif.gif)
 
 Clique no botão **Finalizar**. 
 
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
index d751be077..aabe9fd76 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
@@ -1,10 +1,10 @@
 ---
 title: 'Abrir chamados para o suporte financeiro da VTEX'
 id: 1ad3TguXzCSKq4yuYSK80c
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-04-04T13:58:56.872Z
-updatedAt: 2020-11-27T19:40:27.285Z
-publishedAt: 2020-03-09T18:09:31.386Z
+updatedAt: 2024-07-29T22:02:21.897Z
+publishedAt: 2024-07-29T22:02:21.897Z
 firstPublishedAt: 2018-04-04T19:53:34.588Z
 contentType: tutorial
 productTeam: Billing
@@ -35,16 +35,17 @@ Depois de se autenticar pelo método escolhido, você entra no painel de suporte
 
 Para abrir um chamado, basta clicar no botão __Enviar uma solicitação__.
 
-![chamado financeiro1 PT](https://images.ctfassets.net/alneenqid6w5/51uuDEcQzKOkoOUEImoGqO/c8df51e5c79445754b132ca7cef1c12c/chamado_financeiro1_PT.png)
+![chamado financeiro1 PT](//images.ctfassets.net/alneenqid6w5/51uuDEcQzKOkoOUEImoGqO/c8df51e5c79445754b132ca7cef1c12c/chamado_financeiro1_PT.png)
 
 Você será levado para o formulário de abertura de chamado, onde deve preencher:
 - Seu nome.
 - A conta VTEX à qual se refere o chamado (o formulário carrega uma lista com as contas às quais você tem acesso. Se não tiver acesso a nenhuma conta VTEX, você não consegue abrir chamados).
+- CNPJ.
 - Que sua dúvida é Financeira.
 - O assunto.
 - A descrição da pergunta ou do problema.
 
-![chamado financeiro2 PT](https://images.ctfassets.net/alneenqid6w5/7sG4rinPpeuMyMcYsQke0G/10dc27da30681e980219bab1bba1dc0a/chamado_financeiro2_PT.png)
+![chamado financeiro2 PT](//images.ctfassets.net/alneenqid6w5/7sG4rinPpeuMyMcYsQke0G/10dc27da30681e980219bab1bba1dc0a/chamado_financeiro2_PT.png)
 
 Você pode também incluir anexos, como capturas de telas ou gifs animados que ajudem a descrever o contexto da sua solicitação.
 
@@ -84,7 +85,7 @@ Clicando em __Minhas solicitações__, você vê o histórico de chamados aberto
 
 Se clicar em __Todas as solicitações__, você pode ver o histórico de chamados abertos por quaisquer funcionários da sua loja.
 
-![chamado financeiro3 PT](https://images.ctfassets.net/alneenqid6w5/5rFH6THjZSeC2282OGcO0/575bdab938687e35d787bb41e618fee3/chamado_financeiro3_PT.png)
+![chamado financeiro3 PT](//images.ctfassets.net/alneenqid6w5/5rFH6THjZSeC2282OGcO0/575bdab938687e35d787bb41e618fee3/chamado_financeiro3_PT.png)
 
 ## Os status dos chamados
 
@@ -99,4 +100,4 @@ Depois disso, ele passa pelos status `Aguardando resposta`, `Resolvido` e `Fecha
 
 No seu painel de suporte, você pode filtrar a busca de chamados por status. Para isso, basta usar a caixa de seleção abaixo do botão de envio de solicitação.
 
-![chamado financeiro4 PT](https://images.ctfassets.net/alneenqid6w5/66WicNamPYmIWuKGo2ICSC/f45496c0f278e4382098908fcc1ae872/chamado_financeiro4_PT.png)
+![chamado financeiro4 PT](//images.ctfassets.net/alneenqid6w5/66WicNamPYmIWuKGo2ICSC/f45496c0f278e4382098908fcc1ae872/chamado_financeiro4_PT.png)
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support.md b/docs/tutorials/pt/opening-tickets-to-vtex-support.md
index cb407c7c6..e931554a9 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support.md
@@ -1,10 +1,10 @@
 ---
 title: 'Abrir chamados para o suporte VTEX'
 id: 16yOEqpO32UQYygSmMSSAM
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-11-21T22:18:13.507Z
-updatedAt: 2022-12-16T19:09:29.363Z
-publishedAt: 2022-05-31T21:10:30.601Z
+updatedAt: 2023-12-01T18:51:22.803Z
+publishedAt: 2023-12-01T18:51:22.803Z
 firstPublishedAt: 2017-11-22T02:37:19.330Z
 contentType: tutorial
 productTeam: Others
@@ -17,9 +17,9 @@ subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 
 Todos os clientes têm acesso a atendimento fornecido pelo time de especialistas do [Suporte VTEX](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe). Os especialistas estão preparados para proporcionar a melhor experiência possível para a solução dos chamados. Para contatá-los, é necessário abrir um chamado por meio do sistema de tickets.
 
-Este artigo explica como clientes devem abrir chamados no Suporte VTEX e acompanhar o status dos chamados. Para saber mais sobre disponibilidade, tempo estimado de resposta (SLA) e recursos disponíveis para clientes no Brasil, leia o artigo [Suporte VTEX - Brasil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9).
+<div class="alert alert-info">É necessário <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">habilitar a autorização de suporte</a> no <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">License Manager</a> para que o usuário tenha acesso ao Suporte da VTEX. Esta configuração é válida apenas para contas no Brasil.</div>
 
-![DALL-E 3D aesthetic rendering of one male and two female coders typing on a computer pink background](https://images.ctfassets.net/alneenqid6w5/7r6SOrCUNRVbiiVFklLy6w/08a19a4f7191a1abff66f8690eb9bda4/DALL__E_2022-12-16_15.33.39_-_3D_aesthetic_rendering_of_one_male_and_two_female_coders_typing_on_a_computer_pink_background.png)
+Este artigo explica como clientes devem abrir chamados no Suporte VTEX e acompanhar o status dos chamados. Para saber mais sobre disponibilidade, tempo estimado de resposta (SLA) e recursos disponíveis para clientes no Brasil, leia o artigo [Suporte VTEX - Brasil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9).
 
 Ele está dividido nas etapas a seguir:
 
@@ -67,7 +67,7 @@ Ao selecionar essa opção de suporte, você precisa preencher as informações
    * *Tenho uma dúvida e gostaria de fazer uma pergunta*
    * *Gostaria de solicitar uma configuração*
 2. No campo **Assunto da solicitação**, preencha com informações relacionadas ao tipo de problema que você precisa de ajuda. Baseada na descrição do seu problema, iremos indicar alguns artigos do [Help Center](https://help.vtex.com/pt/) que podem ajudar a solucionar seu problema. Caso você entenda que nenhum artigo pode ajudar a resolver o problema, siga para o próximo passo.
-![https help.vtex.com pt support](https://images.ctfassets.net/alneenqid6w5/1R5JgnPNiJWbG8IDU0MQmm/ae29e8a323aae90c3e6cb11b36baed8d/https___help.vtex.com_pt_support.gif)
+![https help.vtex.com pt support](//images.ctfassets.net/alneenqid6w5/1R5JgnPNiJWbG8IDU0MQmm/ae29e8a323aae90c3e6cb11b36baed8d/https___help.vtex.com_pt_support.gif)
 3. Clique no botão `Continuar`.
 Você será direcionado para outra página.
 4. No campo **Impacto do problema**, selecione a opção que melhor corresponde ao impacto do problema:
@@ -141,4 +141,4 @@ Os status possíveis de um chamado são:
 - __Resolvido__: chamado que foi solucionado pelo agente do suporte ou pelo próprio cliente. Após o chamado ser resolvido, o cliente tem 27 horas úteis para reabrir o chamado respondendo o e-mail do Suporte ou entrando no Histórico de solicitações. Caso não o faça, o chamado será fechado.
 - __Fechado__: chamado marcado como Resolvido e, por não ter recebido nova interação após 27 horas úteis, foi automaticamente fechado. Não pode ser reaberto.
 
-Depois que os chamados são resolvidos, a equipe de suporte envia um email para o usuário com o link para uma [Pesquisa de Satisfação](https://help.vtex.com/pt/announcements/avalie-o-atendimento-da-vtex-pelo-seu-admin--7rSJLgGbtRw2GhjTJezkJf). Através dela, é possível avaliar o atendimento do nosso suporte sem sair do ambiente VTEX e nos ajudar a melhorar nossa experiência.
+Depois que os chamados são resolvidos, a equipe de suporte envia um email para o usuário com o link para uma [Pesquisa de Satisfação](https://help.vtex.com/pt/announcements/avalie-o-atendimento-da-vtex-pelo-seu-admin--7rSJLgGbtRw2GhjTJezkJf). Através dela, é possível avaliar o atendimento do nosso suporte sem sair do ambiente VTEX e nos ajudar a melhorar nossa experiência. 
diff --git a/docs/tutorials/pt/operational-capacity-beta.md b/docs/tutorials/pt/operational-capacity-beta.md
new file mode 100644
index 000000000..fb9ecd28b
--- /dev/null
+++ b/docs/tutorials/pt/operational-capacity-beta.md
@@ -0,0 +1,198 @@
+---
+title: 'Capacidade operacional (Beta)'
+id: 2thSYLMAS8KAd8V4XuBLSy
+status: PUBLISHED
+createdAt: 2023-05-08T18:03:07.644Z
+updatedAt: 2024-04-08T18:59:56.706Z
+publishedAt: 2024-04-08T18:59:56.706Z
+firstPublishedAt: 2023-05-09T17:22:57.861Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: capacidade-operacional-beta
+locale: pt
+legacySlug: modulo-localidades
+subcategory: 13sVE3TApOK1C8jMVLTJRh
+---
+
+<div class = "alert alert-info">
+Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a <b>Capacidade operacional (Beta)</b>, preencha o <a href="https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform">formulário de contato</a>. O requisito para usar a funcionalidade é ter <a href="https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl">contas franquia</a> associadas à <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-conta-na-vtex">conta principal</a>.
+</div>
+
+O módulo **Capacidade operacional** permite que você gerencie a capacidade dos sellers de receberem e prepararem os pedidos da loja, de forma a otimizar sua malha logística. Você acompanha a distribuição de pedidos entre os sellers e pode realizar [ações](#acoes-na-pagina-de-detalhes-do-seller) para melhorar a distribuição dos pedidos entre eles. 
+
+O bom gerenciamento da capacidade operacional dos sellers traz os seguintes benefícios: 
+
+* Redistribui melhor a demanda de produtos entre estoques de diferentes sellers.
+* Otimiza o tempo de envio de pedidos, pois evita a sobrecarga de sellers.
+* Melhora a experiência de compra dos clientes, que recebem seus pedidos nos prazos prometidos.
+
+Ao acessar no Admin VTEX **Envio > Capacidade operacional**, você encontra uma página como a imagem abaixo:
+
+![operational_capacity_image1_PT](//images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/750c0ac19cbb24293a58ccadeb4604b8/operational_capacity_image1_PT.png)
+
+<div class="alert alert-warning">
+Os sellers que aparecem na interface são os sellers da sua operação, e eles são previamente configurados pela nossa equipe. Para acrescentar um novo seller, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
+</div>
+
+O gráfico apresenta os dados abaixo:
+
+* **Total de sellers:** quantidade total de sellers da sua operação.
+* **Ativos:** quantidade de sellers que estão recebendo novos pedidos. 
+* **Pausados:** quantidade de sellers que foram pausados e não estão recebendo novos pedidos. 
+* **Quantidade de sellers que ultrapassaram a capacidade:** número de sellers que recebeu mais pedidos do que o limite configurado. Você pode escolher visualizar resultados dos últimos `7 dias` ou `28 dias`.
+
+A página **Capacidade operacional** apresenta as seguintes informações:
+
+| **Coluna** | **Descrição** |
+|:---:|:---|
+| Nome | Identificação do [seller](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) a que se refere a capacidade operacional. |
+| Capacidade utilizada | <p>Porcentagem da capacidade operacional que foi utilizada no dia.</p><p><b>Exemplo:</b> um seller com capacidade para preparar 100 pedidos está com 80% de sua capacidade do dia utilizada. Portanto, ele só pode receber 20 novos pedidos naquele dia.</p><p>Nesta coluna, aparece um ícone de alerta quando 100% da capacidade do seller é atingida e ele não pode receber novos pedidos no dia.</p><p>Você pode <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#editar-capacidade-operacional-do-seller">editar a capacidade operacional dos sellers</a> de forma individual ou massiva, como será visto em Editar capacidade operacional do seller.</p> |
+| Status | <p>Status da capacidade operacional do seller, que pode ser de dois tipos:</p><p><ul><li><i class="fas fa-toggle-on" aria-hidden="true"></i> <b>Ativo:</b> o toggle está acionado e o seller pode receber novos pedidos.</li><li><i class="fas fa-toggle-off"></i> <b>Pausado:</b> o toggle está desativado e o seller não pode receber novos pedidos.</li></p><p>Para escolher quando pausar um seller, veja a seção <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#escolher-entre-pausar-ou-aumentar-a-capacidade-operacional">Escolher entre pausar ou aumentar a capacidade operacional</a>.</p> |
+
+Quando você clica em um seller, você é redirecionado para a [página de detalhes do seller](#acoes-na-pagina-de-detalhes-do-seller), que será visto adiante.
+
+## Ações em Capacidade operacional
+
+No Admin VTEX, na página **Envio > Capacidade operacional**, você pode realizar as seguintes ações:
+
+* [Buscar seller](#buscar-seller)
+* [Filtrar sellers](#filtrar-sellers)
+* [Ativar e pausar capacidade operacional de sellers](#ativar-e-pausar-capacidade-operacional-de-sellers)
+* [Editar unidade da capacidade operacional do seller](#editar-unidade-da-capacidade-operacional-do-seller)
+
+### Buscar seller
+
+Utilizando a barra de busca, você pode usar o nome do seller para encontrá-lo.
+
+<div class = "alert alert-info">
+É possível associar a busca de sellers com o <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtrar-sellers">filtro por status</a>. Caso os resultados da sua busca retornem vazios, observe se não há um filtro ativo.
+</div>
+
+### Filtrar sellers
+
+Você pode filtrar por status os sellers que aparecem na listagem, clicando em `Status` e selecionando `Ativos` ou `Pausados`. Em seguida, clique em `Aplicar`.
+
+Para limpar os filtros aplicados, clique em **Status > Limpar**.
+
+### Ativar e pausar capacidade operacional de sellers
+
+Um seller vai estar com status <i class="fas fa-toggle-on"></i> `Ativo` se o toggle estiver habilitado e <i class="fas fa-toggle-off"></i> `Pausado` se o toggle estiver desabilitado. Para alterar o status da capacidade operacional de um único seller, clique sobre o toggle da sua linha correspondente e confirme a operação clicando em `Pausar`/`Ativar`.
+
+Para ativar ou pausar a capacidade operacional de vários sellers, realize os seguintes passos:
+
+1. No Admin VTEX, acesse **Envio > Capacidade operacional**, ou digite **Capacidade operacional** na barra de busca no topo da página.
+2. Selecione os sellers desejados, clicando nas caixas de seleção ao lado dos nomes. É possível selecionar todos os sellers, clicando em uma caixa de seleção e, em seguida, clicando em `Selecione todos`.
+3. Clique em `Mais ações`.
+4. Clique em `Ativar` ou `Pausar`, conforme desejado.
+5. Confirme clicando em `Ativar` ou `Pausar`, conforme desejado.
+
+### Editar unidade da capacidade operacional do seller
+
+A capacidade operacional do seller pode ser contabilizada em número de pedidos ou itens de pedidos. Para editar a capacidade operacional de um ou vários sellers, realize o passo a passo abaixo:
+
+1. No Admin VTEX, acesse **Envio > Capacidade operacional**, ou digite **Capacidade operacional** na barra de busca no topo da página.
+2. Selecione os sellers desejados, clicando nas caixas de seleção ao lado dos nomes. É possível selecionar todos os sellers, clicando em uma caixa de seleção e, em seguida, clicando em `Selecione todos`.
+3. Clique em `Editar capacidade`.
+4. Escolha a **Unidade da capacidade operacional**:
+    * **Quantidade de pedidos:** a capacidade operacional do seller será contada por número de pedidos.
+    * **Quantidade de itens:** a capacidade operacional do seller será contada por número de itens do pedido.
+5. Clique em `Salvar alterações`.
+
+<div class="alert alert-warning">
+A plataforma tem algumas restrições com relação a <a href="https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers abrangentes</a>, saiba mais na seção <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidade-operacional-de-seller-abrangente">Capacidade operacional de seller abrangente</a>.
+</div>
+
+## Ações na página de detalhes do seller
+
+No Admin VTEX, na página **Envio > Capacidade operacional**, ao clicar em um seller, você é redirecionado para sua página de detalhes e pode realizar as seguintes ações:
+
+* [Pausar e ativar capacidade operacional de seller](#pausar-e-ativar-capacidade-operacional-de-seller)
+* [Acompanhar capacidade utilizada](#acompanhar-capacidade-utilizada)
+* [Editar endereço associado ao seller](#editar-endereco-associado-ao-seller)
+* [Editar capacidade operacional do seller](#editar-capacidade-operacional-do-seller)
+
+### Pausar e ativar capacidade operacional de seller
+
+No topo direito da página de detalhes do seller, existe um toggle para ativar ou desativar sua capacidade operacional:
+
+* **Ativar:** habilite o toggle para `Ativo` e clique em `Ativar`.
+* **Desativar:** desabilite o toggle para `Pausado` e clique em `Pausar`.
+
+<div class="alert alert-warning">
+A plataforma tem algumas restrições com relação a <a href="https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers abrangentes</a>, saiba mais na seção <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidade-operacional-de-seller-abrangente">Capacidade operacional de seller abrangente</a>.
+</div>
+
+### Acompanhar capacidade utilizada
+
+O gráfico **Status da capacidade operacional** apresenta, em tempo real, a porcentagem da capacidade do seller que já foi consumida, como na imagem a seguir: 
+
+![operational_capacity_image2_PT](//images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/5a10fcf3a7fc20c4796a0bac0f14eeca/operational_capacity_image2_PT.png)
+
+O gráfico apresenta os seguintes períodos:
+
+* Hoje
+* Amanhã
+* Data dos próximos dois dias
+
+Se você configurar no seller a [regra](#iii-regra) _Continuar a receber pedidos consumindo a capacidade dos dias seguintes_, o gráfico vai apresentar a porcentagem da capacidade operacional dos dias seguintes que já foi consumida a partir de pedidos de dias anteriores. Saiba mais em [Editar capacidade operacional do seller](#editar-capacidade-operacional-do-seller).
+
+### Editar endereço associado ao seller
+
+Para editar o endereço ou o nome de identificação do seller na **Capacidade operacional**, siga os passos abaixo:
+
+1. Na seção **Informações básicas**, clique em `Editar informações básicas`.
+2. Altere as informações desejadas.
+3. Clique em `Salvar alterações`.
+
+### Editar capacidade operacional do seller
+
+Na seção **Capacidade operacional**, você visualiza as configurações atuais da capacidade operacional do seller para cada dia da semana, como na imagem abaixo:
+
+![operational_capacity_image3_PT](//images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/f8faca5d71b3729e9c5df67b5609753d/operational_capacity_image3_PT.png)
+
+Para alterar essas configurações, siga os passos abaixo:
+
+1. Na seção **Capacidade operacional**, clique em `Editar`.
+2. Altere as opções desejadas, são elas:
+    * [I - Unidade da capacidade operacional](#i-unidade-da-capacidade-operacional)
+    * [II - Capacidade](#ii-capacidade)
+    * [III - Regra](#iii-regra)
+3. Clique em `Salvar alterações`. 
+
+Veja a seguir as descrições dos campos mencionados no passo a passo.
+
+#### I - Unidade da capacidade operacional
+
+Escolha se a capacidade operacional será definida pelo número de _pedidos_ ou de _itens_. O número de itens considera os itens de todos os pedidos feitos no dia.
+
+#### II - Capacidade
+
+Determine qual o limite da capacidade operacional do seller para cada dia da semana. O sistema não restringe um valor máximo. 
+
+Quando o limite configurado é atingido, a sua loja continua recebendo novos pedidos, que podem ser distribuídos para outros sellers ou alocados para o mesmo seller, mas na capacidade nos próximos dias. Isso vai depender da regra que você escolher.
+
+#### III - Regra
+
+Escolha qual a regra para quando o seller atingir a capacidade máxima do dia:
+
+* **Continuar recebendo pedidos consumindo a capacidade dos dias seguintes:** o seller continua recebendo novos pedidos quando a capacidade é atingida, que são alocados na capacidade dos próximos dias, e a promessa de envio dos próximos pedidos é ajustada no checkout para os clientes. Não é possível configurar esse período em horas, porque ele vai corresponder automaticamente ao número de dias seguintes no qual foi alocado.
+  * Se você escolher esta regra, determine qual o número de dias seguintes para alocar os pedidos que ultrapassarem a capacidade do dia atual.
+  > **Exemplo:** um seller vende chocolates e sua capacidade operacional hoje foi 100% consumida. O seller continua recebendo novos pedidos, mas eles serão preparados só amanhã, porque o time não consegue preparar mais pedidos do que os já previstos para hoje. No checkout, as promessas de envio de novos pedidos agora aparecem com um dia a mais de prazo, pois os pedidos serão preparados amanhã. Se a capacidade de amanhã for consumida ainda hoje, os novos pedidos serão alocados para depois de amanhã e preparados dali a dois dias, porque a loja configurou três dias para Continuar recebendo pedidos consumindo a capacidade dos próximos dias.
+* **Desativar este seller até o final do dia:** uma vez que o seller atinja o limite da sua capacidade do dia, naquele mesmo dia ele deixa de receber novos pedidos, que são repassados para outros sellers.
+
+## Escolher entre pausar ou aumentar a capacidade operacional
+
+Para definir se a melhor estratégia para o seu negócio é [editar a capacidade operacional](#editar-capacidade-operacional-do-seller) de um seller ou [pausá-lo](#ativar-e-pausar-capacidade-operacional-de-sellers), é importante compreender o seguinte:
+
+* **Seller pausado:** o seller deixa de receber novos pedidos até ser reativado. Mesmo que a regra para _Continuar recebendo pedidos consumindo a capacidade dos próximos dias_ esteja configurada, novos pedidos não são aceitos.
+  > **Exemplo:** a loja do seller teve problemas nas instalações e o preparo de novos pedidos foi comprometido. Neste caso, é estratégico pausar o seller e reativá-lo somente quando os pedidos puderem ser preparados novamente.
+* **Seller atingiu limite máximo:** o seller com 100% da capacidade consumida deixa de receber novos pedidos naquele dia. Porém, no dia seguinte, sua capacidade operacional está liberada e ele automaticamente recebe novos pedidos. 
+  > **Exemplo:** na véspera do Natal, o seller atingiu o limite máximo da sua capacidade do dia e não conseguiria preparar mais pedidos, portanto não valeria [aumentar a capacidade operacional do seller](#editar-capacidade-operacional-do-seller). No dia seguinte, novos pedidos poderiam ser preparados, portanto seria preferível não editar o seller, que no dia seguinte já teria sua capacidade liberada e estaria recebendo novos pedidos.
+
+### Capacidade operacional de seller abrangente
+
+No site da sua loja, quando o cliente não informa sua localização, ele visualiza os produtos da sua loja (seller 1) e dos [sellers abrangentes](https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI).
+
+Devido a uma limitação da plataforma, quando você desativa a capacidade operacional de um seller abrangente, os produtos desse seller continuam aparecendo como disponíveis na vitrine, mas o cliente não consegue comprá-los. Desta forma, recomendamos que a capacidade operacional de sellers abrangentes seja sempre mantida ativada.
+
diff --git a/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
index f21734143..96c5dadaa 100644
--- a/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
@@ -53,7 +53,7 @@ Para desabilitar a função __Opções de entrega otimizadas__, siga os passos a
 3. No menu de opções azul localizado na parte superior da página, clique em __Checkout__.
 4. Em __Opções de entrega otimizadas__, clique no botão <i class="fas fa-toggle-off"></i> para desabilitar a opção __Otimizar exibição das opções de entrega__.
 
-![Opções de entrega otimizadas](https://images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/1101fc69a729d79465192bca2b331bfe/Op____es_de_entrega_otimizadas.PNG)
+![Opções de entrega otimizadas](//images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/1101fc69a729d79465192bca2b331bfe/Op____es_de_entrega_otimizadas.PNG)
 
 <ul>
   5. Clique em <b>Salvar</b>.
diff --git a/docs/tutorials/pt/order-allocation-algorithm-beta.md b/docs/tutorials/pt/order-allocation-algorithm-beta.md
index 8bb2d6874..54c11f689 100644
--- a/docs/tutorials/pt/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/pt/order-allocation-algorithm-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Order Allocation Algorithm (Beta)'
 id: 1zLCAyEdnVe3EsE9Kz88xA
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-07-12T23:39:25.008Z
-updatedAt: 2023-03-21T17:27:34.101Z
-publishedAt: 2023-03-21T17:27:34.101Z
+updatedAt: 2023-08-14T17:29:11.705Z
+publishedAt: 
 firstPublishedAt: 2022-07-12T23:51:23.186Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md b/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
index 74c3ec193..a7d39d59f 100644
--- a/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
@@ -3,8 +3,8 @@ title: 'Cancelamento de pedido solicitado pelo cliente'
 id: 3wEI6DUNtecooG2Ki4Akqo
 status: PUBLISHED
 createdAt: 2019-01-24T21:42:57.276Z
-updatedAt: 2023-04-28T00:40:54.949Z
-publishedAt: 2023-04-28T00:40:54.949Z
+updatedAt: 2024-04-01T15:51:58.098Z
+publishedAt: 2024-04-01T15:51:58.098Z
 firstPublishedAt: 2019-01-24T21:42:57.707Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -21,6 +21,10 @@ Existem cenários em que os clientes podem solicitar o cancelamento de um pedido
 Uma vez que o pedido é cancelado, não é mais possível alterar o status do pedido.
 </div>
 
+<div class = "alert alert-warning">
+Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
+</div>
+
 ## Cancelamento no prazo de carência
 
 Ocorre quando o cliente solicita cancelamento no [tempo carência](https://help.vtex.com/pt/tutorial/configurar-o-tempo-de-carencia-para-cancelamento-do-pedido--jYFdnPDtNm4WCEkYWqqC). O pedido é cancelado automaticamente, sem a necessidade de autorização da loja. Até esse momento, seguindo o [fluxo do pedido](https://help.vtex.com/pt/tutorial/fluxo-de-pedido--tutorials_196), o lojista ainda não tomou nenhuma ação em relação àquele pedido.
diff --git a/docs/tutorials/pt/order-details-page.md b/docs/tutorials/pt/order-details-page.md
index aadc8d525..2a24ba9d3 100644
--- a/docs/tutorials/pt/order-details-page.md
+++ b/docs/tutorials/pt/order-details-page.md
@@ -3,8 +3,8 @@ title: 'Página de detalhes do pedido'
 id: 2Y75n54Cc9VizrlG1N6ZNl
 status: PUBLISHED
 createdAt: 2020-12-28T15:51:29.428Z
-updatedAt: 2023-03-23T19:27:38.026Z
-publishedAt: 2023-03-23T19:27:38.026Z
+updatedAt: 2023-12-21T14:06:02.509Z
+publishedAt: 2023-12-21T14:06:02.509Z
 firstPublishedAt: 2020-12-28T19:33:51.059Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,9 +15,20 @@ legacySlug: pagina-de-detalhes-do-pedido-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-A página de **Detalhes do Pedido** permite visualizar todas as informações de um pedido e gerenciá-lo em um único lugar. Para visualizá-la, no Admin VTEX, acesse **Pedidos > [Todos os Pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi)**, e clique no pedido desejado. 
+<div class = "alert alert-info">
+É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
+</div>
+
+A página de **Detalhes do Pedido** permite visualizar todas as informações de um pedido e gerenciá-lo em um único lugar. Para visualizá-la, no Admin VTEX, acesse **Pedidos > [Todos os Pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi)**, e clique no pedido desejado.
+
+Você também pode buscar pedidos a partir de qualquer página no Admin VTEX usando a barra de busca global no topo da página. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
 
-Nesta página, você pode:
+Na página de detalhes do pedido, você pode:
 
 * Consultar em qual estágio o pedido está no fluxo de pedidos (status do pedido).
 * Acessar todo o histórico de mudanças e interações do pedido.
diff --git a/docs/tutorials/pt/order-errors-in-the-mercado-livre-integration.md b/docs/tutorials/pt/order-errors-in-the-mercado-livre-integration.md
index 348623b6b..b00ce4332 100644
--- a/docs/tutorials/pt/order-errors-in-the-mercado-livre-integration.md
+++ b/docs/tutorials/pt/order-errors-in-the-mercado-livre-integration.md
@@ -3,8 +3,8 @@ title: 'Erros de integração de pedidos do Mercado Livre'
 id: 4w4jAIWUy3OELgu3HFmGgh
 status: PUBLISHED
 createdAt: 2021-08-30T18:04:27.780Z
-updatedAt: 2023-03-29T23:44:08.721Z
-publishedAt: 2023-03-29T23:44:08.721Z
+updatedAt: 2023-08-04T18:43:32.189Z
+publishedAt: 2023-08-04T18:43:32.189Z
 firstPublishedAt: 2021-08-30T18:37:05.901Z
 contentType: tutorial
 productTeam: Channels
diff --git a/docs/tutorials/pt/order-flow-and-status.md b/docs/tutorials/pt/order-flow-and-status.md
index 6522f0068..b6c63f1df 100644
--- a/docs/tutorials/pt/order-flow-and-status.md
+++ b/docs/tutorials/pt/order-flow-and-status.md
@@ -3,8 +3,8 @@ title: 'Fluxo e status de pedidos'
 id: tutorials_196
 status: PUBLISHED
 createdAt: 2017-04-27T22:14:33.518Z
-updatedAt: 2023-02-28T16:04:19.511Z
-publishedAt: 2023-02-28T16:04:19.511Z
+updatedAt: 2024-04-01T15:37:30.788Z
+publishedAt: 2024-04-01T15:37:30.788Z
 firstPublishedAt: 2017-04-27T23:02:47.616Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -40,7 +40,7 @@ Para os casos de pedidos incompletos, confira o artigo <a href="https://help.vte
 
 ### Fluxo do marketplace
 
-![pedido_marketplace_pt](https://images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/7916b546cd4e92b0bdddf0e9f4a2ec11/pedido_marketplace_pt.png)
+![pedido_marketplace_pt](//images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/7916b546cd4e92b0bdddf0e9f4a2ec11/pedido_marketplace_pt.png)
 
 O fluxo do marketplace está integrado ao fluxo do seller. Quando um pedido que será entregue por um seller externo (não sendo o seller principal) é finalizado, o fluxo visto pelo marketplace é:
 
@@ -57,7 +57,7 @@ Para saber como identificar pedidos que são provenientes de marketplace, consul
 
 ### Fluxo do seller
 
-![pedido_fluxo_seller_pt](https://images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/23f611308f135cf4b591991934afac70/pedido_fluxo_seller_pt.png)
+![pedido_fluxo_seller_pt](//images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/23f611308f135cf4b591991934afac70/pedido_fluxo_seller_pt.png)
 
 Esse é o fluxo do pedido visto pela loja responsável pelo envio dos produtos que compõem o pedido. O pedido foi realizado através de outra loja (o marketplace), e o fluxo do seller é iniciado depois da confirmação do pedido.
 
@@ -95,7 +95,7 @@ Note que:
 
 ### Fluxo completo
 
-![pedido_fluxo_completo_pt](https://images.ctfassets.net/alneenqid6w5/5b57cGGmPatcg8TtS1UZvW/8ceb29cc95740b3c4d70574f8bf79ab3/pedido_fluxo_completo_pt.png)
+![pedido_fluxo_completo_pt](//images.ctfassets.net/alneenqid6w5/5b57cGGmPatcg8TtS1UZvW/8ceb29cc95740b3c4d70574f8bf79ab3/pedido_fluxo_completo_pt.png)
 
 O fluxo completo do pedido é visto pela loja que realiza a venda e entrega do pedido. Ele é composto pelo fluxo de marketplace e o fluxo do seller de forma sequencial.
 
@@ -121,7 +121,9 @@ O cancelamento de um pedido pode ser iniciado por diversos motivos. Para cada ti
 - **[Solicitação de cancelamento por parte do cliente](https://help.vtex.com/pt/tutorial/como-funciona-o-cancelamento-de-pedido-por-parte-do-cliente--3wEI6DUNtecooG2Ki4Akqo):** o cliente realiza o cancelamento durante a janela para cancelamento ou solicita o cancelamento para a loja. Quando o cancelamento ocorre dentro dessa período, os itens do pedido não são reservados. No entanto, se o cancelamento ocorrer após o manuseio do pedido (após o status `Iniciar manuseio`), os itens são reservados.
 - **[Cancelamento por parte da loja](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/4ts2ItvjYo8wm5gg76miS3):** quando o seller ou marketplace desiste da venda e cancela o pedido.
 
-Quando é feita a solicitação de cancelamento de um pedido, a plataforma processa automaticamente o cancelamento do pedido. O ressarcimento do pagamento ao cliente depende do estágio em que o pagamento está e do meio de pagamento utilizado. 
+Quando é feita a solicitação de cancelamento de um pedido, a plataforma processa automaticamente o cancelamento do pedido. O ressarcimento do pagamento ao cliente depende do estágio em que o pagamento está e do meio de pagamento utilizado.
+
+Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 <div class = "alert alert-info">
 Saiba mais sobre cancelamento e reembolso nos artigos <a href="https://help.vtex.com/pt/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente">Por que meu pedido cancelado foi cobrado na fatura do cliente</a>, <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento">Reembolso ou cancelamento</a>.
@@ -137,7 +139,7 @@ Para saber mais sobre cancelamento de pedidos, confira o artigo [Por que meu ped
 
 ### Fluxo chain
 
-![pedido_fluxo_chain_pt](https://images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/a6129ed22ec48b2506f108951ef6409d/pedido_fluxo_chain_pt.png)
+![pedido_fluxo_chain_pt](//images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/a6129ed22ec48b2506f108951ef6409d/pedido_fluxo_chain_pt.png)
 
 O fluxo de pedidos visto pela loja da camada intermediária de uma venda em[ Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) é semelhante ao fluxo de pedidos do marketplace, exceto pelo recebimento do pagamento de pedidos. No estágio de `Pagamento pendente`, ao invés do chain receber o pagamento diretamente do Gateway, o que ocorre é que o marketplace informa ao chain que recebeu a confirmação do pagamento. 
 
@@ -289,7 +291,7 @@ Observe que os status do fluxo completo do pedido (fluxo visto pelas lojas respo
     <td class="tg-zr06"><span style="font-weight:400">Autorizar despacho</span></td>
     <td class="tg-zr06"><span style="font-weight:400">authorize-fulfillment</span></td>
     <td class="tg-zr06"><span style="font-weight:400">Seller, fluxo completo</span></td>
-    <td class="tg-zr06"><span style="font-weight:400">Processo interno de liberação para manuseio. Aqui ocorre a</span> <a href="https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#reserva-confirmada"><span style="font-weight:400;color:#F71963;background-color:transparent">confirmação da reserva</span></a><span style="font-weight:400">.</span></td>
+    <td class="tg-zr06"><span style="font-weight:400">Processo interno de liberação para manuseio. Aqui ocorre a</span> <a href="https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#reserva-confirmada"><span style="font-weight:400;color:#F71963;background-color:transparent">confirmação da reserva</span></a><span style="font-weight:400">. Quando o marketplace não autoriza o seller a despachar o pedido em até 30 dias, o pedido é automaticamente cancelado pela plataforma.</span></td>
   </tr>
   <tr>
     <td class="tg-zr06"><span style="font-weight:400">Janela para cancelamento</span></td>
diff --git a/docs/tutorials/pt/order-replacement.md b/docs/tutorials/pt/order-replacement.md
index 25fa0adb8..3305f9e45 100644
--- a/docs/tutorials/pt/order-replacement.md
+++ b/docs/tutorials/pt/order-replacement.md
@@ -3,8 +3,8 @@ title: 'Substituição de pedidos'
 id: 2IK9mwQjBKseQmE8K8saO8
 status: PUBLISHED
 createdAt: 2018-02-20T19:29:21.502Z
-updatedAt: 2023-03-29T15:54:02.723Z
-publishedAt: 2023-03-29T15:54:02.723Z
+updatedAt: 2024-07-08T14:22:27.104Z
+publishedAt: 2024-07-08T14:22:27.104Z
 firstPublishedAt: 2018-02-20T20:24:08.083Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -37,7 +37,7 @@ Se a Substituição de pedidos for ativada em lojas que têm customização na p
 
 Para ativar a funcionalidade, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja > Pedidos > Configurações**, ou digite *Envio* na barra de busca no topo da página e selecione **Configurações da loja / Envio**.
+1. No Admin VTEX, acesse **Configurações da loja > Pedidos > Configurações**, ou digite *Pedidos* na barra de busca no topo da página e selecione **Configurações da loja / Pedidos**.
 2. Na aba **Gerais**, ao final da página, selecione o <a class="far fa-check-square"></a> em **Substituição do pedido**, ao lado de _Permitir que os clientes façam alterações em pedidos_.
 3. Clique em `Salvar`.
 
@@ -61,7 +61,7 @@ Os dados que podem ser alterados com a substituição de pedidos são:
 Não é possível realizar substituição de pedidos nos casos de:
 
 * [Pedidos incompletos](https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos--tutorials_294): quando o pedido não está com todas as informações completas para ser finalizado na plataforma.
-* Transação compartilhada: pedidos com mais de um seller e pagamento realizado para o marketplace.
+* Transação compartilhada: pedidos com um seller ou mais e pagamento realizado para o marketplace.
 * Pedidos já modificados pela loja.
 * Pedidos com os seguintes status:
     * Verificando nota fiscal
diff --git a/docs/tutorials/pt/order-report.md b/docs/tutorials/pt/order-report.md
index c77deaf0e..1de29b2e0 100644
--- a/docs/tutorials/pt/order-report.md
+++ b/docs/tutorials/pt/order-report.md
@@ -3,8 +3,8 @@ title: 'Relatório de pedidos'
 id: 31m1ewsmsEe0WS4So2aGMY
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:42.311Z
-updatedAt: 2023-05-31T15:43:26.524Z
-publishedAt: 2023-05-31T15:43:26.524Z
+updatedAt: 2024-03-01T01:28:57.258Z
+publishedAt: 2024-03-01T01:28:57.258Z
 firstPublishedAt: 2019-01-24T22:03:18.967Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -92,7 +92,7 @@ As colunas correspondem a uma informação específica sobre o pedido, conforme
 *   **Authorization ID**: ID da autorização.
 *   **TID**: [Transaction ID](https://app.contentful.com/pt/faq/como-achar-nsu-e-tid-do-pedido) do pedido.
 *   **NSU**: [Número sequencial único](https://app.contentful.com/pt/faq/como-achar-nsu-e-tid-do-pedido) do pedido.
-*    **Card First Digits**: seis primeiros dígitos do cartão usado na compra.
+*   **Card First Digits**: seis primeiros dígitos do cartão usado na compra.
 *   **Card Last Digits**: quatro últimos dígitos do cartão usado na compra.
 *   **Payment Approved By**: email da pessoa que aprovou o pagamento (aplicado quando a aprovação é feita manualmente).
 *   **Canceled By**: email do usuário que realizou o cancelamento do pedido.
@@ -114,7 +114,7 @@ As colunas correspondem a uma informação específica sobre o pedido, conforme
 *   **Taxes**: resultado da soma entre Tax e CustomTax, as taxas atribuídas ao SKU. Se ambos os valores não existirem, a coluna estará vazia.
 *   **Invoice Numbers**: número da nota fiscal do pedido.
 *   **Country**: país em que o pedido foi realizado.
-*   **Input Invoices Numbers**: números de nota fiscal do tipo Input, ou seja, referente a uma devolução.
-*   **Output Invoices Numbers**: números de nota fiscal do tipo Output, ou seja, referente a uma compra.
+*   **Input Invoices Numbers**: números de nota fiscal do tipo Output, ou seja, referente a uma compra.
+*   **Output Invoices Numbers**: números de nota fiscal do tipo Input, ou seja, referente a uma devolução.
 *   **Status raw value (temporary)**: o valor do status de um pedido sem nenhum tratamento específico, ou seja, o estado de um pedido como uma string não tratada. Por exemplo: o status de um pedido pode aparecer na interface como `Manuseando` e nesse campo estaria `handling`.
 *   **Cancellation Data**: motivo indicado pelo cliente final para o cancelamento do pedido, conforme apresentado no campo `Reason` do objeto `cancellationData` apresentado na [API de Orders](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/cancel). Caso o usuário não preencha esse campo no momento do cancelamento, essa coluna estará vazia no relatório.
diff --git a/docs/tutorials/pt/order-split-and-delivery-split.md b/docs/tutorials/pt/order-split-and-delivery-split.md
index af9a33867..cb60e608f 100644
--- a/docs/tutorials/pt/order-split-and-delivery-split.md
+++ b/docs/tutorials/pt/order-split-and-delivery-split.md
@@ -3,8 +3,8 @@ title: 'Divisão de pedidos e divisão de entregas'
 id: jQvzA6QgSd51e2p6bthoV
 status: PUBLISHED
 createdAt: 2021-09-27T21:06:59.520Z
-updatedAt: 2023-01-13T18:53:14.386Z
-publishedAt: 2023-01-13T18:53:14.386Z
+updatedAt: 2023-09-23T01:00:23.558Z
+publishedAt: 2023-09-23T01:00:23.558Z
 firstPublishedAt: 2021-09-27T21:12:55.418Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,7 +15,6 @@ legacySlug: divisao-de-pedidos-e-divisao-de-entregas
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-
 Na plataforma VTEX, há cenários em que o cliente final recebe seu pedido em diferentes pacotes. Este artigo apresenta uma visão geral sobre a **divisão de pacotes (ou divisão de entregas)** e a **divisão de pedidos**, além de indicar as configurações que podem ser realizadas por parte do lojista.
 
 Veja a seguir as principais diferenças entre os cenários de divisão de pedidos e divisão de pacotes.
@@ -57,4 +56,4 @@ O pedido é atendido por um único seller, mas é preciso realizar mais de uma e
   Não recomendamos operar a loja com o campo <code>allowMultipleDeliveries</code> indicado como <i>false</i>. Nesta configuração, quando existirem itens no carrinho que não possuam nenhum método de entrega do tipo delivery em comum, ou seja, os SLAIDs são distintos, e o carrinho tenha algum pickup-point, não será possível concluir o pedido.
 </div>
 
-* **Estoques distintos:** uma única loja oferece todos os itens de um pedido, mas estes estão em estoques diferentes. Então é preciso _dividir os pacotes de entrega,_ mas sem dividir o pedido entre lojas distintas. Isso é feito automaticamente pela plataforma.
+* **Docas distintas:** uma única loja oferece todos os itens de um pedido, mas no cálculo da rota de envio eles envolvem docas diferentes. Então é preciso _dividir os pacotes de entrega,_ mas sem dividir o pedido entre lojas distintas. Isso é feito automaticamente pela plataforma.
diff --git a/docs/tutorials/pt/order-to-delivery.md b/docs/tutorials/pt/order-to-delivery.md
index 76a4ae268..ec9d0e9cc 100644
--- a/docs/tutorials/pt/order-to-delivery.md
+++ b/docs/tutorials/pt/order-to-delivery.md
@@ -29,7 +29,7 @@ subcategory: 5SE2asHiQtHKfbnFru8RWH
 
 Você pode buscar por um pedido clicando no ícone da lupa 🔍. Você pode clicar em <i class="fas fa-ellipsis-v" alt="elipses"></i> para receber pedidos de outra origem ou gerar um relatório de pedidos.
 
-![Pedidos para entrega - PT](https://images.ctfassets.net/alneenqid6w5/6yMDBApwvfHclrY5DS3fVk/d1bad3ebb121029d42034109b5d9154e/Screenshot_2022-06-01_at_17-09-12_Figma.png)
+![Pedidos para entrega - PT](//images.ctfassets.net/alneenqid6w5/6yMDBApwvfHclrY5DS3fVk/d1bad3ebb121029d42034109b5d9154e/Screenshot_2022-06-01_at_17-09-12_Figma.png)
 
 As categorias de etapas do pedido são as seguintes: 
 
@@ -57,7 +57,7 @@ Cada pedido apresenta as seguintes informações:
 - Tipo de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 - Modalidade de entrega do pedido, como **Expressa** ou **Normal**.
 
-![Preparação - PT](https://images.ctfassets.net/alneenqid6w5/4gdmIBJfITnEIkYf68xDjk/c0fc7e138a6bf423b073ee78649b06d7/Screenshot_2022-06-01_at_17-24-04_Figma.png)
+![Preparação - PT](//images.ctfassets.net/alneenqid6w5/4gdmIBJfITnEIkYf68xDjk/c0fc7e138a6bf423b073ee78649b06d7/Screenshot_2022-06-01_at_17-24-04_Figma.png)
 
 ## Entrega em casa
 A etapa **Entrega em casa** exibe os pedidos que estão em fase de envio para a casa do cliente. Os pedidos são ordenados por prioridade de prazo, ou seja, o pedido com previsão de entrega mais próximo ou atrasado há mais tempo é o primeiro da lista.
@@ -71,7 +71,7 @@ Na aba **Pedidos** são exibidos os pedidos na etapa. Cada pedido apresenta as s
 - ID do pedido.
 - Status atual do pedido, podendo ser **Aguardando criação do envio**, **Aguardando transportadora** ou **Coletado pela transportadora**.
 
-![Entrega em casa - PT](https://images.ctfassets.net/alneenqid6w5/4C9M1TGP6cExmF6RICxOR6/090775ac0eacddb8ce7101db419a672e/Screenshot_2022-06-02_at_16-24-36_Figma.png)
+![Entrega em casa - PT](//images.ctfassets.net/alneenqid6w5/4C9M1TGP6cExmF6RICxOR6/090775ac0eacddb8ce7101db419a672e/Screenshot_2022-06-02_at_16-24-36_Figma.png)
 
 Na aba **Lotes de envio** são exibidas informações de cada envio feito pela loja. São apresentadas as seguintes informações:
 
@@ -79,13 +79,13 @@ Na aba **Lotes de envio** são exibidas informações de cada envio feito pela l
 - Número do lote de envio e nome da transportadora.
 - Status atual do envio, podendo ser **Aguardando transportadora**, **Coletado pela transportadora** ou **Concluído**.
 
-![Entrega em casa - lotes de envio -PT](https://images.ctfassets.net/alneenqid6w5/2o1qrINumd4BhrsKCX1YVy/8bd3d3ebb16e344e11a942be97b811b3/Entrega_em_casa_-_lotes_de_envio.png)
+![Entrega em casa - lotes de envio -PT](//images.ctfassets.net/alneenqid6w5/2o1qrINumd4BhrsKCX1YVy/8bd3d3ebb16e344e11a942be97b811b3/Entrega_em_casa_-_lotes_de_envio.png)
 
 Para criar um novo lote, clique em <i class="fas fa-plus"></i> `Criar lote de envio`.
 
 Ao selecionar um lote de envio será exibido uma tela com os detalhes de cada pedido relacionado a ele. Caso a transportadora responsável pelo envio não esteja integrada com a loja, será exibido um alerta, como na imagem abaixo.
 
-![Lote de envio - PT](https://images.ctfassets.net/alneenqid6w5/3dw9uaaJMdMPZQb6q5xqLN/d44731538f9e485360a5af9176812dc0/Screenshot_2022-06-02_at_16-31-42_Figma.png)
+![Lote de envio - PT](//images.ctfassets.net/alneenqid6w5/3dw9uaaJMdMPZQb6q5xqLN/d44731538f9e485360a5af9176812dc0/Screenshot_2022-06-02_at_16-31-42_Figma.png)
 
 Para confirmar o envio dos pedidos, siga os passos a seguir:
 
@@ -103,7 +103,7 @@ Ao clicar no ícone <i class="fas fa-ellipsis-v"></i> de um pedido, é possível
 
 Clicando em `Informações do envio`, será exibida uma tela com **Status**, **Transportadora**, **Pedidos neste envio** e **Data de criação**.
 
-![Informações do envio - PT](https://images.ctfassets.net/alneenqid6w5/132AGJoZVmHLM04lLEkB8B/383a20e3500a3147597af869f47576b9/Screenshot_2022-06-02_at_16-33-50_Figma.png)
+![Informações do envio - PT](//images.ctfassets.net/alneenqid6w5/132AGJoZVmHLM04lLEkB8B/383a20e3500a3147597af869f47576b9/Screenshot_2022-06-02_at_16-33-50_Figma.png)
 
 Caso a loja não apresente integração com transportadora, será preciso marcar manualmente os pedidos como Entregue quando eles forem entregues ao cliente. Caso exista a integração com a transportadora, os pedidos são marcados como entregues automaticamente.
 
@@ -118,7 +118,7 @@ Cada pedido apresenta as seguintes informações:
 - Em casos de atraso, é indicado quanto tempo a retirada do cliente está atrasada.
 - ID do pedido.
 
-![Retirada na loja - PT](https://images.ctfassets.net/alneenqid6w5/5dWy0rBy4GfEb2jVmS0MIE/256dedcced031fcf6717a6404a045a37/Screenshot_2022-06-02_at_16-36-07_Figma.png)
+![Retirada na loja - PT](//images.ctfassets.net/alneenqid6w5/5dWy0rBy4GfEb2jVmS0MIE/256dedcced031fcf6717a6404a045a37/Screenshot_2022-06-02_at_16-36-07_Figma.png)
 
 ## Recusados
 A etapa **Recusados** exibe os pedidos que foram cancelados pela loja por falta do item no estoque, produto com defeito, entre outros motivos. Os pedidos são ordenados por prioridade de prazo, ou seja, o pedido com previsão de entrega mais próximo ou atrasado há mais tempo é o primeiro da lista.
@@ -133,7 +133,7 @@ Cada pedido apresenta as seguintes informações:
 - Status atual do pedido, podendo ser **Cancelado** ou **Aguardando análise**.
 - Modalidade de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 
-![Recusados - PT](https://images.ctfassets.net/alneenqid6w5/6JOEUXqZsrD4Fl4PflbIeU/3295b747e4b5c12bf33d7efa8a5a72c1/Screenshot_2022-06-02_at_16-40-10_Figma.png)
+![Recusados - PT](//images.ctfassets.net/alneenqid6w5/6JOEUXqZsrD4Fl4PflbIeU/3295b747e4b5c12bf33d7efa8a5a72c1/Screenshot_2022-06-02_at_16-40-10_Figma.png)
 
 ## Devoluções
 A etapa **Devoluções** exibe os pedidos que foram devolvidos pelo cliente. Você pode buscar por um pedido clicando no ícone da lupa 🔍. Cada pedido apresenta as seguintes informações:
@@ -142,7 +142,7 @@ A etapa **Devoluções** exibe os pedidos que foram devolvidos pelo cliente. Voc
 - Data e horário de quando o pedido foi devolvido.
 - Modalidade de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 
-![Devoluções - PT](https://images.ctfassets.net/alneenqid6w5/sI6uA75Ms3LQHAkaCF1ts/0a0e7b5140d72fb78053f9a894fff0ff/Screenshot_2022-06-02_at_17-09-08_Figma.png)
+![Devoluções - PT](//images.ctfassets.net/alneenqid6w5/sI6uA75Ms3LQHAkaCF1ts/0a0e7b5140d72fb78053f9a894fff0ff/Screenshot_2022-06-02_at_17-09-08_Figma.png)
 
 ## Entregues
 A etapa Entregues exibe os pedidos que foram finalizados e entregues ao cliente. Você pode buscar por um pedido clicando no ícone da lupa 🔍. Cada pedido apresenta as seguintes informações:
@@ -151,4 +151,4 @@ A etapa Entregues exibe os pedidos que foram finalizados e entregues ao cliente.
 - Tipo de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 - Modalidade de entrega do pedido, como **Expressa** ou **Normal**.
 
-![Entregues - PT](https://images.ctfassets.net/alneenqid6w5/5GJhMUquRRYWAo9zRtZtst/62aaef737462a4f77cd37c025cdbbed5/Screenshot_2022-06-02_at_17-22-45_Figma.png)
+![Entregues - PT](//images.ctfassets.net/alneenqid6w5/5GJhMUquRRYWAo9zRtZtst/62aaef737462a4f77cd37c025cdbbed5/Screenshot_2022-06-02_at_17-22-45_Figma.png)
diff --git a/docs/tutorials/pt/order-transactional-email-templates.md b/docs/tutorials/pt/order-transactional-email-templates.md
index e78af4477..603f24e5d 100644
--- a/docs/tutorials/pt/order-transactional-email-templates.md
+++ b/docs/tutorials/pt/order-transactional-email-templates.md
@@ -3,8 +3,8 @@ title: 'Templates de emails transacionais referentes ao pedido'
 id: 3g2S2kqBOoSGcCaqMYK2my
 status: PUBLISHED
 createdAt: 2018-11-06T21:01:19.818Z
-updatedAt: 2023-02-28T01:10:27.048Z
-publishedAt: 2023-02-28T01:10:27.048Z
+updatedAt: 2024-03-01T01:15:49.954Z
+publishedAt: 2024-03-01T01:15:49.954Z
 firstPublishedAt: 2018-11-07T18:11:42.445Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -29,17 +29,17 @@ Para acessar os templates, siga os passos abaixo.
 
 | Template | Chave | Descrição | Gatilho |
 |-|-|-|-|
-| Order confirmation | vtexcommerce-new-order | Email enviado quando o pedido é concluído | Checkout cria um novo pedido |
-| Replace Order | vtexcommerce-replace-order | Email enviado quando o pedido é substituído com sucesso | Checkout cria um novo pedido e informa o __Gerenciamento de pedidos__ sobre a substituição |
-| Order change payment | vtexcommerce-order-change-payment | Notificação de forma de pagamento alterada | O cliente altera a forma de pagamento e o Checkout notifica o __Gerenciamento de pedidos__ sobre a alteração |
-| Payment pending | vtexcommerce-payment-pending | Notificação de pagamento pendente | O __Gerenciamento de pedidos__ envia o email 2 dias antes de o boleto expirar |
-| Payment approved | vtexcommerce-payment-approved | Notificação de pagamento aprovado | O status do pedido muda para __Pagamento Aprovado__ |
-| Change of information order | vtexcommerce-order-changed | Notificação de que o [pedido foi alterado](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) | O Checkout notifica um evento de alteração no pedido (desconto, adição de itens ou remoção de itens) |
-| Order invoiced | vtexcommerce-order-invoiced | Notificação de que o pedido foi faturado | O status do pedido muda para __Faturado__ |
-| Cancel billed request | vtexcommerce-order-invoiced-with-cancel-request | Notificação de que o pedido não pode ser cancelado após ser faturado | O Seller recusa um pedido de cancelamento quando o pedido está no status __Preparando Entrega__ |
-| Cancel shipped order | vtexcommerce-order-shipped-with-cancel-request | Notificação de que o pedido não pode ser cancelado após ser enviado | O Seller recusa um pedido de cancelamento quando o pedido já possui um número de rastreio ou uma URL de rastreio |
-| Order shipped | vtexcommerce-order-shipped | Notificação de que o pedido foi enviado | O pedido recebe uma nota fiscal e um número de rastreio ou uma URL de rastreio |
+| Order confirmation | vtexcommerce-new-order | Email enviado quando o pedido é concluído. | Checkout cria um novo pedido. |
+| Replace Order | vtexcommerce-replace-order | Email enviado quando o pedido é substituído com sucesso. | Checkout cria um novo pedido e informa o __Gerenciamento de pedidos__ sobre a substituição. |
+| Order change payment | vtexcommerce-order-change-payment | Notificação de forma de pagamento alterada. | O cliente altera a forma de pagamento e o Checkout notifica o __Gerenciamento de pedidos__ sobre a alteração. |
+| Payment pending | vtexcommerce-payment-pending | Notificação de pagamento pendente. | O __Gerenciamento de pedidos__ envia o email 48 horas após a finalização do pedido. |
+| Payment approved | vtexcommerce-payment-approved | Notificação de pagamento aprovado. | O status do pedido muda para __Pagamento Aprovado__. |
+| Change of information order | vtexcommerce-order-changed | Notificação de que o [pedido foi alterado](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190). | O Checkout notifica um evento de alteração no pedido (desconto, adição de itens ou remoção de itens). |
+| Order invoiced | vtexcommerce-order-invoiced | Notificação de que o pedido foi faturado. | O status do pedido muda para __Faturado__. |
+| Cancel billed request | vtexcommerce-order-invoiced-with-cancel-request | Notificação de que o pedido não pode ser cancelado após ser faturado. | O Seller recusa um pedido de cancelamento quando o pedido está no status __Preparando Entrega__. |
+| Cancel shipped order | vtexcommerce-order-shipped-with-cancel-request | Notificação de que o pedido não pode ser cancelado após ser enviado. | O Seller recusa um pedido de cancelamento quando o pedido já possui um número de rastreio ou uma URL de rastreio. |
+| Order shipped | vtexcommerce-order-shipped | Notificação de que o pedido foi enviado. | O pedido recebe uma nota fiscal e um número de rastreio ou uma URL de rastreio. Em caso de primeiro envio, será necessário preencher as duas informações: `trackingNumber` e `trackingURL`. |
 | Shipping Update | vtexcommerce-order-shipping-update | Notificação dos eventos da entrega, como "coletado pela transportadora" e "saiu para entrega", por exemplo. | O pedido precisa ter a nota fiscal, e um número de rastreio ou uma URL de rastreio vinculada à nota. Além disto, deve ter os eventos da entrega, que é a informação principal deste template. |
-| Order delivered | vtexcommerce-order-shipping-finished | Notificação de que a entrega foi realizada. O pedido precisa ter a nota fiscal, e um número de rastreio ou uma URL de rastreio vinculada à nota. | O Seller confirma a entrega do pedido. Essa ação muda o valor do campo `isDelivered` para `true` no json do pedido |
-| Order cancelled | vtexcommerce-order-cancelled | Notificação de cancelamento do pedido | Status do pedido muda para __Cancelado__ |
-| [Order Refund](https://help.vtex.com/pt/tutorial/template-de-e-mail-transacional-para-pedido-estornado--5uy6FCBb6DLyIJlSDeM10G) | vtexcommerce-order-refund | Notificação de estorno | O lojista insere o invoice com o valor estornado pela API [Order Invoice Notification](https://developers.vtex.com/reference/invoice#invoicenotification), com o campo `type` contendo o valor `input`. No Admin, esse evento é disparado quando se clica no botão  **Fazer devolução de itens**, na tela de detalhes do pedido |
+| Order delivered | vtexcommerce-order-shipping-finished | Notificação de que a entrega foi realizada. O pedido precisa ter a nota fiscal, e um número de rastreio ou uma URL de rastreio vinculada à nota. | O Seller confirma a entrega do pedido. Essa ação muda o valor do campo `isDelivered` para `true` no json do pedido. |
+| Order cancelled | vtexcommerce-order-cancelled | Notificação de cancelamento do pedido. | Status do pedido muda para __Cancelado__. |
+| [Order Refund](https://help.vtex.com/pt/tutorial/template-de-e-mail-transacional-para-pedido-estornado--5uy6FCBb6DLyIJlSDeM10G) | vtexcommerce-order-refund | Notificação de estorno. | O lojista insere o invoice com o valor estornado pela API [Order Invoice Notification](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice), com o campo `type` contendo o valor `input`. No Admin, esse evento é disparado quando se clica no botão  **Fazer devolução de itens**, na tela de detalhes do pedido. |
diff --git a/docs/tutorials/pt/orderform-settings.md b/docs/tutorials/pt/orderform-settings.md
new file mode 100644
index 000000000..44c5a10cc
--- /dev/null
+++ b/docs/tutorials/pt/orderform-settings.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurações do orderForm'
+id: 7EAqNk48KP2QHnCxu856jT
+status: DRAFT
+createdAt: 2024-06-18T13:34:07.902Z
+updatedAt: 2024-06-18T13:44:46.612Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Shopping
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configuracoes-do-orderform
+locale: pt
+legacySlug: configuracoes-do-orderform
+subcategory: 
+---
+
+# Configurações do orderForm
+
+Nas seções a seguir, apresentamos algumas configurações de segurança disponíveis no Checkout que podem ser habilitadas pelo endpoint [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
+
+### Exigir login ao fechar uma compra
+
+Declarar o campo `requiresLoginToPlaceOrder` como `true` possibilita que compras sejam efetuadas apenas por clientes que tenham passado pelo processo de autenticação. O cliente precisa estar logado, usando o mesmo endereço de email fornecido no momento em que os produtos foram adicionados ao carrinho de compras.
+
+Quando você optar por ativar este campo, o [SmartCheckout](https://help.vtex.com/pt/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB) será desabilitado para todos os clientes da loja.
+
+### Tempo mínimo entre pedidos
+
+Ao definir um valor numérico para o campo `minimumPurchaseDowntimeSeconds`, é possível determinar um tempo mínimo em segundos que um comprador deve aguardar antes de efetuar outra compra. Essa configuração impede que clientes criem múltiplos pedidos em um pequeno período de tempo.
+
+Recomendamos configurar esse campo para 90 segundos e utilizar esta configuração em conjunto com a [exigência de login para fechar uma compra](#exigir-login-ao-fechar-uma-compra).
+
+### Tempo mínimo de existência de um carrinho para permitir uso de um novo cartão de crédito
+
+A definição de um valor numérico no campo `cartAgeToUseNewCardSeconds` determina por quanto tempo em segundos um novo carrinho precisa existir antes que um novo cartão de crédito seja autorizado para uso nele.
+
+Essa configuração diminui a probabilidade da criação de múltiplos carrinhos e a adição de novos cartões de crédito. A ativação deste campo não afeta compras realizadas com cartões previamente salvos na conta do cliente.
+
+Recomendamos configurar este campo para 30 segundos.
diff --git a/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md b/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
index 261fa7acd..348e203eb 100644
--- a/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
+++ b/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
@@ -29,6 +29,6 @@ Entre as imagens do SKU, a principal será aquela definida no cadastro de imagen
 
 Veja, em nosso exemplo, que mesmo não sendo a primeira imagem cadastrada, a imagem definida como principal é aquela assumida na página de produto quando o cliente seleciona o SKU.
 
-![sku_imagem_principal pt ](https://images.ctfassets.net/alneenqid6w5/4ouTS09QkgCMoqSAomMa2O/b56de01d796e9c75736bf51a865ada18/Ex_1_pt.png)
+![sku_imagem_principal pt ](//images.ctfassets.net/alneenqid6w5/4ouTS09QkgCMoqSAomMa2O/b56de01d796e9c75736bf51a865ada18/Ex_1_pt.png)
 
 - Em caso de upload da planilha de imagens, a plataforma considera linha por linha. Logo, a primeira linha de um SKU será considerada a principal, e assim por diante.
diff --git a/docs/tutorials/pt/orders-list.md b/docs/tutorials/pt/orders-list.md
index 271ff7880..e5febd9e0 100644
--- a/docs/tutorials/pt/orders-list.md
+++ b/docs/tutorials/pt/orders-list.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 É através da lista de pedidos do Gerenciamento de Pedidos que o lojista pode acompanhar as compras concretizadas em sua loja. A listagem está disponível na primeira tela do módulo Gerenciamento de Pedidos.
 
-![todosospedidos.pt](https://images.ctfassets.net/alneenqid6w5/RIjd55ovorcC4L2gZ4aFQ/c1f8a9043d1da0e979348951bbbba1e7/todosospedidos.pt.png)
+![todosospedidos.pt](//images.ctfassets.net/alneenqid6w5/RIjd55ovorcC4L2gZ4aFQ/c1f8a9043d1da0e979348951bbbba1e7/todosospedidos.pt.png)
 
 Na visualização padrão são listados todos os pedidos da loja a partir do mais recente. É possível alterar a ordenação clicando no nome das colunas, assim como buscar ou filtrar os pedidos por dados específicos, e também exportar estes dados.
 
diff --git a/docs/tutorials/pt/orders-overview.md b/docs/tutorials/pt/orders-overview.md
index 640dd5421..95318b79c 100644
--- a/docs/tutorials/pt/orders-overview.md
+++ b/docs/tutorials/pt/orders-overview.md
@@ -3,8 +3,8 @@ title: 'Visão Geral Pedidos'
 id: tutorials_201
 status: PUBLISHED
 createdAt: 2017-04-27T22:13:42.525Z
-updatedAt: 2023-04-26T14:51:44.363Z
-publishedAt: 2023-04-26T14:51:44.363Z
+updatedAt: 2023-12-21T14:01:20.828Z
+publishedAt: 2023-12-21T14:01:20.828Z
 firstPublishedAt: 2017-04-27T23:03:03.051Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -29,6 +29,17 @@ A seção inclui as seguintes páginas:
 - [Transações](https://help.vtex.com/pt/tutorial/how-to-view-transactions-on-pci-gateway--tutorials_461) 
 - [Conciliação Bancária](https://help.vtex.com/pt/tutorial/bank-reconciliations--tutorials_453) 
 
+Além de pesquisar pedidos em **Pedidos > Todos os pedidos**, você pode buscar pedidos a partir de qualquer página no Admin VTEX usando a barra de busca global no topo da página. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
+
+<div class = "alert alert-info">
+É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
+</div>
+
 ## Assinaturas
 
 Na plataforma VTEX, você pode criar [assinaturas](https://help.vtex.com/pt/tutorial/how-subscriptions-work--frequentlyAskedQuestions_4453#), ou seja, oferecer aos seus clientes a possibilidade de fazer pedidos recorrentes de forma automática, segundo uma frequência estabelecida.
diff --git a/docs/tutorials/pt/orders.md b/docs/tutorials/pt/orders.md
new file mode 100644
index 000000000..20518720d
--- /dev/null
+++ b/docs/tutorials/pt/orders.md
@@ -0,0 +1,370 @@
+---
+title: 'Pedidos Data Pipeline (Beta)'
+id: 2f3GlRJ5L5IRGVIxOmzrFv
+status: PUBLISHED
+createdAt: 2024-02-02T17:58:53.962Z
+updatedAt: 2024-06-21T16:26:28.394Z
+publishedAt: 2024-06-21T16:26:28.394Z
+firstPublishedAt: 2024-05-27T19:26:59.238Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: pedidos-data-pipeline-beta
+locale: pt
+legacySlug: pedidos-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+O conjunto de dados de Pedidos é composto por duas tabelas principais: a `orders_historical` e a `orders_latest`, as tabelas incluem diversos campos `SUPER` englobando uma variedade de informações como itens adquiridos, detalhes de envio, vendedores envolvidos, pagamentos, entre outros.
+
+Devido à natureza de relação 1-para-N entre muitos desses campos `SUPER` e os pedidos, e à quantidade de informações contidas neles, implementamos tabelas auxiliares especializadas, como `orders_shipping` e `orders_items`, para facilitar a gestão desses dados.
+
+Para realizar análises, é comum realizar seleções diretas dentro desses campos `SUPER` no Redshift, destacando partes específicas que desejamos extrair como colunas. Alternativamente, também podemos realizar junções entre uma das tabelas principais (`orders` ou `latest`) e as tabelas auxiliares, utilizando `orderid` como chave de ligação. Esse método permite a extração eficiente de informações específicas, possibilitando uma análise detalhada dos pedidos e de seus componentes associados.  
+
+Nesta seção você encontra as seguintes informações:  
+
+- [Características dos dados de pedidos](#caracteristicas-dos-dados-de-pedidos)
+- [Tabela orders_latest](#tabela-orders_latest)
+- [Tabela orders_historical](#tabela-orders_historical)
+- [Tabela orders_totals](#tabela-orders_totals)
+- [Tabela orders_shipping](#tabela-orders_shipping)
+- [Tabela orders_sellers](#tabela-orders_sellers)
+- [Tabela orders_rateandbenefitsidentifiers](#tabela-orders_rateandbenefitsidentifiers)
+- [Tabela orders_payments](#tabela-orders_payments)
+- [Tabela orders_packages](#tabela-orders_packages)
+- [Tabela orders_items](#tabela-orders_items)
+- [Análise com dados de pedidos](#analises-com-dados-de-navegacao)
+- [Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados  
+
+| **Característica** | **Descrição** |
+|:---:|:---:|
+| **Origem do dado** | Os dados do conjunto de Pedidos, são originados do OMS (Order Management System). |
+| **Disponibilidade** | Os dados de Pedidos podem ser acessados através do relatório de Orders no Admin da VTEX e também por APIs de Orders. É importante ressaltar que os dados disponibilizados pela API podem não estar estruturados exatamente como neste conjunto de dados do Data Pipeline. |
+| **Histórico** | Os dados são mantidos por dois anos, a partir de 2022 para clientes que já utilizam a plataforma VTEX. |
+| **Menor intervalo de atualização possível** | Uma hora. |
+
+## Tabela orders_latest
+
+A tabela `orders_latest` armazena o status mais recente de cada pedido, incluindo detalhes como data de atualização, ID do pedido e informações do cliente. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único do pedido. |
+| hostname | character varying(16383) | Nome do host relacionado ao pedido. |
+| value | double precision | Valor total do pedido. |
+| totals | super | Detalhes agregados sobre os totais do pedido, como subtotal, impostos, descontos, etc. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido. |
+| items | super | Informações detalhadas sobre os itens do pedido. |
+| clientprofiledata_userprofileid | character varying(65535) | ID do perfil do usuário no sistema de gestão do cliente. |
+| shippingdata_address_city | character varying(65535) | Cidade de entrega do pedido. |
+| shippingdata_address_state | character varying(65535) | Estado de entrega do pedido. |
+| shippingdata_address_country | character varying(65535) | País de entrega do pedido. |
+| shippingdata_logisticsinfo | super | Informações logísticas sobre o envio do pedido. |
+| sellers | super | Dados sobre os vendedores envolvidos no pedido. |
+| storepreferencesdata_countrycode | character varying(65535) | Código do país da loja. |
+| storepreferencesdata_timezone | character varying(65535) | Fuso horário da loja. |
+| storepreferencesdata_currencycode | character varying(65535) | Código da moeda usada na loja. |
+| packages | super | Detalhes sobre as embalagens dos itens do pedido. |
+| origin | character varying(16383) | Origem do pedido. |
+| iscompleted | boolean | Indica se o pedido está completo. |
+| affiliateid | character varying(16383) | ID do afiliado associado ao pedido. |
+| status | character varying(16383) | Status atual do pedido. |
+| authorizeddate | timestamp with time zone | Data e hora da autorização do pedido. |
+| invoiceddate | timestamp with time zone | Data e hora da emissão da fatura do pedido. |
+| marketplaceorderid | character varying(16383) | ID do pedido no marketplace. |
+| marketplaceservicesendpoint | character varying(16383) | Endpoint de serviços do marketplace. |
+| lastchange | timestamp with time zone | Data e hora da última alteração no pedido. |
+| marketingdata_utmsource | character varying(65535) | Fonte UTM para fins de marketing. |
+| marketingdata_utmmedium | character varying(65535) | Meio UTM para fins de marketing. |
+| marketingdata_utmcampaign | character varying(65535) | Campanha UTM para fins de marketing. |
+| marketingdata_utmpartner | character varying(65535) | Parceiro UTM para fins de marketing. |
+| marketingdata_utmipage | character varying(65535) | Página UTM para fins de marketing. |
+| marketingdata_utmipart | character varying(65535) | Parte UTM para fins de marketing. |
+| marketingdata_utmicampaign | character varying(65535) | Campanha UTM alternativa para fins de marketing. |
+| marketingdata_coupon | character varying(65535) | Código de cupom de desconto aplicado ao pedido. |
+| marketingdata_marketingtags | super | Tags de marketing associadas ao pedido. |
+| marketplace_name | character varying(65535) | Nome do marketplace associado ao pedido. |
+| marketplace_iscertified | super | Indica se o marketplace é certificado. |
+| marketplace_baseurl | character varying(65535) | URL base do marketplace. |
+| contextdata_loggedin | super | Indica se o usuário estava logado durante a realização do pedido. |
+| contextdata_useragent | character varying(65535) | Agente do usuário usado durante a realização do pedido. |
+| contextdata_userid | character varying(65535) | ID do usuário que realizou o pedido. |
+| rateandbenefitsidentifiers | super | Identificadores de tarifas e benefícios aplicados ao pedido. |
+| transactions | super | Detalhes das transações financeiras do pedido. |
+| giftcards | super | Informações sobre cartões-presente usados no pedido. |
+| saleschannel | character varying(16383) | Canal de vendas pelo qual o pedido foi realizado. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados |
+| sellerorderid | character varying(16383) | ID do pedido atribuído pelo vendedor. |
+| ordergroup | character varying(16383) | Grupo de pedidos ao qual este pedido pertence. |
+| workflowisinerror | boolean | Indica se houve algum erro no fluxo de trabalho do pedido. |
+| clientprofiledata_email | character varying(256) | Email do perfil do cliente associado ao pedido. |
+| changesattachment_id | character varying(256) | ID do anexo de alterações do pedido. |
+| changesattachment_changesdata | super | Dados de alterações feitas no pedido. |
+| shippingdata_postal_code | character varying(256) | Código postal do endereço de entrega do pedido. |
+
+## Tabela orders_historical
+
+A tabela `orders_historical` armazena um registro completo de todas as atualizações dos pedidos. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido, normalmente utilizado como chave primária. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, indicando o servidor ou domínio que gerencia o pedido. |
+| value | double precision | Valor monetário total do pedido, possivelmente incluindo impostos, descontos e custos de envio. |
+| totals | super | Informações agregadas sobre os totais do pedido, possivelmente divididos em subtotais, impostos, descontos, etc. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| items | super | Informações detalhadas sobre os itens no pedido, potencialmente incluindo SKU, quantidade, preço e descontos específicos dos itens. |
+| clientprofiledata_userprofileid | character varying(65535) | Identificador do perfil do usuário do cliente que realizou o pedido. |
+| shippingdata_address_city | character varying(65535) | Parte da cidade do endereço de entrega do pedido. |
+| shippingdata_address_state | character varying(65535) | Parte do estado ou região do endereço de entrega do pedido. |
+| shippingdata_address_country | character varying(65535) | Parte do país do endereço de entrega do pedido. |
+| shippingdata_logisticsinfo | super | Informações logísticas relacionadas ao envio do pedido, possivelmente incluindo detalhes do transportador e informações de rastreamento. |
+| sellers | super | Informações sobre os vendedores envolvidos no pedido, que podem incluir IDs e nomes dos vendedores. |
+| storepreferencesdata_countrycode | character varying(65535) | Código do país da loja onde o pedido foi realizado. |
+| storepreferencesdata_timezone | character varying(65535) | Fuso horário da loja onde o pedido foi realizado. |
+| storepreferencesdata_currencycode | character varying(65535) | Código da moeda utilizada na transação do pedido. |
+| packages | super | Detalhes sobre a embalagem dos itens do pedido, que podem incluir tipos e dimensões da embalagem. |
+| origin | character varying(16383) | Origem do pedido, indicando onde ou como o pedido foi iniciado. |
+| iscompleted | boolean | Indica se o pedido foi completado. |
+| affiliateid | character varying(16383) | Identificador de um afiliado ou fonte de referência associada ao pedido. |
+| status | character varying(16383) | O status atual do pedido, como 'pendente', 'enviado' ou 'completado'. |
+| authorizeddate | timestamp with time zone | Data e hora em que o pedido foi autorizado. |
+| invoiceddate | timestamp with time zone | Data e hora em que a fatura do pedido foi emitida. |
+| marketplaceorderid | character varying(16383) | Identificador do pedido dentro de um marketplace, se aplicável. |
+| marketplaceservicesendpoint | character varying(16383) | Endpoint ou URL para serviços de marketplace relacionados ao pedido. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido. |
+| marketingdata_utmsource | character varying(65535) | Parâmetro UTM de fonte em dados de marketing, indicando a origem do tráfego ou campanha. |
+| marketingdata_utmmedium | character varying(65535) | Parâmetro UTM de meio em dados de marketing, indicando o meio da campanha (por exemplo, e-mail, social). |
+| marketingdata_utmcampaign | character varying(65535) | Parâmetro UTM de campanha em dados de marketing, especificando o nome ou código específico da campanha. |
+| marketingdata_utmpartner | character varying(65535) | Parâmetro UTM de parceiro, indicando uma parceria ou colaborador em esforços de marketing. |
+| marketingdata_utmipage | character varying(65535) | Parâmetro UTM de página, potencialmente indicando a página específica ou local da campanha. |
+| marketingdata_utmipart | character varying(65535) | Parâmetro UTM de parte, potencialmente indicando um componente ou seção específica da campanha de marketing. |
+| marketingdata_utmicampaign | character varying(65535) | Parâmetro UTM de campanha alternativo para acompanhamento adicional da campanha. |
+| marketingdata_coupon | character varying(65535) | Código de cupom usado, se houver, para descontos no pedido. |
+| marketingdata_marketingtags | super | Tags ou palavras-chave associadas aos esforços de marketing do pedido. |
+| marketplace_name | character varying(65535) | Nome do marketplace onde o pedido foi realizado, se aplicável. |
+| marketplace_iscertified | super | Indica se o marketplace onde o pedido foi realizado é certificado ou reconhecido. |
+| marketplace_baseurl | character varying(65535) | URL base do marketplace onde o pedido foi realizado. |
+| contextdata_loggedin | super | Indica se o usuário estava logado ao realizar o pedido. |
+| contextdata_useragent | character varying(65535) | String do agente do usuário do navegador ou dispositivo usado ao realizar o pedido. |
+| contextdata_userid | character varying(65535) | ID do usuário que realizou o pedido. |
+| rateandbenefitsidentifiers | super | Identificadores de tarifas e benefícios aplicados ao pedido, como pontos de fidelidade ou descontos de associados. |
+| transactions | super | Informações detalhadas sobre as transações financeiras associadas ao pedido. |
+| giftcards | super | Informações sobre quaisquer cartões-presente usados no pedido. |
+| saleschannel | character varying(16383) | Canal de vendas pelo qual o pedido foi realizado, por exemplo, loja online, loja física. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados |
+| sellerorderid | character varying(16383) | Um ID de pedido atribuído pelo vendedor, diferente do ID principal do pedido. |
+| ordergroup | character varying(16383) | O grupo de pedidos ao qual este pedido pertence, usado para agrupar vários pedidos juntos. |
+| workflowisinerror | boolean | Indica se houve um erro no fluxo de trabalho de processamento do pedido. |
+| clientprofiledata_email | character varying(256) | O endereço de e-mail do cliente associado ao pedido. |
+| changesattachment_id | character varying(256) | Identificador único para uma operação de alteração associada ao pedido. |
+| changesattachment_changesdata | super | Detalhes sobre alterações feitas no pedido, como adições de itens, remoções ou modificações. |
+| shippingdata_postal_code | character varying(256) | O código postal do endereço de entrega do pedido. |
+
+## Tabela orders_totals
+
+A tabela `orders_totals` fornece um resumo dos valores totais associados a cada pedido, incluindo valor total do pedido, descontos aplicados, e impostos. Veja a seguir os campos que compõem essa tabela.  
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. Comumente unido com a coluna `orderid` da tabela `vtex.orders_latest` para análises cruzadas. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, indicando o servidor ou domínio que gerencia o pedido. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido, refletindo a mais recente atualização de status ou conteúdo. |
+| status | character varying(16383) | Status atual do pedido. Frequentemente unido com a coluna `status` da tabela `vtex.orders_latest` para rastrear mudanças de status. |
+| totals_id | character varying(65535) | Identificador único para os totais do pedido, usado para referenciar detalhes específicos do total do pedido. |
+| totals_name | character varying(65535) | Nome ou descrição dos totais do pedido, oferecendo uma visão geral do que o total representa (por exemplo, subtotal, impostos, descontos). |
+| totals_value | double precision | Valor numérico associado aos totais do pedido, como o valor total, subtotal, impostos, descontos, etc. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados |
+
+## Tabela orders_shipping
+
+A tabela de `orders_shipping` detalha as informações de envio de pedidos, como endereço de entrega, custos de envio e prestadores de serviços logísticos. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. |
+| hostname | character varying(16383) | Nome do host associado ao pedido. Frequentemente unido com `hostname` da tabela `vtex.client_registry_gold`. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração no pedido. |
+| status | character varying(16383) | Status atual do pedido. |
+| shippingdata_address_city | character varying(65535) | Cidade no endereço de entrega do pedido. |
+| shippingdata_address_state | character varying(65535) | Estado no endereço de entrega do pedido. |
+| shippingdata_address_country | character varying(65535) | País no endereço de entrega do pedido. |
+| deliveryids | super | Identificadores associados à entrega do pedido. |
+| shippingestimate | character varying(65535) | Estimativa do tempo de envio do pedido. |
+| pickupstoreinfo_ispickupstore | boolean | Indica se o local de retirada é uma loja física. |
+| pickupstoreinfo_friendlyname | character varying(65535) | Nome amigável do local de retirada. |
+| pickupstoreinfo_dockid | character varying(65535) | Identificador do local de retirada. |
+| deliverychannel | character varying(65535) | Canal de entrega utilizado para o pedido. |
+| deliverywindow | character varying(65535) | Janela de tempo estimada para a entrega. |
+| sellingprice | double precision | Preço de venda do item no pedido. |
+| listprice | double precision | Preço de lista do item no pedido. |
+| price | double precision | Preço final do item no pedido. |
+| shippingestimatedate | timestamp with time zone | Data estimada para o envio do pedido. |
+| selecteddeliverychannel | character varying(65535) | Canal de entrega selecionado para o pedido. |
+| selectedsla | character varying(65535) | Acordo de nível de serviço (SLA) selecionado para o pedido. |
+| deliverychannels | super | Canais de entrega disponíveis para o pedido. |
+| slas | super | SLAs disponíveis para o pedido. |
+| pickupdistance | double precision | Distância para o local de retirada do pedido. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados. |
+| shippingdata_postal_code | character varying(256) | Código postal no endereço de entrega do pedido. |
+
+## Tabela orders_sellers
+
+A tabela de `orders_sellers` armazena a lista dos vendedores envolvidos em cada pedido. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. Frequentemente unido com a coluna `orderid` da tabela `vtex.orders_historical` para análises cruzadas. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, indicando o servidor ou domínio que gerencia o pedido. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido, refletindo a mais recente atualização de status ou conteúdo. |
+| status | character varying(16383) | Status atual do pedido. |
+| id | character varying(65535) | Identificador único, geralmente usado para referenciar um elemento específico dentro de um contexto maior. |
+| name | character varying(65535) | Nome ou título do elemento referenciado, fornecendo uma identificação legível por humanos. |
+| logo | character varying(65535) | Caminho ou URL para o logotipo associado, frequentemente usado em contextos de branding ou identificação visual. |
+| fulfillmentendpoint | character varying(65535) | Endpoint ou URL para serviços de fulfillment, indicando onde as operações de cumprimento de pedidos são gerenciadas. |
+| subsellerid | character varying(65535) | Identificador para um subseller ou vendedor secundário associado ao pedido ou operação. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados. |
+
+## Tabela orders_rateandbenefitsidentifiers
+
+A tabela de `orders_rateandbenefitsidentifiers` contém dados sobre promoções e benefícios aplicados aos pedidos. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, indicando o servidor ou domínio que gerencia o pedido. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido, refletindo a mais recente atualização de status ou conteúdo. |
+| status | character varying(16383) | Status atual do pedido. |
+| rateandbenefitsidentifiers_id | character varying(65535) | Identificador único para os identificadores de taxas e benefícios associados ao pedido. |
+| rateandbenefitsidentifiers_name | character varying(65535) | Nome ou título dos identificadores de taxas e benefícios, fornecendo uma identificação clara do benefício ou taxa. |
+| rateandbenefitsidentifiers_featured | boolean | Indica se os identificadores de taxas e benefícios são destacados ou têm uma característica especial. |
+| rateandbenefitsidentifiers_description | character varying(65535) | Descrição detalhada dos identificadores de taxas e benefícios, explicando seus recursos ou benefícios. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados. |
+
+## Tabela orders_payments
+
+A tabela de `orders_payments` registra detalhes dos métodos de pagamento utilizados. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. Frequentemente unido com a coluna `orderid` da tabela `vtex.orders_latest`. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, indicando o servidor ou domínio que gerencia o pedido. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido, refletindo a mais recente atualização de status ou conteúdo. |
+| status | character varying(16383) | Status atual do pedido. |
+| transactions_merchantname | character varying(65535) | Nome do comerciante associado à transação do pedido. |
+| group | character varying(65535) | Grupo ou categoria a que o pedido ou elemento pertence. |
+| installments | integer | Número de parcelas para o pagamento do pedido. |
+| value | double precision | Valor monetário associado à transação ou elemento do pedido. |
+| transactions_paymentsystemname | character varying(65535) | Nome do sistema de pagamento utilizado na transação. |
+| transactions_paymentsystem | character varying(65535) | Identificador do sistema de pagamento utilizado na transação. |
+| giftcards_id | character varying(65535) | Identificador único do cartão-presente utilizado no pedido. |
+| giftcards_name | character varying(65535) | Nome do cartão-presente utilizado. |
+| giftcards_caption | character varying(65535) | Descrição ou legenda do cartão-presente utilizado. |
+| giftcards_value | double precision | Valor monetário do cartão-presente. |
+| giftcards_balance | double precision | Saldo restante no cartão-presente após o uso. |
+| giftcards_provider | character varying(65535) | Provedor ou emissora do cartão-presente. |
+| giftcards_groupname | character varying(65535) | Nome do grupo ou categoria a que o cartão-presente pertence. |
+| giftcards_inuse | boolean | Indica se o cartão-presente está em uso ou foi utilizado no pedido. |
+| giftcards_isspecialcard | boolean | Indica se o cartão-presente é um tipo especial ou promocional. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados. |
+| transactions_transactionid | character varying(65535) | Identificador único da transação financeira associada ao pedido. |
+| transactions_referencevalue | double precision | Valor de referência da transação, possivelmente o valor total antes de descontos ou acréscimos. |
+
+## Tabela orders_packages
+
+A tabela de `orders_packages` armazena informações sobre a embalagem e expedição de produtos. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, indicando o servidor ou domínio que gerencia o pedido. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido, refletindo a mais recente atualização de status ou conteúdo. |
+| status | character varying(16383) | Status atual do pedido. |
+| courier | character varying(65535) | Nome da empresa de courier ou serviço de entrega associado ao pedido. |
+| invoicenumber | character varying(65535) | Número da fatura associada ao pedido. |
+| invoicevalue | double precision | Valor total indicado na fatura do pedido. |
+| invoiceurl | character varying(65535) | URL para acessar a fatura eletrônica do pedido. |
+| issuancedate | timestamp with time zone | Data de emissão da fatura do pedido. |
+| trackingnumber | character varying(65535) | Número de rastreamento associado à entrega do pedido. |
+| invoicekey | character varying(65535) | Chave única identificadora da fatura do pedido. |
+| trackingurl | character varying(65535) | URL para rastreamento da entrega do pedido. |
+| embeddedinvoice | character varying(65535) | Informações incorporadas ou detalhes da fatura do pedido. |
+| type | character varying(65535) | Tipo ou categoria do elemento ou serviço associado ao pedido. |
+| courierstatus_delivereddate | timestamp with time zone | Data de entrega do pedido conforme registrado pelo serviço de courier. |
+| courierstatus_status | character varying(65535) | Status atual da entrega conforme registrado pelo serviço de courier. |
+| courierstatus_finished | boolean | Indica se o processo de entrega foi concluído. |
+| courierstatus_data | super | Dados detalhados sobre o status da entrega fornecidos pelo serviço de courier. |
+| cfop | character varying(65535) | Código Fiscal de Operações e Prestações associado à transação do pedido. |
+| packages_lastchange | timestamp with time zone | Data e hora da última alteração registrada nos pacotes do pedido. |
+| volumes | integer | Número total de volumes ou pacotes no pedido. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados. |
+
+## Tabela orders_items
+
+A tabela de `orders_items` armazena detalhes dos itens individuais em cada pedido, incluindo SKU, quantidade, preço e descontos. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| orderid | character varying(16383) | Identificador único para cada pedido. Comumente unido com a coluna `orderid` da tabela `vtex.orders_latest`. |
+| hostname | character varying(16383) | Nome do host associado ao pedido, frequentemente unido com colunas de outras tabelas como `vtex.client_registry_gold.hostname`. |
+| creationdate | timestamp with time zone | Data e hora de criação do pedido, incluindo o fuso horário. |
+| lastchange | timestamp with time zone | Data e hora da última alteração feita no pedido. |
+| status | character varying(16383) | Status atual do pedido. |
+| tax | double precision | Valor do imposto aplicado ao pedido. |
+| id | character varying(65535) | Identificador único, frequentemente unido com `sku_id` da tabela `vtex.fulfillment_simulations_ca_silver`. |
+| productid | character varying(65535) | Identificador do produto associado ao pedido. |
+| quantity | integer | Quantidade do produto no pedido. |
+| seller | character varying(65535) | Identificador ou nome do vendedor do produto. |
+| sellersku | character varying(65535) | SKU do produto conforme listado pelo vendedor. |
+| pricevaliduntil | timestamp with time zone | Data e hora até a qual o preço do produto é válido. |
+| name | character varying(65535) | Nome do produto. |
+| additionalinfo_brandname | character varying(65535) | Nome da marca do produto. |
+| additionalinfo_brandid | character varying(65535) | Identificador da marca do produto. |
+| additionalinfo_caregoriesid | character varying(65535) | Identificadores de categorias associadas ao produto. |
+| additionalinfo_dimension_cubicweight | double precision | Peso cúbico do produto para fins de envio. |
+| additionalinfo_dimension_height | double precision | Altura do produto. |
+| additionalinfo_dimension_length | double precision | Comprimento do produto. |
+| additionalinfo_dimension_weight | double precision | Peso do produto. |
+| additionalinfo_dimension_width | double precision | Largura do produto. |
+| price | double precision | Preço do produto. |
+| pricetags | super | Tags de preço associadas ao produto, possivelmente incluindo descontos e ofertas. |
+| sellingprice | double precision | Preço de venda do produto. |
+| listprice | double precision | Preço de lista do produto. |
+| imageurl | character varying(65535) | URL da imagem do produto. |
+| measurementunit | character varying(65535) | Unidade de medida do produto. |
+| unitmultiplier | double precision | Multiplicador de unidade para o produto, usado em cálculos de preço e quantidade. |
+| batch_id | character varying(13) | Identificador referente ao carregamento dos dados na tabela para controle de qualidade da ingestão de dados. |
+
+## Análise com dados de Pedidos  
+
+Os dados de Pedidos podem ser empregados nas seguintes análises:  
+
+**- Análise de vendas do ecommerce:** avaliar o volume de vendas, identificar produtos mais vendidos, analisar tendências sazonais e entender o comportamento do consumidor.  
+**- Análise de taxa de cancelamento de pedidos:** investigar as razões dos cancelamentos, identificar padrões relacionados a produtos específicos ou problemas logísticos, e desenvolver estratégias para reduzir as taxas de cancelamento.  
+**- Performance de SKU:** analisar a performance de SKUs individuais, entender a demanda do mercado, e fazer ajustes no inventário e estratégias de marketing.  
+
+## Correlações com outros dados
+
+O conjunto de dados de Pedidos possui correlações com os seguintes conjuntos do  ecossistema de dados da VTEX:
+
+**- Catálogo:** integração direta para entender como variações no catálogo impactam os pedidos. Por exemplo, mudanças nos SKUs ou descrições de produtos podem influenciar tendências de compra.  
+**- Navegação:** os dados de navegação podem ser correlacionados com os pedidos para analisar o comportamento do consumidor e a jornada de compra, ajudando a otimizar a experiência do usuário.  
+**- Promoções:** a interação com dados de promoções é crucial para avaliar a eficácia das campanhas promocionais nos volumes e tipos de pedidos.  
+**- Transações:** a análise conjunta com dados de transações pode revelar padrões de pagamento, preferências do consumidor e eficiência no processamento de pagamentos.
+
+### Conheça outros Conjuntos de dados
+
+- [Inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navegação](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagamentos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)   
+- [Preços](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promoção](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
+
diff --git a/docs/tutorials/pt/overview-of-b2b-orders-history.md b/docs/tutorials/pt/overview-of-b2b-orders-history.md
new file mode 100644
index 000000000..62580b9a7
--- /dev/null
+++ b/docs/tutorials/pt/overview-of-b2b-orders-history.md
@@ -0,0 +1,31 @@
+---
+title: 'Visão Geral do Histórico de Pedidos B2B'
+id: C2i93MZmjSrqhEx16YYuA
+status: PUBLISHED
+createdAt: 2024-07-26T13:17:45.094Z
+updatedAt: 2024-07-26T14:02:09.115Z
+publishedAt: 2024-07-26T14:02:09.115Z
+firstPublishedAt: 2024-07-26T14:02:09.115Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: visao-geral-do-historico-de-pedidos-b2b
+locale: pt
+legacySlug: visao-geral-do-historico-de-pedidos-b2b
+subcategory: 2LaAukjQB4QEbqSYdgjq7l
+---
+
+Em uma [operação B2B](https://help.vtex.com/pt/tutorial/b2b-visao-geral--5vb9SNXhX2bZnkpAh7ADdC), múltiplos usuários dentro de uma mesma organização realizam pedidos em nome da empresa. O aplicativo **Histórico de Pedidos B2B** foi desenvolvido para atender a essas necessidades específicas, permitindo que os usuários visualizem e gerenciem pedidos de forma integrada e colaborativa.
+
+## Funcionalidade
+O aplicativo Histórico de Pedidos B2B substitui a página de Pedidos padrão em [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) por uma versão adaptada para o cenário B2B. Essa personalização permite que os [usuários](https://help.vtex.com/pt/tutorial/gerenciamento-de-permissoes-no-b2b-suite--2PLR7mIFxgbmsGq84paLeA) logados de uma organização não apenas vejam seus próprios pedidos, mas também acessem pedidos feitos por outros membros da mesma organização ou centro de custo, desde que possuam as permissões adequadas.
+
+## Benefícios
+A visualização centralizada de pedidos é importante para:
+
+- Permitir que todos os membros autorizados da organização acompanhem os pedidos realizados, evitando duplicidades e erros.
+- Facilitar o gerenciamento de compras, garantindo que todas as aquisições estejam alinhadas com as políticas da empresa.
+- Proporcionar acesso rápido e fácil aos pedidos, melhorando a eficiência operacional e facilitando a tomada de decisão.
+
+Para mais informações, acesse [Histórico de pedidos B2B](https://developers.vtex.com/docs/apps/vtex.b2b-orders-history).
+
diff --git a/docs/tutorials/pt/overview-pricing-module.md b/docs/tutorials/pt/overview-pricing-module.md
index adb5dd28b..63265a92a 100644
--- a/docs/tutorials/pt/overview-pricing-module.md
+++ b/docs/tutorials/pt/overview-pricing-module.md
@@ -21,7 +21,7 @@ Existem quatro departamentos dentro do módulo que são responsáveis pela confi
 
 ## Audiência de campanhas 
 
-![campanha-pt](https://images.ctfassets.net/alneenqid6w5/2vEodWRzSkHWdujqLvOxmb/dcd29bb90a3ed684c38d276c07afe80e/campanha-pt.png)
+![campanha-pt](//images.ctfassets.net/alneenqid6w5/2vEodWRzSkHWdujqLvOxmb/dcd29bb90a3ed684c38d276c07afe80e/campanha-pt.png)
 
 Audiência de campanha é uma forma de definir o público alvo ao qual uma promoção poderá ser aplicada. Ou seja criar segmentos de clientes com base na definição de alguns critérios que serão elegíveis a uma determinada audiência de campanha e consequentemente a uma ou mais promoções. Uma audiências de campanhas pode ser associada a uma ou mais promoções de audiência de campanha.
 
@@ -29,7 +29,7 @@ Audiência de campanha é uma forma de definir o público alvo ao qual uma promo
 
 ## Promoções
 
-![promoções.pt](https://images.ctfassets.net/alneenqid6w5/6rXDxtSGLLmGlpBlooTQHk/8094b01bc8fab75b014a0da8cd0db0cf/promo____es.pt.png)
+![promoções.pt](//images.ctfassets.net/alneenqid6w5/6rXDxtSGLLmGlpBlooTQHk/8094b01bc8fab75b014a0da8cd0db0cf/promo____es.pt.png)
 
 É aqui que os descontos que a sua loja vai oferecer são criados. É possível ainda visualizar, filtrar, buscar e arquivar todas as promoções. De acordo com a configuração de cada loja, existe um limite de promoções que podem estar ativas ao mesmo tempo. 
 
@@ -44,13 +44,13 @@ Para verificar essa quantidade, observe a mensagem que aparece no canto superior
 
 ## Cupons
 
-![cupons.pt](https://images.ctfassets.net/alneenqid6w5/7AsIdJZzvmLwI08igAZDj3/233c803c436c8cf6909561aeae2da292/cupons.pt.png)
+![cupons.pt](//images.ctfassets.net/alneenqid6w5/7AsIdJZzvmLwI08igAZDj3/233c803c436c8cf6909561aeae2da292/cupons.pt.png)
 
 É nesta seção que são criados os cupons. Você também pode buscá-los e arquivá-los. [Aprenda como criar cupons](/pt/tutorial/como-criar-cupom/).
 
 ## Taxas
 
-![taxas.pt](https://images.ctfassets.net/alneenqid6w5/6M97ug98KchFim5RsY9nXY/e2a626bc42050616032de314949f0b48/taxas.pt.png)
+![taxas.pt](//images.ctfassets.net/alneenqid6w5/6M97ug98KchFim5RsY9nXY/e2a626bc42050616032de314949f0b48/taxas.pt.png)
 
 Nesta área serão criados os impostos que incidirão sobre os seus produtos. É permitido também filtrar, buscar e arquivar as taxas. [Entenda melhor as particularidades dessa configuração no artigo sobre taxas](/pt/tutorial/como-criar-taxaimposto/).
 
diff --git a/docs/tutorials/pt/payment-provider-protocol.md b/docs/tutorials/pt/payment-provider-protocol.md
index 70a12d01d..3e98ddd9d 100644
--- a/docs/tutorials/pt/payment-provider-protocol.md
+++ b/docs/tutorials/pt/payment-provider-protocol.md
@@ -3,8 +3,8 @@ title: 'Payment Provider Protocol'
 id: RdsT2spdq80MMwwOeEq0m
 status: PUBLISHED
 createdAt: 2018-01-02T15:40:00.920Z
-updatedAt: 2023-05-31T14:44:41.300Z
-publishedAt: 2023-05-31T14:44:41.300Z
+updatedAt: 2024-07-24T13:58:10.009Z
+publishedAt: 2024-07-24T13:58:10.009Z
 firstPublishedAt: 2018-01-02T17:53:48.934Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,6 @@ legacySlug: payment-provider-protocol
 subcategory: 2Xay1NOZKE2CSqKMwckOm8
 ---
 
-## O que é o Payment Provider Protocol?
 O Payment Provider Protocol é o protocolo de integração entre a VTEX e outras empresas que processam pagamentos.
 
 Por meio dele, a VTEX oferece um contrato público disponível para todos os provedores que desejam se integrar à nossa plataforma. Assim, os provedores obtêm maior autonomia em relação à integração.
@@ -45,7 +44,7 @@ __Adquirente:__ empresa especializada em processar pagamentos. É responsável p
 ## Pré-requisitos para implementação
 ### Assinatura de um contrato de parceria comercial para Serviços Financeiros
 
-Para implementação, publicação e atualização de um conector de pagamentos na VTEX é necessário a assinatura de um contrato de parceria __específico para serviços financeiros__ que cubram as especificidades do tema e as regulações dentro da plataforma. Se você ainda não tem um contrato de parceria, mas tem interesse em se tornar um provedor de pagamento, entre em contato com o nosso time pelo [site](https://vtex.com/br-pt/partner/).
+Para implementação, publicação e atualização de um conector de pagamentos na VTEX é necessário a assinatura de um contrato de parceria __específico para serviços financeiros__ que cubram as especificidades do tema e as regulações dentro da plataforma. Se você ainda não tem um contrato de parceria, mas tem interesse em se tornar um provedor de pagamento, entre em contato com o nosso time pelo [site](https://vtex.com/br-pt/partner).
 
 ### Ter acesso a um ambiente VTEX
 
@@ -59,7 +58,7 @@ Se o parceiro for SI (Service Implementer) que desenvolva integrações para cli
 Para se tornar um provedor VTEX integrado, é necessário utilizar uma das seguintes soluções:
 
 - A infraestrutura onde o conector será construído precisa ter o certificado PCI-DSS assinado por um QSA (Qualified Security Assessor). Maiores informações no [Conselho de Normas de Segurança do PCI](https://www.pcisecuritystandards.org/).
-- Caso não possua o certificado, implementar o provedor utilizando o [Secure Proxy](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-secure-proxy).
+- Caso não possua o certificado, implementar o provedor utilizando o [Secure Proxy](https://developers.vtex.com/docs/guides/payments-integration-secure-proxy).
 
 Se o provedor for certificado ou já iniciou o processo de certificação, é possível entrar em contato com a equipe de negócios da VTEX para começar a integração.
 
@@ -86,112 +85,86 @@ Antes de configurar o ambiente VTEX, o provedor deve implementar o serviço back
 ### 2. Casos de uso específicos
 Há casos em que conectores podem ser construídos para atender alguma solução específica. Abaixo se encontram referências na nossa documentação para instruir sobre esses casos:
 
-- [Payment Provider Framework (PPF)](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework): Solução para implementação de conectores através do VTEX IO a partir de um boilerplate. O boilerplate já vem com grande parte do trabalho feito, incluindo os endpoints do protocolo. A utilização do VTEX IO também acelera o processo de desenvolvimento e testes na loja.
-- [Payment Provider Protocol aplicado a pagamentos com POS](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-ppp-applied-to-pos): Aplicação do PPP para pagamentos em lojas físicas utilizando um terminal de pagamento (POS). Pode ser utilizado com cartões de crédito e débito. O fluxo do pagamento se inicia com uma compra feita no [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) e então será feita a comunicação com o POS, onde o cliente irá inserir o cartão.
+- [Payment Provider Framework (PPF)](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework): Solução para implementação de conectores através do VTEX IO a partir de um boilerplate. O boilerplate já vem com grande parte do trabalho feito, incluindo os endpoints do protocolo. A utilização do VTEX IO também acelera o processo de desenvolvimento e testes na loja.
+- [Payment Provider Protocol aplicado a pagamentos com POS](https://developers.vtex.com/docs/guides/payments-integration-ppp-applied-to-pos): Aplicação do PPP para pagamentos em lojas físicas utilizando um terminal de pagamento (POS). Pode ser utilizado com cartões de crédito e débito. O fluxo do pagamento se inicia com uma compra feita no [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) e então será feita a comunicação com o POS, onde o cliente irá inserir o cartão.
 
 ### 3. Homologação do Payment Provider
-Depois de receber os dados de acesso e implementar o back-end, o provedor deve instalar a app Payment Provider Test Suite para acessar a ferramenta de testes. A instalação é feita na [VTEX App Store](https://apps.vtex.com/vtex-payment-provider-test-suite/p "VTEX App Store"). 
+Depois de receber os dados de acesso e implementar o back-end, o provedor deve instalar a app Payment Provider Test Suite para acessar a ferramenta de testes. A instalação é feita por meio de [VTEX App Store](https://apps.vtex.com/vtex-payment-provider-test-suite/p "VTEX App Store"). 
 
-![print1](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d9d72ca9a6fa585f959fa932412930d7/print1.png)
+![ppp-vtex-store-pt](//images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d4ba38eb2aed1c4a4072cddbc2b4decf/image.png)
 
 <div class="alert alert-warning">
-Toda comunicação com servidores, seja durante o processo de homologação ou em produção, deve ocorrer via HTTPS, que por padrão utiliza a porta 443. É importante lembrar que toda comunicação HTTPS deve ser exclusivamente sobre <strong>TLS 1.2</strong>.
+Para passar no processo de homologação, é necessário implementar uma lógica específica para lidar com os requisitos do teste. Nas requisições enviadas ao Test Suite, utilize o header extra <code>X-VTEX-API-Is-TestSuite = true</code> para identificá-las e mascarar qualquer cenário exigido.<br>Toda comunicação com servidores, seja durante o processo de homologação ou em produção, deve ocorrer via HTTPS, que por padrão utiliza a porta 443. É importante lembrar que toda comunicação HTTPS deve ser exclusivamente sobre TLS 1.2.
 </div> 
 
-Após a instalação, basta conferir o módulo Outros no menu lateral esquerdo do Admin. Em seguida, selecione a opção Payment Provider para configurá-la corretamente.
+Após a instação, clique no item Apps no painel lateral esquerdo do Admin. Em seguida, selecione o app Payment Provider Test Suite para configurá-lo corretamente.
 
-Desse modo, você verá dois formulários: “Service Information” e “Tests”. 
+Dependendo da versão do Admin utilizada na conta da loja, o app não estará visível na lista de apps. Para acessá-lo, utilize o endereço `https://{{accountName}}.myvtex.com/admin/test-suite/payment-provider`, substituindo `{{accountName}}` pelo Nome da Conta da sua loja.
 
-Preencha os campos de cada um de acordo com as indicações abaixo:
+Feito isso, você encontrará um formulário com três seções: __Service info__, __Payment method__ e __Test cases__. Preencha os campos de acordo com as instruções abaixo.
 
-Ao acessar o ambiente pelo link descrito no item anterior, você verá um formulário. Preencha os campos de acordo com as indicações abaixo:
+#### Service info
 
-#### Service Information
+* **Service URL:** Defina a URL do seu serviço de provedor. Essa URL será o endereço base do protocolo e deve seguir o formato determinado por ele. Por exemplo, se a URL do serviço for `https://example.com/`, a URL completa para o endpoint /payments será `https://example.com/payments`.
+* **AppKey e AppToken:** O botão Test with AppKey and AppToken permite que você escolha entre configurar os valores desses campos ou não, o que pode facilitar os testes durante a etapa de desenvolvimento. Se não habilitar essa opção, as credenciais serão enviadas nos headers como uma string vazia.
 
-- __Service URL__: defina a URL do seu serviço de provedor. Essa URL será o endereço base do protocolo e deve seguir o formato determinado por ele. Por exemplo, se a URL do serviço for https://10.10.10.10, a URL completa para o endpoint /payments será https://10.10.10.10/payments.
-- __Connector Name__: preencha com o nome que você deseja dar ao seu conector dentro da VTEX. Ressaltamos o que o nome só pode conter letras minúsculas, numerais e hífen.
-- __X-VTEX-API-AppKey__: insira o valor de "PROVIDER-API-AppKey" do header do request do seu provedor, para fins de teste.
-- __X-VTEX-API-AppToken__: insira o valor de "PROVIDER-API-AppToken" do header do request do seu provedor, para fins de teste.
-
-<div class="alert alert-warning">
-Seu provedor deve esperar os headers: <strong>X-VTEX-API-AppKey</strong> e <strong>X-VTEX-API-AppToken</strong>. Essa combinação são as credenciais para identificar um lojista. O Gateway armazena as credenciais dos lojistas e os outros parâmetros utilizados na configuração da afiliação, os quais serão enviados para o provedor nas transações.
-</div>
-
-![Payment Provider Test Suite 0](https://images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
+<div class="alert alert-info">
+  <p>O Gateway armazena as credenciais das lojas configuradas na afiliação e as envia nos headers X-VTEX-API-AppKey e X-VTEX-API-AppToken. A exceção para isso são as integrações desenvolvidas com VTEX IO. Para elas, os headers serão enviados como x-provider-api-appKey e x-provider-api-appToken. Se você está desenvolvendo com o <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework">Payment Provider Framework (IO)</a>, isso é configurado pela opção usesProviderHeadersName. Veja as configurações disponíveis <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework#available-configurable-options">aqui</a>.
+</p></div>
 
-#### Tests
+#### Payment method
 
-Depois de revisar todos os campos, clique no botão __CHECK URL__. O sistema vai verificar os métodos de pagamento através de uma chamada para o endpoint __/manifest__ do seu provedor. Veja a referência à API [aqui](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#get-/manifest). 
+Após preeencher o campo Service URL, o Test Suite irá validar o [endpoint Manifest](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#get-/manifest) e fazer uma verificação para os métodos de pagamento declarados. Eles irão aparecer como opções nesse campo. Selecione os meios de pagamento no qual você deseja realizar os testes.
 
-Após a chamada, os endpoints das operações disponíveis no seu provedor serão identificados e os testes respectivos a cada operação serão habilitados automaticamente.
+#### Test cases
 
-Você pode selecionar quais testes deseja rodar, mas para que sua integração passe pela análise da nossa equipe, __todos os testes habilitados automaticamente precisam ser realizados__. Portanto, recomendamos que todos eles permaneçam selecionados.
+Nessa seção, você deve selecionar os casos que deseja testar. Se você está testando um método de cartão de crédito, a sua integração deve passar nos casos Approved, Denied, Cancellation, Async Approved e Async Denied. Para um método de pagamento com [redirecionamento](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows#redirect), apenas o Redirect flow é necessário.
 
-![Payment Provider Test Suite 1](https://images.ctfassets.net/alneenqid6w5/5LROAprSeFd1O64M2WCisC/af4e2408feb2d1e5dfb9b9bac7067f6d/Payment_Provider_Test_Suite_1.jpg)
+![ppp-config-pt](//images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/e41bf6da622195968fe1f91bad8f3b75/image.png)
 
 ### 4. Testes
-Ao clicar no botão __RUN TESTS__, o Payment Provider vai aplicar os testes na sua integração para os diferentes cenários possíveis. É importante lembrar que, para executá-los, seu serviço precisa estar em HTTPS.  Os testes são:
-
-- __Authorize__: esse teste é dividido em três etapas. Na primeira, enviamos um request de _Create Payments_ para `{{ServiceURL}}/payments`, esperando como resposta o status _approved_. Na segunda, um request de _Settle Payment_ é enviado para `/payments/{PAYMENT_ID}/settlements` e esperamos uma resposta com o _settleId_ preenchido. Por fim, enviamos um request de _Refund Payment_ para `/payments/{PAYMENT_ID}/refunds`, esperando uma resposta com o _refundId_ preenchido.
-
-- __Denied__: nesse teste, enviamos um request de _Create Payments_ para `{{ServiceURL}}/payments`, esperando como resposta o status _denied_.
-
-- __Cancel__: para esse teste, precisamos primeiro do status _approved_ como resposta ao request de _Create Payments_ para `{{ServiceURL}}/payments`. Depois, enviamos um request de _Cancel Payment_ para `/payments/{PAYMENT_ID}/cancellations` e esperamos uma resposta com o status _cancelled_.
 
-- __AsyncApproved__: esse teste é dividido em duas etapas. Na primeira, enviamos um request de _Create Payments_ para `{{ServiceURL}}/payments`, esperando como resposta o status _undefined_. Então, esperamos receber em até 15 segundos a mesma resposta, só que com status _approved_ em um POST na URL enviada no campo _callbackUrl_. Em seguida, um request de _Capture Payment_ é enviado para `/payments/{PAYMENT_ID}/settlements` e esperamos uma resposta com o _settleId_ preenchido. Por fim, enviamos um request de _Refund Payment_ para `/payments/{PAYMENT_ID}/refunds`, esperando uma resposta com o _refundId_ preenchido. Depois que a integração está em produção, essa chamada feita por callbackUrl é autenticada com as chaves do ambiente do parceiro: _vtex-app-key_ e _vtex-app-token_.
+Quando você clicar no botão `Run Test`, o Test Suite irá chamar a **Service URL** fornecida e executar os casos de teste selecionados. Os testes são:
 
-- __AsyncDenied__: a exemplo do anterior, esse teste também é dividido em duas etapas. Na primeira, enviamos um request de _Create Payments_ para `{{ServiceURL}}/payments`, esperando como resposta o status _undefined_. Então, esperamos receber em até 15 segundos a mesma resposta, só que com status _denied_ em um POST na URL enviada no campo _callbackUrl_. Depois que a integração está em produção, essa última chamada feita por callbackUrl é autenticada com as chaves do ambiente do parceiro: _vtex-app-key_ e _vtex-app-token_. 
-
-- __BankInvoice__: nesse teste, enviamos um request de _Create Payments_ para `{{ServiceURL}}/payments`, esperando que a resposta venha com o status _undefined_ e o campo `bankIssueInvoiceUrl` preenchido com a URL do boleto. Depois, esperamos receber em até 15 segundos a mesma resposta, só que com status _approved_ em um POST na URL enviada no campo _callbackUrl_. Quando a integração estiver em produção, essa última chamada feita por callbackUrl será autenticada com as chaves do ambiente do parceiro: _vtex-app-key_ e _vtex-app-token_.
-
-- __Redirect__: esse teste é dividido em duas etapas. Na primeira, enviamos um request de _Create Payments_ para `{{ServiceURL}}/payments`, esperando que a resposta venha com o status _undefined_ e o campo `redirectUrl` preenchido com a URL que vai ser usada para redirecionar o cliente. Então, esperamos receber em até 15 segundos a mesma resposta, só que com status _approved_ em um POST na URL enviada no campo _callbackUrl_. Quando a integração estiver em produção, essa última chamada feita por callbackUrl será autenticada com as chaves do ambiente do parceiro: _vtex-app-key_ e _vtex-app-token_. Para o conector que utilizará o Redirect, não existe a necessidade de aprovação em todos os testes do Test Suit, somente no do Redirect.
-
-Todos os requests são enviados desde o IP 54.236.214.202
+* **Approved flow:** Este teste é dividido em três estágios. No primeiro, nós enviamos uma requisição [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`, esperando pelo status approved como resposta. No segundo, uma requisição [Settle Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/settlements) é enviada para `{{ServiceURL}}/payments/{paymentId}/settlements` e esperamos uma resposta com o `settleId` preenchido. E no último, nós enviamos uma requisição [Refund Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/refunds) para `{{ServiceURL}}/payments/{paymentId}/refunds` esperando por uma resposta com `refundId` preenchido.
+* **Denied flow:** Neste teste, nós enviamos uma requisição [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`, esperando pelo status denied como resposta.
+* **Cancellation flow:** Para este teste, primeiro nós precisamos do status approved em resposta à requisição de [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`. Nós então enviamos uma requisição [Cancel Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments/-paymentId-/cancellations) para `{{ServiceURL}}/payments/{paymentId}/cancellations` e esperamos uma resposta com status canceled.
+* **Async Approved flow:** Este teste é divido em dois passos. No primeiro, nós enviamos uma requisição [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`, esperando pelo status undefined como resposta. Após 15 segundos, nós esperamos receber outra resposta no mesmo formato através de um `POST` da URL enviada no campo callbackUrl e com o status approved. Com a integração em produção, esta última chamada feita por `callbackUrl` é autenticada com as chaves de ambiente do parceiro: `vtex-app-key` e `vtex-app-token`. Mais detalhes sobre o fluxo de callback podem ser encontrados na seção [Autorização de pagamento](#autorizacao-de-pagamento).
+* **Async Denied flow:** Este teste é dividido em dois passos, assim como o anterior. No primeiro, nós enviamos uma requisição [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`, esperando pelo status undefined como resposta. Após 15 segundos, nós esperamos receber outra resposta no mesmo formato através de um `POST` da URL enviada no campo callbackUrl e com o status denied. Com a integração em produção, esta última chamada feita por `callbackUrl` é autenticada com as chaves de ambiente do parceiro: `vtex-app-key` e `vtex-app-token`. Mais detalhes sobre o fluxo de callback podem ser encontrados na seção [Autorização de pagamento](#autorizacao-de-pagamento).
+* **Bank Invoice flow** Neste teste, nós enviamos uma requisição[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`, esperando por uma resposta com status undefined e o campo `bankIssueInvoiceUrl` preenchido com a URL do ticket. Após 15 segundos, nós esperamos receber outra resposta no mesmo formato através de um POST da URL enviada no campo callbackUrl e com o status approved. Com a integração em produção, esta última chamada feita por `callbackUrl` é autenticada com as chaves de ambiente do parceiro: `vtex-app-key` e `vtex-app-token`. Mais detalhes sobre o fluxo de callback podem ser encontrados na seção [Autorização de pagamento](#autorizacao-de-pagamento).
+* **Redirect flow:** Este teste é dividido em dois passos. No primeiro, nós enviamos uma requisição [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para {{ServiceURL}}/payments, esperando por uma resposta com status undefined e o campo redirectUrl preenchido com a URL que será utilizada para redirecionar o cliente. Após 15 segundos, nós esperamos receber outra resposta no mesmo formato através de um POST da URL enviada no campo `callbackUrl` e com o status approved. Com a integração em produção, esta última chamada feita por `callbackUrl` é autenticada com as chaves de ambiente do parceiro: `vtex-app-key` e `vtex-app-token`. Mais detalhes sobre o fluxo de callback podem ser encontrados na seção [Autorização de pagamento](#autorizacao-de-pagamento). Para o conector que irá utilizar o Redirect, não há necessidade de passar em todos os testes do Test Suite, apenas no de Redirect.
 
 <div class="alert alert-warning">
-No caso dos cartões de crédito, os testes obrigatórios são: <strong>Authorize</strong>, <strong>Denied</strong>, <strong>Cancel</strong>, <strong>AsyncApproved</strong> e <strong>AsyncDenied</strong>.
-</div>
-
-<div class="alert alert-info">
-Para cada teste com cartões de crédito, enviamos um número específico para retornar a resposta esperada. São eles:<br>
-<strong>Resposta com status approved:</strong> cartão numero 4444333322221111<br>
-<strong>Resposta com status denied:</strong> cartão numero 4444333322221112<br>
-<strong>Resposta com status undefined e retorno no callbackUrl com status approved:</strong> cartão numero 4222222222222224<br>
-<strong>Resposta com status undefined e retorno no callbackUrl com status denied:</strong> cartão numero 4222222222222225<br>
+No caso dos cartões de crédito, os testes obrigatórios são: Authorize, Denied, Cancel, Async Approved e Async Denied.
 </div>
 
-### 5. Resultados
-Depois de executar os testes, o sistema retorna os resultados, tanto positivos quanto negativos. O sistema também traz a informação dos resultados esperados para cada teste. Assim, você tem mais visibilidade do que deve ser ajustado em caso de erro.
-
-![Payment Provider Test Suite 2](https://images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/38e5f5d1391d10ca831eba5682c5544b/Payment_Provider_Test_Suite_2.jpg)
+Para identificar como responder corretamente a cada um dos testes com cartão de crédito, utilize estes números específicos:
 
-Para visualizar de forma detalhada cada ação realizada pela integração (e, assim, identificar possíveis erros), basta clicar no botão __TRY LOADING AGAIN?__. Uma lista com as informações completas dos eventos que aconteceram durante o teste vai ser exibida abaixo dos resultados.
+| Número do cartão | Status da resposta                         |
+| ---------------- | ------------------------------------------ |
+| 4444333322221111 | __approved__                                   |
+| 4444333322221112 | __denied__                                     |
+| 4222222222222224 | __undefined__, `callbackUrl` com status __approved__ |
+| 4222222222222225 | __undefined__, `callbackUrl` com status __denied__   |
 
-![Payment Provider Test Suite Logs](https://images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/12a0a237d1c8725b8eeb9bb61eb48fbc/Payment_Provider_Test_Suite_Logs.jpg)
-
-![Payment Provider Test Suite 3](https://images.ctfassets.net/alneenqid6w5/7svc9sEJaMiwsYK0ykU0SS/590453ef17cda1dab3b1bb4342f1d9d1/Payment_Provider_Test_Suite_3.jpg)
+### 5. Resultados
+Após executar os testes, o sistema irá mostrar o Test Report, onde você pode ver os resultados detalhados de cada caso de teste. Desse modo, você tem mais visibilidade sobre o que deve ser ajustado caso ocorra algum erro.
 
-Quando sua integração tiver passado em todos os testes com sucesso, basta abrir um ticket no [Help da VTEX](/pt/support "VTEX Help") informando a conclusão. Porém, antes de abrir o ticket, certifique-se que você possui as seguintes informações:
+![Payment Provider Test Suite 2](//images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/9ecdf0551940ee02ed6bd21b3b86420e/image.png)
 
-- __Connector Name__: uma descrição do provedor. Use o máximo de 16 caracteres alfanuméricos. Este nome não pode ser modificado após publicado.
-- __Partner contact__: endereço de email do parceiro para caso seja necessário comunicar alterações e novas funcionalidades do nosso protocolo.
-- __Production Service Provider Endpoint__: o caminho base a ser utilizado para chamadas de API para o provedor, por exemplo, _https://vtex.pagseguro.com_. Ele deve responder à rota `{{serviceUrl}}/manifest`. Este endpoint deve estar disponível publicamente. 
-- __Sandbox Service Provider Endpoint__: o caminho base a ser utilizado no modo de teste para chamadas de API para o provedor. Por exemplo: _https://sandboxserviceproviderendpoint.com_. 
-- __Owner account__: o nome da conta VTEX a ser utilizada em solicitações de retorno de chamada. Esta conta deve estar disponível em _{account}.myvtex.com_. 
-- __Allowed Accounts__: informe quais contas VTEX deste provedor estarão disponíveis (todas as contas ou contas específicas).
-- __New Payment methods__: informe se este conector suporta uma forma de pagamento que ainda não está disponível no VTEX Admin. 
-- __New Payment method purchase flow__: se uma “Nova forma de pagamento” for suportada, informe se ela funciona com Redirect ou Payment App. Para maiores informações, accesse [Purchase Flows](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-purchase-flows).
+Para ver as mensagens transmitidas entre o Test Suite e a implementação do seu provedor de pagamento, clique no botão Inspect Log do caso de teste desejado. Um modal irá se abrir para mostrar a lista de mensagem transmitidas e o payload de cada requisição e resposta. O botão no canto superior direito da seção de código facilita a cópia do código para a área de transferência.
 
-<div class="alert alert-warning">
-O SLA necessário para que a equipe de pagamento efetue a homologação é de dia 30 dias. Este prazo será iniciado somente após o envio do documento <b>Master Partner Agreement for Financial Services (MPA)</b>. Para solicitações de homologação sem a utilização do MPA, o prazo do SLA poderá ser estendido devido a necessidade de análise adicional da equipe de pagamentos.
-</div>
+![Payment Provider Test Suite Logs](//images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/369d86cffea42dfbe842d037bfdd065e/image.png)
 
 ## Fluxo do protocolo de pagamento
 Aqui vamos explicar o fluxo de pagamento integrado em detalhes. A imagem abaixo ilustra todo o fluxo, mostrando o fluxo de um pagamento e as responsabilidades do seu fornecedor.
 
 Tudo começa com a solicitação de um novo pagamento, após a criação de um novo pedido. A VTEX cria uma nova representação do pagamento e avança para o processamento dos pagamentos.
 
-![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+![fluxo-atualizado-ppp](//images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+
+<div class="alert alert-info">
+  O período padrão de 7 dias para novas tentativas de pagamento assíncronas só é aplicado quando o usuário não especifica um valor no campo <code>delayToCancel</code> do endpoint <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> ou ao enviar o callbackURL.</div>
 
 ### Autorização de pagamento
 Nesse ponto a VTEX chama o endpoint __*/payments*__ e envia um payload com os dados de pagamento para o seu provedor. O provedor deve processar esses dados e enviar de volta a resposta, que deve conter um dos valores de status: __approved__, __denied__ ou __undefined__.
@@ -205,7 +178,7 @@ Seja qual for o caso, uma vez que o processamento termine e o provedor tenha um
 
 O fluxo completo com status undefined e uso de notificação pode ser visto abaixo:
 
-![Payment authorization callback notification flow](https://images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/90500ae3bc824ff831193cf7cdf59c64/image1.png)
+![Payment authorization callback notification flow](//images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/90500ae3bc824ff831193cf7cdf59c64/image1.png)
 
 1. A autorização do pagamento é iniciada quando o Gateway chama o endpoint Create Payment (__/payment__) para o Provider. No body do request, é enviado no campo `callbackUrl` a URL para fazer a notificação.
 2. O pagamento ocorre de forma assíncrona (não gera o status definitivo no momento em que a transação é iniciada). Então o Gateway recebe a resposta com status __undefined__ e fica esperando a conclusão do processamento do pagamento e, por fim, atualizar com o status definitivo (__approved__ ou __denied__).
@@ -214,7 +187,7 @@ O fluxo completo com status undefined e uso de notificação pode ser visto abai
 
 O fluxo completo com status __undefined__ e uso do __retry__ pode ser visto abaixo:
 
-![Payment authorization callback retry flow](https://images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/66f6fe3be218a9fe6e2584e75bb18640/image2.png)
+![Payment authorization callback retry flow](//images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/66f6fe3be218a9fe6e2584e75bb18640/image2.png)
 
 1. A autorização do pagamento é iniciada quando o Gateway chama o endpoint Create Payment (__/payment__) para o Provider. No body do request, é enviado no campo `callbackUrl` a URL do endpoint __retry__.
 2. O pagamento ocorre de forma assíncrona (não gera o status definitivo no momento em que a transação é iniciada). Então o Gateway recebe a resposta com status __undefined__ e fica esperando a conclusão do processamento do pagamento e, por fim, atualizar com o status definitivo (__approved__ ou __denied__).
@@ -234,6 +207,20 @@ https://gatewayqa.vtexpayments.com.br/api/pvt/payment-provider/transactions/8FB0
 
 Na [página de Transações do Admin](https://help.vtex.com/pt/tutorial/como-visualizar-detalhes-do-pedido--tutorials_452), o token de assinatura aparece mascarado por questões de segurança, como neste exemplo: `X-VTEX-signature=Rj******tk`. 
 
+Veja abaixo, um exemplo de payload encaminhado junto ao callback URL:
+
+```json
+{"paymentId":"8B3BA2F4352545A8B1C5A215F356A01C","status":"approved","authorizationId":"184520","nsu":"21705348","tid":"21705348","acquirer":"pagarme","code":"0000","message":"Transação aprovada com sucesso","delayToAutoSettle":1200, "delayToAutoSettleAfterAntifraud":1200, "delayToCancel":86400,"cardBrand":"Mastercard","firstDigits":"534696","lastDigits":"6921","maxValue":16.6}
+```
+
+<div class="alert alert-info">
+  Os valores dos parâmetros enviados no payload do callback substituem os valores originais informados na chamada do <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a>.  
+</div>
+
+<div class="alert alert-warning">
+  Caso os parâmetros de tempo de espera (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) não sejam enviados com a callback URL, os valores serão automaticamente configurados para 24 horas.
+</div>
+
 Ao fazer a solicitação de callback, recomendamos que os provedores de pagamento utilizem a callback URL exatamente como recebida, o que garante que todos os parâmetros estejam incluídos.
 
 Ao chamar a CallbackURL, seu provedor deve enviar no request os headers *X-VTEX-API-AppKey* e *X-VTEX-API-AppToken*. Mais informações sobre isso na [seção de credenciais VTEX](/pt/tutorial/payment-provider-protocol#credenciais-vtex).
diff --git a/docs/tutorials/pt/payments.md b/docs/tutorials/pt/payments.md
new file mode 100644
index 000000000..021d89fa9
--- /dev/null
+++ b/docs/tutorials/pt/payments.md
@@ -0,0 +1,97 @@
+---
+title: 'Pagamentos Data Pipeline (Beta)'
+id: 7LWkFaA1jPabzc5JAt1rGs
+status: PUBLISHED
+createdAt: 2024-02-02T17:53:35.949Z
+updatedAt: 2024-06-21T16:28:44.958Z
+publishedAt: 2024-06-21T16:28:44.958Z
+firstPublishedAt: 2024-05-27T19:26:59.478Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: pagamentos-data-pipeline-beta
+locale: pt
+legacySlug: pagamentos-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+O conjunto de dados de pagamentos é constituído por duas principais tabelas: a `payments_transitions` e a `transaction_tansitions`.
+
+Nesta seção você encontra as seguintes informações:  
+
+- [Características dos dados de pagamentos](#caracteristicas-dos-dados-de-pagamento)
+- [Tabela payments_transitions](#tabela-payments_transitions)
+- [Tabela transaction_trasitions](#tabela-transaction_transitions)
+- [Análise com dados de pagamentos](#analises-com-dados-de-navegacao)
+- [Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados
+
+| **Característica** | **Descrição** |
+|:---:|:---:|
+| **Origem do dado** | Os dados desse conjunto se origina do <a href="https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB">módulo de Pagamentos da VTEX</a>. Eles são coletados e organizados de modo a refletir as transações e os pagamentos realizados na plataforma. |
+| **Disponibilidade** | Os dados de navegação podem ser acessados somente no Admin da VTEX. |
+| **Histórico** | Os dados são mantidos por dois anos, a partir de 2023 para clientes que já utilizam a plataforma VTEX. Os dados da tabela `transactions_interactions` só possuem o histórico desde 07/05/24 (dd/mm/yy).|
+| **Menor intervalo de atualização possível** | Uma hora. |
+
+## Tabela `payments_transitions`
+
+A tabela `payments_transitions` armazena informações detalhadas sobre os pagamentos, incluindo o conector e o meio de pagamento usado em cada transação. Veja a seguir os campos que compõem a tabela.  
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| batch_id | character varying(13) | ID de controle do lote de ingestão de dados. |
+| event_date_time | timestamp with time zone | Data e hora da transição, incluindo informações de fuso horário. |
+| account | character varying(128) | Nome da conta, mapeado para 'account_name' no License Manager da VTEX. |
+| account_id | character varying(36) | Identificador da conta, mapeado para 'id' no License Manager da VTEX após remoção de hífens. |
+| connector | character varying(1024) | O conector responsável pelo processamento do pagamento. |
+| delta_value | double precision | Tempo em milissegundos gasto na transição 'from_transition'. |
+| from_transition | character varying(64) | Estado do pagamento até a data e hora do evento. |
+| to_transition | character varying(64) | Novo estado da transação a partir da data e hora do evento. |
+| payment_id | character varying(32) | Identificador único do pagamento. |
+| payment_system | character varying(1024) | Tipo de pagamento, como cartão de crédito, débito, etc. |
+| transaction_id | character varying(36) | Identificador único da transação à qual este pagamento pertence. |
+| tid | character varying(1024) | Código externo recebido do Operador, representando um número de identificação para uma transação de e-commerce. |
+| nsu | character varying(1024) | Número Sequencial Único que identifica uma operação de venda com cartão, correspondendo a cada fatura criada. |
+| currency_code | character varying(1024) | Código de moeda em três letras maiúsculas. |
+| value | integer | Valor do pagamento multiplicado por 100, ou seja, este valor será 235 para um pagamento de $2,35. |
+
+## Tabela `transaction_transitions`
+
+A tabela `transaction_transitions` armazena as transações, que estão vinculadas aos pedidos realizados. Cada transação contém um conjunto de pagamentos e muda de status, de acordo com um fluxo de trabalho pré-definido. Veja a seguir os campos que compõem a tabela.
+
+| **Nome da Coluna** | **Tipo de Campo** | **Descrição** |
+|:---:|:---:|:---:|
+| batch_id | character varying(13) | ID de controle do lote de ingestão de dados. |
+| event_date_time | timestamp with time zone | Data e hora da transição, incluindo informações de fuso horário. |
+| account | character varying(128) | Mapeia para um 'account_name' no sistema de gerenciamento de licenças da VTEX. |
+| account_id | character varying(36) | Mapeia para um 'id' no sistema de gerenciamento de licenças da VTEX após remover hífens. |
+| delta_value | double precision | Tempo, em milissegundos, gasto na transição 'from_transition'. |
+| from_transition | character varying(64) | Estado da transação até a data e hora do evento. |
+| to_transition | character varying(64) | Novo estado da transação a partir da data e hora do evento. |
+| transaction_id | character varying(36) | Identificador único da transação. |
+
+## Análise com dados de Pagamentos  
+
+As análises com o conjunto de dados de Pagamentos são as seguintes:  
+
+**- Análise de eficiência do processador de pagamento:** avalie o desempenho dos diferentes conectores de pagamento, analisando o tempo médio gasto em cada transição, para identificar os mais eficientes e confiáveis.  
+**- Monitoramento de transições de estado de pagamento:** rastreie as mudanças de estado dos pagamentos ao longo do tempo para compreender padrões e identificar possíveis problemas no fluxo de pagamento.  
+**- Análise de volume de transações por conta:** determine o volume de transações processadas por cada conta, ajudando a entender a demanda por serviços de pagamento em diferentes contas.  
+**- Distribuição do tipo de pagamento:** analise a distribuição do uso de diferentes sistemas de pagamento para avaliar as preferências dos clientes por diversos métodos de pagamento.  
+
+## Correlações com outros dados
+
+Nos dados de pagamentos da plataforma VTEX, notam-se correlações com outros conjuntos de dados que ampliam a compreensão do ciclo de compras:  
+
+**- Interação com dados de [pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv):** análise dos dados de pagamento em conjunto com os pedidos oferece insights sobre como os métodos de pagamento influenciam nas conversões de pedidos, revelando tendências no comportamento de compra dos clientes.  
+**- Análises financeiras e contábeis:** integrar dados de pagamento com análises financeiras contribui para uma gestão mais eficiente do fluxo de caixa e permite previsões financeiras mais precisas, auxiliando na saúde financeira da empresa.
+
+### Conheça outros Conjuntos de dados
+
+- [Inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navegação](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Preços](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)
+- [Promoção](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)  
+
diff --git a/docs/tutorials/pt/payu-romania-refund-details.md b/docs/tutorials/pt/payu-romania-refund-details.md
index 70dcfeb16..1bbe3b8f5 100644
--- a/docs/tutorials/pt/payu-romania-refund-details.md
+++ b/docs/tutorials/pt/payu-romania-refund-details.md
@@ -38,7 +38,7 @@ Se o botão Excluir não estiver ativo e o tempo limite não tiver expirado, voc
 
 Se o pedido de reembolso ou de reembolso já tiver sido enviado pelo sistema ao banco emissor, não poderemos mais excluir / interromper o pedido de forma alguma.
 
-![PayU Romania](https://images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
+![PayU Romania](//images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
 
 Depois que a PayU enviar o pedido de reembolso ou de reembolso ao banco emissor, o status do pedido será atualizado no PayP cPanel como "REVERSE" (para vazios) ou "REEMBOLSO". E a VTEX receberá um webhook do PaymentsOS, portanto, o status do pedido também pode ser atualizado na plataforma (no Pagamentos e, consequentemente, refletido no OMS).
 
diff --git a/docs/tutorials/pt/pci-gateway-overview.md b/docs/tutorials/pt/pci-gateway-overview.md
index f34d8c11c..32cb65bc4 100644
--- a/docs/tutorials/pt/pci-gateway-overview.md
+++ b/docs/tutorials/pt/pci-gateway-overview.md
@@ -19,7 +19,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 # Começando a usar
 
-![new-admin-pagamentos ](https://images.ctfassets.net/alneenqid6w5/1QtaQtxOB2gYys8yqiaEkE/a10f07d80939b53ae95255b41e5ee6f7/NEW_ADMIN_PAGAMENTOS_PT.png)
+![new-admin-pagamentos ](//images.ctfassets.net/alneenqid6w5/1QtaQtxOB2gYys8yqiaEkE/a10f07d80939b53ae95255b41e5ee6f7/NEW_ADMIN_PAGAMENTOS_PT.png)
 
 Criado para oferecer a flexibilidade máxima em relação às configurações de pagamento, o módulo de **Pagamentos** processa as transações com base em alguns conceitos de negócio. Entenda cada um deles:
 
diff --git a/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md b/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md
index 5db0224b4..9b80b47d8 100644
--- a/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md
+++ b/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md
@@ -1,52 +1,155 @@
 ---
-title: 'Testes de penetração e aviso de vulnerabilidade'
+title: 'Testes de penetração e avisos de vulnerabilidade'
 id: 6jodF6s1I50Fg84ZwutOCb
 status: PUBLISHED
 createdAt: 2022-11-30T14:20:37.453Z
-updatedAt: 2023-05-22T14:22:24.398Z
-publishedAt: 2023-05-22T14:22:24.398Z
+updatedAt: 2024-04-25T03:01:48.522Z
+publishedAt: 2024-04-25T03:01:48.522Z
 firstPublishedAt: 2022-11-30T14:42:44.449Z
 contentType: tutorial
 productTeam: Others
-author: 2Gy429C47ie3tL9XUEjeFL
+author: 1malnhMX0vPThsaJaZMYm2
 slug: testes-de-penetracao-e-aviso-de-vulnerabilidade
 locale: pt
 legacySlug: avaliacoes-de-seguranca-e-relatorios-de-vulnerabilidade
 subcategory: vONCJSxwN5qZiElOEtKkH
 ---
 
-A VTEX avalia rigorosamente os recursos da plataforma, testando e identificando vulnerabilidades por meio de scans e testes de penetração recorrentes. Essas verificações de vulnerabilidade são executadas periodicamente. 
+<div class="alert alert-info">
+  <p>Esta funcionalidade faz parte do produto <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
 
-Caso deseje realizar seu próprio teste de penetração no ambiente da sua loja, a VTEX irá avaliar sua solicitação e verificar a possibilidade de execução do teste. Veja abaixo como realizar esta solicitação.
+<div class="alert alert-warning">
+  <p>Se desejar uma análise do seu relatório de teste de penetração pela equipe de Segurança da VTEX, é necessário ter o VTEX Shield. Além disso, todos os testes de penetração devem ser previamente <a href="#agendar-teste-de-penetracao">agendados com a VTEX</a>. Qualquer teste realizado de forma autônoma sem aviso prévio à VTEX será considerado uma tentativa de ação não autorizada.</p>
+</div>
 
-## Testes de Penetração
+A VTEX avalia rigorosamente os recursos da plataforma, testando e identificando vulnerabilidades por meio de escaneamento e testes de penetração recorrentes. Essas verificações de vulnerabilidade são executadas periodicamente.
 
-Para solicitar e agendar um teste de penetração, siga estes passos:
+Além das verificações padrão,  lojas que utilizam o [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) podem realizar um teste de penetração  e reportar alguma vulnerabilidade encontrada, desde que façam o agendamento com a VTEX com antecedência.
 
-1. Abra um ticket com o [suporte VTEX](https://help.vtex.com/pt/support), solicitando o agendamento de um teste de penetração.
-2. Se a execução do teste for aprovada pela VTEX, nossa equipe solicitará as informações necessárias para o agendamento e a assinatura do acordo de confidencialidade. Se você contratar uma empresa terceira para realizar o teste, ela também deverá assinar o acordo de confidencialidade.
-3. Atualize seu ticket anexando o acordo de confidencialidade e as informações solicitadas pela VTEX. 
+O teste de penetração, ou pentest, é um ataque simulado a um sistema de computador, rede ou aplicativo da Web para identificar e corrigir vulnerabilidades de segurança. Esse teste é realizado de forma ética para avaliar a segurança de um sistema sem causar nenhum dano real.
+
+Neste guia, explicamos o procedimento para agendar um teste de penetração e reportar uma possível vulnerabilidade na plataforma:
+
+- [Agendar teste de penetração](#agendar-teste-de-penetracao)
+  - [Relatórios de testes de penetração](#relatorios-de-testes-de-penetracao)
+  - [Procedimentos não permitidos](#procedimentos-nao-permitidos)
+- [Reportar vulnerabilidade](#reportar-vulnerabilidade)
+  - [Definição de vulnerabilidade](#definicao-de-vulnerabilidade)
+  - [Resposta da VTEX](#resposta-da-vtex)
+
+## Agendar teste de penetração
+
+<div class="alert alert-warning">
+  <p>Somente lojas com o <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a> podem agendar testes de penetração e obter uma resposta do time de Segurança, com acesso a uma análise profunda do relatório do teste, conforme descrito nos procedimentos deste guia.</p>
+</div>
+
+Para realizar um teste de penetração no ambiente da sua loja, é necessário alinhar o cronograma de testes com a VTEX, para organização interna e planejamento da equipe de segurança. Siga as instruções abaixo:
+
+1. Abra um ticket com o [Suporte VTEX](https://help.vtex.com/pt/support), informando que você deseja agendar um teste de penetração.
+2. Nossa equipe solicitará as informações necessárias para o agendamento. Se a loja contratar uma empresa terceirizada para realizar o teste, ela precisa assinar o [acordo de confidencialidade](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+
+    A VTEX recomenda que os clientes realizem seus testes de penetração com parceiros que tenham equipes com um nível mínimo de certificação na área, com atenção aos [procedimentos não permitidos](#procedimentos-nao-permitidos).
+
+    Empresas com profissionais certificados em programas como o [Certified Ethical Hacker](https://www.eccouncil.org/train-certify/certified-ethical-hacker-ceh/) do EC-Council, [CompTIA PenTest+](https://www.comptia.org/pt/certificacoes/pentest) e [GIAC Exploit Researcher and Advanced Penetration Tester](https://www.giac.org/certifications/exploit-researcher-advanced-penetration-tester-gxpn/) tendem a entregar relatórios mais detalhados e padronizados, o que melhora a comunicação e a qualidade da avaliação.
+
+3. Atualize seu ticket anexando o [acordo de confidencialidade](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip) assinado pela empresa contratada para realizar o teste e as informações solicitadas pela VTEX.
 4. Salve o número do ticket. Você precisará dele para comunicações futuras.
+5. Após receber as informações, a equipe VTEX entrará em contato para confirmar a execução do teste de penetração em até dois dias úteis.
+6. Realize o teste na data agendada, mediante a autorização da VTEX.
+7. Envie um relatório com os resultados no mesmo ticket para o [Suporte VTEX](https://help.vtex.com/pt/support).
+
+  <div class="alert alert-warning">
+    <p>É obrigatório seguir as orientações descritas em <a href="#relatorios-de-testes-de-penetracao">Relatórios de testes de penetração</a> para que o prazo de análise seja cumprido pela VTEX.</p>
+  </div>
+
+   Nomeie uma pessoa de sua equipe de segurança para ser o ponto de contato da equipe de segurança da VTEX no processo de análise do relatório do teste.
+
+A equipe de segurança da VTEX se dedica a realizar uma análise abrangente de todas as descobertas relatadas pelo cliente durante testes de penetração previamente autorizados e agendados pela VTEX.
+
+Em até 10 dias úteis após o recebimento do [relatório](#relatorios-de-testes-de-penetracao), a equipe identificará falsos positivos e reclassificará a gravidade das ameaças identificadas conforme necessário, seguindo as práticas recomendadas da VTEX. Cada decisão nesse processo será acompanhada de uma justificativa detalhada para garantir total transparência e compreensão.
+
+<div class="alert alert-warning">
+  <p>Lojas que estão se preparando para o go-live e desejarem realizar um teste de penetração também precisam agendá-lo com antecedência. Nesse caso, é obrigatório enviar o relatório com os resultados para o <a href="https://help.vtex.com/pt/support">Suporte VTEX</a> pelo menos <strong>45 dias</strong> antes da data planejada para o go-live. Neste período, a VTEX vai analisar o resultado e endereçar qualquer vulnerabilidade identificada no processo.</p>
+</div>
+
+### Relatórios de testes de penetração
+
+Para que o prazo de 10 dias úteis de análise do relatório seja cumprido pela VTEX, é necessário seguir as diretrizes abaixo ao criar o relatório do teste de penetração:
+
+* **Detalhamento de qual foi o ponto afetado**:
+
+  Inclua informações sobre onde o problema foi detectado (URL, fluxo de funcionalidade, entre outros).
+* **Detalhamento do impacto nos negócios**:
+
+  Descreva o que esse problema de segurança causa e quais são as vantagens do invasor.
+* **Detalhamento dos critérios para classificar a vulnerabilidade**:
+
+  Utilize uma estrutura ou um documento que detalhe os critérios usados para classificar a criticidade da suposta vulnerabilidade identificada.
+* **Descrição do problema**:
+
+  Adicione imagens para ilustrar o problema.
+* **Descrição das etapas para reproduzir ou prova de conceito**:
+
+  Descreva os procedimentos para replicar o problema de segurança, de preferência com imagens.
+* **Descrição do ataque** (opcional):
+
+  Se o relatório relatar um ataque, inclua uma explicação de quais problemas de segurança foram utilizados para fomentar o ataque, com imagens de evidências (vídeos são opcionais).
+
+### Procedimentos não permitidos
+
+Recomendamos utilizar somente os testes autorizados para identificar vulnerabilidades. Não permitimos os seguintes procedimentos:
+
+* Realizar testes de penetração sem autorização e sem agendamento junto à VTEX.
+* Realizar ações que possam afetar de forma negativa a VTEX, seus produtos ou usuários. Por exemplo, Spam, Brute Force, Denial of Service e outras ações informadas no [acordo de confidencialidade relativo a testes de segurança](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+* Acessar ou tentar acessar dados ou informações que não pertencem a sua conta.
+* Destruir ou tentar corromper dados ou informações que pertençam à VTEX.
+* Realizar qualquer tipo de ataque físico ou eletrônico ao pessoal ou propriedades da VTEX.
+* Técnicas de engenharia social.
+* Violar quaisquer leis e regulamentos ou violar quaisquer acordos para descobrir vulnerabilidades.
+
+## Reportar vulnerabilidade
+
+Nossos clientes são encorajados a reportar, de modo responsável, quaisquer vulnerabilidades de segurança que acreditam ter encontrado durante testes autorizados.
+
+Aqueles que desejarem reportar uma vulnerabilidade devem antes trabalhar com suas próprias equipes de segurança e desenvolvimento para realizar uma avaliação de segurança e eliminar  falsos positivos ou problemas oriundos de configurações personalizadas. Somente casos compatíveis com a [definição de vulnerabilidade](#definicao-de-vulnerabilidade) serão verificados.
+
+<div class="alert alert-warning">
+  <p>Consulte o documento <a href="https://vtex.com/br-pt/security/security-practices/">Práticas de Segurança da VTEX</a> e nossa <a href="https://help.vtex.com/pt/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX#risk-assessment-na-vtex">FAQ de Segurança</a> antes de reportar qualquer vulnerabilidade. Estes documentos esclarecem nossos processos e ajudam a eliminar falsos positivos.</p>
+</div>
+
+Após esse procedimento, caso haja uma vulnerabilidade, siga estes passos:
+
+1. [Baixe o modelo](https://assets.ctfassets.net/alneenqid6w5/7FNzoEpl67wH6crmW98If2/5edb235d1afe34aabf08ab73d67ad8f8/Modelo_-_Comunica____o_de_Vulnerabilidade_-_PT.pdf) para comunicação de vulnerabilidades.
+2. Preencha o modelo de comunicação de vulnerabilidades com os detalhes de cada vulnerabilidade encontrada. Adicione o maior número possível de detalhes para explicar a suspeita identificada, disponibilizando evidências e imagens que nos ajudem a compreender, reproduzir e validar o problema.
+
+  As vulnerabilidades devem ser reportadas individualmente, seguindo o modelo estabelecido. Caso tenha encontrado mais de uma vulnerabilidade em seu teste, preencha múltiplos modelos e anexe ao seu chamado.
+
+  <div class="alert alert-warning">
+    <p>Todas as informações devem ser preenchidas e são importantes para a avaliação. Comunicações de vulnerabilidade fora do padrão estabelecido não serão endereçadas pelo time de Segurança da VTEX.</p>
+  </div>
+
+3. Abra uma solicitação para o nosso [Suporte](https://help.vtex.com/pt/support) para registrar o aviso de vulnerabilidade de segurança. Não esqueça de anexar o modelo de comunicação de vulnerabilidades preenchido neste chamado.
+4. Salve o número do seu chamado, pois você poderá precisar dele em futuras comunicações.
+
+### Definição de vulnerabilidade
 
-Após receber as informações, a equipe VTEX entrará em contato para confirmar a execução  do Teste de Penetração.
+A VTEX considera uma vulnerabilidade de segurança qualquer falha em um dos nossos componentes que possa permitir que a confidencialidade, integridade ou disponibilidade de produto ou infraestrutura seja comprometida de alguma forma.
 
-## Relatório de vulnerabilidade
+Não consideramos como uma vulnerabilidade os seguintes casos: 
 
-Após a [solicitação](#solicitando-uma-avaliacao-de-seguranca) e realização da sua availação de segurança, caso haja descobertas, siga estes passos:
+* Presença ou ausência de cabeçalhos HTTP (X-Frame-Options, CSP, nosniff, entre outros).
+* Ausência de atributos de segurança em cookies.
+* Problemas relacionados a cache.
+* Mensagens de erro de _stack_.
+* Injeção de conteúdo por usuários administrativos.
+* Partes customizadas da loja.
+* Preenchimento automático ativado.
 
-1. Revise e valide todas as descobertas da avaliação. Isso exigirá um recurso de segurança da sua parte, especialmente para relatório de scan automatizado.
-2. Redija relatório especificando, para cada vulnerabilidade descoberta, as seguintes informações:
-    - Quais URLs e fluxos de funcionalidade foram afetados.
-    - Como foi detectado o problema.
-    - Qual é o impacto desta vulnerabilidade na aplicação alvo, caso seja explorada, inclusive que vantagens um invasor poderia obter.
-    - Critérios de priorização e classificação usados. Considere utilizar um framework reconhecido ou descreva documento detalhando a metodologia de classificação da criticidade da vulnerabilidade.
-    - Descreva o problema, detalhando o procedimento para replicação da falha. Se possível inclua imagens.
-    - Caso decida incluir no relatório uma seção reportando um ataque, descreva quais vulnerabilidades foram exploradas no mesmo. Neste caso inclua evidências de imagem, vídeo sendo opcional.
-3. Abra um ticket com o [suporte VTEX](https://help.vtex.com/pt/support) e inclua as seguintes informações:
-    - Número do ticket da [solicitação de avaliação de segurança](#solicitando-uma-avaliacao-de-seguranca) correspondente ao teste.
-    - Relatório de vulnerabilidade produzido como descrito no item 2.
+### Resposta da VTEX
 
-## Acordo de confidencialidade
+A VTEX não se compromete a responder a relatórios em massa gerados por verificadores automatizados. Caso sua análise se baseie em um processo automatizado de identificação de vulnerabilidades, recomendamos que os relatórios sejam analisados por um profissional de segurança para garantir a validade do que foi encontrado antes de comunicar as vulnerabilidades à VTEX.
 
-Aqui você pode fazer o download do [acordo de confidencialidade relativo a testes de segurança](https://assets.ctfassets.net/alneenqid6w5/5iw8rN7CdSn7PHKvMMcO19/ab46ae4025d506e052dcef5974f9007f/Pentest_NDA_.zip).
+A VTEX se compromete a responder os avisos recebidos pelo [Suporte](https://help.vtex.com/pt/support) o mais breve possível, notificar sobre a correção de vulnerabilidades ou fornecer motivos coerentes pelos quais análises ou correções eventualmente não possam ser realizadas.
 
+A VTEX está dedicada a analisar, verificar e solucionar quaisquer vulnerabilidades que nos sejam relatadas e possam comprometer a sua segurança.
diff --git a/docs/tutorials/pt/permissions-management-in-b2b-suite.md b/docs/tutorials/pt/permissions-management-in-b2b-suite.md
new file mode 100644
index 000000000..3ba902279
--- /dev/null
+++ b/docs/tutorials/pt/permissions-management-in-b2b-suite.md
@@ -0,0 +1,67 @@
+---
+title: 'Gerenciamento de permissões no B2B Suite'
+id: 2PLR7mIFxgbmsGq84paLeA
+status: PUBLISHED
+createdAt: 2024-06-05T18:01:03.375Z
+updatedAt: 2024-06-07T13:37:21.121Z
+publishedAt: 2024-06-07T13:37:21.121Z
+firstPublishedAt: 2024-06-06T10:57:21.290Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gerenciamento-de-permissoes-no-b2b-suite
+locale: pt
+legacySlug: gerenciamento-de-permissoes-no-b2b-suite
+subcategory: 1qGLxbxcX8kwKSWESbLZca
+---
+
+Em uma organização, o Organization Admin (usuário principal) é o responsável por gerenciar o acesso de diferentes pessoas em uma loja B2B. Para realizar esta ação, ele utiliza o sistema de permissões no B2B Suite.
+
+Por meio deste aplicativo, é possível realizar:
+
+- **Configuração inicial:** o administrador cria os perfis de acesso predefinidos e as permissões associadas a eles.
+
+- **Associação de papéis e permissões:** os perfis de acesso predefinidos são associados às diferentes funções e responsabilidades dentro da organização. Cada papel tem suas próprias permissões específicas.
+
+- **Sincronização automática de informações:** o aplicativo se comunica automaticamente com outros aplicativos do B2B Suite, como [Organizações B2B](https://developers.vtex.com/docs/apps/vtex.b2b-organizations), para habilitar diferentes capacidades de gerenciamento de organização dependendo do perfil de acesso de cada usuário.
+
+- **Verificação de permissões:** quando um usuário realiza uma ação na loja, como realizar um pedido ou acessar determinada funcionalidade, o aplicativo verifica se esse usuário tem as permissões necessárias para executar essa ação com base no perfil de acesso atribuído a ele anteriormente.
+
+- **Gerenciamento de permissões:** o aplicativo opera em segundo plano (backstage), armazenando os perfis de acesso predefinidos.
+
+## Perfis de acesso e permissões
+
+O aplicativo de Permissões da loja permite que, dentro de uma organização, cada usuário tenha diferentes papéis, como um comprador que faz pedidos com limites de orçamento de um centro de custo pré-definido ou um gerente responsável por revisar e aprovar pedidos. Esses papéis podem estar associados a múltiplas permissões, dependendo das ações que esse usuário precisa realizar.
+
+## Perfis de acesso à loja
+
+A tabela a seguir apresenta os perfis disponíveis na loja, suas chaves e descrições.
+
+| Perfil                | Chave                | Descrição                                                                                                                                                                                |
+|-----------------------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Store Admin           | store-admin          | O administrador da loja é o usuário que acessa o Admin VTEX e gerencia a loja.                                                                                                           |
+| Sales Admin           | sales-admin          | Usuário administrador de vendas que pode gerenciar todos os usuários de vendas.                                                                                                          |
+| Sales Manager         | sales-manager        | Usuário gerente de vendas que pode gerenciar usuários de vendas na mesma organização, além de auxiliar compradores e simular compras em uma loja.                                        |
+| Sales Representative  | sales-representative | Usuário representante de vendas que pode auxiliar ou simular compras em uma loja.                                                                                                        |
+| Organization Admin    | customer-admin       | Usuário principal da organização que gerencia as informações da empresa, assim como seus membros e centros de custo.                                                                     |
+| Organization Approver | customer-approver    | Usuário da organização que pode obter um carrinho ou cotação salvo anteriormente por um Comprador da Organização e criar um novo pedido.                                                 |
+| Organization Buyer    | customer-buyer       | O usuário da organização pode adicionar itens ao carrinho. Se o aplicativo [B2B Quotes & Carts](https://developers.vtex.com/docs/apps/vtex.b2b-quotes) estiver instalado, ele também pode salvar o carrinho para uso futuro ou criar uma cotação. |
+
+## Configurando o gerenciamento de perfis de acesso
+
+Para gerenciar perfis de acesso e permissões de aplicativos, configure as permissões seguindo os passos abaixo na interface de usuário de Permissões da loja.
+
+1. No Admin VTEX, acesse **Aplicativos > Apps instalados > Permissões da loja**, ou digite **Permissões da loja** na barra de busca no topo da página.
+
+2. Clique em um dos perfis da loja disponíveis.
+
+3. Clique em um dos aplicativos listados.
+
+4. Selecione quais permissões deseja habilitar para o perfil.
+
+5. Clique em `Salvar`.
+
+![Gerenciamento de permissões - PT](//images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/8c88c345288f6092061820e2193e104f/Gerenciamento_de_permiss_es_-_PT.gif)
+
+Depois de associar os perfis com as permissões desejadas, você pode atribuir funções aos usuários. Para saber mais, acesse [Organizações B2B](https://developers.vtex.com/docs/guides/vtex-b2b-organizations#users).
+
diff --git a/docs/tutorials/pt/physical-store-instore-beta.md b/docs/tutorials/pt/physical-store-instore-beta.md
index 4affcb3bd..9d0b08af7 100644
--- a/docs/tutorials/pt/physical-store-instore-beta.md
+++ b/docs/tutorials/pt/physical-store-instore-beta.md
@@ -28,7 +28,7 @@ Esta página permite que você realize as seguintes ações:
 * [Editar](#editar-loja-fisica)
 * [Excluir](#excluir-loja-fisica)
 
-![loja-fisica-PT](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
+![loja-fisica-PT](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
 
 A página apresenta as seguintes informações: 
 
@@ -54,7 +54,7 @@ Você pode cadastrar uma loja física seguindo os passos a seguir:
 
 ### Campos de cadastro da loja física
 
-![loja-fisica2-pt](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
+![loja-fisica2-pt](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
 
 #### Identificação
 
diff --git a/docs/tutorials/pt/pickup-points-for-subscription-orders.md b/docs/tutorials/pt/pickup-points-for-subscription-orders.md
new file mode 100644
index 000000000..6419fc095
--- /dev/null
+++ b/docs/tutorials/pt/pickup-points-for-subscription-orders.md
@@ -0,0 +1,54 @@
+---
+title: 'Pontos de retirada para pedidos de assinatura'
+id: csIqB6iBh4QNIFdEj0nVv
+status: PUBLISHED
+createdAt: 2021-05-17T12:45:21.450Z
+updatedAt: 2023-11-16T15:59:51.093Z
+publishedAt: 2023-11-16T15:59:51.093Z
+firstPublishedAt: 2021-05-17T20:55:05.477Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 1malnhMX0vPThsaJaZMYm2
+slug: pontos-de-retirada-para-pedidos-de-assinatura
+locale: pt
+legacySlug: pontos-de-retirada-para-pedidos-de-assinatura-beta
+subcategory: 1rA9wuuskW3PpjvMrhatAM
+---
+
+Um ponto de retirada é um local físico onde o cliente tem a opção de retirar o seu pedido, em vez de recebê-lo em casa. Um cenário para essa funcionalidade é a retirada em loja física, por exemplo.
+
+Além dos pedidos comuns, você pode disponibilizar pontos de retirada para pedidos de assinaturas, caso utilize o [módulo de Assinaturas](https://help.vtex.com/pt/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj).
+
+Veja abaixo o que é necessário para habilitar essa funcionalidade.
+
+- [Requisitos](#requisitos)
+- [Escolher pontos de retirada](#escolher-pontos-de-retirada)
+
+<div class="alert alert-info">
+  <p>A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao <a href="https://help.vtex.com/pt/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH">Checkout V6</a>.</p>
+</div>
+
+## Requisitos
+
+Para disponibilizar pontos de retirada para pedidos de assinatura, é necessário cumprir os requisitos logísticos listados abaixo.
+
+*   Você precisa ter o [módulo de Assinaturas](https://help.vtex.com/pt/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj) instalado e a opção de pontos de retirada habilitada. Para isso, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
+*   É necessário configurar pontos de retirada na sua loja. Apenas pontos de retirada da loja principal ou de franquias (Sellers White Label) podem ser utilizados em pedidos de assinaturas. Para saber como fazer a configuração, leia o artigo [Configurar Pontos de Retirada (Pickup Points)](https://help.vtex.com/pt/tutorial/adding-pickup-points--2R5ClQiwe4KoSQgsuiOw4E).
+*   As transportadoras associadas aos pontos de retirada de pedidos de assinatura **não** podem ter [janelas de entrega](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) configuradas.
+*   Os itens precisam ter estoque na data do ciclo de assinatura, ou seja, no momento em que os pedidos recorrentes são criados.
+
+## Escolher pontos de retirada
+
+O cliente final pode escolher pontos de retirada para itens de um pedido de assinatura no momento do checkout, conforme ilustrado na imagem abaixo.
+
+![subscriptionspickup PT](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
+
+Você também pode atribuir pontos de retirada ao [criar novas assinaturas](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#post_api-rns-pub-subscriptions) por meio da [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1). No caso de assinaturas já existentes, você pode alterar o endereço de entrega com a [rota de atualização de assinatura da API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#patch_api-rns-pub-subscriptions-id) para começar a utilizar um ponto de retirada.
+
+Para descobrir os pontos de retirada disponíveis perto de um CEP ou de determinadas geocoordenadas, você pode utilizar a [API do Checkout](https://developers.vtex.com/vtex-rest-api/reference/fulfillment#listpickupppointsbylocation).
+
+## Artigos relacionados
+
+*   [Como configurar Assinaturas na sua loja](https://help.vtex.com/pt/tutorial/como-configurar-assinatura-v2--1FA9dfE7vJqxBna9Nft5Sj)
+*   [Configurar Pontos de Retirada (Pickup Points)](https://help.vtex.com/pt/tutorial/configurar-pontos-de-retirada-pickup-points--2R5ClQiwe4KoSQgsuiOw4E)
+*   [Configurar Seller White Label como Ponto de Retirada (Pickup Point)](https://help.vtex.com/pt/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e)
diff --git a/docs/tutorials/pt/pickup-points.md b/docs/tutorials/pt/pickup-points.md
index c27c574e4..d2512dc98 100644
--- a/docs/tutorials/pt/pickup-points.md
+++ b/docs/tutorials/pt/pickup-points.md
@@ -3,8 +3,8 @@ title: 'Pontos de retirada'
 id: 2fljn6wLjn8M4lJHA6HP3R
 status: PUBLISHED
 createdAt: 2020-07-01T19:16:21.675Z
-updatedAt: 2023-03-29T19:48:10.418Z
-publishedAt: 2023-03-29T19:48:10.418Z
+updatedAt: 2023-07-25T16:53:09.640Z
+publishedAt: 2023-07-25T16:53:09.640Z
 firstPublishedAt: 2020-07-01T19:25:40.136Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -71,7 +71,7 @@ A VTEX considera que o ponto de retirada é uma forma de envio e, por isso, as c
     - b. Na aba **Política de envio**, selecione a política de envio criada para o ponto de retirada.
     - c. Na coluna **Ações**, clique no ícone <i class="fas fa-pen"></i> para edição.
     - d. Ative o <i class="fas fa-toggle-on"></i> do campo **Relacionar pontos de retirada**.
-    - e. Selecione o ponto de retirada pelos campos disponíveis.![relacionarpontosretiradaPT](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/666ecbf11f8f19e5b8b1ca8b381abbf8/relacionarpontosretiradaPT.png)<div class = "alert alert-info">Para lojas que possuem mais de 50 pontos de retirada, recomendamos utilizar o campo Tags dos pontos de retirada ao criar um ponto de retirada. Utilizar tags facilita a busca dos pontos de <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio">retirada na hora de relacioná-los com a política de envio</a>.Lembre-se também que a política de envio que está associada a um ponto de retirada não fica disponível para outro tipo de envio. Recomendamos criar uma política de envio exclusiva do ponto de retirada.</div>
+    - e. Selecione o ponto de retirada pelos campos disponíveis.![relacionarpontosretiradaPT](//images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/666ecbf11f8f19e5b8b1ca8b381abbf8/relacionarpontosretiradaPT.png)<div class = "alert alert-info">Para lojas que possuem mais de 50 pontos de retirada, recomendamos utilizar o campo Tags dos pontos de retirada ao criar um ponto de retirada. Utilizar tags facilita a busca dos pontos de <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio">retirada na hora de relacioná-los com a política de envio</a>.Lembre-se também que a política de envio que está associada a um ponto de retirada não fica disponível para outro tipo de envio. Recomendamos criar uma política de envio exclusiva do ponto de retirada.</div>
 
 4. [Cadastrar a geolocalização](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): para maior precisão da localização dos pontos de retirada no checkout.<div class = "alert alert-info">A visualização dos pontos de retirada com mapa e horário no checkout está disponível apenas para o Checkout V6.</div>
 
@@ -79,8 +79,8 @@ A VTEX considera que o ponto de retirada é uma forma de envio e, por isso, as c
     - a. No Admin VTEX, acesse **Configurações da loja > Storefront > Checkout**, ou digite *Checkout* na barra de busca no topo da página. 
     - b. Seleciona a configuração utilizada na loja e clique no ícone <i class="fas fa-cog"></i>.
     - c. Clique na aba **Checkout** na barra superior.
-    - d. Selecione o <i class="fas fa-toggle-on"></i> do campo **Endereço na nota fiscal para retirada em loja**.![NFpontoretiradaPT](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/491e27746972c957683057e5c944bb84/NFpontoretiradaPT.png)<div class="alert alert-warning">A opção de <b>Endereço na nota fiscal para retirada em loja</b> deve estar habilitada em todas as lojas do Brasil, pois é num requisito que a Nota Fiscal emitida contenha a informação do endereço do cliente, mesmo que a opção de entrega do pedido seja no ponto de retirada. O endereço preenchido pelo cliente será registrado no campo `invoiceData`do <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - d. Selecione o <i class="fas fa-toggle-on"></i> do campo **Endereço na nota fiscal para retirada em loja**.![NFpontoretiradaPT](//images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/491e27746972c957683057e5c944bb84/NFpontoretiradaPT.png)<div class="alert alert-warning">A opção de <b>Endereço na nota fiscal para retirada em loja</b> deve estar habilitada em todas as lojas do Brasil, pois é num requisito que a Nota Fiscal emitida contenha a informação do endereço do cliente, mesmo que a opção de entrega do pedido seja no ponto de retirada. O endereço preenchido pelo cliente será registrado no campo `invoiceData`do <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
 
 6. Configurar a quantidade de pontos de retirada que são exibidos no checkout:
     - a. No Admin VTEX, acesse **Configurações da loja > Envio > Configurações**, ou digite *Envio* na barra de busca no topo da página e selecione *Configurações da loja / Envio*. 
-    - b. Altere o campo **Configurações de pontos de retirada:** utilize os botões <i class="far fa-caret-square-up"></i> e <i class="far fa-caret-square-down"></i> e selecione os primeiros pontos de retirada que ficarão disponíveis na lista de busca (exibida no checkout).
+    - b. Altere o campo **Configurações de pontos de retirada:** utilize os botões <i class="far fa-caret-square-up"></i> e <i class="far fa-caret-square-down"></i> e selecione a quantidade dos primeiros pontos de retirada que ficarão disponíveis na lista de busca exibida no checkout para o cliente.
diff --git a/docs/tutorials/pt/pipedrive-suiteshare.md b/docs/tutorials/pt/pipedrive-suiteshare.md
index 7a8cdcbd4..e3d12036f 100644
--- a/docs/tutorials/pt/pipedrive-suiteshare.md
+++ b/docs/tutorials/pt/pipedrive-suiteshare.md
@@ -21,37 +21,37 @@ Para realizar a integração acesse no seu painel do **VTEX Assisted Sales (Sui
 
 Na dashboard em _**“Integrações”**_.
 
-![Pipedrive 1](https://images.ctfassets.net/alneenqid6w5/2VCqCuAJgX4c5kqnBx3YnN/e9142c549e1f18a21005b50f10cf71b5/Screenshot_2022-08-30_at_11-33-50_Pipedrive.png)
+![Pipedrive 1](//images.ctfassets.net/alneenqid6w5/2VCqCuAJgX4c5kqnBx3YnN/e9142c549e1f18a21005b50f10cf71b5/Screenshot_2022-08-30_at_11-33-50_Pipedrive.png)
 
  Ou clique em "_**configurações > Integrações"**_.
 
-![Pipedrive 2](https://images.ctfassets.net/alneenqid6w5/Nhn2eGDJpBtVFFthvQZ7U/d51faa28f026a4255e20f25265770e43/Screenshot_2022-08-30_at_11-36-20_Pipedrive.png)
+![Pipedrive 2](//images.ctfassets.net/alneenqid6w5/Nhn2eGDJpBtVFFthvQZ7U/d51faa28f026a4255e20f25265770e43/Screenshot_2022-08-30_at_11-36-20_Pipedrive.png)
 
 Selecione o Pipedrive e clique em _**“integrar”**_.
 
 Clique em _**“Conectar”**_.
 
-![Pipedrive 3](https://images.ctfassets.net/alneenqid6w5/1g0sbuLweixaeJlazFhYFU/1168f8512f4aeb0cbde1b193caffe409/Screenshot_2022-08-30_at_11-36-25_Pipedrive.png)
+![Pipedrive 3](//images.ctfassets.net/alneenqid6w5/1g0sbuLweixaeJlazFhYFU/1168f8512f4aeb0cbde1b193caffe409/Screenshot_2022-08-30_at_11-36-25_Pipedrive.png)
 
 Faça o login na sua conta no Pipedrive
 
-![Pipedrive 4](https://images.ctfassets.net/alneenqid6w5/3TD2H7RDO8b0dqMvkqSJ4N/d4a63437da3d6cce788843c33ac9c173/Screenshot_2022-08-30_at_11-36-30_Pipedrive.png)
+![Pipedrive 4](//images.ctfassets.net/alneenqid6w5/3TD2H7RDO8b0dqMvkqSJ4N/d4a63437da3d6cce788843c33ac9c173/Screenshot_2022-08-30_at_11-36-30_Pipedrive.png)
 
 Autorize a conexão.
 
-![Pipedrive 5](https://images.ctfassets.net/alneenqid6w5/2kQRACyZzHp6Dw0VrHGXrc/5ae1be25734616fc3d4488621b13c272/Screenshot_2022-08-30_at_11-36-35_Pipedrive.png)
+![Pipedrive 5](//images.ctfassets.net/alneenqid6w5/2kQRACyZzHp6Dw0VrHGXrc/5ae1be25734616fc3d4488621b13c272/Screenshot_2022-08-30_at_11-36-35_Pipedrive.png)
 
 Selecione qual será o **Formulário de captura**  a ser conectado e qual será o usuário responsável. 
 
-![Pipedrive 6](https://images.ctfassets.net/alneenqid6w5/3CCTVLOTW1c1dMXTmwFNQG/9fbfe42bf7a3caf548b9ccfb7770f330/Screenshot_2022-08-30_at_11-36-39_Pipedrive.png)
+![Pipedrive 6](//images.ctfassets.net/alneenqid6w5/3CCTVLOTW1c1dMXTmwFNQG/9fbfe42bf7a3caf548b9ccfb7770f330/Screenshot_2022-08-30_at_11-36-39_Pipedrive.png)
 
 Defina qual será o pipeline que será enviado o Lead.
 
-![Pipedrive 7](https://images.ctfassets.net/alneenqid6w5/6E6RhqVHWwvGFmgCpMjga8/2e5add02161795cc1bc8abe9a676030e/Screenshot_2022-08-30_at_11-36-43_Pipedrive.png)
+![Pipedrive 7](//images.ctfassets.net/alneenqid6w5/6E6RhqVHWwvGFmgCpMjga8/2e5add02161795cc1bc8abe9a676030e/Screenshot_2022-08-30_at_11-36-43_Pipedrive.png)
 
 Defina o estágio.
 
-![Pipedrive 8](https://images.ctfassets.net/alneenqid6w5/6ReBh9zp1bL3Eqe5ibku1E/81b25ef6129bb6f68d38a949ebf7e991/Screenshot_2022-08-30_at_11-36-50_Pipedrive.png)
+![Pipedrive 8](//images.ctfassets.net/alneenqid6w5/6ReBh9zp1bL3Eqe5ibku1E/81b25ef6129bb6f68d38a949ebf7e991/Screenshot_2022-08-30_at_11-36-50_Pipedrive.png)
 
 Clique no botão _**“Salvar”**_. 
 
diff --git a/docs/tutorials/pt/piperun-suiteshare.md b/docs/tutorials/pt/piperun-suiteshare.md
index 725cdefc8..300dc29b0 100644
--- a/docs/tutorials/pt/piperun-suiteshare.md
+++ b/docs/tutorials/pt/piperun-suiteshare.md
@@ -21,11 +21,11 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Piperun**.
 
-   ![Piperun - Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/6FkPhokvfKkWwpjUMNF2MF/a2a8aa6ef4cfaa3cf39337769f94232c/Piperun_-_Suiteshare_1.png)
+   ![Piperun - Suiteshare_1](//images.ctfassets.net/alneenqid6w5/6FkPhokvfKkWwpjUMNF2MF/a2a8aa6ef4cfaa3cf39337769f94232c/Piperun_-_Suiteshare_1.png)
 
 2. Acesse **Configurações > Integrações > Piperun > Integrar**.
 
-   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
 Com a Piperun podemos ter duas integrações diferentes: **Integração estática** e **Integração dinâmica**. 
 
@@ -35,23 +35,23 @@ Com a Piperun podemos ter duas integrações diferentes: **Integração estáti
   <p>Na integração dinâmica, você envia os leads para um pipeline e estágio específico do seu funil e atribui a um usuário da sua conta PipeRun.</p>
 </div>
 
-![Piperun - Suiteshare_2](https://images.ctfassets.net/alneenqid6w5/5K6w6Kf2Y47ISe5j8umeIv/9a6b1f91d8d69ec27f1f85d799754af0/Piperun_-_Suiteshare_2.png)
+![Piperun - Suiteshare_2](//images.ctfassets.net/alneenqid6w5/5K6w6Kf2Y47ISe5j8umeIv/9a6b1f91d8d69ec27f1f85d799754af0/Piperun_-_Suiteshare_2.png)
 
 Selecione o [link de captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseje integrar. 
 
-![Piperun - Suiteshare_3](https://images.ctfassets.net/alneenqid6w5/GnzcGDKFpgtNECgfKS2nV/268f05e4d5f3a92b32e10402c004d084/Piperun_-_Suiteshare_3.png)
+![Piperun - Suiteshare_3](//images.ctfassets.net/alneenqid6w5/GnzcGDKFpgtNECgfKS2nV/268f05e4d5f3a92b32e10402c004d084/Piperun_-_Suiteshare_3.png)
 
 Agora, selecione qual o usuário que receberá o Lead.
 
-![Piperun - Suiteshare_4](https://images.ctfassets.net/alneenqid6w5/630ZqvavvlcCWKTAd9hcg6/3acb35f033142492ffb8fbb674631fb1/Piperun_-_Suiteshare_4.png)
+![Piperun - Suiteshare_4](//images.ctfassets.net/alneenqid6w5/630ZqvavvlcCWKTAd9hcg6/3acb35f033142492ffb8fbb674631fb1/Piperun_-_Suiteshare_4.png)
 
 Agora, defina para qual pipeline ele será direcionado.
 
-![Piperun - Suiteshare_5](https://images.ctfassets.net/alneenqid6w5/6DK6dpBefSKHOrJqkSiRRh/07cf8e08698b0d60a0aaf98fa0351ce5/Piperun_-_Suiteshare_5.png)
+![Piperun - Suiteshare_5](//images.ctfassets.net/alneenqid6w5/6DK6dpBefSKHOrJqkSiRRh/07cf8e08698b0d60a0aaf98fa0351ce5/Piperun_-_Suiteshare_5.png)
 
 Você ainda pode definir opcionais para esse lead, por exemplo: de onde ele veio, ou tags para sua identificação. 
 
-![Piperun - Suiteshare_6](https://images.ctfassets.net/alneenqid6w5/DiZTq34gfIsbs37JuhPka/3d689978d9fd79ebf28f5946eca086c8/Piperun_-_Suiteshare_6.png)
+![Piperun - Suiteshare_6](//images.ctfassets.net/alneenqid6w5/DiZTq34gfIsbs37JuhPka/3d689978d9fd79ebf28f5946eca086c8/Piperun_-_Suiteshare_6.png)
 
 Clique no botão **Salvar**.
 
@@ -61,31 +61,31 @@ Clique no botão **Salvar**.
   <p>Na integração estática, você envia os leads para um estágio específico do seu funil sem atribuir a nenhum usuário automaticamente.</p>
 </div>
 
-![Piperun - Suiteshare_7](https://images.ctfassets.net/alneenqid6w5/3adHKF0lGdefcI8eYzs3me/06cf495e6609100c1f06b944d80febff/Piperun_-_Suiteshare_7.png)
+![Piperun - Suiteshare_7](//images.ctfassets.net/alneenqid6w5/3adHKF0lGdefcI8eYzs3me/06cf495e6609100c1f06b944d80febff/Piperun_-_Suiteshare_7.png)
 
 Selecione o [Formulário de captura](http://help.suiteshare.com/support/solutions/articles/67000192044-formul%C3%A1rio-de-captura) que deseje integrar. 
 
-![Piperun - Suiteshare_8](https://images.ctfassets.net/alneenqid6w5/3EJtWkPa5Ks9r3uKgR5Jr/7592ef0a3e2a24f6bab3236f25c022c5/Piperun_-_Suiteshare_8.png)
+![Piperun - Suiteshare_8](//images.ctfassets.net/alneenqid6w5/3EJtWkPa5Ks9r3uKgR5Jr/7592ef0a3e2a24f6bab3236f25c022c5/Piperun_-_Suiteshare_8.png)
 
 Agora você precisa da HasH ID fornecida pela Piperun.
 
-![Piperun - Suiteshare_9](https://images.ctfassets.net/alneenqid6w5/1OyXRL50jrbBNqfwYbHqDe/8bbeaddb6a8498639c99e68921e6503f/Piperun_-_Suiteshare_9.png)
+![Piperun - Suiteshare_9](//images.ctfassets.net/alneenqid6w5/1OyXRL50jrbBNqfwYbHqDe/8bbeaddb6a8498639c99e68921e6503f/Piperun_-_Suiteshare_9.png)
 
 Acesse o painel da [Piperun](https://app.pipe.run/pipeline), clique no seu usuário e acesse [Ajustes](https://app.pipe.run/configuracao). 
 
-![Piperun - Suiteshare_10](https://images.ctfassets.net/alneenqid6w5/gXXMJ1MOmZpyQx2ZcFaEL/b4bc987bdfcfdf1ac448b2ec9e1bd4e1/Piperun_-_Suiteshare_10.png)
+![Piperun - Suiteshare_10](//images.ctfassets.net/alneenqid6w5/gXXMJ1MOmZpyQx2ZcFaEL/b4bc987bdfcfdf1ac448b2ec9e1bd4e1/Piperun_-_Suiteshare_10.png)
 
 Em **Oportunidades**, selecione a opção **Funis e etapas de funis**.
 
-![Piperun - Suiteshare_11](https://images.ctfassets.net/alneenqid6w5/7FdRYz6JrDMDJ9UorXeAdd/68b01e5931f8e1427289a6d184bc98d7/Piperun_-_Suiteshare_11.png)
+![Piperun - Suiteshare_11](//images.ctfassets.net/alneenqid6w5/7FdRYz6JrDMDJ9UorXeAdd/68b01e5931f8e1427289a6d184bc98d7/Piperun_-_Suiteshare_11.png)
 
 Selecione o funil e a etapa que deseja enviar esse cliente.
 
-![Piperun - Suiteshare_12](https://images.ctfassets.net/alneenqid6w5/7bPYfrubfoVFcLTWySDGpr/c0c49d2f10a9506e5d31844db8db89f6/Piperun_-_Suiteshare_12.png)
+![Piperun - Suiteshare_12](//images.ctfassets.net/alneenqid6w5/7bPYfrubfoVFcLTWySDGpr/c0c49d2f10a9506e5d31844db8db89f6/Piperun_-_Suiteshare_12.png)
 
 Copie a Hash fornecida pela Piperun. 
 
-![Piperun - Suiteshare_13](https://images.ctfassets.net/alneenqid6w5/4ZKN2T0Y2GHgzM3fw4ltEN/a251d7d53b4c8a4a8f57a06ec2835008/Piperun_-_Suiteshare_13.png)
+![Piperun - Suiteshare_13](//images.ctfassets.net/alneenqid6w5/4ZKN2T0Y2GHgzM3fw4ltEN/a251d7d53b4c8a4a8f57a06ec2835008/Piperun_-_Suiteshare_13.png)
 
 <div class="alert alert-danger">
   <p>Para copiar a Hash, é necessário clicar com o botão direito do mouse e selecione a opção copiar.</p>
@@ -93,7 +93,7 @@ Copie a Hash fornecida pela Piperun. 
 
 Você ainda pode definir opcionais para esse lead, por exemplo: de onde ele veio, ou tags para sua identificação. 
 
-![Piperun - Suiteshare_14](https://images.ctfassets.net/alneenqid6w5/7DvPeJlG1GyPD2oKQrJMxB/f44496bb6c7f7046c809ec994eb30413/Piperun_-_Suiteshare_14.png)
+![Piperun - Suiteshare_14](//images.ctfassets.net/alneenqid6w5/7DvPeJlG1GyPD2oKQrJMxB/f44496bb6c7f7046c809ec994eb30413/Piperun_-_Suiteshare_14.png)
 
 Clique no botão **Salvar**.
 
diff --git a/docs/tutorials/pt/pix-faq.md b/docs/tutorials/pt/pix-faq.md
index 86c27d648..5619d4d95 100644
--- a/docs/tutorials/pt/pix-faq.md
+++ b/docs/tutorials/pt/pix-faq.md
@@ -64,9 +64,9 @@ A opção de pagar via Pix aparecerá na lista, junto com as outras opções de
 
 Quando o usuário clicar no Pix, um QR Code que comporta as informações da compra será gerado. A partir daí, o usuário tem dez minutos para efetuar a transação com a sua instituição financeira de preferência.
 
-![Checkout_Pix](https://images.ctfassets.net/alneenqid6w5/8wd0gOpf8bsODhLIgZWSS/c57d465dca70e9362f3a3f9a485ae9ac/Checkout_Pix.png)
+![Checkout_Pix](//images.ctfassets.net/alneenqid6w5/8wd0gOpf8bsODhLIgZWSS/c57d465dca70e9362f3a3f9a485ae9ac/Checkout_Pix.png)
 
-![QRCode_Pix](https://images.ctfassets.net/alneenqid6w5/5aHNT7dd5nIXellY6L7Y74/97796620983d212cc6f063860df6734f/QRCode_Pix.png)
+![QRCode_Pix](//images.ctfassets.net/alneenqid6w5/5aHNT7dd5nIXellY6L7Y74/97796620983d212cc6f063860df6734f/QRCode_Pix.png)
 
 ### É possível dividir um pagamento entre Pix e outra forma de pagamento?
 
diff --git a/docs/tutorials/pt/plan-your-project.md b/docs/tutorials/pt/plan-your-project.md
index d217a930d..6990f87be 100644
--- a/docs/tutorials/pt/plan-your-project.md
+++ b/docs/tutorials/pt/plan-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Planeje seu projeto'
 id: tutorials_2546
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:54:42.370Z
-updatedAt: 2019-12-31T15:20:45.999Z
-publishedAt: 2019-12-31T15:20:45.999Z
+updatedAt: 2024-03-11T13:20:06.594Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:51.704Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/pt/planner-calendar-page-beta.md b/docs/tutorials/pt/planner-calendar-page-beta.md
index 9dccb8df1..2c51c91b8 100644
--- a/docs/tutorials/pt/planner-calendar-page-beta.md
+++ b/docs/tutorials/pt/planner-calendar-page-beta.md
@@ -39,7 +39,7 @@ O **Calendário** apresenta somente [lançamentos agendados](https://help.vtex.c
 
 A imagem a seguir apresenta a visualização por mês e identifica o que você pode realizar pela interface:
 
-![releases-calendar-monthly-view-pt](https://images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6f066a16c87c6bccc2ac229dd83cca4b/releases-calendar-monthly-view-pt.png)
+![releases-calendar-monthly-view-pt](//images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6f066a16c87c6bccc2ac229dd83cca4b/releases-calendar-monthly-view-pt.png)
 
 Nesta tela, é possível:
 
@@ -57,7 +57,7 @@ Nesta tela, é possível:
 
 A imagem a seguir apresenta a visualização por semana e identifica o que você pode realizar na interface:
 
-![releases-calendar-weekly-view-pt](https://images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/936efd12d08cbcc539bccfad7dc9da55/releases-calendar-weekly-view-pt.png)
+![releases-calendar-weekly-view-pt](//images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/936efd12d08cbcc539bccfad7dc9da55/releases-calendar-weekly-view-pt.png)
 
 Nesta tela, é possível:
 
@@ -75,7 +75,7 @@ Nesta tela, é possível:
 
 A imagem a seguir apresenta a visualização por dia e identifica o que você pode realizar na interface:
 
-![daily view v2 pt](https://images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/6b5ee0b8d3f0ede45eb8bc70b0c3f885/daily_view_v2_pt.png)
+![daily view v2 pt](//images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/6b5ee0b8d3f0ede45eb8bc70b0c3f885/daily_view_v2_pt.png)
 
 Além de visualizar informações sobre o lançamento, nesta tela, é possível:
 
diff --git a/docs/tutorials/pt/planner-releases-page-beta.md b/docs/tutorials/pt/planner-releases-page-beta.md
index 6416ee370..936d8613b 100644
--- a/docs/tutorials/pt/planner-releases-page-beta.md
+++ b/docs/tutorials/pt/planner-releases-page-beta.md
@@ -35,7 +35,7 @@ A ordenação dos lançamentos agendados é feita com base na data de publicaç
 
 Para acessar a página **Lançamentos** no Admin VTEX, vá no menu de navegação **Lançamentos**. A imagem a seguir apresenta a interface e identifica o que você pode realizar por meio dela:
 
-![Releases list view v2 - PT](https://images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/4dfbad1e1ee3bbf47ffd965472430291/Releases_list_view_v2_-_PT.png)
+![Releases list view v2 - PT](//images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/4dfbad1e1ee3bbf47ffd965472430291/Releases_list_view_v2_-_PT.png)
 
 | **Campo** | **Descrição** |
 |---|---|
diff --git a/docs/tutorials/pt/predefined-roles.md b/docs/tutorials/pt/predefined-roles.md
index ea3908685..f3a898be6 100644
--- a/docs/tutorials/pt/predefined-roles.md
+++ b/docs/tutorials/pt/predefined-roles.md
@@ -3,8 +3,8 @@ title: 'Perfis de acesso predefinidos'
 id: jGDurZKJHvHJS13LnO7Dy
 status: PUBLISHED
 createdAt: 2022-04-07T21:34:06.385Z
-updatedAt: 2023-06-06T21:37:23.798Z
-publishedAt: 2023-06-06T21:37:23.798Z
+updatedAt: 2024-05-22T17:50:31.567Z
+publishedAt: 2024-05-22T17:50:31.567Z
 firstPublishedAt: 2022-04-07T21:48:28.951Z
 contentType: tutorial
 productTeam: Identity
@@ -15,14 +15,20 @@ legacySlug:
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-Nesse documento listaremos os [perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#) que estão predefinidos para novas lojas VTEX. Para acessá-los diretamente, use a lista abaixo:
+[Perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#) agrupam [recursos do License Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#), sendo que cada recurso representa uma permissão na plataforma VTEX.
+
+Neste documento estão listados os perfis de acesso que estão predefinidos para novas lojas VTEX e respectivos recursos. Para acessá-los diretamente, use a lista abaixo.
+
+<div class = "alert alert-info">
+<p>Para saber mais sobre cada recurso listado nos perfis, veja o artigo <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">Recursos do License Manager</a>.</p>
+</div>
 
 * [Admin - Start page only](#admin-start-page-only)
 * [Checkout Admin](#checkout-admin)
 * [Call center operator](#call-center-operator)
 * [Finance](#finance)
 * [Finance - Full access](#finance-full-access)
-* [inStore Sales Person](#instore-sales-person)
+* [Sales App - Sales Associate](#sales-app-sales-associate)
 * [IntegrationProfile - Fulfillment](#integrationprofile-fulfillment)
 * [IntegrationProfile - Fulfillment Gateway](#integrationprofile-fulfillment-gateway)
 * [IntegrationProfile - Fulfillment Gateway GetOrder](#integrationprofile-fulfillment-gateway-getorder)
@@ -44,1143 +50,288 @@ Nesse documento listaremos os [perfis de acesso](https://help.vtex.com/pt/tutori
 
 Perfil básico que dá acesso à página inicial do ambiente administrativo. Mínimo necessário para que um usuário não seja recebido com uma mensagem de erro ao logar no ambiente administrativo.  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página de ajuda inicial</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Homepage | Catalog | Administração | Página inicial |
+| Help page | Catalog | Administração | Página de ajuda inicial |
 
 ## Checkout Admin
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Shopping Cart Full Access</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Full Access</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td>Access all orders</td>
-  </tr>
-  <tr>
-    <td>Order Cancelation</td>
-    <td>Checkout</td>
-    <td>CheckoutResources</td>
-    <td></td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Shopping Cart Full Access | Checkout | CheckoutResources |
+| Orders Full Access | Checkout | CheckoutResources | Access all orders |
+| Order Cancelation | Checkout | CheckoutResources |
 
 ## Call center operator
 
-Este é um perfil que tem características especiais. O recurso **Assisted Sales** causa o redirecionamento automático do usuário para a loja; isso deixará o usuário que fizer login numa conta com esse perfil sem acesso a recursos importantes do menu administrativo. Recomendamos a utilização de duas contas para usuários de televendas. Uma conta separada para o perfil **Call center operator** e uma para outras operações que o usuário possa precisar realizar no menu administrativo.
+Este é um perfil dedicado a operadores de televendas, pois concede acesso às [funcionalidades de televendas](https://help.vtex.com/pt/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS) da VTEX e permite visualizar pedidos.
+
+O recurso **Assisted Sales** causa o redirecionamento automático do usuário para a página de televendas da loja, o que deixará o usuário que fizer login numa conta com esse perfil sem acesso a recursos importantes do menu administrativo.
+
+Portanto, recomendamos a utilização de duas contas separadas (com emails distintos) para usuários de televendas: uma conta para o perfil __Call center operator__ (com os recursos <em>Assisted Sales</em> e <em>View order</em>) e outra conta para realizar operações no Admin, se necessário.
 
 <div class="alert alert-warning">
-  Ao criar um <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evite incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
+  Ao criar um <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil de acesso</a>, evite incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
 </div>
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Assisted Sales</td>
-    <td>Catalog</td>
-    <td>Televendas</td>
-    <td>Após o login o usuario é redirecionado para o site de televendas www.sualoja.com.br/a/televendas. Dessa forma, o operador pode fazer operações na loja em nome do cliente. Uma barra aparecerá no topo da tela.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de pedidos no OMS.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Assisted Sales | Catalog | Televendas | Funcionalidades de televendas. Após o login, o usuário é redirecionado para o site de televendas www.{nomedaloja}.com.br/a/televendas. Dessa forma, o operador pode utilizar as funcionalidades de televendas, como navegar na loja em nome do cliente.Como este recurso causa o redirecionamento automático para a loja, o usuário que fizer login em uma conta com esse perfil não terá acesso a recursos importantes do Admin. |
+| View order | OMS | AcessoOMS | Permite a visualização de pedidos no OMS. |
 
 ## Finance  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>UI - Account list</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-  <tr>
-    <td>Invoices List</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização das notas fiscais.</td>
-  </tr>
-  <tr>
-    <td>Edit Company Information</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite editar dados de uma Company.</td>
-  </tr>
-  <tr>
-    <td>Contracts List</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Visualização de todos os contratos (ativos e inativos) de uma company.</td>
-  </tr>
-  <tr>
-    <td>Display Company info</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Permite visualizar dados de uma Company.</td>
-  </tr>
-  <tr>
-    <td>Contacts List</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização da lista de Contatos que recebem notificação por email da cobrança gerada.</td>
-  </tr>
-  <tr>
-    <td>Edit Contacts</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite editar contatos que recebem notificação da cobrança gerada.</td>
-  </tr>
-  <tr>
-    <td>Generate new Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Financeiro pode gerar uma cobrança na Nota Fiscal manualmente através dos contratos.</td>
-  </tr>
-  <tr>
-    <td>Recalc Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Gerar nova cobrança com juros. Sim, com juros.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| UI - Account list | License Manager | Controle de Acesso Web |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| View store sales stats | OMS | AcessoOMS | Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos. |
+| Invoices List | Billing | Invoice | Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização das notas fiscais. |
+| Edit Company Information | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite editar dados de uma Company. |
+| Contracts List | Billing | Contracts | Clientes, responsáveis de billing e financeiro tem acesso. Visualização de todos os contratos (ativos e inativos) de uma company. |
+| Display Company info | Billing | Company | Clientes, responsáveis de billing e financeiro tem acesso. Permite visualizar dados de uma Company. |
+| Contacts List | Billing | Contacts | Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização da lista de Contatos que recebem notificação por email da cobrança gerada. |
+| Edit Contacts | Billing | Contacts | Somente responsáveis de billing e financeiro tem acesso. Permite editar contatos que recebem notificação da cobrança gerada. |
+| Generate new Invoice | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Financeiro pode gerar uma cobrança na Nota Fiscal manualmente através dos contratos. |
+| Recalc Invoice | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Gerar nova cobrança com juros. Sim, com juros. |
 
 ## Finance - Full access  
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Save account</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Serviços</td>
-    <td>Salva uma conta</td>
-  </tr>
-  <tr>
-    <td>Get account by identifier</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Serviços</td>
-    <td>Consulta que retorna conta pelo identificador, que pode ser o id da conta ou a host da aplicação da conta</td>
-  </tr>
-  <tr>
-    <td>UI - Account list</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>UI - Edit account</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>UI - Edit role</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Web</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-  <tr>
-    <td>Invoices List</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização das notas fiscais.</td>
-  </tr>
-  <tr>
-    <td>Edit Company Information</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite editar dados de uma Company.</td>
-  </tr>
-  <tr>
-    <td>Contracts List</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Visualização de todos os contratos (ativos e inativos) de uma company.</td>
-  </tr>
-  <tr>
-    <td>Display Company info</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Permite visualizar dados de uma Company.</td>
-  </tr>
-  <tr>
-    <td>Contacts List</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização da lista de Contatos que recebem notificação por email da cobrança gerada.</td>
-  </tr>
-  <tr>
-    <td>Edit Contacts</td>
-    <td>Billing</td>
-    <td>Contacts</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite editar contatos que recebem notificação da cobrança gerada.</td>
-  </tr>
-  <tr>
-    <td>Generate new Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Financeiro pode gerar uma cobrança na Nota Fiscal manualmente através dos contratos.</td>
-  </tr>
-  <tr>
-    <td>Edit Company's Document</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite editar os dados de documento (CNPJ ou CPF) da Company, pra onde a fatura será gerada.</td>
-  </tr>
-  <tr>
-    <td>Add Account</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite adicionar conta (account) para agrupar outras contas já vinculadas a esse cliente em um billing só.</td>
-  </tr>
-  <tr>
-    <td>Delete Account</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite deletar conta associada a uma company. Company é a entidade criada para englobar diversas accounts da mesma loja.</td>
-  </tr>
-  <tr>
-    <td>Save contracts</td>
-    <td>Billing</td>
-    <td>Contracts</td>
-    <td>Somente responsáveis de billing, sales operations/growth e financeiro tem acesso. Permite criar novo contrato.</td>
-  </tr>
-  <tr>
-    <td>Cancel Invoice Document</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Cancelar documento fiscal nas prefeituras, dá poder de cancelar documento fiscal mesmo já tendo sido gerada a nota.</td>
-  </tr>
-  <tr>
-    <td>Issue Invoice Document</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Usado quando em casos específicos de países que não tem geração de documento fiscal automaticamente, dependendo do sistema financeiro. Nesse caso, pode ser gerado manualmente.</td>
-  </tr>
-  <tr>
-    <td>Conciliate Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. O default é marcar como pago automaticamente, mas o cliente pode pagar por fora, dependendo da negociação. Nesse caso, o financeiro tem o poder de marcar como pago manualmente, conciliando as Notas fiscais.</td>
-  </tr>
-  <tr>
-    <td>Generate Invoice Overdue without Interest</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Gerar nova cobrança com juros. Sim, com juros.</td>
-  </tr>
-  <tr>
-    <td>Cancel Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Cancelar cobrança no billing, dá poder de cancelar nota fiscal mesmo já tendo sido gerada.</td>
-  </tr>
-  <tr>
-    <td>Change payment status</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Financeiro tem poder de Mudar status de pagamento de uma company, dependendo da negociação que fizer com o cliente.</td>
-  </tr>
-  <tr>
-    <td>Recalc Invoice</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Gerar nova cobrança com juros. Sim, com juros.</td>
-  </tr>
-  <tr>
-    <td>Get Unscrewed Dashboard Charges</td>
-    <td>Billing</td>
-    <td>Dashboard</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Acesso a dashboard externo ao Admin, que visualiza notas fiscais emitidas nesse momento, e quais accounts são provisionadas nesse momento.</td>
-  </tr>
-  <tr>
-    <td>Merge companies</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite a fusão entre duas companies, unificando seu billing.</td>
-  </tr>
-  <tr>
-    <td>Split companies</td>
-    <td>Billing</td>
-    <td>Company</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Permite separar uma company única, em companies diferentes.</td>
-  </tr>
-  <tr>
-    <td>Unpaid invoices</td>
-    <td>Billing</td>
-    <td>Invoice</td>
-    <td>Somente responsáveis de billing e financeiro tem acesso. Financeiro pode desmarcar o pagamento de uma cobrança manualmente, caso não tenha sido feito, ou feito equivocadamente.</td>
-  </tr>
-  <tr>
-    <td>Get App</td>
-    <td>Log</td>
-    <td>Log Admin</td>
-    <td>Uso interno da VTEX.</td>
-  </tr>
-  <tr>
-    <td>Create Table</td>
-    <td>Log</td>
-    <td>Log Admin</td>
-    <td>Uso interno da VTEX.</td>
-  </tr>
-</table>
-
-## inStore Sales Person  
-
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Product Form</td>
-    <td>Catalog</td>
-    <td>Conteúdo</td>
-    <td>Access to product screen</td>
-  </tr>
-  <tr>
-    <td>Store Texts</td>
-    <td>Catalog</td>
-    <td>Configurações</td>
-    <td>Ferramenta do desenvolvedor com todos os textos base da loja</td>
-  </tr>
-  <tr>
-    <td>Assisted Sales</td>
-    <td>Catalog</td>
-    <td>Televendas</td>
-    <td>Após o login o usuário é redirecionado para a loja (accountname.myvtex.com)</td>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página de ajuda inicial</td>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera uma transação.</td>
-  </tr>
-  <tr>
-    <td>Manage Store</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ManageStore</td>
-    <td>Allows modifying configuration settings</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite informar faturas (NF) e dados para rastreio manualmente no OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite Cancelar pedido no OMS.</td>
-  </tr>
-  <tr>
-    <td>Full access in all documents</td>
-    <td>Dynamic Storage</td>
-    <td>Recursos genéricos para o Dynamic Storage</td>
-    <td>Recurso registrado automaticamente pelo Dynamic Storage.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Save account | License Manager | Controle de Acesso Serviços | Salva uma conta |
+| Get account by identifier | License Manager | Controle de Acesso Serviços | Consulta que retorna conta pelo identificador, que pode ser o id da conta ou a host da aplicação da conta |
+| UI - Account list | License Manager | Controle de Acesso Web |
+| UI - Edit account | License Manager | Controle de Acesso Web |
+| UI - Edit role | License Manager | Controle de Acesso Web |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| View store sales stats | OMS | AcessoOMS | Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos. |
+| Invoices List | Billing | Invoice | Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização das notas fiscais. |
+| Edit Company Information | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite editar dados de uma Company. |
+| Contracts List | Billing | Contracts | Clientes, responsáveis de billing e financeiro tem acesso. Visualização de todos os contratos (ativos e inativos) de uma company. |
+| Display Company info | Billing | Company | Clientes, responsáveis de billing e financeiro tem acesso. Permite visualizar dados de uma Company. |
+| Contacts List | Billing | Contacts | Clientes, responsáveis de billing e financeiro tem acesso. Permite a visualização da lista de Contatos que recebem notificação por email da cobrança gerada. |
+| Edit Contacts | Billing | Contacts | Somente responsáveis de billing e financeiro tem acesso. Permite editar contatos que recebem notificação da cobrança gerada. |
+| Generate new Invoice | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Financeiro pode gerar uma cobrança na Nota Fiscal manualmente através dos contratos. |
+| Edit Company's Document | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite editar os dados de documento (CNPJ ou CPF) da Company, pra onde a fatura será gerada. |
+| Add Account | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite adicionar conta (account) para agrupar outras contas já vinculadas a esse cliente em um billing só. |
+| Delete Account | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite deletar conta associada a uma company. Company é a entidade criada para englobar diversas accounts da mesma loja. |
+| Save contracts | Billing | Contracts | Somente responsáveis de billing, sales operations/growth e financeiro tem acesso. Permite criar novo contrato. |
+| Cancel Invoice Document | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Cancelar documento fiscal nas prefeituras, dá poder de cancelar documento fiscal mesmo já tendo sido gerada a nota. |
+| Issue Invoice Document | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Usado quando em casos específicos de países que não tem geração de documento fiscal automaticamente, dependendo do sistema financeiro. Nesse caso, pode ser gerado manualmente. |
+| Conciliate Invoice | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. O default é marcar como pago automaticamente, mas o cliente pode pagar por fora, dependendo da negociação. Nesse caso, o financeiro tem o poder de marcar como pago manualmente, conciliando as Notas fiscais. |
+| Generate Invoice Overdue without Interest | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Gerar nova cobrança com juros. Sim, com juros. |
+| Cancel Invoice | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Cancelar cobrança no billing, dá poder de cancelar nota fiscal mesmo já tendo sido gerada. |
+| Change payment status | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Financeiro tem poder de Mudar status de pagamento de uma company, dependendo da negociação que fizer com o cliente. |
+| Recalc Invoice | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Gerar nova cobrança com juros. Sim, com juros. |
+| Get Unscrewed Dashboard Charges | Billing | Dashboard | Somente responsáveis de billing e financeiro tem acesso. Acesso a dashboard externo ao Admin, que visualiza notas fiscais emitidas nesse momento, e quais accounts são provisionadas nesse momento. |
+| Merge companies | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite a fusão entre duas companies, unificando seu billing. |
+| Split companies | Billing | Company | Somente responsáveis de billing e financeiro tem acesso. Permite separar uma company única, em companies diferentes. |
+| Unpaid invoices | Billing | Invoice | Somente responsáveis de billing e financeiro tem acesso. Financeiro pode desmarcar o pagamento de uma cobrança manualmente, caso não tenha sido feito, ou feito equivocadamente. |
+| Get App | Log | Log Admin | Uso interno da VTEX. |
+| Create Table | Log | Log Admin | Uso interno da VTEX. |
+
+## Sales App - Sales Associate
+
+<div class="alert alert-warning">
+  <p>Vendedores registrados no Sales App não têm acesso ao Admin VTEX, apenas ao Sales App.</p>
+</div>
+
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Assisted Sales | Catalog | Televendas | Após o login o usuário é redirecionado para a loja (accountname.myvtex.com) |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera uma transação. |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| Cancel order | OMS | AcessoOMS | Permite Cancelar pedido no OMS. |
 
 ## IntegrationProfile - Fulfillment
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Place Orders | VTEX Fulfilment | Fulfilment Resources | |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources | |
 
 ## IntegrationProfile - Fulfillment Gateway
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera uma transação.</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite Cancelar pedido no OMS.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Represents the payment gateway transactional operations. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera uma transação. |
+| Notify payment | OMS | AcessoOMS | Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido. |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Cancel order | OMS | AcessoOMS | Permite Cancelar pedido no OMS. |
 
 ## IntegrationProfile - Fulfillment Gateway GetOrder
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera uma transação.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Represents the payment gateway transactional operations. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera uma transação. |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
 
 ## IntegrationProfile - Fulfillment Gateway Oms
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Make Payments</td>
-    <td>PCI Gateway</td>
-    <td>Payment-MakePayments</td>
-    <td>Represents the payment gateway transactional operations.</td>
-  </tr>
-  <tr>
-    <td>View Payment Data</td>
-    <td>PCI Gateway</td>
-    <td>Payment-ViewPaymentData</td>
-    <td>Recupera uma transação.</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite informar faturas (NF) e dados para rastreio manualmente no OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Notify reemburse</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite notificar uma nota fiscal de entrada, indicando a entrada novamente de algo que foi reembolsado. Permite o input de uma nota de devolução.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite Cancelar pedido no OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite que o usuário se inscreva para receber atualizações dos status dos pedidos no Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite registrar mudanças no pedido (descontos e/ou trocas)</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Make Payments | PCI Gateway | Payment-MakePayments | Represents the payment gateway transactional operations. |
+| View Payment Data | PCI Gateway | Payment-ViewPaymentData | Recupera uma transação. |
+| Change order workflow status | OMS | AcessoOMS | Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow |
+| Notify payment | OMS | AcessoOMS | Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido. |
+| Notify invoice | OMS | AcessoOMS | Permite informar faturas (NF) e dados para rastreio manualmente no OMS. |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Notify reemburse | OMS | AcessoOMS | Permite notificar uma nota fiscal de entrada, indicando a entrada novamente de algo que foi reembolsado. Permite o input de uma nota de devolução. |
+| Cancel order | OMS | AcessoOMS | Permite Cancelar pedido no OMS. |
+| Order feed subscription | OMS | AcessoOMS | Permite que o usuário se inscreva para receber atualizações dos status dos pedidos no Order Feed. |
+| Change order | OMS | AcessoOMS | Permite registrar mudanças no pedido (descontos e/ou trocas) |
+| View store sales stats | OMS | AcessoOMS | Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos. |
 
 ## IntegrationProfile - Fulfillment Oms
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite informar faturas (NF) e dados para rastreio manualmente no OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>Place Orders</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-  <tr>
-    <td>Notify reemburse</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite notificar uma nota fiscal de entrada, indicando a entrada novamente de algo que foi reembolsado. Permite o input de uma nota de devolução.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite Cancelar pedido no OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite que o usuário se inscreva para receber atualizações dos status dos pedidos no Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite registrar mudanças no pedido (descontos e/ou trocas)</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Change order workflow status | OMS | AcessoOMS | Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow |
+| Notify payment | OMS | AcessoOMS | Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido. |
+| Notify invoice | OMS | AcessoOMS | Permite informar faturas (NF) e dados para rastreio manualmente no OMS. |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| List Orders | OMS | AcessoOMS | Permite listar todos os pedidos da conta. |
+| Place Orders | VTEX Fulfilment | Fulfilment Resources |
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources |
+| Notify reemburse | OMS | AcessoOMS | Permite notificar uma nota fiscal de entrada, indicando a entrada novamente de algo que foi reembolsado. Permite o input de uma nota de devolução. |
+| Cancel order | OMS | AcessoOMS | Permite Cancelar pedido no OMS. |
+| Order feed subscription | OMS | AcessoOMS | Permite que o usuário se inscreva para receber atualizações dos status dos pedidos no Order Feed. |
+| Change order | OMS | AcessoOMS | Permite registrar mudanças no pedido (descontos e/ou trocas) |
+| View store sales stats | OMS | AcessoOMS | Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos. |
 
 ## IntegrationProfile - OrderSimulation
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Orders Detail</td>
-    <td>VTEX Fulfilment</td>
-    <td>Fulfilment Resources</td>
-    <td></td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Orders Detail | VTEX Fulfilment | Fulfilment Resources | |
 
 ## Logistics - Full access
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página de ajuda inicial</td>
-  </tr>
-  <tr>
-    <td>Logistics full access</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite acesso pleno a todos os recursos de logística (visualização, criação, edição e cancelamento de configurações)</td>
-  </tr>
-  <tr>
-    <td>Logistics viewer</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permissão de visualização da área inicial do módulo de logistica.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory full access</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite acesso pleno ao inventário logístico (visualização, criação, edição e cancelamento de configurações).</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory read only</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite somente a visualização do módulo de inventário.</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping full access</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite acesso pleno a todas as funções de envio do módulo de logística (criação, edição e cancelamento de configurações).</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping read only</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>testar</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Homepage | Catalog | Administração | Página inicial |
+| Help page | Catalog | Administração | Página de ajuda inicial |
+| Logistics full access | Logistics | Acesso ao Logistics | Permite acesso pleno a todos os recursos de logística (visualização, criação, edição e cancelamento de configurações) |
+| Logistics viewer | Logistics | Acesso ao Logistics | Permissão de visualização da área inicial do módulo de logistica. |
+| Logistics inventory full access | Logistics | Acesso ao Logistics | Permite acesso pleno ao inventário logístico (visualização, criação, edição e cancelamento de configurações). |
+| Logistics inventory read only | Logistics | Acesso ao Logistics | Permite somente a visualização do módulo de inventário. |
+| Logistics shipping full access | Logistics | Acesso ao Logistics | Permite acesso pleno a todas as funções de envio do módulo de logística (criação, edição e cancelamento de configurações). |
+| Logistics shipping read only | Logistics | Acesso ao Logistics |  |
 
 ## Logistics - Read only
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Logistics viewer</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permissão de visualização da área inicial do módulo de logistica.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory read only</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite somente a visualização do módulo de inventário.</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping read only</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>testar</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Logistics viewer | Logistics | Acesso ao Logistics | Permissão de visualização da área inicial do módulo de logistica. |
+| Logistics inventory read only | Logistics | Acesso ao Logistics | Permite somente a visualização do módulo de inventário. |
+| Logistics shipping read only | Logistics | Acesso ao Logistics | testar |
 
 ## OMS - Full access
 
 Tabela de recursos:
 
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Home-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página inicial</td>
-  </tr>
-  <tr>
-    <td>Help-page</td>
-    <td>Catalog</td>
-    <td>Administração</td>
-    <td>Página de ajuda inicial</td>
-  </tr>
-  <tr>
-    <td>Change order workflow status</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow</td>
-  </tr>
-  <tr>
-    <td>Notify payment</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido.</td>
-  </tr>
-  <tr>
-    <td>Notify invoice</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite informar faturas (NF) e dados para rastreio manualmente no OMS.</td>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>Logistics full access</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite acesso pleno a todos os recursos de logística (visualização, criação, edição e cancelamento de configurações)</td>
-  </tr>
-  <tr>
-    <td>Notify reemburse</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite notificar uma nota fiscal de entrada, indicando a entrada novamente de algo que foi reembolsado. Permite o input de uma nota de devolução.</td>
-  </tr>
-  <tr>
-    <td>Cancel order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite Cancelar pedido no OMS.</td>
-  </tr>
-  <tr>
-    <td>Order feed subscription</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite que o usuário se inscreva para receber atualizações dos status dos pedidos no Order Feed.</td>
-  </tr>
-  <tr>
-    <td>Change order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite registrar mudanças no pedido (descontos e/ou trocas)</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-  <tr>
-    <td>Logistics inventory full access</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite acesso pleno ao inventário logístico (visualização, criação, edição e cancelamento de configurações).</td>
-  </tr>
-  <tr>
-    <td>Logistics shipping full access</td>
-    <td>Logistics</td>
-    <td>Acesso ao Logistics</td>
-    <td>Permite acesso pleno a todas as funções de envio do módulo de logística (criação, edição e cancelamento de configurações).</td>
-  </tr>
-</table>
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Home-page | Catalog | Administração | Página inicial |
+| Help-page | Catalog | Administração | Página de ajuda inicial |
+| Change order workflow status | OMS | AcessoOMS | Permite acesso às ações dentro do workflow pra mudança de status de pedido, através do botão de Ações no Workflow |
+| Notify payment | OMS | AcessoOMS | Acesso ao botão que notifica pagamento ao gateway manualmente na área de pagamento dentro do pedido. |
+| Notify invoice | OMS | AcessoOMS | Permite informar faturas (NF) e dados para rastreio manualmente no OMS. |
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| Logistics full access | Logistics | Acesso ao Logistics | Permite acesso pleno a todos os recursos de logística (visualização, criação, edição e cancelamento de configurações) |
+| Notify reemburse | OMS | AcessoOMS | Permite notificar uma nota fiscal de entrada, indicando a entrada novamente de algo que foi reembolsado. Permite o input de uma nota de devolução. |
+| Cancel order | OMS | AcessoOMS | Permite Cancelar pedido no OMS. |
+| Order feed subscription | OMS | AcessoOMS | Permite que o usuário se inscreva para receber atualizações dos status dos pedidos no Order Feed. |
+| Change order | OMS | AcessoOMS | Permite registrar mudanças no pedido (descontos e/ou trocas) |
+| View store sales stats | OMS | AcessoOMS | Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos. |
+| Logistics inventory full access | Logistics | Acesso ao Logistics | Permite acesso pleno ao inventário logístico (visualização, criação, edição e cancelamento de configurações). |
+| Logistics shipping full access | Logistics | Acesso ao Logistics | Permite acesso pleno a todas as funções de envio do módulo de logística (criação, edição e cancelamento de configurações). |
 
 ## OMS - Read only
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>View order</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Permite a visualização de todos os pedidos no OMS.</td>
-  </tr>
-  <tr>
-    <td>View store sales stats</td>
-    <td>OMS</td>
-    <td>AcessoOMS</td>
-    <td>Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| View order | OMS | AcessoOMS | Permite a visualização de todos os pedidos no OMS. |
+| View store sales stats | OMS | AcessoOMS | Exibe totalizadores dentro da seção Todos os pedidos do Gerenciamento de pedidos. Exibe total de vendas além dos detalhes dos pedidos. |
 
 ## Seller Manager
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>View Seller</td>
-    <td>Seller Register</td>
-    <td>Seller Administration</td>
-    <td>Allows view all sellers from account</td>
-  </tr>
-  <tr>
-    <td>Save Seller</td>
-    <td>Seller Register</td>
-    <td>Seller Administration</td>
-    <td>Allows to create and edit all sellers from account</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| View Seller | Seller Register | Seller Administration | Allows view all sellers from account |
+| Save Seller | Seller Register | Seller Administration | Allows to create and edit all sellers from account |
 
 ## User Administrator - RESTRICTED
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Save user</td>
-    <td>License Manager</td>
-    <td>Services access control</td>
-    <td>Criar usuários, atribuir ou remover perfis de acesso para usuários, editar dados de usuários, criar e alterar chaves de aplicação.</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Save user | License Manager | Services access control | Criar usuários, atribuir ou remover perfis de acesso para usuários, editar dados de usuários, criar e alterar chaves de aplicação. |
 
 ## VTEX IO Admin
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Get resource by key</td>
-    <td>License Manager</td>
-    <td>Controle de Acesso Serviços</td>
-    <td>Checa permissões de acesso</td>
-  </tr>
-  <tr>
-    <td>Read Workspace Apps</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading the apps installed in the workspace and their direct and indirect dependencies.</td>
-  </tr>
-  <tr>
-    <td>Link App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows listing existing links and linking and unlinking apps.</td>
-  </tr>
-  <tr>
-    <td>Install App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows installation and uninstallation of apps.</td>
-  </tr>
-  <tr>
-    <td>Vbase Read Only</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Read-only access to vbase.</td>
-  </tr>
-  <tr>
-    <td>Vbase Read Write</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Read and write access to vbase.</td>
-  </tr>
-  <tr>
-    <td>Read Workspace Services</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading the infra apps in the workspace.</td>
-  </tr>
-  <tr>
-    <td>Install Service</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows installation and uninstallation of apps</td>
-  </tr>
-  <tr>
-    <td>Log Access - Read-only</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading logs from all applications</td>
-  </tr>
-  <tr>
-    <td>Read Published Service</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows reading the services data from the infra registry</td>
-  </tr>
-  <tr>
-    <td>Debug App</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows connecting a debugger to a linked app</td>
-  </tr>
-  <tr>
-    <td>Workspace CRUD</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Allows creating, deleting and modifying workspaces</td>
-  </tr>
-  <tr>
-    <td>Import Redirects</td>
-    <td>VTEX IO</td>
-    <td>Infrastructure</td>
-    <td>Enable user to manage redirects with VTEX IO's command line interface</td>
-  </tr>
-  <tr>
-    <td>Manage A/B Test</td>
-    <td>VTEX IO</td>
-    <td>A/B Test</td>
-    <td>Allow to start, finish or get status of a A/B Test</td>
-  </tr>
-  <tr>
-    <td>Read logs</td>
-    <td>Application Logs Stream</td>
-    <td>Logs</td>
-    <td>Read logs from VTEX IO apps owned from this account</td>
-  </tr>
-</table>
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Get resource by key | License Manager | Controle de Acesso Serviços | Checa permissões de acesso |
+| Read Workspace Apps | VTEX IO | Infrastructure | Allows reading the apps installed in the workspace and their direct and indirect dependencies. |
+| Link App | VTEX IO | Infrastructure | Allows listing existing links and linking and unlinking apps. |
+| Install App | VTEX IO | Infrastructure | Allows installation and uninstallation of apps. |
+| Vbase Read Only | VTEX IO | Infrastructure | Read-only access to vbase. |
+| Vbase Read Write | VTEX IO | Infrastructure | Read and write access to vbase. |
+| Read Workspace Services | VTEX IO | Infrastructure | Allows reading the infra apps in the workspace. |
+| Install Service | VTEX IO | Infrastructure | Allows installation and uninstallation of apps |
+| Log Access - Read-only | VTEX IO | Infrastructure | Allows reading logs from all applications |
+| Read Published Service | VTEX IO | Infrastructure | Allows reading the services data from the infra registry |
+| Debug App | VTEX IO | Infrastructure | Allows connecting a debugger to a linked app |
+| Workspace CRUD | VTEX IO | Infrastructure | Allows creating, deleting and modifying workspaces |
+| Import Redirects | VTEX IO | Infrastructure | Enable user to manage redirects with VTEX IO's command line interface |
+| Manage A/B Test | VTEX IO | A/B Test | Allow to start, finish or get status of a A/B Test |
+| Read logs | Application Logs Stream | Logs | Read logs from VTEX IO apps owned from this account |
 
 ## VTEX Payment - Account Holder
 
@@ -1192,20 +343,9 @@ Este perfil possibilita a leitura de informações sobre a operação do VTEX Pa
 
 ## Webservice - Full access
 
-&nbsp;&nbsp;&nbsp;&nbsp;Tabela de recursos:
-
-<table>
-  <tr>
-    <th bgcolor="#efefef" >Nome do recurso</th>
-    <th bgcolor="#efefef" >Produto</th>
-    <th bgcolor="#efefef" >Categoria</th>
-    <th bgcolor="#efefef" >Descrição</th>
-  </tr>
-  <tr>
-    <td>Webservice access</td>
-    <td>WebService</td>
-    <td>webservice</td>
-    <td>Permission to use any SOAP request</td>
-  </tr>
-</table>    
+Tabela de recursos:
+
+| Nome do recurso | Produto | Categoria | Descrição |
+|---|---|---|---|
+| Webservice access | WebService | webservice | Criar, editar e deletar informações do catálogo por meio do WebService. |
 
diff --git a/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md b/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md
index c36cef3d3..d6d79788a 100644
--- a/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md
+++ b/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md
@@ -3,8 +3,8 @@ title: 'Como impedir que uma transportadora atenda determinada faixa de CEP?'
 id: 6GEYG5p9E4MOEy2qmY4uGa
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:39.807Z
-updatedAt: 2023-03-29T14:15:58.885Z
-publishedAt: 2023-03-29T14:15:58.885Z
+updatedAt: 2024-03-01T01:07:45.930Z
+publishedAt: 2024-03-01T01:07:45.930Z
 firstPublishedAt: 2019-01-24T22:03:33.994Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -33,3 +33,7 @@ Para isso, siga estes passos:
 4. Cada uma dessas linhas deve ser transformada em duas, de modo que o CEP 45920-000 seja ignorado. Portanto, você passaria a ter: `ZipCodeStart` = __37900-001__ e `ZipCodeEnd` = __45919-999__ / `ZipCodeStart` = __45920-001__ e `ZipCodeEnd` = __97904-999__.  
 
 Com isso, a planilha passaria a "pular" o CEP 45920-000. E consequentemente ele deixaria de ser considerado como opção de endereço atendido por essa transportadora.
+
+<div class = "alert alert-info">
+Os exemplos de código postal deste artigo são referentes ao Brasil, cada país tem o seu próprio formato de código postal.
+</div>
diff --git a/docs/tutorials/pt/price-divergence-rule.md b/docs/tutorials/pt/price-divergence-rule.md
index 90bc990c6..d607c80b2 100644
--- a/docs/tutorials/pt/price-divergence-rule.md
+++ b/docs/tutorials/pt/price-divergence-rule.md
@@ -3,8 +3,8 @@ title: 'Regra de Divergência de valores'
 id: 6RlFLhD1rIRRshl83KnCjW
 status: PUBLISHED
 createdAt: 2021-12-25T20:10:25.853Z
-updatedAt: 2023-03-29T21:53:14.071Z
-publishedAt: 2023-03-29T21:53:14.071Z
+updatedAt: 2024-03-22T15:11:31.300Z
+publishedAt: 2024-03-22T15:11:31.300Z
 firstPublishedAt: 2021-12-25T21:05:20.600Z
 contentType: tutorial
 productTeam: Channels
@@ -29,7 +29,7 @@ A regra de Divergência de valores é composta de uma ou mais regras de autoriza
 - **Negar automaticamente:** pedidos com diferença de preço até a porcentagem definida são automaticamente recusados e não são integrados.
 - **Criar uma tarefa no VTEX DO para aprovação:** para diferenças de preço dentro do intervalo configurado, o pedido é integrado, mas fica pendente de [autorização manual](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#autorizar-pedidos-manualmente) por parte de um usuário habilitado.
 
-![print_1_PT](https://drive.google.com/uc?export=download&id=1GqQINM-uP0UnRrKZ7CxAqrkWEy-1tXkK)
+![price_divergence_rules_PT](//images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/f3858b3abbc1be86fd281ba357198e3f/price_divergence_rules_PT.png)
 
 Quando a [configuração de uma regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) não foi feita, pedidos com erro de divergência de preço são aprovados automaticamente. Isso vale para marketplaces VTEX, marketplaces externos e conectores certificados (parceiros), mas não para [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex).
 
diff --git a/docs/tutorials/pt/price-divergence-rules-beta.md b/docs/tutorials/pt/price-divergence-rules-beta.md
index 567ff984e..1f70a6ca7 100644
--- a/docs/tutorials/pt/price-divergence-rules-beta.md
+++ b/docs/tutorials/pt/price-divergence-rules-beta.md
@@ -60,7 +60,7 @@ Para criar as regras, siga os passos abaixo:
    * É criada uma regra configurada automaticamente com percentual de divergência entre 0% a 30%, correspondente à barra azul claro.
 6. Para aumentar ou diminuir o percentual de divergência, clique na barra e arraste-a pelas extremidades, menos “<” ou para mais “>”.
 7. Escolha entre as seguintes ações de regras para pedidos: `Autorizar automaticamente`, `Negar automaticamente` ou `Criar Uma Tarefa no VTEX DO para Aprovação`.
-8. Para criar a 2ª regra, clique no ícone <img class="shadow-4" src="https://https://images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> e repita os passos 6 e 7.
+8. Para criar a 2ª regra, clique no ícone <img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" /> e repita os passos 6 e 7.
 11. Clique em `Salvar Regras`.
 
 Durante o processo de criação de regras, são apresentadas as seguintes abas:
diff --git a/docs/tutorials/pt/price-table-management-in-b2b-organizations.md b/docs/tutorials/pt/price-table-management-in-b2b-organizations.md
new file mode 100644
index 000000000..315c975d7
--- /dev/null
+++ b/docs/tutorials/pt/price-table-management-in-b2b-organizations.md
@@ -0,0 +1,46 @@
+---
+title: 'Gerenciamento de tabelas de preços em organizações B2B '
+id: 1iNpulqvLT2KJ2fnznpN4L
+status: PUBLISHED
+createdAt: 2024-06-25T18:44:58.230Z
+updatedAt: 2024-06-25T19:14:38.840Z
+publishedAt: 2024-06-25T19:14:38.840Z
+firstPublishedAt: 2024-06-25T19:14:38.840Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gerenciamento-de-tabelas-de-precos-em-organizacoes-b2b
+locale: pt
+legacySlug: gerenciamento-de-tabelas-de-precos-em-organizacoes-b2b
+subcategory: 3b0iTwoSQZq9m3Z2ezbWLd
+---
+
+As [tabelas de preços](https://help.vtex.com/pt/tutorial/criar-tabelas-de-precos?locale=pt) em uma operação B2B da VTEX são fundamentais para personalizar as condições comerciais oferecidas a diferentes organizações. Com elas, você pode:
+- Definir os preços específicos para os produtos.
+- Criar e gerenciar múltiplas tabelas de preços.
+- Garantir que cada cliente veja o valor correto conforme sua categoria.
+
+Veja como gerenciar suas tabelas de preços nas seções a seguir:
+- [Associar a tabela de preços à organização](#associar-a-tabela-de-preços-a-organização)
+- [Remover a associação da tabela de preços](#remover-a-associação-da-tabela-de-preços)
+
+## Associar a tabela de preços à organização
+Na VTEX, uma organização é uma entidade que representa uma empresa. Para associar tabelas de preços a uma organização, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar sua página de detalhes.
+3. Nessa página de detalhes, clique na aba **Tabelas de preços**.
+4. Selecione as tabelas de preços desejadas na lista de **Disponível**.
+5. Clique em `ADICIONAR À ORG` para incluí-la em sua organização.
+6. Clique em `Salvar` no canto superior direito da página.
+
+## Remover a associação da tabela de preços
+Para remover a associação de tabelas de preços de uma organização, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Organizações**, ou digite **Organizações** na barra de busca no topo da página.
+2. Clique no nome da organização desejada para acessar sua página de detalhes.
+3. Nessa página de detalhes, clique na aba **Tabelas de preços**.
+4. Selecione as tabelas de preços desejadas na lista de **Atribuído à organização**.
+5. Clique em `REMOVER DA ORG`.
+6. Clique em `Salvar` no canto superior direito da página.
+
diff --git a/docs/tutorials/pt/price-waterfall.md b/docs/tutorials/pt/price-waterfall.md
index 65432c9c0..9e65102f7 100644
--- a/docs/tutorials/pt/price-waterfall.md
+++ b/docs/tutorials/pt/price-waterfall.md
@@ -21,7 +21,7 @@ Com essa nova feature, temos agora uma nova entidade de preço chamada *Preços
 
 O gráfico abaixo explica como funciona a cascata de preços:
 
-![Cascata de Preço](https://images.ctfassets.net/alneenqid6w5/4Dh0ulBDFCEs8WuuigSsoY/3cfeccdf7b8d690a026533fbcbc699b0/cascataPreco.png)
+![Cascata de Preço](//images.ctfassets.net/alneenqid6w5/4Dh0ulBDFCEs8WuuigSsoY/3cfeccdf7b8d690a026533fbcbc699b0/cascataPreco.png)
 
 Quando um preço para um SKU é solicitado ao módulo de *Pricing*:
 1. Um *Preço Fixo* é selecionado em seus critérios como **agendamento** e **quantidade mínima**
diff --git a/docs/tutorials/pt/prices-data-pipeline-beta.md b/docs/tutorials/pt/prices-data-pipeline-beta.md
new file mode 100644
index 000000000..8a67e097b
--- /dev/null
+++ b/docs/tutorials/pt/prices-data-pipeline-beta.md
@@ -0,0 +1,91 @@
+---
+title: 'Preços Data Pipeline (Beta)'
+id: 3NMGJ8dtv73Bwvo9PSz1fz
+status: PUBLISHED
+createdAt: 2024-06-21T14:58:43.084Z
+updatedAt: 2024-06-21T16:20:22.452Z
+publishedAt: 2024-06-21T16:20:22.452Z
+firstPublishedAt: 2024-06-21T15:27:43.768Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: precos-data-pipeline-beta
+locale: pt
+legacySlug: precos-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+O conjunto de dados de preços contém informações históricas de preços para cada SKU da loja de um comerciante, permitindo a análise dos valores de markup e das tendências mensais de preços.
+
+Neste artigo você encontra as seguintes informações:
+[Características dos dados](#caracteristicas-dos-dados)
+[Tabela pricing_latest](#tabela-pricing-latest)
+[Tabela pricing_historical](#tabela-pricing-historical)
+[Análise com dados de preços](#analise-com-dados-de-precos)
+[Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados
+| **Característica** | **Descrição** |
+|:------:|:--------:|
+| Origem do dado | Módulo de preços. |
+| Disponibilidade | VTEX Admin e APIs de preços. É importante ressaltar que os dados disponibilizados pela API podem não estar estruturados exatamente como neste conjunto de dados do Data Pipeline. |
+| Histórico | O histórico de dados começa em agosto de 2023. Para clientes que já usam a plataforma VTEX, os dados são retidos por dois anos a partir de 2024.|
+| Menor intervalo de atualização possível | Uma hora. | 
+
+## Tabela pricing_latest  
+
+A tabela `pricing_latest` contém dados dos preços atuais dos produtos da loja. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna**  | **Tipo de Coluna** 	| **Descrição da Coluna**  |
+|:--------:|:--------:|:-----------:|
+| account_name | character varying(255) 	| Nome da conta relacionada ao item. |
+| last_date | date 	| Data e hora da última alteração no preço. |
+| sku_id | character varying(255) | Identificador do SKU. |
+| batch_id  | character varying(255) 	| Identificador usado quando os dados são carregados na tabela para controle de qualidade da ingestão de dados. |
+| listPrice | double precision | Preço de lista do SKU. |
+| costPrice | double precision | Preço de custo do SKU. |
+| markup  | double precision 	| Markup do SKU. |
+| basePrice| double precision | Preço-base do SKU. |
+| fixedPrices| super | Preço fixo.|
+
+## Tabela: pricing_historical
+
+A tabela `pricing_historical` apresenta registro histórico dos preços da sua loja. Veja abaixo seguir os campos que compõem essa tabela.  
+
+| **Nome da coluna**  | **Tipo de coluna**  | **Descrição da coluna** |
+|:--------:|:---------:|:----------:|
+| account_name | character varying(255) | Nome da conta relacionada ao item. |
+| date | date  | Data e hora da última alteração no preço. |
+| sku_id | character varying(255) 	| Identificador do SKU. |
+| author_id | character varying(255) 	| Identificação do usuário que fez a alteração de preço. |
+| batch_id | character varying(255) | Identificador usado quando os dados são carregados na tabela para controle de qualidade da ingestão de dados. |
+| id | character varying(255) | ID da alteração de preço. |
+| listPrice | double precision | Preço de lista do SKU. |
+| costPrice | double precision	| Preço de custo do SKU. |
+| markup | double precision| Markup do SKU. |
+| basePrice | double precision | Preço-base do SKU.|
+| fixedPrices | super | Preço fixo.  |
+
+## Análise com dados de preços
+
+Os dados de preços podem ser empregados nas seguintes análises:  
+
+- __Preço atual do SKU:__ avalie o preço atual para um SKU específico ou para toda uma gama de produtos.  
+- __Histórico de preços do SKU:__ analise o histórico de preços para um SKU específico ou para toda uma gama de produtos.  
+- __Preço do SKU por conta:__ para lojas com múltiplas contas VTEX, estes dados ajudam a comparar preços em várias lojas.  
+
+## Correlações com outros dados  
+
+O conjunto de dados de preços possui correlações com os seguintes conjuntos do ecossistema de dados da VTEX:  
+
+- **Interação com dados de pedidos:** analisar dados de pedidos conjuntamente fornece insights valiosos sobre vendas de um produto em função do preço, permitindo uma análise de elasticidade.  
+- **Relação com o inventário:** a integração com dados de inventário capacita você a avaliar com precisão o valor total de seus ativos.  
+- **Impacto da taxa de conversão:** ao analisar dados de navegação e funil de conversão, você pode entender o impacto do preço nas taxas de conversão.  
+
+### Conheça outros Conjuntos de dados
+
+- [Inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)  
+- [Navegação](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd)   
+- [Pagamentos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv) 
+- [Promoção](https://help.vtex.com/tutorial/promocoes-data-pipeline-beta--3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/pt/prices-settings.md b/docs/tutorials/pt/prices-settings.md
index ab5df71fc..ddb03c239 100644
--- a/docs/tutorials/pt/prices-settings.md
+++ b/docs/tutorials/pt/prices-settings.md
@@ -3,8 +3,8 @@ title: 'Configurações de preços'
 id: 3hbBtCzNUBrj8GaWgCtSWN
 status: PUBLISHED
 createdAt: 2020-10-14T18:43:49.750Z
-updatedAt: 2023-03-29T20:45:21.665Z
-publishedAt: 2023-03-29T20:45:21.665Z
+updatedAt: 2023-08-21T17:13:42.982Z
+publishedAt: 2023-08-21T17:13:42.982Z
 firstPublishedAt: 2020-10-22T19:38:48.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,7 +15,7 @@ legacySlug: configuracao-de-precos
 subcategory: 3O1NvPgBPqE0qU88MSQaie
 ---
 
-A página *Configuração de loja > Produto > Configuração de preços* no Admin VTEX permite alterar configurações gerais de precificação forma prática e rápida.
+A página **Configuração de loja > Produto > Configuração de preços** no Admin VTEX permite alterar configurações gerais de precificação forma prática e rápida.
 
 Você pode definir o markup padrão e o limite de variação de preço da sua loja. Aqui também é possível herdar preços da conta-pai e sobrescrever os preços de sellers com os da sua conta.
 
diff --git a/docs/tutorials/pt/prices.md b/docs/tutorials/pt/prices.md
index efffb60c3..e61675840 100644
--- a/docs/tutorials/pt/prices.md
+++ b/docs/tutorials/pt/prices.md
@@ -3,8 +3,8 @@ title: 'Preços'
 id: tutorials_4393
 status: PUBLISHED
 createdAt: 2017-04-27T21:50:28.982Z
-updatedAt: 2021-12-20T21:12:57.515Z
-publishedAt: 2021-12-20T21:12:57.515Z
+updatedAt: 2023-08-21T17:24:39.459Z
+publishedAt: 2023-08-21T17:24:39.459Z
 firstPublishedAt: 2017-04-27T23:11:16.737Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,8 +15,8 @@ legacySlug: precos-v2
 subcategory: 3pGCbMh80UueoeSqoAgSuS
 ---
 
-Na nova versão da lista de preços, o gerenciamento dos preços é realizado no *módulo Pricing*. 
-O módulo que cuida das taxas e promoções da plataforma VTEX é o *Promoções e Taxas*.
+Na nova versão da lista de preços, o gerenciamento dos preços é realizado no módulo Preços. 
+O módulo que cuida das taxas e promoções da plataforma VTEX é o Promoções.
 
 Algumas das vantagens da nova lista de preços são:
 
diff --git a/docs/tutorials/pt/product-list.md b/docs/tutorials/pt/product-list.md
index 8cbbf143b..d28c201da 100644
--- a/docs/tutorials/pt/product-list.md
+++ b/docs/tutorials/pt/product-list.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Produtos'
 id: 49vxWqoaWRZC4atwLz6cMg
 status: PUBLISHED
 createdAt: 2021-04-12T15:21:30.529Z
-updatedAt: 2023-03-24T14:24:33.863Z
-publishedAt: 2023-03-24T14:24:33.863Z
+updatedAt: 2023-11-22T13:59:30.669Z
+publishedAt: 2023-11-22T13:59:30.669Z
 firstPublishedAt: 2021-04-12T18:21:27.025Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 A página **Produtos** permite visualizar e gerenciar a lista completa de produtos cadastrados na sua loja, simplificando a gestão do catálogo no Seller Portal. Você pode acessar a página através do menu **Catálogo** no Admin VTEX.
 
-![product-list-pt](https://images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/7d149b1193674dad3407a94652dcd669/product-list-pt.png)
+![product-list-pt](//images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/7d149b1193674dad3407a94652dcd669/product-list-pt.png)
 
 A partir da lista de produtos, você pode realizar uma variedade de ações:
 
@@ -30,6 +30,8 @@ A partir da lista de produtos, você pode realizar uma variedade de ações:
 
 Ao clicar no botão `CRIAR PRODUTO`, você abrirá a página para cadastro de um novo produto no catálogo. Acesse o artigo [Como criar um produto](https://help.vtex.com/pt/tutorial/como-criar-um-produto-beta--671zAWe0B9eCikzDu7kB1G) para saber como realizar esse procedimento.
 
+<div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+
 ## Buscar produtos
 
 Para localizar um produto específico, você pode digitar a ID ou o nome do produto na barra de busca acima da lista de produtos. Os resultados da pesquisa são atualizados em tempo real, ou seja, enquanto você digita, a lista de produtos exibidos é atualizada de acordo com o termo buscado.
diff --git a/docs/tutorials/pt/products-and-skus-beta.md b/docs/tutorials/pt/products-and-skus-beta.md
index 179878d1a..3f604c98d 100644
--- a/docs/tutorials/pt/products-and-skus-beta.md
+++ b/docs/tutorials/pt/products-and-skus-beta.md
@@ -3,8 +3,8 @@ title: 'Produtos e SKUs (Beta)'
 id: 2ig7TmROlirWirZjFWZ3By
 status: PUBLISHED
 createdAt: 2022-11-30T17:55:25.970Z
-updatedAt: 2023-05-09T22:11:41.664Z
-publishedAt: 2023-05-09T22:11:41.664Z
+updatedAt: 2023-07-11T15:12:54.179Z
+publishedAt: 2023-07-11T15:12:54.179Z
 firstPublishedAt: 2022-11-30T19:04:31.183Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -21,7 +21,7 @@ subcategory: 6XPsLadoT3moZ7eTduCg3c
 
 A página **Produtos e SKUs** possibilita visualizar e gerenciar a lista completa de produtos cadastrados na sua loja, incluindo informações sobre SKUs, data da última atualização e status. Para acessá-la, entre no menu **Catálogo > Produtos e SKUs**.
 
-![produtos-skus-pt](https://images.ctfassets.net/alneenqid6w5/1XLBRg7olhbAUmgkD6kb7K/46b067813ff58d78ebccde46c37b8079/produtos-skus-pt.PNG)
+![products-skus-pt](//images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/42eb4310fbe66a016176c54adb447ad9/products-skus-pt.png)
 
 <div class="alert alert-info">
   <p>Esta página está disponível somente para lojas que estão operando com o <a href="https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">Novo Admin VTEX</a>. Para acessar esta página e fazer parte de uma nova experiência, participe do <a href="https://content.vtex.com/participe-do-programa-beta-pt/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> do Novo Admin VTEX.</p>
@@ -42,10 +42,8 @@ A partir da lista de produtos, você pode visualizar as seguintes informações:
 
 | **Coluna** | **Descrição** |
 |----|----|
-| **Nome** | Nome que identifica o produto, definido na etapa de criação do produto. Abaixo do nome, a página exibe a ID, ou seja, o código identificador único do produto. |
-| **SKUs** | Exibe a opção `Mostrar SKUs` e, entre parênteses, a quantidade de SKUs cadastrados para o produto. Para mais detalhes sobre essa opção, leia a seção [Visualizar lista de SKUs](#visualizar-lista-de-skus). <br/><br/> Para deixar de visualizar os SKUs referentes a um produto, clique no botão `Ocultar SKUs`. |
+| **Nome** | Nome que identifica o produto, definido na etapa de criação. Abaixo do nome, a página exibe a ID, ou seja, o código identificador único do produto. <br/><br/> Ao lado do nome, cada linha exibe uma seta <i class="fas fa-chevron-right"></i> para [visualizar a lista de SKUs](#visualizar-lista-de-skus) associados ao produto, um ícone de [status do produto](#acompanhar-status-de-produtos) e a imagem cadastrada para o produto. |
 | **Última atualização** | Data da [indexação](https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao--tutorials_256) mais recente do produto. Para visualizar detalhes sobre esse processo, confira a seção [Ver informações de indexação](#ver-informacoes-de-indexacao). |
-| **Status** | Situação atual do produto. Confira os status possíveis na seção [Acompanhar status de produtos](#acompanhar-status-de-produtos).|
 
 ## Criar produto
 
@@ -65,7 +63,7 @@ Para localizar um produto específico, você pode digitar um dos seguintes dados
 
 Em seguida, clique no critério que você deseja utilizar para a busca, conforme ilustrado na imagem a seguir:
 
-![facelift-product-search-pt](https://images.ctfassets.net/alneenqid6w5/PCBjrNpVcVr5Z4x3RdTgW/83ece197b90922dac3fcad64b312294e/facelift-product-search-pt.gif)
+![products-skus-search-pt](//images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/7a04a740e895558318b88b2b00dd6949/search-pt.gif)
 
 A lista de produtos exibida será atualizada de acordo com sua busca. 
 
@@ -103,9 +101,9 @@ Para visualizar o status dos SKUs de um produto, leia a seção [Visualizar list
 
 ## Visualizar lista de SKUs
 
-Ao clicar em `Ver SKUs` na linha de um produto da lista, a plataforma exibe uma lista com todos os SKUs cadastrados para aquele produto.
+Ao clicar na seta <i class="fas fa-chevron-right"></i> na linha de um produto da lista, a plataforma exibe uma lista com todos os SKUs cadastrados para aquele produto.
 
-![sku-quick-actions-pt](https://images.ctfassets.net/alneenqid6w5/71pxP9DeCFZ9UrQdl67r9X/b75ddd51b11d3e3d9ab199be1a011f84/sku-quick-actions-pt.gif)
+![sku-actions-pt](//images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/dfbd3240bd021d0c91ca42f80a36ddd4/sku-actions-pt.gif)
 
 Na lista de SKUs, é possível identificar as informações a seguir:
 
@@ -118,6 +116,8 @@ Na lista de SKUs, é possível identificar as informações a seguir:
 * **Nome:** nome do SKU.
 * <svg xmlns="http://www.w3.org/2000/svg" width="1.25rem" height="1.25rem" fill="currentColor" viewBox="0 0 256 256" class=" admin-ui-c-dnTJPl"><rect width="16rem" height="16rem" fill="none"></rect><path d="M224,177.32117V78.67873a8,8,0,0,0-4.07791-6.9726l-88-49.5a8,8,0,0,0-7.84418,0l-88,49.5A8,8,0,0,0,32,78.67873v98.64244a8,8,0,0,0,4.07791,6.97261l88,49.5a8,8,0,0,0,7.84418,0l88-49.5A8,8,0,0,0,224,177.32117Z" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></path><polyline points="222.897 74.626 128.949 128 33.108 74.617" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></polyline><line x1="128.94915" y1="127.99996" x2="128.01036" y2="234.82127" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line></svg> &nbsp; <strong>Editar inventário:</strong> conduz para a tela de gerenciamento de inventário no Admin VTEX, para alterar a quantidade do SKU disponível para a venda em estoque. Confira o artigo [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) para mais informações.
 * <svg xmlns="http://www.w3.org/2000/svg" width="1.25rem" height="1.25rem" fill="currentColor" viewBox="0 0 256 256" class=" admin-ui-c-dnTJPl"><rect width="16rem" height="16rem" fill="none"></rect><line x1="128" y1="72" x2="128" y2="88" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line><line x1="128" y1="168" x2="128" y2="184" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></line><circle cx="128" cy="128" r="96" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></circle><path d="M104,168h36a20,20,0,0,0,0-40H116a20,20,0,0,1,0-40h36" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="18"></path></svg> &nbsp;<strong>Editar preços:</strong> conduz para a **Lista de preços** no Admin VTEX, para alterar os preços cadastrados para o SKU.
+* <i class="far fa-clone"></i> __Copiar código do SKU:__ copia o ID do SKU para a área de transferência.
+* <i class="far fa-eye"></i> __Ativar__ / <i class="far fa-eye-slash"></i> __Desativar:__ torna o SKU ativo ou inativo na loja.
 
 ## Editar produtos
 
@@ -148,7 +148,7 @@ Ao clicar no menu <i class="fas fa-ellipsis-v"></i> na linha de um produto e opt
 
 Esta aba do modal exibe a lista de SKUs associados ao produto e suas respectivas informações indexadas.
 
-![catalog-price-inventory-pt](https://images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/6ae475a3c76de0310e1fc08b8d087312/preco-inventario-pt.PNG)
+![catalog-price-inventory-pt](//images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/6ae475a3c76de0310e1fc08b8d087312/preco-inventario-pt.PNG)
 
 Ao clicar na seta `>` na linha de cada SKU, você pode visualizar uma tabela com as as seguintes informações:
 
@@ -163,7 +163,7 @@ Ao clicar na seta `>` na linha de cada SKU, você pode visualizar uma tabela com
 
 Esta aba do modal apresenta o log, ou seja, o registro técnico detalhado da indexação referente ao produto e aos SKUs relacionados.
 
-![indexed-log-pt](https://images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/1d3d2899be6f6fb3b6b3aa8b993d71a4/log-indexacao-pt.PNG)
+![indexed-log-pt](//images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/1d3d2899be6f6fb3b6b3aa8b993d71a4/log-indexacao-pt.PNG)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/products-errors-in-the-amazon-integration.md b/docs/tutorials/pt/products-errors-in-the-amazon-integration.md
index 389aab02d..215aa47a3 100644
--- a/docs/tutorials/pt/products-errors-in-the-amazon-integration.md
+++ b/docs/tutorials/pt/products-errors-in-the-amazon-integration.md
@@ -57,7 +57,7 @@ O erro ocorre quando a [categoria global](https://help.vtex.com/pt/tutorial/conf
 
 Esse erro ocorre quando a [especificação](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) **Cor** não foi mapeada na [planilha de mapeamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP/5xklf2wSdeztQh4iy5kJvD#4-planilha-de-mapeamento). Você deverá revisar o cadastro desta especificação no [produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) e no [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) para solucioná-lo. Para revisar o cadastro da especificação no Produto, acesse o Admin VTEX, clique em *Produtos > Catálogo > Produtos e SKUs*, selecione o produto e clique em `Alterar`. Clique na aba `Especificações` e identifique o campo **Cor** com a informação já preenchida.
 
-Para revisar o cadastro da especificação no SKU, acesse o Admin VTEX, clique em *Produtos > Catálogo > Produtos e SKUs*, selecione o produto, clique na seta <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6p43gQ8LMQitieDuUlBoiC/c7d43ef209986769bdaf1e2795408a96/alterar_seta.JPG" /> e selecione a opção SKU. Na aba `Especificações`, identifique o campo que utiliza Cor como atributo. Depois, preencha a planilha de mapeamento com as especificações de cor que precisam ser mapeadas.
+Para revisar o cadastro da especificação no SKU, acesse o Admin VTEX, clique em *Produtos > Catálogo > Produtos e SKUs*, selecione o produto, clique na seta <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6p43gQ8LMQitieDuUlBoiC/c7d43ef209986769bdaf1e2795408a96/alterar_seta.JPG" /> e selecione a opção SKU. Na aba `Especificações`, identifique o campo que utiliza Cor como atributo. Depois, preencha a planilha de mapeamento com as especificações de cor que precisam ser mapeadas.
 
 ### Mensagens de erro
 
diff --git a/docs/tutorials/pt/promotion-alerts-beta.md b/docs/tutorials/pt/promotion-alerts-beta.md
index 0e8d70641..daf2cd423 100644
--- a/docs/tutorials/pt/promotion-alerts-beta.md
+++ b/docs/tutorials/pt/promotion-alerts-beta.md
@@ -29,7 +29,7 @@ Se você configurar apenas a ação de alerta por email, outros pedidos com o de
 
 Para acessar a página no Admin VTEX, acesse *Promoções > Alerta de promoções*. A seguinte interface vai aparecer:
 
-![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
+![simuladordepromocoes gerenciar](//images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
 
 A tabela a seguir apresenta a descrição das colunas da listagem de promoções:
 
diff --git a/docs/tutorials/pt/promotion-list-beta.md b/docs/tutorials/pt/promotion-list-beta.md
index dca896db8..1875344d9 100644
--- a/docs/tutorials/pt/promotion-list-beta.md
+++ b/docs/tutorials/pt/promotion-list-beta.md
@@ -3,8 +3,8 @@ title: 'Lista de Promoções'
 id: 4yB7nNdliiFxBTXE19GCIi
 status: PUBLISHED
 createdAt: 2022-05-05T13:39:53.273Z
-updatedAt: 2023-03-02T15:34:23.200Z
-publishedAt: 2023-03-02T15:34:23.200Z
+updatedAt: 2023-07-24T13:34:09.177Z
+publishedAt: 2023-07-24T13:34:09.177Z
 firstPublishedAt: 2022-05-05T13:52:17.590Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -30,7 +30,7 @@ A página apresenta a lista com as promoções cadastradas na sua loja e suas in
 | `Até` | Data de término da promoção. |
 | `Status` | Status da promoção, que pode estar: <p> __Ativa:__ quando a promoção está ativada.</p> <p>__Programada:__ quando a promoção foi programada.</p> <p>__Pausada:__ quando a promoção estiver pausada. <p>__Finalizada:__ quando a promoção foi encerrada.</p> |
 
-![listadepromocoes pt](https://images.ctfassets.net/alneenqid6w5/3vT0P63t0Kvm2heipqfpsT/5f4e74dae8d76243d8214588c2db247a/listadepromocoes_pt.gif)
+![listadepromocoes pt](//images.ctfassets.net/alneenqid6w5/3vT0P63t0Kvm2heipqfpsT/5f4e74dae8d76243d8214588c2db247a/listadepromocoes_pt.gif)
 
 Você pode ordenar a exibição das promoções a partir do nome, das datas ou do status da promoção. Para isso, clique no título da coluna com a informação que você deseja utilizar como critério de ordenação.
 
@@ -82,7 +82,7 @@ O arquivo contém as seguintes informações sobre cada promoção:
 
 ## Uso das promoções
 
-![usodaspromoções pt](https://images.ctfassets.net/alneenqid6w5/6kpAz3b5vxOjIb8o9Aouxe/2c9b92564afeadbeb777b04813fbe0fa/usodaspromo____es_pt.JPG)
+![usodaspromoções pt](//images.ctfassets.net/alneenqid6w5/6kpAz3b5vxOjIb8o9Aouxe/2c9b92564afeadbeb777b04813fbe0fa/usodaspromo____es_pt.JPG)
 
 Para visualizar o total de promoções ativas na sua loja e a cota de espaço restante para novas promoções, clique em `Uso das promoções`.
 
@@ -90,7 +90,7 @@ O número máximo padrão de promoções ativas é 100. Caso precise aumentar es
 
 ## Filtrar promoções
 
-![filtrodepromocoes pt](https://images.ctfassets.net/alneenqid6w5/3flpyzIkBlYDiuhYLea8nu/6e57eb53961b821b54233964711fe4d4/filtrodepromocoes_pt.gif)
+![filtrodepromocoes pt](//images.ctfassets.net/alneenqid6w5/3flpyzIkBlYDiuhYLea8nu/6e57eb53961b821b54233964711fe4d4/filtrodepromocoes_pt.gif)
 
 A lista de promoções pode ser filtrada conforme a sua necessidade. A filtragem da lista pode ser feita pelos filtros a seguir: 
 
@@ -106,7 +106,7 @@ Selecione os filtros desejados e clique em `Aplicar` para filtrar as promoções
 
 Ao clicar no ícone <i class="fas fa-ellipsis-v"></i> de uma promoção, você pode realizar as seguintes ações:
 
-- <i class="far fa-times-circle"></i> __Editar:__ editar a promoção.
+- <i class="fas fa-pencil-alt"></i> __Editar:__ editar a promoção.
 - <i class="far fa-check-circle"></i> __Ativar:__ ativar a promoção.
 - <i class="far fa-clone"></i> __Duplicar:__ criar uma cópia da promoção.
 - <i class="fas fa-archive"></i> __Arquivar:__ arquivar a promoção. A promoção será movida automaticamente para a página *[Promoções arquivadas](#promocoes-arquivadas)*.
diff --git a/docs/tutorials/pt/promotion-summary.md b/docs/tutorials/pt/promotion-summary.md
index 8fcd3a2cd..d2b315db6 100644
--- a/docs/tutorials/pt/promotion-summary.md
+++ b/docs/tutorials/pt/promotion-summary.md
@@ -63,7 +63,7 @@ O resumo da promoção pode exibir três tipos diferentes de alertas. Veja as de
 Alertas de alto risco indicam configurações ou falhas de preenchimento críticas que precisam ser revistas, pois podem comprometer negativamente a atuação da promoção e, consequentemente, a margem de operação da loja.
 
 Exemplo:
-![alert-alto-risco-PT](https://images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/3f4a74d3d0222b13056831b2e941e8dd/image.png)
+![alert-alto-risco-PT](//images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/3f4a74d3d0222b13056831b2e941e8dd/image.png)
 
 ### Médio risco
 Alertas de médio risco apresentam avisos de configurações que podem causar efeitos indesejados na promoção.
diff --git a/docs/tutorials/pt/promotions-beta.md b/docs/tutorials/pt/promotions-beta.md
index bc6ceb792..2036ac5b2 100644
--- a/docs/tutorials/pt/promotions-beta.md
+++ b/docs/tutorials/pt/promotions-beta.md
@@ -33,20 +33,20 @@ A página inicial apresenta a lista de promoções em uma grade que permite visu
 - Duplicar ou arquivar promoções através do botão <i class="fas fa-ellipsis-v"></i>
 - Gerenciar as condições da promoção clicando em qualquer parte da linha do grid (veja [Nova promoção](#nova-promocao) para detalhamento das condições da promoção).
 
-![promobeta1 acoes lista promocoes PT](https://images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/75ce08a03318ebe1cf47d3a01b5b7c62/promobeta1_acoes_lista_promocoes_PT.gif)
+![promobeta1 acoes lista promocoes PT](//images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/75ce08a03318ebe1cf47d3a01b5b7c62/promobeta1_acoes_lista_promocoes_PT.gif)
 
 A lista de promoções pode ser filtrada e ordenada conforme a sua necessidade. A filtragem da lista pode ser feita por *Efeito*, *Estado*, *Data início*, *Data fim* ou *Política comercial*.
 
-![promobeta2 filtros lista promocoes PT](https://images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/8bbb1eefeee7a0f8b4c6c8746249481f/promobeta2_filtros_lista_promocoes_PT.gif)
+![promobeta2 filtros lista promocoes PT](//images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/8bbb1eefeee7a0f8b4c6c8746249481f/promobeta2_filtros_lista_promocoes_PT.gif)
 
 A ordenação pode ser crescente ou decrescente a partir das informações básicas da promoção, bastando clicar sobre o título.
 
-![promobeta3 ordenacao lista promocoes PT](https://images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/1c13ddd465a09fe39561b685a1dbe35f/promobeta3_ordenacao_lista_promocoes_PT.gif)
+![promobeta3 ordenacao lista promocoes PT](//images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/1c13ddd465a09fe39561b685a1dbe35f/promobeta3_ordenacao_lista_promocoes_PT.gif)
 
 ## Nova promoção
 Na tela inicial, clique no botão **NOVA PROMOÇÃO** para acessar a página de criação de promoções, na qual você vai preencher uma variedade de campos para configurar as condições desejadas para a sua promoção.
 
-![promobeta4 botao novapromocao PT](https://images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/e336ee376b77685d357999e5bd6430d2/promobeta4_botao_novapromocao_PT.png)
+![promobeta4 botao novapromocao PT](//images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/e336ee376b77685d357999e5bd6430d2/promobeta4_botao_novapromocao_PT.png)
 
 As condições da nova promoção, bem como os campos da tela, estão separados por grupos, sendo eles:
 
diff --git a/docs/tutorials/pt/promotions-overview.md b/docs/tutorials/pt/promotions-overview.md
index f0c345aa8..641aa208f 100644
--- a/docs/tutorials/pt/promotions-overview.md
+++ b/docs/tutorials/pt/promotions-overview.md
@@ -3,8 +3,8 @@ title: 'Visão Geral Promoções'
 id: 3PeHVYcooLIDmA33IAnjhm
 status: PUBLISHED
 createdAt: 2023-03-29T19:29:50.947Z
-updatedAt: 2023-03-29T19:33:24.646Z
-publishedAt: 2023-03-29T19:33:24.646Z
+updatedAt: 2023-09-13T22:35:44.331Z
+publishedAt: 2023-09-13T22:35:44.331Z
 firstPublishedAt: 2023-03-29T19:31:43.053Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -19,8 +19,6 @@ Uma promoção é um desconto concedido ao cliente, associado a um ou mais produ
 
 No menu **Promoções** do seu Admin renovado é possível configurar uma promoção com restrições de listas de produtos, listas de clientes, intervalos de CEP, valor mínimo de carrinho, entre outros.
 
-![visao-geral-promo-PT](//images.contentful.com/alneenqid6w5/6FHow2OrXNqAoiKaJngwPU/e6c0704b75773a551767099f014774dc/image.png)
-
 Confira abaixo mais detalhes sobre as diferentes seções e páginas deste menu.
 
 ## Promoções
diff --git a/docs/tutorials/pt/promotions-simulator-beta.md b/docs/tutorials/pt/promotions-simulator-beta.md
index 224a7ef21..d89a7e6f6 100644
--- a/docs/tutorials/pt/promotions-simulator-beta.md
+++ b/docs/tutorials/pt/promotions-simulator-beta.md
@@ -1,10 +1,10 @@
 ---
-title: 'Simulador de Promoções (Beta)'
+title: 'Simulador de Promoções '
 id: 4zc8SNqjqeIJ0ZRMhjlnvy
 status: PUBLISHED
 createdAt: 2022-09-13T21:22:59.620Z
-updatedAt: 2022-09-27T19:37:29.437Z
-publishedAt: 2022-09-27T19:37:29.437Z
+updatedAt: 2024-03-13T19:31:16.281Z
+publishedAt: 2024-03-13T19:31:16.281Z
 firstPublishedAt: 2022-09-13T22:59:58.058Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -12,96 +12,92 @@ author: 46G4yHIZerH7B9Jo0Iw5KI
 slug: simulador-de-promocoes-beta
 locale: pt
 legacySlug: simulador-de-promocoes-beta
-subcategory: 6iTRZiMeCGXYiO2ckABFZi
+subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-<div class = "alert alert-info">
-Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte.</a>
+<div class="alert alert-warning">
+  <p>Os usuários devem possuir um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> com autorização para acessar o módulo <strong>Promoções </strong>no Admin VTEX para utilizar o <strong>Simulador de promoções</strong>.</p>
 </div>
 
-<div class = "alert alert-warning">
-Os usuários devem possuir um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> com autorização para acessar o módulo Promoções no Admin VTEX para conseguir acessar o Simulador de Promoções.
-</div>
+O **Simulador de promoções** é uma ferramenta que permite visualizar as promoções criadas na sua loja VTEX que foram aplicadas no carrinho de compras e os motivos para sua ativação. Também é possível testar a aplicação de promoções antes de ativá-las, incluindo promoções agendadas e inativas.
 
-O **Simulador de Promoções** é uma ferramenta que permite visualizar as promoções criadas na plataforma VTEX que foram aplicadas no carrinho de compras e suas condições de ativação. Com múltiplas possibilidades de configuração de promoções, é importante ter visibilidade da [concorrência](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270), do acúmulo de promoções durante a compra e das causas de ativação dessas promoções.
+Com múltiplas possibilidades de configuração de promoções, o simulador possibilita ter visibilidade da [concorrência](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270), do acúmulo de promoções durante a compra e das causas de ativação dessas promoções.
 
-Usando o simulador, você terá autonomia para gerenciar as promoções da sua loja e conduzi-las conforme sua estratégia de negócio.
+O **Simulador de promoções** está disponível para todas as lojas VTEX pelo [Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451), ferramenta para lojistas na etapa do checkout. Para acessar o simulador, siga os passos abaixo:
 
-Também é possível [gerenciar promoções](#gerenciar-promocoes) que estejam ativas ou inativas, clicando no botão `Gerenciar promoções`.
+1. Na barra superior do Admin VTEX, clique no botão `Pré-visualizar` para abrir a página de acesso restrito da sua loja.
 
-A interface do Simulador apresenta cinco colunas, são elas:
+    Se preferir, você pode acessá-la diretamente pela URL `https://{nomedaconta}.myvtex.com/`, substituindo `{nomedaconta}` pelo nome da sua conta VTEX.
 
-| **Colunas** |**Descrição**| 
-| ----------- | ------------- |
-| **Produtos** | Lista dos produtos contidos no carrinho |
-| **Preço** | Preço anterior (De) e preço final (Por) da promoção aplicada |
-| **Quantidade** | Quantidade de itens no carrinho |
-| **Total** | Preço total que será cobrado pelo produto, considerando descontos da promoção e quantidade de itens |
-| **Desconto** | Status do desconto no carrinho, que podem ser `Aplicado` ou `Não aplicado`. O status `Aplicado` indica que ao menos uma promoção foi aplicada no produto |
+2. Adicione produtos no carrinho e acesse o checkout em `https://{nomedaconta}.myvtex.com/checkout/#/cart`.
+3. Clique no botão azul <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> no canto inferior direito da página para iniciar o Cartman.
+4. Clique em **Simulador de promoções**.
 
-<div class = "alert alert-info">
-No canto direito da tela, você encontrará um botão megafone <i class="fas fa-bullhorn"></i> onde é possível enviar um feedback sobre sua experiência utilizando o <b>Simulador de Promoções</b>. 
-</div>
+    Na nova janela, você verá uma listagem dos produtos presentes no seu carrinho. Será possível visualizar todas as promoções aplicadas e aplicáveis em cada um dos itens.
 
-Para aproveitar dos benefícios da funcionalidade, dividimos esse artigo em duas seções:
+![Simulator-promo-pt-gif-1](//images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/be250ed52b2c5abfcbf1a0debf120c98/simulador-promo-pt-230706.gif)
 
-- [Acessar Simulador de Promoções](#acessar-simulador-de-promocoes)
-- [Gerenciar promoções](#gerenciar-promocoes)
+A interface do **Simulador de promoções** apresenta as seguintes informações:
 
-## Acessar Simulador de Promoções
+| Coluna | Descrição |
+|---|---|
+| **Produtos** | Lista dos produtos contidos no carrinho. |
+| **Preço** | Preço computado anterior às promoções (**De**) e preço final (**Por**) do produto com promoções aplicadas. |
+| **Quantidade** | Quantidade de itens no carrinho. |
+| **Total** | Preço total que será cobrado pelo produto, considerando descontos da promoção e quantidade de itens. |
+| **Desconto** | Status do desconto no carrinho, que pode ser `Aplicado` ou `Não aplicado`. O status `Aplicado` indica que ao menos uma promoção foi aplicada ao produto. |
 
-Para acessar a funcionalidade, primeiramente, você deve [configurar o Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451), uma ferramenta que simula, compartilha e investiga carrinhos de lojas VTEX.
+<div class="alert alert-info">
+  <p>Envie um feedback sobre sua experiência utilizando o **Simulador de promoções** a partir do botão de megafone <i class="fas fa-megaphone"></i> no canto direito da tela.</p>
+</div>
 
-Ao entrar no Simulador, você verá uma listagem dos produtos presentes no seu carrinho. Será possível visualizar todas as promoções passíveis de aplicação em cada um dos itens, com uma caixa de marcação <i class="fas fa-check-square"></i> na promoção aplicada.
+### Atualizar simulador
 
-A ferramenta apresenta uma barra de busca para encontrar promoções pelo nome do produto ou nome da promoção. Além disso, você pode filtrar as promoções por **Tipo de promoção** e **Desconto**.
+Se precisar adicionar ou remover itens do carrinho, você pode manter a janela do simulador aberta. Após fazer as alterações no carrinho, clique em `Atualizar` no **Simulador de promoções** para analisar as promoções aplicadas ao carrinho atualizado.
 
-Ao clicar em cada produto, é possível visualizar mais informações sobre as promoções que podem ser aplicadas, detalhes da sua seleção e a condição para ativá-las.
+### Buscar e filtrar promoções
 
-![simuladordepromocoes acessar](https://images.ctfassets.net/alneenqid6w5/7piR33ciR1x0givnQyxbk7/cdb47a1c812d3fa244aeb6127be100ee/simuladordepromocoes_acessar.gif)
+A ferramenta apresenta uma barra de busca para encontrar promoções pelo nome do produto ou nome da promoção. Além disso, você pode filtrar as promoções por **Tipo de promoção** ([Regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI), [Compre Junto](https://help.vtex.com/pt/tutorial/compre-junto--tutorials_323), [Leve Mais por Menos](https://help.vtex.com/pt/tutorial/leve-mais-por-menos--tutorials_325), [Desconto Progressivo](https://help.vtex.com/pt/tutorial/desconto-progressivo--tutorials_324), [Compre e Ganhe](https://help.vtex.com/pt/tutorial/compre-e-ganhe--tutorials_322) ou [Promoção de Campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume)) e **Desconto** (Aplicado ou Não aplicado).
 
-Com o Cartman configurado, siga os passos abaixo para acessar o Simulador de Promoções:
+### Ver detalhes das promoções aplicadas
 
-1. Acesse o carrinho de compras da sua loja VTEX.
-2. Adicione os produtos que você deseja testar. 
-3. No carrinho de compras, abra o `Cartman`. 
-4. Clique na opção **Ver detalhes da promoção**.
-5. As promoções aplicadas no carrinho serão exibidas. Para mais detalhes das promoções, clique em `Ver detalhes`.
-  > Você será direcionado para o **Simulador de Promoções**. Ao entrar no Simulador, você verá uma listagem dos produtos presentes no seu carrinho. Será possível visualizar todas as promoções passíveis de aplicação em cada um dos itens, com um box checkmark na promoção aplicada.
-6. Caso você altere os produtos do carrinho, clique em `Atualizar` para carregar as novas informações.
+Ao clicar em cada produto, é possível visualizar mais informações sobre as promoções aplicadas, detalhes sobre seus efeitos e os motivos para ativá-las. Também é possível ver as promoções não aplicadas e as razões para não terem sido acionadas.
 
 ### Editar promoções
 
-Para editar uma promoção, siga os passos a seguir:
+Para editar uma promoção, siga os passos abaixo:
 
-1. No **Simulador de Promoções**, selecione um produto.
+1. No **Simulador de promoções**, clique na linha de um produto ou na seta <i class="fas fa-chevron-right"></i>.
 2. Clique no nome da promoção que deseja editar.
-  > Você será redirecionado ao formulário da promoção.
+
+   Você será redirecionado(a) ao formulário da promoção.
+
 3. Edite os [campos da promoção](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#quais-os-dados-gerais-desta-promocao).
 4. Ao concluir as alterações, clique no botão `Salvar`.
 
-## Gerenciar promoções
+### Simular promoções
+
+O **Simulador de promoções** possibilita testar a aplicação de uma outra promoção ou simular o que aconteceria ao desativar promoções aplicadas. Para isso, clique no botão `Selecionar promoções`, no topo direito da página, conforme ilustrado na imagem abaixo.
 
-Se você deseja simular uma nova promoção ou gerenciar as promoções existentes, você deve clicar no botão `Gerenciar promoções`, localizado no lado direito do topo da página.
+![ui-Simulator-promo-pt-gif-2](//images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/6bc4e0a9ee37002a0d265d57a156bff6/ui-simulador-promo-pt-230706.gif)
 
-Será possível visualizar todas as promoções ativas, pausadas, agendadas ou encerradas no carrinho. Assim, você consegue testar um estado futuro da loja.
+Para fazer uma simulação, siga as instruções abaixo:
 
-![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/6J3Bp4YcEZ6V5cgVj4dnhM/c0a6896fcec1bb0cf3bbc6ea3362d19f/simuladordepromocoes_gerenciar.gif)
+1. No **Simulador de promoções**, clique em `Selecionar promoções`, no topo direito da página.
 
-Para testar uma promoção, siga os seguintes passos:
+    Você verá uma lista com todas as promoções cadastradas na sua loja, incluindo ativas, pausadas, agendadas e finalizadas.
 
-1. No **Simulador de Promoções**, clique em `Gerenciar promoções`.
-2. Selecione uma ou mais promoções, independente do status.
-3. Clique no botão `Testar`.
+2. Selecione uma ou mais promoções para simular a aplicação delas no carrinho. Você também pode desmarcar promoções ativas, se desejar simular sua desativação.
+3. Clique no botão `Simular`.
 
-Para visualizar se a promoção testada foi aplicada, observe o status da coluna **Desconto** ou clique no produto para mais detalhes.
+    Você verá o resultado da simulação a partir das promoções selecionadas. Para visualizar se as promoções testadas foram aplicadas aos itens do carrinho na simulação, observe o status da coluna **Desconto** ou clique no produto.
 
-<div class = "alert alert-info">
-É possível aplicar promoções em produtos que já possuem uma promoção ativa. Apesar do conflito entre elas, o sistema VTEX sempre selecionará a promoção mais benéfica, considerando o preço total dos itens ou frete, para os clientes da sua loja.
+<div class="alert alert-info">
+  <p>É possível aplicar promoções em produtos que já possuem uma promoção ativa. Apesar do conflito entre elas, o sistema VTEX sempre seleciona a promoção mais benéfica para os clientes da sua loja, considerando o preço total dos itens ou frete.</p>
 </div>
 
 ### Saiba mais
 
- * [Como funcionam as promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR)
- * [Promoções para cenários específicos](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy)
- * [Configurar o Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451)
+* [Como funcionam as promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR)
+* [Promoções para cenários específicos](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/jOu9b69mKbrTDfSJYAawy)
+* [Configurar o Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451)
diff --git a/docs/tutorials/pt/promotions-simulator.md b/docs/tutorials/pt/promotions-simulator.md
index 4d31b1904..ee09ae043 100644
--- a/docs/tutorials/pt/promotions-simulator.md
+++ b/docs/tutorials/pt/promotions-simulator.md
@@ -24,12 +24,12 @@ O **Simulador de promoções** permite visualizar as promoções aplicadas ao ca
 Para usar essa funcionalidade, primeiro você precisa [configurar o Cartman](https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451), uma ferramenta que simula, compartilha e investiga carrinhos. Com o Cartman configurado, siga os passos abaixo para acessar o **Simulador de promoções**.
 
 1. Adicione produtos que estejam incluídos em promoções da loja no carrinho.
-2. No carrinho de compras, clique no botão <img src="https://images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para abrir o Cartman.
+2. No carrinho de compras, clique no botão <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para abrir o Cartman.
 3. Clique na opção `Ver detalhes da promoção`.
 4. Esta janela exibe as promoções aplicadas no carrinho. Para mais detalhes, clique em <i class="fas fa-search"></i>`Ver detalhes`.
-![cartman-analisador-promoção-PT](https://images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/3978d26dac1793e9ced1f1d0e72c88d2/image.png)
+![cartman-analisador-promoção-PT](//images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/3978d26dac1793e9ced1f1d0e72c88d2/image.png)
 5. Em seguida, a janela **Simulador de Promoções** será exibida.
-![analisador-promoção-PT](https://images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/8617bf80e3997673bcc274f1ef97da74/Screenshot_15.png)
+![analisador-promoção-PT](//images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/8617bf80e3997673bcc274f1ef97da74/Screenshot_15.png)
 
 Nesta janela, é possível consultar as seguintes informações:
 
diff --git a/docs/tutorials/pt/promotions.md b/docs/tutorials/pt/promotions.md
new file mode 100644
index 000000000..3655deefa
--- /dev/null
+++ b/docs/tutorials/pt/promotions.md
@@ -0,0 +1,108 @@
+---
+title: 'Promoções Data Pipeline (Beta)'
+id: 3WZ1syNucDFdvVhfKtA6Qd
+status: PUBLISHED
+createdAt: 2024-02-02T18:02:01.395Z
+updatedAt: 2024-06-21T16:25:25.745Z
+publishedAt: 2024-06-21T16:25:25.745Z
+firstPublishedAt: 2024-05-27T19:26:59.739Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: promocoes-data-pipeline-beta
+locale: pt
+legacySlug: promocoes-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+O conjunto de dados de Promoções é constituído por quatro tabelas: `promotion_archived`, `promotion_created`, `promotion_removed` e `promotion_unarchived`. Essas quatro tabelas abrange todo o ciclo de vida das campanhas promocionais, do lançamento ao arquivamento, reativação ou remoção, fornecendo uma visão integral das estratégias promocionais da loja.
+
+Nesta seção você encontra as seguintes informações:
+
+- [Características dos dados de promoções](#caracteristicas-dos-dados-de-promocoes)
+- [Tabela promotion_archivied](#tabela-promotion_archivied)
+- [Tabela promotion_created](#tabela-promotion_created)
+- [Tabela promotion_removed](#tabela-promotion_removed)
+- [Tabela promotion_unarchivied](#tabela-promotion_unarchivied)
+- [Análise com dados de promoções](#analise-com-dados-de-promocoes)
+- [Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados de promoções
+
+| **Característica** | **Descrição** |
+|:---:|:---:|
+| **Origem do dado** | São originadas do <a href="https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR">módulo de Promoções</a> do Admin VTEX. |
+| **Disponibilidade** | Os dados de Promoções podem ser acessados através do Admin da VTEX e também por <a href="https://developers.vtex.com/docs/guides/promotions-overview">APIs de Promotions</a>. |
+| **Histórico** | Os dados são mantidos por dois anos, a partir de 2024 para clientes que já utilizam a plataforma VTEX. |
+| **Menor intervalo de atualização possível** | Uma hora. |
+
+## Tabela promotion_archivied
+
+A tabela `promotion_archivied` registra todas as promoções arquivadas. Inclui detalhes sobre as promoções removidas temporariamente ou permanentemente do uso ativo, permitindo um histórico e análise de campanhas anteriores. Veja a seguir os campos que compõem essa tabela.
+
+| **Nome da Coluna** | **Tipo de Coluna** | **Descrição da Coluna** |
+|:---:|:---:|:---:|
+| version | character varying(16383) | Versão dos dados na tabela, útil para controle de versões e compatibilidade. |
+| ingestion_time | timestamp without time zone | Data e hora em que os dados foram inseridos na tabela. |
+| payload | super | Conjunto de dados efetivamente armazenados na tabela, englobando diversas informações. |
+| batch_id | character varying(13) | Identificador do lote de dados, utilizado para rastrear a ingestão e gerenciamento dos dados. |
+
+## Tabela promotion_created
+
+A tabela `promotion_created` contém informações sobre promoções recém-criadas, ela é crucial para rastrear o lançamento de novas campanhas promocionais, oferecendo insights sobre as estratégias e iniciativas de marketing atuais. Veja a seguir os campos que compõem a tabela.
+
+| **Nome da Coluna** | **Tipo de Coluna** | **Descrição da Coluna** |
+|:---:|:---:|:---:|
+| version | character varying(16383) | Indica a versão dos dados presentes na tabela. |
+| ingestion_time | timestamp without time zone | Representa o momento em que os dados foram inseridos na tabela. |
+| payload | super | Contém o conjunto de dados ou informações efetivamente carregadas na tabela. |
+| batch_id | character varying(13) | Identificador único do lote de dados, utilizado para rastrear e gerenciar a ingestão de dados. |
+
+## Tabela promotion_removed
+
+A tabela `promotion_removed` registra as promoções excluídas ou desativadas, e permite analisar quais promoções foram descontinuadas e entender os motivos das decisões. Veja a seguir os campos que compõem a tabela.
+
+| **Nome da Coluna** | **Tipo de Coluna** | **Descrição da Coluna** |
+|:---:|:---:|:---:|
+| version | character varying(16383) | Versão dos dados. |
+| ingestion_time | timestamp without time zone | Data e hora da ingestão dos dados. |
+| payload | super | Conteúdo dos dados inseridos. |
+| batch_id | character varying(13) | ID de controle do lote de dados. |
+
+## Tabela promotion_unarchived
+
+A tabela `promotion_unarchived` armazena informações de promoções reativadas ou retiradas do arquivo. Ela fornece informações sobre campanhas reintroduzidas, ajudando a compreender as estratégias de reutilização ou revisão de promoções anteriores. Veja a seguir os campos que compõem a tabela.  
+
+| **Nome da Coluna** | **Tipo de Coluna** | **Descrição da Coluna** |
+|:---:|:---:|:---:|
+| version | character varying(16383) | Versão dos dados na tabela. |
+| ingestion_time | timestamp without time zone | Data e hora em que os dados foram inseridos na tabela. |
+| payload | super | Conjunto de dados efetivamente armazenados na tabela. |
+| batch_id | character varying(13) | Identificador do lote de dados inseridos na tabela. |
+
+## Análise com dados de Promoções
+
+Veja a seguir alguns exemplos de análises com o conjunto de sados de promoções:
+
+**- Análise de ciclo de vida da promoção:** compare a frequência e duração das promoções para avaliar a longevidade e o sucesso das campanhas.  
+**- Taxa de reativação de promoções:** analise quantas promoções são reativadas para determinar a eficácia de reutilizar ou revisar campanhas anteriores.  
+**- Tendências de remoção de promoções:** rastreie o número e os tipos de promoções descontinuadas para entender os motivos da remoção e ajustar futuras estratégias.  
+**- Impacto de novas promoções:** compare os lançamentos de promoções com as vendas e o tráfego para avaliar seu impacto imediato.  
+
+## Correlações com outros dados
+
+Veja a seguir a correlação do conjunto de dados de promoções, com alguns outros conjuntos de dados:
+
+**- Dados de [pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv):** a análise da influência das promoções nos pedidos ajuda a compreender seu impacto nas vendas.  
+**- Dados de [inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2):** a correlação com o inventário é crucial para garantir a disponibilidade de produtos promovidos.  
+**- Análises de marketing e publicidade:** a integração com esses dados permite medir a efetividade das promoções em atrair tráfego e engajamento.
+**- Dados de [navegação no Site](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd):** analisar o efeito das promoções na navegação fornece insights sobre o comportamento do cliente e a eficácia da colocação das promoções. 
+
+### Conheça outros Conjuntos de dados
+
+- [Inventário](https://help.vtex.com/tutorial/inventario-data-pipeline-beta--2IvKMZV9SNrE6ipBRQr8h2)
+- [Navegação](https://help.vtex.com/tutorial/navegacao-data-pipeline-beta--4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Pedidos](https://help.vtex.com/tutorial/pedidos-data-pipeline-beta--2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Pagamentos](https://help.vtex.com/tutorial/pagamentos-data-pipeline-beta--7LWkFaA1jPabzc5JAt1rGs)  
+- [Preços](https://help.vtex.com/tutorial/precos-data-pipeline-beta--3NMGJ8dtv73Bwvo9PSz1fz)   
+
diff --git a/docs/tutorials/pt/protection-against-transaction-attacks.md b/docs/tutorials/pt/protection-against-transaction-attacks.md
index d0bee3474..8734cda75 100644
--- a/docs/tutorials/pt/protection-against-transaction-attacks.md
+++ b/docs/tutorials/pt/protection-against-transaction-attacks.md
@@ -3,7 +3,7 @@ title: 'Proteção contra ataques em transações'
 id: 62oQBmi7UZlYlgb0Ha1hZ3
 status: DRAFT
 createdAt: 2021-10-25T19:02:59.690Z
-updatedAt: 2021-12-10T13:52:07.652Z
+updatedAt: 2024-03-01T15:58:16.139Z
 publishedAt: 
 firstPublishedAt: 
 contentType: tutorial
@@ -15,7 +15,7 @@ legacySlug: protecao-contra-ataques-em-transacoes
 subcategory: 
 ---
 
-## Proteção contra ataques em transações
+# Proteção contra ataques em transações
 
 A proteção contra ataques envolvendo transações é uma das soluções que a VTEX oferece para reduzir o risco de operações fraudulentas. Esta proteção é ativada automaticamente quando detectamos uma taxa muito alta de negação de autorizações de transações (acima de 90%) dentro de um curto período de tempo (15 minutos).
 
@@ -36,9 +36,9 @@ Para habilitar a proteção, confira o passo a passo:
 4. No canto superior direito, clilque no ícone de configurações.
 5. Em __Proteção contra ataques__, clique no botão para habilitar (cor verde indica "habilitado").
 
-![proteção-botao-configurações](https://images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
+![proteção-botao-configurações](//images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
 
-![proteção-opção-habilitar1](https://images.ctfassets.net/alneenqid6w5/kk96NiBFAUzzuv23FbQeu/7f4c2e67f22c7aaa2886f9850a3fcc03/prote____o-op____o-habilitar1.png)
+![proteção-opção-habilitar1](//images.ctfassets.net/alneenqid6w5/kk96NiBFAUzzuv23FbQeu/7f4c2e67f22c7aaa2886f9850a3fcc03/prote____o-op____o-habilitar1.png)
 
 ### Como desabilitar a proteção contra ataques em transações?
 
@@ -68,15 +68,16 @@ Para acessar estas informações, confira o passo a passo:
 6. Para selecionar __Ameaças detectadas__ ou __Ameaças neutralizadas__, clique em uma das setas à direita.
 7. Verifique os detalhes dos eventos na janela popup apresentada.
 
-![proteção-opção-historico1](https://images.ctfassets.net/alneenqid6w5/19hGY1Jjv5DOBXABIxCnxd/43d9eb3c6c754576e2879fbc9c5f62bc/prote____o-op____o-historico1.png)
+![proteção-opção-historico1](//images.ctfassets.net/alneenqid6w5/19hGY1Jjv5DOBXABIxCnxd/43d9eb3c6c754576e2879fbc9c5f62bc/prote____o-op____o-historico1.png)
 
-![proteção-tela-historico1](https://images.ctfassets.net/alneenqid6w5/6p6N8EV2PnhzbnxFUkOWda/bec651a71aa79f2374426afefe8cdf23/prote____o-tela-historico1.png)
+![proteção-tela-historico1](//images.ctfassets.net/alneenqid6w5/6p6N8EV2PnhzbnxFUkOWda/bec651a71aa79f2374426afefe8cdf23/prote____o-tela-historico1.png)
 
-![tela-ameaça-potencial1](https://images.ctfassets.net/alneenqid6w5/4l9WCe1f7yYN9Gx0sczBXK/40dddb9cb38a2b415a57c262fc61faa0/tela-amea__a-potencial1.png)
+![tela-ameaça-potencial1](//images.ctfassets.net/alneenqid6w5/4l9WCe1f7yYN9Gx0sczBXK/40dddb9cb38a2b415a57c262fc61faa0/tela-amea__a-potencial1.png)
 
-![tela-ameaça-neutralizada1](https://images.ctfassets.net/alneenqid6w5/68JvVENRbcGGOcBFXno54/fe85365340965f6d7927f2d6525d27a2/tela-amea__a-neutralizada1.png)
+![tela-ameaça-neutralizada1](//images.ctfassets.net/alneenqid6w5/68JvVENRbcGGOcBFXno54/fe85365340965f6d7927f2d6525d27a2/tela-amea__a-neutralizada1.png)
 
 ### Artigos relacionados
+
 - [O que é antifraude?](https://help.vtex.com/pt/tutorial/o-que-e-antifraude)
 - [Como configurar o antifraude](https://help.vtex.com/pt/tutorial/como-configurar-antifraude)
 - [Visão geral de Pagamentos](https://help.vtex.com/pt/tutorial/pci-gateway-visao-geral)
diff --git a/docs/tutorials/pt/qr-code-suiteshare.md b/docs/tutorials/pt/qr-code-suiteshare.md
index 8fa24372a..93de33324 100644
--- a/docs/tutorials/pt/qr-code-suiteshare.md
+++ b/docs/tutorials/pt/qr-code-suiteshare.md
@@ -19,7 +19,7 @@ Código QR é um código de barras bidimensional que pode ser facilmente escanea
 
 No VTEX Assisted Sales (SuiteShare) você conseguirá unir a tecnologia dos QRCODES com o Link de WhatsApp e fazer com que os clientes abram uma conversa com você no WhatsApp com apenas um escaneamento.
 
-![QR Code_1](https://images.ctfassets.net/alneenqid6w5/2I4HDB3mTmDa7I0OPcmLH1/a9a86497f4a5a9e385a65d8ce422c3f1/QR_Code_1.png)
+![QR Code_1](//images.ctfassets.net/alneenqid6w5/2I4HDB3mTmDa7I0OPcmLH1/a9a86497f4a5a9e385a65d8ce422c3f1/QR_Code_1.png)
 
 Se na sua empresa, você utiliza materiais impressos, esses códigos são a melhor opção para levar os clientes do offline para o online.
 
@@ -29,19 +29,19 @@ Se na sua empresa, você utiliza materiais impressos, esses códigos são a melh
 
 No painel do VTEX Assisted Sales (SuiteShare), acesse a opção _**Atrair > Links**_.
 
-![QR Code_2](https://images.ctfassets.net/alneenqid6w5/3Gwg5q0rWo21D4oopPiVKS/29699a9f60e197f2fc0e2ca20dc79644/QR_Code_2.png)
+![QR Code_2](//images.ctfassets.net/alneenqid6w5/3Gwg5q0rWo21D4oopPiVKS/29699a9f60e197f2fc0e2ca20dc79644/QR_Code_2.png)
 
 Clique no ícone do QRCODE, localizado no lado direito do link que você deseja criar um código.
 
-![QR Code_3](https://images.ctfassets.net/alneenqid6w5/6pOgNXtgNW5QMs1fMwJyW9/0b1884f5e61b195c13fc8591f71f9491/QR_Code_3.png)
+![QR Code_3](//images.ctfassets.net/alneenqid6w5/6pOgNXtgNW5QMs1fMwJyW9/0b1884f5e61b195c13fc8591f71f9491/QR_Code_3.png)
 
 Escolha um logotipo (Opcional):
 
-![QR Code_4](https://images.ctfassets.net/alneenqid6w5/2eVNZiKJ6wUsq1f5NqqsPa/f793938eabeae194250c53668a5b84cd/QR_Code_4.png)
+![QR Code_4](//images.ctfassets.net/alneenqid6w5/2eVNZiKJ6wUsq1f5NqqsPa/f793938eabeae194250c53668a5b84cd/QR_Code_4.png)
 
 Pronto! Agora você precisa escolher o formato do arquivo que deseja fazer o download (PNG, SVG, EPS) e adiciona-lo a sua arte do seu material no Corel Drawn, Ilustrator, Potoshop.
 
-![QR Code_5](https://images.ctfassets.net/alneenqid6w5/1ExIlz752tONoKQOz5Eqml/5e63e2fc5c226a332e1ca091c1a98104/QR_Code_5.png)
+![QR Code_5](//images.ctfassets.net/alneenqid6w5/1ExIlz752tONoKQOz5Eqml/5e63e2fc5c226a332e1ca091c1a98104/QR_Code_5.png)
 
 ## Saiba onde utilizar o QR code: 
 
diff --git a/docs/tutorials/pt/rdstation-crm-suiteshare.md b/docs/tutorials/pt/rdstation-crm-suiteshare.md
index 3445af419..989ced14c 100644
--- a/docs/tutorials/pt/rdstation-crm-suiteshare.md
+++ b/docs/tutorials/pt/rdstation-crm-suiteshare.md
@@ -19,22 +19,22 @@ Com essa integração é possível criar oportunidades via VTEX Assisted Sales (
 
 Para realizar está integração, clique na engrenagem que se encontra no canto superior direito e em seguida clique em **"Integrações"**.
 
-![RdStation CRM 1](https://images.ctfassets.net/alneenqid6w5/4Wts5lWqc9NmkPrwjXSd5S/4da0068d32a5509dee6fb4ac230d74fc/Screenshot_2022-08-30_at_16-25-23_RdStation_CRM.png)  
+![RdStation CRM 1](//images.ctfassets.net/alneenqid6w5/4Wts5lWqc9NmkPrwjXSd5S/4da0068d32a5509dee6fb4ac230d74fc/Screenshot_2022-08-30_at_16-25-23_RdStation_CRM.png)  
 
 Após clicar em integrações, localize o RD Station CRM e Clique em Habilitar.
 
-![RdStation CRM 2](https://images.ctfassets.net/alneenqid6w5/73woJ2dZwHCMFCTDc7Jkce/bdb887e8700e217948d223008010494a/Screenshot_2022-08-30_at_16-25-27_RdStation_CRM.png)
+![RdStation CRM 2](//images.ctfassets.net/alneenqid6w5/73woJ2dZwHCMFCTDc7Jkce/bdb887e8700e217948d223008010494a/Screenshot_2022-08-30_at_16-25-27_RdStation_CRM.png)
 
 Após clicar em Habilitar, selecione o link de [Captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que irá integrar os dados para dentro do RD Station CRM.
 
-![RdStation CRM 3](https://images.ctfassets.net/alneenqid6w5/14c77bx8MEprrVkfJwjFZ6/dfb058533fe2bbf8b3822010d8a4989a/Screenshot_2022-08-30_at_16-25-30_RdStation_CRM.png)
+![RdStation CRM 3](//images.ctfassets.net/alneenqid6w5/14c77bx8MEprrVkfJwjFZ6/dfb058533fe2bbf8b3822010d8a4989a/Screenshot_2022-08-30_at_16-25-30_RdStation_CRM.png)
 
 Em seguida, insira o seu Token. Caso esteja com dificuldades para encontrar o seu token, [Clique Aqui](\"https://crmsupport.rdstation.com.br/hc/pt-br/articles/360018468312-O-que-%C3%A9-Token-Como-ativ%C3%A1-lo-\").
 
-![RdStation CRM 4](https://images.ctfassets.net/alneenqid6w5/3NQT2ZZl3zbnJJIheFArXn/375deec9df31676a9998370777042d1b/Screenshot_2022-08-30_at_16-25-35_RdStation_CRM.png)
+![RdStation CRM 4](//images.ctfassets.net/alneenqid6w5/3NQT2ZZl3zbnJJIheFArXn/375deec9df31676a9998370777042d1b/Screenshot_2022-08-30_at_16-25-35_RdStation_CRM.png)
 
 Após inserir o seu token, Preencha o campo usuário de acordo com qual usuário deve receber os leads dentro do CRM.
 
-![RdStation CRM 5](https://images.ctfassets.net/alneenqid6w5/3P9Gen2qj3ccv4JhvaBsMk/91bf86407a3d551ff0bc8c6e70957f10/Screenshot_2022-08-30_at_16-25-39_RdStation_CRM.png)
+![RdStation CRM 5](//images.ctfassets.net/alneenqid6w5/3P9Gen2qj3ccv4JhvaBsMk/91bf86407a3d551ff0bc8c6e70957f10/Screenshot_2022-08-30_at_16-25-39_RdStation_CRM.png)
 
 Pronto, seus leads Capturados serão integrados para o RD CRM.
diff --git a/docs/tutorials/pt/rdstation-suiteshare.md b/docs/tutorials/pt/rdstation-suiteshare.md
index 51c6e6399..8fc4c2fe9 100644
--- a/docs/tutorials/pt/rdstation-suiteshare.md
+++ b/docs/tutorials/pt/rdstation-suiteshare.md
@@ -21,28 +21,28 @@ Com essa integração via **VTEX Assisted Sales (SuiteShare)** (através do for
 
 Na dashboard em _**“Integrações”**_.
 
-![RdStation 1](https://images.ctfassets.net/alneenqid6w5/2eZU6639ayDOZ8QCPfhvIm/b58704b43e43079e466f0c51e2902866/image.png)
+![RdStation 1](//images.ctfassets.net/alneenqid6w5/2eZU6639ayDOZ8QCPfhvIm/b58704b43e43079e466f0c51e2902866/image.png)
 
 Ou clique em "_**configurações > Integrações"**_.
 
-![RdStation 2](https://images.ctfassets.net/alneenqid6w5/69OR69XXK5ksuOkHyhA6ku/c1aaf7c386916941d553316b5b92a3fe/image.png)
+![RdStation 2](//images.ctfassets.net/alneenqid6w5/69OR69XXK5ksuOkHyhA6ku/c1aaf7c386916941d553316b5b92a3fe/image.png)
 
 Selecione a RD Station e clique em _**“integrar”**_.
 
 Clique em _**“conectar”**_.
 
-![RdStation 3](https://images.ctfassets.net/alneenqid6w5/4qA2jyDT6GchuNX1EQay0d/f474ba834120299d199781e04d57859d/image.png)
+![RdStation 3](//images.ctfassets.net/alneenqid6w5/4qA2jyDT6GchuNX1EQay0d/f474ba834120299d199781e04d57859d/image.png)
 
 Faça login na sua conta no RD Station.
 
-![RdStation 4](https://images.ctfassets.net/alneenqid6w5/54xB2yNgi98NQ4aas2MX21/b24bff869eb915b241ad26107e16e701/image.png)
+![RdStation 4](//images.ctfassets.net/alneenqid6w5/54xB2yNgi98NQ4aas2MX21/b24bff869eb915b241ad26107e16e701/image.png)
 
 Escolha qual conta deseja conectar e clique em _**continuar**_.
 
-![RdStation 5](https://images.ctfassets.net/alneenqid6w5/SJmHEE51Md5KjkSMXHtPi/cac3ffe38046d35a4d25f05044c04015/image.png)
+![RdStation 5](//images.ctfassets.net/alneenqid6w5/SJmHEE51Md5KjkSMXHtPi/cac3ffe38046d35a4d25f05044c04015/image.png)
 
 Clique em _**“Conectar”**_.
 
-![RdStation 6](https://images.ctfassets.net/alneenqid6w5/cEx8hWwX1dPWLgbxe5HbM/8e83613e252b12f7154eeb342af8e514/image.png)
+![RdStation 6](//images.ctfassets.net/alneenqid6w5/cEx8hWwX1dPWLgbxe5HbM/8e83613e252b12f7154eeb342af8e514/image.png)
 
 Pronto! Você acabou de integrar a **VTEX Assisted Sales (SuiteShare)** com o seu CRM.
diff --git a/docs/tutorials/pt/ready-to-dispatch.md b/docs/tutorials/pt/ready-to-dispatch.md
index 4e4a15782..8d6cdeec8 100644
--- a/docs/tutorials/pt/ready-to-dispatch.md
+++ b/docs/tutorials/pt/ready-to-dispatch.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Pronto para envio'
 id: 5YOZV7Aotv3pap0fGNESDs
 status: PUBLISHED
 createdAt: 2021-11-11T20:13:17.128Z
-updatedAt: 2023-06-09T12:57:15.077Z
-publishedAt: 2023-06-09T12:57:15.077Z
+updatedAt: 2024-02-29T19:44:25.837Z
+publishedAt: 2024-02-29T19:44:25.837Z
 firstPublishedAt: 2021-11-11T20:44:13.846Z
 contentType: tutorial
 productTeam: Others
@@ -15,8 +15,12 @@ legacySlug: pronto-para-envio
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
+<div class="alert alert-info">
+Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>.
+</div>
+
 <div class="alert alert-warning">
-<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX dos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92">Painel VTEX Shipping Network</a></li><li><a href="https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq">Entregas Correios</a></li><li>Pronto para envio</li></ul></p>
+<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92">Painel VTEX Shipping Network</a></li><li><a href="https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq">Entregas Correios</a></li><li>Pronto para envio</li></ul></p>
 </div>
 
 Quando um pedido está pronto para o envio e com a nota fiscal inserida na plataforma ([faturado](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT)), a loja providencia a etiqueta de envio e notifica a transportadora que o envio deve ser feito.
@@ -24,7 +28,7 @@ Quando um pedido está pronto para o envio e com a nota fiscal inserida na plata
 Para gerar etiquetas padronizadas e notificar as transportadoras do envio automaticamente, o [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) tem a funcionalidade **Pronto para envio**.
 
 <div class = "alert alert-info">
-Além de emitir etiquetas de envio pelo Admin VTEX com a funcionalidade <b>Pronto para envio</b>, você fazer isso por API. Saiba  mais na nossa documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration">VTEX Shipping Network Labels Integration</a>.
+Além de emitir etiquetas de envio pelo Admin VTEX com a funcionalidade <b>Pronto para envio</b>, você pode fazer isso por API conectada diretamente ao seu ERP. Saiba  mais na nossa documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration">VTEX Shipping Network Labels Integration</a>.
 </div>
 
 O sistema da VTEX identifica o número de pacotes de um pedido de acordo com o número de notas fiscais desse pedido, de forma que o número de etiquetas que o lojista pode imprimir para cada pedido corresponde ao número de notas fiscais. 
@@ -68,7 +72,7 @@ Você pode organizar a lista de pacotes de duas formas, clicando nas opções ao
 * `Data da fatura`: ordena pela data em que as notas fiscais foram criadas.
 
 <div class="alert alert-warning">
-A <b>Pronto para envio</b> emite etiquetas para que as Lojas VTEX não precisem ter um modelo de etiqueta própria. No entanto, algumas transportadoras podem ter etiquetas próprias, que não seguem o padrão usado na plataforma VTEX.
+O <b>Pronto para envio</b> emite etiquetas para todos os <a href="https://help.vtex.com/pt/tutorial/faturar-um-pedido-manualmente--7p1h852V5t54KyscpgxE2v">pedidos faturados</a> no Admin VTEX cujos itens foram referenciados na nota fiscal, seja via API no ERP ou manualmente. No entanto, apenas as etiquetas de transportadoras vinculadas ao <b>VTEX Shipping Network</b> possuem layout e rastreabilidade válidos via API.
 </div>
 
 ### Impressão de etiquetas
@@ -91,11 +95,9 @@ As transportadoras são notificadas quando é feito o download das etiquetas.
 ![etiquetas](//images.contentful.com/alneenqid6w5/1L1fExGcJgTPi3WD5nmWBL/7714df72cacfafda1d915aa86cc1203e/etiquetas.png)
 
 <div class="alert alert-danger">
-Se a janela <b>Gerenciar arquivos</b> não iniciar o download da etiqueta automaticamente, vai parecer na tela uma mensagem de erro. Após ver a mensagem, observe se o número da nota fiscal está correto e tente imprimir novamente. , caso o erro persista, entre em contato com o nosso <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">suporte</a>.
+Em caso de erros ou dúvidas, entre em contato diretamente com o suporte do <b>VTEX Shipping Network</b> através do email vtexlog@vtex.com.br.
 </div>
 
-Além de emitir etiquetas de envio pelo Admin VTEX com a funcionalidade **Pronto para envio**, você fazer isso por API. Saiba  mais na nossa documentação para desenvolvedores [VTEX Shipping Network Labels Integration](https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration).
-
 ### Alterar o tipo do tamanho das etiquetas
 
 No Admin VTEX, é possível alterar o formato das dimensões da etiqueta e escolher entre `A4` (297x210mm) ou `ZPL` (Zebra Programming Language). Para isso, siga os passos abaixo:
@@ -148,7 +150,7 @@ Para baixar novamente as etiquetas e notfis, realize os passos abaixo:
 1. No Admin VTEX, acesse **Envio > Pronto para envio**, ou digite *Pronto para envio* na barra de busca no topo da página.
 2. Na aba `Pacotes enviados`, na linha do pacote desejado, clique em menu <i class="fas fa-ellipsis-v"></i> e selecione a opção desejada:
     * Reimprimir etiquetas
-    * Bauxar arquivos notfis
+    * Baixar arquivos notfis
 3. Confira o arquivo baixado.
 
 ## Saiba mais
diff --git a/docs/tutorials/pt/received-skus-beta.md b/docs/tutorials/pt/received-skus-beta.md
new file mode 100644
index 000000000..f694bee29
--- /dev/null
+++ b/docs/tutorials/pt/received-skus-beta.md
@@ -0,0 +1,223 @@
+---
+title: 'SKUs recebidos'
+id: 4hxDUmbgOEVFSTU2Eqi8DK
+status: PUBLISHED
+createdAt: 2024-04-29T13:48:12.818Z
+updatedAt: 2024-06-25T19:27:37.735Z
+publishedAt: 2024-06-25T19:27:37.735Z
+firstPublishedAt: 2024-04-29T14:16:25.091Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: skus-recebidos-beta
+locale: pt
+legacySlug: anuncios-recebidos
+subcategory: 
+---
+
+A página **SKUs recebidos** permite que o [marketplace](https://help.vtex.com/pt/tutorial/visao-geral-marketplace--40Zd0z9h2RXsM9uMUp3kEb) visualize, priorize e catalogue os itens enviados pelos seus sellers. Dessa maneira, é possível criar novos produtos e também associá-los a SKUs ou a produtos já existentes para disponibilizá-los para venda. Acesse a página no Admin VTEX em **Marketplace > SKUs recebidos**  ou digite **SKUs recebidos** na barra de busca do Admin.
+
+A catalogação pode ser feita manualmente ou automaticamente, [por meio de um ou mais matchers](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt), e também pelo [autoApprove](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions/#put-/suggestions/configuration/autoapproval/toggle). Além disso, também existe a possibilidade de usar ferramentas externas para realizar essa operação.
+
+![Apresentação Anúncios Recebidos-PT](//downloads.ctfassets.net/alneenqid6w5/1qyRLboXsLXCwaoT3xfSwI/9882db31e2a68ebe127532f24cf4bcae/GIF_PT.gif)
+
+Neste artigo você encontrará uma visão geral sobre a [Estrutura da página](#estrutura-da-pagina), [Priorizando a catalogação](#priorizando-a-catalogacao) e [Catalogação de itens](#catalogacao-de-itens).
+
+## Estrutura da página
+
+A página **SKUs recebidos** em seções conforme os possíveis status de um anúncio, sendo eles os seguintes:
+
+[Pendentes](#pendentes)
+[Problemas](#problemas)
+[Aprovados](#aprovados)
+[Processando](#processando)
+[Bloqueados](#bloqueados)
+Em cada seção, além da listagem dos SKUs, é possível filtrar os anúncios, visualizar as especificações de cada um e verificar qual a porcentagem dos SKUs recebidos encontram-se naquele status.
+
+### Pendentes
+
+Na seção **Pendentes,** o marketplace encontra a lista de todos os anúncios enviados por um seller e que ainda não foram aprovados. Os anúncios podem ser filtrados por **Seller, Categoria, Marca e Estoque.** Também é possível realizar as seguintes ações em anúncios desta seção: **Criar novo produto, Associar a produto ou SKU, Recusar para correção ou Recusar e bloquear.**
+
+Cada linha da lista representa um produto com as seguintes informações:
+
+- **Anúncio:** apresenta o nome do produto.  
+- **ID do SKU:** número que identifica o produto.  
+- **Seller:** nome do seller que enviou o anúncio.  
+- **Categoria:** categoria na qual o produto está cadastrado, caso a categoria já tenha sido mapeada. Se ainda não foi, aparecerá a mensagem _Não mapeada._  
+- **Preço:** preço do produto enviado pelo seller.  
+- **Estoque:** quantidade disponível daquele produto.  
+
+Para verificar todas as especificações de um produto, clique sobre o nome do produto desejado e uma nova janela abrirá com todas as informações daquele produto.
+
+![pendentes-info-produto-PT](//images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/ea57f537bcad436fad6a45286adc7840/pendentes-info-produto-PT.png)
+
+### Problemas
+
+Na seção **Problemas,** estão disponíveis todos os anúncios que ainda não foram aprovados, por existirem problemas que precisam ser corrigidos pelo seller. Os filtros, ações e campos de identificação disponíveis na seção **[Pendentes](#pendentes)** são similares aos da seção Problemas.
+
+<div class="alert alert-info">
+A ação pedir correção não está disponível na seção <b>Problemas.</b>
+</div>
+
+Para identificar qual o problema de um anúncio, basta clicar no nome do produto desejado. Uma nova janela será exibida com as informações referentes ao produto, a mensagem de erro e o revisor do anúncio.
+
+![problemas do produto-PT](//images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/f0a31393e47198a3ff81d0016c2491e9/problemas_do_produto-PT.png)
+
+### Aprovados
+
+Na seção **Aprovados,** é possível visualizar os SKUs recebidos e aprovados. Nesta seção, é possível filtrar os anúncios por **Seller, Categoria e Marca.**
+
+Cada linha da lista representa um produto com as seguintes informações: 
+
+- **Anúncio:** que apresenta o nome do produto.  
+- **ID do SKU:** número que identifica o produto.  
+- **Seller:**  nome do seller que enviou o anúncio.  
+- **Categoria:** mostra em qual categoria o produto está incluído.  
+
+### Processando
+
+Na seção **Processando,** estão disponíveis os SKUs recebidos, que estão sendo avaliados pelo sistema VTEX.  Esta é uma seção apenas de visualização com opções de filtros por **Seller** e **Data de envio** do produto.
+
+Cada linha da lista representa um produto com as seguintes informações:
+
+- **Anúncio:** que apresenta o nome do produto.  
+- **ID do SKU:** número que identifica o produto.  
+- **Seller:** nome do seller que enviou o anúncio.  
+- **Data de envio:** mostra quando o anúncio foi enviado ao marketplace.  
+
+<div class="alert alert-info">
+Os anúncios listados nessa seção estão sendo avaliados pelo Matcher e pelo Offer Quality ou Auto approve, caso tenham sido configurados. Após essa avaliação o anúncio pode ser enviado para as seções <b>Pendentes, Problemas, Aprovados ou Bloqueados</b>, a depender do cumprimento de requisitos.
+</div>
+
+### Bloqueados
+
+Na seção **Bloqueados,** é possível visualizar os anúncios enviados pelo seller que foram bloqueados pelo marketplace. Nesta seção é possível **Desbloquear** um anúncio e também filtrá-los por **Seller** e **Revisor.**
+
+Cada linha da lista representa um produto com as seguintes informações:
+
+- **Anúncio:** apresenta o nome do produto.
+- **ID do SKU:** número que identifica o produto.
+- **Seller:** nome do seller que enviou o anúncio.
+- **Revisor:** nome do agente que fez a revisão do anúncio.
+
+## Priorizando a catalogação
+
+A listagem de SKUs recebidos foi desenvolvida para priorizar e acelerar a catalogação desses itens. Ao clicar em qualquer SKU da lista, você acessa um resumo das principais informações do SKU por meio de uma barra lateral, sem sair da página de listagem. Na barra lateral, também inclui a porcentagem de equivalência que o SKU recebeu pelo matcher instalado em sua loja.
+
+Algumas das funcionalidades que auxiliam no processo de priorização são:
+
+### Filtros
+
+Em cada uma das seções apresentadas no tópico anterior, é possível combinar diferentes filtros para montar a visualização desejada de SKUs. 
+
+Por exemplo, se a marca "ABC" e a categoria "Meias" forem selecionadas, a visualização mostrará todos os SKUs da marca “ABC” que sejam da categoria "Meias".
+
+Vale ressaltar que as opções de filtros se dão conforme os SKUs disponíveis na listagem. Suponhamos, por exemplo, que o marketplace está conectado aos sellers A, B e C, mas somente existem SKUs dos sellers B e C pendentes. Isso significa que a seleção de filtro na seção [Pendente](#pendente) exibirá apenas os resultados dos sellers B e C.
+
+### Ordenação
+
+Por padrão, os itens com envios mais recentes são os primeiros a serem listados. Contudo, também é possível ordenar por **Preço** e **Estoque.**
+
+Nesse caso, os itens serão ordenados de forma crescente ou decrescente ao clicar em **"Preço"** ou **"Estoque"** no cabeçalho.
+
+![ordenacao-PT](//images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/1f5cbbbae8c8b969fcabcfd531e57d95/ordenacao-PT.png)
+
+## Catalogação de itens
+
+Todos os SKUs exibidos na lista já estão disponíveis para catalogação. Entretanto, recomenda-se realizar o [mapeamento de categorias e marcas](https://help.vtex.com/pt/tutorial/mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta--6NU8LwR6i0tTb8nk30bnbE) antes desse passo para que o processo de catalogação seja mais rápido.
+
+<div class="alert alert-warning">
+Os anúncios presentes na seção Pendentes permanecem disponíveis por apenas 30 dias. Depois desse período, elas expiram automaticamente e o Seller precisará enviar novamente.
+</div>
+
+### Opções de catalogação
+
+Para catalogar um anúncio acesse a página **SKUs recebidos** no Admin VTEX clicando em **Marketplace > SKUs recebidos** ou digite **SKUs recebidos** na barra de busca do Admin.
+
+<div class="alert alert-info">
+Todos os anúncios da seção Pendentes podem ser catalogados individualmente ou em massa.
+</div>
+
+As ações disponíveis para catalogação são:
+
+- **Criar novo produto:** cria um SKU novo no catálogo e, consequentemente, um novo produto. Recomenda-se usar essa opção quando determinado produto ainda não existe no catálogo do marketplace. Para executar essa ação siga os passos abaixo:
+
+  1. Selecione os SKUs desejados.  
+  2. Clique no botão <i class="fas fa-plus" aria-hidden="true"></i> **`Criar novo produto`.**  
+  3. Preencha os campos **Categoria** e **Marca** para cada produto. Caso o mapeamento tenha sido realizado previamente, esses campos já estarão preenchidos.  
+  4. Clique em `Aprovar`.  
+
+![criar-novos-produtos-PT](//images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/07a3e80b2b4143779da1ebfdd29729a7/criar-novos-produtos-PT.png)
+
+<div class="alert alert-info">
+Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
+</div>
+
+- **Associar a um produto existente:** cria uma relação entre o produto do seller e um produto que já existe no catálogo do marketplace. Para executar essa ação siga os passos abaixo:
+
+  1. Selecione os SKUs desejados.  
+  2. Clique no botão <i class="fas fa-link" aria-hidden="true"></i> **`Associar a produto`**.  
+  3. Preencha o ID do produto ao qual será associado.
+  4. Clique em `Aprovar`.  
+
+![associar-a-produto-PT](//images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/d2130d8af5d5de678c36a6821316c09a/associar-a-produto-PT.png)
+
+**Caso de uso**
+
+Imagine que o marketplace já tenha o SKU Camisa Branca nos tamanhos P, M e G. Mas, recentemente, o seller enviou para estoque os tamanhos PP e GG da mesma Camisa Branca.  
+Ao criar uma nova associação, os tamanhos novos são agrupados com os demais que já estavam cadastrados. Dessa forma, o produto terá os tamanhos PP, P, M, G e GG disponíveis.
+
+<div class="alert alert-info">
+Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
+</div>
+
+- **Associar a um SKU existente:** cria uma relação entre o novo SKU do seller e um SKU que já existe no catálogo do marketplace. Para executar essa ação siga os passos abaixo:
+
+  1. Selecione os produtos desejados.  
+  2. Clique no botão <i class="fas fa-link" aria-hidden="true"></i> **`Associar a SKUs`.**  
+  3. Preencha o ID do SKU a associar para cada SKU que está sendo aprovado.  
+  4. Clique em `Aprovar`.  
+
+![associar-a-sku-PT](//images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/9a4c3fdb8049f6825fe752baae239b52/associar-a-sku-PT.png)
+
+**Caso de uso**
+
+Um possível caso seria o de um marketplace ter o “celular XYZ” com memória de 128GB do “seller1”.  
+
+Agora, digamos que o mesmo marketplace recebeu do “seller2” o mesmo SKU 128GB. Assim, para não duplicar o catálogo, o marketplace precisa associar esses SKUs.
+
+<div class="alert alert-info">
+Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
+</div>
+
+- **Recusar e bloquear:** bloqueia os anúncios selecionados e estes não serão mais reprocessados automaticamente. Para executar essa ação siga os passos abaixo:
+
+  1. Selecione os produtos desejados.  
+  2. Clique no botão **`Recusar e bloquear`.**  
+  3. Preencha o campo **Motivo de bloqueio.** O preenchimento é opcional.  
+  4. Clique em `Recusar`.  
+
+![recusar-e-bloquear-PT](//images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/35b8c59c3b4284047fba1882372c8e88/recusar-e-bloquear-PT.png)
+
+Quando um SKU é bloqueado pelo marketplace, significa que na próxima vez que o seller enviar seus produtos, aqueles que foram bloqueados não estarão mais em meio aos enviados. É possível desbloquear um SKU por API REST, se o marketplace deseja voltar a recebê-lo como sugestão do seller.  
+Para saber mais sobre aprovação de SKUs, acesse nossa documentação [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).
+
+<div class="alert alert-info">
+Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>. Os anúncios bloqueados serão exibidos na seção <b>Bloqueados</b>.
+</div>
+
+- **Recusar para correção:** rejeita o anúncio e envia para o seller a solicitação de correção de informação. Para executar essa ação siga os passos abaixo:
+
+  1. Selecione os SKUs desejados.  
+  2. Clique no botão **`Recusar para correção`.**  
+  3. Preencha o campo **correções** com a informação a ser corrigida pelo seller.  
+  4. Clique em `Recusar`.  
+
+![recusar-e-corrigir-PT](//images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/e53cdbf195194a408fb05f790f812083/recusar-e-corrigir-PT.png)
+
+<div class="alert alert-info">
+Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b>. Os anúncios para correção serão exibidos na seção <b>Problemas</b>.
+</div>
+
+**Aprovação automática:** também é possível configurar a aprovação automática de SKUs de um seller específico, independente da sua pontuação do Matcher. Essa ação só pode ser realizada por meio de API Rest. Confira as documentações de [Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions), para saber mais.
+
diff --git a/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
new file mode 100644
index 000000000..cba43e35d
--- /dev/null
+++ b/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -0,0 +1,106 @@
+---
+title: 'Recupere checkouts abandonados com WhatsApp AI Campaigns'
+id: 20i0zLQHt72LKzVEmk1CRZ
+status: PUBLISHED
+createdAt: 2024-06-25T11:27:41.160Z
+updatedAt: 2024-06-25T16:27:45.935Z
+publishedAt: 2024-06-25T16:27:45.935Z
+firstPublishedAt: 2024-06-25T15:29:15.011Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: recupere-checkouts-abandonados-com-whatsapp-ai-campaigns
+locale: pt
+legacySlug: recupere-checkouts-abandonados-com-whatsapp-ai-campaigns
+subcategory: 4SC2gPmUH3cHD5HjGfQ5Vg
+---
+
+O WhatsApp AI Campaigns, é uma funcionalidade desenvolvida pela VTEX,  para recuperar checkouts abandonados. 
+
+Quando um usuário abandona a página de pagamento de compras, a plataforma identifica essa ação. Se o usuário não retornar para concluir a compra no período de 1 hora, a funcionalidade envia uma mensagem de lembrete ao usuário por meio do WhatsApp.
+
+Os principais benefícios dessa funcionalidade são:
+
+- **Melhoria na experiência do cliente:** É possível personalizar  mensagens para aumentar a relevância e fortalecer a relação com a marca.
+
+- **Aumento nas taxas de conversão e vendas:** incentiva que os clientes retornem à página de pagamento para finalizar sua compra, aumentando desta forma as vendas e taxas de conversão para lojistas.
+
+<div class = "alert alert-info">
+O WhatsApp AI Campaigns está disponível  apenas para lojas que utilizam <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> que não tenham customizações no Checkout.
+</div>
+
+## Ativando WhatsApp AI Campaigns
+
+Para ativar a funcionalidade WhatsApp AI Campaigns você deve [instalar o aplicativo Connectly](#instalando-o-app-conectly) e depois [configurar um número de whatsapp no app](#configurando-novo-numero-de-whatsapp).
+
+### Instalando o App Connectly
+
+Para instalar o App Connectly, siga os passos abaixo:
+
+1. Acesse a [App Store](https://apps.vtex.com/) da VTEX.
+2. Na barra de busca digite connectly.
+3. Clique no app Connectly, em seguida clique em `Obter App`.
+4. Clique em `Realizar Pedido`.
+5. Clique em `Ir para a página de instalação`, e você será redirecionado para a seção **My Apps** do Admin VTEX.
+6. Na página de instalação do App Connectlyvtex clique em `instalar`
+7. Clique em `Salvar`.
+
+### Configurando novo número de WhatsApp
+
+Para configurar um novo número de WhatsApp você precisará ter acesso de administrador ao perfil do Facebook. Siga as instruções para configurar um novo número e concluir a vinculação:
+
+<ol start="1">
+  <li>No Admin VTEX, acesse <strong>Promoções &gt; Campanhas de WhatsApp &gt; Visão geral</strong>, ou digite <strong>Visão geral Campanhas de WhatsApp</strong> na barra de busca no topo da página.</li>
+  <li>Clique em <code>Configurar Conta</code>.</li>
+  <li>Selecione <strong>Sim, quero um número gratuito</strong>, e clique em <code>Próximo</code>.</li>
+  <li>Copie o número de telefone fornecido, e clique em <code>Conectar</code> para vincular este número à sua conta do <a href="https://www.facebook.com/business/news/what-is-meta-for-business">Facebook empresarial</a>.</li>
+  <li>Clique em <code>Continuar como Usuário</code>.</li>
+  <li>Clique em <code>Começar</code>.</li>
+  <li>Confirme se as informações de <strong>Portfólio Empresarial</strong>, <strong>Nome da Empresa</strong>, <strong>Site</strong> ou <strong>Perfil Comercial da Empresa</strong> e <strong>País</strong> estão corretas.</li>
+  <li>Clique em <code>Avançar</code>.</li>
+</ol>
+
+<p>Criando uma conta do WhatsApp Business:</p>
+
+<ol start="9">
+  <li>Selecione <strong>Criar uma conta do WhatsApp Business</strong> e <strong>Criar um novo perfil do WhatsApp Business</strong>.</li>
+  <li>Clique em <code>Avançar</code>.</li>
+  <li>Preencha os campos abaixo:
+    <ul>
+      <li><strong>Nome da conta do WhatsApp Business (interno)</strong>, exemplo: Nome da Loja VTEX.</li>
+      <li><strong>Nome de exibição do WhatsApp Business (visível aos clientes)</strong>, exemplo: Nome da loja.</li>
+      <li><strong>Categoria.</strong></li>
+      <li>Clique em <code>Avançar</code>.</li>
+    </ul>
+  </li>
+  <li>Cole o número de telefone copiado na etapa anterior, e selecione a opção de <strong>SMS</strong>, clique em <code>Avançar</code>.</li>
+</ol>
+
+<div class="alert alert-warning">
+  O número gerado pode ser americano, mas se a sua página do Facebook for verificada, seus clientes verão o nome da empresa. Caso não esteja verificada, recomendamos seguir o <a href="https://www.facebook.com/business/help/2058515294227817?id=180505742745347">processo de verificação com a Meta</a>.
+</div>
+
+<ol start="13">
+  <li>Copie o código de verificação exibido no Admin VTEX.</li>
+  <li>Cole o código de verificação no campo dentro do popup do Facebook, e clique em <code>Avançar</code>.</li>
+  <li>Clique em <code>Continuar</code>.</li>
+  <li>Clique em <code>Concluir</code>.</li>
+  <li>Escolha um logo de 400x400 px para o seu novo número de WhatsApp. A imagem não precisa estar em alta qualidade.</li>
+</ol>
+
+<p>Aceitando os termos e condições:</p>
+
+<ol start="18">
+  <li>Revise as páginas dos Termos e Condições.</li>
+  <li>Clique em <code>Concordo e Aceito</code>.</li>
+  <li>Clique em <code>Finalizar</code>.</li>
+</ol>
+
+<div class="alert alert-warning">
+Após ativada uma campanha de recuperação de checkout abandonado, pode levar até 48 horas para as métricas de análise começarem a ser exibidas.
+</div>
+
+<div class = "alert alert-info">
+Saiba mais sobre o <a href="https://help.vtex.com/pt/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">Gerenciamento e detalhes do WhatsApp AI Campaigns</a>.
+</div>
+
diff --git a/docs/tutorials/pt/redirect-from-other-addresses.md b/docs/tutorials/pt/redirect-from-other-addresses.md
new file mode 100644
index 000000000..7b1ede2a7
--- /dev/null
+++ b/docs/tutorials/pt/redirect-from-other-addresses.md
@@ -0,0 +1,81 @@
+---
+title: 'Redirecionamento de outros endereços'
+id: 3Xi2AeLUx2QpJQu8DTX8KQ
+status: PUBLISHED
+createdAt: 2022-09-19T21:21:24.455Z
+updatedAt: 2024-01-23T18:16:55.386Z
+publishedAt: 2024-01-23T18:16:55.386Z
+firstPublishedAt: 2022-09-19T21:40:22.913Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: redirecionamento-de-outros-enderecos
+locale: pt
+legacySlug: 
+subcategory: 2Za4fjGfxYOo6oqykukgyy
+---
+
+Uma loja virtual deve ter um único endereço principal, que irá [apontar para os servidores da VTEX](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ) antes do lançamento oficial da loja. Veja [Configurar o domínio da loja](https://help.vtex.com/pt/tutorial/configurar-o-dominio-da-loja--tutorials_2450) para saber as regras que o endereço precisa cumprir e como cadastrá-lo.
+
+Para permitir o acesso à loja por outros endereços e versões sem subdomínio, é necessário configurar o redirecionamento desses endereços para o endereço principal da loja, cadastrado em **Configurações da conta > Conta > Lojas** no Admin VTEX. Veja exemplos abaixo:
+
+| Endereço | Tipo |
+|---|---|
+| `www.minhaloja.com.br` | Domínio principal |
+| `www.enderecoantigo.com.br` | Redirecionamento |
+| `minhaloja.com.br` | Redirecionamento |
+
+## Configurar redirecionamentos
+
+Existem diversas maneiras de configurar redirecionamentos, sendo o uso do <code>[htaccess](https://developer.mozilla.org/en-US/docs/Learn/Server-side/Apache_Configuration_htaccess)</code> no servidor uma das mais conhecidas. Além disso, é possível usar um redirecionamento de DNS, disponibilizado por diversos serviços, incluindo provedores de domínio, como o [registro.br](https://registro.br/).
+
+A seguir, apresentaremos instruções para configurar redirecionamentos para o endereço principal da sua loja utilizando a ferramenta [Direcionar](http://direcionar.com.br/), por sua simplicidade de uso.
+
+<div class="alert alert-warning">
+  <p>O <a href="http://direcionar.com.br/">Direcionar</a> não é um serviço da VTEX e não funciona com HTTPS. Existem outros serviços similares, e a VTEX não recomenda nenhum específico. A VTEX não se responsabiliza por problemas causados por serviços externos de redirecionamento.</p>
+</div>
+
+### Redirecionamento de endereço sem subdomínio (como www)
+
+Para acessar a loja por meio de um endereço sem subdomínios, como `www`, é preciso criar um redirecionamento para o endereço principal da sua loja. Por exemplo, para ser possível acessar `http://www.meusite.com` a partir do endereço sem subdomínio `http://meusite.com`, é necessário criar um redirecionamento no seu provedor de DNS conforme as instruções abaixo:
+
+1. Crie um registro do tipo A para a raiz do domínio, geralmente representada por `.`, `@` ou apenas `meusite.com`, apontando para `52.8.174.221` (IP da [Direcionar](http://direcionar.com.br/)).
+
+   |   |   |   |
+   |---|---|---|
+   | Host Record: <deixe-vazio\> | Type: A | To: 52.8.174.221 |
+
+2. Crie um registro do tipo CNAME de `redirect` (ou `redirect.meusite.com`), apontando para `www.meusite.com.direcionar.com.br`.
+
+  |   |   |   |
+  |---|---|---|
+  | Host Record: redirect | Type: CNAME | To: www.meusite.com.direcionar.com.br |
+
+Saiba mais sobre situações como essa em [Melhores práticas para acessar a loja sem www](https://help.vtex.com/pt/tutorial/melhores-praticas-para-acessar-a-loja-sem-www--tutorials_4278).
+
+A propagação do redirecionamento pode levar alguns minutos para ser concluída, a depender do provedor de DNS.
+
+### Redirecionamento de um endereço para outro
+
+Para realizar o redirecionamento de um endereço para outro que não compartilha a mesma raiz do domínio, crie uma entrada CNAME no endereço antigo (origem do acesso), seguindo o padrão `{endereçoNovo}.opts-uri.direcionar.com.br`.
+
+Por exemplo, para redirecionar de `www.dominioantigo.com` para `www.novodominio.com.br`:
+
+* Crie uma entrada `www` no domínio `dominioantigo.com` com o CNAME `www.novodominio.com.opts-uri.direcionar.com.br`.
+
+Para redirecionar de `loja.algumendereco.com.br` para `www.site.com`:
+
+* Crie uma entrada `loja` no domínio `algumendereco.com.br` com o CNAME `www.site.com.opts-uri.direcionar.com.br`.
+
+### Redirecionamento de acessos com HTTPS
+
+A VTEX direciona automaticamente endereços `http://` para `https://` . Ainda assim, pode ser necessário redirecionar um endereço `https://` (como uma versão do endereço sem subdomínio ou com outro domínio) para um endereço com `https://`.
+
+Ao acessar uma página com HTTPS, é necessário que o servidor que responde pelo endereço tenha um certificado SSL instalado. A ausência desse certificado faz com que o navegador interprete a conexão como não segura, resultando no bloqueio da requisição. Isso impede o acesso à página desejada e, consequentemente, inviabiliza o redirecionamento para outro endereço.
+
+No [Direcionar](http://direcionar.com.br/), não é possível instalar um certificado SSL para cada domínio a ele apontado. Sendo assim, ele não redireciona acessos originados em HTTPS.
+
+Para lidar com essa limitação, considere os seguintes pontos:
+
+1. Se o domínio de origem não possui subdomínio, como `site.com`, aponte-o para um servidor de gestão da própria loja, ou seja, um servidor físico ou virtual que é administrado pelo próprio usuário ou empresa. Este servidor deve possuir um **certificado SSL instalado para o domínio de origem**, viabilizando o acesso seguro via HTTPS. Acesse [Certificado de segurança (SSL)](https://help.vtex.com/pt/tutorial/certificado-de-seguranca-ssl--tutorials_1308) para mais informações.
+2. Defina uma **regra de redirecionamento**. Para usar um servidor de gestão própria para redirecionar acessos com HTTPS, você precisará definir uma regra de redirecionamento no servidor. Ela pode variar conforme o tipo de servidor utilizado (Apache, ASP, nginx). Portanto, para configurar essa regra, você deve saber qual tipo de servidor está sendo usado e aplicar as configurações correspondentes.
diff --git a/docs/tutorials/pt/redirects.md b/docs/tutorials/pt/redirects.md
new file mode 100644
index 000000000..b72a0491e
--- /dev/null
+++ b/docs/tutorials/pt/redirects.md
@@ -0,0 +1,41 @@
+---
+title: 'Redirecionamentos'
+id: 3okF84cImJwKzcc8hxmZ2r
+status: PUBLISHED
+createdAt: 2024-06-27T17:04:44.975Z
+updatedAt: 2024-06-27T17:05:31.676Z
+publishedAt: 2024-06-27T17:05:31.676Z
+firstPublishedAt: 2024-06-27T17:05:31.676Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: redirecionamentos
+locale: pt
+legacySlug: redirecionamentos
+subcategory: 1wvyJwJhKgewxGeAGCVmM6
+---
+
+**Redirecionamentos** direciona o cliente para qualquer outra página, seja interna ou externa à loja. Esse redirecionamento é feito na área de busca do seu storefront, utilizando termos ou filtros selecionados pelo cliente. Desse modo, uma das vantagens dos Redirecionamentos é contemplar cenários de comunicação que a busca de catálogo da loja não abrange, como o redirecionamento de uma pesquisa por uma marca para a sua página promocional.
+
+<div class="alert alert-warning">
+<p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo VTEX Intelligent Search: configurações Multi-idioma (Beta) para saber mais.</p>
+</div>
+
+## Como o redirecionamento funciona
+
+Ao criar um redirecionamento, é necessário também criar condições - chamadas regras. Elas devem conter um conjunto tanto de termos quanto de filtros cadastrados. A quantidade de regras é ilimitada por redirecionamento.
+
+Com a ferramenta, é viável criar regras que contemplam os interesses do gestor e do cliente final simultaneamente. Outros benefícios são:
+
+- Aumentar as possibilidades da busca do site. Buscas sem resultados geram estatisticamente Taxa de Rejeição (Bounce Rate) - porcentagem de visitantes que entram no site e saem sem ver outras páginas - para o ecommerce.
+- Facilitar a usabilidade do cliente final, como em situações de pós-compra ou em ações promocionais.
+
+Após o cliente ter efetuado a busca, o VTEX Intelligent Search captura o termo pesquisado e verifica se existe alguma regra de redirecionamento cadastrada relacionada a essa busca.
+
+O termo pesquisado é elegível quando já existe, pelo menos, uma regra referente a ele. Assim, o cliente é redirecionado para a URL cadastrada.
+
+Caso o cliente pesquise por "meus pedidos" ou "pedidos", você pode criar um redirecionamento que direcione ele para os pedidos da conta em vez de visualizar uma página de busca vazia.
+
+Além disso, você também pode configurar a ferramenta para direcionar o cliente para uma landing page de promoções específicas. Nesse caso, o cliente que pesquisar por "black friday" será direcionado para essa promoção.
+
+Em outro cenário, caso o cliente pesquise por "tênis de corrida" e filtre pela marca Nike, ele será levado para uma página específica da marca.
diff --git a/docs/tutorials/pt/registering-a-category.md b/docs/tutorials/pt/registering-a-category.md
index 1b4d366d7..b2f5d69e8 100644
--- a/docs/tutorials/pt/registering-a-category.md
+++ b/docs/tutorials/pt/registering-a-category.md
@@ -3,8 +3,8 @@ title: 'Cadastrar uma Categoria'
 id: tutorials_206
 status: PUBLISHED
 createdAt: 2017-04-27T22:15:39.383Z
-updatedAt: 2023-03-29T17:45:06.786Z
-publishedAt: 2023-03-29T17:45:06.786Z
+updatedAt: 2023-11-29T19:10:35.853Z
+publishedAt: 2023-11-29T19:10:35.853Z
 firstPublishedAt: 2017-04-27T23:00:46.516Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -38,5 +38,5 @@ Siga o passo a passo para cadastrar suas categorias:
 - [Preencher campos de cadastro de categoria](/pt/tutorial/campos-de-cadastro-de-categoria)
 - [Excluir uma Categoria](/pt/tutorial/entendendo-a-manutencao-da-base-de-dados)
 - [Cadastrar um Produto](/pt/tutorial/cadastrando-produto)
-- [Cadastrar um SKU](/pt/tutorial/cadastrando-sku)
+- [Cadastrar um SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ?&utm_source=autocomplete)
 
diff --git a/docs/tutorials/pt/registering-brands.md b/docs/tutorials/pt/registering-brands.md
index 0115de444..45828225e 100644
--- a/docs/tutorials/pt/registering-brands.md
+++ b/docs/tutorials/pt/registering-brands.md
@@ -23,4 +23,4 @@ Para cadastrar uma marca, siga os passos abaixo:
 4. Preencha os [campos de cadastro de marca](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-marca--37Ky7lTbEkiWIAYA80EMyI).
 5. Clique no botão `Salvar`.
 
-![cadastrarmarcas3](https://images.ctfassets.net/alneenqid6w5/4PK9aPVzNJrp478wRsSUM0/6aabac3201d04805ea18c3d03c11593c/cadastrarmarcas3.PNG)
+![cadastrarmarcas3](//images.ctfassets.net/alneenqid6w5/4PK9aPVzNJrp478wRsSUM0/6aabac3201d04805ea18c3d03c11593c/cadastrarmarcas3.PNG)
diff --git a/docs/tutorials/pt/registering-gateway-affiliations.md b/docs/tutorials/pt/registering-gateway-affiliations.md
index ae9afc04b..d6a9ecdf4 100644
--- a/docs/tutorials/pt/registering-gateway-affiliations.md
+++ b/docs/tutorials/pt/registering-gateway-affiliations.md
@@ -1,10 +1,10 @@
 ---
-title: 'Cadastrar afiliações de gateway'
+title: 'Cadastrar provedores de pagamento e antifraude'
 id: tutorials_444
 status: PUBLISHED
 createdAt: 2017-04-27T22:05:18.209Z
-updatedAt: 2023-03-21T20:55:24.198Z
-publishedAt: 2023-03-21T20:55:24.198Z
+updatedAt: 2024-01-22T20:37:11.273Z
+publishedAt: 2024-01-22T20:37:11.273Z
 firstPublishedAt: 2017-04-27T23:03:24.823Z
 contentType: tutorial
 productTeam: Financial
@@ -15,27 +15,81 @@ legacySlug: afiliacoes-de-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Afiliação de gateway é um conjunto de configurações que representa o seu contrato com um provedor de pagamento (gateway, adquirente ou subadquirente). 
+Com a VTEX, você pode realizar a configuração de diversos provedores: gateways, adquirentes, subadquirentes, [orquestradores](https://www.y.uno/br), [PSPs](https://en.wikipedia.org/wiki/Payment_service_provider), entre outros. Estes lhe permitem oferecer diferentes métodos e condições de pagamentos aos seus clientes, bem como serviços de proteção de antifraude. Anteriormente, essas configurações eram conhecidas em nosso sistema como afiliações de gateway.
 
-Na VTEX, você pode realizar a configuração de diversos provedores de pagamentos e oferecer diferentes métodos e condições de pagamentos aos seus clientes.
+Por meio da tela de gerenciamento de provedores você pode:
 
-Para configurar uma afiliação de gateway, siga os passos abaixo:
+- [Cadastrar um novo provedor](#cadastrar-provedor)
+- [Visualizar provedores cadastrados](#visualizar-provedores-cadastrados)
+- [Editar configurações de provedores](#editar-configuracoes-de-provedores)
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
+![interface_provedor_PT_1](//images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/d997ea6d0bf7807c1219d307933467e6/interface_provedor_PT_1.JPG)
+
+## Cadastrar provedor
+
+Para adicionar um novo provedor de pagamento ou antifraude em sua loja, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Clique em `Novo provedor`.
 3. Clique no provedor de pagamento de sua preferência.
-4. Preencha os campos __Application Key__ e __Application Token__ com as informações fornecidas pelo provedor de pagamento.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações fornecidas pelo provedor de pagamento.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão __Instalar app__ e siga as instruções de instalação. Esta mensagem é exibida somente para alguns tipos de afiliações de gateway.
-6. Clique em __Salvar__.
+6. Clique em `Salvar`.
 
 <div class = "alert alert-info">
-  <p>Caso haja outros campos a serem preenchidos além do <b>Application Key</b> e <b>Application Token</b> (Passo 6), a afiliação de gateway deve ser configurada conforme tutorial específico. Para maiores informações, verifique a subseção <a href="https://help.vtex.com/pt/subcategory/configuracoes-de-pagamentos--3tDGibM2tqMyqIyukqmmMw">Configurações de Pagamento</a>.</p>
+  <p>Caso haja outros campos a serem preenchidos além do <b>Chave de aplicação</b> e <b>Token de aplicação</b> (Passo 6), o provedor deve ser configurado conforme tutorial específico. Para maiores informações, verifique a subseção <a href="https://help.vtex.com/pt/subcategory/configuracoes-de-pagamentos--3tDGibM2tqMyqIyukqmmMw">Configurações de Pagamento</a>.</p>
 </div>
 
 <div class = "alert alert-danger">
-  As credenciais utilizadas para preencher os campos <strong>Application Key</strong> e <strong>Application Token</strong> devem ser fornecidas pelo provedor de pagamentos para identificar a loja. Não devem ser utilizadas <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet#gerar-chaves-de-aplicacao-na-sua-conta">credenciais geradas no Admin</a>, que se iniciam com <code>vtexappkey-</code>.
+  As credenciais utilizadas para preencher os campos <strong>Chave de aplicação</strong> e <strong>Token de aplicação</strong> devem ser fornecidas pelo provedor de pagamentos para identificar a loja. Não devem ser utilizadas <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet#gerar-chaves-de-aplicacao-na-sua-conta">credenciais geradas no Admin</a>, que se iniciam com <code>vtexappkey-</code>.
 </div>
 
 Para configurar os métodos de pagamento a serem processados pelo provedor de pagamento escolhido, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
 
 Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete).
+
+![interface_provedor_PT_2](//images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/03ec92c0a18fd9cc8b368fd27a4eeee2/artigo_interface_provedor_PT_2.JPG)
+
+## Visualizar provedores cadastrados
+
+A tela principal de gerenciamento de provedores, disponível no Admin VTEX em __Configurações > Pagamentos > Provedores__, exibe todos os provedores de pagamento ou antifraude cadastrados em uma loja. Para permitir o acesso rápido a informações de provedores específicos é possível realizar uma busca ou utilizar um filtro.
+
+### Buscar provedores
+
+Para localizar provedores pelo nome, acesse a página de gerenciamento de provedores e digite o nome do provedor desejado.
+
+![interface_provedor_PT_3](//images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/b7489e1bd5b8f23cf1c41190266c7178/interface_provedor_PT_3.JPG)
+
+### Filtrar provedores
+
+Para selecionar a exibição de provedores por meio de filtros, acesse a página de gerenciamento de provedores e aplique um ou mais filtros indicados abaixo, conforme desejado.
+
+- __Nome__: selecione a exibição de provedores de pagamento por meio do nome, ativando a caixa de texto ou digitando na barra de busca do menu.
+
+![interface_provedor_PT_4](//images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/b994729bad2abcc7fff53dbae2c45788/interface_provedor_PT_4.JPG)
+
+- __Tipo__: selecione a exibição de provedores de pagamento, antifraude ou ambos.
+
+![interface_provedor_PT_5](//images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/52542c9cbf58ab10d6527e5b5c8efd17/interface_provedor_PT_5.JPG)
+
+- __Ambiente__: selecione a exibição de provedores pelo tipo de ambiente de operação cadastrado (produção ou teste).
+
+![interface_provedor_PT_6](//images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/fe3d094d3ce7e5463841694309b28a52/interface_provedor_PT_6.JPG)
+
+<div class = "alert alert-danger">
+Para remover os filtros aplicados e voltar a visualizar todos os provedores cadastrados na loja, clique no botão <code>Limpar todos</code>.</div>
+
+### Editar configurações de provedores
+
+Para editar configurações de provedores de pagamento ou antifraude já cadastrados na loja, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Clique no provedor de pagamento ou antifraude desejado.
+3. Na tela de configuração do provedor, clique em `Editar`.
+4. Realize as modificações necessárias e clique em `Salvar`.
+
+![interface_provedor_PT_7](//images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/1852b341c59e2ac6419504214fcfdee0/artigo_interface_provedor_PT_7.JPG)
+
+<div class = "alert alert-danger">
+Antes de realizar qualquer alteração na configuração de um provedor, como por exemplo: dados de autorização, modo de processamento ou tipo de reembolso, certifique-se de que as novas informações a serem inseridas não irão prejudicar o seu desempenho operacional na loja.</div>
+
diff --git a/docs/tutorials/pt/registering-geolocation.md b/docs/tutorials/pt/registering-geolocation.md
index b050f8d5c..1549ec0ee 100644
--- a/docs/tutorials/pt/registering-geolocation.md
+++ b/docs/tutorials/pt/registering-geolocation.md
@@ -3,8 +3,8 @@ title: 'Cadastrar geolocalização'
 id: tutorials_138
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:36.462Z
-updatedAt: 2023-03-29T13:25:16.724Z
-publishedAt: 2023-03-29T13:25:16.724Z
+updatedAt: 2023-08-25T14:52:20.340Z
+publishedAt: 2023-08-25T14:52:20.340Z
 firstPublishedAt: 2017-04-27T23:00:44.871Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -32,6 +32,10 @@ Acessando o link [Gere seus polígonos com geojson.io](http://geojson.io/#map=2/
 
 Esse JSON será usado para adicionar o polígono na plataforma, que entenderá a partir dessa linguagem quais códigos postais estão inclusos nessa área.
 
+<div class="alert alert-danger">
+Na configuração de um polígono, não é possível delimitar áreas sobrepostas, ou seja, não é possível sobrepor coordenadas geográficas.
+</div>
+
 ### Como adicionar um polígono
 
 Ao adicionar um polígono, é preciso nomeá-lo, de modo que ele seja identificado na planilha de frete, para que depois possa ser consultado por meio do código postal.
diff --git a/docs/tutorials/pt/registering-the-skus-barcode-for-vtex-sales-app.md b/docs/tutorials/pt/registering-the-skus-barcode-for-vtex-sales-app.md
index df9b0c0ea..8ac6229f7 100644
--- a/docs/tutorials/pt/registering-the-skus-barcode-for-vtex-sales-app.md
+++ b/docs/tutorials/pt/registering-the-skus-barcode-for-vtex-sales-app.md
@@ -3,8 +3,8 @@ title: 'Cadastrar os códigos de barras dos SKUs para o VTEX Sales App'
 id: 2jkOdRB4XSMG2ke0uUQIKS
 status: PUBLISHED
 createdAt: 2018-03-12T17:23:32.837Z
-updatedAt: 2023-05-31T16:11:54.350Z
-publishedAt: 2023-05-31T16:11:54.350Z
+updatedAt: 2023-07-26T19:04:52.107Z
+publishedAt: 2023-07-26T19:04:52.107Z
 firstPublishedAt: 2018-03-12T17:27:18.421Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -17,9 +17,9 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 É no catálogo da VTEX que cadastramos os produtos e definimos suas características.
 
-Nesta etapa, cadastramos o código de barras dos SKUs. O código de barras é a informação que possibilita o produto ser adicionado facilmente ao carrinho do inStore. Para adicionar o produto, basta passar o código de barras na máquina leitora. O inStore também permite que o código de barras seja digitado.
+Nesta etapa, cadastramos o código de barras dos SKUs. O código de barras é a informação que possibilita o produto ser adicionado facilmente ao carrinho do VTEX Sales App. Para adicionar o produto, basta passar o código de barras na máquina leitora. O VTEX Sales App também permite que o código de barras seja digitado.
 
-Normalmente, o catálogo do inStore é herdado do cátálogo do e-commerce. Neste cenário, faz-se necessário apenas cadastrar o EAN (campo que deve conter a informação do código de barras) nos SKUs.
+Normalmente, o catálogo do VTEX Sales App é herdado do cátálogo do e-commerce. Neste cenário, faz-se necessário apenas cadastrar o EAN (campo que deve conter a informação do código de barras) nos SKUs.
 
 Para cadastrar o EAN dos SKUs, siga os passos abaixo:
 
@@ -31,4 +31,4 @@ Para cadastrar o EAN dos SKUs, siga os passos abaixo:
 4. No campo __EAN__, preencha com o valor do código de barras.
 5. Clique em `Salvar`.
 
-A informação do EAN pode levar até 10 minutos para se atualizada. Após este procedimento, já será possível adicionar o SKU ao carrinho do inStore através da máquina leitora de código de barras.
+A informação do EAN pode levar até 10 minutos para se atualizada. Após este procedimento, já será possível adicionar o SKU ao carrinho do VTEX Sales App através da máquina leitora de código de barras.
diff --git a/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
index a3dbaa3be..135883e1e 100644
--- a/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -19,7 +19,7 @@ Ao criar uma [promoção regular](https://help.vtex.com/pt/tutorial/promocao-reg
 
 Selecionando esse tipo de desconto, você precisa criar uma fórmula para definir qual será o cálculo do desconto aplicado. Neste artigo, explicamos como construir uma fórmula para atender aos objetivos da sua promoção.
 
-![tipo-desconto-formula](https://images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/fa412a32b6d8d56b3652332ade308dd0/image1.png)
+![tipo-desconto-formula](//images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/fa412a32b6d8d56b3652332ade308dd0/image1.png)
 
 De modo geral, a fórmula para calcular o desconto nominal da promoção segue a mesma lógica das [fórmulas do Microsoft Excel](https://support.microsoft.com/pt-br/office/f%C3%B3rmulas-e-fun%C3%A7%C3%B5es-294d9486-b332-48ed-b489-abe7d0f9eda9), ou seja, você pode utilizar [variáveis](#variaveis) (`total`, `freight` e `quantity`), realizar [operações](#operacoes) (soma, subtração, multiplicação e divisão), e aplicar [funções](#funcoes) (`min` e `max`).
 
@@ -78,19 +78,19 @@ Assim, a promoção vai aplicar o menor valor de desconto em cada caso, comparan
 
 Um cliente adicionou ao carrinho um item cujo preço é R$45. Ao calcular 20% do total do preço, o resultado é 9, já que `total * 0.2 = 9`. Como 9 está abaixo do valor limite de desconto, o desconto aplicado será R$9.
 
-![cenario-1](https://images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/f02144b4ab13eedb33d12f478c273f3d/image3.png)
+![cenario-1](//images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/f02144b4ab13eedb33d12f478c273f3d/image3.png)
 
 #### Cenário 2
 
 Outro cliente adicionou ao carrinho um item cujo preço é R$ 2600. Calculando 20% desse valor, o resultado é 520, já que `total * 0.2 = 520`. Como esse valor está acima do limite (R$10), o desconto aplicado será de R$10.
 
-![cenario-2](https://images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/8da8d4eb9f5facad8c1023e115a9cdae/image7.png)
+![cenario-2](//images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/8da8d4eb9f5facad8c1023e115a9cdae/image7.png)
 
 #### Cenário 3
 
 Um terceiro cliente adicionou dois itens ao carrinho: um cujo preço é R$100 e outro cujo preço é R$2600. A soma desses valores é R$2700, visto que `total = 2700`. Ao calcular 20% do valor total, obtemos o resultado de 540, já que `total * 0.2 = 540`. Como esse valor está acima do limite (R$10), o desconto total aplicado será de R$10.
 
-![cenario-3](https://images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/2d57ca1c8a1f0093721d6fc14fc96095/image2.png)
+![cenario-3](//images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/2d57ca1c8a1f0093721d6fc14fc96095/image2.png)
 
 O desconto total de R$10 é distribuído proporcionalmente entre os itens, considerando o preço e a quantidade de cada um. Essa distribuição é feita automaticamente pela plataforma, seguindo a lógica explicada a seguir.
 
diff --git a/docs/tutorials/pt/regular-promotion-with-reward-value.md b/docs/tutorials/pt/regular-promotion-with-reward-value.md
index b6eaed98f..61dddab23 100644
--- a/docs/tutorials/pt/regular-promotion-with-reward-value.md
+++ b/docs/tutorials/pt/regular-promotion-with-reward-value.md
@@ -39,7 +39,7 @@ O **Valor fidelidade nominal** adiciona um valor fixo de crédito na conta do us
 
 No exemplo ilustrado a seguir, os clientes ganharão um crédito de R$10,00 na loja quando o status do pedido mudar para **Faturado**.
 
-![vf-nominal-pt](https://images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/f2498f3f46cbafe7e1d8dd747422cce8/vf-nominal-pt.png)
+![vf-nominal-pt](//images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/f2498f3f46cbafe7e1d8dd747422cce8/vf-nominal-pt.png)
 
 ### Valor fidelidade percentual
 
@@ -50,7 +50,7 @@ O **Valor fidelidade percentual** adiciona um valor percentual de crédito basea
 
 No exemplo ilustrado a seguir, os clientes ganharão um crédito de 20% do valor da compra quando o status do pedido mudar para **Pagamento aprovado**.
 
-![vf-percentual-pt](https://images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4373e3263836d3388356a06dc025f73a/vf-percentual-pt.png)
+![vf-percentual-pt](//images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4373e3263836d3388356a06dc025f73a/vf-percentual-pt.png)
 
 ## Como configurar restrições
 
@@ -86,17 +86,17 @@ Quando um cliente faz um pedido elegível para receber crédito fidelidade, voc
 
 Na seção **Promoções e parcerias**, aparece o nome da promoção aplicada ao pedido:
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/9b4ede20a2b910d2a4c2b117a4e0b7ec/detalhes-oms-pt__1_.png" alt="detalhes-do-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/1LpXT5YXqbsjb02eAQUsfg/9b4ede20a2b910d2a4c2b117a4e0b7ec/detalhes-oms-pt__1_.png" alt="detalhes-do-pedido" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido</em></figcaption></figure>
 
-<img class="db center mv9 shadow-4 pointer" src="https:https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/b9de1a7d07c48b49026ec6d3adba4d20/detalhes-neworders-pt__1_.png" alt="detalhes-do-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido (Beta)</em></figcaption></figure>
+<img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/2mriJhUbQbqrrUSbp7tjaC/b9de1a7d07c48b49026ec6d3adba4d20/detalhes-neworders-pt__1_.png" alt="detalhes-do-pedido-beta" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Detalhes do pedido (Beta)</em></figcaption></figure>
 
 Na seção __Fluxo do pedido__, é possível verificar o valor fidelidade concedido:
 
-![fluxo-oms-pt](https://images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/57cc8d05f5a909b360634d35bb5eb54e/fluxo-oms-pt__1_.png)
+![fluxo-oms-pt](//images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/57cc8d05f5a909b360634d35bb5eb54e/fluxo-oms-pt__1_.png)
 
 Se você utiliza a nova interface de [Detalhes do pedido (Beta)](https://help.vtex.com/pt/tutorial/order-details-page-beta--2Y75n54Cc9VizrlG1N6ZNl), acesse `Ver interações` para verificar o valor concedido:
 
-![interacoes-neworders-pt (1)](https://images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/0b7c14a0db14110258c907a78377ec7a/interacoes-neworders-pt__1_.png)
+![interacoes-neworders-pt (1)](//images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/0b7c14a0db14110258c907a78377ec7a/interacoes-neworders-pt__1_.png)
 
 Considere que a promoção aplicada no pedido ilustrado oferece **Valor fidelidade percentual** de **50%**. Por isso, a cliente ganhou um crédito de `R$ 54,28` para as próximas compras na loja, que equivale a **50%** de `R$ 108,55`, o valor total do pedido.
 
@@ -104,13 +104,13 @@ Considere que a promoção aplicada no pedido ilustrado oferece **Valor fidelida
 
 O valor fidelidade disponível para uso é apresentado para os clientes da sua loja na etapa de **Pagamento** durante o checkout, conforme ilustrado a seguir.
 
-![checkout-pt (1)](https://images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
+![checkout-pt (1)](//images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
 
 O valor concedido pode ser utilizado para compor o pagamento. Para isso, o cliente deve clicar em `utilizar crédito` e, em seguida, digitar o valor que deseja utilizar.
 
 Observe que o valor será descontado da outra forma de pagamento selecionada. No exemplo a seguir, o boleto passou a ter o valor de `R$ 113,50`, que corresponde a `R$ 167,80` menos o valor fidelidade utilizado (`R$ 54,30`).
 
-![checkout-2-pt (1)](https://images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
+![checkout-2-pt (1)](//images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/regular-promotion.md b/docs/tutorials/pt/regular-promotion.md
index ba7d35bbb..c60d28a60 100644
--- a/docs/tutorials/pt/regular-promotion.md
+++ b/docs/tutorials/pt/regular-promotion.md
@@ -1,10 +1,10 @@
 ---
 title: 'Promoção Regular'
 id: tutorials_327
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-04-27T22:07:59.690Z
-updatedAt: 2022-12-08T19:33:36.098Z
-publishedAt: 2022-08-23T19:50:18.784Z
+updatedAt: 2024-05-15T16:38:18.730Z
+publishedAt: 2024-05-15T16:38:18.730Z
 firstPublishedAt: 2017-04-27T23:03:15.647Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -90,7 +90,7 @@ Para que a promoção seja válida para todas as políticas comerciais, deixe a
 
 Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
 
-![promocoes-restricao-pt](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
+![promocoes-restricao-pt](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
 
 Caso deseje aplicar a promoção a todo o seu catálogo, selecione a opção **Aplicar a todos os produtos**.
 
@@ -100,7 +100,7 @@ Você pode incluir ou excluir **Categorias**, **Marcas**, **Coleções**, **Prod
 
 Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção todos os produtos da categoria **Vestido** cuja marca é **Farm**, com a exceção do produto **Vestido Rosas**.
 
-![exemplo-pt](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/6c40e996aece6e87b82b0bc71a50f3e5/image.png)
+![exemplo-pt](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/6c40e996aece6e87b82b0bc71a50f3e5/image.png)
 
 Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
 
@@ -114,12 +114,12 @@ Para serem válidos na promoção, os produtos precisam atender a todas as condi
 
 O pedido do cliente deve atender às condições cadastradas nesta seção para ser válido na promoção.
 
-- **Valor mínimo e máximo do pedido:** a promoção será aplicada levando em conta o valor "bruto" do carrinho, sem considerar demais promoções ou frete.
+- **Valor mínimo e máximo do pedido:** para promoções de preço que ajustam diretamente o valor dos itens no carrinho, a ativação da promoção é baseada no preço original dos itens. E para promoções que oferecem outros benefícios, como frete gratuito ou brindes, o preço considerado para ativar a promoção é o preço já com descontos aplicados.
 - **Valor acumulado em compras:** o desconto será concedido caso o total de todas as compras já realizadas pelo cliente, esteja atendendo ao valor preenchido.
 - **Valor do item entre:** o desconto será concedido caso o valor do item estiver atendendo ao intervalo de valores preenchidos.
 - **Preço "de" e "por" são iguais** ou **Preço "de" e "por" são diferentes:**  se refere aos valores do cadastro do produto. Somente uma opção pode ser selecionada.
 - **Restrição de Promoção por BIN:** o desconto será concedido caso o BIN do cartão esteja entre os número preenchidos preenchidos.
-- **Marketing Tags:** campo utilizado para restringir a ativação da promoção caso a compra seja realizada pelo [módulo de Assinaturas da VTEX](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453#). 
+- **Marketing Tags:** campo utilizado para restringir a ativação da promoção.
 - **Afiliados:** identificador de pedidos do marketplace. O desconto será aplicado nos afiliados selecionados. Veja o artigo [O que é afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0?locale=pt) para mais informações.
 - **Cluster de clientes:** o desconto será concedido caso o cliente esteja cadastrado no cluster selecionado. É importante destacar que o nome do cluster deve ser exatamente como cadastrado, qualquer erro de grafia impedirá o funcionamento correto da configuração.
 - **Países de entrega**: o desconto será concedido aos países selecionados neste campo.
diff --git a/docs/tutorials/pt/releases-module-beta.md b/docs/tutorials/pt/releases-module-beta.md
index 2ea1b2b1d..ff467b48f 100644
--- a/docs/tutorials/pt/releases-module-beta.md
+++ b/docs/tutorials/pt/releases-module-beta.md
@@ -73,7 +73,7 @@ Nesta etapa, não é obrigatório preencher os campos <b>Dia da publicação</b>
 
 8. Clique em `Criar`.
 
-![print_cms_paginas_pt](https://images.ctfassets.net/alneenqid6w5/qAAAv5fblHtY8C930fegs/10a16411a1e4d6ac49fcdf0e5729c88b/print_cms_paginas.png)
+![print_cms_paginas_pt](//images.ctfassets.net/alneenqid6w5/qAAAv5fblHtY8C930fegs/10a16411a1e4d6ac49fcdf0e5729c88b/print_cms_paginas.png)
 
 ### Criar usando o módulo Lançamentos
 
@@ -94,7 +94,7 @@ Nesta etapa, não é obrigatório preencher os campos <b>Dia da publicação</b>
 
 Todos os lançamentos criados aparecem listados no Admin VTEX, em **Configurações da loja > Lançamentos**. A página apresenta duas abas, a `AGENDADOS` e a `NÃO AGENDADOS`, dependendo se o lançamento foi criado com uma data de publicação ou não. 
 
-![print_lancamentos_pt](https://images.ctfassets.net/alneenqid6w5/5i9KXnDxE2lc3xqcdA3Ts7/a7466170347535b2062f66a533cfc2f6/print_lancamentos.png)
+![print_lancamentos_pt](//images.ctfassets.net/alneenqid6w5/5i9KXnDxE2lc3xqcdA3Ts7/a7466170347535b2062f66a533cfc2f6/print_lancamentos.png)
 
 Na aba `AGENDADOS`, a descrição de cada coluna é a seguinte:
 
diff --git a/docs/tutorials/pt/releasing-the-store-for-production.md b/docs/tutorials/pt/releasing-the-store-for-production.md
index a2725bbf4..23670fa4d 100644
--- a/docs/tutorials/pt/releasing-the-store-for-production.md
+++ b/docs/tutorials/pt/releasing-the-store-for-production.md
@@ -30,7 +30,7 @@ Depois, é preciso colocar a loja com status de produção no License Manager d
 4. Na opção **Está em produção**, clique no botão **Não**, ficando **Sim**;
 5. Clique no botão **Salvar**.
 
-![contas.pt](https://images.ctfassets.net/alneenqid6w5/7bNDNf7soYiH98n5m8GFI6/695149200124cd522b0e2b6962014cf9/contas.pt.png)
+![contas.pt](//images.ctfassets.net/alneenqid6w5/7bNDNf7soYiH98n5m8GFI6/695149200124cd522b0e2b6962014cf9/contas.pt.png)
 
 Após esta configuração, ao acessar a url final da loja, ela já será redirecionada para seu e-commerce!
 
diff --git a/docs/tutorials/pt/relevance-rules.md b/docs/tutorials/pt/relevance-rules.md
new file mode 100644
index 000000000..36bf23e61
--- /dev/null
+++ b/docs/tutorials/pt/relevance-rules.md
@@ -0,0 +1,114 @@
+---
+title: 'Regras de relevância'
+id: 1o9jtVGjSIiptbqdNXIlNK
+status: PUBLISHED
+createdAt: 2024-06-27T17:12:27.900Z
+updatedAt: 2024-06-27T17:13:52.839Z
+publishedAt: 2024-06-27T17:13:52.839Z
+firstPublishedAt: 2024-06-27T17:13:52.839Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: regras-de-relevancia
+locale: pt
+legacySlug: regras-de-relevancia
+subcategory: 32zXHBMygA2dB6TbCjQJej
+---
+
+As **Regras de relevância** definem a ordem em que os produtos são exibidos nos resultados de busca nas páginas de listagem de produtos (PLP). A ordem muda de acordo com os critérios e prioridades configurados.
+
+As Regras de relevância são aplicadas nos resultados de busca apenas quando a ordenação dos resultados é feita por relevância na busca da sua loja. Por exemplo, se um cliente selecionar a ordenação dos resultados por preço, as configurações de relevância não terão efeito na ordem dos resultados.
+
+Existem dois cenários possíveis de configurações de relevância:
+
+- **Critérios prioritários:** é a forma de forçar que um ou mais critérios terão prioridade maior entre os demais. Nessa situação não existem pesos, pois todos os produtos que possuírem essa característica serão apresentados primeiro no resultado de busca.
+- **Composição de critérios:** é a forma de distribuir pesos para cada opção, variando de 0 a 10. Aqui, não existe uma ordem entre os critérios, serão os pesos que vão definir a relevância.
+
+![criterios-pt](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/faefb674583084511a114faf0c39cdbd/criterios-pt.png)
+
+As informações aplicadas para compor a relevância são:
+
+- **Desconto:** critério que compara o [Preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) e o [Preço base](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#definicao) cadastrados para determinar se o produto será classificado com desconto.
+- **Data de lançamento:** esse critério atribui um valor automático decrescente (entre 1 e 0) a partir da data de cadastro do produto na loja, considerando um intervalo de 90 dias. Produtos cadastrados hoje teriam o valor 1 e esse valor vai reduzindo a cada dia, até que, do dia 90 em diante, passa a ser 0. Esse valor é multiplicado pelo peso que você cadastrar para o critério **Data de lançamento** para compor a relevância.
+- **Mais vendidos:** números de pedidos do produto nos últimos 90 dias.
+- **Mais vendidos por receita:** lucro total adquirido pelo produto nos últimos 90 dias.
+- **Popularidade:** número de cliques de um produto nos últimos 90 dias.
+- **Promoção:** critério que verifica se há [Audiências de campanhas](https://help.vtex.com/pt/tutorial/overview-2--tutorials_326#audiencia-de-campanhas) ou [Promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N) vinculadas ao item para determinar se o produto será classificado como promoção.
+- **Pontuação do catálogo:** critério de desempate de ordenações baseado no valor do campo __Score__ cadastrado no __Catálogo__. Para essa finalidade de compor relevância, quanto maior o score, maior o peso, ou seja, o comportamento é decrescente: produtos com score mais alto são priorizados. Saiba mais sobre o campo e seu comportamento no guia [Como funciona o campo Score?](https://help.vtex.com/pt/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae).
+- **Variedade de matriz disponível:** A relevância se dá a partir da porcentagem de SKUs disponíveis por produto. Exemplo: Num cenário em que _Produto A_ tem 3 SKus e 3 deles estão disponíveis, e _Produto B_ tem 5 SKUs 2 dele está disponível, o _Produto A_ se sobressai ao _Produto B_ pois a porcentagem de SKUs é maior.
+
+O conjunto de distribuição de pesos e critérios gera uma pontuação para o produto, o que auxilia no seu posicionamento na ordenação do resultado da pesquisa.
+
+<div class="alert alert-warning">
+  <p>Caso deseje utilizar critérios prioritários, recomendamos adicionar apenas um critério neste campo. Adicionar mais critérios compromete a ordenação do resultado de busca, visto que apenas o primeiro critério será considerado.</p>
+</div>
+
+Dessa forma, é possível adequar o comportamento do resultado de busca a uma estratégia específica.
+
+## Exemplo
+
+Uma loja de moda recebe novas coleções com frequência. O lojista opta por priorizar peças de lançamento a produtos promocionais. Ele configura a ferramenta da seguinte forma:
+
+> **Critérios prioritários:**
+> 
+> - Vazio
+> 
+> **Composição de critérios:**
+> 
+> - Popularidade: 7
+> - Data de lançamento: 10
+> - Mais vendidos: 6
+> - Mais vendidos por receita: 6
+> - Promoção: 0
+> - Desconto: 0
+> - Variedade de matriz disponível: 10
+> - Pontuação do catálogo: 0
+
+Caso esse lojista queira que o lançamento seja sempre a prioridade máxima, ele pode fazer as Regras de relevância de duas formas:
+
+> __Forma A:__
+> 
+> **Critérios prioritários:**
+> 
+> - Data de lançamento
+> 
+> **Composição de critérios:**
+> 
+> - Popularidade: 7
+> - Mais vendidos: 6
+> - Mais vendidos por receita: 6
+> - Promoção: 0
+> - Desconto: 0
+> - Variedade de matriz disponível: 10
+> - Pontuação do catálogo: 0
+
+> __Forma B:__
+> 
+> **Critérios prioritários:**
+> 
+> - Vazio
+> 
+> **Composição de critérios:**
+> 
+> - Popularidade: 0
+> - Data de lançamento: 10
+> - Mais vendidos: 0
+> - Mais vendidos por receita: 0
+> - Promoção: 0
+> - Desconto: 0
+> - Variedade de matriz disponível: 0
+> - Pontuação do catálogo: 0
+
+## Configurar Regra de relevância
+
+Para alterar a configuração de relevância, siga os passos abaixo.
+
+1. No Admin VTEX, clique no módulo de **Storefront** ou digite **Storefront** na barra de busca.
+2. Em **Intelligent Search**, clique em **Regras de relevância**.
+3. Escolha o critério cujo peso você deseja alterar.
+4. Clique nos ícones de seta para baixo <i class="fas fa-chevron-down"></i> ou seta para cima <i class="fas fa-chevron-up"></i> para definir o número desejado.
+
+   Caso você queira mudar a posição de um critério de **Composição de critérios** para **Critérios prioritários**, arraste-o pelo ícone <i class="fas fa-grip-vertical"></i> para a área superior, conforme ilustrado na imagem abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso. 
+
+    ![criterios-prioritarios-pt](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/43155e1e110f6ec8eaff5debf9d8a2df/criterios-prioritarios-pt.gif)
+5. Para finalizar, clique em `Salvar`.
diff --git a/docs/tutorials/pt/remarketing.md b/docs/tutorials/pt/remarketing.md
index c5cfb02ff..198d894b7 100644
--- a/docs/tutorials/pt/remarketing.md
+++ b/docs/tutorials/pt/remarketing.md
@@ -23,19 +23,19 @@ Estudos comprovam que o remarketing é 7x mais barato do que impulsionar um anú
 
 Para começar acesse o painel da Suiteshare, escolha a opção \\"_**Atrair > Remarketing\\".**_
 
-![Remarketing 1](https://images.ctfassets.net/alneenqid6w5/66Ky5eCdV4c52T5Dt9dLos/e73774f335c569358e12c9d3c0e86fee/Screenshot_2022-08-30_at_11-24-18_Remarketing.png)
+![Remarketing 1](//images.ctfassets.net/alneenqid6w5/66Ky5eCdV4c52T5Dt9dLos/e73774f335c569358e12c9d3c0e86fee/Screenshot_2022-08-30_at_11-24-18_Remarketing.png)
 
 Na nova página, clique no botão _**“Novo”**_
 
-![Remarketing 2](https://images.ctfassets.net/alneenqid6w5/2ajyBDBc5UaqXlbcjJ4uv5/432c832d0c7a4db385aaa561aca2a6a2/Screenshot_2022-08-30_at_11-24-23_Remarketing.png)
+![Remarketing 2](//images.ctfassets.net/alneenqid6w5/2ajyBDBc5UaqXlbcjJ4uv5/432c832d0c7a4db385aaa561aca2a6a2/Screenshot_2022-08-30_at_11-24-23_Remarketing.png)
 
 Na opção Plataforma, escolha qual é a rede social que você irá utilizar para fazer o remarketing. Depois, clique em \\"_**avançar\\".**_
 
-![Remarketing 3](https://images.ctfassets.net/alneenqid6w5/7irDLNWoiNDJXCETGRhrtv/6a6b5f717c6493d1cd857375927a6b2b/Screenshot_2022-08-30_at_11-24-27_Remarketing.png)
+![Remarketing 3](//images.ctfassets.net/alneenqid6w5/7irDLNWoiNDJXCETGRhrtv/6a6b5f717c6493d1cd857375927a6b2b/Screenshot_2022-08-30_at_11-24-27_Remarketing.png)
 
 Defina as configurações de dados do Pixel.
 
-![Remarketing 4](https://images.ctfassets.net/alneenqid6w5/4MCC8CYfYtyxcImTAngxiX/78549c164908fb3c706cf745d845f99b/Screenshot_2022-08-30_at_11-24-32_Remarketing.png)
+![Remarketing 4](//images.ctfassets.net/alneenqid6w5/4MCC8CYfYtyxcImTAngxiX/78549c164908fb3c706cf745d845f99b/Screenshot_2022-08-30_at_11-24-32_Remarketing.png)
 
 Em **Identificador**, dê um nome ao seu pixel para reconhecê-lo facilmente dentro da plataforma da **Suiteshare**.
 
@@ -49,7 +49,7 @@ Clique no botão _**“avançar”**_.
 
 Informe como o Remarketing irá rastrear os seus clientes. Em Conexão, você deve selecionar o link que os clientes irão clicar para iniciar uma conversa com o seu time de atendimento. O link selecionado será trackeado e, se desejar, poderá selecionar mais de um.
 
-![Remarketing 5](https://images.ctfassets.net/alneenqid6w5/23NHac0nN3Nz8yzktILGn2/52e1a5e94731325df8624c8b44263b90/Screenshot_2022-08-30_at_11-24-37_Remarketing.png)
+![Remarketing 5](//images.ctfassets.net/alneenqid6w5/23NHac0nN3Nz8yzktILGn2/52e1a5e94731325df8624c8b44263b90/Screenshot_2022-08-30_at_11-24-37_Remarketing.png)
 
 Clique em _**“Finalizar”.**_
 
diff --git a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
new file mode 100644
index 000000000..1bbd7befa
--- /dev/null
+++ b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -0,0 +1,91 @@
+---
+title: 'Como remover a mensagem de erro "Request headers must contain only ASCII characters"'
+id: 19psKZvLXrBqqK1bPaTIHG
+status: PUBLISHED
+createdAt: 2024-07-25T16:54:41.663Z
+updatedAt: 2024-07-25T21:25:10.665Z
+publishedAt: 2024-07-25T21:25:10.665Z
+firstPublishedAt: 2024-07-25T21:21:03.197Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: removendo-mensagem-de-erro-request-headers-must-contain-only-ascii
+locale: pt
+legacySlug: removendo-mensagem-de-erro-request-headers-must-contain-only-ascii
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+__Tags/Palavras-chave__: *request headers, ascii, caracteres, especiais, devtools, cabeçalhos, utm, javascript customizado, script.*
+
+A mensagem "__Request headers must contain only ASCII characters__" pode ser exibida no navegador do usuário quando ele está navegando na loja e tenta acessar uma nova página ou realizar uma ação no site, por exemplo, adicionando itens no carrinho de compras.
+
+Este cenário ocorre se a página ou funcionalidade solicitada contém um cookie com caracteres especiais (não-ASCII).
+
+![ascii_1](//images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/1001eedf70586fcfeaf7847eb641ee5a/ascii_1.png)
+
+Segundo as normas do [IETF](https://www.ietf.org/) (Internet Engineering Task Force), instituição responsável por documentar os padrões utilizados na internet, cookies não devem conter caracteres especiais (não-ASCII). Para mais informações sobre os caracteres aceitos em cookies e headers, acesse [IETF - Request for Comments 7230 - Section 3.2.6 - Field Value Components](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6). 
+
+## Soluções
+
+Para remover a mensagem de erro e permitir que a página ou funcionalidade possa ser acessada novamente, é necessário realizar as seguintes ações:
+
+- [Identificar cookie com caracteres especiais](#identificando-cookies-com-caracteres-especiais)
+- [Desabilitar cookie com caracteres especiais](#desabilitando-cookies-com-caracteres-especiais)
+- [Criar script de limpeza do cache](#criando-script-para-remocao-de-cookies)
+
+### Identificando cookies com caracteres especiais
+
+Na página em que a mensagem "__Request headers must contain only ASCII characters__" foi exibida, siga os passos abaixo para identificar qual cookie contém caracteres especiais:
+
+<blockquote><ui>1. Acesse o <a href="https://help.vtex.com/pt/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">DevTools</a> em seu navegador pressionando a tecla <b>F12</b> ou clicando com o botão direito, e escolhendo a opção <b>Inspecionar</b>.</ui>
+
+<blockquote><ui>2. Na barra superior da tela, acesse a aba <b>Rede</b> e ordene as requisições clicando em <b>Status</b>. A informação <b>400</b> no status indica que uma requisição não foi processada corretamente e, dentre os erros possíveis, pode haver cookies incorretos.</ui>  
+
+![ascii 2](//images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/151a66fb0ce501c47e77869a8b4b6de3/ascii_2.png)    
+
+<blockquote><ui>3. Clique sobre uma requisição e depois na aba <b>Visualização</b> para identificar se o erro encontrado é referente à mensagem "<b>Request headers must contain only ASCII characters</b>".</ui>
+
+![ascii 3](//images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/05f662484ece5d1e5876684319b32c62/ascii_3.png)
+
+<blockquote><ui>4. Clique na aba <b>Cabeçalhos</b> e copie os dados do cookie.</ui>  
+
+![ascii 4](//images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/eab317339dfe8c29f82d9987e3f28980/ascii_4.png)    
+
+<blockquote><ui>5. Acesse um <a href="https://pages.cs.wisc.edu/~markm/ascii.html">validador online de caracteres ASCII</a> e insira a informação do cookie. Se um ou mais caracteres especiais forem identificados, os tipos e posições serão exibidas na parte inferior do validador de caracteres.</ui>     
+
+![ascii 5](//images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/917872a195c9cce233a183a4f44b4677/ascii_5.png)  
+
+<blockquote><ui>6. Repita os passos 3 a 5 com todas as requisições com erro para identificar quais delas contêm cookies com caracteres especiais.</ui>      
+
+### Desabilitando cookies com caracteres especiais
+
+Uma vez identificados os cookies contendo caracteres especiais, é necessário verificar a sua origem para que sejam removidos da página. As fontes mais comuns de cookies incorretos são:
+
+- [UTMs](https://help.vtex.com/pt/tutorial/o-que-sao-as-utms-internas-utmi-cp-utmi-pc-e-utmi-p--5Pvo8ufYWs00AUeCCEY68a) criados em sua loja ou em campanhas de publicidade do Google, Facebook, entre outros, que possuam caracteres acentuados. Exemplo de UTM utilizado em data comemorativa: `www.site.com?utm_source=dia-das-mães`.
+- Javascripts customizados, onde implementações de front-end utilizadas para armazenar dados ou outro tipo de função podem conter caracteres especiais.
+- Scripts de clientes parceiros que criam cookies com caracteres especiais.
+
+Assim que localizar a procedência do cookie, realize os procedimentos necessários para removê-lo da página ou solicite ao cliente parceiro que interrompa o envio do cookie para a sua loja.
+
+### Criando script para remoção de cookies 
+
+Ao remover o cookie com caracteres especiais, a página ou funcionalidade deve voltar ao normal e a mensagem "__Request headers must contain only ASCII characters__" não será mais exibida. Entretanto, esse cenário ocorrerá somente para novos usuários da página, ou seja, clientes que ainda não haviam acessado a página durante o tempo em que o cookie incorreto esteva habilitado.
+
+Usuários que acessaram a página ou funcionalidade enquanto o cookie incorreto estava habilitado continuarão a ver a mensagem de erro *"Request headers must contain only ASCII characters"* em seu navegador. Isto ocorre porque o cookie foi armazenado no cache do navegador do usuário.
+
+Para resolver este problema, e permitir que todos os usuários tenham acesso correto na loja, é necessário criar um script na página a ser executado no navegador do usuário (client-side) visando realizar a expiração do cookie incorreto.
+
+O script deve configurar o cookie para expirar em uma data antiga (qualquer período anterior a criação do script). Veja um exemplo abaixo:
+
+`document.cookie = "cookiename= ; expires = Thu, 01 Jan 1970 00:00:00 GMT"`  
+
+Se desejar, você também pode incluir no script as seguintes funções:
+- Interceptar valores de cookies no momento do request da página
+- Realizar a validação de caracteres ASCII nos cookies
+- Expirar automaticamente os cookies contendo caracteres especiais
+- Acionar o recarregamento da página por meio da função `window.location.reload()`  
+
+<div class="alert alert-warning">
+  A remoção dos cookies via script não é uma solução definitiva. Conforme descrito na seção <b>Desabilitando cookies com caracteres especiais</b>, é necessário identificar a origem e interromper o processo de envio de cookies com caracteres especiais.
+</div>  
+
diff --git a/docs/tutorials/pt/reports.md b/docs/tutorials/pt/reports.md
index 56b04004c..9052197f6 100644
--- a/docs/tutorials/pt/reports.md
+++ b/docs/tutorials/pt/reports.md
@@ -31,4 +31,4 @@ Os relatórios disponíveis, são:
 *   [Relatório de SMS e Email](https://help.vtex.com/pt/tutorial/relatorio-de-sms-e-email--7AZmTlojzg1hDmwhDOxCNO)
 *   [Relatório de Serviços](https://help.vtex.com/pt/tutorial/relatorio-de-servicos--7djPWfxtf9qb6hFTOgKDE8)
 
-![relatorio](https://images.ctfassets.net/alneenqid6w5/7y2pg2YdeX5Y4vEjz2TYMl/44110199a50b25b75041edbf9deb79ec/relatorio.png)
+![relatorio](//images.ctfassets.net/alneenqid6w5/7y2pg2YdeX5Y4vEjz2TYMl/44110199a50b25b75041edbf9deb79ec/relatorio.png)
diff --git a/docs/tutorials/pt/requesting-a-new-organization.md b/docs/tutorials/pt/requesting-a-new-organization.md
new file mode 100644
index 000000000..0b50b399c
--- /dev/null
+++ b/docs/tutorials/pt/requesting-a-new-organization.md
@@ -0,0 +1,98 @@
+---
+title: 'Cadastro de nova organização'
+id: 4bTIDPay4fNz39l5XHijAh
+status: PUBLISHED
+createdAt: 2024-06-06T16:21:26.266Z
+updatedAt: 2024-06-07T10:55:22.825Z
+publishedAt: 2024-06-07T10:55:22.825Z
+firstPublishedAt: 2024-06-06T16:27:05.446Z
+contentType: tutorial
+productTeam: B2B
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: cadastro-de-nova-organizacao
+locale: pt
+legacySlug: cadastro-de-nova-organizacao
+subcategory: 6bSdupUQgvuXjBL9Igawxl
+---
+
+Para que uma empresa se cadastre na loja, ela precisa preencher o formulário de Solicitação de uma nova organização, da seguinte forma:
+
+1. Acesse o formulário de cadastro adicionando `/organization-request` no final do endereço de sua loja.
+2. Preencha o formulário de solicitação com os dados da empresa de acordo com as informações descritas neste documento.
+3. Clique em `Enviar`.
+
+Após enviar o cadastro, o time da loja deve revisar a solicitação no Admin VTEX e realizar a aprovação.
+
+## Formulário de solicitação
+
+O formulário de criação de nova organização está dividido nas seguintes seções:
+
+- [Solicitar nova organização](#solicitar-nova-organização)
+- [Usuário que será o admin da organização](#usuário-que-será-o-admin-da-organização)
+- [Centro de custo padrão](#centro-de-custo-padrão)
+
+### Solicitar nova organização
+
+A empresa solicitante fornece dados para o cadastro, incluindo campos customizados.
+
+O formulário inclui os seguintes campos:
+- **Nome da organização:** nome da organização que deseja cadastrar.
+- **Nome fantasia:** nome fantasia utilizado pela empresa.
+
+### Usuário que será o admin da organização
+
+Informações do usuário que será designado como o admin da nova organização.
+
+O formulário inclui os seguintes campos:
+- **Nome:** primeiro nome do usuário.
+- **Sobrenome:** sobrenome do usuário.
+- **Email:** email do usuário.
+
+### Centro de custo padrão
+
+Informações do centro de custo ao qual essa organização será associada.
+
+O formulário inclui os seguintes campos:
+
+- **Nome de centro de custo:** nome do centro de custo inicial, associado à organização.
+
+- **Número de telefone:** número de telefone para contato com a organização.
+
+- **Documento comercial:** você pode usar o CNPJ, o número de identificação fiscal, o número do IVA ou outro documento.
+
+- **Inscrição estadual:** número de registro da empresa.
+
+- **País:** país onde o centro de custo está localizado.
+
+- **CEP:** código postal do endereço do centro de custo.
+
+- **Endereço:** nome da rua onde o centro de custo está localizado.
+
+- **Número:** número do endereço onde o centro de custo está localizado.
+
+- **Complemento e referência:** informação que possa complementar o endereço do centro de custo.
+
+- **Bairro:** nome do bairro onde o centro de custo está localizado.
+
+- **Cidade:** cidade onde o centro de custo está localizado. Isso é preenchido automaticamente com base no CEP informado.
+
+- **Estado:** estado onde o centro de custo está localizado. Isso é preenchido automaticamente com base no CEP informado.
+
+- **Destinatário:** nome da pessoa que receberá os pedidos no endereço informado.
+
+## Verificação de Solicitações Organizacionais
+
+Depois de realizar a solicitação, o time da loja deve revisar o pedido no Admin VTEX, acessando **Aplicativos > B2B Organizations & Cost Centers > Organizações** ou digitando **Organizações** na barra de busca no topo da página.
+
+Nesta página, você pode visualizar uma lista de todas as solicitações de organização feitas em sua loja.
+
+Cada organização pode ter um status de pendente, aprovado ou recusado. As solicitações pendentes são aquelas que ainda precisam de revisão.
+
+Para revisar uma solicitação, você deve seguir os seguintes passos:
+
+- Clique sobre a organização listada, ou clique nos <i class="fas fa-ellipsis-v" aria-hidden="true"></i> para visualizar.
+
+- Escreva um comentário no campo **Adicionar observação**, se necessário.
+
+- Clique em `Aprovar` ou `Recusar`.
+
diff --git a/docs/tutorials/pt/requesting-an-additional-trade-policy.md b/docs/tutorials/pt/requesting-an-additional-trade-policy.md
index 0a455dab0..b2fae9f92 100644
--- a/docs/tutorials/pt/requesting-an-additional-trade-policy.md
+++ b/docs/tutorials/pt/requesting-an-additional-trade-policy.md
@@ -3,8 +3,8 @@ title: 'Contratação de política comercial adicional'
 id: 61vuFOw4yGh6nwSmkLJL1X
 status: PUBLISHED
 createdAt: 2021-12-06T23:25:42.650Z
-updatedAt: 2022-12-08T20:01:23.876Z
-publishedAt: 2022-12-08T20:01:23.876Z
+updatedAt: 2024-06-20T23:00:50.418Z
+publishedAt: 2024-06-20T23:00:50.418Z
 firstPublishedAt: 2021-12-06T23:51:25.043Z
 contentType: tutorial
 productTeam: Channels
@@ -19,7 +19,9 @@ Na VTEX, o conceito de [política comercial](https://help.vtex.com/pt/tutorial/c
 
 É por meio da política comercial que você determina configurações de catálogo, preços, promoções, pagamentos, inventário, logística e segmentação de público em canais de vendas. No entanto, não é necessário [criar uma política comercial](https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) diferente para cada canal, pois uma mesma política comercial pode ser utilizada em múltiplos canais de vendas.
 
-Na VTEX, a contratação de políticas comerciais adicionais é isenta de taxas para integrações com conectores nativos, conectores certificados (parceiros) ou outras lojas VTEX. Saiba mais em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
+Cada cliente na plataforma VTEX é regido por um contrato que define os parâmetros para a contratação de políticas comerciais adicionais. Essas políticas são projetadas para oferecer benefícios específicos, complementando a política comercial nativa incluída automaticamente em cada conta. A VTEX estabelece [#regras-de-cobrança](## Regras de Cobrança) e [#regras-de-isenção](## Regras de Isenção) para algumas políticas comerciais adicionais, promovendo o fortalecimento das integrações dentro do seu ecossistema.
+
+Na VTEX, a contratação de políticas comerciais adicionais é isenta de taxas para integrações com marketplaces certificados ou outras lojas VTEX. Saiba mais em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
 Para adquirir uma política comercial destinada a um canal de vendas fora do ecossistema VTEX, como um marketplace para o qual não exista um [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), por exemplo, há dois fluxos possíveis:
 
@@ -32,7 +34,15 @@ Para contratar uma política comercial adicional destinada à atuação no merca
 
 ## Contratar política comercial para mercado internacional
 
-Para contratar uma política comercial adicional destinada à atuação no mercado internacional, é necessário entrar em contato com o nosso time de Growth Operations em [*Suporte*](https://help.vtex.com/pt/support), escolhendo a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`
+Para contratar uma política comercial adicional destinada à atuação no mercado internacional, é necessário entrar em contato com o nosso time de Growth Operations em [*Suporte*](https://help.vtex.com/pt/support), escolhendo a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
+
+## Regras de Cobrança
+Cada cliente VTEX possui valores estabelecidos em seu contrato para a contratação de políticas comerciais adicionais e essas possuem custo. Ressaltamos que cada conta na VTEX já possui uma [política comercial nativa](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV?&amp;utm_source=autocomplete), que não se enquadra nessas regras de cobrança.
+
+A Política Comercial será passível de cobrança a partir do momento da sua criação mesmo que não haja pedidos sendo realizados. Caso seja totalmente utilizada para integrações diretas com lojas VTEX ou Marketplaces certificados, a bonificação ocorrerá automaticamente na fatura.
+
+## Regras de Isenção
+As regras de isenção das políticas comerciais são um benefício estratégico concedido pela VTEX, visando incentivar o fortalecimento das integrações dentro do nosso ecossistema. Essas regras podem ser atualizadas ao longo do tempo. Hoje a isenção é aplicada para as políticas que possuem pedidos em conector certificado ou integração direta com outras lojas VTEX.
 
 <br></br>
 ### Saiba mais
diff --git a/docs/tutorials/pt/resetting-your-two-factor-authentication-app-configuration.md b/docs/tutorials/pt/resetting-your-two-factor-authentication-app-configuration.md
index 12630929b..19b45b3fb 100644
--- a/docs/tutorials/pt/resetting-your-two-factor-authentication-app-configuration.md
+++ b/docs/tutorials/pt/resetting-your-two-factor-authentication-app-configuration.md
@@ -1,15 +1,15 @@
 ---
-title: 'Redefinindo sua configuração de aplicativo de autenticação de dois fatores'
+title: 'Redefinir sua configuração de aplicativo de autenticação de dois fatores'
 id: 4ftaOCZono1MiQia2hxbTy
 status: PUBLISHED
 createdAt: 2023-02-08T13:55:25.623Z
-updatedAt: 2023-02-08T14:26:33.141Z
-publishedAt: 2023-02-08T14:26:33.141Z
+updatedAt: 2024-03-12T18:52:44.442Z
+publishedAt: 2024-03-12T18:52:44.442Z
 firstPublishedAt: 2023-02-08T14:26:33.141Z
 contentType: tutorial
 productTeam: Identity
 author: 2Gy429C47ie3tL9XUEjeFL
-slug: redefinindo-sua-configuracao-de-aplicativo-de-autenticacao-de-dois-fatores
+slug: redefinir-sua-configuracao-de-aplicativo-de-autenticacao-de-dois-fatores
 locale: pt
 legacySlug: redefinindo-sua-configuracao-de-aplicativo-de-autenticacao-de-dois-fatores
 subcategory: 4sY1T2qdFehvVmC0tL5xW3
@@ -17,27 +17,29 @@ subcategory: 4sY1T2qdFehvVmC0tL5xW3
 
 Se você já [habilitou login por autenticação de dois fatores](https://help.vtex.com/pt/tutorial/enabling-2-factor-authentication-login--4Ae1fcQi12g8u4SkQKCqWQ), mas cometeu algum erro durante a configuração ou perdeu acesso ao seu aplicativo de autenticação de dois fatores, pode ser que você não consiga acessar a sua conta VTEX.
 
+## Retomar acesso ao Admin VTEX
+
 Para retomar o acesso à sua conta, siga estes passos:
-1. Acesse este endereço para ver a página de login da sua conta:
-```
-https://{accountName}.myvtex.com/admin
-```
+
+1. Acesse o Admin VTEX para ver a página de login da sua conta.
 2. Preencha seu endereço de email.
 3. Clique em `Continue`.
 4. Clique em  **Esqueci minha senha**.
 5. Você receberá um código de acesso no seu email. Insira o código recebido no campo indicado.
 6. Insira uma nova senha para a sua conta e clique em `Definir nova senha`.
 
-## Alterando configurações de verificação de dois fatores
+## Alterar configurações de verificação de dois fatores
 
 Uma vez que retomou acesso a sua conta como descrito acima, poderá redefinir o aplicativo de verificação de duas etapas com estes passos:
 
-1. Acesse a página de configuração de verificação em duas etapas da sua conta neste endereço:
-```
-https://{accountName}.myvtex.com/admin/myuser/twostepverification
-```
-2. Clique em **Alterar** na seção **App Google Authenticator**.
-3. Caso não tenha o aplicativo Google Authenticator instalado, o instale no seu dispositivo móvel.
-4. Escaneie o código QR usando o aplicativo Google Authenticator.
-5. Insira o código exibido no aplicativo no campo indicado na página.
+1. Na barra superior do Admin VTEX, clique no avatar do seu perfil, marcado pela inicial do seu email.
+2. Clique em **Configurações do usuário**.
+3. Na seção **Autenticação**, clique na linha **Verificação em duas etapas**.
+4. Selecione **App Google Authenticator**.
+5. Clique em Configurar ou `Alterar`, se já tiver um aplicativo de autenticação configurado.
+6. Caso não tenha o aplicativo __Google Authenticator__ ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)), instale-o no seu dispositivo móvel.
+7. Escaneie o código QR usando o aplicativo Google Authenticator.
+8. Clique em `Próximo`.
+9. Insira o código exibido no aplicativo no campo indicado na página.
+10. Clique em `Confirmar`.
 
diff --git a/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
new file mode 100644
index 000000000..042aba573
--- /dev/null
+++ b/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
@@ -0,0 +1,219 @@
+---
+title: 'Responsabilidades no ecossistema VTEX'
+id: 3vL9aWICDr3WR64DYi1fJ3
+status: PUBLISHED
+createdAt: 2024-01-31T17:08:24.444Z
+updatedAt: 2024-02-16T17:22:16.507Z
+publishedAt: 2024-02-16T17:22:16.507Z
+firstPublishedAt: 2024-01-31T23:11:13.804Z
+contentType: tutorial
+productTeam: Billing
+author: 1malnhMX0vPThsaJaZMYm2
+slug: responsabilidades-no-ecossistema-vtex
+locale: pt
+legacySlug: responsabilidades-no-ecossistema-vtex
+subcategory: 1VvCpaa8NCA6a0MK6W6oWg
+---
+
+O futuro do comércio digital é colaborativo, e parcerias bem sucedidas são indispensáveis para o sucesso da operação do lojista. Durante a operação de uma loja, é comum surgirem dúvidas sobre papéis e responsabilidades de cada player do ecossistema.
+
+Para otimizar a operação da sua loja e garantir a eficiência da comunicação entre o lojista e o suporte da VTEX, esse artigo apresenta as responsabilidades dos principais players envolvidos em uma operação de comércio digital. Confira as responsabilidades em cada cenário a seguir:
+
+* [Integrações back-office (ERP / PIM / WMS)](#integracoes-back-office-erp-pim-wms)
+* [Integrações com provedores de pagamento](#integracoes-com-provedores-de-pagamento)
+* [Agências implementadoras](#agencias-implementadoras)
+* [Integrações com marketplaces](#integracoes-com-marketplaces)
+
+## Integrações back-office (ERP / PIM / WMS)
+
+Durante a configuração inicial da VTEX, caso a sua loja utilize [integrações externas com ERP / PIM / WMS](https://developers.vtex.com/docs/guides/erp-integration-guide),  é de responsabilidade desses sistemas enviar os produtos, preços e inventário da sua loja para a VTEX. Em seguida, é necessário desenvolver um middleware que será responsável por enviar e receber informações da VTEX de acordo com eventos da rotina de sua operação.
+
+Uma vez configurada a integração inicial de produtos, preços e inventário, e desenvolvido o middleware, o fluxo de informações será conforme o diagrama a seguir.
+
+![back-office-pt](//images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/6bc291243b2b38f8a570d404d88e055e/back-office-pt.PNG)
+
+Durante a rotina da operação, as responsabilidades são divididas da seguinte forma:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <tr>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Player</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Responsabilidades</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>ERP / PIM / WMS</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">Envio das seguintes informações para a VTEX via integração:
+        <ul>
+          <li>Alterações no cadastro de produtos</li>
+          <li>Preços</li>
+          <li>Inventário</li>
+          <li>Nota fiscal</li>
+          <li>Informações de rastreio do pedido</li>
+          <li>Alterações no pedido</li>
+          <li>Cancelamentos</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>VTEX</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">Envio das seguintes informações para o ERP, de acordo com o que for configurado pela loja via <a href="https://developers.vtex.com/docs/guides/orders-feed" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Orders Feed</a> ou <a href="https://developers.vtex.com/docs/guides/orders-feed" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Hook</a>:
+        <ul>
+          <li>Notificações de um novo pedido criado.</li>
+          <li>Notificações do andamento do fluxo de um pedido.</li>
+        </td>
+    </tr>
+  </tbody>
+</table>
+
+## Integrações com provedores de pagamento
+
+Para realizar o processamento de pagamentos dos pedidos em uma loja VTEX, os integrantes da infraestrutura de pagamentos dividem as responsabilidades da seguinte forma:
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+    <tr>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Player</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Responsabilidades</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Lojista</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Contratar o serviço de um provedor de pagamento (gateways, adquirentes ou subadquirentes).</li>
+          <li>Contratar o serviço de um provedor de antifraude (opcional).</li>
+          <li>Configurar na loja os provedores de pagamento e, antifraude com os quais possui contrato.</li>
+          <li>Configurar na loja os meios e as condições de pagamento conforme as especificações de cada contrato
+            estabelecido com os provedores de pagamento e antifraude.</li>
+          <li>Realizar manualmente o cancelamento ou estorno de um pagamento, quando este não for executado de forma
+            automática pelo provedor de pagamento ou em casos específicos onde for necessária a intervenção manual do
+            lojista.</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Provedores de pagamento (gateways, adquirentes ou
+          subadquirentes)</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Desenvolver a integração do provedor de pagamento de acordo com as instruções disponíveis em <a
+              href="https://developers.vtex.com/docs/guides/integrating-a-new-payment-provider-on-vtex" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Integrating a
+              new payment provider on VTEX</a>.</li>
+          <li>Obter a certificação <a
+              href="https://developers.vtex.com/docs/guides/payments-integration-pci-dss-compliance" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">PCI-DSS</a> ou
+            desenvolver integração com a VTEX utilizando o <a
+              href="https://developers.vtex.com/docs/guides/payments-integration-secure-proxy" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Secure Proxy</a> para
+            processar transações de pagamento contendo dados sensíveis, como em cartões de crédito, débito e co-branded.
+          </li>
+          <li>Processar transações financeiras de maneira segura e eficiente, permitindo:
+            <ul>
+              <li>Aprovar ou negar os pagamentos, conforme políticas internas.</li>
+              <li>Capturar ou realizar o reembolso de pagamentos.</li>
+              <li>Adquirente: processar pagamentos realizados por cartões de crédito e
+                débito.</li>
+              <li>Subadquirente: intermediar pagamentos entre adquirentes, provedores de antifraude e
+                lojistas.</li>
+              <li>Transmitir as informações de status das transações de pagamento para o gateway da VTEX.</li>
+            </ul>
+          </li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Provedor de antifraude</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Realizar análise de risco sobre atividades fraudulentas em transações com cartões de crédito, débito e
+            co-branded.</li>
+          <li>Transmitir informações das análises para o gateway da VTEX.</li>
+        </ul>
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5" style="min-width: 15rem;"><strong>Gateway VTEX</strong></td>
+      <td class="t-body pa5" style="min-width: 15rem;">
+        <ul>
+          <li>Criar transações de pagamento para novos pedidos.</li>
+          <li>Enviar
+            informações das transações e pedidos para os parceiros responsáveis por processar ou analisar os dados de
+            pagamentos (provedores de pagamento e antifraude).</li>
+          <li>Registrar nos logs da transação todas as ações realizadas pelos demais players no fluxo de uma transação de pagamento, como criação, aprovação, cancelamento, estorno, entre outros.</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Ao detectar qualquer inconsistência ou erro durante a transação de pagamento de um pedido, o lojista deve:
+
+1. Entrar em contato com o(s) responsável(is) pela respectiva transação (provedores de pagamento e antifraude).
+2. Caso o assunto não seja resolvido, abrir um ticket no [Suporte VTEX](https://help.vtex.com/pt/support) informando os dados da ocorrência.
+
+## Agências implementadoras
+
+No caso das soluções de CMS nativas, é comum que o lojista conte com a parceria de uma agência implementadora para customizar a aparência e a experiência do cliente na frente de loja.
+
+A VTEX possui as seguintes possibilidades de CMS nativas: o [Layout](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj#layout) para lojas [Portal CMS Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj), o [Site Editor](https://help.vtex.com/pt/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) para lojas usando o [Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework) e o [Headless CMS](https://help.vtex.com/pt/tutorial/headless-cms-visao-geral--3U5gvhHdQL0jczYH8gjX09) para lojas usando a [FastStore](https://www.faststore.dev/). Além disso, também é possível integrar o seu CMS externo com as APIs da VTEX de forma [headless](https://developers.vtex.com/docs/guides/headless-commerce).
+
+Problemas relacionados a como o conteúdo está aparecendo para o usuário final devem sempre ser tratados inicialmente com o suporte da agência. Alguns exemplos desses problemas são:
+
+* Imagens, títulos ou banners incorretos ou desatualizados.
+* Produtos indisponíveis na frente de loja.
+* Páginas em branco.
+* Menu de categorias incorreto ou desatualizado.
+* Resultados de busca ou de coleções incorretos ou incompletos.
+* Botões de chamada para ação (por exemplo, Comprar, Avise-me, Adicionar ao carrinho) com comportamento não esperado.
+* Preços de produtos ou valores de frete inconsistentes com o que está cadastrado na plataforma.
+
+Se a agência verificar que o problema está em controles, apps ou componentes nativos da VTEX, acione nossos canais de comunicação, conforme a [Política de atendimento do suporte da VTEX](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9), incluindo todas as evidências da investigação já feita pela agência.
+
+## Integrações com marketplaces externos
+
+A VTEX possui uma arquitetura multi-seller nativa que permite que lojas VTEX se tornem marketplaces ou sellers em outras lojas VTEX. Além disso, a plataforma também possui integrações nativas com marketplaces externos para ofertar seus produtos sem necessidade de desenvolvimento. Os marketplaces com integrações nativas podem ser encontrados no guia [Marketplaces e Integrações](https://help.vtex.com/pt/tutorial/marketplaces-e-integracoes--5AcBO1t29nhq7rBHas9b6V).
+
+Ainda assim, podem existir lojas parceiras estratégicas para o seu negócio que operem fora dessa rede colaborativa nativa. Para casos como esse, a VTEX permite o desenvolvimento de [integrações com marketplaces externos](https://developers.vtex.com/docs/guides/external-marketplace-integration-guide), com conectores externos (hubs) responsáveis por fazer a comunicação entre uma loja VTEX e um marketplace externo não-nativo.
+
+Para o suporte de uma operação nesse cenário, é importante que o lojista entenda quais as responsabilidades de cada participante dessa operação, detalhadas a seguir.
+
+<div class="alert alert-warning">
+  <p>As seções a seguir consideram uma loja que já está operando integrada com um marketplace externo via conector externo. Para saber como integrar o seu Catálogo da VTEX com um conector externo pela primeira vez, acesse o guia <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Catalog Integration</a>.</p>
+</div>
+
+### Atualização ou envio de novos produtos e SKUs
+
+Veja a seguir as responsabilidades envolvidas em caso de atualização ou envio de novos produtos e SKUs para o marketplace externo:
+
+| **Player** | **Responsabilidades** |
+|---|---|
+| **VTEX** | Enviar uma notificação de novo produto ou SKU criado ou atualizado para o endpoint de afiliado fornecido pelo hub e cadastrado na plataforma VTEX. |
+| **Conector parceiro (hub de integração)** | Processar a notificação e enviar o produto ou SKU atualizado para o marketplace. <br /><br />Esse processamento engloba diversas etapas, incluindo verificar se esse SKU já existe no marketplace e registrar como um novo se necessário, validar se o produto está ativo e associado à política comercial do marketplace, fazer uma simulação de pedido para conferir preço e inventário do SKU atualizados, entre outras. |
+| **Marketplace externo não-nativo** | Fornecer os endpoints necessários para o hub enviar o SKU atualizado, registrar o SKU recebido e responder o status para o conector. |
+
+### Atualização ou criação de novos pedidos
+
+Confira as responsabilidades envolvidas na atualização ou criação de pedidos de acordo com o fluxo do pedido.
+
+1. O **marketplace** disponibiliza os produtos e o checkout para que o pedido seja realizado e notifica o conector sobre um novo pedido criado.
+2. O **conector** é responsável por criar o pedido na VTEX.
+3. A VTEX responde ao conector o status de criação do pedido, que pode ser sucesso ou falha. Nesta etapa, se houver falha na criação do pedido na VTEX, ou se pedido for criado com o status **Cancelado**, é necessário contatar o suporte do conector.
+4. Uma vez que o pedido é criado na VTEX, a responsabilidade pela atualização do seu status no OMS depende da etapa do processo:
+
+   * Se o pedido está preparando entrega ou faturado, por exemplo, é responsabilidade do **ERP** notificar a VTEX.
+   * Se o pedido foi cancelado no marketplace, a responsabilidade é do **conector**.
+
+Para mais informações sobre quem é responsável por cada etapa do fluxo de um pedido num cenário de marketplace externo, veja [Fluxo e status de pedidos - Fluxo do Seller](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#fluxo-do-seller).
+
+#### Status do pedido 
+
+Para entender qual suporte deve ser acionado caso haja algum problema na atualização do status do pedido, é preciso seguir o passo a passo:
+
+1. No Admin VTEX, acesse **Pedidos > Todos os Pedidos**.
+2. Clique no pedido desejado para acessar a [página de detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl).
+3. Na seção **Histórico do pedido**, clique em `Ver interações` (botão ilustrado a seguir), e verifique se há alguma mensagem de erro. 
+
+![ver-interacoes-pt](//images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/6d50ebab0fb9de03850bc219ea7fbce8/ver-interacoes-pt.png)
+
+Caso a mensagem de erro não seja autossuficiente, o lojista pode acionar nossos canais de comunicação, conforme a [Política de atendimento do suporte da VTEX](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9). Recomendamos incluir a evidência da tela de interações e o ID do pedido, para que o time de especialistas ajude a identificar a origem do problema.
diff --git a/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md b/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md
new file mode 100644
index 000000000..6c20d9003
--- /dev/null
+++ b/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md
@@ -0,0 +1,59 @@
+---
+title: 'Restringir acesso público a campos do Master Data'
+id: 5eu1N1h4Vqe8GY1yHXUsvz
+status: PUBLISHED
+createdAt: 2024-06-25T12:54:28.672Z
+updatedAt: 2024-06-25T13:28:43.112Z
+publishedAt: 2024-06-25T13:28:43.112Z
+firstPublishedAt: 2024-06-25T13:28:43.112Z
+contentType: tutorial
+productTeam: Master Data
+author: 1malnhMX0vPThsaJaZMYm2
+slug: restringir-acesso-publico-a-campos-do-master-data
+locale: pt
+legacySlug: restringir-acesso-publico-a-campos-do-master-data
+subcategory: WpbGhubuRZaNZilJSXnqu
+---
+
+No [Master Data v1](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw), é possível [criar entidades de dados](https://help.vtex.com/pt/tutorial/data-entity--tutorials_1265#criar-entidade-de-dados) com diferentes restrições de acesso para cada campo:
+
+* Permitir a leitura sem credencial
+* Permitir editar sem credencial
+* Permitir filtrar sem credencial
+
+Dependendo dos dados armazenados, o acesso público sem autenticação pode representar um risco para o seu negócio. Para impor a autenticação e restringir o acesso público aos campos que contêm dados confidenciais, siga as instruções abaixo.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
+2. No Master Data, clique em **Aplicações**.
+3. Clique na engrenagem <i class="fas fa-cog"></i> ao lado de **Profile System**:
+
+   ![1-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/8ef8b96790388f461fa7c987039c2d25/1-master-data-confidential-data-pt.png)
+
+4. Em **Configurações**, clique em **Estrutura de dados**.
+
+   ![2-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/524173ebe8a58a71711ac518b571218b/2-master-data-confidential-data-pt.png)
+5. Clique na aba **Entidades de dados**.
+6. Na linha da entidade de dados, clique no botão de edição <i class="fas fa-edit"></i>.
+
+   ![3-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/8a5d88237d95243515b0528ff1b7a4b0/3-master-data-confidential-data-pt.png)
+7. Na linha do campo que contém um dado confidencial, clique na engrenagem <i class="fas fa-cog"></i>.
+
+   ![4-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/7c1f6afa0c6d7cda830b03b1532d22ed/4-master-data-confidential-data-pt.png)
+8. Desmarque as opções a seguir:
+
+   * **Permitir a leitura sem credencial**
+   * **Permitir editar sem credencial**
+   * **Permitir filtrar sem credencial**
+
+   ![5-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/caf25f3c588303febe067d9a219dd9f2/5-master-data-confidential-data-pt.png)
+
+9. Clique em `Salvar`.
+10. Na linha da entidade de dados alterada, clique no botão de publicação <i class="fas fa-save"></i> para que as configurações salvas sejam publicadas.
+11. Clique em `OK`.
+
+## Permissões necessárias
+
+Após seguir as instruções anteriores, é obrigatório ter um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) com as [permissões](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) necessárias para acessar as informações:
+
+* Pelo menos um recurso da categoria **Generic resources** no produto **Master Data**: **READONLY_USER_CRM**, **POWER_USER_CRM**, **NOREMOVE_USER_CRM** ou **ADMIN_CRM**.
+* Pelo menos um recurso da categoria **Dynamic storage generic resources** no produto **Dynamic Storage**:** READONLY_USER_DS**, **NOREMOVE_USER_DS**, **POWER_USER_DS** ou **ADMIN_DS**.
diff --git a/docs/tutorials/pt/risk-assessment.md b/docs/tutorials/pt/risk-assessment.md
new file mode 100644
index 000000000..5f98530f3
--- /dev/null
+++ b/docs/tutorials/pt/risk-assessment.md
@@ -0,0 +1,467 @@
+---
+title: 'Risk Assessment'
+id: 4K97IpqkpCpDYsZOSxtfkX
+status: PUBLISHED
+createdAt: 2022-05-26T13:08:53.479Z
+updatedAt: 2024-05-28T16:54:14.044Z
+publishedAt: 2024-05-28T16:54:14.044Z
+firstPublishedAt: 2022-05-26T13:17:48.374Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: risk-assessment
+locale: pt
+legacySlug: o-processo-de-risk-assessment
+subcategory: vONCJSxwN5qZiElOEtKkH
+---
+
+O processo de Risk Assessment é fundamental para o bom funcionamento de um programa de gestão de risco de fornecedores. O procedimento é composto de questionários de avaliação de risco de terceiros, projetados para ajudar uma organização a identificar potenciais riscos entre seus fornecedores e parceiros terceirizados.
+
+Os questionários são direcionados à VTEX a fim de:
+
+* Avaliar se a VTEX atende os requisitos de segurança estabelecidos pelo cliente.
+* Conhecer detalhes técnicos sobre a arquitetura de segurança.
+* Aferir potenciais riscos da plataforma.
+
+Para apoiar as avaliações de risco de seus clientes, a VTEX disponibiliza páginas de FAQ com as principais perguntas e respostas relacionadas à estrutura e à segurança da plataforma.
+
+Clique nos itens a seguir para acessar a FAQ referente a cada assunto:
+
+* [Políticas e conformidade](#politicas-e-conformidade)
+* [Educação e conscientização sobre segurança](#educacao-e-conscientizacao-sobre-seguranca)
+* [Gestão de ativos](#gestao-de-ativos)
+* [Privacidade e dados](#privacidade-e-dados)
+* [Criptografia](#criptografia)
+* [Controle de acesso, identificação e autenticação](#controle-de-acesso-identificacao-e-autenticacao)
+* [Segurança da plataforma](#seguranca-da-plataforma)
+* [Auditoria de logs](#auditoria-de-logs)
+* [Desenvolvimento seguro](#desenvolvimento-seguro)
+* [Segurança física e data centers](#seguranca-fisica-e-data-centers)
+* [Gerenciamento de vulnerabilidades](#gerenciamento-de-vulnerabilidades)
+* [Resposta e mitigação a incidentes](#resposta-e-mitigacao-a-incidentes)
+* [Disaster Recovery e continuidade de negócios](#disaster-recovery-e-continuidade-de-negocios)
+
+Algumas informações sobre segurança são restritas a usuários logados no Admin VTEX, por isso não estão presentes no VTEX Help Center. Para acessá-las, insira abaixo seu nome de conta VTEX:
+
+<iframe src="https://help.vtex.com/insertaccountname?id=7AmPOGXykmE9SYyYDzdAZ4" title="Insira seu nome de conta e clique no botão." frameBorder="0" width="400" height="50"></iframe>
+
+<div class="alert alert-warning">
+  Se está tendo dificuldades para acessar o conteúdo dos FAQs, tente instalar a versão mais recente do aplicativo <code>vtex.admin-docs</code> usando a <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">CLI da VTEX</a> e repetir o processo.
+</div>
+
+## FAQ - Segurança
+
+### Políticas e conformidade
+
+#### A VTEX possui uma política de Segurança da Informação? Se sim, com qual periodicidade ela é revisada? A política foi distribuída e comunicada para toda companhia?
+
+A VTEX adota uma abordagem rigorosa em relação à Segurança da Informação, revisando anualmente sua política de Segurança da Informação por meio do processo de gestão de documentos. Todos os colaboradores formalmente aceitam essa política, a qual é comunicada em toda a empresa por meio de nossos canais internos. Alinhada à norma ISO IEC 27001 e a frameworks reconhecidos pelo mercado, a política segue as melhores práticas de segurança, cumprindo também com as leis de proteção de dados e outras obrigações pertinentes à VTEX.
+
+#### Os controles de Segurança da Informação da VTEX são auditados por empresas terceiras? Quais certificações que a VTEX possui?
+
+A VTEX, comprometida com a transparência e a excelência em suas práticas, submete regularmente seus controles de Segurança da Informação a auditorias conduzidas por profissionais independentes. Esses auditores atuam de forma imparcial e objetiva, garantindo uma avaliação rigorosa e isenta das medidas implementadas pela VTEX.
+
+A importância dessa prática reside na validação externa das políticas e procedimentos, assegurando que estão alinhados com as normas, frameworks e melhores práticas de segurança. A auditoria por profissionais independentes fortalece a confiança dos clientes, parceiros e demais partes interessadas, demonstrando o compromisso da VTEX em manter padrões elevados de Segurança da Informação. Atualmente possuímos as seguintes certificações:
+
+* SOC 1 - Tipo 2: relatório que abrange os controles internos sobre os sistemas de relatórios financeiros.
+* SOC 2 - Tipo 2: relatório cobrindo Segurança, Disponibilidade, Integridade, Confidencialidade e Privacidade.
+* PCI DSS: validação de controles em torno dos dados do titular do cartão para reduzir a fraude de cartão de crédito.
+
+Todas essas certificações estão disponíveis na página [Compliance](https://vtex.com/br-pt/compliance) no [VTEX Trust Hub](https://vtex.com/br-pt/trust/).
+
+Além disso, a VTEX, como uma empresa de capital aberto, implementa os controles exigidos pela lei SOX (Sarbanes-Oxley).
+
+#### Quem é responsável por gerenciar o programa de Segurança da Informação da VTEX?
+
+Em nossa organização, contamos com lideranças executivas encarregadas do programa de Segurança da Informação, além de um Data Protection Officer (DPO) encarregado de coordenar o programa de Privacidade. As equipes, compostas por engenheiros e analistas altamente especializados em Segurança da Informação, estão estruturadas de maneira dedicada para oferecer suporte aos principais processos de segurança.
+
+#### As políticas de Segurança da Informação são analisadas criticamente e mantidas para fazer cumprir as obrigações de segurança cibernética legais, regulamentares ou contratuais aplicáveis? Com qual frequência elas são revisadas?
+
+Nossas políticas e procedimentos de Segurança da Informação foram elaborados com base nas melhores práticas e diretrizes de mercado, como a norma ISO IEC 27001. Realizamos a gestão desses instrumentos através de ferramentas internas da VTEX. Eles são revisados anualmente por profissionais especialistas em segurança e lideranças.
+
+#### Como é gerenciado o calendário de auditorias e certificações da VTEX?
+
+A VTEX conta com uma equipe especializada em segurança dedicada à gestão de certificações, garantindo a conformidade com todos os requisitos necessários. Esta equipe se empenha em assegurar que todas as certificações aplicáveis sejam atendidas de maneira eficaz, sendo renovadas sempre que necessário, reforçando o compromisso da empresa com os mais elevados padrões de segurança.
+
+#### Quantas pessoas compõem a equipe de Segurança da Informação?
+
+A VTEX conta com um time composto por gerentes, engenheiros e analistas altamente especializados em Segurança da Informação. Nossa equipe é organizada de forma estruturada e dedicada para oferecer suporte aos principais processos de segurança. Operando em regime de prontidão 24x7 e com presença em diferentes fusos horários, a equipe de segurança assegura uma cobertura contínua que vai além do horário comercial.
+
+Além da equipe de Segurança da Informação, outros times da VTEX também contam com pessoas dedicadas que atuam nos processos de segurança, demonstrando o comprometimento global da organização com a integridade e proteção dos dados.
+
+#### As políticas e controles de Segurança da Informação são aplicados contratualmente aos provedores terceiros?
+
+Todos os fornecedores e parceiros envolvidos no processamento das nossas informações, ou de nossos clientes, são submetidos a acordos contratuais que incluem cláusulas de segurança. Esses contratos estabelecem diretrizes e requisitos específicos para garantir a proteção adequada dos dados, assegurando o comprometimento de todas as partes com elevados padrões de Segurança da Informação.
+
+Saiba mais sobre nossos [provedores terceiros de infraestrutura](https://vtex.com/br-pt/subprocessors/).
+
+### Educação e conscientização sobre segurança
+
+#### A VTEX possui processos e procedimentos para a conscientização em segurança da informação?
+
+A VTEX possui diversos treinamentos recorrentes de segurança da informação:
+
+* Onboarding de segurança para todos os novos funcionários, abrangendo tópicos como a estrutura do time de segurança, canais de comunicação, documentos normativos, políticas, ferramentas homologadas e obrigações externas; boas práticas de segurança, senha segura, engenharia social e gestão de documentos.
+* Treinamento mensal sobre boas práticas de segurança e dicas de práticas diárias. 
+* Reuniões globais mensais sobre tópicos emergentes de segurança da informação, informações e atualizações sobre controles de segurança e boas práticas de segurança da informação.
+* Phishings simulados enviados periodicamente, ferramenta para reporte de phishing e treinamento para todos que clicam nos testes.
+* Iniciativas presenciais durante eventos sobre boas práticas de segurança, controles físicos e técnicos.
+
+Há também um documento normativo específico para a área de conscientização e treinamento em segurança da informação, que descreve as iniciativas acima descritas.
+
+#### Existem treinamentos técnicos para o time de Segurança?
+
+São realizados treinamentos internos relacionados a práticas de desenvolvimento seguro, controles de segurança da informação, resposta a incidentes e outros treinamentos que abordam contexto técnico de segurança e privacidade. 
+
+#### A VTEX adota um programa de conscientização focada na mitigação e proteção contra malwares? Os funcionários são instruídos sobre esse tema?
+
+A empresa possui programas internos para aumentar a conscientização sobre malware e as possíveis consequências dele. Todos os funcionários da VTEX são informados regularmente por meio de comunicações internas e treinamento sobre os riscos associados ao malware, como o malware pode se instalar em um dispositivo e os indicativos de que a máquina foi infectada por malware. Em caso de suspeita de malware, os funcionários são instruídos a entrar em contato com a equipe responsável.
+
+Adicionalmente, a proteção contra malware é feita com monitoramento constante por meio de nossas ferramentas de segurança.
+
+O malware em ambientes de produção é monitorado ativamente pelo software anti-malware instalado nas instâncias. Caso um malware seja detectado, a instância afetada é encerrada para que os processos de escalonamento automático criem uma instância limpa do zero.
+
+### Gestão de ativos
+
+#### Como a VTEX gerencia os ativos mais críticos da sua organização?
+
+Os ativos são gerenciados centralmente por meio de um sistema de gerenciamento de inventário que armazena e rastreia o proprietário, a localização, o status, a manutenção e as informações descritivas dos ativos de propriedade da AWS. Após a aquisição, os ativos são verificados e rastreados, e os ativos em manutenção são verificados e monitorados quanto à propriedade, status e resolução.
+
+#### Como a VTEX inventaria os ativos dentro da companhia?
+
+A VTEX opera 100% na nuvem e é a maior parceira da AWS na América Latina. Assim, não há necessidade de inventário de ativos físicos. Para inventário de software, usamos o inventário do AWS Systems Manager, que fornece visibilidade em nosso ambiente de computação da AWS. No cenário corporativo, utilizamos uma solução dedicada para realizar a gestão dos endpoints e aplicar regras de segurança.
+
+#### Como a VTEX realiza a destruição e descarte dos seus ativos (mídias removíveis, pen drives e etc)?
+
+Os dispositivos de armazenamento de mídia usados para armazenar dados do cliente são classificados como Críticos e tratados adequadamente, como de alto impacto, ao longo de seus ciclos de vida. Existem padrões rigorosos sobre como instalar, fazer manutenção e, eventualmente, destruir os dispositivos quando eles não forem mais úteis. Quando um dispositivo de armazenamento chega ao fim de sua vida útil, ele é desativado usando técnicas detalhadas no NIST 800-88.
+
+### Privacidade e dados
+
+#### A companhia possui uma Política de Privacidade e Proteção de Dados? Se sim, com qual periodicidade ela é revisada? A política foi distribuída e comunicada para toda companhia?
+
+Sim, a VTEX possui Políticas de Privacidade e Proteção de Dados, que são revisadas anualmente. As Políticas de Privacidade Interna e Externa foram distribuídas e comunicadas para toda a companhia através do nosso canal de anúncios internos. A Política de Privacidade Interna é mantida na nossa ferramenta de documentos corporativos internos, para possibilitar o livre acesso pelos colaboradores. A [Política de Privacidade Externa](https://vtex.com/br-pt/privacy-and-agreements/external-notice/) pode ser acessada no website da VTEX.
+
+#### A organização possui um DPO (Data Protection Officer) ou Encarregado de Proteção de Dados, com autoridade, missão, responsabilidade e recursos para coordenar, desenvolver e implementar os requisitos de privacidade aplicáveis e gerenciar os riscos de privacidade por meio do programa de privacidade?
+
+Sim, a VTEX possui uma DPO responsável por coordenar o programa de privacidade: Angela Fonseca ([dpo@vtex.com.br](mailto:dpo@vtex.com.br)).
+
+#### Que tipo de dados pessoais a VTEX trata em nome dos seus clientes?
+
+Como operadora de dados, a VTEX trata dados pessoais de compradores somente quando necessário, em conformidade com os requisitos de cada módulo da plataforma para realizar operações de ecommerce. Confira a seguir a lista de dados pessoais que podem ser tratados pela VTEX:
+
+* Nome
+* Email
+* Endereço IP
+* Informações de navegação ([cookies](https://vtex.com/br-pt/privacy-and-agreements/vtex-platform-cookies-information/))
+* Informações do carrinho
+* Informações e histórico do pedido
+* Endereço de entrega
+* Número de identidade (quando exigido pelo país em que a loja opera)
+* Histórico do cartão-presente
+* Carrinho não utilizado
+* Conversas do [Conversation Tracker](https://help.vtex.com/pt/tutorial/conversation-tracker)
+* Senhas de sessões (criptografadas)
+* Tokens gerados
+
+A lista de dados acima está descrita no [Data Processing Addendum (DPA)](https://help.vtex.com/pt/tracks/data-and-privacy--4Lc0i0an0DgnEtB0AUwlcq/5f8hTEw3xOALgqzus9VXKd#data-processing-addendum-dpa).
+
+#### Como a VTEX cumpre a LGPD (Lei Geral de Proteção de Dados) e o GDPR (_General Data Protection Regulation_)?
+
+A VTEX está comprometida a cumprir todos os regulamentos de proteção de dados aplicáveis, incluindo a LGPD e o GDPR. Você pode ler mais sobre nossas políticas, contratos e compromisso com o compliance em proteção de dados em nosso website, na página [Privacidade & Contratos](https://vtex.com/br-pt/privacy-and-agreements/). 
+
+Confira nosso [Data Processing Addendum (DPA)](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/), ou Adendo ao Tratamento de Dados Pessoais para compreender como tratamos os dados pessoais na VTEX.
+
+#### Quais direitos dos titulares são garantidos pela plataforma VTEX?
+
+A VTEX atua como operadora de dados em relação aos dados dos consumidores finais tratados por seus clientes (lojistas). Por isso, a VTEX não poderá responder às solicitações dos titulares diretamente. Caso receba alguma solicitação de titular (ou de seus representantes), a VTEX comunicará ao lojista, conforme indicado pelo titular.
+
+Como controlador, o lojista define as bases legais e finalidades de tratamento de dados. Caso você não possa atender à solicitação por razões técnicas, contratuais, ou legais, é possível justificar o motivo da recusa.
+
+Se você deseja assistência a respeito do exercício dos direitos dos titulares de algum dos consumidores da sua loja, acesse [Exclusão de dados de clientes](https://help.vtex.com/pt/tutorial/exclusao-de-dados-de-clientes--1R9Fn7A06Ifj4R9YD4JTKU). 
+
+#### A VTEX possui uma política de Classificação da Informação?
+
+A VTEX estabeleceu uma política de classificação de informações com o objetivo de guiar seus colaboradores sobre a correta categorização das informações, de acordo com seu nível de criticidade. Nossa política visa garantir a segurança, integridade e confidencialidade dos dados da VTEX, além de ajudar a gerenciar o acesso a essas informações de maneira apropriada.
+
+Nossa política estabelece os níveis de classificação em público, interno e confidencial, e, especifica as medidas de segurança associadas a cada categoria.
+
+#### Como os dados podem entrar em contato com terceiros, trabalhos terceirizados ou subcontratados e como essas interações são protegidas e monitoradas?
+
+A infraestrutura da VTEX é inteiramente dependente de provedores terceirizados, assegurando que os dados dos locatários permaneçam inacessíveis para esses parceiros externos. Confira a lista completa de nossos subprocessadores em [Subprocessadores - VTEX](https://vtex.com/br-pt/privacy-and-agreements/subprocessors).
+
+A segurança do processamento e envio de dados a terceiros é uma prioridade fundamental para a VTEX. Empregamos uma abordagem abrangente que combina tecnologia avançada, rigorosos processos de segurança e treinamento contínuo de nossa equipe. Utilizamos medidas tecnológicas, como criptografia robusta, para proteger os dados durante o envio e processamento. Além disso, implementamos processos rigorosos de segurança da informação e controles de acesso para garantir que apenas as pessoas autorizadas tenham acesso aos dados. Investimos constantemente em atualizações e melhorias para garantir a proteção eficaz dos dados que são compartilhados com parceiros terceirizados, entre outras medidas. Você pode conhecer nossas medidas de segurança em vigor em [Práticas de Segurança](https://vtex.com/br-pt/security/security-practices/).
+
+#### Você pode garantir que os dados não migrem além de uma região geográfica definida?
+
+Atualmente, a maioria dos dados armazenados pela VTEX são baseados na AWS us-east-1. Isso significa que o cliente não pode definir a região geográfica, mas também significa que, a menos que autorizado pelo cliente, a VTEX não migrará os dados para fora dessa região.
+
+#### A VTEX utiliza a anonimização dos dados?
+
+Em relação à anonimização de dados, a VTEX vem utilizando a tokenização como mecanismo para substituir qualquer dado sensível por outro valor. Basicamente, os dados originais são completamente irrecuperáveis.
+
+#### Quais portas e protocolos a VTEX utiliza para transferir dados? Como cada um é protegido?
+
+A VTEX não transfere dados via servidores, portanto, todos os nossos dados são transferidos via HTTPS via porta 443. Todos os dados sensíveis são armazenados com criptografia. Os dados em trânsito são criptografados com TLS 1.2 e os dados em repouso com algoritmo AES-256 ou RSA com chaves de pelo menos 2048 bits.
+
+### Criptografia
+
+#### Quais são as opções de criptografia em trânsito e em repouso?
+
+A VTEX possui padrões de criptografia definidos para todos os seus clientes tanto para dados em repouso quanto para dados em trânsito. Para atender aos requisitos de certificações como PCI e SOC 2, a VTEX mantém os dados dos usuários sempre criptografados, tanto em armazenamento quanto em trânsito.
+
+Os dados em trânsito são protegidos pelo padrão de segurança TLS 1.2, e conexões utilizando métodos de criptografia mais antigos e inseguros são negadas.
+
+Ao trabalhar com armazenamento ou dados em repouso, a VTEX pode usar um dos seguintes algoritmos para suportar aplicativos que precisam criptografar dados:
+
+* Criptografia bidirecional
+    * RSA com chaves de 2048 bits ou superiores
+    * AES-256
+* Criptografia unidirecional
+    * PBKDF2 baseada em SHA-256
+
+Todos os sistemas relevantes realizam backups automáticos, sendo que a frequência padrão é diária, mas pode ser ajustada conforme necessário para garantir a integridade e disponibilidade dos dados. 
+
+#### As chaves de criptografia são armazenadas em lugar seguro?
+
+Para garantir um alto nível de segurança, as chaves de criptografia são fornecidas pelo serviço da AWS, reconhecido por sua confiabilidade e robustez em termos de segurança. Além disso, as chaves de acesso são armazenadas em um ambiente segregado, com proteção criptográfica adequada, garantindo a confidencialidade e a integridade das informações.
+
+Um exemplo disso é o tratamento das senhas de login: antes de serem armazenadas, as senhas passam por um processo de hash utilizando o algoritmo PBKDF2 baseado em SHA-256. Nesse processo, apenas o valor resultante do hash é armazenado, garantindo que as senhas originais permaneçam seguras e não sejam acessíveis diretamente. Essas medidas adicionais de segurança garantem a proteção dos dados sensíveis e a tranquilidade dos usuários quanto à confidencialidade de suas informações.
+
+### Controle de acesso, identificação e autenticação
+
+#### A VTEX possui uma política de Gestão de Acessos Lógicos? Descreva de modo geral como funcionam seus processos relacionados a gestão de acesso.
+
+A VTEX realiza a gestão de acesso lógico de maneira eficiente, garantindo o controle adequado e monitoramento das permissões de acesso aos sistemas e dados.
+
+Nossas práticas asseguram a conformidade com políticas de segurança, implementando medidas como o Princípio do Mínimo Privilégio e Segregação de Funções para garantir que os usuários tenham acesso somente às informações necessárias para desempenhar suas funções específicas, baseando-se em necessidades legítimas.
+
+Nosso procedimento de revogação de acessos é acionado de maneira imediata, com envolvimento direto do time de Segurança da VTEX.
+
+Para o ambiente corporativo, adotamos uma política de Gestão de Acesso desenvolvida conforme as melhores práticas de mercado, incluindo a implementação de duplo fator de autenticação para acessar nossos servidores e a utilização de VPN, quando necessário.
+
+#### No ambiente corporativo, como é operacionalizada a concessão de acessos aos sistemas internos da VTEX?
+
+No ambiente corporativo, o processo de Gestão de Acessos, desde a concessão até a revogação, é conduzido por uma equipe centralizada encarregada de estabelecer as métricas e executar procedimentos de concessão de acesso. 
+
+Dentro dessa equipe, existem grupos específicos que são designados para gerenciar sistemas críticos da empresa. Dessa forma, quando um colaborador necessita de acesso, ele inicia o processo através do nosso canal de atendimento digital, centralizado e automatizado.
+
+O pedido então passa por uma avaliação, para garantir que o colaborador em questão deve e necessita receber o acesso solicitado. O fluxo passa por diversas etapas de autenticação, validação e aprovação formal da solicitação antes de ser concedido.
+
+#### A VTEX limita o acesso de acordo com o princípio do privilégio mínimo?
+
+A VTEX restringe o acesso de acordo com o princípio do privilégio mínimo. Isso significa que os usuários recebem [permissões de acesso](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) apenas ao estritamente necessário para desempenhar suas funções, minimizando o risco de exposição indevida de informações sensíveis e fortalecendo a segurança dos sistemas e dados.
+
+#### Como é a arquitetura de autenticação e gestão de identidade disponível na plataforma da VTEX?
+
+A plataforma VTEX possui uma solução de identidade pronta para uso, chamada VTEX ID. Também oferecemos suporte à integração de [provedores externos de identidade para SSO](https://developers.vtex.com/docs/guides/login-integration-guide) no Admin e no site da loja.
+
+O Admin conta com [SAML 2.0](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) como protocolo de autenticação, onde clientes da VTEX podem integrar um provedor de identidade existente usando esse padrão. O site da loja pode integrar com provedores externos de identidade pelo protocolo [OAuth 2.0](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2).
+
+Temos um processo para [gerenciamento de acessos](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc), o que inclui acesso aos ambientes produtivos e ambientes relacionados.
+
+Disponibilizamos links com conteúdos técnicos mais profundos sobre nossos controles de autenticação:
+
+* [Login integration guide](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide)
+* [SAML 2 integration](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide-admin-saml2)
+* [OAuth 2.0 integration](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide-webstore-oauth2)
+
+#### Quais os recursos de segurança na autenticação e gerenciamento de identidade relevantes estão disponíveis na plataforma? Por exemplo, complexidade de senha, reutilização de senha, tempo limite de sessão, bloqueio de conta, redefinição de senha e multifator de autenticação.
+
+As senhas sob VTEX ID têm os seguintes requisitos:
+
+* Comprimento mínimo de 8 + Token MFA de 6 dígitos.
+* Mínimo de 1 caractere maiúsculo.
+* Mínimo de 1 dígito.
+* Mínimo de 1 caractere especial.
+* Não é possível repetir as últimas 4 senhas usadas.
+
+Os lojistas podem optar por [aplicar a expiração de senha](https://help.vtex.com/pt/tutorial/autenticacao--21CkKHLKP1o41lUpGhuRUs#aplicar-expiracao-de-senha) após um período específico para usuários do Admin, que pode ser 15, 30 ou 90 dias.
+
+Os lojistas também podem optar por integrar um provedor de identidade externo, permitindo que definam suas próprias políticas de senha de forma personalizada. Confira [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) para mais informações.
+
+No caso de bloqueios de conta devido a várias tentativas com senha incorreta (medida de segurança), usuários legítimos podem ainda realizar login por meio de outros métodos, como receber um token via e-mail ou usar um [login social integrado](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513) (Google ou Facebook), evitando assim possíveis explorações por força bruta de senhas fracas.
+
+#### A plataforma da VTEX oferece logon único Single Sign-On (SSO)?
+
+Oferecemos como uma camada adicional de segurança o recurso de Single Sign On (SSO), disponível tanto no Admin VTEX (ambiente administrativo) da loja quanto na autenticação dos clientes na própria loja.
+
+O Security Assertion Markup Language (SAML) é adotado como padrão para a troca de dados de autenticação e autorização entre diferentes domínios. O SAML 2.0, um protocolo baseado em XML, facilita o SSO em navegadores web. Este protocolo utiliza tokens seguros, assinados digitalmente e mensagens criptografadas para a transmissão de dados entre partes confiáveis.
+
+Para informações mais detalhadas, consulte o [guia de integração do SAML 2](https://developers.vtex.com/vtex-rest-api/docs/login-integration-guide-admin-saml2).
+
+#### A plataforma possui a identificação, controle de acesso e a segregação dos dados dos clientes por meio de controles físicos ou lógicos?
+
+A VTEX mantém a segregação dos dados dos clientes por meio de controles lógicos robustos. Todas as nossas aplicações são multilocatárias (_multitenant_) e exigem identificar a loja de origem em cada requisição, registrando todas as informações específicas de cada loja com o seu identificador correspondente. Dessa forma, toda a nossa infraestrutura de servidores é compartilhada entre todos os clientes. 
+
+É importante ressaltar que não há nenhum método integrado de acesso; cada cliente tem acesso exclusivo às suas próprias informações, garantindo a segurança e privacidade dos dados.
+
+Essa abordagem nos permite agilidade nas melhorias e correções de bugs, ao mesmo tempo em que possibilita escalabilidade eficiente para atender as necessidades específicas de cada cliente, sempre mantendo a segurança e resiliência.
+
+#### Como o acesso do usuário é administrado na plataforma incluindo mover, adicionar, alterar e excluir contas?
+
+A gestão de usuários administrativos é realizada de forma direta através do Admin VTEX. Os usuários administrativos são designados para perfis de acesso que podem conter uma ou várias [permissões](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3), as quais são estabelecidas pelo [usuário titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-titular--3oPr7YuIkEYqUGmEqIMSEy) da conta ou por usuários com o perfil de acesso [User Administrator - RESTRICTED](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted) ou com um perfil customizado que contenha o [recurso](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) _Save User_. Saiba mais no artigo [Gerenciar usuários](https://help.vtex.com/pt/tutorial/managing-users--tutorials_512).
+
+#### A plataforma possui funcionalidades para gerenciar, organizar e customizar as permissões de gerenciamento na loja?
+
+Toda ação na VTEX, como acessar uma página no Admin ou fazer uma chamada de API, envolve uma requisição à nossa infraestrutura. Para garantir a segurança dessas operações, existe o **License Manager**, um sistema responsável por verificar se um usuário possui as permissões adequadas para realizar uma ação na plataforma. Para facilitar o gerenciamento dessas permissões, o License Manager é baseado em recursos e perfis de acesso.
+
+Um recurso é uma entidade associada a uma ação ou informação dentro de nossa infraestrutura. Por exemplo, o recurso**_ Product management_** permite que um usuário acesse e edite o formulário de cadastro de produtos no **Catálogo**. Para detalhes sobre cada recurso disponível, veja [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3).
+
+Um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) determina o conjunto de recursos que um grupo de usuários pode acessar na VTEX. Cada usuário administrativo pode ser associado a um ou mais perfis de acesso. Ao criar um novo perfil de acesso, você tem a opção de utilizar um dos [perfis predefinidos ](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy)disponibilizados pela VTEX ou de [criar um perfil customizado](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy), selecionando cada recurso necessário.
+
+### Segurança da plataforma
+
+#### A plataforma utiliza certificados SSL (Secure Sockets Layer)?
+
+O SSL (Secure Sockets Layer) é um protocolo desenvolvido para elevar a segurança dos dados transmitidos pela internet. As conexões via SSL são particularmente recomendadas para envio de informações como números de cartão de crédito, senhas e qualquer outra informação sigilosa via internet.
+
+Não é necessário solicitar a compra do certificado SSL. A VTEX gera um certificado SSL para a sua loja e garante sua renovação automática. O certificado é emitido via Let’s Encrypt e sua criação é responsabilidade da VTEX no momento do go-live da loja. Saiba mais em [Certificado de segurança (SSL)](https://help.vtex.com/pt/tutorial/certificado-de-seguranca-ssl--tutorials_1308).
+
+#### Como é feito o gerenciamento de Patches de Segurança?
+
+Nossos clientes não são responsáveis por aplicar patches, pois a VTEX conduz um processo de gerenciamento de patches que assegura o uso da mesma versão do software por todos os _tenants_.
+
+A VTEX administra os lançamentos de software em atualizações principais, secundárias e de patches. As atualizações de patches e secundárias não impactam os contratos de API, podendo ser lançadas para todos os clientes sem afetar a funcionalidade das lojas.
+
+Os componentes do sistema operacional e do aplicativo, como bibliotecas, são regularmente atualizados e passam por rigorosas verificações de segurança.
+
+#### A plataforma é monitorada quanto a avaliação de performance? Quais variáveis definem a escalabilidade da plataforma?
+
+A Plataforma da VTEX é uma solução SaaS (Software as a Service) e pode ser acessada utilizando qualquer navegador de Internet. A VTEX se encarrega de disponibilizar e atualizar regularmente a solução com novas funcionalidades e monitorar por completo seu funcionamento. Além disso, existem equipes especializadas que garantem escalabilidade da plataforma, através da realização de um monitoramento constante da performance de cada loja.
+
+#### A plataforma restringe os acessos a IPs públicos da Internet?
+
+O bloqueio de acesso ao ambiente administrativo da loja (Admin VTEX) para IPs específicos é possível. No entanto, o site da loja permanece sempre aberto ao público em geral. Para solicitar bloqueios específicos, favor entre em contato com o nosso [Suporte](https://help.vtex.com/pt/support).
+
+#### A solução trabalha com protocolo seguro (HTTPS)?
+
+A plataforma VTEX trabalha com protocolo seguro HTTPS e esse protocolo garante que a comunicação entre os componentes do sistema se mantenham protegidos e os dados sejam transportados de modo seguro.
+
+#### A solução utiliza WAF?
+
+Oferecemos a solução de WAF como parte do produto adicional [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). Confira a documentação do [WAF](https://help.vtex.com/pt/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn) para mais informações.
+
+#### A plataforma VTEX utiliza o conceito API-First?
+
+A VTEX prioriza o desenvolvimento da API first, onde todos os dados transacionados dentro da plataforma podem ser manipulados através de APIs. Saiba mais sobre as [APIs da VTEX](https://developers.vtex.com/docs/api-reference).
+
+A VTEX segrega as camadas de back-end, APIs, front-end e componentes, garantindo que cada parte responsável interaja somente com a camada que lhe compete. A documentação de apoio ao desenvolvedor pode ser acessada no [Developer Portal](https://developers.vtex.com/).
+
+#### A solução fornece detecções de anomalias, ou seja, possui a habilidade de detectar comportamentos incomuns e possíveis tráficos maliciosos, além de comportamento de contas de usuário?
+
+A plataforma VTEX é constantemente monitorada por um sistema de monitoramento, gerenciado pelo time de Segurança da VTEX. Temos um conjunto abrangente de controles que abarca toda a plataforma e está conectado aos sistemas 100% do tempo para detectar uma ampla gama de anomalias. Esse monitoramento é um esforço contínuo e gradual, e nossa equipe responsável está constantemente trabalhando para adicionar novas regras e alertas.
+
+Alguns desses alertas são encaminhados para nossas equipes internas, enquanto outros são direcionados diretamente para os responsáveis de cada loja. Alguns alertas são apenas registrados e não geram notificações. Por exemplo, as tentativas de login com falha são limitadas e registradas, mas não geram alertas. No entanto, o proprietário da conta receberá um e-mail se um usuário modificar as credenciais de administrador.
+
+O produto adicional [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) gera alguns alertas extras para fortalecer ainda mais a sua segurança e confere mais independência para que os lojistas possam fazer seu próprio monitoramento.
+
+#### Como a plataforma é monitorada quanto a avaliação de performance? Quais variáveis definem a escalabilidade da solução?
+
+Nossa plataforma é equipada com diversos indicadores de desempenho que nos alertam sobre possíveis problemas. Alguns exemplos desses indicadores incluem a medição da CPU e memória dos servidores, o tempo de resposta de cada requisição e o volume médio de vendas. Mantemos um monitoramento constante desses e de vários outros indicadores, com o suporte de uma inteligência artificial baseada em uma heurística proprietária. Essa IA identifica e notifica nossa equipe sempre que há um desvio em relação ao padrão esperado.
+
+Para lidar com esses alertas, contamos com uma equipe de engenharia disponível 24 horas por dia, 7 dias por semana. Essa equipe está sempre de plantão e pronta para intervir em caso de ocorrências técnicas, garantindo assim a estabilidade e o bom funcionamento contínuo da nossa plataforma.
+
+### Auditoria de logs
+
+#### Qual é o conteúdo mínimo dos logs que são registrados pela plataforma?
+
+Todas as operações sensíveis que ocorrem na plataforma são automaticamente registradas em logs e não é possível desabilitar essa funcionalidade. A VTEX armazena todos os logs de erros da plataforma VTEX em um software SIEM (Security Information and Event Management), cujos dados são acessados pelo time VTEX com finalidade de análise e melhoria do produto. Além disso, a VTEX mantém monitores para determinados padrões nos logs da aplicação e da infraestrutura que indiquem potencial risco de segurança para o sistema, emitindo alertas ou até mesmo contramedidas automáticas quando eles são identificados.
+
+Além disso, a VTEX registra diversas operações, seus autores e os horários em que elas ocorreram no [Audit](https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA), um módulo disponível no Admin VTEX para pesquisar e investigar este histórico com o auxílio de filtros. Cada módulo da plataforma possui uma equipe de desenvolvimento dedicada que analisa e decide quais informações são registradas neste módulo. Confira a lista de [eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
+
+#### Como os clientes da VTEX podem obter acesso em tempo real a todos os logs da plataforma?
+
+A VTEX não concede acesso aos seus sistemas internos, a fim de preservar a privacidade e a segurança dos nossos clientes, além de garantir conformidade com as normas e legislações em vigor.
+
+No entanto, disponibilizamos logs de diversos [eventos](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ) no [Audit](https://help.vtex.com/pt/tutorial/searching-for-events-on-audit--5RXf9WJ5YLFBcS8q8KcxTA) e permitimos que nossos clientes solicitem logs de eventos específicos ao [Suporte](https://help.vtex.com/pt/support). Além disso, eles podem optar por implementar uma camada de proxy reverso antes da VTEX, o que proporciona uma maior visibilidade sobre as solicitações que chegam ao seu ambiente. Essa abordagem permite que os clientes tenham um controle mais detalhado e personalizado sobre o fluxo de dados em sua infraestrutura, mantendo a segurança e a privacidade conforme necessário.
+
+### Desenvolvimento seguro
+
+#### Quais são as boas práticas de segurança para desenvolvimento que a companhia utiliza?
+
+O processo de desenvolvimento de software segue etapas automatizadas para garantir eficiência. Quando uma equipe de desenvolvimento finaliza uma parte do software, ela é marcada com uma identificação no sistema de controle de versão. Isso desencadeia automaticamente a sua implementação em um ambiente de teste chamado `BETA` ou em produção real, conhecido como `STABLE`.
+
+Além dos testes feitos por especialistas ou até mesmo pelos próprios clientes no ambiente `BETA`, há testes automáticos que são atualizados para se ajustarem a novidades no software ou em sua infraestrutura. Esses testes são essenciais para detectar problemas que possam surgir na versão nova ou devido a questões técnicas. Essa abordagem assegura a estabilidade e a qualidade do software durante todo o seu ciclo de vida.
+
+#### Os ambientes de Desenvolvimento, de Staging/QA e de Produção são totalmente segregados? Os desenvolvedores da companhia não possuem acesso ao ambiente de produção?
+
+Sim, todos os ambientes são totalmente segregados. O ambiente de produção só pode ser implantado por meio do processo de gerenciamento de mudanças, que é automatizado.
+
+#### Existem diretrizes e padrões de codificação de segurança usados para o desenvolvimento de aplicativos?
+
+Os desenvolvedores na VTEX seguem os princípios do OWASP para garantir a qualidade e a segurança do código. A revisão por pares é obrigatória, o que adiciona uma camada adicional de garantia de qualidade e segurança. Além disso, cada código de produção passa pela aprovação de pelo menos dois desenvolvedores com conhecimento em segurança.
+
+Os engenheiros da VTEX adotam os métodos delineados no OWASP Top 10 para prevenir a inserção de código malicioso. Para reforçar ainda mais a segurança, a VTEX implementou um sistema de escaneamento de código no repositório, que conta com uma revisão dedicada de especialistas em Segurança.
+
+Todos os membros da equipe são treinados em desenvolvimento seguro, e esse conhecimento é continuamente aprimorado através de treinamentos e testes periódicos.
+
+#### A companhia realiza análise de vulnerabilidades em bibliotecas e pacotes de Software?
+
+Sim, a VTEX possui um processo de análise de vulnerabilidades em bibliotecas e pacotes de software implementado como parte de suas práticas de segurança. Esta análise é conduzida regularmente para identificar quaisquer vulnerabilidades ou falhas de segurança presentes nas bibliotecas e pacotes utilizados no desenvolvimento de software. Essa abordagem proativa ajuda a garantir que apenas componentes seguros e livres de vulnerabilidades sejam integrados aos sistemas da empresa, fortalecendo assim a segurança de suas soluções e protegendo os dados dos clientes.
+
+### Segurança física e data centers
+
+#### A VTEX possui medidas de segurança para a proteção física dos dispositivos e equipamentos de rede?
+
+A plataforma VTEX é uma solução SaaS (Software as a Service) hospedada em um ambiente altamente controlado e seguro. Como parte de nossa política de gestão de riscos, os fornecedores são periodicamente reavaliados em relação às suas práticas de segurança e conformidade. É importante ressaltar que a VTEX é uma empresa 100% Cloud Commerce, operando exclusivamente na infraestrutura da Amazon Web Services (AWS). Não possuímos servidores físicos próprios para prestação de serviços.
+
+Todos os dados, tanto os nossos quanto os de nossos clientes, são hospedados na AWS, um dos principais provedores de serviços de infraestrutura em nuvem pública do mundo. Mantemos acordos com a AWS para garantir uma linha de base de segurança física e proteção ambiental para a execução de nossos serviços. Recomendamos que os clientes verifiquem os [controles de segurança física fornecidos pela AWS](https://aws.amazon.com/pt/compliance/data-center/controls/), como parte de sua diligência ao considerar a segurança de seus dados na plataforma VTEX.
+
+#### Como a VTEX aplica medidas de segurança física para a proteção do Data Center?
+
+A VTEX é uma empresa inteiramente baseada em Cloud Commerce, utilizando a Amazon Web Services (AWS) como provedora de seus data centers. A AWS opera seus data centers em conformidade com as [diretrizes do Tier III+](https://aws.amazon.com/pt/compliance/uptimeinstitute/), garantindo assim um alto padrão de confiabilidade e segurança.
+
+Em relação à segurança de nossos escritórios, a VTEX mantém escritórios em várias partes do mundo, e implementa rigorosos controles de segurança física em todas as suas instalações. Isso inclui monitoramento e controle de acesso em todos os escritórios, supervisionados por uma equipe de segurança profissional. O acesso físico é estritamente controlado nos pontos de entrada dos edifícios, utilizando sistemas de vigilância como catracas e outros dispositivos eletrônicos. Todos os acessos autorizados são registrados de forma a garantir um controle completo sobre as entradas e saídas.
+
+Além disso, nossos escritórios são equipados com sistemas de Câmeras de Televisão de Circuito Fechado (CFTV), garantindo uma vigilância contínua e registro de imagens de acordo com os requisitos legais e de conformidade. Também implementamos controles avançados de energia e supressão de incêndios, alinhados com as melhores práticas do setor, a fim de evitar falhas e surtos elétricos, garantindo a segurança e integridade de nossas instalações físicas.
+
+#### Em quais países e localidades os data centers estão localizados?
+
+A VTEX utiliza principalmente as seguintes regiões de dados dentro da AWS para cada finalidade a seguir:
+
+* AWS Northern Virginia: Armazenamento de dados primário
+* AWS norte da Califórnia: Local de backup
+
+### Gerenciamento de vulnerabilidades
+
+#### A VTEX realiza regularmente scans de vulnerabilidade, eles são realizados em qual periodicidade?
+
+As verificações de vulnerabilidade são executadas continuamente. Cada uma delas deve ser executada novamente até que sejam aprovadas, sem problemas apontados para serem aceitos pelo auditor durante nossos períodos de recertificação.
+
+#### As customizações ou configurações do produto realizadas pelos clientes poderão introduzir vulnerabilidades de segurança na plataforma? Se sim, como a eventualidade será gerenciada?
+
+Os lojistas e quaisquer agências implementadoras contratadas por eles têm a liberdade de realizar personalizações e customizações na plataforma dentro de seus próprios ambientes. No caso de identificação de vulnerabilidades nos sistemas da VTEX, nossa equipe de segurança e desenvolvimento atua de forma ágil para tratar essas questões. Devido à natureza personalizável da plataforma, é de responsabilidade do lojista e da agência implementadora lidar com as vulnerabilidades que possam surgir em decorrência de customizações feitas durante o desenvolvimento. Confira [Responsabilidades no ecossistema VTEX](https://help.vtex.com/pt/tutorial/responsabilidades-no-ecossistema-vtex--3vL9aWICDr3WR64DYi1fJ3#agencias-implementadoras) para mais informações.
+
+### Resposta e mitigação a incidentes
+
+#### Existe um Plano de Resposta a Incidentes formal?
+
+Sim, a VTEX conta com um protocolo formalizado para Resposta a Incidentes de Segurança, abrangendo as etapas essenciais do processo: Preparação, Identificação do Incidente, Contenção, Erradicação, Recuperação e Pós-Incidente. Esse procedimento também inclui um plano de comunicação integrado que é aplicado em todas as fases da resposta. Além disso, mantemos playbooks detalhados para orientar a equipe de atendimento e realizamos testes de invasão (Gray Box) anualmente para avaliar e fortalecer constantemente nossas medidas de segurança.
+
+#### A companhia possui um calendário de testes de penetração? Qual a periodicidade?
+
+Os pentests são conduzidos semestralmente na VTEX. Lojistas que desejam realizar testes de penetração e varreduras de vulnerabilidade em seus ambientes precisam contratar o produto adicional [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) e são incentivadas a compartilhar os resultados com a VTEX, permitindo que nossa equipe de Segurança aborde quaisquer possíveis problemas identificados.
+
+#### A VTEX possui um procedimento de Resposta a Incidentes envolvendo vazamento de dados e em conformidade com as leis de proteção de dados pessoais?
+
+Sim, o Plano de Resposta a Incidentes de Segurança da VTEX prevê incidentes relacionados a vazamento de dados e está em conformidade com as leis de proteção de dados pessoais. Ele abrange as etapas essenciais do processo: Preparação, Identificação do Incidente, Contenção, Erradicação, Recuperação e Pós-Incidente. Esse procedimento também inclui um plano de comunicação integrado que é aplicado em todas as fases da resposta. 
+
+#### Quais controles a VTEX utiliza para mitigar ataques Ransomware?
+
+A VTEX utiliza uma abordagem abrangente para mitigar ataques de ransomware, empregando medidas como antivírus avançados, firewalls, e filtros de conteúdo para bloquear o malware. Além disso, mantemos backups regulares de dados críticos, garantindo a capacidade de restauração sem ceder a exigências de criminosos. Atualizações de segurança e treinamento de conscientização para funcionários são prioridades, juntamente com monitoramento constante de atividades em busca de comportamentos suspeitos. Essas medidas combinadas formam uma defesa robusta contra a ameaça crescente de ransomware.
+
+### Disaster Recovery e continuidade de negócios
+
+#### A VTEX possui um Plano de Continuidade de Negócios?
+
+A VTEX possui um plano de continuidade de negócios cuidadosamente elaborado para enfrentar os desafios decorrentes de emergências. Este plano visa estabelecer uma base sólida para a rápida e eficaz retomada das operações habituais, independentemente da natureza da emergência, garantindo assim uma transição suave e minimizando possíveis impactos.
+
+#### A VTEX possui um Plano de Disaster Recovery?
+
+A VTEX adota um plano de Recuperação de Desastres centrado na garantia da continuidade operacional e na disponibilidade de recursos críticos em situações de emergência. Este plano abrange diretrizes detalhadas sobre como agir diante de incidentes não planejados, caracterizados como crises, que podem surgir de desastres naturais, ataques cibernéticos ou quaisquer outros eventos disruptivos. Incorporamos etapas cruciais de recuperação, incluindo a definição dos objetivos RPO (Recovery Point Objective) e RTO (Recovery Time Objective), bem como a realização de testes de backup, assegurando a eficácia e prontidão do plano em cenários reais.
+
+#### A VTEX testa periodicamente o Plano de Recuperação de Desastres?
+
+O Plano de Recuperação de Desastres é submetido a testes pelo menos uma vez por ano para garantir sua eficácia. Não testamos todo o plano em um único evento; diferentes componentes ou processos com ciclos de vida independentes são testados conforme sua relevância e frequência exigida. De qualquer forma, cada parte passa por testes anuais.
+
+Se alguma parte do plano for considerada ineficaz, uma nova versão do processo é desenvolvida para resolver o problema. Tradicionalmente, os eventos que antecedem a Black Friday e a Cyber Monday oferecem a oportunidade ideal para conduzirmos os testes de recuperação de desastres.
diff --git a/docs/tutorials/pt/roles.md b/docs/tutorials/pt/roles.md
index 78f38d979..ecdaddd9a 100644
--- a/docs/tutorials/pt/roles.md
+++ b/docs/tutorials/pt/roles.md
@@ -1,105 +1,68 @@
 ---
 title: 'Perfis de acesso'
 id: 7HKK5Uau2H6wxE1rH5oRbc
-status: PUBLISHED
+status: CHANGED
 createdAt: 2020-04-08T15:21:05.110Z
-updatedAt: 2022-10-04T19:58:47.622Z
-publishedAt: 2022-10-04T19:58:47.622Z
+updatedAt: 2023-11-30T21:36:49.415Z
+publishedAt: 2023-09-26T13:32:10.280Z
 firstPublishedAt: 2020-04-08T20:52:12.334Z
 contentType: tutorial
 productTeam: Identity
-author: 127RQ7SUoFfyTh5gbXUpdM
+author: 1malnhMX0vPThsaJaZMYm2
 slug: perfis-de-acesso
 locale: pt
 legacySlug: como-criar-perfil-de-acesso
 subcategory: 1HSqkejwuYcQSMC400uY84
 ---
 
-Toda ação na plataforma VTEX, como acessar uma página na interface administrativa, clicar em um botão ou fazer uma chamada em uma de nossas APIs, envolve uma requisição à nossa infraestrutura. Como é comum que as interfaces administrativas sejam compartilhadas pelos diversos colaboradores de uma empresa, é importante conseguir limitar o acesso a ações críticas dentro de uma conta. Dessa forma, minimiza-se a possibilidade de disrupções na operação de uma loja e garante-se que cada usuário tenha acesso apenas ao que lhe compete.
+A página **Perfis de acesso** no Admin VTEX possibilita gerenciar os [perfis de acesso](https://help.vtex.com/pt/tutorial/controle-de-acesso--4rM3gyiWqtkim4Q8hOvLTC#perfis-de-acesso) cadastrados na sua loja e os usuários associados a eles. Para acessá-la, na barra superior do Admin VTEX, clique no avatar do seu perfil, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Perfis de acesso**.
 
-## O que é um perfil de acesso?
+A partir da página de perfis de acesso, você pode realizar as seguintes ações:
 
-Na VTEX, utilizamos um sistema baseado em **recursos** para obter maior precisão no controle de acesso. Um **recurso** é uma entidade associada a uma ação ou informação dentro de nossa infraestrutura. Sempre que nossos sistemas recebem uma requisição, é feita uma análise de segurança para garantir que o usuário responsável pela chamada tem a permissão necessária. Para que a requisição seja bem-sucedida, o usuário precisa ter os recursos associados a essa requisição presentes em sua conta.  
+* [Criar um perfil de acesso](#criar-um-perfil-de-acesso) 
+* [Buscar um perfil de acesso](#buscar-um-perfil-de-acesso)
+* [Editar um perfil de acesso](#editar-um-perfil-de-acesso)
+* [Excluir um perfil de acesso](#excluir-um-perfil-de-acesso)
 
-Atualmente, trabalhamos com algumas centenas de recursos diferentes nos produtos VTEX. Para facilitar o gerenciamento de acesso de usuários por parte dos administradores de uma conta, existe o conceito de **Perfil de Acesso**. Para mais detalhes sobre cada recurso disponível, veja [Recursos do License Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
+![roles-pt](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/943f5df380f3fb685bb369014b435454/roles-pt.png)
 
-Um **Perfil de Acesso** é um conjunto de recursos criado para atender a um tipo comum de usuário. Por exemplo: operadores de call center costumam executar um conjunto bem definido de tarefas. Percebendo isso, um administrador da conta, tendo acesso aos [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) necessários, pode criar um **Perfil de Acesso** personalizado com todas as permissões necessárias para aqueles colaboradores e controlar o acesso de todos eles de uma vez.
+A página apresenta uma lista com todos os perfis de acesso cadastrados na conta e suas respectivas informações em uma tabela: 
 
-### Tipos de perfis
+| **Coluna** | **Descrição** |
+|---|---|
+| **Nome** | Nome que identifica o perfil de acesso. |
+| **Usuários** | Quantidade de usuários associados ao perfil de acesso. |
+| **Tipo de perfil de acesso** | Tipo de perfil de acesso, que pode ser **Predefinido** ou **Personalizado**. Para mais informações sobre cada um, confira [Tipos de perfis de acesso](https://help.vtex.com/pt/tutorial/controle-de-acesso--4rM3gyiWqtkim4Q8hOvLTC#tipos-de-perfis-de-acesso). |
+| **Produtos** | Produtos do License Manager incluídos no perfil de acesso. Veja os produtos disponíveis na coluna **Produto** da tabela em [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3). |
+| **Data de criação** | Data em que o perfil de acesso personalizado foi criado. Perfis de acesso predefinidos ou criados antes de dezembro de 2023 não apresentam nenhuma data nesta coluna. |
 
-Ao criar um novo **perfil de acesso** para sua loja, você tem a opção de criar um perfil customizado, selecionando cada recurso necessário, ou um dos perfis predefinidos disponibilizados pela VTEX. Veja aqui todos os [Perfis predefinidos](https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#) e as respectivas permissões associadas.
-
-Caso deseje criar perfis customizados, confira mais detalhes sobre os [Recursos do License Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
-
-## Criando um perfil de acesso
-
-Os perfis de acesso podem ser gerenciados por meio do painel administrativo da sua conta VTEX. No menu lateral do [Admin](https://help.vtex.com/pt/subcategory/visao-do-geral-do-admin--Se4oi5LroIII2Ei0uGAoE), basta acessar **Configurações da conta > Gerenciamento da conta > Perfis de acesso**.
-
-![Lista perfis de acesso](https://images.ctfassets.net/alneenqid6w5/5SsjVcIztKJQ3yxY1udwOH/af2216756b2b71242cf49647ba5ec08d/image_0.png)
-
-Essa tela apresenta uma lista com todos os **perfis de acesso** cadastrados para a conta. Em uma conta recém-criada, apenas o perfil *Owner (Admin Super)* estará listado. Este perfil dá ao usuário acesso irrestrito a todos os **recursos nativos** da plataforma.
+Em uma conta recém-criada, apenas o perfil *Owner (Admin Super)* estará listado. Este perfil dá ao usuário acesso irrestrito a todos os recursos nativos da plataforma.
 
 <div class="alert alert-warning">
-Alguns produtos, como o <a href="https://help.vtex.com/pt/tracks/vtex-payment--7iCCIoIZFmd9OabU6QlmXu/1lZWKCGdy7xpYjukTLfFJL">VTEX Payment</a>, são contratados a parte. Recursos associados a esses produtos não vêm inclusos no perfil <i>Owner (Admin Super)</i>. Para habilitar os recursos associados a esses produtos deve-se usar seus perfis de acessos correspondentes.
+  <p>A quantidade de usuários com o perfil <em>Owner (Admin Super)</em> deve ser a menor possível. Além disso, é preciso se certificar que haja visibilidade e controle de quem recebe esse acesso.</p>
 </div>
 
-A quantidade de usuários com o perfil *Owner (Admin Super) *deve ser a menor possível. Além disso, é preciso se certificar que haja visibilidade e controle de quem recebe esse acesso.
+## Criar um perfil de acesso
 
-<table>
-  <tr>
-    <td style="border-left: 4px solid #F71963;" bgcolor="#FFE6E6"> <b>Atenção!</b> O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas por vazamento de credenciais de login.</td>
-  </tr>
-</table>
+Para cadastrar um novo perfil, clique em `+ Criar perfil de acesso`. Para detalhes sobre o preenchimento do formulário, leia [Criar perfil de acesso](https://help.vtex.com/pt/tutorial/criar-perfil-de-acesso--qGtNQpKSSAduX94l2WZBW).
 
-Para os usuários que não devem ter acesso irrestrito à plataforma, é importante que se criem **perfis de acesso** que limitem os recursos disponíveis a apenas os estritamente necessários para aquele tipo de usuário. Isso é possível clicando em **Novo Perfil**.
+## Buscar um perfil de acesso
 
-![Novo perfil de acesso](https://images.ctfassets.net/alneenqid6w5/1UGqU2dlXOZGUhGinBv8IN/893ea05f59d4dd44cdfbe7dccdf9d07f/image_1.png)
+Você pode buscar por um perfil de acesso digitando parte do nome dele na barra de busca. Os resultados serão atualizados em tempo real na listagem.
 
-Essa tela permite a criação de um novo perfil. Isso pode ser feito baseando-se em formatos já definidos, criados pela equipe VTEX para atender a cenários comuns nas operações, ou de forma customizada, selecionando-se a quais recursos de cada produto devem ter acesso todos aqueles que estiverem com esse perfil associado a seu usuário.
+## Editar um perfil de acesso
 
-Clicando em **Escolher perfil de acesso**, o menu *dropdown* apresenta uma lista de perfis predefinidos.  
+Você pode editar os recursos e usuários relacionados a um perfil de acesso. Para isso, clique em `⫶` na linha do perfil de acesso que deseja editar e, em seguida, em <i class="fas fa-pencil-alt"></i> `Editar`.
 
-![Menu perfis predefinidos](https://images.ctfassets.net/alneenqid6w5/4XGZb5WvW216z8RfX5Vp3c/5c234cace3cb880eda0771407c4323fb/image_2.png)
+## Excluir um perfil de acesso
 
-Selecionar um dos perfis listados permite inspecionar quais são os recursos incluídos nesse perfil, separados por produto.
+Para deletar um perfil de acesso, clique em `⫶` na linha do perfil de acesso que deseja excluir e, em seguida, em <i class="far fa-trash-alt"></i> `Excluir`.
 
-<div class="alert alert-info">
-  Veja aqui todos os <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy">Perfis predefinidos</a> e as respectivas permissões associadas.
+<div class="alert alert-warning">
+  <p>Ao excluir um perfil de acesso, usuários associados a ele perderão acesso aos <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recursos do License Manager</a> relacionados ao perfil excluído, a não ser que tenham outros perfis de acesso com as mesmas permissões.</p>
 </div>
 
-![Novo perfil de acesso](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/1fe552a5c15c7c3dee8d54c88a60fafc/image_3.png)
-
-O perfil **Call center operator**, por exemplo, contém um recurso do produto *Catálogo* que permite executar operações numa loja em nome de um cliente e um recurso do *OMS* que permite checar o status de um pedido.
-
-Para criar um perfil customizado, o administrador pode escolher a opção **Custom** do menu dropdown **Escolher perfil de acesso. **Ao clicar no menu dropdown em **Escolha um produto**, listam-se todos os recursos associados a cada produto.
-
-![Configurando produto](https://images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/39bc16eca81b8a13946f081c5a1454d3/image_4.png)
-
-É possível adicionar quantos produtos forem necessários ao perfil. Basta clicar no botão **Configurar outro produto**, ao final da lista de produtos e recursos.
-
-![Configurar outro produto](https://images.ctfassets.net/alneenqid6w5/Dsc2k29SxUDKB8t6VXScn/dea9f7fffd121036e088761fb3971e40/image_5.png)
-
-Ao finalizar a configuração de produtos e recursos, o administrador pode escolher um nome para o perfil em **Nome do perfil**, caso se trate de uma configuração customizada.
-
-![Nome do perfil](https://images.ctfassets.net/alneenqid6w5/gTuv92HFXKn4jklYX0Hzj/6dfa6d1cd17483a854624dfd8b185296/image_6.png)
-
-<table>
-  <tr>
-    <td style="border-left: 4px solid #F71963;" bgcolor="#FFE6E6"> <b>Atenção!</b> É importante escolher nomes descritivos para os perfis de acesso, para deixar claro que tipo de usuário deve ter aquele acesso. Idealmente indicando o cargo na empresa ou atividade a ser desempenhada na plataforma.</td>
-  </tr>
-</table>
-
-Boas práticas de gerenciamento dos perfis de acesso aumentam a segurança de uma operação, além de se reforçar a atenção de todos os envolvidos com dados sensíveis de uma loja e de seus clientes. Recomendamos a criação de perfis que sejam análogos às estruturas hierárquicas da organização administradora. Desta forma, todos são responsáveis pelas informações a que podem ter acesso.
-
-Também é possível adicionar usuários ao perfil, customizado ou predefinido, preenchendo o email do usuário a ser inserido em **Adicionar usuários para este perfil de acesso**. Se o usuário não existir, será criado um novo usuário usando o email como nome também (nome e email serão iguais).
-
-![Usuários](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/415e4adaf373fdd4ac3dddc0de9b5c1f/image_7.png)
-
-Terminada a configuração do perfil, deve-se salvar o novo perfil clicando no botão azul no rodapé da página.
-
-![Salvar perfil](https://images.ctfassets.net/alneenqid6w5/68NycUF3T52sg96R6HDIna/0a9d0c8cb67f1247da06fb8867a2b4f3/image_8.png)
-
-Após criado, o novo perfil será listado junto aos demais perfis de acesso. Para vê-lo, acesse **Configurações da conta > Gerenciamento da conta > Perfis de acesso** no menu lateral do Admin.
-
-![image 9](https://images.ctfassets.net/alneenqid6w5/3uQ5SvsqjpFCSJimcg9naY/da7ee311ee12afbf6f432a583105360c/image_9.png)
+## Saiba mais
 
+* [Controle de acesso](https://help.vtex.com/pt/tutorial/controle-de-acesso--4rM3gyiWqtkim4Q8hOvLTC)
+* [Criar perfil de acesso](https://help.vtex.com/pt/tutorial/criar-perfil-de-acesso--qGtNQpKSSAduX94l2WZBW)
diff --git a/docs/tutorials/pt/rounding-rules.md b/docs/tutorials/pt/rounding-rules.md
index 324f8a20d..bea8229fd 100644
--- a/docs/tutorials/pt/rounding-rules.md
+++ b/docs/tutorials/pt/rounding-rules.md
@@ -60,16 +60,16 @@ Abaixo é possível ver exemplos dos fluxos de inclusão, edição e exclusão d
 
 *Fluxo de criação de uma regra*
 
-![config-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/6HPUHcVmPcDz90eXLbKrlV/16bd4ce06174eee79c58e998424f36dd/config-arrendodamento-PT.gif)
+![config-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/6HPUHcVmPcDz90eXLbKrlV/16bd4ce06174eee79c58e998424f36dd/config-arrendodamento-PT.gif)
 
 *Fluxo de alteração de uma regra*
 
-![editar-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/2DYnjck4KL2nGvoSIywViM/f5a35515cfbeb14b10f57fa0989c147f/editar-arrendodamento-PT.gif)
+![editar-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/2DYnjck4KL2nGvoSIywViM/f5a35515cfbeb14b10f57fa0989c147f/editar-arrendodamento-PT.gif)
 
 *Fluxo de exclusão de uma regra*
 
-![deletar-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/5T0Ti47Sv4Nndmg1IitZC5/742cccd2aefde6de5843a6b15d27b16c/deletar-arrendodamento-PT.gif)
+![deletar-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/5T0Ti47Sv4Nndmg1IitZC5/742cccd2aefde6de5843a6b15d27b16c/deletar-arrendodamento-PT.gif)
 
 *Simulação de preço para uma regra*
 
-![teste-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/21ONAWrW6xYEjI5C31yski/9f059b32409995f6be45f22856a62885/teste-arrendodamento-PT.gif)
+![teste-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/21ONAWrW6xYEjI5C31yski/9f059b32409995f6be45f22856a62885/teste-arrendodamento-PT.gif)
diff --git a/docs/tutorials/pt/routing-monitoring.md b/docs/tutorials/pt/routing-monitoring.md
index fa3eb9c08..189f32cca 100644
--- a/docs/tutorials/pt/routing-monitoring.md
+++ b/docs/tutorials/pt/routing-monitoring.md
@@ -79,4 +79,4 @@ Caso precise mudar o status, ao final da página [Detalhes da rota](#detalhes-da
 Para que esteja disponível uma Justificativa ela deve ser cadastrada previamente na aba de Configurações de Conta. Para saber mais confira <a href="https://help.vtex.com/pt/tutorial/justificativa-de-status-vtex-tracking--4shboc7h5XPUpA8TQzXPRG">Justificativa de status</a>.
 </div>
 
-![Monitoramento de Rota](https://images.ctfassets.net/alneenqid6w5/3cHz27dvHjO7ObLDxJTIuc/01103e99a288ab15935a7b453487fd7c/Monitoramento_Rota.gif)
+![Monitoramento de Rota](//images.ctfassets.net/alneenqid6w5/3cHz27dvHjO7ObLDxJTIuc/01103e99a288ab15935a7b453487fd7c/Monitoramento_Rota.gif)
diff --git a/docs/tutorials/pt/sales-app-sales-performance.md b/docs/tutorials/pt/sales-app-sales-performance.md
index c874b2a98..87f452191 100644
--- a/docs/tutorials/pt/sales-app-sales-performance.md
+++ b/docs/tutorials/pt/sales-app-sales-performance.md
@@ -22,7 +22,7 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 1. No aplicativo do Sales App, acesse a página principal do aplicativo. 
 2. Clique no botão <i class="fas fa-bars"></i>.
 3. Clique em **Performance de vendas**. 
-![Métricas da Loja](https://images.ctfassets.net/alneenqid6w5/4DLSNWjwX0G26UoKr4K9wg/03d35f5197f748a3f9f3ca2138039c3f/vendas_totais.png)
+![Métricas da Loja](//images.ctfassets.net/alneenqid6w5/4DLSNWjwX0G26UoKr4K9wg/03d35f5197f748a3f9f3ca2138039c3f/vendas_totais.png)
 Nessa página, você terá acesso às seguintes métricas:
 
 - **Valor total das vendas:** exibirá o valor total das vendas da loja referentes aos períodos selecionados no campo **Exibir** (azul) e do campo **Comparado a** (cinza), indicando a porcentagem de aumento ou decréscimo de venda nesta comparação.
@@ -39,7 +39,7 @@ Para acessar métricas específicas de um vendedor, siga os passos abaixo:
 2. Selecione o perfil do vendedor e insira a senha de acesso.
 3. Clique em `Confirmar`.
 
-![Vendas de Bruna - VTEX Sales App](https://images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/bbe1ec3e5cf0e840f01acd279301e81c/Vendas_de_bruna_-.png)
+![Vendas de Bruna - VTEX Sales App](//images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/bbe1ec3e5cf0e840f01acd279301e81c/Vendas_de_bruna_-.png)
 
 Nessa página, você terá acesso às seguintes métricas referentes àquele vendedor:
 
diff --git a/docs/tutorials/pt/sales-associate-code-field-at-checkout.md b/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
new file mode 100644
index 000000000..ce14d9613
--- /dev/null
+++ b/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
@@ -0,0 +1,96 @@
+---
+title: 'Campo Código de Vendedor no Checkout'
+id: 6hiRCXt5Cz250o7hBnN2Tp
+status: PUBLISHED
+createdAt: 2023-06-20T12:18:18.542Z
+updatedAt: 2023-06-20T21:50:57.120Z
+publishedAt: 2023-06-20T21:50:57.120Z
+firstPublishedAt: 2023-06-20T15:04:21.346Z
+contentType: tutorial
+productTeam: Shopping
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: campo-codigo-de-vendedor-no-checkout
+locale: pt
+legacySlug: campo-codigo-de-vendedor-no-checkout
+subcategory: 
+---
+
+Na VTEX, você pode criar um campo para registrar o código de vendedor no Checkout. Por meio dele, é possível:
+- Associar uma determinada ordem de compra a um vendedor.
+- Oferecer descontos exclusivos ao consumidor.
+- Administrar a performance de seus vendedores, extraindo dados como número de vendas / ticket médio por vendedor, ranking para comissionamento de vendas, entre outros.
+
+<div class="alert alert-warning">
+  O campo <b>código de vendedor</b> não substitui o campo <b>cupom de desconto</b> (nativo na plataforma VTEX). Ao realizar as configurações deste artigo, ambos poderão ser utilizados para oferecer descontos.
+</div>
+
+Para criar o campo e inseri-lo na tela do Checkout de sua loja, três etapas são necessárias:
+
+1. [Criar nova entidade de dados](#criar-nova-entidade-de-dados)
+2. [Criar promoção Código do Vendedor](#criar-promocao-codigo-do-vendedor)
+3. [Customizar UI no Checkout](#customizar-ui-no-checkout)
+
+## Criar nova entidade de dados
+
+O campo **Código de Vendedor** deve ser registrado no [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw) como uma nova entidade. Para criar a entidade de dados, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Configurações da loja > Storefront > Master Data**, ou digite **Master Data** na barra de busca no topo da página.
+2. Crie uma nova [entidade de dados](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar) chamada *codigovendedor*.
+3. Dentro da nova entidade de dados, crie os seguintes campos:
+    - **Código do vendedor**: com valor máximo de 10 caracteres (tipo Varchar10).
+    - **Email**: endereço de email do vendedor (tipo Email).
+    - **Nome**: nome de vendedor (tipo Text).
+    - **Status**: indica se o vendedor está ativo ou inativo (tipo Boolean).
+    - **Loja**: identificação da loja onde o vendedor atua (tipo Text).
+    - Demais campos (conforme necessidade).
+
+<blockquote><ui>4. Cadastre as informações de cada vendedor nos campos criados no passo anterior.</ui>
+
+<blockquote><ui>5. Crie um <a href="https://help.vtex.com/pt/tutorial/criando-formulario-no-master-data">formulário</a> para ter acesso às informações da nova entidade <i>codigovendedor</i> por meio da interface do Master Data.</ui>
+
+## Criar promoção Código do Vendedor
+
+Após a criação da entidade *codigovendedor*, é necessário associá-la a uma promoção. Para criar uma nova promoção, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Promoções > Promoções**, ou digite **Promoções** na barra de busca no topo da página.
+2. Crie uma nova [promoção regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI). Preencha as informações de **Dados gerais de promoção** e **A quais itens esta promoção será aplicada?** conforme desejado.
+
+<div class="alert alert-info">
+  Caso deseje utilizar o campo código de vendedor para oferecer desconto no valor da compra, preencha as informações em <b>Tipo e valor de de desconto?</b>.
+</div>
+
+<blockquote><ui>3. Em <b>Quais as condições para a promoção ser válida?</b>, clique na opção <b>utm_campaign</b> e digite no campo <i>codigovendedor</i>.</ui>
+
+![utm campaign codigovendedor](//images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/1896457a0ea45bc20292377e8c963077/UTM_Campaign_codigovendedor.PNG)
+
+<blockquote><ui>4. Em <b>Restrições e limitações de uso</b>, adicione as demais restrições disponíveis, caso desejar. Selecione a opção <b>Permitir acumular promoções</b>.</ui>
+
+<blockquote><ui>5. Clique em <b>Salvar</b>.</ui>
+
+## Customizar UI no Checkout
+
+A última etapa consiste em configurar a tela do Checkout para permitir a exibição do campo **Código do Vendedor**. 
+
+Para realizar esta customização, é necessário entrar em contato com a agência parceira responsável pela criação da sua loja e solicitar que o novo campo seja inserido, permitindo que o cliente insira o código do vendedor e o nome do mesmo seja exibido. 
+
+Adicionalmente, os seguintes passos devem ser realizados:
+
+1. Ao simular uma compra e inserir o código do vendedor na tela do Checkout, certifique-se que a chamada GET [Search Documents](https://developers.vtex.com/docs/api-reference/master-data-api-v2#get-/api/dataentities/-dataEntityName-/search) realize a busca na entidade `codigovendedor` e retorne todas as informações cadastradas do vendedor. Exemplo de chamada: https://{accountName}.{environment}.com.br/api/dataentities/codigovendedor/search?codigovendedor=12345.
+
+<div class="alert alert-warning">
+  O campo <b>status</b> deve retornar o valor <b>true</b>, indicando que o código do vendedor é válido.
+</div>
+
+<blockquote><ui>2. Efetue a chamada POST <a href="https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm">Update orderForm configuration</a> para incluir as seguintes informações no <a href="https://developers.vtex.com/docs/guides/orderform-fields">orderForm</a> de sua loja</ui>:
+
+<blockquote><blockquote>- <b>marketingData</b>: em <i>"utmCampaign"</i>, inserir <i>codigovendedor"</i>. Caso esta informação não seja descrita, a promoção (código do vendedor) não será aplicada no carrinho e o campo não será exibido.
+
+<blockquote><blockquote>- <b>openTextField</b> (opcional): inserir observações ou comentários (ex. informações para filtros de comissionamento).
+
+<div class="alert alert-warning">
+  Somente a informação do nome do vendedor deve ser exibida na tela do Checkout.
+</div>
+
+Após executar todas as etapas acima descritas, o campo **Código do Vendedor** estará disponível na tela do Checkout.
+
+![Código do vendedor](//images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/c44bb28d5954f7f015da9feb751dc8f4/Checkout_UI_-_PT_2.png)
diff --git a/docs/tutorials/pt/sales-associates-instore-beta.md b/docs/tutorials/pt/sales-associates-instore-beta.md
index bd3bcd2f8..d02d40ea2 100644
--- a/docs/tutorials/pt/sales-associates-instore-beta.md
+++ b/docs/tutorials/pt/sales-associates-instore-beta.md
@@ -29,7 +29,7 @@ Esta página permite que você gerencia seus vendedores a partir das seguintes a
 * [Editar](#editar-vendedor)
 * [Excluir](#excluir-vendedor)
 
-![vendedores-pt](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/247cb80ead8132c0b82a5787328279dc/image.png)
+![vendedores-pt](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/247cb80ead8132c0b82a5787328279dc/image.png)
 
 A página apresenta as seguintes informações: 
 
@@ -52,7 +52,7 @@ Você pode cadastrar um vendedor seguindo os passos abaixo:
 
 Após o cadastro, o vendedor irá receber um email confirmando o cadastro e redirecionando para a opção de login do vendedor ao aplicativo inStore.
 
-![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+![email-vendedor-pt](//images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
 <div class ="alert alert-warning">
 <p>Os vendedores cadastrados no inStore não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin seu cadastro será excluído.</p> 
diff --git a/docs/tutorials/pt/sales-funnel-suiteshare.md b/docs/tutorials/pt/sales-funnel-suiteshare.md
index 79453bf80..56ecc5ffe 100644
--- a/docs/tutorials/pt/sales-funnel-suiteshare.md
+++ b/docs/tutorials/pt/sales-funnel-suiteshare.md
@@ -25,22 +25,22 @@ Nessa etapa, será possível localizar todas as informações necessárias para
 
 Nessa página você irá encontrar todas as informações necessárias para realizar a integração.
 
-![Funil de vendas_1](https://images.ctfassets.net/alneenqid6w5/Fk4RseF2XChIrFyoLy4k4/872ac7d142b8f47309be32cd84ea14ff/Funil_de_vendas_1.png)
+![Funil de vendas_1](//images.ctfassets.net/alneenqid6w5/Fk4RseF2XChIrFyoLy4k4/872ac7d142b8f47309be32cd84ea14ff/Funil_de_vendas_1.png)
 
 Para realizar a integração com a Suiteshare, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Funil de Vendas**.
 
-   ![Funil de vendas_2](https://images.ctfassets.net/alneenqid6w5/7kizQsL75XA6W5a0Lz06YR/c2c6238812f816f1b3cd649fdf6288ae/Funil_de_vendas_2.png)
+   ![Funil de vendas_2](//images.ctfassets.net/alneenqid6w5/7kizQsL75XA6W5a0Lz06YR/c2c6238812f816f1b3cd649fdf6288ae/Funil_de_vendas_2.png)
 
 2. Acesse **Configurações > Integrações > Funil de Vendas > Integrar**.
 
-   ![Funil de vendas_3](https://images.ctfassets.net/alneenqid6w5/6pq85VMCe5UDq6XucdVi7h/4e69b243a4d8e5316a9ba95a2e67eb75/Funil_de_vendas_3.png)
+   ![Funil de vendas_3](//images.ctfassets.net/alneenqid6w5/6pq85VMCe5UDq6XucdVi7h/4e69b243a4d8e5316a9ba95a2e67eb75/Funil_de_vendas_3.png)
 
 Clique em **Conectar**.
 
 Pronto! Esse deve ser o resultado da integração dentro do Funil de Vendas CRM:
 
-![Funil de vendas_4](https://images.ctfassets.net/alneenqid6w5/46bMGyUdRbzTwK6OcUss57/42741b5b2196679f2adac2e5131a61e3/Funil_de_vendas_4.png)
+![Funil de vendas_4](//images.ctfassets.net/alneenqid6w5/46bMGyUdRbzTwK6OcUss57/42741b5b2196679f2adac2e5131a61e3/Funil_de_vendas_4.png)
 
 Agora é só aproveitar a integração!
diff --git a/docs/tutorials/pt/sales-performance.md b/docs/tutorials/pt/sales-performance.md
index 8b67d2f39..9243f63ff 100644
--- a/docs/tutorials/pt/sales-performance.md
+++ b/docs/tutorials/pt/sales-performance.md
@@ -3,8 +3,8 @@ title: 'Performance de Vendas'
 id: 3DMube0sEsK9vPcRYGas72
 status: PUBLISHED
 createdAt: 2021-10-19T12:49:42.165Z
-updatedAt: 2022-12-20T14:05:11.128Z
-publishedAt: 2022-12-20T14:05:11.128Z
+updatedAt: 2023-11-09T19:56:56.074Z
+publishedAt: 2023-11-09T19:56:56.074Z
 firstPublishedAt: 2021-10-19T12:55:27.227Z
 contentType: tutorial
 productTeam: Others
@@ -26,7 +26,7 @@ Para acessar a página, em seu Admin VTEX vá para __Dashboards > Performance de
 
 É possível customizar a visualização dos dados do gráfico e da lista filtrando por período, dimensões e métricas.
 
-![Sales Perf Dash PT](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
+![Sales Perf Dash PT](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
 
 ## Dados 
 Os dados da página são provenientes do [sistema de Gerenciamento de Pedidos](https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa) da VTEX. A Performance de Vendas é uma solução analítica, que usa heurísticas e fórmulas criadas a partir de nossa experiência levando nossos clientes de ecommerce para o próximo nível para calcular suas métricas. A página não deve ser utilizada como substituto para os dados do OMS, mas como ferramenta de análise e insights de negócio.
@@ -35,7 +35,9 @@ Para garantir que você tenha acesso tanto aos últimos dados atualizados e tamb
 
 Esses grupos também são processados por sistemas diferentes, o que pode causar uma diferença entre dados do OMS e do Performance de Vendas, apesar de buscarmos apresentar no máximo 5% de divergência. 
 
+<div class ="alert alert-warning">
 É provável que existam diferenças entre as métricas de receita e ticket médio registradas no OMS e no Performance de Vendas, por exemplo. Isso ocorre porque o Performance de Vendas considera o valor dos itens, enquanto o OMS também considera os descontos, frete, taxas e promoções sobre o pedido - o que pode aumentar ou diminuir seu valor final. 
+</div>
 
 ## Período
 
@@ -152,7 +154,7 @@ Além de aplicar filtros, também é possível realizar as ações abaixo:
 
 ## Menu Exibições
 
-![Sales perf update PT](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
+![Sales perf update PT](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
 
 A Performance de Vendas permite customizar o dashboard aplicando diferentes filtros e selecionando as métricas que aparecerão no gráfico e na lista. Para facilitar sua exploração de dados no dia a dia, criamos as Exibições, que gravam os filtros e métricas aplicados na página para sua visualização direta. É possível salvar, editar e compartilhar visualizações distintas do dashboard. A página já vem com as seguintes Exibições configuradas por default:
 
@@ -212,7 +214,7 @@ A lista representa as métricas e filtros aplicados no gráfico em formato de ta
 
 <div class="alert alert-info">
 Note que as métricas <em>Ticket médio</em> e <em>Itens por pedido</em> não terão visualização Percentual ou Representativa disponíveis, já que são métricas calculadas dividindo outras, e a soma de todas as partes de cada uma não é igual ao Total.
-  </div>
+</div>
 
 ### Exportar dados
 
diff --git a/docs/tutorials/pt/scheduled-delivery.md b/docs/tutorials/pt/scheduled-delivery.md
index d0781e46a..6e1463d56 100644
--- a/docs/tutorials/pt/scheduled-delivery.md
+++ b/docs/tutorials/pt/scheduled-delivery.md
@@ -3,8 +3,8 @@ title: 'Entrega agendada'
 id: 22g3HAVCGLFiU7xugShOBi
 status: PUBLISHED
 createdAt: 2021-04-19T13:26:44.564Z
-updatedAt: 2021-10-27T16:49:43.778Z
-publishedAt: 2021-10-27T16:49:43.778Z
+updatedAt: 2024-03-25T19:12:45.519Z
+publishedAt: 2024-03-25T19:12:45.519Z
 firstPublishedAt: 2021-05-24T17:01:23.885Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,16 +15,20 @@ legacySlug: entrega-agendada, como-funciona-a-entrega-agendada
 subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 ---
 
-
 A funcionalidade de entrega agendada permite a você definir períodos de entrega para que o consumidor possa escolher o melhor dia e horário para receber o produto comprado.
 
 Os períodos de entrega que ficam disponíveis para os consumidores são chamados de janelas de entrega e estão diretamente relacionados às Políticas de Envio da sua loja. Nesse sentido, ao oferecer entregas agendadas, você precisa considerar se a política de envio oferece este serviço.
 
 Caso a política de envio ofereça o serviço, você pode habilitar a entrega agendada configurando as janelas de entrega e definindo a capacidade de realização das entregas para cada janela de entrega, caso desejar.A habilitação da entrega agendada é feita através do campo __Entrega Agendada__ presente na tela de criação ou edição de Política de Envio. 
 
+<div class="alert alert-warning">
+Para que a <a href="https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> e a <a href="https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidade de entrega</a> funcionem corretamente, você deve observar que:<p><ul><li>A soma {<a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID da política de envio} não pode exceder 60 caracteres.</li><li>Não se deve utilizar espaçamento no ID de <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">políticas de envio</a>.</li></ul></p>
+</div>
+
 Uma vez habilitada a Entrega Agendada, você pode configurar os campos que determinarão como ela funcionará. Tais campos definem o [tempo máximo de entrega](#tempo-maximo-de-entrega), o [período de entrega](#periodo-de-entrega) e o [limite da capacidade de entrega](#capacidade-de-entrega).
 
-Leia o artigo [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) para saber como criar uma nova política. 
+Leia o artigo [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) para saber como criar uma nova política.
+
 ## Tempo máximo de entrega
 
 O tempo máximo de entrega é o maior período de tempo que a política de envio usa para realizar uma entrega  desde a confirmação do pedido até a  confirmação da entrega. Ele é configurado através do campo `Tempo máximo de entrega` que está localizado na tela de entrega agendada na qual você definirá a quantidade de dias que compõem o tempo máximo de entrega.
diff --git a/docs/tutorials/pt/scheduling-features-for-special-events.md b/docs/tutorials/pt/scheduling-features-for-special-events.md
index a92fdc752..30612d420 100644
--- a/docs/tutorials/pt/scheduling-features-for-special-events.md
+++ b/docs/tutorials/pt/scheduling-features-for-special-events.md
@@ -70,7 +70,7 @@ Para agendar um conteúdo da sua loja, siga os passos abaixo:
 3. Use o campo URL no canto superior para navegar até a página que exibe o bloco cujo conteúdo será sobrescrito.
 4. Selecione o bloco para o qual deseja criar um novo conteúdo. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface](https://images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
+![seta-interface](//images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
 
 5. Clique em `Configurações` no canto superior direito.
 6. Clique no botão `Novo conteúdo`.
diff --git a/docs/tutorials/pt/search-behavior.md b/docs/tutorials/pt/search-behavior.md
new file mode 100644
index 000000000..60cd47ceb
--- /dev/null
+++ b/docs/tutorials/pt/search-behavior.md
@@ -0,0 +1,134 @@
+---
+title: 'Comportamento da busca'
+id: B9o3JbV6utAinBJ1ETujs
+status: PUBLISHED
+createdAt: 2024-06-27T17:30:43.356Z
+updatedAt: 2024-06-27T17:33:21.153Z
+publishedAt: 2024-06-27T17:33:21.153Z
+firstPublishedAt: 2024-06-27T17:33:21.153Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: comportamento-da-busca
+locale: pt
+legacySlug: comportamento-da-busca
+subcategory: 30Kdgc6wJkMWgcXLB8mGr7
+---
+
+O Motor de Busca é o centro da inteligência do VTEX Intelligent Search. Ele interpreta o termo buscado e apresenta a listagem filtrada e ordenada de produtos. Essa ferramenta possibilita uma pesquisa mais objetiva, por meio de indexação e tratamento dos dados do catálogo.
+
+Essa funcionalidade é padrão do VTEX Intelligent Search e atende a maioria dos cenários. Contudo, o Motor de Busca também apresenta alguns ajustes para que o resultado da busca seja aperfeiçoado. Neste guia, apresentamos:
+
+* [Comportamento padrão da busca](#comportamento-padrão-da-busca)
+* [Configurações para o comportamento da busca](#configuracoes-para-o-comportamento-da-busca)
+* [Formas alternativas de busca](#formas-alternativas-de-busca)
+
+## Comportamento padrão da busca
+
+A seguir, apresentamos características do comportamento padrão do Intelligent Search.
+
+### Autocorreção
+
+O usuário pode cometer erros ortográficos ao realizar uma busca. É função da ferramenta interpretar esses erros e apresentar como resultados produtos que se aproximem da pesquisa realizada.
+
+Para isso, o Motor de Busca tenta corrigir o que o usuário digitou de acordo com os itens registrados no Catálogo. Para cada termo pesquisado, uma quantidade específica de caracteres errados é permitida. Essa quantidade de erros aceitos é chamada de _fuzzy_.
+
+O _fuzzy_ varia de acordo com o tamanho do termo pesquisado. Por padrão, caso o termo tenha de 3 a 5 caracteres, o _fuzzy_ aplicado será 1, ou seja, é permitido errar 1 caractere. Para termos de 6 caracteres ou mais, o _fuzzy_ aplicado será 2.
+
+Os erros previstos considerando *fuzzy* = 1 são:
+
+* Inserir 1 caractere a mais.
+* Remover 1 caractere.
+* Trocar 1 caractere.
+* Trocar 2 caracteres que estiverem lado a lado.
+
+Exemplo: suponha que um cliente queira pesquisar pelo termo `bola`. Seguindo a configuração padrão (*fuzzy* = 1 para termos de 3 a 5 caracteres), o Motor de Busca vai apresentar o resultado `bola` para qualquer busca que contenha os erros aceitos, como:
+
+* `bolha` (inserir 1 caractere a mais)
+* `boa` (remover 1 caractere)
+* `bora` (trocar 1 caractere)
+* `obla` (trocar 2 caracteres que ficam um do lado do outro entre eles)
+
+<div class ="alert alert-info">
+	<p>Espaços em branco não são considerados no <em>fuzzy</em>, então <code>base ball</code> não será corrigido para <code>baseball</code>, por exemplo. Recomendamos o uso de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinônimos</a> para esses casos.</p>
+</div>
+
+### Resultado mínimo
+
+A quantidade mínima de resultados exibidos a partir de qualquer busca realizada é 1. Em qualquer busca, se o número mínimo de resultados não for atingido, a [autocorreção](#autocorrecao) é aplicada.
+
+Em uma busca com múltiplos termos, ocorre a lógica a seguir:
+
+1. Se o resultado mínimo não for atingido mesmo com a autocorreção inicial, a busca passa a incluir resultados mais abrangentes, que apresentam qualquer um dos termos pesquisados. Por exemplo, quando um usuário pesquisa por "tenis nike", mas o catálogo não possui nenhum produto com esse nome, a busca pode apresentar como resultado um produto com apenas o termo "tenis" no nome.
+2. Se a busca abrangente não apresentar o resultado mínimo, ela será repetida aplicando a autocorreção novamente a cada um dos termos.
+
+<div class= "alert alert-warning">
+<p>Buscas com múltiplos termos são mais eficientes quando o cliente ordena os resultados por relevância, já que elas podem ter um número maior de resultados além do contexto que foi buscado. Na ordenação por relevância, ainda priorizam-se os itens relacionados aos múltiplos termos. Porém, ao aplicar outras ordenações, como preço ou mais vendidos, a ordem dos resultados depende desses valores numéricos e não necessariamente prioriza itens que contêm mais palavras dos termos de busca.</p>
+</div>
+
+### Limite de paginação
+
+O VTEX Intelligent Search limita o resultado de busca a 50 páginas. Esse limite incentiva o uso de filtros, permitindo uma navegação mais relevante e focada para o usuário.
+
+## Configurações para o comportamento da busca
+
+Há um conjunto de configurações que alteram a listagem e a ordenação de produtos exibidos no resultado de busca. Nas seções a seguir, você verá as principais definições que afetam o comportamento da busca.
+
+### Definição de campos pesquisáveis
+
+Determina quais informações de produto são pesquisáveis. A partir da configuração, toda pesquisa realizada na barra de busca verifica o conteúdo desses campos para gerar resultados de busca. Confira a tabela a seguir para entender quais são as informações pesquisáveis por padrão e as demais opções de configuração:
+
+| Informações | Configuração |
+| - | - |
+| Nome do produto, marca, ID do produto (`ProductID`), código de referência do produto (`ProductRefID`), ID do SKU (`SKUID`), código de referência do SKU (`SKURefID`) e EAN | Essas informações são pesquisáveis por **padrão** no VTEX Intelligent Search. Para remover alguma delas, entre em contato com o nosso [Suporte](https://help.vtex.com/support?/cultureInfo=en-us). |
+| Especificações de produto e de SKU | Para incluir as especificações desejadas como campos pesquisáveis, é preciso configurar a opção **Especificações pesquisáveis** no Admin VTEX, em **Intelligent Search** > **Configurações da busca**.<br /><br /> Por exemplo, se uma camisa não tiver a cor no nome do produto ou do SKU, por padrão, o Intelligent Search não identifica esse atributo em uma pesquisa por "camisa azul", trazendo como resultado camisas de diversas cores. Contudo, se a especificação de cor estiver configurada como pesquisável, a busca consegue trazer camisas azuis nas primeiras posições.<br /><br /> Para mais detalhes sobre a definição de especificações pesquisáveis, acesse o guia [Configurações da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#configuracoes-gerais). Saiba mais sobre especificações em [Especificações de produto e de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP). |
+| Código do fabricante (`ManufactureID`) | Entre em contato com o nosso [Suporte](https://help.vtex.com/support?/cultureInfo=en-us) para definir esse campo como pesquisável. | 
+
+_Exemplo_: foi configurado que a especificação "cor" é pesquisável e o produto está cadastrado com o nome "Tênis Nike Total 90" e com a cor "preta". Se um cliente pesquisar por "Tenis Preto", a ferramenta retornará produtos que possuem o termo "tenis" e cor "preta" no topo do resultado de busca.
+
+É possível buscar por caracteres especiais (`-` e `/`) para encontrar um produto.
+
+<div class ="alert alert-warning">
+	<p>A escolha dos campos de busca afeta as possibilidades das <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">Regras de merchandising</a>, pois apenas campos pesquisáveis podem ser utilizados para configurar as regras. Por exemplo, ao definir somente o campo <strong><code>SKUID</code> </strong>como pesquisável, não será possível promover um <strong><code>ProductID</code> </strong>ou um <strong><code>ProductRefID</code> </strong>utilizando Regras de merchandising.</p>
+</div>
+
+### Definição e ordenação de campos de filtro
+
+Em todos os resultados de busca são apresentados filtros que podem ser selecionados pelo usuário. Por padrão, alguns filtros são pré-definidos, mas é possível criar outros de acordo com a necessidade da loja. Outro ponto customizável é a ordem de visualização. Exemplo: em uma lista de resultados de busca, podem existir os filtros de Preço, Categorias e Marca.
+
+### Configuração de relevância
+
+A relevância é a funcionalidade que define a ordem dos produtos no resultado de busca. Essa configuração permite atribuir pesos e priorizar determinados critérios utilizados pelo Motor de Busca, como popularidade, data de lançamento do produto e participação em promoções, por exemplo. A relevância de um produto é composta pela combinação dos pesos e prioridades definidos por cada lojista.
+
+_Exemplo_: um lojista configurou que o critério Promoção possui uma relevância maior que outros critérios. Dessa forma, quando o cliente pesquisa pelo termo “camiseta” na busca interna da loja, as camisetas incluídas em promoções tendem a aparecer primeiro nos resultados, dependendo dos pesos atribuídos aos outros critérios.
+
+Para mais informações sobre como personalizar a ordenação dos resultados de acordo com as necessidades da sua loja, leia o artigo [Configuração de relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
+
+<div class ="alert alert-info">
+	<p>Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções. Usando o comando <code>map=productClusterIds</code>, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar <code>productClusterNames</code>, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search.</p>
+</div>
+
+## Formas alternativas de busca
+
+É possível buscar pelo ID de um ou mais itens na barra de busca ou adicionando parâmetros de busca (*query*) na URL da loja.
+
+### Match parcial
+
+Ao digitar somente os primeiros dígitos exatos do ID do produto (`ProductID`), código de referência do produto (`ProductRefID`), ID do SKU (`SKUID`), código de referência do SKU (`SKURefID`) ou EAN na barra de busca, o Intelligent Search fará o match parcial com produtos e SKUs ativos na loja, incluindo-os nos resultados da busca.
+
+Por exemplo, se o ID do produto for `123456789` e a busca for `123`, esse produto aparecerá entre os resultados. Porém, se a busca for `234`, sem algum dos primeiros dígitos do ID, esse produto não aparecerá.
+
+### URL
+
+Para buscar a partir da URL da sua loja, adicione parâmetros de busca (*query*) no final da URL da loja, respeitando uma das estruturas a seguir:
+
+- Exemplo para pesquisa de um item: `[endereço da conta]/[tipo do id]:[id_1]?q=[tipo do id]&map=ft`
+- Exemplo para pesquisa de lista de itens: `[endereço da conta]/[tipo do id]:[id_1];[id_2];[id_3]?q=[tipo do id]:[id_1];[id_2];[id_3]&map=ft`
+
+Os possíveis tipos de valores para o campo tipo do ID são `product.id`, `sku.id`,`sku.ean`, `sku.reference` ou `id` (ProductID, ProductRefID, SKUID, SKURefID e EAN). Importante destacar que todos os IDs buscados devem pertencer ao mesmo tipo. 
+
+  - **Busca por SKU ID:** `?q=sku.id:<id>` ou `?q=sku:<id>`
+  - **Busca por EAN:** `?q=sku.ean:<id> `
+  - **Busca por reference ID:** `?q=sku.reference:<id>` 
+  - **Busca por slug:** `?q=product.link:<link>` 
+  - **Busca por product ID:** `?q=product:<id>` ou `?q=product.id:<id>`
diff --git a/docs/tutorials/pt/search-configuration.md b/docs/tutorials/pt/search-configuration.md
new file mode 100644
index 000000000..046915015
--- /dev/null
+++ b/docs/tutorials/pt/search-configuration.md
@@ -0,0 +1,53 @@
+---
+title: 'Configuração da busca'
+id: 1yNCDwz0k77ovSGqkTbZMv
+status: PUBLISHED
+createdAt: 2024-06-17T14:08:59.824Z
+updatedAt: 2024-06-17T14:10:20.364Z
+publishedAt: 2024-06-17T14:10:20.364Z
+firstPublishedAt: 2024-06-17T14:10:20.364Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: configuracao-da-busca
+locale: pt
+legacySlug: configuracao-da-busca
+subcategory: 1EmKjP83dy0RWD9GzZkYsG
+---
+
+A página **Configuração da busca** compreende os ajustes globais do VTEX Intelligent Search. Para acessá-la no Admin VTEX, entre em **Configurações da loja > Intelligent Search > Configuração da busca**. Ela consiste em duas seções: [Configurações gerais](#configuracoes-gerais) e [Configurações de filtros](#configuracoes-de-filtros).
+
+## Configurações gerais
+
+As configurações gerais apresentam as opções a seguir, relacionadas a [especificações de produtos e de SKUs](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP):
+
+* **Use as especificações de SKU para exibir produtos individuais nos resultados da pesquisa**: define quais especificações vão separar os SKUs no resultado de busca.
+
+    Digamos que você tenha um produto com as cores vermelho e azul como SKUs. Se você selecionar o atributo "cor" neste campo, o resultado da pesquisa retornará dois produtos (um azul e outro vermelho) em vez de apenas um.
+
+    Para adicionar uma especificação, clique na barra da funcionalidade e selecione a especificação desejada.
+
+    Confira o guia [Separar SKUs por especificação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5uVxuWxTA8VvLX3G8UCcUE) para mais detalhes sobre o comportamento dessa configuração. 
+
+* **Especificações pesquisáveis:** determina quais especificações terão valores pesquisáveis na busca.
+
+    Por exemplo, se uma camisa não tiver a cor no nome do produto ou do SKU, por padrão, o Intelligent Search não identifica esse atributo em uma pesquisa por "camisa azul", trazendo como resultado camisas de diversas cores. Contudo, se a especificação de cor estiver configurada como pesquisável, a busca consegue trazer camisas azuis nas primeiras posições.
+
+## Configurações de filtros
+
+As configurações de filtros apresentam ajustes relacionados aos filtros exibidos para os clientes da sua loja durante a busca:
+
+![Configurações de filtros](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
+
+* **Ordenação dos filtros:** ordem em que os filtros serão exibidos na loja. Caso não tenha nenhum filtro selecionado na área, a ordem padrão é alfabética.
+
+    Para adicionar um filtro, clique em `Adicionar`, selecione o filtro e clique em `Salvar` para concluir.
+
+    Você pode alterar a ordenação arrastando o ícone de três barras <i class="fas fa-grip-vertical"></i> em cada filtro para a posição desejada.
+
+    Para deletar um filtro, clique no ícone de lixeira <i class="fas fa-trash-alt"></i>.
+
+* **Ocultar filtros:** seleção que permite que determinados filtros não sejam exibidos na loja. Para ocultar um filtro, clique no campo e, em seguida, clique no nome do filtro. 
+
+    Para voltar a exibir um filtro, clique no X ao lado do nome dele. Se deseja voltar a exibir todos os filtros anteriormente ocultos, clique no X do lado direito do campo.
+
diff --git a/docs/tutorials/pt/searching-for-old-orders.md b/docs/tutorials/pt/searching-for-old-orders.md
index 952c1b381..2e986340c 100644
--- a/docs/tutorials/pt/searching-for-old-orders.md
+++ b/docs/tutorials/pt/searching-for-old-orders.md
@@ -19,7 +19,7 @@ Para buscar seus pedidos antigos, siga os passos abaixo:
 
 1. No menu lateral do admin, clique em __Gerenciamento de Pedidos__
 2. Clique em __Todos os pedidos__
-3. Clique no botão de filtro ![filter](https://images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
+3. Clique no botão de filtro ![filter](//images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
 4. Escolha um filtro *por período*: __Data de faturamento__, __Data do pedido__, __Data de autorização__ ou **Data de entrega**
 5. No filtro escolhido, clique no __ícone de calendário__, ao lado do texto __Todas as datas__
 6. Escolha uma data/hora inicial e uma data/hora final
diff --git a/docs/tutorials/pt/searching-for-transactions-on-payments.md b/docs/tutorials/pt/searching-for-transactions-on-payments.md
index 6a6589a04..07a0a42dc 100644
--- a/docs/tutorials/pt/searching-for-transactions-on-payments.md
+++ b/docs/tutorials/pt/searching-for-transactions-on-payments.md
@@ -35,13 +35,13 @@ Para voltar à listagem original das transações, basta apagar o valor anterior
 
 Ao clicar em um pedido no Gerenciamento de Pedidos, você vai para a página que traz um resumo sobre ele. As principais informações estão lá, mas você pode ver ainda mais detalhes se clicar no link _Detalhes da transação_:
 
-![Link transação OMS (PT)](https://images.ctfassets.net/alneenqid6w5/4HbLRjdyNyusgoSYAUmIee/c26af370c7be5288ab100d87a30d34ee/Link_transa____o_OMS__PT_.png)
+![Link transação OMS (PT)](//images.ctfassets.net/alneenqid6w5/4HbLRjdyNyusgoSYAUmIee/c26af370c7be5288ab100d87a30d34ee/Link_transa____o_OMS__PT_.png)
 
 ## TID do Pagamento e ID do Pagamento
 
 A busca utilizando esses códigos necessariamente precisa conter todos os dígitos, ou sua busca retornará vazia. Veja abaixo como encontrá-lo:
 
-![Códigos PT](https://images.ctfassets.net/alneenqid6w5/6cKptwp1XqOYs6umGEeW4m/44436d8afbf8055d10aeddd53f83f3ca/C__digos_PT.png)
+![Códigos PT](//images.ctfassets.net/alneenqid6w5/6cKptwp1XqOYs6umGEeW4m/44436d8afbf8055d10aeddd53f83f3ca/C__digos_PT.png)
 
 Estes valores, dentro do detalhe da transação representarão a comunicação junto ao respectivo conector. Nos [eventos da transação](/pt/tutorial/como-visualizar-detalhes-do-pedido) será possível validar cada contato feito.
 
diff --git a/docs/tutorials/pt/security-certificate-ssl.md b/docs/tutorials/pt/security-certificate-ssl.md
new file mode 100644
index 000000000..20f8ab94b
--- /dev/null
+++ b/docs/tutorials/pt/security-certificate-ssl.md
@@ -0,0 +1,26 @@
+---
+title: 'Certificado de segurança (SSL)'
+id: tutorials_1308
+status: PUBLISHED
+createdAt: 2017-04-27T21:56:41.946Z
+updatedAt: 2023-11-16T17:44:04.092Z
+publishedAt: 2023-11-16T17:44:04.092Z
+firstPublishedAt: 2017-04-27T23:03:50.121Z
+contentType: tutorial
+productTeam: Identity
+author: authors_84
+slug: certificado-de-seguranca-ssl
+locale: pt
+legacySlug: certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar
+subcategory: 2TNXiKzLZOPxjMTyGiEeJu
+---
+
+O SSL (Secure Socket Layer) é um protocolo desenvolvido para elevar a segurança dos dados transmitidos pela internet. As conexões via SSL são particularmente recomendadas para envio de informações como números de cartão de crédito, senhas e qualquer outra informação sigilosa via internet.
+
+Sempre que você acessa uma página segura, isto é, protegida por um certificado SSL, é apresentada uma chave ou um cadeado na barra de status para indicar a comunicação segura. Os certificados tradicionais exigem que você clique na chave ou cadeado para ter acesso às informações do detentor do certificado SSL.
+
+Não é necessário solicitar a compra do certificado SSL. A VTEX gera um certificado SSL para a sua loja e garante sua renovação automática. O certificado é emitido via Let’s Encrypt e sua criação é responsabilidade da VTEX no [momento do Go-Live da loja](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
+
+<div class="alert alert-warning">
+<p>Não recomendamos a instalação de outros certificados. No entanto, caso seja necessário, faça a solicitação para o nosso <a href="https://help.vtex.com/pt/support">suporte</a>.</p>
+</div>
diff --git a/docs/tutorials/pt/security-education-and-awareness.md b/docs/tutorials/pt/security-education-and-awareness.md
index 27c2afbd7..250b084ab 100644
--- a/docs/tutorials/pt/security-education-and-awareness.md
+++ b/docs/tutorials/pt/security-education-and-awareness.md
@@ -3,7 +3,7 @@ title: 'Educação e conscientização sobre segurança'
 id: 5t6HaGHiHFVrCIvePJKkV6
 status: DRAFT
 createdAt: 2022-05-26T13:50:41.046Z
-updatedAt: 2022-08-18T20:43:54.577Z
+updatedAt: 2023-07-19T23:57:15.726Z
 publishedAt: 
 firstPublishedAt: 
 contentType: tutorial
@@ -15,4 +15,4 @@ legacySlug: educacao-e-conscientizacao-sobre-seguranca
 subcategory: 
 ---
 
-
+test
diff --git a/docs/tutorials/pt/security-monitor.md b/docs/tutorials/pt/security-monitor.md
new file mode 100644
index 000000000..53bc0c8a6
--- /dev/null
+++ b/docs/tutorials/pt/security-monitor.md
@@ -0,0 +1,131 @@
+---
+title: 'Security Monitor'
+id: 5LOVNLrrtmgSj99pM1NS4x
+status: PUBLISHED
+createdAt: 2024-04-25T00:42:30.944Z
+updatedAt: 2024-04-25T03:01:13.448Z
+publishedAt: 2024-04-25T03:01:13.448Z
+firstPublishedAt: 2024-04-25T02:41:44.798Z
+contentType: tutorial
+productTeam: Identity
+author: 1malnhMX0vPThsaJaZMYm2
+slug: security-monitor
+locale: pt
+legacySlug: security-monitor
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidade faz parte do produto <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+O Security Monitor é um dashboard que auxilia lojistas a identificarem e gerenciarem riscos potenciais em sua conta em tempo real. A ferramenta identifica e notifica lojistas por email sobre riscos relacionados a configurações e comportamento de usuários administrativos, possibilitando ações preventivas contra vulnerabilidades de segurança.
+
+Para acessar o dashboard, siga os passos abaixo:
+
+1. No Admin VTEX, acesse **Dashboards**, ou digite **Dashboards** na barra de busca.
+2. Em **Security Monitor**, clique em **Security Monitor Dashboard**.
+
+![1-security-monitor-pt](//images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/b0355765dafddea697f6cd29739be2fa/1-security-monitor-pt.png)
+
+O Security Monitor apresenta as descobertas em três abas, divididas por status:
+
+* [Abertas](#abertas)
+* [Silenciadas](#silenciadas)
+* [Fechadas](#fechadas)
+
+Em todas as abas, é possível realizar as seguintes ações:
+
+* [Buscar descobertas](#buscar-descobertas)
+* [Filtrar descobertas por tipo](#filtrar-descobertas-por-tipo)
+* [Editar configurações de notificações](#editar-configuracoes-de-notificacoes)
+
+A seguir, confira informações específicas sobre as informações disponíveis em cada aba e as ações relacionadas.
+
+## Abertas
+
+A aba **Abertas** apresenta as ameaças identificadas pelo Security Monitor que ainda não foram gerenciadas ou silenciadas.
+
+A barra superior indica o total de descobertas e a quantidade de ameaças por nível de severidade (alta, média ou baixa).
+
+![2-findings-pt](//images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/1d9ec105165551da7e470f3be5aa30ec/2-findings-pt.png)
+
+A aba apresenta a listagem completa de descobertas abertas em uma tabela, da mais recente para a mais antiga: 
+
+| Colunas | Descrição |
+| --- | --- |
+| Descoberta | Email de usuário ou chave de aplicação relacionada à descoberta. |
+| Tipo | Tipo de descoberta detectada:<br/><ul><li><strong>Chaves de App antigas:</strong> <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">chaves de aplicação</a> que foram criadas há mais de 6 meses.</li><li><strong>Super Admin Excessivos:</strong> usuários ou chaves de aplicação com o <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">perfil de acesso</a> <strong>Owner (Admin Super)</strong>.</li><li><strong>Chaves de App Vazadas:</strong> <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">chaves de aplicação</a> que foram expostas na web, encontradas pelo time de Segurança da VTEX.</li><li><strong>Usuários Inativos:</strong> usuário que não acessou o Admin nos últimos 30 dias.</li></ul> |
+| Detectada | Data em que a descoberta foi detectada. |
+| Sensor | Sensor que detectou a ameaça: <br/><ul><li><strong>VTEX Identity</strong></li></ul> |
+| Severidade | Nível de severidade da ameaça, determinado pelo impacto ou potencial risco: <br/><ul><li><strong>Alta</strong></li> <li><strong>Média</strong></li><li><strong>Baixa</strong></li></ul> |
+| Menu de ações ⋮ | Menu de ações possíveis para a descoberta: <br/><ul><li><a href="#gerenciar-descoberta" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Gerenciar</a></li><li><a href="#silenciar-descoberta" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Silenciar</a></li></ul> |
+
+### Gerenciar descoberta
+
+Para gerenciar uma descoberta, siga as instruções abaixo:
+
+1. Na linha da descoberta, clique no menu ⋮ .
+2. Clique em `Gerenciar`.
+
+    Você será conduzido(a) à tela de **Usuários** no **Gerenciamento da conta** para editar os perfis de acesso associados ao usuário ou à chave de aplicação em questão.
+
+### Silenciar descoberta
+
+Para mover uma descoberta para a aba **Silenciadas**, ou seja, removê-la temporariamente da aba **Abertas**, siga as instruções abaixo:
+
+1. Na linha da descoberta, clique no menu ⋮ .
+2. Clique em `Silenciar`.
+3. Escolha o período de tempo em dias para manter essa descoberta na aba **Silenciadas**. As opções disponíveis são: **7**, **90** ou **120** dias.
+4. Clique em `Silenciar`.
+
+![3-snooze-finding-pt](//images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/8a2ba4dbd793fcfde04b219947bba6f4/3-snooze-finding-pt.png)
+
+## Silenciadas
+
+A aba **Silenciadas** apresenta a listagem de descobertas que foram silenciadas em uma tabela, com as mesmas informações descritas na aba [Abertas](#abertas).
+
+Na aba **Silenciadas**, o menu de ações na linha de cada descoberta exibe apenas a opção `Alertar`, que permite reverter a ação de silenciar e fazer com que a descoberta retorne para a aba **Abertas**.
+
+## Fechadas
+
+A aba **Fechadas** contém a listagem de descobertas que já foram gerenciadas, ou seja, estão encerradas. Ela apresenta as seguintes informações em uma tabela: 
+
+| Colunas | Descrição |
+| --- | --- |
+| Descoberta | Email de usuário ou chave de aplicação relacionada à descoberta. |
+| Tipo | Tipo de descoberta detectada:<br/><ul><li><strong>Chaves de App antigas:</strong> <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">chaves de aplicação</a> que foram criadas há mais de 6 meses.</li><li><strong>Super Admin Excessivos:</strong> usuários ou chaves de aplicação com o <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">perfil de acesso</a> <strong>Owner (Admin Super)</strong>.</li><li><strong>Chaves de App Vazadas:</strong> <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet" rel="noopener noreferrer" target="_self" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">chaves de aplicação</a> que foram expostas na web, encontradas pelo time de Segurança da VTEX.</li><li><strong>Usuários Inativos:</strong> usuário que não acessou o Admin nos últimos 30 dias.</li></ul> |
+| Detectada | Data em que a descoberta foi detectada. |
+| Fechada | Data em que a descoberta foi fechada. |
+| Fechada por | Indica que a descoberta foi fechada automaticamente, após ser gerenciada por um usuário administrativo. |
+| Severidade | Nível de severidade da ameaça, determinado pelo impacto ou potencial risco: <br/><ul><li><strong>Alta</strong></li> <li><strong>Média</strong></li><li><strong>Baixa</strong></li></ul> |
+
+## Buscar descobertas
+
+Na barra de busca, digite o email de usuário ou o nome da chave de aplicação para encontrar descobertas relacionadas.
+
+## Filtrar descobertas por tipo
+
+Ao clicar em <i class="fas fa-chevron-down"></i> `Tipo`, você pode escolher um dos tipos de descoberta para filtrar os resultados exibidos na listagem. Clique em `Aplicar` para confirmar o filtro escolhido e a listagem será atualizada.
+
+![4-filter-findings-pt](//images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/afdf81607e3076ac05f71515b02e742a/4-filter-findings-pt.png)
+
+## Editar configurações de notificações
+
+Para editar os usuários administrativos que vão receber notificações em caso de descobertas, siga os passos abaixo:
+
+1. Clique no botão de engrenagem no canto superior direito da tela. 
+2. Digite o email do usuário a ser notificado e tecle `Enter`. Repita este passo para quantos usuários forem necessários.
+
+   Para remover um usuário, clique no `X` ao lado do email relacionado.
+
+3. Clique em `Salvar`.
+
+![5-edit-notifications-pt](//images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/db1c1b11d46b98b05ab9b9091db65fa5/5-edit-notifications-pt__1_.png)
+
+## Saiba mais
+
+* [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh)
+* [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc)
+* [Usuários](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512)
+* [Chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet)
diff --git a/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md b/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md
index 9c95bbd3d..addfd792b 100644
--- a/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md
+++ b/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md
@@ -27,9 +27,9 @@ Com o estoque já cadastrado, siga os passos a seguir:
 2. No módulo **Estoque & Entrega**, clique em **Estratégia de Envio**.
 3. Em Estratégia de Envio, selecione a aba Estoques e copie o ID do estoque que você deseja utilizar. 
 4. Vá para o  módulo **Marketplace**, selecione a opção **Integrações** e clique em **Configurações**.
-5. Na integração Mercado Livre, clique na engrenagem<img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
+5. Na integração Mercado Livre, clique na engrenagem<img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/39oIVAfBAL5iIPqR5mrg2y/f1943060e88dd71804dcc7844a71c1cd/engrenagem.JPG" />.
 6. Selecione a opção **Editar configuração**.
 7. Insira o ID do estoque selecionado no campo **Armazém Mercado Full**.
 8. Clique em **Salvar Configuração**.
 
-![Início (3)](https://images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
+![Início (3)](//images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
diff --git a/docs/tutorials/pt/seletivo.md b/docs/tutorials/pt/seletivo.md
index da798088f..69b9b98be 100644
--- a/docs/tutorials/pt/seletivo.md
+++ b/docs/tutorials/pt/seletivo.md
@@ -19,41 +19,41 @@ No modo Seletivo, cada cliente que clicar no link será direcionado para uma tel
 
 Para criar um atendimento seletivo, acesse: _**Organizar > Seletivo**_ 
 
-![Seletivo 1](https://images.ctfassets.net/alneenqid6w5/5aqMlFa9eCrKjp4Rc6VEZF/fbb0948a7381804f786f3dd2dc501af4/Screenshot_2022-08-29_at_14-27-26_Seletivo.png)
+![Seletivo 1](//images.ctfassets.net/alneenqid6w5/5aqMlFa9eCrKjp4Rc6VEZF/fbb0948a7381804f786f3dd2dc501af4/Screenshot_2022-08-29_at_14-27-26_Seletivo.png)
 
 **IMPORTANTE**:  Antes de começar, você já deverá ter criado um link para cada número de WhatsApp que deseja adicionar na central. Se ainda não fez isso, é só [acessar esse link.](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB)
 
 Clique em _**“Novo”.**_
 
-![Seletivo 2](https://images.ctfassets.net/alneenqid6w5/5gwGt7VFr7HoZRu4z4P3Fm/1db890b971e8dca053e7933f5f2670ba/Screenshot_2022-08-29_at_14-27-30_Seletivo.png)
+![Seletivo 2](//images.ctfassets.net/alneenqid6w5/5gwGt7VFr7HoZRu4z4P3Fm/1db890b971e8dca053e7933f5f2670ba/Screenshot_2022-08-29_at_14-27-30_Seletivo.png)
 
 Defina o link principal. 
 
 Em **Link Âncora**, como o próprio nome já diz, você irá selecionar o link principal da central. Esse é o link que você irá divulgar, será o link responsável por fazer a ligação com os demais atendentes.
 
-![Seletivo 3](https://images.ctfassets.net/alneenqid6w5/66tVW8yRNV93ovPLUdmDx/de491f10c1bf46f88283a7a88413d245/Screenshot_2022-08-29_at_14-27-34_Seletivo.png)
+![Seletivo 3](//images.ctfassets.net/alneenqid6w5/66tVW8yRNV93ovPLUdmDx/de491f10c1bf46f88283a7a88413d245/Screenshot_2022-08-29_at_14-27-34_Seletivo.png)
 
 Clique em **“Avançar**”.
 
 Em Links de **Seleção**,escolha quem serão os vendedores ou setores que irão participar da central. Clique em Adicionar , personalize as informações dos atendentes (título, descrição e foto) e selecione o link para cada participante da central.
 
-![Seletivo 4](https://images.ctfassets.net/alneenqid6w5/6CGgMpW1raNaPRl25knaQW/b191e79a7485244b7c045a3fd9828e05/Screenshot_2022-08-29_at_14-27-39_Seletivo.png)
+![Seletivo 4](//images.ctfassets.net/alneenqid6w5/6CGgMpW1raNaPRl25knaQW/b191e79a7485244b7c045a3fd9828e05/Screenshot_2022-08-29_at_14-27-39_Seletivo.png)
 
 Defina se os links ficarão em _**“Ordenação randômica”**_ ou seja, a sequência de links sempre irá mudar para cada acesso.
 
-![Seletivo 5](https://images.ctfassets.net/alneenqid6w5/1Az1uDyBgUIletuPjq7Zum/8065b8091e778b7affe31edda074b789/Screenshot_2022-08-29_at_14-27-43_Seletivo.png)
+![Seletivo 5](//images.ctfassets.net/alneenqid6w5/1Az1uDyBgUIletuPjq7Zum/8065b8091e778b7affe31edda074b789/Screenshot_2022-08-29_at_14-27-43_Seletivo.png)
 
 Clique em "_**Avançar"**_. 
 
 Defina o texto que irá aparecer na sua tela de seleção.
 
-![Seletivo 6](https://images.ctfassets.net/alneenqid6w5/3nQN1TbH980LDrPEIHjpVq/30f6e9e19c82f6d3f8eb2701ee4fcc64/Screenshot_2022-08-29_at_14-27-47_Seletivo.png)
+![Seletivo 6](//images.ctfassets.net/alneenqid6w5/3nQN1TbH980LDrPEIHjpVq/30f6e9e19c82f6d3f8eb2701ee4fcc64/Screenshot_2022-08-29_at_14-27-47_Seletivo.png)
 
 Clique no botão “_**Finalizar**_” para salvar seu atendimento seletivo. 
 
 Configure a aparência, você pode clicar no botão “_**Clique aqui**_” ou acessar  **Configurações > Minha conta > Aparência**
 
-![Seletivo 7](https://images.ctfassets.net/alneenqid6w5/575cQ08f4RMKj8YymWqGhY/1cf33469f22a684d3116d039f881ba4d/Screenshot_2022-08-29_at_14-28-01_Seletivo.png)
+![Seletivo 7](//images.ctfassets.net/alneenqid6w5/575cQ08f4RMKj8YymWqGhY/1cf33469f22a684d3116d039f881ba4d/Screenshot_2022-08-29_at_14-28-01_Seletivo.png)
 
 **Atenção:** Se você ir para a aparência e não salvar seu seletivo, você terá que refazer as opções. 
 
diff --git a/docs/tutorials/pt/seller-management.md b/docs/tutorials/pt/seller-management.md
index b64f34448..b07d3f6a9 100644
--- a/docs/tutorials/pt/seller-management.md
+++ b/docs/tutorials/pt/seller-management.md
@@ -17,7 +17,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 __Gerenciamento de Sellers__ é a página onde operadores de marketplace [adicionam sellers](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392), registram suas informações e administram seus status. A página inclui métricas de andamento da operação de marketplace. Também é possível aplicar filtros nos resultados da lista de sellers e agrupar sellers por meio da opção Grupos que permite filtrar resultados mais facilmente.  
 
-![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 ## Métricas
 A página apresenta métricas gerais dos sellers:
@@ -46,7 +46,7 @@ Com essa funcionalidade, lojistas otimizam cenários de acompanhamento da opera
 
 Grupos são criados manualmente ao Adicionar seller ou clicando em Gerenciar grupos e após criados é possível editar e excluir cada um deles.  
 
-![Gerenciamento de sellers](https://images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/cb37f601d4b9a096b0c1e94c03b90c11/gerenciamento_de_seller.png)  
+![Gerenciamento de sellers](//images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/cb37f601d4b9a096b0c1e94c03b90c11/gerenciamento_de_seller.png)  
 
 ## Gerenciar grupos  
 
diff --git a/docs/tutorials/pt/seller-monitoring.md b/docs/tutorials/pt/seller-monitoring.md
new file mode 100644
index 000000000..a6586853d
--- /dev/null
+++ b/docs/tutorials/pt/seller-monitoring.md
@@ -0,0 +1,64 @@
+---
+title: 'Monitoramento de seller'
+id: 3Gt3Zu7BPFAaTRRehi27ez
+status: DRAFT
+createdAt: 2023-07-18T19:35:09.684Z
+updatedAt: 2023-07-19T13:53:51.474Z
+publishedAt: 
+firstPublishedAt: 2023-07-18T19:55:46.688Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: monitoramento-de-seller
+locale: pt
+legacySlug: monitoramento-de-seller
+subcategory: 2xWRgEIlR2ookieEmm4KQu
+---
+
+O **Monitoramento de seller** é uma ferramenta do módulo [Gerenciamento de sellers](https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv) que permite ao marketplace medir o desempenho dos sellers que vendem através de sua loja. Para acessar essa página, em seu Admin VTEX vá em **Marketplace > Sellers > Gerenciamento > clique no botão Configur armétrica**. Na página inicial,você encontrará as seguintes seções
+
+- **Saúde da operação**: Nesta seção,estarão presentes os dados de todos os sellers que vendem em sua loja,incluindo:  
+
+    - Total de sellers ativos
+    - Tempo médio de faturamento  
+
+- **Oque está acontecendo**: Aqui você acompanhará os detalhes do resultado da métrica com a visão detalhada da infração que levou o seller ao status de ⚠ **Aceitável** ou ❌ **Insatisfatório**. Épossível filtrar por seller,clicando no botão (colocar o símbolo do botão) e selecionar somente os sellers desejados.
+
+![Monitoramento de seller](//images.ctfassets.net/alneenqid6w5/1a6BgbLPMxQzuSPLFGb7DM/5fa662c273968852081a0ef98f50c95d/monitoramento_de_seller.png)
+
+Ao clicar no botão **Ver pedidos,** abrirá um pop-up com o **ID do pedido**, **Valor** e o botão **Ver.**
+
+|**Campo**|**Descrição**|
+| - | - |
+|**ID do pedido**|Código gerado automaticamente para cadapedido realizado no marketplace.|
+|**Valor**|Tempo que aquele pedido está sem faturamento.|
+|**Ver**|Botão de direcionamento. Ao clicar nele o marketplace será direcionado para os detalhes daquele pedido no OMS.|
+
+Se esse for o seu primeiro acesso à ferramenta,será necessária a configuração da métrica de **Tempo de faturamento**, nela você definirá o tempo máximo e o tempo preferível para que os pedidos dos sellers sejam faturados. A seguir, veja como configurar.
+
+## Como configurar as métricas
+
+Para configurar, siga as instruções a seguir.
+
+1. Em seu Admin VTEX vá em **Marketplace > Sellers > Gerenciamento de sellers > Configurar métrica.**
+2. Clique em **Tempo de faturamento**, e preencha os campos que serão apresentados.
+3. Clique em **+ Adicionar Variação** e preencha os campos solicitados para configurar variações para um segmento ou grupo de sellers.
+4. Clique em **Salvar**.
+
+Ao clicar em **`Salvar`**, você receberá notificações no Admin acerca da performance dos sellers em sua operação e você terá visibilidade dos sellers que não estão atingindo os prazos esperados.
+
+|**Campo ( * Obrigatório)**|**Descrição**|
+| - | - |
+|**Valor limite***|Valor máximo definido para medir se o seller está dentro ou fora dos padrões do seu marketplace.|
+|**Segmentação***|Você irá definir quais sellers ou grupo de sellers serão afetados pelo valor definido em **Valor limite.**|
+|**Limite preferível**|Valor definido para alertar que o seller está se aproximando do **Valor limite.**|
+
+<div class ="alert alert-info"> Quando há variação configurada em uma métrica, a ordenação define a prioridade. Para casos em que só existe uma segmentação por grupo e outra por exceção, não existe conflito independente da ordenação. </div> 
+
+## Editando a métrica
+
+Após configurada, essa métrica pode ser editada. Para isso você deve seguir os passos a seguir:
+
+1. Clicar no botão **Editar métrica.**
+2. Altere os valores nos campos que serão apresentados.
+3. Clique no botão **Salvar**.
diff --git a/docs/tutorials/pt/seller-portal-creating-a-promotion.md b/docs/tutorials/pt/seller-portal-creating-a-promotion.md
new file mode 100644
index 000000000..cd46503bf
--- /dev/null
+++ b/docs/tutorials/pt/seller-portal-creating-a-promotion.md
@@ -0,0 +1,102 @@
+---
+title: 'Seller Portal: Criar uma promoção'
+id: kzNPEaiJE8EWkDzO9dbBI
+status: PUBLISHED
+createdAt: 2023-09-01T15:28:13.875Z
+updatedAt: 2023-11-16T18:06:30.499Z
+publishedAt: 2023-11-16T18:06:30.499Z
+firstPublishedAt: 2023-09-01T16:58:54.457Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: seller-portal-criar-uma-promocao
+locale: pt
+legacySlug: seller-portal-criar-uma-promocao
+subcategory: 4hisB47iAVZk4r3SEmMoG
+---
+
+Para criar uma nova promoção como seller no Seller Portal, siga o passo a passo abaixo.
+
+1. No Admin VTEX, acesse **Produtos > Promoções > Promoções **ou digite **Promoções **na barra de busca no topo da página.
+2. Clique em `Criar promoção.`
+3. Preencha as informações descritas em [Campos de cadastro da promoção](#campos-de-cadastro-da-promocao).
+4. Clique em `Salvar.`
+5. Revise as configurações da sua promoção antes de publicá-la.
+![seller-portal-promo-revisao-pt](//images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/b4bd761ce6c36f7165a88ca5ac46eae3/image.png)
+6. Depois de revisar as informações, clique em `Confirmar`.
+
+Feito isso, a promoção será ativada e aplicada na sua loja.
+
+<div class = "alert alert-info">
+As promoções que afetam os mesmos itens inseridos no carrinho são comparadas pelo seu valor de desconto. Nesse caso, o módulo de Promoções procura sempre aplicar a promoção mais vantajosa para o comprador.
+</div>
+
+## Campos de cadastro da promoção
+
+### Geral
+
+Nesta seção, você deve configurar as informações gerais da sua promoção.
+
+![seller-portal-promo-geral-pt](//images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/88a1a7946d0794d9168b3d3816adbb33/image.png)
+
+* **Nome:** nome da promoção.
+* **Status: **opção que define se a promoção está ativa <i class="fas-toggle-on"></i> ou inativa <i class="fas-toggle-off"></i>.
+* **Descrição:** descrição interna da promoção. O objetivo desse campo é que seja usado para comunicação interna na sua loja, a fim de deixar claro se a promoção é devido à alguma campanha, queima de estoque, etc.
+* **Data de início:** data de início da promoção. Pode ser usada uma data futura para que a promoção comece a ser aplicada no site. Caso seja configurada dessa forma, a promoção terá o status de **agendada** até que a data seja atingida. 
+* **Data de término:** data de término da promoção. Enquanto a data de término estiver válida, a promoção terá o status de ativa, e ao término da data definida o desconto será inativado automaticamente.
+* **Horário de início:** hora de início da promoção.
+* **Horário de término:** hora de término da promoção.
+
+### Tipo de desconto
+
+Seção que define o tipo e valor do desconto que será aplicado na promoção. Veja as opções de desconto a seguir:
+
+![seller-portal-promo-tipo-desconto-pt](//images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/9acedc88d86af0f0a2fa860d941ccfa7/image.png)
+
+#### Preço
+
+* **Percentual:** percentual de desconto que será concedido ao valor do produto.
+* **Preço máximo por item:** o preço máximo para cada item elegível da compra será o preço configurado acima. Essa opção só será aplicada nos produtos com preço maior do que o valor configurado nesta opção.
+
+#### Frete
+
+* **Frete grátis:** desconto do valor total do frete dos itens elegíveis para a promoção.
+* **Percentual:** percentual de desconto que será concedido ao valor do frete. 
+* **Frete máximo:** valor máximo que o frete poderá assumir. Caso exista um frete mais barato que o valor máximo configurado, será cobrado o frete de menor preço.
+
+### Produtos elegíveis
+
+Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
+
+![seller-portal-promo-produtos-elegiveis-pt](//images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/737ac93c123828fe3c335dcf067bf7e7/image.png)
+
+* **Todos os produtos:** aplica a promoção a todo o seu catálogo.
+* **Produtos que atendam a todas as seguintes regras:** limita a sua promoção a produtos específicos a partir das regras de seleção a seguir:
+  * **Produto, Categoria, Marca, SKU:** opção que define o critério de seleção de produtos.
+      * `É uma das`: inclui o critério de seleção de produtos.
+      * `Não é uma das`: exclui o critério de seleção de produtos.
+
+Após definir os critérios de seleção, digite o nome dos itens a serem incluidos ou excluidos.
+
+Para adicionar mais de uma regra de seleção, clique em `+ Adicionar regra`. Se mais de uma regra for configurada, apenas os itens que atendem às duas regras receberão o desconto.
+
+Para deletar uma regra, clique em <i class="fas-trash-can"></i> `Remover regra`.
+
+### Condições
+
+O pedido do cliente deve atender a todas as condições cadastradas nesta seção para ser válido na promoção.
+
+![seller-portal-promo-condicoes-pt](//images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/89137c0a33eea10f6c9ca9cd4e0bae1c/image.png)
+
+* **Preço do item:** o desconto será concedido apenas aos itens que estão dentro do intervalo de preço preenchidos. 
+* **Tipo de envio:** o desconto será concedido caso o tipo de frete escolhido pelo cliente seja o mesmo que o cadastrado na promoção. 
+* **País de entrega:** o desconto será concedido aos itens que são entregues aos países selecionados neste campo.
+* **CEP de entrega:** o desconto será concedido caso o CEP de entrega esteja atendendo à regra configurada. É possível adicionar mais de um intervalo de CEP para incluir ou excluir mais áreas.
+
+### Restrições
+
+A atuação da promoção será limitada pelo seguinte critério:
+
+![seller-portal-promo-restricoes-pt](//images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/4f4b06e2fe29eb7ef71c28e4f39d26c8/image.png)
+
+* **Limitar a quantidade de itens elegíveis por carrinho:** define o número máximo de itens do carrinho serão afetados pela promoção. Caso o carrinho apresente uma quantidade de itens maior que o limite, o desconto será aplicado a apenas a quantidade configurada neste campo.
diff --git a/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
index 2ff0b34fa..c9b5519a4 100644
--- a/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
@@ -27,7 +27,7 @@ Por meio do Seller Portal, marketplaces conseguem:
 - Diminuir o tempo de conversão das vendas, com o onboarding self-service de novos sellers, agora mais rápido e sem fricção.  
 - Compartilhar o sortimento de produtos com o seller de forma simples e gerenciar com agilidade anúncios de produtos compartilhados.  
 
-![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 ## Interação entre seller e marketplace no Seller Portal
 
diff --git a/docs/tutorials/pt/seller-portal-product-details.md b/docs/tutorials/pt/seller-portal-product-details.md
index 0a027e599..11a26f6de 100644
--- a/docs/tutorials/pt/seller-portal-product-details.md
+++ b/docs/tutorials/pt/seller-portal-product-details.md
@@ -15,7 +15,7 @@ legacySlug: seller-portal-detalhes-do-produto
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
-![Shared products product details PT](https://images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/6e0ade39ea38708c2081d48b346d96ed/Shared_products_product_details_PT.jpg)
+![Shared products product details PT](//images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/6e0ade39ea38708c2081d48b346d96ed/Shared_products_product_details_PT.jpg)
 
 A página Detalhes do Produto na funcionalidade [Produtos Compartilhados](https://help.vtex.com/pt/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) é onde todas as informações sobre um produto  específico são visualizadas. É a partir dela que o seller:  
 
diff --git a/docs/tutorials/pt/seller-portal-promotions.md b/docs/tutorials/pt/seller-portal-promotions.md
new file mode 100644
index 000000000..13afa97af
--- /dev/null
+++ b/docs/tutorials/pt/seller-portal-promotions.md
@@ -0,0 +1,96 @@
+---
+title: 'Seller Portal: Promoções'
+id: 73LL7Ja0P4JbD77AH0jHwu
+status: PUBLISHED
+createdAt: 2023-10-03T16:07:24.166Z
+updatedAt: 2023-10-03T21:29:14.851Z
+publishedAt: 2023-10-03T21:29:14.851Z
+firstPublishedAt: 2023-10-03T21:26:29.611Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: seller-portal-promocoes
+locale: pt
+legacySlug: seller-portal-promocoes
+subcategory: 4hisB47iAVZk4r3SEmMoG
+---
+
+A página **Promoções** no Seller Portal permite visualizar e gerenciar a lista completa de promoções cadastradas, simplificando a gestão de promoções de sellers. Você pode acessar a página por meio do menu **Promoções > Promoções** no Admin VTEX.
+
+A partir da lista de promoções no Seller Portal, você pode realizar uma variedade de ações:
+
+* [Criar nova promoção](#criar-nova-promocao)
+* [Buscar promoções](#buscar-promocoes)
+* [Filtrar promoções](#filtrar-promocoes)
+* [Exportar promoções](#exportar-promocoes)
+* [Verificar dados de uso das promoções](#verificar-dados-de-uso-das-promocoes)
+* [Acessar menu de ações da promoção](#acessar-menu-de-acoes-da-promocao)
+* [Acessar promoções arquivadas](#acessar-promocoes-arquivadas)
+
+![seller-portal-promo-pt](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/124f6651a5de6411ec93f545748cd75c/image.png)
+
+A página **Promoções** apresenta as seguintes informações em uma tabela: 
+
+| Coluna | Descrição                                         |
+| ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Nome   | Nome e descrição da promoção.        |
+| De     | Data a partir da qual a promoção será aplicada.  |
+| Até    | Data em que a promoção será encerrada. |
+| Status | Status da promoção, que pode estar:<br><br>-   **Ativa:** quando a promoção está ativada e sendo aplicada na loja.<br>-    **Programada:** quando a promoção foi programada.<br>-   **Pausada:** quando a promoção estiver pausada.<br>-   **Finalizada:** quando a promoção foi encerrada. |
+
+## Criar nova promoção
+
+Para cadastrar uma nova promoção, clique no botão `Criar promoção`. Para mais informações, leia o guia [Seller Portal: Como criar uma promoção](https://help.vtex.com/pt/tutorial/seller-portal-criar-uma-promocao--kzNPEaiJE8EWkDzO9dbBI).
+
+## Buscar promoções
+
+Para buscar por uma promoção específica na lista, você pode utilizar a barra de busca. Nela, é possível pesquisar por nome e descrição.
+
+## Filtrar promoções
+
+Você pode filtrar as promoções da listagem a partir das informações a seguir:
+
+* **Status:** status da promoção. As opções são `Ativa`, `Programada`, `Pausada` e `Finalizada`.
+* **Última edição:** filtra as últimas edições nos últimos 12 meses, 3 meses, 30 dias, 7 dias ou no dia anterior à consulta.
+
+Selecione os filtros desejados e clique em `Aplicar` para filtrar as promoções. Para cancelar a seleção, clique em `Limpar` nos filtros desejados.
+
+## Exportar promoções
+
+Você pode fazer download de um arquivo CSV com as promoções cadastradas na sua loja e suas respectivas informações. Para isso, clique no botão `Exportar`, ao lado da barra de busca. O arquivo exportado considera os filtros aplicados na lista e não inclui promoções arquivadas.
+
+O arquivo contém as seguintes informações sobre cada promoção:
+
+| Coluna | Descrição                                                                          |
+| ------ | ---------------------------------------------------------------------------------- |
+| ID     | ID da promoção.                                                                    |
+| Nome   | Nome da promoção.                                                                  |
+| De     | Data de início da promoção.                                                        |
+| Até    | Data de fim da promoção.                                                           |
+| Status | Status atual da promoção, que pode estar **Ativa**, **Programada**, **Pausada** ou **Finalizada**. |
+
+## Verificar dados de uso das promoções
+
+![seller-portal-promo-ativas-pt](//images.ctfassets.net/alneenqid6w5/3tnyz6u3HxC6Qjezn9PvLr/b8e5dbee51610f19330da09d655ee8ca/image.png)
+
+Para visualizar o total de promoções ativas na sua loja e a cota de espaço restante para novas promoções, clique em `Uso das promoções`.
+
+O número máximo padrão de promoções ativas é 100. Caso precise aumentar esse limite, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
+
+## Acessar menu de ações da promoção
+
+Ao clicar no ícone de menu <i class="fas fa-ellipsis-v"></i> de uma promoção, você pode realizar as seguintes ações:
+
+*  <i class="fas fa-pencil-alt"></i> **Editar:** editar a promoção.
+*  <i class="far fa-clone"></i> **Duplicar:** criar uma nova promoção a partir das informações desta promoção.
+* <i class="fas fa-archive"></i> **Arquivar:** arquivar a promoção. A promoção será movida automaticamente para a página [Promoções arquivadas](#acessar-promocoes-arquivadas).
+
+## Acessar promoções arquivadas
+
+Para acessar a página **Promoções arquivadas**, clique no ícone <i class="fas fa-ellipsis-v"></i> e em seguida em <i class="fas fa-box"></i>.
+
+Você poderá desarquivar ou duplicar as promoções arquivadas clicando no ícone <i class="fas fa-ellipsis-v"></i>. 
+
+<div class="alert alert-info">
+  <p>Ao desarquivar uma promoção, seu status mudará para <code>Pausada</code>.</p>
+  </div>
diff --git a/docs/tutorials/pt/seller-portal-shared-products.md b/docs/tutorials/pt/seller-portal-shared-products.md
index d8e55ba76..540fb0127 100644
--- a/docs/tutorials/pt/seller-portal-shared-products.md
+++ b/docs/tutorials/pt/seller-portal-shared-products.md
@@ -3,8 +3,8 @@ title: 'Seller Portal: Produtos Compartilhados'
 id: 6vUGj2UmOuLzQTK9pj04lu
 status: PUBLISHED
 createdAt: 2021-02-02T20:31:40.476Z
-updatedAt: 2023-03-31T15:18:11.408Z
-publishedAt: 2023-03-31T15:18:11.408Z
+updatedAt: 2023-11-22T14:00:41.976Z
+publishedAt: 2023-11-22T14:00:41.976Z
 firstPublishedAt: 2021-09-15T20:52:51.767Z
 contentType: tutorial
 productTeam: Channels
@@ -15,6 +15,9 @@ legacySlug: seller-portal-produtos-compartilhados
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
+
+<div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso<a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+
 **Produtos Compartilhados** é o módulo onde você gerencia os produtos em comum entre seu catálogo e o que já é ofertado no marketplace. O painel de produtos compartilhados informa todos os produtos que o marketplace disponibilizou para sua loja vender. São produtos sincronizados com o Catálogo do marketplace. 
 
 A funcionalidade Produtos Compartilhados diminui a complexidade de vender produtos que o marketplace já tem disponível em seu próprio catálogo, permitindo que o seller comece a vender mais rápido e com menos fricção. A funcionalidade conta com duas abas:
@@ -26,7 +29,7 @@ Para acessar a funcionalidade Produtos Compartilhados, clique em *Preços > Cat
 
 ## Importados
 
-![Shared products Importados PT](https://images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/e7b820dcb3cbbcc3031f58ec3e6dde20/Shared_products_Importados_PT.jpg)
+![Shared products Importados PT](//images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/e7b820dcb3cbbcc3031f58ec3e6dde20/Shared_products_Importados_PT.jpg)
 
 A aba *Importados* reúne produtos do catálogo do marketplace que já foram importados pelo seller, ou seja, que já podem virar anúncios. A lista contém uma barra de busca, para pesquisar produtos por nome ou SKU. É por meio dessa aba, que produtos são ativados.  
 
@@ -36,7 +39,7 @@ Ao clicar em um produto da listagem, você acessa a página de [Detalhes do prod
 
 ## Disponíveis 
 
-![Shared products Disponíveis PT](https://images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/ad06a23c6ec0486964a8465290e215b3/Shared_products_Dispon__veis_PT.jpg)
+![Shared products Disponíveis PT](//images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/ad06a23c6ec0486964a8465290e215b3/Shared_products_Dispon__veis_PT.jpg)
 
 A aba *Disponíveis* reúne produtos do catálogo do marketplace que foram disponibilizados para que o seller os venda, e que não foram incorporados ainda no catálogo do seller. É possível filtrar os produtos disponíveis por marca ou categoria para agilizar o processo de importação dos produtos selecionados. 
 
diff --git a/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md b/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md
index 23a3ef485..45daf8399 100644
--- a/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md
+++ b/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md
@@ -3,13 +3,13 @@ title: 'Enviar ao Gateway ou ao ERP o preço do item já com o imposto separado'
 id: 77O1rBSLHqW8eWWsE6IEii
 status: PUBLISHED
 createdAt: 2017-08-14T15:30:39.027Z
-updatedAt: 2019-12-31T15:21:46.929Z
-publishedAt: 2019-12-31T15:21:46.929Z
+updatedAt: 2024-04-17T14:38:57.929Z
+publishedAt: 2024-04-17T14:38:57.929Z
 firstPublishedAt: 2017-08-16T17:43:33.301Z
 contentType: tutorial
 productTeam: Others
 author: 5V92cmF9jG8KG600EwUgEg
-slug: enviar-preço-com-imposto-separado
+slug: enviar-preco-com-imposto-separado
 locale: pt
 legacySlug: enviar-preço-com-imposto-separado
 subcategory: 18Gsips3u48UYCu0Ku2sWm
@@ -33,7 +33,7 @@ Para indicar nas vitrines o preço somando as taxas aplicadas, utilize o atribut
 
 Ou, então, para criar um JS e somar o valor do imposto nas vitrines, também é possível utilizar o controle `$product.Tax` (Ele indica as taxas registradas referentes ao produto).
 
-[Veja a documentação sobre controles aqui](/pt/tutorial/controles-do-template-de-prateleira)
+[Veja a documentação sobre controles aqui](https://developers.vtex.com/docs/guides/shelf-template-controls)
 
 __Atenção__: Na página de produto é necessário colocar um JavaScript para fazer a soma do valor.
 
diff --git a/docs/tutorials/pt/sending-sku-attributes-to-amazon.md b/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
index f8985dcdb..8a5e78f3e 100644
--- a/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
@@ -19,7 +19,7 @@ Feitas as configurações iniciais para a [integração com a Amazon](/pt/tutori
 
 O mapeamento só será feito uma vez para cada categoria. Desta forma, mesmo já tendo feito um mapeamento, quando novos produtos forem criados, eles serão integrados diretamente. Será feito um __de/para__ dos atributos cadastrados na VTEX com os atributos aceitos pela Amazon.
 
-1. Crie uma __planilha de upload__ no formato `.xlsx` e preencha o título das colunas conforme a imagem abaixo.![Modelo Atributos Amazon](https://images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
+1. Crie uma __planilha de upload__ no formato `.xlsx` e preencha o título das colunas conforme a imagem abaixo.![Modelo Atributos Amazon](//images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
 
 2. Preencha os campos da planilha de mapeamento de acordo com as indicações abaixo:
 
@@ -49,7 +49,7 @@ Atenção: caso as colunas não forem nomeadas <strong>tal qual</strong> a forma
 
 Planilha de exemplo usando a categoria Clothing & Accessories:
 
-![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
+![Amazon Mapeamento ](//images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
 <div class="alert alert-danger">
 Lembre-se que estes valores devem estar de acordo com os valores aceitos pela Amazon. Consulte os termos aceitos e faça o De/Para entre o que está cadastrado no seu campo de SKU na VTEX e os valores permitidos na Amazon.
diff --git a/docs/tutorials/pt/sent-offers-beta.md b/docs/tutorials/pt/sent-offers-beta.md
index 1529128e9..668b896e8 100644
--- a/docs/tutorials/pt/sent-offers-beta.md
+++ b/docs/tutorials/pt/sent-offers-beta.md
@@ -22,7 +22,7 @@ O módulo Anúncios Enviados permite que sellers supervisionem o envio e a sincr
 - [Anúncios](https://help.vtex.com/pt/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#anuncios)            
 - [Canais](https://help.vtex.com/pt/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#canais)          
 
-![Anuncios enviados Home PT](https://images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/7b571504f49ac69f0788861144905d4e/Anuncios_enviados_Home_PT.jpg)
+![Anuncios enviados Home PT](//images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/7b571504f49ac69f0788861144905d4e/Anuncios_enviados_Home_PT.jpg)
 
 ## Anúncios
 
diff --git a/docs/tutorials/pt/sent-offers-buybox-opportunities.md b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
index a375479b4..013a044ac 100644
--- a/docs/tutorials/pt/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
@@ -1,10 +1,10 @@
 ---
-title: 'Gerenciamento de anúncios: oportunidades de Buybox '
+title: 'Gerenciamento de anúncios: oportunidades de Catálogo MeLi '
 id: 1hO9eI1th47EGxQoTzGewC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2021-07-29T19:59:30.988Z
-updatedAt: 2022-10-20T01:38:56.059Z
-publishedAt: 2022-10-20T01:38:56.059Z
+updatedAt: 2024-06-20T21:42:56.304Z
+publishedAt: 
 firstPublishedAt: 2021-07-29T20:20:39.780Z
 contentType: tutorial
 productTeam: Channels
@@ -12,14 +12,21 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: anuncios-enviados-oportunidades-de-buybox
 locale: pt
 legacySlug: anuncios-enviados-oportunidades-de-buybox-beta
-subcategory: 2zVauFUkYn8vgS0y0MfWeK
+subcategory: 
 ---
 
+<div class="alert alert-info">
+Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
+Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
+Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
+</div>  
+
 Anúncio é um SKU de um seller que foi enviado para um canal de vendas e teve seu preço e estoque configurados. O módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) do Admin VTEX permite que sellers supervisionem o envio e sincronização de seus produtos para marketplaces e também apresenta oportunidades de mais vendas para seus anúncios. 
 
 A funcionalidade chamada *Oportunidades* identifica anúncios do seller que podem performar com mais sucesso nos canais em que são vendidos e direciona ações para que essas oportunidades se realizem. 
 
-Um exemplo de oportunidade é a funcionalidade de *Buybox* do Mercado Livre. O Buybox é um recurso no checkout do Mercado Livre, que seleciona anúncios de sellers diferentes como opções de compra para um mesmo produto. O **Gerenciamento de anúncios** avalia os anúncios que são compatíveis com produtos já presentes no Mercado Livre, para que sejam adicionados ao seu Buybox.
+Um exemplo de oportunidade é a funcionalidade de Catálogo MeLi. O Catálogo MeLi é um recurso no checkout do Mercado Livre, que seleciona anúncios de sellers diferentes como opções de compra para um mesmo produto. O Gerenciamento de anúncios avalia os anúncios que são compatíveis com produtos já presentes no Mercado Livre, para que sejam adicionados ao seu Catálogo MeLi.
 
 As *Oportunidades* acompanham a presença de um anúncio nas diferentes páginas do módulo **Gerenciamento de anúncios**, como será visto nas imagens a seguir.
 
@@ -29,54 +36,58 @@ O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="
 
 ## Listagem de Anúncios
 
-Na página [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/offers-listing--7MRb9S78aBdZjFGpbuffpE), anúncios com oportunidades de Buybox abertas terão um ícone <i class="fas fa-bolt"></i> em seu título. Ao clicar no anúncio marcado com uma `Oportunidade`, você será redirecionado para a página a seguir.
+Na página [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/offers-listing--7MRb9S78aBdZjFGpbuffpE), anúncios com oportunidades de Catálogo MeLi abertas terão um ícone em seu título. Ao clicar no anúncio marcado com uma `Oportunidade`, você será redirecionado para a página a seguir.
 
 ## Detalhes do Anúncio
 
-![PT Oportunidades Offer details](https://images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/c50404811bbb7be69e463f97cdc4408e/PT_Oportunidades_Offer_details.jpg)
+![PT Oportunidades Offer details](//images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/c50404811bbb7be69e463f97cdc4408e/PT_Oportunidades_Offer_details.jpg)
 
 A página de [Detalhes do anúncio](https://help.vtex.com/pt/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) apresenta um card de `Oportunidade` no topo. Ao clicar em `Ver Oportunidade`, você será redirecionado para a página a seguir.
 
 ## Oportunidades do Anúncio
 
-![PT Oportunidades oportunidades do anúncio](https://images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/753c2b80a4bf68ca6f82aa6f23cca363/PT_Oportunidades_oportunidades_do_an__ncio.jpg)
+![PT Oportunidades oportunidades do anúncio](//images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/753c2b80a4bf68ca6f82aa6f23cca363/PT_Oportunidades_oportunidades_do_an__ncio.jpg)
+
+A página **Oportunidades do anúncio** apresenta o anúncio elegível para o Catálogo MeLi ao lado do anúncio já presente no marketplace. A página permite comparar os dados dos dois anúncios, incluindo informações das marcas, especificações e dimensões.
+
+Além da oportunidade de adicionar anúncios, há o __Auto Optin (criação automática de anúncios Catálogo MeLi)__, nesta opção o Mercado Livre irá avaliar as publicações dos sellers, caso cumpra com todos os requisitos para se tornar um anúncio de Catálogo MeLi, ele será feito automaticamente e o seller visualizará a mensagem da imagem abaixo.
 
-A página **Oportunidades do anúncio** apresenta o anúncio elegível para o Buybox ao lado do anúncio já presente no marketplace. A página permite comparar os dados dos dois anúncios, incluindo informações das marcas, especificações e dimensões.
+![Auto Optin MELI](//images.ctfassets.net/alneenqid6w5/2Hiw11uUW5n5QHvwIlpo0C/95e691c69a8a8afccdf50abd0f0d09c4/Captura_de_tela_2023-06-27_175316.png)
 
-## Adicionar anúncios ao Buybox
+## Adicionar anúncios ao Catálogo MeLi
 
-Siga os passos abaixo para adicionar seu anúncio ao Buybox:
+Siga os passos abaixo para adicionar seu anúncio ao Catálogo MeLi:
 
 1. No Admin VTEX, acesse **MARKETPLACE > Gestão de anúncios**. 
 > Se sua loja usa o [Novo Admin VTEX](https://content.vtex.com/join-new-admin-beta-program-pt/), acesse **Marketplace > Conexões**.
 2. Selecione o anúncio que tiver o ícone raio <i class="fas fa-bolt"></i>.
 3. Na página **Detalhes do Anúncio**, clique em `Ver Oportunidade`.
-4. Na página de **Oportunidade do Anúncio**, avalie se seu anúncio é compatível com o anúncio já presente no marketplace. Caso sejam compatíveis, clique em `Adicionar ao Buybox`. 
+4. Na página de **Oportunidade do Anúncio**, avalie se seu anúncio é compatível com o anúncio já presente no marketplace. Caso sejam compatíveis, clique em `Adicionar ao Catálogo MeLi`. 
 5. Clique em `Adicionar`.
 
 <div class="alert alert-warning">
-Essa ação não poderá ser desfeita, portanto certifique-se de que os anúncios são compatíveis. Se seu anúncio não for compatível com o produto já presente no marketplace, não adicione-o ao Buybox. Adicionar anúncios que não fazem parte do produto pode prejudicar sua reputação como seller naquele marketplace.  
+Essa ação não poderá ser desfeita, portanto certifique-se de que os anúncios são compatíveis. Se seu anúncio não for compatível com o produto já presente no marketplace, não adicione-o ao Catálogo MeLi. Adicionar anúncios que não fazem parte do produto pode prejudicar sua reputação como seller naquele marketplace.  
 </div>
 
-Para que seu anúncio esteja bem posicionado no Buybox, finalize as configurações indicadas na próxima seção [Ganhando e perdendo no Buybox](#ganhando-e-perdendo-no-buybox).
+Para que seu anúncio esteja bem posicionado no Catálogo MeLi, finalize as configurações indicadas na próxima seção [Ganhando e perdendo no Catálogo MeLi](#ganhando-e-perdendo-no-buybox).
 
-## Ganhando e perdendo no Buybox
+## Ganhando e perdendo no Catálogo MeLi
 
-Após [adicionar o anúncio ao Buybox](#adicionar-anuncios-ao-buybox), seu anúncio estará ativo no Buybox daquele produto, mas não necessariamente será o primeiro item indicado para a compra no marketplace. Anúncios podem estar, portanto, com um dos status abaixo:
+Após [adicionar o anúncio ao Catálogo MeLi](#adicionar-anuncios-ao-buybox), seu anúncio estará ativo no Catálogo MeLi daquele produto, mas não necessariamente será o primeiro item indicado para a compra no marketplace. Anúncios podem estar, portanto, com um dos status abaixo:
 
-- **Ganhando:** você ativou a oportunidade e seu anúncio está em primeiro lugar do Buybox.   
+- **Ganhando:** você ativou a oportunidade e seu anúncio está em primeiro lugar do Catálogo MeLi.   
 - **Perdendo:** você ativou a oportunidade, mas não terminou as configurações necessárias para tornar o anúncio atrativo suficiente para estar em primeiro lugar.
 
 Para que seu anúncio esteja ganhando, siga as instruções abaixo:
 
 1. Na página **Oportunidade do Anúncio**, clique em `Ver detalhes do anúncio`, 
 2. Acesse as **Oportunidades Ativas**. 
-3. Siga as instruções listadas na seção, para finalizar a configuração do anúncio e ativá-lo no Buybox.
+3. Siga as instruções Catálogo MeLi.
 
 A seção de *Oportunidades Ativas* da página [Detalhes do anúncio](https://help.vtex.com/pt/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) reúne: 
 
-- **Dados da Buybox:** informações sobre os buyboxes em que o anúncio foi adicionado.  
+- **Dados da Catálogo MeLi:** informações sobre o Catálogo MeLi em que o anúncio foi adicionado.  
 - **Status da oportunidade:** incluindo `Ganhando` ou `Perdendo`.  
-- **Lista de configurações:** ações necessárias para que seu anúncio esteja ganhando na buybox. As instruções listadas incluem alterar preço, promover frete grátis, entrega rápida ou oferecer pagamento com parcelamento sem juros, por exemplo. Cada item da lista apresenta uma sugestão de configuração  que tornará o anúncio mais atrativo, posicionando-o em primeiro lugar no Buybox. 
+- **Lista de configurações:** ações necessárias para que seu anúncio esteja ganhando na Catálogo MeLi. As instruções listadas incluem alterar preço, promover frete grátis, entrega rápida ou oferecer pagamento com parcelamento sem juros, por exemplo. Cada item da lista apresenta uma sugestão de configuração  que tornará o anúncio mais atrativo, posicionando-o em primeiro lugar no Catálogo MeLi. 
 
-![PT Oportunidades oportunidades ativas](https://images.ctfassets.net/alneenqid6w5/1e5ozasXAVsjNrH7RBjq71/6e7672dc863d4150b4e8b8efe600187a/PT_Oportunidades_oportunidades_ativas.jpg)
+![PT Oportunidades oportunidades ativas](//images.ctfassets.net/alneenqid6w5/1e5ozasXAVsjNrH7RBjq71/6e7672dc863d4150b4e8b8efe600187a/PT_Oportunidades_oportunidades_ativas.jpg)
diff --git a/docs/tutorials/pt/sequencial-suiteshare.md b/docs/tutorials/pt/sequencial-suiteshare.md
index 9c7ad4e4f..db049a682 100644
--- a/docs/tutorials/pt/sequencial-suiteshare.md
+++ b/docs/tutorials/pt/sequencial-suiteshare.md
@@ -21,25 +21,25 @@ O Sequencial garante que a sua empresa terá um atendimento no WhatsApp mais org
 
  Para criar um atendimento seletivo, acesse: _**Organizar > Sequencial**_. 
 
-![Sequencial  1](https://images.ctfassets.net/alneenqid6w5/5d6rENDv7iZliW45U3wSdX/863a4066aeb31f4130f509441aed7560/Screenshot_2022-08-29_at_17-29-16_Sequencial.png)
+![Sequencial  1](//images.ctfassets.net/alneenqid6w5/5d6rENDv7iZliW45U3wSdX/863a4066aeb31f4130f509441aed7560/Screenshot_2022-08-29_at_17-29-16_Sequencial.png)
 
 IMPORTANTE: Antes de começar, você já deverá ter criado um link para cada número de WhatsApp que deseja adicionar na central. Se ainda não fez isso, é só [acessar esse link](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB).
 
 Clique em “_**Novo**_”.
 
-![Sequencial 2](https://images.ctfassets.net/alneenqid6w5/6yE3a7cKM7tjSmg2YUCnsi/372a64bb021c5ed195aa0d49fc3a0508/Screenshot_2022-08-29_at_17-29-21_Sequencial.png)
+![Sequencial 2](//images.ctfassets.net/alneenqid6w5/6yE3a7cKM7tjSmg2YUCnsi/372a64bb021c5ed195aa0d49fc3a0508/Screenshot_2022-08-29_at_17-29-21_Sequencial.png)
 
 Defina o **link principal**. 
 
 Em **Link Âncora**, como o próprio nome já diz, você irá selecionar o link principal da central. Esse é o link que você irá divulgar, será o link responsável por fazer a ligação com os demais atendentes.
 
-![Sequencial 3](https://images.ctfassets.net/alneenqid6w5/1ey00JvWyDeOWkCG7kzhgl/1985a9808e85374f15d3fb21feabb4b5/Screenshot_2022-08-29_at_17-29-25_Sequencial.png)
+![Sequencial 3](//images.ctfassets.net/alneenqid6w5/1ey00JvWyDeOWkCG7kzhgl/1985a9808e85374f15d3fb21feabb4b5/Screenshot_2022-08-29_at_17-29-25_Sequencial.png)
 
 Clique em _**“Avançar”**_.
 
 Em Links de Sequência, você irá escolher quem serão os vendedores ou números que irão participar da central. Clique em Adicionar e selecione o link para cada participante da central.
 
-![Sequencial 4](https://images.ctfassets.net/alneenqid6w5/7wYRRK5a5E8Myh7LUkSNKN/facae61bda1dafdc6421eca7cbd19687/Screenshot_2022-08-29_at_17-29-30_Sequencial.png)
+![Sequencial 4](//images.ctfassets.net/alneenqid6w5/7wYRRK5a5E8Myh7LUkSNKN/facae61bda1dafdc6421eca7cbd19687/Screenshot_2022-08-29_at_17-29-30_Sequencial.png)
 
 **NOTA**: Em atendimento fixo (opcional), você irá escolher se um cliente que já falou com algum atendente, ao clicar novamente no link principal (/minhacentral), cairá sempre para o mesmo atendente.
 
diff --git a/docs/tutorials/pt/services-import.md b/docs/tutorials/pt/services-import.md
index cbb5b62d9..26639db7e 100644
--- a/docs/tutorials/pt/services-import.md
+++ b/docs/tutorials/pt/services-import.md
@@ -86,5 +86,5 @@ Cuidados com o preenchimento da planilha:
   </body>
 </div>
 
-![menu importação de serviços](https://images.ctfassets.net/alneenqid6w5/6VXBtxVKQvnNvqEwCI09dZ/15a4abddec959d9efdd9ae97f4116b97/importacao_servi__os.png)
+![menu importação de serviços](//images.ctfassets.net/alneenqid6w5/6VXBtxVKQvnNvqEwCI09dZ/15a4abddec959d9efdd9ae97f4116b97/importacao_servi__os.png)
 
diff --git a/docs/tutorials/pt/services-scheduling.md b/docs/tutorials/pt/services-scheduling.md
index 210a6c8ae..f986ed053 100644
--- a/docs/tutorials/pt/services-scheduling.md
+++ b/docs/tutorials/pt/services-scheduling.md
@@ -48,7 +48,7 @@ Na planilha os campos a serem preenchidos são:
 
 Para escolher o turno da entrega, marque um X na célula em apenas um dos turnos (Manhã, Tarde ou Noite).
 
-![exemplo de planilha de agendamento](https://images.ctfassets.net/alneenqid6w5/5crlOibYcmzfWkusdc2iSP/2cefb30f0df8fc7ab61104a09f8f9414/exemplo_planilha_agendamento.png)
+![exemplo de planilha de agendamento](//images.ctfassets.net/alneenqid6w5/5crlOibYcmzfWkusdc2iSP/2cefb30f0df8fc7ab61104a09f8f9414/exemplo_planilha_agendamento.png)
 
 <div class="alert alert-danger"> 
 O modelo da planilha não deve ser alterado. Nenhuma coluna deve ser modificada ou trocada de posição. 
@@ -76,4 +76,4 @@ Depois de preencher a planilha, você precisa subir o arquivo na plataforma VTEX
 Os agendamentos só podem ser alterados se as entregas ainda estiverem no status Ativo. 
 </div>
 
-![Agendamento de serviços](https://images.ctfassets.net/alneenqid6w5/OhKdJX8S3Ef4EjoUOaGL3/5f463a280ae7cfa51a856d047b39be82/Agendamento.gif)
+![Agendamento de serviços](//images.ctfassets.net/alneenqid6w5/OhKdJX8S3Ef4EjoUOaGL3/5f463a280ae7cfa51a856d047b39be82/Agendamento.gif)
diff --git a/docs/tutorials/pt/set-up-mundi-gateway.md b/docs/tutorials/pt/set-up-mundi-gateway.md
index fdc50b90b..2a2b70d77 100644
--- a/docs/tutorials/pt/set-up-mundi-gateway.md
+++ b/docs/tutorials/pt/set-up-mundi-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway Mundi '
 id: 2yn9dKzvZOF5tn4RCX2Nbq
 status: PUBLISHED
 createdAt: 2019-04-04T21:12:48.808Z
-updatedAt: 2023-03-26T21:57:24.882Z
-publishedAt: 2023-03-26T21:57:24.882Z
+updatedAt: 2024-01-23T19:02:29.463Z
+publishedAt: 2024-01-23T19:02:29.463Z
 firstPublishedAt: 2019-04-04T21:20:22.149Z
 contentType: tutorial
 productTeam: Financial
@@ -21,13 +21,13 @@ Na VTEX, é possível fazer uma integração com o provedor de pagamentos Mundi.
 Se desejar utilizar também o antifraude da Mundi, as configurações desta função devem ser realizadas pelo hub da própria empresa. Em caso de dúvidas sobre essa etapa da operação, consulte o suporte técnico da Mundi.
 </div>
 
-Para configurar a afiliação Mundi, siga os passos abaixo:
+Para configurar Mundi, siga os passos abaixo:
 
-<ui>1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.</ui>
+<ui>1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.</ui>
 
-<ui>2. Na aba __Afiliações de Gateways__, clique no botão __+__.</ui>
+<ui>2. Na tela de provedores, clique no botão `Novo provedor`.</ui>
 
-<ui>3. Clique no conector __Mundi__.</ui>
+<ui>3. Digite o nome __Mundi__ na barra de busca e clique sobre o nome do provedor.</ui>
 
 <ui>4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Mundi.</ui>
 
diff --git a/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md b/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md
index 0ad42d386..1c65b37fc 100644
--- a/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md
+++ b/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md
@@ -27,7 +27,7 @@ Para configurar essa autenticação, siga os passos abaixo:
 2. Entre em __Configurações__ 
 3. Na seção de **Carrinho**, ative a flag __Exigir autenticação do usuário para pagamentos autorizados automaticamente__
 
-![autenticação-usuario-pagamento-recorrencia pt](https://images.ctfassets.net/alneenqid6w5/16uRqeq2F4k4UIouOooeoo/40ff615b3f2cbe6b079462960f0a5e8f/autentica____o-usuario-pagamento-recorrencia_pt.png)
+![autenticação-usuario-pagamento-recorrencia pt](//images.ctfassets.net/alneenqid6w5/16uRqeq2F4k4UIouOooeoo/40ff615b3f2cbe6b079462960f0a5e8f/autentica____o-usuario-pagamento-recorrencia_pt.png)
 
 
 4. Clique no botão __Salvar__.
diff --git a/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md b/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md
index 70145b28f..f63dbe80d 100644
--- a/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md
+++ b/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md
@@ -3,8 +3,8 @@ title: 'Configurar produto similar, sugestões, acessórios e genéricos'
 id: tutorials_280
 status: PUBLISHED
 createdAt: 2017-04-27T22:10:17.727Z
-updatedAt: 2023-03-29T14:45:42.789Z
-publishedAt: 2023-03-29T14:45:42.789Z
+updatedAt: 2024-07-25T21:19:12.871Z
+publishedAt: 2024-07-25T21:19:12.871Z
 firstPublishedAt: 2017-04-27T23:03:13.377Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -35,7 +35,7 @@ Para te auxiliar na utilização da técnicas acima podemos utilizar os campos n
 4. Preencha os campos corretamente conforme indicação abaixo.
 5. Clique no botão `Salvar`.
 
-![produto-similar-sugestão-acessório-exemplo pt](https://images.ctfassets.net/alneenqid6w5/2Eg0eAnNjCkWu6acGQYq4Q/02418b5ba84fbbca1c8269ebcbc51d96/produto-simular-sugest__o-acess__rio-exemplo_pt.png)
+![produto-similar-sugestão-acessório-exemplo pt](//images.ctfassets.net/alneenqid6w5/2Eg0eAnNjCkWu6acGQYq4Q/02418b5ba84fbbca1c8269ebcbc51d96/produto-simular-sugest__o-acess__rio-exemplo_pt.png)
 
 **Acessórios:** nesse campo cadastramos os produtos que devem ser vendidos como complemento de um outro produto. Nesta opção os produto cadastrados como acessórios são mostrados como opção de compra com o checkbox de seleção habilitado (função feita no layout).
 
@@ -45,6 +45,4 @@ Para te auxiliar na utilização da técnicas acima podemos utilizar os campos n
 
 **Mostrar junto:** Exibe os SKUs dos produtos sugeridos para compra em conjunto. 
 
-Outras opções de Cross Selling podem ser habilitadas na construção do layout da loja através das opções de templates de prateleiras como “Quem comprou comprou também”, "Quem viu comprou também" e “Quem viu viu também". Para mais informações, acesse o artigo sobre [Controles do template de prateleira](https://help.vtex.com/pt/tutorial/lista-de-controles-para-templates--tutorials_563).
-
 A opção de Up Selling pode ser trabalhada com o uso da promoção [Compre Junto](http://help.vtex.com/pt/tutorial/compre-junto).
diff --git a/docs/tutorials/pt/setting-up-abandoned-carts.md b/docs/tutorials/pt/setting-up-abandoned-carts.md
index d5c5d317a..c420a17bb 100644
--- a/docs/tutorials/pt/setting-up-abandoned-carts.md
+++ b/docs/tutorials/pt/setting-up-abandoned-carts.md
@@ -3,8 +3,8 @@ title: 'Configurar Carrinho Abandonado'
 id: tutorials_740
 status: PUBLISHED
 createdAt: 2017-04-27T21:59:05.882Z
-updatedAt: 2023-04-28T14:50:21.362Z
-publishedAt: 2023-04-28T14:50:21.362Z
+updatedAt: 2024-06-24T14:49:04.124Z
+publishedAt: 2024-06-24T14:49:04.124Z
 firstPublishedAt: 2017-04-27T23:03:41.572Z
 contentType: tutorial
 productTeam: Shopping
@@ -18,19 +18,19 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 O carrinho abandonado é a funcionalidade da VTEX que envia e-mails aos clientes para lembrá-los de finalizar a compra em um carrinho que foi montado, mas não finalizado.
 
 A configuração do carrinho abandonado pode ser realizada de duas formas diferentes, de acordo com o ambiente de operação da loja:
-- [VTEX Legado](#configuracao-para-lojas-vtex-legado): por meio de diversos módulos da plataforma VTEX (CMS, Master Data e Central de Mensagens) e também em seu servidor de host.
+- [Portal CMS Legado](#configuracao-para-lojas-portal-cms-legado): por meio de diversos módulos da plataforma VTEX (CMS, Master Data e Central de Mensagens) e também em seu servidor de host.
 - [VTEX IO](#configuracao-para-lojas-vtex-io): por meio da instalação do app “Abandoned Cart”, configuração do template de email na Central de Mensagens, e do Trigger no Master Data.
 
-### Configuração para lojas VTEX Legado 
+## Configuração para lojas Portal CMS Legado 
 
 Nesta seção são apresentados os seguintes tópicos para configuração da funcionalidade carrinho abandonado nas lojas VTEX Legado:
 
 - [Configurar template de email no CMS](#configurar-template-de-email-no-cms)
 - [Configurar modelo de email na Central de Mensagens](#configurar-modelo-de-email-na-central-de-mensagens)
-- [Liberação do SPF](#liberacao-do-spf)
-- [Configuração da trigger](#configuracao-da-trigger)
+- [Liberar SPF](#liberar-spf)
+- [Configurar trigger](#configurar-trigger)
 
-#### Configurar template de email no CMS
+### Configurar template de email no CMS
 
 Você pode criar o seu próprio template de email customizado ou utilizar a opção padrão de template para carrinho abandonado. Para criar um novo template, siga os passos abaixo:
 
@@ -40,7 +40,7 @@ Você pode criar o seu próprio template de email customizado ou utilizar a opç
 4. Preencha o campo __Template XHTML__ com os códigos do template.
 5. Clique em `Save Template`.
 
-![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
+![template xhtml](//images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
 
 <div class="alert alert-warning">
 Recomendamos que a customização de template seja realizada por profissionais com experiência no módulo CMS, e preferencialmente, que já tenham realizado configurações de outros templates de página e prateleira.
@@ -52,9 +52,9 @@ Para utilizar uma opção padrão de template, siga os seguintes passos:
 2. Em __CMS > HTML Templates__, clique em `CEM-Abandoned-Cart`.
 3. Verifique as informações dos códigos de template presentes no campo __Template XHTML__.
 
-![CEM-Abandoned-Cart](https://images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
+![CEM-Abandoned-Cart](//images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
 
-#### Configurar modelo de email na Central de Mensagens
+### Configurar modelo de email na Central de Mensagens
 
 Uma vez criado o novo template de email ou utilizado os dados do template padrão, acesse a Central de Mensagens para configurar o modelo do email. Siga os passos abaixo:
 
@@ -71,124 +71,85 @@ Uma vez criado o novo template de email ou utilizado os dados do template padrã
 O campo JSON Data não deve ser preenchido ou seus dados utilizados no template do email. Ele contém apenas informações para permitir uma pré-visualização do formato em que os dados que serão visualizados no email.
 </div>
 
-![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
+![New template - message center](//images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
 
-#### Liberação do SPF
+### Liberar SPF
 
-A liberação do SPF é fundamental para evitar problemas de entregabilidade do e-mail, e deve ser realizada conforme o artigo [Configuração de SPF](https://help.vtex.com/pt/tutorial/configuracao-de-spf--42t0lkl2VyC6Yewc4wA6wI#).
+A liberação do SPF é fundamental para evitar problemas de entregabilidade do e-mail, e deve ser realizada conforme o artigo [Configuração de SPF](https://help.vtex.com/pt/tutorial/configuracao-de-spf--42t0lkl2VyC6Yewc4wA6wI).
 
 Como boa prática de configuração de DNS de um domínio genérico (não obrigatório), segue o exemplo abaixo:
 
-![Hostnames - SPF](https://images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
+![Hostnames - SPF](//images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
 
 Saiba mais em [Configurar o apontamento de DNS para a VTEX](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280?&utm_source=autocomplete).
 
-#### Configuração da trigger
-
-Nesta configuração será preciso criar uma [trigger no Master Data](https://help.vtex.com/pt/tutorial/criando-trigger-no-master-data?locale=pt). O processo consiste em preencher alguns valores que determinarão o disparo da trigger.
-
-Entre eles, três filtros adicionais, como:
-
-- Checkout
-- Carrinho
-- Último carrinho
-
-O filtro “Checkout” estabelece uma das condições para que a trigger seja disparada. No exemplo abaixo, a trigger será acionada se o carrinho não for finalizado e for diferente de nulo. Ou seja, caso o cliente não conclua a compra e não tenha incluído nada no carrinho.
-
-Além disso, temos ainda os filtros “Carrinho” e “Último Carrinho”. Por mais que ambos sejam semelhantes, os comportamentos são diferentes. O “Carrinho” é referente aos últimos produtos que o cliente incluiu no carrinho de compras propriamente dito. Já o “Último carrinho” consiste no registro de data e hora em que o carrinho foi criado.
-
-<div class="alert alert-warning">Para que o disparo da trigger seja realizado, os três filtros precisam estar obrigatoriamente preenchidos de acordo com o exemplo abaixo.
-</div>
-
-<blockquote><ui>1. No Admin VTEX, acesse <b>Configurações da loja</b> > <b>Storefront</b> > <b>Master Data.</b></ui>
-
-<blockquote><ui>2. No Master Data, clique em <b>Aplicações</b> > <b>Estrutura de dados.</b></ui>
-
-<blockquote><ui>2. Clique na aba <b>Trigger</b>.</ui>
-
-<blockquote><ui>3. Clique no botão <b>Add New</b>.</ui>
-
-<blockquote><ui>4. Insira o nome da trigger.</ui>
-
-<blockquote><ui>5. Em <b>Data Entity</b>, selecione o valor <b>Cliente</b>.</ui>
-
-<blockquote><ui>6. Em <b>Status</b>, marque <b>Enabled</b>.</ui>
-
-<blockquote><ui>7. Em <b>Trigger Rule</b>, selecione <b>O valor de um atributo for alterado</b>.</ui>
-
-<blockquote><ui>8. Em <b>Field</b>, selecione <b>Última sessão</b>.</ui>
-
-<blockquote><ui>9. Clique em <b>Add filter</b> (5x) para habilitar os campos. Selecione e preencha conforme indicação e ilustração abaixo.  
-
-<blockquote><blockquote><ui>-> Checkout - Diferente - Finalizado - and</ui>
-
-<blockquote><blockquote><ui>-> Checkout - Não está nulo - and</ui>
-
-<blockquote><blockquote><ui>-> Carrinho - Não está nulo - and</ui>
-
-<blockquote><blockquote><ui>-> Último Carrinho - Não está nulo</ui> 
-
-![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/d6c7e5d4e84c5d2b8b870de4ee0db4bc/Filter_Master_Data.PNG)
-
-<div class="alert alert-warning">
-  Além dos filtros indicados acima, é recomendável inserir um outro filtro no seguinte formato: <code>Receives newsletter? - Igual a - True</code>. Isso garante conformidade com os <a href="https://help.vtex.com/pt/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">direitos de titulares de dados</a>, já que somente clientes inscritos na newsletter receberão emails de carrinho abandonado. A inscrição na newsletter da sua loja pode ser gerenciada no momento do checkout ou na seção <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">Minha Conta</a> da sua loja.
-</div>
-
-<blockquote><ui> 10. Clique na aba <b>Schedule</b> e selecione se o envio do email deve ocorrer em uma data específica ou em uma data dinâmica.</ui>
-
-![Schedule date](https://images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/840f17bdc08c9703fdc972b2c8793668/Schedule_date.PNG)
-
-<blockquote><ui>11. Na aba <b>If positive</b>:</ui>
-
-<blockquote><blockquote><ui>a. Em Action, selecione <b>Send an email</b>.</ui>
-
-<blockquote><blockquote><ui>b. Em <b>Recipient</b>, para realizar um teste do sistema, digite o email e clique em <b>Add Static email</b>.</ui>
-
-<div class="alert alert-warning">Uma vez efetuada as demais configurações abaixo e verificado que recebeu a mensagem do carrinho abandonado em seu email, retorne a este passo, selecione a opção <strong>CL</strong>: <strong>Email</strong>, clique em <strong>Add Dynamic email</strong>, e depois em <strong>Save</strong>.
+### Configurar trigger
+
+Nesta etapa será necessário criar uma [trigger no Master Data](https://help.vtex.com/pt/tutorial/criando-trigger-no-master-data--tutorials_1270). O processo consiste em preencher alguns valores que determinarão o disparo da trigger. Entre eles, será necessário definir alguns filtros:
+
+- __Checkout:__ a trigger será acionada se o checkout não for finalizado e for diferente de nulo, ou seja, caso o cliente não conclua a compra.
+- __Carrinho:__ referente aos últimos produtos que o cliente incluiu no carrinho de compras. A trigger será acionada se o valor for diferente de nulo.
+- __Último carrinho:__ registro de data e hora em que o carrinho foi criado. A trigger será acionada se o valor for diferente de nulo.
+- __Recebe newsletter?:__ garante conformidade com os <a href="https://help.vtex.com/pt/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">direitos de titulares de dados</a>, já que somente clientes inscritos na newsletter receberão emails de carrinho abandonado. A inscrição na newsletter da sua loja pode ser gerenciada no momento do checkout ou na seção <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#perfil">Minha Conta</a> da sua loja. A trigger será acionada se o valor for verdadeiro.
+
+Para que o disparo da trigger seja realizado, os filtros precisam estar obrigatoriamente preenchidos de acordo com as instruções abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Storefront > Master Data__.
+2. No Master Data, clique em __Aplicações > Configurações avançadas > Estrutura de dados__.
+3. Clique na aba __Ativação__.
+4. Clique no botão `Adicionar`.
+5. Preencha os campos a seguir:
+
+   * **Nome:** insira o nome da trigger.
+   * **Entidade de dados:** selecione a entidade Cliente.
+   * **Status:** marque a opção __Ativo__.
+6. Na aba **Regras**, selecione *O valor de um atributo é alterado**.
+7. Em **Campo**, selecione *Última sessão*.
+8. Clique em `Adicionar filtro` cinco vezes para visualizar os campos de filtros. Selecione-os e preencha as informações conforme a indicação abaixo:
+
+   - *Checkout - Diferente de - Finalizado - e*
+   - *Checkout - Não é nulo - e*
+   - *Carrinho - Não é nulo - e*
+   - *Último Carrinho - Não é nulo - e*
+   - *Recebe newsletter? - Igual a - True*
+
+9. Clique na aba __Agendar__ e selecione se o envio do email deve ocorrer assim que possível, em uma data específica ou em uma data dinâmica.
+11. Clique na aba __Se positivo__.
+12. Preencha a aba conforme as instruções a seguir:
+
+    * **Ação:** selecione _Enviar um email_.
+    * **Destinatário**: para realizar um teste, digite o seu email e clique em `Adicionar email estático`.
+    * **Formato do corpo do email**: selecione _HTML_.
+    * **Nome do remetente:** insira o nome de sua loja da forma que você deseja que apareça no remetente do email.
+    * **Responder para:** preencha com o endereço de email para o qual o cliente poderá enviar uma resposta.
+    * __Tipo de conteúdo:__ selecione *Conteúdo da URL*.
+    * __Assunto:__ preencha com o assunto do email.
+    * __URL:__ insira o endereço de sua loja com as pastas em que o layout do carrinho abandonado foi configurado, com a tag do carrinho `{!carttag_SCORE}` ao final. Exemplo: `nomedaloja.com.br/CEM/Abandoned-Cart?refs={!carttag_SCORE}`.
+    * __Adicionar utm_source em todos os links com valor:__ preencha com *CEM*, para facilitar a identificação de compras pelo carrinho abandonado.
+    * __Sobrescrever utm_source:__ marque esta opção.
+
+13. Clique em `Salvar`.
+14. Crie um carrinho e feche a página para testar a trigger.
+
+  <div class="alert alert-warning">
+    <p>A sessão de uma página expira em 30 minutos. Somente depois desse período o Master Data inicia a contagem do período agendado para o disparo da trigger de Carrinho Abandonado. Logo, o tempo até o email chegar corresponde ao tempo da sessão (30 minutos) mais o período agendado na trigger.</p>
 </div>
 
-<blockquote><blockquote><ui>c. Em <b>Email body format</b>, selecione <b>Html</b>.</ui>
-
-<blockquote><blockquote><ui>d. Em <b>Sender's name</b>, insira o nome de sua loja.</ui>
-
-<blockquote><blockquote><ui>e. Em <b>Reply to</b>, preencha com o endereço de email no qual o cliente poderá responder caso tenha dúvidas.</ui>
-
-<blockquote><blockquote><ui>f. Em <b>Content type</b>, selecione <b>URL content</b>.</ui>
-
-<blockquote><blockquote><ui>g. Preencha o campo <b>Subject</b>.</ui>
+14. Uma vez que você houver recebido a mensagem do carrinho abandonado em seu email, no campo __Destinatário__ (passo 12), selecione a opção __CL:Email__ e  clique em `Adicionar email dinâmico`.
+15. Clique em `Salvar`.
 
-<blockquote><blockquote><ui>h. Em <b>URL</b>, insira o endereço de sua loja com as pastas em que o layout do carrinho abandonado foi configurado, com a tag do carrinho depois (?refs={!carttag_SCORE}). Ex.: nomedaloja.com.br/CEM/Abandoned-Cart?refs={!carttag_SCORE}.</ui>
-
-  ![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)
-
-<div class="alert alert-warning">O endereço da URL deve ser o real da loja, e não a URL com vtexcommercestable.
-</div>
-
-<blockquote><blockquote><ui>i. Em <b>Add utm_source to all links whose value is</b>, preencha com "CEM", para facilitar a identificação de compras pelo carrinho abandonado.</ui>
-
-<blockquote><blockquote><ui>j. Selecione a opção <b>Overwrite utm_source</b>.</ui>
-
-<blockquote><blockquote><ui>k. Clique no botão <b>Save</b>.</ui>
-
-<div class="alert alert-warning">A sessão de uma página expira em 30 minutos. Somente depois desse tempo consideramos o agendamento do disparo da trigger de Carrinho Abandonado. Ou seja, o tempo a ser considerado é o tempo da sessão + o agendamento da trigger.
-</div>
-
-![If positive tab](https://images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/d863f83956f876035351cd222a0482ad/If_positive_Tab.PNG)
-
-### Configuração para lojas VTEX IO
+## Configuração para lojas VTEX IO
 
 Para realizar a configuração da funcionalidade carrinho abandonado nas lojas VTEX IO, siga os seguintes passos:
 
 1. Instale o app [Abandoned Cart Service](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service) em sua loja.
 2. Configure o modelo de email na [Central de Mensagens](#configurar-modelo-de-email-na-central-de-mensagens). As especificações do JSON estão disponíveis em [Message Center Information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#message-center-information).
-3. Realize a [liberação do SPF](#liberacao-do-spf).
-4. [Configure a trigger](#configuracao-da-trigger) da mesma forma que nas lojas Legado até no Step 10. A partir do Step 11 (aba __If positive__), siga as instruções disponíveis em [Trigger configuration information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#trigger-configuration-information).
-
-![If positive tab IO](https://images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/ce32f7997824f648690edefe77ad03c0/If_positive_Tab_IO.PNG)
+3. Realize a [liberação do SPF](#liberar-spf).
+4. [Configure a trigger](#configurar-trigger) da mesma forma que nas lojas Legado até o passo 10. A partir do passo 11 (aba __Se positivo__), siga as instruções disponíveis em [Trigger configuration information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#trigger-configuration-information).
 
 ## Dúvidas frequentes
 
-### Minha trigger está configurada corretamente porém os e-mails não estão chegando para o e-mail de teste. O que verificar?
+### Minha trigger está configurada corretamente porém os emails não estão chegando para o email de teste. O que verificar?
 
 Para garantir o fluxo correto dos disparos, devemos conferir dois detalhes:
 
diff --git a/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
index 88660b170..f06796908 100644
--- a/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
@@ -17,7 +17,7 @@ subcategory:
 
 Este artigo tem como objetivo explicar como a app do inStore configura o AppLinking para as ações de `payment` e `payment-reversal` com as apps dos adquirentes.
 
-![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuração
 
diff --git a/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md b/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md
index 316fb7741..80461486c 100644
--- a/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md
+++ b/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md
@@ -3,7 +3,7 @@ title: 'Configurar boleto registrado Bradesco'
 id: bbnXBjvKOkWYiOosmASiA
 status: DRAFT
 createdAt: 2018-03-20T22:08:43.187Z
-updatedAt: 2022-12-23T20:13:39.299Z
+updatedAt: 2024-03-18T18:04:46.311Z
 publishedAt: 
 firstPublishedAt: 2018-03-21T17:27:23.026Z
 contentType: tutorial
@@ -15,6 +15,8 @@ legacySlug: configurar-boleto-registrado-bradesco
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Para configurar o boleto registrado do Bradesco, é necessário utilizar o conector do __Bradesco Registrado__ e configurar a condição de pagamento de boleto bancário. Desta forma, os boletos emitidos serão registrados pelo Bradesco.
 
 <div class="alert alert-info">
@@ -25,26 +27,26 @@ Para realizar a configuração, siga os passos abaixo:
 
 ## Configurar afiliação de gateway Bradesco Registrado
 
-1. Acesse o módulo __Pagamentos__.
-2. Clique em __Configurações__.
-3. Na aba __Afiliações de Gateways__, clique no botão __+__.
-4. Clique no conector __Bradesco Registrado__.
-5. Sigas as orientações do primeiro campo, __Cadastro Url de Notificações__.
-6. Preencha os campos de cadastro com os dados fornecidos pelo Bradesco (Campos *Merchant ID, Login (email), Chave de Segurança*).
-7. Em __Beneficiário__, preencha com a razão social da empresa beneficiária.
-8. Em __Carteira__, verifique com o Bradesco se você é um *cliente antigo (25)* ou um *cliente novo (26)*.
-9. No campo __Nosso numero prefixo__, preencha com um número para identificar os códigos gerados pela VTEX.
-10. Em __Agência__, digite com o dado fornecido pelo __Bradesco__.
-11. No campo __Dias__, preencha com o número de dias para pagamento até a expiração do boleto.
-12. Em __Instruções__, preencha com orientações para o pagamento do boleto.
-13. Em __Boleto registrado__, marque *Sim* para exigir a autenticação do comprador.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Bradesco Registrado__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos de cadastro com os dados fornecidos pelo Bradesco (Campos __Merchant ID__, __Login (email)__ e __Chave de Segurança__).
+5. Em __Beneficiário__, preencha com a razão social da empresa beneficiária.
+6. Em __Carteira__, verifique com o Bradesco se você é um *cliente antigo (25)* ou um *cliente novo (26)*.
+7. No campo __Nosso numero prefixo__, preencha com um número para identificar os códigos gerados pela VTEX.
+8. Em __Agência__, digite a informação fornecida pelo __Bradesco__.
+9. No campo __Dias__, preencha com o número de dias para pagamento até a expiração do boleto.
+10. Em __Instruções__, preencha com orientações para o pagamento do boleto.
+11. Em __Boleto registrado__, marque *Sim* para exigir a autenticação do comprador.
+12. Clique em `Salvar`.
 
 ## Configurar a condição de pagamento Boleto Bancário
 
-1. Acesse o módulo __PCI Gateway__.
-2. Clique em __Configurações__.
-3. Na aba __Condições de Pagamento__, clique no botão __+__.
-4. Na seção __Boleto__, selecione a opção __Boleto Bancário__.
-5. Preencha o nome da condição de pagamento e selecione a afiliação de gateway configurada acima (__Bradesco Registrado__).
-6. Caso deseje, você pode configurar uma [condição especial](/pt/tutorial/condicoes-especiais/) para essa condição de pagamento.
-7. Clique no botão __Salvar__.
+1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
+2. Na aba __Condições de Pagamento__, clique no botão `+`.
+3. Na seção __Boleto__, selecione a opção __Boleto Bancário__.
+4. Preencha o nome da condição de pagamento e selecione a afiliação de gateway configurada acima (__Bradesco Registrado__).
+5. Caso deseje, você pode configurar uma [condição especial](https://help.vtex.com/pt/tutorial/condicoes-especiais/) para essa condição de pagamento.
+6. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o conector Boleto Registrado Bradesco pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
diff --git a/docs/tutorials/pt/setting-up-braspag-gateway.md b/docs/tutorials/pt/setting-up-braspag-gateway.md
index fab69ce8f..99f840989 100644
--- a/docs/tutorials/pt/setting-up-braspag-gateway.md
+++ b/docs/tutorials/pt/setting-up-braspag-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar o gateway Braspag'
 id: 7tQmfLMvtYEsWoaaAaeKSC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-27T18:21:37.603Z
-updatedAt: 2023-03-29T01:03:06.303Z
-publishedAt: 2023-03-29T01:03:06.303Z
+updatedAt: 2023-09-19T14:26:39.079Z
+publishedAt: 
 firstPublishedAt: 2018-02-27T18:52:38.519Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/setting-up-conductor-gateway.md b/docs/tutorials/pt/setting-up-conductor-gateway.md
index 18890d8ca..41cfdbc18 100644
--- a/docs/tutorials/pt/setting-up-conductor-gateway.md
+++ b/docs/tutorials/pt/setting-up-conductor-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Conductor'
 id: Q5Ezi95TSEyE2GCQSs8ak
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-05-02T17:09:15.090Z
-updatedAt: 2023-03-29T00:55:20.862Z
-publishedAt: 2023-03-29T00:55:20.862Z
+updatedAt: 2024-03-18T18:11:12.675Z
+publishedAt: 
 firstPublishedAt: 2018-05-02T18:38:56.879Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-conductor
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A Conductor é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) que atua há mais de 20 anos com o processamento de pagamentos. Na VTEX, ela pode ser configurada para processar pagamentos realizados com __cartões de crédito com bandeira própria__.
 
 Para habilitar a Conductor na sua loja, siga os passos abaixo:
 
-## Configurar afiliação de gateway Conductor
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Conductor__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Conductor__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __External Service Url__, configure a url externa que vai estar associada a `/pvt/payments?an={AccoutName}`.
 5. Preencha os campos de cadastro com os dados fornecidos pela Conductor (campos _appKey_ e _appToken_).
 6. Em __Implements Installments Service__, escolha se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Se escolher a opção _yes_, o sistema vai utilizar a url configurada no campo __Installments Service Url__.
diff --git a/docs/tutorials/pt/setting-up-cybersource-antifraud.md b/docs/tutorials/pt/setting-up-cybersource-antifraud.md
index 4e5cec7d6..c0489a330 100644
--- a/docs/tutorials/pt/setting-up-cybersource-antifraud.md
+++ b/docs/tutorials/pt/setting-up-cybersource-antifraud.md
@@ -3,8 +3,8 @@ title: 'Configurar antifraude CyberSource'
 id: 2Z88QmpRAsWmI0qaCo4aQg
 status: PUBLISHED
 createdAt: 2018-04-30T18:08:44.396Z
-updatedAt: 2023-03-26T21:48:46.023Z
-publishedAt: 2023-03-26T21:48:46.023Z
+updatedAt: 2024-03-15T15:29:09.166Z
+publishedAt: 2024-03-15T15:29:09.166Z
 firstPublishedAt: 2018-04-30T20:25:40.199Z
 contentType: tutorial
 productTeam: Financial
@@ -25,29 +25,32 @@ Se você estiver procurando mais detalhes sobre o __gateway__ CyberSource, leia
 Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de efetuar o Passo 6. desta seção.
 </div>
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __CyberSource__ que fica na seção _ANTIFRAUDES_.
-4. Configure a URL `https://{store}.vtexpayments.com.br/api/pub/cybersource/antifraud/notification` no site da CyberSource, substituindo `{store}` pelo store name da sua loja. Isso vai habilitar as notificações quando houver alteração de status de um pedido.
-5. Configure o device fingerprint no Google Tag Manager usando [este artigo do Help](/pt/faq/como-configurar-o-device-finger-print-para-braspag-cybersource).
-6. Preencha os campos de cadastro com os dados fornecidos pela CyberSource (campos _ID da loja no Cybersource_ / _Nome de usuário no CyberSource_ e _Sua senha no Cybersource_).
-7. No campo __Nome da sua empresa__, informe a razão social da sua loja.
-8. Em __CNPJ da sua empresa__, diga o número do CNPJ da sua loja.
-9. Em __Certificado privado (.p12)__, faça o upload de um certificado privado válido (gerado por você, usando uma certificadora ou um software especializado), com extensão .p12 e chave.
-10. No campo __Senha do certificado privado__, informe a senha criada para acessar o certificado.
-11. Em __Merchant Key ID__ e __Merchant Secret Key__, informe os dados fornecidos pela CyberSource para acessar a API de relatórios.
-12. Em __Documento Opcional__, selecione se é necessário enviar o documento para a análise de fraude.
-13. Em __Enviar transações autenticadas?__, escolha se deseja enviar para análise do antifraude todas as transações ou somente aquelas que não são autenticadas.
-14. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Cybersource__ na barra de busca e clique sobre o nome do provedor.
+4. Caso deseje modificar o nome de identificação a ser exibido para o antifraude Cybersource na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+5. Configure a URL `https://{store}.vtexpayments.com.br/api/pub/cybersource/antifraud/notification` no site da CyberSource, substituindo `{store}` pelo store name da sua loja. Isso vai habilitar as notificações quando houver alteração de status de um pedido.
+6. Configure o device fingerprint no Google Tag Manager usando [este artigo do Help](/pt/faq/como-configurar-o-device-finger-print-para-braspag-cybersource).
+7. Preencha os campos __ID do comerciante no Cybersource__, __Nome de usuário no CyberSource__ e __Sua senha no Cybersource__ de acordo com os dados fornecidos pela CyberSource.
+8. Em __Nome da sua empresa__, informe a razão social da sua loja.
+9. Em __CNPJ da sua empresa__, insira o número do CNPJ da sua loja.
+10. Em __Certificado privado (.p12)__, faça o upload de um certificado privado válido (gerado por você, usando uma certificadora ou um software especializado), com extensão .p12 e chave.
+11. Em __Senha do certificado privado__, informe a senha criada para acessar o certificado.
+12. Em __Merchant Key ID__ e __Merchant Secret Key__, informe os dados fornecidos pela CyberSource para acessar a API de relatórios.
+13. Em __Documento Opcional__, selecione se é necessário enviar o documento para a análise de fraude.
+14. Em __Enviar transações autenticadas?__, escolha se deseja enviar para análise do antifraude todas as transações ou somente aquelas que não são autenticadas.
+15. Clique em `Salvar`.
 
 ## Associar antifraude a uma condição de pagamento
+
 Depois de configurar o antifraude da CyberSource, ele vai estar disponível para ser usado na sua loja. Para isso, você deve associá-lo às condições de pagamento, seja as que já estão configuradas ou aquelas que você ainda vai disponibilizar.
 
-1. Já dentro das __Configurações__ do módulo Pagamentos, clique na aba __Condições de Pagamento__.
-2. Clique sobre a condição desejada ou [crie uma nova condição de pagamento](/pt/tutorial/condicoes-de-pagamento).
-3. Marque a opção __Usar antifraude__.
-4. Selecione a CyberSource.
-5. Clique no botão __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre a condição desejada ou [crie uma nova condição de pagamento](/pt/tutorial/condicoes-de-pagamento).
+5. Marque a opção __Usar antifraude__.
+6. Selecione a CyberSource.
+7. Clique em `Salvar`.
 
 <div class="alert alert-warning">
 Para que uma transação passe pela análise do antifraude, <strong>a condição de pagamento utilizada pelo cliente precisa estar associada a ele</strong>.
diff --git a/docs/tutorials/pt/setting-up-cybersource-gateway.md b/docs/tutorials/pt/setting-up-cybersource-gateway.md
index 71f9c310f..33d22ecf7 100644
--- a/docs/tutorials/pt/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/pt/setting-up-cybersource-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar gateway CyberSource'
+title: 'Configurar gateway CyberSource IO'
 id: 6nhvUTrLxeacsoYG6GkGM
 status: PUBLISHED
 createdAt: 2018-04-30T17:34:57.517Z
-updatedAt: 2023-03-29T00:33:54.554Z
-publishedAt: 2023-03-29T00:33:54.554Z
+updatedAt: 2024-04-22T14:35:34.191Z
+publishedAt: 2024-04-22T14:35:34.191Z
 firstPublishedAt: 2018-04-30T20:20:44.704Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,212 @@ legacySlug: configurar-gateway-cybersource
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A CyberSource é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que oferece diversas soluções para ajudar sua loja a gerenciar pagamentos. Entre elas está um __gateway__, que oferece integração com a plataforma VTEX. Se você estiver procurando mais detalhes sobre o __antifraude__ CyberSource, leia [este artigo do Help](/pt/tutorial/configurar-antifraude-cybersource).
+A Cybersource é uma empresa que oferece diversas soluções para auxiliar a gestão de pagamentos da sua loja. Entre elas estão um [gateway](https://help.vtex.com/pt/tutorial/o-que-e-um-gateway-de-pagamentos) e um [antifraude](https://help.vtex.com/pt/tutorial/o-que-e-antifraude), ambos com integrações disponíveis na VTEX.
 
-Para configurar o __gateway__ da CyberSource, siga os passos abaixo:
+Caso deseje maiores informações sobre como integrar o antifraude da Cybersource em sua loja, acesse [Configurar antifraude Cybersource](https://help.vtex.com/pt/tutorial/configurar-antifraude-cybersource--2Z88QmpRAsWmI0qaCo4aQg).
 
-## Configurar afiliação de gateway CyberSource
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __CyberSource__.
-4. Preencha os campos de cadastro com os dados fornecidos pela CyberSource (campos _Id do Merchant / Id do comerciante CyberSource_, _Username / Nome do Usuário usado no painel da Cybersource_ e _Password / Senha usada no painel da Cybersource_).
-5. No campo __Nome da Empresa__, informe a razão social da sua loja.
-6. Em __CNPJ da Empresa__, diga o número do CNPJ da sua loja.
-7. No campo __Moeda__, escolha a moeda que será usada nas transações da sua loja.
-8. Em __Certificado privado (.p12)__, faça o upload de um certificado privado válido (gerado por você, usando uma certificadora ou um software especializado), com extensão .p12 e chave.
-9. No campo __Senha do certificado privado__, informe a senha (isto é, o seu _Id do Merchant / Id do comerciante CyberSource_).
-10. Clique em __Salvar__.
+Para utilizar o gateway da Cybersource IO em sua loja, as seguintes ações são necessárias:
+
+1. [Instalar os aplicativos Cybersource IO (VTEX IO CLI)](#instalando-apps-da-cybersource)
+2. [Criar as chaves de autenticação na Cybersource (Cybersource environment)](#criando-chaves-de-autenticacao-na-cybersource)
+3. [Realizar as configurações do app Cybersource (Admin VTEX)](#configurando-o-app-cybersource-io)
+4. [Configurar o gateway Cybersource (Admin VTEX)](#configurando-o-gateway-cybersource)
+5. [Configurar a condição de pagamento (Admin VTEX)](#configurando-condicao-de-pagamento)
+6. [Configurar o Device Fingerprint (opcional)](#configurar-cybersource-io-device-fingerprint-opcional)
+7. [Configurar campos do merchant (opcional)](#configurar-campos-do-merchant-opcional)
+
+## Instalando apps da Cybersource 
+
+Os seguintes apps da Cybersource devem ser instalados na conta de sua loja:
+
+- __vtex.cybersource-ui__
+- __vtex.cybersource__
+- __vtex.cybersource-payer-auth__
+
+<div class="alert alert-warning">
+  Caso você pretenda utilizar o sistema de antifraude da Cybersource, mas deseja transacionar os pagamentos em um gateway que não seja o da Cybersource, será necessário instalar o app <b>vtex.cybersource-fraud</b>.
+  </div>
+
+Saiba mais como instalar aplicativos em uma conta VTEX em [Installing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app). 
+
+## Criando chaves de autenticação na Cybersource 
+
+Após a instalação dos apps você deve criar as chaves de autenticação no ambiente da Cybersource. 
+
+<div class="alert alert-warning">
+  As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Cybersource para informações atualizadas.
+  </div>
+
+Siga os passos abaixo:
+
+1. Acesse o [painel EBC](https://businesscenter.cybersource.com/ebc2/) (Enterprise Business Center) da Cybersource com os seus dados.
+2. No painel de navegação lateral, selecione __Payment Configuration > Key Management__.
+3. Clique em __Generate Key__.
+4. Em __REST APIs__, selecione a opção __REST - Shared Secret__.
+5. Clique em __Generate Key__.
+6. Clique em __Download key__ ou copie as informações das chaves utilizando a função copiar localizada a frente dos campos __Key__ e __Shared Secret__.
+
+## Configurando o app Cybersource IO 
+
+Com as chaves de autenticação disponíveis, é o momento de realizar a configuração do app Cybersource IO no Admin. 
+
+![Cybersource Admin settings PT](//images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/635fe1762fa5be2e9c6c118f5245cb39/Cybersource_Admin_settings_PT.JPG)
+
+Siga os passos abaixo para configurar o app Cybersource IO:
+
+1. No Admin VTEX, acesse __Aplicativos > Apps Instalados > Cybersource__, ou digite __Cybersource__ na barra de busca no topo da página.
+2. Na aba __Admin Settings__, preencha ou selecione os campos abaixo:
+<br>
+<ul>
+<br>
+    	<li><b>ID do comerciante</b>: o seu merchant ID na Cybersource.</li>
+    	<li><b>Chave do comerciante</b> e <b>Chave secreta compartilhada</b>: as duas chaves obtidas anteriormente no ambiente da Cybersource.</li>
+    	<li><b>Processor</b>: selecione a empresa que realizará o processamento do pagamento, ou clique em <b>Other</b> caso ela não esteja na lista.</li>
+    	<li><b>Region</b>: selecione uma das regiões, ou clique em <b>Other</b> caso a região desejada não esteja na lista.</li>
+    	<li><b>Sufixo de referência (opcional)</b>: por padrão, os pedidos no sistema Cybersource serão associados ao ID do grupo de pedidos VTEX, mas esta configuração pode ser usada para anexar um sufixo como “-01”.</li>
+    	<li><b>NSU personalizado (opcional)</b>: substituir NSU padrão por valor personalizado.</li>
+    	<li><b>Use o ID do pedido para impressão digital do dispositivo</b>: selecione se deseja utilizar o ID do pedido para impressão digital do dispositivo no lugar do ID da sessão.</li>
+    	<li><b>Ativar cálculos de impostos</b>: selecione se deseja utilizar a Cybersource como seu provedor de cálculo de impostos no checkout.</li>
+    	<li><b>Ativar lançamento de transações</b>: selecione se deseja ativar o lançamento de transações concluídas para questões de relatórios fiscais.</li>
+    	<li><b>Canais de vendas a serem excluídos da Cybersource (opcional)</b>: insira qualquer canal de venda de vendas em que não deseja utilizar as transações na Cybersource.</li>
+    	<li><b>Código do produto de envio (opcional)</b>: insira um código de produto para fins de cálculo do imposto de envio.</li>
+    	<li><b>Regiões de nexo fiscal (opcional)</b>: insira uma lista de regiões onde os impostos devem ser recolhidos.</li>
+</ul>
+3. Clique em __Salvar configurações__.
+
+## Configurando o gateway Cybersource
+
+Para configurar o gateway Cybersource, siga os passos abaixo: 
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Cybersource IO__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, não é necessário preencher os campos __Chave de aplicação__ e __Token de aplicação__.
+5. Caso deseje modificar o nome de identificação a ser exibido para o gateway Cybersource na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o gateway em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada para ser realizada após 4 dias (ou se o pedido for faturado, o que ocorrer primeiro).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Em __Campos do provedor__, preencha ou selecione os campos abaixo:
+<ul>
+<br>
+    	<li><b>Company Name</b>: nome da empresa.</li>
+      <li><b>Company Tax id</b>: CNPJ da empresa.</li>
+  <li><b>Capture Setting</b>: selecione <b>Delayed Capture</b> para ocorrer o procedimento padrão da plataforma VTEX (chamadas separadas para autenticação e captura) ou <b>Immediate Capture</b>, onde será enviada uma única chamada de autenticação e captura à Cybersource quando o pedido for realizado.</li>
+    	<li><b>Payer Authentication</b>: se desejar ativar esta opção, o <a href="https://www.cybersource.com/en/solutions/fraud-and-risk-management/payer-authentication-for-3d-secure.html">3-D Secure Payer Authentication da Cybersource</a> deverá ser utilizado.</li>
+    	<li><b>Capture Delay</b> e <b>Capture Delay Interval</b>: determine o período antes da captura automática.</li>
+    	<li><b>Using Decision Manager</b>: selecione se o <a href="https://www.cybersource.com/apac/en/solutions/fraud-and-risk-management/decision-manager.html">CyberSource Decision Manager</a> estará ativo em sua conta.</li>
+      <li><b>Authorized Payments Flagged by Decision Manager</b>: quando o status é Authorized, Fraud Reject, selecione as seguintes opções:</li>
+      <blockquote><li><b>Treat as Successful Authorizations</b>: para aceitar o pedido.</li></blockquote>
+      <blockquote><li><b>Treat as Failed Authorizations</b>: para negar o pedido.</li></blockquote>
+      <blockquote><li><b>Treat as Pending Authorizations</b>: mantém o pedido enquanto é aguardada uma decisão final.</li></blockquote>  
+</ul>
+9. Os campos __Merchant Id__, __Merchant Key__ e __Shared Secret Key__ devem ser deixados em branco, pois serão utilizados os valores definidos no passo 2 da seção [Configurando o app Cybersource IO](#configurando-o-app-cybersource-io). Caso os campos sejam preenchidos com algum valor, estes irão sobrescrever as informações inseridas no passo 2.
+10. Cliquem em __Salvar__.
+
+## Configurando condição de pagamento
+
+Para processar pagamentos com cartões de crédito por meio da Cybersource, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão +.
+3. Clique sobre o nome do cartão de crédito desejado.
+4. Preencha o campo __Nome da condição__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Em __Processar com o provedor__ selecione a opção __Cybersource - IO__.
+7. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__ e escolha o provedor de sua preferência.
+8. Se desejar, você também poderá configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+9. Clique em __Salvar__.
+
+<div class="alert alert-warning">
+  Se você criou anteriormente condições de pagamento com cartão de crédito para outros gateways (incluindo o provedor Cybersource legado), poderá definir essas condições como <b>Inativas</b>. As transações em andamento iniciadas nesse provedor ainda serão processadas por ele, mesmo que esteja inativo. Apenas novas transações serão processadas pelo novo provedor Cybersource IO. Caso você precise reverter para o provedor anterior por qualquer motivo, basta definir as respectivas condições de pagamento como <b>Ativas</b> e as condições de pagamento do Cybersource IO como <b>Inativas</b>.
+  </div>
+
+## Configurar Cybersource IO Device Fingerprint (opcional)
+
+Device Fingerprint é um identificador que atua no processamento de um pagamento, tendo como objetivo melhorar a análise do risco de fraude em cada transação. 
+
+Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
+
+<div class="alert alert-info">
+Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
+</div>
+
+Para configurar o Device Fingerprint da Cybersource IO, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Storefront > Checkout__, ou digite __Checkout__ na barra de busca no topo da página.
+2. Clique no ícone <i class="fas fa-cog" alt="engrenagem azul"></i> do site desejado.
+3. No menu de opções azul localizado na parte superior da página, clique em __Código__.
+4. Em __Arquivos__, clique sobre __checkout5.custom.js__.
+5. Insira o código abaixo no campo de texto e clique em `Salvar`.
+
+    function addsDeviceFingerPrint() {
+      if (!window.vtex) return;
+      if (window.vtex.deviceFingerprint) return;
+      $.ajax({
+type: 'get',
+async: true,
+url: rootPath() + '/api/sessions?items=*'
+      }).then(function(response) {
+var ORG_ID = "{{ORG_ID}}";
+var MERCHANT_ID = "{{MERCHANT_ID}}";
+console.log('session', response);
+window.vtex.deviceFingerprint = response.id;
+var sessionId = response.id || "CYBERSOURCE";
+var script = document.createElement("script");
+script.type = "text/javascript";
+script.src = `https://h.online-metrix.net/fp/tags.js?org_id=${ORG_ID}&session_id=${MERCHANT_ID}${sessionId}`;
+document.head.appendChild(script);
+var noScript = document.createElement("noscript");
+var iframe = document.createElement("iframe");
+iframe.style = "width: 100px; height: 100px; border: 0; position: absolute; top: -5000px;";
+iframe.src = `https://h.online-metrix.net/fp/tags?org_id=${ORG_ID}&session_id=${MERCHANT_ID}${sessionId}`;
+noScript.appendChild(iframe);
+document.body.appendChild(noScript);
+      })
+    }
+
+## Configurar campos do merchant (opcional)
+
+Adicionalmente, você pode definir campos customizados que serão incluídos em pedidos encaminhados da VTEX para a Cybersource. 
+
+![Cybersource Admin merchant define fields PT](//images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/107a5ce54fb0f218e8bed5918499d9b4/Cybersource_Admin_merchant_define_fields_PT.JPG)
+
+Veja abaixo como criar estes campos:
+
+1. No Admin VTEX, acesse __Aplicativos > Apps Instalados > Cybersource__, ou digite __Cybersource__ na barra de busca no topo da página.
+2. Na aba __Campos definidos pelo comerciante__, em __Informações definidas pelo comerciante__, você pode inserir os campos seguindo as seguintes regras: 
+<ul>
+<br>
+    	<li>Quaisquer valores fora das chaves <b>{{}}</b> serão considerados como valor direto.</li>
+      <li>Quaisquer valores entre <b>{{}}</b> devem estar no seguinte formato <i>Palavra de Referência|Palavra de Modificação|Valores</i>.</li>
+      <li>Todas as <b>palavras de referência</b> podem ser encontradas no menu suspenso <b>Mostrar todas as palavras referenciáveis</b>:</li>
+      <blockquote><li>As <b>palavras de referência</b> podem ser deixadas em branco se a <b>Palavra de Modificação</b> e os <b>Valores</b> estiverem presentes</b>.</li></blockquote>
+      <blockquote><li>A <b>palavra de referência</b> diferencia maiúsculas de minúsculas.</li></blockquote>
+    	<li>As <b>palavras de modificação</b> devem ser do tipo <b>Pad</b>, <b>Date</b>, <b>Trim</b>, <b>Age</b>, ou <b>Equals</b>. Veja abaixo as características ao cadastrar cada um deles:</li>
+      <blockquote><li><b>Pad</b>: os <b>Valores</b> devem estar no formato de <b>comprimento desejado:caractere preenchido</b>.</li></blockquote>
+      <blockquote><blockquote><li>O <b>caractere preenchido</b> deve ser um valor único. Por exemplo, <i>9:x</i> resultará em um comprimento desejado de 9, e irá preencher espaços vazios com x.</li></blockquote></blockquote>
+      <blockquote><blockquote><li>Se o valor do campo exceder o comprimento desejado, o campo será cortado.</li></blockquote></blockquote>         
+<br>       
+      <blockquote><li><b>Date</b>: os <b>Valores</b> devem estar no formato dd/MM/aaaa ou qualquer combinação dele.</li></blockquote>
+      <blockquote><blockquote><li><b>M</b> para mês deve ser maiúsculo. Este formato pode ser ordenado conforme desejar, tal como, <b>aaaa/MM</b> ou <b>aaaa</b> ou <b>dd/aaaa/MM</b>.</li></blockquote></blockquote>
+      <blockquote><li><b>Trim</b>: limitará o comprimento máximo do valor do campo sem adicionar caracteres de preenchimento.</li></blockquote>
+      <blockquote><li><b>Age</b>: retornará a diferença entre a data atual e o valor do campo usando o formato Timespan.</li></blockquote>
+      <blockquote><li><b>Equals</b>: retornará o valor booleano de uma comparação de string entre o valor do campo e o valor de comparação.</li></blockquote>
+<br>
+    	<li>Cada nova linha é um considerada como um novo campo definido pelo comerciante.</li>
+
+Exemplos:
+
+| Valor inserido no Admin em `Informações definidas pelo comerciante`    | Cenário simulado     | Resultado     |
+| ---------- | ---------- | ---------- |
+| `969{{Reference|PAD|9:0}}`       | Quando `Reference` é 6023       | 969602300000       |
+| `{{OrderId}}-01`       | Quando `OrderId` é 124578       | 124578-01       |
+| `{{MiniCart.Buyer.LastName}},{{MiniCart.Buyer.FirstName}}`       | Quando o nome do comprador (`Buyer`) é John Doe       | Doe,John       |        
 
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, o gateway da CyberSource estará configurado na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ele estará disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com a CyberSource). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
diff --git a/docs/tutorials/pt/setting-up-firstdata-acquirer.md b/docs/tutorials/pt/setting-up-firstdata-acquirer.md
index 487f32a3b..abf0225d5 100644
--- a/docs/tutorials/pt/setting-up-firstdata-acquirer.md
+++ b/docs/tutorials/pt/setting-up-firstdata-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar adquirente FirstData'
 id: 4mW6gU343eWY6c8m6ocO0i
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-26T21:04:20.319Z
-updatedAt: 2023-03-21T18:04:57.904Z
-publishedAt: 2023-03-21T18:04:57.904Z
+updatedAt: 2024-03-18T18:23:46.570Z
+publishedAt: 
 firstPublishedAt: 2018-04-26T22:08:51.029Z
 contentType: tutorial
 productTeam: Financial
@@ -15,49 +15,51 @@ legacySlug: configurar-adquirente-firstdata
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A FirstData, é uma [adquirente](https://help.vtex.com/pt/tutorial/o-que-e-um-adquirente) disponível exclusivamente para o mercado brasileiro e argentino.
-
-Para configurar a solução, siga as etapas abaixo:
-
-1.  Acesse o **Admin** VTEX.    
-2.  No módulo **Pagamentos**, clique em **Configurações**.    
-3.  Acesse **Afiliações de gateway** e clique no sinal verde “**+**”    
-4.  Busque por **FirstData** e selecione o conector.    
-5.  Preencha os campos solicitados com as seguintes informações:
-
--   **Nome de usuário:** ID do usuário que tem permissão de acesso ao Web Service API. Essa informação é necessária para realizar a autorização básica  
--   **Senha para autorização básica:** Senha geral do usuário do FirstData (o mesmo citado no campo “Nome de usuário”), que será usada na autorização.  
--   **StoreId:** Código que é enviado no arquivo .xml das chamadas. 
--   **País:** País de origem.  
--   **Moeda:** Moeda do país de origem. 
--   **SoftDescriptor:** Texto que identificará a compra no extrato do seu cliente.  
--   **Senha do certificado privado:** Senha do certificado na sua loja. 
--   **Certificado privado (.p12):** Faça o upload de um certificado privado válido (gerado por você, usando uma certificadora ou um software especializado), com extensão .p12 e chave.
-- **Plan Ahora:** Se você ativou as opções de plano de governo Ahora com a FirstData, escolha "True",caso contrário, escolha "False". Para mais detalhes sobre o plano Ahora, [clique aqui](http://planesahora.gob.fiservargentina.com/).
-
-  -   **Plan Ahora 3:** Para descontos em parcelamentos realizados em 3X.
-  -   **Plan Ahora 6:** Para descontos em parcelamentos realizados em 6X.
-  -   **Plan Ahora 10:** Para descontos em parcelamentos realizados em 10X.
-  -   **Plan Ahora 12:** Para descontos em parcelamentos realizados em 12X.
-  -   **Plan Ahora 18:** Para descontos em parcelamentos realizados em 18X.
-  -   **Plan Ahora 24:** Para descontos em parcelamentos realizados em 24X.
-  -   **Plan Ahora 30:** Para descontos em parcelamentos realizados em 30X.
-
-- **Auto Settle:** Configure essa opção para definir quando será realizada a captura automática do pagamento.
-
-  -   **Imediatamente:** A captura será realizada logo após a autorização do pagamento.
-  -   **1 a 30 dias:** A captura será realizada após a autorização do pagamento, levando em conta o número de dias selecionado.
-  -   **Desativado:**  A captura automática será desligada e não terá o comportamento padrão da plataforma (4 dias para captura). Dessa forma, o pedido somente será capturado no momento em
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
+Na VTEX, é possível realizar a integração com a FirstData. Com este provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito e Plan Ahora (sistema de pagamento argentino).
+
+Para configurar a FirstData, siga as etapas abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __FirstData__ na barra de busca e clique sobre o nome do provedor.
+4.  Preencha os campos solicitados com as seguintes informações:
+
+- __Nome de usuário__: ID do usuário que tem permissão de acesso ao Web Service API. Essa informação é necessária para realizar a autorização básica.  
+- __Senha para autorização básica__: Senha geral do usuário do FirstData (o mesmo citado no campo “Nome de usuário”), que será usada na autorização.  
+- __ID da loja__: Código que é enviado no arquivo .xml das chamadas. 
+- __País__: País de origem.  
+- __Moeda__: Moeda do país de origem. 
+- __Descrição da transação__: Texto que identificará a compra no extrato do seu cliente. 
+- __Senha do certificado privado__: Senha do certificado na sua loja. 
+- __Certificado privado (.p12)__: Faça o upload de um certificado privado válido (gerado por você, usando uma certificadora ou um software especializado), com extensão .p12 e chave.
+- __Plan Ahora__: Se você ativou as opções de plano de governo Ahora com a FirstData, escolha "True",caso contrário, escolha "False". Para mais detalhes sobre o plano Ahora, [clique aqui](http://planesahora.gob.fiservargentina.com/).
+
+  - __Plan Ahora 3__: Para descontos em parcelamentos realizados em 3X.
+  - __Plan Ahora 6__: Para descontos em parcelamentos realizados em 6X.
+  - __Plan Ahora 10__: Para descontos em parcelamentos realizados em 10X.
+  - __Plan Ahora 12__: Para descontos em parcelamentos realizados em 12X.
+  - __Plan Ahora 18__: Para descontos em parcelamentos realizados em 18X.
+  - __Plan Ahora 24__: Para descontos em parcelamentos realizados em 24X.
+  - __Plan Ahora 30__: Para descontos em parcelamentos realizados em 30X.
+
+- __Auto Settle__: Configure essa opção para definir quando será realizada a captura automática do pagamento.
+
+  - __Imediatamente__: A captura será realizada logo após a autorização do pagamento.
+  - __1 a 30 dias__: A captura será realizada após a autorização do pagamento, levando em conta o número de dias selecionado.
+  - __Desativado__: A captura automática será desligada e não terá o comportamento padrão da plataforma (4 dias para captura). Dessa forma, o pedido somente será capturado no momento em
 que for faturado, ou se a [captura manual](https://developers.vtex.com/docs/api-reference/payments-gateway-api#post-/api/pvt/transactions/-transactionId-/settlement-request) for acionada.
 
-- **Change Margin:** Defina a margem percentual para um pagamento ser modificado para um valor maior do que o inicialmente autorizado. Se a compra foi fechada e autorizada por BRL 100,00, por exemplo, mas houver uma [mudança no pedido](https://help.vtex.com/pt/tutorial/change-mudanca-em-pedidos--3d1XLIgPQcwaKGyMiWaYog?&utm_source=autocomplete) para um valor maior antes da captura, este conector permite que o aumento seja de até 20% do inicialmente autorizado.
+- __Change Margin__: Defina a margem percentual para um pagamento ser modificado para um valor maior do que o inicialmente autorizado. Se a compra foi fechada e autorizada por BRL 100,00, por exemplo, mas houver uma [mudança no pedido](https://help.vtex.com/pt/tutorial/change-mudanca-em-pedidos--3d1XLIgPQcwaKGyMiWaYog?&utm_source=autocomplete) para um valor maior antes da captura, este conector permite que o aumento seja de até 20% do inicialmente autorizado.
 
 <ul>
-6. Clique em <b>Salvar</b>.
+5. Clique em <b>Salvar</b>.
   </ul>
 
-### Configurar condições de pagamento
+Para configurar os métodos de pagamento a serem processados pela FirstData, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Depois de concluir todas as etapas, a FirstData estará configurada e pronta para ser utilizada em sua loja.
+Depois de seguir os passos indicados, o conector FirstData pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
 
-Para associá-la a uma condição de pagamento, leia o artigo [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
diff --git a/docs/tutorials/pt/setting-up-getnet-acquirer-with-egetnet-connector.md b/docs/tutorials/pt/setting-up-getnet-acquirer-with-egetnet-connector.md
index 14733ab56..72b27d3a5 100644
--- a/docs/tutorials/pt/setting-up-getnet-acquirer-with-egetnet-connector.md
+++ b/docs/tutorials/pt/setting-up-getnet-acquirer-with-egetnet-connector.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar adquirente Getnet com o conector Egetnet'
+title: 'Configurar pagamento com Egetnet'
 id: 75kwGKPKnK8mwiEmQGYiWq
 status: PUBLISHED
 createdAt: 2018-04-27T13:55:54.133Z
-updatedAt: 2023-03-29T00:59:42.828Z
-publishedAt: 2023-03-29T00:59:42.828Z
+updatedAt: 2024-03-14T18:03:01.948Z
+publishedAt: 2024-03-14T18:03:01.948Z
 firstPublishedAt: 2018-04-27T16:07:30.586Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,19 @@ legacySlug: configurar-adquirente-getnet-com-o-conector-egetnet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A Getnet, um dos maiores [adquirentes](/pt/tutorial/o-que-e-um-adquirente) do Brasil, pode ser configurada na sua loja usando o conector Egetnet. Recomendamos que você utilize esse conector para ter acesso à integração mais atual e às novas features da Getnet.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Egetnet. Por meio deste provedor, sua loja pode realizar vendas por cartão de crédito, débito, boleto e PIX.
 
-Para configurar a Getnet com o conector Egetnet, siga os passos abaixo:
+Para configurar a Egetnet, siga os passos abaixo:
 
-## Configurar afiliação de gateway Egetnet
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Egetnet__.
-4. No campo __Application Key__, informe a chave da aplicação, fornecida pela Getnet.
-5. Em __Application Token__, preencha o campo com o token fornecido pela Getnet.
-6. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Egetnet__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Egetnet.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Egetnet na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
 
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, o conector Egetnet vai estar configurado na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ele vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com o Egetnet). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
+Para configurar os métodos de pagamento a serem processados pela Egetnet, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, Egetnet pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md b/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md
new file mode 100644
index 000000000..6cea1dd0b
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md
@@ -0,0 +1,30 @@
+---
+title: 'Configurar integração do Intelligent Search com o Catálogo'
+id: 3Nt5cIdwISSlzVtnYfLeIH
+status: PUBLISHED
+createdAt: 2024-06-27T16:56:47.833Z
+updatedAt: 2024-06-27T17:01:32.662Z
+publishedAt: 2024-06-27T17:01:32.662Z
+firstPublishedAt: 2024-06-27T16:57:41.295Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: configurar-integracao-do-intelligent-search-com-o-catalogo
+locale: pt
+legacySlug: integracoes
+subcategory: 1EmKjP83dy0RWD9GzZkYsG
+---
+
+A página **Configurações da loja** > **Intelligent Search** > **Integrações** no Admin VTEX é responsável pela indexação inicial do Catálogo com o VTEX Intelligent Search. Após instalar o aplicativo, esse será o primeiro passo para integrá-lo com o Catálogo.
+
+Siga as instruções para iniciar o processo de integração:
+
+1. No Admin VTEX, acesse **Configurações da loja**, ou digite **Configurações da loja** na barra de busca no topo da página.
+2. Em **Intelligent Search**, clique em **Integrações**.
+4. Clique em `Iniciar`.
+
+O processo de indexação será iniciado. Uma vez concluído, a tela ilustrada a seguir será exibida.
+
+![integracoes-is](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/43b9e3474b8f3046405278e34266e0fc/integracoes-is.PNG)
+
+Não é necessário repetir esse processo. Depois de iniciar a integração, é possível acompanhar o status da indexação na página [Histórico da indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md b/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md
index c4f7f1d47..9f40a9f12 100644
--- a/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md
+++ b/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto registrado Itaú (Itaú Registrado)'
 id: 6MEHf1oDTOkuWM2CaYi4gu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-11-30T18:23:45.696Z
-updatedAt: 2021-07-08T19:14:45.697Z
-publishedAt: 2021-07-08T19:14:45.697Z
+updatedAt: 2024-03-18T18:01:00.472Z
+publishedAt: 
 firstPublishedAt: 2018-12-11T17:59:44.827Z
 contentType: tutorial
 productTeam: Financial
@@ -15,28 +15,30 @@ legacySlug: configurar-boleto-registrado-itau-itau-registrado
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Para configurar o boleto registrado do Itaú, você pode escolher entre dois conectores diferentes: o __Boleto Itaú__ (também conhecido como __Itaú Registrado__ e que você vai aprender a configurar neste artigo) ou o [ItauShopline](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq). No caso do __Boleto Itaú__, a geração do boleto é feita de forma transparente (sem redirecionamento para o site do Itaú), mas a conciliação é feita através de arquivos.
 
 Depois de cadastrar uma dessas afiliações de gateway, você deverá configurar a condição de pagamento de boleto bancário. Assim, os boletos emitidos pela sua loja vão poder ser registrados pelo Itaú.
 
 ## Configurar afiliação de gateway Boleto Itaú (Itaú Registrado)
-1. No menu lateral, clique em __Pagamentos__, na seção __Transações__.
-2. Nas opções que se abrem, clique em __Configurações__.
-3. Na aba __Afiliações de Gateways__, clique no botão __+__.
-4. Clique no conector __Boleto Itaú__.
-5. Informe o nome da sua empresa no campo __Nome da Empresa__. Lembre-se de que essa é a informação que vai vir no campo _Beneficiário_ do boleto.
-6. No campo __CNPJ__, preencha com o número do CNPJ da sua empresa, sem pontuação.
-7. Preencha os dados bancários da sua empresa nos campos __Agência__ e __Número de Conta__.
-8. Em __Validade do boleto em dias__, escolha a quantidade de dias (contados a partir da geração do boleto) que seu cliente terá para fazer o pagamento.
-9. No campo __Instruções no boleto ao Caixa__, escreva as instruções que serão impressas no boleto.
-10. Preencha os campos de cadastro com os dados fornecidos pelo Itaú: _Portfólio ou Carteira_, _Convênio_ e _Código do Cedente_.
-11. Em __Endereço do Beneficiário__, informe o endereço comercial da sua empresa (respeitando o limite de até _200 caracteres_).
-12. No campo __Registrado?__, selecione a opção _Sim_. Ao fazer isso, novos campos vão surgir para você preencher.
-13. Em __Ambiente de Autenticação__, informe o valor `beta`.
-14. No campo __Tipo de Ambiente__, informe o valor `2`.
-15. Preencha os campos seguintes com os dados fornecidos pelo Itaú: _Id do cliente_, _Secret do cliente_ e _Chave do itau_.
-16. No campo __Dias para expiração da transação de boleto__, defina em quantos dias, depois do vencimento do boleto, a transação irá expirar.
-17. Clique no botão __Salvar__.
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BankInvoiceItau__ na barra de busca e clique sobre o nome do provedor.
+4. Informe o nome da sua empresa no campo __Nome da Empresa__. Lembre-se de que essa é a informação que vai vir no campo _Beneficiário_ do boleto.
+5. No campo __CNPJ__, preencha com o número do CNPJ da sua empresa, sem pontuação.
+6. Preencha os dados bancários da sua empresa nos campos __Agência__ e __Número de Conta__.
+7. Em __Validade do boleto em dias__, escolha a quantidade de dias (contados a partir da geração do boleto) que seu cliente terá para fazer o pagamento.
+8. No campo __Instruções no boleto ao Caixa__, escreva as instruções que serão impressas no boleto.
+9. Preencha os campos de cadastro com os dados fornecidos pelo Itaú: _Portfólio ou Carteira_, _Convênio_ e _Código do Cedente_.
+10. Em __Endereço do Beneficiário__, informe o endereço comercial da sua empresa (respeitando o limite de até _200 caracteres_).
+11. No campo __Registrado?__, selecione a opção _Sim_. Ao fazer isso, novos campos vão surgir para você preencher.
+12. Em __Ambiente de Autenticação__, informe o valor `beta`.
+13. No campo __Tipo de Ambiente__, informe o valor `2`.
+14. Preencha os campos seguintes com os dados fornecidos pelo Itaú: _Id do cliente_, _Secret do cliente_ e _Chave do itau_.
+15. No campo __Dias para expiração da transação de boleto__, defina em quantos dias, depois do vencimento do boleto, a transação irá expirar.
+16. Clique no botão __Salvar__.
 
 ## Configurar a condição de pagamento Boleto Bancário
 1. Depois de configurada a afiliação de gateway __Boleto Itau__, clique na aba __Condições de Pagamento__. 
diff --git a/docs/tutorials/pt/setting-up-itau-registered-ticket.md b/docs/tutorials/pt/setting-up-itau-registered-ticket.md
index 6d01b5c6b..780d6b928 100644
--- a/docs/tutorials/pt/setting-up-itau-registered-ticket.md
+++ b/docs/tutorials/pt/setting-up-itau-registered-ticket.md
@@ -3,8 +3,8 @@ title: 'Configurar boleto registrado Itaú (ItauShopline)'
 id: 3TqzCHPU7KIYGsOKuUeQcq
 status: PUBLISHED
 createdAt: 2018-02-28T15:50:53.154Z
-updatedAt: 2023-03-29T01:19:04.085Z
-publishedAt: 2023-03-29T01:19:04.085Z
+updatedAt: 2024-03-18T18:27:01.365Z
+publishedAt: 2024-03-18T18:27:01.365Z
 firstPublishedAt: 2018-02-28T19:38:07.445Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-boleto-registrado-itau
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Para configurar o boleto registrado do Itaú, você pode escolher entre dois conectores diferentes: o __ItauShopline__ (que você vai aprender a configurar neste artigo) ou o [Boleto Itaú (Itaú Registrado)](/pt/tutorial/configurar-boleto-registrado-itau-itau-registrado). No caso do __ItauShopline__, ele faz um redirecionamento para o site do Itaú e a conciliação do boleto é feita automaticamente.
 
 Depois de cadastrar uma dessas afiliações de gateway, você deverá configurar a condição de pagamento de boleto bancário. Assim, os boletos emitidos pela sua loja vão poder ser registrados pelo Itaú.
diff --git a/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md b/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
index f6476b529..2f0b3654b 100644
--- a/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
+++ b/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar boleto parcelado Provu (Lendico) como meio de pagamento'
 id: 1pRpPlkppLDEc1TVXTgrcu
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-12-02T10:58:09.076Z
-updatedAt: 2023-03-26T21:47:26.770Z
-publishedAt: 2023-03-26T21:47:26.770Z
+updatedAt: 2024-07-23T18:06:34.554Z
+publishedAt: 
 firstPublishedAt: 2020-12-02T12:54:57.731Z
 contentType: tutorial
 productTeam: Financial
@@ -36,6 +36,7 @@ Mas antes de prosseguirmos, lembre-se que a maioria das instruções a seguir se
 Caso você não tenha familiaridade com essa parte do Admin, recomendamos a leitura da nossa [track de primeiros passos](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG "track de primeiros passos") desse módulo.
 
 ### 1. Criação de chaves de acesso
+
 A Provu precisa ter acesso à sua loja para ter acesso às notas fiscais dos seus pedidos. Mais especificamente, ao módulo de Gerenciamento de Pedidos para, assim, pode realizar os processos legais e de auditoria.   
 
 Essas chaves de acesso são conhecidas como AppKey e AppToken e o  passo a passo para criá-las é descrito no [artigo sobre autenticação do Developer Portal](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication "artigo sobre autenticação no Developer Portal").
@@ -49,21 +50,21 @@ Guarde as credenciais da Provu em lugar seguro, em que não irá perdê-las. Os
 </div>
 
 ### 2. Cadastro da afiliação
+
 A partir de agora, todos as etapas serão realizadas no módulo de Pagamentos do Admin. 
 
 Com as credenciais da Provu em mãos, prossiga com as instruções a seguir:
-1. 
-2. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-3. Clique na aba __Afiliações de Gateway__.
-4. Ao lado da barra de busca, clique no __botão verde “+”__.
-5. Na seção “Outros”, clique na opção __"Lendico"__.
-6. Preencha o campo __Nome da Afiliação__.
-7. Logo abaixo, clique no botão __"Live/Produção"__ para ativar a afiliação.
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Lendico__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha o campo __Nome da Afiliação__.
+5. Logo abaixo, clique no botão __Live/Produção__ para ativar a afiliação.
 <div class="alert alert-warning">
 Confira se a área ao redor do botão mudou a cor para verde. Isso indica que a afiliação será ativada ao final da configuração. 
 </div>
-11. Do lado direito da tela, preencha os campos __Aplication Key__ e __Aplication Token__ com os respectivos dados fornecidos pela própria Lendico.
-12. Finalize clicando no botão azul __"Salvar"__.
+6. Do lado direito da tela, preencha os campos __Aplication Key__ e __Aplication Token__ com os respectivos dados fornecidos pela própria Lendico.
+7. Clique em __Salvar__.
 
 Desse modo, a afiliação Lendico estará habilitada para processar os pagamentos realizados com o boleto parcelado.  
 
diff --git a/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md b/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md
index c207f742e..baf37d188 100644
--- a/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md
+++ b/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar o subadquirente MercadoPagoV1'
 id: 6wTlR3UTJe6YMAsEuquO26
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-08T13:05:57.452Z
-updatedAt: 2023-03-22T18:05:53.962Z
-publishedAt: 2023-03-22T18:05:53.962Z
+updatedAt: 2024-03-18T18:35:39.248Z
+publishedAt: 
 firstPublishedAt: 2018-03-08T19:45:23.370Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,21 @@ legacySlug: configurar-o-subadquirente-mercadopagov1
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 No gateway da VTEX, você pode configurar o [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) MercadoPago para operar de várias formas. O __MercadoPagoV1__ permite que sua loja receba pagamentos com cartões de débito e crédito, além da [carteira digital](/pt/faq/o-que-e-uma-carteira-digital-e-wallet) Mercado Pago.
 
 <div class="alert alert-warning">
-A afiliação <strong>MercadoPagoV1</strong> não suporta pagamentos por boleto bancário.
+A integração <strong>MercadoPagoV1</strong> não suporta pagamentos por boleto bancário.
 </div>
 
 Para configurar o MercadoPagoV1, siga os passos abaixo:
 
-## Configurar afiliação de gateway MercadoPagoV1
+## Configurar MercadoPagoV1
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __MercadoPagoV1__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __MercadoPagoV1__ na barra de busca e clique sobre o nome do provedor.
 4. O campo __OAuth login__ não é utilizado. Deixe-o como está.
 5. Preencha os campos de cadastro __PublicKey__ e __AccessToken__ com os dados fornecidos pelo MercadoPago.
 6. Deixe os campos __RefreshToken__, __ExpiredTokenIn__ e __Merchant Account Id__ em branco.
diff --git a/docs/tutorials/pt/setting-up-mercadopagov2-sub-acquirer.md b/docs/tutorials/pt/setting-up-mercadopagov2-sub-acquirer.md
index 99b19918e..9bb7c2ca7 100644
--- a/docs/tutorials/pt/setting-up-mercadopagov2-sub-acquirer.md
+++ b/docs/tutorials/pt/setting-up-mercadopagov2-sub-acquirer.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar o subadquirente MercadoPagoV2'
+title: 'Configurar pagamento com MercadoPagoV2'
 id: 1y6k8lCSzJYfPs2yObNFo4
 status: PUBLISHED
 createdAt: 2021-11-30T18:49:42.837Z
-updatedAt: 2023-03-22T18:35:39.911Z
-publishedAt: 2023-03-22T18:35:39.911Z
+updatedAt: 2024-03-11T18:11:39.540Z
+publishedAt: 2024-03-11T18:11:39.540Z
 firstPublishedAt: 2021-11-30T19:32:27.420Z
 contentType: tutorial
 productTeam: Financial
@@ -15,38 +15,42 @@ legacySlug: configurar-o-subadquirente-mercadopagov2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-No gateway da VTEX, você pode configurar o [subadquirente](https://help.vtex.com/pt/tutorial/o-que-e-um-subadquirente) MercadoPagoV2. Por meio dele, sua loja pode receber os pagamentos pelos métodos tradicionais, como: boleto, PIX, cartões de débito e crédito, bem como por métodos exclusivos do Mercado Pago, como: MercadoPagoOff, MercadoPagoPro e MercadoPagoWallet.
-
-<div class="alert alert-warning">
-  Os subadquirentes <strong>MercadoPago</strong> e <strong>MercadoPagoV1</strong> não permitem o recebimento por meio do PIX. Esta é uma característica exclusiva do <strong>MercadoPagoV2</strong>.
-</div>
-
-## Configurar afiliação de gateway MercadoPagoV2
-
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no __botão “+”__.
-3. Clique no conector __MercadoPagoV2__.
-4. Preencha os campos de cadastro __Application Key__ e __Application Token__ com os dados fornecidos pelo Mercado Pago.
-5. Em __Prazo de vencimento do boleto__, escolha a quantidade de dias (contados a partir da geração do boleto) que seu cliente terá para fazer o pagamento.
-6. Informe o nome da sua empresa no campo __Nome da loja__. Lembre-se de que essa é a informação que será descrita no campo Beneficiário do boleto ou na fatura do cartão do cliente.
-7. Em __Parcelamento máximo__, escolha a quantidade máxima de parcelas enviadas ao Mercado Pago.
-8. Em __Categoria principal da loja__, escolha a categoria que mais se encaixa com sua loja.
-9. Na opção __Reembolso automático / manual__, escolha se o cliente será reembolsado de forma automática ou manualmente em caso de cancelamento da ordem.
-10. Em __Modo binário__, selecione “Sim” ou “Não”. Selecionar “Sim”, indica que o processo de aprovação do pagamento ocorra instantaneamente, podendo ser aprovado ou recusado. Selecionar “Não”, indica que o pagamento pode ficar no status “pendente” (caso exija qualquer ação do comprador) ou “em processo” (se for necessária uma revisão manual).
-11. Em __Métodos de pagamento excluídos__, descreva os métodos de pagamentos que não deseja utilizar por meio do MercadoPagoV2 (opcional). Caso opte por deixar em branco este campo, todos os métodos de pagamento disponíveis do MercadoPagoV2 estarão disponíveis em sua loja.
-12. Em __Tipos de pagamento excluídos__,  descreva as bandeiras específicas de crédito e débito (Visa, Mastercard, entre outros) que não deseja utilizar por meio do MercadoPagoV2 (opcional). Caso opte por deixar em branco este campo, todos os tipos de pagamento disponíveis do MercadoPagoV2 estarão disponíveis em sua loja.
-13. Em __Modo de processamento__, escolha como você quer usar o MercadoPagoV2 ( subadquirente ou gateway). Para maiores informações, acesse [O que é um subadquirente?](https://help.vtex.com/pt/tutorial/o-que-e-um-subadquirente--64aX6PeRQQ66O8uCqo0W4q#) e [O que é um gateway de pagamentos?](https://help.vtex.com/pt/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk#). 
-14. Na opção __Integrator ID__, indique o código identificador do programador ou agência que realiza a configuração do Mercado Pago.
-15. Na opção __Moeda__, escolha se a moeda utilizada no pagamento será “Local” (cada país) ou “Dólar Americano” (USD).
-16. Clique em __Salvar__.
-
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, o MercadoPagoV2 estará configurado na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ele estará disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com o MercadoPagoV2).
-
-Para saber como definir condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+Na VTEX, é possível realizar a integração com o provedor de pagamento MercadoPagoV2. Por meio dele, sua loja pode receber os pagamentos pelos métodos tradicionais, tais como: boleto, PIX, cartões de débito e crédito, bem como por métodos exclusivos do Mercado Pago, como: MercadoPagoOff, MercadoPagoPro e MercadoPagoWallet.
+
+Para configurar o MercadoPagoV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __MercadoPagoV2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos de cadastro __Chave de aplicação__ e __Token de aplicação__ com os dados fornecidos pelo Mercado Pago.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor MercadoPagoV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Prazo de vencimento do boleto__, escolha a quantidade de dias (contados a partir da geração do boleto) que seu cliente terá para fazer o pagamento.
+8. Em __Nome da loja__, insira o nome da sua empresa. Esta informação será descrita no campo Beneficiário do boleto ou na fatura do cartão do cliente.
+9. Em __Parcelamento máximo__, escolha a quantidade máxima de parcelas enviadas ao Mercado Pago.
+10. Em __Suporte 3DS 2.0__, selecione "Sim" caso deseje ativar a validação de segurança do 3DS. Para o correto funcionamento deste protocolo, certifique-se de que o __Mercado Pago Payment app__ já esteja instalado em sua loja e que o campo __Modo binário__ (step 14), seja selecionado como __Não__.
+11. Em __Categoria principal da loja__, escolha a categoria do ramo de atuação de sua loja.
+12. Em __Compartilhamento de categoria (loja ou produto) por transação__, selecione se deseja compartilhar com o Mercado Pago em cada transação, os dados da categoria da loja ou do produto.
+13. Na opção __Reembolso automático / manual__, escolha se o cliente será reembolsado de forma automática ou manualmente em caso de cancelamento da ordem.
+14. Em __Modo binário__, indique se a loja deve aceitar pagamentos pendentes. Selecionar "Sim", indica que o processo de aprovação do pagamento ocorre de forma instantânea, podendo ser aprovado ou recusado. Selecionar "Não", define que o pagamento pode permanecer no status "pendente" (caso exija qualquer ação do comprador) ou "em processo" (se for necessária uma revisão manual).
+15. Em __Métodos de pagamento excluídos__, descreva os métodos de pagamentos que não deseja utilizar por meio do MercadoPagoV2 (opcional). Caso opte por deixar em branco este campo, todos os métodos de pagamento disponíveis do MercadoPagoV2 estarão disponíveis em sua loja.
+16. Em __Tipos de pagamento excluídos__,  descreva as bandeiras específicas de crédito e débito (Visa, Mastercard, entre outros) que não deseja utilizar por meio do MercadoPagoV2 (opcional). Caso opte por deixar em branco este campo, todos os tipos de pagamento disponíveis do MercadoPagoV2 estarão disponíveis em sua loja.
+17. Em __Modo de processamento__, escolha como você deseja utilizar MercadoPagoV2: subadquirente (agreggator) ou gateway. Para maiores informações, acesse [O que é um subadquirente?](https://help.vtex.com/pt/tutorial/o-que-e-um-subadquirente--64aX6PeRQQ66O8uCqo0W4q#) e [O que é um gateway de pagamentos?](https://help.vtex.com/pt/tutorial/o-que-e-um-gateway-de-pagamentos--2KH9Wdi7F6swOU4amECSOk#). 
+18. Em __Integrator ID__, indique o código identificador do programador ou agência que realiza a configuração do Mercado Pago.
+19. Em __Moeda__, escolha se a moeda utilizada no pagamento será "Local" (cada país) ou "Dólar Americano" (USD)
+20. O campo __Merchant Account ID__ identifica a conta do merchant. Não é necessário preeenche-lo.
+21. Em __Prazo de captura de pagamento aprovado__, selecione o prazo desejado para captura do pagamento.
+22. Em __Tempo para cancelar compras de um carrinho abandonado__, insira o intervalo de tempo que deve ser aguardado até que os meios de pagamento habilitados não estejam disponíveis para efetuar a compra. 
+23. Clique em __Salvar__.
+
+## Configurar condições de pagamento
+
+Para configurar os métodos de pagamento padrões a serem processados pelo MercadoPagoV2, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
 ## Configurar métodos exclusivos de pagamento
 
-Para saber como configurar métodos exclusivos de pagamento do Mercado Pago, acesse [configurar Mercado Pago Offline e Wallet como métodos de pagamento](https://help.vtex.com/pt/tutorial/configurar-mercado-pago-offline-e-wallet-como-metodos-de-pagamentos).
+Para configurar métodos exclusivos de pagamento do Mercado Pago, acesse [configurar Mercado Pago Offline e Wallet como métodos de pagamento](https://help.vtex.com/pt/tutorial/configurar-mercado-pago-offline-e-wallet-como-metodos-de-pagamentos).
 
-Para maiores informações sobre a integração com o Mercado Pago, acesse o [DevSite Mercado Pago](https://www.mercadopago.com.br/developers/pt/guides/plugins/unofficial/vtex/gateway-affiliations).
+Para maiores informações sobre a integração com o Mercado Pago, acesse o [DevSite Mercado Pago](https://www.mercadopago.com.br/developers/pt/docs/vtex/introduction).
diff --git a/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
index ea7951823..2c4b71f09 100644
--- a/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
@@ -35,18 +35,18 @@ Dito isso, confira o passo a passo:
 
 1. Acesse sua __conta de desenvolvedor__ Apple em `https://developer.apple.com/account/#/overview`;
 2. Selecione a opção __Certificates, IDs & Profiles__;
-![AP1](https://images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
+![AP1](//images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
 3. Clique em __Identifiers__;
- ![AP2](https://images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
+ ![AP2](//images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
 4. Ao lado de Identifiers, clique no __botão azul +__;
-![AP3](https://images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
+![AP3](//images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
 5. Selecione a opção __Merchant IDs__; 
 6. Clique no botão azul __Continue__;
-![AP4](https://images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
+![AP4](//images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
 7. Preencha o campo __Description__;
 8. Preencha o campo __Identifier__; 
 9. Clique no botão __Continue__;
-![AP5](https://images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
+![AP5](//images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
 
 Desse modo, o __Merchant ID__ será criado. 
 
@@ -61,14 +61,14 @@ Em seguida, o lojista pode submetê-lo ao sistema do Apple Pay.
 Para iniciar essa etapa, prossiga com as instruções: 
 
 1. No menu do lado esquerdo, selecione __Certificates__;
-![AP6](https://images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
+![AP6](//images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
 2. Digite seu __Merchant ID__ recém-criado na barra de busca;
 3. Selecione o __Merchant ID__ desejado;
-![AP7](https://images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
+![AP7](//images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
 4. No item __Apple Pay Payment Processing Certificate__, clique no botão __Create Certificate__;
-![AP8](https://images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
+![AP8](//images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
 5. Certifique-se que a pergunta *"Will payments associated with this Merchant ID be processed exclusively in China?"* está marcada com __a opção default (No)__.
-![AP9](https://images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
+![AP9](//images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
 
 Em seguida, você será direcionado para uma tela com instruções sobre a criação do CSR (Certificate Signing Request). 
 
@@ -81,9 +81,9 @@ Com o {{merchantID}}.csr. que você recebeu, finalize:
 1. Clique em __Choose File__; 
 2. Selecione o __arquivo CSR__ desejado;
 3. Clique no botão __Continue__;
-![AP10](https://images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
+![AP10](//images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
 4. Clique em __Download__; 
-![AP11](https://images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
+![AP11](//images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
 5. Clique em __Done__.
 
 ## Registrando domínios no Merchant ID
@@ -100,17 +100,17 @@ Por fim, é preciso importar esse arquivo para o sistema da VTEX por meio do Pos
 Confira as instruções:
 
 1. Digite pelo __Merchant ID__ recém-criado na barra de busca;
-![AP12](https://images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
+![AP12](//images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
 2. Clique no __Merchant ID__ desejado;
 3. No módulo __Merchant Domains__, clique no botão __Add Domain__;
-![AP13](https://images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
+![AP13](//images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
 4. Adicione o domínio no campo __Enter the domain you wish to register__; 
 5. Clique em __Save__.
 
 Agora, para fazer o upload do arquivo `.txt` por meio da API, prossiga com as instruções:
 
 1. Clique em __Download__ e não faça nenhuma alteração no arquivo; 
-![AP14](https://images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
+![AP14](//images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
 2. Abra o arquivo `.txt` e __copie__ todo o conteúdo.
 
 Em seguida, inicie uma sessão no Postman. Você realizará uma chamada via POST para a CDN da VTEX:
@@ -122,7 +122,7 @@ Em seguida, inicie uma sessão no Postman. Você realizará uma chamada via POST
 Ao fazer a chamada *POST*, a resposta deve informar que o certificado estará salvo por 60 minutos. Durante esse período, você deve concluir a validação do domínio. 
 
 Agora, volte ao site da Apple. Na mesma tela em que você fez o download do arquivo `.txt`, clique em __Verify__.
-![AP15](https://images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
+![AP15](//images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
 
 Assim, caso o passo a passo seja feito corretamente, o domínio estará registrado com o status __Verified__. Se quiser, você pode repetir todo o processo para registrar mais domínios usando o botão __Add Domain__ na seção __Merchant Domains__.
 
@@ -138,12 +138,12 @@ Atenção: recomendamos que a senha seja fácil de lembrar, já que ela será in
 
 1. Acesse o módulo __Certificates, Identifiers & Profilers__;
 2. No menu do lado esquerdo, clique em __Identifiers__;
-3. No canto superior direito, filtre por __Merchant IDs__;    ![AP16](https://images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
+3. No canto superior direito, filtre por __Merchant IDs__;    ![AP16](//images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
 4. Selecione o __Merchant Identifier__ desejado;
-5. Clique em __Create Certificate__;    ![AP17](https://images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
+5. Clique em __Create Certificate__;    ![AP17](//images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
 6. Siga as __instruções__ expostas na tela para criar um certificado;
-7. Clique no botão __Continue__;    ![AP18](https://images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
-8. Clique em __Download__.    ![AP19](https://images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
+7. Clique no botão __Continue__;    ![AP18](//images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
+8. Clique em __Download__.    ![AP19](//images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
 
 Agora, quando o arquivo for baixado, clique duas vezes para instalá-lo no Keychain Access.
 
@@ -151,7 +151,7 @@ Em seguida, continue com o passo a passo:
 
 1. Abra o __Keychain Access__; 
 2. Localize o __certificado__ criado no passo quatro acima;
-3. Com o botão direito do mouse, clique no ícone __Chave__; ![AP20](https://images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
+3. Com o botão direito do mouse, clique no ícone __Chave__; ![AP20](//images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
 4. Clique em __Export__;
 5. Nomeie o __certificado__; 
 6. Selecione o formato de exportação __.p12__; 
diff --git a/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md b/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md
index 49baa32b3..5b1ca9837 100644
--- a/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md
+++ b/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Mundipagg Fraud Prevention'
 id: yFbysX42GW2wawu82q6QA
-status: PUBLISHED
+status: CHANGED
 createdAt: 2018-04-18T21:01:40.512Z
-updatedAt: 2023-03-29T00:39:20.112Z
-publishedAt: 2023-03-29T00:39:20.112Z
+updatedAt: 2024-03-18T18:40:56.708Z
+publishedAt: 2024-02-16T12:17:04.418Z
 firstPublishedAt: 2018-04-18T21:23:11.844Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-mundipagg-fraud-prevention
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A Mundipagg oferece uma versão do seu [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com a funcionalidade de antifraude. O Mundipagg Fraud Prevention traz ainda mais segurança para o processamento de compras feitas com boletos, transferências bancárias e as principais bandeiras de cartão de crédito.
 
 Para configurar o Mundipagg Fraud Prevention, siga os passos abaixo:
 
-## Configurar afiliação de gateway Mundipagg Fraud Prevention
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Mundipagg Fraud Prevention__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Mundipagg Fraud Prevention__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha o campo __Merchant Key__ ("Chave da Loja") com a chave cadastrada na Mundipagg. Ela é formada por 36 caracteres, entre letras, números e hífens.
 5. Em __País__, escolha o país da sua loja.
 6. O campo __Cadastro Url Post Notification em Mundipagg__ traz um endereço para que você configure o recebimento de notificações sobre status de pagamento. No link `https://{sellerhost}.vtexpayments.com.br/mundipagg/payment/statusnotification`, substitua `{sellerhost}` pelo account name da sua loja. Então, envie a URL final para a Mundipagg completar o cadastro.
diff --git a/docs/tutorials/pt/setting-up-mundipagg-gateway.md b/docs/tutorials/pt/setting-up-mundipagg-gateway.md
index c3b502722..072ca4288 100644
--- a/docs/tutorials/pt/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/pt/setting-up-mundipagg-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Mundipagg'
 id: 6C9412jePCUMGguq0YWU8M
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T18:01:44.533Z
-updatedAt: 2023-03-29T00:36:17.690Z
-publishedAt: 2023-03-29T00:36:17.690Z
+updatedAt: 2024-03-18T18:39:56.272Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T20:58:03.675Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-mundipagg
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A Mundipagg é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que processa pagamentos feitos com boletos, transferências bancárias e as principais bandeiras de cartão de crédito.
 
 Para configurar a Mundipagg, siga os passos abaixo:
 
-## Configurar afiliação de gateway Mundipagg
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Mundipagg__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Mundipagg__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha o campo __Merchant Key__ ("Chave da Loja") com a chave cadastrada na Mundipagg. Ela é formada por 36 caracteres, entre letras, números e hífens.
 5. Em __País__, escolha o país da sua loja.
 6. O campo __Cadastro Url Post Notification em Mundipagg__ traz um endereço para que você configure o recebimento de notificações sobre status de pagamento. No link `https://{sellerhost}.vtexpayments.com.br/mundipagg/payment/statusnotification`, substitua `{sellerhost}` pelo nome da conta da sua loja. Então, envie a URL final para a Mundipagg completar o cadastro.
diff --git a/docs/tutorials/pt/setting-up-my-account.md b/docs/tutorials/pt/setting-up-my-account.md
index 9740b9e8f..5def7a7e1 100644
--- a/docs/tutorials/pt/setting-up-my-account.md
+++ b/docs/tutorials/pt/setting-up-my-account.md
@@ -3,8 +3,8 @@ title: 'Configurar o My Account'
 id: 23Ayv5D6b86UBnYfoXqZL1
 status: PUBLISHED
 createdAt: 2019-02-19T21:35:31.855Z
-updatedAt: 2021-05-24T18:07:48.662Z
-publishedAt: 2021-05-24T18:07:48.662Z
+updatedAt: 2023-12-21T14:12:18.587Z
+publishedAt: 2023-12-21T14:12:18.587Z
 firstPublishedAt: 2019-02-19T21:37:25.249Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: configurar-o-my-account
 subcategory: 1RWR7qSyaREbD5RfgCjdYG
 ---
 
+<div class = "alert alert-info">
+Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
+</div>
+
 O novo [My Account](https://help.vtex.com/pt/tutorial/como-funciona-o-my-account--2BQ3GiqhqGJTXsWVuio3Xh) já está instalado em todas as contas VTEX em um <strong>ambiente teste</strong>, permitindo ajustes na nova página sem impactos na experiência do usuário. 
 
 Isso quer dizer que o My Account já está disponível para a sua loja realizar as customizações necessárias, antes da migração massiva do aplicativo para produção, através do link abaixo:
diff --git a/docs/tutorials/pt/setting-up-nexxpago-gateway.md b/docs/tutorials/pt/setting-up-nexxpago-gateway.md
index 3cf9e4f2c..a0c7984d5 100644
--- a/docs/tutorials/pt/setting-up-nexxpago-gateway.md
+++ b/docs/tutorials/pt/setting-up-nexxpago-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Nexxpago'
 id: 28Fgmof1WYEeAcM8MkOcWm
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T15:46:11.611Z
-updatedAt: 2023-03-29T01:08:32.601Z
-publishedAt: 2023-03-29T01:08:32.601Z
+updatedAt: 2024-03-18T18:58:03.614Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T16:05:40.588Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-nexxpago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A Nexxpago é uma empresa com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) que oferece diversas soluções de pagamento. A principal delas é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que permite o processamento de pagamentos por meio de boletos bancários e cartões de crédito.
 
 Para configurar a Nexxpago, siga os passos abaixo:
 
-## Configurar afiliação de gateway Nexxpago
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Nexxpago__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Nexxpago__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __External Service Url__("URL externa do serviço), você deve configurar a url externa que vai estar associada a `/pvt/payments?an={AccountName}`.
 5. Preencha os campos de cadastro com os dados fornecidos pela Nexxpago (campos _appKey_ e _appToken_).
 6. Em __Implements Installments Service__ ("Implementação do serviço de parcelamentos"), você deve escolher se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Se escolher a opção _yes_, o sistema vai utilizar a URL configurada no campo __Installments Service Url__ ("URL serviço de parcelamentos").
@@ -31,7 +32,10 @@ Para configurar a Nexxpago, siga os passos abaixo:
 9. Em __SoftDescriptor__ ("Descrição da Transação"), indique o que vai aparecer para identificar a transação realizada na sua loja.
 10. No campo __Captura de segurança antecipada__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude). Você também pode desativar a função.
 11. Em __Usa Antifraude__, informe se deseja usar um antifraude.
-12. Clique em __Salvar__.
+12. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Nexxpago, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, a Nexxpago vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ela vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com a Nexxpago). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
+Depois de seguir os passos indicados, Nexxpago pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-nps-gateway.md b/docs/tutorials/pt/setting-up-nps-gateway.md
index b17d200ec..aad40ad97 100644
--- a/docs/tutorials/pt/setting-up-nps-gateway.md
+++ b/docs/tutorials/pt/setting-up-nps-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Ingenico ePayments (NPS)'
 id: 4DtjieyNQIQeI2O2kymEgq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-18T13:22:00.721Z
-updatedAt: 2023-03-29T01:15:32.462Z
-publishedAt: 2023-03-29T01:15:32.462Z
+updatedAt: 2024-03-18T19:00:20.612Z
+publishedAt: 
 firstPublishedAt: 2018-04-18T15:09:45.694Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-gateway-nps
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 O Ingenico ePayments (NPS) é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com forte atuação na América Latina e que permite que sua loja aceite diversas condições de pagamento.
 
 Para configurar o Ingenico ePayments (NPS), siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-pagar-me-gateway.md b/docs/tutorials/pt/setting-up-pagar-me-gateway.md
index b7b63bd26..c664f3fba 100644
--- a/docs/tutorials/pt/setting-up-pagar-me-gateway.md
+++ b/docs/tutorials/pt/setting-up-pagar-me-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway Pagar.me'
 id: egFyDkXjfa80wkSkUWsmc
 status: PUBLISHED
 createdAt: 2018-04-10T17:54:18.410Z
-updatedAt: 2023-03-26T21:05:35.943Z
-publishedAt: 2023-03-26T21:05:35.943Z
+updatedAt: 2024-01-23T19:17:28.562Z
+publishedAt: 2024-01-23T19:17:28.562Z
 firstPublishedAt: 2018-04-10T18:10:52.337Z
 contentType: tutorial
 productTeam: Financial
@@ -19,10 +19,9 @@ O Pagar.me é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que of
 
 Para configurar o Pagar.me, siga os passos abaixo:
 
-## Configurar afiliação de gateway Pagar.me
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PagarMe__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Pagar.me__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __External Service Url__, você deve configurar a url externa que vai estar associada à `/pvt/payments?an={AccountName}`.
 5. Preencha os campos de cadastro com os dados fornecidos pelo Pagar.me (campos __appKey__ e __appToken__).
 6. Em __Implements Installments Service__, você deve escolher se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Se escolher a opção _yes_, o sistema vai utilizar a url configurada no campo __Installments Service Url__.
diff --git a/docs/tutorials/pt/setting-up-pagarmev2-gateway.md b/docs/tutorials/pt/setting-up-pagarmev2-gateway.md
index 50a487551..65cbd8abf 100644
--- a/docs/tutorials/pt/setting-up-pagarmev2-gateway.md
+++ b/docs/tutorials/pt/setting-up-pagarmev2-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway PagarMeV2'
 id: 5TugxXNMOs0Ocyg4uqussM
 status: PUBLISHED
 createdAt: 2018-04-10T18:50:48.932Z
-updatedAt: 2023-03-26T21:04:07.182Z
-publishedAt: 2023-03-26T21:04:07.182Z
+updatedAt: 2024-01-23T19:19:58.174Z
+publishedAt: 2024-01-23T19:19:58.174Z
 firstPublishedAt: 2018-04-11T21:51:25.333Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,20 @@ legacySlug: configurar-gateway-pagarmev2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-O PagarMeV2 é a versão mais recente do conector do [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) Pagar.me. Para configurá-la, siga os passos abaixo:
+Na VTEX, é possível processar pagamentos com o provedor PagarMe por meio das integrações V2 e V3.
 
-## Configurar afiliação de gateway PagarMeV2
+<div class="alert alert-warning">
+Caso deseje configurar a versão V3 da Pagarme em sua loja, acesse <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-pagarmev3--5PMavdamrVijwIrHas9ndE">Configurar pagamento com PagarMeV3</a>.
+</div>
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Em __Afiliações de gateway__, clique no botão verde “__+__”.
-3. Busque e clique em __PagarMeV2__.
+Para configurar a PagarMeV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagarMeV2__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos indicados com as seguintes informações:<br><br>
 <ul>
-<li><b>Application Key</b> e <b>Application Token</b>: insira as informações que foram fornecidas pela Pagar.me.</li>
+<li><b>Chave de aplicação</b> e <b>Token de aplicação</b>: insira as informações que foram fornecidas pela Pagar.me.</li>
 <li><b>Captura automática de pagamento</b>: selecione uma das seguintes opções:<br><br>
     <ul>
     	<li><b>Use O Comportamento Recomendado Pelo Processador de Pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
diff --git a/docs/tutorials/pt/setting-up-pagbrasil-gateway.md b/docs/tutorials/pt/setting-up-pagbrasil-gateway.md
index 16fccae6c..3c29c82ac 100644
--- a/docs/tutorials/pt/setting-up-pagbrasil-gateway.md
+++ b/docs/tutorials/pt/setting-up-pagbrasil-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway PagBrasil'
 id: 2vzj6MkFRuKm4KQAOOmWaa
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-10T12:40:34.957Z
-updatedAt: 2023-03-29T01:00:48.970Z
-publishedAt: 2023-03-29T01:00:48.970Z
+updatedAt: 2024-03-18T19:02:31.069Z
+publishedAt: 
 firstPublishedAt: 2018-04-10T12:50:24.707Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-pagbrasil
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A PagBrasil é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) especializado em meios de pagamento brasileiros, principalmente cartões de crédito e débito, transferências online e boletos bancários.
 
 Para configurar a PagBrasil, siga os passos abaixo:
 
-## Configurar afiliação de gateway PagBrasil
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PagBrasil__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagBrasil__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __External Service Url__ ("URL externa do serviço), você deve configurar a URL externa que vai estar associada a `/pvt/payments?an={AccountName}`.
 5. Preencha os campos de cadastro com os dados fornecidos pela PagBrasil (campos _appKey_ e _appToken_).
 6. Em __Implements Installments Service__ ("Implementação do serviço de parcelamentos"), você deve escolher se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Se escolher a opção _yes_, o sistema vai utilizar a URL configurada no campo __Installments Service Url__ ("URL serviço de parcelamentos").
diff --git a/docs/tutorials/pt/setting-up-paghiper-gateway.md b/docs/tutorials/pt/setting-up-paghiper-gateway.md
index 5f5ce2d6b..88fd6f2de 100644
--- a/docs/tutorials/pt/setting-up-paghiper-gateway.md
+++ b/docs/tutorials/pt/setting-up-paghiper-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway PagHiper'
 id: I3KXAIIJG0oyyg4A4MykE
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-09T22:06:11.621Z
-updatedAt: 2023-03-29T01:13:11.291Z
-publishedAt: 2023-03-29T01:13:11.291Z
+updatedAt: 2024-03-18T19:04:40.079Z
+publishedAt: 
 firstPublishedAt: 2018-04-09T22:43:35.309Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-paghiper
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A PagHiper é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) especializado no processamento de compras realizadas por boletos bancários.
 
 Para configurar a PagHiper, siga os passos abaixo:
 
-## Configurar afiliação de gateway PagHiper
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PagHiper__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagHiper__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __External Service Url__, você deve configurar a url externa que vai estar associada à `/pvt/payments?an={AccountName}`.
 5. Preencha os campos de cadastro com os dados fornecidos pela PagHiper (campos _appKey_ e _appToken_).
 6. Em __Implements Installments Service__, você deve escolher se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Se escolher a opção _yes_, o sistema vai utilizar a URL configurada no campo __Installments Service Url__.
diff --git a/docs/tutorials/pt/setting-up-pagseguro-v3.md b/docs/tutorials/pt/setting-up-pagseguro-v3.md
index 25b65878e..57ea58f33 100644
--- a/docs/tutorials/pt/setting-up-pagseguro-v3.md
+++ b/docs/tutorials/pt/setting-up-pagseguro-v3.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar o PagSeguro V3'
+title: 'Configurar pagamento com PagBankV3'
 id: 5Noi1mUbBQ6CyqdeDQtWfw
 status: PUBLISHED
 createdAt: 2021-12-02T12:14:58.698Z
-updatedAt: 2023-03-23T15:40:31.170Z
-publishedAt: 2023-03-23T15:40:31.170Z
+updatedAt: 2024-03-14T18:59:12.645Z
+publishedAt: 2024-03-14T18:59:12.645Z
 firstPublishedAt: 2021-12-02T19:18:21.251Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,30 @@ legacySlug: configurar-o-pagseguro-v3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Se você possui uma conta PagSeguro, pode configurar o PagseguroV3 no gateway da VTEX para receber pagamentos por: boleto, PIX, cartões de débito e crédito.
+Na VTEX, é possível realizar a integração com o provedor de pagamento PagBankV3. Por meio deste provedor, sua loja pode realizar vendas por meio de boleto, PIX, cartões de débito e crédito.
 
-## Configurar afiliação de gateway PagseguroV3
+Para configurar o PagBankV3, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no __botão “+”__.
-3. Clique no conector __PagSeguroV3__.
-4. Em __Click to authorize VTEX to make payments__, clique em __Autorizar__. Neste momento, você será redirecionado para a página do PagSeguro, onde deverá acessar a sua conta, e autorizar a conexão da VTEX na sua conta do PagSeguro.
-5. Após autorizar, você retornará automaticamente para o Admin da VTEX, e os campos __Application Key__, __Application Token__, __Application Id__ já estarão preenchidos.
-6. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagBankV3__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, clique em __Autorizar via OAuth__. Neste momento, você será redirecionado para a página do PagBank, onde deverá acessar a sua conta, e autorizar a conexão da VTEX na sua conta do PagBank. Após o processo de autorização, você retornará automaticamente para o Admin VTEX.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagBank na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, no campo __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+7. Caso deseje utilizar o [split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) em sua loja, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
+8. Em __Campos do provedor__, no campo __Prazo para captura do pagamento__ selecione o período desejado para realizar a captura do pagamento.  
+9. Clique em __Salvar__.
 
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, o PagSeguroV3 estará configurado na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ele estará disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com o PagSeguroV3).
+Para configurar os métodos de pagamento a serem processados pela PagBankV3, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
 
-Para saber como definir condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PagBankV3 pode demorar até 10 minutos para aparecer no checkout da sua loja como opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payment-with-paypal.md b/docs/tutorials/pt/setting-up-payment-with-paypal.md
index 1c34d2d83..df02ddc04 100644
--- a/docs/tutorials/pt/setting-up-payment-with-paypal.md
+++ b/docs/tutorials/pt/setting-up-payment-with-paypal.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamento com PayPal'
 id: 4p3sD9u1moq2Aya2oc684w
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-21T17:15:53.516Z
-updatedAt: 2023-03-21T20:46:52.481Z
-publishedAt: 2023-03-21T20:46:52.481Z
+updatedAt: 2024-03-18T20:29:36.504Z
+publishedAt: 
 firstPublishedAt: 2018-02-21T17:54:19.079Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-paypal
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 No gateway da VTEX, é possível configurar o subadquirente PayPal para receber seus pagamentos. Nesta modalidade, o seu cliente escolhe o __meio de pagamento__ PayPal e realiza sua autenticação no ambiente do PayPal.
 
 Para fazer as configurações, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-paymentez-gateway.md b/docs/tutorials/pt/setting-up-paymentez-gateway.md
index 9ba88cf65..d759ee1ca 100644
--- a/docs/tutorials/pt/setting-up-paymentez-gateway.md
+++ b/docs/tutorials/pt/setting-up-paymentez-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Paymentez'
 id: 7zmH2WCtVuAoUUQWyU2qgO
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-28T17:47:41.909Z
-updatedAt: 2023-03-26T22:08:53.622Z
-publishedAt: 2023-03-26T22:08:53.622Z
+updatedAt: 2024-03-18T19:16:05.956Z
+publishedAt: 
 firstPublishedAt: 2018-03-28T18:18:57.206Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-paymentez
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A Paymentez é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que possui certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) nível 2 e tem sua atuação concentrada na América Latina.
 
-Para configurar a Paymentez, siga os passos abaixo:
+Para configurar Paymentez, siga os passos abaixo:
 
-## Configurar afiliação de gateway Paymentez
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Paymentez__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Paymentez__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __External Service Url__, você deve configurar a url externa que vai estar associada à `/pvt/payments?an={AccountName}`.
 5. Preencha os campos de cadastro com os dados fornecidos pela Paymentez (campos _appKey_ e _appToken_).
 6. Em __Implements Installments Service__, você deve escolher se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Se escolher a opção _yes_, o sistema vai utilizar a url configurada no campo __Installments Service Url__.
@@ -31,7 +32,10 @@ Para configurar a Paymentez, siga os passos abaixo:
 9. Em __SoftDescriptor__, indique o que vai aparecer para identificar a transação realizada na sua loja.
 10. No campo __Captura de segurança antecipada__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude). Você também pode desativar a função.
 11. Em __Tem um antifraude contratado com essa afiliação?__, informe se deseja usar um antifraude.
-12. Clique em __Salvar__.
+12. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Paymentez, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-## Configurar condição de pagamento
-Depois de seguir os passos indicados, a Paymentez vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ela vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com a Paymentez). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
+Depois de seguir os passos indicados, Paymentez pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-55pay.md b/docs/tutorials/pt/setting-up-payments-with-55pay.md
index 1e970a33e..6494647b9 100644
--- a/docs/tutorials/pt/setting-up-payments-with-55pay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-55pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com 55PAY'
 id: 4ktYG4reu5T6taEj2pKjvZ
 status: PUBLISHED
 createdAt: 2022-05-05T13:22:59.869Z
-updatedAt: 2023-03-26T21:43:11.110Z
-publishedAt: 2023-03-26T21:43:11.110Z
+updatedAt: 2024-01-23T18:31:36.516Z
+publishedAt: 2024-01-23T18:31:36.516Z
 firstPublishedAt: 2022-05-05T13:44:32.122Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-55pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway 55PAY. Com este conector, sua loja pode utilizar os serviços de [PABX Virtual](https://suporte.55pbx.com/hc/pt-br/articles/218648978-O-que-%C3%A9-PABX-Virtual-) da empresa 55PBX.
+Na VTEX, é possível realizar a integração com o gateway 55PAY. Por meio desta integração, sua loja pode utilizar os serviços de [PABX Virtual](https://suporte.55pbx.com/hc/pt-br/articles/218648978-O-que-%C3%A9-PABX-Virtual-) da empresa 55PBX.
 
-Para configurar a afiliação 55PAY, siga os passos abaixo:
+Para configurar 55PAY, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __55Pay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __55Pay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta 55PBX.
 5. Clique em `Salvar`.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-99pay.md b/docs/tutorials/pt/setting-up-payments-with-99pay.md
index c376b8b8e..03f9f76f8 100644
--- a/docs/tutorials/pt/setting-up-payments-with-99pay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-99pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com 99Pay'
 id: QIStxPsGb6LoIwFBfcTfb
 status: PUBLISHED
 createdAt: 2023-04-06T19:37:06.116Z
-updatedAt: 2023-04-06T19:41:32.060Z
-publishedAt: 2023-04-06T19:41:32.060Z
+updatedAt: 2024-01-23T18:31:10.050Z
+publishedAt: 2024-01-23T18:31:10.050Z
 firstPublishedAt: 2023-04-06T19:41:32.060Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-99pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento 99Pay. Com este conector, sua loja pode realizar vendas por meio do 99Pay.
+Na VTEX, é possível realizar a integração com o provedor de pagamento 99Pay. Por meio deste provedor, sua loja pode realizar vendas por meio do 99Pay.
 
-Para configurar a afiliação 99Pay, siga os passos abaixo:
+Para configurar 99Pay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __99Pay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __99Pay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta 99Pay.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-aarin.md b/docs/tutorials/pt/setting-up-payments-with-aarin.md
index 624f8472b..7911df2b1 100644
--- a/docs/tutorials/pt/setting-up-payments-with-aarin.md
+++ b/docs/tutorials/pt/setting-up-payments-with-aarin.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Aarin'
 id: 2kVQVFqutbZYK3I6XBVgLp
 status: PUBLISHED
 createdAt: 2022-06-22T12:45:29.082Z
-updatedAt: 2023-03-26T21:42:40.807Z
-publishedAt: 2023-03-26T21:42:40.807Z
+updatedAt: 2024-01-23T18:32:06.337Z
+publishedAt: 2024-01-23T18:32:06.337Z
 firstPublishedAt: 2022-06-22T13:00:38.494Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-aarin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Aarin. Com este conector, sua loja pode realizar vendas por meio do PIX.
+Na VTEX, é possível realizar a integração com o gateway Aarin. Por meio desta integração, sua loja pode realizar vendas por meio do PIX.
 
-Para configurar a afiliação Aarin, siga os passos abaixo:
+Para configurar Aarin, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Aarin__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Aarin__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Aarin.
 5. Em __Chave Pix__, preencha as informações da sua chave pix.
 6. Em __Aarin Secret__, preencha a informação fornecida pela Aarin.
diff --git a/docs/tutorials/pt/setting-up-payments-with-addi.md b/docs/tutorials/pt/setting-up-payments-with-addi.md
index 980f9927c..8f7c2fea4 100644
--- a/docs/tutorials/pt/setting-up-payments-with-addi.md
+++ b/docs/tutorials/pt/setting-up-payments-with-addi.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Addi'
 id: 7FhMbT3hN2i5je74lqx6QI
 status: PUBLISHED
 createdAt: 2022-02-14T12:22:11.957Z
-updatedAt: 2023-03-27T12:46:46.989Z
-publishedAt: 2023-03-27T12:46:46.989Z
+updatedAt: 2024-01-23T18:29:23.380Z
+publishedAt: 2024-01-23T18:29:23.380Z
 firstPublishedAt: 2022-02-14T15:04:37.219Z
 contentType: tutorial
 productTeam: Financial
@@ -15,12 +15,13 @@ legacySlug: configurar-pagamento-com-a-addi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Addi. Com este conector, sua loja pode realizar vendas a prazo sem cartão de crédito.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Addi. Por meio deste provedor, sua loja pode realizar vendas a prazo sem cartão de crédito.
 
-Para configurar a afiliação Addi, siga os passos abaixo:
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Addi__.
+Para configurar Addi, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Addi__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Addi.
 5. Em __Country of Operation__, selecione o país onde o conector irá operar.
 6. Clique em __Salvar__.
diff --git a/docs/tutorials/pt/setting-up-payments-with-alignet.md b/docs/tutorials/pt/setting-up-payments-with-alignet.md
index ed7021b23..b4d24e85b 100644
--- a/docs/tutorials/pt/setting-up-payments-with-alignet.md
+++ b/docs/tutorials/pt/setting-up-payments-with-alignet.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamentos com Alignet'
 id: 4qfl6jgDyMGA0IuM0siEii
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-28T20:48:01.728Z
-updatedAt: 2023-03-29T01:04:08.516Z
-publishedAt: 2023-03-29T01:04:08.516Z
+updatedAt: 2024-03-18T17:48:35.669Z
+publishedAt: 
 firstPublishedAt: 2018-03-28T23:00:56.209Z
 contentType: tutorial
 productTeam: Financial
@@ -15,29 +15,32 @@ legacySlug: configurar-pagamentos-com-alignet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Na plataforma VTEX, é possível configurar o [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) Alignet para receber pagamentos na sua loja. Nessa modalidade, o cliente escolhe o __meio de pagamento__ Alignet e é redirecionado para autenticação no ambiente do subadquirente.
 
-Para fazer as configurações, siga os passos abaixo:
+Para configurar Alignet, siga os passos abaixo:
 
-## Configurar afiliação de gateway Alignet
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Alignet__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Alignet__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __Acquirer__, escolha o adquirente que será usado na integração.
 5. Preencha os campos de cadastro com os dados fornecidos pela Alignet (campos _Código Adquirente_, _CodigoComercio_, _CodigoMall_, _CodigoTerminal_ _ChavePrivadaAssinatura_, _ChavePrivadaCriptografia_, _ChavePublicaAssinaturaAlignet_ e _ChavePublicaCriptografiaAlignet_).
 6. No campo __CodigoMoeda__, preencha com o código [ISO 4217](https://pt.wikipedia.org/wiki/ISO_4217) da moeda que será usada nos pagamentos.
 7. Em __Linguagem__, escolha entre espanhol e inglês.
 8.  No campo __Vector__, preencha a sequência de até 16 caracteres (somente letras e números) gerada pela sua loja.
-9.  Clique em __Salvar__.
+9.  Clique em `Salvar`.
 
 ## Configurar condição de pagamento Alignet
+
 1. Já dentro das __Configurações__ do módulo Pagamentos, clique na aba __Condições de pagamento__.
 2. Clique no botão __+__.
 3. Clique no meio de pagamento __Alignet__.
 4. Clique no botão __Status__, para ativar esta condição de pagamento.
 5. Caso sua loja tenha um antifraude configurado, você pode ativá-lo marcando a caixa __Usar Antifraude__.
 6. Se quiser, você também pode adicionar uma [condição especial de pagamento](/pt/tutorial/condicoes-especiais).
-8. Clique em __Salvar__.
+8. Clique em `Salvar`.
 
 Depois de seguir os passos indicados, a Alignet vai aparecer no checkout da sua loja como uma opção de pagamento. Depois de clicar em __Finalizar Compra__, seu cliente será redirecionado para autenticação no ambiente da Alignet.
-Outra opção para você habilitar essa condição de pagamento é usar o conector [Pay-me](/pt/tutorial/configurar-gateway-pay-me).
+
+Você também pode ativar esta condição de pagamento usando o [PayMee](https://help.vtex.com/pt/tutorial/configurar-o-gateway-paymee--3fsilRdrBS6GOAy622soWy).
diff --git a/docs/tutorials/pt/setting-up-payments-with-alignetv2.md b/docs/tutorials/pt/setting-up-payments-with-alignetv2.md
new file mode 100644
index 000000000..5d6540288
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-alignetv2.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pagamento com AlignetV2'
+id: 1rZU7cexTYdzB4SHWjr3eJ
+status: PUBLISHED
+createdAt: 2024-03-07T16:37:07.030Z
+updatedAt: 2024-03-07T16:56:11.973Z
+publishedAt: 2024-03-07T16:56:11.973Z
+firstPublishedAt: 2024-03-07T16:56:11.973Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-alignetv2
+locale: pt
+legacySlug: configurar-pagamento-com-alignetv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento AlignetV2. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito.
+
+Para configurar o AlignetV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __AlignetV2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta AlignetV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor AlignetV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre o nome da bandeira do cartão de crédito desejado.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor AlignetV2 pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-ame-digital.md b/docs/tutorials/pt/setting-up-payments-with-ame-digital.md
index e313bbedb..985f27d41 100644
--- a/docs/tutorials/pt/setting-up-payments-with-ame-digital.md
+++ b/docs/tutorials/pt/setting-up-payments-with-ame-digital.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com a Ame Digital'
 id: 4oEhDjLM4uk95X8omwLEG2
 status: PUBLISHED
 createdAt: 2022-02-14T17:02:38.944Z
-updatedAt: 2023-03-26T21:42:08.346Z
-publishedAt: 2023-03-26T21:42:08.346Z
+updatedAt: 2024-01-23T18:28:00.633Z
+publishedAt: 2024-01-23T18:28:00.633Z
 firstPublishedAt: 2022-02-14T17:35:18.865Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-pagamento-com-a-ame-digital
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Ame Digital. Com este conector, sua loja pode realizar vendas à vista, prazo, com QR Code ou link de pagamento. Além disto, os seus clientes podem ter acesso a cashback durante as compras.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Ame Digital. Por meio deste provedor, sua loja pode realizar vendas à vista, prazo, com QR Code ou link de pagamento. Além disto, os seus clientes podem ter acesso a cashback durante as compras.
 
-Para configurar a afiliação Ame Digital, siga os passos abaixo:
-1. 
-2. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-3. Na aba __Afiliações de Gateways__, clique no botão __+__.
-4. Clique no conector __AmeDigital__.
-5. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Ame Digital.
-6. Clique em __Salvar__.
+Para configurar Ame Digital, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __AmeDigital__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Ame Digital.
+5. Clique em __Salvar__.
 
 ## Configurar condição de pagamento
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-apple-pay.md b/docs/tutorials/pt/setting-up-payments-with-apple-pay.md
index d19af5cfb..6125e57cf 100644
--- a/docs/tutorials/pt/setting-up-payments-with-apple-pay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-apple-pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamentos com Apple Pay'
 id: 5L3NWMgvdKswWQa6eIc008
 status: PUBLISHED
 createdAt: 2018-04-12T20:38:42.521Z
-updatedAt: 2023-03-26T21:54:30.284Z
-publishedAt: 2023-03-26T21:54:30.284Z
+updatedAt: 2024-06-25T21:20:56.252Z
+publishedAt: 2024-06-25T21:20:56.252Z
 firstPublishedAt: 2018-05-23T19:26:11.000Z
 contentType: tutorial
 productTeam: Financial
@@ -26,38 +26,32 @@ Seus clientes podem fazer compras usando o Apple Pay, a [carteira digital](/pt/f
 
 Com os requisitos cumpridos, basta seguir os passos abaixo para oferecer essa condição de pagamento na sua loja:
 
-## Configurar afiliação de gateway
-Oferecer condições de pagamento aos clientes da sua loja depende de afiliações de gateway capazes de processá-las. Na plataforma VTEX, as afiliações compatíveis atualmente com o __Apple Pay__ são: __ERedeREST__ (integração da adquirente Rede), __Adyen__ e __Stripe__.
+## Configurar provedor de pagamento
 
-Nestes artigos, você tem o passo a passo para configurar o [ERedeREST](/pt/tutorial/configurar-adquirente-rede-com-o-erederest), [Adyen](/pt/tutorial/como-configurar-o-gateway-adyen-na-vtex) e [Stripe](https://help.vtex.com/pt/tutorial/configuring-stripe-gateway-affiliation--fwF2wk2FQKrODrWWkvSLO). 
+Primeiramente é necessário configurar no Admin de sua loja um provedor que processe transações com o Apple Pay, tais como, [Adyen](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3) e [Stripe](https://help.vtex.com/pt/tutorial/configurar-a-afiliacao-de-gateway-stripe--fwF2wk2FQKrODrWWkvSLO).
 
-Mas lembre-se: é fundamental [registrar o Merchant ID no Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay) antes de fazer a configuração da afiliação de gateway.
+Para conferir todas as opções de provedores disponíveis para este meio de pagamento, acesse a lista conforme descrito no Passo 5 da seção [Configurar pagamento com Apple Pay](#configurar-pagamento-com-apple-pay).
 
-## Baixar e instalar aplicativo da VTEX App Store 
-1. No menu lateral do admin, clique em __Apps__.
-2. Acesse o link __VTEX App Store__ ou use a URL `https://apps.vtex.com/?an={{AccountName}}` direto no navegador, trocando `{{AccountName}}` pelo store name em que deseja oferecer o Apple Pay.
-3. Procure pelo app __Apple Pay__ e clique em __Get__.
-4. Você será direcionado para uma tela de revisão de pedido. Confira os dados e clique no botão __Confirm order and begin installation__.
-5. Com tudo certo, você vai para a tela de instalação. Lá, você pode rever as permissões do aplicativo e iniciar o download (clicando em __Instalar__).
-6. O app vai ser instalado no seu workspace, mas precisará que você preencha o __Merchant ID__ (no campo __Merchant Identifier__) para ser aplicado na sua loja.
-7. Clique em __Salvar__. 
+<div class="alert alert-warning">
+  Antes de iniciar a configuração do provedor é necessário <a href="registrar o Merchant ID no Apple Pay">registrar o Merchant ID no Apple Pay</a>.
+</div>
+
+## Configurar pagamento com Apple Pay
 
-## Configurar condição de pagamento Apple Pay
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Clique na aba __Condições de pagamento__ e, em seguida, no botão __+__.
 3. Selecione o meio de pagamento __Apple Pay__.
-4. Clique no botão __Status__ para ativar essa condição de pagamento.
-5. No campo __Processar com a afiliação__, selecione a opção que vai ser usada para processar os pagamentos.
-6. Se houver um antifraude configurado na sua loja, você pode ativá-lo para essa condição de pagamento marcando a caixa __Usar Antifraude__.
+4. Clique no botão `Status` para ativar essa condição de pagamento.
+5. No campo __Processar com o provedor__, selecione o provedor que será utilizado para processar os pagamentos.
+6. Se houver um antifraude configurado na sua loja, você pode ativá-lo para essa condição de pagamento marcando a caixa __Usar solução antifraude___.
 7. Escolha se deseja que os pagamentos sejam feitos à vista ou parcelados.
-8. Se quiser, você também pode optar por uma [condição especial de pagamento](/pt/tutorial/condicoes-especiais).
-9. Clique em __Salvar__.
+8. Se quiser, você também pode optar por uma [condição especial de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+9. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o __Apple Pay__ vai aparecer no checkout da sua loja como uma opção de pagamento para seus clientes utilizarem.
+Depois de seguir os passos indicados, Apple Pay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
 
 ### Artigos relacionados
-- [Configurar adquirente Rede com o ERedeREST](/pt/tutorial/configurar-adquirente-rede-com-o-erederest)
-- [Configurar o gateway Adyen na VTEX](/pt/tutorial/como-configurar-o-gateway-adyen-na-vtex)
+
 - [Configurando Merchant ID no Apple Pay](https://developers.vtex.com/vtex-rest-api/docs/setting-up-merchant-id-in-apple-pay)
-- [Configurar condições especiais de pagamento](/pt/tutorial/condicoes-especiais)
-- [O que é um carteira digital (e-wallet)?](/pt/faq/o-que-e-uma-carteira-digital-e-wallet)
+- [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456)
+- [O que é um carteira digital (ewallet)?](https://help.vtex.com/pt/tutorial/o-que-e-uma-carteira-digital-e-wallet--4v5wcOe4A0SiaimWM2cU60)
diff --git a/docs/tutorials/pt/setting-up-payments-with-appmax.md b/docs/tutorials/pt/setting-up-payments-with-appmax.md
new file mode 100644
index 000000000..a9e310498
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-appmax.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pagamento com Appmax'
+id: 6IIo8dyXKtdmXykBOhYmi0
+status: PUBLISHED
+createdAt: 2023-12-18T14:21:48.704Z
+updatedAt: 2024-01-23T18:26:05.083Z
+publishedAt: 2024-01-23T18:26:05.083Z
+firstPublishedAt: 2023-12-18T14:32:23.030Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-appmax
+locale: pt
+legacySlug: configurar-pagamento-com-appmax
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Appmax. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, boleto e Pix.
+
+Para configurar Appmax, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Appmax__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Click to authorize VTEX to make payments__, clique em __Autorizar__. Neste momento, você será redirecionado para a página da Appmax, onde deverá acessar a sua conta, e autorizar a conexão da VTEX na sua conta do Appmax.
+5. Após autorizar, você retornará automaticamente para o Admin VTEX, e os campos __Application Key__, __Application Token__, __Application Id__ já estarão preenchidos.
+6. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Appmax, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector Appmax pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-argonpay.md b/docs/tutorials/pt/setting-up-payments-with-argonpay.md
new file mode 100644
index 000000000..70686c398
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-argonpay.md
@@ -0,0 +1,50 @@
+---
+title: 'Configurar pagamento com argonPAY'
+id: 6Pktml6MJpdc7dNvJ4zwzI
+status: PUBLISHED
+createdAt: 2023-12-18T14:51:00.261Z
+updatedAt: 2023-12-18T15:02:08.524Z
+publishedAt: 2023-12-18T15:02:08.524Z
+firstPublishedAt: 2023-12-18T15:02:08.524Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-argonpay
+locale: pt
+legacySlug: configurar-pagamento-com-argonpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento argonPAY. Por meio deste conector, sua loja pode realizar vendas por meio do argonPAY.
+
+Para configurar o provedor argonPAY, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja__ > __Pagamentos__ > __Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Afiliações de Gateways__, clique no botão `+`.
+3. Clique em __ArgonPay__.
+4. Nos campos __Application Key__ e __Application Token__, insira as informações que foram fornecidas pela argonPAY.
+5. No campo __Captura automática de pagamento__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Use o comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Imediatamente: captura automática ao autorizar o pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Imediatamente: captura automática ao passar a análise de risco de fraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Imediatamente: Captura Automática Ao Autorizar O Pagamento").</li>
+   		<li><b>Agendada: defina quando a captura automática será realizada</b>: ao selecionar esta opção, o campo <b>Prazo agendado em horas para a captura automática</b> estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.</li>        
+   		<li><b>Desativado: não capturado automaticamente</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+
+6. Em __Ativar divisão e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+7. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja__ > __Pagamentos__ > __Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Selecione a condição de pagamento __ArgonPay__.
+4. Preencha o campo __Nome da regra__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o conector argonPAY pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-astropay.md b/docs/tutorials/pt/setting-up-payments-with-astropay.md
index ae898d390..59935fbae 100644
--- a/docs/tutorials/pt/setting-up-payments-with-astropay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-astropay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Astropay'
 id: 1A5hrnp3wLTlkUkYLlielB
 status: PUBLISHED
 createdAt: 2022-08-15T18:20:38.640Z
-updatedAt: 2023-03-26T21:21:01.948Z
-publishedAt: 2023-03-26T21:21:01.948Z
+updatedAt: 2024-01-25T19:07:17.927Z
+publishedAt: 2024-01-25T19:07:17.927Z
 firstPublishedAt: 2022-08-15T18:39:51.774Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-astropay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Astropay. Com este conector, sua loja pode realizar vendas por meio da Astropay.
+Na VTEX, é possível realizar a integração com o gateway Astropay. Com esta integração, sua loja pode realizar vendas por meio da Astropay.
 
-Para configurar a afiliação Astropay, siga os passos abaixo:
+Para configurar Astropay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __AstroPayOneTouch__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __AstroPayOneTouch__ na barra de busca e clique sobre o nome do provedor.
 4. Clique no botão __Instalar app__ e siga as instruções de instalação.
 5. Preencha os campos __Application Key__, __Application Token__, __App Key - Astropay__ e __Api Secret - Astropay__ com as informações da sua conta Astropay.
 6. Clique em `Salvar`.
@@ -34,5 +34,5 @@ Para configurar a afiliação Astropay, siga os passos abaixo:
 4. Ative a condição no campo __Status__.
 5. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Astropay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Astropay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-bamboo.md b/docs/tutorials/pt/setting-up-payments-with-bamboo.md
index d99c26db0..68233a6a0 100644
--- a/docs/tutorials/pt/setting-up-payments-with-bamboo.md
+++ b/docs/tutorials/pt/setting-up-payments-with-bamboo.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Bamboo'
 id: 33TDZBp1wmgzJdiZtvu1xY
 status: PUBLISHED
 createdAt: 2022-08-12T20:06:37.117Z
-updatedAt: 2022-08-12T20:13:31.863Z
-publishedAt: 2022-08-12T20:13:31.863Z
+updatedAt: 2024-01-25T19:18:30.701Z
+publishedAt: 2024-01-25T19:18:30.701Z
 firstPublishedAt: 2022-08-12T20:13:31.863Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: configurar-pagamento-com-bamboo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Bamboo. Por meio deste conector, sua loja pode realizar vendas por meio do cartões de crédito, débito, private labels, cobranded e boletos.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Bamboo. Por meio deste provedor, sua loja pode realizar vendas por meio do cartões de crédito, débito, private labels, cobranded e boletos.
 
-Para configurar a afiliação Bamboo, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para configurar a Bamboo, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#).
 
-Depois de seguir os passos indicados, o conector Bamboo pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Bamboo pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-bancolombia-bnpl.md b/docs/tutorials/pt/setting-up-payments-with-bancolombia-bnpl.md
index 790086198..2cd542c38 100644
--- a/docs/tutorials/pt/setting-up-payments-with-bancolombia-bnpl.md
+++ b/docs/tutorials/pt/setting-up-payments-with-bancolombia-bnpl.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Bancolombia BNPL'
 id: 16iFxjwsOPwmBwmjhb17WN
 status: PUBLISHED
 createdAt: 2023-03-30T16:25:46.370Z
-updatedAt: 2023-03-30T17:24:01.279Z
-publishedAt: 2023-03-30T17:24:01.279Z
+updatedAt: 2024-01-24T21:15:43.651Z
+publishedAt: 2024-01-24T21:15:43.651Z
 firstPublishedAt: 2023-03-30T17:24:01.279Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-bancolombia-bnpl
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Bancolombia BNPL. Por meio deste conector, sua loja pode realizar vendas por meio do BNPL (Buy Now Pay Later) do Bancolombia.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Bancolombia BNPL. Por meio deste provedor, sua loja pode realizar vendas por meio do BNPL (Buy Now Pay Later) do Bancolombia.
 
-Para configurar a afiliação Bancolombia BNPL, siga os passos abaixo:
+Para configurar Bancolombia BNPL, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __BancolombiaBNPL__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BancolombiaBNPL__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Bancolombia.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
@@ -36,4 +36,4 @@ Para configurar a afiliação Bancolombia BNPL, siga os passos abaixo:
 6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
 7. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Bancolombia BNPL pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Bancolombia BNPL pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-banqi.md b/docs/tutorials/pt/setting-up-payments-with-banqi.md
index 3085dcfed..960392987 100644
--- a/docs/tutorials/pt/setting-up-payments-with-banqi.md
+++ b/docs/tutorials/pt/setting-up-payments-with-banqi.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com banQi'
 id: 41rk9E7JUmCl683MJ9p52P
 status: PUBLISHED
 createdAt: 2023-03-30T12:31:49.459Z
-updatedAt: 2023-03-30T19:51:34.281Z
-publishedAt: 2023-03-30T19:51:34.281Z
+updatedAt: 2024-01-23T18:25:15.982Z
+publishedAt: 2024-01-23T18:25:15.982Z
 firstPublishedAt: 2023-03-30T13:04:03.008Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-banqi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento banQi. Por meio deste conector, sua loja pode realizar vendas pelo carnê banQi.
+Na VTEX, é possível realizar a integração com o provedor de pagamento banQi. Por meio deste provedor, sua loja pode realizar vendas pelo carnê banQi.
 
-Para configurar a afiliação banQi, siga os passos abaixo:
+Para configurar banQi, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __banQi__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __banQi__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta banQi.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-bitfy.md b/docs/tutorials/pt/setting-up-payments-with-bitfy.md
index eb466807e..6d5f5e0a5 100644
--- a/docs/tutorials/pt/setting-up-payments-with-bitfy.md
+++ b/docs/tutorials/pt/setting-up-payments-with-bitfy.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Bitfy'
 id: 2PSTfW4PsMh19K9y3DkQec
 status: PUBLISHED
 createdAt: 2022-08-15T17:30:29.886Z
-updatedAt: 2023-03-24T15:05:15.559Z
-publishedAt: 2023-03-24T15:05:15.559Z
+updatedAt: 2024-01-23T18:24:11.153Z
+publishedAt: 2024-01-23T18:24:11.153Z
 firstPublishedAt: 2022-08-15T17:41:45.501Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-bitfy
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Bitfy. Com este conector, sua loja pode realizar vendas por meio da Bitfy.
+Na VTEX, é possível realizar a integração com o Bitfy. Por meio deste provedor, sua loja pode realizar vendas por meio da Bitfy.
 
-Para configurar a afiliação Bitfy, siga os passos abaixo:
+Para configurar Bitfy, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __BitfyBr__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BitfyBr__ na barra de busca e clique sobre o nome do provedor.
 4. Clique no botão __Instalar app__ e siga as instruções de instalação.
 5. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Bitfy.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-bluepay.md b/docs/tutorials/pt/setting-up-payments-with-bluepay.md
index 5f600b54b..7cf39f0a1 100644
--- a/docs/tutorials/pt/setting-up-payments-with-bluepay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-bluepay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com BluePay'
 id: 26gzpfmEiwgpE8yhkaFS16
 status: PUBLISHED
 createdAt: 2023-04-03T14:55:51.576Z
-updatedAt: 2023-04-03T15:04:37.336Z
-publishedAt: 2023-04-03T15:04:37.336Z
+updatedAt: 2024-07-24T13:29:26.700Z
+publishedAt: 2024-07-24T13:29:26.700Z
 firstPublishedAt: 2023-04-03T15:04:37.336Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-bluepay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento BluePay. Por meio deste conector, sua loja pode realizar vendas pelo PIX.
+Na VTEX, é possível realizar a integração com o provedor de pagamento BluePay. Por meio deste provedor, sua loja pode realizar vendas pelo PIX.
 
-Para configurar a afiliação BluePay, siga os passos abaixo:
+Para configurar BluePay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __BluePay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BluePay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta BluePay.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-boletoflex.md b/docs/tutorials/pt/setting-up-payments-with-boletoflex.md
index 56a8bc8eb..6d006ef94 100644
--- a/docs/tutorials/pt/setting-up-payments-with-boletoflex.md
+++ b/docs/tutorials/pt/setting-up-payments-with-boletoflex.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com BoletoFlex'
 id: 3ikLbJGXMI6bkAm6YiglOx
 status: PUBLISHED
 createdAt: 2022-01-10T17:36:39.512Z
-updatedAt: 2023-03-22T19:10:38.069Z
-publishedAt: 2023-03-22T19:10:38.069Z
+updatedAt: 2024-01-23T15:50:34.329Z
+publishedAt: 2024-01-23T15:50:34.329Z
 firstPublishedAt: 2022-01-10T20:19:23.317Z
 contentType: tutorial
 productTeam: Financial
@@ -18,9 +18,10 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 BoletoFlex é um meio de pagamento no qual o usuário pode parcelar as suas compras no boleto, com taxas de juros pré-determinadas e sem a necessidade de utilizar cartão de crédito.
 
 ## Configurar afiliação de gateway BoletoFlex
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __BoletoFlex__.
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BoletoFlex__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta BoletoFlex.
 5. Clique em __Salvar__.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-bom-pra-credito.md b/docs/tutorials/pt/setting-up-payments-with-bom-pra-credito.md
index a623c038e..e7b4c1ee8 100644
--- a/docs/tutorials/pt/setting-up-payments-with-bom-pra-credito.md
+++ b/docs/tutorials/pt/setting-up-payments-with-bom-pra-credito.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Bom Pra Crédito'
 id: 2arjSmF9ksov6IXTEMaGkl
 status: PUBLISHED
 createdAt: 2022-08-10T19:47:21.251Z
-updatedAt: 2023-03-26T21:24:13.881Z
-publishedAt: 2023-03-26T21:24:13.881Z
+updatedAt: 2024-01-23T18:19:59.534Z
+publishedAt: 2024-01-23T18:19:59.534Z
 firstPublishedAt: 2022-08-10T19:52:22.782Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-bom-pra-credito
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Bom Pra Crédito. Com este conector, sua loja pode realizar vendas parceladas por meio da Bom Pra Crédito.
+Na VTEX, é possível realizar a integração com o gateway Bom Pra Crédito. Por meio desta integração, sua loja pode realizar vendas parceladas por meio da Bom Pra Crédito.
 
-Para configurar a afiliação Bom Pra Crédito, siga os passos abaixo:
+Para configurar Bom Pra Crédito, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __BomPraCredito__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __BomPraCredito__ na barra de busca e clique sobre o nome do provedor.
 4. Clique no botão __Instalar app__ e siga as instruções de instalação.
 5. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Bom Pra Crédito.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-braintree.md b/docs/tutorials/pt/setting-up-payments-with-braintree.md
new file mode 100644
index 000000000..dd6fac32a
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-braintree.md
@@ -0,0 +1,50 @@
+---
+title: 'Configurar pagamento com Braintree'
+id: 3Is3N2MmTldXPa2FtiV8xy
+status: PUBLISHED
+createdAt: 2022-08-11T12:01:04.231Z
+updatedAt: 2024-03-18T11:55:35.217Z
+publishedAt: 2024-03-18T11:55:35.217Z
+firstPublishedAt: 2022-08-11T12:27:01.656Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-braintree
+locale: pt
+legacySlug: configurar-pagamento-com-braintree
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Braintree.
+Por meio deste provedor, sua loja pode realizar vendas or cartões de crédito e débito.
+
+Para configurar Braintree-DCC, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Braintree-DCC__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos de cadastro __Chave de aplicação__ e __Token de aplicação__ com os dados fornecidos pelo Braintree.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Braintree na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Em __Campos do provedor__, selecione ou preencha os campos abaixo com as informações da sua conta Braintree:
+   - __Change Order Single Charge__
+   - __PayPal Secret (opcional)__
+   - __PayPal Client ID (opcional)__
+   - __PayPal Merchant ID (opcional)__
+   - __Merchant Account Id (opcional)__
+   - __Merchant Id (Braintree)__
+9. Clique em `Salvar`.
+
+Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#).
+
+Depois de seguir os passos indicados, Braintree-DCC pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+
diff --git a/docs/tutorials/pt/setting-up-payments-with-braspagv2.md b/docs/tutorials/pt/setting-up-payments-with-braspagv2.md
index 6b76fc4af..2fb99f98c 100644
--- a/docs/tutorials/pt/setting-up-payments-with-braspagv2.md
+++ b/docs/tutorials/pt/setting-up-payments-with-braspagv2.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamento com BraspagV2'
 id: 6gaw7zu9wlItgjfDVndRPn
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-01-20T19:41:22.154Z
-updatedAt: 2023-03-22T19:03:11.096Z
-publishedAt: 2023-03-22T19:03:11.096Z
+updatedAt: 2023-09-19T14:27:03.358Z
+publishedAt: 
 firstPublishedAt: 2022-01-21T16:38:10.049Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/setting-up-payments-with-brinks-cash-ecommerce.md b/docs/tutorials/pt/setting-up-payments-with-brinks-cash-ecommerce.md
index d685593bd..31c057999 100644
--- a/docs/tutorials/pt/setting-up-payments-with-brinks-cash-ecommerce.md
+++ b/docs/tutorials/pt/setting-up-payments-with-brinks-cash-ecommerce.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Brinks Cash Ecommerce'
 id: 5Zoex6NXtyzUFOCctdGjlZ
 status: PUBLISHED
 createdAt: 2022-08-15T17:49:34.660Z
-updatedAt: 2023-03-26T21:22:32.556Z
-publishedAt: 2023-03-26T21:22:32.556Z
+updatedAt: 2024-01-24T21:18:37.297Z
+publishedAt: 2024-01-24T21:18:37.297Z
 firstPublishedAt: 2022-08-15T18:04:15.733Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-brinks-cash-ecommerce
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Brinks Cash Ecommerce. Com este conector, sua loja pode realizar vendas por meio de Recaudo Efectivo (cobrança em dinheiro) na Colômbia.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Brinks Cash Ecommerce. Por meio deste provedor, sua loja pode realizar vendas por meio de Recaudo Efectivo (cobrança em dinheiro) na Colômbia.
 
-Para configurar a afiliação Brinks Cash Ecommerce, siga os passos abaixo:
+Para configurar Brinks Cash Ecommerce, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Brinks Cash Ecommerce__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Brinks Cash Ecommerce__ na barra de busca e clique sobre o nome do provedor.
 4. Clique no botão __Instalar app__ e siga as instruções de instalação.
 5. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Brinks Cash Ecommerce.
 6. Clique em `Salvar`.
@@ -34,5 +34,5 @@ Para configurar a afiliação Brinks Cash Ecommerce, siga os passos abaixo:
 4. Ative a condição no campo __Status__.
 5. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Brinks Cash Ecommerce pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Brinks Cash Ecommerce pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md b/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md
new file mode 100644
index 000000000..ed105d62b
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md
@@ -0,0 +1,66 @@
+---
+title: 'Configurar pagamento com CieloEcommerce'
+id: 6zuELBqEo0QzApbU4l7L4
+status: PUBLISHED
+createdAt: 2023-09-18T14:07:22.540Z
+updatedAt: 2024-03-27T17:13:40.793Z
+publishedAt: 2024-03-27T17:13:40.793Z
+firstPublishedAt: 2023-09-18T15:29:57.321Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-cieloecommerce
+locale: pt
+legacySlug: configurar-pagamento-com-cieloecommerce
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o CieloEcommerce. Por meio desta integração, sua loja pode realizar vendas com cartões de crédito, débito, private labels, cobranded, boletos bancário, PIX, entre outros. 
+
+Para configurar a CieloEcommerce, siga os passos abaixo:
+
+<blockquote><ui>1. No Admin VTEX, acesse <b>Configurações da loja > Pagamentos > Provedores</b>, ou digite <b>Provedores</b> na barra de busca no topo da página.</ui>
+
+<blockquote><ui>2. Na tela de provedores, clique no botão <b>Novo provedor</b>.</ui>
+
+<blockquote><ui>3. Digite o nome <b>CieloEcommerce</b> na barra de busca e clique sobre o nome do provedor.</ui>
+
+<blockquote><ui>4. Em <b>Autorização do provedor</b>, preencha os campos <b>Chave de aplicação</b> e <b>Token de aplicação</b> com o <b>MerchantID</b> e <b>MerchantKey</b> fornecidos pela CieloEcommerce.</ui>
+
+<blockquote><ui>5. Caso deseje modificar o nome de identificação a ser exibido para o provedor CieloEcommerce na tela do Admin VTEX, insira a informação no campo <b>Nome</b> em <b>Informações básicas</b>.</ui>
+
+<blockquote><ui>6. Em <b>Controle de pagamento</b>, selecione se deseja ativar o provedor em ambiente de teste clicando em <b>Ativar modo de teste</b>.</ui>
+
+<blockquote><ui>7. Caso deseje utilizar o <a href="https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx">Split de pagamento</a> em sua loja, selecione a opção <b>Ativar split de recebíveis e enviar recebedores de pagamento</b> e indique o <b>Responsável pelas tarifas de processamento de pagamentos</b> e <b>Responsável pelos estornos</b> (marketplace, sellers ou marketplaces e sellers).</ui>
+
+<blockquote><ui>8. Em <b>Integration</b>, selecione se o conector será utilizado como <b>Adquirencia</b> ou <b>Gateway</b>.</ui>
+
+<blockquote><ui>9. Em <b>Provider</b>, selecione o adquirente a ser utilizado com o provedor CieloEcommerce.</ui>
+
+<blockquote><ui>10. Em <b>IsSplit</b>, escolha se a opção de split estará disponível.</ui>
+
+<blockquote><ui>11. Em <b>UseMpi</b>, escolha se as transações serão autenticadas (3DS 2.0). Este campo é obrigatório para o tipo de pagamento débito. Caso selecione "True", siga para o Passo 12. Caso selecione "False", siga para o Passo 13.</ui>
+
+<blockquote><ui>12. Preencha os campos <b>MpiClientId</b>, <b>MpiClientSecret</b>, <b>MpiMerchantName</b>, <b>MpiMCC</b> e <b>MpiEstablishmentCode</b> com os seus dados de acesso Mpi.</ui>
+
+<blockquote><ui>13. Em <b>SoftDescriptor</b>, indique a informação a ser exibida para identificar a transação realizada na sua loja.</ui>
+
+<blockquote><ui>14. Em <b>AntifraudProvider</b>, selecione o provedor de antifraude que deseja utilizar com o CieloEcommerce.</ui>
+
+<blockquote><ui><div class="alert alert-warning">
+  Verifique com a Cielo se as opções de antifraude no CieloEcommerce já estão disponíveis para uso. Caso ainda estejam em desenvolvimento, ambos os campos descritos no passo 15 deverão ser deixados em branco. Para mais informações sobre como utilizar opções de antifraude em sua loja, acesse <a href="https://help.vtex.com/pt/tutorial/como-configurar-antifraude">Configurar o antifraude</a>.
+  </div></blockquote>
+<br>
+<blockquote><ui>15. Em <b>Antifraud</b> e <b>AntifraudSequenceCriteria</b>, selecione as opções conforme informações do antifraude CieloEcommerce.</ui>
+
+<blockquote><ui>16. Em <b>Captura</b>, selecione o período em que a captura do pagamento deve ser solicitada. O tempo padrão será realizado quatro dias após a autorização.</ui>
+
+<blockquote><ui>17. Selecione os campos <b>UseVerifyCard</b>, <b>AcceptInternationalCard</b>, <b>AcceptPrePaidCard</b>, <b>SaveCard</b> e <b>CancelRefundType</b> de acordo com as suas configurações no CieloEcommerce.</ui>
+
+<blockquote><ui>18. Clique em <b>Salvar</b>.</ui>
+
+Para configurar os métodos de pagamento a serem processados pela CieloEcommerce, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector CieloEcommerce pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-cielov4.md b/docs/tutorials/pt/setting-up-payments-with-cielov4.md
index c52373759..fc1376cee 100644
--- a/docs/tutorials/pt/setting-up-payments-with-cielov4.md
+++ b/docs/tutorials/pt/setting-up-payments-with-cielov4.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamento com CieloV4'
 id: 7M2CqJxprwpDtbgLZHBoiI
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-07-20T14:25:28.188Z
-updatedAt: 2023-03-26T21:25:12.482Z
-publishedAt: 2023-03-26T21:25:12.482Z
+updatedAt: 2023-09-19T14:27:43.425Z
+publishedAt: 
 firstPublishedAt: 2022-07-20T17:07:25.186Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/setting-up-payments-with-conekta.md b/docs/tutorials/pt/setting-up-payments-with-conekta.md
index 93a1a8797..21c561e1d 100644
--- a/docs/tutorials/pt/setting-up-payments-with-conekta.md
+++ b/docs/tutorials/pt/setting-up-payments-with-conekta.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Conekta'
 id: 7kiAD3SlnABF75xLSL3eSA
 status: PUBLISHED
 createdAt: 2022-08-11T12:41:42.110Z
-updatedAt: 2023-03-26T21:16:15.989Z
-publishedAt: 2023-03-26T21:16:15.989Z
+updatedAt: 2024-01-25T17:54:14.697Z
+publishedAt: 2024-01-25T17:54:14.697Z
 firstPublishedAt: 2022-08-11T12:54:43.579Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-conekta
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Conekta. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito, débito, OXXO e promissórias.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Conekta. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito, OXXO e promissórias.
 
-Para configurar a afiliação Conekta, siga os passos abaixo:
+Para configurar Conekta, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Conekta__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Conekta__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos abaixo de as informações da sua conta Conekta:
    - __Application Key__
    - __Application Token__
@@ -33,6 +33,8 @@ Para configurar a afiliação Conekta, siga os passos abaixo:
    - __Metadata 5__ 
 5. Clique em `Salvar`.
 
-Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete).
+Para configurar os métodos de pagamento a serem processados pela Conekta, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
 
-Depois de seguir os passos indicados, o conector Conekta pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, Conekta pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-crecoscorp.md b/docs/tutorials/pt/setting-up-payments-with-crecoscorp.md
index 14e3f68e2..86fb3e06f 100644
--- a/docs/tutorials/pt/setting-up-payments-with-crecoscorp.md
+++ b/docs/tutorials/pt/setting-up-payments-with-crecoscorp.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com CrecosCorp'
 id: 2NNAhG7ugxXhyk7U45hIeZ
 status: PUBLISHED
 createdAt: 2022-08-15T18:54:07.978Z
-updatedAt: 2022-08-15T18:59:46.828Z
-publishedAt: 2022-08-15T18:59:46.828Z
+updatedAt: 2024-01-25T17:37:02.016Z
+publishedAt: 2024-01-25T17:37:02.016Z
 firstPublishedAt: 2022-08-15T18:59:46.828Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: configurar-pagamento-com-dcrecoscorp
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos CrecosCorp. Com este conector, sua loja pode realizar vendas por meio de cartões private labels.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos CrecosCorp. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões private labels.
 
-Para configurar a afiliação CrecosCorp, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para configurar CrecosCorp, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 Para configurar o pagamento por cartões private labels, acesse [Configurar pagamentos com Cartões de Loja](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4#).
 
-Depois de seguir os passos indicados, o conector CrecosCorp pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, CrecosCorp pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-credimarcas.md b/docs/tutorials/pt/setting-up-payments-with-credimarcas.md
new file mode 100644
index 000000000..c0ac99ac0
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-credimarcas.md
@@ -0,0 +1,61 @@
+---
+title: 'Configurar pagamento com Credimarcas'
+id: 78855lTT6A1vX2wFURmxV
+status: PUBLISHED
+createdAt: 2023-12-18T13:12:50.542Z
+updatedAt: 2023-12-18T14:09:15.538Z
+publishedAt: 2023-12-18T14:09:15.538Z
+firstPublishedAt: 2023-12-18T14:09:15.538Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-credimarcas
+locale: pt
+legacySlug: configurar-pagamento-com-credimarcas
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Credimarcas. Com este conector, sua loja pode realizar vendas por meio de promissórias e cartões private labels.
+
+Para configurar o provedor Credimarcas, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Afiliações de Gateways__, clique no botão `+`.
+3. Clique no conector __credimarcas__.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Credimarcas.
+5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
+
+    - __Use O Comportamento Recomendado Pelo Processador de Pagamentos__: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).
+    - __Imediatamente: Captura Automática Ao Autorizar O Pagamento__: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.
+    - __Imediatamente: Captura Automática Ao Passar A Análise De Risco De Fraude__: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento – *Imediatamente: Captura Automática Ao Autorizar O Pagamento*.
+    - __Agendada: defina quando a captura automática será realizada__: ao selecionar esta opção, o campo __Prazo agendado em horas para a captura automática__ estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.
+    - __Desativado: Não Capturado Automaticamente__: a captura não é autorizada automaticamente. É importante atentar-se ao escolher esse comportamento, pois a demora no faturamento pode extrapolar o tempo de captura acordado com o provedor e levar à perda do pagamento.
+
+<ui>  6. Em <b>Type Payment</b>, selecione se o pagamento será realizado via "Payment App" ou "Redirect".</ui>
+
+<ui>  7. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão <b>Instalar app</b> e siga as instruções de instalação.</ui>
+
+<ui>  8. Clique em <b>Salvar.</b></ui>
+
+## Configurar Promissória
+
+<div class="alert alert-warning">
+  <p>Caso ainda não tenha configurado a promissória como método de pagamento em outros conectores de sua loja, acesse <a href="https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ">Configurar pagamentos com Promissória</a>.</p>
+</div>
+
+Para utilizar a Credimarcas com promissórias, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Em __Pagamento Customizado__, clique no botão correspondente ao nome utilizado para o método de pagamento por promissória (configurado anteriormente).
+4. Ative a condição no campo __Status__.
+5. Em __Processar com a afiliação__, selecione __confepartnerco-credimarcas-v0__.
+6. Se desejar, você também pode configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+7. Clique em `Salvar`.
+
+## Configurar Private label
+
+Para utilizar a Credimarcas com private labels, acesse [Configurar pagamentos com Cartões de Loja](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-cartoes-de-loja-bandeira-propria--428FgVdSGQUeAOoogkaIw4#).
+
+Depois de seguir os passos indicados, o conector Credimarcas pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+
diff --git a/docs/tutorials/pt/setting-up-payments-with-credit-key.md b/docs/tutorials/pt/setting-up-payments-with-credit-key.md
index 71724e79f..c819a51c2 100644
--- a/docs/tutorials/pt/setting-up-payments-with-credit-key.md
+++ b/docs/tutorials/pt/setting-up-payments-with-credit-key.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Credit Key'
 id: 4TtmhhkcXQYnkaCPUa9adB
 status: PUBLISHED
 createdAt: 2023-04-20T14:33:42.988Z
-updatedAt: 2023-04-20T14:51:31.849Z
-publishedAt: 2023-04-20T14:51:31.849Z
+updatedAt: 2024-01-25T17:48:48.188Z
+publishedAt: 2024-01-25T17:48:48.188Z
 firstPublishedAt: 2023-04-20T14:51:31.849Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-credit-key
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Credit Key. Com este conector, sua loja pode realizar vendas por meio do Credit Key.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Credit Key. Por meio deste provedor, sua loja pode realizar vendas por meio do Credit Key.
 
-Para configurar a afiliação Credit Key, siga os passos abaixo:
+Para configurar Credit Key, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __CreditKey__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __CreditKey__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Credit Key.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão __Instalar app__ e siga as instruções de instalação.
 6. Clique em `Salvar`.
@@ -36,5 +36,5 @@ Para configurar a afiliação Credit Key, siga os passos abaixo:
 6. Se desejar, você também pode configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 7. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Credit Key pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Credit Key pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-culqi.md b/docs/tutorials/pt/setting-up-payments-with-culqi.md
new file mode 100644
index 000000000..e3b604a84
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-culqi.md
@@ -0,0 +1,58 @@
+---
+title: 'Configurar pagamento com Culqi'
+id: 6LUOpYBpg48XSL8X0Le6e3
+status: PUBLISHED
+createdAt: 2023-11-16T13:31:38.132Z
+updatedAt: 2024-01-25T19:01:02.616Z
+publishedAt: 2024-01-25T19:01:02.616Z
+firstPublishedAt: 2023-11-16T14:54:41.647Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-culqi
+locale: pt
+legacySlug: configurar-pagamento-com-culqi
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Culqi. Por meio deste provedor, sua loja pode realizar vendas por meio do Culqi.
+
+Para configurar Culqi, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Culqi__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__, __Application Token__ e __Public Key__, insira as informações que foram fornecidas pela Culqi.
+5. No campo __Captura automática de pagamento__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Use o comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Imediatamente: captura automática ao autorizar o pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Imediatamente: captura automática ao passar a análise de risco de fraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Imediatamente: Captura Automática Ao Autorizar O Pagamento").</li>
+   		<li><b>Agendada: defina quando a captura automática será realizada</b>: ao selecionar esta opção, o campo <b>Prazo agendado em horas para a captura automática</b> estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.</li>        
+   		<li><b>Desativado: não capturado automaticamente</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+6. Em __Aceptar tarjetas de crédito__, selecione se deseja aceitar cartões de crédito como meio de pagamento.
+7. Em __Aceptar YAPE__, selecione se deseja aceitar [YAPE](https://www.yape.com.pe/) como meio de pagamento.
+8. Em __Aceptar billeteras móviles__, selecione se deseja aceitar carteiras digitais como meio de pagamento.
+9. Em __Aceptar banca móvil o internet__, selecione se deseja aceitar pagamentos via dispositivos móveis e internet banking.
+10. Em __Aceptar agentes y bodegas__, selecione se deseja aceitar pagamentos via agentes e bodegas (armazéns).
+11. Em __Aceptar cuotéalo BCP__, selecione se deseja aceitar pagamentos parcelados via [cuotéalo BCP](https://www.viabcp.com/cuotealo).
+12. Em __Tiempo de expiración de pago__, selecione o período (em dias) para expirar os pagamentos.
+13. Nos campos __URL de logo__, __Tema elegido__, __RSA Id__, __Llave pública RSA__, __Usuario Webhook__ e __Password Webhook__, insira as informações que foram fornecidas pela Culqi.
+14. Em __Ativar divisão e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+15. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja__ > __Pagamentos__ > __Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Selecione a condição de pagamento __Culqi__.
+4. Preencha o campo __Nome da regra__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Se desejar utilizar um sistema antifraude, selecione a opção __Usar antifraude__.
+7. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, Culqi pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-dapp.md b/docs/tutorials/pt/setting-up-payments-with-dapp.md
new file mode 100644
index 000000000..6800d366b
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-dapp.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pagamento com Dapp'
+id: 1p0FGViQcgCinPyi0GNXYM
+status: PUBLISHED
+createdAt: 2023-09-08T17:59:03.453Z
+updatedAt: 2024-01-25T18:09:29.307Z
+publishedAt: 2024-01-25T18:09:29.307Z
+firstPublishedAt: 2023-09-08T18:08:01.746Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-dapp
+locale: pt
+legacySlug: configurar-pagamento-com-dapp
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Dapp. Por meio deste provedor, sua loja pode realizar vendas por meio do Dapp.
+
+Para configurar Dapp, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Dapp__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__, __Application Token__, __Clave 1 - Dapp__ e __Clave 2 - Dapp__ com as informações da sua conta Dapp.
+5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Dapp__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, Dapp pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-deuna.md b/docs/tutorials/pt/setting-up-payments-with-deuna.md
new file mode 100644
index 000000000..270853110
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-deuna.md
@@ -0,0 +1,49 @@
+---
+title: 'Configurar pagamento com Deuna'
+id: 5Y4BfCdbQWraZAyoSm0Zzr
+status: PUBLISHED
+createdAt: 2023-04-06T18:37:58.919Z
+updatedAt: 2024-01-23T18:11:08.945Z
+publishedAt: 2024-01-23T18:11:08.945Z
+firstPublishedAt: 2023-04-06T18:42:52.173Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-deuna
+locale: pt
+legacySlug: configurar-pagamento-com-deuna
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Deuna. Por meio deste provedor, sua loja pode realizar vendas por meio do Deuna.
+
+Para configurar Deuna, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __DEUNA__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Deuna.
+5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
+
+    - __Use O Comportamento Recomendado Pelo Processador de Pagamentos__: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).
+    - __Imediatamente: Captura Automática Ao Autorizar O Pagamento__: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.
+    - __Imediatamente: Captura Automática Ao Passar A Análise De Risco De Fraude__: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento – *Imediatamente: Captura Automática Ao Autorizar O Pagamento*.
+    - __Agendada: Defina Quando A Captura Automática Será Realizada__: ao selecionar esta opção, o campo __Prazo agendado em horas para a captura automática__ estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.
+    - __Desativado: Não Capturado Automaticamente__: a captura não é autorizada automaticamente. É importante atentar-se ao escolher esse comportamento, pois a demora no faturamento pode extrapolar o tempo de captura acordado com o provedor e levar à perda do pagamento.
+
+<ui>  6. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão <b>Instalar app</b> e siga as instruções de instalação.</ui>
+
+<ui>  7. Clique em <b>Salvar.</b></ui>
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique no método de pagamento __DEUNA__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o conector Deuna pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+
diff --git a/docs/tutorials/pt/setting-up-payments-with-digital-river-v2.md b/docs/tutorials/pt/setting-up-payments-with-digital-river-v2.md
index 476c2d08c..d6a3e46d4 100644
--- a/docs/tutorials/pt/setting-up-payments-with-digital-river-v2.md
+++ b/docs/tutorials/pt/setting-up-payments-with-digital-river-v2.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Digital River V2'
 id: 5dlXHutd9Ik6vtN3WP7GRP
 status: PUBLISHED
 createdAt: 2022-02-17T12:11:27.726Z
-updatedAt: 2023-03-26T21:59:25.157Z
-publishedAt: 2023-03-26T21:59:25.157Z
+updatedAt: 2024-01-24T17:19:19.577Z
+publishedAt: 2024-01-24T17:19:19.577Z
 firstPublishedAt: 2022-02-17T13:44:17.095Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-pagamento-com-digital-river-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Digital River V2. Por meio deste conector, sua loja pode realizar vendas por diversos [métodos de pagamentos](https://www.digitalriver.com/payment-method-guide/).
+Na VTEX, é possível realizar a integração com o provedor de pagamento Digital River V2. Por meio deste provedor, sua loja pode realizar vendas por diversos [métodos de pagamentos](https://www.digitalriver.com/payment-method-guide/).
 
-Para configurar a afiliação Digital River V2, siga os passos abaixo:
+Para configurar Digital River V2, siga os passos abaixo:
 
-<ui>1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.</ui>
+<ui>1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Provedores**, ou digite **Provedores** na barra de busca no topo da página.</ui>
 
-<ui>2. Na aba __Afiliações de Gateways__, clique no botão __+__.</ui>
+<ui>2. Na tela de provedores, clique no botão `Novo provedor`.</ui>
 
-<ui>3. Clique no conector __DigitalRiverV2__.</ui>
+<ui>3. Digite o nome __DigitalRiverV2__ na barra de busca e clique sobre o nome do provedor.</ui>
 
 <ui>4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Digital River V2.</ui>
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-dlocal-payments.md b/docs/tutorials/pt/setting-up-payments-with-dlocal-payments.md
index 2ed829e21..cca3ea81f 100644
--- a/docs/tutorials/pt/setting-up-payments-with-dlocal-payments.md
+++ b/docs/tutorials/pt/setting-up-payments-with-dlocal-payments.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com DLocal Payments'
 id: 50DpZAd6td8oJaAIzHfQB5
 status: PUBLISHED
 createdAt: 2023-04-03T13:40:15.432Z
-updatedAt: 2023-04-03T14:03:12.910Z
-publishedAt: 2023-04-03T14:03:12.910Z
+updatedAt: 2024-01-23T18:09:56.316Z
+publishedAt: 2024-01-23T18:09:56.316Z
 firstPublishedAt: 2023-04-03T14:03:12.910Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-dlocal-payments
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento DLocal Payments. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito, débito e boletos bancários.
+Na VTEX, é possível realizar a integração com o provedor de pagamento DLocal Payments. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito e boletos bancários.
 
-Para configurar a afiliação DLocal Payments, siga os passos abaixo:
+Para configurar DLocal Payments, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __DLocalPayments__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __DLocalPayments__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta DLocal Payments.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-dock.md b/docs/tutorials/pt/setting-up-payments-with-dock.md
index 07dff3fe6..c6ca813cf 100644
--- a/docs/tutorials/pt/setting-up-payments-with-dock.md
+++ b/docs/tutorials/pt/setting-up-payments-with-dock.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com a Dock'
 id: 3Y0tLnXjBcG9qxHwAHGbHn
 status: PUBLISHED
 createdAt: 2022-07-19T19:58:56.608Z
-updatedAt: 2023-03-26T21:25:49.936Z
-publishedAt: 2023-03-26T21:25:49.936Z
+updatedAt: 2024-01-23T18:08:45.414Z
+publishedAt: 2024-01-23T18:08:45.414Z
 firstPublishedAt: 2022-07-19T20:12:07.212Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-a-dock
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Dock. Por meio deste conector, sua loja pode realizar vendas por meio do cartão de crédito, débito e private labels.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Dock. Por meio deste provedor, sua loja pode realizar vendas por meio do cartão de crédito, débito e private labels.
 
-Para configurar a afiliação Dock, siga os passos abaixo:
+Para configurar Dock, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __DOCK__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __DOCK__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Dock.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-e-sitef.md b/docs/tutorials/pt/setting-up-payments-with-e-sitef.md
new file mode 100644
index 000000000..340c13948
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-e-sitef.md
@@ -0,0 +1,48 @@
+---
+title: 'Configurar pagamento com e-SiTef'
+id: 6UEi0QAlU6BXz5RgWj34Ac
+status: PUBLISHED
+createdAt: 2021-12-06T14:51:20.250Z
+updatedAt: 2024-03-14T16:59:21.753Z
+publishedAt: 2024-03-14T16:59:21.753Z
+firstPublishedAt: 2021-12-06T17:37:55.667Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-e-sitef
+locale: pt
+legacySlug: configurar-pagamento-com-e-sitef
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento e-Sitef. Por meio deste provedor, sua loja pode realizar vendas por cartões de crédito, débito, private labels, cobranded e PIX.
+
+Para configurar o e-Sitef, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __ESITEF__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta e-Sitef.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor e-Sitef na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. No campo __Captura antecipada (em horas)__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação). Você também pode desativar a função.
+9. Em __Alterar tempo máximo para captura automática (em dias)__, preencha com o período máximo de dias no qual deve ocorrer a captura automática.
+10. Em __Soft Descriptor__, você pode inserir uma string personalizada (caracteres) que serão impressos na fatura do cliente.
+11. Em __Habilitar Pré-autorização__, selecione se você deseja que as compras feitas com cartão de crédito tenham o valor reservado (pré-autorizada a captura após a aprovação da transação).
+12. No campo __Captura antecipada após anti-fraude (em horas)__, escolha em quanto tempo você deseja que a captura seja realizada (depois da análise do antifraude). Você também pode desativar a função.
+13. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela e-Sitef, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, e-Sitef pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md b/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md
new file mode 100644
index 000000000..d6f002adb
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md
@@ -0,0 +1,232 @@
+---
+title: 'Configurar pagamento com easypay marketplace'
+id: 7EbImm3pJ8xCVRNxF06chN
+status: DRAFT
+createdAt: 2023-09-18T19:52:45.357Z
+updatedAt: 2023-09-19T12:04:40.833Z
+publishedAt: 
+firstPublishedAt: 2023-09-19T00:11:57.369Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-easypay-marketplace
+locale: pt
+legacySlug: configurar-pagamento-com-easypay-marketplace
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, você pode integrar com o provedor de pagamento easypay. Por meio deste conector, sua loja pode efetuar vendas utilizando a easypay, MBWay e MultiBanco.
+
+Para utilizar a afiliação EasyPay no seu marketplace, é necessário:
+
+- [Instalar o app easypay](#instalar-o-app-easypay)
+- [Configurar o app easypay](#configurar-o-app-easypay)
+- [Configurar Webhook easypay](#configurar-webhook-easypay)
+- [Configurar afiliação easypay](#configurar-afiliacao-easypay)  
+
+<div class="alert alert-warning" role="alert">Caso sua loja não seja um marketplace, acesse os artigos <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay--3xJQqjMIn0ARDI1HcwK88J">Configurar pagamento com easypay</a> ou <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay-seller--5mYMCM1tiRiZO6PozuUncE">Configurar pagamento com easypay seller</a>.</div>
+
+## Instalar o app easypay
+
+Para instalar o app easypay, siga os passos abaixo:
+
+1. No [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), execute o comando `vtex login nomedaconta` para realizar o login em sua conta.
+2. Instale o app easypay por meio do comando `vtex install labsitpartnerpt.payment-provider-easypay`. 
+
+## Configurar o app easypay
+
+Após realizar a instalação do app easypay, você precisa configurá-lo. Para acessar a tela de configurações, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Hub de Extensões > Gerenciamento de Aplicativos__, ou digite __Gerenciamento de Aplicativos__ na barra de busca no topo da página.
+2. Localize o app __Easypay Payment Provider__ e clique em __Configurações__.
+
+As informações de configuração estão divididas em quatro seções:
+
+- [Credenciais easypay (obrigatório)](#credenciais-easypay)
+- [Pagamento (obrigatório)](#pagamento)
+- [Personalização do Checkout easypay (opcional)](#personalizacao-do-checkout-easypay)
+- [Modo sandbox](#modo-sandbox)
+
+![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+
+<div class="alert alert-warning" role="alert">Você deve realizar as configurações abaixo no <a href="https://backoffice.easypay.pt/">ambiente easypay</a>. O controle destas configurações é de responsabilidade da easypay, e portanto, a VTEX não garante que os passos abaixo estejam atualizados permanentemente. Utilize este documento como uma referência e consulte sua conta no <a href="https://backoffice.easypay.pt/">ambiente easypay</a> para informações atualizadas.</div>
+
+### Credenciais easypay
+
+As informações desta seção devem ser preenchidas obrigatoriamente.
+
+__Key ID e Key Value__: valor e ID da chave easypay.
+
+   <ui>1. No [ambiente easypay](https://backoffice.easypay.pt/), clique no logotipo da easypay localizado no canto superior esquerdo da tela, e na seta da conta <b>Marketplace</b>.</ui>
+
+![easypay_pt_10](//images.ctfassets.net/alneenqid6w5/4EEjKGvGS9CtKtpKoIxM6P/e872f7e1484e7498288ac9c214572261/easypay_pt_10.PNG)
+
+   <ui>2. Acesse <b>Web Services > Configuração API 2.0</b>.</ui>
+
+   <ui>3. No menu <b>Alias</b>, opção <b>Criar Dados de Pagamentos</b>, clique em <b>Chaves</b>.</ui>
+
+![easypay_pt_11](//images.ctfassets.net/alneenqid6w5/76UJMX2vIty0CSYqHSyvRM/25620b17b9a968615a66e71505e81c65/easypay_pt_11.png)
+
+   <ui>4. Copie e salve as informações <b>ID</b> e <b>Chave</b>. Caso deseje criar uma nova chave, clique em <b>+ Nova</b>.</ui>
+
+![easypay_pt_12](//images.ctfassets.net/alneenqid6w5/61bArIKoWC0mVXu8WmRlq7/ca541fe6220d0e6b1f74bf7816fe18a7/easypay_pt_12.PNG)
+
+__Merchant account UID__: identificação da conta do comerciante onde serão depositados os valores das compras dos produtos efetuados na loja. Caso não haja uma conta comerciante separada, é possível utilizar o “Account UID” da conta de pagamentos.
+
+   <ui>1. No [ambiente easypay](https://backoffice.easypay.pt/), clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois na conta “COMERCIANTE 1”, clique na seta.</ui>
+
+![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+
+   <ui>2. Copie e salve as informações do __Account UID__.</ui>
+
+![easypay_pt_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/084650f9a54f09ac4466c7c0c52e6ba8/easypay_pt_6.PNG)
+
+__Margin account UID__: identificação da conta de margens. 
+
+1. No menu lateral do [ambiente easypay](https://backoffice.easypay.pt/), clique em __Beneficiário__.
+2. Copie as informações e salve as informações do __Account UID__ disponíveis em __Conta de Margens__.
+
+![easypay_pt_13](//images.ctfassets.net/alneenqid6w5/6SjwHG131w2wUNlXLFcCD3/2853c1435b96a9be0f442236d36039c0/easypay_pt_13.PNG)
+
+__Refund account ID e Refund account key__: easypay refund keys ID e value.
+
+   <ui>1. No menu lateral do ambiente Easypay, acesse <b>Web Services > Configuração API 2.0</b>.</ui>
+
+   <ui>2. No menu <b>Alias</b>, opção <b>Conta de margens</b>, clique em <b>Chaves</b>.</b>.</ui>
+
+![easypay_pt_14](//images.ctfassets.net/alneenqid6w5/3Llo906P3snImorgYKdsEn/5df8f470383b6e45032959a3707fa399/easypay_pt_14.PNG)
+
+   <ui>3. Clique em <b>+ Nova</b>.</ui>
+
+![easypay_pt_15](//images.ctfassets.net/alneenqid6w5/3CQJbQd6HywrS4FVMNzrIp/6cfaca92ba1aa114173cc97862d325ac/easypay_pt_15.PNG)
+
+   <ui>4. Preencha o campo <b>Nome</b> com <b>Refund Account</b>.</ui>
+
+![easypay_pt_16](//images.ctfassets.net/alneenqid6w5/28yf4dj3pbum7HuzvO7FHH/49c04507ba1eb16fa85c6964786d50f5/easypay_pt_16.png)
+
+   <ui>5. Clique em <b>Salvar</b>.</ui>
+
+   <ui>6. Copie e salve as informações <b>ID</b> e <b>Chave</b>.</ui>
+
+![easypay_pt_17](//images.ctfassets.net/alneenqid6w5/4Syc7o7Twuasd3uFyw9F0W/b22ae772f368d8e25db2723ff88b5276/easypay_pt_17.png)
+
+<div class="alert alert-warning" role="alert">Os reembolsos são debitados diretamente de uma conta pertencente ao marketplace. Posteriormente, o marketplace deve solicitar ao seller o valor reembolsado.</div>
+
+### Pagamento
+
+Nesta seção, você deve indicar se a sua loja utilizará pagamentos assíncronos, síncronos ou ambos. Acesse a documentação easypay para verificar os [métodos de pagamentos](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) disponíveis e suas respectivas [siglas](https://docs.quality-utility.aws.easypay.pt/checkout/reference) de identificação.
+
+![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+
+__Tipos de pagamento assíncronos aceites__: métodos de pagamento assíncronos disponíveis para o cliente. Preencha apenas com as siglas dos tipos de Assíncronos, separados por vírgula, sem pontos e sem espaços.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| mb,dd,vi,sc | mb, dd, vi, sc |
+
+<div class="alert alert-warning" role="alert">Caso este campo seja preenchido, será obrigatório o preenchimento do campo <b>Dias para expiração de pagamentos assíncronos</b>.</div>
+
+__Tipos de pagamento síncronos aceites__: métodos de pagamento síncronos disponíveis para o cliente. Preencha apenas com as siglas dos tipos de Síncronos, separados por vírgula, sem pontos e sem espaços.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| cc,mbw,uf | cc, mbw, uf |
+
+__Dias para expiração de pagamentos assíncronos__: tempo de expiração (em dias) de pagamentos assíncronos. Preencha apenas o número de dias desejados. 
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 10 | 10 dias, Dez ou 10/05/2023 |
+
+### Personalização do Checkout easypay
+
+A easypay possui um layout de Checkout nativo configurado no app. Veja abaixo:
+
+![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+
+Caso deseje realizar algum tipo de personalização no Checkout nativo da easypay, preencha um ou mais dos campos nesta seção:
+
+- __Checkout logo URL__: logotipo a ser exibido no Checkout easypay. Preencha com o link do endereço da imagem a ser utilizada.
+- __Checkout background color__: cor do background. Preencha o código HEX da cor desejada. Padrão nativo: #ffffff.
+- __Checkout accent color__: cor dos destaques, padrão de botões e bordas dos inputs. Preencha o código HEX da cor desejada. Padrão nativo: #0d71f9.
+- __Checkout error color__: cor das mensagens de erros. Preencha o código HEX da cor desejada. Padrão nativo: #ff151f.
+- __Checkout input background color__: cor do background dos inputs. Preencha o código HEX da cor desejada. Padrão nativo: transparent.
+- __Checkout input border color__: cor da borda dos inputs. Preencha o código HEX da cor desejada. Padrão nativo: a mesma cor utilizada no __accent color__.
+- __Checkout input border radius__: permite definir o arredondamento das bordas dos inputs. Preencha com o valor desejado em pixels (apenas números). Padrão nativo: 50 pixels.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 35 | 35px |
+
+- __Checkout button background color__: cor do background dos botões. Preencha o código HEX da cor desejada. Padrão nativo: a mesma cor utilizada no __accent color__.
+- __Checkout button border radius__: permite definir o arredondamento das bordas dos botões. Preencha com o valor desejado em pixels (apenas números). Padrão nativo: 50 pixels.
+
+Exemplo:
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 30 | 30px |
+
+- __Checkout button box shadow__: opção que permite ativar ou desativar a sombra nos botões.
+- __Checkout font family__: fontes utilizadas em textos. Preencha com o _generic family name_, _web safe font_ ou link da fonte . Padrão nativo: Overpass. Exemplo correto: sans-serif, verdana, ou https://fonts.gstatic.com/s/overpass/v12/qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PPbM5qKl8Kuo8AzesE.woff2
+
+- __Checkout base font size__: permite definir o tamanho da fonte no elemento raíz. Preencha com o valor desejado em pixels (apenas números). Padrão nativo: 10 pixels.
+
+Exemplo:
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 11 | 11px |
+
+<div class="alert alert-warning" role="alert">Não utilize fontes acima de 12 pixels, pois poderão distorcer a visualização do layout.</b>.</div>
+
+### Modo Sandbox
+
+Para habilitar o ambiente de testes de desenvolvimento, selecione a opção __Ativar modo sandbox__. Você deve utilizar credenciais de teste.
+
+Após concluir o preenchimento dos campos de configuração, clique em __Salvar__.
+
+## Configurar webhook easypay
+
+Para configurar o webhook da easypay, sig os passos abaixo:
+
+   <ui>1. No [ambiente easypay](https://backoffice.easypay.pt/), clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois clique na seta da conta marketplace.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+   <ui>2. Acesse __Web Services > Configuração URL__.</ui>
+
+   <ui>3. Em __URL: Notificar__, preencha com o link abaixo, modificando apenas a informação do nome real de sua loja marketplace.</ui>
+
+`https://{nome-da-sua-conta}.myvtex.com/_v/labsitpartnerpt.payment-provider-easypay/webhook`
+
+![easypay_pt_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/5724ef2676c10b5f1eff6594eafb5412/easypay_pt_9.PNG)
+
+<div class="alert alert-warning" role="alert">Caso haja mais de uma conta de pagamento em seu marketplace, adicione um link para cada uma das contas existentes.</div>
+
+   <ui>4. Clique em __Submeter__.</ui>
+
+## Configurar afiliação easypay
+
+Para configurar a afiliação easypay, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba Afiliações de Gateways, clique no botão `+`.
+3. Clique no conector __easypay__.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta easypay.
+5. Em __Captura Automática de Pagamento__, selecione a opção __Use O Comportamento Recomendado Pelo Processador de Pagamentos__.
+6. Em __Ativar divisão e enviar recebedores?__, selecione a opção __Sim__.
+7. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela easypay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector easypay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
+
diff --git a/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md b/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md
new file mode 100644
index 000000000..db45677d2
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md
@@ -0,0 +1,51 @@
+---
+title: 'Configurar pagamento com easypay seller'
+id: 5mYMCM1tiRiZO6PozuUncE
+status: PUBLISHED
+createdAt: 2023-09-19T00:16:47.408Z
+updatedAt: 2023-09-28T11:36:30.237Z
+publishedAt: 2023-09-28T11:36:30.237Z
+firstPublishedAt: 2023-09-19T00:26:38.480Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-easypay-seller
+locale: pt
+legacySlug: configurar-pagamento-com-seller
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, você que é seller pode integrar os seus produtos em um marketplace que esteja integrado com o provedor de pagamento easypay. Por meio deste conector, você pode efetuar vendas utilizando a Easypay, MBWay e MultiBanco.
+
+Para utilizar a afiliação easypay no seu marketplace, é necessário:
+
+- [Instalar o app Easypay Seller Account](#instalar-o-app-easypay-seller-account)
+- [Configurar o app Easypay Seller Account](#configurar-o-app-easypay-seller-account)
+
+<div class="alert alert-warning" role="alert">Caso você deseje configurar easypay para outro contexto, que não o de seller, acesse os artigos <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay--3xJQqjMIn0ARDI1HcwK88J">Configurar pagamento com easypay</a> ou <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configurar pagamento com easypay no Marketplace</a>.</div>
+
+## Instalar o app Easypay Seller Account
+
+Para instalar o app Easypay Seller Account, siga os passos abaixo:
+
+1. No [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), execute o comando `vtex login nomedaconta` para realizar o login em sua conta.
+2. Instale o app easypay por meio do comando `vtex install easypaypartnerpt.easypay-seller`. 
+
+## Configurar o app Easypay Seller Account
+
+Após realizar a instalação do app Easypay Seller Account, você deve configurá-lo. Para acessar a tela de configurações, siga os passos abaixo:
+
+<blockquote><ui>1. No Admin VTEX, acesse <b>Hub de Extensões > Gerenciamento de Aplicativos</b>, ou digite <b>Gerenciamento de Aplicativos</b> na barra de busca no topo da página.</ui>
+
+<blockquote><ui>2. Localize o app <b>Easypay Seller Account</b> e clique em <b>Configurações</b>.</ui>
+
+<blockquote><ui>3. Na tela <b>Easypay Seller Account</b>, preencha os seguintes campos:</ui>
+
+<blockquote><ui>- <b>VTEX Marketplace Account</b>: URL da conta da VTEX na qual você está associado. Ex. https://{nome-da-sua-conta}.myvtex.com/admin</ui> 
+
+<blockquote><ui>- <b>Easypay Account UID</b>: identificação de sua conta seller onde serão depositados os valores das compras dos produtos efetuados na loja. Para obter esta informação, acesse o <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da Easypay localizado no canto superior da tela, e depois na conta desejada. Copie e salve a informação <b>Account UID</b>.</ui> 
+
+![easypay_pt_18](//images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/e9218fcccf92ed76e45024aa1c4c2285/easypay_pt_18.PNG)
+
+<blockquote><ui>4. Clique em <b>Salvar</b>.</ui>
+
diff --git a/docs/tutorials/pt/setting-up-payments-with-easypay.md b/docs/tutorials/pt/setting-up-payments-with-easypay.md
new file mode 100644
index 000000000..bc4ee41b8
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-easypay.md
@@ -0,0 +1,210 @@
+---
+title: 'Configurar pagamento com easypay'
+id: 3xJQqjMIn0ARDI1HcwK88J
+status: PUBLISHED
+createdAt: 2023-09-18T16:48:21.184Z
+updatedAt: 2024-06-17T15:38:51.146Z
+publishedAt: 2024-06-17T15:38:51.146Z
+firstPublishedAt: 2023-09-18T18:53:57.235Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-easypay
+locale: pt
+legacySlug: configurar-pagamento-com-easypay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, você pode integrar com o provedor de pagamento easypay. Por meio deste provedor, sua loja pode efetuar vendas utilizando a easypay, MBWay e MultiBanco.
+
+Para utilizar easypay, é necessário:
+
+- [Instalar o app easypay](#instalar-o-app-easypay)
+- [Configurar o app easypay](#configurar-o-app-easypay)
+- [Configurar Webhook easypay](#configurar-webhook-easypay)
+- [Configurar afiliação easypay](#configurar-afiliacao-easypay)
+- [Configurar pagamento com Apple Pay na easypay (opcional)](#configurar-pagamento-com-apple-pay-na-easypay-opcional)    
+
+<div class="alert alert-warning" role="alert">Caso você seja um marketplace ou seller, acesse os artigos <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configurar pagamento com easypay no Marketplace</a> ou <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay-seller--5mYMCM1tiRiZO6PozuUncE">Configurar pagamento com easypay seller</a>.</div>
+
+## Instalar o app easypay
+
+Para instalar o app easypay, siga os passos abaixo:
+
+1. No [VTEX IO CLI](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-install), execute o comando `vtex login nomedaconta` para realizar o login em sua conta.
+2. Instale o app easypay por meio do comando `vtex install easypaypartnerpt.payment-provider-easypay`. 
+
+## Configurar o app easypay
+
+Após realizar a instalação do App easypay, você precisa configurá-lo. Para acessar a tela de configurações, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Hub de Extensões > Gerenciamento de Aplicativos__, ou digite __Gerenciamento de Aplicativos__ na barra de busca no topo da página.
+2. Localize o app __Easypay Payment Provider__ e clique em __Configurações__.
+
+As informações de configuração estão divididas em quatro seções:
+
+- [Credenciais easypay (obrigatório)](#credenciais-easypay)
+- [Pagamento (obrigatório)](#pagamento)
+- [Personalização do Checkout easypay (opcional)](#personalizacao-do-checkout-easypay)
+- [Modo sandbox](#modo-sandbox)
+
+![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+
+<div class="alert alert-warning" role="alert">Você deve realizar as configurações abaixo no <a href="https://backoffice.easypay.pt/">ambiente easypay</a>. O controle destas configurações é de responsabilidade da easypay, e portanto, a VTEX não garante que os passos abaixo estejam atualizados permanentemente. Utilize este documento como uma referência e consulte sua conta no <a href="https://backoffice.easypay.pt/">ambiente easypay</a> para informações atualizadas.</div>
+
+### Credenciais easypay
+
+As informações desta seção devem ser preenchidas obrigatoriamente.
+
+__Key ID e Key Value__: valor e ID da chave easypay.
+
+<blockquote><ui>1. No <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da easypay localizado no canto superior esquerdo da tela, e na seta da conta desejada.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+<blockquote><ui>2. Acesse <b>Web Services > Configuração API 2.0 > Chaves</b>.</ui>
+
+![easypay_pt_3](//images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/912dd97df028290e81d6f90057093878/easypay_pt_3.PNG)
+
+<blockquote><ui>3. Copie e salve as informações <b>ID</b> e <b>Chave</b>.</ui>
+
+![easypay_pt_4](//images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/849733bfcb8535a272d38c08c39138d2/easypay_pt_4.PNG)
+
+__Merchant account UID__: identificação da conta do comerciante onde serão depositados os valores das compras dos produtos efetuados na loja. Caso não haja uma conta comerciante separada, é possível utilizar o “Account UID” da conta de pagamentos.
+
+<blockquote><ui>1. No <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois na conta “COMERCIANTE 1”, clique na seta.</ui>
+
+![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+
+<blockquote><ui>2. Copie e salve as informações do <b>Account UID</b>.</ui>
+
+![easypay_pt_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/084650f9a54f09ac4466c7c0c52e6ba8/easypay_pt_6.PNG)
+
+__Margin account UID__: identificação da conta de margens. 
+
+<div class="alert alert-info" role="alert">Este campo somente deverá ser preenchido quando a loja for um marketplace e realizar split de pagamentos. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-easypay-marketplace--3YllWiITcPEOpteuToEdO7">Configurar pagamento com easypay no Marketplace</a>.</div>
+
+__Refund account ID e Refund account key__: caso não exista conta específica de reembolso, o valor do __Key ID__ deverá ser preenchido no campo __Refund account ID__, e o valor de __Key value__ em __Refund account key__.
+
+### Pagamento
+
+Nesta seção, você deve indicar se a sua loja utilizará pagamentos assíncronos, síncronos ou ambos. Acesse a documentação easypay para verificar os [métodos de pagamentos](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) disponíveis e suas respectivas [siglas](https://docs.quality-utility.aws.easypay.pt/checkout/reference) de identificação.
+
+![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+
+__Tipos de pagamento assíncronos aceites__: métodos de pagamento assíncronos disponíveis para o cliente. Preencha apenas com as siglas dos tipos de Assíncronos, separados por vírgula, sem pontos e sem espaços.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| mb,dd,vi,sc | mb, dd, vi, sc |
+
+<div class="alert alert-warning" role="alert">Caso este campo seja preenchido, será obrigatório o preenchimento do campo <b>Dias para expiração de pagamentos assíncronos</b>.</div>
+
+__Tipos de pagamento síncronos aceites__: métodos de pagamento síncronos disponíveis para o cliente. Preencha apenas com as siglas dos tipos de Síncronos, separados por vírgula, sem pontos e sem espaços.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| cc,mbw,uf | cc, mbw, uf |
+
+__Dias para expiração de pagamentos assíncronos__: tempo de expiração (em dias) de pagamentos assíncronos. Preencha apenas o número de dias desejados. 
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 10 | 10 dias, Dez ou 10/05/2023 |
+
+### Personalização do Checkout easypay
+
+A easypay possui um layout de Checkout nativo configurado no app. Veja abaixo:
+
+![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+
+Caso deseje realizar algum tipo de personalização no Checkout nativo da easypay, preencha um ou mais dos campos nesta seção:
+
+- __Checkout logo URL__: logotipo a ser exibido no Checkout easypay. Preencha com o link do endereço da imagem a ser utilizada.
+- __Checkout background color__: cor do background. Preencha o código HEX da cor desejada. Padrão nativo: #ffffff.
+- __Checkout accent color__: cor dos destaques, padrão de botões e bordas dos inputs. Preencha o código HEX da cor desejada. Padrão nativo: #0d71f9.
+- __Checkout error color__: cor das mensagens de erros. Preencha o código HEX da cor desejada. Padrão nativo: #ff151f.
+- __Checkout input background color__: cor do background dos inputs. Preencha o código HEX da cor desejada. Padrão nativo: transparent.
+- __Checkout input border color__: cor da borda dos inputs. Preencha o código HEX da cor desejada. Padrão nativo: a mesma cor utilizada no __accent color__.
+- __Checkout input border radius__: permite definir o arredondamento das bordas dos inputs. Preencha com o valor desejado em pixels (apenas números). Padrão nativo: 50 pixels.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 35 | 35px |
+
+- __Checkout button background color__: cor do background dos botões. Preencha o código HEX da cor desejada. Padrão nativo: a mesma cor utilizada no __accent color__.
+- __Checkout button border radius__: permite definir o arredondamento das bordas dos botões. Preencha com o valor desejado em pixels (apenas números). Padrão nativo: 50 pixels.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 30 | 30px |
+
+- __Checkout button box shadow__: opção que permite ativar ou desativar a sombra nos botões.
+- __Checkout font family__: fontes utilizadas em textos. Preencha com o _generic family name_, _web safe font_ ou link da fonte . Padrão nativo: Overpass. Exemplo correto: sans-serif, verdana, ou https://fonts.gstatic.com/s/overpass/v12/qFda35WCmI96Ajtm83upeyoaX6QPnlo6_PPbM5qKl8Kuo8AzesE.woff2
+
+- __Checkout base font size__: permite definir o tamanho da fonte no elemento raíz. Preencha com o valor desejado em pixels (apenas números). Padrão nativo: 10 pixels.
+
+Exemplo:
+
+| Correto | Incorreto |
+| ---------------- | ---------------- |
+| 11 | 11px |
+
+<div class="alert alert-warning" role="alert">Não utilize fontes acima de 12 pixels, pois poderão distorcer a visualização do layout.</b></div>
+
+### Modo Sandbox
+
+Para habilitar o ambiente de testes de desenvolvimento, selecione a opção __Ativar modo sandbox__. Você deve utilizar credenciais de teste.
+
+Após concluir o preenchimento dos campos de configuração, clique em __Salvar__.
+
+## Configurar webhook easypay
+
+Para configurar o webhook da easypay, sig os passos abaixo:
+
+<blockquote><ui>1. No <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois clique na seta da conta desejada.</ui>
+
+![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+
+<blockquote><ui>2. Acesse <b>Web Services > Configuração URL</b>.</ui>
+
+<blockquote><ui>3. Em <b>URL: Notificar</b>, preencha com o link abaixo, modificando apenas a informação do nome real de sua loja.</ui>
+
+`https://{nome-da-sua-conta}.myvtex.com/_v/easypaypartnerpt.payment-provider-easypay/webhook`
+
+![easypay_pt_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/5724ef2676c10b5f1eff6594eafb5412/easypay_pt_9.PNG)
+
+<blockquote><ui>4. Clique em <b>Submeter</b>.</ui>
+
+## Configurar afiliação easypay
+
+Para configurar a afiliação easypay, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __easypay__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta easypay.
+5. Em __Captura Automática de Pagamento__, selecione a opção __Use O Comportamento Recomendado Pelo Processador de Pagamentos__.
+6. Em __Ativar divisão e enviar recebedores?__, selecione a opção __Sim__.
+7. Clique em `Salvar`.
+
+## Configurar pagamento com Apple Pay na easypay (opcional) 
+
+Para processar pagamentos com Apple Pay na easypay você precisa primeiramente realizar configurações para habilitar sua loja no ambiente da Apple Pay. Saiba mais em [Setting up Merchant ID in Apple Pay](https://developers.vtex.com/docs/guides/setting-up-merchant-id-in-apple-pay).
+
+Para configurar outros métodos de pagamento a serem processados pela easypay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector easypay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
+
diff --git a/docs/tutorials/pt/setting-up-payments-with-ebanx-local.md b/docs/tutorials/pt/setting-up-payments-with-ebanx-local.md
index 8e97db6c8..e0a0237b5 100644
--- a/docs/tutorials/pt/setting-up-payments-with-ebanx-local.md
+++ b/docs/tutorials/pt/setting-up-payments-with-ebanx-local.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Ebanx-Local'
 id: 6vVYppbwct3B4j8KuCAvUR
 status: PUBLISHED
 createdAt: 2023-03-22T17:09:50.665Z
-updatedAt: 2023-03-23T12:45:48.284Z
-publishedAt: 2023-03-23T12:45:48.284Z
+updatedAt: 2024-01-23T18:06:33.564Z
+publishedAt: 2024-01-23T18:06:33.564Z
 firstPublishedAt: 2023-03-22T17:34:38.586Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-ebanx-local
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Ebanx-Local. Por meio deste conector, sua loja pode realizar vendas por meio de boleto bancário, cartões de crédito e PIX.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Ebanx-Local. Por meio deste provedor, sua loja pode realizar vendas por meio de boleto bancário, cartões de crédito e PIX.
 
-Para configurar a afiliação Ebanx-Local, siga os passos abaixo:
+Para configurar Ebanx-Local, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __EBANX-Local__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __EBANX-Local__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Ebanx.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-ebanx.md b/docs/tutorials/pt/setting-up-payments-with-ebanx.md
index 0a562b885..9470c9ee3 100644
--- a/docs/tutorials/pt/setting-up-payments-with-ebanx.md
+++ b/docs/tutorials/pt/setting-up-payments-with-ebanx.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Ebanx'
 id: 4yKdQrt57AW7aElfHH4QKM
 status: PUBLISHED
 createdAt: 2023-03-22T14:27:42.440Z
-updatedAt: 2023-03-23T12:45:53.859Z
-publishedAt: 2023-03-23T12:45:53.859Z
+updatedAt: 2024-01-23T18:07:19.598Z
+publishedAt: 2024-01-23T18:07:19.598Z
 firstPublishedAt: 2023-03-22T17:04:49.283Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-ebanx
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Ebanx. Por meio deste conector, sua loja pode realizar vendas por meio de boleto bancário, cartões de crédito e PIX.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Ebanx. Por meio deste provedor, sua loja pode realizar vendas por meio de boleto bancário, cartões de crédito e PIX.
 
-Para configurar a afiliação Ebanx, siga os passos abaixo:
+Para configurar Ebanx, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Ebanx__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Ebanx__ na barra de busca e clique sobre o nome do provedor.
 4. Clique em __Autorizar__. Você será redirecionado para o ambiente do Ebanx.
 5. No ambiente do Ebanx, insira os seus dados de login e senha da conta Ebanx. Siga as instruções indicadas para concluir a vinculação da conta Ebanx com a VTEX.
 6. Ao retornar ao __Admin VTEX__, clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-egetnetv2.md b/docs/tutorials/pt/setting-up-payments-with-egetnetv2.md
index 2013bae7b..e7f954329 100644
--- a/docs/tutorials/pt/setting-up-payments-with-egetnetv2.md
+++ b/docs/tutorials/pt/setting-up-payments-with-egetnetv2.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com EgetnetV2'
 id: 6jfBE8ocN5T0xQo8BTGH31
 status: PUBLISHED
 createdAt: 2023-02-13T13:55:05.519Z
-updatedAt: 2023-02-13T14:12:54.200Z
-publishedAt: 2023-02-13T14:12:54.200Z
+updatedAt: 2024-03-14T18:21:39.711Z
+publishedAt: 2024-03-14T18:21:39.711Z
 firstPublishedAt: 2023-02-13T14:12:54.200Z
 contentType: tutorial
 productTeam: Financial
@@ -15,19 +15,21 @@ legacySlug: configurar-pagamento-com-egetnetv2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos EgetnetV2. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito, boletos e PIX.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos EgetnetV2. Por meio deste provedor, sua loja pode realizar vendas por cartões de crédito, boletos e PIX.
 
-Para configurar a afiliação EgetnetV2, siga os passos abaixo:
+Para configurar EgetnetV2, siga os passos abaixo:
 
-1. Acesse o __Admin__ VTEX.
-2. Clique em __Pagamentos__.
-3. Em seguida, clique em __Configurações__.
-4. Na aba __Afiliações de Gateways__, clique no botão `+`.
-5. Clique no conector __EgetnetV2__.
-6. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta EgetnetV2.
-7. Em __Ativar divisão e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __EgetnetV2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta EgetnetV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor EgetnetV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Caso deseje utilizar o [split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) em sua loja, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
 8. Clique em `Salvar`.
 
-Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#).
+Para configurar os métodos de pagamento a serem processados pela EgetnetV2, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-Depois de seguir os passos indicados, o conector EgetnetV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, EgetnetV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-etpay.md b/docs/tutorials/pt/setting-up-payments-with-etpay.md
index e655d1a69..aadd7bcd8 100644
--- a/docs/tutorials/pt/setting-up-payments-with-etpay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-etpay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com ETpay'
 id: 1vYO022oVj4MdVKP5fCMNx
 status: PUBLISHED
 createdAt: 2022-10-18T17:45:32.139Z
-updatedAt: 2023-03-21T20:54:12.646Z
-publishedAt: 2023-03-21T20:54:12.646Z
+updatedAt: 2024-01-24T17:24:23.326Z
+publishedAt: 2024-01-24T17:24:23.326Z
 firstPublishedAt: 2022-10-18T17:56:29.587Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-etpay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway ETpay. Com este conector, sua loja pode realizar vendas por meio da ETpay.
+Na VTEX, é possível realizar a integração com o gateway ETpay. Por meio deste provedor, sua loja pode realizar vendas por meio da ETpay.
 
-Para configurar a afiliação ETpay, siga os passos abaixo:
+Para configurar ETpay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __EtPayment__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __EtPayment__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta ETpay.
 5. Clique em `Salvar`.
 
@@ -33,5 +33,5 @@ Para configurar a afiliação ETpay, siga os passos abaixo:
 4. Ative a condição no campo __Status__.
 5. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector ETpay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, ETpay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-evopayments.md b/docs/tutorials/pt/setting-up-payments-with-evopayments.md
new file mode 100644
index 000000000..38f665301
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-evopayments.md
@@ -0,0 +1,46 @@
+---
+title: 'Configurar pagamento com EvoPayments'
+id: 7CxSgoftps0DHsfR8otQMf
+status: PUBLISHED
+createdAt: 2024-03-11T17:36:12.910Z
+updatedAt: 2024-03-14T16:37:46.611Z
+publishedAt: 2024-03-14T16:37:46.611Z
+firstPublishedAt: 2024-03-11T18:19:00.757Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-evopayments
+locale: pt
+legacySlug: configurar-pagamento-com-evopayments
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento EVO Payments. Por meio deste provedor, sua loja pode realizar vendas por meio do cartões de crédito, débito, private labels, cobranded e boletos.
+
+Para configurar a EVO Payments, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __EvoPayments__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta EVO Payments.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor EVO Payments na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Em __Habilitar autenticación 3DS__, selecione se deseja ativar a validação de segurança do 3DS.
+9. Em __Habilitar autorización y captura__, selecione se deseja ativar esta função.
+10. Em __Habilitar plan Iphone For Life__, selecione se deseja ativar esta opção.
+11. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela EVO Payments, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, EVO Payments pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-fcamara-payment-initiator.md b/docs/tutorials/pt/setting-up-payments-with-fcamara-payment-initiator.md
index 129f9469d..e54693f71 100644
--- a/docs/tutorials/pt/setting-up-payments-with-fcamara-payment-initiator.md
+++ b/docs/tutorials/pt/setting-up-payments-with-fcamara-payment-initiator.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com FCamara (Iniciador de pagamentos)'
 id: 4p5E3jc9J5xHkOI6AbnhTV
 status: PUBLISHED
 createdAt: 2023-04-03T15:12:23.123Z
-updatedAt: 2023-04-03T16:42:01.758Z
-publishedAt: 2023-04-03T16:42:01.758Z
+updatedAt: 2024-01-23T18:01:44.039Z
+publishedAt: 2024-01-23T18:01:44.039Z
 firstPublishedAt: 2023-04-03T16:42:01.758Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-fcamara-iniciador-de-pagamentos
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o iniciador de pagamento FCamara. Por meio deste conector, sua loja pode realizar vendas pelo PIX.
+Na VTEX, é possível realizar a integração com o iniciador de pagamento FCamara. Por meio dele, sua loja pode realizar vendas pelo PIX.
 
-Para configurar a afiliação FCamara, siga os passos abaixo:
+Para configurar FCamara, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __iniciadorfcamara__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __iniciadorfcamara__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta FCamara.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-fintoc.md b/docs/tutorials/pt/setting-up-payments-with-fintoc.md
new file mode 100644
index 000000000..df7be4723
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-fintoc.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pagamento com Fintoc'
+id: 3TIz2oxbNtzhypWiypqrOZ
+status: PUBLISHED
+createdAt: 2023-07-14T17:06:16.055Z
+updatedAt: 2024-01-24T17:39:34.960Z
+publishedAt: 2024-01-24T17:39:34.960Z
+firstPublishedAt: 2023-07-14T17:49:20.115Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-fintoc
+locale: pt
+legacySlug: configurar-pagamento-com-fintoc
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Fintoc. Por meio deste provedor, sua loja pode realizar vendas por meio da Fintoc.
+
+Para configurar Fintoc, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Fintoc__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__, __Application Token__ e __Secret Key__ com as informações da sua conta Fintoc.
+5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Fintoc__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o conector Fintoc pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-flywire.md b/docs/tutorials/pt/setting-up-payments-with-flywire.md
index 291714049..e33aaa0ff 100644
--- a/docs/tutorials/pt/setting-up-payments-with-flywire.md
+++ b/docs/tutorials/pt/setting-up-payments-with-flywire.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Flywire'
 id: 12nQ0teCWM1UUtd2Fo6lzO
 status: PUBLISHED
 createdAt: 2023-04-03T13:05:10.955Z
-updatedAt: 2023-04-03T13:32:26.361Z
-publishedAt: 2023-04-03T13:32:26.361Z
+updatedAt: 2024-01-25T18:15:31.540Z
+publishedAt: 2024-01-25T18:15:31.540Z
 firstPublishedAt: 2023-04-03T13:32:26.361Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-flywire
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Flywire. Com este conector, sua loja pode realizar vendas por meio de promissórias e do Flywire.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Flywire. Por meio deste provedor, sua loja pode realizar vendas por meio de promissórias e do Flywire.
 
-Para configurar a afiliação Flywire, siga os passos abaixo:
+Para configurar Flywire, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Flywire__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Flywire__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__, __Application Token__, __Recipient__, __Locale__, __Provider__ e __Callback version__ com as informações da sua conta 
 Flywire.
 5. Em __Environment__, escolha uma das duas opções: __Demo__ ou __Production__.
@@ -52,5 +52,5 @@ Depois, siga os passos abaixo:
 6. Se desejar, você também pode configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 7. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Flywire pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Flywire pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-fpay.md b/docs/tutorials/pt/setting-up-payments-with-fpay.md
index aa80f83fc..ec3e508f3 100644
--- a/docs/tutorials/pt/setting-up-payments-with-fpay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-fpay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Fpay'
 id: 6BaLIO2R7tOh6E1MmNoDXj
 status: PUBLISHED
 createdAt: 2022-10-18T19:13:32.326Z
-updatedAt: 2023-03-21T20:52:34.889Z
-publishedAt: 2023-03-21T20:52:34.889Z
+updatedAt: 2024-01-24T17:26:52.492Z
+publishedAt: 2024-01-24T17:26:52.492Z
 firstPublishedAt: 2022-10-18T19:42:03.523Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-fpay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Fpay. Com este conector, sua loja pode realizar vendas por meio de promissórias.
+Na VTEX, é possível realizar a integração com o gateway Fpay. Por meio deste provedor, sua loja pode realizar vendas por meio de promissórias.
 
-Para configurar a afiliação Fpay, siga os passos abaixo:
+Para configurar Fpay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Fpay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Fpay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Fpay.
 5. Clique em `Salvar`.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-geru.md b/docs/tutorials/pt/setting-up-payments-with-geru.md
new file mode 100644
index 000000000..45f8dc1ed
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-geru.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pagamento com Geru'
+id: 2XmYp4Uh1Yulv3a9puRgwm
+status: PUBLISHED
+createdAt: 2024-02-05T11:49:37.163Z
+updatedAt: 2024-03-13T14:10:42.303Z
+publishedAt: 2024-03-13T14:10:42.303Z
+firstPublishedAt: 2024-02-05T13:45:07.728Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-geru
+locale: pt
+legacySlug: configurar-pagamento-com-geru
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Geru. Por meio deste provedor, sua loja pode realizar vendas por meio do Geru e BNPL.
+
+Para configurar a Geru, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Geru__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Geru.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Geru na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Geru__ ou __BNPL__.
+4. Ative a condição no campo __Status__. Para utilizar o __BNPL__, em __Processar com a afiliação__, selecione a opção __boletoflex-geru-v0__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor Geru pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-gocuotas.md b/docs/tutorials/pt/setting-up-payments-with-gocuotas.md
new file mode 100644
index 000000000..7e88863cb
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-gocuotas.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pagamento com GOcuotas'
+id: 6oGcugCc3pXIJEhbOZ5YmV
+status: PUBLISHED
+createdAt: 2023-09-29T11:30:25.004Z
+updatedAt: 2024-02-05T13:42:55.988Z
+publishedAt: 2024-02-05T13:42:55.988Z
+firstPublishedAt: 2023-09-29T11:39:03.239Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-gocuotas
+locale: pt
+legacySlug: configurar-pagamento-com-gocuotas
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento GOcuotas. Por meio deste provedor, sua loja pode realizar vendas por meio do GOcuotas.
+
+Para configurar GOcuotas, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __GOcuotas___ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta GOcuotas.
+5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __GOcuotas__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, GOcuotas pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-guatapay.md b/docs/tutorials/pt/setting-up-payments-with-guatapay.md
new file mode 100644
index 000000000..0352247f2
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-guatapay.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pagamento com Guatapay'
+id: 57ilA6k1VKZjy0dgwSs7pu
+status: PUBLISHED
+createdAt: 2023-09-18T15:35:35.188Z
+updatedAt: 2024-01-25T17:04:24.009Z
+publishedAt: 2024-01-25T17:04:24.009Z
+firstPublishedAt: 2023-09-18T16:33:40.921Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-guatapay
+locale: pt
+legacySlug: configurar-pagamento-com-guatapay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Guatapay. Por meio deste provedor, sua loja pode realizar vendas por meio do Guatapay.
+
+Para configurar Guatapay, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Guatapay__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__, __Application Token__, __Client ID - Guatapay__ e __Client Secret - Guatapay__ com as informações da sua conta Guatapay.
+5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Guatapay__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, Guatapay pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-inswitch.md b/docs/tutorials/pt/setting-up-payments-with-inswitch.md
new file mode 100644
index 000000000..f119b4dc8
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-inswitch.md
@@ -0,0 +1,49 @@
+---
+title: 'Configurar pagamento com Inswitch'
+id: XxY7tbpg4GMrexGQfto6Q
+status: PUBLISHED
+createdAt: 2023-07-14T17:56:24.581Z
+updatedAt: 2024-01-24T17:44:57.275Z
+publishedAt: 2024-01-24T17:44:57.275Z
+firstPublishedAt: 2023-07-14T18:11:24.293Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-inswitch
+locale: pt
+legacySlug: configurar-pagamento-com-inswitch
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Inswitch. Por meio deste provedor, sua loja pode realizar vendas por meio do Inswitch.
+
+Para configurar Inswitch, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Inswitch__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__ e __Application Token__, insira as informações que foram fornecidas pela Inswitch.
+5. No campo __Captura automática de pagamento__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Use o comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Imediatamente: captura automática ao autorizar o pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Imediatamente: captura automática ao passar a análise de risco de fraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Imediatamente: Captura Automática Ao Autorizar O Pagamento").</li>
+   		<li><b>Agendada: defina quando a captura automática será realizada</b>: ao selecionar esta opção, o campo <b>Prazo agendado em horas para a captura automática</b> estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.</li>        
+   		<li><b>Desativado: não capturado automaticamente</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja__ > __Pagamentos__ > __Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Selecione a condição de pagamento __Inswitch__.
+4. Preencha o campo __Nome da regra__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Se desejar utilizar um sistema antifraude, selecione a opção __Usar antifraude__.
+7. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+8. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, Inswitch pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-itau-rede.md b/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
new file mode 100644
index 000000000..72e0cc24b
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
@@ -0,0 +1,91 @@
+---
+title: 'Configurar pagamento com Itaú Rede'
+id: 77BYOKxVzONWulAf8dTVSX
+status: PUBLISHED
+createdAt: 2024-04-18T15:03:32.890Z
+updatedAt: 2024-04-25T15:26:44.454Z
+publishedAt: 2024-04-25T15:26:44.454Z
+firstPublishedAt: 2024-04-25T14:54:53.085Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-itau-rede
+locale: pt
+legacySlug: configurar-pagamento-com-itau-rede
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Itaú Rede. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito.
+
+Para utilizar o Itaú Rede, é necessário:
+
+- [Obter credenciais no ambiente Userede](#obter-credenciais-no-ambiente-userede)
+- [Configurar Itaú Rede na VTEX](#configurar-itau-rede-na-vtex)
+- [Configurar condição de pagamento](#configurar-condicao-de-pagamento) 
+
+## Obter credenciais no ambiente Userede
+
+<div class="alert alert-warning">
+As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta no Itaú Rede para informações atualizadas.
+</div>
+
+Para obter as credenciais __Chave de aplicação__ e __Token de aplicação__ necessárias para configurar o Itaú Rede na VTEX, siga os passos abaixo:
+
+<blockquote><ui>1. Acesse o <a href="https://meu.userede.com.br/login">Portal Userede</a> com as informações de sua conta na Itaú Rede.</ui>
+
+<blockquote><ui>2. Selecione a conta na qual deseja transacionar pagamentos na VTEX e clique em <b>Aplicar</b>. Guarde o número da conta, pois ele deve ser utilizado no campo <b>Chave de aplicação</b> na seção <a href="#configurar-itau-rede-na-vtex">Configurar Itaú Rede na VTEX</a>.</ui> 
+
+![Itaú Rede_1](//images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
+
+<blockquote><ui>3. Após a tela atualizar para a conta desejada, no menu <b>para vender</b>, selecione a opção <b>e-commerce</b>.</ui>
+
+![Itaú Rede_2](//images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
+
+<blockquote><ui>4. Na página <b>e-commerce</b>, clique no card <b>chave de integração</b>.</ui>
+
+![Itaú Rede_3](//images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
+
+<blockquote><ui>5. Após ler as informações da chave de integração, clique em <b>li, estou ciente</b>.</ui>
+
+![Itaú Rede_4](//images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
+
+<blockquote><ui>6. Clique no botão <b>gerar nova chave</b>.</ui>
+
+![Itaú Rede_5](//images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
+
+<blockquote><ui>7. Verifique as informações descritas na janela <b>gerar nova chave de integração</b> e clique em <b>gerar nova chave</b>.</ui>
+
+![Itaú Rede_6](//images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
+
+<blockquote><ui>8. Após a criação da nova chave, clique em <b>copiar</b> e preserve a informação em um local seguro. Esta chave deverá ser utilizada no campo <b>Token de aplicação</b> na seção <a href="#configurar-itau-rede-na-vtex">Configurar Itaú Rede na VTEX</a>.</ui>
+
+<blockquote><ui><div class="alert alert-warning">
+Após uma chave de integração ser criada no ambiente Rede, não é possível acessá-la novamente em outros locais. Registre a informação da chave em um local protegido, e em caso de perda, repita o processo para gerar uma nova chave.
+  </div></ui></blockquote>
+
+## Configurar Itaú Rede na VTEX
+
+Para configurar o Itaú Rede, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __ItauRede__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ obtidos nos passos 2 e 8 da seção [Obter credenciais no ambiente Userede](#obter-credenciais-no-ambiente-userede).
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Itaú Rede na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __merchantName__, insira o nome de sua loja.
+8. Em __SoftDescriptor__, descreva a mensagem de identificação a ser exibida na transação realizada na sua loja.
+9. No campo __delayToAutoSettle__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude).
+10. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre o nome da bandeira do cartão de crédito desejado.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor Itaú Rede pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-iugu.md b/docs/tutorials/pt/setting-up-payments-with-iugu.md
index 30cfb6b3f..6a2dffa9a 100644
--- a/docs/tutorials/pt/setting-up-payments-with-iugu.md
+++ b/docs/tutorials/pt/setting-up-payments-with-iugu.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar pagamento com Iugu'
+title: 'Configurar pagamento com iugu'
 id: 2c1nAo5iR6jG1UySzRB89t
 status: PUBLISHED
 createdAt: 2022-03-31T18:58:08.146Z
-updatedAt: 2022-03-31T19:22:31.835Z
-publishedAt: 2022-03-31T19:22:31.835Z
+updatedAt: 2024-03-13T11:53:59.094Z
+publishedAt: 2024-03-13T11:53:59.094Z
 firstPublishedAt: 2022-03-31T19:22:31.835Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,69 @@ legacySlug: configurar-pagamento-com-iugu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Iugu. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito, boletos e PIX.
+A [iugu](https://partnerportal.vtex.com/iugu-156/p) é uma solução parceira da VTEX que disponibiliza as seguintes opções de pagamentos por meio de [checkout transparente](https://help.vtex.com/pt/tutorial/o-que-e-checkout-transparente--2Y4ECegUmcYUggmck2GOwe): cartão de crédito, pix e boleto bancário. Além disso, é possível realizar [operações de recorrência](https://help.vtex.com/pt/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW) e [split de pagamentos](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) (recebíveis e transação) entre marketplaces.
 
-Para configurar a afiliação Iugu, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para adicionar a iugu em sua loja, siga os passos abaixo:
 
-Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#).
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __iugu__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Chave de aplicação__ e __Token de aplicação__ insira as informações que foram fornecidas pela iugu ([ID da conta e Chave API](https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#localizando-id-da-conta-e-chave-api-no-painel-da-iugu)).
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor iugu na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Caso deseje utilizar o boleto bancário como meio de pagamento, em __Campos do provedor__, preencha o campo __Prazo de vencimento do boleto (em dias)__ com o mesmo valor configurado na sua área do cliente no portal da iugu.
+8. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Iugu pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+## Configurar condições de pagamento
+
+Para processar os meios de pagamento cartão de crédito, pix e boleto bancário com a iugu em sua loja, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre o meio de pagamento desejado (nome da bandeira do cartão de crédito, pix ou boleto bancário).
+4. Preencha o campo __Nome da condição__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Em __Processar com provedor__ selecione a opção iugu.
+7. Para pagamentos com cartão de crédito, selecione se deseja utilizar um sistema antifraude selecionando a opção __Usar solução antifraude__. Também é possível configurar se os pagamentos com cartão de crédito devem ser realizados [à vista ou parcelados (com e sem juros)](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455#a-vista).
+8. Se desejar, você também poderá configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+9. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor iugu pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento.
+
+<div class="alert alert-warning">
+  Antes de realizar transações por cartão de crédito, PIX ou Boleto bancário com a iugu em sua loja, verifique se esses meios de pagamento já estão habilitados em <a href="https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento">sua área do cliente no portal da iugu</a>.
+  </div>
+
+## Configurar split de pagamento no marketplace com iugu
+
+Para processar pagamentos em [marketplace com split de pagamento](https://help.vtex.com/pt/tutorial/pagamentos-em-marketplaces-vtex--2kYOfWCZYweJkYl18bw9yD#split-de-pagamentos) na iugu é necessário cadastrar os sellers de sua loja com o mesmo CNPJ no Admin VTEX e na sua área do cliente no portal da iugu. 
+
+Saiba mais sobre criar sellers na VTEX em [Adicionar seller](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392) e acesse as documentações da iugu para criar subcontas (sellers) via [área do cliente](https://support.iugu.com/hc/pt-br/articles/4411276874779-Como-criar-uma-subconta-pelo-painel-iugu-) ou [API](https://dev.iugu.com/docs/configurar-subconta-por-api). 
+
+### Habilitar split de recebíveis com iugu
+
+Para habilitar o split de recebíveis com a iugu em sua loja, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Digite o nome __iugu__ na barra de busca e clique sobre o nome do provedor.
+3. Em __Detalhes__, clique sobre o botão `Editar`.
+4. Em __Controle de pagamento__, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
+5. Clique em `Salvar`.
+
+<div class="alert alert-warning">
+  A opção de split de recebíveis não está disponível para utilização em ambiente de teste.
+  </div>
+
+Depois de seguir os passos indicados, a funcionalidade de split de recebíveis com o provedor iugu pode demorar até 10 minutos para ser ativada em sua loja.
+
+<div class="alert alert-warning">
+  Para definir as comissões específicas de cada seller em sua loja, acesse <b>Marketplace > Sellers> Gerenciamento</b> no Admin VTEX, selecione o seller desejado e insira os valores de comissão em <b>Comissões</b>.
+  </div>
+
+## Configurar recorrência com a iugu
+
+Para disponibilizar a [recorrência](https://help.vtex.com/pt/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW) como condição especial de pagamento por meio da iugu, é necessário:
+
+- Habilitar o modo recorrência no Admin VTEX.
+- Configurar os meios de pagamento cartão de crédito ou boleto bancário no Admin VTEX e na iugu.
+- Configurar a funcionalidade [assinaturas](https://help.vtex.com/pt/tutorial/como-configurar-assinaturas--1FA9dfE7vJqxBna9Nft5Sj) em sua loja.
diff --git a/docs/tutorials/pt/setting-up-payments-with-k8bank.md b/docs/tutorials/pt/setting-up-payments-with-k8bank.md
new file mode 100644
index 000000000..d69261034
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-k8bank.md
@@ -0,0 +1,44 @@
+---
+title: 'Configurar pagamento com K8Bank'
+id: 1ewZll1fwjClvp5Wl1uES1
+status: PUBLISHED
+createdAt: 2023-09-18T13:14:17.375Z
+updatedAt: 2024-01-23T17:56:32.780Z
+publishedAt: 2024-01-23T17:56:32.780Z
+firstPublishedAt: 2023-09-18T13:48:29.694Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-k8bank
+locale: pt
+legacySlug: configurar-pagamento-com-k8bank
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento K8Bank. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito, private labels, cobranded, boletos bancário e PIX.
+
+Para configurar o K8Bank, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __K8Bank__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__, __Application Token__, __cnpj__ e __CobrancasClientId__ insira as informações que foram fornecidas pelo K8Bank.
+5. No campo __Captura automática de pagamento__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Use o comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Imediatamente: captura automática ao autorizar o pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Imediatamente: captura automática ao passar a análise de risco de fraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Imediatamente: Captura Automática Ao Autorizar O Pagamento").</li>
+   		<li><b>Agendada: defina quando a captura automática será realizada</b>: ao selecionar esta opção, o campo <b>Prazo agendado em horas para a captura automática</b> estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.</li>        
+   		<li><b>Desativado: não capturado automaticamente</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+6. Em __Ativar divisão e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+
+7. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela K8Bank, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector K8Bank pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-kaiowa.md b/docs/tutorials/pt/setting-up-payments-with-kaiowa.md
index 6ea4fe80e..346ff0b5f 100644
--- a/docs/tutorials/pt/setting-up-payments-with-kaiowa.md
+++ b/docs/tutorials/pt/setting-up-payments-with-kaiowa.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Kaiowa'
 id: 1QfsSpAF0CHQFVd9qSGcA5
 status: PUBLISHED
 createdAt: 2023-04-06T18:20:04.972Z
-updatedAt: 2023-04-06T18:26:07.966Z
-publishedAt: 2023-04-06T18:26:07.966Z
+updatedAt: 2024-01-23T17:58:45.045Z
+publishedAt: 2024-01-23T17:58:45.045Z
 firstPublishedAt: 2023-04-06T18:26:07.966Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-kaiowa
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Kaiowa. Por meio deste conector, sua loja pode realizar vendas pela Kaiowa.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Kaiowa. Por meio deste provedor, sua loja pode realizar vendas pela Kaiowa.
 
-Para configurar a afiliação Kaiowa, siga os passos abaixo:
+Para configurar Kaiowa, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Kaiowa__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Kaiowa__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Kaiowa.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-khipu.md b/docs/tutorials/pt/setting-up-payments-with-khipu.md
index c3d989c89..27f2b0301 100644
--- a/docs/tutorials/pt/setting-up-payments-with-khipu.md
+++ b/docs/tutorials/pt/setting-up-payments-with-khipu.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Khipu'
 id: RcHQjURWDXa0doL15DiUj
 status: PUBLISHED
 createdAt: 2023-03-24T19:34:06.675Z
-updatedAt: 2023-03-30T14:08:54.819Z
-publishedAt: 2023-03-30T14:08:54.819Z
+updatedAt: 2024-01-24T17:53:53.676Z
+publishedAt: 2024-01-24T17:53:53.676Z
 firstPublishedAt: 2023-03-30T14:08:54.819Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-khipu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Khipu. Com este conector, sua loja pode realizar vendas por meio de promissórias.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Khipu. Por meio deste provedor, sua loja pode realizar vendas por meio de promissórias.
 
-Para configurar a afiliação Khipu, siga os passos abaixo:
+Para configurar Khipu, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Khipu__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Khipu__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Khipu.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
@@ -49,5 +49,5 @@ Caso ainda não tenha configurado a promissória como método de pagamento em ou
 6. Se desejar, você também pode configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 7. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Khipu pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Khipu pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-koin-payments.md b/docs/tutorials/pt/setting-up-payments-with-koin-payments.md
index 7af13d8b7..91d880348 100644
--- a/docs/tutorials/pt/setting-up-payments-with-koin-payments.md
+++ b/docs/tutorials/pt/setting-up-payments-with-koin-payments.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Koin-Payments'
 id: 5nTQFgTLGkPcJrqi7PKlO1
 status: PUBLISHED
 createdAt: 2022-08-18T12:40:14.512Z
-updatedAt: 2023-03-21T21:02:35.479Z
-publishedAt: 2023-03-21T21:02:35.479Z
+updatedAt: 2024-03-11T17:58:22.260Z
+publishedAt: 2024-03-11T17:58:22.260Z
 firstPublishedAt: 2022-08-18T12:56:36.170Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,20 @@ legacySlug: configurar-pagamento-com-koin-payments
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Koin-Payments. Por meio deste conector, sua loja pode realizar vendas por meio do cartões de crédito, débito, PIX e BoletoParceladoKoin.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Koin-Payments. Por meio deste provedor, sua loja pode realizar vendas por meio do cartões de crédito, débito, PIX e BoletoParceladoKoin.
 
-Para configurar a afiliação Koin-Payments, siga os passos abaixo:
+Para configurar a Koin-Payments, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Koin-Payments__.
-4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Koin-Payments.
-5. Clique em `Salvar`.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Koin-Payments__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Koin-Payments.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Koin-Payments na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Clique em `Salvar`.
 
-Para configurar os métodos de pagamento a serem processados pela Koin-Payments, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+Para configurar os métodos de pagamento a serem processados pela Koin-Payments, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
 Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Depois de seguir os passos indicados, o conector Koin-Payments pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Koin-Payments pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-koin.md b/docs/tutorials/pt/setting-up-payments-with-koin.md
index 46a5a0b2f..20fcfcfad 100644
--- a/docs/tutorials/pt/setting-up-payments-with-koin.md
+++ b/docs/tutorials/pt/setting-up-payments-with-koin.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamentos com Koin'
 id: 415vLlrVSUgeYYwycCaGiQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-24T19:48:39.401Z
-updatedAt: 2023-03-29T00:51:56.272Z
-publishedAt: 2023-03-29T00:51:56.272Z
+updatedAt: 2024-03-18T18:30:25.798Z
+publishedAt: 
 firstPublishedAt: 2018-04-24T21:17:23.835Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,8 @@ legacySlug: configurar-pagamentos-com-koin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Você pode configurar a Koin para receber pagamentos na sua loja. Nesta modalidade, seu cliente escolhe o __meio de pagamento__ Koin Pós-pago para efetuar a compra.
 
 Para configurar pagamentos com Koin, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-payments-with-kueski-pay.md b/docs/tutorials/pt/setting-up-payments-with-kueski-pay.md
index a7d8be92c..a414e0cf5 100644
--- a/docs/tutorials/pt/setting-up-payments-with-kueski-pay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-kueski-pay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Kueski Pay'
 id: 3jDfBFi33tMC12Ifi8M6X7
 status: PUBLISHED
 createdAt: 2022-08-10T17:09:57.124Z
-updatedAt: 2022-08-10T17:13:39.881Z
-publishedAt: 2022-08-10T17:13:39.881Z
+updatedAt: 2024-01-25T18:14:41.859Z
+publishedAt: 2024-01-25T18:14:41.859Z
 firstPublishedAt: 2022-08-10T17:13:39.881Z
 contentType: tutorial
 productTeam: Financial
@@ -15,10 +15,10 @@ legacySlug: configurar-pagamento-com-kueski-pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Kueski Pay. Com este conector, sua loja pode realizar vendas por meio de promissórias.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Kueski Pay. Por meio deste provedor, sua loja pode realizar vendas por meio de promissórias.
 
-Para configurar a afiliação Kueski Pay, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
+Para configurar Kueski Pay, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
 Para configurar o pagamento por meio de promissória, acesse [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria#).
 
-Depois de seguir os passos indicados, o conector Kueski Pay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Kueski Pay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-liquido-payment.md b/docs/tutorials/pt/setting-up-payments-with-liquido-payment.md
new file mode 100644
index 000000000..ff93f030d
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-liquido-payment.md
@@ -0,0 +1,32 @@
+---
+title: 'Configurar pagamento com Liquido Payment'
+id: 1GKtFlkdwLqabKAyK6pa3J
+status: PUBLISHED
+createdAt: 2023-09-08T20:08:53.120Z
+updatedAt: 2024-01-23T18:36:25.367Z
+publishedAt: 2024-01-23T18:36:25.367Z
+firstPublishedAt: 2023-09-08T20:28:25.462Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-liquido-payment
+locale: pt
+legacySlug: configurar-pagamento-com-liquido-payment
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Liquido Payment. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito e PIX.
+
+Para configurar Liquido Payment, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __LiquidoPayment__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__, __Application Token__ e __Client ID__ insira as informações que foram fornecidas pela Liquido Payment.
+5. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Liquido Payment, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector Liquido Payment pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-mach.md b/docs/tutorials/pt/setting-up-payments-with-mach.md
index 11f122243..b86a2ad72 100644
--- a/docs/tutorials/pt/setting-up-payments-with-mach.md
+++ b/docs/tutorials/pt/setting-up-payments-with-mach.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com MACH'
 id: 7h2NpL6p94NSkNFoOhVG4q
 status: PUBLISHED
 createdAt: 2022-10-18T17:01:32.912Z
-updatedAt: 2023-03-21T20:50:53.363Z
-publishedAt: 2023-03-21T20:50:53.363Z
+updatedAt: 2024-01-24T17:56:37.977Z
+publishedAt: 2024-01-24T17:56:37.977Z
 firstPublishedAt: 2022-10-18T17:19:40.370Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-mach
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway MACH. Com este conector, sua loja pode realizar vendas por meio da MACH.
+Na VTEX, é possível realizar a integração com o gateway MACH. Por meio desta integração, sua loja pode realizar vendas por meio da MACH.
 
-Para configurar a afiliação MACH, siga os passos abaixo:
+Para configurar MACH, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Mach-PayBot__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Mach-PayBot__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta MACH.
 5. Clique em `Salvar`.
 
@@ -33,5 +33,5 @@ Para configurar a afiliação MACH, siga os passos abaixo:
 4. Ative a condição no campo __Status__.
 5. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector MACH pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, MACH pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-meliuz.md b/docs/tutorials/pt/setting-up-payments-with-meliuz.md
index 9303c7d77..7ef160ce8 100644
--- a/docs/tutorials/pt/setting-up-payments-with-meliuz.md
+++ b/docs/tutorials/pt/setting-up-payments-with-meliuz.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Méliuz'
 id: 6ajsvgOtRWnKhmgZjnOmZN
 status: PUBLISHED
 createdAt: 2022-07-19T12:45:45.247Z
-updatedAt: 2023-03-26T21:35:11.618Z
-publishedAt: 2023-03-26T21:35:11.618Z
+updatedAt: 2024-01-23T18:53:00.570Z
+publishedAt: 2024-01-23T18:53:00.570Z
 firstPublishedAt: 2022-07-19T13:15:41.771Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-meliuz
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Méliuz. Com este conector, sua loja pode realizar vendas por meio do método de pagamento Quatro (Pix parcelado em 4x sem juros).
+Na VTEX, é possível realizar a integração com o gateway Méliuz. Por meio desta integração, sua loja pode realizar vendas por meio do método de pagamento Quatro (Pix parcelado em 4x sem juros).
 
-Para configurar a afiliação Méliuz, siga os passos abaixo:
+Para configurar Méliuz, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Méliuz__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Méliuz__ na barra de busca e clique sobre o nome do provedor.
 4. Clique no botão __Instalar app__ e siga as instruções de instalação.
 5. Preencha os campos __Application Key__ e __Application Token__ com as informações fornecidas pela Méliuz.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md b/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md
index 4aa170480..b14c89c2d 100644
--- a/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md
+++ b/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamentos com Mercado Pago'
 id: 2FPdhTma6QywUmwEcEUGoS
 status: PUBLISHED
 createdAt: 2018-03-08T21:11:28.158Z
-updatedAt: 2023-03-23T16:02:38.696Z
-publishedAt: 2023-03-23T16:02:38.696Z
+updatedAt: 2024-01-23T11:46:52.226Z
+publishedAt: 2024-01-23T11:46:52.226Z
 firstPublishedAt: 2018-03-08T22:43:32.092Z
 contentType: tutorial
 productTeam: Financial
@@ -23,10 +23,11 @@ Além de um subadquirente para processar transações realizadas com diversas co
 
 Abaixo estão as configurações para o conector __Mercado Pago__.
 
-## Configurar afiliação de gateway MercadoPago
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __MercadoPago__.
+## Configurar gateway MercadoPago
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __MercadoPago__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos de cadastro com as credenciais fornecidas pelo MercadoPago (campos _Client id_ e _Client secret_). Lembrando que elas não devem começar com __APP\_USR__.
 5. No campo __País__, selecione o país da sua loja.
 6. Em __Time Zone__, indique a região que define seu horário local.
diff --git a/docs/tutorials/pt/setting-up-payments-with-mobbex.md b/docs/tutorials/pt/setting-up-payments-with-mobbex.md
new file mode 100644
index 000000000..174f3f1f9
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-mobbex.md
@@ -0,0 +1,34 @@
+---
+title: 'Configurar pagamento com Mobbex'
+id: 2pgHFFeRRe7LRJOTCWigmh
+status: PUBLISHED
+createdAt: 2023-09-29T12:02:01.214Z
+updatedAt: 2024-01-24T13:31:18.969Z
+publishedAt: 2024-01-24T13:31:18.969Z
+firstPublishedAt: 2023-09-29T12:27:46.314Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-mobbex
+locale: pt
+legacySlug: configurar-pagamento-com-mobbex
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Mobbex. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito e Mobbex.
+
+Para configurar a Mobbex, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Mobbex__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Click to authorize VTEX to make payments__, clique em __Autorizar__. Neste momento, você será redirecionado para a página da Mobbex, onde deverá acessar a sua conta, e autorizar a conexão da VTEX na sua conta do Mobbex.
+5. Após autorizar, você retornará automaticamente para o Admin VTEX, e os campos __Application Key__, __Application Token__, __Application Id__ já estarão preenchidos.
+6. Em __Ativar split e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+7. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Mobbex, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector Mobbex pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-msc-payment.md b/docs/tutorials/pt/setting-up-payments-with-msc-payment.md
new file mode 100644
index 000000000..12a1e8dae
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-msc-payment.md
@@ -0,0 +1,51 @@
+---
+title: 'Configurar pagamento com MSC Payment'
+id: 6hPTXSe57DSCuo7i2r3cjV
+status: PUBLISHED
+createdAt: 2023-09-11T14:04:54.926Z
+updatedAt: 2024-01-25T17:06:19.483Z
+publishedAt: 2024-01-25T17:06:19.483Z
+firstPublishedAt: 2023-09-11T14:17:31.484Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-msc-payment
+locale: pt
+legacySlug: configurar-pagamento-com-msc-payment
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento MSC Payment. Por meio deste provedor, sua loja pode realizar vendas por meio do MSC Payment.
+
+Para configurar MSC Payment, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __MSC-Payment__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__, __Application Token__ e __tasaCambio__ insira as informações que foram fornecidas pela MSC Payment.
+5. No campo __Captura automática de pagamento__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Use o comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Imediatamente: captura automática ao autorizar o pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Imediatamente: captura automática ao passar a análise de risco de fraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Imediatamente: Captura Automática Ao Autorizar O Pagamento").</li>
+   		<li><b>Agendada: defina quando a captura automática será realizada</b>: ao selecionar esta opção, o campo <b>Prazo agendado em horas para a captura automática</b> estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.</li>        
+   		<li><b>Desativado: não capturado automaticamente</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+
+6. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar` app e siga as instruções de instalação.
+
+7. Clique em __Salvar__.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja__ > __Pagamentos__ > __Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão __+__.
+3. Selecione a condição de pagamento __MSC Payment__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Clique em __Salvar__.
+
+Depois de seguir os passos indicados, MSC Payment pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-netpay-and-netpay-checkout.md b/docs/tutorials/pt/setting-up-payments-with-netpay-and-netpay-checkout.md
index b1a051763..2819dc705 100644
--- a/docs/tutorials/pt/setting-up-payments-with-netpay-and-netpay-checkout.md
+++ b/docs/tutorials/pt/setting-up-payments-with-netpay-and-netpay-checkout.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com NetPay e NetPay Checkout'
 id: 4x03ZhET2ocg9jzx6y482Y
 status: PUBLISHED
 createdAt: 2023-03-02T12:01:13.847Z
-updatedAt: 2023-03-22T17:33:39.076Z
-publishedAt: 2023-03-22T17:33:39.076Z
+updatedAt: 2024-01-25T18:29:38.914Z
+publishedAt: 2024-01-25T18:29:38.914Z
 firstPublishedAt: 2023-03-02T12:47:50.707Z
 contentType: tutorial
 productTeam: Financial
@@ -15,21 +15,19 @@ legacySlug: configurar-pagamento-com-netpay-e-netpay-checkout
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento NetPay. Por meio deste conector, sua loja pode realizar vendas por meio de boleto bancário, cartões de crédito e redirect.
+Na VTEX, é possível realizar a integração com o provedor de pagamento NetPay. Por meio deste provedor, sua loja pode realizar vendas por meio de boleto bancário, cartões de crédito e redirect.
 
-Para configurar a afiliação NetPay, siga os passos abaixo:
+Para configurar NetPay, siga os passos abaixo:
 
-1. Acesse o __Admin__ VTEX.
-2. Clique em __Pagamentos__.
-3. Em seguida, clique em __Configurações__.
-4. Na aba __Afiliações de Gateways__, clique no botão `+`.
-5. Clique em um dos conectores: __NetPay__ ou __NetPayCheckout__.
-6. Preencha os campos __Application Key__, __Application Token__ e __Numero del comercio__ com as informações da sua conta NetPay.
-7. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
-8. Clique em `Salvar`.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __NetPay__ ou __NetPayCheckout__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__, __Application Token__ e __Numero del comercio__ com as informações da sua conta NetPay.
+5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+6. Clique em `Salvar`.
 
 Para configurar os métodos de pagamento a serem processados pela NetPay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
 
 Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Depois de seguir os passos indicados, o conector NetPay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, NetPay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-notes-payable.md b/docs/tutorials/pt/setting-up-payments-with-notes-payable.md
new file mode 100644
index 000000000..28fd4be5f
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-notes-payable.md
@@ -0,0 +1,57 @@
+---
+title: 'Configurar pagamentos com Promissória'
+id: 5pW7avTwtyQcMu4uiW8quQ
+status: PUBLISHED
+createdAt: 2018-06-21T20:20:24.484Z
+updatedAt: 2023-10-18T11:58:23.708Z
+publishedAt: 2023-10-18T11:58:23.708Z
+firstPublishedAt: 2018-06-25T15:42:31.515Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: configurar-pagamentos-com-promissoria
+locale: pt
+legacySlug: configurar-pagamentos-com-promissoria
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, sua loja pode receber pagamentos por meio de promissórias. Para isso, você deve seguir os seguintes passos:
+
+- [Configurar afiliação de gateway](#configurar-afiliacao-de-gateway)
+- [Configurar Promissória](#configurar-promissoria)
+- [Configurar condição de pagamento](#configurar-condicao-de-pagamento)
+
+## Configurar afiliação de gateway
+
+Para configurar uma afiliação de gateway, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
+
+<div class="alert alert-warning">
+Verifique se a afiliação de gateway desejada suporta o processamento de pagamento por promissória.
+</div>
+
+## Configurar Promissória
+
+Com uma das afiliações de gateway acima cadastrada, você deverá configurar o pagamento customizado __Promissória__.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
+2. Clique na aba __Pagamentos Customizados__.
+3. Em __Promissórias__, clique em uma das 5 caixas de configuração (Configurar).
+4. Preencha os seguinte campos com as devidas informações:
+
+- __Nome:__ Nome que será usado para identificar o pagamento.
+- __Descrição:__ Detalhes sobre a condição de pagamento.
+- __Validade da promissória:__ Tempo limite que seu cliente terá para pagar a promissória antes de perder a validade.
+- __Autorizar automaticamente:__ Autorize ou não os pagamentos de forma automática. Recomendamos essa opção somente para casos em que o pagamento é feito na entrega ou retirada do pedido na loja. Ao escolher Yes, o status do pedido muda automaticamente para Preparando Entrega, sem passar por nenhuma verificação de pagamento.
+- __Modificar margem:__ Margem percentual permitida para alteração no valor do pagamento realizado com promissória. Para alguns clientes, pode ser importante autorizar mudanças nos pedidos ([change order](https://help.vtex.com/pt/tutorial/change-mudanca-em-pedidos--3d1XLIgPQcwaKGyMiWaYog?&utm_source=autocomplete)). Nesse caso, o campo _Modificar margem_ deve ser preenchido para determinar a margem percentual de alteração permitida.
+- __Ativar divisão de pagamento:__ Escolha se utilizará a solução de [split de pagamentos](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx?&utm_source=autocomplete). Caso opte por essa opção, quando a venda envolver lojas do marketplace, a promissória será dividida entre os sellers e o marketplace.
+- __Faturamento automático:__ Quantidade de dias para faturamento automático da promissória após autorização. Promissórias são faturadas no momento da autorização do pagamento. Ao configurar esse campo, o faturamento deixará de acontecer na autorização e passará a ser feito após o número de dias definido pelo cliente.<br>
+
+<ul>  
+5. Clique em <b>Salvar</b>.  
+</ul>
+
+## Configurar condição de pagamento
+
+Depois de concluir todas as etapas, o pagamento por promissória estará configurado e pronto para ser utilizado em sua loja.
+
+Para associá-lo a uma condição de pagamento, siga o artigo [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
diff --git a/docs/tutorials/pt/setting-up-payments-with-nupay.md b/docs/tutorials/pt/setting-up-payments-with-nupay.md
index 88c18eac1..76b200359 100644
--- a/docs/tutorials/pt/setting-up-payments-with-nupay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-nupay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Nubank (NuPay)'
 id: 4nVjWfJw7PwraBHCoS45tc
 status: PUBLISHED
 createdAt: 2022-07-19T17:39:57.710Z
-updatedAt: 2023-03-26T21:17:16.116Z
-publishedAt: 2023-03-26T21:17:16.116Z
+updatedAt: 2024-01-23T19:13:04.800Z
+publishedAt: 2024-01-23T19:13:04.800Z
 firstPublishedAt: 2022-07-19T18:24:09.993Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-nupay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Nubank (NuPay). Com este conector, sua loja pode realizar vendas parceladas por meio do Nubank.
+Na VTEX, é possível realizar a integração com o gateway Nubank (NuPay). Por meio desta integração, sua loja pode realizar vendas parceladas por meio do Nubank.
 
-Para configurar a afiliação Nubank, siga os passos abaixo:
+Para configurar Nubank, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Nubank__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Nubank__ na barra de busca e clique sobre o nome do provedor.
 4. Clique no botão __Instalar app__ e siga as instruções de instalação.
 5. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Nubank.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-nuvei.md b/docs/tutorials/pt/setting-up-payments-with-nuvei.md
new file mode 100644
index 000000000..91c44aa8d
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-nuvei.md
@@ -0,0 +1,69 @@
+---
+title: 'Configurar pagamento com Nuvei'
+id: 67DjdrpIaZZmhXv9Iwa6Ev
+status: DRAFT
+createdAt: 2024-03-27T12:55:27.016Z
+updatedAt: 2024-03-27T17:47:53.436Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-nuvei
+locale: pt
+legacySlug: configurar-pagamento-com-nuvei
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o Nuvei. Por meio deste provedor, sua loja pode realizar vendas com cartões de crédito e débito.
+
+Para utilizar o Nuvei, siga os passos abaixo:
+
+- [Configurar Nuvei na VTEX](#configurar-provedor-nuvei-na-vtex)
+- [Configurar o DMN Url na Nuvei](#configurar-dmn-url-na-nuvei)
+
+## Configurar provedor Nuvei na VTEX
+
+<blockquote><ui>1. No Admin VTEX, acesse <b>Configurações da loja > Pagamentos > Provedores</b>, ou digite <b>Provedores</b> na barra de busca no topo da página.</ui>
+
+<blockquote><ui>2. Na tela de provedores, clique no botão <b>Novo provedor</b>.</ui>
+
+<blockquote><ui>3. Digite o nome <b>nuvei-payment-provider</b> na barra de busca e clique sobre o nome do provedor.</ui>
+
+<blockquote><ui>4. Em <b>Autorização do provedor</b>, preencha os campos <b>Chave de aplicação</b> e <b>Token de aplicação</b> com as informações da sua conta Nuvei.</ui>  
+
+<blockquote><ui>5. Caso deseje modificar o nome de identificação a ser exibido para o provedor CieloEcommerce na tela do Admin VTEX, insira a informação no campo <b>Nome</b> em <b>Informações básicas</b>.</ui>
+
+<blockquote><ui>6. Em <b>Controle de pagamento</b>, selecione se deseja ativar o provedor em ambiente de teste clicando em <b>Ativar modo de teste</b>.</ui>
+
+<blockquote><ui>7. Para preencher os campos <b>Merchant Id</b>, <b>Merchant Site Id</b> e <b>Client Secret</b> (Secret Key), acesse as informações disponíveis em <b>Settings > My Integration Settings</b> dentro do painel de controle de sua conta no ambiente Nuvei.</ui>
+
+<blockquote><ui><div class="alert alert-warning">
+ A Nuvei possui credenciais (Merchant Id, Merchant Site Id e Client Secret) específicas para cada tipo de ambiente. Acesse os ambientes de teste <a href="sandbox.nuvei.com">(Integration)</a> e <a href="cpanel.nuvei.com">Live</a> para identificar as informações relativas a cada um deles.
+  </div></blockquote>
+<br>  
+<blockquote><ui>8. Em <b>Environment</b>, selecione se deseja configurar o provedor Nuvei no ambiente <b>Integration</b> ou <b>Live</b>.</ui>
+
+<blockquote><ui>9. Em <b>Test 3ds challenge Integration only</b>, caso você tenha selecionado o ambiente de teste (<b>Integration</b>) é possível realizar testes de segurança 3DS por meio das opções <b>Force 3ds Challenge</b>, <b>Force 3ds Frictionless</b> ou <b>User cardHolder name</b>. Para mais informações sobre os testes, acesse a documentação <a href="https://docs.nuvei.com/documentation/integration/testing/testing-cards/?highlight=test%20cards#3d-secure-v2-test-scenarios">Nuvei</a>.</ui>
+
+ <blockquote><ui><div class="alert alert-warning">
+   Sempre que o <b>Environment</b> do provedor for configurado como <b>Live</b>, a opção selecionada para o campo <b>Test 3ds challenge Integration only</b> deve ser <b>User cardHolder name</b>.
+  </div></blockquote>
+<br>  
+<blockquote><ui>10. Clique em <b>Salvar</b>.</ui>
+
+## Configurar DMN Url na Nuvei
+
+Para configurar a informação DMN Url na Nuvei, siga os passos abaixo:
+
+1. Acesse o seu ambiente Nuvei de teste ([Integration](sandbox.nuvei.com)) ou [Live](cpanel.nuvei.com).
+2. No menu __Settings__, clique em __My Integration settings__.
+3. Em __DMN URL__, substitua o campo __{account-name}__ com o nome de sua conta VTEX.
+
+`https://master--{account-name}.myvtex.com/_v/api/nuvei-payment-provider/v0/dmn`
+
+Para configurar os métodos de pagamento a serem processados pela Nuvei, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o provedor Nuvei pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagaleve.md b/docs/tutorials/pt/setting-up-payments-with-pagaleve.md
index a55b06656..42e4815e9 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pagaleve.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pagaleve.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Pagaleve'
 id: 3ro5eb99noG7T4QpoQaJI5
 status: PUBLISHED
 createdAt: 2022-06-22T16:26:18.290Z
-updatedAt: 2023-03-26T21:40:42.801Z
-publishedAt: 2023-03-26T21:40:42.801Z
+updatedAt: 2024-01-23T19:14:42.547Z
+publishedAt: 2024-01-23T19:14:42.547Z
 firstPublishedAt: 2022-06-22T16:33:24.266Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-pagaleve
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Pagaleve. Com este conector, sua loja pode realizar vendas parceladas e sem cartão por meio da Pagaleve.
+Na VTEX, é possível realizar a integração com o gateway Pagaleve. Por meio desta integração, sua loja pode realizar vendas parceladas e sem cartão por meio da Pagaleve.
 
-Para configurar a afiliação Pagaleve, siga os passos abaixo:
+Para configurar Pagaleve, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Pagaleve__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Pagaleve__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Pagaleve.
 5. Em __Pagaleve__, preencha a informação fornecida pela Pagaleve.
 6. Em __Ativar split e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagarmev3.md b/docs/tutorials/pt/setting-up-payments-with-pagarmev3.md
index b3aa08432..fa1795d8a 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pagarmev3.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pagarmev3.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com PagarMeV3'
 id: 5PMavdamrVijwIrHas9ndE
 status: PUBLISHED
 createdAt: 2022-06-22T17:05:12.930Z
-updatedAt: 2023-03-26T21:02:02.940Z
-publishedAt: 2023-03-26T21:02:02.940Z
+updatedAt: 2024-03-11T14:27:05.534Z
+publishedAt: 2024-03-11T14:27:05.534Z
 firstPublishedAt: 2022-06-22T17:51:37.670Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,21 @@ legacySlug: configurar-pagamento-com-pagarmev3
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos PagarMeV3. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito e débito, boletos e PIX.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos PagarMeV3. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito e débito, boletos e PIX.
 
-Para configurar a afiliação PagarMeV3, siga os passos abaixo:
+Para configurar PagarMeV3, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __PagarMeV3__.
-4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta PagarMeV3.
-5. Em __Ativar split e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
-6. Clique em `Salvar`.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagarMeV3__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PagarMeV3.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagarMeV3 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Caso deseje utilizar o [split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) em sua loja, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
+8. Clique em `Salvar`.
 
-Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#).
+Para configurar os métodos de pagamento a serem processados pela PagarMeV3, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-Depois de seguir os passos indicados, o conector PagarMeV3 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PagarMeV3 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagbrasilv2.md b/docs/tutorials/pt/setting-up-payments-with-pagbrasilv2.md
new file mode 100644
index 000000000..7a3484c1e
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-pagbrasilv2.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pagamento com PagBrasilV2'
+id: 5ONHAWmRbZpNIDPXCkNJXD
+status: PUBLISHED
+createdAt: 2024-03-13T16:31:07.244Z
+updatedAt: 2024-03-13T22:24:02.876Z
+publishedAt: 2024-03-13T22:24:02.876Z
+firstPublishedAt: 2024-03-13T22:21:24.967Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: configurar-pagamento-com-pagbrasilv2
+locale: pt
+legacySlug: configurar-pagamento-com-pagbrasilv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PagBrasilV2. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de débito e crédito, boleto, promissórias e PIX.
+
+Para configurar o PagBrasilV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagBrasil-v2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PagBrasilV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagBrasilV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __External Service Url__ (URL externa do serviço), insira a URL externa que vai estar associada a `/pvt/payments?an={AccountName}`.
+7. Em __Implements Installments Service__ (Implementação do serviço de parcelamentos), selecione se deseja usar serviços externos de parcelamento ou o que está configurado no portal. Caso escolha a opção __Sim__, o sistema vai utilizar a URL configurada no campo __Installments Service Url__ (URL serviço de parcelamentos).
+8. Em __External Cancellation Service__ (Serviço de cancelamento externo), selecione se deverá ser utilizado um serviço de cancelamento externo. Caso escolha a opção __Sim__, o sistema irá acessar a URL configurada no campo __External Service Url__ (URL externa do serviço).
+9. Em __Installments Service Url__ (URL serviço de parcelamentos), insira a URL externa que vai estar associada a `/options`.
+10. Em __SoftDescriptor__ (Descrição da transação), indique qual informação deverá aparecer para identificar a transação realizada na sua loja.
+11. Em __Captura antecipada__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude). Esta função também pode ser desativada.
+12. Em __Tem um antifraude contratado com essa afiliação?__, informe se deseja usar um antifraude.
+13. Clique em __Salvar__.
+
+Para configurar os métodos de pagamento a serem processados pela PagBrasilV2, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PagBrasilV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
diff --git a/docs/tutorials/pt/setting-up-payments-with-paghiperv2.md b/docs/tutorials/pt/setting-up-payments-with-paghiperv2.md
new file mode 100644
index 000000000..af2b01d09
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-paghiperv2.md
@@ -0,0 +1,36 @@
+---
+title: 'Configurar pagamento com PagHiperV2'
+id: 131E6zBcTTkzZtL82cZh1x
+status: PUBLISHED
+createdAt: 2024-03-14T12:01:07.521Z
+updatedAt: 2024-03-14T12:18:12.256Z
+publishedAt: 2024-03-14T12:18:12.256Z
+firstPublishedAt: 2024-03-14T12:18:12.256Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-paghiperv2
+locale: pt
+legacySlug: configurar-pagamento-com-paghiperv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PagHiperV2. Por meio deste provedor, sua loja pode realizar vendas por boletos e PIX.
+
+Para configurar a PagHiperV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagHiperV2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PagHiperV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagHiperV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Limite Vencimento__, insira quantos dias o boleto permanecerá em aberto após o seu vencimento.
+7. Em __Exibir Frase fixa__, selecione se deseja incluir uma frase a ser exibida nos boletos emitidos.
+8. Em __Frase variável do vendedor__, caso desejar, configure a frase a ser exibida para cada boleto específico.
+9. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela PagHiperV2, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PagHiperV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-paghiperv3.md b/docs/tutorials/pt/setting-up-payments-with-paghiperv3.md
new file mode 100644
index 000000000..bff6d78c0
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-paghiperv3.md
@@ -0,0 +1,38 @@
+---
+title: 'Configurar pagamento com PagHiperV3'
+id: 1dYVbSK0yHNY5vp0gJj4fC
+status: PUBLISHED
+createdAt: 2024-03-14T12:27:03.520Z
+updatedAt: 2024-03-14T12:39:32.791Z
+publishedAt: 2024-03-14T12:39:32.791Z
+firstPublishedAt: 2024-03-14T12:39:32.791Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-paghiperv3
+locale: pt
+legacySlug: configurar-pagamento-com-paghiperv3
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PagHiperV3. Por meio deste provedor, sua loja pode realizar vendas por boletos e PIX.
+
+Para configurar a PagHiperV3, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagHiperV3__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PagHiperV3.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagHiperV3 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Limite Vencimento__, insira quantos dias o boleto permanecerá em aberto após o seu vencimento.
+8. Em __Dias corridos até o vencimento__, insira o prazo máximo de vencimento dos boletos. Para pagamentos por PIX não é possível alterar o prazo de expiração, sendo o prazo padrão de 15 minutos.
+9. Em __Exibir Frase fixa__, selecione se deseja incluir uma frase a ser exibida nos boletos emitidos.
+10. Em __Frase variável do vendedor__, caso desejar, configure a frase a ser exibida para cada boleto específico.
+11. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela PagHiperV3, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PagHiperV3 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagoefectivo.md b/docs/tutorials/pt/setting-up-payments-with-pagoefectivo.md
index 3c749f9a0..a5f85aeb3 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pagoefectivo.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pagoefectivo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamentos com PagoEfectivo'
 id: 1GGyNqZSYE2a8ga4UemYyw
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-09T20:26:14.388Z
-updatedAt: 2021-06-17T18:59:09.202Z
-publishedAt: 2021-06-17T18:59:09.202Z
+updatedAt: 2024-03-18T19:11:11.066Z
+publishedAt: 
 firstPublishedAt: 2018-04-09T21:57:41.363Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagoefectivov2.md b/docs/tutorials/pt/setting-up-payments-with-pagoefectivov2.md
new file mode 100644
index 000000000..5fe1177e5
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-pagoefectivov2.md
@@ -0,0 +1,55 @@
+---
+title: 'Configurar pagamento com PagoEfectivoV2'
+id: 63Raoh7hlWoWbMJOAacfMV
+status: PUBLISHED
+createdAt: 2024-02-06T11:22:25.720Z
+updatedAt: 2024-03-13T15:08:00.716Z
+publishedAt: 2024-03-13T15:08:00.716Z
+firstPublishedAt: 2024-02-06T11:40:45.294Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-pagoefectivov2
+locale: pt
+legacySlug: configurar-pagamento-com-pagoefectivov2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PagoEfectivoV2. Por meio deste provedor, sua loja pode realizar vendas por meio do Cuotealo e PagoEfectivo.
+
+Para configurar o PagoEfectivoV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagoEfectivoV2__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PagoEfectivoV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagoEfectivoV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Em __Campos do provedor__, insira as informações do __TradeID__, __TradeName__, __TradeEmail__ e __MaxActiveCipTime__ conforme as informações da sua conta PagoEfectivoV2.
+
+9. Em __Country__, selecione o país onde a transação de pagamento será realizada.
+
+10. Em __Currency__, selecione a moeda a ser utilizada na transação de pagamento.
+
+11. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __PagoEfectivo__ ou __Cuotealo__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor PagoEfectivoV2 pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagoexpress.md b/docs/tutorials/pt/setting-up-payments-with-pagoexpress.md
new file mode 100644
index 000000000..4b51249bd
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-pagoexpress.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pagamento com PagoExpress'
+id: 4VmPz20GbXZ1gMKPaJ09l0
+status: PUBLISHED
+createdAt: 2024-02-05T19:13:06.972Z
+updatedAt: 2024-03-13T15:13:51.485Z
+publishedAt: 2024-03-13T15:13:51.485Z
+firstPublishedAt: 2024-02-05T20:10:35.385Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-pagoexpress
+locale: pt
+legacySlug: configurar-pagamento-com-pagoexpress
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PagoExpress. Por meio deste provedor, sua loja pode realizar vendas por meio do PIX.
+
+Para configurar a PagoExpress, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PagoExpress__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PagoExpress.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PagoExpress na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __PIX__.
+4. Ative a condição no campo __Status__.
+5. Em __Processar com a afiliação__, selecione a opção __pagoexpresspartnerbr-pagoexpress-v0__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor PagoExpress pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagosweb.md b/docs/tutorials/pt/setting-up-payments-with-pagosweb.md
index 111496ee0..ce54cc06f 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pagosweb.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pagosweb.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamentos com PagosWEB'
 id: 2qKIeEPUBKqEGo2OyikyQw
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-05T15:48:50.151Z
-updatedAt: 2023-03-29T01:06:09.900Z
-publishedAt: 2023-03-29T01:06:09.900Z
+updatedAt: 2024-03-18T19:12:24.950Z
+publishedAt: 
 firstPublishedAt: 2018-04-05T22:01:49.141Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagamentos-com-pagosweb
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Você pode configurar o PagosWEB para receber pagamentos na sua loja. Nesta modalidade, seu cliente escolhe o __meio de pagamento__ PagosWEB para efetuar a compra.
 
 Para habilitar pagamentos com PagosWEB, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-payments-with-parcelex.md b/docs/tutorials/pt/setting-up-payments-with-parcelex.md
index 27c65aa8a..9f77bbb5e 100644
--- a/docs/tutorials/pt/setting-up-payments-with-parcelex.md
+++ b/docs/tutorials/pt/setting-up-payments-with-parcelex.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Parcelex'
 id: 2CqB2f1A8pxaAFyk8lxbzy
 status: PUBLISHED
 createdAt: 2022-06-22T19:16:08.714Z
-updatedAt: 2023-03-26T21:40:05.111Z
-publishedAt: 2023-03-26T21:40:05.111Z
+updatedAt: 2024-01-23T21:03:35.230Z
+publishedAt: 2024-01-23T21:03:35.230Z
 firstPublishedAt: 2022-06-22T19:19:11.694Z
 contentType: tutorial
 productTeam: Financial
@@ -15,23 +15,23 @@ legacySlug: configurar-pagamento-com-parcelex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway Parcelex. Com este conector, sua loja pode realizar vendas parceladas e sem cartão por meio da Parcelex.
+Na VTEX, é possível realizar a integração com o gateway Parcelex. Por meio desta integração, sua loja pode realizar vendas parceladas e sem cartão por meio da Parcelex.
 
-Para configurar a afiliação Parcelex, siga os passos abaixo:
+Para configurar Parcelex, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Parcelex__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Parcelex__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Parcelex.
 5. Clique em `Salvar`.
 
 ## Configurar condição de pagamento
-1. 
-2. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-3. Na aba __Condições de Pagamentos__, clique no botão `+`.
-4. Selecione a condição de pagamento __Parcelex__.
-5. Ative a condição no campo __Status__.
-6. Clique em `Salvar`.
+
+1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Selecione a condição de pagamento __Parcelex__.
+4. Ative a condição no campo __Status__.
+5. Clique em `Salvar`.
 
 Depois de seguir os passos indicados, o conector Parcelex pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pay4fun.md b/docs/tutorials/pt/setting-up-payments-with-pay4fun.md
new file mode 100644
index 000000000..2d01fd677
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-pay4fun.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pagamento com Pay4Fun'
+id: 7xCpO35RMDRcp1UCvOGZX3
+status: PUBLISHED
+createdAt: 2024-02-05T14:53:57.694Z
+updatedAt: 2024-03-13T15:15:38.399Z
+publishedAt: 2024-03-13T15:15:38.399Z
+firstPublishedAt: 2024-02-05T15:29:05.357Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-pay4fun
+locale: pt
+legacySlug: configurar-pagamento-com-pay4fun
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Pay4Fun. Por meio deste provedor, sua loja pode realizar vendas por meio do PIX.
+
+Para configurar a Pay4Fun, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Pay4Fun__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Pay4Fun.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Pay4Fun na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __PIX__.
+4. Ative a condição no campo __Status__.
+5. Em __Processar com a afiliação__, selecione a opção __p4fpartnerbr-pay4fun-v0__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor Pay4Fun pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-paycash.md b/docs/tutorials/pt/setting-up-payments-with-paycash.md
index 82392f9d4..c101b5ae7 100644
--- a/docs/tutorials/pt/setting-up-payments-with-paycash.md
+++ b/docs/tutorials/pt/setting-up-payments-with-paycash.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Paycash'
 id: 5gxrb0YlEhq0JnprN2uaOf
 status: PUBLISHED
 createdAt: 2023-04-06T17:19:09.254Z
-updatedAt: 2023-04-06T17:57:16.146Z
-publishedAt: 2023-04-06T17:57:16.146Z
+updatedAt: 2024-01-23T21:05:57.921Z
+publishedAt: 2024-01-23T21:05:57.921Z
 firstPublishedAt: 2023-04-06T17:40:32.746Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-paycash
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Paycash. Com este conector, sua loja pode realizar vendas por meio do Paycash.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Paycash. Por meio deste provedor, sua loja pode realizar vendas por meio do Paycash.
 
-Para configurar a afiliação Paycash, siga os passos abaixo:
+Para configurar Paycash, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Paycash__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Paycash__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__, __Application Token__ e __Paycash Production Api Key__ com as informações da sua conta Paycash.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-payclub.md b/docs/tutorials/pt/setting-up-payments-with-payclub.md
index 25e55057a..42a6b4d53 100644
--- a/docs/tutorials/pt/setting-up-payments-with-payclub.md
+++ b/docs/tutorials/pt/setting-up-payments-with-payclub.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamentos com PayClub'
 id: 3C3bDia3Tyq48MOuMomcUW
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-03T13:12:17.337Z
-updatedAt: 2023-03-28T00:07:06.076Z
-publishedAt: 2023-03-28T00:07:06.076Z
+updatedAt: 2024-03-18T19:14:09.539Z
+publishedAt: 
 firstPublishedAt: 2018-04-03T15:07:32.416Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagamentos-com-payclub
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Você pode configurar o [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) PayClub para receber pagamentos na sua loja. Nesta modalidade, seu cliente escolhe o __meio de pagamento__ PayClub e realiza a autenticação no ambiente externo da solução de pagamentos.
 
 Para habilitar pagamentos com PayClub, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-payments-with-paymentezv2.md b/docs/tutorials/pt/setting-up-payments-with-paymentezv2.md
new file mode 100644
index 000000000..dbc162cd0
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-paymentezv2.md
@@ -0,0 +1,34 @@
+---
+title: 'Configurar pagamento com PaymentezV2'
+id: 6MQiFTLnSaQoCswRUN1SVe
+status: PUBLISHED
+createdAt: 2024-03-14T12:48:31.013Z
+updatedAt: 2024-03-14T13:10:44.458Z
+publishedAt: 2024-03-14T13:10:44.458Z
+firstPublishedAt: 2024-03-14T13:10:44.458Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-paymentezv2
+locale: pt
+legacySlug: configurar-pagamento-com-paymentezv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PaymentezV2. Por meio deste provedor, sua loja pode realizar vendas por TuyaPay, cartões de crédito, private label, co-branded e promissórias.
+
+Para configurar a PaymentezV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PaymentezV2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PaymentezV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PaymentezV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela PaymentezV2, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PaymentezV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-paypalv2.md b/docs/tutorials/pt/setting-up-payments-with-paypalv2.md
new file mode 100644
index 000000000..5d9fe4618
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-paypalv2.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurar pagamento com PayPalV2'
+id: 2nGiQVk3YKvOAu8Zg4RKFr
+status: PUBLISHED
+createdAt: 2024-03-14T18:53:09.449Z
+updatedAt: 2024-07-24T19:40:23.978Z
+publishedAt: 2024-07-24T19:40:23.978Z
+firstPublishedAt: 2024-03-14T19:02:53.958Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-paypalv2
+locale: pt
+legacySlug: configurar-pagamento-com-paypalv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PayPalV2. Por meio deste provedor, sua loja pode realizar vendas por meio de PayPalCP e PayPal.
+
+Para configurar o PayPalV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __paypal-v2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PayPalV2. No ambiente Paypal, o __App Key__ corresponde ao __Client ID__, e o __App token__ refere-se ao __Secret__.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PayPalV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Clique em __Salvar__.
+
+Para configurar os métodos de pagamento a serem processados pela PayPalV2, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, PayPalV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-payu-india.md b/docs/tutorials/pt/setting-up-payments-with-payu-india.md
index 87bcd031c..6e3839723 100644
--- a/docs/tutorials/pt/setting-up-payments-with-payu-india.md
+++ b/docs/tutorials/pt/setting-up-payments-with-payu-india.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamento com PayU India'
 id: 7JFaP3jBukdZHWel9p7dKX
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-08-15T12:33:46.519Z
-updatedAt: 2023-03-21T20:56:57.589Z
-publishedAt: 2023-03-21T20:56:44.797Z
+updatedAt: 2024-01-25T19:21:08.479Z
+publishedAt: 2024-01-25T19:21:08.479Z
 firstPublishedAt: 2022-08-15T14:38:06.151Z
 contentType: tutorial
 productTeam: Financial
@@ -15,18 +15,18 @@ legacySlug: configurar-pagamento-com-payu-india
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos PayU India. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito e promissórias.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos PayU India. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito e promissórias.
 
-Para configurar a afiliação PayU India, siga os passos abaixo:
+Para configurar PayU India, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PayuIndia__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PayuIndia__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__, __Application Token__, __Public API Key__, __Soft descriptor__ e __Type of refund__ com as informações da sua conta PayU India.
 5. No campo __Early capture__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude). Você também pode desativar a função.
 6. Em __Have an anti-fraud deal with this affiliation?__, selecione se a sua loja usará um antifraude com este conector.
-7. Clique em __Salvar__.
+7. Clique em `Salvar`.
 
 Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#). 
 
-Depois de seguir os passos indicados, o conector PayU India pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, PayU India pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-payuv2.md b/docs/tutorials/pt/setting-up-payments-with-payuv2.md
new file mode 100644
index 000000000..41b203629
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-payuv2.md
@@ -0,0 +1,48 @@
+---
+title: 'Configurar pagamento com PayUv2'
+id: 7twMgKUZZtJGmR72wS1k3n
+status: PUBLISHED
+createdAt: 2024-03-08T18:30:40.587Z
+updatedAt: 2024-03-13T15:35:06.533Z
+publishedAt: 2024-03-13T15:35:06.533Z
+firstPublishedAt: 2024-03-08T18:47:05.125Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-payuv2
+locale: pt
+legacySlug: configurar-pagamento-com-payuv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PayUv2. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito, private label, co-branded, promissórias e boleto bancário. 
+
+Para configurar o PayUv2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PayUv2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PayUv2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PayUv2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Caso deseje utilizar o [split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) em sua loja, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
+9. Em __Campos do provedor__, no campo __Tipo Autorizacion__, selecione se suas transações de pagamento são executadas em fluxos de uma ou duas etapas. Para fluxos de uma etapa, selecione __Autorizacion y Captura__. Para fluxos de duas etapas, selecione __Pre-Autorizacion__.
+10. Em __Public Key__, informe a sua chave API da PayU.
+11. Em __Idioma__, selecione qual linguagem deve ser utilizada no sistema da PayU.
+12. Em __Expiración pago (días)__, selecione o período em que deseja configurar o vencimento de pagamentos realizados por promissórias.
+13. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela PayUv2, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o provedor PayUv2 pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-payway.md b/docs/tutorials/pt/setting-up-payments-with-payway.md
new file mode 100644
index 000000000..69f2b119b
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-payway.md
@@ -0,0 +1,37 @@
+---
+title: 'Configurar pagamento com Payway'
+id: wHkvX7olfPPsAdeFq7obp
+status: PUBLISHED
+createdAt: 2024-03-07T17:04:59.563Z
+updatedAt: 2024-03-13T15:29:48.955Z
+publishedAt: 2024-03-13T15:29:48.955Z
+firstPublishedAt: 2024-03-07T19:10:55.092Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-payway
+locale: pt
+legacySlug: configurar-pagamento-com-payway
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Payway. Por meio deste provedor, sua loja pode realizar vendas por meio de PayWay, cartões de crédito, débito, private label, co-branded, promissórias e boleto bancário. 
+
+Para configurar o Payway, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Payway__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Payway.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Payway na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Campos do provedor__, insira as informações do __User ID__, __Consume Username (PUBLIC)__ e __Consume Username (PRIVATE)__ conforme as informações da sua conta Payway.
+8. Em __Payment type__, selecione a opção __Simple Payment__ ou __Two Steps Payment__.
+9. Em __Do you use Cybersource?__, selecione se deseja utilizar a Cybersource como provedor de antifraude.
+10. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Worldpay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o provedor Payway pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-picpay.md b/docs/tutorials/pt/setting-up-payments-with-picpay.md
index 98a345c3a..aa9097060 100644
--- a/docs/tutorials/pt/setting-up-payments-with-picpay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-picpay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com PicPay'
 id: 5jd6wgPCaWm8IcguyCyaY2
 status: PUBLISHED
 createdAt: 2018-03-13T15:53:25.279Z
-updatedAt: 2023-03-29T01:02:29.955Z
-publishedAt: 2023-03-29T01:02:29.955Z
+updatedAt: 2024-01-23T21:16:28.952Z
+publishedAt: 2024-01-23T21:16:28.952Z
 firstPublishedAt: 2018-03-13T19:36:37.769Z
 contentType: tutorial
 productTeam: Financial
@@ -17,16 +17,16 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 O PicPay é uma [carteira digital](/pt/faq/o-que-e-uma-carteira-digital-e-wallet) que permite a transferência de valores entre usuários, incluindo estabelecimentos comerciais. Seu cliente escolhe pagar com ela e recebe um código para escanear usando o aplicativo para smartphones.
 
-Para configurar pagamentos com essa carteira digital, você primeiro precisa cadastrar a afiliação de gateway __PicPay__ seguindo os passos abaixo:
+Para configurar PicPay, siga os passos abaixo:
 
-## Configurar afiliação de gateway PicPay
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PicPay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PicPay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos _Application Key_ e _Application Token_ com as informações da sua conta __PicPay__.
-5. Clique em __Salvar__.
+5. Clique em `Salvar`.
 
 ## Configurar condição de pagamento PicPay
+
 1. Já dentro das __Configurações__ do módulo Pagamentos, clique na aba __Condições de pagamento__.
 2. Clique no botão __+__.
 3. Selecione o meio de pagamento __PicPay__.
diff --git a/docs/tutorials/pt/setting-up-payments-with-pine-labs.md b/docs/tutorials/pt/setting-up-payments-with-pine-labs.md
index 312abdc9a..0dc0dc90c 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pine-labs.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pine-labs.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Pine Labs'
 id: 6cmZ0Qs9HUpN7AUBZQDmc0
 status: PUBLISHED
 createdAt: 2023-04-03T17:01:53.868Z
-updatedAt: 2023-04-14T12:48:59.843Z
-publishedAt: 2023-04-14T12:48:59.843Z
+updatedAt: 2024-01-25T19:11:09.123Z
+publishedAt: 2024-01-25T19:11:09.123Z
 firstPublishedAt: 2023-04-03T17:17:06.240Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-pine-labs
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Pine Labs. Por meio deste conector, sua loja pode realizar vendas por meio de cartões de crédito, boleto bancário e promissórias.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Pine Labs. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, boleto bancário e promissórias.
 
-Para configurar a afiliação Pine Labs, siga os passos abaixo:
+Para configurar Pine Labs, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Pinelabs connector__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Pinelabs connector__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Pine Labs.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
@@ -30,4 +30,4 @@ Para configurar os métodos de pagamento a serem processados pela Pine Labs, ace
 
 Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Depois de seguir os passos indicados, o conector Pine Labs pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Pine Labs pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-poolpay.md b/docs/tutorials/pt/setting-up-payments-with-poolpay.md
new file mode 100644
index 000000000..997ccb424
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-poolpay.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pagamento com PoolPay'
+id: 5N3llK2tpVPKdfJvOIJmQ0
+status: PUBLISHED
+createdAt: 2023-09-11T14:36:06.412Z
+updatedAt: 2024-01-25T17:26:19.086Z
+publishedAt: 2024-01-25T17:26:19.086Z
+firstPublishedAt: 2023-09-11T14:58:37.086Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-poolpay
+locale: pt
+legacySlug: configurar-pagamento-com-poolpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento PoolPay. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, PIX, ITP (Iniciador de transação de pagamento) e BNPL (Buy Now Pay Later).
+
+Para configurar PoolPay, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PoolPay__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__ e __Application Token__, insira as informações que foram fornecidas pela PoolPay.
+5. Em __Ativar divisão e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+6. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela PoolPay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector PoolPay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-powerpay.md b/docs/tutorials/pt/setting-up-payments-with-powerpay.md
new file mode 100644
index 000000000..5b4defbfa
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-powerpay.md
@@ -0,0 +1,50 @@
+---
+title: 'Configurar pagamento com Powerpay'
+id: 4v3ohBfSTxIyi06aqvlrPp
+status: PUBLISHED
+createdAt: 2023-09-08T18:31:43.851Z
+updatedAt: 2024-01-23T21:22:03.339Z
+publishedAt: 2024-01-23T21:22:03.339Z
+firstPublishedAt: 2023-09-08T19:50:37.486Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-powerpay
+locale: pt
+legacySlug: configurar-pagamento-com-powerpay
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Powerpay. Por meio deste provedor, sua loja pode realizar vendas por meio do Powerpay.
+
+Para configurar Powerpay, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Powerpay__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__, __Application Token__, __secretKey__ e __merchant_id__ insira as informações que foram fornecidas pela Powerpay.
+5. No campo __Captura automática de pagamento__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Use o comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Imediatamente: captura automática ao autorizar o pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Imediatamente: captura automática ao passar a análise de risco de fraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Imediatamente: Captura Automática Ao Autorizar O Pagamento").</li>
+   		<li><b>Agendada: defina quando a captura automática será realizada</b>: ao selecionar esta opção, o campo <b>Prazo agendado em horas para a captura automática</b> estará disponível, e deve ser preenchido com o período no qual a captura automática acontecerá. Este período deve estar em acordo com os limites permitidos pelo provedor de pagamento.</li>        
+   		<li><b>Desativado: não capturado automaticamente</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+6. Em __Ativar divisão e enviar recebedores?__, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.
+
+7. Clique em __Salvar__.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja__ > __Pagamentos__ > __Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão __+__.
+3. Selecione a condição de pagamento __Powerpay__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
+7. Clique em __Salvar__.
+
+Depois de seguir os passos indicados, o conector Powerpay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-puntos-colombia.md b/docs/tutorials/pt/setting-up-payments-with-puntos-colombia.md
index c98cd0f5d..d6ff661b7 100644
--- a/docs/tutorials/pt/setting-up-payments-with-puntos-colombia.md
+++ b/docs/tutorials/pt/setting-up-payments-with-puntos-colombia.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Puntos Colombia'
 id: 5lj66uK0w5XxfzfncEyhP6
 status: PUBLISHED
 createdAt: 2022-03-17T14:14:06.885Z
-updatedAt: 2023-03-26T21:55:55.409Z
-publishedAt: 2023-03-26T21:55:55.409Z
+updatedAt: 2024-01-25T17:08:21.898Z
+publishedAt: 2024-01-25T17:08:21.898Z
 firstPublishedAt: 2022-03-17T14:23:01.073Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-puntos-colombia
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Puntos Colombia. Com este conector, sua loja pode realizar vendas por meio do programa de fidelidade Puntos Colombia.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Puntos Colombia. Por meio deste provedor, sua loja pode realizar vendas por meio do programa de fidelidade Puntos Colombia.
 
-Para configurar a afiliação Puntos Colombia, siga os passos abaixo:
+Para configurar Puntos Colombia, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PuntosColombia__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PuntosColombia__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Puntos Colombia.
 5. Clique em __Salvar__.
 
@@ -36,4 +36,4 @@ Para configurar a afiliação Puntos Colombia, siga os passos abaixo:
 7. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete#).
 8. Clique em __Salvar__.
 
-Depois de seguir os passos indicados, o conector Puntos Colombia pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Puntos Colombia pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-qhantuy.md b/docs/tutorials/pt/setting-up-payments-with-qhantuy.md
index b9a2a8519..55b5fe557 100644
--- a/docs/tutorials/pt/setting-up-payments-with-qhantuy.md
+++ b/docs/tutorials/pt/setting-up-payments-with-qhantuy.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Qhantuy'
 id: 4KO2beK0scqVy4lrrs3Myq
 status: PUBLISHED
 createdAt: 2023-04-20T13:44:39.377Z
-updatedAt: 2023-04-20T17:36:03.040Z
-publishedAt: 2023-04-20T17:36:03.040Z
+updatedAt: 2024-01-24T17:10:50.292Z
+publishedAt: 2024-01-24T17:10:50.292Z
 firstPublishedAt: 2023-04-20T14:12:44.589Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-qhantuy
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Qhantuy. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito e Qhantuy.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Qhantuy. Com este provedor, sua loja pode realizar vendas por meio de cartões de crédito e Qhantuy.
 
-Para configurar a afiliação Qhantuy, siga os passos abaixo:
+Para configurar Qhantuy, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Qhantuy__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Qhantuy__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Qhantuy.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-retrypay.md b/docs/tutorials/pt/setting-up-payments-with-retrypay.md
index 39b068803..881e353a5 100644
--- a/docs/tutorials/pt/setting-up-payments-with-retrypay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-retrypay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Retrypay'
 id: 3QGioVKVI1Qnk3JbbJlJVY
 status: PUBLISHED
 createdAt: 2023-03-30T19:35:06.661Z
-updatedAt: 2023-03-30T20:01:51.283Z
-publishedAt: 2023-03-30T20:01:51.283Z
+updatedAt: 2024-02-08T14:23:02.038Z
+publishedAt: 2024-02-08T14:23:02.038Z
 firstPublishedAt: 2023-03-30T20:01:51.283Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-retrypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Retrypay. Com este conector, sua loja pode realizar vendas por meio de promissórias e do Retrypay.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Retrypay. Por meio deste provedor, sua loja pode realizar vendas por meio de promissórias e do Retrypay.
 
-Para configurar a afiliação Retrypay, siga os passos abaixo:
+Para configurar Retrypay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __RetryPay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __RetryPay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__, __Application Token__, __Tenant__, __Retripay Merchant API Key__ e __Retripay Hook Token__ com as informações da sua conta Retrypay.
 5. Em __Payment Method__, escolha uma das duas opções: __Redirect__ ou __Payment App__.
 6. Em __Environment__, escolha uma das duas opções: __Demo__ ou __Production__.
@@ -29,7 +29,7 @@ Para configurar a afiliação Retrypay, siga os passos abaixo:
 
 ## Configurar condição de pagamento Promissória
 
-Caso deseje utilizar o Retrypay com promissória e ainda não tenha configurado a promissória como método de pagamento em outros conectores de sua loja, acesse [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ).
+Caso deseje utilizar o Retrypay com promissória e ainda não tenha configurado a promissória como método de pagamento em outros provedores de sua loja, acesse [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria).
 
 Depois, siga os passos abaixo:
 
@@ -51,5 +51,5 @@ Depois, siga os passos abaixo:
 6. Se desejar, você também pode configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 7. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Retrypay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Retrypay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-safetypayv2.md b/docs/tutorials/pt/setting-up-payments-with-safetypayv2.md
new file mode 100644
index 000000000..62bd5a41a
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-safetypayv2.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pagamento com SafetyPayV2'
+id: 5VBwbJODDKJ6zIW5a23l8V
+status: PUBLISHED
+createdAt: 2024-03-14T17:24:16.678Z
+updatedAt: 2024-03-14T17:44:09.769Z
+publishedAt: 2024-03-14T17:44:09.769Z
+firstPublishedAt: 2024-03-14T17:41:17.188Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-safetypayv2
+locale: pt
+legacySlug: configurar-pagamento-com-safetypayv2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento SafetyPayV2. Por meio deste provedor, sua loja pode realizar vendas por Safetypay e Lotérica.
+
+Para configurar a SafetyPayV2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __SafetyPayV2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta SafetyPayV2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor SafetyPayV2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela SafetyPayV2, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, SafetyPayV2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-scalapay.md b/docs/tutorials/pt/setting-up-payments-with-scalapay.md
index 6d14b70ff..d634edf38 100644
--- a/docs/tutorials/pt/setting-up-payments-with-scalapay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-scalapay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Scalapay'
 id: 6SCh3WUqjeqIrOl209MENA
 status: PUBLISHED
 createdAt: 2022-08-12T19:31:38.569Z
-updatedAt: 2023-05-09T14:07:50.542Z
-publishedAt: 2023-05-09T14:07:50.542Z
+updatedAt: 2024-01-25T18:03:45.856Z
+publishedAt: 2024-01-25T18:03:45.856Z
 firstPublishedAt: 2022-08-12T19:39:58.598Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-pagamento-com-scalapay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Scalapay. Com este conector, sua loja pode realizar vendas por meio de cartão de crédito e Scalapay.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Scalapay. Por meio deste provedor, sua loja pode realizar vendas por meio de cartão de crédito e Scalapay.
 
-Para configurar a afiliação Scalapay, siga os passos abaixo:
+Para configurar Scalapay, siga os passos abaixo:
 
-<ui>1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.</ui>
+<ui>1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.</ui>
 
-<ui>2. Na aba __Afiliações de Gateways__, clique no botão __+__.</ui>
+<ui>2. Na tela de provedores, clique no botão `Novo provedor`.</ui>
 
-<ui>3. Clique no conector __Scalapay__.</ui>
+<ui>3. Digite o nome __Scalapay__ na barra de busca e clique sobre o nome do provedor.</ui>
 
 <ui>4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Scalapay.</ui>
 
@@ -34,8 +34,8 @@ Para configurar a afiliação Scalapay, siga os passos abaixo:
  - __Imediatamente: Captura Automática Ao Passar A Análise De Risco De Fraude__:  a captura é realizada automaticamente logo após a autorização  do pagamento e análise do antifraude. Se desejar utilizar esta opção e não existe análise do antifraude a ser realizada, o sistema irá seguir o mesmo fluxo da opção __Imediatamente: Captura Automática Ao Autorizar O Pagamento__.  
  - __Desativado: Não Capturado Automaticamente__: a captura ocorre apenas quando o pedido é faturado. Se desejar utilizar essa opção, é importante ficar atento ao momento do faturamento, pois caso o pedido seja faturado em um período de tempo maior que o acordado com o provedor para a captura do pagamento, a transação poderá ser cancelada.
 
-<ui>6.Clique em __Salvar__.</ui>
+<ui>6.Clique em `Salvar`.</ui>
 
 Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#). Para a opção de cartão de crédito, selecione a afiliação __vtex-integration-scalapay-v0__.
 
-Depois de seguir os passos indicados, o conector Scalapay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Scalapay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-shipay.md b/docs/tutorials/pt/setting-up-payments-with-shipay.md
index 910e30234..09ef28457 100644
--- a/docs/tutorials/pt/setting-up-payments-with-shipay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-shipay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Shipay'
 id: 2GVBCDdxZPexI2TikFf9Au
 status: PUBLISHED
 createdAt: 2023-03-27T14:40:05.161Z
-updatedAt: 2023-03-27T16:15:57.347Z
-publishedAt: 2023-03-27T16:15:57.347Z
+updatedAt: 2024-01-23T21:27:19.732Z
+publishedAt: 2024-01-23T21:27:19.732Z
 firstPublishedAt: 2023-03-27T14:44:22.502Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-shipay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Shipay. Por meio deste conector, sua loja pode realizar vendas pelo PIX.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Shipay. Por meio deste provedor, sua loja pode realizar vendas pelo PIX.
 
-Para configurar a afiliação Shipay, siga os passos abaixo:
+Para configurar Shipay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Shipay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Shipay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Shipay.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-sibs.md b/docs/tutorials/pt/setting-up-payments-with-sibs.md
index 6f9158419..2a9b1a27c 100644
--- a/docs/tutorials/pt/setting-up-payments-with-sibs.md
+++ b/docs/tutorials/pt/setting-up-payments-with-sibs.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com SIBS'
 id: sNLPtJlAMnDpq40CCPKNo
 status: PUBLISHED
 createdAt: 2023-04-06T18:57:27.591Z
-updatedAt: 2023-04-06T19:07:28.327Z
-publishedAt: 2023-04-06T19:07:28.327Z
+updatedAt: 2024-01-25T19:05:01.739Z
+publishedAt: 2024-01-25T19:05:01.739Z
 firstPublishedAt: 2023-04-06T19:07:28.327Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-sibs
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento SIBS. Com este conector, sua loja pode realizar vendas por meio de cartão de crédito SIBS, Promissórias, MBWay e MultiBanco.
+Na VTEX, é possível realizar a integração com o provedor de pagamento SIBS. Por meio deste provedor, sua loja pode realizar vendas por meio de cartão de crédito SIBS, Promissórias, MBWay e MultiBanco.
 
-Para configurar a afiliação SIBS, siga os passos abaixo:
+Para configurar SIBS, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __SIBS__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __SIBS__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta SIBS.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
@@ -38,5 +38,5 @@ Para configurar os métodos de pagamento a serem processados pela SIBS, acesse [
 
 Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Depois de seguir os passos indicados, o conector SIBS pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, SIBS pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-stark-bank.md b/docs/tutorials/pt/setting-up-payments-with-stark-bank.md
new file mode 100644
index 000000000..3680cdae7
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-stark-bank.md
@@ -0,0 +1,34 @@
+---
+title: 'Configurar pagamento com Stark Bank'
+id: 19pwHHVuEGN743WOGXcbUM
+status: PUBLISHED
+createdAt: 2023-09-08T15:29:02.297Z
+updatedAt: 2024-01-23T21:44:38.751Z
+publishedAt: 2024-01-23T21:44:38.751Z
+firstPublishedAt: 2023-09-08T15:45:11.373Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-stark-bank
+locale: pt
+legacySlug: configurar-pagamento-com-stark-bank
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Stark Bank. Por meio deste provedor, sua loja pode realizar vendas por meio de boleto bancário e PIX.
+
+Para configurar Stark Bank, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __StarkBank__ na barra de busca e clique sobre o nome do provedor.
+4. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão __Instalar app__ e siga as instruções de instalação.
+5. Clique em __Autorizar__. Você será redirecionado para o ambiente do Stark Bank.
+6. No ambiente do Stark Bank, insira os seus dados de login e senha da conta Stark Bank. Siga as instruções indicadas para concluir a vinculação da conta Stark Bank com a VTEX.
+7. Ao retornar ao __Admin VTEX__, clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Stark Bank, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o conector Stark Bank pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-stelo.md b/docs/tutorials/pt/setting-up-payments-with-stelo.md
index f6e44f28c..d275af05a 100644
--- a/docs/tutorials/pt/setting-up-payments-with-stelo.md
+++ b/docs/tutorials/pt/setting-up-payments-with-stelo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamentos com Stelo'
 id: 6c16nRhAGWaA2mSUOOuC00
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T20:20:44.376Z
-updatedAt: 2023-03-29T01:07:31.337Z
-publishedAt: 2023-03-29T01:07:31.337Z
+updatedAt: 2024-03-18T20:21:28.181Z
+publishedAt: 
 firstPublishedAt: 2018-03-05T19:08:32.807Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-pagamentos-com-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Além de um [subadquirente](/pt/tutorial/configurar-subadquirente-stelo) para processar transações realizadas com diversas condições de pagamento, a Stelo também oferece um serviço de [carteira digital](/pt/faq/o-que-e-uma-carteira-digital-e-wallet). Seu cliente escolhe pagar com ela e é redirecionado para autenticação no ambiente da Stelo.
 
 Para configurar pagamentos com a carteira digital Stelo na sua loja, você primeiro precisa cadastrar a afiliação de gateway __Stelo Redirect__.
diff --git a/docs/tutorials/pt/setting-up-payments-with-stelom1v2.md b/docs/tutorials/pt/setting-up-payments-with-stelom1v2.md
new file mode 100644
index 000000000..2e91ec77c
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-stelom1v2.md
@@ -0,0 +1,33 @@
+---
+title: 'Configurar pagamento com SteloM1V2'
+id: 1lO9Rn87U0iyBTCpgBlqYD
+status: PUBLISHED
+createdAt: 2024-03-14T13:56:38.010Z
+updatedAt: 2024-03-14T14:05:14.839Z
+publishedAt: 2024-03-14T14:05:14.839Z
+firstPublishedAt: 2024-03-14T14:05:14.839Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-stelom1v2
+locale: pt
+legacySlug: configurar-pagamento-com-stelom1v2
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento SteloM1V2. Por meio deste provedor, sua loja pode realizar vendas por cartões de crédito e boleto.
+
+Para configurar a SteloM1V2, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __SteloM1V2__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta SteloM1V2.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor SteloM1V2 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela SteloM1V2, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, SteloM1V2 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md b/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md
index 2ba0b519f..3abd072ae 100644
--- a/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md
+++ b/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamentos com Cartões de Loja (co-branded)'
 id: jrkLK41IjuquUmyKUi86Q
 status: PUBLISHED
 createdAt: 2018-06-25T15:48:13.031Z
-updatedAt: 2023-03-22T19:19:30.029Z
-publishedAt: 2023-03-22T19:19:30.029Z
+updatedAt: 2023-09-22T21:25:38.666Z
+publishedAt: 2023-09-22T21:25:38.666Z
 firstPublishedAt: 2018-06-27T20:17:05.882Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,10 +26,17 @@ A primeira estapa de configuração será a de criação do pagamento customizad
 4. Em __Nome__, preencha o nome do cartão.
 5. Em __Descrição__, escreva o texto que vai dar mais detalhes sobre a condição de pagamento.
 6. Em __Bandeira do cartão__, escolha a bandeira à qual o cartão da sua loja está vinculado. Atualmente, as bandeiras possíveis são: American Express, Cabal, Diners, Elo, Mastercard e Visa.
-7. Em __Faixas de Bin{min}-{max},{min}-{max},{bin1},{bin2} (opcional)__, informe os códigos BIN dos cartões para que eles sejam validados pelo sistema. Você pode inserir uma faixa de BINs (inserindo o primeiro e o último código da sequência, separados por hífen) ou várias (separando cada faixa por vírgula e sem espaços). Se preferir, você pode usar o validador do cartão co-branded, preenchendo os valores `100000-999999`.
-8. No campo __Código de Pagamento em Adquirente (opcional)__, indique o código para ser enviado e processado pelo adquirente contratado por você.
-9. Em __Ativar split de pagamento__, caso opte por utilizar essa opção, quando a venda envolver lojas de marketplace, os valores serão divididos entre os sellers e o marketplace.
-10. Clique em __Salvar__.
+7. Em __Intervalos de BIN (opcional)__, você pode informar uma faixa de BINs (inserindo o primeiro e o último código da sequência, separados por hífen) ou várias (separando cada faixa por vírgula e sem espaços).
+
+<div class="alert alert-warning">
+  Quando o cliente inserir um número bin fora da faixa especificada neste campo, a seguinte mensagem será exibida "Confira o número do seu cartão. Não conseguimos confirmar se o número digitado está correto". Caso não haja erro no número digitado, ele poderá clicar em "SIM, O NÚMERO ESTÁ CORRETO" para continuar a finalização do pedido.
+</div>
+
+<blockquote><ui>8. No campo <b>Código de Pagamento em Adquirente (opcional)</b>, indique o código para ser enviado e processado pelo adquirente contratado por você.</ui>
+
+<blockquote><ui>9. Em <b>Ativar divisão de pagamento</b>, caso opte por utilizar essa opção, quando a venda envolver lojas de marketplace, os valores serão divididos entre os sellers e o marketplace.</ui>
+
+<ui>10. Clique em <b>Salvar</b>.</ui>
 
 ## Configurar condição de pagamento
 Após configurar o cartão, será necessária a configuração da condição de pagamento.
diff --git a/docs/tutorials/pt/setting-up-payments-with-transfero-crypto-checkout.md b/docs/tutorials/pt/setting-up-payments-with-transfero-crypto-checkout.md
new file mode 100644
index 000000000..0a7be4953
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-transfero-crypto-checkout.md
@@ -0,0 +1,49 @@
+---
+title: 'Configurar pagamento com Transfero Crypto Checkout'
+id: 29ZW22EW09zQDWZlPdyZ1T
+status: PUBLISHED
+createdAt: 2024-04-17T18:14:15.873Z
+updatedAt: 2024-04-17T18:44:01.978Z
+publishedAt: 2024-04-17T18:44:01.978Z
+firstPublishedAt: 2024-04-17T18:44:01.978Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-transfero-crypto-checkout
+locale: pt
+legacySlug: configurar-pagamento-com-transfero-crypto-checkout
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o processador de pagamentos Transfero Crypto Checkout. Por meio dele, sua loja pode realizar vendas por meio de criptomoedas e PIX, e receber em [moeda Fiat](https://pt.wikipedia.org/wiki/Moeda_fiduci%C3%A1ria).
+
+Para configurar o Transfero Crypto Checkout, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __CryptoCheckout__ na barra de busca e clique sobre o nome do processador.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta [Transfero Crypto Checkout](https://onboarding.transfero.com/).
+5. Caso deseje modificar o nome de identificação a ser exibido para o processador de pagamentos Transfero Crypto Checkout na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o processador em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Transfero Checkout__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o processador Transfero Crypto Checkout pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-tyendacrypto.md b/docs/tutorials/pt/setting-up-payments-with-tyendacrypto.md
index 15aaa3865..2bf2a9990 100644
--- a/docs/tutorials/pt/setting-up-payments-with-tyendacrypto.md
+++ b/docs/tutorials/pt/setting-up-payments-with-tyendacrypto.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com TiendaCrypto'
 id: 7qC52v2j7q7B0YUtLnW2I9
 status: PUBLISHED
 createdAt: 2023-05-26T18:19:21.462Z
-updatedAt: 2023-05-26T22:40:14.439Z
-publishedAt: 2023-05-26T22:40:14.439Z
+updatedAt: 2024-01-24T13:32:40.359Z
+publishedAt: 2024-01-24T13:32:40.359Z
 firstPublishedAt: 2023-05-26T18:43:41.573Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-tyendacrypto
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento TiendaCrypto. Com este conector, sua loja pode realizar vendas por meio do criptomoedas.
+Na VTEX, é possível realizar a integração com o provedor de pagamento TiendaCrypto. Por meio deste provedor, sua loja pode realizar vendas por meio do criptomoedas.
 
-Para configurar a afiliação TiendaCrypto, siga os passos abaixo:
+Para configurar TiendaCrypto, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __TiendaCrypto__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __TiendaCrypto__ na barra de busca e clique sobre o nome do provedor.
 4. Clique em __Autorizar__. Você será redirecionado para o ambiente do TiendaCrypto.
 5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-unlimit.md b/docs/tutorials/pt/setting-up-payments-with-unlimit.md
new file mode 100644
index 000000000..c1fbc33fd
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-unlimit.md
@@ -0,0 +1,43 @@
+---
+title: 'Configurar pagamento com Unlimit'
+id: 5emdjkgQOEQruDinUrfXY8
+status: PUBLISHED
+createdAt: 2024-06-05T15:41:23.584Z
+updatedAt: 2024-07-29T15:08:14.122Z
+publishedAt: 2024-07-29T15:08:14.122Z
+firstPublishedAt: 2024-06-06T15:38:46.103Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-unlimit
+locale: pt
+legacySlug: configurar-pagamento-com-unlimit
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Unlimit. Por meio deste provedor, sua loja pode realizar vendas utilizando diversos meios de pagamento, como: cartões de crédito, débito, private label, co-branded, boleto bancário e PIX. 
+
+Para configurar o Unlimit, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Unlimit__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Unlimit.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Unlimit na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Clique em `Salvar`.
+
+Para configurar os métodos de pagamento a serem processados pela Unlimit, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, o provedor Unlimit pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-ventipay.md b/docs/tutorials/pt/setting-up-payments-with-ventipay.md
index 948f8543f..dc6fc5e00 100644
--- a/docs/tutorials/pt/setting-up-payments-with-ventipay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-ventipay.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com VentiPay'
 id: 11n076tXgeLa1wDT3n2hyZ
 status: PUBLISHED
 createdAt: 2022-10-18T18:04:20.082Z
-updatedAt: 2023-03-21T20:49:01.107Z
-publishedAt: 2023-03-21T20:49:01.107Z
+updatedAt: 2024-01-24T18:08:16.663Z
+publishedAt: 2024-01-24T18:08:16.663Z
 firstPublishedAt: 2022-10-18T18:28:35.755Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-ventipay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway VentiPay. Com este conector, sua loja pode realizar vendas por meio da VentiPay.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos VentiPay. Por meio deste provedor, sua loja pode realizar vendas por meio da VentiPay.
 
-Para configurar a afiliação VentiPay, siga os passos abaixo:
+Para configurar VentiPay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Ventipay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Ventipay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta VentiPay.
 5. Clique em `Salvar`.
 
@@ -33,5 +33,5 @@ Para configurar a afiliação VentiPay, siga os passos abaixo:
 4. Ative a condição no campo __Status__.
 5. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector VentiPay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, VentiPay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-virtuspay.md b/docs/tutorials/pt/setting-up-payments-with-virtuspay.md
index 7b126bec9..e16848d3c 100644
--- a/docs/tutorials/pt/setting-up-payments-with-virtuspay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-virtuspay.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar pagamento com VirtusPay'
 id: 2Agqwp19cwyIbxuHErVG8I
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-08-11T15:02:59.728Z
-updatedAt: 2023-03-27T12:42:29.231Z
-publishedAt: 2023-03-26T21:15:04.050Z
+updatedAt: 2024-01-23T21:50:25.883Z
+publishedAt: 2024-01-23T21:50:25.883Z
 firstPublishedAt: 2022-08-11T16:38:04.718Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-virtuspay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o gateway VirtusPay. Com este conector, sua loja pode realizar vendas parceladas e sem cartão por meio da VirtusPay.
+Na VTEX, é possível realizar a integração com o gateway VirtusPay. Com esta integração, sua loja pode realizar vendas parceladas e sem cartão por meio da VirtusPay.
 
-Para configurar a afiliação VirtusPay, siga os passos abaixo:
+Para configurar VirtusPay, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __VirtusPay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __VirtusPay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta VirtusPay.
 5. Clique em `Salvar`.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-virtuspayv2.md b/docs/tutorials/pt/setting-up-payments-with-virtuspayv2.md
index acb28e20c..5145a7d4e 100644
--- a/docs/tutorials/pt/setting-up-payments-with-virtuspayv2.md
+++ b/docs/tutorials/pt/setting-up-payments-with-virtuspayv2.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com VirtusPayV2'
 id: 1tbcLRNIB5Bz0oWl8LnayB
 status: PUBLISHED
 createdAt: 2023-03-27T12:14:53.392Z
-updatedAt: 2023-03-27T12:56:49.578Z
-publishedAt: 2023-03-27T12:56:49.578Z
+updatedAt: 2024-01-23T21:52:05.259Z
+publishedAt: 2024-01-23T21:52:05.259Z
 firstPublishedAt: 2023-03-27T12:56:49.578Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-virtuspayv2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento VirtusPayV2. Por meio deste conector, sua loja pode realizar vendas por meio do VirtusPay e VirtusPay Transparente.
+Na VTEX, é possível realizar a integração com o provedor de pagamento VirtusPayV2. Por meio deste provedor, sua loja pode realizar vendas por meio do VirtusPay e VirtusPay Transparente.
 
-Para configurar a afiliação VirtusPayV2, siga os passos abaixo:
+Para configurar VirtusPayV2, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __VirtusPayV2__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __VirtusPayV2__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta VirtusPay.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-webpayoneclick.md b/docs/tutorials/pt/setting-up-payments-with-webpayoneclick.md
new file mode 100644
index 000000000..3b2cfb62e
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-webpayoneclick.md
@@ -0,0 +1,39 @@
+---
+title: 'Configurar pagamento com WebpayOneClick'
+id: 7jIwDOcBbF3cxIyHKaj4LF
+status: PUBLISHED
+createdAt: 2024-03-07T14:01:33.652Z
+updatedAt: 2024-03-07T15:06:06.370Z
+publishedAt: 2024-03-07T15:06:06.370Z
+firstPublishedAt: 2024-03-07T15:06:06.370Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-webpayoneclick
+locale: pt
+legacySlug: configurar-pagamento-com-webpayoneclick
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento WebpayOneClick. Por meio deste provedor, sua loja pode realizar vendas por meio do Transbank Oneclick.
+
+Para configurar o WebpayOneClick, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __WebpayOneClick__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta WebpayOneClick.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor WebpayOneClick na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Transbank Oneclick__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor WebpayOneClick pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-wepay4u.md b/docs/tutorials/pt/setting-up-payments-with-wepay4u.md
new file mode 100644
index 000000000..1e04cf89a
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-wepay4u.md
@@ -0,0 +1,52 @@
+---
+title: 'Configurar pagamento com Wepay4u'
+id: 7xbyIPpU7PAXQNCfpVBqGC
+status: PUBLISHED
+createdAt: 2024-02-05T20:19:10.668Z
+updatedAt: 2024-03-13T15:09:57.098Z
+publishedAt: 2024-03-13T15:09:57.098Z
+firstPublishedAt: 2024-02-05T20:29:59.689Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-wepay4u
+locale: pt
+legacySlug: configurar-pagamento-com-wepay4u
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Wepay4u. Por meio deste provedor, sua loja pode realizar vendas por meio do Wepay4u.
+
+Para configurar o Wepay4u, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Wepay4u__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Wepay4u.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Wepay4u na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Em __Campos do provedor__, insira as informações do __MerchantCode__ e __SecretKey__ conforme as informações da sua conta Wepay4u.
+
+9. Em __Currency__, selecione a moeda a ser utilizada na transação de pagamento.
+
+10. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Wepay4u__.
+4. Ative a condição no campo __Status__.
+5. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+6. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o provedor Wepay4u pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-wompi.md b/docs/tutorials/pt/setting-up-payments-with-wompi.md
index 47be050ef..305c14973 100644
--- a/docs/tutorials/pt/setting-up-payments-with-wompi.md
+++ b/docs/tutorials/pt/setting-up-payments-with-wompi.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Wompi'
 id: 40d6lWEyzLViHS7aYvcsqV
 status: PUBLISHED
 createdAt: 2022-02-21T18:22:13.804Z
-updatedAt: 2023-03-26T22:00:59.701Z
-publishedAt: 2023-03-26T22:00:59.701Z
+updatedAt: 2024-01-24T13:49:31.304Z
+publishedAt: 2024-01-24T13:49:31.304Z
 firstPublishedAt: 2022-02-21T19:06:12.105Z
 contentType: tutorial
 productTeam: Financial
@@ -15,16 +15,16 @@ legacySlug: configurar-pagamento-com-wompi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Wompi. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito, débito, transações bancárias, Nequi e PSE (sistemas de pagamentos colombianos) e correspondentes bancários.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Wompi. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito, transações bancárias, Nequi e PSE (sistemas de pagamentos colombianos) e correspondentes bancários.
 
-Para configurar a afiliação Wompi, siga os passos abaixo:
+Para configurar a Wompi, siga os passos abaixo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Afiliações de Gateways__, clique no botão __+__.
 3. Clique no conector __WompiCo__.
 4. Clique em __Autorizar__. Você será redirecionado para o ambiente do Wompi.
 5. No ambiente do Wompi, insira os seus dados de login e senha da conta Wompi e clique em __Vincular cuenta__. Siga as instruções indicadas para concluir a vinculação da conta Wompi com a VTEX.
-6. Ao retornar ao Admin VTEX, clique em __Salvar__.
+6. Ao retornar ao Admin VTEX, clique em `Salvar`.
 
 ## Configurar condição de pagamento
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-wompicov2.md b/docs/tutorials/pt/setting-up-payments-with-wompicov2.md
index 4e8e12c93..e69f2c9fc 100644
--- a/docs/tutorials/pt/setting-up-payments-with-wompicov2.md
+++ b/docs/tutorials/pt/setting-up-payments-with-wompicov2.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com WompiCoV2'
 id: SnkXNUXkESqKxfFZu0LS4
 status: PUBLISHED
 createdAt: 2023-04-14T13:55:18.776Z
-updatedAt: 2023-04-14T14:23:30.858Z
-publishedAt: 2023-04-14T14:23:30.858Z
+updatedAt: 2024-01-24T13:54:46.662Z
+publishedAt: 2024-01-24T13:54:46.662Z
 firstPublishedAt: 2023-04-14T14:23:30.858Z
 contentType: tutorial
 productTeam: Financial
@@ -15,9 +15,9 @@ legacySlug: configurar-pagamento-com-wompicov2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento WompiCoV2. Por meio deste conector, sua loja pode realizar vendas por meio de cartões de crédito e débito.
+Na VTEX, é possível realizar a integração com o provedor de pagamento WompiCoV2. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito e débito.
 
-Para configurar a afiliação WompiCoV2, siga os passos abaixo:
+Para configurar WompiCoV2, siga os passos abaixo:
 
 1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
 2. Na aba __Afiliações de Gateways__, clique no botão `+`.
diff --git a/docs/tutorials/pt/setting-up-payments-with-woovi.md b/docs/tutorials/pt/setting-up-payments-with-woovi.md
new file mode 100644
index 000000000..d041676bb
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-payments-with-woovi.md
@@ -0,0 +1,40 @@
+---
+title: 'Configurar pagamento com Woovi'
+id: a61xxlOLJTQRrPx2MrVfs
+status: PUBLISHED
+createdAt: 2023-09-08T17:29:33.321Z
+updatedAt: 2024-01-23T21:54:32.467Z
+publishedAt: 2024-01-23T21:54:32.467Z
+firstPublishedAt: 2023-09-08T17:49:01.961Z
+contentType: tutorial
+productTeam: Financial
+author: 6DODK49lJPk3yvcoe6GB6g
+slug: configurar-pagamento-com-woovi
+locale: pt
+legacySlug: configurar-pagamento-com-woovi
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+Na VTEX, é possível realizar a integração com o provedor de pagamento Woovi. Por meio deste provedor, sua loja pode realizar vendas por meio do Woovi e Woovi Parcelado.
+
+Para configurar Woovi, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __WooviConnector__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__, __Application Token__ e __App ID__ com as informações da sua conta Woovi.
+5. Em __Method__, selecione __Pix__ ou __Woovi Parcelado__.
+6. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
+7. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __Woovi__ ou __Woovi Parcelado__.
+4. Ative a condição no campo __Status__.
+5. Se desejar utilizar um sistema antifraude, selecione a opção __Usar solução antifraude__.
+6. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
+7. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o conector Woovi pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-yuno.md b/docs/tutorials/pt/setting-up-payments-with-yuno.md
index 95b4664db..f92d2ae00 100644
--- a/docs/tutorials/pt/setting-up-payments-with-yuno.md
+++ b/docs/tutorials/pt/setting-up-payments-with-yuno.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Yuno'
 id: h7PS0vDJJokqI9axZPNzE
 status: PUBLISHED
 createdAt: 2023-04-14T12:42:43.736Z
-updatedAt: 2023-04-14T13:21:45.782Z
-publishedAt: 2023-04-14T13:21:45.782Z
+updatedAt: 2024-01-23T21:56:16.050Z
+publishedAt: 2024-01-23T21:56:16.050Z
 firstPublishedAt: 2023-04-14T13:21:45.782Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-yuno
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Yuno. Por meio deste conector, sua loja pode realizar vendas por meio de cartões de crédito, boleto bancário e promissórias.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Yuno. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, boleto bancário e promissórias.
 
-Para configurar a afiliação Yuno, siga os passos abaixo:
+Para configurar Yuno, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Yuno__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Yuno__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__, __Application Token__ e __Account ID__ com as informações da sua conta Yuno.
 5. Em __Auto Capture__, selecione se a captura do pagamento será automática após a autorização.
 6. Em __Delay To Capture (in days) Default 1 day, max 7 days__, preencha o período (em dias) no qual a captura do pagamento deverá aguardar para ser realizada. O valor padrão é 1 dia e o máximo é de 7 dias.
diff --git a/docs/tutorials/pt/setting-up-payments-with-zenki.md b/docs/tutorials/pt/setting-up-payments-with-zenki.md
index 300b04520..5f5fa04dc 100644
--- a/docs/tutorials/pt/setting-up-payments-with-zenki.md
+++ b/docs/tutorials/pt/setting-up-payments-with-zenki.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Zenki'
 id: 6LK7wMg0OB39UQKoZILoNL
 status: PUBLISHED
 createdAt: 2023-03-30T17:34:01.758Z
-updatedAt: 2023-03-30T18:04:59.870Z
-publishedAt: 2023-03-30T18:04:59.870Z
+updatedAt: 2024-01-25T18:50:47.590Z
+publishedAt: 2024-01-25T18:50:47.590Z
 firstPublishedAt: 2023-03-30T18:02:25.796Z
 contentType: tutorial
 productTeam: Financial
@@ -15,13 +15,13 @@ legacySlug: configurar-pagamento-com-zenki
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamento Zenki. Por meio deste conector, sua loja pode realizar vendas por meio de bitcoins.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Zenki. Por meio deste provedor, sua loja pode realizar vendas por meio de bitcoins.
 
-Para configurar a afiliação Zenki, siga os passos abaixo:
+Para configurar Zenki, siga os passos abaixo:
 
-1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão `+`.
-3. Clique no conector __Zenki__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Zenki__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos __Application Key__, __Application Token__, __API key__, __Secret Key__ e __Webhook signing secret__ com as informações da sua conta Zenki.
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 6. Clique em `Salvar`.
@@ -37,4 +37,4 @@ Para configurar a afiliação Zenki, siga os passos abaixo:
 7. Se desejar, você também pode [configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456).
 8. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o conector Zenki pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
+Depois de seguir os passos indicados, Zenki pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-payments-with-zoop.md b/docs/tutorials/pt/setting-up-payments-with-zoop.md
index fda0cebc9..ce11eef0e 100644
--- a/docs/tutorials/pt/setting-up-payments-with-zoop.md
+++ b/docs/tutorials/pt/setting-up-payments-with-zoop.md
@@ -3,8 +3,8 @@ title: 'Configurar pagamento com Zoop'
 id: 5bRYiUjX1sewZuON8HA6Ld
 status: PUBLISHED
 createdAt: 2023-02-13T18:17:14.240Z
-updatedAt: 2023-02-13T18:57:07.275Z
-publishedAt: 2023-02-13T18:57:07.275Z
+updatedAt: 2024-01-23T21:58:29.652Z
+publishedAt: 2024-01-23T21:58:29.652Z
 firstPublishedAt: 2023-02-13T18:50:09.746Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,24 @@ legacySlug: configurar-pagamento-com-zoop
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível realizar a integração com o provedor de pagamentos Zoop. Com este conector, sua loja pode realizar vendas por meio de cartões de crédito e boletos.
+Na VTEX, é possível realizar a integração com o provedor de pagamentos Zoop. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito e boletos.
 
-Para configurar a afiliação Zoop, siga os passos abaixo:
+Para configurar Zoop, siga os passos abaixo:
 
-1. Acesse o __Admin__ VTEX.
-2. Clique em __Pagamentos__.
-3. Em seguida, clique em __Configurações__.
-4. Na aba __Afiliações de Gateways__, clique no botão `+`.
-5. Clique no conector __Zoop__.
-6. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Zoop.
-7. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Zoop__ na barra de busca e clique sobre o nome do provedor.
+4. Preencha os campos __Application Key__ e __Application Token__ com as informações da sua conta Zoop.
+5. Em __Captura Automática de Pagamento__, selecione uma das opções disponíveis:
 
     - __Use O Comportamento Recomendado Pelo Processador de Pagamentos__: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).
     - __Imediatamente: Captura Automática Ao Autorizar O Pagamento__: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.
     - __Imediatamente: Captura Automática Ao Passar A Análise De Risco De Fraude__: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento – *Imediatamente: Captura Automática Ao Autorizar O Pagamento*.
     - __Desativado: Não Capturado Automaticamente__: a captura não é autorizada automaticamente. É importante atentar-se ao escolher esse comportamento, pois a demora no faturamento pode extrapolar o tempo de captura acordado com o provedor e levar à perda do pagamento.
 
-<ui>  8. Em <b>Ativar divisão e enviar recebedores?</b>, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.</ui>
+<ui>  6. Em <b>Ativar divisão e enviar recebedores?</b>, selecione se o split de pagamentos estará disponível para o marketplace e os sellers.</ui>
 
-<ui>  9. Clique em <b>Salvar.</b></ui>
+<ui>  7. Clique em <b>Salvar.</b></ui>
 
 Para configurar as condições de pagamento, acesse [Configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento#).
 
diff --git a/docs/tutorials/pt/setting-up-paypal-plus.md b/docs/tutorials/pt/setting-up-paypal-plus.md
index ef3dbb991..645486355 100644
--- a/docs/tutorials/pt/setting-up-paypal-plus.md
+++ b/docs/tutorials/pt/setting-up-paypal-plus.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar PayPal Plus (PayPal Transparente)'
 id: 2akxq3I92k8A4kymIYOiWy
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-20T20:15:36.950Z
-updatedAt: 2023-03-29T01:12:02.453Z
-publishedAt: 2023-03-29T01:12:02.453Z
+updatedAt: 2024-03-18T20:30:56.156Z
+publishedAt: 
 firstPublishedAt: 2018-02-20T22:56:13.192Z
 contentType: tutorial
 productTeam: Financial
@@ -15,38 +15,44 @@ legacySlug: configurar-paypal-plus-paypal-transparente
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-No gateway da VTEX, é possível configurar o subadquirente PayPal Plus, o checkout transparente da PayPal. Nesta modalidade, basta o cliente inserir as informações de __cartão de crédito__ e finalizar a compra normalmente. O pagamento é feito diretamente em seu site, sem redirecionar seus clientes. 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
+No gateway da VTEX, é possível configurar o subadquirente PayPal Plus, o checkout transparente da PayPal. Nesta modalidade, basta o cliente inserir as informações do cartão de crédito e finalizar a compra normalmente. O pagamento é feito diretamente em seu site, sem redirecionar seus clientes. 
 
 Para fazer as configurações, siga os passos abaixo:
 
-## Configurar afiliação de gateway PayPal Plus
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PayPalPlus__ na barra de busca e clique sobre o nome do provedor.
+4. Caso deseje modificar o nome de identificação a ser exibido para o PayPal Plus na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+5. Em __Controle de pagamento__, selecione se deseja ativar o PayPal Plus em ambiente de teste clicando em __Ativar modo de teste__.
+6. Preencha os campos abaixo conforme dados fornecidos pela PayPal:
+    - Em __ID do cliente__ insira o _clientId_.
+    - Em __Segredo__ insira o _secret_.
+    - Em __Nome do usuário__ insira o _userName_.
+    - Em __Senha__ insira o _password_.
+    - Em __Assinatura__ insira o _signature_.
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PayPal Plus__.
+<blockquote><ui>  7. Em <b>Salvar cartões</b>, selecione <b>Sim</b> para que o cliente possa selecionar a opção de salvar o cartão no momento do checkout. Caso não deseje habilitar esta opção, selecione <b>Não</b>.</ui>
 
-Preencha os campos de cadastro com os dados fornecidos pela PayPal, conforme abaixo.
-- O *clientId* deve ser inserido no campo __ID do cliente__.
-- O *secret* deve ser inserido no campo __Secret__.
-- O *userName* deve ser inserido no campo __Nome de usuário__.
-- A *password* deve ser inserida no campo __Senha__.
-- A *signature* deve ser inserida no campo __Assinatura__.
+<blockquote><ui>  8. Em <b>Moeda</b>, escolha a moeda da transação.</ui>
 
-Depois, siga estes passos:
-1. No campo __Lembrar cartões__,  selecione __Sim__ para que o cliente possa selecionar a opção de salvar o cartão no momento do checkout. Caso não deseje habilitar esta opção, selecione __Não__.
-2. Em __Moeda__, escolha a moeda da transação.
-3. Em __Local__, selecione o local da transação.  
-4. Clique em __Salvar__
+<blockquote><ui>  9. Em <b>Local de transação</b>, selecione o país da transação.</ui>
 
-## Configurar condição de pagamento PayPal Plus
+<blockquote><ui>  10. Em <b>Ativar API de risco (STC</b>, selecione a opção de acordo com as suas configurações na PayPal.</ui>
 
-1. Já dentro das __Configurações__ do módulo Pagamentos, clique na aba __Condições de pagamento__.
-2. Clique no botão __+__.
-3. Clique no meio de pagamento __PayPal Plus__.
-4. Clique no botão __Status__, para ativar esta condição de pagamento.
-5. Caso deseje, marque a caixa __Usar Antifraude__ para ativar o antifraude básico.
-6. Como o pagamento com PayPal Plus é um pagamento com cartão de crédito, vocês pode escolher [configurar a condição de pagamento à vista ou parcelado](/pt/tutorial/condicoes-de-pagamento).
-7. Caso queira, você também pode configurar [condições especiais de pagamento](/pt/tutorial/condicoes-especiais).
-8. Após realizar as configurações, clique em __Salvar__.
+<blockquote><ui>  11. Clique em <b>Salvar</b>.</ui>
+
+## Configurar condição de pagamento PayPal Plus
 
-Pronto! Agora será exibida no checkout a opção de pagamento por __cartão de crédito__ utilizando a [PayPal como subadquirente](/pt/tutorial/o-que-e-um-subadquirente).
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique em __PayPalPlus__.
+4. Preencha o campo __Nome da condição__ com um nome de sua preferência para identificação.
+5. Ative a condição no campo __Status__.
+6. Selecione se deseja utilizar um sistema antifraude selecionando a opção __Usar solução antifraude__.
+7. Indique se os pagamentos com cartão de crédito devem ser realizados [à vista ou parcelados (com e sem juros)](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455#a-vista).
+8. Se desejar, você também poderá configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
+9. Clique em `Salvar`.
+
+Depois de seguir os passos indicados, o PayPal Plus pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento.
diff --git a/docs/tutorials/pt/setting-up-payu-gateway.md b/docs/tutorials/pt/setting-up-payu-gateway.md
index 89fe93110..9e0b3698d 100644
--- a/docs/tutorials/pt/setting-up-payu-gateway.md
+++ b/docs/tutorials/pt/setting-up-payu-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway PayU'
 id: 36zWOAFHmwIAoWIEU2Y08q
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-27T15:25:04.654Z
-updatedAt: 2023-03-21T20:17:16.717Z
-publishedAt: 2023-03-21T20:17:16.717Z
+updatedAt: 2024-03-18T20:27:28.378Z
+publishedAt: 
 firstPublishedAt: 2018-03-27T22:13:40.899Z
 contentType: tutorial
 productTeam: Financial
@@ -15,14 +15,15 @@ legacySlug: configurar-gateway-payu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A PayU é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que oferece uma série de soluções para facilitar (e deixar mais seguras) as transações realizadas na sua loja. Com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc), essa solução é exclusiva para Argentina, Brasil, Chile, Colômbia, México, Panamá e Peru.
 
 Para configurar a PayU, siga os passos abaixo:
 
-## Configurar afiliação de gateway PayU
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __PayU__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PayU__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos de cadastro com os dados fornecidos pela PayU (campos _API Login_, _API Key_, _Account Id_ e _Merchant Id_).
 5. No campo __Forma de Autorização__, escolha o modo como quer autorizar as transações.
 6. Em __Moeda__, selecione a moeda que será usada nas transações.
diff --git a/docs/tutorials/pt/setting-up-payzen-gateway.md b/docs/tutorials/pt/setting-up-payzen-gateway.md
index d26e29304..9ec2feb44 100644
--- a/docs/tutorials/pt/setting-up-payzen-gateway.md
+++ b/docs/tutorials/pt/setting-up-payzen-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar o gateway PayZen'
 id: 3v3n5eQvxem8MQOCkugk24
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-13T19:39:04.093Z
-updatedAt: 2023-03-29T00:56:10.654Z
-publishedAt: 2023-03-29T00:56:10.654Z
+updatedAt: 2024-03-18T19:50:54.475Z
+publishedAt: 
 firstPublishedAt: 2018-03-13T22:27:11.198Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-o-gateway-payzen
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Na VTEX, você pode configurar o [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) PayZen na sua loja. De fácil integração, ele segue os padrões de segurança definidos pelo [Pagamentos](/pt/faq/o-que-e-o-pci-ssc).
 
 Para configurar o PayZen, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md b/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md
index dc8b32b9e..38b296041 100644
--- a/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md
+++ b/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md
@@ -21,18 +21,18 @@ Para acessá-la, siga os passos abaixo:
 
 1. Na topbar do Admin, no canto direito, clique no botão com a letra inicial do seu nome;
 2. Clique na opção __Configurações de usuário__.  
-![Opção Configurações de usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/44c8a24a6ac48c1aeedc6c8adba9f908/Op____o_Configura____es_de_usu__rio_User_Management_PT.png)
+![Opção Configurações de usuário User Management PT](//images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/44c8a24a6ac48c1aeedc6c8adba9f908/Op____o_Configura____es_de_usu__rio_User_Management_PT.png)
 
 Há duas opções no menu:
 
 - Em __Pessoal__ você pode ver seu nome, seu e-mail cadastrado no Admin e o número do seu telefone.  
-![Configuração Pessoal User Management PT](https://images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/0dec6b4bc84d23a354515d5e3b0af587/Configura____o_Pessoal_User_Management_PT.png)
+![Configuração Pessoal User Management PT](//images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/0dec6b4bc84d23a354515d5e3b0af587/Configura____o_Pessoal_User_Management_PT.png)
   - Ao clicar em __Nome__, você terá a opção de editar seu nome e sobrenome.  
-  ![Configuração Nome User Management PT](https://images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/5f20a76c8125496df3ae088cc96a26d5/Configura____o_Nome_User_Management_PT.png)
+  ![Configuração Nome User Management PT](//images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/5f20a76c8125496df3ae088cc96a26d5/Configura____o_Nome_User_Management_PT.png)
   - Ao clicar em __Número de celular__, você terá a opção de editar seu número de celular com o código do país.  
-  ![Configuração Celular User Management PT](https://images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/be07018ea8cb2d69ababafa7bf136c35/Configura____o_Celular_User_Management_PT.png)
+  ![Configuração Celular User Management PT](//images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/be07018ea8cb2d69ababafa7bf136c35/Configura____o_Celular_User_Management_PT.png)
 - Em __Autenticação__, você encontra as opções de modificação de senha, gerenciamento da verificação em 2 passos (2FA) para seu login no Admin VTEX e gerenciamento de sessões. Veja abaixo quais são essas opções.  
-![Configuração Autenticação User Management PT](https://images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/809706ede591d828432722b73feb06ad/Configura____o_Autentica____o_User_Management_PT.png)
+![Configuração Autenticação User Management PT](//images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/809706ede591d828432722b73feb06ad/Configura____o_Autentica____o_User_Management_PT.png)
 
 ## Verificação em 2 passos
 
@@ -50,4 +50,4 @@ Aqui você deve configurar o aplicativo que fornecerá a chave de autenticação
 
 Veja em detalhes como configurar o aplicativo no artigo [Habilitar login por autenticação de 2 fatores](https://help.vtex.com/pt/tutorial/habilitar-login-por-autenticacao-de-2-fatores#habilitar-o-2fa-por-aplicativo).
 
-![Configuração Verificação em 2 passos User Management PT](https://images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2f8ad9e2ee454b407adb333d0af7dfd7/Configura____o_Verifica____o_em_2_passos_User_Management_PT.png)
+![Configuração Verificação em 2 passos User Management PT](//images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2f8ad9e2ee454b407adb333d0af7dfd7/Configura____o_Verifica____o_em_2_passos_User_Management_PT.png)
diff --git a/docs/tutorials/pt/setting-up-place2pay-gateway.md b/docs/tutorials/pt/setting-up-place2pay-gateway.md
index 7a6ad3c63..942629e04 100644
--- a/docs/tutorials/pt/setting-up-place2pay-gateway.md
+++ b/docs/tutorials/pt/setting-up-place2pay-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Place2Pay'
 id: 2NmmnLpUPY0A8aMi0oyiQq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-07T21:45:23.671Z
-updatedAt: 2023-03-29T01:09:24.503Z
-publishedAt: 2023-03-29T01:09:24.503Z
+updatedAt: 2024-03-18T19:53:38.738Z
+publishedAt: 
 firstPublishedAt: 2018-03-07T22:13:43.326Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-gateway-place2pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 O Place2Pay é a versão com redirect do gateway PlaceToPay, que oferece soluções para lojas de grande e pequeno porte.
 
 Para configurar o Place2Pay, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md b/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
index bda4b0976..f2bb65564 100644
--- a/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
@@ -78,11 +78,11 @@ No menu principal do Admin, acesse __Preços__ e escolha a opção __Lista de pr
 
 No filtro da busca, insira os nomes das tabelas criadas no __Master Data__.
 
-![Filters](https://images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
+![Filters](//images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
 
 As tabelas de preço são mostradas como colunas da lista de preços, assim como as políticas comerciais.
 
-![Prices](https://images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
+![Prices](//images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
 
 Para atualizar o preço fixo em uma tabela específica, clique na coluna dessa tabela e depois em __Definir preços fixos__. 
 
@@ -99,7 +99,7 @@ Quando um usuário da sua loja não está logado, os preços mostrados a ele sã
 Mas se o usuário estiver logado, ele verá os preços correspondentes à tabela de preços à qual o email dele estiver associado.
 
 Por exemplo, estes dois clientes estão atrelados a tabelas de preços diferentes:
-![Clients](https://images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
+![Clients](//images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
 
 Quando o cliente Daniel, que está na tabela Silver, estiver logado na loja, ele verá os preços definidos nessa tabela. A mochila do exemplo acima aparecerá com o valor de R$ 50,00.
 Já o cliente Breno, que está na tabela Gold, verá os preços definidos nessa outra tabela. Para ele a mochila custará R$ 60,50.
diff --git a/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md b/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md
index a0371ffc3..d447a4a01 100644
--- a/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md
+++ b/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar adquirente Rede com o ERedeRest'
 id: 5TD6Ap9kiIUSiAMUsgYmcY
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-04-12T15:47:44.783Z
-updatedAt: 2023-03-29T01:11:21.243Z
-publishedAt: 2023-03-29T01:11:21.243Z
+updatedAt: 2024-03-18T18:22:35.227Z
+publishedAt: 
 firstPublishedAt: 2018-04-13T15:41:42.879Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-adquirente-rede-com-o-erederest
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Na VTEX, você pode fazer a integração com o [adquirente](/pt/tutorial/o-que-e-um-adquirente) Rede usando o conector ERedeREST. Esse conector traz uma série de melhorias, entre elas o suporte a meios de pagamento com pré-autorização (__Visa__, __Mastercard__, __American Express__, __Diners__, __Hipercard__, __JCB__ e __Credz__).
 
 <div class="alert alert-warning">
diff --git a/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md b/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md
index 504153153..04304e3d2 100644
--- a/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md
+++ b/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar Seller White Label como Ponto de Retirada (Pickup Point)'
 id: 6fSUE2O0taaoKieAaiuc4e
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-09-04T14:22:05.290Z
-updatedAt: 2023-03-29T18:58:34.411Z
-publishedAt: 2023-03-29T18:58:34.411Z
+updatedAt: 2023-07-26T21:33:59.946Z
+publishedAt: 
 firstPublishedAt: 2018-09-05T20:38:04.270Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -34,7 +34,7 @@ Para configurar um seller white label como ponto de retirada, é preciso cadastr
 - [Ponto de Retirada](https://help.vtex.com/pt/tutorial/creating-pickup-points--2R5ClQiwe4KoSQgsuiOw4E): com o endereço do seller white label.    
 - [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140): para exibir o Ponto de Retirada no checkout, é necessário configurar uma política de envio e vincular um ponto de retirada cadastrado.   
 - [Doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW): agora, você deve configurar uma Doca e vincular a transportadora cadastrada com o ponto de retirada. 
-- [Estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#cadastrar-estoque): você deve configurar um Estoque e vincular a política de envio cadastrada com o ponto de retirada.     
+- [Estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#cadastrar-estoque): você deve configurar um Estoque e vincular a política de envio cadastrada com o ponto de retirada.
 
 ## Preencher quantidade em estoque
 
@@ -48,6 +48,10 @@ Para saber em detalhes como preencher os  campos da planilha, acesse nosso artig
 
 Se a configuração do ponto de retirada tiver sido feita corretamente na Conta Franquia, os SKUs com __estoque disponível e preço__ poderão ser vendidos na Conta Principal, onde a Conta Franquia vai atuar como um __Seller White Label__ e a Conta Principal funcionará como um __Marketplace__.
 
+<div class="alert alert-warning">
+Certifique-se de que o seller white label está ativo. Para isso, acesse o Admin VTEX, em <b>Marketplace > Sellers > Gerenciamento</b>, e na linha do seller e coluna <i>Status</i>, clique em <code>Ativo</code>.
+</div>
+
 ### Seller White Label/Conta Franquia
 
 Para validar se o seller white label está realizando a entrega de um SKU através do ponto de retirada cadastrado, você deve fazer um `POST` na rota de fulfillment: 
diff --git a/docs/tutorials/pt/setting-up-shipment.md b/docs/tutorials/pt/setting-up-shipment.md
index ec8295e56..984e2b71a 100644
--- a/docs/tutorials/pt/setting-up-shipment.md
+++ b/docs/tutorials/pt/setting-up-shipment.md
@@ -27,7 +27,7 @@ A primeira caixinha com tempo total de __2 dias__ irá esperar o item represent
 
 O período considera T = 0 como a data do pedido.
 
-![Configuração em estoque e entrega ](https://images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/3dd5e11e0c89ad2285777f6a0a8eadc5/Configura____o_em_estoque_e_entrega_PT.png)
+![Configuração em estoque e entrega ](//images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/3dd5e11e0c89ad2285777f6a0a8eadc5/Configura____o_em_estoque_e_entrega_PT.png)
 
 ## Como configurar a remessa
 1. No Admin VTEX, acesse **Configurações da loja > Envio > Configurações**, ou digite *Envio* na barra de busca no topo da página e selecione *Configurações da loja / Envio*.  
diff --git a/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md b/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md
index cd03708bd..c36398e80 100644
--- a/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md
+++ b/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Sitef com pre-auth'
 id: 2ZH4DLmZpKw022aSGcGYag
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-05T21:07:59.629Z
-updatedAt: 2023-03-29T01:21:24.445Z
-publishedAt: 2023-03-29T01:21:24.445Z
+updatedAt: 2024-03-18T20:04:33.165Z
+publishedAt: 
 firstPublishedAt: 2018-03-06T14:09:56.654Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-gateway-sitef-com-pre-auth
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 Para permitir que compras feitas com cartão de crédito tenham o valor reservado, você pode configurar o gateway __Sitef com pre-auth__ (pré-autorização) na sua loja.
 
 Para isso, basta seguir os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-sitef-gateway.md b/docs/tutorials/pt/setting-up-sitef-gateway.md
index 5665f80db..ab6ac0f8c 100644
--- a/docs/tutorials/pt/setting-up-sitef-gateway.md
+++ b/docs/tutorials/pt/setting-up-sitef-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway Sitef'
 id: 1y3gqmbb6wgwscW8yeccAc
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-05T17:07:51.846Z
-updatedAt: 2023-03-29T01:01:36.029Z
-publishedAt: 2023-03-29T01:01:36.029Z
+updatedAt: 2024-03-18T20:02:31.580Z
+publishedAt: 
 firstPublishedAt: 2018-03-05T17:35:10.870Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,17 @@ legacySlug: configurar-gateway-sitef
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível configurar o gateway __Sitef__. Caso queira receber pagamentos pela Sitef, siga os passos abaixo:
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
 
-## Configurar afiliação de gateway Sitef
+Na VTEX, é possível configurar o gateway Sitef. Para configurá-lo, siga os passos abaixo:
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Sitef__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Sitef__ na barra de busca e clique sobre o nome do provedor.
 4. No campo __Id da Loja__, preencha com os dados do seu MerchantId na Sitef.
 5. Em __Chave de Acesso__, preencha com o MerchantKey fornecido pela Sitef.
 6. No campo __Captura de segurança antecipada__, escolha em quanto tempo deve ser realizada a captura do valor após a aprovação da transação.
-7. Clique em __Salvar__.
+7. Clique em `Salvar`.
 
 ## Configurar condição de pagamento
 
diff --git a/docs/tutorials/pt/setting-up-sms-password-recovery.md b/docs/tutorials/pt/setting-up-sms-password-recovery.md
index f9e06addc..f8ab6b821 100644
--- a/docs/tutorials/pt/setting-up-sms-password-recovery.md
+++ b/docs/tutorials/pt/setting-up-sms-password-recovery.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar recuperação de senha por SMS'
 id: 4MBZmPN2GSBNFooa9la555
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-03-07T21:02:11.023Z
-updatedAt: 2020-09-17T21:00:30.654Z
-publishedAt: 2020-09-17T21:00:30.654Z
+updatedAt: 2024-05-22T13:29:09.953Z
+publishedAt: 
 firstPublishedAt: 2019-03-07T21:04:24.196Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -26,13 +26,13 @@ Dito isso, confira o passo a passo de como configurar essa modalidade:
 1. Acesse __Central de Mensagens__.
 2. Clique em __Templates__.
 
-  ![5NrtBpFRTxInFl4aY2FrVz-pt](https://images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/554312ca709ec61b03aee1fed2f16e24/5NrtBpFRTxInFl4aY2FrVz-pt.png)
+  ![5NrtBpFRTxInFl4aY2FrVz-pt](//images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/554312ca709ec61b03aee1fed2f16e24/5NrtBpFRTxInFl4aY2FrVz-pt.png)
 
 3. Clique no template __Password Recovery__.
 4. Clique na aba __SMS__.
 5. Selecione a opção __“Ativar envio de SMS?”__
 
-  ![password-recovery-sms-tab-pt](https://images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/9199293f8290a94fbc4cf47c9cc2dd4a/password-recovery-sms-tab-pt.gif)
+  ![password-recovery-sms-tab-pt](//images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/9199293f8290a94fbc4cf47c9cc2dd4a/password-recovery-sms-tab-pt.gif)
 
   *No momento em que o usuário clica em “Ativar envio de SMS”, a plataforma apresenta as demais configurações de envio.*
 
@@ -40,7 +40,7 @@ Dito isso, confira o passo a passo de como configurar essa modalidade:
 7. Preencha o campo __Destination__ com a variável `{{_accountInfo.Telephone}}`.
 8. Preencha o campo __Message Text__ com o conteúdo da mensagem. As informações `Nome:{{name}}`, `Login:{{login}}` e `Senha: {{senha}}` são essenciais.
 
-  ![password-recovery-sms-fields-pt](https://images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ec001c43cf655f023b30db5a0bba2b29/password-recovery-sms-fields-pt.png)
+  ![password-recovery-sms-fields-pt](//images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ec001c43cf655f023b30db5a0bba2b29/password-recovery-sms-fields-pt.png)
 
 9. Revise o conteúdo do SMS em __Preview__.
 10. Clique em __Salvar __.
diff --git a/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md b/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md
index 45e0fca36..a1a27893c 100644
--- a/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md
+++ b/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar subadquirente Stelo'
 id: 3gHWiaK9wQg08wOsoysciQ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T17:43:45.957Z
-updatedAt: 2023-03-29T01:10:18.026Z
-publishedAt: 2023-03-29T01:10:18.026Z
+updatedAt: 2024-03-18T20:16:43.458Z
+publishedAt: 
 firstPublishedAt: 2018-03-02T20:17:14.474Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-subadquirente-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 A Stelo é um [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) que facilita a integração de meios de pagamento à sua loja.
 
 Para configurar a Stelo, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-the-critical-stock-alert.md b/docs/tutorials/pt/setting-up-the-critical-stock-alert.md
index 5af720806..5aaa013fb 100644
--- a/docs/tutorials/pt/setting-up-the-critical-stock-alert.md
+++ b/docs/tutorials/pt/setting-up-the-critical-stock-alert.md
@@ -23,7 +23,7 @@ O alerta de estoque crítico é uma funcionalidade de logística que tem o objet
 2. Preencha o campo de **Alerta de estoque crítico** com a quantidade de itens ou porcentagem de estoque desejada.
 3. Clique em **Salvar**.
 
-![alerta-estoque-critico pt](https://images.ctfassets.net/alneenqid6w5/4NNqAy9PJ6wUQsywOyE0UK/b033e0752c942adfbe5bab4e616acb63/alerta-estoque-critico_pt.png)
+![alerta-estoque-critico pt](//images.ctfassets.net/alneenqid6w5/4NNqAy9PJ6wUQsywOyE0UK/b033e0752c942adfbe5bab4e616acb63/alerta-estoque-critico_pt.png)
 
 ## Como funciona o Alerta
 
diff --git a/docs/tutorials/pt/setting-up-the-notes-payable-conector.md b/docs/tutorials/pt/setting-up-the-notes-payable-conector.md
new file mode 100644
index 000000000..526014ee2
--- /dev/null
+++ b/docs/tutorials/pt/setting-up-the-notes-payable-conector.md
@@ -0,0 +1,31 @@
+---
+title: 'Configurar o conector Promissórias'
+id: 7Gy0SJRVS0Qi2CuWMAqQc0
+status: CHANGED
+createdAt: 2018-06-22T15:15:02.946Z
+updatedAt: 2024-01-19T19:28:16.938Z
+publishedAt: 2023-10-18T17:29:11.714Z
+firstPublishedAt: 2018-06-22T19:10:55.195Z
+contentType: tutorial
+productTeam: Financial
+author: 245tA425AIeioKAk2eaiwS
+slug: configurar-o-conector-promissorias
+locale: pt
+legacySlug: configurar-o-conector-promissorias
+subcategory: 3tDGibM2tqMyqIyukqmmMw
+---
+
+O conector __Promissórias__, como o próprio nome já sugere, permite que sua loja passe a aceitar promissórias como forma de pagamento.
+
+Para configurar o Promissórias, siga os passos abaixo:
+
+## Configurar afiliação de gateway Promissórias
+1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
+2. Na aba __Afiliações de Gateways__, clique no botão `+`.
+3. Clique no conector __Promissórias__.
+4. No campo __Validade da promissória em dias (máx. de 180)__, defina quantos dias seu cliente terá para pagar a promissória antes que ela perca a validade.
+5. Em __Autorizar automaticamente__, informe se deseja aprovar o pagamento de imediato. Só recomendamos a escolha dessa opção para casos em que o pagamento é feito na entrega ou na retirada do pedido na loja. Ao escolher _Sim_, o pedido passa automaticamente para o status _Preparando Entrega_, sem passar por nenhuma verificação de pagamento.
+6. Clique em `Salvar`.
+
+## Configurar condição de pagamento
+Depois de seguir os passos indicados, o conector Promissórias vai estar configurado na sua loja. Assim, quando você for cadastrar uma Promissória (na aba __Pagamentos customizados__ da página de __Configurações__ do Pagamentos), ele vai estar disponível no campo __Processar com a afiliação__. Para saber como cadastrar pagamentos customizados, acesse [este artigo](/pt/tutorial/como-configurar-pagamento-customizado).
diff --git a/docs/tutorials/pt/setting-up-the-notify-me-option.md b/docs/tutorials/pt/setting-up-the-notify-me-option.md
index 57e6e943e..3480c1e5b 100644
--- a/docs/tutorials/pt/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/pt/setting-up-the-notify-me-option.md
@@ -23,7 +23,7 @@ Quando um produto está fora de [estoque](https://help.vtex.com/pt/tutorial/gere
 
 Veja abaixo um exemplo de como a opção **Avise-me** é exibida em uma loja. Para receber uma notificação quando o item estiver disponível para venda, o cliente deve digitar o nome e o email nos campos destacados e, em seguida, clicar no botão `Enviar`.
 
-![aviseme-pt](https://images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/c97a66089cc55b3570f518fd901a139f/image1.png)
+![aviseme-pt](//images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/c97a66089cc55b3570f518fd901a139f/image1.png)
 
 Assim que o item é reposto no estoque da loja, o sistema envia um email para o cliente automaticamente, informando que o produto já está disponível para compra. 
 
diff --git a/docs/tutorials/pt/setting-up-the-paymee-gateway.md b/docs/tutorials/pt/setting-up-the-paymee-gateway.md
index 567dd09e1..5a4cd3c3f 100644
--- a/docs/tutorials/pt/setting-up-the-paymee-gateway.md
+++ b/docs/tutorials/pt/setting-up-the-paymee-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar o gateway PayMee'
 id: 3fsilRdrBS6GOAy622soWy
 status: PUBLISHED
 createdAt: 2018-02-28T21:29:08.666Z
-updatedAt: 2019-12-31T15:20:50.800Z
-publishedAt: 2019-12-31T15:20:50.800Z
+updatedAt: 2024-03-14T17:02:16.884Z
+publishedAt: 2024-03-14T17:02:16.884Z
 firstPublishedAt: 2018-03-01T21:53:29.140Z
 contentType: tutorial
 productTeam: Financial
@@ -15,26 +15,19 @@ legacySlug: configurar-o-gateway-paymee
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-Na VTEX, é possível configurar o gateway de pagamentos PayMee. Com este conector, sua loja pode receber pagamentos por transferência bancária ou dinheiro.
+Na VTEX, é possível realizar a integração com o provedor de pagamento PayMee. Por meio deste provedor, sua loja pode realizar vendas por PayMee e PIX.
 
-Para realizar as configurações, siga os passos abaixo:
+Para configurar PayMee, siga os passos abaixo:
 
-## Configurar afiliação de gateway PayMee
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __PayMee__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta PayMee.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor PayMee na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
 
-1. Acesse __Pagamentos__.
-2. Clique em __Configurações__.
-3. Na aba __Afiliações de Gateways__, clique no botão __+__.
-4. Clique no conector __PayMee__.
-5. Preencha os campos de __Application Key__ e __Application Token__ com os dados fornecidos pela PayMee.
-6. Clique em __Salvar__.
+Para configurar os métodos de pagamento a serem processados pela PayMee, acesse [Configurar condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-## Configurar condição de pagamento PayMee
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-1. Já dentro das __Configurações__ em Pagamentos, clique na aba __Condições de pagamento__.
-2. Clique no botão __+__.
-3. Clique no meio de pagamento __PayMee__.
-4. Clique no botão __Status__, para ativar esta condição de pagamento.
-5. Caso deseje, marque a caixa __Usar Antifraude__ para ativar o antifraude básico.
-6. Clique em __Salvar__.
-
-__Pronto!__ Agora será exibida no checkout a opção de pagamento através do __PayMee__.
+Depois de seguir os passos indicados, PayMee pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-the-price-range-filter.md b/docs/tutorials/pt/setting-up-the-price-range-filter.md
index 34ec36778..7349af9cf 100644
--- a/docs/tutorials/pt/setting-up-the-price-range-filter.md
+++ b/docs/tutorials/pt/setting-up-the-price-range-filter.md
@@ -20,7 +20,7 @@ Importantíssimas para navegação e procura dos produtos desejados na loja.
 
 O cadastro é simples e pode-se determinar diferentes faixas de preços para categorias, conforme imagem abaixo:
 
-![faixa-de-preço pt](https://images.ctfassets.net/alneenqid6w5/2H77Lil1K88GcO4W6CYoy8/5af2211860af12fdcd846fbebabb9c2e/faixa-de-pre__o_pt.png)
+![faixa-de-preço pt](//images.ctfassets.net/alneenqid6w5/2H77Lil1K88GcO4W6CYoy8/5af2211860af12fdcd846fbebabb9c2e/faixa-de-pre__o_pt.png)
 
 Dentro de Faixas de Preço, clique em “Nova Faixa de Preço” e preencha os campos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
index a8bd1c120..e0b84398a 100644
--- a/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
@@ -25,23 +25,23 @@ Para facilitar, toda a configuração apresentada neste artigo pode ser <a href=
 
 Para configuração manual ou edição de uma meta já existente, o primeiro passo é acessar o Analytics e clicar no botão __Administrador__ no canto inferior esquerdo. Em seguida, ir na opção __Metas__, da coluna "Vista".
 
-![image](https://images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
 
 Na tela de administração de metas, opte por criar uma nova ou editar uma já existente.
 
 __No passo 1__ você pode seguir com uma meta de tipo personalizado:
 
-![image](https://images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
 
 __No passo 2__ você pode definir o nome que preferir para a sua meta e um código de posição (de uso interno do Google Analytics). Em tipo, vamos usar "Destino":
 
-![image](https://images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
 
 __No passo 3__ temos as configurações mais sensíveis. Nele configuramos a página que determina a conclusão da meta e o caminho que os clientes vão percorrer para atingi-la.
 
 No campo "Destino" selecione a opção expressão regular e insira a URL da página de pedido concluído: `^/checkout/orderPlaced`
 
-![image](https://images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
 
 Depois configure o caminho que o cliente vai percorrer até finalizar um pedido. Neste caso, estamos levando em conta que o processo de compra inicia na tela do produto; então meu funil vai servir para medir a quantidade de clientes que acessam essa tela, quantos pedidos foram finalizados e em qual passo os clientes estão desistindo da compra.
 
@@ -54,7 +54,7 @@ Ainda __no passo 3__, então, ative a opção __Funil__ com as etapas a seguir:
 5. __Entrega__: `^/checkout/(\?.*)?#/shipping$`
 6. __Pagamento__: `^/checkout/(\?.*)?#/payment$`
 
-![image](https://images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
+![image](//images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
 
 Uma forma de verificar se a meta está configurada corretamente é usar o link "Verifique essa meta". O Google vai gerar uma simulação da conversão da meta nos últimos 7 dias.
 
diff --git a/docs/tutorials/pt/setting-up-the-tnspay-gateway.md b/docs/tutorials/pt/setting-up-the-tnspay-gateway.md
index bfbdbbe9b..dfb090e05 100644
--- a/docs/tutorials/pt/setting-up-the-tnspay-gateway.md
+++ b/docs/tutorials/pt/setting-up-the-tnspay-gateway.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar o gateway TNSPay'
 id: 6jIUr6Va00QyEuMEGAmQA6
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-03-02T12:43:42.795Z
-updatedAt: 2023-03-29T01:14:08.864Z
-publishedAt: 2023-03-29T01:14:08.864Z
+updatedAt: 2024-03-18T20:23:20.750Z
+publishedAt: 
 firstPublishedAt: 2018-03-02T15:56:49.389Z
 contentType: tutorial
 productTeam: Financial
@@ -15,6 +15,8 @@ legacySlug: configurar-o-gateway-tnspay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 O TNSPay é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com certificação PCI e que oferece uma série de recursos de segurança para facilitar o processamento de [compras recorrentes](/pt/faq/como-funciona-a-compra-recorrente).
 
 Para configurar o TNSPay, siga os passos abaixo:
diff --git a/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md b/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
index 174b7dcdd..5888cf310 100644
--- a/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
@@ -25,7 +25,7 @@ O ID da forma de pagamento, que será configurada com Juros Simples, é obtido d
 - Acesse a Condição de Pagamento que deseja configurar para usar Juros Simples
 - Copie o último parâmetro da URL, que indica o ID dessa Forma de Pagamento (ver imagem)
 
-![imagem para valer do artigo em português de financial](https://images.ctfassets.net/alneenqid6w5/2Q1rgCboSZE7N9hQ5k7qlD/f179a4a58dc9c75a1154b48141d3c003/imagem_para_valer_do_artigo_em_portugu__s_de_financial.png)
+![imagem para valer do artigo em português de financial](//images.ctfassets.net/alneenqid6w5/2Q1rgCboSZE7N9hQ5k7qlD/f179a4a58dc9c75a1154b48141d3c003/imagem_para_valer_do_artigo_em_portugu__s_de_financial.png)
 
 ## Configurar o tipo de juros usando API
 
diff --git a/docs/tutorials/pt/setting-up-the-voucher-list.md b/docs/tutorials/pt/setting-up-the-voucher-list.md
index 109e24fa8..3fba6c038 100644
--- a/docs/tutorials/pt/setting-up-the-voucher-list.md
+++ b/docs/tutorials/pt/setting-up-the-voucher-list.md
@@ -27,14 +27,14 @@ A configuração depende de dois pontos, listados abaixo.
 
 - O SKU precisa ser configurado para gerar crédito em vale.
 
-![sku-opção-credito-vale pt](https://images.ctfassets.net/alneenqid6w5/JLjFssu5Q2awo2UyiuOEQ/2719360144a349ef7fcf68fc96a7dee6/sku-op____o-credito-vale_pt.png)
+![sku-opção-credito-vale pt](//images.ctfassets.net/alneenqid6w5/JLjFssu5Q2awo2UyiuOEQ/2719360144a349ef7fcf68fc96a7dee6/sku-op____o-credito-vale_pt.png)
 
 
 ## Configurações no Tipo de Lista
 
 A criação desse tipo de lista pede que, nas configurações, a entrega seja marcada como "Valor dos produtos comprados será convertido em Vale Compras". Veja a imagem de exemplo.
 
-![entrega-tipos-lista pt](https://images.ctfassets.net/alneenqid6w5/7cX5Qz5CG4gSQuwOUKSy0Y/21687cba7440124b65e6b4be17007191/entrega-tipos-lista_pt.png)
+![entrega-tipos-lista pt](//images.ctfassets.net/alneenqid6w5/7cX5Qz5CG4gSQuwOUKSy0Y/21687cba7440124b65e6b4be17007191/entrega-tipos-lista_pt.png)
 
 Salve a sua lista após realizadas as demais configurações desejadas.
 
diff --git a/docs/tutorials/pt/setting-up-the-worldpay-acquirer.md b/docs/tutorials/pt/setting-up-the-worldpay-acquirer.md
index bf96f5c9d..fd480a528 100644
--- a/docs/tutorials/pt/setting-up-the-worldpay-acquirer.md
+++ b/docs/tutorials/pt/setting-up-the-worldpay-acquirer.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar o adquirente Worldpay '
+title: 'Configurar pagamento com Worldpay-Payments-Via-WPG'
 id: 7GCtigwhNYMi604UM0KeO6
 status: PUBLISHED
 createdAt: 2018-02-28T22:09:45.321Z
-updatedAt: 2023-03-29T00:47:52.166Z
-publishedAt: 2023-03-29T00:47:52.166Z
+updatedAt: 2024-03-18T17:20:43.467Z
+publishedAt: 2024-03-18T17:20:43.467Z
 firstPublishedAt: 2018-02-28T22:38:14.737Z
 contentType: tutorial
 productTeam: Financial
@@ -19,16 +19,29 @@ A Worldpay é um [adquirente](/pt/tutorial/o-que-e-um-adquirente) de atuação g
 
 Para configurar o Worldpay, siga os passos abaixo:
 
-## Configurar afiliação de gateway Worldpay
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Worldpay-Payments-Via-WPG__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Chave de aplicação__ e __Token de aplicação__ insira as informações que foram fornecidas pela Worldpay.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor Worldpay na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Em __Controle de pagamento__, selecione se deseja ativar o provedor em ambiente de teste clicando em __Ativar modo de teste__.
+7. Em __Liquidação automática__, selecione uma das seguintes opções:
+<br>
+<ul>
+<br>
+    	<li><b>Usar comportamento recomendado pelo processador de pagamentos</b>: a captura não é automática, mas agendada de acordo com o prazo especificado pela adquirente que, além de indicar se o pagamento foi autorizado, pode especificar ou recomendar um número de dias para a captura no momento da resposta à autorização do pagamento (este é o comportamento padrão da plataforma).</li>
+    	<li><b>Liquidação automática imediatamente após a autorização do pagamento</b>: a captura é automática e acontece logo após a autorização, mesmo que a transação possua uma análise antifraude.</li>
+   		<li><b>Liquidação automática imediatamente após a análise antifraude</b>: a captura é automática e acontece logo após a autorização e análise antifraude (Caso você selecione este comportamento e não possua análise antifraude, a captura do pagamento acontecerá da mesma forma que no comportamento "Liquidação automática imediatamente após a autorização do pagamento").</li>      
+   		<li><b>Desativado</b>: a captura acontece somente quando o pedido for faturado. Caso escolha esse comportamento de captura, é importante atentar-se quanto ao tempo do faturamento. Isso porque o faturamento pode ultrapassar o tempo de captura acordado com o provedor de pagamentos e levar à perda da transação.</li>
+</ul>
+8. Caso deseje utilizar o [split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) em sua loja, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
 
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Worldpay__.
-4. Preencha os campos de cadastro com as informações da sua conta na Worldpay (campos _UserName_, _Password_, _Version_, _MerchantCode_).
-5. No campo __Currency__, escolha a moeda das transações.
-6. No campo __Captura de segurança antecipada__, escolha em quanto tempo você deseja que a captura seja realizada após a aprovação da tranasação e análise do antifraude. Você também pode desativar a função.
-7. Clique em __Salvar__.
+9. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão `Instalar app` e siga as instruções de instalação.
 
-## Configurar condição de pagamento
+10. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, a Worldpay vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ela vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento faça parte da rede de adquirência da Worldpay). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
+Para configurar os métodos de pagamento a serem processados pela Worldpay, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
+
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, Worldpay pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento. 
diff --git a/docs/tutorials/pt/setting-up-the-yamisplitmoipv1-gateway.md b/docs/tutorials/pt/setting-up-the-yamisplitmoipv1-gateway.md
index 262405e59..a84726e3a 100644
--- a/docs/tutorials/pt/setting-up-the-yamisplitmoipv1-gateway.md
+++ b/docs/tutorials/pt/setting-up-the-yamisplitmoipv1-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar o gateway YamiSplitMoipV1'
 id: 5qrjr9yukwsk4oaMMAisSK
 status: PUBLISHED
 createdAt: 2018-02-28T16:56:41.540Z
-updatedAt: 2023-03-29T00:48:49.159Z
-publishedAt: 2023-03-29T00:48:49.159Z
+updatedAt: 2024-03-12T21:02:38.695Z
+publishedAt: 2024-03-12T21:02:38.695Z
 firstPublishedAt: 2018-02-28T21:48:56.044Z
 contentType: tutorial
 productTeam: Financial
@@ -15,17 +15,19 @@ legacySlug: configurar-o-gateway-yamisplitmoipv1
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-O YamiSplitMoipV1 é um gateway dedicado que extende funcionalidades do Moip. Com ele, é possível realizar splits de pagamento nos marketplaces (solução para o usuário fazer um único pagamento, mesmo comprando produtos de sellers diferentes) usando o subadquirente.
+Na VTEX, é possível realizar a integração com o provedor de pagamento YamiSplitMoipV1. Por meio deste provedor, sua loja pode realizar vendas com cartões de crédito e boleto.
 
-## Configurar afiliação de gateway YamiSplitMoipV1
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __YamiSplitMoipV1__.
-4. Preencha os campos _Application Key_ e _Application Token_ com as informações da sua conta __Moip__.
-5. Clique em __Salvar__.
+Para configurar o YamiSplitMoipV1, siga os passos abaixo:
 
-## Configurar condição de pagamento
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __YamiSplitMoipV1__ na barra de busca e clique sobre o nome do provedor.
+4. Em __Autorização do provedor__, preencha os campos __Chave de aplicação__ e __Token de aplicação__ com as informações da sua conta Moip.
+5. Caso deseje modificar o nome de identificação a ser exibido para o provedor YamiSplitMoipV1 na tela do Admin VTEX, insira a informação no campo __Nome__ em __Informações básicas__.
+6. Clique em `Salvar`.
 
-Depois de seguir os passos indicados, o YamiSplitMoipV1 vai estar configurado na sua loja. Assim, quando você for cadastrar uma condição de pagamento para ser usada em um marketplace, ele vai estar disponível no campo __Processar com a afiliação__. 
+Para configurar os métodos de pagamento a serem processados pelo YamiSplitMoipV1, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
+
+Depois de seguir os passos indicados, YamiSplitMoipV1 pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
diff --git a/docs/tutorials/pt/setting-up-vcmais-gateway.md b/docs/tutorials/pt/setting-up-vcmais-gateway.md
index d06c035d4..e4c14288e 100644
--- a/docs/tutorials/pt/setting-up-vcmais-gateway.md
+++ b/docs/tutorials/pt/setting-up-vcmais-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar gateway vcmais'
 id: 28nAmwnfxWSoQEIO8EYYaI
 status: PUBLISHED
 createdAt: 2018-04-17T21:48:38.248Z
-updatedAt: 2023-03-29T00:43:23.712Z
-publishedAt: 2023-03-29T00:43:23.712Z
+updatedAt: 2023-10-18T12:07:58.261Z
+publishedAt: 2023-10-18T12:07:58.261Z
 firstPublishedAt: 2018-04-18T21:26:18.172Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/setting-up-vindi-gateway.md b/docs/tutorials/pt/setting-up-vindi-gateway.md
index bac1f415d..a919e2080 100644
--- a/docs/tutorials/pt/setting-up-vindi-gateway.md
+++ b/docs/tutorials/pt/setting-up-vindi-gateway.md
@@ -1,10 +1,10 @@
 ---
-title: 'Configurar o gateway Vindi'
+title: 'Configurar pagamento com Vindi'
 id: 61EXzfrBZYIgGU26EGcaMo
-status: DRAFT
+status: PUBLISHED
 createdAt: 2018-03-01T15:25:39.368Z
-updatedAt: 2022-12-23T20:47:23.110Z
-publishedAt: 
+updatedAt: 2024-01-23T21:49:28.618Z
+publishedAt: 2024-01-23T21:49:28.618Z
 firstPublishedAt: 2018-03-01T16:21:19.864Z
 contentType: tutorial
 productTeam: Financial
@@ -15,20 +15,18 @@ legacySlug: configurar-o-gateway-vindi
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-A Vindi é um gateway de pagamentos com certificação PCI, o que garante a segurança dos dados transacionados por ela. Atualmente, ela processa pagamentos realizados por cartões de crédito, boletos bancários e Paypal.
+Na VTEX, é possível realizar a integração com o provedor de pagamento Vindi. Por meio deste provedor, sua loja pode realizar vendas por meio de cartões de crédito, boletos bancários e Paypal.
 
-Para configurar a Vindi, siga os passos abaixo:
+Para configurar Vindi, siga os passos abaixo:
 
-## Configurar afiliação de gateway Vindi
-1. Acesse o módulo __Pagamentos__.
-2. Clique em __Configurações__.
-3. Na aba __Afiliações de Gateways__, clique no botão __+__.
-4. Clique no conector __Vindi__.
-5. Preencha os campos de cadastro com os dados fornecidos pela Vindi (campos _Application Key_ e _Application Token_).
-6. Clique em __Salvar__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __Vindi__ na barra de busca e clique sobre o nome do provedor.
+4. Nos campos __Application Key__ e __Application Token__, insira as informações que fornecidas pela Vindi.
+5. Clique em `Salvar`.
 
-## Configurar condição de pagamento
+Para configurar os métodos de pagamento a serem processados pela Vindi, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-Depois de seguir os passos indicados, a Vindi vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, esse gateway vai estar disponível no campo __Processar com a afiliação__ (desde que os meios de pagamento sejam compatíves com a Vindi).
+Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
+Depois de seguir os passos indicados, o provedor Vindi pode demorar até 10 minutos para aparecer no checkout da sua loja como uma opção de pagamento.
diff --git a/docs/tutorials/pt/setting-up-webpay2p-gateway.md b/docs/tutorials/pt/setting-up-webpay2p-gateway.md
index 23cf5552b..4cdc3369f 100644
--- a/docs/tutorials/pt/setting-up-webpay2p-gateway.md
+++ b/docs/tutorials/pt/setting-up-webpay2p-gateway.md
@@ -3,8 +3,8 @@ title: 'Configurar o gateway WebPay2P'
 id: 34Bn1nOoVO6iesWAgSEQQA
 status: PUBLISHED
 createdAt: 2018-04-02T19:30:48.720Z
-updatedAt: 2021-07-07T17:45:55.414Z
-publishedAt: 2021-07-07T17:45:55.414Z
+updatedAt: 2024-03-07T13:50:16.754Z
+publishedAt: 2024-03-07T13:50:16.754Z
 firstPublishedAt: 2018-04-02T19:46:03.221Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/setup-safetypay.md b/docs/tutorials/pt/setup-safetypay.md
index fefa989fe..921211b0d 100644
--- a/docs/tutorials/pt/setup-safetypay.md
+++ b/docs/tutorials/pt/setup-safetypay.md
@@ -1,10 +1,10 @@
 ---
 title: 'Configurar gateway SafetyPay'
 id: lf89DOdeveuMOI4Q0CwgC
-status: PUBLISHED
+status: DRAFT
 createdAt: 2018-02-22T13:57:16.523Z
-updatedAt: 2023-03-29T00:44:35.344Z
-publishedAt: 2023-03-29T00:44:35.344Z
+updatedAt: 2024-03-18T19:57:00.504Z
+publishedAt: 
 firstPublishedAt: 2018-02-22T15:12:57.862Z
 contentType: tutorial
 productTeam: Financial
@@ -15,15 +15,15 @@ legacySlug: configurar-safetypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
+<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+
 SafetyPay é uma solução de pagamentos que conecta diretamente o checkout da sua loja ao banco do seu cliente. Nesta solução, o seu cliente escolhe a SafetyPay como meio de pagamento e é *redirecionado* para o ambiente seguro do internet banking escolhido. Uma vez redirecionado, o cliente pode fazer uma transferência bancária e realizar o pagamento do pedido.
 
 Para configurar o SafetyPay, siga os passos abaixo:
 
-## Configurar afiliação de gateway SafetyPay
-
-1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
-2. Na aba __Afiliações de Gateways__, clique no botão __+__.
-3. Clique no conector __Safety Pay__.
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
+2. Na tela de provedores, clique no botão `Novo provedor`.
+3. Digite o nome __SafetyPay__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha os campos de cadastro com os dados fornecidos pela SafetyPay (Campos *ApiKey, SignatureKey, Custom Merchant Name*).
 5. O campo __Tracking Code__ é opcional. Ele pode ser utilizado para você realizar análises de marketing.
 6. No campo __Product ID__, preencha com o meio de pagamento desejado: __Express__ para transferência bancária ou __Cash__ para pagamento em dinheiro.
@@ -31,7 +31,7 @@ Para configurar o SafetyPay, siga os passos abaixo:
 8. Em __Language__, escolha o idioma que será utilizado na UI.
 9. No campo __Time To Expire (in hours)__, escolha o tempo de expiração do pagamento.
 10. No campo __Time To Expire for Lottery Payment (in days)__, escolha o tempo de expiração de pagamentos a serem feitos em lotéricas (aplica-se somente ao Brasil).  
-11. Clique em __Salvar__.
+11. Clique em `Salvar`.
 
 ## Configurar condição de pagamento SafetyPay
 
diff --git a/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md b/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
index 003f66985..48bd47390 100644
--- a/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
+++ b/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
@@ -3,8 +3,8 @@ title: 'Informações compartilhadas entre marketplace e seller na VTEX'
 id: 3o7WGiBtfnKKZ3Ddug26k3
 status: PUBLISHED
 createdAt: 2022-04-07T13:32:06.199Z
-updatedAt: 2023-04-17T21:51:10.740Z
-publishedAt: 2023-04-17T21:51:10.740Z
+updatedAt: 2023-10-31T19:54:13.803Z
+publishedAt: 2023-10-31T19:54:13.803Z
 firstPublishedAt: 2022-04-07T14:23:25.578Z
 contentType: tutorial
 productTeam: Channels
@@ -44,7 +44,7 @@ Além disso, para [adicionar o seller](https://help.vtex.com/pt/tutorial/configu
 É possível integrar o marketplace VTEX a seller VTEX, ou seller externo, tanto pelo Admin VTEX quanto por API. Nos dois casos, os dados compartilhados entre marketplace e seller serão os mesmos.
 
 <div class = "alert alert-info">
-Para mais informações sobre como conectar marketplace VTEX a seller VTEX, ou seller externo, pelo Admin VTEX, veja o artigo <a href="https://help.vtex.com/pt/tutorial/configurando-seller">Adicionar seller</a>. Para integração por API, utilize a chamada <a href="https://developers.vtex.com/vtex-rest-api/reference/upsertsellerrequest">Configure Seller Account</a>. Em caso de seller externo, confira o <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">guia de integração com seller externo</a>.
+Para mais informações sobre como conectar marketplace VTEX a seller VTEX, ou seller externo, pelo Admin VTEX, veja o artigo <a href="https://help.vtex.com/pt/tutorial/configurando-seller">Adicionar seller</a>. Para integração por API, utilize a chamada <a href="https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers">Configure Seller Account</a>. Em caso de seller externo, confira o <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">guia de integração com seller externo</a>.
 </div>
 
 ### Conectar marketplace VTEX a seller VTEX
@@ -75,14 +75,14 @@ Quando o seller é do tipo externo, não hospedado no ambiente VTEX, ele precisa
 
 Uma vez que o marketplace VTEX e o seller VTEX, ou externo, estejam conectados, o marketplace pode acessar essas informações sobre o seller pelo Admin VTEX, em **MARKETPLACE > Gerenciamento**.
 
-Também é possível consultar as informações fornecidas pelo seller por API, tanto para seller VTEX quanto externo, pela chamada [Get Seller data by ID](https://developers.vtex.com/vtex-rest-api/reference/getretrieveseller).
+Também é possível consultar as informações fornecidas pelo seller por API, tanto para seller VTEX quanto externo, pela chamada [Get Seller data by ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#get-/seller-register/pvt/sellers/-sellerId-).
 
 ## Compartilhamento de emails de clientes
 
 O marketplace pode conceder ao seller acesso parcial aos emails da sua base de clientes, de forma que esses emails sejam utilizados nas requisições de consulta às condições comerciais de itens e na criação de pedidos. Esta não é uma configuração padrão e o gerenciamento dessas informações é feito por API, por meio do campo `TrustPolicy`, utilizando as seguintes chamadas:
 
-- [Configure Seller Account](https://developers.vtex.com/vtex-rest-api/reference/upsertsellerrequest): permite configurar a conta do seller, seja ele seller VTEX ou externo.
-- [Update Seller by Seller ID](https://developers.vtex.com/vtex-rest-api/reference/updateseller): permite atualizar os dados do seller, seja ele seller VTEX ou externo.
+- [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers): permite configurar a conta do seller, seja ele seller VTEX ou externo.
+- [Update Seller by Seller ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#patch-/seller-register/pvt/sellers/-sellerId-): permite atualizar os dados do seller, seja ele seller VTEX ou externo.
 
 <div class = "alert alert-info">
 Em pedidos realizados no marketplace, o email do cliente não é exibido para o seller. A relação do cliente é estabelecida com o marketplace e seria necessário o consentimento do cliente para o compartilhamento de seus dados.
diff --git a/docs/tutorials/pt/sharpspring-suiteshare.md b/docs/tutorials/pt/sharpspring-suiteshare.md
index 3b7377779..cadda81fd 100644
--- a/docs/tutorials/pt/sharpspring-suiteshare.md
+++ b/docs/tutorials/pt/sharpspring-suiteshare.md
@@ -21,29 +21,29 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **SharpSrpring**.
 
-   ![SharpSpring_1](https://images.ctfassets.net/alneenqid6w5/3GAphuPmnfRLWSwUj6kf2t/9b3a07ed03a91a5c7b56cbf813fd31b8/SharpSpring_1.png)
+   ![SharpSpring_1](//images.ctfassets.net/alneenqid6w5/3GAphuPmnfRLWSwUj6kf2t/9b3a07ed03a91a5c7b56cbf813fd31b8/SharpSpring_1.png)
 
 2. Acesse **Configurações > Integrações > Marketing > Habilitar**.
 
-   ![SharpSpring_2](https://images.ctfassets.net/alneenqid6w5/2mVIrVMqw46gouJObzggSb/e84e232c373a1388f66bd21e99d4e163/SharpSpring_2.png)
+   ![SharpSpring_2](//images.ctfassets.net/alneenqid6w5/2mVIrVMqw46gouJObzggSb/e84e232c373a1388f66bd21e99d4e163/SharpSpring_2.png)
 
-   ![SharpSpring_3](https://images.ctfassets.net/alneenqid6w5/2iyTWPWFwA8knyZVVTvMNz/f8841da59167b18c48f6a81d8a7c0190/SharpSpring_3.png)
+   ![SharpSpring_3](//images.ctfassets.net/alneenqid6w5/2iyTWPWFwA8knyZVVTvMNz/f8841da59167b18c48f6a81d8a7c0190/SharpSpring_3.png)
 
 O próximo passo é acessar sua conta da **SharpSpring** e fazer login.
 
-![SharpSpring_4](https://images.ctfassets.net/alneenqid6w5/2WlxccYGdMlXuhmqndYnZE/f4774b9e268ffb3e1f5439c15413127e/SharpSpring_4.png)
+![SharpSpring_4](//images.ctfassets.net/alneenqid6w5/2WlxccYGdMlXuhmqndYnZE/f4774b9e268ffb3e1f5439c15413127e/SharpSpring_4.png)
 
 Agora, acesse o menu **Configurações** no canto superior direito.
 
-![SharpSpring_5](https://images.ctfassets.net/alneenqid6w5/5Ywk5ubVZNDQi0IpYt2u0Y/7c728729f51983336ce07e02b5c8a856/SharpSpring_5.png)
+![SharpSpring_5](//images.ctfassets.net/alneenqid6w5/5Ywk5ubVZNDQi0IpYt2u0Y/7c728729f51983336ce07e02b5c8a856/SharpSpring_5.png)
 
 Em **Configurações**, clique em **Configurações API**.
 
-![SharpSpring_6](https://images.ctfassets.net/alneenqid6w5/2gzKOi3F2hCvrhHH7LRFOk/29f24870c6c09d3cd9e509550b9c5b37/SharpSpring_6.png)
+![SharpSpring_6](//images.ctfassets.net/alneenqid6w5/2gzKOi3F2hCvrhHH7LRFOk/29f24870c6c09d3cd9e509550b9c5b37/SharpSpring_6.png)
 
 Agora que você tem acesso às chaves da API, basta selecionar o link que deseja integrar com o CRM (captura) e inserior os códigos dentro da VTEX Assisted Sales (SuiteShare).
 
-![SharpSpring_7](https://images.ctfassets.net/alneenqid6w5/5EuuoLIO47LBgF0cKElMdo/6321b7c9b4ce5137efbcc669f80a7a47/SharpSpring_7.png)
+![SharpSpring_7](//images.ctfassets.net/alneenqid6w5/5EuuoLIO47LBgF0cKElMdo/6321b7c9b4ce5137efbcc669f80a7a47/SharpSpring_7.png)
 
 Pronto! Você acabou de integrar a VTEX Assisted Sales (SuiteShare) com o seu CRM. 
 
diff --git a/docs/tutorials/pt/shipping-options-beta.md b/docs/tutorials/pt/shipping-options-beta.md
index a001ac512..08cf7e222 100644
--- a/docs/tutorials/pt/shipping-options-beta.md
+++ b/docs/tutorials/pt/shipping-options-beta.md
@@ -1,10 +1,10 @@
 ---
 title: 'Opções de envio (Beta)'
 id: 7gsdck3519Z3VPqzwFFHJL
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-05-27T15:35:44.505Z
-updatedAt: 2023-03-21T17:44:07.634Z
-publishedAt: 2023-03-21T17:44:07.634Z
+updatedAt: 2023-08-14T17:28:57.629Z
+publishedAt: 
 firstPublishedAt: 2022-05-31T18:53:28.695Z
 contentType: tutorial
 productTeam: Others
@@ -93,7 +93,7 @@ Para criar uma opção de envio, siga os passos abaixo:
     - **Frete grátis:** sem custos para o consumidor, não requer configurações adicionais.
 8. Clique no botão `Salvar`.
 
-![opcoes_envio_criacao_pt](https://images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/a99720c733f07f383aa9cfcdd9a18e76/opcoes_envio_criacao_pt.png)
+![opcoes_envio_criacao_pt](//images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/a99720c733f07f383aa9cfcdd9a18e76/opcoes_envio_criacao_pt.png)
 
 ### Editar opção de envio
 
@@ -117,7 +117,7 @@ Além de editar uma opção de envio, no ícone menu <i class="fas fa-ellipsis-v
 
 Uma vez que você tenha opções de envio configuradas, elas vão aparecer em uma listagem em **Configurações da loja > Envio > Opções de envio**, conforme a imagem a seguir:
 
-![opcoes_envio_listagem_pt](https://images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/713a7a5fa03c809e2bd0ad8b8abe60f5/opcoes_envio_listagem_pt.png)
+![opcoes_envio_listagem_pt](//images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/713a7a5fa03c809e2bd0ad8b8abe60f5/opcoes_envio_listagem_pt.png)
 
 A tabela abaixo contém a descrição das colunas apresentadas:
 
diff --git a/docs/tutorials/pt/shipping-policy.md b/docs/tutorials/pt/shipping-policy.md
index 98b597b80..b346d2a61 100644
--- a/docs/tutorials/pt/shipping-policy.md
+++ b/docs/tutorials/pt/shipping-policy.md
@@ -1,10 +1,10 @@
 ---
-title: 'Política de Envio'
+title: 'Política de envio'
 id: tutorials_140
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:12.502Z
-updatedAt: 2023-03-29T18:19:38.883Z
-publishedAt: 2023-03-29T18:19:38.883Z
+updatedAt: 2024-01-31T01:24:50.628Z
+publishedAt: 2024-01-31T01:24:50.628Z
 firstPublishedAt: 2017-04-27T23:00:45.247Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,69 +15,44 @@ legacySlug: cadastrar-transportadora, gerenciar-transportadora
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-Política de envio é um conjunto de regras que definem as opções e condições de frete que serão apresentadas ao consumidor no momento da finalização da compra. As condições de frete incluem configurações de horário de funcionamento da transportadora, prazos de entrega, valores adicionais de frete, tipos de produtos passíveis de entrega (modais) e janelas de entrega.
+O conjunto de configurações [logísticas](https://help.vtex.com/pt/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) essenciais de uma loja VTEX recebe o nome de [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), que é a relação entre os seguintes aspectos:
 
-Todas essas configurações são baseadas principalmente no contrato que a sua loja tem com uma [transportadora](https://help.vtex.com/pt/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE), com um prestador de serviço, ou com qualquer outro tipo de contrato de serviço de frete que sua loja ofereça aos consumidores.
+1. Política de envio
+2. [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)
+3. [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
 
-<div class="alert alert-info"> 
-É possível que uma mesma transportadora seja base de múltiplas políticas de envio, cada uma com suas particularidades. Veja abaixo como criar, editar e excluir políticas de envio.
-</div>
+A imagem abaixo mostra como esses conceitos se relacionam entre si:
 
-Pela plataforma da VTEX, é possível: 
+![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
 
-*   [Cadastrar políticas de envio](#cadastrar-uma-politica-de-envio)
-*   [Editar políticas de envio](#editar-uma-politica-de-envio)
-*   [Excluir políticas de envio](#excluir-uma-politica-de-envio)
+**Política de envio** é um conjunto de regras e configurações que definem quais opções de envio serão apresentadas aos clientes no checkout. Quando a plataforma VTEX [calcula o tempo de envio](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) do pedido, as configurações das políticas de envio são consideradas, e algumas das principais são:
 
-## Cadastrar uma política de envio
+* [Transportadora](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE)
+* [Horário de funcionamento da transportadora](https://help.vtex.com/pt/tutorial/horario-de-funcionamento-das-transportadoras--2oGpbInIgdxSWUi3TZjdCS)
+* [Feriados](https://help.vtex.com/pt/tutorial/cadastrar-feriados--2ItOthSEAoyAmcwsuiO6Yk)
+* [Adicionais de frete](https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV)
+* [Entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)
+* [Pontos de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R)
 
-1. No Admin VTEX, acesse **Envio > Estratégia de Envio > Políticas de Envio** ou digite *Estratégia de envio* na barra de busca no topo da página.
-2. Clique no botão `Criar política de envio`.
-3. Preencha os campos da tela e clique em `Salvar alterações` ao terminar:
-*   **Ativa**: ativa ou desativa a política de envio.
-*   **Nome:** nome interno da política de envio.
-*   **ID:** identificador interno e para integradores. Deve ser preenchido apenas com letras e números. Caso não seja preenchido, será criado um ID automaticamente.
-*   **[Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126):** nome do tipo de entrega. Serve para separar os diferentes serviços de entrega. É o nome que será exibido na finalização de compra para o cliente. Ex. expresso vs. normal. 
-*   **[Upload de tarifas de envio](https://help.vtex.com/pt/tutorial/como-montar-a-planilha-de-frete--tutorials_127)**: é a tabela com os valores e prazos de frete assumidos pela política de envio. 
-*   **[Dimensões do Pacote](https://help.vtex.com/pt/tutorial/como-funciona-o-empilhamento--tutorials_124):**
-    *   **Soma das dimensões:** limite de dimensão do pacote que leva em conta a soma da medida de todas as arestas do pacote. Ao atingir esse valor, ou a entrega é dividida em pacotes ou não é feita. Estes dados são passados pela transportadora no momento de fechamento do contrato com a mesma. 
-    *   **Maior aresta:** limite de tamanho da maior aresta do pacote. Ao atingir esse valor, ou a entrega é dividida em pacotes ou não é feita.
-    *   **[Fator de peso cúbico](https://help.vtex.com/pt/tutorial/como-o-peso-cubado-e-calculado--tutorials_128):** fator que será utilizado para cálculo do peso cubado. Soma das medidas, dividida pelo fator cúbico. 
-    *   **Fator de peso mínimo:** use o peso cúbico apenas se este passar deste valor. Limite de peso onde, a partir dele, será considerado o cálculo do peso cubado para o frete.
-*   **Fins de semana e feriados:** os dias da semana para entregas. Marque as flags, para ativar a entrega nos seguintes cenários: `Entrega nos sábados`, `Entrega nos domingos`, `Entrega nos feriados`.
-*   **[Modais ativos](https://help.vtex.com/pt/tutorial/como-funciona-o-modal--tutorials_125):** especificações de produtos que necessitam de uma entrega especial. São as limitações de envio do produto que a política de envio permite. Marque as flags para ativar a entrega nos seguintes cenários: `químicos`, `eletrônicos`, `móveis`, `vidro`, `líquidos`, `colchões`, `refrigerados`, `pneus`, `linha branca` e `armas de fogo`.
-*   **Itens do pacote:** descrição de valor e número de itens do pacote:
-    *   **Valor mínimo:** valor mínimo aceito pela política de envio, para realizar o frete.
-    *   **Mínimo de itens:**  múltiplo mínimo da quantidade de itens aceita pela transportadora. Por exemplo, se for preenchido com o valor **3**, significa que a transportadora só realiza  entregas que têm quantidades de itens múltiplos de  três (3, 6, 9, 21…).
-    *   **Valor máximo:** máximo valor aceito pela política de envio, para realizar o frete.
-*   **Relacionar pontos de retirada:** marque esta flag, para abrir a opção de Pontos de retirada. Clique no dropdown e selecione entre `Tags dos pontos de retirada`, `Nomes dos pontos de retirada` e `Importar ponto de retirada de sellers` previamente cadastrados.
-*   **[Horário de funcionamento:](https://help.vtex.com/pt/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS)** os horários em que a política de envio faz coletas ou as janelas de tempo em que ela envia os itens para os clientes. Estas configurações influenciam o cálculo do tempo de entrega:
-    *   **Período de envio:** é onde você cadastra os períodos de funcionamento da política de envio, ou seja, os horários em que ela aceita o recebimento do pedido. Para configurar selecione a janela `Período de envio` :
-        *   `Aceitar compras fora do horário de funcionamento`: ativa ou inativa o recebimento de compras fora do horário de funcionamento. Quando ativo, o intervalo de tempo do momento do pedido até o início horário, será somado ao tempo total da entrega.
-        *   Selecione o `Dia da semana`, e preencha `Horário de início` e `Horário de fim`.
-        *   Para adicionar mais dias da semana, clique em `Adicionar período de envio`.
-    *   **Horário de coleta:** é onde você cadastra os horários em que a política de envio coleta pacotes em seu estoque ou centro de distribuição, para em seguida enviá-los aos clientes finais. Caso o pedido seja feito antes do início do horário de coleta, nenhum tempo será adicionado ao tempo total da entrega. No entanto, se ele for feito após o horário de coleta, o intervalo de tempo do momento do pedido até o início horário, será somado ao tempo total da entrega.
-        *   Selecione o `Dia da semana` e preencha o `Horário da coleta`. 
-        *   Para adicionar mais dias da semana, clique em `Adicionar período de coleta`.
-*   **[Entrega agendada:](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)** essa funcionalidade pode ser habilitada caso a política de envio ofereça o serviço de entrega agendada. É aqui que você deverá adicionar as janelas de entrega que ficarão disponíveis para o cliente ao final da compra. Para utilizar, habilite `entrega agendada` e preencha:
-    *   **Tempo máximo de entrega:** define o tempo máximo de entrega, deve ser preenchido com o tempo em dias.
-    *   **Período de entrega:** define as janelas de entrega que a política de entrega realiza. Você deve adicionar os dias da semana, horários de `Início` e `Fim` da janela de entrega, e valor adicional. Clique em `Adicionar novo período de entrega` para adicionar mais janelas de entrega. 
-    *   **Capacidade de entrega:** permite limitar quantos itens/pedidos podem ser entregues para cada janela de entrega. Essa funcionalidade pode ser habilitada, ou não. O uso ou não dessa funcionalidade não interfere no funcionamento da plataforma. Para saber mais sobre esses recursos consulte a [Entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) e [Gerenciar capacidade de entrega](https://help.vtex.com/pt/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz). Caso seja habilitada você deve:
-        *   Escolher a unidade da capacidade de entrega entre `itens` e `pedidos`.
-        *   Conferir as janelas de entrega.
-        *   Definir o número da capacidade de entrega. Recomendamos cuidado especial ao escolher a unidade e a quantidade da capacidade de entrega, pois o sistema não calcula a disponibilidade da `capacidade de entrega` levando em conta a quantidade de itens sendo comprada. Então, se a janela de entregas ainda tiver capacidade para 2 itens e seu cliente estiver comprando 4 itens, ele ainda terá a opção de selecionar a janela de entrega disponível.
+Para saber como criar uma política de envio, veja o artigo [Criar uma política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT). Para informações sobre gerenciamento, confira o artigo [Gerenciar políticas de envio](https://help.vtex.com/pt/tutorial/gerenciar-politicas-de-envio--30nynylgbWieimhaMtGTIE).
 
-            É importante lembrar que as janelas de entrega deixam de ficar disponíveis aos clientes caso já tenham atingido o limite da `capacidade de entrega`. Para que uma janela fique novamente disponível aos clientes, é preciso aumentar a quantidade de itens/pedidos da capacidade de entrega da janela. 
+## Política de envio e planilha de frete
 
-## Editar uma política de envio
+Toda política de envio está associada a uma [planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127), que é onde você cadastra informações como:
 
-1. No Admin VTEX, acesse **Envio > Estratégia de Envio > Políticas de Envio** ou digite *Estratégia de envio* na barra de busca no topo da página.
-2. Clique na `política de envio` que deseja alterar.
-3. Altere `os campos de` [Cadastrar políticas de envio](#cadastrar-uma-politica-de-envio) e salve.
+* Identificação da transportadora
+* Valor de envio cobrado pela transportadora
+* Intervalos de código postal ou [polígonos](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138) válidos para envios
 
-## Excluir uma política de envio
+Uma vez que a planilha de frete é associada à política de envio, essas informações passam a fazer parte da sua operação logística na VTEX.
+
+## Primeiras configurações logísticas
+
+As configurações podem ser realizadas pelo Admin VTEX ou por API. Se você está começando a configurar sua [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), a ordem de cadastro sugerida é a seguinte:
+
+| **Assunto** | **Configuração via Admin VTEX** | **Configuração via API** |
+| :--- | :--- | :--- |
+| 1. Política de envio | [Criar uma política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| 2. [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) | [Gerenciar estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| 3. [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) | [Gerenciar doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
 
-1. No Admin VTEX, acesse **Envio > Estratégia de Envio > Políticas de Envio** ou digite *Estratégia de envio* na barra de busca no topo da página.
-2. Passe o mouse sobre a política de envio que deseja excluir.
-3. Clique no ícone de lixeira.
-4. Clique no botão `Deletar`.
diff --git a/docs/tutorials/pt/shipping-rate-template.md b/docs/tutorials/pt/shipping-rate-template.md
index d672d91b7..b763bc50d 100644
--- a/docs/tutorials/pt/shipping-rate-template.md
+++ b/docs/tutorials/pt/shipping-rate-template.md
@@ -3,8 +3,8 @@ title: 'Planilha de frete'
 id: tutorials_127
 status: PUBLISHED
 createdAt: 2019-02-22T19:36:18.509Z
-updatedAt: 2023-03-29T18:18:59.537Z
-publishedAt: 2023-03-29T18:18:59.537Z
+updatedAt: 2023-10-10T13:26:19.271Z
+publishedAt: 2023-10-10T13:26:19.271Z
 firstPublishedAt: 2019-02-22T19:36:22.375Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -121,7 +121,7 @@ Confira a tabela a seguir para entender cada campo detalhadamente.
             <td class="t-body pa5" style="min-width: 15rem;">
                 <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">PricePercent</span>
             </td>
-            <td class="t-body pa5" style="min-width: 15rem;"><a href="https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">Adicional por preço,</a> calculado de acordo com o preço do carrinho, em número decimal. Para o preenchimento da tabela utilize o valor em porcentagem (por exemplo para um adicional de 10% preencha a tabela com 10).
+            <td class="t-body pa5" style="min-width: 15rem;"><a href="https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">Adicional por preço,</a> calculado em número decimal de acordo com o preço dos produtos no carrinho. Para o preenchimento da tabela, utilize o valor em porcentagem. Por exemplo: para um adicional de 10% preencha a tabela com 10.
             </td>
             <td class="t-body pa5" style="min-width: 15rem;"> Utilize o campo nos casos em que exista um adicional de preço para a entrega. Os <a href="https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">adicionais de frete</a> são somados ao valor fixo.
             </td>
@@ -181,11 +181,7 @@ Para fins de usabilidade de termos, utilizamos em nossa documentação o termo "
 
 Veja abaixo um exemplo de preenchimento dos campos, considerando o formato aceito em cada coluna. 
 
-![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
-
-### Planilha para os Correios
-
-Caso queira disponibilizar a entrega pelos Correios, é possível gerar uma planilha automática no padrão VTEX. Acesse o integrador Correios, e gere a planilha pela ferramenta oferecida pela XP Agência no link [XP planilhas](http://planilha.xpagencia.com.br/).
+![modelo_planilhanumerica](//images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
 
 ## Enviar o arquivo pelo Admin VTEX
 
diff --git a/docs/tutorials/pt/shipping-rates.md b/docs/tutorials/pt/shipping-rates.md
index 49b136f27..cdffc8a3c 100644
--- a/docs/tutorials/pt/shipping-rates.md
+++ b/docs/tutorials/pt/shipping-rates.md
@@ -21,7 +21,7 @@ As tarifas de envio são os custos de frete que sua loja oferece aos clientes, e
 O <a href="https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV">custo final do envio</a> para o cliente inclui tarifa de envio, <a href="https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">adicionais de frete</a> e custo de doca com estoque.
 </div>
 
-![Tarifa envio PT](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
+![Tarifa envio PT](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
 
 Pelo Admin VTEX, há duas maneiras de cadastrar as tarifas de envio:
 
diff --git a/docs/tutorials/pt/shipping-simulation.md b/docs/tutorials/pt/shipping-simulation.md
index 33f7c1698..6e8504a5b 100644
--- a/docs/tutorials/pt/shipping-simulation.md
+++ b/docs/tutorials/pt/shipping-simulation.md
@@ -3,8 +3,8 @@ title: 'Simulador de envio'
 id: tutorials_144
 status: PUBLISHED
 createdAt: 2017-04-27T22:16:36.879Z
-updatedAt: 2023-03-29T19:24:17.032Z
-publishedAt: 2023-03-29T19:24:17.032Z
+updatedAt: 2024-06-18T19:48:13.737Z
+publishedAt: 2024-06-18T19:48:13.737Z
 firstPublishedAt: 2017-04-27T23:00:45.450Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -47,7 +47,7 @@ Nesse artigo contém:
  6. Selecione a `quantidade`do SKU.    
  7. Determine o `Preço`. Este campo é aberto, e opcional.  
 
-	> O simulador não leva em consideração o preço cadastrado no módulo Catálogo. Portanto, o custo indicado pelo simulador não considera qualquer promoção vigente para aqueles SKUs, podendo indicar um custo diferente do valor real na sua loja. Sugerimos que insira manualmente o valor exato do SKU já com as promoções aplicadas, para que o simulador retorne um cálculo preciso.    
+	> O simulador não leva em consideração o preço cadastrado no módulo Catálogo, portanto, ele não considera possíveis acréscimos nos valores do frete de acordo com o preço do carrinho e promoções de SKUs, o que pode resultar em um custo diferente do valor real do item na sua loja. Para que o simulador realize um cálculo preciso, sugerimos que você insira manualmente o valor final do SKU com as promoções aplicadas.  
 
  8. Clique no ícone `+` para adicionar mais de um produto na simulação. 
 Se desejar, pode preencher o box `Simular itens individualmente`.    
@@ -66,7 +66,7 @@ No resultado da simulação, as medidas dos itens aparecem em centímetros e gra
 
 ## Detalhes da Simulação
 
-A simulação de frete indica todas as possibilidades de envio e disponibilidade dos itens incluídos na simulação e descreve os [detalhes de entrega de um pedido](https://help.vtex.com/tutorial/ver-detalhes-de-entrega-de-um-pedido?locale=pt), o custo de frete e o tempo de entrega considerando as particularidades abaixo.
+A simulação de frete indica todas as possibilidades de envio e disponibilidade dos itens incluídos na simulação e descreve os [detalhes de entrega de um pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl), o custo de frete e o tempo de entrega considerando as particularidades abaixo.
 
 * **Transportadoras desconsideradas:** ao realizar a simulação, algumas transportadoras podem estar indisponíveis por não atenderem os critérios da [ Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) (veja [transportadoras desconsideradas](#transportadoras-desconsideradas) para mais informações).
 * **Compartilhamento de simulação**: é possível o compartilhamento da simulação clicando em `compartilhar a simulação` no canto superior direito da página em. Ao clicar, um link de compartilhamento é copiado para a sua área de transferência. Essa funcionalidade facilita o acionamento da equipe VTEX, ou da sua loja, para resolver problemas em pedidos específicos. Somente quem tem acesso ao ambiente VTEX consegue visualizar o link gerado pelo compartilhamento.
diff --git a/docs/tutorials/pt/shipping-strategy.md b/docs/tutorials/pt/shipping-strategy.md
index 63e4053a4..5be66fc10 100644
--- a/docs/tutorials/pt/shipping-strategy.md
+++ b/docs/tutorials/pt/shipping-strategy.md
@@ -1,10 +1,10 @@
 ---
-title: 'Estratégia de Envio'
+title: 'Estratégia de envio'
 id: 58vLBDbjYVQzJ6rRc5QNz3
 status: PUBLISHED
 createdAt: 2021-07-15T17:04:23.563Z
-updatedAt: 2021-09-23T22:21:40.782Z
-publishedAt: 2021-09-23T22:21:40.782Z
+updatedAt: 2024-01-31T15:00:05.216Z
+publishedAt: 2024-01-31T15:00:05.216Z
 firstPublishedAt: 2021-07-15T17:27:37.590Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Estratégia de envio é a relação entre estoque, doca e política de envio. A forma que   estoque, doca e política de envio se comunicam definirá a combinação de estrutura para entrega dos pedidos da loja.
 
-![EstrategiaEnvio](//images.contentful.com/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/02cad4cbd4829e774e2b51474e4675cf/Frame_2__1_.svg)
+![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
    <tr class="bb b--muted-3">
@@ -43,14 +43,13 @@ Estratégia de envio é a relação entre estoque, doca e política de envio. A
     </tr>
 </table>
 
-<div class="alert alert-warning">
-A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de Envio;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">Doca;</a></li>
-<li><a href="https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137">Estoque.</a></li>
-</ol>
-</body>
-</div>
+## Primeiras configurações logísticas
+
+As configurações podem ser realizadas pelo Admin VTEX ou por API. Se você está começando a configurar sua estratégia de envio, a ordem de cadastro sugerida é a seguinte:
+
+| **Assunto** | **Configuração via Admin VTEX** | **Configuração via API** |
+| :--- | :--- | :--- |
+| 1. [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) | [Criar uma política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT) | [Create shipping policy](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/shipping-policies) |
+| 2. [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) | [Gerenciar estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137) | [Create/update warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/warehouses) |
+| 3. [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) | [Gerenciar doca](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) | [Create/update dock](https://developers.vtex.com/docs/api-reference/logistics-api#post-/api/logistics/pvt/configuration/docks) |
+
diff --git a/docs/tutorials/pt/shopee-integration.md b/docs/tutorials/pt/shopee-integration.md
index 1fe0d4c8b..93f7b5332 100644
--- a/docs/tutorials/pt/shopee-integration.md
+++ b/docs/tutorials/pt/shopee-integration.md
@@ -3,8 +3,8 @@ title: 'Integração com a Shopee '
 id: 5OV9idUY6fHu3P8grnCnqj
 status: PUBLISHED
 createdAt: 2022-09-05T19:33:02.717Z
-updatedAt: 2022-12-08T20:41:49.398Z
-publishedAt: 2022-12-08T20:41:49.398Z
+updatedAt: 2024-04-17T16:10:43.661Z
+publishedAt: 2024-04-17T16:10:43.661Z
 firstPublishedAt: 2022-09-06T01:42:40.106Z
 contentType: tutorial
 productTeam: Channels
@@ -15,10 +15,6 @@ legacySlug: integracao-com-a-shopee-beta
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class = "alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. A integração com a Shopee está disponível apenas para lojas no Brasil.
-</div>
-
 A [Shopee](https://shopee.com.br/) é uma plataforma de ecommerce que funciona como marketplace. A plataforma conta com um grande catálogo de produtos que podem ser consultados pelo site oficial ou pelo aplicativo, além de mais de 43 milhões de usuários cadastrados.
 
 Através da integração entre a VTEX e a Shopee, você poderá utilizar a Shopee como canal de vendas.
@@ -88,9 +84,13 @@ Depois de ter feito as pré-configurações da sua loja VTEX, você poderá inst
 
 No final da instalação, o app estará disponível no seu Admin VTEX.
 
+<div class="alert alert-info">
+O acesso ao aplicativo da Shopee pode ser realizado seguindo as instruções acima ou através do caminho <b>Admin VTEX > Marketplace > Marketplaces e integrações.</b>
+</div>
+
 ## Configurações Shopee
 
-Depois de instalar o aplicativo, é necessário configurá-lo no Admin VTEX. Acesse *MARKETPLACE > Shopee > Configurações*.
+Depois de instalar o aplicativo, é necessário configurá-lo no Admin VTEX. Acesse **Apps > Shopee > Configurações,** ou digite **Shopee** na barra de busca do Admin.
 
 A página **Configurações Shopee** possui duas abas:
 
@@ -148,7 +148,7 @@ Os Serviços ERP disponibilizam um endpoint para obter o arquivo da etiqueta de
 5. Com a chave de acesso em maõs, faça uma requisição GET no seu provedor com o endpoint do campo `Endpoint`, substituindo `{vtex_order_id}` pelo ID do pedido na VTEX e utilizando no Header a chave de acesso obtida.
 6. Na resposta dessa requisição, no campo `base64Encoded` a etiqueta será disponibilizada no formato base64.
 
-  ![postman etiquetas shopee](https://images.ctfassets.net/alneenqid6w5/fXwvkIp7rguIH22t04rAy/de4a888cd831e0f60917c30f23fb5602/postman_etiquetas_shopee.png)
+  ![postman etiquetas shopee](//images.ctfassets.net/alneenqid6w5/fXwvkIp7rguIH22t04rAy/de4a888cd831e0f60917c30f23fb5602/postman_etiquetas_shopee.png)
 
 7. Selecione o arquivo no campo `base64Encoded`, copie e use um decodificador de arquivos formato base64 para fazer a conversão no formato do arquivo selecionado no campo `Tipo de etiqueta de envio`.
 8. No final da conversão, a etiqueta estará pronta para ser utilizada.
@@ -192,68 +192,55 @@ Seus produtos precisam ter o <a href="https://help.vtex.com/pt/tutorial/estoque-
 
 ### Mapear categorias
 
-Para acessar a página de mapeamento, você deverá acessar no Admin *MARKETPLACE > Shopee > Mapeamento de categorias*.
+Para acessar a página de mapeamento, você deverá acessar no Admin VTEX em **Apps > Shopee > Mapear Categorias.**
 
 Você será direcionado a página de mapeamento da Shopee e a página apresentará uma lista com as categorias da sua loja VTEX. O mapeamento das categorias permite que exista uma correspondência entre as categorias da sua loja e as categorias da Shopee. Dessa forma, os produtos enviados serão exibidos na categoria equivalente no marketplace.
 
 Na página de mapeamento, existe uma barra de busca que permite buscar a categoria por nome. Além disso, a seção **Categorias da loja** exibe lista das categorias da sua loja VTEX. 
 
+<div class="alert alert-info">
+  A Shopee exige uma especificação para diferenciar um SKU do outro. Caso não haja especificação mapeada em seu produto, a integração utilizará o nome do SKU para criar essa especificação.
+  </div>
+
 A lista de categorias da sua loja VTEX inclui o status de seu  mapeamento  por meio dos ícones:
 
 | **Ícone** | **Status** | **Descrição** |
 | ---------- | ---------- | ---------- | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado**| Indica que o mapeamento da categoria foi concluído. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6v4eFsWHVy8F5VIqTVLQD9/e63d945d60a958a37246f57d919eede8/mapeamentoincompleto_mapper.JPG" /> | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto.  Para solucionar esse problema basta refazer o mapeamento da categoria. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado** | Indica que a categoria não foi mapeada. |
-
-Ainda na página de mapeamento, existem as seções **Categoria do marketplace** e **Mapeamento de Atributos**, ambos com uma opção de menu de seleção, onde ao clicar sobre a seta, aparecem novos campos e informações.
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Mapeado**| Indica que o mapeamento da categoria foi concluído. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6v4eFsWHVy8F5VIqTVLQD9/e63d945d60a958a37246f57d919eede8/mapeamentoincompleto_mapper.JPG" /> | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto.  Para solucionar esse problema basta refazer o mapeamento da categoria. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado** | Indica que a categoria não foi mapeada. |
 
-Para realizar o mapeamento de categorias:
-
-1. Acesse o Admin VTEX.
-2. Em *MARKETPLACE*, selecione a opção **Shopee**.
-3. Clique em `Mapeamento de categorias`.
-> Uma nova janela será aberta com a página de mapeamento.
-4. Na seção **Categorias da loja**, escolha a categoria que deseja mapear. 
-5. Selecione na seção **Categoria do marketplace** a categoria correspondente no marketplace do produto que você deseja enviar.
-
-Para finalizar o mapeamento da categoria, siga as instruções abaixo a partir do passo 4 para finalizar.
+Ainda na página de mapeamento, existem as seções, **Categoria do marketplace** e **[Mapeamento de Atributos](#mapear-atributos)**, ambos com uma opção de menu de seleção, onde ao clicar sobre a seta, aparecem novos campos e informações.
 
 ### Mapear atributos
 
-O mapeamento dos atributos permite que exista uma correspondência entre o padrão da sua loja VTEX e o padrão utilizado pela Shopee. Cada categoria possui seus atributos obrigatórios pelo marketplace e é necessário preenchê-los para que o mapeamento seja concluído. 
+O mapeamento dos atributos permite que exista uma correspondência entre o padrão da sua loja VTEX e o padrão utilizado pela Shopee. Cada categoria possui seus atributos obrigatórios pelo marketplace e é necessário preenchê-los para que o mapeamento seja concluído.
 
-Os campos não mapeados não impedem que o mapeamento ocorra, porém quanto mais atributos enviados para a Shopee seu produto tiver, melhor rankeado ele será no marketplace.
-
-<div class = "alert alert-info">
-A Shopee exige uma especificação para diferenciar um SKU do outro. Caso não haja especificação mapeada em seu produto, a integração utilizará o nome do SKU para criar essa especificação.
-</div>
+Os campos não mapeados não impedem que o mapeamento ocorra, porém, quanto mais atributos enviados para a Shopee seu produto tiver, melhor rankeado ele será no marketplace.
 
 <div class="alert alert-warning">
-A Shopee só aceita marcas já registradas no seu catálogo de produtos. Quando não houver uma marca cadastrada no produto ou a marca cadastrada no produto não corresponder aos nomes aceitos pelo marketplace, ele será categorizado na Shopee como <code>NoBrand</code>.
+A descrição dos produtos precisa ter, no mínimo, 100 caracteres. Além disso, a Shopee não aceita produtos com menos de 100 gramas, assim como não é possível enviar produtos com dimensões inválidas. Exemplo: Altura = 0 cm , Largura = 0,000001 cm. Em caso de dúvida, acesse o artigo <a href="https://seller.shopee.com.br/edu/article/3305/dimensoes-e-pesos-permitidos-para-enviar-pacotes-na-shopee">Dimensões e pesos permitidos para enviar pacotes da Shopee</a>.
 </div>
 
-Para mapear os atributos, siga os passos abaixo:
+Para realizar o mapeamento de categorias e atributos no Admin VTEX vá em **Apps > Shopee > Mapeamento de categorias** e siga os passos abaixo:
 
-1. Acesse o Admin VTEX.
-2. No módulo MARKETPLACE, selecione a opção **Shopee**.
-3. Clique em `Mapeamento de categorias`.
-> Uma nova janela será aberta com a interface de mapeamento.
-4. Na seção **Mapeamento de Atributos**, preencha os campos com os atributos que deseja mapear (o asterisco indica preenchimento obrigatório).
-5. Caso tenha preenchido os atributos *Cor* ou *Tamanho*, na coluna **Valores de Atributo** clique na `Cor equivalente` ou `Tamanho equivalente` e selecione a opção de valor correspondente.
-6. Se desejar personalizar um atributo, clique no botão `Adicionar valor personalizado` e crie um nome para o valor do atributo personalizado.
-7. Clique em `Salvar Alterações`.
+1. Na seção __Categorias da loja__, escolha a categoria que deseja mapear.
+2. Na seção __Categoria do marketplace,__ selecione a categoria correspondente no marketplace do produto que você deseja enviar.
+3. Preencha os campos dos atributos que deseja mapear (o asterisco indica preenchimento obrigatório).
+4. Caso tenha preenchido os atributos **Cor** ou **Tamanho**, na coluna **Valores de Atributo** clique na Cor equivalente ou Tamanho equivalente e selecione a opção de valor correspondente.
+5. Se desejar personalizar um atributo, clique no botão Adicionar valor personalizado e crie um nome para o valor do atributo personalizado.
+6. Clique em `Salvar Alterações`.
 
 Ao finalizar o mapeamento de categorias e atributos corretamente, o status da categoria mudará para **Mapeado**.
 
 <div class="alert alert-warning">
-A descrição dos produtos precisa ter, no mínimo, 100 caracteres. Além disso, a Shopee não aceita produtos com menos de 100 gramas, assim como não é possível enviar produtos com dimensões inválidas. Exemplo: Altura = 0 cm , Largura = 0,000001 cm. Em caso de dúvida, acesse o artigo <a href="https://seller.shopee.com.br/edu/article/3305/dimensoes-e-pesos-permitidos-para-enviar-pacotes-na-shopee">Dimensões e pesos permitidos para enviar pacotes da Shopee</a>.
+A Shopee só aceita marcas já registradas no seu catálogo de produtos. Quando não houver uma marca cadastrada no produto ou a marca cadastrada no produto não corresponder aos nomes aceitos pelo marketplace, ele será categorizado na Shopee como `NoBrand`.
 </div>
 
 ## Gerenciar produtos
 
-Para acessar a página de gerenciamento, você deverá acessar no Admin *MARKETPLACE > Shopee > Gerenciar produtos*. 
+Para acessar a página de gerenciamento, você deverá acessar no Admin **Apps > Shopee > Gerenciar produtos**. 
 
 Você será direcionado a página de gerenciamento de produtos da Shopee e a página apresentará uma lista com os produtos da sua loja VTEX. O gerenciamento de produtos permite inserir políticas comerciais diretamente em produtos do catálogo VTEX antes de serem importados para a plataforma da Shopee. 
 
@@ -271,8 +258,7 @@ A interface está dividida em três seções, são elas:
 
 Para enviar seus produtos para a Shoope, siga os passos a seguir:
 
-1. Acesse no Admin VTEX.
-2. Em *MARKETPLACE*, selecione a opção **Shopee**.
+1.Acesse no **Admin VTEX > Apps > Shopee.**
 3. Clique em **Gerenciar Produtos**.
 4. Selecione o produto que deseja importar.
 5. Clique em `Importar produto`.
@@ -283,8 +269,7 @@ Ao finalizar a importação, o processo de envio de produtos pode demorar um pou
 
 Para excluir seus produtos da Shoope, siga os passos a seguir:
 
-1. Acesse no Admin VTEX.
-2. Em *MARKETPLACE*, selecione a opção **Shopee**.
+1. Acesse no **Admin VTEX > Apps > Shopee**.
 3. Clique em **Gerenciar Produtos**.
 4. Selecione o produto que deseja excluir.
 5. Clique em `Remover produto`.
@@ -295,11 +280,11 @@ A lista de status da sincronização das categorias da sua loja VTEX que foram i
 
 | **Ícone** | **Status** | **Descrição** |
 | ---------- | ---------- | ---------- | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Processed**| Indica que o mapeamento da categoria foi concluído. | 
-| <img class="shadow-4" src="https:https://images.ctfassets.net/alneenqid6w5/2sMPoDbIM0AzJrnpHTCaGB/6ad0cfe1b76db6fe18339ea6f3194feb/status_erro_importacaoshopee.JPG" /> | **Erro** | Indica que a importação da categoria não foi concluída. O motivo do erro será informado para que a correção possa ser realizada. |
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/6Ry65cPvgGmChmE3RipFio/deec73c3e429f63dfa8971ae8c848221/mapeado_mapper.JPG" /> | **Processed**| Indica que o mapeamento da categoria foi concluído. | 
+| <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2sMPoDbIM0AzJrnpHTCaGB/6ad0cfe1b76db6fe18339ea6f3194feb/status_erro_importacaoshopee.JPG" /> | **Erro** | Indica que a importação da categoria não foi concluída. O motivo do erro será informado para que a correção possa ser realizada. |
 
 ## Gerenciamento de pedidos da Shopee na plataforma VTEX
 
 O pedido da Shopee só é criado na VTEX quando o [status do pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#tabela-de-status-de-pedidos) é `Pagamento Aprovado`. Entretanto, a integração já reserva o estoque do produto antes do pagamento. Quando o pagamento é confirmado, a reserva é cancelada e o pedido é criado na VTEX.
 
-Para liberar as etiquetas de envio, a Shopee exige que seja feito o faturamento do pedido e a emissão da Nota fiscal do produto. Para isso, você pode utilizar seu [ERP](https://developers.vtex.com/vtex-rest-api/reference/invoicenotification) ou [inserir a nota fiscal no pedido](https://help.vtex.com/pt/tutorial/como-inserir-a-nota-fiscal--tutorials_193), enviando o campo `invoiceKey (Chave da Nota Fiscal)` preenchido com a chave de acesso da NF-e.
+Para liberar as etiquetas de envio, a Shopee exige que seja feito o faturamento do pedido e a emissão da Nota fiscal do produto. Para isso, você pode utilizar seu [ERP](https://developers.vtex.com/vtex-rest-api/reference/invoicenotification) ou [inserir a nota fiscal no pedido](https://help.vtex.com/pt/tutorial/como-inserir-a-nota-fiscal--tutorials_193), enviando o campo `invoiceKey (Chave da Nota Fiscal)` preenchido com a chave de acesso da NF-e e o preenchimento obrigatório do campo `embeddedInvoice` com o XML da nota fiscal.
diff --git a/docs/tutorials/pt/shopify-suiteshare.md b/docs/tutorials/pt/shopify-suiteshare.md
index 6741e3fd3..83fe74320 100644
--- a/docs/tutorials/pt/shopify-suiteshare.md
+++ b/docs/tutorials/pt/shopify-suiteshare.md
@@ -21,7 +21,7 @@ Para localizar o script da Suiteshare, acesse **Configurações** no canto supe
 
 Com o script da Suiteshare em mãos, acesse em sua conta Shopify o menu localizado no canto inferior esquerdo **My Store**, depois em **Themes**, clique em **Edit HTML/CSS** conforme a imagem abaixo:
 
-![Shopify - Suiteshare](https://images.ctfassets.net/alneenqid6w5/45EPnxpruUgUqIUl9cDR3t/894418df9be3fab2755c2f895fc9145e/Shopify_-_Suiteshare.png)
+![Shopify - Suiteshare](//images.ctfassets.net/alneenqid6w5/45EPnxpruUgUqIUl9cDR3t/894418df9be3fab2755c2f895fc9145e/Shopify_-_Suiteshare.png)
 
 O próximo passo é acessar no canto esquerdo **Layout**, a opção **Theme Liquid**.
 
diff --git a/docs/tutorials/pt/site-editor-overview.md b/docs/tutorials/pt/site-editor-overview.md
index 277151a4d..44c7b556e 100644
--- a/docs/tutorials/pt/site-editor-overview.md
+++ b/docs/tutorials/pt/site-editor-overview.md
@@ -23,7 +23,7 @@ Site Editor é uma interface gráfica de gerenciamento de conteúdo da sua frent
 
 No Admin VTEX, acesse **Storefront > Site Editor** e confira as principais ferramentas disponíveis na interface gráfica.
 
-![Site Editor - PT](https://images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/e526abc990cdf0bfa1d451580e7a8ec2/site-editor-ui-pt.png)
+![Site Editor - PT](//images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/e526abc990cdf0bfa1d451580e7a8ec2/site-editor-ui-pt.png)
 
 | **Ferramenta**    | **Descrição** |
 | ----------        | ----------    |
diff --git a/docs/tutorials/pt/sku-bindings.md b/docs/tutorials/pt/sku-bindings.md
index ffa0fbdd3..ae5e5fad0 100644
--- a/docs/tutorials/pt/sku-bindings.md
+++ b/docs/tutorials/pt/sku-bindings.md
@@ -1,10 +1,10 @@
 ---
 title: 'Vínculos de SKU'
 id: 1SmrVgNwjJX17hdqwLa0TX
-status: CHANGED
+status: PUBLISHED
 createdAt: 2022-05-27T17:27:26.963Z
-updatedAt: 2023-05-25T15:51:50.053Z
-publishedAt: 2023-03-31T19:05:52.334Z
+updatedAt: 2024-01-23T15:50:13.022Z
+publishedAt: 2024-01-23T15:50:13.022Z
 firstPublishedAt: 2022-05-31T17:14:23.589Z
 contentType: tutorial
 productTeam: Channels
@@ -27,7 +27,7 @@ Por padrão, para <a href="https://help.vtex.com/pt/tutorial/seller-white-label-
 
 A página **Vínculos de SKU** permite ao marketplace acompanhar e gerenciar a relação de vínculo entre os SKUs do seller e do marketplace. Para acessar a página, no Admin VTEX vá em **Marketplace > Sellers > Vínculos de SKU**. A seguinte interface vai aparecer:
 
-![sku-bindings-pt](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/f226cc707a595197ffa86fcb68db212b/sku-bindings-pt.png)
+![sku-bindings-pt](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/f226cc707a595197ffa86fcb68db212b/sku-bindings-pt.png)
 
 A tabela a seguir apresenta a descrição das colunas da listagem de vínculos de SKUs:
 
diff --git a/docs/tutorials/pt/sku-price-change.md b/docs/tutorials/pt/sku-price-change.md
index 8c1537093..f445fd4bf 100644
--- a/docs/tutorials/pt/sku-price-change.md
+++ b/docs/tutorials/pt/sku-price-change.md
@@ -3,8 +3,8 @@ title: 'Alterar preço de SKU'
 id: tutorials_95
 status: PUBLISHED
 createdAt: 2017-04-27T22:19:48.759Z
-updatedAt: 2023-03-30T16:36:10.950Z
-publishedAt: 2023-03-30T16:36:10.950Z
+updatedAt: 2024-01-05T17:59:41.793Z
+publishedAt: 2024-01-05T17:59:41.793Z
 firstPublishedAt: 2017-04-27T23:00:42.506Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -41,8 +41,8 @@ Essa atualização normalmente é feita quando precisa ser feito um rápido ajus
 
 Esses campos representam as informações que são alteradas em qualquer uma das três maneiras mencionadas. A diferença é que manualmente, quem está preenchendo enxerga esse formulário, via importação por planilha estão dispostos em colunas e via integração são campos na estrutura de request em formato JSon.
 
-- **ID:** código do SKU que acessou
-- **Sku:** nome do SKU
+- **ID:** código do SKU que acessou.
+- **Sku:** nome do SKU.
 - **Parceiro (utm\_source):** Campo opcional. Trata-se de um parâmetro para condicionar uma precificação diferenciada, a partir do uso no site da utm source que for cadastrada aqui.
 - **Audiência de campanha (utm\_campaign):** Campo opcional. Trata-se de um parâmetro para condicionar uma precificação diferenciada, a partir do uso no site da utm campaign que for cadastrada aqui, a qual também pode ser usada em links de mail marketing.
 - **Audiência de campanha interna (utmi\_cp):** Campo opcional. Trata-se de um parâmetro para condicionar uma precificação diferenciada, a partir do uso no site da utm source que for cadastrada aqui. Normalmente usada para funcionários da loja, quando é o caso de ter condições de compra diferenciada.
@@ -66,36 +66,33 @@ Essa ferramenta normalmente é usada para atualização de preços em massa, que
 
 Depois que o e-mail chegar e fizer o download, altere somente aqueles SKUs que realmente precisarão serem atualizados, os demais pode excluir da planilha, assim a importação levará menos tempo e evitará reindexação desnecessária dos produtos que não foram alterados. É importante ressaltar que o formato aceito pela plataforma para importar a planilha é o .xls. Levando em consideração que não fechou a página do Admin, continue com os passos abaixo:
 
-1. Selecione a aba **Importar**
-2. Clique em **Selecionar arquivo**
-3. Busque pelo arquivo que salvou em sua máquina com os preços alterados;
-4. Selecione o arquivo e clique em **Abrir**
-5. Preencha em **Email para notificação** o seu e-mail, para ser notificado quanto a possíveis erros na importação (preenchimento, formato da planilha, etc);
+1. Selecione a aba **Importar**.
+2. Clique em **Selecionar arquivo**.
+3. Busque pelo arquivo que salvou em sua máquina com os preços alterados.
+4. Selecione o arquivo e clique em **Abrir**.
+5. Preencha em **Email para notificação** o seu e-mail, para ser notificado quanto a possíveis erros na importação (preenchimento, formato da planilha, etc).
 6. Clique no botão **Importar**.
-7. Colunas da planilha de importação
+7. Colunas da planilha de importação.
 
 Essas são as colunas da planilha que chega no e-mail do usuário, quando faz a exportação conforme mencionado no passo a passo acima. Abaixo está escrito exatamente como está na planilha. A obrigatoriedade de preenchimento de cada coluna, segue o mesmo padrão dos campos do formulário descrito no referido tópico acima.
 
-- **StockKeepingUnitId:** ID do SKU;
-- **Source: **utm\_source;
-- **Price:** preço de venda do produto;
-- **Id:** ID do preço. Não altere esse valor, caso contrário o sistema criará uma nova linha na tabela de preço e ficarão dois preços cadastrados para o SKU;
-- **StoreId:** ID da política comercial onde o preço será aplicado. Caso tenha dúvida de qual é o código de identificação de alguma política, acesse o módulo Catalog > Marketplace > Política Comercial. Verifique o número que aparece na coluna **Id - Nome**. Esse é o código que deverá ser usado aqui;
-- **Medium (Desconsiderar):** Campo descontinuado;
-- **Campaign:** utm\_campaign;
-- **InternalCampaign:** utmi\_cp;
-- **DateFrom: **data do início da vigência do preço. Preencher no formato dd/mm/aaaa;
-- **DateTo: **data do fim da vigência do preço. Preencher no formato dd/mm/aaaa;
-- **ListPrice: **preço de, também conhecido como preço de lista. É aquele que aparece tachado (ex: `De: R$ 10,00`) no site;
-- **RefId (Não alterável): **código de referência de produto, conforme cadastro do produto. Não alterar esse valor;
-- **Ean13Default (Não alterável):** EAN do produto, conforme cadastro do produto. Não alterar esse valor;
-- **BrandName (Não alterável):** marca do produto, conforme cadastro do produto. Não alterar esse valor;
-- **StockKeepingUnitName (Não alterável):** nome do SKU, conforme cadastro do produto. Não alterar esse valor;
+- **StockKeepingUnitId:** ID do SKU.
+- **Source: **utm\_source.
+- **Price:** preço de venda do produto.
+- **Id:** ID do preço. Não altere esse valor, caso contrário o sistema criará uma nova linha na tabela de preço e ficarão dois preços cadastrados para o SKU.
+- **StoreId:** ID da política comercial onde o preço será aplicado. Caso tenha dúvida de qual é o código de identificação de alguma política, acesse o módulo Catalog > Marketplace > Política Comercial. Verifique o número que aparece na coluna **Id - Nome**. Esse é o código que deverá ser usado aqui.
+- **Medium (Desconsiderar):** Campo descontinuado.
+- **Campaign:** utm\_campaign.
+- **InternalCampaign:** utmi\_cp.
+- **DateFrom: **data do início da vigência do preço. Preencher no formato dd/mm/aaaa.
+- **DateTo: **data do fim da vigência do preço. Preencher no formato dd/mm/aaaa.
+- **ListPrice: **preço de, também conhecido como preço de lista. É aquele que aparece tachado (ex: `De: R$ 10,00`) no site.
+- **RefId (Não alterável): **código de referência de produto, conforme cadastro do produto. Não alterar esse valor.
+- **Ean13Default (Não alterável):** EAN do produto, conforme cadastro do produto. Não alterar esse valor.
+- **BrandName (Não alterável):** marca do produto, conforme cadastro do produto. Não alterar esse valor.
+- **StockKeepingUnitName (Não alterável):** nome do SKU, conforme cadastro do produto. Não alterar esse valor.
 - **SellerId:** ID do seller dono do produto. Somente virá preenchido caso sua loja seja marketplace de outra loja.
 
 ## Por integração com ERP
 
-Normalmente é configurada no momento que a sua loja está sendo implantada e, deve ser seguido o manual de integração junto à sua equipe técnica, para evitar integrações inconsistentes ou qualquer problema que possa prejudicar a informação que alimentará a plataforma. A atualização de preço é feito via REST, através de método POST com body no padrão JSON.
-
-Veja a documentação da API em nossos Developer Docs:
-https://developers.vtex.com/reference/pricing-api-overview#listorders
+Normalmente é configurada no momento que a sua loja está sendo implantada e, deve ser seguido o manual de integração junto à sua equipe técnica, para evitar integrações inconsistentes ou qualquer problema que possa prejudicar a informação que alimentará a plataforma. A atualização de preço é feito via API, para obter informações, acesse [Pricing API](https://developers.vtex.com/docs/api-reference/pricing-api#overview).
diff --git a/docs/tutorials/pt/sku-registration-fields.md b/docs/tutorials/pt/sku-registration-fields.md
index f9921cb3f..15124b1ab 100644
--- a/docs/tutorials/pt/sku-registration-fields.md
+++ b/docs/tutorials/pt/sku-registration-fields.md
@@ -3,8 +3,8 @@ title: 'Preencher campos de cadastro de SKU'
 id: 21DDItuEQc6mseiW8EakcY
 status: PUBLISHED
 createdAt: 2017-09-22T00:20:45.920Z
-updatedAt: 2022-12-19T18:03:03.864Z
-publishedAt: 2022-12-19T18:03:03.864Z
+updatedAt: 2023-07-14T20:59:40.541Z
+publishedAt: 2023-07-14T20:59:40.541Z
 firstPublishedAt: 2017-09-22T00:40:16.232Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -23,7 +23,7 @@ Para entender o significado de cada campo do cadastro de SKU, veja a descrição
 
 __Nome do produto:__ já aparece preenchido com o nome do produto ao qual o SKU irá pertencer.
 
-__Nome:__ deve conter o nome do SKU, ou seja, a variação do produto, que já foi cadastrado anteriormente. Produto - Geladeira, SKU -110 volts.
+__Nome:__ deve conter o nome do SKU, ou seja, a variação do produto, que já foi cadastrado anteriormente. Exemplo: Produto - Geladeira, SKU - 110 volts. O nome do SKU é limitado a 200 caracteres.
 
 __Valor para Fidelidade:__ crédito que o cliente recebe ao concluir uma compra de 1 unidade de um determinado SKU. Ao colocar “1,00” neste campo, o cliente ganha um crédito de R$ 1,00 no site.
 
diff --git a/docs/tutorials/pt/skus.md b/docs/tutorials/pt/skus.md
new file mode 100644
index 000000000..f24fbc53b
--- /dev/null
+++ b/docs/tutorials/pt/skus.md
@@ -0,0 +1,128 @@
+---
+title: 'SKUs Data Pipeline (Beta)'
+id: 4zkfF1asM3ayvIigsySevw
+status: DRAFT
+createdAt: 2024-02-02T18:06:58.601Z
+updatedAt: 2024-05-27T20:55:21.862Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: skus-data-pipeline-beta
+locale: pt
+legacySlug: skus-data-pipeline-beta
+subcategory: oMrzcOMVbBpH0reeMFHFg
+---
+
+# SKUs  
+
+O conjunto de dados de SKUs é composto pela tabela `products_sku`, que centraliza informações detalhadas dos produtos, incluindo identificadores, descrições, dados de marca, URLs de imagem e especificações do SKU, facilitando a gestão e análise de catálogos de produtos.
+
+Nesta seção você encontra as seguintes informações:
+
+- [Características dos dados de SKUs](#caracteristicas-dos-dados-de-skus)
+- [Tabela products_sku](#tabela-products_sku)
+- [Análise com products_sku](#analise-com-products_sku)
+- [Correlações com outros dados](#correlacoes-com-outros-dados)
+
+## Características dos dados
+
+| **Característica** | **Descrição** |
+|:---:|:---:|
+| **Origem do dado** | São originados do **Catálogo de produtos**. |
+| **Disponibilidade** | Os dados de catálogo podem ser acessados através do relatório do Admin da VTEX e também por <a href="https://developers.vtex.com/docs/api-reference/catalog-api/">APIs de catálogo</a>. |
+| **Histórico** | Os dados são mantidos por dois anos, a partir de 2024 para clientes que já utilizam a plataforma VTEX. |
+| **Menor intervalo de atualização possível** | Uma hora. |
+
+## Tabela products_sku
+
+Além das informações já citadas sobre os dados de catálogo, a tabela `products_sku` centraliza informações de identificação do produto como, descrição, marca e especificações. Conheça a seguir os campos que constituem a tabela.
+
+| **Nome da Coluna** | **Tipo de Coluna** | **Descrição da Coluna** |
+|:---:|:---:|:---:|
+| id | integer | Identificador único do produto. |
+| product_id | integer | Identificador único do produto no sistema. |
+| name_complete | character varying(255) | Nome completo do produto. |
+| complement_name | character varying(255) | Nome complementar do produto. |
+| product_name | character varying(255) | Nome do produto. |
+| product_description | character varying(1000) | Descrição detalhada do produto. |
+| sku_name | character varying(255) | Nome do SKU do produto. |
+| product_ref_id | character varying(255) | Referência externa ou interna do produto. |
+| tax_code | character varying(255) | Código fiscal associado ao produto. |
+| is_active | boolean | Indica se o produto está ativo. |
+| is_transported | boolean | Indica se o produto é transportável. |
+| is_inventoried | boolean | Indica se o produto está sujeito a inventário. |
+| is_gift_card_recharge | boolean | Indica se o produto é um recarregamento de cartão-presente. |
+| image_url | character varying(1024) | URL da imagem do produto. |
+| detail_url | character varying(1024) | URL de detalhes do produto. |
+| csc_identification | character varying(255) | Identificação CSC do produto. |
+| brand_id | character varying(255) | Identificador da marca do produto. |
+| brand_name | character varying(255) | Nome da marca do produto. |
+| is_brand_active | boolean | Indica se a marca do produto está ativa. |
+| dimension | super | Dimensões do produto. |
+| real_dimension | super | Dimensões reais do produto. |
+| manufacturer_code | character varying(255) | Código do fabricante do produto. |
+| is_kit | boolean | Indica se o produto é um kit. |
+| kit_items | super | Itens incluídos no kit do produto. |
+| services | super | Serviços associados ao produto. |
+| categories | super | Categorias às quais o produto pertence. |
+| categories_full_path | super | Caminho completo das categorias do produto. |
+| attachments | super | Anexos relacionados ao produto. |
+| collections | super | Coleções às quais o produto pertence. |
+| sku_sellers | super | Vendedores do SKU do produto. |
+| sales_channels | super | Canais de venda do produto. |
+| images | super | Imagens do produto. |
+| videos | super | Vídeos do produto. |
+| sku_specifications | super | Especificações do SKU do produto. |
+| product_specifications | super | Especificações do produto. |
+| product_clusters_ids | character varying(255) | IDs dos clusters de produtos. |
+| positions_in_clusters | super | Posições nos clusters de produtos. |
+| product_cluster_names | super | Nomes dos clusters de produtos. |
+| product_cluster_highlights | super | Destaques dos clusters de produtos. |
+| product_category_ids | character varying(255) | IDs das categorias do produto. |
+| is_direct_category_active | boolean | Indica se a categoria direta do produto está ativa. |
+| product_global_category_id | integer | ID da categoria global do produto. |
+| product_categories | super | Categorias do produto. |
+| commercial_condition_id | integer | ID da condição comercial do produto. |
+| reward_value | double precision | Valor de recompensa associado ao produto. |
+| alternate_ids | super | IDs alternativos do produto. |
+| alternate_id_values | super | Valores dos IDs alternativos do produto. |
+| estimated_date_arrival | character varying(255) | Data estimada de chegada do produto. |
+| measurement_unit | character varying(255) | Unidade de medida do produto. |
+| unit_multiplier | double precision | Multiplicador de unidade do produto. |
+| information_source | character varying(255) | Fonte de informação do produto. |
+| modal_type | character varying(255) | Tipo de modal do produto. |
+| key_words | character varying(1000) | Palavras-chave associadas ao produto. |
+| release_date | character varying(255) | Data de lançamento do produto. |
+| product_is_visible | boolean | Indica se o produto é visível. |
+| show_if_not_available | boolean | Indica se o produto deve ser mostrado mesmo se não estiver disponível. |
+| is_product_active | boolean | Indica se o produto está ativo. |
+| product_final_score | integer | Pontuação final do produto. |
+| account_name | character varying(255) | Nome da conta associada ao produto. |
+| batch_id | character varying(13) | ID de controle do lote de ingestão de dados. |
+
+## Análises com products_sku
+
+Veja abaixo algumas das diversas possibilidades de análises possíveis com a tabela de catálogo:  
+
+**- Análise de desempenho do produto:** calcule as vendas por SKU para identificar os produtos mais populares, direcionando estratégias de marketing e reabastecimento.  
+**- Tendências de categoria de produto:** agrupe SKUs por categorias para analisar as tendências de vendas em diferentes segmentos, ajustando o foco do catálogo conforme necessário.  
+**- Análise de preços e promoções:** examine os preços e as condições comerciais de cada SKU para identificar oportunidades para promoções e ajustes de preço.  
+**- Monitoramento de inventário:** verifique a disponibilidade de cada SKU em relação às tendências de vendas para gerenciar o inventário eficientemente.  
+
+## Correlações com outros dados
+
+As Correlações dos dados de catálogo com outros conjuntos de dados são cruciais para análises aprofundadas, veja alguns exemplos:
+
+**- Interação com dados de inventário:** a correlação entre os SKUs e o inventário é essencial para gerenciar as operações de venda e estoque, alinhando a disponibilidade de produtos com a demanda.  
+**- Dados de pedidos:** a análise conjunta do catálogo com os dados de pedidos revela insights sobre as preferências de compra, ajudando a otimizar o catálogo com base nas tendências de vendas.  
+**- Dados de navegação:** a interação com dados de navegação oferece uma visão sobre como os clientes exploram o catálogo, indicando quais produtos atraem mais atenção e orientando estratégias de marketing e promoção.  
+
+### Conheça outros Conjuntos de dados
+
+- [Inventário](2IvKMZV9SNrE6ipBRQr8h2)
+- [Navegação](4X4hK0zdIHN0Xn5x2MLYYd) 
+- [Pedidos](2f3GlRJ5L5IRGVIxOmzrFv)  
+- [Pagamentos](7LWkFaA1jPabzc5JAt1rGs)   
+- [Promoção](3WZ1syNucDFdvVhfKtA6Qd)
diff --git a/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md b/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
new file mode 100644
index 000000000..675904b39
--- /dev/null
+++ b/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
@@ -0,0 +1,70 @@
+---
+title: 'Características gerais do SmartCheckout™ V5'
+id: tutorials_3811
+status: PUBLISHED
+createdAt: 2017-04-27T21:51:49.943Z
+updatedAt: 2024-02-08T15:03:13.491Z
+publishedAt: 2024-02-08T15:03:13.491Z
+firstPublishedAt: 2017-04-27T23:11:15.321Z
+contentType: tutorial
+productTeam: Shopping
+author: authors_65
+slug: caracteristicas-gerais-smartcheckout-v5
+locale: pt
+legacySlug: mudando-para-nova-versao-do-smart-checkout
+subcategory: 8AGXmtpbTqUE2KQu0Swwk
+---
+
+O SmartCheckout™ V5 permite a compra sem login e senha da VTEX (one-click-buy checkout). Listamos aqui suas principais características e vantagens.
+
+### Iframe nas formas de pagamento com cartão
+
+As formas de pagamento por cartão de crédito, débito e private label (cartão emitido pelo varejista e aceito apenas dentro da sua rede de estabelecimentos) ficam isoladas em um iframe. Isso impede a customização de JavaScript, o que aumenta a segurança da sua loja. Para saber mais sobre proteção de dados, acesse [Segurança do SmartCheckout](https://help.vtex.com/pt/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB#).
+
+Note que, apesar de estar em um iframe, ainda é possível aplicar CSS normalmente no campo. Mas é importante prestar atenção no seletor CSS utilizado porque, por ser um iframe, ele deve começar com elementos que estejam dentro de `#app-container .App` sem, por exemplo, `#payment-data` ou `.payment-group` (que estão fora do iframe).
+
+Em exemplo prático, para ocultar a opção "Pagar usando dois cartões", deve ser usado apenas `.ChangeNumberOfPayments {display: none}`.
+
+![2017-06-22 162341](//images.contentful.com/alneenqid6w5/5Un86ot46Qg0kwKoUkSioG/fb3cc25e273d68ab27a3ccd2b254eea6/2017-06-22_162341.jpg)
+
+### Nova opção de cálculo de frete por geocoordenada
+
+Por meio dessa funcionalidade, é possível definir regiões de entrega usando como base um ponto geográfico (latitude e longitude) em vez de um código postal.
+
+Para saber como usar esse recurso, leia o artigo [Geolocalização no Checkout](/pt/tutorial/geolocalizacao-no-checkout/).
+
+__Atenção:__ uma vez que a API Key seja informada nas configurações do Checkout, a geolocalização já estará visível no checkout da sua loja, independente da ativação da nova versão do SmartCheckout.
+
+### Título da página
+
+O título da página do SmartCheckout™, que aparece na barra ou na aba do navegador, pode ser customizado. Para saber como fazer isso, é só seguir os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Storefront > Checkout__, ou digite __Checkout__ na barra de busca no topo da página.
+2. Clique no ícone <i class="fas fa-cog" alt="engrenagem azul"></i> do site desejado.
+3. No menu de opções azul localizado na parte superior da página, clique em __Checkout__. 
+4. No campo __Título da Página__, escreva o título desejado e verifique o resultado na caixa PRÉ-VISUALIZAÇÃO.
+5. Clique em `Salvar`.
+
+### JavaScript customizado
+
+Você pode usar os arquivos `checkout5-custom.js` e `orderplaced2-custom.js` para inserir suas customizações de JavaScript no Checkout e na tela de pedido finalizado, respectivamente. Para acessá-los, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Storefront > Checkout__, ou digite __Checkout__ na barra de busca no topo da página.
+2. Clique no ícone <i class="fas fa-cog" alt="engrenagem azul"></i> do site desejado.
+3. No menu de opções azul localizado na parte superior da página, clique em __Código__. 
+4. No menu __Arquivos__, localizado no lado direito da página, clique naqueles em que desejar realizar ajustes no código.
+5. Clique no botão `Salvar`.
+
+<div class="alert alert-warning">
+  Customizar arquivos de Javascript pode danificar seu Checkout. A VTEX <b>não recomenda</b> customizações e não se responsabiliza por qualquer dano causado por esse código.
+</div>
+
+__IMPORTANTE:__ não use esses arquivos para inserir tags de marketing e integrações. Se precisar delas, faça isso pelo Google Tag Manager.
+
+### PayPal Plus
+
+O SmartCheckout™ V5 dá suporte ao método de pagamento PayPal Plus, que permite que o pagamento seja feito diretamente em seu site, sem redirecionar seus clientes (checkout transparente).
+
+### Google Enhanced Ecommerce
+
+O SmartCheckout™ V5 adiciona ao data layer informações para serem usadas com o Google Enhanced Ecommerce. Para saber como criar essas tags, verifique a documentação do Google: https://developers.google.com/tag-manager/enhanced-ecommerce.
diff --git a/docs/tutorials/pt/special-conditions.md b/docs/tutorials/pt/special-conditions.md
index 3a70bcda3..c3a20c2c3 100644
--- a/docs/tutorials/pt/special-conditions.md
+++ b/docs/tutorials/pt/special-conditions.md
@@ -3,8 +3,8 @@ title: 'Configurar condições especiais de pagamento'
 id: tutorials_456
 status: PUBLISHED
 createdAt: 2017-04-27T22:03:58.783Z
-updatedAt: 2023-02-24T20:54:02.331Z
-publishedAt: 2023-02-24T20:54:02.331Z
+updatedAt: 2023-07-27T16:59:12.708Z
+publishedAt: 2023-07-27T16:59:12.708Z
 firstPublishedAt: 2017-04-27T23:03:26.753Z
 contentType: tutorial
 productTeam: Financial
@@ -19,11 +19,7 @@ As condições especiais fazem parte da configuração das condições de pagame
 
 Para identificar as condições especiais aplicáveis a cada forma de pagamento, no Admin VTEX, acesse __Pagamentos > Configurações > Condições de Pagamento__, selecione a forma de pagamento desejada e verifique as opções conforme ilustração abaixo.
 
-![condições especiais de pago](https://images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/7d7e10782385dcd7f76019a6ac8390e0/Condi____o_especial_de_pagamento.png)
-
-<div class = "alert alert-info">
-  <p>As condições especiais das regras de pagamento são aplicadas somente para o número de parcelas. A forma de pagamento permanece a mesma.</p>
-</div>
+![condições especiais de pago](//images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/7d7e10782385dcd7f76019a6ac8390e0/Condi____o_especial_de_pagamento.png)
 
 ## Condição Comercial
 
@@ -33,7 +29,7 @@ Para saber como cadastrar uma nova condição comercial e associá-la a um SKU,
 
 ## Como configurar a condição comercial na condição de pagamento
 
-![condicao-comercial pt](https://images.ctfassets.net/alneenqid6w5/3VXKTcFtIkca4iwioWw648/6d574cddd91fd57ad6610631b11129c7/condicao-comercial.png)
+![condicao-comercial pt](//images.ctfassets.net/alneenqid6w5/3VXKTcFtIkca4iwioWw648/6d574cddd91fd57ad6610631b11129c7/condicao-comercial.png)
 
 1. Dentro da condição de pagamento, clique em `Adicionar condição especial`.
 2. Em seguida, clique em `Condição Comercial`.
@@ -93,7 +89,7 @@ Permite disponibilizar uma condição de pagamento para uma política comercial
 
 Como configurar a política comercial na condição de pagamento
 
-![politica-comercial pt](https://images.ctfassets.net/alneenqid6w5/25wX7GscdqwUmiWQC4Oi4U/291c228f5deee2036890f4e6bbb812d0/politica-comercial.png)
+![politica-comercial pt](//images.ctfassets.net/alneenqid6w5/25wX7GscdqwUmiWQC4Oi4U/291c228f5deee2036890f4e6bbb812d0/politica-comercial.png)
 
 1. Dentro da condição de pagamento, clique em `Adicionar condição especial`.
 3. Em seguida em `Política Comercial (Canal de Vendas)`.
@@ -118,7 +114,7 @@ Como configurar o banco emissor na condição de pagamento:
 6. Caso deseje segmentar por co-brand, selecione a opção desejada em __Co-brand__ (essa caixa de seleção só vai aparecer se sua loja houver informado à VTEX a lista de cartões com co-brand).
 7. Salve as alterações.
 
-![banco-emissor pt](https://images.ctfassets.net/alneenqid6w5/6e5Hf9tpLyuSkoGk08oOcw/38c528cd80c158b750a06ce3b99beea0/banco-emissor.png)
+![banco-emissor pt](//images.ctfassets.net/alneenqid6w5/6e5Hf9tpLyuSkoGk08oOcw/38c528cd80c158b750a06ce3b99beea0/banco-emissor.png)
 
 ### Exemplos
 
@@ -150,7 +146,7 @@ Permite configurar uma validade na condição de pagamento, para que deixe de se
 
 Veja a seguir como configurar o período na condição de pagamento:
 
-![periodo pt](https://images.ctfassets.net/alneenqid6w5/4zOoeve2Q8mgqkCQGQIWoq/5a37b26881341ce133c582693816bf18/periodo.png)
+![periodo pt](//images.ctfassets.net/alneenqid6w5/4zOoeve2Q8mgqkCQGQIWoq/5a37b26881341ce133c582693816bf18/periodo.png)
 
 1. Dentro da condição de pagamento, clique em `Adicionar condição especial`.
 3. Em seguida, clique em `Período`.
diff --git a/docs/tutorials/pt/split-payment.md b/docs/tutorials/pt/split-payment.md
index 6f07c4e83..25c4fcf10 100644
--- a/docs/tutorials/pt/split-payment.md
+++ b/docs/tutorials/pt/split-payment.md
@@ -3,8 +3,8 @@ title: 'Split de Pagamento'
 id: 6k5JidhYRUxileNolY2VLx
 status: PUBLISHED
 createdAt: 2021-04-06T20:03:53.443Z
-updatedAt: 2023-04-24T19:09:31.016Z
-publishedAt: 2023-04-24T19:09:31.016Z
+updatedAt: 2024-06-18T17:50:44.146Z
+publishedAt: 2024-06-18T17:50:44.146Z
 firstPublishedAt: 2021-04-07T18:57:19.713Z
 contentType: tutorial
 productTeam: Financial
@@ -19,13 +19,18 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 Esta é uma solução para pagamentos em contextos de marketplace.
 </div>
 
-Para garantir que nossos clientes de marketplace dividam o pagamento entre todos os sellers automaticamente, estabeleçam uma comissão baseada em um percentual fixo e permaneçam em conformidade com as regulamentações em vigor, a VTEX oferece a solução __Split de pagamentos__.
+Para garantir que nossos clientes de [marketplace](https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8) dividam o pagamento entre todos os [sellers](https://help.vtex.com/pt/tutorial/what-is-a-seller) automaticamente, estabeleçam uma comissão baseada em um percentual fixo e permaneçam atuando conforme as regulamentações em vigor, a VTEX oferece o __Split de pagamentos__.
 
-Quando um consumidor adiciona produtos de sellers diferentes ao mesmo carrinho e paga por eles em uma experiência de checkout unificada, a VTEX divide automaticamente esse pagamento para que cada beneficiário obtenha sua parte diretamente na sua conta bancária.
+Veja a seguir dois exemplos de cenários de aplicação de split de pagamentos onde um consumidor adiciona produtos de sellers diferentes ao mesmo carrinho:
 
-Esse valor nem sempre será dividido igualmente entre os beneficiários. A distribuição é feita de acordo com as condições predefinidas do seller e as comissões cobradas pelo marketplace. Quando configurado, o Split de pagamentos permite que o valor pago por um pedido seja automaticamente dividido entre [sellers](https://help.vtex.com/pt/tutorial/what-is-a-seller) e [marketplaces](https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8). 
+1. Quando o marketplace é responsável por processar o pagamento da compra, a VTEX divide automaticamente esse pagamento para que cada beneficiário receba a sua parte diretamente na própria conta bancária, realizando assim o [Split de recebíveis](https://help.vtex.com/pt/tutorial/split-payment#split-de-recebiveis).
+2. Quando o carrinho envolve sellers que são responsáveis por processar o seu próprio meio de pagamento (sem depender do marketplace), a VTEX cria diferentes transações de pagamento para o Marketplace e os sellers, efetuando o [Split de transação](https://help.vtex.com/pt/tutorial/split-payment#split-de-transacao).
 
-Você pode configurar o Split de pagamentos de duas maneiras: Por [Split de recebíveis](https://help.vtex.com/pt/tutorial/split-payment#split-de-recebiveis) ou [Split de transação](https://help.vtex.com/pt/tutorial/split-payment#split-de-transacao). Há diferenças entre os tipos de Split de pagamentos que você deve levar em consideração antes de escolher um deles.
+<div class="alert alert-warning">
+A distribuição dos valores de uma compra sempre é realizada conforme os acordos de percentual de comissão pré-definidos entre o marketplace e os sellers.
+</div>
+
+Confira abaixo mais detalhes sobre cada um dos modelos de split de pagamentos:
 
 | Características    | Split de recebíveis     | Split de transação     |
 | ---------- | ---------- | ---------- |
@@ -34,7 +39,7 @@ Você pode configurar o Split de pagamentos de duas maneiras: Por [Split de rece
 | __Número de compras na fatura do cartão de crédito do cliente__       | Apenas uma compra.       | Uma compra para cada seller. <li>*Essa opção pode gerar mal-entendidos e aumentar o número de disputas e estornos*.</li>       |
 | __Negociação de tarifas__  | O marketplace será responsável por negociar todas as tarifas. <li>Em escala, isso pode ser positivo para aumentar o poder de negociação.</li>       | Cada beneficiário escolhe seu provedor de pagamento e negocia suas tarifas.       |
 | __Avaliação antifraude__      | Como apenas uma transação é gerada, o pedido inteiro passa por uma única análise antifraude.       | Como várias transações são geradas, cada uma delas passa por uma análise antifraude diferente. Se uma transação for negada, todas as outras também serão negadas automaticamente.       |
-| __Provedores de pagamento integrados__       | Informação disponível na [Lista de Provedores de Pagamento por País](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp) | Todos os provedores de pagamento integrados à VTEX.       |
+| __Provedores de pagamento integrados__       | Veja quais provedores de pagamento utilizam o Payout Split na [Lista de Provedores de Pagamento por País](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp) | Todos os provedores de pagamento integrados à VTEX.       |
 | __Custo__       |Custos de acordo com a tarifa negociada. <ul><li>Geralmente é mais caro do que transações sem split.</li><li>Carrinhos com produtos apenas do marketplace serão processados levando em consideração a tarifa negociada, o que pode aumentar o custo.</li></ul>       | Sem custos adicionais. Os clientes VTEX serão responsáveis apenas pelas tarifas usuais acordadas com os provedores de pagamento.       |
 | __Experiência de checkout__       | Sem limitações em relação aos meios e condições de pagamento, que serão definidos pelo marketplace. <ul><li>O provedor de pagamento também deve oferecer split em meios de pagamento específicos (Pix, por exemplo). Hoje em dia, nossos parceiros oferecem split com um ou dois cartões de crédito, cartões de débito e boleto.</li></ul>      | Exibe apenas os métodos de pagamento aceitos por todos os vendedores que realizam o pedido. Ou seja, pagamentos com cartão de crédito, dinheiro ou card promissory (promissória que aceita parcelamento), só estarão disponíveis se todos os vendedores envolvidos no pedido aceitarem. Incompatível com:<ul><li>Boleto.</li><li>Pix.</li></ul><ul><li>Cartões com 3DS2 ou qualquer autenticação.</li></ul> |
 | __Ideal para__       | <ul><li>Marketplaces que desejam cobrar comissões automáticas, evitando o risco de inadimplência.</li><li>Marketplaces cujos sellers não têm um provedor de pagamento.</li></ul><ul><li>Marketplaces que desejam ter mais controle sobre o fluxo de pagamento dos sellers.</li><li>  Marketplaces que desejam processar transações com Pix, boleto e cartões de crédito com 3DS2 ou outra autenticação.</li></ul>       | <ul><li> Marketplaces que não querem ser comerciantes registrados (comum para empresas B2B da Europa e dos Estados Unidos).</li><li> Casos em que o seller tem mais poder de decisão do que o marketplace e só aceita que o pagamento seja processado pelo seu próprio provedor de pagamento.</li></ul><ul><li> Marketplaces que têm urgência para implementar o split de pagamentos e não têm parceiros que oferecem esse recurso em seus países.</li><li>Marketplaces que não querem arcar com todos os riscos de estorno.</li></ul>       |
@@ -52,32 +57,26 @@ Por exemplo, um cliente adiciona dois produtos ao mesmo carrinho de compras. Um
 
 O pagamento é distribuído da seguinte forma:
 
-![Split de recebíveis](https://images.ctfassets.net/alneenqid6w5/4XGw7jeLfayteKzZ9eMaUU/60f806b9ee7dc128b7b6b55e8cc114c7/Split_de_receb__veis.png)
+![Split de recebíveis](//images.ctfassets.net/alneenqid6w5/4XGw7jeLfayteKzZ9eMaUU/60f806b9ee7dc128b7b6b55e8cc114c7/Split_de_receb__veis.png)
 
 Nosso gateway calcula e distribui os pagamentos para cada beneficiário quando o pedido é faturado e envia essas informações ao provedor de pagamento. A distribuição é feita considerando o valor destinado a cada parte envolvida no pedido e as comissões cobradas pelo marketplace.
 
-![Relatório de comissão](https://images.ctfassets.net/alneenqid6w5/2C8DFezzCKaSzgq2f77pxB/ca3cbcf0fa22a2bca6ab0d219b45e684/Split_de_receb__veis_2.png)
-
-Com esse modelo, os marketplaces também têm acesso a um relatório de comissionamento, no qual podem consultar a relação de pedidos faturados por cada um dos seus sellers e as respectivas comissões que foram retidas.
-
-O relatório de comissionamento traz transparência em relação aos valores devidos a cada seller e às comissões que os pedidos geraram para o marketplace.
-
-<div class="alert alert-warning">
-Atualmente, nosso relatório de comissionamento está disponível apenas para os clientes que participam do teste beta.
-</div>
+![Relatório de comissão](//images.ctfassets.net/alneenqid6w5/2C8DFezzCKaSzgq2f77pxB/ca3cbcf0fa22a2bca6ab0d219b45e684/Split_de_receb__veis_2.png)
 
 É importante considerar que a nossa solução de split de recebíveis tem algumas limitações:
 
 - __Meios de pagamento combinados:__ não está disponível quando um dos meios escolhidos não é compatível com split. Exemplo: vale-compra + cartão de crédito (vale-compra não é compatível com split).  Devido a uma limitação do checkout, atualmente só é possível dividir o pagamento quando os meios combinados são dois cartões de crédito.
-- __Alteração do pedido:__ não funciona com alterações de valores ou itens após o pedido ter sido realizado. Dessa forma, também não é possível cancelar parcialmente um pedido com split.
+- __Alteração do pedido:__ não funciona com alterações de valores ou itens após o pedido ter sido realizado. O pedido que contenha split pode ser reembolsado parcialmente, mas não cancelado.
 - __Assinaturas VTEX:__ não é compatível com pedidos de marketplace.
 - __ID do seller:__ o CNPJ é a chave primária para fazer o split, portanto os beneficiários (marketplaces ou sellers) precisam ser pessoas jurídicas.
 - __Mesmo CNPJ:__ como o CNPJ é a chave primária para fazer o split, não é possível que dois ou mais beneficiários/participantes da venda com o mesmo CNPJ sejam considerados "entidades" distintas.
 - __Partes envolvidas:__ não é possível dividir o pagamento com beneficiários que não estejam vendendo produtos no carrinho. Por exemplo: pagar o frete diretamente para a transportadora.
 - __Tarifas nominais:__ não permite tarifas nominais. Atualmente, só é possível aplicar comissões percentuais sobre produtos e/ou fretes.
 - __Atribuição de transações ao provedor:__ atualmente só é possível atribuir uma afiliação preferencial no gateway para processar o split usando condições comerciais para os SKUs que são vendidos pelo seller. No entanto, há limitações:
-        - Se o seller e o marketplace tiverem o mesmo SKU, o carrinho sempre escolherá o meio de pagamento com split.
-        - A lista de SKUs precisa ser constantemente atualizada.
+    - Se o seller e o marketplace tiverem o mesmo SKU, o carrinho sempre escolherá o meio de pagamento com split.
+    - A lista de SKUs precisa ser constantemente atualizada.
+
+- __Juros da transação:__ não é possível selecionar quem receberá a informação dos juros (marketplace ou seller). Todas as transações em que o cliente efetuou pagamento de juros são enviadas automaticamente para o marketplace.
 
 ## Split de transação
 
@@ -89,11 +88,11 @@ Isso significa que o marketplace tem menos controle sobre o fluxo de pagamento.
 
 Por exemplo, um cliente adiciona dois produtos ao mesmo carrinho de compras. Um deles será entregue pelo próprio marketplace e o outro por um seller chamado Seller A.
 
-![Split de transação](https://images.ctfassets.net/alneenqid6w5/3ZOMQYkxlRzMgUMck9o7o8/d36e97acd5addabaee0d1ef6c21fd712/Split_de_transa____o.png)
+![Split de transação](//images.ctfassets.net/alneenqid6w5/3ZOMQYkxlRzMgUMck9o7o8/d36e97acd5addabaee0d1ef6c21fd712/Split_de_transa____o.png)
 
 No split de transação, o marketplace não precisa fazer nenhuma configuração. O seller é quem precisa configurar seu próprio meio de pagamento na afiliação com o marketplace em questão. Para mais detalhes, confira nossa documentação [Envie os meios de pagamento do seller white label ao marketplace.](https://help.vtex.com/pt/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW)
 
-![Afiliação](https://images.ctfassets.net/alneenqid6w5/yX3yPgPbkjlDDoYYdsnYD/9b03a7e73c7747db5b6cf22518730c50/Afiliados.png)
+![Afiliação](//images.ctfassets.net/alneenqid6w5/yX3yPgPbkjlDDoYYdsnYD/9b03a7e73c7747db5b6cf22518730c50/Afiliados.png)
 
 O split de transação tem algumas limitações que devem ser levadas em consideração.
 
@@ -112,6 +111,4 @@ Quando o split de transação e o split de recebíveis são combinados, o split
 
 ### Saiba mais
 
-- [Configurar gateway PagarMeV2](https://help.vtex.com/pt/tutorial/setting-up-pagarmev2-gateway--5TugxXNMOs0Ocyg4uqussM?&utm_source=autocomplete)
-- [Configurar o VTEX Payment](https://help.vtex.com/pt/tracks/vtex-payment--7iCCIoIZFmd9OabU6QlmXu/1lZWKCGdy7xpYjukTLfFJL)
 - [Enviar os meios de pagamento do Seller White Label para o Marketplace](https://help.vtex.com/pt/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW) (para obter mais informações sobre como configurar o split de transação).
diff --git a/docs/tutorials/pt/store-access-permission.md b/docs/tutorials/pt/store-access-permission.md
index fe3c19cae..b13877427 100644
--- a/docs/tutorials/pt/store-access-permission.md
+++ b/docs/tutorials/pt/store-access-permission.md
@@ -25,4 +25,4 @@ Para realizar essa configuração, no painel administrativo (Admin) da conta des
 4. Selecione a opção __VTEX Store__.
 5. Marque a caixa de seleção __“Enables B2B behaviour”__ e salve as alterações.
 
-![Habilitar cenário B2B](https://images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
+![Habilitar cenário B2B](//images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
diff --git a/docs/tutorials/pt/store-overview-beta.md b/docs/tutorials/pt/store-overview-beta.md
new file mode 100644
index 000000000..6ac109a70
--- /dev/null
+++ b/docs/tutorials/pt/store-overview-beta.md
@@ -0,0 +1,162 @@
+---
+title: 'Visão geral da loja (Beta)'
+id: 7i8wNsQQgbbFhYMYbQ5X46
+status: PUBLISHED
+createdAt: 2023-06-14T17:43:51.256Z
+updatedAt: 2023-11-09T19:56:54.060Z
+publishedAt: 2023-11-09T19:56:54.060Z
+firstPublishedAt: 2023-06-15T14:16:58.510Z
+contentType: tutorial
+productTeam: Management
+author: 0QBQws7rk0t5Mnu8fgfUv
+slug: visao-geral-da-loja-beta
+locale: pt
+legacySlug: visao-geral-da-loja-beta
+subcategory: QPnz120TdtLcXSh65c4Gs
+---
+
+<div class="alert alert-info"> 
+A versão atualizada da página Visão Geral da Loja (Beta) está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É importante observar que podem ser aplicadas taxas extras no futuro. Além disso, a página Visão Geral atualmente presente no Admin VTEX continuará disponível para uso por enquanto.
+</div>
+
+A página Visão Geral (Beta) em seu Admin VTEX fornece um acompanhamento em tempo real da sua operação no dia atual, oferecendo visibilidade sobre indicadores para que você e sua equipe tenham um feedback rápido das ações realizadas na loja e possam atuar prontamente em melhorias. 
+
+Essa ferramenta está disponível no Admin VTEX, na página de início. Para acessá-la, clique em **Dashboards > Visão Geral** no menu de navegação, ou digite _Visão Geral_ na barra de busca no topo da página.
+
+![PT Visão geral Beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/62aceefab415f246a39fcd604a89f080/PT_Visa__o_geral_Beta.png)
+
+Neste artigo, apresentamos as principais seções e ações presentes na página. Saiba mais sobre:
+
+* [Dados na página](#dados-na-pagina)
+* [Analisar resultados e saúde da operação](#analisar-resultados-e-saude-da-operacao)
+* [Comparar períodos](#comparar-periodos)
+* [Visualização](#visualizacao)
+* [Monitoramento](#monitoramento)
+* [Métricas](#metricas)
+
+## Dados na página
+
+As métricas da página incluem dados sobre pedidos e navegação, que são captados de sistemas diferentes.
+
+<div class ="alert alert-warning">
+É provável que existam diferenças entre as métricas de receita e ticket médio registradas no OMS e no Performance de Vendas, por exemplo. Isso ocorre porque o Performance de Vendas considera o valor dos itens, enquanto o OMS também considera os descontos, frete, taxas e promoções sobre o pedido - o que pode aumentar ou diminuir seu valor final. 
+</div>
+
+* **Pedidos e receitas:** os dados sobre pedidos e receitas vêm do OMS, ou Sistema de Gerenciamento de Pedidos da VTEX e incluem pedidos realizados em todos os seus canais de venda.
+* **Sessões:** os dados de navegação vêm do sistema interno da plataforma que capta sessões dos usuários no storefront de lojas VTEX. Sessões são representadas pelo conjunto de visualizações das páginas acessadas por um mesmo usuário  ao navegar em seu ecommerce, desconsiderando marketplaces, apps, Sales App e qualquer outro canal de venda.
+
+### Restrições nos dados
+
+Não captamos dados de navegação para storefronts que não são VTEX, ou de sellers que somente anunciam produtos em marketplaces externos. Por isso os tipos de gráficos presentes no [Monitoramento](#monitoramento) podem não estar disponíveis, dependendo se captamos dados de navegação da sua loja, ou não.
+
+Apesar de buscarmos apresentar no máximo 3% de divergência com os dados do OMS da VTEX, por vezes, você pode encontrar discrepâncias entre os dados informados na Visão Geral e no OMS. 
+
+### Atualização de dados
+
+Os dados da página são atualizados com frequências diferentes. Os gráficos na seção de [Monitoramento](#monitoramento) se atualizam em até três minutos, dependendo da [Visualização](#visualizacao), enquanto as outras seções da página são atualizadas a cada 15 minutos. A etiqueta  <i class='fas fa-circle-notch blue-color'></i>  1 min mostra a última vez que os dados da página foram atualizados. 
+
+## Analisar resultados e saúde da operação
+
+É possível utilizar diferentes [métricas](#metricas) e gráficos de [monitoramento](#monitoramento) para sua análise de resultados, dependendo de qual aspecto deseja explorar. A tabela abaixo pode guiar a sua análise. Clique em cada métrica listada na tabela para saber mais sobre seu cálculo e funcionamento. 
+
+| O que deseja explorar  | Quais métricas e gráficos analisar                                                                                                                                                                                                                                                           |
+|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Engajamento da ação    | - [Novas sessões](#monitoramento) <br>- [Produtos com mais unidades vendidas](#metricas)                                                                                                                                                                                                                                     |
+| Resultados financeiros | - [Receita captada](#monitoramento) <br>- [Ticket Médio](#metricas)<br>- [Produtos com maior receita](#metricas)                                                                                                                                                                                                                         |
+| Conversão              | - [Taxa de Conversão](#metricas) <br>- [Funil de vendas](#funil-de-vendas) <br>- [Pedidos captados](#monitoramento), comparando com o número de Pedidos cancelados. Dependendo do resultado, isso pode direcionar sua equipe a identificar problemas operacionais no fulfillment ou atendimento ao consumidor que causaram os pedidos cancelados. |
+
+<div class="alert alert-info"> 
+Note que enquanto os gráficos em Monitoramento são atualizados em até três minutos, as Métricas são atualizadas de quinze em quinze minutos, o que pode influenciar a sua análise de resultados. Saiba mais em <a href="#atualizacao-de-dados">Atualização de dados</a>.
+</div>
+
+### Analisar resultados de campanhas
+
+Caso deseje analisar os resultados gerados por campanhas, promoções ou lançamentos de novos produtos ocorridos em uma data passada, siga as instruções abaixo: 
+
+1. Selecione a **Loja** onde a ação ocorreu.
+2. Selecione a **data** da campanha para [comparar o período](#comparar-periodos) com a data de hoje.
+3. Selecione a [visualização](#visualizacao) `Acumulada`.
+4. Acompanhe a performance hora a hora das métricas.
+
+![PT visão geral acumulado](//images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/93f86ef067d3c7630ba6b545a8811a8b/PT_visa__o_geral_acumulado.png)
+
+### Acompanhar impactos de mudanças na loja
+
+Para manter a estabilidade da saúde da sua operação é importante identificar se "deploys", campanhas, ou alterações de configurações impactaram negativamente o número de pedidos, sessões ou conversão de clientes nos momentos imediatos após a sua aplicação.
+
+Caso deseje ver o impacto de mudanças feitas na loja, para identificar um possível impacto negativo ou alterações na saúde do negócio, siga as instruções abaixo. 
+
+1. Selecione a **Loja** onde a ação ocorreu.
+2. Selecione a [visualização](#visualizacao) `Últimas horas`.
+3. Avalie o pulso nas métricas, ou pontos de inflexão no gráfico, ocorridos nas últimas duas horas. 
+4. Compare os horários dos pontos de inflexão, com as mudanças geradas para identificar sua causa e impacto. 
+
+![PT visão geral últimas duas horas](//images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/a069a0657d521f68a7be3a4221b70036/PT_visa__o_geral_u__ltimas_duas_horas.png)
+
+## Comparar períodos
+
+É possível filtrar dados com base no período selecionado e comparar as métricas da loja com datas passadas. Para comparar dados de diferentes períodos, no topo da página, selecione a data ao lado de `Comparar hoje com:`, depois selecione entre as seguintes opções:
+
+| Período       | Início                                                                                   | Fim                                  |
+|---------------|------------------------------------------------------------------------------------------|--------------------------------------|
+| Ontem         | 00:00 do dia anterior                                                                    | 23:59 do dia anterior                |
+| 7 dias atrás  | 00:00 dos oito dias anteriores ao dia de hoje                                            | 23:59 do dia anterior ao dia de hoje |
+| 28 dias atrás | 00:00 do 29° dia anterior ao dia atual                                                   | 23:59 do dia anterior ao dia de hoje |
+| Personalizado | Marque no calendário a Data de comparação desejada, com um limite de 13 meses no passado | 23:59 do dia anterior ao dia de hoje |
+
+## Visualização
+
+Ao clicar no botão `Visualização:` dentro da seção [Monitoramento](#monitoramento), é possível alternar entre as seguintes opções:
+
+* **Acumulado:** valor total acumulado no dia para cada métrica de monitoramento, desde 00:00h até a última atualização. Os dados nessa visualização são atualizados a cada três minutos. 
+* **Últimas horas:** valor recebido nas últimas duas horas para cada métrica de monitoramento. Essa visualização não exibe a comparação com outros períodos nem a porcentagem de crescimento ou decrescimento da métrica. Os dados nessa visualização são atualizados a cada minutos. 
+
+Também é possível filtrar por loja selecionando pelo menu suspenso.  
+
+## Monitoramento
+
+Cada gráfico contém os seguintes elementos:
+
+* O eixo X apresenta o horário, enquanto o eixo Y apresenta o valor da métrica de monitoramento.
+* Número absoluto de cada métrica, podendo ser `Acumulada` ou nas `Últimas horas`. Saiba mais em [Visualização](#visualização). 
+* A linha azul mais grossa indica a evolução de valores no dia de hoje. 
+* A linha cinza pontilhada indica a taxa para o período que está sendo comparado. 
+* Ao passar o cursor, o gráfico mostra o valor absoluto para cada período comparado.
+
+A tabela abaixo descreve os gráficos incluídos na seção _Monitoramento_ da página. 
+
+| Métrica          | Descrição                                                                                                                                                                       |
+|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Receita captada  | Valor total determinado pelo valor final dos pedidos captados, indicando o valor que a loja recebeu de receita, comparando o dia de hoje com um período específico selecionado. |
+| Pedidos captados | Número de pedidos recebidos pela sua loja no dia de hoje comparado com o período selecionado.                                                                                   |
+| Ticket médio     | Receita média por pedido captado no dia de hoje comparado com o período selecionado.                                                                                            |
+| Novas Sessões    | Número de novas visitas ou interações à sua loja, dependendo do tipo de [Visualização](#visualizacao) escolhida. Esta métrica só está disponível para lojas que [capturam dados de navegação](#dados-na-pagina).     |
+
+## Métricas
+
+![PT métricas](//images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/5757d545cae0367ad8a8e784532252f8/PT_me__tricas.png)
+
+A tabela abaixo descreve as métricas disponíveis no painel da página inicial. Todas as métricas se referem aos fluxos de compra realizados em lojas VTEX no período selecionado.
+
+| Métrica                             | Descrição                                                                                                                                                                                                                                                                                                                                       |
+|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Ticket Médio                        | Média do valor pago por pedidos captados no período selecionado. Essa métrica acompanha o ícone <i class='fa fa-caret-down'></i> para baixo e <i class='fa fa-caret-up'></i> para cima, para demonstrar a porcentagem de crescimento ou decrescimento do ticket médio.                                                                                                                                                                  |
+| Taxa de conversão                   | Porcentagem calculada dividindo o número total de pedidos pelo número total de sessões na sua loja. Ao clicar no ícone de seta <i class='fa fa-chevron-down'></i>,  você expande o Funil de vendas.                                                                                                                                             |
+| Produtos com maior receita          | Produtos que geraram a maior receita no período selecionado. Indica o valor recebido em receita e uma porcentagem indicando aumento ou diminuição de receita, comparando entre os períodos selecionados. Ao clicar no ícone de seta <i class='fa fa-chevron-down'></i>, você alterna entre essa métrica e Produtos com mais unidades vendidas.  |
+| Produtos com mais unidades vendidas | Produtos que venderam mais unidades no período selecionado. Indica a quantidade de itens vendidos e uma porcentagem indicando aumento ou diminuição de itens vendidos, comparando entre os períodos selecionados. Ao clicar no ícone de seta <i class='fa fa-chevron-down'></i>, você alterna entre essa métrica e Produtos com maior receita.  |
+
+### Funil de vendas
+
+Na métrica de _Taxa de conversão_, ao clicar no ícone de seta <i class='fa fa-chevron-down'></i>,  você expande o **Funil de vendas**. Esse gráfico acompanha e rastreia o volume de sessões nas etapas intermediárias do fluxo de compras e identifica oportunidades para otimizar a taxa de conversão da loja. A tabela abaixo descreve as etapas intermediárias do fluxo de compras.
+
+| Etapa     | Descrição                                                                 |
+|-----------|---------------------------------------------------------------------------|
+| Sessões   | Número total de visitas à sua loja                                        |
+| Produto   | Uma página de produto foi acessada pelo usuário durante a sessão          |
+| Carrinho  | Um produto foi adicionado ao carrinho pelo usuário durante a sessão       |
+| Envio     | As informações de entrega foram preenchidas pelo usuário durante a sessão |
+| Pagamento | Os dados de pagamento foram preenchidos durante a sessão                  |
+| Pedidos   | Pedidos que foram realizados durante a sessão                             |
+
+Cada barra azul no gráfico representa o volume de sessões que atingiram um determinado estágio do fluxo de compras. Esse volume é representado como um valor absoluto, e como uma porcentagem do número de sessões, juntamente com os pontos percentuais de aumento ou diminuição no funil de vendas. 
+
diff --git a/docs/tutorials/pt/store-overview.md b/docs/tutorials/pt/store-overview.md
index 92efe42b7..c4e99928e 100644
--- a/docs/tutorials/pt/store-overview.md
+++ b/docs/tutorials/pt/store-overview.md
@@ -17,7 +17,7 @@ subcategory: 1TIJqw8kV2Yok4iQe4SAkq
 
 Na página Visão Geral, os proprietários de lojas VTEX têm acesso às principais métricas que impactam a receita de suas lojas. Nesse painel, você pode acompanhar a evolução das suas vendas através dos recursos de análise de tendências de pedidos, taxa de conversão e gráficos de funil de vendas. Essa ferramenta está disponível no Admin VTEX. Para acessá-la, clique em __Dashboards > Visão Geral__ no menu de navegação, ou digite *Visão Geral* na barra de busca no topo da página.
 
-![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 A página de Visão Geral traz um resumo do seu negócio com a VTEX. Para consultar análises mais profundas das métricas da sua loja, acesse [Performance de Vendas](https://help.vtex.com/pt/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp).
 
@@ -54,7 +54,7 @@ Para comparar dados de diferentes períodos, no topo da página, selecione a dat
 | Últimos 28 dias | 00:00 do 29° dia anterior ao dia atual        | 23:59 do dia anterior ao dia de hoje                                                                                                                                    |
 
 ## Métricas
-![Store overview Métricas PT](https://images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/efa916ff3c1f70906439c3f2f4adbf06/Me__tricas_PT.png)
+![Store overview Métricas PT](//images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/efa916ff3c1f70906439c3f2f4adbf06/Me__tricas_PT.png)
 
 A tabela abaixo descreve as principais métricas disponíveis no painel da página inicial. Todas as métricas se referem aos fluxos de compra realizados em lojas VTEX em um determinado período de tempo.
 
@@ -71,7 +71,7 @@ Pedidos cancelados                               | Número total de pedidos canc
 | Pedidos na última hora                | Pedidos feitos na sua loja na última hora. Ao clicar nessa métrica, você será redirecionado para a página [Todos os pedidos](https://help.vtex.com/pt/v4/docs/todos-os-pedidos--6JHeydzIft46VY7JTEpbJT).                                                                                                                                                                   |
 
 ## Produtos com maior receita / Produtos com mais unidades vendidas
-![Store overview Growing products PT](https://images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/186c31b9b5632b5a106d3439dac945ec/Store_overview_Growing_products_PT.jpg)
+![Store overview Growing products PT](//images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/186c31b9b5632b5a106d3439dac945ec/Store_overview_Growing_products_PT.jpg)
 
 Esse componente lista seus produtos com maior receita e os produtos com mais unidades vendidas no período selecionado. Você pode alternar entre as duas opções clicando no título, ou no ícone <i class="fas fa-chevron-down"></i>.
 
@@ -80,16 +80,16 @@ Saiba mais sobre as listas:
 - **Produtos com mais unidades vendidas:** produtos que venderam mais unidades no período selecionado. Indica a quantidade de itens vendidos e uma porcentagem indicando aumento ou diminuição de itens vendidos, comparando entre os períodos selecionados. 
 
 ## Pedidos realizados
-![Store overview Pedidos realizados PT](https://images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/7f8f3d3bab538d4c680dcd09511f0984/Pedidos_realizados_PT.png)
+![Store overview Pedidos realizados PT](//images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/7f8f3d3bab538d4c680dcd09511f0984/Pedidos_realizados_PT.png)
 
 Esse gráfico mostra o número de pedidos recebidos pela sua loja no período selecionado. A linha azul mais grossa indica os pedidos feitos no período mais recente. A linha cinza mais fina indica os pedidos feitos no período que está sendo comparado.   Ao passar o cursor, o gráfico mostra o número de pedidos captados para cada data. 
 
 ## Pedidos cancelados
-![Store overview Pedidos cancelados PT](https://images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/3bb0e1ec615af3d38c6b10cdcf3a3370/Pedidos_cancelados_PT.png)
+![Store overview Pedidos cancelados PT](//images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/3bb0e1ec615af3d38c6b10cdcf3a3370/Pedidos_cancelados_PT.png)
 Esse gráfico mostra o número de pedidos cancelados na sua loja no período selecionado. A linha azul mais grossa indica os pedidos cancelados no período mais recente. A linha cinza mais fina indica os pedidos cancelados no período que está sendo comparado. Ao passar o cursor, o gráfico mostra o número de pedidos cancelados em cada data. 
 
 ## Análise de tendências de pedidos
-![Store overview Order trend PT](https://images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/9807c6b956c1b2a34d558046766d1120/Store_overview_Order_trend_PT.jpg)
+![Store overview Order trend PT](//images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/9807c6b956c1b2a34d558046766d1120/Store_overview_Order_trend_PT.jpg)
 
 Esse gráfico mostra o comportamento dos pedidos da sua loja, indicando o número de pedidos feitos pelos compradores no período selecionado.
 
@@ -98,14 +98,14 @@ A linha indica a curva de pedidos para o período selecionado. Ao passar o curso
 A etiqueta acima do gráfico indica se o número de pedidos está `normal`, `baixo` ou `alto` em comparação com o desempenho habitual da sua loja no período selecionado.
 
 ## Taxa de conversão
-![Store overview Conversion rate PT](https://images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/c974a11d3e708c5d40d0757ebfa95faf/Store_overview_Conversion_rate_PT.jpg)  
+![Store overview Conversion rate PT](//images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/c974a11d3e708c5d40d0757ebfa95faf/Store_overview_Conversion_rate_PT.jpg)  
 
 Esse gráfico mostra a taxa de conversão da sua loja nos períodos que você deseja comparar. 
 
 A taxa de conversão é calculada dividindo o número total de pedidos pelo número total de sessões na sua loja. A linha azul mais grossa indica a taxa de conversão para o período mais recente. A linha cinza mais fina indica a taxa para o período que está sendo comparado.  Ao passar o cursor, o gráfico mostra a taxa de conversão para cada período comparado. 
 
 ## Funil de vendas
-![Store overview sales funnel PT](https://images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/c00dbe392b24f5157350d6c037759837/Store_overview_sales_funnel_PT.jpg)
+![Store overview sales funnel PT](//images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/c00dbe392b24f5157350d6c037759837/Store_overview_sales_funnel_PT.jpg)
 
 Esse gráfico acompanha e rastreia o volume de sessões nas etapas intermediárias do fluxo de compras e identifica oportunidades para otimizar a taxa de conversão da loja. A tabela abaixo descreve as etapas intermediárias do fluxo de compras.
 
@@ -121,7 +121,7 @@ Esse gráfico acompanha e rastreia o volume de sessões nas etapas intermediári
 Cada barra azul no gráfico representa o volume de sessões que atingiram um determinado estágio do fluxo de compras. Esse volume é representado como um valor absoluto (acima), e como uma porcentagem do número de sessões (abaixo), juntamente com os pontos percentuais (p.p) de aumento ou diminuição no funil de vendas. Ao passar o cursor sobre a porcentagem, você pode ver mais detalhes sobre essa etapa intermediária.
 
 ## Categorias com maior receita
-![Categorias PT](https://images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/18f8e56b4d93e7a89ca021153a73eb8e/Categorias_PT.png)
+![Categorias PT](//images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/18f8e56b4d93e7a89ca021153a73eb8e/Categorias_PT.png)
 
 Este gráfico indica as dez categorias da sua loja que geraram mais receita no período selecionado. A barra azul indica a receita gerada na data mais recente, e a barra cinza indica a receita gerada no período comparado. Ao passar o cursor, o gráfico mostra a taxa de conversão para cada período comparado. Ao clicar no título do gráfico é possível mudar a visualização para __Categorias mais vendidas por pedido__.
 
diff --git a/docs/tutorials/pt/store-profile.md b/docs/tutorials/pt/store-profile.md
new file mode 100644
index 000000000..7d06d9a8e
--- /dev/null
+++ b/docs/tutorials/pt/store-profile.md
@@ -0,0 +1,86 @@
+---
+title: 'Perfil da Loja'
+id: 72qjh4BIc9ppKsbEpdBKoo
+status: PUBLISHED
+createdAt: 2023-07-19T21:17:55.736Z
+updatedAt: 2023-07-19T21:29:37.370Z
+publishedAt: 2023-07-19T21:29:37.370Z
+firstPublishedAt: 2023-07-19T21:29:37.370Z
+contentType: tutorial
+productTeam: Channels
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: perfil-da-loja
+locale: pt
+legacySlug: perfil-da-loja
+subcategory: 6riYYNZCpO8wyksi8Ksgyq
+---
+
+A VTEX disponibiliza em seu Admin as páginas **[Encontrar sellers](https://help.vtex.com/tutorial/encontrar-sellers--6kkZaxIgfDyvN5trgIuwBl)** e **[Marketplaces e Integrações](https://help.vtex.com/en/tutorial/marketplaces-and-integrations--5AcBO1t29nhq7rBHas9b6V).** Ambas têm como objetivo disponibilizar e facilitar o encontro e comunicação entre sellers e marketplaces que operam no ecossistema VTEX, abrindo a possibilidade de novos negócios e crescimento mútuo para todos os envolvidos.
+
+Para contatar os potenciais parceiros presentes nessas listas, é necessário ativar o perfil da sua loja, como marketplace, seller ou ambos. Isso é feito na página Perfil da loja em, **Marketplace > Perfil da loja** ou digitando **Perfil da loja** na barra de busca.
+
+## <a name="informacoes-da-loja"></a>Informações da loja
+
+Os dados preenchidos na seção de Informações da loja não serão aplicadas no seu storefront, mas sim nas páginas *Encontrar sellers* e *Marketplaces e Integrações.*
+
+- **Logo**: imagem do logo da sua loja, com tamanho máximo de 500kB.
+- **Nome da loja:** nome comercial da sua loja.
+- **Segmento do Negócio:** o mercado em que a loja está inserida, selecionado
+a partir das opções na listagem.
+- **País**: país onde a sede, ou principal operação da loja está situada.
+- **Link do ecommerce:** URL do site oficial da marca.
+- **Selecione os estados onde sua loja faz entrega:** caixas de seleção para cada estado.
+
+## Ativando Perfil de seller
+
+Se você deseja atuar somente como seller e disponibilizar os seus produtos em outros marketplaces, será necessário ativar o seu perfil de seller seguindo os passos e recomendações abaixo.
+
+1. Na seção *Marketplace* do seu Admin VTEX, clique em **Perfil da loja** ou digite **Perfil da loja** na barra de busca.
+2. Preencha o formulário com as **[Informações da loja](#informações-da-loja)**.
+3. Preencha a seção **[Perfil de seller](#preenchendo-o-perfil-do-seller)**.
+4. Clique em **Termos e condições de uso do Marketplace Network**. Deslize a tela, para ler toda a declaração de Termos e Condições.
+5. Clique no botão `Salvar alterações`.
+
+### <a name="preenchendo-o-perfil-do-seller"></a>Preenchendo o Perfil de seller
+
+Para realizar o preenchimento do Perfil de seller, você deverá clicar no ícone <i class="fas fa-toggle-on"></i>, para iniciar o processo de preenchimento do perfil. Após preenchido e clicar em `Salvar alterações`, sua loja estará visível ou oculta na página **Encontrar sellers** para os marketplaces.
+
+Veja abaixo os campos e orientações para o preenchimento da seção.
+
+- **Descrição**: texto com até 1200 caracteres, descrevendo sua loja e operação, que aparecerá em seu perfil. Sugerimos que inclua detalhes da sua operação como SLA de entrega, cobertura logística, quais as principais categorias do seu mix de produtos, entre outros.
+- **Nome do responsável pelo contato:** nome da pessoa responsável pelo contato com potenciais parceiros. Sugerimos que seja a pessoa da sua equipe que já é responsável pela atração de parceiros.
+- **Email**: endereço de email da pessoa responsável pelo contato com potenciais parceiros. Garanta que é um endereço de email válido, pois é lá que as mensagens enviadas para a sua loja irão chegar.
+- **Telefone**: número de telefone da pessoa responsável pelo contato com potenciais parceiros.
+- **Usar uma mensagem padrão:** mensagem criada pela loja para ser o padrão nas comunicações que marketplaces irão ver no campo `Enviar uma mensagem`, ao clicar em seu perfil. Mesmo ativando essa opção, é possível editar a mensagem antes de enviá-la para o potencial parceiro.
+
+## Ativando Perfil de marketplace
+
+Se você deseja atuar somente como marketplace e vender os produtos de outros sellers em seu ambiente de venda, será necessário ativar o seu perfil de marketplace seguindo os passos abaixo.
+
+1. Na seção *Marketplace* do seu Admin VTEX, clique em **Perfil da loja** ou digite **Perfil da loja** na barra de busca.
+2. Preencha o formulário com as **[Informações da loja](#informacoes-da-loja)**.
+3. Preencha a seção **[Perfil de marketplace](#preenchendo-perfil-de-marketplace)**.
+4. Clique em **Termos e condições de uso do Marketplace Network**. Deslize a tela, para ler toda a declaração de Termos e Condições.
+5. Clique no botão `Salvar alterações`.
+
+### <a name="preenchendo-perfil-de-marketplace"></a>Preenchendo Perfil de marketplace
+
+Para realizar o preenchimento do Perfil de marketplace, você deverá clicar no ícone <i class="fas fa-toggle-on"></i>, para iniciar o processo de preenchimento do perfil. Após preenchido e clicar em `Salvar alterações`, sua loja estará visível ou oculta na página **Marketplaces e Integrações** para sellers.
+
+Veja abaixo os campos e orientações para o preenchimento da seção.
+
+- **Descrição**: texto com até 1200 caracteres, descrevendo sua loja e operação, que aparecerá em seu perfil. Sugerimos que inclua detalhes da sua operação como categorias de maior receita, políticas de cobrança, comissão sobre produtos, se permite que o seller processe o pagamento, entre outros.
+- **Nome do responsável pelo contato:** nome da pessoa responsável pelo contato com potenciais parceiros. Sugerimos que seja a pessoa da sua equipe que já é responsável pela atração de parceiros.
+- **Email**: endereço de email da pessoa responsável pelo contato com potenciais parceiros. Garanta que é um endereço de email válido, pois é lá que as mensagens enviadas para a sua loja irão chegar.
+- **Telefone**: número de telefone da pessoa responsável pelo contato com potenciais parceiros.
+- **Usar uma mensagem padrão:** mensagem personalizada que sellers verão como padrão no campo Enviar uma mensagem, ao clicar em seu perfil. Mesmo ativando essa opção, é possível editar a mensagem antes de enviá-la para o potencial parceiro.
+
+## Recomendações
+
+Ao interagir com as páginas **Encontrar sellers** e **Marketplaces e Integrações**, fique atento às seguintes recomendações para aproveitar a funcionalidade ao máximo:
+
+- Ao preencher o perfil da sua loja, coloque o site oficial da marca.
+- Sugerimos colocar o contato de funcionários já especializados e responsáveis por atração de parceiros.
+- Garanta que o email e telefone cadastrados sejam válidos e atualizados.
+- Mantenha seu perfil sempre atualizado com os links e informações adequadas sobre a empresa.
+- Escreva um resumo atrativo sobre sua loja. O seu perfil é o que aparece na listagem em **[Encontrar Sellers](https://help.vtex.com/tutorial/encontrar-sellers--6kkZaxIgfDyvN5trgIuwBl)** e **[Marketplaces e integrações](https://help.vtex.com/en/tutorial/marketplaces-and-integrations--5AcBO1t29nhq7rBHas9b6V)**, por isso é importante dar contexto e falar dos seus diferenciais.
diff --git a/docs/tutorials/pt/store-settings-overview.md b/docs/tutorials/pt/store-settings-overview.md
index 4bb4157ac..0f51b7917 100644
--- a/docs/tutorials/pt/store-settings-overview.md
+++ b/docs/tutorials/pt/store-settings-overview.md
@@ -3,8 +3,8 @@ title: 'Visão Geral Configurações da Loja'
 id: 6VtlMoid6iM9dP14X1CopT
 status: PUBLISHED
 createdAt: 2023-03-29T23:00:51.439Z
-updatedAt: 2023-03-29T23:07:38.446Z
-publishedAt: 2023-03-29T23:07:38.446Z
+updatedAt: 2023-09-13T22:38:50.560Z
+publishedAt: 2023-09-13T22:38:50.560Z
 firstPublishedAt: 2023-03-29T23:07:38.446Z
 contentType: tutorial
 productTeam: Management
@@ -17,13 +17,11 @@ subcategory: 5RAUzLD6X9Wa1maenj1eGA
 
 **Configurações da Loja** são as configurações aplicadas à sua loja, o que inclui o seu storefront. Elas estão agrupadas na seção __Configurações da Loja__, no menu de navegação esquerdo do Admin VTEX. Aqui, você pode acessar as configurações aplicadas às seguintes seções: Pagamentos, Pedidos, Templates de Email, Produtos, Storefront, Canais e Intelligent Search.
 
-Para acessar esse recurso, clique no ícone de __Configurações da Loja__ no menu de navegação à esquerda, e então clique na seção desejada.
+Para acessar esse recurso, clique em __Configurações da Loja__ no menu de navegação à esquerda, e então clique na seção desejada.
 
 <div class="alert alert-warning" role="alert">
 Observe que as páginas e as configurações definidas no ambiente anterior não foram alteradas, apenas reorganizadas no menu lateral do Admin, mudando a forma como você as acessa.
-  </div>
-
-![Admin v4 Store settings menu PT](https://images.ctfassets.net/alneenqid6w5/2EIX54YHzIivbQjreHGV4B/794611f3616f225deb26e20cb74f77ae/Admin_v4_Store_settings_menu_PT.jpg)
+</div>
 
 Veja abaixo mais detalhes sobre as diferentes seções e páginas deste menu.
 
diff --git a/docs/tutorials/pt/styles-overview.md b/docs/tutorials/pt/styles-overview.md
index a16dd89f8..b4a761895 100644
--- a/docs/tutorials/pt/styles-overview.md
+++ b/docs/tutorials/pt/styles-overview.md
@@ -19,7 +19,7 @@ A página **Estilos** permite que você defina a tipografia e a paleta de cores
 
 Para acessar a seção Estilos, entre no Admin VTEX, acesse **Storefront > Estilos** e descubra as principais ferramentas disponíveis na interface.
 
-![Estilos - Visão geral](https://images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/e4118ab1f6d82ffdb0c093068c93759b/PT.png)
+![Estilos - Visão geral](//images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/e4118ab1f6d82ffdb0c093068c93759b/PT.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Para aplicar e prever mudanças nos estilos da sua loja, certifique-se de utilizar um workspace que suporte o tráfego de produção, como um <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">workspace de produção</a>. 
diff --git a/docs/tutorials/pt/subscription-plans.md b/docs/tutorials/pt/subscription-plans.md
index 94e6c4d09..f1d3050f2 100644
--- a/docs/tutorials/pt/subscription-plans.md
+++ b/docs/tutorials/pt/subscription-plans.md
@@ -21,7 +21,7 @@ Para disponibilizar planos de assinatura, você precisa antes instalar o aplicat
 
 A partir da página **Planos**, você pode visualizar e gerenciar os planos de assinaturas disponibilizados para os clientes da sua loja, conforme ilustrado abaixo.
 
-![planslist PT](https://images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/a727c14ea5611ca6da8bb6207ef3b09a/planslist_PT.png)
+![planslist PT](//images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/a727c14ea5611ca6da8bb6207ef3b09a/planslist_PT.png)
 
 As principais funcionalidades desta página são:
 
diff --git a/docs/tutorials/pt/synonym-list.md b/docs/tutorials/pt/synonym-list.md
new file mode 100644
index 000000000..269294d76
--- /dev/null
+++ b/docs/tutorials/pt/synonym-list.md
@@ -0,0 +1,112 @@
+---
+title: 'Lista de sinônimos'
+id: 3E1fi0C6tVrR0klMFXAaU8
+status: PUBLISHED
+createdAt: 2024-06-07T13:18:30.251Z
+updatedAt: 2024-06-17T13:55:16.006Z
+publishedAt: 2024-06-17T13:55:16.006Z
+firstPublishedAt: 2024-06-17T13:43:23.975Z
+contentType: tutorial
+productTeam: Marketing & Merchandising
+author: 1malnhMX0vPThsaJaZMYm2
+slug: lista-de-sinonimos
+locale: pt
+legacySlug: lista-de-sinonimos
+subcategory: BBzMtJan1UTxC9QZODnlN
+---
+
+A página de **Sinônimos** possibilita visualizar e gerenciar todos os [sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do Intelligent Search cadastrados na sua loja. Para acessá-la no Admin VTEX, clique em **Storefront > Intelligent Search > Sinônimos**.
+
+![lista-sinonimos-pt](//images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/df0221f5313f7218c943a6f5f58b1088/lista-sinonimos-pt.PNG)
+
+A página apresenta as seguintes informações em uma tabela: 
+
+<table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
+  <thead>
+    <tr class="bb b--muted-3">
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Colunas</th>
+      <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descrição</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Termos</td>
+      <td class="t-body pa5">
+        Termos definidos como sinônimos e indicação do tipo de sinônimo:
+        <ul>
+          <li><i class="fas fa-exchange-alt"></i> Bidirecional</li>
+          <li><i class="fas fa-long-arrow-alt-right"></i> Unidirecional</li>
+        </ul>
+        Saiba mais sobre cada um em
+        <a
+          href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV#tipos-de-sinonimos"
+          target="_blank"
+          rel="noopener noreferrer"
+          >Tipos de sinônimos</a>.
+      </td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Criada em</td>
+      <td class="t-body pa5">Data de criação dos sinônimos.</td>
+    </tr>
+    <tr class="bb b--muted-3">
+      <td class="t-body pa5">Status</td>
+      <td class="t-body pa5">
+        Situação dos sinônimos, que pode ser:
+        <ul>
+          <li>Ativa</li>
+          <li>Inativa</li>
+        </ul>
+      </td>
+    </tr>
+  </tbody>
+</table>
+
+Esta página permite que você realize as seguintes ações:
+
+* [Criar um sinônimo](#criar-um-sinonimo)
+* [Importar sinônimo](#importar-sinonimo)
+* [Buscar sinônimos](#buscar-sinonimos)
+* [Filtrar sinônimos](#filtrar-sinonimos)
+* [Editar sinônimo](#editar-sinonimo)
+* [Deletar sinônimo](#deletar-sinonimo)
+
+## Criar um sinônimo
+
+Você pode criar sinônimos individualmente a partir do botão `Criar sinônimo`. Siga as instruções descritas em [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#criar-sinonimos-individualmente).
+
+## Importar sinônimos
+
+É possível criar sinônimos em massa pela importação de um arquivo CSV, a partir do botão `Importar`. Confira as instruções descritas em [Configurar Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#importar-csv) para entender o template da planilha e como fazer upload dela.
+
+## Buscar sinônimos
+
+A página de **Sinônimos** possibilita buscar por qualquer termo configurado como sinônimo utilizando a barra de busca. Os sinônimos listados são atualizados automaticamente.
+
+## Filtrar sinônimos
+
+Você pode filtrar a listagem de sinônimos a partir das seguintes opções:
+
+* **Status**
+    * Ativa
+    * Inativa
+* **Data de criação**
+    * Hoje
+    * Ontem
+    * Últimos 7 dias
+    * Últimos 15 dias
+    * Últimos 30 dias
+    * Últimos 3 meses
+    * Últimos 12 meses
+
+## Editar sinônimo
+
+Para editar um sinônimo cadastrado, clique na linha correspondente a ele na listagem de sinônimos. Saiba mais sobre os campos editáveis em [Configurar sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL#criar-sinonimos-individualmente).
+
+## Deletar sinônimo
+
+Para deletar um sinônimo, siga o passo a passo abaixo:
+
+1. Passe o mouse sobre a linha do sinônimo
+2. Clique no ícone de lixeira <i class="fas fa-trash-alt"></i>.
+3. Clique em `Excluir` para confirmar.
diff --git a/docs/tutorials/pt/table-of-base-prices.md b/docs/tutorials/pt/table-of-base-prices.md
index d85aae2b7..66dae4f96 100644
--- a/docs/tutorials/pt/table-of-base-prices.md
+++ b/docs/tutorials/pt/table-of-base-prices.md
@@ -44,7 +44,7 @@ Os próximos campos são opcionais na planilha, exportados somente para exibiç
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/2XX0xwgVreVnFb6U2rjJR7/8a4d5893336315d414078ff7518d83ca/baseprices_table.png" style="display: block; margin-left: auto; margin-right: auto;" alt="base prices table" title="base prices table">
+    <img src="https://images.ctfassets.net/alneenqid6w5/2XX0xwgVreVnFb6U2rjJR7/8a4d5893336315d414078ff7518d83ca/baseprices_table.png" style="display: block; margin-left: auto; margin-right: auto;" alt="base prices table" title="base prices table">
    </td>
   </tr>
   <tr>
diff --git a/docs/tutorials/pt/telesales-features.md b/docs/tutorials/pt/telesales-features.md
index 1945ef3b2..36adff0cb 100644
--- a/docs/tutorials/pt/telesales-features.md
+++ b/docs/tutorials/pt/telesales-features.md
@@ -1,10 +1,10 @@
 ---
 title: 'Funcionalidades de televendas'
 id: UqhiccIRIK2KD0OqkzJaS
-status: PUBLISHED
+status: CHANGED
 createdAt: 2021-05-13T18:26:51.189Z
-updatedAt: 2023-03-07T00:19:05.776Z
-publishedAt: 2023-03-07T00:19:05.776Z
+updatedAt: 2023-12-20T16:58:46.983Z
+publishedAt: 2023-10-18T17:09:06.185Z
 firstPublishedAt: 2021-05-17T12:07:02.897Z
 contentType: tutorial
 productTeam: Post-purchase
diff --git a/docs/tutorials/pt/telesales-toolbar.md b/docs/tutorials/pt/telesales-toolbar.md
index 758257b33..1b732d1c3 100644
--- a/docs/tutorials/pt/telesales-toolbar.md
+++ b/docs/tutorials/pt/telesales-toolbar.md
@@ -3,8 +3,8 @@ title: 'Toolbar de televendas'
 id: tutorials_5500
 status: PUBLISHED
 createdAt: 2017-04-27T21:48:31.368Z
-updatedAt: 2023-03-29T19:50:13.858Z
-publishedAt: 2023-03-29T19:50:13.858Z
+updatedAt: 2023-12-07T15:29:46.537Z
+publishedAt: 2023-12-07T15:29:46.537Z
 firstPublishedAt: 2017-04-27T23:11:19.311Z
 contentType: tutorial
 productTeam: Shopping
@@ -19,7 +19,7 @@ A toolbar de televendas é uma barra superior exibida no site da loja para usuá
 
 A toolbar aparece uma vez que o operador cadastrado faz o login no ambiente da loja e é exibida em todas as áreas do site.
 
-![toolbartelevendas PT](https://images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/14d47a02678e01865dfcfc304647f1f2/toolbartelevendas_PT.png)
+![toolbartelevendas PT](//images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/14d47a02678e01865dfcfc304647f1f2/toolbartelevendas_PT.png)
 
 Veja abaixo os principais recursos da toolbar:
 *   [Entrar como cliente](#entrar-como-cliente)
@@ -57,8 +57,9 @@ Ao clicar no nome do cliente, o operador pode visualizar as informações abaixo
 
 ## Artigos relacionados
 
-*   [Como criar um usuário televendas](https://help.vtex.com/pt/tutorial/como-criar-um-usuario-de-televendas--frequentlyAskedQuestions_4227)
-*   [Customizar a Toolbar de televendas](https://help.vtex.com/pt/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg)
-*   [Pedidos](https://help.vtex.com/pt/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#pedidos)
-*   [Como utilizar as funcionalidades de televendas](https://help.vtex.com/pt/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS)
-*   [Como configurar as funcionalidades de televendas](https://help.vtex.com/pt/tutorial/como-configurar-as-funcionalidades-de-televendas--76FNgQP2Glc4umMJ5Yr50R)
+* [Perfis de acesso predefinidos - Call center operator](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#call-center-operator)
+* [Como criar um usuário televendas](https://help.vtex.com/pt/tutorial/como-criar-um-usuario-de-televendas--frequentlyAskedQuestions_4227)
+* [Customizar a Toolbar de televendas](https://help.vtex.com/pt/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg)
+* [Pedidos](https://help.vtex.com/pt/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#pedidos)
+* [Como utilizar as funcionalidades de televendas](https://help.vtex.com/pt/tutorial/funcionalidades-de-televendas--UqhiccIRIK2KD0OqkzJaS)
+* [Como configurar as funcionalidades de televendas](https://help.vtex.com/pt/tutorial/como-configurar-as-funcionalidades-de-televendas--76FNgQP2Glc4umMJ5Yr50R)
diff --git a/docs/tutorials/pt/test-kr1.md b/docs/tutorials/pt/test-kr1.md
new file mode 100644
index 000000000..dad975dab
--- /dev/null
+++ b/docs/tutorials/pt/test-kr1.md
@@ -0,0 +1,18 @@
+---
+title: 'Test KR1'
+id: 4IbRozfaZJHar1adTlr1yq
+status: DRAFT
+createdAt: 2024-06-07T18:51:10.051Z
+updatedAt: 2024-06-07T18:52:10.590Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: VTEX IO
+author: 
+slug: test-kr1
+locale: pt
+legacySlug: test-kr1
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+
diff --git a/docs/tutorials/pt/teste.md b/docs/tutorials/pt/teste.md
index 372fb1a5b..6776de554 100644
--- a/docs/tutorials/pt/teste.md
+++ b/docs/tutorials/pt/teste.md
@@ -21,7 +21,7 @@ Este é apenas um teste do markdown-renderer.
 16. Em __Chave Secreta do Aplicativo__, clique no botão __Mostrar__.
     - Copie o campo __ID do Aplicativo__ e cole no campo `Client Id` no admin do VTEX ID.
     - Copie o campo __Chave Secreta do Aplicativo__ do Aplicativo do Facebook e cole no campo `Client Secret` no admin do VTEX ID.
-    ![ID Chave Facebook PT](https://images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/ae15499ad9a86bc2adc92ec7907d30f6/ID_Chave_Facebook_PT.png)
+    ![ID Chave Facebook PT](//images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/ae15499ad9a86bc2adc92ec7907d30f6/ID_Chave_Facebook_PT.png)
 
 1. LoremIpsum
 16. Em __Chave Secreta do Aplicativo__, clique no botão __Mostrar__.
diff --git a/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md b/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md
new file mode 100644
index 000000000..1f8798282
--- /dev/null
+++ b/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md
@@ -0,0 +1,46 @@
+---
+title: 'O pedido foi dividido em pacotes com entregas distintas'
+id: 3OCOC82543vOsc3Ex32XTY
+status: PUBLISHED
+createdAt: 2024-06-19T15:03:37.373Z
+updatedAt: 2024-06-19T15:13:11.172Z
+publishedAt: 2024-06-19T15:13:11.172Z
+firstPublishedAt: 2024-06-19T15:13:11.172Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: o-pedido-foi-dividido-em-pacotes-com-entregas-distintas
+locale: pt
+legacySlug: o-pedido-foi-dividido-em-pacotes-com-entregas-distintas
+subcategory: 2Q0IQjRcOqSgJTh6wRHVMB
+---
+
+**Tags / Palavras-chave:** entregas distintas, split de pedido, pacotes, remessa, produtos de pré-venda.
+
+Na VTEX, há situações em que o cliente recebe seu pedido dividido em vários pacotes, independentemente de haver ou não uma [divisão do pedido](https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV) na plataforma. O cliente pode receber os itens do pedido em pacotes distintos nos seguintes casos:
+
+* **Pedido com diferentes sellers:** é gerado um pedido para cada seller e haverá pelo menos um pacote correspondendo à entrega de cada seller.
+* **Seleção de sellers white label:** quando envolve [sellers white label](https://help.vtex.com/pt/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa), a entrega do pedido pode ser feita em pacotes diferentes.
+* **Seller com diferentes SLAs para envio dos itens:** mesmo se o pedido for atendido por um único seller, se os itens tiverem diferentes SLAs, o pedido poderá ser dividido em pacotes distintos.
+* **Produtos de pré-venda:** quando o pedido inclui tanto [produtos de pré-venda](https://help.vtex.com/pt/tutorial/cadastrar-um-produto-para-pre-venda--4o6cUJ4gIg0MQWW8WfN34K) quanto produtos normais, a entrega será feita em pacotes diferentes.
+
+No caso de produtos de pré-venda, quando o pedido é gerado, tanto os produtos pré-venda quanto os produtos normais têm a mesma data de entrega no checkout, mas isto é apenas uma estimativa da entrega. Após a aprovação do pagamento, o pedido é dividido em pacotes diferentes, sendo um pacote para os produtos de pré-venda e outro para os produtos normais. 
+
+A data de entrega de cada pacote é alterada de acordo com o valor do `shippingEstimateDate` de cada produto, e esse campo pode ser verificado através do endpoint [Get order](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-).
+
+## Solução
+
+Para evitar uma divisão de pacotes em pedidos que incluam produtos de pré-venda, você pode configurar o [agrupamento de produtos por remessa](https://help.vtex.com/pt/tutorial/como-funciona-a-remessa). Desta forma, é possível agrupar em um único conjunto todos os pacotes a serem entregues pela mesma transportadora e provenientes da mesma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
+
+<div class="alert alert-danger">
+Ao configurar o agrupamento da remessa, esse comportamento será aplicado a todos os pedidos com datas de entrega distintas e não somente aos casos envolvendo produtos de pré-venda.
+</div>
+
+### Configurando a remessa
+
+Para configurar a remessa na sua loja, siga os passos abaixo: 
+
+1. No Admin VTEX, acesse **Configurações da loja > Envio > Configurações**, ou digite **Envio** na barra de busca no topo da página e selecione **Configurações da loja / Envio**.
+2. Na página **Configurações gerais**, na seção **Agrupar produtos na mesma remessa**, preencha o campo _Criar grupos de remessa com intervalos de {X} dia(s)_ com o número de dias que deseja definir para a [remessa](https://help.vtex.com/pt/tutorial/como-funciona-a-remessa).
+3. Clique em **Salvar**.
+
diff --git a/docs/tutorials/pt/the-price-in-the-search-result-is-different-from-the-product-page.md b/docs/tutorials/pt/the-price-in-the-search-result-is-different-from-the-product-page.md
index 9893771d7..c8439abd4 100644
--- a/docs/tutorials/pt/the-price-in-the-search-result-is-different-from-the-product-page.md
+++ b/docs/tutorials/pt/the-price-in-the-search-result-is-different-from-the-product-page.md
@@ -3,8 +3,8 @@ title: 'Preço do resultado de busca é diferente da página de produto'
 id: 1108Xha3zw6ZvVUINfY7HR
 status: PUBLISHED
 createdAt: 2022-11-22T14:26:20.489Z
-updatedAt: 2022-11-22T14:42:50.738Z
-publishedAt: 2022-11-22T14:42:50.738Z
+updatedAt: 2024-06-04T12:45:41.670Z
+publishedAt: 2024-06-04T12:45:41.670Z
 firstPublishedAt: 2022-11-22T14:42:50.738Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -12,7 +12,7 @@ author: 2o8pvz6z9hvxvhSoKAiZzg
 slug: preco-do-resultado-de-busca-e-diferente-da-pagina-de-produto
 locale: pt
 legacySlug: preco-do-resultado-de-busca-e-diferente-da-pagina-de-produto
-subcategory: 4tkE7m5rJisNuhJisIxWHD
+subcategory: 23NGhMgqA1eCYad7kzRFGu
 ---
 
 Durante a [atualização de preço de um SKU](https://help.vtex.com/pt/tutorial/alteracao-de-preco-de-sku--tutorials_95), é possível que o preço do resultado de busca apresente uma divergência com o preço ou estoque  da página de produto, caso a loja use o [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb). 
diff --git a/docs/tutorials/pt/tools-to-help-the-performance-of-your-e-commerce.md b/docs/tutorials/pt/tools-to-help-the-performance-of-your-e-commerce.md
index 3d370fa07..72212f981 100644
--- a/docs/tutorials/pt/tools-to-help-the-performance-of-your-e-commerce.md
+++ b/docs/tutorials/pt/tools-to-help-the-performance-of-your-e-commerce.md
@@ -1,10 +1,10 @@
 ---
 title: 'Ferramentas para melhorar a performance da loja'
 id: tutorials_4852
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:49:27.344Z
-updatedAt: 2020-07-26T15:27:37.237Z
-publishedAt: 2020-07-26T15:27:37.237Z
+updatedAt: 2024-03-11T13:20:56.413Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:11:17.373Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/pt/tracking-your-sales-analytics.md b/docs/tutorials/pt/tracking-your-sales-analytics.md
index f2a42f090..34de764a1 100644
--- a/docs/tutorials/pt/tracking-your-sales-analytics.md
+++ b/docs/tutorials/pt/tracking-your-sales-analytics.md
@@ -1,10 +1,10 @@
 ---
 title: 'Acompanhando a evolução das suas vendas'
 id: 5QtyTR0jFy9gDnr4EYCjdq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2020-09-10T13:32:39.637Z
-updatedAt: 2020-09-11T00:16:35.791Z
-publishedAt: 2020-09-11T00:16:35.791Z
+updatedAt: 2023-10-18T15:24:34.576Z
+publishedAt: 
 firstPublishedAt: 2020-09-10T17:37:50.007Z
 contentType: tutorial
 productTeam: Management
@@ -38,7 +38,7 @@ O horário de referência para os dados é indicado na interface, com uma defasa
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/2f8tj5XokKtnZOvjfgmFVf/8766d35f81efb2710d048d67618781b0/Insights_-_Conhecendo_a_interface.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Conhecendo a interface" title="Insights - Conhecendo a interface">
+    <img src="https://images.ctfassets.net/alneenqid6w5/2f8tj5XokKtnZOvjfgmFVf/8766d35f81efb2710d048d67618781b0/Insights_-_Conhecendo_a_interface.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Conhecendo a interface" title="Insights - Conhecendo a interface">
    </td>
   </tr>
   <tr>
@@ -57,7 +57,7 @@ Este painel permite comparar o valor consolidado das métricas entre os dias sel
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/5lKQrdbytYWAaMV3tHnOi4/0235b8bc175e3a3575b37caf68760d0d/Insights_-_Visa__o_Geral.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Visão Geral" title="Insights - Visão Geral">
+    <img src="https://images.ctfassets.net/alneenqid6w5/5lKQrdbytYWAaMV3tHnOi4/0235b8bc175e3a3575b37caf68760d0d/Insights_-_Visa__o_Geral.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Visão Geral" title="Insights - Visão Geral">
    </td>
   </tr>
   <tr>
@@ -76,7 +76,7 @@ Este painel permite acompanhar a evolução das métricas ao longo do dia. Ao ar
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/L43eNghJLlakmOFcGmKiM/b33fac8dc56733bd1c8bec7ffcf50dbc/Insights_-_Detalhes.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 1" title="Insights - Detalhes 1">
+    <img src="https://images.ctfassets.net/alneenqid6w5/L43eNghJLlakmOFcGmKiM/b33fac8dc56733bd1c8bec7ffcf50dbc/Insights_-_Detalhes.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 1" title="Insights - Detalhes 1">
    </td>
   </tr>
   <tr>
@@ -91,7 +91,7 @@ Este painel permite acompanhar a evolução das métricas ao longo do dia. Ao ar
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/1TExoNJjCZInwh3LGQrkzO/9f3552d7e67b8916f740eb8113e9ed65/image11.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 2" title="Insights - Detalhes 2">
+    <img src="https://images.ctfassets.net/alneenqid6w5/1TExoNJjCZInwh3LGQrkzO/9f3552d7e67b8916f740eb8113e9ed65/image11.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Detalhes 2" title="Insights - Detalhes 2">
    </td>
   </tr>
   <tr>
@@ -117,7 +117,7 @@ Este painel permite acompanhar o volume de sessões nas etapas intermediárias d
 <table width="100%">
   <tr>
    <td>
-    <img src="https:https://images.ctfassets.net/alneenqid6w5/4DdN3hdCz7CdoukLu3H0Ea/0284cb7630896fbf4f45e63ddd9506e0/Insights_-_Funil_de_conversa__o.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Funil de conversão" title="Insights - Funil de conversão">
+    <img src="https://images.ctfassets.net/alneenqid6w5/4DdN3hdCz7CdoukLu3H0Ea/0284cb7630896fbf4f45e63ddd9506e0/Insights_-_Funil_de_conversa__o.png" style="display: block; margin-left: auto; margin-right: auto;" alt="Insights - Funil de conversão" title="Insights - Funil de conversão">
    </td>
   </tr>
   <tr>
diff --git a/docs/tutorials/pt/transactional-emails-for-subscription-orders.md b/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
index 5cacfdd00..88c9f086b 100644
--- a/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
@@ -3,8 +3,8 @@ title: 'E-mails Transacionais para pedidos de Assinatura'
 id: 2NYHqHMRqZ43Cn6s84ZCB5
 status: PUBLISHED
 createdAt: 2020-02-11T15:13:38.504Z
-updatedAt: 2021-11-30T18:14:37.654Z
-publishedAt: 2021-11-30T18:14:37.654Z
+updatedAt: 2023-12-21T14:14:10.536Z
+publishedAt: 2023-12-21T14:14:10.536Z
 firstPublishedAt: 2020-02-17T21:15:14.903Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -28,6 +28,10 @@ Também é possível criar seu próprio template de e-mail. Entenda melhor como
 
 ## Como seu cliente acompanha seus Pedidos de Assinatura
 
+<div class = "alert alert-info">
+Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
+</div>
+
 Cada ação, ocorrida dentro do fluxo de pedidos de Assinatura, contém um gatilho que dispara um e-mail notificando o seu cliente. Após a ativação da Assinatura, seu cliente receberá e-mails com detalhes do estado de cada pedido da assinatura toda vez que realizar uma ação. 
 
 Não é preciso ativar o envio de e-mails manualmente, pois são enviados de forma automática de acordo com cada cenário incluído na Central de Mensagens. Porém, se desejar, é possível desativar o envio de e-mails específicos:
@@ -39,7 +43,7 @@ Não é preciso ativar o envio de e-mails manualmente, pois são enviados de for
 5. Desmarque a caixa `Ativar envio de e-mail?`, que por default, vem marcada como ativa.
 6. Clique em **Salvar**.
 
-![PT Subscription Message Center](https://images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
+![PT Subscription Message Center](//images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
 
 ## Templates default da Central de Mensagens
 
diff --git a/docs/tutorials/pt/transactions-events.md b/docs/tutorials/pt/transactions-events.md
index 8bf7b2898..c7ec73972 100644
--- a/docs/tutorials/pt/transactions-events.md
+++ b/docs/tutorials/pt/transactions-events.md
@@ -77,5 +77,5 @@ Geralmente as afiliações permitem que você configure uma data agendada de cap
 
 Aqui você consegue ver a data do agendamento da captura automática:
 
-![captura-auto-agendada pt](https://images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
+![captura-auto-agendada pt](//images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
 
diff --git a/docs/tutorials/pt/transferring-store-ownership.md b/docs/tutorials/pt/transferring-store-ownership.md
index 24467d81f..84c52f598 100644
--- a/docs/tutorials/pt/transferring-store-ownership.md
+++ b/docs/tutorials/pt/transferring-store-ownership.md
@@ -25,7 +25,7 @@ A página de Gerenciamento de Titular permite identificar o usuário Titular atu
 
 Você deverá ver uma tela semelhante à imagem abaixo, com informações de contato do usuário Titular atual, um aviso indicando os riscos associados à transferência de propriedade da loja e um botão para confirmar que você reconhece os riscos e deseja transferir a propriedade mesmo assim.
 
-![Painel de gerenciamento de titular](https://images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/5bfcb540546580d2f584550ce67a04a4/Sponsor_Management_pt.png)
+![Painel de gerenciamento de titular](//images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/5bfcb540546580d2f584550ce67a04a4/Sponsor_Management_pt.png)
 
 ## Etapas do fluxo de transferência de propriedade
 
diff --git a/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
index b505a61e1..7fed93247 100644
--- a/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
@@ -3,8 +3,8 @@ title: 'Como solucionar erros em pedidos de assinaturas'
 id: uLL8AYBGdtAmbbdL5gRCf
 status: PUBLISHED
 createdAt: 2020-02-05T14:32:49.763Z
-updatedAt: 2022-12-05T17:09:40.639Z
-publishedAt: 2022-12-05T17:09:40.639Z
+updatedAt: 2023-12-21T14:07:42.772Z
+publishedAt: 2023-12-21T14:07:42.772Z
 firstPublishedAt: 2020-02-11T15:00:00.666Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: como-solucionar-pedidos-de-assinatura-com-erros
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
+<div class = "alert alert-info">
+É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
+</div>
+
 É possível identificar e gerenciar erros em pedidos de assinaturas através do módulo de **Assinaturas** > **Dashboards** > **Pedidos de Assinatura** no Admin.
 
 Existem dois tipos de erros que podem ocorrer com pedidos de assinaturas:
@@ -28,7 +32,7 @@ Problemas em ciclos de assinaturas acontecem quando há um problema que impede a
 
 A aba **Ciclos com problema**, ilustrada na imagem abaixo, reúne os pedidos de assinaturas que apresentam problemas desse tipo.
 
-![cicloscomproblema PT](https://images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/ee04171d3d9c785e049382f1e927b715/cicloscomproblema_PT.png)
+![cicloscomproblema PT](//images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/ee04171d3d9c785e049382f1e927b715/cicloscomproblema_PT.png)
 
 A partir dessa aba, é possível gerenciar os pedidos que apresentam ciclos com problema e fazer novas tentativas manuais de criação de pedidos. Por exemplo, quando um produto está indisponível, você pode ajustar o estoque e, em seguida, fazer a nova tentativa.
 
@@ -185,7 +189,7 @@ Erros de pagamento são os que acontecem durante o fluxo de aprovação do pagam
 
 Pedidos com esse tipo de erro podem ser visualizados na aba **Erro de Pagamento**, ilustrada na imagem abaixo.
 
-![errosdepagamento PT](https://images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/305350275dedd4e7c7888814db9fab07/errosdepagamento_PT.png)
+![errosdepagamento PT](//images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/305350275dedd4e7c7888814db9fab07/errosdepagamento_PT.png)
 
 Para analisar erros de pagamento, confira o passo a passo a seguir.
 
@@ -193,7 +197,7 @@ Para analisar erros de pagamento, confira o passo a passo a seguir.
 2. Clique na aba **Dashboards**.
 3. Na seção **Pedidos de Assinatura**, clique na aba **Erro de Pagamento**.
 4. Identifique o pedido desejado e clique na ID do pedido, conforme ilustrado na imagem abaixo. Você será redirecionado à página de detalhes do pedido, no módulo de **Todos os pedidos**.
-  ![PT Log Erro de pagamento](https://images.ctfassets.net/alneenqid6w5/7697GbtjQbOutzL1sgrpjV/afdaba25349564a26d46149b437aab2a/PT_Log_Erro_de_pagamento.png)
+  ![PT Log Erro de pagamento](//images.ctfassets.net/alneenqid6w5/7697GbtjQbOutzL1sgrpjV/afdaba25349564a26d46149b437aab2a/PT_Log_Erro_de_pagamento.png)
 5. Uma vez na página de detalhes do pedido, clique em `Ver detalhes da transação`, no card de **Pagamento**. Você será redirecionado à página de **Transações**, no módulo de **Pagamentos**.
 6. Na página de **Transações**, você poderá visualizar e analisar os eventos de transação do pedido. Leia o artigo [Visualizar detalhes da transação no Pagamentos](https://help.vtex.com/pt/tutorial/como-visualizar-detalhes-do-pedido) para mais informações.
 
diff --git a/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md b/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md
index b6ecae274..518e65070 100644
--- a/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md
+++ b/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md
@@ -53,7 +53,7 @@ Com os dados do cadastro em mãos, siga as instruções abaixo para acesso:
 4. Clique em __ENTRAR.__
 
 <p align="center">
-  <img src="https://https://images.ctfassets.net/alneenqid6w5/3a3HtOlFA2xpLn5UsufytL/affee1c9cccda41ad54258fd8e99e09d/tela1seriousblack.png" width="250" height="450">
+  <img src="https:////images.ctfassets.net/alneenqid6w5/3a3HtOlFA2xpLn5UsufytL/affee1c9cccda41ad54258fd8e99e09d/tela1seriousblack.png" width="250" height="450">
 </p>
 
 <div class="alert alert-warning">
@@ -75,7 +75,7 @@ Utilize como email de recuperação o mesmo email que foi cadastrado na platafor
 </div>
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/1CSmj8fe1tImUFUT6URnUc/42133d558ae524c9559cac2a13d2a5a8/tela2seriousblack.png" width="250" height="450">
+  <img src="//images.ctfassets.net/alneenqid6w5/1CSmj8fe1tImUFUT6URnUc/42133d558ae524c9559cac2a13d2a5a8/tela2seriousblack.png" width="250" height="450">
 </p>
 
  ## Como fazer uma entrega 
@@ -86,7 +86,7 @@ Para que as rotas estejam disponíveis no aplicativo é necessário que elas sej
 </div>
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/5qjV5bJ7TIcbw1gNMZ41sB/ebd8ec4093e7e46852e0f297d705cac6/tela3seriousblack.png" width="230" height="450">
+  <img src="//images.ctfassets.net/alneenqid6w5/5qjV5bJ7TIcbw1gNMZ41sB/ebd8ec4093e7e46852e0f297d705cac6/tela3seriousblack.png" width="230" height="450">
 </p>
 <div class="alert alert-danger">
   Use a opção <b>PAUSAR</b> com cautela pois ao iniciar novamente a rota, os destinatários receberão notificações do novo início da entrega. 
@@ -113,7 +113,7 @@ Após a inicialização da entrega, o destinatário passa a receber notificaçõ
 3. Clique em __OK__.
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/5t3tVl6Y5y2okAuB50jDkH/b73c7ae1b8a208c22396855e5216c4c8/tela4seriousblack.png" width="230" height="450">
+  <img src="//images.ctfassets.net/alneenqid6w5/5t3tVl6Y5y2okAuB50jDkH/b73c7ae1b8a208c22396855e5216c4c8/tela4seriousblack.png" width="230" height="450">
 </p>
 
 <div class="alert alert-info">
@@ -127,10 +127,10 @@ Essa opção pode também estar disponível antes do início da rota mediante a
   <table class="center">
     <tr>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/7ISKJH3ZW7nEQZkR95hKjk/f51efbf5bcdfe29e73c96728baad3519/tela5seriousblack.png" width="250" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/7ISKJH3ZW7nEQZkR95hKjk/f51efbf5bcdfe29e73c96728baad3519/tela5seriousblack.png" width="250" height="450">
       </td>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/6buR2z5OvycFvz340pLxsI/52aed865af8c9b7d557c99dfda43896d/tela6seriousblack.png" width="250" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/6buR2z5OvycFvz340pLxsI/52aed865af8c9b7d557c99dfda43896d/tela6seriousblack.png" width="250" height="450">
       </td>
     </tr>
   </table>
@@ -143,7 +143,7 @@ Essa opção pode também estar disponível antes do início da rota mediante a
 A forma de reporte da ocorrência está condicionada ao tipo de ocorrência e às configurações realizadas pela empresa de serviço de entrega. Para cada tipo de ocorrência é possível escrever uma descrição do acontecido ou conversar com um atendente da central através do chat. 
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/2WTJMk7dNvdUByoLylUO97/c4cbc37059f858b27d8028053e2fc906/tela7seriousblack.png" width="230" height="450">
+  <img src="//images.ctfassets.net/alneenqid6w5/2WTJMk7dNvdUByoLylUO97/c4cbc37059f858b27d8028053e2fc906/tela7seriousblack.png" width="230" height="450">
 </p>
 
 #### Para descrever uma ocorrência  na tela de dados da entrega: 
@@ -166,10 +166,10 @@ Ao escolher uma ocorrência que tenha possibilidade de abertura de chat, uma men
   <table class="center">
     <tr>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/3ZQ2RVGVA6MbvShNqsp17J/1c951eeb52df1be5a448196243efe277/tela15seriousblack.jpg" width="230" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/3ZQ2RVGVA6MbvShNqsp17J/1c951eeb52df1be5a448196243efe277/tela15seriousblack.jpg" width="230" height="450">
       </td>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/WEC77nf23enBRAKPsciv7/fe4ec937cbd940d67687972842284220/tela13seriousblack.jpg" width="230" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/WEC77nf23enBRAKPsciv7/fe4ec937cbd940d67687972842284220/tela13seriousblack.jpg" width="230" height="450">
       </td>
     </tr>
   </table>
@@ -179,7 +179,7 @@ Ao escolher uma ocorrência que tenha possibilidade de abertura de chat, uma men
 <a id="Pausar_entrega"> Se durante a entrega</a> ocorrerem situações que impossibilitem a entrega e que  não foram resolvidos pelo chat, é possível que o entregador pause o serviço. Com a entrega iniciada basta  clicar no botão __PAUSAR__, a entrega será pausada e você será redirecionado para a tela com a lista de entregas.
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/5KMsyiWbF99kWOHlLR4cLO/78f5f101f39f66d04bcdeea3e80c7645/tela8seriousblack.jpg" width="230" height="450">
+  <img src="//images.ctfassets.net/alneenqid6w5/5KMsyiWbF99kWOHlLR4cLO/78f5f101f39f66d04bcdeea3e80c7645/tela8seriousblack.jpg" width="230" height="450">
 </p>
 
 <div class="alert alert-danger">
@@ -201,17 +201,17 @@ Ao escolher uma ocorrência que tenha possibilidade de abertura de chat, uma men
   <table class="center">
     <tr>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/2DUhdRA98j5Yu624T7ijbL/c43f0721edadb9b5ed6e1e2c162bb70f/tela9seriousblack.jpg" width="230" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/2DUhdRA98j5Yu624T7ijbL/c43f0721edadb9b5ed6e1e2c162bb70f/tela9seriousblack.jpg" width="230" height="450">
       </td>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/1cHo4w1rgx3KoBCxqakhUQ/d17ffbe8675dae79f251cf55dfaa3bee/tela16seriousblack.jpg1.jpg" width="230" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/1cHo4w1rgx3KoBCxqakhUQ/d17ffbe8675dae79f251cf55dfaa3bee/tela16seriousblack.jpg1.jpg" width="230" height="450">
       </td>
     </tr>
   </table>
 </figure>
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/2TyOpvC1TJpo6NWvfXyM0i/79b9e43980bd3b87ab6c577447ecf9e0/tela11seriousblack.jpg" width="450" height="230">
+  <img src="//images.ctfassets.net/alneenqid6w5/2TyOpvC1TJpo6NWvfXyM0i/79b9e43980bd3b87ab6c577447ecf9e0/tela11seriousblack.jpg" width="450" height="230">
 </p>
 
 Ao voltar para a página de finalização, será preciso escrever um comentário sobre a entrega. 
@@ -221,7 +221,7 @@ Ao voltar para a página de finalização, será preciso escrever um comentário
 3. Clique em __OK__.
 
 <p align="center">
-  <img src="https://images.ctfassets.net/alneenqid6w5/36HjG927orqVTwrFHt2KEx/18e923175d20cc82abf005444e3c62cb/tela17seriousblack.jpg" width="230" height="450">
+  <img src="//images.ctfassets.net/alneenqid6w5/36HjG927orqVTwrFHt2KEx/18e923175d20cc82abf005444e3c62cb/tela17seriousblack.jpg" width="230" height="450">
 </p>
 
 Após esses passos, a entrega é finalizada e o  aplicativo  abre uma caixa de diálogo perguntando se você deseja iniciar a próxima entrega da lista. Caso deseje, clique em __SIM__. 
@@ -234,10 +234,10 @@ Se esta caixa de diálogo não abrir automaticamente, na próxima entrega da tel
   <table class="center">
     <tr>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/7FjkM96pbKxqO0Rh82LhvE/9f732c45f20e4b6394f4db2ff02fceb1/tela18.png" width="230" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/7FjkM96pbKxqO0Rh82LhvE/9f732c45f20e4b6394f4db2ff02fceb1/tela18.png" width="230" height="450">
       </td>
       <td>
-        <img src="https://images.ctfassets.net/alneenqid6w5/3U0mEzOmXvI7jKIiibjx9p/c984d37fe5b513a955e984d0b4117aa5/tela19.png" width="230" height="450">
+        <img src="//images.ctfassets.net/alneenqid6w5/3U0mEzOmXvI7jKIiibjx9p/c984d37fe5b513a955e984d0b4117aa5/tela19.png" width="230" height="450">
       </td>
     </tr>
   </table>
diff --git a/docs/tutorials/pt/understand-your-balance.md b/docs/tutorials/pt/understand-your-balance.md
index ad8de0387..eafd1be0f 100644
--- a/docs/tutorials/pt/understand-your-balance.md
+++ b/docs/tutorials/pt/understand-your-balance.md
@@ -32,7 +32,7 @@ A box apresenta dois valores. O primeiro, __Disponível__, apresenta o saldo em
  
 Porém, isso não significa que você já pode movimentar o saldo completo. Os valores só podem ser movimentados depois que o recebível for liquidado na conta, que ocorre na data predeterminada de cada recebível.  
 
-![saldo_VTEXPAYMENT](https://images.ctfassets.net/alneenqid6w5/3gxHd6hbhoTaKTJAe5IFBJ/08939976b6a113437a5852310ea3b467/image.png)
+![saldo_VTEXPAYMENT](//images.ctfassets.net/alneenqid6w5/3gxHd6hbhoTaKTJAe5IFBJ/08939976b6a113437a5852310ea3b467/image.png)
 
 ### Como calcular o saldo a receber?
 
diff --git a/docs/tutorials/pt/understanding-b2b-orders.md b/docs/tutorials/pt/understanding-b2b-orders.md
index 71f32105a..8dc1b708a 100644
--- a/docs/tutorials/pt/understanding-b2b-orders.md
+++ b/docs/tutorials/pt/understanding-b2b-orders.md
@@ -19,7 +19,7 @@ Na operação de um e-commerce B2B, frequentemente é necessário informar o sta
 
 O app **Pedidos B2B** simplifica este processo, permitindo que qualquer funcionário possa consultar os pedidos feitos pela sua empresa pela própria loja virtual.
 
-![orders VTEX B2B](https://images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
+![orders VTEX B2B](//images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
 
 Essa experiência de autosserviço é possível graças a uma integração via API com o ERP. Com isso, o funcionário pode buscar pedidos por:
 
diff --git a/docs/tutorials/pt/understanding-how-indexation-works.md b/docs/tutorials/pt/understanding-how-indexation-works.md
index fad3d3400..a8f94958f 100644
--- a/docs/tutorials/pt/understanding-how-indexation-works.md
+++ b/docs/tutorials/pt/understanding-how-indexation-works.md
@@ -3,8 +3,8 @@ title: 'Como funciona a indexação'
 id: tutorials_256
 status: PUBLISHED
 createdAt: 2017-04-27T22:11:43.688Z
-updatedAt: 2023-03-29T19:50:49.722Z
-publishedAt: 2023-03-29T19:50:49.722Z
+updatedAt: 2024-03-04T16:39:16.578Z
+publishedAt: 2024-03-04T16:39:16.578Z
 firstPublishedAt: 2017-04-27T23:03:11.322Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,6 +15,11 @@ legacySlug: entendendo-o-funcionamento-da-indexacao
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
+<div class="alert alert-warning">
+<p>Tutorial válido apenas para lojas que utilizam a busca do <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>.</p>
+<p>Se a sua loja utiliza o <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>, consulte a página <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Histórico da Indexação</a> para acompanhar o processo de indexação.</p>
+</div>
+
 A indexação é um processo que prepara os dados gerais do SKU, tais como dados de catálogo, de preço e de estoque e atualiza as informações para servir de base para pesquisas e montagens das prateleiras do site.
 
 Toda vez que há alguma alteração como as listadas abaixo em um produto, a reindexação é realizada. 
diff --git a/docs/tutorials/pt/understanding-how-the-cache-works.md b/docs/tutorials/pt/understanding-how-the-cache-works.md
index 8f1cd6d72..31b308223 100644
--- a/docs/tutorials/pt/understanding-how-the-cache-works.md
+++ b/docs/tutorials/pt/understanding-how-the-cache-works.md
@@ -25,11 +25,11 @@ A solicitação do browser é conhecida como **request**, e a resposta do servid
 
 Veja o esquema abaixo:
 
-![Como o cache funciona - comunicação entre servidor e browser](https://images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/51e191e174947c589ad4de6d4d56e474/1_PT.png)
+![Como o cache funciona - comunicação entre servidor e browser](//images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/51e191e174947c589ad4de6d4d56e474/1_PT.png)
 
 O cache é representado através de uma camada entre o browser e o servidor. Assim, quando um **request** acontece, em vez de o sistema ir buscar as informações diretamente no servidor, primeiramente ele vai até essa camada, o que torna a resposta muito mais ágil. Veja o esquema abaixo:
 
-![Como o cache funciona - comunicação com cache (sem expirar)](https://images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/bb35e006ee78f624c403a0d81aefb65a/2_PT.png)
+![Como o cache funciona - comunicação com cache (sem expirar)](//images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/bb35e006ee78f624c403a0d81aefb65a/2_PT.png)
 
 No entanto, como o dado atualizado está no servidor, de tempos em tempos o cache precisa ser atualizado. Esse tempo varia de acordo com o tipo de **request**, ou seja, se o **request** for uma página, o tempo é um, se for um arquivo javascript ou CSS é outro e, ainda, se for uma imagem, outro.
 
@@ -60,7 +60,7 @@ Quando o cache de um **request** (página ou arquivo) expira, ao realizar uma no
 
 Depois de atualizada, a versão cacheada volta a ser retornada para novas solicitações da URL. Veja o esquema ilustrando esse caso:
 
-![Como o cache funciona - comunicação com cache (expirado)](https://images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/369d7e767ed2f09583955cea2d432a36/3_PT.png)
+![Como o cache funciona - comunicação com cache (expirado)](//images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/369d7e767ed2f09583955cea2d432a36/3_PT.png)
 
 Nesse aspecto, podemos separar as respostas em dois grupos: Cacheadas e não cacheadas.
 
diff --git a/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md b/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md
index 6ae75794a..6982af4f1 100644
--- a/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md
+++ b/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md
@@ -15,7 +15,7 @@ legacySlug: conhecendo-o-storebuilder-e-o-stylesbuilder
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-![UI Blocks Voando.mp4](https://images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
+![UI Blocks Voando.mp4](//images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
 
 Esta documentação foi estruturada para explicar os conceitos por tras do StoreBuilder e StyleBuilder da Store 2.xx. Durante toda a documentação, usaremos a DreamStore (um loja template que utiliza a `Store 2.xx`) para entender os principais conceitos que lhe permitirão estruturar e estilizar sua loja.
 
@@ -35,7 +35,7 @@ Esta documentação foi estruturada para explicar os conceitos por tras do Store
 
 Vamos olhar dentro do `/manifest.json` da DreamStore para ver o que nosso aplicativo precisa para funcionar corretamente:
 
-![Screen Shot 2019-01-25 at 16.40.06](https://images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
+![Screen Shot 2019-01-25 at 16.40.06](//images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
 
 Observe como temos dois builders especificados:
 
@@ -54,7 +54,7 @@ Como toda theme app (uma loja) faz uso do aplicativo `Store` (através da depend
 
 Execute "vtex link" e envie o app DreamStore para um workspace para que possamos estudá-lo
 
-![Screen Shot 2019-01-27 at 22.24.47](https://images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
+![Screen Shot 2019-01-27 at 22.24.47](//images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
 
 Se você é familiarizado com  React ou outros frameworks modernos de Javascript , você estará familiarizado com o conceito de componentes em uma página da Web. Como podemos observar, nossa página da Web tem um "cabeçalho", "carrossel" e uma "prateleira". Como esses componentes foram inseridos?
 
@@ -92,7 +92,7 @@ _Por favor, tenha em mente que você não estará desenvolvendo no aplicativo St
 
 Vamos olhar dentro do arquivo `/manifest.json` do Store2.xx para ver o que o aplicativo importa.
 
-![Screen Shot 2019-01-25 at 17.18.56](https://images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
+![Screen Shot 2019-01-25 at 17.18.56](//images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
 
 Podemos ver que é uma estrutura semelhante à do `manifest.json` da `Dreamstore`.
 
@@ -137,7 +137,7 @@ __Como cada página é definida por blocos e organizada por interfaces__, é hor
 Abra a pasta `store` e abra o arquivo `interfaces.json`.
 
 ### Interfaces
-![Screen Shot 2019-01-25 at 17.35.10](https://images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
+![Screen Shot 2019-01-25 at 17.35.10](//images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
 
 Uma interface é um conjunto de `blocks` e existe exclusivamente dentro do `Store2.xx`. Ele serve como um contrato entre os blocos e determina como vão trabalhar juntos.
 
@@ -194,7 +194,7 @@ Vamos continuar analisando o `store.home`. Eu estarei comentando inline.
 ```
 
 Se descermos podemos ver os mesmos objetos JSON definindo e configurando a organização da pagina. Outro exemplo é a página de resultados da pesquisa:
-![Screen Shot 2019-01-25 at 18.22.12](https://images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
+![Screen Shot 2019-01-25 at 18.22.12](//images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
 
 A informação descreve as seguintes informações de interface
   
@@ -216,7 +216,7 @@ Até agora, entendemos que:
 
 ### Estruturando e configurando nossa loja com o `StoreBuilder`
 
-![Codigo voando blocks.mp4](https://images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
+![Codigo voando blocks.mp4](//images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
 
 Abra `/ blocks.json` e encontre o nosso conhecido `store.home`. Vamos começar analisando o primeiro bloco dentro de `store.home : carrossel#home`.
 
@@ -240,12 +240,12 @@ Role para baixo até encontrarmos `carrossel#home`. Através de `props` podemos
   
   
 ### Estilizando nossa loja com o `StylesBuilder`
-![StyleBuilder.mp4](https://images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
+![StyleBuilder.mp4](//images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
 
 
 O StylesBuilder é simples de entender pois pega seu arquivo styles.json durente o build e usa o gerador de [Tachyons](https://tachyons.io/) para produzir o CSS da sua loja.
 
 Nós projetamos o StylesBuilder para ser extremamente intuitivo e autoexplicativo. É tão simples quanto ajustar os códigos hexadecimais adequadamente e ver os resultados permearem por toda a loja.
 
-![Screen Shot 2019-01-28 at 00.40.17](https://images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
+![Screen Shot 2019-01-28 at 00.40.17](//images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
 
diff --git a/docs/tutorials/pt/understanding-the-additional-shipping-cost.md b/docs/tutorials/pt/understanding-the-additional-shipping-cost.md
index 00a8eac01..38baad68c 100644
--- a/docs/tutorials/pt/understanding-the-additional-shipping-cost.md
+++ b/docs/tutorials/pt/understanding-the-additional-shipping-cost.md
@@ -29,7 +29,7 @@ Existem três formas de se adicionar um valor extra sobre o frete: adicional por
 
 O adicional por valor é calculado a partir do preço do produto. É definida uma porcentagem que se aplicará ao preço do produto, e esse valor resultante é adicionado ao valor inicialmente calculado pelo frete. 
 
-![adicionalfrete1 PT](https://images.ctfassets.net/alneenqid6w5/JRCo7yI9iwkS0uYW822eY/32044c9a1d1636d10d9eec1202625fc6/adicionalfrete1_PT.png)
+![adicionalfrete1 PT](//images.ctfassets.net/alneenqid6w5/JRCo7yI9iwkS0uYW822eY/32044c9a1d1636d10d9eec1202625fc6/adicionalfrete1_PT.png)
 
 No caso acima, o valor dos produtos totaliza R$ 80,00 e o valor cadastrado como __Valor adicional__ é 10%. Com isso, o valor calculado para ser adicionado ao valor do frete é de R$ 8,00. A soma do valor final de frete e o valor adicional, é de R$18,00.
 
@@ -46,7 +46,7 @@ O adicional por peso é calculado com base no peso do produto. O cálculo desse
 
 A conta é a seguinte:
 
-![adicionalfrete2 PT](https://images.ctfassets.net/alneenqid6w5/19t4etUFuYCK0sM2SCK4g2/99a0bc4b935a1db688f94795ea3614b3/adicionalfrete2_PT.png)
+![adicionalfrete2 PT](//images.ctfassets.net/alneenqid6w5/19t4etUFuYCK0sM2SCK4g2/99a0bc4b935a1db688f94795ea3614b3/adicionalfrete2_PT.png)
 
 Ou seja, no exemplo, o limite mínimo da faixa de peso que o produto se encontra é de 100 gramas. O valor cadastrado no campo __Valor adicional por peso__ é de 0,1. Logo, o valor a ser adicionado ao cálculo de 14,00, o valor final ficou em R$ 24,00.
 
@@ -62,7 +62,7 @@ O adicional no frete é calculado sobre o valor final do frete, e não sobre o v
 
 O valor cadastrado na tabela de frete + o adicional por peso + o adicional por valor * o valor cadastrado no campo adicional no frete.
 
-![adicionalfrete3 PT](https://images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
+![adicionalfrete3 PT](//images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
 
 Nesse caso, o valor inserido no campo __Valor adicional__, será o valor percentual a ser somado ao valor final calculado do frete. Por exemplo: se o frete, com todos seus adicionais já calculados, der R$20,00 e o valor cadastrado no campo Adicional nos Fretes for 10, significa que será acrescentando R$2,00 aos R$20,00 do frete, totalizando R$ 22,00 a ser cobrado ao cliente pelo frete. Essa é uma maneira simples de conseguir uma margem sobre os fretes das compras.
 
diff --git a/docs/tutorials/pt/understanding-the-cubic-weight-factor.md b/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
index 63b258af1..c906758f7 100644
--- a/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
@@ -3,8 +3,8 @@ title: 'Calcular o fator cúbico de peso'
 id: tutorials_128
 status: PUBLISHED
 createdAt: 2017-04-27T22:17:52.970Z
-updatedAt: 2022-11-08T19:15:57.550Z
-publishedAt: 2022-11-08T19:15:57.550Z
+updatedAt: 2023-12-19T17:17:26.713Z
+publishedAt: 2023-12-19T17:17:26.713Z
 firstPublishedAt: 2017-04-27T23:00:44.419Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -23,10 +23,10 @@ A cubagem é a relação existente entre o volume e o peso da mercadoria, que é
 
 A função da cubagem no transporte é evitar que se ocupe todo o espaço físico do veículo sem utilizar toda a sua capacidade em peso ou vice-versa. Desta forma, o conceito de cubagem está ligado à capacidade de se preencher a carga de um veículo utilizando-se todo o seu volume disponível para carga e capacidade de peso ou tonelagem.
 
-- __Peso Real:__ é aquele indicado na balança.
-- __Peso Cubado:__ é a forma de cálculo que determina o espaço efetivamente ocupado pelo pacote no veículo de transporte.
+- __Peso mínimo:__ é aquele indicado na balança.
+- __Peso cúbico:__ é a forma de cálculo que determina o espaço efetivamente ocupado pelo pacote no veículo de transporte.
 
-## Fator de Cubagem
+## Fator de cubagem
 
 O fator de cubagem é o coeficiente resultante da relação entre peso e volume mais adequada e comercialmente justa à cubagem de aeronaves, conforme recomendado pela IATA (entidade internacional que congrega as empresas aéreas).
 
@@ -34,30 +34,30 @@ O fator de cubagem é o coeficiente resultante da relação entre peso e volume
 
 O cálculo do peso cubado é realizado efetuando a multiplicação do Comprimento pela Largura e pela Altura e, em seguida, a divisão pelo Fator de cubagem fornecido pela transportadora.
 
+<div class="alert alert-warning">
+Ao realizar o cálculo do peso cúbico, a plataforma VTEX não utiliza unidades de medida e os números gerados são absolutos. Ou seja, os números e medidas que você levar em consideração serão aqueles do resultado final. Vale ressaltar que a unidade de medida do seu cálculo deve ser igual àquela utilizada pela transportadora em questão.
+</div>
+
 Observe o exemplo a seguir:
 
 ![](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
 
 - __Dimensões do pacote:__ `50cm x 60cm x 15cm`
-- __Peso real do pacote:__ `9kg`
+- __Peso mínimo do pacote:__ `9kg`
 - __Fator de cubagem:__ `6.000`
-- __Peso cubado:__ `50cm * 60cm * 15cm / 6.000 = 7,5kg`
+- __Peso cúbico:__ `50cm * 60cm * 15cm / 6.000 = 7,5kg`
 
-Ao comparar o peso real com o peso cubado do pacote, a transportadora fará a cobrança pelo peso real, pois ele é maior que o peso cubado.
+Ao comparar o peso mínimo com o peso cúbico do pacote, a transportadora fará a cobrança pelo peso mínimo, pois ele é maior que o peso cubado.
 
 Porém, o cálculo acima é apenas ilustrativo. Na transportadora, o valor cadastrado como fator cúbico será multiplicado ao produto de `Comprimento x Largura x Altura`. Ou seja, o cálculo a ser feito será `Comprimento x Largura x Altura x Fator Cúbico`.
 
-Ou seja, caso o valor oferecido pela sua transportadora `6.000`, é necessário primeiro realizar o cálculo onde este valor dividirá 1.000: Exemplo: `1.000 / 6.000 = 0,167`.
+Ou seja, caso o valor oferecido pela sua transportadora `6.000`, é necessário primeiro realizar o cálculo onde este valor dividirá 1.000: Exemplo: `1000g/6000 cm³ = 0,167`.
 
-Ao realizar o cadastro da sua transportadora, esse é o valor que você deve preencher no campo __Fator Cúbico de Peso__.
+Ao realizar o cadastro da sua transportadora, esse é o valor que você deve preencher no campo **Fator de peso cúbico** na sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 
-![PesoCubado](//images.contentful.com/alneenqid6w5/ZzHF9fwwec6c6m2AiyYGS/37343a8bb4858cdf296f5a3c450567f3/PesoCubado.png)
+![cubic_weight_PT](//images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/dffa4cf86d504ec7325bb80b7b26704d/cubic_weight_PT.png)
 
 Portanto, o cálculo final seria:
 - __Dimensões do pacote:__ `50cm x 60cm x 15cm`
-- __Peso real do pacote:__ 9kg
-- __Peso cubado__: `50cm x 60cm x 15cm x 0,167 = 7.515kg`
-
-<div class="alert alert-info">
-  <p>Verifique com sua transportadora se a unidade de medidas está em gramas, que é a unidade utilizada na VTEX.</p>
-</div>
+- __Peso mínimo do pacote:__ `9kg`
+- __Peso cúbico__: `50cm x 60cm x 15cm x 0,167 = 7.515kg`
diff --git a/docs/tutorials/pt/understanding-the-message-center.md b/docs/tutorials/pt/understanding-the-message-center.md
index e703dead4..7caec06b5 100644
--- a/docs/tutorials/pt/understanding-the-message-center.md
+++ b/docs/tutorials/pt/understanding-the-message-center.md
@@ -33,7 +33,7 @@ Entenda as informações que cada _card_ do template traz:
 
 Para facilitar a navegação a interface disponibiliza, além do campo de busca por texto livre, filtros por aplicações (módulos) e tipo (mensagem padrão ou personalizada/alterada).
 
-![busca-templates-central-mensagens pt](https://images.ctfassets.net/alneenqid6w5/QbPAmXYUeIwUqsugGkw40/c489a00144a36b78df59ba4eb4cc539c/busca-templates-central-mensagens_pt.png)
+![busca-templates-central-mensagens pt](//images.ctfassets.net/alneenqid6w5/QbPAmXYUeIwUqsugGkw40/c489a00144a36b78df59ba4eb4cc539c/busca-templates-central-mensagens_pt.png)
 
 Depois de entender o básico sobre os templates, você já pode ver como editá-los. Esse passo não é obrigatório, pois a VTEX fornece um layout básico e responsivo para todas as mensagens, com os dados necessários para uma boa comunicação com seu cliente, mas é natural que as lojas os adequem ao padrão de comunicação já usado para a marca.
 
diff --git a/docs/tutorials/pt/understanding-the-price-change-rule.md b/docs/tutorials/pt/understanding-the-price-change-rule.md
index 52c950c94..7c0d870c7 100644
--- a/docs/tutorials/pt/understanding-the-price-change-rule.md
+++ b/docs/tutorials/pt/understanding-the-price-change-rule.md
@@ -26,6 +26,6 @@ Esse bloqueio também é realizado para todas as demais formas de atualização
 
 O percentual da __trava de preço__ pode ser removido ou alterado nas __Configurações__ do módulo de __Preços__.
 
-![trava-variação-preço pt](https://images.ctfassets.net/alneenqid6w5/5anjARjLAk0sCKgEEoWCK8/c148b88625482f6fb9ca35373ab69fe7/trava-varia____o-pre__o_pt.png)
+![trava-variação-preço pt](//images.ctfassets.net/alneenqid6w5/5anjARjLAk0sCKgEEoWCK8/c148b88625482f6fb9ca35373ab69fe7/trava-varia____o-pre__o_pt.png)
 
 Alguns marketplaces também possuem esta trava de variação de preços. Caso você deseje alterar os preços para além dos ranges da trava, basta entrar em contato com o marketplace solicitando a alteração. 
diff --git a/docs/tutorials/pt/understanding-the-security-report.md b/docs/tutorials/pt/understanding-the-security-report.md
index 785a268d4..24246f138 100644
--- a/docs/tutorials/pt/understanding-the-security-report.md
+++ b/docs/tutorials/pt/understanding-the-security-report.md
@@ -31,7 +31,7 @@ Siga o passo a passo para acessar o relatório:
 
 O exemplo abaixo ilustra o filtro para uma alteração (seja criação ou atualização) de preço de um SKU. Para isso, é necessário utilizar os campos __Dados__ com o Id do SKU, __Tela__ com o local da plataforma onde ocorre essa alteração e um período de tempo específico. De acordo com o relatório que se deseja, pode ser necessário usar outros campos em conjunto ou em substituição a esses.
 
-![relatoriosegurançaPT](https://images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/beca72120562bfd90fa0b81965fcf2be/relatorio-seguranca-pt.gif)
+![relatoriosegurançaPT](//images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/beca72120562bfd90fa0b81965fcf2be/relatorio-seguranca-pt.gif)
 
 Confira a seção a seguir para entender todos os campos disponíveis para filtrar o relatório.
 
diff --git a/docs/tutorials/pt/understanding-the-topbar.md b/docs/tutorials/pt/understanding-the-topbar.md
index 0d43f5412..66d681c75 100644
--- a/docs/tutorials/pt/understanding-the-topbar.md
+++ b/docs/tutorials/pt/understanding-the-topbar.md
@@ -19,16 +19,16 @@ A sidebar é o ponto de partida para todas as áreas do admin VTEX. Abaixo, voc
 
 **Navegue entre os módulos**: Para isso, basta clicar sobre o simbolo da VTEX à sua esquerda. Na barra lateral que se abrirá, basta clicar sobre o nome do módulo desejado para acessá-lo.
 
-![paginainicial.pt](https://images.ctfassets.net/alneenqid6w5/9od439KuVjDIGM1iFrBRc/75561521e641b3f19488b4e5e5897a9b/ppaginainicial.pt.png)
+![paginainicial.pt](//images.ctfassets.net/alneenqid6w5/9od439KuVjDIGM1iFrBRc/75561521e641b3f19488b4e5e5897a9b/ppaginainicial.pt.png)
 
 **Navegue entre os subdomínios**: Para navegar entre os subdomínios de sua loja, basta clicar sobre o domínio atual. Você visualizará todas as opções. Para ir para o admin de um dos subdomínios, basta clicar sobre ele no menu.
 
-![subdominios.pt](https://images.ctfassets.net/alneenqid6w5/4U9sb38voR0peYq5FQS5cI/ff7c5aef5d05a5cb98d53087f0552a45/subdominios.pt.png)
+![subdominios.pt](//images.ctfassets.net/alneenqid6w5/4U9sb38voR0peYq5FQS5cI/ff7c5aef5d05a5cb98d53087f0552a45/subdominios.pt.png)
 
 **Selecione o idioma do admin**: Para selecionar o idioma, basta clicar sobre o ícone de idioma e selecionar o desejado.
-![idioma.pt](https://images.ctfassets.net/alneenqid6w5/1scR4VdnKvmExP9kRGeDGy/c880564e43448077d0fee2fd8336ea49/idioma.pt.png)
+![idioma.pt](//images.ctfassets.net/alneenqid6w5/1scR4VdnKvmExP9kRGeDGy/c880564e43448077d0fee2fd8336ea49/idioma.pt.png)
 
 **Acesse nossas bases de conhecimento**: Para acessar uma de nossas bases, clique sobre seu perfil de suporte e selecione o local que deseja acessar, clicando sobre ele.
-![support.pt](https://images.ctfassets.net/alneenqid6w5/7h9sRBe9lVGqqS1NpX9c5J/9bd14d91177a930317fd1137f34a8188/support.pt.png)
+![support.pt](//images.ctfassets.net/alneenqid6w5/7h9sRBe9lVGqqS1NpX9c5J/9bd14d91177a930317fd1137f34a8188/support.pt.png)
 
 **Faça o logoff**: Para realizar o logoff, basta clicar sobre seu nome e clicar sobre o link **Sair**.
diff --git a/docs/tutorials/pt/understanding-the-updating-of-the-xml.md b/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
index 20065b67b..10f65a2a6 100644
--- a/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
@@ -3,8 +3,8 @@ title: 'Como funciona a atualização do XML'
 id: tutorials_297
 status: PUBLISHED
 createdAt: 2017-04-27T22:09:31.811Z
-updatedAt: 2019-12-31T15:28:59.361Z
-publishedAt: 2019-12-31T15:28:59.361Z
+updatedAt: 2024-02-29T14:57:59.233Z
+publishedAt: 2024-02-29T14:57:59.233Z
 firstPublishedAt: 2017-04-27T23:03:14.354Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/pt/understanding-vtexs-email-capture-system.md b/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
index 76c731fff..164062ad0 100644
--- a/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
@@ -3,8 +3,8 @@ title: 'Captura de email'
 id: 15oNhcDa7HA8ztfJnpvhmJ
 status: PUBLISHED
 createdAt: 2022-10-17T19:51:45.533Z
-updatedAt: 2022-10-17T19:55:21.831Z
-publishedAt: 2022-10-17T19:55:21.831Z
+updatedAt: 2023-07-20T17:49:29.730Z
+publishedAt: 2023-07-20T17:49:29.730Z
 firstPublishedAt: 2022-10-17T19:53:55.523Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: entendendo-o-sistema-de-captura-de-email-da-vtex
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
-O objetivo deste artigo é mostrar como o e-mail de um usuário é recebido no CRM do [Master Data](https://help.vtex.com/pt/subcategory/visao-geral-do-master-data--5gtjaqCG7eIseyCI0aSqc2#). Para isto, será demonstrado como o **Checkout**, **RC.JS** e **Master Data** trabalham em conjunto para capturar as informações de e-mail de um novo usuário.
+O objetivo deste artigo é mostrar como o e-mail de um usuário é recebido no CRM do [Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw). Para isto, será demonstrado como o **Checkout**, **RC.JS** e **Master Data** trabalham em conjunto para capturar as informações de e-mail de um novo usuário.
 
 Para melhor compreensão, iremos apresentar um cenário (dividido em 3 etapas), onde o usuário conclui sua compra com sucesso e o pedido é encaminhado ao OMS, enquanto o seu e-mail é transmitido de forma segura para o Master Data. Neste contexto, as ações do usuário e o fluxo da plataforma ocorrem na seguinte ordem:
 
@@ -51,4 +51,4 @@ Para que a função do <a href="https://help.vtex.com/pt/tutorial/acesse-o-carri
 Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
 </div>
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
diff --git a/docs/tutorials/pt/untitled-entry-2024-03-13-at-16-25-15.md b/docs/tutorials/pt/untitled-entry-2024-03-13-at-16-25-15.md
new file mode 100644
index 000000000..2d51d3d1d
--- /dev/null
+++ b/docs/tutorials/pt/untitled-entry-2024-03-13-at-16-25-15.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 4GN2eQe58qKvEaLA4u7Cl8
+status: DRAFT
+createdAt: 2024-03-13T16:25:15.804Z
+updatedAt: 2024-03-13T16:25:21.748Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: 
+author: 
+slug: untitled-entry-2024-03-13-at-16-25-15
+locale: pt
+legacySlug: untitled-entry-2024-03-13-at-16-25-15
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/pt/untitled-entry-2024-07-25-at-21-25-31.md b/docs/tutorials/pt/untitled-entry-2024-07-25-at-21-25-31.md
new file mode 100644
index 000000000..8a1071606
--- /dev/null
+++ b/docs/tutorials/pt/untitled-entry-2024-07-25-at-21-25-31.md
@@ -0,0 +1,18 @@
+---
+title: ''
+id: 3eu2vU8e9uMF7eNHJMHcYU
+status: DRAFT
+createdAt: 2024-07-25T21:25:31.372Z
+updatedAt: 2024-07-25T21:25:33.666Z
+publishedAt: 
+firstPublishedAt: 
+contentType: tutorial
+productTeam: 
+author: 
+slug: untitled-entry-2024-07-25-at-21-25-31
+locale: pt
+legacySlug: untitled-entry-2024-07-25-at-21-25-31
+subcategory: 
+---
+
+
diff --git a/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md b/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md
index c027e04c8..b75014f35 100644
--- a/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md
+++ b/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md
@@ -45,7 +45,7 @@ _Unidades disponíveis = unidades da última atualização - unidades reservadas
 
 O estoque negativo normalmente ocorre quando há atualização na quantidade de itens de um SKU de um pedido em que os produtos já estavam reservados no inventário. Para evitar essa situação, é importante que a atualização da quantidade de SKUs ocorra com pedidos com status posterior a `Preparando entrega`. Dessa forma, a [reserva já terá sido reconhecida](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona/#reserva-reconhecida) e não haverá conflito entre os itens do inventário com os itens que de fato estão disponíveis para venda.
 
-![gerenciar inventario](https://images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/9ce03695fdd2173d9fa079ab2887eb68/gerenciar_inventario.gif)
+![gerenciar inventario](//images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/9ce03695fdd2173d9fa079ab2887eb68/gerenciar_inventario.gif)
 
 ## Artigos relacionados
 
diff --git a/docs/tutorials/pt/using-recaptcha-at-checkout.md b/docs/tutorials/pt/using-recaptcha-at-checkout.md
index 31a9f9bfe..246ba99ce 100644
--- a/docs/tutorials/pt/using-recaptcha-at-checkout.md
+++ b/docs/tutorials/pt/using-recaptcha-at-checkout.md
@@ -3,8 +3,8 @@ title: 'reCAPTCHA no Checkout'
 id: 18Te3oDd7f4qcjKu9jhNzP
 status: PUBLISHED
 createdAt: 2021-08-03T12:53:12.155Z
-updatedAt: 2023-03-21T17:52:28.440Z
-publishedAt: 2023-03-21T17:52:28.440Z
+updatedAt: 2023-12-11T22:07:06.233Z
+publishedAt: 2023-12-11T22:07:06.233Z
 firstPublishedAt: 2021-08-03T13:51:19.441Z
 contentType: tutorial
 productTeam: Others
@@ -18,7 +18,7 @@ subcategory: 3shmvletqbB206RqbY2vYQ
 
 O reCAPTCHA é uma solução utilizada para validação de usuário real em pedidos que serão pagos com cartão de crédito ou débito. Ele prevê cenários em que programas maliciosos são utilizados para fraudes, evitando acesso de falsos usuários. 
 
-Para dar maior segurança, a VTEX disponibiliza o [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) checkbox e indica aos clientes que o habilitem para proteger a criação e o pagamento de pedidos. Essa versão do reCAPTCHA é otimizada e o usuário deverá apenas clicar no <i class="far fa-check-square"></i> _(checkbox),_ e só será apresentado o desafio de validação caso o Google desconfie do usuário.
+Recomendamos que o habilite para proteger a criação e o pagamento de pedidos na sua loja.
 
 A exigência do reCAPTCHA vai seguir a opção configurada pela loja através da [API de configuração do checkout](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm). Para saber mais sobre a ativação confira este artigo sobre o [uso de reCAPTCHA para integrações](https://developers.vtex.com/vtex-rest-api/docs/recaptcha).
 
@@ -26,7 +26,7 @@ Antes da ativação, é importante atentar-se à:
 
 * **Adequação da interface:** ao ativar a funcionalidade é necessário adequar a interface (web  e mobile) que cria pedidos na conta da sua loja (caso esse passo não seja realizado, a criação dos pedidos será prejudicada). Saiba mais sobre como adequar a interface com o[ guia de reCAPTCHA para integrações.](https://developers.vtex.com/vtex-rest-api/docs/recaptcha)
 * **Consequência para a conta**: a habilitação da funcionalidade implica o seu uso em toda conta, incluindo o uso em todas as lojas e subcontas.
-* **Realização de testes:** para realizar testes da funcionalidade é necessário uma um [ambiente Beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu),e utilizar do [Checkout V6](https://help.vtex.com/pt/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH). 
+* **Realização de testes:** para realizar testes da funcionalidade sem impacto na loja em produção use o [ambiente Beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) com [Checkout V6](https://help.vtex.com/pt/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH). 
 
 ## Regra de aplicação
 
@@ -36,7 +36,21 @@ A opção recomendada pela VTEX é a [VTEX criteria](https://developers.vtex.com
 
 Sua intenção é buscar o menor volume de uso necessário (focando na experiência do usuário), mas sem deixar de aplicar a proteção necessária. As sessões tidas como confiáveis ficam isentas de reCAPTCHA. Assim, o reCAPTCHA só é ativado para sessões potencialmente maliciosas.
 
-## Experiência de compra com VTEX Criteria
+## Versões do reCAPTCHA
+
+A VTEX está integrada com o reCAPTCHA enterprise, que oferece duas abordagens de validação: checkbox (equivalente ao [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display)) e baseada em pontuação (equivalente ao [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3)). Confira a tabela abaixo para saber qual versão se aplica a sua operação.
+
+| **Características da loja**                        | **Versão do reCAPTCHA** |
+|----------------------------------------------------|-------------------------|
+| Frente de loja nativa VTEX                         | Checkbox (v2)                      |
+| Frente de loja próprietária para web               | Checkbox (v2) ou Baseada em pontuação (v3)                |
+| Frente de loja próprietária para aplicativo mobile | Baseada em pontuação (v3)                      |
+
+## reCAPTCHA v2
+
+Você pode utilizar reCAPTCHA checkbox (v2). Ou seja, quando aplicável, o usuário deverá apenas clicar no <i class="far fa-check-square"></i> _(checkbox),_ e só será apresentado o desafio de validação caso o Google desconfie do usuário. Veja abaixo mais detalhes sobre a experiência de compra.
+
+### Experiência de compra com VTEX Criteria e reCAPTCHA v2
 
 Levando em consideração os fatores mencionados acima, a experiência de compra com cartão de débito ou crédito tende a seguir o fluxo abaixo. Isso minimiza a incidência de alguns tipos de fraudes e ataques com o mínimo de fricção para o usuário.
 
@@ -46,8 +60,25 @@ Como mostrado na imagem acima, existem diferentes possibilidades de resultado ne
 1. Se o algoritmo do VTEX Criteria não considerar a sessão suspeita, a plataforma prossegue normalmente com a compra.
 
 2. Caso contrário, a interface deverá exibir o reCAPTCHA Checkbox, a qual deverá ser marcada pelo cliente. Se o reCAPTCHA não considerar o comportamento suspeito ao marcar a Checkbox, a compra prossegue normalmente.
-![newCaptchaAnchor](https://images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/f4d75c1fab0fc5789b22fb1b259e7560/newCaptchaAnchor.gif)
+![newCaptchaAnchor](//images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/f4d75c1fab0fc5789b22fb1b259e7560/newCaptchaAnchor.gif)
 3. Se o reCAPTCHA ainda considera o comportamento suspeito, a interface exibirá o desafio.
 ![desafio recaptcha](//images.contentful.com/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/8276208bf8d6db1f086f33df1e8a3641/desafio_recaptcha.png)
 4. Se o desafio for resolvido com sucesso, a plataforma prossegue com a compra. Caso contrário, o comportamento é considerado compatível com o de um bot e a plataforma não finaliza a compra.
 
+## reCAPTCHA v3
+
+O reCAPTCHA baseado em pontuação ([v3](https://developers.google.com/recaptcha/docs/v3)) não interrompe a experiência do usuário na sua loja. Ele analisa as interações no site e retorna uma pontuação entre `1.0` (muito provavelmente uma interação normal) e `0.0` (muito provavelmente um bot).
+
+Ao configurar reCAPTCHA v3 para sua loja VTEX, você tem a opção de definir uma pontuação mínima para [cada chave cadastrada](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#getting-the-recaptcha-key-for-mobile-implementations) e uma [pontuação mínima para a sua loja](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#recaptcha-v3-score). Valores possíveis são `0.1`, `0.3`, `0.7` and `0.9`. 
+
+A prioridade de aplicação da pontuação mínima para uma dada compra é:
+
+```
+Pontuação da chave > Pontuação da conta > Pontuação padrão da VTEX (0.7)
+```
+
+Isso significa que se você definir pontuação mínima para a sua chave e para a sua conta, a pontuação da chave será aplicada. Entretanto, caso você não defina nenhuma pontuação, a VTEX aplicará o valor padrão de `0.7`.
+
+Interações que retornem um valor menor que o mínimo aplicável não serão capazes de finalizar a compra.
+
+Para configurar o reCAPTCHA e definir pontuações mínimas de chaves ou contas, entre em contato com seu time de desenvolvimento e confira o guia de [integração com reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
diff --git a/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 61c68a105..4913ea208 100644
--- a/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -41,7 +41,7 @@ Apps que têm uma dependência de sessão monitoram mudanças nas suas entradas
 
 Transforms frequentemente disparam outras transforms, repetindo até que nenhuma atualização de parâmetro adicional seja enviada por apps. Esta operação é, naturalmente, cautelosamente monitorada para evitar condições de loop. O diagrama abaixo ilustra um exemplo de ciclo de transform:
 
-![EN - Session Manager](https://images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
+![EN - Session Manager](//images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
 
 1. Uma mudança foi feita no parâmetro de sessão X
 2. A App A monitorava o parâmetro de sessão X, o que disparou a Transform 1
diff --git a/docs/tutorials/pt/using-the-project-task-timeline.md b/docs/tutorials/pt/using-the-project-task-timeline.md
index d74510338..7f03870a5 100644
--- a/docs/tutorials/pt/using-the-project-task-timeline.md
+++ b/docs/tutorials/pt/using-the-project-task-timeline.md
@@ -1,10 +1,10 @@
 ---
 title: 'Usar o cronograma de tarefas em seu projeto'
 id: tutorials_1864
-status: PUBLISHED
+status: DRAFT
 createdAt: 2017-04-27T21:55:58.397Z
-updatedAt: 2019-12-31T15:21:08.316Z
-publishedAt: 2019-12-31T15:21:08.316Z
+updatedAt: 2024-03-11T13:20:50.510Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:51.067Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/pt/validating-your-store-and-uploading-it-for-production.md b/docs/tutorials/pt/validating-your-store-and-uploading-it-for-production.md
index a60334972..1eefcd0d3 100644
--- a/docs/tutorials/pt/validating-your-store-and-uploading-it-for-production.md
+++ b/docs/tutorials/pt/validating-your-store-and-uploading-it-for-production.md
@@ -1,10 +1,10 @@
 ---
 title: 'Validar a loja para subir para produção'
 id: tutorials_1419
-status: CHANGED
+status: DRAFT
 createdAt: 2017-04-27T21:56:14.582Z
-updatedAt: 2022-06-01T20:06:41.976Z
-publishedAt: 2019-12-31T15:29:01.968Z
+updatedAt: 2023-07-25T21:07:26.780Z
+publishedAt: 
 firstPublishedAt: 2017-04-27T23:03:49.725Z
 contentType: tutorial
 productTeam: Others
diff --git a/docs/tutorials/pt/via-inventory-integration-errors.md b/docs/tutorials/pt/via-inventory-integration-errors.md
index 3965fd486..d51ffafc9 100644
--- a/docs/tutorials/pt/via-inventory-integration-errors.md
+++ b/docs/tutorials/pt/via-inventory-integration-errors.md
@@ -3,8 +3,8 @@ title: 'Erros de integração de estoque com a Via'
 id: 2jzz4Ip0M2BDzwslEtCzPc
 status: PUBLISHED
 createdAt: 2021-10-26T23:55:47.528Z
-updatedAt: 2023-03-29T14:41:26.271Z
-publishedAt: 2023-03-29T14:41:26.271Z
+updatedAt: 2023-11-30T21:50:54.362Z
+publishedAt: 2023-11-30T21:50:54.362Z
 firstPublishedAt: 2021-10-27T00:08:05.224Z
 contentType: tutorial
 productTeam: Channels
@@ -15,19 +15,19 @@ legacySlug: erros-de-integracao-de-estoque-com-a-via
 subcategory: 7lxg0kyL3TYIsrlSQlf1zP
 ---
 
-Nos marketplaces para os quais a VTEX desenvolveu um [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), por vezes ocorrem erros de integração de estoque. Este artigo reúne os erros mais comuns de integração de estoque com a Via e orienta sobre como solucioná-los.
+Nos marketplaces para os quais a VTEX desenvolveu um [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), por vezes ocorrem erros de integração de estoque. Este artigo reúne os erros mais comuns de integração de estoque com a Casas Bahia Marketplace e orienta sobre como solucioná-los.
 
 Existem mensagens que identificam quais são os erros. Você pode visualizá-las no Admin VTEX, em **MARKETPLACE > Conexões > Estoque**, clicando sobre a mensagem de processo com erro.
 
 Após solucionar um erro, é necessário reprocessar manualmente a integração do estoque daquele SKU. Isso é feito no mesmo local onde o erro é visualizado, clicando em **Ações > Reprocessar**.
 
-Seguem abaixo as mensagens mais comuns de erros de integração de estoque com a Via:
+Seguem abaixo as mensagens mais comuns de erros de integração de estoque com a Casas Bahia Marketplace:
 
 #### Mensagem de erro
 
 `Acesso Negado - Auth-token inválido ou inexistente`
 
-Este erro ocorre devido a problemas com _token_, também chamado de chave de acesso. Para a Via, um _token_ pode ser considerado inválido ou inexistente por diferentes motivos, como prazo de validade expirado, ou suspeita de ameaça à segurança, por exemplo. Neste caso, é necessário entrar em contato com a Via para validar o _token_, por meio do [Portal do Lojista da Via](https://pas.viavarejo.com.br/login?returnUrl=%2F). Após essa validação, corrija as configurações do [cadastro da integração.](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/1okse2MybWk04AQoueu88O) No seu Admin VTEX, vá em **MARKETPLACE > Conexões > Integrações**. No _card_ da Via, clique sobre o ícone <i class="fas fa-cog"></i> engrenagem, e escolha a opção **Editar configuração**. Preencha o campo _Chave de acesso_ com o novo _token_ e clique em **Salvar configuração**.
+Este erro ocorre devido a problemas com _token_, também chamado de chave de acesso. Para a Casas Bahia Marketplace, um _token_ pode ser considerado inválido ou inexistente por diferentes motivos, como prazo de validade expirado, ou suspeita de ameaça à segurança, por exemplo. Neste caso, é necessário entrar em contato com a Casas Bahia Marketplace para validar o _token_, por meio do [Portal do Lojista da Casas Bahia Marketplace](https://pas.viavarejo.com.br/login?returnUrl=%2F). Após essa validação, corrija as configurações do [cadastro da integração.](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY/1okse2MybWk04AQoueu88O) No seu Admin VTEX, vá em **MARKETPLACE > Conexões > Integrações**. No _card_ da Casas Bahia Marketplace, clique sobre o ícone <i class="fas fa-cog"></i> engrenagem, e escolha a opção **Editar configuração**. Preencha o campo _Chave de acesso_ com o novo _token_ e clique em **Salvar configuração**.
 
 ____
 
@@ -35,7 +35,7 @@ ____
 
 `Estoque inexistente para o warehouse. Problemas ao atualizar item.`
 
-Este erro significa que não foi possível identificar um estoque válido na integração com a Via. O problema pode estar relacionado à indisponibilidade de estoque, ou às configurações logísticas da sua [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3).
+Este erro significa que não foi possível identificar um estoque válido na integração com a Casas Bahia Marketplace. O problema pode estar relacionado à indisponibilidade de estoque, ou às configurações logísticas da sua [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3).
 
 Para identificar a causa, faça uma [simulação de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144). A simulação apresenta quais são as possibilidades de envio, e qual a quantidade disponível de itens para um produto. A imagem a seguir apresenta o resultado de uma simulação de envio:
 
@@ -43,18 +43,18 @@ Para identificar a causa, faça uma [simulação de envio](https://help.vtex.com
 
 Quando não há estoque disponível, ou quando existe algum erro nas configurações da sua [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3), o resultado da simulação apresenta o motivo para o insucesso da operação. Neste exemplo, existem algumas transportadoras que não cumpriam as condições necessárias para a entrega do produto.
 
-Erros relacionados à coluna _Transportadora_ são erros de SLA, sigla para _Service Level Agreement_, que é o acordo de serviço firmado entre a loja VTEX e a Via. Erros de SLA significam que algum fator está inviabilizando a entrega do pedido ao consumidor final. Neste caso, é necessário rever as configurações da Estratégia de Envio utilizada na integração com a Via.
+Erros relacionados à coluna _Transportadora_ são erros de SLA, sigla para _Service Level Agreement_, que é o acordo de serviço firmado entre a loja VTEX e a Casas Bahia Marketplace. Erros de SLA significam que algum fator está inviabilizando a entrega do pedido ao consumidor final. Neste caso, é necessário rever as configurações da Estratégia de Envio utilizada na integração com a Casas Bahia Marketplace.
 
 Erros relacionados à coluna _Quantidade disponível_ são erros de estoque, e em geral ocorrem devido a algum dos seguintes fatores:
 
 - **Indisponibilidade de estoque: **um ou mais SKUs do pedido estão indisponíveis, é necessário [atualizar a quantidade de SKUs em estoque](https://help.vtex.com/pt/tutorial/como-atualizar-estoque--2MDwYV1COA6YuoiY22AyGo).
 - **SKU inativo:** o SKU não está ativo, e somente SKUs ativos são integrados. Verifique o status do item no seu Admin, em _PRODUTOS > Catálogo > Produtos e SKU_.
 - **Estoque negativo:** é possível que o [estoque esteja negativo](https://help.vtex.com/pt/tutorial/atualizar-quantidade-de-skus-em-estoque--IKMWjOjMcMqKusSGko8c0#por-que-meu-estoque-esta-negativo). Isso ocorre quando existem mais itens reservados do que a quantidade total disponível em estoque.
-- **Item não consta na coleção ou política comercial:** verifique se o SKU está marcado corretamente na coleção ou política comercial definidos para a integração com a Via. Saiba mais em [Associação de SKU à Política Comercial](https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb).
+- **Item não consta na coleção ou política comercial:** verifique se o SKU está marcado corretamente na coleção ou política comercial definidos para a integração com a Casas Bahia Marketplace. Saiba mais em [Associação de SKU à Política Comercial](https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb).
 
 <br></br>
 ### Saiba mais
 
-- [Integração com a Via Varejo](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY)
+- [Integração com a Casas Bahia Marketplace](https://help.vtex.com/pt/tracks/configurar-integracao-da-via-varejo--3E9XylGaJ2wqwISGyw4GuY)
 - [Controle de estoque mínimo para integrações](https://help.vtex.com/pt/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D)
 - [Configurar o Alerta de Estoque Crítico](https://help.vtex.com/pt/tutorial/configurar-o-alerta-de-estoque-critico--6FD0GHeQPCsKIMgkQ88SGu)
diff --git a/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md b/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md
index e9e51e3bd..1992845ec 100644
--- a/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md
+++ b/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md
@@ -17,7 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 *Configurações de usuário* são o conjunto de configurações aplicadas ao seu perfil pessoal no Admin, e não relacionadas à sua loja ou conta do seu negócio na VTEX. Para acessar essa página, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e clique no botão **Configurações do usuário**. 
 
-![Admin v4 User settings menu PT](https://images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/4128b79a8b245fb113072ca97c5988ae/Admin_v4_User_settings_menu_PT.jpg)
+![Admin v4 User settings menu PT](//images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/4128b79a8b245fb113072ca97c5988ae/Admin_v4_User_settings_menu_PT.jpg)
 
 Nessa página, que em breve estará no design do Admin v4, é possível realizar as seguintes ações:
 
diff --git a/docs/tutorials/pt/vtex-ad-network-beta.md b/docs/tutorials/pt/vtex-ad-network-beta.md
new file mode 100644
index 000000000..e86ec086e
--- /dev/null
+++ b/docs/tutorials/pt/vtex-ad-network-beta.md
@@ -0,0 +1,124 @@
+---
+title: 'VTEX Ad Network (Beta)'
+id: 2cgqXcBuJmXN2livQvClur
+status: CHANGED
+createdAt: 2024-04-23T17:38:07.378Z
+updatedAt: 2024-07-05T13:14:45.135Z
+publishedAt: 2024-07-05T13:13:03.955Z
+firstPublishedAt: 2024-04-23T19:11:42.313Z
+contentType: tutorial
+productTeam: Others
+author: 2Gy429C47ie3tL9XUEjeFL
+slug: vtex-ad-network-beta
+locale: pt
+legacySlug: vtex-ad-network-beta
+subcategory: 2AksvvAtAsbAfE7HsBIVDU
+---
+
+<div class = "alert alert-info">
+<p>O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+O **VTEX Ad Network** conecta lojas VTEX a marcas interessadas em anunciar seus produtos. Com esta conexão, anunciantes e lojas VTEX podem potencializar seu negócio:
+
+- **Anunciantes:** marcas, que podem criar campanhas de anúncios para promover seus produtos nas frentes de lojas VTEX que possuem aqueles produtos em seus catálogos, aumentando suas vendas.
+- **Lojas VTEX:** podem disponibilizar espaço publicitário para que marcas promovam seus produtos na sua frente de loja. Estas lojas receberão um valor por cada clique recebido em anúncios na sua loja.
+
+## Campanhas
+
+Uma campanha do **VTEX Ad Network** é definida pelas seguintes características:
+
+- Produtos promovidos.
+- Orçamento total.
+- Lance, que é o custo por clique (CPC), ou seja, valor que o anunciante está disposto a pagar por cada clique recebido no anúncio. Este valor também determina a [prioridade de diferentes anúncios](#priorizacao-de-anuncios) por um mesmo espaço de exibição. Este valor é definido por produto.
+- Duração.
+- Cobertura, que determina se a campanha vai rodar em todo o Ad Network ou em lojas específicas.
+
+Ao criar uma campanha, o anunciante define um ou mais códigos EAN (código de barras), associados aos produtos que deseja promover. Dessa forma, a VTEX poderá exibir estes anúncios em todas as lojas que vendam aquele produto e que tenham aderido ao **VTEX Ad Network**. Ou, se preferir, o anunciante pode selecionar em quais lojas deseja exibir sua campanha, dentre as possíveis.
+
+## Formato de anúncio
+
+Atualmente, a VTEX disponibiliza um único formato de anúncio: produtos patrocinados. Isso significa que produtos que foram promovidos por anunciantes podem aparecer em um lugar de destaque em alguns contextos onde há listagem de produtos:
+
+- Resultados de busca.
+- Páginas de categorias.
+
+Veja abaixo um exemplo da exibição deste formato:
+
+![vtex_ad_network_sponsored_PT](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
+
+Lojas participantes do **VTEX Ad Network** poderão [configurar a quantidade de espaços de anúncio](https://help.vtex.com/pt/tutorial/advertising-with-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse#criando-uma-campanha) que disponibilizarão em cada um destes contextos na loja.
+
+## Priorização de anúncios
+
+Toda vez que um cliente navega até uma página de loja que têm espaços de anúncios disponíveis, o **VTEX Ad Network** determina que anúncios serão exibidos.
+
+Este processo de priorização ocorre em três etapas:
+
+#### 1. Seleção
+
+- O **VTEX Ad Network** considera o contexto de navegação do cliente, ou seja, termo de busca, categoria ou vitrine, e seleciona campanhas que contêm produtos que se encaixam neste contexto. A plataforma considera inclusive uma pontuação mínima de relevância, para garantir que só serão exibidos anúncios que podem interessar ao cliente.
+- Nesta etapa, a VTEX também considera compatibilidade do ponto de vista de [configurações da campanha](#campanhas) como cobertura e termos de busca negativos.
+
+#### 2. Avaliação de ritmo de gasto
+
+- Nesta etapa, a VTEX pondera o orçamento das campanhas, excluindo campanhas que não tem orçamento disponível e otimizando gastos. Esta otimização é baseada na probabilidade de haver cliques e conversão, com o objetivo de maximizar o sucesso da campanha.
+
+#### 3. Leilão
+
+- A partir dos candidatos selecionados nas etapas anteriores, o **VTEX Ad Network** determina os melhores produtos promovidos para preencher os espaços disponíveis.
+- A plataforma classifica os anúncios com base no seu lance (CPC) e [índice de qualidade](#indice-de-qualidade).
+- Há também um fator de exploração no cálculo do leilão para evitar vieses. Portanto, quanto maior o valor CPC x índice de qualidade, maior a probabilidade de um anúncio ser melhor classificado, mas não há garantia de que será sempre.
+
+Uma vez determinados os anúncios exibidos na página, determina-se o valor dos lances. O lance vencedor do leilão terá o valor final do segundo maior lance mais R$ 0,01.
+
+<div class="alert alert-danger">
+É possível que nenhum anúncio seja selecionado com o processo de priorização, caso não haja produtos promovidos que se encaixem no contexto de navegação, na cobertura de loja ou que não tenham orçamento disponível.
+</div>
+
+### Índice de qualidade
+
+O índice de qualidade de anúncios estima a probabilidade de um usuário clicar no anúncio, baseando-se na taxa de cliques deste anúncio. Este índice influencia na etapa de leilão do processo de [Priorização de anúncios](#priorizacao-de-anuncios). Quanto maior o índice de qualidade, mais provável que um determinado anúncio tenha uma boa classificação no leilão.
+
+### Exemplo de priorização
+
+Considere os seguintes anúncios, de campanhas diferentes, que concorrem em uma mesma loja.
+
+| **Anúncio** | **Produto** | **Índice de qualidade** | **Lance** | **Orçamento** |
+| :---: | :---: | :---: | :---: | :---: |
+| 1 | Perfume A | 10% | R$ 1,00 | R$ 0 |
+| 2 | Perfume B | 1% | R$ 2,00 | R$ 10 |
+| 3 | Perfume C | 10% | R$ 0,90 | R$ 10 |
+| 4 | Xampu A | 5% | R$ 0,50 | R$ 10 |
+
+Imagine que um cliente desta loja acessa a página da categoria **Perfumes**, que contém 300 produtos. Neste caso, o processo de priorização seguiria da seguinte forma:
+
+1. Na etapa de direcionamento, a plataforma descarta o anúncio 4, pois não se encaixa no contexto de navegação do cliente.
+2. Ao avaliar o ritmo, a plataforma descarta o anúncio 1, já que este não possui orçamento disponível.
+3. No leilão, o produto 3 tem uma chance maior de ser classificado em primeiro lugar, considerando **Lance** e **Taxa de conversão**.
+
+## Janela de atribuição
+
+A janela de atribuição do **VTEX Ad Network** é de 15 dias. Isso significa que se um cliente clica em um anúncio de um produto e compra aquele produto até 15 dias depois deste clique, o VTEX Ad Network atribui esta venda ao anúncio.
+
+Caso o cliente compre após esse período, a venda não será atribuída ao anúncio.
+
+## Como fazer parte do VTEX Ad Network
+
+Confira abaixo como você pode fazer parte do **VTEX Ad Network**, seja como [loja](#lojas) que exibe anúncios ou [anunciante](#anunciantes).
+
+### Lojas
+
+<div class="alert alert-warning">
+Por ora, apenas lojas desenvolvidas com <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> podem disponibilizar espaço de anúncios.
+</div>
+
+Para disponibilizar espaço publicitário na sua loja, você precisa entrar em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar a instalação do app __VTEX Ad Network para lojas__ na sua conta VTEX.
+
+Saiba mais sobre as funcionalidades para lojas com o artigo [Exibir anúncios do VTEX Ad Network na sua loja (Beta)](https://help.vtex.com/pt/tutorial/exibir-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA).
+
+### Anunciantes
+
+Qualquer marca que deseja promover seus produtos que já são vendidos em lojas VTEX pode anunciar com **VTEX Ad Network**. Para isso, você precisa entrar em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar a instalação do app __VTEX Ad Network__ na sua conta VTEX.
+
+Saiba mais sobre as funcionalidades disponíveis para anunciantes com o artigo [Anunciar com VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/anunciar-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse).
diff --git a/docs/tutorials/pt/vtex-admin-start-here.md b/docs/tutorials/pt/vtex-admin-start-here.md
index cf57786b8..bfac7ffec 100644
--- a/docs/tutorials/pt/vtex-admin-start-here.md
+++ b/docs/tutorials/pt/vtex-admin-start-here.md
@@ -3,8 +3,8 @@ title: 'Admin VTEX: Comece Aqui'
 id: 531cHtUCUi3puRXNDmKziw
 status: PUBLISHED
 createdAt: 2019-02-04T15:41:26.380Z
-updatedAt: 2023-05-24T18:06:55.015Z
-publishedAt: 2023-05-24T18:06:55.015Z
+updatedAt: 2024-07-03T11:18:48.914Z
+publishedAt: 2024-07-03T11:18:48.914Z
 firstPublishedAt: 2019-02-04T15:51:04.667Z
 contentType: tutorial
 productTeam: Others
@@ -12,14 +12,14 @@ author: 0QBQws7rk0t5Mnu8fgfUv
 slug: admin-vtex-comece-aqui
 locale: pt
 legacySlug: encontre-aqui-todas-as-respostas-que-voce-precisa
-subcategory: 
+subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 ---
 
 O Admin permite que os comerciantes gerenciem toda sua experiência de comércio digital em um só lugar, de uma maneira simples e inteligente.  É onde acompanham pedidos, cadastram produtos, configuram fulfillment e todos os outros aspectos de uma operação de comércio unificado. 
 
 ## Página inicial
 
-![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 A página inicial oferece uma visão geral de alto nível da sua loja, como uma cabine de comando para as suas operações de comércio digital. Por isso, ela se chama [Visão Geral](https://help.vtex.com/pt/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -28,7 +28,14 @@ Assim que você fizer login no Admin, verá métricas e gráficos úteis para mo
 ## Menu de navegação 
 Nossos menus de navegação lateral e barra superior agrupam categorias similares para reduzir as distrações e ajudar a sua equipe a encontrar o que precisa mais rapidamente. 
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![menu de navegação admin SEP2023](//images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/40fe4023fbe2c890f512761ae1ff77ed/admin-navigation.png)
+
+Na topbar, você pode usar a barra de busca global para pesquisar páginas do Admin VTEX ou pedidos da sua loja. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
+
+- ID do pedido
+- Nome do cliente
+- Email do cliente
+- Documento do cliente 
 
 Confira nossos artigos sobre a visão geral de cada menu do seu Admin VTEX, para saber mais sobre sua função e as páginas incluídas em cada seção:
 
@@ -40,7 +47,7 @@ Confira nossos artigos sobre a visão geral de cada menu do seu Admin VTEX, para
 - [Envio](https://help.vtex.com/pt/v4/docs/visao-geral-envio--1hw1otLpTkIjQh4WiBTFYv)
 - [Marketplace](https://help.vtex.com/pt/v4/docs/visao-geral-marketplace--1MwABSIGjYSrFPUXhnUXiV)
 - [Apps](https://help.vtex.com/pt/v4/docs/apps-overview--Abz99oney4PUmrf7QcHc9)
-- [Configurações da Loja](https://help.vtex.com/pt/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4)
+- [Configurações da Loja](https://help.vtex.com/pt/tutorial/visao-geral-configuracoes-da-loja--6VtlMoid6iM9dP14X1CopT)
 - [Configurações da conta](https://help.vtex.com/pt/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r)
 - [Configurações de usuário](https://help.vtex.com/pt/v4/docs/visao-geral-configuracoes-usuario--1qYAvOTZBVYMosJ7tQm3Ry)
 - [Faturas](https://help.vtex.com/pt/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC)
@@ -51,13 +58,47 @@ Também é possível utilizar a barra de busca na parte superior do Admin VTEX p
 
 ### Central de Informações
 
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![central de informações admin SEP2023](//images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/d344e0470f3980a3a7323216e46a95c8/Information_center.gif)
 
 É aqui que reunimos todos os links úteis do nosso ecossistema VTEX, para ajudá-lo(a) a aproveitar a nossa plataforma ao máximo. C Clicando no botão <i class='fa fa-question-circle-o'></i> na barra superior, você pode acessar nosso [Help Center](https://help.vtex.com), [Developer Portal](https://developers.vtex.com/), [Status da Plataforma](https://status.vtex.com/), [blog](https://vtex.com/pt/blog/) e central de suporte.
 
+### Fornecendo feedbacks no Admin VTEX
+
+O botão Enviar feedback permite que um usuário possa enviar comentários a respeito da sua experiência na plataforma por meio do Admin VTEX. Para acessá-lo, siga os passos abaixo:
+1. Clique no botão Central de Informações, localizado no canto superior direito do Admin VTEX.
+2. Clique na opção **Enviar feedback**.
+
+Neste momento um formulário do Google será exibido para que você possa enviar seu feedback. Após o envio, você receberá um email.
+
+![Botão feedback - PT -](//images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/b9b9ecdd1ade0fce9e3a29cd6df1432c/Bot_o_feedback_-_PT_-.gif)
+
+#### Formulário do feedback
+O objetivo principal das perguntas no formulário de feedback é coletar informações detalhadas sobre as experiências e percepções em relação ao produto no Admin VTEX.
+Com essas informações, podemos direcionar nossos esforços de desenvolvimento e suporte para melhor atender às necessidades dos usuários.
+
+##### Descrição dos campos do formulário
+- **Email:** insira seu endereço de email.
+- **URL da página do Admin:** informe a URL da página do Admin relacionada ao feedback.
+
+Tipo de feedback (selecione um ou mais campos): 
+- **Experiência geral:** descreve a experiência geral com o produto.
+- **Funcionalidades:** fornece comentários sobre as características do produto.
+- **Interface e usabilidade:** analisa a interface e usabilidade.
+- **Tradução:** avalia a tradução do conteúdo.
+- **Tempo de carregamento:** verifica a performance sobre o tempo de carregamento.
+- **Outros:** campo disponível para adicionar outro tipo de comentário não coberto anteriormente.
+
+**Descreva seu feedback:** insira detalhes a respeito dos produtos e dos tipos de feedbacks selecionados nas seções anteriores do formulário.
+
+**Uma captura de tela nos ajudará a entender melhor seu feedback (opcional):** campo opcional para adicionar capturas de tela ou documentos que possam nos auxiliar na compreensão do seu feedback.
+
+<div class = "alert alert-info">
+Este processo de envio de feedback não deve ser utilizado para criar um ticket ou solicitação de suporte técnico na VTEX.
+</div>
+
 ### Configurações da conta e do usuário
 
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![configurações de avatar admin SEP2023](//images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/34b6240c3917892dc8c34f2c5efa4afd/Avatar_settings2.gif)
 
 Seu avatar de perfil, reúne todas as configurações relacionadas ao seu usuário e à sua conta. Através do avatar, você pode acessar as [Configurações do usuário](https://help.vtex.com/pt/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Configurações da conta](https://help.vtex.com/pt/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), e [Faturas](https://help.vtex.com/pt/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC), alterar o idioma do seu Admin e encerrar a sessão. 
 
@@ -78,8 +119,6 @@ O Admin VTEX traz uma experiência localizada, incluindo as seguintes opções d
 
 ### Configurações da Loja
 
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
-
 Reunimos todas as configurações de todas as seções do seu Admin VTEX em um menu específico: [Configurações da Loja](https://help.vtex.com/pt/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Por meio dessa melhoria, você pode acessar facilmente todas as configurações que afetam cada serviço da sua operação.
 
 ## Desempenho e compatibilidade 
diff --git a/docs/tutorials/pt/vtex-admin-start-here1.md b/docs/tutorials/pt/vtex-admin-start-here1.md
index d5ff64594..0b765bce8 100644
--- a/docs/tutorials/pt/vtex-admin-start-here1.md
+++ b/docs/tutorials/pt/vtex-admin-start-here1.md
@@ -19,7 +19,7 @@ O Admin permite que os comerciantes gerenciem toda sua experiência de comércio
 
 ## Página inicial
 
-![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 A página inicial do nosso Admin foi redesenhada para oferecer uma visão geral de alto nível da sua loja, como uma cabine de comando para as suas operações de comércio digital. Por isso, ela se chama [Visão Geral](https://help.vtex.com/pt/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -29,23 +29,23 @@ Assim que você fizer login no Admin, verá métricas e gráficos úteis para mo
 
 Tudo que você precisa para administrar sua loja VTEX continua disponível no Admin, mas agora com uma organização mais simples. Nossos menus de navegação lateral e barra superior foram reformulados do zero, agrupando categorias similares de forma mais clara para reduzir as distrações e ajudar a sua equipe a encontrar o que precisa mais rapidamente. Também é possível utilizar a barra de busca para encontrar seções específicas no menu lateral.
 
-![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Central de Informações
 
 É aqui que reunimos todos os links úteis do nosso ecossistema VTEX, para ajudá-lo(a) a aproveitar a nossa plataforma ao máximo. Clicando no botão `?` na barra superior, você pode acessar nosso Help Center, Developer Portal, Status da Plataforma, blog e páginas de suporte.
 
-![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Configurações da Loja
 
 Para esta experiência, reunimos todas as configurações de todas as seções do seu Admin em uma guia específica: [Configurações da Loja](https://help.vtex.com/pt/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Através dessa melhoria, você pode acessar facilmente todas as configurações que afetam cada serviço da sua conta.
 
-![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Configurações da conta e do usuário
 
-![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 Seu avatar de perfil, no canto superior direito, agora reúne todas as configurações relacionadas ao seu usuário e à sua conta. Através do avatar, você pode acessar as [Configurações do usuário](https://help.vtex.com/pt/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Configurações da conta](https://help.vtex.com/pt/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), e [Faturas](https://help.vtex.com/pt/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC), alterar o idioma do seu Admin e encerrar a sessão. 
 
diff --git a/docs/tutorials/pt/vtex-agreement.md b/docs/tutorials/pt/vtex-agreement.md
new file mode 100644
index 000000000..a3511dc13
--- /dev/null
+++ b/docs/tutorials/pt/vtex-agreement.md
@@ -0,0 +1,35 @@
+---
+title: 'Contrato VTEX'
+id: gjJL5j4zZuiC2qAuSuoG4
+status: PUBLISHED
+createdAt: 2019-01-24T20:45:47.050Z
+updatedAt: 2024-02-20T18:14:26.057Z
+publishedAt: 2024-02-20T18:14:26.057Z
+firstPublishedAt: 2019-01-24T22:07:46.230Z
+contentType: tutorial
+productTeam: Billing
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: contrato-vtex
+locale: pt
+legacySlug: por-que-nao-recebi-o-contrato-assinado-da-vtex
+subcategory: 22TaEgFhwE6a6CG2KASYkC
+---
+
+O contrato VTEX, ou acordo comercial, é composto por duas partes: o [MSA (Master Service Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/) e o **Anexo 1 Order Form** para prestação de serviços às empresas ou o [MPA (Master Partner Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) e os **Termos e condições específicos da parceria.**
+
+![Contrato VTEX](//images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/cb616e04ff8e452d9f286210d9ad4c57/PT.png)
+
+O [Master Service Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/) e o [Master Partner Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) são os acordos mestre de serviço e parceria, respectivamente, que regulam o relacionamento entre VTEX e cliente ou VTEX e parceiro. Ambos variam de acordo com a região em que a empresa ou o parceiro estão localizados. 
+
+O **Anexo 1 Order Form** e os **Termos e condições específicos de parcerias** são documentos que preveem todas as condições comerciais negociadas para cada empresa ou parceiro e possuem as condições jurídicas da contratação.
+
+## Onde posso encontrar o meu contrato com a VTEX?
+
+O Master Agreement aplicável a você está disponível na seção **Política de privacidade > Arquivo de contratos > [Master Agreements](https://vtex.com/us-en/privacy-and-agreements/agreements-archive/#:~:text=Master%20Agreements,September%2006%2C%202020%5D)** para clientes e **Política de privacidade > Arquivo de contratos > [Partner Agreement](https://vtex.com/br-pt/privacy-and-agreements/agreements-archive/#:~:text=Contratos%20Anteriores,Partner%20Agreement)** para parceiros, a depender da região e da data em que o **Anexo 1** ou **Termos e condições específicos de parcerias** foi assinado. O **Anexo 1** e os **Termos e condições** assinados com a VTEX podem ser solicitados diretamente para o CS da sua conta por meio do [Suporte VTEX](https://help.vtex.com/support?/cultureInfo=pt-br).
+
+Também é possível encontrar os Master Agreements mais atualizados, ou seja, aplicáveis aos novos clientes e parceiros, na página [Contrato da VTEX](https://vtex.com/br-pt/privacy-and-agreements/agreements/).
+
+<div class="alert alert-info">
+Caso os <b>MSA, MPA, Anexo 1</b> ou <b>Termos e condições específicos de parceria</b> firmados com a VTEX tragam alguma informação diferente daquela descrita nesta documentação, priorize o seu documento assinado com a VTEX.
+</div>
+
diff --git a/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
new file mode 100644
index 000000000..4cd5d780c
--- /dev/null
+++ b/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
@@ -0,0 +1,199 @@
+---
+title: 'Guia dos dashboards VTEX para a Black Week: FAQ'
+id: 6O3CiGiZctVIgIrpIcko9h
+status: PUBLISHED
+createdAt: 2023-11-17T17:09:40.720Z
+updatedAt: 2023-11-21T16:06:22.017Z
+publishedAt: 2023-11-21T16:06:22.017Z
+firstPublishedAt: 2023-11-20T18:30:27.790Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: guia-dos-dashboards-vtex-para-a-black-week-faq
+locale: pt
+legacySlug: guia-dos-dashboards-vtex-para-a-black-week-faq
+subcategory: 1TIJqw8kV2Yok4iQe4SAkq
+---
+
+Este guia tem como objetivo responder as perguntas mais frequentes sobre como utilizar os [dashboards do Admin VTEX](https://help.vtex.com/pt/subcategory/visao-geral-do-insights--1TIJqw8kV2Yok4iQe4SAkq) durante a Black Week.
+
+- [Qual a melhor forma de acompanhar meu ecommerce durante a Black Week no Admin VTEX?](#qual-a-melhor-forma-de-acompanhar-meu-ecommerce-durante-a-black-week-no-admin-vtex)
+- [Como acompanhar meus dados de ecommerce além do dia de hoje?](#como-acompanhar-meus-dados-de-ecommerce-alem-do-dia-de-hoje)
+- [Por que minhas métricas estão diferentes da tela de Pedidos do Admin?](#por-que-minhas-metricas-estao-diferentes-da-tela-de-pedidos-do-admin)
+- [Por que não tenho dados de sessões ou taxa de conversão?](#por-que-nao-tenho-dados-de-sessoes-ou-taxa-de-conversao)
+- [Por que as minhas métricas de taxa de conversão, novas sessões ou funil de vendas não batem com os números das minhas ferramentas internas?](#por-que-as-minhas-metricas-de-taxa-de-conversao-novas-sessoes-ou-funil-de-vendas-nao-batem-com-os-numeros-das-minhas-ferramentas-internas)
+- [Por que minha métrica de receita está em somente uma moeda, sendo que opero com mais de uma?](#por-que-minha-metrica-de-receita-esta-em-somente-uma-moeda-sendo-que-opero-com-mais-de-uma)
+- [Por que o número de pedidos da análise de funil de vendas não bate com a da parte de Monitoramento?](#por-que-o-numero-de-pedidos-da-analise-de-funil-de-vendas-nao-bate-com-a-da-parte-de-monitoramento)
+- [Por que a nova Visão geral está em uma URL separada?](#por-que-a-nova-visao-geral-esta-em-uma-url-separada)
+
+## Qual a melhor forma de acompanhar meu ecommerce durante a Black Week no Admin VTEX?  
+
+Durante um período de intensa atividade e volatilidade nas vendas, a ferramenta ideal para monitoramento é a nova página **Visão geral em tempo real** da VTEX. Para acessar essa página, clique em **Dashboards > Visão geral em tempo real** no menu de navegação ou digite **Visão geral** na barra de busca no topo da página.
+
+Veja abaixo algumas dicas para aproveitar ao máximo essa funcionalidade:
+
+Inicie ajustando o fuso horário e selecionando a loja que deseja monitorar na Visão geral em tempo real.
+
+![fuso-pt](//images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/27380d6a540c52fb03aaf6a19ccdafb4/fuso-pt.png)
+
+### Filtro de referência
+
+O filtro de referência ou Comparar hoje com traz uma avaliação do seu desempenho atual em relação a um período específico. 
+
+Para configurar a referência, siga os passos a seguir:
+
+1. Clique em `Comparar hoje com`.  
+3. Selecione `Personalizado`.  
+4. Defina uma data.  
+5. Clique em **`Aplicar`**.  
+
+<div class="alert alert-warning">
+Uma comparação útil durante a Black Week é com a mesma data do ano anterior. No ajuste de referência, defina preferencialmente uma data entre 21/11/2022 e 27/11/2022, idealmente, os mesmos dias da semana. <br>Esta opção está disponível para clientes que utilizavam a plataforma VTEX nesse período no ano passado.</br>
+</div>
+
+![referencia-pt](//images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/c92d901550424a6ce3e095a28fd1f8db/referencia-pt.png)
+
+### Filtro de visualização
+
+- **Acompanhe a performance do dia com a visão acumulada:** a **visão acumulada** mostra o monitoramento da performance de vendas do seu ecommerce minuto a minuto, trazendo insights para ajustes rápidos na operação.  
+Para selecionar o modo **visão acumulada** no dashboard, clique em **Visualização<i class="fas fa-angle-down"></i> > Acumulado.**   
+
+![acumulada-pt](//images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/90c6937f448f6b02da0721181b8ae552/acumulada-pt.png)
+
+- **Acompanhe a performance das últimas horas:** a **visão das últimas 2 horas** apresenta as métricas isoladas minuto a minuto, o que é importante para assegurar a estabilidade operacional da sua loja durante o evento.  
+Para selecionar o modo **Últimas 2 horas** no dashboard, clique em **Visualização <i class="fas fa-angle-down"></i> > Últimas 2 horas.**
+
+![horas-pt](//images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/76b3ea0dbacfa045ebd05cd6ae939796/horas-pt.png)
+
+### Métricas  
+
+Com a **Visão geral em tempo real,** obtenha insights importantes sobre sua estratégia de vendas. Por exemplo, use os "produtos mais vendidos" como referência para impulsionar campanhas e alavancar ainda mais seus resultados.  
+Para visualizar os produtos mais vendidos, no quadro de **Métricas,** clique no botão <i class="fas fa-ellipsis-v"></i> e selecione **Produtos mais vendidos.**
+
+![mais-vendidos-pt](//images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/9c99acbbf617a57ef431bfec05873aa9/mais-vendidos-pt.png)
+
+<div class="alert alert-info">
+Para análises ou acompanhamentos de períodos maiores, recomendamos o uso do nosso dashboard de performance de vendas, que será detalhado na próxima pergunta.
+  </div>
+
+## Como acompanhar meus dados de ecommerce além do dia de hoje?
+
+Para um acompanhamento diário da operação do seu ecommerce, o [dashboard de Performance de vendas da VTEX](https://help.vtex.com/pt/tutorial/performance-de-vendas--3DMube0sEsK9vPcRYGas72) é a ferramenta indicada. Sua taxa de atualização é de cerca de 90 minutos e ele fornece um histórico de dados mais extenso. Veja nos pontos abaixo como maximizar seu uso.  
+
+### Filtros
+- **Data**  
+Ao acessar o dashboard, o primeiro passo é definir o **Período principal** e **Comparar com**. Se estiver analisando após a Black Week, selecione `Última semana` para comparar com a Black Week do ano passado (opção disponível se você já era cliente VTEX). Durante a Black Week, prefira `Personalizar` e escolha os dias específicos para análise.
+
+![vendas-data-pt](//images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/e55170c03fa62f9df615a8be66d0dcd6/vendas-data-pt.png)
+
+- **Filtros combinados**  
+Os dados apresentados no dashboard de vendas podem ser segmentados através dos filtros combinados, um exemplo é o filtro de categoria. Para adicionar um novo filtro, siga os seguintes passos:  
+1. No dashboard de vendas, clique em Filtros.  
+2. Clique em  <i class="fas fa-plus"></i> Adicionar filtro.  
+3. Selecione as categorias desejadas.  
+4. Clique em  `Aplicar`.  
+
+É possível explorar outros filtros conforme a necessidade e os aspectos do seu ecommerce.  
+
+![adicionar-filtro-pt](//images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/f6e9ab2ea49d191a99cabda460179bc7/adicionar-filtro-pt.png)
+
+### Métricas  
+
+As métricas exibidas podem ser personalizadas para visualização de acordo com a necessidade da análise. Cada métrica pode ser alterada clicando no botão <i class="fas fa-ellipsis-v"></i> que aparece ao lado do nome de cada uma.  
+
+Durante a Black Week, esse dashboard pode ser utilizado para analisar as seguintes métricas de desempenho da sua operação:  
+
+- Receita (aprovada)
+- Pedidos (aprovados) 
+- Pedidos (captados) 
+- Ticket médio (aprovado)
+- Pedidos (cancelados)
+
+![mudar-metrica-pt](//images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/0c821bba0f892f370cb964c3066ca260/mudar-metrica-pt.png)
+
+- **Performance da semana**  
+Após os ajustes, compare o desempenho da semana atual com a Black Week do ano passado para identificar tendências e oportunidades.  
+
+![performance-semana-pt](//images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/b6f43694faee09f289227978a311a797/performance-semana-pt.png)
+
+- **Análise da tabela**   
+Analise a tabela detalhada para obter insights mais profundos. Por exemplo, a análise por SKU pode revelar quais produtos devem ser destacados em futuras campanhas.
+
+![analise-tabela-pt](//images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/05e608c70c457650ee826c85cb7a18b5/analise-tabela-pt.png)
+
+- **Salve sua visualização**   
+Para consultas futuras, salve a configuração do seu dashboard. Clique em **Gestão de vendas > <i class="fas fa-plus"></i>  > Adicione um nome > `Criar`** para guardar sua visualização personalizada.  
+
+![criar-exibição-pt](//images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/f3f76fdffa9837442e414b42aae75ac3/criar-exibi__o-pt.png)
+
+## Por que minhas métricas estão diferentes da tela de Pedidos do Admin?  
+
+Há alguns motivos que podem levar a diferenças entre as métricas da Visão geral em tempo real e da tela de Pedidos do Admin:  
+
+- **Visão geral:** as métricas apresentadas nos dashboards do Admin VTEX considera apenas as vendas de uma loja por vez, então, todas as métricas apresentadas serão referentes à loja selecionada no filtro do dashboard.  
+- **Pedidos:** as métricas de pedidos considera todas as vendas realizadas no período em questão.  
+- **Tempo de atualização diferente:** a tela Visão geral em tempo real tem um tempo de atualização de cerca de 1 a 3 minutos. Portanto, é comum haver uma pequena discrepância (de 1 a 3% do total) entre as duas telas.  
+- **Fórmula de cálculo de receita:** as métricas na Visão geral em tempo real não consideram descontos, frete, taxas e promoções no cálculo da receita, enquanto a tela de Pedidos considera esses fatores.  
+
+![selecao-loja-pt](//images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/89439bd5b253d4c38eacbdb441df0d5a/selecao-loja-pt.png)
+
+Para ver as métricas combinadas de todas as lojas,acesse o dashboard **Performance de vendas,** que apresenta dados agregados com uma taxa de atualização de aproximadamente 90 minutos. 
+
+<div class="alert alert-danger">
+  No <b>dashboard Visão geral em tempo real,</b> ecommercess que operam com mais de uma moeda têm seus pedidos somados somente na moeda mais utilizada em suas vendas.<br>Para comparar com a tela de <b>Pedidos,</b> você deve somar o total de pedidos de todas as suas moedas.</br>
+</div>  
+
+![todos-os-pedidos-pt](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)
+
+- **Fuso horário:** este filtro está disponível na **Visão geral.** Se usar um fuso horário diferente do padrão da tela de Pedidos (que é seu fuso horário atual), as métricas não serão iguais. Ajuste o fuso horário conforme necessário.  
+
+![vendas-fuso-pt](//images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/cb0e95d1cb6606230099bc85855254c6/vendas-fuso-pt.png)
+
+## Por que não tenho dados de sessões ou taxa de conversão?  
+
+As análises de taxa de conversão, sessões e funil de vendas na VTEX são baseadas em dados captados pela nossa base de navegação, que depende de um script próprio executado dentro da loja online do cliente. Este script é essencial para registrar as informações necessárias para essas análises.  
+
+No entanto, é importante saber que nosso script não captura dados de sessões originadas em marketplaces, aplicativos ou em implementações headless, em que não gerenciamos o frontend. Além disso, alterações personalizadas feitas no frontend da loja podem interferir ou mesmo inativar nosso script. Isso significa que, em alguns casos, essas sessões e atividades não são registradas, resultando na falta de dados de sessões ou taxa de conversão no seu dashboard.  
+
+Se você notar a ausência desses dados, é possível que isso se deva a uma dessas limitações. Recomendamos verificar as configurações do script e possíveis personalizações no frontend que possam estar afetando a captura de dados.
+
+![vendas-visao-geral-pt](//images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/c20776ac629c196881678e0a720f5e86/vendas-visao-geral-pt.png)  
+
+## Por que as minhas métricas de taxa de conversão, novas sessões ou funil de vendas não batem com os números das minhas ferramentas internas?  
+
+Outras ferramentas de análise, como o Google Analytics, geralmente são instaladas de forma personalizada e com prioridade elevada, podendo capturar um espectro mais amplo de dados. Isso frequentemente resulta em discrepâncias nos números comparados aos nossos.  
+
+A captura de dados de navegação na VTEX, por outro lado, é realizada por um script próprio, executado dentro da loja online do cliente. Como o script é carregado por último na página para minimizar impactos no desempenho, sessões muito breves podem não ser registradas.  
+
+Vale destacar que nosso script não capta dados de sessões originadas de marketplaces, apps ou de implementações headless. Além disso, customizações no frontend feitas pelo cliente podem interferir ou mesmo inativar nosso script, impactando a coleta de dados.  
+
+## Por que minha métrica de receita está em somente uma moeda, sendo que opero com mais de uma?  
+
+Na VTEX, para simplificar a visualização do gráfico de receita na parte de monitoramento da Visão geral em tempo real, optamos por apresentar o valor em apenas uma moeda. Essa escolha se deve à necessidade de oferecer uma visão clara e direta das receitas, sem a complexidade adicional de múltiplas moedas.  
+
+Para definir qual moeda será exibida, avaliamos qual é a moeda mais utilizada nas vendas do seu ecommerce e convertemos todos os outros valores para essa moeda. Isso é feito para proporcionar uma compreensão mais simples e direta do desempenho de vendas.  
+
+Como resultado, se você opera com mais de uma moeda, é importante somar o total de pedidos da tela de Pedidos do Admin de todas as suas moedas para corresponder ao dado de pedidos apresentado na Visão geral em tempo real.  
+
+![todos-os-pedidos-pt](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)  
+![monitoramento-pt](//images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/cd0ac69320e37428e59c1a7770895632/monitoramento-pt.png)  
+
+## Por que o número de pedidos da análise de funil de vendas não bate com o da parte de Monitoramento?
+
+Para entender essa diferença, é essencial saber que as métricas de monitoramento na Visão geral em tempo real são geradas a partir de dados do nosso [Sistema de Gerenciamento de Pedidos (OMS)](https://help.vtex.com/pt/subcategory/visao-geral-de-pedidos--3VNOhxDrvYxJThhuJClrYZ). O OMS contém informações sobre todos os diferentes tipos de pedidos da loja, incluindo vendas de marketplaces, vendas diretas, aplicativos, entre outros.  
+
+Por outro lado, os dados do funil de vendas são coletados da base de navegação do site, que captura exclusivamente os dados de vendas realizadas dentro da loja online do cliente. Isso significa que vendas realizadas em marketplaces ou em outras lojas que não utilizam o storefront da VTEX não são contabilizadas neste funil.  
+
+Como resultado, é comum que o número de pedidos no funil de vendas seja menor do que na parte de monitoramento, que apresenta uma visão mais ampla das vendas da loja, incluindo canais externos à plataforma VTEX.  
+
+![taxa-conversão-pt](//images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/837f35d360d6b1c7fad1089e39fb4119/taxa-convers_o-pt.png)  
+![novas-sessoes-pt](//images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/7f9a00ffd9e4bf2cf5c6718403e0c0ab/novas-sessoes-pt.png)  
+
+## Por que a nova Visão geral está em uma URL separada?
+
+Na VTEX, decidimos manter temporariamente a tela antiga de Visão geral enquanto introduzíamos a nova Visão geral em tempo real. Para garantir uma transição suave e não interromper o acesso à versão anterior, a nova Visão geral foi hospedada em um ambiente separado. Isso significa que, ao acessar a nova Visão geral, você pode ser solicitado a fazer login novamente no Admin VTEX.  
+
+É importante notar que, ocasionalmente, você pode encontrar erros ao tentar carregar a página da nova Visão geral. Esses erros geralmente são relacionados à necessidade de reautenticação no sistema, devido ao ambiente separado em que a nova Visão geral está hospedada.  
+
+Estamos trabalhando para integrar a nova Visão geral de volta ao ambiente original do Admin VTEX. Assim que essa integração for concluída, planejamos descontinuar a tela antiga, simplificando o processo e melhorando a experiência do usuário. Até lá, agradecemos sua paciência e compreensão.  
+
diff --git a/docs/tutorials/pt/vtex-do-interface.md b/docs/tutorials/pt/vtex-do-interface.md
index b40a7b8b5..3951bf161 100644
--- a/docs/tutorials/pt/vtex-do-interface.md
+++ b/docs/tutorials/pt/vtex-do-interface.md
@@ -3,8 +3,8 @@ title: 'VTEX DO'
 id: 7KMbRL4OslN8DTX9oiuCiu
 status: PUBLISHED
 createdAt: 2022-04-04T21:12:30.592Z
-updatedAt: 2023-03-29T14:50:36.206Z
-publishedAt: 2023-03-29T14:50:36.206Z
+updatedAt: 2023-11-06T14:21:27.706Z
+publishedAt: 2023-11-06T14:21:27.706Z
 firstPublishedAt: 2022-04-04T21:58:08.236Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -17,10 +17,10 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 O VTEX DO é um gerenciador de tarefas criadas automaticamente pelo Admin VTEX, para que a equipe de ecommerce da sua loja as realize manualmente. Para acessá-lo, em seu Admin VTEX, vá em **Pedidos > [Todos os pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos--2QTduKHAJMFIZ3BAsi6Pi)** e clique no ícone de caixa de entrada, localizado no canto inferior direito da página. Ao clicar no ícone, um modal se abrirá com a lista de tarefas relacionadas aos pedidos da loja. 
 
-![VTEX Do overview PT](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
+![VTEX Do overview PT](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
 
 <div class = "alert alert-info">
-Somente usuários com o recurso <a href = "https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> cadastrado em seu <a href = "https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> podem realizar tarefas pelo VTEX DO. 
+Somente usuários com o perfil de acesso <a href = "https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> podem realizar tarefas pelo VTEX DO. 
 </div>
 
 As tarefas estão listadas em duas abas:
@@ -116,7 +116,7 @@ As tarefas gerenciadas por meio do VTEX DO podem incluir mensagens de todos os s
 
 ## Detalhes da tarefa
 
-![VTEX Do details PT](https://images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/08c283d0b9bcebf7da71bd78c0d7eeec/VTEX_Do_details_PT.jpg)
+![VTEX Do details PT](//images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/08c283d0b9bcebf7da71bd78c0d7eeec/VTEX_Do_details_PT.jpg)
 
 Ao clicar no nome de uma tarefa da lista, você é redirecionado para o modal de detalhes da tarefa, que apresenta mais informações sobre a tarefa e ações para resolvê-la. São apresentados os seguintes campos:
 
diff --git a/docs/tutorials/pt/vtex-insurance.md b/docs/tutorials/pt/vtex-insurance.md
index c66f5a64d..5014990b6 100644
--- a/docs/tutorials/pt/vtex-insurance.md
+++ b/docs/tutorials/pt/vtex-insurance.md
@@ -1,10 +1,10 @@
 ---
 title: 'VTEX Insurance'
 id: 2aF3SDIj5t2qGe3bWKCjLD
-status: PUBLISHED
+status: DRAFT
 createdAt: 2023-05-23T20:15:25.639Z
-updatedAt: 2023-05-26T18:43:28.958Z
-publishedAt: 2023-05-26T18:43:28.958Z
+updatedAt: 2024-01-11T20:01:57.317Z
+publishedAt: 
 firstPublishedAt: 2023-05-26T17:46:59.436Z
 contentType: tutorial
 productTeam: B2B
@@ -55,7 +55,7 @@ Após a instalação do VTEX Insurance, é necessário realizar a preparação d
 5. Após a criação do campo **Garantia do Fabricante**, defina o período desejado de garantia. No campo **Valor Padrão**, é recomendado o valor 12, representando um período de 12 meses.
 6. [Crie uma categoria](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1?&utm_source=autocomplete) específica para o produto de seguro.
 7. [Crie o produto](https://help.vtex.com/pt/tutorial/produtos-e-skus-beta--2ig7TmROlirWirZjFWZ3By?&utm_source=autocomplete#criar-produto) de seguro.
-8. [Crie SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) de seguro. É recomendada a criação de mais de três SKUs para cada seguro.![Insurance - SKUs](https://images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/763ed10aa72e1f453bca4e858b4347e1/image1.png)
+8. [Crie SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) de seguro. É recomendada a criação de mais de três SKUs para cada seguro.![Insurance - SKUs](//images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/763ed10aa72e1f453bca4e858b4347e1/image1.png)
 9. [Vincule os SKUs criados](https://help.vtex.com/pt/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX?&utm_source=autocomplete) com o seller da Assurant.
 10.  [Vincule o seguro com o produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106#preencher-especificacoes-de-produto) desejado.
 
@@ -69,37 +69,38 @@ Após a preparação do catálogo, sua loja já tem o vínculo do seguro com os
 Siga os passos abaixo para configurar seu app VTEX Insurance.
 
 ### Company Information
-![Insurance Configuration](https://images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/343aefaafe713ae74ab488f87caf4b55/image5.png)
-
+1. ![Insurance Configuration](//images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/343aefaafe713ae74ab488f87caf4b55/image5.png)
 1. Preencha a seção com as seguintes informações:
-**Email**: email da loja.
-**Name**: nome da loja.
-**Phone**: telefone da loja.
-**Mark-Up Value**: margem de lucro a ser obtida. Deve ser preenchida com valor 0 (zero). 
-**Street Name**: rua da loja ou do seu escritório.
-**City**: cidade da loja ou do seu escritório.
-**State**: Estado da loja ou do seu escritório.
-**Postal Code**: CEP da sua loja ou do seu escritório.
-**Country**: país de sua loja ou do seu escritório.
+
+- **Email**: email da loja.
+- **Name**: nome da loja.
+- **Phone**: telefone da loja.
+- **Mark-Up Value**: margem de lucro a ser obtida. Deve ser preenchida com valor 0 (zero). 
+- **Street Name**: rua da loja ou do seu escritório.
+- **City**: cidade da loja ou do seu escritório.
+- **State**: Estado da loja ou do seu escritório.
+- **Postal Code**: CEP da sua loja ou do seu escritório.
+- **Country**: país de sua loja ou do seu escritório.
+
 2. Clique em `Submit`.
 
 ### Items bound to insurance items
-![Items Bound to Source Items](https://images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/e55e7f2af44167b5885af398cfda7637/image6.png)
+![Items Bound to Source Items](//images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/e55e7f2af44167b5885af398cfda7637/image6.png)
 
 1. Selecione os códigos que representam os tipos de seguro desejados para a coleção criada. 
-2. Vincule os SKUs criados com os planos de seguro: você deverá incluir o plano de seguro seguido pelo SKU ID. 
+2. Vincule os SKUs criados com os planos de seguro: você deverá incluir o plano de seguro seguido pelo SKU ID.
 _Exemplo_: Ao vincular o Tipo de Seguro **Garantia Estendida** (Código **EW**) com o SKU criado para esse mesmo tipo de seguro (ID **357**), o vínculo será representado da seguinte maneira: **EW|357** (sem espaçamento).
-Se desejar vincular mais de um plano de seguro, como o de **Roubo e Furto Qualificado** (Código **TH**) com o SKU criado (ID **358**), vínculo **TH|358**, O campo deverá ser preenchido da seguinte maneira: **EW|357, TH|358**
+Se desejar vincular mais de um plano de seguro, como o de **Roubo e Furto Qualificado** (Código **TH**) com o SKU criado (ID **358**), vínculo **TH|358**, O campo deverá ser preenchido da seguinte maneira: **EW|357, TH|358**.
 3. Clique em `Submit`.      
 
 ### Warranty field name
-![Warranty Field Name](https://images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/441c24ddc67aa0182fbaad41b6ca4f86/image2.png)
+![Warranty Field Name](//images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/441c24ddc67aa0182fbaad41b6ca4f86/image2.png)
 
 1. Especifique o campo de garantia do fabricante, indicando o nome da garantia utilizada no catálogo.
 2. Clique em `Submit`.
 
 ### Insurance attachment setup
-![Attachement Setup](https://images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/976dc38542cfe701e45e8ce0eec936b1/image7.png)
+![Attachement Setup](//images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/976dc38542cfe701e45e8ce0eec936b1/image7.png)
 
 1. [Crie um anexo](https://help.vtex.com/pt/tutorial/cadastrar-um-anexo) para a Assurant com as informações recebidas pelo suporte na contratação do serviço.
 2. Em **Seguro > Configuração**, clique em `Add attachment` na seção **Insurance** **attachment setup**.
@@ -108,7 +109,7 @@ Se desejar vincular mais de um plano de seguro, como o de **Roubo e Furto Qualif
 5. Clique em `Salvar`.
 
 ### Manual pricing setup
-![Manual Pricing](https://images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/59f5683a077151a789969ff64b7b5aac/image4.png)
+![Manual Pricing](//images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/59f5683a077151a789969ff64b7b5aac/image4.png)
 
 1. Ative o manual pricing na sua loja.
 2. Clique em `Done, next`.
diff --git a/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
index 01334aa95..97c5878e1 100644
--- a/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -3,8 +3,8 @@ title: 'VTEX Intelligent Search: configurações Multi-idioma (Beta)'
 id: 2WahlTESLXIJ9XBdQMdTYO
 status: PUBLISHED
 createdAt: 2021-03-09T22:44:16.513Z
-updatedAt: 2023-03-30T17:45:54.079Z
-publishedAt: 2023-03-30T17:45:54.079Z
+updatedAt: 2023-07-26T19:15:24.855Z
+publishedAt: 2023-07-26T19:15:24.855Z
 firstPublishedAt: 2021-03-10T21:13:35.816Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,11 +27,7 @@ O VTEX Intelligent Search Multi-idioma expande as funcionalidades do [Intelligen
 <p> Caso você deseje expandir o seu ecommerce para outro idioma, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a> para que o time da VTEX realize as configurações necessárias.</p>
 </div>
 
-Com o VTEX Intelligent Search Multi-idioma instalado, as informações do Catálogo da loja são traduzidas pelo aplicativo [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization). Para isso, você deve cadastrar previamente como traduzíveis os termos dos seguintes campos: __Nome__, __Marca__, __Descrição__, __Categorias__, __CategoryTrees__, __metadata__, __metadataKeyword__, __Especificações__, __SKU {name}__.
-
-<div class="alert alert-warning">
-  <p> Se um termo não possui tradução cadastrada no <strong>Messages</strong>, sua tradução é realizada por um serviço automático, exceto no caso do campo <strong>Marca</strong>. Por isso, é importante <a href="https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization">cadastrar a tradução de todos os campos</a> para evitar efeitos indesejados, como traduções literais que não refletem a língua utilizada em determinada região. Sem o cadastro do termo correto, o nome de um produto como “whole milk", por exemplo, corre o risco de ser traduzido automaticamente para "leite inteiro" em vez de "leite integral".</p>
-</div>
+Com o VTEX Intelligent Search Multi-idioma instalado, as informações do Catálogo da loja são traduzidas pelo aplicativo [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization). Para isso, é importante cadastrar a tradução dos seguintes campos: __Nome__, __Marca__, __Descrição__, __Categorias__, __CategoryTrees__, __metadata__, __metadataKeyword__, __Especificações__, __SKU {name}__. Leia o guia para desenvolvedores [Tradução do conteúdo do catálogo](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) para mais informações.
 
 A partir da [Multi-Tenant API](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-multi-language-stores), o VTEX Intelligent Search Multi-idioma obtém todos os locais e respectivos idiomas (exemplos: `pt-br`, `en-uk`) registrados na loja. Cada local possui uma URL própria.
 
@@ -47,7 +43,7 @@ O VTEX Intelligent Search Multi-idioma permite que você personalize a experiên
 ### Regras de merchandising
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Regras de merchandising — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Regras de merchandising__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas a Regra de Merchandising será aplicada através da seleção dos idiomas desejados, conforme mostrado na figura abaixo.
 
-![img regrasmerch intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/000fe10fd8752c5996afdea9a4bc8e9a/01-merchrules-pt.png)
+![img regrasmerch intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/000fe10fd8752c5996afdea9a4bc8e9a/01-merchrules-pt.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Regras de merchandising no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8).
 
@@ -61,7 +57,7 @@ Existem duas formas de configurar Sinônimos em uma loja multi-idioma no Admin:
 #### Criar Sinônimos via formulário
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Sinônimos — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Sinônimos__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Sinônimos cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
 
-![img sinonimos intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/d513d8a4b124aa077b447ce9a1d4adb8/02-sinonimos-pt.png)
+![img sinonimos intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/d513d8a4b124aa077b447ce9a1d4adb8/02-sinonimos-pt.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Sinônimos no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
@@ -85,7 +81,7 @@ Para saber mais sobre a importação de planilha de Sinônimos, leia nosso artig
 
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Redirecionamentos — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Redirecionamentos__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Redirecionamentos cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
 
-![img redirecionamentos intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/38bda1599742284c81ed067b2330514d/03-redirecionamentos-pt.png)
+![img redirecionamentos intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/38bda1599742284c81ed067b2330514d/03-redirecionamentos-pt.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Redirecionamentos no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4Gd2wLQFbCwTsh8RUDwSoL).
 
@@ -93,6 +89,6 @@ Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Redire
 
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Banners — encontrada no Admin VTEX em __Storefront__ > __Banners__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Banners cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
 
-![img banner intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/9c5e675df49840e3fa4db7437f866524/image_8.png)
+![img banner intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/9c5e675df49840e3fa4db7437f866524/image_8.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Banners no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
diff --git a/docs/tutorials/pt/vtex-invoice-notifier.md b/docs/tutorials/pt/vtex-invoice-notifier.md
index 06ebe2573..c7dc446a7 100644
--- a/docs/tutorials/pt/vtex-invoice-notifier.md
+++ b/docs/tutorials/pt/vtex-invoice-notifier.md
@@ -15,7 +15,7 @@ legacySlug: vtex-invoice-notifier
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-![invoice-flow](https://images.ctfassets.net/alneenqid6w5/1J8NLy4mw7miEPixtV20G8/80c960a20017f2058209c58681fae862/invoice-flow.svg)
+![invoice-flow](//images.ctfassets.net/alneenqid6w5/1J8NLy4mw7miEPixtV20G8/80c960a20017f2058209c58681fae862/invoice-flow.svg)
 
 ## Instalação da app - VTEX Invoice Notifier
 
@@ -25,7 +25,7 @@ Usuário deve fazer instalação da APP através da VTEX App Store - apps.vtex.c
 
 Ao realizar a instalação, uma página de configuração será exibida, nela o usuário insere o endpoint de comunicação com o sistema responsável pela emissão das notas.
 
-![install-app](https://images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
+![install-app](//images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
 
 ## OMS notificar faturador
 
@@ -33,9 +33,9 @@ Com o endpoint cadastrado na APP o OMS passa a reconhecer que está habilitado p
 
 O operador deve, no pedido, selecionar o pacote ou os itens que deseja faturar e gerar uma nova notificação:
 
-![notify-invoicer1](https://images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
+![notify-invoicer1](//images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
 
-![notify-invoicer2](https://images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
+![notify-invoicer2](//images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
 
 quando o usuário do OMS apertar o botão __Request Invoice__, a app irá realizar um request POST no endpoint cadastrado na APP com o seguinte BODY exemplo:
 
@@ -59,7 +59,7 @@ Essa propriedade deve ser utilizada para saber qual endereço enviar o Invoice.
 
 Uma vez notificado com sucesso, a APP grava no Banco de Dados (VBASE) essa notificação.
 
-![callBackProperty](https://images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
+![callBackProperty](//images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
 
 ## Faturador pegar detalhes da nota
 
@@ -170,7 +170,7 @@ Pedidos de Pickup podem conter a identificação do cliente ou não. Um pedido f
 
 A forma base de identificar se um pedido é Delivery ou Pickup é através do objeto __shippingData.logisticsInfo[0].deliveryChannel__
 
-![shipping-type](https://images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
+![shipping-type](//images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
 
 ## Inserir nota fiscal no pedido
 
diff --git a/docs/tutorials/pt/vtex-operation-service-level-agreement-sla.md b/docs/tutorials/pt/vtex-operation-service-level-agreement-sla.md
new file mode 100644
index 000000000..39cfa3170
--- /dev/null
+++ b/docs/tutorials/pt/vtex-operation-service-level-agreement-sla.md
@@ -0,0 +1,27 @@
+---
+title: 'Acordo de nível de serviço (SLA) de operação da VTEX'
+id: 2cIFrsY5S8usk84OU4QOKm
+status: PUBLISHED
+createdAt: 2019-01-24T20:45:48.688Z
+updatedAt: 2024-03-11T22:27:09.058Z
+publishedAt: 2024-03-11T22:27:09.058Z
+firstPublishedAt: 2019-01-24T22:13:57.539Z
+contentType: tutorial
+productTeam: Reliability
+author: 7FpKZ0rc6k4WqeymES80cw
+slug: acordo-de-nivel-de-servico-sla-de-operacao-da-vtex
+locale: pt
+legacySlug: o-que-e-o-sla-de-operacao-da-plataforma
+subcategory: 5PYkoNDZyo2G80yiiqG2YW
+---
+
+O [Service Level Agreement (SLA)](https://vtex.com/br-pt/privacy-and-agreements/agreements/) é um acordo de nível de serviço, ou seja, uma política que rege o uso da plataforma VTEX sob os termos do contrato celebrado entre a VTEX e o cliente, que é o contratante. Este documento especifica todos os serviços que um contratante pode esperar da VTEX.
+
+O SLA expressa o nível de serviço da infraestrutura da plataforma e esclarece tecnicamente seu tempo de atividade e inatividade operacional, assim como todos os eventos que são contabilizados ou não como incidentes.
+
+Confira o nosso SLA em [VTEX Commerce - SLA Agreement](https://vtex.com/br-pt/privacy-and-agreements/agreements/).
+
+## Saiba mais
+
+- [Como é apurado o SLA de operação da plataforma?](https://help.vtex.com/pt/tutorial/como-e-apurado-o-sla-de-operacao-da-plataforma--frequentlyAskedQuestions_662)
+
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
index 3344820ef..9768586c8 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack: Fulfillment'
 id: 1zGUEItEEVsal6cuBEBNcA
 status: PUBLISHED
 createdAt: 2023-04-10T15:43:59.687Z
-updatedAt: 2023-04-20T15:41:30.789Z
-publishedAt: 2023-04-20T15:41:30.789Z
+updatedAt: 2023-08-31T19:52:23.529Z
+publishedAt: 2023-08-31T19:52:23.529Z
 firstPublishedAt: 2023-04-10T17:57:34.714Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: vtex-pick-and-pack-fulfillment
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
+<div class = "alert alert-info">
+Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
 [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU) é uma solução para otimizar os processos de fulfillment das lojas, otimizando a coleta e o empacotamento dos pedidos, além da entrega last mile. A solução é composta pelas páginas de [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) e **VTEX Pick and Pack Fulfillment**, e aparece em seu Admin VTEX em **Apps**.
 
 O módulo **VTEX Pick and Pack Fulfillment** está relacionado ao processo de manuseio de pedidos e apresenta as seguintes seções:
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-insights.md b/docs/tutorials/pt/vtex-pick-and-pack-insights.md
new file mode 100644
index 000000000..33640f914
--- /dev/null
+++ b/docs/tutorials/pt/vtex-pick-and-pack-insights.md
@@ -0,0 +1,65 @@
+---
+title: 'VTEX Pick and Pack: Insights'
+id: 5C4wXYmbbHTnMAUO0o11rn
+status: PUBLISHED
+createdAt: 2024-01-05T17:27:08.558Z
+updatedAt: 2024-01-05T20:28:40.388Z
+publishedAt: 2024-01-05T20:28:40.388Z
+firstPublishedAt: 2024-01-05T20:24:02.931Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-insights
+locale: pt
+legacySlug: vtex-pick-and-pack-insights
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
+**Insights** é uma página do Admin VTEX que exibe informações sobre o desempenho da sua loja em relação ao VTEX Pick and Pack.
+
+![pick-pack-insights-pt](//images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/2764b70414073ede61f4481cd159ae6e/image.png)
+
+A página apresenta as seguintes seções:
+
+* [Pedidos - Total no período atual](#pedidos-total-no-periodo-atual)
+* [Tempo das etapas](#tempo-das-etapas)
+* [Pedidos - Orders Perfomance](#pedidos-orders-perfomance)
+* [Itens](#itens)
+
+## Pedidos - Total no período atual
+
+Nesta seção você terá acesso ao total de pedidos ou ordens de serviço de um determinado período de tempo e em determinadas instalações. Você pode selecionar os seguintes períodos:
+
+* Último dia
+* Último sete dias
+* Último mês
+* Últimos três meses
+* Últimos seis meses
+
+![pick-pack-insights-2-pt](//images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/8c4e56474ee580fa0b975912637ee596/image.png)
+
+## Tempo das etapas
+
+Nesta seção, você terá acesso às informações relativas a duração de cada etapa do processo de preparação dos pedidos. Você tem acesso ao tempo das seguintes etapas:
+
+* Tempo de separação
+* Tempo de embalagem
+* Tempo de envio
+
+![pick-pack-insights-3-pt](//images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/3123713047ffc0a8a3e74a3ac745468f/image.png)
+
+## Pedidos - Orders Perfomance
+
+Nesta seção você terá acesso às informações sobre o desempenho geral dos pedidos e o tempo médio de atendimento de cada pedido.
+
+![pick-pack-insights-4-pt](//images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/4260d9e311ad31e53f535d59e9b6f463/image.png)
+
+## Itens
+
+Nesta seção você terá acesso às informações sobre os itens dos pedidos gerenciados no VTEX Pick and Pack, o tempo médio de separação por item, quantidade de itens selecionados por separador e taxa de preenchimento dos pedidos.
+
+![pick-pack-insights-5-pt](//images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/40317d13fe72e856459cd97d7d66fb88/image.png)
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md b/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md
index 44528b1c6..fde798f50 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack: Last Mile'
 id: HN7WKV0xoq2ssVjsJlfzr
 status: PUBLISHED
 createdAt: 2023-04-10T16:01:14.613Z
-updatedAt: 2023-04-20T15:46:42.209Z
-publishedAt: 2023-04-20T15:46:42.209Z
+updatedAt: 2023-08-25T15:52:19.799Z
+publishedAt: 2023-08-25T15:52:19.799Z
 firstPublishedAt: 2023-04-10T16:35:43.623Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -16,3 +16,8 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
 <div class="alert alert-warning" role="alert">Conteúdo em tradução.</div>
+
+<div class = "alert alert-info">
+Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
new file mode 100644
index 000000000..ac2f375fc
--- /dev/null
+++ b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
@@ -0,0 +1,225 @@
+---
+title: 'VTEX Pick and Pack Mobile'
+id: 3i1K01CQlDBFYYp42WFOet
+status: PUBLISHED
+createdAt: 2024-04-04T20:42:46.548Z
+updatedAt: 2024-04-06T02:45:49.741Z
+publishedAt: 2024-04-06T02:45:49.741Z
+firstPublishedAt: 2024-04-06T01:59:46.300Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-mobile
+locale: pt
+legacySlug: vtex-pick-and-pack-mobile
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+<p>Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+O aplicativo móvel do [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) auxilia o separador - profissional responsável por selecionar e empacotar itens na instalação - no manuseio de pedidos, abrangendo desde a separação dos itens até o envio. Assim, o fluxo de separação e entrega dos pedidos da loja torna-se mais organizado e fluido.
+
+![pickpack-mobile-pt](//images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/825577c3ee5232ac15408d243a20d04e/image.png)
+
+O manuseio do pedido é dividido em quatro etapas, seguindo o caminho normal de pedidos na loja:
+
+1. [Criar ordem de serviço](#criar-ordem-de-servico)
+2. [Separação dos produtos](#separacao-dos-produtos)
+3. [Empacotamento do pedido](#empacotamento-do-pedido)
+4. [Envio dos pacotes](#envio-dos-pacotes)
+
+## Ordens de serviço
+
+Uma ordem de serviço consiste em um conjunto de pedidos que serão processados pelo fluxo do Pick and Pack simultaneamente. Essa abordagem permite uma gestão eficiente, agilizando o processamento simultâneo de múltiplos pedidos.
+
+Por exemplo, considere uma ordem de serviço que inclua apenas três pedidos:
+
+- Pedido 1: uma camiseta vermelha e uma saia rosa.
+- Pedido 2: duas camisetas vermelhas e um chapéu branco.
+- Pedido 3: uma saia rosa e um chapéu branco.
+
+Ao selecionar esta ordem de serviço para manuseio, o aplicativo indicará a separação de:
+
+- Três camisetas vermelhas.
+- Duas saias rosa.
+- Dois chapéus brancos.
+
+Em seguida, o aplicativo te auxiliará no empacotamento de cada pedido com seus respectivos itens.
+
+<div class="alert alert-warning">
+Ordens de serviço se aplicam apenas às fases de separação e empacotamento de pedidos. Você deve fazer o envio de cada pedido separadamente.
+</div>
+
+### Criar ordem de serviço
+
+A aba __Sem alocação__ lista os pedidos que devem ser selecionados para [ordens de serviço](#ordem-de-servico).
+
+![pickpack-ordemservico-pt](//images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/ed6060bd509ee50e397b06e62a335547/image.png)
+
+Para criar uma ordem de serviço, siga os passos abaixo:
+
+1. Na tela inicial, clique em Sem alocação <i class="fas fa-arrow-right"></i>.
+2. Selecione os pedidos que deseja incluir na ordem de serviço. Para criar uma ordem de serviço com todos os pedidos, clique em <i class="fas fa-square"></i> `Selecionar tudo`.
+3. Clique em `Iniciar separação`.
+
+## Separar produtos
+
+A etapa de separação consiste em selecionar fisicamente os itens correspondentes a uma [ordem de serviço](#ordens-de-servico) e direcioná-los até a área adequada para empacotamento na sua instalação.
+
+### Ordens de serviço pendentes
+
+A aba __Pendentes__ exibe a lista de ordens de serviço que ainda não tiveram sua separação finalizada.
+
+![pickpack-pendente-pt](//images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/617071b6d8e6f098f74aa466bd5321fc/image.png)
+
+Nesta aba, é possível selecionar pelo ID de uma ordem de serviço, caso queira visualizar apenas os itens separados daquele pedido.
+
+Caso haja ordens de serviço atribuídas ao separador, é possível acessá-las na tela de separação seguindo estes passos:
+
+1. Na tela inicial do aplicativo, clique em **Continuar separação**. Será exibida uma lista com as [ordens de serviço](#ordens-de-servico) designadas ao separador que estão na etapa de separação.
+2. Clique na ordem de serviço que deseja separar.
+
+Ao clicar em uma ordem de serviço, as seguintes informações são exibidas:
+
+- __Item(ns):__ produtos que devem ser separados na ordem de serviço.
+- __Informações:__ informações gerais da ordem de serviço e do pedido.
+- __Resumo:__ produtos que já foram separados pelo separador.
+
+![pickpack-em-separacao-pt](//images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/5f0e48be4c066bf3aa3757f0ddc3db07/image.png)
+
+Ao clicar no menu <i class="fas fa-ellipsis-v"></i>, serão exibidas as seguintes ações:
+
+- **Adicionar observação:** adiciona uma observação livre à ordem de serviço.
+- **Marcar como pronto para empacotar:** utilizada para separar pedidos em massa ou recusar pedidos em massa.
+- **Pausar separação:** pausa a contagem de tempo referente à separação da ordem de serviço.
+- **Abrir leitor de código de barras:** utiliza a câmera do dispositivo para ler código de barras dos produtos.
+- **Imprimir lista de separação:** disponibiliza um documento com a lista de itens da ordem de serviço para impressão.
+- **Fechar menu:** fecha o menu e volta para a tela de separação. 
+
+Para separar um produto, siga estes passos:
+
+1. Na tela de __Separação__, acesse a aba __Item(ns)__.
+2. Clique no produto que deseja separar ou deslize o produto para a direita. Caso o produto tenha mais de uma unidade, é necessário clicar a quantidade de unidades do produto. Para produtos que contém peso ou volume é preciso confirmar a medida e depois confirmar a seleção, como o exemplo abaixo.
+
+![pickpack-item-pt](//images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/f46444bb6af306fc698e2084473a421d/image.png)
+
+Para separar todos os produtos da ordem de serviço de uma única vez, siga estes passos:
+
+1. Clique no menu <i class="fas fa-ellipsis-v"></i>.
+2. Clique na opção **Marcar como pronto para empacotar.** 
+3. Clique em **Separar todos os itens disponíveis.**
+
+Uma vez separados, os produtos são listados na aba __Resumo__.
+
+## Recusar itens
+
+Há cenários em que pode ser necessário recusar produtos por conta das configurações da loja e disponibilidade dos itens no inventário. 
+
+<div class="alert alert-warning">
+A opção de recusar itens pode não estar disponível. Em caso de dúvida, consulte a administração da loja.
+</div>
+
+Para recusar um produto da ordem de serviço, siga os passos abaixo:
+
+1. Acesse a aba __Item(ns)__.
+2. Clique e deslize para a esquerda o produto que deseja recusar.
+3. Selecione a razão da recusa da lista **Motivos de recusa**.
+  ![pickpack-item-recusa-pt](//images.ctfassets.net/alneenqid6w5/2rFwEeBHOf6PLRpgpcdDTL/08fac545bfe628e5211c0c818a22c3df/image.png)
+4. Selecione a quantidade de itens que deseja recusar ou clique em `Confirmar e descartar todas as unidades`.
+5. Clique em `Descartar unidades`.
+
+Para recusar todos os produtos da ordem de serviço de uma única vez, siga estes passos:
+
+1. Clique no menu <i class="fas fa-ellipsis-v"></i>.
+2. Clique na opção **Marcar como pronto para empacotar.** 
+3. Toque em **Recusar todos os itens disponíveis.**
+
+<div class="alert alert-danger">
+Se todos os itens de um pedido forem recusados, o pedido será concluído automaticamente.
+</div>
+
+## Substituir itens
+
+Outra opção para casos de itens indisponíveis é substituir o item por um outro, a depender das configurações da loja e disponibilidade dos itens no inventário.
+
+<div class="alert alert-warning">
+A opção de substituir itens pode não estar disponível. Em caso de dúvida, consulte a administração da loja.
+</div>
+
+Para substituir itens da ordem de serviço, siga os passos abaixo:
+
+1. Acesse a aba __Item(ns)__.
+2. Pressione o produto que deseja substituir.
+3. Clique na opção **Substituir item**.
+4. Busque ou selecione o item que substituirá o produto do pedido e clique na caixa de seleção <i class="fas fa-check-square"></i>.
+  ![pickpack-item-substituir-pt](//images.ctfassets.net/alneenqid6w5/3rdotgG0FkRbv3AprESrYA/6558b779984c5b763bfbc5e3a87c838d/image.png)
+5. Selecione o número de unidades que deverão ser substituídas.
+6. Selecione o motivo da substituição dentre as opções da lista.
+7. Preencha o campo **Descrição** com mais informações sobre a substituição.
+8. Clique no botão `Confirmar substituição`.
+
+## Concluir separação
+
+Uma vez que todos os itens da ordem de serviço foram separados, recusados ou substituídos, clique no botão `Iniciar empacotamento` para que a ordem de serviço passe para a etapa de [empacotamento](#empacotamento).
+
+## Empacotamento
+
+Na etapa de empacotamento, o separador seleciona os itens de cada pedido nas respectivas embalagens de envio. O aplicativo móvel do Pick and Pack permite organizar todos os pacotes necessários para diversos pedidos de forma simples e fácil.
+
+![pickpack-empacotamento-pt](//images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/346447464d242ff16d085322378503fe/image.png)
+
+É possível acessar a página de Empacotamento ao [concluir a separação](#concluir-separacao) de uma ordem de serviço ou seguindo estes passos:
+
+1. Na tela inicial do aplicativo, clique em **Para empacotar**. Será exibida uma lista com as [ordens de serviço](#ordens-de-servico) designadas ao separador que estão na etapa de empacotamento.
+2. Clique na ordem de serviço cujos produtos deseja separar. 
+
+![pickpack-item-pendente-pt](//images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/abcca3f55094eea7f71c73660bd1b5f0/image.png)
+
+Siga os passos abaixo para empacotar itens:
+
+1. Em Empacotamento, clique no pedido que deseja empacotar. 
+2. Clique no botão <i class="fas fa-plus"></i> do produto que deseja adicionar no pacote ou clique em <i class="fas fa-box"></i> para empacotar todos os produtos ao mesmo tempo.
+<div class="alert alert-warning">
+Caso opte por empacotar todos os itens do pedido, os produtos que ainda não foram empacotados serão registrados em um único novo pacote.
+</div>
+4. Selecione um pacote já registrado ou adicione um novo pacote clicando em `+ Criar pacote`. 
+5. Selecione o tipo do pacote que deseja adicionar.
+6. Selecione o número de unidades deste produto que deseja adicionar àquele pacote.
+7. Clique no botão `Empacotar produto`.
+
+É necessário repetir este procedimento quantas vezes for necessário para empacotar todos os itens referente a uma ordem de serviço.
+
+Os itens que já foram empacotados estão disponíveis na aba **Itens empacotados**. É possível alternar a visualização dos itens entre uma lista de itens ou de pedidos e pacotes, clicando em <i class="fas fa-toggle-on"></i>.
+
+__Lista de itens__
+![pickpack-item-empacotado-pt](//images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/5bb135ce0588205f44ff5511681ff816/image.png)
+
+__Pedidos e pacotes__
+![pickpack-item-empacotado-2-pt](//images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/fbaaedf590f158d3dbc9d24941d9f15a/image.png)
+
+### Envio
+
+A fase de envio permite criar serviços de envio referentes a pedidos que foram separados e empacotados.
+
+<div class="alert alert-warning">
+O envio é uma etapa opcional do aplicativo, a depender da sua operação e configurações feitas pelo administrador de loja.
+</div>
+
+Para enviar pacotes no aplicativo Pick and Pack, siga os passos abaixo:
+
+1. Na tela inicial, clique no menu <i class="fas fa-ellipsis-v"></i>.
+2. Clique na opção **Para envio.**
+3. Selecione o pacote que deseja enviar. Aqui é preciso selecionar um pedido que tenha status `Preparando envio`.
+4. Preencha as informações de envio:
+    - **Data prevista para coleta**
+    - **Data prevista para entrega**
+    ![pickpack-envio-pt](//images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/913d43663fb129edf3750b852bad2706/image.png)
+5. Selecione uma transportadora disponível.
+6. Clique em `Selecionar e continuar`.
+7. Confirme as informações do envio. Se nenhuma correção for necessária, clique no botão `Criar serviço`. Caso contrário, clique em `Voltar` e volte ao passo 5. 
+
+Finalizado o cadastro, as informações do envio serão exibidas na tela seguinte no aplicativo. Os pedidos enviados estão disponíveis pelo menu <i class="fas fa-ellipsis-v"></i> __> Concluído__. 
+
+![pickpack-finalizacao-pt](//images.ctfassets.net/alneenqid6w5/40mZiPyjG5VEHmcDazxUrI/2007a8d429ddb218f53add49575c0e76/image.png)
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-orders.md b/docs/tutorials/pt/vtex-pick-and-pack-orders.md
new file mode 100644
index 000000000..2da7d1d83
--- /dev/null
+++ b/docs/tutorials/pt/vtex-pick-and-pack-orders.md
@@ -0,0 +1,95 @@
+---
+title: 'VTEX Pick and Pack: Pedidos'
+id: 3rGbJlyedHdbWjvZ52p95b
+status: PUBLISHED
+createdAt: 2023-12-14T17:26:02.135Z
+updatedAt: 2024-01-05T17:31:16.218Z
+publishedAt: 2024-01-05T17:31:16.218Z
+firstPublishedAt: 2023-12-19T15:00:12.093Z
+contentType: tutorial
+productTeam: Shopping
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-pedidos
+locale: pt
+legacySlug: vtex-pick-and-pack-pedidos
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
+**Pedidos** é uma página do Admin VTEX que exibe as informações dos pedidos realizados e gerenciados pelo [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU).  
+
+Esta página permite que você realize as seguintes ações: 
+
+* [Consultar pedido](#consultar-pedido)
+* [Buscar pedido](#buscar-pedido)
+* [Filtrar pedidos](#filtrar-pedido)
+* [Exportar pedidos](#exportar-pedidos)
+
+![pick-and-pack-pedidos-PT](//images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/83a5b409f6cbeff9c7efbdfe55b22fbe/image.png)
+
+A página apresenta as seguintes informações em uma tabela: 
+
+| Campo da tabela | Descrição                                                                             |
+| --------------- | ------------------------------------------------------------------------------------- |
+| ID do pedido    | Número identificador do pedido. Indica também a data de criação do pedido.            |
+| Faturas         | Situação de fatura do pedido, com valores possíveis **Faturados** e **Não faturados**.        |
+| Item(ns)        | Quantidade de itens que compõe o pedido.                                              |
+| Envio           | Tipo de envio do pedido, com valores possíveis **Entrega ao cliente** e **Retirada na loja**. |
+| Pagamento       | Meio de pagamento utilizado para realizar o pedido.                                   |
+| Tags            | Tags relacionadas à venda do pedido, como UTM ou cupons.                              |
+| Prazo           | Prazo de entrega ou retirada do pedido.                                               |
+| Status          | Etapa do processo de fulfillment do pedido.                                           |
+
+## Consultar pedido
+
+Você pode otimizar a consulta de pedidos a partir das seguintes abas:
+
+* **Todos:** todos os pedidos realizados.
+* **Pendente:** pedidos pendentes, em separação de itens e em preparação.
+* **Para envio:** pedidos que estão aguardando o envio.
+* **Entregue:** pedidos que foram entregues ao cliente, seja por retirada em loja ou entregue pela transportadora.
+* **Cancelado:** pedidos cancelados.
+* **Rejeitado:** pedidos rejeitados.
+
+Você também pode acessar informações mais detalhadas sobre cada pedido clicando no respectivo pedido na tabela.
+
+![pick-and-pack-pedidos-2-PT](//images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/20b4531d5c5f49f9f70ea4c839fcaacb/image.png)
+
+Ao selecionar o pedido desejado, você terá acesso às seguintes informações:
+
+* **Item(ns):** lista de itens que compõem o pedido. É possível buscar por um item digitando o SKU ID ou nome do item na barra de busca. Além disso, é possível clicar no item para acessar informações mais detalhadas sobre ele.
+* **Observações do pedido:** observações adicionadas pelo lojista.
+* **Informações do envio:** informações sobre o envio do pedido, incluindo o status do envio. 
+* **Informações de pagamento:** informações sobre o pagamento realizado no pedido.
+* **Informações adicionais:** informações adicionais do pedido.
+* **Logs:** linha do tempo com o histórico de atualizações do pedido.
+
+## Buscar pedido
+
+Você pode buscar um pedido utilizando a barra de busca. Para isso, digite o ID do pedido na barra de busca, por exemplo `SLR-1341470502250-01`. 
+
+## Filtrar pedido
+
+Você pode refinar a busca e a visualização dos pedidos, selecionando a opção **Filtrar**. Filtre os pedidos utilizando as seguintes opções:  
+
+* **Data de criação:** selecione a data de criação do pedido.
+* **Data de entrega:** selecione a data de criação do pedido.
+* **Categorias:** selecione a categoria que os itens do pedido estão contidos.
+* **Meios de pagamento:** selecione o meio de pagamento utilizado no pedido.
+* **Estratégia de envio:** selecione a estratégia de envio utilizada no pedido.
+* **Tipo de envio:** selecione o tipo de envio utilizado no pedido.
+
+Clique em `Limpar tudo` para remover os filtros selecionados.
+
+## Exportar pedidos
+
+Você pode exportar os pedidos seguindo os passos abaixo:
+
+1. Clique em `Exportar`.
+2. Selecione os dados que deseja exportar: `Relatório de pacotes` ou `Orders Reports`.
+    * No caso de `Relatório de pacotes`, você deve selecionar o período que deseja exportar, o tipo e o método de envio.
+  ![pick-and-pack-pedidos-3-PT](//images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/b0f36539e9039aa4e127fc49e47f8a6b/image.png)
+3. Clique em `Exportar`.
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-settings.md b/docs/tutorials/pt/vtex-pick-and-pack-settings.md
new file mode 100644
index 000000000..be50022b7
--- /dev/null
+++ b/docs/tutorials/pt/vtex-pick-and-pack-settings.md
@@ -0,0 +1,269 @@
+---
+title: 'VTEX Pick and Pack: Configurações'
+id: 16cs3e7hWk7c4cSZqe10O9
+status: PUBLISHED
+createdAt: 2024-01-05T20:43:38.480Z
+updatedAt: 2024-01-09T18:30:22.578Z
+publishedAt: 2024-01-09T18:30:22.578Z
+firstPublishedAt: 2024-01-09T16:30:00.192Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-configuracoes
+locale: pt
+legacySlug: vtex-pick-and-pack-configuracoes
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
+**Configurações** é uma página do Admin VTEX que permite selecionar as configurações desejadas para o funcionamento do VTEX Pick and Pack na sua loja. As configurações estão distribuídas nas seguintes abas:
+
+* [Separação](#separacao)
+* [Categorias](#categorias)
+* [Empacotamento](#empacotamento)
+* [Pedidos](#pedidos)
+* [Automação](#automacao)
+* [Usuários](#usuarios)
+* [Catálogo](#catalogo)
+* [Instalações](#instalacoes)
+
+## Separação
+
+Nesta aba, você encontrará as configurações relacionadas à etapa de separação de itens do pedido. Nela você consegue definir ações que o separador pode realizar durante o processo de separação, incluindo informar que um item do pedido não estava disponível e sugerir uma substituição.
+
+![pick-and-pack-separacao-pt](//images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/a57a373de5dc0b3875f2e4286ab039b4/image.png)
+
+### Estratégia de separação
+
+Nesta seção, você pode definir o tipo de estratégia de separação que deseja para os seus separadores.
+
+<div class = "alert alert-info">
+  Apenas a estratégia <strong>Separação por ondas</strong> está disponível no momento.
+</div>
+
+### Alterações no pedido
+
+Nesta seção, você pode definir ações sobre a alteração de um pedido, por falta de itens, por exemplo.
+
+* **Enviar alterações para o OMS:** permite enviar as alterações feitas pelo separador para o [OMS](https://help.vtex.com/pt/tutorial/gerenciamento-de-pedidos-visao-geral--tutorials_201#) da VTEX. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir alterar os preços dos itens:** permite o separador alterar os preços dos itens de um pedido. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir substituição de itens:** permite o separador substituir itens do pedido que estavam indisponíveis. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir recusar itens:** permite o separador a recusar itens do pedido que estejam indisponíveis. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir alterar a quantidade dos itens:** permite o separador alterar a quantidade de itens do pedido. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir adicionar observações nos pedidos:** permite o separador adicionar observações nos pedidos, como indicando motivo de alteração de preço, por exemplo. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir adicionar observações nos itens:** permite o separador adicionar observações nos itens, como indicando motivo de recusa de um item, por exemplo. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Motivos de recusa:** indica as opções que o separador poderá selecionar como motivo de recusa de itens do pedido. Você pode inserir quantas opções desejar.
+* **Motivos de alteração de preços:** indica as opções que o separador poderá selecionar como motivo de alteração de preço de itens do pedido. Você pode inserir quantas opções desejar.
+* **Limite de alterações da quantidade de itens dos pedidos:** porcentagem que limita quantos itens podem sofrer alterações em relação à quantidade em cada pedido. 
+* **Limite de alterações de preço dos itens dos pedidos:** porcentagem que limita quantos itens podem sofrer alterações em relação ao preço em cada pedido. 
+* **Limite total de alterações nos pedidos:** porcentagem que limita a quantidade total de pedidos que podem sofrer alterações. 
+
+### Ordens de serviço
+
+Nesta seção, você pode definir as opções que serão aplicadas às ordens de serviço da sua loja. 
+
+* **Permitir vários pedidos em uma ordem de serviço:** permite adicionar vários pedidos a uma ordem de serviço. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Ativar separação rápida:** permite ativar a separação rápida, realizando a confirmação automática da quantidade e do preço dos produtos, evitando a necessidade da confirmação manual pelo seletor. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Ativar express fulfillment:** ativa a opção de express fulfillment, que permite a separação e o empacotamento do pedido simultaneamente. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir mover os pedidos após a separação ter sido iniciada:** permite editar as ordens de serviço, mesmo depois do processo de separação ter sido iniciado. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir mover pedidos entre ordens de serviço:** permite editar as ordens de serviço, movendo os pedidos adicionados entre elas. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Tags de ordem de serviço:** permite adicionar tags customizadas a fim de automatizar o processo de separação dos pedidos.
+* **Ativar códigos EAN dinâmicos:** permite ativar código de barras dinâmicos, os quais podem ser alterados dependendo das características do produto, como peso. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+
+### Apresentação
+
+Você pode habilitar o processo de configuração do aplicativo do VTEX Pick and Pack por meio dos passos abaixo:
+
+1. Clique em `Apresentação`.
+2. Clique em `Início`.
+3. Selecione as opções que serão definidas para o aplicativo. Estas configurações só serão aplicadas na conta principal.
+4. Clique em `Próximo`.
+5. Selecione as ordens de serviço que serão gerenciadas no aplicativo e o número de separadores que devem ser criados.
+6. Clique em `Próximo`.
+7. Ative <i class="fas fa-toggle-on"></i> os vendedores aos quais deseja aplicar as configurações.
+8. Clique em `Concluído`.
+9. Clique em `Fechar`, para finalizar.
+
+Clique em `Salvar` para registrar as alterações feitas na aba.
+
+## Categorias
+
+Nesta aba, você pode configurar a ordem das categorias em que os pedidos serão separados. Dessa forma, o separador consegue organizar o fluxo de coleta dos produtos para a montagem dos pedidos com eficiência.
+
+![pick-pack-categorias-pt](//images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/700e3120ee48d2b4e557e12325f7fe6f/image.png)
+
+* **Configuração rápida:** habilita as configurações em todas as instalações. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Instalação**: determina qual a instalação terá as configurações de categorias aplicadas.
+
+Para adicionar uma categoria na lista, clique na categoria desejada. Para reordenar, arraste a categoria na lista para a posição desejada.
+
+Você pode importar um arquivo CSV ou exportar a lista que já está configurada.
+
+## Empacotamento
+
+Nesta aba, você encontrará as configurações relacionadas à etapa de empacotamento de itens do pedido. 
+
+![pick-pack-empacotamento-pt](//images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/dfef3cd4f98481adef1f31c9b5be8da7/image.png)
+
+* **Permitir relatório de pacotes:** habilita a exibição de relatório de pacotes. O relatório será exibido  na tela de **Pedidos**. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+* **Permitir empacotamento automático:** habilita o empacotamento automático. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
+
+### Configuração de impressão das etiquetas dos pacotes
+
+Nesta seção, você irá configurar as características da etiqueta que será colada ao pacote do pedido. Veja abaixo as características disponíveis: 
+
+* **Configuração de impressão das etiquetas dos pacotes ativa:** ativa ou desativa a possibilidade de editar as características das etiquetas.
+* **Formato:** determina o formato da etiqueta.
+* **Tamanho da fonte (px):** determina o tamanho da fonte que será impressa na etiqueta, em pixels.
+
+#### Margens
+
+* **Esquerda:** tamanho da margem esquerda da etiqueta em milímetros.
+* **Direita:** tamanho da margem direita da etiqueta em milímetros.
+* **Superior:** tamanho da margem superior da etiqueta em milímetros.
+* **Inferior:** tamanho da margem inferior da etiqueta em milímetros.
+
+#### Dimensões
+
+* **Largura:** largura da etiqueta em milímetros.
+* **Altura:** altura da etiqueta em milímetros.
+
+### Configuração de impressão de recibos
+
+Nesta seção, você irá configurar as características da impressão de recibos dos pedidos. Veja abaixo as características disponíveis: 
+
+* **Configuração de impressão de recibos ativa:** ativa ou desativa a possibilidade de editar as características do recibo.
+* **Formato:** determina o formato do recibo.
+* **Tamanho da fonte (px):** determina o tamanho da fonte que será impressa no recibo, em pixels.
+
+#### Margens
+
+* **Esquerda:** tamanho da margem esquerda do recibo.
+* **Direita:** tamanho da margem direita do recibo.
+* **Superior:** tamanho da margem superior do recibo.
+* **Inferior:** tamanho da margem inferior do recibo.
+
+#### Dimensões
+
+* **Largura:** largura do recibo.
+* **Altura:** altura do recibo.
+
+### Envelopes
+
+Nesta seção, você deve cadastrar os tipos de envelopes que serão utilizados pela sua loja para realizar o empacotamento e envio dos pedidos. Para cadastrar um novo envelope, siga os seguintes passos:
+
+1. Clique em `Criar`.
+2. Preencha o formulário abaixo:
+   * **Nome:** nome que irá identificar o envelope.
+   * **Tipo:** tipo do envelope. Os tipos possíveis de envelopes são **Caixa, Sacola, Envelopes, Fita, Papel, Outros**.
+   * **Descrição:** descrição do envelope para uso interno.
+   * **Código:** código identificador do envelope.
+   * **Peso cúbico:** [peso cúbico](https://help.vtex.com/pt/tutorial/como-o-peso-cubado-e-calculado--tutorials_128) do envelope. 
+   * **Altura:** altura do envelope em milímetros. 
+   * **Comprimento:** comprimento do envelope em milímetros.
+   * **Peso:** peso do envelope em milímetros.
+   * **Largura:** peso do envelope em milímetros.
+3. Clique em `Salvar` para finalizar.
+
+Clique em `Salvar` para registrar as alterações feitas na aba.
+
+## Pedidos
+
+Nesta aba, você encontrará configurações relacionadas aos pedidos processados pelo VTEX Pick and Pack.
+
+![pick-pack-config-pedidos-pt](//images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/70c1a50002db6ec6f984b0382391483a/image.png)
+
+* **Baixar pedidos do OMS:** permite exportar pedidos do OMS.
+* **Meios de pagamento:** meios de pagamento utilizados nos pedidos que serão exportados.
+* **Métodos de envio:** métodos de envio utilizados nos pedidos que serão exportados.
+* **Tipo de envio:** tipos de envio utilizados nos pedidos que serão exportados.
+* **Tags de pedidos:** tags utilizadas nos pedidos que serão exportados.
+
+Clique em `Salvar` para registrar as alterações feitas na aba.
+
+## Automação
+
+Nesta aba, você encontrará as configurações de automação de processos do VTEX Pick and Pack.
+
+![pick-pack-automacao-pt](//images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/2d72b5f563970d8deb9041e2b5d301e8/image.png)
+
+Para criar uma nova automação, siga os passos abaixo:
+
+1. Clique em `Criar`.
+2. Preencha o campo **Nome** com o nome da automação e **Automação para** com a opção que deseja automatizar.
+3. Clique em `Salvar` para finalizar.
+
+## Usuários
+
+Nesta aba, você fará o gerenciamento dos usuários, admins e separadores, da sua operação VTEX Pick and Pack. Usuários com permissão **Admin** terão acesso ao Admin VTEX e poderão realizar alterações na ferramenta. Usuários com permissão **Separador** terão acesso apenas ao aplicativo do VTEX PIck and Pack. 
+
+![pick-pack-usuarios-pt](//images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/b2d142e6e32bef9d35a6afa9feedaca9/image.png)
+
+Para criar um novo usuário, siga os seguintes passos:
+
+1. Clique em `Criar`.
+2. Selecione o tipo de permissão que deseja para o seu novo usuário: **Admin** ou **Separador**.
+3. Realize o cadastro de acordo com a permissão desejada: 
+     * Permissão **Admin**
+        1. Selecione o usuário listado que deseja cadastrar como **Admin**.
+        2. Clique em `Criar`.
+![pick-pack-usuarios-2-pt](//images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/a0b7366fe48d624a3470933629474032/image.png)
+     * Permissão **Separador**
+        1.  Preencha o formulário com as seguintes informações:
+           * Nome de usuário
+           * Nome
+           * Email (campo obrigatório)
+           * Senha (campo obrigatório)
+           * Instalações
+           * Permitir o envio de pacotes
+           * Categorias
+        2. Clique em `Criar`.
+        ![pick-pack-usuarios-3-pt](//images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/e06dcefd1c9f172c90debd7c2108c049/image.png)
+
+## Catálogo
+
+Nesta aba, você terá acesso às informações dos itens dos pedidos que estão na etapa de entrega para o cliente.
+
+![pick-pack-catalogo-pt](//images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/b517d26ac0b52f72ac4e97e65b232979/image.png)
+
+A página apresenta as seguintes informações em uma tabela: 
+
+| Campos da coluna | Descrição                                                                                                                   |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
+| Item             | Nome do produto.                                                                                                            |
+| ID do produto    | Número identificador do produto.                                                                                            |
+| SKU              | Número identificador do SKU do produto.                                                                                     |
+| EAN              | Número EAN do produto.                                                                                                      |
+| Categorias       | Categorias em que o produto está cadastrado.                                                                                |
+| Dimensões        | Dimensões do produto.                                                                                                       |
+| Peso             | Peso do produto.                                                                                                            |
+| Pesável          | Produtos que precisam ser pesados para fornecer sua unidade de medida em quilogramas ou gramas, dependendo da configuração. |
+| Temperatura      | Produtos que devem ser armazenados em uma temperatura mínima para evitar deterioração.                                      |
+| Ativo            | Se o produto está disponível para os clientes ou não.                                                                       |
+
+Você pode adicionar SKU IDs e EANs dos seus produtos em massa, por meio de um arquivo CSV. Para isso, siga os passos abaixo:
+
+1. Clique no botão `Carregar códigos SKU/EAN em massa`.
+2. Adicione o arquivo que deseja fazer upload.
+3. Clique em `Continuar`.
+
+Você também pode indexar o catálogo para atualizar a listagem de produtos. Para isso, clique em `Indexar catálogo` e depois em `Continuar`.
+
+<div class = "alert alert-danger">
+A indexação do catálogo irá apagar e recriar todo o conteúdo dele, o que significa que você poderá perder todos os códigos EAN e SKU personalizados.
+</div>
+
+## Instalações
+
+Nesta aba, você terá acesso ao cadastro e consulta das instalações da sua loja.
+
+![pick-pack-instalacoes-pt](//images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/14186600ad10fec8354aa80e7c1a077e/image.png)
+
+Para criar uma nova instalação, siga os seguintes passos:
+
+1. Clique em `Criar`.
+2. Preencha o formulário com as informações de localização da sua instalação. É obrigatório preencher os campos **Rua**, **Cidade** e **Estado**.
+3. Clique em `Salvar` para finalizar.
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md b/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
new file mode 100644
index 000000000..fe5074fcc
--- /dev/null
+++ b/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
@@ -0,0 +1,79 @@
+---
+title: 'VTEX Pick and Pack: Ordens de serviço'
+id: 7bUwvmTY6eOqxzhyMIIzvz
+status: PUBLISHED
+createdAt: 2024-01-03T18:38:05.781Z
+updatedAt: 2024-01-03T20:13:50.986Z
+publishedAt: 2024-01-03T20:13:50.986Z
+firstPublishedAt: 2024-01-03T19:55:03.094Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 2o8pvz6z9hvxvhSoKAiZzg
+slug: vtex-pick-and-pack-ordens-de-servico
+locale: pt
+legacySlug: vtex-pick-and-pack-ordens-de-servico
+subcategory: 7Kllu6CmeLNV3tYXlCFvOt
+---
+
+<div class = "alert alert-info">
+Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
+**Ordens de serviço** é uma página do Admin VTEX que gerencia, em tempo real, as ordens de serviço utilizadas pelos separadores para agrupar e separar os itens de cada pedido. O separador pode agrupar quantos pedidos desejar em cada ordem de serviço. 
+
+Esta página permite que você realize as seguintes ações: 
+
+* [Criar ordem de serviço](#criar-ordem-de-servico)
+* [Buscar ordem de serviço](#buscar-ordem-de-servico)
+* [Filtrar ordens de serviço](#filtrar-ordem-de-servico)
+
+![pick-pack-ordem-servico-pt](//images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/0d7875431b5940b7d94bcc7d156c4d7c/image.png)
+
+As ordens de pedido são apresentadas em cartões contendo as seguintes informações: 
+
+![pick-pack-ordem-servico-2-pt](//images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/c8143a8bf5b02f69cf6906531e46b755/image.png)
+
+* ID da ordem de serviço.
+* Quantidade de pedidos contidos na ordem de serviço.
+* Quantidade de itens contidos na ordem de serviço.
+* Nome do separador responsável pela ordem de serviço.
+* Nome da instalação.
+* Status da ordem de serviço.
+
+## Criar ordem de serviço
+
+Você pode criar uma nova ordem de serviço seguindo os passos descritos abaixo:
+
+1. No menu **Pedidos não alocados**, selecione os pedidos desejados para incluir na ordem de serviço. Não há limite para a quantidade de pedidos por ordem de serviço.
+2. Clique em `Alocar para`.
+3. Clique na aba **Manual** para criar manualmente a ordem de serviço.
+4. Clique em `+` para criar uma ordem de serviço. Você pode criar mais de uma ordem de serviço.
+5. Arraste os pedidos que deseja para a ordem de serviço.
+  ![pick-pack-ordem-servico-3-pt](//images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/9fff8b6632fe20c3b5e8b6b568b5adc1/image.png)
+6. Clique em `Criar` para finalizar.
+
+## Consultar ordem de serviço
+
+Você pode otimizar a consulta por ordens de serviço a partir das seguintes abas:
+
+* **Todos:** todas as ordens de serviço organizadas.
+* **Separando:** ordens de serviço que estão em andamento, com a separação de itens dos pedidos.
+* **Empacotando:** ordens de serviço que estão aguardando o envio.
+* **Concluído:** ordens de serviço de pedidos que foram concluídos.
+* **Cancelado:** ordens de serviço de pedidos cancelados.
+
+Você também pode acessar mais informações de cada ordem de serviço clicando no botão <i class="fas fa-chevron-down"></i> no bloco.
+
+![pick-pack-ordem-servico-4-pt](//images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/bb8e751deeb457a5f2d73a941ef05689/image.png)
+
+## Buscar ordem de serviço
+
+Você pode buscar uma ordem de serviço utilizando a barra de busca. Você pode digitar o ID da ordem de serviço ou o ID do pedido que deseja encontrar.
+
+## Filtrar ordem de serviço
+
+Você pode refinar a busca e a visualização dos pedidos, selecionando a opção **Filtrar**. Filtreas ordens de serviço pelas opções: 
+
+* **Categorias:** categorias que contém os itens dos pedidos.
+* **Separadores disponíveis:** pelos separadores disponíveis.
+* **Instalações:** pelas instalações cadastradas, podendo ser todas ou específicas.
diff --git a/docs/tutorials/pt/vtex-pick-and-pack.md b/docs/tutorials/pt/vtex-pick-and-pack.md
index 409db78e9..fbf6cf4ac 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack.md
@@ -3,8 +3,8 @@ title: 'VTEX Pick and Pack'
 id: 1OOops3WrUyz7e0bnhkfXU
 status: PUBLISHED
 createdAt: 2023-04-10T15:22:56.572Z
-updatedAt: 2023-04-20T00:55:31.302Z
-publishedAt: 2023-04-20T00:55:31.302Z
+updatedAt: 2023-08-25T15:48:44.351Z
+publishedAt: 2023-08-25T15:48:44.351Z
 firstPublishedAt: 2023-04-10T15:42:38.221Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,6 +15,10 @@ legacySlug: vtex-pick-and-pack
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
+<div class = "alert alert-info">
+Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
+</div>
+
 **VTEX Pick and Pack** é a solução que permite aos comerciantes gerenciar a coleta, o empacotamento e a entrega de pedidos a partir de lojas físicas e estoques para endereços de clientes ou [pontos de retirada](https://help.vtex.com/pt/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). Todo o gerenciamento é feito em um só lugar, gerando maior controle e visibilidade para os comerciantes em todo o processo de fulfillment.
 
 ## Funcionalidades
diff --git a/docs/tutorials/pt/vtex-shield.md b/docs/tutorials/pt/vtex-shield.md
new file mode 100644
index 000000000..c2407e1a0
--- /dev/null
+++ b/docs/tutorials/pt/vtex-shield.md
@@ -0,0 +1,63 @@
+---
+title: 'VTEX Shield'
+id: 2CVk6H9eY2CBtHjtDI7BFh
+status: PUBLISHED
+createdAt: 2024-04-25T00:31:01.895Z
+updatedAt: 2024-07-09T13:39:54.272Z
+publishedAt: 2024-07-09T13:39:54.272Z
+firstPublishedAt: 2024-04-25T01:19:00.025Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: vtex-shield
+locale: pt
+legacySlug: vtex-shield
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+O VTEX Shield oferece camadas adicionais e personalizáveis de proteção para lojas que priorizam a resiliência da plataforma, além dos padrões de segurança garantidos pelas [certificações e práticas de segurança](https://vtex.com/br-pt/security/security-practices/) existentes na VTEX.
+
+A solução apresenta recursos avançados de segurança que possibilitam detectar potenciais riscos e realizar ações preventivas. Assim, é possível se proteger contra interrupções imprevistas, mantendo a sua loja operacional e confiável.
+
+Ao contratar o VTEX Shield, é possível optar pelas funcionalidades a seguir:
+
+* [Security Monitor](#security-monitor)
+* [Testes de penetração](#testes-de-penetracao)
+* [Web Application Firewall (WAF)](#web-application-firewall-waf)
+* [Data Protection Plus](#data-protection-plus)
+
+## Security Monitor
+
+O Security Monitor é um dashboard no Admin VTEX que detecta ameaças à segurança relacionadas ao comportamento de usuários administrativos e a configurações inadequadas. Os riscos potenciais incluem [chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) antigas ou expostas na web, usuários ou credenciais com permissões excessivas e usuários inativos. A ferramenta apresenta uma visão geral das ameaças e das soluções, com a opção de notificar lojistas por email a cada descoberta.
+
+O Security Monitor está disponível no Admin VTEX somente para lojas com VTEX Shield que optarem por esse recurso. Para mais informações, confira o guia [Security Monitor](https://help.vtex.com/pt/tutorial/security-monitor--5LOVNLrrtmgSj99pM1NS4x).
+
+## Testes de penetração
+
+Testes de penetração ou _pentests_ são simulações de ataques a um sistema de computador, rede ou aplicativo da Web com o intuito de avaliar a segurança, possibilitando identificar e corrigir vulnerabilidades.
+
+Somente lojas com VTEX Shield que optarem por esse recurso possuem permissão para realizar testes de penetração, conforme os procedimentos indicados em [Testes de penetração e avisos de vulnerabilidade](https://help.vtex.com/pt/tutorial/testes-de-penetracao-e-aviso-de-vulnerabilidade--6jodF6s1I50Fg84ZwutOCb).
+
+## Web Application Firewall (WAF)
+
+O Web Application Firewall (WAF) é uma ferramenta para proteger aplicações web por meio do monitoramento e da filtragem do tráfego da Internet.
+
+Esse recurso de segurança desempenha um papel fundamental na proteção de sites, serviços on-line e aplicativos da Web contra vários ataques, como injeção de SQL, XSS (cross-site scripting) e outras vulnerabilidades comuns da web.
+
+Somente lojas com VTEX Shield que optarem por esse recurso podem solicitar a ativação do WAF. Saiba mais sobre o funcionamento e os tipos de ameaças protegidas em [Web Application Firewall (WAF)](https://help.vtex.com/pt/tutorial/web-application-firewall-waf--6BZYLlU03ws72iqIFF6jdn).
+
+## Data Protection Plus
+
+<div class="alert alert-info">
+  <p>Esta funcionalidade está em fase beta fechada, disponível apenas para algumas regiões. Em caso de dúvidas, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>.</p>
+</div>
+
+O [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) é uma arquitetura de dados que oferece uma camada adicional de proteção para dados pessoais. Nessa arquitetura, todos os dados PII (Personally Identifiable Information) são armazenados no [Profile System](https://developers.vtex.com/docs/guides/profile-system), um serviço desenvolvido especificamente para processar PII seguindo um [conjunto de regras e processos](https://developers.vtex.com/docs/guides/pii-data-architecture-specifications) apropriados para esse objetivo.
+
+Outros módulos da plataforma, como Pedidos e Checkout, armazenam apenas dados anonimizados associados a um token do Profile System, ampliando a segurança dessas informações.
+
+Leia o conjunto de guias da categoria [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) no Developer Portal para mais detalhes e especificações dessa arquitetura.
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
new file mode 100644
index 000000000..6acd13a19
--- /dev/null
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
@@ -0,0 +1,78 @@
+---
+title: 'VTEX Shipping Network Correios: ativação'
+id: 57opHihFbRAwrjQjCTymTa
+status: PUBLISHED
+createdAt: 2023-08-31T13:25:47.887Z
+updatedAt: 2023-08-31T14:48:48.682Z
+publishedAt: 2023-08-31T14:48:48.682Z
+firstPublishedAt: 2023-08-31T14:36:56.281Z
+contentType: tutorial
+productTeam: Post-purchase
+author: 5l9ZQjiivHzkEVjafL4O6v
+slug: vtex-shipping-network-correios-ativacao
+locale: pt
+legacySlug: vtex-shipping-network-correios-ativacao
+subcategory: 5n5MnINzWTQUX1I2EZl4Ib
+---
+
+<div class="alert alert-info">
+Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network-correios/">VTEX Shipping Network Correios</a>. Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
+</div>
+
+[VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/) é a solução para você integrar sua operação com os serviços PAC e SEDEX dos Correios pelo Admin VTEX e obter de recursos exclusivos. Para lojas VTEX, as tabelas dos Correios ofertadas têm preços especiais, de forma a reduzir os custos logísticos do seu negócio. 
+
+Este artigo é sobre como ativar o **VTEX Shipping Network Correios**. Esta ativação ocorre pelo seu Admin VTEX e não requer investimento inicial, uso mínimo ou pré-requisitos. Para informações sobre [benefícios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC#3-quais-sao-os-beneficios-do-vtex-shipping-network-correios), [modelo de cobrança](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC#5-qual-o-modelo-de-cobranca-do-vtex-shipping-network-correios) e detalhes sobre a solução, veja nosso [FAQ](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC), ou acesse o site [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/).
+
+O vídeo abaixo apresenta todas as etapas da ativação, e na seção seguinte você encontra o passo a passo:
+
+![vsncorreios_ativacao_PT](//images.ctfassets.net/alneenqid6w5/3jkyhn9NypaHZBeXAib7iz/410d76ca2ba8b25cbfce2c0adcb27813/vsncorreios_ativacao.gif)
+
+<div class = "alert alert-info">
+Se você deseja integrar a sua operação com outras transportadoras além dos Correios, temos o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>, com sugestões de parceiros selecionados pela nossa equipe com foco no seu modelo de negócio.
+</div>
+
+## Ativar VTEX Shipping Network Correios
+
+Para realizar a ativação, siga o passo a passo abaixo:
+
+1. No Admin VTEX, acesse **Envio > Estratégia de envio**, ou digite **Estratégia de envio** na barra de busca no topo da página. Em seguida, clique no banner em `Veja a sua oferta`.
+  ![vsncorreios_banner_PT](//images.ctfassets.net/alneenqid6w5/SHhb94U7uQeYTggJBFYxJ/487402ecdbfa87d8777c8071ae49c297/vsncorreios_banner.png)
+  > Se o banner não aparecer na página, acesse a URL `https://{nome-da-loja}.myvtex.com/admin/shipping-strategy/beta/shipping-network-offer/form`, substituindo `{nome-da-loja}` pelo seu [account name](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC).
+2. Na etapa **Sua Operação**, realize os passos abaixo:
+
+  a. Em **Seu custo mensal de frete**, selecione a faixa de preço mais representativa do custo médio mensal de frete da sua operação.
+
+  b. Em **Sua tabela dos Correios**, selecione uma das seguintes opções: <p><ul><li>Não possuo contrato com os Correios</li><li>Bronze</li><li>Prata</li><li>Ouro</li><li>Platinum</li></ul></p>
+
+  <div class="alert alert-warning">
+Caso você já possua um contrato com os Correios, antes de ativar o <b>VTEX Shipping Network Correios</b> você deve desativá-lo nas suas <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">políticas de envio</a> ou removê-lo das <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">docas</a>. Se isso não for feito, a plataforma VTEX pode gerar erros de duplicidade e outros problemas, inclusive erros na emissão de etiquetas no <a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a>.
+</div>
+
+  c. Clique em **Conhecer Oferta**.
+
+  ![vsncorreios_conhecer_oferta_PT](//images.ctfassets.net/alneenqid6w5/oIBsNdSOSJoNQtzT14RGc/1e836be59f73d8171a0e0551ede0be25/vsncorreios_conhecer_oferta.png)
+
+3. Na etapa **Nossa Oferta**, consulte os benefícios da tabela que foi considerada a mais adequada à sua operação.
+  > A imagem abaixo é um exemplo da _Tabela Ouro_:
+
+  ![vsncorreios_nossa_oferta_PT](//images.ctfassets.net/alneenqid6w5/3dW4e20L9fdXo5lVdp1MLy/34dee25d430596a57261894e759b1b27/vsncorreios_nossa_oferta.png)
+
+4. Em seguida, clique em `Tenho interesse` e um modal será aberto contendo os termos e condições da ativação.
+  > Você pode adquirir uma cópia do arquivo em formato PDF clicando em **Download dos termos**.
+
+  ![vsncorreios_termos_condicoes_PT](//images.ctfassets.net/alneenqid6w5/1X6rp478ZIsZlGZCOCPjEq/b518371d3989a37595ce48a9175b05b6/vsncorreios_termos_condicoes.png)
+
+5. Clique em `Aceitar` para concordar com as condições apresentadas e ativar o VTEX Shipping Network Correios.
+6. Na etapa **Um Resumo**, confira as informações finais e garanta que a sua operação tenha uma [agência dos Correios parceira](https://www.correios.com.br/coronavirus/rede-de-atendimento).
+7. Em seguida, selecione uma das seguintes opções:
+    * `Manter políticas de envio inativas`: as novas [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) são mantidas como inativas e só serão consideradas para envios quando forem ativadas.
+    * `Ativar políticas de envio`: as novas políticas de envio são criadas ativas e, em poucos instantes após a confirmação, serão válidas para envio de pedidos.
+    > Você pode a qualquer momento ativar ou desativar as políticas de envio associadas aos Correios, e não existe cobrança quando o serviço não é utilizado. 
+
+    ![vsncorreios_contratou_tabela_PT](//images.ctfassets.net/alneenqid6w5/5qYbCqvYVzttbB3RnsAkCX/cdc81c301c9409f5e9a518f9212c9d15/vsncorreios_contratou_tabela.png)
+
+Feito isso, a ativação do **VTEX Shipping Network Correios** terá sido concluída.
+
+<div class="alert alert-danger">
+Para as novas políticas de envio serem válidas, além de estarem ativadas, é necessário que todas as <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">docas</a> da sua operação tenham o endereço cadastrado. Caso contrário, a plataforma vai apresentar erros. Portanto, certifique-se de configurar o endereço de todas as docas, mesmo aquelas não associadas aos Correios.
+</div>
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-faq.md b/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
index 2fb413af5..79d7908e1 100644
--- a/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network Correios: FAQ'
 id: 2Wavf7Wie5GEUAEHKtn5oC
 status: PUBLISHED
 createdAt: 2023-06-01T13:24:23.895Z
-updatedAt: 2023-06-09T12:55:42.194Z
-publishedAt: 2023-06-09T12:55:42.194Z
+updatedAt: 2023-08-25T15:32:25.418Z
+publishedAt: 2023-08-25T15:32:25.418Z
 firstPublishedAt: 2023-06-01T14:47:24.289Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -16,7 +16,7 @@ subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
 <div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
+Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network-correios/">VTEX Shipping Network Correios</a>. Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
 </div>
 
 Este artigo reúne as dúvidas mais comuns sobre o [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/), a solução da VTEX para você integrar sua operação com os serviços PAC e SEDEX dos Correios pelo Admin VTEX, dispor de recursos exclusivos e aproveitar nossas tarifas competitivas.
diff --git a/docs/tutorials/pt/vtex-shipping-network-dashboard.md b/docs/tutorials/pt/vtex-shipping-network-dashboard.md
index 756ce3077..4beee0b5a 100644
--- a/docs/tutorials/pt/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/pt/vtex-shipping-network-dashboard.md
@@ -3,8 +3,8 @@ title: 'VTEX Shipping Network: Painel'
 id: 51e8tx1IehiN4ZtURRWU92
 status: PUBLISHED
 createdAt: 2020-04-06T20:01:00.909Z
-updatedAt: 2023-06-09T12:56:22.175Z
-publishedAt: 2023-06-09T12:56:22.175Z
+updatedAt: 2024-02-29T19:20:49.152Z
+publishedAt: 2024-02-29T19:20:49.152Z
 firstPublishedAt: 2020-04-16T21:37:18.831Z
 contentType: tutorial
 productTeam: Post-purchase
@@ -15,8 +15,12 @@ legacySlug: painel-vtex-log
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
+<div class="alert alert-info">
+Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>.
+</div>
+
 <div class="alert alert-warning">
-<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX dos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a></li><li><a href="https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq">Entregas Correios</a></li><li>Painel VTEX Shipping Network</li></ul></p>
+<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a></li><li><a href="https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq">Entregas Correios</a></li><li>Painel VTEX Shipping Network</li></ul></p>
 </div>
 
 O [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) utiliza os dados de rastreio dos pedidos diretamente das transportadoras, mantendo você e seu cliente atualizados sobre o status de cada entrega.
@@ -51,8 +55,8 @@ A aba `Resumo Financeiro` é voltada para o acompanhamento e supervisão do resu
 | **Receita Faturada VTEX Shipping Network** | Soma de todos os fretes pagos no checkout. Quanto de fato seu cliente pagou pelo frete, filtrando apenas por transportadoras VTEX Shipping Network. Ou seja, é considerado se teve desconto no frete ou se foi frete grátis por exemplo. |
 | **Custo Projetado Geral** | Independente do VTEX Shipping Network ou não, é a soma dos valores de frete estimados pelo módulo de Estoque e Entrega para todos os pedidos. Acompanha setas que indicam a porcentagem de crescimento ou decrescimento de custos. A diminuição de custos nesse  (seta para baixo) card é uma medida positiva para os resultados de uma loja. |
 | **Custo Projetado VTEX Shipping Network** | Soma dos valores de frete estimados pelo módulo Eenvio para todos os pedidos, filtrando apenas transportadoras _VTEX Shipping Network_. Acompanha setas que indicam a porcentagem de crescimento ou decrescimento de custos.  A diminuição de custos nesse (seta para baixo) card é uma medida positiva para os resultados de uma loja. |
-| **Custo Emitido via CTE** | Custo que veio do CONEMB para todos esses pedidos. A VTEX recebe essa informação através do envio dos arquivos CONEMB, que as transportadoras nos enviam. Esse arquivo demonstra quanto a transportadora gastou em detalhe, e o número da nota fiscal do pedido. Acompanha setas que indicam a porcentagem de crescimento ou decrescimento de custos. A diminuição de custos nesse (seta para baixo) card é uma medida positiva para os resultados de uma loja. |
-| **Diferença de Custo apontada** | Diferença entre o custo projetado e do custo emitido via CTE. CTE é o arquivo recebido das transportadoras _VTEX Shipping Network_, que demonstra quanto a transportadora gastou em detalhe, e o número da nota fiscal do pedido. Acompanha setas que indicam a porcentagem de crescimento ou decrescimento de custos. O aumento entre a diferença de custos nesse card é uma medida positiva para os resultados de uma loja. |
+
+* Estamos melhorando o **Custo Emitido via CTE** e a **Diferença de Custo apontada**, e eles estão temporariamente indisponíveis.
 
 ## Aba Performance
 
@@ -62,7 +66,7 @@ No cálculo da performance, são considerados todos os pacotes que fazem parte d
 
 A performance é o resultado em percentual do cálculo entre a relação dos pacotes entregues dentro do  prazo pelo total de pacotes entregues. Assim, o cálculo da performance só leva em consideração os pacotes que foram entregues. Veja:
 
-![equation PT performance](https://images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/5f190d7ed6439920a22dfbb5d86fe127/CodeCogsEqn.gif)
+![equation PT performance](//images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/5f190d7ed6439920a22dfbb5d86fe127/CodeCogsEqn.gif)
 
  A ferramenta de Performance do **VTEX Shipping Network** permite:
 
@@ -92,9 +96,9 @@ Todas as transportadoras **VTEX Shipping Network** possuem selo de verificação
 É importante saber que, no caso em que a transportadora não teve a performance calculada na plataforma, os dados de rastreamento não foram integrados ao <b>VTEX Shipping Network</b>.
 </div>
 
-Para que o cálculo da performance seja feito em transportadoras que não são **VTEX Shipping Network**, os dados devem ser enviados pelo seller por uma API de tracking disponibilizada pela solução **VTEX Shipping Network**. 
+Para que o cálculo da performance seja feito em transportadoras que não são **VTEX Shipping Network**, os dados devem ser enviados pelo seller por uma API de tracking disponibilizada pela solução **VTEX Shipping Network**. Nestes casos, vale ressaltar que os dados do painel podem ser imprecisos, pois não há validação da entrega ser realizada no prazo indicado. 
 
-Para saber mais como realizar essa integração confira o [Overview VTEX Shipping Network](https://developers.vtex.com/vtex-rest-api/reference/vtex-log-api-overview) das nossas APIs.
+Para saber mais como realizar essa integração, confira o [Overview VTEX Shipping Network](https://developers.vtex.com/docs/api-reference/vtex-shipping-network-api) das nossas APIs.
 
 ### Exportar relatório
 
diff --git a/docs/tutorials/pt/vtex-status-page.md b/docs/tutorials/pt/vtex-status-page.md
new file mode 100644
index 000000000..d5a58bd46
--- /dev/null
+++ b/docs/tutorials/pt/vtex-status-page.md
@@ -0,0 +1,169 @@
+---
+title: 'Página de status da VTEX'
+id: gPhqDn9IQ3c67wbJEX3JJ
+status: PUBLISHED
+createdAt: 2019-01-14T19:58:58.431Z
+updatedAt: 2023-12-21T17:10:08.895Z
+publishedAt: 2023-12-21T17:10:08.895Z
+firstPublishedAt: 2019-01-14T20:01:43.663Z
+contentType: tutorial
+productTeam: Reliability
+author: 1malnhMX0vPThsaJaZMYm2
+slug: pagina-de-status-da-vtex
+locale: pt
+legacySlug: status-vtex-entenda-como-funciona-o-status-da-plataforma, pagina-de-status-da-plataforma
+subcategory: 5PYkoNDZyo2G80yiiqG2YW
+---
+
+Na página [Status VTEX](https://status.vtex.com/), você pode acompanhar a estabilidade da plataforma em tempo real, assim como acessar todo o histórico de incidentes.
+
+Os eventos são reportados pela nossa equipe sempre que nosso sistema automático de monitoramento identifica uma instabilidade nos módulos da plataforma. As manutenções programadas também são comunicadas em detalhes.
+
+![statuspage-1](//images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/8fc52cd3637d63edbd9963962460e6dc/statuspage-1.png)
+
+Abaixo, você encontra detalhes sobre os elementos da página de status da plataforma VTEX, desenvolvida com a ferramenta [incident.io](https://incident.io/):
+
+* [Reportar um problema](#reportar-um-problema)
+* [Notificações](#notificacoes)
+* [Status geral](#status-geral)
+* [Status dos sistemas](#status-dos-sistemas)
+* [Calendário](#calendario)
+* [Registro de incidente](#registro-de-incidente)
+* [Registro de manutenção agendada](#registro-de-manutencao-agendada)
+
+## Reportar um problema
+
+Ao clicar no botão `Report a problem` no canto superior direito da página você pode entrar em contato com o [nosso Suporte](https://support.vtex.com/hc/pt-br/requests) para nos informar sobre instabilidades na plataforma.
+
+## Notificações
+
+A página de status apresenta o botão `Subscribe to updates `no canto superior direito da página. Ao clicar, você tem a opção de se inscrever para receber atualizações via email, [feed RSS](https://rss.com/blog/how-do-rss-feeds-work/), ou [Slack](https://slack.com/).
+
+Ao escolher a inscrição por email, você pode optar por receber notificações apenas para impactos em componentes específicos. Para isso, marque a opção **Subscribe to specific components** e, em seguida, marque os componentes a acompanhar.
+
+![statuspage-2](//images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/a5d988626d923d454ef74bb60d7104c4/statuspage-2.png)
+
+## Status geral
+
+Nesta seção, você pode visualizar o status geral da plataforma, que pode ser _fully operational _(totalmente operacional), _experiencing issues_ (enfrentando problemas) ou _undergoing maintenance_ (em manutenção).
+
+Quando problemas ou manutenção estão afetando algum sistema, o componente impactado é apresentado, assim como uma explicação da ocorrência. Veja exemplos a seguir.
+
+![statuspage-3](//images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/f464e8250a0b198b4b0d5fd6daafd514/statuspage-3.png)
+
+![statuspage-4](//images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/723008187b05b2c81eba0af564b7514d/statuspage-4.png)
+
+![statuspage-5](//images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/5d64281bddf023076fa17e84671a6cc9/statuspage-5.png)
+
+## Status dos sistemas
+
+Nesta seção, é possível verificar, em tempo real, o status de cada sistema da plataforma e de seus componentes.
+
+![statuspage-6](//images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/decc90536636cd0a50086535cb9f3450/statuspage-6.png)
+
+Ao clicar na seta <i class="fas fa-chevron-down"></i> ao lado do número de componentes, você pode visualizar o status de componentes específicos de cada sistema.
+
+Se houver uma manutenção agendada para uma data futura, você verá também o botão `Upcoming maintenance scheduled`, ilustrado a seguir. Ao passar o mouse sobre ele, aparece o evento de manutenção agendada, no qual é possível clicar para visualizar o registro dessa ocorrência.
+
+![statuspage-7](//images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/9e861753a2f77e368d0f32f262d98f26/statuspage-7.png)
+
+Os estados possíveis para cada componente são:
+
+* **Operational:** funcionamento estável.
+* **Degraded performance:** funcionamento com performance abaixo do esperado.
+* **Partial outage:** funcionamento parcial das funcionalidades.
+* **Full outage:** funcionamento totalmente impactado.
+* **Under maintenance:** sistema em manutenção.
+
+A seguir, detalhamos os componentes exibidos na página.
+
+### Storefront
+
+Problemas na navegação na frente de loja.
+
+* **Portal/CMS:** instabilidades observadas em lojas desenvolvidas com a tecnologia de storefront [Portal CMS Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
+* **Store Framework:** instabilidades observadas em lojas desenvolvidas com a tecnologia de storefront [Store Framework](https://developers.vtex.com/docs/guides/vtex-io-documentation-what-is-vtex-store-framework).
+* **FastStore:** instabilidades observadas em lojas desenvolvidas com a tecnologia de storefront [FastStore](https://www.faststore.dev/).
+* **Sales App:** instabilidades observadas no [Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc), a solução da VTEX para vendas assistidas em lojas físicas.
+* **3rd Party Apps**: instabilidades observadas em extensões mantidas por terceiros.
+
+### Checkout
+
+Problemas em funcionalidades relacionadas ao fluxo de criação de pedidos, ou seja, checkout e suas dependências.
+
+ * **Order Placement:** interrupções no fluxo de vendas.
+ * **Shipping Calculation:** inconsistências em condições de frete.
+ * **Pricing Calculation:** inconsistências em preços, promoções ou taxas.
+ * **Payments Gateway:** inconsistências em transações de pagamento.
+ * **Payment Connectors:** instabilidades observadas em conectores de pagamentos específicos.
+
+### Admin
+
+Problemas relacionados à navegação no Admin VTEX e seus módulos, como gerenciamento de pedidos, configurações de preços e logística, por exemplo.
+
+* **Catalog Management:** interrupções na atualização do conteúdo do catálogo (detalhes do produto, imagens, preços, inventário, indexação da busca, etc.).
+* **Content Management:** interrupções na atualização de conteúdo não relacionado a produtos (banners, landing pages, promoções, cupons, cartões-presente, etc.).
+* **Order Management:** interrupções no fulfillment de pedidos.
+* **Marketplace Connectors:** instabilidades observadas em conectores de marketplaces específicos.
+* **Admin Operations** outros impactos na experiência dos lojistas, fora do escopo de outros componentes do Admin.
+
+### Developer Tools
+
+Problemas relacionados a desenvolvimento de apps, integrações e temas de lojas.
+
+* **VTEX IO:** instabilidades observadas em apps desenvolvidos em VTEX IO.
+* **Master Data:** instabilidades observadas em integrações que dependem do Master Data.
+* **API Integrations:** outros impactos no uso das APIs da VTEX.
+
+## Calendário 
+
+A seção do calendário exibe o registro de incidentes e manutenções programadas ocorridos a cada dia do mês atual.
+
+Para navegar para meses anteriores, clique na seta `&lt;`.
+
+Para visualizar as ocorrências de um dia específico, passe o mouse sobre a data. Para acessar a página com o registro completo da ocorrência, clique no incidente ou na manutenção listada.
+
+![statuspage-8](//images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/36a4d394c1fb447958eec18ceaa849d3/statuspage-8.png)
+
+<div class="alert alert-warning">
+  <p>Se a manutenção agendada durar um período maior que um dia, somente a data de início estará marcada no calendário. É necessário abrir o <a href="#registro-de-manutencao-agendada">registro da manutenção</a> para ver a data de início e a data de fim.</p>
+</div>
+
+A seguir, detalhamos as informações disponíveis no [registro de incidente](#registro-de-incidente) e no [registro de manutenção agendada](#registro-de-manutencao-agendada).
+
+## Registro de incidente
+
+A página de detalhes do incidente contém as seguintes informações:
+
+![statuspage-9](//images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/af16c15476205d3a3529d4a434bfdd8d/statuspage-9.png)
+
+* **Título:** título que descreve o incidente.
+* **Status:** cada incidente possui um ciclo definido, em que nossa equipe trabalha para identificar e solucionar os problemas. Conheça um pouco mais sobre cada etapa desse ciclo:
+    * **Investigating:** o primeiro estado do incidente é dedicado à análise dos impactos, serviços relacionados e identificação da causa raiz.
+    * **Identified:** com a origem do erro devidamente identificada, a equipe de desenvolvimento começa a executar ações para a solução do comportamento.
+    * **Monitoring:** depois de concluir as ações de estabilização do sistema, já com os indicadores da operação normalizados, seguimos em estado alerta com um monitoramento mais próximo da performance no serviço ou módulo impactado.
+    * **Resolved:** com a performance da plataforma estabilizada, voltamos ao nosso monitoramento normal e consideramos que a plataforma está funcionando como esperado.
+* **Duração:** tempo até a resolução do incidente.
+* **Resumo:** texto que resume o incidente.
+* **Componentes afetados:** componentes da plataforma que foram impactados pelo incidente. Ao clicar na set a ao lado do número de componentes, você pode visualizar o impacto em componentes mais específicos.
+* **Atualizações**: linha do tempo com as atualizações e mudanças de status do incidente.
+
+Ao clicar no botão `Subscribe to updates` no registro de um incidente, você tem a opção de se inscrever para receber atualizações sobre aquele incidente específico via email, feed RSS, ou Slack.
+
+## Registro de manutenção agendada
+
+As atualizações na plataforma são feitas continuamente e, no geral, não impactam a operação dos nossos clientes. Mas, às vezes, algumas delas precisam que o serviço fique temporariamente indisponível.
+
+Para casos que afetam a estabilidade da plataforma, usamos a página de status da VTEX para comunicar todos os detalhes: quando será executada a manutenção, o período de duração e o impacto.
+
+O registro de manutenção agendada apresenta as mesmas informações dos registros de incidentes. Os status possíveis da manutenção agendada são:
+
+* **Scheduled:** evento de manutenção programado.
+* **In progress:** evento de manutenção em progresso.
+* **Complete:** evento de manutenção finalizado.
+
+Veja a seguir exemplos do status e da linha do tempo de uma manutenção agendada.
+
+![statuspage-10](//images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/a2d673b455bd2ecc8f76745515609e5c/statuspage-10.png)
+
+![statuspage-11](//images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/d54ae87af5467cc94d9978cf5bca6e93/statuspage-11.png)
diff --git a/docs/tutorials/pt/vtex-suiteshare.md b/docs/tutorials/pt/vtex-suiteshare.md
index 1c8b67d89..729ab1278 100644
--- a/docs/tutorials/pt/vtex-suiteshare.md
+++ b/docs/tutorials/pt/vtex-suiteshare.md
@@ -19,28 +19,28 @@ Para instalar o script do **VTEX Assisted Sales (SuiteShare)** no seu site, bas
 
 Primeiro, acesse o painel administrativo da VTEX e, no menu à esquerda, siga para: **_CMS -> Layout -> CMS -> Custom Elements._**
 
-![VTEX 1](https://images.ctfassets.net/alneenqid6w5/c6LgDxrCW3RPrrYoLcjlH/6e006379d1252dd7b128c914ae4660c8/Screenshot_2022-08-31_at_12-22-28_VTEX.png)
+![VTEX 1](//images.ctfassets.net/alneenqid6w5/c6LgDxrCW3RPrrYoLcjlH/6e006379d1252dd7b128c914ae4660c8/Screenshot_2022-08-31_at_12-22-28_VTEX.png)
 
 Desça até encontrar a opção “Menu Footer - Primeiro”, ou somente “Menu Footer” caso não exista a divisão, clique em cima da linha para selecioná-la e depois clique em “Update”.
 
-![VTEX 2](https://images.ctfassets.net/alneenqid6w5/f4sFPkaytHRI850pKkrQY/de55c692384c29a1b1a2bf1522b40b48/Screenshot_2022-08-31_at_12-22-35_VTEX.png)
+![VTEX 2](//images.ctfassets.net/alneenqid6w5/f4sFPkaytHRI850pKkrQY/de55c692384c29a1b1a2bf1522b40b48/Screenshot_2022-08-31_at_12-22-35_VTEX.png)
 
 Na tela a seguir, clique no ícone de lápis como mostrado abaixo para editar o rodapé do site.
 
-![VTEX 3](https://images.ctfassets.net/alneenqid6w5/4kLaAycDHWE8o8qVg4C3Xd/7a9dd8b0233fdab27a1f0b72e6193ad4/Screenshot_2022-08-31_at_12-22-41_VTEX.png)
+![VTEX 3](//images.ctfassets.net/alneenqid6w5/4kLaAycDHWE8o8qVg4C3Xd/7a9dd8b0233fdab27a1f0b72e6193ad4/Screenshot_2022-08-31_at_12-22-41_VTEX.png)
 
 Role até o final do código que verá na tela, dê um Enter para pular uma linha e cole o código de instalação do **VTEX Assisted Sales (SuiteShare)**.
 
 O código de instalação do **VTEX Assisted Sales (SuiteShare)** está disponível em diversos locais, um deles é no menu _configurações> perfil>rastreamento_, ou caso você já tenha configurado o chat, em _atrair> chat> instruções de instalação_.
 
-![VTEX 4](https://images.ctfassets.net/alneenqid6w5/1AgyPu8q1IZpCpdF4EkSRU/5f91387bdf97e016da3c1699a0a729ea/Screenshot_2022-08-31_at_12-22-47_VTEX.png)
+![VTEX 4](//images.ctfassets.net/alneenqid6w5/1AgyPu8q1IZpCpdF4EkSRU/5f91387bdf97e016da3c1699a0a729ea/Screenshot_2022-08-31_at_12-22-47_VTEX.png)
 
 Após colar o código, clique em “Update content list”.
 
-![VTEX 5](https://images.ctfassets.net/alneenqid6w5/6lifcFGPbg4Jvc1Tpx2Vii/2d86aadbb2bf066b8c1b16a9d1c6dc6e/Screenshot_2022-08-31_at_12-22-53_VTEX.png)
+![VTEX 5](//images.ctfassets.net/alneenqid6w5/6lifcFGPbg4Jvc1Tpx2Vii/2d86aadbb2bf066b8c1b16a9d1c6dc6e/Screenshot_2022-08-31_at_12-22-53_VTEX.png)
 
 Depois, clique em “Save Content” para finalizar a instalação.
 
-![VTEX 6](https://images.ctfassets.net/alneenqid6w5/7CN7v2TnOQwqflotqdK53o/673ccbe75774f9f54b4948ade030fc04/Screenshot_2022-08-31_at_12-23-01_VTEX.png)
+![VTEX 6](//images.ctfassets.net/alneenqid6w5/7CN7v2TnOQwqflotqdK53o/673ccbe75774f9f54b4948ade030fc04/Screenshot_2022-08-31_at_12-23-01_VTEX.png)
 
 Pronto, o Chat/Widget ou CTA está instalado no seu site. Agora é aproveitar as funcionalidades!
diff --git a/docs/tutorials/pt/vtex-support-apac.md b/docs/tutorials/pt/vtex-support-apac.md
new file mode 100644
index 000000000..5a708aeb9
--- /dev/null
+++ b/docs/tutorials/pt/vtex-support-apac.md
@@ -0,0 +1,18 @@
+---
+title: 'Suporte VTEX - APAC'
+id: 4tHKlUwXgjW8ebnCxd6COc
+status: PUBLISHED
+createdAt: 2024-04-29T23:32:23.667Z
+updatedAt: 2024-04-30T11:02:29.768Z
+publishedAt: 2024-04-30T11:02:29.768Z
+firstPublishedAt: 2024-04-29T23:36:32.127Z
+contentType: tutorial
+productTeam: Billing
+author: 5l3eEiSz8MpcppCxcnijGz
+slug: suporte-vtex-apac
+locale: pt
+legacySlug: suporte-vtex-apac
+subcategory: 
+---
+
+Este conteúdo está disponível apenas em inglês. [Clique aqui](https://help.vtex.com/pt/faq/vtex-support-brazil--5q861sTw1n7H2BENOu7ls9?&utm_source=autocompletE) para acessar.
diff --git a/docs/tutorials/pt/vtex-tracking-agencies.md b/docs/tutorials/pt/vtex-tracking-agencies.md
index 4fe8f425b..1406f0f66 100644
--- a/docs/tutorials/pt/vtex-tracking-agencies.md
+++ b/docs/tutorials/pt/vtex-tracking-agencies.md
@@ -76,13 +76,13 @@ Para cada status de entrega, é enviado um e-mail e um SMS para o consumidor com
 *O corpo do email deve ser preenchido em HTML, CSS e Javascript. Já a mensagem SMS pode ser preenchida em texto normal, substituindo os valores variáveis pelas `{{tags}}`, que explicaremos a seguir.*   
  7. Clique em **Salvar**.  
 
-![PT Tracking Agencia Configurar email](https://images.ctfassets.net/alneenqid6w5/3piB2Vv9Lwkk7dIg0pvZnx/577774614e73f3d37f420ed92a681f89/PT_Tracking_Agencia_Configurar_email.png)
+![PT Tracking Agencia Configurar email](//images.ctfassets.net/alneenqid6w5/3piB2Vv9Lwkk7dIg0pvZnx/577774614e73f3d37f420ed92a681f89/PT_Tracking_Agencia_Configurar_email.png)
 
 #### Status 
 
 A imagem abaixo representa o fluxo de disparo de emails e SMS para destinatários presentes em uma rota. 
 
-![PT Tracking Agencia status disparo](https://images.ctfassets.net/alneenqid6w5/7qxjQpPt56Xs6HgsMP9vs9/c4ea6b54e215dcfc881b6c989c88ebc8/PT_Tracking_Agencia_status_disparo.png)
+![PT Tracking Agencia status disparo](//images.ctfassets.net/alneenqid6w5/7qxjQpPt56Xs6HgsMP9vs9/c4ea6b54e215dcfc881b6c989c88ebc8/PT_Tracking_Agencia_status_disparo.png)
 
 - **Rota itinerante:** rota itinerante é aquela que demora mais de um dia para ser concluída. A comunicação é enviada quando o portador inicia a primeira entrega da rota. No email ou SMS a mensagem avisa que o serviço está em rota, e determina que a entrega será feita até o dia cadastrado como a data de fim da rota. 
 - **Rota Iniciada:** enviado quando o portador inicia a primeira entrega da rota. Todos os pedidos dentro daquela rota recebem uma previsão estimada, que será atualizada quando a comunicação de Entrega Iniciada for enviado.    
diff --git a/docs/tutorials/pt/warehouse.md b/docs/tutorials/pt/warehouse.md
index 9c687982a..b1577003c 100644
--- a/docs/tutorials/pt/warehouse.md
+++ b/docs/tutorials/pt/warehouse.md
@@ -19,7 +19,7 @@ Para a plataforma VTEX o estoque é a identificação do espaço físico de arma
 
 É importante atentar-se à etapa logística do estoque e como as configurações na plataforma VTEX influenciam na entrega de pedidos. A partir do estoque os pedidos saem para as docas, e nas docas são retirados pelas transportadoras. 
 
-![EstrategiaEnvio](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/02cad4cbd4829e774e2b51474e4675cf/Frame_2__1_.svg)
+![EstrategiaEnvio](//images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/02cad4cbd4829e774e2b51474e4675cf/Frame_2__1_.svg)
 
 <div class="alert alert-info">
 A transportadora que realizará a entrega de um certo pedido é definida pela <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">política de envio</a>. Para que uma transportadora seja escolhida para a realização da entrega do pedido, é preciso que a política de envio dessa transportadora satisfaça as condições necessárias para a entrega do pedido. A política de envio é vinculada ao estoque pela Doca.
diff --git a/docs/tutorials/pt/web-application-firewall-waf.md b/docs/tutorials/pt/web-application-firewall-waf.md
new file mode 100644
index 000000000..9476ba33e
--- /dev/null
+++ b/docs/tutorials/pt/web-application-firewall-waf.md
@@ -0,0 +1,58 @@
+---
+title: 'Web Application Firewall (WAF)'
+id: 6BZYLlU03ws72iqIFF6jdn
+status: PUBLISHED
+createdAt: 2024-04-25T00:17:16.172Z
+updatedAt: 2024-04-30T15:03:41.186Z
+publishedAt: 2024-04-30T15:03:41.186Z
+firstPublishedAt: 2024-04-25T01:16:27.468Z
+contentType: tutorial
+productTeam: Others
+author: 1malnhMX0vPThsaJaZMYm2
+slug: web-application-firewall-waf
+locale: pt
+legacySlug: web-application-firewall-waf
+subcategory: jrgbOxKaOW0kdZs7rdgvS
+---
+
+<div class="alert alert-info">
+  <p>Esta funcionalidade faz parte do produto <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
+</div>
+
+O Web Application Firewall (WAF) é uma camada de segurança projetada para proteger aplicações web por meio do monitoramento e da filtragem do tráfego da Internet.
+
+O WAF é direcionado especificamente para comunicações que ocorrem pelos protocolos HTTP (Hypertext Transfer Protocol) e HTTPS (HTTP Secure), examinando os dados de entrada e saída para detectar e bloquear possíveis ameaças.
+
+![waf-pt](//images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/9eb9944bfed9b23421e053f2c6102825/waf-pt.png)
+
+A operação do WAF começa com a definição de [regras de segurança](#regras-de-seguranca), que são definidas pelo time de Segurança da VTEX a partir da análise de padrões de circulação de informações. A partir dessas regras, o WAF monitora continuamente o tráfego da web. Quando detecta uma atividade potencialmente prejudicial, ele pode bloquear o tráfego, evitando assim a exploração de vulnerabilidades no aplicativo web.
+
+## Regras de segurança
+
+Lojas que utilizam o VTEX Shield e optarem pelo WAF contam com as regras de segurança a seguir contra ameaças no site:
+
+| Ameaça | Medida de segurança |
+|---|---|
+| Remote File Inclusions (RFI) | Detecta tentativas de incluir arquivos, geralmente por meio de scripts no servidor da web. |
+| Directory Traversal | Verifica e valida nomes de arquivos fornecidos pelos usuários, evitando acesso não autorizado a arquivos e pastas sensíveis. |
+| Cross-Site Scripting (XSS) | Impede a injeção de scripts do lado do cliente nas páginas visualizadas por seus visitantes. |
+| Upload de arquivos | Detecta tentativas de upload de arquivos para o servidor da web. |
+| Truques de evasão | Protege contra alguns truques de codificação usados para tentar burlar os mecanismos de proteção. |
+| Acesso indesejado | Detecta tentativas de acesso a páginas administrativas ou vulneráveis, bots e ferramentas de varredura de segurança. |
+| Ataques identificados | Previne vários tipos de ataques comuns e vulnerabilidades conhecidas que devem ser bloqueadas. |
+| Filtro de IP | Consulta uma lista de endereços IPs que possuem permissões ou bloqueios de acesso. |
+| Bloqueio da rede Tor | Impede o acesso ao site utilizando o navegador Tor. |
+
+## Solicitar ativação do WAF
+
+Para solicitar a ativação do WAF na sua loja, entre em contato com o [Suporte VTEX](https://help.vtex.com/pt/support). Inclua as informações a seguir no ticket:
+
+* URLs a serem adicionadas ao WAF.
+* Nome e informações de contato da pessoa que será o ponto de contato com a equipe de Segurança da VTEX durante o processo de ativação.
+* Provedor: para ter acesso ao WAF, todo o tráfego de URLs da loja deve passar pela [Azion](https://www.azion.com/), o provedor atualmente utilizado pela VTEX. Se isso não ocorrer, é preciso seguir um procedimento com a equipe de Tráfego da VTEX, que pode durar entre 1 e 2 semanas.
+
+Após a solicitação, o prazo para a ativação do WAF nas URLs da loja é de 4 semanas, além do período necessário para migrar para a [Azion](https://www.azion.com/), quando aplicável.
+
+## Saiba mais
+
+* [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh)
diff --git a/docs/tutorials/pt/web-page-performance.md b/docs/tutorials/pt/web-page-performance.md
index 584f968d2..995b68e26 100644
--- a/docs/tutorials/pt/web-page-performance.md
+++ b/docs/tutorials/pt/web-page-performance.md
@@ -25,7 +25,7 @@ A tela “Performance das páginas web” disponibiliza a ferramenta [PageSpeed
 
 Embora o dashboard “Performance das páginas web” ofereça as mesmas funcionalidades da ferramenta PageSpeed Insights do Google, somente no Admin VTEX os comerciantes conseguem adicionar várias URLs e monitorá-las continuamente. 
 
-![Web page performance Dash PT](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
+![Web page performance Dash PT](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
 
 ## Por que você deve ficar de olho no desempenho de uma página web?
 
@@ -109,7 +109,7 @@ Observação: não é possível excluir as 10 páginas mais acessadas do seu eco
 
 ## Principais métricas da web
 
-![Core web vitals PT](https://images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/a7221d5dc9e5197b55069697fbd3f758/Screen_Shot_2022-06-29_at_15.48.06.png)
+![Core web vitals PT](//images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/a7221d5dc9e5197b55069697fbd3f758/Screen_Shot_2022-06-29_at_15.48.06.png)
 
 Para cada URL, o dashboard Performance das páginas web exibe as [Principais métricas da web do Google](https://web.dev/vitals/#core-web-vitals) referentes à página em questão. 
 
diff --git a/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md b/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
index 7d97a3754..58b4736e4 100644
--- a/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
+++ b/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
@@ -19,7 +19,7 @@ Ao acessar a seção __Todos os pedidos__, em __Gerenciamento de pedidos__, é p
 
 A coluna __Origem__ indica de onde partiu o pedido, diferenciando o mesmo em duas possíveis origens: __Marketplace__ e __Fulfillment__.
 
-![orders-list-origin-pt](https://images.ctfassets.net/alneenqid6w5/38XgFUqPIlB8T8FDRLsSXc/8db60848bd28cee74c5177d425130d1c/oders-list-origin-pt.png)
+![orders-list-origin-pt](//images.ctfassets.net/alneenqid6w5/38XgFUqPIlB8T8FDRLsSXc/8db60848bd28cee74c5177d425130d1c/oders-list-origin-pt.png)
 
 ## Marketplace
 
diff --git a/docs/tutorials/pt/what-are-templates.md b/docs/tutorials/pt/what-are-templates.md
index d56bee40c..1917ea50f 100644
--- a/docs/tutorials/pt/what-are-templates.md
+++ b/docs/tutorials/pt/what-are-templates.md
@@ -32,7 +32,7 @@ Além desses dois tipos básicos, há ainda uma subdivisão dos __templates de p
 
 E falando em organização, você encontra todos os templates no módulo **Storefront > Layout > CMS**, reunidos em pastas de acordo com seu tipo (HTML ou Shelves). Os __Sub Templates__ estão na pasta de mesmo nome, que fica dentro do diretório __HTML Templates__. Nesses locais, você vai poder criar novos templates e editar os que já existem.
 
-![cms](https://images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
+![cms](//images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
 
 ### Artigos relacionados
 - [O que é o CMS?](/pt/tutorial/o-que-e-o-cms)
diff --git a/docs/tutorials/pt/what-customized-payments-are-available-in-latin-america.md b/docs/tutorials/pt/what-customized-payments-are-available-in-latin-america.md
index c5086344d..f90b4cb9d 100644
--- a/docs/tutorials/pt/what-customized-payments-are-available-in-latin-america.md
+++ b/docs/tutorials/pt/what-customized-payments-are-available-in-latin-america.md
@@ -1,10 +1,10 @@
 ---
 title: 'Que pagamentos customizados estão disponíveis na América Latina?'
 id: 6plXudxQJiwaE0key20Yoe
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.217Z
-updatedAt: 2019-12-31T15:29:09.442Z
-publishedAt: 2019-12-31T15:29:09.442Z
+updatedAt: 2024-03-19T12:09:37.330Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T21:58:52.021Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md b/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
index 302387155..557aac590 100644
--- a/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
+++ b/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
@@ -24,4 +24,4 @@ Ao configurar uma promoção **Compre e Ganhe**, é possível **Ativar multiplic
 Para ambos cenários, é necessário preencher a quantidade máxima de selecionável. Com o multiplicador de brindes **ativado**, determine a **quantidade máxima** de brindes para a condição. Para o multiplicador de brindes **desativado**, a quantidade é **sempre 1**. 
 
 
-![ativar-multiplicador-brinde pt ](https://images.ctfassets.net/alneenqid6w5/X9IFg93pUiQQSeMocSqwS/b60bfe34e64450bcd25d97294dd2d66c/gift_multi_pt.png)
+![ativar-multiplicador-brinde pt ](//images.ctfassets.net/alneenqid6w5/X9IFg93pUiQQSeMocSqwS/b60bfe34e64450bcd25d97294dd2d66c/gift_multi_pt.png)
diff --git a/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md b/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
index 626df3202..75ca3ff3b 100644
--- a/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
+++ b/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
@@ -31,7 +31,7 @@ Para descobrir como acessar os pedidos que foram considerados na apuração da r
 
 Buscando facilitar sua visualização, todos os pedidos financeiramente aprovados terão essa marcação, que poderá ser vista no módulo gerenciamento de pedidos. 
 
-![image (3)](https://images.ctfassets.net/alneenqid6w5/2hl6jNViPdxOaOqF9ZCrt7/ac5af18b2a91c8d3da149eff421991ea/image__3_.png)
+![image (3)](//images.ctfassets.net/alneenqid6w5/2hl6jNViPdxOaOqF9ZCrt7/ac5af18b2a91c8d3da149eff421991ea/image__3_.png)
 
 Para acessar o módulo, siga os procedimentos abaixo:
 
diff --git a/docs/tutorials/pt/what-is-a-franchise-account.md b/docs/tutorials/pt/what-is-a-franchise-account.md
index 4e90a73fb..6382ac0fd 100644
--- a/docs/tutorials/pt/what-is-a-franchise-account.md
+++ b/docs/tutorials/pt/what-is-a-franchise-account.md
@@ -3,8 +3,8 @@ title: 'O que é conta franquia?'
 id: kWQC6RkFSCUFGgY5gSjdl
 status: PUBLISHED
 createdAt: 2021-10-13T20:38:07.014Z
-updatedAt: 2023-05-31T15:20:29.177Z
-publishedAt: 2023-05-31T15:20:29.177Z
+updatedAt: 2024-05-24T16:38:26.710Z
+publishedAt: 2024-05-24T16:38:26.710Z
 firstPublishedAt: 2021-10-13T20:57:01.457Z
 contentType: tutorial
 productTeam: Shopping
@@ -73,6 +73,11 @@ Para que a conta franquia utilize os preços configurados na conta principal, é
 
 Para configurar preços próprios da conta franquia, você precisa desmarcar a opção **Herdar preços da conta-pai** nas Configurações do módulo de **Preços** da conta franquia, conforme detalhado [neste artigo](https://help.vtex.com/pt/tutorial/price-configuration--3hbBtCzNUBrj8GaWgCtSWN#configuracoes-gerais-de-precos). Além disso, é necessário configurar os preços desejados no [módulo de **Preços**](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) ou pela [API de Pricing](https://developers.vtex.com/vtex-rest-api/reference/pricing-api-overview).
 
+Para garantir uma experiência de compra consistente, é importante [configurar a regionalização](https://help.vtex.com/pt/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw?&utm_source=autocomplete) quando existirem preços diferentes para cada conta franquia.
+Ao adotar a regionalização, é possível solicitar o CEP do cliente antes de iniciar a navegação, permitindo assim exibir os produtos e  preços correspondentes à conta franquia antes de prosseguir para o Checkout.
+Caso a regionalização não esteja em vigor, é possível que o consumidor visualize um determinado valor de produto ao navegar pela loja, mas ao chegar ao Checkout e inserir o CEP, pode-se constatar que a conta franquia responsável pelo atendimento do pedido é outra, resultando em um preço diferente.
+Essa situação ocorre porque, durante a navegação  na loja, o catálogo de menor preço é priorizado. No entanto, ao chegar ao Checkout, caso a conta franquia com o menor preço não tenha estoque disponível, será selecionado o catálogo de outro vendedor que possua o produto em estoque, resultando em uma atualização do preço para o valor praticado por esse vendedor.
+
 ### Pagamentos
 
 #### Utilizar meios de pagamento da conta principal
@@ -92,7 +97,7 @@ Uma vez que você tenha [alterado essa configuração](#configurar-meios-de-paga
 A VTEX oferece soluções de split de pagamentos que podem tornar automática a distribuição de recebíveis para sellers. Recomendamos a leitura do artigo [Split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) para mais informações.
 
 <div class="alert alert-warning">
-<p>Caso você deseje implementar o VTEX Sales App nas suas lojas físicas, não recomendamos configurar meios de pagamentos próprios para as contas franquia. O ideal é que as contas franquias utilizem os meios de pagamento da conta principal, para evitar conflitos de pagamento.</p>
+<p>Caso você deseje implementar o VTEX Sales App,é necessario que as lojas físicas utilizem os meios de pagamento da conta principal.</p>
 </div>
 
 ## Solicitar criação de conta franquia
diff --git a/docs/tutorials/pt/what-is-a-service.md b/docs/tutorials/pt/what-is-a-service.md
index 3de476059..80257493c 100644
--- a/docs/tutorials/pt/what-is-a-service.md
+++ b/docs/tutorials/pt/what-is-a-service.md
@@ -3,8 +3,8 @@ title: 'O que é um Serviço?'
 id: 46Ha8CEEQoC6Y40i6akG0y
 status: PUBLISHED
 createdAt: 2018-02-16T13:35:47.291Z
-updatedAt: 2020-09-10T14:25:34.223Z
-publishedAt: 2020-09-10T14:25:34.223Z
+updatedAt: 2023-11-16T17:24:14.877Z
+publishedAt: 2023-11-16T17:24:14.877Z
 firstPublishedAt: 2018-02-16T17:24:14.979Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -25,5 +25,5 @@ Se o seu produto comprado for uma Camisa da Seleção Brasileira, o nome do seu
 
 ### Artigos relacionados
 - [O que é um anexo?](/pt/tutorial/o-que-e-um-anexo)
-- [Cadastrar um anexo](/pt/tutorial/cadastrar-um-anexo)
+- [Cadastrar um anexo](/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU)
 - [Criar serviço para um SKU](/pt/tutorial/criando-servico-para-um-sku)
diff --git a/docs/tutorials/pt/what-is-a-transaction.md b/docs/tutorials/pt/what-is-a-transaction.md
index cc42e0e36..7e0043f9e 100644
--- a/docs/tutorials/pt/what-is-a-transaction.md
+++ b/docs/tutorials/pt/what-is-a-transaction.md
@@ -1,10 +1,10 @@
 ---
 title: 'O que é uma transação?'
 id: 36vMP5PES4oUWMWQuskIQ6
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-02-23T16:09:38.585Z
-updatedAt: 2020-11-27T19:39:37.153Z
-publishedAt: 2020-04-28T19:07:01.620Z
+updatedAt: 2023-09-28T16:00:07.059Z
+publishedAt: 2023-09-28T16:00:07.059Z
 firstPublishedAt: 2018-02-26T20:24:17.085Z
 contentType: tutorial
 productTeam: Financial
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 O movimento que o dinheiro faz ao ser trocado por um produto ou serviço é o que chamamos de __transação__. Assim, o pagamento é apenas uma etapa de um processo que envolve um intenso fluxo de troca de informações entre diversas partes: [gateways](/pt/tutorial/o-que-e-um-gateway-de-pagamentos), [subadquirentes](/pt/tutorial/o-que-e-um-subadquirente) e/ou [adquirentes](/pt/tutorial/o-que-e-um-adquirente), [bandeiras](/pt/tutorial/o-que-e-uma-bandeira-de-cartao-de-credito) e [bancos emissores](/pt/tutorial/o-que-e-banco-emissor).
 
-Em uma loja VTEX, uma transação se inicia toda vez que um usuário escolhe uma [condição de pagamento](/pt/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento) e fecha seu pedido. A partir daí, os dados da compra são enviados para a validação de cada um dos integrantes do processo. Você pode acompanhar cada etapa do [fluxo de transação](/pt/faq/fluxo-da-transacao-no-pci-gateway) no Pagamentos. Nele, você visualiza exatamente a situação de um pagamento através dos status exibidos.
+Em uma loja VTEX, uma transação se inicia toda vez que um usuário escolhe uma [condição de pagamento](/pt/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento) e fecha seu pedido. A partir daí, os dados da compra são enviados para a validação de cada um dos integrantes do processo. Você pode acompanhar cada etapa do [fluxo de transação](/pt/tutorial/fluxo-da-transacao-no-pagamentos) no Pagamentos. Nele, você visualiza exatamente a situação de um pagamento através dos status exibidos.
 
 ### Artigos relacionados
 - [O que é um gateway de pagamentos?](/pt/tutorial/o-que-e-um-gateway-de-pagamentos)
@@ -26,4 +26,4 @@ Em uma loja VTEX, uma transação se inicia toda vez que um usuário escolhe uma
 - [O que é uma bandeira de cartão de crédito?](/pt/tutorial/o-que-e-uma-bandeira-de-cartao-de-credito)
 - [O que é banco emissor?](/pt/tutorial/o-que-e-banco-emissor)
 - [Diferença entre meios de pagamento e condições de pagamento](/pt/tutorial/diferenca-entre-meios-de-pagamento-e-condicoes-de-pagamento)
--[ Fluxo na transação no Pagamentos](https://help.vtex.com/pt/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ "Fluxo na transação no Pagamentos") 
+- [Fluxo na transação no Pagamentos](https://help.vtex.com/pt/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ "Fluxo na transação no Pagamentos") 
diff --git a/docs/tutorials/pt/what-is-an-affiliate.md b/docs/tutorials/pt/what-is-an-affiliate.md
index 982ec2822..3ea0202a2 100644
--- a/docs/tutorials/pt/what-is-an-affiliate.md
+++ b/docs/tutorials/pt/what-is-an-affiliate.md
@@ -3,8 +3,8 @@ title: 'O que é afiliado'
 id: 4bN3e1YarSEammk2yOeMc0
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:48.620Z
-updatedAt: 2022-10-05T18:24:46.905Z
-publishedAt: 2022-10-05T18:24:46.905Z
+updatedAt: 2024-05-23T16:09:45.545Z
+publishedAt: 2024-05-23T16:09:45.545Z
 firstPublishedAt: 2019-01-24T22:01:57.938Z
 contentType: tutorial
 productTeam: Channels
@@ -21,6 +21,6 @@ O conceito de afiliado da VTEX é diferente da <a href="https://pt.wikipedia.org
 
 [Configurar afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado) será necessário apenas quando a loja atuar como seller de um marketplace.
 
-O afiliado funciona de uma maneira diferente das [políticas comerciais](https://help.vtex.com/pt/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV), pois todo marketplace deve corresponder a um código de afiliado único para o seller. Ou seja, o seller cria um afiliado para identificar o marketplace, e ainda que se utilize a mesma política comercial em marketplaces, os afiliados devem ser diferentes. Caso o seller integre com um [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), o [afiliado](https://help.vtex.com/es/tutorial/como-configurar-afiliado) será criado automaticamente.
+O afiliado funciona de uma maneira diferente das [políticas comerciais](https://help.vtex.com/pt/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV), pois todo marketplace deve corresponder a um código de afiliado único para o seller. Ou seja, o seller cria um afiliado para identificar o marketplace, e ainda que se utilize a mesma política comercial em marketplaces, os afiliados devem ser diferentes. Caso o seller integre com um [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), o [afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado) será criado automaticamente.
 
 Além da identificação de pedidos, os afiliados também funcionam como um webhook que notifica o serviço externo sobre mudanças em informações de um SKU, estoque ou preço. Saiba mais em [Guia de Integração - Consumir as informações do catálogo para utilizar em um Serviço Externo](http://help.vtex.com/pt/tutorial/guia-de-integracao-consumir-as-informacoes-do-catalogo).
diff --git a/docs/tutorials/pt/what-is-an-e-wallet.md b/docs/tutorials/pt/what-is-an-e-wallet.md
index b025021fa..c0f54f226 100644
--- a/docs/tutorials/pt/what-is-an-e-wallet.md
+++ b/docs/tutorials/pt/what-is-an-e-wallet.md
@@ -1,10 +1,10 @@
 ---
-title: 'O que é uma carteira digital (e-wallet)?'
+title: 'O que é uma carteira digital (ewallet)?'
 id: 4v5wcOe4A0SiaimWM2cU60
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:38.294Z
-updatedAt: 2019-12-31T15:26:35.284Z
-publishedAt: 2019-12-31T15:26:35.284Z
+updatedAt: 2023-09-26T15:16:20.294Z
+publishedAt: 2023-09-26T15:16:20.294Z
 firstPublishedAt: 2019-01-24T22:05:07.777Z
 contentType: tutorial
 productTeam: Financial
@@ -15,7 +15,7 @@ legacySlug: o-que-e-uma-carteira-digital-e-wallet
 subcategory: 2Xay1NOZKE2CSqKMwckOm8
 ---
 
-Uma carteira digital (também chamada de e-wallet) é um ambiente seguro onde podem ser armazenados dados bancários e/ou de cartão de crédito. Essas informações ficam criptografadas no sistema e, quando acessadas pelo seu dono, podem ser usadas para realizar compras na internet.
+Uma carteira digital (também chamada de ewallet) é um ambiente seguro onde podem ser armazenados dados bancários e/ou de cartão de crédito. Essas informações ficam criptografadas no sistema e, quando acessadas pelo seu dono, podem ser usadas para realizar compras na internet.
 
 Comprar com uma carteira digital oferece mais segurança para o usuário, uma vez que ele não precisa informar seus dados de pagamento no checkout da loja. Ao invés disso, o usuário é redirecionado para o ambiente da carteira digital, onde deverá passar por etapas de autenticação.
 
diff --git a/docs/tutorials/pt/what-is-deposit-slip.md b/docs/tutorials/pt/what-is-deposit-slip.md
index 60754bce9..887bd0b71 100644
--- a/docs/tutorials/pt/what-is-deposit-slip.md
+++ b/docs/tutorials/pt/what-is-deposit-slip.md
@@ -3,8 +3,8 @@ title: 'O que é  Ficha Depósito'
 id: 5zcak00O9G2KqoysQggus6
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:35.451Z
-updatedAt: 2019-12-31T15:25:20.325Z
-publishedAt: 2019-12-31T15:25:20.325Z
+updatedAt: 2024-03-18T13:03:11.449Z
+publishedAt: 2024-03-18T13:03:11.449Z
 firstPublishedAt: 2019-01-24T22:10:45.867Z
 contentType: tutorial
 productTeam: Financial
@@ -23,6 +23,13 @@ Para pagar com Ficha Depósito, o usuário precisa escolher essa condição de p
 Para efetivar a compra, o usuário precisa ir até um dos pontos credenciados e pagar o valor do documento. Esse pagamento pode ser feito em dinheiro ou com cartões de crédito.
 
 ## Como aceitar Ficha Depósito na sua loja
-Sua loja VTEX pode aceitar pagamentos com Ficha Depósito, desde que atue no México e tenha cadastro no Citibanamex. Esse banco mexicano possui integração com nossa plataforma e pode ser configurado na sua loja.
 
-Para saber como configurar o conector Banamex (responsável pela comunicação com o Citibanamex), acesse [este artigo do Help](/pt/tutorial/configurar-gateway-banamex).
+Para verificar os provedores que realizam transações com a Ficha Depósito e configurá-los em sua loja, siga os passos abaixo:
+
+1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Configurações__, ou digite __Configurações__ na barra de busca no topo da página.
+2. Na aba __Condições de Pagamentos__, clique no botão `+`.
+3. Clique sobre __FichaDeposito__.
+4. Ative a condição no campo __Status__.
+5. Selecione as opções disponíveis de provedores e realize as configurações necessárias para cada um deles.
+6. Clique em `Salvar`.
+
diff --git a/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md b/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
index 30918563b..a54ee4ea9 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
@@ -1,10 +1,10 @@
 ---
 title: 'Qual é o papel dos agentes financeiros no fluxo de pagamento de um pedido no Brasil?'
 id: 1dyPJ3gQCCO4ea2o6OMgCi
-status: CHANGED
+status: PUBLISHED
 createdAt: 2017-10-11T19:08:49.654Z
-updatedAt: 2020-11-27T19:40:35.496Z
-publishedAt: 2019-12-31T15:27:52.279Z
+updatedAt: 2024-03-18T18:55:40.724Z
+publishedAt: 2024-03-18T18:55:40.724Z
 firstPublishedAt: 2017-10-11T19:34:43.203Z
 contentType: tutorial
 productTeam: Financial
@@ -21,7 +21,7 @@ Neste artigo, esclareceremos os conceitos de adquirente, subadquirente, gateway,
 
 ## Gateway 
 
-Um gateway (também chamado de gateway de pagamento) é um __sistema que efetua a transmissão dos dados das compras realizadas na sua loja no momento do checkout__ como as empresas Braspag e Mundipagg.
+Um gateway (também chamado de gateway de pagamento) é um __sistema que efetua a transmissão dos dados das compras realizadas na sua loja no momento do checkout__.
 
 Como primeiro player do fluxo, ele é responsável por enviar as informações do pagamento recebidas no checkout para adquirentes, bandeiras e [bancos emissores](https://help.vtex.com/pt/tutorial/o-que-e-banco-emissor--7aVIVGwgtU4SWuqowSQksg "O que é Banco Emissor?") para, então, obter um retorno sobre a continuação do fluxo de compra ou do seu cancelamento. Em outras palavras, o gateway envia os dados de pagamento da compra e recebe respostas para que você saiba se uma determinada compra deve ou não ser confirmada, ou seja, se o pagamento foi ou não aprovado. 
 
@@ -41,7 +41,6 @@ Para que sua loja VTEX possa receber pagamentos, por exemplo, você precisa habi
 
 Quando tudo está em ordem e uma compra é autorizada pelos outros players do fluxo de compra, o adquirente fica responsável por repassar os valores (cobrados do cliente pelo banco emissor) para a conta da sua loja.
 
-
 ## Subadquirente
 
 Um subdadquirente é uma empresa que processa pagamentos e transmite suas informações para os outros players envolvidos no [fluxo de pagamento](https://help.vtex.com/pt/tutorial/cartao-de-credito-fluxo-basico-de-um-pagamento--1L1Y66GgcAUgkIqwgccCUK "Cartão de crédito - Fluxo básico de um pagamento"). Como facilitador, o seu papel é semelhante ao de um adquirente, mas não o substitui por completo pela sua falta de autonomia para desempenhar todas as funcionalidades de um adquirente. 
@@ -60,7 +59,6 @@ As bandeiras mantêm uma relação próxima com os adquirentes para garantir a a
 
 No [fluxo de pagamento por cartão de crédito](https://help.vtex.com/pt/tutorial/cartao-de-credito-fluxo-basico-de-um-pagamento--1L1Y66GgcAUgkIqwgccCUK "Cartão de crédito - Fluxo básico de um pagamento"), a bandeira recebe do adquirente as informações da compra realizada na sua loja. Então, ela valida as condições (como o número de parcelas) e envia os dados para o banco emissor, que verifica se o comprador possui limite disponível. Dessa forma, a bandeira serve tanto para regular o uso do cartão quanto como ponte entre a adquirente e o banco do consumidor.
 
-
 ## Banco Emissor
 
 Banco Emissor é a instituição financeira responsável pelos meios de pagamento, sejam eles boletos bancários, cartões de débito ou de crédito. É ele que, ao receber os dados de uma compra feita na sua loja, vai autorizar ou não a venda (dependendo do limite de crédito ou do dinheiro disponível na conta do usuário). Com tudo certo, o banco efetiva a cobrança do valor.
@@ -75,6 +73,7 @@ Ele coleta dados sobre o comportamento dos usuários e os comparam com padrões
 
 Na VTEX, primeiro a operadora do pagamento aprova a compra e, em seguida, o antifraude avalia o pedido. Com tudo em ordem, ele segue seu fluxo normal. São exemplos de antifraude a ClearSale e a Konduto. 
 
----
-
+<div class="alert alert-info">
 É importante ressaltar que cada negócio depende de fatores específicos que influenciam na decisão sobre qual modalidade usar. São diversas as variáveis que podem determinar a escolha do meio de pagamento e qual será o seu fluxo financeiro. É fundamental, portanto, ter em mente as reais necessidades e propósitos do lojista e do projeto desejado.
+</div>
+
diff --git a/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md b/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md
index 5a668e11d..73879bb65 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md
@@ -25,7 +25,7 @@ __As três etapas da logística são representadas pela seguinte estrutura:__
 
 __E podem ser ilustradas pelo fluxo abaixo:__
 
-![PT Conceitos Logistics](https://images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/bfa6fd2b0feed227b8f7338ee5a9db24/PT_Conceitos_Logistics.png)
+![PT Conceitos Logistics](//images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/bfa6fd2b0feed227b8f7338ee5a9db24/PT_Conceitos_Logistics.png)
 
 ## Estoque 
 É o espaço físico utilizado para a armazenagem das mercadorias de um e-commerce, funcionando como o repositório de disponibilidade dos itens da sua loja.
diff --git a/docs/tutorials/pt/what-is-the-difference-between-product-and-sku.md b/docs/tutorials/pt/what-is-the-difference-between-product-and-sku.md
index 5b4553fdd..2fec202b8 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-product-and-sku.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-product-and-sku.md
@@ -3,8 +3,8 @@ title: 'Qual a diferença entre produto e SKU?'
 id: 5yhABFDOpyiUcicce2W4CM
 status: PUBLISHED
 createdAt: 2018-01-26T17:49:48.383Z
-updatedAt: 2022-06-08T15:45:08.032Z
-publishedAt: 2022-06-08T15:45:08.032Z
+updatedAt: 2023-07-17T13:15:51.969Z
+publishedAt: 2023-07-17T13:15:51.969Z
 firstPublishedAt: 2018-01-26T18:00:17.827Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -27,6 +27,4 @@ Estruturalmente, primeiro você define as informações do produto para, depois,
 
 ## Artigos relacionados
 
-- [Cadastrar um produto](/pt/tutorial/cadastrando-produto)
-
-- [Cadastrar um SKU](/pt/tutorial/cadastrando-sku)
+- [Cadastrar um produto](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567)
diff --git a/docs/tutorials/pt/what-is-the-maximum-limit-of-promotions.md b/docs/tutorials/pt/what-is-the-maximum-limit-of-promotions.md
index a461947df..c148d010d 100644
--- a/docs/tutorials/pt/what-is-the-maximum-limit-of-promotions.md
+++ b/docs/tutorials/pt/what-is-the-maximum-limit-of-promotions.md
@@ -3,8 +3,8 @@ title: 'Quantos cupons, taxas e promoções posso ter na minha loja?'
 id: frequentlyAskedQuestions_352
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:52.883Z
-updatedAt: 2021-02-01T15:43:04.116Z
-publishedAt: 2021-02-01T15:43:04.116Z
+updatedAt: 2023-07-10T18:00:19.469Z
+publishedAt: 2023-07-10T18:00:19.469Z
 firstPublishedAt: 2019-01-24T22:05:32.884Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
@@ -15,13 +15,12 @@ legacySlug: qual-o-limite-maximo-de-promocoes
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-Hoje temos uma limitação na quantidade de promoções, taxas e cupons ativos.
+Existe um limite na quantidade de promoções, taxas e cupons ativos:
 
 - [Promoções](/pt/tutorial/como-criar-promocoes--tutorials_320): 100
 - [Taxas](/pt/tutorial/como-criar-taxaimposto/): 100
-- [Cupons:](/pt/tutorial/como-criar-cupom/) 50.000
+- [Cupons](/pt/tutorial/como-criar-cupom/): 50.000
 
-_Serão contabilizadas somente as promoções, taxas ou cupons ativos, ou seja, as promoções, taxas ou cupons arquivados não serão contabilizados._
-
-Entre em contato com a VTEX caso tenha necessidade de alterar algum desses limites.
+Somente as promoções, taxas ou cupons ativos são contabilizados no cálculo desse limite, ou seja, promoções, taxas ou cupons arquivados não são considerados.
 
+Se for necessário alterar algum desses limites, entre em contato com o nosso [Suporte](https://help.vtex.com/en/support) para analisarmos a viabilidade da mudança.
diff --git a/docs/tutorials/pt/what-is-the-pci-ssc.md b/docs/tutorials/pt/what-is-the-pci-ssc.md
index 826149c6b..ad6220d37 100644
--- a/docs/tutorials/pt/what-is-the-pci-ssc.md
+++ b/docs/tutorials/pt/what-is-the-pci-ssc.md
@@ -3,8 +3,8 @@ title: 'O que é o PCI SSC'
 id: 4jo3Vkox3amSO2w4qIWa0E
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:48.373Z
-updatedAt: 2021-09-22T12:32:07.193Z
-publishedAt: 2021-09-22T12:32:07.193Z
+updatedAt: 2024-07-23T15:26:30.020Z
+publishedAt: 2024-07-23T15:26:30.020Z
 firstPublishedAt: 2019-01-24T22:12:41.627Z
 contentType: tutorial
 productTeam: Financial
@@ -21,4 +21,4 @@ Foi fundado pelas empresas American Express, Discover Financial Services, JCB In
 
 O PCI SSC é uma certificação que a VTEX possui de seus serviços, dada por essa instituição, trazendo informações da segurança que disponibilizamos às lojas e aos seus consumidores. 
 
-Para maiores informações, veja a [categoria de certificação PCI SSC da VTEX](https://secure.vtex.com/?an=VTEX).
+Para maiores informações, veja a [categoria de certificação PCI SSC da VTEX](https://vtex.com/br-pt/compliance/certifications/).
diff --git a/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
index d71663818..45a336cf5 100644
--- a/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
@@ -35,7 +35,7 @@ Os tipos são:
 
 Para criar uma tag personalizada de controle customizado, basta clicar em __Add__ e cadastrar um nome e uma tag, e então selecionar o tipo.
 
-![cms-custom-elements PT](https://images.ctfassets.net/alneenqid6w5/oYjlNFuR8WKUkCag2yiQM/8da98e4f84d6e31639552d8d28931089/custom_elements_pt.png)
+![cms-custom-elements PT](//images.ctfassets.net/alneenqid6w5/oYjlNFuR8WKUkCag2yiQM/8da98e4f84d6e31639552d8d28931089/custom_elements_pt.png)
 
 <div class="alert alert-warning">
   <p><b>Atenção:</b> não crie um controle do tipo HTML com um elemento <code>title</code>. Isso pode interferir no funcionamento correto da sua loja.</p>
diff --git a/docs/tutorials/pt/what-is-transparent-checkout.md b/docs/tutorials/pt/what-is-transparent-checkout.md
index b4f16a90e..0c7306bce 100644
--- a/docs/tutorials/pt/what-is-transparent-checkout.md
+++ b/docs/tutorials/pt/what-is-transparent-checkout.md
@@ -1,10 +1,10 @@
 ---
 title: 'O que é checkout transparente?'
 id: 2Y4ECegUmcYUggmck2GOwe
-status: CHANGED
+status: PUBLISHED
 createdAt: 2018-02-27T18:58:12.252Z
-updatedAt: 2020-11-27T19:39:49.137Z
-publishedAt: 2020-05-31T14:34:28.895Z
+updatedAt: 2023-07-20T18:06:08.385Z
+publishedAt: 2023-07-20T18:06:08.385Z
 firstPublishedAt: 2018-02-27T20:40:08.480Z
 contentType: tutorial
 productTeam: Shopping
diff --git a/docs/tutorials/pt/what-offline-payment-conditions-are-available-in-latin-america.md b/docs/tutorials/pt/what-offline-payment-conditions-are-available-in-latin-america.md
index 5352409da..8b21175c7 100644
--- a/docs/tutorials/pt/what-offline-payment-conditions-are-available-in-latin-america.md
+++ b/docs/tutorials/pt/what-offline-payment-conditions-are-available-in-latin-america.md
@@ -1,10 +1,10 @@
 ---
 title: 'Que condições de pagamento offline estão disponíveis na América Latina?'
 id: 2lXPwiH6KcsSMuWaoigueq
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:37.602Z
-updatedAt: 2019-12-31T15:19:41.744Z
-publishedAt: 2019-12-31T15:19:41.744Z
+updatedAt: 2024-03-19T12:05:40.449Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:01:19.092Z
 contentType: tutorial
 productTeam: Financial
diff --git a/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md b/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md
index 50c4d3369..1e8975abd 100644
--- a/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md
+++ b/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md
@@ -3,8 +3,8 @@ title: 'O que fazer quando o relatório de exportações não chega no email?'
 id: 1zUBgmgkgMZyHyy0veR7Oj
 status: PUBLISHED
 createdAt: 2022-10-17T19:56:25.618Z
-updatedAt: 2023-03-28T23:24:48.040Z
-publishedAt: 2023-03-28T23:24:48.040Z
+updatedAt: 2024-06-11T16:48:56.974Z
+publishedAt: 2024-06-11T16:48:56.974Z
 firstPublishedAt: 2022-10-17T19:59:15.174Z
 contentType: tutorial
 productTeam: Master Data
@@ -15,7 +15,7 @@ legacySlug: o-que-fazer-quando-o-relatorio-de-exportacoes-nao-chega-no-email
 subcategory: 2AThnkEZAYbk4G4EIs53rL
 ---
 
-Na VTEX, cada lojista pode acessar um relatório sobre [as exportações de dados](https://help.vtex.com/pt/tutorial/exportando-dados "as exportações de dados") do [Master Data](https://help.vtex.com/pt/tutorial/o-que-e-o-master-data "Master Data") - módulo que reúne informações dos clientes de uma loja. 
+Na VTEX, cada lojista pode acessar um relatório sobre [as exportações de dados](https://help.vtex.com/en/tutorial/making-a-master-data-field-editable--frequentlyAskedQuestions_3049 "as exportações de dados") do [Master Data](https://help.vtex.com/pt/tutorial/o-que-e-o-master-data "Master Data") - módulo que reúne informações dos clientes de uma loja. 
 
 Estes relatórios são enviados para o email do solicitante da ação. Porém, por motivos externos a VTEX, é possível que esse conteúdo demore mais que o esperado para chegar na caixa de entrada do lojista. 
 
@@ -24,10 +24,9 @@ Ainda assim, existe uma maneira de extrair manualmente esse relatório acessando
 A seguir, entenda o passo a passo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. Clique em __“Exportations”__.
-![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
-3. Certifique-se que aba aberta é a de __“Aplicações”__.
-![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
-4. Em __“Status de exportações”__, clique no relatório que deseja baixar.
+2. Clique em __Exportações__. ![exportacoes-md](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/043eef8efcf827b16d0546110bcec786/exportacoes.png)
+3. Certifique-se que aba aberta é a de __Aplicações__.
+4. Em __Status das exportações__, identifique a linha do relatório que deseja baixar.
+5. Se o __Status__ for __Finalizado - Baixar__, clique em **Baixar** para fazer download do arquivo.
 
 Dessa forma, é possível acessar esse material mesmo que o email original não tenha chegado para o solicitante.
diff --git a/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md b/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md
new file mode 100644
index 000000000..7fb3783ec
--- /dev/null
+++ b/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md
@@ -0,0 +1,96 @@
+---
+title: 'Gerenciamento e detalhes do WhatsApp AI Campaigns'
+id: q9JqDErMqGV4zvsYqkD4s
+status: PUBLISHED
+createdAt: 2024-06-25T11:58:05.514Z
+updatedAt: 2024-06-25T16:28:52.542Z
+publishedAt: 2024-06-25T16:28:52.542Z
+firstPublishedAt: 2024-06-25T16:11:51.825Z
+contentType: tutorial
+productTeam: Others
+author: 2AhArvGNSPKwUAd8GOz0iU
+slug: gerenciamento-e-detalhes-do-whatsapp-ai-campaigns
+locale: pt
+legacySlug: gerenciamento-e-detalhes-do-whatsapp-ai-campaigns
+subcategory: 4SC2gPmUH3cHD5HjGfQ5Vg
+---
+
+Esta página fornece uma visão detalhada sobre o gerenciamento e o detalhe do WhatsApp AI Campaigns na plataforma VTEX. Abordamos desde a configuração até o acompanhamento das métricas de desempenho, ajudando você a otimizar a eficácia de suas campanhas e a maximizar as conversões.
+
+Confira neste artigo como você pode gerenciar e acompanhar suas campanhas:
+
+- [Selecionando datas](#selecionando-datas)
+- [Enviando relatório](#enviando-relatorio)
+- [Editando uma campanha](#editando-uma-campanha)
+- [Pausando uma campanha](#pausando-uma-cmpanha)
+- [Visualizando detalhes do painel Análises](#visualizando-detalhes-do-painel-analises)
+
+## Gerenciamento do WhatsApp AI Campaigns
+
+A página do WhatsApp AI Campaigns permite visualizar as informações de Análises e Campanhas Ativas.
+
+### Selecionando datas
+
+Navegue pelos dias específicos para visualizar os disparos de mensagens realizados em cada período.
+
+1. No Admin VTEX, acesse **Promoções > Campanhas de WhatsApp > Visão geral**.
+2. Clique no Seletor de datas.
+3. Selecione a data que deseja visualizar os dados de análises.
+
+### Enviando relatório
+
+1. No Admin VTEX, acesse Promoções > Campanhas de WhatsApp > Visão geral.
+2. Clique em `ENVIAR RELATÓRIO` no canto superior direito da seção.
+3. Forneça o endereço de email que irá receber o relatório.
+4. Clique em `ENVIAR RELATÓRIO`.
+
+O relatório enviado por email será um arquivo `csv`com as seguintes informações:
+
+- **userId:** identificador único do usuário que realizou a compra. 
+- **deliveredReminderAt:** data e hora em que um lembrete sobre a compra foi enviado ao usuário.
+- **readReminderAt:** data e hora em que o usuário visualizou o lembrete enviado. 
+- **orderCreatedAt:** data e hora em que o pedido foi criado no sistema. 
+- **hasClickedOnReminder:** indica se o usuário clicou ou não no lembrete enviado. 
+- **checkoutItems:** lista de itens que o usuário adicionou ao carrinho durante o processo de checkout. 
+- **orderItems:** lista de itens que foram efetivamente comprados pelo usuário. 
+- **orderTotal:** valor total do pedido, somando o preço de todos os itens comprados. 
+- **currency:** moeda utilizada para o pagamento do pedido. 
+- **orderFormId:** identificador único do formulário de pedido utilizado durante o checkout. 
+
+### Editando uma campanha
+
+Depois da campanha configurada, você pode editar o idioma ou o tipo de mensagem que deseja personalizar.
+
+1. No Admin VTEX, acesse Promoções > Campanhas de WhatsApp > Visão geral.
+2. Clique no ícone <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Clique em `Editar`.
+4. Altere as informações que deseja.
+5. Clique em `Confirmar`.
+
+### Pausando uma campanha
+
+Para pausar o envio de mensagens de uma campanha:
+
+1. No Admin VTEX, acesse Promoções > Campanhas de WhatsApp > Visão geral.
+2. Clique no ícone <i class="fas fa-ellipsis-v" aria-hidden="true"></i>.
+3. Clique em `Pausar`.
+4. Clique em `Confirmar`.
+
+## Visualizando detalhes do painel Análises
+
+Você pode encontrar informações relativas às suas campanhas em andamento no Admin VTEX.
+
+![Visão geral-PT](//images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/5b970054cd95f9bd75086f1df4fca02d/Vis_o_geral-PT.png)
+
+Abaixo estão os detalhes das métricas disponíveis:
+
+- **Mensagens entregues:** número total de mensagens que chegaram com êxito aos destinatários pretendidos, sem problemas de entrega.
+- **Mensagens lidas:** número total de mensagens abertas pelos destinatários, indicando o envolvimento do público.
+- **Cliques únicos:** número de usuários que clicaram nos botões das mensagens.
+- **Total de cliques:** número total de interações com os botões incorporados nas mensagens, fornecendo uma medida quantitativa do engajamento.
+- **Total de conversões:** o número total de conversões que ocorrem após a entrega bem-sucedida de uma mensagem a um destinatário. O total de conversões é a soma das duas métricas abaixo:
+      - **Conversões assistidas:** conversões que ocorrem dentro de 3 dias após o recebimento da mensagem.
+      - **Conversões por clique (CTC):** conversões que ocorrem quando os usuários clicam no link da mensagem e realizam uma compra dentro de 15 dias.
+- **Valor total de conversões:** valor total do pedido das conversões.
+- **Valor total de conversões por clique:** valor total do pedido proveniente de conversões de clique.
+
diff --git a/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md b/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md
index edf90f17a..a4b10db7d 100644
--- a/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md
+++ b/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md
@@ -22,6 +22,6 @@ Mas lembre-se: uma recorrência só aparece na listagem depois que seu pagamento
 1. Acesse o módulo __Gerenciamento de Pedidos__.
 2. Clique na aba __Assinaturas__.
 
-![subscriptions PT](https://images.ctfassets.net/alneenqid6w5/yF4h1Bs3Ys2gU4kYGCkyK/feb155bc4414f904db25aea5dc0f12e8/subscriptions_PT.png)
+![subscriptions PT](//images.ctfassets.net/alneenqid6w5/yF4h1Bs3Ys2gU4kYGCkyK/feb155bc4414f904db25aea5dc0f12e8/subscriptions_PT.png)
 
 
diff --git a/docs/tutorials/pt/which-security-certificates-may-be-added-to-my-store.md b/docs/tutorials/pt/which-security-certificates-may-be-added-to-my-store.md
index dc840141a..9ce35e10f 100644
--- a/docs/tutorials/pt/which-security-certificates-may-be-added-to-my-store.md
+++ b/docs/tutorials/pt/which-security-certificates-may-be-added-to-my-store.md
@@ -1,10 +1,10 @@
 ---
 title: 'Quais selos de segurança podem ser adicionados à minha loja?'
 id: 29ivkiHbXqMIa8QMKCSQ2K
-status: PUBLISHED
+status: DRAFT
 createdAt: 2019-01-24T20:45:48.223Z
-updatedAt: 2019-12-31T15:23:12.479Z
-publishedAt: 2019-12-31T15:23:12.479Z
+updatedAt: 2024-03-11T13:21:15.878Z
+publishedAt: 
 firstPublishedAt: 2019-01-24T22:15:04.845Z
 contentType: tutorial
 productTeam: Marketing & Merchandising
diff --git a/docs/tutorials/pt/white-label-seller.md b/docs/tutorials/pt/white-label-seller.md
index a97b6bc71..78acbb036 100644
--- a/docs/tutorials/pt/white-label-seller.md
+++ b/docs/tutorials/pt/white-label-seller.md
@@ -3,8 +3,8 @@ title: 'Seller white label'
 id: 5orlGHyDHGAYciQ64oEgKa
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:34.034Z
-updatedAt: 2022-10-17T17:52:42.676Z
-publishedAt: 2022-10-17T17:52:42.676Z
+updatedAt: 2023-07-14T15:15:56.338Z
+publishedAt: 2023-07-14T15:15:56.338Z
 firstPublishedAt: 2019-01-24T22:03:52.175Z
 contentType: tutorial
 productTeam: Channels
@@ -48,3 +48,4 @@ Para adicionar um seller white label é necessário ter esse modelo previsto no
 - [Seleção de sellers white label](https://help.vtex.com/pt/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa)
 - [Configurar marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb)
 - [Adicionar seller](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392)
+- [Escolher entre conta padrão, conta franquia ou Seller Portal](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78)
diff --git a/docs/tutorials/pt/white-label-sellers-selection.md b/docs/tutorials/pt/white-label-sellers-selection.md
index b37a28a6a..b1bc504c8 100644
--- a/docs/tutorials/pt/white-label-sellers-selection.md
+++ b/docs/tutorials/pt/white-label-sellers-selection.md
@@ -112,13 +112,13 @@ Se existir um empate entre sellers nos critérios de melhor custo ou prazo, o cr
 
 Um cliente adicionou ao carrinho cinco SKUs. Dentre os sellers que entregam na sua região, os sellers A, B, C e D, cada um possui no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) apenas parte dos itens, conforme a imagem a seguir:
 
-![print_selecao_seller_white_label_1](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
+![print_selecao_seller_white_label_1](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
 
 A plataforma VTEX seleciona o seller que tem disponível no estoque a quantidade máxima de SKUs do carrinho. Neste caso, trata-se do Seller B, o único que entrega três SKUs. 
 
 Depois que o Seller B é selecionado, existem ainda dois SKUs não entregues. Se um único seller enviasse ambos, esse seria o fator decisivo da seleção, pois o objetivo é reunir o menor número de sellers para atender o carrinho. No entanto, são necessários os sellers A e C para entregar os SKUs 1 e 4, conforme imagem a seguir:
 
-![print_selecao_seller_white_label_2](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
+![print_selecao_seller_white_label_2](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
 
 Na primeira imagem, o Seller C era capaz de entregar os SKUs 3 e 4, e o Seller D entregava o SKU 5. No entanto, o Seller B foi selecionado para entregar esses itens, de forma que os SKUs são desconsiderados nas outras etapas de seleção. Isso foi representado com a remoção da seta do Seller C para o SKU 3 e do Seller D para o SKU 5.
 
@@ -128,7 +128,7 @@ O resultado da seleção para entrega é uma combinação dos sellers A, B e C.
 
 Um cliente adicionou cinco SKUs ao carrinho e existem quatro sellers que entregam na sua região, os sellers A, B, C e D. Nenhum deles tem no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) todos os itens, conforme imagem a seguir:
 
-![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+![print_selecao_seller_white_label_3](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
 
 A plataforma VTEX seleciona o seller que tem disponível no estoque o maior número de SKUs do carrinho. Tanto o Seller B quanto o D são capazes de entregar três itens, e como ambos entregam o SKU 3, existe uma concorrência.
 
@@ -141,11 +141,11 @@ Digamos que o Seller B tenha a entrega mais barata e que o Seller D tenha a mais
 
 - **Entrega mais rápida:** quando o Seller D é selecionado, restam como não entregues os SKUs 3 e 4. O Seller C consegue entregar ambos, sendo o escolhido, e o resultado da seleção é a combinação dos seller D e C.
 
-![print_selecao_seller_white_label_4](https://images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
+![print_selecao_seller_white_label_4](//images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
 
 - **Entrega mais barata:** quando o Seller B é selecionado, restam como não entregues os SKUs 1 e 4. Como somente o Seller A entrega o SKU 1, e somente o Seller C entrega o SKU 4, o resultado da seleção é uma combinação dos sellers A, B e C. 
 
-![print_selecao_seller_white_label_5](https://images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
+![print_selecao_seller_white_label_5](//images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
 
 Nas imagens para entrega mais barata e mais rápida, foram retiradas as setas repetidas de sellers que entregavam SKUs já cobertos pelos sellers B e D. O motivo é que, nas sucessivas etapas de seleção, SKUs cobertos são desconsiderados.
 
diff --git a/docs/tutorials/pt/why-dont-marketplace-orders-integrate-with-my-store.md b/docs/tutorials/pt/why-dont-marketplace-orders-integrate-with-my-store.md
new file mode 100644
index 000000000..f86f2ac5d
--- /dev/null
+++ b/docs/tutorials/pt/why-dont-marketplace-orders-integrate-with-my-store.md
@@ -0,0 +1,42 @@
+---
+title: 'Porque os pedidos do marketplace não integram com minha loja?'
+id: 275YvF8dyry5KmfY9epoET
+status: PUBLISHED
+createdAt: 2024-06-21T14:24:48.621Z
+updatedAt: 2024-06-21T14:50:25.468Z
+publishedAt: 2024-06-21T14:50:25.468Z
+firstPublishedAt: 2024-06-21T14:48:49.434Z
+contentType: tutorial
+productTeam: Others
+author: 2p7evLfTcDrhc5qtrzbLWD
+slug: porque-os-pedidos-do-marketplace-nao-integram-com-minha-loja
+locale: pt
+legacySlug: porque-os-pedidos-do-marketplace-nao-integram-com-minha-loja
+subcategory: 2LcLWCYaEm5qPmOuYUiKIS
+---
+
+**Tags:** pedidos, marketplace  
+**Palavras-chave:** integração, marketplace, pedidos, SKU, estoque 
+
+Quando erros de integração em pedidos ocorrem entre um marketplace e sua loja, mensagens são exibidas na página de cada pedido, informando qual o erro ocorreu no pedido. Os possíveis erros de integração de pedido são os seguintes:  
+
+- Dados de entrega incompletos.  
+- Divergência de valores.  
+- ID de SKU inválido.  
+- Indisponibilidade de inventário.  
+- Status de indisponibilidade.  
+- Transportadora não cadastrada no ERP.  
+
+Verifique o status da integração dos pedidos e as mensagens acessando no Admin VTEX. **Marketplace > Conexões > Pedidos** ou digite **Pedidos** na barra de busca.   
+
+## Solução
+
+| **Tipo de erro** | **Significado** | **Ação requerida** |
+|:---:|:---:|:---:|
+| **Dados de entrega incompletos** | Os dados para entrega estão incompletos ou preenchidos incorretamente. | Corrigir ou preencher os dados solicitados seguindo a documentação [Fluxo e status de pedidos.](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196) |
+| <br>**Divergência de valores** | <br>O valor total do pedido pago no marketplace difere do valor esperado pela loja VTEX, e essa diferença de valor supera o percentual aceito pela loja VTEX ou a Taxa de divergência de preço não está configurada.<br>**Exemplo**<br>O total pago pelo pedido no marketplace é igual R$ 311,77, o valor esperado pela loja é igual R$ 313,61. Ou seja, pedido tem uma diferença de R$ 1,84. | [Reprocessar o pedido](https://help.vtex.com/pt/tutorial/verificando-integracao-no-bridge#pedidos) ou Configurar a [Regra de divergência de valores.](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) |
+| **ID de SKU inválido** | Os IDs dos produtos cadastrados na política comercial são diferentes dos IDs cadastrados no marketplace. | Alterar os IDs dos SKUs no marketplace, para terem os mesmos códigos dos produtos na política comercial. |
+| **Indisponibilidade inventário** | O SKU não está sendo exibido no marketplace.<br>Veja a lista completa de [Erros de integração de estoque com marketplaces.](https://help.vtex.com/pt/tutorial/erros-de-integracao-de-estoque-com-marketplaces--32bcsv9Dx1Dtl0YQOwWDpc) | Aplicar a correção requerida conforme o erro identificado na documentação [Erros de integração de estoque com marketplaces.](https://help.vtex.com/pt/tutorial/erros-de-integracao-de-estoque-com-marketplaces--32bcsv9Dx1Dtl0YQOwWDpc)<br>  |
+| **Status de indisponibilidade** | O produto está disponível em sua loja, porém o marketplace bloqueou o item em sua vitrine. O status do pedido aparecerá como **Unavailable.** | Entrar em contato com o marketplace para a liberação do pedido. |
+| **Transportadora não cadastrada no ERP** | Transportadora selecionada para a entrega do produto não está cadastrada no ERP.<br>**Exemplo**<br>Transportadora nova foi cadastrada na VTEX, mas não foi cadastrada no ERP. | Atualizar o cadastro de transportadoras no ERP conforme as cadastradas na VTEX. |
+
diff --git a/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 6c7724b47..eb129098d 100644
--- a/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -1,10 +1,10 @@
 ---
 title: 'Por que um cliente conseguiu cadastrar um CPF num campo de CNPJ?'
 id: K6zJn8JFOKk5ON1XFB6ZJ
-status: PUBLISHED
+status: DRAFT
 createdAt: 2022-10-17T19:22:31.749Z
-updatedAt: 2023-03-28T22:55:52.032Z
-publishedAt: 2023-03-28T22:55:52.032Z
+updatedAt: 2024-07-11T19:21:58.380Z
+publishedAt: 
 firstPublishedAt: 2022-10-17T19:43:17.176Z
 contentType: tutorial
 productTeam: Master Data
@@ -37,7 +37,7 @@ Siga os passos abaixo para validar as informações:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
 2. Na caixa __Profile System__, clique em __Clientes__.
-3. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+3. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 4. Clique no registro do cliente para acessar os detalhes do perfil.
 
 Na seção __Contato__, você verá que a opção `É Empresa?` está preenchida com o valor `Não`. Ao mesmo tempo, na seção __Dados da empresa__, você verá que o campo `Tipo documento` está preenchido com o valor `cnpj`. 
diff --git a/docs/tutorials/pt/widget.md b/docs/tutorials/pt/widget.md
index 501c4e93a..cde6bcc91 100644
--- a/docs/tutorials/pt/widget.md
+++ b/docs/tutorials/pt/widget.md
@@ -27,21 +27,21 @@ Para começar a configuração, você deve ter criado anteriormente os links da
 
 Para configurar o Widget, acesse o menu **Atrair > Widget**:
 
-![Widget 1](https://images.ctfassets.net/alneenqid6w5/plu5lwBYTbLY02fyz1orV/42c0462dfe1cf8bbb2990a684992cbb9/Screenshot_2022-08-26_at_16-48-30_Widget.png)
+![Widget 1](//images.ctfassets.net/alneenqid6w5/plu5lwBYTbLY02fyz1orV/42c0462dfe1cf8bbb2990a684992cbb9/Screenshot_2022-08-26_at_16-48-30_Widget.png)
 
 Clique em **Novo**.
 
-![Widget 2](https://images.ctfassets.net/alneenqid6w5/5gdzo6cmPcnahgjsNBggVm/625f4267163a0acd29e77357a29591de/Screenshot_2022-08-26_at_16-48-35_Widget.png)
+![Widget 2](//images.ctfassets.net/alneenqid6w5/5gdzo6cmPcnahgjsNBggVm/625f4267163a0acd29e77357a29591de/Screenshot_2022-08-26_at_16-48-35_Widget.png)
 
 Selecione qual será o **link** do seu Widget:
 
-![Widget 3](https://images.ctfassets.net/alneenqid6w5/3KLP64x03ZXU08YUj91rWO/7f4164e710339ea907d081da684e5a20/Screenshot_2022-08-26_at_16-52-25_Widget.png)
+![Widget 3](//images.ctfassets.net/alneenqid6w5/3KLP64x03ZXU08YUj91rWO/7f4164e710339ea907d081da684e5a20/Screenshot_2022-08-26_at_16-52-25_Widget.png)
 
 Lembrando: Seu widget ficará disponível para visualização durante a configuração para que você acompanhe as alterações simultaneamente, no canto inferior direito.
 
 Defina agora as **configurações:**
 
-![Widget 4](https://images.ctfassets.net/alneenqid6w5/4jdAfiLbtqcX6PjueiA6nk/46ad924295bd825ca9629270d2041d42/Screenshot_2022-08-26_at_16-52-32_Widget.png)
+![Widget 4](//images.ctfassets.net/alneenqid6w5/4jdAfiLbtqcX6PjueiA6nk/46ad924295bd825ca9629270d2041d42/Screenshot_2022-08-26_at_16-52-32_Widget.png)
 
 Entre as opções, é possível definir o **tamanho** do Widget, se ficará **posicionado** no canto inferior esquerdo ou direito e também, se terá **ícone ou título, balão com mensagem** ou não.
 
@@ -49,24 +49,24 @@ Dica: explore todas as opções para escolher qual se adequa ao seu objetivo.
 
 Você também pode configurar **Gatilhos** para o seu Widget, ou seja, definir quando ele ficará visivel ou não para o seu cliente. 
 
-![Widget 5](https://images.ctfassets.net/alneenqid6w5/3Adkuu3v93Bi7t0boSDTrN/e1e66f29e390c15bde4d2e1cf6b7d3d4/Screenshot_2022-08-26_at_16-52-38_Widget.png)
+![Widget 5](//images.ctfassets.net/alneenqid6w5/3Adkuu3v93Bi7t0boSDTrN/e1e66f29e390c15bde4d2e1cf6b7d3d4/Screenshot_2022-08-26_at_16-52-38_Widget.png)
 
 Defina em quais **páginas** do seu site o Widget aparecerá:
 
-![Widget 6](https://images.ctfassets.net/alneenqid6w5/3tfk4LFq53xFe71wCzaKl7/82271947ed49cd1ce205d2860dc19ec7/Screenshot_2022-08-26_at_16-52-41_Widget.png)
+![Widget 6](//images.ctfassets.net/alneenqid6w5/3tfk4LFq53xFe71wCzaKl7/82271947ed49cd1ce205d2860dc19ec7/Screenshot_2022-08-26_at_16-52-41_Widget.png)
 
 É possível definir também se o clique no Widget direcionará seu cliente para uma nova aba, ou se o link destino será aberto na mesma aba.
 
-![Widget 7](https://images.ctfassets.net/alneenqid6w5/01vdpRCpknmKAuCn4Vepve/8272a56f4daf91e749bd35c8b2a461b9/Screenshot_2022-08-26_at_16-52-46_Widget.png)
+![Widget 7](//images.ctfassets.net/alneenqid6w5/01vdpRCpknmKAuCn4Vepve/8272a56f4daf91e749bd35c8b2a461b9/Screenshot_2022-08-26_at_16-52-46_Widget.png)
 
 Após definir as configurações, gatilhos e ação do clique, acesse _**“Salvar”**_
 
 Para instalar o Widget no seu site, acesse o menu _**\\"Widget\\"**_ e depois em _**\\"Instalação\\"**_:
 
-![Widget 8](https://images.ctfassets.net/alneenqid6w5/14g7BJkYhfCrn5l2W4GQB5/c1929880319410d55d389976bd1ba456/Screenshot_2022-08-26_at_16-52-51_Widget.png)
+![Widget 8](//images.ctfassets.net/alneenqid6w5/14g7BJkYhfCrn5l2W4GQB5/c1929880319410d55d389976bd1ba456/Screenshot_2022-08-26_at_16-52-51_Widget.png)
 
 Basta clicar em _**\\"copiar código\\"**_ e colar o código fornecido no _“Body”_ do painel administrativo do seu site:
 
-![Widget 9](https://images.ctfassets.net/alneenqid6w5/6S6gSymknb9qibSStoAINz/d76815718ce166b4b922519224a9316c/Screenshot_2022-08-26_at_16-52-56_Widget.png)
+![Widget 9](//images.ctfassets.net/alneenqid6w5/6S6gSymknb9qibSStoAINz/d76815718ce166b4b922519224a9316c/Screenshot_2022-08-26_at_16-52-56_Widget.png)
 
 E pronto, qualquer ajuste dentro do painel do VTEX Assisted Sales (SuiteShare), seá atualizado automaticamente no seu site, sem que seja necessária qualquer alteração no script.
diff --git a/docs/tutorials/pt/wix-suiteshare.md b/docs/tutorials/pt/wix-suiteshare.md
index 008c6819d..aa556f003 100644
--- a/docs/tutorials/pt/wix-suiteshare.md
+++ b/docs/tutorials/pt/wix-suiteshare.md
@@ -19,11 +19,11 @@ Para instalar o script do VTEX Assisted Sales (SuiteShare) no seu site do Wix, 
 
 Para isso, você deve acessar seu painel do Wix e clicar em **_Configurações > Acompanhamento e Análises_**.
 
-![Wix_1](https://images.ctfassets.net/alneenqid6w5/7H7h9u61B7hV52gAJlzOtv/bf8fb87c8ee103a11575009809a83510/Wix_1.png)
+![Wix_1](//images.ctfassets.net/alneenqid6w5/7H7h9u61B7hV52gAJlzOtv/bf8fb87c8ee103a11575009809a83510/Wix_1.png)
 
 Na janela que será aberta, o próximo passo é clicar em **_Nova Ferramenta > Personalizado_**.
 
-![Wix_2](https://images.ctfassets.net/alneenqid6w5/26eIVGEMNUEfq9FmPzE2T1/46e34a3251d12d5471d45d37d2cffa81/Wix_2.png)
+![Wix_2](//images.ctfassets.net/alneenqid6w5/26eIVGEMNUEfq9FmPzE2T1/46e34a3251d12d5471d45d37d2cffa81/Wix_2.png)
 
 Preencha então os seguintes campos:
 - **Cole o trecho do código aqui**: insira seu código de instalação (script) do VTEX Assisted Sales (SuiteShare).
@@ -33,7 +33,7 @@ Preencha então os seguintes campos:
 
 Salve a nova configuração.
 
-![Wix_3](https://images.ctfassets.net/alneenqid6w5/1HQbRhPZamrTy4qwMtR1iM/0b9835329e68004479cf4d8cf49212a9/Wix_3.png)
+![Wix_3](//images.ctfassets.net/alneenqid6w5/1HQbRhPZamrTy4qwMtR1iM/0b9835329e68004479cf4d8cf49212a9/Wix_3.png)
 
 Pronto! Agora o chat do VTEX Assisted Sales (SuiteShare) estará disponível no seu site do Wix.
 
diff --git a/docs/tutorials/pt/wordpress-suiteshare.md b/docs/tutorials/pt/wordpress-suiteshare.md
index cec286bd8..eb76d4478 100644
--- a/docs/tutorials/pt/wordpress-suiteshare.md
+++ b/docs/tutorials/pt/wordpress-suiteshare.md
@@ -21,14 +21,14 @@ Após realizar o download, você deve acessar seu wordpress clicar em: **Plugin
 
 Selecione o arquivo que você acabou de fazer download e instale.
 
-![Wordpress 1](https://images.ctfassets.net/alneenqid6w5/1QRLLMPv7aDIYIxyJ8wIoC/93e8387838b2f916cd5dc1b9097def28/Screenshot_2022-08-30_at_12-00-57_Wordpress.png)
+![Wordpress 1](//images.ctfassets.net/alneenqid6w5/1QRLLMPv7aDIYIxyJ8wIoC/93e8387838b2f916cd5dc1b9097def28/Screenshot_2022-08-30_at_12-00-57_Wordpress.png)
 
 O próximo passo é clicar em **Plugins** no menu do seu Wordpress e ativar o plugin do VTEX Assisted Sales (SuiteShare).
 
-![Wordpress 2](https://images.ctfassets.net/alneenqid6w5/1BUOMxdFlKQYcUmNqNxZ7j/8c1e91fdb619bfe0033cccf3d2e6e638/Screenshot_2022-08-30_at_12-01-02_Wordpress.png)
+![Wordpress 2](//images.ctfassets.net/alneenqid6w5/1BUOMxdFlKQYcUmNqNxZ7j/8c1e91fdb619bfe0033cccf3d2e6e638/Screenshot_2022-08-30_at_12-01-02_Wordpress.png)
 
 Por fim, após o plugin devidamente instalado e ativado só precisamos acessar **Configurações** -> **VTEX Assisted Sales (SuiteShare)**, aqui você deve marcar a opção **Ativar Plugin** e também preencher o campo token com o seu token: 
 
-![Wordpress 3](https://images.ctfassets.net/alneenqid6w5/63DIufRLNRJQws24szLTS1/839c6cfd2e7b5523baaebca1c7831cb0/Screenshot_2022-08-30_at_12-01-08_Wordpress.png)
+![Wordpress 3](//images.ctfassets.net/alneenqid6w5/63DIufRLNRJQws24szLTS1/839c6cfd2e7b5523baaebca1c7831cb0/Screenshot_2022-08-30_at_12-01-08_Wordpress.png)
 
 Agora se você já configurou um Chat, CTA ou Widget aqui na Suiteshare, ele irá começar a ser exibido no seu Wordpress.
diff --git a/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md b/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md
index e260f0eb2..53e85ae97 100644
--- a/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md
+++ b/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md
@@ -1,15 +1,15 @@
 ---
-title: 'Como escrever um ticket completo para o suporte VTEX'
+title: 'Boas práticas para a abertura de um ticket para o Suporte VTEX'
 id: 6u4ehk6F0ksuDgYuCbFDRX
 status: PUBLISHED
 createdAt: 2023-03-23T22:00:24.560Z
-updatedAt: 2023-03-24T18:24:48.580Z
-publishedAt: 2023-03-24T18:24:48.580Z
+updatedAt: 2024-04-22T23:02:06.481Z
+publishedAt: 2024-04-22T23:02:06.481Z
 firstPublishedAt: 2023-03-23T22:57:50.828Z
 contentType: tutorial
 productTeam: Others
 author: 46G4yHIZerH7B9Jo0Iw5KI
-slug: como-escrever-um-ticket-completo-para-o-suporte-vtex
+slug: boas-praticas-para-a-abertura-de-um-ticket-para-o-suporte-vtex
 locale: pt
 legacySlug: como-escrever-um-ticket-completo-para-o-suporte-vtex
 subcategory: 1VvCpaa8NCA6a0MK6W6oWg
@@ -19,18 +19,58 @@ Todos os clientes e parceiros têm acesso a atendimento fornecido pelo time de e
 
 Os especialistas estão preparados para proporcionar a melhor experiência possível para a solução dos chamados. Porém, para garantir um atendimento mais rápido e objetivo, existem algumas orientações que devem ser seguidas durante a abertura do ticket. 
 
-Lembre-se que, quanto mais contexto os especialistas tiverem, mais rápido será possível chegar a uma resolução para o problema. 
+Lembre-se que, quanto mais contexto os especialistas tiverem, mais rápido será possível chegar a uma resolução para o problema.
 
-Este artigo orienta os clientes e parceiros a abrirem os tickets com informações relevantes para agilizar o processo de investigação dos nossos especialistas. Ele está dividido nas seguintes seções:
+Este artigo orienta clientes e parceiros VTEX a abrirem tickets com informações relevantes para agilizar o processo de investigação dos nossos especialistas e alcançar mais rapidamente a solução do seu problema. Ele está dividido nas seguintes seções:
 
-- [Orientações gerais](#orientacoes-gerais)
-- [Informações relevantes por cenário](#informacoes-relevantes-por-cenario)
+- [Antes de abrir um ticket](#Antes-de-abrir-um-ticket)
+- [Preenchendo um ticket](#preenchendo-um-ticket)
 
 Para saber como abrir um chamado na VTEX, leia o artigo [Abrir chamados para o suporte VTEX](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-## Orientações gerais
+## Antes de abrir um ticket
 
-Para que um ticket esteja preenchido de forma completa, é necessário seguir algumas orientações:
+Antes de abrir um ticket, confira se o problema está relacionado às customizações da loja. Se a origem do problema for uma customização, você precisará entrar em contato com a sua equipe responsável pela customização. Caso contrário, abra um ticket no suporte VTEX. 
+
+### Carrinho, Checkout e lojas em CMS
+
+É importante validar se o cenário ocorre sem customização da loja. Para realizar este teste, desative as customizações (JS e CSS) e tente reproduzir o erro. Saiba como fazer isso com o artigo [Como bloquear customizações para investigar problemas no front-end da loja](https://help.vtex.com/pt/faq/como-bloquear-customizacoes-para-investigar-problemas-no-front-end-da-loja--5c1a4bvVK8rAvKLczhkCnY). Caso o erro persista, entre em contato com o [nosso Suporte](https://help.vtex.com/support?/cultureInfo=pt-br). 
+
+### Store Framework
+
+Para verificar se o problema está associado ao IO siga os passos abaixo:
+
+1. Abra o prompt de comando e faça login na sua loja, utilizando a <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">VTEX IO CLI</a>.
+2. Acesse um workspace de desenvolvimento, rodando o seguinte comando:
+    ```
+    vtex use {workspace}
+     ```
+3. Se a sua loja possui um tema do Store Framework instalado, desinstale usando o comando abaixo:  
+      ```
+    vtex uninstall {tema}
+     ```
+    <div class="alert alert-info">
+    Você pode conferir se existe algum tema instalado usando o comando <code>vtex list</code>, que lista todos os aplicativos instalados na loja.
+    </div>
+4. Clone o tema padrão do Store Framework no seu computador.
+5. No prompt de comando, acesse a pasta do tema padrão.
+6. Rode o comando:
+    ```
+    vtex link
+    ```
+   <div class="alert alert-warning"> Se a sua loja não possui o aplicativo Reviews and Ratings instalado, você pode receber um erro ao tentar linkar. Para evitar isso, remova este app da lista de `peer dependencies` do arquivo `manifest.json` do tema padrão.   </div>
+7. Acesse a frente de loja relativa ao seu workspace, usando a URL:
+    ```
+    https://{workspace}--{accountName}.myvtex.com
+    ```
+
+8. Tente reproduzir o erro.
+
+Se o erro não acontece após o bloqueio dos arquivos ou no tema padrão do Store Framework, significa que o erro é relacionado às customizações presentes no site e para a resolução, você deve entrar em contato com a equipe responsável pelo frontend da sua loja.
+
+## Preenchendo um ticket  
+
+Se o erro persistir, abra um ticket para o time VTEX seguindo as orientações da tabela abaixo. 
 
 | Informações | Orientações |
 | ----------- | ----------- |
@@ -41,7 +81,7 @@ Para que um ticket esteja preenchido de forma completa, é necessário seguir al
 | Escopo do ticket | <p> - Não enderece mais de um problema no mesmo ticket. </p> <p> - Não crie mais de um ticket para o mesmo problema. </p> |
 | Prioridade | Verifique a [prioridade](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9#prioridade-de-chamados) correta de acordo com  a natureza do problema, para que o [SLA](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9#disponibilidade-e-sla-de-atendimento) correto seja aplicado. |
 
-## Informações relevantes por cenário
+### Informações relevantes por cenário
 
 Existem vários cenários que podem levar à abertura de um ticket. Nessa seção, serão elencados os cenários mais comuns com informações básicas necessárias para abertura do ticket em cada cenário.
 
@@ -49,9 +89,9 @@ Você pode adaptar essas informações ao seu cenário específico e também us
 
 | Cenários | Informações |
 | ----------- | ----------- |
-| Pedidos | <p> - ID do pedido ou do <code> orderForm </code>. </p> <p> - URL do pedido no <strong> Gerenciamento de pedidos </strong> ou no <strong> Bridge </strong> (em casos de pedidos de marketplaces com integrações nativas). </p> |
-| Checkout | <p> - URL do carrinho gerado pelo <a href="https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451">Cartman</a>. </p> <p> - IDs dos SKUs e CEP para reprodução do carrinho. </p>
-| Logística | <p> - ID do seller. </p> <p> - URL de estoque, doca ou transportadora do seller. </p> <p> - Informações para simular entrega, como IDs dos SKUs e CEP </p> |
+| Pedidos | <p> - ID do pedido ou do <code>orderForm </code>. </p> <p> - URL do pedido no <strong> Gerenciamento de pedidos </strong> ou no <strong> Bridge </strong> (em casos de pedidos de marketplaces com integrações nativas). </p> |
+| Checkout | <p> - URL do carrinho gerado pelo <a href="https://help.vtex.com/pt/tutorial/configurar-o-cartman--1ACMTStZYkMqB0lTgwg451">Cartman</a>. </p> <p> - IDs dos SKUs e CEP para reprodução do carrinho. </p> <p> - <a href="https://help.vtex.com/pt/tutorial/generating-a-har-file--15xVlw8nuakk2k6Cao4k2Q">HAR</a>. </p>
+| Logística | <p> - ID do seller. </p> <p> - URL de estoque, doca ou transportadora do seller. </p> <p> - Informações para simular entrega, como IDs dos SKUs e CEP.</p> |
 | Pagamentos | <p> - ID da transação. </p> <p> - Link da transação, acessando no Admin VTEX <em> Pagamentos > Transações. </em> </p>
 | VTEX IO | <p> - Nome e versão do aplicativo utilizado. </p> <p> - Workspace utilizado. </p> <p> - Arquivo ZIP com o <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-3-settingyourstoretheme">store-theme</a> em caso de tema linkado e não instalado. </p> |
 | Promoções | <p> - Nome da promoção. </p> <p> - URL da promoção. </p> <p> - Produto e CEP aplicáveis à promoção para testes. </p> |
@@ -60,5 +100,5 @@ Você pode adaptar essas informações ao seu cenário específico e também us
 #### Saiba mais
 
 - [Abrir chamado no suporte VTEX](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM)
-- [Como funciona o suporte da VTEX ?](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe)
+- [Como funciona o suporte da VTEX?](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe)
 - [Suporte VTEX - Brasil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9)
diff --git a/docs/tutorials/pt/zapier-suiteshare.md b/docs/tutorials/pt/zapier-suiteshare.md
index 57e2a7c8f..f8578ce53 100644
--- a/docs/tutorials/pt/zapier-suiteshare.md
+++ b/docs/tutorials/pt/zapier-suiteshare.md
@@ -19,32 +19,32 @@ Para realizar a integração, acesse a plataforma **Zapier** clicando [aqui](htt
 
 Fazendo **login** ou criando uma **conta**.
 
-![Zapier_1](https://images.ctfassets.net/alneenqid6w5/EQrfjNlvuFJMEv38vvptl/dec4fdb4b6c09c6b0ce30f5097226727/Zapier_1.png)
+![Zapier_1](//images.ctfassets.net/alneenqid6w5/EQrfjNlvuFJMEv38vvptl/dec4fdb4b6c09c6b0ce30f5097226727/Zapier_1.png)
 
 Após a criação, personalize sua conta com suas **informações**.
 
-![Zapier_2](https://images.ctfassets.net/alneenqid6w5/4vjr8JP1W1XG9Xzc2HhITd/7c42c60a14c836eeff91041de5f99d15/Zapier_2.png)
+![Zapier_2](//images.ctfassets.net/alneenqid6w5/4vjr8JP1W1XG9Xzc2HhITd/7c42c60a14c836eeff91041de5f99d15/Zapier_2.png)
 
 Depois de configurado, pesquise o **VTEX Assisted Sales (SuiteShare)** nos aplicativos do **Zapier**.
 
 E conclua a configuração no **botão inferior**.
 
-![Zapier_3](https://images.ctfassets.net/alneenqid6w5/1sF6axf20MhMIxzklT9mbi/7a148a23418c84341f97240ab1576c83/Zapier_3.png)
+![Zapier_3](//images.ctfassets.net/alneenqid6w5/1sF6axf20MhMIxzklT9mbi/7a148a23418c84341f97240ab1576c83/Zapier_3.png)
 
 Crie seu fluxo de integração adicionando o **VTEX Assisted Sales (SuiteShare)** e a outra plataforma que desejar, e configure a ação que a integração fará.
 
-![Zapier_4](https://images.ctfassets.net/alneenqid6w5/zfjtW84RbUzLM93CbmX2M/57c15b87bcb4e050986f07a00ba06c1b/Zapier_4.png)
+![Zapier_4](//images.ctfassets.net/alneenqid6w5/zfjtW84RbUzLM93CbmX2M/57c15b87bcb4e050986f07a00ba06c1b/Zapier_4.png)
 
 Clique em **iniciar**.
 
-![Zapier_5](https://images.ctfassets.net/alneenqid6w5/5jfRBJCFsW9XGErRInbWMh/fb77fd84708e430ca51969f2e2d85b0a/Zapier_5.png)
+![Zapier_5](//images.ctfassets.net/alneenqid6w5/5jfRBJCFsW9XGErRInbWMh/fb77fd84708e430ca51969f2e2d85b0a/Zapier_5.png)
 
 Clique em **conectar** para acessar sua conta **VTEX Assisted Sales (SuiteShare)**.
 
-![Zapier_6](https://images.ctfassets.net/alneenqid6w5/3Pl48zsf6uJhKhL73E5GYN/d5b4de316a721a92a8306920f2af46a9/Zapier_6.png)
+![Zapier_6](//images.ctfassets.net/alneenqid6w5/3Pl48zsf6uJhKhL73E5GYN/d5b4de316a721a92a8306920f2af46a9/Zapier_6.png)
 
 Forneça seu email **VTEX Assisted Sales (SuiteShare)** e sua senha para realizar a **conexão**.
 
-![Zapier_7](https://images.ctfassets.net/alneenqid6w5/7vbkoNnBLR8SYBG6mQireN/45eef9978e5715ff671c3dc06f0743e9/Zapier_7.png)
+![Zapier_7](//images.ctfassets.net/alneenqid6w5/7vbkoNnBLR8SYBG6mQireN/45eef9978e5715ff671c3dc06f0743e9/Zapier_7.png)
 
 Pronto! Após o login, sua integração está pronta para ser utilizada!

From 12b51552cc9df75cc70cb2671e414ca2a4c71e3d Mon Sep 17 00:00:00 2001
From: PedroAntunesCosta <47991446+PedroAntunesCosta@users.noreply.github.com>
Date: Fri, 2 Aug 2024 22:32:41 -0300
Subject: [PATCH 02/13] correcting images urls

---
 ...s-pagespeed-insights-in-your-vtex-admin.md |  2 +-
 .../en/admin-disponivel-em-japones.md         |  2 +-
 ...ion-will-now-be-restricted-by-user-role.md |  2 +-
 ...to-simplify-product-customization-teste.md |  2 +-
 ...w-app-to-simplify-product-customization.md |  2 +-
 ...lment-operation-with-vtex-pick-and-pack.md |  2 +-
 ...option-when-configuring-target-audience.md |  2 +-
 .../en/catalogs-new-visual-and-navigation.md  |  8 ++--
 ...ed-actions-available-to-the-master-user.md |  2 +-
 ...ing-up-the-cardholder-document-id-field.md |  2 +-
 .../en/coupon-experience-improvements.md      |  4 +-
 ...displaying-pickup-points-on-google-maps.md |  2 +-
 ...before-activating-it-to-ensure-security.md |  2 +-
 ...efore-activating-it-to-ensure-security1.md |  2 +-
 ...rs-with-the-new-reviews-and-ratings-app.md |  2 +-
 ...trol-on-your-order-authorization-screen.md |  2 +-
 ...xpand-your-operation-through-vtex-admin.md |  4 +-
 ...-and-google-login-settings-have-changed.md |  2 +-
 ...t-your-conversion-with-the-new-checkout.md |  4 +-
 ...ty-with-the-updated-price-table-feature.md |  2 +-
 .../get-to-know-the-new-vtex-status-page.md   |  2 +-
 ...ck-friday-with-our-best-practices-guide.md |  2 +-
 ...ason-with-our-best-practices-guide-2022.md |  2 +-
 ...ay-new-payment-method-available-on-vtex.md |  2 +-
 ...le-shopping-new-option-to-submit-prices.md |  4 +-
 ...dless-cms-create-non-duplicatable-pages.md |  2 +-
 ...r-insights-into-page-publication-status.md |  2 +-
 ...t-creation-and-management-with-projects.md |  4 +-
 ...y-informed-on-your-publication-progress.md |  4 +-
 ...nt-of-discount-price-viewing-experience.md |  8 ++--
 ...nts-in-exporting-prices-via-spreadsheet.md |  2 +-
 ...nts-to-unified-search-in-vtex-sales-app.md |  2 +-
 ...s-with-a-new-order-authorization-screen.md |  2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |  2 +-
 ...-emails-containing-access-code-requests.md |  2 +-
 ...-configuring-shipping-time-at-sku-level.md |  4 +-
 ...g-the-vtex-app-to-broadcast-live-events.md |  4 +-
 ...-for-credit-and-debit-cards-at-checkout.md |  2 +-
 ...rketplace-improvements-on-received-skus.md |  2 +-
 .../marketplace-network-has-been-improved.md  |  2 +-
 .../marketplace-new-offer-quality-filters.md  |  2 +-
 ...e-new-sidebar-with-received-sku-details.md |  2 +-
 ...-and-integrations-are-now-a-single-page.md |  2 +-
 .../en/marketplaces-received-skus-beta.md     |  6 +--
 ...er-data-v1-dynamic-settings-deprecation.md |  4 +-
 ...ice-per-item-promotion-will-be-disabled.md |  2 +-
 ...ew-interface-for-mapping-categories-and.md |  2 +-
 ...tion-new-promotion-management-interface.md |  2 +-
 ...tenacao-reduz-erros-no-envio-de-e-mails.md |  6 +--
 .../en/multi-currency-gift-card.md            |  2 +-
 ...my-authentication-section-in-my-account.md | 16 +++----
 ...-data-in-store-overview-beta-admin-page.md |  2 +-
 .../en/new-indexation-history-screen.md       |  2 +-
 .../new-orders-module-interface-official.md   |  6 +--
 ...der-and-anti-fraud-management-interface.md |  2 +-
 ...manage-your-promotions-more-efficiently.md |  2 +-
 docs/announcements/en/new-roles-page.md       |  2 +-
 .../en/new-sales-performance-dashboard.md     |  2 +-
 .../en/new-sku-bindings-interface.md          |  2 +-
 .../en/new-subscriptions-module.md            | 16 +++----
 ...or-the-admins-user-management-dashboard.md |  2 +-
 ...vo-layout-no-e-mail-de-codigo-de-acesso.md |  2 +-
 ...r-pickup-points-for-subscription-orders.md |  2 +-
 ...for-integrations-with-vtex-marketplaces.md |  2 +-
 ...ores-my-account-page-will-change-review.md |  2 +-
 .../price-filters-more-search-flexibility.md  |  2 +-
 ...ontinued-update-your-store-by-september.md |  2 +-
 ...tand-the-promotions-applied-to-the-cart.md |  2 +-
 .../en/rate-vtexs-service-in-your-admin.md    |  2 +-
 ...rderform-configuration-for-all-requests.md |  2 +-
 .../en/redesigned-products-and-skus-page.md   |  2 +-
 ...-pickup-points-is-now-easier-and-faster.md |  2 +-
 .../en/reusing-images-in-site-editor.md       |  2 +-
 .../en/sales-performance-dashboard-updates.md |  2 +-
 ...stored-information-for-future-purchases.md |  2 +-
 ...le-content-publication-with-site-editor.md |  2 +-
 ...earch-filters-in-instores-endless-aisle.md |  2 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |  2 +-
 ...grates-your-business-to-google-shopping.md |  2 +-
 ...eady-with-our-best-practices-guide-2023.md |  2 +-
 ...ling-share-instore-carts-using-qr-codes.md |  2 +-
 .../social-selling-share-your-instore-cart.md |  4 +-
 ...t-page-will-change-review-your-settings.md |  2 +-
 ...laced-by-the-term-role-in-your-admin-ui.md |  2 +-
 ...-and-security-with-the-new-audit-module.md |  2 +-
 .../update-grants-in-the-promotions-module.md |  2 +-
 ...ustomers-abandoning-their-shopping-cart.md |  2 +-
 ...rovements-at-checkout-for-expired-cards.md |  2 +-
 ...w-visual-editor-for-merchandising-rules.md |  2 +-
 .../vtex-io-documentation-has-a-new-home.md   |  4 +-
 ...ow-available-in-dutch-french-and-korean.md |  2 +-
 .../en/vtex-login-now-features-recaptcha.md   |  2 +-
 .../en/vtex-marketplace-launches-in-2022.md   |  6 +--
 .../en/we-released-the-new-order-placed.md    |  4 +-
 ...elcome-to-the-redesigned-vtex-admin-new.md |  2 +-
 ...nching-your-personal-data-set-up-screen.md |  2 +-
 ...ist-discover-the-new-vtex-app-store-app.md |  2 +-
 ...ss-to-the-settings-screen-on-the-orders.md |  4 +-
 ...s-pagespeed-insights-in-your-vtex-admin.md |  2 +-
 .../es/admin-disponivel-em-japones.md         |  2 +-
 ...ion-will-now-be-restricted-by-user-role.md |  2 +-
 ...to-simplify-product-customization-teste.md |  2 +-
 ...w-app-to-simplify-product-customization.md |  2 +-
 ...lment-operation-with-vtex-pick-and-pack.md |  2 +-
 ...option-when-configuring-target-audience.md |  2 +-
 .../es/catalogs-new-visual-and-navigation.md  |  8 ++--
 ...ed-actions-available-to-the-master-user.md |  2 +-
 ...ing-up-the-cardholder-document-id-field.md |  2 +-
 .../es/coupon-experience-improvements.md      |  4 +-
 ...s-with-the-new-card-level-functionality.md |  2 +-
 ...displaying-pickup-points-on-google-maps.md |  2 +-
 ...before-activating-it-to-ensure-security.md |  2 +-
 ...efore-activating-it-to-ensure-security1.md |  2 +-
 ...rs-with-the-new-reviews-and-ratings-app.md |  2 +-
 ...trol-on-your-order-authorization-screen.md |  2 +-
 ...xpand-your-operation-through-vtex-admin.md |  4 +-
 ...-and-google-login-settings-have-changed.md |  2 +-
 ...t-your-conversion-with-the-new-checkout.md |  4 +-
 ...ty-with-the-updated-price-table-feature.md |  2 +-
 .../get-to-know-the-new-vtex-status-page.md   |  2 +-
 ...ck-friday-with-our-best-practices-guide.md |  2 +-
 ...ason-with-our-best-practices-guide-2022.md |  2 +-
 ...ay-new-payment-method-available-on-vtex.md |  2 +-
 ...le-shopping-new-option-to-submit-prices.md |  4 +-
 ...dless-cms-create-non-duplicatable-pages.md |  2 +-
 ...r-insights-into-page-publication-status.md |  2 +-
 ...t-creation-and-management-with-projects.md |  4 +-
 ...y-informed-on-your-publication-progress.md |  4 +-
 ...nt-of-discount-price-viewing-experience.md |  8 ++--
 ...nts-in-exporting-prices-via-spreadsheet.md |  2 +-
 ...nts-to-unified-search-in-vtex-sales-app.md |  2 +-
 ...s-with-a-new-order-authorization-screen.md |  2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |  2 +-
 ...-emails-containing-access-code-requests.md |  2 +-
 ...-configuring-shipping-time-at-sku-level.md |  4 +-
 ...g-the-vtex-app-to-broadcast-live-events.md |  4 +-
 ...-for-credit-and-debit-cards-at-checkout.md |  2 +-
 ...rketplace-improvements-on-received-skus.md |  2 +-
 .../marketplace-network-has-been-improved.md  |  2 +-
 .../marketplace-new-offer-quality-filters.md  |  2 +-
 ...e-new-sidebar-with-received-sku-details.md |  2 +-
 ...-and-integrations-are-now-a-single-page.md |  2 +-
 .../es/marketplaces-received-skus-beta.md     |  6 +--
 ...er-data-v1-dynamic-settings-deprecation.md |  4 +-
 ...ice-per-item-promotion-will-be-disabled.md |  2 +-
 ...ew-interface-for-mapping-categories-and.md |  2 +-
 ...tion-new-promotion-management-interface.md |  2 +-
 ...tenacao-reduz-erros-no-envio-de-e-mails.md |  6 +--
 .../es/multi-currency-gift-card.md            |  2 +-
 ...my-authentication-section-in-my-account.md | 16 +++----
 ...-data-in-store-overview-beta-admin-page.md |  2 +-
 .../es/new-indexation-history-screen.md       |  2 +-
 .../new-orders-module-interface-official.md   |  6 +--
 ...der-and-anti-fraud-management-interface.md |  2 +-
 ...manage-your-promotions-more-efficiently.md |  2 +-
 docs/announcements/es/new-roles-page.md       |  2 +-
 .../es/new-sales-performance-dashboard.md     |  2 +-
 .../es/new-sku-bindings-interface.md          |  2 +-
 .../es/new-subscriptions-module.md            | 16 +++----
 ...or-the-admins-user-management-dashboard.md |  2 +-
 ...vo-layout-no-e-mail-de-codigo-de-acesso.md |  2 +-
 ...r-pickup-points-for-subscription-orders.md |  2 +-
 ...for-integrations-with-vtex-marketplaces.md |  2 +-
 ...ores-my-account-page-will-change-review.md |  2 +-
 .../price-filters-more-search-flexibility.md  |  2 +-
 ...ontinued-update-your-store-by-september.md |  2 +-
 ...tand-the-promotions-applied-to-the-cart.md |  2 +-
 .../es/rate-vtexs-service-in-your-admin.md    |  2 +-
 ...rderform-configuration-for-all-requests.md |  2 +-
 .../es/redesigned-products-and-skus-page.md   |  2 +-
 ...-pickup-points-is-now-easier-and-faster.md |  2 +-
 .../es/reusing-images-in-site-editor.md       |  2 +-
 .../es/sales-performance-dashboard-updates.md |  2 +-
 ...stored-information-for-future-purchases.md |  2 +-
 ...le-content-publication-with-site-editor.md |  2 +-
 ...earch-filters-in-instores-endless-aisle.md |  2 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |  2 +-
 ...grates-your-business-to-google-shopping.md |  2 +-
 ...eady-with-our-best-practices-guide-2023.md |  2 +-
 ...ling-share-instore-carts-using-qr-codes.md |  2 +-
 .../social-selling-share-your-instore-cart.md |  4 +-
 ...t-page-will-change-review-your-settings.md |  2 +-
 ...-and-security-with-the-new-audit-module.md |  2 +-
 .../update-grants-in-the-promotions-module.md |  2 +-
 ...ustomers-abandoning-their-shopping-cart.md |  2 +-
 ...rovements-at-checkout-for-expired-cards.md |  2 +-
 ...w-visual-editor-for-merchandising-rules.md |  2 +-
 .../vtex-io-documentation-has-a-new-home.md   |  4 +-
 ...ow-available-in-dutch-french-and-korean.md |  2 +-
 .../es/vtex-login-now-features-recaptcha.md   |  2 +-
 .../es/vtex-marketplace-launches-in-2022.md   |  6 +--
 .../es/we-released-the-new-order-placed.md    |  4 +-
 ...elcome-to-the-redesigned-vtex-admin-new.md |  2 +-
 ...nching-your-personal-data-set-up-screen.md |  2 +-
 ...ist-discover-the-new-vtex-app-store-app.md |  2 +-
 ...ss-to-the-settings-screen-on-the-orders.md |  4 +-
 ...s-pagespeed-insights-in-your-vtex-admin.md |  2 +-
 .../pt/admin-disponivel-em-japones.md         |  2 +-
 ...ion-will-now-be-restricted-by-user-role.md |  2 +-
 ...to-simplify-product-customization-teste.md |  2 +-
 ...w-app-to-simplify-product-customization.md |  2 +-
 ...ome-an-expert-in-vtex-with-training-day.md |  2 +-
 ...lment-operation-with-vtex-pick-and-pack.md |  2 +-
 ...option-when-configuring-target-audience.md |  2 +-
 .../pt/catalogs-new-visual-and-navigation.md  |  8 ++--
 ...ed-actions-available-to-the-master-user.md |  2 +-
 ...ing-up-the-cardholder-document-id-field.md |  2 +-
 .../pt/coupon-experience-improvements.md      |  4 +-
 ...s-with-the-new-card-level-functionality.md |  2 +-
 ...displaying-pickup-points-on-google-maps.md |  2 +-
 ...before-activating-it-to-ensure-security.md |  2 +-
 ...efore-activating-it-to-ensure-security1.md |  2 +-
 ...rs-with-the-new-reviews-and-ratings-app.md |  2 +-
 ...trol-on-your-order-authorization-screen.md |  2 +-
 ...xpand-your-operation-through-vtex-admin.md |  4 +-
 ...-and-google-login-settings-have-changed.md |  2 +-
 ...t-your-conversion-with-the-new-checkout.md |  4 +-
 ...ty-with-the-updated-price-table-feature.md |  2 +-
 .../get-to-know-the-new-vtex-status-page.md   |  2 +-
 ...ck-friday-with-our-best-practices-guide.md |  2 +-
 ...ason-with-our-best-practices-guide-2022.md |  2 +-
 ...ay-new-payment-method-available-on-vtex.md |  2 +-
 ...le-shopping-new-option-to-submit-prices.md |  4 +-
 ...dless-cms-create-non-duplicatable-pages.md |  2 +-
 ...r-insights-into-page-publication-status.md |  2 +-
 ...t-creation-and-management-with-projects.md |  4 +-
 ...y-informed-on-your-publication-progress.md |  4 +-
 ...nt-of-discount-price-viewing-experience.md |  8 ++--
 ...nts-in-exporting-prices-via-spreadsheet.md |  2 +-
 ...nts-to-unified-search-in-vtex-sales-app.md |  2 +-
 ...s-with-a-new-order-authorization-screen.md |  2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |  2 +-
 .../pt/introducing-vtex-ad-network-beta.md    |  4 +-
 ...-emails-containing-access-code-requests.md |  2 +-
 ...-configuring-shipping-time-at-sku-level.md |  4 +-
 ...g-the-vtex-app-to-broadcast-live-events.md |  4 +-
 ...-for-credit-and-debit-cards-at-checkout.md |  2 +-
 ...rketplace-improvements-on-received-skus.md |  2 +-
 .../marketplace-network-has-been-improved.md  |  2 +-
 .../marketplace-new-offer-quality-filters.md  |  2 +-
 ...e-new-sidebar-with-received-sku-details.md |  2 +-
 ...-and-integrations-are-now-a-single-page.md |  2 +-
 .../pt/marketplaces-received-skus-beta.md     |  6 +--
 ...er-data-v1-dynamic-settings-deprecation.md |  4 +-
 ...ice-per-item-promotion-will-be-disabled.md |  2 +-
 ...ew-interface-for-mapping-categories-and.md |  2 +-
 ...tion-new-promotion-management-interface.md |  2 +-
 ...tenacao-reduz-erros-no-envio-de-e-mails.md |  6 +--
 .../pt/multi-currency-gift-card.md            |  2 +-
 ...my-authentication-section-in-my-account.md | 16 +++----
 ...-data-in-store-overview-beta-admin-page.md |  2 +-
 .../pt/new-indexation-history-screen.md       |  2 +-
 .../new-orders-module-interface-official.md   |  6 +--
 ...der-and-anti-fraud-management-interface.md |  2 +-
 ...manage-your-promotions-more-efficiently.md |  2 +-
 docs/announcements/pt/new-roles-page.md       |  2 +-
 .../pt/new-sales-performance-dashboard.md     |  2 +-
 .../pt/new-sku-bindings-interface.md          |  2 +-
 .../pt/new-subscriptions-module.md            | 16 +++----
 ...or-the-admins-user-management-dashboard.md |  2 +-
 ...vo-layout-no-e-mail-de-codigo-de-acesso.md |  2 +-
 ...r-pickup-points-for-subscription-orders.md |  2 +-
 ...for-integrations-with-vtex-marketplaces.md |  2 +-
 ...ores-my-account-page-will-change-review.md |  2 +-
 .../price-filters-more-search-flexibility.md  |  2 +-
 ...ontinued-update-your-store-by-september.md |  2 +-
 ...tand-the-promotions-applied-to-the-cart.md |  2 +-
 .../pt/rate-vtexs-service-in-your-admin.md    |  2 +-
 ...rderform-configuration-for-all-requests.md |  2 +-
 .../pt/redesigned-products-and-skus-page.md   |  2 +-
 ...-pickup-points-is-now-easier-and-faster.md |  2 +-
 .../pt/reusing-images-in-site-editor.md       |  2 +-
 .../pt/sales-performance-dashboard-updates.md |  2 +-
 ...stored-information-for-future-purchases.md |  2 +-
 ...le-content-publication-with-site-editor.md |  2 +-
 ...earch-filters-in-instores-endless-aisle.md |  2 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |  2 +-
 ...grates-your-business-to-google-shopping.md |  2 +-
 ...eady-with-our-best-practices-guide-2023.md |  2 +-
 ...ling-share-instore-carts-using-qr-codes.md |  2 +-
 .../social-selling-share-your-instore-cart.md |  4 +-
 ...t-page-will-change-review-your-settings.md |  2 +-
 ...-and-security-with-the-new-audit-module.md |  2 +-
 .../untitled-entry-2021-01-19-at-17-22-53.md  |  2 +-
 .../update-grants-in-the-promotions-module.md |  2 +-
 ...ustomers-abandoning-their-shopping-cart.md |  2 +-
 ...rovements-at-checkout-for-expired-cards.md |  2 +-
 ...w-visual-editor-for-merchandising-rules.md |  2 +-
 .../vtex-io-documentation-has-a-new-home.md   |  4 +-
 ...ow-available-in-dutch-french-and-korean.md |  2 +-
 .../pt/vtex-login-now-features-recaptcha.md   |  2 +-
 .../pt/vtex-marketplace-launches-in-2022.md   |  8 ++--
 .../pt/we-released-the-new-order-placed.md    |  4 +-
 ...elcome-to-the-redesigned-vtex-admin-new.md |  2 +-
 ...nching-your-personal-data-set-up-screen.md |  2 +-
 ...ist-discover-the-new-vtex-app-store-app.md |  2 +-
 ...ss-to-the-settings-screen-on-the-orders.md |  4 +-
 ...-why-is-it-not-working-google-analytics.md |  6 +--
 ...ations-to-troubleshoot-front-end-issues.md | 12 ++---
 ...h-the-best-selling-products-in-my-store.md |  4 +-
 ...iliations-that-support-native-split-faq.md |  2 +-
 ...e-upload-button-is-not-displayed-at-cms.md |  2 +-
 .../en/how-do-i-find-the-order-nsu-and-tid.md |  2 +-
 ...ciate-two-promotions-to-the-same-coupon.md |  4 +-
 ...w-to-configure-mercadopago-transparente.md |  4 +-
 ...o-disable-the-two-factor-authentication.md |  8 ++--
 ...nt-edit-a-required-field-on-master-data.md |  6 +--
 ...calculators-has-been-reached-what-to-do.md |  2 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |  2 +-
 ...-the-site-hasnt-been-updated-what-to-do.md |  4 +-
 ...ook-is-not-displayed-in-the-shop-window.md |  2 +-
 .../nao-encontro-uma-colecao-o-que-fazer.md   |  4 +-
 ...cked-in-ready-for-handling-what-do-i-do.md |  2 +-
 ...iliations-are-highlighted-in-yellow-why.md |  2 +-
 ...r-when-trying-to-process-sku-suggestion.md |  8 ++--
 docs/faq/en/understanding-the-dashboard.md    |  4 +-
 ...understanding-vtex-email-capture-system.md |  2 +-
 .../en/website-with-error-how-to-fix-it.md    |  4 +-
 docs/faq/en/what-are-pre-installed-apps.md    |  2 +-
 .../en/what-deleting-a-sku-seller-means.md    |  2 +-
 .../en/what-delinking-a-sku-seller-means.md   |  2 +-
 .../en/what-is-url-mapping-301-redirect.md    |  4 +-
 ...n-there-are-problems-with-a-transaction.md |  4 +-
 ...exported-report-does-not-reach-my-email.md |  4 +-
 ...n-the-notify-me-option-is-not-displayed.md |  2 +-
 ...-authorize-fulfillment-error-what-to-do.md |  2 +-
 ...y-mercado-pago-transparente-credentials.md |  6 +--
 ...hy-can-t-i-change-the-fields-in-a-group.md |  8 ++--
 ...return-attribution-errors-after-mapping.md | 12 ++---
 ...nt-information-from-the-license-manager.md |  2 +-
 ...nt-my-benefit-work-for-a-client-cluster.md |  2 +-
 ...-benefit-work-for-all-types-of-delivery.md |  2 +-
 ...alize-the-cancellation-of-a-transaction.md |  2 +-
 ...yment-methods-appear-on-the-marketplace.md |  2 +-
 ...en-wrongly-categorized-on-mercado-livre.md |  2 +-
 docs/faq/en/why-is-let-me-know-not-showing.md |  2 +-
 docs/faq/en/why-is-my-freight-value-wrong.md  |  4 +-
 ...product-appearing-in-the-wrong-category.md |  2 +-
 .../en/why-is-my-stores-zoom-not-working.md   |  2 +-
 ...-the-product-not-visible-on-the-website.md | 26 +++++------
 .../why-is-the-thumb-image-of-poor-quality.md |  2 +-
 ...t-the-order-invoiced-on-the-marketplace.md |  2 +-
 ...ilter-bringing-any-result-in-the-search.md |  2 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  2 +-
 .../why-was-the-item-splitted-in-the-cart.md  |  2 +-
 ...s-the-order-closed-with-the-wrong-price.md |  2 +-
 ...heckout-when-the-purchase-was-concluded.md |  2 +-
 ...he-promotion-applied-to-the-marketplace.md |  2 +-
 ...-why-is-it-not-working-google-analytics.md |  6 +--
 ...ations-to-troubleshoot-front-end-issues.md | 12 ++---
 ...iliations-that-support-native-split-faq.md |  2 +-
 ...e-upload-button-is-not-displayed-at-cms.md |  2 +-
 .../es/how-do-i-find-the-order-nsu-and-tid.md |  2 +-
 ...ciate-two-promotions-to-the-same-coupon.md |  4 +-
 ...w-to-configure-mercadopago-transparente.md |  4 +-
 ...o-disable-the-two-factor-authentication.md |  8 ++--
 ...nt-edit-a-required-field-on-master-data.md |  6 +--
 ...calculators-has-been-reached-what-to-do.md |  2 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |  2 +-
 ...-the-site-hasnt-been-updated-what-to-do.md |  4 +-
 ...ook-is-not-displayed-in-the-shop-window.md |  2 +-
 .../nao-encontro-uma-colecao-o-que-fazer.md   |  4 +-
 ...cked-in-ready-for-handling-what-do-i-do.md |  2 +-
 ...iliations-are-highlighted-in-yellow-why.md |  2 +-
 ...r-when-trying-to-process-sku-suggestion.md |  8 ++--
 docs/faq/es/understanding-the-dashboard.md    |  4 +-
 ...understanding-vtex-email-capture-system.md |  2 +-
 .../untitled-entry-2017-09-19-at-09-42-49.md  |  2 +-
 .../es/website-with-error-how-to-fix-it.md    |  4 +-
 .../es/what-deleting-a-sku-seller-means.md    |  2 +-
 .../es/what-delinking-a-sku-seller-means.md   |  2 +-
 ...n-there-are-problems-with-a-transaction.md |  4 +-
 ...exported-report-does-not-reach-my-email.md |  4 +-
 ...n-the-notify-me-option-is-not-displayed.md |  2 +-
 ...-authorize-fulfillment-error-what-to-do.md |  2 +-
 ...y-mercado-pago-transparente-credentials.md |  6 +--
 ...hy-can-t-i-change-the-fields-in-a-group.md |  6 +--
 ...return-attribution-errors-after-mapping.md | 12 ++---
 ...nt-information-from-the-license-manager.md |  2 +-
 ...nt-my-benefit-work-for-a-client-cluster.md |  2 +-
 ...-benefit-work-for-all-types-of-delivery.md |  2 +-
 ...alize-the-cancellation-of-a-transaction.md |  2 +-
 ...yment-methods-appear-on-the-marketplace.md |  2 +-
 ...en-wrongly-categorized-on-mercado-livre.md |  2 +-
 docs/faq/es/why-is-let-me-know-not-showing.md |  2 +-
 docs/faq/es/why-is-my-freight-value-wrong.md  |  4 +-
 ...product-appearing-in-the-wrong-category.md |  2 +-
 .../es/why-is-my-stores-zoom-not-working.md   |  2 +-
 ...-the-product-not-visible-on-the-website.md | 26 +++++------
 .../why-is-the-thumb-image-of-poor-quality.md |  2 +-
 ...t-the-order-invoiced-on-the-marketplace.md |  2 +-
 ...ilter-bringing-any-result-in-the-search.md |  2 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  2 +-
 .../why-was-the-item-splitted-in-the-cart.md  |  2 +-
 ...heckout-when-the-purchase-was-concluded.md |  2 +-
 ...he-promotion-applied-to-the-marketplace.md |  2 +-
 ...-why-is-it-not-working-google-analytics.md |  6 +--
 ...ations-to-troubleshoot-front-end-issues.md |  8 ++--
 ...h-the-best-selling-products-in-my-store.md |  4 +-
 ...iliations-that-support-native-split-faq.md |  2 +-
 ...e-upload-button-is-not-displayed-at-cms.md |  2 +-
 .../pt/how-do-i-find-the-order-nsu-and-tid.md |  2 +-
 ...ciate-two-promotions-to-the-same-coupon.md |  4 +-
 ...w-to-configure-mercadopago-transparente.md |  4 +-
 ...o-disable-the-two-factor-authentication.md |  8 ++--
 docs/faq/pt/how-to-edit-a-whatsapp-link.md    |  2 +-
 docs/faq/pt/how-to-find-facebook-pixel.md     |  6 +--
 .../pt/how-to-find-google-analytics-pixel.md  |  6 +--
 .../how-to-find-google-tag-manager-pixel.md   |  4 +-
 ...nt-edit-a-required-field-on-master-data.md |  6 +--
 ...calculators-has-been-reached-what-to-do.md |  2 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |  2 +-
 ...-the-site-hasnt-been-updated-what-to-do.md |  4 +-
 ...ook-is-not-displayed-in-the-shop-window.md |  2 +-
 docs/faq/pt/locate-the-google-ads-pixel.md    | 10 ++---
 .../nao-encontro-uma-colecao-o-que-fazer.md   |  4 +-
 ...ta-hospedada-e-como-e-a-infra-estrutura.md |  2 +-
 ...cked-in-ready-for-handling-what-do-i-do.md |  2 +-
 ...o-oms-fica-com-quebra-de-linha-no-excel.md |  4 +-
 ...iliations-are-highlighted-in-yellow-why.md |  2 +-
 ...r-when-trying-to-process-sku-suggestion.md |  8 ++--
 docs/faq/pt/understanding-the-dashboard.md    |  4 +-
 ...understanding-vtex-email-capture-system.md |  2 +-
 .../untitled-entry-2017-06-20-at-05-47-41.md  |  2 +-
 .../untitled-entry-2017-07-03-at-18-55-27.md  |  2 +-
 docs/faq/pt/utms.md                           |  4 +-
 .../pt/website-with-error-how-to-fix-it.md    |  4 +-
 docs/faq/pt/what-are-pre-installed-apps.md    |  2 +-
 .../pt/what-deleting-a-sku-seller-means.md    |  2 +-
 .../pt/what-delinking-a-sku-seller-means.md   |  2 +-
 .../pt/what-is-url-mapping-301-redirect.md    |  4 +-
 ...n-there-are-problems-with-a-transaction.md |  4 +-
 ...exported-report-does-not-reach-my-email.md |  4 +-
 ...n-the-notify-me-option-is-not-displayed.md |  2 +-
 ...-authorize-fulfillment-error-what-to-do.md |  2 +-
 ...y-mercado-pago-transparente-credentials.md |  6 +--
 ...hy-can-t-i-change-the-fields-in-a-group.md |  8 ++--
 ...return-attribution-errors-after-mapping.md | 12 ++---
 ...duct-appear-as-unavailable-at-the-store.md |  4 +-
 ...nt-information-from-the-license-manager.md |  2 +-
 ...nt-my-benefit-work-for-a-client-cluster.md |  2 +-
 ...-benefit-work-for-all-types-of-delivery.md |  2 +-
 ...alize-the-cancellation-of-a-transaction.md |  2 +-
 ...yment-methods-appear-on-the-marketplace.md |  2 +-
 ...en-wrongly-categorized-on-mercado-livre.md |  2 +-
 docs/faq/pt/why-is-let-me-know-not-showing.md |  2 +-
 docs/faq/pt/why-is-my-freight-value-wrong.md  |  4 +-
 ...product-appearing-in-the-wrong-category.md |  2 +-
 .../pt/why-is-my-stores-zoom-not-working.md   |  2 +-
 ...-the-product-not-visible-on-the-website.md | 26 +++++------
 .../why-is-the-thumb-image-of-poor-quality.md |  2 +-
 ...t-the-order-invoiced-on-the-marketplace.md |  2 +-
 ...ilter-bringing-any-result-in-the-search.md |  2 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  2 +-
 .../why-was-the-item-splitted-in-the-cart.md  |  2 +-
 ...heckout-when-the-purchase-was-concluded.md |  2 +-
 ...he-promotion-applied-to-the-marketplace.md |  2 +-
 ...-not-available-when-creating-dictionary.md |  2 +-
 ...n-how-to-improve-section-of-the-catalog.md |  4 +-
 ...culate-during-the-first-hour-of-the-day.md |  2 +-
 ...date-of-deliveries-tracking-by-correios.md |  2 +-
 ...is-not-accessible-through-the-new-admin.md |  2 +-
 ...ting-or-editing-list-type-does-not-work.md |  2 +-
 .../crm-error-when-searching-with-spaces.md   |  4 +-
 ...ative-module-when-performing--cpf-query.md |  4 +-
 ...al-order-value-and-total-products-value.md |  2 +-
 .../en/encoding-error-in-apple-mail-app.md    |  2 +-
 ...er-page-with-special-character-in-value.md |  2 +-
 ...-sellers-to-marketplaces-and-vice-versa.md |  2 +-
 ...en-running-vtex-link-for-the-first-time.md |  2 +-
 ...-for-pickup-points-loading-indefinitely.md |  2 +-
 ...items-with-assembly-options-in-the-cart.md |  2 +-
 .../incorrect-canonical-tag-on-https-pages.md |  2 +-
 ...ctions-when-adding-or-removing-a-filter.md |  2 +-
 ...ve-a-commercial-condition-in-the-seller.md |  4 +-
 ...-app-breaks-other-apps-of-the-same-type.md |  4 +-
 ...s-layout-breaking-without-customization.md |  2 +-
 ...acters-and-causes-problem-in-order-flow.md |  2 +-
 ...of-delivery-times-scheduled-at-checkout.md |  2 +-
 .../en/orders-with-error-sistema-de-perfis.md |  2 +-
 ...played-on-the-orders-managment-timeline.md |  2 +-
 ...kup-point-disregarded-based-on-priority.md |  2 +-
 ...-to-the-searched-zip-codes-availability.md |  2 +-
 .../en/reserved-stock-in-invoiced-orders.md   |  2 +-
 ...t-price-in-outofstock-items-unavailable.md |  2 +-
 ...lection-filter-disregards-searched-term.md |  2 +-
 ...hange-a-main-web-site-generating-errors.md |  4 +-
 ...mation-button-does-not-display-the-data.md |  6 +--
 ...t-consider-items-removed-from-the-order.md |  4 +-
 ...nable-to-delete-templates-on-legacy-cms.md |  4 +-
 ...es-not-update-all-files-in-file-manager.md |  2 +-
 ...experience-some-trouble-on-firefox-89-0.md |  2 +-
 ...inding-with-old-license-manager-details.md |  8 ++--
 ...xpires-the-fixed-price-is-not-reenabled.md |  2 +-
 ...-url-the-price-is-not-correctly-updated.md |  2 +-
 ...-not-available-when-creating-dictionary.md |  2 +-
 ...n-how-to-improve-section-of-the-catalog.md |  4 +-
 ...culate-during-the-first-hour-of-the-day.md |  2 +-
 ...date-of-deliveries-tracking-by-correios.md |  2 +-
 ...is-not-accessible-through-the-new-admin.md |  2 +-
 ...ting-or-editing-list-type-does-not-work.md |  2 +-
 .../crm-error-when-searching-with-spaces.md   |  4 +-
 ...ative-module-when-performing--cpf-query.md |  2 +-
 ...al-order-value-and-total-products-value.md |  2 +-
 .../es/encoding-error-in-apple-mail-app.md    |  2 +-
 ...-sellers-to-marketplaces-and-vice-versa.md |  2 +-
 ...en-running-vtex-link-for-the-first-time.md |  2 +-
 ...-for-pickup-points-loading-indefinitely.md |  2 +-
 ...items-with-assembly-options-in-the-cart.md |  2 +-
 .../incorrect-canonical-tag-on-https-pages.md |  2 +-
 ...ctions-when-adding-or-removing-a-filter.md |  2 +-
 ...ve-a-commercial-condition-in-the-seller.md |  4 +-
 ...-app-breaks-other-apps-of-the-same-type.md |  4 +-
 ...s-layout-breaking-without-customization.md |  2 +-
 ...acters-and-causes-problem-in-order-flow.md |  2 +-
 ...of-delivery-times-scheduled-at-checkout.md |  2 +-
 .../es/orders-with-error-sistema-de-perfis.md |  2 +-
 ...played-on-the-orders-managment-timeline.md |  2 +-
 ...kup-point-disregarded-based-on-priority.md |  2 +-
 ...-to-the-searched-zip-codes-availability.md |  2 +-
 .../es/reserved-stock-in-invoiced-orders.md   |  2 +-
 ...t-price-in-outofstock-items-unavailable.md |  2 +-
 ...lection-filter-disregards-searched-term.md |  2 +-
 ...hange-a-main-web-site-generating-errors.md |  4 +-
 ...mation-button-does-not-display-the-data.md |  6 +--
 ...t-consider-items-removed-from-the-order.md |  4 +-
 ...nable-to-delete-templates-on-legacy-cms.md |  4 +-
 ...es-not-update-all-files-in-file-manager.md |  2 +-
 ...experience-some-trouble-on-firefox-89-0.md |  2 +-
 ...inding-with-old-license-manager-details.md |  8 ++--
 ...xpires-the-fixed-price-is-not-reenabled.md |  2 +-
 ...-url-the-price-is-not-correctly-updated.md |  2 +-
 ...-not-available-when-creating-dictionary.md |  2 +-
 ...n-how-to-improve-section-of-the-catalog.md |  4 +-
 ...culate-during-the-first-hour-of-the-day.md |  2 +-
 ...date-of-deliveries-tracking-by-correios.md |  2 +-
 ...is-not-accessible-through-the-new-admin.md |  2 +-
 ...ting-or-editing-list-type-does-not-work.md |  2 +-
 .../crm-error-when-searching-with-spaces.md   |  4 +-
 ...ative-module-when-performing--cpf-query.md |  4 +-
 ...al-order-value-and-total-products-value.md |  2 +-
 .../pt/encoding-error-in-apple-mail-app.md    |  2 +-
 ...er-page-with-special-character-in-value.md |  2 +-
 ...-sellers-to-marketplaces-and-vice-versa.md |  2 +-
 ...en-running-vtex-link-for-the-first-time.md |  2 +-
 ...y-in-master-data-lead-to-checkout-error.md |  6 +--
 ...-for-pickup-points-loading-indefinitely.md |  2 +-
 ...items-with-assembly-options-in-the-cart.md |  2 +-
 .../pt/inconsistent-shipping-calculator.md    |  2 +-
 .../incorrect-canonical-tag-on-https-pages.md |  2 +-
 ...ctions-when-adding-or-removing-a-filter.md |  2 +-
 ...ve-a-commercial-condition-in-the-seller.md |  4 +-
 ...-app-breaks-other-apps-of-the-same-type.md |  4 +-
 ...s-layout-breaking-without-customization.md |  2 +-
 ...acters-and-causes-problem-in-order-flow.md |  2 +-
 ...of-delivery-times-scheduled-at-checkout.md |  2 +-
 .../pt/orders-with-error-sistema-de-perfis.md |  2 +-
 ...played-on-the-orders-managment-timeline.md |  2 +-
 ...kup-point-disregarded-based-on-priority.md |  2 +-
 ...-to-the-searched-zip-codes-availability.md |  2 +-
 .../pt/reserved-stock-in-invoiced-orders.md   |  2 +-
 ...t-price-in-outofstock-items-unavailable.md |  2 +-
 ...lection-filter-disregards-searched-term.md |  2 +-
 ...hange-a-main-web-site-generating-errors.md |  4 +-
 ...mation-button-does-not-display-the-data.md |  6 +--
 ...t-consider-items-removed-from-the-order.md |  4 +-
 ...nable-to-delete-templates-on-legacy-cms.md |  4 +-
 ...es-not-update-all-files-in-file-manager.md |  2 +-
 ...experience-some-trouble-on-firefox-89-0.md |  2 +-
 ...inding-with-old-license-manager-details.md |  8 ++--
 ...xpires-the-fixed-price-is-not-reenabled.md |  2 +-
 ...-url-the-price-is-not-correctly-updated.md |  2 +-
 .../en/access-to-the-customers-last-cart.md   |  2 +-
 docs/tracks/en/accounts-and-architecture.md   |  4 +-
 docs/tracks/en/add-on-products.md             | 16 +++----
 docs/tracks/en/add-pickup-points.md           |  2 +-
 docs/tracks/en/add-sku-specifications.md      |  8 ++--
 docs/tracks/en/adding-a-loading-dock.md       |  2 +-
 .../adding-extra-text-to-the-order-print.md   |  4 +-
 .../tracks/en/adding-new-stores-to-instore.md |  4 +-
 .../en/adding-product-specifications.md       |  8 ++--
 docs/tracks/en/adding-products.md             |  2 +-
 docs/tracks/en/adding-skus.md                 |  6 +--
 docs/tracks/en/adding-vendors.md              |  4 +-
 docs/tracks/en/adding-warehouses.md           |  2 +-
 docs/tracks/en/amazon.md                      |  2 +-
 .../associating-a-template-with-a-layout.md   |  2 +-
 docs/tracks/en/autocomplete-search.md         |  8 ++--
 docs/tracks/en/b2b-form.md                    |  6 +--
 docs/tracks/en/backend-integrations.md        |  4 +-
 docs/tracks/en/banners-en.md                  |  2 +-
 docs/tracks/en/barcode-reading.md             |  2 +-
 .../en/basic-vtex-io-developer-setup.md       |  6 +--
 .../en/best-practices-for-testing-instore.md  |  2 +-
 docs/tracks/en/cart-transfer-and-capture.md   |  6 +--
 docs/tracks/en/cart-transfer.md               |  6 +--
 docs/tracks/en/catalog-architecture.md        |  2 +-
 docs/tracks/en/catalog-concept-definition.md  |  2 +-
 .../en/changing-the-instore-language.md       |  2 +-
 docs/tracks/en/cms-folder-structure.md        |  2 +-
 docs/tracks/en/cms-vtex-io.md                 | 10 ++---
 .../en/configure-customer-identification.md   | 10 ++---
 .../en/configuring-a-payment-condition.md     |  2 +-
 docs/tracks/en/configuring-banners.md         |  4 +-
 ...nfiguring-cash-payments-through-instore.md |  2 +-
 .../en/configuring-login-with-facebook.md     |  2 +-
 .../en/configuring-login-with-google.md       |  2 +-
 docs/tracks/en/configuring-redirect.md        |  2 +-
 docs/tracks/en/configuring-ship-from-store.md |  2 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |  2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  2 +-
 .../en/configuring-the-relevance-feature.md   |  6 +--
 docs/tracks/en/create-brands.md               |  2 +-
 docs/tracks/en/create-product-feed.md         |  4 +-
 docs/tracks/en/create-the-category-tree.md    |  2 +-
 docs/tracks/en/creating-accounts.md           |  4 +-
 ...ating-merchandising-rules-visual-editor.md |  2 +-
 .../en/creating-or-editing-a-page-template.md |  4 +-
 docs/tracks/en/creating-regular-promotions.md |  2 +-
 docs/tracks/en/credit-card-payment-flow.md    |  2 +-
 docs/tracks/en/customer-identification.md     |  2 +-
 docs/tracks/en/customizing-styles.md          |  4 +-
 docs/tracks/en/customizing-templates.md       |  2 +-
 docs/tracks/en/dashboard.md                   |  2 +-
 docs/tracks/en/delivery.md                    |  8 ++--
 .../en/detaching-skus-by-specification.md     |  2 +-
 .../enabling-2-factor-authentication-login.md | 16 +++----
 docs/tracks/en/enabling-a-sales-rep-code.md   |  4 +-
 .../enabling-cart-transfer-between-devices.md |  6 +--
 .../en/enabling-product-recommendations.md    |  2 +-
 docs/tracks/en/explained-search.md            |  2 +-
 docs/tracks/en/extensions-hub-1.md            |  2 +-
 docs/tracks/en/extensions-hub-app-store.md    |  6 +--
 docs/tracks/en/filter-orders-by-vendor.md     |  4 +-
 docs/tracks/en/frontend-implementation.md     |  6 +--
 docs/tracks/en/frontend.md                    |  2 +-
 .../en/getting-started-with-logistics.md      |  2 +-
 docs/tracks/en/go-live-process.md             |  4 +-
 docs/tracks/en/google-pay.md                  |  6 +--
 docs/tracks/en/google-shopping-marketplace.md |  2 +-
 ...hide-product-suggestions-recommendation.md |  2 +-
 .../how-a-split-payment-transaction-works.md  |  2 +-
 ...ustom-text-in-the-printout-of-the-order.md |  4 +-
 ...change-the-sales-policy-used-by-instore.md |  4 +-
 ...nfigure-a-device-for-printout-the-order.md |  4 +-
 ...ister-your-salespersons-on-vtex-instore.md | 10 ++---
 docs/tracks/en/import-orders-from-lengow.md   |  2 +-
 ...uding-order-variables-in-email-template.md |  4 +-
 docs/tracks/en/indexing-history.md            | 16 +++----
 .../en/initializing-your-store-theme.md       |  6 +--
 .../inserting-and-configuring-placeholders.md |  6 +--
 docs/tracks/en/installation-and-setup.md      |  4 +-
 docs/tracks/en/instore-basic-settings.md      |  8 ++--
 docs/tracks/en/instore-customizations.md      |  6 +--
 docs/tracks/en/instore-login.md               |  2 +-
 docs/tracks/en/instore.md                     | 30 ++++++-------
 ...ating-instore-to-a-new-payment-acquirer.md |  2 +-
 docs/tracks/en/integration-settings.md        |  2 +-
 docs/tracks/en/intelligent-synonyms.md        |  4 +-
 docs/tracks/en/intro-to-vtex-io-builders.md   |  2 +-
 docs/tracks/en/introduction-to-vtex-io.md     |  2 +-
 docs/tracks/en/introduction-to-vtex.md        |  2 +-
 .../inventory-and-shipping-module-overview.md |  2 +-
 docs/tracks/en/legacy-cms-portal.md           |  6 +--
 docs/tracks/en/live-support.md                |  6 +--
 docs/tracks/en/managing-accounts.md           |  2 +-
 .../en/managing-customer-credit-invoices.md   |  2 +-
 .../managing-sales-associates-in-instore.md   |  2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  2 +-
 docs/tracks/en/mapping-colors-and-sizes.md    |  2 +-
 docs/tracks/en/merchandising-rules.md         |  2 +-
 docs/tracks/en/opening-tickets.md             |  2 +-
 docs/tracks/en/order-delivery.md              |  2 +-
 docs/tracks/en/order-flow.md                  |  6 +--
 docs/tracks/en/other-vtex-module-settings.md  |  2 +-
 docs/tracks/en/payment.md                     | 16 +++----
 docs/tracks/en/planning-the-go-live.md        |  4 +-
 .../en/preco-base-definicao-de-conceito.md    |  2 +-
 .../en/preco-fixo-definicao-de-conceito.md    |  4 +-
 docs/tracks/en/pricing-system-architecture.md | 12 ++---
 docs/tracks/en/printing-an-order-summary.md   |  6 +--
 docs/tracks/en/product-details.md             |  2 +-
 .../en/promotions-for-specific-scenarios.md   | 18 ++++----
 docs/tracks/en/relevance.md                   |  4 +-
 .../en/reports-vtex-intelligent-search.md     |  4 +-
 docs/tracks/en/sale-confirmed.md              |  2 +-
 docs/tracks/en/sales-channel-mapping.md       |  2 +-
 docs/tracks/en/search-settings.md             |  2 +-
 docs/tracks/en/sending-products-to-amazon.md  | 16 +++----
 .../en/set-the-sku-quantity-in-inventory.md   |  2 +-
 ...etting-instore-up-in-a-store-easy-setup.md | 12 ++---
 ...setting-up-a-marketplace-trade-policy-2.md |  4 +-
 .../setting-up-a-marketplace-trade-policy.md  |  4 +-
 ...app-linking-for-payments-app-in-instore.md |  2 +-
 docs/tracks/en/setting-up-the-app.md          | 16 +++----
 .../setting-up-the-order-summary-printing.md  |  8 ++--
 ...pping-cart-using-instore-social-selling.md |  4 +-
 docs/tracks/en/shipping-strategies.md         |  2 +-
 docs/tracks/en/specifications-mapping.md      |  2 +-
 docs/tracks/en/store-development.md           |  2 +-
 docs/tracks/en/technical-support.md           |  2 +-
 docs/tracks/en/the-reservation.md             |  2 +-
 docs/tracks/en/the-transaction-flow.md        |  2 +-
 docs/tracks/en/unified-commerce-101.md        |  4 +-
 docs/tracks/en/unified-commerce.md            |  2 +-
 docs/tracks/en/unified-search.md              |  6 +--
 .../en/update-and-import-product-feed.md      |  2 +-
 docs/tracks/en/using-custom-controls.md       |  2 +-
 docs/tracks/en/vtex-modules-i.md              | 10 ++---
 docs/tracks/en/vtex-modules-ii.md             |  8 ++--
 docs/tracks/en/what-is-a-logistics-route.md   |  2 +-
 docs/tracks/en/what-is-the-cms.md             |  2 +-
 docs/tracks/en/what-is-the-master-user.md     |  2 +-
 docs/tracks/en/whatsapp-integration.md        |  6 +--
 .../es/access-to-the-customers-last-cart.md   |  2 +-
 docs/tracks/es/accounts-and-architecture.md   |  4 +-
 docs/tracks/es/add-an-image-to-the-sku.md     |  4 +-
 docs/tracks/es/add-on-products.md             | 16 +++----
 docs/tracks/es/add-pickup-points.md           |  2 +-
 docs/tracks/es/add-sku-specifications.md      |  8 ++--
 docs/tracks/es/adding-a-loading-dock.md       |  2 +-
 .../adding-extra-text-to-the-order-print.md   |  4 +-
 .../tracks/es/adding-new-stores-to-instore.md |  4 +-
 .../es/adding-product-specifications.md       |  8 ++--
 docs/tracks/es/adding-products.md             |  2 +-
 docs/tracks/es/adding-skus.md                 |  6 +--
 docs/tracks/es/adding-vendors.md              |  4 +-
 docs/tracks/es/adding-warehouses.md           |  2 +-
 docs/tracks/es/amazon.md                      |  2 +-
 .../associating-a-template-with-a-layout.md   |  2 +-
 docs/tracks/es/autocomplete-search.md         |  8 ++--
 docs/tracks/es/b2b-form.md                    |  6 +--
 docs/tracks/es/backend-integrations.md        |  4 +-
 docs/tracks/es/banners-en.md                  |  2 +-
 docs/tracks/es/barcode-reading.md             |  2 +-
 .../es/basic-vtex-io-developer-setup.md       |  6 +--
 .../es/best-practices-for-testing-instore.md  |  2 +-
 .../es/calculating-order-shipping-time.md     |  8 ++--
 docs/tracks/es/cart-transfer-and-capture.md   |  6 +--
 docs/tracks/es/cart-transfer.md               |  6 +--
 docs/tracks/es/catalog-architecture.md        |  2 +-
 docs/tracks/es/catalog-concept-definition.md  |  2 +-
 .../es/changing-the-instore-language.md       |  2 +-
 docs/tracks/es/cms-folder-structure.md        |  2 +-
 docs/tracks/es/cms-vtex-io.md                 | 10 ++---
 .../es/configure-customer-identification.md   | 10 ++---
 ...configure-integration-of-pick-up-points.md | 10 ++---
 .../es/configuring-a-payment-condition.md     |  2 +-
 docs/tracks/es/configuring-banners.md         |  4 +-
 ...nfiguring-cash-payments-through-instore.md |  2 +-
 .../tracks/es/configuring-dafiti-connector.md |  2 +-
 .../es/configuring-login-with-facebook.md     |  2 +-
 .../es/configuring-login-with-google.md       |  2 +-
 docs/tracks/es/configuring-redirect.md        |  2 +-
 docs/tracks/es/configuring-ship-from-store.md |  2 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |  2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  2 +-
 .../es/configuring-the-relevance-feature.md   |  6 +--
 docs/tracks/es/create-a-brand.md              |  2 +-
 docs/tracks/es/create-a-category.md           |  8 ++--
 docs/tracks/es/create-a-product.md            |  4 +-
 docs/tracks/es/create-an-sku.md               |  4 +-
 docs/tracks/es/create-brands.md               |  2 +-
 docs/tracks/es/create-the-category-tree.md    |  2 +-
 docs/tracks/es/creating-accounts.md           |  4 +-
 ...ating-merchandising-rules-visual-editor.md |  4 +-
 .../es/creating-or-editing-a-page-template.md |  4 +-
 docs/tracks/es/creating-regular-promotions.md |  2 +-
 docs/tracks/es/credit-card-payment-flow.md    |  2 +-
 ...tor-and-dimensional-weight-calculations.md |  2 +-
 docs/tracks/es/customer-identification.md     |  2 +-
 docs/tracks/es/customizing-styles.md          |  4 +-
 docs/tracks/es/customizing-templates.md       |  2 +-
 docs/tracks/es/dashboard.md                   |  2 +-
 docs/tracks/es/delivery.md                    |  8 ++--
 .../es/detaching-skus-by-specification.md     |  2 +-
 .../enabling-2-factor-authentication-login.md | 16 +++----
 docs/tracks/es/enabling-a-sales-rep-code.md   |  4 +-
 .../enabling-cart-transfer-between-devices.md |  6 +--
 .../es/enabling-product-recommendations.md    |  2 +-
 docs/tracks/es/explained-search.md            |  2 +-
 docs/tracks/es/extensions-hub-1.md            |  2 +-
 docs/tracks/es/extensions-hub-app-store.md    |  6 +--
 docs/tracks/es/filter-orders-by-vendor.md     |  4 +-
 docs/tracks/es/frontend-implementation.md     |  6 +--
 docs/tracks/es/frontend.md                    |  2 +-
 .../es/getting-started-with-logistics.md      |  2 +-
 docs/tracks/es/go-live-process.md             |  4 +-
 docs/tracks/es/google-pay.md                  |  6 +--
 docs/tracks/es/google-shopping-marketplace.md |  2 +-
 ...hide-product-suggestions-recommendation.md |  2 +-
 .../how-a-split-payment-transaction-works.md  |  2 +-
 .../es/how-clustered-conditions-work.md       |  2 +-
 docs/tracks/es/how-message-center-works.md    |  6 +--
 ...change-the-sales-policy-used-by-instore.md |  4 +-
 .../es/how-to-configure-a-custom-payment.md   |  2 +-
 ...nfigure-a-device-for-printout-the-order.md |  8 ++--
 ...ister-your-salespersons-on-vtex-instore.md | 10 ++---
 ...uding-order-variables-in-email-template.md |  4 +-
 docs/tracks/es/indexing-history.md            | 16 +++----
 .../es/initializing-your-store-theme.md       |  6 +--
 .../inserting-and-configuring-placeholders.md |  6 +--
 docs/tracks/es/instore-basic-settings.md      |  8 ++--
 docs/tracks/es/instore-customizations.md      |  6 +--
 docs/tracks/es/instore-login.md               |  2 +-
 docs/tracks/es/instore.md                     | 30 ++++++-------
 ...ating-instore-to-a-new-payment-acquirer.md |  2 +-
 docs/tracks/es/integration-configurations.md  |  2 +-
 docs/tracks/es/integration-settings.md        |  2 +-
 docs/tracks/es/intelligent-synonyms.md        |  4 +-
 docs/tracks/es/intro-to-vtex-io-builders.md   |  2 +-
 docs/tracks/es/introduction-to-vtex-io.md     |  2 +-
 docs/tracks/es/introduction-to-vtex.md        |  2 +-
 .../inventory-and-shipping-module-overview.md |  2 +-
 docs/tracks/es/legacy-cms-portal.md           |  6 +--
 docs/tracks/es/live-support.md                |  6 +--
 docs/tracks/es/managing-accounts.md           |  2 +-
 .../es/managing-customer-credit-invoices.md   |  2 +-
 .../managing-sales-associates-in-instore.md   |  2 +-
 docs/tracks/es/managing-shipping-rates.md     |  2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  2 +-
 docs/tracks/es/mapping-colors-and-sizes.md    |  2 +-
 ...egories-and-attributes-to-mercado-libre.md |  2 +-
 docs/tracks/es/mercado-libre-marketplace.md   |  2 +-
 docs/tracks/es/merchandising-rules.md         |  2 +-
 docs/tracks/es/opening-tickets.md             |  2 +-
 docs/tracks/es/order-delivery.md              |  2 +-
 docs/tracks/es/order-flow.md                  |  6 +--
 docs/tracks/es/other-vtex-module-settings.md  |  2 +-
 docs/tracks/es/payment.md                     | 16 +++----
 docs/tracks/es/planning-the-go-live.md        |  4 +-
 .../es/preco-base-definicao-de-conceito.md    |  2 +-
 .../es/preco-fixo-definicao-de-conceito.md    |  4 +-
 docs/tracks/es/pricing-system-architecture.md | 12 ++---
 docs/tracks/es/printing-an-order-summary.md   |  6 +--
 docs/tracks/es/product-details.md             |  2 +-
 .../es/promotions-for-specific-scenarios.md   | 18 ++++----
 docs/tracks/es/relevance.md                   |  4 +-
 .../es/reports-vtex-intelligent-search.md     |  4 +-
 docs/tracks/es/sale-confirmed.md              |  2 +-
 docs/tracks/es/search-settings.md             |  2 +-
 docs/tracks/es/sending-products-to-amazon.md  | 16 +++----
 docs/tracks/es/set-a-price-for-the-sku.md     |  4 +-
 .../es/set-the-sku-quantity-in-inventory.md   |  6 +--
 ...etting-instore-up-in-a-store-easy-setup.md | 12 ++---
 ...setting-up-a-marketplace-trade-policy-2.md |  2 +-
 .../setting-up-a-marketplace-trade-policy.md  |  6 +--
 ...app-linking-for-payments-app-in-instore.md |  2 +-
 docs/tracks/es/setting-up-the-app.md          | 16 +++----
 .../setting-up-the-order-summary-printing.md  |  8 ++--
 ...pping-cart-using-instore-social-selling.md |  4 +-
 docs/tracks/es/shipping-strategies.md         |  2 +-
 docs/tracks/es/size-chart.md                  |  2 +-
 docs/tracks/es/store-development.md           |  2 +-
 docs/tracks/es/technical-support.md           |  2 +-
 docs/tracks/es/the-reservation.md             |  2 +-
 docs/tracks/es/the-transaction-flow.md        |  2 +-
 docs/tracks/es/unified-commerce-101.md        |  4 +-
 docs/tracks/es/unified-commerce.md            |  2 +-
 docs/tracks/es/unified-search.md              |  6 +--
 docs/tracks/es/using-custom-controls.md       |  2 +-
 docs/tracks/es/vtex-modules-i.md              | 10 ++---
 docs/tracks/es/vtex-modules-ii.md             |  8 ++--
 docs/tracks/es/what-is-a-logistics-route.md   |  2 +-
 docs/tracks/es/what-is-the-master-user.md     |  2 +-
 docs/tracks/es/whatsapp-integration.md        |  6 +--
 .../pt/access-to-the-customers-last-cart.md   |  2 +-
 docs/tracks/pt/accounts-and-architecture.md   |  4 +-
 docs/tracks/pt/add-an-image-to-the-sku.md     |  4 +-
 docs/tracks/pt/add-on-products.md             | 16 +++----
 docs/tracks/pt/add-pickup-points.md           |  2 +-
 docs/tracks/pt/add-sku-specifications.md      |  8 ++--
 docs/tracks/pt/adding-a-loading-dock.md       |  2 +-
 .../adding-extra-text-to-the-order-print.md   |  4 +-
 .../tracks/pt/adding-new-stores-to-instore.md |  4 +-
 .../pt/adding-product-specifications.md       |  8 ++--
 docs/tracks/pt/adding-products.md             |  2 +-
 docs/tracks/pt/adding-skus.md                 |  6 +--
 docs/tracks/pt/adding-vendors.md              |  4 +-
 docs/tracks/pt/adding-warehouses.md           |  2 +-
 docs/tracks/pt/amazon.md                      |  2 +-
 .../associating-a-template-with-a-layout.md   |  2 +-
 docs/tracks/pt/autocomplete-search.md         |  8 ++--
 docs/tracks/pt/b2b-form.md                    |  6 +--
 docs/tracks/pt/backend-integrations.md        |  4 +-
 docs/tracks/pt/banners-en.md                  |  2 +-
 docs/tracks/pt/barcode-reading.md             |  2 +-
 .../pt/basic-vtex-io-developer-setup.md       |  6 +--
 .../pt/best-practices-for-testing-instore.md  |  2 +-
 .../pt/calculating-order-shipping-time.md     |  8 ++--
 .../cancel-and-refund-an-order-on-instore.md  |  2 +-
 ...tes-de-iniciar-uma-conversa-no-whatsapp.md | 10 ++---
 docs/tracks/pt/carrefour-marketplace.md       |  2 +-
 docs/tracks/pt/cart-transfer-and-capture.md   |  6 +--
 docs/tracks/pt/cart-transfer.md               |  6 +--
 docs/tracks/pt/catalog-architecture.md        |  2 +-
 docs/tracks/pt/catalog-concept-definition.md  |  2 +-
 docs/tracks/pt/centauro-marketplace.md        |  2 +-
 .../pt/changing-the-instore-language.md       |  2 +-
 docs/tracks/pt/cms-folder-structure.md        |  2 +-
 docs/tracks/pt/cms-vtex-io.md                 | 10 ++---
 ...ento-no-whatsapp-para-mais-de-um-numero.md |  4 +-
 .../pt/como-funciona-o-adaptador-vtex.md      |  4 +-
 docs/tracks/pt/configurar-adaptador.md        | 10 ++---
 docs/tracks/pt/configurar-erps.md             |  6 +--
 .../pt/configure-customer-identification.md   | 10 ++---
 ...configure-integration-of-pick-up-points.md | 10 ++---
 docs/tracks/pt/configure-integration.md       |  6 +--
 .../pt/configuring-a-payment-condition.md     |  2 +-
 docs/tracks/pt/configuring-banners.md         |  4 +-
 ...nfiguring-cash-payments-through-instore.md |  2 +-
 .../tracks/pt/configuring-dafiti-connector.md |  2 +-
 .../pt/configuring-login-with-facebook.md     |  2 +-
 .../pt/configuring-login-with-google.md       |  2 +-
 docs/tracks/pt/configuring-redirect.md        |  2 +-
 docs/tracks/pt/configuring-ship-from-store.md |  2 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |  2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  4 +-
 .../pt/configuring-the-relevance-feature.md   |  6 +--
 docs/tracks/pt/create-a-brand.md              |  2 +-
 docs/tracks/pt/create-a-category.md           |  8 ++--
 docs/tracks/pt/create-a-product.md            |  4 +-
 docs/tracks/pt/create-an-sku.md               |  4 +-
 docs/tracks/pt/create-brands.md               |  2 +-
 docs/tracks/pt/create-the-category-tree.md    |  2 +-
 docs/tracks/pt/creating-accounts.md           |  4 +-
 ...ating-merchandising-rules-visual-editor.md |  4 +-
 .../pt/creating-or-editing-a-page-template.md |  4 +-
 docs/tracks/pt/creating-regular-promotions.md |  2 +-
 docs/tracks/pt/credit-card-payment-flow.md    |  2 +-
 ...tor-and-dimensional-weight-calculations.md |  2 +-
 docs/tracks/pt/customer-identification.md     |  2 +-
 docs/tracks/pt/customizing-styles.md          |  4 +-
 docs/tracks/pt/customizing-templates.md       |  2 +-
 docs/tracks/pt/dafiti-marketplace.md          |  2 +-
 docs/tracks/pt/dashboard.md                   |  2 +-
 docs/tracks/pt/delivery.md                    | 10 ++---
 .../pt/detaching-skus-by-specification.md     |  2 +-
 .../enabling-2-factor-authentication-login.md |  4 +-
 docs/tracks/pt/enabling-a-sales-rep-code.md   |  4 +-
 .../enabling-cart-transfer-between-devices.md |  6 +--
 .../enabling-order-filter-by-salesperson.md   |  4 +-
 .../pt/enabling-product-recommendations.md    |  4 +-
 ...o-os-clientes-chegam-ate-o-seu-whatsapp.md | 16 +++----
 docs/tracks/pt/explained-search.md            |  2 +-
 docs/tracks/pt/extensions-hub-1.md            |  2 +-
 docs/tracks/pt/extensions-hub-app-store.md    |  6 +--
 docs/tracks/pt/filter-orders-by-vendor.md     |  4 +-
 docs/tracks/pt/frontend-implementation.md     |  6 +--
 docs/tracks/pt/frontend.md                    |  2 +-
 ...website-and-social-networks-to-whatsapp.md |  2 +-
 .../pt/getting-started-with-logistics.md      |  2 +-
 docs/tracks/pt/go-live-process.md             |  4 +-
 docs/tracks/pt/google-pay.md                  |  6 +--
 docs/tracks/pt/google-shopping-marketplace.md |  2 +-
 ...hide-product-suggestions-recommendation.md |  2 +-
 .../how-a-split-payment-transaction-works.md  |  2 +-
 .../pt/how-clustered-conditions-work.md       |  8 ++--
 docs/tracks/pt/how-message-center-works.md    |  6 +--
 ...ustom-text-in-the-printout-of-the-order.md |  4 +-
 ...change-the-sales-policy-used-by-instore.md |  4 +-
 .../pt/how-to-configure-a-custom-payment.md   |  2 +-
 ...nfigure-a-device-for-printout-the-order.md |  8 ++--
 docs/tracks/pt/how-to-get-started.md          |  6 +--
 ...ister-your-salespersons-on-vtex-instore.md | 10 ++---
 ...uding-order-variables-in-email-template.md |  4 +-
 docs/tracks/pt/indexing-history.md            | 16 +++----
 .../pt/initializing-your-store-theme.md       |  6 +--
 .../inserting-and-configuring-placeholders.md |  6 +--
 docs/tracks/pt/instore-basic-settings.md      |  8 ++--
 docs/tracks/pt/instore-customizations.md      |  6 +--
 docs/tracks/pt/instore-login.md               |  2 +-
 docs/tracks/pt/instore.md                     | 32 +++++++-------
 ...ating-instore-to-a-new-payment-acquirer.md |  2 +-
 docs/tracks/pt/integration-configurations.md  |  2 +-
 docs/tracks/pt/integration-settings.md        |  2 +-
 docs/tracks/pt/intelligent-synonyms.md        |  4 +-
 docs/tracks/pt/intro-to-vtex-io-builders.md   |  2 +-
 docs/tracks/pt/introduction-to-vtex-io.md     |  2 +-
 docs/tracks/pt/introduction-to-vtex.md        |  2 +-
 .../inventory-and-shipping-module-overview.md |  2 +-
 docs/tracks/pt/legacy-cms-portal.md           |  6 +--
 ...var-os-contatos-do-whatsapp-para-um-crm.md | 10 ++---
 docs/tracks/pt/live-support.md                |  8 ++--
 docs/tracks/pt/livelo-integration-overview.md |  2 +-
 docs/tracks/pt/login-e-senha.md               |  2 +-
 docs/tracks/pt/magazine-luiza-marketplace.md  |  2 +-
 docs/tracks/pt/managing-accounts.md           |  2 +-
 .../pt/managing-customer-credit-invoices.md   |  2 +-
 .../managing-sales-associates-in-instore.md   |  2 +-
 docs/tracks/pt/managing-shipping-rates.md     |  2 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  2 +-
 docs/tracks/pt/mapping-colors-and-sizes.md    |  2 +-
 ...egories-and-attributes-to-mercado-libre.md |  2 +-
 docs/tracks/pt/mercado-libre-marketplace.md   |  2 +-
 docs/tracks/pt/merchandising-rules.md         |  2 +-
 docs/tracks/pt/monitor-da-integracao.md       |  8 ++--
 docs/tracks/pt/netshoes-marketplace.md        |  2 +-
 docs/tracks/pt/opening-tickets.md             |  2 +-
 docs/tracks/pt/order-delivery.md              |  2 +-
 docs/tracks/pt/order-flow.md                  |  6 +--
 docs/tracks/pt/other-vtex-module-settings.md  |  2 +-
 docs/tracks/pt/payment.md                     | 16 +++----
 docs/tracks/pt/planning-the-go-live.md        |  4 +-
 .../pt/preco-base-definicao-de-conceito.md    |  2 +-
 .../pt/preco-fixo-definicao-de-conceito.md    |  4 +-
 docs/tracks/pt/pricing-system-architecture.md |  2 +-
 docs/tracks/pt/printing-an-order-summary.md   |  6 +--
 docs/tracks/pt/product-details.md             |  2 +-
 .../pt/promotions-for-specific-scenarios.md   | 18 ++++----
 docs/tracks/pt/rappi-integration-overview.md  |  2 +-
 docs/tracks/pt/relevance.md                   |  4 +-
 .../pt/reports-vtex-intelligent-search.md     |  4 +-
 docs/tracks/pt/sale-confirmed.md              |  2 +-
 docs/tracks/pt/search-settings.md             |  2 +-
 docs/tracks/pt/sending-products-to-amazon.md  | 16 +++----
 docs/tracks/pt/set-a-price-for-the-sku.md     |  4 +-
 .../pt/set-the-sku-quantity-in-inventory.md   |  6 +--
 ...etting-instore-up-in-a-store-easy-setup.md | 12 ++---
 ...setting-up-a-marketplace-trade-policy-2.md |  4 +-
 .../setting-up-a-marketplace-trade-policy.md  |  6 +--
 ...app-linking-for-payments-app-in-instore.md |  2 +-
 docs/tracks/pt/setting-up-the-app.md          | 16 +++----
 .../setting-up-the-order-summary-printing.md  |  8 ++--
 ...pping-cart-using-instore-social-selling.md |  4 +-
 docs/tracks/pt/shipping-strategies.md         |  2 +-
 docs/tracks/pt/size-chart.md                  | 10 ++---
 docs/tracks/pt/store-development.md           |  2 +-
 docs/tracks/pt/technical-support.md           |  2 +-
 docs/tracks/pt/the-reservation.md             |  2 +-
 docs/tracks/pt/the-transaction-flow.md        |  2 +-
 docs/tracks/pt/unified-commerce-101.md        |  4 +-
 docs/tracks/pt/unified-commerce.md            |  2 +-
 docs/tracks/pt/unified-search.md              |  6 +--
 docs/tracks/pt/using-custom-controls.md       |  2 +-
 docs/tracks/pt/via-varejo-marketplace.md      |  2 +-
 docs/tracks/pt/vtex-modules-i.md              | 10 ++---
 docs/tracks/pt/vtex-modules-ii.md             |  8 ++--
 docs/tracks/pt/what-is-a-logistics-route.md   |  2 +-
 .../what-is-conversational-commerce-vtex.md   |  2 +-
 docs/tracks/pt/what-is-the-cms.md             |  2 +-
 docs/tracks/pt/what-is-the-master-user.md     |  2 +-
 docs/tracks/pt/whatsapp-integration.md        |  6 +--
 .../en/accessing-a-client-abandoned-cart.md   | 12 ++---
 docs/tutorials/en/account-management.md       |  2 +-
 .../tutorials/en/account-settings-overview.md |  2 +-
 ...complete-list-link-on-the-category-menu.md |  4 +-
 .../en/activating-the-new-order-placed.md     |  4 +-
 ...-a-url-mapping-through-worksheet-import.md |  2 +-
 ...a-client-secret-to-log-in-with-facebook.md | 14 +++---
 ...d-a-client-secret-to-log-in-with-google.md | 24 +++++-----
 docs/tutorials/en/adding-an-attachment.md     |  2 +-
 docs/tutorials/en/adding-bin-information.md   |  4 +-
 docs/tutorials/en/adding-collections-cms.md   | 20 ++++-----
 .../en/adding-sku-specifications-or-fields.md | 12 ++---
 ...adding-specifications-or-product-fields.md | 10 ++---
 docs/tutorials/en/adding-your-brands.md       |  2 +-
 .../tutorials/en/additional-shipping-costs.md |  8 ++--
 docs/tutorials/en/admin-v4-getting-started.md | 10 ++---
 docs/tutorials/en/ads-from-vtex-sales-app.md  | 18 ++++----
 .../advertising-with-vtex-ad-network-beta.md  |  4 +-
 docs/tutorials/en/affiliates-program-app.md   | 10 ++---
 docs/tutorials/en/all-orders.md               |  4 +-
 ...mazon-multi-channel-fulfillment-mcf-app.md |  2 +-
 docs/tutorials/en/amazon-offer-matching.md    |  8 ++--
 docs/tutorials/en/analytics.md                |  4 +-
 .../en/analyze-a-products-reservations.md     |  2 +-
 docs/tutorials/en/antifraud-provider.md       | 14 +++---
 docs/tutorials/en/application-keys.md         |  4 +-
 ...roving-payment-of-the-bank-payment-slip.md |  2 +-
 docs/tutorials/en/apps-overview.md            |  2 +-
 docs/tutorials/en/assembly-options-app.md     |  2 +-
 .../en/assembly-options-in-vtex-sales-app.md  | 10 ++---
 docs/tutorials/en/assembly-options.md         |  4 +-
 .../associating-a-template-with-a-layout.md   |  2 +-
 docs/tutorials/en/audit.md                    |  4 +-
 docs/tutorials/en/authentication.md           |  2 +-
 docs/tutorials/en/autocomplete.md             |  8 ++--
 .../en/b2b-organization-general-settings.md   |  2 +-
 docs/tutorials/en/b2b-store-settings.md       |  4 +-
 docs/tutorials/en/b2b-suite-overview.md       |  2 +-
 docs/tutorials/en/bank-reconciliations.md     |  6 +--
 docs/tutorials/en/banners.md                  |  2 +-
 docs/tutorials/en/beta-price-configuration.md |  6 +--
 docs/tutorials/en/billing-module-overview.md  |  2 +-
 docs/tutorials/en/brands.md                   |  2 +-
 docs/tutorials/en/breadcrumb-control.md       |  4 +-
 ...inging-app-content-into-the-admin-panel.md |  8 ++--
 docs/tutorials/en/buy-one-get-one.md          | 12 ++---
 ...e-articulos-del-mismo-sku-en-el-carrito.md |  2 +-
 docs/tutorials/en/campaign-audiences-list.md  |  4 +-
 docs/tutorials/en/campaign-audiences.md       |  2 +-
 docs/tutorials/en/campaign-promotion.md       |  4 +-
 ...rking-hours-and-scheduled-delivery-beta.md |  6 +--
 docs/tutorials/en/catalog-overview.md         |  4 +-
 docs/tutorials/en/categories.md               |  4 +-
 .../en/category-registration-fields.md        |  6 +--
 ...egory-variations-and-attributes-mapping.md |  6 +--
 .../en/change-a-placeholder-title.md          |  4 +-
 docs/tutorials/en/change-seller.md            |  4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |  2 +-
 .../en/changing-a-pages-body-class.md         |  4 +-
 ...ult-system-texts-displayed-in-the-store.md |  4 +-
 .../changing-the-total-cost-of-the-order.md   |  4 +-
 docs/tutorials/en/changing-tracking-data.md   |  2 +-
 .../en/check-order-delivery-details.md        |  2 +-
 ...-order-delivery-deadline-was-calculated.md | 12 ++---
 docs/tutorials/en/checkout-vtex-overview.md   |  2 +-
 docs/tutorials/en/cms-folder-structure.md     |  2 +-
 docs/tutorials/en/cms-overview.md             |  2 +-
 docs/tutorials/en/cms-store-overview.md       |  2 +-
 .../en/collection-highlight-control.md        |  2 +-
 ...-sistema-esta-sendo-renderizada-no-site.md |  2 +-
 .../en/conditions-builder-usage-examples.md   |  6 +--
 ...-accounts-with-multiple-official-stores.md |  6 +--
 docs/tutorials/en/configure-cartman.md        |  8 ++--
 ...yee-benefits-using-master-data-clusters.md |  4 +-
 ...figure-template-in-smartcheckout-update.md | 32 +++++++-------
 ...configure-template-in-the-smartcheckout.md | 26 +++++------
 ...g-a-discount-for-orders-prepaid-in-full.md |  2 +-
 .../configuring-a-marketplace-trade-policy.md | 18 ++++----
 docs/tutorials/en/configuring-banners.md      |  4 +-
 ...port-for-organizations-and-cost-centers.md |  4 +-
 .../en/configuring-cargo-splitting.md         |  2 +-
 ...ng-clearsale-global-anti-fraud-solution.md |  2 +-
 .../en/configuring-clearsale-v3-antifraud.md  |  2 +-
 ...nctions-in-the-message-center-templates.md |  4 +-
 docs/tutorials/en/configuring-greenlist.md    | 10 ++---
 ...figuring-login-with-facebook-and-google.md |  6 +--
 ...automatic-payment-settlement-time-frame.md |  2 +-
 ...guring-mercado-pagos-device-fingerprint.md |  4 +-
 ...ring-my-account-conversational-commerce.md |  2 +-
 .../en/configuring-payment-gateways.md        |  2 +-
 ...-payment-with-adyenv3-in-vtex-sales-app.md | 12 ++---
 .../en/configuring-payment-with-adyenv3.md    | 14 +++---
 .../en/configuring-price-divergence-rule.md   |  6 +--
 docs/tutorials/en/configuring-prices-v2.md    |  4 +-
 .../en/configuring-product-visited.md         | 14 +++---
 ...iguring-promotions-with-a-highlightflag.md |  6 +--
 ...uring-pwa-in-your-store-framework-store.md |  6 +--
 docs/tutorials/en/configuring-redirects.md    |  2 +-
 ...guring-seller-allocation-for-buying-xky.md |  6 +--
 .../en/configuring-seo-in-your-store.md       |  6 +--
 .../en/configuring-shipping-promotions.md     | 16 +++----
 .../configuring-sign-in-with-apple-id-beta.md |  2 +-
 .../en/configuring-the-past-prices-control.md |  2 +-
 .../en/configuring-the-pickup-in-store.md     | 12 ++---
 .../en/configuring-the-scheduled-delivery.md  |  4 +-
 .../en/configuring-the-store-domain.md        |  2 +-
 docs/tutorials/en/configuring-your-layout.md  |  2 +-
 ...g-a-layout-from-one-web-site-to-another.md |  4 +-
 docs/tutorials/en/coupons-list-beta.md        | 12 ++---
 ...ate-a-talk-to-us-form-using-master-data.md |  2 +-
 .../en/creating-a-campaign-audience.md        |  4 +-
 ...o-guarantee-it-as-an-option-at-checkout.md |  2 +-
 docs/tutorials/en/creating-a-coupon-beta.md   |  8 ++--
 .../en/creating-a-more-for-less-promotion.md  | 14 +++---
 ...eating-a-personalized-master-data-query.md |  8 ++--
 .../en/creating-a-product-collection.md       | 20 ++++-----
 .../en/creating-a-subscription-plan.md        |  2 +-
 .../en/creating-a-subscription-promotion.md   |  2 +-
 docs/tutorials/en/creating-a-type-of-list.md  |  4 +-
 .../en/creating-an-oauth2-authentication.md   |  2 +-
 ...h-promotional-price-using-a-price-table.md |  4 +-
 .../tutorials/en/creating-collections-beta.md | 18 ++++----
 ...eating-custom-queries-in-master-data-v1.md |  4 +-
 docs/tutorials/en/creating-data-entity.md     |  2 +-
 .../en/creating-form-in-master-data.md        |  2 +-
 .../en/creating-landing-pages-per-binding.md  |  2 +-
 docs/tutorials/en/creating-landing-pages.md   |  2 +-
 ...-merchandising-rules-visual-editor-beta.md |  2 +-
 ...ating-merchandising-rules-visual-editor.md |  2 +-
 docs/tutorials/en/creating-price-tables.md    |  2 +-
 ...eating-promotion-for-a-customer-cluster.md |  8 ++--
 docs/tutorials/en/creating-promotions.md      |  2 +-
 ...etween-master-data-entities-using-admin.md | 40 ++++++++---------
 docs/tutorials/en/creating-roles.md           |  8 ++--
 .../en/creating-service-for-a-sku.md          |  2 +-
 docs/tutorials/en/creating-surchargestaxes.md |  2 +-
 .../en/creating-the-category-tree.md          |  2 +-
 .../en/creating-trigger-in-master-data.md     |  8 ++--
 docs/tutorials/en/creating-your-promotions.md |  2 +-
 .../en/credit-card-basic-payment-flow.md      |  2 +-
 docs/tutorials/en/credit-control-overview.md  |  2 +-
 docs/tutorials/en/criar-um-produto-beta.md    | 20 ++++-----
 docs/tutorials/en/customer-credit-overview.md |  2 +-
 ...omizing-the-checkout-confirmation-pages.md |  8 ++--
 .../en/customizing-the-my-orders-section.md   |  6 +--
 .../en/customizing-your-stores-typography.md  |  4 +-
 docs/tutorials/en/data-entity.md              |  2 +-
 docs/tutorials/en/data-subject-rights.md      |  2 +-
 .../deactivating-store-skus-and-products.md   |  2 +-
 .../en/declining-order-cancelation.md         |  6 +--
 docs/tutorials/en/defining-product-prices.md  |  2 +-
 docs/tutorials/en/defining-window-displays.md | 12 ++---
 docs/tutorials/en/deleting-a-category.md      |  2 +-
 .../en/deleting-a-folder-from-cms.md          |  4 +-
 .../en/detaching-skus-by-specification.md     |  2 +-
 docs/tutorials/en/disable-cloudflare-proxy.md |  2 +-
 ...isplaying-the-store-in-another-language.md |  2 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |  4 +-
 ...ic-relevance-in-intelligent-search-beta.md |  4 +-
 docs/tutorials/en/enable-checkout-v6.md       |  4 +-
 .../enabling-2-factor-authentication-login.md | 16 +++----
 ...enabling-3ds2-for-redsys-v2-integration.md |  2 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |  6 +--
 ...ng-pwa-push-notifications-in-your-store.md |  2 +-
 .../en/entering-tax-receipts-in-the-order.md  |  2 +-
 .../en/excluding-a-product-from-the-store.md  |  2 +-
 docs/tutorials/en/explained-search.md         |  2 +-
 ...mporting-product-and-sku-specifications.md |  6 +--
 docs/tutorials/en/facebook-faq.md             |  2 +-
 .../en/facilitating-b2b-store-operation.md    |  2 +-
 ...-import-spreadsheets-fixed-price-fields.md |  2 +-
 docs/tutorials/en/filtering-all-orders.md     | 10 ++---
 ...tplaces-and-sellers-in-the-vtex-network.md |  4 +-
 ...d-questions-new-orders-module-interface.md | 12 ++---
 .../en/fulfillment-logistics-vtex.md          |  2 +-
 .../en/general-configurations-on-the-oms.md   |  2 +-
 docs/tutorials/en/generating-a-har-file.md    |  8 ++--
 docs/tutorials/en/geolocation-at-checkout.md  |  4 +-
 docs/tutorials/en/google-pay-beta.md          |  2 +-
 .../google-search-console-tracking-sitemap.md |  4 +-
 docs/tutorials/en/headless-cms-overview.md    |  2 +-
 ...how-can-i-change-the-domain-of-my-store.md |  2 +-
 ...how-can-i-create-a-field-in-master-data.md |  4 +-
 .../en/how-can-i-create-callcenter-user.md    |  2 +-
 .../how-can-my-customer-login-to-my-store.md  | 18 ++++----
 ...e-the-https-protocol-on-my-stores-pages.md |  8 ++--
 ...-in-installments-with-compound-interest.md |  8 ++--
 .../en/how-does-promotion-proration-work.md   |  2 +-
 ...th-multiple-items-work-in-mercado-livre.md |  2 +-
 .../en/how-does-the-delivery-flow-work.md     |  2 +-
 ...arch-context-on-website-folders-operate.md |  2 +-
 .../en/how-does-the-type-of-delivery-work.md  |  2 +-
 .../tutorials/en/how-does-vtex-search-work.md |  2 +-
 .../en/how-is-pro-rata-calculated-in-vtex.md  |  2 +-
 .../en/how-is-taxhub-api-rest-structure.md    | 14 +++---
 ...-the-order-delivery-deadline-calculated.md |  2 +-
 .../how-is-the-taxhub-app-structure-in-js.md  |  2 +-
 docs/tutorials/en/how-my-account-works.md     | 18 ++++----
 .../en/how-order-authorization-works.md       |  2 +-
 .../en/how-order-authorization-workss.md      |  2 +-
 .../en/how-promotion-competition-works.md     |  2 +-
 .../en/how-recursive-marketplace-works.md     |  2 +-
 ...hen-delivery-is-done-by-the-marketplace.md |  4 +-
 ...he-automatic-compacting-of-images-works.md |  2 +-
 .../en/how-the-documents-saving-flow-works.md |  2 +-
 .../en/how-the-order-replacement-works.md     |  6 +--
 .../en/how-the-seller-portal-catalog-works.md |  2 +-
 .../how-to-activate-the-shareable-cart-app.md |  4 +-
 docs/tutorials/en/how-to-alter-a-banner.md    |  6 +--
 .../tutorials/en/how-to-archive-ratestaxes.md |  2 +-
 .../en/how-to-assemble-a-look-kit.md          |  4 +-
 .../en/how-to-capture-the-ip-of-an-order.md   |  4 +-
 .../tutorials/en/how-to-change-orders-beta.md | 12 ++---
 ...-of-vtex-store-on-google-search-console.md | 10 ++---
 .../tutorials/en/how-to-check-your-balance.md |  2 +-
 ...-configure-extra-fields-in-instore-cart.md |  4 +-
 ...ago-transparente-in-the-payments-module.md |  6 +--
 ...e-and-maximum-quantity-of-items-per-sku.md |  4 +-
 .../en/how-to-configure-payment-conditions.md |  4 +-
 ...to-configure-rating-and-review-controls.md |  4 +-
 docs/tutorials/en/how-to-configure-taxhub.md  |  2 +-
 .../en/how-to-configure-the-favicon.md        |  4 +-
 ...figure-the-fingerprint-device-for-stelo.md |  8 ++--
 ...ow-to-configure-xml-for-google-shopping.md |  2 +-
 ...ng-feed-and-the-google-product-taxonomy.md |  6 +--
 ...pment-environment-with-a-mobile-version.md |  2 +-
 ...ow-to-create-a-financial-access-profile.md |  4 +-
 .../en/how-to-create-a-page-template.md       |  2 +-
 docs/tutorials/en/how-to-create-a-product.md  | 18 ++++----
 ...eate-a-promotion-with-limitation-of-use.md |  2 +-
 .../en/how-to-create-a-store-name.md          |  2 +-
 ...how-to-create-a-subscription-attachment.md |  4 +-
 .../en/how-to-create-conditional-prices.md    |  2 +-
 ...ipt-customization-file-for-vtex-instore.md | 10 ++---
 ...-to-customize-a-page-using-placeholders.md | 14 +++---
 ...ize-the-checkout-ui-custom-in-the-admin.md |  8 ++--
 ...ow-to-define-the-url-for-a-product-page.md |  2 +-
 ...w-to-deprecate-and-undeprecate-your-app.md |  2 +-
 .../how-to-disable-a-transactional-email.md   |  2 +-
 .../en/how-to-download-the-vtex-invoices.md   |  6 +--
 docs/tutorials/en/how-to-find-an-sku-id.md    |  2 +-
 ...rls-that-are-inactive-or-contain-errors.md | 10 ++---
 .../en/how-to-identify-a-page-template.md     |  6 +--
 ...ayout-errors-caused-by-javascript-files.md |  2 +-
 ...identify-promotions-applied-to-the-cart.md |  4 +-
 ...dentify-promotions-attributed-to-an-sku.md | 12 ++---
 ...import-pickup-points-using-spreadsheets.md |  6 +--
 ...llection-of-products-in-the-shop-window.md | 18 ++++----
 ...ata-when-exporting-a-prices-spreadsheet.md |  4 +-
 ...ll-the-masterpass-in-the-vtex-app-store.md | 12 ++---
 .../tutorials/en/how-to-install-the-taxhub.md |  2 +-
 .../en/how-to-integrate-with-dafiti.md        |  6 +--
 .../en/how-to-manage-subscriptions.md         |  6 +--
 .../en/how-to-manage-the-kit-stock.md         |  2 +-
 .../en/how-to-manually-invoice-an-order.md    |  4 +-
 ...how-to-register-a-store-in-vtex-instore.md |  8 ++--
 ...how-to-request-receivables-anticipation.md |  2 +-
 .../en/how-to-retrieve-the-access-password.md | 10 ++---
 .../how-to-see-orders-closed-with-benefits.md |  2 +-
 ...fine-a-default-sla-for-recurrent-orders.md |  4 +-
 .../en/how-to-set-up-fingerprint-for-payu.md  | 22 +++++-----
 ...r-to-accept-payments-with-adyen-at-vtex.md |  4 +-
 ...t-up-the-device-fingerprint-for-braspag.md |  8 ++--
 ...set-up-the-indeva-scheduled-appointment.md | 10 ++---
 docs/tutorials/en/how-to-set-up-the-zoom.md   |  6 +--
 docs/tutorials/en/how-to-set-up-visa-debit.md |  6 +--
 .../en/how-to-use-conditions-builder-app.md   |  6 +--
 .../en/how-to-use-the-index-report.md         |  2 +-
 .../how-to-use-the-search-result-control.md   | 10 ++---
 .../en/how-to-use-the-shareable-cart-app.md   | 12 ++---
 ...ow-to-use-the-unavailable-product-class.md |  2 +-
 .../en/how-to-use-vtex-predictor-bot.md       |  8 ++--
 ...how-to-view-taxes-information-in-taxhub.md |  2 +-
 .../en/how-to-view-the-orders-details.md      | 20 ++++-----
 ...how-to-view-transactions-on-pci-gateway.md |  2 +-
 ...ith-different-layouts-for-the-same-page.md |  2 +-
 .../en/i-cant-import-the-price-table.md       |  2 +-
 .../en/i-cant-receive-emails-from-vtex.md     |  2 +-
 ...-view-the-product-in-the-search-results.md |  6 +--
 ...eting-utms-are-being-passed-to-checkout.md |  4 +-
 docs/tutorials/en/image-compression.md        |  4 +-
 .../en/importing-data-into-master-data.md     |  2 +-
 ...oving-the-performance-of-product-images.md |  2 +-
 ...roving-the-seo-of-product-listing-pages.md |  4 +-
 ...les-in-the-transactional-email-template.md |  4 +-
 docs/tutorials/en/indexes-in-master-data.md   |  8 ++--
 docs/tutorials/en/indexing-history-beta.md    | 16 +++----
 docs/tutorials/en/indexing-history.md         | 16 +++----
 ...ll-visa-checkout-in-the-extension-store.md |  4 +-
 ...g-my-orders-through-the-extension-store.md |  6 +--
 docs/tutorials/en/integrate-with-carrefour.md |  2 +-
 .../en/integrating-with-farmacias-app.md      |  6 +--
 ...egration-guide-for-erps-express-catalog.md |  2 +-
 ...integration-guide-for-erps-full-catalog.md |  2 +-
 .../en/integration-guide-for-erps-orders.md   |  8 ++--
 docs/tutorials/en/integration-interfaces.md   |  2 +-
 .../en/integration-with-google-tag-manager.md |  2 +-
 ...lligent-search-synonym-suggestions-beta.md |  4 +-
 docs/tutorials/en/intelligent-synonyms.md     |  4 +-
 ...racting-with-masterdata-through-graphql.md | 10 ++---
 docs/tutorials/en/interaction-details.md      | 12 ++---
 ...erpreting-the-data-of-the-oms-order-bar.md |  2 +-
 .../tutorials/en/introduction-to-vtex-apis.md | 10 ++---
 docs/tutorials/en/kit-registration.md         | 10 ++---
 .../lead-time-shipping-time-at-sku-level.md   |  4 +-
 ...-the-store-by-means-of-the-trade-policy.md |  2 +-
 ...ng-an-account-name-to-a-website-binding.md |  8 ++--
 ...g-urls-to-banners-using-the-site-editor.md |  4 +-
 .../en/list-the-account-workspaces.md         |  2 +-
 .../en/listing-apps-installed-in-the-store.md |  2 +-
 docs/tutorials/en/loading-dock.md             |  2 +-
 docs/tutorials/en/log-in-to-the-account.md    |  2 +-
 .../logging-in-to-the-account-with-vtex-io.md |  2 +-
 ...ics-in-the-grocery-segment-supermarkets.md |  8 ++--
 .../tutorials/en/logistics-module-overview.md | 12 ++---
 .../en/making-a-master-data-field-editable.md |  2 +-
 .../en/manage-the-sales-comissions-report.md  |  2 +-
 .../en/managing-b2b-organizations.md          |  4 +-
 .../managing-credit-with-customer-credit.md   |  4 +-
 .../en/managing-page-and-template-content.md  |  6 +--
 docs/tutorials/en/managing-pages.md           |  4 +-
 docs/tutorials/en/managing-placeholders.md    |  6 +--
 docs/tutorials/en/managing-projects.md        |  6 +--
 .../en/managing-redirects-per-binding.md      |  8 ++--
 .../en/managing-shipping-policies.md          |  4 +-
 .../en/managing-singleton-content-types.md    |  2 +-
 docs/tutorials/en/managing-url-redirects.md   |  2 +-
 docs/tutorials/en/managing-users.md           | 14 +++---
 ...-classes-and-methods-used-on-webservice.md |  2 +-
 .../en/marketplace-invited-sellers.md         |  2 +-
 .../en/marketplace-strategies-at-vtex.md      |  4 +-
 .../en/marketplaces-and-integrations.md       |  2 +-
 docs/tutorials/en/master-data-v2.md           |  4 +-
 docs/tutorials/en/master-data.md              |  2 +-
 docs/tutorials/en/media-overview.md           |  4 +-
 docs/tutorials/en/merchandising-rules-list.md |  2 +-
 ...re-not-displayed-in-the-order-dashboard.md |  4 +-
 .../en/multilevel-omnichannel-inventory.md    |  2 +-
 .../en/names-of-vtex-branches-worldwide.md    |  2 +-
 .../new-integration-with-erede-erederest.md   | 10 ++---
 docs/tutorials/en/new-my-orders-area.md       | 14 +++---
 docs/tutorials/en/offer-details.md            | 12 ++---
 docs/tutorials/en/offer-management.md         |  6 +--
 docs/tutorials/en/offer-quality-filters.md    |  4 +-
 docs/tutorials/en/offer-status.md             | 12 ++---
 ...-the-same-vtex-sellers-and-marketplaces.md |  2 +-
 docs/tutorials/en/oms-page-structure.md       | 16 +++----
 ...pening-tickets-to-vtex-support-finacial.md |  8 ++--
 .../en/opening-tickets-to-vtex-support.md     |  2 +-
 .../tutorials/en/operational-capacity-beta.md |  6 +--
 ...ization-of-shipping-options-at-checkout.md |  2 +-
 docs/tutorials/en/order-details-page.md       | 18 ++++----
 docs/tutorials/en/order-flow-and-status.md    |  8 ++--
 ...name-of-a-customer-using-the-callcenter.md |  4 +-
 ...-window-display-and-on-the-product-page.md |  2 +-
 docs/tutorials/en/orders-list.md              |  8 ++--
 docs/tutorials/en/overview-pricing-module.md  |  8 ++--
 ...-program-intranet-and-vtex-store-manual.md | 20 ++++-----
 .../tutorials/en/payment-provider-protocol.md | 16 +++----
 .../en/payu-romania-refund-details.md         |  2 +-
 docs/tutorials/en/pci-gateway-overview.md     |  2 +-
 .../en/permissions-management-in-b2b-suite.md |  2 +-
 .../en/physical-store-instore-beta.md         |  4 +-
 .../pickup-points-for-subscription-orders.md  |  2 +-
 docs/tutorials/en/pickup-points.md            |  4 +-
 .../en/planner-calendar-page-beta.md          |  6 +--
 .../en/planner-releases-page-beta.md          |  2 +-
 docs/tutorials/en/price-divergence-rule.md    |  2 +-
 .../en/price-divergence-rules-beta.md         | 10 ++---
 docs/tutorials/en/price-waterfall.md          |  2 +-
 docs/tutorials/en/pricing-rules-v2.md         | 10 ++---
 docs/tutorials/en/product-list.md             |  2 +-
 docs/tutorials/en/products-and-skus-beta.md   | 10 ++---
 docs/tutorials/en/promotion-alerts-beta.md    |  2 +-
 docs/tutorials/en/promotion-list-beta.md      |  6 +--
 docs/tutorials/en/promotion-summary.md        |  6 +--
 docs/tutorials/en/promotions-beta.md          |  8 ++--
 .../tutorials/en/promotions-simulator-beta.md |  4 +-
 docs/tutorials/en/promotions-simulator.md     |  4 +-
 .../protection-against-transaction-attacks.md | 12 ++---
 docs/tutorials/en/received-skus-beta.md       | 18 ++++----
 docs/tutorials/en/registered-ticket-flow.md   |  4 +-
 docs/tutorials/en/registering-brands.md       |  2 +-
 .../en/registering-gateway-affiliations.md    | 14 +++---
 docs/tutorials/en/registering-sku-price.md    |  6 +--
 ...-with-nominal-discount-based-on-formula.md |  8 ++--
 .../en/regular-promotion-with-reward-value.md | 12 ++---
 docs/tutorials/en/regular-promotion.md        |  4 +-
 docs/tutorials/en/releases-module-beta.md     |  4 +-
 .../en/releasing-the-store-for-production.md  |  2 +-
 docs/tutorials/en/relevance-rules.md          |  4 +-
 ...request-headers-must-only-contain-ascii.md | 10 ++---
 ...requering-authentication-on-store-pages.md |  6 +--
 .../en/requesting-the-ssl-certificate.md      |  2 +-
 .../responsibilities-in-the-vtex-ecosystem.md |  4 +-
 .../en/responsive-vs-mobile-version.md        |  4 +-
 ...ict-public-access-to-master-data-fields.md | 10 ++---
 docs/tutorials/en/roles.md                    |  2 +-
 docs/tutorials/en/rounding-rules.md           |  8 ++--
 .../en/sales-app-sales-performance.md         |  4 +-
 .../sales-associate-code-field-at-checkout.md |  4 +-
 .../en/sales-associates-instore-beta.md       |  4 +-
 docs/tutorials/en/sales-performance.md        |  4 +-
 .../scheduling-features-for-special-events.md |  2 +-
 docs/tutorials/en/scheduling-prices.md        |  4 +-
 docs/tutorials/en/search-configuration.md     |  2 +-
 .../en/search-control-fulltextsearchbox.md    |  8 ++--
 docs/tutorials/en/search-navigator-control.md |  6 +--
 docs/tutorials/en/search-parameters.md        | 12 ++---
 docs/tutorials/en/searching-for-old-orders.md |  2 +-
 .../searching-for-transactions-on-payments.md |  4 +-
 docs/tutorials/en/security-monitor.md         | 10 ++---
 docs/tutorials/en/seller-management.md        |  4 +-
 .../en/seller-portal-creating-a-promotion.md  | 12 ++---
 ...tal-getting-started-for-the-marketplace.md |  2 +-
 .../en/seller-portal-product-details.md       |  2 +-
 docs/tutorials/en/seller-portal-promotions.md |  4 +-
 .../en/seller-portal-shared-products.md       |  4 +-
 ...nd-item-price-with-tax-shown-separately.md | 16 +++----
 ...es-and-bags-attributes-to-mercado-livre.md | 10 ++---
 .../en/sending-products-to-the-marketplace.md |  4 +-
 .../en/sending-sku-attributes-to-amazon.md    |  4 +-
 docs/tutorials/en/sent-offers-beta.md         |  2 +-
 .../en/sent-offers-buybox-opportunities.md    |  4 +-
 ...r-authentication-for-recurring-payments.md |  2 +-
 .../en/setting-up-a-personal-gift-message.md  |  4 +-
 ...ct-suggestions-accessories-and-generics.md |  2 +-
 .../en/setting-up-abandoned-carts.md          | 18 ++++----
 .../tutorials/en/setting-up-amazonpay-beta.md | 22 +++++-----
 .../en/setting-up-an-index-on-master-data.md  |  8 ++--
 ...app-linking-for-payments-app-in-instore.md |  2 +-
 docs/tutorials/en/setting-up-b2b-on-vtex.md   | 10 ++---
 ...ing-up-cache-for-queries-to-master-data.md |  2 +-
 .../en/setting-up-cybersource-gateway.md      |  4 +-
 ...ent-search-integration-with-the-catalog.md |  2 +-
 .../en/setting-up-merchant-id-in-apple-pay.md | 40 ++++++++---------
 ...setting-up-payments-with-easypay-seller.md |  2 +-
 .../en/setting-up-payments-with-easypay.md    | 20 ++++-----
 .../en/setting-up-payments-with-itau-rede.md  | 12 ++---
 ...ng-up-personal-data-on-the-users-screen.md | 12 ++---
 ...ting-up-price-tables-for-specific-users.md |  6 +--
 docs/tutorials/en/setting-up-shipment.md      |  2 +-
 .../en/setting-up-sms-password-recovery.md    |  6 +--
 ...setting-up-the-css-for-the-product-zoom.md |  4 +-
 .../en/setting-up-the-notify-me-option.md     |  2 +-
 .../en/setting-up-the-price-range-filter.md   |  2 +-
 ...up-the-sales-funnel-on-google-analytics.md | 10 ++---
 .../setting-up-the-type-of-interest-rate.md   |  2 +-
 .../en/setting-up-the-voucher-list.md         |  4 +-
 .../en/setting-up-vtex-instore-logistics.md   |  2 +-
 ...-store-access-to-google-webmaster-tools.md |  8 ++--
 docs/tutorials/en/shipping-options-beta.md    |  4 +-
 docs/tutorials/en/shipping-policy.md          |  2 +-
 docs/tutorials/en/shipping-rate-template.md   |  4 +-
 docs/tutorials/en/shipping-rates.md           |  2 +-
 docs/tutorials/en/shipping-strategy.md        |  2 +-
 docs/tutorials/en/site-editor-overview.md     |  2 +-
 docs/tutorials/en/sku-bindings.md             |  2 +-
 docs/tutorials/en/special-conditions.md       | 10 ++---
 docs/tutorials/en/split-payment.md            |  8 ++--
 docs/tutorials/en/store-access-permission.md  |  2 +-
 docs/tutorials/en/store-overview-beta.md      |  8 ++--
 docs/tutorials/en/store-overview.md           | 18 ++++----
 ...ough-google-search-console-data-markers.md | 10 ++---
 docs/tutorials/en/styles-overview.md          |  2 +-
 docs/tutorials/en/subscription-plans.md       |  2 +-
 docs/tutorials/en/synonym-list.md             |  2 +-
 docs/tutorials/en/telesales-toolbar.md        |  2 +-
 .../en/testing-webservice-using-soapui.md     |  4 +-
 docs/tutorials/en/total-shipping-cost.md      |  2 +-
 .../en/transaction-flow-in-payments.md        |  2 +-
 docs/tutorials/en/transactions-events.md      | 14 +++---
 .../en/transferring-store-ownership.md        |  4 +-
 ...eshooting-errors-in-subscription-orders.md |  6 +--
 docs/tutorials/en/understanding-b2b-orders.md |  2 +-
 .../en/understanding-how-indexation-works.md  |  4 +-
 .../en/understanding-how-the-cache-works.md   |  8 ++--
 ...standing-storebuilder-and-stylesbuilder.md | 18 ++++----
 ...erstanding-the-additional-shipping-cost.md |  6 +--
 .../understanding-the-cubic-weight-factor.md  |  4 +-
 .../en/understanding-the-message-center.md    |  2 +-
 .../en/understanding-the-price-change-rule.md |  2 +-
 .../en/understanding-the-security-report.md   |  2 +-
 ...e-suspicious-purchase-notice-on-vtex-do.md |  2 +-
 .../en/understanding-the-task-list-vtex-do.md | 16 +++----
 docs/tutorials/en/understanding-the-topbar.md |  8 ++--
 .../understanding-the-updating-of-the-xml.md  |  2 +-
 ...nderstanding-vtexs-email-capture-system.md |  2 +-
 .../updating-quantity-of-skus-in-inventory.md |  2 +-
 ...ting-the-quantity-of-items-in-inventory.md |  2 +-
 docs/tutorials/en/uploading-a-product-xml.md  |  2 +-
 docs/tutorials/en/url-mapping-301-redirect.md |  2 +-
 .../using-orders-managment-filters-in-api.md  | 10 ++---
 .../en/using-recaptcha-at-checkout.md         |  6 +--
 ...-track-browsing-sessions-in-vtex-stores.md |  2 +-
 .../using-the-homepage-of-the-admin-panel.md  |  4 +-
 ...a-layout-before-moving-it-to-production.md |  4 +-
 docs/tutorials/en/view-reindex-log.md         |  2 +-
 .../visao-geral-configuracoes-de-usuario.md   |  2 +-
 .../visao-geral-da-estrutura-do-catalogo.md   |  2 +-
 docs/tutorials/en/vtex-ad-network-beta.md     |  2 +-
 docs/tutorials/en/vtex-admin-start-here.md    | 10 ++---
 docs/tutorials/en/vtex-admin-start-here1.md   | 10 ++---
 docs/tutorials/en/vtex-agreement.md           |  2 +-
 ...vtex-dashboard-guide-for-black-week-faq.md | 38 ++++++++--------
 docs/tutorials/en/vtex-do-interface.md        |  4 +-
 docs/tutorials/en/vtex-insurance.md           | 12 ++---
 ...gent-search-multilanguage-settings-beta.md |  8 ++--
 docs/tutorials/en/vtex-invoice-notifier.md    | 12 ++---
 .../en/vtex-pick-and-pack-insights.md         | 10 ++---
 .../tutorials/en/vtex-pick-and-pack-mobile.md | 20 ++++-----
 .../tutorials/en/vtex-pick-and-pack-orders.md |  6 +--
 .../en/vtex-pick-and-pack-settings.md         | 20 ++++-----
 .../en/vtex-pick-and-pack-worksheets.md       |  8 ++--
 .../en/vtex-shipping-network-dashboard.md     |  4 +-
 docs/tutorials/en/vtex-status-page.md         | 22 +++++-----
 docs/tutorials/en/warehouse.md                |  2 +-
 .../en/web-application-firewall-waf.md        |  2 +-
 docs/tutorials/en/web-page-performance.md     |  4 +-
 docs/tutorials/en/welcome-message-control.md  |  2 +-
 ...urce-and-orders-with-fulfillment-source.md |  2 +-
 docs/tutorials/en/what-are-shelves.md         |  2 +-
 docs/tutorials/en/what-are-templates.md       |  2 +-
 .../en/what-are-the-internal-utms.md          |  4 +-
 ...tivate-a-gift-multiplier-on-a-promotion.md |  2 +-
 ...r-as-revenue-in-the-billing-calculation.md |  2 +-
 .../en/what-is-a-franchise-account.md         |  4 +-
 docs/tutorials/en/what-is-binding.md          |  2 +-
 docs/tutorials/en/what-is-cms-layout.md       |  2 +-
 ...ce-between-inventory-and-warehouse-dock.md |  2 +-
 ...s-the-purpose-of-the-customized-control.md |  2 +-
 ...-when-my-report-does-not-reach-my-inbox.md |  2 +-
 ...app-ai-campaigns-management-and-details.md |  2 +-
 ...re-do-i-see-clients-that-use-recurrence.md |  2 +-
 ...where-do-i-see-the-payment-capture-date.md |  2 +-
 .../en/white-label-sellers-selection.md       | 10 ++---
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  2 +-
 .../en/wow-to-integrate-with-multiplus.md     |  4 +-
 .../es/accessing-a-client-abandoned-cart.md   | 12 ++---
 docs/tutorials/es/account-management.md       |  2 +-
 .../tutorials/es/account-settings-overview.md |  2 +-
 ...complete-list-link-on-the-category-menu.md |  4 +-
 .../es/activating-the-new-order-placed.md     |  4 +-
 ...-a-url-mapping-through-worksheet-import.md |  2 +-
 ...a-client-secret-to-log-in-with-facebook.md | 14 +++---
 ...d-a-client-secret-to-log-in-with-google.md | 24 +++++-----
 docs/tutorials/es/adding-an-attachment.md     |  2 +-
 docs/tutorials/es/adding-bin-information.md   |  4 +-
 docs/tutorials/es/adding-collections-cms.md   | 20 ++++-----
 .../es/adding-sku-specifications-or-fields.md | 12 ++---
 ...adding-specifications-or-product-fields.md | 10 ++---
 docs/tutorials/es/adding-your-brands.md       |  2 +-
 .../tutorials/es/additional-shipping-costs.md |  8 ++--
 docs/tutorials/es/admin-v4-getting-started.md | 10 ++---
 docs/tutorials/es/ads-from-vtex-sales-app.md  | 18 ++++----
 .../advertising-with-vtex-ad-network-beta.md  |  4 +-
 docs/tutorials/es/affiliates-program-app.md   | 10 ++---
 docs/tutorials/es/all-orders.md               |  4 +-
 ...mazon-multi-channel-fulfillment-mcf-app.md |  2 +-
 docs/tutorials/es/amazon-offer-matching.md    |  8 ++--
 docs/tutorials/es/analytics.md                |  4 +-
 .../es/analyze-a-products-reservations.md     |  2 +-
 docs/tutorials/es/antifraud-provider.md       | 14 +++---
 docs/tutorials/es/application-keys.md         |  4 +-
 ...roving-payment-of-the-bank-payment-slip.md |  2 +-
 docs/tutorials/es/apps-overview.md            |  2 +-
 docs/tutorials/es/assembly-options-app.md     |  2 +-
 .../es/assembly-options-in-vtex-sales-app.md  | 10 ++---
 docs/tutorials/es/assembly-options.md         |  4 +-
 .../associating-a-template-with-a-layout.md   |  2 +-
 docs/tutorials/es/audit.md                    |  4 +-
 docs/tutorials/es/authentication.md           |  2 +-
 docs/tutorials/es/autocomplete.md             |  8 ++--
 .../es/b2b-organization-general-settings.md   |  2 +-
 docs/tutorials/es/b2b-store-settings.md       |  4 +-
 docs/tutorials/es/b2b-suite-overview.md       |  2 +-
 docs/tutorials/es/bank-reconciliations.md     |  6 +--
 docs/tutorials/es/banners.md                  |  2 +-
 docs/tutorials/es/beta-price-configuration.md |  6 +--
 docs/tutorials/es/billing-module-overview.md  |  2 +-
 docs/tutorials/es/brands.md                   |  2 +-
 docs/tutorials/es/breadcrumb-control.md       |  4 +-
 ...inging-app-content-into-the-admin-panel.md |  8 ++--
 docs/tutorials/es/buy-one-get-one.md          | 12 ++---
 ...e-articulos-del-mismo-sku-en-el-carrito.md |  2 +-
 docs/tutorials/es/campaign-audiences-list.md  |  4 +-
 docs/tutorials/es/campaign-audiences.md       |  2 +-
 docs/tutorials/es/campaign-promotion.md       |  4 +-
 ...rking-hours-and-scheduled-delivery-beta.md |  6 +--
 docs/tutorials/es/catalog-overview.md         |  4 +-
 docs/tutorials/es/categories.md               |  4 +-
 .../es/category-registration-fields.md        |  6 +--
 ...egory-variations-and-attributes-mapping.md |  4 +-
 .../es/change-a-placeholder-title.md          |  4 +-
 docs/tutorials/es/change-seller.md            |  4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |  2 +-
 .../es/changing-a-pages-body-class.md         |  4 +-
 ...ult-system-texts-displayed-in-the-store.md |  4 +-
 .../changing-the-total-cost-of-the-order.md   |  4 +-
 docs/tutorials/es/changing-tracking-data.md   |  2 +-
 .../es/check-order-delivery-details.md        |  2 +-
 ...-order-delivery-deadline-was-calculated.md | 12 ++---
 docs/tutorials/es/checkout-vtex-overview.md   |  2 +-
 docs/tutorials/es/cms-folder-structure.md     |  2 +-
 docs/tutorials/es/cms-overview.md             |  2 +-
 docs/tutorials/es/cms-store-overview.md       |  2 +-
 .../es/collection-highlight-control.md        |  2 +-
 ...-sistema-esta-sendo-renderizada-no-site.md |  2 +-
 ...ipacao-dos-recebiveis-pelo-vtex-payment.md |  2 +-
 .../es/conditions-builder-usage-examples.md   |  6 +--
 ...-accounts-with-multiple-official-stores.md |  6 +--
 docs/tutorials/es/configure-cartman.md        |  8 ++--
 ...yee-benefits-using-master-data-clusters.md |  4 +-
 ...figure-template-in-smartcheckout-update.md | 32 +++++++-------
 ...configure-template-in-the-smartcheckout.md | 26 +++++------
 ...g-a-discount-for-orders-prepaid-in-full.md |  2 +-
 .../configuring-a-marketplace-trade-policy.md | 18 ++++----
 docs/tutorials/es/configuring-banners.md      |  4 +-
 ...port-for-organizations-and-cost-centers.md |  4 +-
 .../es/configuring-cargo-splitting.md         |  2 +-
 ...ng-clearsale-global-anti-fraud-solution.md |  2 +-
 .../es/configuring-clearsale-v3-antifraud.md  |  2 +-
 ...nctions-in-the-message-center-templates.md |  4 +-
 docs/tutorials/es/configuring-greenlist.md    | 10 ++---
 ...figuring-login-with-facebook-and-google.md |  6 +--
 ...automatic-payment-settlement-time-frame.md |  2 +-
 ...guring-mercado-pagos-device-fingerprint.md |  4 +-
 ...ring-my-account-conversational-commerce.md |  2 +-
 .../es/configuring-payment-gateways.md        |  2 +-
 ...-payment-with-adyenv3-in-vtex-sales-app.md | 12 ++---
 .../es/configuring-payment-with-adyenv3.md    | 14 +++---
 .../es/configuring-price-divergence-rule.md   |  6 +--
 docs/tutorials/es/configuring-prices-v2.md    |  4 +-
 .../es/configuring-product-visited.md         | 14 +++---
 ...iguring-promotions-with-a-highlightflag.md |  6 +--
 ...uring-pwa-in-your-store-framework-store.md |  6 +--
 docs/tutorials/es/configuring-redirects.md    |  2 +-
 ...guring-seller-allocation-for-buying-xky.md |  6 +--
 .../es/configuring-seo-in-your-store.md       |  6 +--
 .../es/configuring-shipping-promotions.md     | 16 +++----
 .../configuring-sign-in-with-apple-id-beta.md |  2 +-
 ...ing-the-marketplace-between-vtex-stores.md |  2 +-
 .../es/configuring-the-past-prices-control.md |  2 +-
 .../es/configuring-the-pickup-in-store.md     | 12 ++---
 .../es/configuring-the-scheduled-delivery.md  |  4 +-
 .../es/configuring-the-store-domain.md        |  2 +-
 docs/tutorials/es/configuring-your-layout.md  |  2 +-
 ...g-a-layout-from-one-web-site-to-another.md |  4 +-
 docs/tutorials/es/coupons-list-beta.md        | 12 ++---
 ...ate-a-talk-to-us-form-using-master-data.md |  2 +-
 .../es/creating-a-campaign-audience.md        |  4 +-
 ...o-guarantee-it-as-an-option-at-checkout.md |  2 +-
 docs/tutorials/es/creating-a-coupon-beta.md   |  8 ++--
 ...nformation-using-master-data-newsletter.md |  2 +-
 .../es/creating-a-more-for-less-promotion.md  | 14 +++---
 ...eating-a-personalized-master-data-query.md |  8 ++--
 .../es/creating-a-product-collection.md       | 20 ++++-----
 .../es/creating-a-subscription-plan.md        |  2 +-
 .../es/creating-a-subscription-promotion.md   |  2 +-
 docs/tutorials/es/creating-a-type-of-list.md  |  4 +-
 .../es/creating-an-oauth2-authentication.md   |  2 +-
 ...h-promotional-price-using-a-price-table.md |  4 +-
 .../tutorials/es/creating-collections-beta.md | 18 ++++----
 ...eating-custom-queries-in-master-data-v1.md |  4 +-
 docs/tutorials/es/creating-data-entity.md     |  2 +-
 .../es/creating-form-in-master-data.md        |  2 +-
 .../es/creating-landing-pages-per-binding.md  |  2 +-
 docs/tutorials/es/creating-landing-pages.md   |  2 +-
 .../es/creating-lists-on-the-site.md          |  4 +-
 ...-merchandising-rules-visual-editor-beta.md |  4 +-
 ...ating-merchandising-rules-visual-editor.md |  4 +-
 docs/tutorials/es/creating-price-tables.md    |  2 +-
 ...eating-promotion-for-a-customer-cluster.md |  8 ++--
 docs/tutorials/es/creating-promotions.md      |  2 +-
 ...etween-master-data-entities-using-admin.md | 40 ++++++++---------
 docs/tutorials/es/creating-roles.md           |  8 ++--
 .../es/creating-service-for-a-sku.md          |  2 +-
 docs/tutorials/es/creating-surchargestaxes.md |  2 +-
 .../es/creating-the-category-tree.md          |  2 +-
 .../es/creating-trigger-in-master-data.md     |  8 ++--
 docs/tutorials/es/creating-users.md           |  2 +-
 docs/tutorials/es/creating-your-promotions.md |  2 +-
 .../es/credit-card-basic-payment-flow.md      |  2 +-
 docs/tutorials/es/credit-control-overview.md  |  2 +-
 docs/tutorials/es/criar-um-produto-beta.md    | 22 +++++-----
 docs/tutorials/es/customer-credit-overview.md |  2 +-
 ...omizing-the-checkout-confirmation-pages.md |  8 ++--
 .../es/customizing-the-my-orders-section.md   |  6 +--
 .../es/customizing-your-stores-typography.md  |  4 +-
 docs/tutorials/es/data-entity.md              |  2 +-
 docs/tutorials/es/data-subject-rights.md      |  2 +-
 .../deactivating-store-skus-and-products.md   |  2 +-
 .../es/declining-order-cancelation.md         |  6 +--
 docs/tutorials/es/defining-product-prices.md  |  2 +-
 docs/tutorials/es/defining-window-displays.md | 12 ++---
 docs/tutorials/es/deleting-a-category.md      |  2 +-
 .../es/deleting-a-folder-from-cms.md          |  4 +-
 .../es/detaching-skus-by-specification.md     |  2 +-
 docs/tutorials/es/disable-cloudflare-proxy.md |  2 +-
 ...isplaying-the-store-in-another-language.md |  2 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |  4 +-
 ...ic-relevance-in-intelligent-search-beta.md |  4 +-
 docs/tutorials/es/enable-checkout-v6.md       |  4 +-
 .../enabling-2-factor-authentication-login.md | 16 +++----
 ...enabling-3ds2-for-redsys-v2-integration.md |  2 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |  6 +--
 ...ng-pwa-push-notifications-in-your-store.md |  2 +-
 .../es/entering-tax-receipts-in-the-order.md  |  2 +-
 .../es/excluding-a-product-from-the-store.md  |  2 +-
 docs/tutorials/es/explained-search.md         |  2 +-
 ...mporting-product-and-sku-specifications.md |  6 +--
 docs/tutorials/es/facebook-faq.md             |  2 +-
 .../es/facilitating-b2b-store-operation.md    |  2 +-
 ...-import-spreadsheets-fixed-price-fields.md |  2 +-
 docs/tutorials/es/filtering-all-orders.md     | 10 ++---
 ...tplaces-and-sellers-in-the-vtex-network.md |  4 +-
 ...d-questions-new-orders-module-interface.md | 12 ++---
 .../es/fulfillment-logistics-vtex.md          |  2 +-
 .../es/general-configurations-on-the-oms.md   |  2 +-
 docs/tutorials/es/generating-a-har-file.md    |  8 ++--
 docs/tutorials/es/geolocation-at-checkout.md  |  4 +-
 docs/tutorials/es/google-pay-beta.md          |  2 +-
 .../google-search-console-tracking-sitemap.md |  8 ++--
 docs/tutorials/es/headless-cms-overview.md    |  2 +-
 ...how-can-i-change-the-domain-of-my-store.md |  2 +-
 ...how-can-i-create-a-field-in-master-data.md |  4 +-
 .../es/how-can-i-create-callcenter-user.md    |  2 +-
 .../how-can-my-customer-login-to-my-store.md  | 18 ++++----
 ...e-the-https-protocol-on-my-stores-pages.md |  8 ++--
 ...-in-installments-with-compound-interest.md |  8 ++--
 .../es/how-does-promotion-proration-work.md   |  2 +-
 ...th-multiple-items-work-in-mercado-livre.md |  2 +-
 .../es/how-does-the-delivery-flow-work.md     |  2 +-
 ...arch-context-on-website-folders-operate.md |  2 +-
 .../es/how-does-the-type-of-delivery-work.md  |  2 +-
 .../tutorials/es/how-does-vtex-search-work.md |  2 +-
 .../es/how-is-pro-rata-calculated-in-vtex.md  |  2 +-
 .../es/how-is-taxhub-api-rest-structure.md    | 14 +++---
 ...-the-order-delivery-deadline-calculated.md |  2 +-
 .../how-is-the-taxhub-app-structure-in-js.md  |  2 +-
 docs/tutorials/es/how-my-account-works.md     | 18 ++++----
 .../es/how-order-authorization-works.md       |  2 +-
 .../es/how-order-authorization-workss.md      |  2 +-
 .../es/how-promotion-competition-works.md     |  2 +-
 .../es/how-recursive-marketplace-works.md     |  2 +-
 ...hen-delivery-is-done-by-the-marketplace.md |  4 +-
 ...he-automatic-compacting-of-images-works.md |  2 +-
 .../es/how-the-documents-saving-flow-works.md |  2 +-
 .../es/how-the-order-replacement-works.md     |  6 +--
 .../es/how-the-seller-portal-catalog-works.md |  2 +-
 .../how-to-activate-the-shareable-cart-app.md |  4 +-
 docs/tutorials/es/how-to-alter-a-banner.md    |  6 +--
 .../tutorials/es/how-to-archive-ratestaxes.md |  2 +-
 .../es/how-to-assemble-a-look-kit.md          |  4 +-
 .../es/how-to-capture-the-ip-of-an-order.md   |  4 +-
 .../tutorials/es/how-to-change-orders-beta.md | 12 ++---
 ...-of-vtex-store-on-google-search-console.md | 10 ++---
 .../tutorials/es/how-to-check-your-balance.md |  2 +-
 ...-configure-extra-fields-in-instore-cart.md |  4 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |  4 +-
 .../es/how-to-configure-payment-conditions.md | 10 ++---
 ...to-configure-rating-and-review-controls.md |  4 +-
 docs/tutorials/es/how-to-configure-taxhub.md  |  2 +-
 .../es/how-to-configure-the-favicon.md        |  4 +-
 ...figure-the-fingerprint-device-for-stelo.md |  8 ++--
 ...ow-to-configure-xml-for-google-shopping.md |  2 +-
 ...ng-feed-and-the-google-product-taxonomy.md |  6 +--
 ...pment-environment-with-a-mobile-version.md |  2 +-
 ...ow-to-create-a-financial-access-profile.md |  4 +-
 .../es/how-to-create-a-page-template.md       |  2 +-
 docs/tutorials/es/how-to-create-a-product.md  | 16 +++----
 ...eate-a-promotion-with-limitation-of-use.md |  2 +-
 .../es/how-to-create-a-store-name.md          |  2 +-
 ...how-to-create-a-subscription-attachment.md |  4 +-
 .../es/how-to-create-conditional-prices.md    |  2 +-
 ...ipt-customization-file-for-vtex-instore.md | 10 ++---
 ...-to-customize-a-page-using-placeholders.md | 14 +++---
 ...ize-the-checkout-ui-custom-in-the-admin.md |  8 ++--
 ...ow-to-define-the-url-for-a-product-page.md |  2 +-
 ...w-to-deprecate-and-undeprecate-your-app.md |  2 +-
 .../how-to-disable-a-transactional-email.md   |  2 +-
 .../es/how-to-download-the-vtex-invoices.md   |  6 +--
 docs/tutorials/es/how-to-find-an-sku-id.md    |  2 +-
 ...rls-that-are-inactive-or-contain-errors.md | 10 ++---
 .../es/how-to-identify-a-page-template.md     |  8 ++--
 ...ayout-errors-caused-by-javascript-files.md |  2 +-
 ...identify-promotions-applied-to-the-cart.md |  4 +-
 ...dentify-promotions-attributed-to-an-sku.md | 12 ++---
 ...import-pickup-points-using-spreadsheets.md |  6 +--
 ...llection-of-products-in-the-shop-window.md | 18 ++++----
 ...ata-when-exporting-a-prices-spreadsheet.md |  4 +-
 ...ll-the-masterpass-in-the-vtex-app-store.md | 12 ++---
 .../tutorials/es/how-to-install-the-taxhub.md |  2 +-
 .../es/how-to-integrate-with-dafiti.md        |  6 +--
 .../es/how-to-manage-subscriptions.md         |  6 +--
 .../es/how-to-manage-the-kit-stock.md         |  2 +-
 .../es/how-to-manually-invoice-an-order.md    |  4 +-
 ...how-to-register-a-store-in-vtex-instore.md |  8 ++--
 ...how-to-request-receivables-anticipation.md |  2 +-
 .../es/how-to-retrieve-the-access-password.md | 10 ++---
 .../how-to-see-orders-closed-with-benefits.md |  2 +-
 ...fine-a-default-sla-for-recurrent-orders.md |  4 +-
 .../es/how-to-set-up-fingerprint-for-payu.md  | 20 ++++-----
 ...r-to-accept-payments-with-adyen-at-vtex.md |  4 +-
 ...t-up-the-device-fingerprint-for-braspag.md | 10 ++---
 ...set-up-the-indeva-scheduled-appointment.md | 10 ++---
 docs/tutorials/es/how-to-set-up-the-zoom.md   |  6 +--
 docs/tutorials/es/how-to-set-up-visa-debit.md |  8 ++--
 .../es/how-to-use-conditions-builder-app.md   |  6 +--
 .../es/how-to-use-the-index-report.md         |  2 +-
 .../how-to-use-the-search-result-control.md   | 10 ++---
 .../es/how-to-use-the-shareable-cart-app.md   | 12 ++---
 ...ow-to-use-the-unavailable-product-class.md |  2 +-
 .../es/how-to-use-vtex-predictor-bot.md       |  8 ++--
 ...how-to-view-taxes-information-in-taxhub.md |  2 +-
 .../es/how-to-view-the-orders-details.md      | 20 ++++-----
 ...how-to-view-transactions-on-pci-gateway.md |  2 +-
 ...ith-different-layouts-for-the-same-page.md |  2 +-
 .../es/i-cant-import-the-price-table.md       |  2 +-
 .../es/i-cant-receive-emails-from-vtex.md     |  2 +-
 ...-view-the-product-in-the-search-results.md |  6 +--
 ...eting-utms-are-being-passed-to-checkout.md |  4 +-
 docs/tutorials/es/image-compression.md        |  4 +-
 .../es/importing-data-into-master-data.md     |  2 +-
 ...oving-the-performance-of-product-images.md |  2 +-
 ...roving-the-seo-of-product-listing-pages.md |  4 +-
 ...les-in-the-transactional-email-template.md |  4 +-
 docs/tutorials/es/indexes-in-master-data.md   |  8 ++--
 docs/tutorials/es/indexing-history-beta.md    | 16 +++----
 docs/tutorials/es/indexing-history.md         | 16 +++----
 ...ll-visa-checkout-in-the-extension-store.md |  4 +-
 ...g-my-orders-through-the-extension-store.md |  6 +--
 docs/tutorials/es/integrate-with-carrefour.md |  2 +-
 .../es/integrating-with-farmacias-app.md      |  6 +--
 .../es/integration-guide-for-erps-orders.md   |  8 ++--
 docs/tutorials/es/integration-interfaces.md   |  2 +-
 .../es/integration-with-google-tag-manager.md |  2 +-
 ...lligent-search-synonym-suggestions-beta.md |  4 +-
 docs/tutorials/es/intelligent-synonyms.md     |  4 +-
 ...racting-with-masterdata-through-graphql.md | 10 ++---
 docs/tutorials/es/interaction-details.md      | 12 ++---
 ...erpreting-the-data-of-the-oms-order-bar.md |  2 +-
 .../tutorials/es/introduction-to-vtex-apis.md | 10 ++---
 docs/tutorials/es/kit-registration.md         | 10 ++---
 .../lead-time-shipping-time-at-sku-level.md   |  4 +-
 ...-the-store-by-means-of-the-trade-policy.md |  2 +-
 ...ng-an-account-name-to-a-website-binding.md |  8 ++--
 ...g-urls-to-banners-using-the-site-editor.md |  4 +-
 .../es/list-the-account-workspaces.md         |  2 +-
 .../es/listing-apps-installed-in-the-store.md |  2 +-
 docs/tutorials/es/loading-dock.md             |  2 +-
 .../logging-in-to-the-account-with-vtex-io.md |  2 +-
 ...ics-in-the-grocery-segment-supermarkets.md |  8 ++--
 .../tutorials/es/logistics-module-overview.md | 12 ++---
 .../es/making-a-master-data-field-editable.md |  2 +-
 .../es/manage-the-sales-comissions-report.md  |  2 +-
 .../es/managing-b2b-organizations.md          |  4 +-
 .../tutorials/es/managing-content-versions.md |  2 +-
 .../managing-credit-with-customer-credit.md   |  4 +-
 .../es/managing-page-and-template-content.md  |  6 +--
 docs/tutorials/es/managing-pages.md           |  4 +-
 docs/tutorials/es/managing-placeholders.md    |  6 +--
 docs/tutorials/es/managing-projects.md        |  6 +--
 .../es/managing-redirects-per-binding.md      |  8 ++--
 .../es/managing-shipping-policies.md          |  4 +-
 .../es/managing-singleton-content-types.md    |  2 +-
 docs/tutorials/es/managing-url-redirects.md   |  2 +-
 docs/tutorials/es/managing-users.md           | 14 +++---
 ...-classes-and-methods-used-on-webservice.md |  2 +-
 ...re-categories-variations-and-attributes.md |  2 +-
 .../es/marketplace-invited-sellers.md         |  2 +-
 .../es/marketplace-strategies-at-vtex.md      |  4 +-
 .../es/marketplaces-and-integrations.md       |  2 +-
 docs/tutorials/es/master-data-v2.md           |  4 +-
 docs/tutorials/es/master-data.md              |  2 +-
 .../es/match-offers-mercado-livre.md          | 18 ++++----
 docs/tutorials/es/media-overview.md           |  4 +-
 docs/tutorials/es/mercado-libre-promotions.md |  2 +-
 ...ercado-livre-automobilist-compatibility.md |  4 +-
 docs/tutorials/es/mercado-livre-faq.md        |  8 ++--
 docs/tutorials/es/merchandising-rules-list.md |  2 +-
 ...re-not-displayed-in-the-order-dashboard.md |  4 +-
 .../es/migrating-ads-in-mercado-livre.md      |  2 +-
 .../es/multilevel-omnichannel-inventory.md    |  2 +-
 ...my-ad-is-not-displayed-on-mercado-livre.md |  4 +-
 .../new-integration-with-erede-erederest.md   | 10 ++---
 docs/tutorials/es/new-my-orders-area.md       | 14 +++---
 docs/tutorials/es/offer-details.md            | 12 ++---
 docs/tutorials/es/offer-management.md         |  6 +--
 docs/tutorials/es/offer-quality-filters.md    |  4 +-
 docs/tutorials/es/offer-status.md             | 12 ++---
 ...-the-same-vtex-sellers-and-marketplaces.md |  2 +-
 docs/tutorials/es/oms-page-structure.md       | 16 +++----
 ...pening-tickets-to-vtex-support-finacial.md |  8 ++--
 .../es/opening-tickets-to-vtex-support.md     |  2 +-
 .../tutorials/es/operational-capacity-beta.md |  6 +--
 ...ization-of-shipping-options-at-checkout.md |  2 +-
 docs/tutorials/es/order-details-page.md       | 18 ++++----
 docs/tutorials/es/order-flow-and-status.md    |  8 ++--
 ...name-of-a-customer-using-the-callcenter.md |  4 +-
 ...-window-display-and-on-the-product-page.md |  2 +-
 docs/tutorials/es/orders-list.md              |  8 ++--
 docs/tutorials/es/overview-pricing-module.md  |  8 ++--
 docs/tutorials/es/pages-overview.md           |  2 +-
 ...-program-intranet-and-vtex-store-manual.md | 20 ++++-----
 .../tutorials/es/payment-provider-protocol.md | 14 +++---
 .../es/payu-romania-refund-details.md         |  2 +-
 docs/tutorials/es/pci-gateway-overview.md     |  2 +-
 .../es/permissions-management-in-b2b-suite.md |  2 +-
 .../es/physical-store-instore-beta.md         |  4 +-
 .../pickup-points-for-subscription-orders.md  |  2 +-
 docs/tutorials/es/pickup-points.md            |  4 +-
 .../es/planner-calendar-page-beta.md          |  6 +--
 .../es/planner-releases-page-beta.md          |  2 +-
 docs/tutorials/es/price-divergence-rule.md    |  2 +-
 .../es/price-divergence-rules-beta.md         | 10 ++---
 docs/tutorials/es/price-waterfall.md          |  2 +-
 docs/tutorials/es/pricing-rules-v2.md         | 10 ++---
 docs/tutorials/es/product-list.md             |  2 +-
 docs/tutorials/es/products-and-skus-beta.md   | 10 ++---
 docs/tutorials/es/promotion-alerts-beta.md    |  2 +-
 docs/tutorials/es/promotion-list-beta.md      |  6 +--
 docs/tutorials/es/promotion-summary.md        |  6 +--
 docs/tutorials/es/promotions-beta.md          |  8 ++--
 .../tutorials/es/promotions-simulator-beta.md |  4 +-
 docs/tutorials/es/promotions-simulator.md     |  4 +-
 .../protection-against-transaction-attacks.md | 12 ++---
 docs/tutorials/es/received-skus-beta.md       | 18 ++++----
 docs/tutorials/es/registered-ticket-flow.md   |  4 +-
 docs/tutorials/es/registering-brands.md       |  2 +-
 .../es/registering-gateway-affiliations.md    | 14 +++---
 docs/tutorials/es/registering-sku-price.md    |  6 +--
 ...-with-nominal-discount-based-on-formula.md |  8 ++--
 .../es/regular-promotion-with-reward-value.md | 12 ++---
 docs/tutorials/es/regular-promotion.md        |  4 +-
 docs/tutorials/es/releases-module-beta.md     |  4 +-
 .../es/releasing-the-store-for-production.md  |  2 +-
 docs/tutorials/es/relevance-rules.md          |  4 +-
 ...request-headers-must-only-contain-ascii.md | 10 ++---
 ...requering-authentication-on-store-pages.md |  6 +--
 .../es/requesting-the-ssl-certificate.md      |  2 +-
 .../responsibilities-in-the-vtex-ecosystem.md |  4 +-
 .../es/responsive-vs-mobile-version.md        |  4 +-
 ...ict-public-access-to-master-data-fields.md | 10 ++---
 docs/tutorials/es/roles.md                    |  2 +-
 docs/tutorials/es/rounding-rules.md           |  8 ++--
 .../es/sales-app-sales-performance.md         |  4 +-
 .../sales-associate-code-field-at-checkout.md |  4 +-
 .../es/sales-associates-instore-beta.md       |  4 +-
 docs/tutorials/es/sales-performance.md        |  4 +-
 .../scheduling-features-for-special-events.md |  2 +-
 docs/tutorials/es/scheduling-prices.md        |  4 +-
 docs/tutorials/es/search-configuration.md     |  2 +-
 .../es/search-control-fulltextsearchbox.md    |  8 ++--
 docs/tutorials/es/search-navigator-control.md |  6 +--
 docs/tutorials/es/search-parameters.md        | 12 ++---
 docs/tutorials/es/searching-for-old-orders.md |  2 +-
 .../searching-for-transactions-on-payments.md |  4 +-
 docs/tutorials/es/security-monitor.md         | 10 ++---
 ...ng-stock-for-orders-mercado-envios-full.md |  2 +-
 docs/tutorials/es/seller-management.md        |  4 +-
 .../es/seller-portal-creating-a-promotion.md  | 12 ++---
 ...tal-getting-started-for-the-marketplace.md |  2 +-
 .../es/seller-portal-product-details.md       |  2 +-
 docs/tutorials/es/seller-portal-promotions.md |  4 +-
 .../es/seller-portal-shared-products.md       |  4 +-
 ...nd-item-price-with-tax-shown-separately.md | 16 +++----
 ...es-and-bags-attributes-to-mercado-livre.md | 10 ++---
 .../es/sending-products-to-the-marketplace.md |  4 +-
 .../es/sending-sku-attributes-to-amazon.md    |  4 +-
 docs/tutorials/es/sent-offers-beta.md         |  2 +-
 .../es/sent-offers-buybox-opportunities.md    |  6 +--
 ...r-authentication-for-recurring-payments.md |  2 +-
 .../es/setting-up-a-personal-gift-message.md  |  4 +-
 ...ct-suggestions-accessories-and-generics.md |  2 +-
 .../es/setting-up-abandoned-carts.md          | 18 ++++----
 .../es/setting-up-an-index-on-master-data.md  |  8 ++--
 ...app-linking-for-payments-app-in-instore.md |  2 +-
 docs/tutorials/es/setting-up-b2b-on-vtex.md   | 10 ++---
 ...ing-up-cache-for-queries-to-master-data.md |  2 +-
 .../es/setting-up-cybersource-gateway.md      |  4 +-
 ...ent-search-integration-with-the-catalog.md |  2 +-
 .../es/setting-up-merchant-id-in-apple-pay.md | 40 ++++++++---------
 ...setting-up-payments-with-easypay-seller.md |  2 +-
 .../es/setting-up-payments-with-easypay.md    | 20 ++++-----
 .../es/setting-up-payments-with-itau-rede.md  | 12 ++---
 ...ng-up-personal-data-on-the-users-screen.md | 12 ++---
 ...ting-up-price-tables-for-specific-users.md |  2 +-
 docs/tutorials/es/setting-up-shipment.md      |  2 +-
 .../es/setting-up-sms-password-recovery.md    |  6 +--
 .../es/setting-up-the-critical-stock-alert.md |  2 +-
 ...setting-up-the-css-for-the-product-zoom.md |  4 +-
 .../es/setting-up-the-notify-me-option.md     |  2 +-
 .../es/setting-up-the-price-range-filter.md   |  2 +-
 ...up-the-sales-funnel-on-google-analytics.md | 10 ++---
 .../setting-up-the-type-of-interest-rate.md   |  2 +-
 .../es/setting-up-the-voucher-list.md         |  4 +-
 .../es/setting-up-vtex-instore-logistics.md   |  2 +-
 ...-store-access-to-google-webmaster-tools.md |  8 ++--
 docs/tutorials/es/shipping-options-beta.md    |  4 +-
 docs/tutorials/es/shipping-policy.md          |  2 +-
 docs/tutorials/es/shipping-rate-template.md   |  4 +-
 docs/tutorials/es/shipping-rates.md           |  2 +-
 docs/tutorials/es/shipping-strategy.md        |  2 +-
 docs/tutorials/es/site-editor-overview.md     |  2 +-
 docs/tutorials/es/sku-bindings.md             |  2 +-
 docs/tutorials/es/special-conditions.md       | 10 ++---
 docs/tutorials/es/split-payment.md            |  8 ++--
 docs/tutorials/es/store-access-permission.md  |  2 +-
 docs/tutorials/es/store-overview-beta.md      |  8 ++--
 docs/tutorials/es/store-overview.md           | 18 ++++----
 docs/tutorials/es/storefront-overview.md      |  2 +-
 ...ough-google-search-console-data-markers.md | 10 ++---
 docs/tutorials/es/styles-overview.md          |  2 +-
 docs/tutorials/es/subscription-plans.md       |  2 +-
 docs/tutorials/es/synonym-list.md             |  2 +-
 docs/tutorials/es/telesales-toolbar.md        |  2 +-
 .../es/testing-webservice-using-soapui.md     |  4 +-
 docs/tutorials/es/total-shipping-cost.md      |  2 +-
 .../es/transaction-flow-in-payments.md        |  2 +-
 ...actional-emails-for-subscription-orders.md |  2 +-
 docs/tutorials/es/transactions-events.md      | 14 +++---
 .../es/transferring-store-ownership.md        |  4 +-
 ...eshooting-errors-in-subscription-orders.md |  4 +-
 docs/tutorials/es/understanding-b2b-orders.md |  2 +-
 .../es/understanding-how-indexation-works.md  |  4 +-
 .../es/understanding-how-the-cache-works.md   |  8 ++--
 ...standing-storebuilder-and-stylesbuilder.md | 18 ++++----
 ...erstanding-the-additional-shipping-cost.md |  6 +--
 .../understanding-the-cubic-weight-factor.md  |  4 +-
 .../es/understanding-the-message-center.md    |  2 +-
 .../es/understanding-the-price-change-rule.md |  2 +-
 .../es/understanding-the-security-report.md   |  2 +-
 ...e-suspicious-purchase-notice-on-vtex-do.md |  2 +-
 .../es/understanding-the-task-list-vtex-do.md | 16 +++----
 docs/tutorials/es/understanding-the-topbar.md |  8 ++--
 .../understanding-the-updating-of-the-xml.md  |  2 +-
 ...nderstanding-vtexs-email-capture-system.md |  2 +-
 .../untitled-entry-2017-07-03-at-03-49-03.md  | 16 +++----
 .../updating-quantity-of-skus-in-inventory.md |  2 +-
 ...ting-the-quantity-of-items-in-inventory.md |  2 +-
 docs/tutorials/es/uploading-a-product-xml.md  |  2 +-
 docs/tutorials/es/url-mapping-301-redirect.md |  2 +-
 .../using-orders-managment-filters-in-api.md  | 10 ++---
 .../es/using-recaptcha-at-checkout.md         |  6 +--
 ...-track-browsing-sessions-in-vtex-stores.md |  2 +-
 .../using-the-homepage-of-the-admin-panel.md  |  4 +-
 ...a-layout-before-moving-it-to-production.md |  4 +-
 docs/tutorials/es/view-reindex-log.md         |  2 +-
 .../visao-geral-configuracoes-de-usuario.md   |  2 +-
 .../visao-geral-da-estrutura-do-catalogo.md   |  2 +-
 docs/tutorials/es/vtex-ad-network-beta.md     |  2 +-
 docs/tutorials/es/vtex-admin-start-here.md    | 10 ++---
 docs/tutorials/es/vtex-admin-start-here1.md   | 10 ++---
 docs/tutorials/es/vtex-agreement.md           |  2 +-
 ...vtex-dashboard-guide-for-black-week-faq.md | 38 ++++++++--------
 docs/tutorials/es/vtex-do-interface.md        |  4 +-
 docs/tutorials/es/vtex-insurance.md           | 12 ++---
 ...gent-search-multilanguage-settings-beta.md |  8 ++--
 docs/tutorials/es/vtex-invoice-notifier.md    |  4 +-
 .../es/vtex-pick-and-pack-fulfillment.md      | 44 +++++++++----------
 .../es/vtex-pick-and-pack-insights.md         | 10 ++---
 .../tutorials/es/vtex-pick-and-pack-mobile.md | 20 ++++-----
 .../tutorials/es/vtex-pick-and-pack-orders.md |  6 +--
 .../es/vtex-pick-and-pack-settings.md         | 20 ++++-----
 .../es/vtex-pick-and-pack-worksheets.md       |  8 ++--
 .../es/vtex-shipping-network-dashboard.md     |  4 +-
 docs/tutorials/es/vtex-status-page.md         | 22 +++++-----
 docs/tutorials/es/warehouse.md                |  2 +-
 .../es/web-application-firewall-waf.md        |  2 +-
 docs/tutorials/es/web-page-performance.md     |  4 +-
 docs/tutorials/es/welcome-message-control.md  |  2 +-
 ...urce-and-orders-with-fulfillment-source.md |  2 +-
 docs/tutorials/es/what-are-shelves.md         |  2 +-
 docs/tutorials/es/what-are-templates.md       |  2 +-
 .../es/what-are-the-internal-utms.md          |  4 +-
 ...tivate-a-gift-multiplier-on-a-promotion.md |  2 +-
 ...r-as-revenue-in-the-billing-calculation.md |  2 +-
 .../es/what-is-a-franchise-account.md         |  4 +-
 docs/tutorials/es/what-is-binding.md          |  2 +-
 docs/tutorials/es/what-is-cms-layout.md       |  2 +-
 ...ce-between-inventory-and-warehouse-dock.md |  2 +-
 ...s-the-purpose-of-the-customized-control.md |  2 +-
 ...-when-my-report-does-not-reach-my-inbox.md |  2 +-
 ...app-ai-campaigns-management-and-details.md |  2 +-
 ...re-do-i-see-clients-that-use-recurrence.md |  2 +-
 ...where-do-i-see-the-payment-capture-date.md |  2 +-
 .../es/white-label-sellers-selection.md       | 10 ++---
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  2 +-
 .../es/wow-to-integrate-with-multiplus.md     |  4 +-
 .../pt/accessing-a-client-abandoned-cart.md   | 12 ++---
 docs/tutorials/pt/account-management.md       |  2 +-
 .../tutorials/pt/account-settings-overview.md |  2 +-
 docs/tutorials/pt/account-summary.md          | 14 +++---
 ...complete-list-link-on-the-category-menu.md |  4 +-
 .../pt/activating-the-new-order-placed.md     |  4 +-
 .../pt/active-campaign-suiteshare.md          | 10 ++---
 ...-a-url-mapping-through-worksheet-import.md |  2 +-
 ...a-client-secret-to-log-in-with-facebook.md | 14 +++---
 ...d-a-client-secret-to-log-in-with-google.md | 24 +++++-----
 docs/tutorials/pt/adding-an-attachment.md     |  2 +-
 docs/tutorials/pt/adding-bin-information.md   |  4 +-
 docs/tutorials/pt/adding-collections-cms.md   | 20 ++++-----
 .../pt/adding-sku-specifications-or-fields.md | 12 ++---
 ...adding-specifications-or-product-fields.md | 10 ++---
 docs/tutorials/pt/adding-your-brands.md       |  2 +-
 .../tutorials/pt/additional-shipping-costs.md |  8 ++--
 docs/tutorials/pt/admin-v4-getting-started.md | 10 ++---
 docs/tutorials/pt/ads-from-vtex-sales-app.md  | 18 ++++----
 .../advertising-with-vtex-ad-network-beta.md  |  4 +-
 docs/tutorials/pt/affiliates-program-app.md   | 10 ++---
 docs/tutorials/pt/all-orders.md               |  4 +-
 docs/tutorials/pt/amaro-integration.md        |  2 +-
 ...mazon-multi-channel-fulfillment-mcf-app.md |  2 +-
 docs/tutorials/pt/amazon-offer-matching.md    |  8 ++--
 docs/tutorials/pt/analytics.md                |  4 +-
 .../pt/analyze-a-products-reservations.md     |  2 +-
 docs/tutorials/pt/analyze-suiteshare.md       | 18 ++++----
 docs/tutorials/pt/anapro-suiteshare.md        | 10 ++---
 docs/tutorials/pt/antifraud-provider.md       | 14 +++---
 docs/tutorials/pt/application-keys.md         |  4 +-
 ...roving-payment-of-the-bank-payment-slip.md |  2 +-
 docs/tutorials/pt/apps-overview.md            |  2 +-
 docs/tutorials/pt/assembly-options-app.md     |  2 +-
 .../pt/assembly-options-in-vtex-sales-app.md  | 10 ++---
 docs/tutorials/pt/assembly-options.md         |  4 +-
 .../associating-a-template-with-a-layout.md   |  2 +-
 docs/tutorials/pt/audit.md                    |  4 +-
 docs/tutorials/pt/authentication-page.md      |  2 +-
 docs/tutorials/pt/authentication.md           |  2 +-
 docs/tutorials/pt/autocomplete.md             |  8 ++--
 .../pt/b2b-organization-general-settings.md   |  2 +-
 docs/tutorials/pt/b2b-store-settings.md       |  4 +-
 docs/tutorials/pt/b2b-suite-overview.md       |  2 +-
 docs/tutorials/pt/bank-reconciliations.md     |  6 +--
 docs/tutorials/pt/banners.md                  |  2 +-
 docs/tutorials/pt/beta-price-configuration.md |  6 +--
 docs/tutorials/pt/billing-module-overview.md  |  2 +-
 docs/tutorials/pt/bitrix24.md                 | 16 +++----
 docs/tutorials/pt/black-friday-checklist.md   |  8 ++--
 docs/tutorials/pt/black-week.md               |  8 ++--
 docs/tutorials/pt/brands.md                   |  2 +-
 docs/tutorials/pt/breadcrumb-control.md       |  4 +-
 ...inging-app-content-into-the-admin-panel.md |  8 ++--
 docs/tutorials/pt/buy-one-get-one.md          | 12 ++---
 .../tutorials/pt/call-to-action-suiteshare.md | 26 +++++------
 ...e-articulos-del-mismo-sku-en-el-carrito.md |  2 +-
 docs/tutorials/pt/campaign-audiences-list.md  |  4 +-
 docs/tutorials/pt/campaign-audiences.md       |  2 +-
 docs/tutorials/pt/campaign-promotion.md       |  4 +-
 docs/tutorials/pt/capture-form-suiteshare.md  | 22 +++++-----
 ...rking-hours-and-scheduled-delivery-beta.md |  6 +--
 docs/tutorials/pt/catalog-overview.md         |  4 +-
 docs/tutorials/pt/categories.md               |  4 +-
 .../pt/category-registration-fields.md        |  6 +--
 ...egory-variations-and-attributes-mapping.md |  6 +--
 .../pt/change-a-placeholder-title.md          |  6 +--
 ...-seller-of-an-vtex-sales-app-order-beta.md |  8 ++--
 docs/tutorials/pt/change-seller.md            |  4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |  2 +-
 .../pt/changing-a-pages-body-class.md         |  4 +-
 ...ult-system-texts-displayed-in-the-store.md |  4 +-
 .../changing-the-total-cost-of-the-order.md   |  4 +-
 docs/tutorials/pt/changing-tracking-data.md   |  2 +-
 docs/tutorials/pt/chat.md                     | 20 ++++-----
 .../pt/check-order-delivery-details.md        |  2 +-
 ...-order-delivery-deadline-was-calculated.md | 12 ++---
 docs/tutorials/pt/checkout-vtex-overview.md   |  2 +-
 docs/tutorials/pt/cms-folder-structure.md     |  2 +-
 docs/tutorials/pt/cms-overview.md             |  2 +-
 docs/tutorials/pt/cms-store-overview.md       |  2 +-
 .../pt/collection-highlight-control.md        |  2 +-
 ...-sistema-esta-sendo-renderizada-no-site.md |  2 +-
 ...ipacao-dos-recebiveis-pelo-vtex-payment.md |  2 +-
 .../pt/conditions-builder-usage-examples.md   | 14 +++---
 docs/tutorials/pt/configuracao-de-precos.md   |  6 +--
 docs/tutorials/pt/configurar-o-cartman.md     |  6 +--
 ...-accounts-with-multiple-official-stores.md |  6 +--
 docs/tutorials/pt/configure-cartman.md        |  8 ++--
 ...e-direct-consumer-credit-cdc-by-losango.md |  6 +--
 ...yee-benefits-using-master-data-clusters.md |  4 +-
 ...figure-template-in-smartcheckout-update.md | 32 +++++++-------
 ...configure-template-in-the-smartcheckout.md | 28 ++++++------
 ...g-a-discount-for-orders-prepaid-in-full.md |  2 +-
 .../configuring-a-marketplace-trade-policy.md | 18 ++++----
 docs/tutorials/pt/configuring-banners.md      |  4 +-
 ...port-for-organizations-and-cost-centers.md |  4 +-
 .../pt/configuring-cargo-splitting.md         |  2 +-
 ...ng-clearsale-global-anti-fraud-solution.md |  2 +-
 .../pt/configuring-clearsale-v3-antifraud.md  |  2 +-
 ...nctions-in-the-message-center-templates.md |  4 +-
 docs/tutorials/pt/configuring-greenlist.md    | 10 ++---
 ...figuring-login-with-facebook-and-google.md |  6 +--
 ...automatic-payment-settlement-time-frame.md |  2 +-
 ...guring-mercado-pagos-device-fingerprint.md |  4 +-
 ...ring-my-account-conversational-commerce.md |  2 +-
 .../pt/configuring-payment-gateways.md        |  2 +-
 ...-payment-with-adyenv3-in-vtex-sales-app.md | 12 ++---
 .../pt/configuring-payment-with-adyenv3.md    | 14 +++---
 ...ng-physical-stores-integration-with-b2w.md |  8 ++--
 .../pt/configuring-price-divergence-rule.md   |  6 +--
 docs/tutorials/pt/configuring-prices-v2.md    |  4 +-
 .../pt/configuring-product-visited.md         | 14 +++---
 ...iguring-promotions-with-a-highlightflag.md |  6 +--
 ...uring-pwa-in-your-store-framework-store.md |  6 +--
 docs/tutorials/pt/configuring-redirects.md    |  2 +-
 ...guring-seller-allocation-for-buying-xky.md |  6 +--
 .../pt/configuring-seo-in-your-store.md       |  6 +--
 .../pt/configuring-shipping-promotions.md     | 16 +++----
 .../configuring-sign-in-with-apple-id-beta.md |  2 +-
 .../pt/configuring-the-additional-freight.md  |  2 +-
 .../pt/configuring-the-global-checkout.md     |  2 +-
 ...ing-the-marketplace-between-vtex-stores.md |  2 +-
 .../pt/configuring-the-past-prices-control.md |  2 +-
 .../pt/configuring-the-pickup-in-store.md     | 12 ++---
 .../pt/configuring-the-scheduled-delivery.md  |  4 +-
 .../pt/configuring-the-store-domain.md        |  2 +-
 ...g-a-layout-from-one-web-site-to-another.md |  4 +-
 docs/tutorials/pt/coupons-list-beta.md        | 12 ++---
 ...ate-a-talk-to-us-form-using-master-data.md |  2 +-
 .../pt/creating-a-campaign-audience.md        |  4 +-
 ...o-guarantee-it-as-an-option-at-checkout.md |  2 +-
 docs/tutorials/pt/creating-a-coupon-beta.md   |  8 ++--
 ...nformation-using-master-data-newsletter.md |  2 +-
 .../pt/creating-a-more-for-less-promotion.md  | 14 +++---
 ...eating-a-personalized-master-data-query.md |  8 ++--
 .../pt/creating-a-product-collection.md       | 20 ++++-----
 .../pt/creating-a-subscription-plan.md        |  2 +-
 .../pt/creating-a-subscription-promotion.md   |  2 +-
 docs/tutorials/pt/creating-a-type-of-list.md  |  4 +-
 .../pt/creating-an-oauth2-authentication.md   |  2 +-
 ...h-promotional-price-using-a-price-table.md |  4 +-
 .../tutorials/pt/creating-collections-beta.md | 18 ++++----
 ...eating-custom-queries-in-master-data-v1.md |  4 +-
 docs/tutorials/pt/creating-data-entity.md     |  2 +-
 .../pt/creating-form-in-master-data.md        |  2 +-
 .../pt/creating-landing-pages-per-binding.md  |  2 +-
 docs/tutorials/pt/creating-landing-pages.md   |  2 +-
 ...-merchandising-rules-visual-editor-beta.md |  4 +-
 ...ating-merchandising-rules-visual-editor.md |  4 +-
 docs/tutorials/pt/creating-price-tables.md    |  2 +-
 ...eating-promotion-for-a-customer-cluster.md |  8 ++--
 docs/tutorials/pt/creating-promotions.md      |  2 +-
 ...etween-master-data-entities-using-admin.md |  8 ++--
 docs/tutorials/pt/creating-roles.md           |  8 ++--
 .../pt/creating-service-for-a-sku.md          |  2 +-
 docs/tutorials/pt/creating-surchargestaxes.md |  2 +-
 .../pt/creating-the-category-tree.md          |  2 +-
 .../pt/creating-trigger-in-master-data.md     |  8 ++--
 docs/tutorials/pt/creating-your-promotions.md |  2 +-
 .../pt/credit-card-basic-payment-flow.md      |  2 +-
 docs/tutorials/pt/credit-control-overview.md  |  2 +-
 docs/tutorials/pt/criar-um-produto-beta.md    | 22 +++++-----
 docs/tutorials/pt/crm-zen-suiteshare.md       | 10 ++---
 docs/tutorials/pt/customer-credit-overview.md |  2 +-
 docs/tutorials/pt/customize-suiteshare.md     | 14 +++---
 ...omizing-the-checkout-confirmation-pages.md |  8 ++--
 .../pt/customizing-the-my-orders-section.md   |  6 +--
 .../pt/customizing-your-stores-typography.md  |  4 +-
 docs/tutorials/pt/data-entity.md              |  2 +-
 docs/tutorials/pt/data-subject-rights.md      |  2 +-
 .../deactivating-store-skus-and-products.md   |  2 +-
 .../pt/declining-order-cancelation.md         |  6 +--
 docs/tutorials/pt/defining-product-prices.md  |  2 +-
 docs/tutorials/pt/defining-window-displays.md | 12 ++---
 docs/tutorials/pt/deleting-a-category.md      |  2 +-
 .../pt/deleting-a-folder-from-cms.md          |  4 +-
 ...liveries-progress-vtex-shipping-network.md |  4 +-
 .../pt/detaching-skus-by-specification.md     |  2 +-
 .../pt/direct-migration-magazine-luiza.md     |  4 +-
 docs/tutorials/pt/disable-cloudflare-proxy.md |  2 +-
 ...isplaying-the-store-in-another-language.md |  2 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |  4 +-
 ...ic-relevance-in-intelligent-search-beta.md |  4 +-
 .../pt/editing-my-data-suiteshare.md          |  8 ++--
 docs/tutorials/pt/enable-checkout-v6.md       |  4 +-
 .../enabling-2-factor-authentication-login.md |  8 ++--
 ...enabling-3ds2-for-redsys-v2-integration.md |  2 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |  8 ++--
 ...ng-pwa-push-notifications-in-your-store.md |  2 +-
 .../pt/entering-tax-receipts-in-the-order.md  |  2 +-
 docs/tutorials/pt/exact-sales-suiteshare.md   |  6 +--
 .../pt/excluding-a-product-from-the-store.md  |  2 +-
 docs/tutorials/pt/explained-search.md         |  2 +-
 ...mporting-product-and-sku-specifications.md |  6 +--
 docs/tutorials/pt/facebook-faq.md             |  2 +-
 ...acebook-liberacao-de-dominio-suiteshare.md |  2 +-
 .../pt/facilitating-b2b-store-operation.md    |  2 +-
 ...-import-spreadsheets-fixed-price-fields.md |  2 +-
 docs/tutorials/pt/filtering-all-orders.md     | 10 ++---
 ...tplaces-and-sellers-in-the-vtex-network.md |  4 +-
 ...d-questions-new-orders-module-interface.md | 12 ++---
 .../pt/fulfillment-logistics-vtex.md          |  2 +-
 docs/tutorials/pt/fulfillment-magalu.md       |  2 +-
 .../pt/general-configurations-on-the-oms.md   |  2 +-
 docs/tutorials/pt/generating-a-har-file.md    | 10 ++---
 docs/tutorials/pt/geolocalizado-suiteshare.md | 10 ++---
 docs/tutorials/pt/geolocation-at-checkout.md  |  4 +-
 docs/tutorials/pt/google-pay-beta.md          |  2 +-
 .../google-search-console-tracking-sitemap.md |  8 ++--
 docs/tutorials/pt/headless-cms-overview.md    |  2 +-
 ...how-can-i-change-the-domain-of-my-store.md |  2 +-
 ...how-can-i-create-a-field-in-master-data.md |  4 +-
 .../pt/how-can-i-create-callcenter-user.md    |  2 +-
 ...w-can-i-make-master-data-field-editable.md |  8 ++--
 ...w-can-i-track-the-status-of-my-disputes.md |  2 +-
 .../how-can-my-customer-login-to-my-store.md  | 18 ++++----
 ...e-the-https-protocol-on-my-stores-pages.md |  8 ++--
 ...-in-installments-with-compound-interest.md |  8 ++--
 .../pt/how-does-promotion-proration-work.md   |  2 +-
 ...th-multiple-items-work-in-mercado-livre.md |  2 +-
 .../pt/how-does-the-delivery-flow-work.md     |  2 +-
 .../pt/how-does-the-score-field-work.md       |  2 +-
 ...arch-context-on-website-folders-operate.md |  2 +-
 .../pt/how-does-the-type-of-delivery-work.md  |  2 +-
 .../tutorials/pt/how-does-vtex-search-work.md |  2 +-
 .../pt/how-is-pro-rata-calculated-in-vtex.md  |  2 +-
 .../pt/how-is-taxhub-api-rest-structure.md    | 14 +++---
 ...-the-order-delivery-deadline-calculated.md |  2 +-
 .../how-is-the-taxhub-app-structure-in-js.md  |  2 +-
 docs/tutorials/pt/how-my-account-works.md     | 18 ++++----
 .../pt/how-order-authorization-works.md       |  2 +-
 .../pt/how-order-authorization-workss.md      |  8 ++--
 .../pt/how-promotion-competition-works.md     |  2 +-
 .../pt/how-recursive-marketplace-works.md     |  2 +-
 ...hen-delivery-is-done-by-the-marketplace.md |  4 +-
 ...he-automatic-compacting-of-images-works.md |  2 +-
 .../pt/how-the-documents-saving-flow-works.md |  2 +-
 .../pt/how-the-order-replacement-works.md     |  6 +--
 .../pt/how-the-seller-portal-catalog-works.md |  2 +-
 .../how-to-activate-the-shareable-cart-app.md |  4 +-
 docs/tutorials/pt/how-to-alter-a-banner.md    |  6 +--
 .../tutorials/pt/how-to-archive-ratestaxes.md |  2 +-
 .../pt/how-to-assemble-a-look-kit.md          |  6 +--
 .../pt/how-to-capture-the-ip-of-an-order.md   |  4 +-
 .../tutorials/pt/how-to-change-orders-beta.md | 12 ++---
 ...-of-vtex-store-on-google-search-console.md | 10 ++---
 .../tutorials/pt/how-to-check-your-balance.md |  2 +-
 ...-configure-extra-fields-in-instore-cart.md |  4 +-
 ...ago-transparente-in-the-payments-module.md |  6 +--
 ...e-and-maximum-quantity-of-items-per-sku.md |  4 +-
 .../pt/how-to-configure-payment-conditions.md | 10 ++---
 ...to-configure-rating-and-review-controls.md |  4 +-
 docs/tutorials/pt/how-to-configure-taxhub.md  |  2 +-
 .../pt/how-to-configure-the-favicon.md        |  4 +-
 ...figure-the-fingerprint-device-for-stelo.md |  8 ++--
 ...ow-to-configure-xml-for-google-shopping.md |  2 +-
 ...ng-feed-and-the-google-product-taxonomy.md |  6 +--
 ...pment-environment-with-a-mobile-version.md |  2 +-
 ...ow-to-create-a-financial-access-profile.md |  4 +-
 .../pt/how-to-create-a-page-template.md       |  2 +-
 docs/tutorials/pt/how-to-create-a-product.md  | 18 ++++----
 ...eate-a-promotion-with-limitation-of-use.md |  2 +-
 .../pt/how-to-create-a-store-name.md          |  2 +-
 ...how-to-create-a-subscription-attachment.md |  4 +-
 .../pt/how-to-create-conditional-prices.md    |  2 +-
 ...ipt-customization-file-for-vtex-instore.md | 10 ++---
 ...-to-customize-a-page-using-placeholders.md | 14 +++---
 ...ize-the-checkout-ui-custom-in-the-admin.md |  8 ++--
 ...ow-to-define-the-url-for-a-product-page.md |  2 +-
 ...w-to-deprecate-and-undeprecate-your-app.md |  2 +-
 .../how-to-disable-a-transactional-email.md   |  2 +-
 .../pt/how-to-download-the-vtex-invoices.md   |  6 +--
 docs/tutorials/pt/how-to-find-an-sku-id.md    |  2 +-
 ...rls-that-are-inactive-or-contain-errors.md | 10 ++---
 .../pt/how-to-identify-a-page-template.md     |  6 +--
 ...ayout-errors-caused-by-javascript-files.md |  2 +-
 ...identify-promotions-applied-to-the-cart.md |  4 +-
 ...dentify-promotions-attributed-to-an-sku.md | 12 ++---
 ...ore-and-salesperson-in-an-instore-order.md | 12 ++---
 ...import-pickup-points-using-spreadsheets.md |  6 +--
 ...llection-of-products-in-the-shop-window.md | 18 ++++----
 ...de-a-registration-on-a-master-data-form.md |  4 +-
 ...ata-when-exporting-a-prices-spreadsheet.md |  4 +-
 ...he-vtex-tracking-app-on-your-vtex-admin.md |  2 +-
 ...ll-the-masterpass-in-the-vtex-app-store.md | 12 ++---
 .../tutorials/pt/how-to-install-the-taxhub.md |  2 +-
 .../pt/how-to-integrate-vtex-using-zapier.md  |  6 +--
 .../pt/how-to-integrate-with-dafiti.md        |  6 +--
 .../pt/how-to-manage-subscriptions.md         |  6 +--
 .../pt/how-to-manage-the-kit-stock.md         |  2 +-
 .../pt/how-to-manually-invoice-an-order.md    |  4 +-
 ...how-to-register-a-store-in-vtex-instore.md |  8 ++--
 ...how-to-request-receivables-anticipation.md |  2 +-
 .../pt/how-to-retrieve-the-access-password.md | 10 ++---
 .../how-to-see-orders-closed-with-benefits.md |  2 +-
 ...fine-a-default-sla-for-recurrent-orders.md |  4 +-
 .../pt/how-to-set-up-fingerprint-for-payu.md  | 22 +++++-----
 ...r-to-accept-payments-with-adyen-at-vtex.md |  4 +-
 ...t-up-the-device-fingerprint-for-braspag.md | 10 ++---
 ...set-up-the-indeva-scheduled-appointment.md | 10 ++---
 docs/tutorials/pt/how-to-set-up-the-zoom.md   |  6 +--
 docs/tutorials/pt/how-to-set-up-visa-debit.md |  6 +--
 .../pt/how-to-use-conditions-builder-app.md   |  6 +--
 .../pt/how-to-use-the-index-report.md         |  2 +-
 .../how-to-use-the-search-result-control.md   | 10 ++---
 .../pt/how-to-use-the-shareable-cart-app.md   | 12 ++---
 ...ow-to-use-the-unavailable-product-class.md |  2 +-
 .../pt/how-to-use-vtex-predictor-bot.md       |  8 ++--
 ...how-to-view-taxes-information-in-taxhub.md |  2 +-
 .../pt/how-to-view-the-orders-details.md      | 20 ++++-----
 ...how-to-view-transactions-on-pci-gateway.md |  2 +-
 ...ith-different-layouts-for-the-same-page.md |  2 +-
 docs/tutorials/pt/hubspot-suiteshare.md       |  4 +-
 .../pt/i-cant-import-the-price-table.md       |  2 +-
 .../pt/i-cant-receive-emails-from-vtex.md     |  2 +-
 ...-view-the-product-in-the-search-results.md |  6 +--
 .../pt/i-forgot-my-password-suiteshare.md     |  6 +--
 ...eting-utms-are-being-passed-to-checkout.md |  4 +-
 docs/tutorials/pt/image-compression.md        |  4 +-
 .../pt/importing-amazon-dba-orders.md         |  2 +-
 .../pt/importing-data-into-master-data.md     |  2 +-
 ...oving-the-performance-of-product-images.md |  2 +-
 ...roving-the-seo-of-product-listing-pages.md |  4 +-
 ...les-in-the-transactional-email-template.md |  4 +-
 docs/tutorials/pt/indexes-in-master-data.md   |  8 ++--
 docs/tutorials/pt/indexing-history-beta.md    | 16 +++----
 docs/tutorials/pt/indexing-history.md         | 16 +++----
 ...ll-visa-checkout-in-the-extension-store.md |  4 +-
 ...g-my-orders-through-the-extension-store.md |  6 +--
 ...stalling-the-widget-with-gtm-suiteshare.md | 20 ++++-----
 .../pt/integrating-with-farmacias-app.md      |  4 +-
 .../pt/integration-guide-for-erps-orders.md   |  8 ++--
 docs/tutorials/pt/integration-interfaces.md   |  2 +-
 .../pt/integration-with-google-tag-manager.md |  2 +-
 .../pt/integration-with-vtex-tracking.md      |  2 +-
 ...lligent-search-synonym-suggestions-beta.md |  4 +-
 docs/tutorials/pt/intelligent-synonyms.md     |  4 +-
 ...racting-with-masterdata-through-graphql.md | 10 ++---
 docs/tutorials/pt/interaction-details.md      | 12 ++---
 ...erpreting-the-data-of-the-oms-order-bar.md |  2 +-
 .../tutorials/pt/introduction-to-vtex-apis.md | 10 ++---
 docs/tutorials/pt/kit-registration.md         | 10 ++---
 .../lead-time-shipping-time-at-sku-level.md   |  4 +-
 ...-the-store-by-means-of-the-trade-policy.md |  2 +-
 ...ng-an-account-name-to-a-website-binding.md |  8 ++--
 ...g-urls-to-banners-using-the-site-editor.md |  4 +-
 docs/tutorials/pt/links-suiteshare.md         | 18 ++++----
 .../pt/list-the-account-workspaces.md         |  2 +-
 docs/tutorials/pt/lista-da-vez.md             |  8 ++--
 .../pt/listing-apps-installed-in-the-store.md |  2 +-
 docs/tutorials/pt/loading-dock.md             |  2 +-
 .../pt/locations-details-page-beta.md         | 10 ++---
 docs/tutorials/pt/log-in-to-the-account.md    |  2 +-
 .../logging-in-to-the-account-with-vtex-io.md |  2 +-
 ...ics-in-the-grocery-segment-supermarkets.md |  8 ++--
 .../tutorials/pt/logistics-module-overview.md | 12 ++---
 docs/tutorials/pt/magento-suiteshare.md       |  2 +-
 .../pt/making-a-master-data-field-editable.md |  2 +-
 .../pt/manage-the-sales-comissions-report.md  |  2 +-
 .../pt/managing-b2b-organizations.md          |  4 +-
 .../managing-credit-with-customer-credit.md   |  4 +-
 .../pt/managing-page-and-template-content.md  |  6 +--
 docs/tutorials/pt/managing-pages.md           |  4 +-
 docs/tutorials/pt/managing-placeholders.md    |  6 +--
 docs/tutorials/pt/managing-projects.md        |  6 +--
 .../pt/managing-redirects-per-binding.md      |  8 ++--
 .../pt/managing-shipping-policies.md          |  4 +-
 .../pt/managing-singleton-content-types.md    |  2 +-
 docs/tutorials/pt/managing-url-redirects.md   |  2 +-
 docs/tutorials/pt/managing-users.md           | 14 +++---
 ...-classes-and-methods-used-on-webservice.md |  2 +-
 .../pt/marketplace-invited-sellers.md         |  2 +-
 .../pt/marketplace-strategies-at-vtex.md      |  4 +-
 .../pt/marketplaces-and-integrations.md       |  2 +-
 docs/tutorials/pt/master-data-v2.md           |  4 +-
 docs/tutorials/pt/master-data.md              |  2 +-
 .../pt/match-offers-mercado-livre.md          | 18 ++++----
 docs/tutorials/pt/media-overview.md           |  4 +-
 docs/tutorials/pt/mercado-libre-promotions.md |  2 +-
 ...ercado-livre-automobilist-compatibility.md |  4 +-
 docs/tutorials/pt/mercado-livre-faq.md        |  8 ++--
 docs/tutorials/pt/merchandising-rules-list.md |  2 +-
 docs/tutorials/pt/meta-tags-suiteshare.md     | 10 ++---
 ...re-not-displayed-in-the-order-dashboard.md |  4 +-
 .../pt/migrating-ads-in-mercado-livre.md      |  2 +-
 ...ng-to-the-new-version-of-smart-checkout.md |  2 +-
 docs/tutorials/pt/moskit-suiteshare.md        | 12 ++---
 .../pt/multilevel-omnichannel-inventory.md    |  2 +-
 ...my-ad-is-not-displayed-on-mercado-livre.md |  4 +-
 .../pt/names-of-vtex-branches-worldwide.md    |  2 +-
 .../new-integration-with-erede-erederest.md   | 10 ++---
 docs/tutorials/pt/new-my-orders-area.md       | 14 +++---
 docs/tutorials/pt/new-route.md                |  2 +-
 docs/tutorials/pt/offer-details.md            | 12 ++---
 docs/tutorials/pt/offer-management.md         |  6 +--
 docs/tutorials/pt/offer-quality-filters.md    |  4 +-
 docs/tutorials/pt/offer-status.md             | 12 ++---
 ...-the-same-vtex-sellers-and-marketplaces.md |  2 +-
 docs/tutorials/pt/oms-page-structure.md       | 16 +++----
 docs/tutorials/pt/opening-hours-suiteshare.md | 10 ++---
 ...pening-tickets-to-vtex-support-finacial.md |  8 ++--
 .../pt/opening-tickets-to-vtex-support.md     |  2 +-
 .../tutorials/pt/operational-capacity-beta.md |  6 +--
 ...ization-of-shipping-options-at-checkout.md |  2 +-
 docs/tutorials/pt/order-flow-and-status.md    |  8 ++--
 ...name-of-a-customer-using-the-callcenter.md |  4 +-
 docs/tutorials/pt/order-to-delivery.md        | 20 ++++-----
 ...-window-display-and-on-the-product-page.md |  2 +-
 docs/tutorials/pt/orders-list.md              |  8 ++--
 docs/tutorials/pt/overview-pricing-module.md  |  8 ++--
 ...-program-intranet-and-vtex-store-manual.md | 20 ++++-----
 .../tutorials/pt/payment-provider-protocol.md | 14 +++---
 .../pt/payu-romania-refund-details.md         |  2 +-
 docs/tutorials/pt/pci-gateway-overview.md     |  2 +-
 .../pt/permissions-management-in-b2b-suite.md |  2 +-
 .../pt/physical-store-instore-beta.md         |  4 +-
 .../pickup-points-for-subscription-orders.md  |  2 +-
 docs/tutorials/pt/pickup-points.md            |  4 +-
 docs/tutorials/pt/pipedrive-suiteshare.md     | 16 +++----
 docs/tutorials/pt/piperun-suiteshare.md       | 30 ++++++-------
 docs/tutorials/pt/pix-faq.md                  |  4 +-
 .../pt/planner-calendar-page-beta.md          |  6 +--
 .../pt/planner-releases-page-beta.md          |  2 +-
 docs/tutorials/pt/price-divergence-rule.md    |  2 +-
 .../pt/price-divergence-rules-beta.md         | 10 ++---
 docs/tutorials/pt/price-waterfall.md          |  2 +-
 docs/tutorials/pt/pricing-rules-v2.md         | 10 ++---
 docs/tutorials/pt/product-list.md             |  2 +-
 docs/tutorials/pt/products-and-skus-beta.md   | 10 ++---
 docs/tutorials/pt/promotion-alerts-beta.md    |  2 +-
 docs/tutorials/pt/promotion-list-beta.md      |  6 +--
 docs/tutorials/pt/promotion-summary.md        |  6 +--
 docs/tutorials/pt/promotions-beta.md          |  8 ++--
 .../tutorials/pt/promotions-simulator-beta.md |  4 +-
 docs/tutorials/pt/promotions-simulator.md     |  4 +-
 .../protection-against-transaction-attacks.md | 12 ++---
 docs/tutorials/pt/qr-code-suiteshare.md       | 10 ++---
 docs/tutorials/pt/rdstation-crm-suiteshare.md | 10 ++---
 docs/tutorials/pt/rdstation-suiteshare.md     | 12 ++---
 docs/tutorials/pt/ready-to-dispatch.md        |  2 +-
 docs/tutorials/pt/received-skus-beta.md       | 18 ++++----
 docs/tutorials/pt/registered-ticket-flow.md   |  4 +-
 docs/tutorials/pt/registering-brands.md       |  2 +-
 .../pt/registering-gateway-affiliations.md    | 14 +++---
 docs/tutorials/pt/registering-sku-price.md    |  6 +--
 ...-with-nominal-discount-based-on-formula.md |  8 ++--
 .../pt/regular-promotion-with-reward-value.md | 12 ++---
 docs/tutorials/pt/regular-promotion.md        |  4 +-
 docs/tutorials/pt/releases-module-beta.md     |  4 +-
 .../pt/releasing-the-store-for-production.md  |  2 +-
 docs/tutorials/pt/relevance-rules.md          |  4 +-
 docs/tutorials/pt/remarketing.md              | 10 ++---
 ...request-headers-must-only-contain-ascii.md | 10 ++---
 docs/tutorials/pt/reports.md                  |  2 +-
 ...requering-authentication-on-store-pages.md |  6 +--
 .../pt/requesting-the-ssl-certificate.md      |  2 +-
 .../responsibilities-in-the-vtex-ecosystem.md |  4 +-
 .../pt/responsive-vs-mobile-version.md        |  4 +-
 ...ict-public-access-to-master-data-fields.md | 10 ++---
 docs/tutorials/pt/roles.md                    |  2 +-
 docs/tutorials/pt/rounding-rules.md           |  8 ++--
 docs/tutorials/pt/routing-monitoring.md       |  2 +-
 .../pt/sales-app-sales-performance.md         |  4 +-
 .../sales-associate-code-field-at-checkout.md |  4 +-
 .../pt/sales-associates-instore-beta.md       |  4 +-
 docs/tutorials/pt/sales-funnel-suiteshare.md  |  8 ++--
 docs/tutorials/pt/sales-performance.md        |  4 +-
 .../scheduling-features-for-special-events.md |  2 +-
 docs/tutorials/pt/scheduling-prices.md        |  4 +-
 docs/tutorials/pt/search-configuration.md     |  2 +-
 .../pt/search-control-fulltextsearchbox.md    |  8 ++--
 docs/tutorials/pt/search-navigator-control.md |  6 +--
 docs/tutorials/pt/search-parameters.md        | 12 ++---
 docs/tutorials/pt/searching-for-old-orders.md |  2 +-
 .../searching-for-transactions-on-payments.md |  4 +-
 docs/tutorials/pt/security-monitor.md         | 10 ++---
 ...ng-stock-for-orders-mercado-envios-full.md |  2 +-
 docs/tutorials/pt/seletivo.md                 | 14 +++---
 docs/tutorials/pt/seller-management.md        |  4 +-
 docs/tutorials/pt/seller-monitoring.md        |  2 +-
 .../pt/seller-portal-creating-a-promotion.md  | 12 ++---
 ...tal-getting-started-for-the-marketplace.md |  2 +-
 .../pt/seller-portal-product-details.md       |  2 +-
 docs/tutorials/pt/seller-portal-promotions.md |  4 +-
 .../pt/seller-portal-shared-products.md       |  4 +-
 ...nd-item-price-with-tax-shown-separately.md | 16 +++----
 ...es-and-bags-attributes-to-mercado-livre.md | 10 ++---
 .../pt/sending-products-to-the-marketplace.md |  4 +-
 .../pt/sending-sku-attributes-to-amazon.md    |  4 +-
 docs/tutorials/pt/sent-offers-beta.md         |  2 +-
 .../pt/sent-offers-buybox-opportunities.md    |  8 ++--
 docs/tutorials/pt/sequencial-suiteshare.md    |  8 ++--
 docs/tutorials/pt/services-import.md          |  2 +-
 docs/tutorials/pt/services-scheduling.md      |  4 +-
 ...r-authentication-for-recurring-payments.md |  2 +-
 .../pt/setting-up-a-personal-gift-message.md  |  4 +-
 ...ct-suggestions-accessories-and-generics.md |  2 +-
 .../pt/setting-up-abandoned-carts.md          |  8 ++--
 .../pt/setting-up-an-index-on-master-data.md  |  8 ++--
 ...app-linking-for-payments-app-in-instore.md |  2 +-
 docs/tutorials/pt/setting-up-b2b-on-vtex.md   | 10 ++---
 ...ing-up-cache-for-queries-to-master-data.md |  2 +-
 .../pt/setting-up-cybersource-gateway.md      |  4 +-
 ...ent-search-integration-with-the-catalog.md |  2 +-
 .../pt/setting-up-merchant-id-in-apple-pay.md | 40 ++++++++---------
 ...ng-up-payments-with-easypay-marketplace.md | 30 ++++++-------
 ...setting-up-payments-with-easypay-seller.md |  2 +-
 .../pt/setting-up-payments-with-easypay.md    | 20 ++++-----
 .../pt/setting-up-payments-with-itau-rede.md  | 12 ++---
 ...ng-up-personal-data-on-the-users-screen.md | 12 ++---
 ...ting-up-price-tables-for-specific-users.md |  6 +--
 docs/tutorials/pt/setting-up-shipment.md      |  2 +-
 .../pt/setting-up-sms-password-recovery.md    |  6 +--
 .../pt/setting-up-the-critical-stock-alert.md |  2 +-
 ...setting-up-the-css-for-the-product-zoom.md |  4 +-
 .../pt/setting-up-the-notify-me-option.md     |  2 +-
 .../pt/setting-up-the-price-range-filter.md   |  2 +-
 ...up-the-sales-funnel-on-google-analytics.md | 10 ++---
 .../setting-up-the-type-of-interest-rate.md   |  2 +-
 .../pt/setting-up-the-voucher-list.md         |  4 +-
 .../pt/setting-up-vtex-instore-logistics.md   |  2 +-
 ...-store-access-to-google-webmaster-tools.md |  8 ++--
 docs/tutorials/pt/sharpspring-suiteshare.md   | 14 +++---
 docs/tutorials/pt/shipping-options-beta.md    |  4 +-
 docs/tutorials/pt/shipping-policy.md          |  2 +-
 docs/tutorials/pt/shipping-rate-template.md   |  2 +-
 docs/tutorials/pt/shipping-rates.md           |  2 +-
 docs/tutorials/pt/shipping-strategy.md        |  2 +-
 docs/tutorials/pt/shopee-integration.md       |  2 +-
 docs/tutorials/pt/shopify-suiteshare.md       |  2 +-
 docs/tutorials/pt/site-editor-overview.md     |  2 +-
 docs/tutorials/pt/sku-bindings.md             |  2 +-
 ...martcheckout-v5-general-characteristics.md |  2 +-
 docs/tutorials/pt/special-conditions.md       | 10 ++---
 docs/tutorials/pt/split-payment.md            |  8 ++--
 docs/tutorials/pt/store-access-permission.md  |  2 +-
 docs/tutorials/pt/store-overview-beta.md      |  8 ++--
 docs/tutorials/pt/store-overview.md           | 18 ++++----
 ...ough-google-search-console-data-markers.md | 10 ++---
 docs/tutorials/pt/styles-overview.md          |  2 +-
 docs/tutorials/pt/subscription-plans.md       |  2 +-
 docs/tutorials/pt/synonym-list.md             |  2 +-
 docs/tutorials/pt/telesales-toolbar.md        |  2 +-
 docs/tutorials/pt/teste.md                    |  2 +-
 .../pt/testing-webservice-using-soapui.md     |  4 +-
 docs/tutorials/pt/total-shipping-cost.md      |  2 +-
 .../pt/transaction-flow-in-payments.md        |  2 +-
 ...actional-emails-for-subscription-orders.md |  2 +-
 docs/tutorials/pt/transactions-events.md      | 14 +++---
 .../pt/transferring-store-ownership.md        |  4 +-
 ...eshooting-errors-in-subscription-orders.md |  6 +--
 docs/tutorials/pt/understand-your-balance.md  |  2 +-
 docs/tutorials/pt/understanding-b2b-orders.md |  2 +-
 .../pt/understanding-how-indexation-works.md  |  4 +-
 .../pt/understanding-how-the-cache-works.md   |  8 ++--
 ...standing-storebuilder-and-stylesbuilder.md | 18 ++++----
 ...erstanding-the-additional-shipping-cost.md |  6 +--
 .../understanding-the-cubic-weight-factor.md  |  4 +-
 .../pt/understanding-the-message-center.md    |  6 +--
 .../pt/understanding-the-price-change-rule.md |  2 +-
 .../pt/understanding-the-security-report.md   |  2 +-
 ...e-suspicious-purchase-notice-on-vtex-do.md |  2 +-
 .../pt/understanding-the-task-list-vtex-do.md | 16 +++----
 docs/tutorials/pt/understanding-the-topbar.md |  8 ++--
 .../understanding-the-updating-of-the-xml.md  |  2 +-
 ...nderstanding-vtexs-email-capture-system.md |  2 +-
 .../untitled-entry-2017-07-10-at-10-14-00.md  |  2 +-
 .../untitled-entry-2017-07-19-at-06-54-03.md  |  2 +-
 .../untitled-entry-2017-09-12-at-06-50-03.md  |  6 +--
 .../updating-quantity-of-skus-in-inventory.md |  2 +-
 ...ting-the-quantity-of-items-in-inventory.md |  2 +-
 docs/tutorials/pt/uploading-a-product-xml.md  |  2 +-
 docs/tutorials/pt/url-mapping-301-redirect.md |  2 +-
 .../using-orders-managment-filters-in-api.md  | 10 ++---
 .../pt/using-recaptcha-at-checkout.md         |  6 +--
 ...-track-browsing-sessions-in-vtex-stores.md |  2 +-
 .../using-the-homepage-of-the-admin-panel.md  |  4 +-
 docs/tutorials/pt/using-tools-html.md         |  4 +-
 ...a-layout-before-moving-it-to-production.md |  4 +-
 docs/tutorials/pt/view-reindex-log.md         |  2 +-
 .../visao-geral-configuracoes-de-usuario.md   |  2 +-
 .../visao-geral-da-estrutura-do-catalogo.md   |  2 +-
 docs/tutorials/pt/vtex-ad-network-beta.md     |  2 +-
 docs/tutorials/pt/vtex-admin-start-here.md    | 10 ++---
 docs/tutorials/pt/vtex-admin-start-here1.md   | 10 ++---
 docs/tutorials/pt/vtex-agreement.md           |  2 +-
 ...vtex-dashboard-guide-for-black-week-faq.md | 38 ++++++++--------
 docs/tutorials/pt/vtex-do-interface.md        |  4 +-
 docs/tutorials/pt/vtex-insurance.md           | 12 ++---
 ...gent-search-multilanguage-settings-beta.md |  8 ++--
 docs/tutorials/pt/vtex-invoice-notifier.md    | 12 ++---
 .../pt/vtex-pick-and-pack-insights.md         | 10 ++---
 .../tutorials/pt/vtex-pick-and-pack-mobile.md | 26 +++++------
 .../tutorials/pt/vtex-pick-and-pack-orders.md |  6 +--
 .../pt/vtex-pick-and-pack-settings.md         | 20 ++++-----
 .../pt/vtex-pick-and-pack-worksheets.md       |  8 ++--
 ...ex-shipping-network-correios-activation.md | 12 ++---
 .../pt/vtex-shipping-network-dashboard.md     |  2 +-
 docs/tutorials/pt/vtex-status-page.md         | 22 +++++-----
 docs/tutorials/pt/vtex-suiteshare.md          | 12 ++---
 docs/tutorials/pt/vtex-tracking-agencies.md   |  4 +-
 docs/tutorials/pt/warehouse.md                |  2 +-
 .../pt/web-application-firewall-waf.md        |  2 +-
 docs/tutorials/pt/web-page-performance.md     |  4 +-
 docs/tutorials/pt/welcome-message-control.md  |  2 +-
 ...urce-and-orders-with-fulfillment-source.md |  2 +-
 docs/tutorials/pt/what-are-shelves.md         |  2 +-
 docs/tutorials/pt/what-are-templates.md       |  2 +-
 ...tivate-a-gift-multiplier-on-a-promotion.md |  2 +-
 ...r-as-revenue-in-the-billing-calculation.md |  2 +-
 .../pt/what-is-a-franchise-account.md         |  4 +-
 docs/tutorials/pt/what-is-binding.md          |  2 +-
 docs/tutorials/pt/what-is-cms-layout.md       |  2 +-
 ...ce-between-inventory-and-warehouse-dock.md |  2 +-
 ...s-the-purpose-of-the-customized-control.md |  2 +-
 ...hat-to-do-when-a-customer-opens-dispute.md |  2 +-
 ...-when-my-report-does-not-reach-my-inbox.md |  2 +-
 ...app-ai-campaigns-management-and-details.md |  2 +-
 ...re-do-i-see-clients-that-use-recurrence.md |  2 +-
 ...where-do-i-see-the-payment-capture-date.md |  2 +-
 .../pt/white-label-sellers-selection.md       | 10 ++---
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  2 +-
 docs/tutorials/pt/widget.md                   | 18 ++++----
 docs/tutorials/pt/wix-suiteshare.md           |  6 +--
 docs/tutorials/pt/wordpress-suiteshare.md     |  6 +--
 .../pt/wow-to-integrate-with-multiplus.md     |  4 +-
 docs/tutorials/pt/zapier-suiteshare.md        | 14 +++---
 2761 files changed, 6965 insertions(+), 6965 deletions(-)

diff --git a/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md b/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md
index 8d5f2fe1e..becbe6b0b 100644
--- a/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md
+++ b/docs/announcements/en/access-googles-pagespeed-insights-in-your-vtex-admin.md
@@ -21,7 +21,7 @@ This is why we created the new [Web Page Performance](https://help.vtex.com/en/v
 
 PageSpeed Insights and Lighthouse are tools developed by Google to report on the user experience of a page on both mobile and desktop devices, providing suggestions on how that page may be improved. They use [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals) as metrics to assess online user experience. 
 
-![Web page performance Dash EN](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
+![Web page performance Dash EN](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/admin-disponivel-em-japones.md b/docs/announcements/en/admin-disponivel-em-japones.md
index cff46147d..58d1ad916 100644
--- a/docs/announcements/en/admin-disponivel-em-japones.md
+++ b/docs/announcements/en/admin-disponivel-em-japones.md
@@ -26,4 +26,4 @@ The Admin’s translation into Japanese was driven by the [opening of our new of
 
 ## What do you need to do
 To view the Admin in Japanese, select JP in the language dropdown menu in the upper right corner of the screen. 
-![Select JP](//images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/962f59494964fb2dddfb42f557949e28/japones.png)
+![Select JP](https://images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/962f59494964fb2dddfb42f557949e28/japones.png)
diff --git a/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
index 9cbaf3a0e..e148719d3 100644
--- a/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -29,7 +29,7 @@ Now, users will only see the sidebar menu items they are allowed to access, acco
 
 The image below illustrates how the sidebar might change as a result of these housekeeping procedures to improve your store's security and user experience.
 
-![EN Sidebar permissions announcement screenshot](//images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/8ffedd77b8566929fd3c39b73cad6590/EN_Sidebar_permissions_announcement_screenshot.png)
+![EN Sidebar permissions announcement screenshot](https://images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/8ffedd77b8566929fd3c39b73cad6590/EN_Sidebar_permissions_announcement_screenshot.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md
index 37f4903d3..f6710a36c 100644
--- a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md
+++ b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization-teste.md
@@ -21,7 +21,7 @@ For example, restaurants that accept online orders usually allow customers to ch
 
 To simplify this feature, we developed the Assembly Options app, which provides an interface for configuring and managing custom options. The app is only available for stores using [VTEX IO](https://vtex.com/us-en/store-framework/).
 
-![assembly-options-app-en](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
+![assembly-options-app-en](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md
index 12184a066..57ff44efe 100644
--- a/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md
+++ b/docs/announcements/en/assembly-options-new-app-to-simplify-product-customization.md
@@ -21,7 +21,7 @@ For example, restaurants that accept online orders usually allow customers to ch
 
 To simplify this feature, we developed the Assembly Options app, which provides an interface for configuring and managing custom options. The app is only available for stores using [VTEX IO](https://vtex.com/us-en/store-framework/).
 
-![assembly-options-app-en](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
+![assembly-options-app-en](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 545b1fec5..3c39e4e17 100644
--- a/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -25,7 +25,7 @@ In addition, **VTEX Pick and Pack** [collects data and analytics](https://help.v
 * [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): Control of last-mile delivery.
 * **Mobile Applications:** Applications for pickers and couriers.
 
-![pick_pack_gif_EN](//images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/a6b1137ac375e1a046cc2a76a56e3958/pick_pack_gif_EN.gif)
+![pick_pack_gif_EN](https://images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/a6b1137ac375e1a046cc2a76a56e3958/pick_pack_gif_EN.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md b/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md
index 923a5d91d..63245e49b 100644
--- a/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md
+++ b/docs/announcements/en/campaign-promotions-new-option-when-configuring-target-audience.md
@@ -23,7 +23,7 @@ We have improved the campaign audience settings so that you can add up target au
 
 In the VTEX Admin, **Products > Promotions and Taxes > Campaign Audience > New Campaign Audience**, in the settings related to the **Target Audience**, we added the "and" option, where there was previously only the "or" option. This means that now you can apply a criteria adding logic ("and") besides the pre-existent alternative logic ("or"). Please see the image below:
 
-![publico-alvo-e-ou-en](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
+![publico-alvo-e-ou-en](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
 
 Using the new option, you can create campaign promotions flexibly combining different criteria.
 
diff --git a/docs/announcements/en/catalogs-new-visual-and-navigation.md b/docs/announcements/en/catalogs-new-visual-and-navigation.md
index a2684f479..93f0b443f 100644
--- a/docs/announcements/en/catalogs-new-visual-and-navigation.md
+++ b/docs/announcements/en/catalogs-new-visual-and-navigation.md
@@ -23,16 +23,16 @@ The main difference to the old version is on how you navigate through it. We've
 ## What has changed
 
 Most items of the old Catalog can now be found on the _Catalog_ option, on the sidebar's _PRODUCTS_ section.
-![EN-Catálogo1](//images.ctfassets.net/alneenqid6w5/6PWNLidc6AYwsIw4W8GcEQ/e5fb1c8e3aaf79fa05d895a920dd78c7/EN-Cat__logo1.png)
+![EN-Catálogo1](https://images.ctfassets.net/alneenqid6w5/6PWNLidc6AYwsIw4W8GcEQ/e5fb1c8e3aaf79fa05d895a920dd78c7/EN-Cat__logo1.png)
 
 
 The _Gift card_ subitem (formerly known as _Vouchers_ and previously located under the _Campaign Control_ tab) is now one of the _Payments_ drop-down options, on the sidebar's _TRANSACTIONS_ section. 
-![EN-Catálogo2](//images.ctfassets.net/alneenqid6w5/mYzfITNdIWSQ00qaewAsQ/0a9fd430c40271c4f4d6ed9574bf13fd/EN-Cat__logo2.png)
+![EN-Catálogo2](https://images.ctfassets.net/alneenqid6w5/mYzfITNdIWSQ00qaewAsQ/0a9fd430c40271c4f4d6ed9574bf13fd/EN-Cat__logo2.png)
 
 
 The _Settings_ item (formerly a tab of its own) is now one of the _CMS_ drop-down options, on the sidebar's _STORE SETUP_ section. 
-![EN-Catálogo3](//images.ctfassets.net/alneenqid6w5/5mVP1uxDzi2e28ym2o0IEO/3c72b956fb706517dacd2bc3d473550f/EN-Cat__logo3.png)
+![EN-Catálogo3](https://images.ctfassets.net/alneenqid6w5/5mVP1uxDzi2e28ym2o0IEO/3c72b956fb706517dacd2bc3d473550f/EN-Cat__logo3.png)
 
 
 The former _Marketplace_ tab continues independent (even the name remains the same), with a section of its own on the sidebar.
-![EN-Catálogo4](//images.ctfassets.net/alneenqid6w5/2BjYZAd5PKACmiiOum64O4/a9379e8f4bb1cb762b744db5a2cae42a/EN-Cat__logo4.png)
+![EN-Catálogo4](https://images.ctfassets.net/alneenqid6w5/2BjYZAd5PKACmiiOum64O4/a9379e8f4bb1cb762b744db5a2cae42a/EN-Cat__logo4.png)
diff --git a/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md b/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
index 995df8e74..85a42b068 100644
--- a/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
+++ b/docs/announcements/en/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
@@ -27,7 +27,7 @@ Rest assured, we made no mistake. After careful consideration, our team decided
 
 But that's not all. We also completely revamped the process to change the Sponsor user for an account, transforming it into an invitation-based transfer flow that is fully auditable. 
 
-![Sponsor management gif](//images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/93870cb4eae7fd2591b388279faa2db9/Announcement_EN.gif)
+![Sponsor management gif](https://images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/93870cb4eae7fd2591b388279faa2db9/Announcement_EN.gif)
 
 Check out [Transferring store ownership](https://help.vtex.com/en/tutorial/transferring-store-ownership) for more details on this new process.
 
diff --git a/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
index 5ff9b8954..c5edb4390 100644
--- a/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
@@ -45,7 +45,7 @@ To check if the anti-fraud solutions configured in your store allow changing the
 2. In the **Payments** module, click on **Settings > Gateway affiliations**. 
 3. After selecting the desired anti-fraud solution, check if the **Cardholder document field** option is available on the configuration screen.
 
-![cardholder document field](//images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/350f0aaab8c88555c89a9ca3f2304f6c/cardholder_document_field.png)
+![cardholder document field](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/350f0aaab8c88555c89a9ca3f2304f6c/cardholder_document_field.png)
 
 <div class = "alert alert-warning">
   If the <b>Cardholder document field</b> option is not available on the configuration screen of your anti-fraud solution provider, the <b>Cardholder document</b> field will still be displayed at Checkout in your store, and the customer will be required to fill it out.
diff --git a/docs/announcements/en/coupon-experience-improvements.md b/docs/announcements/en/coupon-experience-improvements.md
index 91f36f140..1d736b70b 100644
--- a/docs/announcements/en/coupon-experience-improvements.md
+++ b/docs/announcements/en/coupon-experience-improvements.md
@@ -27,7 +27,7 @@ The new [Coupons](https://help.vtex.com/en/tutorial/cupons-beta--1aAEN3ADpz19ss5
 
 The new [coupon list](https://help.vtex.com/en/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ) shows all the existing coupons in your store. This allows you to manage coupon data and analyze in which orders they were used.
 
-![listacupons en](//images.ctfassets.net/alneenqid6w5/3EL3TmEa9iBuABSPWAkT0B/1cfe126f85df72b7c9e30f8e4cb85606/listacupons_en.gif)
+![listacupons en](https://images.ctfassets.net/alneenqid6w5/3EL3TmEa9iBuABSPWAkT0B/1cfe126f85df72b7c9e30f8e4cb85606/listacupons_en.gif)
 
 ### Easier access to coupon codes
 
@@ -44,7 +44,7 @@ The new filters allow you to view coupons that meet specific criteria. The avail
 - Last modified
 - Coupon type
 
-![filtroscupons en](//images.ctfassets.net/alneenqid6w5/5ImK8Og5MsOnruVxkwblJ6/b2abce2b73d9facd5edcf6f589dad039/filtroscupons_en.gif)
+![filtroscupons en](https://images.ctfassets.net/alneenqid6w5/5ImK8Og5MsOnruVxkwblJ6/b2abce2b73d9facd5edcf6f589dad039/filtroscupons_en.gif)
 
 ### Coupon groups for agile management
 
diff --git a/docs/announcements/en/displaying-pickup-points-on-google-maps.md b/docs/announcements/en/displaying-pickup-points-on-google-maps.md
index 5962c0512..2c7dad755 100644
--- a/docs/announcements/en/displaying-pickup-points-on-google-maps.md
+++ b/docs/announcements/en/displaying-pickup-points-on-google-maps.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'An application that lists pickup locations and displays
 
 One of the most common features of websites and online stores is a map showing the location of physical stores. The new[ Store Locator](https://apps.vtex.com/vtex-store-locator/p#overview) app allows stores developed with VTEX IO to list their pickup points on Google Maps and show them as markers on a map.
 
-![Maps](//images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
+![Maps](https://images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
 
 ## What changed?
 
diff --git a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md
index 3985e2bfc..bed3eb7ce 100644
--- a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md
+++ b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Promotion summary allows you to review information abou
 
 Mistakes can happen when configuring a new promotion and filling in information. To avoid activating promotions with incorrect information, we created the promotion summary. The new feature allows you to confirm the promotion settings before activating it.
 
-![resumo-promo-EN](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
+![resumo-promo-EN](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
 
 ## What has changed?
 Previously, a promotion was automatically activated when saved with **Active** status. With the new feature, you can view a summary of the settings configured before activating a new promotion. This allows you to make sure that all data in the promotion is correct, avoiding implementation errors.
diff --git a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
index 297af14e5..f1f18d0af 100644
--- a/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
+++ b/docs/announcements/en/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Promotion summary allows you to review information abou
 
 Mistakes can happen when configuring a new promotion and filling in information. To avoid activating promotions with incorrect information, we created the promotion summary. The new feature allows you to confirm the promotion settings before activating it.
 
-![resumo-promo-EN](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
+![resumo-promo-EN](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/b9caef1451ab9b973ec678b858945652/image.png)
 
 ## What has changed?
 Previously, a promotion was automatically activated when saved with **Active** status. With the new feature, you can view a summary of the settings configured before activating a new promotion. This allows you to make sure that all data in the promotion is correct, avoiding implementation errors.
diff --git a/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 3683313d2..9689ce484 100644
--- a/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -25,7 +25,7 @@ The application is available in the [VTEX App Store](https://apps.vtex.com "VTEX
 - Allows you to moderate reviews: approve product reviews before they are published on the product page;
 - Allows you to configure your store to enable anonymous reviews.
 
-![Reviews and Ratings - Printscreen](//images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
+![Reviews and Ratings - Printscreen](https://images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
 
 ## What are the advantages?
 - Allows your customer to be more confident and assertive when shopping, based on ratings from other users;
diff --git a/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index ce9c241f8..3ced52386 100644
--- a/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -38,6 +38,6 @@ In order to do this, you need to add a product called `Order Authorization` to t
 6. Choose the type of permission you wish to grant: either `Save Configuration` if you want to allow the user to edit and save changes, or `View Configuration` if you want the user to only view the Order Authorization page.
 7. Finally, click on **Save**.
 
-![GIT-OrderAutho.en](//images.ctfassets.net/alneenqid6w5/1K34RexhGDYnU2ogYWsH6L/5214f0861ae9a92073005c074ab5c128/GIT-OrderAutho.en.gif)
+![GIT-OrderAutho.en](https://images.ctfassets.net/alneenqid6w5/1K34RexhGDYnU2ogYWsH6L/5214f0861ae9a92073005c074ab5c128/GIT-OrderAutho.en.gif)
 
 Upon adding this new product to a profile, ensure that the desired users are in fact linked to this profile.
diff --git a/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
index 8fd6229b8..8b5e4b965 100644
--- a/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'The new VTEX Admin section to find partners, add featur
 
 Extensions Hub is a new section of VTEX Admin that gathers partner developers and merchants who want to expand their operation capabilities. Through Extensions Hub, partners can publish extensions, and merchants can view, purchase, install, and manage them. Extensions Hub will be available globally in all VTEX stores during the third quarter (Q3) of 2023. If you want to enable Extensions Hub in your store immediately, you can request it by [opening a ticket to our support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM).
 
-![Extensions Hub GIF](//images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e48b0ef19071288b6ed0cf7f6880dc16/Extensions_Hub.gif)
+![Extensions Hub GIF](https://images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e48b0ef19071288b6ed0cf7f6880dc16/Extensions_Hub.gif)
 
 ## What has changed?
 
@@ -49,7 +49,7 @@ The [Partner Portal website](https://partnerportal.vtex.com/) will remain unchan
 
 Extensions Hub will be available for all stores in the third quarter (Q3) of 2023. If you want to enable Extensions Hub in your store immediately, you can request it by [opening a ticket to our support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM). Then, to start using the Extensions Hub, access it in your Admin. On the VTEX Admin left side menu, click the **Extensions** icon, and the Extensions Hub will be visible at the top of the menu.
 
-![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
+![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/facebook-and-google-login-settings-have-changed.md b/docs/announcements/en/facebook-and-google-login-settings-have-changed.md
index 0e99a6713..1d898658c 100644
--- a/docs/announcements/en/facebook-and-google-login-settings-have-changed.md
+++ b/docs/announcements/en/facebook-and-google-login-settings-have-changed.md
@@ -21,6 +21,6 @@ The flag __Use VTEX keys__, which previously activated the use of data provided
 
 This means that the stream has been fixed and it is no longer possible to use VTEX keys to login with Facebook and Google. Now retailers need to set up their own keys.
 
-![login2](//images.contentful.com/alneenqid6w5/8ctzWCGmeAuay68eyk888/630cfc3d79ef248f06ca47575556738c/login2.png)
+![login2](https://images.contentful.com/alneenqid6w5/8ctzWCGmeAuay68eyk888/630cfc3d79ef248f06ca47575556738c/login2.png)
 
 This change does not have any negative impact on your store. However, if some customization was done wrongly on your login screen, crashes may occur. So check out your login screen to make sure everything goes like it used to.
diff --git a/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
index 5ca356c1b..4cbb62525 100644
--- a/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
+++ b/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Introducing FastCheckout: Checkout innovation for custo
 
 Committed to continuously innovating and delivering excellence to our clients, VTEX introduces **FastCheckout**, the latest evolution of our checkout. This new solution allows us to create custom checkout experiences with high conversion rates and is constantly updated with new features.
 
-![fastcheckout](//images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/15f7c568ca3e481a52d3c93ecc9865bf/image.png)
+![fastcheckout](https://images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/15f7c568ca3e481a52d3c93ecc9865bf/image.png)
 
 ## What has changed?
 
@@ -56,7 +56,7 @@ We allow you to add fully custom elements, without having to be familiar with Ja
 
 The new purchase flow in FastCheckout is designed to be dynamic and intuitive, providing your customers with a more fluid and streamlined buying experience. We've made the checkout process more efficient with clear steps and intuitive navigation.
 
-![GIFCheckout](//images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/0f6cf76a12a01a77905195ba835d5028/GIFCheckout.gif)
+![GIFCheckout](https://images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/0f6cf76a12a01a77905195ba835d5028/GIFCheckout.gif)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md b/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md
index 0c41c9558..bd11a29f0 100644
--- a/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md
+++ b/docs/announcements/en/gain-speed-and-practicality-with-the-updated-price-table-feature.md
@@ -20,7 +20,7 @@ It is now possible to create Price Tables in a more intuitive, practical and fas
 ## What changes
 Before, to create a Price Table, it was necessary to acess the Prices module filter and enter the name of the table to be created. Now, we've added a new __Price Table__ button that allows you to create and select the price table you want to view.
 
-![Annoucement Price Table EN](//images.ctfassets.net/alneenqid6w5/2TtSjOmyXMNNA523PqsQxB/3d2711e543c6bef5aa0c5cadf231d0a7/Annoucement_Price_Table_EN.png)
+![Annoucement Price Table EN](https://images.ctfassets.net/alneenqid6w5/2TtSjOmyXMNNA523PqsQxB/3d2711e543c6bef5aa0c5cadf231d0a7/Annoucement_Price_Table_EN.png)
 
 ## Advantages
 
diff --git a/docs/announcements/en/get-to-know-the-new-vtex-status-page.md b/docs/announcements/en/get-to-know-the-new-vtex-status-page.md
index 2a54d89b7..2932bd93e 100644
--- a/docs/announcements/en/get-to-know-the-new-vtex-status-page.md
+++ b/docs/announcements/en/get-to-know-the-new-vtex-status-page.md
@@ -23,7 +23,7 @@ Previously, we faced challenges by categorizing incidents into four components:
 
 Now, we have introduced 18 more specific components, grouped into four categories: Storefront, Checkout, Admin, and Developer Tools. This approach focuses not only on our internal architecture but mainly on where merchants can see the symptoms. The following image shows all the components displayed on the new page:
 
-![status-page-vtex](//images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/c79f37753e6a20025ad5b529a7c43e99/status-page-vtex.png)
+![status-page-vtex](https://images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/c79f37753e6a20025ad5b529a7c43e99/status-page-vtex.png)
 
 Check out the [VTEX Status page](https://help.vtex.com/en/tutorial/vtex-status-page--gPhqDn9IQ3c67wbJEX3JJ) article for more information on each component.
 
diff --git a/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md b/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
index 20ba839f1..7c3522bd4 100644
--- a/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
+++ b/docs/announcements/en/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
@@ -21,4 +21,4 @@ As in previous years, we came up with a guide with recommendations and exclusive
 
 The guide is available to all our clients and partners and may be accessed through the homepage of your Admin or directly through the URL `https://{AccountName}.myvtex.com/admin/blackfriday`. Just replace `{AccountName}` with your store's Account Name.
 
-![Announcement Cartilha BF - EN](//images.ctfassets.net/alneenqid6w5/1qu1Wg1MFyc0aCCeA6AimE/7f7644728fe95b415ea45bf1203a17f3/Announcement_Cartilha_BF_-_EN.png)
+![Announcement Cartilha BF - EN](https://images.ctfassets.net/alneenqid6w5/1qu1Wg1MFyc0aCCeA6AimE/7f7644728fe95b415ea45bf1203a17f3/Announcement_Cartilha_BF_-_EN.png)
diff --git a/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md b/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
index e4260f363..f0e731833 100644
--- a/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
+++ b/docs/announcements/en/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
@@ -27,4 +27,4 @@ https://{AccountName}.myvtex.com/admin/shopping-season
 
 Simply replace `{AccountName}` with your store's Account Name, as in the image below.
 
-![Shopping Season Guidelines - 2022 - EN](//images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/4e64d85173498b710da6706438fb100a/Screen_Shot_2022-10-19_at_18.14.44.png)
+![Shopping Season Guidelines - 2022 - EN](https://images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/4e64d85173498b710da6706438fb100a/Screen_Shot_2022-10-19_at_18.14.44.png)
diff --git a/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md b/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md
index 95ed6673c..ffc43a9a3 100644
--- a/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md
+++ b/docs/announcements/en/google-pay-new-payment-method-available-on-vtex.md
@@ -27,7 +27,7 @@ Google Pay is a digital wallet platform and online payment system developed by G
 
 Now, you can add Google Pay as a payment method to your store, giving customers a faster and more convenient checkout process.
 
-![google-pay-checkout-en](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b0a0e3b391668b1fcf2df8d3dc33a3f7/image.png)
+![google-pay-checkout-en](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b0a0e3b391668b1fcf2df8d3dc33a3f7/image.png)
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/google-shopping-new-option-to-submit-prices.md b/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
index b1ccfd02f..e88241e05 100644
--- a/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
+++ b/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
@@ -27,14 +27,14 @@ Previously, merchants could see the **Consider discount for boleto payment in th
   The <b>Apply discount to submitted price</b> setting is only available for VTEX stores in Brazil.
 </div>
 
-![envio-de-precos-google-en](//images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/419f9830910ef18e14deec1eef56f5aa/envio-de-precos-google-en.png)  
+![envio-de-precos-google-en](https://images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/419f9830910ef18e14deec1eef56f5aa/envio-de-precos-google-en.png)  
 
 ## What needs to be done?
 
 As of December 14, 2023, the update will be available to all [VTEX accounts acting as sellers](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-seller).
 Accounts not using the Google Shopping integration but wanting to activate the __Submit base price (for discount prices)__ and __Apply discount to submitted price__ settings should follow [this article track](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4z) to start using the new settings. Accounts that are integrated with Google Shopping and have the __Consider discount for boleto payment in the submitted price__ setting active will automatically have the __Apply discount to submitted price__ option active after the update, as shown in the image below:
 
-![fluxo-update-news-google-en](//images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/8feca453a73f6c2a09f311f9b482d8da/fluxo-update-news-google-en.png)
+![fluxo-update-news-google-en](https://images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/8feca453a73f6c2a09f311f9b482d8da/fluxo-update-news-google-en.png)
 
 Check out the documentation and learn how to [configure a discount linked to a payment method](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/3AqbcsWrge8zLt0BC5CtGd#desconto-vinculado-ao-metodo-de-pagamento) and [how to configure a discount in the connector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
 
diff --git a/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md b/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md
index ac953448e..c8fe439c0 100644
--- a/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md
+++ b/docs/announcements/en/headless-cms-create-non-duplicatable-pages.md
@@ -16,7 +16,7 @@ announcementSynopsisEN: 'Introducing the Singleton: a Headless CMS content type
 ---
 
 The Singleton is a new type of content type that allows merchants to create and manage a single page of a content type in the Headless CMS. Unlike other content types, the Singleton cannot be duplicated, ensuring that only one page exists and the content is consistent across the store's pages.
-![singleton-en](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
+![singleton-en](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 The Singleton content type is only available for stores using the <a href="https://help.vtex.com/en/tutorial/managing-pages-beta--3DO6rBhZ1p3zndnFu5BgRt">VTEX Headless CMS</a> (Currently in Beta phase).
diff --git a/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md b/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md
index 2802d51b5..be8913e9a 100644
--- a/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md
+++ b/docs/announcements/en/headless-cms-deeper-insights-into-page-publication-status.md
@@ -19,7 +19,7 @@ Starting November 1st, 2023, the **Publishing** status on Pages in the Headless
 
 When a new page is created, it is initially set to **Draft**, indicating that the page has not yet been deployed. Once the page is successfully deployed, its status is updated to **Published**, meaning that the build process is ready to commence. Upon completion of the build, the page becomes accessible to end users.
 
-![Build Status - EN](//images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/81374cc9a9e94e04975cca5946de4ece/publishing-status-en.gif)
+![Build Status - EN](https://images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/81374cc9a9e94e04975cca5946de4ece/publishing-status-en.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md b/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md
index 2ccb7de54..363e8fea3 100644
--- a/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md
+++ b/docs/announcements/en/headless-cms-simplify-content-creation-and-management-with-projects.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Headless CMS - Centralize and customize your projects i
 
 **Projects** is the new feature in the Headless CMS that streamlines the management of multiple digital experiences, such as mobile apps, websites, and email marketing, from one control panel. 
 
-![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c7ccee21dc6cae85a41886c49d9a3d8f/projects-two-en.png)
+![Projects overview](https://images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c7ccee21dc6cae85a41886c49d9a3d8f/projects-two-en.png)
 
 With Projects, you can customize each project's settings, content, and branding to specific audiences or purposes.
 
@@ -26,7 +26,7 @@ Before, to handle different projects with distinct target audiences or solutions
 
 Now, the **Projects** interface allows you to manage all your projects from a single dashboard, providing a centralized control panel where you can manage all projects. You can now easily switch between projects, adjusting settings, content, and identity in one place. This improvement makes you more adaptable, catering to different audiences and objectives.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
 
 ## Why are we making this change?
 The **Projects** interface brings the following improvements:
diff --git a/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md b/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md
index 81890d313..ac211b130 100644
--- a/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md
+++ b/docs/announcements/en/headless-cms-stay-informed-on-your-publication-progress.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Stay informed about Headless CMS publication stages and
 
 The Headless CMS now offers a notification feature that keeps you informed throughout each stage of the publication process. The new notification cards provide updates on each stage of a publication in the VTEX Headless CMS, keeping users informed about the publication on Releases, VTEX Headless CMS, and FastStore build stages. 
 
-![Headless CMS - Notification](//images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/7ab62cbd7fbb27b46894c0f366e7d25c/headless-cms-publish-en.gif)
+![Headless CMS - Notification](https://images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/7ab62cbd7fbb27b46894c0f366e7d25c/headless-cms-publish-en.gif)
 
 This feature also helps you identify and report errors during deployment by indicating the exact error stage. It also provides the option to retry deployments if needed.
 
@@ -35,7 +35,7 @@ With the notification feature, you can now stay informed about the status of eac
 
 If an error occurs during deployment, the notification card will indicate the stage at which the error occurred. You can click `Try again` to redeploy.
 
-![Headless CMS - Redeploy](//images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/2e950f93b204d1ce40d67b0f8516b327/headless-cms-redeploy-en.gif)
+![Headless CMS - Redeploy](https://images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/2e950f93b204d1ce40d67b0f8516b327/headless-cms-redeploy-en.gif)
 
 ## Why are we making this change?
 The notification feature gives you more autonomy to understand and address issues related to store publications. It enables you to precisely identify and report issues and retry the publication process.
diff --git a/docs/announcements/en/improvement-of-discount-price-viewing-experience.md b/docs/announcements/en/improvement-of-discount-price-viewing-experience.md
index 6518bee28..1fc9a744f 100644
--- a/docs/announcements/en/improvement-of-discount-price-viewing-experience.md
+++ b/docs/announcements/en/improvement-of-discount-price-viewing-experience.md
@@ -24,16 +24,16 @@ Before this change, customers could experience issues in the order summary if th
 Consider, for instance, a customer that wants to buy a product that costs US$ 600 and is eligible for a 10% discount for prepayment in full. The customer proceeds to checkout and lands on the order summary page, where they must select a payment option. Here are the three main error scenarios that could occur:
 
 - The customer has not selected a payment option yet, and the price is displayed without the discount in all options, even the one that is eligible for it.
-![O usuário ainda não selecionou um número de parcelas](//images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
+![O usuário ainda não selecionou um número de parcelas](https://images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
 
 - The customer has selected a payment option that is not eligible for the discount, and the price is displayed without the discount in all options, even the one that is eligible for it (prepayment in full).
-![O usuário selecionou um número de parcelas não elegível para desconto](//images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
+![O usuário selecionou um número de parcelas não elegível para desconto](https://images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
 
 - The customer has selected a payment option that is eligible for the discount (prepayment in full), and the discount is applied to all options, even the ones that are not eligible for it.
-![O usuário selecionou um número de parcelas elegível para desconto (à vista)](//images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
+![O usuário selecionou um número de parcelas elegível para desconto (à vista)](https://images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
 
 With this change, discounts will be displayed correctly in the payment options that are eligible for them.
-![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](//images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
+![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](https://images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md b/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md
index b633d2745..520a2b9d4 100644
--- a/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md
+++ b/docs/announcements/en/improvements-in-exporting-prices-via-spreadsheet.md
@@ -25,7 +25,7 @@ On VTEX, you can change the price many times a day according to your store's str
 
 You can add prices via spreadsheet in two steps, exporting and importing. The price export had its experience improved with new features to give the user more visibility about the status of each price export spreadsheet.
 
-![exportacao en](//images.ctfassets.net/alneenqid6w5/5mPN6MnLBwQOvlRAccbT58/c5c7b58769f5355ac63eb89c96200b6a/exportacao_en.gif)
+![exportacao en](https://images.ctfassets.net/alneenqid6w5/5mPN6MnLBwQOvlRAccbT58/c5c7b58769f5355ac63eb89c96200b6a/exportacao_en.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md b/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md
index ee8c5db7e..778178cb4 100644
--- a/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md
+++ b/docs/announcements/en/improvements-to-unified-search-in-vtex-sales-app.md
@@ -31,7 +31,7 @@ This improvement allows sales associates to find products beyond the store's inv
 
 - **Optimization for slow connections:** By leveraging browser caching, the search will return new information only when necessary, guaranteeing a fast response even in scenarios with slow internet connections.
 
-![Mobile - EN](//images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/13a9e307f44564906b210cc72a38c436/mobile__1_.gif)
+![Mobile - EN](https://images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/13a9e307f44564906b210cc72a38c436/mobile__1_.gif)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md b/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md
index ef7292a36..02e102fbb 100644
--- a/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md
+++ b/docs/announcements/en/increase-your-sales-with-a-new-order-authorization-screen.md
@@ -22,7 +22,7 @@ This tool allows to control order approvals with changes in their values. The ch
 ## What changes? 
 Now, instead of opening a ticket directly with the support, you can manage the authorization rules by admin. To do this, go to the path: Menu - Order Management - Order Authorization.
 
-![ENAutorizacaoPedidos.PNG?h=250](//images.ctfassets.net/alneenqid6w5/5DZywamKgUPvEGpYkTfZZ5/02ce2c609e45a7eccfacf103b5351f29/ENAutorizacaoPedidos.PNG_h_250)
+![ENAutorizacaoPedidos.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/5DZywamKgUPvEGpYkTfZZ5/02ce2c609e45a7eccfacf103b5351f29/ENAutorizacaoPedidos.PNG_h_250)
 
 ## What you need to do
 It is important to mention that the store will not lose the previous rules, which were done by opening a ticket to the support team. They will automatically update on the new screen.
diff --git a/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
index e3b3a2e86..3f9e39a9b 100644
--- a/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
@@ -19,7 +19,7 @@ Starting from May 31st, we are launching for all VTEX stores the beta version of
 
 The **Shipping Strategy** pages have been updated according to the new VTEX design system, as shown below:
 
-![nova_estrategia_envio_announcement_boards_EN](//images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/9a19eb3111c11ccc7b8f085255449b1e/nova_estrategia_envio_announcement_boards_EN.png)
+![nova_estrategia_envio_announcement_boards_EN](https://images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/9a19eb3111c11ccc7b8f085255449b1e/nova_estrategia_envio_announcement_boards_EN.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md b/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
index 82828a2ec..adf426f16 100644
--- a/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
+++ b/docs/announcements/en/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
@@ -28,4 +28,4 @@ When trying to access a store's Admin using an email address, you have the optio
 
 Security is a major focus here at VTEX, which takes center stage even more as major events like Black Friday comes into play. This new feature can help identify the source of an unauthorized access attempt.
 
-![IP Geolocation email - EN](//images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/97307ceb15b0b247e4ae14c3f29bd607/IP_Geolocation_email_-_EN.png)
+![IP Geolocation email - EN](https://images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/97307ceb15b0b247e4ae14c3f29bd607/IP_Geolocation_email_-_EN.png)
diff --git a/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
index 700415bce..5d9661957 100644
--- a/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
+++ b/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Global launch of lead time, an optional SKU-level shipp
 
 VTEX has made [lead time](https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B), a shipping time setting for inventory SKUs, available to all stores. In other words, you can set an additional shipping time at SKU level when calculating the shipping promises displayed to customers at checkout.
 
-![lead_time_image_total_time_EN](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
+![lead_time_image_total_time_EN](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
 
 The store's shipping will remain unchanged when not configured, as lead time is optional. Note that the checkout consolidation rules are maintained, calculating the total shipping time of the order based on the longest shipping time among the items.
 
@@ -31,7 +31,7 @@ Previously, the order [shipping calculation](https://help.vtex.com/en/tutorial/c
 
 Now, you can also configure the shipping time at SKU level with the new lead time column on the [Inventory Management](https://help.vtex.com/en/tutorial/gerenciar-inventario--tutorials_139) page, which can be found in your VTEX Admin under **Catalog > Inventory > Inventory Management**, as shown in the image below:
 
-![lead_time_inventory_management_EN](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png) 
+![lead_time_inventory_management_EN](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png) 
 
 <div class="alert alert-warning">
 In the VTEX Admin, the lead time is configured in days, with a 365-day limit. By default, the days are calculated in business days, but you can configure your shipping policy to <a href="https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configuring-lead-time-calculation-in-calendar-days-optional">calculate them in calendar days</a>. You need to use the <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a> endpoint to configure periods in hours, minutes, and seconds.
diff --git a/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md b/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md
index 50fd7a3d6..616f15ab2 100644
--- a/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md
+++ b/docs/announcements/en/live-shopping-the-vtex-app-to-broadcast-live-events.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'The app allows stores to carry out live broadcasts, pro
 
 The Live Shopping app is responsible for revolutionizing your relationship with your customers: use it to broadcast live on your store’s website, promoting product collections, increasing selling rates, and enhancing user experience simultaneously and in real-time.
 
-![live-shopping-overviewen](//images.contentful.com/alneenqid6w5/6QNneCank2FRHN1M5pZVF1/ba18d4b047e7bad242dd8d739cc1f34a/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
+![live-shopping-overviewen](https://images.contentful.com/alneenqid6w5/6QNneCank2FRHN1M5pZVF1/ba18d4b047e7bad242dd8d739cc1f34a/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
 
 The application is available on the [VTEX App Store](https://apps.vtex.com/) and can be downloaded for a fair subscription price by all stores running on VTEX IO and Legacy.
 
@@ -42,7 +42,7 @@ Behind the scenes on the Admin, it allows you to:
 - Set a list of forbidden words that will be blocked in the realtime chat;
 - Propose polls and quizzes to your users.
 
-![live-shopping-event-details-en](//images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/e1929b824a37a1e0c1b21a0e3bf38ab8/image4.png)
+![live-shopping-event-details-en](https://images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/e1929b824a37a1e0c1b21a0e3bf38ab8/image4.png)
 
 ## What are the advantages?
 
diff --git a/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
index 252f4f518..a7e8ba235 100644
--- a/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
+++ b/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -25,7 +25,7 @@ Now, the Luhn algorithm will ensure that only a valid card number can be used fo
 
 If a customer enters an incorrect number, an error message is displayed at checkout. In such cases, the customer must check and correct the number to complete the purchase.
 
-![algoritmo_luhn_en](//images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/ccd302d3086caaeca01c5725bdbd8b2d/algoritmo_luhn_en.PNG)
+![algoritmo_luhn_en](https://images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/ccd302d3086caaeca01c5725bdbd8b2d/algoritmo_luhn_en.PNG)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/marketplace-improvements-on-received-skus.md b/docs/announcements/en/marketplace-improvements-on-received-skus.md
index 7531f8981..b1705fdd1 100644
--- a/docs/announcements/en/marketplace-improvements-on-received-skus.md
+++ b/docs/announcements/en/marketplace-improvements-on-received-skus.md
@@ -29,7 +29,7 @@ No configuration is needed to activate this functionality - it will be installed
 
 It is worth noting that this action can be undone. It is possible to approve a blocked SKU through REST API if the marketplace wishes to receive it again as a suggestion from the seller. To learn more about SKU approval, access our API documentation on the Developer Portal.
 
-![EN SKUs Recebidos Announcement](//images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/fab32d8d2bbf1b59bace4e2fb0d85ac5/EN_SKUs_Recebidos_Announcement.jpg)
+![EN SKUs Recebidos Announcement](https://images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/fab32d8d2bbf1b59bace4e2fb0d85ac5/EN_SKUs_Recebidos_Announcement.jpg)
 
 ## Configuring automatic SKU approval
 
diff --git a/docs/announcements/en/marketplace-network-has-been-improved.md b/docs/announcements/en/marketplace-network-has-been-improved.md
index 2de558b0c..8eeb19d1a 100644
--- a/docs/announcements/en/marketplace-network-has-been-improved.md
+++ b/docs/announcements/en/marketplace-network-has-been-improved.md
@@ -19,7 +19,7 @@ A big challenge for marketplaces and sellers in our ecosystem is connecting with
 
 The Marketplace Network has been revamped to improve your experience. In addition, it is no longer necessary to download the app from our App Store, as the feature has been automatically added to all stores that act as sellers or marketplaces.
 
-![Marketplace network tour EN](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
+![Marketplace network tour EN](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
 
 ## What has changed?
 The Marketplace Network pages have undergone some changes:
diff --git a/docs/announcements/en/marketplace-new-offer-quality-filters.md b/docs/announcements/en/marketplace-new-offer-quality-filters.md
index 92ae7077d..2a68d138a 100644
--- a/docs/announcements/en/marketplace-new-offer-quality-filters.md
+++ b/docs/announcements/en/marketplace-new-offer-quality-filters.md
@@ -21,7 +21,7 @@ To give marketplaces more control over the approval criteria for an offer, we cr
 
 Thus, the SKUs that are sent to the marketplace meet the requirements relevant to catalog curation. 
 
- ![Offer Quality gif](//images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/ecf196465a00c5b0e12eca29f1c9e3f4/Offer_Quality_01.gif)
+ ![Offer Quality gif](https://images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/ecf196465a00c5b0e12eca29f1c9e3f4/Offer_Quality_01.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md b/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md
index d4959c722..e8e0b2049 100644
--- a/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md
+++ b/docs/announcements/en/marketplace-new-sidebar-with-received-sku-details.md
@@ -24,7 +24,7 @@ Previously, to check a received SKU's information, you had to leave the main lis
 
 The sidebar contains the SKU's images, price, inventory levels, and product attributes such as a description, specifications, codes and IDs. It also includes the matching percentage that the SKU received from the [matcher](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) set up in your store. You can still access the SKU’s full details by clicking on the button *View details page*.
 
-![EN Sidebar received](//images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/e77bda0e72c12f4190a3fe61249a7e65/EN_Sidebar_received.gif)
+![EN Sidebar received](https://images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/e77bda0e72c12f4190a3fe61249a7e65/EN_Sidebar_received.gif)
 
 ## Why did we make this change?
 We developed the sidebar to provide more agility to your operation and facilitate the cataloging of received SKUs, by allowing you to:  
diff --git a/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md b/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md
index 1b7490875..955d45b25 100644
--- a/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md
+++ b/docs/announcements/en/marketplacenetwork-and-integrations-are-now-a-single-page.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'We have unified the Marketplace Network and the Integra
 
 To unify the opportunities to connect to VTEX and external marketplaces, we have merged the Integrations and Marketplace Network pages, now called __Marketplaces and Integrations__. The update will be available in all VTEX accounts as of May 03, 2023.  
 
-![Marketplaces and Integrations](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
+![Marketplaces and Integrations](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
 
 ## What has changed?  
 
diff --git a/docs/announcements/en/marketplaces-received-skus-beta.md b/docs/announcements/en/marketplaces-received-skus-beta.md
index 17e2c1f5b..7fd269e02 100644
--- a/docs/announcements/en/marketplaces-received-skus-beta.md
+++ b/docs/announcements/en/marketplaces-received-skus-beta.md
@@ -25,7 +25,7 @@ This open beta is the first in a series of product updates and improvements to c
 
 One of the first and principal improvements is the new way to select SKUs en masse — so you can approve or reject them in bulk. Aligned with our [Styleguide](https://styleguide.vtex.com/ "Styleguide"), the bulk selection will make your work faster and better.
 
-![received-skus-bulk](//images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
+![received-skus-bulk](https://images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
 
 
 
@@ -33,13 +33,13 @@ One of the first and principal improvements is the new way to select SKUs en mas
 One of the challenges in managing items from multiple sellers is prioritizing your never-ending items list. To help you with that we've built a brand new __ordering__ feature, where you can reorder all submissions according to price and – one of the main improvements – by inventory availability. See how many items are available at a glance, so you can approve the SKUs that will perform better.
 
 
-![received-skus-ordering](//images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
+![received-skus-ordering](https://images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
 
 
 This extends to the new __filtering__ tool. See and filter SKUs by category, brand, and seller in a simple and intuitive way.
 
 
-![received-skus-filtering](//images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
+![received-skus-filtering](https://images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
 
 
 
diff --git a/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md b/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md
index b4e41e535..3e866b990 100644
--- a/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md
+++ b/docs/announcements/en/master-data-v1-dynamic-settings-deprecation.md
@@ -33,7 +33,7 @@ The **Calculated field** was a setting within the [data entity](https://help.vte
 
 This field type and the calculated fields created will no longer be available from June 17, 2024, as illustrated below. 
 
-![image5](//images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/f0f168a3da476c6dfce2d74060569f98/image5.png)
+![image5](https://images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/f0f168a3da476c6dfce2d74060569f98/image5.png)
 
 ### Change field value
 
@@ -41,7 +41,7 @@ When configuring triggers, the **Change field value** option allows you to add C
 
 The **Change field value** option, illustrated below, will no longer be available when configuring trigger actions from June 17, 2024. Triggers previously created with this option will continue to work until that date.
 
-![image2](//images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/cb208350954b305141787aa0b4c65407/image2.png)
+![image2](https://images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/cb208350954b305141787aa0b4c65407/image2.png)
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
index 2e17afec9..f3d79f5b3 100644
--- a/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
@@ -33,7 +33,7 @@ There are two possible ways to achieve the same effect of the Maximum Price per
 
 You can set up a [Regular Promotion](/en/tutorial/regular-promotion) with the __Maximum Price per Item__ discount.
 
-![PrecoMaximoEN](//images.contentful.com/alneenqid6w5/ZqS2JBJtEkgusUu4qOsEE/ab84f34757924220efe4d44250d499a5/PrecoMaximoEN.png)
+![PrecoMaximoEN](https://images.contentful.com/alneenqid6w5/ZqS2JBJtEkgusUu4qOsEE/ab84f34757924220efe4d44250d499a5/PrecoMaximoEN.png)
 
 This is a better scenario than the previous one, since retailers have more options for grouping, for example, by product category.
 
diff --git a/docs/announcements/en/mercado-libre-integration-new-interface-for-mapping-categories-and.md b/docs/announcements/en/mercado-libre-integration-new-interface-for-mapping-categories-and.md
index cdb615985..ad230de1d 100644
--- a/docs/announcements/en/mercado-libre-integration-new-interface-for-mapping-categories-and.md
+++ b/docs/announcements/en/mercado-libre-integration-new-interface-for-mapping-categories-and.md
@@ -19,7 +19,7 @@ Continuing the improvements made for [Mercado Libre certification](https://help.
 
 Prior to certification, sellers had to fill out the [mapping template](https://help.vtex.com/en/tutorial/mapeamento-de-categorias-variacoes-e-atributos-do-mercado-libre--4xNFUZZmboCSUVdLCFo6eA) with the categories and attributes of the products they wanted to list on Mercado Libre. The new interface for mapping categories and attributes will replace the mapping template.
 
-![announcement mapperEN](//images.contentful.com/alneenqid6w5/4lbnm6aagle6ANYGorCsA0/8e62cc6cd46b1a9a1507e65f96b6226c/announcement_mapperEN.gif)
+![announcement mapperEN](https://images.contentful.com/alneenqid6w5/4lbnm6aagle6ANYGorCsA0/8e62cc6cd46b1a9a1507e65f96b6226c/announcement_mapperEN.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md b/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md
index ed2e3e58f..faaa1b4e5 100644
--- a/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md
+++ b/docs/announcements/en/mercado-libre-integration-new-promotion-management-interface.md
@@ -19,7 +19,7 @@ Continuing with the improvements implemented for the [Mercado Libre certificatio
 
 On the new Mercado Libre **Promotions** page, you can manage a list of different promotional campaigns on the platform available for your store.
 
-![Promotions](//images.ctfassets.net/alneenqid6w5/1uv8mQZR9ey8oQsnhDbvCo/eae937e7894481e7f1e555f5a9993c61/Promotions.gif)
+![Promotions](https://images.ctfassets.net/alneenqid6w5/1uv8mQZR9ey8oQsnhDbvCo/eae937e7894481e7f1e555f5a9993c61/Promotions.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md b/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
index f4d53aa9c..f5d448920 100644
--- a/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
+++ b/docs/announcements/en/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
@@ -19,14 +19,14 @@ From now on, your store can use a semicolon (`;`) to concatenate e-mail addresse
 
 This feature works for both the copy field (`Cc`) and the hidden copy field (`Bcc`), just as the comma already worked. The two concatenation options are now valid.
 
-![Message Center bug fix - EN](//images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
+![Message Center bug fix - EN](https://images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
 
 This simple change in the module responsible for sending transactional emails dramatically reduced the error rate on customer communications.
 
 The chart below shows the error rate of a store before we implemented the support for semicolon concatenation. More than 90% of e-mails failed every day.
 
-![Message Center bug fix 2](//images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
+![Message Center bug fix 2](https://images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
 
 After the improvement was implemented, the errors in sending transactional emails from the same store were completely eliminated, as this other chart shows:
 
-![Message Center bug fix 3](//images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
+![Message Center bug fix 3](https://images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
diff --git a/docs/announcements/en/multi-currency-gift-card.md b/docs/announcements/en/multi-currency-gift-card.md
index 3fca00f09..37193d8b3 100644
--- a/docs/announcements/en/multi-currency-gift-card.md
+++ b/docs/announcements/en/multi-currency-gift-card.md
@@ -39,7 +39,7 @@ To create a gift card using a specific currency, follow the steps below:
 4. Complete the other fields for creating the gift card.
 5. Click `Save`.
 
-![Multi-currency gift card](//images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/9c698709e61906ad413c76cfbbbb4c46/GiftCard_Multicurrency_EN_1.PNG)
+![Multi-currency gift card](https://images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/9c698709e61906ad413c76cfbbbb4c46/GiftCard_Multicurrency_EN_1.PNG)
 
 The currencies available will be the same as those in the [trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) of each store.
 
diff --git a/docs/announcements/en/my-authentication-section-in-my-account.md b/docs/announcements/en/my-authentication-section-in-my-account.md
index 1b79bb500..a4018efc3 100644
--- a/docs/announcements/en/my-authentication-section-in-my-account.md
+++ b/docs/announcements/en/my-authentication-section-in-my-account.md
@@ -25,15 +25,15 @@ This change will affect all VTEX stores. Because this change interferes with som
 
 In this section, all users can manage their password and login sessions, allowing them to sign out other sessions remotely. For more details on using My Authentication, see the [Authentication section on the article Setting up My account](https://help.vtex.com/en/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh).
 
-![My Authentication app EN](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
+![My Authentication app EN](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
 
-![My Authentication Session Management EN](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
+![My Authentication Session Management EN](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
 
 On September 29, the component for managing passwords will also be removed from the user profile page to prevent duplication issues. The images below show examples of a user profile page with and without the password management component.
 
-![My Account with password EN](//images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/0ae8b228f91e42d0baef43d66e99c43f/My_Account_with_password_EN.png)
+![My Account with password EN](https://images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/0ae8b228f91e42d0baef43d66e99c43f/My_Account_with_password_EN.png)
 
-![My Account no password EN](//images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/08d27ed752e8e08a1019272cc832a182/My_Account_no_password_EN.png)
+![My Account no password EN](https://images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/08d27ed752e8e08a1019272cc832a182/My_Account_no_password_EN.png)
 
 ## Why did we make this change?
 
@@ -66,12 +66,12 @@ To make the My authentication section visible for your customers, follow the ste
 1. On the left side menu in the Admin, go to **ACCOUNT SETTINGS**.
 2. Click on **Apps**.
 3. Click on **My apps**.  
-![My apps menu EN](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
+![My apps menu EN](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
 4. Go to the **My Account** app and click on `Settings`.  
-![My apps installed EN](//images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/eec5a07fc1a77033113a4767b4672fc7/My_apps_installed_EN.png)
+![My apps installed EN](https://images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/eec5a07fc1a77033113a4767b4672fc7/My_apps_installed_EN.png)
 5. In the **AUTHENTICATION** field, check the `Visible` box.
 6. Click on `Save`.  
-![My Authentication visible setting EN](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
+![My Authentication visible setting EN](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
 
 You can also directly access the My Account app settings via URL.
 
@@ -80,4 +80,4 @@ You can also directly access the My Account app settings via URL.
 
 After enabling the **Authentication** section, it will be displayed for your customers in their user profiles in your store, and they can access it using the left side menu on the My Account page.
 
-![My Authentication visible setting EN](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
+![My Authentication visible setting EN](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/205cccf0a08be76be0c91e4074d77215/My_Authentication_visible_setting_EN.png)
diff --git a/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md b/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
index 93590e70f..abf8275c6 100644
--- a/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
+++ b/docs/announcements/en/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: "We've redesigned the Admin home page, which now feature
 
 The [Overview (beta)](https://help.vtex.com/en/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) page in your VTEX Admin has been redesigned and now offers new charts, metrics, and views. These new features allow you to monitor your operation in real time, providing insights on metrics for you and your team to get quick feedback on the actions taken in the store and act promptly on improvements.
 
-![EN visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/88b40023b0c9d38dae93d2ccb563e378/EN_visa__o_geral_beta.png)
+![EN visão geral beta](https://images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/88b40023b0c9d38dae93d2ccb563e378/EN_visa__o_geral_beta.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/new-indexation-history-screen.md b/docs/announcements/en/new-indexation-history-screen.md
index 2412a2f0e..f68e13404 100644
--- a/docs/announcements/en/new-indexation-history-screen.md
+++ b/docs/announcements/en/new-indexation-history-screen.md
@@ -19,7 +19,7 @@ In every ecommerce operation, it is necessary to add or edit product information
 
 To improve the catalog indexing monitoring experience, we redesigned the **Indexing History** page in the VTEX Admin. The new interface allows you to track the indexing time of products and the indexing status of your store.
 
-![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+![Histórico da Indexação 1 - EN](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/new-orders-module-interface-official.md b/docs/announcements/en/new-orders-module-interface-official.md
index ffe3ecfd6..1fa947490 100644
--- a/docs/announcements/en/new-orders-module-interface-official.md
+++ b/docs/announcements/en/new-orders-module-interface-official.md
@@ -27,15 +27,15 @@ The new interface, which will be official as of February 1st, has two main new f
 
 * **No-date limit order search:** You can search for orders without setting a date limit, which returns all orders related to the criteria used, regardless of the order creation date. This search cannot be combined with other filters. However, you can select a custom search period of up to 6 months and then combine it with the filters. Learn more in the article [Filter orders on All orders](https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192).
 
-  ![busca_sem_limite_data_all_en](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
+  ![busca_sem_limite_data_all_en](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
 
 * **Order diagram:** In the _Order status_ section of the new interface, by default, a timeline with the events of the order is displayed. Now you can also see the _Order diagram_. When you click `View diagram`, a modal opens and displays the following image:
 
-  ![diagrama_pedido_en](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
+  ![diagrama_pedido_en](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
 
 For those not using the beta version yet, the image below maps the  fields between the old and new versions of the **Order Details** page:
 
-![board_comparativo_interface_pedido_v2_en](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
+![board_comparativo_interface_pedido_v2_en](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
index adc379ef8..59df44f9f 100644
--- a/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
+++ b/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
@@ -23,7 +23,7 @@ From now on, you can view the information of providers in your store more quickl
 
 The screen for adding a new provider, editing settings, and searching for providers was also improved for better navigation.
 
-![new_admin_providers_interface](//images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/af1aed9f59ac711ba1f07d5d84b54eb5/Announcement_interface_provedor_EN.JPG)
+![new_admin_providers_interface](https://images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/af1aed9f59ac711ba1f07d5d84b54eb5/Announcement_interface_provedor_EN.JPG)
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md b/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md
index af9c2f77c..ec3526b13 100644
--- a/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md
+++ b/docs/announcements/en/new-promotion-list-manage-your-promotions-more-efficiently.md
@@ -30,7 +30,7 @@ We developed a new interface for the Promotion List, which includes:
 * Exporting your active promotions list.
 * Duplicating active or archived promotions for a faster creation process.
 
-![lista-promocoes-en](//images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/f08b0d232c4b386e29cc75c436f91471/promotions-list-en.PNG)
+![lista-promocoes-en](https://images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/f08b0d232c4b386e29cc75c436f91471/promotions-list-en.PNG)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/new-roles-page.md b/docs/announcements/en/new-roles-page.md
index c8d31e1c7..e94cb70ff 100644
--- a/docs/announcements/en/new-roles-page.md
+++ b/docs/announcements/en/new-roles-page.md
@@ -28,7 +28,7 @@ Besides all features from the previous version, the new **Roles** page allows yo
 *	Access the complete list of roles added to your store with a more intuitive and elegant design, updated for the [New VTEX Admin](https://help.vtex.com/en/tutorial/admin-vtex-start-here--531cHtUCUi3puRXNDmKziw).
 *	View useful information for managing roles directly in the list, such as the number of users associated with each profile, the type of profile (predefined or customized), and the date the profile was created.
 
-![roles-en](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/d0c8e68b433a987fb1d0c9f031726d6f/roles-en.png)
+![roles-en](https://images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/d0c8e68b433a987fb1d0c9f031726d6f/roles-en.png)
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/new-sales-performance-dashboard.md b/docs/announcements/en/new-sales-performance-dashboard.md
index 44a3f6a6a..53112a837 100644
--- a/docs/announcements/en/new-sales-performance-dashboard.md
+++ b/docs/announcements/en/new-sales-performance-dashboard.md
@@ -19,7 +19,7 @@ With an ever-increasing volume of data available for ecommerce operations to eva
 
 The dashboard allows users to analyze data from all sales channels of the store and its sellers, including metrics on revenue, orders, average ticket, and more. It also includes charts and tables so you can compare results from different periods, and introduces eleven filter options to provide unified insights into your entire operation.
 
-![Sales Perf Dash EN](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
+![Sales Perf Dash EN](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
 
 ## What has changed?
 Previously, your VTEX Admin only had the Insights page to generate business intelligence from your operations data. We have now included the Sales Performance page, where you can have a more detailed view of the results of the different sales channels of your store. The Insights page will remain in your VTEX Admin.
diff --git a/docs/announcements/en/new-sku-bindings-interface.md b/docs/announcements/en/new-sku-bindings-interface.md
index 7abaad92d..0e991ecf2 100644
--- a/docs/announcements/en/new-sku-bindings-interface.md
+++ b/docs/announcements/en/new-sku-bindings-interface.md
@@ -19,7 +19,7 @@ VTEX allows your store to act both as a [seller](https://help.vtex.com/en/tutori
 
 To improve this experience, we redesigned the **SKU Bindings** page in the VTEX Admin. The new interface allows you to track and manage the binding relationship between seller and marketplace SKUs in a simpler and more agile way.
 
-![sku_binding_page_EN_final](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/495c45bef9699a32fbfb55842890a91f/sku_binding_page_EN_final.png)
+![sku_binding_page_EN_final](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/495c45bef9699a32fbfb55842890a91f/sku_binding_page_EN_final.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/new-subscriptions-module.md b/docs/announcements/en/new-subscriptions-module.md
index 69e262c44..66a0491a4 100644
--- a/docs/announcements/en/new-subscriptions-module.md
+++ b/docs/announcements/en/new-subscriptions-module.md
@@ -39,37 +39,37 @@ The improvements to the Subscription system include new features for your end cu
 #### Subscription details 
 Our subscription details page has been redesigned to improve customer experience by reducing the time to find information and perform tasks. In addition, a new feature allows you to add items to an existing subscription.
 
-![img1 subscriptions EN](//images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/01b71fce5ac6f65621c37a917a798050/img1_subscriptions_EN.png)
+![img1 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/01b71fce5ac6f65621c37a917a798050/img1_subscriptions_EN.png)
 
 #### Notification box
 Now you can use a notification box to improve your communication with users about actions they need to perform or to communicate important events about your subscriptions.
 
-![img2 subscriptions EN](//images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/b925e16f3a4eefc38b2b2edc6af2333a/img2_subscriptions_EN.png)
+![img2 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/b925e16f3a4eefc38b2b2edc6af2333a/img2_subscriptions_EN.png)
 
 #### Adding products to your subscription
 You can also add new items to your subscription by searching for products available in the store.
 
-![img3 subscriptions EN](//images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/adbd8d1d4cc519b9f687e27f4fea3a5a/img3_subscriptions_EN.png)
+![img3 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/adbd8d1d4cc519b9f687e27f4fea3a5a/img3_subscriptions_EN.png)
 
 #### Creating a new subscription
 A long-awaited feature is now available: a screen for creating subscriptions. You can now configure a new subscription without the need to go through the checkout and place an order. To do that, click on the __New subscription__ button on the subscriptions list.
 
-![img4 subscriptions EN](//images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/784b7439f54cedde4fc381f3a275f556/img4_subscriptions_EN.png)
+![img4 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/784b7439f54cedde4fc381f3a275f556/img4_subscriptions_EN.png)
 
 ### New subscription concept in the VTEX system
 Previously, in the VTEX system, a subscription consisted of an SKU linked to a purchase configuration. It allowed the customer to subscribe to SKUs with different shipping addresses and different payment methods—which represented an evolution compared to the first version of the system.
 
 #### Before:
-![img5 subscriptions EN](//images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/107288b39d263aad20e153aa3c0a045a/img5_subscriptions_EN.png)
+![img5 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/107288b39d263aad20e153aa3c0a045a/img5_subscriptions_EN.png)
 
-![img6 subscriptions EN](//images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/18bbe8fa02f3361873d6e2ceba450d01/img6_subscriptions_EN.png)
+![img6 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/18bbe8fa02f3361873d6e2ceba450d01/img6_subscriptions_EN.png)
 
-![img7 subscriptions EN](//images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/6e0250e84776f69dad0d8f1c17ee1eff/img7_subscriptions_EN.png)
+![img7 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/6e0250e84776f69dad0d8f1c17ee1eff/img7_subscriptions_EN.png)
 
 The subscription now consists of an SKU list and a particular purchase configuration. This means that we have removed the concept of Subscription Groups from our system. For more information, read our article [How subscription works](https://help.vtex.com/en/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453). The diagram below shows our new subscription concept:
 
 #### Now:
-![img8 subscriptions EN](//images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/33a97511d0c48f954b9de33bcad8fa40/img8_subscriptions_EN.png)
+![img8 subscriptions EN](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/33a97511d0c48f954b9de33bcad8fa40/img8_subscriptions_EN.png)
 
 ### Subscription order cycle date
 
diff --git a/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md b/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md
index 46d34cb30..fa095e887 100644
--- a/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md
+++ b/docs/announcements/en/new-ui-for-the-admins-user-management-dashboard.md
@@ -22,7 +22,7 @@ The user management dashboard design has been refreshed with the same interface
 - The MFA (multi-factor authentication) configuration is now displayed for each user in the user list.
 - A button to export the user list data to a csv file that includes id, email and name.
 
-![Lista Usuários User Management EN](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
+![Lista Usuários User Management EN](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
 
 In addition, the dashboard has undergone some changes:
 
diff --git a/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md b/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md
index cf11b2fc3..64df6554a 100644
--- a/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md
+++ b/docs/announcements/en/novo-layout-no-e-mail-de-codigo-de-acesso.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: "We've updated the layout for the email you receive when
 
 We've updated the layout for the email you receive when requesting an access code for your admin. From now on, every time access to login or change password is requested, you'll receive an email as the one shown below:
 
-![announcement-novo-layout-email-codigo-acesso EN](//images.ctfassets.net/alneenqid6w5/5jLkyQ1zg1ZhtORCCLq4OR/3f69be2db4b8edfd6685e74216093b8a/announcement-novo-layout-email-codigo-acesso_EN.png)
+![announcement-novo-layout-email-codigo-acesso EN](https://images.ctfassets.net/alneenqid6w5/5jLkyQ1zg1ZhtORCCLq4OR/3f69be2db4b8edfd6685e74216093b8a/announcement-novo-layout-email-codigo-acesso_EN.png)
 
 ## What changes
 The new version makes the layout more seamless and usable, in addition to making it more coherent with VTEX's visual identity.
diff --git a/docs/announcements/en/offer-pickup-points-for-subscription-orders.md b/docs/announcements/en/offer-pickup-points-for-subscription-orders.md
index d7eb03bde..a0f3bb586 100644
--- a/docs/announcements/en/offer-pickup-points-for-subscription-orders.md
+++ b/docs/announcements/en/offer-pickup-points-for-subscription-orders.md
@@ -24,7 +24,7 @@ The pickup points feature for subscriptions is available in beta only for accoun
 
 Previously, pickup was not a delivery option available for subscriptions. With this feature, end customers can choose pickup points for items in a subscription order at checkout, as illustrated in the image below.
 
-![subscriptionspickup EN](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
+![subscriptionspickup EN](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
 
 You can also assign pickup points to new and existing subscriptions via the[ Subscriptions API](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1).
 
diff --git a/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md b/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md
index b35993fcc..cbe631000 100644
--- a/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md
+++ b/docs/announcements/en/offer-status-module-for-integrations-with-vtex-marketplaces.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Monitor your offers with the new Offer Status module'
 
 __Offer Status__ is the new VTEX Admin module that allows sellers to monitor offers being sent and synced from integrations with VTEX marketplaces worldwide. To access the module, in the VTEX Admin, go to __Marketplace > Connections > Offer Status,__ or type __Offer Status__ in the search bar.
 
-![Offer Status Screen](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/2de2b349e1c114b7b50db65533eee1df/-EN-_Offer_Status_-_GIF.gif)
+![Offer Status Screen](https://downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/2de2b349e1c114b7b50db65533eee1df/-EN-_Offer_Status_-_GIF.gif)
 
 ## Why did we develop this feature?
 
diff --git a/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md b/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
index 6ce198087..05e3f1d3d 100644
--- a/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
+++ b/docs/announcements/en/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
@@ -34,7 +34,7 @@ This change's review and subsequent adjustment should be implemented following t
 
 Required steps for review and adjustment:
 
-1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Customization__: if the "/account/orders" page is affected by any front-end customization, it should be migrated and adapted to the new URL: "/account#/orders". Review and perform all necessary tests to ensure that all custom resources are functioning properly.  
 3. __Site links__: Review and update all of the site's custom links, in addition to the ones pertaining to transactional emails that would previously direct users to "/account/orders". These links should now direct users to "/account#/orders".
 
diff --git a/docs/announcements/en/price-filters-more-search-flexibility.md b/docs/announcements/en/price-filters-more-search-flexibility.md
index 68b088ae1..0add1d5b9 100644
--- a/docs/announcements/en/price-filters-more-search-flexibility.md
+++ b/docs/announcements/en/price-filters-more-search-flexibility.md
@@ -23,7 +23,7 @@ Now you can filter prices by combining multiple Categories and Brands, as well a
 
 This update enables you to export more specific prices from filter selection.
 
-![filtro preco-EN](//images.ctfassets.net/alneenqid6w5/6zuHx35ldRSPGIGMCw61VH/f16a50faf4cfba4d806f8d6aa7430735/filtro_preco-EN.png)
+![filtro preco-EN](https://images.ctfassets.net/alneenqid6w5/6zuHx35ldRSPGIGMCw61VH/f16a50faf4cfba4d806f8d6aa7430735/filtro_preco-EN.png)
 
 ## What do I need to do?
 To use this new configuration, follow the steps below:
diff --git a/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md b/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
index c4c519977..d92b415e3 100644
--- a/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
+++ b/docs/announcements/en/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
@@ -31,7 +31,7 @@ To find out if your account is still using Pricing V1, follow the steps below:
 
 If you see a screen similar to the one below, it means that your account needs to migrate.
 
-![Tela pricing antiga - EN](//images.ctfassets.net/alneenqid6w5/7wk5rGZNxCldv1KHUEUIFz/e3c41c74ab30125e804250a432eb95c0/Tela_pricing_antiga_-_EN.png)
+![Tela pricing antiga - EN](https://images.ctfassets.net/alneenqid6w5/7wk5rGZNxCldv1KHUEUIFz/e3c41c74ab30125e804250a432eb95c0/Tela_pricing_antiga_-_EN.png)
 
 If your VTEX account still uses previous versions of the VTEX Admin (such as "vtexcommercestable"), it will also need to migrate. To do so, please follow the steps below:
 
diff --git a/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md b/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
index b3e428098..895f2a4b6 100644
--- a/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
+++ b/docs/announcements/en/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
@@ -32,7 +32,7 @@ From now on, the **Promotion Simulator** will be available for all VTEX stores v
 * **Test applying** other promotions to the cart before activating them, including scheduled or inactive promotions.
 * **Understand the reasons** a promotion was not applied to the cart.
 
-![promotions simulator - en-gif 3](//downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/c54434442ee4cd19b211505896daa841/promotions_simulator_gi-3.gif)
+![promotions simulator - en-gif 3](https://downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/c54434442ee4cd19b211505896daa841/promotions_simulator_gi-3.gif)
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/rate-vtexs-service-in-your-admin.md b/docs/announcements/en/rate-vtexs-service-in-your-admin.md
index b8c8aa60c..d892c92a8 100644
--- a/docs/announcements/en/rate-vtexs-service-in-your-admin.md
+++ b/docs/announcements/en/rate-vtexs-service-in-your-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'We have launched a satisfaction survey page in the VTEX
 
 We have launched the new *Satisfaction Survey* page in the VTEX Admin. Now, you can rate our support service without leaving the VTEX environment.
 
-![Pesquisa de satisfação EN](//images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/eaadd736c6ce0d1b06e9f7cf2543f643/image__17_.png)
+![Pesquisa de satisfação EN](https://images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/eaadd736c6ce0d1b06e9f7cf2543f643/image__17_.png)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
index ff3751aad..752fca65a 100644
--- a/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
+++ b/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -46,7 +46,7 @@ Ask your development team to review your integrations that use the Checkout API
 
 They should be able to follow the diagram below to assess whether an integration needs to be adjusted, according to your store's [reCAPTCHA orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) and how requests made to these endpoints are [authenticated](https://developers.vtex.com/docs/guides/authentication-overview):
 
-![reCAPTCHA diagram](//images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/077e3f3122263a78aaa5a4cf47bd9eb2/recaptcha-config-EN.png)
+![reCAPTCHA diagram](https://images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/077e3f3122263a78aaa5a4cf47bd9eb2/recaptcha-config-EN.png)
 
 - __Case 1__: *No changes are required in the integration, but your store might be at risk.*
 
diff --git a/docs/announcements/en/redesigned-products-and-skus-page.md b/docs/announcements/en/redesigned-products-and-skus-page.md
index 7536b158d..a7314264a 100644
--- a/docs/announcements/en/redesigned-products-and-skus-page.md
+++ b/docs/announcements/en/redesigned-products-and-skus-page.md
@@ -28,7 +28,7 @@ The new **Products & SKUs** interface allows you to:
 * Track product and SKU status in a more straightforward and visual way, with icons and SKU status in the list.
 * Easily identify products and SKUs with pending information waiting to be available for sale through the new **Pending** status.
 
-![catalog-products-skus-en](//images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/8efc01107b80405151eb83c94061f2cb/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_23_24_1.png)
+![catalog-products-skus-en](https://images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/8efc01107b80405151eb83c94061f2cb/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_23_24_1.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/registering-pickup-points-is-now-easier-and-faster.md b/docs/announcements/en/registering-pickup-points-is-now-easier-and-faster.md
index ca7dd81b0..e40b6c13b 100644
--- a/docs/announcements/en/registering-pickup-points-is-now-easier-and-faster.md
+++ b/docs/announcements/en/registering-pickup-points-is-now-easier-and-faster.md
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Now, you can upload an XLS file containing all the pickup points you want to offer on your website.'
 ---
 
-You don't need to register pickup points one by one anymore. Now, you can use your Admin to upload an XLS file [(like this one)](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls) with all the pickup points you want to offer on your website.
+You don't need to register pickup points one by one anymore. Now, you can use your Admin to upload an XLS file [(like this one)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls) with all the pickup points you want to offer on your website.
 
 
 ## Your logistics setup has never been this fast
diff --git a/docs/announcements/en/reusing-images-in-site-editor.md b/docs/announcements/en/reusing-images-in-site-editor.md
index ca99725f4..1b4ad7b87 100644
--- a/docs/announcements/en/reusing-images-in-site-editor.md
+++ b/docs/announcements/en/reusing-images-in-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'We have improved blocks with the native option to uploa
 
 We have improved the way you manage your images in [Site Editor](https://help.vtex.com/en/subcategory/site-editor--9Arh3cJIOYlfSD1MUC2h3) through an Image Widget, a centralized image repository that allows you to upload and reuse your store’s images. 
 
-![gif-image-widget-en](//images.contentful.com/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/14669f1c19ef2e47289c64f7ebaff7f6/yXXdu5wtTC.gif)
+![gif-image-widget-en](https://images.contentful.com/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/14669f1c19ef2e47289c64f7ebaff7f6/yXXdu5wtTC.gif)
 
 <div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 16px">
   Image Widget is available in Open Beta for VTEX IO users.
diff --git a/docs/announcements/en/sales-performance-dashboard-updates.md b/docs/announcements/en/sales-performance-dashboard-updates.md
index dae05ee98..0175b4098 100644
--- a/docs/announcements/en/sales-performance-dashboard-updates.md
+++ b/docs/announcements/en/sales-performance-dashboard-updates.md
@@ -19,7 +19,7 @@ The Sales Performance dashboard allows store operators to analyze data from all
 
 We have improved the experience on this page based on your suggestions, adding new features for applying filters, customizing views, and exploring data. 
 
-![Sales perf update EN](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
+![Sales perf update EN](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
 
 ## What has changed?
 We have enhanced existing features, such as Filters and Data, and added the Views menu. The new filter experience allows you to try different filter combinations with fewer clicks. The new Views feature has been designed to save the filters and metrics applied on the page, allowing you to access the same view combination quickly. 
diff --git a/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md b/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md
index 57fae259a..4c3628568 100644
--- a/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md
+++ b/docs/announcements/en/save-user-opt-in-using-stored-information-for-future-purchases.md
@@ -23,7 +23,7 @@ Previously, after customers entered their information at checkout or after their
 
 From now on, two checkboxes will be available on the Checkout screen, allowing users to indicate if they want their personal and payment information to be stored and used for future purchases. This will reduce your customers' shopping time. 
 
-![ Save user data opt-in EN](//images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/465f60548b25abfde675c3e81cbbcebe/Save_user_data_-_EN.PNG)
+![ Save user data opt-in EN](https://images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/465f60548b25abfde675c3e81cbbcebe/Save_user_data_-_EN.PNG)
 
 Learn more in [SmartCheckout - Customer information automatic fill-in](https://help.vtex.com/en/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan#).
 
diff --git a/docs/announcements/en/schedule-content-publication-with-site-editor.md b/docs/announcements/en/schedule-content-publication-with-site-editor.md
index aa03ae83c..bd7a431bd 100644
--- a/docs/announcements/en/schedule-content-publication-with-site-editor.md
+++ b/docs/announcements/en/schedule-content-publication-with-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'Create and schedule predefined block versions in Site E
 
 The Site Editor feature **Configurations** was updated. It is now called **Versions** and allows you to create deactivated versions of your store’s content and activate them whenever you want.
 
-![activating-versions-en](//images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/d3402adb77ed7eaada1fb51b8ac736ab/activating-versions-en.gif)
+![activating-versions-en](https://images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/d3402adb77ed7eaada1fb51b8ac736ab/activating-versions-en.gif)
 
 ## What has changed?
 Previously, the **Versions** feature was called **Configurations**, and it only allowed users to create a new activated version, such as a Carousel with promotional products or schedule to activate it. After inactivating a version, it was also not possible to activate it again.
diff --git a/docs/announcements/en/search-filters-in-instores-endless-aisle.md b/docs/announcements/en/search-filters-in-instores-endless-aisle.md
index ce5e58d3d..72c27ce22 100644
--- a/docs/announcements/en/search-filters-in-instores-endless-aisle.md
+++ b/docs/announcements/en/search-filters-in-instores-endless-aisle.md
@@ -26,7 +26,7 @@ Previously, VTEX Intelligent Search filters were not available in inStore, only
 
 With the new feature, when searching for a term, sales associates can filter results by price range, department, and brand, for example, among other configurable filters in VTEX Intelligent Search. This allows them to quickly find the desired product.
 
-![instore-filtros-en](//images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b253d8baf245473167c7ad606283b315/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_05_18.png)
+![instore-filtros-en](https://images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b253d8baf245473167c7ad606283b315/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_05_18.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
index 814545388..7e4ea2b83 100644
--- a/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
+++ b/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -30,7 +30,7 @@ Previously, the global search bar allowed you to search only the VTEX Admin page
 
 To do this, click the search bar, select the `Orders` option, and search for what you want. Each search can return up to 10 results, as shown in the image below:
 
-![order_global_search_EN](//images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/cbf95c626a1dcc5a75382fc8db06a863/order_global_search_EN.gif)
+![order_global_search_EN](https://images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/cbf95c626a1dcc5a75382fc8db06a863/order_global_search_EN.gif)
 
 By clicking a result, you will be redirected to the [Order Details page](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). The last 10 orders you searched for will be recorded in your recent search history, making access more convenient. The search record is stored at the [user](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) level and not shared among users.
 
diff --git a/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md b/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
index 72b1ade5d..b9c2ee357 100644
--- a/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
+++ b/docs/announcements/en/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
@@ -19,7 +19,7 @@ __Black Friday__ is coming. And with it comes the need to use this unique opport
 
 To help you with this task, VTEX is launching an __exclusive app in partnership with Google__, which will be available in our [App Store](https://apps.vtex.com/vtex-google-shopping/p).
 
-![Google Shopping App](//images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
+![Google Shopping App](https://images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
 
 It integrates your business with Google Ads and allows you to advertise your products on Google Shopping, using the new Smart Shopping Campaigns, and track the results easily and quickly.
 
diff --git a/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md b/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
index b47f40f37..adca3a1d9 100644
--- a/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
+++ b/docs/announcements/en/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
@@ -27,4 +27,4 @@ https://{accountName}.myvtex.com/admin/shopping-season
 
 Simply replace `{accountName}` with your store's Account Name, as in the image below.
 
-![Shopping Season Guidelines - 2023 - EN](//images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/0dbbce1dd40337f020fbcd57833af2fc/Shopping_Season_Guidelines_-_2023_-_EN.png)
+![Shopping Season Guidelines - 2023 - EN](https://images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/0dbbce1dd40337f020fbcd57833af2fc/Shopping_Season_Guidelines_-_2023_-_EN.png)
diff --git a/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md b/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md
index 59cd9337d..204ac6d8f 100644
--- a/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md
+++ b/docs/announcements/en/social-selling-share-instore-carts-using-qr-codes.md
@@ -27,7 +27,7 @@ Previously, the Social Selling feature in inStore consisted of generating a link
 
 With the change, inStore now also generates a QR code that can be scanned by customers' devices, in addition to the shareable link.
 
-![instore-social-selling-qr-code-share-en](//images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/f3ec6fdf7a587799dcf51ebdf30cf6f7/image2.png)
+![instore-social-selling-qr-code-share-en](https://images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/f3ec6fdf7a587799dcf51ebdf30cf6f7/image2.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/social-selling-share-your-instore-cart.md b/docs/announcements/en/social-selling-share-your-instore-cart.md
index 6037a2ff2..5a57bd1e7 100644
--- a/docs/announcements/en/social-selling-share-your-instore-cart.md
+++ b/docs/announcements/en/social-selling-share-your-instore-cart.md
@@ -27,7 +27,7 @@ Previously, cart sharing wasn’t possible on inStore, [only through ecommerce](
 
 With inStore Social Selling, your physical store sales reps can select products and generate a link to share the **Cart Suggestion** with one or more customers via WhatsApp, as shown below. It is also possible to copy the link and share it on other social media.
 
-![socialselling-EN2](//images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/e1fd62dd05b2468ba4cb198572a5bce8/socialselling-EN2.gif)
+![socialselling-EN2](https://images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/e1fd62dd05b2468ba4cb198572a5bce8/socialselling-EN2.gif)
 
 The sales rep can share the same link with several customers, as many times as they want. Every time someone opens this link, a new shopping cart is generated, exactly like the one created on inStore. Each cart accessed is also linked to the sales rep account and their code, if any.
 
@@ -35,7 +35,7 @@ The customers can access the cart, make the payment, and complete the purchase o
 
 The sales rep can also fill in the customer's delivery information, choose the payment method, and then share a **Payment Link**. That way, the shared cart link will have all the personal information already filled in, so the customer will only need to fill in the payment information to complete the purchase on their own device.  Check out how it works.
 
-![paymentlink EN](//images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/b20493f0a9350f2ae8574441fc6bbc9f/paymentlink_EN.gif)
+![paymentlink EN](https://images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/b20493f0a9350f2ae8574441fc6bbc9f/paymentlink_EN.gif)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md b/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md
index 8ace5107c..d061a8f15 100644
--- a/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md
+++ b/docs/announcements/en/the-native-links-to-my-account-page-will-change-review-your-settings.md
@@ -34,7 +34,7 @@ This change's review and subsequent adjustment should be implemented following t
 
 Required steps for review and adjustment:
 
-1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Basic configuration__: ensure that the template of the "/account" page (illustration below) already uses the `<vtex.cmc:accountUserProfile />` view part and update it if necessary. This view part is responsible for loading all of the customer information, including orders. The previous view parts, `<vtex.cmc:accountAddress/>` and `<vtex.cmc:orderList />`, must be deleted from this template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Customization__: if the "/account/orders" page is affected by any front-end customization, it should be migrated and adapted to the new URL: "/account#/orders". Review and perform all necessary tests to ensure that all custom resources are functioning properly.  
 3. __Site links__: Review and update all of the site's custom links, in addition to the ones pertaining to transactional emails that would previously direct users to "/account/orders". These links should now direct users to "/account#/orders".
 
diff --git a/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md b/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
index 2e8c1db59..2c25c5918 100644
--- a/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
+++ b/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
@@ -19,7 +19,7 @@ announcementSynopsisEN: 'The term "Access Profile" has been replaced by "Role" t
 
 What was called “Access Profile” in the Account Management module will now be called “Role”. This change applies only to the English interface. The Admin and all documentation have been updated with the new term. No functionality has been affected. Here’s an example of how the term appears on the Roles dashboard in the Admin:
 
-![Roles Panel](//images.ctfassets.net/alneenqid6w5/3onlQoxSxoBtgwPGtGUUdH/bd0130c89de14555d1bf9dd465c420be/Roles_Panel.png)
+![Roles Panel](https://images.ctfassets.net/alneenqid6w5/3onlQoxSxoBtgwPGtGUUdH/bd0130c89de14555d1bf9dd465c420be/Roles_Panel.png)
 
 All documents that mentioned this concept, both on our Developer Portal and Help Center, have been changed to include the new term.
 
diff --git a/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md b/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md
index 51a67155a..593a62f64 100644
--- a/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md
+++ b/docs/announcements/en/transparency-and-security-with-the-new-audit-module.md
@@ -18,7 +18,7 @@ announcementSynopsisEN: 'Launch of the new auditing tool'
 
 Ensuring your store is always in compliance with security and transparency best practices, VTEX has launched a new audit feature, **Audit**. 
 
-![Screenshot for Audit UI for announcement](//images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/1cae72785358e9622b3bbf0c481bd998/Audit_EN.png)
+![Screenshot for Audit UI for announcement](https://images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/1cae72785358e9622b3bbf0c481bd998/Audit_EN.png)
 
 From now on, users with the admin role can check operations performed in their store in a simple and fast way. You can create multiple search filters to make it easier to search for events and increase the speed of auditing processes.
 
diff --git a/docs/announcements/en/update-grants-in-the-promotions-module.md b/docs/announcements/en/update-grants-in-the-promotions-module.md
index eb6a2618c..734ea12bb 100644
--- a/docs/announcements/en/update-grants-in-the-promotions-module.md
+++ b/docs/announcements/en/update-grants-in-the-promotions-module.md
@@ -37,4 +37,4 @@ This update gives you more power over your promotions' behavior. The new buttons
 6. Tick the box next to **Use recurrence settings**
 7. Set the desired days and schedule for that promotion 
 
-![CRON 2 EN](//images.ctfassets.net/alneenqid6w5/48EFCYtz5TvqhZVXmBasyW/d37188c1a6a742e3a086fe6984eded31/CRON_2_EN.png)
+![CRON 2 EN](https://images.ctfassets.net/alneenqid6w5/48EFCYtz5TvqhZVXmBasyW/d37188c1a6a742e3a086fe6984eded31/CRON_2_EN.png)
diff --git a/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md b/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
index 55184bee1..05fcd0dd2 100644
--- a/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
+++ b/docs/announcements/en/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
@@ -32,5 +32,5 @@ The functionality can be used whenever retailers want to opt for a fixed product
 - Under "What kind and amount of tax?", choose the Nominal tax option
 - Fill in the required fields and click on save
 
-![Nominal tax EN](//images.ctfassets.net/alneenqid6w5/5ntJCk8NaGwYD4W4ZzTx9b/6217dcf2fd3ba137d84f78a7d3e8d129/Nominal_tax_EN.png)
+![Nominal tax EN](https://images.ctfassets.net/alneenqid6w5/5ntJCk8NaGwYD4W4ZzTx9b/6217dcf2fd3ba137d84f78a7d3e8d129/Nominal_tax_EN.png)
 
diff --git a/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md b/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md
index 5986df865..bc5b0be5d 100644
--- a/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md
+++ b/docs/announcements/en/ux-improvements-at-checkout-for-expired-cards.md
@@ -23,7 +23,7 @@ To continue enhancing this experience, we have included additional validation in
 
 Previously, customers could select an expired card, proceed with a purchase, and then the payment would be declined. We now flag expired cards and prevent them from being chosen at checkout, in order to offer a smoother shopping experience.
 
-![EN - Expired Cards](//images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/857a5d45b665bbde2d646f06a32d8fe2/EN_-_Expired_Cards.png)
+![EN - Expired Cards](https://images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/857a5d45b665bbde2d646f06a32d8fe2/EN_-_Expired_Cards.png)
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md b/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
index 6a205a764..58c848164 100644
--- a/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
+++ b/docs/announcements/en/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
@@ -28,7 +28,7 @@ Previously, stores using [VTEX Intelligent Search](https://help.vtex.com/en/trac
 * Pin a product to the top positions in the search results.
 * Review the main product information.
 
-![visual-merch-rules-EN-announcement](//images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/058e0548f09749d0db291a9a222e369f/visual-merch-rules-EN-announcement.png)
+![visual-merch-rules-EN-announcement](https://images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/058e0548f09749d0db291a9a222e369f/visual-merch-rules-EN-announcement.png)
 
 When creating a merchandising rule in the VTEX Admin under **Storefront > Intelligent Search > Merchandising Rules > New**, you can choose the type of editor you want to use. Read the [Merchandising Rules](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#types-of-editing) guide for more information on the differences between the manual and the visual editor.
 
diff --git a/docs/announcements/en/vtex-io-documentation-has-a-new-home.md b/docs/announcements/en/vtex-io-documentation-has-a-new-home.md
index f54d527d5..208a2bb94 100644
--- a/docs/announcements/en/vtex-io-documentation-has-a-new-home.md
+++ b/docs/announcements/en/vtex-io-documentation-has-a-new-home.md
@@ -19,7 +19,7 @@ Since March 13th, 2020, VTEX IO and VTEX IO Store Framework documentation is no
 
 The documentation can be accessed in [**VTEX IO Docs**](https://vtex.io/docs), our documentation platform where all content related to both solutions is available. 
 
-![vtex-io-docs](//images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/a78b3e5600bc5b7c1dcefcaa5da40fb6/vtex-io-docs.png)
+![vtex-io-docs](https://images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/a78b3e5600bc5b7c1dcefcaa5da40fb6/vtex-io-docs.png)
 
 ## Why the change?
 
@@ -33,7 +33,7 @@ The decision to remove VTEX IO and VTEX IO Store Framework documentation from He
 
 Home to our [API documentation](https://developers.vtex.com/reference), [guides](https://developers.vtex.com/docs) aimed at developers working with integrations and customization, and the [Release Notes](https://developers.vtex.com/changelog), which are synced with all the latest updates about our product, the [**Developer Portal**](https://developers.vtex.com) - formerly known as Help Center Developer Docs - offers all the necessary resources for VTEX's most advanced users in a single place. 
 
-![developer-portal](//images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/4c1aa7fcb8d7275e1287d5e03bbe1e80/developer-portal.png)
+![developer-portal](https://images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/4c1aa7fcb8d7275e1287d5e03bbe1e80/developer-portal.png)
 
 Aiming to improve VTEX development experience, the Developer Portal will soon incorporate the VTEX IO and VTEX IO Store Framework documentation - which is available today on VTEX IO Docs.
 
diff --git a/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md b/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md
index 20c078037..e2df97019 100644
--- a/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md
+++ b/docs/announcements/en/vtex-is-now-available-in-dutch-french-and-korean.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'VTEX Admin has three new language options.'
 
 The VTEX admin currently supports different language options to serve our clients all over the world. We localize our product to enhance its overall experience, not only through translations but also on a cultural level, taking into account the particularities of each country.
 
-![EN new locales](//images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/aa4557f81746ab4e3735b07aaf4085a0/EN_new_locales.jpg)
+![EN new locales](https://images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/aa4557f81746ab4e3735b07aaf4085a0/EN_new_locales.jpg)
 
 ## What has changed?
 In addition to Portuguese, English, Spanish, Italian, Romanian and Japanese, starting May 2021, VTEX users will find three new language options in our Admin: Dutch, French and Korean. 
diff --git a/docs/announcements/en/vtex-login-now-features-recaptcha.md b/docs/announcements/en/vtex-login-now-features-recaptcha.md
index 3398e3a5a..73a9634cc 100644
--- a/docs/announcements/en/vtex-login-now-features-recaptcha.md
+++ b/docs/announcements/en/vtex-login-now-features-recaptcha.md
@@ -19,7 +19,7 @@ VTEX login via e-mail and password now features reCAPTCHA, which makes store acc
 
 We use Invisible reCAPTCHA, a Google technology that determines when it's necessary to confirm whether the access attempt is being made by a robot or a human.
 
-![reCAPTCHA](//images.contentful.com/alneenqid6w5/2obeayJZP6k8q8a6W68sQI/08bbf823714965fd207961a792a94f9f/reCAPTCHA.png)
+![reCAPTCHA](https://images.contentful.com/alneenqid6w5/2obeayJZP6k8q8a6W68sQI/08bbf823714965fd207961a792a94f9f/reCAPTCHA.png)
 
 This means that the confirmation request may or may not appear, depending on several variables.
 
diff --git a/docs/announcements/en/vtex-marketplace-launches-in-2022.md b/docs/announcements/en/vtex-marketplace-launches-in-2022.md
index ca074df55..ba5ad79b6 100644
--- a/docs/announcements/en/vtex-marketplace-launches-in-2022.md
+++ b/docs/announcements/en/vtex-marketplace-launches-in-2022.md
@@ -29,7 +29,7 @@ The new features allow marketplaces to:
 
 Go beyond traditional ecommerce with the [VTEX 2022 Marketplace Release](https://content.vtex.com/en/2022-marketplace-release/?utm_source=announcement&utm_medium=organic&utm_campaign=2022_marketplace_release).
 
-![capa de blog marketplace 2022](//images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/9c691ba396bbd1c6fdd0c8d6b53f1b58/capa_de_blog.png)
+![capa de blog marketplace 2022](https://images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/9c691ba396bbd1c6fdd0c8d6b53f1b58/capa_de_blog.png)
 
 ## What are the launches? 
 
@@ -78,7 +78,7 @@ Learn more about each one below.
 
 ### Seller Portal 
 
-![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 The Seller Portal is a VTEX platform edition for [sellers](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402) to connect and sell their products on VTEX marketplaces. The portal allows sellers to access all the key features necessary to operate ecommerce on big storefronts, increasing visibility and sales conversion. 
 
@@ -126,7 +126,7 @@ To facilitate new sellers joining the Seller Portal, we have also launched the [
 
 ### Seller management
 
-![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 We launched the redesigned experience of the [Seller Management](https://help.vtex.com/en/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv) page, where marketplace operators can [add sellers](https://help.vtex.com/en/tutorial/adicionar-seller-beta--6q4G4RNqVENr5YMJyindwL) and their respective information and manage their status. 
 
diff --git a/docs/announcements/en/we-released-the-new-order-placed.md b/docs/announcements/en/we-released-the-new-order-placed.md
index de23e1e42..f7a29b308 100644
--- a/docs/announcements/en/we-released-the-new-order-placed.md
+++ b/docs/announcements/en/we-released-the-new-order-placed.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'The new version of the order confirmation page is now a
 
 Earlier this month we announced the release of one of the many new features that VTEX is developing to further enhance the user experience - the new My Orders section. Today we released another feature that integrates this section: the new version of the Order Placed page.
 
-![RequestConfirmed](// images.contentful.com/alneenqid6w5/2Xr5mMmZMs0WAy4i6cK4EC/50c153cf99a137eb55f0d0dbc34ee820/ConfirmedPosition.png)
+![RequestConfirmed](https:// images.contentful.com/alneenqid6w5/2Xr5mMmZMs0WAy4i6cK4EC/50c153cf99a137eb55f0d0dbc34ee820/ConfirmedPosition.png)
 
 It is now part of __Checkout Confirmation__, feature that's responsible for the Checkout confirmation pages. And it brings important advantages to your store:
 
@@ -29,7 +29,7 @@ Activating this update is simple: just access the Orders tab in your admin's Por
 
 After August 24, 2017, the new version will be activated by default, and the old one will be discontinued. So stay tuned!
 
-![RequestConfirmed2](// images.contentful.com/alneenqid6w5/5xM0PRucykSa84SWWO4k2S/0dcf664d17697bdbf8a32b074578af27/Confirmed2.png)
+![RequestConfirmed2](https:// images.contentful.com/alneenqid6w5/5xM0PRucykSa84SWWO4k2S/0dcf664d17697bdbf8a32b074578af27/Confirmed2.png)
 
 You may want to update your customization. To learn how, see the tutorial [Customize Checkout Confirmation Pages](/en/tutorial/customizing-the-checkout-confirmation-pages).
 
diff --git a/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md
index b2f028220..215defd36 100644
--- a/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/en/welcome-to-the-redesigned-vtex-admin-new.md
@@ -19,7 +19,7 @@ Digital businesses are increasingly looking for tools that can help them grow, w
 
 Welcome to the [redesigned Admin experience](https://content.vtex.com/join-new-admin-beta-program-en/?utm_source=announcement&utm_medium=organic&utm_campaign=new_admin_beta).
 
-![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
 ## What has changed?
 
diff --git a/docs/announcements/en/were-launching-your-personal-data-set-up-screen.md b/docs/announcements/en/were-launching-your-personal-data-set-up-screen.md
index 225f3972d..c61d87bed 100644
--- a/docs/announcements/en/were-launching-your-personal-data-set-up-screen.md
+++ b/docs/announcements/en/were-launching-your-personal-data-set-up-screen.md
@@ -19,7 +19,7 @@ It has become easier to edit your personal VTEX Admin access settings.
 
 VTEX ID team has created the My User screen, which can be easily accessed by the Admin topbar.
 
-![dadosPessoais](//images.contentful.com/alneenqid6w5/3c85FBDbJumIgA0smG4Q2S/2af591bd4d724dadae3adebd7525311b/dadosPessoais.png)
+![dadosPessoais](https://images.contentful.com/alneenqid6w5/3c85FBDbJumIgA0smG4Q2S/2af591bd4d724dadae3adebd7525311b/dadosPessoais.png)
 
 In this screen you can:
 - View your email registered on Admin.
diff --git a/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md b/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md
index 62ee37cc0..cf5be8e54 100644
--- a/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md
+++ b/docs/announcements/en/wishlist-discover-the-new-vtex-app-store-app.md
@@ -24,7 +24,7 @@ The application is available in the [VTEX App Store](https://apps.vtex.com/ "VTE
 - Adding a heart icon next to each product in the product lists and product detail pages;
 - Creating a Wishlist page, where customers can see their favorite items and easily purchase them.
 
-![Wishlist Printscreen](//images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
+![Wishlist Printscreen](https://images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
 
 ## What are the advantages?
 - Makes your store’s shopping experience more complete;
diff --git a/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index bae1d05c4..354383732 100644
--- a/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -21,7 +21,7 @@ From June 25 <sup>th</sup>, 2019, users without access to <code>Checkout</code>
 
 Seeking to ensure greater safety, we created the possibility to limit user access to the **Settings** screen on the Orders Management module, allowing information to be edited by selected users only. 
 
-![2019-06-07 17 24 10-Settings.en](//images.ctfassets.net/alneenqid6w5/6YfxLgI43YD5FwrXu92j2A/aca4f546516816fabd42f25a39450a6d/2019-06-07_17_24_10-Settings.en.png)
+![2019-06-07 17 24 10-Settings.en](https://images.ctfassets.net/alneenqid6w5/6YfxLgI43YD5FwrXu92j2A/aca4f546516816fabd42f25a39450a6d/2019-06-07_17_24_10-Settings.en.png)
 
 ## Main Advantages 
 
@@ -41,7 +41,7 @@ In order to do this, you need to add a product called `Checkout` to the desired
 6. Choose the type of permission you wish to grant: either `Save Order Configuration` if you want to allow the user to edit the **Orders** secction, or `Save OrderForm Configuration` if you want the user to edit the **Cart** section.
 7. Finally, click on **Save**.
 
-![GIT-Checkout.en](//images.ctfassets.net/alneenqid6w5/1stGxj4wiW6Ijfl4f5QFry/481f3c628d303dc72a40db8bbb81a89e/GIT-Checkout.en.gif)
+![GIT-Checkout.en](https://images.ctfassets.net/alneenqid6w5/1stGxj4wiW6Ijfl4f5QFry/481f3c628d303dc72a40db8bbb81a89e/GIT-Checkout.en.gif)
 
 Upon adding this new product to a profile, ensure that the desired users are in fact linked to this profile.
 
diff --git a/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md b/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md
index 743884554..029683f8f 100644
--- a/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md
+++ b/docs/announcements/es/access-googles-pagespeed-insights-in-your-vtex-admin.md
@@ -21,7 +21,7 @@ Con este fin, hemos creado la nueva pantalla [Rendimiento de las páginas web](h
 
 PageSpeed Insights y Lighthouse son herramientas desarrolladas por Google para proporcionar información sobre la experiencia de usuario de una página tanto en dispositivos móviles como de escritorio, ofreciendo sugerencias sobre cómo se puede mejorar esa página. Utilizan las [Métricas web principales de Google](https://web.dev/vitals/#core-web-vitals) para evaluar la experiencia del usuario _online_.
 
-![Web page performance Dash ES](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
+![Web page performance Dash ES](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/admin-disponivel-em-japones.md b/docs/announcements/es/admin-disponivel-em-japones.md
index b12a28ea1..705a4b574 100644
--- a/docs/announcements/es/admin-disponivel-em-japones.md
+++ b/docs/announcements/es/admin-disponivel-em-japones.md
@@ -25,4 +25,4 @@ La [apertura de una oficina en Singapur](https://vtex.com/us-en/press/vtex-opens
 
 ## ¿Qué se necesita hacer?
 Para visualizar el Admin en japonés, basta con seleccionar el código __JP__ en el menú desplegable de idioma situado en la esquina superior derecha de la pantalla. 
-![Seleccionar el código JP ](//images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/7ab7644ee7b02343b7eccaa5dc2e4596/japones.png)
+![Seleccionar el código JP ](https://images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/7ab7644ee7b02343b7eccaa5dc2e4596/japones.png)
diff --git a/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
index 2ee705f62..f38564df5 100644
--- a/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -29,7 +29,7 @@ Ahora, los usuarios sólo verán los ítems del menú de la barra lateral a los
 
 La imagen a continuación ilustra cómo la barra lateral cambiaría al aplicar esta modificación de mantenimiento para mejorar la seguridad y la experiencia de usuario de su tienda.
 
-![ES Sidebar permissions announcement screenshot](//images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/e099126ea9483ee64e156948b6bd1695/ES_Sidebar_permissions_announcement_screenshot__1_.png)
+![ES Sidebar permissions announcement screenshot](https://images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/e099126ea9483ee64e156948b6bd1695/ES_Sidebar_permissions_announcement_screenshot__1_.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md
index ae9387bc5..6b4ca8322 100644
--- a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md
+++ b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization-teste.md
@@ -22,7 +22,7 @@ Una situación común en los restaurantes que aceptan pedidos online, por ejempl
 
 Para simplificar el uso de esta funcionalidad, hemos desarrollado la aplicación **Assembly Options**, que presenta una interfaz para configurar y gestionar las opciones de personalización. La aplicación solo está disponible para las tiendas que utilizan [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app-es](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
+![assembly-options-app-es](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md
index e35f023bf..3d3e8ec2c 100644
--- a/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md
+++ b/docs/announcements/es/assembly-options-new-app-to-simplify-product-customization.md
@@ -22,7 +22,7 @@ Una situación común en los restaurantes que aceptan pedidos online, por ejempl
 
 Para simplificar el uso de esta funcionalidad, hemos desarrollado la aplicación **Assembly Options**, que presenta una interfaz para configurar y gestionar las opciones de personalización. La aplicación solo está disponible para las tiendas que utilizan [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app-es](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
+![assembly-options-app-es](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 6099ce0b0..33bacada6 100644
--- a/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -25,7 +25,7 @@ La solución combina dos funcionalidades y aplicaciones móviles:
 - [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): control de la entrega last-mile.
 - **Aplicaciones móviles:** aplicaciones para entregadores y conductores.
 
-![pick_pack_gif_ES](//images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/c662e643c1ab451f005898166b65b0f7/pick_pack_gif_ES.gif)
+![pick_pack_gif_ES](https://images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/c662e643c1ab451f005898166b65b0f7/pick_pack_gif_ES.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md b/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md
index 7f1fa6e49..d144d9240 100644
--- a/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md
+++ b/docs/announcements/es/campaign-promotions-new-option-when-configuring-target-audience.md
@@ -23,7 +23,7 @@ Mejoramos la configuración de Audiencia de campañas para permitirte sumar púb
 
 En el Admin VTEX, en **Productos > Promociones y Tasas > Audiencia de campañas > Nueva audiencia de campaña**, en las configuraciones referidas al **Público objetivo**, agregamos la opción «y», donde antes solo estaba la opción «o».  Esto significa que ahora puedes aplicar una lógica de adición de criterios («y»), además de la lógica de alternativa («o») que ya existía. Observa la imagen a continuación:
 
-![publico-alvo-e-ou-es](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
+![publico-alvo-e-ou-es](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
 
 Con la nueva opción, puedes crear promociones de campaña a partir de una combinación de criterios de una manera más flexible.
 
diff --git a/docs/announcements/es/catalogs-new-visual-and-navigation.md b/docs/announcements/es/catalogs-new-visual-and-navigation.md
index 5a6d5bbd5..77fe0cfad 100644
--- a/docs/announcements/es/catalogs-new-visual-and-navigation.md
+++ b/docs/announcements/es/catalogs-new-visual-and-navigation.md
@@ -23,16 +23,16 @@ La principal diferencia para la versión antigua está en la navegación. Cambie
 ## Que ha cambiado
 
 La mayoría de los elementos del Catálogo se pueden encontrar en _Catálogo_, que se encuentra en la sección _PRODUCTOS_ del menú lateral.
-![ES-Catálogo1](//images.ctfassets.net/alneenqid6w5/34XVA7oE408IGWg0ksG4qQ/7ac747eed47cc684526edd8a8e860ace/ES-Cat__logo1.png)
+![ES-Catálogo1](https://images.ctfassets.net/alneenqid6w5/34XVA7oE408IGWg0ksG4qQ/7ac747eed47cc684526edd8a8e860ace/ES-Cat__logo1.png)
 
 
 El ítem _Tarjeta de regallo_ (que antes se llamaba _Vales_ y se encontraba en _Controles de campañas_) ahora está en _Pagos_, dentro de la sección _TRANSACCIONES_ del menú lateral.
-![ES-Catálogo2](//images.ctfassets.net/alneenqid6w5/1QZmRnr4Y8M80sSQGywG8i/6b66051ad5a8fe23a79d779faa2dfea4/ES-Cat__logo2.png)
+![ES-Catálogo2](https://images.ctfassets.net/alneenqid6w5/1QZmRnr4Y8M80sSQGywG8i/6b66051ad5a8fe23a79d779faa2dfea4/ES-Cat__logo2.png)
 
 
 El elemento _Configuraciones_ se convirtió en un ítem de _CMS_, que se encuentra en la sección _CONFIGURACIÓN DE LA TIENDA_ del menú lateral.
-![ES-Catálogo3](//images.ctfassets.net/alneenqid6w5/2KMa8ImOCsakEyaGa8yci0/c7f86a05fcb34f14b31771f558b3efe0/ES-Cat__logo3.png)
+![ES-Catálogo3](https://images.ctfassets.net/alneenqid6w5/2KMa8ImOCsakEyaGa8yci0/c7f86a05fcb34f14b31771f558b3efe0/ES-Cat__logo3.png)
 
 
 La pestaña _Marketplace_ ganó una sección propia del mismo nombre en el menú lateral.
-![ES-Catálogo4](//images.ctfassets.net/alneenqid6w5/6bTv54WR4QwaiOKOoiwSIG/f124f5a1bd87d0ce854108658cd52467/ES-Cat__logo4.png)
+![ES-Catálogo4](https://images.ctfassets.net/alneenqid6w5/6bTv54WR4QwaiOKOoiwSIG/f124f5a1bd87d0ce854108658cd52467/ES-Cat__logo4.png)
diff --git a/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md b/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
index 542b9be6d..0d6fbbe3f 100644
--- a/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
+++ b/docs/announcements/es/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
@@ -27,7 +27,7 @@ Tenga la seguridad de que no nos equivocamos. Tras un cuidadoso análisis, nuest
 
 Pero eso no es todo. También renovamos por completo el proceso para cambiar el usuario titular de una cuenta, transformándolo en un flujo de transferencia basado en invitaciones que es totalmente auditable. 
 
-![Gestion titular gif](//images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/0faedf49cfdee92ffdaabbdb3a624b04/Announcement_ES.gif)
+![Gestion titular gif](https://images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/0faedf49cfdee92ffdaabbdb3a624b04/Announcement_ES.gif)
 
 Consulte [Transferir la propiedad de la tienda](https://help.vtex.com/es/tutorial/transferir-la-propiedad-de-la-tienda) para conocer más detalles sobre este nuevo proceso. 
 
diff --git a/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
index 532fe509d..8f133a2a7 100644
--- a/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
@@ -45,7 +45,7 @@ Para comprobar si los proveedores antifraude configurados en tu tienda permiten
 2. En **Pagos**, haz clic en **Configuración > Afiliaciones de gateway**. 
 3. Al seleccionar el proveedor antifraude escogido, comprueba si la opción **Campo de documento del titular de la tarjeta** está disponible en la pantalla de configuración.
 
-![campo de documento del titular de la tarjeta](//images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/d826f02dac101b0385119f52685fb846/campo_de_documento_del_titular_de_la_tarjeta.png)
+![campo de documento del titular de la tarjeta](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/d826f02dac101b0385119f52685fb846/campo_de_documento_del_titular_de_la_tarjeta.png)
 
 <div class = "alert alert-warning">
   Si la opción <b>Campo de documento del titular de la tarjeta</b> no está disponible en la pantalla de configuración de tu proveedor antifraude, el campo <b>Identificación del titular de la tarjeta</b> seguirá apareciendo en la pantalla del Checkout de la tienda y será obligatorio que el cliente lo rellene.
diff --git a/docs/announcements/es/coupon-experience-improvements.md b/docs/announcements/es/coupon-experience-improvements.md
index e4b3fcddb..a1c13cf87 100644
--- a/docs/announcements/es/coupon-experience-improvements.md
+++ b/docs/announcements/es/coupon-experience-improvements.md
@@ -27,7 +27,7 @@ La nueva experiencia de [Cupones](https://help.vtex.com/es/tutorial/cupons-beta-
 
 La nueva [lista de Cupones](https://help.vtex.com/es/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ) muestra todos los cupones registrados en tu tienda, permitiendo gestionar los datos y analizar en qué pedidos se han utilizado.
 
-![listacupons es](//images.ctfassets.net/alneenqid6w5/2BeCmFJ9bya2SOvx7wQHxC/7e1236597924f6ffd9c2f288884631b6/listacupons_es.gif)
+![listacupons es](https://images.ctfassets.net/alneenqid6w5/2BeCmFJ9bya2SOvx7wQHxC/7e1236597924f6ffd9c2f288884631b6/listacupons_es.gif)
 
 ### Acceso más fácil a los códigos de los cupones
 
@@ -44,7 +44,7 @@ Los nuevos filtros permiten la visualización de aquellos cupones que cumplen cr
 - Última modificación
 - Tipo de cupón
 
-![filtroscupons es](//images.ctfassets.net/alneenqid6w5/5wiejFZZWnKU6ASUP3yk74/6474e893083a2db3a9cfb525b463162d/filtroscupons_es.gif)
+![filtroscupons es](https://images.ctfassets.net/alneenqid6w5/5wiejFZZWnKU6ASUP3yk74/6474e893083a2db3a9cfb525b463162d/filtroscupons_es.gif)
 
 ### Grupos de cupones para una gestión ágil
 
diff --git a/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md b/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md
index f372691d3..4be7de4ee 100644
--- a/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md
+++ b/docs/announcements/es/customize-your-payment-conditions-with-the-new-card-level-functionality.md
@@ -38,6 +38,6 @@ La configuración es similar al de las demás condiciones especiales de pago.
 
 La principal diferencia es que, después de seleccionar el país y el banco emisor, el administrador de la tienda puede elegir entre las opciones de Card Level que ofrece  la institución financiera elegida.
 
-![comousarcardlevelES.gif?h=250](//images.ctfassets.net/alneenqid6w5/7GeRvL3w0PW2czAGdnQWRw/e7ed1290e19aea854cb4dda72f501b26/comousarcardlevelES.gif_h_250)
+![comousarcardlevelES.gif?h=250](https://images.ctfassets.net/alneenqid6w5/7GeRvL3w0PW2czAGdnQWRw/e7ed1290e19aea854cb4dda72f501b26/comousarcardlevelES.gif_h_250)
 
 Para saber en detalle cómo configurar esta funcionalidad, vea nuestro [artículo sobre Configuración de Condiciones Especiales de Pago](https://help.vtex.com/tutorial/condiciones-especiales--tutorials_456).
diff --git a/docs/announcements/es/displaying-pickup-points-on-google-maps.md b/docs/announcements/es/displaying-pickup-points-on-google-maps.md
index bb2a24557..884d668a0 100644
--- a/docs/announcements/es/displaying-pickup-points-on-google-maps.md
+++ b/docs/announcements/es/displaying-pickup-points-on-google-maps.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Aplicación que lista los Puntos de Recogida y los mues
 
 Una de las funcionalidades más comunes de los sitios web y de las tiendas en línea es poner a disposición mapas que señalan la ubicación de las tiendas físicas. Con la nueva aplicación [Store Locator](https://apps.vtex.com/vtex-store-locator/p#overview), las tiendas desarrolladas con VTEX IO pueden utilizar Google Maps para listar los puntos de recogida registrados en la tienda y mostrarlos como marcadores en un mapa.
 
-![Maps](//images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
+![Maps](https://images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
 
 ## ¿Qué cambió?
 Las tiendas desarrolladas con VTEX IO ahora pueden instalar la aplicación Store Locator y mostrar los puntos de recogida como marcadores en Google Maps.
diff --git a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md
index 2472589cb..2a051f85d 100644
--- a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md
+++ b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'El resumen de la promoción permite revisar su informac
 
 Es posible que se cometan errores al rellenar la información en el momento de configurar una nueva promoción. Para evitar que se activen promociones con información incorrecta, hemos creado el resumen de la promoción. Esta nueva funcionalidad te permite confirmar la configuración de la promoción antes de activarla.
 
-![resumo-promo-ES](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
+![resumo-promo-ES](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
 
 ## ¿Qué cambió?
 Anteriormente, una promoción se activaba automáticamente cuando se guardaba con el status **Activa**. Con el nuevo recurso, puedes ver un resumen de las configuraciones definidas antes de activar una nueva promoción. De este modo, es posible revisar si todos los datos de la promoción son correctos, evitando errores de implementación.
diff --git a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
index e5afe405f..eef88f042 100644
--- a/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
+++ b/docs/announcements/es/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'El resumen de la promoción permite revisar su informac
 
 Es posible que se cometan errores al rellenar la información en el momento de configurar una nueva promoción. Para evitar que se activen promociones con información incorrecta, hemos creado el resumen de la promoción. Esta nueva funcionalidad te permite confirmar la configuración de la promoción antes de activarla.
 
-![resumo-promo-ES](//images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
+![resumo-promo-ES](https://images.ctfassets.net/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/ec043089cafef418ee0def411242c940/image.png)
 
 ## ¿Qué cambió?
 Anteriormente, una promoción se activaba automáticamente cuando se guardaba con el status **Activa**. Con el nuevo recurso, puedes ver un resumen de las configuraciones definidas antes de activar una nueva promoción. De este modo, es posible revisar si todos los datos de la promoción son correctos, evitando errores de implementación.
diff --git a/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 1d5cda1d9..c232b4bb4 100644
--- a/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -25,7 +25,7 @@ La aplicación está disponible en [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Permite moderar las calificaciones: apruebe las calificaciones de los productos antes de que estén disponibles en la página de producto.
 - Permite que usted configure su tienda para habilitar las calificaciones anónimas.
 
-![Reviews and Ratings - Printscreen](//images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
+![Reviews and Ratings - Printscreen](https://images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
 
 ## ¿Cuáles son los beneficios?
 - Permite que su consumidor compre con más confianza y asertividad basándose en las calificaciones de otros usuarios.
diff --git a/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 0e6858b92..1673e18a9 100644
--- a/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -38,6 +38,6 @@ Para hacer esto es necesario añadir un producto llamado `Order Authorization` a
  6. Elija el tipo de permiso que desea: `Save Configuration`, para permitir al usuario editar y guardar modificaciones, o `View Configuration`, para permitirle la visualización de la página de Autorización de Pedidos.
  7. Haga clic en **Guardar**.
 
-![GIT-OrderAutho.es](//images.ctfassets.net/alneenqid6w5/405FxMK69Z6aRClIKAqcqb/6879d0b48f435ed7dcc212cd239c62fe/GIT-OrderAutho.es.gif)
+![GIT-OrderAutho.es](https://images.ctfassets.net/alneenqid6w5/405FxMK69Z6aRClIKAqcqb/6879d0b48f435ed7dcc212cd239c62fe/GIT-OrderAutho.es.gif)
 
 Después de añadir este nuevo producto a un perfil, asegúrese de que los usuarios deseados están asociados a este perfil de acceso.
diff --git a/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
index 32fe90f5d..43cda1f7c 100644
--- a/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'La nueva sección del Admin VTEX para encontrar partner
 
 El Hub de extensiones es la nueva sección del Admin VTEX que reúne a desarrolladores, partners y administradores de las tiendas que desean ampliar las funcionalidades de su operación. A través del Hub de extensiones los partners pueden publicar sus extensiones y los administradores de las tiendas pueden verlas, comprarlas, instalarlas y gestionarlas. El Hub de extensiones estará disponible globalmente en todas las tiendas VTEX durante el tercer trimestre de 2023. Si deseas habilitar el Hub de extensiones en tu tienda de forma inmediata, puedes hacer la solicitud [abriendo un ticket con soporte](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-![Extensions Hub GIF](//images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/ebae6d6f5ef33a29f0037730c2a64cea/Extensions_Hub.gif)
+![Extensions Hub GIF](https://images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/ebae6d6f5ef33a29f0037730c2a64cea/Extensions_Hub.gif)
 
 ## ¿Qué cambió?
 
@@ -49,7 +49,7 @@ El [sitio web Partner portal](https://partnerportal.vtex.com/) continuará exist
 
 El Hub de extensiones estará disponible para todas las tiendas a partir del tercer trimestre de 2023. Si deseas habilitar el Hub de extensiones en tu tienda de forma inmediata, puedes realizar la solicitud [abriendo un ticket a nuestro equipo de soporte](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM). A continuación, para empezar a utilizar el Hub de extensiones, solo tendrás que acceder a través del Admin de tu tienda. En el panel lateral izquierdo del Admin VTEX, haz clic en el ícono **Extensiones** y el Hub de extensiones estará visible en la parte superior del menú.
 
-![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
+![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/facebook-and-google-login-settings-have-changed.md b/docs/announcements/es/facebook-and-google-login-settings-have-changed.md
index 475022474..0ee0d89be 100644
--- a/docs/announcements/es/facebook-and-google-login-settings-have-changed.md
+++ b/docs/announcements/es/facebook-and-google-login-settings-have-changed.md
@@ -21,6 +21,6 @@ La flag __Usar claves VTEX__, que antes activaba el uso de datos proporcionados
 
 Esto significa que el flujo se ha corregido y ya no es posible utilizar las claves de VTEX para iniciar sesión con Facebook y Google. Ahora la tienda necesita configurar sus propias llaves.
 
-![login2](//images.contentful.com/alneenqid6w5/8ctzWCGmeAuay68eyk888/630cfc3d79ef248f06ca47575556738c/login2.png)
+![login2](https://images.contentful.com/alneenqid6w5/8ctzWCGmeAuay68eyk888/630cfc3d79ef248f06ca47575556738c/login2.png)
 
 Este cambio no tiene ningún impacto negativo en el almacén. Sin embargo, si alguna personalización se ha cometido incorrectamente en su pantalla de login, se pueden producir accidentes. Entonces verifique su pantalla de login para asegurarse de que todo sigue bien.
diff --git a/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
index a426afc88..5cab46f1a 100644
--- a/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
+++ b/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'FastCheckout: innovación en el checkout para experienc
 
 Con el compromiso continuo de innovar y ofrecer calidad de excelencia a nuestros clientes, VTEX presenta **FastCheckout**, la evolución más reciente de nuestro checkout. La nueva solución permite crear experiencias de checkout personalizadas de alta conversión, que siempre están actualizadas con nuevas funcionalidades.
 
-![fastcheckout](//images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/14df7a3c5d09bdf75b288dd352763515/image.png)
+![fastcheckout](https://images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/14df7a3c5d09bdf75b288dd352763515/image.png)
 
 ## ¿Qué cambió?
 
@@ -56,7 +56,7 @@ También es posible incluir elementos completamente personalizados sin necesidad
 
 El nuevo flujo de compra de FastCheckout está diseñado para ser dinámico e intuitivo y ofrecer a tus clientes una experiencia de compra más ágil y simplificada. Los pasos claramente definidos y la navegación intuitiva hacen que el proceso de checkout sea más eficaz.
 
-![GIFCheckout](//images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/4196b4d4a12b04c1561ebe01b4db5323/GIFCheckout.gif)
+![GIFCheckout](https://images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/4196b4d4a12b04c1561ebe01b4db5323/GIFCheckout.gif)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md b/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md
index 12307eab0..096cd55b4 100644
--- a/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md
+++ b/docs/announcements/es/gain-speed-and-practicality-with-the-updated-price-table-feature.md
@@ -21,7 +21,7 @@ Ahora es posible crear Tablas de Precios de una manera más intuitiva, práctica
 
 Antes, para crear una tabla de precios era necesario ir hasta el filtro y digitar el nombre de la tabla que se crearía. Ahora, hemos añadido un nuevo campo Tablas de Precios que permite crear y seleccionar la tabla que desea visualizar y trabajar con los precios.
 
-![Annoucement Price Table ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6ORyt5Phgwt65ORLPJbGtU/40e250956718b901dcea414b9e759294/Annoucement_Price_Table_ES.png_h_250)
+![Annoucement Price Table ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6ORyt5Phgwt65ORLPJbGtU/40e250956718b901dcea414b9e759294/Annoucement_Price_Table_ES.png_h_250)
 
 ## Ventajas
 
diff --git a/docs/announcements/es/get-to-know-the-new-vtex-status-page.md b/docs/announcements/es/get-to-know-the-new-vtex-status-page.md
index 1d1508b97..2c280f1e1 100644
--- a/docs/announcements/es/get-to-know-the-new-vtex-status-page.md
+++ b/docs/announcements/es/get-to-know-the-new-vtex-status-page.md
@@ -23,7 +23,7 @@ Antes, enfrentábamos dificultades a la hora de categorizar los incidentes en so
 
 Ahora, tenemos 18 componentes más específicos agrupados en cuatro categorías: Storefront, Checkout, Admin y Developer Tools, enfocados no solo en nuestra arquitectura interna, sino también los puntos donde los retailers pueden observar los síntomas. La siguiente imagen muestra todos los componentes que se incluyen en la nueva página:
 
-![status-page-vtex](//images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/83a6e336c064817e69ed39e85fb83a96/status-page-vtex.png)
+![status-page-vtex](https://images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/83a6e336c064817e69ed39e85fb83a96/status-page-vtex.png)
 
 Consulta el artículo [Página VTEX Status](https://help.vtex.com/es/tutorial/pagina-vtex-status--gPhqDn9IQ3c67wbJEX3JJ), para más información sobre cada componente.
 
diff --git a/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md b/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
index a7beffbda..a14342aac 100644
--- a/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
+++ b/docs/announcements/es/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
@@ -21,4 +21,4 @@ Como hacemos todos los años, hemos creado una guía con recomendaciones y conse
 
 Disponible para clientes y socios VTEX, usted puede acceder a la guía por la homepage del Admin o directamente por la URL `https://{AccountName}.myvtex.com/admin/blackfriday`. Sólo hay que sustituir `{AccountName}` por el Account Name de su tienda.
 
-![Announcement Cartilha BF - ES](//images.ctfassets.net/alneenqid6w5/1RSlbXUdcYiAUQSi6S226w/325d5511f9fea08746aa5362ec65a814/Announcement_Cartilha_BF_-_ES.png)
+![Announcement Cartilha BF - ES](https://images.ctfassets.net/alneenqid6w5/1RSlbXUdcYiAUQSi6S226w/325d5511f9fea08746aa5362ec65a814/Announcement_Cartilha_BF_-_ES.png)
diff --git a/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md b/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
index 16982c8d7..5398d27e1 100644
--- a/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
+++ b/docs/announcements/es/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
@@ -27,4 +27,4 @@ https://{AccountName}.myvtex.com/admin/shopping-season
 
 Sólo hay que sustituir `{AccountName}` por el Account Name de su tienda, como en la imagen de abajo.
 
-![Shopping Season Guidelines - 2022 - ES](//images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/f364db4afdea7487e01325f9c455cdcf/Screen_Shot_2022-10-19_at_18.15.02.png)
+![Shopping Season Guidelines - 2022 - ES](https://images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/f364db4afdea7487e01325f9c455cdcf/Screen_Shot_2022-10-19_at_18.15.02.png)
diff --git a/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md b/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md
index 3969102a8..7f5a38a9c 100644
--- a/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md
+++ b/docs/announcements/es/google-pay-new-payment-method-available-on-vtex.md
@@ -27,7 +27,7 @@ Google Pay es una plataforma de cartera digital y un sistema de pagos online des
 
 Ahora, puedes agregar Google Pay como medio de pago en tu tienda para proporcionar a tus clientes un proceso de checkout más ágil y conveniente.
 
-![google-pay-checkout-es](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/35be7ad3c5e155d0af64fdf42611cc9d/image.png)
+![google-pay-checkout-es](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/35be7ad3c5e155d0af64fdf42611cc9d/image.png)
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/google-shopping-new-option-to-submit-prices.md b/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
index 1f9c1600b..162c3a8c3 100644
--- a/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
+++ b/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
@@ -27,14 +27,14 @@ Antes, el registro de la [integración con Google Shopping](https://help.vtex.co
   La configuración <b>Aplicar descuento al precio enviado</b> solo está disponible para tiendas VTEX en Brasil.
 </div>
 
-![envio-de-precos-google-es](//images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/afc4f30ca92f564cb47326e9956b21df/envio-de-precos-google-es.png)
+![envio-de-precos-google-es](https://images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/afc4f30ca92f564cb47326e9956b21df/envio-de-precos-google-es.png)
 
 ## ¿Qué se necesita hacer?
 
 La actualización estará disponible para todas las [cuentas VTEX que operan como seller](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) a partir del 14 de diciembre de 2023.
 Las cuentas que aún no utilizan la integración con Google Shopping y desean activar la configuración __Enviar precio base (para precios con descuento)__ y __Aplicar descuento al precio enviado__, deben seguir [esta serie de tutoriales](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) para comenzar a utilizar los nuevos ajustes. Las cuentas que ya estén integradas con Google Shopping y tienen la configurada la opción __Considerar descuento para pago con boleto en el precio enviado__ activa, tendrán la opción __Aplicar descuento al precio enviado__ activa después de que se realice la actualización según se muestra en la imagen a continuación:
 
- ![fluxo-update-news-google-es](//images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/4c8dc610fc35a1ab2dc5d2c820f7fea4/fluxo-update-news-google-es.png)
+ ![fluxo-update-news-google-es](https://images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/4c8dc610fc35a1ab2dc5d2c820f7fea4/fluxo-update-news-google-es.png)
 
 Consulta la documentación para más información sobre cómo configurar [un descuento vinculado al medio de pago](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/3AqbcsWrge8zLt0BC5CtGd#desconto-vinculado-ao-metodo-de-pagamento) y [un descuento en el conector](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
 
diff --git a/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md b/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md
index b69fcbc7e..36f60ed18 100644
--- a/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md
+++ b/docs/announcements/es/headless-cms-create-non-duplicatable-pages.md
@@ -16,7 +16,7 @@ announcementSynopsisES: 'Singleton: el tipo de content type en Headless CMS que
 ---
 
 Singleton es un nuevo tipo de content type que permite que el comerciante (administrador de la tienda) pueda crear y gestionar una única página de un content type en el Headless CMS. Los content types de Singleton no pueden duplicarse, lo que garantiza que solo haya una página de ese tipo de contenido y que sea coherente en toda la tienda.
-![singleton-es](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
+![singleton-es](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 El content type Singleton solo está disponible para tiendas que utilicen <a href="https://help.vtex.com/es/tutorial/managing-pages-beta--3DO6rBhZ1p3zndnFu5BgRt">VTEX Headless CMS</a> (Actualmente se encuentra en fase beta).
diff --git a/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md b/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md
index da063b13c..dc96489cf 100644
--- a/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md
+++ b/docs/announcements/es/headless-cms-deeper-insights-into-page-publication-status.md
@@ -19,7 +19,7 @@ A partir del 1 de noviembre de 2023, se descontinuará el estado **Publicando**
 
 Cuando se crea una nueva página, inicialmente se muestra como **Borrador** en la columna Versiones, lo que indica que aún no se hizo deploy de la página. Una vez que el deploy se ha realizado, el status se actualiza a **Publicado**, lo que significa que el proceso de compilación está listo para comenzar. Una vez completado este proceso, la página pasa a estar disponible para los usuarios finales.
 
-![Build Status - ES](//images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/bab768f8fd499965a4836002ae1bdd6b/publishing-status-es.gif)
+![Build Status - ES](https://images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/bab768f8fd499965a4836002ae1bdd6b/publishing-status-es.gif)
 
 ## ## ¿Qué cambió?
 El status *Publicando* se utilizaba anteriormente para describir el proceso de deploy de una página CMS en FastStore. Sin embargo, no proporcionaba más detalles sobre el proceso.
diff --git a/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md b/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md
index e76feb1a0..9f2524709 100644
--- a/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md
+++ b/docs/announcements/es/headless-cms-simplify-content-creation-and-management-with-projects.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Headless CMS - Administre sus proyectos de manera centr
 
 **Proyectos** es una nueva funcionalidad en Headless CMS que agiliza la gestión de múltiples experiencias digitales, tales como aplicaciones móviles, sitios web y email marketing desde un solo dashboard.
 
-![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/fa66fd00d9a29e3eeb835369c70277d7/projects-two-es-outro.png)
+![Projects overview](https://images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/fa66fd00d9a29e3eeb835369c70277d7/projects-two-es-outro.png)
 
 Proyectos te permite personalizar la configuración, contenido y marca de cada proyecto para ajustarlo a públicos u objetivos específicos.
 
@@ -27,7 +27,7 @@ Antes, para gestionar diferentes proyectos con distintos públicos o soluciones,
 
 Ahora, la interfaz **Proyectos** te permite gestionar todos tus proyectos desde un único dashboard centralizado, desde donde puedes cambiar fácilmente de un proyecto a otro para ajustar la configuración, contenido e identidad desde un solo lugar. Esta mejora le aporta adaptabilidad a tu operación y te brinda la oportunidad de atender públicos y objetivos distintos.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md b/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md
index 571b10345..d79da3444 100644
--- a/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md
+++ b/docs/announcements/es/headless-cms-stay-informed-on-your-publication-progress.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Mantente informado sobre las etapas de publicación de
 
 Headless CMS ofrece ahora una funcionalidad de notificaciones que te mantiene informado durante cada etapa del proceso de publicación. Las nuevas notificaciones proporcionan actualizaciones sobre cada etapa de las publicaciones en el VTEX Headless CMS, manteniendo a los usuarios informados acerca de las fases de compilación (build) de las publicaciones en Releases, VTEX Headless CMS y FastStore. 
 
-![Headless CMS - Notificaciones](//images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/1da7e60b1ebb7b74b67140a0832581a4/headless-cms-publish-es.gif)
+![Headless CMS - Notificaciones](https://images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/1da7e60b1ebb7b74b67140a0832581a4/headless-cms-publish-es.gif)
 
 Esta funcionalidad también te ayuda a identificar y notificar errores durante el deploy, indicando la etapa exacta en la que se produjo el error. También ofrece la opción de reintentar los deploys si es necesario.
 
@@ -35,7 +35,7 @@ Con la funcionalidad de notificaciones, ahora puedes mantenerte informado sobre
 
 Si se produce un error durante el deploy, el mensaje de la notificación indicará en qué etapa ocurrió. Puedes hacer clic en `Reintentar` para repetir el deploy.
 
-![Headless CMS - Novo deploy](//images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/5f9ba3184bd15234a1a4a0d4a09a78c3/headless-cms-redeploy-es.gif)
+![Headless CMS - Novo deploy](https://images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/5f9ba3184bd15234a1a4a0d4a09a78c3/headless-cms-redeploy-es.gif)
 
 ## ¿Por qué realizamos este cambio?
 La funcionalidad de notificaciones te da más autonomía para comprender y abordar los problemas relacionados con las publicaciones de tu tienda, permitiendo identificar e informar con precisión los problemas y reintentar el proceso de publicación.
diff --git a/docs/announcements/es/improvement-of-discount-price-viewing-experience.md b/docs/announcements/es/improvement-of-discount-price-viewing-experience.md
index 8629806e4..1655007d7 100644
--- a/docs/announcements/es/improvement-of-discount-price-viewing-experience.md
+++ b/docs/announcements/es/improvement-of-discount-price-viewing-experience.md
@@ -24,16 +24,16 @@ Antes de este cambio, podían producirse errores de visualización en el resumen
 Considere, por ejemplo, un usuario que ve un producto que cuesta  US$ 600, con un descuento del 10% pagando al contado. La persona continúa para el checkout y llega a la página de resumen del pedido, donde debe seleccionar las opciones de pago. Estos son los tres principales errores que pueden producirse:
 
 - El usuario aún no ha seleccionado un número de cuotas y el precio se muestra sin descuentos, incluso en la opción elegible.
-![O usuário ainda não selecionou um número de parcelas](//images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
+![O usuário ainda não selecionou um número de parcelas](https://images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
 
 - El cliente ha seleccionado un número de cuotas no elegibles para el descuento, y el precio se muestra solo sin descuentos, incluso en la opción elegible para el descuento.
-![O usuário selecionou um número de parcelas não elegível para desconto](//images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
+![O usuário selecionou um número de parcelas não elegível para desconto](https://images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
 
 - El usuario seleccionó un número de cuotas válido para aplicar el descuento y el descuento se muestra incluso en las opciones no elegibles.
-![O usuário selecionou um número de parcelas elegível para desconto (à vista)](//images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
+![O usuário selecionou um número de parcelas elegível para desconto (à vista)](https://images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
 
 Con este cambio, el descuento se mostrará siempre solo en las opciones de pago en cuotas  elegibles.
-![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](//images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
+![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](https://images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
 
 ## ¿Por qué realizamos este cambio?  
 
diff --git a/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md b/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md
index b7bbab219..b5f2a2685 100644
--- a/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md
+++ b/docs/announcements/es/improvements-in-exporting-prices-via-spreadsheet.md
@@ -25,7 +25,7 @@ En VTEX, puedes cambiar el precio varias veces al día según la estrategia de t
 
 El registro con una plantilla se realiza en dos etapas: exportación e importación. Se ha mejorado la experiencia de exportación de precios con nuevas funcionalidades para dar más visibilidad al usuario del status de cada plantilla de exportación de precios.
 
-![exportacao es](//images.ctfassets.net/alneenqid6w5/2w6DG43n73r48D3pM6OmXa/0f70f35ceb6f562f16f40346e4e046cb/exportacao_es.gif)
+![exportacao es](https://images.ctfassets.net/alneenqid6w5/2w6DG43n73r48D3pM6OmXa/0f70f35ceb6f562f16f40346e4e046cb/exportacao_es.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md b/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md
index 56a1d90cf..1c089d66a 100644
--- a/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md
+++ b/docs/announcements/es/improvements-to-unified-search-in-vtex-sales-app.md
@@ -33,7 +33,7 @@ Los cambios optimizan la experiencia de búsqueda y compra:
 
 - **Optimización para conexiones lentas:** gracias al uso de la caché del navegador, la búsqueda solo devolverá nueva información cuando sea necesario, garantizando una respuesta rápida aun cuando la conexión de internet esté lenta.
 
-![Mobile - ES](//images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/095d38f345e181216351f7560a65d914/mobile__1_.gif)
+![Mobile - ES](https://images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/095d38f345e181216351f7560a65d914/mobile__1_.gif)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md b/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md
index eda387408..f44814875 100644
--- a/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md
+++ b/docs/announcements/es/increase-your-sales-with-a-new-order-authorization-screen.md
@@ -22,7 +22,7 @@ Esta herramienta permite el control de las aprobaciones de pedidos con cambios e
 ## Lo que cambia
 Ahora, en lugar de abrir un ticket directamente con el soporte, es posible configurar las reglas de autorización por el administrador. Para ello, acceda al camino: Menú - Gestión de Pedidos - Autorización de Pedidos.
 
-![ESAutorizacaoPedidosPrint.PNG?h=250](//images.ctfassets.net/alneenqid6w5/445WPSN6h0ELYf07ZlPg0M/e0fd3a929af7ed9b1c23f03826e43271/ESAutorizacaoPedidosPrint.PNG_h_250)
+![ESAutorizacaoPedidosPrint.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/445WPSN6h0ELYf07ZlPg0M/e0fd3a929af7ed9b1c23f03826e43271/ESAutorizacaoPedidosPrint.PNG_h_250)
 
 ## Qué necesitas hacer
 Es importante mencionar que la tienda no perderá las reglas anteriores, que se hicieron abriendo un ticket al equipo de soporte. Se actualizarán automáticamente en la nueva pantalla.
diff --git a/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
index 590b937ac..465183b69 100644
--- a/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
@@ -19,7 +19,7 @@ A partir del 31 de mayo, estamos lanzando para todas las tiendas VTEX la versió
 
 Las páginas de la **Estrategia de envío** fueran actualizadas al nuevo _VTEX design system_, como se puede ver a continuación:
 
-![nova_estrategia_envio_announcement_boards_ES](//images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/6ec635cd52cd33a2845fed3d1b444ba6/nova_estrategia_envio_announcement_boards_ES.png)
+![nova_estrategia_envio_announcement_boards_ES](https://images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/6ec635cd52cd33a2845fed3d1b444ba6/nova_estrategia_envio_announcement_boards_ES.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md b/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
index 54578577e..c6f0b7231 100644
--- a/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
+++ b/docs/announcements/es/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
@@ -28,4 +28,4 @@ Al intentar acceder al Admin de una tienda utilizando una dirección de correo e
 
 La seguridad es una de las principales preocupaciones de VTEX, y esto se vuelve aún más importante cuando estamos cerca de grandes eventos como el Black Friday. Esta nueva función ayudará a identificar de donde provienen posibles intentos de acceso no deseados.
 
-![IP Geolocation email - ES](//images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/7d95bdb689d5af09718c80c7ba077b95/IP_Geolocation_email_-_ES.png)
+![IP Geolocation email - ES](https://images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/7d95bdb689d5af09718c80c7ba077b95/IP_Geolocation_email_-_ES.png)
diff --git a/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
index abdaca421..072d8dcc1 100644
--- a/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
+++ b/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Lanzamiento global del lead time, una configuración op
 
 VTEX ha puesto a disposición de todas las tiendas el [lead time](https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B), una configuración del tiempo de envío de un SKU en un determinado stock. En otras palabras, puedes definir a nivel de SKU un tiempo de envío adicional en el cálculo de las promesas de envío que se muestran a los clientes en el checkout.
 
-![lead_time_image_total_time_ES](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
+![lead_time_image_total_time_ES](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
 
 El uso del lead time es opcional y, cuando no se configura, el envío de pedidos de la tienda permanece sin cambios. Cabe señalar que las reglas de consolidación del checkout, que calculan el plazo de envío total del pedido tomando en consideración el tiempo más largo de uno de los ítems, se mantienen.
 
@@ -31,7 +31,7 @@ Antes, el [cálculo del envío de pedidos](https://help.vtex.com/es/tutorial/com
 
 Ahora, también existe la opción de configurar el tiempo de envío a nivel de SKU, con la nueva columna de lead time en la página [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-inventario--tutorials_139), a la que puedes acceder a través del Admin VTEX > **Catálogo > Stock > Gestión del stock**, como se muestra en la imagen a continuación:
 
-![lead_time_inventory_management_ES](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
+![lead_time_inventory_management_ES](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
 
 <div class="alert alert-warning">
 En el Admin VTEX, el lead time se configura en días, hasta un límite de 365. De manera predeterminada, el contaje se realiza en días laborables, pero puedes configurar tu política de envío para se <a href="https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional">realice en días naturales</a>. Para configurar periodos en horas, minutos y segundos debes utilizar el endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
diff --git a/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md b/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md
index e3ad15707..79e85f00d 100644
--- a/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md
+++ b/docs/announcements/es/live-shopping-the-vtex-app-to-broadcast-live-events.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'La aplicación permite a las tiendas transmitir en vivo
 
 La aplicación Live Shopping es responsable por revolucionar su relación con los consumidores: utilícela para realizar transmisiones en vivo en el sitio web de su tienda para promover colecciones de productos, aumentar los índices de venta y mejorar la experiencia de los usuarios de forma simultánea y en tiempo real.
 
-![live-shopping-overviewes](//images.ctfassets.net/alneenqid6w5/6QNneCank2FRHN1M5pZVF1/db72cb142151c3a0745d07c8025ced0c/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
+![live-shopping-overviewes](https://images.ctfassets.net/alneenqid6w5/6QNneCank2FRHN1M5pZVF1/db72cb142151c3a0745d07c8025ced0c/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
 
 La aplicación está disponible en la [VTEX App Store](https://apps.vtex.com/) y todas las tiendas que utilicen VTEX IO y Legado la pueden descargar por un precio de suscripción razonable.
 
@@ -42,7 +42,7 @@ Los controles en el Admin le permiten:
 - establecer una lista de palabras prohibidas que serán bloqueadas en el chat en tiempo real;
 - proponer encuestas y pruebas a sus usuarios.
 
-![live-shopping-event-details-es](//images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/d6c04ae630f2d812789410ad5e2fe2a7/image4.png)
+![live-shopping-event-details-es](https://images.ctfassets.net/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/d6c04ae630f2d812789410ad5e2fe2a7/image4.png)
 
 ## ¿Cuáles son las ventajas?
 
diff --git a/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
index 776d5af38..3bee9311e 100644
--- a/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
+++ b/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -25,7 +25,7 @@ De ahora en adelante, se aplicará el algoritmo de Luhn para garantizar que solo
 
 Si el cliente ingresa un número incorrecto, se mostrará un mensaje de error en el checkout. En ese caso, el cliente deberá comprobar el número ingresado y corregirlo para continuar con la finalización de la compra.
 
-![algoritmo_luhn_es](//images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/b061baadc25eb3b451af06004a05a9d9/algoritmo_luhn_es.PNG)
+![algoritmo_luhn_es](https://images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/b061baadc25eb3b451af06004a05a9d9/algoritmo_luhn_es.PNG)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/marketplace-improvements-on-received-skus.md b/docs/announcements/es/marketplace-improvements-on-received-skus.md
index 32563e7f6..ce267c7b2 100644
--- a/docs/announcements/es/marketplace-improvements-on-received-skus.md
+++ b/docs/announcements/es/marketplace-improvements-on-received-skus.md
@@ -29,7 +29,7 @@ No se requiere ninguna configuración para activar esta funcionalidad, se instal
 
 Cabe señalar que esta acción puede ser deshecha. Es posible aprobar un SKU por API REST, si el marketplace quiere recibirlo de nuevo como una sugerencia del seller. Para obtener más información sobre la aprobación de SKUs, acceda a nuestra documentación de API en el Portal del Desarrollador.
 
-![ES SKUs Recebidos Announcement](//images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/d4b04317dc8e786079db0c7fe8127a4a/ES_SKUs_Recebidos_Announcement.jpg)
+![ES SKUs Recebidos Announcement](https://images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/d4b04317dc8e786079db0c7fe8127a4a/ES_SKUs_Recebidos_Announcement.jpg)
 
 ## Configuración de aprobación automática de SKUs
 
diff --git a/docs/announcements/es/marketplace-network-has-been-improved.md b/docs/announcements/es/marketplace-network-has-been-improved.md
index eb372458c..4301d7340 100644
--- a/docs/announcements/es/marketplace-network-has-been-improved.md
+++ b/docs/announcements/es/marketplace-network-has-been-improved.md
@@ -19,7 +19,7 @@ Uno de los desafíos de los *marketplaces* y *sellers* de nuestro ecosistema es
 
 Hemos rediseñado Marketplace Network para mejorar la experiencia. Además, ya no es necesario descargar la aplicación desde nuestra App Store, se añadió la funcionalidad a todas las tiendas que operan como *sellers* o *marketplaces* de forma automática.
 
-![Marketplace network tour ES](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/27c4fdcd812b730a445b022c7232a5f2/Marketplace_network_tour_ES.gif)
+![Marketplace network tour ES](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/27c4fdcd812b730a445b022c7232a5f2/Marketplace_network_tour_ES.gif)
 
 ## ¿Qué cambió?
 Se hicieron algunos cambios a las páginas de Marketplace Network:
diff --git a/docs/announcements/es/marketplace-new-offer-quality-filters.md b/docs/announcements/es/marketplace-new-offer-quality-filters.md
index 9498dddbc..adb8a627a 100644
--- a/docs/announcements/es/marketplace-new-offer-quality-filters.md
+++ b/docs/announcements/es/marketplace-new-offer-quality-filters.md
@@ -21,7 +21,7 @@ Para que los _marketplaces_ tengan más control sobre los criterios de aprobaci
 
 De esta forma, los SKU que se envían al _marketplace_ cumplen los requisitos relevantes para la curación de catálogos. 
 
-![Offer Quality gif](//images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/5525f637d51f9d9fc5fe29395f58d07f/Offer_Quality_01.gif)
+![Offer Quality gif](https://images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/5525f637d51f9d9fc5fe29395f58d07f/Offer_Quality_01.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md b/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md
index d12e070d6..e0b69d2c6 100644
--- a/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md
+++ b/docs/announcements/es/marketplace-new-sidebar-with-received-sku-details.md
@@ -24,7 +24,7 @@ Antes, para comprobar la información de un SKU recibido, era necesario acceder
 
 La barra contiene imágenes del SKU, precio, nivel de stock y otros atributos del producto, como descripción, especificaciones, códigos e ID. También incluye el porcentaje de equivalencia que el SKU recibió por el [matcher](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) instalado en su tienda. Aún es posible acceder a la página completa de detalles del SKU, haciendo clic en el botón *«Ver página de detalles»*.
 
-![ES Sidebar received](//images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/fd3306cf276f1f52281fa583a448661a/ES_Sidebar_received.gif)
+![ES Sidebar received](https://images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/fd3306cf276f1f52281fa583a448661a/ES_Sidebar_received.gif)
 ## ¿Por qué realizamos este cambio?
 Desarrollamos la barra lateral para brindar más agilidad a su operación y facilitar la catalogación de SKU recibidos, permitiendo:    
 - Acceder a la información necesaria para un SKU sin salir de la lista principal.  
diff --git a/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md b/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md
index 471db3684..9408140da 100644
--- a/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md
+++ b/docs/announcements/es/marketplacenetwork-and-integrations-are-now-a-single-page.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Unificamos Marketplace Network y el módulo de Integrac
 
 Para centralizar las oportunidades de conexión entre marketplaces VTEX y marketplaces externos, unificamos las páginas de Integraciones y Marketplace Network, y ahora se denominan __Marketplaces e integraciones__. La actualización estará disponible en todas las cuentas VTEX a partir del 03 de mayo de 2023.   
 
-![Marketplaces e integraciones](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
+![Marketplaces e integraciones](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
 
 ## ¿Qué cambió?  
 
diff --git a/docs/announcements/es/marketplaces-received-skus-beta.md b/docs/announcements/es/marketplaces-received-skus-beta.md
index 75ceb0644..5dce4480f 100644
--- a/docs/announcements/es/marketplaces-received-skus-beta.md
+++ b/docs/announcements/es/marketplaces-received-skus-beta.md
@@ -25,7 +25,7 @@ Esta beta abierta es la primera de una serie de mejoras y actualizaciones de pro
 
 Una de las primeras y principales mejoras es la nueva forma de seleccionar los SKUs en masa - para que pueda aprobarlos o rechazarlos en masa. Alineado con nuestra [Styleguide](https://styleguide.vtex.com/ "Styleguide"), la selección masiva hará que su trabajo sea más rápido y mejor.
 
-![received-skus-bulk](//images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
+![received-skus-bulk](https://images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
 
 
 
@@ -33,13 +33,13 @@ Una de las primeras y principales mejoras es la nueva forma de seleccionar los S
 Uno de los desafíos en la gestión de ítems de múltiples sellers es priorizar su lista de ítems interminable. Para ayudarlo con eso, hemos creado una nueva característica de ordenamiento, donde puede reordenar todos los envíos de acuerdo con el precio y – una de las principales mejoras–  por disponibilidad de inventario. Vea cuántos ítems están disponibles a simple vista, para que pueda aprobar los SKUs que mejor se desempeñarán.
 
 
-![received-skus-ordering](//images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
+![received-skus-ordering](https://images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
 
 
 Esto se extiende a la nueva herramienta de filtrado. Vea y filtre las SKUs por categoría, marca y seller de una manera simple e intuitiva.
 
 
-![received-skus-filtering](//images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
+![received-skus-filtering](https://images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
 
 
 
diff --git a/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md b/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md
index f25c2a949..2be5df72a 100644
--- a/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md
+++ b/docs/announcements/es/master-data-v1-dynamic-settings-deprecation.md
@@ -33,7 +33,7 @@ El **Campo calculado** era una configuración dentro de los campos de [entidad d
 
 Este tipo de campo, ilustrado a continuación, ya no estará disponible a partir del 17 de junio de 2024. Los campos calculados creados anteriormente dejarán de funcionar en la misma fecha.
 
-![image6](//images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/981d72dc1c1cc713a12f2be8bb4e1658/image6.png)
+![image6](https://images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/981d72dc1c1cc713a12f2be8bb4e1658/image6.png)
 
 ### Editar el valor del campo
 
@@ -41,7 +41,7 @@ Al configurar acciones de triggers, existía la opción de **Editar el valor del
 
 La opción **Editar el valor del campo**, ilustrada a continuación, ya no estará disponible al configurar acciones de triggers a partir del 17 de junio de 2024. Los triggers configurados con esta acción continuarán operativos solo hasta esa fecha.
 
-![image1](//images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/05a36119e4539dec726d1bdea30622d6/image1.png)
+![image1](https://images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/05a36119e4539dec726d1bdea30622d6/image1.png)
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
index ac1db3297..e623e7347 100644
--- a/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
@@ -33,7 +33,7 @@ Usted tiene dos maneras por las cuales puede alcanzar el mismo efecto de la prom
 
 Usted puede configurar una [Promoción Regular](/es/tutorial/registro-promocion-regular) con el tipo de descuento __Precio Máximo por Artículo__.
 
-![PrecoMaximoEN](//images.contentful.com/alneenqid6w5/ZqS2JBJtEkgusUu4qOsEE/ab84f34757924220efe4d44250d499a5/PrecoMaximoEN.png)
+![PrecoMaximoEN](https://images.contentful.com/alneenqid6w5/ZqS2JBJtEkgusUu4qOsEE/ab84f34757924220efe4d44250d499a5/PrecoMaximoEN.png)
 
 Se trata de un escenario incluso mejor que el anterior, ya que el comerciante tiene más opciones de agrupación, por ejemplo, por categoría de producto.
 
diff --git a/docs/announcements/es/mercado-libre-integration-new-interface-for-mapping-categories-and.md b/docs/announcements/es/mercado-libre-integration-new-interface-for-mapping-categories-and.md
index f07b7804b..fa3c5faf2 100644
--- a/docs/announcements/es/mercado-libre-integration-new-interface-for-mapping-categories-and.md
+++ b/docs/announcements/es/mercado-libre-integration-new-interface-for-mapping-categories-and.md
@@ -19,7 +19,7 @@ Continuando con las mejoras realizadas para la [certificación de Mercado Libre]
 
 Antes de la certificación, los sellers tenían que rellenar la [plantilla de mapeo](https://help.vtex.com/es/tutorial/mapeamento-de-categorias-variacoes-e-atributos-do-mercado-libre--4xNFUZZmboCSUVdLCFo6eA) con las categorías y los atributos de los productos que deseaban anunciar en Mercado Libre. La nueva interfaz para mapear categorías y atributos llega para sustituir a la plantilla de mapeo.
 
-![announcement mapperES2](//images.contentful.com/alneenqid6w5/6paqLHxIDlX6t02g7L8qOu/6b22c6d9dace59cd549a632cb2b81706/announcement_mapperES2.gif)
+![announcement mapperES2](https://images.contentful.com/alneenqid6w5/6paqLHxIDlX6t02g7L8qOu/6b22c6d9dace59cd549a632cb2b81706/announcement_mapperES2.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md b/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md
index 5c698e7a0..4021f0774 100644
--- a/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md
+++ b/docs/announcements/es/mercado-libre-integration-new-promotion-management-interface.md
@@ -19,7 +19,7 @@ Continuando con las mejoras realizadas para la [certificación de Mercado Libre]
 
 En la nueva página **Promociones** de Mercado Libre, puedes gestionar una lista con las diferentes campañas promocionales en la plataforma disponibles para tu tienda.
 
-![Promociones](//images.ctfassets.net/alneenqid6w5/2drMTXsElqn1iLe0WnVuTa/81ac8a2fea28f3db675cc33ef164ab8c/Promociones.gif)
+![Promociones](https://images.ctfassets.net/alneenqid6w5/2drMTXsElqn1iLe0WnVuTa/81ac8a2fea28f3db675cc33ef164ab8c/Promociones.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md b/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
index 1974e21f2..8fa857f90 100644
--- a/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
+++ b/docs/announcements/es/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
@@ -19,14 +19,14 @@ A partir de ahora, su tiendna puede utilizar punto y coma (`;`) para concatenar
 
 Esta feature funciona en los campos de copia (`CC`) y copia oculta (`CCO`), así como la coma ya funcionaba anteriormente. Ahora las dos opciones de concatenación son válidas.
 
-![Message Center bug fix - EN](//images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
+![Message Center bug fix - EN](https://images.ctfassets.net/alneenqid6w5/4P6PvvTcgEASE8ooUakoSG/73b01a7f5ebdaaebc66aa805dbe61169/Message_Center_bug_fix_-_EN.png)
 
 Este cambio simple en el módulo responsable del envío de e-mails transaccionales redujo drásticamente la tasa de errores en comunicaciones con clientes.
 
 El gráfico siguiente muestra la tasa de errores de una tienda antes de implementado el soporte de concatenación con punto y coma. Más del 90% de los correos electrónicos fallaban todos los días.
 
-![Message Center bug fix 2](//images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
+![Message Center bug fix 2](https://images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
 
 Después de implementada la mejora, los errores en el envío de e-mails transaccionales de la misma tienda fueron completamente eliminados, como muestra este otro gráfico:
 
-![Message Center bug fix 3](//images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
+![Message Center bug fix 3](https://images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
diff --git a/docs/announcements/es/multi-currency-gift-card.md b/docs/announcements/es/multi-currency-gift-card.md
index 411a68bb9..5ca5019d5 100644
--- a/docs/announcements/es/multi-currency-gift-card.md
+++ b/docs/announcements/es/multi-currency-gift-card.md
@@ -39,7 +39,7 @@ Para crear una tarjeta de regalo en una moneda concreta, sigue los pasos que se
 4. Rellena los demás campos para crear la tarjeta de regalo.
 5. Haz clic en `Guardar`.
 
-![Tarjeta de regalo multimoneda](//images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/8908f1e2a6d350ebdbc3ae648aad5eec/GiftCard_Multicurrency_ES_1.PNG)
+![Tarjeta de regalo multimoneda](https://images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/8908f1e2a6d350ebdbc3ae648aad5eec/GiftCard_Multicurrency_ES_1.PNG)
 
 Las monedas disponibles serán las mismas que las registradas en las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) de cada tienda.
 
diff --git a/docs/announcements/es/my-authentication-section-in-my-account.md b/docs/announcements/es/my-authentication-section-in-my-account.md
index ffe592b5f..14b0aa73c 100644
--- a/docs/announcements/es/my-authentication-section-in-my-account.md
+++ b/docs/announcements/es/my-authentication-section-in-my-account.md
@@ -25,15 +25,15 @@ Este cambio afectará a todas las tiendas VTEX. Debido a que el cambio interfier
 
 En esta pestaña los usuarios podrán gestionar su contraseña. También es posible gestionar las sesiones de inicio de sesión, lo que permite al usuario cancelar otras sesiones de forma remota. Encontrará más detalles sobre el uso de la pestaña en la sección [Autenticación del artículo Configurar My Account](https://help.vtex.com/es/tutorial/como-funciona-mi-cuenta--2BQ3GiqhqGJTXsWVuio3Xh).
 
-![My Authentication app ES](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
+![My Authentication app ES](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
 
-![My Authentication Session Management ES](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
+![My Authentication Session Management ES](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
 
 El 29 de septiembre también se eliminará el componente de gestión de contraseña del perfil de usuario para evitar duplicidades. Las siguientes imágenes muestran ejemplos de una página de perfil de usuario con y sin el componente de gestión de contraseña.
 
-![My Account with password ES](//images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/35a836d86b2c5ace5ae163209ef847dc/My_Account_with_password_ES.png)
+![My Account with password ES](https://images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/35a836d86b2c5ace5ae163209ef847dc/My_Account_with_password_ES.png)
 
-![My Account no password ES](//images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/d60f96ecdedda8f48b23be754f3fbfae/My_Account_no_password_ES.png)
+![My Account no password ES](https://images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/d60f96ecdedda8f48b23be754f3fbfae/My_Account_no_password_ES.png)
 
 ## ¿Por qué hicimos este cambio?
 
@@ -66,12 +66,12 @@ Para que la pestaña My Authentication sea visible públicamente en su tienda:
 1. En el panel lateral izquierdo del Admin, vaya a la sección **CONFIGURACIÓN DE LA CUENTA**.
 2. Haga clic en **Apps**.
 3. Haga clic en **Mis aplicaciones**.  
-![My apps menu ES](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/0beb96ff4fd9af269359146a2df949be/My_apps_menu_ES.png)
+![My apps menu ES](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/0beb96ff4fd9af269359146a2df949be/My_apps_menu_ES.png)
 4. Vaya a la app **My Account** y haga clic en `Configuración`.  
-![My apps installed ES](//images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/919435a4bf6e8222afc6a4d91c136ff5/My_apps_installed_ES.png)
+![My apps installed ES](https://images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/919435a4bf6e8222afc6a4d91c136ff5/My_apps_installed_ES.png)
 5. En la sección **AUTHENTICATION** de la configuración de la app, marque la casilla `Visible`.
 6. Haga clic en `Guardar`.
-![My Authentication visible setting ES](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/7669ac9d7f583253b032a48b0471fbd7/My_Authentication_visible_setting_ES.png)
+![My Authentication visible setting ES](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/7669ac9d7f583253b032a48b0471fbd7/My_Authentication_visible_setting_ES.png)
 
 También puede acceder directamente a la configuración de la aplicación My Account en el Admin a través de una URL.
 
@@ -80,4 +80,4 @@ También puede acceder directamente a la configuración de la aplicación My Acc
 
 Tras habilitar la visibilidad de la pestaña **Autenticación**, esta aparecerá en el perfil de usuario de la tienda. Cualquier usuario puede acceder a ella desde el panel lateral izquierdo.
 
-![My Authentication app ES](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
+![My Authentication app ES](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
diff --git a/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md b/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
index 5c64eee73..2c6cd668b 100644
--- a/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
+++ b/docs/announcements/es/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'La página Vista General de tu Admin VTEX ha sido redis
 
 La página de [Vista general (Beta)](https://help.vtex.com/es/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) de tu Admin VTEX ha sido rediseñada y ahora ofrece nuevos gráficos, métricas y vistas. Estas nuevas funcionalidades proporcionan un seguimiento en tiempo real de tu operación, ofreciendo visibilidad con relación a los indicadores para que tu equipo y tú tengan un rápido feedback sobre las acciones realizadas en la tienda y puedan actuar con prontitud para implementar mejoras. 
 
-![ES Visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/5b97a2cf1346f1c95fc32512c95da972/ES_Visa__o_geral_beta.png)
+![ES Visão geral beta](https://images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/5b97a2cf1346f1c95fc32512c95da972/ES_Visa__o_geral_beta.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/new-indexation-history-screen.md b/docs/announcements/es/new-indexation-history-screen.md
index d965989d3..284984fa7 100644
--- a/docs/announcements/es/new-indexation-history-screen.md
+++ b/docs/announcements/es/new-indexation-history-screen.md
@@ -19,7 +19,7 @@ En toda operación de ecommerce, es necesario registrar o cambiar información d
 
 Para mejorar la experiencia de monitoreo de la indexación del catálogo, rediseñamos la página **Historial de indexación** en el Admin VTEX. La nueva interfaz permite dar seguimiento al tiempo de indexación de los productos y al status de indexación de la tienda.
 
-![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+![Histórico da Indexação 1 - ES](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/new-orders-module-interface-official.md b/docs/announcements/es/new-orders-module-interface-official.md
index fa9d67c67..0085564fe 100644
--- a/docs/announcements/es/new-orders-module-interface-official.md
+++ b/docs/announcements/es/new-orders-module-interface-official.md
@@ -27,15 +27,15 @@ En comparación con la versión beta, la interfaz que será oficial a partir del
 
 * **Búsqueda de pedidos sin límite de fecha:** se puede buscar pedidos sin límite de fecha y ver todos los pedidos relacionados con el criterio utilizado, independientemente de la fecha de creación del pedido. Esta búsqueda no puede ser asociada a otros filtros. Sin embargo, puedes seleccionar un periodo de búsqueda personalizado de hasta seis meses y combinarlo con los filtros. Aprende más en el artículo [Filtrar pedidos en Todos los pedidos](https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192).
 
-  ![busca_sem_limite_data_all_es](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
+  ![busca_sem_limite_data_all_es](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
 
 * **Diagrama del pedido:** en la sección _Status del pedido_ de la nueva interfaz, de forma predeterminada, se muestra una línea de tiempo con los eventos del pedido. Ahora también puedes ver el _Diagrama del pedido_. Al hacer clic en `Ver diagrama`, se abrirá una ventana modal que muestra una imagen similar a la siguiente:
 
-  ![diagrama_pedido_es](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
+  ![diagrama_pedido_es](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
 
 Si todavía no has utilizado la versión beta, la imagen a continuación muestra la correspondencia de campos entre la versión antigua de la página **Detalles del pedido** y la versión oficial:
 
-![board_comparativo_interface_pedido_v2_es](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
+![board_comparativo_interface_pedido_v2_es](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
index 503d58fa8..1ad282c60 100644
--- a/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
+++ b/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
@@ -23,7 +23,7 @@ Ahora puedes acceder a la información de los proveedores registrados en tu tien
 
 También hemos mejorado la experiencia de navegación de la pantalla que permite agregar, editar y buscar proveedores.
 
-![nueva_interfaz_de_proveedores_de_administración](//images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/48c5d451e15c9ce565047821cb074b03/nueva_interfaz_de_proveedores_de_administraci_n.JPG)
+![nueva_interfaz_de_proveedores_de_administración](https://images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/48c5d451e15c9ce565047821cb074b03/nueva_interfaz_de_proveedores_de_administraci_n.JPG)
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md b/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md
index 470799496..6fc48eece 100644
--- a/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md
+++ b/docs/announcements/es/new-promotion-list-manage-your-promotions-more-efficiently.md
@@ -30,7 +30,7 @@ Para la Lista de promociones, desarrollamos una nueva interfaz que te permite:
 * Exportar tu lista de promociones activas.
 * Duplicar las promociones activas o archivadas para que el proceso de creación sea más rápido.
 
-![lista-promocoes-es](//images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/4549ea65d574f5481ccbea5cde7e549c/lista-promociones-es.PNG)
+![lista-promocoes-es](https://images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/4549ea65d574f5481ccbea5cde7e549c/lista-promociones-es.PNG)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/new-roles-page.md b/docs/announcements/es/new-roles-page.md
index e84c9e785..4b27974f4 100644
--- a/docs/announcements/es/new-roles-page.md
+++ b/docs/announcements/es/new-roles-page.md
@@ -28,7 +28,7 @@ Además de todas las funcionalidades de la versión anterior, la nueva página *
 * Acceder a la lista completa de los roles registrados en tu tienda con un diseño más moderno e intuitivo, actualizado de acuerdo con el [nuevo Admin VTEX](https://help.vtex.com/es/tutorial/admin-vtex-comience-aqui--531cHtUCUi3puRXNDmKziw).
 * Consultar información útil para gestionar los roles directamente desde la lista, así como el número de usuarios asociados a cada uno; también el tipo de rol (predefinido o personalizado) y la fecha de creación del mismo.
 
-![roles-es](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/61435c94a6654fd066e3b0f5f8cd2fd0/roles-es.png)
+![roles-es](https://images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/61435c94a6654fd066e3b0f5f8cd2fd0/roles-es.png)
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/new-sales-performance-dashboard.md b/docs/announcements/es/new-sales-performance-dashboard.md
index 2d421b01e..916b9b2b4 100644
--- a/docs/announcements/es/new-sales-performance-dashboard.md
+++ b/docs/announcements/es/new-sales-performance-dashboard.md
@@ -20,7 +20,7 @@ Con un volumen cada vez mayor de datos disponibles para que las operaciones de e
 
 El dashboard permite a los usuarios analizar los datos de todos los canales de venta de la tienda y de sus sellers, incluyendo métricas sobre los ingresos, los pedidos, el ticket promedio y mucho más. También incluye gráficos y tablas para que puedas comparar los resultados de diferentes periodos, e introduce once opciones de filtro para proporcionar insights unificados de toda la operación.
 
-![Sales Perf Dash ES](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
+![Sales Perf Dash ES](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
 
 ## ¿Qué cambió?
 Anteriormente, tu Admin VTEX solo contaba con la página Insights para generar inteligencia empresarial a partir de los datos de tus operaciones. Ahora hemos incluido una nueva página, Desempeño de Ventas, para ofrecerte una visión más detallada de los resultados de los diferentes canales de venta de tu tienda. La página Insights permanecerá en tu Admin VTEX.
diff --git a/docs/announcements/es/new-sku-bindings-interface.md b/docs/announcements/es/new-sku-bindings-interface.md
index 26c835333..e03530e7b 100644
--- a/docs/announcements/es/new-sku-bindings-interface.md
+++ b/docs/announcements/es/new-sku-bindings-interface.md
@@ -19,7 +19,7 @@ VTEX permite que tu tienda actúe a la vez como [seller](https://help.vtex.com/e
 
 Para mejorar esta experiencia, hemos rediseñado la página **Vínculos de SKU** en el Admin VTEX. La nueva interfaz te permite seguir y gestionar la relación de vínculo entre los SKU del seller y del marketplace de una forma más sencilla y ágil.
 
-![sku_binding_page_ES_final](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/c5f9ed73561edd82c340eef6f28ef12a/sku_binding_page_ES_final.png)
+![sku_binding_page_ES_final](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/c5f9ed73561edd82c340eef6f28ef12a/sku_binding_page_ES_final.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/new-subscriptions-module.md b/docs/announcements/es/new-subscriptions-module.md
index c3166182c..3d81c3458 100644
--- a/docs/announcements/es/new-subscriptions-module.md
+++ b/docs/announcements/es/new-subscriptions-module.md
@@ -39,36 +39,36 @@ La mejora del sistema de suscripciones también trajo nuevas funcionalidades par
 #### Nueva página de detalles de suscripción 
 Nuestra página de detalles de suscripción fue rediseñada con el fin de mejorar la experiencia del consumidor al reducir el tiempo para encontrar información y realizar tareas.  Además, contamos con una nueva funcionalidad de agregar ítems a una suscripción existente. 
 
-![img1 subscriptions ES](//images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/4af981552e541469c5e6e64cce65c0fe/img1_subscriptions_ES.png)
+![img1 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/4af981552e541469c5e6e64cce65c0fe/img1_subscriptions_ES.png)
 
 #### Barra de acciones
 Añadimos una barra de acciones para mejorar la comunicación con el usuario sobre lo que se necesita realizar o comunicar eventos importantes sobre su suscripción. 
 
-![img2 subscriptions ES](//images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/3e81d1e12117816f16aed0868751f9fa/img2_subscriptions_ES.png)
+![img2 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/3e81d1e12117816f16aed0868751f9fa/img2_subscriptions_ES.png)
 
 #### Agregar productos a su suscripción 
 Ahora se puede agregar nuevos ítems a su suscripción a través de la búsqueda de los productos disponibles en su tienda.
-![img3 subscriptions ES](//images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/a6418dd71b17f26b8052bae335b51514/img3_subscriptions_ES.png)
+![img3 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/a6418dd71b17f26b8052bae335b51514/img3_subscriptions_ES.png)
 
 #### Crear una nueva suscripción
 Añadimos una funcionalidad muy esperada: la pantalla de creación de suscripciones. La misma permite configurar una nueva suscripción sin tener que pasar por el checkout y ejecutar un pedido en ese momento. Para realizar esta acción, basta hacer clic en el botón __Nueva suscripción__, en la lista de suscripciones. 
 
-![img4 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/f6798de027a9761f8844f8a989ab45ea/img4_subscriptions_ES.png)
+![img4 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/f6798de027a9761f8844f8a989ab45ea/img4_subscriptions_ES.png)
 
 ### Nuevo concepto de suscripción para el sistema 
 Antes, para el sistema de VTEX, una suscripción estaba compuesta por un SKU asociado a una configuración de compra. Eso permitía que el consumidor de la tienda suscriba SKUs con direcciones de entrega e, incluso, con formas de pago diferentes —una evolución en comparación con la primera versión del sistema.
 
 #### Antes:
-![img5 subscriptions ES](//images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/0746b7539b10864ce48ed94972ac7f73/img5_subscriptions_ES_2.png)
+![img5 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/0746b7539b10864ce48ed94972ac7f73/img5_subscriptions_ES_2.png)
 
-![img6 subscriptions ES](//images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/be74eff4e0f355e2f2f54025d67e6b31/img6_subscriptions_ES.png)
+![img6 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/be74eff4e0f355e2f2f54025d67e6b31/img6_subscriptions_ES.png)
 
-![img7 subscriptions ES](//images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/8de4a03901a548be9c3ca65eaf9b68a4/img7_subscriptions_ES.png)
+![img7 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/8de4a03901a548be9c3ca65eaf9b68a4/img7_subscriptions_ES.png)
 
 La suscripción ahora consiste en una lista de SKUs y una configuración de compra determinada. Esto significa que eliminamos el concepto de «Grupos de suscripción» de nuestro sistema. Vea más información en nuestro artículo [Cómo funciona la suscripción](https://help.vtex.com/es/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453). El siguiente diagrama muestra el nuevo concepto de suscripción:  
 
 #### Ahora:
-![img8 subscriptions ES](//images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/0d226ff2f1bbcf31e803c7b9d297e35a/img8_subscriptions_ES_2.png)
+![img8 subscriptions ES](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/0d226ff2f1bbcf31e803c7b9d297e35a/img8_subscriptions_ES_2.png)
 
 ### Fecha de ciclo de la suscripción
 El cálculo de la próxima fecha del pedido por suscripción cambió. Esta alteración permite que el usuario modifique la fecha de su pedido con mayor facilidad. Para acompañar el cambio, desarrollamos una [API](https://developers.vtex.com/vtex-developer-docs/reference/cycles) que permite elegir con exactitud la próxima fecha, sin tener que modificar la frecuencia de la suscripción para que se adecue a la fecha deseada.
diff --git a/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md b/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md
index d26f57d1f..f9c874bdb 100644
--- a/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md
+++ b/docs/announcements/es/new-ui-for-the-admins-user-management-dashboard.md
@@ -22,7 +22,7 @@ El diseño del panel de gestión de usuarios se actualizó con los mismos están
 - Exhibición de la configuración de MFA (autenticación de múltiples factores) de cada usuario en la lista de usuarios.
 - Botón para exportar los datos de la lista de usuarios en un archivo CSV que incluye ID, email y nombre.
 
-![Lista Usuários User Management ES](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
+![Lista Usuários User Management ES](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
 
 Además, el panel tiene algunos cambios:
 
diff --git a/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md b/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md
index 5c1126f0e..7dc0941a9 100644
--- a/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md
+++ b/docs/announcements/es/novo-layout-no-e-mail-de-codigo-de-acesso.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Actualizamos el layout del e-mail recibido al solicitar
 
 Actualizamos el layout del e-mail recibido al solicitar el código de acceso para su admin. Ahora, cada vez que se solicite el código de acceso para iniciar sesión o cambiar la contraseña, recibirá un e-mail como este a continuación:
 
-![announcement-novo-layout-email-codigo-acesso ES](//images.ctfassets.net/alneenqid6w5/6LquxoOPXIDPxed7Zj46xY/f97c0ba49ec2942bfd37033f3e4ea521/announcement-novo-layout-email-codigo-acesso_ES.png)
+![announcement-novo-layout-email-codigo-acesso ES](https://images.ctfassets.net/alneenqid6w5/6LquxoOPXIDPxed7Zj46xY/f97c0ba49ec2942bfd37033f3e4ea521/announcement-novo-layout-email-codigo-acesso_ES.png)
 
 ## ¿Qué cambia?
 
diff --git a/docs/announcements/es/offer-pickup-points-for-subscription-orders.md b/docs/announcements/es/offer-pickup-points-for-subscription-orders.md
index 5b76d2d48..acfb900f3 100644
--- a/docs/announcements/es/offer-pickup-points-for-subscription-orders.md
+++ b/docs/announcements/es/offer-pickup-points-for-subscription-orders.md
@@ -23,7 +23,7 @@ La funcionalidad de puntos de recogida del módulo Suscripciones solo está disp
 
 Anteriormente, las suscripciones no tenían puntos de recogida como una de las opciones de entrega. Con la nueva funcionalidad, el cliente final puede elegir los puntos de recogida de los ítems de un pedido de suscripción cuando realiza el _checkout_, como se ilustra en la siguiente imagen.
 
-![subscriptionspickup ES](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
+![subscriptionspickup ES](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
 
 Además, puede asignar puntos de recogida para las suscripciones nuevas y las suscripciones existentes a través de la [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1).
 
diff --git a/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md b/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md
index 5db168042..60d45bb79 100644
--- a/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md
+++ b/docs/announcements/es/offer-status-module-for-integrations-with-vtex-marketplaces.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Monitorea tus anuncios con el nuevo módulo Status de l
 
 __Status de los anuncios__ es el nuevo módulo en el Admin VTEX que les permite a los sellers monitorear el envío y la sincronización de los anuncios de integraciones con marketplaces VTEX globalmente. Puedes acceder al módulo en el Admin VTEX a través de __Marketplace > Conexiones > Status de los anuncios__ o ingresando Status de los anuncios en la barra de búsqueda.  
 
-![Pantalla de estado de la oferta](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/91b3ae83719e933617324f74223d736b/-ES-_Offer_Status_-_GIF.gif)
+![Pantalla de estado de la oferta](https://downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/91b3ae83719e933617324f74223d736b/-ES-_Offer_Status_-_GIF.gif)
 
 ## ¿Por qué desarrollamos esta funcionalidad?
 
diff --git a/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md b/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
index e061b78f5..df793921b 100644
--- a/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
+++ b/docs/announcements/es/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
@@ -33,7 +33,7 @@ La revisión y la eventual adaptación de este cambio deben aplicarse a través
 
 Pasos necesarios para la revisión y adaptación:
 
-1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Personalización__: Si la página "/account/orders" tiene alguna personalización de front-end, debe migrarse y adaptarse a la nueva URL "/account#/orders". Revise y realice todas las pruebas necesarias garantizando el funcionamiento de todos los recursos personalizados.  
 3. __Enlaces del sitio__: Revise y actualice todos los enlaces personalizados del sitio y de los correos electrónicos transaccionales que antes dirigían al usuario a la URL "/account/orders". Estos enlaces ahora deben direccionar al usuario a "/account#/orders".
 
diff --git a/docs/announcements/es/price-filters-more-search-flexibility.md b/docs/announcements/es/price-filters-more-search-flexibility.md
index ebf8f69c6..46201ef07 100644
--- a/docs/announcements/es/price-filters-more-search-flexibility.md
+++ b/docs/announcements/es/price-filters-more-search-flexibility.md
@@ -23,7 +23,7 @@ Ahora usted puede filtrar los precios combinando las múltiples Categorías y Ma
 
 Esta actualización de la funcionalidad permite la exportación de precios más específicos, a partir de la selección de los filtros.
 
-![filtro preco-ES](//images.ctfassets.net/alneenqid6w5/7rJSF8qFUuoagVZaeVw2mp/4f00df74073f97f6da58c621b0b4a313/filtro_preco-ES.png)
+![filtro preco-ES](https://images.ctfassets.net/alneenqid6w5/7rJSF8qFUuoagVZaeVw2mp/4f00df74073f97f6da58c621b0b4a313/filtro_preco-ES.png)
 
 ## ¿Qué necesito hacer?
 Para utilizar esta nueva configuración, realice los siguientes pasos:
diff --git a/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md b/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
index c274ce86c..72e4a848c 100644
--- a/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
+++ b/docs/announcements/es/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
@@ -31,7 +31,7 @@ Para saber si su cuenta aún está utilizando Pricing V1, realice los siguientes
 
 Si ve una pantalla similar a la que aparece a continuación, significa que necesita realizar la migración de su cuenta. 
 
-![Tela pricing antiga - ES](//images.ctfassets.net/alneenqid6w5/54yIQLSCHg9VfDUumByo2r/20ba1b2f56b1e1b90fa6ecc4f386cbc5/Tela_pricing_antiga_-_ES.png)
+![Tela pricing antiga - ES](https://images.ctfassets.net/alneenqid6w5/54yIQLSCHg9VfDUumByo2r/20ba1b2f56b1e1b90fa6ecc4f386cbc5/Tela_pricing_antiga_-_ES.png)
 
 Si su cuenta VTEX sigue utilizando versiones anteriores del Admin de VTEX (como "vtexcommercestable"), usted necesitará realizar la migración de la misma. Para eso, siga los pasos a continuación: 
 
diff --git a/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md b/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
index 64c88cd23..07baac4f6 100644
--- a/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
+++ b/docs/announcements/es/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
@@ -31,7 +31,7 @@ A partir de ahora, el **Simulador de promociones** estará accesible para todas
 * **Probar la aplicación** de otras promociones en el carrito antes de activarlas, incluidas las promociones programadas o inactivas.
 * **Comprender los motivos** por los que no se ha aplicado una promoción al carrito.
 
-![promotions simulator - es-gif 3](//downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/57780b2b9e038420e502eda2c41f4357/promotions_simulator_gi-3.gif)
+![promotions simulator - es-gif 3](https://downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/57780b2b9e038420e502eda2c41f4357/promotions_simulator_gi-3.gif)
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/rate-vtexs-service-in-your-admin.md b/docs/announcements/es/rate-vtexs-service-in-your-admin.md
index 1593031f8..3701c1d76 100644
--- a/docs/announcements/es/rate-vtexs-service-in-your-admin.md
+++ b/docs/announcements/es/rate-vtexs-service-in-your-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Hemos lanzado una página de encuesta de satisfacción
 
 Hemos lanzado la nueva página *Encuesta de Satisfacción* en el Admin VTEX. Ahora, puedes evaluar nuestro servicio de soporte sin salir de la plataforma VTEX.
 
-![Pesquisa de satisfação ES](//images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/075a8169826dbd7f0a98354b9825d467/image__18_.png)
+![Pesquisa de satisfação ES](https://images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/075a8169826dbd7f0a98354b9825d467/image__18_.png)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
index 36ad5a829..fe21df5cf 100644
--- a/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
+++ b/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -47,7 +47,7 @@ Pide a tu equipo de desarrolladores que revisen tus integraciones que utilizan l
 
 Tu equipo podrá guiarse por el siguiente diagrama para evaluar si es necesario ajustar una integración, según la [configuración del reCAPTCHA en el orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) de tu tienda y cómo se [autentican](https://developers.vtex.com/docs/guides/authentication-overview) los requests realizados a estos endpoints:
 
-![reCAPTCHA diagram](//images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/ec9c6f6a9dfdc69fbcd412bde938d4f2/recaptcha-config-ES.png)
+![reCAPTCHA diagram](https://images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/ec9c6f6a9dfdc69fbcd412bde938d4f2/recaptcha-config-ES.png)
 
 - __Caso 1__: *no se requieren cambios en la integración, pero tu tienda podría estar en riesgo.*
 
diff --git a/docs/announcements/es/redesigned-products-and-skus-page.md b/docs/announcements/es/redesigned-products-and-skus-page.md
index 2b815ae61..06a4036e6 100644
--- a/docs/announcements/es/redesigned-products-and-skus-page.md
+++ b/docs/announcements/es/redesigned-products-and-skus-page.md
@@ -28,7 +28,7 @@ La nueva interfaz de **Productos y SKUs** permite:
 - Monitorear el status de los productos y SKU de forma más directa y visual con iconos y status de SKU directamente en la lista.
 - Identificar más fácilmente los productos y SKU que tengan información pendiente para estar disponibles para la venta mediante el nuevo status **Pendiente**.
 
-![catalog-products-skus-es](//images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/2978ab303cb7eba7b77ad22caa620a49/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_29_13_1.png)
+![catalog-products-skus-es](https://images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/2978ab303cb7eba7b77ad22caa620a49/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_29_13_1.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/registering-pickup-points-is-now-easier-and-faster.md b/docs/announcements/es/registering-pickup-points-is-now-easier-and-faster.md
index f0266bbf6..2902f6819 100644
--- a/docs/announcements/es/registering-pickup-points-is-now-easier-and-faster.md
+++ b/docs/announcements/es/registering-pickup-points-is-now-easier-and-faster.md
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Ahora, usted puede subir una planilla XLS con todos los puntos de recogida que desea ofrecer en su tienda.'
 ---
 
-Usted no necesita más registrar puntos de recogida uno a uno. Ahora, el administrador le permite subir una planilla XLS [(como la de este ejemplo)](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls) con todos los puntos de recogida que desea ofrecer en su tienda.
+Usted no necesita más registrar puntos de recogida uno a uno. Ahora, el administrador le permite subir una planilla XLS [(como la de este ejemplo)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls) con todos los puntos de recogida que desea ofrecer en su tienda.
 
 
 ## Más agilidad en sus configuraciones de logística
diff --git a/docs/announcements/es/reusing-images-in-site-editor.md b/docs/announcements/es/reusing-images-in-site-editor.md
index 5d91e86b2..e7511f01a 100644
--- a/docs/announcements/es/reusing-images-in-site-editor.md
+++ b/docs/announcements/es/reusing-images-in-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Hemos mejorado los bloques con la opción nativa de sub
 
 Hemos mejorado la forma de gestionar sus imágenes en [Site Editor](https://help.vtex.com/es/subcategory/site-editor--9Arh3cJIOYlfSD1MUC2h3) mediante un Image Widget, que es un repositorio de imágenes centralizado para que pueda subir y reutilizar las imágenes de la tienda. 
 
-![gif-image-widget-es](//images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/d92ceb37b53da2c63b9802a6c082db77/Yhin0k3Vio.gif)
+![gif-image-widget-es](https://images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/d92ceb37b53da2c63b9802a6c082db77/Yhin0k3Vio.gif)
 
 <div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 16px">
   Image Widget está disponible en Open Beta para los usuarios de VTEX IO.
diff --git a/docs/announcements/es/sales-performance-dashboard-updates.md b/docs/announcements/es/sales-performance-dashboard-updates.md
index a00eb375b..4d7b3187a 100644
--- a/docs/announcements/es/sales-performance-dashboard-updates.md
+++ b/docs/announcements/es/sales-performance-dashboard-updates.md
@@ -19,7 +19,7 @@ La página «Desempeño de ventas» es un dashboard que permite a los operadores
 
 Actualizamos la experiencia en la página basándonos en tus sugerencias y agregamos nuevas posibilidades para aplicar filtros, vistas y exploración de datos. 
 
-![Sales perf update ES](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
+![Sales perf update ES](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
 
 ## ¿Qué cambió?
 Mejoramos algunas funcionalidades existentes, como Filtros y Datos y expandimos el menú de Vistas. La nueva experiencia de filtros de la página permite más combinaciones de filtros con menos clics. Por su parte, la nueva funcionalidad de menú Vista está diseñada para guardar los filtros y métricas aplicados en la página, lo que permite volver rápidamente al mismo contexto. 
diff --git a/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md b/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md
index 0febd274e..0ba947a2d 100644
--- a/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md
+++ b/docs/announcements/es/save-user-opt-in-using-stored-information-for-future-purchases.md
@@ -23,7 +23,7 @@ Anteriormente, tras el registro en la tienda o la primera compra, los datos del
 
 A partir de ahora, dos casillas de verificación en la pantalla de pago permitirán al usuario indicar si quiere que su información personal y de pago se almacene y se reutilice para futuras compras. De este modo, se reducirá el tiempo que tarda el cliente en realizar la compra. 
 
-![ Save user data opt-in ES](//images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/503e29a5bdf5749d0d44bd525b96117e/Save_user_data_-_ES.PNG)
+![ Save user data opt-in ES](https://images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/503e29a5bdf5749d0d44bd525b96117e/Save_user_data_-_ES.PNG)
 
 Más información en [SmartCheckout - Rellenado automático de los datos del cliente](https://help.vtex.com/es/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan#).
 
diff --git a/docs/announcements/es/schedule-content-publication-with-site-editor.md b/docs/announcements/es/schedule-content-publication-with-site-editor.md
index 05e87cef7..c9cbd7c26 100644
--- a/docs/announcements/es/schedule-content-publication-with-site-editor.md
+++ b/docs/announcements/es/schedule-content-publication-with-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Crea y programa versiones de bloques predefinidas en el
 
 El recurso **Configuraciones** del Site Editor se actualizó. Ahora, además de llamarse **Versiones**, puedes crear versiones del contenido de tu tienda que se han desactivado, y activarlas cuando así lo desees.
 
-![activating-versions-es](//images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/fe0961feb8749a97ba1879d2245e2a04/activating-versions-es.gif)
+![activating-versions-es](https://images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/fe0961feb8749a97ba1879d2245e2a04/activating-versions-es.gif)
 
 ## ¿Qué cambió?
 Anteriormente, la funcionalidad **Versiones** se llamaba **Configuraciones**, y solo era posible crear una nueva versión activada, por ejemplo un carrusel con productos en promoción, o programar su activación. Después de deshabilitar una versión, no podía volver a activarla.
diff --git a/docs/announcements/es/search-filters-in-instores-endless-aisle.md b/docs/announcements/es/search-filters-in-instores-endless-aisle.md
index 0ffff6aca..5f33f491c 100644
--- a/docs/announcements/es/search-filters-in-instores-endless-aisle.md
+++ b/docs/announcements/es/search-filters-in-instores-endless-aisle.md
@@ -25,7 +25,7 @@ Anteriormente, los filtros de búsqueda de VTEX Intelligent Search no estaban di
 
 Con la nueva funcionalidad, al buscar un término, los vendedores pueden filtrar los resultados por rango de precios, departamento y marca, por ejemplo, entre otros filtros configurables en VTEX Intelligent Search. Esto permite encontrar rápidamente el producto deseado.
 
-![instore-filtros-es](//images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b4bbbc744c5efe25cbc100d53113ca6b/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_09_28.png)
+![instore-filtros-es](https://images.ctfassets.net/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/b4bbbc744c5efe25cbc100d53113ca6b/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-14_09_28.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
index 34df1727c..6bb117c3a 100644
--- a/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
+++ b/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -30,7 +30,7 @@ Antes, la barra de búsqueda solo permitía buscar las páginas del Admin VTEX.
 
 Para buscar, haz clic en la barra de búsqueda, selecciona la opción `Pedidos` y ejecuta la búsqueda deseada. Cada búsqueda puede devolver hasta 10 resultados, como se muestra en la siguiente imagen:
 
-![order_global_search_ES](//images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/a109785412d490a21a2f9f984ad47114/order_global_search_ES.gif)
+![order_global_search_ES](https://images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/a109785412d490a21a2f9f984ad47114/order_global_search_ES.gif)
 
 Al hacer clic en un resultado, se te redirigirá a la [página de detalles](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) del pedido. Además, los últimos 10 pedidos buscados se registran como historial de búsquedas recientes para mayor facilidad de acceso. El registro de búsqueda se almacena a nivel de [usuario](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) y no se comparte entre diferentes usuarios.
 
diff --git a/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md b/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
index 90ba46050..4d3cd31f8 100644
--- a/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
+++ b/docs/announcements/es/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
@@ -19,7 +19,7 @@ La __Black Friday__ será pronto. Y, con ella, viene el deseo de aprovechar esta
 
 Para ayudarle en esta tarea, VTEX está lanzando una __app exclusiva en asociación con Google__, que estará disponible en nuestra [App Store](https://apps.vtex.com/vtex-google-shopping/p).
 
-![Google Shopping App](//images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
+![Google Shopping App](https://images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
 
 Ella integra su negocio a Google Ads y le permite divulgar sus productos en Google Shopping, utilizando las nuevas Smart Shopping Campaigns, y acompañar los resultados con facilidad y rapidez.
 
diff --git a/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md b/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
index 86d98a486..e62ecbef0 100644
--- a/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
+++ b/docs/announcements/es/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
@@ -27,4 +27,4 @@ https://{accountName}.myvtex.com/admin/shopping-season
 
 Sólo hay que sustituir `{accountName}` por el Account Name de su tienda, como en la imagen de abajo.
 
-![Shopping Season Guidelines - 2023 - ES](//images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/6fec5cf6a7f649fef7c71a4c0f3d7e00/Shopping_Season_Guidelines_-_2023_-_ES.png)
+![Shopping Season Guidelines - 2023 - ES](https://images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/6fec5cf6a7f649fef7c71a4c0f3d7e00/Shopping_Season_Guidelines_-_2023_-_ES.png)
diff --git a/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md b/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md
index 1b7ae878b..c1db4a78d 100644
--- a/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md
+++ b/docs/announcements/es/social-selling-share-instore-carts-using-qr-codes.md
@@ -27,7 +27,7 @@ Anteriormente, la funcionalidad Social Selling en inStore consistía en generar
 
 Con el cambio, inStore ahora también genera un código QR que puede ser leído por los dispositivos de los clientes, además del enlace compartible.
 
-![instore-social-selling-qr-code-share-es](//images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/1d1c94682042d029f24d527ef8290e94/image3.png)
+![instore-social-selling-qr-code-share-es](https://images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/1d1c94682042d029f24d527ef8290e94/image3.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/social-selling-share-your-instore-cart.md b/docs/announcements/es/social-selling-share-your-instore-cart.md
index ee65bfad7..6441ae1d6 100644
--- a/docs/announcements/es/social-selling-share-your-instore-cart.md
+++ b/docs/announcements/es/social-selling-share-your-instore-cart.md
@@ -27,7 +27,7 @@ Anteriormente no era posible compartir el carrito en inStore, [solo en el ecomme
 
 Con inStore Social Selling, los vendedores de su tienda física pueden seleccionar productos y generar un enlace para compartir la **Sugerencia de carrito** con uno o más clientes a través de WhatsApp, como se muestra a continuación. También es posible copiar el enlace y compartirlo en otras redes sociales.
 
-![socialselling-ES](//images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/7eb64840bde5bb1648e313d6277e872f/socialselling-ES.gif)
+![socialselling-ES](https://images.ctfassets.net/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/7eb64840bde5bb1648e313d6277e872f/socialselling-ES.gif)
 
 El vendedor puede enviar el mismo enlace a varios clientes, tantas veces como lo desee. Cada vez que una persona acceda a este enlace, se generará un nuevo carrito de compra, exactamente igual al creado en inStore. Cada carrito también estará asociado a la cuenta del vendedor y, si lo hay, al código del vendedor.
 
@@ -35,7 +35,7 @@ Sus clientes pueden acceder al carrito, realizar el pago y concluir la compra en
 
 Otra posibilidad es que el vendedor rellene los datos de entrega del cliente, elija el método de pago y luego comparta un **Enlace de pago.** De este modo, el enlace del carrito compartido ya contendrá toda la información personal. El cliente solo tiene que completar los datos de pago para finalizar la compra. Vea cómo funciona a continuación.
 
-![paymentlink ES](//images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/1136d3cb3448664865ce0615392076d7/paymentlink_ES.gif)
+![paymentlink ES](https://images.ctfassets.net/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/1136d3cb3448664865ce0615392076d7/paymentlink_ES.gif)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md b/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md
index 539d653ca..7a660224c 100644
--- a/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md
+++ b/docs/announcements/es/the-native-links-to-my-account-page-will-change-review-your-settings.md
@@ -33,7 +33,7 @@ La revisión y la eventual adaptación de este cambio deben aplicarse a través
 
 Pasos necesarios para la revisión y adaptación:
 
-1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
+1. __Configuración básica__: Revise si el template de la página "/account" (imagen a continuación) ya utiliza view part `<vtex.cmc:accountUserProfile />` y, si es necesario, realice una actualización.  View part es responsable por cargar toda la información del cliente, incluyendo sus pedidos. Se debe eliminar de este template view parts anteriores, `<vtex.cmc:accountAddress/>` y `<vtex.cmc:orderList />`.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)  
 2. __Personalización__: Si la página "/account/orders" tiene alguna personalización de front-end, debe migrarse y adaptarse a la nueva URL "/account#/orders". Revise y realice todas las pruebas necesarias garantizando el funcionamiento de todos los recursos personalizados.  
 3. __Enlaces del sitio__: Revise y actualice todos los enlaces personalizados del sitio y de los correos electrónicos transaccionales que antes dirigían al usuario a la URL "/account/orders". Estos enlaces ahora deben direccionar al usuario a "/account#/orders".
 
diff --git a/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md b/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md
index fc189e4f2..9105f2461 100644
--- a/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md
+++ b/docs/announcements/es/transparency-and-security-with-the-new-audit-module.md
@@ -18,7 +18,7 @@ announcementSynopsisES: 'Lanzamiento de una nueva herramienta de auditoría'
 
 Siempre en línea con las mejores prácticas de seguridad y transparencia para tu tienda, VTEX ha lanzado un nuevo recurso de auditoría: **Audit**. 
 
-![Screenshot for Audit UI for announcement](//images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/e5e64ab35e499176c8815260dd703e00/Audit_ES.png)
+![Screenshot for Audit UI for announcement](https://images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/e5e64ab35e499176c8815260dd703e00/Audit_ES.png)
 
 A partir de ahora, los administradores pueden verificar las distintas operaciones que se han realizado en su tienda de forma sencilla y rápida. Es posible crear varios filtros para facilitar la búsqueda de eventos y aumentar la velocidad de los procesos de auditoría.
 
diff --git a/docs/announcements/es/update-grants-in-the-promotions-module.md b/docs/announcements/es/update-grants-in-the-promotions-module.md
index 9f5e5e4ea..e0d2e0bf9 100644
--- a/docs/announcements/es/update-grants-in-the-promotions-module.md
+++ b/docs/announcements/es/update-grants-in-the-promotions-module.md
@@ -37,6 +37,6 @@ Con esta actualización, usted tiene más poder sobre el comportamiento de sus p
  6. Haga clic en **Utilizar configuraciones de recurrencia**
  7. Establezca la configuración deseable de días y horarios para la promoción
 
-![CRON 2 ES](//images.ctfassets.net/alneenqid6w5/7b6Kfpi1jxXcrr1qrPSycM/f08e20b7f69d579ff8b9d6f79bf19b01/CRON_2_ES.png)
+![CRON 2 ES](https://images.ctfassets.net/alneenqid6w5/7b6Kfpi1jxXcrr1qrPSycM/f08e20b7f69d579ff8b9d6f79bf19b01/CRON_2_ES.png)
 
  
diff --git a/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md b/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
index 7dcdf4a85..721315711 100644
--- a/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
+++ b/docs/announcements/es/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
@@ -33,5 +33,5 @@ La funcionalidad puede ser utilizada siempre que el administrador de la tienda d
 - En  “¿Cuál es el tipo y el valor de la tasa?”, escoja la opción Tasa Nominal
 - Complete los ítems necesarios y haga clic en guardar
 
-![Nominal tax ES](//images.ctfassets.net/alneenqid6w5/2qg2CsNALcvSojlXkcJkvI/3bdf5a1e180bc33a30efa9b99a802aaf/Nominal_tax_ES.png)
+![Nominal tax ES](https://images.ctfassets.net/alneenqid6w5/2qg2CsNALcvSojlXkcJkvI/3bdf5a1e180bc33a30efa9b99a802aaf/Nominal_tax_ES.png)
 
diff --git a/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md b/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md
index 20441c382..55758f6fc 100644
--- a/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md
+++ b/docs/announcements/es/ux-improvements-at-checkout-for-expired-cards.md
@@ -23,7 +23,7 @@ Con el objetivo de continuar perfeccionando esa experiencia, incluimos una valid
 
 Antes, un consumidor podía seleccionar una tarjeta vencida y realizar una compra, cuyo pago luego sería rechazado. Ahora, señalamos las tarjetas caducadas y evitamos que sean seleccionadas en el checkout, para una experiencia de compra más fluida.
 
-![ES - Expired Cards](//images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/276fcf10f19f3c8ec703547d75e2aa5d/ES_-_Expired_Cards.png)
+![ES - Expired Cards](https://images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/276fcf10f19f3c8ec703547d75e2aa5d/ES_-_Expired_Cards.png)
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md b/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
index 0249545d7..4e7d8ceda 100644
--- a/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
+++ b/docs/announcements/es/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
@@ -28,7 +28,7 @@ Antes, las tiendas que utilizaban [VTEX Intelligent Search](https://help.vtex.co
 * Fijar un producto en las primeras posiciones de los resultados de búsqueda.
 * Analizar la información principal del producto.
 
-![visual-merch-rules-ES-announcement](//images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/5230eea36b9eb3014e45d1f988d6057d/visual-merch-rules-ES-announcement.png)
+![visual-merch-rules-ES-announcement](https://images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/5230eea36b9eb3014e45d1f988d6057d/visual-merch-rules-ES-announcement.png)
 
 Al crear una regla de merchandising en el Admin VTEX en **Storefront > Intelligent Search > Reglas de merchandising > Agregar** puedes escoger el tipo de editor que deseas utilizar. Consulta la guía [Reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicion) para más información sobre las diferencias entre el Editor manual y el Editor visual.
 
diff --git a/docs/announcements/es/vtex-io-documentation-has-a-new-home.md b/docs/announcements/es/vtex-io-documentation-has-a-new-home.md
index e10c57a0d..1ede9649b 100644
--- a/docs/announcements/es/vtex-io-documentation-has-a-new-home.md
+++ b/docs/announcements/es/vtex-io-documentation-has-a-new-home.md
@@ -19,7 +19,7 @@ Desde el 13 de marzo de 2020, la documentación de VTEX IO y VTEX IO Store Frame
 
 Se puede acceder a esta documentación a través de [**VTEX IO Docs**](https://vtex.io/docs), una plataforma de documentación que reúne todos los contenidos disponibles en ambas soluciones. 
 
-![vtex-io-docs](//images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/d22c3ecd05c9fecccdba405a83e61d30/vtex-io-docs.png)
+![vtex-io-docs](https://images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/d22c3ecd05c9fecccdba405a83e61d30/vtex-io-docs.png)
 
 ## ¿Por qué estamos haciendo este cambio?
 
@@ -33,7 +33,7 @@ La decisión de eliminar la documentación de VTEX IO y VTEX IO Store Framework
 
 Con nuestra [documentación de la API](https://developers.vtex.com/reference), [guías](https://developers.vtex.com/docs) dirigidas a los desarrolladores que trabajan con integraciones, personalizaciones y  [Release Notes](https://developers.vtex.com/changelog)  sincronizadas con todo lo nuevo de nuestro producto, el [**Developer Portal**](https://developers.vtex.com) - antiguo Developer Docs del Help Center - ofrece en un solo lugar todos los recursos necesarios para los usuarios más técnicos de VTEX. 
 
-![developer-portal](//images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/7785b5da696fe5e428e742a93abb654f/developer-portal.png)
+![developer-portal](https://images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/7785b5da696fe5e428e742a93abb654f/developer-portal.png)
 
 Con el fin de mejorar la experiencia de desarrollo en VTEX, el Developer Portal pronto contará también con la documentación de VTEX IO y VTEX IO Store Framework - disponible hoy en VTEX IO Docs. 
 
diff --git a/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md b/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md
index 84daea5c9..6cc15566c 100644
--- a/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md
+++ b/docs/announcements/es/vtex-is-now-available-in-dutch-french-and-korean.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'El VTEX Admin tiene tres nuevas opciones de idioma.'
 
 El panel de VTEX ahora admite diferentes opciones de idiomas para atender a nuestros clientes en todo el mundo. Localizamos nuestro producto para mejorar su experiencia en general, no solo mediante traducciones, sino también a nivel cultural al tomar en cuenta las particularidades de cada país.  
 
-![ES new locales](//images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/bb1e1ac7fefbeccdc3d9d6d05883cc6a/ES_new_locales.jpg)
+![ES new locales](https://images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/bb1e1ac7fefbeccdc3d9d6d05883cc6a/ES_new_locales.jpg)
 
 ## ¿Qué cambió?
 Además de portugués, inglés, español, italiano, rumano y japonés, a partir de mayo de 2021, los usuarios VTEX encontrarán tres nuevas opciones de idioma en nuestro panel del admin: neerlandés, francés y coreano. 
diff --git a/docs/announcements/es/vtex-login-now-features-recaptcha.md b/docs/announcements/es/vtex-login-now-features-recaptcha.md
index 752b61e6b..00f8d14d3 100644
--- a/docs/announcements/es/vtex-login-now-features-recaptcha.md
+++ b/docs/announcements/es/vtex-login-now-features-recaptcha.md
@@ -19,7 +19,7 @@ El acceso de VTEX a través de email y contraseña ahora cuenta con reCAPTCHA, q
 
 Usamos Invisible reCAPTCHA, una tecnología de Google que determina cuándo es necesario confirmar si el intento de acceso está siendo realizado por un robot o un humano.
 
-![reCAPTCHA](//images.contentful.com/alneenqid6w5/2obeayJZP6k8q8a6W68sQI/08bbf823714965fd207961a792a94f9f/reCAPTCHA.png)
+![reCAPTCHA](https://images.contentful.com/alneenqid6w5/2obeayJZP6k8q8a6W68sQI/08bbf823714965fd207961a792a94f9f/reCAPTCHA.png)
 
 Esto significa que la solicitud de confirmación puede o no aparecer, dependiendo de varios factores.
 
diff --git a/docs/announcements/es/vtex-marketplace-launches-in-2022.md b/docs/announcements/es/vtex-marketplace-launches-in-2022.md
index 02d696746..addca80c4 100644
--- a/docs/announcements/es/vtex-marketplace-launches-in-2022.md
+++ b/docs/announcements/es/vtex-marketplace-launches-in-2022.md
@@ -29,7 +29,7 @@ Nuestras nuevas funcionalidades permiten a los _marketplaces_:
 
 Ve más allá del ecommerce tradicional con las [novedades de Marketplace de VTEX](https://content.vtex.com/es/2022-marketplace-release/?utm_source=announcement&utm_medium=organic&utm_campaign=2022_marketplace_release).
 
-![capa de blog marketplace 2022](//images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/20f7d7d151a3dbd76d0d69e5858510d0/capa_de_blog.png)
+![capa de blog marketplace 2022](https://images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/20f7d7d151a3dbd76d0d69e5858510d0/capa_de_blog.png)
 
 ## ¿Qué estamos lanzando?
 
@@ -78,7 +78,7 @@ Obtén más información sobre cada característica a continuación.
 
 ### Seller Portal
 
-![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
 
 Seller Portal es una edición de la plataforma VTEX destinada a que los [sellers](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#vender-em-marketplace) se conecten y vendan sus productos en los _marketplaces_ hospedados en VTEX. Con el portal, los _sellers_ acceden a todas las funcionalidades esenciales para la operación del ecommerce en grandes vitrinas, aportando visibilidad y conversión de ventas.
 
@@ -126,7 +126,7 @@ Para facilitar que los nuevos _sellers_ se unan al Seller Portal, también hemos
 
 ### Gestión de sellers
 
-![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 Hemos lanzado la experiencia renovada de la página [Gestión de sellers](https://help.vtex.com/es/tutorial/gerenciamento-de-sellers-beta--6eEiOISwxuAWJ8w6MtK7iv), donde los operadores de los _marketplaces_ [agregan sellers](https://help.vtex.com/es/tutorial/adicionar-seller-beta--6q4G4RNqVENr5YMJyindwL), registran su información respectiva y gestionan el status de cada _seller_.
 
diff --git a/docs/announcements/es/we-released-the-new-order-placed.md b/docs/announcements/es/we-released-the-new-order-placed.md
index 54908a84f..8e9e6d0d1 100644
--- a/docs/announcements/es/we-released-the-new-order-placed.md
+++ b/docs/announcements/es/we-released-the-new-order-placed.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'La nueva versión de la página de confirmación de ped
 
 A principios de este mes divulgamos el lanzamiento de una de las muchas novedades que VTEX está desarrollando para mejorar aún más la experiencia del usuario - la nueva sección de Mis Pedidos. Hoy lanzamos otra feature que integra esta sección: la nueva versión de la página de confirmación de pedido (Order Placed).
 
-![PedidoConfirmado](//images.contentful.com/alneenqid6w5/2Xr5mMmZMs0WAy4i6cK4EC/50c153cf99a137eb55f0d0dbc34ee820/PedidoConfirmado.png)
+![PedidoConfirmado](https://images.contentful.com/alneenqid6w5/2Xr5mMmZMs0WAy4i6cK4EC/50c153cf99a137eb55f0d0dbc34ee820/PedidoConfirmado.png)
 
 Ahora forma parte del __Checkout Confirmation__, feature responsable de las páginas de confirmación de Checkout. Y trae ventajas importantes para su tienda:
 
@@ -29,7 +29,7 @@ Activar esta actualización es simple: basta con acceder a la pestaña Pedidos e
 
 Todas las tiendas VTEX tienen hasta 3 meses para probar a voluntad la nueva versión de Order Placed. Después del 24 de agosto de 2017, la nueva versión será activada por defecto, y la antigua será descontinuada. ¡Entonces quédate conectado!
 
-![PedidoConfirmado2](//images.contentful.com/alneenqid6w5/5xM0PRucykSa84SWWO4k2S/0dcf664d17697bdbf8a32b074578af27/PedidoConfirmado2.png)
+![PedidoConfirmado2](https://images.contentful.com/alneenqid6w5/5xM0PRucykSa84SWWO4k2S/0dcf664d17697bdbf8a32b074578af27/PedidoConfirmado2.png)
 
 Es probable que desee actualizar su personalización. Para saber cómo, vea el tutorial [Personalizar las páginas de Checkout Confirmation](/es/tutorial/personalizando-las-paginas-del-checkout-confirmation).
 
diff --git a/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md
index af55cf104..c544ba47c 100644
--- a/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/es/welcome-to-the-redesigned-vtex-admin-new.md
@@ -19,7 +19,7 @@ Las empresas digitales buscan cada vez más contar con herramientas que les perm
 
 Bienvenido a la [experiencia del nuevo Admin VTEX](https://content.vtex.com/join-new-admin-beta-program-es/?utm_source=announcement&utm_medium=organic&utm_campaign=new_admin_beta).
 
-![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/were-launching-your-personal-data-set-up-screen.md b/docs/announcements/es/were-launching-your-personal-data-set-up-screen.md
index 37ba2facf..25dbe558f 100644
--- a/docs/announcements/es/were-launching-your-personal-data-set-up-screen.md
+++ b/docs/announcements/es/were-launching-your-personal-data-set-up-screen.md
@@ -19,7 +19,7 @@ Ahora es más fácil editar su configuración personal de acceso al Admin VTEX.
 
 El equipo de VTEX ID creó la pantalla My User, que puede ser fácilmente accesada por la topbar del Admin.
 
-![dadosPessoais](//images.contentful.com/alneenqid6w5/3c85FBDbJumIgA0smG4Q2S/2af591bd4d724dadae3adebd7525311b/dadosPessoais.png)
+![dadosPessoais](https://images.contentful.com/alneenqid6w5/3c85FBDbJumIgA0smG4Q2S/2af591bd4d724dadae3adebd7525311b/dadosPessoais.png)
 
 En ella puedes:
 - Ver su e-mail registrado en el Admin.
diff --git a/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md b/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md
index 851198379..2cd87eb11 100644
--- a/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md
+++ b/docs/announcements/es/wishlist-discover-the-new-vtex-app-store-app.md
@@ -24,7 +24,7 @@ La aplicación está disponible en [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Inclusión de un ícono de corazón al lado de cada producto en las listas de productos y en las páginas de detalle de los productos.
 - Creación de una página para la Lista de Deseos, donde el consumidor pueda ver todos los artículos y comprarlos fácilmente.
 
-![Wishlist Printscreen](//images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
+![Wishlist Printscreen](https://images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
 
 ## ¿Cuáles son los beneficios?
 - Hace que la experiencia de compra de su tienda sea más completa.
diff --git a/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index d977ae0c4..55303f276 100644
--- a/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -21,7 +21,7 @@ A partir del 25 de junio de 2019, el usuario que no tenga acceso vinculado al pe
 
 Con el fin de garantizar una mayor seguridad, creamos la posibilidad de limitar perfiles de acceso en la pantalla **Configuración**, permitiendo que solo algunos usuarios editen las informaciones.
 
-![2019-06-07 17 24 38-Configuración.es](//images.ctfassets.net/alneenqid6w5/1SrUApvjjUxaUZRJfJnqwB/b597be4eb4343dbf03e74feee5cb5cdc/2019-06-07_17_24_38-Configuraci__n.es.png)
+![2019-06-07 17 24 38-Configuración.es](https://images.ctfassets.net/alneenqid6w5/1SrUApvjjUxaUZRJfJnqwB/b597be4eb4343dbf03e74feee5cb5cdc/2019-06-07_17_24_38-Configuraci__n.es.png)
 
 ## Principales ventajas
 
@@ -41,6 +41,6 @@ Para hacer esto es necesario añadir un producto llamado `Checkout` al perfil de
  6. Elija el tipo de permiso deseado: `Save Order Configuration`, para permitir al usuario editar la sección **Pedidos**, o `Save OrderForm Configuration`, para permitir al usuario editar la sección **Carrito**.
  7. Haga clic en **Guardar**
 
-![GIT-Checkout.es](//images.ctfassets.net/alneenqid6w5/245LTWQExeQEmDWb7HrAyZ/9acea81b01288dd051acffec409a2984/GIT-Checkout.es.gif)
+![GIT-Checkout.es](https://images.ctfassets.net/alneenqid6w5/245LTWQExeQEmDWb7HrAyZ/9acea81b01288dd051acffec409a2984/GIT-Checkout.es.gif)
 
 Después de añadir este nuevo producto a un perfil, asegúrese de que los usuarios deseados están asociados a este perfil de acceso.
diff --git a/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md b/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md
index 5d3e405fc..b7d8e6896 100644
--- a/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md
+++ b/docs/announcements/pt/access-googles-pagespeed-insights-in-your-vtex-admin.md
@@ -21,7 +21,7 @@ Com esse objetivo, nós criamos a nova tela [Performance das páginas web](https
 
 O PageSpeed Insights e o Lighthouse são ferramentas desenvolvidas pelo Google para gerar relatórios sobre a experiência do usuário de uma página tanto em dispositivos móveis quanto em computadores, fornecendo sugestões sobre como essa página pode ser aprimorada. Eles usam as [principais métricas da web do Google](https://web.dev/vitals/#core-web-vitals) para avaliar a experiência do usuário online. 
 
-![Web page performance Dash PT](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
+![Web page performance Dash PT](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/admin-disponivel-em-japones.md b/docs/announcements/pt/admin-disponivel-em-japones.md
index 6eb3ec3b7..dfe4e3ac0 100644
--- a/docs/announcements/pt/admin-disponivel-em-japones.md
+++ b/docs/announcements/pt/admin-disponivel-em-japones.md
@@ -25,4 +25,4 @@ A tradução do Admin para o japonês foi incentivada pela [abertura do nosso no
 
 ## O que precisa ser feito?
 Para visualizar o Admin em japonês, basta selecionar o código __JP__ no menu de seleção de idiomas no canto superior direito da tela. 
-![ Selecionar o código JP](//images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/900a9b6d702feaa51ea2d582354165a4/japones.png)
+![ Selecionar o código JP](https://images.ctfassets.net/alneenqid6w5/4rQI0Nb2Bmz6P6dQs3Bixv/900a9b6d702feaa51ea2d582354165a4/japones.png)
diff --git a/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
index 1d7eecd2a..b6ba0b616 100644
--- a/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -28,7 +28,7 @@ Agora, os usuários irão visualizar apenas os itens do menu lateral que eles t
 
 A imagem abaixo ilustra uma das possibilidades de visualização da barra lateral de acordo com a nova organização para melhorar a segurança e a experiência do usuário da sua loja.
 
-![PT Sidebar permissions announcement screenshot](//images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/0404c44da45173707c4fb3af5eb2de74/PT_Sidebar_permissions_announcement_screenshot.png)
+![PT Sidebar permissions announcement screenshot](https://images.ctfassets.net/alneenqid6w5/1dnqc48HsZDxmiUygavYHZ/0404c44da45173707c4fb3af5eb2de74/PT_Sidebar_permissions_announcement_screenshot.png)
 
 ## Por que fizemos essa mudança?
 O objetivo dessa mudança é limitar a visualização de módulos importantes dentro de uma conta, protegendo a integridade da sua loja. Dessa forma, o risco de possíveis interrupções na operação da loja é minimizado e você garante que cada usuário irá visualizar apenas o que é permitido ao seu perfil de acesso.
diff --git a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md
index 5a8e7d015..9905578ee 100644
--- a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md
+++ b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization-teste.md
@@ -21,7 +21,7 @@ Uma situação comum em restaurantes que aceitam pedidos online, por exemplo, é
 
 Para simplificar o uso dessa funcionalidade, desenvolvemos o aplicativo **Assembly Options**, que apresenta uma interface para configuração e gerenciamento das opções de customização. O aplicativo está disponível somente para lojas que utilizam [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
+![assembly-options-app](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md
index 4244c98d1..32b4af495 100644
--- a/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md
+++ b/docs/announcements/pt/assembly-options-new-app-to-simplify-product-customization.md
@@ -21,7 +21,7 @@ Uma situação comum em restaurantes que aceitam pedidos online, por exemplo, é
 
 Para simplificar o uso dessa funcionalidade, desenvolvemos o aplicativo **Assembly Options**, que apresenta uma interface para configuração e gerenciamento das opções de customização. O aplicativo está disponível somente para lojas que utilizam [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
-![assembly-options-app](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
+![assembly-options-app](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md b/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
index 6533636c8..3b7a3baec 100644
--- a/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
+++ b/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Participe de um dia de treinamento intensivo em VTEX com os maiores especialistas no assunto.'
 ---
 
-![cover fb 01](//images.ctfassets.net/alneenqid6w5/fj8PzFYRP2yaeAaIiKCW2/e06c967d7129640c493c545ecfc48db8/cover_fb_01.png)
+![cover fb 01](https://images.ctfassets.net/alneenqid6w5/fj8PzFYRP2yaeAaIiKCW2/e06c967d7129640c493c545ecfc48db8/cover_fb_01.png)
 
 <div class="alert alert-info">
 Um dia inteiro de treinamento em VTEX com os maiores especialistas no assunto.
diff --git a/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 8241515f6..92df48457 100644
--- a/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -25,7 +25,7 @@ A solução combina duas funcionalidades e aplicativos móveis:
 * [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): controle da entrega last mile.
 * **Aplicativos móveis:** aplicativos móveis para separadores e entregadores.
 
-![pick_pack_gif_PT](//images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/f35996b674b6ded591dcb0d8b46ee0f1/pick_pack_gif_PT.gif)
+![pick_pack_gif_PT](https://images.ctfassets.net/alneenqid6w5/5T6FQD7E0lFkze9DtsrDas/f35996b674b6ded591dcb0d8b46ee0f1/pick_pack_gif_PT.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md b/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md
index 905550602..b09f59846 100644
--- a/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md
+++ b/docs/announcements/pt/campaign-promotions-new-option-when-configuring-target-audience.md
@@ -23,7 +23,7 @@ Aprimoramos a configuração de audiência de campanha para permitir que você s
 
 No Admin VTEX, em **Produtos > Promoções e Taxas > Audiências de campanhas > Nova audiência de campanha**, nas configurações referentes ao **Público-alvo**, acrescentamos a opção “e”, onde antes havia apenas a opção “ou”.  Isso significa que agora você pode aplicar uma lógica de adição de critérios (“e”), além da lógica de alternativa (“ou”) que já existia antes. Veja a imagem a seguir:
 
-![publico-alvo-e-ou-pt](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
+![publico-alvo-e-ou-pt](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
 
 Com a nova opção, é possível criar promoções de campanha a partir da combinação de critérios de forma mais flexível.
 
diff --git a/docs/announcements/pt/catalogs-new-visual-and-navigation.md b/docs/announcements/pt/catalogs-new-visual-and-navigation.md
index 8af62cc16..c87e2f320 100644
--- a/docs/announcements/pt/catalogs-new-visual-and-navigation.md
+++ b/docs/announcements/pt/catalogs-new-visual-and-navigation.md
@@ -23,16 +23,16 @@ A principal diferença para a versão antiga está na navegação. Rearranjamos
 ## O que mudou
 
 A maior parte dos itens do Catálogo podem ser encontrados em _Catálogo_, que fica na seção _PRODUTOS_ do menu lateral.
-![Catálogo1](//images.ctfassets.net/alneenqid6w5/6zg0sXt3qwc8KGUuwEwsSI/0f3f2fafcc1a4addaabe3e5deb100296/Cat__logo1.png)
+![Catálogo1](https://images.ctfassets.net/alneenqid6w5/6zg0sXt3qwc8KGUuwEwsSI/0f3f2fafcc1a4addaabe3e5deb100296/Cat__logo1.png)
 
 
 O subitem _Vale-compra_ (que antes se chamava _Vales_ e ficava em _Controle de Campanhas_) está no item _Pagamentos_, dentro da seção _TRANSAÇÕES_ do menu lateral.
-![Catálogo2](//images.ctfassets.net/alneenqid6w5/2giEGOSr8EGWWqS4goeOU8/c655d3c669fcfb54ea7a44b97d490d4e/Cat__logo2.png)
+![Catálogo2](https://images.ctfassets.net/alneenqid6w5/2giEGOSr8EGWWqS4goeOU8/c655d3c669fcfb54ea7a44b97d490d4e/Cat__logo2.png)
 
 
 O item _Configurações_ virou um subitem de _CMS_, que fica na seção _CONFIGURAÇÕES DE LOJA_ do menu lateral.
-![Catálogo3](//images.ctfassets.net/alneenqid6w5/6ybb0PjANUOC6kgugu4WCW/d599404279f39970b047aa9aac532d3d/Cat__logo3.png)
+![Catálogo3](https://images.ctfassets.net/alneenqid6w5/6ybb0PjANUOC6kgugu4WCW/d599404279f39970b047aa9aac532d3d/Cat__logo3.png)
 
 
 A aba _Marketplace_ ganhou uma seção própria de mesmo nome no menu lateral.
-![Catálogo4](//images.ctfassets.net/alneenqid6w5/5oQsBoQHOoMqYK688g8c6a/d708824d3496d3d66b06dcd27dd5aa1b/Cat__logo4.png)
+![Catálogo4](https://images.ctfassets.net/alneenqid6w5/5oQsBoQHOoMqYK688g8c6a/d708824d3496d3d66b06dcd27dd5aa1b/Cat__logo4.png)
diff --git a/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md b/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
index 6b06048d8..c518d28e6 100644
--- a/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
+++ b/docs/announcements/pt/changes-in-the-name-and-restricted-actions-available-to-the-master-user.md
@@ -27,7 +27,7 @@ Fique tranquilo, nós não nos enganamos. Após uma análise criteriosa, nossa e
 
 Mas isso não é tudo. Também modificamos o processo para mudar o usuário Titular de uma conta, transformando-o em um fluxo de transferência controlado por convite que é totalmente auditável.  
 
-![Gerenciamento titular gif](//images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/a3f49ef6a2cc6208afa52859da36b7fe/Announcement_PT.gif)
+![Gerenciamento titular gif](https://images.ctfassets.net/alneenqid6w5/ha7KIfmy1QJQvmpnXJN5R/a3f49ef6a2cc6208afa52859da36b7fe/Announcement_PT.gif)
 
 Confira o artigo [Transferência de propriedade da loja](https://help.vtex.com/pt/tutorial/transferencia-de-propriedade-da-loja) para mais detalhes sobre este novo processo.
 
diff --git a/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
index 4a38867fb..9fa08e9c1 100644
--- a/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
@@ -45,7 +45,7 @@ Para verificar se os provedores de antifraude configurados em sua loja permitem
 2. Em **Pagamentos**, clique em **Configurações > Afiliações de Gateway**. 
 3. Ao selecionar o provedor de antifraude escolhido, verifique se a opção **Campo de documento do titular do cartão **está disponível na tela de configuração.
 
-![campo de documento do titular do cartão](//images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/5bbfb8cbfce605b09d61e10a8ff06e3b/campo_de_documento_do_titular_do_cart__o.png)
+![campo de documento do titular do cartão](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/5bbfb8cbfce605b09d61e10a8ff06e3b/campo_de_documento_do_titular_do_cart__o.png)
 
 <div class = "alert alert-warning">
   Caso a opção <b>Campo de documento do titular do cartão</b> não esteja disponível na tela de configuração do seu provedor de antifraude, o campo <b>Identificação do titular do cartão</b> continuará sendo exibido na tela do Checkout da loja e deverá ser obrigatoriamente preenchido pelo cliente.
diff --git a/docs/announcements/pt/coupon-experience-improvements.md b/docs/announcements/pt/coupon-experience-improvements.md
index 668a6cb9d..be067095c 100644
--- a/docs/announcements/pt/coupon-experience-improvements.md
+++ b/docs/announcements/pt/coupon-experience-improvements.md
@@ -27,7 +27,7 @@ A nova experiência de Cupons oferece os seguintes recursos:
 
 A nova [Lista de cupons](https://help.vtex.com/pt/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ) exibe todos os cupons cadastrados na sua loja, possibilitando gerenciar seus dados e analisar em quais pedidos foram utilizados.
 
-![listacupons pt](//images.ctfassets.net/alneenqid6w5/2uuixGwgV7WgvGhpwZnQiM/a883b91403037b62476bb53c0b905ad3/listacupons_pt.gif)
+![listacupons pt](https://images.ctfassets.net/alneenqid6w5/2uuixGwgV7WgvGhpwZnQiM/a883b91403037b62476bb53c0b905ad3/listacupons_pt.gif)
 
 ### Acesso mais fácil aos códigos de cupom
 
@@ -44,7 +44,7 @@ Os novos filtros possibilitam a visualização apenas dos cupons que atendem a c
 - Última edição
 - Tipo de cupom 
 
-![filtroscupons pt](//images.ctfassets.net/alneenqid6w5/4ycZkMAbrCVdN5sryskEcE/0d0fe4fe0dc88f7fdadc0bc21999a946/filtroscupons_pt.gif)
+![filtroscupons pt](https://images.ctfassets.net/alneenqid6w5/4ycZkMAbrCVdN5sryskEcE/0d0fe4fe0dc88f7fdadc0bc21999a946/filtroscupons_pt.gif)
 
 ### Grupos de cupons para gerenciamento ágil
 
diff --git a/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md b/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md
index 47d4cfa98..e544c38b7 100644
--- a/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md
+++ b/docs/announcements/pt/customize-your-payment-conditions-with-the-new-card-level-functionality.md
@@ -35,6 +35,6 @@ A configuração é similar à das demais condições especiais de pagamento.
 
 A principal diferença é que, depois de selecionar o país e o banco emissor, o lojista pode escolher entre as opções de Card Level disponibilizadas pela instituição financeira escolhida.
 
-![comousarcardlevel](//images.ctfassets.net/alneenqid6w5/29GOP06jAv6PhE408fiaD8/947436f46b295ce09ab7928a9bb7ce95/comousarcardlevel.gif)
+![comousarcardlevel](https://images.ctfassets.net/alneenqid6w5/29GOP06jAv6PhE408fiaD8/947436f46b295ce09ab7928a9bb7ce95/comousarcardlevel.gif)
 
 Para saber em detalhes como configurar essa feature, veja nosso [artigo sobre Configuração de Condições Especiais de Pagamento](https://help.vtex.com/tutorial/special-conditions--tutorials_456).
diff --git a/docs/announcements/pt/displaying-pickup-points-on-google-maps.md b/docs/announcements/pt/displaying-pickup-points-on-google-maps.md
index 5b5a12650..25452b35f 100644
--- a/docs/announcements/pt/displaying-pickup-points-on-google-maps.md
+++ b/docs/announcements/pt/displaying-pickup-points-on-google-maps.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Aplicativo que lista Pontos de Retirada e os exibe como
 
 Uma das funcionalidades mais comuns de websites e lojas online é a disponibilização de mapas que sinalizam a localização de lojas físicas. Com o novo app [Store Locator](https://apps.vtex.com/vtex-store-locator/p#overview), as lojas desenvolvidas com VTEX IO podem utilizar o Google Maps para listar os Pontos de Retirada registrados na loja e exibi-los como marcadores em um mapa.
 
-![Maps](//images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
+![Maps](https://images.ctfassets.net/alneenqid6w5/5Y2mR6XMrFEcRFTAapWrGY/ac3eb4449114856b2c0e573644840dec/mapas.png)
 
 ## O que mudou? 
 As lojas desenvolvidas com VTEX IO agora podem instalar o aplicativo Store Locator e apresentar os pontos de retirada no Google Maps através de marcadores.
diff --git a/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security.md b/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security.md
index 019694a00..e6a15f863 100644
--- a/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security.md
+++ b/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'O resumo da promoção permite revisar as informações
 
 Ao configurar uma nova promoção, é possível cometer erros ao preencher as informações. Para evitar ativar promoções com informações incorretas, criamos o resumo da promoção. Esse novo recurso permite confirmar as configurações da promoção antes de ativá-la.
 
-![resumo-promo-PT](//images.contentful.com/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/3497411cbf0f85ec694c6cc0cfda602f/image.png)
+![resumo-promo-PT](https://images.contentful.com/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/3497411cbf0f85ec694c6cc0cfda602f/image.png)
 
 ## O que mudou?
 Antes, uma promoção era ativada automaticamente quando salva com o status **Ativa**. Com o novo recurso, você pode visualizar um resumo das configurações definidas antes de ativar uma nova promoção. Assim, é possível verificar se os dados da promoção estão corretos, evitando erros de implementação.
diff --git a/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security1.md b/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
index 986186009..76773ce7e 100644
--- a/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
+++ b/docs/announcements/pt/double-check-promotion-settings-before-activating-it-to-ensure-security1.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'O resumo da promoção permite revisar as informações
 
 Ao configurar uma nova promoção, é possível cometer erros ao preencher as informações. Para evitar ativar promoções com informações incorretas, criamos o resumo da promoção. Esse novo recurso permite confirmar as configurações da promoção antes de ativá-la.
 
-![resumo-promo-PT](//images.contentful.com/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/3497411cbf0f85ec694c6cc0cfda602f/image.png)
+![resumo-promo-PT](https://images.contentful.com/alneenqid6w5/5dJybcC7bLKUDnhP2r6ezx/3497411cbf0f85ec694c6cc0cfda602f/image.png)
 
 ## O que mudou?
 Antes, uma promoção era ativada automaticamente quando salva com o status **Ativa**. Com o novo recurso, você pode visualizar um resumo das configurações definidas antes de ativar uma nova promoção. Assim, é possível verificar se os dados da promoção estão corretos, evitando erros de implementação.
diff --git a/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 158752503..01cbafc1f 100644
--- a/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -25,7 +25,7 @@ O aplicativo está disponível na [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Possibilita moderar as avaliações: aprovar as avaliações de produtos antes de serem disponibilizadas na página do produto;
 - Permite que você configure a sua loja para habilitar avaliações anônimas.
 
-![Reviews and Ratings - Printscreen](//images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
+![Reviews and Ratings - Printscreen](https://images.ctfassets.net/alneenqid6w5/2WZ7g7iF3goyERWcguegBV/6b79887b72f793cd2f600e8a1505de8a/Screen_Shot_2020-12-07_at_15.52.05.png)
 
 ## Quais os benefícios?
 - Permite que o seu consumidor faça compras com mais confiança e assertividade baseando-se em avaliações de outros usuários;
diff --git a/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 8737ffbce..41397822a 100644
--- a/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -39,7 +39,7 @@ Para fazer isso é necessário adicionar um produto chamado `Order Authorization
  6. Escolha o tipo de permissão desejada: `Save Configuration`, para permitir que o usuário edite e salve modificações, ou `View Configuration`, para permitir a visualização da página de Autorização de Pedidos.
  7. Clique em **Salvar**
 
-![GIT-OrderAutho](//images.ctfassets.net/alneenqid6w5/4jnwsJuKbMW7YMt6g3Jhfp/19219d84c921d287462551b1b5ddbd00/GIT-OrderAutho.gif)
+![GIT-OrderAutho](https://images.ctfassets.net/alneenqid6w5/4jnwsJuKbMW7YMt6g3Jhfp/19219d84c921d287462551b1b5ddbd00/GIT-OrderAutho.gif)
 
 Após adicionar este novo produto a um perfil, certifique-se de que os usuários desejados estão associados a este perfil de acesso.
   
diff --git a/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
index d224d66d6..4cd2080e8 100644
--- a/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'A nova seção do Admin VTEX para encontrar parceiros,
 
 Hub de Extensões é a nova seção do Admin VTEX que reúne desenvolvedores parceiros e merchants que querem estender as funcionalidades da sua operação. Pelo Hub de Extensões, parceiros podem publicar suas extensões e merchants podem visualizar, comprar, instalar e gerenciar extensões. O Hub de Extensões estará disponível globalmente em todas as lojas VTEX durante o terceiro trimestre (Q3) de 2023. Caso você queira habilitar o Hub de Extensões na sua loja imediatamente, você pode fazer o pedido [abrindo um ticket para o nosso suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-![Extensions Hub GIF](//images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e5d1491570f8676841390e1899c54250/Extensions_Hub.gif)
+![Extensions Hub GIF](https://images.ctfassets.net/alneenqid6w5/2J9kCcwWYl36mQjphjpoOv/e5d1491570f8676841390e1899c54250/Extensions_Hub.gif)
 
 ## O que mudou?
 
@@ -49,7 +49,7 @@ O [site Portal de Parceiros](https://partnerportal.vtex.com/) continuará existi
 
 O Hub de Extensões estará disponível para todas as lojas a partir do terceiro trimestre (Q3) de 2023. Caso você queira habilitar o Hub de Extensões na sua loja imediatamente, você pode fazer o pedido [abrindo um ticket para o nosso suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). Em seguida, para começar a utilizar o Hub de Extensões, basta acessá-lo no Admin da sua loja. No painel lateral esquerdo do Admin VTEX, clique no ícone **Extensões** e o Hub de Extensões estará visível na parte superior do menu.
 
-![Extensions Hub painel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
+![Extensions Hub painel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/facebook-and-google-login-settings-have-changed.md b/docs/announcements/pt/facebook-and-google-login-settings-have-changed.md
index ff20d054c..79076ea32 100644
--- a/docs/announcements/pt/facebook-and-google-login-settings-have-changed.md
+++ b/docs/announcements/pt/facebook-and-google-login-settings-have-changed.md
@@ -21,7 +21,7 @@ A flag __Usar chaves VTEX__, que antes ativava o uso de dados fornecidos pela VT
 
 Isto significa que o fluxo foi corrigido e não é mais possível usar as chaves da VTEX para login com Facebook e Google. Agora o lojista precisa configurar suas próprias chaves.
 
-![login2](//images.contentful.com/alneenqid6w5/8ctzWCGmeAuay68eyk888/630cfc3d79ef248f06ca47575556738c/login2.png)
+![login2](https://images.contentful.com/alneenqid6w5/8ctzWCGmeAuay68eyk888/630cfc3d79ef248f06ca47575556738c/login2.png)
 
 Para saber como fazer isso, leia os artigos do Help VTEX:
 
diff --git a/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
index bee0fba4a..bd58a9afb 100644
--- a/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
+++ b/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -18,7 +18,7 @@ announcementSynopsisPT: 'Apresentamos o FastCheckout: inovação em checkout par
 
 Com o compromisso contínuo de inovar e a entregar excelência aos nossos clientes, a VTEX apresenta o **FastCheckout**, a mais recente evolução em nosso checkout. A nova solução permite criar experiências de checkout personalizadas com alta conversão, sempre atualizadas com novas funcionalidades.
 
-![fastcheckout](//images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/4e751e1a0b31e6e68d6f9053f0451ecd/image.png)
+![fastcheckout](https://images.ctfassets.net/alneenqid6w5/42O8ebq6UcdyuSyvUukhM/4e751e1a0b31e6e68d6f9053f0451ecd/image.png)
 
 ## O que mudou?
 
@@ -57,7 +57,7 @@ Proporcionamos a liberdade de incluir elementos completamente customizados, sem
 
 O novo fluxo de compra no FastCheckout é projetado para ser dinâmico e intuitivo, para oferecer aos seus clientes uma experiência de compra mais fluida e simplificada. Com etapas claramente definidas e uma navegação intuitiva, tornamos o processo de checkout mais eficiente.
 
-![GIFCheckout](//images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/27979c72da22a010d210379d502dab88/GIFCheckout.gif)
+![GIFCheckout](https://images.ctfassets.net/alneenqid6w5/3BruRej7wHet2sTobFDLBD/27979c72da22a010d210379d502dab88/GIFCheckout.gif)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md b/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md
index 9208a85e0..700fed0bc 100644
--- a/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md
+++ b/docs/announcements/pt/gain-speed-and-practicality-with-the-updated-price-table-feature.md
@@ -21,7 +21,7 @@ Agora é possível criar Tabelas de Preços de forma mais intuitiva, prática e
 
 Antes, para criar uma tabela de preços, era necessário ir até o filtro do módulo de Preços e digitar o nome da tabela a ser criada. Agora, adicionamos um novo botão __Tabelas de Preços__ que permite criar e selecionar as tabelas de preço que você deseja visualizar.
 
-![Annoucement Price table PT](//images.ctfassets.net/alneenqid6w5/22qst5crxgQq0Mdih3XgnK/93c3034eabe8c139143bcb2fc92ec35f/Annoucement_Price_table_PT.png)
+![Annoucement Price table PT](https://images.ctfassets.net/alneenqid6w5/22qst5crxgQq0Mdih3XgnK/93c3034eabe8c139143bcb2fc92ec35f/Annoucement_Price_table_PT.png)
 
 ## Vantagens
 
diff --git a/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md b/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md
index 3350ffdbc..482b64c63 100644
--- a/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md
+++ b/docs/announcements/pt/get-to-know-the-new-vtex-status-page.md
@@ -23,7 +23,7 @@ Anteriormente, enfrentamos desafios ao categorizar incidentes em apenas quatro c
 
 Agora, apresentamos 18 componentes mais específicos agrupados em quatro categorias – Storefront, Checkout, Admin e Developer Tools – com foco não apenas em nossa arquitetura interna, mas principalmente em onde os sintomas podem ser observados por lojistas. A imagem a seguir apresenta todos os componentes exibidos na nova página:
 
-![status-page-vtex](//images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/08f9ab11d14629a3f6e534268be71b06/status-page-vtex.png)
+![status-page-vtex](https://images.ctfassets.net/alneenqid6w5/7s1xozhZ4Kih3e9Atsuq6a/08f9ab11d14629a3f6e534268be71b06/status-page-vtex.png)
 
 Confira o artigo [Página de status da VTEX](https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ) para mais informações sobre cada componente.
 
diff --git a/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md b/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
index 0d7524d20..09c211d4c 100644
--- a/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
+++ b/docs/announcements/pt/get-your-store-ready-for-black-friday-with-our-best-practices-guide.md
@@ -21,4 +21,4 @@ Como fazemos todos os anos, criamos uma cartilha com recomendações e dicas exc
 
 Disponível para clientes e parceiros VTEX, o guia pode ser acessado pela homepage do seu Admin ou diretamente pela URL `https://{AccountName}.myvtex.com/admin/blackfriday`. Basta substituir `{AccountName}` pelo Account Name da sua loja.
 
-![Announcement Cartilha BF](//images.ctfassets.net/alneenqid6w5/etqQlJKljisiesmY8kUYS/c45814633c167f8af372df7ec75749ab/Announcement_Cartilha_BF.png)
+![Announcement Cartilha BF](https://images.ctfassets.net/alneenqid6w5/etqQlJKljisiesmY8kUYS/c45814633c167f8af372df7ec75749ab/Announcement_Cartilha_BF.png)
diff --git a/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md b/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
index 4c9e321aa..d718adc30 100644
--- a/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
+++ b/docs/announcements/pt/get-your-store-ready-for-shopping-season-with-our-best-practices-guide-2022.md
@@ -27,4 +27,4 @@ https://{AccountName}.myvtex.com/admin/shopping-season
 
 Basta substituir `{AccountName}` pelo Account Name da sua loja, como na imagem abaixo.
 
-![Shopping Season Guidelines - 2022 - PT](//images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/55de9dc55b06266326e99aa3d0b89836/Screen_Shot_2022-10-19_at_18.15.20.png)
+![Shopping Season Guidelines - 2022 - PT](https://images.ctfassets.net/alneenqid6w5/3vmyW3BipNCRN698zQdRVQ/55de9dc55b06266326e99aa3d0b89836/Screen_Shot_2022-10-19_at_18.15.20.png)
diff --git a/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md b/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md
index 3518de750..cd1b33301 100644
--- a/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md
+++ b/docs/announcements/pt/google-pay-new-payment-method-available-on-vtex.md
@@ -27,7 +27,7 @@ O Google Pay é uma plataforma de carteira digital e um sistema de pagamento onl
 
 A partir de agora, você pode adicionar o Google Pay como meio de pagamento na sua loja, proporcionando aos seus clientes um processo de checkout mais ágil e conveniente.
 
-![google-pay-checkout-pt](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/1e5184005b2c0a2098589a1abffb9e72/image.png)
+![google-pay-checkout-pt](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/1e5184005b2c0a2098589a1abffb9e72/image.png)
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md b/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
index 34cc1fb19..367562790 100644
--- a/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
+++ b/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
@@ -27,13 +27,13 @@ Anteriormente, no cadastro da [integração com o Google Shopping](https://help.
   A configuração <b>Aplicar desconto no preço enviado</b> está disponível somente para lojas VTEX Brasil.
 </div>
 
-![envio-de-precos-google-pt](//images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/309246aab10954d984d851b58442a4ef/envio-de-precos-google-pt.png)
+![envio-de-precos-google-pt](https://images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/309246aab10954d984d851b58442a4ef/envio-de-precos-google-pt.png)
 
 ## O que precisa ser feito?
 
 A atualização estará disponível para todas as [contas VTEX que atuam como seller](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex) a partir de 14 de dezembro de 2023. 
 Para contas que ainda não utilizam a integração com o Google Shopping e desejam ativar as configurações **Enviar preço base (para preços com desconto)** e **Aplicar desconto no preço enviado**, siga [esta trilha](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG) para começar a utilizar as novas configurações. Para contas já integradas com o Google Shopping e com a configuração **Considerar desconto para pagamento com boleto no preço enviado** ativa, após a atualização a configuração correspondente **Aplicar desconto no preço enviado** já estará ativa conforme imagem abaixo:  
 
-![fluxo-update-news-google](//images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/9f4ee800552c105e69dae21676a58b31/fluxo-update-news-google.png)  
+![fluxo-update-news-google](https://images.ctfassets.net/alneenqid6w5/3JvNH6bvMe4warWK5aOrNv/9f4ee800552c105e69dae21676a58b31/fluxo-update-news-google.png)  
 
 Confira a documentação e saiba como [Configurar desconto vinculado ao meio de pagamento](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/3AqbcsWrge8zLt0BC5CtGd#desconto-vinculado-ao-metodo-de-pagamento) e como [Configurar o desconto no conector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
diff --git a/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md b/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md
index 39f8cce0a..0648cb342 100644
--- a/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md
+++ b/docs/announcements/pt/headless-cms-create-non-duplicatable-pages.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Conheça o Singleton: tipo de content type no Headless
 
 O Singleton é um novo tipo de content type que permite comerciantes criar e gerenciar uma única página de um content type no Headless CMS. Content types do tipoSingleton não podem ser duplicados. Isto garanteque haja apenas uma página daquele content type e que o conteúdo seja consistente em toda a loja.
 
-![singleton-br](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
+![singleton-br](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 O content type Singleton está disponível apenas para lojas usando o <a href="https://help.vtex.com/pt/tutorial/managing-pages-beta--3DO6rBhZ1p3zndnFu5BgRt">VTEX Headless CMS</a> (Atualmente está em fase Beta).
diff --git a/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md b/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md
index f43d6322a..6d85e345e 100644
--- a/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md
+++ b/docs/announcements/pt/headless-cms-deeper-insights-into-page-publication-status.md
@@ -19,7 +19,7 @@ A partir de 01 de novembro de 2023, o status **Publicando** em Páginas no Headl
 
 Quando uma nova página é criada, ela recebe o status de **Rascunho**, indicando que ainda não foi feito o deploy. Após o deploy da página, o status é atualizado para **Publicado**, o que significa que o processo de compilação (build) poderá ser iniciado. Após a conclusão da compilação, a página ficará disponível para os usuários finais.
 
-![Build Status - PT](//images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/3b495e096d368969817a01eaea027f08/publishing-status-pt.gif)
+![Build Status - PT](https://images.ctfassets.net/alneenqid6w5/4oOFiKgKpuTVaBics5MaI0/3b495e096d368969817a01eaea027f08/publishing-status-pt.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md b/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md
index 43f5443e8..353373bf1 100644
--- a/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md
+++ b/docs/announcements/pt/headless-cms-simplify-content-creation-and-management-with-projects.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Headless CMS - Gerencie seus projetos de forma centrali
 
 **Projetos** é a nova funcionalidade do Headless CMS que simplifica o gerenciamento de diversas experiências digitais, como aplicativos móveis, sites e email marketing em uma única tela.
 
-![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c5a1f1ba3077c11504d9f78c1712c59e/projects-two-pt.png)
+![Projects overview](https://images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c5a1f1ba3077c11504d9f78c1712c59e/projects-two-pt.png)
 
 Com ele, você pode personalizar as configurações, o conteúdo e a marca de cada projeto para públicos ou objetivos específicos.
 
@@ -26,7 +26,7 @@ Antes, para lidar com diferentes projetos com diferentes públicos-alvo ou solu
 
 Agora, a interface de **Projetos** permite que você gerencie todos os seus projetos a partir de uma experiência centralizada, além de permitir que você navegue entre os projetos facilmente, edite as configurações, o conteúdo e a identidade em um só lugar. Essa melhoria aumenta sua capacidade de se adaptar, atendendo diferentes públicos e objetivos.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
 
 ## Por que fizemos essa mudança?
 Com a interface de **Projetos**, você poderá:
diff --git a/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md b/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md
index 9d660dd04..d332244f7 100644
--- a/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md
+++ b/docs/announcements/pt/headless-cms-stay-informed-on-your-publication-progress.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: ' Mantenha-se informado sobre as etapas de publicação
 
 O Headless CMS agora conta com uma funcionalidade de notificação que mantém você informado durante cada etapa do processo de publicação. As novas notificações fornecem atualizações sobre cada estágio de uma publicação no VTEX Headless CMS, mantendo os usuários informados sobre os estágios de compilação (build) da publicação em Lançamentos, VTEX Headless CMS e FastStore. 
 
-![Headless CMS - Notificações](//images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/faec3fe558ef0b94048f83cefd6a5106/headless-cms-publish-pt.gif)
+![Headless CMS - Notificações](https://images.ctfassets.net/alneenqid6w5/3snUhFhKzrzE71wg5GJRws/faec3fe558ef0b94048f83cefd6a5106/headless-cms-publish-pt.gif)
 
 Essa funcionalidade também permite identificar e relatar erros durante o deploy, indicando o estágio exato do erro. Além de oferecer a opção de refazer os deploys, se necessário.
 
@@ -35,7 +35,7 @@ Com esta funcionalidade, agora você pode acompanhar o status de cada estágio d
 
 Caso ocorra um erro durante a implementação, a notificação indicará o estágio em que se deu o erro. Você pode clicar em `Tentar novamente` para refazer o deploy.
 
-![Headless CMS - Novo deploy](//images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/b9ce5d741d88aa05661c2e592b9cf550/headless-cms-redeploy-pt.gif)
+![Headless CMS - Novo deploy](https://images.ctfassets.net/alneenqid6w5/wxnKpmFM0GRlSAB7uboMK/b9ce5d741d88aa05661c2e592b9cf550/headless-cms-redeploy-pt.gif)
 
 ## Por que fizemos essa mudança?
 A funcionalidade de notificação permite que você tenha maior autonomia para entender e resolver os problemas relacionados às publicações da loja, possibilitando identificá-los e relatá-los com precisão, além de repetir o processo de publicação.
diff --git a/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md b/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md
index 96574029b..cfcc9b4a7 100644
--- a/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md
+++ b/docs/announcements/pt/improvement-of-discount-price-viewing-experience.md
@@ -24,16 +24,16 @@ Antes desta mudança, era possível ocorrer erros de visualização no resumo do
 Considere, por exemplo, um usuário que vê um produto que custa R$ 600,00, elegível para um desconto de 10% em caso de pagamento à vista. A pessoa procede para o checkout e chega à página do resumo do pedido, na qual deverá selecionar as opções de pagamento. Estes são os três erros principais que poderiam ocorrer:
 
 - O usuário ainda não selecionou um número de parcelas e o preço é exibido sem descontos, mesmo na opção elegível.
-![O usuário ainda não selecionou um número de parcelas](//images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
+![O usuário ainda não selecionou um número de parcelas](https://images.ctfassets.net/alneenqid6w5/4dFdvU6HcZGvBWSpr0VI04/fe470a5050d3c66d98b21d978f968036/image6.png)
 
 - O usuário selecionou um número de parcelas não elegível para desconto e o preço é exibido sem descontos, mesmo na opção elegível (à vista).
-![O usuário selecionou um número de parcelas não elegível para desconto](//images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
+![O usuário selecionou um número de parcelas não elegível para desconto](https://images.ctfassets.net/alneenqid6w5/nY13uDOX3JBOJvCN5Oj2i/d931d2d73ffb7f1b8c8ddbf7310b7bc9/image8.png)
 
 - O usuário selecionou um número de parcelas elegível (à vista) para desconto e o desconto é exibido mesmo em opções não elegíveis.
-![O usuário selecionou um número de parcelas elegível para desconto (à vista)](//images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
+![O usuário selecionou um número de parcelas elegível para desconto (à vista)](https://images.ctfassets.net/alneenqid6w5/3hRThIcKzoGWirn17UIXqV/bd64d486417ca73e2d510fc03e4ddd05/image2.png)
 
 Com essa mudança, o desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.
-![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](//images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
+![O desconto será sempre exibido corretamente apenas nas opções de parcelamento elegíveis.](https://images.ctfassets.net/alneenqid6w5/XBFP0W5B1wlGwpoz3In3W/99a531d3dbd3eeae102536126c849212/image4.png)
 
 ## Por que realizamos essa mudança?
 
diff --git a/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md b/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md
index ff54522d5..24cbf885b 100644
--- a/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md
+++ b/docs/announcements/pt/improvements-in-exporting-prices-via-spreadsheet.md
@@ -25,7 +25,7 @@ Na VTEX, é possível alterar o preço várias vezes ao dia de acordo com a estr
 
 O cadastro via planilha se dá por duas etapas, a exportação e importação. A exportação dos preços teve sua experiência aprimorada com novas features, buscando dar mais visibilidade ao usuário do status de cada planilha de exportação de preços.
 
-![exportacao pt](//images.ctfassets.net/alneenqid6w5/3yLQbrPd39kTWYnNrsbJgC/fbf24da5553dee1c5bc0ba5a51e2f070/exportacao_pt.gif)
+![exportacao pt](https://images.ctfassets.net/alneenqid6w5/3yLQbrPd39kTWYnNrsbJgC/fbf24da5553dee1c5bc0ba5a51e2f070/exportacao_pt.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md b/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md
index 60a9b011e..aac2cb2ce 100644
--- a/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md
+++ b/docs/announcements/pt/improvements-to-unified-search-in-vtex-sales-app.md
@@ -32,7 +32,7 @@ Com a nova melhoria, você encontrará mudanças que visam melhorar sua experiê
 
 - **Otimização para conexões lentas:** com o uso de caches do navegador, a busca retornará novas informações apenas quando necessário, garantindo uma resposta rápida mesmo em cenários de conexão lenta.
 
-![Mobile - PT](//images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/9d6c3d38f68b7ddbca623b0cf4b2067a/mobile__1_.gif)
+![Mobile - PT](https://images.ctfassets.net/alneenqid6w5/2wdRQcrdDW1OKapj13T6Lq/9d6c3d38f68b7ddbca623b0cf4b2067a/mobile__1_.gif)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md b/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md
index 98bb3b6ee..4579b561d 100644
--- a/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md
+++ b/docs/announcements/pt/increase-your-sales-with-a-new-order-authorization-screen.md
@@ -22,7 +22,7 @@ Esta ferramenta permite o controle das aprovações de pedidos com mudanças em
 ## O que muda
 Agora, ao invés de abrir um chamado diretamente com o suporte, é possível configurar as regras de autorização pelo admin. Para isso, acesse o caminho: Menu - Gerenciamento de Pedidos - Autorização de Pedidos.
 
-![Print Tela Principal OrderAuthorization (2)](//images.ctfassets.net/alneenqid6w5/3hRybooCq6ynxWhOBN2J6C/58182a66426ecd5d480c9a79a5f8a9e7/Print_Tela_Principal_OrderAuthorization__2_.jpg)
+![Print Tela Principal OrderAuthorization (2)](https://images.ctfassets.net/alneenqid6w5/3hRybooCq6ynxWhOBN2J6C/58182a66426ecd5d480c9a79a5f8a9e7/Print_Tela_Principal_OrderAuthorization__2_.jpg)
 
 ## O que você precisa fazer
 Importante mencionar que a loja não perde as regras configuradas através do fluxo antigo, que era feito abrindo chamado para a equipe de suporte. Elas serão atualizadas automaticamente na nova tela.
diff --git a/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
index 7f2951423..11133d20b 100644
--- a/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
@@ -19,7 +19,7 @@ A partir de 31 de maio, estamos lançando para todas as lojas VTEX a versão bet
 
 As páginas da **Estratégia de envio** foram atualizadas para o novo design system da VTEX, como pode ser visto a seguir:
 
-![nova_estrategia_envio_announcement_boards_PT](//images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/b93bbe35c2870827dd761f244cb447dc/nova_estrategia_envio_announcement_boards_PT.png)
+![nova_estrategia_envio_announcement_boards_PT](https://images.ctfassets.net/alneenqid6w5/7gWgtAG6jo0wXjKCUKYGnj/b93bbe35c2870827dd761f244cb447dc/nova_estrategia_envio_announcement_boards_PT.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/introducing-vtex-ad-network-beta.md b/docs/announcements/pt/introducing-vtex-ad-network-beta.md
index d913ffe63..1f050ab75 100644
--- a/docs/announcements/pt/introducing-vtex-ad-network-beta.md
+++ b/docs/announcements/pt/introducing-vtex-ad-network-beta.md
@@ -23,7 +23,7 @@ Anunciantes podem [criar campanhas](https://help.vtex.com/pt/tutorial/anunciando
 
 Ao criar campanhas para um produto da sua marca, seu anúncio poderá aparecer em espaços de destaque em diversas lojas VTEX que já possuem aquele produto em seu catálogo.
 
-![vtex_ad_network_admin_PT](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/c479a1adcfce1ab838edfa17aeb6aca7/vtex_ad_network_admin.png)
+![vtex_ad_network_admin_PT](https://images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/c479a1adcfce1ab838edfa17aeb6aca7/vtex_ad_network_admin.png)
 
 ## Lojas
 
@@ -31,7 +31,7 @@ Podem disponibilizar espaço publicitário para que anunciantes promovam seus pr
 
 A VTEX selecionará para a sua loja anúncios de produtos que já compõem o seu catálogo, garantindo uma jornada de compra fluida e sem quebras. Esta seleção é feita com base no contexto de navegação dos clientes da sua loja.
 
-![vtex_ad_network_sponsored_PT](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_PT](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md b/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
index 8fa08abd8..40a3f179a 100644
--- a/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
+++ b/docs/announcements/pt/ip-and-geolocation-info-is-now-provided-in-emails-containing-access-code-requests.md
@@ -28,4 +28,4 @@ Ao tentar acessar o Admin de uma loja usando um endereço de email, você tem a
 
 Segurança é uma das principais preocupações na VTEX, e isso se torna ainda mais importante quando estamos próximos de grandes eventos como a Black Friday. Esse novo recurso pode ajudar a identificar a fonte de uma tentativa de acesso indesejado.
 
-![IP Geolocation email - PT](//images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/0f65303dae22ac38b6f66e1942830224/IP_Geolocation_email_-_PT.png)
+![IP Geolocation email - PT](https://images.ctfassets.net/alneenqid6w5/2lDMP34wKY5qrn4TtIPvKr/0f65303dae22ac38b6f66e1942830224/IP_Geolocation_email_-_PT.png)
diff --git a/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
index 0e8f94c4e..269072861 100644
--- a/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
+++ b/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Lançamento global do lead time, uma configuração opc
 
 A VTEX disponibilizou para todas as lojas o [lead time](https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B), uma configuração do tempo de envio do SKU de um estoque. Ou seja, você pode definir a nível de SKU um tempo de envio adicional no cálculo das promessas de envio apresentadas para os clientes no checkout.
 
-![lead_time_image_total_time_PT](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
+![lead_time_image_total_time_PT](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
 
 O uso do lead time é opcional e, quando não configurado, o envio de pedidos da loja segue inalterado. Vale ressaltar que as regras de consolidação do checkout se mantêm, calculando o prazo de envio total do pedido pelo maior tempo de um dos itens.
 
@@ -31,7 +31,7 @@ Antes, o [cálculo de envio](https://help.vtex.com/pt/tutorial/como-funciona-o-c
 
 Agora, existe também a opção de configurar o tempo de envio a nível de SKU, com a nova coluna do lead time na página [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-inventario--tutorials_139), que se encontra no seu Admin VTEX, em **Catálogo > Estoque > Gerenciamento de inventário**, como na imagem abaixo:
 
-![lead_time_inventory_management_PT](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
+![lead_time_inventory_management_PT](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
 
 <div class="alert alert-warning">
 Pelo Admin VTEX, o lead time é configurado em dias, até o limite de 365 dias. Por padrão, os dias são contados em dias úteis, mas você pode configurar sua política de envio para que a <a href="https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional">contagem seja feita em dias corridos</a>. Para configurar períodos em horas, minutos e segundos, é necessário utilizar o endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
diff --git a/docs/announcements/pt/live-shopping-the-vtex-app-to-broadcast-live-events.md b/docs/announcements/pt/live-shopping-the-vtex-app-to-broadcast-live-events.md
index 6ac956ffb..ca06356c9 100644
--- a/docs/announcements/pt/live-shopping-the-vtex-app-to-broadcast-live-events.md
+++ b/docs/announcements/pt/live-shopping-the-vtex-app-to-broadcast-live-events.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'O aplicativo permite que as lojas façam transmissões
 
 O aplicativo Live Shopping é responsável por revolucionar o seu relacionamento com os clientes. Com ele, você pode realizar transmissões ao vivo no site de sua loja para promover coleções de produtos, aumentar as vendas e melhorar a experiência do usuário de forma simultânea e em tempo real.
 
-![VTEX Live Shopping App](//images.contentful.com/alneenqid6w5/laSpBi1YPl54TxoSam7M7/6c377e4f93f45175ceda43a5629d8420/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
+![VTEX Live Shopping App](https://images.contentful.com/alneenqid6w5/laSpBi1YPl54TxoSam7M7/6c377e4f93f45175ceda43a5629d8420/-Official_Sales_Deck-_VTEX_Live_Shopping_App.png)
 
 O aplicativo está disponível na [VTEX App Store](https://apps.vtex.com/) e pode ser baixado por um preço de assinatura acessível por todas as lojas em VTEX IO e Legado.
 
@@ -42,7 +42,7 @@ No Admin, ele permite:
 - Estabelecer uma lista de palavras proibidas que serão bloqueadas no bate-papo em tempo real;
 - Disponibilizar enquetes e testes aos usuários.
 
-![live-shopping-event-details-pt](//images.contentful.com/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/f93c9f80c325cbdb319f4a6a03968b20/image4.png)
+![live-shopping-event-details-pt](https://images.contentful.com/alneenqid6w5/3S1LlDHlh3P3VAZzLEgMOl/f93c9f80c325cbdb319f4a6a03968b20/image4.png)
 
 ## Quais são as vantagens de usar o app?
 
diff --git a/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
index 85ebca27a..1fb9ab0de 100644
--- a/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
+++ b/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -25,7 +25,7 @@ A partir de agora, o algoritmo de Luhn será aplicado para assegurar que somente
 
 Caso um cliente digite um número incorreto, uma mensagem de erro será exibida no Checkout. Nesta situação, o cliente deverá verificar o número inserido e corrigí-lo para prosseguir com a finalização da compra.
 
-![algoritmo_luhn_pt](//images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/2ab586ebecb172fa058c7daffdb5833d/algoritmo_luhn_pt.PNG)
+![algoritmo_luhn_pt](https://images.ctfassets.net/alneenqid6w5/5HN1Iu9vKUmeglMLOV46Rd/2ab586ebecb172fa058c7daffdb5833d/algoritmo_luhn_pt.PNG)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/marketplace-improvements-on-received-skus.md b/docs/announcements/pt/marketplace-improvements-on-received-skus.md
index 2ab2c0a94..42483522b 100644
--- a/docs/announcements/pt/marketplace-improvements-on-received-skus.md
+++ b/docs/announcements/pt/marketplace-improvements-on-received-skus.md
@@ -29,7 +29,7 @@ Vale notar que essa ação pode ser desfeita. É possível aprovar um SKU bloque
 
 Não é preciso realizar nenhuma configuração para ativar essa funcionalidade, ela será instalada de forma automática na plataforma VTEX. Para saber mais sobre o bloqueio de SKUs, no painel do módulo SKUs recebidos, confira nosso artigo sobre [Catalogação manual de SKUs](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus--tutorials_396).
 
-![PT SKUs Recebidos Announcement](//images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/b6d7724cfd093568a02012b5fdd14afe/PT_SKUs_Recebidos_Announcement.jpg)
+![PT SKUs Recebidos Announcement](https://images.ctfassets.net/alneenqid6w5/5UdF6jOSwSvqYQIng9w7mS/b6d7724cfd093568a02012b5fdd14afe/PT_SKUs_Recebidos_Announcement.jpg)
 
 ## Configurações de aprovação automática de SKUs
 
diff --git a/docs/announcements/pt/marketplace-network-has-been-improved.md b/docs/announcements/pt/marketplace-network-has-been-improved.md
index 8137a45d6..8668ee33e 100644
--- a/docs/announcements/pt/marketplace-network-has-been-improved.md
+++ b/docs/announcements/pt/marketplace-network-has-been-improved.md
@@ -19,7 +19,7 @@ Para marketplaces e sellers do nosso ecossistema, um dos maiores desafios é con
 
 O Marketplace Network foi redesenhado para melhorar sua experiência. Além disso, não é mais preciso baixar a app em nossa App Store, a funcionalidade foi inserida em todas as lojas que atuam como sellers ou marketplaces automaticamente.
 
-![Marketplace network tour](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
+![Marketplace network tour](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
 
 ## O que mudou?
 As páginas do Marketplace Network passaram por algumas mudanças:
diff --git a/docs/announcements/pt/marketplace-new-offer-quality-filters.md b/docs/announcements/pt/marketplace-new-offer-quality-filters.md
index 9b93f7349..c42668c02 100644
--- a/docs/announcements/pt/marketplace-new-offer-quality-filters.md
+++ b/docs/announcements/pt/marketplace-new-offer-quality-filters.md
@@ -21,7 +21,7 @@ Para que marketplaces tenham mais controle sobre os critérios de aprovação de
 
 Dessa forma, os SKUs que chegam até o marketplace já estão de acordo com os requisitos que importam na curadoria de seu catálogo. 
 
-![Offer Quality gif](//images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/4311d5d111ba8d0f8f92a586dd833eef/Offer_Quality_01.gif)
+![Offer Quality gif](https://images.ctfassets.net/alneenqid6w5/2TsdhoMwl0Fmwp8WBoViXw/4311d5d111ba8d0f8f92a586dd833eef/Offer_Quality_01.gif)
 
 ## O que mudou? 
 
diff --git a/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md b/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md
index e774e5706..d2eed2141 100644
--- a/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md
+++ b/docs/announcements/pt/marketplace-new-sidebar-with-received-sku-details.md
@@ -24,7 +24,7 @@ Até então, para conferir as informações de um SKU recebido era preciso acess
 
 A barra contém  imagens do SKU, preço, nível de estoque, além de outros atributos do produto, como descrição, especificações, códigos e IDs. Também inclui a porcentagem de equivalência que o SKU recebeu pelo [matcher](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt) instalado em sua loja. Ainda é possível acessar a página completa de detalhes do SKU, clicando no botão *Ver página de detalhes*. 
 
-![Sidebar received](//images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/6ea0f2c2f6403f60b7ca96418da7f04e/Sidebar_received.gif)
+![Sidebar received](https://images.ctfassets.net/alneenqid6w5/5weIxQqzG0wxPTsWu61XOI/6ea0f2c2f6403f60b7ca96418da7f04e/Sidebar_received.gif)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md b/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md
index d1b706a79..f3f02e18e 100644
--- a/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md
+++ b/docs/announcements/pt/marketplacenetwork-and-integrations-are-now-a-single-page.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Unificamos o Marketplace Network e o módulo de Integra
 
 Para centralizar as oportunidades de conexão com marketplaces VTEX e marketplaces externos, unificamos as páginas de Integrações e Marketplace Network, chamando-se agora __Marketplaces e Integrações__. A atualização estará disponível em todas as contas VTEX a partir do dia 03 de maio de 2023. 
 
-![Marketplace e integrações](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png)
+![Marketplace e integrações](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png)
 
 ## O que mudou?  
 
diff --git a/docs/announcements/pt/marketplaces-received-skus-beta.md b/docs/announcements/pt/marketplaces-received-skus-beta.md
index 46f9015ca..310b7453d 100644
--- a/docs/announcements/pt/marketplaces-received-skus-beta.md
+++ b/docs/announcements/pt/marketplaces-received-skus-beta.md
@@ -25,7 +25,7 @@ A versão beta está aberta para todos que quiserem testar e é só a primeira d
 
 Uma das principais melhorias é a nova forma de selecionar SKUs em massa. Assim, você pode aprovar ou rejeitar todos eles de uma só vez. Alinhado com nosso [Styleguide](https://styleguide.vtex.com/ "Styleguide"), a seleção em massa vai trazer ainda mais agilidade e eficiência para o seu trabalho.
 
-![received-skus-bulk](//images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
+![received-skus-bulk](https://images.ctfassets.net/alneenqid6w5/5AoUTuM27q7LhWOOIzbPtT/26c63e97b66a252e570cadf36a8356f2/received-skus-bulk.gif)
 
 
 
@@ -33,13 +33,13 @@ Uma das principais melhorias é a nova forma de selecionar SKUs em massa. Assim,
 Um dos desafios de gerenciar itens de múltiplos sellers é priorizar uma lista que nunca acaba. Para ajudar, construímos uma nova funcionalidade de ordenação, para você reordenar tudo o que foi enviado por preço e - uma das principais melhorias - por disponibilidade de estoque. Visualize com facilidade quantos itens estão disponíveis e aprove os SKUs que vão performar melhor.
 
 
-![received-skus-ordering](//images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
+![received-skus-ordering](https://images.ctfassets.net/alneenqid6w5/2CxfuYmpmVhaTJxyGEphpl/017bd6730f3de0408c056266ec5fad4f/received-skus-ordering.gif)
 
 
 Tudo isso é potencializado com os novos filtros. Veja e filtre SKUs por categoria, marca e seller de forma simples e intuitiva.
 
 
-![received-skus-filtering](//images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
+![received-skus-filtering](https://images.ctfassets.net/alneenqid6w5/5dK6UorOok8kH86Ueek7UF/0e572dcadf65e72132d3d41a499a8726/received-skus-filtering.gif)
 
 
 
diff --git a/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md b/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md
index 6629b6e0a..0857fe182 100644
--- a/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md
+++ b/docs/announcements/pt/master-data-v1-dynamic-settings-deprecation.md
@@ -33,7 +33,7 @@ O **Campo calculado** era uma configuração dentro dos campos de [entidade de d
 
 Esse tipo de campo, ilustrado abaixo, não estará mais disponível a partir de 17 de junho de 2024. Os campos calculados criados previamente deixarão de funcionar na mesma data.
 
-![md-deprecation-calculated-field-pt](//images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/e25fa67f6207592c2893b3f86132c057/md-deprecation-calculated-field-pt.png)
+![md-deprecation-calculated-field-pt](https://images.ctfassets.net/alneenqid6w5/13NWpWtxQGLFfh0ecW4ZV6/e25fa67f6207592c2893b3f86132c057/md-deprecation-calculated-field-pt.png)
 
 ### Alterar valor do campo
 
@@ -41,7 +41,7 @@ Ao configurar ações de triggers na aba **Ativação**, havia a opção de **Al
 
 A opção **Alterar valor do campo**, ilustrada abaixo, não estará mais disponível ao configurar ações de triggers a partir de 17 de junho de 2024. Os triggers criados anteriormente com essa ação continuarão funcionando somente até essa data.
 
-![md-deprecation-trigger-pt](//images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/267ad58ad21c7ba83b7182d3bc4c581b/md-deprecation-trigger-pt.png)
+![md-deprecation-trigger-pt](https://images.ctfassets.net/alneenqid6w5/2meuBC8t6dnVAfg1YzZnwL/267ad58ad21c7ba83b7182d3bc4c581b/md-deprecation-trigger-pt.png)
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md
index 9ae9864ab..42f6ed366 100644
--- a/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md
@@ -33,7 +33,7 @@ Você tem duas maneiras pelas quais pode alcançar o mesmo efeito da promoção
 
 Você pode configurar uma [Promoção Regular](/pt/tutorial/promocao-regular) com o tipo de desconto __Preço Máximo por Item__.
 
-![PrecoMaximo](//images.contentful.com/alneenqid6w5/1lv90zHrOIk0mwqcumEGkE/6e3b7b7cf7a678c003ad0497b2b2629f/PrecoMaximo.png)
+![PrecoMaximo](https://images.contentful.com/alneenqid6w5/1lv90zHrOIk0mwqcumEGkE/6e3b7b7cf7a678c003ad0497b2b2629f/PrecoMaximo.png)
 
 Trata-se de um cenário até melhor que o anterior, uma vez que o lojista tem mais opções de agrupamento, por exemplo, por categoria de produto.
 
diff --git a/docs/announcements/pt/mercado-libre-integration-new-interface-for-mapping-categories-and.md b/docs/announcements/pt/mercado-libre-integration-new-interface-for-mapping-categories-and.md
index 44f83a5bc..657f43d42 100644
--- a/docs/announcements/pt/mercado-libre-integration-new-interface-for-mapping-categories-and.md
+++ b/docs/announcements/pt/mercado-libre-integration-new-interface-for-mapping-categories-and.md
@@ -19,7 +19,7 @@ Dando continuidade às melhorias feitas para a [certificação do Mercado Livre]
 
 Antes da certificação, os sellers precisavam preencher a [planilha de mapeamento](https://help.vtex.com/pt/tutorial/mapeamento-de-categorias-variacoes-e-atributos-do-mercado-libre--4xNFUZZmboCSUVdLCFo6eA) com as categorias e atributos dos produtos que desejavam anunciar no Mercado Livre. A nova interface para mapear categorias e atributos chega para substituir a planilha de mapeamento.
 
-![announcement mapperPT (2)](//images.contentful.com/alneenqid6w5/1LlkDGWoB39iUgkixjpTmN/130f95a8bad70defbab742752dbbe403/announcement_mapperPT__2_.gif)
+![announcement mapperPT (2)](https://images.contentful.com/alneenqid6w5/1LlkDGWoB39iUgkixjpTmN/130f95a8bad70defbab742752dbbe403/announcement_mapperPT__2_.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md b/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md
index 38bef89a1..380ca0b66 100644
--- a/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md
+++ b/docs/announcements/pt/mercado-libre-integration-new-promotion-management-interface.md
@@ -19,7 +19,7 @@ Dando continuidade às melhorias feitas para a [certificação do Mercado Livre]
 
 Na nova página de **Promoções** do Mercado Livre, é possível gerenciar uma lista com diferentes campanhas promocionais na plataforma disponíveis para a sua loja.
 
-![Promoções](//images.ctfassets.net/alneenqid6w5/7qDxLkDgrBDJWovD2dhG9I/08759bd0132772b8c5cb51078f9e80bd/Promo____es.gif)
+![Promoções](https://images.ctfassets.net/alneenqid6w5/7qDxLkDgrBDJWovD2dhG9I/08759bd0132772b8c5cb51078f9e80bd/Promo____es.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md b/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
index c0bbcfbd8..9e3be17c3 100644
--- a/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
+++ b/docs/announcements/pt/mudanca-na-concatenacao-reduz-erros-no-envio-de-e-mails.md
@@ -19,14 +19,14 @@ A partir de agora, sua loja pode usar ponto e vírgula (`;`) para concatenar end
 
 Esse recurso funciona nos campos de cópia (`Destinatário (CC)`) e cópia oculta (`Destinatário (CCO)`), assim como a vírgula já funcionava anteriormente. Agora as duas opções de concatenação são válidas.
 
-![Message Center bug fix](//images.ctfassets.net/alneenqid6w5/1DCmh5JlI4cGyIEgwuQQUk/068e65871809d2810df7ec0427773b56/Message_Center_bug_fix.png)
+![Message Center bug fix](https://images.ctfassets.net/alneenqid6w5/1DCmh5JlI4cGyIEgwuQQUk/068e65871809d2810df7ec0427773b56/Message_Center_bug_fix.png)
 
 Essa mudança simples no módulo responsável pelo envio de e-mails transacionais reduziu drasticamente a taxa de erros em comunicações com clientes.
 
 O gráfico abaixo mostra a taxa de erros de uma loja antes de implementarmos o suporte à concatenação com ponto e vírgula. Mais de 90% dos e-mails falhavam todos os dias.
 
-![Message Center bug fix 2](//images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
+![Message Center bug fix 2](https://images.ctfassets.net/alneenqid6w5/2WTicguBZ6ucAO2a48QKum/fb0774ca2f6d2b746a702813c95126a2/Message_Center_bug_fix_2.png)
 
 Depois de implementada a melhoria, os erros no envio de e-mails transacionais da mesma loja foram completamente eliminados, como mostra este outro gráfico:
 
-![Message Center bug fix 3](//images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
+![Message Center bug fix 3](https://images.ctfassets.net/alneenqid6w5/1OmAZMSyp2cm8K4e6aKs8S/bf862028ae01ed3cb1b77cab375ebdf4/Message_Center_bug_fix_3.png)
diff --git a/docs/announcements/pt/multi-currency-gift-card.md b/docs/announcements/pt/multi-currency-gift-card.md
index d62ef0204..d58af7cad 100644
--- a/docs/announcements/pt/multi-currency-gift-card.md
+++ b/docs/announcements/pt/multi-currency-gift-card.md
@@ -39,7 +39,7 @@ Para criar um vale-presente em uma moeda específica, siga os passos abaixo:
 4. Preencha os demais campos de criação do vale-presente.
 5. Clique em `Salvar`.
 
-![Vales-presente multimoedas](//images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/d27b2d03cf01d9626f267a315e2a0c88/GiftCard_Multicurrency_PT_1.PNG)
+![Vales-presente multimoedas](https://images.ctfassets.net/alneenqid6w5/5OBq7L6L2IeSOz5fBe6aRK/d27b2d03cf01d9626f267a315e2a0c88/GiftCard_Multicurrency_PT_1.PNG)
 
 As moedas disponíveis serão as mesmas cadastradas nas [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) de cada loja.
 
diff --git a/docs/announcements/pt/my-authentication-section-in-my-account.md b/docs/announcements/pt/my-authentication-section-in-my-account.md
index 58b791443..ed316e547 100644
--- a/docs/announcements/pt/my-authentication-section-in-my-account.md
+++ b/docs/announcements/pt/my-authentication-section-in-my-account.md
@@ -25,15 +25,15 @@ Esta mudança afetará todas as lojas da VTEX. Como a mudança interfere em algu
 
 Esta aba é um local onde os usuários serão capazes de gerenciar a sua senha. Na aba também é possível gerenciar as sessões de login, permitindo ao usuário encerrar outras sessões remotamente. Mais detalhes sobre o uso da aba podem ser encontrados na seção [Autenticação do artigo Configurar o My Account](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh).
 
-![My Authentication app PT](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
+![My Authentication app PT](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
 
-![My Authentication Session Management PT](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
+![My Authentication Session Management PT](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
 
 No dia 29/09 o componente de gerenciamento de senha também será removido do perfil do usuário para evitar a sua duplicidade. As imagens abaixo mostram exemplos de página de perfil do usuário com e sem o componente de gerenciamento de senha.
 
-![My Account with password PT](//images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/2a78bae58eb46f9ec94c7bb70ccbe11c/My_Account_with_password_PT.png)
+![My Account with password PT](https://images.ctfassets.net/alneenqid6w5/6L8Do8W0nbG4jfKE04ddpj/2a78bae58eb46f9ec94c7bb70ccbe11c/My_Account_with_password_PT.png)
 
-![My Account no password PT](//images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/65082d69145a716441e2d2b555798c72/My_Account_no_password_PT.png)
+![My Account no password PT](https://images.ctfassets.net/alneenqid6w5/22CaEOhOusmmDM73taAw6R/65082d69145a716441e2d2b555798c72/My_Account_no_password_PT.png)
 
 ## Por que realizamos essa mudança?
 
@@ -66,12 +66,12 @@ Para tornar a aba My Authentication visível publicamente na sua loja:
 1. No painel lateral esquerdo do Admin, vá até a seção **CONFIGURAÇÕES DA CONTA**.
 2. Clique em **Aplicativos**.
 3. Clique em **Meus aplicativos**.  
-![My apps menu PT](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/600c792e5f1d3854175315a1854c85bc/My_apps_menu_PT.png)
+![My apps menu PT](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/600c792e5f1d3854175315a1854c85bc/My_apps_menu_PT.png)
 4. Vá até o app **My Account** e clique em `Configurações`.  
-![My apps installed PT](//images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/20d89a53135279f89f0484c0bfef5685/My_apps_installed_PT.png)
+![My apps installed PT](https://images.ctfassets.net/alneenqid6w5/5umcJos7Uz0wnmv0VsZs3Y/20d89a53135279f89f0484c0bfef5685/My_apps_installed_PT.png)
 5. Na seção **AUTHENTICATION** das configurações do app, marque a caixa `Visible`.
 6. Clique em `Salvar`.  
-![My Authentication visible setting PT](//images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/537169239dc172ce1fe772aa91d75b92/My_Authentication_visible_setting_PT.png)
+![My Authentication visible setting PT](https://images.ctfassets.net/alneenqid6w5/5104wJeIBEUYXI7hfkRdH0/537169239dc172ce1fe772aa91d75b92/My_Authentication_visible_setting_PT.png)
 
 Também é possível acessar diretamente as configurações do app My Account no Admin por uma URL.
 - Caso a sua loja seja VTEX IO, utilize o endereço `https://{account}.myvtex.com/admin/apps/vtex.my-account@1.x/setup`, substituindo `{account}` pelo nome da conta.
@@ -79,4 +79,4 @@ Também é possível acessar diretamente as configurações do app My Account no
 
 Após habilitar a visibilidade da aba **Autenticação**, ela aparecerá no perfil de usuário da loja. Ela pode ser acessada por qualquer usuário pelo painel lateral esquerdo.
 
-![My Authentication app PT](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
+![My Authentication app PT](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
diff --git a/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md b/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
index cf5c9d8af..f2db1c264 100644
--- a/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
+++ b/docs/announcements/pt/new-charts-and-real-time-data-in-store-overview-beta-admin-page.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Redesenhamos a página inicial do seu Admin, agora com
 
 A página [Visão Geral (Beta)](https://help.vtex.com/pt/tutorial/visao-geral-da-loja-beta--7i8wNsQQgbbFhYMYbQ5X46) em seu Admin VTEX foi redesenhada e agora oferece novos gráficos, métricas e visualizações. Estas novas funcionalidades permitem o acompanhamento em tempo real da sua operação, fornecendo visibilidade sobre indicadores para que você e sua equipe tenham um feedback rápido das ações realizadas na loja e possam atuar prontamente em melhorias. 
 
-![PT Visão geral Beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/62aceefab415f246a39fcd604a89f080/PT_Visa__o_geral_Beta.png)
+![PT Visão geral Beta](https://images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/62aceefab415f246a39fcd604a89f080/PT_Visa__o_geral_Beta.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/new-indexation-history-screen.md b/docs/announcements/pt/new-indexation-history-screen.md
index c0620e6bd..3a6c4453b 100644
--- a/docs/announcements/pt/new-indexation-history-screen.md
+++ b/docs/announcements/pt/new-indexation-history-screen.md
@@ -19,7 +19,7 @@ Em toda operação de ecommerce, é necessário cadastrar ou alterar informaçõ
 
 Para aprimorar a experiência de monitoramento da indexação do seu Catálogo, redesenhamos a página de **Histórico da Indexação** no Admin VTEX. A nova interface permite acompanhar o tempo de indexação dos seus produtos e o status de indexação da sua loja.
 
-![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 1 - PT](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/new-orders-module-interface-official.md b/docs/announcements/pt/new-orders-module-interface-official.md
index f27957414..b9478018e 100644
--- a/docs/announcements/pt/new-orders-module-interface-official.md
+++ b/docs/announcements/pt/new-orders-module-interface-official.md
@@ -27,15 +27,15 @@ Em relação à versão beta, a interface que será oficial a partir de 1 de fev
 
 * **Busca de pedidos sem limite de data:** possibilidade de buscar pedidos sem definir um limite de data, o que retorna todos os pedidos relacionados ao critério utilizado, independente da data de criação do pedido. Essa busca não pode ser associada a outros filtros. No entanto, você pode selecionar um período de busca personalizado de até seis meses e então combiná-lo com os filtros. Saiba mais no artigo [Filtrar pedidos em Todos os pedidos](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192).
 
-  ![busca_sem_limite_data_all_pt](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
+  ![busca_sem_limite_data_all_pt](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
 
 * **Diagrama do pedido:** na seção _Status do pedido_ da nova interface, por padrão, o que é exibido é uma linha tempo com os eventos do pedido. Agora você pode também ver o _Diagrama do pedido_. Ao clicar em `Ver diagrama`, um modal é aberto e apresenta uma imagem como a seguinte:
 
-  ![diagrama_pedido_pt](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
+  ![diagrama_pedido_pt](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
 
 Para quem ainda não usava a versão beta, a imagem abaixo é um mapeamento da correspondência de campos entre a versão antiga da página **Detalhes do pedido** e a versão oficial:
 
-![board_comparativo_interface_pedido_v2_pt](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
+![board_comparativo_interface_pedido_v2_pt](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
index d25716190..bd5f5cad3 100644
--- a/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
+++ b/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
@@ -23,7 +23,7 @@ A partir de agora você poderá acessar de forma mais rápida as informações d
 
 A tela que permite adicionar um novo provedor, editar configurações e realizar busca de provedores, também foi aprimorada para permitir uma melhor experiência de navegação.
 
-![nova_interface_provedores_admin](//images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/339b129737e2bbf0167d892a50de7f8e/nova_interface_provedores_admin.JPG)
+![nova_interface_provedores_admin](https://images.ctfassets.net/alneenqid6w5/pRDw2IDO4F6G7SadBNwLp/339b129737e2bbf0167d892a50de7f8e/nova_interface_provedores_admin.JPG)
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md b/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md
index 44d014e7c..a88022e79 100644
--- a/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md
+++ b/docs/announcements/pt/new-promotion-list-manage-your-promotions-more-efficiently.md
@@ -30,7 +30,7 @@ Desenvolvemos uma nova interface para a Lista de Promoções, que permite:
 * Exportar sua lista de promoções ativas.
 * Duplicar promoções ativas ou arquivadas para um processo de criação mais rápido.
 
-![geral-promo-PT](//images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/76708dc950cfef626516c9a08b6fe13d/image3.png)
+![geral-promo-PT](https://images.ctfassets.net/alneenqid6w5/5J9dSnkUhLm1gTUjhUftrP/76708dc950cfef626516c9a08b6fe13d/image3.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/new-roles-page.md b/docs/announcements/pt/new-roles-page.md
index a0931c686..64dd64cd4 100644
--- a/docs/announcements/pt/new-roles-page.md
+++ b/docs/announcements/pt/new-roles-page.md
@@ -28,7 +28,7 @@ Além de todas as funcionalidades da versão anterior, a nova página de **Perfi
 * Acessar a listagem completa dos perfis de acesso cadastrados na sua loja com um design mais moderno e intuitivo, atualizado para o [Novo Admin VTEX](https://help.vtex.com/pt/tutorial/admin-vtex-comece-aqui--531cHtUCUi3puRXNDmKziw).
 * Visualizar informações úteis para o gerenciamento de perfis de acesso diretamente na listagem, como a quantidade de usuários associados a cada perfil, o tipo de perfil (predefinido ou personalizado) e a data de criação do perfil.
 
-![roles-pt](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/943f5df380f3fb685bb369014b435454/roles-pt.png)
+![roles-pt](https://images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/943f5df380f3fb685bb369014b435454/roles-pt.png)
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/new-sales-performance-dashboard.md b/docs/announcements/pt/new-sales-performance-dashboard.md
index 0f57f6135..cf30a6b48 100644
--- a/docs/announcements/pt/new-sales-performance-dashboard.md
+++ b/docs/announcements/pt/new-sales-performance-dashboard.md
@@ -19,7 +19,7 @@ Com um volume cada vez maior de dados disponíveis para operações de ecommerce
 
 O dashboard permite que os usuários analisem dados de todos os canais de venda da loja, e de seus sellers, incluindo métricas sobre receita, pedidos, ticket médio e muito mais. Inclui também gráficos e tabelas para que você compare resultados de períodos diferentes, introduzindo onze opções de filtros para que obtenham insights unificados de toda a operação.
 
-![Sales Perf Dash PT](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
+![Sales Perf Dash PT](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
 
 ## O que mudou?
 Antes, o seu Admin VTEX incluía somente a página Insights para gerar inteligência de negócios a partir dos dados da sua operação. Agora incluímos uma nova página, a Performance de Vendas, para que você tenha uma visão mais detalhada dos resultados dos diferentes canais de venda da sua loja. A página de Insights ainda permanecerá em seu Admin VTEX.
diff --git a/docs/announcements/pt/new-sku-bindings-interface.md b/docs/announcements/pt/new-sku-bindings-interface.md
index 248c4b4f1..de022f859 100644
--- a/docs/announcements/pt/new-sku-bindings-interface.md
+++ b/docs/announcements/pt/new-sku-bindings-interface.md
@@ -19,7 +19,7 @@ A VTEX possibilita que a sua loja atue tanto como [seller](https://help.vtex.com
 
 Para aprimorar essa experiência, redesenhamos a página de **Vínculos de SKU** no Admin VTEX. A nova interface permite acompanhar e gerenciar a relação de vínculo entre os SKUs do seller e do marketplace de forma mais simples e ágil.
 
-![sku_binding_page_PT_final](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/5b8897408601d49051d35dd5364c2a8e/sku_binding_page_PT_final.png)
+![sku_binding_page_PT_final](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/5b8897408601d49051d35dd5364c2a8e/sku_binding_page_PT_final.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/new-subscriptions-module.md b/docs/announcements/pt/new-subscriptions-module.md
index fe0f7196f..7da275344 100644
--- a/docs/announcements/pt/new-subscriptions-module.md
+++ b/docs/announcements/pt/new-subscriptions-module.md
@@ -39,35 +39,35 @@ A melhoria do sistema de assinaturas também trouxe novas funcionalidades para o
 #### Novo detalhamento de assinaturas 
 A nossa página de detalhamento de assinatura foi remodelada pensando em melhorar a experiência do consumidor ao reduzir o tempo para localizar informações e realizar tarefas. Além disso, contamos com a nova funcionalidade de adicionar itens a uma assinatura existente.
 
-![img1 subscriptions PT](//images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/0578726c45d942f7960c7e3999649627/img1_subscriptions_PT.png)
+![img1 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/YTLE4SVoIbfDCdH9BK97s/0578726c45d942f7960c7e3999649627/img1_subscriptions_PT.png)
 
 #### Barra de ações
 Adicionamos uma barra de ações para melhorar a comunicação com o usuário sobre o que precisa ser feito ou comunicar eventos importantes sobre a sua assinatura.
 
-![img2 subscriptions PT](//images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/77b61a6259cf558bfa78db8c5ada1f80/img2_subscriptions_PT.png)
+![img2 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/4SOJIaVfD2pnRqDK8oChFM/77b61a6259cf558bfa78db8c5ada1f80/img2_subscriptions_PT.png)
 
 #### Adicionar produto à sua assinatura
 Agora é possível adicionar um novo item à sua assinatura através da busca dos produtos disponíveis na loja. 
 
-![img3 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/64249fe1d011fc477d8760f27a783506/img3_subscriptions_PT.png)
+![img3 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1QLpkpJqU4GmAxG2kQl34s/64249fe1d011fc477d8760f27a783506/img3_subscriptions_PT.png)
 
 #### Criar uma nova assinatura
 Adicionamos uma funcionalidade muito aguardada que é a tela de criação de assinaturas. Ela permite configurar uma nova assinatura sem ter que passar pelo checkout e realizar um pedido na hora. Para realizar essa ação, basta clicar no botão __Nova assinatura__, na listagem de assinaturas.
 
-![img4 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/8659bfceec1f88773e5871092be90771/img4_subscriptions_PT.png)
+![img4 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1Olba34z68eZB3VqeGLPvL/8659bfceec1f88773e5871092be90771/img4_subscriptions_PT.png)
 
 ### Novo conceito de assinaturas para o sistema
 Até então, para o sistema da VTEX, uma assinatura era composta por um SKU, atrelado a uma configuração de compra. Isso permitia que o consumidor da loja assinasse SKUs com endereços de entrega e até mesmo formas de pagamento diferentes – uma evolução em comparação à primeira versão do sistema. 
 
 #### Antes:
-![img5 subscriptions PT](//images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/4d469f2404f59d76b5ebe67b89e36365/img5_subscriptions_PT.png)
-![img6 subscriptions PT](//images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/eb2c0c259c6ffba5c7bd4e7ac0cda841/img6_subscriptions_PT.png)
-![img7 subscriptions PT](//images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/cab5768ff5bad6dab10ca2cd5e931c8f/img7_subscriptions_PT.png)
+![img5 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/36iPClYx89vn03OHhkUfho/4d469f2404f59d76b5ebe67b89e36365/img5_subscriptions_PT.png)
+![img6 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/3R0ImpMVwP9C81ndi5oCvg/eb2c0c259c6ffba5c7bd4e7ac0cda841/img6_subscriptions_PT.png)
+![img7 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/W44xbs0MAAwYxjyU8Dj4E/cab5768ff5bad6dab10ca2cd5e931c8f/img7_subscriptions_PT.png)
 
 A assinatura para nós agora consiste em uma lista de SKUs e uma determinada configuração de compra. Isso significa que nós retiramos o conceito de Grupos de Assinatura do nosso sistema. Saiba mais no artigo [Como funciona a assinatura](https://help.vtex.com/pt/tutorial/como-funciona-a-assinatura--frequentlyAskedQuestions_4453). O diagrama abaixo demonstra o novo conceito de assinatura:
 
 #### Agora:
-![img8 subscriptions PT](//images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/474f3170b2f10977be30172465ffd630/img8_subscriptions_PT.png)
+![img8 subscriptions PT](https://images.ctfassets.net/alneenqid6w5/1tNo9gQza7gWuDXZPRxQRO/474f3170b2f10977be30172465ffd630/img8_subscriptions_PT.png)
 
 ### Data do ciclo da assinatura
 
diff --git a/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md b/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md
index da30caf57..87747e3a3 100644
--- a/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md
+++ b/docs/announcements/pt/new-ui-for-the-admins-user-management-dashboard.md
@@ -22,7 +22,7 @@ O painel de gerenciamento de usuários teve seu design atualizado com os mesmos
 - Apresentação da configuração de MFA (autenticação de múltiplos fatores) para cada usuário na lista de usuários.
 - Botão para exportar os dados da lista de usuários para um arquivo csv que inclui id, email e nome.
 
-![Lista Usuários User Management PT](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
+![Lista Usuários User Management PT](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
 
 Além disso, o painel sofreu algumas alterações:
 
diff --git a/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md b/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md
index 56d062234..4352721cf 100644
--- a/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md
+++ b/docs/announcements/pt/novo-layout-no-e-mail-de-codigo-de-acesso.md
@@ -18,7 +18,7 @@ announcementSynopsisPT: 'Atualizamos o layout do e-mail recebido ao solicitar o
 Atualizamos o layout do e-mail recebido ao solicitar o código de acesso para seu admin. 
 Agora, todas as vezes que o código de acesso for requisitado para logar ou alterar a senha, você receberá um e-mail como este abaixo:  
 
-![announcement-novo-layout-email-codigo-acesso PT](//images.ctfassets.net/alneenqid6w5/cQVFNnznSclT585LRuACz/06a49b0a9837c3d5a64503f982a354d1/announcement-novo-layout-email-codigo-acesso.png)
+![announcement-novo-layout-email-codigo-acesso PT](https://images.ctfassets.net/alneenqid6w5/cQVFNnznSclT585LRuACz/06a49b0a9837c3d5a64503f982a354d1/announcement-novo-layout-email-codigo-acesso.png)
 
 ## O que muda  
 A nova versão proporciona mais usabilidade e fluidez ao layout e está mais coerente com a identidade visual da VTEX. Além disso, o código recebeu mais destaque no corpo do e-mail, privilegiando a informação. Outro ponto favorável são as versões disponíveis para cada idioma.  
diff --git a/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md b/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md
index 20da4f1f5..6804e0d0e 100644
--- a/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md
+++ b/docs/announcements/pt/offer-pickup-points-for-subscription-orders.md
@@ -23,7 +23,7 @@ A funcionalidade de pontos de retirada para assinaturas está disponível em ver
 
 Antes, as assinaturas não tinham pontos de retirada como uma das opções de entrega. Com a nova funcionalidade, o cliente final pode escolher pontos de retirada para itens de um pedido de assinatura no momento do checkout, conforme ilustrado na imagem abaixo.
 
-![subscriptionspickup PT](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
+![subscriptionspickup PT](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
 
 Além disso, você também pode atribuir pontos de retirada a novas assinaturas e a assinaturas já existentes por meio da [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1).
 
diff --git a/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md b/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md
index 3cf5428fd..98b9047a2 100644
--- a/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md
+++ b/docs/announcements/pt/offer-status-module-for-integrations-with-vtex-marketplaces.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Acompanhe seus anúncios com o novo módulo Status dos
 
 __Status dos anúncios__ é o novo módulo no Admin VTEX que permite ao seller acompanhar o envio e a sincronização dos anúncios de integrações com marketplaces VTEX de todas as regiões do mundo. Para acessar o módulo, vá em __Marketplace > Conexões > Status de anúncios,__ ou digite __Status de anúncios__ na barra de busca.
 
-![Tela Offer Status](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/e383485bcec5739e5594fb942ab529a2/-PT-_Offer_Status_-_GIF.gif)
+![Tela Offer Status](https://downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/e383485bcec5739e5594fb942ab529a2/-PT-_Offer_Status_-_GIF.gif)
 
 ## Por que desenvolvemos essa funcionalidade?
 
diff --git a/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md b/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
index 8496a445a..e0deeeb9e 100644
--- a/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
+++ b/docs/announcements/pt/on-06-17-the-native-links-to-your-stores-my-account-page-will-change-review.md
@@ -35,7 +35,7 @@ A revisão e o eventual ajuste desta mudança devem ser aplicados através dos t
 
 Passos necessários para a revisão e adaptação:
 
-1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
+1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
 2. __Customização__: se a página "/account/orders" possuir alguma customização de front-end, esta deve ser migrada e adaptada para a nova URL "/account#/orders". Revise e realize todos os testes necessários garantindo funcionamento de todas as recursos personalizados;  
 3. __Links do site__: Revise e atualize todos os links customizados do site e dos e-mails transacionais que antes direcionavam o usuário para a URL "/account/orders". Estes links agora devem direcionar o usuário para "/account#/orders".
 
diff --git a/docs/announcements/pt/price-filters-more-search-flexibility.md b/docs/announcements/pt/price-filters-more-search-flexibility.md
index 547b8fab6..aca2bb5fb 100644
--- a/docs/announcements/pt/price-filters-more-search-flexibility.md
+++ b/docs/announcements/pt/price-filters-more-search-flexibility.md
@@ -23,7 +23,7 @@ Agora, você pode filtrar os preços combinando as múltiplas Categorias e Marca
 
 Essa atualização da funcionalidade viabiliza a exportação de preços mais específicos, a partir da seleção dos filtros.
 
-![filtro preco-PT](//images.ctfassets.net/alneenqid6w5/NzavsKoHY8DQUX2FZeoG6/f8152dfe5944412d46bea030585a20f0/filtro_preco-PT.png)
+![filtro preco-PT](https://images.ctfassets.net/alneenqid6w5/NzavsKoHY8DQUX2FZeoG6/f8152dfe5944412d46bea030585a20f0/filtro_preco-PT.png)
 
 ## O que preciso fazer?
 Para utilizar essa nova configuração, siga os passos  abaixo:
diff --git a/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md b/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
index 5ab1274a7..636fa23c5 100644
--- a/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
+++ b/docs/announcements/pt/pricing-v1-module-will-be-discontinued-update-your-store-by-september.md
@@ -31,7 +31,7 @@ Para saber se a sua conta ainda está utilizando o Pricing V1, siga os passos ab
 
 Caso você visualize uma tela semelhante à tela abaixo, significa que sua conta precisa realizar a migração. 
 
-![Tela pricing antiga - PT](//images.ctfassets.net/alneenqid6w5/7JRnTJEIa0Fh3noWBUEiUF/1c961c41028c24c19969c521ba1df552/Tela_pricing_antiga_-_PT.png)
+![Tela pricing antiga - PT](https://images.ctfassets.net/alneenqid6w5/7JRnTJEIa0Fh3noWBUEiUF/1c961c41028c24c19969c521ba1df552/Tela_pricing_antiga_-_PT.png)
 
 Caso a sua conta VTEX ainda utiliza versões anteriores do Admin VTEX (como "vtexcommercestable", por exemplo), ela também precisará realizar a migração. Para isso, siga os passos a seguir:
 
diff --git a/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md b/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
index f588515d7..5dfee2f79 100644
--- a/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
+++ b/docs/announcements/pt/promotion-simulator-understand-the-promotions-applied-to-the-cart.md
@@ -32,7 +32,7 @@ A partir de agora, o **Simulador de promoções** está disponível para todas a
 * **Testar a aplicação** de outras promoções ao carrinho antes de ativá-las, incluindo promoções agendadas e inativas.
 * **Entender os motivos** de uma promoção não ter sido aplicada ao carrinho.
 
-![promotions simulator - pt-gif 3](//downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/54f7514e928050ff2ae19ce3fc3a93d4/promotions_simulator_announcement.gif)
+![promotions simulator - pt-gif 3](https://downloads.ctfassets.net/alneenqid6w5/5RwzKZuP1klBEZfpUYAivG/54f7514e928050ff2ae19ce3fc3a93d4/promotions_simulator_announcement.gif)
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/rate-vtexs-service-in-your-admin.md b/docs/announcements/pt/rate-vtexs-service-in-your-admin.md
index 2699c6cbb..b34222774 100644
--- a/docs/announcements/pt/rate-vtexs-service-in-your-admin.md
+++ b/docs/announcements/pt/rate-vtexs-service-in-your-admin.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Lançamos uma página de pesquisa de satisfação no Ad
 
 Lançamos a nova página *Pesquisa de Satisfação* no seu Admin VTEX. Agora, você pode avaliar o atendimento do nosso suporte sem sair do ambiente VTEX.
 
-![Pesquisa de satisfação PT](//images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/b213884709ae4bd96dc820d6b60b99b2/image__19_.png)
+![Pesquisa de satisfação PT](https://images.ctfassets.net/alneenqid6w5/3W8q5tdB9ZOrPT4QFMZP2D/b213884709ae4bd96dc820d6b60b99b2/image__19_.png)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
index 7559784d4..5d3bac41c 100644
--- a/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
+++ b/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -46,7 +46,7 @@ Peça à sua equipe de desenvolvimento para revisar as integrações que usam a
 
 Ela poderá seguir o diagrama abaixo para avaliar se uma integração precisa ser ajustada, de acordo com a [configuração de reCAPTCHA do orderForm](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) da sua loja e como as solicitações feitas a esses endpoints são [autenticadas](https://developers.vtex.com/docs/guides/authentication-overview):
 
-![reCAPTCHA diagram](//images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/bfd89311bfff3e2597bb5fbf2862d6da/recaptcha-config-PT.png)
+![reCAPTCHA diagram](https://images.ctfassets.net/alneenqid6w5/46F1byxPKdYgWcf1lSkPMn/bfd89311bfff3e2597bb5fbf2862d6da/recaptcha-config-PT.png)
 
 - __Caso 1__: *não são necessárias alterações na integração, mas sua loja pode estar em risco.*
 
diff --git a/docs/announcements/pt/redesigned-products-and-skus-page.md b/docs/announcements/pt/redesigned-products-and-skus-page.md
index 377aefd48..3a4c65f78 100644
--- a/docs/announcements/pt/redesigned-products-and-skus-page.md
+++ b/docs/announcements/pt/redesigned-products-and-skus-page.md
@@ -28,7 +28,7 @@ A nova interface de **Produtos & SKUs** possibilita:
 * Acompanhar status de produtos e SKUs de forma mais direta e visual, com ícones e status de SKUs diretamente na listagem.
 * Identificar com mais facilidade produtos e SKUs com informações pendentes para ficarem disponíveis para venda, a partir do novo status **Pendente**.
 
-![catalog-products-skus-pt](//images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/269a128e08a453ce564041ceb39bea9e/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_25_56_1.png)
+![catalog-products-skus-pt](https://images.ctfassets.net/alneenqid6w5/20sC1yswkFmqokxll0ehi1/269a128e08a453ce564041ceb39bea9e/screencapture-catalog-sandboxintegracao-myvtex-admin-catalog-2023-04-10-10_25_56_1.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/registering-pickup-points-is-now-easier-and-faster.md b/docs/announcements/pt/registering-pickup-points-is-now-easier-and-faster.md
index f631f8d3e..d28de1dcb 100644
--- a/docs/announcements/pt/registering-pickup-points-is-now-easier-and-faster.md
+++ b/docs/announcements/pt/registering-pickup-points-is-now-easier-and-faster.md
@@ -15,7 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Agora, você pode fazer o upload de uma planilha XLS com todos os pickup points que deseja oferecer na sua loja.'
 ---
 
-Você não precisa mais cadastrar pontos de retirada um a um. Agora, o Admin permite que você faça o upload de uma planilha XLS [(como a deste exemplo)](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls) com todos os pickup points que deseja oferecer na sua loja.
+Você não precisa mais cadastrar pontos de retirada um a um. Agora, o Admin permite que você faça o upload de uma planilha XLS [(como a deste exemplo)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls) com todos os pickup points que deseja oferecer na sua loja.
 
 
 ## Mais agilidade nas suas configurações de logística
diff --git a/docs/announcements/pt/reusing-images-in-site-editor.md b/docs/announcements/pt/reusing-images-in-site-editor.md
index 611569e84..a130592cd 100644
--- a/docs/announcements/pt/reusing-images-in-site-editor.md
+++ b/docs/announcements/pt/reusing-images-in-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Aprimoramos blocos com a opção nativa de envio de ima
 
 Aprimoramos a maneira como você gerencia suas imagens no [Site Editor](https://help.vtex.com/pt/subcategory/site-editor--9Arh3cJIOYlfSD1MUC2h3) por meio do Image Widget, um repositório de imagens centralizado para que você possa enviar e reutilizar imagens da loja. 
 
-![gif-image-widget-pt](//images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/04a48b195d89b88cf44fde97989c3770/Irec5JDGdy.gif)
+![gif-image-widget-pt](https://images.ctfassets.net/alneenqid6w5/5PlVIsozLB3d1TY7NGqsqe/04a48b195d89b88cf44fde97989c3770/Irec5JDGdy.gif)
 
 <div style="background-color:#cfe2ff; border-left: 2px solid #084298; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 16px">
   Image Widget está disponível em Open Beta para usuários VTEX IO.
diff --git a/docs/announcements/pt/sales-performance-dashboard-updates.md b/docs/announcements/pt/sales-performance-dashboard-updates.md
index 985b95e27..bb428c492 100644
--- a/docs/announcements/pt/sales-performance-dashboard-updates.md
+++ b/docs/announcements/pt/sales-performance-dashboard-updates.md
@@ -19,7 +19,7 @@ A página Performance de Vendas é um dashboard que permite que operadores de lo
 
 Atualizamos a sua experiência na página a partir das sugestões dadas por vocês, adicionando novas possibilidades para aplicação de filtros, visualizações e exploração de dados. 
 
-![Sales perf update PT](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
+![Sales perf update PT](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
 
 ## O que mudou?
 Aprimoramos algumas funcionalidades existentes, como Filtros e Dados, e acrescentamos o menu Visualização. A nova experiência de filtros da página possibilita mais combinações de filtros, com menos cliques. Já a nova funcionalidade de menu Visualização foi feita para gravar os filtros e métricas aplicados na página, permitindo voltar rapidamente para o mesmo contexto. 
diff --git a/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md b/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md
index be765a6c0..8986a4a4e 100644
--- a/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md
+++ b/docs/announcements/pt/save-user-opt-in-using-stored-information-for-future-purchases.md
@@ -23,7 +23,7 @@ Anteriormente, após o cadastro na loja ou primeira compra, os dados do cliente
 
 A partir de agora, duas caixas de seleção estarão disponíveis na tela do Checkout, permitindo que o usuário indique se deseja que suas informações pessoais e de pagamento sejam armazenadas e reutilizadas para futuras compras. Dessa maneira, será  reduzido o tempo de compra realizado pelo cliente. 
 
-![ Save user data opt-in PT](//images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/5324e710aa8787fc411b63e1f67609e2/Save_user_data_-_PT.PNG)
+![ Save user data opt-in PT](https://images.ctfassets.net/alneenqid6w5/6NGmOzVPMDNlcptCwaqTsM/5324e710aa8787fc411b63e1f67609e2/Save_user_data_-_PT.PNG)
 
 Saiba mais em [SmartCheckout - Preenchimento automático de dados do cliente](https://help.vtex.com/pt/tutorial/smartcheckout-customer-information-automatic-fill-in--2Nuu3xAFzdhIzJIldAdtan#).
 
diff --git a/docs/announcements/pt/schedule-content-publication-with-site-editor.md b/docs/announcements/pt/schedule-content-publication-with-site-editor.md
index 47a08580f..f48e215c6 100644
--- a/docs/announcements/pt/schedule-content-publication-with-site-editor.md
+++ b/docs/announcements/pt/schedule-content-publication-with-site-editor.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Crie e programe versões de bloco predefinidas no Site
 
 O recurso **Configurações** do Site Editor foi atualizado. Agora, além de se chamar **Versões**, você pode criar as  versões do conteúdo de sua loja desativadas e ativá-las quando desejar.
 
-![activating-versions-pt](//images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/01ea74a9392015c3eb54ae8b0546908a/activating-versions-pt.gif)
+![activating-versions-pt](https://images.ctfassets.net/alneenqid6w5/31O8XD7Pt9GWWYk2W8q13K/01ea74a9392015c3eb54ae8b0546908a/activating-versions-pt.gif)
 
 ## O que mudou?
 Antes, o recurso **Versões** se chamava **Configurações**, e era apenas possível criar uma nova versão ativada, por exemplo, de um Carrossel com produtos em promoção, ou agendar a sua ativação. Após uma versão sair do ar, também não era possível ativá-la novamente.
diff --git a/docs/announcements/pt/search-filters-in-instores-endless-aisle.md b/docs/announcements/pt/search-filters-in-instores-endless-aisle.md
index 86604e1f1..5ae7209e0 100644
--- a/docs/announcements/pt/search-filters-in-instores-endless-aisle.md
+++ b/docs/announcements/pt/search-filters-in-instores-endless-aisle.md
@@ -25,7 +25,7 @@ Anteriormente, os filtros de busca do VTEX Intelligent Search não estavam dispo
 
 Com a nova funcionalidade, ao pesquisar por um termo, os vendedores podem filtrar os resultados por faixa de preço, departamento e marca, por exemplo, entre outros filtros configuráveis no VTEX Intelligent Search. Assim, é possível encontrar o produto desejado rapidamente.
 
-![instore-filtros-pt](//images.contentful.com/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/7323d6b08db453a0271cc2b2c618c274/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-13_54_51.png)
+![instore-filtros-pt](https://images.contentful.com/alneenqid6w5/2ppFcrZLpmUs1Sa1d93mYj/7323d6b08db453a0271cc2b2c618c274/screencapture-demoinstore-myvtex-checkout-instore-2021-12-02-13_54_51.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
index 19dbfa9ac..619ea5376 100644
--- a/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
+++ b/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -30,7 +30,7 @@ Antes, a barra de busca global permitia buscar somente nas páginas do Admin VTE
 
 Para isso, clique na barra de busca, selecione a opção `Pedidos`, e realize a pesquisa desejada. Cada busca pode apresentar até 10 resultados, como na imagem abaixo:
 
-![order_global_search_PT](//images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/1d0f182535930b7157f9ed03aa363af6/order_global_search_PT.gif)
+![order_global_search_PT](https://images.ctfassets.net/alneenqid6w5/7sJBPUKfTt3bUTuSTEQJEP/1d0f182535930b7157f9ed03aa363af6/order_global_search_PT.gif)
 
 Ao clicar em um resultado, você é redirecionado para a [página de detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) do pedido. Além disso, os últimos 10 pedidos buscados ficam registrados como um histórico de buscas recentes, aumentando a praticidade de acesso. O registro de busca é armazenado a nível de [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) e não é compartilhado entre usuários diferentes.
 
diff --git a/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md b/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
index 50ef42a8f..007d80cea 100644
--- a/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
+++ b/docs/announcements/pt/sell-more-with-the-app-that-integrates-your-business-to-google-shopping.md
@@ -19,7 +19,7 @@ A __Black Friday__ está chegando. E, com ela, vem o desejo de aproveitar essa o
 
 Para te ajudar nessa tarefa, a VTEX está lançando uma __app exclusiva em parceria com o Google__, que ficará disponível em nossa [App Store](https://apps.vtex.com/vtex-google-shopping/p).
 
-![Google Shopping App](//images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
+![Google Shopping App](https://images.ctfassets.net/alneenqid6w5/2pPKWvJT2YQEge4yWkEMSS/aa05248d6aa8df9b6b05cc2095ad00e4/Google_Shopping_App.png)
 
 Ela integra seu negócio ao Google Ads, permitindo que você divulgue seus produtos no Google Shopping, usando as novas Smart Shopping Campaigns, e acompanhe os resultados com facilidade e rapidez.
 
diff --git a/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md b/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
index 47526a27a..032e0167d 100644
--- a/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
+++ b/docs/announcements/pt/shopping-season-get-your-store-ready-with-our-best-practices-guide-2023.md
@@ -27,4 +27,4 @@ https://{accountName}.myvtex.com/admin/shopping-season
 
 Basta substituir `{accountName}` pelo Account Name da sua loja, como na imagem abaixo.
 
-![Shopping Season Guidelines - 2023 - PT](//images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/241e179f90c255d883968098fc781826/Shopping_Season_Guidelines_-_2023_-_PT.png)
+![Shopping Season Guidelines - 2023 - PT](https://images.ctfassets.net/alneenqid6w5/53t6AKSniwItQHaG5qalil/241e179f90c255d883968098fc781826/Shopping_Season_Guidelines_-_2023_-_PT.png)
diff --git a/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md b/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md
index af0681483..bc2ca5c9e 100644
--- a/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md
+++ b/docs/announcements/pt/social-selling-share-instore-carts-using-qr-codes.md
@@ -27,7 +27,7 @@ Antes, a funcionalidade de Social Selling no inStore consistia em gerar um link
 
 Com a mudança, agora o inStore também gera um QR code que pode ser lido pelos dispositivos dos clientes, além do link compartilhável.
 
-![instore-social-selling-qr-code-share-pt](//images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/21874f9cc593ea5f8dda4f985deb6fe2/image1.png)
+![instore-social-selling-qr-code-share-pt](https://images.ctfassets.net/alneenqid6w5/3JOA4Ar1iW4PudeTYWzaQD/21874f9cc593ea5f8dda4f985deb6fe2/image1.png)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/social-selling-share-your-instore-cart.md b/docs/announcements/pt/social-selling-share-your-instore-cart.md
index d1d24aa34..95c118fc5 100644
--- a/docs/announcements/pt/social-selling-share-your-instore-cart.md
+++ b/docs/announcements/pt/social-selling-share-your-instore-cart.md
@@ -28,7 +28,7 @@ Anteriormente, o compartilhamento de carrinho não era possível no inStore, [ap
 
 Com o inStore Social Selling, vendedores da sua loja física podem selecionar produtos e gerar um link para compartilhar a __Sugestão de carrinho__ com um ou mais clientes pelo WhatsApp, conforme demonstrado a seguir. Também existe a possibilidade de copiar o link e compartilhar em outras redes sociais.
 
-![socialselling-PT](//images.contentful.com/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/4549760d18071306dcc4ce085b622115/socialselling-PT.gif)
+![socialselling-PT](https://images.contentful.com/alneenqid6w5/1jdz7EIobEDMQqdRmdIVJY/4549760d18071306dcc4ce085b622115/socialselling-PT.gif)
 
 Nesse caso, o vendedor pode enviar o mesmo link para vários clientes, quantas vezes desejar. Cada vez que uma pessoa acessar esse link, um novo carrinho será gerado, exatamente igual ao criado no inStore. Cada carrinho acessado também fica associado à conta do vendedor e,  se houver, ao código do vendedor.
 
@@ -36,7 +36,7 @@ Os clientes podem acessar o carrinho, realizar o pagamento e concluir a compra e
 
 Outra possibilidade é o vendedor preencher as informações de entrega do cliente, escolher a forma de pagamento e depois compartilhar um **Link de pagamento**. Assim, o link do carrinho compartilhado vai conter todas as informações pessoais já preenchidas. O cliente só precisa preencher os dados de pagamento para finalizar a compra em seu dispositivo. Veja a seguir como funciona.
 
-![paymentlink PT](//images.contentful.com/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/27152cf81c5e0d9c598c00ebb32f6e28/paymentlink_PT.gif)
+![paymentlink PT](https://images.contentful.com/alneenqid6w5/7FjwJywOLKl0WjdC8U1IFc/27152cf81c5e0d9c598c00ebb32f6e28/paymentlink_PT.gif)
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md b/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md
index 632464912..d911d6b35 100644
--- a/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md
+++ b/docs/announcements/pt/the-native-links-to-my-account-page-will-change-review-your-settings.md
@@ -35,7 +35,7 @@ A revisão e o eventual ajuste desta mudança devem ser aplicados através dos t
 
 Passos necessários para a revisão e adaptação:
 
-1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](//images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
+1. __Configuração básica__: revise se o template da página "/account" (ilustração abaixo) já utiliza a view part `<vtex.cmc:accountUserProfile />` e a atualize se houver necessidade. Esta view part é responsável por carregar todas as informações do cliente, incluindo seus pedidos. As view parts anteriores, `<vtex.cmc:accountAddress/>` e `<vtex.cmc:orderList />` devem ser removidas deste template.![account](https://images.ctfassets.net/alneenqid6w5/LIki0Pf7j1gOUi01EIajh/f7089fece0b6b10921fcb969066e2f4a/account.png)
 2. __Customização__: se a página "/account/orders" possuir alguma customização de front-end, esta deve ser migrada e adaptada para a nova URL "/account#/orders". Revise e realize todos os testes necessários garantindo funcionamento de todas as recursos personalizados;  
 3. __Links do site__: Revise e atualize todos os links customizados do site e dos e-mails transacionais que antes direcionavam o usuário para a URL "/account/orders". Estes links agora devem direcionar o usuário para "/account#/orders".
 
diff --git a/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md b/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md
index baf1060ae..fb98c04f6 100644
--- a/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md
+++ b/docs/announcements/pt/transparency-and-security-with-the-new-audit-module.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Lançamento de nova ferramenta de auditoria'
 
 Sempre em conformidade com as melhores práticas de segurança e transparência para sua loja, a VTEX lançou mais um novo recurso de auditoria, o **Audit**. 
 
-![Screenshot for Audit UI for announcement](//images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/a7e351d449a8ff53422f9a9b914dbdc2/Audit_PT.png)
+![Screenshot for Audit UI for announcement](https://images.ctfassets.net/alneenqid6w5/1CwFsrYwjxCIhyqcc6ei86/a7e351d449a8ff53422f9a9b914dbdc2/Audit_PT.png)
 
 A partir de agora, os administradores podem verificar diversas operações que foram feitas em sua loja de uma maneira simples e rápida. É possível criar vários filtros de busca para facilitar a procura de eventos e aumentar a rapidez dos processos de auditoria.
 
diff --git a/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md b/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md
index 0cacbc950..db0cd8576 100644
--- a/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md
+++ b/docs/announcements/pt/untitled-entry-2021-01-19-at-17-22-53.md
@@ -17,6 +17,6 @@ announcementSynopsisPT: ''
 
 kjevfuevd
 
-![PT Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![PT Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 jsvdcusv
diff --git a/docs/announcements/pt/update-grants-in-the-promotions-module.md b/docs/announcements/pt/update-grants-in-the-promotions-module.md
index 0adb6172d..9343a92e9 100644
--- a/docs/announcements/pt/update-grants-in-the-promotions-module.md
+++ b/docs/announcements/pt/update-grants-in-the-promotions-module.md
@@ -37,5 +37,5 @@ Com esta atualização, você tem mais poder sobre  o comportamento das suas pro
  6. Clique em  **Usar configurações de recorrência**
  7. Faça a configuração desejável de dias e horários para a promoção
 
-![CRON 2 PT](//images.ctfassets.net/alneenqid6w5/7sn8XLs4lRqMFeWaR77Jqa/ab7e5605b834f8054b84191448cc6240/CRON_2_PT.png)
+![CRON 2 PT](https://images.ctfassets.net/alneenqid6w5/7sn8XLs4lRqMFeWaR77Jqa/ab7e5605b834f8054b84191448cc6240/CRON_2_PT.png)
 
diff --git a/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md b/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
index 39039a17b..0e1d574e3 100644
--- a/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
+++ b/docs/announcements/pt/use-the-nominal-tax-and-avoid-customers-abandoning-their-shopping-cart.md
@@ -33,5 +33,5 @@ A funcionalidade  pode ser utilizada sempre que o lojista desejar que a taxa no
 - Em "Qual o tipo e valor da Taxa?", escolha a opção Taxa Nominal
 - Preencha os itens necessários e clique em salvar
 
-![Nominal tax PT](//images.ctfassets.net/alneenqid6w5/2TKpj3XiV3ZOULJnsDrZoO/02331539e2325d6b26f9547f48ca8575/Nominal_tax_PT.png)
+![Nominal tax PT](https://images.ctfassets.net/alneenqid6w5/2TKpj3XiV3ZOULJnsDrZoO/02331539e2325d6b26f9547f48ca8575/Nominal_tax_PT.png)
 
diff --git a/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md b/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md
index 2536eeb92..f0d3aa016 100644
--- a/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md
+++ b/docs/announcements/pt/ux-improvements-at-checkout-for-expired-cards.md
@@ -23,7 +23,7 @@ Para continuarmos refinando essa experiência, incluímos uma validação adicio
 
 Antes era possível que um comprador selecionasse um cartão vencido e realizasse uma compra, que teria seu pagamento negado em seguida. Agora sinalizamos cartões vencidos e impedimos que eles sejam selecionados checkout, para uma experiência de compra mais fluida.
 
-![PT - Expired Cards](//images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/d9be78a77ef1849dd23b5bb86bd58fc7/PT_-_Expired_Cards.png)
+![PT - Expired Cards](https://images.ctfassets.net/alneenqid6w5/7HzPrSIeXAcZj1x5v7PFsB/d9be78a77ef1849dd23b5bb86bd58fc7/PT_-_Expired_Cards.png)
 
 ## Por que realizamos esta mudança?
 
diff --git a/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md b/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
index bc054cf27..b8bd40de3 100644
--- a/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
+++ b/docs/announcements/pt/vtex-intelligent-search-new-visual-editor-for-merchandising-rules.md
@@ -28,7 +28,7 @@ Anteriormente, lojas com [VTEX Intelligent Search](https://help.vtex.com/pt/trac
 * Fixar um produto nas primeiras posições dos resultados de busca.
 * Analisar as principais informações do produto.
 
-![visual-merch-rules-PT-announcement (1)](//images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/618748bfb039c6a3e757b1655774a8e0/visual-merch-rules-PT-announcement__1_.png)
+![visual-merch-rules-PT-announcement (1)](https://images.ctfassets.net/alneenqid6w5/3QINWXoZCkcpqPq00SLR6q/618748bfb039c6a3e757b1655774a8e0/visual-merch-rules-PT-announcement__1_.png)
 
 Ao criar uma regra de merchandising no Admin VTEX em **Storefront > Intelligent Search > Regras de merchandising > Adicionar**, é possível escolher o tipo de editor a ser utilizado. Acesse o guia [Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao) para obter mais informações sobre as diferenças entre o editor manual e o editor visual.
 
diff --git a/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md b/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md
index a6ce60005..50f454f61 100644
--- a/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md
+++ b/docs/announcements/pt/vtex-io-documentation-has-a-new-home.md
@@ -19,7 +19,7 @@ Desde 13 de março de 2020, as documentações do  VTEX IO e VTEX IO Store Frame
 
 Agora, elas devem ser acessadas através do [**VTEX IO Docs**](https://vtex.io/docs), plataforma de documentação que reúne todos os conteúdos disponíveis sobre ambas soluções. 
 
-![vtex-io-docs](//images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/3b50ae0f6b3b3252901ad7597f128c2a/vtex-io-docs.png)
+![vtex-io-docs](https://images.ctfassets.net/alneenqid6w5/3mjm7jrAJybhh11YIBsU7Y/3b50ae0f6b3b3252901ad7597f128c2a/vtex-io-docs.png)
 
 ## Por que estamos realizando esta mudança?
 
@@ -33,7 +33,7 @@ A decisão de remover do Help Center as documentações do VTEX IO e VTEX IO Sto
 
 Abrigando nossa [documentação de API](https://developers.vtex.com/reference), [guias](https://developers.vtex.com/docs) voltados para desenvolvedores que trabalham com integrações e customizações e [Release Notes](https://developers.vtex.com/changelog) sincronizados com tudo de novo que acontece no nosso produto, o [**Developer Portal**](https://developers.vtex.com) - antigo Developer Docs do Help Center - oferece em um só lugar todos os recursos necessários para os usuários mais técnicos da VTEX. 
 
-![developer-portal](//images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/e5bcdea0033bf9dd9ac8b8d2ff120f72/developer-portal.png)
+![developer-portal](https://images.ctfassets.net/alneenqid6w5/7MvPBbDIyOhzeOXqpJ7IqP/e5bcdea0033bf9dd9ac8b8d2ff120f72/developer-portal.png)
 
 Com o objetivo de melhorar a experiência de desenvolvimento na VTEX, o Developer Portal em breve também contará com as documentações do VTEX IO e VTEX IO Store Framework - hoje disponibilizadas no VTEX IO Docs. 
 
diff --git a/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md b/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md
index 4fd05bc93..1e644c1db 100644
--- a/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md
+++ b/docs/announcements/pt/vtex-is-now-available-in-dutch-french-and-korean.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Existem três novas opções de idioma no Admin da VTEX
 
 O admin da VTEX suporta atualmente diferentes opções de idiomas para atender nossos clientes em todo o mundo. Localizamos o nosso produto para melhorar a sua experiência, não apenas por meio de traduções, mas também a nível cultural, levando em conta as particularidades de cada país.  
 
-![PT new locales](//images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/c4201ae259f80a1aa0359441ca1c8dff/PT_new_locales.jpg)
+![PT new locales](https://images.ctfassets.net/alneenqid6w5/4ymaJnFYZxRTjTZmoD54Gy/c4201ae259f80a1aa0359441ca1c8dff/PT_new_locales.jpg)
 
 ## O que mudou?
 Além do português, inglês, espanhol, italiano, romeno e japonês, a partir de maio de 2021, os usuários da VTEX encontrarão três novas opções de idiomas em nosso Admin: holandês, francês e coreano.   
diff --git a/docs/announcements/pt/vtex-login-now-features-recaptcha.md b/docs/announcements/pt/vtex-login-now-features-recaptcha.md
index 826fe5151..e86ca26c0 100644
--- a/docs/announcements/pt/vtex-login-now-features-recaptcha.md
+++ b/docs/announcements/pt/vtex-login-now-features-recaptcha.md
@@ -19,7 +19,7 @@ O login da VTEX por meio de e-mail e senha agora conta com reCAPTCHA, que torna
 
 Usamos o Invisible reCAPTCHA, uma tecnologia do Google que determina quando é necessário confirmar se a tentativa de acesso está sendo feita por um robô ou um humano.
 
-![reCAPTCHA](//images.contentful.com/alneenqid6w5/2obeayJZP6k8q8a6W68sQI/08bbf823714965fd207961a792a94f9f/reCAPTCHA.png)
+![reCAPTCHA](https://images.contentful.com/alneenqid6w5/2obeayJZP6k8q8a6W68sQI/08bbf823714965fd207961a792a94f9f/reCAPTCHA.png)
 
 Isto significa que o pedido de confirmação pode ou não aparecer, dependendo de diversos fatores.
 
diff --git a/docs/announcements/pt/vtex-marketplace-launches-in-2022.md b/docs/announcements/pt/vtex-marketplace-launches-in-2022.md
index 08f0946b7..25a8b51fc 100644
--- a/docs/announcements/pt/vtex-marketplace-launches-in-2022.md
+++ b/docs/announcements/pt/vtex-marketplace-launches-in-2022.md
@@ -29,7 +29,7 @@ Com nossas novas funcionalidades, marketplaces podem:
 
 Vá além do ecommerce tradicional com as [novidades de Marketplace da VTEX](https://content.vtex.com/pt-br/2022-marketplace-release/?utm_source=announcement&utm_medium=organic&utm_campaign=2022_marketplace_release). 
 
-![capa de blog marketplace 2022](//images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/a84a5eb1e72967e9365c6334d33ab1c1/capa_de_blog.png)
+![capa de blog marketplace 2022](https://images.ctfassets.net/alneenqid6w5/6U2cM7UiQOatP0A781yxEk/a84a5eb1e72967e9365c6334d33ab1c1/capa_de_blog.png)
 
 ## O que estamos lançando?
 
@@ -78,7 +78,7 @@ Saiba mais sobre cada funcionalidade a seguir.
 
 ### Seller Portal 
 
-![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 O Seller Portal é uma edição da plataforma VTEX voltada para [sellers](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#vender-em-marketplace) se conectarem e venderem seus produtos em marketplaces hospedados na VTEX. Com o portal, sellers acessam todas as funcionalidades essenciais para a operação de ecommerce em grandes vitrines, trazendo visibilidade e conversão de vendas.
 
@@ -126,7 +126,7 @@ Para facilitar a entrada de novos sellers no Seller Portal, lançamos também a
 
 ### Gestão de sellers
 
-![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 Lançamos a experiência renovada da página [Gestão de Sellers](https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers-beta--6eEiOISwxuAWJ8w6MtK7iv), onde operadores de marketplace [adicionam sellers](https://help.vtex.com/pt/tutorial/adicionar-seller-beta--6q4G4RNqVENr5YMJyindwL), registram suas respectivas informações e administram o status de cada seller. 
 
@@ -141,7 +141,7 @@ _Esta página segue o novo Design System da VTEX, com um visual mais limpo, mode
 
 ### Gerenciamento de anúncios
 
-![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 A eficiência e atuação estratégica de um seller depende da sua visibilidade sobre o envio dos anúncios ao marketplace, além da identificação e correção de erros durante o envio. Para facilitar esse processo, lançamos a funcionalidade [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/gestao-de-anuncios--7MRb9S78aBdZjFGpbuffpE).
 
diff --git a/docs/announcements/pt/we-released-the-new-order-placed.md b/docs/announcements/pt/we-released-the-new-order-placed.md
index 97751952a..5add14ae1 100644
--- a/docs/announcements/pt/we-released-the-new-order-placed.md
+++ b/docs/announcements/pt/we-released-the-new-order-placed.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'A nova versão da página de confirmação de pedido j
 
 No início deste mês divulgamos o lançamento de uma das muitas novidades que a VTEX está desenvolvendo para melhorar ainda mais a experiência do usuário — a nova seção de Meus Pedidos. Hoje lançamos mais uma feature que integra essa seção: a nova versão da página de confirmação de pedido (Order Placed).
 
-![PedidoConfirmado](//images.contentful.com/alneenqid6w5/2Xr5mMmZMs0WAy4i6cK4EC/50c153cf99a137eb55f0d0dbc34ee820/PedidoConfirmado.png)
+![PedidoConfirmado](https://images.contentful.com/alneenqid6w5/2Xr5mMmZMs0WAy4i6cK4EC/50c153cf99a137eb55f0d0dbc34ee820/PedidoConfirmado.png)
 
 Ela agora faz parte do __Checkout Confirmation__, feature responsável pelas páginas de confirmação do Checkout. E traz vantagens importantes para sua loja:
 
@@ -29,7 +29,7 @@ Ativar essa atualização é simples: basta acessar a aba Pedidos no módulo Por
 
 Depois do dia 24 de agosto de 2017, a nova versão será ativada por default, e a antiga será descontinuada. Então fique ligado!
 
-![PedidoConfirmado2](//images.contentful.com/alneenqid6w5/5xM0PRucykSa84SWWO4k2S/0dcf664d17697bdbf8a32b074578af27/PedidoConfirmado2.png)
+![PedidoConfirmado2](https://images.contentful.com/alneenqid6w5/5xM0PRucykSa84SWWO4k2S/0dcf664d17697bdbf8a32b074578af27/PedidoConfirmado2.png)
 
 É provável que você queira atualizar sua customização. Para saber como, veja o tutorial [Customizar as páginas do Checkout Confirmation](/pt/tutorial/customizando-o-checkout-confirmation).
 
diff --git a/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
index 5947c678b..ec7e449d5 100644
--- a/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
@@ -19,7 +19,7 @@ As empresas digitais têm buscado cada vez mais ferramentas que permitam que ela
 
 Dê as boas-vindas à [experiência do novo Admin](https://content.vtex.com/join-new-admin-beta-program-pt/?utm_source=announcement&utm_medium=organic&utm_campaign=new_admin_beta).
 
-![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/were-launching-your-personal-data-set-up-screen.md b/docs/announcements/pt/were-launching-your-personal-data-set-up-screen.md
index 92a94118c..62d36fa8a 100644
--- a/docs/announcements/pt/were-launching-your-personal-data-set-up-screen.md
+++ b/docs/announcements/pt/were-launching-your-personal-data-set-up-screen.md
@@ -19,7 +19,7 @@ Ficou mais fácil editar suas configurações pessoais de acesso ao Admin VTEX.
 
 O time do VTEX ID criou a tela My User, que pode ser facilmente acessada pela topbar do Admin.
 
-![dadosPessoais](//images.contentful.com/alneenqid6w5/3c85FBDbJumIgA0smG4Q2S/2af591bd4d724dadae3adebd7525311b/dadosPessoais.png)
+![dadosPessoais](https://images.contentful.com/alneenqid6w5/3c85FBDbJumIgA0smG4Q2S/2af591bd4d724dadae3adebd7525311b/dadosPessoais.png)
 
 Nela você pode:
 - Ver seu e-mail cadastrado no Admin.
diff --git a/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md b/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md
index 5ce29a06c..c6fd3a2f6 100644
--- a/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md
+++ b/docs/announcements/pt/wishlist-discover-the-new-vtex-app-store-app.md
@@ -24,7 +24,7 @@ O aplicativo está disponível na [VTEX App Store](https://apps.vtex.com/ "VTEX
 - Inclusão de um ícone de coração ao lado de cada produto nas listas de produtos e nas páginas de detalhamento do produto;
 - Criação de uma página para a Lista de Desejos, onde o comprador consegue ver todos os itens e facilmente comprá-los.
 
-![Wishlist Printscreen](//images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
+![Wishlist Printscreen](https://images.ctfassets.net/alneenqid6w5/5EVie6cixnjJTZPoxqa5MG/5a6e2ce9fe25d828a14e0ee9d6df4f80/Screen_Shot_2020-12-07_at_16.04.01.png)
 
 ## Quais os benefícios?
 - Torna a experiência de compra da sua loja mais completa;
diff --git a/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 11586ee1a..60df2c039 100644
--- a/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -21,7 +21,7 @@ A partir do dia 25 de junho de 2019, o usuário que não tiver acesso vinculado
 
 Buscando garantir maior segurança, criamos a possibilidade de limitar perfis de acesso a tela de **Configurações** do módulo Gerenciamento de Pedidos, permitindo que somente alguns usuários editem as informações.
 
-![2019-06-07 17 23 36-Configurações.pt](//images.ctfassets.net/alneenqid6w5/45magq14vJ6nY1opKENj62/f7f22017b6c4fb359d5d0a0211669401/2019-06-07_17_23_36-Configura____es.pt.png)
+![2019-06-07 17 23 36-Configurações.pt](https://images.ctfassets.net/alneenqid6w5/45magq14vJ6nY1opKENj62/f7f22017b6c4fb359d5d0a0211669401/2019-06-07_17_23_36-Configura____es.pt.png)
 
 ## Principais Vantagens
 
@@ -41,7 +41,7 @@ Para fazer isso é necessário adicionar um produto chamado `Checkout` ao perfil
  6. Escolha o tipo de permissão desejada: `Save Order Configuration`, para permitir que o usuário edite e salve modificações na seção de **Pedidos**, ou `Save OrderForm Configuration`, para permitir a edição na seção de **Carrinho**.
  7. Clique em **Salvar**
 
-![GIT-Checkout.pt](//images.ctfassets.net/alneenqid6w5/4nqdHOVWcKnMNdMjLqJhtF/9d285f0e1d5c4f6f3277cbce6f73cfb3/GIT-Checkout.pt.gif)
+![GIT-Checkout.pt](https://images.ctfassets.net/alneenqid6w5/4nqdHOVWcKnMNdMjLqJhtF/9d285f0e1d5c4f6f3277cbce6f73cfb3/GIT-Checkout.pt.gif)
 
 Após adicionar este novo produto a um perfil, certifique-se de que os usuários desejados estão associados a este perfil de acesso.
   
diff --git a/docs/faq/en/ab-testing-why-is-it-not-working-google-analytics.md b/docs/faq/en/ab-testing-why-is-it-not-working-google-analytics.md
index ba890a3bd..1c5fabb96 100644
--- a/docs/faq/en/ab-testing-why-is-it-not-working-google-analytics.md
+++ b/docs/faq/en/ab-testing-why-is-it-not-working-google-analytics.md
@@ -26,10 +26,10 @@ This way, AB Testing will be successful.
 See below the screens with examples of the steps:
 
 __Control Screen__:
-![](//images.contentful.com/alneenqid6w5/3GIGsJXbo4KAMikCqesM6s/e8231671043f3ce763c8faf87718d6d7/testeAB-controle1-300x138.png)
+![](https://images.contentful.com/alneenqid6w5/3GIGsJXbo4KAMikCqesM6s/e8231671043f3ce763c8faf87718d6d7/testeAB-controle1-300x138.png)
 
 __Script Screen__:
-![](//images.contentful.com/alneenqid6w5/7gUgGNnvlmcQyiW4A0A6ao/dac8e58e0931686de3e9e4ae46c66afa/testeAB-script-300x148.png)
+![](https://images.contentful.com/alneenqid6w5/7gUgGNnvlmcQyiW4A0A6ao/dac8e58e0931686de3e9e4ae46c66afa/testeAB-script-300x148.png)
 
 __Template Screen__:
-![](//images.contentful.com/alneenqid6w5/4u6uQHYOPuw6Ws8CYKCISo/d04c5fbcc08a5de8a05a242ef76e7ecf/testeAB-template-300x216.png)
+![](https://images.contentful.com/alneenqid6w5/4u6uQHYOPuw6Ws8CYKCISo/d04c5fbcc08a5de8a05a242ef76e7ecf/testeAB-template-300x216.png)
diff --git a/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
index f14e8a3fd..e3ba3e98a 100644
--- a/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -26,15 +26,15 @@ To do that, we will show you how to remove the customizations using a Chrome nat
 
 1. To open DevTools, open Chrome and click **F12** or **right-click** anywhere on the page and select **Inspect**.
 
-![Customizations1](//images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
+![Customizations1](https://images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
 
 2. Search for the **Request Blocking** function to block all customizations made via CSS, JavaScript, and Google Tag Manager. Click on the three vertical dots on the top right of the page, as indicated in the image below. Select **More Tools** and then **Request Blocking**.
 
-![Customizations2](//images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
+![Customizations2](https://images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
 
 3. A box will be displayed, as in the image below:
 
-![Customizations3](//images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
+![Customizations3](https://images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
 
 4. Click on the **Request Blocking** tab.
 
@@ -49,7 +49,7 @@ Now you will determine the features you want to block. This configuration must b
 
 The box will finally be displayed as in the image below:
 
-![Customizations4](//images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
+![Customizations4](https://images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
 
 Please remember that this configuration must be done only __once__.
 
@@ -59,11 +59,11 @@ Please remember that this configuration must be done only __once__.
 
 2. This configuration will be set by default, with all options for blocking enabled.
 
-![Customizations5](//images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
+![Customizations5](https://images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
 
 3. Now refresh the page by clicking on **F5**. The page will be displayed without custom components.
 
-![Customizations6](//images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
+![Customizations6](https://images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
 
 4. To view customizations again, deselect the checkbox **Enable request blocking** and refresh the page.
 
diff --git a/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md b/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
index 4756dab04..dcc9eb361 100644
--- a/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
+++ b/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
@@ -23,8 +23,8 @@ __To access this spreadsheet, follow the steps below:__
 1. Access the __OMS__ module.
 2. Click the __Filter__ icon.
 3. Do a search __by period__ (remembering that the maximum allowed range is up to 6 months. In case you want to search for a period of 1 year, for example, search twice).
-4. When returning to the filtered list of orders, __click the export icon__.![exportacaoOMS](//images.contentful.com/alneenqid6w5/3pX1xFqvS0uMOEe8OUquci/81e2be7c1948d62a863cfccfc36f18a9/exportacaoOMS.png)
-5. A progress bar will appear. So, to finish, you need to click __Export xxx orders to e-mail__.![ExportarOMS](//images.contentful.com/alneenqid6w5/3Z7h82etgIuQcUI6iGsgyk/11bbadc4b3c2174c82844e9125af8e50/ExportarOMS.png)
+4. When returning to the filtered list of orders, __click the export icon__.![exportacaoOMS](https://images.contentful.com/alneenqid6w5/3pX1xFqvS0uMOEe8OUquci/81e2be7c1948d62a863cfccfc36f18a9/exportacaoOMS.png)
+5. A progress bar will appear. So, to finish, you need to click __Export xxx orders to e-mail__.![ExportarOMS](https://images.contentful.com/alneenqid6w5/3Z7h82etgIuQcUI6iGsgyk/11bbadc4b3c2174c82844e9125af8e50/ExportarOMS.png)
 
 Your request will enter a queue, which can be followed through the OMS. When your turn arrives, you will receive the orders spreadsheet in your email.
 
diff --git a/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
index 00820554c..5c1249dd1 100644
--- a/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -30,7 +30,7 @@ For this reason, to access the change seller feature, you must configure the aff
 - __Use Payment Processor Recommended Behavior__.
 - __Disabled: Do Not Auto Settle__.
 
-![AutoSettlement](//images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/a085c82de3cd5dfac48f16deeb7c4cdd/AutoSettlement.png)
+![AutoSettlement](https://images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/a085c82de3cd5dfac48f16deeb7c4cdd/AutoSettlement.png)
 
 ### If I opted for a non-automatic settlement behavior, when will the payment be settled?
 
diff --git a/docs/faq/en/file-upload-button-is-not-displayed-at-cms.md b/docs/faq/en/file-upload-button-is-not-displayed-at-cms.md
index e829d47ce..b1fb320bc 100644
--- a/docs/faq/en/file-upload-button-is-not-displayed-at-cms.md
+++ b/docs/faq/en/file-upload-button-is-not-displayed-at-cms.md
@@ -21,7 +21,7 @@ If you have this problem on Google Chrome, just activate the Flash plug-in as fo
 1. Click on the information button or on the padlock in front of the current URL;
 2. In the line corresponding to the Flash, which normally shows "Perguntar (padrão)", select "Sempre permitir neste site".
 
-![chrome-flash](//images.contentful.com/alneenqid6w5/URF5k1wvQsaAiSoOeo4WI/5560f944b3b3fabb21bfbf4cebe21037/chrome-flash.jpg)
+![chrome-flash](https://images.contentful.com/alneenqid6w5/URF5k1wvQsaAiSoOeo4WI/5560f944b3b3fabb21bfbf4cebe21037/chrome-flash.jpg)
 
 Normally this problem is related to the availability of Flash Player on the browser for the site accessed. 
 
diff --git a/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md b/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md
index 576e7eef2..186544234 100644
--- a/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md
+++ b/docs/faq/en/how-do-i-find-the-order-nsu-and-tid.md
@@ -23,5 +23,5 @@ NSU and TID are payment data that remain stored in the __Payment__ module, in th
 
 This information is notified to VTEX during the transactions and organized for a simple view in **+ Information** in the [details of the order](/en/tutorial/how-to-view-the-orders-details), as illustrated below:
 
-![mais-informações-detalhes-pedido en](//images.ctfassets.net/alneenqid6w5/3ncJnNqpXeGWmlhalll0Ck/507f1008c7121f7722f3d694faddc94b/mais-informa____es-detalhes-pedido_en.png)
+![mais-informações-detalhes-pedido en](https://images.ctfassets.net/alneenqid6w5/3ncJnNqpXeGWmlhalll0Ck/507f1008c7121f7722f3d694faddc94b/mais-informa____es-detalhes-pedido_en.png)
 
diff --git a/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md b/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md
index 9e6454088..421498545 100644
--- a/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md
+++ b/docs/faq/en/how-to-associate-two-promotions-to-the-same-coupon.md
@@ -31,7 +31,7 @@ Check below how to perform this process:
 4. Proceed to the __What are the conditions for the benefit to be valid?__ section.
 5. Enter the coupon code in __utm_source__.
 
-  ![Sincronizar promoções no mesmo cupom - 1 - EN](//images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/8393ce300e19c709d554f7794ce06a43/7yJhwPnclx3tCiJdgpcYyv_-_EN.png)
+  ![Sincronizar promoções no mesmo cupom - 1 - EN](https://images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/8393ce300e19c709d554f7794ce06a43/7yJhwPnclx3tCiJdgpcYyv_-_EN.png)
 
 6. Click 'Create coupon from UTMs above'.
 7. Click 'Save'.
@@ -39,6 +39,6 @@ Check below how to perform this process:
 9. Repeat the process with the second regular promotion.
 10. In the end, both promotions must present the same UTM.
 
-  ![Sincronizar promoções no mesmo cupom - 2 - EN](//images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/491e1a1df904baa955571eed701be5f5/5nhdQy1Y4YWs4pHHokSA44_-_EN.png)
+  ![Sincronizar promoções no mesmo cupom - 2 - EN](https://images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/491e1a1df904baa955571eed701be5f5/5nhdQy1Y4YWs4pHHokSA44_-_EN.png)
 
 With this, the customer can get a full discount of both values before closing the purchase.
diff --git a/docs/faq/en/how-to-configure-mercadopago-transparente.md b/docs/faq/en/how-to-configure-mercadopago-transparente.md
index 63406de71..a345bf0fb 100644
--- a/docs/faq/en/how-to-configure-mercadopago-transparente.md
+++ b/docs/faq/en/how-to-configure-mercadopago-transparente.md
@@ -32,7 +32,7 @@ These configurations take place on your Google TagManager.
 8. Save the trigger;
 9. Click on the **Criar Tag **button, enter a name for this tag and Save.
 
-![](//images.contentful.com/alneenqid6w5/YndMcdc0aAw2GKYU0EyU2/c917ac451cfeb262d8354164c6caa285/MercadoPagoTransparente_1_PT.gif)
+![](https://images.contentful.com/alneenqid6w5/YndMcdc0aAw2GKYU0EyU2/c917ac451cfeb262d8354164c6caa285/MercadoPagoTransparente_1_PT.gif)
 
 ## Creating the second tag
 
@@ -49,4 +49,4 @@ These configurations take place on your Google TagManager.
 9. Click on the **Criar Tag **button, enter a name for this tag and Save;
 10. In the upper right-hand corner, click on **Publicar** and then on **Publicar****.**
 
-![](//images.contentful.com/alneenqid6w5/32NgyD7KNqicqiASoIUEkK/892ab0a77b4bf2295dcb72d6335de49e/MercadoPagoTransparente_2_PT.gif)
+![](https://images.contentful.com/alneenqid6w5/32NgyD7KNqicqiASoIUEkK/892ab0a77b4bf2295dcb72d6335de49e/MercadoPagoTransparente_2_PT.gif)
diff --git a/docs/faq/en/how-to-disable-the-two-factor-authentication.md b/docs/faq/en/how-to-disable-the-two-factor-authentication.md
index 0d28b17fd..ae910d3ba 100644
--- a/docs/faq/en/how-to-disable-the-two-factor-authentication.md
+++ b/docs/faq/en/how-to-disable-the-two-factor-authentication.md
@@ -16,8 +16,8 @@ legacySlug: how-to-disable-the-two-factor-authentication
 
 To disable the login to VTEX Admin through two factor authentication, follow these steps:
 
-1. Login with your user and password;![2FA 1](//images.contentful.com/alneenqid6w5/4cgNDZ16dGoQGKK6MKeK0m/8afc25a77f0e1554a03a788de5bc19bb/2FA_1.png)
-2. Fill the field with the code that was sent to your cell phone and click on the button **Configure telefone**;![2FA 2](//images.contentful.com/alneenqid6w5/4uMb0UXDNSMa4sMAOSMMaO/2a4eb422eccd35fc4a491018c4cc1517/2FA_2.png)
-3. Click on the button **Remover telefone**.![2FA 3](//images.contentful.com/alneenqid6w5/1p3qDi9viUgWqWCAyiuom0/456e8eefa5fc1f5dc845f9715e120304/2FA_3.png)
+1. Login with your user and password;![2FA 1](https://images.contentful.com/alneenqid6w5/4cgNDZ16dGoQGKK6MKeK0m/8afc25a77f0e1554a03a788de5bc19bb/2FA_1.png)
+2. Fill the field with the code that was sent to your cell phone and click on the button **Configure telefone**;![2FA 2](https://images.contentful.com/alneenqid6w5/4uMb0UXDNSMa4sMAOSMMaO/2a4eb422eccd35fc4a491018c4cc1517/2FA_2.png)
+3. Click on the button **Remover telefone**.![2FA 3](https://images.contentful.com/alneenqid6w5/1p3qDi9viUgWqWCAyiuom0/456e8eefa5fc1f5dc845f9715e120304/2FA_3.png)
 
-With that, the two factor authentication will be disabled for your account and you will be redirected to the Admin.![2FA 4](//images.contentful.com/alneenqid6w5/5e37R8mEEMuSWwmMAmsGAC/b9caea8225ee2c4421a430553a6f51ad/2FA_4.png)
+With that, the two factor authentication will be disabled for your account and you will be redirected to the Admin.![2FA 4](https://images.contentful.com/alneenqid6w5/5e37R8mEEMuSWwmMAmsGAC/b9caea8225ee2c4421a430553a6f51ad/2FA_4.png)
diff --git a/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md b/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md
index bfe907e92..cbba8a074 100644
--- a/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md
+++ b/docs/faq/en/i-cant-edit-a-required-field-on-master-data.md
@@ -19,11 +19,11 @@ Editing the fields that appear as mandatory in __Profile System__ in __Master Da
 1. In the admin menu, select the __Master Data__ module.
 2. Make sure that you're in the __Applications__ tab, in __Quick Links__.
 3. Click on settings in __Profile System__.
-![MasterDataTutorial 1 UM](//images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
+![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
 4. Click on the __pencil__ next to the item you wish to configure.
-![MasterDataTutorial2](//images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
+![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
 5. Click on __Layout Outlines__.
 6. In __Section 1__, choose the item of the field you wish to configure.
-7. In __Advanced field settings, select __Mandatory Field__ on the form. ![MasterDataTutorial3](//images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
+7. In __Advanced field settings, select __Mandatory Field__ on the form. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
 The option may be changed whenever it may be necessary. 
 
diff --git a/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md b/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
index 92c6b370e..9f285cb38 100644
--- a/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
+++ b/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
@@ -16,6 +16,6 @@ legacySlug: i-received-the-message-error-the-limit-of-activated-calculators-has-
 
 This message indicates that the maximum number of promotions has been reached, and it is not possible to create the promotion that was being configured. You can check this information on the promotions management screen (`{AccountName}.vtexcommercestable.com.br/admin/rnb`), as shown in the image below.
 
-![](//images.contentful.com/alneenqid6w5/3MZkA9wEMgYO0mYi2YcQSa/b132514fefacffecfeed56a99307daaf/promo__es.jpg)
+![](https://images.contentful.com/alneenqid6w5/3MZkA9wEMgYO0mYi2YcQSa/b132514fefacffecfeed56a99307daaf/promo__es.jpg)
 
 You must review your active promotions, in order to adjust and rearrange them, so that not so many units are necessary. Usually, It is possible to join several rules in just one promotion. This way, you can improve the performance of the cart, and the organization of promotions.
diff --git a/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 3e26f8b5b..2d1c55776 100644
--- a/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/en/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -31,6 +31,6 @@ For manual inclusion of specific SKUs, follow these step-by-step instructions:
 5. Name your Collection (the other fields are not to be filled).
 6. Insert the SKUs in the field and __separate them with commas__.
 
-![recurrence-specific-skus](//images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
+![recurrence-specific-skus](https://images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
 
 Finally, give a name to the __Group__ of your Collection and click __Save Group__.
diff --git a/docs/faq/en/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md b/docs/faq/en/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
index d3277f941..84ddf2784 100644
--- a/docs/faq/en/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
+++ b/docs/faq/en/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
@@ -19,5 +19,5 @@ It is usual for the store to make changes to the placeholders of a layout in the
 Usually this happens because the store saves the placeholder after the changes but does not save the layout.
 
 Whenever you change a placeholder, remember to:
-1. Save the placeholder.![savePlaceholder](//images.contentful.com/alneenqid6w5/3CefNlrWxWOO8kgyKEkMMk/3deea3f44d5f21e037e799a07500f147/savePlaceholder.png)
-2. Save the layout.![saveLayout](//images.contentful.com/alneenqid6w5/1WUC8Yy2Vq2qEOAuQMG0km/83bce62e6f8145112655dae251474bf5/saveLayout.png)
+1. Save the placeholder.![savePlaceholder](https://images.contentful.com/alneenqid6w5/3CefNlrWxWOO8kgyKEkMMk/3deea3f44d5f21e037e799a07500f147/savePlaceholder.png)
+2. Save the layout.![saveLayout](https://images.contentful.com/alneenqid6w5/1WUC8Yy2Vq2qEOAuQMG0km/83bce62e6f8145112655dae251474bf5/saveLayout.png)
diff --git a/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md b/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md
index 11d2eec37..b8a4dfae4 100644
--- a/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md
+++ b/docs/faq/en/kitlook-is-not-displayed-in-the-shop-window.md
@@ -32,7 +32,7 @@ __Fill in the Label field__
 4. Go to the __Images__ tab;
 5. Enter a term to populate the __Label__;
 
-  ![Kit Look - Label - EN](//images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/2789e7a69d5258c78d192a47ecc2aff5/7FR879Lzl3eEDmAHiBV0TV_en.jpg)
+  ![Kit Look - Label - EN](https://images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/2789e7a69d5258c78d192a47ecc2aff5/7FR879Lzl3eEDmAHiBV0TV_en.jpg)
 
 6. Click __Save__.
 
diff --git a/docs/faq/en/nao-encontro-uma-colecao-o-que-fazer.md b/docs/faq/en/nao-encontro-uma-colecao-o-que-fazer.md
index c75d4b5a0..3dc1c1a20 100644
--- a/docs/faq/en/nao-encontro-uma-colecao-o-que-fazer.md
+++ b/docs/faq/en/nao-encontro-uma-colecao-o-que-fazer.md
@@ -22,8 +22,8 @@ By default, the CMS module only displays the __last 20 collections__ updated.
 
 So if your store has more than 20 collections, it's normal for some of them not to appear in the list shown in the CMS.
 
-![findCollection1](//images.contentful.com/alneenqid6w5/1DM1TNjCKYsY0KQkMgycGm/c49a70d5570d62c993539114d8596549/findCollection1.png)
+![findCollection1](https://images.contentful.com/alneenqid6w5/1DM1TNjCKYsY0KQkMgycGm/c49a70d5570d62c993539114d8596549/findCollection1.png)
 
 But you can fetch any collection using the __search field__ (Find), including those that are not displayed by default.
 
-![findCollection2](//images.contentful.com/alneenqid6w5/6LBUTpvCH64Uc2CQEwiigk/5739b97f92b27ec9fc40fb4e93ffb2af/findCollection2.png)
+![findCollection2](https://images.contentful.com/alneenqid6w5/6LBUTpvCH64Uc2CQEwiigk/5739b97f92b27ec9fc40fb4e93ffb2af/findCollection2.png)
diff --git a/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
index 6d0196428..c4f16f1d8 100644
--- a/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -25,7 +25,7 @@ When the ERP queries and enters this order in your base, it has to inform VTEX t
 
 > To do so, click on the arrow symbol on top of the **Start handling** box in the order flow diagram below.
 
-![ProntoParaManuseio](//images.contentful.com/alneenqid6w5/5VSeCrxvSogcI46mgkYkm8/84ea107934684ada917d6a8163aeae34/ProntoParaManuseio.png)
+![ProntoParaManuseio](https://images.contentful.com/alneenqid6w5/5VSeCrxvSogcI46mgkYkm8/84ea107934684ada917d6a8163aeae34/ProntoParaManuseio.png)
 
 > You must have a [OMS - Full access role](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") in order to perform this action.
 
diff --git a/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md b/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md
index a29c22c50..731a64b8d 100644
--- a/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md
+++ b/docs/faq/en/some-gateway-affiliations-are-highlighted-in-yellow-why.md
@@ -18,7 +18,7 @@ In __Gateway Affiliation__, you can view the list of all settings made. However,
 
 This means that these affiliations are not enabled, but being tested. You may confirm this information by clicking on the affiliation highlighted. 
 
-![afiliação-gateway-teste en](//images.ctfassets.net/alneenqid6w5/4o2BXZ5q9iyQqyO064sSwm/b0f8f391add763acdad6a91686bcd730/gateway_teste_en.png)
+![afiliação-gateway-teste en](https://images.ctfassets.net/alneenqid6w5/4o2BXZ5q9iyQqyO064sSwm/b0f8f391add763acdad6a91686bcd730/gateway_teste_en.png)
 
 
 That is, the settings that have not yet been enabled are highlighted in a different color.
diff --git a/docs/faq/en/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md b/docs/faq/en/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
index 8c500dba4..ce4ed2368 100644
--- a/docs/faq/en/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
+++ b/docs/faq/en/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
@@ -22,14 +22,14 @@ This happens when there is some error in the SKU registration in the seller.
 
 To identify what the error is, follow the steps below:
 1. Enter the __Suggestions__ module.
-2. Click the SKU that the marketplace did not accept.![erroSuggestion1](//images.contentful.com/alneenqid6w5/2T4ywpCeacosAGoQCS0k4M/f27f1729b879a02cd11f5bc916c8f8a6/erroSuggestion1.png)
+2. Click the SKU that the marketplace did not accept.![erroSuggestion1](https://images.contentful.com/alneenqid6w5/2T4ywpCeacosAGoQCS0k4M/f27f1729b879a02cd11f5bc916c8f8a6/erroSuggestion1.png)
 3. Enter the browser __developer tools__ (for this, if you are using Google Chrome, press `F12` on Windows or` Command + Option + I` on the Mac).
 4. In the developer tools, click the __Network__ tab.
-5. Still in the developer tools, click the option __All__.![erroSuggestion2](//images.contentful.com/alneenqid6w5/tXLZF0IEO4KKa6O4WuQg6/58adc90c3afa5ce2d02238079cabd958/erroSuggestion2.png)
+5. Still in the developer tools, click the option __All__.![erroSuggestion2](https://images.contentful.com/alneenqid6w5/tXLZF0IEO4KKa6O4WuQg6/58adc90c3afa5ce2d02238079cabd958/erroSuggestion2.png)
 6. Click the __Activate__ button of the Suggestions module.
 7. You will see a list of the calls activated by the Accept button.
-8. If one of them is in red and has `400` status, as in the image below, click on this call.![erroSuggestion3](//images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)
-9. You will see below the description of the error that caused the failure to process the SKU suggestion.![erroSuggestion4](//images.contentful.com/alneenqid6w5/4yN8mswXdYoKO6wcsyO0eW/2de11f133c3ee911c1e712d7b1188711/erroSuggestion4.png)
+8. If one of them is in red and has `400` status, as in the image below, click on this call.![erroSuggestion3](https://images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)
+9. You will see below the description of the error that caused the failure to process the SKU suggestion.![erroSuggestion4](https://images.contentful.com/alneenqid6w5/4yN8mswXdYoKO6wcsyO0eW/2de11f133c3ee911c1e712d7b1188711/erroSuggestion4.png)
 
 To resolve the problem, the seller must resolve the error pointed out in this description.
 
diff --git a/docs/faq/en/understanding-the-dashboard.md b/docs/faq/en/understanding-the-dashboard.md
index ff513b033..6077833ef 100644
--- a/docs/faq/en/understanding-the-dashboard.md
+++ b/docs/faq/en/understanding-the-dashboard.md
@@ -22,7 +22,7 @@ To access the Dashboard, click on the **License Manager** in the top menu of the
 
 The Dashboard includes 3 charts. In the first chart, you can compare the average loading time of your store (in red) to the average loading time of all other VTEX stores (in blue). See below an example of this chart.
 
-![](//images.contentful.com/alneenqid6w5/2z4iBEY5UEkqcmsa0KEgoi/3d661f25118a2e876d20a565ebfc88f9/dashboard-chart1-560x320.png)
+![](https://images.contentful.com/alneenqid6w5/2z4iBEY5UEkqcmsa0KEgoi/3d661f25118a2e876d20a565ebfc88f9/dashboard-chart1-560x320.png)
 
 Based on this chart, you can notice if a slowness in the system is affecting only your store or all VTEX stores. You will also be able to view whether a potential peak in loading time still persists or if it was just momentary. _It is _also_ important to mention that peaks do not necessarily mean a problem, _since the chart naturally reflects the behavior of your customers and a greater number of accesses at certain times of the day. As time goes by, you will get used to the behavior of your store and be able to distinguish uncommon behaviors.
 
@@ -30,7 +30,7 @@ Based on this chart, you can notice if a slowness in the system is affecting onl
 
 In the second chart, you can also view your store’s average loading time, but, this time, it will be divided in the different factors that make up a webpage uploading time: network time (in blue), DOM tree processing (in red) and page rendering in the browser (yellow).
 
-![](//images.contentful.com/alneenqid6w5/2DMi5uS3awigGGIAEKCqea/b95fc4689141764c25b5fd506eeaac33/2.jpg)
+![](https://images.contentful.com/alneenqid6w5/2DMi5uS3awigGGIAEKCqea/b95fc4689141764c25b5fd506eeaac33/2.jpg)
 
 You will be able to distinguish whether a delay in page loading is being caused, for example, by a delay in response from server (NetworkTime), an error in JavaScript (DomProcessing), or a heavy image (PageRendering).
 
diff --git a/docs/faq/en/understanding-vtex-email-capture-system.md b/docs/faq/en/understanding-vtex-email-capture-system.md
index d092ebb92..17f72c5ed 100644
--- a/docs/faq/en/understanding-vtex-email-capture-system.md
+++ b/docs/faq/en/understanding-vtex-email-capture-system.md
@@ -50,5 +50,5 @@ So that the <a href="https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandon
 Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
 </div>
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/faq/en/website-with-error-how-to-fix-it.md b/docs/faq/en/website-with-error-how-to-fix-it.md
index a90263cce..6ff2ae979 100644
--- a/docs/faq/en/website-with-error-how-to-fix-it.md
+++ b/docs/faq/en/website-with-error-how-to-fix-it.md
@@ -23,7 +23,7 @@ However, if it's yellow, it means there is an error.
 Below are the steps to adjust it:
 
 1. Click on the website.
-2. Select the Binding on the screen (line highlighted in the image below), and click on __Update__.![Binding 1](//images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
+2. Select the Binding on the screen (line highlighted in the image below), and click on __Update__.![Binding 1](https://images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
 3. On the screen displayed, the __Store name from License Manager__ field will be blank; click on the arrow that appears in this field and select the name of your store.
-4. Click on __Save Binding__.![Binding 2](//images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
+4. Click on __Save Binding__.![Binding 2](https://images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
 5. Click on __Websites__ again to update the page, and that’s it! The little globe will appear in blue, which means that now this is right.
diff --git a/docs/faq/en/what-are-pre-installed-apps.md b/docs/faq/en/what-are-pre-installed-apps.md
index 706240271..b5c64ca87 100644
--- a/docs/faq/en/what-are-pre-installed-apps.md
+++ b/docs/faq/en/what-are-pre-installed-apps.md
@@ -18,7 +18,7 @@ The first time you access your account through VTEX IO CLI, you will see there a
 
 They have been previously installed and are responsible for performing some basic functions.
 
-![appList](//images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
+![appList](https://images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
 
 For example:
 - __admins-app__: renders the page of the new VTEX administrative panel.
diff --git a/docs/faq/en/what-deleting-a-sku-seller-means.md b/docs/faq/en/what-deleting-a-sku-seller-means.md
index de1cc9a5b..ecf8389dc 100644
--- a/docs/faq/en/what-deleting-a-sku-seller-means.md
+++ b/docs/faq/en/what-deleting-a-sku-seller-means.md
@@ -14,7 +14,7 @@ locale: en
 legacySlug: what-deleting-a-sku-seller-means
 ---
 
-![excluir](//images.contentful.com/alneenqid6w5/3H8ijBZBEseoomo0wyMKoi/fea00e532fc957357b8794a1afc278ba/excluir.png)
+![excluir](https://images.contentful.com/alneenqid6w5/3H8ijBZBEseoomo0wyMKoi/fea00e532fc957357b8794a1afc278ba/excluir.png)
 
 When you delete a Seller SKU, it is removed from the Marketplace catalogue. This means that **it will no longer appear in the list of SKUs**.
 
diff --git a/docs/faq/en/what-delinking-a-sku-seller-means.md b/docs/faq/en/what-delinking-a-sku-seller-means.md
index 9e6011f96..dd4fe0c69 100644
--- a/docs/faq/en/what-delinking-a-sku-seller-means.md
+++ b/docs/faq/en/what-delinking-a-sku-seller-means.md
@@ -14,7 +14,7 @@ locale: en
 legacySlug: what-delinking-a-sku-seller-means
 ---
 
-![desvincular](//images.contentful.com/alneenqid6w5/2fJNaa6xkEC0CwguKWK4o0/f6f8625d2409ff921826ffb913598eaf/desvincular.png)
+![desvincular](https://images.contentful.com/alneenqid6w5/2fJNaa6xkEC0CwguKWK4o0/f6f8625d2409ff921826ffb913598eaf/desvincular.png)
 
 When you delink a Seller SKU, it will **no longer be shown as available** in the Marketplace.
 
diff --git a/docs/faq/en/what-is-url-mapping-301-redirect.md b/docs/faq/en/what-is-url-mapping-301-redirect.md
index ab04ba13f..8454f5494 100644
--- a/docs/faq/en/what-is-url-mapping-301-redirect.md
+++ b/docs/faq/en/what-is-url-mapping-301-redirect.md
@@ -20,11 +20,11 @@ All mapping activities recorded will be executed within the 301 type. The 301 re
 
 URL mapping is recorded in the Portal Manager. In the “E-Commerce” module, go to the menu “Configurações &gt; Portal”:
 
-![](//images.contentful.com/alneenqid6w5/2sLb71Ajkg8s4MIOgCymsO/de7f2f3747389d99ee8100d9cf8f1093/mapeamento1.png)
+![](https://images.contentful.com/alneenqid6w5/2sLb71Ajkg8s4MIOgCymsO/de7f2f3747389d99ee8100d9cf8f1093/mapeamento1.png)
 
 In the Portal Management, go to “Mapeamento de Urls”:
 
-![](//images.contentful.com/alneenqid6w5/5xi3Mase2skUgcI0cU2e28/8459c10133f623d74d55d7c28075b408/mapeamento2.png)
+![](https://images.contentful.com/alneenqid6w5/5xi3Mase2skUgcI0cU2e28/8459c10133f623d74d55d7c28075b408/mapeamento2.png)
 
 There are two ways to Add/Change a URL Mapping:
 1. Manually
diff --git a/docs/faq/en/what-should-i-do-when-there-are-problems-with-a-transaction.md b/docs/faq/en/what-should-i-do-when-there-are-problems-with-a-transaction.md
index c9d0c550e..f2f75b881 100644
--- a/docs/faq/en/what-should-i-do-when-there-are-problems-with-a-transaction.md
+++ b/docs/faq/en/what-should-i-do-when-there-are-problems-with-a-transaction.md
@@ -25,10 +25,10 @@ Sometimes there may be a breakdown in communications between VTEX and the partne
 In these cases logs are generated or the request is held in a loop. If erratic behavior is noted, the quickest solution is to check whether the request status is the same in both platforms. For instance, the Gateway may have updated the Status to "Settling", but subsequently reports that the Status is not correct, when in fact it is. Here is an example:
 
 On February 8, VTEX received a notification from Gateway of a change of Status.
-![2017-04-11-17 28 32-4820587- -VTEX-PCI-Gateway-300x65](//images.contentful.com/alneenqid6w5/7us92BzXFYwyQsUqWQa0sM/9c8e7dc490e5497bf8cfa16e0f7874ce/2017-04-11-17_28_32-4820587-_-VTEX-PCI-Gateway-300x65.png) 
+![2017-04-11-17 28 32-4820587- -VTEX-PCI-Gateway-300x65](https://images.contentful.com/alneenqid6w5/7us92BzXFYwyQsUqWQa0sM/9c8e7dc490e5497bf8cfa16e0f7874ce/2017-04-11-17_28_32-4820587-_-VTEX-PCI-Gateway-300x65.png) 
 
 On April 3, the gateway returns an error in the Status.
-![2017-04-11-17 26 40-4820587- -VTEX-PCI-Gateway-300x87](//images.contentful.com/alneenqid6w5/35WTOXDAC4WgS0Ki866SSS/6d7f6ed699ef653d79d709c97320d10c/2017-04-11-17_26_40-4820587-_-VTEX-PCI-Gateway-300x87.png)
+![2017-04-11-17 26 40-4820587- -VTEX-PCI-Gateway-300x87](https://images.contentful.com/alneenqid6w5/35WTOXDAC4WgS0Ki866SSS/6d7f6ed699ef653d79d709c97320d10c/2017-04-11-17_26_40-4820587-_-VTEX-PCI-Gateway-300x87.png)
 
 Another example would be if the Gateway (partner) reports that it does not have full details of a credit card to complete a purchase. However, the transaction details at the top of the page show that the information exists - the order could not have been completed without this information. The solution here would be the same, to contact your Gateway.
 
diff --git a/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md b/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md
index ec7614f6e..cdde5d03b 100644
--- a/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md
+++ b/docs/faq/en/what-to-do-when-my-exported-report-does-not-reach-my-email.md
@@ -23,8 +23,8 @@ However, there is a way to extract this report manually by accessing Master Data
 Let's see how in the following step-by-step:
 
 1. Enter the __Master Data__;
-2. Click __"Exportations"__;![3WNNUZ8EgDZ4iYv8e0OyQG](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
-3. Make sure that the tab currently open is __"Applications"__;![7ecXBGaCeC3hTaO0lODPq1](//images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
+2. Click __"Exportations"__;![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
+3. Make sure that the tab currently open is __"Applications"__;![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
 4. Under __"Export Status"__, click the report you want to download.
 
 With this, you'll be able access the content even if the original email has not arrived.
diff --git a/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
index adb7f6a8c..78694cc04 100644
--- a/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -16,7 +16,7 @@ legacySlug: what-to-do-when-the-avise-me-doesnt-show
 
 There is a situation in which, despite having [set up the “Notify me” option](/en/tutorial/set-up-the-avise-me) correctly, it does not appear. This happens **when the category display type is marked as “List of SKUs”.**
 
-![categoria-lista-de-skus EN](//images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
+![categoria-lista-de-skus EN](https://images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
 
 In this case, in addition to the default settings, the use of the `vtex.cmc:SkuSelection` control is required, even if there is only one SKU per page.
 
diff --git a/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md b/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
index 473727696..025b18db2 100644
--- a/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
+++ b/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
@@ -18,7 +18,7 @@ A common mistake in payment approval at the **Orders** module is the lack of inv
 
 In such case, when you try to approve the payment in **Orders**, you will see the following error:
 
-![error authorize fulfillment](//images.contentful.com/alneenqid6w5/5Wvwem2kucqsOIYKq4WW00/23b0ffb4209565da148382c3299e2bac/error_authorize_fulfillment.png)
+![error authorize fulfillment](https://images.contentful.com/alneenqid6w5/5Wvwem2kucqsOIYKq4WW00/23b0ffb4209565da148382c3299e2bac/error_authorize_fulfillment.png)
 
 To confirm that this is the problem, in the [order details page](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), click `View Interactions` to see the order details.
 
diff --git a/docs/faq/en/where-can-i-see-my-mercado-pago-transparente-credentials.md b/docs/faq/en/where-can-i-see-my-mercado-pago-transparente-credentials.md
index 7ddcaeb01..7cb9aeacd 100644
--- a/docs/faq/en/where-can-i-see-my-mercado-pago-transparente-credentials.md
+++ b/docs/faq/en/where-can-i-see-my-mercado-pago-transparente-credentials.md
@@ -18,8 +18,8 @@ _Part of the configurations documented in this article are done in an environmen
 
 To access your credentials in Mercado Pago Transparente, access its configurations of, in the PCI Gateway module, and proceed as follows.
 
-1. On the menu on the right, below "Get Credentials", click on **Consultar**. This link will take you to the Mercado Pago authentication page.![2017-01-26 19_37_19-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/4hKomsptCEgGWUsyw4e4GM/09fba68bccee98e6c7d13f6ba4112d6a/2017-01-26-19_37_19-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x140.png)
-2. Below “How to obtain my access\_token”, click on **Credentials**.![2017-01-26 19_43_49-Authentication - MercadoPago Developers](//images.contentful.com/alneenqid6w5/1ZM0tXM4DWk6SEE68ecU4m/0f5802acc942e3ca7ac7d1760754cd43/2017-01-26-19_43_49-Authentication-MercadoPago-Developers-279x300.png)
-3. You will find your credentials on the **Checkout básico** tab.![2017-01-26 19_48_02-MercadoPago - Credenciais](//images.contentful.com/alneenqid6w5/6hgEPEEkWkAqY2u80cqeGI/8152d6e0a24defb9986335be54a0e169/2017-01-26-19_48_02-MercadoPago-Credenciais-300x88.png)
+1. On the menu on the right, below "Get Credentials", click on **Consultar**. This link will take you to the Mercado Pago authentication page.![2017-01-26 19_37_19-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/4hKomsptCEgGWUsyw4e4GM/09fba68bccee98e6c7d13f6ba4112d6a/2017-01-26-19_37_19-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x140.png)
+2. Below “How to obtain my access\_token”, click on **Credentials**.![2017-01-26 19_43_49-Authentication - MercadoPago Developers](https://images.contentful.com/alneenqid6w5/1ZM0tXM4DWk6SEE68ecU4m/0f5802acc942e3ca7ac7d1760754cd43/2017-01-26-19_43_49-Authentication-MercadoPago-Developers-279x300.png)
+3. You will find your credentials on the **Checkout básico** tab.![2017-01-26 19_48_02-MercadoPago - Credenciais](https://images.contentful.com/alneenqid6w5/6hgEPEEkWkAqY2u80cqeGI/8152d6e0a24defb9986335be54a0e169/2017-01-26-19_48_02-MercadoPago-Credenciais-300x88.png)
  
 _The correct credentials are `CLIENT\_ID` and `CLIENT\_SECRET`. They are in the **Checkout básico** tab, not in Checkout transparente._
diff --git a/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md b/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md
index c7c657e27..ad10f0d59 100644
--- a/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md
+++ b/docs/faq/en/why-can-t-i-change-the-fields-in-a-group.md
@@ -26,14 +26,14 @@ Once that field has been located, follow the instructions below:
 
 1. Access the __Catalog__ module
 2. Click on __Categories__
-![ENgrupo1](//images.ctfassets.net/alneenqid6w5/1FV4cfZ09pHFMm5PQQjh7I/67df4c591f88db3ae47f057ad81b5d49/ENgrupo1.PNG)
+![ENgrupo1](https://images.ctfassets.net/alneenqid6w5/1FV4cfZ09pHFMm5PQQjh7I/67df4c591f88db3ae47f057ad81b5d49/ENgrupo1.PNG)
 3. Click on __Actions__
 4. Select __Product Fields__
-![ENSgrupo2](//images.ctfassets.net/alneenqid6w5/3F6DH1j52N2e1oUBMKoSNf/8d5b1a3644ae4700f1eb99fc065d2464/ENSgrupo2.png)
+![ENSgrupo2](https://images.ctfassets.net/alneenqid6w5/3F6DH1j52N2e1oUBMKoSNf/8d5b1a3644ae4700f1eb99fc065d2464/ENSgrupo2.png)
 5. Find the __group__ you wish to make changes to
 6. Click on __Edit__
-![ENgrupo3](//images.ctfassets.net/alneenqid6w5/4GBCyFv6QYipoaBROwGxbN/0d5050a3e8bd6021e8a6cca3ca8606ad/ENgrupo3.png)
+![ENgrupo3](https://images.ctfassets.net/alneenqid6w5/4GBCyFv6QYipoaBROwGxbN/0d5050a3e8bd6021e8a6cca3ca8606ad/ENgrupo3.png)
 7. After performing the required changes, click on __Save__ 
-![ENgrupo4](//images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
+![ENgrupo4](https://images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
 
 Done, fields have been changed! Don't forget to save the settings for the changes to be displayed on your store's front end.
diff --git a/docs/faq/en/why-does-mercado-livre-return-attribution-errors-after-mapping.md b/docs/faq/en/why-does-mercado-livre-return-attribution-errors-after-mapping.md
index 0742c6241..7810b5b05 100644
--- a/docs/faq/en/why-does-mercado-livre-return-attribution-errors-after-mapping.md
+++ b/docs/faq/en/why-does-mercado-livre-return-attribution-errors-after-mapping.md
@@ -24,13 +24,13 @@ However, these attributes are quite clear (Primary color, Secondary color, Size
 
 If any of these attributes is wrongly entered (for example, if you attribute a code for belt size to a pair of shoes), the Integrations will return an error in the following format:
 
-![Shot1](//images.contentful.com/alneenqid6w5/7A7DwGFr0cw8Q2qek0EqMU/9cad02c847f5dc7be7df68ad14bba39e/Shot1.jpg)
+![Shot1](https://images.contentful.com/alneenqid6w5/7A7DwGFr0cw8Q2qek0EqMU/9cad02c847f5dc7be7df68ad14bba39e/Shot1.jpg)
 
 In this case, we have examples of two errors in the same message.
 
 he first indicates that an attribute whose code begins with the number `113000` is needed for the category selected and was not entered in the mapping worksheet. Look at the following worksheet:
 
-![Shot2](//images.contentful.com/alneenqid6w5/4Nue6IMwP6YEKiweMIe0s4/e835e5ab80f6db2b7a13ee4ed6a4f1e4/Shot2.png)
+![Shot2](https://images.contentful.com/alneenqid6w5/4Nue6IMwP6YEKiweMIe0s4/e835e5ab80f6db2b7a13ee4ed6a4f1e4/Shot2.png)
 
 The second error indicates that the attribute with a code beginning with the number `63000`, entered in the final column of the above worksheet, is not valid for the category selected.
 
@@ -40,7 +40,7 @@ The codes for each variation of an attribute start with the same number. For exa
 
 To identify the attribute indicated in an error message, see the code start number defined by the Mercado Livre. Click on the name of your country to download the reference worksheet:
 
-- [Brazil](//assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
-- [Argentina](//assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
-- [Colombia](//assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
-- [México](//assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+- [Brazil](https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
+- [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
+- [Colombia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
+- [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
diff --git a/docs/faq/en/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md b/docs/faq/en/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
index e1d206056..8315f7625 100644
--- a/docs/faq/en/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
+++ b/docs/faq/en/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
@@ -18,6 +18,6 @@ The JSON used by the Message Center, that is, the source of information to be se
 
 When viewing the `hostName` variable in MessageCenter JSON, doubts may arise as to where this data is loaded from. No matter that the name of the variable is host, it bears the - unchangeable - name of the site created in the Accounts tab of the Account management.
 
-![VTEX - License Manager](//images.contentful.com/alneenqid6w5/5sZb9Mvw4wcK6oM40CKEak/eee7f0e5848c179c678761a418a978b4/2017-03-22-12_33_29-VTEX-License-Manager.png)
+![VTEX - License Manager](https://images.contentful.com/alneenqid6w5/5sZb9Mvw4wcK6oM40CKEak/eee7f0e5848c179c678761a418a978b4/2017-03-22-12_33_29-VTEX-License-Manager.png)
 
 In other words, the value inserted will not be loaded in the Hosts area, rather, as shown in the image above, the value registered under **Nome da Loja** will be loaded to the email template.
diff --git a/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md b/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md
index 4d5a932dd..a88b7fc35 100644
--- a/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md
+++ b/docs/faq/en/why-doesnt-my-benefit-work-for-a-client-cluster.md
@@ -34,7 +34,7 @@ Make sure the value has been entered by following these steps:
 4. Go to the session __"What are the conditions for the benefit to be valid?"__;!
 5. Check which clusters are registered in __"Customers Cluster"__;
 
-![EN - 7GcSb6BuF6JKnmGAggO3uA](//images.ctfassets.net/alneenqid6w5/5dIEGqj1MTmtqOvWdIJFh5/0a0656ee4a3c8f7ac084d438c7cdf82d/Cluster-promo-EN.png)
+![EN - 7GcSb6BuF6JKnmGAggO3uA](https://images.ctfassets.net/alneenqid6w5/5dIEGqj1MTmtqOvWdIJFh5/0a0656ee4a3c8f7ac084d438c7cdf82d/Cluster-promo-EN.png)
 
 6. Enter the "new data";
 7. Click __Save__;
diff --git a/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md b/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
index 966c0fc39..462770d9e 100644
--- a/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
+++ b/docs/faq/en/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
@@ -22,7 +22,7 @@ To specify the type of delivery to which you want to apply the benefit, you must
 2. Click on the card of the benefit to which you want to apply the free shipping.
 3. In item 3, activate the __Shipping Method__ flag and specify which ones should receive the free shipping.
 
-![promoções-campo-tipo-frete en](//images.ctfassets.net/alneenqid6w5/cEe5QqUczQ4MikWAEGkwS/054310fa7cf2bef0d7b02f058f4ddc49/promo____es-campo-tipo-frete_en.png)
+![promoções-campo-tipo-frete en](https://images.ctfassets.net/alneenqid6w5/cEe5QqUczQ4MikWAEGkwS/054310fa7cf2bef0d7b02f058f4ddc49/promo____es-campo-tipo-frete_en.png)
 
 Once this has been done, the specified shipping types will enter the promotion and will appear to the customer with free shipping available.
 
diff --git a/docs/faq/en/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md b/docs/faq/en/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
index db25cb255..ff35742eb 100644
--- a/docs/faq/en/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
+++ b/docs/faq/en/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
@@ -16,6 +16,6 @@ legacySlug: why-doesnt-the-pci-gateway-finalize-the-cancellation-of-a-transactio
 
 This happens when a transaction continues in `Cancelling` status indefinitely, preventing it from being cancelled and, consequently, preventing a request in OMS. This happens when VTEX is awaiting a response from the gateway system, but the correct response is not sent. We can see in the picture below an example of a gateway response preventing VTEX from proceeding with the cancellation process:
 
-![resposta-inadequada-pci-gateway](//images.contentful.com/alneenqid6w5/3P9FblRbzGIEyWo0IW6msa/278ba7912bcbb49a537e94fb7bb4a1b1/resposta-inadequada-pci-gateway.png)
+![resposta-inadequada-pci-gateway](https://images.contentful.com/alneenqid6w5/3P9FblRbzGIEyWo0IW6msa/278ba7912bcbb49a537e94fb7bb4a1b1/resposta-inadequada-pci-gateway.png)
 
 To solve this, you must contact the gateway responsible for payment, give the transaction details and request cancellation.
diff --git a/docs/faq/en/why-dont-my-payment-methods-appear-on-the-marketplace.md b/docs/faq/en/why-dont-my-payment-methods-appear-on-the-marketplace.md
index 219e90cb1..01368607f 100644
--- a/docs/faq/en/why-dont-my-payment-methods-appear-on-the-marketplace.md
+++ b/docs/faq/en/why-dont-my-payment-methods-appear-on-the-marketplace.md
@@ -20,4 +20,4 @@ In other words, payment is made on the marketplace using the marketplace’s pay
 
 For example: A purchase made by the CNova marketplace will be displayed on your OMS, under **Payment**, with the following message: "Assumed value by affiliate CNova (NVP)", as illustrated below.
 
-![exemplopagamento](//images.contentful.com/alneenqid6w5/54QIARxAYUM4igUYQEieSK/d9f8f1e9e95b8028cce7c6b1e7a89503/exemplopagamento.png)
+![exemplopagamento](https://images.contentful.com/alneenqid6w5/54QIARxAYUM4igUYQEieSK/d9f8f1e9e95b8028cce7c6b1e7a89503/exemplopagamento.png)
diff --git a/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md b/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
index 4dc5551f2..71e940a80 100644
--- a/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
+++ b/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
@@ -29,7 +29,7 @@ Mercado Livre has a tool which automatically defines the category of each produc
 
 To fix this, you can [add a product specification](/en/tutorial/creating-a-product-field), **mandatorily** with the `categoria_meli` name. This specification will be able to be given different values, each of them representing a category in Mercado Livre.
 
-The values will be the category IDs. Click [here](//assets.contentful.com/alneenqid6w5/7jBN2dUrjaUOqc4SYCoyaI/54997b8b1df385be79157a5d3c6dd907/MercadoLivre_CategoriasFixas.xlsx) to download a worksheet showing these values.
+The values will be the category IDs. Click [here](https://assets.contentful.com/alneenqid6w5/7jBN2dUrjaUOqc4SYCoyaI/54997b8b1df385be79157a5d3c6dd907/MercadoLivre_CategoriasFixas.xlsx) to download a worksheet showing these values.
 
 After registering the specification, you must access each product register and enter the ID as shown in the worksheet.
 
diff --git a/docs/faq/en/why-is-let-me-know-not-showing.md b/docs/faq/en/why-is-let-me-know-not-showing.md
index b260d08e3..75a10870d 100644
--- a/docs/faq/en/why-is-let-me-know-not-showing.md
+++ b/docs/faq/en/why-is-let-me-know-not-showing.md
@@ -21,7 +21,7 @@ The basic settings for displaying **Let me know** when the product is not availa
 
 However, there is a situation in which despite having set up the items above, “Let me know” does not appear. This happens **when the Category display type is marked as “List of SKUs”.**
 
-![categoria-lista-de-skus EN](//images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
+![categoria-lista-de-skus EN](https://images.ctfassets.net/alneenqid6w5/2C4pwhZgdeQSmmiA4ss8y4/9cfd91a623e3e87734c2b9f417a08be7/lista_de_skus_EN.png)
 
 In this case, in addition to the default settings, the use of the `vtex.cmc:SkuSelection` control is required, even if there is only one SKU per page.
 
diff --git a/docs/faq/en/why-is-my-freight-value-wrong.md b/docs/faq/en/why-is-my-freight-value-wrong.md
index 860ddaaed..d0aff7dd0 100644
--- a/docs/faq/en/why-is-my-freight-value-wrong.md
+++ b/docs/faq/en/why-is-my-freight-value-wrong.md
@@ -23,7 +23,7 @@ Freight calculation is based on several factors: freight table, additional freig
 3. Here, you can see the value registered on the spreadsheet, as well as all [additionals](/en/tutorial/understanding-the-additional-freight) added to this value.
 4. If the value is not consistent with the one displayed at the store, follow the steps below to check if there isn't a sale altering the value of the freight.
 
-![por-que-meu-valor-de-frete-esta-errado en](//images.ctfassets.net/alneenqid6w5/440sXQOHl6ME0SsyuoEaAA/8ea9d8cd9e2c9bb70509664c7f82eb86/por-que-meu-valor-de-frete-esta-errado_en.jpg)
+![por-que-meu-valor-de-frete-esta-errado en](https://images.ctfassets.net/alneenqid6w5/440sXQOHl6ME0SsyuoEaAA/8ea9d8cd9e2c9bb70509664c7f82eb86/por-que-meu-valor-de-frete-esta-errado_en.jpg)
 
 ## Sale
 
@@ -32,4 +32,4 @@ Freight calculation is based on several factors: freight table, additional freig
 3. Observe the box **Total Value** box.
 4. Check if, among sales, there is one offering a freight discount. To check that, simply access the sale and verify the type of discount offered.
 
-![valortotal en](//images.ctfassets.net/alneenqid6w5/5MBxhrcMi4wMgKCIOWckWg/b767465dc888b24295de98b036e2eefe/valortotal_en.jpg)
+![valortotal en](https://images.ctfassets.net/alneenqid6w5/5MBxhrcMi4wMgKCIOWckWg/b767465dc888b24295de98b036e2eefe/valortotal_en.jpg)
diff --git a/docs/faq/en/why-is-my-product-appearing-in-the-wrong-category.md b/docs/faq/en/why-is-my-product-appearing-in-the-wrong-category.md
index fa57b61ec..1a64725d6 100644
--- a/docs/faq/en/why-is-my-product-appearing-in-the-wrong-category.md
+++ b/docs/faq/en/why-is-my-product-appearing-in-the-wrong-category.md
@@ -22,7 +22,7 @@ The first step is to perform a GET request to Catalog API's [Get Product by Id A
 
 The response of this call brings the information of `DepartmentId` and `CategoryId`, as we may see in the image below:
 
-![department-id-category-id](//images.contentful.com/alneenqid6w5/1wJqRKDEcYkGqqsMAGy0aA/bf3521922d99fe678031a1898326b1ea/department-id-category-id.png)
+![department-id-category-id](https://images.contentful.com/alneenqid6w5/1wJqRKDEcYkGqqsMAGy0aA/bf3521922d99fe678031a1898326b1ea/department-id-category-id.png)
 
 Then you should compare this response to the Ids that appear in your category tree. To access your category tree, follow the steps below:
 
diff --git a/docs/faq/en/why-is-my-stores-zoom-not-working.md b/docs/faq/en/why-is-my-stores-zoom-not-working.md
index 34c2a9545..c44f71ded 100644
--- a/docs/faq/en/why-is-my-stores-zoom-not-working.md
+++ b/docs/faq/en/why-is-my-stores-zoom-not-working.md
@@ -25,7 +25,7 @@ This image size can be set up through the following steps:
 2. Enter Settings.
 3. Click __File Types__ tab.
 
-![Tipos de Arquivo EN](//images.ctfassets.net/alneenqid6w5/3vFG4pv5Wgkcu6GaIEgOAa/17ee2d04db1d1dce4237de9bfaf6cc9e/Tipos_de_Arquivo_EN.png)
+![Tipos de Arquivo EN](https://images.ctfassets.net/alneenqid6w5/3vFG4pv5Wgkcu6GaIEgOAa/17ee2d04db1d1dce4237de9bfaf6cc9e/Tipos_de_Arquivo_EN.png)
 
 The 1000x1000 size means that the resulting zoom will display the image in that size. Thus, this is the minimum size for the zoom to work.
 
diff --git a/docs/faq/en/why-is-the-product-not-visible-on-the-website.md b/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
index 67e1e804e..6898a5409 100644
--- a/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
@@ -42,7 +42,7 @@ We recommend beginning the investigation with **Catalog**. To check the **Catalo
 1. Access the VTEX Admin and go to **Products > Catalog > Products and SKUs** to check the products listed in your store.
 2. Find the product you want to display in the list, as illustrated below.
 
-    ![01-produto-en](//images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/8b6bbeb3f736a6e16c77b4b9889c6026/01-produto-en.PNG)
+    ![01-produto-en](https://images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/8b6bbeb3f736a6e16c77b4b9889c6026/01-produto-en.PNG)
 
 3. Follow the instructions described in the next sections to check this information:
     * [Product](#product)
@@ -85,16 +85,16 @@ On the SKUs page, in **Products > Catalog > Products and SKUs**, follow the inst
 
     |Button | Description |
     |-|-|
-    | ![04-botao-precos](//images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Allows you to access the __Price list__ to check if the desired trade policy has a valid price associated with the product SKUs. For more information, check the [Prices](#prices) section. |
-    | ![05-botao-logistica](//images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Allows you to access the __Inventory management__ page to check if the SKU is available in stock.  For more information, check the [Logistics](#logistics) section. |
-    | ![06-botao-indexed-info](//images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Allows you to view each **Seller ** selling the SKU, the trade policy (**Policy**), the price (**Value**) and the SKU quantity in inventory (**Quantity**). |
+    | ![04-botao-precos](https://images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Allows you to access the __Price list__ to check if the desired trade policy has a valid price associated with the product SKUs. For more information, check the [Prices](#prices) section. |
+    | ![05-botao-logistica](https://images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Allows you to access the __Inventory management__ page to check if the SKU is available in stock.  For more information, check the [Logistics](#logistics) section. |
+    | ![06-botao-indexed-info](https://images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Allows you to view each **Seller ** selling the SKU, the trade policy (**Policy**), the price (**Value**) and the SKU quantity in inventory (**Quantity**). |
 
 2. On the row displaying the product with the SKU you want to verify, click the down arrow <i class="fas fa-caret-down"></i>, next to the `Update` button.
 3. Click the **SKU** option to access the SKUs detailed list.
 4. In the **Status** column, check if the indicated situation is `Active`. If the SKUs are active, go to step 7.
 5. If a SKU appears as `Inactive`, click `Update` to view the SKU detailed information.
 
-    ![07-catalogo-skus-en](//images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/038a679284d7261a44ace5814e67ee34/07-catalogo-skus-en.png)
+    ![07-catalogo-skus-en](https://images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/038a679284d7261a44ace5814e67ee34/07-catalogo-skus-en.png)
 
 6. On the SKU information page, continue checking the items listed below.
     * **Activate SKU if possible:** Check if this option is selected. Otherwise, the SKU will not be displayed. When you activate this option, you determine that the SKU will be activated if it meets the necessary requirements:
@@ -109,7 +109,7 @@ On the SKUs page, in **Products > Catalog > Products and SKUs**, follow the inst
 
 <img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/ebc572e69e7dc83a5de491a83c4233ac/08-aba-imagens-en.png" alt="08-aba-imagens-es" style="margin-bottom: 20px;"> <figcaption align = "center"><em><strong>Images</strong> tab</em></figcaption></figure>
 
-![09-sku-imagens-en](//images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/f58814d66052faf18d3bc44e68eb83cc/09-sku-imagens-en.PNG)
+![09-sku-imagens-en](https://images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/f58814d66052faf18d3bc44e68eb83cc/09-sku-imagens-en.PNG)
 
 ### Indexed Info
 
@@ -123,13 +123,13 @@ The indexing list displays each product SKU status. If any issue is detected, th
 
 In the example below, you can conclude that the SKU is unavailable because there are no items in stock:
 
-![10-indexed-info-code](//images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/f1e1650c980fd7042649f6bd8ae3e9a4/Group_1__7_.png)
+![10-indexed-info-code](https://images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/f1e1650c980fd7042649f6bd8ae3e9a4/Group_1__7_.png)
 
 Based on this information, you can take action to correct the issue. In this example, you should adjust the item quantity in stock in the [Logistics](#logistics) system.
 
 An active SKU without errors will appear in the index, similar to the one illustrated below:
 
-![11-indexed-info-code-active](//images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/9e9c99cc4c9408c6dfbaddd4feaaaa84/11-indexed-info-code-active.png)
+![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/9e9c99cc4c9408c6dfbaddd4feaaaa84/11-indexed-info-code-active.png)
 
 <div class="alert alert-info">
 <p>If no reason is given for the product’s unavailability and if you do not find any issues in the product/SKUs, reindexing the product may solve the problem.</p>
@@ -147,7 +147,7 @@ In the **Prices** module, it's important to verify if your product SKU contains
 
 In the example illustrated below, there are two SKUs without a base price. This is why there is no calculated price in the trade policy column — only the information _No price yet_ is displayed.
 
-![12-precos-en](//images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/fe4b6781deb81831cd88cef790af7aee/12-precos-en.PNG)
+![12-precos-en](https://images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/fe4b6781deb81831cd88cef790af7aee/12-precos-en.PNG)
 
 ### Creating a base price
 
@@ -175,7 +175,7 @@ The **Shipping simulator** allows you to check if the item exists in the invento
 2. Fill in the necessary information, as described in [Shipping simulator](https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144).
 3. Click `Shipping simulation`.
 
-![13-simular-frete-pt](//images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/0fbc4b15077d4ea265c82c0a70f5f064/13-simular-frete-en.PNG)
+![13-simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/0fbc4b15077d4ea265c82c0a70f5f064/13-simular-frete-en.PNG)
 
 <div class="alert alert-info">
 <p>To investigate a specific item, you must perform the simulation using a <strong>zip code</strong> included in all the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140">trade policies</a>. If you find out the item is not available for that zip code, it means it will not be available for any other one.</p>
@@ -183,7 +183,7 @@ The **Shipping simulator** allows you to check if the item exists in the invento
 
 The simulation result shows whether the product is available for delivery at the provided address and which are the best shipping options. For example, if there are not enough available items in stock, the simulator will display the following message:
 
-![14-simulador-motivos-en](//images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/68f0e61b7646bb685b5f28278856512b/14-simulador-motivos-en.PNG)
+![14-simulador-motivos-en](https://images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/68f0e61b7646bb685b5f28278856512b/14-simulador-motivos-en.PNG)
 
 For more information on using the simulator, please read the article [Shipping simulator](https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144).
 
@@ -204,7 +204,7 @@ If a product is not available on the website because it is out of stock, you mus
 3. To update the stock count, go to the desired SKU row and write the current quantity in the **Update count** column, as illustrated below.
 4. Click `Save`.
 
-![15-gerenciar-inventario-en](//images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/1ef88e4a10e7cac64efaca80a3fe37fa/15-gerenciar-inventario-en.gif)
+![15-gerenciar-inventario-en](https://images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/1ef88e4a10e7cac64efaca80a3fe37fa/15-gerenciar-inventario-en.gif)
 
 For more information, please read the [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) tutorial.
 
@@ -249,7 +249,7 @@ Follow the steps below to check the template your page is using.
 
     In the example below, the default template is `vtex.curbside-pickup@0.x:store.curbside-pickup` and there is no conditional template.
 
-    ![16-templates-cms-en](//images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/13b66c83e437aa4e2a3bd0d9f722553b/16-templates-cms-en.PNG)
+    ![16-templates-cms-en](https://images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/13b66c83e437aa4e2a3bd0d9f722553b/16-templates-cms-en.PNG)
 
 4. Next, you must check the blocks declared in the used template, as described in [Templates](#templates).
 
diff --git a/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
index d9f568e31..7010bfc30 100644
--- a/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
@@ -24,7 +24,7 @@ To perform this configuration:
 3. Click **Edit** on the `Produto - Thumb` row.
 4. In the display, you can choose the maximum file size  for the thumbnails in the **Maximum size in Kb** field.
 
-![File type settings in CMS](//images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/388b019bc9fa6b0331b56209353f9165/EN.PNG)
+![File type settings in CMS](https://images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/388b019bc9fa6b0331b56209353f9165/EN.PNG)
 
 To learn how to improve the quality of any image from your store without compromising the page load performance, we also recommend reading the article [Improving the performance of product images](https://help.vtex.com/pt/tutorial/improving-the-performance-of-product-images/).
 
diff --git a/docs/faq/en/why-isnt-the-order-invoiced-on-the-marketplace.md b/docs/faq/en/why-isnt-the-order-invoiced-on-the-marketplace.md
index 49b0ccd53..082f5b4dc 100644
--- a/docs/faq/en/why-isnt-the-order-invoiced-on-the-marketplace.md
+++ b/docs/faq/en/why-isnt-the-order-invoiced-on-the-marketplace.md
@@ -30,7 +30,7 @@ As a result, we will be able to reach the “faturado” status only on VTEX, an
 
 The Tax Invoice Access Key is an auxiliary instrument for querying the electronic Tax Invoice (NF-e), enabling the holder of this document to confirm that it actually exists, as well as its field name Invoice Key:
 
-[]![ChaveDeAcesso](//images.contentful.com/alneenqid6w5/447ljGvDxuW0mmQoAumGOg/f1f246378401f4c9a56655974300ab04/ChaveDeAcesso-1.png)
+[]![ChaveDeAcesso](https://images.contentful.com/alneenqid6w5/447ljGvDxuW0mmQoAumGOg/f1f246378401f4c9a56655974300ab04/ChaveDeAcesso-1.png)
 
 __Remember!__ This information item is created when the Tax Invoice is generated and works on ERP. If you have one, request it.
 
diff --git a/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md b/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
index 3c157788e..08e8992a6 100644
--- a/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
+++ b/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
@@ -32,4 +32,4 @@ To access this screen, follow the steps below:
 
 The Filter flag is on the product field configuration screen.
 
-![Filtro Campo de produto](//images.contentful.com/alneenqid6w5/3XSX1nXvjW8kuCi20GaueM/d81f6eea3d6d53c78e00b3e367cbf99b/Filtro_Campo_de_produto.png)
+![Filtro Campo de produto](https://images.contentful.com/alneenqid6w5/3XSX1nXvjW8kuCi20GaueM/d81f6eea3d6d53c78e00b3e367cbf99b/Filtro_Campo_de_produto.png)
diff --git a/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 04cdeea35..477d09975 100644
--- a/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/faq/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -21,7 +21,7 @@ Follow the steps below to validate the information:
 1. Go to your store Admin: `https://{AccountName}.myvtex.com/admin`.
 2. On the side menu, click __Master Data__.
 3. In the __Profile System__ box, click __Customers__.
-4. Select the option __Email__ and search the client's email.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+4. Select the option __Email__ and search the client's email.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 5. Click the customer record to access the profile details.
 
 In the __Contact__ section, you will see that the `Is Company?` option is filled with the value `No`. At the same time, in the section __Company Data__, you will see that the `Document Type` field is filled with the value `cnpj`.
diff --git a/docs/faq/en/why-was-the-item-splitted-in-the-cart.md b/docs/faq/en/why-was-the-item-splitted-in-the-cart.md
index 1a6609223..db3f371e1 100644
--- a/docs/faq/en/why-was-the-item-splitted-in-the-cart.md
+++ b/docs/faq/en/why-was-the-item-splitted-in-the-cart.md
@@ -20,7 +20,7 @@ This scenario is presented when more than one item from the same SKU is splitt
 
 The example below helps to understand this concept :
 
-![Por que o item do carrinho foi separado](//images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/f3753a72da2cdfa13dc4cc797b2d9883/Por_que_o_item_do_carrinho_foi_separado.jpg)
+![Por que o item do carrinho foi separado](https://images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/f3753a72da2cdfa13dc4cc797b2d9883/Por_que_o_item_do_carrinho_foi_separado.jpg)
 
 1. Multiplier unit.
 2. Product price after discount.
diff --git a/docs/faq/en/why-was-the-order-closed-with-the-wrong-price.md b/docs/faq/en/why-was-the-order-closed-with-the-wrong-price.md
index 4307927ab..d9c9f345b 100644
--- a/docs/faq/en/why-was-the-order-closed-with-the-wrong-price.md
+++ b/docs/faq/en/why-was-the-order-closed-with-the-wrong-price.md
@@ -18,7 +18,7 @@ The [Integrations](/en/tutorial/checking-integrations-in-bridge) module informs
 
 `Total do pagamento (311,77) é diferente do pretendido pela loja (313,61)`
 
-[]![DescontoMarketplace](//images.contentful.com/alneenqid6w5/1HmHmw1xTCCe2uc4KWqGio/07fcec1e79b19410f460439419c19178/DescontoMarketplace.png)
+[]![DescontoMarketplace](https://images.contentful.com/alneenqid6w5/1HmHmw1xTCCe2uc4KWqGio/07fcec1e79b19410f460439419c19178/DescontoMarketplace.png)
 
 And when the order has not been integrated due to difference in value, the following message is displayed on Integrations :
 
diff --git a/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 705feaecc..1f5abc26e 100644
--- a/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -18,7 +18,7 @@ A security rule exists at checkout, regarding SmartCheckout purchase facility.
 
 Since with SmartCheckout purchases can be closed just with the email and with the CVV of the card, where the customer has already completed the purchase before, we restrict the number of unsuccessful attempts to conclude the purchase to 3 before asking the customer for their user ID.
 
-![LoginEN](//images.ctfassets.net/alneenqid6w5/FeavXteriS8e4sUYiccgG/fdc93275e4e4145405e95b9e57ab6e4a/LoginEN.png)
+![LoginEN](https://images.ctfassets.net/alneenqid6w5/FeavXteriS8e4sUYiccgG/fdc93275e4e4145405e95b9e57ab6e4a/LoginEN.png)
 
 In other words, if the customer concludes the purchase using only the email and the CVV of the credit card, and if the operator’s approval does not occur after 3 consecutive attempts, a user ID screen is displayed so that the customer can continue trying to purchase. This countdown starts again when the customer logs in and successfully completes their purchase.
 
diff --git a/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md b/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md
index a283b6443..b0cc87599 100644
--- a/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md
+++ b/docs/faq/en/why-wasnt-the-promotion-applied-to-the-marketplace.md
@@ -16,7 +16,7 @@ legacySlug: why-wasnt-the-promotion-applied-to-the-marketplace
 
 To create a promotion for marketplaces, the scenario is almost the same as that for usual promotions. However, you must select, in the **política comercial** field, the value **Loja(s) de terceiro(s)** and select the trade policy applied by the marketplace, or fill out the **afiliado **field with the Id of the marketplace.
 
-![marketplace.es](//images.ctfassets.net/alneenqid6w5/1eBfrn5ZxkarVv9eS793vG/cd52d2a90c555f8bb3829c626afc159a/marketplace.es.png)
+![marketplace.es](https://images.ctfassets.net/alneenqid6w5/1eBfrn5ZxkarVv9eS793vG/cd52d2a90c555f8bb3829c626afc159a/marketplace.es.png)
 
 For more details on how to do so, check [our article on how to create a promotion for the marketplace](https://help.vtex.com/en/tutorial/configurando-promocao-para-marketplace/).
 
diff --git a/docs/faq/es/ab-testing-why-is-it-not-working-google-analytics.md b/docs/faq/es/ab-testing-why-is-it-not-working-google-analytics.md
index 29c193223..6a20d8919 100644
--- a/docs/faq/es/ab-testing-why-is-it-not-working-google-analytics.md
+++ b/docs/faq/es/ab-testing-why-is-it-not-working-google-analytics.md
@@ -26,10 +26,10 @@ Así la Prueba AB funcionará con éxito.
 Siguen las pantallas que ejemplifican el paso a paso:
 
 __Pantalla Control__:
-![](//images.contentful.com/alneenqid6w5/3GIGsJXbo4KAMikCqesM6s/e8231671043f3ce763c8faf87718d6d7/testeAB-controle1-300x138.png)
+![](https://images.contentful.com/alneenqid6w5/3GIGsJXbo4KAMikCqesM6s/e8231671043f3ce763c8faf87718d6d7/testeAB-controle1-300x138.png)
 
 __Pantalla Script__:
-![](//images.contentful.com/alneenqid6w5/7gUgGNnvlmcQyiW4A0A6ao/dac8e58e0931686de3e9e4ae46c66afa/testeAB-script-300x148.png)
+![](https://images.contentful.com/alneenqid6w5/7gUgGNnvlmcQyiW4A0A6ao/dac8e58e0931686de3e9e4ae46c66afa/testeAB-script-300x148.png)
 
 __Pantalla Template__:
-![](//images.contentful.com/alneenqid6w5/4u6uQHYOPuw6Ws8CYKCISo/d04c5fbcc08a5de8a05a242ef76e7ecf/testeAB-template-300x216.png)
+![](https://images.contentful.com/alneenqid6w5/4u6uQHYOPuw6Ws8CYKCISo/d04c5fbcc08a5de8a05a242ef76e7ecf/testeAB-template-300x216.png)
diff --git a/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
index 26a78ebbc..19e4d623f 100644
--- a/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -26,15 +26,15 @@ Hay varias aplicaciones y extensiones de Chrome que retiran las personalizacione
 
 1. Para abrir DevTools, ingrese a Chrome y oprima **F12** o haga clic en el **botón derecho del mouse > Inspeccionar**.
 
-![Customizations1](//images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
+![Customizations1](https://images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/6e445678697a809650b9185adb0df631/Customizations1.png)
 
 2. Vamos a buscar la función **Request Blocking** para bloquear todas las personalizaciones realizadas con CSS, JavaScript y Google Tag Manager. Haga clic en los tres puntos de la derecha, como se indica en la imagen, después en **More Tools** y, por último, en **Request Blocking**.
 
-![Customizations2](//images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
+![Customizations2](https://images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/e04f5f48d28ddfa160f977371972549d/Customizations2.png)
 
 3. Se abrirá un recuadro como se muestra aquí:
 
-![Customizations3](//images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
+![Customizations3](https://images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/973bf322f246e2a24eb89ac9de9e449e/Customizations3.png)
 
 4. Haga clic en la pestaña **Request Blocking**.
 
@@ -50,7 +50,7 @@ Ahora defina los recursos que se deben bloquear. Solo tiene que hacer la configu
 
 El recuadro se verá así:
 
-![Customizations4](//images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
+![Customizations4](https://images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/61f32fd8a4c49715c4c1bc95f0ee1e8d/Customizations4.png)
 
 Recuerde: solo tiene que hacer la configuración __una__ vez.
 
@@ -60,11 +60,11 @@ Recuerde: solo tiene que hacer la configuración __una__ vez.
 
 2. Esta será la configuración que quedará definida como estándar, con las cinco opciones habilitadas para el bloqueo.
 
-![Customizations5](//images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
+![Customizations5](https://images.ctfassets.net/alneenqid6w5/McVb5AEghRIe3tpl1dWGr/5e1881a4a781880dd31eea0938b1ab01/Customizations5.png)
 
 3. Ahora, actualice la página oprimiendo **F5**. La página se mostrará sin los componentes de personalización.
 
-![Customizations6](//images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
+![Customizations6](https://images.ctfassets.net/alneenqid6w5/5MOuqKoGsMU8QpvoR03n9Y/5ca0038583837708383438479a6ead23/Customizations6.png)
 
 4. Para volver a visualizar las personalizaciones, solo tiene que desactivar la casilla **Enable request blocking** y actualizar la página otra vez.
 
diff --git a/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
index 18f62ea88..bec68f16b 100644
--- a/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -31,7 +31,7 @@ Por eso, para tener acceso al cambio de seller, la afiliación con split se debe
 - __Utilizar el comportamiento recomendado del procesador de pagos__.
 - __Desactivado: No se captura automáticamente__.
 
-![Captura de Pago Automática](//images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/0c82ee9775c65757ccfd014d8dd910eb/Captura_De_Pago.png)
+![Captura de Pago Automática](https://images.ctfassets.net/alneenqid6w5/2QsxlUck2BOohNQ8sQUZDL/0c82ee9775c65757ccfd014d8dd910eb/Captura_De_Pago.png)
 
 ### ¿Al seleccionar el comportamiento de liquidación que no es automático, cuándo se liquidará el pago?
 
diff --git a/docs/faq/es/file-upload-button-is-not-displayed-at-cms.md b/docs/faq/es/file-upload-button-is-not-displayed-at-cms.md
index e13464d6c..efccd62ce 100644
--- a/docs/faq/es/file-upload-button-is-not-displayed-at-cms.md
+++ b/docs/faq/es/file-upload-button-is-not-displayed-at-cms.md
@@ -21,7 +21,7 @@ Si tienes este problema en Google Chrome, sólo tienes que activar el plugin Fla
 1. Haga clic en el botón de información o en el candado, que precede a la URL actual;
 2. En la línea correspondiente al Flash, que normalmente está como "Preguntar (estándar)", seleccione **Siempre permitir en este sitio**.
 
-![chrome-flash](//images.contentful.com/alneenqid6w5/URF5k1wvQsaAiSoOeo4WI/5560f944b3b3fabb21bfbf4cebe21037/chrome-flash.jpg)
+![chrome-flash](https://images.contentful.com/alneenqid6w5/URF5k1wvQsaAiSoOeo4WI/5560f944b3b3fabb21bfbf4cebe21037/chrome-flash.jpg)
 
 Normalmente este problema está vinculado a la disponibilidad del Flash Player en el browser, y para el sitio web accesado. 
 
diff --git a/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md b/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md
index b755109c1..5e11232e5 100644
--- a/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md
+++ b/docs/faq/es/how-do-i-find-the-order-nsu-and-tid.md
@@ -23,4 +23,4 @@ NSU y TID son datos de pago que quedan guardados en __Pagos__, en la sección de
 
 Esas informaciones son facilitadas a VTEX durante las transacciones y son organizadas para una simple visualización en **+ Informaciones**, en el [detalle del pedido](/es/tutorial/como-visualizar-detalle-del-pedido), conforme imagen abajo:
 
-![mais-informações-detalhes-pedido es](//images.ctfassets.net/alneenqid6w5/3Ht2Oe6PAYLQCEtwxULNZA/f54b2b67f42713cb300977e387b12a5b/mais-informa____es-detalhes-pedido_es.png)
+![mais-informações-detalhes-pedido es](https://images.ctfassets.net/alneenqid6w5/3Ht2Oe6PAYLQCEtwxULNZA/f54b2b67f42713cb300977e387b12a5b/mais-informa____es-detalhes-pedido_es.png)
diff --git a/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md b/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md
index 756430832..411fe9548 100644
--- a/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md
+++ b/docs/faq/es/how-to-associate-two-promotions-to-the-same-coupon.md
@@ -31,7 +31,7 @@ En este caso,
 4. Acceda a __¿Cuáles son las condiciones para que la promoción sea válida?__.
 5. Introduzca el código del cupón en __utm_source__.
 
-  ![Sincronizar promoções no mesmo cupom - 1 - ES](//images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/c049994bcf92c903a7d4792330ad4306/7yJhwPnclx3tCiJdgpcYyv_-_ES.png)
+  ![Sincronizar promoções no mesmo cupom - 1 - ES](https://images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/c049994bcf92c903a7d4792330ad4306/7yJhwPnclx3tCiJdgpcYyv_-_ES.png)
 
 6. Haga clic en 'Crear cupón a partir de las UTMs arriba'.
 7. Haga clic en 'Guardar'.
@@ -39,6 +39,6 @@ En este caso,
 9. Repita el proceso con la segunda promoción regular.
 10. Al final, ambas promociones deben presentar la misma UTM.
 
-  ![Sincronizar promoções no mesmo cupom - 2 - ES](//images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/b1d28f6435312f320902fb62c12dc6b6/5nhdQy1Y4YWs4pHHokSA44_-_ES.png)
+  ![Sincronizar promoções no mesmo cupom - 2 - ES](https://images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/b1d28f6435312f320902fb62c12dc6b6/5nhdQy1Y4YWs4pHHokSA44_-_ES.png)
 
 De este modo, el cliente puede quitar los dos valores antes de finalizar la compra.
diff --git a/docs/faq/es/how-to-configure-mercadopago-transparente.md b/docs/faq/es/how-to-configure-mercadopago-transparente.md
index 401c60d47..62c114654 100644
--- a/docs/faq/es/how-to-configure-mercadopago-transparente.md
+++ b/docs/faq/es/how-to-configure-mercadopago-transparente.md
@@ -32,7 +32,7 @@ Estas configuraciones deben ser realizadas en su Google TagManager.
 8. Guarde el control;
 9. Haga click en el botón **Crear Tag**, coloque un nombre para esta tag y guarde.
 
-![](//images.contentful.com/alneenqid6w5/YndMcdc0aAw2GKYU0EyU2/c917ac451cfeb262d8354164c6caa285/MercadoPagoTransparente_1_PT.gif)
+![](https://images.contentful.com/alneenqid6w5/YndMcdc0aAw2GKYU0EyU2/c917ac451cfeb262d8354164c6caa285/MercadoPagoTransparente_1_PT.gif)
 
 ## Creando la segunda tag
 
@@ -49,4 +49,4 @@ Estas configuraciones deben ser realizadas en su Google TagManager.
 9. Haga click en el botón **Crear Tag**, inserte un nombre para esta tag y Guarde;
 10. En el margen superior derecho, haga click en **Publicar** y luego también en **Publicar.**
 
-![](//images.contentful.com/alneenqid6w5/32NgyD7KNqicqiASoIUEkK/892ab0a77b4bf2295dcb72d6335de49e/MercadoPagoTransparente_2_PT.gif)
+![](https://images.contentful.com/alneenqid6w5/32NgyD7KNqicqiASoIUEkK/892ab0a77b4bf2295dcb72d6335de49e/MercadoPagoTransparente_2_PT.gif)
diff --git a/docs/faq/es/how-to-disable-the-two-factor-authentication.md b/docs/faq/es/how-to-disable-the-two-factor-authentication.md
index 6796d4c68..8982802e7 100644
--- a/docs/faq/es/how-to-disable-the-two-factor-authentication.md
+++ b/docs/faq/es/how-to-disable-the-two-factor-authentication.md
@@ -16,8 +16,8 @@ legacySlug: como-inhabilitar-la-autenticacion-de-dos-factores
 
 Para inhabilitar el login via autenticacion de dos factores de su cuenta (two factor authentication), siga los siguientes pasos:
 
-1. Haga login con su usuario y contraseña;![2FA 1](//images.contentful.com/alneenqid6w5/4cgNDZ16dGoQGKK6MKeK0m/8afc25a77f0e1554a03a788de5bc19bb/2FA_1.png)
-2. Inserte en el campo que aparece el codigo enviado a su celular y haga clic en el botón **Configure telefone**;![2FA 2](//images.contentful.com/alneenqid6w5/4uMb0UXDNSMa4sMAOSMMaO/2a4eb422eccd35fc4a491018c4cc1517/2FA_2.png)
-3. Haga clic en el botón **Remover telefone**.![2FA 3](//images.contentful.com/alneenqid6w5/1p3qDi9viUgWqWCAyiuom0/456e8eefa5fc1f5dc845f9715e120304/2FA_3.png)
+1. Haga login con su usuario y contraseña;![2FA 1](https://images.contentful.com/alneenqid6w5/4cgNDZ16dGoQGKK6MKeK0m/8afc25a77f0e1554a03a788de5bc19bb/2FA_1.png)
+2. Inserte en el campo que aparece el codigo enviado a su celular y haga clic en el botón **Configure telefone**;![2FA 2](https://images.contentful.com/alneenqid6w5/4uMb0UXDNSMa4sMAOSMMaO/2a4eb422eccd35fc4a491018c4cc1517/2FA_2.png)
+3. Haga clic en el botón **Remover telefone**.![2FA 3](https://images.contentful.com/alneenqid6w5/1p3qDi9viUgWqWCAyiuom0/456e8eefa5fc1f5dc845f9715e120304/2FA_3.png)
 
-Con eso, la autenticación de dos factores será desactivada de su cuenta y usted será redireccionado para el admin VTEX.![2FA 4](//images.contentful.com/alneenqid6w5/5e37R8mEEMuSWwmMAmsGAC/b9caea8225ee2c4421a430553a6f51ad/2FA_4.png)
+Con eso, la autenticación de dos factores será desactivada de su cuenta y usted será redireccionado para el admin VTEX.![2FA 4](https://images.contentful.com/alneenqid6w5/5e37R8mEEMuSWwmMAmsGAC/b9caea8225ee2c4421a430553a6f51ad/2FA_4.png)
diff --git a/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md b/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md
index 5d8424486..ae75a9efd 100644
--- a/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md
+++ b/docs/faq/es/i-cant-edit-a-required-field-on-master-data.md
@@ -18,11 +18,11 @@ Puede editar los campos que aparecen como obligatorios en el __Profile System__
 
 1. En el menú de admin, seleccione el módulo __Master Data__. 
 2. Asegúrese de que se encuentra en la pestaña Aplicaciones, dentro de __ Links Rápidos__.
-3. Haga clic en el __engranaje__ en __Profile System__. ![MasterDataTutorial 1 UM](//images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
-4. Haga clic en el __lápiz__ al lado del ítem que desea configurar. ![MasterDataTutorial2](//images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
+3. Haga clic en el __engranaje__ en __Profile System__. ![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
+4. Haga clic en el __lápiz__ al lado del ítem que desea configurar. ![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
 5. Haga clic en __Schemas de Layout__.
 6. En la __Sección 1__, escoja el ítem del campo que desea configurar.
-7. En __Configuraciones avanzadas del campo__, seleccione __Campo obligatorio__ en el formulario. ![MasterDataTutorial3](//images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
+7. En __Configuraciones avanzadas del campo__, seleccione __Campo obligatorio__ en el formulario. ![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
 
 La opción también puede modificarse siempre que lo desee. 
 
diff --git a/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md b/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
index d45f39364..e2e849f29 100644
--- a/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
+++ b/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
@@ -16,6 +16,6 @@ legacySlug: he-recibido-el-mensaje-erro-the-limit-of-activated-calculators-has-b
 
 Este mensaje indica que se ha alcanzado el número máximo de promociones y que no es posible crear la promoción que se estaba a configurar. Es posible verificar esta información en la pantalla de gestión de promociones (`{AccountName}.vtexcommercestable.com.br/admin/rnb`), como en la imagen de abajo.
 
-![](//images.contentful.com/alneenqid6w5/3MZkA9wEMgYO0mYi2YcQSa/b132514fefacffecfeed56a99307daaf/promo__es.jpg)
+![](https://images.contentful.com/alneenqid6w5/3MZkA9wEMgYO0mYi2YcQSa/b132514fefacffecfeed56a99307daaf/promo__es.jpg)
 
 Debes revisar sus promociones activas para ajustarlas y reorganizarlas, para que tantas unidades no sean necesarias. En general, la unión de varias reglas en sólo una promoción es posible, ayudando a mejorar la performance del carrito y la organización de las promociones.
diff --git a/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 4925902a9..4d0cdf6f2 100644
--- a/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -31,6 +31,6 @@ __Para hacer la inclusión manual de SKUs específicos, siga el paso a paso abaj
 5. Dé un nombre a su colección (los demás campos no se deben llenar).
 6. Introduzca los SKUs en el campo informado y __los separe con comas__.
 
-![recurrence-specific-skus](//images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
+![recurrence-specific-skus](https://images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
 
 Por fin, dé un nombre al __Grupo__ de su Colección y haga clic en __Save Group__.
diff --git a/docs/faq/es/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md b/docs/faq/es/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
index a6c7e08e0..2f75470d0 100644
--- a/docs/faq/es/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
+++ b/docs/faq/es/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
@@ -19,5 +19,5 @@ Es común que la tienda haga cambios en los placeholders de un layout, en el mó
 Normalmente, esto sucede porque la tienda guarda el placeholder después de los cambios pero no guarda el layout.
 
 Siempre que cambie un placeholder, recuerde que es necesario:
-1. Guardar el placeholder.![savePlaceholder](//images.contentful.com/alneenqid6w5/3CefNlrWxWOO8kgyKEkMMk/3deea3f44d5f21e037e799a07500f147/savePlaceholder.png)
-2. Guardar el layout.![saveLayout](//images.contentful.com/alneenqid6w5/1WUC8Yy2Vq2qEOAuQMG0km/83bce62e6f8145112655dae251474bf5/saveLayout.png)
+1. Guardar el placeholder.![savePlaceholder](https://images.contentful.com/alneenqid6w5/3CefNlrWxWOO8kgyKEkMMk/3deea3f44d5f21e037e799a07500f147/savePlaceholder.png)
+2. Guardar el layout.![saveLayout](https://images.contentful.com/alneenqid6w5/1WUC8Yy2Vq2qEOAuQMG0km/83bce62e6f8145112655dae251474bf5/saveLayout.png)
diff --git a/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md b/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md
index 61445833c..bae23d77e 100644
--- a/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md
+++ b/docs/faq/es/kitlook-is-not-displayed-in-the-shop-window.md
@@ -32,7 +32,7 @@ __Llene el campo Label__
 4. Vaya a la pestaña __Imágenes__;
 5. Introduzca un término para llenar la __Label__;
 
-  ![Kit Look - Label - ES](//images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/63dcfae1b88d48e1a8582c43cfa9af81/7FR879Lzl3eEDmAHiBV0TV_es.jpg)
+  ![Kit Look - Label - ES](https://images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/63dcfae1b88d48e1a8582c43cfa9af81/7FR879Lzl3eEDmAHiBV0TV_es.jpg)
 
 6. Haga clic en __Guardar__.
 
diff --git a/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md b/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md
index 9e7a34022..c403f8822 100644
--- a/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md
+++ b/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md
@@ -22,8 +22,8 @@ De forma predeterminada, el CMS sólo muestra las __últimas 20 colecciones__ ac
 
 Por lo tanto, si su tienda tiene más de 20 colecciones, es normal que algunas de ellas no aparezcan en la lista mostrada en el CMS.
 
-![findCollection1](//images.contentful.com/alneenqid6w5/1DM1TNjCKYsY0KQkMgycGm/c49a70d5570d62c993539114d8596549/findCollection1.png)
+![findCollection1](https://images.contentful.com/alneenqid6w5/1DM1TNjCKYsY0KQkMgycGm/c49a70d5570d62c993539114d8596549/findCollection1.png)
 
 Pero usted puede buscar cualquier colección utilizando el campo de búsqueda (Find), incluyendo aquellos que no se muestran por defecto.
 
-![findCollection2](//images.contentful.com/alneenqid6w5/6LBUTpvCH64Uc2CQEwiigk/5739b97f92b27ec9fc40fb4e93ffb2af/findCollection2.png)
+![findCollection2](https://images.contentful.com/alneenqid6w5/6LBUTpvCH64Uc2CQEwiigk/5739b97f92b27ec9fc40fb4e93ffb2af/findCollection2.png)
diff --git a/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
index aaddad8e5..d0126a99e 100644
--- a/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -25,7 +25,7 @@ Cuando el ERP consulta e inserta este pedido en su base, es necesario que él le
 
 > Para ello, haga clic en el símbolo de flecha encima del box **Iniciar manoseo**, en el diagrama de flujo de pedidos.
 
-![ Listo para manoseo](//images.contentful.com/alneenqid6w5/5VSeCrxvSogcI46mgkYkm8/84ea107934684ada917d6a8163aeae34/ProntoParaManuseio.png)
+![ Listo para manoseo](https://images.contentful.com/alneenqid6w5/5VSeCrxvSogcI46mgkYkm8/84ea107934684ada917d6a8163aeae34/ProntoParaManuseio.png)
 
 > Es necesario tener un [perfil de acceso con permiso OMS - Full access](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para llevar a cabo esta acción.
 
diff --git a/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md b/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md
index 76ec2d0df..41de5cee5 100644
--- a/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md
+++ b/docs/faq/es/some-gateway-affiliations-are-highlighted-in-yellow-why.md
@@ -18,6 +18,6 @@ Cuando entre en __Afiliaciones__, es posible ver la lista de todas las configura
 
 Eso significa que esta afiliación no está activa, y sí que está en teste. Es posible confirmar esa información haciendo clic en la Afiliación.
 
-![afiliação-gateway-teste es](//images.ctfassets.net/alneenqid6w5/6CYa8SyybuMGwYqOqkoa8U/b1b1d471edd3d98336719c8e07f22605/gateway_teste_es.png)
+![afiliação-gateway-teste es](https://images.ctfassets.net/alneenqid6w5/6CYa8SyybuMGwYqOqkoa8U/b1b1d471edd3d98336719c8e07f22605/gateway_teste_es.png)
 
 O sea, el color destaca aquellas configuraciones que todavía no están activas.
diff --git a/docs/faq/es/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md b/docs/faq/es/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
index 8b6351da9..03de80da4 100644
--- a/docs/faq/es/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
+++ b/docs/faq/es/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
@@ -22,14 +22,14 @@ Esto sucede cuando hay algún error en el registro del SKU en el seller.
 
 Para identificar cuál es el error, siga los pasos abajo:
 1. Entre en el módulo __Sugerencias__.
-2. Haga clic en el SKU que el marketplace no aceptó.![erroSuggestion1](//images.contentful.com/alneenqid6w5/2T4ywpCeacosAGoQCS0k4M/f27f1729b879a02cd11f5bc916c8f8a6/erroSuggestion1.png)
+2. Haga clic en el SKU que el marketplace no aceptó.![erroSuggestion1](https://images.contentful.com/alneenqid6w5/2T4ywpCeacosAGoQCS0k4M/f27f1729b879a02cd11f5bc916c8f8a6/erroSuggestion1.png)
 3. Entre en el __developer tools__ del navegador (para eso, si está usando Google Chrome, presione `F12` en Windows o `Command + Option + I` en Mac).
 4. En developer tools, haga clic en la pestaña __Network__.
-5. Todavía en developer tools, haga clic en la opción __All__.![erroSuggestion2](//images.contentful.com/alneenqid6w5/tXLZF0IEO4KKa6O4WuQg6/58adc90c3afa5ce2d02238079cabd958/erroSuggestion2.png)
+5. Todavía en developer tools, haga clic en la opción __All__.![erroSuggestion2](https://images.contentful.com/alneenqid6w5/tXLZF0IEO4KKa6O4WuQg6/58adc90c3afa5ce2d02238079cabd958/erroSuggestion2.png)
 6. Haga clic en el botón __Aceptar__ del módulo Sugerencias.
 7. Usted verá una lista de las llamadas activadas por el botón Aceptar.
-8. Si una de ellas está en rojo y con status `400`, como en la siguiente imagen, haga clic en esa llamada.![erroSuggestion3](//images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)
-9. Usted verá a continuación la descripción del error que ocasionó el problema en el procesamiento de la sugerencia de SKU.![erroSuggestion4](//images.contentful.com/alneenqid6w5/4yN8mswXdYoKO6wcsyO0eW/2de11f133c3ee911c1e712d7b1188711/erroSuggestion4.png)
+8. Si una de ellas está en rojo y con status `400`, como en la siguiente imagen, haga clic en esa llamada.![erroSuggestion3](https://images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)
+9. Usted verá a continuación la descripción del error que ocasionó el problema en el procesamiento de la sugerencia de SKU.![erroSuggestion4](https://images.contentful.com/alneenqid6w5/4yN8mswXdYoKO6wcsyO0eW/2de11f133c3ee911c1e712d7b1188711/erroSuggestion4.png)
 
 Para resolverlo, el seller debe resolver el error señalado en esta descripción.
 
diff --git a/docs/faq/es/understanding-the-dashboard.md b/docs/faq/es/understanding-the-dashboard.md
index 6973fd05d..e4633d1a3 100644
--- a/docs/faq/es/understanding-the-dashboard.md
+++ b/docs/faq/es/understanding-the-dashboard.md
@@ -22,7 +22,7 @@ Para acceder al Dashboard, haga clic en el módulo **License Manager** en el men
 
 Son 3 gráficos en total. En el primero de ellos es posible comparar el promedio del tiempo de carga total de su tienda (en rojo) con el promedio del tiempo de carga total de todas las demás tiendas de VTEX (en azul). A continuación usted puede ver un ejemplo de ese gráfio.
 
-![](//images.contentful.com/alneenqid6w5/2z4iBEY5UEkqcmsa0KEgoi/3d661f25118a2e876d20a565ebfc88f9/dashboard-chart1-560x320.png)
+![](https://images.contentful.com/alneenqid6w5/2z4iBEY5UEkqcmsa0KEgoi/3d661f25118a2e876d20a565ebfc88f9/dashboard-chart1-560x320.png)
 
 A partir de este gráfico es posible percibir si una eventual lentitud en el sistema está impactando solamente su tienda o todas las tiendas de VTEX. También es posible visualizar si un eventual pico en el tiempo de carga todavía persiste o si ha sido momentáneo. _Es importante destacar_también que _no todo pico significa necesariamente un problema_, pues es natural que el gráfico refleje el comportamiento de los clientes de su tienda, con un mayor número de acceso en determinados horarios. Con el tiempo, usted se acostumbrará al comportamiento de su tienda y estará más apto a discernir lo que se escapa a lo común.
 
@@ -30,7 +30,7 @@ A partir de este gráfico es posible percibir si una eventual lentitud en el sis
 
 En el segundo gráfico usted también podrá visualizar el tiempo medio de carga de su tienda, pero de esta vez dividido entre los diferentes factores que componen el tiempo de carga de una página web: el tiempo de red (en azul), el procesamiento del árbol DOM (en rojo) y la renderización de la página en el navegador (amarillo).
 
-![](//images.contentful.com/alneenqid6w5/2DMi5uS3awigGGIAEKCqea/b95fc4689141764c25b5fd506eeaac33/2.jpg)
+![](https://images.contentful.com/alneenqid6w5/2DMi5uS3awigGGIAEKCqea/b95fc4689141764c25b5fd506eeaac33/2.jpg)
 
 Esto permite discernir si un eventual problema de demora en la carga en la página está siendo causado por una demora en la respuesta del servidor (NetworkTime), por un script JavaScript (DomProcessing) con error o por una imagen muy pesada (PageRendering), por ejemplo.
 
diff --git a/docs/faq/es/understanding-vtex-email-capture-system.md b/docs/faq/es/understanding-vtex-email-capture-system.md
index ec18282e3..c365d2000 100644
--- a/docs/faq/es/understanding-vtex-email-capture-system.md
+++ b/docs/faq/es/understanding-vtex-email-capture-system.md
@@ -50,5 +50,5 @@ Para que se pueda utilizar la función <a href="https://help.vtex.com/es/tutoria
 Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
 </div>
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md b/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md
index a0d274577..d0be6edc6 100644
--- a/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md
+++ b/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md
@@ -24,7 +24,7 @@ El ID de la forma de pago que se configurará a Interés Simple se obtiene del s
 - Ingresar a la Forma de Pago que se desea configurar para que utilice Interés Simple
 - Copiar el último parámetro de la URL, que indica el ID de esa Forma de Pago (ver imagen)
 
-![Interes Simple - Obtener ID Transaccion](//images.contentful.com/alneenqid6w5/19PugiXjNssA6c48WoqoSC/808db9360d3dbb5dd12466882ce3e852/interes-simple-id-transaccion.png)
+![Interes Simple - Obtener ID Transaccion](https://images.contentful.com/alneenqid6w5/19PugiXjNssA6c48WoqoSC/808db9360d3dbb5dd12466882ce3e852/interes-simple-id-transaccion.png)
 
 ## Configurar el tipo de interés mediante la API
 
diff --git a/docs/faq/es/website-with-error-how-to-fix-it.md b/docs/faq/es/website-with-error-how-to-fix-it.md
index df9aafcd8..bc52a56d8 100644
--- a/docs/faq/es/website-with-error-how-to-fix-it.md
+++ b/docs/faq/es/website-with-error-how-to-fix-it.md
@@ -22,7 +22,7 @@ Pero, si está Amarillo, está con error.
 Sigue el paso a paso de cómo ajustarlo:
 
 1. Haga clic en el website.
-2. Seleccione el Binding (línea seleccionada en la imagen abajo) y haga clic en __Update__:![Binding 1](//images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
+2. Seleccione el Binding (línea seleccionada en la imagen abajo) y haga clic en __Update__:![Binding 1](https://images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
 3. En la pantalla que será mostrada, el campo __Store name from License Manager__ estará en blanco. Con eso, haga clic en la flecha que aparece en ese campo y seleccione el nombre de su tienda.
-4. Haga clic en __Save Binding__.![Binding 2](//images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
+4. Haga clic en __Save Binding__.![Binding 2](https://images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
 5. Haga clic en __Websites__ de nuevo para actualizar la página y listo. El globito estará azul. ¡Lo que es una indicación de que ahora esta correcto!
diff --git a/docs/faq/es/what-deleting-a-sku-seller-means.md b/docs/faq/es/what-deleting-a-sku-seller-means.md
index 0554ff3f2..e6ed1651a 100644
--- a/docs/faq/es/what-deleting-a-sku-seller-means.md
+++ b/docs/faq/es/what-deleting-a-sku-seller-means.md
@@ -14,7 +14,7 @@ locale: es
 legacySlug: que-significa-excluir-un-sku-seller
 ---
 
-![excluir](//images.contentful.com/alneenqid6w5/3H8ijBZBEseoomo0wyMKoi/fea00e532fc957357b8794a1afc278ba/excluir.png)
+![excluir](https://images.contentful.com/alneenqid6w5/3H8ijBZBEseoomo0wyMKoi/fea00e532fc957357b8794a1afc278ba/excluir.png)
 
 Al excluir el SKU Seller, él deja de formar parte del catálogo del Marketplace. Esto significa que ** él no existirá más en la lista de SKUs **.
 
diff --git a/docs/faq/es/what-delinking-a-sku-seller-means.md b/docs/faq/es/what-delinking-a-sku-seller-means.md
index 5bc16d147..101a8279a 100644
--- a/docs/faq/es/what-delinking-a-sku-seller-means.md
+++ b/docs/faq/es/what-delinking-a-sku-seller-means.md
@@ -14,7 +14,7 @@ locale: es
 legacySlug: que-significa-desvincular-un-sku-seller
 ---
 
-![desvincular](//images.contentful.com/alneenqid6w5/2fJNaa6xkEC0CwguKWK4o0/f6f8625d2409ff921826ffb913598eaf/desvincular.png)
+![desvincular](https://images.contentful.com/alneenqid6w5/2fJNaa6xkEC0CwguKWK4o0/f6f8625d2409ff921826ffb913598eaf/desvincular.png)
 
 Al desvincular un SKU Seller, éste __dejará de exhibirse como disponible__ en el Marketplace.
 
diff --git a/docs/faq/es/what-should-i-do-when-there-are-problems-with-a-transaction.md b/docs/faq/es/what-should-i-do-when-there-are-problems-with-a-transaction.md
index c060d6948..a15eaa2c5 100644
--- a/docs/faq/es/what-should-i-do-when-there-are-problems-with-a-transaction.md
+++ b/docs/faq/es/what-should-i-do-when-there-are-problems-with-a-transaction.md
@@ -25,10 +25,10 @@ En ocasiones puede ocurrir una falla de comunicación entre VTEX y el aliado. Ha
 Casos como ése generan logs o mantienen el pedido en un looping. Una vez que se identifique un comportamiento errático, el camino más rápido es verificar si el status del pedido está igual en ambas plataformas. Como, por ejemplo, el Gateway haber atualizado el Status como "Settling", pero posteriormente contestar que el Status no está correcto para captura, sin embargo el Status estaría correcto. Vea el ejemplo:
 
 El día 08 de febrero, VTEX recibió una notificación del Gateway en la que hay un cambio de Status.
-![2017-04-11-17 28 32-4820587- -VTEX-PCI-Gateway-300x65](//images.contentful.com/alneenqid6w5/7us92BzXFYwyQsUqWQa0sM/9c8e7dc490e5497bf8cfa16e0f7874ce/2017-04-11-17_28_32-4820587-_-VTEX-PCI-Gateway-300x65.png) 
+![2017-04-11-17 28 32-4820587- -VTEX-PCI-Gateway-300x65](https://images.contentful.com/alneenqid6w5/7us92BzXFYwyQsUqWQa0sM/9c8e7dc490e5497bf8cfa16e0f7874ce/2017-04-11-17_28_32-4820587-_-VTEX-PCI-Gateway-300x65.png) 
 
 El día 03 de abril el gateway retorna error en el Status
-![2017-04-11-17 26 40-4820587- -VTEX-PCI-Gateway-300x87](//images.contentful.com/alneenqid6w5/35WTOXDAC4WgS0Ki866SSS/6d7f6ed699ef653d79d709c97320d10c/2017-04-11-17_26_40-4820587-_-VTEX-PCI-Gateway-300x87.png)
+![2017-04-11-17 26 40-4820587- -VTEX-PCI-Gateway-300x87](https://images.contentful.com/alneenqid6w5/35WTOXDAC4WgS0Ki866SSS/6d7f6ed699ef653d79d709c97320d10c/2017-04-11-17_26_40-4820587-_-VTEX-PCI-Gateway-300x87.png)
 
 Otro ejemplo sería el Gateway (aliado) retornar que no posee los datos completos de la tarjeta de crédito para proseguir con la compra. Sin embargo, en los detalles de la transacción en la parte superior de la página, es posible confirmar que la información existe – incluso porque el pedido no se habría creado sin esa información. El camino aquí sería el mismo, ponerse en contacto con su Gateway.
 
diff --git a/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md b/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md
index 7dd4376a5..91411e478 100644
--- a/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md
+++ b/docs/faq/es/what-to-do-when-my-exported-report-does-not-reach-my-email.md
@@ -24,9 +24,9 @@ A continuación, entienda el paso a paso para hacerlo:
 
 1. Acceda al __Master Data__;
 2. Haga clic en __Exportations__;
-![3WNNUZ8EgDZ4iYv8e0OyQG](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
+![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
 3. Asegúrese de que la pestaña abierta es la de __"Applications"__;
-![7ecXBGaCeC3hTaO0lODPq1](//images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
+![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
 4. En __"Status de exportaciones"__, haga clic en el informe que desea descargar.
 
 De esta forma, es posible acceder a este material aunque el email original no haya llegado al solicitante.
diff --git a/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md
index 5d152b705..a6727de1f 100644
--- a/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/es/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -16,7 +16,7 @@ legacySlug: que-hacer-cuando-el-aviseme-no-es-exhibido
 
 Existe un caso en que, aun con la [configuración del Avíseme](/es/tutorial/configurar-el-aviseme) hecha, el Avíseme no aparece. Es **cuando el tipo de exhibición de la categoría está seleccionado como Lista de SKUs**.
 
-![categoria-lista-de-skus ES](//images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
+![categoria-lista-de-skus ES](https://images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
 
 En este caso, además de las configuraciones estándar, es necesario usar el control `vtex.cmc:SkuSelection`, aunque no exista más de un SKU por página.
 
diff --git a/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md b/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
index 5f8b0e50c..d5754b2af 100644
--- a/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
+++ b/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
@@ -18,7 +18,7 @@ Un error común en la aprobación de pago, en el módulo **Pedidos**, es el de f
 
 En este caso, al intentar aprobar el pago en **Pedidos**, usted verá el siguiente error:
 
-![error authorize fulfillment](//images.contentful.com/alneenqid6w5/5Wvwem2kucqsOIYKq4WW00/23b0ffb4209565da148382c3299e2bac/error_authorize_fulfillment.png)
+![error authorize fulfillment](https://images.contentful.com/alneenqid6w5/5Wvwem2kucqsOIYKq4WW00/23b0ffb4209565da148382c3299e2bac/error_authorize_fulfillment.png)
 
 Para confirmar que el problema es este, en la [página de detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), haga clic en `Ver interacciones` para ver los detalles del pedido.
 
diff --git a/docs/faq/es/where-can-i-see-my-mercado-pago-transparente-credentials.md b/docs/faq/es/where-can-i-see-my-mercado-pago-transparente-credentials.md
index 54520e7c1..25926abea 100644
--- a/docs/faq/es/where-can-i-see-my-mercado-pago-transparente-credentials.md
+++ b/docs/faq/es/where-can-i-see-my-mercado-pago-transparente-credentials.md
@@ -18,9 +18,9 @@ _Parte de las configuraciones documentadas en este artículo deben ser realizad
 
 Para tener acceso a sus credenciales de Mercado Pago Transparente, acceda a las configuraciones de esta afiliación, en el módulo PCI Gateway, y siga los pasos explicado aquí:
 
-1. En los datos a la derecha, debajo de "Get Credentials", haga click en **Consultar**. Este link lo conducirá para la página de autenticación de Mercado Pago![2017-01-26 19_37_19-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/4hKomsptCEgGWUsyw4e4GM/09fba68bccee98e6c7d13f6ba4112d6a/2017-01-26-19_37_19-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x140.png)
-2. Debajo de "How to obtain my access\_token", haga click en **Credentials**;![2017-01-26 19_43_49-Authentication - MercadoPago Developers](//images.contentful.com/alneenqid6w5/1ZM0tXM4DWk6SEE68ecU4m/0f5802acc942e3ca7ac7d1760754cd43/2017-01-26-19_43_49-Authentication-MercadoPago-Developers-279x300.png)
-3. En la solapa **Checkout básico**, encontrará sus credenciales.![2017-01-26 19_48_02-MercadoPago - Credenciais](//images.contentful.com/alneenqid6w5/6hgEPEEkWkAqY2u80cqeGI/8152d6e0a24defb9986335be54a0e169/2017-01-26-19_48_02-MercadoPago-Credenciais-300x88.png)
+1. En los datos a la derecha, debajo de "Get Credentials", haga click en **Consultar**. Este link lo conducirá para la página de autenticación de Mercado Pago![2017-01-26 19_37_19-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/4hKomsptCEgGWUsyw4e4GM/09fba68bccee98e6c7d13f6ba4112d6a/2017-01-26-19_37_19-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x140.png)
+2. Debajo de "How to obtain my access\_token", haga click en **Credentials**;![2017-01-26 19_43_49-Authentication - MercadoPago Developers](https://images.contentful.com/alneenqid6w5/1ZM0tXM4DWk6SEE68ecU4m/0f5802acc942e3ca7ac7d1760754cd43/2017-01-26-19_43_49-Authentication-MercadoPago-Developers-279x300.png)
+3. En la solapa **Checkout básico**, encontrará sus credenciales.![2017-01-26 19_48_02-MercadoPago - Credenciais](https://images.contentful.com/alneenqid6w5/6hgEPEEkWkAqY2u80cqeGI/8152d6e0a24defb9986335be54a0e169/2017-01-26-19_48_02-MercadoPago-Credenciais-300x88.png)
 
 Las credenciales correctas son `CLIENT\_ID` y `CLIENT\_SECRET`. Se encuentran en la solapa **Checkout básico**, y no en Checkout transparente.
 
diff --git a/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md b/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md
index 178657379..fc974c119 100644
--- a/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md
+++ b/docs/faq/es/why-can-t-i-change-the-fields-in-a-group.md
@@ -26,13 +26,13 @@ Una vez localizado el campo, continúe con las instrucciones:
 
 1. Acceda al módulo __Catálogo__
 2. Haga clic en __Categorías__
-![campos1](//images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
+![campos1](https://images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
 3. Haga clic en __Acciones__
 4. Seleccione __Campos (Producto)__
-![campos2](//images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
+![campos2](https://images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
 5. Encuentre el __grupo__ al que desea hacerle modificaciones. 
 6. Haga clic en __Alterar__
-![campos3](//images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
+![campos3](https://images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
 7. Después de realizar los cambios requeridos, haga clic en __Guardar__
 
 ¡Listo, campos alterados! No se olvide de guardar las configuraciones para que las alteraciones sean exhibidas en el front de la tienda.
diff --git a/docs/faq/es/why-does-mercado-livre-return-attribution-errors-after-mapping.md b/docs/faq/es/why-does-mercado-livre-return-attribution-errors-after-mapping.md
index 95700d046..ebd42b6e5 100644
--- a/docs/faq/es/why-does-mercado-livre-return-attribution-errors-after-mapping.md
+++ b/docs/faq/es/why-does-mercado-livre-return-attribution-errors-after-mapping.md
@@ -24,13 +24,13 @@ Sin embargo, esos atributos son muy claros (Color principal, Color secundario, T
 
 Si alguno de esos atributos es rellenado incorrectamente (por ejemplo, si usted ha atribuido un código relativo a Tamaño de cinturón para un calzado), el Integraciones va a retornar un error con el siguiente formato:
 
-![Shot1](//images.contentful.com/alneenqid6w5/7A7DwGFr0cw8Q2qek0EqMU/9cad02c847f5dc7be7df68ad14bba39e/Shot1.jpg)
+![Shot1](https://images.contentful.com/alneenqid6w5/7A7DwGFr0cw8Q2qek0EqMU/9cad02c847f5dc7be7df68ad14bba39e/Shot1.jpg)
 
 En este caso, tenemos dos ejemplos de errores en el mismo mensaje.
 
 El primero de ellos indica que el atributo cuyo código empieza con el número `113000` es necesario para la categoría elegida y no fue insertado en la planilla de mapeo. Vea la planilla a continuación:
 
-![Shot2](//images.contentful.com/alneenqid6w5/4Nue6IMwP6YEKiweMIe0s4/e835e5ab80f6db2b7a13ee4ed6a4f1e4/Shot2.png)
+![Shot2](https://images.contentful.com/alneenqid6w5/4Nue6IMwP6YEKiweMIe0s4/e835e5ab80f6db2b7a13ee4ed6a4f1e4/Shot2.png)
 
 El segundo error indica que el atributo cuyo código empieza con el número `63000`, insertado en la última columna de la planilla arriba es inválido para la categoría elegida.
 
@@ -40,7 +40,7 @@ Los códigos de cada variación de atributo empiezan con el mismo número. Por e
 
 Para identificar el atributo indicado en el mensaje de error, consulte el número inicial de los códigos determinados por Mercado Livre. Haga clic en el nombre de su país para descargar la planilla de referencia:
 
-- [Brasil](//assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
-- [Argentina](//assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
-- [Colombia](//assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
-- [México](//assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+- [Brasil](https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
+- [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
+- [Colombia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
+- [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
diff --git a/docs/faq/es/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md b/docs/faq/es/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
index acd6a8644..db1c2894b 100644
--- a/docs/faq/es/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
+++ b/docs/faq/es/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
@@ -18,6 +18,6 @@ El JSON utilizado por el Centro de mensajes, o sea, la fuente de las informacion
 
 Al visualizar la variable `hostName` en el JSON del Centro de mensajes, puede aparecer la duda sobre dónde es cargado ese dato. Por más que el nombre de la variable sea host, ella lleva el nombre - no modificable - del site creado en la pestaña Cuentas de la sección Gestión de la cuenta.
 
-![VTEX - License Manager](//images.contentful.com/alneenqid6w5/5sZb9Mvw4wcK6oM40CKEak/eee7f0e5848c179c678761a418a978b4/2017-03-22-12_33_29-VTEX-License-Manager.png)
+![VTEX - License Manager](https://images.contentful.com/alneenqid6w5/5sZb9Mvw4wcK6oM40CKEak/eee7f0e5848c179c678761a418a978b4/2017-03-22-12_33_29-VTEX-License-Manager.png)
 
 O sea, o será cargado el valor insertado en el área de Hosts, sino que, conforme a la imagen arriba, será cargado para el template de email el valor registrado en **Nombre de la Tienda**.
diff --git a/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md b/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md
index c3feea836..0851e92d4 100644
--- a/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md
+++ b/docs/faq/es/why-doesnt-my-benefit-work-for-a-client-cluster.md
@@ -34,7 +34,7 @@ Asegúrese de que el valor se ha insertado siguiendo los pasos abajo:
 4. Acceda a la sesión __"¿Cuáles son las condiciones para la promoción sea válida?"__;
 5. Compruebe qué clústeres están registrados en __"Clúster de clientes"__;
 
-![ES - 7GcSb6BuF6JKnmGAggO3uA](//images.ctfassets.net/alneenqid6w5/5mX30OM2efHdMldl5xHS6A/9a8352287ca7193f213098189a182abe/Cluster-promo-ES.png)
+![ES - 7GcSb6BuF6JKnmGAggO3uA](https://images.ctfassets.net/alneenqid6w5/5mX30OM2efHdMldl5xHS6A/9a8352287ca7193f213098189a182abe/Cluster-promo-ES.png)
 
 6. Introduzca los __nuevos datos__;
 7. Haga clic en __Guardar__.!
diff --git a/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md b/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
index 7ad4b8c6f..4d29db0d3 100644
--- a/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
+++ b/docs/faq/es/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
@@ -22,7 +22,7 @@ Para especificar en qué tipo de entrega desea aplicar la promoción, es necesar
 2. Haga clic en el card de la promoción a que desea aplicar el envío gratis.
 3. En el ítem 3, active la flag __Tipo de carga__ y especifique cuales deben recibir el flete gratis.
 
-![promoções-campo-tipo-frete es](//images.ctfassets.net/alneenqid6w5/4wTOYyINOgy4oGceMGmQKM/46c06b029b0e1a8fcf3f3ab48eaddf3a/promo____es-campo-tipo-frete_es.png)
+![promoções-campo-tipo-frete es](https://images.ctfassets.net/alneenqid6w5/4wTOYyINOgy4oGceMGmQKM/46c06b029b0e1a8fcf3f3ab48eaddf3a/promo____es-campo-tipo-frete_es.png)
 
 Hecho esto, los tipos de flete especificados entrarán en la promoción y aparecerán para el cliente con el flete gratis disponible.
 
diff --git a/docs/faq/es/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md b/docs/faq/es/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
index 438904b11..a1d2414a8 100644
--- a/docs/faq/es/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
+++ b/docs/faq/es/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
@@ -16,6 +16,6 @@ legacySlug: por-que-el-pci-gateway-no-finaliza-la-cancelacion-de-la-transaccion
 
 Este escenario ocurre cuando una transacción permanece indefinidamente en el status `Cancelling`, impidiendo la cancelación de la transacción, y por consiguiente, del pedido en el OMS. Esta situación ocurre cuando VTEX está esperando un retorno del sistema del gateway, pero la respuesta correcta no llega hasta VTEX. Podemos ver en la imagen a continuación un ejemplo de respuesta del gateway que no permite la continuidad del proceso de cancelación por parte de VTEX:
 
-![resposta-inadequada-pci-gateway](//images.contentful.com/alneenqid6w5/3P9FblRbzGIEyWo0IW6msa/278ba7912bcbb49a537e94fb7bb4a1b1/resposta-inadequada-pci-gateway.png)
+![resposta-inadequada-pci-gateway](https://images.contentful.com/alneenqid6w5/3P9FblRbzGIEyWo0IW6msa/278ba7912bcbb49a537e94fb7bb4a1b1/resposta-inadequada-pci-gateway.png)
 
 Para solucionar la cuestión, el comerciante debe ponerse en contacto con el gateway responsable del pago, informar los datos de la transacción y solicitar la cancelación.
diff --git a/docs/faq/es/why-dont-my-payment-methods-appear-on-the-marketplace.md b/docs/faq/es/why-dont-my-payment-methods-appear-on-the-marketplace.md
index 4526da1b8..9409199b3 100644
--- a/docs/faq/es/why-dont-my-payment-methods-appear-on-the-marketplace.md
+++ b/docs/faq/es/why-dont-my-payment-methods-appear-on-the-marketplace.md
@@ -20,4 +20,4 @@ O sea, el pago es realizado en el marketplace por las formas de pago del marketp
 
 Ejemplo: una compra realizada por el marketplace CNova se mostrará en su OMS con el siguiente mensaje en __Pago__: "Assumed value by affiliate CNova (NVP)", como en la imagen abajo.
 
-![exemplopagamento](//images.contentful.com/alneenqid6w5/54QIARxAYUM4igUYQEieSK/d9f8f1e9e95b8028cce7c6b1e7a89503/exemplopagamento.png)
+![exemplopagamento](https://images.contentful.com/alneenqid6w5/54QIARxAYUM4igUYQEieSK/d9f8f1e9e95b8028cce7c6b1e7a89503/exemplopagamento.png)
diff --git a/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md b/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
index a46359000..401a64e73 100644
--- a/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
+++ b/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
@@ -20,7 +20,7 @@ Esta definición de la categoría de destino se realiza sobre la base del __nomb
 
 Sin embargo, hay casos en que esta configuración automática no asocia el producto a la categoría correcta. Para corregir este escenario, es necesario realizar el cambio directamente en el panel del Mercado Libre o seguir el camino detallado abajo:
 
-1. [Descargue esta hoja de trabajo](//assets.ctfassets.net/alneenqid6w5/3rSztadiHm2wucS4cQ0O4o/2dba1cfc3a3687ec0510215ed040c25d/Mercado_Libre_-__Recategorizacion.xlsx) y rellene sus respectivas columnas.
+1. [Descargue esta hoja de trabajo](https://assets.ctfassets.net/alneenqid6w5/3rSztadiHm2wucS4cQ0O4o/2dba1cfc3a3687ec0510215ed040c25d/Mercado_Libre_-__Recategorizacion.xlsx) y rellene sus respectivas columnas.
 2. __ID de anuncio:__ se debe rellenar con el ID de su anuncio en Mercado Libre, sacando el guión que separa el sufijo del número.
 _`Ex:` el ID se puede encontrar en la URL del anuncio. En el siguiente enlace por ejemplo, el ID sería "MLA713224614"._
 https://articulo.mercadolibre.com.ar/MLA-713224614-cafetera-de-filtro-electrolux-cmb31-jarra-de-vidrio-_JM
diff --git a/docs/faq/es/why-is-let-me-know-not-showing.md b/docs/faq/es/why-is-let-me-know-not-showing.md
index 866615e1a..c217f112e 100644
--- a/docs/faq/es/why-is-let-me-know-not-showing.md
+++ b/docs/faq/es/why-is-let-me-know-not-showing.md
@@ -21,7 +21,7 @@ Las configuraciones básicas para exhibir **avíseme** cuando el producto está
 
 Pero existe un caso en que, aun con los ítems arriba configurados, el avíseme no aparece, que es **cuando el tipo de exhibición de la Categoría está seleccionado como Lista de SKUs**.
 
-![categoria-lista-de-skus ES](//images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
+![categoria-lista-de-skus ES](https://images.ctfassets.net/alneenqid6w5/2doqFhClnKAsqisO6qUeqA/fb3df652f2b63be1b27609322b4956bd/lista_de_skus_ES.png)
 
 En este caso, además de las configuraciones estándar, es necesario usar el control `vtex.cmc:SkuSelection`, aunque no exista más de un SKU por página.
 Luego, cuando la Categoría del producto deseado esté flechada para Lista de SKUs, como en la imagen arriba, es necesario que sea insertado el control `vtex.cmc:SkuSelection` en el template de página para que el avíseme sea exhibido.
diff --git a/docs/faq/es/why-is-my-freight-value-wrong.md b/docs/faq/es/why-is-my-freight-value-wrong.md
index a59de9a73..bc87f1480 100644
--- a/docs/faq/es/why-is-my-freight-value-wrong.md
+++ b/docs/faq/es/why-is-my-freight-value-wrong.md
@@ -23,7 +23,7 @@ Se calcula el valor de flete en base a varios factores: tabla de flete, adiciona
 3. Aquí, usted verificará el valor catastrado en la plantilla más todos los [adicionales](/es/tutorial/como-se-maneja-el-adicional-de-carga) sumados a ese valor.
 4. Caso el valor todavía no este condecente con el exhibido en la tienda, siga los pasos abajo para verificar si no hay ninguna promoción alterando el valor del flete.
 
-![por-que-meu-valor-de-frete-esta-errado sp](//images.ctfassets.net/alneenqid6w5/6Olcu5Bw88Q0Q644gQ06qQ/803b38526bb74d1fcafa2400355b8f1e/por-que-meu-valor-de-frete-esta-errado_sp.jpg)
+![por-que-meu-valor-de-frete-esta-errado sp](https://images.ctfassets.net/alneenqid6w5/6Olcu5Bw88Q0Q644gQ06qQ/803b38526bb74d1fcafa2400355b8f1e/por-que-meu-valor-de-frete-esta-errado_sp.jpg)
 
 ## Promoción
 
@@ -32,4 +32,4 @@ Se calcula el valor de flete en base a varios factores: tabla de flete, adiciona
 3. Verifique el box __Valor Total__.
 4. Verifique si, entre las promociones, existe alguna con descuento en flete. Para verificar, basta que aceda la promoción del pedido y verifique el tipo de descuento.
 
-![valortotal es](//images.ctfassets.net/alneenqid6w5/4vNJocmHWEqoqWGQgyU6Ck/d0a87594351705001565612159df9312/valortotal_es.jpg)
+![valortotal es](https://images.ctfassets.net/alneenqid6w5/4vNJocmHWEqoqWGQgyU6Ck/d0a87594351705001565612159df9312/valortotal_es.jpg)
diff --git a/docs/faq/es/why-is-my-product-appearing-in-the-wrong-category.md b/docs/faq/es/why-is-my-product-appearing-in-the-wrong-category.md
index 95d1e8a93..dc8fd52f1 100644
--- a/docs/faq/es/why-is-my-product-appearing-in-the-wrong-category.md
+++ b/docs/faq/es/why-is-my-product-appearing-in-the-wrong-category.md
@@ -22,7 +22,7 @@ El primer paso es realizar un request GET con nuestra [API de Product by Id](htt
 
 La respuesta de esta llamada trae la información de `DepartmentId` y `CategoryId`, como podemos ver en la siguiente imagen:
 
-![department-id-category-id](//images.contentful.com/alneenqid6w5/1wJqRKDEcYkGqqsMAGy0aA/bf3521922d99fe678031a1898326b1ea/department-id-category-id.png)
+![department-id-category-id](https://images.contentful.com/alneenqid6w5/1wJqRKDEcYkGqqsMAGy0aA/bf3521922d99fe678031a1898326b1ea/department-id-category-id.png)
 
 Después, usted debe comparar esta respuesta con los Ids que aparecen en su árbol de categoría. Para acceder a su árbol de categorías, siga los pasos abajo:
 
diff --git a/docs/faq/es/why-is-my-stores-zoom-not-working.md b/docs/faq/es/why-is-my-stores-zoom-not-working.md
index 85650fd6a..24e5a3a69 100644
--- a/docs/faq/es/why-is-my-stores-zoom-not-working.md
+++ b/docs/faq/es/why-is-my-stores-zoom-not-working.md
@@ -25,7 +25,7 @@ Este tamaño de imagen puede configurarse por el camino abajo:
 2. Haga clic en __Configuraciones__.
 3. Acceda a la pestaña __Tipos de Archivos__.
 
-![Tipos de Arquivo ES](//images.ctfassets.net/alneenqid6w5/4j5jxDs3lSgOmgEOgyI2KS/2321dffd3c570bba5bd73b0efba87c4e/Tipos_de_Arquivo_ES.png)
+![Tipos de Arquivo ES](https://images.ctfassets.net/alneenqid6w5/4j5jxDs3lSgOmgEOgyI2KS/2321dffd3c570bba5bd73b0efba87c4e/Tipos_de_Arquivo_ES.png)
 
 El tamaño 1000x1000 significa que el zoom resultante mostrará la imagen en ese tamaño. Por tanto, éste es el tamaño mínimo para que funcione el zoom.
 
diff --git a/docs/faq/es/why-is-the-product-not-visible-on-the-website.md b/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
index 7b8fef230..f45c0b2c4 100644
--- a/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
@@ -42,7 +42,7 @@ Te recomendamos que empieces tu búsqueda de errores por el **Catálogo**. Para
 1. Accede al Admin VTEX y navega hasta **Productos > Catálogo > Gestión de productos y SKU** para verificar los productos registrados en tu tienda.
 2. Busca el producto que deseas mostrar en la lista, tal como se ilustra en la imagen a continuación.
 
-    ![01-produto-es](//images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/b7bf043742b03bd0ea130f8541a8fbad/01-produto-es.PNG)
+    ![01-produto-es](https://images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/b7bf043742b03bd0ea130f8541a8fbad/01-produto-es.PNG)
 
 3. Sigue las instrucciones descriptas en las próximas secciones para verificar la información a continuación:
     * [Producto](#producto)
@@ -85,16 +85,16 @@ En la página de SKU, en **Productos > Catálogo > Gestión de productos y SKU**
 
     | Botón | Descripción |
     |-|-|
-    | ![04-botao-precos](//images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acceder a la __Lista de precios__ para verificar si existe un precio válido para la política comercial deseada que esté asociado a los SKU del producto. Consulta la sección de [Precios](#precios) para más información. |
-    | ![05-botao-logistica](//images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acceder a la página __Gestión del stock__ para verificar si el SKU tiene stock disponible. Consulta la sección de [Logística](#logistica) para más información. |
-    | ![06-botao-indexed-info](//images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite ver a cada **_seller_** que comercializa el SKU, la política comercial (**Policy**), el precio (**Value**) y la cantidad de SKU en stock (**Quantity**). |
+    | ![04-botao-precos](https://images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acceder a la __Lista de precios__ para verificar si existe un precio válido para la política comercial deseada que esté asociado a los SKU del producto. Consulta la sección de [Precios](#precios) para más información. |
+    | ![05-botao-logistica](https://images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acceder a la página __Gestión del stock__ para verificar si el SKU tiene stock disponible. Consulta la sección de [Logística](#logistica) para más información. |
+    | ![06-botao-indexed-info](https://images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite ver a cada **_seller_** que comercializa el SKU, la política comercial (**Policy**), el precio (**Value**) y la cantidad de SKU en stock (**Quantity**). |
 
 2. En la línea del producto correspondiente al SKU que se verificará, haz clic en la flecha hacia abajo <i class="fas fa-caret-down"></i>, al lado del botón `Modificar`.
 3. Haz clic en la opción** SKU** para acceder a la lista detallada de los SKU.
 4. En la columna **Status**, verifica que el status indicado sea `Activo`. Si los SKU están activos, continúa con el paso 7.
 5. Si algún SKU está con el status `Inactivo`, haz clic en `Modificar` para ver la información detallada del SKU.
 
-    ![07-catalogo-skus-es](//images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/720d48a725fe4740f78466149846d29a/07-catalogo-skus-es.png)
+    ![07-catalogo-skus-es](https://images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/720d48a725fe4740f78466149846d29a/07-catalogo-skus-es.png)
 
 6. En la página de información del SKU, el próximo paso es verificar los ítems que se enumeran a continuación.
     * **Activar SKU si es posible:** verifica si esta opción está seleccionada. De lo contrario, el SKU no se mostrará. Activar esta opción significa determinar que el SKU se activará si cumple con los requisitos necesarios:
@@ -109,7 +109,7 @@ En la página de SKU, en **Productos > Catálogo > Gestión de productos y SKU**
 
 <img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/1be699da86b880750f7884f9aabaa8a3/08-aba-imagens-es.png" alt="08-aba-imagens-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Pestaña  <strong>Imágenes</strong></em></figcaption></figure>
 
-![09-sku-imagens-es](//images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/06bad0f8081c24488cee7ec6d0853853/09-sku-imagens-es.PNG)
+![09-sku-imagens-es](https://images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/06bad0f8081c24488cee7ec6d0853853/09-sku-imagens-es.PNG)
 
 ### Información indexada
 
@@ -123,13 +123,13 @@ El registro de indexación muestra el status de cada SKU del producto. Si hay al
 
 En el ejemplo a continuación, podemos llegar a la conclusión de que el SKU no está disponible por falta de ítems en el stock:
 
-![10-indexed-info-code](//images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/eade8a30097193dabb38a1085d28defa/Group_1__7_.png)
+![10-indexed-info-code](https://images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/eade8a30097193dabb38a1085d28defa/Group_1__7_.png)
 
 A partir de esto, es posible tomar medidas para corregir el problema. En el caso del ejemplo, sería necesario ajustar el número de ítems en el stock del sistema de [Logística](#logistica).
 
 Un SKU activo y sin errores tendrá el registro en el indexador parecido al que se muestra a continuación:
 
-![11-indexed-info-code-active](//images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/059ed660c68d5e05fbe5f2ac0c571326/11-indexed-info-code-active.png)
+![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/059ed660c68d5e05fbe5f2ac0c571326/11-indexed-info-code-active.png)
 
 <div class="alert alert-info">
 <p>Si la información de la indexación no muestra ningún motivo para la falta de disponibilidad de los productos, y si no encontraste ningún error en el registro de los productos y SKU, probablemente lo que resuelva el problema sea volver a indexar el producto.</p>
@@ -147,7 +147,7 @@ En el módulo de **Precios**, es importante verificar que los SKU del producto t
 
 En el ejemplo a continuación, hay dos SKU sin precio base registrado. Es por esto que no hay un precio ingresado en la columna de la política comercial. Solo aparece la información _Precio no registrado_.
 
-![12-precos-es](//images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/35266b55e248d148f419219696f5b661/12-precos-es.PNG)
+![12-precos-es](https://images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/35266b55e248d148f419219696f5b661/12-precos-es.PNG)
 
 ### Crear precio base
 
@@ -175,7 +175,7 @@ El **Simulador de envío** sirve para verificar si el ítem está en stock y si
 2. Completa la información necesaria que se describe en el [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144).
 3. Haz clic en `Simulación de envío`.
 
-![13-simular-frete-es](//images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/9d99f84da1c2fa38d8457f1668eb4a5f/13-simular-frete-es.PNG)
+![13-simular-frete-es](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/9d99f84da1c2fa38d8457f1668eb4a5f/13-simular-frete-es.PNG)
 
 <div class="alert alert-info">
 <p>Para revisar un ítem específico, debes realizar la simulación con un <strong>código postal</strong> que cubra todas las <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">políticas de envío</a> registradas. Así sabrás que si un ítem no está disponible para ese CP, tampoco lo estará para algún otro.</p>
@@ -183,7 +183,7 @@ El **Simulador de envío** sirve para verificar si el ítem está en stock y si
 
 El resultado obtenido indica si el producto está disponible o no para ser entregado en la dirección informada y cuáles son las mejores opciones de envío. Ejemplo: si no hay ítems suficientes disponibles en stock, el simulador mostrará el siguiente mensaje:
 
-![14-simulador-motivos-es](//images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/2edfa46661ba21558a2d9ee2c5507a67/14-simulador-motivos-es.PNG)
+![14-simulador-motivos-es](https://images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/2edfa46661ba21558a2d9ee2c5507a67/14-simulador-motivos-es.PNG)
 
 Para más información sobre cómo usar el simulador, consulta el tutorial [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144).
 
@@ -204,7 +204,7 @@ Si un producto no está disponible en el sitio web por falta de _ítems_ en el _
 3. Para actualizar el recuento de stock, escribe la cantidad actual en la columna **Actualizar recuento** en la línea del SKU deseado, según la imagen a continuación.
 4. Haz clic en `Guardar`.
 
-![15-gerenciar-inventario-es](//images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/f8fcc9989836959c1c300c332bffb91e/15-gerenciar-inventario-es.gif)
+![15-gerenciar-inventario-es](https://images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/f8fcc9989836959c1c300c332bffb91e/15-gerenciar-inventario-es.gif)
 
 Para más información, consulta el tutorial [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139).
 
@@ -249,7 +249,7 @@ Sigue los pasos a continuación para verificar la plantilla que está usando tu
 
     En el ejemplo a continuación, la plantilla estándar que se usó es `vtex.curbside-pickup@0.x:store.curbside-pickup` y no hay una plantilla condicional.
 
-    ![16-templates-cms-es](//images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/c23d4524c1339d0f952613f13c4c3cac/16-templates-cms-es.PNG)
+    ![16-templates-cms-es](https://images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/c23d4524c1339d0f952613f13c4c3cac/16-templates-cms-es.PNG)
 
 4. Luego, debes configurar los bloques incluidos en la plantilla utilizada, tal como se indica en [Templates](#templates).
 
diff --git a/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
index 2454feb0d..2617eca32 100644
--- a/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
@@ -25,6 +25,6 @@ Para activar esta configuración:
 3. Haz clic en **Editar** en la línea `Producto - Thumb`.
 4. En el panel que aparece, se puede elegir el tamaño máximo del archivo para las imágenes en miniaturas en el campo **Tamaño máximo en KB**.
 
-![Configuración de tipo de archivo en CMS](//images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/3eb78e622efb3066eee570dc342c1a20/ES.PNG)
+![Configuración de tipo de archivo en CMS](https://images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/3eb78e622efb3066eee570dc342c1a20/ES.PNG)
 
 También te recomendamos que leas el artículo [Mejorar la performance de imágenes de productos](https://help.vtex.com/pt/tutorial/improving-the-performance-of-product-images/) para aprender cómo mejorar la calidad de cualquier imagen de la tienda reduciendo al máximo cualquier alteración en la performance de la carga de la página.
diff --git a/docs/faq/es/why-isnt-the-order-invoiced-on-the-marketplace.md b/docs/faq/es/why-isnt-the-order-invoiced-on-the-marketplace.md
index 92ec64d16..8dad09bb8 100644
--- a/docs/faq/es/why-isnt-the-order-invoiced-on-the-marketplace.md
+++ b/docs/faq/es/why-isnt-the-order-invoiced-on-the-marketplace.md
@@ -30,7 +30,7 @@ El impacto de esto es que conseguimos ir hasta el status facturado sólo en VTEX
 
 La clave de acceso de la factura es un instrumento auxiliar para la consulta de la NF-y que permite al titular de ese documento confirmar su efectiva existencia, nombre del campo Invoice Key:
 
-[]![ChaveDeAcesso](//images.contentful.com/alneenqid6w5/447ljGvDxuW0mmQoAumGOg/f1f246378401f4c9a56655974300ab04/ChaveDeAcesso-1.png)
+[]![ChaveDeAcesso](https://images.contentful.com/alneenqid6w5/447ljGvDxuW0mmQoAumGOg/f1f246378401f4c9a56655974300ab04/ChaveDeAcesso-1.png)
 
 __ ¡Recuerde! __ Este elemento de información se crea cuando se genera la factura fiscal y funciona en ERP. Si tiene uno, solicítelo.
 
diff --git a/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md b/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
index f460759de..ee7b0bc47 100644
--- a/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
+++ b/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
@@ -32,4 +32,4 @@ Para acceder a esta pantalla, siga los pasos abajo:
 
 La flag Filtro aparece en la pantalla de configuración del campo de producto.
 
-![Filtro Campo de produto](//images.contentful.com/alneenqid6w5/3XSX1nXvjW8kuCi20GaueM/d81f6eea3d6d53c78e00b3e367cbf99b/Filtro_Campo_de_produto.png)
+![Filtro Campo de produto](https://images.contentful.com/alneenqid6w5/3XSX1nXvjW8kuCi20GaueM/d81f6eea3d6d53c78e00b3e367cbf99b/Filtro_Campo_de_produto.png)
diff --git a/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 88c87fcac..ad15c1c30 100644
--- a/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/faq/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -21,7 +21,7 @@ Siga estos pasos para validar la información:
 1. Acceda al Admin de su tienda: `https://{AccountName}.myvtex.com/admin`.
 2. En el menú lateral del Admin, haga clic en __Master Data__.
 3. En el cuadro __Profile System__, haga clic en __Clientes__.
-4. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+4. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 5. Haga clic en el registro del cliente para acceder a los detalles del perfil.
 
 En la sección __Contato__, usted verá que la opción `Es Empresa?` Se llena con el valor `No`. Al mismo tiempo, en la sección __Datos de la empresa__, usted verá que el campo `Tipo documento` tiene el valor `cnpj`.
diff --git a/docs/faq/es/why-was-the-item-splitted-in-the-cart.md b/docs/faq/es/why-was-the-item-splitted-in-the-cart.md
index 2d4a0cc72..671181b72 100644
--- a/docs/faq/es/why-was-the-item-splitted-in-the-cart.md
+++ b/docs/faq/es/why-was-the-item-splitted-in-the-cart.md
@@ -18,7 +18,7 @@ Este escenario sucede cuando más de un artículo del mismo SKU se separa en má
 
 Pero hay escenarios en que el importe de descuento es indivisible por el número de artículos, especialmente en los casos en que el SKU tiene una unidad de multiplicación, por lo que necesitamos dar diferentes descuentos para los artículos del mismo SKU, de manera que el importe de descuento sea correcto. Lo que termina dejando los precios diferentes y separando cada unidad en una fila. Vea mejor esta explicación con el siguiente ejemplo.
 
-![Por que o item do carrinho foi separado](//images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/4e46b5b17ed4c3eeb1cfba4e3440d845/Por_que_o_item_do_carrinho_foi_separado.jpg)
+![Por que o item do carrinho foi separado](https://images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/4e46b5b17ed4c3eeb1cfba4e3440d845/Por_que_o_item_do_carrinho_foi_separado.jpg)
 
 1. Unidad de multiplicación.
 2. Precio del producto después del descuento.
diff --git a/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index f75615794..8da2b358c 100644
--- a/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -18,7 +18,7 @@ Existe una regla de seguridad en el Checkout que está relacionada con la facili
 
 Como el SmartCheckout permite cerrar una compra sólo con el email y con el CVV de la tarjeta, si el cliente ya ha finalizado la compra anteriormente, limitamos la cantidad de finalización de compra sin éxito a 3. Depois de eses 3 intentos, solicitamos el login del cliente.
 
-![LoginES](//images.ctfassets.net/alneenqid6w5/3iJKRBnU00IAwu24SMey0y/50a69e45f7f1a8380e0299490fb58603/LoginES.png)
+![LoginES](https://images.ctfassets.net/alneenqid6w5/3iJKRBnU00IAwu24SMey0y/50a69e45f7f1a8380e0299490fb58603/LoginES.png)
 
 O sea, en el caso de que el cliente finalice la compra tan sólo con el email y el CVV de la tarjeta de crédito y la autorización de la operadora no ocurra en hasta 3 veces seguidas, es mostrada la pantalla de login para que el cliente siga intentando comprar. Ese conteo vuelve al inicio cuando el cliente inicia sesión y completa con éxito su compra.
 
diff --git a/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md b/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md
index b77c277a9..145a777ee 100644
--- a/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md
+++ b/docs/faq/es/why-wasnt-the-promotion-applied-to-the-marketplace.md
@@ -16,7 +16,7 @@ legacySlug: por-que-la-promocion-no-fue-aplicada-em-el-marketplace
 
 Para crear una promoción para marketplaces, el escenario es casi el mismo de una promoción común. Sin embargo, se debe seleccionar en el campo **política comercial** el valor **Tienda(s) de tercero(s)** y seleccionar la **política comercial** usada por el marketplace o llenar el campo **afiliado** con el ID del marketplace.
 
-![marketplace.ess](//images.ctfassets.net/alneenqid6w5/1eKWkGJX4m9jrQC971dxJH/50bec937a116cdd40cdcd26fc6c337ce/marketplace.ess.png)
+![marketplace.ess](https://images.ctfassets.net/alneenqid6w5/1eKWkGJX4m9jrQC971dxJH/50bec937a116cdd40cdcd26fc6c337ce/marketplace.ess.png)
 
 Para obtener más información sobre cómo hacerlo, lea nuestro [artículo sobre cómo crear promoción para el marketplace](/es/tutorial/promocion-para-marketplace).
 
diff --git a/docs/faq/pt/ab-testing-why-is-it-not-working-google-analytics.md b/docs/faq/pt/ab-testing-why-is-it-not-working-google-analytics.md
index 0782d8d86..70cd2def7 100644
--- a/docs/faq/pt/ab-testing-why-is-it-not-working-google-analytics.md
+++ b/docs/faq/pt/ab-testing-why-is-it-not-working-google-analytics.md
@@ -26,10 +26,10 @@ Dessa forma o Teste AB funcionará com sucesso.
 Seguem as telas que exemplificam o passo a passo:
 
 __Tela Controle__:
-![](//images.contentful.com/alneenqid6w5/3GIGsJXbo4KAMikCqesM6s/e8231671043f3ce763c8faf87718d6d7/testeAB-controle1-300x138.png)
+![](https://images.contentful.com/alneenqid6w5/3GIGsJXbo4KAMikCqesM6s/e8231671043f3ce763c8faf87718d6d7/testeAB-controle1-300x138.png)
 
 __Tela Script__:
-![](//images.contentful.com/alneenqid6w5/7gUgGNnvlmcQyiW4A0A6ao/dac8e58e0931686de3e9e4ae46c66afa/testeAB-script-300x148.png)
+![](https://images.contentful.com/alneenqid6w5/7gUgGNnvlmcQyiW4A0A6ao/dac8e58e0931686de3e9e4ae46c66afa/testeAB-script-300x148.png)
 
 __Tela Template__:
-![](//images.contentful.com/alneenqid6w5/4u6uQHYOPuw6Ws8CYKCISo/d04c5fbcc08a5de8a05a242ef76e7ecf/testeAB-template-300x216.png)
+![](https://images.contentful.com/alneenqid6w5/4u6uQHYOPuw6Ws8CYKCISo/d04c5fbcc08a5de8a05a242ef76e7ecf/testeAB-template-300x216.png)
diff --git a/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
index 1929b0e69..56fa2bdbd 100644
--- a/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -29,11 +29,11 @@ Para configurar o [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
 1. Abra o [Google Chrome](https://www.google.com/intl/pt-BR/chrome/) no seu computador.
 2. Clique no botão `F12` do seu teclado ou com o botão direito do mouse em qualquer lugar da tela e selecione **Inspecionar**.
 3. Clique nos três pontos verticais na parte superior direita da página, conforme indicado na imagem abaixo.
-![Customizations1 - PT](//images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/cb8f01010eb287fcc5b63f2b9956a2ad/Captura_de_Tela_2022-09-20_a__s_14.51.15.png)
+![Customizations1 - PT](https://images.ctfassets.net/alneenqid6w5/3fMKFRgHKwCa8dlwcMbnDk/cb8f01010eb287fcc5b63f2b9956a2ad/Captura_de_Tela_2022-09-20_a__s_14.51.15.png)
 4. Selecione **Mais ferramentas** e, em seguida, **Bloqueios de solicitação de rede** para bloquear todas as customizações feitas via CSS, JavaScript e Google Tag Manager. 
-![Customizations2 - PT](//images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/cee054457174fb6309d84826753d7411/Captura_de_Tela_2022-09-20_a__s_14.59.20.png)
+![Customizations2 - PT](https://images.ctfassets.net/alneenqid6w5/7wjDCIMx0j0VMLFBlJs4x3/cee054457174fb6309d84826753d7411/Captura_de_Tela_2022-09-20_a__s_14.59.20.png)
 5. A aba **Bloqueios de solicitação de rede** abrirá em seguida como mostra a imagem abaixo:
-![Customizations3 - PT](//images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/8eaa7683eaccc0f4af13088a328c022b/Captura_de_Tela_2022-09-20_a__s_15.00.47.png)
+![Customizations3 - PT](https://images.ctfassets.net/alneenqid6w5/1oi04fyBlkMVmio4LtMVcv/8eaa7683eaccc0f4af13088a328c022b/Captura_de_Tela_2022-09-20_a__s_15.00.47.png)
 6. Clique em `Adicionar padrão` para definir o primeiro recursos será bloqueado. Para adicionar mais recursos, clique em `+` e, depois de defini-lo, clique em `Adicionar`. Essa configuração precisa ser feita apenas uma vez no seu navegador. Inclua os itens abaixo:
 
  * `*/arquivos/*.js`
@@ -42,7 +42,7 @@ Para configurar o [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
  * `*/files/*.css`
  * `*gtm.js*`
 
-![Customizations4 - PT](//images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/021f16c927cedf17ec8c8410b447c026/Captura_de_Tela_2022-09-20_a__s_15.14.39.png)
+![Customizations4 - PT](https://images.ctfassets.net/alneenqid6w5/49opNOaTq3t2xJ2HpAnuo1/021f16c927cedf17ec8c8410b447c026/Captura_de_Tela_2022-09-20_a__s_15.14.39.png)
 <ol start ="7">
 <li>Marque a opção <b>Ativar bloqueio de solicitação de rede</b> e habilite todos os checkboxes abaixo. Essa será a configuração que ficará definida por padrão, com todas as opções habilitadas para bloqueio.</li>
 <li>Agora atualize a página. Ela será exibida sem os componentes customizados.</li>
diff --git a/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md b/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
index 0ca7daf23..628144d65 100644
--- a/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
+++ b/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
@@ -23,8 +23,8 @@ __Para acessar essa planilha, siga os passos abaixo:__
 1. Acesse o módulo __OMS__
 2. Clique no ícone de __filtro__
 3. Faça uma busca __por período__ (lembrando que o range máximo permitido é de até 6 meses. No caso de querer fazer uma busca por perído de 1 ano, por exemplo, faça a busca 2 vezes) 
-4. Ao retornar para a lista já filtrada de pedidos, __clique no ícone de exportação__.![exportacaoOMS](//images.contentful.com/alneenqid6w5/3pX1xFqvS0uMOEe8OUquci/81e2be7c1948d62a863cfccfc36f18a9/exportacaoOMS.png)
-5. Será exibida uma barra de progresso. Então, para finalizar, é preciso clicar em __Exportar xxx pedidos para e-mail__.![ExportarOMS](//images.contentful.com/alneenqid6w5/3Z7h82etgIuQcUI6iGsgyk/11bbadc4b3c2174c82844e9125af8e50/ExportarOMS.png)
+4. Ao retornar para a lista já filtrada de pedidos, __clique no ícone de exportação__.![exportacaoOMS](https://images.contentful.com/alneenqid6w5/3pX1xFqvS0uMOEe8OUquci/81e2be7c1948d62a863cfccfc36f18a9/exportacaoOMS.png)
+5. Será exibida uma barra de progresso. Então, para finalizar, é preciso clicar em __Exportar xxx pedidos para e-mail__.![ExportarOMS](https://images.contentful.com/alneenqid6w5/3Z7h82etgIuQcUI6iGsgyk/11bbadc4b3c2174c82844e9125af8e50/ExportarOMS.png)
 
 Sua solicitação irá para uma fila, que pode ser acompanhada pelo OMS. Quando chegar sua vez, você receberá a planilha de pedidos no seu e-mail.
 
diff --git a/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
index 36fb365b2..60d0ee256 100644
--- a/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -31,7 +31,7 @@ Por isso, para ter acesso ao change seller, a afiliação com split deve ser con
 - __Use O Comportamento Recomendado Pelo Processador de Pagamentos__.
 - __Desativado: Não Capturado Automaticamente__.
 
-![Captura automática de pagamento](//images.ctfassets.net/alneenqid6w5/6oARqXfu6KSJ6g8ZH4069P/cf5b21c4ecb29930d9e52d7df430d60c/Captura_Autom__tica.png)
+![Captura automática de pagamento](https://images.ctfassets.net/alneenqid6w5/6oARqXfu6KSJ6g8ZH4069P/cf5b21c4ecb29930d9e52d7df430d60c/Captura_Autom__tica.png)
 
 ### Selecionando o comportamento de liquidação não automática, quando o pagamento será liquidado?
 
diff --git a/docs/faq/pt/file-upload-button-is-not-displayed-at-cms.md b/docs/faq/pt/file-upload-button-is-not-displayed-at-cms.md
index 21131ef39..3b8f7f85b 100644
--- a/docs/faq/pt/file-upload-button-is-not-displayed-at-cms.md
+++ b/docs/faq/pt/file-upload-button-is-not-displayed-at-cms.md
@@ -21,7 +21,7 @@ Se você tem este problema no Google Chrome, basta ativar o plugin do Flash faze
 1. Clicar no botão de informação ou no cadeado, que precede a URL atual;
 2. Na linha correspondente ao Flash, que normalmente está como "Perguntar (padrão)", selecionar "Sempre permitir neste site".
 
-![chrome-flash](//images.contentful.com/alneenqid6w5/URF5k1wvQsaAiSoOeo4WI/5560f944b3b3fabb21bfbf4cebe21037/chrome-flash.jpg)
+![chrome-flash](https://images.contentful.com/alneenqid6w5/URF5k1wvQsaAiSoOeo4WI/5560f944b3b3fabb21bfbf4cebe21037/chrome-flash.jpg)
 
 Normalmente esse problema está ligado à disponibilidade do Flash Player no navegador, e para o site acessado. 
 
diff --git a/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md b/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md
index 7bcd9be55..2bb662dbf 100644
--- a/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md
+++ b/docs/faq/pt/how-do-i-find-the-order-nsu-and-tid.md
@@ -24,4 +24,4 @@ NSU e TID são dados de pagamento que ficam registrados em __Pagamentos__, na se
 
 Essas informações são informadas à VTEX durante as transações e são organizadas para uma simples visualização em **+ Informações**, no [detalhe do pedido](/pt/tutorial/como-visualizar-detalhes-do-pedido "detalhe do pedido"), conforme imagem abaixo:
 
-![mais-informações-detalhes-pedido pt](//images.ctfassets.net/alneenqid6w5/5SaZEE8HcJHaXfdahYfueX/aae0b71aea18bd58876bdf3b5af7ca4e/mais-informa____es-detalhes-pedido_pt.png)
+![mais-informações-detalhes-pedido pt](https://images.ctfassets.net/alneenqid6w5/5SaZEE8HcJHaXfdahYfueX/aae0b71aea18bd58876bdf3b5af7ca4e/mais-informa____es-detalhes-pedido_pt.png)
diff --git a/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md b/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md
index 67153d3bd..006608653 100644
--- a/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md
+++ b/docs/faq/pt/how-to-associate-two-promotions-to-the-same-coupon.md
@@ -31,7 +31,7 @@ Confira abaixo como realizar esse processo:
 4. Vá para a seção __Quais as condições para a promoção ser válida?__.
 5. Insira o código do cupom em __utm_source__.
 
-  ![Sincronizar promoções no mesmo cupom - 1 - PT](//images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/070d7f66702c0c4c71fa1431b3d896fc/7yJhwPnclx3tCiJdgpcYyv_-_PT.png)
+  ![Sincronizar promoções no mesmo cupom - 1 - PT](https://images.ctfassets.net/alneenqid6w5/7yJhwPnclx3tCiJdgpcYyv/070d7f66702c0c4c71fa1431b3d896fc/7yJhwPnclx3tCiJdgpcYyv_-_PT.png)
 
 6. Clique em `Criar cupom a partir das UTMs acima`.
 7. Clique em `Salvar`.
@@ -39,6 +39,6 @@ Confira abaixo como realizar esse processo:
 9. Repita o processo com a segunda promoção regular.
 10. Ao final, ambas as promoções devem apresentar a mesma UTM.
 
-  ![Sincronizar promoções no mesmo cupom - 2 - PT](//images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/4aebcc54458e4661a94360cf6d9f566a/5nhdQy1Y4YWs4pHHokSA44_-_PT.png)
+  ![Sincronizar promoções no mesmo cupom - 2 - PT](https://images.ctfassets.net/alneenqid6w5/5nhdQy1Y4YWs4pHHokSA44/4aebcc54458e4661a94360cf6d9f566a/5nhdQy1Y4YWs4pHHokSA44_-_PT.png)
 
 Desse modo, o cliente pode abater os dois valores antes de finalizar a compra. 
diff --git a/docs/faq/pt/how-to-configure-mercadopago-transparente.md b/docs/faq/pt/how-to-configure-mercadopago-transparente.md
index 79c236b00..18ace6cb2 100644
--- a/docs/faq/pt/how-to-configure-mercadopago-transparente.md
+++ b/docs/faq/pt/how-to-configure-mercadopago-transparente.md
@@ -32,7 +32,7 @@ Essas configurações são realizadas em seu Google TagManager.
 8. Salve o acionador;
 9. Clique no botão **Criar Tag**, insira um nome para esta tag e Salve.
 
-![](//images.contentful.com/alneenqid6w5/YndMcdc0aAw2GKYU0EyU2/c917ac451cfeb262d8354164c6caa285/MercadoPagoTransparente_1_PT.gif)
+![](https://images.contentful.com/alneenqid6w5/YndMcdc0aAw2GKYU0EyU2/c917ac451cfeb262d8354164c6caa285/MercadoPagoTransparente_1_PT.gif)
 
 ## Criando a segunda tag
 
@@ -49,4 +49,4 @@ Essas configurações são realizadas em seu Google TagManager.
 9. Clique no botão **Criar Tag**, insira um nome para esta tag e Salve;
 10. No canto superior direito, clique em **Publicar** e logo após em **Publicar.**
 
-![](//images.contentful.com/alneenqid6w5/32NgyD7KNqicqiASoIUEkK/892ab0a77b4bf2295dcb72d6335de49e/MercadoPagoTransparente_2_PT.gif)
+![](https://images.contentful.com/alneenqid6w5/32NgyD7KNqicqiASoIUEkK/892ab0a77b4bf2295dcb72d6335de49e/MercadoPagoTransparente_2_PT.gif)
diff --git a/docs/faq/pt/how-to-disable-the-two-factor-authentication.md b/docs/faq/pt/how-to-disable-the-two-factor-authentication.md
index ad6c68486..4d00a1a45 100644
--- a/docs/faq/pt/how-to-disable-the-two-factor-authentication.md
+++ b/docs/faq/pt/how-to-disable-the-two-factor-authentication.md
@@ -16,8 +16,8 @@ legacySlug: como-desabilitar-a-autenticacao-de-dois-fatores
 
 Para desabilitar o login via autenticação de dois fatores da sua conta (two factor authentication), os seguintes passos devem ser seguidos.
 
-1. Faça login com seu usuário e senha;![2FA 1](//images.contentful.com/alneenqid6w5/4cgNDZ16dGoQGKK6MKeK0m/8afc25a77f0e1554a03a788de5bc19bb/2FA_1.png)
-2. Insira no campo que aparece o código enviado para o seu celular e clicar no botão **Configure telefone**;![2FA 2](//images.contentful.com/alneenqid6w5/4uMb0UXDNSMa4sMAOSMMaO/2a4eb422eccd35fc4a491018c4cc1517/2FA_2.png)
-3. Clique no botão **Remover telefone**.![2FA 3](//images.contentful.com/alneenqid6w5/1p3qDi9viUgWqWCAyiuom0/456e8eefa5fc1f5dc845f9715e120304/2FA_3.png)
+1. Faça login com seu usuário e senha;![2FA 1](https://images.contentful.com/alneenqid6w5/4cgNDZ16dGoQGKK6MKeK0m/8afc25a77f0e1554a03a788de5bc19bb/2FA_1.png)
+2. Insira no campo que aparece o código enviado para o seu celular e clicar no botão **Configure telefone**;![2FA 2](https://images.contentful.com/alneenqid6w5/4uMb0UXDNSMa4sMAOSMMaO/2a4eb422eccd35fc4a491018c4cc1517/2FA_2.png)
+3. Clique no botão **Remover telefone**.![2FA 3](https://images.contentful.com/alneenqid6w5/1p3qDi9viUgWqWCAyiuom0/456e8eefa5fc1f5dc845f9715e120304/2FA_3.png)
 
-Com isso, a autenticação de dois fatores será desativada de sua conta e você será redirecionado para o Admin.![2FA 4](//images.contentful.com/alneenqid6w5/5e37R8mEEMuSWwmMAmsGAC/b9caea8225ee2c4421a430553a6f51ad/2FA_4.png)
+Com isso, a autenticação de dois fatores será desativada de sua conta e você será redirecionado para o Admin.![2FA 4](https://images.contentful.com/alneenqid6w5/5e37R8mEEMuSWwmMAmsGAC/b9caea8225ee2c4421a430553a6f51ad/2FA_4.png)
diff --git a/docs/faq/pt/how-to-edit-a-whatsapp-link.md b/docs/faq/pt/how-to-edit-a-whatsapp-link.md
index 5c671cfd2..1b8461129 100644
--- a/docs/faq/pt/how-to-edit-a-whatsapp-link.md
+++ b/docs/faq/pt/how-to-edit-a-whatsapp-link.md
@@ -18,7 +18,7 @@ No painel da **VTEX Assisted Sales (SuiteShare)**, acesse a opção _**Atrair >
 
 Na nova página, localize o link que você deseja editar, clique na seta localizada no lado direito e clique na opção **Editar**. 
 
-![LinkWhatsapp](//images.ctfassets.net/alneenqid6w5/4o2p2Hz94PIONgv9fK3Wzs/ac8052b0a1343b7437699b3ce1318d22/LinkWhatsapp.png)
+![LinkWhatsapp](https://images.ctfassets.net/alneenqid6w5/4o2p2Hz94PIONgv9fK3Wzs/ac8052b0a1343b7437699b3ce1318d22/LinkWhatsapp.png)
 
 Pronto, basta editar a opção desejada. 
 
diff --git a/docs/faq/pt/how-to-find-facebook-pixel.md b/docs/faq/pt/how-to-find-facebook-pixel.md
index 0ac44adbc..f9f0f9f4a 100644
--- a/docs/faq/pt/how-to-find-facebook-pixel.md
+++ b/docs/faq/pt/how-to-find-facebook-pixel.md
@@ -16,16 +16,16 @@ legacySlug: como-encontrar-pixel-do-facebook
 
 Para começar a capturar dados do público por meio do Link Manager, você precisa configurar os pixels para cada uma das suas plataformas de publicidade. Para encontrar seu ID de pixel no Facebook, siga as instruções abaixo. Não tem um pixel do Facebook configurado? [Siga as instruções aqui para começar](https://www.facebook.com/business/help/952192354843755).
 
-![Pixel Facebook](//images.ctfassets.net/alneenqid6w5/SyRmwIJcSHT6hub7cHL0i/57094d247c03c7768144dce07fc4f88c/Facebook1.png)
+![Pixel Facebook](https://images.ctfassets.net/alneenqid6w5/SyRmwIJcSHT6hub7cHL0i/57094d247c03c7768144dce07fc4f88c/Facebook1.png)
 
 Faça o login no Facebook e vá para sua conta do Gerenciador de Anúncios.
 
 Abra a barra de navegação e selecione Gerenciador de eventos.
 
-![Gerenciador de Negócios Facebook](//images.ctfassets.net/alneenqid6w5/2zRxhjDHyVTj1VqTOKjnP3/ff5aa015c1ca8809ce3cf43b2c2e4644/Facebook2.png)
+![Gerenciador de Negócios Facebook](https://images.ctfassets.net/alneenqid6w5/2zRxhjDHyVTj1VqTOKjnP3/ff5aa015c1ca8809ce3cf43b2c2e4644/Facebook2.png)
 
 Copie o Pixel ID do pixel que você deseja usar.
 
-![Pixel ID](//images.ctfassets.net/alneenqid6w5/1ViWYddvpIbNYruMIjG9Xx/aa38ac1dc6d812a86e7a962752d59369/Facebook3.png)
+![Pixel ID](https://images.ctfassets.net/alneenqid6w5/1ViWYddvpIbNYruMIjG9Xx/aa38ac1dc6d812a86e7a962752d59369/Facebook3.png)
 
 Pronto! Agora você poderá adicionar o seu Pixel do Facebook na opção de _**Atrair > Remarketing**_ da **VTEX Assisted Sales (SuiteShare)**.
diff --git a/docs/faq/pt/how-to-find-google-analytics-pixel.md b/docs/faq/pt/how-to-find-google-analytics-pixel.md
index aa10ace25..6422975fa 100644
--- a/docs/faq/pt/how-to-find-google-analytics-pixel.md
+++ b/docs/faq/pt/how-to-find-google-analytics-pixel.md
@@ -16,11 +16,11 @@ legacySlug: como-encontrar-o-pixel-do-google-analytics
 
 Para encontrar o ID de acompanhamento faça login na sua conta do [Analytics](https://analytics.google.com/analytics/web/#/).
 
-![GoogleAnalyticsLogo](//images.ctfassets.net/alneenqid6w5/1ahGCXWIcYa4uTIo9RCtLO/bc57ebf9e9eed16c22431dc6b06939d0/GoogleAnalyticsLogo.png)
+![GoogleAnalyticsLogo](https://images.ctfassets.net/alneenqid6w5/1ahGCXWIcYa4uTIo9RCtLO/bc57ebf9e9eed16c22431dc6b06939d0/GoogleAnalyticsLogo.png)
 
 Clique em **Administrador**. 
 
-![GoogleAnalytics_menu](//images.ctfassets.net/alneenqid6w5/7weyAzsvGxyeYyU4EHA9JG/7b761daaf7806248de5d6f259da52a3d/GoogleAnalytics_menu.png)
+![GoogleAnalytics_menu](https://images.ctfassets.net/alneenqid6w5/7weyAzsvGxyeYyU4EHA9JG/7b761daaf7806248de5d6f259da52a3d/GoogleAnalytics_menu.png)
 
 Selecione uma conta no menu na coluna conta.
 
@@ -28,6 +28,6 @@ Selecione uma propriedade no menu na coluna propriedade.
 
 Em propriedade, clique em Informações de rastreamento e depois em Código de acompanhamento. Seu ID de rastreamento é exibido na parte superior da página.
 
-![GoogleAnalytics_informações de acompanhamento](//images.ctfassets.net/alneenqid6w5/7Dz2GrDyXgbGmS49YMcZ7S/627ff46b8b3e2656d270b6ea11ace913/GoogleAnalytics_informa____es_de_acompanhamento.png)
+![GoogleAnalytics_informações de acompanhamento](https://images.ctfassets.net/alneenqid6w5/7Dz2GrDyXgbGmS49YMcZ7S/627ff46b8b3e2656d270b6ea11ace913/GoogleAnalytics_informa____es_de_acompanhamento.png)
 
 Pronto! Agora você poderá adicionar o seu Pixel do Google Analytics na opção de _**Atrair > Remarketing**_ da **VTEX Assisted Sales (SuiteShare)**.
diff --git a/docs/faq/pt/how-to-find-google-tag-manager-pixel.md b/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
index 5397ee41e..7efa61583 100644
--- a/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
+++ b/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
@@ -16,7 +16,7 @@ legacySlug: como-encontrar-o-pixel-do-google-tag-manager
 
 Faça login no Gerenciador de [tags do Google](https://www.google.com/intl/pt-BR/tagmanager/).
 
-![Gerenciador de Tags Google](//images.ctfassets.net/alneenqid6w5/6LoAdO0EywCYPEraFxwKb5/4e29b0762d74cc540d81c9fb6b64ef2a/Gerenciador_de_Tags_Google.png)
+![Gerenciador de Tags Google](https://images.ctfassets.net/alneenqid6w5/6LoAdO0EywCYPEraFxwKb5/4e29b0762d74cc540d81c9fb6b64ef2a/Gerenciador_de_Tags_Google.png)
 
 Na opção **Contâiner ID**, você encontrará o código. Copie-o.
 
@@ -24,6 +24,6 @@ Na opção **Contâiner ID**, você encontrará o código. Copie-o.
   <p><b>Atenção</b>: Seu ID deve conter o prefixo do GTM.</p>
 </div>
 
-![Gerenciador de tags Goggle 2](//images.ctfassets.net/alneenqid6w5/4UqVluoy3i3PraHgP3upQ3/5f45d8f38635a803a00b417667102433/Gerenciador_de_Tags_Google_2.png)
+![Gerenciador de tags Goggle 2](https://images.ctfassets.net/alneenqid6w5/4UqVluoy3i3PraHgP3upQ3/5f45d8f38635a803a00b417667102433/Gerenciador_de_Tags_Google_2.png)
 
 Pronto! Agora você poderá adicionar o seu Pixel do Google Tag Manager na opção de _**Atrair > Remarketing**_ da **VTEX Assisted Sales (SuiteShare)**.
diff --git a/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md b/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md
index b8eccd3ea..03ce3f390 100644
--- a/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md
+++ b/docs/faq/pt/i-cant-edit-a-required-field-on-master-data.md
@@ -19,11 +19,11 @@ legacySlug: nao-consigo-editar-um-campo-obrigatorio-do-master-data
 1. No menu do admin, selecione o módulo __Master Data__. 
 2. Certifique-se que está na aba __Aplicações__, dentro de __Links Rápidos__.
 3. Clique na engrenagem em __Profile System__.
-![MasterDataTutorial 1 UM](//images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
+![MasterDataTutorial 1 UM](https://images.ctfassets.net/alneenqid6w5/6BwZrUrNopO6Nb3n49B8L9/ba74f6ae261e1d8f0fc7a32cf7ad321f/MasterDataTutorial_1_UM.jpg)
 4. Clique no __lápis__ ao lado do item que deseja configurar.
-![MasterDataTutorial2](//images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
+![MasterDataTutorial2](https://images.ctfassets.net/alneenqid6w5/1OU9KjvK8sUUtHr5MZqbci/4297f3f56819f622d77845054b3dbb0d/MasterDataTutorial2.png)
 5. Clique em __Schemas de Layout__.
 6.  Na __Seção 1__, escolha o item do campo que deseja configurar.
 7. Em __Configurações avançadas do campo__, selecione__ Campo obrigatório no formulário__.
-![MasterDataTutorial3](//images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
+![MasterDataTutorial3](https://images.ctfassets.net/alneenqid6w5/1gYKfvwuQaL5fR6nlyZQ8Y/50be6084a8df932cced78ae6359981bc/MasterDataTutorial3.png)
 A opção também pode ser alterada sempre que desejado.
diff --git a/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md b/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
index c2863cdc5..99e77f915 100644
--- a/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
+++ b/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
@@ -16,6 +16,6 @@ legacySlug: mensagem-erro-the-limit-of-activated-calculators-has-been-reached
 
 Essa mensagem indica que o número máximo de promoções foi atingido e que não é possível criar a promoção que estava sendo configurada. É possível verificar esse dado na tela de administração de promoções (`{AccountName}.vtexcommercestable.com.br/admin/rnb`), conforme a imagem abaixo.
 
-![](//images.contentful.com/alneenqid6w5/3MZkA9wEMgYO0mYi2YcQSa/b132514fefacffecfeed56a99307daaf/promo__es.jpg)
+![](https://images.contentful.com/alneenqid6w5/3MZkA9wEMgYO0mYi2YcQSa/b132514fefacffecfeed56a99307daaf/promo__es.jpg)
 
 Você deve rever suas promoções ativas para ajustá-las e reorganizá-las, de modo que não sejam necessárias tantas unidades. Geralmente, é possível a união de várias regras em apenas uma promoção. Desse modo, melhorando a performance do carrinho e a organização das promoções.
diff --git a/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index d8ff57db6..26596aa42 100644
--- a/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -31,6 +31,6 @@ _Para fazer a inclusão manual de SKUs específicos, siga o passo a passo abaixo
 5. Dê um nome à sua Coleção (os demais campos não devem ser preenchidos).
 6. Insira os SKUs no campo informado e __separe-os com vírgulas__.
 
-![recurrence-specific-skus](//images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
+![recurrence-specific-skus](https://images.ctfassets.net/alneenqid6w5/70r903nMha2s220AsC2W6k/2fa8421274d56304d680388cc3309323/recurrence-specific-skus.png)
 
 Por fim, dê um nome ao __Grupo__ da sua Coleção e clique em __Save Group__.
diff --git a/docs/faq/pt/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md b/docs/faq/pt/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
index a9ed5307b..a5b752e76 100644
--- a/docs/faq/pt/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
+++ b/docs/faq/pt/ive-edited-a-placeholder-and-the-site-hasnt-been-updated-what-to-do.md
@@ -19,7 +19,7 @@ legacySlug: editei-um-placeholder-e-o-site-nao-atualiza-o-que-fazer
 Normalmente, isso acontece porque o lojista salva o placeholder após as alterações mas não salva o layout.
 
 Sempre que você alterar um placeholder, lembre-se de:
-1. Salvar o placeholder.![savePlaceholder](//images.contentful.com/alneenqid6w5/3CefNlrWxWOO8kgyKEkMMk/3deea3f44d5f21e037e799a07500f147/savePlaceholder.png)
-2. Salvar o layout.![saveLayout](//images.contentful.com/alneenqid6w5/1WUC8Yy2Vq2qEOAuQMG0km/83bce62e6f8145112655dae251474bf5/saveLayout.png)
+1. Salvar o placeholder.![savePlaceholder](https://images.contentful.com/alneenqid6w5/3CefNlrWxWOO8kgyKEkMMk/3deea3f44d5f21e037e799a07500f147/savePlaceholder.png)
+2. Salvar o layout.![saveLayout](https://images.contentful.com/alneenqid6w5/1WUC8Yy2Vq2qEOAuQMG0km/83bce62e6f8145112655dae251474bf5/saveLayout.png)
 
 
diff --git a/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md b/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md
index edfcc7d8c..94390c9eb 100644
--- a/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md
+++ b/docs/faq/pt/kitlook-is-not-displayed-in-the-shop-window.md
@@ -32,7 +32,7 @@ __Preencha o campo da Label__
 4. Vá para a aba __Imagens__
 5. Insira um termo para preencher a __Label__
 
-  ![Kit Look - Label - PT](//images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/ba398076f25a3f1bc85df073e0e571c4/7FR879Lzl3eEDmAHiBV0TV_pt.png)
+  ![Kit Look - Label - PT](https://images.ctfassets.net/alneenqid6w5/7FR879Lzl3eEDmAHiBV0TV/ba398076f25a3f1bc85df073e0e571c4/7FR879Lzl3eEDmAHiBV0TV_pt.png)
 
 6. Clique em __Salvar__
 
diff --git a/docs/faq/pt/locate-the-google-ads-pixel.md b/docs/faq/pt/locate-the-google-ads-pixel.md
index 838767411..b6d3f4371 100644
--- a/docs/faq/pt/locate-the-google-ads-pixel.md
+++ b/docs/faq/pt/locate-the-google-ads-pixel.md
@@ -16,23 +16,23 @@ legacySlug: localize-o-pixel-do-google-ads
 
 Para localizar o ID do pixel de remarketing é necessário realizar o login dentro do Google ads.
 
-![Google_Ads](//images.ctfassets.net/alneenqid6w5/3WHxCxHMQ7glNyc32wFa8G/3de7c855fa9574725c9df93eaf555ff9/Google_Ads.png)
+![Google_Ads](https://images.ctfassets.net/alneenqid6w5/3WHxCxHMQ7glNyc32wFa8G/3de7c855fa9574725c9df93eaf555ff9/Google_Ads.png)
 
 O próximo passo, é acessar o menu **Ferramentas e Definições** e em **Biblioteca Partilhada**, acesse **Gestor de públicos-alvo**, conforme a imagem abaixo:
 
-![Google_Ads_Menu](//images.ctfassets.net/alneenqid6w5/38QwaYvtbHLw3o52tKJjG1/417e13fdbf1bea474d9cb6e180808f9f/Google_Ads_Menu.png)
+![Google_Ads_Menu](https://images.ctfassets.net/alneenqid6w5/38QwaYvtbHLw3o52tKJjG1/417e13fdbf1bea474d9cb6e180808f9f/Google_Ads_Menu.png)
 
 Agora, em gestor de público alvo, selecione a opção **Origens de públicos-alvo**.
 
-![Google_Ads_Menu_2](//images.ctfassets.net/alneenqid6w5/29cE5O5pA3VrxJVmBrA52Y/9c5ae98d7886f80430928be4049dd7f8/Google_Ads_Menu_2.png)
+![Google_Ads_Menu_2](https://images.ctfassets.net/alneenqid6w5/29cE5O5pA3VrxJVmBrA52Y/9c5ae98d7886f80430928be4049dd7f8/Google_Ads_Menu_2.png)
 
 Dentro do menu Origens de públicos-alvo, algumas opções estarão disponíveis (Analytics, Youtube, etc), selecione a tag do Google ADS. Acesse **Detalhes** ou em **Editar origem**. Agora, o próximo passo é selecionar o tipo de dados recolhidos por esta origem:
 
-![Google_Ads_Menu_3](//images.ctfassets.net/alneenqid6w5/17FFDoGSDe74oPlheNvL1a/3a05b360a1375aed52e4e29a5f32ea45/Google_Ads_Menu_3.png)
+![Google_Ads_Menu_3](https://images.ctfassets.net/alneenqid6w5/17FFDoGSDe74oPlheNvL1a/3a05b360a1375aed52e4e29a5f32ea45/Google_Ads_Menu_3.png)
 
 A seguir, selecione o tipo de tag:
 
-![Google_Ads_Menu_4](//images.ctfassets.net/alneenqid6w5/5F1q4U7ZLrgvbJF0rBtEOu/5a41e7c9e34be8e340d7a633ebb983b0/Google_Ads_Menu_4.png)
+![Google_Ads_Menu_4](https://images.ctfassets.net/alneenqid6w5/5F1q4U7ZLrgvbJF0rBtEOu/5a41e7c9e34be8e340d7a633ebb983b0/Google_Ads_Menu_4.png)
 
 Uma vez que o tipo de tag seja selecionada, aparecerão as instruções, bem como o código da tag que você deverá copiar.
 
diff --git a/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md b/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md
index 74dfb7829..df2af4984 100644
--- a/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md
+++ b/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md
@@ -22,8 +22,8 @@ Por padrão, o CMS só exibe as __últimas 20 coleções__ atualizadas.
 
 Portanto, se sua loja tem mais do que 20 coleções, é normal que algumas delas não apareçam na lista exibida no CMS.
 
-![findCollection1](//images.contentful.com/alneenqid6w5/1DM1TNjCKYsY0KQkMgycGm/c49a70d5570d62c993539114d8596549/findCollection1.png)
+![findCollection1](https://images.contentful.com/alneenqid6w5/1DM1TNjCKYsY0KQkMgycGm/c49a70d5570d62c993539114d8596549/findCollection1.png)
 
 Mas você pode buscar qualquer coleção utilizando o __campo de busca__ (Find), incluindo as que não são exibidas por padrão.
 
-![findCollection2](//images.contentful.com/alneenqid6w5/6LBUTpvCH64Uc2CQEwiigk/5739b97f92b27ec9fc40fb4e93ffb2af/findCollection2.png)
+![findCollection2](https://images.contentful.com/alneenqid6w5/6LBUTpvCH64Uc2CQEwiigk/5739b97f92b27ec9fc40fb4e93ffb2af/findCollection2.png)
diff --git a/docs/faq/pt/onde-a-plataforma-vtex-esta-hospedada-e-como-e-a-infra-estrutura.md b/docs/faq/pt/onde-a-plataforma-vtex-esta-hospedada-e-como-e-a-infra-estrutura.md
index a3c0849c7..4f1189850 100644
--- a/docs/faq/pt/onde-a-plataforma-vtex-esta-hospedada-e-como-e-a-infra-estrutura.md
+++ b/docs/faq/pt/onde-a-plataforma-vtex-esta-hospedada-e-como-e-a-infra-estrutura.md
@@ -19,7 +19,7 @@ A arquitetura da plataforma VTEX foi desenvolvida com objetivo de gerar alta esc
 
 Hospedada na Amazon utilizando os serviços AWS (Amazon Web Services), abaixo uma representação da nossa arquitetura e infra-estrutura.
 
-![arquitetura vtex](//images.contentful.com/alneenqid6w5/3QJpGctI7YGEkuoy2cwwoW/a25ee9e8c71cc0d66b198e4da2869510/arquitetura_VTEX.JPG)
+![arquitetura vtex](https://images.contentful.com/alneenqid6w5/3QJpGctI7YGEkuoy2cwwoW/a25ee9e8c71cc0d66b198e4da2869510/arquitetura_VTEX.JPG)
 
 ## Serviços AWS:
 Amazon EC2 (servidor de aplicativo)
diff --git a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
index 9e2c4a816..b24075ebc 100644
--- a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -25,7 +25,7 @@ Quando o ERP consulta e insere este pedido em sua base, é preciso que ele infor
 
 > Para isso, clique no símbolo de seta acima do box **Iniciar manuseio**, conforme indicado no diagrama de fluxo de pedidos abaixo.
 
-![ProntoParaManuseio](//images.contentful.com/alneenqid6w5/5VSeCrxvSogcI46mgkYkm8/84ea107934684ada917d6a8163aeae34/ProntoParaManuseio.png)
+![ProntoParaManuseio](https://images.contentful.com/alneenqid6w5/5VSeCrxvSogcI46mgkYkm8/84ea107934684ada917d6a8163aeae34/ProntoParaManuseio.png)
 
 > É necessário ter um [perfil de acesso com permissão OMS - Full access](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para realizar esta ação.
 
diff --git a/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md b/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md
index 45410eed7..64b8d3c9b 100644
--- a/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md
+++ b/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md
@@ -20,10 +20,10 @@ Esses casos podem acontecer quando alguma informação no pedido gravou com espa
 Abaixo um caso, onde a __UTM do facebook__ postado em algum local da internet levou o cliente para o site contendo um espaço na URL, o browser trata o espaço com um código "enconding" e deixa seguir o processo normal de navegação e compra no site.
 
 print1 - excel:
-![print1-oms](//images.contentful.com/alneenqid6w5/1VCM1e8XOMO88yCiokKGS2/929622ce8f009c1a6fff007f5225ddce/print1-oms.jpg)
+![print1-oms](https://images.contentful.com/alneenqid6w5/1VCM1e8XOMO88yCiokKGS2/929622ce8f009c1a6fff007f5225ddce/print1-oms.jpg)
 
 print2 - API:
-![print2-oms](//images.contentful.com/alneenqid6w5/5uxbAw046W4mQuEQWkoEGe/dbd6b801f6706f5e7d57ba32b4df44f6/print2-oms.JPG)
+![print2-oms](https://images.contentful.com/alneenqid6w5/5uxbAw046W4mQuEQWkoEGe/dbd6b801f6706f5e7d57ba32b4df44f6/print2-oms.JPG)
 
 
 Para situações desse tipo, __não podemos alterar o pedido__ uma vez que foi fechado na loja corretamente pelo cliente. __Deve-se ajustar na origem que está enviando o campo errado para a loja__ e exportar os dados do OMS, desconsiderando esse pedido com campo gravado errado (utilizando a data e hora na url do OMS, para exportar) ou utilizando API do OMS.
diff --git a/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md b/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md
index 68f672231..00298f2f5 100644
--- a/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md
+++ b/docs/faq/pt/some-gateway-affiliations-are-highlighted-in-yellow-why.md
@@ -18,6 +18,6 @@ Ao entrar em **Afiliações de Gateways**, é possível ver a listagem de todas
 
 Isso significa que esta afiliação não está ativa, e sim, está em teste. É possível confirmar essa informação entrando na afiliação destacada. 
 
-![afiliação-gateway-teste pt](//images.ctfassets.net/alneenqid6w5/5fCrLnTamsyKIwY4WaEI4e/1d5e0ef719b52b6b46257032a3d5d521/gateway_teste_pt.png)
+![afiliação-gateway-teste pt](https://images.ctfassets.net/alneenqid6w5/5fCrLnTamsyKIwY4WaEI4e/1d5e0ef719b52b6b46257032a3d5d521/gateway_teste_pt.png)
 
 Ou seja, a cor destaca aquelas configurações que ainda não estão ativas.
diff --git a/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md b/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
index d9353ad82..cddb40882 100644
--- a/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
+++ b/docs/faq/pt/suggestion-module-returns-error-when-trying-to-process-sku-suggestion.md
@@ -22,14 +22,14 @@ Isto acontece quando há algum erro no cadastro do SKU no seller.
 
 Para identificar qual é o erro, siga os passos abaixo:
 1. Entre no módulo __Sugestões__.  
-2. Clique no SKU que o marketplace não aceitou.!![suggestions1](//images.ctfassets.net/alneenqid6w5/4cgijfXaTmcy00Q8G8eISS/fb35d1ecb947bd68b76674902ea30ac8/suggestions1.png)  
+2. Clique no SKU que o marketplace não aceitou.!![suggestions1](https://images.ctfassets.net/alneenqid6w5/4cgijfXaTmcy00Q8G8eISS/fb35d1ecb947bd68b76674902ea30ac8/suggestions1.png)  
 3. Entre no __developer tools__ do browser (para isso, se estiver usando o Google Chrome, aperte `F12` no Windows ou `Command+Option+I` no Mac).   
 4. No developer tools, clique na aba __Network__.  
-5. Ainda no developer tools, clique na opção __All__.!![f12pt](//images.ctfassets.net/alneenqid6w5/29nyZivZywIyM8m4aE6Omu/f595c009eb3e8f7559bee5ebc3444c16/f12pt.png)  
+5. Ainda no developer tools, clique na opção __All__.!![f12pt](https://images.ctfassets.net/alneenqid6w5/29nyZivZywIyM8m4aE6Omu/f595c009eb3e8f7559bee5ebc3444c16/f12pt.png)  
 6. Clique no botão __Aceitar__ do módulo Sugestões.  
 7. Você verá uma lista das chamadas ativadas pelo botão Aceitar.  
-8. Se uma delas estiver em vermelho e com status `400`, como na imagem abaixo, clique nessa chamada.![erroSuggestion3](//images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)  
-9. Você verá em seguida a descrição do erro que ocasionou a falha no processamento da sugestão do SKU.![erroSuggestion4](//images.contentful.com/alneenqid6w5/4yN8mswXdYoKO6wcsyO0eW/2de11f133c3ee911c1e712d7b1188711/erroSuggestion4.png)  
+8. Se uma delas estiver em vermelho e com status `400`, como na imagem abaixo, clique nessa chamada.![erroSuggestion3](https://images.contentful.com/alneenqid6w5/3aObfkI9zqSOaUmGqu8MMU/0532f37ce192de8b36672b7e633ab99c/erroSuggestion3.png)  
+9. Você verá em seguida a descrição do erro que ocasionou a falha no processamento da sugestão do SKU.![erroSuggestion4](https://images.contentful.com/alneenqid6w5/4yN8mswXdYoKO6wcsyO0eW/2de11f133c3ee911c1e712d7b1188711/erroSuggestion4.png)  
 
 Para resolver o problema, o seller deve resolver o erro apontado nessa descrição.
 
diff --git a/docs/faq/pt/understanding-the-dashboard.md b/docs/faq/pt/understanding-the-dashboard.md
index f7e91cc68..c48334258 100644
--- a/docs/faq/pt/understanding-the-dashboard.md
+++ b/docs/faq/pt/understanding-the-dashboard.md
@@ -22,7 +22,7 @@ Para acessar o Dashboard, clique no módulo **License Manager** no menu superior
 
 São 3 gráficos no total. No primeiro deles é possível comparar a média do tempo de carregamento total de sua loja (em vermelho) com a média do tempo de carregamento total de todas as outras lojas da VTEX (em azul). Abaixo, você pode conferir um exemplo desse gráfico.
 
-![](//images.contentful.com/alneenqid6w5/2z4iBEY5UEkqcmsa0KEgoi/3d661f25118a2e876d20a565ebfc88f9/dashboard-chart1-560x320.png)
+![](https://images.contentful.com/alneenqid6w5/2z4iBEY5UEkqcmsa0KEgoi/3d661f25118a2e876d20a565ebfc88f9/dashboard-chart1-560x320.png)
 
 A partir deste gráfico é possível perceber se uma eventual lentidão no sistema está atingindo apenas a sua loja ou todas as lojas da VTEX. Também é possível visualizar se um eventual pico no tempo de carregamento ainda persiste ou foi momentâneo. _É importante destacar_também que _nem todo pico significa necessariamente um problema_, pois é natural que o gráfico reflita o comportamento dos clientes de sua loja, com um maior número de acesso em determinados horários. Com o tempo você se habituará ao comportamento da sua loja e estará mais apito a discernir aquilo que foge do comum.
 
@@ -30,7 +30,7 @@ A partir deste gráfico é possível perceber se uma eventual lentidão no siste
 
 No segundo gráfico você também poderá visualizar o tempo médio de carregamento da sua loja, só que desta vez dividido entre os diferentes fatores que compõem o tempo carregamento de uma página web: o tempo de rede (em azul), o processamento da árvore DOM (em vermelho) e a renderização da página no navegador (amarelo).
 
-![](//images.contentful.com/alneenqid6w5/2DMi5uS3awigGGIAEKCqea/b95fc4689141764c25b5fd506eeaac33/2.jpg)
+![](https://images.contentful.com/alneenqid6w5/2DMi5uS3awigGGIAEKCqea/b95fc4689141764c25b5fd506eeaac33/2.jpg)
 
 Isso permite discernir se um eventual problema de demora no carregamento na página está sendo causado por uma demora na resposta do servidor (NetworkTime), por um script JavaScript (DomProcessing) com erro, ou por uma imagem muito pesada (PageRendering), por exemplo.
 
diff --git a/docs/faq/pt/understanding-vtex-email-capture-system.md b/docs/faq/pt/understanding-vtex-email-capture-system.md
index f9382fa90..b70f6d7d9 100644
--- a/docs/faq/pt/understanding-vtex-email-capture-system.md
+++ b/docs/faq/pt/understanding-vtex-email-capture-system.md
@@ -50,4 +50,4 @@ Para que a função do <a href="https://help.vtex.com/pt/tutorial/acesse-o-carri
 Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
 </div>
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
diff --git a/docs/faq/pt/untitled-entry-2017-06-20-at-05-47-41.md b/docs/faq/pt/untitled-entry-2017-06-20-at-05-47-41.md
index cf3a1d950..589f45831 100644
--- a/docs/faq/pt/untitled-entry-2017-06-20-at-05-47-41.md
+++ b/docs/faq/pt/untitled-entry-2017-06-20-at-05-47-41.md
@@ -22,4 +22,4 @@ Quando um pedido dentro da recorrence falha em ser criado por algum problema rel
 
 Falhas na geração de pedidos recorrentes geram um DO ([VTEX DO](http://help.vtex.com/pt/tutorial/vtex-do "VTEX DO")). Um aviso também é feito quado a recorrência não for gerada por conta de indisponibilidade de itens.
 
-![recorrencia erro vtexdo](//images.contentful.com/alneenqid6w5/5bW2FX0E24yeiEkWKUimsI/44121ea3f5f90edb0991cab05c54f23f/recorrencia_erro_vtexdo.png)
+![recorrencia erro vtexdo](https://images.contentful.com/alneenqid6w5/5bW2FX0E24yeiEkWKUimsI/44121ea3f5f90edb0991cab05c54f23f/recorrencia_erro_vtexdo.png)
diff --git a/docs/faq/pt/untitled-entry-2017-07-03-at-18-55-27.md b/docs/faq/pt/untitled-entry-2017-07-03-at-18-55-27.md
index 40cf04211..fd7f7cec1 100644
--- a/docs/faq/pt/untitled-entry-2017-07-03-at-18-55-27.md
+++ b/docs/faq/pt/untitled-entry-2017-07-03-at-18-55-27.md
@@ -18,6 +18,6 @@ Para quem utiliza o conector __CieloV3__ é possível buscar por pedidos pelos c
 
 Para isso, basta abrir a aba de filtros e ir na seção Outros > Campo Buscado
 
-![filtro nsu e tid](//images.contentful.com/alneenqid6w5/1uXWcfrnn6oYgUcMGSiWCq/6c78582fcdf126706ab592470abf66e3/2017-07-03_16_05_45-Vendas___VTEX_OMS.png)
+![filtro nsu e tid](https://images.contentful.com/alneenqid6w5/1uXWcfrnn6oYgUcMGSiWCq/6c78582fcdf126706ab592470abf66e3/2017-07-03_16_05_45-Vendas___VTEX_OMS.png)
 
 A exportação do OMS também traz as informações de TIS e NSU para pedidos transacionados com o conector CieloV3.
diff --git a/docs/faq/pt/utms.md b/docs/faq/pt/utms.md
index 8a41152fa..82e4212bd 100644
--- a/docs/faq/pt/utms.md
+++ b/docs/faq/pt/utms.md
@@ -24,12 +24,12 @@ Para que as **UTMS** configuradas funcionem corretamente, é necessário que **
 2 - utm\_medium.  
 3 - utm\_campaign.
 
-![UTMs1](//images.ctfassets.net/alneenqid6w5/3rxDnnXLJN8HFAeoDaD7Dz/5ef0ebc8475ef92c049fd998ff0e6f96/UTMs1.png)
+![UTMs1](https://images.ctfassets.net/alneenqid6w5/3rxDnnXLJN8HFAeoDaD7Dz/5ef0ebc8475ef92c049fd998ff0e6f96/UTMs1.png)
 
 Abaixo um exemplo de como o link deve ficar e como aparecerá no **RD Station**: 
 
 **[https://whts.co/marcelows](\"https://whts.co/marcelows\")**utm\_source=**facebook**&utm\_medium=cpc&utm\_campaign=nomecampanhaexemplo&utm\_term=palavrachaveYou
 
-![UTMs2](//images.ctfassets.net/alneenqid6w5/49FZ9GtBTiNiXhNYMla6Hd/b14036e3cbe534ea449dd9b9e7011752/UTMs2.png)
+![UTMs2](https://images.ctfassets.net/alneenqid6w5/49FZ9GtBTiNiXhNYMla6Hd/b14036e3cbe534ea449dd9b9e7011752/UTMs2.png)
 
 Após estar com o link configurado, as origens de leads convertidos nesse link respeitarão as configurações inseridas por você.
diff --git a/docs/faq/pt/website-with-error-how-to-fix-it.md b/docs/faq/pt/website-with-error-how-to-fix-it.md
index e53fb1764..8a109a0e6 100644
--- a/docs/faq/pt/website-with-error-how-to-fix-it.md
+++ b/docs/faq/pt/website-with-error-how-to-fix-it.md
@@ -23,7 +23,7 @@ No entanto, se estiver amarelo, há um erro.
 Veja abaixo o passo a passo para corrigi-lo:
 
 1. Clique no website desejado.
-2. Selecione o Binding (linha selecionada na imagem abaixo), e clique em __Update__.![Binding 1](//images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
+2. Selecione o Binding (linha selecionada na imagem abaixo), e clique em __Update__.![Binding 1](https://images.ctfassets.net/alneenqid6w5/5LR7a32CjuCISemEqiUCcW/ad11100f7da9727f1fccaa3adf16ae39/Binding_1.png)
 3. Na tela que aparecerá em seguida, o campo __Store name from License Manager__ estará em branco. Clique na seta que aparece nesse campo e selecione o nome da sua loja.
-4. Clique em **Save Binding**.![Binding 2](//images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
+4. Clique em **Save Binding**.![Binding 2](https://images.ctfassets.net/alneenqid6w5/27JCHH8IOIgwQY2qaQ0MIU/de9d5bdde8cdfa57a5c08a0ae8291506/Binding_2.png)
 5. Clique em **Websites** novamente para atualizar a página. Pronto! O globo estará azul, o que indica que agora está tudo certo com a associação ao Binding.
diff --git a/docs/faq/pt/what-are-pre-installed-apps.md b/docs/faq/pt/what-are-pre-installed-apps.md
index aef18f0ee..96cbd307f 100644
--- a/docs/faq/pt/what-are-pre-installed-apps.md
+++ b/docs/faq/pt/what-are-pre-installed-apps.md
@@ -18,7 +18,7 @@ Na primeira vez que acessar sua conta pela CLI do VTEX IO, você verá que já e
 
 Elas foram previamente instaladas e são responsáveis por executarem algumas funções básicas.
 
-![appList](//images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
+![appList](https://images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
 
 Por exemplo:
 - __admins-app__: renderiza a página do novo painel administrativo da VTEX.
diff --git a/docs/faq/pt/what-deleting-a-sku-seller-means.md b/docs/faq/pt/what-deleting-a-sku-seller-means.md
index 2af9f51f6..c880d9c76 100644
--- a/docs/faq/pt/what-deleting-a-sku-seller-means.md
+++ b/docs/faq/pt/what-deleting-a-sku-seller-means.md
@@ -14,7 +14,7 @@ locale: pt
 legacySlug: o-que-significa-excluir-um-sku-seller
 ---
 
-![excluir](//images.contentful.com/alneenqid6w5/3H8ijBZBEseoomo0wyMKoi/fea00e532fc957357b8794a1afc278ba/excluir.png)
+![excluir](https://images.contentful.com/alneenqid6w5/3H8ijBZBEseoomo0wyMKoi/fea00e532fc957357b8794a1afc278ba/excluir.png)
 
 Ao excluir o SKU Seller, ele deixa de fazer parte do catálogo do Marketplace. Isso significa que **ele não existirá mais na lista de SKUs**.
 
diff --git a/docs/faq/pt/what-delinking-a-sku-seller-means.md b/docs/faq/pt/what-delinking-a-sku-seller-means.md
index d6d11115a..83c133eaa 100644
--- a/docs/faq/pt/what-delinking-a-sku-seller-means.md
+++ b/docs/faq/pt/what-delinking-a-sku-seller-means.md
@@ -14,7 +14,7 @@ locale: pt
 legacySlug: o-que-significa-desvincular-um-sku-seller
 ---
 
-![desvincular](//images.contentful.com/alneenqid6w5/2fJNaa6xkEC0CwguKWK4o0/f6f8625d2409ff921826ffb913598eaf/desvincular.png)
+![desvincular](https://images.contentful.com/alneenqid6w5/2fJNaa6xkEC0CwguKWK4o0/f6f8625d2409ff921826ffb913598eaf/desvincular.png)
 
 Al desvincular un SKU Seller, éste ****dejará de exhibirse como disponible ** en el Marketplace.
 
diff --git a/docs/faq/pt/what-is-url-mapping-301-redirect.md b/docs/faq/pt/what-is-url-mapping-301-redirect.md
index fcc67330d..08a10ea37 100644
--- a/docs/faq/pt/what-is-url-mapping-301-redirect.md
+++ b/docs/faq/pt/what-is-url-mapping-301-redirect.md
@@ -20,11 +20,11 @@ Todos os mapeamentos cadastrados serão executados no tipo 301. O redirecionamen
 
 Os mapeamentos de URLs são cadastrados no **Gerenciador de Portal**. No módulo **Catalog**, acesse o menu “Configurações" -> "Portal”:
 
-![](//images.contentful.com/alneenqid6w5/2sLb71Ajkg8s4MIOgCymsO/de7f2f3747389d99ee8100d9cf8f1093/mapeamento1.png)
+![](https://images.contentful.com/alneenqid6w5/2sLb71Ajkg8s4MIOgCymsO/de7f2f3747389d99ee8100d9cf8f1093/mapeamento1.png)
 
 No Gerenciador de Portal, acesse **Mapeamento de URLs**:
 
-![](//images.contentful.com/alneenqid6w5/5xi3Mase2skUgcI0cU2e28/8459c10133f623d74d55d7c28075b408/mapeamento2.png)
+![](https://images.contentful.com/alneenqid6w5/5xi3Mase2skUgcI0cU2e28/8459c10133f623d74d55d7c28075b408/mapeamento2.png)
 
 Existem duas formas de adicionar / alterar um Mapeamento de URL:
 1. Manualmente
diff --git a/docs/faq/pt/what-should-i-do-when-there-are-problems-with-a-transaction.md b/docs/faq/pt/what-should-i-do-when-there-are-problems-with-a-transaction.md
index e2e256183..631ac2f11 100644
--- a/docs/faq/pt/what-should-i-do-when-there-are-problems-with-a-transaction.md
+++ b/docs/faq/pt/what-should-i-do-when-there-are-problems-with-a-transaction.md
@@ -25,10 +25,10 @@ Em algumas ocasiões pode ocorrer uma falha de comunicação entre VTEX e o parc
 Casos como esse geram logs ou mantém o pedido em um looping. Uma vez que um comportamento errático seja identificado, o caminho mais rápido é verificar se o status do pedido está igual em ambas plataformas. Como por exemplo, o gateway ter atualizado o status como "Settling", mas posteriormente retornar que o status não está correto para captura, contudo o status estaria correto. Veja o exemplo:
 
 No dia 08 de fevereiro a VTEX recebeu uma notificação do gateway em que há uma mudança de status.
-![2017-04-11-17 28 32-4820587- -VTEX-PCI-Gateway-300x65](//images.contentful.com/alneenqid6w5/7us92BzXFYwyQsUqWQa0sM/9c8e7dc490e5497bf8cfa16e0f7874ce/2017-04-11-17_28_32-4820587-_-VTEX-PCI-Gateway-300x65.png) 
+![2017-04-11-17 28 32-4820587- -VTEX-PCI-Gateway-300x65](https://images.contentful.com/alneenqid6w5/7us92BzXFYwyQsUqWQa0sM/9c8e7dc490e5497bf8cfa16e0f7874ce/2017-04-11-17_28_32-4820587-_-VTEX-PCI-Gateway-300x65.png) 
 
 No dia 03 de abril o gateway retorna erro no status
-![2017-04-11-17 26 40-4820587- -VTEX-PCI-Gateway-300x87](//images.contentful.com/alneenqid6w5/35WTOXDAC4WgS0Ki866SSS/6d7f6ed699ef653d79d709c97320d10c/2017-04-11-17_26_40-4820587-_-VTEX-PCI-Gateway-300x87.png)
+![2017-04-11-17 26 40-4820587- -VTEX-PCI-Gateway-300x87](https://images.contentful.com/alneenqid6w5/35WTOXDAC4WgS0Ki866SSS/6d7f6ed699ef653d79d709c97320d10c/2017-04-11-17_26_40-4820587-_-VTEX-PCI-Gateway-300x87.png)
 
 Um outro exemplo seria o gateway (parceiro) retornar que não possui os dados completos do cartão de crédito para prosseguir com a compra. Contudo, nos detalhes da transação no topo da página é possível confirmar que a informação existe - até porque o pedido não teria sido criado sem essas informações. O caminho aqui seria o mesmo, entrar em contato com o seu gateway.
 
diff --git a/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md b/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md
index 7f90b493e..b1fee4695 100644
--- a/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md
+++ b/docs/faq/pt/what-to-do-when-my-exported-report-does-not-reach-my-email.md
@@ -24,9 +24,9 @@ A seguir, entenda o passo a passo:
 
 1. Acesse o __Master Data__
 2. Clique em __“Exportations”__
-![3WNNUZ8EgDZ4iYv8e0OyQG](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
+![3WNNUZ8EgDZ4iYv8e0OyQG](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/8ebaf7d4ddba8fd8803969c2c98e3c18/3WNNUZ8EgDZ4iYv8e0OyQG.png)
 3. Certifique-se que aba aberta é a de __“Aplicações”__
-![7ecXBGaCeC3hTaO0lODPq1](//images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
+![7ecXBGaCeC3hTaO0lODPq1](https://images.ctfassets.net/alneenqid6w5/rBSEy9DQVSPNEjHLOXjU6/afac5d6a147ad01f1dbb4566bd751510/7ecXBGaCeC3hTaO0lODPq1.png)
 4. Em __“Status de exportações”__, clique no relatório que deseja baixar.
 
 Dessa forma, é possível acessar esse material mesmo que o email original não tenha chegado para o solicitante.
diff --git a/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
index 1029df20a..622936471 100644
--- a/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -16,7 +16,7 @@ legacySlug:
 
 Existe um caso em que, mesmo com o Avise-me [corretamente configurado](/pt/tutorial/configurar-o-avise-me), ele não aparece. É **quando o tipo de exibição da categoria está selecionado como Lista de SKUs**.
 
-![categoria-lista-de-skus PT](//images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
+![categoria-lista-de-skus PT](https://images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
 
 Neste caso, além das configurações padrão, é necessário o uso do controle `vtex.cmc:SkuSelection`, mesmo que não exista mais de um SKU por página.
 
diff --git a/docs/faq/pt/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md b/docs/faq/pt/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
index aaa2b20cb..7c80d8014 100644
--- a/docs/faq/pt/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
+++ b/docs/faq/pt/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
@@ -18,7 +18,7 @@ Um erro comum na aprovação do pagamento, no módulo **Pedidos**, é o de falta
 
 Neste caso, ao tentar aprovar o pagamento em **Pedidos**, você verá um erro parecido com os seguintes:
 
-![error authorize fulfillment](//images.contentful.com/alneenqid6w5/5Wvwem2kucqsOIYKq4WW00/23b0ffb4209565da148382c3299e2bac/error_authorize_fulfillment.png)
+![error authorize fulfillment](https://images.contentful.com/alneenqid6w5/5Wvwem2kucqsOIYKq4WW00/23b0ffb4209565da148382c3299e2bac/error_authorize_fulfillment.png)
 
 Para confirmar se o problema é este, na página de [detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl), clique em `Ver interações` para ver os detalhes do pedido.
 
diff --git a/docs/faq/pt/where-can-i-see-my-mercado-pago-transparente-credentials.md b/docs/faq/pt/where-can-i-see-my-mercado-pago-transparente-credentials.md
index 81cc731b5..f929fd776 100644
--- a/docs/faq/pt/where-can-i-see-my-mercado-pago-transparente-credentials.md
+++ b/docs/faq/pt/where-can-i-see-my-mercado-pago-transparente-credentials.md
@@ -18,8 +18,8 @@ _Parte das configurações documentadas neste artigo é realizada em um ambient
 
 Para ter acesso às suas credenciais do Mercado Pago Transparente, acesse as configurações dessa afiliação, no módulo PCI Gateway, e siga os passos abaixo.
 
-1. Nos dados à direita, abaixo de "Get Credentials", clique em **Consultar**. Este link vai lhe conduzir para a página de autenticação do Mercado Pago.![2017-01-26 19_37_19-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/4hKomsptCEgGWUsyw4e4GM/09fba68bccee98e6c7d13f6ba4112d6a/2017-01-26-19_37_19-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x140.png)
-2. Abaixo de "How to obtain my access\_token", clique em **Credentials**.![2017-01-26 19_43_49-Authentication - MercadoPago Developers](//images.contentful.com/alneenqid6w5/1ZM0tXM4DWk6SEE68ecU4m/0f5802acc942e3ca7ac7d1760754cd43/2017-01-26-19_43_49-Authentication-MercadoPago-Developers-279x300.png)
-3. Na aba **Checkout básico**, você encontrará suas credenciais.![2017-01-26 19_48_02-MercadoPago - Credenciais](//images.contentful.com/alneenqid6w5/6hgEPEEkWkAqY2u80cqeGI/8152d6e0a24defb9986335be54a0e169/2017-01-26-19_48_02-MercadoPago-Credenciais-300x88.png)
+1. Nos dados à direita, abaixo de "Get Credentials", clique em **Consultar**. Este link vai lhe conduzir para a página de autenticação do Mercado Pago.![2017-01-26 19_37_19-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/4hKomsptCEgGWUsyw4e4GM/09fba68bccee98e6c7d13f6ba4112d6a/2017-01-26-19_37_19-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x140.png)
+2. Abaixo de "How to obtain my access\_token", clique em **Credentials**.![2017-01-26 19_43_49-Authentication - MercadoPago Developers](https://images.contentful.com/alneenqid6w5/1ZM0tXM4DWk6SEE68ecU4m/0f5802acc942e3ca7ac7d1760754cd43/2017-01-26-19_43_49-Authentication-MercadoPago-Developers-279x300.png)
+3. Na aba **Checkout básico**, você encontrará suas credenciais.![2017-01-26 19_48_02-MercadoPago - Credenciais](https://images.contentful.com/alneenqid6w5/6hgEPEEkWkAqY2u80cqeGI/8152d6e0a24defb9986335be54a0e169/2017-01-26-19_48_02-MercadoPago-Credenciais-300x88.png)
  
 _As credenciais corretas são o `CLIENT\_ID` e o `CLIENT\_SECRET`. Elas ficam na aba **Checkout básico**, e não em Checkout transparente._
diff --git a/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md b/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md
index a307649b8..61e7c7c5f 100644
--- a/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md
+++ b/docs/faq/pt/why-can-t-i-change-the-fields-in-a-group.md
@@ -28,14 +28,14 @@ Uma vez localizado o campo, prossiga com as instruções a seguir:
 
 1. Acesse o módulo __Catálogo__
 2. Do lado esquerdo da tela, clique em __Categorias__
-![campos1](//images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
+![campos1](https://images.ctfassets.net/alneenqid6w5/5BKcfVdzklTK5ZIdPdjvvS/5a4f032447dadfc8a8e7aa129960c6a3/campos1.PNG)
 3. Vá até o lado direito da página e clique no botão azul __Ações__
 4. Selecione a opção __Campos (Produto)__
-![campos2](//images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
+![campos2](https://images.ctfassets.net/alneenqid6w5/14Ak3SlbVXodLJr17Cd8Nu/00dfd546a9c2297250a1aec6fb74336a/campos2.PNG)
 5. Encontre o __grupo__ em que deseja fazer as modificações
 6. Clique em __Alterar__
-![campos3](//images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
+![campos3](https://images.ctfassets.net/alneenqid6w5/5k3B7j47J6TBfSAyzeNUGS/5bbb39dfcd00093401e71f036efcb3e0/campos3.PNG)
 7. Após fazer as mudanças necessárias, clique em __Salvar__
-![PTgrupo4](//images.ctfassets.net/alneenqid6w5/TwYOgTmuhvs1buHQoWEf4/4b75359b1604b842446960bb64d8f6da/PTgrupo4.png)![ENgrupo4](//images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
+![PTgrupo4](https://images.ctfassets.net/alneenqid6w5/TwYOgTmuhvs1buHQoWEf4/4b75359b1604b842446960bb64d8f6da/PTgrupo4.png)![ENgrupo4](https://images.ctfassets.net/alneenqid6w5/6O7gv1HlM2P2cD0lj6y1Fg/7531c48a52521c1cca9dc4bc2225bd30/ENgrupo4.png)
 
 Pronto, campos alterados! Não se esqueça de salvar as configurações para que as alterações sejam exibidas no front da loja.
diff --git a/docs/faq/pt/why-does-mercado-livre-return-attribution-errors-after-mapping.md b/docs/faq/pt/why-does-mercado-livre-return-attribution-errors-after-mapping.md
index 9e4603b09..ef279ab41 100644
--- a/docs/faq/pt/why-does-mercado-livre-return-attribution-errors-after-mapping.md
+++ b/docs/faq/pt/why-does-mercado-livre-return-attribution-errors-after-mapping.md
@@ -24,13 +24,13 @@ No entanto, esses atributos são bastante claros (Cor principal, Cor secundária
 
 Se algum desses atributos for preenchido incorretamente (por exemplo, se você atribuiu um código referente a Tamanho de cinto para um calçado), o Integrações vai retornar um erro com o seguinte formato:
 
-![Shot1](//images.contentful.com/alneenqid6w5/7A7DwGFr0cw8Q2qek0EqMU/9cad02c847f5dc7be7df68ad14bba39e/Shot1.jpg)
+![Shot1](https://images.contentful.com/alneenqid6w5/7A7DwGFr0cw8Q2qek0EqMU/9cad02c847f5dc7be7df68ad14bba39e/Shot1.jpg)
 
 Neste caso, temos dois exemplos de erros na mesma mensagem.
 
 O primeiro deles indica que o atributo cujo código se inicia com o número `113000` é necessário para a categoria escolhida e não foi inserido na planilha de mapeamento. Veja a planilha abaixo:
 
-![Shot2](//images.contentful.com/alneenqid6w5/4Nue6IMwP6YEKiweMIe0s4/e835e5ab80f6db2b7a13ee4ed6a4f1e4/Shot2.png)
+![Shot2](https://images.contentful.com/alneenqid6w5/4Nue6IMwP6YEKiweMIe0s4/e835e5ab80f6db2b7a13ee4ed6a4f1e4/Shot2.png)
 
 O segundo erro indica que o atributo cujo código se inicia com o número `63000`, inserido na última coluna da planilha acima, é inválido para a categoria escolhida.
 
@@ -40,7 +40,7 @@ Os códigos de cada variação de atributo se iniciam com o mesmo número. Por e
 
 Para identificar o atributo indicado na mensagem de erro, consulte o número inicial dos códigos determinados pelo Mercado Livre. Clique no nome do seu país para fazer o download da planilha de referência:
 
-- [Brasil](//assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
-- [Argentina](//assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
-- [Colômbia](//assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
-- [México](//assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+- [Brasil](https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
+- [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
+- [Colômbia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
+- [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
diff --git a/docs/faq/pt/why-does-my-product-appear-as-unavailable-at-the-store.md b/docs/faq/pt/why-does-my-product-appear-as-unavailable-at-the-store.md
index 2832671be..deaeb472c 100644
--- a/docs/faq/pt/why-does-my-product-appear-as-unavailable-at-the-store.md
+++ b/docs/faq/pt/why-does-my-product-appear-as-unavailable-at-the-store.md
@@ -32,10 +32,10 @@ Quando esse produto não aparece na loja ou quando aparece como indisponível si
 
 O indexed info é um recurso disponível no catálogo que também poderá auxiliar investigações dessa natureza. Quando você precisa identificar de forma rápida, a razão para um SKU estar indisponível, inativo ou invisível, utilize esse recurso.
 
-![IndexedInfo](//images.contentful.com/alneenqid6w5/2lUKVABxNimkqEQiikmKIm/dc0b86cb1b992b70529e221bafceb372/IndexedInfo-1024x636.png)
+![IndexedInfo](https://images.contentful.com/alneenqid6w5/2lUKVABxNimkqEQiikmKIm/dc0b86cb1b992b70529e221bafceb372/IndexedInfo-1024x636.png)
 No exemplo abaixo, é possível concluir que o SKU está indisponível por ausência de preço.
 
-![IndexedInfo_detail](//images.contentful.com/alneenqid6w5/4tSNvER0GIoE8oAKWoiq6W/3b066ab5b55c4441ae883518bfa924ff/IndexedInfo_detail-1024x677.png)
+![IndexedInfo_detail](https://images.contentful.com/alneenqid6w5/4tSNvER0GIoE8oAKWoiq6W/3b066ab5b55c4441ae883518bfa924ff/IndexedInfo_detail-1024x677.png)
 
 ## Logística
 
diff --git a/docs/faq/pt/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md b/docs/faq/pt/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
index 07a895586..e4dd2ca50 100644
--- a/docs/faq/pt/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
+++ b/docs/faq/pt/why-does-the-hostName-in-the-message-center-JSON-display-different-information-from-the-license-manager.md
@@ -18,6 +18,6 @@ O JSON utilizado pela Central de mensagens, ou seja, a fonte das informações q
 
 Ao visualizar a variável `hostName` no JSON da Central de mensagens, pode surgir a dúvida de onde esse dado é carregado. Por mais que o nome da variável seja host, ela carrega o nome - não alterável - do site criado na aba Conta do Gerenciamento da conta.
 
-![VTEX - License Manager](//images.contentful.com/alneenqid6w5/5sZb9Mvw4wcK6oM40CKEak/eee7f0e5848c179c678761a418a978b4/2017-03-22-12_33_29-VTEX-License-Manager.png)
+![VTEX - License Manager](https://images.contentful.com/alneenqid6w5/5sZb9Mvw4wcK6oM40CKEak/eee7f0e5848c179c678761a418a978b4/2017-03-22-12_33_29-VTEX-License-Manager.png)
 
 Ou seja, não será carregado o valor inserido na área de Hosts, e sim, conforme imagem acima, será carregado para o template de e-mail o valor cadastrado em **Nome da Loja**.
diff --git a/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md b/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md
index f0a3bc716..037120b7a 100644
--- a/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md
+++ b/docs/faq/pt/why-doesnt-my-benefit-work-for-a-client-cluster.md
@@ -34,7 +34,7 @@ Certifique-se o valor foi inserido seguindo os seguintes passos:
 4. Vá para a sessão __“Quais as condições para a promoção ser válida?”__
 5. Confira quais Clusters estão cadastradas em __“Cluster de clientes”__
 
-![PT - 7GcSb6BuF6JKnmGAggO3uA ](//images.ctfassets.net/alneenqid6w5/wltgxrSqvTKY5QmcZpK6A/6588a08d631b0bee3b52aa885ca34dda/Cluster-promo-PT.png)
+![PT - 7GcSb6BuF6JKnmGAggO3uA ](https://images.ctfassets.net/alneenqid6w5/wltgxrSqvTKY5QmcZpK6A/6588a08d631b0bee3b52aa885ca34dda/Cluster-promo-PT.png)
 
 6. Insira os __novos dados__
 7. Clique em __Salvar__
diff --git a/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md b/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
index e2be433c0..564b29b4a 100644
--- a/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
+++ b/docs/faq/pt/why-doesnt-my-benefit-work-for-all-types-of-delivery.md
@@ -22,7 +22,7 @@ Para especificar em que tipo de entrega você deseja aplicar a promoção, é pr
 2. Clique no card da promoção à qual você deseja aplicar o frete grátis.
 3. No item 3, ative a flag __Tipo de frete__ e especifique quais devem receber o frete grátis.
 
-![promoções-campo-tipo-frete pt](//images.ctfassets.net/alneenqid6w5/5FX7WnVH3OOaoUGmUAumMO/a3f7f8fec3b78167565da7717e04b137/promo____es-campo-tipo-frete_pt.png)
+![promoções-campo-tipo-frete pt](https://images.ctfassets.net/alneenqid6w5/5FX7WnVH3OOaoUGmUAumMO/a3f7f8fec3b78167565da7717e04b137/promo____es-campo-tipo-frete_pt.png)
 
 Feito isso, os tipos de frete epecificados entrarão na promoção e aparecerão para o cliente com o frete grátis disponível.
 
diff --git a/docs/faq/pt/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md b/docs/faq/pt/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
index c793d2072..47f8adb04 100644
--- a/docs/faq/pt/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
+++ b/docs/faq/pt/why-doesnt-the-payments-finalize-the-cancellation-of-a-transaction.md
@@ -16,6 +16,6 @@ legacySlug: por-que-o-pci-gateway-nao-finaliza-o-cancelamento-da-transacao
 
 Este cenário ocorre quando uma transação permanece indefinidamente no status `Cancelling`, impedindo o cancelamento da transação e, consequentemente, do pedido no OMS. Esta situação ocorre quando a VTEX está aguardando um retorno do sistema do gateway, mas a resposta correta não chega até a VTEX. Podemos ver na imagem abaixo um exemplo de resposta do gateway que não permite a continuidade do processo de cancelamento por parte da VTEX:
 
-![resposta-inadequada-pci-gateway](//images.contentful.com/alneenqid6w5/3P9FblRbzGIEyWo0IW6msa/278ba7912bcbb49a537e94fb7bb4a1b1/resposta-inadequada-pci-gateway.png)
+![resposta-inadequada-pci-gateway](https://images.contentful.com/alneenqid6w5/3P9FblRbzGIEyWo0IW6msa/278ba7912bcbb49a537e94fb7bb4a1b1/resposta-inadequada-pci-gateway.png)
 
 Para solucionar a questão, o lojista deve entrar em contato com o gateway responsável pelo pagamento, informar os dados da transação e solicitar o cancelamento.
diff --git a/docs/faq/pt/why-dont-my-payment-methods-appear-on-the-marketplace.md b/docs/faq/pt/why-dont-my-payment-methods-appear-on-the-marketplace.md
index 76f5543b5..87a7ecfc5 100644
--- a/docs/faq/pt/why-dont-my-payment-methods-appear-on-the-marketplace.md
+++ b/docs/faq/pt/why-dont-my-payment-methods-appear-on-the-marketplace.md
@@ -20,4 +20,4 @@ Ou seja, o pagamento é realizado no marketplace pelas formas de pagamento do ma
 
 Exemplo: Uma compra realizada pelo marketplace CNova irá ser exibida em seu OMS com a seguinte mensagem em __Pagamento__: "Assumed value by affiliate CNova (NVP)", como na imagem abaixo.
 
-![exemplopagamento](//images.contentful.com/alneenqid6w5/54QIARxAYUM4igUYQEieSK/d9f8f1e9e95b8028cce7c6b1e7a89503/exemplopagamento.png)
+![exemplopagamento](https://images.contentful.com/alneenqid6w5/54QIARxAYUM4igUYQEieSK/d9f8f1e9e95b8028cce7c6b1e7a89503/exemplopagamento.png)
diff --git a/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md b/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
index fb6173ae6..d18055455 100644
--- a/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
+++ b/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
@@ -20,7 +20,7 @@ Essa definição da categoria de destino é feita com base no __nome__ e no __pr
 
 No entanto, há casos em que essa definição automática não associa o produto à categoria correta. Para corrigir esse cenário, é preciso fazer a alteração diretamente no painel do Mercado Livre ou seguir o caminho detalhado abaixo:
 
-1. [Baixe esta planilha](//assets.ctfassets.net/alneenqid6w5/oGLLZ7lKFMuKUcmKmIuQk/1bac4c828d4c3a361f70dd8016952796/Recategorizac__a__o_Mercado_Livre.xlsx) e preencha suas respectivas colunas.
+1. [Baixe esta planilha](https://assets.ctfassets.net/alneenqid6w5/oGLLZ7lKFMuKUcmKmIuQk/1bac4c828d4c3a361f70dd8016952796/Recategorizac__a__o_Mercado_Livre.xlsx) e preencha suas respectivas colunas.
 2. __Item ID:__ deve ser preenchido com o ID do seu anúncio no Mercado Livre, tirando o hífen que separa o prefixo do número. <br />
 _`Ex:` o ID pode ser encontrado na URL do anúncio. No link abaixo, por exemplo, o ID seria "MLB875426061"._
 `https://produto.mercadolivre.com.br/MLB-875426061-liquidificador-oster-maximum-dial-vermelho-127v-_JM` 
diff --git a/docs/faq/pt/why-is-let-me-know-not-showing.md b/docs/faq/pt/why-is-let-me-know-not-showing.md
index 922260209..94941a6fe 100644
--- a/docs/faq/pt/why-is-let-me-know-not-showing.md
+++ b/docs/faq/pt/why-is-let-me-know-not-showing.md
@@ -21,7 +21,7 @@ As configurações básicas para a exibição do **Avise-me** quando o produto e
 
 Porém, existe um caso em que, mesmo com os itens acima configurados, o Avise-me não aparece, que é **quando o tipo de exibição da Categoria está selecionado como Lista de SKUs**.
 
-![categoria-lista-de-skus PT](//images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
+![categoria-lista-de-skus PT](https://images.ctfassets.net/alneenqid6w5/bZSp5aNwWsAiSIYU8Oso0/a647479f70fa0e760ff4f3064bbbd421/lista_de_skus.png)
 
 Neste caso, além das configurações padrão, é necessário o uso do controle `vtex.cmc:SkuSelection`, mesmo que não exista mais de um SKU por página.
 Logo, quando a Categoria do produto desejado estiver setada para Lista de SKUs, como na imagem acima, é necessário que seja inserido o controle `vtex.cmc:SkuSelection` no template de página para que o avise-me seja exibido.
diff --git a/docs/faq/pt/why-is-my-freight-value-wrong.md b/docs/faq/pt/why-is-my-freight-value-wrong.md
index 0a79d7509..60c15e7ea 100644
--- a/docs/faq/pt/why-is-my-freight-value-wrong.md
+++ b/docs/faq/pt/why-is-my-freight-value-wrong.md
@@ -23,7 +23,7 @@ O valor de frete é calculado com base em vários fatores: tabela de frete, adic
 3. Aqui, você verificará o valor cadastrado na planilha mais todos os [adicionais](/pt/tutorial/como-funciona-o-adicional-de-frete/) somados a esse valor.
 4. Caso o valor ainda não esteja condizente com o exibido na loja, siga os passos abaixo para verificar se não há nenhuma promoção alterando o valor do frete.
 
-![por-que-meu-valor-de-frete-esta-errado pt](//images.ctfassets.net/alneenqid6w5/4voY55RWlOO8m0wOmciwkk/2663f2b117d2ce1cfffcbc513602937b/por-que-meu-valor-de-frete-esta-errado_pt.jpg)
+![por-que-meu-valor-de-frete-esta-errado pt](https://images.ctfassets.net/alneenqid6w5/4voY55RWlOO8m0wOmciwkk/2663f2b117d2ce1cfffcbc513602937b/por-que-meu-valor-de-frete-esta-errado_pt.jpg)
 
 ### Promoção
 
@@ -32,4 +32,4 @@ O valor de frete é calculado com base em vários fatores: tabela de frete, adic
 3. Observe a box **Valor Total**.
 4. Verifique se, entre as promoções, existe alguma com desconto em frete. Para verificar, basta você acessar a promoção do pedido e verificar o tipo de desconto.
 
-![valortotal pt](//images.ctfassets.net/alneenqid6w5/HTsaBSleouCOQKO0g0AEO/eac925ecef4c78b1fc41c22c8127dce1/valortotal_pt.jpg)
+![valortotal pt](https://images.ctfassets.net/alneenqid6w5/HTsaBSleouCOQKO0g0AEO/eac925ecef4c78b1fc41c22c8127dce1/valortotal_pt.jpg)
diff --git a/docs/faq/pt/why-is-my-product-appearing-in-the-wrong-category.md b/docs/faq/pt/why-is-my-product-appearing-in-the-wrong-category.md
index c8cbbede4..577d241b9 100644
--- a/docs/faq/pt/why-is-my-product-appearing-in-the-wrong-category.md
+++ b/docs/faq/pt/why-is-my-product-appearing-in-the-wrong-category.md
@@ -22,7 +22,7 @@ O primeiro passo é fazer um request GET na rota [Get Product by Id da Catalog A
 
 A resposta desta chamada traz as informações de `DepartmentId` e `CategoryId`, como vemos na imagem abaixo:
 
-![department-id-category-id](//images.contentful.com/alneenqid6w5/1wJqRKDEcYkGqqsMAGy0aA/bf3521922d99fe678031a1898326b1ea/department-id-category-id.png)
+![department-id-category-id](https://images.contentful.com/alneenqid6w5/1wJqRKDEcYkGqqsMAGy0aA/bf3521922d99fe678031a1898326b1ea/department-id-category-id.png)
 
 Depois, você deve comparar esta resposta com os Ids exibidos em sua árvore de categoria. Para acessar sua árvore de categorias, siga os passos a seguir:
 
diff --git a/docs/faq/pt/why-is-my-stores-zoom-not-working.md b/docs/faq/pt/why-is-my-stores-zoom-not-working.md
index 43b42c859..0cb260c38 100644
--- a/docs/faq/pt/why-is-my-stores-zoom-not-working.md
+++ b/docs/faq/pt/why-is-my-stores-zoom-not-working.md
@@ -25,7 +25,7 @@ Para configurar este tamanho de imagem, siga estes passos:
 2. Clique em __Configurações__.
 3. Acesse a aba __Tipos de Arquivo__.
 
-![Tipos de Arquivo PT](//images.ctfassets.net/alneenqid6w5/6Bc1z4n3tSqwYIa40YwKC2/ae8cac2252ac614d548bf2fbb1831401/Tipos_de_Arquivo_PT.png)
+![Tipos de Arquivo PT](https://images.ctfassets.net/alneenqid6w5/6Bc1z4n3tSqwYIa40YwKC2/ae8cac2252ac614d548bf2fbb1831401/Tipos_de_Arquivo_PT.png)
 
 O tamanho 1000x1000 significa que o zoom resultante mostrará a imagem nesse tamanho. Logo, este é o tamanho mínimo para o zoom funcionar.
 
diff --git a/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md b/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
index 09a323bda..7510b5e9d 100644
--- a/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
@@ -42,7 +42,7 @@ Recomendamos iniciar a investigação pelo **Catálogo**. Para verificar as conf
 1. Acesse o Admin VTEX e navegue até **Produtos > Catálogo > Produtos e SKUs** para verificar os produtos cadastrados na sua loja.
 2. Encontre na listagem o produto que você pretende exibir, conforme ilustrado a seguir.
 
-    ![01-produto-pt](//images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/89bf951c58bd80765de8bfb480fd73df/01-produto-pt.png)
+    ![01-produto-pt](https://images.ctfassets.net/alneenqid6w5/75SkVRup4MW0URypUVayEh/89bf951c58bd80765de8bfb480fd73df/01-produto-pt.png)
 
 3. Siga as instruções descritas nas próximas seções para verificar as seguintes informações:
    - [Produto](#produto)
@@ -85,16 +85,16 @@ Na página de SKUs, em **Produtos > Catálogo > Produtos e SKUs**, siga as instr
 
     |Botão | Descrição |
     |-|-|
-    | ![04-botao-precos](//images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acessar a **Lista de preços** para verificar se existe um preço válido para a política comercial desejada associado aos SKUs do produto. Confira a seção de [Preços](#precos) para mais informações.|
-    | ![05-botao-logistica](//images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acessar a página **Gerenciar inventário** para verificar se o SKU está disponível em estoque. Confira a seção de [Logística](#logistica) para mais informações. |
-    | ![06-botao-indexed-info](//images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite visualizar cada **Seller **que comercializa o SKU, a política comercial (**Policy**), o preço (**Value**) e a quantidade do SKU em estoque (**Quantity**). |
+    | ![04-botao-precos](https://images.ctfassets.net/alneenqid6w5/7f0NyYsrdO9dRgW2OQb0ND/1343af5f40a6f0a64cdd8378385977c0/04-botao-precos.png) | Permite acessar a **Lista de preços** para verificar se existe um preço válido para a política comercial desejada associado aos SKUs do produto. Confira a seção de [Preços](#precos) para mais informações.|
+    | ![05-botao-logistica](https://images.ctfassets.net/alneenqid6w5/4Y2GdsvjxHYkVSBfElhVr9/17742a7ce2632fa9d800d942bb016283/05-botao-logistica.png) | Permite acessar a página **Gerenciar inventário** para verificar se o SKU está disponível em estoque. Confira a seção de [Logística](#logistica) para mais informações. |
+    | ![06-botao-indexed-info](https://images.ctfassets.net/alneenqid6w5/5G3dZgdVZDiPqADnodmHc7/e31e69a2333d82a74ca980303e93b690/06-botao-indexed-info.png) | Permite visualizar cada **Seller **que comercializa o SKU, a política comercial (**Policy**), o preço (**Value**) e a quantidade do SKU em estoque (**Quantity**). |
 
 2. Na linha do produto que corresponde ao SKU a ser verificado, clique na seta para baixo <i class="fas fa-caret-down"></i>, ao lado do botão `Alterar`.
 3. Clique na opção **Sku** para acessar a lista detalhada de SKUs.
 4. Na coluna **Status**, verifique se a situação indicada é `Ativa`. Se os SKUs estiverem ativos, prossiga para o passo 7.
 5. Caso algum SKU esteja com situação `Inativa`, clique em `Alterar` para visualizar as informações detalhadas do SKU.
 
-    ![07-catalogo-skus-pt](//images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/a1f33a9ce222d960b565f61d47dc1230/07-catalogo-skus-pt.png)
+    ![07-catalogo-skus-pt](https://images.ctfassets.net/alneenqid6w5/6hs2pWjN8Mze7A274XRAm3/a1f33a9ce222d960b565f61d47dc1230/07-catalogo-skus-pt.png)
 
 6. Na página de informações do SKU, prossiga para a verificação dos itens listados a seguir:
     * **Ativar o SKU se possível:** verifique se esta opção está marcada. Caso contrário, o SKU não será exibido. Ativar esta opção significa determinar que o SKU será ativado se cumprir os requisitos necessários:
@@ -109,7 +109,7 @@ Na página de SKUs, em **Produtos > Catálogo > Produtos e SKUs**, siga as instr
 
 <img class="db center mv9 shadow-4 pointer" src="https://images.ctfassets.net/alneenqid6w5/3StXGBCMW8ZExshcEhfF9m/71839095433fdf925be4cbe97710fb7c/08-aba-imagens-pt.png" alt="08-aba-imagens-pt" style="margin-bottom: 20px;"> <figcaption align = "center"><em>Aba <strong>Imagens</strong></em></figcaption></figure>
 
-![09-sku-imagens-pt](//images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/ef6a125c561d518d683a942b15b3bf58/09-sku-imagens-pt.png)
+![09-sku-imagens-pt](https://images.ctfassets.net/alneenqid6w5/1JJflflW0ACgVn05sRv29x/ef6a125c561d518d683a942b15b3bf58/09-sku-imagens-pt.png)
 
 ### Indexed Info
 
@@ -123,13 +123,13 @@ O registro de indexação apresenta o status de cada SKU do produto. Caso exista
 
 No exemplo abaixo, é possível concluir que o SKU está indisponível por causa da ausência de itens em estoque:
 
-![10-indexed-info-code](//images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/6c4b52fbcf0abaf0f53e3b49ca224e15/Group_1__7_.png)
+![10-indexed-info-code](https://images.ctfassets.net/alneenqid6w5/3J8ZK4CikAYOwYh8GAzbWa/6c4b52fbcf0abaf0f53e3b49ca224e15/Group_1__7_.png)
 
 A partir disso, é possível tomar ações para corrigir o problema. No caso do exemplo, seria necessário ajustar a quantidade de itens em estoque no sistema de [Logística](#logistica).
 
 Um SKU ativo e sem erros terá o registro no indexador similar ao ilustrado a seguir:
 
-![11-indexed-info-code-active](//images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/a5c498ba9733244ba7d9c85cd02d801c/11-indexed-info-code-active.png)
+![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/a5c498ba9733244ba7d9c85cd02d801c/11-indexed-info-code-active.png)
 
 <div class="alert alert-info">
 <p>Se as informações de indexação não apontarem nenhum motivo para a indisponibilidade dos produtos e se você não tiver encontrado nenhum erro no cadastro dos produtos e dos SKUs, é possível que reindexar o produto resolva o problema.</p>
@@ -147,7 +147,7 @@ No módulo de **Preços**, é importante verificar se os SKUs do seu produto con
 
 No exemplo ilustrado a seguir, há três SKUs sem preço base cadastrado. Por isso, não há preço computado na coluna da política comercial – aparece apenas a informação _Preço não cadastrado_.
 
-![12-precos-pt](//images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/13794723132a95851a9810320575adcf/12-precos-pt.png)
+![12-precos-pt](https://images.ctfassets.net/alneenqid6w5/3XrEvLWMmU3LlsxF75v9NN/13794723132a95851a9810320575adcf/12-precos-pt.png)
 
 ### Criar preço base
 
@@ -175,7 +175,7 @@ O **Simulador de envio** serve para verificar se o item existe em estoque e se s
 2. Preencha as informações necessárias, descritas em [Simulador de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete).
 3. Clique em `Simular frete`.
 
-![13-simular-frete-pt](//images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/4acf4052c5e41e259ef8374afae39472/13-simular-frete-pt.png)
+![13-simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/4acf4052c5e41e259ef8374afae39472/13-simular-frete-pt.png)
 
 <div class="alert alert-info">
 <p>Para investigar um item específico, você deve realizar essa simulação com um <strong>Código postal</strong> atendido por todas as <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Políticas de envio</a> cadastradas, pois saberá que, se o item não estiver disponível para esse CEP, não estará disponível para nenhum outro.</p>
@@ -183,7 +183,7 @@ O **Simulador de envio** serve para verificar se o item existe em estoque e se s
 
 O resultado obtido indica se o produto está disponível ou não para entrega no endereço informado e quais são as melhores opções de frete. Exemplo: caso não existam itens suficientes disponíveis em estoque, o simulador apresenta a seguinte mensagem:
 
-![14-simulador-motivos-pt](//images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/36096b0e89ac6a6aa7236200be70fb59/14-simulador-motivos-pt.png)
+![14-simulador-motivos-pt](https://images.ctfassets.net/alneenqid6w5/4oVBH9r7Vs3jDWZF2MUqdO/36096b0e89ac6a6aa7236200be70fb59/14-simulador-motivos-pt.png)
 
 Para mais informações sobre como utilizar o simulador, leia o tutorial [Simulador de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete).
 
@@ -204,7 +204,7 @@ Caso um produto não esteja disponível no site por falta de itens em estoque, v
 3. Para atualizar a contagem de estoque, escreva a quantidade atual na coluna **Atualizar contagem** na linha do SKU desejado, conforme ilustrado a seguir.
 4. Clique em `Salvar`.
 
-![15-gerenciar-inventario-pt](//images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/3f5d9cfcb6029899be80ba3b2a1d3c7e/15-gerenciar-inventario-pt.gif)
+![15-gerenciar-inventario-pt](https://images.ctfassets.net/alneenqid6w5/7gcnOqUFhzOrvf0EPJTTeM/3f5d9cfcb6029899be80ba3b2a1d3c7e/15-gerenciar-inventario-pt.gif)
 
 Para mais informações, leia o tutorial [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
@@ -249,7 +249,7 @@ Siga os passos abaixo para verificar o template que a sua página está utilizan
 
     No exemplo abaixo, o template padrão utilizado é `vtex.curbside-pickup@0.x:store.curbside-pickup` e não há template condicional.
 
-    ![16-templates-cms-pt](//images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/eb5a2372a8a1dd70d98b8d32676fd710/16-templates-cms-pt.png)
+    ![16-templates-cms-pt](https://images.ctfassets.net/alneenqid6w5/5EMFVK2j0O7l6im1ZJIQQI/eb5a2372a8a1dd70d98b8d32676fd710/16-templates-cms-pt.png)
 
 4. Em seguida, é necessário conferir os blocos declarados no template utilizado, conforme descrito em [Templates](#templates).
 
diff --git a/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
index d55632506..19868a985 100644
--- a/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
@@ -24,7 +24,7 @@ Para realizar esta configuração:
 3. Clique em **Alterar** na linha `Produto - Thumb`.
 4. No painel exibido é possível escolher o tamanho máximo de arquivo para as miniaturas no campo **Tamanho Máximo em KB**.
 
-![Configuração de tipo de arquivo no CMS](//images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/b7aed6fe9d4892aba36b6695c22fbfb5/PT.PNG)
+![Configuração de tipo de arquivo no CMS](https://images.ctfassets.net/alneenqid6w5/6aprfJCiiT9y05IAsRvwH/b7aed6fe9d4892aba36b6695c22fbfb5/PT.PNG)
 
 Recomendamos também a leitura do artigo [Melhorar a performance de imagens de produtos](https://help.vtex.com/pt/tutorial/improving-the-performance-of-product-images/) para aprender como melhorar a qualidade de qualquer imagem da loja evitando ao máximo o prejuízo de performance de carregamento da página.
 
diff --git a/docs/faq/pt/why-isnt-the-order-invoiced-on-the-marketplace.md b/docs/faq/pt/why-isnt-the-order-invoiced-on-the-marketplace.md
index 73b080027..5b86b9ba5 100644
--- a/docs/faq/pt/why-isnt-the-order-invoiced-on-the-marketplace.md
+++ b/docs/faq/pt/why-isnt-the-order-invoiced-on-the-marketplace.md
@@ -30,7 +30,7 @@ O impacto disto é que conseguimos ir até o status faturado apenas na VTEX, sen
 
 A Chave de Acesso da Nota Fiscal é um instrumento auxiliar para consulta da NF-e que permite ao detentor desse documento confirmar a sua efetiva existência, nome do campo Invoice Key:
 
-[]![ChaveDeAcesso](//images.contentful.com/alneenqid6w5/447ljGvDxuW0mmQoAumGOg/f1f246378401f4c9a56655974300ab04/ChaveDeAcesso-1.png)
+[]![ChaveDeAcesso](https://images.contentful.com/alneenqid6w5/447ljGvDxuW0mmQoAumGOg/f1f246378401f4c9a56655974300ab04/ChaveDeAcesso-1.png)
 
 **Lembre-se!** Este dado é criado na geração da Nota Fiscal e comporta ao ERP. Caso tenha um, solicite-o.
 
diff --git a/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md b/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
index 507ba6a62..06be6f523 100644
--- a/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
+++ b/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
@@ -32,4 +32,4 @@ Para acessar essa tela, siga os passos abaixo:
 
 A flag Filtro fica na tela de configuração do campo de produto.
 
-![Filtro Campo de produto](//images.contentful.com/alneenqid6w5/3XSX1nXvjW8kuCi20GaueM/d81f6eea3d6d53c78e00b3e367cbf99b/Filtro_Campo_de_produto.png)
+![Filtro Campo de produto](https://images.contentful.com/alneenqid6w5/3XSX1nXvjW8kuCi20GaueM/d81f6eea3d6d53c78e00b3e367cbf99b/Filtro_Campo_de_produto.png)
diff --git a/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 1ecef55c3..2b80665ee 100644
--- a/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/faq/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -21,7 +21,7 @@ Siga os passos abaixo para validar as informações:
 1. Acesse o admin da sua loja: `https://{AccountName}.myvtex.com/admin`.
 2. No menu lateral do admin, clique em __Master Data__.
 3. Na caixa __Profile System__, clique em __Clientes__.
-4. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+4. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 5. Clique no registro do cliente para acessar os detalhes do perfil.
 
 Na seção __Contato__, você verá que a opção `É Empresa?` está preenchida com o valor `Não`. Ao mesmo tempo, na seção __Dados da empresa__, você verá que o campo `Tipo documento` está preenchido com o valor `cnpj`. 
diff --git a/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md b/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md
index 0cf9e6b59..207edd7a5 100644
--- a/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md
+++ b/docs/faq/pt/why-was-the-item-splitted-in-the-cart.md
@@ -18,7 +18,7 @@ Esse cenário acontece quando mais de um item do mesmo SKU é separado em mais d
 
 Porém, existem cenários em que o valor do desconto é indivisível pelo número de itens, principalmente em casos em que o SKU possui uma unidade multiplicadora e, por isso, é preciso dar descontos diferentes para itens de um mesmo SKU para que o valor do desconto fique correto. O que acaba por deixar os preços diferentes e separando cada unidade em uma linha. Visualize melhor essa explicação com exemplo abaixo:
 
-![Por_que_o_item_do_carrinho_foi_separado](//images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/9f522427584df5bf97156641a1ac2bb3/Por_que_o_item_do_carrinho_foi_separado.jpg)
+![Por_que_o_item_do_carrinho_foi_separado](https://images.ctfassets.net/alneenqid6w5/5XCSjyHOKsKI4GaQqYMUcs/9f522427584df5bf97156641a1ac2bb3/Por_que_o_item_do_carrinho_foi_separado.jpg)
 
 1. Unidade multiplicadora.
 2. Preço do produto após o desconto.
diff --git a/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 3750338ad..261a1e246 100644
--- a/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -18,7 +18,7 @@ Existe uma regra de segurança no Checkout que está relacionada à facilidade d
 
 Como o SmartCheckout permite fechar uma compra apenas com o e-mail e com o CVV do cartão, caso o cliente já tenha finalizado compra anteriormente, limitamos a quantidade de tentativas de finalização de compra sem sucesso a 3. Depois dessas 3 tentativas, pedimos o login do cliente.
 
-![LoginPT](//images.ctfassets.net/alneenqid6w5/6M66QYzmnYoaAieMEkgeQU/ad36bed2e62bedaa2fb6ca5e9efe67c0/LoginPT.png)
+![LoginPT](https://images.ctfassets.net/alneenqid6w5/6M66QYzmnYoaAieMEkgeQU/ad36bed2e62bedaa2fb6ca5e9efe67c0/LoginPT.png)
 
 Ou seja, caso o cliente finalize a compra apenas com o e-mail e o CVV do cartão de crédito e a autorização da operadora não ocorra em até 3 vezes seguidas, é mostrada a tela de login para que o cliente continue tentando comprar. Essa contagem volta ao início quando o cliente fizer o login e finalizar sua compra com sucesso.
 
diff --git a/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md b/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md
index 4f8da5a4b..c2f4c5d4c 100644
--- a/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md
+++ b/docs/faq/pt/why-wasnt-the-promotion-applied-to-the-marketplace.md
@@ -16,7 +16,7 @@ legacySlug: por-que-a-promocao-nao-foi-aplicada-no-marketplace
 
 Para criar uma promoção para marketplaces, o cenário é quase o mesmo de uma promoção comum, porém, deve-se selecionar no campo **política comercial** o valor **Loja(s) de terceiro(s)** e selecionar a **política comercial** usada pelo marketplace ou preencher o campo **afiliado** com o ID do marketplace.
 
-![marketplace.pt](//images.ctfassets.net/alneenqid6w5/2WLaENr8b1szg1iBnTS3e9/6f7a2d4e07cc7b0da7173519212e19e4/marketplace.pt.png)
+![marketplace.pt](https://images.ctfassets.net/alneenqid6w5/2WLaENr8b1szg1iBnTS3e9/6f7a2d4e07cc7b0da7173519212e19e4/marketplace.pt.png)
 
 Para saber mais detalhes de como fazê-lo, verifique nosso [artigo sobre como criar promoção para marketplace](/pt/tutorial/configurando-promocao-para-marketplace/).
 
diff --git a/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
index daa2bfda7..6f37ddca1 100644
--- a/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
@@ -31,5 +31,5 @@ Create a new dictionary in the CMS Module that has no previously registered Host
 
 In the CMS module, click on the magnifying glass and then on the "Clear" button to unlock the "Add" new host button.
 
-![PT - Criar dicionário não disponibiliza opção de "Add"](//images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
+![PT - Criar dicionário não disponibiliza opção de "Add"](https://images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
 
diff --git a/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index 52dda1b74..a2cb2e61c 100644
--- a/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -30,7 +30,7 @@ This was because the number `1` had been set as the default, even when there was
 
 Log in to your **VTEX Admin > Home > How to improve > Catalog**. If the section indicates that `1` issue was found, by clicking on `Popular products without stock` you will be redirected to the Catalog page.
 
-![Como melhorar EN](//images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/956eb8af39b7edff3928a4acb13ba700/Como_melhorar_EN.png)
+![Como melhorar EN](https://images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/956eb8af39b7edff3928a4acb13ba700/Como_melhorar_EN.png)
 
 
 ## Workaround
@@ -39,5 +39,5 @@ No action is required from the user as we have already fixed the issue. When no
 
 `We didn't find any issues in your catalog`
 
-![Como melhorar fixed EN](//images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/4251750222051f48f073536c305e0f10/Como_melhorar_fixed_EN.png)
+![Como melhorar fixed EN](https://images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/4251750222051f48f073536c305e0f10/Como_melhorar_fixed_EN.png)
 
diff --git a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index e7c172260..d8a71f481 100644
--- a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Summary
 
-The automatic field works correctly when set to recalculate itself when there is a new entry.  It stops working however, when set to one of the "first hour" options. ![inline1511102536](//images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
+The automatic field works correctly when set to recalculate itself when there is a new entry.  It stops working however, when set to one of the "first hour" options. ![inline1511102536](https://images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
index 5faedfba8..2c789e362 100644
--- a/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
@@ -30,7 +30,7 @@ The only thing necessary is a valid tracking code for each order. On the followi
 
 It's possible to send tracking updates via API, with emails continuing to be sent. The same is true for the delivery confirmation, which can also be done on the OMS interface.
 
-![2017-08-16 195850](//images.contentful.com/alneenqid6w5/1IPsGBnkKYggY8m6smeqOA/a2a95afc6fb34e7bfe89c1cab2fdb612/2017-08-16_195850.jpg)
+![2017-08-16 195850](https://images.contentful.com/alneenqid6w5/1IPsGBnkKYggY8m6smeqOA/a2a95afc6fb34e7bfe89c1cab2fdb612/2017-08-16_195850.jpg)
 
 Delivery confirmation via OMS is also passed on to the marketplaces.
 
diff --git a/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md b/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md
index 54395bbae..38c7024e5 100644
--- a/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md
+++ b/docs/known-issues/en/cms-is-not-accessible-through-the-new-admin.md
@@ -20,7 +20,7 @@ internalReference:
 
 When accessing the CMS through the new administrative environment (My VTEX - `{AccountName}.myvtex.com/admin`), an error page is displayed, and the CMS can not be accessed.
 
-![4JSc1cw](//images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
+![4JSc1cw](https://images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/creating-or-editing-list-type-does-not-work.md b/docs/known-issues/en/creating-or-editing-list-type-does-not-work.md
index 82a940b36..0d533a1a5 100644
--- a/docs/known-issues/en/creating-or-editing-list-type-does-not-work.md
+++ b/docs/known-issues/en/creating-or-editing-list-type-does-not-work.md
@@ -20,7 +20,7 @@ internalReference:
 
 On the List Types screen, when clicking on "See details" or "New List Type", it's not possible to create or change the List Type.
 
-![List Type Creation](//images.contentful.com/alneenqid6w5/3dmnyQDRyMc8guqw8m8EOc/b6192d84ade5e8990990d170ac4614d2/1.png)
+![List Type Creation](https://images.contentful.com/alneenqid6w5/3dmnyQDRyMc8guqw8m8EOc/b6192d84ade5e8990990d170ac4614d2/1.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/crm-error-when-searching-with-spaces.md b/docs/known-issues/en/crm-error-when-searching-with-spaces.md
index dcee68f4d..54c5c30fe 100644
--- a/docs/known-issues/en/crm-error-when-searching-with-spaces.md
+++ b/docs/known-issues/en/crm-error-when-searching-with-spaces.md
@@ -20,7 +20,7 @@ internalReference:
 
 User receives a generic error message when using the CRM's search bar to filter documents containing attributes with spaces. Example:Searching for a city called "Rio de Janeiro" will yield an error message
 
-[Screen Shot 2018-12-26 at 14.38.55](//images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
+[Screen Shot 2018-12-26 at 14.38.55](https://images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
 
 ## Simulation
 
@@ -31,6 +31,6 @@ User receives a generic error message when using the CRM's search bar to filter
 
 ## Workaround
 
-![Screen Shot 2018-12-26 at 14.40.03](//images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
+![Screen Shot 2018-12-26 at 14.40.03](https://images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
 Fortunately there is a simple workaround that does not require the use of an API.  By clicking on the "Todos"("All") dropdown next to the search bar, the same search can be made successfully without an error message.
 
diff --git a/docs/known-issues/en/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md b/docs/known-issues/en/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
index 06f42a406..d7b5440c6 100644
--- a/docs/known-issues/en/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
+++ b/docs/known-issues/en/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
@@ -20,7 +20,7 @@ internalReference:
 
 When performing a GiftCard query in the Admin by ID (document), the customer's voucher is not listed.
 
-![vale](//images.contentful.com/alneenqid6w5/78Mt2DDgaIwg2I66gSYGgM/66de95f8e3b3b73d20a0165f4da67f88/vale.png)
+![vale](https://images.contentful.com/alneenqid6w5/78Mt2DDgaIwg2I66gSYGgM/66de95f8e3b3b73d20a0165f4da67f88/vale.png)
 
 ## Simulation
 
@@ -41,5 +41,5 @@ To query an ID with no dots or hyphens (created using the API), follow these ste
 2. Remove the dots and the hyphen;
 3. Click "Search".
 
-![vale animado](//images.contentful.com/alneenqid6w5/p5ybSG51tYmIe2qCu2GGg/2c68720ce41c517630b7049c49daf3f9/vale.gif)
+![vale animado](https://images.contentful.com/alneenqid6w5/p5ybSG51tYmIe2qCu2GGg/2c68720ce41c517630b7049c49daf3f9/vale.gif)
 
diff --git a/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md b/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md
index 96c43c14f..dfe08aff1 100644
--- a/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md
+++ b/docs/known-issues/en/divergence-between-total-order-value-and-total-products-value.md
@@ -26,7 +26,7 @@ The order is closed and normally transacted at VTEX. But, depending on the exter
 
 Example of occurrence:
 
-![image](//images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
 
 In this case, the total value of the order charged to the customer was `R$ 7.98`. However, when adding the sales figures recorded in each product, the total would be `R$ 7.95`.
 
diff --git a/docs/known-issues/en/encoding-error-in-apple-mail-app.md b/docs/known-issues/en/encoding-error-in-apple-mail-app.md
index dabc78a7e..3dfba0339 100644
--- a/docs/known-issues/en/encoding-error-in-apple-mail-app.md
+++ b/docs/known-issues/en/encoding-error-in-apple-mail-app.md
@@ -29,7 +29,7 @@ Mount an email sending trigger that has a special character in the "Subject" of
 
 Result:
 
-![png](//images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
+![png](https://images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md b/docs/known-issues/en/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md
index f688621bd..0552bb793 100644
--- a/docs/known-issues/en/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md
+++ b/docs/known-issues/en/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md
@@ -20,7 +20,7 @@ internalReference:
 
 When applying a filter by specification (side menu) with special character, the system returns a white screen with the following error 400: "Bad Request! Scripts are not allowed!"
 
-![Filtro com erro 400](//images.contentful.com/alneenqid6w5/zFVBtySVCoYSoCqEQioOw/b0ac0afcad2eb753d0c02cf14850e087/erro_400.png)
+![Filtro com erro 400](https://images.contentful.com/alneenqid6w5/zFVBtySVCoYSoCqEQioOw/b0ac0afcad2eb753d0c02cf14850e087/erro_400.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md b/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
index 3db5a8a4b..abc34ab47 100644
--- a/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
+++ b/docs/known-issues/en/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
@@ -22,7 +22,7 @@ VTEX stores can become each other's [sellers](https://help.vtex.com/en/tutorial/
 
 This is because products that are sold by both the marketplace and its sellers are not recognized by the system when they are sent. It is only possible to send products that are sold by only one of the stores.
 
-![arquitetura circular](//images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/9e024cb7fedda9e1c4fda6566c598be2/arquitetura_circular.JPG)
+![arquitetura circular](https://images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/9e024cb7fedda9e1c4fda6566c598be2/arquitetura_circular.JPG)
 
 
 ## Simulation
diff --git a/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
index 9c960e92e..565eabfaa 100644
--- a/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
@@ -29,7 +29,7 @@ The error authorization message can change from `node`to `react` according to th
 1.  Install the VTEX CLI (Toolbelt)
 2.  Navigate towards the app's directory
 3.  Execute the "vtex-link" command through the terminal.
-4.  ![image (8)](//images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
+4.  ![image (8)](https://images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md b/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md
index aa51dc1f9..9a2a08dec 100644
--- a/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md
+++ b/docs/known-issues/en/geolocation-search-for-pickup-points-loading-indefinitely.md
@@ -34,7 +34,7 @@ After making sure your browser meets the said condition, follow the steps below:
 5. At checkout, select the **pickup point** delivery option. 
 6. Note that the page is stuck on loading, displaying the message "Awaiting permission to get your current location".
 
-![erro EN](//images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/22bc5539ee83ef63668f4ad01c7e0933/erro_EN.png)
+![erro EN](https://images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/22bc5539ee83ef63668f4ad01c7e0933/erro_EN.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md b/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
index af63f0f64..0d04cb697 100644
--- a/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
+++ b/docs/known-issues/en/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
@@ -28,7 +28,7 @@ In products with assembly options customization, a parent item has components, w
 3. Select the child item of the product, in the same quantity;
 4. Check the items in the cart.
 
-![KI assembly](//images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/2296bfc12736ff882e99f2bf70645470/KI_assembly.png)
+![KI assembly](https://images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/2296bfc12736ff882e99f2bf70645470/KI_assembly.png)
 
 Notice that the cart contains one more unit of the child item relative to the parent item.
 
diff --git a/docs/known-issues/en/incorrect-canonical-tag-on-https-pages.md b/docs/known-issues/en/incorrect-canonical-tag-on-https-pages.md
index 1eab0bb23..9db47b76f 100644
--- a/docs/known-issues/en/incorrect-canonical-tag-on-https-pages.md
+++ b/docs/known-issues/en/incorrect-canonical-tag-on-https-pages.md
@@ -25,7 +25,7 @@ Upon activating a specific HTTPS folder, the _canonical_ HTML tag continues to r
 1. Activate HTTPS in a single folder of the site ([guide](https://help.vtex.com/tutorial/--frequentlyAskedQuestions_4378));
 2. Check the _canonical_ tag in the rendered HTML.
 
-![image](//images.contentful.com/alneenqid6w5/5B2i3p2lva8OO0I4geI8Qw/7321c0d4c0a2f8d20a7940ace91bcbff/image.png)
+![image](https://images.contentful.com/alneenqid6w5/5B2i3p2lva8OO0I4geI8Qw/7321c0d4c0a2f8d20a7940ace91bcbff/image.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/layout-malfunctions-when-adding-or-removing-a-filter.md b/docs/known-issues/en/layout-malfunctions-when-adding-or-removing-a-filter.md
index 96c3e1421..f2ad41200 100644
--- a/docs/known-issues/en/layout-malfunctions-when-adding-or-removing-a-filter.md
+++ b/docs/known-issues/en/layout-malfunctions-when-adding-or-removing-a-filter.md
@@ -30,5 +30,5 @@ When adding/removing a filter within the Product and SKUs creation page, the lay
 
 You should click on where the *Filter results or search* button was and then click on the blue button in the lower left corner, thus normalizing the page layout.
 
-![Image](//images.contentful.com/alneenqid6w5/2HUT45Pgcgqack2CMg22ug/0073487d59c786e3f959e608f9015e38/Exemplo.jpg)
+![Image](https://images.contentful.com/alneenqid6w5/2HUT45Pgcgqack2CMg22ug/0073487d59c786e3f959e608f9015e38/Exemplo.jpg)
 
diff --git a/docs/known-issues/en/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md b/docs/known-issues/en/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
index b3c4c3265..b30e5e523 100644
--- a/docs/known-issues/en/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
+++ b/docs/known-issues/en/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
@@ -25,10 +25,10 @@ This feature is commonly used to create scenarios like: The **X** refrigerator s
 The known issue is evident in the following example, in which the marketplace can not reflect the same rules of installment as the seller:
 
 ## Marketplace - Up to 12x without interest
-![Marketplace Marketplace](//images.contentful.com/alneenqid6w5/c7CtSlVToIIQScyiM4AiS/e9f1415ccbe79d8fe34af8e9901b6570/Geladeira_Marketplace.png)
+![Marketplace Marketplace](https://images.contentful.com/alneenqid6w5/c7CtSlVToIIQScyiM4AiS/e9f1415ccbe79d8fe34af8e9901b6570/Geladeira_Marketplace.png)
 
 ## Seller - Up to 10x without interest
-![2017-06-16 18 15 44-Refrigerator 540 Liters Evox Brastemp Side Inverse - Brastemp](//images.contentful.com/alneenqid6w5/6HZs1prIVaUsOYCWeEMG8U/169a380f8e4c43cd0c644d280da0d126/2017-06-16_18_15_44-Geladeira_540_Litros_Evox_Brastemp_Side_Inverse_-Brastemp.png)
+![2017-06-16 18 15 44-Refrigerator 540 Liters Evox Brastemp Side Inverse - Brastemp](https://images.contentful.com/alneenqid6w5/6HZs1prIVaUsOYCWeEMG8U/169a380f8e4c43cd0c644d280da0d126/2017-06-16_18_15_44-Geladeira_540_Litros_Evox_Brastemp_Side_Inverse_-Brastemp.png)
 
 The display in the marketplace is wrong. The installments in 11x and 12x do not show interest, when in reality they should.
 
diff --git a/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md b/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
index 9e590d7d5..1576e1f63 100644
--- a/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
+++ b/docs/known-issues/en/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
@@ -29,9 +29,9 @@ Main causes of a badly configured app:
 
 In the case of a non-existent JSON Schema, insert the correct JSON Schema's name in the `model` field.
 
-For example: ![Screen Shot 2019-01-03 at 19.31.53](//images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
+For example: ![Screen Shot 2019-01-03 at 19.31.53](https://images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
 
-Notice how the app's border turns red and the error message on the console indicates "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](//images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
+Notice how the app's border turns red and the error message on the console indicates "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](https://images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/my-orders-layout-breaking-without-customization.md b/docs/known-issues/en/my-orders-layout-breaking-without-customization.md
index 3b562345b..c492ab851 100644
--- a/docs/known-issues/en/my-orders-layout-breaking-without-customization.md
+++ b/docs/known-issues/en/my-orders-layout-breaking-without-customization.md
@@ -25,7 +25,7 @@ internalReference:
 
 ---
 
-![Screen Shot 2017-05-26 at 12.01.58](//images.contentful.com/alneenqid6w5/qUqOq8ZyGOCAAoiUM0600/66a6bf0fa60bbd65fa9abd1ca7c825ae/Screen_Shot_2017-05-26_at_12.01.58.png)
+![Screen Shot 2017-05-26 at 12.01.58](https://images.contentful.com/alneenqid6w5/qUqOq8ZyGOCAAoiUM0600/66a6bf0fa60bbd65fa9abd1ca7c825ae/Screen_Shot_2017-05-26_at_12.01.58.png)
 
 If the layout of the new My Orders presents problems in your store _out of the box_, without any customization, it may be that your store's CSS is interfering with it.
 
diff --git a/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md b/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
index 4ac97b1c7..10cc1b775 100644
--- a/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
+++ b/docs/known-issues/en/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
@@ -20,7 +20,7 @@ internalReference:
 
 The NIF field (document) in the checkout for Portugal (UI) is allowing special characters to be entered as value. However, orders that are closed with special characters get stuck with error in the OMS.
 
-![OMS](//images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
+![OMS](https://images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md b/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md
index 54dc306d3..b58e29bec 100644
--- a/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md
+++ b/docs/known-issues/en/ordering-of-delivery-times-scheduled-at-checkout.md
@@ -20,7 +20,7 @@ internalReference:
 
 Currently the delivery times for a scheduled delivery are out of order, or in descending order. For better readability, this information is expected to be organized in ascending order.
 
-![image](//images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/orders-with-error-sistema-de-perfis.md b/docs/known-issues/en/orders-with-error-sistema-de-perfis.md
index f1e7eda7f..53585eb7e 100644
--- a/docs/known-issues/en/orders-with-error-sistema-de-perfis.md
+++ b/docs/known-issues/en/orders-with-error-sistema-de-perfis.md
@@ -24,7 +24,7 @@ Some orders in Orders Managment are stuck in the status "Processando", presentin
 
 This error is intermittent and its simulation is very difficult. The following is the log image of when this error occurs.
 
-![erro-sistema-de-perfis](//images.contentful.com/alneenqid6w5/3XS6EnP8kU8W2SewuYsAes/503ce84831f50a80f57bc31a713a71c7/erro-sistema-de-perfis.png)
+![erro-sistema-de-perfis](https://images.contentful.com/alneenqid6w5/3XS6EnP8kU8W2SewuYsAes/503ce84831f50a80f57bc31a713a71c7/erro-sistema-de-perfis.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md b/docs/known-issues/en/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
index 6495ec74d..ac8c4ea52 100644
--- a/docs/known-issues/en/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
+++ b/docs/known-issues/en/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
@@ -25,7 +25,7 @@ In the timeline, found in the order details (Orders Managment), the PCI informat
 
 - Select an old order (for instance, from June 2017).
 
-![pedido com log pci](//images.contentful.com/alneenqid6w5/1OflzCTMYcQwkgcWUCkwIC/6a4dc455400128870cd4790fa3ff3372/com_log.PNG)
+![pedido com log pci](https://images.contentful.com/alneenqid6w5/1OflzCTMYcQwkgcWUCkwIC/6a4dc455400128870cd4790fa3ff3372/com_log.PNG)
 
 - Compare it to a current order.
 - See that the information on Anti-Fraud, for exmaple - which comes from the PCI module -, will not be displayed.
diff --git a/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md b/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md
index 885c5aaa5..bf5b424a0 100644
--- a/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md
+++ b/docs/known-issues/en/pickup-point-disregarded-based-on-priority.md
@@ -36,7 +36,7 @@ To simulate the described scenario, at least two shipping policies serving the s
 4. See which pickup point has been selected;
 5. Check which pickup points were disregarded and note the message displayed.
 
-![KIpontoderetirada EN](//images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/097a4d4b13f79150adf8f2eda2e7a888/KIpontoderetirada_EN.png)
+![KIpontoderetirada EN](https://images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/097a4d4b13f79150adf8f2eda2e7a888/KIpontoderetirada_EN.png)
 
 The pickup point was disregarded because there was another shipping method already named as **SCS Mall**.
 
diff --git a/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index 5ada9f921..2276fbfca 100644
--- a/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/en/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -21,7 +21,7 @@ internalReference:
 At present, the possibility to display the "Receive | Pick up" options is subject to a CEP (ZIP code) search in any of the tabs. This means that, if for example you would search for a ZIP code that doesn't offer the pick-up point option in the "Receive" tab, the "Pick-up" tab would not be displayed.
 
 
-![Captura de Tela 2018-11-21 às 14.25.40](//images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
+![Captura de Tela 2018-11-21 às 14.25.40](https://images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
 
 ## Simulation
 
diff --git a/docs/known-issues/en/reserved-stock-in-invoiced-orders.md b/docs/known-issues/en/reserved-stock-in-invoiced-orders.md
index fccf1eb79..f3b9548a4 100644
--- a/docs/known-issues/en/reserved-stock-in-invoiced-orders.md
+++ b/docs/known-issues/en/reserved-stock-in-invoiced-orders.md
@@ -24,7 +24,7 @@ This happens when the order is in the `Pronto para Manuseio` status (Ready for H
 
 Example with order flow:
 
-![2017-06-13 182850](//images.contentful.com/alneenqid6w5/5Skd8YsCcMIicCcEGyoqwG/1a1a839dc36cdb9f818240b68817de3e/2017-06-13_182850.jpg)
+![2017-06-13 182850](https://images.contentful.com/alneenqid6w5/5Skd8YsCcMIicCcEGyoqwG/1a1a839dc36cdb9f818240b68817de3e/2017-06-13_182850.jpg)
 
 In the circulated step of the order flow, the product is invoiced without acknowledgment of the reservation.
 
diff --git a/docs/known-issues/en/schema-doesnt-present-price-in-outofstock-items-unavailable.md b/docs/known-issues/en/schema-doesnt-present-price-in-outofstock-items-unavailable.md
index 9b2c687b0..d7181d903 100644
--- a/docs/known-issues/en/schema-doesnt-present-price-in-outofstock-items-unavailable.md
+++ b/docs/known-issues/en/schema-doesnt-present-price-in-outofstock-items-unavailable.md
@@ -24,7 +24,7 @@ Unavailable products (outOfstock) do not have price information in Schema.
 
 - Take an item with no stock being displayed on the website as unavailable;
 - See in Schema that it will be displayed as outOfstock and will not show the price.
-![schema  outOfstock ](//images.contentful.com/alneenqid6w5/6PgCuzUXXGo0iC6UeAMUA6/4390b013aaf5d3083ffef407180cd484/ItemTypes-duplicidade.png)
+![schema  outOfstock ](https://images.contentful.com/alneenqid6w5/6PgCuzUXXGo0iC6UeAMUA6/4390b013aaf5d3083ffef407180cd484/ItemTypes-duplicidade.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md b/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md
index 2dfc26d78..4e97280e4 100644
--- a/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md
+++ b/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md
@@ -24,7 +24,7 @@ internalReference:
 
 When a user searches for a term and thereafter applies a filter to the multi-selection options (in the searchNavigator control), the searched term is initially removed from the query, meaning that the filter ignores the term and performs the search query only by considering the options chosen by the user.
 
-![search result](//images.contentful.com/alneenqid6w5/6BZ5Xh6OHe8WSWywOQCKGw/e814ecd5db35ff565151876dd8f826d5/search_result.gif)
+![search result](https://images.contentful.com/alneenqid6w5/6BZ5Xh6OHe8WSWywOQCKGw/e814ecd5db35ff565151876dd8f826d5/search_result.gif)
 
 ## Simulation
 
diff --git a/docs/known-issues/en/system-allows-the-user-to-change-a-main-web-site-generating-errors.md b/docs/known-issues/en/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
index e646231e2..70e8cac55 100644
--- a/docs/known-issues/en/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
+++ b/docs/known-issues/en/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
@@ -22,7 +22,7 @@ In the CMS module, the system lets the user manipulate a Web Site A and point to
 
 If the user wants to return, there is no possibility to point the Web Site B to A, as a parent. With this, it generates errors in the site like the error below, and the admin becomes inaccessible.
 
-![KI erro website](//images.contentful.com/alneenqid6w5/17hdmuW8qis8kyKUs6e8SG/2234b8f8916038ce6e8ccf98b6ff14a9/KI_erro_website.png)
+![KI erro website](https://images.contentful.com/alneenqid6w5/17hdmuW8qis8kyKUs6e8SG/2234b8f8916038ce6e8ccf98b6ff14a9/KI_erro_website.png)
 
 ## Simulation
 
@@ -31,7 +31,7 @@ If the user wants to return, there is no possibility to point the Web Site B to
 - In the first Web Site > Parent Web Site field, insert the Web Site referring to the Web Site 2;
 - In the second Web Site > Parent Web Site field, insert the Web Site referring to the Web Site 1.
 
-![KI erro website2](//images.contentful.com/alneenqid6w5/a6SpuvdBT2KOIiaSO6EGq/e98a7e9081262e773f63f165f7344ecc/KI_erro_website2.png)
+![KI erro website2](https://images.contentful.com/alneenqid6w5/a6SpuvdBT2KOIiaSO6EGq/e98a7e9081262e773f63f165f7344ecc/KI_erro_website2.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md b/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md
index 2e8da74d0..6bf9b5600 100644
--- a/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md
+++ b/docs/known-issues/en/the-product-information-button-does-not-display-the-data.md
@@ -21,10 +21,10 @@ internalReference:
 The <i class="fas fa-info-circle"></i> button available on the **Product and SKUs** listing on the **Catalog** module does not always display the product information. See the images below to understand the normal behavior of the button.
 
 **Product is not available**
-![info vazia](//images.ctfassets.net/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/695d568800f3c1ee1443b9632ebe5de9/image.png)
+![info vazia](https://images.ctfassets.net/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/695d568800f3c1ee1443b9632ebe5de9/image.png)
 
 **Product is available**
-![info preenchida](//images.ctfassets.net/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/0d029051c2061caccefa64d1184a5d9e/image.png)
+![info preenchida](https://images.ctfassets.net/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/0d029051c2061caccefa64d1184a5d9e/image.png)
 
 ## Simulation
 
@@ -41,5 +41,5 @@ The <i class="fas fa-info-circle"></i> button available on the **Product and SKU
 4. Click on the `Indexed Info` button.
 5. Check the Sales Channel item for information on the SKU as shown below.
 
-![indexed info](//images.contentful.com/alneenqid6w5/7oC2oM6doEqm0pXVAN6Y6u/558f152a4d9c05442178db25e1e4c582/image.png)
+![indexed info](https://images.contentful.com/alneenqid6w5/7oC2oM6doEqm0pXVAN6Y6u/558f152a4d9c05442178db25e1e4c582/image.png)
 
diff --git a/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md b/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md
index adb30a22d..36cbf04ad 100644
--- a/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md
+++ b/docs/known-issues/en/transactional-emails-dont-consider-items-removed-from-the-order.md
@@ -19,10 +19,10 @@ internalReference:
 ## Summary
 
 When an item is removed from the order:
-![item removido](//images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
+![item removido](https://images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
 
 The transactional email doesn't consider the removed item and shows both items in the email:
-![email transacional](//images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
+![email transacional](https://images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
 
 
 
diff --git a/docs/known-issues/en/unable-to-delete-templates-on-legacy-cms.md b/docs/known-issues/en/unable-to-delete-templates-on-legacy-cms.md
index d0ebca241..2fc210ce5 100644
--- a/docs/known-issues/en/unable-to-delete-templates-on-legacy-cms.md
+++ b/docs/known-issues/en/unable-to-delete-templates-on-legacy-cms.md
@@ -28,11 +28,11 @@ Customers are not able to delete templates from the legacy CMS.
 4. Click on the **HTML Templates** folder.
 5. Click on the `delete` button in any template.
 
-![HTML templates](//images.contentful.com/alneenqid6w5/6PWmj8jj0YJyi0tJ2h1Ay5/788bfa080f071df9f16adb8a1e7af67d/image.png)
+![HTML templates](https://images.contentful.com/alneenqid6w5/6PWmj8jj0YJyi0tJ2h1Ay5/788bfa080f071df9f16adb8a1e7af67d/image.png)
 
 When you try to delete a template, the following message will pop up:
 
-![Messagem CMS](//images.contentful.com/alneenqid6w5/579ZOpaYA2XeRW60bXcVow/7f915c8ec079be49f159c4f8a959efa1/image.png)
+![Messagem CMS](https://images.contentful.com/alneenqid6w5/579ZOpaYA2XeRW60bXcVow/7f915c8ec079be49f159c4f8a959efa1/image.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/en/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md b/docs/known-issues/en/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
index 6bd4cda7b..380e31342 100644
--- a/docs/known-issues/en/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
+++ b/docs/known-issues/en/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
@@ -32,7 +32,7 @@ When you upload two or more existing files to File Manager simultaneously, only
 
 After saving, the following message will be displayed:
 
-![File manager](//images.contentful.com/alneenqid6w5/4Z7tY3FKCDV1Cz6Whji6HI/d730b6accf6caeb81b373745b20c337d/image.png)
+![File manager](https://images.contentful.com/alneenqid6w5/4Z7tY3FKCDV1Cz6Whji6HI/d730b6accf6caeb81b373745b20c337d/image.png)
 
 This means that only one file was identified; the others are not being validated. All files are uploaded, but only one will replace its previous version.
 
diff --git a/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index e189b32d0..7ffc0ca7c 100644
--- a/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -42,6 +42,6 @@ Don’t worry: turning off this option will not make your store unprotected.
 If after these steps your Admin or store is still not loading, we advise you to try another browser.
 </div>
 
-![Firefox bug EN](//images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/06a078dc34744d8e07cf858e2288679a/Firefox_bug_EN.jpg)
+![Firefox bug EN](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/06a078dc34744d8e07cf858e2288679a/Firefox_bug_EN.jpg)
 
 
diff --git a/docs/known-issues/en/website-binding-with-old-license-manager-details.md b/docs/known-issues/en/website-binding-with-old-license-manager-details.md
index 8cd057f4c..bcdcf9401 100644
--- a/docs/known-issues/en/website-binding-with-old-license-manager-details.md
+++ b/docs/known-issues/en/website-binding-with-old-license-manager-details.md
@@ -29,13 +29,13 @@ The example of the __Delacasa__ store illustrates the bug:
 Before it was called __delacasa__ the domain __decoramovel__ had been created. The Portal created the Binding and then added the new information to the new domain for the same Binding.
 
 The new details entered in the LM:
-![license-manager-delacasa](//images.contentful.com/alneenqid6w5/6rC1pqQuQ0yeI60YqqS0Si/2d0cf344afd3f7cea14cf844ea86329b/license-manager-delacasa.JPG) 
+![license-manager-delacasa](https://images.contentful.com/alneenqid6w5/6rC1pqQuQ0yeI60YqqS0Si/2d0cf344afd3f7cea14cf844ea86329b/license-manager-delacasa.JPG) 
 
 of the Website dictionary (mundinho) were shown as follows, making it clear what had happened:
-![dictionary-delacasa](//images.contentful.com/alneenqid6w5/2w9Zf8aK1aw0euMsSouUEm/59b5b620f7c36f52f81af250be71b542/dicionario-delacasa.JPG) 
+![dictionary-delacasa](https://images.contentful.com/alneenqid6w5/2w9Zf8aK1aw0euMsSouUEm/59b5b620f7c36f52f81af250be71b542/dicionario-delacasa.JPG) 
 
 From the Website Binding showing the result:
-![binding-delacasa](//images.contentful.com/alneenqid6w5/4JqhEdsgdGWgo2QOCksUaM/bc67aa1883df5f8827d399f4e89fc123/binding-delacasa.JPG)
+![binding-delacasa](https://images.contentful.com/alneenqid6w5/4JqhEdsgdGWgo2QOCksUaM/bc67aa1883df5f8827d399f4e89fc123/binding-delacasa.JPG)
 
 ## Simulation
 
@@ -52,5 +52,5 @@ The new Binding will have the new details.
 After creating a new one, make the change and later, if necessary, delete the old one.
 
 It is important to do things in this order, or the site will go off the air.
-![2017-04-10 10 40 41-Index](//images.contentful.com/alneenqid6w5/Jvzm768i64YeqQkqCYAWk/3261595cb7f9af998aac4f0c99fe3fb6/2017-04-10_10_40_41-Index.png)
+![2017-04-10 10 40 41-Index](https://images.contentful.com/alneenqid6w5/Jvzm768i64YeqQkqCYAWk/3261595cb7f9af998aac4f0c99fe3fb6/2017-04-10_10_40_41-Index.png)
 
diff --git a/docs/known-issues/en/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md b/docs/known-issues/en/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
index 0a56a4dea..0b473999f 100644
--- a/docs/known-issues/en/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
+++ b/docs/known-issues/en/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
@@ -20,7 +20,7 @@ internalReference:
 
 There are two prices: a fixed price that is always in effect and a scheduled price, which is valid for a limited data range, which will be active concurrently with the fixed price.
 
-![precio-agendado-no-reactiva](//images.contentful.com/alneenqid6w5/28x1hbS9l2QgsyIcYyUoSM/bf1eecf7c1a429f8fc0070040f6fc2ac/precio-agendado-no-reactiva.png)
+![precio-agendado-no-reactiva](https://images.contentful.com/alneenqid6w5/28x1hbS9l2QgsyIcYyUoSM/bf1eecf7c1a429f8fc0070040f6fc2ac/precio-agendado-no-reactiva.png)
 
 When the scheduled price expires, the fixed price should be reenabled, since it will be the new and only price valid for this SKU. This re-enablement occurs for most of prices, but it is not happening for all cases; the product continues published on the web, in general with a price lower than the fixed price that was not automatically reenabled. 
 
diff --git a/docs/known-issues/en/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md b/docs/known-issues/en/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
index f5ae5843d..c8b2cf435 100644
--- a/docs/known-issues/en/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
+++ b/docs/known-issues/en/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
@@ -22,7 +22,7 @@ When you access a product page with a change (more than one SKU) with the querys
 
 However if the SKU selected (from the parameter) is unavailable (out of stock / not deliverable), when the user selects another available SKU in the SKU selector, price details are not shown.
 
-![Price not updated on selection of SKU](//images.contentful.com/alneenqid6w5/1GKcK5NUSoEcmMuesmiGiM/6ddb61d748aa566c6eb5607711a0ae3d/preco.gif)
+![Price not updated on selection of SKU](https://images.contentful.com/alneenqid6w5/1GKcK5NUSoEcmMuesmiGiM/6ddb61d748aa566c6eb5607711a0ae3d/preco.gif)
 
 ## Simulation
 
diff --git a/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
index b0a7ecf5b..5134c8199 100644
--- a/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
@@ -31,5 +31,5 @@ Crear un nuevo diccionario en el módulo CMS que no tenga ningún Host previamen
 
 Acceda al módulo CMS, haga clic en los botones lupa y limpiar en secuencia y se desbloqueará el botón agregar nuevo host.
 
-![PT - Criar dicionário não disponibiliza opção de "Add"](//images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/d9118e018381d7733489a862eb7140ad/image__1_.png)
+![PT - Criar dicionário não disponibiliza opção de "Add"](https://images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/d9118e018381d7733489a862eb7140ad/image__1_.png)
 
diff --git a/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index aa8162916..2cfb32c8c 100644
--- a/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -31,7 +31,7 @@ Esto se debía a que el número `1` se había configurado por defecto, incluso c
 
 Accede al **Admin VTEX > Home > Cómo mejorar > Catálogo**. Si la sección indica que hay `1` problema encontrado, al hacer clic en `Productos sin stock en los más vistos`, serás redirigido a la página del Catálogo.
 
-![Como melhorar ES](//images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/6315fb589d4ac05737e3bd3cd76c0dd4/Como_melhorar_ES.png)
+![Como melhorar ES](https://images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/6315fb589d4ac05737e3bd3cd76c0dd4/Como_melhorar_ES.png)
 
 
 ## Workaround
@@ -40,6 +40,6 @@ No es necesario que el usuario realice ninguna acción porque ya hemos soluciona
 
 `No encontramos ningún problema en su catálogo.`
 
-![Como melhorar fixed ES](//images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/67494d3447838a49e35454aafa2f5e3a/Como_melhorar_fixed_ES.png)
+![Como melhorar fixed ES](https://images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/67494d3447838a49e35454aafa2f5e3a/Como_melhorar_fixed_ES.png)
 
 
diff --git a/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index 75cd2e1c1..8cf4552f7 100644
--- a/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/es/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumario
 
-El Campo Automático (campo calculado) funciona correctamente cuando "Recalcular este campo:" está establecido para "solo cuando ingrese el registro", pero deja de funcionar cuando está programado para recalcular "en la primera hora..." y susvariantes. ![inline1511102536](//images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
+El Campo Automático (campo calculado) funciona correctamente cuando "Recalcular este campo:" está establecido para "solo cuando ingrese el registro", pero deja de funcionar cuando está programado para recalcular "en la primera hora..." y susvariantes. ![inline1511102536](https://images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
index fab67d978..dec29830c 100644
--- a/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
@@ -30,7 +30,7 @@ Basta tener un código de rastreo válido en cualquier pedido. Los días siguien
 
 Es posible enviar actualizaciones de rastreo vía API, manteniendo el comportamiento de envío de e-mails. Lo mismo para la confirmación de entrega, que también puede hacerse por la interfaz del OMS.
 
-![2017-08-16 195850](//images.contentful.com/alneenqid6w5/1IPsGBnkKYggY8m6smeqOA/a2a95afc6fb34e7bfe89c1cab2fdb612/2017-08-16_195850.jpg)
+![2017-08-16 195850](https://images.contentful.com/alneenqid6w5/1IPsGBnkKYggY8m6smeqOA/a2a95afc6fb34e7bfe89c1cab2fdb612/2017-08-16_195850.jpg)
 
 La confirmación de entrega hecha vía OMS también se retransmite a los marketplaces.
 
diff --git a/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md b/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md
index da92bb71d..4747e7eee 100644
--- a/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md
+++ b/docs/known-issues/es/cms-is-not-accessible-through-the-new-admin.md
@@ -20,7 +20,7 @@ internalReference:
 
 Al acceder al CMS a través del nuevo ambiente administrativo (My VTEX - `{AccountName}.myvtex.com/admin`), se muestra una página de error, no siendo posible acceder al CMS.
 
-![4JSc1cw](//images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
+![4JSc1cw](https://images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/creating-or-editing-list-type-does-not-work.md b/docs/known-issues/es/creating-or-editing-list-type-does-not-work.md
index 1cae71ac5..8260b7558 100644
--- a/docs/known-issues/es/creating-or-editing-list-type-does-not-work.md
+++ b/docs/known-issues/es/creating-or-editing-list-type-does-not-work.md
@@ -20,7 +20,7 @@ internalReference:
 
 En la pantalla de Tipos de lista, al hacer clic en "Ver detalles" o "Nuevo tipo de lista" no se puede crear / cambiar el tipo de lista.
 
-![Creación de tipo de lista](//images.contentful.com/alneenqid6w5/3dmnyQDRyMc8guqw8m8EOc/b6192d84ade5e8990990d170ac4614d2/1.png)
+![Creación de tipo de lista](https://images.contentful.com/alneenqid6w5/3dmnyQDRyMc8guqw8m8EOc/b6192d84ade5e8990990d170ac4614d2/1.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/crm-error-when-searching-with-spaces.md b/docs/known-issues/es/crm-error-when-searching-with-spaces.md
index 7e27c6371..63cb94683 100644
--- a/docs/known-issues/es/crm-error-when-searching-with-spaces.md
+++ b/docs/known-issues/es/crm-error-when-searching-with-spaces.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumario
 
-El usuario recibe un mensaje de error al buscar un documento con un atributo que contenga espacio [Screen Shot 2018-12-26 at 14.38.55](//images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
+El usuario recibe un mensaje de error al buscar un documento con un atributo que contenga espacio [Screen Shot 2018-12-26 at 14.38.55](https://images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
 Ejemplo: Buscando/filtrando por el campo "Ciudad" con el atributo "Rio de Janeiro" producirá un mensaje de error.
 
 
@@ -36,7 +36,7 @@ Ejemplo: Buscando/filtrando por el campo "Ciudad" con el atributo "Rio de Janeir
 
 ## Workaround
 
-![Screen Shot 2018-12-26 at 14.40.03](//images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
+![Screen Shot 2018-12-26 at 14.40.03](https://images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)
 Felizmente hay una alternativa simple que no necesita el uso de API.
 Al hacer clic en "Todos" en el menú desplegable, la misma búsqueda puede realizarse sin causar error.
 
diff --git a/docs/known-issues/es/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md b/docs/known-issues/es/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
index a57172aa3..d4f6702f0 100644
--- a/docs/known-issues/es/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
+++ b/docs/known-issues/es/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
@@ -20,7 +20,7 @@ internalReference:
 
 Al realizar una consulta de GiftCard en el Admin, por ID (documento), el voucher del cliente no aparece.
 
-![vale](//images.contentful.com/alneenqid6w5/78Mt2DDgaIwg2I66gSYGgM/66de95f8e3b3b73d20a0165f4da67f88/vale.png)
+![vale](https://images.contentful.com/alneenqid6w5/78Mt2DDgaIwg2I66gSYGgM/66de95f8e3b3b73d20a0165f4da67f88/vale.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md b/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md
index cad976877..a2dea15b0 100644
--- a/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md
+++ b/docs/known-issues/es/divergence-between-total-order-value-and-total-products-value.md
@@ -26,7 +26,7 @@ El pedido se cierra y se transacciona normalmente en VTEX. Pero dependiendo de l
 
 Ejemplo de ocurrencia:
 
-![image](//images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
 
 En ese caso, el valor total del pedido cobrado del cliente quedó en `R$ 7,98`. Sin embargo, al sumar los valores de venta registrados en cada producto, el total sería de `R$ 7,95`.
 
diff --git a/docs/known-issues/es/encoding-error-in-apple-mail-app.md b/docs/known-issues/es/encoding-error-in-apple-mail-app.md
index 5331aac64..6707961ba 100644
--- a/docs/known-issues/es/encoding-error-in-apple-mail-app.md
+++ b/docs/known-issues/es/encoding-error-in-apple-mail-app.md
@@ -29,7 +29,7 @@ Montar un trigger de envío de correo electrónico que tenga carácter especial
 
 Resultado:
 
-![png](//images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
+![png](https://images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md b/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
index 1f415fded..116a0bfe9 100644
--- a/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
+++ b/docs/known-issues/es/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
@@ -22,7 +22,7 @@ Las tiendas VTEX pueden convertirse en [sellers](https://help.vtex.com/es/tutori
 
 Esto se debe a que los productos que son vendidos tanto por el marketplace como por sus sellers no son reconocidos por el sistema al ser enviados. Solo es posible enviar productos que se venden en solo una de las tiendas.
 
-![arquitetura circular](//images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/8fde1676b4fb9b405e56b4e52689f982/arquitetura_circular.JPG)
+![arquitetura circular](https://images.ctfassets.net/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/8fde1676b4fb9b405e56b4e52689f982/arquitetura_circular.JPG)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
index 4b1c1265c..f34973483 100644
--- a/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
@@ -29,7 +29,7 @@ El mensaje de autorización de error puede cambiar de `node` a `react` de acuerd
 1. Instalar el VTEX CLI (ToolBelt);
 2. Navegar hasta el directorio de la app;
 3. Ejecutar el comando "vtex-link" en el terminal.
-4. ![image (8)](//images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
+4. ![image (8)](https://images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/geolocation-search-for-pickup-points-loading-indefinitely.md b/docs/known-issues/es/geolocation-search-for-pickup-points-loading-indefinitely.md
index 3e30409e5..f8b9d19b5 100644
--- a/docs/known-issues/es/geolocation-search-for-pickup-points-loading-indefinitely.md
+++ b/docs/known-issues/es/geolocation-search-for-pickup-points-loading-indefinitely.md
@@ -35,7 +35,7 @@ Si la ubicación de su navegador satisface la condición anterior, siga los paso
 5. Durante el _checkout_, seleccione la opción de entrega «punto de recogida». 
 6. Observe que la página se queda cargando, mostrando el mensaje «Esperando permiso para obtener su ubicación actual».
 
-![erro Es](//images.contentful.com/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/c9b547445063ca5893288590621944c9/erro_Es.png)
+![erro Es](https://images.contentful.com/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/c9b547445063ca5893288590621944c9/erro_Es.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md b/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
index 376a30e8e..e44582555 100644
--- a/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
+++ b/docs/known-issues/es/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
@@ -28,7 +28,7 @@ En los productos con personalización de Assembly options, un ítem principal ti
 3. Selecciona el ítem secundario del producto, en la misma cantidad;
 4. Revisa los ítems en el carrito.
 
-![KI assembly](//images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/01c933c01f3b6b361b06de22d8160e9a/KI_assembly.png)
+![KI assembly](https://images.ctfassets.net/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/01c933c01f3b6b361b06de22d8160e9a/KI_assembly.png)
 
 Observa que el carrito contiene una unidad más del ítem secundario en comparación con el ítem principal.
 
diff --git a/docs/known-issues/es/incorrect-canonical-tag-on-https-pages.md b/docs/known-issues/es/incorrect-canonical-tag-on-https-pages.md
index 7815ec4a7..60c8e394c 100644
--- a/docs/known-issues/es/incorrect-canonical-tag-on-https-pages.md
+++ b/docs/known-issues/es/incorrect-canonical-tag-on-https-pages.md
@@ -25,7 +25,7 @@ Al activar el HTTPS en una carpeta específica, la tag HTML _canonical_ permanec
 1. Activar HTTPS en una sola carpeta del sitio ([guía](https://help.vtex.com/tutorial/--frequentlyAskedQuestions_4378));
 2. Comprobar, en el HTML renderizado, la tag _canonical_.
 
-![image](//images.contentful.com/alneenqid6w5/5B2i3p2lva8OO0I4geI8Qw/7321c0d4c0a2f8d20a7940ace91bcbff/image.png)
+![image](https://images.contentful.com/alneenqid6w5/5B2i3p2lva8OO0I4geI8Qw/7321c0d4c0a2f8d20a7940ace91bcbff/image.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/layout-malfunctions-when-adding-or-removing-a-filter.md b/docs/known-issues/es/layout-malfunctions-when-adding-or-removing-a-filter.md
index 10efd7bab..53bdd44e2 100644
--- a/docs/known-issues/es/layout-malfunctions-when-adding-or-removing-a-filter.md
+++ b/docs/known-issues/es/layout-malfunctions-when-adding-or-removing-a-filter.md
@@ -30,5 +30,5 @@ Al añadir / quitar filtro dentro de la página de registro de productos y Skus,
 
 Usted debe hacer clic donde quedaba *Filtrar resultados o hacer una búsqueda* y luego hacer clic en el botón azul en la esquina inferior izquierda, con lo que el diseño de la página será normalizado.
 
-![Image](//images.contentful.com/alneenqid6w5/2HUT45Pgcgqack2CMg22ug/0073487d59c786e3f959e608f9015e38/Exemplo.jpg)
+![Image](https://images.contentful.com/alneenqid6w5/2HUT45Pgcgqack2CMg22ug/0073487d59c786e3f959e608f9015e38/Exemplo.jpg)
 
diff --git a/docs/known-issues/es/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md b/docs/known-issues/es/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
index 6e2bfd3df..32af66825 100644
--- a/docs/known-issues/es/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
+++ b/docs/known-issues/es/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
@@ -25,10 +25,10 @@ Esta funcionalidad se utiliza comúnmente para crear escenarios como éste: la n
 El problema conocido es evidente en el siguiente ejemplo, en el que el marketplace no puede reflejar las mismas reglas de parcelación que el seller:
 
 ## Mercado - Hasta 12x sin intereses
-![Heladera Marketplace](//images.contentful.com/alneenqid6w5/c7CtSlVToIIQScyiM4AiS/e9f1415ccbe79d8fe34af8e9901b6570/Geladeira_Marketplace.png)
+![Heladera Marketplace](https://images.contentful.com/alneenqid6w5/c7CtSlVToIIQScyiM4AiS/e9f1415ccbe79d8fe34af8e9901b6570/Geladeira_Marketplace.png)
 
 ## Vendedor - Hasta 10x sin intereses
-![2017-06-16 18 15 44-Refrigerador 540 Litros Evox Brastemp Side Inverse - Brastemp](//images.contentful.com/alneenqid6w5/6HZs1prIVaUsOYCWeEMG8U/169a380f8e4c43cd0c644d280da0d126/2017-06-16_18_15_44-Geladora_540_Litros_Evox_Brastemp_Side_Inverse_-_Brastemp.png)
+![2017-06-16 18 15 44-Refrigerador 540 Litros Evox Brastemp Side Inverse - Brastemp](https://images.contentful.com/alneenqid6w5/6HZs1prIVaUsOYCWeEMG8U/169a380f8e4c43cd0c644d280da0d126/2017-06-16_18_15_44-Geladora_540_Litros_Evox_Brastemp_Side_Inverse_-_Brastemp.png)
 
 La visualización en el marketplace es incorrecta. Las parcelas en 11x y 12x no exhiben intereses, cuando, en realidad, deberían exhibir.
 
diff --git a/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md b/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
index fe5e3feea..2e54f9ffe 100644
--- a/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
+++ b/docs/known-issues/es/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
@@ -29,9 +29,9 @@ Principales causas de una aplicación mal configurada:
 
 En el caso de un JSON Schema inexistente, coloque en el campo `model` el nombre correcto del JSON Schema.
 
-Por ejemplo: ![Screen Shot 2019-01-03 at 19.31.53](//images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
+Por ejemplo: ![Screen Shot 2019-01-03 at 19.31.53](https://images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
 
-Observe cómo el borde de la aplicación se vuelve rojo y el mensaje de error en la consola indica el error "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](//images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
+Observe cómo el borde de la aplicación se vuelve rojo y el mensaje de error en la consola indica el error "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](https://images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
 
 
 ## Workaround
diff --git a/docs/known-issues/es/my-orders-layout-breaking-without-customization.md b/docs/known-issues/es/my-orders-layout-breaking-without-customization.md
index fbd5479c1..faa476225 100644
--- a/docs/known-issues/es/my-orders-layout-breaking-without-customization.md
+++ b/docs/known-issues/es/my-orders-layout-breaking-without-customization.md
@@ -25,7 +25,7 @@ internalReference:
 
 ---
 
-![Screen Shot 2017-05-26 at 12.01.58](//images.contentful.com/alneenqid6w5/qUqOq8ZyGOCAAoiUM0600/66a6bf0fa60bbd65fa9abd1ca7c825ae/Screen_Shot_2017-05-26_at_12.01.58.png)
+![Screen Shot 2017-05-26 at 12.01.58](https://images.contentful.com/alneenqid6w5/qUqOq8ZyGOCAAoiUM0600/66a6bf0fa60bbd65fa9abd1ca7c825ae/Screen_Shot_2017-05-26_at_12.01.58.png)
 
 Si el layout del nuevo My Orders presenta problemas en su tienda _out of the box_, sin ninguna personalización, puede que el CSS de su tienda esté interfiriendo con él.
 
diff --git a/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md b/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
index aa4a27657..cd6bb9799 100644
--- a/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
+++ b/docs/known-issues/es/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
@@ -20,7 +20,7 @@ internalReference:
 
 El campo NIF (documento) del checkout de Portugal (IU) está permitiendo introducir caracteres especiales en sus valores. Sin embargo, los pedidos que se cierran con caracteres especiales quedan bloqueados con error en el OMS.
 
-![OMS](//images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
+![OMS](https://images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md b/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md
index fc2e94f3e..2dc051b98 100644
--- a/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md
+++ b/docs/known-issues/es/ordering-of-delivery-times-scheduled-at-checkout.md
@@ -20,7 +20,7 @@ internalReference:
 
 Actualmente los horarios de entrega para una entrega programada están fuera de orden, o en orden decreciente. Para una mejor legibilidad, se espera que esta información se ordene de forma creciente.
 
-![image](//images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
 
 ## Simulación
 
diff --git a/docs/known-issues/es/orders-with-error-sistema-de-perfis.md b/docs/known-issues/es/orders-with-error-sistema-de-perfis.md
index cfdaf0ed8..dcf504959 100644
--- a/docs/known-issues/es/orders-with-error-sistema-de-perfis.md
+++ b/docs/known-issues/es/orders-with-error-sistema-de-perfis.md
@@ -24,7 +24,7 @@ Algunos pedidos en el Gestión de Pedidos quedan parados en el estado "Processan
 
 Este error es intermitente, siendo muy difícil su simulación. A continuación, tenemos la imagen del registro de cuando se produce este error.
 
-![erro-sistema-de-perfis](//images.contentful.com/alneenqid6w5/3XS6EnP8kU8W2SewuYsAes/503ce84831f50a80f57bc31a713a71c7/erro-sistema-de-perfis.png)
+![erro-sistema-de-perfis](https://images.contentful.com/alneenqid6w5/3XS6EnP8kU8W2SewuYsAes/503ce84831f50a80f57bc31a713a71c7/erro-sistema-de-perfis.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md b/docs/known-issues/es/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
index 54661779e..6fccf47a8 100644
--- a/docs/known-issues/es/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
+++ b/docs/known-issues/es/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
@@ -25,7 +25,7 @@ En la línea de tiempo, encontrada en los detalles del pedido (Gestión de Pedid
 
 - Elegir un pedido antiguo (por ejemplo, de Junio de 2017).
 
-![pedido com log pci](//images.contentful.com/alneenqid6w5/1OflzCTMYcQwkgcWUCkwIC/6a4dc455400128870cd4790fa3ff3372/com_log.PNG)
+![pedido com log pci](https://images.contentful.com/alneenqid6w5/1OflzCTMYcQwkgcWUCkwIC/6a4dc455400128870cd4790fa3ff3372/com_log.PNG)
 
 - Comparar con un pedido actual.
 - Ver que no aparecerán las informaciones del PCI sobre Antifraude, que mostramos como ejemplo.
diff --git a/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md b/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md
index 33f42f896..06ebd8a62 100644
--- a/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md
+++ b/docs/known-issues/es/pickup-point-disregarded-based-on-priority.md
@@ -39,7 +39,7 @@ To simulate the described scenario, at least two shipping policies serving the s
 4. See which pickup point has been selected;
 5. Check which pickup points were disregarded and note the message displayed.
 
-![KIpontoderetirada ES](//images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/3a5671abaf682e8a0a52e73e5db41896/KIpontoderetirada_ES.png)
+![KIpontoderetirada ES](https://images.ctfassets.net/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/3a5671abaf682e8a0a52e73e5db41896/KIpontoderetirada_ES.png)
 
 The pickup point was disregarded because there was another shipping method already named as **SCS Mall**.
 
diff --git a/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index 32c4e476e..adec58422 100644
--- a/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -20,7 +20,7 @@ internalReference:
 
 Actualmente, el escenario de exhibición de las opciones "Recibir | Retirar" está condicionado a la búsqueda del código postal en cualquiera de las pestañas. Esto significa que, si se busca en la pestaña "Recibir" un código postal que no se atienda en un punto de recogida, la pestaña "Retirar" no se mostrará al usuario.
 
-![Captura de Pantalla 2018-11-21 a las  14.25.40](//images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png)
+![Captura de Pantalla 2018-11-21 a las  14.25.40](https://images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png)
 
 
 ## Simulación
diff --git a/docs/known-issues/es/reserved-stock-in-invoiced-orders.md b/docs/known-issues/es/reserved-stock-in-invoiced-orders.md
index 0416c0e7e..070bb5c30 100644
--- a/docs/known-issues/es/reserved-stock-in-invoiced-orders.md
+++ b/docs/known-issues/es/reserved-stock-in-invoiced-orders.md
@@ -24,7 +24,7 @@ Esto ocurre cuando el pedido está en el estado `Pronto para Manuseio` status (L
 
 Ejemplo con el flujo del pedido:
 
-![2017-06-13 182850](//images.contentful.com/alneenqid6w5/5Skd8YsCcMIicCcEGyoqwG/1a1a839dc36cdb9f818240b68817de3e/2017-06-13_182850.jpg)
+![2017-06-13 182850](https://images.contentful.com/alneenqid6w5/5Skd8YsCcMIicCcEGyoqwG/1a1a839dc36cdb9f818240b68817de3e/2017-06-13_182850.jpg)
 
 En el paso circulado del flujo del pedido, el producto se factura sin el reconocimiento de la reserva.
 
diff --git a/docs/known-issues/es/schema-doesnt-present-price-in-outofstock-items-unavailable.md b/docs/known-issues/es/schema-doesnt-present-price-in-outofstock-items-unavailable.md
index 8b96a66b0..7545bdad1 100644
--- a/docs/known-issues/es/schema-doesnt-present-price-in-outofstock-items-unavailable.md
+++ b/docs/known-issues/es/schema-doesnt-present-price-in-outofstock-items-unavailable.md
@@ -24,7 +24,7 @@ Los productos no disponibles (outOfstock) no tienen la información de precio en
 
 - Tome un artículo sin stock que se esté mostrando en el sitio como no disponible;
 - Usted verá en el Schema que él se imprimirá como outOfstock y no se mostrará el precio.
-![schema  outOfstock ](//images.contentful.com/alneenqid6w5/6PgCuzUXXGo0iC6UeAMUA6/4390b013aaf5d3083ffef407180cd484/ItemTypes-duplicidade.png)
+![schema  outOfstock ](https://images.contentful.com/alneenqid6w5/6PgCuzUXXGo0iC6UeAMUA6/4390b013aaf5d3083ffef407180cd484/ItemTypes-duplicidade.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md b/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md
index 34810d720..f4394729f 100644
--- a/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md
+++ b/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md
@@ -24,7 +24,7 @@ internalReference:
 
 Cuando el usuario realiza una búsqueda por término y, a continuación, aplica un filtro en las opciones de selección múltiple (en el control searchNavigator), el término buscado inicialmente se elimina de la consulta, es decir, el filtro ignora el término y aplica la búsqueda solo con las opciones elegidas por el usuario.
 
-![search result](//images.contentful.com/alneenqid6w5/6BZ5Xh6OHe8WSWywOQCKGw/e814ecd5db35ff565151876dd8f826d5/search_result.gif)
+![search result](https://images.contentful.com/alneenqid6w5/6BZ5Xh6OHe8WSWywOQCKGw/e814ecd5db35ff565151876dd8f826d5/search_result.gif)
 
 
 ## Simulación
diff --git a/docs/known-issues/es/system-allows-the-user-to-change-a-main-web-site-generating-errors.md b/docs/known-issues/es/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
index 69900622b..1be6cc433 100644
--- a/docs/known-issues/es/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
+++ b/docs/known-issues/es/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
@@ -22,7 +22,7 @@ En el módulo CMS, el sistema deja al usuario manipular un sitio web A y apuntar
 
 Si el usuario desea regresar, no hay la posibilidad de apuntar el sitio B al A, como padre. Con eso, genera errores en el sitio como el error abajo, y el admin queda inaccesible.
 
-![KI erro website](//images.contentful.com/alneenqid6w5/17hdmuW8qis8kyKUs6e8SG/2234b8f8916038ce6e8ccf98b6ff14a9/KI_erro_website.png)
+![KI erro website](https://images.contentful.com/alneenqid6w5/17hdmuW8qis8kyKUs6e8SG/2234b8f8916038ce6e8ccf98b6ff14a9/KI_erro_website.png)
 
 ## Simulación
 
@@ -31,7 +31,7 @@ Si el usuario desea regresar, no hay la posibilidad de apuntar el sitio B al A,
 - En el primer Web Site > campo Web Site Padre, insertar el Web Site referente al Web Site 2;
 - En el segundo sitio web> campo Web Site Padre, inserte el Web Site referente al Web Site 1.
 
-![KI erro website2](//images.contentful.com/alneenqid6w5/a6SpuvdBT2KOIiaSO6EGq/e98a7e9081262e773f63f165f7344ecc/KI_erro_website2.png)
+![KI erro website2](https://images.contentful.com/alneenqid6w5/a6SpuvdBT2KOIiaSO6EGq/e98a7e9081262e773f63f165f7344ecc/KI_erro_website2.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/the-product-information-button-does-not-display-the-data.md b/docs/known-issues/es/the-product-information-button-does-not-display-the-data.md
index ee058875a..d18d51083 100644
--- a/docs/known-issues/es/the-product-information-button-does-not-display-the-data.md
+++ b/docs/known-issues/es/the-product-information-button-does-not-display-the-data.md
@@ -22,11 +22,11 @@ El botón <i class="fas fa-info-circle"></i>, disponible en la lista de **Produc
 
 **Producto no disponible**
 
-![info vazia](//images.contentful.com/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/762ff4e2e1986c8438c5c1f2ee2f9a29/image.png)
+![info vazia](https://images.contentful.com/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/762ff4e2e1986c8438c5c1f2ee2f9a29/image.png)
 
 **Producto disponible**
 
-![info preenchida](//images.contentful.com/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/d71ae910c0726c0643a5f7ad9e6f7e52/image.png)
+![info preenchida](https://images.contentful.com/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/d71ae910c0726c0643a5f7ad9e6f7e52/image.png)
 
 
 ## Simulación
@@ -44,6 +44,6 @@ El botón <i class="fas fa-info-circle"></i>, disponible en la lista de **Produc
 4. Haga clic en el botón `Información indexada`.
 5. Verifique la información del SKU en el ítem Sales Channel como se muestra en la imagen a continuación.
 
-![indexed info](//images.contentful.com/alneenqid6w5/7oC2oM6doEqm0pXVAN6Y6u/558f152a4d9c05442178db25e1e4c582/image.png)
+![indexed info](https://images.contentful.com/alneenqid6w5/7oC2oM6doEqm0pXVAN6Y6u/558f152a4d9c05442178db25e1e4c582/image.png)
 
 
diff --git a/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md b/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md
index c342f52dd..b59df20f4 100644
--- a/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md
+++ b/docs/known-issues/es/transactional-emails-dont-consider-items-removed-from-the-order.md
@@ -19,10 +19,10 @@ internalReference:
 ## Sumario
 
 Cuando un ítem es excluído del pedido:
-![item removido](//images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
+![item removido](https://images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
 
 El e-mail transaccional no considera el item removido y presenta los dos ítems en el e-mail:
-![email transacional](//images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
+![email transacional](https://images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
 
 
 
diff --git a/docs/known-issues/es/unable-to-delete-templates-on-legacy-cms.md b/docs/known-issues/es/unable-to-delete-templates-on-legacy-cms.md
index e4c6821fa..ed5557ff3 100644
--- a/docs/known-issues/es/unable-to-delete-templates-on-legacy-cms.md
+++ b/docs/known-issues/es/unable-to-delete-templates-on-legacy-cms.md
@@ -28,11 +28,11 @@ Los clientes no pueden eliminar las plantillas del CMS antiguo.
 4. Haz clic en la carpeta **HTML Templates**.
 5. Haz clic en el botón `delete` de cualquier plantilla.
 
-![HTML templates](//images.contentful.com/alneenqid6w5/6PWmj8jj0YJyi0tJ2h1Ay5/788bfa080f071df9f16adb8a1e7af67d/image.png)
+![HTML templates](https://images.contentful.com/alneenqid6w5/6PWmj8jj0YJyi0tJ2h1Ay5/788bfa080f071df9f16adb8a1e7af67d/image.png)
 
 Cuando intentas eliminar una plantilla, se muestra el siguiente mensaje:
 
-![Messagem CMS](//images.contentful.com/alneenqid6w5/579ZOpaYA2XeRW60bXcVow/7f915c8ec079be49f159c4f8a959efa1/image.png)
+![Messagem CMS](https://images.contentful.com/alneenqid6w5/579ZOpaYA2XeRW60bXcVow/7f915c8ec079be49f159c4f8a959efa1/image.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/es/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md b/docs/known-issues/es/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
index 9930c01e9..cc357bd7e 100644
--- a/docs/known-issues/es/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
+++ b/docs/known-issues/es/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
@@ -32,7 +32,7 @@ Cuando se envían simultáneamente dos o más archivos existentes en el File Man
 
 A continuación, se mostrará el siguiente mensaje:
 
-![File manager](//images.contentful.com/alneenqid6w5/4Z7tY3FKCDV1Cz6Whji6HI/d730b6accf6caeb81b373745b20c337d/image.png)
+![File manager](https://images.contentful.com/alneenqid6w5/4Z7tY3FKCDV1Cz6Whji6HI/d730b6accf6caeb81b373745b20c337d/image.png)
 
 Esto significa que solo se identifica un archivo; los demás no se validan. Se cargan todos los archivos, pero solo uno de ellos sustituirá a su versión anterior.
 
diff --git a/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index fe299ccf3..33209d0ae 100644
--- a/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -41,5 +41,5 @@ No se preocupe: desactivar esta opción no significa que su tienda estará despr
 Si después de estos pasos su Admin VTEX o tienda aún no se carga, le sugerimos que intente acceder con otro navegador.
 </div>
 
-![Firefox bug ES](//images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/5d89ca13799da3ada490e383f0913573/Firefox_bug_ES.jpg)
+![Firefox bug ES](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/5d89ca13799da3ada490e383f0913573/Firefox_bug_ES.jpg)
 
diff --git a/docs/known-issues/es/website-binding-with-old-license-manager-details.md b/docs/known-issues/es/website-binding-with-old-license-manager-details.md
index 8be1a4128..fc8a1e328 100644
--- a/docs/known-issues/es/website-binding-with-old-license-manager-details.md
+++ b/docs/known-issues/es/website-binding-with-old-license-manager-details.md
@@ -29,13 +29,13 @@ El ejemplo de la tienda __Delacasa__ ilustra el bug:
 Antes de llamarse __delacasa__ habían creado el dominio __decoramovel__, el Portal creó el Binding y posteriormente adicionó las nuevas informaciones del nuevo dominio en el mismo Binding.
 
 Las nuevas informaciones insertadas en el LM:
-![license-manager-delacasa](//images.contentful.com/alneenqid6w5/6rC1pqQuQ0yeI60YqqS0Si/2d0cf344afd3f7cea14cf844ea86329b/license-manager-delacasa.JPG) 
+![license-manager-delacasa](https://images.contentful.com/alneenqid6w5/6rC1pqQuQ0yeI60YqqS0Si/2d0cf344afd3f7cea14cf844ea86329b/license-manager-delacasa.JPG) 
 
 El diccionario del Website (mundinho) [mundito] como quedó, dejando el comportamiento en evidencia:
-![dicionario-delacasa](//images.contentful.com/alneenqid6w5/2w9Zf8aK1aw0euMsSouUEm/59b5b620f7c36f52f81af250be71b542/dicionario-delacasa.JPG) 
+![dicionario-delacasa](https://images.contentful.com/alneenqid6w5/2w9Zf8aK1aw0euMsSouUEm/59b5b620f7c36f52f81af250be71b542/dicionario-delacasa.JPG) 
 
 La parte de Webiste Binding que muestra el resultado:
-![binding-delacasa](//images.contentful.com/alneenqid6w5/4JqhEdsgdGWgo2QOCksUaM/bc67aa1883df5f8827d399f4e89fc123/binding-delacasa.JPG)
+![binding-delacasa](https://images.contentful.com/alneenqid6w5/4JqhEdsgdGWgo2QOCksUaM/bc67aa1883df5f8827d399f4e89fc123/binding-delacasa.JPG)
 
 ## Simulación
 
@@ -52,5 +52,5 @@ El nuevo Binding cargará las informaciones nuevas.
 Luego de crear el nuevo, hacer el cambio y luego, de ser necesario, excluir el antiguo.
 
 Es importante mantener este orden, para evitar que el sitio salga del aire.
-![2017-04-10 10 40 41-Index](//images.contentful.com/alneenqid6w5/Jvzm768i64YeqQkqCYAWk/3261595cb7f9af998aac4f0c99fe3fb6/2017-04-10_10_40_41-Index.png)
+![2017-04-10 10 40 41-Index](https://images.contentful.com/alneenqid6w5/Jvzm768i64YeqQkqCYAWk/3261595cb7f9af998aac4f0c99fe3fb6/2017-04-10_10_40_41-Index.png)
 
diff --git a/docs/known-issues/es/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md b/docs/known-issues/es/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
index addd4387a..4c3366c0d 100644
--- a/docs/known-issues/es/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
+++ b/docs/known-issues/es/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
@@ -20,7 +20,7 @@ internalReference:
 
 Se cuentan con dos precios: un precio fijo que siempre permanece vigente y un precio agendado que tiene validez para un rango acotado de fechas, que estará activo a la par del precio fijo.
 
-![precio-agendado-no-reactiva](//images.contentful.com/alneenqid6w5/28x1hbS9l2QgsyIcYyUoSM/bf1eecf7c1a429f8fc0070040f6fc2ac/precio-agendado-no-reactiva.png)
+![precio-agendado-no-reactiva](https://images.contentful.com/alneenqid6w5/28x1hbS9l2QgsyIcYyUoSM/bf1eecf7c1a429f8fc0070040f6fc2ac/precio-agendado-no-reactiva.png)
 
 Cuando el precio agendado vence, debería reactivar el precio fijo, ya que será el nuevo y único precio válido para ese SKU. Esta reactivación ocurre para la mayoría de los precios, pero no está ocurriendo en todos los casos y el producto queda publicado en la web, generalmente con un precio más económico que el precio fijo que no se reactivó automáticamente.
 
diff --git a/docs/known-issues/es/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md b/docs/known-issues/es/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
index 4b028e2d3..8aa910f5d 100644
--- a/docs/known-issues/es/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
+++ b/docs/known-issues/es/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
@@ -22,7 +22,7 @@ Al acceder a una página de producto con variación (más de un SKU) con el par
 
 Sin embargo, si el SKU elegido (Del parámetro) está indisponible (sin stock / no entregable), cuando el usuario selecciona otro SKU disponible en el selector de SKU, no se exhiben las informaciones de precio.
 
-![Precio no actualizado con selección de SKU](//images.contentful.com/alneenqid6w5/1GKcK5NUSoEcmMuesmiGiM/6ddb61d748aa566c6eb5607711a0ae3d/preco.gif)
+![Precio no actualizado con selección de SKU](https://images.contentful.com/alneenqid6w5/1GKcK5NUSoEcmMuesmiGiM/6ddb61d748aa566c6eb5607711a0ae3d/preco.gif)
 
 ## Simulación
 
diff --git a/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
index 825fc6eef..c33f22ff1 100644
--- a/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
@@ -30,5 +30,5 @@ Criar um novo dicionário no Módulo CMS que não possua nenhum Host previamente
 
 Acesse o módulo CMS, clique nos botões lupa e limpar em sequência e o botão adicionar novo host será desbloqueado.
 
-![PT - Criar dicionário não disponibiliza opção de "Add"](//images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
+![PT - Criar dicionário não disponibiliza opção de "Add"](https://images.ctfassets.net/alneenqid6w5/7bUb8P0cVAGpEb2Do9oRLz/f1e0765bbcb26d36981c3fe76d268cd3/image__2_.png)
 
diff --git a/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index 7c748d4a4..06e156e3a 100644
--- a/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/pt/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -31,7 +31,7 @@ Isso ocorria porque o número `1` tinha sido configurado como padrão, mesmo qua
 
 Acesse seu **Admin VTEX > Início > Como melhorar > Catálogo**. Se a seção indicar que há `1` problema encontrado, ao clicar em `Produtos populares sem estoque`, você será redirecionado para a página do Catálogo.
 
-![Como melhorar PT](//images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/0c7b4d56e4f469c92c9cb4568e1b2268/Como_melhorar_PT.png)
+![Como melhorar PT](https://images.ctfassets.net/alneenqid6w5/54P0d7km19QIamqTFa10F6/0c7b4d56e4f469c92c9cb4568e1b2268/Como_melhorar_PT.png)
 
 ## Workaround
 
@@ -39,5 +39,5 @@ Não é necessário que o usuário realize nenhuma ação, pois já corrigimos o
 
 `Não encontramos problemas no seu catálogo.`
 
-![Como melhorar fixed PT](//images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/9db429271ca62c42c8b4fc9fa3f5fe37/Como_melhorar_fixed_PT.png)
+![Como melhorar fixed PT](https://images.ctfassets.net/alneenqid6w5/32jMVhuthv5CUK5oECisEr/9db429271ca62c42c8b4fc9fa3f5fe37/Como_melhorar_fixed_PT.png)
 
diff --git a/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index ea127337e..03783e2f3 100644
--- a/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/pt/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumário
 
-O Campo automático (campo calculado) funciona corretamente quando  "Recalcular esse campo:" é setado para "somente quando inserir registro", mas para de funcionar quando é programado para recalcular "na primeira hora..." e suas variantes.![inline1511102536](//images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
+O Campo automático (campo calculado) funciona corretamente quando  "Recalcular esse campo:" é setado para "somente quando inserir registro", mas para de funcionar quando é programado para recalcular "na primeira hora..." e suas variantes.![inline1511102536](https://images.ctfassets.net/alneenqid6w5/JbRenxvruoyYOueqguwcy/8ae33d07ce4db627a1c45eed5916824e/inline1511102536.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
index 6b9ac42cf..edf04445d 100644
--- a/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
@@ -31,7 +31,7 @@ Basta ter um código de rastreio válido em qualquer pedido. Nos dias seguintes,
 
 É possível enviar atualizações de rastreio via API, mantendo o comportamento do envio de e-mails. O mesmo para a confirmação de entrega, que também pode ser feita pela interface do OMS.
 
-![2017-08-16 195850](//images.contentful.com/alneenqid6w5/1IPsGBnkKYggY8m6smeqOA/a2a95afc6fb34e7bfe89c1cab2fdb612/2017-08-16_195850.jpg)
+![2017-08-16 195850](https://images.contentful.com/alneenqid6w5/1IPsGBnkKYggY8m6smeqOA/a2a95afc6fb34e7bfe89c1cab2fdb612/2017-08-16_195850.jpg)
 
 A confirmação de entrega feita via OMS também é repassada aos marketplaces.
 
diff --git a/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md b/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md
index 3ca3eb934..8704049c5 100644
--- a/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md
+++ b/docs/known-issues/pt/cms-is-not-accessible-through-the-new-admin.md
@@ -20,7 +20,7 @@ internalReference:
 
 Ao acessar o CMS por meio do novo ambiente administrativo (My VTEX - `{AccountName}.myvtex.com/admin`), é apresentada uma página de erro, não sendo possível acessá-lo.
 
-![4JSc1cw](//images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
+![4JSc1cw](https://images.ctfassets.net/alneenqid6w5/2SQ58O96w0u668aoMgeygI/2fe3498d2cade6d204c2b2b67e0be9b0/4JSc1cw.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/creating-or-editing-list-type-does-not-work.md b/docs/known-issues/pt/creating-or-editing-list-type-does-not-work.md
index 4cf82ed64..395c4a169 100644
--- a/docs/known-issues/pt/creating-or-editing-list-type-does-not-work.md
+++ b/docs/known-issues/pt/creating-or-editing-list-type-does-not-work.md
@@ -20,7 +20,7 @@ internalReference:
 
 Na tela de Tipos de Lista, ao clicar em "Ver Detalhes" ou "Novo Tipo de Lista" não está sendo possível criar/alterar o Tipo de Lista.
 
-![Criação de Tipo de Lista](//images.contentful.com/alneenqid6w5/3dmnyQDRyMc8guqw8m8EOc/b6192d84ade5e8990990d170ac4614d2/1.png)
+![Criação de Tipo de Lista](https://images.contentful.com/alneenqid6w5/3dmnyQDRyMc8guqw8m8EOc/b6192d84ade5e8990990d170ac4614d2/1.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/crm-error-when-searching-with-spaces.md b/docs/known-issues/pt/crm-error-when-searching-with-spaces.md
index 7fd3a1c91..c5cd75265 100644
--- a/docs/known-issues/pt/crm-error-when-searching-with-spaces.md
+++ b/docs/known-issues/pt/crm-error-when-searching-with-spaces.md
@@ -18,7 +18,7 @@ internalReference:
 
 ## Sumário
 
-Usuário recebe uma mensagem de erro ao buscar por um documento com um atributo contendo espaço [Screen Shot 2018-12-26 at 14.38.55](//images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
+Usuário recebe uma mensagem de erro ao buscar por um documento com um atributo contendo espaço [Screen Shot 2018-12-26 at 14.38.55](https://images.ctfassets.net/alneenqid6w5/6kN77jtFDOKME8UiW0acW8/e3bc9a3bcb750f30067f11befdd78fcb/Screen_Shot_2018-12-26_at_14.38.55.png)
 
 
 Exemplo:  Buscando/filtrando pelo Campo "Cidade" com o atributo "Rio de Janeiro" produzirá uma mensagem de erro.
@@ -32,6 +32,6 @@ Exemplo:  Buscando/filtrando pelo Campo "Cidade" com o atributo "Rio de Janeiro"
 
 ## Workaround
 
-![Screen Shot 2018-12-26 at 14.40.03](//images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)Felizmente ha um workaround simples que não necessita o uso da API.
+![Screen Shot 2018-12-26 at 14.40.03](https://images.ctfassets.net/alneenqid6w5/1LUggCuWywGosGoCOgKE2g/426a9dbd86c26f15a9db06cadb88ec46/Screen_Shot_2018-12-26_at_14.40.03.png)Felizmente ha um workaround simples que não necessita o uso da API.
 Ao clicar em "Todos" no dropdown, a mesma busca pode ser feita sem causar erro.
 
diff --git a/docs/known-issues/pt/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md b/docs/known-issues/pt/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
index bbf3622bc..8072303f9 100644
--- a/docs/known-issues/pt/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
+++ b/docs/known-issues/pt/customer-giftcard-not-located-in-the-administrative-module-when-performing--cpf-query.md
@@ -20,7 +20,7 @@ internalReference:
 
 Ao realizar uma consulta de vales, no admin, por CPF (documento), o vale do cliente não é listado.
 
-![vale](//images.contentful.com/alneenqid6w5/78Mt2DDgaIwg2I66gSYGgM/66de95f8e3b3b73d20a0165f4da67f88/vale.png)
+![vale](https://images.contentful.com/alneenqid6w5/78Mt2DDgaIwg2I66gSYGgM/66de95f8e3b3b73d20a0165f4da67f88/vale.png)
 
 ## Simulação
 
@@ -41,5 +41,5 @@ Para consultar um CPF sem pontos e hífen (criados por API), então:
 2. Remova os pontos e o hífen;
 3. Clique em "Buscar";
 
-![vale animado](//images.contentful.com/alneenqid6w5/p5ybSG51tYmIe2qCu2GGg/2c68720ce41c517630b7049c49daf3f9/vale.gif)
+![vale animado](https://images.contentful.com/alneenqid6w5/p5ybSG51tYmIe2qCu2GGg/2c68720ce41c517630b7049c49daf3f9/vale.gif)
 
diff --git a/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md b/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md
index 74b242838..24f0b10ce 100644
--- a/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md
+++ b/docs/known-issues/pt/divergence-between-total-order-value-and-total-products-value.md
@@ -26,7 +26,7 @@ O pedido é fechado e transacionado normalmente na VTEX mas, dependendo dos flux
 
 Exemplo de ocorrência:
 
-![image](//images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/4sJOKvC97OggkWYoCQaa6G/c6b38b60fc500436bb36a5ae6409094e/image.png)
 
 Nesse caso, o valor total do pedido cobrado do cliente ficou em `R$ 7,98`. No entanto, ao somar os valores de venda registrados em cada produto, o total seria de `R$ 7,95`.
 
diff --git a/docs/known-issues/pt/encoding-error-in-apple-mail-app.md b/docs/known-issues/pt/encoding-error-in-apple-mail-app.md
index 5c32b2596..a35041a17 100644
--- a/docs/known-issues/pt/encoding-error-in-apple-mail-app.md
+++ b/docs/known-issues/pt/encoding-error-in-apple-mail-app.md
@@ -29,7 +29,7 @@ Montar um trigger de envio de e-mail que possua caracter especial no "Assunto" d
 
 Resultado:
 
-![png](//images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
+![png](https://images.ctfassets.net/alneenqid6w5/2O4zWlYa1WoaQ0sUMUKS2Q/2862790a2e5124fcb612a7f17774a339/png.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md b/docs/known-issues/pt/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md
index c09b18c52..2f0f57106 100644
--- a/docs/known-issues/pt/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md
+++ b/docs/known-issues/pt/error-400-bad-request-when-accessing-filter-page-with-special-character-in-value.md
@@ -20,7 +20,7 @@ internalReference:
 
 Ao aplicar um filtro por especificação (menu lateral) com caracter especial, o sistema retorna tela branca com o seguinte erro 400: "Bad Request! Scripts are not allowed!"
 
-![Filtro com erro 400](//images.contentful.com/alneenqid6w5/zFVBtySVCoYSoCqEQioOw/b0ac0afcad2eb753d0c02cf14850e087/erro_400.png)
+![Filtro com erro 400](https://images.contentful.com/alneenqid6w5/zFVBtySVCoYSoCqEQioOw/b0ac0afcad2eb753d0c02cf14850e087/erro_400.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md b/docs/known-issues/pt/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
index d8d211570..e83de0115 100644
--- a/docs/known-issues/pt/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
+++ b/docs/known-issues/pt/error-sending-skus-from-sellers-to-marketplaces-and-vice-versa.md
@@ -22,7 +22,7 @@ As lojas VTEX podem se tornar [sellers](https://help.vtex.com/pt/tutorial/estrat
 
 Isso acontece porque produtos que são vendidos tanto pelo marketplace como pelos seus sellers não são reconhecidos pelo sistema ao serem enviados. Só é possível enviar produtos que são vendidos por apenas uma das lojas.
 
-![arquitetura circular](//images.contentful.com/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/371206531ea37589ffe30f7c0db64b57/arquitetura_circular.JPG)
+![arquitetura circular](https://images.contentful.com/alneenqid6w5/56mCQjosVr8YmmMpcv67gj/371206531ea37589ffe30f7c0db64b57/arquitetura_circular.JPG)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
index 010cc365d..50a9b8c04 100644
--- a/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
@@ -29,7 +29,7 @@ A mensagem de autorização de erro pode mudar de `node` para `react` de acordo
 1. Instalar o VTEX CLI (ToolBelt)
 2. Navegar até o diretorio da app
 3. Executar o comando "vtex-link" no terminal
-4. ![image (8)](//images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
+4. ![image (8)](https://images.ctfassets.net/alneenqid6w5/3NTzMXCKgM8GA6Y6eEKAA2/7d11d9a4e05ef1274beebe494bd8baf9/image__8_.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md b/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md
index c4067fbdb..249253ace 100644
--- a/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md
+++ b/docs/known-issues/pt/fields-not-marked-as-mandatory-in-master-data-lead-to-checkout-error.md
@@ -22,7 +22,7 @@ Ao obter os endereços que um cliente pode ter, o checkout não está validando
 
 Mensagem: Não são permitidos múltiplos países nos endereços
 Vale lembrar que, na entidade de dados "endereços" (AD), dentro do Master Data, esses campos são abertos, ou seja, podem ser colocados como não obrigatórios, e podem estar vazios. Então, nos momentos em que esta informação é alimentada por meio de integrações (usando nossas APIs), a porta se abre para ter registros que não possuem, por exemplo, os dados de "País", terminando no erro mencionado acima.
-![image1](//images.ctfassets.net/alneenqid6w5/3eMExnt2FHAFOsBEt4nldh/80f92f5e5f02611d394cf3e1037a6865/image1.png)
+![image1](https://images.ctfassets.net/alneenqid6w5/3eMExnt2FHAFOsBEt4nldh/80f92f5e5f02611d394cf3e1037a6865/image1.png)
 
 __Comportamento esperado__
 
@@ -35,10 +35,10 @@ O checkout recebe as informações dos endereços que estão associados ao dito
 As opções são mostradas e, apesar de não ter os dados do país dentro do JSON (country) do OrderForm (selectedAddresses.[0].country), na interface do usuário, os endereços mostram o país. Isto significa que o cliente ou o gerente da loja não pode perceber facilmente que algumas informações críticas são necessárias para continuar a compra.
 
 __JSON__
-![image2](//images.ctfassets.net/alneenqid6w5/4uAXxjyD8rI8hdA0fq5T5B/d45c179e4038ca6be57883d307228cf6/image2.png)
+![image2](https://images.ctfassets.net/alneenqid6w5/4uAXxjyD8rI8hdA0fq5T5B/d45c179e4038ca6be57883d307228cf6/image2.png)
 
 __Checkout UI__
-![image3](//images.ctfassets.net/alneenqid6w5/5Q1zZJRzUxPIziPp0Giqy3/79d822c3e9d6042e7399c6fa53958d47/image3.png)
+![image3](https://images.ctfassets.net/alneenqid6w5/5Q1zZJRzUxPIziPp0Giqy3/79d822c3e9d6042e7399c6fa53958d47/image3.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md b/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md
index 86952e551..e387190ce 100644
--- a/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md
+++ b/docs/known-issues/pt/geolocation-search-for-pickup-points-loading-indefinitely.md
@@ -35,7 +35,7 @@ Se a localização do seu navegador satisfaz a condição acima, siga com estes
 5. Durante o checkout, selecione a opção de entrega: ponto de retirada. 
 6. Verifique que a tela apresenta uma mensagem contínua sobre carregamento da localização.
 
-![erro PT](//images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/c3a49aa994fb5e5042a0d5a06f40c336/erro_PT.png)
+![erro PT](https://images.ctfassets.net/alneenqid6w5/4MVL2ctjpB3TRIfQt1ht3O/c3a49aa994fb5e5042a0d5a06f40c336/erro_PT.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md b/docs/known-issues/pt/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
index dc202f19f..f82e3a525 100644
--- a/docs/known-issues/pt/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
+++ b/docs/known-issues/pt/inconsistency-in-the-quantity-of-items-with-assembly-options-in-the-cart.md
@@ -28,7 +28,7 @@ Nos produtos com customização do Assembly options, um item pai possui componen
 3. Selecione o item filho do produto, na mesma quantidade;
 4. Confira os itens no carrinho de compras.
 
-![KI assembly](//images.contentful.com/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/b2d02da26c27f468b43e32e0d3a81f61/KI_assembly.png)
+![KI assembly](https://images.contentful.com/alneenqid6w5/1xmOq4gUrxUjJLMMox7WQj/b2d02da26c27f468b43e32e0d3a81f61/KI_assembly.png)
 Observe que o carrinho contém uma unidade a mais do item filho em relação ao item pai.
 
 
diff --git a/docs/known-issues/pt/inconsistent-shipping-calculator.md b/docs/known-issues/pt/inconsistent-shipping-calculator.md
index e20f7781e..21d128a0e 100644
--- a/docs/known-issues/pt/inconsistent-shipping-calculator.md
+++ b/docs/known-issues/pt/inconsistent-shipping-calculator.md
@@ -24,7 +24,7 @@ Nestes casos, o calculador de frete tem comportamento inconsistente, exibindo do
 
 Isso acontece somente na versão 5 do checkout.
 
-![image](//images.ctfassets.net/alneenqid6w5/5jaAAeUm9q4c4oy6GcYeO6/c08fe588cedc9d9a30453985a1589df9/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/5jaAAeUm9q4c4oy6GcYeO6/c08fe588cedc9d9a30453985a1589df9/image.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/incorrect-canonical-tag-on-https-pages.md b/docs/known-issues/pt/incorrect-canonical-tag-on-https-pages.md
index e21c3afee..e49f9169d 100644
--- a/docs/known-issues/pt/incorrect-canonical-tag-on-https-pages.md
+++ b/docs/known-issues/pt/incorrect-canonical-tag-on-https-pages.md
@@ -25,7 +25,7 @@ Ao ativar o HTTPS em uma pasta específica, a tag HTML _canonical_ permanece ren
 1. Ativar HTTPS em uma única pasta do site ([guia](https://help.vtex.com/tutorial/--frequentlyAskedQuestions_4378));
 2. Verificar, no HTML renderizado, a tag _canonical_.
 
-![image](//images.contentful.com/alneenqid6w5/5B2i3p2lva8OO0I4geI8Qw/7321c0d4c0a2f8d20a7940ace91bcbff/image.png)
+![image](https://images.contentful.com/alneenqid6w5/5B2i3p2lva8OO0I4geI8Qw/7321c0d4c0a2f8d20a7940ace91bcbff/image.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/layout-malfunctions-when-adding-or-removing-a-filter.md b/docs/known-issues/pt/layout-malfunctions-when-adding-or-removing-a-filter.md
index c7b5edba1..8e598db72 100644
--- a/docs/known-issues/pt/layout-malfunctions-when-adding-or-removing-a-filter.md
+++ b/docs/known-issues/pt/layout-malfunctions-when-adding-or-removing-a-filter.md
@@ -30,5 +30,5 @@ Ao adicionar/retirar filtro dentro da página de Cadastro de Produtos e Skus oco
 
 Você deve clicar onde ficava *Filtrar resultados ou fazer uma busca* e depois clicar no botão azul no canto esquerdo inferior, com isso o layout da página será normalizado.
 
-![Image](//images.contentful.com/alneenqid6w5/2HUT45Pgcgqack2CMg22ug/0073487d59c786e3f959e608f9015e38/Exemplo.jpg)
+![Image](https://images.contentful.com/alneenqid6w5/2HUT45Pgcgqack2CMg22ug/0073487d59c786e3f959e608f9015e38/Exemplo.jpg)
 
diff --git a/docs/known-issues/pt/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md b/docs/known-issues/pt/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
index 64e676c2a..ca9809a31 100644
--- a/docs/known-issues/pt/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
+++ b/docs/known-issues/pt/marketplace-doesnt-consider-installment-rule-for-products-that-have-a-commercial-condition-in-the-seller.md
@@ -25,10 +25,10 @@ Essa funcionalidade é comumente usada para criar cenários como este: a geladei
 O problema conhecido fica evidente no seguinte exemplo, em que o marketplace não consegue refletir as mesmas regras de parcelamento que o seller:
 
 ## Marketplace - Até 12x sem juros
-![Geladeira Marketplace](//images.contentful.com/alneenqid6w5/c7CtSlVToIIQScyiM4AiS/e9f1415ccbe79d8fe34af8e9901b6570/Geladeira_Marketplace.png)
+![Geladeira Marketplace](https://images.contentful.com/alneenqid6w5/c7CtSlVToIIQScyiM4AiS/e9f1415ccbe79d8fe34af8e9901b6570/Geladeira_Marketplace.png)
 
 ## Seller - Até 10x sem juros
-![2017-06-16 18 15 44-Geladeira 540 Litros Evox Brastemp Side Inverse - Brastemp](//images.contentful.com/alneenqid6w5/6HZs1prIVaUsOYCWeEMG8U/169a380f8e4c43cd0c644d280da0d126/2017-06-16_18_15_44-Geladeira_540_Litros_Evox_Brastemp_Side_Inverse_-_Brastemp.png)
+![2017-06-16 18 15 44-Geladeira 540 Litros Evox Brastemp Side Inverse - Brastemp](https://images.contentful.com/alneenqid6w5/6HZs1prIVaUsOYCWeEMG8U/169a380f8e4c43cd0c644d280da0d126/2017-06-16_18_15_44-Geladeira_540_Litros_Evox_Brastemp_Side_Inverse_-_Brastemp.png)
 
 A exibição no marketplace está errada. Os parcelamentos em 11x e 12x não exibem juros, quando, na realidade, deveriam exibir.
 
diff --git a/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md b/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
index 1a7e55fa7..94fbd2e1b 100644
--- a/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
+++ b/docs/known-issues/pt/misconfigured-vtable-app-breaks-other-apps-of-the-same-type.md
@@ -29,9 +29,9 @@ Principais causas de uma app mal configurada:
 
 No caso de um JSON Schema inexistente, coloque no campo `model` o nome correto do JSON Schema.
 
-Por exemplo: ![Screen Shot 2019-01-03 at 19.31.53](//images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
+Por exemplo: ![Screen Shot 2019-01-03 at 19.31.53](https://images.ctfassets.net/alneenqid6w5/EVwmyhWMmGmcs2Y8wEQiw/ddbf9f821818f2c061a5f262ee43e675/Screen_Shot_2019-01-03_at_19.31.53.png)
 
-Observe como a borda da app fica vermelha e a mensagem de erro no console indica o erro "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](//images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
+Observe como a borda da app fica vermelha e a mensagem de erro no console indica o erro "Error to get jsonschema by name": ![Screen Shot 2019-01-03 at 19.24.22](https://images.ctfassets.net/alneenqid6w5/62I23QUXPauQGGcUcoCucK/b484536ae3e462823b7715ff52a737ea/Screen_Shot_2019-01-03_at_19.24.22.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/my-orders-layout-breaking-without-customization.md b/docs/known-issues/pt/my-orders-layout-breaking-without-customization.md
index 94d729d4c..8fab3802e 100644
--- a/docs/known-issues/pt/my-orders-layout-breaking-without-customization.md
+++ b/docs/known-issues/pt/my-orders-layout-breaking-without-customization.md
@@ -26,7 +26,7 @@ internalReference:
 ---
 
 
-![Screen Shot 2017-05-26 at 12.01.58](//images.contentful.com/alneenqid6w5/qUqOq8ZyGOCAAoiUM0600/66a6bf0fa60bbd65fa9abd1ca7c825ae/Screen_Shot_2017-05-26_at_12.01.58.png)
+![Screen Shot 2017-05-26 at 12.01.58](https://images.contentful.com/alneenqid6w5/qUqOq8ZyGOCAAoiUM0600/66a6bf0fa60bbd65fa9abd1ca7c825ae/Screen_Shot_2017-05-26_at_12.01.58.png)
 
 Se o layout do novo Meus Pedidos apresentar problemas em sua loja _out of the box_, sem nenhuma customização, pode ser que o CSS de sua loja esteja interferindo com ele.
 
diff --git a/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md b/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
index 773d88ae3..4a1dc54d4 100644
--- a/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
+++ b/docs/known-issues/pt/nif-field-at-checkout-in-portugal-allows-special-characters-and-causes-problem-in-order-flow.md
@@ -20,7 +20,7 @@ internalReference:
 
 O campo NIF (document) do checkout de Portugal (UI) está permitindo entrada de caracteres especiais nos seus valores. No entanto, os pedidos que forem fechados com caracteres especiais ficam travados com erro no OMS.
 
-![OMS](//images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
+![OMS](https://images.ctfassets.net/alneenqid6w5/19LgQNhPlIIAoA62k06ac2/2b394138cd21e4ad76c21e0ea871417f/OMS.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md b/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md
index bd3131684..235334f13 100644
--- a/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md
+++ b/docs/known-issues/pt/ordering-of-delivery-times-scheduled-at-checkout.md
@@ -20,7 +20,7 @@ internalReference:
 
 Atualmente os horários de entrega para uma entrega agendada estão fora de ordem, ou em ordenação decrescente. Para melhor legibilidade, é esperado que estas informações sejam ordenadas de forma crescente.
 
-![image](//images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/dpGWYjydIAiC2i4qEigsm/0334f47a61fa7dcc4defe1cde08d616b/image.png)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md b/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md
index 585740ae2..8a06df005 100644
--- a/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md
+++ b/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md
@@ -24,7 +24,7 @@ Alguns pedidos no Gerenciamento de Pedidos ficam parados no status "Processando"
 
 Este erro é intermitente, sendo muito difícil sua simulação. A seguir, temos a imagem do log de quando este erro ocorre.
 
-![erro-sistema-de-perfis](//images.contentful.com/alneenqid6w5/3XS6EnP8kU8W2SewuYsAes/503ce84831f50a80f57bc31a713a71c7/erro-sistema-de-perfis.png)
+![erro-sistema-de-perfis](https://images.contentful.com/alneenqid6w5/3XS6EnP8kU8W2SewuYsAes/503ce84831f50a80f57bc31a713a71c7/erro-sistema-de-perfis.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md b/docs/known-issues/pt/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
index 1ae9b1f4c..d14899333 100644
--- a/docs/known-issues/pt/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
+++ b/docs/known-issues/pt/pci-logs-are-no-longer-displayed-on-the-orders-managment-timeline.md
@@ -24,7 +24,7 @@ Na linha do tempo, encontrada no detalhe do pedido (Gerenciamento de Pedidos), n
 
 - Selecione um pedido antigo (por exemplo, de junho de 2017).
 
-![pedido com log pci](//images.contentful.com/alneenqid6w5/1OflzCTMYcQwkgcWUCkwIC/6a4dc455400128870cd4790fa3ff3372/com_log.PNG)
+![pedido com log pci](https://images.contentful.com/alneenqid6w5/1OflzCTMYcQwkgcWUCkwIC/6a4dc455400128870cd4790fa3ff3372/com_log.PNG)
 
 - Compare-o com um pedido atual.
 - Veja que não aparecerão as informações do PCI sobre Antifraude, que mostramos como exemplo.
diff --git a/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md b/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md
index 060c8e125..9e74eee40 100644
--- a/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md
+++ b/docs/known-issues/pt/pickup-point-disregarded-based-on-priority.md
@@ -39,7 +39,7 @@ Para que a simulação apresente o cenário descrito, é preciso que estejam cad
 4. Veja qual ponto de retirada foi selecionado;
 5. Confira quais pontos de retirada foram descartados e observe a mensagem apresentada.
 
-![KIpontoderetirada PT](//images.contentful.com/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/cb91079a96bb328efd04b1e81960343c/KIpontoderetirada_PT.png)
+![KIpontoderetirada PT](https://images.contentful.com/alneenqid6w5/6TLSPTSA7E5EG2sevnDYXf/cb91079a96bb328efd04b1e81960343c/KIpontoderetirada_PT.png)
 
 O ponto de retirada foi desconsiderado porque havia outro método de envio já nomeado como **SCS Mall**.
 
diff --git a/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index a03f1d98d..be7ca6043 100644
--- a/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -21,7 +21,7 @@ internalReference:
 Atualmente, o cenário de exibição das opções "Receber | Retirar" é condicionado ao CEP buscado em qualquer uma das abas. Isso significa que, se na aba de "Receber" for buscado um CEP que não é atendido por um ponto de retirada, a aba "Retirar" não será exibida ao usuário.
 
 
-![Captura de Tela 2018-11-21 às 14.25.40](//images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
+![Captura de Tela 2018-11-21 às 14.25.40](https://images.ctfassets.net/alneenqid6w5/5kj7LZNmpiMsum4OSUc8mC/575006d7f6b4ad87dbeb60dea57b191c/Captura_de_Tela_2018-11-21_a__s_14.25.40.png) 
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md b/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md
index 4c1145f0e..6901f7be8 100644
--- a/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md
+++ b/docs/known-issues/pt/reserved-stock-in-invoiced-orders.md
@@ -24,7 +24,7 @@ Isso acontece quando o pedido está no status `Pronto para manuseio` e o cliente
 
 Exemplo com o fluxo do pedido:
 
-![2017-06-13 182850](//images.contentful.com/alneenqid6w5/5Skd8YsCcMIicCcEGyoqwG/1a1a839dc36cdb9f818240b68817de3e/2017-06-13_182850.jpg)
+![2017-06-13 182850](https://images.contentful.com/alneenqid6w5/5Skd8YsCcMIicCcEGyoqwG/1a1a839dc36cdb9f818240b68817de3e/2017-06-13_182850.jpg)
 
 Na etapa circulada do fluxo do pedido, o produto é faturado sem o reconhecimento da reserva.
 
diff --git a/docs/known-issues/pt/schema-doesnt-present-price-in-outofstock-items-unavailable.md b/docs/known-issues/pt/schema-doesnt-present-price-in-outofstock-items-unavailable.md
index fde0ddad4..607e3b0ef 100644
--- a/docs/known-issues/pt/schema-doesnt-present-price-in-outofstock-items-unavailable.md
+++ b/docs/known-issues/pt/schema-doesnt-present-price-in-outofstock-items-unavailable.md
@@ -24,7 +24,7 @@ Produtos indisponíveis ( outOfstock ) não possuem a informação de preço no
 
 - Pegue um item sem estoque que esteja sendo exibido no site como indisponível
 - Veja no Schema que ele estará impresso como  outOfstock e não exibe o preço.
-![schema  outOfstock ](//images.contentful.com/alneenqid6w5/6PgCuzUXXGo0iC6UeAMUA6/4390b013aaf5d3083ffef407180cd484/ItemTypes-duplicidade.png)
+![schema  outOfstock ](https://images.contentful.com/alneenqid6w5/6PgCuzUXXGo0iC6UeAMUA6/4390b013aaf5d3083ffef407180cd484/ItemTypes-duplicidade.png)
 
 
 
diff --git a/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md b/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md
index 0731426a4..02c9907cb 100644
--- a/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md
+++ b/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md
@@ -24,7 +24,7 @@ internalReference:
 
 Quando o usuário realiza uma busca por termo e, em seguida, aplica um filtro nas opções de multi seleção (no controle searchNavigator), o termo buscado inicialmente é removido da consulta, ou seja, o filtro ignora o termo e aplica a busca somente com as opções escolhidas pelo usuário.
 
-![search result](//images.contentful.com/alneenqid6w5/6BZ5Xh6OHe8WSWywOQCKGw/e814ecd5db35ff565151876dd8f826d5/search_result.gif)
+![search result](https://images.contentful.com/alneenqid6w5/6BZ5Xh6OHe8WSWywOQCKGw/e814ecd5db35ff565151876dd8f826d5/search_result.gif)
 
 ## Simulação
 
diff --git a/docs/known-issues/pt/system-allows-the-user-to-change-a-main-web-site-generating-errors.md b/docs/known-issues/pt/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
index 90f759d50..81c0288c7 100644
--- a/docs/known-issues/pt/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
+++ b/docs/known-issues/pt/system-allows-the-user-to-change-a-main-web-site-generating-errors.md
@@ -22,7 +22,7 @@ No módulo CMS, o sistema deixa o usuário manusear um Web Site A e apontar a um
 
 Caso o usuário queira retornar, nao há a possibilidade de apontar o Web Site B para o A, como pai. Com isso, gera erros no site como o erro abaixo, e o admin fica inacessível.
 
-![KI erro website](//images.contentful.com/alneenqid6w5/17hdmuW8qis8kyKUs6e8SG/2234b8f8916038ce6e8ccf98b6ff14a9/KI_erro_website.png)
+![KI erro website](https://images.contentful.com/alneenqid6w5/17hdmuW8qis8kyKUs6e8SG/2234b8f8916038ce6e8ccf98b6ff14a9/KI_erro_website.png)
 
 
 ## Simulação
@@ -32,7 +32,7 @@ Caso o usuário queira retornar, nao há a possibilidade de apontar o Web Site B
 - No primeiro Web Site > campo Web Site Pai, inserir o Web Site referente ao Web Site 2;
 - No segundo Web Site > campo Web Site Pai, inserir o Web Site referente ao Web Site 1.
 
-![KI erro website2](//images.contentful.com/alneenqid6w5/a6SpuvdBT2KOIiaSO6EGq/e98a7e9081262e773f63f165f7344ecc/KI_erro_website2.png)
+![KI erro website2](https://images.contentful.com/alneenqid6w5/a6SpuvdBT2KOIiaSO6EGq/e98a7e9081262e773f63f165f7344ecc/KI_erro_website2.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/the-product-information-button-does-not-display-the-data.md b/docs/known-issues/pt/the-product-information-button-does-not-display-the-data.md
index b0cc4e740..426081d91 100644
--- a/docs/known-issues/pt/the-product-information-button-does-not-display-the-data.md
+++ b/docs/known-issues/pt/the-product-information-button-does-not-display-the-data.md
@@ -22,11 +22,11 @@ O botão <i class="fas fa-info-circle"></i> disponível na listagem de **Produto
 
 **Produto não disponível**
 
-![info vazia](//images.contentful.com/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/762ff4e2e1986c8438c5c1f2ee2f9a29/image.png)
+![info vazia](https://images.contentful.com/alneenqid6w5/7KB0N2iRtVhLHkGNx3phPh/762ff4e2e1986c8438c5c1f2ee2f9a29/image.png)
 
 **Produto disponível**
 
-![info preenchida](//images.contentful.com/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/d71ae910c0726c0643a5f7ad9e6f7e52/image.png)
+![info preenchida](https://images.contentful.com/alneenqid6w5/4TsjOjvtlZ6gn8k26X0Vpr/d71ae910c0726c0643a5f7ad9e6f7e52/image.png)
 
 ## Simulação
 
@@ -43,5 +43,5 @@ O botão <i class="fas fa-info-circle"></i> disponível na listagem de **Produto
 4. Clique no botão `Indexed Info`.
 5. Verifique as informações do SKU no item Sales Channel como mostrado na imagem abaixo.
 
-![indexed info](//images.contentful.com/alneenqid6w5/7oC2oM6doEqm0pXVAN6Y6u/558f152a4d9c05442178db25e1e4c582/image.png)
+![indexed info](https://images.contentful.com/alneenqid6w5/7oC2oM6doEqm0pXVAN6Y6u/558f152a4d9c05442178db25e1e4c582/image.png)
 
diff --git a/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md b/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md
index e6d7d42cb..efe9030f4 100644
--- a/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md
+++ b/docs/known-issues/pt/transactional-emails-dont-consider-items-removed-from-the-order.md
@@ -19,10 +19,10 @@ internalReference:
 ## Sumário
 
 Quando um item é removido do pedido:
-![item removido](//images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
+![item removido](https://images.ctfassets.net/alneenqid6w5/6Z4eZwTaE00c4IoWWwgoAE/c280b06fb2912bad51afceac5db4c4d0/tozOd3.jpg)
 
 O email transacional não considera o item removido e apresenta os dois itens no e-mail:
-![email transacional](//images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
+![email transacional](https://images.ctfassets.net/alneenqid6w5/77NEYq80oM6Umm44KO8Uc/625b13837f9ff4b4333e2e28a0745431/zbXg5s.jpg)
 
 
 
diff --git a/docs/known-issues/pt/unable-to-delete-templates-on-legacy-cms.md b/docs/known-issues/pt/unable-to-delete-templates-on-legacy-cms.md
index 5411e98a1..2e37de739 100644
--- a/docs/known-issues/pt/unable-to-delete-templates-on-legacy-cms.md
+++ b/docs/known-issues/pt/unable-to-delete-templates-on-legacy-cms.md
@@ -28,11 +28,11 @@ Os clientes não conseguem excluir templates do CMS antigo.
 4. Clique na pasta **HTML Templates**.
 5. Clique no botão `delete` em qualquer template.
 
-![HTML templates](//images.contentful.com/alneenqid6w5/6PWmj8jj0YJyi0tJ2h1Ay5/788bfa080f071df9f16adb8a1e7af67d/image.png)
+![HTML templates](https://images.contentful.com/alneenqid6w5/6PWmj8jj0YJyi0tJ2h1Ay5/788bfa080f071df9f16adb8a1e7af67d/image.png)
 
 Quando você tenta excluir um template, a seguinte mensagem é exibida:
 
-![Messagem CMS](//images.contentful.com/alneenqid6w5/579ZOpaYA2XeRW60bXcVow/7f915c8ec079be49f159c4f8a959efa1/image.png)
+![Messagem CMS](https://images.contentful.com/alneenqid6w5/579ZOpaYA2XeRW60bXcVow/7f915c8ec079be49f159c4f8a959efa1/image.png)
 
 ## Workaround
 
diff --git a/docs/known-issues/pt/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md b/docs/known-issues/pt/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
index b91521f25..8749dc800 100644
--- a/docs/known-issues/pt/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
+++ b/docs/known-issues/pt/uploading-more-than-one-existing-file-at-a-time-does-not-update-all-files-in-file-manager.md
@@ -32,7 +32,7 @@ Ao enviar simultaneamente dois ou mais arquivos existentes no File Manager, apen
 
 Depois disso, você receberá o seguinte aviso:
 
-![File manager](//images.contentful.com/alneenqid6w5/4Z7tY3FKCDV1Cz6Whji6HI/d730b6accf6caeb81b373745b20c337d/image.png)
+![File manager](https://images.contentful.com/alneenqid6w5/4Z7tY3FKCDV1Cz6Whji6HI/d730b6accf6caeb81b373745b20c337d/image.png)
 
 Isto significa que apenas um arquivo é identificado; os outros não estão sendo validados. Todos os arquivos são carregados, mas apenas um substituirá sua versão anterior.
 
diff --git a/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 3caf89d8d..03de1111b 100644
--- a/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -41,5 +41,5 @@ Não se preocupe: desligar essa opção não significa que sua loja estará desp
 Se após estes passos o seu Admin ou loja ainda não carregarem, sugerimos que tente acessá-lo com outro navegador. 
 </div>  
 
-![Firefox bug PT](//images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/4ec41440848f1adad3924c07d5154369/Firefox_bug_PT.jpg)
+![Firefox bug PT](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/4ec41440848f1adad3924c07d5154369/Firefox_bug_PT.jpg)
 
diff --git a/docs/known-issues/pt/website-binding-with-old-license-manager-details.md b/docs/known-issues/pt/website-binding-with-old-license-manager-details.md
index 3cbd7fcd3..498dded69 100644
--- a/docs/known-issues/pt/website-binding-with-old-license-manager-details.md
+++ b/docs/known-issues/pt/website-binding-with-old-license-manager-details.md
@@ -29,13 +29,13 @@ O exemplo da loja __Delacasa__ ilustra o bug:
 Antes de se chamar __delacasa__ haviam criado o domínimo __decoramovel__, o Portal criou o Binding e posteriormente adicionou as novas informações do novo domínio no mesmo Binding.
 
 As novas informações inseridas no LM:
-![license-manager-delacasa](//images.contentful.com/alneenqid6w5/6rC1pqQuQ0yeI60YqqS0Si/2d0cf344afd3f7cea14cf844ea86329b/license-manager-delacasa.JPG) 
+![license-manager-delacasa](https://images.contentful.com/alneenqid6w5/6rC1pqQuQ0yeI60YqqS0Si/2d0cf344afd3f7cea14cf844ea86329b/license-manager-delacasa.JPG) 
 
 O dicionário do Website (mundinho) como ficou, deixando o comportamento em evidência:
-![dicionario-delacasa](//images.contentful.com/alneenqid6w5/2w9Zf8aK1aw0euMsSouUEm/59b5b620f7c36f52f81af250be71b542/dicionario-delacasa.JPG) 
+![dicionario-delacasa](https://images.contentful.com/alneenqid6w5/2w9Zf8aK1aw0euMsSouUEm/59b5b620f7c36f52f81af250be71b542/dicionario-delacasa.JPG) 
 
 A parte de Webiste Binding que mostra o resultado:
-![binding-delacasa](//images.contentful.com/alneenqid6w5/4JqhEdsgdGWgo2QOCksUaM/bc67aa1883df5f8827d399f4e89fc123/binding-delacasa.JPG)
+![binding-delacasa](https://images.contentful.com/alneenqid6w5/4JqhEdsgdGWgo2QOCksUaM/bc67aa1883df5f8827d399f4e89fc123/binding-delacasa.JPG)
 
 ## Simulação
 
@@ -53,5 +53,5 @@ O novo Binding irá carregar as informações novas.
 Após criar o novo, fazer a mudança e posteriormente, se necessário, excluir o antigo.
 
 Importante manter essa ordem, para evitar que o site saia do ar.
-![2017-04-10 10 40 41-Index](//images.contentful.com/alneenqid6w5/Jvzm768i64YeqQkqCYAWk/3261595cb7f9af998aac4f0c99fe3fb6/2017-04-10_10_40_41-Index.png)
+![2017-04-10 10 40 41-Index](https://images.contentful.com/alneenqid6w5/Jvzm768i64YeqQkqCYAWk/3261595cb7f9af998aac4f0c99fe3fb6/2017-04-10_10_40_41-Index.png)
 
diff --git a/docs/known-issues/pt/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md b/docs/known-issues/pt/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
index 085ce7677..82ad1a3b7 100644
--- a/docs/known-issues/pt/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
+++ b/docs/known-issues/pt/when-a-schedule-price-expires-the-fixed-price-is-not-reenabled.md
@@ -20,7 +20,7 @@ internalReference:
 
 Contamos com dois preços: um preço fixo que sempre permanece vigente e um preço agendado que tem validade para uma faixa limitada de datas, que estará ativo juntamente com o preço fixo.
 
-![precio-agendado-no-reactiva](//images.contentful.com/alneenqid6w5/28x1hbS9l2QgsyIcYyUoSM/bf1eecf7c1a429f8fc0070040f6fc2ac/precio-agendado-no-reactiva.png)
+![precio-agendado-no-reactiva](https://images.contentful.com/alneenqid6w5/28x1hbS9l2QgsyIcYyUoSM/bf1eecf7c1a429f8fc0070040f6fc2ac/precio-agendado-no-reactiva.png)
 
 Quando o preço agendado é atingido, deveria reativar o preço fixo, já que será o novo e único preço válido para esse SKU. Esta reativação ocorre para a maioria dos preços, mas não está ocorrendo em todos os casos e o produto fica publicado na web, geralmente com um preço mais econômico do que o preço fixo que não foi reativado automaticamente.
 
diff --git a/docs/known-issues/pt/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md b/docs/known-issues/pt/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
index cd9180046..b5f8ac24c 100644
--- a/docs/known-issues/pt/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
+++ b/docs/known-issues/pt/when-loading-a-product-page-with-a-selection-of-skus-by-parameter-url-the-price-is-not-correctly-updated.md
@@ -22,7 +22,7 @@ Ao acessar uma página de produto com variação (mais de um SKU) com o parâmet
 
 No entanto, se o SKU escolhido (Do parâmetro) estiver indisponível (sem estoque / não entregável), quando o usuário seleciona outro SKU disponível no seletor de SKU, as informações de preço não são exibidas.
 
-![Preço não atualizado com seleção de SKU](//images.contentful.com/alneenqid6w5/1GKcK5NUSoEcmMuesmiGiM/6ddb61d748aa566c6eb5607711a0ae3d/preco.gif)
+![Preço não atualizado com seleção de SKU](https://images.contentful.com/alneenqid6w5/1GKcK5NUSoEcmMuesmiGiM/6ddb61d748aa566c6eb5607711a0ae3d/preco.gif)
 
 ## Simulação
 
diff --git a/docs/tracks/en/access-to-the-customers-last-cart.md b/docs/tracks/en/access-to-the-customers-last-cart.md
index 32adfbf35..a59017cd5 100644
--- a/docs/tracks/en/access-to-the-customers-last-cart.md
+++ b/docs/tracks/en/access-to-the-customers-last-cart.md
@@ -20,4 +20,4 @@ When having access to this information, the sales associate can try to complete
 
 They just need to click `Access` to see the products in the abandoned cart.
 
-![last-cart-en](//images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/fcddb8f976cb0a98d0bb459497b9ef59/last-cart-EN.png)
+![last-cart-en](https://images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/fcddb8f976cb0a98d0bb459497b9ef59/last-cart-EN.png)
diff --git a/docs/tracks/en/accounts-and-architecture.md b/docs/tracks/en/accounts-and-architecture.md
index bfaafd214..50ca9f68c 100644
--- a/docs/tracks/en/accounts-and-architecture.md
+++ b/docs/tracks/en/accounts-and-architecture.md
@@ -28,7 +28,7 @@ VTEX account types are:
 
 The following image is an overview to help you [choose between standard, franchise, or Seller Portal accounts](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78):
 
-![main_account_franchise_seller_portal_EN](//images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/b8f887b2f84c72b3c20a38a020f9c53f/main_account_franchise_seller_portal_EN.png)
+![main_account_franchise_seller_portal_EN](https://images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/b8f887b2f84c72b3c20a38a020f9c53f/main_account_franchise_seller_portal_EN.png)
 
 ## Account characteristics
 
@@ -58,7 +58,7 @@ However, using many trade policies simultaneously can compromise the store's per
 
 The image below is an example of how the main account, environment (sub-account), multi-store (stores), and trade policies are related:
 
-![multistore_aditional_environment_EN](//images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/4bf1e15428b5db24e4658c446eb5e2cf/multistore_aditional_environment_EN.png)
+![multistore_aditional_environment_EN](https://images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/4bf1e15428b5db24e4658c446eb5e2cf/multistore_aditional_environment_EN.png)
 
 ### Multistore
 
diff --git a/docs/tracks/en/add-on-products.md b/docs/tracks/en/add-on-products.md
index 964838bba..c736b94be 100644
--- a/docs/tracks/en/add-on-products.md
+++ b/docs/tracks/en/add-on-products.md
@@ -27,18 +27,18 @@ Add-on products are solutions offered by VTEX to meet the specific business need
 - **Advertisers:** Brands that can create ad campaigns to promote products in VTEX stores offering the same products in their catalogs, thus increasing sales.
 - **Merchants:** Can offer ad space in their stores for advertisers to promote products. In return, these merchants will receive a fee for each click on an ad in their stores.
 
-![vtex_ad_network_sponsored_EN](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/1abdea32c119ed4890e414ad7dbc8fea/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_EN](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/1abdea32c119ed4890e414ad7dbc8fea/vtex_ad_network_sponsored.png)
 
 ## VTEX Assisted Sales
 
 [Assisted Sales (SuiteShare)](https://help.vtex.com/en/tracks/suiteshare--khP0p8mjIYRIpvM7Cb4Zr/onWmyS8j4Thhde67UBBsB) is the solution created by VTEX to boost sales through WhatsApp. It allows you to attract new customers, integrate sales tools, and manage user service data and result metrics.
 
-![suitshare-en](//images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/bb4f1b69fe157f9b529e108898a924ca/next_steps_image11_ONLYPT.JPG)
+![suitshare-en](https://images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/bb4f1b69fe157f9b529e108898a924ca/next_steps_image11_ONLYPT.JPG)
 
 ## VTEX Live Shopping
 VTEX Live Shopping allows creating online broadcasts for live demos of store product features. Direct and instantaneous interactions with customers improve public engagement with the brand and help increase sales performance.
 
-![live-shopping-en](//images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/3f7ee6f650ddb4497166ca049f8a62e5/next_steps_image5_ALL.JPG)
+![live-shopping-en](https://images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/3f7ee6f650ddb4497166ca049f8a62e5/next_steps_image5_ALL.JPG)
 
 To schedule an app demo with an expert, go to the [VTEX Live Shopping](https://vtex.com/us-en/live-shopping/#contact) page.
 
@@ -46,7 +46,7 @@ To schedule an app demo with an expert, go to the [VTEX Live Shopping](https://v
 
 VTEX Personal Shopper allows offering a direct, personalized service between the customer and the sales associate, bringing the physical store shopping experience to the digital environment. The sales associate can show products, make recommendations, and answer customers' questions through this app. They can also add items to the shopping cart during a video call.
 
-![personal-shopper-en](//images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/529260928af943b74c4e8ff30fc61022/next_steps_image6_ALL.JPG)
+![personal-shopper-en](https://images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/529260928af943b74c4e8ff30fc61022/next_steps_image6_ALL.JPG)
 
 To schedule an app demo with an expert, go to the [VTEX Personal Shopper](https://vtex.com/us-en/vtex-personal-shopper/#contact) page.
 
@@ -60,7 +60,7 @@ VTEX Pick and Pack is a solution for managing and ensuring complete visibility t
 
 - [Last Mile app](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): Coordinates the shipping of packages from warehouses or stores to the customer's address by creating efficient delivery routes, selecting available drivers, and tracking the exact location of the order.
 
-![pick-and-pack-en](//images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/6031e1df55ab9664ca2bf5a32ee32f62/next_steps_image7_ALL.JPG)
+![pick-and-pack-en](https://images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/6031e1df55ab9664ca2bf5a32ee32f62/next_steps_image7_ALL.JPG)
 
 To watch an app demo or schedule a custom service with an expert, go to the[ VTEX Pick and Pack](https://content.vtex.com/en/pick-and-pack/) page. 
 
@@ -75,7 +75,7 @@ With [VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-an
 
 - Manage performance metrics for each sales associate.
 
- ![sales-app-en](//images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/c573fe37979371d79899d3fe4761f0a5/next_steps_image8_ALL.JPG)
+ ![sales-app-en](https://images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/c573fe37979371d79899d3fe4761f0a5/next_steps_image8_ALL.JPG)
 
 To watch an app demo or schedule a custom service with an expert, go to the[ VTEX Sales App](https://assets.vtex.com/sales-app/) page.
 
@@ -89,7 +89,7 @@ Explore options for shipping products to all regions of Brazil with [VTEX Shippi
 
 **VTEX Shipping Network** offers the option of connecting carriers to create an integrated delivery network. With currently over 20 partners, it provides customers with the best cost and delivery time options.
 
-![shipping-network-en](//images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/e962d9f6b9b97df93f8a536e3b48b96d/image7.png)
+![shipping-network-en](https://images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/e962d9f6b9b97df93f8a536e3b48b96d/image7.png)
 
 Learn more on the [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) page.
 
@@ -97,7 +97,7 @@ Learn more on the [VTEX Shipping Network](https://vtex.com/br-pt/shipping-networ
 
 [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) is a partnership between VTEX and Correios, the primary postal service in Brazil. This solution allows stores to use PAC and SEDEX shipping services directly through the VTEX Admin with special rates, thereby reducing operational shipping costs.
 
-![image6](//images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/7e85c1b51be49ce02b06036276fd3a0d/image6.png)
+![image6](https://images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/7e85c1b51be49ce02b06036276fd3a0d/image6.png)
 
 Requesting this solution is simple and can be done in a few minutes. To do so, accept the Terms and Conditions and [enable](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) the solution in the store's Admin. These are the features available in the VTEX Shipping Network Correios:
 
diff --git a/docs/tracks/en/add-pickup-points.md b/docs/tracks/en/add-pickup-points.md
index e5123df4b..2c9190b17 100644
--- a/docs/tracks/en/add-pickup-points.md
+++ b/docs/tracks/en/add-pickup-points.md
@@ -32,7 +32,7 @@ Follow the step-by-step below to add a pickup point in your store:
 
 
 
-![EN Cadastrar Pontos de Retirada GIF](//images.ctfassets.net/alneenqid6w5/2vf3pXYddrDf1sybyoTon/efa6e8bc465fb5188c06b1d2deaa2eef/EN_Cadastrar_Pontos_de_Retirada_GIF.gif)
+![EN Cadastrar Pontos de Retirada GIF](https://images.ctfassets.net/alneenqid6w5/2vf3pXYddrDf1sybyoTon/efa6e8bc465fb5188c06b1d2deaa2eef/EN_Cadastrar_Pontos_de_Retirada_GIF.gif)
 
 
 
diff --git a/docs/tracks/en/add-sku-specifications.md b/docs/tracks/en/add-sku-specifications.md
index 0951bba06..971666048 100644
--- a/docs/tracks/en/add-sku-specifications.md
+++ b/docs/tracks/en/add-sku-specifications.md
@@ -34,7 +34,7 @@ To add the specifications, your store already needs to have departments, categor
 7. Fill out the specification form fields. In the case of SKUs, the mandatory fields flag is selected by default. For more info on each field, access our article on [how to fill out SKU specification fields](https://help.vtex.com/en/tutorial/creating-sku-fields--tutorials_119) 
 8. Click on **Save**
 
-![EN.1novo](//images.ctfassets.net/alneenqid6w5/1UNDWQPmeRtLkc1VKqctAF/4e5526d5496d6f0b0fd0c1cc97d4bb05/EN.1novo.gif)
+![EN.1novo](https://images.ctfassets.net/alneenqid6w5/1UNDWQPmeRtLkc1VKqctAF/4e5526d5496d6f0b0fd0c1cc97d4bb05/EN.1novo.gif)
 
 The following steps will let you add SKU specification values:
 
@@ -48,7 +48,7 @@ The following steps will let you add SKU specification values:
 8. Click on **New Value**
 9. Type in the **Name** of the desired value and click on **Save**
 
-![EN.2novo](//images.ctfassets.net/alneenqid6w5/2vwsLaRQy4JXIDCIreLhHg/db0b782d93a8ca16734a59105f9d264a/EN.2novo.gif)
+![EN.2novo](https://images.ctfassets.net/alneenqid6w5/2vwsLaRQy4JXIDCIreLhHg/db0b782d93a8ca16734a59105f9d264a/EN.2novo.gif)
 
 ### Link specifications to a SKU
 
@@ -63,7 +63,7 @@ To include specifications to a **SKU**, complete the following steps:
 6. Select the **Specifications** tab and choose the specification value for this SKU
 7. Click on **Save**
 
-![EN.3novo](//images.ctfassets.net/alneenqid6w5/5IitjVxPxsC0gRmx8Gclpr/7a07cbc2c58f06e8379bc4c1771cbea6/EN.3novo.gif)
+![EN.3novo](https://images.ctfassets.net/alneenqid6w5/5IitjVxPxsC0gRmx8Gclpr/7a07cbc2c58f06e8379bc4c1771cbea6/EN.3novo.gif)
 
 ## Spreadsheet
 
@@ -92,7 +92,7 @@ After filling in the spreadsheet data, follow the instructions below to import y
 5. Click on **Select** to choose the filled out spreadsheet
 6. Click on **Import**
 
-![EN.4](//images.ctfassets.net/alneenqid6w5/3hx1Cvscz5vuvSv05NRl4E/d2dd8151c493ee8d6765aa2ad1374c89/EN.4.gif)
+![EN.4](https://images.ctfassets.net/alneenqid6w5/3hx1Cvscz5vuvSv05NRl4E/d2dd8151c493ee8d6765aa2ad1374c89/EN.4.gif)
 
 ## API 
 
diff --git a/docs/tracks/en/adding-a-loading-dock.md b/docs/tracks/en/adding-a-loading-dock.md
index ea45435fa..7602ad8c0 100644
--- a/docs/tracks/en/adding-a-loading-dock.md
+++ b/docs/tracks/en/adding-a-loading-dock.md
@@ -29,7 +29,7 @@ Follow the steps below to add a loading dock to your store:
 4. Fill out the data entry fields. For more details on each field's meaning, refer to section [data entry fields](#data-entry-fields) below.;
 5. **Save** changes.
 
-![EN Cadastrar Doca GIF](//images.ctfassets.net/alneenqid6w5/5RGUQFBMdcOPn3xV49SSqW/202dce17e72e2fb8da79961326626f03/EN_Cadastrar_Doca_GIF.gif)
+![EN Cadastrar Doca GIF](https://images.ctfassets.net/alneenqid6w5/5RGUQFBMdcOPn3xV49SSqW/202dce17e72e2fb8da79961326626f03/EN_Cadastrar_Doca_GIF.gif)
 
 ### Data entry fields
 
diff --git a/docs/tracks/en/adding-extra-text-to-the-order-print.md b/docs/tracks/en/adding-extra-text-to-the-order-print.md
index d30bfbb03..bad208411 100644
--- a/docs/tracks/en/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/en/adding-extra-text-to-the-order-print.md
@@ -38,7 +38,7 @@ After reloading inStore, whenever a salesperson prints an order, this text will
 
 Before adding extra text, the printout of the order summary has the following format:
 
-![28. Adding extra text to the order print - 1](//images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
+![28. Adding extra text to the order print - 1](https://images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
 
 In our example, we changed the `checkout-instore-custom.js` file by inserting the following extra text:
 
@@ -50,4 +50,4 @@ window.INSTORE_CONFIG = {
 
 Now, whenever an order summary is printed, we will get the following result:
 
-![28. Adding extra text to the order print - 2](//images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
+![28. Adding extra text to the order print - 2](https://images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
diff --git a/docs/tracks/en/adding-new-stores-to-instore.md b/docs/tracks/en/adding-new-stores-to-instore.md
index 2f2f9099b..1161f14f2 100644
--- a/docs/tracks/en/adding-new-stores-to-instore.md
+++ b/docs/tracks/en/adding-new-stores-to-instore.md
@@ -25,7 +25,7 @@ This page allows you to perform the following actions:
 * [Edit](#editing-a-physical-store)
 * [Inactivate](#inactivating-a-physical-store)
 
-![loja-fisica-EN](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
+![loja-fisica-EN](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
 
 The page displays the following information: 
 
@@ -50,7 +50,7 @@ You can add a physical store by following the steps below:
 
 ### Physical store fields
 
-![loja-fisica2-en](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
+![loja-fisica2-en](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
 
 #### Identification
 
diff --git a/docs/tracks/en/adding-product-specifications.md b/docs/tracks/en/adding-product-specifications.md
index 8705bf627..6269e5059 100644
--- a/docs/tracks/en/adding-product-specifications.md
+++ b/docs/tracks/en/adding-product-specifications.md
@@ -35,7 +35,7 @@ To add specifications, your store already needs to have departments, categories,
 7. Fill out the specification form fields. For more info on each field, access our article on [how to fill out product specification fields](https://help.vtex.com/en/tutorial/creating-a-product-field--tutorials_106).
 8. Click on **Save**.
 
-![EN.1novo](//images.ctfassets.net/alneenqid6w5/2dF0ogtrRK8JwAfpklyJ7I/2ff6abcfd3e119739d8d383524b6305b/EN.1novo.gif)
+![EN.1novo](https://images.ctfassets.net/alneenqid6w5/2dF0ogtrRK8JwAfpklyJ7I/2ff6abcfd3e119739d8d383524b6305b/EN.1novo.gif)
 
 The following steps will let you add specification values:
 
@@ -49,7 +49,7 @@ The following steps will let you add specification values:
 8. Click on **New Value**.
 9. Type in the **Name** of the desired value and click on **Save**.
 
-![EN.2novo](//images.ctfassets.net/alneenqid6w5/2LBqRIgwrRKGFRZI1k66xV/c225f4b00ecd036deb541355d10278e8/EN.2novo.gif)
+![EN.2novo](https://images.ctfassets.net/alneenqid6w5/2LBqRIgwrRKGFRZI1k66xV/c225f4b00ecd036deb541355d10278e8/EN.2novo.gif)
 
 ### Linking specifications to a product
 
@@ -63,7 +63,7 @@ To include specifications to a **Product**, complete the following steps:
 4. Select the **Specifications** tab and choose the specification value for this product.
 5. Click on the **Product** tab and then on **Save**.
 
-![EN.3novo](//images.ctfassets.net/alneenqid6w5/6aLqyJEcn1gn7ZY6D1HOBR/b98761150ff82fce355480c78f7693e6/EN.3novo.gif)
+![EN.3novo](https://images.ctfassets.net/alneenqid6w5/6aLqyJEcn1gn7ZY6D1HOBR/b98761150ff82fce355480c78f7693e6/EN.3novo.gif)
 
 ## Spreadsheet
 
@@ -92,7 +92,7 @@ After filling in the spreadsheet data, follow the instructions below to import y
 5. Click on **Select** to choose the filled-out spreadsheet.
 6. Click on **Import**.
 
-![EN.4](//images.ctfassets.net/alneenqid6w5/38zcVf51x9HpqztCxmfgRy/d4d6d36b35f4d0717c3d97fcc9c9223b/EN.4.gif)
+![EN.4](https://images.ctfassets.net/alneenqid6w5/38zcVf51x9HpqztCxmfgRy/d4d6d36b35f4d0717c3d97fcc9c9223b/EN.4.gif)
 
 ## API 
 
diff --git a/docs/tracks/en/adding-products.md b/docs/tracks/en/adding-products.md
index 973f7abf9..77348df09 100644
--- a/docs/tracks/en/adding-products.md
+++ b/docs/tracks/en/adding-products.md
@@ -30,7 +30,7 @@ In the VTEX Admin, follow the steps below.
 4.	Fill out the product form fields. For more on what each field means, read our article on [product registration fields](https://help.vtex.com/en/tutorial/product-registration-fields--4dYXWIK3zyS8IceKkQseke).
 5.	Click on `Save` or `Save and add new SKU`, in case you want to add SKUs associated to that product. 
 
-![Catalogo - Cadastrar produto EN.gif?h=250](//images.ctfassets.net/alneenqid6w5/4Egs4EQBhRUeVCGRvIyNE2/0a89b7d303c4b2a67a686bd9d696bff4/Catalogo_-_Cadastrar_produto_EN.gif_h_250)
+![Catalogo - Cadastrar produto EN.gif?h=250](https://images.ctfassets.net/alneenqid6w5/4Egs4EQBhRUeVCGRvIyNE2/0a89b7d303c4b2a67a686bd9d696bff4/Catalogo_-_Cadastrar_produto_EN.gif_h_250)
 
 ## Spreadsheet
 
diff --git a/docs/tracks/en/adding-skus.md b/docs/tracks/en/adding-skus.md
index 545c97b64..dbef58c40 100644
--- a/docs/tracks/en/adding-skus.md
+++ b/docs/tracks/en/adding-skus.md
@@ -25,7 +25,7 @@ There are two flows which can be used to add SKUs through the VTEX Admin: creati
 ### Adding SKUs after creating a product
 
 1.	On the Product creation page, after filling out the fields, click on **Save and add new SKU**. 
-  ![picture1.en](//images.ctfassets.net/alneenqid6w5/3J1j18vSKiyJ4Bwy5ZLywM/bb8974140c754821ea0d10006a5f943a/picture1.en.png) 
+  ![picture1.en](https://images.ctfassets.net/alneenqid6w5/3J1j18vSKiyJ4Bwy5ZLywM/bb8974140c754821ea0d10006a5f943a/picture1.en.png) 
 2.	You will be redirected to the SKU form page, where you need to fill out fields. For more on each field’s meaning, access our article on [how to fill in SKU creation fields](https://help.vtex.com/en/tutorial/sku-fields--21DDItuEQc6mseiW8EakcY). 
 3.	Click on `Save`.
 
@@ -43,7 +43,7 @@ There are two flows which can be used to add SKUs through the VTEX Admin: creati
 After adding a SKU you’ll need to also link an image to it in order to activate it. Follow the steps below to add an image:
 
 1.	On the page where you added a SKU, click on the **Images** tab
-![picture6.en](//images.ctfassets.net/alneenqid6w5/o99jKS63EZgaeahw9fQvn/47726c30833fd390f2c93f7ec6c0d404/picture6.en.png)
+![picture6.en](https://images.ctfassets.net/alneenqid6w5/o99jKS63EZgaeahw9fQvn/47726c30833fd390f2c93f7ec6c0d404/picture6.en.png)
 2.	Click on `Insert` and choose the image you want to add.
 3.	Fill out the **Text** (image alt tag) and **Label** fields. The label will be used to assist with your site’s page template organization, by referencing the value contained within, i.e. front, side, upper side, etc.
 4.	Click on `Send`.
@@ -53,7 +53,7 @@ After adding a SKU you’ll need to also link an image to it in order to activat
 After adding the images, you must add the SKU specifications. The next step on this track will explain how to add specifications.
 
 1.	Click on the **Specifications** tab.
-![picture7.en](//images.ctfassets.net/alneenqid6w5/4rKSynG7dNq1iwcwLZBKQo/6180b20ecf55cc6a841ac81757dd0f26/picture7.en.png) 
+![picture7.en](https://images.ctfassets.net/alneenqid6w5/4rKSynG7dNq1iwcwLZBKQo/6180b20ecf55cc6a841ac81757dd0f26/picture7.en.png) 
 2.	Fill out the mandatory fields. Specifications may vary according to the selected SKU category.
 3.	Click on `Save`.
 
diff --git a/docs/tracks/en/adding-vendors.md b/docs/tracks/en/adding-vendors.md
index cff96dcf1..85cbacdb5 100644
--- a/docs/tracks/en/adding-vendors.md
+++ b/docs/tracks/en/adding-vendors.md
@@ -18,7 +18,7 @@ If you have set up your store using the __Easy Setup__ flow you may have already
 
 When you enter VTable (https://{{AccountName}}.myvtex.com/admin/vtable) you will see two applications, __Stores Admin__ and __Vendors Admin__:
 
-![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Click __Vendors Admin__ to open the table where we will add a new vendor.
 
@@ -26,7 +26,7 @@ If you have already registered a seller through __Easy Setup__, just click on __
 
 > __IMPORTANT__: the email of each vendor __CAN'T__ be the same used in VTEX platform, because your admin email has permissions that a salesperson should not have, so it is necessary to use some other email without privileges on the platform.
 
-![inStore adicionando vendedor](//images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
+![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
 If you skipped the vendor creation step in __Easy Setup__ and you don't have any vendors created, you will need to get the __Store__ ID in the __Stores Admin__ in VTable.
 
diff --git a/docs/tracks/en/adding-warehouses.md b/docs/tracks/en/adding-warehouses.md
index 137d31946..38c565312 100644
--- a/docs/tracks/en/adding-warehouses.md
+++ b/docs/tracks/en/adding-warehouses.md
@@ -29,7 +29,7 @@ Follow the steps below to add a warehouse to your store:
 4. Fill out the inventory form fields. For more on each field's meaning, see the [Data Entry Fields](#data-entry-fields) section below.
 5. **Save**.
 
-![EN Cadastrar Estoque GIF](//images.ctfassets.net/alneenqid6w5/4teusm8ha4Qp7z2SJ8C6R6/d1e9f85854f1da52135f6920b1ad8aaa/EN_Cadastrar_Estoque_GIF.gif)
+![EN Cadastrar Estoque GIF](https://images.ctfassets.net/alneenqid6w5/4teusm8ha4Qp7z2SJ8C6R6/d1e9f85854f1da52135f6920b1ad8aaa/EN_Cadastrar_Estoque_GIF.gif)
 
 ### Data Entry Fields
 
diff --git a/docs/tracks/en/amazon.md b/docs/tracks/en/amazon.md
index 1cb10e9dc..6311941b0 100644
--- a/docs/tracks/en/amazon.md
+++ b/docs/tracks/en/amazon.md
@@ -16,7 +16,7 @@ trackSlugEN: amazon-integration
 
 Amazon is an ecommerce platform and is considered one of the five largest technology companies in the world. It currently sells a variety of products, such as toys, electronics, clothing, accessories and others In addition, the online retail giant offers streaming services, cloud storage, and virtual assistants.
 
-![amazon logo](//images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
+![amazon logo](https://images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
 
 The integration with Amazon sends products from your VTEX store's catalog to Amazon, allowing you to list your products and increase your sales. 
 
diff --git a/docs/tracks/en/associating-a-template-with-a-layout.md b/docs/tracks/en/associating-a-template-with-a-layout.md
index 999174d06..8ceef1579 100644
--- a/docs/tracks/en/associating-a-template-with-a-layout.md
+++ b/docs/tracks/en/associating-a-template-with-a-layout.md
@@ -30,4 +30,4 @@ This association is made in the layout properties setting. To get there, follow
 6. Select the template you want to associate with this layout.
 7. Type "yes" to confirm the change (this step is necessary because this is a critical change for the site, as the page's front-end will be replaced).
 
-![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tracks/en/autocomplete-search.md b/docs/tracks/en/autocomplete-search.md
index c8fa4fea6..8b80535b3 100644
--- a/docs/tracks/en/autocomplete-search.md
+++ b/docs/tracks/en/autocomplete-search.md
@@ -55,22 +55,22 @@ Another advantage for the store's manager is the increase in conversion due to t
 
 This section displays the most searched terms on the website by other customers.
 
-![top-busca-EN](//images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
+![top-busca-EN](https://images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
 
 ## Last searches
 
 This section displays the last searches performed by the customer. This way, it is possible to start the interaction with the search instantly.
 
-![historico-EN](//images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
+![historico-EN](https://images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
 
 ## Search suggestions
 
 This section displays the terms and categories other users searched related to the search performed at that time. 
 
-![sugest-EN](//images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
+![sugest-EN](https://images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
 
 ## Product suggestion
 
 This section shows the products that correspond to the search carried out at that moment. By displaying products related to your search while you are typing, it reduces dropouts and gives the user the possibility to make a more dynamic purchase.
 
-![produtos-EN](//images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
+![produtos-EN](https://images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
diff --git a/docs/tracks/en/b2b-form.md b/docs/tracks/en/b2b-form.md
index 64e904408..eb554d1ec 100644
--- a/docs/tracks/en/b2b-form.md
+++ b/docs/tracks/en/b2b-form.md
@@ -46,12 +46,12 @@ Examples of how the form with legal entity is presented in inStore:
 
 __B2B Form__ - optional and closed:
 
-![b2b-opcional-fechado](//images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
+![b2b-opcional-fechado](https://images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
 
 __B2B Form__ - optional and open:
 
-![b2b-opcional-aberto](//images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
+![b2b-opcional-aberto](https://images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
 
 __B2B Form__ - mandatory (all fields come already open):
 
-![b2b-obrigatorio](//images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
+![b2b-obrigatorio](https://images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
diff --git a/docs/tracks/en/backend-integrations.md b/docs/tracks/en/backend-integrations.md
index fcf3b4cdd..15f83c4d6 100644
--- a/docs/tracks/en/backend-integrations.md
+++ b/docs/tracks/en/backend-integrations.md
@@ -102,7 +102,7 @@ You must follow the setup steps for this phase in the order shown below. A detai
 
 After configuring the store and integrating with the middleware, the general flow of information will follow this format:
 
-![ERP-integrations-en](//images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/8e7c022f2bfa116bccf9ccdc80ac2ca7/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_2.jpg)
+![ERP-integrations-en](https://images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/8e7c022f2bfa116bccf9ccdc80ac2ca7/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_2.jpg)
 
 Each request or process represented by the arrows in the diagram above is triggered by a different type of event in the operation of an ecommerce store. Learn more about this flow in the [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide#ongoing-middleware-flow).
 
@@ -168,7 +168,7 @@ There are three types of specifications, which should be created in the followin
 
 The diagram below illustrates this procedure.
 
-![catalog_specification_diagram_EN](//images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/2f813d423b73074446a2e2a743e22328/catalog_specification_diagram_EN.png)
+![catalog_specification_diagram_EN](https://images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/2f813d423b73074446a2e2a743e22328/catalog_specification_diagram_EN.png)
 
 Specifications follow the Catalog hierarchy. When a group is created within a department or category, it will be inherited by the subsequent lower levels. 
 
diff --git a/docs/tracks/en/banners-en.md b/docs/tracks/en/banners-en.md
index 4a1e55b13..d9cbfad06 100644
--- a/docs/tracks/en/banners-en.md
+++ b/docs/tracks/en/banners-en.md
@@ -33,7 +33,7 @@ On VTEX Admin, the page **Storefront** > **Banners** shows the full list of regi
 * [Edit a banner](#editing-a-banner)
 * [Delete a banner](#deleting-a-banner) 
 
-![banners-intro-en](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
+![banners-intro-en](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
 
 The page shows the following information:
 
diff --git a/docs/tracks/en/barcode-reading.md b/docs/tracks/en/barcode-reading.md
index 57a40007d..f58990ca5 100644
--- a/docs/tracks/en/barcode-reading.md
+++ b/docs/tracks/en/barcode-reading.md
@@ -18,7 +18,7 @@ After identifying the customer, the sales associate is taken directly to the car
 
 If the sales associate is using a tablet or smartphone, they will see a barcode button <i class="fas fa-barcode"></i> on the top bar of the application.
 
-![31. VTEX Sales App - Product Overview - 6 - EN](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/2db81c47910586c71b8f4251f324d5f5/barcode.png)
+![31. VTEX Sales App - Product Overview - 6 - EN](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/2db81c47910586c71b8f4251f324d5f5/barcode.png)
 
 When clicking on it, the sales associate can use the camera to beep a product and, with that, be automatically taken to the details screen of that product.
 
diff --git a/docs/tracks/en/basic-vtex-io-developer-setup.md b/docs/tracks/en/basic-vtex-io-developer-setup.md
index 2633c78cc..bf18a7d29 100644
--- a/docs/tracks/en/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/en/basic-vtex-io-developer-setup.md
@@ -38,7 +38,7 @@ This will open a browser window and ask for your credentials.
 
 When you are logged in, you can use the `vtex whoami` command to find out which *account* and *workspace* you are currently using.
 
-![Command Line](//images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
+![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
 <div class="alert alert-info">
 PROTIP: You can configure your terminal to display your current account and workspace automatically. The easiest way to do it is to use our <a href="https://github.com/vtex/dotfiles">dotfiles</a>, which automatically configure <a href="https://fishshell.com/">Fish Shell</a> and add a <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">prompt function</a> for you.
@@ -54,7 +54,7 @@ By default, when you log in to a store you are in the `master` workspace. You ca
 $ vtex ls
 ```
 
-![Command Line vtex ls](//images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
+![Command Line vtex ls](https://images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
 
 ## Creating your own workspace
 
@@ -72,6 +72,6 @@ TIP: You can switch to <em>and reset</em> a workspace to master in a single comm
 
 Workspaces can be named arbitrarily, but we find it’s usually convenient to name it after yourself when you want to develop something in your own environment.
 
-![command line workspace](//images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
+![command line workspace](https://images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
 
 Now you have your own workspace. You can call `vtex list` again and notice that the installed apps mirror those in `master`. Now, let’s `link` a local version of the store theme so you can start editing it.
diff --git a/docs/tracks/en/best-practices-for-testing-instore.md b/docs/tracks/en/best-practices-for-testing-instore.md
index 6e00069be..08a9733a4 100644
--- a/docs/tracks/en/best-practices-for-testing-instore.md
+++ b/docs/tracks/en/best-practices-for-testing-instore.md
@@ -17,7 +17,7 @@ trackSlugEN: instore-using-the-app
 
 After configuring the basic settings and installing VTEX Sales App on a device, it is important to run tests before you start using the app in your physical stores. In this article, you will learn about best practices for testing VTEX Sales App.
 
-![testes-instore-en](//images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/52fda979578d04c818658558df9a753f/Group_5__1_.png)
+![testes-instore-en](https://images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/52fda979578d04c818658558df9a753f/Group_5__1_.png)
 
 ## Technical testing
 
diff --git a/docs/tracks/en/cart-transfer-and-capture.md b/docs/tracks/en/cart-transfer-and-capture.md
index 72265934a..510ac2b5e 100644
--- a/docs/tracks/en/cart-transfer-and-capture.md
+++ b/docs/tracks/en/cart-transfer-and-capture.md
@@ -20,11 +20,11 @@ VTEX Sales App allows you to [enable the cart transfer functionality](https://he
 
 For the sales associate to share a cart, they can generate a numeric code or a QR Code. To do this, while on the cart screen, just click on the __Transfer__ button. See an example in the image below.
 
-![24. Enable cart transfer between devices - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
 
 When they click this button, the app shows a QR Code and a four-digit numeric code.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Another sales associate logged into the same store can then capture that cart and continue selling from their device.
 
@@ -34,7 +34,7 @@ To capture a cart, enter the VTEX Sales App main menu and click on `Capture Cart
 
 Alternatively, on the app's home screen, the sales associate can slide the screen to the right. When they drag the screen to the right, they will see the __Cart Capture__ option, as shown in the image below.
 
-![24. Enable cart transfer between devices - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
 
 On this screen, they can capture a cart using one of three methods:
 
diff --git a/docs/tracks/en/cart-transfer.md b/docs/tracks/en/cart-transfer.md
index d3c2f0b2c..8835c903e 100644
--- a/docs/tracks/en/cart-transfer.md
+++ b/docs/tracks/en/cart-transfer.md
@@ -31,14 +31,14 @@ window.INSTORE_CONFIG = {
 
 When making this change, you should notice that two polyesters appear at the bottom of the inStore ID page:
 
-![01 inStore slider transferencia](//images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
+![01 inStore slider transferencia](https://images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
 
 When dragging the screen to the side you will see the screen for __ "Capture Cart" __:
 
-![02 inStore capturar carrinho](//images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
+![02 inStore capturar carrinho](https://images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
 
 In it it is possible to capture a cart by the code of the cart, QR code or even by seller.
 
 In order to generate a QR code or code from a cart you must use the __ "Transfer" option __ in the inStore cart:
 
-![03 inStore transferir](//images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
+![03 inStore transferir](https://images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
diff --git a/docs/tracks/en/catalog-architecture.md b/docs/tracks/en/catalog-architecture.md
index 95a5c0a20..fc99c3234 100644
--- a/docs/tracks/en/catalog-architecture.md
+++ b/docs/tracks/en/catalog-architecture.md
@@ -35,4 +35,4 @@ Such specifications are, for example, a product's composition or an SKU's voltag
 
 An example of a VTEX Catalog architecture blueprint is found below:
 
-![arquitetura-catalogo-EN](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
+![arquitetura-catalogo-EN](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
diff --git a/docs/tracks/en/catalog-concept-definition.md b/docs/tracks/en/catalog-concept-definition.md
index 958fdc2d5..201814760 100644
--- a/docs/tracks/en/catalog-concept-definition.md
+++ b/docs/tracks/en/catalog-concept-definition.md
@@ -16,7 +16,7 @@ trackSlugEN: catalog-101
 
 The **Catalog** menu contains the features related to the product assortment of your ecommerce store. In order for your customer to see the products on the website, you need to add them to this Admin menu first.
 
-![visao-geral-produto-EN](//images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/be0aec115746ca9494e44e3f120983ed/image.png)
+![visao-geral-produto-EN](https://images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/be0aec115746ca9494e44e3f120983ed/image.png)
 
 The **Catalog** section enables the setup of capabilities related to the assortment of ecommerce products, such as their categories, brands, and collections, for example. To sell your products, you must add them in this section.
 
diff --git a/docs/tracks/en/changing-the-instore-language.md b/docs/tracks/en/changing-the-instore-language.md
index abf7d42ef..5ca03c9c0 100644
--- a/docs/tracks/en/changing-the-instore-language.md
+++ b/docs/tracks/en/changing-the-instore-language.md
@@ -80,4 +80,4 @@ After making the code change, save the file `checkout-instore-custom.js`.
 
 Then, in the inStore application, to see the reflected changes, enter the menu and click the __Reset app local data__ button, as shown in the image below.
 
-![22. Change the inStore language - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/7qVSATLXP6DBktXwwWsE0H/72515ce67429eaf6334a3cd1288e3884/22._Change_the_inStore_language_-_1_-_EN.png_h_250)
+![22. Change the inStore language - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/7qVSATLXP6DBktXwwWsE0H/72515ce67429eaf6334a3cd1288e3884/22._Change_the_inStore_language_-_1_-_EN.png_h_250)
diff --git a/docs/tracks/en/cms-folder-structure.md b/docs/tracks/en/cms-folder-structure.md
index cea030b39..9cb44638c 100644
--- a/docs/tracks/en/cms-folder-structure.md
+++ b/docs/tracks/en/cms-folder-structure.md
@@ -35,7 +35,7 @@ These are the folders that every store needs to have in the CMS to ensure the co
 
 See below these basic folders in the CMS:
 
-![pastasObrigatorias](//images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
+![pastasObrigatorias](https://images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
 
 These folders come by default in the environment of all VTEX stores.
 
diff --git a/docs/tracks/en/cms-vtex-io.md b/docs/tracks/en/cms-vtex-io.md
index 79fdb500b..54474ac7a 100644
--- a/docs/tracks/en/cms-vtex-io.md
+++ b/docs/tracks/en/cms-vtex-io.md
@@ -28,19 +28,19 @@ Configure the [store’s binding](https://help.vtex.com/en/tutorial/what-is-cms-
 
 Binding is the process to link your website to a store. For more details , please refer to the article [Linking a store to a folder structure in CMS (binding)](https://help.vtex.com/en/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![CMS - Sites and channels EN](//images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/73e1c8e48c93825b917c547c624ff8de/cms-sites-and-channels-en.png)
+![CMS - Sites and channels EN](https://images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/73e1c8e48c93825b917c547c624ff8de/cms-sites-and-channels-en.png)
 
 ## Pages
 In **[Pages](https://help.vtex.com/en/tutorial/pages-overview--5iBUUJbK5NqG6OxlDrGNzc)**, create a new URL and link it to a template already defined in your [Store theme code](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-4-configuringtemplates).
 
-![CMS - Pages](//images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/0e439bd649959c6b451120e21fb95f75/cms-pages-en.png)
+![CMS - Pages](https://images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/0e439bd649959c6b451120e21fb95f75/cms-pages-en.png)
 
 Also, this section contains the **Redirects** page, which redirects users and search engines from one URL to a more relevant or similar one. 
 
 ## Site Editor
 The **[Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1)** is a graphical interface for managing your storefront content. It allows you to create, edit, publish, and schedule changes in your storefront components and behavior.
 
-![CMS - Site Editor EN](//images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/223fd5b5913716fa5d972779a2ee90ce/cms-siteeditor-en.png)
+![CMS - Site Editor EN](https://images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/223fd5b5913716fa5d972779a2ee90ce/cms-siteeditor-en.png)
 
 ## Styles
 
@@ -50,12 +50,12 @@ The **[Styles](https://help.vtex.com/en/tutorial/styles-overview--v0Db5ohEKSFIkT
   This feature only works in <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-creating-a-production-workspace">production workspaces</a>.
 </div>
 
-![CMS - Styles](//images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/7922d221d3e07ae06655f6f99a8b9882/cms-styles-en.png)
+![CMS - Styles](https://images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/7922d221d3e07ae06655f6f99a8b9882/cms-styles-en.png)
 
 ## Store
 The **[Store](https://help.vtex.com/en/tutorial/cms-loja-visao-geral--3Eat287G6wUi6Mly5rW5Fs)** section is responsible for SEO configurations, performance optimization flags, and enabling PWA push notifications in your store.
 
-![CMS - Store](//images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/11c316fb6a30988b9db10be80defa05d/cms-store-en.png)
+![CMS - Store](https://images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/11c316fb6a30988b9db10be80defa05d/cms-store-en.png)
 
 ## References
 - [Concepts - VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6loFGF4nXvgIVIzsyyJA5c#concepts)
diff --git a/docs/tracks/en/configure-customer-identification.md b/docs/tracks/en/configure-customer-identification.md
index bfb18e1a7..e1e4bd0bb 100644
--- a/docs/tracks/en/configure-customer-identification.md
+++ b/docs/tracks/en/configure-customer-identification.md
@@ -26,11 +26,11 @@ To choose which identification methods you want to enable, access the VTEX admin
 
 In the __Customer's login__ box, you must select the identification methods you want to enable.
 
-![21. Configure client identification - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3E5pzs9HJLG8lt2MhxU8ej/962eaa1511cc39f933da2a5c94c97974/21._Configure_client_identification_-_1_-_EN.png_h_250)
+![21. Configure client identification - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3E5pzs9HJLG8lt2MhxU8ej/962eaa1511cc39f933da2a5c94c97974/21._Configure_client_identification_-_1_-_EN.png_h_250)
 
 You can also change the order of these methods. To do this, just drag them, as shown in the image below. The order of the methods defined on this screen determines the order in which they will appear to the salespeople in the app. Therefore, the first method will be the default.
 
-![21. Configure client identification - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6qpyKGeKGdLBckP50im7px/1a5b927292b28a85114c01195212d501/21._Configure_client_identification_-_2_-_EN.png_h_250)
+![21. Configure client identification - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6qpyKGeKGdLBckP50im7px/1a5b927292b28a85114c01195212d501/21._Configure_client_identification_-_2_-_EN.png_h_250)
 
 ## Enabling Anonymous User
 
@@ -38,7 +38,7 @@ It is possible to use the inStore to cater customers anonymously, that is, witho
 
 For this, still in the Customer Identification screen, you need to enable the __Anonymous user__ flag.
 
-![21. Configure client identification - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3MpFYKg99z1oW1w0ZPzCbN/2d6da3c24fa44ec72ed3cb385c49f96c/21._Configure_client_identification_-_3_-_EN.png_h_250)
+![21. Configure client identification - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3MpFYKg99z1oW1w0ZPzCbN/2d6da3c24fa44ec72ed3cb385c49f96c/21._Configure_client_identification_-_3_-_EN.png_h_250)
 
 ## Legal Entity Registration for B2B sales
 
@@ -50,10 +50,10 @@ You can then choose whether these fields are mandatory or optional.
 
 In the example below, the Legal Entity registration is activated and configured as optional.
 
-![21. Configure client identification - 4 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2bf1NMJMXF9JHnM67mFI2s/2c342420c8705dd137048a6ac6edee17/21._Configure_client_identification_-_4_-_EN.png_h_250)
+![21. Configure client identification - 4 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2bf1NMJMXF9JHnM67mFI2s/2c342420c8705dd137048a6ac6edee17/21._Configure_client_identification_-_4_-_EN.png_h_250)
 
 In this case, the application will show the salespeople a form like the one below:
 
-![21. Configure client identification - 5.png?h=250](//images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/47968bd2948a339e964f5057b251b5f1/21._Configure_client_identification_-_5.png_h_250)
+![21. Configure client identification - 5.png?h=250](https://images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/47968bd2948a339e964f5057b251b5f1/21._Configure_client_identification_-_5.png_h_250)
 
 Note that a flag is displayed that allows the salesperson to decide whether to show these additional fields or not. This is because, in the settings, we marked the legal entity registration fields as optional. If they are marked as mandatory, this flag will not show on the app.
diff --git a/docs/tracks/en/configuring-a-payment-condition.md b/docs/tracks/en/configuring-a-payment-condition.md
index ae4abc9c3..2f2f77d60 100644
--- a/docs/tracks/en/configuring-a-payment-condition.md
+++ b/docs/tracks/en/configuring-a-payment-condition.md
@@ -100,7 +100,7 @@ If you decide to configure a payment method that accepts installments with inter
 The Automatic Installment option allows you to configure the details of the installments directly in the payment provider (outside the VTEX environment).
 To enable this option, select “Yes” in the **Use external installments** field during the [provider setup](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444) step.
 
-![automaticinstallment](//images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/965203e926177f608618ed0048411de6/parcelamentoautomaticous.JPG)
+![automaticinstallment](https://images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/965203e926177f608618ed0048411de6/parcelamentoautomaticous.JPG)
 
 After enabling automatic installment payment on the provider, follow these steps:
 
diff --git a/docs/tracks/en/configuring-banners.md b/docs/tracks/en/configuring-banners.md
index f1e08d116..1a804e4ef 100644
--- a/docs/tracks/en/configuring-banners.md
+++ b/docs/tracks/en/configuring-banners.md
@@ -28,7 +28,7 @@ After configuring the banner, you have to add it to a page on your store. To do
 <p> This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: Multilanguage settings (Beta)</a>.</p>
 </div>
 
-![banner-form-en](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
+![banner-form-en](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
 
 ## Banner fields
 
@@ -59,7 +59,7 @@ To add a banner, the following fields need to be completed:
 
 Click <i class="fas-solid fa-link"></i> `Autofill from URL` to add the URL of the search page to the trigger rules that will be applied.
 
-![banner-url-en](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
+![banner-url-en](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
 
 Click <i class="fas fa-plus"></i> `Add condition` to create a rule. Rules can be of two types:
 
diff --git a/docs/tracks/en/configuring-cash-payments-through-instore.md b/docs/tracks/en/configuring-cash-payments-through-instore.md
index 06bca64d4..863f62086 100644
--- a/docs/tracks/en/configuring-cash-payments-through-instore.md
+++ b/docs/tracks/en/configuring-cash-payments-through-instore.md
@@ -35,7 +35,7 @@ Now we will create the payment condition.
 1. Still on the **Settings** page of the **Payments** module in the VTEX Admin, click on the **Payment conditions** tab.
 2. Click on the green button with the `+` icon to add a new condition, as shown below.
 
-![en-add-payment-condition](//images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/fefd28c063c5572c3dfe2852aac484f5/en-add-payment-condition-1.png)
+![en-add-payment-condition](https://images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/fefd28c063c5572c3dfe2852aac484f5/en-add-payment-condition-1.png)
 
 3. In the **Custom payment** section, select the **Cash** option you have created.
 4. Enter a name for this payment condition, change the status to **Active**, and in the **Process with affiliation** field, select the custom payment you created in the previous step.
diff --git a/docs/tracks/en/configuring-login-with-facebook.md b/docs/tracks/en/configuring-login-with-facebook.md
index 69b9198df..b810f509e 100644
--- a/docs/tracks/en/configuring-login-with-facebook.md
+++ b/docs/tracks/en/configuring-login-with-facebook.md
@@ -28,7 +28,7 @@ After configuring the Facebook registration, you need to configure this login op
 1. In the **Account Settings** module, click on the **Authentications** tab.
 2. Click on the **Edit** button corresponding to Facebook.
 3. Fill in the fields with the _Client Id_ and _Client Secret_ registered on **Facebook**.
-    ![Facebook OAuth EN](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/06b29f9c839316df31c736a315ba1786/facebook_EN.png)
+    ![Facebook OAuth EN](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/06b29f9c839316df31c736a315ba1786/facebook_EN.png)
 4. Click on the **Save** button.
 5. To confirm that your login was successful, go to the front-end of your store and click on **Login**. 
 6. The configured login options will be shown. Click on the **Facebook** option and check if your store name is displayed.
diff --git a/docs/tracks/en/configuring-login-with-google.md b/docs/tracks/en/configuring-login-with-google.md
index e7dc96ec6..5ce00dba7 100644
--- a/docs/tracks/en/configuring-login-with-google.md
+++ b/docs/tracks/en/configuring-login-with-google.md
@@ -29,7 +29,7 @@ After configuring your Google identity platform, you need to configure your logi
 1. In the **Account Settings** module, click on the **Authentication** tab.
 2. Click on the **Edit** button corresponding to Google.
 3. Fill in the fields with the _Client Id_ and _Client Secret_ added to **Google**.
-    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
+    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
 4. Click on the **Save** button.
 5. To confirm whether your login was successfully configured, access the front-end of your store and click on **Login**.
 6. The configured login options will be shown. Click on the **Google** option and check whether your store name is displayed.
diff --git a/docs/tracks/en/configuring-redirect.md b/docs/tracks/en/configuring-redirect.md
index 6cafeecf0..e4a0fef22 100644
--- a/docs/tracks/en/configuring-redirect.md
+++ b/docs/tracks/en/configuring-redirect.md
@@ -26,7 +26,7 @@ To configure a redirect, follow the steps below.
 
 You must fill in the fields below.
 
-![redirecionamentos-adminv4-EN](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
+![redirecionamentos-adminv4-EN](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
 
 ### General information
 
diff --git a/docs/tracks/en/configuring-ship-from-store.md b/docs/tracks/en/configuring-ship-from-store.md
index 000906140..b969423a8 100644
--- a/docs/tracks/en/configuring-ship-from-store.md
+++ b/docs/tracks/en/configuring-ship-from-store.md
@@ -16,7 +16,7 @@ trackSlugEN: unified-commerce-strategies
 
 The **Ship From Store** strategy allows a customer who wants to receive the products at home to receive them from the warehouse of a physical store. In other words, in this scenario, the store functions as a mini distribution center.
 
-![35. Setting up Shipping From Store - 1](//images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
+![35. Setting up Shipping From Store - 1](https://images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
 
 This type of logistics helps your operation to reduce costs and shipping time. Instead of having only the main warehouses - usually away from the central areas of cities - you now have a more capillary delivery network.
 
diff --git a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 5a6190101..15b5b18b5 100644
--- a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -40,7 +40,7 @@ For the integration to work properly, we recommended that you grant all the perm
 10. Click on `Next`.
 11. In the pop-up window, a confirmation that the integration has been configured will be displayed. Click on `Done`.
 
-![gif en v1](//images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/6eec11fdae6edb9afd05f70a1814b248/gif_en_v1.gif)
+![gif en v1](https://images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/6eec11fdae6edb9afd05f70a1814b248/gif_en_v1.gif)
 
 ## Sending product information to Facebook Business Extension
 
diff --git a/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 7c0a6bc7f..a172c25a3 100644
--- a/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -82,7 +82,7 @@ After completing the integration configuration form, you need to connect your Ti
 
 On the **Set Up TikTok for Business page**, as illustrated below, please follow the configuration instructions described next.
 
-![set-up-tiktok-for-business](//images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
+![set-up-tiktok-for-business](https://images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
 
 1. Click the __TikTok for Business Account__ section and check if your account is listed.
     * If you want to connect another account, click `Disconnect` and repeat the login step described in [Connecting the TikTok account](#2-connecting-the-tiktok-account).
diff --git a/docs/tracks/en/configuring-the-relevance-feature.md b/docs/tracks/en/configuring-the-relevance-feature.md
index 595050da1..85c2409c8 100644
--- a/docs/tracks/en/configuring-the-relevance-feature.md
+++ b/docs/tracks/en/configuring-the-relevance-feature.md
@@ -34,7 +34,7 @@ The page is divided into two sections: __Priority criteria__ and __Criteria comp
   <li><b>Catalog Score:</b> 3</li>
 </ul>
 
-![default priority criteria EN](//images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/398cdb38b52d775d9fe9058ace66fdf2/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_18.png)
+![default priority criteria EN](https://images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/398cdb38b52d775d9fe9058ace66fdf2/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_18.png)
 
 To change Relevance settings, follow the steps below.
 
@@ -42,7 +42,7 @@ To change Relevance settings, follow the steps below.
 2. Click on __Relevance settings__.
 3. Choose the criterion whose weight you want to change.
 4. Drag the slider to choose its weight, as shown in the image below.
-  ![composicao-criterios-en](//images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/4ab581d6ffbed81312d9d853dc79f917/composicao-criterios-en.gif)
+  ![composicao-criterios-en](https://images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/4ab581d6ffbed81312d9d853dc79f917/composicao-criterios-en.gif)
   If you want to change a criterion from __Criteria composition__ to __Priority criteria__, click on the <i class="fas fa-bars"></i> icon and drag it to the Priority criteria block at the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight.
-  ![priority-criteria-en](//images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/e81fd3673b90c0a48d166712f6017bdf/priority-criteria-en.gif)
+  ![priority-criteria-en](https://images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/e81fd3673b90c0a48d166712f6017bdf/priority-criteria-en.gif)
 5. Click on __Save__.
diff --git a/docs/tracks/en/create-brands.md b/docs/tracks/en/create-brands.md
index fc9de5bc2..c617da332 100644
--- a/docs/tracks/en/create-brands.md
+++ b/docs/tracks/en/create-brands.md
@@ -38,7 +38,7 @@ Information that is filled out can be updated at any time using the Catalog modu
 
 To delete a brand entry, click the arrow next to `Edit` and then click `Delete`.
 
-![editar-marca EN](//images.ctfassets.net/alneenqid6w5/lAOk9EHq8WLoXs6SnrXsv/55b9ba52f46ae8582315ffda359a3b39/editar-marca_EN.png)
+![editar-marca EN](https://images.ctfassets.net/alneenqid6w5/lAOk9EHq8WLoXs6SnrXsv/55b9ba52f46ae8582315ffda359a3b39/editar-marca_EN.png)
 
 ## API
 
diff --git a/docs/tracks/en/create-product-feed.md b/docs/tracks/en/create-product-feed.md
index 554a4b243..82923a693 100644
--- a/docs/tracks/en/create-product-feed.md
+++ b/docs/tracks/en/create-product-feed.md
@@ -32,7 +32,7 @@ To make product updates available to Lengow, you must [configure an XML feed](ht
 
 The feed itself should then be filled in as seen in the image below:
 
-![image2](//images.ctfassets.net/alneenqid6w5/2TuXQFVWgd7liQ7jSxYHDu/c46858cd6a536d3f3290bafe2e105724/image2.png)
+![image2](https://images.ctfassets.net/alneenqid6w5/2TuXQFVWgd7liQ7jSxYHDu/c46858cd6a536d3f3290bafe2e105724/image2.png)
 
 ## Verify XML feed consistency
 
@@ -42,7 +42,7 @@ Your product feed should now be available at the following URL:
 
 If you visit this URL in your browser, you should see an XML document tree like this:
 
-![image8](//images.ctfassets.net/alneenqid6w5/7fBOjuxHDkRYtIoLPSnJcp/038cfb985ae364a3af5068ed5f69e489/image8.png)
+![image8](https://images.ctfassets.net/alneenqid6w5/7fBOjuxHDkRYtIoLPSnJcp/038cfb985ae364a3af5068ed5f69e489/image8.png)
 
 The numbers seen in the XML feed correspond to the Product ID for all products in the collection you created for the Lengow connector.
 
diff --git a/docs/tracks/en/create-the-category-tree.md b/docs/tracks/en/create-the-category-tree.md
index 48c8599a0..7456fa3d9 100644
--- a/docs/tracks/en/create-the-category-tree.md
+++ b/docs/tracks/en/create-the-category-tree.md
@@ -38,7 +38,7 @@ At the beginning of the project, before any product is inserted into the platfor
 
 Such structure, therefore, could be the initial drawing of your category tree:
 
-![Category tree](//images.contentful.com/alneenqid6w5/1nka2VMUo002C6cUqsCyQW/bae0791861085cfba9183b6308fbd1db/Untitled__2_.png)
+![Category tree](https://images.contentful.com/alneenqid6w5/1nka2VMUo002C6cUqsCyQW/bae0791861085cfba9183b6308fbd1db/Untitled__2_.png)
 
 __Note__: The names __Department__, __Category__ and __Subcategory__ are just a way to see your tree, which may or may not facilitate your work. The platform does not require this or any other naming standard. For VTEX, any levels that may be created for the distribution of your products are taken only as category levels.
 
diff --git a/docs/tracks/en/creating-accounts.md b/docs/tracks/en/creating-accounts.md
index 8abc3f5a8..78d739039 100644
--- a/docs/tracks/en/creating-accounts.md
+++ b/docs/tracks/en/creating-accounts.md
@@ -40,7 +40,7 @@ Filling in the <b>Email</b> field is mandatory, as the VTEX platform uses this i
 
 From this moment on, the new account created will be displayed on the __Accounts__ screen.
 
-![CC_new_account_1_EN](//images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/29c36c044a54c156d6dbf4d385da0dee/CC_new_account_1_EN.JPG)
+![CC_new_account_1_EN](https://images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/29c36c044a54c156d6dbf4d385da0dee/CC_new_account_1_EN.JPG)
 
 ## Create multiple accounts (bulk import)
 
@@ -57,7 +57,7 @@ To create multiple accounts at the same time (in bulk) in Customer Credit, you c
   <li>Columns <b>Credit limit</b> and <b>Tolerance rate</b>: values available to each customer. The <b>Tolerance rate</b> must be entered in decimal format, for example, a tolerance of 5% must be indicated as 0.05.</li>
 </ul>
 
-![CC_criar_conta_2_ALL](//images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
+![CC_criar_conta_2_ALL](https://images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
 
 <blockquote><ui>6. Save the .csv spreadsheet.</ui>
 
diff --git a/docs/tracks/en/creating-merchandising-rules-visual-editor.md b/docs/tracks/en/creating-merchandising-rules-visual-editor.md
index 6dc45ffb2..7927b064f 100644
--- a/docs/tracks/en/creating-merchandising-rules-visual-editor.md
+++ b/docs/tracks/en/creating-merchandising-rules-visual-editor.md
@@ -51,7 +51,7 @@ To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.co
 
 The Visual Editor for merchandising rules in VTEX Intelligent Search allows you to perform the actions shown in the image below:
 
-![visual-merch-rules-EN-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
+![visual-merch-rules-EN-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Edit the name of the merchandising rule.</li>
diff --git a/docs/tracks/en/creating-or-editing-a-page-template.md b/docs/tracks/en/creating-or-editing-a-page-template.md
index f79b467e6..54bb7013d 100644
--- a/docs/tracks/en/creating-or-editing-a-page-template.md
+++ b/docs/tracks/en/creating-or-editing-a-page-template.md
@@ -42,9 +42,9 @@ Check out the walk-through:
 </ul></p>
 </div>
 7. Then fill in the __Template XHTML__ box with your template code. 
-![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 9. Click on the __Save Template__ button.
-![4 2](//images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
+![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
 To edit an existing template, the process is almost identical.
 
diff --git a/docs/tracks/en/creating-regular-promotions.md b/docs/tracks/en/creating-regular-promotions.md
index d996b4457..8d1f10fb1 100644
--- a/docs/tracks/en/creating-regular-promotions.md
+++ b/docs/tracks/en/creating-regular-promotions.md
@@ -109,7 +109,7 @@ You can include or exclude **categories**, **brands**, **collections**, **produc
 
 To be eligible for the promotion, products must meet all the conditions added in this section.
 
-![A quais itens esta promoção será aplicada - EN](//images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/2b8a18cfaa26f45756354a1a081cd2a0/A_quais_itens_-_EN.png)
+![A quais itens esta promoção será aplicada - EN](https://images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/2b8a18cfaa26f45756354a1a081cd2a0/A_quais_itens_-_EN.png)
 
 # 3. Conditions for the promotion to be valid
 
diff --git a/docs/tracks/en/credit-card-payment-flow.md b/docs/tracks/en/credit-card-payment-flow.md
index f372b1b42..22c0c148c 100644
--- a/docs/tracks/en/credit-card-payment-flow.md
+++ b/docs/tracks/en/credit-card-payment-flow.md
@@ -28,7 +28,7 @@ To learn more about the financial agents involved in the payment flow of an orde
 
 The complete credit card payment flow at VTEX is shown in the following scheme:
 
-![Credit Card - Basic payment flow](//images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/dbee2595f3dda339db8010cb8d00f67d/payments_image1_EN.JPG)
+![Credit Card - Basic payment flow](https://images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/dbee2595f3dda339db8010cb8d00f67d/payments_image1_EN.JPG)
 
 1. On the Checkout screen of your store, the customer chooses the _credit card_ **Payment Method** to complete the purchase.
 
diff --git a/docs/tracks/en/customer-identification.md b/docs/tracks/en/customer-identification.md
index bba6eeed5..acae9fce8 100644
--- a/docs/tracks/en/customer-identification.md
+++ b/docs/tracks/en/customer-identification.md
@@ -27,7 +27,7 @@ You can [configure which identification methods you want to enable](https://deve
 
 In the example image below, Email and CPF are enabled.
 
-![31. VTEX Sales App - Product Overview - 2 - EN](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99343004a1e70a756f043ea293d5cd24/identify-customer-en.PNG)
+![31. VTEX Sales App - Product Overview - 2 - EN](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99343004a1e70a756f043ea293d5cd24/identify-customer-en.PNG)
 
 Just enter one of these data in the field and click on the `Confirm` button.
 
diff --git a/docs/tracks/en/customizing-styles.md b/docs/tracks/en/customizing-styles.md
index 051fb7ed6..f1727eb3c 100644
--- a/docs/tracks/en/customizing-styles.md
+++ b/docs/tracks/en/customizing-styles.md
@@ -48,7 +48,7 @@ Let's make some changes to our `style.json` file. We can change the colors a bit
 
 Now, see the results by `linking` our app:
 
-![style-json](//images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
+![style-json](https://images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
 
 Success! Now you know how to customize your store's styles.
 
@@ -98,4 +98,4 @@ Let’s type some CSS inside, giving us a nice solid red line:
 ```
 Our new category menu will now have a solid red line along the bottom of our menu.
 
-![red-line](//images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
+![red-line](https://images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
diff --git a/docs/tracks/en/customizing-templates.md b/docs/tracks/en/customizing-templates.md
index fb103c222..c97ff86a3 100644
--- a/docs/tracks/en/customizing-templates.md
+++ b/docs/tracks/en/customizing-templates.md
@@ -119,6 +119,6 @@ To add a component to this page, we simply need to declare a new shelf block and
 
 If you save this in `store/blocks.json` and `vtex link` your store, you should see a new shelf rendered when visiting the home.
 
-![shelf](//images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
+![shelf](https://images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
 
 You can customize the blocks declared by the `store-theme` app freely, and also declare new ones yourself. For now, you can find the documentation for each component on their [GitHub repositories](https://github.com/vtex-apps?q=store-components). There, you can find the available properties for each component.
diff --git a/docs/tracks/en/dashboard.md b/docs/tracks/en/dashboard.md
index 83e43bbec..eb35d913f 100644
--- a/docs/tracks/en/dashboard.md
+++ b/docs/tracks/en/dashboard.md
@@ -16,7 +16,7 @@ trackSlugEN: conversational-commerce
 
 On the Dashboard page, VTEX store owners have access to metrics from the [VTEX Conversational Commerce](https://help.vtex.com/en/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/1NwwADrU70v3roPUV7dWxI) channel. In this dashboard, you can view the sales performance and session indicators, filter them by period and export them to a CSV file.
 
-![Conversational Commerce Analytics Panel](//images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/d138299cada7a34e32a0a5189ee1a5f7/Conversational_Commerce_Analytics_Panel_EN.png)
+![Conversational Commerce Analytics Panel](https://images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/d138299cada7a34e32a0a5189ee1a5f7/Conversational_Commerce_Analytics_Panel_EN.png)
 
 ## Data
 
diff --git a/docs/tracks/en/delivery.md b/docs/tracks/en/delivery.md
index 6fa611df6..426f24e0d 100644
--- a/docs/tracks/en/delivery.md
+++ b/docs/tracks/en/delivery.md
@@ -27,18 +27,18 @@ You can choose between:
 - Pick up in a store.
 - Customize by item.
 
-![entrega-2-en](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/6acc2ea35a43a1056fc26336baff9db6/entrega-2-en.png)
+![entrega-2-en](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/6acc2ea35a43a1056fc26336baff9db6/entrega-2-en.png)
 
 ### Pickup points
 
 For pickup point options, the system selects the stores that have the SKUs in stock and shows the store closest to the customer's zip code, as a suggestion. If the sales associate wants to change the store where the customer will pick up the items, they just need to click the `Change pickup point` button.
 
-![entrega-retirada-en](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/f842bfa6851d45177338b3241e7c350c/entrega-retirada-en.png)
+![entrega-retirada-en](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/f842bfa6851d45177338b3241e7c350c/entrega-retirada-en.png)
 
 When choosing to change the pickup point, the sales associate first has access to the pickup point suggested by the system. To see all available pickup points, click `View all pickup points`.
 
-![31. VTEX Sales App - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
+![31. VTEX Sales App - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
 
 The app will then show the list of pick-up points ordered by the shortest distance from the customer's zip code. It's also possible to choose a pickup point on the map.
 
-![31. VTEX Sales App - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
+![31. VTEX Sales App - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
diff --git a/docs/tracks/en/detaching-skus-by-specification.md b/docs/tracks/en/detaching-skus-by-specification.md
index 45720af92..175f22bae 100644
--- a/docs/tracks/en/detaching-skus-by-specification.md
+++ b/docs/tracks/en/detaching-skus-by-specification.md
@@ -24,7 +24,7 @@ This tool is useful for clothing stores as it allows you to display the products
 
 See the following example of detaching SKUs by color. In the image below, the featured sandals are available in two different colors in the search results:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.</p></div>
diff --git a/docs/tracks/en/enabling-2-factor-authentication-login.md b/docs/tracks/en/enabling-2-factor-authentication-login.md
index 7a2145f06..5ac510e52 100644
--- a/docs/tracks/en/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/en/enabling-2-factor-authentication-login.md
@@ -32,7 +32,7 @@ There are two authentication options:
 - __App Google__ (key generated by an authentication app)
 - __SMS Message__ (key sent by text message)
 
-![2FA - Select - EN](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
+![2FA - Select - EN](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
 
 <div class="alert alert-warning">
   We recommend you to use a<a href="#enabling-2fa-por-aplicativo">authentication application</a> to prevent failures in your telephone provider from making your login impossible. Though the app, the access key will always be available for use.
@@ -48,17 +48,17 @@ To use a key generated by authentication application:
 
 1. Download the application **Google Authenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)).
 
-  ![2FA - App Download - EN](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
+  ![2FA - App Download - EN](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
 
 2. Use the application to read the QR Code with your phone's camera.
 
-  ![2FA - App QR Code - EN](//images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/69de792a6a67c42dca1f35570dbaa562/2FA_-_App_QR_Code_-_EN.png)
+  ![2FA - App QR Code - EN](https://images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/69de792a6a67c42dca1f35570dbaa562/2FA_-_App_QR_Code_-_EN.png)
 
 3. Your VTEX account will be added to the application, with a 6-digit code. Enter the code to finish your login.
 
   *The app code is regularly updated. It will not be necessary to memorize it, go to the application whenever you need it.*
 
-  ![2FA - App Insert Code - EN](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
+  ![2FA - App Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
 
 <div class="alert alert-info">
 If you log in using your email and password on the same computer, you will be asked for your access key every 3 days. When this happens, check the code in the application.
@@ -70,11 +70,11 @@ To use a key sent by text message:
 
 1. enter your phone number to receive the code by SMS - don't forget to enter your country and area code.
 
-  ![2FA - SMS Insert Phone - EN](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
+  ![2FA - SMS Insert Phone - EN](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
 
 2. You will receive a text message from VTEX on the indicated phone. Enter the 6-digit key to finish your login.
 
-   ![2FA - SMS Insert Code - EN](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
+   ![2FA - SMS Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
 
  <div class="alert alert-warning">
 We cannot guarantee that your telephone company will be able to deliver the access key whenever necessary. If the VTEX text message does not arrive, try resending the code or <a href="#enabling-2fa-through-an-app" >enable the 2FA per-application</a>.
@@ -86,10 +86,10 @@ To change the two-step verification settings:
 
 1. Access your user settings by clicking on the circle with your initials in the top-right corner of the Admin.
 
-  ![2FA - User Initials - EN](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
+  ![2FA - User Initials - EN](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
 
 2. Click **2-step verification** to see your settings.
 
-  ![2FA - My User - EN](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
+  ![2FA - My User - EN](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
 
 3. You can then change your settings by following similar steps as those described in the sections above to enable 2FA via [SMS](#enabling-2fa-via-sms) and [application](#enable-o-2fa-by-application). 
diff --git a/docs/tracks/en/enabling-a-sales-rep-code.md b/docs/tracks/en/enabling-a-sales-rep-code.md
index d67aeefac..1b9af7ed6 100644
--- a/docs/tracks/en/enabling-a-sales-rep-code.md
+++ b/docs/tracks/en/enabling-a-sales-rep-code.md
@@ -42,7 +42,7 @@ After following these recommendations, access the __Store setup__ module. Then g
 
 On the right side of the screen, you will see the `checkout-instore-custom.js` file. 
 
-![codevendorEN](//images.ctfassets.net/alneenqid6w5/71ZvVaWtn6hk5mYoISKE1y/2f4f5e201f6bc9b53fc694f7d70e05f3/codevendorEN.png)
+![codevendorEN](https://images.ctfassets.net/alneenqid6w5/71ZvVaWtn6hk5mYoISKE1y/2f4f5e201f6bc9b53fc694f7d70e05f3/codevendorEN.png)
 
 Open the file and add the following piece of code to the `window.INSTORE_CONFIG` object:
 
@@ -64,7 +64,7 @@ The properties of the `window.INSTORE_CONFIG` object must be filled in according
 
 Click on the __Save__ blue button at the top of the page. 
 
-![codevendor2EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4T3vxA5Yatu9icLNPGuyCX/f456976ff81339225eef6bd0c458e6db/codevendor2EN.png)
+![codevendor2EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4T3vxA5Yatu9icLNPGuyCX/f456976ff81339225eef6bd0c458e6db/codevendor2EN.png)
 
 ## Understanding the priorities
 
diff --git a/docs/tracks/en/enabling-cart-transfer-between-devices.md b/docs/tracks/en/enabling-cart-transfer-between-devices.md
index 6af1ec564..b42e2f905 100644
--- a/docs/tracks/en/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/en/enabling-cart-transfer-between-devices.md
@@ -34,11 +34,11 @@ window.INSTORE_CONFIG = {
 
 After making this change, open the inStore menu and update the data by clicking on the __Reset app local data__ button. Once this is done, a slider will appear at the bottom of the inStore identification page:
 
-![24. Enable cart transfer between devices - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6n8QGjNTdsUv8LYa5BS9k4/adb1f076df8c7c02a7210249f258016f/24._Enable_cart_transfer_between_devices_-_1_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6n8QGjNTdsUv8LYa5BS9k4/adb1f076df8c7c02a7210249f258016f/24._Enable_cart_transfer_between_devices_-_1_-_EN.png_h_250)
 
 When you drag the screen to the right, you will see the screen for __Cart Capture__, as shown in the image below.
 
-![24. Enable cart transfer between devices - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4HFA0E3oefpFShXIpygidj/63c8ce16230f02347fe36420fd578d4d/24._Enable_cart_transfer_between_devices_-_2_-_EN.png_h_250)
 
 On this screen, you can capture a cart using one of three methods:
 - Cart code
@@ -49,4 +49,4 @@ On this screen, you can capture a cart using one of three methods:
 
 For the salesperson to share a cart, they can generate a numeric code or a QR Code. To do this, while on the cart screen, just click on the __Transfer__ button. See an example in the image below.
 
-![24. Enable cart transfer between devices - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
+![24. Enable cart transfer between devices - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2X6CjDIIvcp87PEln8076S/8e728587064d10fcd9caae506a6a963c/24._Enable_cart_transfer_between_devices_-_3_-_EN.png_h_250)
diff --git a/docs/tracks/en/enabling-product-recommendations.md b/docs/tracks/en/enabling-product-recommendations.md
index b10cd0bf9..aa03e371c 100644
--- a/docs/tracks/en/enabling-product-recommendations.md
+++ b/docs/tracks/en/enabling-product-recommendations.md
@@ -28,7 +28,7 @@ If you want to hide these recommendations, you need to edit the files `checkout-
 
 Like the inStore customization JavaScript file, `checkout-instore-custom.css` must be accessed through the VTEX administrative panel (as explained in the [inStore Customizations article](https://help.tex.com/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/4mwdBrFsmE2EPE0FzgX28b)).
 
-![25. Enable product recommendations - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/tPaSFJCJ0k3mk1GJh14r0/339b836008564c70f192820041a9df62/25._Enable_product_recommendations_-_1_-_EN.png_h_250)
+![25. Enable product recommendations - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/tPaSFJCJ0k3mk1GJh14r0/339b836008564c70f192820041a9df62/25._Enable_product_recommendations_-_1_-_EN.png_h_250)
 
 In the `checkout-instore-custom.css` file, include the following CSS rule:
 
diff --git a/docs/tracks/en/explained-search.md b/docs/tracks/en/explained-search.md
index 5fda158b5..d772c866b 100644
--- a/docs/tracks/en/explained-search.md
+++ b/docs/tracks/en/explained-search.md
@@ -26,5 +26,5 @@ Follow the steps below to access it:
 1. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
 2. Under **Intelligent Search**, click __Explained Search__. 
 
-![Explained Search](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
+![Explained Search](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
 
diff --git a/docs/tracks/en/extensions-hub-1.md b/docs/tracks/en/extensions-hub-1.md
index 5fdf4d00c..fb8e6b95b 100644
--- a/docs/tracks/en/extensions-hub-1.md
+++ b/docs/tracks/en/extensions-hub-1.md
@@ -18,6 +18,6 @@ The Extensions Hub is an Admin section that groups all extension information and
 
 To access the Extensions Hub, go to the left-side menu in the Admin and click the **Extensions** icon at the top.
 
-![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
+![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/3834f464b390752e71c65d675f6d4361/Extensions_Hub_panel_EN.png)
 
 You can find three pages in the Extensions Hub section: **App Store**, **App Management**, and **Partners**. Documentation on each of these pages can be found in the articles below.
diff --git a/docs/tracks/en/extensions-hub-app-store.md b/docs/tracks/en/extensions-hub-app-store.md
index da2d2f8f1..224a9954b 100644
--- a/docs/tracks/en/extensions-hub-app-store.md
+++ b/docs/tracks/en/extensions-hub-app-store.md
@@ -18,7 +18,7 @@ The App Store is the Admin page where you can search, view and get apps to expan
 
 ## Home page
 
-![Extensions Hub App Store home page](//images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/3ee2d2f5b9ece590e163aad7fb5123ea/Extensions_Hub_App_Store_home_page_EN.png)
+![Extensions Hub App Store home page](https://images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/3ee2d2f5b9ece590e163aad7fb5123ea/Extensions_Hub_App_Store_home_page_EN.png)
 
 When you log in to the store, you will see the home page with the following available options:
 
@@ -28,13 +28,13 @@ When you log in to the store, you will see the home page with the following avai
 
 ## Search
 
-![Extensions Hub App Store search](//images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/d71df4490f5671670f04c6786ccc182f/Extensions_Hub_App_Store_search_EN.png)
+![Extensions Hub App Store search](https://images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/d71df4490f5671670f04c6786ccc182f/Extensions_Hub_App_Store_search_EN.png)
 
 You can search for an app by typing its name in the search text box and pressing `Enter`. Then, you will be redirected to the search results page. The results will be the apps whose names match the text you entered in the search. The apps are displayed as square cards, where you can see the app name, headline, and price. Clicking an app will take you to the [app page](#app-page).
 
 ## App page
 
-![Extensions Hub App Store app page](//images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/5b4946289b0a1ec0a29b9e12e1b94d69/Extensions_Hub_App_Store_app_page_EN.png)
+![Extensions Hub App Store app page](https://images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/5b4946289b0a1ec0a29b9e12e1b94d69/Extensions_Hub_App_Store_app_page_EN.png)
 
 When you click an app on the home page or in the search results, you will be redirected to the app page. On this page, you will find detailed information about the app, including its price and the option to acquire it.
 
diff --git a/docs/tracks/en/filter-orders-by-vendor.md b/docs/tracks/en/filter-orders-by-vendor.md
index 0dc57bc7d..5c1257a8b 100644
--- a/docs/tracks/en/filter-orders-by-vendor.md
+++ b/docs/tracks/en/filter-orders-by-vendor.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-setup
 
 With inStore you can see the listing of all completed orders in a store:
 
-![pedidos finalizados](//images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
+![pedidos finalizados](https://images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
 
 However, sometimes it makes sense for a sales representative to see only the orders made by him. To enable this option you need to edit the `checkout-instore-custom.js` file in the Portal Admin. Because it is a JavaScript present in several streams of application use, it's important that you have programming knowledge before changing it, to avoid breaking other features.
 
@@ -37,4 +37,4 @@ __IMPORTANT__: Do not remove any of the other properties present in the `window.
 
 After reloading inStore the result should be as follows:
 
-![pedidos finalizados filtrados por vendedor](//images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
+![pedidos finalizados filtrados por vendedor](https://images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
diff --git a/docs/tracks/en/frontend-implementation.md b/docs/tracks/en/frontend-implementation.md
index 4f0c9cac5..e69089247 100644
--- a/docs/tracks/en/frontend-implementation.md
+++ b/docs/tracks/en/frontend-implementation.md
@@ -93,7 +93,7 @@ When talking about frontend implementation, remember that [VTEX IO](https://deve
 
 This means that with VTEX IO, you develop your code locally. However, when it comes to deploying and running the store, VTEX IO manages the infrastructure, CI/CD, and security and takes care of the deployment process. The image below shows how these concepts relate to each other:
 
-![Frontend development architecture](//images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/9d5da1e9f3ba8d7fe3f8808a0e8d639e/frontend_image1_EN.png)
+![Frontend development architecture](https://images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/9d5da1e9f3ba8d7fe3f8808a0e8d639e/frontend_image1_EN.png)
 
 ### Store Framework main features
 
@@ -230,7 +230,7 @@ The development team must start a new project with FastStore through the [Onboar
 - *Product Details Page* (PDP)
 - *Minicart*
 
-![FastStore template](//images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
+![FastStore template](https://images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
 
 #### FastStore MVP requirements
 
@@ -283,7 +283,7 @@ The development team must start a new project with Store Framework by cloning an
 - Product Listing Page (PLP)
 - Product Details Page (PDP)
 
-![Store Framework template](//images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
+![Store Framework template](https://images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
 
 #### Store Framework MVP requirements
 
diff --git a/docs/tracks/en/frontend.md b/docs/tracks/en/frontend.md
index 5f9c740a8..3892e20df 100644
--- a/docs/tracks/en/frontend.md
+++ b/docs/tracks/en/frontend.md
@@ -26,7 +26,7 @@ The way this feature extension happens is through VTEX apps that are available g
 
 Store Framework is a solution for building storefronts that leverages VTEX IO. Using it, you can rely on the user-friendly interface of [Site Editor](https://help.vtex.com/en/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) and easily manage store content.
 
-![vtex io](//images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5b55c0f934c47034373e47f9be09c754/image3.png)
+![vtex io](https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5b55c0f934c47034373e47f9be09c754/image3.png)
 
 Stores created with Store Framework also include: 
 - **[Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)**: Search tool that corrects spelling errors and enables conditional rules for displaying the search result.
diff --git a/docs/tracks/en/getting-started-with-logistics.md b/docs/tracks/en/getting-started-with-logistics.md
index 480a47eb6..d5ab89c2f 100644
--- a/docs/tracks/en/getting-started-with-logistics.md
+++ b/docs/tracks/en/getting-started-with-logistics.md
@@ -56,7 +56,7 @@ Basically, the **Inventory & shipping** module is divided into the following sec
 * **Settings**: General logistics settings, such as enabling critical stock notification.
 * **[Pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R)**: For listing physical locations where customers can pick up their orders.
 
-![estoque e entregaEN](//images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/8286563b415555a4ab5e56cb8e6e290c/estoque_e_entregaEN.png)
+![estoque e entregaEN](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/8286563b415555a4ab5e56cb8e6e290c/estoque_e_entregaEN.png)
 
 <div class = "alert alert-info"> Clients using <a href="https://vtex.com/us-en/">VTEX Shipping Network</a> can access this feature in the Inventory & shipping module.
 </div>
diff --git a/docs/tracks/en/go-live-process.md b/docs/tracks/en/go-live-process.md
index 873b540b7..7a5515151 100644
--- a/docs/tracks/en/go-live-process.md
+++ b/docs/tracks/en/go-live-process.md
@@ -18,7 +18,7 @@ If you have [configured your store's operation](https://help.vtex.com/pt/tracks)
 
 Here you will find detailed step-by-step instructions on how to go live with your store.
 
-![Go-live](//images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/b1f21c5f9b94732df8e7ca5fd3b6ed69/go_live_en.jpg)
+![Go-live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/b1f21c5f9b94732df8e7ca5fd3b6ed69/go_live_en.jpg)
 
 <div class = "alert alert-info">
 Note that a store in production is different from an account in production. In general, to have a store in production, you need to put the account in production and set up DNS pointing. See below all the steps involved in this process.
@@ -28,7 +28,7 @@ Note that a store in production is different from an account in production. In g
 
 Before going live, you need to ensure that you have set up all configurations for your store to run smoothly.
 
-Copy this [Store configuration checklist](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/be48d84768e5fb014f3903ad23927a11/Store_configuration_checklist_EN.xlsx) and check if you have configured each item according to your desired operation.
+Copy this [Store configuration checklist](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/be48d84768e5fb014f3903ad23927a11/Store_configuration_checklist_EN.xlsx) and check if you have configured each item according to your desired operation.
 
 <div class="alert alert-warning">
 The checklist above lists the basic features and configurations required to run a VTEX store. It is your team's responsibility to determine which features to implement in your store and how to configure them to create the desired store experience. Therefore, this list may only cover some of the features your store uses, and you must check all aspects of your store's operation, even if they are not on the suggested list.
diff --git a/docs/tracks/en/google-pay.md b/docs/tracks/en/google-pay.md
index d856da80d..6ff1bcd4d 100644
--- a/docs/tracks/en/google-pay.md
+++ b/docs/tracks/en/google-pay.md
@@ -33,7 +33,7 @@ To enable Google Pay, follow the steps below.
 <p>The card brands supported by the Google Pay extension are the ones configured in the payment conditions.</p>
 </div>
 
-![google-pay-checkout-en](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/2857562e61a935524807632c23be2e91/Screenshot_2024-08-01_at_14.21.39.png)
+![google-pay-checkout-en](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/2857562e61a935524807632c23be2e91/Screenshot_2024-08-01_at_14.21.39.png)
 
 Google Pay will then be available in your VTEX store's checkout as a new payment method. It may take around 10 minutes to be implemented.
 
@@ -58,11 +58,11 @@ To use Google Pay, you must meet the following requirements:
 
 To view transactions that have been completed with Google Pay, please follow the steps described in the article [Viewing transaction details](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy). In the search bar of the transactions page, type **Google Pay** to filter the transactions carried out with this type of payment.
 
-![Google Pay Transaction_1](//images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/e1521f4f47aff56a64d808f2f450ce38/Google_Pay_Transaction1_EN.png)
+![Google Pay Transaction_1](https://images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/e1521f4f47aff56a64d808f2f450ce38/Google_Pay_Transaction1_EN.png)
 
 After accessing the desired transaction, click on `+ Information` to verify the **Google Pay** information described in the `paymentOrigin` field.
 
-![Google Pay Transaction_2](//images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/a565b60f7ca5f541c836553140261985/Google_Pay_Transaction2_EN.png)
+![Google Pay Transaction_2](https://images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/a565b60f7ca5f541c836553140261985/Google_Pay_Transaction2_EN.png)
 
 <div class="alert alert-warning">
   <p>It is also possible to identify transactions made with Google Pay through the <b>All Orders</b> page in Admin. You just need to select the desired search period, <a href="https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">export the orders</a> in a report in .csv and locate the Google Pay information in the "payment origin" field.</p>
diff --git a/docs/tracks/en/google-shopping-marketplace.md b/docs/tracks/en/google-shopping-marketplace.md
index d5f9a5b6b..4026c3c2a 100644
--- a/docs/tracks/en/google-shopping-marketplace.md
+++ b/docs/tracks/en/google-shopping-marketplace.md
@@ -16,7 +16,7 @@ trackSlugEN: integrating-with-google-shopping
 
 [Google Shopping](https://shopping.google.com/) is a platform that displays product offers in free, organic listings through Google searches. It is a price comparison and tracking service that displays local products for free in search results.
 
-![Google Shopping](//images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/93da7aae0e11388851c2d861817e73d5/logo_Google_shopping.png)
+![Google Shopping](https://images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/93da7aae0e11388851c2d861817e73d5/logo_Google_shopping.png)
 
 Using Google Shopping, you can display to potential customers some of the attributes of your products, such as image, title, price, and the name of your store.
 
diff --git a/docs/tracks/en/hide-product-suggestions-recommendation.md b/docs/tracks/en/hide-product-suggestions-recommendation.md
index 356ea7ac2..a4e273cd6 100644
--- a/docs/tracks/en/hide-product-suggestions-recommendation.md
+++ b/docs/tracks/en/hide-product-suggestions-recommendation.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-setup
 
 By default inStore includes a list of suggested products in the cart and in the product page.
 
-![inStore recommendation](//images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
+![inStore recommendation](https://images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
 
 If you want to hide the recommendations, you need to edit the `checkout-instore-custom.css` and `checkout-instore-custom.js` files in the Portal admin. This files are used across the application, so it is important that you have some programming knowledge before editing them, to avoid breaking other functionalities.
 
diff --git a/docs/tracks/en/how-a-split-payment-transaction-works.md b/docs/tracks/en/how-a-split-payment-transaction-works.md
index 0d0d45097..3ca6b708c 100644
--- a/docs/tracks/en/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/en/how-a-split-payment-transaction-works.md
@@ -59,4 +59,4 @@ The $ 6.50 will be split between the marketplace and the acquirer. As the MDR wa
 
 Check the diagram below:
 
-![Payment Split](//images.ctfassets.net/alneenqid6w5/71DjeU0CjjxlDE1qrwr3n9/c228dc62dc40e68c34337c0d21fc8cce/Split-EN.png)
+![Payment Split](https://images.ctfassets.net/alneenqid6w5/71DjeU0CjjxlDE1qrwr3n9/c228dc62dc40e68c34337c0d21fc8cce/Split-EN.png)
diff --git a/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md b/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md
index f0778742c..e0a99f2a2 100644
--- a/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md
+++ b/docs/tracks/en/how-to-add-a-custom-text-in-the-printout-of-the-order.md
@@ -33,7 +33,7 @@ After reloading the inStore, when you print an order you will see that extra tex
 Quick Example:
 
 Before adding the extra text we would have an impression as follows:
-![inStore recommended text before](//images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
+![inStore recommended text before](https://images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
 
 By changing the `checkout-instore-custom.js` file by putting the following extra text:
 
@@ -44,4 +44,4 @@ window.INSTORE_CONFIG = {
 ```
 
 Now when the order is printed, we will have:
-![inStore recommended text after](//images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
+![inStore recommended text after](https://images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
diff --git a/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md b/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md
index a97680411..2073d83fd 100644
--- a/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md
+++ b/docs/tracks/en/how-to-change-the-sales-policy-used-by-instore.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-setup
 
 If you have set up your store using the __Easy Setup__ flow, a store for you has already been created in the __Stores Admin__ within VTEX VTable (https://{{AccountName}}.myvtex.com/admin/vtable).
 
-![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Click __Stores Admin__ to open the table where you will see the physical stores.
 
@@ -24,7 +24,7 @@ If you have not used the __Easy Setup__ and so don't see any registered stores,
 
 If you have already registered a store through __Easy Setup__, you will see the registry of this store created as in the following image.
 
-![vtable-admin-das-lojas-2](//images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
+![vtable-admin-das-lojas-2](https://images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
 
 To change any data, including the store's sales policy, simply change the related cell and then click the __Save__ button.
 
diff --git a/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
index f50a6f3fe..1d6b56d1f 100644
--- a/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
@@ -27,7 +27,7 @@ Today this configuration is included in the portal administrator, more specifica
 
 To enable the _“Configure device”_ option, you must find the **_window.INSTORE_CONFIG_** object present in this file and add the **_configureDeviceEnabled_** property with the value **_true_**, and also add the **_printingConfig_** object to the **_printByBroker_** property with the value true, so that inStore allows you to use the option within the menu, as shown in the example image below:
 
-![EN-Configurar dispositivo](//images.ctfassets.net/alneenqid6w5/7sjOnFRRd3FFBFM4MQej7m/692f871ee51737c132a6df68e39591bd/EN-Configurar_dispositivo.png)
+![EN-Configurar dispositivo](https://images.ctfassets.net/alneenqid6w5/7sjOnFRRd3FFBFM4MQej7m/692f871ee51737c132a6df68e39591bd/EN-Configurar_dispositivo.png)
 
 Do not delete any of the other properties included in this object. The result should be something like:
 
@@ -64,7 +64,7 @@ printPageAutomatically: true
   3. In the “Settings” block inside the inStore menu, the option “Configure device” should appear. Click there.
   4. You will find the summary of the configured device. If this is the first time, the information will be empty. If a device has been configured previously, some information about the device will appear _(Device Name and Standard Printer)_. Click on the "Edit" option.
   
-![EN-Device via Broadcast](//images.ctfassets.net/alneenqid6w5/7DuIhb5gjLHpCoLx48DMvl/d51a551e1d23f6dae131ec9b34c184b7/EN-Device_via_Broadcast.png)
+![EN-Device via Broadcast](https://images.ctfassets.net/alneenqid6w5/7DuIhb5gjLHpCoLx48DMvl/d51a551e1d23f6dae131ec9b34c184b7/EN-Device_via_Broadcast.png)
 
   5. A form will appear indicating the data of _AppKey_, _AppToken_ and the name by which you want to identify the device. After entering this data, click on “Configure”.
   6. Finally, after including the above data, it will be possible to select the printer from the list of options. The idea is to select one of these options and then click on “Configure” again.
diff --git a/docs/tracks/en/how-to-register-your-salespersons-on-vtex-instore.md b/docs/tracks/en/how-to-register-your-salespersons-on-vtex-instore.md
index e007e8298..b8295d41e 100644
--- a/docs/tracks/en/how-to-register-your-salespersons-on-vtex-instore.md
+++ b/docs/tracks/en/how-to-register-your-salespersons-on-vtex-instore.md
@@ -24,19 +24,19 @@ Registering a salesperson will let the app associate the person identified with
 2. Load the prices, payment conditions and product availability regarding the store in which the salesperson operates.
 
 The salesperson identification is obtained as shown in the image below:
-![identificacao-vendedor](//images.contentful.com/alneenqid6w5/2LhlUtsEYouEY4i4iYOIOq/d556be06047c26ee85f392ba7256f9f8/identificacao-vendedor.png)
+![identificacao-vendedor](https://images.contentful.com/alneenqid6w5/2LhlUtsEYouEY4i4iYOIOq/d556be06047c26ee85f392ba7256f9f8/identificacao-vendedor.png)
 
 To register the salesperons identified in the screen above, just access your Masterdata. After accessing the Masterdata, search for the area named `Profile System`. In this area, search for the word `Vendedores` and click on `listar` as shown in the image below.
-![masterdata-home-vendedores](//images.contentful.com/alneenqid6w5/32iOuRESyIwEwSE4WcEWmu/b64645e6f940399933df3db5b40d6a4f/masterdata-home-vendedores.png)
+![masterdata-home-vendedores](https://images.contentful.com/alneenqid6w5/32iOuRESyIwEwSE4WcEWmu/b64645e6f940399933df3db5b40d6a4f/masterdata-home-vendedores.png)
 
 By clicking on `listar`, a list of registered salespersons will be displayed as shown in the image below. Click on `Novo` to register a new salesperson.
-![masterdata-lista-vendedores](//images.contentful.com/alneenqid6w5/xsepOCP9Dwiys6MKkQGY4/4717c2ff41b7b52a43b549294877713f/masterdata-lista-vendedores.png)
+![masterdata-lista-vendedores](https://images.contentful.com/alneenqid6w5/xsepOCP9Dwiys6MKkQGY4/4717c2ff41b7b52a43b549294877713f/masterdata-lista-vendedores.png)
 
 Fill out the form with the salesperson’s data.  In the `Loja` field, start typing the store's name and a chek box will be displayed.  When the store name is displayed, click on the name, check whether the information is correct, and then, click on `Salvar`.
-![masterdata-novo-vendedor](//images.contentful.com/alneenqid6w5/7mfVtDbemWWA6yqqYIQgwC/a498d9fbd2dcfbe87546711d8d8c7a36/masterdata-novo-vendedor.png)
+![masterdata-novo-vendedor](https://images.contentful.com/alneenqid6w5/7mfVtDbemWWA6yqqYIQgwC/a498d9fbd2dcfbe87546711d8d8c7a36/masterdata-novo-vendedor.png)
 
 It will also be necessary to set up an access profile for this person in your License Manager. Just click on `Usuários` and create a new user with the same e-mail informed in Masterdata. The Access Profile to be added is `Vendedor inStore`. Then, do not forget to click on `Salvar`.
 
 *New salespersons will have to create and confirm their passwords through an e-mail that will be sent to each registered user.*
 
-![license-manager-novo-vendedor](//images.contentful.com/alneenqid6w5/98ppRH68esOwU2cWSiM4w/501c79f9cc247103868a026581f7573c/license-manager-novo-vendedor.png)
+![license-manager-novo-vendedor](https://images.contentful.com/alneenqid6w5/98ppRH68esOwU2cWSiM4w/501c79f9cc247103868a026581f7573c/license-manager-novo-vendedor.png)
diff --git a/docs/tracks/en/import-orders-from-lengow.md b/docs/tracks/en/import-orders-from-lengow.md
index e2931090e..8da3bcebf 100644
--- a/docs/tracks/en/import-orders-from-lengow.md
+++ b/docs/tracks/en/import-orders-from-lengow.md
@@ -30,6 +30,6 @@ To import orders automatically, use any scheduling service to perform a periodic
 
 The image below provides an example of what that would look like in [EasyCron](https://www.easycron.com/):
 
-![Lengow - EasyCron](//images.ctfassets.net/alneenqid6w5/34iwIOlV3gTIxg8JipHwu5/4d5e6b4419ea69cb66dddb923082b374/image14.png)
+![Lengow - EasyCron](https://images.ctfassets.net/alneenqid6w5/34iwIOlV3gTIxg8JipHwu5/4d5e6b4419ea69cb66dddb923082b374/image14.png)
 
 For more information on how to set up cron jobs using EasyCron, refer to the [FAQ](https://www.easycron.com/faq) available in their website.
diff --git a/docs/tracks/en/including-order-variables-in-email-template.md b/docs/tracks/en/including-order-variables-in-email-template.md
index 72fac66f0..4c0ecd742 100644
--- a/docs/tracks/en/including-order-variables-in-email-template.md
+++ b/docs/tracks/en/including-order-variables-in-email-template.md
@@ -30,7 +30,7 @@ Let's say you want to enter the carrier's name in the order sent email.
 
 To do this, go to the order sent template and, in the __JSON Data__ field, look for the `courier` property.
 
-![EN Incluir variáveis do pedido no template de e-mail - 1](//images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/338873a8e5b2558b0fa0df9c2bc3b4c6/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)
+![EN Incluir variáveis do pedido no template de e-mail - 1](https://images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/338873a8e5b2558b0fa0df9c2bc3b4c6/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)
 
 The value entered for this property is just an example, but you can use it in the __HTML__ field so that when the email is sent, the customer will see the carrier actually responsible for delivering the order.
 
@@ -38,6 +38,6 @@ Note that the `courier` property is inside the `package` object. Therefore, you
 
 `{{package.courier}}`
 
-![EN Incluir variáveis do pedido no template de e-mail - 2](//images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/cf78d7e9f4408c7eec101e5768aaef4b/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)
+![EN Incluir variáveis do pedido no template de e-mail - 2](https://images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/cf78d7e9f4408c7eec101e5768aaef4b/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)
 
 See that the example value ("Carrier Teste Courier S.A.") was inserted in the preview screen, below the __HTML__ and __JSON Data__ fields.
diff --git a/docs/tracks/en/indexing-history.md b/docs/tracks/en/indexing-history.md
index 04ac40139..59c840205 100644
--- a/docs/tracks/en/indexing-history.md
+++ b/docs/tracks/en/indexing-history.md
@@ -16,12 +16,12 @@ trackSlugEN: vtex-intelligent-search
 
 **Indexing history** is the page that monitors the synchronization status of all products in the Catalog sent to Intelligent Search. It provides a broad view of the indexing progress of your store.
 
-![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+![Histórico da Indexação 1 - EN](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
 
 The **Indexing status** section displays the following information:
 
 * **Average indexing time:** The average time for products to be indexed, from the time the system received the change notification to the in-store update. Indexing time performance is measured by a green (healthy) or red (bad) dot. 
-![Historico Indexação 2 - EN](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
+![Historico Indexação 2 - EN](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
 * **Products in store:** Quantity of products with up-to-date information currently displayed in the store.
 * **Indexing status share:** The percentage of products in each indexing step. Status breakdown performance is measured by a green (healthy) or red (bad) dot. The steps displayed are:
     * **Updated:** Latest product update has been entered in the store.
@@ -32,15 +32,15 @@ You can filter the list of indexed products for a custom view. It is important t
 
 To filter the list of indexed products, click on `Filter` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
 
 If you filter by `Status` you can select which status you want to filter by, which could be `Updated`, `Updating`, `Error`.
 
-![Historico indexação 4 - EN](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
+![Historico indexação 4 - EN](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
 
 If you filter by `Indexing time` you can select whether the time interval `Is greater than`, `Is equal to or greater than`, `Is shorter than` or `Is equal to or less than` a defined time.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
 
 After defining the filter, click `Apply` to activate it. 
 
@@ -50,17 +50,17 @@ You can also filter the products displayed in the listing by **ID**, **Last upda
 
 If you want more information about the indexing of a specific product, you can click on the product row in the table to access a page that contains more details, as illustrated below.
 
-![Historico indexação 6 - EN](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
+![Historico indexação 6 - EN](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
 
 In addition to the information displayed in the product list, you can also see:
 
 * **Indexing time:** Is an entry of how long the product indexing lasted using the `hh:mm:ss` format`.
 * **Indexing timeline:** Shows a log of every status change with date and time. You can view more details of each step by clicking the <i class="fa-solid fa-chevron-down"></i> icon.
 
-![Historico indexação 7 - EN](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
+![Historico indexação 7 - EN](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
 
 It is possible to manually reindex a product without having to update the entry. To reindex a product, click <i class="fa-solid fa-arrows-rotate"></i> `Reindex`. Only products in **Updated** status can be indexed.
 
 You can access the product **Indexing history**, a list with the date and time of each update performed. Therefore, it is possible to have a record of every change that was made to the product. To access it, click <i class="fa-solid fa-arrows-rotate"></i> `History`. 
 
-![Histórico da Indexação 8 - EN](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
+![Histórico da Indexação 8 - EN](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
diff --git a/docs/tracks/en/initializing-your-store-theme.md b/docs/tracks/en/initializing-your-store-theme.md
index ea7a3e527..ceb1cb6ce 100644
--- a/docs/tracks/en/initializing-your-store-theme.md
+++ b/docs/tracks/en/initializing-your-store-theme.md
@@ -27,7 +27,7 @@ Select `store-theme` and confirm that you would like to download the template pr
 
 You will then be asked important app meta information like this app's vendor, name, title, and description. Use the __account name__ you're developing in as the __vendor__. This is important so you can correctly publish this app in this account later. You can use the default values by pressing enter.
 
-![store-theme](//images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
+![store-theme](https://images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
 
 ## Understanding the app structure
 
@@ -86,7 +86,7 @@ During a `link`, any changes you make to your code are automatically uploaded an
 
 Run `vtex link`  and watch your template app be compiled and published to the account and workspace you just created.
 
-![vtex-link](//images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
+![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
 <div class="alert alert-info">
 Remember: run <code>vtex whoami</code> to make sure you are in the correct account and in a test workspace, otherwise <code>VTEX Toolbelt</code> will complain about linking directly to master.
@@ -104,4 +104,4 @@ The `{{account}}.myvtex.com` is your private domain for testing new workspaces,
 
 Congratulations on linking your first VTEX IO App!
 
-![dreamstore](//images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
+![dreamstore](https://images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
diff --git a/docs/tracks/en/inserting-and-configuring-placeholders.md b/docs/tracks/en/inserting-and-configuring-placeholders.md
index 8d5674556..23e07b877 100644
--- a/docs/tracks/en/inserting-and-configuring-placeholders.md
+++ b/docs/tracks/en/inserting-and-configuring-placeholders.md
@@ -35,14 +35,14 @@ It creates a configurable element in the part of the code where it is inserted.
 It is important to enter an `id` value. It will be the identifier of that placeholder in the system.
 
 
-![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configuring the placeholder
 
 Once the placeholder control has been inserted into the template, you can configure it in the settings of the layout that uses this template.
 
 1. Open the layout and then click on the **Settings** tab. The new placeholder should appear there, with the name equal to the id value defined in the control. For now, this placeholder is empty, meaning there are no objects inside it.
-![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. To insert an object, click on **add object**.
 3. Then choose the object type and click on the **Add** button.
 4. Finally, click on the **Save Settings** button.
@@ -51,7 +51,7 @@ You can now edit the object inserted in the placeholder.
 
 To do this, click on the pencil icon inside the object, and then click on **add content**.
 
-![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 You can now name this object, upload images to it and configure the conditions under which it will be rendered.
 
diff --git a/docs/tracks/en/installation-and-setup.md b/docs/tracks/en/installation-and-setup.md
index 6590fd91b..42fd9227b 100644
--- a/docs/tracks/en/installation-and-setup.md
+++ b/docs/tracks/en/installation-and-setup.md
@@ -40,13 +40,13 @@ To get started, we will fill out basic settings that allow VTEX and Lengow to co
 
 Once this is done, as seen in the image below, press **Save** to store the settings and move on to the next step.
 
-![Lengow Basic Setup](//images.ctfassets.net/alneenqid6w5/47hHUySqAFsoAXKSX0ec8N/9be820ddefcc9e6893c634d7fe627b16/Screen_Shot_2020-07-01_at_22.44.34.png)
+![Lengow Basic Setup](https://images.ctfassets.net/alneenqid6w5/47hHUySqAFsoAXKSX0ec8N/9be820ddefcc9e6893c634d7fe627b16/Screen_Shot_2020-07-01_at_22.44.34.png)
 
 ### Configure VTEX affiliate for Lengow
 
 To fill out the **Prefix to imported orders - Affilitiate ID** field you should configure an [affiliate](https://help.vtex.com/en/tutorial/configuring-affiliates--tutorials_187) for the Lengow connector in *Orders > Orders Management > Settings*. We recommend using the settings below, with LNG as the affiliate ID and your own e-mail address for notifications.
 
-![Lengow affiliate](//images.ctfassets.net/alneenqid6w5/7384AJaO2ZFcECDGFqWHPT/78a10bd0370a43cdd65116f067fc814c/image9.png)
+![Lengow affiliate](https://images.ctfassets.net/alneenqid6w5/7384AJaO2ZFcECDGFqWHPT/78a10bd0370a43cdd65116f067fc814c/image9.png)
 
 ### Get Lengow authentication credentials
 
diff --git a/docs/tracks/en/instore-basic-settings.md b/docs/tracks/en/instore-basic-settings.md
index 8b55f586e..4df951ff1 100644
--- a/docs/tracks/en/instore-basic-settings.md
+++ b/docs/tracks/en/instore-basic-settings.md
@@ -54,7 +54,7 @@ After installing, you will configure the basic settings of the VTEX Sales App ap
 
 ### Add the store address
 
-![cadastrar-loja-pt](//images.contentful.com/alneenqid6w5/51ICHIzuWsMAwPCVwQuQoB/071ec5240f968e662badf4e828954072/cadastrar-loja-pt.png)
+![cadastrar-loja-pt](https://images.contentful.com/alneenqid6w5/51ICHIzuWsMAwPCVwQuQoB/071ec5240f968e662badf4e828954072/cadastrar-loja-pt.png)
 
 On this screen, enter the name of the first physical store where VTEX Sales App will be used and the full address of the store. After filling out all the fields, click on `Confirm`.
 
@@ -64,7 +64,7 @@ If you choose to `Skip this step`, a fictitious store will be created for testin
 
 ### Adding a sales associate's email and name
 
-![registrar-vendedor-pt](//images.contentful.com/alneenqid6w5/5PvZutdPYWkm7rj4HCrlPC/0316ea7fd74dae942a64e5fdb22f3807/registrar-vendedor-pt.png)
+![registrar-vendedor-pt](https://images.contentful.com/alneenqid6w5/5PvZutdPYWkm7rj4HCrlPC/0316ea7fd74dae942a64e5fdb22f3807/registrar-vendedor-pt.png)
 
 You must define an email and a name to be used as a sales associate’s login credentials. When you are ready, click on `Confirm`.
 
@@ -80,7 +80,7 @@ If you choose to `Skip this step`, a fictitious sales associate will be created
 
 The next step is to set up the payment methods you will accept on VTEX Sales App. Enable the desired options using the <i class="fas fa-toggle-on"></i> button, as shown below.
 
-![configurar-meios-de-pagamento-pt](//images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
+![configurar-meios-de-pagamento-pt](https://images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
 
 There are two options:
 
@@ -89,7 +89,7 @@ There are two options:
 
 After selecting the desired options, click on `Confirm`. You will see the following confirmation message:
 
-![sucesso-instore-pt](//images.contentful.com/alneenqid6w5/nVSjiQuE0EXIYecELJJFQ/79a0d24adb51e7ad68f371afe5ca0491/sucesso-instore-pt.png)
+![sucesso-instore-pt](https://images.contentful.com/alneenqid6w5/nVSjiQuE0EXIYecELJJFQ/79a0d24adb51e7ad68f371afe5ca0491/sucesso-instore-pt.png)
 
 ## Configuring payment conditions
 
diff --git a/docs/tracks/en/instore-customizations.md b/docs/tracks/en/instore-customizations.md
index 1ef5eaa1e..e8cc1588b 100644
--- a/docs/tracks/en/instore-customizations.md
+++ b/docs/tracks/en/instore-customizations.md
@@ -36,11 +36,11 @@ Alternatively, you can browse to the configuration file from the VTEX Admin home
 
 In the main menu, click on __Checkout__ and then click on the store's gear symbol, as shown in the image below.
 
-![20. inStore Customizations - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6AXuX4eeuPus1uiuyFcXkp/ce21c3df39b94600d4165f0b357321c0/20._inStore_Customizations_-_1_-_EN.png_h_250)
+![20. inStore Customizations - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6AXuX4eeuPus1uiuyFcXkp/ce21c3df39b94600d4165f0b357321c0/20._inStore_Customizations_-_1_-_EN.png_h_250)
 
 Then click on the __Code__ tab and finally on the `checkout-instore-custom.js` file, which is in the file list on the right-hand side of the screen.
 
-![20. inStore Customizations - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3TCYyx8ZthAnzwDPOQYdNZ/7a31e38624df1ffa2d0f649f2d9328d2/20._inStore_Customizations_-_2_-_EN.png_h_250)
+![20. inStore Customizations - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3TCYyx8ZthAnzwDPOQYdNZ/7a31e38624df1ffa2d0f649f2d9328d2/20._inStore_Customizations_-_2_-_EN.png_h_250)
 
 ## Changing the inStore customization file
 
@@ -48,7 +48,7 @@ Then click on the __Code__ tab and finally on the `checkout-instore-custom.js` f
 
 To make any changes, simply add or modify the lines of code directly in the file edit box, in the VTEX Admin, and—once you're done— click on the __Save__ button, as shown in the image below.
 
-![20. inStore Customizations - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6gxUvg8FcYg2b7zhNpoTj8/0137d152efa66e076f438e849a5bde87/20._inStore_Customizations_-_3_-_EN.png_h_250)
+![20. inStore Customizations - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6gxUvg8FcYg2b7zhNpoTj8/0137d152efa66e076f438e849a5bde87/20._inStore_Customizations_-_3_-_EN.png_h_250)
 
 <div class="alert alert-warning">
 Always follow the customization instructions in this documentation and only make changes as indicated here.
diff --git a/docs/tracks/en/instore-login.md b/docs/tracks/en/instore-login.md
index 75f7836c8..38a5dff31 100644
--- a/docs/tracks/en/instore-login.md
+++ b/docs/tracks/en/instore-login.md
@@ -18,7 +18,7 @@ The first contact between the the physical store sales associate and VTEX Sales
 
 Here, the email and password created for the sales associate in the [Basic Setup](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO#adding-a-sales-associates-email-and-name) must be used. Remember that you cannot use emails that already have access to the administrative panel of VTEX stores.
 
-![31. inStore - Product Overview - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/60fcdfec07dcf51a556bb1a80b2d987f/instore-login-EN__1_.png)
+![31. inStore - Product Overview - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/60fcdfec07dcf51a556bb1a80b2d987f/instore-login-EN__1_.png)
 
 Upon logging in, the sales associate accesses the VTEX Sales App application specific to a VTEX account. Although it is not a common scenario, the same sales associate may be linked to more than one account. If you need to switch accounts, just log out and, on the login screen, click on `Change store`.
 
diff --git a/docs/tracks/en/instore.md b/docs/tracks/en/instore.md
index 642102f73..0d18e1816 100644
--- a/docs/tracks/en/instore.md
+++ b/docs/tracks/en/instore.md
@@ -24,7 +24,7 @@ The first contact between the the physical store salesperson and inStore happens
 
 Here, the e-mail and password created for the salesperson in the [Basic Setup](https://help.vtex.com/en/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc) must be used. Remember that you cannot use emails that already have access to the administrative panel of VTEX stores.
 
-![31. inStore - Product Overview - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
+![31. inStore - Product Overview - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
 
 Upon logging in, the salesperson accesses the inStore application specific to a VTEX account. Although it is not a common scenario, the same salesperson may be linked to more than one account. If you need to switch accounts, just log out and, on the login screen, click on __Change Store__.
 
@@ -46,7 +46,7 @@ You can [configure which identification methods you want to enable](https://help
 
 In the example image below, E-mail and CPF are enabled.
 
-![31. inStore - Product Overview - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
+![31. inStore - Product Overview - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
 
 Just enter one of these data in the field and click on the __Confirm__ button.
 
@@ -60,11 +60,11 @@ Although it is possible to cater customers without identifying them, we always r
 
 The top bar of the inStore app offers some options frequently used by the salesperson. One of them is the SKU search, available in the upper right corner.
 
-![31. inStore - Product Overview - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
+![31. inStore - Product Overview - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
 
 In inStore the search is omnichannel. That is, when doing a search in the app, the salesperson is searching both in the local inventory (of the physical store itself) and in the catalog of other physical stores and the e-commerce.
 
-![31. inStore - Product Overview - 4 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
+![31. inStore - Product Overview - 4 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
 
 The delivery and pickup availability options will be shown later, in the delivery stage.
 
@@ -72,11 +72,11 @@ The delivery and pickup availability options will be shown later, in the deliver
 
 After identifying the customer, the salesperson is taken directly to the cart. There, if you are using the desktop version of inStore, connected to a barcode reader, simply beep the products and they will appear in the cart.
 
-![31. inStore - Product Overview - 5 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
+![31. inStore - Product Overview - 5 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
 
 If the salesperson is using a tablet or smartphone, they will see a barcode reading button on the top bar of the application.
 
-![31. inStore - Product Overview - 6 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
+![31. inStore - Product Overview - 6 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
 
 When clicking on it, the salesperson can use the camera to beep a product and, with that, be automatically taken to the details screen of that product.
 
@@ -119,7 +119,7 @@ Remember that all this information refers not only to the customer's experience
 
 When clicking on the details of a product that appears in the inStore search results, or when beeping a product, the salesperson is directed to the product details screen.
 
-![31. inStore - Product Overview - 7 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
+![31. inStore - Product Overview - 7 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
 
 This screen shows the name of the product, its photo gallery, variations, description and availability. On this screen, the salesperson can add the product to the cart.
 
@@ -137,7 +137,7 @@ InStore let's you [enable a cart transfer functionality](https://help.vtex.com/e
 
 Once in an order cart, the salesperson has access to the __Transfer__ button. When clicking this button, the app shows a QR Code and a four-digit numeric code.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Another salesperson logged into the same store can then capture that cart and continue selling from their device.
 
@@ -156,21 +156,21 @@ The next screen shows the delivery options. As inStore deals with the catalog of
 
 The example below shows two options: receive all items at home or pick up at another physical store within 5 working days.
 
-![31. inStore - Product Overview - 10](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
+![31. inStore - Product Overview - 10](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
 
 ### Pick-up Points
 
 For pick-up point options, the system selects the stores that have the SKUs in stock and shows the store closest to the customer's zip code, as a suggestion. If the salesperson wants to change the store where the customer will pick up the items, they just need to click the __Change pick-up point__ button.
 
-![31. inStore - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
+![31. inStore - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
 
 When choosing to change the pick-up point, the salesperson first has access to the pick-up point suggested by the system. To see all available pick-up points, click __View all pick-up points__.
 
-![31. inStore - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
+![31. inStore - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
 
 The app will then show the list of pick-up points ordered by the shortest distance from the customer's zip code. It's also possible to choose a pick-up point on the map.
 
-![31. inStore - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
+![31. inStore - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
 
 ## 12. Payment
 
@@ -178,17 +178,17 @@ In the payment step, the salesperson will see the [payment options that have bee
 
 An important feature allowed by inStore is multiple payments. For example, by choosing Cash and then clicking __Add another payment__, the salesperson can charge part of the amount in cash and part on credit or debit card.
 
-![31. inStore - Product Overview - 14](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
+![31. inStore - Product Overview - 14](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
 
 The top bar of the payment screen allows you to add a coupon and a gift card. It also allows changing the customer ID number that will appear on the invoice.
 
-![31. inStore - Product Overview - 15](//images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
+![31. inStore - Product Overview - 15](https://images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
 
 ## 13. Order placed
 
 The salesperson can see this same screen by clicking on __Completed Orders__ in inStore's main menu or searching for the order by order number or customer.
 
-![31. inStore - Product Overview - 16](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
+![31. inStore - Product Overview - 16](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
 
 ## 14. NFC-e printing
 
diff --git a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
index a3abd66b2..605f834f8 100644
--- a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
@@ -16,7 +16,7 @@ trackSlugEN: integrating-instore-to-a-new-payment-acquirer
 
 This article aims to explain how the inStore app configures AppLinking for `payment` and `payment-reversal` actions with the acquirers' apps.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Setting fields
 
diff --git a/docs/tracks/en/integration-settings.md b/docs/tracks/en/integration-settings.md
index e41ff0756..c21995399 100644
--- a/docs/tracks/en/integration-settings.md
+++ b/docs/tracks/en/integration-settings.md
@@ -24,7 +24,7 @@ Follow the instructions to start the integration process:
 
 The indexing process will start. Once completed, the screen shown below will be displayed.
 
-![integracoes-is-en](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/20ef33f4ff2b33fca08a777d6c3c90c2/integracoes-is-en.PNG)
+![integracoes-is-en](https://images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/20ef33f4ff2b33fca08a777d6c3c90c2/integracoes-is-en.PNG)
 
 You don't need to repeat this process. After starting the integration, you can follow the indexing status on the [Indexing History](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) page.
 
diff --git a/docs/tracks/en/intelligent-synonyms.md b/docs/tracks/en/intelligent-synonyms.md
index 63c7dada5..409053c92 100644
--- a/docs/tracks/en/intelligent-synonyms.md
+++ b/docs/tracks/en/intelligent-synonyms.md
@@ -32,7 +32,7 @@ The suggestions are displayed in two categories in the list of synonyms, as show
 * **New suggestions:** Suggestions generated by the platform that have not yet been viewed.
 * **Saved suggestions:** Suggestions saved for later, as described in step 5 of the [Reviewing suggestions](#revisar-sugestoes) section.
 
-![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
+![synonym-suggestion-list-es](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
 
 You can review the suggestions and choose to save for later, decline, edit, or approve. See the steps in the next section.
 
@@ -47,7 +47,7 @@ Follow these instructions to view the synonym suggestions and choose whether to
     If you click `Not Now`, the suggestions will remain in the **New suggestions** box, indicating the number of generated suggestions. To review them, click `Review`. 
 4. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
 
-   ![synonym-suggestion-en](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
+   ![synonym-suggestion-en](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
 
 5. To review each suggestion, choose one of the following actions:
     * <i class="fas fa-bookmark"></i> **Save for Later:** Removes the suggestion from the **New suggestions** count and stores it in the **Saved suggestions** box. To review the saved suggestions later, click `Review`.
diff --git a/docs/tracks/en/intro-to-vtex-io-builders.md b/docs/tracks/en/intro-to-vtex-io-builders.md
index e4ab38d2b..1286c488a 100644
--- a/docs/tracks/en/intro-to-vtex-io-builders.md
+++ b/docs/tracks/en/intro-to-vtex-io-builders.md
@@ -19,6 +19,6 @@ Apps in VTEX IO export code or configuration to provide features or alter the be
 These pieces of code and configuration usually require some preparation or validation in order to serve their purpose. For example, React components need to have their dependencies pulled and be compiled into JavaScript bundles. 
 
 VTEX IO automatically takes care of all of these steps by implementing them as Builders. Once your app declares it uses a builder, the corresponding folder and its contents are processed by it upon linking. 
-![builders](//images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
+![builders](https://images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
 
 The store theme project uses two main builders (`store` and `styles`), but as you create apps with more advanced functionality, you will start using other, lower-level builders such as `react`, `messages`, `graphql` and `node`.
diff --git a/docs/tracks/en/introduction-to-vtex-io.md b/docs/tracks/en/introduction-to-vtex-io.md
index 153b379e3..280498881 100644
--- a/docs/tracks/en/introduction-to-vtex-io.md
+++ b/docs/tracks/en/introduction-to-vtex-io.md
@@ -22,7 +22,7 @@ In this track, we will teach you step by step how to develop an app using VTEX I
 
 See in the image below the hierarchical structure of VTEX IO:
 
-![VTEX IO Hierarchy](//images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
+![VTEX IO Hierarchy](https://images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
 
 - __Account__: To develop an app, you need to have a VTEX account.
 - __Workspaces__: These are the environments where the apps will be developed. These environments are linked to the account. You may have multiple workspaces for a single account.
diff --git a/docs/tracks/en/introduction-to-vtex.md b/docs/tracks/en/introduction-to-vtex.md
index 988ba87d5..704130b0d 100644
--- a/docs/tracks/en/introduction-to-vtex.md
+++ b/docs/tracks/en/introduction-to-vtex.md
@@ -18,7 +18,7 @@ trackSlugEN: vtex-store-overview
 
 The following image shows VTEX's solutions and possibilities, which will be covered throughout this article series:
 
-![vtex_composable_complete_EN](//images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/d4622b765ea964b60da83fd11dffe865/vtex_composable_complete_EN.png)
+![vtex_composable_complete_EN](https://images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/d4622b765ea964b60da83fd11dffe865/vtex_composable_complete_EN.png)
 
 <div class="alert alert-info">
 Besides the resources available on the Help Center and <a href="https://developers.vtex.com/">Developer Portal</a>, as well as the <a href="https://community.vtex.com/">VTEX Community</a>, our <a href="https://vtex.com/us-en/">website</a> provides additional information about the platform through <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">demo videos</a> and <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> created by our <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">partners</a>. There is also a series of <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">onboarding videos</a> (available only in Portuguese).
diff --git a/docs/tracks/en/inventory-and-shipping-module-overview.md b/docs/tracks/en/inventory-and-shipping-module-overview.md
index b29628893..a3a58b0b6 100644
--- a/docs/tracks/en/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/en/inventory-and-shipping-module-overview.md
@@ -22,7 +22,7 @@ The __Inventory and Shipping__ module is the service responsible for your store'
 
 The logistics system has several useful functionalities. These *features* allow you to come up with a shipping and inventory strategy tailored to your business. In this track's next steps, we'll have a closer look at each one of the functionalities highlighted below. In your store's admin, you'll come across the following sections: 
 
-![inventory-shipping-admin-en](//images.ctfassets.net/alneenqid6w5/1nycgD4T0mrDjbvXG9FL6u/989a48356d35c559a958073f96cc77a0/inventory-shipping-admin-en.png)
+![inventory-shipping-admin-en](https://images.ctfassets.net/alneenqid6w5/1nycgD4T0mrDjbvXG9FL6u/989a48356d35c559a958073f96cc77a0/inventory-shipping-admin-en.png)
 
 __Shipping strategy__ (Dashboard) - This section allows you to add logistics routes used for order shipping. A basic route consists of a __warehouse__,  a __loading dock__ and a __shipping policy__ (carrier).
 
diff --git a/docs/tracks/en/legacy-cms-portal.md b/docs/tracks/en/legacy-cms-portal.md
index 55d93c59f..a43a92a3b 100644
--- a/docs/tracks/en/legacy-cms-portal.md
+++ b/docs/tracks/en/legacy-cms-portal.md
@@ -18,7 +18,7 @@ trackSlugEN: cms
 
 The [Layout](https://help.vtex.com/en/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW) section allows you to create your storefront with HTML and CSS. It is organized into folders and files with specific purposes:
 
-![CMS - Layout EN](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/0e1fc8acb3b24882504c11d857508d68/cms-layout-en.png)
+![CMS - Layout EN](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/0e1fc8acb3b24882504c11d857508d68/cms-layout-en.png)
 
 - **HTML Templates:** build the HTML code and reference JavaScript and CSS files to be used in the website pages.
 
@@ -38,7 +38,7 @@ The [Layout](https://help.vtex.com/en/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW
 
 The [Settings](https://help.vtex.com/en/subcategory/cms-settings--6kovkwzMRyeOOc2iEC4suM) section allows you to configure settings related to your store website, such as its metadata, SEO tags, file types, and more. 
 
-![CMS - Settings EN](//images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/852f9d3a206658b19dc33e3e857c97d9/cms-settings-en.png)
+![CMS - Settings EN](https://images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/852f9d3a206658b19dc33e3e857c97d9/cms-settings-en.png)
 
 The **Settings** section is structured as follows.
 
@@ -68,7 +68,7 @@ These are the folders that every store needs to have in the CMS to ensure the co
 
 See below these basic folders in the CMS:
 
-![pastasObrigatorias](//images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
+![pastasObrigatorias](https://images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
 
 These folders come by default in the environment of all VTEX stores.
 
diff --git a/docs/tracks/en/live-support.md b/docs/tracks/en/live-support.md
index 6cbe1ed2d..309de69e6 100644
--- a/docs/tracks/en/live-support.md
+++ b/docs/tracks/en/live-support.md
@@ -27,12 +27,12 @@ Follow the steps below to configure your store live support business hours.
 # General settings
 
 1. Set whether you want to enable human support in your store.
- ![Live Support en](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/aeabaad112b555b4b8275ef7e682bf49/general_settings.png)
+ ![Live Support en](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/aeabaad112b555b4b8275ef7e682bf49/general_settings.png)
 
 If you choose not to provide it, you need to define an unavailability message indicating the best service channel for your customer.
- ![Mensagem de indisponibilidade](//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/029fcd7b9d0eb4f7dfe59fbb2abebcbb/unaviability.png)
+ ![Mensagem de indisponibilidade](https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/029fcd7b9d0eb4f7dfe59fbb2abebcbb/unaviability.png)
 2. Set the time zone for your live support service.
-![fuso horário en](//images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/867851568c68409ae8242293cb30bdd6/horarios_de_funcionamento_en.png)
+![fuso horário en](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/867851568c68409ae8242293cb30bdd6/horarios_de_funcionamento_en.png)
 3. Select the days and set the business hours of your live support. You can specify more than one window per weekday.
 
 <div class="alert alert-info">
diff --git a/docs/tracks/en/managing-accounts.md b/docs/tracks/en/managing-accounts.md
index a5780430a..54a9fcb06 100644
--- a/docs/tracks/en/managing-accounts.md
+++ b/docs/tracks/en/managing-accounts.md
@@ -26,7 +26,7 @@ When clicking on the name of a specific account, the __Account Details__ screen
 - [Account closure](#account-closure)
 <br>
 <br>
-![Account_EN](//images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/a9f3a550884255677d837466ec63cf3c/Contas_EN.png)
+![Account_EN](https://images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/a9f3a550884255677d837466ec63cf3c/Contas_EN.png)
 
 ## Holder
 
diff --git a/docs/tracks/en/managing-customer-credit-invoices.md b/docs/tracks/en/managing-customer-credit-invoices.md
index c97c96139..6b4aeba67 100644
--- a/docs/tracks/en/managing-customer-credit-invoices.md
+++ b/docs/tracks/en/managing-customer-credit-invoices.md
@@ -21,7 +21,7 @@ The __Invoices__ screen in the VTEX Admin (__Apps > Customer Credit > Invoices__
 - [Settle invoices](#settle-invoices)
 <br>
 <br>
-![Invoices_EN](//images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/5f6f07bf3e43e11762d057b41b2277bb/Invoices_EN.JPG)
+![Invoices_EN](https://images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/5f6f07bf3e43e11762d057b41b2277bb/Invoices_EN.JPG)
 
 ## Invoice filter
 
diff --git a/docs/tracks/en/managing-sales-associates-in-instore.md b/docs/tracks/en/managing-sales-associates-in-instore.md
index da9689d9b..4ff8a8873 100644
--- a/docs/tracks/en/managing-sales-associates-in-instore.md
+++ b/docs/tracks/en/managing-sales-associates-in-instore.md
@@ -17,7 +17,7 @@ trackSlugEN: instore-first-steps-and-configurations
 After configuring the [VTEX Sales App basic settings](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), you can add sales associates to the system or manage the existing ones in the VTEX Admin.
 On the VTEX Admin **Store Settings** page, there is a **Sales associates** category that displays a list of the sales associates added to your [VTEX Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). It allows you to manage sales associate information across all [franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) of your store, enabling you to [add](#adding-a-sales-associate), [search](#searching-for-a-sales-associate), [filter](#filtering-sales-associates), [edit](#editing-sales-associate-information), and [inactivate](#inactivating-a-sales-associate) them.
 
-![vendedores-en](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/6011c48aa3efe75b2131b7870d237483/EN.png)
+![vendedores-en](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/6011c48aa3efe75b2131b7870d237483/EN.png)
 
 The page displays the following information:
 
diff --git a/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index bd7899c8c..97cccc993 100644
--- a/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -18,7 +18,7 @@ After installing and configuring TikTok for Business, you can manage the integra
 
 After the configuration has been successfully completed, any user logged into the VTEX Admin can access the TikTok management area. However, when interacting with the buttons in this area, users will be redirected to  TikTok environments — TikTok Business Center, TikTok Ads Manager and TikTok Catalog Manager — where they need permissions to view content and make changes.
 
-![manage-tiktok-integration](//images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
+![manage-tiktok-integration](https://images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
 
 From that page, you can do the following:
 
diff --git a/docs/tracks/en/mapping-colors-and-sizes.md b/docs/tracks/en/mapping-colors-and-sizes.md
index fffb1fb7a..6e8562aa3 100644
--- a/docs/tracks/en/mapping-colors-and-sizes.md
+++ b/docs/tracks/en/mapping-colors-and-sizes.md
@@ -66,7 +66,7 @@ You should choose the closest color match, which in Wish's case can be "White/Ic
 The table's header should be filled in exactly as in the example below. Remember to not add any special characters such as "enter" or "space" when filling this table in.   
 </div>
 
-![PT - Tabela Wish](//images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
+![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
 ## Uploading the spreadsheet
 
diff --git a/docs/tracks/en/merchandising-rules.md b/docs/tracks/en/merchandising-rules.md
index cad79a064..c04e3c9d1 100644
--- a/docs/tracks/en/merchandising-rules.md
+++ b/docs/tracks/en/merchandising-rules.md
@@ -30,7 +30,7 @@ On VTEX Admin, the page **Storefront** > **Intelligent Search** > **Merchandisin
 * [Edit](#editing-merchandising-rules)
 * [Delete](#deleting-merchandising-rules)
 
-![merch-rules-en](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/6b6dc34a4127cd654dab40fa17a70664/merch-rules-en.PNG)
+![merch-rules-en](https://images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/6b6dc34a4127cd654dab40fa17a70664/merch-rules-en.PNG)
 
 The page displays the following information: 
 
diff --git a/docs/tracks/en/opening-tickets.md b/docs/tracks/en/opening-tickets.md
index 34f1eb5fe..3d7aa2ac7 100644
--- a/docs/tracks/en/opening-tickets.md
+++ b/docs/tracks/en/opening-tickets.md
@@ -20,7 +20,7 @@ Access to a VTEX account gives you access to the [support dashboard](https://sup
 - Going to any [Help Center](https://help.vtex.com/) page and click `Support` at the top or `Contact Us` at the bottom of the page.
 - Accessing the VTEX Admin, click the `?` question mark icon in the **Information Center** and choose the **Talk to Our Experts** option.
 
-![Support imagem 1 - EN](//images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/c0f1b4654f82949a438f82b2416a11c7/support_imagem1_EN.gif)
+![Support imagem 1 - EN](https://images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/c0f1b4654f82949a438f82b2416a11c7/support_imagem1_EN.gif)
 
 <div class = "alert alert-info">
 Learn more about how to open a ticket and ticket types in the article <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Opening tickets to VTEX support. </a>
diff --git a/docs/tracks/en/order-delivery.md b/docs/tracks/en/order-delivery.md
index 698fa4dab..fa3fcf116 100644
--- a/docs/tracks/en/order-delivery.md
+++ b/docs/tracks/en/order-delivery.md
@@ -23,7 +23,7 @@ See two examples of this scenario:
 
 In this case, items usually come from the warehouse of a distribution center, as illustrated below.
 
-![EN Conceitos Logística](//images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
+![EN Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
 
 Another shipping possibility that can optimize your store’s operation and reduce costs is implementing the [Ship From Store](https://help.vtex.com/en/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl) strategy. This strategy refers to in-store fulfillment, meaning items can also be shipped from physical stores' inventories.
 
diff --git a/docs/tracks/en/order-flow.md b/docs/tracks/en/order-flow.md
index bc3049a37..4cf90e4a5 100644
--- a/docs/tracks/en/order-flow.md
+++ b/docs/tracks/en/order-flow.md
@@ -33,7 +33,7 @@ It's important to understand these concepts because the Marketplace's order flow
 
 ## Marketplace Order Flow
 
-![screenshoot fluxo marketplace EN](//images.ctfassets.net/alneenqid6w5/6S7796dGpdWlRojJbrSgg/0ca93f3020f0393abafa75e7dd5951aa/screenshoot_fluxo_marketplace_EN.JPG)
+![screenshoot fluxo marketplace EN](https://images.ctfassets.net/alneenqid6w5/6S7796dGpdWlRojJbrSgg/0ca93f3020f0393abafa75e7dd5951aa/screenshoot_fluxo_marketplace_EN.JPG)
 
 It happens when the store acts exclusively as a Marketplace in the order. That is, when the store sells products from another store - its Seller.
 
@@ -47,7 +47,7 @@ The dispatch is then authorized and the order enters the status `Window to Cance
 
 ## Seller Order Flow
 
-![screenshoot fluxo seller EN](//images.ctfassets.net/alneenqid6w5/14SsrA3HbuAxsYerakdGGf/9a50dbe872d8712670ce7a1ddbbf2e6e/screenshoot_fluxo_seller_EN.JPG)
+![screenshoot fluxo seller EN](https://images.ctfassets.net/alneenqid6w5/14SsrA3HbuAxsYerakdGGf/9a50dbe872d8712670ce7a1ddbbf2e6e/screenshoot_fluxo_seller_EN.JPG)
 
 It happens when the store acts as a Seller. That is, when it is the owner of the product.
 
@@ -61,7 +61,7 @@ The next status is then `Handling Shipping`, when the Seller prepares the invoic
 
 ## Complete Order Flow
 
-![screenshoot fluxo completo EN](//images.ctfassets.net/alneenqid6w5/5uYoEIqMJxUMFZzXKf72Sh/2cf49ed2ddd0cceac3f429e1f4492422/screenshoot_fluxo_completo_EN.JPG)
+![screenshoot fluxo completo EN](https://images.ctfassets.net/alneenqid6w5/5uYoEIqMJxUMFZzXKf72Sh/2cf49ed2ddd0cceac3f429e1f4492422/screenshoot_fluxo_completo_EN.JPG)
 
 It happens when the store is both the Marketplace and the Seller. That is, it's when the order was closed in the store and the store itself is the owner of the product, being responsible for the fulfillment.
 
diff --git a/docs/tracks/en/other-vtex-module-settings.md b/docs/tracks/en/other-vtex-module-settings.md
index 4c0724ec8..ef3a23aef 100644
--- a/docs/tracks/en/other-vtex-module-settings.md
+++ b/docs/tracks/en/other-vtex-module-settings.md
@@ -82,7 +82,7 @@ To allow customers to make recurring purchases of their favorite products at the
 - Access details and information for completing each task.
 - Assign [users](https://help.vtex.com/en/tutorial/managing-users--tutorials_512) to tasks.
 
-![vtex-do-en](//images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/9c4752761e0a8215e6938f8fdf2d4358/next_steps_image12_EN.JPG)
+![vtex-do-en](https://images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/9c4752761e0a8215e6938f8fdf2d4358/next_steps_image12_EN.JPG)
 
 ### VTEX Social Selling
 
diff --git a/docs/tracks/en/payment.md b/docs/tracks/en/payment.md
index 2c5d91939..52416fce6 100644
--- a/docs/tracks/en/payment.md
+++ b/docs/tracks/en/payment.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-using-the-app
 
 In the VTEX Sales App payment step, the sales associate will see the [payment options that have been configured](https://help.vtex.com/en/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy) for your store.
 
-![instore-payment-en](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/37e9029b397ce3f04d2b6a87462c8666/Screenshot_2022-10-21_at_14-57-36_VTEX_VTEX Sales App_Checkout.png)
+![instore-payment-en](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/37e9029b397ce3f04d2b6a87462c8666/Screenshot_2022-10-21_at_14-57-36_VTEX_VTEX Sales App_Checkout.png)
 
 The top bar of the payment screen displays the following options:
 
@@ -45,7 +45,7 @@ To configure a payment method, follow the [VTEX Sales App - Payments](https://he
 
 The customer must select the **Cash** option and click `Complete Sale`. 
 
-![instore-dinheiro-en](//images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/868ca0e64245ec78ed6794e0e4e5726f/Screenshot_2022-10-21_at_14-57-55_VTEX_VTEX Sales App_Checkout.png)
+![instore-dinheiro-en](https://images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/868ca0e64245ec78ed6794e0e4e5726f/Screenshot_2022-10-21_at_14-57-55_VTEX_VTEX Sales App_Checkout.png)
 
 Then, you must complete the transaction with the sales associate. Depending on the store's configuration, it can be either [manual or automatic](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT). 
 
@@ -53,21 +53,21 @@ Then, you must complete the transaction with the sales associate. Depending on t
 
 The customer must select **Pix** and click `Complete Sale`. 
 
-![instore-pix-en](//images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/a65732c1fb0af5e4f5a161b8b64c6186/Screenshot_2022-10-21_at_14-58-22_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix-en](https://images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/a65732c1fb0af5e4f5a161b8b64c6186/Screenshot_2022-10-21_at_14-58-22_VTEX_VTEX Sales App_Checkout.png)
 
 After completing the sale, the QR Code will be displayed on the VTEX Sales App screen. The customer must scan it using their phone to proceed with payment. 
 
-![instore-pix2-en](//images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/f252d0b00eff1385cc1e14cb7dbdf3bf/image.png)
+![instore-pix2-en](https://images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/f252d0b00eff1385cc1e14cb7dbdf3bf/image.png)
 
 After payment, the sale will be processed and confirmed on the order page, as shown in the image below.
 
-![instore-pix3-en](//images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/0c648cce0a942b1eb2d86420372d9729/Screenshot_2022-10-21_at_14-58-53_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix3-en](https://images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/0c648cce0a942b1eb2d86420372d9729/Screenshot_2022-10-21_at_14-58-53_VTEX_VTEX Sales App_Checkout.png)
 
 ### Boleto (Brazil)
 
 The customer must select **Boleto** and click `Complete Sale`. 
 
-![instore-boleto-en](//images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/61116b8b732842719e8783ec3711e22f/Screenshot_2022-10-21_at_14-57-50_VTEX_VTEX Sales App_Checkout.png)
+![instore-boleto-en](https://images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/61116b8b732842719e8783ec3711e22f/Screenshot_2022-10-21_at_14-57-50_VTEX_VTEX Sales App_Checkout.png)
 
 The boleto will be sent to the customer by email. Once the boleto payment is confirmed, so is the purchase.
 
@@ -75,7 +75,7 @@ The boleto will be sent to the customer by email. Once the boleto payment is con
 
 The customer must select the **Credit Card** option, choose the number of installments for the purchase, and click `Complete Sale`. 
 
-![instore-credito-en](//images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ef042ee59ae511b33c95c708597f6f99/Screenshot_2022-10-21_at_14-58-11_VTEX_VTEX Sales App_Checkout.png)
+![instore-credito-en](https://images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ef042ee59ae511b33c95c708597f6f99/Screenshot_2022-10-21_at_14-58-11_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App will display a waiting screen while the payment is made though the store's card machine. Once the system accepts the payment, the transaction will be confirmed.
 
@@ -83,6 +83,6 @@ VTEX Sales App will display a waiting screen while the payment is made though th
 
 The customer must select **Debit Card** and click `Complete Sale`. 
 
-![instore-debito-en](//images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/73fb933dcd5a70d63c7bc1c73bbad4c3/Screenshot_2022-10-21_at_14-58-01_VTEX_VTEX Sales App_Checkout.png)
+![instore-debito-en](https://images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/73fb933dcd5a70d63c7bc1c73bbad4c3/Screenshot_2022-10-21_at_14-58-01_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App will display a waiting screen while the payment is made through the store's card machine. Once the system accepts the payment, the transaction will be confirmed.
diff --git a/docs/tracks/en/planning-the-go-live.md b/docs/tracks/en/planning-the-go-live.md
index 6ffa18cd4..8e1b86567 100644
--- a/docs/tracks/en/planning-the-go-live.md
+++ b/docs/tracks/en/planning-the-go-live.md
@@ -34,7 +34,7 @@ The process of a store's go-live, including the necessary settings and tests, ca
 
 The following image shows the planning steps for the VTEX store go-live:
 
-![go-live-en](//images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/42ac375fd2ab83f78c34dfca3da81260/golive_1_EN.png)
+![go-live-en](https://images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/42ac375fd2ab83f78c34dfca3da81260/golive_1_EN.png)
 
 ### Define the MVP
 
@@ -54,7 +54,7 @@ Therefore, the whole planning process should start at least 45 days in advance,
 
 To organize the teams involved and go live on the planned date, you need to create a _roadmap_, i.e., a document with the actions required for the go-live, indicating who is accountable for each step and the agreed deadlines. The following image shows a timeline as an example:
 
-![golive 2 EN](//images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/bae691008a305280c7c3d14aeb319b11/golive_2_EN.png)
+![golive 2 EN](https://images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/bae691008a305280c7c3d14aeb319b11/golive_2_EN.png)
 
 We recommend scheduling regular meetings with the [implementation teams](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) to ensure alignment and, if necessary, establishing a _war room_ to deal with pending issues in the week before the go-live.
 
diff --git a/docs/tracks/en/preco-base-definicao-de-conceito.md b/docs/tracks/en/preco-base-definicao-de-conceito.md
index 2f59fa098..ebce13a25 100644
--- a/docs/tracks/en/preco-base-definicao-de-conceito.md
+++ b/docs/tracks/en/preco-base-definicao-de-conceito.md
@@ -18,7 +18,7 @@ trackSlugEN: prices-101
 
 A SKU's base price is the value which results from merging the **Cost Price** with the **Markup**, the desired profit margin with the SKU's sale. It represents the SKU's __reference price__ for all price tables. 
 
-![base-price-en](//images.ctfassets.net/alneenqid6w5/cbmJa638a5NuZHtjF1FPN/4bb70f39b01a19c15ec07525e8372329/base-price-en.png)
+![base-price-en](https://images.ctfassets.net/alneenqid6w5/cbmJa638a5NuZHtjF1FPN/4bb70f39b01a19c15ec07525e8372329/base-price-en.png)
 
 This **base price** can be combined with a price table's applied **price rule**. If there are no registered price rules, a price table's selling price will be equal to the base price itself.
 
diff --git a/docs/tracks/en/preco-fixo-definicao-de-conceito.md b/docs/tracks/en/preco-fixo-definicao-de-conceito.md
index 9571e8a4f..d7191119c 100644
--- a/docs/tracks/en/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/en/preco-fixo-definicao-de-conceito.md
@@ -73,7 +73,7 @@ Let's suppose that an SKU has two fixed prices linked to it. In addition, both p
 
 For example, the first fixed price is set at __U$ 50,00__ and its schedule runs from __10AM__ to __4PM__. The second price is set at __U$ 25,00__ and is scheduled from __noon__ to __8PM of the same day__. Therefore, the prices compete for the same schedule between *noon and 4PM*, which means that the __U$ 25,00__ SKU sales price will prevail during this time.
 
-![fixed price - example2](//images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
+![fixed price - example2](https://images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
 
 ### Competing criteria for minimum number of cart items
 
@@ -83,7 +83,7 @@ Let's suppose that you've added a fixed price of U$ 200,00 for __two of more ite
 
 Which price would in this case be applied to five or more items? The sales price would be the lower one, U$ 100,00. 
 
-![fixed price - example1](//images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
+![fixed price - example1](https://images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
 
 ## Examples 
 
diff --git a/docs/tracks/en/pricing-system-architecture.md b/docs/tracks/en/pricing-system-architecture.md
index 5400ade4c..c06391071 100644
--- a/docs/tracks/en/pricing-system-architecture.md
+++ b/docs/tracks/en/pricing-system-architecture.md
@@ -33,7 +33,7 @@ These may be:
 
 Below, we can see a blueprint of how the concepts of *prices*, *price table* and *context* are related to one another:
 
-![Architecture-EN](//images.ctfassets.net/alneenqid6w5/6e0dbJq89EfPqJTKUiuju8/b0acbc822f1da5c78e100c075831982d/Architecture__2_.svg)
+![Architecture-EN](https://images.ctfassets.net/alneenqid6w5/6e0dbJq89EfPqJTKUiuju8/b0acbc822f1da5c78e100c075831982d/Architecture__2_.svg)
 
 ## Computed price
 
@@ -47,21 +47,21 @@ The pricing module takes these 4 criteria into account when calculating a price
 - Fixed Price
 
 1. In cases where the SKU only has the *base price* set, the computed price for a specific price table will be equal to the **base price**.
-![rule1-EN](//images.ctfassets.net/alneenqid6w5/49vh298CSTLJBLWRvAt9Wx/b6e4cd1212dfbcffbeff6e8feafc7a3d/rule1__1_.svg) 
+![rule1-EN](https://images.ctfassets.net/alneenqid6w5/49vh298CSTLJBLWRvAt9Wx/b6e4cd1212dfbcffbeff6e8feafc7a3d/rule1__1_.svg) 
 
 2. When the SKU has a *price rule* configured for a specific price table, the computed price will be equal to **the base price, modified by the price rule**
-![rule2-EN](//images.ctfassets.net/alneenqid6w5/49T4V2FxtwLPfQdPWp27Hm/746255f33fb8d0dc0fc6696808971e37/rule2__1_.svg) 
+![rule2-EN](https://images.ctfassets.net/alneenqid6w5/49T4V2FxtwLPfQdPWp27Hm/746255f33fb8d0dc0fc6696808971e37/rule2__1_.svg) 
 
 3. In another scenario, we will consider a SKU with a *base price*, a *price rule* and *rounding rules*. **The computer price for a specific price table will be the result of these three factors**. First, the base price will be changed by the price rule. Afterwards, the psychological pricing's rounding takes place.
-![rule3-EN](//images.ctfassets.net/alneenqid6w5/7xwUkHqOkGx6toE6qkXQ2M/ab20002cafca089dcfbb909970dd4e4b/rule3__1_.svg) 
+![rule3-EN](https://images.ctfassets.net/alneenqid6w5/7xwUkHqOkGx6toE6qkXQ2M/ab20002cafca089dcfbb909970dd4e4b/rule3__1_.svg) 
 
 4. Lastly, if the SKU has a *fixed price*, **a specific price table's computed price will be equal to the fixed price**. This price weighs more than any of the others, which results in the pricing module *ignoring the other prices* when a fixed price is associated to an SKU. 
-![rule4-EN](//images.ctfassets.net/alneenqid6w5/7qQe04LL529cFeyW2UjGws/3b80fb4386164dd52d792c81bf4956c0/rule4__1_.svg)
+![rule4-EN](https://images.ctfassets.net/alneenqid6w5/7qQe04LL529cFeyW2UjGws/3b80fb4386164dd52d792c81bf4956c0/rule4__1_.svg)
 
 ## Validating a computed price
 
 To check an SKU's sales price for a specific price table, you can query the **computed price value** in the **Price List** section in admin. In the example below, we can see that the computed price for **SKU 14** in **trade policy table 1** is equal to **334,62**:
-![computed-price-en](//images.ctfassets.net/alneenqid6w5/4LtPPVFSSHGOZAENhHeRyZ/56a5705d20dff8ebe13d8fdfa181a330/computed-price-en.png)
+![computed-price-en](https://images.ctfassets.net/alneenqid6w5/4LtPPVFSSHGOZAENhHeRyZ/56a5705d20dff8ebe13d8fdfa181a330/computed-price-en.png)
 
 You can also check an SKU's computed price in a price table by **making an API request**. To achieve this, you'll need to send a **GET** to the [Get Computed Price by price table or trade policy](https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-) call.
 
diff --git a/docs/tracks/en/printing-an-order-summary.md b/docs/tracks/en/printing-an-order-summary.md
index 8deea3208..edf9cc087 100644
--- a/docs/tracks/en/printing-an-order-summary.md
+++ b/docs/tracks/en/printing-an-order-summary.md
@@ -18,7 +18,7 @@ When an order is placed using VTEX Sales App, it is possible to print the order
 
 To do this, the sales associate can click on the `Print order` button on the completed order screen, as illustrated below. Another option is to configure VTEX Sales App to print the order summary automatically as soon as an order is placed.
 
-![15. Configurar impressão de resumo do pedido - 1 - EN](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/790d42c635583e24fafdd613393184a4/print-order-en.png)
+![15. Configurar impressão de resumo do pedido - 1 - EN](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/790d42c635583e24fafdd613393184a4/print-order-en.png)
 
 To enable order summary printing, follow the steps below.
 
@@ -50,13 +50,13 @@ After obtaining the AppKey and AppToken, follow the steps below.
 2. Open the VTEX Sales App app and enter the name of the store where you want to configure the printer.
 3. In the VTEX Sales App main menu, go to **Settings** and click on the <i class="fas fa-cog"></i> **Configure device** option, as shown below.
 
-![15. Configurar impressão de resumo do pedido - 2 - EN](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/6b9437dbb66b4f0d86329a38ba619e5a/configuration-en.png)
+![15. Configurar impressão de resumo do pedido - 2 - EN](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/6b9437dbb66b4f0d86329a38ba619e5a/configuration-en.png)
 
 <ol start="4">
   <li>You will see the summary of the configured device. If this is the first time this configuration is performed, the fields on the screen will be empty, as shown in the image below. If a device has been previously configured, you will see the <b>Device name</b> and <b>Default printer</b>. Click on the <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">Edit</span> button.</li>
 </ol>
 
-![15. Configurar impressão de resumo do pedido - 4 - EN](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/19ce84bc4f5f802487e75c9ce03c8fd6/image_3.png)
+![15. Configurar impressão de resumo do pedido - 4 - EN](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/19ce84bc4f5f802487e75c9ce03c8fd6/image_3.png)
 
 <ol start="5">
   <li>Fill out the form according to the descriptions below.
diff --git a/docs/tracks/en/product-details.md b/docs/tracks/en/product-details.md
index f6d85fac1..b1ca273c9 100644
--- a/docs/tracks/en/product-details.md
+++ b/docs/tracks/en/product-details.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-using-the-app
 
 When clicking on the details of a product that appears in the VTEX Sales App search results, or when beeping a product, the sales associate is directed to the product details page.
 
-![instore-pdp-en](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/6f2be63cd50dfda6d84bae201315f387/pdp-en.png)
+![instore-pdp-en](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/6f2be63cd50dfda6d84bae201315f387/pdp-en.png)
 
 This page shows the name of the product, its photo gallery, variations, description and availability. On this screen, the sales associate can add the product to the cart.
 
diff --git a/docs/tracks/en/promotions-for-specific-scenarios.md b/docs/tracks/en/promotions-for-specific-scenarios.md
index 26cf5fa58..19a07eab7 100644
--- a/docs/tracks/en/promotions-for-specific-scenarios.md
+++ b/docs/tracks/en/promotions-for-specific-scenarios.md
@@ -37,7 +37,7 @@ The promotion configuration screen offers two SKU lists, which can be added manu
 
 You can define a discount value for each of these lists. If, for example, list 1 has a 10% discount and list 2 has a 5% discount, when the cart has at least one product from each of these lists, a total of 10% discount will be granted on the value of the items from list 1 and a 5% discount will be granted on the value of the items from list 2.
 
-![Compre junto - EN](//images.ctfassets.net/alneenqid6w5/5BDhbniC14qWJbV6L8e3Kk/c7fdc229614791d92043d350ca5b1319/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_4_.png)
+![Compre junto - EN](https://images.ctfassets.net/alneenqid6w5/5BDhbniC14qWJbV6L8e3Kk/c7fdc229614791d92043d350ca5b1319/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_4_.png)
 
 Two examples of this type of promotion would be "Buy a pair of pants and get 10% off when buying a belt" and "Buy a pair of sneakers + a pair of socks and get a 15% off".
 
@@ -49,7 +49,7 @@ The More for Less promotion is used to grant a discount when the customer adds s
 
 In the configuration of the More for Less promotion, the store must define which collections or SKUs it will apply to. Then, it must choose the minimum number of items in the cart for it to apply and the number of items that get a discount.
 
-![More less](//images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/823b88ebf22ca83427e4c9c809d31d2e/More_less.png)
+![More less](https://images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/823b88ebf22ca83427e4c9c809d31d2e/More_less.png)
 
 For example:
 - For every `3` products, the customer will get `1` `free` product.
@@ -67,7 +67,7 @@ When configuring the Progressive Discount promotion, the store must define which
 
 To add more details to the progressive discount promotion, click on the "+" button. A new line will be added, and then you can add a new discount. For example: for the next 2 products, the customer will receive an additional 5% discount. And so on.
 
-![Desconto progressivo - EN](//images.ctfassets.net/alneenqid6w5/7qZXWf05OIow5vgX5eYulO/808c44fcd80666575444d3d9d6afd560/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_6_.png)
+![Desconto progressivo - EN](https://images.ctfassets.net/alneenqid6w5/7qZXWf05OIow5vgX5eYulO/808c44fcd80666575444d3d9d6afd560/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_6_.png)
 
 To understand the Progressive Discount promotion in more detail, read our article on <a href="https://help.vtex.com/en/tutorial/progressive-discount--tutorials_324">How progressive discount works</a>.
 
@@ -77,7 +77,7 @@ The Buy One Get One promotion is used to offer free shipping or a freebie when a
 
 The applied discount (free shipping or freebie) must be defined in the promotion's general data. Then the store must choose the collections or SKUs to which it will apply. Finally, you must define the minimum number of items in the cart for the promotion to apply.
 
-![Compre um e leve outro - EN](//images.ctfassets.net/alneenqid6w5/L17yG5ZAgaGnCuamDWLwk/141c68c306baa0b2bedec04ee3d0c894/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_7_.png)
+![Compre um e leve outro - EN](https://images.ctfassets.net/alneenqid6w5/L17yG5ZAgaGnCuamDWLwk/141c68c306baa0b2bedec04ee3d0c894/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_7_.png)
 
 To understand the Buy One Get One promotion in more detail, read our article on <a href="https://help.vtex.com/en/tutorial/buy-and-win--tutorials_322">How the Buy and Win promotion works</a>.
 
@@ -91,22 +91,22 @@ It is important to note that such restrictions are only <strong>valid for regula
 
 After filling in all the [regular promotion fields](https://help.vtex.com/en/tutorial/regular-promotion--tutorials_327) with the percentage discount, you can __set a maximum number of items affected per cart__ by checking the box for this option, found in the __restrictions__ section.
 
-![Limite itens - EN](//images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/98c764ea9fd40bd809d3b7bf55c7a313/Limite_itens_-_EN.png)
+![Limite itens - EN](https://images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/98c764ea9fd40bd809d3b7bf55c7a313/Limite_itens_-_EN.png)
 
 By default, the __unlimited__ selection is active, applying the promotion to all items in the cart, as illustrated in the diagram below:  
 
-![Caso ilimitado EN](//images.ctfassets.net/alneenqid6w5/3H9q2Ywy6uPZmQaff7LgO2/5f69462ef9ecf3d57817ad0fba44a337/Caso_ilimitado_EN.png)
+![Caso ilimitado EN](https://images.ctfassets.net/alneenqid6w5/3H9q2Ywy6uPZmQaff7LgO2/5f69462ef9ecf3d57817ad0fba44a337/Caso_ilimitado_EN.png)
 
 To restrict the number of items in the cart, you can choose one from the following options:
 
 - __Items by cart__: this setting restrict a promotion to a predetermined number of items in the cart. Once the limit is reached, the promotion will apply to the rest of the cart. The system uses price as a selection criterion so the items with the lowest prices will be affected first.
 
-![Caso por itens EN](//images.ctfassets.net/alneenqid6w5/2UUHQC3AZW5g0QzFouGw0u/f414491e89bbd9f08b96914243584be2/Caso_por_itens_EN.png)
+![Caso por itens EN](https://images.ctfassets.net/alneenqid6w5/2UUHQC3AZW5g0QzFouGw0u/f414491e89bbd9f08b96914243584be2/Caso_por_itens_EN.png)
 
 - __Items by product__: this setting restricts the promotion to a number of units per product. As in the example below, only two units per product will be eligible for the promotion. The lowest price determines which product items are eligible first.   
 
-![Caso por produto EN](//images.ctfassets.net/alneenqid6w5/2WN8gDLFhTSjcpx16S3bjb/c4221f0b4901a7df2432d3951deec983/Caso_por_produto_EN.png)
+![Caso por produto EN](https://images.ctfassets.net/alneenqid6w5/2WN8gDLFhTSjcpx16S3bjb/c4221f0b4901a7df2432d3951deec983/Caso_por_produto_EN.png)
 
 - __Items by SKU__: this setting restricts the promotion to a predetermined number of units for each SKU in the cart. As in the example below, only two units per SKU will be eligible. As seen in the previous case, the lowest price will determine the eligible items. 
 
-![Caso por SKU EN](//images.ctfassets.net/alneenqid6w5/huuzHYSvrVxk2THs7zx2P/0a513d9fbd247797218c25089372c450/Caso_por_SKU_EN.png)
+![Caso por SKU EN](https://images.ctfassets.net/alneenqid6w5/huuzHYSvrVxk2THs7zx2P/0a513d9fbd247797218c25089372c450/Caso_por_SKU_EN.png)
diff --git a/docs/tracks/en/relevance.md b/docs/tracks/en/relevance.md
index 9928aeda3..6e73145d5 100644
--- a/docs/tracks/en/relevance.md
+++ b/docs/tracks/en/relevance.md
@@ -23,7 +23,7 @@ You can configure relevance in two ways:
   - __Priority Criteria__: it imposes that one or more criteria has a higher priority among the others. In this situation, there are no weights; all products that have this feature will be shown first in the search results.
   - __Criteria Composition__: it is a way to distribute weights for each option, ranging from 0 to 10. Here, there is no order between the criteria; the weights will define the relevance.
 
-![criterios-en](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/56c8163ed9b449419c17db066dd4506e/criterios-en.png)
+![criterios-en](https://images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/56c8163ed9b449419c17db066dd4506e/criterios-en.png)
 
 The information considered for the relevance is:
 
@@ -102,6 +102,6 @@ To change relevance settings, follow the steps below.
 
    If you want to change a criterion from **Criteria Composition** to **Priority Criteria**, click on the <i class="fas fa-grip-vertical"></i> icon and drag it to the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight. 
 
-   ![criterios-prioritarios-en](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/326edf2ab5b2c2ee3050a97a98090dd9/criterios-prioritarios-en.gif)
+   ![criterios-prioritarios-en](https://images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/326edf2ab5b2c2ee3050a97a98090dd9/criterios-prioritarios-en.gif)
 5. Click `Save` to finish.
 
diff --git a/docs/tracks/en/reports-vtex-intelligent-search.md b/docs/tracks/en/reports-vtex-intelligent-search.md
index 111592978..3bfd24c1d 100644
--- a/docs/tracks/en/reports-vtex-intelligent-search.md
+++ b/docs/tracks/en/reports-vtex-intelligent-search.md
@@ -79,8 +79,8 @@ To export a report in .csv format, you must follow the steps below:
 
 The report (CSV file) you have downloaded contains two tables. The first table contains information about searched terms, as illustrated below. It also shows funnel metrics (from the **ProductsClick** column to the **ProductsSold** column) if you have selected this option.
 
-![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
+![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
 
 The second table shows data for the selected period, as illustrated below. In the __Date__ column, you can see the date of the search.
 
-![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
+![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
diff --git a/docs/tracks/en/sale-confirmed.md b/docs/tracks/en/sale-confirmed.md
index f93387258..adbd54f0f 100644
--- a/docs/tracks/en/sale-confirmed.md
+++ b/docs/tracks/en/sale-confirmed.md
@@ -16,4 +16,4 @@ trackSlugEN: instore-using-the-app
 
 The sales associate can see the __Sale confirmed__ page with the order summary when they finish a sale, or by clicking on a sale in the __Latest sales__ page, which they can access through VTEX Sales App's main menu. In the __Latest sales__ page, they can search for the order by order number or customer name.
 
-![order-placed-en](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/50395e206f1f6eb47f02a8f5a271a8d9/order-placed-en.png)
+![order-placed-en](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/50395e206f1f6eb47f02a8f5a271a8d9/order-placed-en.png)
diff --git a/docs/tracks/en/sales-channel-mapping.md b/docs/tracks/en/sales-channel-mapping.md
index 26b3935c3..842a1049f 100644
--- a/docs/tracks/en/sales-channel-mapping.md
+++ b/docs/tracks/en/sales-channel-mapping.md
@@ -20,6 +20,6 @@ To do this, go to *Marketplace > Lengow Integration > Settings* and find the **S
 
 For each sales channel, select the trade policy that should be used in the left column and fill in the sales channel identifier for Lengow in the right column. We recommend combining Marketplace names and country codes in the sales channel identifier, as this will make it easier to organize your data in Lengow. For example, *Amazon UK* would be identified as `amazon_uk`.
 
-![Lengow - Sales channel mapping](//images.ctfassets.net/alneenqid6w5/x2fhsfCef0cWzGtVQepzK/487b1b2f601979ce6c97c5822965dd00/Screen_Shot_2020-07-01_at_22.49.58.png)
+![Lengow - Sales channel mapping](https://images.ctfassets.net/alneenqid6w5/x2fhsfCef0cWzGtVQepzK/487b1b2f601979ce6c97c5822965dd00/Screen_Shot_2020-07-01_at_22.49.58.png)
 
 <div class="alert alert-warning" role="alert">All <a href="https://help.vtex.com/en/tutorial/configuring-a-marketplace-trade-policy--tutorials_404" target="_blank">trade policies</a> must be created and set up prior to this step. Their names do not need to correspond to the sales channel. If you do not need to adopt different catalog, pricing and shipping strategies for two sales channels, they may share the same trade policy.</div>
diff --git a/docs/tracks/en/search-settings.md b/docs/tracks/en/search-settings.md
index 2c271cb56..aac13393f 100644
--- a/docs/tracks/en/search-settings.md
+++ b/docs/tracks/en/search-settings.md
@@ -36,7 +36,7 @@ The general settings display the following options related to[ product and SKU s
 
 The facet settings have settings related to the[ filters](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) displayed to your customers during the search:
 
-![Facet configurations](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
+![Facet configurations](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
 
 * **Facet order:** Order in which the facets will be displayed in the store. If no facet is selected, the default order is alphabetical.
 
diff --git a/docs/tracks/en/sending-products-to-amazon.md b/docs/tracks/en/sending-products-to-amazon.md
index e6250cc35..4c849b5c6 100644
--- a/docs/tracks/en/sending-products-to-amazon.md
+++ b/docs/tracks/en/sending-products-to-amazon.md
@@ -41,17 +41,17 @@ This list includes icons to indicate the status of your mapping:
 
 | **Icon** | **Status**| **Description**|
 |:---:|:---:|:---:|
-|![mapeado mapper](//images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/94a47adb24232c9a88da68e951edfad4/mapeado_mapper.jpg)| **Mapped** |Indicates that the category mapping was completed.|
-|![mapeamentoincompleto mapper](//images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/5c707e0427e064603b127ecffba75970/mapeamentoincompleto_mapper.jpg) | **Incomplete mapping** |The category is partially mapped.The required attributes, indicated by an asterisk, need to be added for completing the mapping. |
-|![erromapeamento mapper](//images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/f84c40b49563dacdf2f96c5ac20ad65e/erromapeamento_mapper.jpg) | **Error in mapping** |The mapping error occurs when the marketplace removes or changes the product category. To solve this, simply remap the category. |
-|![incompleto mapper](//images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/5c2bb3c9fd5f5d131b9a2e153d7857d0/incompleto_mapper.jpg) | **Not mapped** | Indicates that the category was not mapped. |  
+|![mapeado mapper](https://images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/94a47adb24232c9a88da68e951edfad4/mapeado_mapper.jpg)| **Mapped** |Indicates that the category mapping was completed.|
+|![mapeamentoincompleto mapper](https://images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/5c707e0427e064603b127ecffba75970/mapeamentoincompleto_mapper.jpg) | **Incomplete mapping** |The category is partially mapped.The required attributes, indicated by an asterisk, need to be added for completing the mapping. |
+|![erromapeamento mapper](https://images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/f84c40b49563dacdf2f96c5ac20ad65e/erromapeamento_mapper.jpg) | **Error in mapping** |The mapping error occurs when the marketplace removes or changes the product category. To solve this, simply remap the category. |
+|![incompleto mapper](https://images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/5c2bb3c9fd5f5d131b9a2e153d7857d0/incompleto_mapper.jpg) | **Not mapped** | Indicates that the category was not mapped. |  
 
 To map a category, follow these steps:  
 
 1. In the Admin, go to **Marketplace > Marketplaces and Integrations > Amazon > Perform Mapping.**  
 2. Select the category you want to map.
 3. Select the corresponding category on Amazon for the product you want to send.
-4. Match the attributes in the side window, as shown in the image below: ![Amazon Mapper Attributes](//downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/da4ea7365efc744b036e55305feaea6f/mapper_amazon_atributos.gif)  
+4. Match the attributes in the side window, as shown in the image below: ![Amazon Mapper Attributes](https://downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/da4ea7365efc744b036e55305feaea6f/mapper_amazon_atributos.gif)  
 5. Click the `Save Changes` button.  
 
 <div class="alert alert-danger">
@@ -115,13 +115,13 @@ To configure a global category in the VTEX environment according to the global c
 
 **Example of a spreadsheet query**
 In the Amazon required attributes template, we will use the **Health** category as an example:  
-![categoriageral01](//images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
+![categoriageral01](https://images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
 
 In the Amazon general categories template, filter column "I" Cat-Amazon-General by clicking on **Filter > Health > OK**.
-![categoriageral02](//images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
+![categoriageral02](https://images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
 
 Following the previous example, filter columns B, C, and D in the **Health & Beauty > Personal care > Massage & Relaxation** tree.
-![categoriageral03](//images.contentful.com/alneenqid6w5/1p0cIHz7bp8HHuzud1H4zE/e79bf00cbe09f7b1fb155730cfc401f8/categoriageral03.JPG)
+![categoriageral03](https://images.contentful.com/alneenqid6w5/1p0cIHz7bp8HHuzud1H4zE/e79bf00cbe09f7b1fb155730cfc401f8/categoriageral03.JPG)
 
 Now that you have found the Amazon general category, go back to the Admin to [configure the VTEX global category](https://help.vtex.com/es/tutorial/configurando-a-categoria-global--tutorials_188) according to the Amazon general category. 
 
diff --git a/docs/tracks/en/set-the-sku-quantity-in-inventory.md b/docs/tracks/en/set-the-sku-quantity-in-inventory.md
index b738e9d14..c3abb9716 100644
--- a/docs/tracks/en/set-the-sku-quantity-in-inventory.md
+++ b/docs/tracks/en/set-the-sku-quantity-in-inventory.md
@@ -18,7 +18,7 @@ You already have a product associated with a category and a brand, have a SKU fo
 
 To register the stock, follow the steps below.
 1. In the __Catalog__ module, hover over __Products Management__, go to __Products and SKUs__ and click the __Products and SKUs Management__ option.
-2. In the line of the SKU you want, click on the truck symbol (you will be taken to the Logistics module).![SKUstock](//images.contentful.com/alneenqid6w5/5HArBLp1qoq6cyUk8Oc8mO/473c1415e082ee2c644f5ab95f24ff73/SKUstock.png)
+2. In the line of the SKU you want, click on the truck symbol (you will be taken to the Logistics module).![SKUstock](https://images.contentful.com/alneenqid6w5/5HArBLp1qoq6cyUk8Oc8mO/473c1415e082ee2c644f5ab95f24ff73/SKUstock.png)
 
 You will see a table with information about:
 - The SKU whose stock you are editing.
diff --git a/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md b/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md
index 888045ff1..c1fb74576 100644
--- a/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md
+++ b/docs/tracks/en/setting-instore-up-in-a-store-easy-setup.md
@@ -26,31 +26,31 @@ You can find download links at: [http://instore.vtex.com/#download](http://insto
 
 When opening inStore for the first time, you will need to enter the VTEX account where you want to configure it and click on __Confirm__.
 
-![01 inStore selecione conta](//images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
+![01 inStore selecione conta](https://images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
 
 If inStore is not configured on this account, you will be redirected to the VTEX App Store where you will need to log in with your admin account in VTEX.
 
 After login, you will be able to install inStore in your account.
 
-![02 inStore instalar](//images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
+![02 inStore instalar](https://images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
 
 A setup form will be displayed, the first step being the address information.
 
-![03 inStore endereco](//images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
+![03 inStore endereco](https://images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
 
 Then you must set an email and password to be used as a vendor login.
 
 > __IMPORTANT__: this email __CAN'T__ be the same as the one used on VTEX platform, because your admin email has permissions that a salesperson should not have, so it's necessary to use some other email without privileges on the platform.
 
-![04 inStore registre vendedor](//images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
+![04 inStore registre vendedor](https://images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
 
 Once you've set up the seller and confirmed the activation code received via email, you can set up payment methods.
 
-![05 inStore configure pagamento](//images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
+![05 inStore configure pagamento](https://images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
 
 If you do not already have an agreement with an acquirer, you can only keep the __Cash__ option active. After clicking on __Confirm__, you should see the success screen.
 
-![06 inStore sucesso](//images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
+![06 inStore sucesso](https://images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
 
 Now just go back to the app, log in with the vendor credentials and start selling!
 
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
index 9a16818d3..35ff11781 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
@@ -20,11 +20,11 @@ One of the functions of sales policies is to make a differentiation of __catalog
 
 A single sales policy can be shared by more than one marketplace or between the main store and the marketplace. To do this, simply use the same sales policy ID in the [settings](/en/tutorial/integrating-with-marketplace). By doing so, the same catalog and the same logistics will be used for the stores or channels that are configured with the same sales policy.
 
-![carrefour.en2](//images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/6838742905e194a219bc848592b79906/carrefour.en2.png)
+![carrefour.en2](https://images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/6838742905e194a219bc848592b79906/carrefour.en2.png)
 
 In other words, if there is no need to define a specific catalog or logistics type for different sales channels, then you will not need to use separate sales policies. Simply associate your integration with the marketplace to the sales policy ID that already exists.
 
-![carrefour.en3](//images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/bd7e0ec03f86e280299e18b83ba1ecbf/carrefour.en3.png)
+![carrefour.en3](https://images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/bd7e0ec03f86e280299e18b83ba1ecbf/carrefour.en3.png)
 
 So before setting up a new sales policy in your store, make sure you need to do that. If the answer is yes, follow the guidelines in the article [How to hire a new sales policy](https://help.vtex.com/en/faq/how-to-configure-a-new-trade-policy--frequentlyAskedQuestions_700) before moving on to the next configuration step. If your sales policy already meets the conditions you need for integration with the marketplace, follow the instructions below.
 
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
index 0a411cfe6..ff0878c7d 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
@@ -20,11 +20,11 @@ One of the functions of sales policies is to make a differentiation of __catalog
 
 A single sales policy can be shared by more than one marketplace or between the main store and the marketplace. To do this, simply use the same sales policy ID in the [settings](/en/tutorial/integrating-with-marketplace). By doing so, the same catalog and the same logistics will be used for the stores or channels that are configured with the same sales policy.
 
-![carrefour.en2](//images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/ac520788fc2a7f4c7455c21fb9eb7a06/carrefour.en2.png)
+![carrefour.en2](https://images.ctfassets.net/alneenqid6w5/5ZpCw7QeOoLULQmVMx1qil/ac520788fc2a7f4c7455c21fb9eb7a06/carrefour.en2.png)
 
 In other words, if there is no need to define a specific catalog or logistics type for different sales channels, then you will not need to use separate sales policies. Simply associate your integration with the marketplace to the sales policy ID that already exists.
 
-![carrefour.en3](//images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/7c11964cda1bfc0eab26adec48027cc4/carrefour.en3.png)
+![carrefour.en3](https://images.ctfassets.net/alneenqid6w5/8lImGnaG3epR5OtYHyykP/7c11964cda1bfc0eab26adec48027cc4/carrefour.en3.png)
 
 So before setting up a new sales policy in your store, make sure you need to do that. If the answer is yes, follow the guidelines in the article [How to hire a new sales policy](https://help.vtex.com/en/faq/how-to-configure-a-new-trade-policy--frequentlyAskedQuestions_700) before moving on to the next configuration step. If your sales policy already meets the conditions you need for integration with the marketplace, follow the instructions below.
 
diff --git a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
index 7e873cdde..e7730f273 100644
--- a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -16,7 +16,7 @@ trackSlugEN:
 
 This article aims to explain how the inStore app configures AppLinking for `payment` and `payment-reversal` actions with the acquirers' apps.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Setting fields
 
diff --git a/docs/tracks/en/setting-up-the-app.md b/docs/tracks/en/setting-up-the-app.md
index bcaead8f0..d5267774a 100644
--- a/docs/tracks/en/setting-up-the-app.md
+++ b/docs/tracks/en/setting-up-the-app.md
@@ -34,7 +34,7 @@ To perform the initial Customer Credit settings, follow the steps below:
   	<li><b>Affiliation not authenticated</b>: click in <b>Authenticate</b> to be redirected to the configuration screen where you must fill in the information <b>Application Key</b> and <b>Application Token</b>. This action will allow payments made through Customer Credit to be processed in your store. Find out more at <a href="https://developers.vtex.com/docs/guides/authentication">Authentication</a>.</li>
 </ul>
 
-![CC Configuration 1 EN](//images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/25a43afef349f6443a55820be9f17616/CC_Configuration_1_EN.JPG)
+![CC Configuration 1 EN](https://images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/25a43afef349f6443a55820be9f17616/CC_Configuration_1_EN.JPG)
 
 ## App settings
 
@@ -56,13 +56,13 @@ For example, for an account created with a credit limit of $1,000.00 and a toler
 Tolerance values are configured in decimal numbers, with 0 representing 0% and 1 representing 100%. Example: to use a tolerance of 5%, the value to be configured is 0.05.
 </div>
 
-![CC_Configuration_2_EN](//images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/42de816c9685f31074c0637dcbd6c5f1/CC_Configuration_2_EN.JPG)
+![CC_Configuration_2_EN](https://images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/42de816c9685f31074c0637dcbd6c5f1/CC_Configuration_2_EN.JPG)
 
 ### Automatic account creation
 
 This option allows any store customer to use Customer Credit as a payment method, even if you have not previously created an account for them in the Customer Credit app. When activating this functionality, you must also define the initial credit limit that can be used for orders placed by customers without a Customer Credit account.
 
-![CC_Configurações_3_EN](//images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/07a144ef285f845819fb1e12442b3f56/CC_Configuration_3_EN.JPG)
+![CC_Configurações_3_EN](https://images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/07a144ef285f845819fb1e12442b3f56/CC_Configuration_3_EN.JPG)
 
 ### My Credits page
 
@@ -70,7 +70,7 @@ By installing the __My Credits__ page, you will allow customers to view and mana
 
 The customer can access this page on your store's website at __My account > My Credits__.
 
-![CC_Configuration_4_EN](//images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/92daf3c995157e03887f1975d2cccbc8/CC_Configuration_4_EN.JPG)
+![CC_Configuration_4_EN](https://images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/92daf3c995157e03887f1975d2cccbc8/CC_Configuration_4_EN.JPG)
 
 ### Payment Instructions 
 
@@ -80,15 +80,15 @@ This configuration allows you to insert instructions related to payment in the i
 The message registered in this configuration will be replicated on all invoices issued for all Customer Credit accounts. It is not possible to configure a unique message for each specific customer or invoice.
 </div>
 
-![CC_Configuration_5_EN](//images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/cdf9331ac0d8e46d6537c8f265bc621b/CC_Configuration_5_EN.JPG)
+![CC_Configuration_5_EN](https://images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/cdf9331ac0d8e46d6537c8f265bc621b/CC_Configuration_5_EN.JPG)
 
 ### Identifying Information
 
 This option allows you to select which store identification information should be displayed at the top of issued invoices.
 
-![CC_Configuration_6_EN](//images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/94bce774843c23fa582f065689423087/CC_Configuration_6_EN.JPG)
+![CC_Configuration_6_EN](https://images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/94bce774843c23fa582f065689423087/CC_Configuration_6_EN.JPG)
 
-![CC_Configuration_8_EN](//images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/7078eccb9c08d690fb0f453456f2dcaf/CC_Configuration_8_EN.JPG)
+![CC_Configuration_8_EN](https://images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/7078eccb9c08d690fb0f453456f2dcaf/CC_Configuration_8_EN.JPG)
 
 ## Payment conditions
 
@@ -103,7 +103,7 @@ To create payment conditions for Customer Credit invoices, follow the steps belo
 5. Enable the condition in the __Status__ field.
 6. In __Configure Due Date and Installment Rules__, indicate the number of installments, due period (in days) and the simple interest rate to be applied to each installment. To create more than one payment condition, click `Add new condition`.
 
-![CC_Configuration_9_EN](//images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/77399f912ebbb03ac5611682eca77c06/CC_Configuration_9_EN.JPG)
+![CC_Configuration_9_EN](https://images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/77399f912ebbb03ac5611682eca77c06/CC_Configuration_9_EN.JPG)
 
 <blockquote><ui>7. If you wish, you can also configure <a href="https://help.vtex.com/en/tutorial/special-conditions--tutorials_456">payment special conditions</a>.</ui>
 
diff --git a/docs/tracks/en/setting-up-the-order-summary-printing.md b/docs/tracks/en/setting-up-the-order-summary-printing.md
index 7a0d424d4..19acc5790 100644
--- a/docs/tracks/en/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/en/setting-up-the-order-summary-printing.md
@@ -16,7 +16,7 @@ trackSlugEN: instore-customizations
 
 When the salesperson completes an order with inStore, they can print a summary of that order. But, to enable this functionality, you need to make some settings.
 
-![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
+![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
 
 Two steps are required:
 
@@ -50,7 +50,7 @@ Do not remove any of the other properties present in the <code>window.INSTORE_CO
 
 This change will make the __Configure device__ option appear in the inStore main menu, as shown in the image below. It is through this option that you will configure the printer.
 
-![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
+![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
 <div class="alert alert-info">
 <strong>Note:</strong> There is an option to automatically print the order summary as soon as the order is completed. To enable it, add the <code>printPageAutomatically</code> property with the value <code>true</code> inside the <code>printingConfig</code> object. See below how the code would look like in this case.
@@ -84,11 +84,11 @@ With AppKey and AppToken in hand, follow the steps below:
 2. Open the inStore app and enter the store where you want to set up the printer.
 3. In the inStore main menu, in the Settings section, the option __Configure device__ should now appear. Click on that option.
 
-![15. Configurar impressão de resumo do pedido - 3](//images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
+![15. Configurar impressão de resumo do pedido - 3](https://images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
 
 You will find the summary of the configured device. If this is the first time you are making this configuration, the fields on this screen will be empty. If a device has been previously configured, some information about the device will be displayed (Device name and Default printer). Click the __Edit__ button.
 
-![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 A form will show containing the __AppKey__, __AppToken__ and __name__ fields with which you want to identify the device. After entering this data, click __Configure__.
 
diff --git a/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
index 63efea955..d8ede6cc0 100644
--- a/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
@@ -37,7 +37,7 @@ This option allows sales associates to share shopping carts ready for purchase w
 
 See the step-by-step instructions illustrated below.
 
-![socialselling-sugestaocarrinho-en](//images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/66a5a405d1c213ebe66d798799e972ef/socialselling-sugestaocarrinho-en.gif)
+![socialselling-sugestaocarrinho-en](https://images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/66a5a405d1c213ebe66d798799e972ef/socialselling-sugestaocarrinho-en.gif)
 
 The same link is shareable with multiple customers as many times as they like. Each time a person accesses this link, a new shopping cart is generated, exactly like the one created in VTEX Sales App. Carts accessed are also associated with the sales associate account and their code, if they have one.
 
@@ -63,4 +63,4 @@ In this case, the sales associate needs to add items to the cart, fill in the cu
 
 See the step-by-step instructions illustrated below.
 
-![socialselling-paymentlink-en](//images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/13e08b6558e7c4b2ecd22c242d4f7247/socialselling-paymentlink-en.gif)
+![socialselling-paymentlink-en](https://images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/13e08b6558e7c4b2ecd22c242d4f7247/socialselling-paymentlink-en.gif)
diff --git a/docs/tracks/en/shipping-strategies.md b/docs/tracks/en/shipping-strategies.md
index edb9e6f15..653c327d5 100644
--- a/docs/tracks/en/shipping-strategies.md
+++ b/docs/tracks/en/shipping-strategies.md
@@ -18,7 +18,7 @@ The shipping options offered to the customer at the checkout of your store are c
 
 The shipping strategy defines how warehouses, loading docks, and shipping policies interact to meet the needs of your customers and your business. 
 
-![Estrategia EnvioEN](//images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/f21e70736f667399bb811dea84caf5c7/Estrategia_EnvioEN.png)
+![Estrategia EnvioEN](https://images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/f21e70736f667399bb811dea84caf5c7/Estrategia_EnvioEN.png)
 
 The shipping strategy is defined by three logistics entities:
 
diff --git a/docs/tracks/en/specifications-mapping.md b/docs/tracks/en/specifications-mapping.md
index 9c52b3589..52a6abf4b 100644
--- a/docs/tracks/en/specifications-mapping.md
+++ b/docs/tracks/en/specifications-mapping.md
@@ -20,6 +20,6 @@ In the **Specifications mapping** section seen in *Marketplace > Lengow Integrat
 
 For each specification, fill in the left column with its name in VTEX and the right column with the name that should be used in Lengow. Both columns may have the same values. If needed, you may repeat a VTEX specification to map it out to multiple Lengow specifications.
 
-![Lengow - Specifications mapping](//images.ctfassets.net/alneenqid6w5/4mcy8worOtuTEiPzSBHthD/8c7304156d13269af3eca4c1efa12eec/Screen_Shot_2020-07-01_at_23.00.21.png)
+![Lengow - Specifications mapping](https://images.ctfassets.net/alneenqid6w5/4mcy8worOtuTEiPzSBHthD/8c7304156d13269af3eca4c1efa12eec/Screen_Shot_2020-07-01_at_23.00.21.png)
 
 <div class="alert alert-warning" role="alert">All <a href="https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP" target="_blank">specification fields</a> must be created and set up prior to this step. Make sure the name used in the mapping tables is exactly as seen in the Catalog, otherwise the connector will not be able to find the proper values to send to Lengow.</div>
diff --git a/docs/tracks/en/store-development.md b/docs/tracks/en/store-development.md
index 5f9e72c8d..2743c71fb 100644
--- a/docs/tracks/en/store-development.md
+++ b/docs/tracks/en/store-development.md
@@ -19,7 +19,7 @@ In an ecommerce store, both the interface that users see and interact with, and
 - **Frontend**: The frontend consists of the visual layer of an application, such as a website's or mobile app's interface. It is through it that users interact with a store. On VTEX, three different technologies can be used to build storefronts: the CMS Portal (Legacy), the Store Framework, and FastStore.
 - **Backend**: The backend is the layer responsible for computing and processing all the data needed to execute the functionalities offered by a given application. On VTEX, the integration and backend application development are done mainly through VTEX IO and VTEX APIs.
 
-![storefront mockup](//images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/9f957800cf3b303a7887421c75fb1f74/image1.png)
+![storefront mockup](https://images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/9f957800cf3b303a7887421c75fb1f74/image1.png)
 
 In the following sections, we will further explore the key aspects and technologies related to store development on VTEX.
 
diff --git a/docs/tracks/en/technical-support.md b/docs/tracks/en/technical-support.md
index 41a04bf50..d2a063f69 100644
--- a/docs/tracks/en/technical-support.md
+++ b/docs/tracks/en/technical-support.md
@@ -28,6 +28,6 @@ The following table shows the main topics related to technical support:
 
 If the user needs technical support and can't find solutions on the portals and documentation mentioned, they can contact us via the [Support page](https://support.vtex.com/hc/pt-br/requests) and select the **Technical** option via the VTEX IA Support Bot, a chatbot focused on technical assistance, as shown in the image below:
 
-![Support imagem 2 -EN](//images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/bebfbb302b01ba80644d77e460136f99/support_imagem2_EN.png)
+![Support imagem 2 -EN](https://images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/bebfbb302b01ba80644d77e460136f99/support_imagem2_EN.png)
 
 If the user needs support beyond the VTEX IA Support Bot, they can open a ticket by clicking `OPEN TICKET`. For more information on how to complete a ticket for technical support, read the [Opening tickets to VTEX Support - Technical](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#technical) article.
diff --git a/docs/tracks/en/the-reservation.md b/docs/tracks/en/the-reservation.md
index 95cda2559..86062a28d 100644
--- a/docs/tracks/en/the-reservation.md
+++ b/docs/tracks/en/the-reservation.md
@@ -34,7 +34,7 @@ This is the reservation flow at VTEX:
  
  3. Finally, once the order is being prepared for delivery, the items move to the status `Reservation Acknowledged`. This status indicates that the items no longer exist in the physical inventory.
 
-![reservation en](//images.ctfassets.net/alneenqid6w5/7mm0YP3bcfb5fqZf5XhmZX/8798695363d5f4008f0a9c7078ebc386/reservation_en.png)
+![reservation en](https://images.ctfassets.net/alneenqid6w5/7mm0YP3bcfb5fqZf5XhmZX/8798695363d5f4008f0a9c7078ebc386/reservation_en.png)
 
 <div class="alert alert-warning">
 VTEX does not automatically remove items from the inventory, even after they have moved to <code>Reservation Recognized</code> status. Purchased items will remain in this status until the ERP or the store remove them from the inventory.
diff --git a/docs/tracks/en/the-transaction-flow.md b/docs/tracks/en/the-transaction-flow.md
index d5e5a5e3d..9daa6d627 100644
--- a/docs/tracks/en/the-transaction-flow.md
+++ b/docs/tracks/en/the-transaction-flow.md
@@ -22,7 +22,7 @@ Transactions performed by VTEX payments module go through various statuses, from
 
 See below an example timeline with the transaction statuses.
 
-![Transaction Flow](//images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
+![Transaction Flow](https://images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
 
 1. __Authorizing__: This is the first status of a Payments transaction. At this stage, Payments indicates that the process of sending information to an acquirer or to another gateway has begun.
 2. __Authorized__: Upon the initiation of the authorization process, the acquirer or other gateway sends the transaction information to the issuing bank. The bank responds if the transaction should be authorized or not. If it denies the transaction, the payment is __canceled__. If it authorizes, the transaction status changes to __Authorized__.
diff --git a/docs/tracks/en/unified-commerce-101.md b/docs/tracks/en/unified-commerce-101.md
index cfedb3eb8..5385f7aef 100644
--- a/docs/tracks/en/unified-commerce-101.md
+++ b/docs/tracks/en/unified-commerce-101.md
@@ -16,7 +16,7 @@ trackSlugEN: unified-commerce-strategies
 
 The evolution of online retail has brought a series of improvements to the customer experience, and one of the most relevant is perhaps the one that transformed the multichannel relationship between customer and store into an omnichannel relationship.
 
-![32. Unified Commerce 101 - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/YYPXpy8HRuqRE8CX2cgYC/b4c9a5a5b094d256798a3a017c4d9ce7/32._Unified_Commerce_101_-_1_-_EN.png_h_250)
+![32. Unified Commerce 101 - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/YYPXpy8HRuqRE8CX2cgYC/b4c9a5a5b094d256798a3a017c4d9ce7/32._Unified_Commerce_101_-_1_-_EN.png_h_250)
 
 In a __multichannel__ architecture, each channel communicates independently with the store, be it the ecommerce, physical stores, call centers, social media, etc. When a customer interacts with one of these channels, the store has no knowledge at all of who that customer is.
 
@@ -26,7 +26,7 @@ In omnichannel, however, orders are still processed in isolation. Although there
 
 The __Unified Commerce__ solves this problem.
 
-![32. Unified Commerce 101 - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/6IuAQNFiyqaUgcRLA2mSDP/673202ebbfa44580a9e737269b738b9c/32._Unified_Commerce_101_-_2_-_EN.png_h_250)
+![32. Unified Commerce 101 - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6IuAQNFiyqaUgcRLA2mSDP/673202ebbfa44580a9e737269b738b9c/32._Unified_Commerce_101_-_2_-_EN.png_h_250)
 
 Unified Commerce is an evolution of omnichannel: in addition to data sharing, this strategy also involves __unifying the order processing and management system__. In practice, this means that every order placed on one store channel is not only visible by other channels but can be processed by them.
 
diff --git a/docs/tracks/en/unified-commerce.md b/docs/tracks/en/unified-commerce.md
index a6835c5a4..d08fdd362 100644
--- a/docs/tracks/en/unified-commerce.md
+++ b/docs/tracks/en/unified-commerce.md
@@ -20,7 +20,7 @@ trackSlugEN: next-steps-after-the-go-live
 
 [Franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) are accounts associated with a [main account](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). Companies with multiple physical stores, franchisees, or multi-brands can create franchise accounts associated with the brand's main account.
 
-![main account](//images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/aaa2c7b886fb7a050c684465fb08c8f8/next_steps_image1_EN.png)
+![main account](https://images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/aaa2c7b886fb7a050c684465fb08c8f8/next_steps_image1_EN.png)
 
 This model shares Catalog and [storefront](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) information, allowing the franchise accounts' inventory to be available for sale in the main store. It also supports different unified commerce strategies, such as [ship from store](#ship-from-store), [physical stores as pickup points](#pickup-points), and [endless aisle](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
 
diff --git a/docs/tracks/en/unified-search.md b/docs/tracks/en/unified-search.md
index 1b2d69e64..10c358cee 100644
--- a/docs/tracks/en/unified-search.md
+++ b/docs/tracks/en/unified-search.md
@@ -20,13 +20,13 @@ VTEX Sales App's [endless aisle](https://help.vtex.com/en/tracks/estrategias-de-
 This feature uses the browser's cache to optimize searches in scenarios with slow internet connections.
 </div>
 
-![Barra busca - EN](//images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/31aeb140714a23b6e5d0f958e90dcea2/Tela_1_barra_busca.gif)
+![Barra busca - EN](https://images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/31aeb140714a23b6e5d0f958e90dcea2/Tela_1_barra_busca.gif)
 
 VTEX Sales App features a unified search, which means that, when searching for a product in the app, search results will include not only the local inventory (of the current physical store) but also inventories of other physical stores and distribution centers associated with the ecommerce operation.
 
 Search results are organized to improve customer experience, displaying images that facilitate product identification and providing relevant information for sales associates.
 
-![Busca unificada - EN](//images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/89c5c59cc9e5ce4f86f3d97966439ed7/Busca_unificada_VTEX_Sales_App.png)
+![Busca unificada - EN](https://images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/89c5c59cc9e5ce4f86f3d97966439ed7/Busca_unificada_VTEX_Sales_App.png)
 
 When you click the `Add to Cart` option, the following product information will be displayed:
 - Product variations, SKUs.
@@ -35,7 +35,7 @@ When you click the `Add to Cart` option, the following product information will
 
 To add a product to the cart, select the desired variation, shipping option, and quantity, then click `Add to Cart`.
 
-![Carrinho - EN](//images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/4e2090b5e30f545a65f35c7faefd67ac/Adicionar_ao_carrinho_VTEX_Sales_App.png)
+![Carrinho - EN](https://images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/4e2090b5e30f545a65f35c7faefd67ac/Adicionar_ao_carrinho_VTEX_Sales_App.png)
 
 ## Filters
 
diff --git a/docs/tracks/en/update-and-import-product-feed.md b/docs/tracks/en/update-and-import-product-feed.md
index 8c15d0739..c485c52e6 100644
--- a/docs/tracks/en/update-and-import-product-feed.md
+++ b/docs/tracks/en/update-and-import-product-feed.md
@@ -23,6 +23,6 @@ http://{accountName}.myvtex.com/integration/lengow/feed
 
 Using the Lengow product feed URL you will now be able to import your products into a new Lengow catalogue using the direct link (HTTP/HTTPS) method.
 
-![Lengow - Import products](//images.ctfassets.net/alneenqid6w5/67HpK4zsXv2GeqZZ3U99zj/c1472e7e7b92e1a41a7ee7e8a3a38422/image4.png)
+![Lengow - Import products](https://images.ctfassets.net/alneenqid6w5/67HpK4zsXv2GeqZZ3U99zj/c1472e7e7b92e1a41a7ee7e8a3a38422/image4.png)
 
 For more information on how to publish your products on the channels of your choice, please refer to the how-to articles available in the Lengow Help Center.
diff --git a/docs/tracks/en/using-custom-controls.md b/docs/tracks/en/using-custom-controls.md
index 245a18cc6..ff235bbe5 100644
--- a/docs/tracks/en/using-custom-controls.md
+++ b/docs/tracks/en/using-custom-controls.md
@@ -32,7 +32,7 @@ To create a custom control, follow the walk-through below:
 3. Click on the __CMS__ folder.
 4. Click on the __Custom Elements__ folder.
 5. Click on the __Add__ button.
-![8 1](//images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
+![8 1](https://images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
 6. Fill in the __Name__ field with the custom control name.
 7. Fill in the __Tag name__ field. This is the name that will be used in the control when adding it to the template.
 8. Select the control type on __Type__.
diff --git a/docs/tracks/en/vtex-modules-i.md b/docs/tracks/en/vtex-modules-i.md
index b132707b0..e21a770f2 100644
--- a/docs/tracks/en/vtex-modules-i.md
+++ b/docs/tracks/en/vtex-modules-i.md
@@ -40,7 +40,7 @@ There are no prior settings to make before configuring the Catalog, but the foll
 
 The Catalog architecture has some key concepts: category, brand, product, SKU (_Stock Keeping Unit_) and specification. The image below shows the relation between these concepts:
 
-![arquitetura-catalogo-EN](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
+![arquitetura-catalogo-EN](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/2bb87144a5e665c082374be39da9d7af/EN.png)
 
 The store catalog must be created following the steps below:
 
@@ -77,7 +77,7 @@ __Example__: Department `Women`, Category `Shirts and T-shirts`, and Sub-categor
 
 Before importing the store catalog to VTEX, we recommend that you start working on the category tree by creating a table such as the one below. This allows you to better view the tree's organization and the display of specifications.
 
-![catalog_arquitecture_table_EN](//images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/f539ab283449f2aa2163be8b8ddd957e/catalog_arquitecture_table_EN.png)
+![catalog_arquitecture_table_EN](https://images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/f539ab283449f2aa2163be8b8ddd957e/catalog_arquitecture_table_EN.png)
 
 <div class="alert alert-info">
 For more information on how to import back-office specifications, read the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
@@ -158,7 +158,7 @@ Prices are the sales value information for your SKUs. These prices are stored in
 
 The image below illustrates the relationship between prices, the price table, and the context in which they will be applied:
 
-![Conceito de Preços-EN](//images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/c229973cb7f6f135570b309d23af10a3/Conceito_de_Pre_os-EN.png)
+![Conceito de Preços-EN](https://images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/c229973cb7f6f135570b309d23af10a3/Conceito_de_Pre_os-EN.png)
 
 You can create price tables for your SKUs in three ways:
 
@@ -278,7 +278,7 @@ The set of essential logistics settings for a VTEX store is called [Shipping Str
 
 The image below shows how these concepts relate to each other when selling a product:
 
-![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
+![shipping_strategy_EN](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
 
 The following table shows the store's main logistics settings on VTEX:
 
@@ -331,7 +331,7 @@ The [main use cases](https://help.vtex.com/en/tutorial/lead_time-shipping-time-a
 
 The VTEX platform considers the following settings to [calculate the order shipping time](https://help.vtex.com/en/tutorial/how-shipping-calculation-works--tutorials_116):
 
-![Shipping Calculation_EN](//images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/7088aadd2ae56175b3a9b57ae0af38a8/Shipping_Calculation_EN.png)
+![Shipping Calculation_EN](https://images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/7088aadd2ae56175b3a9b57ae0af38a8/Shipping_Calculation_EN.png)
 
 - [Lead time](https://help.vtex.com/en/tutorial/lead-time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B): Configurable amount of time for an SKU in stock. This configuration is optional and is set to zero days by default.
 - [Warehouse time](https://help.vtex.com/en/tutorial/managing-warehouses--tutorials_137): time it takes for an SKU to move from a warehouse to a [loading dock](https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj). This configuration is required, but you can set the time to zero.
diff --git a/docs/tracks/en/vtex-modules-ii.md b/docs/tracks/en/vtex-modules-ii.md
index 875034a38..cd32e6336 100644
--- a/docs/tracks/en/vtex-modules-ii.md
+++ b/docs/tracks/en/vtex-modules-ii.md
@@ -55,11 +55,11 @@ The table below shows the main agents and terms used in the Payments context:
 
 When a purchase is completed on VTEX, a new transaction is created and the payment flow begins. In the example below, you can see the payment flow for a credit card purchase:
 
-![payments-en](//images.ctfassets.net/alneenqid6w5/6rqeRDDqm3rijRrwpG6Lb1/8df497f70d26352352a11d942887afa7/payments_image1_EN__1_.JPG)
+![payments-en](https://images.ctfassets.net/alneenqid6w5/6rqeRDDqm3rijRrwpG6Lb1/8df497f70d26352352a11d942887afa7/payments_image1_EN__1_.JPG)
 
 As the data is transferred among the agents responsible for data processing, the payment transaction status is updated to reflect the current stage of the resources in the flow. In the credit card payment flow, we can consider the following example of transaction statuses:
 
-![payments-flow-en](//images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/14fa9b346e6a041fa934f2cfa9d94ace/payments_image2_ALL.JPG)
+![payments-flow-en](https://images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/14fa9b346e6a041fa934f2cfa9d94ace/payments_image2_ALL.JPG)
 
 ### Configuring payments in your store
 
@@ -180,7 +180,7 @@ In the VTEX Admin, under **Orders > [All Orders](https://help.vtex.com/en/tutori
 
 On the order details page, you can also track the progress of the [order flow](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196). The image below illustrates an example of this flow when the store acts as both a marketplace and a seller:
 
-![order-flow-en](//images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/3ea6fe2efb78e9b449acb2dac8b1700f/pedido_fluxo_completo_en.png)
+![order-flow-en](https://images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/3ea6fe2efb78e9b449acb2dac8b1700f/pedido_fluxo_completo_en.png)
 
 To find a purchase record in the VTEX Admin, you can either [filter orders](https://help.vtex.com/en/tutorial/filtering-all-orders--tutorials_192) on the **All Orders** page or use the global search bar, which is accessible from any page within the VTEX Admin. To search, simply select the `Orders` option in the right corner of the search bar and enter any of the following values:
 
@@ -235,7 +235,7 @@ Checkout is the last stage in the online shopping process, playing a significant
 
 To ensure the checkout will work properly, the following modules must be correctly configured: [Catalog](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), [Logistics](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx), [Prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP#), [Promotions](https://help.vtex.com/en/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#), [Payments](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#), and [Orders](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE).
 
-![checkout-en](//images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/fd3e825135b5ca4f2a1c3b976bf9d9ad/checkout_image_EN.jpg)
+![checkout-en](https://images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/fd3e825135b5ca4f2a1c3b976bf9d9ad/checkout_image_EN.jpg)
 
 Sharing information allows processing details regarding availability, prices, applicable promotions, shipping options, and payment methods.
 
diff --git a/docs/tracks/en/what-is-a-logistics-route.md b/docs/tracks/en/what-is-a-logistics-route.md
index bb1d4d026..851a65f91 100644
--- a/docs/tracks/en/what-is-a-logistics-route.md
+++ b/docs/tracks/en/what-is-a-logistics-route.md
@@ -33,4 +33,4 @@ To add a loading dock to a store's admin, follow the steps detailed in this [lin
 ### Carrier
 A carrier is used to distribute orders to the their respective end users and is comprised of a fleet of vehicles that will perform the actual deliveries. The distribution center sends orders out for delivery directly to the carrier that will be used to complete the process until its final destination.
 
-![EN Conceitos Logística](//images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
+![EN Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/4G4LhYlo2dWZKdyM17uxry/745f847e0eae518e231c98bfff99906e/EN_Conceitos_Log__stica.png)
diff --git a/docs/tracks/en/what-is-the-cms.md b/docs/tracks/en/what-is-the-cms.md
index 5efa7bbe1..2df70a6ce 100644
--- a/docs/tracks/en/what-is-the-cms.md
+++ b/docs/tracks/en/what-is-the-cms.md
@@ -14,7 +14,7 @@ trackId: 2YcpgIljVaLVQYMzxQbc3z
 trackSlugEN: cms
 ---
 
-![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System) is a feature dedicated to manage content in a constant and practical manner.
 
diff --git a/docs/tracks/en/what-is-the-master-user.md b/docs/tracks/en/what-is-the-master-user.md
index 30636e3b2..743f74187 100644
--- a/docs/tracks/en/what-is-the-master-user.md
+++ b/docs/tracks/en/what-is-the-master-user.md
@@ -26,7 +26,7 @@ If your user has role to the Account management module, you can verify who is th
 
 By clicking on the desired account name, the Sponsor user's name and email are in the __Contact__ section.
 
-![usuario-master-contato en](//images.ctfassets.net/alneenqid6w5/3ezUM1WmYEcIkGOoKm2s8e/0d14ffe3cce780a79f6111b46943db80/contato_usuario_master_en.png)
+![usuario-master-contato en](https://images.ctfassets.net/alneenqid6w5/3ezUM1WmYEcIkGOoKm2s8e/0d14ffe3cce780a79f6111b46943db80/contato_usuario_master_en.png)
 
 Among the actions that only the Sponsor user can take are:
 - Reindex the catalog.
diff --git a/docs/tracks/en/whatsapp-integration.md b/docs/tracks/en/whatsapp-integration.md
index c3c1c709a..af9735691 100644
--- a/docs/tracks/en/whatsapp-integration.md
+++ b/docs/tracks/en/whatsapp-integration.md
@@ -62,17 +62,17 @@ After installing the app, VTEX will share the VTEX Conversational Commerce Admin
 Then, follow the steps below:
 
 1. Log in to the VTEX Admin using the URL provided by the support team. You will be directed to the screen below:
-![Track 101 - Conversational Commerce 1 - PT](//images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 1 - PT](https://images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
 2. Click the `Configure WhatsApp Business Account` button.
 3. A Facebook window will open for configuration. Log in with the desired Business Manager Admin profile.
 4. Select the `Create a WhatsApp Business Account` option.
 5. Enter the account name for your WhatsApp profile.
 6. Select the category and enter the account description. 
-![Track 101 - Conversational Commerce 2 - PT](//images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 2 - PT](https://images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
 7. Check the phone number you want to associate with the account via the code sent to the phone.
 8. Notify VTEX support to complete the configuration.
 
 Once the configuration is complete, the alert below will be displayed in the Admin. 
 
-![Track 101 - Conversational Commerce 3 - PT](//images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 3 - PT](https://images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
 
diff --git a/docs/tracks/es/access-to-the-customers-last-cart.md b/docs/tracks/es/access-to-the-customers-last-cart.md
index a9e5645ba..261342adf 100644
--- a/docs/tracks/es/access-to-the-customers-last-cart.md
+++ b/docs/tracks/es/access-to-the-customers-last-cart.md
@@ -20,4 +20,4 @@ Al tener acceso a esta información, el vendedor puede intentar completar la ven
 
 Simplemente haga clic en `Acceder` para ver los productos en el carrito abandonado.
 
-![last-cart-es](//images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/13c98f924fcee93b1a04f4bcd9f91821/last-cart-ES.png)
+![last-cart-es](https://images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/13c98f924fcee93b1a04f4bcd9f91821/last-cart-ES.png)
diff --git a/docs/tracks/es/accounts-and-architecture.md b/docs/tracks/es/accounts-and-architecture.md
index fbfd5dc64..531cc4736 100644
--- a/docs/tracks/es/accounts-and-architecture.md
+++ b/docs/tracks/es/accounts-and-architecture.md
@@ -28,7 +28,7 @@ Los tipos de cuenta VTEX son:
 
 La siguiente imagen muestra una visión general para ayudarte a [elegir entre la cuenta estándar, franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78):
 
-![main_account_franchise_seller_portal_ES](//images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/befcaed2563320ca9280d44759fe4962/main_account_franchise_seller_portal_ES.png)
+![main_account_franchise_seller_portal_ES](https://images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/befcaed2563320ca9280d44759fe4962/main_account_franchise_seller_portal_ES.png)
 
 ## Recursos de las cuentas
 
@@ -58,7 +58,7 @@ Sin embargo, el uso simultáneo de muchas políticas comerciales puede afectar e
 
 La siguiente imagen es un ejemplo de la relación entre la cuenta principal, entorno (subcuenta), multitiendas (tiendas) y políticas comerciales:  
 
-![multistore_aditional_environment_ES](//images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/a0d486cc33bba9057698b54eb2f8eaf4/multistore_aditional_environment_ES.png)
+![multistore_aditional_environment_ES](https://images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/a0d486cc33bba9057698b54eb2f8eaf4/multistore_aditional_environment_ES.png)
 
 ### Multitienda
 
diff --git a/docs/tracks/es/add-an-image-to-the-sku.md b/docs/tracks/es/add-an-image-to-the-sku.md
index 9fd342a63..4b6e2c360 100644
--- a/docs/tracks/es/add-an-image-to-the-sku.md
+++ b/docs/tracks/es/add-an-image-to-the-sku.md
@@ -22,7 +22,7 @@ Si ninguna imagen está asociada a un SKU, no se activará.
 
 Por lo tanto, después de terminar de llenar la configuración de su nuevo SKU y hacer clic en __Guardar__, usted será llevado a la pantalla de registro de imagen, donde se muestra el mensaje siguiente.
 
-![SKUimg](//images.contentful.com/alneenqid6w5/2lV4fLbTJqEiCmUQOaaOOm/c7480c2c8095f51c8236d2022991fe43/SKUimg.png)
+![SKUimg](https://images.contentful.com/alneenqid6w5/2lV4fLbTJqEiCmUQOaaOOm/c7480c2c8095f51c8236d2022991fe43/SKUimg.png)
 
 Para asociar una imagen a ese SKU, siga estos pasos:
 1. Haga clic en el botón __Insertar__.
@@ -31,4 +31,4 @@ Para asociar una imagen a ese SKU, siga estos pasos:
 4. Haga clic en el botón __Enviar__.
 5. Haga clic en __Guardar__.
 
-![SKUimg3](//images.contentful.com/alneenqid6w5/5E5rl4SdC8a4qSy40Gqaum/7e000aebd9a7f7087229f630f8a6c38d/SKUimg3.gif)
+![SKUimg3](https://images.contentful.com/alneenqid6w5/5E5rl4SdC8a4qSy40Gqaum/7e000aebd9a7f7087229f630f8a6c38d/SKUimg3.gif)
diff --git a/docs/tracks/es/add-on-products.md b/docs/tracks/es/add-on-products.md
index 990f2db66..17519ebd9 100644
--- a/docs/tracks/es/add-on-products.md
+++ b/docs/tracks/es/add-on-products.md
@@ -27,18 +27,18 @@ Los productos add-on son soluciones que VTEX ofrece para satisfacer demandas esp
 - **Anunciantes:** marcas que pueden crear campañas de anuncios para promocionar productos en storefronts de tiendas VTEX que tengan esos mismos productos en sus catálogos, incrementando las ventas.
 - **Retailers:** son retailers que tienen tiendas VTEX que pueden ofrecer espacios en sus storefronts para que los anunciantes promocionen sus productos. Estos retailers recibirán una valor por cada clic recibido en anuncios de su tienda.
 
-![vtex_ad_network_sponsored_ES](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/bfec823e3960cac69bf878395437cdec/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_ES](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/bfec823e3960cac69bf878395437cdec/vtex_ad_network_sponsored.png)
 
 ## VTEX Assisted Sales
 
 [Assisted Sales (SuiteShare)](https://help.vtex.com/es/tracks/suiteshare--khP0p8mjIYRIpvM7Cb4Zr/onWmyS8j4Thhde67UBBsB) es una solución creada por VTEX para potenciar las ventas en WhatsApp que ayuda a atraer nuevos clientes, integrar herramientas de ventas, gestionar datos de atención al usuario y métricas de resultados.
 
-![suiteshare-es](//images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/2e88a04abe0eeb3008df7f4bb0f87f49/next_steps_image11_ONLYPT.JPG)
+![suiteshare-es](https://images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/2e88a04abe0eeb3008df7f4bb0f87f49/next_steps_image11_ONLYPT.JPG)
 
 ## VTEX Live Shopping
 VTEX Live Shopping permite crear transmisiones online para hacer demostraciones en vivo de las características de los productos de la tienda. Las interacciones directas e instantáneas con los clientes ayudan a mejorar el engagement del público con la marca y aumentar el rendimiento de ventas.
 
-![live-shopping-es](//images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/5db3287d499b2abdc4acfe7ef38689f7/next_steps_image5_ALL.JPG)
+![live-shopping-es](https://images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/5db3287d499b2abdc4acfe7ef38689f7/next_steps_image5_ALL.JPG)
 
 Para programar una demostración de la aplicación con un especialista, debes acceder a la página de [VTEX Live Shopping](https://vtex.com/es-es/live-shopping/#contact).
 
@@ -46,7 +46,7 @@ Para programar una demostración de la aplicación con un especialista, debes ac
 
 VTEX Personal Shopper permite ofrecer un servicio personalizado directo entre el cliente y el vendedor para incorporar la experiencia de la tienda física al entorno digital. Con esta aplicación el vendedor puede hacer demostraciones de productos, dar recomendaciones y aclarar las dudas de los clientes. Durante la videollamada se pueden agregar ítems al carrito.
 
-![personal-shopper-es](//images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/5ea754ef7cfe6f2f4a17db69964d8ca9/next_steps_image6_ALL.JPG)
+![personal-shopper-es](https://images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/5ea754ef7cfe6f2f4a17db69964d8ca9/next_steps_image6_ALL.JPG)
 
 Para programar una demostración de la aplicación con un especialista, debes acceder a la página de [VTEX Personal Shopper](https://vtex.com/mx-es/vtex-personal-shopper/).
 
@@ -59,7 +59,7 @@ La solución se compone de:
 
 - [Aplicación Last Mile](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): coordina el envío de paquetes desde los almacenes o tiendas a las direcciones de los clientes mediante la creación de rutas inteligentes de entrega, selección de conductores disponibles y seguimiento de la ubicación exacta del pedido.
 
-![pick-and-pack-es](//images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/2a0495961f4d1dd6024ab04af3af8893/next_steps_image7_ALL.JPG)
+![pick-and-pack-es](https://images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/2a0495961f4d1dd6024ab04af3af8893/next_steps_image7_ALL.JPG)
 
 Para ver una demostración de la aplicación o programar una sesión personalizada con un especialista, debes acceder a la página de [VTEX Pick and Pack](https://content.vtex.com/es/pick-and-pack/). 
 
@@ -74,7 +74,7 @@ Con [VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-co
 
 - Gestionar métricas de rendimiento por vendedor.
 
-![sales-app-es](//images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/fdac94d9c5de3a71957368c552b3cecd/image3.png)
+![sales-app-es](https://images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/fdac94d9c5de3a71957368c552b3cecd/image3.png)
 
 Para ver una demostración de la aplicación o programar una sesión personalizada con un especialista, debes acceder a la página de [VTEX Sales App](https://assets.vtex.com/es-sales-app/).
 
@@ -84,7 +84,7 @@ Explora las opciones de envío de productos a todas las regiones de Brasil con [
 
 **VTEX Shipping Network** permite conectar transportadoras para crear una red de entrega integrada, que actualmente cuenta con más de 20 socios, para ofrecer a los clientes mejores opciones de costo y plazo.
 
-![shipping-network-es](//images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/5fec34d4b9279162c37ff9efff927a49/image7.png)
+![shipping-network-es](https://images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/5fec34d4b9279162c37ff9efff927a49/image7.png)
 
 Para más información, debes acceder a la página de VTEX Shipping Network.
 
@@ -96,7 +96,7 @@ Para más información, debes acceder a la página de VTEX Shipping Network.
 
 [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) es una asociación entre VTEX y Correios en la que la tienda puede contratar servicios de envío de productos a través de PAC y SEDEX directamente en el Admin VTEX, con tarifas especiales que reducen los costos operativos del envío.
 
-![image6](//images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/536e7173450c2b066da7ef539baf8e19/image6.png)
+![image6](https://images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/536e7173450c2b066da7ef539baf8e19/image6.png)
 
 Contratar la solución es simple y solo toma unos pocos minutos: basta con aceptar los Términos y condiciones y la [activación](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) directamente en el Admin de la tienda. Algunas de las funcionalidades de VTEX Shipping Network Correios son:
 
diff --git a/docs/tracks/es/add-pickup-points.md b/docs/tracks/es/add-pickup-points.md
index 1a34a38fd..b929226e5 100644
--- a/docs/tracks/es/add-pickup-points.md
+++ b/docs/tracks/es/add-pickup-points.md
@@ -33,7 +33,7 @@ Siga el siguiente procedimiento para registrar un punto de recogida en su tienda
 4. Rellene los campos del formulario de punto de recogida. Para entender mejor el significado de cada campo, consulte la sección [Campos de registro](#campos-de-registro), abajo.
 5. Haga clic en el botón **Guardar cambios**
 
-![ES Cadastrar Ponto de Retirada GIF](//images.ctfassets.net/alneenqid6w5/1tWiezGUaoTRohpM2m5241/f1dfb789d45d72d8054f0f4ccebe740b/ES_Cadastrar_Ponto_de_Retirada_GIF.gif)
+![ES Cadastrar Ponto de Retirada GIF](https://images.ctfassets.net/alneenqid6w5/1tWiezGUaoTRohpM2m5241/f1dfb789d45d72d8054f0f4ccebe740b/ES_Cadastrar_Ponto_de_Retirada_GIF.gif)
 
 
 ### Campos de registro
diff --git a/docs/tracks/es/add-sku-specifications.md b/docs/tracks/es/add-sku-specifications.md
index 860c56cbb..ad9d4547d 100644
--- a/docs/tracks/es/add-sku-specifications.md
+++ b/docs/tracks/es/add-sku-specifications.md
@@ -35,7 +35,7 @@ Para registrar las especificaciones, su tienda necesita tener departamentos, cat
  7. Rellene los campos del formulario de especificaciones. En el caso de los SKUs, el flag de campo obligatorio siempre está seleccionado por default. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre [cómo rellenar los campos de especificaciones de SKU](https://help.vtex.com/es/tutorial/criando-campo-de-sku--tutorials_119)
  8.  Haga clic en **Guardar**
 
-![ES1](//images.ctfassets.net/alneenqid6w5/4cSrsR60RiWrSSllCFgbsQ/2d8e6ffab449e23f59c3521e67764568/ES1.gif)
+![ES1](https://images.ctfassets.net/alneenqid6w5/4cSrsR60RiWrSSllCFgbsQ/2d8e6ffab449e23f59c3521e67764568/ES1.gif)
 
 Para añadir valores a la especificación de SKU, siga los siguientes pasos:
 
@@ -49,7 +49,7 @@ Para añadir valores a la especificación de SKU, siga los siguientes pasos:
  9. Haga clic en **Nuevo valor**
  10. Escriba el **Nombre** del valor deseado y haga clic en **Guardar**
 
-![ES2](//images.ctfassets.net/alneenqid6w5/7v4nItIFqlZZP6SVOhVlcf/2e81e722d6f6c69a3e551ddc5c221bec/ES2.gif)
+![ES2](https://images.ctfassets.net/alneenqid6w5/7v4nItIFqlZZP6SVOhVlcf/2e81e722d6f6c69a3e551ddc5c221bec/ES2.gif)
 
 ### Vincular las especificaciones a un SKU
 
@@ -65,7 +65,7 @@ Para incluir las especificaciones en un **SKU** siga los siguientes pasos:
  6. Haga clic en la pestaña **Especificaciones** y seleccione el valor de la especificación para ese SKU
  7. Haga clic en **Guardar**
 
-![ES3](//images.ctfassets.net/alneenqid6w5/2r7p71kBKd70qbLDu7EJBS/c10904a508a3a2e5baf02c2a22288c8a/ES3.gif)
+![ES3](https://images.ctfassets.net/alneenqid6w5/2r7p71kBKd70qbLDu7EJBS/c10904a508a3a2e5baf02c2a22288c8a/ES3.gif)
 
 ## Plantilla
 
@@ -94,7 +94,7 @@ Después de rellenar los datos de la plantilla, siga el procedimiento para impor
 5. Haga clic en **Select** para seleccionar la plantilla rellenada
 6. Haga clic en **Importar**
 
-![ES4](//images.ctfassets.net/alneenqid6w5/7gytIVRaKu9gmvZXlIyfe2/073d2f187de623baf5bb44a89615e5e1/ES4.gif)
+![ES4](https://images.ctfassets.net/alneenqid6w5/7gytIVRaKu9gmvZXlIyfe2/073d2f187de623baf5bb44a89615e5e1/ES4.gif)
 
 ## API
 
diff --git a/docs/tracks/es/adding-a-loading-dock.md b/docs/tracks/es/adding-a-loading-dock.md
index 077d04b2d..bdc71b79b 100644
--- a/docs/tracks/es/adding-a-loading-dock.md
+++ b/docs/tracks/es/adding-a-loading-dock.md
@@ -28,7 +28,7 @@ Siga el procedimiento a continuación para registrar un muelle en su tienda:
 4. Rellene los campos del formulario de registro. Para comprender mejor el significado de cada campo, consulte a continuación la sección [Campos de Registro] (#campos-de-registro).
 5. Haga clic en el botón **Guardar**.
 
-![ES Cadastrar Doca GIF](//images.ctfassets.net/alneenqid6w5/1nWWY7VL7GvqTA3s9TuQ3Z/470d02a8d6a602066a4585fd3db15208/ES_Cadastrar_Doca_GIF.gif)
+![ES Cadastrar Doca GIF](https://images.ctfassets.net/alneenqid6w5/1nWWY7VL7GvqTA3s9TuQ3Z/470d02a8d6a602066a4585fd3db15208/ES_Cadastrar_Doca_GIF.gif)
 
 ### Campos de registro
 
diff --git a/docs/tracks/es/adding-extra-text-to-the-order-print.md b/docs/tracks/es/adding-extra-text-to-the-order-print.md
index 5e86c6feb..ffcc7fdaf 100644
--- a/docs/tracks/es/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/es/adding-extra-text-to-the-order-print.md
@@ -38,7 +38,7 @@ Después de volver a cargar inStore, cada vez que un vendedor imprima un pedido,
 
 Antes de agregar texto adicional, la impresión del resumen del pedido tiene el siguiente formato:
 
-![28. Adding extra text to the order print - 1](//images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
+![28. Adding extra text to the order print - 1](https://images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
 
 En nuestro ejemplo, cambiamos el archivo `checkout-instore-custom.js` insertando el siguiente texto adicional:
 
@@ -50,4 +50,4 @@ window.INSTORE_CONFIG = {
 
 Ahora, cada vez que se imprima un resumen del pedido, obtendremos el siguiente resultado:
 
-![28. Adding extra text to the order print - 2](//images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
+![28. Adding extra text to the order print - 2](https://images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
diff --git a/docs/tracks/es/adding-new-stores-to-instore.md b/docs/tracks/es/adding-new-stores-to-instore.md
index ad39f9e9a..ffce7a9ad 100644
--- a/docs/tracks/es/adding-new-stores-to-instore.md
+++ b/docs/tracks/es/adding-new-stores-to-instore.md
@@ -25,7 +25,7 @@ Esta página te permite realizar las siguientes acciones:
 * [Editar](#editar-tienda-física)
 * [Inativar](#inativar-tienda-física)
 
-![loja-fisica-ES](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
+![loja-fisica-ES](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
 
 La página contiene la siguiente información:
 
@@ -50,7 +50,7 @@ Puedes crear una tienda física siguiendo los pasos a continuación:
 
 ### Campos de registro de la tienda física
 
-![loja-fisica2-es](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
+![loja-fisica2-es](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
 
 #### Identificación
 
diff --git a/docs/tracks/es/adding-product-specifications.md b/docs/tracks/es/adding-product-specifications.md
index c0f0667e0..ab207bb0d 100644
--- a/docs/tracks/es/adding-product-specifications.md
+++ b/docs/tracks/es/adding-product-specifications.md
@@ -35,7 +35,7 @@ Para registrar las especificaciones, su tienda necesita tener departamentos, cat
  7. Rellene los campos del formulario de especificaciones. Para comprender mejor el significado de cada campo, acceda a nuestro  artículo sobre [cómo rellenar los campos de especificaciones de producto](https://help.vtex.com/es/tutorial/creando-un-campo-de-producto--tutorials_106)
  8.  Haga clic en **Guardar**.
 
-![ES1](//images.ctfassets.net/alneenqid6w5/26nmolyzhktK7RHFRIfeGn/bd9cc1425426b6f32212083f98760014/ES1.gif)
+![ES1](https://images.ctfassets.net/alneenqid6w5/26nmolyzhktK7RHFRIfeGn/bd9cc1425426b6f32212083f98760014/ES1.gif)
 
 Para añadir valores a la especificación de un producto, siga los pasos a continuación:
 
@@ -49,7 +49,7 @@ Para añadir valores a la especificación de un producto, siga los pasos a conti
  9. Haga clic en **Nuevo valor**.
 10. Escriba el **Nombre** del valor deseado y haga clic en **Guardar**.
 
-![ES2](//images.ctfassets.net/alneenqid6w5/1t2mGbtHaq6Koiz4anwOOO/79b47af516682cb283ccf2faf605af4d/ES2.gif)
+![ES2](https://images.ctfassets.net/alneenqid6w5/1t2mGbtHaq6Koiz4anwOOO/79b47af516682cb283ccf2faf605af4d/ES2.gif)
 
 ### Vincular las especificaciones a un producto
 
@@ -63,7 +63,7 @@ Para incluir las especificaciones en un **Producto** siga los siguientes pasos:
  4. Haga clic en la pestaña **Especificaciones** y elija el valor de la especificación para este producto.
  5. Haga clic en la pestaña **Producto** y después haga clic en **Guardar**.
 
-![ES3](//images.ctfassets.net/alneenqid6w5/1PVutb4VQX4Tbt8VuRzxNA/348cf9167307462767ae79b1f5887105/ES3.gif)
+![ES3](https://images.ctfassets.net/alneenqid6w5/1PVutb4VQX4Tbt8VuRzxNA/348cf9167307462767ae79b1f5887105/ES3.gif)
 
 ## Plantilla
 
@@ -92,7 +92,7 @@ Después de rellenar los datos de la plantilla, siga este procedimiento para imp
 5. Haga clic en **Select** para seleccionar la plantilla de importación.
 6. Haga clic en **Importar**.
 
-![ES4](//images.ctfassets.net/alneenqid6w5/3yZtK0w9QXrf3kBV0UfWq0/e65a0dad3840a0adee367c503b781233/ES4.gif)
+![ES4](https://images.ctfassets.net/alneenqid6w5/3yZtK0w9QXrf3kBV0UfWq0/e65a0dad3840a0adee367c503b781233/ES4.gif)
 
 ## API
 
diff --git a/docs/tracks/es/adding-products.md b/docs/tracks/es/adding-products.md
index 046213004..6f3399871 100644
--- a/docs/tracks/es/adding-products.md
+++ b/docs/tracks/es/adding-products.md
@@ -30,7 +30,7 @@ En el Admin VTEX, realice los siguientes pasos:
 4. Rellene los campos del formulario de producto. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre los [campos de registro de producto](https://help.vtex.com/es/tutorial/campos-de-registro-de-producto--4dYXWIK3zyS8IceKkQseke).
 5. Haga clic en `Guardar` o `Guardar y registrar nuevo SKU`, si quiere agregar SKUs asociados a este producto.
 
-![Catalogo - Cadastrar produto ES.gif?h=250](//images.ctfassets.net/alneenqid6w5/IaFCYaexWNcL8nMvkI1Ya/1704449927dee788756723f216072b92/Catalogo_-_Cadastrar_produto_ES.gif_h_250)
+![Catalogo - Cadastrar produto ES.gif?h=250](https://images.ctfassets.net/alneenqid6w5/IaFCYaexWNcL8nMvkI1Ya/1704449927dee788756723f216072b92/Catalogo_-_Cadastrar_produto_ES.gif_h_250)
 
 ## Plantilla
 
diff --git a/docs/tracks/es/adding-skus.md b/docs/tracks/es/adding-skus.md
index 2449b5b5e..1659cdd55 100644
--- a/docs/tracks/es/adding-skus.md
+++ b/docs/tracks/es/adding-skus.md
@@ -25,7 +25,7 @@ Existen dos flujos de registro de SKU por el admin: luego de registrar un produc
 ### Registrar SKU luego del registro de un producto
 
 1. En la pantalla de registro de Producto, después de rellenar los campos, haga clic en `Guardar y Crear SKU`.
-  ![1foto.es](//images.ctfassets.net/alneenqid6w5/5lYrKBh17OA6yUU5HHdZO7/cd48c8350405235a7526b16c0248083f/1foto.es.png)
+  ![1foto.es](https://images.ctfassets.net/alneenqid6w5/5lYrKBh17OA6yUU5HHdZO7/cd48c8350405235a7526b16c0248083f/1foto.es.png)
 2. Usted será redirigido a la pantalla de registro de SKU. Rellene los campos del formulario de SKU. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre [cómo rellenar los campos de registro de SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY).
 3. Haga clic en `Guardar`.
 
@@ -43,7 +43,7 @@ Existen dos flujos de registro de SKU por el admin: luego de registrar un produc
 Después del registro de un SKU, es necesario agregar una imagen para que se active. Para esto, realice el siguiente procedimiento:
 
 1. En la página de registro de SKU, haga clic en la pestaña **Imágenes**.
-  ![6foto.es](//images.ctfassets.net/alneenqid6w5/5AgORlEQzTGpvxSKSuGUl7/f363abad82ee975e0a0dab1448f47348/6foto.es.png)
+  ![6foto.es](https://images.ctfassets.net/alneenqid6w5/5AgORlEQzTGpvxSKSuGUl7/f363abad82ee975e0a0dab1448f47348/6foto.es.png)
 2. Haga clic en `Insertar` y elija la imagen deseada.
 3. Rellene los campos **Texto** (tag alt de la imagen) y **Label** (la “etiqueta” utilizada para facilitar la organización del template de las páginas de su sitio web, a través de la referencia del valor rellenado en esta. Ej.: Frontal, lateral, superior, etc.)
 4. Haga clic en `Enviar`.
@@ -53,7 +53,7 @@ Después del registro de un SKU, es necesario agregar una imagen para que se act
 Después de registrar las imágenes, debe registrar las especificaciones del SKU. El registro de las especificaciones se detallará en el próximo paso de esta guía. 
 
 1. Haga clic en la pestaña **Especificaciones**.
-  ![7foto.es](//images.ctfassets.net/alneenqid6w5/3OdYoTaGUSznx0PsVyrKaX/b89adf4357e466db3d9a9efcb3109b4d/7foto.es.png)
+  ![7foto.es](https://images.ctfassets.net/alneenqid6w5/3OdYoTaGUSznx0PsVyrKaX/b89adf4357e466db3d9a9efcb3109b4d/7foto.es.png)
 2. Rellene los campos solicitados. Los valores de las especificaciones se configuran en el nivel de la Categoría.
 3. Haga clic en `Guardar`.
 
diff --git a/docs/tracks/es/adding-vendors.md b/docs/tracks/es/adding-vendors.md
index 12837bf9f..2a1139735 100644
--- a/docs/tracks/es/adding-vendors.md
+++ b/docs/tracks/es/adding-vendors.md
@@ -18,7 +18,7 @@ Si usted ha configurado su tienda utilizando el flujo de __Easy Setup__, tal vez
 
 Al entrar en el VTable (https://{{AccountName}}.myvtex.com/admin/vtable) usted verá dos aplicaciones, __Admin de las tiendas__ y __Admin de los vendedores__:
 
-![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Haga clic en __Admin de los vendedores__ para abrir la tabla donde incluiremos un nuevo vendedor.
 
@@ -26,7 +26,7 @@ En el caso de que ya haya registrado un vendedor a través del __Easy Setup__, s
 
 > __IMPORTANTE__: el e-mail de cada vendedor __NO__ puede ser el mismo utilizado en la plataforma VTEX, porque su e-mail de administrador tiene permisos que un vendedor no debería tener, por lo que es necesario utilizar algún otro e-mail sin privilegios en la plataforma.
 
-![inStore adicionando vendedor](//images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
+![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
 Si ha saltado el paso de creación de vendedor en el __Easy Setup__ y no tiene ningún vendedor creado, usted necesitará recoger el ID de __Tienda__ en el __Admin de las Tiendas__ en el VTable.
 
diff --git a/docs/tracks/es/adding-warehouses.md b/docs/tracks/es/adding-warehouses.md
index 6556b8b70..0868b53ca 100644
--- a/docs/tracks/es/adding-warehouses.md
+++ b/docs/tracks/es/adding-warehouses.md
@@ -29,7 +29,7 @@ Siga el siguiente procedimiento para registrar un inventario en su tienda:
 4. Rellene los campos del formulario de inventario. Para entender mejor el significado de cada campo, consulte abajo la sección [Campos de Registro](#campos-de-registro).
 5. Haga clic en el botón **Guardar**
 
-![ES Cadastrar Estoque GIF](//images.ctfassets.net/alneenqid6w5/29hDNueQOJgRlg6rLIk8T5/ee2fba7fcb9da60690df299825e0cdef/ES_Cadastrar_Estoque_GIF.gif)
+![ES Cadastrar Estoque GIF](https://images.ctfassets.net/alneenqid6w5/29hDNueQOJgRlg6rLIk8T5/ee2fba7fcb9da60690df299825e0cdef/ES_Cadastrar_Estoque_GIF.gif)
 
 ### Campos de registro
 
diff --git a/docs/tracks/es/amazon.md b/docs/tracks/es/amazon.md
index 547cebd49..d62172a7d 100644
--- a/docs/tracks/es/amazon.md
+++ b/docs/tracks/es/amazon.md
@@ -16,7 +16,7 @@ trackSlugES: integracion-de-amazon
 
 Amazon es una plataforma de ecommerce y se le considera una de las cinco mayores empresas de tecnología del mundo. Actualmente, Amazon vende una gran variedad de productos, como juguetes, productos electrónicos, ropa y accesorios, entre otros. Además, la empresa de comercio minorista online ofrece servicios de streaming, almacenamiento en la nube y asistentes virtuales.
 
-![amazon logo](//images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
+![amazon logo](https://images.ctfassets.net/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
 
 La configuración con Amazon tiene como objetivo enviar el catálogo de productos de su tienda VTEX a este marketplace, permitiéndole anunciar sus productos y aumentar sus ventas. 
 
diff --git a/docs/tracks/es/associating-a-template-with-a-layout.md b/docs/tracks/es/associating-a-template-with-a-layout.md
index bb6e50d01..111f6555d 100644
--- a/docs/tracks/es/associating-a-template-with-a-layout.md
+++ b/docs/tracks/es/associating-a-template-with-a-layout.md
@@ -29,4 +29,4 @@ Esta asociación se realiza en la configuración de las propiedades del layout.
 5. Haga clic en el menú desplegable __Template__. Ahí se listarán los templates configurados en HTML Templates.
 6. Seleccione el template que desea asociar a este layout.
 7. Digite "yes" para confirmar el cambio (este paso es necesario porque se trata de un cambio crítico para el sitio web, ya que el front-end de la página será reemplazado). 
-![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tracks/es/autocomplete-search.md b/docs/tracks/es/autocomplete-search.md
index a2c053bae..d3cd7aaa4 100644
--- a/docs/tracks/es/autocomplete-search.md
+++ b/docs/tracks/es/autocomplete-search.md
@@ -53,22 +53,22 @@ Otra ventaja para el administrador de la tienda es el aumento de conversión, qu
 
 En esta sección se muestran los términos más buscados por otros clientes dentro del sitio web.
 
-![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+![PT - Autocomplete termos mais pesquisados](https://images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
 
 ## Últimas búsquedas realizadas
 
 En esta sección se muestran las últimas búsquedas realizadas por el cliente. Así, es posible comenzar la interacción con la búsqueda instantáneamente.
 
-![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+![PT - Autocomplete historico](https://images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
 
 ## Sugerencia de búsquedas
 
 En esta sección se muestran los términos buscados por otros usuarios que se relacionan con la búsqueda realizada en ese momento. Además de términos, también se sugieren categorías relacionadas con la búsqueda.
 
-![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+![PT - Autocomplete sugestao termos](https://images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
 
 ## Sugerencia de productos
 
 En esta sección se muestran los productos que coinciden con la búsqueda realizada en ese momento. Así, al mostrar productos relacionados con su búsqueda durante la escritura, se reducen las interrupciones y se le permite al usuario realizar una compra más dinámica.
 
-![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
+![PT - Autocomplete sugestao de produtos](https://images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tracks/es/b2b-form.md b/docs/tracks/es/b2b-form.md
index 32172e74d..409d03121 100644
--- a/docs/tracks/es/b2b-form.md
+++ b/docs/tracks/es/b2b-form.md
@@ -46,12 +46,12 @@ Ejemplos de cómo queda en el inStore el formulario con persona jurídica:
 
 __Formulario B2B__ - opcional y cerrado:
 
-![b2b-opcional-fechado](//images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
+![b2b-opcional-fechado](https://images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
 
 __Formulario B2B__ - opcional y abierto:
 
-![b2b-opcional-aberto](//images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
+![b2b-opcional-aberto](https://images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
 
 __Formulario B2B__ - obligatorio (ya vienen todos los campos abiertos):
 
-![b2b-obrigatorio](//images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
+![b2b-obrigatorio](https://images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
diff --git a/docs/tracks/es/backend-integrations.md b/docs/tracks/es/backend-integrations.md
index f4320f53f..112c637c2 100644
--- a/docs/tracks/es/backend-integrations.md
+++ b/docs/tracks/es/backend-integrations.md
@@ -102,7 +102,7 @@ Los pasos para la configuración se deben seguir en el orden indicado a continua
 
 Después de configurar la tienda y completar la integración con el middleware, el flujo general de información seguirá el formato que se muestra en la imagen:
 
-![ERP-integrations-es](//images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/fc870c6a2aedf5a3bebd4d0c33058794/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_3.jpg)
+![ERP-integrations-es](https://images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/fc870c6a2aedf5a3bebd4d0c33058794/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_3.jpg)
 
 Cada una de las solicitudes o procesos representados por las flechas en el diagrama anterior es accionado por un tipo diferente de evento en la operación cotidiana de una tienda online. Para más información sobre este flujo, consulta[ Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide#ongoing-middleware-flow).
 
@@ -168,7 +168,7 @@ Hay tres tipos de especificaciones que se deben crear en el siguiente orden:
 
 El diagrama a continuación ilustra el procedimiento.
 
-![catalog_specification_diagram_ES](//images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/8614400d84e83d97dcc00ae1029161e4/catalog_specification_diagram_ES.png)
+![catalog_specification_diagram_ES](https://images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/8614400d84e83d97dcc00ae1029161e4/catalog_specification_diagram_ES.png)
 
 Las especificaciones siguen la jerarquía de Catálogo. Cuando se crea un grupo en un departamento o categoría, el mismo se heredará en los niveles inferiores.
 Una vez creados los grupos, campos y valores, hay que asociar las especificaciones a productos y SKU. Estos procedimientos se describen en la próxima sección: [Importar productos](#importar-productos).
diff --git a/docs/tracks/es/banners-en.md b/docs/tracks/es/banners-en.md
index c8660f801..4878efd00 100644
--- a/docs/tracks/es/banners-en.md
+++ b/docs/tracks/es/banners-en.md
@@ -33,7 +33,7 @@ En VTEX Admin, la página **Storefront** > **Banners** muestra la lista completa
 * [Editar banner](#editar-banner)
 * [Eliminar banner](#eliminar-banner) 
 
-![banners-intro-es](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
+![banners-intro-es](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
 
 La página contiene la siguiente información:
 
diff --git a/docs/tracks/es/barcode-reading.md b/docs/tracks/es/barcode-reading.md
index f44c959bb..b82237be4 100644
--- a/docs/tracks/es/barcode-reading.md
+++ b/docs/tracks/es/barcode-reading.md
@@ -18,6 +18,6 @@ Después de identificar al cliente, el vendedor es llevado directamente al carri
 
 Si el vendedor está usando un tablet o smartphone, verá un botón de código de barras <i class="fas fa-barcode"></i> en la barra superior de la aplicación.
 
-![31. VTEX Sales App - Product Overview - 6 - EN](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/faddd95042b7890f597f30c00d933222/barcode.png)
+![31. VTEX Sales App - Product Overview - 6 - EN](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/faddd95042b7890f597f30c00d933222/barcode.png)
 
 Al hacer clic en él, el vendedor puede usar la cámara para emitir leer un producto y, con eso, pasar automáticamente a la pantalla de detalles de ese producto.
diff --git a/docs/tracks/es/basic-vtex-io-developer-setup.md b/docs/tracks/es/basic-vtex-io-developer-setup.md
index 722a923f8..d14e2ff88 100644
--- a/docs/tracks/es/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/es/basic-vtex-io-developer-setup.md
@@ -38,7 +38,7 @@ Esto abrirá una ventana del navegador que solicitará sus credenciales.
 
 Cuando esté conectado, usted puede utilizar el comando `vtex whoami` para descubrir qué *cuenta* y *workspace* está utilizando actualmente.
 
-![Command Line](//images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
+![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
 <div class="alert alert-info">
 Sugerencia: Usted puede configurar su terminal para mostrar automáticamente su cuenta y workspace. La manera más fácil de hacer esto es usar nuestros <a href="https://github.com/vtex/dotfiles">dotfiles</a>, que configuran automáticamente la <a href="https://fishshell.com/">Fish Shell</a> y añaden una <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">función de prompt</a> para usted.
@@ -54,7 +54,7 @@ De forma predeterminada, cuando inicie sesión en una tienda, usted está en el
 $ vtex ls
 ```
 
-![Command Line vtex ls](//images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
+![Command Line vtex ls](https://images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
 
 ## Creando su propio workspace
 
@@ -72,6 +72,6 @@ Sugerencia: Usted puede cambiar a (<em>y restablecer</em>) un workspace master c
 
 Los workspaces pueden ser nombrados arbitrariamente, pero generalmente es conveniente asignar su propio nombre cuando usted desea desarrollar en su ambiente.
 
-![command line workspace](//images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
+![command line workspace](https://images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
 
 Ahora usted tiene su propio workspace. Usted puede ejecutar `vtex list` nuevamente y observar que las apps instaladas reflejan aquellas en `master`. Ahora, vamos a "linkar" una versión local del tema de la tienda para que usted pueda comenzar a editarla.
diff --git a/docs/tracks/es/best-practices-for-testing-instore.md b/docs/tracks/es/best-practices-for-testing-instore.md
index 8b202c678..3844b7061 100644
--- a/docs/tracks/es/best-practices-for-testing-instore.md
+++ b/docs/tracks/es/best-practices-for-testing-instore.md
@@ -16,7 +16,7 @@ trackSlugES: instore-usando-el-app
 
 Tras completar la configuración básica y la instalación de la aplicación de VTEX Sales App en un dispositivo, es importante realizar pruebas antes de empezar a utilizar VTEX Sales App en tus tiendas físicas. En este artículo, conocerás las mejores prácticas para probar el uso de VTEX Sales App.
 
-![testes-instore-es](//images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/9e729d91cf79c227665adeeb099b79ac/Group_6.png)
+![testes-instore-es](https://images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/9e729d91cf79c227665adeeb099b79ac/Group_6.png)
 
 ## Pruebas técnicas
 
diff --git a/docs/tracks/es/calculating-order-shipping-time.md b/docs/tracks/es/calculating-order-shipping-time.md
index afa784f42..551900e8d 100644
--- a/docs/tracks/es/calculating-order-shipping-time.md
+++ b/docs/tracks/es/calculating-order-shipping-time.md
@@ -23,17 +23,17 @@ El plazo de entrega de un pedido tiene en cuenta los __tiempos de costo__ defini
 
 Para cada una de las tres etapas de la ruta logística, puede establecer un tiempo de costo - y el tiempo de entrega que verá su cliente en el checkout es la suma de estos tiempos de costo (+ feriados, y considerando también los horarios de corte).
 
-![deliveryCostTimes](//images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
+![deliveryCostTimes](https://images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
 
 Los tiempos de costo del __stock__ y del __muelle__ se definen en las pantallas de configuración de cada una de estas etapas, en el módulo Inventario y Envío > Paneles.
 
-![calculoPrazoEntrega1](//images.contentful.com/alneenqid6w5/4QgQlroxxCK4iu6YoU2uIQ/a2df01bdbe2449e924a6380b5a39a19b/calculoPrazoEntrega1.png) 
+![calculoPrazoEntrega1](https://images.contentful.com/alneenqid6w5/4QgQlroxxCK4iu6YoU2uIQ/a2df01bdbe2449e924a6380b5a39a19b/calculoPrazoEntrega1.png) 
 
-![calculoPrazoEntrega2](//images.contentful.com/alneenqid6w5/6xAiBHXxwA2cMIaaK4AKm2/bfff8d81b7363121cc84de1149cfd587/calculoPrazoEntrega2.png)
+![calculoPrazoEntrega2](https://images.contentful.com/alneenqid6w5/6xAiBHXxwA2cMIaaK4AKm2/bfff8d81b7363121cc84de1149cfd587/calculoPrazoEntrega2.png)
 
 El tiempo de costo de la __transportadora__ se define en la tabla de flete, que se envía a VTEX a través de la pantalla de configuración de la transportadora, también en el módulo Inventario y Envío.
 
-![calculoPrazoEntrega3](//images.contentful.com/alneenqid6w5/2bL9Gw0AeswGAeKSqYCYw4/57c492eb08239d61e463839a768101ad/calculoPrazoEntrega3.png)
+![calculoPrazoEntrega3](https://images.contentful.com/alneenqid6w5/2bL9Gw0AeswGAeKSqYCYw4/57c492eb08239d61e463839a768101ad/calculoPrazoEntrega3.png)
 
 ## Ejemplos
 
diff --git a/docs/tracks/es/cart-transfer-and-capture.md b/docs/tracks/es/cart-transfer-and-capture.md
index 4b51be5e0..996390b5f 100644
--- a/docs/tracks/es/cart-transfer-and-capture.md
+++ b/docs/tracks/es/cart-transfer-and-capture.md
@@ -20,11 +20,11 @@ VTEX Sales App permite [habilitar una funcionalidad de transferencia de carrito]
 
 Para compartir un carrito, el vendedor puede generar un código numérico o un código QR. Para hacer esto, mientras está en la pantalla del carrito, haga clic en el botón __Transferir__. Vea un ejemplo en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
 
 Al hacer clic en este botón, la aplicación muestra un código QR y un código numérico de cuatro dígitos.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Otro vendedor vinculado a la misma tienda puede capturar ese carrito y continuar la venta desde su dispositivo.
 
@@ -34,7 +34,7 @@ Para capturar un carrito, ingrese al menú principal de VTEX Sales App y haga cl
 
 Alternativamente, en la pantalla de inicio de la aplicación, el vendedor simplemente puede arrastrar la pantalla hacia la derecha. Cuando arrastre la pantalla hacia la derecha, verá la pantalla para __Capturar Carrito__, como se muestra en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
 
 En esta pantalla, el vendedor puede capturar un carrito utilizando uno de estos tres métodos:
 - Código del carrito
diff --git a/docs/tracks/es/cart-transfer.md b/docs/tracks/es/cart-transfer.md
index 3d8363054..16e19d391 100644
--- a/docs/tracks/es/cart-transfer.md
+++ b/docs/tracks/es/cart-transfer.md
@@ -31,14 +31,14 @@ window.INSTORE_CONFIG = {
 
 Al realizar este cambio, debe darse cuenta de que aparecerán dos bolitas al final de la página de identificación del inStore:
 
-![01 inStore slider transferencia](//images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
+![01 inStore slider transferencia](https://images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
 
 Al arrastrar la pantalla hacia el lateral verá la pantalla para __ "Capturar carrito" __:
 
-![02 inStore capturar carrinho](//images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
+![02 inStore capturar carrinho](https://images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
 
 En ella es posible capturar un carrito por el código del carrito, QR code o incluso por vendedor.
 
 Para generar un código o código QR de un carro usted debe usar la opción __ "Transferir" __ presente en el carrito del inStore:
 
-![03 inStore transferir](//images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
+![03 inStore transferir](https://images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
diff --git a/docs/tracks/es/catalog-architecture.md b/docs/tracks/es/catalog-architecture.md
index 544f721a2..f231aabbe 100644
--- a/docs/tracks/es/catalog-architecture.md
+++ b/docs/tracks/es/catalog-architecture.md
@@ -35,4 +35,4 @@ Estas especificaciones son, por ejemplo, la composición de un producto, o el ta
 
 A continuación, vea un esquema de la arquitectura del Catálogo en VTEX:
 
-![arquitetura-catalogo-ES](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
+![arquitetura-catalogo-ES](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
diff --git a/docs/tracks/es/catalog-concept-definition.md b/docs/tracks/es/catalog-concept-definition.md
index 0523d5c40..8976c160d 100644
--- a/docs/tracks/es/catalog-concept-definition.md
+++ b/docs/tracks/es/catalog-concept-definition.md
@@ -18,7 +18,7 @@ El menú **Catálogo** contiene las funcionalidades relativas al surtido de prod
 
 El menú **Catálogo** de tu Admin actualizado reúne las páginas donde gestionas tu catálogo, los precios y el stock de tu *ecommerce*.
 
-![visao-geral-produto-ES](//images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/ad397a99b3db19ea9187ef5667577a26/image.png)
+![visao-geral-produto-ES](https://images.ctfassets.net/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/ad397a99b3db19ea9187ef5667577a26/image.png)
 
 El **Catálogo** permite la configuración de funcionalidades relacionadas con el surtido de productos del *ecommerce*, como sus categorías, marcas y colecciones, por ejemplo. Para vender tus productos, debes registrarlos en esta sección.
 
diff --git a/docs/tracks/es/changing-the-instore-language.md b/docs/tracks/es/changing-the-instore-language.md
index 8008f09d1..6d84012b9 100644
--- a/docs/tracks/es/changing-the-instore-language.md
+++ b/docs/tracks/es/changing-the-instore-language.md
@@ -80,4 +80,4 @@ Después de hacer el cambio de código, guarde el archivo `checkout-instore-cust
 
 Luego, en la aplicación inStore, para ver los cambios reflejados, ingrese al menú y haga clic en el botón __Restaurar datos__, como se muestra en la imagen a continuación.
 
-![22. Change the inStore language - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6kyOLVTDlyawsehMQwORid/589ff63de4574dc8cf1d9cc3ed84024a/22._Change_the_inStore_language_-_1_-_ES.png_h_250)
+![22. Change the inStore language - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6kyOLVTDlyawsehMQwORid/589ff63de4574dc8cf1d9cc3ed84024a/22._Change_the_inStore_language_-_1_-_ES.png_h_250)
diff --git a/docs/tracks/es/cms-folder-structure.md b/docs/tracks/es/cms-folder-structure.md
index aaef10e49..d9b799e6a 100644
--- a/docs/tracks/es/cms-folder-structure.md
+++ b/docs/tracks/es/cms-folder-structure.md
@@ -34,7 +34,7 @@ Toda tienda debe tener, sin excepción, las siguientes carpetas en el CMS para a
 
 Vea abajo estas carpetas básicas en el CMS:
 
-![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas carpetas vienen de forma predeterminada en el ambiente de todas las tiendas VTEX.
 
diff --git a/docs/tracks/es/cms-vtex-io.md b/docs/tracks/es/cms-vtex-io.md
index 32c7e0921..4a1f9aae7 100644
--- a/docs/tracks/es/cms-vtex-io.md
+++ b/docs/tracks/es/cms-vtex-io.md
@@ -28,19 +28,19 @@ Configura el [binding de la tienda](https://help.vtex.com/en/tutorial/what-is-cm
 
 Binding es el proceso para vincular tu sitio web a una tienda. Para más detalles, consulta el artículo [Vincular una tienda a una estructura de carpetas en CMS (binding)](https://help.vtex.com/en/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![CMS - Layout ES](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
+![CMS - Layout ES](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
 
 ## Páginas
 En **[Páginas](https://help.vtex.com/es/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc)**, crea una nueva URL y enlázala a una plantilla ya definida en el [código del tema de la tienda](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-4-configuringtemplates).
 
-![CMS - Páginas](//images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/b6c227e2c39991747ae1c60b826269e7/cms-pages-es.png)
+![CMS - Páginas](https://images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/b6c227e2c39991747ae1c60b826269e7/cms-pages-es.png)
 
 Además, esta sección contiene la página **Redirecciones**, que redirige a los usuarios y a los motores de búsqueda de una URL a otra más relevante o similar. 
 
 ## Site Editor
 El **[Site Editor](https://help.vtex.com/es/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1)** es una interfaz gráfica para gestionar el contenido de tu storefront. Te permite crear, editar, publicar y programar cambios en los componentes y el comportamiento de tu storefront.
 
-![CMS - Site Editor ES](//images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/e44ac6d9f16a0523d476ccf15cf55fec/cms-siteeditor-es.png)
+![CMS - Site Editor ES](https://images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/e44ac6d9f16a0523d476ccf15cf55fec/cms-siteeditor-es.png)
 
 ## Estilos
 
@@ -50,12 +50,12 @@ La sección **[Estilos](https://help.vtex.com/pt/tutorial/styles-overview--v0Db5
   Este recurso solo funciona en production workspaces <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-creating-a-production-workspace">espacios de trabajo de producción</a>.
 </div>
 
-![CMS - Estilos](//images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/b6562343e0c7cfd98210964a5dfd30e8/cms-styles-es.png)
+![CMS - Estilos](https://images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/b6562343e0c7cfd98210964a5dfd30e8/cms-styles-es.png)
 
 ## Tienda
 La sección **[Tienda](https://help.vtex.com/es/tutorial/cms-loja-visao-geral--3Eat287G6wUi6Mly5rW5Fs)** es donde se configuran los ajustes de SEO, de las flags de optimización de rendimiento y se habilitan las notificaciones push de PWA en tu tienda.
 
-![CMS - Tienda](//images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/02496bd9a4cdcb3ebbf6baeb51a50044/cms-store-es.png)
+![CMS - Tienda](https://images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/02496bd9a4cdcb3ebbf6baeb51a50044/cms-store-es.png)
 
 ## Referencias
 - [Layout - Sites and channels](https://help.vtex.com/es/tutorial/what-is-cms-layout--EmO8u2WBj2W4MUQCS8262?&utm_source=autocomplete#sites-and-channels)
diff --git a/docs/tracks/es/configure-customer-identification.md b/docs/tracks/es/configure-customer-identification.md
index a9054e679..10b2d85c0 100644
--- a/docs/tracks/es/configure-customer-identification.md
+++ b/docs/tracks/es/configure-customer-identification.md
@@ -26,11 +26,11 @@ Para elegir qué métodos de identificación desea habilitar, acceda al panel ad
 
 En el cuadro __Inicio de sesión del cliente__, usted debe seleccionar los métodos de identificación que desea habilitar.
 
-![21. Configure client identification - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/4efcT1xJ2naRxi5pUykS1M/4f9e6cd6f793a6126e956cbd023863e4/21._Configure_client_identification_-_1_-_ES.png_h_250)
+![21. Configure client identification - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/4efcT1xJ2naRxi5pUykS1M/4f9e6cd6f793a6126e956cbd023863e4/21._Configure_client_identification_-_1_-_ES.png_h_250)
 
 También puede cambiar el orden de estos métodos. Para hacer esto, arrástrelos como se muestra en la imagen a continuación. El orden de los métodos definidos en esta pantalla determina el orden en que aparecerán para el vendedor en la aplicación. Por lo tanto, el primer método será el predeterminado.
 
-![21. Configure client identification - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/1oZXmjWc7ii8yirafQiiEQ/50cc598d8e315665968919c04bdd1164/21._Configure_client_identification_-_2_-_ES.png_h_250)
+![21. Configure client identification - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/1oZXmjWc7ii8yirafQiiEQ/50cc598d8e315665968919c04bdd1164/21._Configure_client_identification_-_2_-_ES.png_h_250)
 
 ## Habilitar usuario anónimo
 
@@ -38,7 +38,7 @@ Es posible utilizar inStore para atender a los clientes de forma anónima, es de
 
 Para esto, aún en la pantalla de Identificación del Cliente, es necesario habilitar la flag __Usuario anónimo__.
 
-![21. Configure client identification - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/5rkF0v7jr91rGCQsbIgAGV/73dd9f1c038c42bef465e4507152f05f/21._Configure_client_identification_-_3_-_ES.png_h_250)
+![21. Configure client identification - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/5rkF0v7jr91rGCQsbIgAGV/73dd9f1c038c42bef465e4507152f05f/21._Configure_client_identification_-_3_-_ES.png_h_250)
 
 ## Registro de entidad legal para ventas B2B
 
@@ -50,10 +50,10 @@ A continuación, puede elegir si estos campos deben completarse necesariamente o
 
 En el siguiente ejemplo, el registro de la entidad legal se activa y configura como opcional.
 
-![21. Configure client identification - 4 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6AidakHNTZAZxB9ygG14aF/310070d0cf327cd90c1915dbb05b7e4f/21._Configure_client_identification_-_4_-_ES.png_h_250)
+![21. Configure client identification - 4 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6AidakHNTZAZxB9ygG14aF/310070d0cf327cd90c1915dbb05b7e4f/21._Configure_client_identification_-_4_-_ES.png_h_250)
 
 En este caso, la aplicación le mostrará al vendedor un formulario como el siguiente:
 
-![21. Configure client identification - 5.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/aa10e2401c309494320033a556b323f4/21._Configure_client_identification_-_5.png_h_250_h_250)
+![21. Configure client identification - 5.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/1wjA3eb0wgoeVsnq3Bgl17/aa10e2401c309494320033a556b323f4/21._Configure_client_identification_-_5.png_h_250_h_250)
 
 Tenga en cuenta que se muestra una flag que le permite al vendedor decidir si mostrar estos campos adicionales o no. Esto se debe a que, en la configuración, marcamos los campos de registro de la entidad legal como opcionales. Si están marcados como obligatorios, esta flag no se mostrará en la aplicación.
diff --git a/docs/tracks/es/configure-integration-of-pick-up-points.md b/docs/tracks/es/configure-integration-of-pick-up-points.md
index 0db7955b5..66576db8d 100644
--- a/docs/tracks/es/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/es/configure-integration-of-pick-up-points.md
@@ -20,7 +20,7 @@ En este artículo, explicaremos cómo crear puntos de recogida en Mercado Libre,
 
 Cuando los pedidos que utilizan la opción de recogida en la tienda llegan a VTEX, se asignan a la cuenta franquicia que posee el punto de recogida elegido por el cliente y se modifica el stock del punto de recogida.
 
-![configurar pontosderetirada01 ES](//images.contentful.com/alneenqid6w5/39DuF7GI3SC432EtzjWlwn/6361d5707ff1139a6dfed63d1c48380c/configurar_pontosderetirada01_ES.JPG)
+![configurar pontosderetirada01 ES](https://images.contentful.com/alneenqid6w5/39DuF7GI3SC432EtzjWlwn/6361d5707ff1139a6dfed63d1c48380c/configurar_pontosderetirada01_ES.JPG)
 
 <div class="alert alert-info">
 Antes de crear los puntos de recogida, debe solicitar a Mercado Livre la activación de la modalidad “Recogida en la tienda”. Para eso, contacte a su asesor comercial de Mercado Libre o abra un ticket para el equipo de <a href="https://developers.mercadolivre.com.br/en_us/support/">Soporte.</a>
@@ -63,7 +63,7 @@ Para ativar os pontos de retirada nas contas franquias:
 6. En el campo **Activar integración de los puntos de recogida de las cuentas franquicia**, haga clic en la opción `Sí`.
 7. Haga clic en `Guardar configuración`.
 
-![Home (3)](//images.contentful.com/alneenqid6w5/57X4xTb1GhL1nJbUyHMZJ7/a46c76f83a00f9dda9569b364beddd04/Home__3_.gif)
+![Home (3)](https://images.contentful.com/alneenqid6w5/57X4xTb1GhL1nJbUyHMZJ7/a46c76f83a00f9dda9569b364beddd04/Home__3_.gif)
 
 ## Confirmar el envío del punto de recogida  
 
@@ -75,13 +75,13 @@ Para comprobar si el punto de recogida se envió a Mercado Libre:
 
 En la lista de puntos de recogida enviados, podrá ver cuáles se enviaron con éxito y cuáles tienen un error de configuración.
 
-![Home (4)](//images.contentful.com/alneenqid6w5/4qygOb8Eo7uCPJc3oVuFfW/2277aac1274797ac269d1259b2035f23/Home__4_.gif)
+![Home (4)](https://images.contentful.com/alneenqid6w5/4qygOb8Eo7uCPJc3oVuFfW/2277aac1274797ac269d1259b2035f23/Home__4_.gif)
 
 En Mercado Libre no hay una pantalla para visualizar si un determinado punto de recogida ha sido vinculado. Recomendamos que elija un anuncio en Mercado Libre que esté asociado al punto de recogida y que realice una compra de prueba, eligiendo la opción «Punto de recogida» en el checkout. A continuación, compruebe si el punto de recogida realmente está disponible en la lista que Mercado Libre muestra en el checkout.
 
 ## Confirmar la asociación del punto de recogida y el anuncio  
 
-![configurar pontosderetirada02 ES](//images.contentful.com/alneenqid6w5/4X8ectjkvXMtxZygafunJ1/ee4121a438cbbecc712f2e2ca9849f69/configurar_pontosderetirada02_ES.JPG)
+![configurar pontosderetirada02 ES](https://images.contentful.com/alneenqid6w5/4X8ectjkvXMtxZygafunJ1/ee4121a438cbbecc712f2e2ca9849f69/configurar_pontosderetirada02_ES.JPG)
 
 Para confirmar si el punto de recogida se asoció correctamente con el anuncio de Mercado Libre, debe verificar qué puntos de recogida están sincronizados con cada SKU y sus respectivos stocks. Realice los siguientes pasos:
 
@@ -93,4 +93,4 @@ Para confirmar si el punto de recogida se asoció correctamente con el anuncio d
 
 Si no se produjo ningún error, el SKU encontrado se sincronizará con los puntos de recogida, y sus respectivos stocks se mostrarán en la lista.
 
-![Home (5)](//images.contentful.com/alneenqid6w5/4k1x9ZQWKFwuxm8sbCod25/de93e9b7e9645ee73b55f013b828a529/Home__5_.gif)
+![Home (5)](https://images.contentful.com/alneenqid6w5/4k1x9ZQWKFwuxm8sbCod25/de93e9b7e9645ee73b55f013b828a529/Home__5_.gif)
diff --git a/docs/tracks/es/configuring-a-payment-condition.md b/docs/tracks/es/configuring-a-payment-condition.md
index e9e07c9fc..54284cf9b 100644
--- a/docs/tracks/es/configuring-a-payment-condition.md
+++ b/docs/tracks/es/configuring-a-payment-condition.md
@@ -98,7 +98,7 @@ Si decide configurar un medio de pago que acepte cuotas con intereses, este camp
 La opción Cuota Automática le permite configurar los detalles de las cuotas directamente en el proveedor de pago (fuera del entorno VTEX).
 Para habilitar esta opción, seleccione "Sí" en el campo **Utilizar pago en cuotas externo** durante el paso de [configuración de proveedor](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444).
 
-![cuotaautomatica](//images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/5e3f569ad3db6cb29111199467b34892/parcelamentoautomaticoes.JPG)
+![cuotaautomatica](https://images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/5e3f569ad3db6cb29111199467b34892/parcelamentoautomaticoes.JPG)
 
 Después de habilitar la cuota automática en el proveedor, siga estos pasos:
 
diff --git a/docs/tracks/es/configuring-banners.md b/docs/tracks/es/configuring-banners.md
index a10af26c8..1acc1f111 100644
--- a/docs/tracks/es/configuring-banners.md
+++ b/docs/tracks/es/configuring-banners.md
@@ -28,7 +28,7 @@ Después de configurar el banner, debes agregarlo a una página de tu tienda. Pa
 <p> Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configuración Multidioma (Beta)</a>para saber más.</p>
 </div>
 
-![banner-form-es](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
+![banner-form-es](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
 
 ## Campos de registro del banner
 
@@ -59,7 +59,7 @@ Para registrar el banner, debes rellenar los siguientes campos:
 
 Haz clic en <i class="fa-solid fa-link"></i> `Autocompletar desde URL` para agregar la URL de la página de búsqueda donde se aplicarán las reglas de activación.
 
-![banner-url-es](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
+![banner-url-es](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
 
 Haz clic en <i class="fas fa-plus"></i> `Agregar condición` para crear una regla. Pueden ser de los siguientes tipos:
 
diff --git a/docs/tracks/es/configuring-cash-payments-through-instore.md b/docs/tracks/es/configuring-cash-payments-through-instore.md
index 7e2666145..64c9d15b6 100644
--- a/docs/tracks/es/configuring-cash-payments-through-instore.md
+++ b/docs/tracks/es/configuring-cash-payments-through-instore.md
@@ -34,7 +34,7 @@ Ahora vamos a crear la condición de pago.
 1. Aún en la página de **Configuración **del módulo de **Pagos**, haz clic en la pestaña **Planes de Pago**.
 2. Haz clic en el botón verde con el ícono `+` para añadir una nueva condición de pago, como se muestra a continuación.
 
-![es-add-payment-condition](//images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/7aa38306086b2bb26b9b789b63baeeb0/es-add-payment-condition.png)
+![es-add-payment-condition](https://images.ctfassets.net/alneenqid6w5/27933kBohPNieKSiiulGZA/7aa38306086b2bb26b9b789b63baeeb0/es-add-payment-condition.png)
 
 3. En la sección __Pagos Personalizados__, haz clic en la opción __Efectivo__ que ha creado.
 4. Introduce un nombre para esta condición de pago, cambia el status a __Activo__, y en el campo __Procesar con la afiliación__, selecciona el pago personalizado que creaste en el paso anterior.
diff --git a/docs/tracks/es/configuring-dafiti-connector.md b/docs/tracks/es/configuring-dafiti-connector.md
index 568897adb..f3f3a7caf 100644
--- a/docs/tracks/es/configuring-dafiti-connector.md
+++ b/docs/tracks/es/configuring-dafiti-connector.md
@@ -50,7 +50,7 @@ Si se activa la opción <i>No</i>, los intentos de enviar SKU registrados como k
 
 - **Nombre de SKU*:** determina cuál será la regla para nombrar los SKU en el portal de Dafiti. Debe seleccionar una de las combinaciones disponibles de los siguientes atributos: _Marca_, _Nombre del Producto_ y _Nombre del SKU._
 
-![print nome exibicao produto es](//images.ctfassets.net/alneenqid6w5/3MiGbDbIXFGiawLcXjji5w/35e795635bba7aa025facd31d63d76d7/print_nome_exibicao_produto_es.png)
+![print nome exibicao produto es](https://images.ctfassets.net/alneenqid6w5/3MiGbDbIXFGiawLcXjji5w/35e795635bba7aa025facd31d63d76d7/print_nome_exibicao_produto_es.png)
 
 > Ejemplo: mi producto es una zapatilla deportiva negra de Nike. El _Nombre de SKU_ que seleccioné fue _Marca - Nombre del Producto - Nombre del SKU_. Así, el nombre que aparecerá en el portal de Dafiti será Nike zapatilla deportiva negra.
 
diff --git a/docs/tracks/es/configuring-login-with-facebook.md b/docs/tracks/es/configuring-login-with-facebook.md
index 671724c0a..a4aa08eed 100644
--- a/docs/tracks/es/configuring-login-with-facebook.md
+++ b/docs/tracks/es/configuring-login-with-facebook.md
@@ -28,7 +28,7 @@ Después de la configuración en Facebook, es necesario configurar esta opción
 1.  En el módulo de **Configuración de la cuenta**, acceda a la pestaña de **Autenticación**.
 2.  Haga clic en el botón **Editar** correspondiente a Facebook.
 3.  Rellene los campos con el _Client Id_ y _Client Secret_ registrados en **Facebook**.
-    ![Facebook OAuth ES](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/ffc13a1eb81a285feea15e78a72342b9/facebook_ES.png)
+    ![Facebook OAuth ES](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/ffc13a1eb81a285feea15e78a72342b9/facebook_ES.png)
 4.  Haga clic en el botón **Salvar**. 
 5.  Para validar si el inicio de sesión se hizo correctamente, acceda al  front-end de su tienda y haga clic en **Login**.
 6. Aparecerán las opciones de inicio de sesión configuradas. Haga clic en la opción **Facebook** y compruebe si se muestra el nombre de su tienda.
diff --git a/docs/tracks/es/configuring-login-with-google.md b/docs/tracks/es/configuring-login-with-google.md
index 083b471c1..9c996f7d9 100644
--- a/docs/tracks/es/configuring-login-with-google.md
+++ b/docs/tracks/es/configuring-login-with-google.md
@@ -29,7 +29,7 @@ Después de hacer la configuración en Google, puede configurar el inicio de ses
 1.  En el módulo **Configuración de la cuenta**, acceda a la pestaña **Autenticación**.  
 2.  Haga clic en el botón **Editar** correspondiente a Google.
 3.  Complete los campos ingresando el _Client Id_ y _Client Secret_ registrados en **Google**.
-    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
+    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
 5.  Haga clic en el botón **Salvar**. 
 6. Para validar si el inicio de sesión se hizo correctamente, acceda al front-end de su tienda y haga clic en **Login**.
 7. Las opciones de inicio de sesión aparecerán configuradas. Haga clic en la opción **Google** y verifique si se muestra el nombre de su tienda.    
diff --git a/docs/tracks/es/configuring-redirect.md b/docs/tracks/es/configuring-redirect.md
index e5f363e84..09925a4b7 100644
--- a/docs/tracks/es/configuring-redirect.md
+++ b/docs/tracks/es/configuring-redirect.md
@@ -26,7 +26,7 @@ Para configurar un redireccionamiento, es necesario seguir los siguientes pasos:
 
 Debes rellenar los siguientes campos:
 
-![redirecionamentos-adminv4-ES](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
+![redirecionamentos-adminv4-ES](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
 
 ### Informaciones generales
 
diff --git a/docs/tracks/es/configuring-ship-from-store.md b/docs/tracks/es/configuring-ship-from-store.md
index 599416280..f4daba01e 100644
--- a/docs/tracks/es/configuring-ship-from-store.md
+++ b/docs/tracks/es/configuring-ship-from-store.md
@@ -16,7 +16,7 @@ trackSlugES: estrategias-de-comercio-unificado
 
 La estrategia de **Ship From Store** se produce cuando el cliente desea recibir los productos en su casa y estos productos provienen del almacén de una tienda física. En otras palabras, en este escenario, la tienda funciona como un mini centro de distribución.
 
-![35. Setting up Shipping From Store - 1](//images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
+![35. Setting up Shipping From Store - 1](https://images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
 
 Este tipo de logística ayuda a su operación a reducir costos y tiempo de envío. Esto se debe a que, en lugar de tener solo los almacenes principales, generalmente lejos de las áreas centrales de las ciudades, ahora usted tiene una red de entrega más capilar.
 
diff --git a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index e8025111b..9b18c3eb4 100644
--- a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -40,7 +40,7 @@ Para que la integración funcione correctamente, se recomienda conceder todos lo
 10. Haz clic en `Siguiente`.
 11. En la ventana abierta, aparecerá una confirmación de que la integración se ha realizado. Haz clic en `Listo`.
 
-![gif es v1](//images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/aad4d60cb7baecae018ef1d38d25acef/gif_es_v1.gif)
+![gif es v1](https://images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/aad4d60cb7baecae018ef1d38d25acef/gif_es_v1.gif)
 
 ## Envío de datos de productos a Facebook Business Extension
 
diff --git a/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 497c7a1b5..ea164dcf9 100644
--- a/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -80,7 +80,7 @@ Después de rellenar el formulario de configuración de la integración, debes c
 
 En la página **Set up TikTok for Business** (Configurar TikTok for Business), que se muestra abajo, debes seguir las instrucciones de configuración que se describen a continuación.
 
-![set-up-tiktok-for-business](//images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
+![set-up-tiktok-for-business](https://images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
 
 1. Haz clic en la sección **TikTok for Business Account** y verifica que tu cuenta esté en la lista.
     * Si quieres conectar otra cuenta, haz clic en `Disconnect` y repite el paso de inicio de sesión que se describe en [Conectar con la cuenta de TikTok](#2-conectar-con-la-cuenta-de-tiktok).
diff --git a/docs/tracks/es/configuring-the-relevance-feature.md b/docs/tracks/es/configuring-the-relevance-feature.md
index 425921182..68dd4ba5e 100644
--- a/docs/tracks/es/configuring-the-relevance-feature.md
+++ b/docs/tracks/es/configuring-the-relevance-feature.md
@@ -34,7 +34,7 @@ Hay dos áreas para configurar esta funcionalidad: __Criterios de prioridad__ y
   <li><b>Score del catálogo:</b> 3</li>
 </ul>
 
-![default priority criteria ES](//images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/a87d76864944720f3e33c55d0275ada1/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_33.png)
+![default priority criteria ES](https://images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/a87d76864944720f3e33c55d0275ada1/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_22_33.png)
 
 Para cambiar la configuración de relevancia, realice los siguientes pasos.
 
@@ -42,7 +42,7 @@ Para cambiar la configuración de relevancia, realice los siguientes pasos.
 2. Haga clic en __Configuración de relevancia__.
 3. Elija el criterio cuyo peso desea cambiar.
 4. Arrastre el control deslizante hasta el número deseado utilizando el cursor como se muestra en la imagen siguiente.
-  ![composicao-criterios-es](//images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/1753fa46745b8fb9468f1c8adeb47aba/composicao-criterios-es.gif)
+  ![composicao-criterios-es](https://images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/1753fa46745b8fb9468f1c8adeb47aba/composicao-criterios-es.gif)
   Si quiere cambiar la posición de un criterio de __Composición de criterios__ a __Criterios de prioridad__, simplemente arrástrelo por el ícono <i class="fas fa-bars"></i> a la zona superior, como se muestra a continuación. Tenga en cuenta que cuando el criterio se convierte en prioritario, ya no es posible cambiar su peso.
-  ![criterios-prioridad-es](//images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/59e0ec635987e5d8a11aa1e45f296f68/criterios-prioridad-es.gif)
+  ![criterios-prioridad-es](https://images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/59e0ec635987e5d8a11aa1e45f296f68/criterios-prioridad-es.gif)
 5. Para terminar, haga clic en __Guardar__.
diff --git a/docs/tracks/es/create-a-brand.md b/docs/tracks/es/create-a-brand.md
index 865fb91ae..3ec66e584 100644
--- a/docs/tracks/es/create-a-brand.md
+++ b/docs/tracks/es/create-a-brand.md
@@ -18,7 +18,7 @@ Cada producto en su tienda debe formar parte de una categoría, pero también ne
 
 Para registrarla, siga estos pasos:
 
-1. En el módulo __Catalog__, pase el ratón en la pestaña __Registro de productos__ y haga clic en la opción __Marca__.![Marca](//images.contentful.com/alneenqid6w5/BmTrfJzB0kWa6ouku6Uc8/4f57e62ab6dd7e51f65b2dc1f7235dc4/Marca.png)
+1. En el módulo __Catalog__, pase el ratón en la pestaña __Registro de productos__ y haga clic en la opción __Marca__.![Marca](https://images.contentful.com/alneenqid6w5/BmTrfJzB0kWa6ouku6Uc8/4f57e62ab6dd7e51f65b2dc1f7235dc4/Marca.png)
 2. Haga clic en el botón __Nueva marca__.
 3. Introduzca el nombre de la marca en el campo __Nombre__.
 4. Rellene el campo __Título de la página de marca (Tag Title)__ con el título que aparecerá en la barra del navegador cuando el usuario accede a la página de la marca.
diff --git a/docs/tracks/es/create-a-category.md b/docs/tracks/es/create-a-category.md
index be6d4b0a5..3a2a8dba3 100644
--- a/docs/tracks/es/create-a-category.md
+++ b/docs/tracks/es/create-a-category.md
@@ -20,14 +20,14 @@ Después de que su árbol de categorías está establecido, usted ya puede inser
 
 En VTEX, el registro de categorías se realiza en el módulo __Catalog__.
 
-1. En el menú de la topbar de su admin, haga clic en __Catalog__ (si ya no está allí).![Catalog](//images.contentful.com/alneenqid6w5/48wP1cDIw0EwoeOUY8OGWI/8874d5f10e57364c7d78852d5b48aed4/catalog.png)
-2. En las opciones de la pestaña __Cadastro de Productos__, haga clic en __Categoría __.![Categoria](//images.contentful.com/alneenqid6w5/2w0IBMGwik0AGauGA4Eu0G/260db5fed8cca932f10b194a05a5f9c1/Categoria.png)
+1. En el menú de la topbar de su admin, haga clic en __Catalog__ (si ya no está allí).![Catalog](https://images.contentful.com/alneenqid6w5/48wP1cDIw0EwoeOUY8OGWI/8874d5f10e57364c7d78852d5b48aed4/catalog.png)
+2. En las opciones de la pestaña __Cadastro de Productos__, haga clic en __Categoría __.![Categoria](https://images.contentful.com/alneenqid6w5/2w0IBMGwik0AGauGA4Eu0G/260db5fed8cca932f10b194a05a5f9c1/Categoria.png)
 
 En la parte izquierda de la pantalla, usted verá el nivel más alto de categorías, que por defecto tiene el nombre __Categorías__. Es dentro de él que vamos a distribuir las categorías de su árbol.
 Haga clic en él y siga los pasos abajo:
 
-1. Haga clic en el botón __Acciones__ que aparece a la derecha de su pantalla.![acoes](//images.contentful.com/alneenqid6w5/lIbUp2QFuSckgmwsSGigE/41351e98a797a11deeb60d7bf7b0cac5/acoes.png)
-2. Haga clic en la opción __Incluir__.![incluir](//images.contentful.com/alneenqid6w5/3DGlwjNNpmsW80AYS6CM4Q/3ccf2d1d74bb18e7ebd234977b1137ec/incluir.png)
+1. Haga clic en el botón __Acciones__ que aparece a la derecha de su pantalla.![acoes](https://images.contentful.com/alneenqid6w5/lIbUp2QFuSckgmwsSGigE/41351e98a797a11deeb60d7bf7b0cac5/acoes.png)
+2. Haga clic en la opción __Incluir__.![incluir](https://images.contentful.com/alneenqid6w5/3DGlwjNNpmsW80AYS6CM4Q/3ccf2d1d74bb18e7ebd234977b1137ec/incluir.png)
 
 Usted puede ver la lista completa de los campos de registro de categoría [en este artículo](/pt/tutorial/campos-de-cadastro-de-categoria).
 Pero aquí nos atenemos a algunos campos.
diff --git a/docs/tracks/es/create-a-product.md b/docs/tracks/es/create-a-product.md
index 64794b904..0e2b614d1 100644
--- a/docs/tracks/es/create-a-product.md
+++ b/docs/tracks/es/create-a-product.md
@@ -46,8 +46,8 @@ Vamos a ver cómo crear el producto.
 En el módulo __Catalog__, siga estos pasos:
 
 1. Pase el ratón en la pestaña __Regitro de Productos__.
-2. Vaya a la opción __Productos y SKUs__ y haga clic en __Registro de Productos y SKUs__.![Produto1](//images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
-3. Haga clic en el botón __Agregar producto__.![Produto2](//images.contentful.com/alneenqid6w5/2HhkAREgQMMAkIMm8GaGgQ/7038413048c0611edb9079acd73020ba/Produto2.png)
+2. Vaya a la opción __Productos y SKUs__ y haga clic en __Registro de Productos y SKUs__.![Produto1](https://images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
+3. Haga clic en el botón __Agregar producto__.![Produto2](https://images.contentful.com/alneenqid6w5/2HhkAREgQMMAkIMm8GaGgQ/7038413048c0611edb9079acd73020ba/Produto2.png)
 
 Se le llevará a la pantalla de registro de producto.
 
diff --git a/docs/tracks/es/create-an-sku.md b/docs/tracks/es/create-an-sku.md
index 159418c74..8c7e1c763 100644
--- a/docs/tracks/es/create-an-sku.md
+++ b/docs/tracks/es/create-an-sku.md
@@ -19,9 +19,9 @@ Después de crear el producto, es hora de crear el primer SKU que formará parte
 Si después de rellenar los campos del [registro de producto](/pt/getting-started/crear-un-producto), se hace clic en __Guardar y registrar SKU__, la pantalla que aparece a continuación será justamente la de registro de SKU.
 
 Pero también es posible llegar al registro de SKU por el camino abajo:
-1. Acceda al módulo __Catalog__ y, en la pestaña __Registro de productos__, vaya a la opción __Productos y SKUs__ y haga clic en __Registro de productos y SKUs__![Produto1](//images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
+1. Acceda al módulo __Catalog__ y, en la pestaña __Registro de productos__, vaya a la opción __Productos y SKUs__ y haga clic en __Registro de productos y SKUs__![Produto1](https://images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
 2. Haga clic en la flecha del botón azul, en la línea del producto para el cual quiere crear el SKU, y luego en la opción __SKU__.
-3. Haga clic en el botón __Nuevo SKU__.![novoSKU](//images.contentful.com/alneenqid6w5/5VonhvkjXaoma84SqGuYSQ/f072e69753933862ba5ad205f9a55ecd/novoSKU.gif)
+3. Haga clic en el botón __Nuevo SKU__.![novoSKU](https://images.contentful.com/alneenqid6w5/5VonhvkjXaoma84SqGuYSQ/f072e69753933862ba5ad205f9a55ecd/novoSKU.gif)
 
 Usted será llevado a la pantalla de registro de SKU.
 
diff --git a/docs/tracks/es/create-brands.md b/docs/tracks/es/create-brands.md
index a80b3edda..222a5eeba 100644
--- a/docs/tracks/es/create-brands.md
+++ b/docs/tracks/es/create-brands.md
@@ -39,7 +39,7 @@ Las informaciones rellenadas en el registro se pueden actualizar en cualquier mo
 
 Para eliminar el registro de alguna marca, debe hacer clic en la flecha al lado de `Editar` y seleccionar la opción `Eliminar`.
 
-![editar-marca es](//images.ctfassets.net/alneenqid6w5/1klwWT7dVmC63Az7KqX4hI/5fb442a9f0f4c3b566b61899ad17eb3c/editar-marca_ES.png)
+![editar-marca es](https://images.ctfassets.net/alneenqid6w5/1klwWT7dVmC63Az7KqX4hI/5fb442a9f0f4c3b566b61899ad17eb3c/editar-marca_ES.png)
 
 ## API
 
diff --git a/docs/tracks/es/create-the-category-tree.md b/docs/tracks/es/create-the-category-tree.md
index 3fe90b568..7ee5ec126 100644
--- a/docs/tracks/es/create-the-category-tree.md
+++ b/docs/tracks/es/create-the-category-tree.md
@@ -38,7 +38,7 @@ Al principio del proyecto, antes de que cualquier producto sea insertado en la p
 
 Este, por lo tanto, podría ser el diseño inicial del árbol de categorías de su tienda:
 
-![ArbolCategorias](//images.contentful.com/alneenqid6w5/5PafF9e7i84ik0KGG6gAe8/e5b88d15993ef729b6f55c3b73b3ba93/ArbolCategorias.png)
+![ArbolCategorias](https://images.contentful.com/alneenqid6w5/5PafF9e7i84ik0KGG6gAe8/e5b88d15993ef729b6f55c3b73b3ba93/ArbolCategorias.png)
 
 __OBS__: la nomenclatura __Departamento / Categoría / Subcategoría__ es solamente una manera de ver su árbol, y que puede o no facilitar su trabajo. La plataforma no requiere este o cualquier otro patrón de nomenclatura. Para VTEX, los niveles que se crean para la distribución de sus productos sólo se toman como niveles de categoría.
 
diff --git a/docs/tracks/es/creating-accounts.md b/docs/tracks/es/creating-accounts.md
index 1a43f9380..4a26629b3 100644
--- a/docs/tracks/es/creating-accounts.md
+++ b/docs/tracks/es/creating-accounts.md
@@ -40,7 +40,7 @@ El llenado del campo <b>Email</b> es obligatorio, ya que la plataforma VTEX util
 
 A partir de este momento, la nueva cuenta creada se mostrará en la pantalla __Cuentas__.
 
-![CC_nueva_cuenta_1_ES](//images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/137feed49de06cbae706252e4d6ef813/CC_nueva_cuenta_1_ES.JPG)
+![CC_nueva_cuenta_1_ES](https://images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/137feed49de06cbae706252e4d6ef813/CC_nueva_cuenta_1_ES.JPG)
 
 ## Crear varias cuentas (importación masiva)
 
@@ -57,7 +57,7 @@ Para crear varias cuentas al mismo tiempo (en masa) en Customer Credit, puede ut
   <li>Columnas <b>Credit limit</b> y <b>Tolerance rate</b>: valores disponibles para cada cliente. La <b>tasa de tolerancia</b> debe ingresarse en formato decimal, por ejemplo, una tolerancia del 5% debe indicarse como 0,05.</li>
 </ul>
 
-![CC_criar_conta_2_ALL](//images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
+![CC_criar_conta_2_ALL](https://images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
 
 <blockquote><ui>6. Guardar la plantilla .csv.</ui>
 
diff --git a/docs/tracks/es/creating-merchandising-rules-visual-editor.md b/docs/tracks/es/creating-merchandising-rules-visual-editor.md
index 8c825d540..b54bc86a5 100644
--- a/docs/tracks/es/creating-merchandising-rules-visual-editor.md
+++ b/docs/tracks/es/creating-merchandising-rules-visual-editor.md
@@ -50,7 +50,7 @@ Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vte
 
 El Editor visual de reglas de merchandising de VTEX Intelligent Search permite realizar las acciones que se ilustran en la imagen siguiente:
 
-![visual-merch-rules-ES-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
+![visual-merch-rules-ES-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Editar nombre de la regla de merchandising.</li>
@@ -85,7 +85,7 @@ El Editor visual de reglas de merchandising de VTEX Intelligent Search permite r
 
 El filtro es un atributo seleccionable predefinido que restringe los resultados de la búsqueda, por ejemplo, permite filtrar por todos los productos de una categoría o marca, entre otras condiciones. Puedes agregar una o más condiciones a un filtro, tal como se muestra a continuación.
 
-![filtros-merchrules-es](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
+![filtros-merchrules-es](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
 
 Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
 
diff --git a/docs/tracks/es/creating-or-editing-a-page-template.md b/docs/tracks/es/creating-or-editing-a-page-template.md
index 2ddd43236..53186a073 100644
--- a/docs/tracks/es/creating-or-editing-a-page-template.md
+++ b/docs/tracks/es/creating-or-editing-a-page-template.md
@@ -41,8 +41,8 @@ Vea a continuación el procedimiento:
 <li><code>admin</code></li>
 </ul></p>
 </div>
-7. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
-8. En la esquina superior derecha, haga clic en el botón  __Save Template__.![4 2](//images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
+7. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+8. En la esquina superior derecha, haga clic en el botón  __Save Template__.![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
 Para editar un template ya existente, el proceso es casi idéntico.
 
diff --git a/docs/tracks/es/creating-regular-promotions.md b/docs/tracks/es/creating-regular-promotions.md
index c534ccfdf..404b48fb3 100644
--- a/docs/tracks/es/creating-regular-promotions.md
+++ b/docs/tracks/es/creating-regular-promotions.md
@@ -112,7 +112,7 @@ En esta sección, debes seleccionar si la promoción se aplicará a todos los pr
 Puedes incluir o excluir **categorías**, **marcas**, **colecciones**, **productos** y **SKU** de la promoción utilizando los criterios **Igual a** o **Diferentes de**.
 Los productos deben cumplir todas las condiciones para ser válidos en la promoción.
 
-![A quais itens esta promoção será aplicada - ES](//images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/7ad5d4c49596dad8d2e81e0f1ef28d66/A_quais_itens_-_ES.png)
+![A quais itens esta promoção será aplicada - ES](https://images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/7ad5d4c49596dad8d2e81e0f1ef28d66/A_quais_itens_-_ES.png)
 
 # 3. Condiciones de la promoción
 El pedido del cliente debe cumplir las condiciones registradas en esta sección para ser válido en la promoción.
diff --git a/docs/tracks/es/credit-card-payment-flow.md b/docs/tracks/es/credit-card-payment-flow.md
index 54a69fa5d..31cb99c1d 100644
--- a/docs/tracks/es/credit-card-payment-flow.md
+++ b/docs/tracks/es/credit-card-payment-flow.md
@@ -31,7 +31,7 @@ Para saber más sobre los agentes financieros involucrados en el flujo de pago d
 
 El flujo completo para pago por tarjeta de crédito en VTEX puede ser descrito por la siguiente imagen.  
 
-![Tarjeta de crédito - Flujo básico de un pago](//images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/354650e116ee61e05196dd1b592b6f6c/payments_image1_ES.JPG)
+![Tarjeta de crédito - Flujo básico de un pago](https://images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/354650e116ee61e05196dd1b592b6f6c/payments_image1_ES.JPG)
 
 1. En la pantalla de Checkout de su tienda, el cliente elige el **Medio de pago** _tarjeta de crédito_ para realizar el pago de su compra.
 2. La información de este pago se pasa al **Gateway de Pagos**, que es el player responsable de garantizar que este pago se realice con éxito.
diff --git a/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md b/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
index 22e247e94..f5d9274b5 100644
--- a/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
+++ b/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
@@ -50,4 +50,4 @@ Verifique con su transportadora si la unidad de medida está en <strong>gramos</
 Al realizar el registro de su transportadora, ese es el valor que debe completar  en el campo Factor Cúbico de Peso.
 
 
-![PesoCubado](//images.contentful.com/alneenqid6w5/ZzHF9fwwec6c6m2AiyYGS/37343a8bb4858cdf296f5a3c450567f3/PesoCubado.png)
+![PesoCubado](https://images.contentful.com/alneenqid6w5/ZzHF9fwwec6c6m2AiyYGS/37343a8bb4858cdf296f5a3c450567f3/PesoCubado.png)
diff --git a/docs/tracks/es/customer-identification.md b/docs/tracks/es/customer-identification.md
index 4feaf1459..4a3d025f5 100644
--- a/docs/tracks/es/customer-identification.md
+++ b/docs/tracks/es/customer-identification.md
@@ -27,7 +27,7 @@ Usted puede [configurar qué métodos de identificación desea habilitar](https:
 
 En el ejemplo de la imagen a continuación, Email y CPF están habilitados.
 
-![31. inStore - Product Overview - 2 - ES](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99fe77f7a5c0a43318ffa841e67d20cb/identify-customer-es.PNG)
+![31. inStore - Product Overview - 2 - ES](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/99fe77f7a5c0a43318ffa841e67d20cb/identify-customer-es.PNG)
 
 Ingrese uno de estos datos en el campo y haga clic en el botón `Confirmar`.
 
diff --git a/docs/tracks/es/customizing-styles.md b/docs/tracks/es/customizing-styles.md
index 87dfb4ef3..0e529f00b 100644
--- a/docs/tracks/es/customizing-styles.md
+++ b/docs/tracks/es/customizing-styles.md
@@ -48,7 +48,7 @@ Vamos a hacer algunos cambios en nuestro archivo `style.json`. Podemos cambiar u
 
 Ahora, vamos a ver los resultados al "linkar" nuestra aplicación:
 
-![style-json](//images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
+![style-json](https://images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
 
 Muy bien! Ahora usted sabe cómo personalizar los estilos de su tienda.
 
@@ -98,4 +98,4 @@ Vamos a escribir un poco de CSS, para añadir una línea roja sólida:
 ```
 Nuestro nuevo menú de categoría tendrá ahora una línea roja sólida a lo largo de la parte inferior del menú.
 
-![red-line](//images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
+![red-line](https://images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
diff --git a/docs/tracks/es/customizing-templates.md b/docs/tracks/es/customizing-templates.md
index d4c93077b..8db7d9d97 100644
--- a/docs/tracks/es/customizing-templates.md
+++ b/docs/tracks/es/customizing-templates.md
@@ -119,6 +119,6 @@ Para añadir un componente a esa página, basta con declarar un nuevo bloque de
 
 Si guarda esto en `store/blocks.json` y ejecuta `vtex link` en su tienda, usted deberá ver un nuevo estante renderizado al visitar la página principal.
 
-![shelf](//images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
+![shelf](https://images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
 
 Usted puede personalizar los bloques declarados por la app `store-theme` libremente y también declarar nuevos. Por ahora, usted puede encontrar la documentación para cada componente en sus [repositorios de GitHub](https://github.com/vtex-apps?q=store-components). Aquí encontrará las propiedades disponibles para cada componente.
diff --git a/docs/tracks/es/dashboard.md b/docs/tracks/es/dashboard.md
index 42d18d920..1f82f1db3 100644
--- a/docs/tracks/es/dashboard.md
+++ b/docs/tracks/es/dashboard.md
@@ -16,7 +16,7 @@ trackSlugES: conversational-commerce
 
 En la página Dashboard, los dueños de tiendas VTEX pueden ver las métricas del canal [VTEX Conversational Commerce](https://help.vtex.com/es/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/1NwwADrU70v3roPUV7dWxI). En este panel, puedes ver el rendimiento de las ventas y los indicadores de las sesiones, que también puedes filtrar por periodo y exportar a un archivo CSV.
 
-![Conversational Commerce Analytics Panel](//images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/5493bb92bc05b4ab33eb295551783a96/Conversational_Commerce_Analytics_Panel_ES.png)
+![Conversational Commerce Analytics Panel](https://images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/5493bb92bc05b4ab33eb295551783a96/Conversational_Commerce_Analytics_Panel_ES.png)
 
 ## Datos
 
diff --git a/docs/tracks/es/delivery.md b/docs/tracks/es/delivery.md
index 9973ab0d2..e5ced40e6 100644
--- a/docs/tracks/es/delivery.md
+++ b/docs/tracks/es/delivery.md
@@ -27,19 +27,19 @@ Puedes elegir entre:
 - Recoger en una tienda física.
 - Personalizar por ítem.
 
-![entrega-2-es](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/338f5137a3c8c920f612657fd7290f3d/entrega-2-es.png)
+![entrega-2-es](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/338f5137a3c8c920f612657fd7290f3d/entrega-2-es.png)
 
 ### Puntos de recogida
 
 Para los puntos de recogida, el sistema selecciona las tiendas que tienen los SKUs en stock y muestra la tienda más cercana al código postal del cliente, como sugerencia. Si el vendedor quiere cambiar la tienda donde el cliente recogerá los productos, solo hay que hacer clic en el botón `Editar punto de recogida`.
 
-![entrega-retirada-es](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/6cdbea15076e2d11b6bcdb4bb72108ab/entrega-retirada-es.png)
+![entrega-retirada-es](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/6cdbea15076e2d11b6bcdb4bb72108ab/entrega-retirada-es.png)
 
 Al hacer clic en ese botón, el vendedor primero tiene acceso al punto de recogida sugerido por el sistema. Para ver todos los puntos de recogida disponibles, hay que hacer clic en `Ver todos los puntos de recogida`.
 
-![31. VTEX Sales App - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
+![31. VTEX Sales App - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
 
 La aplicación mostrará la lista de puntos de recogida ordenados por la distancia más corta desde el código postal del cliente. También es posible elegir el punto de recogida en el mapa.
 
-![31. VTEX Sales App - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
+![31. VTEX Sales App - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
 
diff --git a/docs/tracks/es/detaching-skus-by-specification.md b/docs/tracks/es/detaching-skus-by-specification.md
index 9dc8872b0..98f52f322 100644
--- a/docs/tracks/es/detaching-skus-by-specification.md
+++ b/docs/tracks/es/detaching-skus-by-specification.md
@@ -24,7 +24,7 @@ Esta herramienta se recomienda, principalmente, para las tiendas de ropa, porque
 
 A continuación, vea un ejemplo de separación de SKUs por color. La sandalia que se destaca en la siguiente imagen se exhibe en dos colores en el resultado de la búsqueda:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.</p></div>
diff --git a/docs/tracks/es/enabling-2-factor-authentication-login.md b/docs/tracks/es/enabling-2-factor-authentication-login.md
index 5251c5e7f..78c13db36 100644
--- a/docs/tracks/es/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/es/enabling-2-factor-authentication-login.md
@@ -31,7 +31,7 @@ Hay dos opciones de autenticación:
 - __App Google__ (clave generada por aplicación de autenticación)
 - __Mensaje SMS__ (clave enviada por mensaje de texto)
 
-![2FA - Select - ES](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
+![2FA - Select - ES](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
 
 <div class="alert alert-warning">
 Recomendamos el uso de la <a href="#habilitar-o-2fa-por-aplicativo">aplicación de autenticación</a> para que las fallas del servicio de su operador de telefonía no impidan su inicio de sesión. A través de la aplicación, la clave de acceso siempre estará disponible para que la utilice.
@@ -47,17 +47,17 @@ Debido a que algunas empresas restringen el uso de celulares a los operadores de
 Para utilizar una clave generada a través de la aplicación de autenticación:
 1. Descargue la aplicación **Google Autenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)). 
 
-![2FA - App Download - ES](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
+![2FA - App Download - ES](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
 
 2. Utilice la aplicación para leer el código QR a través de la cámara del celular.
 
-![2FA - App QR Code - ES](//images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/fde55b590db79ef108e5f1d508e18d3a/2FA_-_App_QR_Code_-_ES.png)
+![2FA - App QR Code - ES](https://images.ctfassets.net/alneenqid6w5/1Nyt9wLnfYG5z75tUhinQ6/fde55b590db79ef108e5f1d508e18d3a/2FA_-_App_QR_Code_-_ES.png)
 
 3. Su cuenta VTEX se agregará a la aplicación, que generará un código de 6 dígitos. Ingrese ese código para finalizar su inicio de sesión.
 
   *El código de la app se actualiza periódicamente. No es necesario que lo memorice, solo debe consultar la aplicación cuando lo necesite.*
 
-![2FA - App Insert Code - ES](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
+![2FA - App Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
 
 <div class="alert alert-info">
 Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso <strong> cada 3 días</strong>. Cuando eso suceda, basta con consultar el código en la aplicación.
@@ -69,11 +69,11 @@ Para utilizar una clave enviada a través de mensaje de texto:
 
 1. Ingrese su número de celular para que le enviemos el código por SMS, no olvide colocar el código de país y área. 
 
-![2FA - SMS Insert Phone - ES](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
+![2FA - SMS Insert Phone - ES](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
 
 2. Usted recibirá un mensaje de texto de VTEX en el celular indicado. Ingrese la clave de 6 dígitos para finalizar su inicio de sesión.
 
-![2FA - SMS Insert Code - ES](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
+![2FA - SMS Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
 
 <div class="alert alert-warning">
 No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o <a href="#habilitar-o-2fa-por-aplicativo">habilitar 2FA a través de la aplicación</a>.
@@ -85,11 +85,11 @@ Para modificar la configuración de la verificación en dos etapas:
 
 1. Acceda a su configuración de usuario, haciendo clic en el círculo con sus iniciales en el lado superior derecho del Admin. 
 
-![2FA - User Initials - ES](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
+![2FA - User Initials - ES](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
 
 2. Haga clic en **Verificación en 2 pasos** para ver su configuración.
 
-![2FA - My User - ES](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
+![2FA - My User - ES](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
 
 3. Usted también puede modificar su configuración siguiendo pasos similares a los anteriores para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) y por [aplicación](#habilitar-o-2fa-por-aplicativo).
 
diff --git a/docs/tracks/es/enabling-a-sales-rep-code.md b/docs/tracks/es/enabling-a-sales-rep-code.md
index 2ff62450e..16afe7087 100644
--- a/docs/tracks/es/enabling-a-sales-rep-code.md
+++ b/docs/tracks/es/enabling-a-sales-rep-code.md
@@ -42,7 +42,7 @@ Después de seguir estas recomendaciones, acceda al módulo __Configuración de
 
 Al lado derecho de la pantalla, encontrará el archivo `checkout-custom-instore.js`.
 
-![codevendorES.png?h=250](//images.ctfassets.net/alneenqid6w5/4hITwpBXNEoN359J96d2oy/0bb39f0f4085e4daf2bc3d6b4fca1d97/codevendorES.png)
+![codevendorES.png?h=250](https://images.ctfassets.net/alneenqid6w5/4hITwpBXNEoN359J96d2oy/0bb39f0f4085e4daf2bc3d6b4fca1d97/codevendorES.png)
 
 Acceda a este archivo y agregue el siguiente código al objeto `window.INSTORE_CONFIG`:
 
@@ -66,7 +66,7 @@ Cada responsable debe completar las propiedades del objeto `window.INSTORE_CONFI
 
 Por último, finalice haciendo clic en el botón azul __Guardar__ que se encuentra en la parte superior de la página.
 
-![codevendor2ES](//images.ctfassets.net/alneenqid6w5/zkFzm3m0NvekTQZQRznzZ/8a65b58374a71cd91b3ce972844fc762/codevendor2ES.png)
+![codevendor2ES](https://images.ctfassets.net/alneenqid6w5/zkFzm3m0NvekTQZQRznzZ/8a65b58374a71cd91b3ce972844fc762/codevendor2ES.png)
 
 ## Entendiendo las propiedades
 
diff --git a/docs/tracks/es/enabling-cart-transfer-between-devices.md b/docs/tracks/es/enabling-cart-transfer-between-devices.md
index bc0daf875..12f212d3b 100644
--- a/docs/tracks/es/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/es/enabling-cart-transfer-between-devices.md
@@ -34,11 +34,11 @@ window.INSTORE_CONFIG = {
 
 Después de realizar este cambio, abra el menú inStore y actualice los datos haciendo clic en el botón __Restaurar Datos__. Una vez hecho esto, aparecerá un slider en la parte inferior de la página de identificación de inStore:
 
-![24. Enable cart transfer between devices - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/62BOCXeTPeE0Qa4dJQvAWV/01364823bc0b73dd1b8f383215f6602e/24._Enable_cart_transfer_between_devices_-_1_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/62BOCXeTPeE0Qa4dJQvAWV/01364823bc0b73dd1b8f383215f6602e/24._Enable_cart_transfer_between_devices_-_1_-_ES.png_h_250)
 
 Cuando arrastre la pantalla hacia la derecha, verá la pantalla para __Capturar Carrito__, como se muestra en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7GdTfFFfOFLoogeWZCHThR/0287a10b7fe85ed4fb1cd4a17045fc36/24._Enable_cart_transfer_between_devices_-_2_-_ES.png_h_250)
 
 En esta pantalla, el vendedor puede capturar un carrito utilizando uno de estos tres métodos:
 - Código del carrito
@@ -49,4 +49,4 @@ En esta pantalla, el vendedor puede capturar un carrito utilizando uno de estos
 
 Para compartir un carrito, el vendedor puede generar un código numérico o un código QR. Para hacer esto, mientras está en la pantalla del carrito, haga clic en el botón __Transferir__. Vea un ejemplo en la imagen a continuación.
 
-![24. Enable cart transfer between devices - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
+![24. Enable cart transfer between devices - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/lur8HH4iTaiw0KKkq7UHn/90dd5fa5297759372d7cb5c8f083559e/24._Enable_cart_transfer_between_devices_-_3_-_ES.png_h_250)
diff --git a/docs/tracks/es/enabling-product-recommendations.md b/docs/tracks/es/enabling-product-recommendations.md
index 4b734665c..2c3f6c96a 100644
--- a/docs/tracks/es/enabling-product-recommendations.md
+++ b/docs/tracks/es/enabling-product-recommendations.md
@@ -28,7 +28,7 @@ Si desea ocultar estas recomendaciones, debe editar los archivos `checkout-insto
 
 Al igual que el archivo JavaScript de personalización inStore, se debe acceder a `checkout-instore-custom.css` a través del panel administrativo de VTEX (como se explica en el artículo sobre [personalizaciones en el inStore](https://help.tex.com/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/4mwdBrFsmE2EPE0FzgX28b)).
 
-![25. Enable product recommendations - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/nEA1Zz5EeltimlFEFSMzy/8f489dd051c79453fd858d5376699c79/25._Enable_product_recommendations_-_1_-_ES.png_h_250)
+![25. Enable product recommendations - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/nEA1Zz5EeltimlFEFSMzy/8f489dd051c79453fd858d5376699c79/25._Enable_product_recommendations_-_1_-_ES.png_h_250)
 
 En el archivo `checkout-instore-custom.css`, incluya la siguiente regla CSS:
 
diff --git a/docs/tracks/es/explained-search.md b/docs/tracks/es/explained-search.md
index 7381a59ee..5bef7462a 100644
--- a/docs/tracks/es/explained-search.md
+++ b/docs/tracks/es/explained-search.md
@@ -26,5 +26,5 @@ Siga las instrucciones a continuación para acceder a la página:
 1. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
 2. En **Intelligent Search**, haga clic en **Explicación de la búsqueda**. 
 
-![Explicación de Búsqueda](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
+![Explicación de Búsqueda](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
 
diff --git a/docs/tracks/es/extensions-hub-1.md b/docs/tracks/es/extensions-hub-1.md
index 4b04faa62..aa0218d96 100644
--- a/docs/tracks/es/extensions-hub-1.md
+++ b/docs/tracks/es/extensions-hub-1.md
@@ -18,6 +18,6 @@ El Hub de extensiones es una sección del Admin VTEX que agrupa toda la informac
 
 Para acceder al Hub de extensiones ve al panel lateral izquierdo del Admin, haz clic en el ícono **Extensiones** y verás la sección en la parte superior del menú.
 
-![Extensions Hub panel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
+![Extensions Hub panel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/d20a9d4bf800eeaa2e6b952c312b0982/Extensions_Hub_panel_ES.png)
 
 La sección del Hub de extensiones tiene tres páginas: **App Store**, **Partners** y **Gestión de aplicaciones**. La documentación sobre cada una de ellas puede consultarse en los artículos a continuación.
diff --git a/docs/tracks/es/extensions-hub-app-store.md b/docs/tracks/es/extensions-hub-app-store.md
index b8b0814af..63a0620e7 100644
--- a/docs/tracks/es/extensions-hub-app-store.md
+++ b/docs/tracks/es/extensions-hub-app-store.md
@@ -20,7 +20,7 @@ App Store es la página del Admin VTEX donde puedes buscar, visualizar y obtener
 
 Al entrar en la tienda estarás en la página de inicio,  con las siguientes opciones disponibles: 
 
-![Extensions Hub App Store página de inicio](//images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/03756392e94a93e19546acc1f9e1bc75/Extensions_Hub_App_Store_home_page_ES.png)
+![Extensions Hub App Store página de inicio](https://images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/03756392e94a93e19546acc1f9e1bc75/Extensions_Hub_App_Store_home_page_ES.png)
 
 * **Buscar:** cuadro de texto donde puedes buscar aplicaciones en la tienda. Al escribir en el cuadro de texto y pulsar la tecla `Intro`, accederás a la [página de búsqueda](#buscar).
 * **Destacados:** aplicaciones y partners destacados. Los destacados aparecen en formato de tarjetas rectangulares, en las que se puede ver el título y el subtítulo. Al hacer clic en un elemento destacado, accederás a la página de una aplicación o a la de un partner.
@@ -28,13 +28,13 @@ Al entrar en la tienda estarás en la página de inicio,  con las siguientes opc
 
 ## Buscar
 
-![Extensions Hub App Store busca](//images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/59564b2103a79a2e5b4ebd9dfbad5fa5/Extensions_Hub_App_Store_search_ES.png)
+![Extensions Hub App Store busca](https://images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/59564b2103a79a2e5b4ebd9dfbad5fa5/Extensions_Hub_App_Store_search_ES.png)
 
 El cuadro de búsqueda te permite buscar aplicaciones por su nombre. Al escribir lo que deseas encontrar y pulsar `Intro`, se te dirigirá a la página de resultados de la búsqueda. Los resultados serán las aplicaciones cuyos nombres coincidan con el texto introducido en la búsqueda. Las aplicaciones aparecen en formato de tarjetas cuadradas, donde puedes ver el nombre, el subtítulo y el costo de la misma. Al hacer clic en una tarjeta, accederás a la [página de la aplicación](#pagina-de-la-aplicacion).
 
 ## Página de la aplicación
 
-![Extensions Hub App Store app page](//images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/a08b32f1a0af455d68c111c42cf4dd75/Extensions_Hub_App_Store_app_page_ES.png)
+![Extensions Hub App Store app page](https://images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/a08b32f1a0af455d68c111c42cf4dd75/Extensions_Hub_App_Store_app_page_ES.png)
 
 Al hacer clic en una tarjeta en la página de inicio o en la búsqueda, se te dirigirá a la página de inicio de la aplicación. En esta página encontrarás toda la información sobre la aplicación, incluido el precio, y la opción de comprarla.
 
diff --git a/docs/tracks/es/filter-orders-by-vendor.md b/docs/tracks/es/filter-orders-by-vendor.md
index a0ab8e782..1a1d3ea0f 100644
--- a/docs/tracks/es/filter-orders-by-vendor.md
+++ b/docs/tracks/es/filter-orders-by-vendor.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 En inStore es posible ver el listado de todos los pedidos finalizados en una tienda:
 
-![pedidos finalizados](//images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
+![pedidos finalizados](https://images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
 
 Sin embargo, a veces tiene sentido que un vendedor vea sólo los pedidos finalizados por él. Para habilitar esta opción es necesario editar el archivo `checkout-instore-custom.js` presente en el Admin del Portal. Por tratarse de un JavaScript presente en diversos flujos de uso de la aplicación, es importante que usted tenga conocimientos de programación antes de cambiarlo, para evitar la ruptura de otras funcionalidades.
 
@@ -37,4 +37,4 @@ __IMPORTANTE__: No quite ninguna de las otras propiedades presentes en el objeto
 
 Después de recargar el inStore el resultado debe ser el siguiente:
 
-![pedidos finalizados filtrados por vendedor](//images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
+![pedidos finalizados filtrados por vendedor](https://images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
diff --git a/docs/tracks/es/frontend-implementation.md b/docs/tracks/es/frontend-implementation.md
index b306a5c30..b5dd98e38 100644
--- a/docs/tracks/es/frontend-implementation.md
+++ b/docs/tracks/es/frontend-implementation.md
@@ -93,7 +93,7 @@ Cuando se habla de implementación frontend, cabe recordar que [VTEX IO](https:/
 
 Esto significa que cuando trabajas con VTEX IO, desarrollas tu código localmente. Sin embargo, en lo que respecta a implementar y ejecutar la tienda, además de encargarse del proceso de deploy, VTEX IO gestiona la infraestructura, CI/CD y la seguridad. La siguiente imagen muestra cómo se relacionan estos conceptos entre sí:
 
-![Arquitectura de desarrollo frontend](//images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/b86208e7447890ebd62183059c0b22f6/frontend_image3_ES.png)
+![Arquitectura de desarrollo frontend](https://images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/b86208e7447890ebd62183059c0b22f6/frontend_image3_ES.png)
 
 ### Principales funcionalidades de Store Framework
 
@@ -228,7 +228,7 @@ El equipo de desarrollo debe iniciar un nuevo proyecto con FastStore a través d
 - Página de detalles de producto (PDP)
 - Minicart
 
-![FastStore template](//images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
+![FastStore template](https://images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
 
 #### Requisitos para un PMV de FastStore
 
@@ -281,7 +281,7 @@ El equipo de desarrollo debe iniciar un nuevo proyecto con Store Framework clona
 - Página de lista de productos (PLP)
 - Página de detalles de producto (PDP)
 
-![Store Framework template](//images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
+![Store Framework template](https://images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
 
 #### Requisitos para un PMV de Store Framework
 
diff --git a/docs/tracks/es/frontend.md b/docs/tracks/es/frontend.md
index c99033826..d6a9ce07c 100644
--- a/docs/tracks/es/frontend.md
+++ b/docs/tracks/es/frontend.md
@@ -26,7 +26,7 @@ La ampliación de funcionalidades se produce a través de aplicaciones VTEX disp
 
 Store Framework es una solución para construir storefronts aprovechando VTEX IO. Esta solución permite utilizar la interfaz intuitiva de [Site Editor](https://help.vtex.com/es/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) y simplificar la gestión de contenido de la tienda.
 
-![vtex io](//images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5c359c6ec0fd106a7f7783669485c64e/image3.png)
+![vtex io](https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/5c359c6ec0fd106a7f7783669485c64e/image3.png)
 
 Las tiendas creadas con Store Framework también tienen las siguientes funcionalidades:
 - **[Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)**: herramienta de búsqueda que corrige errores ortográficos y permite usar reglas condicionales para mostrar los resultados de búsqueda.
diff --git a/docs/tracks/es/getting-started-with-logistics.md b/docs/tracks/es/getting-started-with-logistics.md
index ce9be5d6f..9dd93b2ea 100644
--- a/docs/tracks/es/getting-started-with-logistics.md
+++ b/docs/tracks/es/getting-started-with-logistics.md
@@ -55,7 +55,7 @@ El módulo de **Inventario y envío** se divide en las siguientes secciones:
 * **Configuración**: configuraciones logísticas generales, como la activación de la notificación de stock crítico.
 * **[Puntos de recogida](https://help.vtex.com/es/tutorial/puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R)**: sección para registrar los puntos físicos donde los clientes pueden recoger sus pedidos.
 
-![estoque e entregaES](//images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/a66b016481c796b9170823b1c111d3d9/estoque_e_entregaES.png)
+![estoque e entregaES](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/a66b016481c796b9170823b1c111d3d9/estoque_e_entregaES.png)
 
 <div class = "alert alert-info">
 Los clientes que utilizan <a href="https://vtex.com/ar-es/">VTEX Shipping Network</a> acceden a la funcionalidad a través del módulo Inventario y envío.
diff --git a/docs/tracks/es/go-live-process.md b/docs/tracks/es/go-live-process.md
index 48a052b79..50d061518 100644
--- a/docs/tracks/es/go-live-process.md
+++ b/docs/tracks/es/go-live-process.md
@@ -18,7 +18,7 @@ Si has [configurado el funcionamiento de tu tienda](https://help.vtex.com/pt/tra
 
 En este tutorial, encontrarás una guía detallada paso a paso sobre cómo realizar el _go live_ de tu tienda.
 
-![Go live](//images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/d2dcbd2093cd822624d8ed29642eae4e/go_live_es.jpg)
+![Go live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/d2dcbd2093cd822624d8ed29642eae4e/go_live_es.jpg)
 
 <div class = "alert alert-info">
 Ten en cuenta que una tienda en producción es diferente de una cuenta en producción. En general, se puede decir que para que una tienda esté en producción, es necesario poner la cuenta en producción y realizar el apuntamiento de DNS. Consulta todos los pasos de este proceso a continuación.
@@ -27,7 +27,7 @@ Ten en cuenta que una tienda en producción es diferente de una cuenta en produc
 ## Antes de comenzar
 Antes de realizar el go live de tu tienda, es importante garantizar que hayas completado todas las configuraciones necesarias para el buen funcionamiento de la tienda.
 
-Copia esta [Lista de verificación de tienda](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f254ea28c42f4fe323bb5ad29fd0da36/Lista_verificacion_tienda.xlsx) y comprueba, para cada ítem, si realizaste la configuración de acuerdo con el funcionamiento deseado de la tienda.
+Copia esta [Lista de verificación de tienda](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f254ea28c42f4fe323bb5ad29fd0da36/Lista_verificacion_tienda.xlsx) y comprueba, para cada ítem, si realizaste la configuración de acuerdo con el funcionamiento deseado de la tienda.
 
 <div class="alert alert-warning">
 La lista de verificación que se presenta aquí muestra las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. Tu equipo debe definir qué funcionalidades implementará en la tienda y cómo se deben configurar para crear la experiencia de tienda deseada. Esto significa que la lista no necesariamente incluye todas las funcionalidades que tu tienda utiliza. Sin embargo, es importante verificar todos los aspectos del funcionamiento de tu tienda aunque no estén en la lista sugerida.
diff --git a/docs/tracks/es/google-pay.md b/docs/tracks/es/google-pay.md
index 3df083e66..daa330e37 100644
--- a/docs/tracks/es/google-pay.md
+++ b/docs/tracks/es/google-pay.md
@@ -35,7 +35,7 @@ Para activar Google Pay, sigue los pasos a continuación.
 
 Una vez hecho esto, Google Pay estará disponible en el checkout de tu tienda VTEX como nuevo medio de pago. La configuración puede demorarse alrededor de 10 minutos en aparecer en el checkout.
 
-![google-pay-checkout-es](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b131b38fa81affd857db8c107278f3e9/Screenshot_2024-08-01_at_14.22.06.png)
+![google-pay-checkout-es](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b131b38fa81affd857db8c107278f3e9/Screenshot_2024-08-01_at_14.22.06.png)
 
 <div class = "alert alert-warning">
 <p>Google Pay, por el momento, no admite suscripciones.</p>
@@ -58,11 +58,11 @@ Para utilizar Google Pay deben cumplirse los siguientes requisitos:
 
 Para consultar y verificar las transacciones finalizadas con Google Pay, sigue los pasos indicados en el artículo [Ver detalles de la transacción](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy). En la barra de búsqueda de la página de transacciones, escriba **Google Pay** para filtrar las transacciones realizadas con este tipo de pago.
 
-![Google Pay Transaction_1](//images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/77ec267f3567f8d3988adf07c3a5d06a/Google_Pay_Transaction1_ES.png)
+![Google Pay Transaction_1](https://images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/77ec267f3567f8d3988adf07c3a5d06a/Google_Pay_Transaction1_ES.png)
 
 Después de acceder a la transacción deseada, haga clic en "+ Información" para verificar la información de **Google Pay** descrita en el campo `paymentOrigin`.
 
-![Google Pay Transaction_2](//images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/394481aab2e3d50703ab836080f1e1c9/Google_Pay_Transaction2_ES.png)
+![Google Pay Transaction_2](https://images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/394481aab2e3d50703ab836080f1e1c9/Google_Pay_Transaction2_ES.png)
 
 <div class="alert alert-warning">
   <p>También es posible identificar las transacciones realizadas con Google Pay a través de la página <b>Todos los pedidos</b> en Admin. Sólo necesitas seleccionar el periodo de búsqueda deseado, <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">exportar los pedidos</a> en un informe en formato . csv y localizar la información de Google Pay en el campo "payment origin".</p>
diff --git a/docs/tracks/es/google-shopping-marketplace.md b/docs/tracks/es/google-shopping-marketplace.md
index 93a24dbd8..81d2ea1e1 100644
--- a/docs/tracks/es/google-shopping-marketplace.md
+++ b/docs/tracks/es/google-shopping-marketplace.md
@@ -16,7 +16,7 @@ trackSlugES: integracion-con-google-shopping
 
 [Google Shopping](https://shopping.google.com/) es una plataforma en la que el producto aparece en listas gratis que son clasificadas orgánicamente en las búsquedas de Google. Es decir, es un servicio de comparación y seguimiento de precios que incluye sus productos de forma gratuita en los resultados de búsqueda de productos locales.
 
-![Google Shopping](//images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/1cd372670bd55e0dbf359984e058d81e/logo_Google_shopping.png)
+![Google Shopping](https://images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/1cd372670bd55e0dbf359984e058d81e/logo_Google_shopping.png)
 
 A través de Google Shopping, puede mostrar al consumidor algunos de los atributos de su producto, tales como imagen, título, precio y nombre de su tienda.
 
diff --git a/docs/tracks/es/hide-product-suggestions-recommendation.md b/docs/tracks/es/hide-product-suggestions-recommendation.md
index 33882651d..3f1a9add1 100644
--- a/docs/tracks/es/hide-product-suggestions-recommendation.md
+++ b/docs/tracks/es/hide-product-suggestions-recommendation.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 De forma predeterminada, inStore incluye una lista de productos sugeridos en el carrito y en la página de producto.
 
-![inStore recommendation](//images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
+![inStore recommendation](https://images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
 
 Si desea ocultar las recomendaciones, es necesario editar los archivos `checkout-instore-custom.css` y `checkout-instore-custom.js` presentes en el administrador del Portal. Por tratarse de archivos utilizados en diversos flujos de uso de la aplicación, es importante que usted tenga conocimientos de programación antes de cambiarlos, para evitar la ruptura de otras funcionalidades.
 
diff --git a/docs/tracks/es/how-a-split-payment-transaction-works.md b/docs/tracks/es/how-a-split-payment-transaction-works.md
index 4c0861e29..f7e5a41ce 100644
--- a/docs/tracks/es/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/es/how-a-split-payment-transaction-works.md
@@ -60,4 +60,4 @@ Aquellos USD 6,50 serían divididos entre el *marketplace* y adquirente. Como la
 
 Vea el siguiente gráfico: 
 
-![Split de pagos](//images.ctfassets.net/alneenqid6w5/1VXR6E7dDgMTTSBM0D6qyL/2900b47ba92432068e940c185088399b/Split-ES.png)
+![Split de pagos](https://images.ctfassets.net/alneenqid6w5/1VXR6E7dDgMTTSBM0D6qyL/2900b47ba92432068e940c185088399b/Split-ES.png)
diff --git a/docs/tracks/es/how-clustered-conditions-work.md b/docs/tracks/es/how-clustered-conditions-work.md
index b5fe5c0e4..ff903a858 100644
--- a/docs/tracks/es/how-clustered-conditions-work.md
+++ b/docs/tracks/es/how-clustered-conditions-work.md
@@ -26,7 +26,7 @@ De esta manera, las reglas de plazo y de pago en cuotas se aplicarán al consumi
 
 Para configurarlas, escoja una propiedad y, luego, seleccione los parámetros para crear un clúster.
 
-![Pagamentos Clusterizados_ES](//images.ctfassets.net/alneenqid6w5/9VBsI8vnkYsrpnKIQLE6C/9c4af9336f284033455bc20a66ad9225/image.png)
+![Pagamentos Clusterizados_ES](https://images.ctfassets.net/alneenqid6w5/9VBsI8vnkYsrpnKIQLE6C/9c4af9336f284033455bc20a66ad9225/image.png)
 
 ## Propiedad
 
diff --git a/docs/tracks/es/how-message-center-works.md b/docs/tracks/es/how-message-center-works.md
index 8557a9009..276edd55f 100644
--- a/docs/tracks/es/how-message-center-works.md
+++ b/docs/tracks/es/how-message-center-works.md
@@ -43,7 +43,7 @@ Al entrar en el Message Center y hacer clic en __Templates__, encontrará una li
 
 Comprendamos la información presente en estos cards.
 
-![Emails 1 1](//images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
+![Emails 1 1](https://images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
 
 - Nombre del template para identificación interna. Este *no* es el asunto del correo electrónico.  
 - Aplicación o módulo al que pertenece el template, indicado en verde.  
@@ -53,7 +53,7 @@ Comprendamos la información presente en estos cards.
   
 Para buscar templates, puede utilizar filtros por aplicación (módulo) y tipo (mensaje estándar o personalizado).
 
-![Emails 1 2](//images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
+![Emails 1 2](https://images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
 
 ### Remitentes
 
@@ -61,7 +61,7 @@ Aquí, el usuario verifica y edita la información - nombre, correo electrónico
 
 Esta es la información que se muestra en los cards de los remitentes:
 
-![Emails 1 3](//images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
+![Emails 1 3](https://images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
 
 - Nombre del remitente, para identificación interna.  
 - Tipo de servidor SMTP, que puede ser de VTEX o de la propia tienda.  
diff --git a/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md b/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md
index 3849fe664..77b680b94 100644
--- a/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md
+++ b/docs/tracks/es/how-to-change-the-sales-policy-used-by-instore.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 Si usted ha configurado su tienda utilizando el flujo de __Easy Setup__ ya se ha creado una tienda en el __Admin de tiendas__ dentro del VTable de VTEX (https://{{AccountName}}.myvtex.com/admin/vtable).
 
-![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Haga clic en __Admin de tiendas__ para abrir la tabla donde usted verá las tiendas físicas.
 
@@ -24,7 +24,7 @@ Si no ha utilizado el __Easy Setup__ y así no ve ninguna tienda registrada, cre
 
 Si ya ha registrado una tienda a través de __Easy Setup__, verá el registro de esta tienda creada como en la siguiente imagen.
 
-![vtable-admin-das-lojas-2](//images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
+![vtable-admin-das-lojas-2](https://images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
 
 Para cambiar cualquier dato, incluso la política comercial de la tienda, basta con cambiar la celda relacionada y luego hacer clic en el botón __Guardar__.
 
diff --git a/docs/tracks/es/how-to-configure-a-custom-payment.md b/docs/tracks/es/how-to-configure-a-custom-payment.md
index fc3b0f0b4..0e80695ee 100644
--- a/docs/tracks/es/how-to-configure-a-custom-payment.md
+++ b/docs/tracks/es/how-to-configure-a-custom-payment.md
@@ -36,7 +36,7 @@ Le permite usar una tarjeta de crédito de la tienda con una de las siguientes b
 3. Seleccione una de las opciones de pago personalizado.
 4. Complete los campos del formulario y haga clic en **Guardar**.
 
-![PT Pagamento Customizado](//images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
+![PT Pagamento Customizado](https://images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
 
 Después de esta configuración, deberá crear la [Condición de pago](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento/).  
 
diff --git a/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
index a3b6d4f11..50b4c0492 100644
--- a/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
@@ -16,7 +16,7 @@ trackSlugES: instore-setup
 
 Dentro de las opciones que ofrece **inStore** al momento de completar una venta, se encuentra una que permite imprimir el resumen del pedido.
 
-![ES-Venda confirmada](//images.ctfassets.net/alneenqid6w5/54Z1ETTtBXkSxJsWu16UKV/fe90bb4197cce83777fd9f4fee75bbd7/ES-Venda_confirmada.png)
+![ES-Venda confirmada](https://images.ctfassets.net/alneenqid6w5/54Z1ETTtBXkSxJsWu16UKV/fe90bb4197cce83777fd9f4fee75bbd7/ES-Venda_confirmada.png)
 
 Para configurar esta opción, serán necesarios dos pequeños pasos:
   1. Por el Admin VTEX, active la opción de configuración del dispositivo en el menú inStore.
@@ -29,7 +29,7 @@ Hoy, esta configuración está presente en el administrador del portal, más esp
 Para habilitar la opción _“Configurar dispositivo”_, debe encontrar el objeto **_window.INSTORE_CONFIG_** presente en este archivo y agregar la propiedad **_configureDeviceEnabled_** con el valor **_true_** y también agregar el objeto **_printingConfig_** a la propiedad **_printByBroker_** con el valor true, para que inStore permita utilizar la propiedad opción dentro del menú, como se muestra en la imagen de ejemplo a continuación:
 
 
-![ES-Configurar dispositivo](//images.ctfassets.net/alneenqid6w5/5alZn4GuAJkvZkEW7PkQE/5aef5e117ba6a20ae8ba6438e23e0f91/ES-Configurar_dispositivo.png)
+![ES-Configurar dispositivo](https://images.ctfassets.net/alneenqid6w5/5alZn4GuAJkvZkEW7PkQE/5aef5e117ba6a20ae8ba6438e23e0f91/ES-Configurar_dispositivo.png)
 
 No elimine ninguna de las otras propiedades presentes en este objeto, pero el resultado debería ser algo como:
 
@@ -64,11 +64,11 @@ printPageAutomatically: true
   2. Abra la aplicación inStore y entre a la tienda donde desea configurar la impresora.
   3. En el menú de inStore, en el bloque de “Configuraciones”, deberá aparecer la opción “Configurar dispositivo”. Haga clic allí.
 
-![ES-Barra inStore](//images.ctfassets.net/alneenqid6w5/1sluYEwdo4f01KnUyyEsoa/19344feb059bd03b316c37e2caed9ae0/ES-Barra_inStore.png)
+![ES-Barra inStore](https://images.ctfassets.net/alneenqid6w5/1sluYEwdo4f01KnUyyEsoa/19344feb059bd03b316c37e2caed9ae0/ES-Barra_inStore.png)
 
   4. Va a encontrar el resumen del dispositivo configurado. En caso de que sea la primera vez, las informaciones estarán vacías o, si ya se ha configurado un dispositivo previamente, van a aparecer algunas informaciones sobre el dispositivo _(Nombre del dispositivo e Impresora estándar)_. Haga clic en la opción “Editar”.
 
-![ES-Dispositivo via Broadcast](//images.ctfassets.net/alneenqid6w5/4KoNSOz0DB2KvXEyYcBiCd/668bc635360f6934f604ad1e53defddd/ES-Dispositivo_via_Broadcast.png)
+![ES-Dispositivo via Broadcast](https://images.ctfassets.net/alneenqid6w5/4KoNSOz0DB2KvXEyYcBiCd/668bc635360f6934f604ad1e53defddd/ES-Dispositivo_via_Broadcast.png)
 
   5. Aparecerá un formulario indicando los datos de _AppKey_,  _AppToken_ y el nombre con el que desee identificar el dispositivo. Luego de ingresar estos datos, haga clic en “Configurar”.
   6. Por último, al incluir los datos anteriores, será posible seleccionar la impresora en la lista de opciones. La idea es que sea seleccionada una de esas opciones y haga clic en “Configurar” nuevamente.
diff --git a/docs/tracks/es/how-to-register-your-salespersons-on-vtex-instore.md b/docs/tracks/es/how-to-register-your-salespersons-on-vtex-instore.md
index cc102b145..1ba4c3d34 100644
--- a/docs/tracks/es/how-to-register-your-salespersons-on-vtex-instore.md
+++ b/docs/tracks/es/how-to-register-your-salespersons-on-vtex-instore.md
@@ -24,19 +24,19 @@ El registro del vendedor deja la app tener una asociación del vendedor identifi
 2. Cargar los precios, condiciones de pago y disponibilidad del producto de la tienda de la que forma parte el dependiente.
 
 La identificación del vendedor se obtiene como muestra la siguiente imagen:
-![identificacao-vendedor](//images.contentful.com/alneenqid6w5/2LhlUtsEYouEY4i4iYOIOq/d556be06047c26ee85f392ba7256f9f8/identificacao-vendedor.png)
+![identificacao-vendedor](https://images.contentful.com/alneenqid6w5/2LhlUtsEYouEY4i4iYOIOq/d556be06047c26ee85f392ba7256f9f8/identificacao-vendedor.png)
 
 Para registrar los vendedores que la pantalla arriba permite identificar basta acceder a su Masterdata. Cuando haya accedido al Masterdata, usted deberá buscar el área con el título `Profile System`. En esa área encuentre la palabra `Vendedores` y haga clic en `listar` como muestra la imagen a continuación.
-![masterdata-home-vendedores](//images.contentful.com/alneenqid6w5/32iOuRESyIwEwSE4WcEWmu/b64645e6f940399933df3db5b40d6a4f/masterdata-home-vendedores.png)
+![masterdata-home-vendedores](https://images.contentful.com/alneenqid6w5/32iOuRESyIwEwSE4WcEWmu/b64645e6f940399933df3db5b40d6a4f/masterdata-home-vendedores.png)
 
 Cuando usted haga clic en `listar`, una lista de vendedores registrados va a aparecer, como muestra la imagen siguiente. Haga clic en `Novo` para registrar un nuevo vendedor.
-![masterdata-lista-vendedores](//images.contentful.com/alneenqid6w5/xsepOCP9Dwiys6MKkQGY4/4717c2ff41b7b52a43b549294877713f/masterdata-lista-vendedores.png)
+![masterdata-lista-vendedores](https://images.contentful.com/alneenqid6w5/xsepOCP9Dwiys6MKkQGY4/4717c2ff41b7b52a43b549294877713f/masterdata-lista-vendedores.png)
 
 Complete la información del vendedor en el formulario. En el campo `Loja`, usted debe comenzar a digitar el nombre de la tienda para que aparezca una caja de selección. Cuando aparezca el nombre de la tienda, haga clic en el nombre, verifique si toda la información está correcta y luego haga clic en `Salvar`.
-![masterdata-novo-vendedor](//images.contentful.com/alneenqid6w5/7mfVtDbemWWA6yqqYIQgwC/a498d9fbd2dcfbe87546711d8d8c7a36/masterdata-novo-vendedor.png)
+![masterdata-novo-vendedor](https://images.contentful.com/alneenqid6w5/7mfVtDbemWWA6yqqYIQgwC/a498d9fbd2dcfbe87546711d8d8c7a36/masterdata-novo-vendedor.png)
 
 También será necesario configurar um perfil de acceso para ese vendedor en su License Manager. Basta hacer clic en `Usuarios` y crear un nuevo con el mismo email que fue puesto en el Masterdata, el Perfil de Acceso que debe adicionarse es el `Vendedor inStore` y después recuerde de hacer clic en `Salvar`.
 
 *Nuevos vendedores deberán crear y confirmar su contraseña a través de un email enviado a cada usuario registrado.*
 
-![license-manager-novo-vendedor](//images.contentful.com/alneenqid6w5/98ppRH68esOwU2cWSiM4w/501c79f9cc247103868a026581f7573c/license-manager-novo-vendedor.png)
+![license-manager-novo-vendedor](https://images.contentful.com/alneenqid6w5/98ppRH68esOwU2cWSiM4w/501c79f9cc247103868a026581f7573c/license-manager-novo-vendedor.png)
diff --git a/docs/tracks/es/including-order-variables-in-email-template.md b/docs/tracks/es/including-order-variables-in-email-template.md
index aaf183022..88578d278 100644
--- a/docs/tracks/es/including-order-variables-in-email-template.md
+++ b/docs/tracks/es/including-order-variables-in-email-template.md
@@ -30,7 +30,7 @@ Supongamos que desea ingresar el nombre de la transportadora en el correo electr
 
 Para hacer esto, entre en el template de pedido enviado y, en el campo __JSON Data__, busque la propiedad `courier`.
 
-![EN Incluir variáveis do pedido no template de e-mail - 1](//images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/a8060a2a2c8dca9887178af7d6c97812/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)  
+![EN Incluir variáveis do pedido no template de e-mail - 1](https://images.ctfassets.net/alneenqid6w5/3lkYWEKSwjz99oSGDCpapE/a8060a2a2c8dca9887178af7d6c97812/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_1.png)  
 
 El valor ingresado para esta propiedad es apenas un ejemplo, pero puede usarlo en el campo __HTML__ para que, cuando se envíe el correo electrónico, el cliente vea la transportadora de hecho responsable de entregar el pedido.
 
@@ -39,7 +39,7 @@ Tenga en cuenta que la propiedad `courier` está dentro del objeto `package`. Po
 `{{package.courier}}`
 
 
-![EN Incluir variáveis do pedido no template de e-mail - 2](//images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/f3e8ee4de1d2a5d5a46c0385660a9c67/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)  
+![EN Incluir variáveis do pedido no template de e-mail - 2](https://images.ctfassets.net/alneenqid6w5/5MhBjWokAHVHZKXgvswn6X/f3e8ee4de1d2a5d5a46c0385660a9c67/EN_Incluir_vari__veis_do_pedido_no_template_de_e-mail_-_2.png)  
 
 
 Vea que el valor de ejemplo  ("Transportadora Teste Courier S.A.") fue ingresado en la pantalla de preview, debajo de los campos __HTML__ y __JSON Data__. 
diff --git a/docs/tracks/es/indexing-history.md b/docs/tracks/es/indexing-history.md
index 2781b2d91..9ae8a5a9a 100644
--- a/docs/tracks/es/indexing-history.md
+++ b/docs/tracks/es/indexing-history.md
@@ -16,12 +16,12 @@ trackSlugES: vtex-intelligent-search
 
 El **Historial de indexación** es la página que monitorea el estado de sincronización de todos los productos del catálogo que se envían a Intelligent Search. Allí se puede ver ampliamente el progreso de la indexación de tu tienda.
 
-![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+![Histórico da Indexação 1 - ES](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
 
 La sección **Status de la indexación** muestra la siguiente información:
 
 * **Tiempo promedio de indexación:** tiempo promedio para la indexación de los productos, desde el momento en que el sistema recibió la notificación de un cambio, hasta la actualización en la tienda. El desempeño del tiempo de indexación se mide por un punto verde (saludable) o rojo (no saludable). 
-![Historico Indexação 2 - ES](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
+![Historico Indexação 2 - ES](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
 * **Productos en tienda:** cantidad de productos con información actualizada que se muestran actualmente en la tienda.
 * **División de status de indexación:** porcentaje de productos en cada etapa de indexación. El desempeño de los estados compartidos se mide por un punto verde (saludable) o rojo (no saludable). Las etapas que se muestran son:
     * **Actualizado:** la actualización más reciente del producto que se introdujo en la tienda.
@@ -32,15 +32,15 @@ Puedes filtrar la lista de productos indexados para tener una vista personalizad
 
 Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
 
 Si filtras por `Status`, puedes seleccionar el estado por el que deseas filtrar: `Actualizado`, `Actualizando`, `Error`.
 
-![Historico indexação 4 - ES](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
+![Historico indexação 4 - ES](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
 
 Si filtras por `Tiempo de indexación`, puedes seleccionar si el intervalo de tiempo `Es mayor que`, `Es igual o mayor que`, `Es menor que` o `Es igual o menor que` un horario definido.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
 
 Luego de definir el filtro, haz clic en `Aplicar` para activarlo. 
 
@@ -50,17 +50,17 @@ También puedes filtrar los productos exhibidos en la lista por **ID**, **Últim
 
 Si deseas obtener más información sobre la indexación de un producto específico, puedes hacer clic en la línea del producto en la lista para acceder a una ventana con más detalles, tal como se muestra a continuación.
 
-![Historico indexação 6 - ES](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
+![Historico indexação 6 - ES](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
 
 Además de los datos que se muestran en la lista de productos, también puedes ver:
 
 * **Tiempo de indexación:** registro de cuánto tiempo duró la última actualización del producto, en el formato `hh:mm:ss`.
 * **Cronología de indexación:** registro de cada cambio de estado con fecha y hora. Puedes ver más detalles de cada etapa haciendo clic en el ícono <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - ES](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
+![Historico indexação 7 - ES](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
 
 Puedes reindexar un producto manualmente sin tener que ingresar una actualización en su registro. Para reindexar un producto, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Reintentar la indexación`. Solo se pueden reindexar los productos en el estado **Actualizado**.
 
 Puedes acceder al **Historial de indexación** del producto, una lista con los datos y la hora de cada actualización realizada. De esta manera, puedes llevar un registro de todas las modificaciones que se le hicieron al producto. Para acceder al historial, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Historial`. 
 
-![Histórico da Indexação 8 - ES](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
+![Histórico da Indexação 8 - ES](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
diff --git a/docs/tracks/es/initializing-your-store-theme.md b/docs/tracks/es/initializing-your-store-theme.md
index feb01ab9d..8369c048d 100644
--- a/docs/tracks/es/initializing-your-store-theme.md
+++ b/docs/tracks/es/initializing-your-store-theme.md
@@ -28,7 +28,7 @@ Seleccione `store-theme` y confirme que desea descargar el proyecto template en
 
 Usted recibirá información importante sobre la aplicación, como el vendor, el nombre, el título y la descripción de la app. Utilice el __account name__ de la tienda que está desarrollando como el __vendor__. Esto es importante para que posteriormente pueda publicar correctamente esta aplicación en esta cuenta. Para utilizar los valores predeterminados, simplemente presione Enter.
 
-![store-theme](//images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
+![store-theme](https://images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
 
 ## Entendiendo la estructura de la app
 
@@ -88,7 +88,7 @@ Durante un "link", todos los cambios realizados en su código se envían automá
 
 Ejecute `vtex link` y vea que su aplicación de ejemplo se compila y se publica en la cuenta y en el workspace que acaba de crear.
 
-![vtex-link](//images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
+![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
 <div class="alerta alerta-info">
 Recuerde: ejecute <code>vtex whoami</code> para asegurarse de que está en la cuenta correcta y en un workspace de prueba. De lo contrario, el <code>VTEX Toolbelt</code> se queja del link directo con master.
@@ -106,4 +106,4 @@ El `{{account}}.myvtex.com` es su dominio privado destinado a probar nuevos work
 
 Felicitaciones por hacer el link de su primera app en VTEX IO!
 
-![dreamstore](//images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
+![dreamstore](https://images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
diff --git a/docs/tracks/es/inserting-and-configuring-placeholders.md b/docs/tracks/es/inserting-and-configuring-placeholders.md
index 7e501b40c..c78788087 100644
--- a/docs/tracks/es/inserting-and-configuring-placeholders.md
+++ b/docs/tracks/es/inserting-and-configuring-placeholders.md
@@ -34,7 +34,7 @@ Lo que hace es crear un elemento configurable en el lugar del código donde se i
 
 Es importante ingresar un valor de `id`. Este será el identificador para este placeholder en el sistema.
 
-![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando el placeholder
 
@@ -42,7 +42,7 @@ Ahora que el control de placeholder se ha ingresado en el template, vamos a conf
 
 Esto se hace en las configuraciones del layout que utiliza este template.
 
-1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para ingresar un objeto, haga clic en **add object**. 
 3. A continuación, seleccione el tipo de objeto y haga clic en **Añadir**.
 4. Finalmente, haga clic en el botón  **Save Settings**, en la parte superior de la página.
@@ -51,7 +51,7 @@ Ahora puede editar el objeto que ha ingresado en el placeholder.
 
 Para esto, haga clic en el lápiz que se encuentra dentro del objeto y, a continuación, haga clic en **add content**.
 
-![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Ahora puede definir el nombre de este objeto, subir imágenes y configurar las condiciones en las que se renderizará, tales como el período. 
 
diff --git a/docs/tracks/es/instore-basic-settings.md b/docs/tracks/es/instore-basic-settings.md
index d0c0437ae..c2b2b7964 100644
--- a/docs/tracks/es/instore-basic-settings.md
+++ b/docs/tracks/es/instore-basic-settings.md
@@ -54,7 +54,7 @@ Después de la instalación, deberás realizar la configuración básica de la a
 
 ### Registrar la dirección de la tienda
 
-![cadastrar-loja-pt](//images.contentful.com/alneenqid6w5/51ICHIzuWsMAwPCVwQuQoB/071ec5240f968e662badf4e828954072/cadastrar-loja-pt.png)
+![cadastrar-loja-pt](https://images.contentful.com/alneenqid6w5/51ICHIzuWsMAwPCVwQuQoB/071ec5240f968e662badf4e828954072/cadastrar-loja-pt.png)
 
 En esta página, introduce el nombre de la primera tienda física donde se utilizará VTEX Sales App y la dirección completa de la tienda. Cuando hayas rellenado todos los campos, haz clic en `Confirmar`.
 
@@ -64,7 +64,7 @@ Si decides `Saltar este paso`, se creará una tienda ficticia con fines de prueb
 
 ### Registrar el email y el nombre del vendedor
 
-![registrar-vendedor-pt](//images.contentful.com/alneenqid6w5/5PvZutdPYWkm7rj4HCrlPC/0316ea7fd74dae942a64e5fdb22f3807/registrar-vendedor-pt.png)
+![registrar-vendedor-pt](https://images.contentful.com/alneenqid6w5/5PvZutdPYWkm7rj4HCrlPC/0316ea7fd74dae942a64e5fdb22f3807/registrar-vendedor-pt.png)
 
 Es necesario registrar un email y un nombre que se utilizarán como credenciales de inicio de sesión del vendedor. Haz clic en `Confirmar`.
 
@@ -80,7 +80,7 @@ Si decides `Saltar este paso`, se creará un vendedor ficticio con el email `ins
 
 El siguiente paso es configurar los métodos de pago que aceptarás en VTEX Sales App. Activa las opciones deseadas utilizando el botón <i class="fas fa-toggle-on"></i> como se ilustra a continuación.
 
-![configurar-meios-de-pagamento-pt](//images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
+![configurar-meios-de-pagamento-pt](https://images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
 
 Hay dos opciones:
 
@@ -89,7 +89,7 @@ Hay dos opciones:
 
 Después de seleccionar las opciones deseadas, haz clic en `Confirmar`. Verás el siguiente mensaje de confirmación:
 
-![sucesso-instore-pt](//images.contentful.com/alneenqid6w5/nVSjiQuE0EXIYecELJJFQ/79a0d24adb51e7ad68f371afe5ca0491/sucesso-instore-pt.png)
+![sucesso-instore-pt](https://images.contentful.com/alneenqid6w5/nVSjiQuE0EXIYecELJJFQ/79a0d24adb51e7ad68f371afe5ca0491/sucesso-instore-pt.png)
 
 ## Configurar condiciones de pago
 
diff --git a/docs/tracks/es/instore-customizations.md b/docs/tracks/es/instore-customizations.md
index 9fa24db18..4c15746b3 100644
--- a/docs/tracks/es/instore-customizations.md
+++ b/docs/tracks/es/instore-customizations.md
@@ -36,11 +36,11 @@ Alternativamente, puede buscar el archivo de configuración desde la página de
 
 En el menú principal, haga clic en __Checkout__ y luego haga clic en el símbolo de engranaje de la tienda, como se muestra en la imagen a continuación.
 
-![20. inStore Customizations - 1 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/4EDg8NKDGXRYEG6C8t6TjM/5e7c8c88e79ad04b7c6b0a31795a0b20/20._inStore_Customizations_-_1_-_ES.png_h_250)
+![20. inStore Customizations - 1 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/4EDg8NKDGXRYEG6C8t6TjM/5e7c8c88e79ad04b7c6b0a31795a0b20/20._inStore_Customizations_-_1_-_ES.png_h_250)
 
 Haga clic en la pestaña __Código__ y luego en el archivo `checkout-instore-custom.js`, que se encuentra en la lista de archivos a la derecha.
 
-![20. inStore Customizations - 2 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/6mGe02KwVH7z0HGy6UpgKQ/6d4d983a3aa4bf7e3ec98540b3bc23f0/20._inStore_Customizations_-_2_-_ES.png_h_250)
+![20. inStore Customizations - 2 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/6mGe02KwVH7z0HGy6UpgKQ/6d4d983a3aa4bf7e3ec98540b3bc23f0/20._inStore_Customizations_-_2_-_ES.png_h_250)
 
 ## Cambiar el archivo de personalización del inStore
 
@@ -48,7 +48,7 @@ Haga clic en la pestaña __Código__ y luego en el archivo `checkout-instore-cus
 
 Para realizar cualquier cambio, simplemente agregue o modifique las líneas de código directamente en el cuadro de edición de archivos, en el Admin de VTEX, y finalmente haga clic en el botón __Guardar__, como se muestra en la imagen a continuación.
 
-![20. inStore Customizations - 3 - ES.png?h=250](//images.ctfassets.net/alneenqid6w5/7xWS4qln2lhLN1CgM9VwOy/69495b399f32730531e0b8eb553d6d94/20._inStore_Customizations_-_3_-_ES.png_h_250)
+![20. inStore Customizations - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7xWS4qln2lhLN1CgM9VwOy/69495b399f32730531e0b8eb553d6d94/20._inStore_Customizations_-_3_-_ES.png_h_250)
 
 <div class="alert alert-warning">
 Siga siempre las instrucciones de personalización en esta documentación y realice solo los cambios como se indica aquí.
diff --git a/docs/tracks/es/instore-login.md b/docs/tracks/es/instore-login.md
index 3f2e62335..bd95a70cc 100644
--- a/docs/tracks/es/instore-login.md
+++ b/docs/tracks/es/instore-login.md
@@ -18,7 +18,7 @@ El primer contacto entre el vendedor de la tienda física y el VTEX Sales App se
 
 Aquí, se debe utilizar el correo electrónico y la contraseña creados para el vendedor en el paso de [Configuración Básica](https://help.vtex.com/es/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO#adding-a-sales-associates-email-and-name). Recuerde que no está permitido usar correos electrónicos que ya tengan acceso al panel administrativo de las tiendas VTEX.
 
-![instore-login-PT](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/1e7ad4161b3afa2b048b4166e26a240a/instore-login-PT.png)
+![instore-login-PT](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/1e7ad4161b3afa2b048b4166e26a240a/instore-login-PT.png)
 
 Al iniciar sesión, el vendedor accede al VTEX Sales App específico de una cuenta VTEX. Aunque no es un escenario común, el mismo vendedor puede estar vinculado a más de una cuenta. Si necesita cambiar de cuenta, simplemente cierre sesión y, en la pantalla de inicio de sesión, haga clic en `Cambiar tienda`.
 
diff --git a/docs/tracks/es/instore.md b/docs/tracks/es/instore.md
index 93d801a57..d723dff92 100644
--- a/docs/tracks/es/instore.md
+++ b/docs/tracks/es/instore.md
@@ -24,7 +24,7 @@ El primer contacto entre el vendedor de la tienda física y el inStore se produc
 
 Aquí, se debe utilizar el correo electrónico y la contraseña creados para el vendedor en el paso de [Configuración Básica](https://help.vtex.com/es/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO). Recuerde que no está permitido usar correos electrónicos que ya tengan acceso al panel administrativo de las tiendas VTEX.
 
-![31. inStore - Product Overview - 1 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
+![31. inStore - Product Overview - 1 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/608f3fa8cef774bee9106a997de71567/31._inStore_-_Product_Overview_-_1_-_EN.png_h_250)
 
 Al iniciar sesión, el vendedor accede al inStore específico de una cuenta VTEX. Aunque no es un escenario común, el mismo vendedor puede estar vinculado a más de una cuenta. Si necesita cambiar de cuenta, simplemente cierre sesión y, en la pantalla de inicio de sesión, haga clic en __Cambiar tienda__.
 
@@ -46,7 +46,7 @@ Usted puede [configurar qué métodos de identificación desea habilitar](https:
 
 En el ejemplo de la imagen a continuación, E-mail y CPF están habilitados.
 
-![31. inStore - Product Overview - 2 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
+![31. inStore - Product Overview - 2 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/f15d5d5556b31f7ce78eb3d77994c722/31._inStore_-_Product_Overview_-_2_-_EN.png_h_250)
 
 Ingrese uno de estos datos en el campo y haga clic en el botón __Confirmar__.
 
@@ -60,11 +60,11 @@ Aunque es posible atender a los clientes sin identificarlos, siempre recomendamo
 
 La barra superior de la aplicación de inStore ofrece algunas opciones utilizadas frecuentemente por el vendedor. Una de ellas es la búsqueda de SKU, disponible en la esquina superior derecha.
 
-![31. inStore - Product Overview - 3 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
+![31. inStore - Product Overview - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5zBP54Dt2s7P6514vC1K8z/f0680a6383e525a329089eb247501d4d/31._inStore_-_Product_Overview_-_3_-_EN.png_h_250)
 
 La búsqueda de inStore es omnicanal. Es decir, cuando realiza una búsqueda en la aplicación, el vendedor busca tanto en el stock local (de la tienda física en sí) como en el catálogo de otras tiendas físicas y del e-commerce.
 
-![31. inStore - Product Overview - 4 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
+![31. inStore - Product Overview - 4 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5jBZMQOVW1n0ObtiwMYDtV/37bc53a81fea4d2db3cc61e5ccc0dd51/31._inStore_-_Product_Overview_-_4_-_EN.png_h_250)
 
 Las opciones de disponibilidad de entrega y recogida se mostrarán más adelante, en la etapa de entrega.
 
@@ -72,11 +72,11 @@ Las opciones de disponibilidad de entrega y recogida se mostrarán más adelante
 
 Después de identificar al cliente, el vendedor es llevado directamente al carrito. Allí, si está utilizando la versión para computadora de inStore, conectada a un lector de código de barras, simplemente lea los productos para que aparezcan en el carrito.
 
-![31. inStore - Product Overview - 5 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
+![31. inStore - Product Overview - 5 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5QbuILII93SyE4j7ovXed5/0390993518b96fb07f68c19345470413/31._inStore_-_Product_Overview_-_5_-_EN.png_h_250)
 
 Si el vendedor está usando un tablet o smartphone, verá un botón de lectura de código de barras en la barra superior de la aplicación.
 
-![31. inStore - Product Overview - 6 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
+![31. inStore - Product Overview - 6 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/b1b41cfb9a3cfb9266383011e793c175/31._inStore_-_Product_Overview_-_6_-_EN.png_h_250)
 
 Al hacer clic en él, el vendedor puede usar la cámara para emitir leer un producto y, con eso, pasar automáticamente a la pantalla de detalles de ese producto.
 
@@ -119,7 +119,7 @@ Es bueno recordar que toda esta información se refiere no solo a la experiencia
 
 Al hacer clic en los detalles de un producto que aparece en los resultados de búsqueda de inStore, o al leer el código de un producto, el vendedor se dirige a la pantalla de detalles del producto.
 
-![31. inStore - Product Overview - 7 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
+![31. inStore - Product Overview - 7 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/52e0133e7222676d105e4444ce83ea96/31._inStore_-_Product_Overview_-_7_-_EN.png_h_250)
 
 Esta pantalla muestra el nombre del producto, su galería de fotos, variaciones, descripción y disponibilidad. El vendedor puede, en esta pantalla, agregar el producto al carrito.
 
@@ -137,7 +137,7 @@ InStore permite [habilitar una funcionalidad de transferencia de carrito](https:
 
 Una vez en un carrito, el vendedor tiene acceso al botón __Transferir__. Al hacer clic en este botón, la aplicación muestra un código QR y un código numérico de cuatro dígitos.
 
-![31. inStore - Product Overview - 8 - EN.png?h=250](//images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
+![31. inStore - Product Overview - 8 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/4DIaRH9gE7NVSsFMQINg4x/2531727e3528f275e02919c9939c5c09/31._inStore_-_Product_Overview_-_8_-_EN.png_h_250)
 
 Otro vendedor vinculado a la misma tienda puede capturar ese carrito y continuar la venta desde su dispositivo.
 
@@ -155,21 +155,21 @@ La siguiente pantalla muestra las opciones de entrega. Como inStore tiene acceso
 
 El siguiente ejemplo muestra dos opciones: recibir todos los artículos en casa a través de una entrega económica o recogerlos en otra tienda física dentro de 5 días hábiles.
 
-![31. inStore - Product Overview - 10](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
+![31. inStore - Product Overview - 10](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
 
 ### Puntos de recogida
 
 Para los puntos de recogida, el sistema selecciona las tiendas que tienen los SKUs en stock y muestra la tienda más cercana al código postal del cliente, como sugerencia. Si el vendedor quiere cambiar la tienda donde el cliente recogerá los productos, solo hay que hacer clic en el botón __Cambiar punto de recogida__.
 
-![31. inStore - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
+![31. inStore - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
 
 Al hacer clic en ese botón, el vendedor primero tiene acceso al punto de recogida sugerido por el sistema. Para ver todos los puntos de recogida disponibles, hay que hacer clic en __Ver todos los puntos de recogida__.
 
-![31. inStore - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
+![31. inStore - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
 
 La aplicación mostrará la lista de puntos de recogida ordenados por la distancia más corta desde el código postal del cliente. También es posible elegir el punto de recogida en el mapa.
 
-![31. inStore - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
+![31. inStore - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
 
 ## 12. Pago
 
@@ -177,17 +177,17 @@ En el paso de pago, las [opciones de pago que se han configurado](https://help.v
 
 Una feature importante permitida por inStore son los pagos múltiples. Por ejemplo, al elegir Efectivo y luego hacer clic en __Agregar otro pago__, el vendedor puede cobrar parte del importe en efectivo y parte con tarjeta de crédito.
 
-![31. inStore - Product Overview - 14](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
+![31. inStore - Product Overview - 14](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
 
 La barra superior de la pantalla de pago le permite agregar cupones y gift cards. También permite cambiar el número de identificación del cliente que aparecerá en la factura.
 
-![31. inStore - Product Overview - 15](//images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
+![31. inStore - Product Overview - 15](https://images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
 
 ## 13. Pedido completado
 
 El vendedor puede ver esta misma pantalla haciendo clic en __Pedidos completos__ en el menú principal de inStore, y buscando el pedido por número de pedido o cliente.
 
-![31. inStore - Product Overview - 16](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
+![31. inStore - Product Overview - 16](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
 
 ## 14. Impresión de factura
 
diff --git a/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
index d75aefb8a..1f338c15f 100644
--- a/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
@@ -16,7 +16,7 @@ trackSlugES: integrar-el-instore-a-un-nuevo-adquirente-de-pago
 
 Este artículo tiene como objetivo explicar cómo la aplicación de inStore configura el AppLinking para las acciones de `payment` y `payment-reversal` con las apps de los adquirentes.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuración
 
diff --git a/docs/tracks/es/integration-configurations.md b/docs/tracks/es/integration-configurations.md
index 39318f1f5..04e4d65f5 100644
--- a/docs/tracks/es/integration-configurations.md
+++ b/docs/tracks/es/integration-configurations.md
@@ -21,7 +21,7 @@ Los siguientes pasos deben realizarse dentro de la app.
 1. En el selector, escoja la política comercial que se utilizará en Wish ([predefinida en el paso 2](https://help.vtex.com/es/tracks/configurar-integracao-da-wish--50hbG4bzhSIhjz1lzqI1g43OHGQIQmt1dKw9RwKruE7H#definindo-politica-comercial))
 2. Después de seleccionar la política comercial, haga clic en "Continuar".
 
-![PT - Configurar Wish](//images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
+![PT - Configurar Wish](https://images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
 
 ## Configuraciones de envío 
 
diff --git a/docs/tracks/es/integration-settings.md b/docs/tracks/es/integration-settings.md
index bd2319929..b32013246 100644
--- a/docs/tracks/es/integration-settings.md
+++ b/docs/tracks/es/integration-settings.md
@@ -24,6 +24,6 @@ Sigue las instrucciones a continuación para iniciar el proceso de integración:
 
 Se dará inicio al proceso de indexación. Una vez completado, se mostrará la siguiente pantalla:
 
-![integracoes-es](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/0e53cf7952ac60b089bbcb5f6441640e/integracoes-es.PNG)
+![integracoes-es](https://images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/0e53cf7952ac60b089bbcb5f6441640e/integracoes-es.PNG)
 
 No es necesario repetir este proceso. Una vez iniciada la integración, puedes realizar un seguimiento del status de indexación en la página [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tracks/es/intelligent-synonyms.md b/docs/tracks/es/intelligent-synonyms.md
index 222d22031..769155017 100644
--- a/docs/tracks/es/intelligent-synonyms.md
+++ b/docs/tracks/es/intelligent-synonyms.md
@@ -31,7 +31,7 @@ Las sugerencias se muestran en dos categorías en la lista de sinónimos, como s
 * **Nuevas sugerencias:** son aquellas generadas por la plataforma que aún no se han revisado.
 * **Sugerencias guardadas:** son aquellas que se guardaron para su posterior revisión, tal como se describe en el paso 5 de la sección [Revisar sugerencias](#revisar-sugestoes).
 
-![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
+![synonym-suggestion-list-es](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
 
 Puedes revisar las sugerencias generadas y elegir guardar para más tarde, rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
 
@@ -47,7 +47,7 @@ Sigue las instrucciones para visualizar las sugerencias de sinónimos y definir
 
 4. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
 
-   ![synonym-suggestion-es](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
+   ![synonym-suggestion-es](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
 
 4. Para revisar cada sugerencia, elige una de las siguientes opciones:
     * <i class="fas fa-bookmark"></i> **Guardar para más tarde:** remueve la sugerencia del recuento **Nuevas sugerencias** y la almacena en **Sugerencias guardadas**. Para analizarla posteriormente, haz clic en `Revisar`.
diff --git a/docs/tracks/es/intro-to-vtex-io-builders.md b/docs/tracks/es/intro-to-vtex-io-builders.md
index 9a9f543d7..86ff2b8f4 100644
--- a/docs/tracks/es/intro-to-vtex-io-builders.md
+++ b/docs/tracks/es/intro-to-vtex-io-builders.md
@@ -19,6 +19,6 @@ Las apps de VTEX IO exportan código o configuración para proporcionar features
 Estos pedazos de código y configuración generalmente requieren alguna preparación o validación para servir a su propósito. Por ejemplo, los componentes React deben tener sus dependencias extraídas y compiladas en paquetes JavaScript.
 
 El VTEX IO se encarga automáticamente de todos estos pasos, implementándolos como builders. Una vez que su app declara que utiliza un builder, la carpeta correspondiente y su contenido son procesados por él cuando se realiza el link.
-![builders](//images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
+![builders](https://images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
 
 El proyecto store theme utiliza dos builders principales (`store` y `styles`), pero a medida que cree apps con funciones más avanzadas, usted comenzará a usar otros builders de nivel más bajo, como `react`, `messages`, `graphql` y `node`.
diff --git a/docs/tracks/es/introduction-to-vtex-io.md b/docs/tracks/es/introduction-to-vtex-io.md
index 7d5c57d32..694c8bbd3 100644
--- a/docs/tracks/es/introduction-to-vtex-io.md
+++ b/docs/tracks/es/introduction-to-vtex-io.md
@@ -22,7 +22,7 @@ En esta track, vamos a enseñar paso a paso cómo desarrollar una aplicación ut
 
 En la siguiente imagen se muestra la estructura jerárquica del VTEX IO:
 
-![VTEX IO Hierarchy](//images.ctfassets.net/alneenqid6w5/41yNT81ioog0yMeq0wMKM4/86005dd6b0cee4548e16133acfb8b6fe/VTEX_IO_Hierarchy.jpg)
+![VTEX IO Hierarchy](https://images.ctfassets.net/alneenqid6w5/41yNT81ioog0yMeq0wMKM4/86005dd6b0cee4548e16133acfb8b6fe/VTEX_IO_Hierarchy.jpg)
 
 - __Account__: para desarrollar una aplicación, es necesario tener una cuenta en VTEX.
 - __Workspaces__: son los ambientes donde las aplicaciones serán desarrolladas. Estos ambientes están vinculados a la cuenta. Es posible que haya varios workspaces para una sola cuenta.
diff --git a/docs/tracks/es/introduction-to-vtex.md b/docs/tracks/es/introduction-to-vtex.md
index 37325723f..f11862b2c 100644
--- a/docs/tracks/es/introduction-to-vtex.md
+++ b/docs/tracks/es/introduction-to-vtex.md
@@ -18,7 +18,7 @@ trackSlugES: serie-de-la-tienda-vtex
 
 La imagen a continuación muestra las soluciones y posibilidades de VTEX, que se tratarán a lo largo de esta serie de artículos:
 
-![vtex_composable_complete_ES](//images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/80e21dd3aebbe2c74c752b8d61d7a2f9/vtex_composable_complete_ES.png)
+![vtex_composable_complete_ES](https://images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/80e21dd3aebbe2c74c752b8d61d7a2f9/vtex_composable_complete_ES.png)
 
 <div class="alert alert-info">
 Además de los portales Help Center y <a href="https://developers.vtex.com/">Developer Portal</a> y <a href="https://community.vtex.com/">VTEX Community</a>, en nuestro <a href="https://vtex.com/co-es/">sitio web</a>ofrecemos más información sobre la plataforma a través de <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">videos explicativos</a> (solo en inglés) y <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> creados por nuestros <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">partners</a>. También ponemos a disposición una serie de <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">videos de onboarding</a> (solamente en portugués).
diff --git a/docs/tracks/es/inventory-and-shipping-module-overview.md b/docs/tracks/es/inventory-and-shipping-module-overview.md
index e81371a47..1fee9e258 100644
--- a/docs/tracks/es/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/es/inventory-and-shipping-module-overview.md
@@ -23,7 +23,7 @@ El módulo __Inventario y Envío__ es el servicio responsable de la *logística*
 El sistema de logística tiene diversas funcionalidades útiles. Estas *features* le permiten crear una estrategia de inventario y envío que se adecue mejor a su negocio. En los próximos pasos de esta guía, veremos cómo utilizar cada una de las funcionalidades que se muestran a continuación. En el Admin de su tienda, encontrará las siguientes secciones:
 
 
-![inventory-shipping-admin-es](//images.ctfassets.net/alneenqid6w5/jUIsT8CjbAP2O637yW3Mu/d68d30481a1e37d708a92881a227fb52/inventory-shipping-admin-es.png)
+![inventory-shipping-admin-es](https://images.ctfassets.net/alneenqid6w5/jUIsT8CjbAP2O637yW3Mu/d68d30481a1e37d708a92881a227fb52/inventory-shipping-admin-es.png)
 
 __Estrategia de Envío__ (Paneles) - En esta sección, debe registrar las rutas logísticas que realizan la entrega de sus pedidos. Una ruta básica se compone de un __stock__, un __muelle__ y una __política de envío__ (transportadora).
 
diff --git a/docs/tracks/es/legacy-cms-portal.md b/docs/tracks/es/legacy-cms-portal.md
index 81346c920..571567874 100644
--- a/docs/tracks/es/legacy-cms-portal.md
+++ b/docs/tracks/es/legacy-cms-portal.md
@@ -18,7 +18,7 @@ trackSlugES: cms
 
 La sección [Layout](https://help.vtex.com/es/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW) te permite crear tu storefront con HTML y CSS. Se organiza en carpetas y archivos con fines específicos:
 
-![CMS - Layout ES](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
+![CMS - Layout ES](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/b79de6b1ecd88c672cd7f004666e4106/cms-layout-es.png)
 
 - **HTML Templates:** construye el código HTML y los archivos JavaScript y CSS de referencia que se utilizarán en las páginas del sitio web.
 
@@ -38,7 +38,7 @@ La sección [Layout](https://help.vtex.com/es/subcategory/layout--2g6LxtasS4iSeG
 
 La sección [Configuración](https://help.vtex.com/es/subcategory/configuracion-de-cms--6kovkwzMRyeOOc2iEC4suM) te permite configurar los ajustes relacionados con el sitio web de tu tienda, como sus metadatos, las etiquetas SEO, los tipos de archivo, etc. 
 
-![CMS - Settings ES](//images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/68fd8114fc801d74c45f115716d2a73e/cms-settings-es.png)
+![CMS - Settings ES](https://images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/68fd8114fc801d74c45f115716d2a73e/cms-settings-es.png)
 
 La sección **Configuración** está estructurada de la siguiente manera:
 
@@ -69,7 +69,7 @@ Toda tienda debe tener, sin excepción, las siguientes carpetas en el CMS para a
 
 Vea abajo estas carpetas básicas en el CMS:
 
-![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas carpetas vienen de forma predeterminada en el ambiente de todas las tiendas VTEX.
 
diff --git a/docs/tracks/es/live-support.md b/docs/tracks/es/live-support.md
index 43c85f430..8c5484cc0 100644
--- a/docs/tracks/es/live-support.md
+++ b/docs/tracks/es/live-support.md
@@ -29,12 +29,12 @@ Para configurar los horarios en los que el servicio estará disponible, sigue lo
 
 1. Define si quieres activar el Servicio al cliente humano en tu tienda.
 
-![Live Support es](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/3b266be75366e3db076799ba968028ca/configuracion_general.png)
+![Live Support es](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/3b266be75366e3db076799ba968028ca/configuracion_general.png)
 Si eliges no utilizarlo, debes incluir un mensaje de indisponibilidad que indique el canal de atención al cliente.
-![Mensagem de indisponibilidade](//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png)
+![Mensagem de indisponibilidade](https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png)
 2. Define la zona horaria. 
 3. Selecciona los días y establece el horario en el que tu tienda estará disponible para atender a los clientes vía WhatsApp. Es posible definir más de un período de servicio por día de la semana.
-![fuso horário es](//images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/ee9b18b394f724ea9b8c6e31eb79fcb0/horarios_funcionamento_es.png)
+![fuso horário es](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/ee9b18b394f724ea9b8c6e31eb79fcb0/horarios_funcionamento_es.png)
 <div class="alert alert-info">
 Para los feriados nacionales, regionales u otras fechas en las que no vayas a prestar servicio: informa la fecha y hora en que el servicio no estará disponible. Si los periodos se repiten anualmente, es posible seleccionar “Recurrencia anual”, predefiniendo la configuración de los periodos seleccionados.
 </div>
diff --git a/docs/tracks/es/managing-accounts.md b/docs/tracks/es/managing-accounts.md
index f9649798c..54de3cbb6 100644
--- a/docs/tracks/es/managing-accounts.md
+++ b/docs/tracks/es/managing-accounts.md
@@ -26,7 +26,7 @@ Al hacer clic en el nombre de una cuenta específica, la pantalla __Detalles de
 - [Cierre de cuenta](#cierre-de-cuenta)
 <br>
 <br>
-![Cuenta_ES](//images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/4ee2770f072e2cbd60d80045423ad427/Contas_ES.png)
+![Cuenta_ES](https://images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/4ee2770f072e2cbd60d80045423ad427/Contas_ES.png)
 
 ## Titular
 
diff --git a/docs/tracks/es/managing-customer-credit-invoices.md b/docs/tracks/es/managing-customer-credit-invoices.md
index 641e97f86..75fa6c0be 100644
--- a/docs/tracks/es/managing-customer-credit-invoices.md
+++ b/docs/tracks/es/managing-customer-credit-invoices.md
@@ -21,7 +21,7 @@ La pantalla __Facturas__ en el Admin de VTEX (__Aplicaciones > Customer Credit >
 - [Liquidar facturas](#liquidar-facturas)
 <br>
 <br>
-![Invoices_ES](//images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/ef748599f8033d5bdac2d320a5cb2be3/Invoices_ES.JPG)
+![Invoices_ES](https://images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/ef748599f8033d5bdac2d320a5cb2be3/Invoices_ES.JPG)
 
 ## Filtro de facturas
 
diff --git a/docs/tracks/es/managing-sales-associates-in-instore.md b/docs/tracks/es/managing-sales-associates-in-instore.md
index 8d7f8f6be..e6fd433b0 100644
--- a/docs/tracks/es/managing-sales-associates-in-instore.md
+++ b/docs/tracks/es/managing-sales-associates-in-instore.md
@@ -17,7 +17,7 @@ trackSlugES: instore-primeros-pasos-y-configuracion
 Una vez realizadas las [configuraciones básicas de VTEX Sales App en el Admin](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), es posible agregar nuevos vendedores al sistema o administrar vendedores ya registrados.
 La categoría **Vendedores** representa una sección dentro del módulo **Configuración de la tienda** del Admin VTEX, mostrando la lista completa de vendedores registrados en la aplicación [VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). Dentro de esta página, es posible gestionar la información de los vendedores en todas las [cuentas franquicia]() de tu tienda, mediante operaciones de [crear](#crear-vendedor), [buscar](#buscar-vendedor), [filtrar](#filtrar-vendedore), [editar](Editar) y [eliminar](#eliminar-vendedor).
 
-![vendedores-es](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
+![vendedores-es](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
 
 La página contiene la siguiente información:
 
diff --git a/docs/tracks/es/managing-shipping-rates.md b/docs/tracks/es/managing-shipping-rates.md
index 613e2738c..5b267fabf 100644
--- a/docs/tracks/es/managing-shipping-rates.md
+++ b/docs/tracks/es/managing-shipping-rates.md
@@ -18,7 +18,7 @@ Para la correcta configuración de una nueva transportadora, es importante detal
 
 Esta se utiliza para registrar los códigos postales atendidos, los valores cobrados, los rangos de peso considerados y los valores adicionales de cada transportadora.
 
-![planilha-frete-pt](//images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
+![planilha-frete-pt](https://images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
 
 ## Cómo crear la plantilla 
 
diff --git a/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 8e5e3c038..e69500108 100644
--- a/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -19,7 +19,7 @@ Después de instalar y configurar TikTok for Business, podrás gestionar la inte
 
 Cualquier usuario conectado al Admin VTEX podrá acceder a esta área para gestionar TikTok. Sin embargo, al interactuar con los botones de esta zona, el usuario será redireccionado a los entornos de TikTok – TikTok Business Center, TikTok Ads Manager y TikTok Catalog Manager, donde necesitará los permisos necesarios para ver el contenido y realizar cambios.
 
-![manage-tiktok-integration](//images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
+![manage-tiktok-integration](https://images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
 
 Desde esta página, puedes:
 
diff --git a/docs/tracks/es/mapping-colors-and-sizes.md b/docs/tracks/es/mapping-colors-and-sizes.md
index 15a6177af..b73da5bd2 100644
--- a/docs/tracks/es/mapping-colors-and-sizes.md
+++ b/docs/tracks/es/mapping-colors-and-sizes.md
@@ -65,7 +65,7 @@ Debe escogerse el color disponible más cercano que, en el caso de Wish, "Hielo"
   OBS: la cabecera de la tabla debe rellenarse exactamente como está en el siguiente ejemplo. Recuerde no agregar caracteres especiales como enter o espacio al rellenar esta tabla. 
   </div>
 
-![PT - Tabela Wish](//images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
+![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
 ## Cargando el archivo
 
diff --git a/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
index c4120c874..0530a9c33 100644
--- a/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -57,7 +57,7 @@ Para finalizar el mapeo de la categoría, debes seguir las instrucciones a conti
 
 ## Mapear atributos
 
-![Home (8)](//images.ctfassets.net/alneenqid6w5/1WVspX796PMYQcgOycbhVC/5de9a1c9a262f8556b2eb82b9fd6cf20/Home__8_.gif)
+![Home (8)](https://images.ctfassets.net/alneenqid6w5/1WVspX796PMYQcgOycbhVC/5de9a1c9a262f8556b2eb82b9fd6cf20/Home__8_.gif)
 
 El mapeo de los atributos permite que haya una correspondencia entre el patrón de tu tienda VTEX y el patrón utilizado por Mercado Libre. Cada categoría tiene atributos obligatorios en Mercado Libre y es necesario rellenarlos para que el mapeo pueda completarse. Los campos no mapeados no impiden que se realice el mapeo, sin embargo, mientras más atributos de tu producto se envíen a Mercado Libre, mejor clasificado estará en ese marketplace.
 
diff --git a/docs/tracks/es/mercado-libre-marketplace.md b/docs/tracks/es/mercado-libre-marketplace.md
index 443cef00c..2365ca273 100644
--- a/docs/tracks/es/mercado-libre-marketplace.md
+++ b/docs/tracks/es/mercado-libre-marketplace.md
@@ -18,7 +18,7 @@ trackSlugES: configurar-integracion-con-mercado-libre
 
 Su operación está presente en países: Argentina, Brasil, Chile, Colombia, México, Uruguay y Venezuela.
 
-![image3](//images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/c459fc424669363e045e5a6bca90c82d/image3.png)
+![image3](https://images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/c459fc424669363e045e5a6bca90c82d/image3.png)
 
 El marketplace de Mercado Libre ofrece un entorno de comercio en línea totalmente automatizado, organizado por temas y fácil de usar. Este servicio ofrece a los compradores una amplia variedad de artículos nuevos y usados, permitiendo a empresas y particulares publicitar artículos y realizar sus ventas y compras en el mercado más grande de América Latina.
 
diff --git a/docs/tracks/es/merchandising-rules.md b/docs/tracks/es/merchandising-rules.md
index f309c9ce1..1e01482d7 100644
--- a/docs/tracks/es/merchandising-rules.md
+++ b/docs/tracks/es/merchandising-rules.md
@@ -30,7 +30,7 @@ En el Admin VTEX, la página **Storefront** > **Intelligent Search** > **Reglas
 * [Editar](#editar-reglas-de-merchandising)
 * [Eliminar](#eliminar-reglas-de-merchandising)
 
-![reglas-merch-es](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/4624acb4cd7dbe4e2a4d858e570f1f92/reglas-merch-es.PNG)
+![reglas-merch-es](https://images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/4624acb4cd7dbe4e2a4d858e570f1f92/reglas-merch-es.PNG)
 
 La página contiene la siguiente información: 
 
diff --git a/docs/tracks/es/opening-tickets.md b/docs/tracks/es/opening-tickets.md
index 94935bdda..cdfe306f7 100644
--- a/docs/tracks/es/opening-tickets.md
+++ b/docs/tracks/es/opening-tickets.md
@@ -20,7 +20,7 @@ El acceso a una cuenta VTEX te permite entrar al [dashboard de soporte](https://
 - Accediendo a cualquier página del [Help Center](https://help.vtex.com/es/) y haciendo clic en `Soporte` en la parte superior de la página o en `Entrar en contacto`, en la parte inferior.
 - Accediendo al Admin VTEX, haciendo clic en el ícono de la interrogación `?` del **Centro de información** y eligiendo la opción **Habla con nuestros expertos**.
 
-![Support imagem 1 - ES](//images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/0ac7e761404016450b146bfc8fabfa67/support__imagem1_ES.gif)
+![Support imagem 1 - ES](https://images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/0ac7e761404016450b146bfc8fabfa67/support__imagem1_ES.gif)
 
 <div class = "alert alert-info">
 Para obtener más información sobre cómo abrir un ticket y sobre los tipos existentes, consulta el artículo <a href="https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM"> Abrir tickets para el soporte VTEX. </a>
diff --git a/docs/tracks/es/order-delivery.md b/docs/tracks/es/order-delivery.md
index e93b63ef7..ab6d9b7a3 100644
--- a/docs/tracks/es/order-delivery.md
+++ b/docs/tracks/es/order-delivery.md
@@ -23,7 +23,7 @@ Vea a continuación dos ejemplos de este escenario:
 
 En este caso, es habitual que los ítems salgan del almacén de un Centro de Distribución, como se ilustra a continuación.
 
-![ES Conceitos Logística](//images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
+![ES Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
 
 Otra posibilidad de entrega que puede optimizar la operación y reducir los costes es implementar la estrategia de [envío desde la tienda](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl), de modo que los ítems también puedan enviarse desde el <i>*stock*</i> de las tiendas físicas.
 
diff --git a/docs/tracks/es/order-flow.md b/docs/tracks/es/order-flow.md
index 90b82b077..95a1d0ceb 100644
--- a/docs/tracks/es/order-flow.md
+++ b/docs/tracks/es/order-flow.md
@@ -33,7 +33,7 @@ Es importante comprender estos conceptos porque el flujo de pedidos en el Market
 
 ## Flujo del pedido en el Marketplace
 
-![screenshoot fluxo marketplace ES](//images.ctfassets.net/alneenqid6w5/2ehRbL33XqtPTTF8DoHtvT/49e8aad025ddba81b5f3d169a040d9f2/screenshoot_fluxo_marketplace_ES.JPG)
+![screenshoot fluxo marketplace ES](https://images.ctfassets.net/alneenqid6w5/2ehRbL33XqtPTTF8DoHtvT/49e8aad025ddba81b5f3d169a040d9f2/screenshoot_fluxo_marketplace_ES.JPG)
 
 Se produce cuando la tienda actúa solamente como Marketplace en el pedido. O sea, es cuando la tienda vende productos de otra tienda: su Seller.
 
@@ -47,7 +47,7 @@ El envío se autoriza y luego el pedido ingresa el status `Carencia para la canc
 
 ## Flujo del pedido en el Seller
 
-![screenshoot fluxo seller ES](//images.ctfassets.net/alneenqid6w5/eEAFKk01PalVIOQFHrPUr/e10848ee747ff9c9334489d871fde01e/screenshoot_fluxo_seller_ES.JPG)
+![screenshoot fluxo seller ES](https://images.ctfassets.net/alneenqid6w5/eEAFKk01PalVIOQFHrPUr/e10848ee747ff9c9334489d871fde01e/screenshoot_fluxo_seller_ES.JPG)
 
 Se produce cuando la tienda actúa como Seller. O sea, es entonces cuando ella posee el producto.
 
@@ -61,7 +61,7 @@ El siguiente status es `Preparando entrega`, cuando el Seller prepara la factura
 
 ## Flujo completo del pedido
 
-![screenshoot fluxo completo ES](//images.ctfassets.net/alneenqid6w5/35UAHChmiqzGYFTsKDEnRI/ae60c51044ef99dab1c262fb73afc5ad/screenshoot_fluxo_completo_ES.JPG)
+![screenshoot fluxo completo ES](https://images.ctfassets.net/alneenqid6w5/35UAHChmiqzGYFTsKDEnRI/ae60c51044ef99dab1c262fb73afc5ad/screenshoot_fluxo_completo_ES.JPG)
 
 Ocurre cuando la tienda es tanto Marketplace como Seller. Es decir, es cuando el pedido se cerró en la tienda y la tienda en sí es el propietario del producto, siendo responsable del fulfillment.
 
diff --git a/docs/tracks/es/other-vtex-module-settings.md b/docs/tracks/es/other-vtex-module-settings.md
index d9f953ff3..9f6133561 100644
--- a/docs/tracks/es/other-vtex-module-settings.md
+++ b/docs/tracks/es/other-vtex-module-settings.md
@@ -83,7 +83,7 @@ Se puede configurar la programación de compras recurrentes en el [sistema de Su
 
 - Asignación de [usuario](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512) encargado de la tarea.
 
-![vtex-do-es](//images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/68b05218448ed87c58001b235024bb46/next_steps_image12_ES.JPG)
+![vtex-do-es](https://images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/68b05218448ed87c58001b235024bb46/next_steps_image12_ES.JPG)
 
 ### VTEX Social Selling
 
diff --git a/docs/tracks/es/payment.md b/docs/tracks/es/payment.md
index d638625ba..7fb6da073 100644
--- a/docs/tracks/es/payment.md
+++ b/docs/tracks/es/payment.md
@@ -16,7 +16,7 @@ trackSlugES: instore-usando-el-app
 
 En el paso de pago de VTEX Sales App, las [opciones de pago que se han configurado](https://help.vtex.com/es/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy) aparecerán en su tienda.
 
-![instore-payment-es](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/b91142c0f767502f5e68f91830032fcb/Screenshot_2022-10-21_at_15-02-51_VTEX_VTEX Sales App_Checkout.png)
+![instore-payment-es](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/b91142c0f767502f5e68f91830032fcb/Screenshot_2022-10-21_at_15-02-51_VTEX_VTEX Sales App_Checkout.png)
 
 La barra superior de la pantalla de pago muestra las siguientes opciones:
 
@@ -45,7 +45,7 @@ Para configurar un medio de pago, sigue las instrucciones de la guía[ VTEX Sale
 
 El cliente debe seleccionar la opción **Efectivo** y hacer clic en `Finalizar venta`.
 
-![instore-dinheiro-es](//images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/12ee090451235610a53ec937f8af2b69/Screenshot_2022-10-21_at_15-03-02_VTEX_VTEX Sales App_Checkout.png)
+![instore-dinheiro-es](https://images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/12ee090451235610a53ec937f8af2b69/Screenshot_2022-10-21_at_15-03-02_VTEX_VTEX Sales App_Checkout.png)
 
 Luego, el cliente debe realizar la transacción con el vendedor. La aprobación de la venta puede ser [manual o automática](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), dependiendo de la configuración de la tienda.
 
@@ -53,21 +53,21 @@ Luego, el cliente debe realizar la transacción con el vendedor. La aprobación
 
 El cliente debe seleccionar la opción **Pix** y hacer clic en `Finalizar venta`.
 
-![instore-pix-es](//images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/2f9ad65f84c36686f1e9f06ed94a69ed/Screenshot_2022-10-21_at_15-03-27_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix-es](https://images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/2f9ad65f84c36686f1e9f06ed94a69ed/Screenshot_2022-10-21_at_15-03-27_VTEX_VTEX Sales App_Checkout.png)
 
 Después de finalizar la venta, se mostrará el código QR en la pantalla de VTEX Sales App. El cliente debe escanear el código QR con el celular para realizar el pago.
 
-![instore-pix2-es](//images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/ebdb109d680d504c71b41318c3dcfa24/image.png) 
+![instore-pix2-es](https://images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/ebdb109d680d504c71b41318c3dcfa24/image.png) 
 
 Después de que el cliente realice el pago, la venta será procesada y finalmente confirmada en la página del pedido, como se muestra en la imagen a continuación.
 
-![instore-pix3-es](//images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/3d4621cb3e131300d783dae3b5531f73/Screenshot_2022-10-21_at_15-03-58_VTEX_VTEX Sales App_Checkout.png)
+![instore-pix3-es](https://images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/3d4621cb3e131300d783dae3b5531f73/Screenshot_2022-10-21_at_15-03-58_VTEX_VTEX Sales App_Checkout.png)
 
 ### Boleto (Brasil)
 
 El cliente debe seleccionar la opción **Boleto** y hacer clic en `Finalizar venta`.
 
-![instore-boleto-es](//images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/e0800b0dc8dec484040eb5980a888adc/Screenshot_2022-10-21_at_15-02-56_VTEX_VTEX Sales App_Checkout.png)
+![instore-boleto-es](https://images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/e0800b0dc8dec484040eb5980a888adc/Screenshot_2022-10-21_at_15-02-56_VTEX_VTEX Sales App_Checkout.png)
 
 El boleto se enviará al email del cliente. Después de que se confirme el pago del boleto, la venta será confirmada.
 
@@ -75,7 +75,7 @@ El boleto se enviará al email del cliente. Después de que se confirme el pago
 
 El cliente debe seleccionar la opción **Tarjeta de crédito**, seleccionar el número de cuotas de la compra y hacer clic en `Finalizar venta`.
 
- ![instore-credito-es](//images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ede072361e0b860a57134816109a34e7/Screenshot_2022-10-21_at_15-03-20_VTEX_VTEX Sales App_Checkout.png)
+ ![instore-credito-es](https://images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/ede072361e0b860a57134816109a34e7/Screenshot_2022-10-21_at_15-03-20_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App mostrará una pantalla de espera mientras se realiza el pago en la máquina de tarjetas de la tienda. Una vez que el sistema reconozca el pago, la venta será confirmada.
 
@@ -83,7 +83,7 @@ VTEX Sales App mostrará una pantalla de espera mientras se realiza el pago en l
 
 El cliente debe seleccionar la opción **Tarjeta de débito** y hacer clic en `Finalizar venta`.
 
-![instore-debito-es](//images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4574ff7ac0657f38ccc46ecfcb7200e7/Screenshot_2022-10-21_at_15-03-13_VTEX_VTEX Sales App_Checkout.png)
+![instore-debito-es](https://images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4574ff7ac0657f38ccc46ecfcb7200e7/Screenshot_2022-10-21_at_15-03-13_VTEX_VTEX Sales App_Checkout.png)
 
 VTEX Sales App mostrará una pantalla de espera mientras se realiza el pago en la máquina de tarjetas de la tienda. Una vez que el sistema reconozca el pago, la venta será confirmada.
 
diff --git a/docs/tracks/es/planning-the-go-live.md b/docs/tracks/es/planning-the-go-live.md
index 1eb7212d8..fe912e0d8 100644
--- a/docs/tracks/es/planning-the-go-live.md
+++ b/docs/tracks/es/planning-the-go-live.md
@@ -34,7 +34,7 @@ El proceso de go live de una tienda, incluyendo las configuraciones y pruebas ne
 
 En la siguiente imagen puedes ver las etapas de planificación del go live de una tienda VTEX:
 
-![go-live-es](//images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/41e4c49c159b2a1d22c863808f3e382c/golive_1_ES.png)
+![go-live-es](https://images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/41e4c49c159b2a1d22c863808f3e382c/golive_1_ES.png)
 
 ### Definir MVP
 
@@ -54,7 +54,7 @@ Por lo tanto, todo el proceso de planificación debe comenzar con al menos 45 d
 
 Para organizar los equipos participantes y realizar el go live en la fecha deseada, es importante crear un roadmap, es decir, un documento que recoja las acciones requeridas y que indique los responsables de cada etapa y los plazos acordados. La siguiente imagen muestra un ejemplo de roadmap:
 
-![golive 2 ES](//images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/135bae2dca13c1881fb5d7c02a5f0b60/golive_2_ES.png)
+![golive 2 ES](https://images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/135bae2dca13c1881fb5d7c02a5f0b60/golive_2_ES.png)
 
 Recomendamos planificar reuniones periódicas con los [equipos de implementación](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion) para mantener una alineación frecuente y, de ser necesario, crear un war room para resolver asuntos pendientes la semana antes del go live.
 
diff --git a/docs/tracks/es/preco-base-definicao-de-conceito.md b/docs/tracks/es/preco-base-definicao-de-conceito.md
index 9478731e8..a785494bb 100644
--- a/docs/tracks/es/preco-base-definicao-de-conceito.md
+++ b/docs/tracks/es/preco-base-definicao-de-conceito.md
@@ -18,7 +18,7 @@ trackSlugES: precios-101
 
 El Precio Base de un SKU es el valor calculado a través de la combinación entre el **Precio de Costo** y el **Markup**, el margen de ganancia deseado con la venta del SKU. Es el __precio de referencia__ de un SKU para todas las tablas de precio. 
 
-![base-price-es](//images.ctfassets.net/alneenqid6w5/14OYPLF5k6gNJhSUZ5OE53/9b59c8c88d39347707be5054d948ad91/base-price-es.png)
+![base-price-es](https://images.ctfassets.net/alneenqid6w5/14OYPLF5k6gNJhSUZ5OE53/9b59c8c88d39347707be5054d948ad91/base-price-es.png)
 
 Este **precio base** puede combinarse con una **regla de precio** aplicada a la tabla de precios. Si no existe regla de precio registrada, el precio de venta en una tabla será el propio precio base.
 
diff --git a/docs/tracks/es/preco-fixo-definicao-de-conceito.md b/docs/tracks/es/preco-fixo-definicao-de-conceito.md
index 3828042db..63dbaebd5 100644
--- a/docs/tracks/es/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/es/preco-fixo-definicao-de-conceito.md
@@ -74,7 +74,7 @@ Digamos que se registren dos precios fijos para el mismo SKU. Además, ambos tie
 
 Por ejemplo: el primer precio fijo es __$ 50.00__ y ​​su programación va de __10h a 16h__. Ya el segundo es __$ 25.00__, solo que está programado de __12h a 20h del mismo día__. En este caso, *entre las 12h y las 16h*, los dos precios fijos compiten entre sí. Por lo tanto, el valor de __$ 25.00__ será el precio de venta del SKU en este horario en común.
 
-![fixed price - example2](//images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
+![fixed price - example2](https://images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
 
 ### Competencia por el Criterio de Ítems Mínimos en el Carrito 
 
@@ -84,7 +84,7 @@ Imagine que registramos un precio fijo de $ 200.00 para __dos o más ítems en e
 
 ¿Cuál sería el precio aplicado para 5 o más ítems? El precio de venta será de $ 100.00, visto que el sistema prioriza el valor más bajo.
 
-![fixed price - example1](//images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
+![fixed price - example1](https://images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
 
 ## Ejemplos
 
diff --git a/docs/tracks/es/pricing-system-architecture.md b/docs/tracks/es/pricing-system-architecture.md
index 0ab02e1b6..ffe7ebc05 100644
--- a/docs/tracks/es/pricing-system-architecture.md
+++ b/docs/tracks/es/pricing-system-architecture.md
@@ -33,7 +33,7 @@ Estos pueden ser:
 
 A continuación, vemos un esquema de cómo se relacionan los conceptos de *precios*, *tabla de precios* y *contextos*:
 
-![Architecture-ES](//images.ctfassets.net/alneenqid6w5/6bnxEox2mBlC6eFRoXv2B2/c8275d94ff8ec1867467a22eeed50464/Architecture__3_.svg)
+![Architecture-ES](https://images.ctfassets.net/alneenqid6w5/6bnxEox2mBlC6eFRoXv2B2/c8275d94ff8ec1867467a22eeed50464/Architecture__3_.svg)
 
 ## Precio calculado
 
@@ -47,22 +47,22 @@ El módulo de precios considera 4 criterios para calcular el precio calculado pa
 - Precio Fijo
 
 1. Si el SKU tiene apenas registrado el *precio base*, el precio calculado para una determinada tabla de precios será igual al **precio base**.
-![rule1-ES](//images.ctfassets.net/alneenqid6w5/4R46AGzDiANh7Qvki4aAFb/585544b840165564ed86a740ae90850d/rule1__2_.svg) 
+![rule1-ES](https://images.ctfassets.net/alneenqid6w5/4R46AGzDiANh7Qvki4aAFb/585544b840165564ed86a740ae90850d/rule1__2_.svg) 
 
 2. Si el SKU tiene el *precio base* y una *regla de precio* configurada para una determinada tabla de precios, el precio calculado será igual al **precio base modificado por la regla de precio**.
-![rule2-ES](//images.ctfassets.net/alneenqid6w5/6G50mQEFbvLdoS0GshmqrZ/45c8762d46b0cca57ec96505db2b708f/rule2__2_.svg) 
+![rule2-ES](https://images.ctfassets.net/alneenqid6w5/6G50mQEFbvLdoS0GshmqrZ/45c8762d46b0cca57ec96505db2b708f/rule2__2_.svg) 
 
 3. En otro escenario, vamos a considerar un SKU con *precio base*, *regla de precio* y *redondeo de precios*. **El precio calculado para una determinada tabla de precio se calculará mediante una combinación de estos tres factores**. Primero, el precio base se modificará por la regla de precio. Después de esto, se producirá el redondeo por la regla de precio psicológico.
-![rule3-ES](//images.ctfassets.net/alneenqid6w5/3FEUQbPoblkpqqQpBrzUjC/cb730b634996a8f57356b794353f63d2/rule3__2_.svg)
+![rule3-ES](https://images.ctfassets.net/alneenqid6w5/3FEUQbPoblkpqqQpBrzUjC/cb730b634996a8f57356b794353f63d2/rule3__2_.svg)
 
 4. Finalmente, si un SKU tiene un *precio fijo* registrado, **el precio calculado para una determinada tabla de precios será igual al precio fijo**. Este precio tiene un peso superior a los otros precios. De esta manera, el módulo de precios *ignora los otros precios* si encuentra un precio fijo asociado a un SKU.
-![rule4-ES](//images.ctfassets.net/alneenqid6w5/1IO167lvTydJX8UqYSgdWi/58103cb411586d9bbe924ecc11680155/rule4__3_.svg)
+![rule4-ES](https://images.ctfassets.net/alneenqid6w5/1IO167lvTydJX8UqYSgdWi/58103cb411586d9bbe924ecc11680155/rule4__3_.svg)
 
 ## Validar precio calculado
 
 Para verificar el precio de venta de un SKU en una determinada tabla de precios, puede consultar el **valor del precio computado** en la sección de **Lista de precios** del admin de VTEX. En el siguiente ejemplo, vemos que el precio computado del **SKU 14** para la **tabla de la política comercial 1** es igual a **334.62**:
 
-![computed-price-es](//images.ctfassets.net/alneenqid6w5/4bUfMSdT0nD8ySiMZ5QztD/6e34043f53fbb6296a3d82c9d6892aa4/computed-price-es.png)
+![computed-price-es](https://images.ctfassets.net/alneenqid6w5/4bUfMSdT0nD8ySiMZ5QztD/6e34043f53fbb6296a3d82c9d6892aa4/computed-price-es.png)
 
 También puede verificar cuál es el precio computado de un SKU en una tabla de precios **haciendo una llamada por API**. Para esto, debe hacer un **GET** en el endpoint [Get Computed Price by price table or trade policy](https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-).
 
diff --git a/docs/tracks/es/printing-an-order-summary.md b/docs/tracks/es/printing-an-order-summary.md
index 15bf09e60..7274e7968 100644
--- a/docs/tracks/es/printing-an-order-summary.md
+++ b/docs/tracks/es/printing-an-order-summary.md
@@ -18,7 +18,7 @@ Al finalizar un pedido utilizando VTEX Sales App, es posible imprimir un resumen
 
 Para ello, el vendedor puede hacer clic en el botón `Imprimir pedido` en la pantalla del pedido finalizado, como se ilustra a continuación. Otra opción es configurar VTEX Sales App para que imprima el resumen del pedido automáticamente en cuanto se finalice el pedido.
 
-![15. Configurar impressão de resumo do pedido - 1 - ES](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/5a3aabdd6ad7b66958a744955fbfa979/print-order-es.png)
+![15. Configurar impressão de resumo do pedido - 1 - ES](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/5a3aabdd6ad7b66958a744955fbfa979/print-order-es.png)
 
 Para habilitar la impresión del resumen del pedido, sigue los pasos descritos a continuación.
 
@@ -50,13 +50,13 @@ Después de obtener el AppKey y el AppToken, sigue los pasos a continuación.
 2. Abre la aplicación VTEX Sales App e introduce el nombre de la tienda en la que quieres configurar la impresora.
 3. En el menú principal de inStore, en la sección **Configuración**, haz clic en la opción <i class="fas fa-cog"></i> **Configurar el dispositivo**, ilustrada a continuación.
 
-![15. Configurar impressão de resumo do pedido - 2 - ES](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/901224ec3c5342310a3ad2c54274caf8/configuracion-es.png)
+![15. Configurar impressão de resumo do pedido - 2 - ES](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/901224ec3c5342310a3ad2c54274caf8/configuracion-es.png)
 
 <ol start="4">
   <li>A continuación, verás el resumen del dispositivo configurado. Si es la primera vez que se realiza esta configuración, los campos en la pantalla estarán vacíos, como se muestra en la siguiente imagen. Si un dispositivo ha sido configurado anteriormente, verás el <b>Nombre del dispositivo</b> y la <b>Impresora estándar</b>. Haz clic en el botón <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">Editar</span>.</li>
 </ol>
 
-![15. Configurar impressão de resumo do pedido - 4 - ES](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/f8ad79cb1907905f230318c0c25ad964/image_4__1_.png)
+![15. Configurar impressão de resumo do pedido - 4 - ES](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/f8ad79cb1907905f230318c0c25ad964/image_4__1_.png)
 
 <ol start="5">
   <li>Rellena el formulario con los campos descritos a continuación.
diff --git a/docs/tracks/es/product-details.md b/docs/tracks/es/product-details.md
index 0a5b456e4..5936dd110 100644
--- a/docs/tracks/es/product-details.md
+++ b/docs/tracks/es/product-details.md
@@ -16,7 +16,7 @@ trackSlugES: instore-usando-el-app
 
 Al hacer clic en los detalles de un producto que aparece en los resultados de búsqueda de VTEX Sales App, o al leer el código de un producto, el vendedor se dirige a la pantalla de detalles del producto.
 
-![instore-pdp-es](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/89db3673ca4d66e8c5af7e18dcb4c296/pdp-es.png)
+![instore-pdp-es](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/89db3673ca4d66e8c5af7e18dcb4c296/pdp-es.png)
 
 Esta pantalla muestra el nombre del producto, su galería de fotos, variaciones, descripción y disponibilidad. El vendedor puede, en esta pantalla, agregar el producto al carrito.
 
diff --git a/docs/tracks/es/promotions-for-specific-scenarios.md b/docs/tracks/es/promotions-for-specific-scenarios.md
index 67aad83d1..5996dda25 100644
--- a/docs/tracks/es/promotions-for-specific-scenarios.md
+++ b/docs/tracks/es/promotions-for-specific-scenarios.md
@@ -38,7 +38,7 @@ La pantalla de configuración de la promoción ofrece dos listas de SKUs, que pu
 
 Puede, entonces, definir un valor de descuento para cada una de estas listas. Si, por ejemplo, la lista 1 tiene un 10% de descuento y la lista 2 un 5% de descuento, cuando el carrito tenga al menos un producto de cada una de estas listas, se concederá un descuento total del 10% sobre el valor de los ítems de la lista 1 y un descuento del 5% sobre el valor de los ítems de la lista 2.
 
-![Compre Junto - ES](//images.ctfassets.net/alneenqid6w5/6Heut08iWTOC9Ph1CpVjJ0/255d0f4409b49327640aebba743afe6b/Screenshot_2020-06-24_https_lojadobreno_myvtex_com.png)
+![Compre Junto - ES](https://images.ctfassets.net/alneenqid6w5/6Heut08iWTOC9Ph1CpVjJ0/255d0f4409b49327640aebba743afe6b/Screenshot_2020-06-24_https_lojadobreno_myvtex_com.png)
 
 Dos ejemplos de este tipo de promoción serían "Compre un pantalón y gane 10% de descuento en la compra de un cinturón" y "Compre un par de zapatos + un par de calcetines y gane 15% de descuento".
 
@@ -50,7 +50,7 @@ La promoción Más por Menos se utiliza para otorgar un descuento cuando el clie
 
 En la configuración de la promoción Más por Menos, la tienda debe definir a qué colecciones o SKUs se aplicará. Luego, elija el número de ítems en el carrito para que funcione y el número de ítems con descuento.
 
-![Más por menos](//images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/2f8e02eef7f52bdaccf728ff9406ece7/Mas_por_menos.png)
+![Más por menos](https://images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/2f8e02eef7f52bdaccf728ff9406ece7/Mas_por_menos.png)
 
 Por ejemplo:
 
@@ -69,7 +69,7 @@ Al configurar la promoción de Descuento Progresivo, la tienda debe definir a qu
 
 Para continuar la progresión del descuento, haga clic en el botón "+". Se agregará una nueva línea y, entonces, podrá agregar un nuevo descuento. Por ejemplo: para los siguientes 2 productos, el cliente recibirá un descuento adicional del 5%. Y así sucesivamente.
 
-![Desconto progressivo - ES](//images.ctfassets.net/alneenqid6w5/2JgsOt6rikmlj5SeXNEjvo/f245c7434417c86f0d8cccd977d68907/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_2_.png)
+![Desconto progressivo - ES](https://images.ctfassets.net/alneenqid6w5/2JgsOt6rikmlj5SeXNEjvo/f245c7434417c86f0d8cccd977d68907/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_2_.png)
 
 Para entender la promoción del Descuento Progresivo con más detalle, vea el artículo <a href="https://help.vtex.com/es/tutorial/descuento-progresivo--tutorials_324">Cómo el Descuento Progresivo funciona</a>.
 
@@ -79,7 +79,7 @@ La promoción Compre y Gane se utiliza para ofrecer flete gratis o un regalo si
 
 El descuento aplicado (flete gratis o regalo) debe definirse en los datos generales de la promoción. Luego, la tienda debe elegir las colecciones o SKUs a los que se aplicará. Finalmente, debe definir la cantidad mínima de ítems en el carrito para que la promoción funcione.
 
-![Compre e Ganhe - ES](//images.ctfassets.net/alneenqid6w5/3VixYm5a1Yj3Qb30ZSWVWp/054fe69fe18da0a1636309d621adcc59/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_3_.png)
+![Compre e Ganhe - ES](https://images.ctfassets.net/alneenqid6w5/3VixYm5a1Yj3Qb30ZSWVWp/054fe69fe18da0a1636309d621adcc59/Screenshot_2020-06-24_https_lojadobreno_myvtex_com_3_.png)
 
 Para entender la promoción Compre y Gane con más detalle, vea el artículo  <a href="https://help.vtex.com/es/tutorial/compre-y-gane--tutorials_322">Cómo funciona la promoción Compre y Gane</a>.
 
@@ -93,22 +93,22 @@ Es importante señalar que esta posibilidad es <strong>válida apenas para una p
 
 Después de rellenar todos [los campos de una promoción regular](https://help.vtex.com/es/tutorial/regular-promotion--tutorials_327) con descuento porcentual, puede seleccionar la opción __Definir la cantidad máxima de ítems afectados por carrito__ en la sección __Restricciones y limitaciones de uso__.
 
-![Limite itens - ES](//images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/b2df8c53d0e4cb8d144db320ddb983ae/Limite_itens_-_ES.png)
+![Limite itens - ES](https://images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/b2df8c53d0e4cb8d144db320ddb983ae/Limite_itens_-_ES.png)
 
 Por defecto, la opción __ilimitado__ está activa, aplicando la promoción a todos los ítems del carrito, como se ilustra en el siguiente diagrama:
 
-![Caso ilimitado ES](//images.ctfassets.net/alneenqid6w5/7LMJMOT1k3hs8lHbe1BmtJ/811dc4e9f2210817bee4dcaf319443a4/Caso_ilimitado_ES.png)
+![Caso ilimitado ES](https://images.ctfassets.net/alneenqid6w5/7LMJMOT1k3hs8lHbe1BmtJ/811dc4e9f2210817bee4dcaf319443a4/Caso_ilimitado_ES.png)
 
 Para restringir el número de ítems del carrito que recibirán el descuento, puede elegir una de las siguientes opciones:
 
 - __Ítems por carrito__: esta configuración limita la aplicación de la promoción a un número de ítems del carrito. Una vez alcanzado el límite, la promoción no se aplicará al resto del carrito. El sistema utiliza el precio como criterio de elección, por lo que los ítems con el precio más bajo serán los primeros en ser afectados.
 
-![Caso por itens ES](//images.ctfassets.net/alneenqid6w5/4ZE8Sc1reAjgnSzJHlEaar/6891a83f39caa6f6d4e4fc8fc8034dfd/Caso_por_itens_ES.png)
+![Caso por itens ES](https://images.ctfassets.net/alneenqid6w5/4ZE8Sc1reAjgnSzJHlEaar/6891a83f39caa6f6d4e4fc8fc8034dfd/Caso_por_itens_ES.png)
 
 - __Ítems por producto__: esta configuración limita la promoción a un número de unidades de cada producto. Como en el siguiente ejemplo, apenas dos unidades por producto serán elegibles para la promoción. El precio más bajo define qué ítems de cada producto son elegibles para la promoción.
 
-![Caso por produto ES](//images.ctfassets.net/alneenqid6w5/X34R3R6KpYR3xCJdF2AcI/596e61129705dc40d677f5356796c5b2/Caso_por_produto_ES.png)
+![Caso por produto ES](https://images.ctfassets.net/alneenqid6w5/X34R3R6KpYR3xCJdF2AcI/596e61129705dc40d677f5356796c5b2/Caso_por_produto_ES.png)
 
 - __Ítems por SKU__: esta configuración limita la promoción a un número de unidades por cada SKU en el carrito. Como en el siguiente ejemplo, apenas dos unidades de cada SKU serán elegibles para la promoción. Como en el caso anterior, será el precio más bajo el que defina los ítems elegibles para la promoción.
 
-![Caso por SKU ES](//images.ctfassets.net/alneenqid6w5/2l071JBnZtESSnbM2MPAQ1/1b22d7143f3ce6ed219ec6817acfd489/Caso_por_SKU_ES.png)
+![Caso por SKU ES](https://images.ctfassets.net/alneenqid6w5/2l071JBnZtESSnbM2MPAQ1/1b22d7143f3ce6ed219ec6817acfd489/Caso_por_SKU_ES.png)
diff --git a/docs/tracks/es/relevance.md b/docs/tracks/es/relevance.md
index d0d887926..52c20b105 100644
--- a/docs/tracks/es/relevance.md
+++ b/docs/tracks/es/relevance.md
@@ -23,7 +23,7 @@ Hay dos posibles escenarios de configuración de relevancia:
 - **Criterios de prioridad:** es la forma de forzar que uno o más criterios tengan mayor prioridad entre los demás. En esta situación no hay pesos, porque todos los productos que tienen esta característica se presentarán primero en el resultado de la búsqueda.
 - **Composición de criterios:** es la forma de distribuir los pesos de cada opción, que van de 0 a 10. Aquí no hay un orden entre los criterios, serán los pesos los que definan la relevancia.
 
-![criterios-es](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/0b54c302ffac20ed831392a3c7d5135d/criterios-es.png)
+![criterios-es](https://images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/0b54c302ffac20ed831392a3c7d5135d/criterios-es.png)
 
 La información aplicada para establecer la relevancia es:
 
@@ -109,5 +109,5 @@ Para cambiar la configuración de Reglas de relevancia, sigue los pasos a contin
 
    Si deseas cambiar la posición de un criterio de **Composición de criterios** a **Criterios de prioridad**, solo tienes que arrastrarlo por el ícono <i class="fas fa-grip-vertical"></i> a la parte superior según se muestra aquí. Ten en cuenta que cuando el criterio cambia a criterio de prioridad, no se le puede cambiar el peso.
 
-   ![criterios-prioritarios-es](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/1bdaef8e82e1e1801a439a45acb2e4e3/criterios-prioritarios-es.gif)
+   ![criterios-prioritarios-es](https://images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/1bdaef8e82e1e1801a439a45acb2e4e3/criterios-prioritarios-es.gif)
 5. Para terminar, haz clic en  `Guardar`.
diff --git a/docs/tracks/es/reports-vtex-intelligent-search.md b/docs/tracks/es/reports-vtex-intelligent-search.md
index 81da2576d..d447c7833 100644
--- a/docs/tracks/es/reports-vtex-intelligent-search.md
+++ b/docs/tracks/es/reports-vtex-intelligent-search.md
@@ -79,8 +79,8 @@ Para exportar un informe en formato CSV, debe seguir los pasos que se indican a
 
 El informe CSV descargado tiene dos tablas. La primera tabla, que se muestra a continuación, contiene información sobre los términos de búsqueda y las métricas de embudo (desde la columna **ProductsClick** hasta la columna **ProductsSold**), si se ha seleccionado esa opción.
 
-![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
+![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
 
 La segunda tabla, que se muestra a continuación, muestra los datos del periodo seleccionado, mostrando la columna **Date**, que indica la fecha de la búsqueda.
 
-![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
+![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
diff --git a/docs/tracks/es/sale-confirmed.md b/docs/tracks/es/sale-confirmed.md
index 4583072c7..4e858848e 100644
--- a/docs/tracks/es/sale-confirmed.md
+++ b/docs/tracks/es/sale-confirmed.md
@@ -16,4 +16,4 @@ trackSlugES: instore-usando-el-app
 
 El vendedor puede ver la pantalla __Venta confirmada__ con el resumen del pedido cuando termina una venta, o haciendo clic en una venta en la página __Últimas ventas__, a la que puede acceder a través del menú principal de VTEX Sales App. En la página __Últimas ventas__, pueden buscar el pedido por número de pedido o nombre del cliente.
 
-![order-placed-es](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/11ccd0884f76f8407d439678a338b3b3/order-placed-es.png)
+![order-placed-es](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/11ccd0884f76f8407d439678a338b3b3/order-placed-es.png)
diff --git a/docs/tracks/es/search-settings.md b/docs/tracks/es/search-settings.md
index c7d82c091..80736ab84 100644
--- a/docs/tracks/es/search-settings.md
+++ b/docs/tracks/es/search-settings.md
@@ -36,7 +36,7 @@ La configuración general presenta las siguientes opciones relativas a [las espe
 
 La configuración de facetas presenta ajustes relacionados con las [facetas](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) mostradas a los clientes de tu tienda durante la búsqueda:
 
-![Configuracion del filtro](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
+![Configuracion del filtro](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
 
 * **Orden de las facetas:** orden en el que se mostrarán las facetas en la tienda. Si no hay ninguna faceta seleccionada en la sección, el orden predeterminado es alfabético.
 
diff --git a/docs/tracks/es/sending-products-to-amazon.md b/docs/tracks/es/sending-products-to-amazon.md
index b2b211725..54a8f06af 100644
--- a/docs/tracks/es/sending-products-to-amazon.md
+++ b/docs/tracks/es/sending-products-to-amazon.md
@@ -41,10 +41,10 @@ La lista de categorías de tu tienda VTEX incluye el status del mapeo a través
 
 | **Ícono** | **Status** | **Descripción** |
 |:---:|:---:|:---:|
-| ![mapeado mapper](//images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/069480d9eeb7b6108d5f6ec3d7ad1d78/mapeado_mapper.jpg) | **Mapeada** | Indica que el mapeo de categorías está completo. |
-| ![mapeamentoincompleto mapper](//images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/695f33c0eba4012f7e585ca1785ec17f/mapeamentoincompleto_mapper.jpg) | **Mapeo incompleto** | La categoría está parcialmente mapeada, por lo que es necesario ingresar sus atributos obligatorios (señalados con un asterisco) para realizar el mapeo. |
-| ![erromapeamento mapper](//images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/7036253cccb4415d9759867b28ff1695/erromapeamento_mapper.jpg) | **Error al realizar el mapeo** | El error de mapeo ocurre cuando el marketplace elimina o cambia la categoría del producto. Para resolver este problema, solo hay que rehacer el mapeo de categorías. |
-|![incompleto mapper](//images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/3eaea439ecfdbb54eaa8fefec12247ae/incompleto_mapper.jpg) | **No mapeada** | Indica que no se realizó el mapeo de la categoría. |  
+| ![mapeado mapper](https://images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/069480d9eeb7b6108d5f6ec3d7ad1d78/mapeado_mapper.jpg) | **Mapeada** | Indica que el mapeo de categorías está completo. |
+| ![mapeamentoincompleto mapper](https://images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/695f33c0eba4012f7e585ca1785ec17f/mapeamentoincompleto_mapper.jpg) | **Mapeo incompleto** | La categoría está parcialmente mapeada, por lo que es necesario ingresar sus atributos obligatorios (señalados con un asterisco) para realizar el mapeo. |
+| ![erromapeamento mapper](https://images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/7036253cccb4415d9759867b28ff1695/erromapeamento_mapper.jpg) | **Error al realizar el mapeo** | El error de mapeo ocurre cuando el marketplace elimina o cambia la categoría del producto. Para resolver este problema, solo hay que rehacer el mapeo de categorías. |
+|![incompleto mapper](https://images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/3eaea439ecfdbb54eaa8fefec12247ae/incompleto_mapper.jpg) | **No mapeada** | Indica que no se realizó el mapeo de la categoría. |  
 
 Para realizar el mapeo de categorías:  
 
@@ -53,7 +53,7 @@ Para realizar el mapeo de categorías:
 3. Selecciona la categoría de Amazon correspondiente al producto que deseas enviar.
 4. Haz la correspondencia de los atributos en la ventana lateral, como se muestra en la imagen a continuación:
 
-![Atributos del mapeador de Amazon](//downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/9dbef07f676b7bf29ef81bfda39d9bda/mapper_amazon_atributos.gif)
+![Atributos del mapeador de Amazon](https://downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/9dbef07f676b7bf29ef81bfda39d9bda/mapper_amazon_atributos.gif)
 
 5. Haz clic en el botón `Guardar cambios`.
 
@@ -119,13 +119,13 @@ Para configurar la categoría global en su entorno VTEX según las categorías g
 ##### Ejemplo de cómo consultar las plantillas 
 
 En la Plantilla de atributos de Amazon, utilizaremos la categoría **Health**, centrada en los productos de salud:
-![categoriageral01](//images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
+![categoriageral01](https://images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
 
 En la Plantilla de categorías generales de Amazon, filtre la columna «I» Cat-Amazon-Geral, haciendo clic en **Filtro > Health > OK**.
-![categoriageral02](//images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
+![categoriageral02](https://images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
 
 Siguiendo el ejemplo anterior, filtre las columnas B, C y D, haciendo clic en **Salud y Belleza > Cuidado personal > Masaje y relajación**.
-![categoriageral03](//images.contentful.com/alneenqid6w5/1p0cIHz7bp8HHuzud1H4zE/e79bf00cbe09f7b1fb155730cfc401f8/categoriageral03.JPG)
+![categoriageral03](https://images.contentful.com/alneenqid6w5/1p0cIHz7bp8HHuzud1H4zE/e79bf00cbe09f7b1fb155730cfc401f8/categoriageral03.JPG)
 
 Ahora que ha encontrado la categoría general de Amazon, vuelva al Admin para [configurar la categoría global de VTEX](https://help.vtex.com/es/tutorial/configurando-a-categoria-global--tutorials_188) según la categoría general de Amazon.
 
diff --git a/docs/tracks/es/set-a-price-for-the-sku.md b/docs/tracks/es/set-a-price-for-the-sku.md
index 4b3405e74..8fec00e22 100644
--- a/docs/tracks/es/set-a-price-for-the-sku.md
+++ b/docs/tracks/es/set-a-price-for-the-sku.md
@@ -22,7 +22,7 @@ Incluso un SKU que se ofrecerá como regalo necesita tener un precio registrado.
 
 Para registrar el precio, siga los pasos abajo.
 1. En el módulo __Catalog__, pase el ratón sobre __Cadastro de Productos__, vaya a __Productos y SKUs__ y haga clic en la opción __Cadastro de Productos y SKUs__.
-2. En la línea del SKU deseado, haga clic en el símbolo de signo de dólar (se le llevará al módulo Pricing).![SKUprice1](//images.contentful.com/alneenqid6w5/2JbgHp3MuciccYsiAIqwki/ec0d7871c26758bd28d40e51f130edda/SKUprice1.png)
+2. En la línea del SKU deseado, haga clic en el símbolo de signo de dólar (se le llevará al módulo Pricing).![SKUprice1](https://images.contentful.com/alneenqid6w5/2JbgHp3MuciccYsiAIqwki/ec0d7871c26758bd28d40e51f130edda/SKUprice1.png)
 3. En la columna SKU, haga clic en la celda con el nombre del SKU.
 
 En la barra lateral que aparece a la izquierda, usted verá algunas informaciones de precio para rellenar. Las más importantes son:
@@ -31,6 +31,6 @@ En la barra lateral que aparece a la izquierda, usted verá algunas informacione
 
 Al rellenar estos dos valores, el sistema le dará automáticamente el __precio base__ del producto.
 
-![SKUprice3](//images.contentful.com/alneenqid6w5/lvdNQdSq52emikM8QGImA/801b0e9fce71acbd0f923bf3db13187c/SKUprice3.gif)
+![SKUprice3](https://images.contentful.com/alneenqid6w5/lvdNQdSq52emikM8QGImA/801b0e9fce71acbd0f923bf3db13187c/SKUprice3.gif)
 
 Ahora sólo hay que definir el inventario de ese SKU para que esté disponible a sus clientes.
diff --git a/docs/tracks/es/set-the-sku-quantity-in-inventory.md b/docs/tracks/es/set-the-sku-quantity-in-inventory.md
index 315541bd7..bdc4a7e98 100644
--- a/docs/tracks/es/set-the-sku-quantity-in-inventory.md
+++ b/docs/tracks/es/set-the-sku-quantity-in-inventory.md
@@ -18,12 +18,12 @@ Usted ya tiene un producto asociado a una categoría y una marca, tiene un SKU p
 
 Para registrar el stock, siga estos pasos.
 1. En el módulo __Catalog__, pase el ratón sobre __Registro de Productos__, vaya a __Productos y SKUs__ y haga clic en la opción __Registro de Productos y SKUs__.
-2. En la línea del SKU, haga clic en el símbolo del carrito (se le llevará al módulo Logistics).![SKUstock](//images.contentful.com/alneenqid6w5/5HArBLp1qoq6cyUk8Oc8mO/473c1415e082ee2c644f5ab95f24ff73/SKUstock.png)
+2. En la línea del SKU, haga clic en el símbolo del carrito (se le llevará al módulo Logistics).![SKUstock](https://images.contentful.com/alneenqid6w5/5HArBLp1qoq6cyUk8Oc8mO/473c1415e082ee2c644f5ab95f24ff73/SKUstock.png)
 
 Usted verá una tabla con información acerca de:
 - El SKU cuya acción está editando.
-- Las cantidades de ese SKU para cada uno de sus inventarios (es probable que por el momento usted tenga solamente 1 inventario).![SKUstock3](//images.contentful.com/alneenqid6w5/1L6j4KnLm80OGIeamy2G6S/c0e141d79feed20965dd038e06ad21b7/SKUstock3.png)
+- Las cantidades de ese SKU para cada uno de sus inventarios (es probable que por el momento usted tenga solamente 1 inventario).![SKUstock3](https://images.contentful.com/alneenqid6w5/1L6j4KnLm80OGIeamy2G6S/c0e141d79feed20965dd038e06ad21b7/SKUstock3.png)
 
-En la columna __Actalizar conteo__, introduzca la cantidad de items del SKU. A continuación, haga clic en __Guardar__.![SKUstock2](//images.contentful.com/alneenqid6w5/vOnvVfbYHIu6yEgoe0gwS/2de31b3086df606783c38ded788733ae/SKUstock2.gif)
+En la columna __Actalizar conteo__, introduzca la cantidad de items del SKU. A continuación, haga clic en __Guardar__.![SKUstock2](https://images.contentful.com/alneenqid6w5/vOnvVfbYHIu6yEgoe0gwS/2de31b3086df606783c38ded788733ae/SKUstock2.gif)
 
 Listo, su SKU ahora tiene stock y ya está disponible para sus clientes.
diff --git a/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md b/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md
index 7e4928354..352b7dae6 100644
--- a/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md
+++ b/docs/tracks/es/setting-instore-up-in-a-store-easy-setup.md
@@ -26,31 +26,31 @@ Puede encontrar enlaces para descargar en: [http://instore.vtex.com/#download](h
 
 Al abrir inStore por primera vez, tendrá que introducir la cuenta VTEX donde desea configurar el inStore y hacer clic en __Confirmar__.
 
-![01 inStore selecione conta](//images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
+![01 inStore selecione conta](https://images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
 
 Al identificar que el inStore no está configurado en esta cuenta, se redirirá a la VTEX App Store en la que tendrá que iniciar sesión con su cuenta de administrador en VTEX.
 
 Después de iniciar sesión, usted podrá instalar el inStore en su cuenta.
 
-![02 inStore instalar](//images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
+![02 inStore instalar](https://images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
 
 Se mostrará un formulario de configuración, siendo el primer paso la información de dirección.
 
-![03 inStore endereco](//images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
+![03 inStore endereco](https://images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
 
 A continuación, usted debe definir un correo electrónico y una contraseña que se utilizarán como login de vendedor.
 
 > __IMPORTANTE__: ese e-mail __NO__ puede ser el mismo utilizado en la plataforma VTEX, porque su e-mail de administrador tiene permisos que un vendedor no debería tener, por lo que es necesario utilizar algún otro e-mail sin privilegios en la plataforma.
 
-![04 inStore registre vendedor](//images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
+![04 inStore registre vendedor](https://images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
 
 Después de configurar el vendedor y confirmar el código de activación recibido por correo electrónico, usted puede definir las formas de pago.
 
-![05 inStore configure pagamento](//images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
+![05 inStore configure pagamento](https://images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
 
 Si aún no tiene contrato con un adquirente, sólo puede mantener la opción __Efectivo__ activa. Al hacer clic en __Confirmar__, usted verá la pantalla de éxito.
 
-![06 inStore sucesso](//images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
+![06 inStore sucesso](https://images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
 
 Ahora basta con volver a la aplicación, iniciar sesión con las credenciales de vendedor y empezar a vender!
 
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md
index d9018f226..5fca041d1 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy-2.md
@@ -18,7 +18,7 @@ El primer paso de cualquier integración es definir la política comercial que s
 
 Una de las funciones de la política comercial es hacer una diferenciación de __catálogo__ y/o __logística__ entre los diferentes canales de venta de la tienda. Es decir, una nueva política comercial solo es necesaria cuando uno de estos factores es diferente entre los canales de venta.
 
-![carrefour.1es](//images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/9f0435400496cfcfeb6201edb5c9837f/carrefour.1es.png)
+![carrefour.1es](https://images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/9f0435400496cfcfeb6201edb5c9837f/carrefour.1es.png)
 
 La misma política comercial puede ser utilizada por más de un marketplace o entre tienda principal y marketplace. Para esto, basta con utilizar el mismo ID de política comercial en la [configuración](es/tutorial/integrando-con-marketplace). Al hacer esto, se utilizará el mismo catálogo y la misma logística para las tiendas o canales que están configurados con la misma política comercial.
 
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
index 9390225de..b2b790b96 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
@@ -18,15 +18,15 @@ El primer paso de cualquier integración es definir la política comercial que s
 
 Una de las funciones de la política comercial es hacer una diferenciación de __catálogo__ y/o __logística__ entre los diferentes canales de venta de la tienda. Es decir, una nueva política comercial solo es necesaria cuando uno de estos factores es diferente entre los canales de venta.
 
-![carrefour.1es](//images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/51afdc673afc6959b447a7c28a81f170/carrefour.1es.png)
+![carrefour.1es](https://images.ctfassets.net/alneenqid6w5/5K4NqjICKTJMoXWmaTDnpD/51afdc673afc6959b447a7c28a81f170/carrefour.1es.png)
 
 La misma política comercial puede ser utilizada por más de un marketplace o entre tienda principal y marketplace. Para esto, basta con utilizar el mismo ID de política comercial en la [configuración](es/tutorial/integrando-con-marketplace). Al hacer esto, se utilizará el mismo catálogo y la misma logística para las tiendas o canales que están configurados con la misma política comercial.
 
-![carrefour.2es](//images.ctfassets.net/alneenqid6w5/2F7jSO1EjBamKdt5ArgPjm/8a0835cd3f38702fe82c2fb187af3a11/carrefour.2es.png)
+![carrefour.2es](https://images.ctfassets.net/alneenqid6w5/2F7jSO1EjBamKdt5ArgPjm/8a0835cd3f38702fe82c2fb187af3a11/carrefour.2es.png)
 
 En otras palabras, si no es necesario definir un catálogo o un tipo de logística específicos para diferentes canales de ventas, usted tampoco necesitará utilizar políticas comerciales separadas. Basta asociar el ID de la política comercial que ya existe a su integración con el marketplace. 
 
-![carrefour.3es](//images.ctfassets.net/alneenqid6w5/3SW2dNax736jMp5eZ54gpj/646492b31b365d60cbfebde8356a9018/carrefour.3es.png)
+![carrefour.3es](https://images.ctfassets.net/alneenqid6w5/3SW2dNax736jMp5eZ54gpj/646492b31b365d60cbfebde8356a9018/carrefour.3es.png)
 
 Luego de entender esto, evalúe si es necesario configurar una nueva política comercial en su tienda. Si la respuesta es sí, siga las instrucciones de [este artículo](https://help.vtex.com/es/faq/como-contratar-nueva-politica-comercial--frequentlyAskedQuestions_700) antes de pasar a la siguiente etapa de configuración. Si su política comercial ya cumple las condiciones que necesita para la integración con el marketplace, siga las próximas instrucciones.
 
diff --git a/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
index 18546b8fe..757d20372 100644
--- a/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
@@ -16,7 +16,7 @@ trackSlugES:
 
 Este artículo tiene como objetivo explicar cómo la aplicación de inStore configura el AppLinking para las acciones de `payment` y `payment-reversal` con las apps de los adquirentes.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuración
 
diff --git a/docs/tracks/es/setting-up-the-app.md b/docs/tracks/es/setting-up-the-app.md
index 696671e9c..ebd04fb0e 100644
--- a/docs/tracks/es/setting-up-the-app.md
+++ b/docs/tracks/es/setting-up-the-app.md
@@ -34,7 +34,7 @@ Para realizar la configuración inicial del Customer Credit, siga los pasos a co
   	<li><b>Afiliación no autenticada todavía</b>: haga clic en <b>Autenticar</b> para ser redirigido a la pantalla de configuración donde deberás completar la información <b>Application Key</b> y <b>Application Token</b>. Esta acción permitirá que los pagos realizados a través de Customer Credit se procesen en su tienda. Obtenga más información en <a href="https://developers.vtex.com/docs/guides/authentication">Autenticación</a>.</li>
 </ul>
 
-![CC Configuracion 1 ES](//images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/7e7102273c6ef79723ff3124d3aab727/CC_Configuracion_1_ES.JPG)
+![CC Configuracion 1 ES](https://images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/7e7102273c6ef79723ff3124d3aab727/CC_Configuracion_1_ES.JPG)
 
 ## Configuración de app
 
@@ -56,13 +56,13 @@ Por ejemplo, para una cuenta creada con un límite de crédito de $1.000,00 y un
 Los valores de tolerancia se configuran en números decimales, donde 0 representa el 0% y 1 representa el 100%. Ejemplo: para utilizar una tolerancia del 5%, el valor a configurar es 0,05.
 </div>
 
-![CC_Configuracion_2_ES](//images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/c87641a0ebdb835abfb632fcc2ebff90/CC_Configuracion_2_ES.JPG)
+![CC_Configuracion_2_ES](https://images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/c87641a0ebdb835abfb632fcc2ebff90/CC_Configuracion_2_ES.JPG)
 
 ### Creación automática de cuenta
 
 Esta opción permite que cualquier cliente de la tienda utilice Customer Credit como método de pago, incluso si no ha creado previamente una cuenta para ellos en la aplicación Customer Credit . Al activar esta funcionalidad, también deberás definir el límite de crédito inicial que se puede utilizar para los pedidos realizados por clientes sin una cuenta de Customer Credit .
 
-![CC_Configurações_3_ES](//images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/7ff9a5cbdb0e164891c5da0931add045/CC_Configuracion_3_ES.JPG)
+![CC_Configurações_3_ES](https://images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/7ff9a5cbdb0e164891c5da0931add045/CC_Configuracion_3_ES.JPG)
 
 ### Página Mis créditos
 
@@ -70,7 +70,7 @@ Al instalar la página __Mis créditos__, permitirá a los clientes ver y admini
 
 El cliente puede acceder a esta página en el sitio web de su tienda en __Mi Cuenta > Mis Créditos__.
 
-![CC_Configuracion_4_ES](//images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/72cff75048d2ac6bb609169f73bb9c49/CC_Configuracion_4_ES.JPG)
+![CC_Configuracion_4_ES](https://images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/72cff75048d2ac6bb609169f73bb9c49/CC_Configuracion_4_ES.JPG)
 
 ### Instrucciones de pago 
 
@@ -80,15 +80,15 @@ Esta configuración permite insertar instrucciones relacionadas con el pago en l
 El mensaje registrado en esta configuración se replicará en todos las facturas emitidas para todas las cuentas de clientes de Customer Credit. No es posible configurar un mensaje único para cada cliente o factura específica.
 </div>
 
-![CC_Configuracion_5_ES](//images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/791355858bde3d7fa86eaa8b142b56e9/CC_Configuracion_5_ES.JPG)
+![CC_Configuracion_5_ES](https://images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/791355858bde3d7fa86eaa8b142b56e9/CC_Configuracion_5_ES.JPG)
 
 ### Información de identificación
 
 Esta opción le permite seleccionar qué información de identificación de la tienda debe mostrarse en la parte superior de las facturas emitidas.
 
-![CC_Configuracion_6_ES](//images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/cda6ab4a6232705bfb4323be12fc93bb/CC_Configuracion_6_ES.JPG)
+![CC_Configuracion_6_ES](https://images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/cda6ab4a6232705bfb4323be12fc93bb/CC_Configuracion_6_ES.JPG)
 
-![CC_Configuration_8_ES](//images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/708d343130c21d3c308ea058e4414c5c/CC_Configuration_8_ES.JPG)
+![CC_Configuration_8_ES](https://images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/708d343130c21d3c308ea058e4414c5c/CC_Configuration_8_ES.JPG)
 
 ## Condiciones de pago 
 
@@ -103,7 +103,7 @@ Para crear condiciones de pago para títulos de Customer Credit, siga los pasos
 5. Active la condición en el campo __Status__.
 6. En __Configura las condiciones de plazo y de pago en cuotas__, indique el número de cuotas, el plazo de vencimiento (en días) y la tasa de interés simple a aplicar a cada cuota. Para crear más de una condición de pago, haga clic en `Agregar nueva regla`.
 
-![CC_Configuration_9_ES](//images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/35c2d14c21c1e10aba4ac95f49fc3354/CC_Configuration_9_ES.JPG)
+![CC_Configuration_9_ES](https://images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/35c2d14c21c1e10aba4ac95f49fc3354/CC_Configuration_9_ES.JPG)
 
 <blockquote><ui>7. Si lo deseas también puedes <a href="https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456">Configurar condiciones especiales de pago</a>.</ui>
 
diff --git a/docs/tracks/es/setting-up-the-order-summary-printing.md b/docs/tracks/es/setting-up-the-order-summary-printing.md
index f3c1b4bd5..c77b748a9 100644
--- a/docs/tracks/es/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/es/setting-up-the-order-summary-printing.md
@@ -16,7 +16,7 @@ trackSlugES: instore-personalizaciones
 
 Cuando el vendedor completa un pedido con inStore, puede imprimir un resumen de ese pedido. Pero, para habilitar esta funcionalidad, usted debe realizar algunas configuraciones.
 
-![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
+![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
 
 Se requieren dos pasos:
 
@@ -50,7 +50,7 @@ No elimine ninguna de las otras propiedades presentes en el objeto <code>window.
 
 Este cambio hará que la opción __Configurar dispositivo__ aparezca en el menú principal de inStore, como se muestra en la imagen a continuación. Es a través de esta opción que configuraremos la impresora.
 
-![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
+![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> hay una opción para imprimir automáticamente el resumen del pedido tan pronto como se complete el pedido. Para habilitarla, agregue la propiedad <code>printPageAutomatically</code> con el valor <code>true</code> dentro del objeto <code>printingConfig</code>. Vea a continuación cómo se vería el código en este caso.
@@ -84,11 +84,11 @@ Con AppKey y AppToken en mano, siga los pasos a continuación:
 2. Abra la aplicación inStore e ingrese a la tienda donde desea configurar la impresora.
 3. En el menú principal de inStore, en la sección Configuración, ahora debería aparecer la opción __Configurar dispositivo__. Haga clic en esa opción.
 
-![15. Configurar impressão de resumo do pedido - 3](//images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
+![15. Configurar impressão de resumo do pedido - 3](https://images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
 
 Usted encontrará el resumen del dispositivo configurado. Si es la primera vez que realiza esta configuración, los campos en esta pantalla estarán vacíos. Si un dispositivo se ha configurado previamente, mostrarán algumas informaciones sobre el dispositivo (nombre del dispositivo e impresora predeterminada). Haga clic en el botón __Editar__.
 
-![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 Aparecerá un formulario que contiene los campos __AppKey__, __AppToken__ y __Nome__ con los que desea identificar el dispositivo. Después de ingresar estos datos, haga clic en __Configurar__.
 
diff --git a/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
index e8154e440..91de93c59 100644
--- a/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
@@ -37,7 +37,7 @@ Esta opción permite compartir un carrito lleno de ítems con uno o más cliente
 
 Vea el paso a paso que se muestra a continuación.
 
-![socialselling-sugestaocarrinho-es](//images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/dccf53fd6fdac19cd750717c4dd4a0be/socialselling-sugestaocarrinho-es.gif)
+![socialselling-sugestaocarrinho-es](https://images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/dccf53fd6fdac19cd750717c4dd4a0be/socialselling-sugestaocarrinho-es.gif)
 
 El vendedor puede enviar el mismo enlace a varios clientes, tantas veces como lo desee. Cada vez que una persona acceda a este enlace, se generará un nuevo carrito de compra, exactamente igual al creado en VTEX Sales App. Cada carrito al que se accede también está asociado a la cuenta del vendedor y, si existe, al código del vendedor.
 
@@ -63,4 +63,4 @@ En este caso, el vendedor tiene que poner los ítems en el carrito, rellenar los
 
 Vea el paso a paso que se muestra a continuación.
 
-![socialselling-paymentlink-es](//images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/3690f99dd3ac16dd3ae0f90c2bf85cc1/socialselling-paymentlink-es.gif)
+![socialselling-paymentlink-es](https://images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/3690f99dd3ac16dd3ae0f90c2bf85cc1/socialselling-paymentlink-es.gif)
diff --git a/docs/tracks/es/shipping-strategies.md b/docs/tracks/es/shipping-strategies.md
index 512d753e7..7829b1c6c 100644
--- a/docs/tracks/es/shipping-strategies.md
+++ b/docs/tracks/es/shipping-strategies.md
@@ -18,7 +18,7 @@ Las opciones de envío a disposición del cliente en el _checkout_ de tu tienda
 
 La estrategia de envío define cómo los almacenes, muelles y políticas de envío interactúan para atender las necesidades de tus clientes y de tu empresa. 
 
-![Estrategia EnvioES](//images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/d0349a827fc24a4c5a3e1782289fd8c0/Estrategia_EnvioES.png)
+![Estrategia EnvioES](https://images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/d0349a827fc24a4c5a3e1782289fd8c0/Estrategia_EnvioES.png)
 
 La estrategia de envío está definida por tres entidades logísticas:
 
diff --git a/docs/tracks/es/size-chart.md b/docs/tracks/es/size-chart.md
index 3f9383182..441e9fc34 100644
--- a/docs/tracks/es/size-chart.md
+++ b/docs/tracks/es/size-chart.md
@@ -18,7 +18,7 @@ Al comprar ropa o calzados en línea, muchos usuarios suelen tener preguntas sob
 
 La guía de tallas de Mercado Libre es una tabla de medidas o equivalencias que permite que los usuarios vean las medidas exactas para que puedan elegir el producto ideal para ellos. 
 
-![MLB tamanosARG](//images.ctfassets.net/alneenqid6w5/4xmAfYyY7z2sVGNKAaR2XM/404d040e8a9bae57b462da40b78e2321/MLB_tamanosARG.gif)
+![MLB tamanosARG](https://images.ctfassets.net/alneenqid6w5/4xmAfYyY7z2sVGNKAaR2XM/404d040e8a9bae57b462da40b78e2321/MLB_tamanosARG.gif)
 
 ## Entendiendo la guía de tallas
 
diff --git a/docs/tracks/es/store-development.md b/docs/tracks/es/store-development.md
index 5abbd1c48..4c6a194ef 100644
--- a/docs/tracks/es/store-development.md
+++ b/docs/tracks/es/store-development.md
@@ -19,7 +19,7 @@ En una tienda de ecommerce, tanto la interfaz que los usuarios ven y con la que
 - **Frontend**: el frontend comprende la capa visual de una aplicación, como la interfaz de un sitio web o de una aplicación móvil. A través del frontend, los usuarios interactúan con la tienda. En VTEX, hay tres tecnologías diferentes que pueden utilizarse para el desarrollo del storefront de la tienda: CMS Portal (Legado), Store Framework y FastStore.
 - **Backend**: el backend es la capa que computa y procesa todos los datos necesarios para ejecutar las funcionalidades ofrecidas por una determinada aplicación. En VTEX, el desarrollo de integraciones y aplicaciones backend mayormente se realiza a través de VTEX IO y de las API de VTEX.
 
-![storefront mockup](//images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/f7db8614b227a93b636b593870dab50c/image1.png)
+![storefront mockup](https://images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/f7db8614b227a93b636b593870dab50c/image1.png)
 
 En las siguientes secciones, profundizaremos en los principales aspectos y tecnologías relacionados con el desarrollo de la tienda en VTEX.
 
diff --git a/docs/tracks/es/technical-support.md b/docs/tracks/es/technical-support.md
index 05cc04710..bd2d56bf7 100644
--- a/docs/tracks/es/technical-support.md
+++ b/docs/tracks/es/technical-support.md
@@ -29,6 +29,6 @@ La siguiente tabla muestra los principales temas relacionados con el soporte té
 
 Si el usuario necesita soporte técnico y no encuentra respuesta en los portales y documentación mencionados, puede contactarnos a través de la página de soporte  y elegir la opción **Técnico** a través del VTEX AI Support Bot, un chatbot dedicado a la asistencia técnica, como se muestra en la imagen a continuación:
 
-![Support imagem 2 -ES](//images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/889524bdd11a69c86f075412447b03e2/suppot_imagem2_ES.png)
+![Support imagem 2 -ES](https://images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/889524bdd11a69c86f075412447b03e2/suppot_imagem2_ES.png)
 
 Si el usuario necesita soporte más allá del VTEX AI Support Bot, puede abrir un ticket haciendo clic en `ABRIR TICKET`. Para más información sobre cómo rellenar un ticket para el soporte técnico, consulta el artículo [Abrir ticket para soporte VTEX - Técnico](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#tecnico).
diff --git a/docs/tracks/es/the-reservation.md b/docs/tracks/es/the-reservation.md
index 4e2584fa7..17d4f653c 100644
--- a/docs/tracks/es/the-reservation.md
+++ b/docs/tracks/es/the-reservation.md
@@ -34,7 +34,7 @@ Este es el flujo de reserva en VTEX:
 
  3. Finalmente, una vez que el pedido se encuentra en la etapa de preparación para la entrega, los artículos pasan al estado `Reserva Reconocida`. Este estado indica que el artículo ya no existe en el inventario físico.  
 
-![reservation es](//images.ctfassets.net/alneenqid6w5/3qiFEUNLlkbc403lzwFCdS/31eaafb108b2e75685cc33441f127407/reservation_es.png)
+![reservation es](https://images.ctfassets.net/alneenqid6w5/3qiFEUNLlkbc403lzwFCdS/31eaafb108b2e75685cc33441f127407/reservation_es.png)
 
 <div class="alert alert-warning">
 VTEX no quita automáticamente los artículos del inventario, incluso después de que hayan pasado al estado <code>Reserva Reconocida</code>. Los artículos comprados permanecerán en este estado hasta que el ERP o la tienda los quiten del inventario.
diff --git a/docs/tracks/es/the-transaction-flow.md b/docs/tracks/es/the-transaction-flow.md
index 7b90c5dd1..daec00306 100644
--- a/docs/tracks/es/the-transaction-flow.md
+++ b/docs/tracks/es/the-transaction-flow.md
@@ -22,7 +22,7 @@ Las transacciones realizadas por el módulo de pagos de VTEX pasan por diversos
 
 Vea abajo un ejemplo de la línea de tiempo con los status de la transacción.
 
-![Transaction Flow](//images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
+![Transaction Flow](https://images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
 
 1. __Authorizing__: Este es el primer status de una transacción en Pagos. En esta etapa, Pagos indica que se ha iniciado el proceso de envío de información a un adquirente o a otro gateway.
 2. __Authorized__: Una vez iniciado el proceso de autorización, el adquirente u otro gateway envía la información de la transacción al banco emisor. El banco responde si la transacción debe ser o no autorizada. Si niega la transacción, el pago es __cancelado__. Si la autoriza, el status de la transacción pasa a __Authorized__.
diff --git a/docs/tracks/es/unified-commerce-101.md b/docs/tracks/es/unified-commerce-101.md
index bd3ce12d1..35277f6da 100644
--- a/docs/tracks/es/unified-commerce-101.md
+++ b/docs/tracks/es/unified-commerce-101.md
@@ -16,7 +16,7 @@ trackSlugES: estrategias-de-comercio-unificado
 
 La evolución del comercio en línea ha traído una serie de mejoras a la experiencia del cliente, y una de las más relevantes es quizás la que transformó la relación multicanal entre el cliente y la tienda en una relación omnicanal.
 
-![32. Unified Commerce 101 - 1 - ES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/3WXokD0CaXdjQIp78KVZ9K/91a5153042717c725708d7a4e289fde4/32._Unified_Commerce_101_-_1_-_ES.png_h_250_h_250)
+![32. Unified Commerce 101 - 1 - ES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/3WXokD0CaXdjQIp78KVZ9K/91a5153042717c725708d7a4e289fde4/32._Unified_Commerce_101_-_1_-_ES.png_h_250_h_250)
 
 En una arquitectura __multicanal__, cada canal se comunica independientemente con la tienda, ya sea comercio electrónico, tiendas físicas, call center, redes sociales, etc. Cuando un cliente interactúa con uno de estos canales, la tienda no tiene conocimiento de quién es ese cliente.
 
@@ -26,7 +26,7 @@ En el omnichannel, sin embargo, los pedidos aún se procesan de forma aislada. A
 
 El __Comercio Unificado__ resuleve ese problema.
 
-![32. Unified Commerce 101 - 2 - ES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/6nzjDTPhDPePrbcG2lYuV9/39f8bc1548b7c31d13d11bb491540d55/32._Unified_Commerce_101_-_2_-_ES.png_h_250_h_250)
+![32. Unified Commerce 101 - 2 - ES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/6nzjDTPhDPePrbcG2lYuV9/39f8bc1548b7c31d13d11bb491540d55/32._Unified_Commerce_101_-_2_-_ES.png_h_250_h_250)
 
 El Comercio Unificado es una evolución del omnichannel: además del intercambio de datos, esta estrategia también implica __unificar el sistema de procesamiento y gestión de pedidos__. En la práctica, esto significa que todos los pedidos realizados en un canal de la tienda no solo son visibles por otros canales, sino que también pueden ser procesados por ellos.
 
diff --git a/docs/tracks/es/unified-commerce.md b/docs/tracks/es/unified-commerce.md
index 9f585e76b..710ce5e93 100644
--- a/docs/tracks/es/unified-commerce.md
+++ b/docs/tracks/es/unified-commerce.md
@@ -22,7 +22,7 @@ El [comercio unificado](https://help.vtex.com/es/tracks/estrategias-de-comercio-
 
 Las [cuentas franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) son cuentas asociadas a una [cuenta principal](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). Las empresas que tienen varias tiendas físicas, franquicia o multimarca pueden crear cuentas franquicia vinculadas a la cuenta principal de la marca.
 
-![cuenta principal](//images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/4cc2eed8bca448fa38b8eb39a8428e52/next_steps_image1_ES.png)
+![cuenta principal](https://images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/4cc2eed8bca448fa38b8eb39a8428e52/next_steps_image1_ES.png)
 
 Este modelo comparte la información del catálogo y [storefront](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), permitiendo que el stock de las cuentas franquicia esté disponible para la venta en la cuenta principal y que se puedan utilizar varias estrategias de comercio unificado, tales como [envío desde la tienda](#envio-desde-la-tienda), [tiendas físicas como puntos de recogida](#punto-de-recogida) y [pasillo infinito](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
 
diff --git a/docs/tracks/es/unified-search.md b/docs/tracks/es/unified-search.md
index da4fa0b22..ea138e406 100644
--- a/docs/tracks/es/unified-search.md
+++ b/docs/tracks/es/unified-search.md
@@ -21,13 +21,13 @@ El [pasillo infinito](https://help.vtex.com/es/tracks/estrategias-de-comercio-un
 Para mejorar la experiencia en situaciones en que la conexión de internet esté lenta, esta funcionalidad tiene recursos de optimización que utilizan la caché del navegador para agilizar la búsqueda.
 </div>
 
-![Barra busca - ES](//images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/1ad8c720186c675630364918f1d9e0f1/Tela_1_barra_busca.gif)
+![Barra busca - ES](https://images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/1ad8c720186c675630364918f1d9e0f1/Tela_1_barra_busca.gif)
 
 La búsqueda de VTEX Sales App es unificada, lo que significa que al realizar una búsqueda los resultados se obtienen tanto del stock local (de la tienda física) como de otras tiendas físicas y centros de distribución asociados a la tienda de ecommerce.
 
 Los resultados de búsqueda muestran los productos organizados para mejorar la experiencia del cliente, incluyendo imágenes que facilitan la identificación de los productos e información relevante para el vendedor.
 
-![Busca unificada - ES](//images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/a94fdd1ace89c89f2081c9fb43174216/Busca_unificada_VTEX_Sales_App.png)
+![Busca unificada - ES](https://images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/a94fdd1ace89c89f2081c9fb43174216/Busca_unificada_VTEX_Sales_App.png)
 
 Al hacer clic en la opción `Agregar al carrito`, se mostrará la siguiente información del producto:
 
@@ -37,7 +37,7 @@ Al hacer clic en la opción `Agregar al carrito`, se mostrará la siguiente info
 
 Para agregar el producto al carrito, selecciona la variación, envío y cantidad deseada y haz clic en `Agregar al carrito`.
 
-![Carrinho - ES](//images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/defe694e7ce4805172e3879c78411c3c/Adicionar_ao_carrinho_VTEX_Sales_App.png)
+![Carrinho - ES](https://images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/defe694e7ce4805172e3879c78411c3c/Adicionar_ao_carrinho_VTEX_Sales_App.png)
 
 ## Filtros
 
diff --git a/docs/tracks/es/using-custom-controls.md b/docs/tracks/es/using-custom-controls.md
index cac3e5e6b..c58c5fd14 100644
--- a/docs/tracks/es/using-custom-controls.md
+++ b/docs/tracks/es/using-custom-controls.md
@@ -30,7 +30,7 @@ Para crear un control personalizado, siga el procedimiento a continuación:
 2. Haga clic en __Layout__
 3. Haga clic en la carpeta __CMS__
 4. A continuación, haga clic en la carpeta __Custom Elements__
-5. Haga clic en el botón __Add__![8 1](//images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
+5. Haga clic en el botón __Add__![8 1](https://images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
 6. Complete el campo __Name__ con el nombre del control personalizado
 7. Complete el campo __Tag name__. Este es el nombre que se usará en el control al agregarlo al template
 8. Seleccione el tipo de control en __Type__
diff --git a/docs/tracks/es/vtex-modules-i.md b/docs/tracks/es/vtex-modules-i.md
index 6895ef93a..2a7ef7ec4 100644
--- a/docs/tracks/es/vtex-modules-i.md
+++ b/docs/tracks/es/vtex-modules-i.md
@@ -40,7 +40,7 @@ No se requieren ajustes preliminares antes de realizar configuraciones en Catál
 
 La arquitectura de Catálogo presenta algunos conceptos fundamentales: categoría, marca, producto, SKU (_Stock Keeping Unit_) y especificación. La siguiente imagen ilustra la relación entre estos conceptos:
 
-![arquitetura-catalogo-ES](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
+![arquitetura-catalogo-ES](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/93df901612fa89e7b315cee7b7d121ae/ES.png)
 
 El catálogo de la tienda debe crearse siguiendo el orden de los pasos que se indican a continuación:
 
@@ -77,7 +77,7 @@ __Ejemplo__: Departamento `Femenino`, Categoría `Blusas y camisas` y Subcategor
 
 Antes de importar el catálogo de la tienda a VTEX, recomendamos empezar a trabajar en el árbol de categorías creando una tabla como la que se ilustra a continuación. Esto facilita la visualización de la estructura del árbol y la presentación de las especificaciones.
 
-![catalog_arquitecture_table_ES](//images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/60756721b1e21b27b981dee2f2a5e9ad/catalog_arquitecture_table_ES.png)
+![catalog_arquitecture_table_ES](https://images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/60756721b1e21b27b981dee2f2a5e9ad/catalog_arquitecture_table_ES.png)
 
 <div class="alert alert-info">
 En el artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a> puedes consultar más información sobre cómo importar especificaciones para back office.
@@ -158,7 +158,7 @@ Los precios son la información del valor de venta de tus SKU. Estos precios se
 
 La relación entre los precios, la tabla de precios y el contexto que se aplicará se muestra en la siguiente imagen:
 
-![Conceito de Precios-ES](//images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/2a14232018aea8b88b70c21d5a9b6618/Conceito_de_Precios-ES.png)
+![Conceito de Precios-ES](https://images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/2a14232018aea8b88b70c21d5a9b6618/Conceito_de_Precios-ES.png)
 
 Puedes registrar tablas de precios para los SKU de la tienda de tres maneras:
 
@@ -278,7 +278,7 @@ El conjunto de configuraciones esenciales de logística para una tienda VTEX se
 
 La imagen siguiente muestra cómo se relacionan estos conceptos en la venta de un producto:
 
-![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
+![shipping_strategy_ES](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
 
 La siguiente tabla muestra los principales ajustes de logística de la tienda VTEX:
 
@@ -331,7 +331,7 @@ Entre los [principales casos de uso](https://help.vtex.com/es/tutorial/lead_time
 
 Para realizar el [cálculo de envio](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) de los pedidos, la plataforma VTEX considera las siguientes configuraciones:
 
-![Envío de Pedidos_ES](//images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/19fd25987e328aeb22f03f48764b2479/Env_o_de_Pedidos_ES.png)
+![Envío de Pedidos_ES](https://images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/19fd25987e328aeb22f03f48764b2479/Env_o_de_Pedidos_ES.png)
 
 - [Lead time](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B): cantidad de tiempo configurable para el SKU de un almacén. Esta configuración es opcional y se establece en cero días de forma predeterminada.
 - [Tiempo de almacén](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137): tiempo que tarda el SKU en pasar del almacén al [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Esta configuración es obligatoria, pero el tiempo puede establecerse en cero.
diff --git a/docs/tracks/es/vtex-modules-ii.md b/docs/tracks/es/vtex-modules-ii.md
index 52ceb26f6..e8542287c 100644
--- a/docs/tracks/es/vtex-modules-ii.md
+++ b/docs/tracks/es/vtex-modules-ii.md
@@ -55,11 +55,11 @@ La siguiente tabla muestra los principales agentes y términos utilizados en el
 
 Cuando se finaliza una compra en VTEX, se crea una nueva transacción y se inicia el flujo de pago. El siguiente ejemplo muestra el flujo de pago para una compra realizada con tarjeta de crédito:
 
-![payments-es](//images.ctfassets.net/alneenqid6w5/5QPFkvZhpZzRWuq15zlMoz/1a6dd2fc04096a775c1208ff0e20088a/payments_image1_ES.JPG)
+![payments-es](https://images.ctfassets.net/alneenqid6w5/5QPFkvZhpZzRWuq15zlMoz/1a6dd2fc04096a775c1208ff0e20088a/payments_image1_ES.JPG)
 
 A medida que la información se transmite entre los agentes encargados de procesar los datos, el status de la transacción del pago se actualiza para indicar en qué etapa del flujo se encuentran los recursos. Para ilustrar el flujo de pago con tarjeta de crédito, tenemos el siguiente ejemplo de status de la transacción:
 
-![payments-flow-es](//images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/4d17ee553dfe4fadfdc59a502339159e/payments_image2_ALL.JPG)
+![payments-flow-es](https://images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/4d17ee553dfe4fadfdc59a502339159e/payments_image2_ALL.JPG)
 
 Consulta más información sobre cada paso en el artículo [Flujo de la transacción en Pagos](https://help.vtex.com/es/tutorial/flujo-de-la-transaccion-en-pagos--Er2oWmqPIWWyeIy4IoEoQ). Para acceder a más información sobre transacciones en el Admin VTEX, consulta el artículo [Ver detalles de la transacción](https://help.vtex.com/es/tracks/pagos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
 
@@ -182,7 +182,7 @@ En el Admin VTEX, en **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tu
 
 En la página de detalles del pedido, también puede monitorearse la información del [flujo del pedido](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196). La imagen siguiente ilustra un ejemplo del flujo cuando la tienda actúa simultáneamente como marketplace y seller:
 
-![order-flow-es](//images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/7cb86712ed404f7ae9a8d804820ae673/pedido_fluxo_completo_es.png)
+![order-flow-es](https://images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/7cb86712ed404f7ae9a8d804820ae673/pedido_fluxo_completo_es.png)
 
 Para ubicar el registro de una compra en el Admin VTEX, además de poder [filtrar pedidos](https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192) en la página **Todos los pedidos**, existe la opción de buscar a través de la barra de búsqueda global, presente en todas las páginas del Admin VTEX. Para realizar la búsqueda solo hay que seleccionar la opción `Pedidos` en la esquina derecha de la barra de búsqueda y utilizar cualquiera de los siguientes valores:
 
@@ -236,7 +236,7 @@ El checkout es la etapa final en el proceso de compras online y contribuye de ma
 
 Para garantizar el correcto funcionamiento del checkout, los siguientes módulos deben ser debidamente configurados en la tienda: [Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), [Logística](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx), [Precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP#), [Promociones](https://help.vtex.com/es/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#), [Pagos](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#) y [Pedidos](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE).
 
-![checkout-es](//images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/2c7ccff2d662fb9bff20c549819f1576/checkout_image_ES.jpg)
+![checkout-es](https://images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/2c7ccff2d662fb9bff20c549819f1576/checkout_image_ES.jpg)
 
 Este intercambio de información permite procesar datos sobre disponibilidad, precios, promociones aplicables, métodos de envío y medios de pago.
 
diff --git a/docs/tracks/es/what-is-a-logistics-route.md b/docs/tracks/es/what-is-a-logistics-route.md
index 391c714dd..b125fed47 100644
--- a/docs/tracks/es/what-is-a-logistics-route.md
+++ b/docs/tracks/es/what-is-a-logistics-route.md
@@ -33,5 +33,5 @@ Para registrar un muelle en el admin de la tienda, siga los pasos indicados en e
 ### Transportadora
 Es a partir de aquí que los pedidos se distribuyen a sus destinos finales. Una transportadora está compuesta por la flota de vehículos que realizarán las entregas. Por lo tanto, los pedidos salen  del centro de distribución directo a la transportadora que completa el proceso hasta el cliente final.
 
-![ES Conceitos Logística](//images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
+![ES Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/6BRAmfZf1X7QPkYrh9bZar/a17438d4438465cde7b9b88689dd0b18/ES_Conceitos_Log__stica.png)
 
diff --git a/docs/tracks/es/what-is-the-master-user.md b/docs/tracks/es/what-is-the-master-user.md
index 460ee9021..a9a4d59e6 100644
--- a/docs/tracks/es/what-is-the-master-user.md
+++ b/docs/tracks/es/what-is-the-master-user.md
@@ -26,7 +26,7 @@ Si su usuario tiene perfil de acceso al módulo Gestión de la cuenta, usted pue
 
 Al hacer clic en el nombre de la cuenta deseada, el nombre y el correo electrónico del usuario Titular se encuentran en la sección __Contacto__.
 
-![usuario-master-contato es](//images.ctfassets.net/alneenqid6w5/2lYlZR55HqYSk4aoGMCCI6/eea8b18ab53d475f046820db05eb717c/contato_usuario_master_es.png)
+![usuario-master-contato es](https://images.ctfassets.net/alneenqid6w5/2lYlZR55HqYSk4aoGMCCI6/eea8b18ab53d475f046820db05eb717c/contato_usuario_master_es.png)
 
 Entre las acciones que sólo el usuario Titular puede tomar, están:
 - Reindexar el catálogo.
diff --git a/docs/tracks/es/whatsapp-integration.md b/docs/tracks/es/whatsapp-integration.md
index 7d8b4994c..bf4f31d1b 100644
--- a/docs/tracks/es/whatsapp-integration.md
+++ b/docs/tracks/es/whatsapp-integration.md
@@ -62,17 +62,17 @@ Una vez instalada la aplicación, VTEX compartirá la URL del Admin de VTEX Conv
 Con esta información, sigue los pasos a continuación.
 
 1. Accede al VTEX Admin a través de la URL que te ha enviado el equipo de soporte. Verás la siguiente pantalla:
-![Track 101 - Conversational Commerce 1 - PT](//images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 1 - PT](https://images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
 2. Haz clic en el botón `Configurar la cuenta de WhatsApp Business`.
 3. Se abrirá una ventana de Facebook para la configuración. Inicia sesión con el perfil de administrador deseado de Business Manager.
 4. Selecciona la opción `Crear una cuenta de WhatsApp Business`.
 5. Introduce el nombre de la cuenta que se mostrará como nombre de perfil en WhatsApp.
 6. Selecciona la categoría y introduce la descripción de la cuenta. 
-![Track 101 - Conversational Commerce 2 - PT](//images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 2 - PT](https://images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
 7. Verifica el número de teléfono que se asociará a la cuenta mediante el código enviado al teléfono.
 8. Comunica al equipo de soporte de VTEX para que finalice la configuración.
 
 Una vez completada la configuración, se mostrará la alerta de abajo en el Admin. 
 
-![Track 101 - Conversational Commerce 3 - PT](//images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 3 - PT](https://images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
 
diff --git a/docs/tracks/pt/access-to-the-customers-last-cart.md b/docs/tracks/pt/access-to-the-customers-last-cart.md
index ccc545504..94892caa5 100644
--- a/docs/tracks/pt/access-to-the-customers-last-cart.md
+++ b/docs/tracks/pt/access-to-the-customers-last-cart.md
@@ -20,4 +20,4 @@ Ao ter acesso a essa informação, o vendedor pode tentar concluir a venda dos i
 
 Basta clicar em `Acessar` para ver os produtos do carrinho abandonado.
 
-![last-cart-pt](//images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/2cccf8f174d42a76d25c0811782dc79e/last-cart-PT.png)
+![last-cart-pt](https://images.ctfassets.net/alneenqid6w5/5A40nJsnX5wRDlHJGn9ZsD/2cccf8f174d42a76d25c0811782dc79e/last-cart-PT.png)
diff --git a/docs/tracks/pt/accounts-and-architecture.md b/docs/tracks/pt/accounts-and-architecture.md
index 0b6e31d66..aaf06c1de 100644
--- a/docs/tracks/pt/accounts-and-architecture.md
+++ b/docs/tracks/pt/accounts-and-architecture.md
@@ -27,7 +27,7 @@ Os tipos de conta que existem na VTEX são:
 
 A imagem a seguir é uma visão geral para auxiliar a [escolher entre contas padrão, franquia ou Seller Portal](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78):
 
-![main_account_franchise_seller_portal_PT](//images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/dc7b2ca283b2613838a840589bf3b9d3/main_account_franchise_seller_portal_PT.png)
+![main_account_franchise_seller_portal_PT](https://images.ctfassets.net/alneenqid6w5/4NfyGbu9eVJFRc6EfCpTHr/dc7b2ca283b2613838a840589bf3b9d3/main_account_franchise_seller_portal_PT.png)
 
 ## Recursos das contas
 
@@ -54,7 +54,7 @@ No entanto, o uso simultâneo de muitas políticas comerciais pode comprometer a
 
 A imagem a seguir é um exemplo de como conta principal, ambiente (subconta), multilojas (lojas) e políticas comerciais estão relacionados:
 
-![multistore_aditional_environment_PT](//images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/c91d697c801dd5fb42e7186e697b2abb/multistore_aditional_environment_PT.png)
+![multistore_aditional_environment_PT](https://images.ctfassets.net/alneenqid6w5/6XOI59M49L18E99hSDpgWe/c91d697c801dd5fb42e7186e697b2abb/multistore_aditional_environment_PT.png)
 
 ### Multiloja
 
diff --git a/docs/tracks/pt/add-an-image-to-the-sku.md b/docs/tracks/pt/add-an-image-to-the-sku.md
index a903bf051..73c85f722 100644
--- a/docs/tracks/pt/add-an-image-to-the-sku.md
+++ b/docs/tracks/pt/add-an-image-to-the-sku.md
@@ -22,7 +22,7 @@ Se nenhuma imagem for associada a um SKU, ele não ficará ativo.
 
 Por isso, depois que terminar de preencher as configurações do seu novo SKU e clicar em __Salvar__, você será levado para a tela de cadastro de imagem, onde a mensagem abaixo é exibida.
 
-![SKUimg](//images.contentful.com/alneenqid6w5/2lV4fLbTJqEiCmUQOaaOOm/c7480c2c8095f51c8236d2022991fe43/SKUimg.png)
+![SKUimg](https://images.contentful.com/alneenqid6w5/2lV4fLbTJqEiCmUQOaaOOm/c7480c2c8095f51c8236d2022991fe43/SKUimg.png)
 
 Para associar uma imagem a esse SKU, siga os passos abaixo:
 1. Clique no botão __Inserir__.
@@ -31,4 +31,4 @@ Para associar uma imagem a esse SKU, siga os passos abaixo:
 4. Clique no botão __Enviar__.
 5. Clique em __Salvar__.
 
-![SKUimg3](//images.contentful.com/alneenqid6w5/5E5rl4SdC8a4qSy40Gqaum/7e000aebd9a7f7087229f630f8a6c38d/SKUimg3.gif)
+![SKUimg3](https://images.contentful.com/alneenqid6w5/5E5rl4SdC8a4qSy40Gqaum/7e000aebd9a7f7087229f630f8a6c38d/SKUimg3.gif)
diff --git a/docs/tracks/pt/add-on-products.md b/docs/tracks/pt/add-on-products.md
index 7f7fd11b4..a5bfde31e 100644
--- a/docs/tracks/pt/add-on-products.md
+++ b/docs/tracks/pt/add-on-products.md
@@ -27,18 +27,18 @@ O [VTEX Ad Network](https://help.vtex.com/tutorial/vtex-ad-network-beta--2cgqXcB
 - **Anunciantes:** marcas, que podem criar campanhas de anúncios para promover seus produtos nas frentes de lojas VTEX que possuem aqueles produtos em seus catálogos, aumentando suas vendas.
 - **Lojas VTEX:** podem disponibilizar espaço publicitário para que marcas promovam seus produtos na sua frente de loja. Estas lojas receberão um valor por cada clique recebido em anúncios na sua loja.
 
-![vtex_ad_network_sponsored_PT](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_PT](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
 
 ## VTEX Assisted Sales
 
 [Assisted Sales (SuiteShare)](https://help.vtex.com/pt/tracks/suiteshare--khP0p8mjIYRIpvM7Cb4Zr/onWmyS8j4Thhde67UBBsB) é a solução criada pela VTEX para impulsionamento de vendas no WhatsApp. Por meio dela, é possível atrair novos clientes, integrar ferramentas de vendas, gerenciar dados de atendimento do usuário e métricas de resultados.
 
-![suitshare-pt](//images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/23ef16a09a1c9b86b743059ba4c364ef/next_steps_image11_ONLYPT.JPG)
+![suitshare-pt](https://images.ctfassets.net/alneenqid6w5/6TuLLNIaD33jhiLdtECaM2/23ef16a09a1c9b86b743059ba4c364ef/next_steps_image11_ONLYPT.JPG)
 
 ## VTEX Live Shopping
 Solução que permite a criação de transmissões online para a realização de demonstrações ao vivo das características dos produtos na loja. Interações diretas e instantâneas com os clientes permitem melhorar o engajamento do público com a marca e contribuem para aumentar a performance de venda.
 
-![live-shopping-pt](//images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/aa4276798ea8f4a5edc2b61cab366154/next_steps_image5_ALL.JPG)
+![live-shopping-pt](https://images.ctfassets.net/alneenqid6w5/2ayznZWJIuJDSBxaviiL2M/aa4276798ea8f4a5edc2b61cab366154/next_steps_image5_ALL.JPG)
 
 Para agendar uma demonstração do aplicativo com um especialista, é preciso acessar a página sobre [VTEX Live Shopping](https://vtex.com/br-pt/live-shopping/#contact).
 
@@ -46,7 +46,7 @@ Para agendar uma demonstração do aplicativo com um especialista, é preciso ac
 
 Solução que permite o atendimento personalizado direto entre o cliente e o vendedor, trazendo a experiência de compra da loja física para o ambiente digital. Por meio deste aplicativo, o vendedor tem a possibilidade demonstrar produtos, fazer recomendações e esclarecer dúvidas dos clientes. Durante a videochamada, também é possível adicionar itens no carrinho de compras.
 
-![personal-shopper-pt](//images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/0853e4731a4f6b688fe214bde2f88d70/next_steps_image6_ALL.JPG)
+![personal-shopper-pt](https://images.ctfassets.net/alneenqid6w5/6KKt1hJ8CVHx2ezrbo7L8h/0853e4731a4f6b688fe214bde2f88d70/next_steps_image6_ALL.JPG)
 
 ## VTEX Pick and Pack
 
@@ -57,7 +57,7 @@ O **VTEX Pick and Pack** é composto por:
 - [Pick and Pack app](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA): gerencia pedidos na loja ou depósito, permitindo personalizar o método de separação de pedidos, selecionar tipos de embalagens por produto, remover ou adicionar produtos de acordo com o estoque da loja.
 - [Last Mile app](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr): coordena o envio de pacotes a partir de depósitos ou lojas até os endereços, criando rotas inteligentes de entrega, selecionando motoristas disponíveis, e rastreando a localização exata do pedido.
 
-![pick-and-pack-pt](//images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/61b013dcf10e9427d68f42b909ba0c23/next_steps_image7_ALL.JPG)
+![pick-and-pack-pt](https://images.ctfassets.net/alneenqid6w5/6QOR5fOlkCV3RpE0Se3fdM/61b013dcf10e9427d68f42b909ba0c23/next_steps_image7_ALL.JPG)
 
 Para assistir uma demonstração do aplicativo ou agendar o atendimento personalizado com um especialista, é preciso acessar a página sobre [VTEX Pick and Pack](https://content.vtex.com/pt-br/pick-and-pack/). 
 
@@ -70,7 +70,7 @@ Com o [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-
 - Oferecer opções de entrega instantânea, retirada agendada ou no local do cliente.
 - Gerenciar métricas de performance para cada vendedor.
 
-![sales-app-pt](//images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/e5e9b59e94c59f05ffb9cead6d2f7d93/image3.png)
+![sales-app-pt](https://images.ctfassets.net/alneenqid6w5/5AIDSFirQO1LJmXFtoPc9L/e5e9b59e94c59f05ffb9cead6d2f7d93/image3.png)
 
 Para assistir uma demonstração do aplicativo ou agendar o atendimento personalizado com um especialista, é preciso acessar a página sobre [VTEX Sales App](https://assets.vtex.com/sales-app/).
 
@@ -80,7 +80,7 @@ Explore opções de envio de produtos para todas as regiões do Brasil com o [VT
 
 O **VTEX Shipping Network** proporciona a possibilidade de conectar transportadoras para criar uma rede integrada de entrega, atualmente com mais de 20 parceiros, para oferecer as melhores opções de custo e prazo aos clientes. 
 
-![shipping-network-pt](//images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/573663b07a3ec62b235be4037b75b93e/image7.png)
+![shipping-network-pt](https://images.ctfassets.net/alneenqid6w5/37E5iPi055VVgdvk96Jye9/573663b07a3ec62b235be4037b75b93e/image7.png)
 
 Para mais informações, é preciso acessar a página sobre [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/).
 
@@ -92,7 +92,7 @@ Para mais informações, é preciso acessar a página sobre [VTEX Shipping Netwo
 
 O [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) é uma parceria entre a VTEX e os Correios na qual a loja pode contratar serviços de envio de produtos via PAC e SEDEX diretamente no Admin VTEX, com taxas diferenciadas que reduzem os custos operacionais de frete.
 
-![image6](//images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/4a83e3f251f45e5bae81f44cc35d6d4d/image6.png)
+![image6](https://images.ctfassets.net/alneenqid6w5/7C4Qk8X51zlTzXVYrJ0vkD/4a83e3f251f45e5bae81f44cc35d6d4d/image6.png)
 
 A contratação dessa solução pode ser realizada de maneira simples e em poucos minutos, por meio da aceitação dos Termos e Condições e a [ativação](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-ativacao--57opHihFbRAwrjQjCTymTa) no próprio Admin da loja. As seguintes funcionalidades estão presentes no VTEX Shipping Network Correios: 
 
diff --git a/docs/tracks/pt/add-pickup-points.md b/docs/tracks/pt/add-pickup-points.md
index 44fd45005..988336237 100644
--- a/docs/tracks/pt/add-pickup-points.md
+++ b/docs/tracks/pt/add-pickup-points.md
@@ -29,7 +29,7 @@ Siga o passo a passo abaixo para cadastrar um ponto de retirada na sua loja:
 4. Preencha os campos do formulário de ponto de retirada. Para entender melhor o significado de cada campo, consulte a seção [Campos de cadastro](#campos-de-cadastro), abaixo.
 5. Clique no botão **Save Changes** 
 
-![PT Cadastrar Pontos de Retirada GIF](//images.ctfassets.net/alneenqid6w5/7m2LOZGJLly2gdprwvU7Gt/06d1113db5efc6d6fc35c26daa9fabf4/PT_Cadastrar_Pontos_de_Retirada_GIF.gif)
+![PT Cadastrar Pontos de Retirada GIF](https://images.ctfassets.net/alneenqid6w5/7m2LOZGJLly2gdprwvU7Gt/06d1113db5efc6d6fc35c26daa9fabf4/PT_Cadastrar_Pontos_de_Retirada_GIF.gif)
 
 ### Campos de cadastro
 
diff --git a/docs/tracks/pt/add-sku-specifications.md b/docs/tracks/pt/add-sku-specifications.md
index ac0a56c09..1edd1dda6 100644
--- a/docs/tracks/pt/add-sku-specifications.md
+++ b/docs/tracks/pt/add-sku-specifications.md
@@ -35,7 +35,7 @@ Para cadastrar as especificações sua loja precisa ter departamentos, categoria
  7. Preencha os campos do formulário de especificações. No caso dos SKUs,  a flag de campo obrigatório sempre está selecionada por default. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher campos de especificações de SKU](https://help.vtex.com/pt/tutorial/criando-campo-de-sku--tutorials_119)
  8.  Clique em **Salvar**
 
-![1.PT](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/fa7b4836240b18cd3d941f6260b512b8/1.PT.gif)
+![1.PT](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/fa7b4836240b18cd3d941f6260b512b8/1.PT.gif)
 
 Para adicionar valores à especificação de SKU, siga os passos abaixo:
 
@@ -49,7 +49,7 @@ Para adicionar valores à especificação de SKU, siga os passos abaixo:
  8. Clique em **Novo Valor**
  9. Escreva o **Nome** do valor desejado e clique em **Salvar**
 
-![2.PT](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/8f8ee16b8a59dd7be5e5b77f358fba0c/2.PT.gif)
+![2.PT](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/8f8ee16b8a59dd7be5e5b77f358fba0c/2.PT.gif)
 
 ### Vincular as especificações a um SKU
 
@@ -65,7 +65,7 @@ Para incluir as especificações em um **SKU** siga os seguintes passos:
  6. Clique na aba **Especificações** e escolha o valor da especificação para esse SKU
  7. Clique em **Salvar**
 
-![3.PT](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/f1a986c79116835f7abb23853b51278e/3.PT.gif)
+![3.PT](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/f1a986c79116835f7abb23853b51278e/3.PT.gif)
 
 ## Planilha 
 
@@ -94,7 +94,7 @@ Depois de preencher os dados da planilha, siga o passo a passo para Importar sua
 5. Clique em **Select** para selecionar a planilha preenchida
 6.  Clique em **Importar**
 
-![4.PT](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/39b16e05c0e7f952fed25892902da30e/4.PT.gif)
+![4.PT](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/39b16e05c0e7f952fed25892902da30e/4.PT.gif)
 
 ## API 
 
diff --git a/docs/tracks/pt/adding-a-loading-dock.md b/docs/tracks/pt/adding-a-loading-dock.md
index 009cd1e3a..f7a07823d 100644
--- a/docs/tracks/pt/adding-a-loading-dock.md
+++ b/docs/tracks/pt/adding-a-loading-dock.md
@@ -28,7 +28,7 @@ Siga o passo a passo abaixo para cadastrar uma Doca na sua loja:
 4.  Preencha os campos do formulário de cadastro. Para entender melhor o significado de cada campo, veja abaixo a seção [Campos de Cadastro](#campos-de-cadastro).
 5.  Clique no botão  **Salvar**.
 
-![PT Cadastrar Doca GIF](//images.ctfassets.net/alneenqid6w5/4GWA3i4x5LSitJRR2nPSF/518140a1c67b5382bcd2042148f2b05c/PT_Cadastrar_Doca.gif)
+![PT Cadastrar Doca GIF](https://images.ctfassets.net/alneenqid6w5/4GWA3i4x5LSitJRR2nPSF/518140a1c67b5382bcd2042148f2b05c/PT_Cadastrar_Doca.gif)
 
 ### Campos de cadastro
 
diff --git a/docs/tracks/pt/adding-extra-text-to-the-order-print.md b/docs/tracks/pt/adding-extra-text-to-the-order-print.md
index 77a43ac08..1c4e32f99 100644
--- a/docs/tracks/pt/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/pt/adding-extra-text-to-the-order-print.md
@@ -38,7 +38,7 @@ Após recarregar o inStore, sempre que um vendedor imprimir um pedido, esse text
 
 Antes de adicionar texto extra, a impressão do resumo do pedido tem o seguinte formato:
 
-![28. Adding extra text to the order print - 1](//images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
+![28. Adding extra text to the order print - 1](https://images.ctfassets.net/alneenqid6w5/6kSTTkw3pk8A7aiTJXqDJJ/ec86382eb7e27484f3f37a80752a6153/28._Adding_extra_text_to_the_order_print_-_1.png)
 
 Em nosso exemplo, alteramos o arquivo `checkout-instore-custom.js` inserindo o seguinte texto extra:
 
@@ -50,4 +50,4 @@ window.INSTORE_CONFIG = {
 
 Agora, quando sempre que um resumo de pedido for impresso, teremos o seguinte resultado:
 
-![28. Adding extra text to the order print - 2](//images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
+![28. Adding extra text to the order print - 2](https://images.ctfassets.net/alneenqid6w5/1g4wvz3z8tIEZuRSSiACps/c227091af9a69d0af04d21c2b6b0b8d3/28._Adding_extra_text_to_the_order_print_-_2.png)
diff --git a/docs/tracks/pt/adding-new-stores-to-instore.md b/docs/tracks/pt/adding-new-stores-to-instore.md
index cb502f869..b775a3360 100644
--- a/docs/tracks/pt/adding-new-stores-to-instore.md
+++ b/docs/tracks/pt/adding-new-stores-to-instore.md
@@ -25,7 +25,7 @@ Esta página permite que você realize as seguintes ações:
 * [Editar](#editar-loja-fisica)
 * [Inativar](#inativar-loja-fisica)
 
-![loja-fisica-PT](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
+![loja-fisica-PT](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
 
 A página apresenta as seguintes informações: 
 
@@ -51,7 +51,7 @@ Você pode cadastrar uma loja física seguindo os passos a seguir:
 
 ### Campos de cadastro da loja física
 
-![loja-fisica2-pt](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
+![loja-fisica2-pt](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
 
 #### Identificação
 
diff --git a/docs/tracks/pt/adding-product-specifications.md b/docs/tracks/pt/adding-product-specifications.md
index 5948914e6..c8c74d624 100644
--- a/docs/tracks/pt/adding-product-specifications.md
+++ b/docs/tracks/pt/adding-product-specifications.md
@@ -35,7 +35,7 @@ Para cadastrar as especificações sua loja precisa ter departamentos, categoria
  7. Preencha os campos do formulário de especificações. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher campos de especificações de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).
  8.  Clique em **Salvar**.
 
-![1.PT](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/309fc619d5f3fa5dfc472ea31336b646/1.PT.gif)
+![1.PT](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/309fc619d5f3fa5dfc472ea31336b646/1.PT.gif)
 
 Para adicionar valores à especificação de um produto, siga os passos abaixo:
 
@@ -49,7 +49,7 @@ Para adicionar valores à especificação de um produto, siga os passos abaixo:
  9. Clique em **Novo Valor**.
  10. Escreva o **Nome** do valor desejado e clique em **Salvar**.
 
-![2.PT](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/38de1f08c0bab9de62b6003688e678e5/2.PT.gif)
+![2.PT](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/38de1f08c0bab9de62b6003688e678e5/2.PT.gif)
 
 ### Vincular as especificações a um produto
 
@@ -63,7 +63,7 @@ Para incluir as especificações em um **Produto** siga os seguintes passos:
  4. Clique na aba **Especificações** e escolha o valor da especificação para esse produto.
  5. Clique na aba **Produto** e depois clique em **Salvar**.
 
-![3.PT](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/e884dd25a34b8dc9ffeade1e8dc9b9bd/3.PT.gif)
+![3.PT](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/e884dd25a34b8dc9ffeade1e8dc9b9bd/3.PT.gif)
 
 ## Planilha 
 
@@ -92,7 +92,7 @@ Depois de preencher os dados da planilha, siga o passo a passo para Importar sua
 5. Clique em **Select** para selecionar a planilha de Importação.
 6.  Clique em **Importar**.
 
-![4.PT](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/33cb6da8c5fc3f57f84e9559e4a9867a/4.PT.gif)
+![4.PT](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/33cb6da8c5fc3f57f84e9559e4a9867a/4.PT.gif)
 
 ## API 
 
diff --git a/docs/tracks/pt/adding-products.md b/docs/tracks/pt/adding-products.md
index 5bc77e9f3..6c66f941a 100644
--- a/docs/tracks/pt/adding-products.md
+++ b/docs/tracks/pt/adding-products.md
@@ -30,7 +30,7 @@ No Admin VTEX, siga os passos abaixo.
 4. Preencha os campos do formulário de produto. Para entender melhor o significado de cada campo, acesse nosso artigo sobre os [campos de cadastro de produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke).
 5. Clique em `Salvar` ou `Salvar e Cadastrar novo SKU`, caso queira adicionar SKUs associados a esse produto.
 
-![Catalogo - Cadastrar produto PT](//images.ctfassets.net/alneenqid6w5/bdIAqfM86PlhwB3and8rX/48c5f7c1aa60306d9bdc114e1464c0aa/Catalogo_-_Cadastrar_produto_PT.gif)
+![Catalogo - Cadastrar produto PT](https://images.ctfassets.net/alneenqid6w5/bdIAqfM86PlhwB3and8rX/48c5f7c1aa60306d9bdc114e1464c0aa/Catalogo_-_Cadastrar_produto_PT.gif)
 
 ## Planilha
 
diff --git a/docs/tracks/pt/adding-skus.md b/docs/tracks/pt/adding-skus.md
index 62b25577e..7ca83fac7 100644
--- a/docs/tracks/pt/adding-skus.md
+++ b/docs/tracks/pt/adding-skus.md
@@ -25,7 +25,7 @@ Existem dois fluxos de cadastro de SKU pelo Admin VTEX: criar um SKU logo após
 ### Cadastrar SKU logo após o cadastro de um produto
 
 1. Na tela de cadastro de Produto, após preencher os campos, clique em `Salvar e Cadastrar novo SKU`.
-  ![foto1.pt](//images.ctfassets.net/alneenqid6w5/4hbOFLl4i0ItEagHpb0SQD/49b2bd614f938aef01f48444c07843f3/foto1.pt.png)
+  ![foto1.pt](https://images.ctfassets.net/alneenqid6w5/4hbOFLl4i0ItEagHpb0SQD/49b2bd614f938aef01f48444c07843f3/foto1.pt.png)
 2. Você será redirecionado(a) para a tela de cadastro de SKU. Preencha os campos do formulário de SKU. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher os campos de cadastro de SKU](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) 
 3. Clique em `Salvar`.
 
@@ -43,7 +43,7 @@ Existem dois fluxos de cadastro de SKU pelo Admin VTEX: criar um SKU logo após
 Após o cadastro de um SKU é necessário adicionar uma imagem para torná-lo ativo. Para fazer isso, siga o passo a passo abaixo: 
 
 1. Na página de cadastro do SKU, clique na aba **Imagens**.
-![foto6.pt](//images.ctfassets.net/alneenqid6w5/78tvoRLdoSO4dI8QtDPfuH/f1ba5b1a2cd4b917c4d46df95f44cc1c/foto6.pt.png)
+![foto6.pt](https://images.ctfassets.net/alneenqid6w5/78tvoRLdoSO4dI8QtDPfuH/f1ba5b1a2cd4b917c4d46df95f44cc1c/foto6.pt.png)
 2. Clique em `Inserir` e escolha a imagem desejada.
 3. Preencha os campos **Texto** (tag alt da imagem) e **Label** (a “etiqueta” usada para facilitar na organização do template das páginas do seu site, através do referenciamento do valor preenchido nesta. Ex.: Frontal, lateral, superior etc).
 4. Clique em `Enviar`.
@@ -53,7 +53,7 @@ Após o cadastro de um SKU é necessário adicionar uma imagem para torná-lo at
 Após cadastrar as imagens, você deve cadastrar as especificações do SKU. O cadastro das especificações será detalhado no próximo passo dessa trilha.  
 
 1. Clique na aba **Especificações**.
-![foto7.pt](//images.ctfassets.net/alneenqid6w5/TCWsuTxF97y0yZNLfggIX/f316524c44ec171e226d454d58da321c/foto7.pt.png)
+![foto7.pt](https://images.ctfassets.net/alneenqid6w5/TCWsuTxF97y0yZNLfggIX/f316524c44ec171e226d454d58da321c/foto7.pt.png)
 2. Preencha os campos solicitados. Os valores das especificações são configurados no nível da Categoria.
 3. Clique em `Salvar`.
 
diff --git a/docs/tracks/pt/adding-vendors.md b/docs/tracks/pt/adding-vendors.md
index 2902c8c9a..1ebfb06c5 100644
--- a/docs/tracks/pt/adding-vendors.md
+++ b/docs/tracks/pt/adding-vendors.md
@@ -18,7 +18,7 @@ Se você configurou sua loja utilizando o fluxo de __Easy Setup__ talvez já ten
 
 Ao entrar no VTable (https://{{AccountName}}.myvtex.com/admin/vtable) você verá duas aplicações, __Admin das lojas__ e __Admin dos vendedores__:
 
-![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Clique em __Admin dos vendedores__ para abrir a tabela onde incluiremos um novo vendedor.
 
@@ -28,7 +28,7 @@ Caso você já tenha cadastrado um vendedor através do __Easy Setup__, basta cl
 <strong>IMPORTANTE</strong>: o e-mail de cada vendedor <strong>NÃO</strong> pode ser o mesmo utilizado na plataforma VTEX, isso porque o seu e-mail de admin possui permissões que um vendedor não deveria ter, por isso é necessário utilizar algum outro e-mail sem privilégios na plataforma.
 </div>
 
-![inStore adicionando vendedor](//images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
+![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
 Se você pulou a etapa de criação de vendedor no __Easy Setup__ e não tem nenhum vendedor criado, precisará pegar o id da __Loja__ no __Admin das Lojas__ no VTable.
 
diff --git a/docs/tracks/pt/adding-warehouses.md b/docs/tracks/pt/adding-warehouses.md
index 2c459b057..c3d27e08b 100644
--- a/docs/tracks/pt/adding-warehouses.md
+++ b/docs/tracks/pt/adding-warehouses.md
@@ -29,7 +29,7 @@ Siga o passo a passo abaixo para cadastrar um estoque na sua loja:
 4. Preencha os campos do formulário de estoque. Para entender melhor o significado de cada campo, veja abaixo a seção [Campos de Cadastro](#campos-de-cadastro).
 5. Clique no botão **Salvar**
 
-![PT Cadastrar Estoque GIF](//images.ctfassets.net/alneenqid6w5/2z4bJ7wuzd6vePDariRnX8/90c3c2e7fa6e7f00ae360a7fd77f2dbd/PT_Cadastrar_Estoque.gif)
+![PT Cadastrar Estoque GIF](https://images.ctfassets.net/alneenqid6w5/2z4bJ7wuzd6vePDariRnX8/90c3c2e7fa6e7f00ae360a7fd77f2dbd/PT_Cadastrar_Estoque.gif)
 
 ### Campos de cadastro
 
diff --git a/docs/tracks/pt/amazon.md b/docs/tracks/pt/amazon.md
index 6663793e8..7841b51bf 100644
--- a/docs/tracks/pt/amazon.md
+++ b/docs/tracks/pt/amazon.md
@@ -16,7 +16,7 @@ trackSlugPT: integracao-com-a-amazon
 
 A Amazon é uma plataforma de ecommerce, considerada uma das cinco maiores empresas de tecnologia do mundo. Atualmente a Amazon comercializa produtos diversos, incluindo brinquedos, eletrônicos, vestuários,  acessórios, entre outros itens. Além disso, a empresa de varejo online oferece serviços de streaming, armazenamento em nuvem e assistentes virtuais. 
 
-![amazon logo](//images.contentful.com/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
+![amazon logo](https://images.contentful.com/alneenqid6w5/3hRQ23BqGdnYGkQtzOtsRF/abbcb463e142e13825d97358da9af010/amazon_logo.png)
 
 A configuração com a Amazon tem como objetivo enviar o catálogo de produtos da sua loja VTEX para esse marketplace, permitindo que você anuncie seus produtos e aumente suas vendas.
 
diff --git a/docs/tracks/pt/associating-a-template-with-a-layout.md b/docs/tracks/pt/associating-a-template-with-a-layout.md
index 00bc88447..c2beafcfe 100644
--- a/docs/tracks/pt/associating-a-template-with-a-layout.md
+++ b/docs/tracks/pt/associating-a-template-with-a-layout.md
@@ -30,4 +30,4 @@ Essa associação é feita na configuração de propriedades do layout. Para che
 6. Selecione o template que você deseja associar a esse layout.
 7. Digite "yes" para confirmar a mudança. (Este passo é necessário porque esta é uma alteração crítica para o site, já que o front-end da página será substituído.) 
 
-![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tracks/pt/autocomplete-search.md b/docs/tracks/pt/autocomplete-search.md
index 1a2bbeda9..f78c35fd9 100644
--- a/docs/tracks/pt/autocomplete-search.md
+++ b/docs/tracks/pt/autocomplete-search.md
@@ -52,22 +52,22 @@ Outra vantagem para o gestor da loja é o aumento de conversão, resultado dessa
 
 Essa seção exibe os termos mais buscados por outros clientes dentro do site.
 
-![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+![PT - Autocomplete termos mais pesquisados](https://images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
 
 ## Últimas buscas efetuadas
 
 Essa seção exibe as últimas buscas efetuadas pelo cliente. Assim, é possível  iniciar a interação com a busca instantaneamente.
 
-![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+![PT - Autocomplete historico](https://images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
 
 ## Sugestão de buscas
 
 Essa seção apresenta os termos pesquisados por outros usuários que se relacionam com a busca efetuada naquele momento. Além de termos, também são sugeridas categorias que estejam relacionadas com a busca.
 
-![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+![PT - Autocomplete sugestao termos](https://images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
 
 ## Sugestão de produtos
 
 Essa seção apresenta os produtos que correspondem a busca efetuada naquele momento. Dessa forma, ao mostrar produtos relacionados a sua busca durante a sua digitação, diminui as desistências e dá a possibilidade do usuário efetuar uma compra mais dinâmica.
 
-![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
+![PT - Autocomplete sugestao de produtos](https://images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tracks/pt/b2b-form.md b/docs/tracks/pt/b2b-form.md
index eda7258df..effdfda22 100644
--- a/docs/tracks/pt/b2b-form.md
+++ b/docs/tracks/pt/b2b-form.md
@@ -46,12 +46,12 @@ Exemplos de como fica no inStore o formulário com pessoa jurídica:
 
 __Formulário B2B__ opcional fechado:
 
-![b2b-opcional-fechado](//images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
+![b2b-opcional-fechado](https://images.ctfassets.net/alneenqid6w5/5gFb3SBRocc6Gwcm4YusAA/86d15e9f80377edc8bda880c2fda829c/b2b-opcional-fechado.png)
 
 __Formulário B2B__ opcional aberto:
 
-![b2b-opcional-aberto](//images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
+![b2b-opcional-aberto](https://images.ctfassets.net/alneenqid6w5/5KlFHUrxhmWmiK468eogck/f13e50591cb44afb21c804c6f3d7618b/b2b-opcional-aberto.png)
 
 __Formulário B2B__ obrigatório (já vem todos os campos abertos):
 
-![b2b-obrigatorio](//images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
+![b2b-obrigatorio](https://images.ctfassets.net/alneenqid6w5/1t7EvHWtg0AiSsUSkaAqUi/3f704862cc694d3feeaf540fabfba228/b2b-obrigatorio.png)
diff --git a/docs/tracks/pt/backend-integrations.md b/docs/tracks/pt/backend-integrations.md
index 1c5316108..7c813c5c2 100644
--- a/docs/tracks/pt/backend-integrations.md
+++ b/docs/tracks/pt/backend-integrations.md
@@ -102,7 +102,7 @@ Os passos para esta configuração devem ser seguidos na ordem apresentada abaix
 
 Após configurar a loja e fazer a integração com middleware, o fluxo geral de informações terá o seguinte formato:
 
-![ERP-integrations-pt](//images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/cfbbd0b541595fd3788d895bbeeef071/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_1.jpg)
+![ERP-integrations-pt](https://images.ctfassets.net/alneenqid6w5/7G5OqBkp2i7tpz19u6XBFy/cfbbd0b541595fd3788d895bbeeef071/Diagrama_do_fluxo_de_integra__o_com_o_ERP_-_Frame_1.jpg)
 
 Cada uma das requisições ou processos representados pelas setas no diagrama acima é acionada por um tipo diferente de evento na operação do dia a dia de um ecommerce. Para saber mais detalhes sobre esse fluxo, veja o [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide#ongoing-middleware-flow).
 
@@ -168,7 +168,7 @@ Existem três tipos de especificações e elas devem ser criadas na seguinte ord
 
 O diagrama abaixo ilustra este procedimento:
 
-![catalog_specification_diagram_PT](//images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/1880753cbe1e9b79f0dae39125a76cb8/catalog_specification_diagram_PT.png)
+![catalog_specification_diagram_PT](https://images.ctfassets.net/alneenqid6w5/16tZGd00Gxeqk5awp711gz/1880753cbe1e9b79f0dae39125a76cb8/catalog_specification_diagram_PT.png)
 
 As especificações seguem a hierarquia do Catálogo. Quando um grupo é criado em um departamento ou categoria, ele será herdado nos níveis abaixo. 
 
diff --git a/docs/tracks/pt/banners-en.md b/docs/tracks/pt/banners-en.md
index 814c6a284..4585769a6 100644
--- a/docs/tracks/pt/banners-en.md
+++ b/docs/tracks/pt/banners-en.md
@@ -33,7 +33,7 @@ No Admin VTEX, a página **Storefront** > **Banners** exibe a listagem dos banne
 * [Editar um banner](#editar-banner)
 * [Deletar um banner](#deletar-banner) 
 
-![banners-intro-pt](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
+![banners-intro-pt](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
 
 A página apresenta as seguintes informações: 
 
diff --git a/docs/tracks/pt/barcode-reading.md b/docs/tracks/pt/barcode-reading.md
index f379fe9c9..cae9667f4 100644
--- a/docs/tracks/pt/barcode-reading.md
+++ b/docs/tracks/pt/barcode-reading.md
@@ -18,6 +18,6 @@ Após fazer a identificação do cliente, o vendedor é levado já diretamente p
 
 Se o vendedor estiver usando um tablet ou smartphone, ele verá, na barra superior do aplicativo, um botão de código de barras <i class="fas fa-barcode"></i>.
 
-![31. VTEX Sales App - Product Overview - 6 - EN](//images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/543f300da71b929ff7e6d57581040128/barcode.png)
+![31. VTEX Sales App - Product Overview - 6 - EN](https://images.ctfassets.net/alneenqid6w5/4yAzpm3JHk9Ksjku7FbVcO/543f300da71b929ff7e6d57581040128/barcode.png)
 
 Ao clicar nele, o vendedor pode usar a câmera para bipar um produto e, com isso, ser levado automaticamente à tela de detalhes deste produto.
diff --git a/docs/tracks/pt/basic-vtex-io-developer-setup.md b/docs/tracks/pt/basic-vtex-io-developer-setup.md
index 36f63761b..ad4f0dbe4 100644
--- a/docs/tracks/pt/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/pt/basic-vtex-io-developer-setup.md
@@ -38,7 +38,7 @@ Isso abrirá uma janela do navegador que solicitará suas credenciais.
 
 Quando estiver logado, você pode usar o comando `vtex whoami` para descobrir qual *conta* e *workspace* está usando atualmente.
 
-![Command Line](//images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
+![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
 <div class="alert alert-info">
 Dica: Você pode configurar seu terminal para exibir sua conta e workspace atuais automaticamente. A maneira mais fácil de fazer isso é usar nossos <a href="https://github.com/vtex/dotfiles">dotfiles</a>, que configuram automaticamente  a <a href="https://fishshell.com/">Fish Shell</a> e adicionam uma <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">função de prompt</a> para você.
@@ -54,7 +54,7 @@ Por padrão, quando efetua login em uma loja, você está no workspace `master`.
 $ vtex ls
 ```
 
-![Command Line vtex ls](//images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
+![Command Line vtex ls](https://images.ctfassets.net/alneenqid6w5/4AH5vzt1JfOCzIDtB0fRvR/110dda0479f9aa9891062ece2766837f/Command_Line_vtex_ls.svg)
 
 ## Criando seu próprio workspace
 
@@ -72,6 +72,6 @@ Dica: Você pode alternar para (<em>e redefinir</em>) um workspace master em um
 
 Os workspaces podem ser nomeados arbitrariamente, mas geralmente é conveniente atribuir o seu próprio nome quando você deseja desenvolver em seu ambiente.
 
-![command line workspace](//images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
+![command line workspace](https://images.ctfassets.net/alneenqid6w5/1Urbt6L0XfNEWukSvdKRdK/41e7e9c9f900fb96ddf5fc3aa6d7c2af/command_line_workspace.svg)
 
 Agora você tem seu próprio workspace. Você pode rodar `vtex list` novamente e observar que as apps instaladas espelham aquelas em `master`. Agora, vamos "linkar" uma versão local do tema da loja para que você possa começar a editá-la.
diff --git a/docs/tracks/pt/best-practices-for-testing-instore.md b/docs/tracks/pt/best-practices-for-testing-instore.md
index 34b61ac8e..86d198f5e 100644
--- a/docs/tracks/pt/best-practices-for-testing-instore.md
+++ b/docs/tracks/pt/best-practices-for-testing-instore.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Após finalizar as configurações básicas e a instalação do aplicativo do VTEX Sales App em um dispositivo, é importante realizar testes antes de começar a utilizar o VTEX Sales App em suas lojas físicas. Neste artigo, você vai conhecer as boas práticas para testes de uso do VTEX Sales App.
 
-![testes-instore-pt](//images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/090c0fa4f420c4d875181819c200360b/Group_4__2_.png)
+![testes-instore-pt](https://images.ctfassets.net/alneenqid6w5/1g0a3CiYD3I1MFIALGRjOP/090c0fa4f420c4d875181819c200360b/Group_4__2_.png)
 
 ## Testes de retaguarda
 
diff --git a/docs/tracks/pt/calculating-order-shipping-time.md b/docs/tracks/pt/calculating-order-shipping-time.md
index eeb51aa7c..845d40c2e 100644
--- a/docs/tracks/pt/calculating-order-shipping-time.md
+++ b/docs/tracks/pt/calculating-order-shipping-time.md
@@ -23,17 +23,17 @@ O prazo de entrega de um pedido leva em consideração os __tempos de custo__ de
 
 Para cada uma das três etapas da rota logística, você pode definir um tempo de custo - e o prazo de entrega que o seu cliente verá no checkout é a soma desses tempos de custo (+ feriados, e ainda considerando os horários de corte).
 
-![deliveryCostTimes](//images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
+![deliveryCostTimes](https://images.contentful.com/alneenqid6w5/hA6N4VPj440AEqEecIUck/0a6784f0c3d6f6d88b65547762600a7d/deliveryCostTimes.png)
 
 Os tempos de custo do __estoque__ e da __doca__ são definidos nas telas de configuração de cada uma dessas etapas, no módulo Estoque & Entrega > Painéis.
 
-![calculoPrazoEntrega1](//images.contentful.com/alneenqid6w5/4QgQlroxxCK4iu6YoU2uIQ/a2df01bdbe2449e924a6380b5a39a19b/calculoPrazoEntrega1.png) 
+![calculoPrazoEntrega1](https://images.contentful.com/alneenqid6w5/4QgQlroxxCK4iu6YoU2uIQ/a2df01bdbe2449e924a6380b5a39a19b/calculoPrazoEntrega1.png) 
 
-![calculoPrazoEntrega2](//images.contentful.com/alneenqid6w5/6xAiBHXxwA2cMIaaK4AKm2/bfff8d81b7363121cc84de1149cfd587/calculoPrazoEntrega2.png)
+![calculoPrazoEntrega2](https://images.contentful.com/alneenqid6w5/6xAiBHXxwA2cMIaaK4AKm2/bfff8d81b7363121cc84de1149cfd587/calculoPrazoEntrega2.png)
 
 O tempo de custo da __transportadora__ é definido na tabela de frete, enviada à VTEX por meio da tela de configuração da transportadora, também no módulo Estoque & Entrega.
 
-![calculoPrazoEntrega3](//images.contentful.com/alneenqid6w5/2bL9Gw0AeswGAeKSqYCYw4/57c492eb08239d61e463839a768101ad/calculoPrazoEntrega3.png)
+![calculoPrazoEntrega3](https://images.contentful.com/alneenqid6w5/2bL9Gw0AeswGAeKSqYCYw4/57c492eb08239d61e463839a768101ad/calculoPrazoEntrega3.png)
 
 ## Exemplos
 
diff --git a/docs/tracks/pt/cancel-and-refund-an-order-on-instore.md b/docs/tracks/pt/cancel-and-refund-an-order-on-instore.md
index 37d118385..2f6db1115 100644
--- a/docs/tracks/pt/cancel-and-refund-an-order-on-instore.md
+++ b/docs/tracks/pt/cancel-and-refund-an-order-on-instore.md
@@ -42,7 +42,7 @@ Caso o pedido cancelado tenha sido pago em dinheiro, o vendedor precisa estornar
 
 Após os passos descritos [anteriormente](#cenario-2-o-cliente-esta-na-loja), o vendedor verá a tela abaixo, que informa que o pagamento **Dinheiro** já foi estornado.
 
-![estornar-pagamentos-instore-PT](//images.contentful.com/alneenqid6w5/3B51VlNXxKyfwvWMstcAtY/5f1b4407bcd67cb098427cdaf1fd7171/image3.png)
+![estornar-pagamentos-instore-PT](https://images.contentful.com/alneenqid6w5/3B51VlNXxKyfwvWMstcAtY/5f1b4407bcd67cb098427cdaf1fd7171/image3.png)
 
 Para retornar para a página de detalhes do pedido cancelado, é preciso clicar na seta <i class="fas fa-arrow-left"></i> na barra superior do VTEX Sales App.
 
diff --git a/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md b/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
index ae67aacf3..9acd65d85 100644
--- a/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
+++ b/docs/tracks/pt/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
@@ -20,25 +20,25 @@ Após o seu cliente clicar no chat, ele será direcionado a um formulário, onde
 
 Depois de preencher o  as informações ele será direcionado para o WhatsApp.
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 1](//images.ctfassets.net/alneenqid6w5/3XFOXC4aO8kqu550uXLsCG/d957132af5ff3ac5b48f6a340625fb06/Screenshot_2022-08-25_at_14-57-08_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 1](https://images.ctfassets.net/alneenqid6w5/3XFOXC4aO8kqu550uXLsCG/d957132af5ff3ac5b48f6a340625fb06/Screenshot_2022-08-25_at_14-57-08_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
 
 Para começar, você precisa criar um **link** para cada número que irá atender na sua empresa. Se você ainda não criou ou não sabe como criar, [leia mais sobre links.](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB) Mas, se você já possui todos os links criados, vamos começar a organizar o nosso processo de [**captura**.](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo)  
 
 1. Defina em qual etapa você deseja capturar as informações (ela pode ser diretamente no link distribuído nas redes sociais, no chat antes de selecionar o setor ou até mesmo na hora do redirecionamento [sequencial](https://help.vtex.com/pt/tutorial/seletivo--7zjQVFhGbwYZ7NW8yKRSKX) ou [geolocalizado](https://help.vtex.com/pt/tutorial/geolocalizado--6XIfgaqXaPe5exQa9oVp6D)).
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 2](//images.ctfassets.net/alneenqid6w5/7Lc7JSpcU6lSIK0vEZZkzu/2e0b8536fb814f1f7bcf9a4e401942b1/Screenshot_2022-08-25_at_15-01-46_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 2](https://images.ctfassets.net/alneenqid6w5/7Lc7JSpcU6lSIK0vEZZkzu/2e0b8536fb814f1f7bcf9a4e401942b1/Screenshot_2022-08-25_at_15-01-46_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
 
 2. Selecione o link que será o link âncora**.
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 3](//images.ctfassets.net/alneenqid6w5/2QKQTKLBwpZSfcMNoOfijk/3d1d0c8b42fcd2cb4d6215cbed713a15/Screenshot_2022-08-25_at_15-02-27_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 3](https://images.ctfassets.net/alneenqid6w5/2QKQTKLBwpZSfcMNoOfijk/3d1d0c8b42fcd2cb4d6215cbed713a15/Screenshot_2022-08-25_at_15-02-27_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)  
 
 3. Recomendamos sempre o mesmo link que será o de destino.
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 4](//images.ctfassets.net/alneenqid6w5/2ZJjdfc2ICq5Zh6UR9x8JZ/c0c7c33d49a9de249f5e953af397c93c/Screenshot_2022-08-25_at_15-03-19_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 4](https://images.ctfassets.net/alneenqid6w5/2ZJjdfc2ICq5Zh6UR9x8JZ/c0c7c33d49a9de249f5e953af397c93c/Screenshot_2022-08-25_at_15-03-19_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
 
 4. Defina os campos que deseja capturar de seus Leads 
 
-![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 5](//images.ctfassets.net/alneenqid6w5/79O7HBEFJpTbDxJt2XkahA/50e889ee13894faac97e5bd1b582f6e8/Screenshot_2022-08-25_at_15-05-18_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
+![Capturar dados do lead antes de iniciar uma conversa no WhatsApp 5](https://images.ctfassets.net/alneenqid6w5/79O7HBEFJpTbDxJt2XkahA/50e889ee13894faac97e5bd1b582f6e8/Screenshot_2022-08-25_at_15-05-18_Capturar_dados_do_lead_antes_de_iniciar_uma_conversa_no_WhatsApp.png)
 
 5. Para definir, basta clicar e selecionar o campo desejado. Além disso, você ainda pode ativar o modo robô. Acesse [https://whts.co/bot](\"https://whts.co/bot\") e faça um teste da experiência que seu cliente terá.
 
diff --git a/docs/tracks/pt/carrefour-marketplace.md b/docs/tracks/pt/carrefour-marketplace.md
index 661f16b09..10ef4af8d 100644
--- a/docs/tracks/pt/carrefour-marketplace.md
+++ b/docs/tracks/pt/carrefour-marketplace.md
@@ -16,6 +16,6 @@ trackSlugPT: configurar-integracao-do-carrefour
 
 O [Carrefour](https://www.carrefour.com.br/) é uma das principais empresas do ramo varejista físico e online do país, operando no Brasil há mais de 40 anos e uma das suas linhas de negócio é o [Carrefour Marketplace](https://www.carrefour.com.br/marketplace), onde sellers se beneficiam da visibilidade nacional e credibilidade da marca para vender seus produtos para mais de 6 milhões de clientes cadastrados na sua plataforma.
 
-![carrefourmkt](//images.ctfassets.net/alneenqid6w5/3vjhZetYnWLNUAZWZXCBiI/dc1d6f0d919a1ec5784a31c1d0ce1ea7/carrefourmkt.jpg)
+![carrefourmkt](https://images.ctfassets.net/alneenqid6w5/3vjhZetYnWLNUAZWZXCBiI/dc1d6f0d919a1ec5784a31c1d0ce1ea7/carrefourmkt.jpg)
 
 A configuração com o Carrefour tem como objetivo enviar o catálogo de produtos da sua loja VTEX para esse marketplace, permitindo que você anuncie seus produtos e expanda seus canais de venda.
diff --git a/docs/tracks/pt/cart-transfer-and-capture.md b/docs/tracks/pt/cart-transfer-and-capture.md
index 0f9642c16..ee3474d19 100644
--- a/docs/tracks/pt/cart-transfer-and-capture.md
+++ b/docs/tracks/pt/cart-transfer-and-capture.md
@@ -20,11 +20,11 @@ O VTEX Sales App permite [habilitar uma funcionalidade de transferência de carr
 
 Para o vendedor compartilhar um carrinho, ele pode gerar um código numérico ou um QR Code. Para isso, estando na tela do carrinho, basta clicar no botão __Transferir__. Veja um exemplo na imagem abaixo.
 
-![24. Enable cart transfer between devices - 3](//images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
+![24. Enable cart transfer between devices - 3](https://images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
 
 Ao clicar nesse botão, o aplicativo mostra um QR Code e um código numérico de quatro dígitos.
 
-![31. VTEX Sales App - Product Overview - 9](//images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._VTEX Sales App_-_Product_Overview_-_9.png)
+![31. VTEX Sales App - Product Overview - 9](https://images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._VTEX Sales App_-_Product_Overview_-_9.png)
 
 Um outro vendedor logado na mesma loja pode, então, capturar esse carrinho e continuar a venda a partir do seu dispositivo.
 
@@ -34,7 +34,7 @@ Para capturar um carrinho, basta entrar no menu principal do VTEX Sales App e cl
 
 Alternativamente, na tela inicial do aplicativo, o vendedor pode simplesmente arrastar a tela para a direita. Ao arrastar a tela para a direita, você verá a tela para __Capturar Carrinho__, conforme mostra a imagem abaixo.
 
-![24. Enable cart transfer between devices - 2](//images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
+![24. Enable cart transfer between devices - 2](https://images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
 
 Nessa tela, é possível capturar um carrinho por um desses três métodos:
 - Código do carrinho
diff --git a/docs/tracks/pt/cart-transfer.md b/docs/tracks/pt/cart-transfer.md
index d83277759..046aeeb44 100644
--- a/docs/tracks/pt/cart-transfer.md
+++ b/docs/tracks/pt/cart-transfer.md
@@ -31,14 +31,14 @@ window.INSTORE_CONFIG = {
 
 Ao realizar essa alteração, você deve perceber que aparecerão duas bolinhas no fim da página de identificação do inStore:
 
-![01 inStore slider transferencia](//images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
+![01 inStore slider transferencia](https://images.ctfassets.net/alneenqid6w5/5h4AVCw4sE4oAIsMEMskU0/a5739c88008a9029755adadc58a332bf/01_inStore_slider_transferencia.png)
 
 Ao arrastar a tela para a lateral você verá a tela para __“Capturar carrinho”__:
 
-![02 inStore capturar carrinho](//images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
+![02 inStore capturar carrinho](https://images.ctfassets.net/alneenqid6w5/1hfTK0X9dg4CgSKEqYm0gG/637365736b1bb04e0dae621e2a7022b9/02_inStore_capturar_carrinho.png)
 
 Nela é possível capturar um carrinho pelo código do carrinho, QR code ou até por vendedor.
 
 Para gerar um código ou QR code de um carrinho você deve usar a opção __“Transferir”__ presente no carrinho do inStore:
 
-![03 inStore transferir](//images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
+![03 inStore transferir](https://images.ctfassets.net/alneenqid6w5/5fpW69RgkgAgaig46S6kwu/72442a8c5d24f48861881f2a884c065a/03_inStore_transferir.png)
diff --git a/docs/tracks/pt/catalog-architecture.md b/docs/tracks/pt/catalog-architecture.md
index 36a0a7413..3a6d413ce 100644
--- a/docs/tracks/pt/catalog-architecture.md
+++ b/docs/tracks/pt/catalog-architecture.md
@@ -35,4 +35,4 @@ Essas especificações são, por exemplo, a composição de um produto, ou o tam
 
 Abaixo, vemos um esquema da arquitetura do Catálogo na VTEX.
 
-![arquitetura-catalogo-PT](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
+![arquitetura-catalogo-PT](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
diff --git a/docs/tracks/pt/catalog-concept-definition.md b/docs/tracks/pt/catalog-concept-definition.md
index 16e9eec43..933517482 100644
--- a/docs/tracks/pt/catalog-concept-definition.md
+++ b/docs/tracks/pt/catalog-concept-definition.md
@@ -18,7 +18,7 @@ O menu **Catálogo** contém as funcionalidades referentes ao sortimento de prod
 
 O menu **Catálogo** do Admin VTEX reúne as páginas onde você gerencia catálogo, preços e inventário do seu ecommerce.
 
-![visao-geral-produto-PT](//images.contentful.com/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/e5cf20175dc73345dbf7c9330fcf29e4/image.png)
+![visao-geral-produto-PT](https://images.contentful.com/alneenqid6w5/6hg7IQ4sv6sphRtywSsDMQ/e5cf20175dc73345dbf7c9330fcf29e4/image.png)
 
 A área **Catálogo** possibilita a configuração das funcionalidades referentes ao sortimento de produtos do ecommerce, como suas categorias, marcas e coleções, por exemplo. Para vender seus produtos, é preciso cadastrá-los nesta seção.
 
diff --git a/docs/tracks/pt/centauro-marketplace.md b/docs/tracks/pt/centauro-marketplace.md
index 5b92c448b..d4240db5c 100644
--- a/docs/tracks/pt/centauro-marketplace.md
+++ b/docs/tracks/pt/centauro-marketplace.md
@@ -16,7 +16,7 @@ trackSlugPT: integracao-com-a-centauro
 
 A Centauro é maior rede de lojas esportivas da América Latina, presente em mais de 22 estados e com mais de 190 lojas. Seu site possui 15 milhões de visitantes únicos por mês, 5 milhões de usuários conectados por mês via redes sociais.  
 
-![logo centauro](//images.ctfassets.net/alneenqid6w5/4GJN1Dn7SBPMN0CzP2nIqg/f48e6b057a585abcd3eb5cf8b0b0e75c/logo_centauro.jpg)
+![logo centauro](https://images.ctfassets.net/alneenqid6w5/4GJN1Dn7SBPMN0CzP2nIqg/f48e6b057a585abcd3eb5cf8b0b0e75c/logo_centauro.jpg)
 
 Usando a integração nativa com o Marketplace da Centauro, você poderá expor e vender seus produtos na loja online.
 
diff --git a/docs/tracks/pt/changing-the-instore-language.md b/docs/tracks/pt/changing-the-instore-language.md
index 7a909b103..50ed7102b 100644
--- a/docs/tracks/pt/changing-the-instore-language.md
+++ b/docs/tracks/pt/changing-the-instore-language.md
@@ -80,4 +80,4 @@ Após fazer a alteração no código, salve o arquivo `checkout-instore-custom.j
 
 Em seguida, no aplicativo inStore, para ver as alterações refletidas, entre no menu e clique no botão __Restaurar dados__, como mostra a reprodução abaixo.
 
-![22. Change the inStore language - 1](//images.ctfassets.net/alneenqid6w5/6kMdyIyQkEUJ9HYKSLSFj4/55748d5b159dc83944dc211e95833669/22._Change_the_inStore_language_-_1.png)
+![22. Change the inStore language - 1](https://images.ctfassets.net/alneenqid6w5/6kMdyIyQkEUJ9HYKSLSFj4/55748d5b159dc83944dc211e95833669/22._Change_the_inStore_language_-_1.png)
diff --git a/docs/tracks/pt/cms-folder-structure.md b/docs/tracks/pt/cms-folder-structure.md
index 45b01c5c4..b72091abd 100644
--- a/docs/tracks/pt/cms-folder-structure.md
+++ b/docs/tracks/pt/cms-folder-structure.md
@@ -33,7 +33,7 @@ Toda loja precisa ter, sem exceção, as seguintes pastas no CMS para garantir o
 
 Veja abaixo estas pastas básicas no CMS:
 
-![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas pastas vêm por padrão no ambiente de todas as lojas VTEX.
 
diff --git a/docs/tracks/pt/cms-vtex-io.md b/docs/tracks/pt/cms-vtex-io.md
index 587a83d98..d10b3e9a7 100644
--- a/docs/tracks/pt/cms-vtex-io.md
+++ b/docs/tracks/pt/cms-vtex-io.md
@@ -27,19 +27,19 @@ Configure o [binding da loja](https://help.vtex.com/en/tutorial/what-is-cms-layo
 
 Binding é o processo utilizado para vincular o seu site a uma loja. Para mais detalhes, consulte o artigo [Vincular uma loja a uma estrutura de pastas do CMS (binding)](https://help.vtex.com/en/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![CMS - Sites and channels PT](//images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/0c3d2414ac7931cc88b8e11264927765/cms-sites-and-channels-pt.png)
+![CMS - Sites and channels PT](https://images.ctfassets.net/alneenqid6w5/4mXskFs41ULqUjO0naKtPd/0c3d2414ac7931cc88b8e11264927765/cms-sites-and-channels-pt.png)
 
 ## Páginas
 Em **[Páginas](https://help.vtex.com/pt/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc)**, crie uma nova URL e vincule-a a uma template já definido no [código do tema da loja](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-4-configuringtemplates).
 
 Essa seção também contém a página **Redirecionamentos**, que redireciona usuários e mecanismos de pesquisa de uma URL para outra mais relevante ou similar. 
 
-![CMS - Páginas](//images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/43932eacc38cd05af0f1a913cd2eb488/cms-pages-pt.png)
+![CMS - Páginas](https://images.ctfassets.net/alneenqid6w5/3f6BEwp3ifvCYNFpwMQjNn/43932eacc38cd05af0f1a913cd2eb488/cms-pages-pt.png)
 
 ## Site Editor
 O **[Site Editor](https://help.vtex.com/pt/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1)** é uma interface gráfica para o gerenciamento do conteúdo do storefront (frente de loja). Ele permite criar, editar, publicar e agendar mudanças nos seus componentes e no comportamento do storefront.
 
-![CMS - Site Editor PT](//images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/4258f07e4ba21f1d2c0ade81579207e1/cms-siteeditor-pt.png)
+![CMS - Site Editor PT](https://images.ctfassets.net/alneenqid6w5/5mh4dQ3fdbM4wTDcdx6Cb/4258f07e4ba21f1d2c0ade81579207e1/cms-siteeditor-pt.png)
 
 ## Estilos
 
@@ -49,12 +49,12 @@ A seção **[Estilos](https://help.vtex.com/pt/tutorial/styles-overview--v0Db5oh
   Esse recurso só funciona em <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-creating-a-production-workspace">workspaces de produção</a>.
 </div>
 
-![CMS - Estilos](//images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/a58296966e9b912d16546bbd232d0800/cms-styles-pt.png)
+![CMS - Estilos](https://images.ctfassets.net/alneenqid6w5/6oMURjcDdxF2DCR1x59rR6/a58296966e9b912d16546bbd232d0800/cms-styles-pt.png)
 
 ## Loja
 A seção **[Loja](https://help.vtex.com/pt/tutorial/cms-loja-visao-geral--3Eat287G6wUi6Mly5rW5Fs)** é responsável pelas configurações de SEO, marcadores de otimização de desempenho e notificações PWA na sua loja.
 
-![CMS - Loja](//images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/f5c8cf60d396197462842c2152d70e3b/cms-store-pt.png)
+![CMS - Loja](https://images.ctfassets.net/alneenqid6w5/6hUAHs42TAVSzXp5KgT34f/f5c8cf60d396197462842c2152d70e3b/cms-store-pt.png)
 
 ## Referências
 - [Conceitos - VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6loFGF4nXvgIVIzsyyJA5c#concepts)
diff --git a/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md b/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
index 6bc629081..ac9b3c764 100644
--- a/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
+++ b/docs/tracks/pt/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
@@ -16,7 +16,7 @@ trackSlugPT: suiteshare
 
 Você já conseguiu o mais difícil, fazer com que seus clientes entrem em contato com a sua empresa pelo WhatsApp. Agora, basta configurar com quem eles irão falar, definir os setores ou se serão direcionados para o atendente mais próximo a ele. 
 
-![Como distribuir o atendimento no WhatsApp para mais de um número 1](//images.ctfassets.net/alneenqid6w5/7wLfyYNfAzOf7tn6xIBOWm/c899205e4a03b341c5ece68646d8f17e/Screenshot_2022-08-25_at_14-51-20_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
+![Como distribuir o atendimento no WhatsApp para mais de um número 1](https://images.ctfassets.net/alneenqid6w5/7wLfyYNfAzOf7tn6xIBOWm/c899205e4a03b341c5ece68646d8f17e/Screenshot_2022-08-25_at_14-51-20_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
 
 Para começar, você precisa criar um link para cada número que irá atender na sua empresa. Se você ainda não criou ou não sabe como criar, [leia mais sobre links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB). Mas, se você já possui todos os links criados vamos começar a organizar o nosso time. 
 
@@ -24,7 +24,7 @@ Para começar, você precisa criar um link para cada número que irá atender na
 
 Acesse “_**Organizar**_” e escolha como será distribuído o atendimento, você pode escolher entre **Sequencial, Geolocalizado** (Apenas para o plano Enterprise) e **Seletivo**.
 
-![Como distribuir o atendimento no WhatsApp para mais de um número 2](//images.ctfassets.net/alneenqid6w5/6ODYG6o8SZUk9dQvx0Lps/e73c6dca3304220e27815eef943928bc/Screenshot_2022-08-25_at_14-55-02_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
+![Como distribuir o atendimento no WhatsApp para mais de um número 2](https://images.ctfassets.net/alneenqid6w5/6ODYG6o8SZUk9dQvx0Lps/e73c6dca3304220e27815eef943928bc/Screenshot_2022-08-25_at_14-55-02_Como_distribuir_o_atendimento_no_WhatsApp_para_mais_de_um_n__mero.png)
 
 No modo **sequencial**, cada cliente que clica nesse link cairá para um atendente diferente, a distribuição é feita de forma sequencial, onde cada atendente terá a sua vez de forma igualitária.  Como se fosse uma fila de espera, cada cliente será direcionado para um atendente, numa espécie de central de atendimento (ou como alguns gostam de chamar), em um call-center de WhatsApp.
 
diff --git a/docs/tracks/pt/como-funciona-o-adaptador-vtex.md b/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
index 5b4316e20..c09bb816a 100644
--- a/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
+++ b/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
@@ -20,7 +20,7 @@ O Adaptador VTEX foi criado para clientes que já possuem integração do ERP co
   <p>Este guia se aplica apenas a lojas que já utilizam a integração entre um ERP e a CIASHOP. Nos demais casos, é necessário seguir o guia para desenvolvedores <a href="https://developers.vtex.com/docs/guides/erp-integration-guide">Back office integration guide (ERP/PIM/WMS)</a> para realizar a integração com um ERP.</p>
 </div>
 
-![imagem-adaptador-1](//images.contentful.com/alneenqid6w5/3YzpvrWy5X48siMcATs5Ba/094e532302f3f96a66d21ecee0d96a72/image.png)
+![imagem-adaptador-1](https://images.contentful.com/alneenqid6w5/3YzpvrWy5X48siMcATs5Ba/094e532302f3f96a66d21ecee0d96a72/image.png)
 
 Para facilitar o entendimento, organizamos o documento em tópicos:
 
@@ -33,7 +33,7 @@ Para facilitar o entendimento, organizamos o documento em tópicos:
 
 Por meio da tabela abaixo, você pode verificar o que a integração do adaptador contempla:
 
-![image-adaptador-2](//images.ctfassets.net/alneenqid6w5/4TsEw3tXkfK0IEAZlcRzwR/b9dc7e117331beacf34577442c69da0c/Group_1_9_.png)
+![image-adaptador-2](https://images.ctfassets.net/alneenqid6w5/4TsEw3tXkfK0IEAZlcRzwR/b9dc7e117331beacf34577442c69da0c/Group_1_9_.png)
 
 <div class="alert alert-warning">
   <p>Para integração via WEBSERVICE, os pedidos na VTEX serão coletados quando estiverem com pagamento aprovado, no status <b>Pronto-para-manuseio</b>.</p>
diff --git a/docs/tracks/pt/configurar-adaptador.md b/docs/tracks/pt/configurar-adaptador.md
index 64cad87b8..5fad82143 100644
--- a/docs/tracks/pt/configurar-adaptador.md
+++ b/docs/tracks/pt/configurar-adaptador.md
@@ -20,7 +20,7 @@ Abaixo você encontrar informações sobre como você efetua a configuração do
 
 1. Para executar este procedimento você deve abrir o administrador da sua loja VTEX e a tela de configuração do adaptador. Sugerimos fazer isto em duas abas separadas do seu navegador preferido.
 2. No administrador da VTEX (`https://{suaconta}.myvtex.com.br/admin`), clique em **Gerenciamento de contas** e, em seguida, em **Contas**.
-![imagem-adaptador3](//images.contentful.com/alneenqid6w5/16pH131NlS4xUtpmPbXbTN/b2392494bf4b077eb3642b810617a06e/image.png)
+![imagem-adaptador3](https://images.contentful.com/alneenqid6w5/16pH131NlS4xUtpmPbXbTN/b2392494bf4b077eb3642b810617a06e/image.png)
 3. Digite o nome da sua conta na barra de pesquisa e pressione o botão `Enter`.
 4. Clique no nome da sua conta. Você será redirecionado para a página **Editar conta**.
 5. Na seção **Segurança**, clique em `Gerar appKey e appToken`.
@@ -28,7 +28,7 @@ Abaixo você encontrar informações sobre como você efetua a configuração do
 7. Clique em `Gerar novos tokens`.
 8. Por uma questão de segurança, é mostrado apenas uma vez. Copie esse token e salve-o em um local seguro para usá-los na tela de configuração do adaptador.
 9. Na tela do adaptador, você deve colocar os valores copiados nos respectivos campos.
-![imagem-adaptador-4](//images.contentful.com/alneenqid6w5/6R4NOb4hNQFozSlj2zQ90u/8b4b1c2730e7776bc5075826921c0054/image.png)
+![imagem-adaptador-4](https://images.contentful.com/alneenqid6w5/6R4NOb4hNQFozSlj2zQ90u/8b4b1c2730e7776bc5075826921c0054/image.png)
 10. Preencha o email para receber notificações do adapter. Este email será utilizado para lembrete de senha.
 11. Preencha o campo  app-Key com o valor configurado no ambiente VTEX.
 12. Preencha o campo appToken com o valor gerado no ambiente VTEX.
@@ -42,7 +42,7 @@ Abaixo você encontrar informações sobre como você efetua a configuração do
 
 Você deve criar os campos da tabela abaixo dentro do MasterData.
 
-![imagem-adaptador-5](//images.contentful.com/alneenqid6w5/5X8ejWR6ag2C9yv16v8Rjy/ef95d8b91860e8a3b1c170e067f15030/image.png)
+![imagem-adaptador-5](https://images.contentful.com/alneenqid6w5/5X8ejWR6ag2C9yv16v8Rjy/ef95d8b91860e8a3b1c170e067f15030/image.png)
 
 <div class="alert alert-warning">
 <p>Você deve criar estes campos antes de executar as operações de migração de dados da Ciashop para VTEX.</p>
@@ -100,6 +100,6 @@ Para trabalhar com integração de campos customizados de produto, você deve cr
 ## Configurar os métodos de pagamento corretamente na VTEX
 
 1. No administrador da loja, dentro de condições de pagamento, usada durante a criação dos métodos de pagamento no ambiente VTEX, você deve selecionar o o campo abaixo para inserir o nome do meio de pagamento.
-![imagem-adaptador-6](//images.contentful.com/alneenqid6w5/1iQe6XtH6bIrayKoHR8xdl/8fda5767c04aef042f432b25a5152ce0/image.png)
+![imagem-adaptador-6](https://images.contentful.com/alneenqid6w5/1iQe6XtH6bIrayKoHR8xdl/8fda5767c04aef042f432b25a5152ce0/image.png)
 2. Você deve escolher uma dos valores da lista abaixo, contidos na coluna **Nome da Regra** e colocá-lo no campo sinalizado acima, de acordo com o método de pagamento que está configurando. Exemplo: se você estiver configurando o Boleto Bancário Bradesco, então deve colocar o nome Bradesco Registrado.
-![lista-da-regra-metodo-pagamento-adaptador](//images.contentful.com/alneenqid6w5/6xtIude1FzuhGd6eTtLXBX/648098004b0be3ef24890ed10310e4a7/lista-da-regra-metodo-pagamento.png)
+![lista-da-regra-metodo-pagamento-adaptador](https://images.contentful.com/alneenqid6w5/6xtIude1FzuhGd6eTtLXBX/648098004b0be3ef24890ed10310e4a7/lista-da-regra-metodo-pagamento.png)
diff --git a/docs/tracks/pt/configurar-erps.md b/docs/tracks/pt/configurar-erps.md
index 94891c948..9f7feb824 100644
--- a/docs/tracks/pt/configurar-erps.md
+++ b/docs/tracks/pt/configurar-erps.md
@@ -23,7 +23,7 @@ Esta seção apresenta o passo-a-passo de confirmação dos ERPs:
 
 Tudo o que você precisa é acessar a tela da integradora clicando em  e, em seguida, na filial utilizada para integrar com Ecommerce, você deve alterar os campos URL de integração e o campo Token, conforme os passos abaixo:
 
-![integra winthor-adaptador](//images.contentful.com/alneenqid6w5/32FkfE0nBRdrWM88p3enOA/7615e676fcc0f84f9a19d2a3e577ccc2/integra_winthor-adaptador.png)
+![integra winthor-adaptador](https://images.contentful.com/alneenqid6w5/32FkfE0nBRdrWM88p3enOA/7615e676fcc0f84f9a19d2a3e577ccc2/integra_winthor-adaptador.png)
 
 1. No campo URL da integração, insira o o endereço: `https://adapterstaging.ciashop.com.br`. 
 2. Após executar todo o processo de validação da integração com o ambiente de homologação (`https://adapterstaging.ciashop.com.br`), você deve requisitar ao time de suporte VTEX CURITIBA, para que seja liberado o acesso ao ambiente de produção do adapter.
@@ -38,9 +38,9 @@ Tudo o que você precisa fazer no ambiente Protheus é alterar os valores  de tr
 1. No ambiente Proteus, acesse o **SigaCFG**. 
 2. No menu lateral, acesse **Ambiente** > **Cadastros**. 
 3. Clique em **Parâmetros**. A seguinte tela será exibida:
-![protheusParametros-adaptador](//images.contentful.com/alneenqid6w5/3aqBRHAGIDIeEuSJUTwPjm/c442a2efa4ea45d6040db8a9e6eeaa62/protheusParametros-adaptador.png)
+![protheusParametros-adaptador](https://images.contentful.com/alneenqid6w5/3aqBRHAGIDIeEuSJUTwPjm/c442a2efa4ea45d6040db8a9e6eeaa62/protheusParametros-adaptador.png)
 4. Na barra de ferramentas superior, clique no botão `FILTRO`. Abrirá a tela **Expressão de Filtro**:
-![protheusParametros2-adaptador](//images.ctfassets.net/alneenqid6w5/5RJ5621Oog3oUS5kzl1Siq/91d3daf359cb35448132f1c68191869d/protheusParametros2-adaptador.png)
+![protheusParametros2-adaptador](https://images.ctfassets.net/alneenqid6w5/5RJ5621Oog3oUS5kzl1Siq/91d3daf359cb35448132f1c68191869d/protheusParametros2-adaptador.png)
 5. Na caixa **campos**, informe `X6_VAR`.
 6. Na caixa **Operadores**, escolha **Contém a expressão**.
 7. Na caixa **expressão** informe `MV_LJEC`.
diff --git a/docs/tracks/pt/configure-customer-identification.md b/docs/tracks/pt/configure-customer-identification.md
index 5f63b4ce1..aa1c0eb86 100644
--- a/docs/tracks/pt/configure-customer-identification.md
+++ b/docs/tracks/pt/configure-customer-identification.md
@@ -26,11 +26,11 @@ Para escolher quais métodos de identificação você deseja habilitar, acesse o
 
 Na caixa __Login do cliente__, você deve selecionar os métodos de identificação que deseja habilitar.
 
-![21. Configure client identification - 1](//images.ctfassets.net/alneenqid6w5/30Kb57zS5TKV5rHY851Xl2/d15329ea3a76733869ecefd3c861e150/21._Configure_client_identification_-_1.png)
+![21. Configure client identification - 1](https://images.ctfassets.net/alneenqid6w5/30Kb57zS5TKV5rHY851Xl2/d15329ea3a76733869ecefd3c861e150/21._Configure_client_identification_-_1.png)
 
 Você também pode alterar a ordem desses métodos. Para isso, basta arrastá-los, como mostra a imagem abaixo. A ordem dos métodos definida nessa tela determina a ordem em que eles aparecerão para o vendedor no aplicativo. Portanto, o primeiro método será o default.
 
-![21. Configure client identification - 2](//images.ctfassets.net/alneenqid6w5/6C2oVlDbGtNMJfllED6pcO/9b62fb9778af207ba77320b67ddab653/21._Configure_client_identification_-_2.png)
+![21. Configure client identification - 2](https://images.ctfassets.net/alneenqid6w5/6C2oVlDbGtNMJfllED6pcO/9b62fb9778af207ba77320b67ddab653/21._Configure_client_identification_-_2.png)
 
 ## Habilitar Usuário Anônimo
 
@@ -38,7 +38,7 @@ Você também pode alterar a ordem desses métodos. Para isso, basta arrastá-lo
 
 Para isso, ainda na tela de Identificação do Cliente, é necessário habilitar a flag __Usuário anônimo__.
 
-![21. Configure client identification - 3](//images.ctfassets.net/alneenqid6w5/62h8jghzR0LhqmnhzXYcws/02869cc40d8244aad5985c4f5483a4e6/21._Configure_client_identification_-_3.png)
+![21. Configure client identification - 3](https://images.ctfassets.net/alneenqid6w5/62h8jghzR0LhqmnhzXYcws/02869cc40d8244aad5985c4f5483a4e6/21._Configure_client_identification_-_3.png)
 
 ## Cadastro de Pessoa Jurídica para vendas B2B
 
@@ -50,10 +50,10 @@ Você poderá, então, escolher se esses campos devem necessariamente ser preenc
 
 No exemplo abaixo, o cadastro de Pessoa Jurídica está ativado e configurado como opcional.
 
-![21. Configure client identification - 4](//images.ctfassets.net/alneenqid6w5/i5hr6RRXlNC0aNHKUvg2C/b309608994fe85592c01abf35f643e84/21._Configure_client_identification_-_4.png)
+![21. Configure client identification - 4](https://images.ctfassets.net/alneenqid6w5/i5hr6RRXlNC0aNHKUvg2C/b309608994fe85592c01abf35f643e84/21._Configure_client_identification_-_4.png)
 
 Neste caso, o aplicativo mostrará para o vendedor um formulário como este abaixo:
 
-![21. Configure client identification - 5](//images.ctfassets.net/alneenqid6w5/4bvM9B3FeukRQaHXXMqLhL/7695d831d0f93a7669f054179467ace2/21._Configure_client_identification_-_5.png)
+![21. Configure client identification - 5](https://images.ctfassets.net/alneenqid6w5/4bvM9B3FeukRQaHXXMqLhL/7695d831d0f93a7669f054179467ace2/21._Configure_client_identification_-_5.png)
 
 Note que é exibida uma flag que permite ao vendedor decidir entre mostrar ou não esses campos adicionais. Isto é porque, nas configurações, marcamos os campos de cadastro de pessoa jurídica como opcionais. Caso sejam marcados como obrigatórios, essa flag não será exibida no aplicativo.
diff --git a/docs/tracks/pt/configure-integration-of-pick-up-points.md b/docs/tracks/pt/configure-integration-of-pick-up-points.md
index ce18e4526..8909bb3e2 100644
--- a/docs/tracks/pt/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/pt/configure-integration-of-pick-up-points.md
@@ -20,7 +20,7 @@ Neste artigo, explicaremos como criar pontos de retirada no Mercado Livre, a par
 
 Quando os pedidos que utilizam a opção de retirada em loja chegam à VTEX, são atribuídos à conta franquia que possui o ponto de retirada escolhido pelo cliente e o ponto de retirada terá seu estoque modificado.
 
-![configurar pontosderetirada01 PT](//images.contentful.com/alneenqid6w5/6V2QIEoUaOUIqNLf5Nfrg6/4a10e2e330c1fa333bbd62f34cf6bcc5/configurar_pontosderetirada01_PT.JPG)
+![configurar pontosderetirada01 PT](https://images.contentful.com/alneenqid6w5/6V2QIEoUaOUIqNLf5Nfrg6/4a10e2e330c1fa333bbd62f34cf6bcc5/configurar_pontosderetirada01_PT.JPG)
 
 <div class="alert alert-info">
 Antes de criar os pontos de retirada, você deve solicitar ao Mercado Livre a ativação da modalidade de Retirada em Loja. Para isso, entre em contato com o seu assessor comercial do Mercado Livre ou abra um chamado com o time de <a href="https://developers.mercadolivre.com.br/devcenter/support">Suporte.</a>
@@ -62,7 +62,7 @@ Para ativar os pontos de retirada nas contas franquias:
 5. No campo **Ativar integração de pontos de retirada para contas franquias**, clique na opção `Sim`.
 6. Clique em `Salvar Configurações`.
 
-![Início (12)](//images.contentful.com/alneenqid6w5/73IhuYUuFMCX3k4tGB0K07/b88a06aa30a5643af251043da2aea2d8/In__cio__12_.gif)
+![Início (12)](https://images.contentful.com/alneenqid6w5/73IhuYUuFMCX3k4tGB0K07/b88a06aa30a5643af251043da2aea2d8/In__cio__12_.gif)
 
 ## Confirmar o envio do ponto de retirada 
 
@@ -73,13 +73,13 @@ Para verificar se o ponto de retirada foi enviado ao Mercado Livre:
 
 Na listagem dos pontos de retirada enviados, você conseguirá visualizar quais foram enviados com sucesso e quais possuem erro de configuração.
 
-![Início (11)](//images.contentful.com/alneenqid6w5/1kHVZxPH1CEtw9v57A56MT/7e60a01cca9d76ba79ffec547b430038/In__cio__11_.gif)
+![Início (11)](https://images.contentful.com/alneenqid6w5/1kHVZxPH1CEtw9v57A56MT/7e60a01cca9d76ba79ffec547b430038/In__cio__11_.gif)
 
 No Mercado Livre não existe uma tela para visualizar se determinado ponto de retirada foi vinculado. Recomendamos escolher um anúncio no Mercado Livre que esteja associado ao ponto de retirada e efetuar uma compra teste, escolhendo a opção Ponto de retirada durante o checkout. Em seguida, confira na lista oferecida pelo Mercado Livre no checkout se o ponto de retirada realmente está disponível.
 
 ## Confirmar a associação do ponto de retirada e anúncio 
 
-![configurar pontosderetirada02 PT](//images.contentful.com/alneenqid6w5/5yvk1AFDsNY62wKdbHzO8N/8e0122b02481b3825f9de7016410835a/configurar_pontosderetirada02_PT.JPG)
+![configurar pontosderetirada02 PT](https://images.contentful.com/alneenqid6w5/5yvk1AFDsNY62wKdbHzO8N/8e0122b02481b3825f9de7016410835a/configurar_pontosderetirada02_PT.JPG)
 
 Para confirmar se o ponto de retirada foi corretamente associado ao anúncio do Mercado Livre, você deve verificar quais pontos de retirada estão sincronizados com cada SKU e seus respectivos estoques. Siga os passos abaixo:
 
@@ -90,4 +90,4 @@ Para confirmar se o ponto de retirada foi corretamente associado ao anúncio do
 
 Não tendo ocorrido nenhum erro com o SKU localizado, os pontos de retirada estarão sincronizados com ele, e seus respectivos estoques serão apresentados na lista.
 
-![Início (10)](//images.contentful.com/alneenqid6w5/2w5jyORw3v1VIg5Cd0rJX7/45eb1cacfa766718460386f73355ae96/In__cio__10_.gif)
+![Início (10)](https://images.contentful.com/alneenqid6w5/2w5jyORw3v1VIg5Cd0rJX7/45eb1cacfa766718460386f73355ae96/In__cio__10_.gif)
diff --git a/docs/tracks/pt/configure-integration.md b/docs/tracks/pt/configure-integration.md
index 114968f6b..35c7fbc6b 100644
--- a/docs/tracks/pt/configure-integration.md
+++ b/docs/tracks/pt/configure-integration.md
@@ -34,15 +34,15 @@ Feito isso, a integração da sua loja VTEX com o Magalu Marketplace estará con
 
 | **Campo** | **Descrição** | **Exemplo**|
 |---|---|---|
-| **Integração*** | Marque como *Ativada* para que a integração comece a operar. Se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos. | ![Integração Magalu](//images.ctfassets.net/alneenqid6w5/3h6E673Nx6xsCpjbqGAjYd/d8b34130a2a85301b469a5f5fea55f45/integra____o_magalu.png) |
+| **Integração*** | Marque como *Ativada* para que a integração comece a operar. Se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos. | ![Integração Magalu](https://images.ctfassets.net/alneenqid6w5/3h6E673Nx6xsCpjbqGAjYd/d8b34130a2a85301b469a5f5fea55f45/integra____o_magalu.png) |
 | **CNPJ*** | CNPJ utilizado no cadastrado no portal Magalu Marketplace. Inserir apenas números, sem caracteres especiais. | **45121594000127** |
 | **Id do afiliado*** | Código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não. Vogais não são aceitas. A configuração do conector cria automaticamente o afiliado. | **MGZ** |
 | **Política Comercial*** | ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será utilizada para a integração com o Magalu Marketplace. Todos os produtos vinculados a esta política comercial serão enviados para o marketplace. | **1** |
 | **Série da Nota Fiscal*** | Numeração da série de um grupo de notas fiscais. Caso nenhum valor seja preenchido, o sistema automaticamente vai atribuir o número 1. |**123**|
 | **Estoque Mínimo*** | Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização do Magalu pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial. Se o saldo do SKU estiver igual ou abaixo do valor configurado, será enviado saldo 0 para o marketplace. | **3** |
 | **Mapeamento de SLA Customizável** | Tipo de Entrega Magalu x Tipo de Entrega VTEX. No caso do seu Tipo de Entrega Magalu ter um nome diferente da sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), é necessário fazer uma convergência de denominação **(de > para)** entre ambos.É possível associar vários Tipos de Entrega Magalu a uma mesma política de envio na VTEX, e não há um número limite de tipos de entrega que podem ser cadastrados no Magalu Marketplace. Você também pode alterar os valores padrões do Tipo de entrega Magalu (de até 50 caracteres) para que tenham os mesmos nomes das suas políticas de envio. Neste caso, o mapeamento da correspondência não será necessário, pois os valores serão idênticos. O pedido só será integrado na VTEX se estiver relacionado a uma [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3). Mesmo quando a entrega é feita pelo Magalu Marketplace, é necessário haver uma correspondência entre a sua política de envio e o seu Tipo de Entrega Magalu, seja por meio do mapeamento entre valores diferentes ou utilizando valores idênticos. Os Correios (PAC) são usados como transportadoras, seu Tipo de Entrega no Magalu se chama NORMAL, e sua política de envio (nome dado ao seu método de envio) na VTEX é Comum. Portanto, você deve preencher o primeiro campo com NORMAL e o segundo com Comum. Esteja atento para letras maiúsculas, minúsculas e espaçamentos. | <p><b>NORMAL > Comum</b></p>|
-| **Enviar Kit*** | Ao escolher Não, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para o Magalu Marketplace. Ao habilitar Sim, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudar sua configuração de *Sim* para *Não*, SKUs enviados anteriormente para o Magalu não são removidos ou alterados. Com a opção Não ativada, tentativas de envio para o Magalu Marketplace de SKUs cadastrados como kit resultam no seguinte aviso: `O conector está configurado para não enviar SKUs do tipo Kit.`  Esta mensagem pode ser visualizada no Admin VTEX, em **Marketplace > Conexões > Produtos**, clicando no SKU. | ![Enviar kit Magalu](//images.ctfassets.net/alneenqid6w5/27gXQYqGSyzJlJPIcOkFKh/fefbd13c07f92ce502972d47bfe7d18e/enviar_kit_magalu.png) |
-| **Ativar estoque para entrega de cotação de frete para contas franquias*** | Com a opção *Sim* selecionada, a funcionalidade [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) permite que você venda na Magalu produtos dos estoques das suas contas franquias. Ou seja, o estoque de contas franquias é disponibilizado para *fullfilment* de pedidos na Magalu. | ![Ativar estoque Magalu](//images.ctfassets.net/alneenqid6w5/4AfIZTX6Oe5KPRUOlmoBug/4d7f29cc1480552f6a2897b409599403/ativar_estoque_magalu.png) |
+| **Enviar Kit*** | Ao escolher Não, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para o Magalu Marketplace. Ao habilitar Sim, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudar sua configuração de *Sim* para *Não*, SKUs enviados anteriormente para o Magalu não são removidos ou alterados. Com a opção Não ativada, tentativas de envio para o Magalu Marketplace de SKUs cadastrados como kit resultam no seguinte aviso: `O conector está configurado para não enviar SKUs do tipo Kit.`  Esta mensagem pode ser visualizada no Admin VTEX, em **Marketplace > Conexões > Produtos**, clicando no SKU. | ![Enviar kit Magalu](https://images.ctfassets.net/alneenqid6w5/27gXQYqGSyzJlJPIcOkFKh/fefbd13c07f92ce502972d47bfe7d18e/enviar_kit_magalu.png) |
+| **Ativar estoque para entrega de cotação de frete para contas franquias*** | Com a opção *Sim* selecionada, a funcionalidade [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) permite que você venda na Magalu produtos dos estoques das suas contas franquias. Ou seja, o estoque de contas franquias é disponibilizado para *fullfilment* de pedidos na Magalu. | ![Ativar estoque Magalu](https://images.ctfassets.net/alneenqid6w5/4AfIZTX6Oe5KPRUOlmoBug/4d7f29cc1480552f6a2897b409599403/ativar_estoque_magalu.png) |
 | **Estratégia de envio para cotação de frete (Válida apenas caso a configuração de estoque e cotação para contas franquias estiver ativa)** | É possível escolher entre duas opções de frete. <p><b>Mais barato:</b> a escolha de estoque para fulfillment do pedido é feita com base no menor preço, mas o envio do produto leva mais tempo.</p> <p><b>Mais rápido:</b> a escolha de estoque para fulfillment do pedido é feita com base no menor tempo, mas o envio do produto custa mais caro.</p>| |
 |**Etiqueta de entrega**| Qual o tipo do arquivo da etiqueta de entrega deve ser disponibilizada. | PDF ou ZPL |
 | <b>Mapeamento de Certificados de Homologação (ANATEL, INMETRO, ANVISA e MAPA)</b> | Devido à <a href="https://www.gov.br/anatel/pt-br/assuntos/noticias/marketplaces-adotam-medidas-para-coibir-venda-de-produtos-nao-homologados">determinação da Anatel</a>, produtos da categoria Smartphones e Celulares deverão possuir obrigatoriamente uma <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin">especificação de produto</a> cadastrada com o código de homologação da Anatel para serem comercializados no Magalu Marketplace. Por isso, é necessário preencher este campo com o nome da especificação de produto criada e o código de homologação do produto disponibilizado pela Anatel. Você poderá cadastrar a especificação com o nome que quiser. <p>Se o certificado de homologação não for mapeado, os produtos apresentarão erros de integração. Para cadastrar a especificação, você irá preencher os campos <b>DE e PARA</b> e clicar no botão <b>+</b>.</p>Você pode cadastrar quantas especificações forem necessárias.| <b> CERTIFICADO_1 > ANATEL </b>|
diff --git a/docs/tracks/pt/configuring-a-payment-condition.md b/docs/tracks/pt/configuring-a-payment-condition.md
index acc6dd961..0c05dd41c 100644
--- a/docs/tracks/pt/configuring-a-payment-condition.md
+++ b/docs/tracks/pt/configuring-a-payment-condition.md
@@ -98,7 +98,7 @@ Caso você decida configurar um meio de pagamento que aceite parcelas com juros,
 A opção de Parcelamento Automático permite que você configure os detalhes dos parcelamentos diretamente no provedor de pagamento (externamente ao ambiente VTEX).
 Para habilitar esta opção, selecione “Sim” no campo **Usar parcelamento externo** durante a etapa de [configuração de provedores](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
 
-![parcelamentoautomatico](//images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/f05aa9a6c8ed312d82a5aa2e51b5fa03/parcelamentoautomaticobr.JPG)
+![parcelamentoautomatico](https://images.ctfassets.net/alneenqid6w5/3ErHSFlSGyUwbLzJWaUlXw/f05aa9a6c8ed312d82a5aa2e51b5fa03/parcelamentoautomaticobr.JPG)
 
 Após habilitar o parcelamento automático no provedor, siga os seguintes passos:
 
diff --git a/docs/tracks/pt/configuring-banners.md b/docs/tracks/pt/configuring-banners.md
index 20ed85781..bd3cc5c30 100644
--- a/docs/tracks/pt/configuring-banners.md
+++ b/docs/tracks/pt/configuring-banners.md
@@ -28,7 +28,7 @@ Depois de realizar as configurações do banner, você deve adicioná-lo a uma p
   <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
 </div>
 
-![banner-form-pt](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
+![banner-form-pt](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
 
 ## Campos de cadastro do banner
 
@@ -59,7 +59,7 @@ Para cadastrar o banner, é necessário preencher os seguintes campos:
 
 Clique em <i class="fa-solid fa-link"></i> `Preencher a partir de uma URL` para adicionar a URL da página de busca em as regras de ativação serão aplicadas. 
 
-![banner-url-pt](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
+![banner-url-pt](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
 
 Clique em <i class="fas fa-plus"></i> `Adicionar condição` para criar uma regra. Elas podem ser dos seguintes tipos:
 
diff --git a/docs/tracks/pt/configuring-cash-payments-through-instore.md b/docs/tracks/pt/configuring-cash-payments-through-instore.md
index cb0e54884..a4155eaa7 100644
--- a/docs/tracks/pt/configuring-cash-payments-through-instore.md
+++ b/docs/tracks/pt/configuring-cash-payments-through-instore.md
@@ -32,7 +32,7 @@ Agora vamos criar a condição de pagamento.
 1. Ainda na página **Configurações**, clique na aba **Condições de pagamento**.
 2. Clique no botão verde com o ícone de `+` para adicionar uma nova condição, conforme destacado abaixo.
 
-![pt-add-payment-condition](//images.contentful.com/alneenqid6w5/27933kBohPNieKSiiulGZA/dba7411939d50fe127453f77a9ec727d/pt-add-payment-condition.png)
+![pt-add-payment-condition](https://images.contentful.com/alneenqid6w5/27933kBohPNieKSiiulGZA/dba7411939d50fe127453f77a9ec727d/pt-add-payment-condition.png)
 
 3. Na seção **Pagamento Customizado**, clique na opção **Dinheiro** que você criou anteriormente.
 4. Dê um nome para essa condição de pagamento, mude o status para **Ativa** e, no seletor **Processar com a afiliação**, escolha o pagamento customizado que você criou no passo anterior.
diff --git a/docs/tracks/pt/configuring-dafiti-connector.md b/docs/tracks/pt/configuring-dafiti-connector.md
index 5b06f897e..4be568d22 100644
--- a/docs/tracks/pt/configuring-dafiti-connector.md
+++ b/docs/tracks/pt/configuring-dafiti-connector.md
@@ -48,7 +48,7 @@ Com a opção <i>Não</i> ativada, tentativas de envio para a Dafiti de SKUs cad
 
 - **Nome do SKU*:** determina qual será a regra para nomeação de SKUs no portal da Dafiti. Você deve selecionar uma das combinações disponíveis dos seguintes atributos: _Marca_, _Nome do Produto_ e _Nome do SKU_.
 
-![print nome exibicao produto es](//images.ctfassets.net/alneenqid6w5/3MiGbDbIXFGiawLcXjji5w/62b3d417ca2cfc58e13f8602c482ff23/print_nome_exibicao_produto.png)
+![print nome exibicao produto es](https://images.ctfassets.net/alneenqid6w5/3MiGbDbIXFGiawLcXjji5w/62b3d417ca2cfc58e13f8602c482ff23/print_nome_exibicao_produto.png)
 
 > Exemplo: meu produto é um tênis preto da marca Nike. O _Nome do SKU_ que eu selecionei foi _Marca - Nome do Produto - Nome do SKU_. Assim, o nome que aparecerá no portal da Dafiti será _Nike tênis preto_.
 
diff --git a/docs/tracks/pt/configuring-login-with-facebook.md b/docs/tracks/pt/configuring-login-with-facebook.md
index af490978d..d5266c453 100644
--- a/docs/tracks/pt/configuring-login-with-facebook.md
+++ b/docs/tracks/pt/configuring-login-with-facebook.md
@@ -28,7 +28,7 @@ Após a configuração no Facebook, é preciso configurar essa opção de login
 1.  No módulo de **Configurações da Conta**, acesse a aba de **Autenticação**.
 2.  Clique no botão **Editar** correspondente ao Facebook.
 3.  Preencha os campos com o _Client Id_ e o _Client Secret_ cadastrados no **Facebook**.
-    ![Facebook OAuth PT](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/c07c9d4160e7273a0f5ad2a0cabd1bec/facebook_PT.png)
+    ![Facebook OAuth PT](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/c07c9d4160e7273a0f5ad2a0cabd1bec/facebook_PT.png)
 4.  Clique no botão **Salvar**. 
 5.  Para validar se o login foi feito corretamente, acesse o front-end da sua loja e clique em **Login**.
 6. Aparecerão as opções de login configuradas. Clique na opção **Facebook** e confira se o nome da sua loja é exibido.
diff --git a/docs/tracks/pt/configuring-login-with-google.md b/docs/tracks/pt/configuring-login-with-google.md
index db80158fc..c2afd5735 100644
--- a/docs/tracks/pt/configuring-login-with-google.md
+++ b/docs/tracks/pt/configuring-login-with-google.md
@@ -29,7 +29,7 @@ Após a configuração no Google, é preciso configurar o login na VTEX.
 1.  No módulo de **Configurações da Conta**, acesse a aba de **Autenticações**.
 2.  Clique no botão **Editar** correspondente ao Google.
 3.  Preencha os campos com o _Client Id_ e o _Client Secret_ cadastrados no **Google**.
-    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
+    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
 4.  Clique no botão **Salvar**.
 5.  Para validar se o login foi feito corretamente, acesse o front-end da sua loja e clique em **Login**.
 6. Aparecerão as opções de login configuradas. Clique na opção **Google** e veja se o nome da sua loja é exibido.
diff --git a/docs/tracks/pt/configuring-redirect.md b/docs/tracks/pt/configuring-redirect.md
index ce3edea52..3380e8a54 100644
--- a/docs/tracks/pt/configuring-redirect.md
+++ b/docs/tracks/pt/configuring-redirect.md
@@ -26,7 +26,7 @@ Para configurar um redirecionamento, você precisa seguir os passos a seguir:
 
 Você deve preencher os seguintes campos:
 
-![redirecionamentos-adminv4-PT](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
+![redirecionamentos-adminv4-PT](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
 
 ### Informações gerais
 
diff --git a/docs/tracks/pt/configuring-ship-from-store.md b/docs/tracks/pt/configuring-ship-from-store.md
index ce24a4593..3208e88c2 100644
--- a/docs/tracks/pt/configuring-ship-from-store.md
+++ b/docs/tracks/pt/configuring-ship-from-store.md
@@ -16,7 +16,7 @@ trackSlugPT: estrategias-de-comercio-unificado
 
 A estratégia de **Ship From Store** se dá quando o cliente deseja receber os produtos em casa e esses produtos partem do estoque de uma loja física. Ou seja, neste cenário, a loja funciona como um mini centro de distribuição.
 
-![35. Setting up Shipping From Store - 1](//images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
+![35. Setting up Shipping From Store - 1](https://images.ctfassets.net/alneenqid6w5/7uHIuX10TvTGJS1kkwPmBb/6847796e390c9d18123eea24f87469c4/35._Setting_up_Shipping_From_Store_-_1.png)
 
 Esse tipo de logística ajuda sua operação a reduzir custos e tempo de envio. Isto porque, em vez de contar apenas com os estoques principais - geralmente afastados da zonas centrais das cidades - você passa a ter uma rede mais capilarizada de entrega. 
 
diff --git a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 03e32466c..7c8baf56a 100644
--- a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -40,7 +40,7 @@ Para que a integração funcione corretamente, o recomendável é conceder todas
 10. Clique em `Avançar`.
 11. Na janela aberta, aparecerá uma confirmação de que a integração foi realizada. Clique em `Concluir`.
 
-![gif pt v1](//images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/a677146be91000f363e02c81cd5e6e25/gif_pt_v1.gif)
+![gif pt v1](https://images.ctfassets.net/alneenqid6w5/1FptUh8HMlsK1FvVPBw89H/a677146be91000f363e02c81cd5e6e25/gif_pt_v1.gif)
 
 ## Envio de dados dos produtos para o Facebook Business Extension
 
diff --git a/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index ea3b50d5b..d8ed2a9d0 100644
--- a/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -84,7 +84,7 @@ Depois de preencher o formulário de configuração da integração, você preci
 
 Na página **Set up TikTok For Business** (Configurar o TikTok For Business), ilustrada abaixo, é necessário cumprir as instruções de configuração descritas a seguir.
 
-![set-up-tiktok-for-business](//images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
+![set-up-tiktok-for-business](https://images.ctfassets.net/alneenqid6w5/77d9v0437SxRBVXD0OUmW/290a1ece93c0fcb0fe91a1da61352513/image2.png)
 
 1. Clique na seção **TikTok For Business Account** e verifique se a sua conta está listada.
     * Caso queira conectar outra conta, clique em `Disconnect` e repita a etapa de login descrita em [Conectar a conta do TikTok](#conectar-a-conta-do-tiktok).
@@ -105,7 +105,7 @@ Na página **Set up TikTok For Business** (Configurar o TikTok For Business), il
 
 Ao concluir essa configuração, você será conduzido novamente para **Marketplace > TikTok** no Admin VTEX, onde poderá [gerenciar a integração](https://help.vtex.com/pt/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd/24SfBYkRkKMaetgjLDKgaP). Para algumas versões do Admin VTEX, a página se encontra em **Aplicativos > Meus Aplicativos > TikTok**. Após a configuração ter sido concluída com sucesso, qualquer usuário logado no Admin VTEX poderá acessar essa área de gerenciamento do TikTok. 
 
-![tiktok-config-3](//downloads.ctfassets.net/alneenqid6w5/4gryDGvlRXWO50awLjcpBx/6f225b366777870d8eed7dd33f90614a/tiktok-config-3.gif)
+![tiktok-config-3](https://downloads.ctfassets.net/alneenqid6w5/4gryDGvlRXWO50awLjcpBx/6f225b366777870d8eed7dd33f90614a/tiktok-config-3.gif)
 
 ### Envio de dados dos produtos para o TikTok
 
diff --git a/docs/tracks/pt/configuring-the-relevance-feature.md b/docs/tracks/pt/configuring-the-relevance-feature.md
index 378e42a38..8c89d6b39 100644
--- a/docs/tracks/pt/configuring-the-relevance-feature.md
+++ b/docs/tracks/pt/configuring-the-relevance-feature.md
@@ -34,7 +34,7 @@ Há duas áreas de configuração dessa funcionalidade: __Critérios prioritári
   <li><b>Score do Catálogo:</b> 3</li>
 </ul>
 
-![default priority criteria PT](//images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/092139dbd13f66e3b061fba36704450a/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_19_41.png)
+![default priority criteria PT](https://images.ctfassets.net/alneenqid6w5/46WH9rGu8E2dpDry9i7uQ3/092139dbd13f66e3b061fba36704450a/screencapture-biggy-myvtex-admin-search-boost-settings-2021-06-23-16_19_41.png)
 
 Para alterar a configuração de Relevância, siga os passos abaixo.
 
@@ -42,7 +42,7 @@ Para alterar a configuração de Relevância, siga os passos abaixo.
 2. Clique em __Configuração de relevância__.
 3. Escolha o critério cujo peso você deseja alterar.
 4. Arraste o indicador para o número desejado, utilizando o cursor, conforme demonstrado na imagem abaixo.
-  ![composicao-criterios-pt](//images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/008effff0981f64be5a28b8b4cc53063/composicao-criterios-pt.gif)
+  ![composicao-criterios-pt](https://images.ctfassets.net/alneenqid6w5/6qRT6JsD2MecPTXHksGIMa/008effff0981f64be5a28b8b4cc53063/composicao-criterios-pt.gif)
   Caso você queira mudar a posição de um critério de __Composição de critérios__ para __Critérios prioritários__, basta arrastá-lo pelo ícone <i class="fas fa-bars"></i> para a área superior, conforme demonstrado abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso.
-  ![criterios-prioritarios-pt](//images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/4cf717f0197e391b10d723dc13bfb57b/criterios-prioritarios-pt.gif)
+  ![criterios-prioritarios-pt](https://images.ctfassets.net/alneenqid6w5/51sDib8UqJmQJmcqyIDSIE/4cf717f0197e391b10d723dc13bfb57b/criterios-prioritarios-pt.gif)
 5. Para finalizar, clique em __Salvar__.
diff --git a/docs/tracks/pt/create-a-brand.md b/docs/tracks/pt/create-a-brand.md
index 494a5f913..d34f2094e 100644
--- a/docs/tracks/pt/create-a-brand.md
+++ b/docs/tracks/pt/create-a-brand.md
@@ -18,7 +18,7 @@ Todo produto em sua loja precisa fazer parte de uma categoria, mas precisa tamb
 
 Para cadastrá-la, siga os passos abaixo:
 
-1. No módulo __Catalog__, passe o mouse na aba __Cadastro de produtos__ e clique na opção __Marca__.![Marca](//images.contentful.com/alneenqid6w5/BmTrfJzB0kWa6ouku6Uc8/4f57e62ab6dd7e51f65b2dc1f7235dc4/Marca.png)
+1. No módulo __Catalog__, passe o mouse na aba __Cadastro de produtos__ e clique na opção __Marca__.![Marca](https://images.contentful.com/alneenqid6w5/BmTrfJzB0kWa6ouku6Uc8/4f57e62ab6dd7e51f65b2dc1f7235dc4/Marca.png)
 2. Clique no botão __Nova marca__.
 3. Insira o nome da marca no campo __Nome__.
 4. Preencha o campo __Título da Página da Marca (Tag Title)__ com o título que aparecerá na barra do navegador quando o usuário acessar a página da marca.
diff --git a/docs/tracks/pt/create-a-category.md b/docs/tracks/pt/create-a-category.md
index bb757bc7e..bf9783fba 100644
--- a/docs/tracks/pt/create-a-category.md
+++ b/docs/tracks/pt/create-a-category.md
@@ -20,14 +20,14 @@ Depois que a sua árvore de categorias estiver definida, você já pode inserir
 
 Na VTEX, o cadastro de categorias é feito no módulo __Catalog__.
 
-1. No menu da topbar do seu admin, clique em __Catalog__ (se você já não estiver lá).![Catalog](//images.contentful.com/alneenqid6w5/48wP1cDIw0EwoeOUY8OGWI/8874d5f10e57364c7d78852d5b48aed4/catalog.png)
-2. Nas opções da aba __Cadastro de Produtos__, clique em __Categoria__.![Categoria](//images.contentful.com/alneenqid6w5/2w0IBMGwik0AGauGA4Eu0G/260db5fed8cca932f10b194a05a5f9c1/Categoria.png)
+1. No menu da topbar do seu admin, clique em __Catalog__ (se você já não estiver lá).![Catalog](https://images.contentful.com/alneenqid6w5/48wP1cDIw0EwoeOUY8OGWI/8874d5f10e57364c7d78852d5b48aed4/catalog.png)
+2. Nas opções da aba __Cadastro de Produtos__, clique em __Categoria__.![Categoria](https://images.contentful.com/alneenqid6w5/2w0IBMGwik0AGauGA4Eu0G/260db5fed8cca932f10b194a05a5f9c1/Categoria.png)
 
 No lado esquerdo da tela, você vê o nível mais alto de categorias, que por padrão tem o nome __Categorias__. É dentro dele que vamos distribuir as categorias da sua árvore.
 Clique nele e siga os passos abaixo:
 
-1. Clique no botão __ações__ que aparece à direita da sua tela.![acoes](//images.contentful.com/alneenqid6w5/lIbUp2QFuSckgmwsSGigE/41351e98a797a11deeb60d7bf7b0cac5/acoes.png)
-2. Clique na opção __Incluir__.![incluir](//images.contentful.com/alneenqid6w5/3DGlwjNNpmsW80AYS6CM4Q/3ccf2d1d74bb18e7ebd234977b1137ec/incluir.png)
+1. Clique no botão __ações__ que aparece à direita da sua tela.![acoes](https://images.contentful.com/alneenqid6w5/lIbUp2QFuSckgmwsSGigE/41351e98a797a11deeb60d7bf7b0cac5/acoes.png)
+2. Clique na opção __Incluir__.![incluir](https://images.contentful.com/alneenqid6w5/3DGlwjNNpmsW80AYS6CM4Q/3ccf2d1d74bb18e7ebd234977b1137ec/incluir.png)
 
 Você pode ver a lista completa dos campos de cadastro de categoria [neste artigo](/pt/tutorial/campos-de-cadastro-de-categoria).
 Mas aqui vamos nos ater apenas a alguns campos.
diff --git a/docs/tracks/pt/create-a-product.md b/docs/tracks/pt/create-a-product.md
index 7d8e22984..7521baec3 100644
--- a/docs/tracks/pt/create-a-product.md
+++ b/docs/tracks/pt/create-a-product.md
@@ -45,8 +45,8 @@ Vamos ver como criar o produto.
 No módulo __Catalog__, siga os passos abaixo:
 
 1. Passe o mouse na aba __Cadastro de Produtos__.
-2. Vá até a opção __Produtos e SKUs__ e clique em __Cadastro de Produtos e SKUs__.![Produto1](//images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
-3. Clique no botão __Adicionar Produto__.![Produto2](//images.contentful.com/alneenqid6w5/2HhkAREgQMMAkIMm8GaGgQ/7038413048c0611edb9079acd73020ba/Produto2.png)
+2. Vá até a opção __Produtos e SKUs__ e clique em __Cadastro de Produtos e SKUs__.![Produto1](https://images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
+3. Clique no botão __Adicionar Produto__.![Produto2](https://images.contentful.com/alneenqid6w5/2HhkAREgQMMAkIMm8GaGgQ/7038413048c0611edb9079acd73020ba/Produto2.png)
 
 Você será levado para a tela de cadastro de produto.
 
diff --git a/docs/tracks/pt/create-an-sku.md b/docs/tracks/pt/create-an-sku.md
index e20d464ee..40bca3c38 100644
--- a/docs/tracks/pt/create-an-sku.md
+++ b/docs/tracks/pt/create-an-sku.md
@@ -19,9 +19,9 @@ Depois de criar o produto, é hora de criar o primeiro SKU que fará parte desse
 Se, após preenchidos os campos do [cadastro de produto](/pt/getting-started/crie-um-produto), você clicar em __Salvar e cadastrar SKU__, a tela que aparece em seguida será justamente a de cadastro de SKU.
 
 Mas também é possível chegar ao cadastro de SKU pelo caminho abaixo:
-1. Entre no módulo __Catalog__ e, na aba __Cadastro de produtos__, vá até a opção __Produtos e SKUs__ e clique em __Cadastro de produtos e SKUs__.![Produto1](//images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
+1. Entre no módulo __Catalog__ e, na aba __Cadastro de produtos__, vá até a opção __Produtos e SKUs__ e clique em __Cadastro de produtos e SKUs__.![Produto1](https://images.contentful.com/alneenqid6w5/4X1QYKrHz2ysAEAAW6gK6/85b81671add3f7573a9c4531b215ba82/Produto1.png)
 2. Clique na seta do botão azul, na linha do produto para o qual quer criar o SKU, e depois na opção __SKU__.
-3. Clique no botão __Novo SKU__.![novoSKU](//images.contentful.com/alneenqid6w5/5VonhvkjXaoma84SqGuYSQ/f072e69753933862ba5ad205f9a55ecd/novoSKU.gif)
+3. Clique no botão __Novo SKU__.![novoSKU](https://images.contentful.com/alneenqid6w5/5VonhvkjXaoma84SqGuYSQ/f072e69753933862ba5ad205f9a55ecd/novoSKU.gif)
 
 Você será levado para a tela de cadastro de SKU.
 
diff --git a/docs/tracks/pt/create-brands.md b/docs/tracks/pt/create-brands.md
index 84355b65b..2e61974c8 100644
--- a/docs/tracks/pt/create-brands.md
+++ b/docs/tracks/pt/create-brands.md
@@ -39,7 +39,7 @@ As informações preenchidas no cadastro podem ser atualizadas a qualquer moment
 
 Para excluir o cadastro de alguma marca, você deve clicar na seta ao lado de  `Alterar ` e selecionar a opção `Excluir`. 
 
-![editar-marca pt](//images.ctfassets.net/alneenqid6w5/3lz8nIX88GLSISJCiFk1h7/c45e2225e20611d450e91f3e97bc24c9/editar-marca_PT.png)
+![editar-marca pt](https://images.ctfassets.net/alneenqid6w5/3lz8nIX88GLSISJCiFk1h7/c45e2225e20611d450e91f3e97bc24c9/editar-marca_PT.png)
 
 ## API
 
diff --git a/docs/tracks/pt/create-the-category-tree.md b/docs/tracks/pt/create-the-category-tree.md
index 4a52a5f76..870aa155e 100644
--- a/docs/tracks/pt/create-the-category-tree.md
+++ b/docs/tracks/pt/create-the-category-tree.md
@@ -38,7 +38,7 @@ No início do projeto, antes que qualquer produto seja inserido na plataforma, v
 
 Este, portanto, poderia ser o desenho inicial da árvore de categorias da sua loja:
 
-![diagrama-help](//images.contentful.com/alneenqid6w5/5W7d9NCYCscs6wks2gGQW8/176a2ae08c349fd0473ae796dead9d29/diagrama-help.png)
+![diagrama-help](https://images.contentful.com/alneenqid6w5/5W7d9NCYCscs6wks2gGQW8/176a2ae08c349fd0473ae796dead9d29/diagrama-help.png)
 
 __OBS__: a nomenclatura __Departamento / Categoria / Subcategoria__ é apenas uma maneira de enxergar a sua árvore, e que pode ou não facilitar seu trabalho. A plataforma não exige este ou qualquer outro padrão de nomenclatura. Para a VTEX, quaisquer níveis que venham a ser criados para a distribuição dos seus produtos são tomados apenas como níveis de categoria.
 
diff --git a/docs/tracks/pt/creating-accounts.md b/docs/tracks/pt/creating-accounts.md
index de0386c2a..27e8be490 100644
--- a/docs/tracks/pt/creating-accounts.md
+++ b/docs/tracks/pt/creating-accounts.md
@@ -40,7 +40,7 @@ Para cadastrar um novo cliente no Customer Credit, siga os passos abaixo:
 
 A partir deste momento, a nova conta criada será exibida na tela de __Contas__.
 
-![CC_criar_conta_1_PT](//images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/d260357ee6bb9151e7dfc99d8fc72e90/CC_criar_conta_1_PT.JPG)
+![CC_criar_conta_1_PT](https://images.ctfassets.net/alneenqid6w5/5Kpskv3ba4pSvVpPROQQQf/d260357ee6bb9151e7dfc99d8fc72e90/CC_criar_conta_1_PT.JPG)
 
 ## Criar múltiplas contas (importação em massa)
 
@@ -57,7 +57,7 @@ Para criar múltiplas contas ao mesmo tempo (em massa) no Customer Credit, você
   <li>Colunas <b>Credit limit</b> e <b>Tolerance rate</b>: valores disponibilizados para cada cliente. O <b>Tolerance rate</b> deve ser inserido em formato decimal, por exemplo, uma tolerância de 5% deve ser indicada como 0.05.</li>
 </ul>
 
-![CC_criar_conta_2_ALL](//images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
+![CC_criar_conta_2_ALL](https://images.ctfassets.net/alneenqid6w5/2KwguLYrq4sasC46xAIUfV/9b504a53cbf5796f78fafc77c5125e22/CC_criar_conta_2_ALL.JPG)
 
 <blockquote><ui>6. Salve a planilha .csv.</ui>
 
diff --git a/docs/tracks/pt/creating-merchandising-rules-visual-editor.md b/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
index 2593d0593..0746e0d12 100644
--- a/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
+++ b/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
@@ -48,7 +48,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
 
 O Editor visual de regras de merchandising do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
 
-![visual-merch-rules-PT-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
+![visual-merch-rules-PT-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
@@ -84,7 +84,7 @@ O Editor visual de regras de merchandising do VTEX Intelligent Search permite re
 
 O filtro é um atributo selecionável pré-definido que restringe os resultados da busca, por exemplo, possibilitando filtrar por todos os produtos de uma categoria ou marca, entre outras condições. Você pode adicionar uma ou mais condições a um filtro, conforme ilustrado a seguir.
 
-![filtros-merchrules-pt](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
+![filtros-merchrules-pt](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
 
 Para adicionar uma condição no Editor visual, siga o passo a passo abaixo. 
 
diff --git a/docs/tracks/pt/creating-or-editing-a-page-template.md b/docs/tracks/pt/creating-or-editing-a-page-template.md
index 883d21549..c047e70ec 100644
--- a/docs/tracks/pt/creating-or-editing-a-page-template.md
+++ b/docs/tracks/pt/creating-or-editing-a-page-template.md
@@ -41,8 +41,8 @@ Confira o passo a passo a seguir:
 <li><code>admin</code></li>
 </ul></p>
 </div>
-7. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
-8. No canto superior direito, clique no botão __Save Template__.![4 2](//images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
+7. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+8. No canto superior direito, clique no botão __Save Template__.![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
 Para editar um template já existente, o processo é quase idêntico.
 
diff --git a/docs/tracks/pt/creating-regular-promotions.md b/docs/tracks/pt/creating-regular-promotions.md
index 34b54e045..980aa0a68 100644
--- a/docs/tracks/pt/creating-regular-promotions.md
+++ b/docs/tracks/pt/creating-regular-promotions.md
@@ -111,7 +111,7 @@ Você pode incluir ou excluir **Categorias**, **Marcas**, **Coleções**, **Prod
 
 Para serem válidos na promoção, os produtos precisam atender a todas as condições cadastradas nesta seção.
 
-![A quais itens esta promoção será aplicada - PT](//images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/811aa40a0ac7caaf32b2e04e9dd438f6/A_quais_itens.png)
+![A quais itens esta promoção será aplicada - PT](https://images.ctfassets.net/alneenqid6w5/7lxp9shJsZD5LBMzXldQnz/811aa40a0ac7caaf32b2e04e9dd438f6/A_quais_itens.png)
 
 # 3. Quais as condições para a promoção ser válida?
 
diff --git a/docs/tracks/pt/credit-card-payment-flow.md b/docs/tracks/pt/credit-card-payment-flow.md
index df6921564..b976df8ca 100644
--- a/docs/tracks/pt/credit-card-payment-flow.md
+++ b/docs/tracks/pt/credit-card-payment-flow.md
@@ -28,7 +28,7 @@ Para saber mais sobre os agentes financeiros envolvidos no fluxo de pagamento de
 
 O fluxo completo para pagamento por cartão de crédito na VTEX pode ser descrito pela imagem abaixo. 
 
-![Cartão de crédito - Fluxo básico de um pagamento](//images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/424c414ed06f81c4edcc676773fd00d9/Fluxo_Cart__o_de_Cr__dito.jpg)
+![Cartão de crédito - Fluxo básico de um pagamento](https://images.ctfassets.net/alneenqid6w5/64zjpwrBkpqbOhR7vtZhKs/424c414ed06f81c4edcc676773fd00d9/Fluxo_Cart__o_de_Cr__dito.jpg)
 
 1. Na tela de Checkout da sua loja, o cliente escolhe o  **Meio de Pagamento**  _cartão de crédito_ para realizar o pagamento de sua compra.  
 
diff --git a/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md b/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
index 210013795..db57eaa34 100644
--- a/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
+++ b/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
@@ -50,4 +50,4 @@ Neste caso, ao comparar o peso real com o peso cubado do pacote, a transportador
 
 Ao realizar o cadastro da sua transportadora, esse é o valor que você deve preencher no campo Fator Cúbico de Peso.
 
-![PesoCubado](//images.contentful.com/alneenqid6w5/ZzHF9fwwec6c6m2AiyYGS/37343a8bb4858cdf296f5a3c450567f3/PesoCubado.png)
+![PesoCubado](https://images.contentful.com/alneenqid6w5/ZzHF9fwwec6c6m2AiyYGS/37343a8bb4858cdf296f5a3c450567f3/PesoCubado.png)
diff --git a/docs/tracks/pt/customer-identification.md b/docs/tracks/pt/customer-identification.md
index 43db8e9de..1f6adf697 100644
--- a/docs/tracks/pt/customer-identification.md
+++ b/docs/tracks/pt/customer-identification.md
@@ -27,7 +27,7 @@ Você pode [configurar quais métodos de identificação deseja habilitar](https
 
 No exemplo da imagem abaixo, estão habilitados Email e CPF.
 
-![31. VTEX Sales App - Product Overview - 2 - PT](//images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/8923621c44984ce4d58ff7a9ac97a77f/identify-customer-pt.PNG)
+![31. VTEX Sales App - Product Overview - 2 - PT](https://images.ctfassets.net/alneenqid6w5/2YKc9S2FehS7eA2zTskL33/8923621c44984ce4d58ff7a9ac97a77f/identify-customer-pt.PNG)
 
 Basta inserir um desses dados no campo e clicar em `Confirmar`.
 
diff --git a/docs/tracks/pt/customizing-styles.md b/docs/tracks/pt/customizing-styles.md
index 33698af4b..9910c9bf4 100644
--- a/docs/tracks/pt/customizing-styles.md
+++ b/docs/tracks/pt/customizing-styles.md
@@ -48,7 +48,7 @@ Vamos fazer algumas alterações no nosso arquivo `style.json`. Podemos mudar um
 
 Agora, vamos ver os resultados "linkando" nossa app:
 
-![style-json](//images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
+![style-json](https://images.ctfassets.net/alneenqid6w5/1S0DU3mL8MxRVleCmUGGol/3594be77ecae98c6c223e04191f95def/style-json.svg)
 
 Sucesso! Agora você sabe como personalizar os estilos da sua loja.
 
@@ -98,4 +98,4 @@ Vamos escrever um pouco de CSS, para acrescentar uma linha vermelha sólida:
 ```
 Nosso novo menu de categoria terá agora uma linha vermelha sólida ao longo da parte inferior do nosso menu.
 
-![red-line](//images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
+![red-line](https://images.ctfassets.net/alneenqid6w5/2zVZNpUFepCptn5Zuo3YNa/1d939c7f78544c6b716bfc57db774b79/red-line.svg)
diff --git a/docs/tracks/pt/customizing-templates.md b/docs/tracks/pt/customizing-templates.md
index 22e76abe7..b1407ceaa 100644
--- a/docs/tracks/pt/customizing-templates.md
+++ b/docs/tracks/pt/customizing-templates.md
@@ -119,6 +119,6 @@ Para adicionar um componente a essa página, basta declarar um novo bloco de pra
 
 Se salvar isso em `store/blocks.json` e rodar `vtex link` em sua loja, você deverá ver uma nova prateleira renderizada ao visitar a home page.
 
-![shelf](//images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
+![shelf](https://images.ctfassets.net/alneenqid6w5/6Hw3fRA4E8xC0Q4bNdO6gV/8b6742fd0c57a341db0cc0baea4cfb06/shelf.svg)
 
 Você pode personalizar os blocos declarados pela aplicativo `store-theme` livremente e também declarar novos. Por enquanto, você pode encontrar a documentação para cada componente em seus [repositórios do GitHub](https://github.com/vtex-apps?q=store-components). Lá você encontra as propriedades disponíveis para cada componente.
diff --git a/docs/tracks/pt/dafiti-marketplace.md b/docs/tracks/pt/dafiti-marketplace.md
index 6807121e1..c8ef982a6 100644
--- a/docs/tracks/pt/dafiti-marketplace.md
+++ b/docs/tracks/pt/dafiti-marketplace.md
@@ -16,7 +16,7 @@ trackSlugPT: configurar-integracao-da-dafiti
 
 A Dafiti é o maior marketplace de moda e _lifestyle_ da América Latina. Fundada em 2011, já são mais de 10 anos influenciando o varejo online. Em 2020, foram estimados mais de 7,7 milhões de clientes ativos, e o faturamento para o ano ultrapassou 3 bilhões de reais.
 
-![Dafiti Logo](//images.ctfassets.net/alneenqid6w5/47bytXO1eU2uoKkomqWQaS/c06477ee90fb10a4a6ad1168c5bf9c7a/Dafiti_new_logo.png)
+![Dafiti Logo](https://images.ctfassets.net/alneenqid6w5/47bytXO1eU2uoKkomqWQaS/c06477ee90fb10a4a6ad1168c5bf9c7a/Dafiti_new_logo.png)
 
 Na Dafiti você pode vender produtos de diversas categorias, tais como roupas, esporte, beleza, decoração, dentre outros. O marketplace concentra cerca de 6 mil marcas e um portifólio de mais de 400 mil produtos.
 
diff --git a/docs/tracks/pt/dashboard.md b/docs/tracks/pt/dashboard.md
index cea29ff01..a8372c160 100644
--- a/docs/tracks/pt/dashboard.md
+++ b/docs/tracks/pt/dashboard.md
@@ -16,7 +16,7 @@ trackSlugPT: conversational-commerce
 
 Na página Dashboard, os proprietários de lojas VTEX têm acesso às métricas do canal de [Conversational Commerce VTEX](https://help.vtex.com/pt/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/1NwwADrU70v3roPUV7dWxI#). Neste painel, você pode visualizar o desempenho das vendas e os indicadores das sessões, além de filtrá-los pelo período e exportá-los para um arquivo CSV.
 
-![Conversational Commerce Analytics Panel](//images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/0317999b94d984da418d5126851085d1/Conversational_Commerce_Analytics_Panel_PT.png)
+![Conversational Commerce Analytics Panel](https://images.ctfassets.net/alneenqid6w5/1kQwpA3cAfiW4OdlGOYjOf/0317999b94d984da418d5126851085d1/Conversational_Commerce_Analytics_Panel_PT.png)
 
 ## Dados
 
diff --git a/docs/tracks/pt/delivery.md b/docs/tracks/pt/delivery.md
index 20fd31821..6e0e6987f 100644
--- a/docs/tracks/pt/delivery.md
+++ b/docs/tracks/pt/delivery.md
@@ -18,7 +18,7 @@ Ao clicar em `Ir para a entrega`, o VTEX Sales App mostra os endereços disponí
 
 Alternativamente, o vendedor pode inserir um outro CEP no campo __Informe o CEP para ver as opções de entrega__ e, em seguida, clicar em `Confirmar`.
 
-![instore-entrega-1](//images.ctfassets.net/alneenqid6w5/6gysul2FyDXGWJRUC0nwJT/2b1d1f617824ddbac290d8ee0c98ead3/entrega-1.png)
+![instore-entrega-1](https://images.ctfassets.net/alneenqid6w5/6gysul2FyDXGWJRUC0nwJT/2b1d1f617824ddbac290d8ee0c98ead3/entrega-1.png)
 
 A tela seguinte permite definir escolhas de entrega. Como o VTEX Sales App lida com o estoque de múltiplas lojas, há diversas possibilidades de organização da entrega, dependendo de onde se encontram os produtos do carrinho.
 
@@ -29,19 +29,19 @@ A tela seguinte permite definir escolhas de entrega. Como o VTEX Sales App lida
 - Retirar em uma loja física.
 - Personalizar por item.
 
-![instore-definir-escolhas-de-entrega](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/697cb506db0466fd5f137629ec57458a/entrega-2.png)
+![instore-definir-escolhas-de-entrega](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/697cb506db0466fd5f137629ec57458a/entrega-2.png)
 
 ### Pontos de retirada
 
 Para opções de retirada em loja (pickup point), o sistema seleciona as lojas que têm os itens em estoque e mostra a loja mais próxima ao CEP do cliente, como sugestão. Se o vendedor quiser trocar a loja onde o cliente fará a coleta, basta clicar no botão `Alterar ponto de retirada`.
 
-![31. VTEX Sales App - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/667f6c141be1ad04b2588fc6e28526be/entrega-retirada.png)
+![31. VTEX Sales App - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/667f6c141be1ad04b2588fc6e28526be/entrega-retirada.png)
 
 Ao clicar em `Alterar ponto de retirada`, o vendedor primeiro visualiza o ponto de retirada sugerido pelo sistema. Para ver os demais pontos de retirada disponíveis, é necessário clicar em `Ver todos os pontos de retirada`.
 
-![31. VTEX Sales App - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
+![31. VTEX Sales App - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._VTEX Sales App_-_Product_Overview_-_12.png)
 
 O VTEX Sales App mostrará, então, a lista de pontos de retirada, ordenada por menor distância do CEP do cliente. Também é possível escolher o ponto de retirada a partir da visualização no mapa, clicando na aba __Mapa__.
 
-![31. VTEX Sales App - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
+![31. VTEX Sales App - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._VTEX Sales App_-_Product_Overview_-_13.png)
 
diff --git a/docs/tracks/pt/detaching-skus-by-specification.md b/docs/tracks/pt/detaching-skus-by-specification.md
index 1c2bd4347..1803808cd 100644
--- a/docs/tracks/pt/detaching-skus-by-specification.md
+++ b/docs/tracks/pt/detaching-skus-by-specification.md
@@ -24,7 +24,7 @@ Essa ferramenta é indicada, principalmente, para lojas de vestuários, pois é
 
 A seguir, confira um exemplo de separação de SKUs por cor. Na imagem abaixo, a sandália em destaque apresenta duas cores diferentes no resultado da pesquisa:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.</p></div>
diff --git a/docs/tracks/pt/enabling-2-factor-authentication-login.md b/docs/tracks/pt/enabling-2-factor-authentication-login.md
index 369f07051..9959e1d70 100644
--- a/docs/tracks/pt/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/pt/enabling-2-factor-authentication-login.md
@@ -86,10 +86,10 @@ Para modificar as configurações de verificação em duas etapas:
 
 1. Acesse suas configurações de usuário, clicando no círculo com suas iniciais no canto superior-direito do Admin.
 
-  ![2FA - User Initials - PT](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
+  ![2FA - User Initials - PT](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
 
 2. Clique em **Verificação em 2 passos** para visualizar suas configurações.
 
-  ![2FA - My User - PT](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
+  ![2FA - My User - PT](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
 
 3. Você poderá então alterar suas configurações seguindo passos similares aos apresentados nas seções acima para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) e [aplicativo](#habilitar-o-2fa-por-aplicativo). 
diff --git a/docs/tracks/pt/enabling-a-sales-rep-code.md b/docs/tracks/pt/enabling-a-sales-rep-code.md
index aa36cb730..bf29478c7 100644
--- a/docs/tracks/pt/enabling-a-sales-rep-code.md
+++ b/docs/tracks/pt/enabling-a-sales-rep-code.md
@@ -42,7 +42,7 @@ Depois de seguir essas recomendações, acesse o módulo __Configurações da lo
 
 Do lado direito da tela, você verá o arquivo `checkout-instore-custom.js`. 
 
-![vendorcode](//images.ctfassets.net/alneenqid6w5/ZvQVCvlacD2AYf9eHKcxl/53885297fc0e0882178a6230815b2b6e/vendorcode.PNG)
+![vendorcode](https://images.ctfassets.net/alneenqid6w5/ZvQVCvlacD2AYf9eHKcxl/53885297fc0e0882178a6230815b2b6e/vendorcode.PNG)
 
 Acesse-o e adicione o seguinte trecho ao objeto `window.INSTORE_CONFIG`:
 
@@ -64,7 +64,7 @@ Cada responsável deve preencher as propriedades do objeto `window.INSTORE_CONFI
 
 Por fim, finalize clicando no botão azul __Salvar__ localizado no topo da página.
 
-![vendorcode2](//images.ctfassets.net/alneenqid6w5/59lZVji41rXxNjVXhwC6Ae/76513fc455650813e5740e68882421dd/vendorcode2.PNG) 
+![vendorcode2](https://images.ctfassets.net/alneenqid6w5/59lZVji41rXxNjVXhwC6Ae/76513fc455650813e5740e68882421dd/vendorcode2.PNG) 
 
 ## Entendendo as propriedades
 
diff --git a/docs/tracks/pt/enabling-cart-transfer-between-devices.md b/docs/tracks/pt/enabling-cart-transfer-between-devices.md
index 7cdd8a408..17d86be15 100644
--- a/docs/tracks/pt/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/pt/enabling-cart-transfer-between-devices.md
@@ -34,11 +34,11 @@ window.INSTORE_CONFIG = {
 
 Após realizar essa alteração, abra o menu do inStore e atualize os dados, clicando no botão __Restaurar dados__. Feito isso, aparecerão duas bolinhas ao fim da página de identificação do inStore:
 
-![24. Enable cart transfer between devices - 1](//images.ctfassets.net/alneenqid6w5/4HXR0QuEd2wa6GiRFL9gsm/4515dcc3ca2bb5a7d6d2304886724704/24._Enable_cart_transfer_between_devices_-_1.png)
+![24. Enable cart transfer between devices - 1](https://images.ctfassets.net/alneenqid6w5/4HXR0QuEd2wa6GiRFL9gsm/4515dcc3ca2bb5a7d6d2304886724704/24._Enable_cart_transfer_between_devices_-_1.png)
 
 Ao arrastar a tela para a direita, você verá a tela para __Capturar Carrinho__, conforme mostra a imagem abaixo.
 
-![24. Enable cart transfer between devices - 2](//images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
+![24. Enable cart transfer between devices - 2](https://images.ctfassets.net/alneenqid6w5/2BdYpDo4UL0GETBeTM72u3/a017156e7e2beac121abb5d2cd0b1ba0/24._Enable_cart_transfer_between_devices_-_2.png)
 
 Nessa tela, é possível capturar um carrinho por um desses três métodos:
 - Código do carrinho
@@ -49,4 +49,4 @@ Nessa tela, é possível capturar um carrinho por um desses três métodos:
 
 Para o vendedor compartilhar um carrinho, ele pode gerar um código numérico ou um QR Code. Para isso, estando na tela do carrinho, basta clicar no botão __Transferir__. Veja um exemplo na imagem abaixo.
 
-![24. Enable cart transfer between devices - 3](//images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
+![24. Enable cart transfer between devices - 3](https://images.ctfassets.net/alneenqid6w5/1rk5DOgk5a0XAWwWqLCO4t/dcc5225d218120953155432b30f43c21/24._Enable_cart_transfer_between_devices_-_3.png)
diff --git a/docs/tracks/pt/enabling-order-filter-by-salesperson.md b/docs/tracks/pt/enabling-order-filter-by-salesperson.md
index 49a57d796..a393f8983 100644
--- a/docs/tracks/pt/enabling-order-filter-by-salesperson.md
+++ b/docs/tracks/pt/enabling-order-filter-by-salesperson.md
@@ -20,7 +20,7 @@ A mudança das configurações de filtro por vendedor, explicada neste artigo, e
 
 No inStore, é possível ver a listagem de todos os pedidos finalizados em uma loja:
 
-![26. Enable order filter by salesperson - 1](//images.ctfassets.net/alneenqid6w5/4pI7zxSaInuVvjIqWUK3Uv/ef9c2555f36f9bed41970a85727c2059/26._Enable_order_filter_by_salesperson_-_1.png)
+![26. Enable order filter by salesperson - 1](https://images.ctfassets.net/alneenqid6w5/4pI7zxSaInuVvjIqWUK3Uv/ef9c2555f36f9bed41970a85727c2059/26._Enable_order_filter_by_salesperson_-_1.png)
 
 Porém, algumas vezes faz sentido que um vendedor veja apenas os pedidos finalizados por ele. Para habilitar essa opção é necessário editar o arquivo `checkout-instore-custom.js`.
 
@@ -43,4 +43,4 @@ Não remova nenhuma das outras propriedades presentes no objeto <code>window.INS
 
 Após recarregar os dados do inStore, clicando no botão __Restaurar dados__, o vendedor verá apenas os pedidos fechados por ele, como no seguinte exemplo:
 
-![26. Enable order filter by salesperson - 2](//images.ctfassets.net/alneenqid6w5/4vi7YeUa3706ls0bQ2p0eE/343cfe8b50ae2956522bc5c79de8ec58/26._Enable_order_filter_by_salesperson_-_2.png)
+![26. Enable order filter by salesperson - 2](https://images.ctfassets.net/alneenqid6w5/4vi7YeUa3706ls0bQ2p0eE/343cfe8b50ae2956522bc5c79de8ec58/26._Enable_order_filter_by_salesperson_-_2.png)
diff --git a/docs/tracks/pt/enabling-product-recommendations.md b/docs/tracks/pt/enabling-product-recommendations.md
index 9a604098b..bea6eeacf 100644
--- a/docs/tracks/pt/enabling-product-recommendations.md
+++ b/docs/tracks/pt/enabling-product-recommendations.md
@@ -22,7 +22,7 @@ Por padrão, o inStore mostra uma lista de produtos sugeridos ao vendedor em dua
 - No carrinho
 - Na página de produto
 
-![25. Enable product recommendations - 1](//images.ctfassets.net/alneenqid6w5/4j8YWYRuwENptnipUat6Wj/44401abb84a8aba3c3c89282afafc511/25._Enable_product_recommendations_-_1.png)
+![25. Enable product recommendations - 1](https://images.ctfassets.net/alneenqid6w5/4j8YWYRuwENptnipUat6Wj/44401abb84a8aba3c3c89282afafc511/25._Enable_product_recommendations_-_1.png)
 
 Caso deseje ocultar essas recomendações, é necessário editar os arquivos `checkout-instore-custom.css` e `checkout-instore-custom.js`.
 
@@ -30,7 +30,7 @@ Caso deseje ocultar essas recomendações, é necessário editar os arquivos `ch
 
 Assim como o arquivo JavaScript de customização do inStore, o `checkout-instore-custom.css` deve ser acessado pelo painel administrativo da VTEX (conforme explicado no artigo [inStore Customizations](https://help.tex.com/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/4mwdBrFsmE2EPE0FzgX28b)).
 
-![25. Enable product recommendations - 2](//images.ctfassets.net/alneenqid6w5/4jRvpkXNEW0k5kwXXxkRnG/fe7e30eef89ad19ad4d4bfc0ca9579a5/25._Enable_product_recommendations_-_2.png)
+![25. Enable product recommendations - 2](https://images.ctfassets.net/alneenqid6w5/4jRvpkXNEW0k5kwXXxkRnG/fe7e30eef89ad19ad4d4bfc0ca9579a5/25._Enable_product_recommendations_-_2.png)
 
 No arquivo `checkout-instore-custom.css`, inclua a seguinte regra de CSS:
 
diff --git a/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md b/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
index 9a8b66da2..9ceb9ef0d 100644
--- a/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
+++ b/docs/tracks/pt/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
@@ -16,11 +16,11 @@ trackSlugPT: suiteshare
 
 Você já criou o [chat](https://help.vtex.com/pt/tutorial/chat--2HdGrTcSYL1ZIXy7QTWE5), criou os [links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB), a [captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) está funcionando perfeitamente, agora só precisamos entender de onde vieram esses clientes. Para fazer isso é super tranquilo, acesse o seu painel admin e clique em “_**Analisar**_” 
 
-![Entenda como os clientes chegam até o seu WhatsApp 1](//images.ctfassets.net/alneenqid6w5/5wsUGreWmGzlbgMNYFiKmg/996bf462e45d3274236d3d70246dca78/Screenshot_2022-08-25_at_15-24-42_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 1](https://images.ctfassets.net/alneenqid6w5/5wsUGreWmGzlbgMNYFiKmg/996bf462e45d3274236d3d70246dca78/Screenshot_2022-08-25_at_15-24-42_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Acessando o painel, você terá as seguintes opções: 
 
-![Entenda como os clientes chegam até o seu WhatsApp 2](//images.ctfassets.net/alneenqid6w5/rERjlfyQ0Ck7UZTukK1nX/54d8ca1cdbb8216136dd9f19af636144/Screenshot_2022-08-25_at_15-25-53_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 2](https://images.ctfassets.net/alneenqid6w5/rERjlfyQ0Ck7UZTukK1nX/54d8ca1cdbb8216136dd9f19af636144/Screenshot_2022-08-25_at_15-25-53_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 **1 Geral:** Uma análise geral de todos os links criados na sua conta
 
@@ -34,27 +34,27 @@ Acessando o painel, você terá as seguintes opções: 
 
 No analisar você consegue entender o número total de cliques no seu link, o relatório do mês, semana e diário. 
 
-![Entenda como os clientes chegam até o seu WhatsApp 3](//images.ctfassets.net/alneenqid6w5/1ks9WLyhVQ3X0jNrvOSVeT/9f0f3450ebe47a4fbe777d5052b52a5a/Screenshot_2022-08-25_at_15-32-26_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 3](https://images.ctfassets.net/alneenqid6w5/1ks9WLyhVQ3X0jNrvOSVeT/9f0f3450ebe47a4fbe777d5052b52a5a/Screenshot_2022-08-25_at_15-32-26_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Além disso é possível filtrar períodos específicos 
 
-![Entenda como os clientes chegam até o seu WhatsApp 4](//images.ctfassets.net/alneenqid6w5/6SLlRKkWTRV7KdKYWVl8zs/3fb77230a60ed93026c8122a1be89711/Screenshot_2022-08-25_at_15-39-59_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 4](https://images.ctfassets.net/alneenqid6w5/6SLlRKkWTRV7KdKYWVl8zs/3fb77230a60ed93026c8122a1be89711/Screenshot_2022-08-25_at_15-39-59_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Além disso é possível filtrar períodos específicos
 
-![Entenda como os clientes chegam até o seu WhatsApp 5](//images.ctfassets.net/alneenqid6w5/6EmQOv4uPAdhAxT2Mo8Nur/bb80d00d59f31098c0a90c49e94103b7/Screenshot_2022-08-25_at_15-42-13_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 5](https://images.ctfassets.net/alneenqid6w5/6EmQOv4uPAdhAxT2Mo8Nur/bb80d00d59f31098c0a90c49e94103b7/Screenshot_2022-08-25_at_15-42-13_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Analisar também a região de onde o seu cliente está vindo
 
-![Entenda como os clientes chegam até o seu WhatsApp 6](//images.ctfassets.net/alneenqid6w5/5iYtWzO8XFn2oHCCe1GqZR/271dec5624608a53f1adff8e31347321/Screenshot_2022-08-25_at_15-43-10_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 6](https://images.ctfassets.net/alneenqid6w5/5iYtWzO8XFn2oHCCe1GqZR/271dec5624608a53f1adff8e31347321/Screenshot_2022-08-25_at_15-43-10_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 E a referência de domínio, de onde originou esse acesso 
 
-![Entenda como os clientes chegam até o seu WhatsApp 7](//images.ctfassets.net/alneenqid6w5/2mOHLwD91XCdPVFLplkdTb/01e92096688aa4cad6a2f2552c02bb2a/Screenshot_2022-08-25_at_15-47-17_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 7](https://images.ctfassets.net/alneenqid6w5/2mOHLwD91XCdPVFLplkdTb/01e92096688aa4cad6a2f2552c02bb2a/Screenshot_2022-08-25_at_15-47-17_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Além de uma visão geral sobre dispositivos e navegadores
 
-![Entenda como os clientes chegam até o seu WhatsApp 8](//images.ctfassets.net/alneenqid6w5/7Ak1oh5FTardmnq18olO0U/3e2ac6b3487ee8a15c5ee369d999bf50/Screenshot_2022-08-25_at_15-48-00_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
+![Entenda como os clientes chegam até o seu WhatsApp 8](https://images.ctfassets.net/alneenqid6w5/7Ak1oh5FTardmnq18olO0U/3e2ac6b3487ee8a15c5ee369d999bf50/Screenshot_2022-08-25_at_15-48-00_Entenda_como_os_clientes_chegam_at___o_seu_WhatsApp.png)
 
 Gostou? 
 
diff --git a/docs/tracks/pt/explained-search.md b/docs/tracks/pt/explained-search.md
index a0e68f773..6f0a388ac 100644
--- a/docs/tracks/pt/explained-search.md
+++ b/docs/tracks/pt/explained-search.md
@@ -26,5 +26,5 @@ Para utilizá-la, siga o passo a passo abaixo:
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
 2. Em **Intelligent Search**, clique em **Explicação da busca**. 
 
-![Explicação da Busca](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
+![Explicação da Busca](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
 
diff --git a/docs/tracks/pt/extensions-hub-1.md b/docs/tracks/pt/extensions-hub-1.md
index b70c9243c..804f3e9a4 100644
--- a/docs/tracks/pt/extensions-hub-1.md
+++ b/docs/tracks/pt/extensions-hub-1.md
@@ -18,6 +18,6 @@ O Hub de Extensões é uma seção do Admin que agrupa todas as informações e
 
 Para acessar o Hub de Extensões, vá ao painel lateral esquerdo do Admin, clique no ícone **Extensões** e ele estará visível na parte superior do menu.
 
-![Extensions Hub painel](//images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
+![Extensions Hub painel](https://images.ctfassets.net/alneenqid6w5/6agEF92xgLL9slUgOgnI8j/8e71018376cc86219f4aa0ddd0d01ffa/Extensions_Hub_panel_PT.png)
 
 No Hub de Extensões podem ser encontradas três páginas: **Loja de aplicativos**, **Parceiros** e **Gerenciamento de aplicativos**. A documentação sobre cada um deles pode ser vista nos artigos logo em seguida.
diff --git a/docs/tracks/pt/extensions-hub-app-store.md b/docs/tracks/pt/extensions-hub-app-store.md
index f0ea6a195..7cb1ecbff 100644
--- a/docs/tracks/pt/extensions-hub-app-store.md
+++ b/docs/tracks/pt/extensions-hub-app-store.md
@@ -18,7 +18,7 @@ A App Store é a página do Admin onde você pode buscar, visualizar e obter app
 
 ## Página inicial
 
-![Extensions Hub App Store página inicial](//images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/ba56f15ab8cc4041dd0d8cf3d10afa1d/Extensions_Hub_App_Store_home_page_PT.png)
+![Extensions Hub App Store página inicial](https://images.ctfassets.net/alneenqid6w5/3wzHr69aCqLuPG2cuT2e6y/ba56f15ab8cc4041dd0d8cf3d10afa1d/Extensions_Hub_App_Store_home_page_PT.png)
 
 Ao entrar na loja, você estará na página inicial. Nesta página estão disponíveis as seguintes opções:
 
@@ -28,13 +28,13 @@ Ao entrar na loja, você estará na página inicial. Nesta página estão dispon
 
 ## Busca
 
-![Extensions Hub App Store busca](//images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/1cca7f3ff65a4568f6327cae2e4e6de0/Extensions_Hub_App_Store_search_PT.png)
+![Extensions Hub App Store busca](https://images.ctfassets.net/alneenqid6w5/1VuHQqhPZ9G88K3ZOQqny8/1cca7f3ff65a4568f6327cae2e4e6de0/Extensions_Hub_App_Store_search_PT.png)
 
 A busca permite que você pesquise por apps através do nome. Ao digitar na caixa de texto da busca e pressionar a tecla `Enter`, você será direcionado para a página de resultados da busca. Os resultados serão os apps cujos nomes correspondam ao texto inserido na busca. Os apps aparecem no formato de cartões quadrados, onde é possível ver o nome, o subtítulo e o custo do app. Ao clicar em um app, você será levado para a [página do app](#pagina-do-app).
 
 ## Página do app
 
-![Extensions Hub App Store app page](//images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/c0e06d0a250b05fa32b97b4161fae294/Extensions_Hub_App_Store_app_page_PT.png)
+![Extensions Hub App Store app page](https://images.ctfassets.net/alneenqid6w5/4VdhF4EhRvcktxnlqK0nt/c0e06d0a250b05fa32b97b4161fae294/Extensions_Hub_App_Store_app_page_PT.png)
 
 Ao clicar em um app na página inicial ou na busca, você será direcionado para a página do respectivo app. Nesta página você encontrará todas as informações sobre o app, incluindo os custos, e a opção para baixá-lo.
 
diff --git a/docs/tracks/pt/filter-orders-by-vendor.md b/docs/tracks/pt/filter-orders-by-vendor.md
index ed6389331..f171a4929 100644
--- a/docs/tracks/pt/filter-orders-by-vendor.md
+++ b/docs/tracks/pt/filter-orders-by-vendor.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 No inStore é possível ver a listagem de todos os pedidos finalizados em uma loja:
 
-![pedidos finalizados](//images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
+![pedidos finalizados](https://images.ctfassets.net/alneenqid6w5/2bBNpiFuswIAqsc2EGuAMe/ee70cebba8bef3fe609f31dd5a7d905c/pedidos_finalizados.png)
 
 Porém, algumas vezes faz sentido que um vendedor veja apenas os pedidos finalizados por ele. Para habilitar essa opção é necessário editar o arquivo `checkout-instore-custom.js` presente no admin do Portal. Por se tratar de um JavaScript presente em diversos fluxos de uso da aplicação, é importante que você tenha conhecimentos de programação antes de alterá-lo, para evitar a quebra de outras funcionalidades.
 
@@ -37,4 +37,4 @@ __IMPORTANTE__: Não remova nenhuma das outras propriedades presentes no objeto
 
 Após recarregar o inStore o resultado deve ser o seguinte:
 
-![pedidos finalizados filtrados por vendedor](//images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
+![pedidos finalizados filtrados por vendedor](https://images.ctfassets.net/alneenqid6w5/HhNBrdQZA2YAWQa8aUm6U/4f71b847a38caabe9b708bc070fda396/pedidos_finalizados_filtrados_por_vendedor.png)
diff --git a/docs/tracks/pt/frontend-implementation.md b/docs/tracks/pt/frontend-implementation.md
index 8a57f1d79..7731f240c 100644
--- a/docs/tracks/pt/frontend-implementation.md
+++ b/docs/tracks/pt/frontend-implementation.md
@@ -93,7 +93,7 @@ Ao falar de implementação de frontend, é preciso lembrar que o [VTEX IO](http
 
 Isso significa que ao trabalhar com VTEX IO, a pessoa desenvolve seu código localmente. Porém, quando se trata de implantar e executar a loja, o VTEX IO gerencia a infraestrutura, CI/CD e segurança, além de cuidar do processo de implantação. A imagem abaixo apresenta como estes conceitos se relacionam entre si:
 
-![Arquitetura de desenvolvimento frontend](//images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/a552a6ae6c50ef92304ff8f11e651cbf/frontend_image2_PT.png)
+![Arquitetura de desenvolvimento frontend](https://images.ctfassets.net/alneenqid6w5/70awnhEGvAlpk5NBrGJJJ6/a552a6ae6c50ef92304ff8f11e651cbf/frontend_image2_PT.png)
 
 ### Principais funcionalidades do Store Framework
 
@@ -229,7 +229,7 @@ O time de desenvolvimento deve iniciar um novo projeto com a FastStore através
 - *Product Details Page* (PDP)
 - *Minicart*
 
-![FastStore template](//images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
+![FastStore template](https://images.ctfassets.net/alneenqid6w5/gRMxctAER60dhr8UEIEh2/56b79e81aae806bf7ab17d6088267f90/frontend_image4_ALL.png)
 
 #### Requisitos para um MVP da FastStore
 
@@ -282,7 +282,7 @@ O time de desenvolvimento deve iniciar um novo projeto com o Store Framework clo
 - *Product Listing Page* (PLP)
 - *Product Details Page* (PDP)
 
-![Store Framework template](//images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
+![Store Framework template](https://images.ctfassets.net/alneenqid6w5/5TpA31coQ1lu5ZoMkj8boS/d1f1bfb2f0e46ff3755375e00658a466/frontend_image5_ALL.png)
 
 #### Requisitos para um MVP do Store Framework
 
diff --git a/docs/tracks/pt/frontend.md b/docs/tracks/pt/frontend.md
index baad22859..5f1bb936f 100644
--- a/docs/tracks/pt/frontend.md
+++ b/docs/tracks/pt/frontend.md
@@ -26,7 +26,7 @@ A maneira como essa extensão de funcionalidades ocorre é através de apps VTEX
 
 O Store Framework é uma solução para construção de frente de loja que se alavanca do VTEX IO. Através dela podemos contar com a interface amigável do [Site Editor](https://help.vtex.com/pt/tutorial/site-editor-overview--299Dbeb9mFczUTyNQ9xPe1) e tornar o gerenciamento de conteúdo da loja mais simples.
 
-![vtex io](//images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/51d67a21e5ab6bf0517fee83f9455337/image3.png)
+![vtex io](https://images.ctfassets.net/alneenqid6w5/2ihbniXa1S2L7pLOPP0E3o/51d67a21e5ab6bf0517fee83f9455337/image3.png)
 
 Lojas criadas com o Store Framework também contam com as features de: 
 - **[Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)**: ferramenta de busca, que corrige erros ortográficos e possibilita regras condicionais para exibição do resultado de busca.
diff --git a/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md b/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
index fcd6069ce..96b2f6b5b 100644
--- a/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
+++ b/docs/tracks/pt/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
@@ -22,7 +22,7 @@ Primeiro, você já deve ter criado os links, caso não tenha criado clique aqui
 
 Agora é só criar seus anúncios no Facebook, Instagram e outras redes que utilizar, e inserir seu link no campo de texto. Seu cliente irá diretamente para a conversa no WhatsApp com a sua empresa.
 
-![Levar os visitantes do meu site e redes sociais para o WhatsApp 1](//images.ctfassets.net/alneenqid6w5/44eCSKO1yJcy816ZA4wKlR/2f95d30387906b9d67ee953c6d484e31/Screenshot_2022-08-25_at_15-09-21_Levar_os_visitantes_do_meu_site_e_redes_sociais_para_o_WhatsApp.png)
+![Levar os visitantes do meu site e redes sociais para o WhatsApp 1](https://images.ctfassets.net/alneenqid6w5/44eCSKO1yJcy816ZA4wKlR/2f95d30387906b9d67ee953c6d484e31/Screenshot_2022-08-25_at_15-09-21_Levar_os_visitantes_do_meu_site_e_redes_sociais_para_o_WhatsApp.png)
 
 Além de levar o seu cliente diretamente para o WhatsApp de forma rápida e fácil, você ainda pode capturar informações diretamente para o seu CRM, analisar quais redes estão lhe trazendo mais clientes, além do Remarketing no seu link. 
 
diff --git a/docs/tracks/pt/getting-started-with-logistics.md b/docs/tracks/pt/getting-started-with-logistics.md
index 23745b7ab..f7137509d 100644
--- a/docs/tracks/pt/getting-started-with-logistics.md
+++ b/docs/tracks/pt/getting-started-with-logistics.md
@@ -56,7 +56,7 @@ De forma resumida, o módulo **Estoque & entrega** divide-se nas seguintes seç
 * **Configurações**: configurações gerais de logística, como habilitar a notificação de estoque crítico.
 * **[Pontos de retirada](https://help.vtex.com/pt/tutorial/como-funcionam-pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R)**: seção para cadastro de pontos físicos onde os clientes podem retirar seus pedidos.
 
-    ![estoque e entregaPT](//images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/4dff7a2616eb80d8ec89344ec2d2363c/estoque_e_entregaPT.png)
+    ![estoque e entregaPT](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/4dff7a2616eb80d8ec89344ec2d2363c/estoque_e_entregaPT.png)
 
 <div class = "alert alert-info">
   Clientes que utilizam o <a href="https://vtex.com/br-pt/log/"><b>VTEX Shipping Network</a></b> acessam a funcionalidade pelo módulo <b>Estoque & Entrega</b>.
diff --git a/docs/tracks/pt/go-live-process.md b/docs/tracks/pt/go-live-process.md
index c9f8884fa..369c838c6 100644
--- a/docs/tracks/pt/go-live-process.md
+++ b/docs/tracks/pt/go-live-process.md
@@ -18,7 +18,7 @@ Se você já [configurou o funcionamento da sua loja](https://help.vtex.com/pt/t
 
 Neste tutorial você encontra o passo a passo detalhado de como realizar o go-live da sua loja.
 
-![Go-live](//images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/032594f36e1fe4fda13252502060b753/go_live_pt.jpg)
+![Go-live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/032594f36e1fe4fda13252502060b753/go_live_pt.jpg)
 
 <div class = "alert alert-info">
 Note que uma loja em produção é diferente de uma conta em produção. De modo geral, pode-se dizer que para ter uma loja em produção é necessário colocar a conta em produção e realizar o apontamento de DNS. Confira abaixo todos os passos envolvidos nesse processo.
@@ -28,7 +28,7 @@ Note que uma loja em produção é diferente de uma conta em produção. De modo
 
 Antes de realizar o go-live da sua loja, é essencial garantir que você tenha realizado todas as configurações necessárias para o bom funcionamento da sua loja.
 
-Copie esta [Checklist de configuração de loja](//assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f504033fb6e8bf38b639547c5fd8790a/Checklist_de_configura__o_de_loja.xlsx) e verifique, para cada item, se realizou as configurações de acordo com o funcionamento desejado da loja.
+Copie esta [Checklist de configuração de loja](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f504033fb6e8bf38b639547c5fd8790a/Checklist_de_configura__o_de_loja.xlsx) e verifique, para cada item, se realizou as configurações de acordo com o funcionamento desejado da loja.
 
 <div class="alert alert-warning">
 A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. Cabe à sua equipe definir quais funcionalidades implementar na sua loja e como deverão ser configuradas de maneira a produzir a experiência de loja desejada. Isso significa que a lista pode não contemplar todas as funcionalidades usadas pela sua loja. Ainda assim, é importante verificar todos os aspectos do funcionamento da sua loja, mesmo que não estejam na lista sugerida.
diff --git a/docs/tracks/pt/google-pay.md b/docs/tracks/pt/google-pay.md
index f496b1e09..a83cce218 100644
--- a/docs/tracks/pt/google-pay.md
+++ b/docs/tracks/pt/google-pay.md
@@ -35,7 +35,7 @@ Para ativar o Google Pay, siga o passo a passo abaixo.
 
 Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como nova forma de pagamento. É possível que demore em torno de 10 minutos para que a configuração apareça no Checkout.
 
-![google-pay-checkout-pt](//images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/6ba2af94c811c8cb76d553f68c5578d6/Screenshot_2024-08-01_at_14.21.25.png)
+![google-pay-checkout-pt](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/6ba2af94c811c8cb76d553f68c5578d6/Screenshot_2024-08-01_at_14.21.25.png)
 
 <div class="alert alert-warning">
 <p>Google Pay, neste momento, não vai suportar assinatura.</p>
@@ -58,11 +58,11 @@ Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como n
 
 Para consultar e verificar transações que foram finalizadas com o Google Pay no pagamento, siga os passos descritos no artigo [Ver detalhes da transação](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy). Na barra de busca da página de transações, digite **Google Pay** para filtrar as transações realizadas com este tipo de pagamento.
 
-![Google Pay Transaction_1](//images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/7529f5dce8a104bc97e546cb31a47843/Google_Pay_Transaction1_PT.png)
+![Google Pay Transaction_1](https://images.ctfassets.net/alneenqid6w5/3N6LkrdAmAEfmDDsuLaWz5/7529f5dce8a104bc97e546cb31a47843/Google_Pay_Transaction1_PT.png)
 
 Após acessar a transação desejada, clique em `+ Informações` para verificar a informação **Google Pay** descrita no campo `paymentOrigin`.
 
-![Google Pay Transaction_2](//images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/904607c6df63c9168c35435b9bb5068e/Google_Pay_Transaction2_PT.png)
+![Google Pay Transaction_2](https://images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/904607c6df63c9168c35435b9bb5068e/Google_Pay_Transaction2_PT.png)
 
 <div class="alert alert-warning">
   <p>Também é possível identificar transações realizadas com o Google Pay por meio da página <b>Todos os pedidos</b> no Admin. Você precisa somente selecionar o período desejado de busca, <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">exportar os pedidos</a> em um relatório no formato .csv e localizar a informação Google Pay no campo "payment origin".</p>
diff --git a/docs/tracks/pt/google-shopping-marketplace.md b/docs/tracks/pt/google-shopping-marketplace.md
index 01b7c6a5a..c3192a5b3 100644
--- a/docs/tracks/pt/google-shopping-marketplace.md
+++ b/docs/tracks/pt/google-shopping-marketplace.md
@@ -16,7 +16,7 @@ trackSlugPT: configurar-integracao-com-o-google-shopping
 
 O [Google Shopping](https://shopping.google.com/) é uma plataforma na qual um produto é apresentado em listagens gratuitas classificadas de forma orgânica em pesquisas do Google. Ou seja, é um serviço de comparação e rastreamento de preços, que apresenta seus produtos gratuitamente nos resultados de pesquisa de produtos locais.
 
-![Google Shopping](//images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/d9e89361ff7eec1ad054348e16d15432/logo_Google_shopping.png)
+![Google Shopping](https://images.ctfassets.net/alneenqid6w5/4NP2qyti6VbXkuVSzAg5iH/d9e89361ff7eec1ad054348e16d15432/logo_Google_shopping.png)
 
 Através do Google Shopping, é possível exibir ao consumidor alguns dos atributos do seu produto, tais como imagem, título, preço e nome da sua loja.
 
diff --git a/docs/tracks/pt/hide-product-suggestions-recommendation.md b/docs/tracks/pt/hide-product-suggestions-recommendation.md
index d1d96f6be..e512ad180 100644
--- a/docs/tracks/pt/hide-product-suggestions-recommendation.md
+++ b/docs/tracks/pt/hide-product-suggestions-recommendation.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 Por padrão o inStore inclui uma lista de produtos sugeridos no carrinho e na página de produto.
 
-![inStore recommendation](//images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
+![inStore recommendation](https://images.ctfassets.net/alneenqid6w5/5hN8l2xFTGMU4Gw8YGq0E8/dc9f7e8e4f02db0ae31dd50b08cacd31/inStore_recommendation.png)
 
 Caso deseje ocultar as recomendações, é necessário editar os arquivos `checkout-instore-custom.css` e `checkout-instore-custom.js` presentes no admin do Portal. Por se tratarem de arquivos utilizados em diversos fluxos de uso da aplicação, é importante que você tenha conhecimentos de programação antes de alterá-los, para evitar a quebra de outras funcionalidades.
 
diff --git a/docs/tracks/pt/how-a-split-payment-transaction-works.md b/docs/tracks/pt/how-a-split-payment-transaction-works.md
index 1f0c17dc5..3f79ed1b4 100644
--- a/docs/tracks/pt/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/pt/how-a-split-payment-transaction-works.md
@@ -62,4 +62,4 @@ Esses mesmos R$ 6,50 serão divididos entre marketplace e adquirente. Como o MDR
 
 Confira o diagrama abaixo:
 
-![Split de pagamento](//images.ctfassets.net/alneenqid6w5/3D3Lso54Ho1lXbelILxaZO/ed7b92307403f708227bb85f492d0984/Split.png)
+![Split de pagamento](https://images.ctfassets.net/alneenqid6w5/3D3Lso54Ho1lXbelILxaZO/ed7b92307403f708227bb85f492d0984/Split.png)
diff --git a/docs/tracks/pt/how-clustered-conditions-work.md b/docs/tracks/pt/how-clustered-conditions-work.md
index adc1bd80e..f6746f729 100644
--- a/docs/tracks/pt/how-clustered-conditions-work.md
+++ b/docs/tracks/pt/how-clustered-conditions-work.md
@@ -26,7 +26,7 @@ Desse modo, as regras de prazo e parcelamento serão aplicadas ao(s) consumidor(
 
 Para configurá-las, escolha uma propriedade e, em seguida, selecione os parâmetros para criar um cluster.
 
-![UI - Pagamentos Clusterizados](//images.ctfassets.net/alneenqid6w5/5CqjpJpWRzVAPpTSUAIt8C/91425fe2c9d9d49b66655419b89abf9a/image.png)
+![UI - Pagamentos Clusterizados](https://images.ctfassets.net/alneenqid6w5/5CqjpJpWRzVAPpTSUAIt8C/91425fe2c9d9d49b66655419b89abf9a/image.png)
 
 ## Propriedade
 
@@ -40,7 +40,7 @@ Consequentemente, ele pode criar as propriedades - que podem ser de texto, numé
 
 Sigamos com o exemplo. Na imagem abaixo, a propriedade usada é “Localização Padrão”. Mas outros campos que poderiam ser usados são “E-mail” e “Telefone”, por exemplo.
 
-![Propriedade - PC](//images.ctfassets.net/alneenqid6w5/3acMvJIDlyTfdbIWKcuweT/80c035726574476b316c91b054d3c741/PC1.png)
+![Propriedade - PC](https://images.ctfassets.net/alneenqid6w5/3acMvJIDlyTfdbIWKcuweT/80c035726574476b316c91b054d3c741/PC1.png)
 
 ## Operador 
 
@@ -50,7 +50,7 @@ Na imagem abaixo, a regra será aplicada a todos os clientes que correspondem a
 
 Caso o lojista determinasse a condição “Localização diferente São Paulo” - “diferente” como operador - a regra de pagamento seria aplicada a todos os consumidores da base que não moram em São Paulo.
 
-![Operador](//images.ctfassets.net/alneenqid6w5/4KHYbVD6ubXXFSW01ZuS9q/8ed89399d9f88f2285cbaefc236b4507/PC2.png)
+![Operador](https://images.ctfassets.net/alneenqid6w5/4KHYbVD6ubXXFSW01ZuS9q/8ed89399d9f88f2285cbaefc236b4507/PC2.png)
 
 ## Valor
 Por fim, o último campo é preenchido com um valor relacionado à propriedade escolhida. Sigamos com o exemplo da condição “Localização Igual São Paulo”. 
@@ -61,4 +61,4 @@ Nesse caso, o sistema segmenta os consumidores que correspondam à localização
 
 Caso exista apenas um consumidor que corresponda ao cluster “Localização é São Paulo”, essa regra será aplicadas apenas para ele.
 
-![PC3](//images.ctfassets.net/alneenqid6w5/3oQrXen2cJCOsLpwRAqT74/3600f14168835dcbeabec367e512805e/PC3.png)
+![PC3](https://images.ctfassets.net/alneenqid6w5/3oQrXen2cJCOsLpwRAqT74/3600f14168835dcbeabec367e512805e/PC3.png)
diff --git a/docs/tracks/pt/how-message-center-works.md b/docs/tracks/pt/how-message-center-works.md
index d3b7fd1ce..3e9d5eef6 100644
--- a/docs/tracks/pt/how-message-center-works.md
+++ b/docs/tracks/pt/how-message-center-works.md
@@ -43,7 +43,7 @@ Ao entrar no Message Center e clicar em __Templates__, você encontra a lista de
 
 Vamos entender as informações presentes nesses cards.
 
-![Emails 1 1](//images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
+![Emails 1 1](https://images.ctfassets.net/alneenqid6w5/2cuPA5D3ICgDt8TqlGY9fO/5dd2b918489d7a5fdaa9752f8518ecdd/Emails_1_1.png)
 
 - Nome do template para identificação interna. Este *não* é o assunto do e-mail.
 - Aplicação ou módulo ao qual o template pertence, sinalizado em verde.
@@ -53,7 +53,7 @@ Vamos entender as informações presentes nesses cards.
 
 Para buscar templates, você pode usar filtros por aplicação (módulo) e tipo (mensagem padrão ou personalizada).
 
-![Emails 1 2](//images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
+![Emails 1 2](https://images.ctfassets.net/alneenqid6w5/3tUJ7WpRbHOjUne8tGBaNa/cf9705309d6be38c06fa895ee59268e4/Emails_1_2.png)
 
 ### Remetentes
 
@@ -61,7 +61,7 @@ Aqui, o usuário confere e edita as informações - nome, e-mail e dados do serv
 
 Estas são as informações apresentadas nos cards dos remetentes:
 
-![Emails 1 3](//images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
+![Emails 1 3](https://images.ctfassets.net/alneenqid6w5/2zJnpHTT74AzVysxE5Q6k1/4abac7e5feef61e4495288126f74cc86/Emails_1_3.png)
 
 - Nome do remetente, para identificação interna.
 - Tipo de servidor SMTP, que pode ser da VTEX ou da própria loja.
diff --git a/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md b/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md
index 553f905f3..fc66acb00 100644
--- a/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md
+++ b/docs/tracks/pt/how-to-add-a-custom-text-in-the-printout-of-the-order.md
@@ -33,7 +33,7 @@ Após recarregar o inStore, quando for imprimir um pedido verá esse texto extra
 Exemplo rápido:
 
 Antes de adicionar o texto extra teriamos uma impressão da seguinte forma:
-![inStore recommended text before](//images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
+![inStore recommended text before](https://images.ctfassets.net/alneenqid6w5/5AWqMIPwGc6aCSYGEsOAOq/6c1eda39348438463dc65a30fa56261e/inStore_recommended_text_before.png)
 
 Ao alterar o arquivo `checkout-instore-custom.js` colocando o seguinte texto extra:
 
@@ -44,6 +44,6 @@ window.INSTORE_CONFIG = {
 ```
 
 Agora quando for impresso o pedido, teremos:
-![inStore recommended text after](//images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
+![inStore recommended text after](https://images.ctfassets.net/alneenqid6w5/7loSAqq1wIWIioOekyiaIO/2226bb32bb7a191b5f709e3ce429d30d/inStore_recommended_text_after.png)
 
 
diff --git a/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md b/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md
index a685c5bfe..7be3da08f 100644
--- a/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md
+++ b/docs/tracks/pt/how-to-change-the-sales-policy-used-by-instore.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 Se você configurou sua loja utilizando o fluxo de __Easy Setup__ já foi criada uma loja para você no __Admin das lojas__ dentro do VTable da VTEX (https://{{AccountName}}.myvtex.com/admin/vtable).
 
-![inStore aplicacoes vtable](//images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
+![inStore aplicacoes vtable](https://images.ctfassets.net/alneenqid6w5/6BRkoPO2cMOQkYkuSOeCO6/641c901771af479df13a487c123aff23/inStore_aplicacoes_vtable.png)
 
 Clique em __Admin dos lojas__ para abrir a tabela onde você verá as lojas físicas.
 
@@ -24,7 +24,7 @@ Se você não usou o __Easy Setup__ e assim não ver nenhuma loja cadastrada, cr
 
 Caso você já tenha cadastrado uma loja por meio do __Easy Setup__, você verá o registro dessa loja criada como na imagem a seguir.
 
-![vtable-admin-das-lojas-2](//images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
+![vtable-admin-das-lojas-2](https://images.ctfassets.net/alneenqid6w5/5cPD8WQ7aweMmwEoksiEC4/2380695922f3ca7f7288e921bf859a78/vtable-admin-das-lojas-2.png)
 
 Para alterar qualquer dado, incluindo a política comercial da loja, basta alterar a celula relacionada e depois clicar no botão de __Salvar__.
 
diff --git a/docs/tracks/pt/how-to-configure-a-custom-payment.md b/docs/tracks/pt/how-to-configure-a-custom-payment.md
index a8ba38c59..fa4ab1bfc 100644
--- a/docs/tracks/pt/how-to-configure-a-custom-payment.md
+++ b/docs/tracks/pt/how-to-configure-a-custom-payment.md
@@ -36,7 +36,7 @@ Permite que você utilize um cartão de crédito da loja com uma das seguintes b
 3.  Selecione uma das opções de pagamento customizado.  
 4.  Preencha os campos do formulário e clique em  **Salvar**.
 
-![PT Pagamento Customizado](//images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
+![PT Pagamento Customizado](https://images.ctfassets.net/alneenqid6w5/2Pg4CTwaCjKH0iQvXgbSm9/b0bf041d2adfa1d0046d6f2f3b849948/PT_Pagamento_Customizado.gif)
 
 Após essa configuração, será necessária a criação da [Condição de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento/).  
 
diff --git a/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
index be4b2a005..6f0832a2e 100644
--- a/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-setup
 
 Entre as opções oferecidas pela **inStore** ao concluir uma venda, existe uma que permite imprimir o resumo do pedido.
 
-![PT-Venda corfimada](//images.ctfassets.net/alneenqid6w5/4S51lvnSiCJIyH2IiG49Uy/2b3a3dfd3a7248080339e9e4a16efd93/PT-Venda_confirmada.png)
+![PT-Venda corfimada](https://images.ctfassets.net/alneenqid6w5/4S51lvnSiCJIyH2IiG49Uy/2b3a3dfd3a7248080339e9e4a16efd93/PT-Venda_confirmada.png)
 
 Para configurar esta opção, serão necessárias duas pequenas etapas:
   1. Pelo Admin VTEX, ative a opção de configuração do dispositivo no menu inStore
@@ -28,7 +28,7 @@ Hoje, essa configuração está presente no administrador do portal, mais especi
 
 Para habilitar a opção _"Configurar dispositivo"_, você deve encontrar o objeto **_window.INSTORE_CONFIG_** presente neste arquivo e adicionar a propriedade **_configureDeviceEnabled_** com o valor **_true_**, e também adicionar o objeto **_printingConfig_** à propriedade **_printByBroker_** com o valor true, para que o inStore permita o uso da propriedade opção dentro do menu, como mostra a imagem de exemplo abaixo:
 
-![PT-Configurar dispositivo](//images.ctfassets.net/alneenqid6w5/FNNbs1nFbkwbQHD4LfMx5/639002d286b1c502cc8079a2b6b64aad/PT-Configurar_dispositivo.png)
+![PT-Configurar dispositivo](https://images.ctfassets.net/alneenqid6w5/FNNbs1nFbkwbQHD4LfMx5/639002d286b1c502cc8079a2b6b64aad/PT-Configurar_dispositivo.png)
 
 Não exclua nenhuma das outras propriedades presentes neste objeto. O resultado deve ser algo como:
 
@@ -62,11 +62,11 @@ printPageAutomatically: true
   2. Abra o aplicativo inStore e entre na loja onde deseja configurar a impressora.
   3. No menu do inStore, no bloco "Configurações", a opção "Configurar o dispositivo" deve aparecer. Clique ali.
 
-![PT-Barra inStore](//images.ctfassets.net/alneenqid6w5/3D4dG6jMeBrKYFzdatmWID/4a0c6e1daa1c7f324174dc87d0119ca7/PT-Barra_inStore.png)
+![PT-Barra inStore](https://images.ctfassets.net/alneenqid6w5/3D4dG6jMeBrKYFzdatmWID/4a0c6e1daa1c7f324174dc87d0119ca7/PT-Barra_inStore.png)
 
   4. Você encontrará o resumo do dispositivo configurado. Se for a primeira vez, as informações estarão vazias. Se um dispositivo já tiver sido configurado anteriormente, algumas informações sobre o dispositivo serão exibidas _(Nome do dispositivo e Impressora padrão)_. Clique na opção "Editar".
   
-  ![PT-Dispositivo via Broadcast](//images.ctfassets.net/alneenqid6w5/5EqfgcZGdhiLtJcZmYkqGb/66c7deeb361ad97d98cf649458f09758/PT-Dispositivo_via_Broadcast.png)
+  ![PT-Dispositivo via Broadcast](https://images.ctfassets.net/alneenqid6w5/5EqfgcZGdhiLtJcZmYkqGb/66c7deeb361ad97d98cf649458f09758/PT-Dispositivo_via_Broadcast.png)
   
   5. Um formulário aparecerá indicando os dados do _AppKey_, _AppToken_ e o nome com o qual você deseja identificar o dispositivo. Após inserir esses dados, clique em "Configurar".
   6. Por fim, incluindo os dados acima, será possível selecionar a impressora na lista de opções. A ideia é selecionar uma dessas opções e clicar em “Configurar” novamente.
diff --git a/docs/tracks/pt/how-to-get-started.md b/docs/tracks/pt/how-to-get-started.md
index 4416e19e3..997a27d04 100644
--- a/docs/tracks/pt/how-to-get-started.md
+++ b/docs/tracks/pt/how-to-get-started.md
@@ -16,17 +16,17 @@ trackSlugPT: suiteshare
 
 Após realizar o seu cadastro na **VTEX Assisted Sales (SuiteShare)**, você pode estar em uma dessas duas situações: No trial de 7 dias do plano Enterprise ou no plano que você já contratou conosco. 
 
-![Suitshare-Como começar](//images.ctfassets.net/alneenqid6w5/8fSuhGRJ2V9P3SJUz2lgB/211f16f93cc9b6b056171968f45db640/Screenshot_2022-08-24_at_17-39-46_Como_come__ar.png)
+![Suitshare-Como começar](https://images.ctfassets.net/alneenqid6w5/8fSuhGRJ2V9P3SJUz2lgB/211f16f93cc9b6b056171968f45db640/Screenshot_2022-08-24_at_17-39-46_Como_come__ar.png)
 
 Caso você não não saiba em que situação está o seu plano, você pode consultar em **Minha conta**: 
 
-![Suitshare-Como começar2](//images.ctfassets.net/alneenqid6w5/3NmGx5TTBsOZlrFSIqIwNR/bb96395f146e9ea661acccd1615fd652/Screenshot_2022-08-24_at_17-39-52_Como_come__ar.png)
+![Suitshare-Como começar2](https://images.ctfassets.net/alneenqid6w5/3NmGx5TTBsOZlrFSIqIwNR/bb96395f146e9ea661acccd1615fd652/Screenshot_2022-08-24_at_17-39-52_Como_come__ar.png)
 
 O primeiro passo dentro da **VTEX Assisted Sales (SuiteShare)** é [criar os links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB) de Whatsapp que serão utilizados. Os links são a maneira mais fácil para que o seu cliente entre em contato com você via Whatsapp em apenas um clique. Para facilitar o processo de criação, você pode [acessar o nosso tutorial](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB) que irá lhe auxiliar na criação dos links.
 
 Após finalizar a criação dos seus links, você pode gerenciá-los através da aba de links, gerar um [QRCode](https://help.vtex.com/pt/tutorial/qr-code-suiteshare--t7faoKDUUr4ZZlrfS0sXV) para utilizar em materiais impressos, descobrir o número de cliques e data de criação.
 
-![Suitshare-Como começar3](//images.ctfassets.net/alneenqid6w5/2fQZjEXKihad8NTPxkfHgB/a10e14d441d00734cfa72d68221a53c8/Screenshot_2022-08-24_at_17-39-56_Como_come__ar.png)
+![Suitshare-Como começar3](https://images.ctfassets.net/alneenqid6w5/2fQZjEXKihad8NTPxkfHgB/a10e14d441d00734cfa72d68221a53c8/Screenshot_2022-08-24_at_17-39-56_Como_come__ar.png)
 
 Com os links criados, podemos passar para os próximos passos da nossa jornada. Defina o maior desafio da sua empresa para começar: 
 
diff --git a/docs/tracks/pt/how-to-register-your-salespersons-on-vtex-instore.md b/docs/tracks/pt/how-to-register-your-salespersons-on-vtex-instore.md
index db5c37cb9..fcd254310 100644
--- a/docs/tracks/pt/how-to-register-your-salespersons-on-vtex-instore.md
+++ b/docs/tracks/pt/how-to-register-your-salespersons-on-vtex-instore.md
@@ -24,23 +24,23 @@ O cadastro do vendedor permite o app ter uma associação de um vendedor com uma
 2. Carregar os preços, condições de pagamento e disponibilidade do produto da loja que o vendedor faz parte;
 
 A identificação do vendedor é feita assim que o inStore é aberto pela primeira vez no dia:
-![identificacao-vendedor](//images.contentful.com/alneenqid6w5/2LhlUtsEYouEY4i4iYOIOq/d556be06047c26ee85f392ba7256f9f8/identificacao-vendedor.png)
+![identificacao-vendedor](https://images.contentful.com/alneenqid6w5/2LhlUtsEYouEY4i4iYOIOq/d556be06047c26ee85f392ba7256f9f8/identificacao-vendedor.png)
 
 Para cadastrar os vendedores que a tela acima permite identificar basta acessar o seu Masterdata.
 
  1. Clique em `Profile System`;
  2. Em seguida `Vendedores`;
  3. Em seguida `Listar`, como mostra a imagem abaixo.
-![masterdata-home-vendedores](//images.contentful.com/alneenqid6w5/32iOuRESyIwEwSE4WcEWmu/b64645e6f940399933df3db5b40d6a4f/masterdata-home-vendedores.png)
+![masterdata-home-vendedores](https://images.contentful.com/alneenqid6w5/32iOuRESyIwEwSE4WcEWmu/b64645e6f940399933df3db5b40d6a4f/masterdata-home-vendedores.png)
 
 Após clicar em `listar`, uma lista de vendedores cadastrados irá aparecer conforme mostra a imagem abaixo. Clique em `Novo` para cadastrar um novo vendedor.
-![masterdata-lista-vendedores](//images.contentful.com/alneenqid6w5/xsepOCP9Dwiys6MKkQGY4/4717c2ff41b7b52a43b549294877713f/masterdata-lista-vendedores.png)
+![masterdata-lista-vendedores](https://images.contentful.com/alneenqid6w5/xsepOCP9Dwiys6MKkQGY4/4717c2ff41b7b52a43b549294877713f/masterdata-lista-vendedores.png)
 
 Preencha as informações do vendedor no formulário. No campo `Loja`, digite o nome da loja. Verifique se todas as informações estão corretas e depois clique em `Salvar`.
-![masterdata-novo-vendedor](//images.contentful.com/alneenqid6w5/7mfVtDbemWWA6yqqYIQgwC/a498d9fbd2dcfbe87546711d8d8c7a36/masterdata-novo-vendedor.png)
+![masterdata-novo-vendedor](https://images.contentful.com/alneenqid6w5/7mfVtDbemWWA6yqqYIQgwC/a498d9fbd2dcfbe87546711d8d8c7a36/masterdata-novo-vendedor.png)
 
 Também será necessário configurar um perfil de acesso para esse vendedor no seu License Manager. Basta clicar em `Usuários` e criar um novo cadastro com o mesmo email que foi colocado no cadastro de Vendedor no Masterdata, o Perfil de Acesso que deve ser adicionado é o `Vendedor inStore`.
 
 *Assim que o novo vendedor for cadastrado no License Manager ele receberá um email de confirmação. Será solicitado que ele cadastre e confirme uma senha de acesso.*
 
-![license-manager-novo-vendedor](//images.contentful.com/alneenqid6w5/98ppRH68esOwU2cWSiM4w/501c79f9cc247103868a026581f7573c/license-manager-novo-vendedor.png)
+![license-manager-novo-vendedor](https://images.contentful.com/alneenqid6w5/98ppRH68esOwU2cWSiM4w/501c79f9cc247103868a026581f7573c/license-manager-novo-vendedor.png)
diff --git a/docs/tracks/pt/including-order-variables-in-email-template.md b/docs/tracks/pt/including-order-variables-in-email-template.md
index 7451ab725..73ab2674f 100644
--- a/docs/tracks/pt/including-order-variables-in-email-template.md
+++ b/docs/tracks/pt/including-order-variables-in-email-template.md
@@ -30,7 +30,7 @@ Digamos que você queira inserir o nome da transportadora no e-mail de pedido en
 
 Para fazer isso, entre no template de pedido enviado e, no campo __JSON Data__, busque a propriedade `courier`.
 
-![courier](//images.contentful.com/alneenqid6w5/2AKyoHdoQ8c40SsQa2uSKS/b4c2b0c460d0f31bec40148f5bba6006/courier.png)
+![courier](https://images.contentful.com/alneenqid6w5/2AKyoHdoQ8c40SsQa2uSKS/b4c2b0c460d0f31bec40148f5bba6006/courier.png)
 
 O valor preenchido para essa propriedade é apenas um exemplo, mas você pode usá-la no campo __HTML__ para que, quando o e-mail for enviado, o cliente veja a transportadora de fato responsável pela entrega do pedido.
 
@@ -38,6 +38,6 @@ Note que a propriedade `courier` está dentro do objeto `package`. Portanto, voc
 
 `{{package.courier}}`
 
-![courier3](//images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
+![courier3](https://images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
 
 Veja que o valor de exemplo ("Transportadora Teste Courier S.A.") foi inserido na tela de preview, abaixo dos campos __HTML__ e __JSON Data__.
diff --git a/docs/tracks/pt/indexing-history.md b/docs/tracks/pt/indexing-history.md
index 3457629f0..b03ff60a6 100644
--- a/docs/tracks/pt/indexing-history.md
+++ b/docs/tracks/pt/indexing-history.md
@@ -16,12 +16,12 @@ trackSlugPT: vtex-intelligent-search
 
 **Histórico da Indexação** é a página que monitora a situação de sincronização de todos os produtos do Catálogo enviados para o Intelligent Search. Ele permite visualizar de forma ampla o progresso da indexação da sua loja.
 
-![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 1 - PT](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
 
 A seção **Status da indexação** exibe as seguintes informações:
 
 * **Tempo médio de indexação:** tempo médio para a indexação dos produtos, a partir do momento em que o sistema recebeu a notificação de uma mudança até a atualização na loja. O desempenho do tempo de indexação é medido por um ponto verde (saudável) ou vermelho (ruim). 
-![Historico Indexação 2 - PT](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
+![Historico Indexação 2 - PT](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
 * **Produtos na loja:** quantidade de produtos com informações atualizadas exibidos atualmente na loja.
 * **Divisão dos status:** porcentagem de produtos em cada etapa de indexação. O desempenho da divisão dos status é medido por um ponto verde (saudável) ou vermelho (ruim). As etapas exibidas são:
     * **Atualizado:** a atualização mais recente do produto foi inserida na loja.
@@ -32,15 +32,15 @@ Você pode filtrar a lista de produtos indexados para uma visualização customi
 
 Para filtrar a lista de produtos indexados clique em `Filtro` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Status` você pode selecionar por qual status deseja filtrar, podendo ser `Atualizado`, `Atualizando`, `Erro`.
 
- ![Historico indexação 4 - PT](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+ ![Historico indexação 4 - PT](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Tempo de indexação` você pode selecionar se o intervelo de tempo `É maior que`, `É igual ou maior que`, `É menor que` ou `É igual ou menor que` um horário definido.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
 
 Depois de definir o filtro, clique em `Aplicar` para ativá-lo. 
 
@@ -50,18 +50,18 @@ Você também pode filtrar os produtos exibidos na listagem por **ID**, **Últim
 
 Caso deseje obter mais informações sobre a indexação de um produto específico, você pode clicar na linha do produto na lista para acessar a janela com mais detalhes, ilustrada abaixo.
 
-![Historico indexação 6 - PT](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 6 - PT](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Além dos dados exibidos na lista de produtos, também é possível visualizar:
 
 * **Tempo de Indexação:** registro de quanto tempo durou a última atualização do produto, no formato `hh:mm:ss`.
 * **Linha do tempo da indexação:** registro de cada mudança de status com data e horário. Você pode vizualizar mais detalhes de cada etapa clicando no ícone <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - PT](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 7 - PT](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 É possível reindexar um produto manualmente sem a necessidade de realizar alguma atualização no seu cadastro. Para reidexar um produto, clique em <i class="fa-solid fa-arrows-rotate"></i> `Reindexar`. Apenas produtos no status **Atualizado** podem ser reindexados.
 
 Você pode acessar o **Histórico de indexação** do produto, uma lista com data e horário de cada atualização realizada. Dessa forma, é possível ter registro de toda alteração que foi realizada no produto. Para acessá-lo, clique em <i class="fa-solid fa-arrow-rotate-left"></i> `Histórico`. 
 
-![Histórico da Indexação 8 - PT](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 8 - PT](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
 
diff --git a/docs/tracks/pt/initializing-your-store-theme.md b/docs/tracks/pt/initializing-your-store-theme.md
index 3cbdde0aa..598ef7349 100644
--- a/docs/tracks/pt/initializing-your-store-theme.md
+++ b/docs/tracks/pt/initializing-your-store-theme.md
@@ -27,7 +27,7 @@ Selecione `store-theme` e confirme que você gostaria de fazer o download do pro
 
 Você receberá informações importantes sobre o aplicativo, como o vendor, o nome, o título e a descrição do aplicativo. Use o __account name__ da loja que você está desenvolvendo como o __vendor__. Isso é importante para que posteriormente você consiga publicar corretamente essa app nesta conta. Para usar os valores padrão, basta pressionar Enter.
 
-![store-theme](//images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
+![store-theme](https://images.ctfassets.net/alneenqid6w5/6FEPaKbOMqkndELmvd0u6z/f47d4a3a04b5cf270372b5dbc72940a9/store-theme.svg)
 
 ## Entendendo a estrutura da app
 
@@ -87,7 +87,7 @@ Durante um "link", todas as alterações feitas no seu código são automaticame
 
 Execute o `vtex link` e veja seu aplicativo de exemplo ser compilado e publicado na conta e no workspace que você acabou de criar.
 
-![vtex-link](//images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
+![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
 <div class="alerta alerta-info">
 Lembre-se: execute <code>vtex whoami</code> para ter certeza de que você está na conta certa e em um workspace de teste. Caso contrário, o <code>VTEX Toolbelt</code> irá reclamar do link direto com o master.
@@ -105,4 +105,4 @@ O `{{account}}.myvtex.com` é o seu domínio privado destinado a testar novos wo
 
 Parabéns por linkar sua primeira app no VTEX IO!
 
-![dreamstore](//images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
+![dreamstore](https://images.ctfassets.net/alneenqid6w5/7G77GAWEmdysNJ2JBYaAI8/6b2bc7f47f994242c8a853e84e3f0b67/dreamstore.svg)
diff --git a/docs/tracks/pt/inserting-and-configuring-placeholders.md b/docs/tracks/pt/inserting-and-configuring-placeholders.md
index f00a5f3c6..4a15e52c6 100644
--- a/docs/tracks/pt/inserting-and-configuring-placeholders.md
+++ b/docs/tracks/pt/inserting-and-configuring-placeholders.md
@@ -34,7 +34,7 @@ O que ele faz é criar um elemento configurável no local do código onde for in
 
 É importante inserir um valor de `id`. Este será o identificador desse placeholder no sistema.
 
-![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando o placeholder
 
@@ -42,7 +42,7 @@ Agora que o controle de placeholder foi inserido no template, vamos configurá-l
 
 Isso é feito nas configurações do layout que usa esse template.
 
-1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para inserir um objeto, clique em **add object**. 
 3. Em seguida, escolha o tipo de objeto e clique em **Adicionar**.
 4. Por fim, clique no botão **Save Settings**, no alto da página.
@@ -51,7 +51,7 @@ Agora você já pode editar o objeto inserido no placeholder.
 
 Para isso, clique no lápis dentro do objeto e, em seguida, clique em **add content**.
 
-![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Agora você pode definir o nome desse objeto, subir imagens para ele e configurar as condições em que ele vai ser renderizado, tais como o período. 
 
diff --git a/docs/tracks/pt/instore-basic-settings.md b/docs/tracks/pt/instore-basic-settings.md
index add0f54a3..881245ded 100644
--- a/docs/tracks/pt/instore-basic-settings.md
+++ b/docs/tracks/pt/instore-basic-settings.md
@@ -54,7 +54,7 @@ Após a instalação você vai realizar as configurações básicas do aplicativ
 
 ### Cadastre o endereço da loja
 
-![cadastrar-loja-pt](//images.contentful.com/alneenqid6w5/51ICHIzuWsMAwPCVwQuQoB/071ec5240f968e662badf4e828954072/cadastrar-loja-pt.png)
+![cadastrar-loja-pt](https://images.contentful.com/alneenqid6w5/51ICHIzuWsMAwPCVwQuQoB/071ec5240f968e662badf4e828954072/cadastrar-loja-pt.png)
 
 Nesta tela, informe o nome da primeira loja física onde o VTEX Sales App será utilizado e o endereço completo da loja. Quando tiver preenchido todos os campos, clique em `Confirmar`.
 
@@ -64,7 +64,7 @@ Se você optar por `Pular este passo`, uma loja fictícia será criada para fins
 
 ### Registre o email e nome do vendedor
 
-![registrar-vendedor-pt](//images.contentful.com/alneenqid6w5/5PvZutdPYWkm7rj4HCrlPC/0316ea7fd74dae942a64e5fdb22f3807/registrar-vendedor-pt.png)
+![registrar-vendedor-pt](https://images.contentful.com/alneenqid6w5/5PvZutdPYWkm7rj4HCrlPC/0316ea7fd74dae942a64e5fdb22f3807/registrar-vendedor-pt.png)
 
 Você precisa definir um email e um nome para serem usados como credenciais de login de um vendedor. Quando estiver pronto, clique em `Confirmar`.
 
@@ -80,7 +80,7 @@ Se você optar por `Pular este passo`, um vendedor fictício será criado com o
 
 O próximo passo é configurar os meios de pagamento que você vai aceitar no inStore. Ative as opções desejadas utilizando o botão <i class="fas fa-toggle-on"></i>, conforme ilustrado abaixo.
 
-![configurar-meios-de-pagamento-pt](//images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
+![configurar-meios-de-pagamento-pt](https://images.contentful.com/alneenqid6w5/3kjTg7Y2tUI5UErQBsGc02/5174724afd2987a4b8f578c1d74b87b9/configurar-meios-de-pagamento-pt.gif)
 
 Existem duas opções:
 
@@ -89,7 +89,7 @@ Existem duas opções:
 
 Após selecionar as opções desejadas, clique em `Confirmar`. Você verá a mensagem de confirmação abaixo.
 
-![sucesso-instore-pt](//images.contentful.com/alneenqid6w5/nVSjiQuE0EXIYecELJJFQ/79a0d24adb51e7ad68f371afe5ca0491/sucesso-instore-pt.png)
+![sucesso-instore-pt](https://images.contentful.com/alneenqid6w5/nVSjiQuE0EXIYecELJJFQ/79a0d24adb51e7ad68f371afe5ca0491/sucesso-instore-pt.png)
 
 ## Configurar condições de pagamento
 
diff --git a/docs/tracks/pt/instore-customizations.md b/docs/tracks/pt/instore-customizations.md
index 52447f98d..b66809881 100644
--- a/docs/tracks/pt/instore-customizations.md
+++ b/docs/tracks/pt/instore-customizations.md
@@ -36,11 +36,11 @@ Alternativamente, você pode navegar até o arquivo de configuração a partir d
 
 No menu principal, clique em __Checkout__ e, em seguida, clique no símbolo de engrenagem da loja, como indica a imagem abaixo.
 
-![20. inStore Customizations (intro) - 1](//images.ctfassets.net/alneenqid6w5/4LKGRGjbprogSqW8fZfFDS/2a0919796851d030aa6dd86d93942620/20._inStore_Customizations__intro__-_1.png)
+![20. inStore Customizations (intro) - 1](https://images.ctfassets.net/alneenqid6w5/4LKGRGjbprogSqW8fZfFDS/2a0919796851d030aa6dd86d93942620/20._inStore_Customizations__intro__-_1.png)
 
 Clique, então, na aba __Código__ e depois no arquivo checkout-instore-custom.js, que se encontra na lista de arquivos à direita.
 
-![20. inStore Customizations (intro) - 2](//images.ctfassets.net/alneenqid6w5/6YhI3qfwXzJEn4jnkWHPKC/e64eb7aa7ae72a71deb0308bffa65592/20._inStore_Customizations__intro__-_2.png)
+![20. inStore Customizations (intro) - 2](https://images.ctfassets.net/alneenqid6w5/6YhI3qfwXzJEn4jnkWHPKC/e64eb7aa7ae72a71deb0308bffa65592/20._inStore_Customizations__intro__-_2.png)
 
 ## Alterando o arquivo de customização do inStore
 
@@ -48,7 +48,7 @@ O `checkout-instore-custom.js` é um arquivo JavaScript que aceita uma série de
 
 Para fazer qualquer alteração, basta incluir ou modificar as linhas de código diretamente na caixa de edição do arquivo, no Admin da VTEX, e finalmente clicar no botão de __Salvar__, como indica a imagem abaixo.
 
-![20. inStore Customizations (intro) - 3](//images.ctfassets.net/alneenqid6w5/4MRxgu5pLvZYTa8hGObbH1/96489ddb7665b702da05e72fd6d7e1bf/20._inStore_Customizations__intro__-_3.png)
+![20. inStore Customizations (intro) - 3](https://images.ctfassets.net/alneenqid6w5/4MRxgu5pLvZYTa8hGObbH1/96489ddb7665b702da05e72fd6d7e1bf/20._inStore_Customizations__intro__-_3.png)
 
 <div class="alert alert-warning">
 Siga sempre as instruções de customização desta documentação e faça apenas as alterações conforme indicadas aqui.
diff --git a/docs/tracks/pt/instore-login.md b/docs/tracks/pt/instore-login.md
index 445d694e4..ae7d1611a 100644
--- a/docs/tracks/pt/instore-login.md
+++ b/docs/tracks/pt/instore-login.md
@@ -18,7 +18,7 @@ O primeiro contato do vendedor da loja física com o VTEX Sales App acontece no
 
 Aqui devem ser usados o email e a senha criados para o vendedor na etapa de [Configurações Básicas](https://help.vtex.com/pt/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO#adding-a-sales-associates-email-and-name). Lembre-se que não é permitido usar emails que já tenham acesso ao Admin de lojas VTEX.
 
-![31. inStore - Product Overview - 1](//images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/6043e4d8fe06f651f2740286a89e323c/instore-login-PT.png)
+![31. inStore - Product Overview - 1](https://images.ctfassets.net/alneenqid6w5/35HU0Wz5eJp53X7JSebBgx/6043e4d8fe06f651f2740286a89e323c/instore-login-PT.png)
 
 Ao fazer o login, o vendedor acessa o VTEX Sales App específico de uma conta VTEX. Embora não seja um cenário comum, um mesmo vendedor pode estar atrelado a mais de uma conta. Se precisar trocar de conta, basta fazer logout e, na tela de login, clicar em `Alterar Loja`.
 
diff --git a/docs/tracks/pt/instore.md b/docs/tracks/pt/instore.md
index 4cc6abfdc..8fe2fd311 100644
--- a/docs/tracks/pt/instore.md
+++ b/docs/tracks/pt/instore.md
@@ -24,7 +24,7 @@ O primeiro contato do vendedor da loja física com o inStore acontece no momento
 
 Aqui devem ser usados o e-mail e a senha criados para o vendedor na etapa de [Basic Setup](https://help.vtex.com/pt/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO). Lembre-se que não é permitido usar e-mails que já tenham acesso ao painel administrativo de lojas VTEX.
 
-![31. inStore - Product Overview - 1](//images.ctfassets.net/alneenqid6w5/3PLZFDcKUMOzX4oDtPg1D9/de1b8f3d8b6d4fd6503bc9775892d0ee/31._inStore_-_Product_Overview_-_1.jpg)
+![31. inStore - Product Overview - 1](https://images.ctfassets.net/alneenqid6w5/3PLZFDcKUMOzX4oDtPg1D9/de1b8f3d8b6d4fd6503bc9775892d0ee/31._inStore_-_Product_Overview_-_1.jpg)
 
 Ao fazer o login, o vendedor acessa o inStore específico de uma conta VTEX. Embora não seja um cenário comum, um mesmo vendedor pode estar atrelado a mais de uma conta. Se precisar trocar de conta, basta fazer logout e, na tela de login, clicar em __Alterar Loja__.
 
@@ -46,7 +46,7 @@ Você pode [configurar quais métodos de identificação deseja habilitar](https
 
 No exemplo da imagem abaixo, estão habilitados E-mail e CPF.
 
-![31. inStore - Product Overview - 2](//images.ctfassets.net/alneenqid6w5/3PXA3jRSgYOX4YABRCNe22/d032f9ee41ace4b964a0900cbc58a3af/31._inStore_-_Product_Overview_-_2.jpg)
+![31. inStore - Product Overview - 2](https://images.ctfassets.net/alneenqid6w5/3PXA3jRSgYOX4YABRCNe22/d032f9ee41ace4b964a0900cbc58a3af/31._inStore_-_Product_Overview_-_2.jpg)
 
 Basta inserir um desses dados no campo e clicar no botão __Confirmar__.
 
@@ -60,11 +60,11 @@ Embora seja possível atender clientes sem identificá-los, recomendamos sempre
 
 A barra superior do aplicativo do inStore oferece algumas opções frequentemente usadas pelo vendedor. Uma delas é a da busca por SKUs, disponível no canto superior direito.
 
-![31. inStore - Product Overview - 3](//images.ctfassets.net/alneenqid6w5/6LJqD76EflPnW1ntKJ05Tt/098471e730845c8a31801e3750a28c97/31._inStore_-_Product_Overview_-_3.png)
+![31. inStore - Product Overview - 3](https://images.ctfassets.net/alneenqid6w5/6LJqD76EflPnW1ntKJ05Tt/098471e730845c8a31801e3750a28c97/31._inStore_-_Product_Overview_-_3.png)
 
 A busca do inStore é omnichannel. Ou seja, ao fazer uma busca no aplicativo, o vendedor está buscando tanto no estoque local (da loja física em si) quanto no catálogo de outras lojas físicas e do e-commerce.
 
-![31. inStore - Product Overview - 4](//images.ctfassets.net/alneenqid6w5/1m7tJFo3VHdqNZbbw9SDMG/b5a0dc2efb81521f8317ec6f0edd86db/31._inStore_-_Product_Overview_-_4.png)
+![31. inStore - Product Overview - 4](https://images.ctfassets.net/alneenqid6w5/1m7tJFo3VHdqNZbbw9SDMG/b5a0dc2efb81521f8317ec6f0edd86db/31._inStore_-_Product_Overview_-_4.png)
 
 As opções de disponibilidade de entrega e retirada serão mostradas depois, na etapa de entrega.
 
@@ -72,11 +72,11 @@ As opções de disponibilidade de entrega e retirada serão mostradas depois, na
 
 Após fazer a identificação do cliente, o vendedor é levado já diretamente para o carrinho. Lá, se estiver usando a versão para desktop do inStore, conectada a um leitor de código de barras, basta bipar os produtos para que eles apareçam no carrinho.
 
-![31. inStore - Product Overview - 5](//images.ctfassets.net/alneenqid6w5/zYrBMK3ZD8nLWSlWJ0k1C/ffead039b599a608e2767e642290a396/31._inStore_-_Product_Overview_-_5.png)
+![31. inStore - Product Overview - 5](https://images.ctfassets.net/alneenqid6w5/zYrBMK3ZD8nLWSlWJ0k1C/ffead039b599a608e2767e642290a396/31._inStore_-_Product_Overview_-_5.png)
 
 Se o vendedor estiver usando um tablet ou smartphone, ele verá, na barra superior do aplicativo, um botão de leitura de código de barras.
 
-![31. inStore - Product Overview - 6](//images.ctfassets.net/alneenqid6w5/6AIhwNFp2qUA74hhScWN76/5a46203e12b175a4f8beebe26b4d7bc3/31._inStore_-_Product_Overview_-_6.png)
+![31. inStore - Product Overview - 6](https://images.ctfassets.net/alneenqid6w5/6AIhwNFp2qUA74hhScWN76/5a46203e12b175a4f8beebe26b4d7bc3/31._inStore_-_Product_Overview_-_6.png)
 
 Ao clicar nele, o vendedor pode usar a câmera para bipar um produto e, com isso, ser levado automaticamente à tela de detalhes deste produto.
 
@@ -119,11 +119,11 @@ Todas essas informações, é bom lembrar, se referem não apenas à experiênci
 
 Ao clicar nos detalhes de um produto que aparece nos resultados da busca do inStore, ou ao bipar um produto, o vendedor é direcionado à tela de detalhes do produto.
 
-![31. inStore - Product Overview - 7](//images.ctfassets.net/alneenqid6w5/6xjT1krpqTtSVhDEh4i3vk/ad365df3960022885ed0e279b08d2848/31._inStore_-_Product_Overview_-_7.png)
+![31. inStore - Product Overview - 7](https://images.ctfassets.net/alneenqid6w5/6xjT1krpqTtSVhDEh4i3vk/ad365df3960022885ed0e279b08d2848/31._inStore_-_Product_Overview_-_7.png)
 
 Essa tela mostra o nome do produto, sua galeria de fotos, variações, descrição e disponibilidade. O vendedor pode, nessa tela, adicionar o produto ao carrinho.
 
-![31. inStore - Product Overview - 8](//images.ctfassets.net/alneenqid6w5/1CEnHyRjNNX1GvMd8hKjLg/2f765e5a9959a5c0114651e4283baf71/31._inStore_-_Product_Overview_-_8.png)
+![31. inStore - Product Overview - 8](https://images.ctfassets.net/alneenqid6w5/1CEnHyRjNNX1GvMd8hKjLg/2f765e5a9959a5c0114651e4283baf71/31._inStore_-_Product_Overview_-_8.png)
 
 Note que, se você configurou sua loja para [forçar disponibilidade de estoque](https://help.vtex.com/pt/tracks/instore-customizations--1z9kBm12oBPyVNDo1ivVc2/2SgRUekV8FO4lg2aO6YTmh), mesmo que o produto esteja indisponível em todos os canais, o vendedor poderá adicioná-lo ao carrinho.
 
@@ -139,7 +139,7 @@ O inStore permite [habilitar uma funcionalidade de transferência de carrinho](h
 
 Uma vez no carrinho de um pedido, o vendedor tem acesso ao botão __Transferir__. Ao clicar nesse botão, o aplicativo mostra um QR Code e um código numérico de quatro dígitos.
 
-![31. inStore - Product Overview - 9](//images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._inStore_-_Product_Overview_-_9.png)
+![31. inStore - Product Overview - 9](https://images.ctfassets.net/alneenqid6w5/3pefz4lrKG7nWWZpJjmR5N/c1149aec863d3554fb2ea67cc79d97ba/31._inStore_-_Product_Overview_-_9.png)
 
 Um outro vendedor logado na mesma loja pode, então, capturar esse carrinho e continuar a venda a partir do seu dispositivo.
 
@@ -158,21 +158,21 @@ A tela seguinte mostra as opções de entrega. Como o inStore lida com o catálo
 
 O exemplo abaixo mostra duas opções: receber todos os itens em casa via entrega econômica ou retirar em outra loja física no prazo de 5 dias úteis.
 
-![31. inStore - Product Overview - 10](//images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
+![31. inStore - Product Overview - 10](https://images.ctfassets.net/alneenqid6w5/621Dlpel880kPOoL8Ur6id/476f54c1dba26c76fc90a691f33baa0c/31._inStore_-_Product_Overview_-_10.png)
 
 ### Pontos de Retirada
 
 Para opções de retirada em loja (pickup point), o sistema seleciona as lojas que têm os SKUs em estoque e mostra a loja mais próxima ao CEP do cliente, como sugestão. Se o vendedor quiser trocar a loja onde o cliente fará a coleta, basta clicar no botão __Alterar ponto de retirada__.
 
-![31. inStore - Product Overview - 11](//images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
+![31. inStore - Product Overview - 11](https://images.ctfassets.net/alneenqid6w5/2lmJceEfryZV6OBtgGc3Tq/167a7c3f169dab3ffbf49c30d670702e/31._inStore_-_Product_Overview_-_11.png)
 
 Ao clicar em Alterar ponto de retirada, o vendedor primeiro tem acesso ao ponto de retirada sugerido pelo sistema. Para ver todos os pontos de retirada disponíveis, basta clicar em __Ver todos os pontos de retirada__.
 
-![31. inStore - Product Overview - 12](//images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
+![31. inStore - Product Overview - 12](https://images.ctfassets.net/alneenqid6w5/1ZUGWgHe2jI2ROLpIZ1HnN/e6a59ee600f6ae05a2d3e2a27cc8501e/31._inStore_-_Product_Overview_-_12.png)
 
 O aplicativo mostrará, então, a lista de pontos de retirada, ordenada por menor distância do CEP do cliente. Também é possível escolher o ponto de retirada pelo mapa.
 
-![31. inStore - Product Overview - 13](//images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
+![31. inStore - Product Overview - 13](https://images.ctfassets.net/alneenqid6w5/uT46sKKgmyT4Lmh8usLO3/3aa559f183e4d5dda3254844aac2fd19/31._inStore_-_Product_Overview_-_13.png)
 
 ## 12. Pagamento
 
@@ -180,17 +180,17 @@ Na etapa de pagamento, aparecerão as [opções de pagamento que foram configura
 
 Uma funcionalidade importante permitida pelo inStore são os múltiplos pagamentos. Por exemplo: escolhendo Dinheiro e depois clicando em __Adicionar outro pagamento__, o vendedor pode fazer parte da cobrança em dinheiro e outra parte em cartão de crédito ou débito.
 
-![31. inStore - Product Overview - 14](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
+![31. inStore - Product Overview - 14](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/6701ce986792dce02f88bfc4a18c0d9d/31._inStore_-_Product_Overview_-_14.png)
 
 A barra superior da tela de pagamento permite adicionar cupom e vale-presente. Permite, ainda, alterar o número do CPF que constará na Nota Fiscal do pedido.
 
-![31. inStore - Product Overview - 15](//images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
+![31. inStore - Product Overview - 15](https://images.ctfassets.net/alneenqid6w5/3CymGlJlWQ9I9w5tiheXQk/577fb68901d2e0a8b17ae11fb55ed98f/31._inStore_-_Product_Overview_-_15.png)
 
 ## 13. Pedido finalizado
 
 O vendedor pode ver essa mesma tela clicando em __Pedidos finalizados__, no menu principal do inStore, e buscando o pedido por número do pedido ou cliente.
 
-![31. inStore - Product Overview - 16](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
+![31. inStore - Product Overview - 16](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/3bda7ef00a309b1e57081ad805adb889/31._inStore_-_Product_Overview_-_16.png)
 
 ## 14. Impressão de NFC-e
 
diff --git a/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
index 8dbd54e38..3c76e97cc 100644
--- a/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
@@ -16,7 +16,7 @@ trackSlugPT: integrar-o-instore-a-um-novo-adquirente-de-pagamento
 
 Este artigo tem como objetivo explicar como a app do inStore configura o AppLinking para as ações de `payment` e `payment-reversal` com as apps dos adquirentes.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuração
 
diff --git a/docs/tracks/pt/integration-configurations.md b/docs/tracks/pt/integration-configurations.md
index 2b085ba58..a7a99f5f6 100644
--- a/docs/tracks/pt/integration-configurations.md
+++ b/docs/tracks/pt/integration-configurations.md
@@ -21,7 +21,7 @@ Os passos a seguir deverão ser feitos dentro do app.
 1. No seletor, escolha a política comercial que será usada na Wish ([pré definida no passo 2](https://help.vtex.com/pt/tracks/configurar-integracao-da-wish--50hbG4bzhSIhjz1lzqI1g43OHGQIQmt1dKw9RwKruE7H#definindo-politica-comercial))
 2. Após selecionar a política comercial, clique em "Continuar".
 
-![PT - Configurar Wish](//images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
+![PT - Configurar Wish](https://images.ctfassets.net/alneenqid6w5/3EGGUHCj7UViCY8Jjct3UY/1172fa1d438d6d0ecaf35a01b57959f1/PT_-_Configurar_Wish.png)
 
 ## Configurações de envio
 
diff --git a/docs/tracks/pt/integration-settings.md b/docs/tracks/pt/integration-settings.md
index 6e00980d4..1858c5fcb 100644
--- a/docs/tracks/pt/integration-settings.md
+++ b/docs/tracks/pt/integration-settings.md
@@ -24,6 +24,6 @@ Siga as instruções para iniciar o processo de integração:
 
 O processo de indexação será iniciado. Uma vez concluído, a tela ilustrada a seguir será exibida.
 
-![integracoes-is](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/43b9e3474b8f3046405278e34266e0fc/integracoes-is.PNG)
+![integracoes-is](https://images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/43b9e3474b8f3046405278e34266e0fc/integracoes-is.PNG)
 
 Não é necessário repetir esse processo. Depois de iniciar a integração, é possível acompanhar o status da indexação na página [Histórico da indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tracks/pt/intelligent-synonyms.md b/docs/tracks/pt/intelligent-synonyms.md
index 85d4faf55..b4133789c 100644
--- a/docs/tracks/pt/intelligent-synonyms.md
+++ b/docs/tracks/pt/intelligent-synonyms.md
@@ -31,7 +31,7 @@ As sugestões são exibidas em duas categorias na listagem de sinônimos, confor
 * **Novas sugestões:** sugestões geradas pela plataforma que ainda não foram visualizadas.
 * **Sugestões salvas:** sugestões salvas para depois, como descrito no passo 5 da seção [Revisar sugestões](#revisar-sugestoes).
 
-![synonym-suggestion-list-pt](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
+![synonym-suggestion-list-pt](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
 
 Você pode revisar as sugestões geradas e optar por salvar para depois, recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
 
@@ -47,7 +47,7 @@ Siga as instruções para visualizar as sugestões de sinônimos e definir se el
 
 4. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
 
-   ![synonym-suggestion-pt](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
+   ![synonym-suggestion-pt](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
 
 5. Para revisar cada sugestão, escolha uma das ações a seguir:
 
diff --git a/docs/tracks/pt/intro-to-vtex-io-builders.md b/docs/tracks/pt/intro-to-vtex-io-builders.md
index 2ce458286..9ec3e1dad 100644
--- a/docs/tracks/pt/intro-to-vtex-io-builders.md
+++ b/docs/tracks/pt/intro-to-vtex-io-builders.md
@@ -19,6 +19,6 @@ Apps do VTEX IO exportam código ou configuração para fornecer features ou alt
 Esses pedaços de código e configuração geralmente requerem alguma preparação ou validação para servirem à sua finalidade. Por exemplo, os componentes React precisam ter suas dependências extraídas e compiladas em pacotes JavaScript.
 
 O VTEX IO cuida automaticamente de todas essas etapas, implementando-as como Builders. Uma vez que sua app declara que ela usa um builder, a pasta correspondente e seu conteúdo são processados ​​por ele quando é realizado o link.
-![builders](//images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
+![builders](https://images.ctfassets.net/alneenqid6w5/4giehwW3uYLEMkq42cFFiX/ba4d8c95146e19f7db0f55bd1a41c2d4/builders.svg)
 
 O projeto store theme usa dois builders principais (`store` e `styles`), mas à medida que criar apps com funcionalidades mais avançadas, você começará a usar outros builders de nível mais baixo, como `react`, `messages`, `graphql` e `node`.
diff --git a/docs/tracks/pt/introduction-to-vtex-io.md b/docs/tracks/pt/introduction-to-vtex-io.md
index 291e44348..be841fd18 100644
--- a/docs/tracks/pt/introduction-to-vtex-io.md
+++ b/docs/tracks/pt/introduction-to-vtex-io.md
@@ -22,7 +22,7 @@ Nesta track, vamos ensinar passo a passo como desenvolver uma app utilizando o V
 
 Veja na imagem abaixo a estrutura de hierarquia do VTEX IO:
 
-![VTEX IO Hierarchy](//images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
+![VTEX IO Hierarchy](https://images.ctfassets.net/alneenqid6w5/44SdYX37X2WKa6gicUKQWS/4b699f3355a2d9d70126354578d285cd/VTEX_IO_-_track_img.png)
 
 - __Account__: Para desenvolver uma app, é necessário ter uma conta na VTEX.
 - __Workspaces__: São os ambientes onde as apps serão desenvolvidas. Esses ambientes estão vinculados ao account. É possível ter diversos workspaces para um único account.
diff --git a/docs/tracks/pt/introduction-to-vtex.md b/docs/tracks/pt/introduction-to-vtex.md
index bae9aca47..5c497fae3 100644
--- a/docs/tracks/pt/introduction-to-vtex.md
+++ b/docs/tracks/pt/introduction-to-vtex.md
@@ -18,7 +18,7 @@ A [VTEX](https://vtex.com/br-pt/) é uma solução integrada de comércio global
 
 A imagem a seguir apresenta as soluções e possibilidades da VTEX, que serão abordadas ao longo desta trilha:
 
-![vtex_composable_complete_PT](//images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/c5b053eec0632543c254624f13bf6dbf/vtex_composable_complete_PT.png)
+![vtex_composable_complete_PT](https://images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/c5b053eec0632543c254624f13bf6dbf/vtex_composable_complete_PT.png)
 
 <div class="alert alert-info">
 Além dos portais de documentação Help Center e <a href="https://developers.vtex.com/">Developer Portal</a> e da <a href="https://community.vtex.com/">VTEX Community</a>, em nosso <a href="https://vtex.com/br-pt/">site</a> disponibilizamos mais informações sobre a plataforma por meio de <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">demo videos</a> (somente inglês) e <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> criados por <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros</a>. Também é possível conferir uma série de <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">vídeos de onboarding</a> (somente português).
diff --git a/docs/tracks/pt/inventory-and-shipping-module-overview.md b/docs/tracks/pt/inventory-and-shipping-module-overview.md
index 25be04966..409b4917e 100644
--- a/docs/tracks/pt/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/pt/inventory-and-shipping-module-overview.md
@@ -18,7 +18,7 @@ O módulo de __Estoque e entrega__ é o serviço responsável pela *logística*
 
 O sistema de logística possui diversas funcionalidades úteis. Estas *features* permitem que você monte uma estratégia de estoque e entrega da maneira mais adequada ao seu negócio. Nos próximos passos desta trilha, veremos como utilizar cada uma das funcionalidades exibidas abaixo. No admin da sua loja, você vai encontrar as seguintes seções:
 
-![inventory-shipping-admin-pt](//images.ctfassets.net/alneenqid6w5/6S8H6GEZ58BQc9V6YfTT6Y/242d97ee4ba2809fcb9dd2c209e7fa9b/inventory-shipping-admin-pt.png)
+![inventory-shipping-admin-pt](https://images.ctfassets.net/alneenqid6w5/6S8H6GEZ58BQc9V6YfTT6Y/242d97ee4ba2809fcb9dd2c209e7fa9b/inventory-shipping-admin-pt.png)
 
 __Estratégia de envio__ (Painéis) - Nesta seção, você deve cadastrar as rotas logísticas que realizam a entrega dos seus pedidos. Um rota básica é composta por um __estoque__, uma __doca__ e uma __política de envio__ (transportadora).
 
diff --git a/docs/tracks/pt/legacy-cms-portal.md b/docs/tracks/pt/legacy-cms-portal.md
index b46b0e8f1..536cda3b3 100644
--- a/docs/tracks/pt/legacy-cms-portal.md
+++ b/docs/tracks/pt/legacy-cms-portal.md
@@ -18,7 +18,7 @@ trackSlugPT: cms
 
 A seção [Layout](https://help.vtex.com/pt/subcategory/layout--2g6LxtasS4iSeGEqeYUuGW) permite que você crie seu storefront usando HTML e CSS. Ela é organizada em pastas e arquivos com as funções descritas abaixo.
 
-![CMS - Layout PT](//images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/ce15ae6de766c7856a26d9c2f7e21cbc/cms-layout-pt.png)
+![CMS - Layout PT](https://images.ctfassets.net/alneenqid6w5/4YnFtKkC8exlv3vm8VTCqh/ce15ae6de766c7856a26d9c2f7e21cbc/cms-layout-pt.png)
 
 - **HTML Templates:** criar o código HTML e os arquivos JavaScript e CSS de referência que serão usados nas páginas do site.
 
@@ -38,7 +38,7 @@ A seção [Layout](https://help.vtex.com/pt/subcategory/layout--2g6LxtasS4iSeGEq
 
 A seção [Configurações](https://help.vtex.com/pt/subcategory/configuracoes-de-cms--6kovkwzMRyeOOc2iEC4suM) permite que você defina configurações relacionadas ao site da sua loja, como metadados, tags de SEO, tipos de arquivos, etc. 
 
-![CMS - Settings PT](//images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/77031b9bdbae01c422147d00c9f9a2cb/cms-settings-pt.png)
+![CMS - Settings PT](https://images.ctfassets.net/alneenqid6w5/1JFkw9wFlJd5oulogEGDDL/77031b9bdbae01c422147d00c9f9a2cb/cms-settings-pt.png)
 
 A seção **Configurações*** contém as seguintes abas:
 
@@ -67,7 +67,7 @@ Toda loja precisa ter, sem exceção, as seguintes pastas no CMS para garantir o
 
 Veja abaixo estas pastas básicas no CMS:
 
-![2 1](//images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
+![2 1](https://images.ctfassets.net/alneenqid6w5/6jvwsPMcIBTllVekqROlkk/ea2d4a9d0d4cdb8a07dd02a3add4b40b/2_1.png)
 
 Estas pastas vêm por padrão no ambiente de todas as lojas VTEX.
 
diff --git a/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md b/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md
index 99d64037f..94153abc3 100644
--- a/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md
+++ b/docs/tracks/pt/levar-os-contatos-do-whatsapp-para-um-crm.md
@@ -26,9 +26,9 @@ Você provavelmente já definiu quais [links](https://help.vtex.com/pt/tutorial/
 
 1. No menu principal do seu painel admin na VTEX Assisted Sales (SuiteShare), clique em **Configurações**.
 2. Selecione a opção **Integrações**. 
-![Levar os contatos do WhatsApp para um CRM 1](//images.ctfassets.net/alneenqid6w5/1eVxgg7WRTzIhymKuIKHui/f03e6023c83e6bd24ac65f00e987ef5b/Screenshot_2022-08-24_at_17-59-46_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 1](https://images.ctfassets.net/alneenqid6w5/1eVxgg7WRTzIhymKuIKHui/f03e6023c83e6bd24ac65f00e987ef5b/Screenshot_2022-08-24_at_17-59-46_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 3. Localize o seu CRM dentro das opções de integrações
-![Levar os contatos do WhatsApp para um CRM 2](//images.ctfassets.net/alneenqid6w5/4owv76x3alggHV7HJsHgt8/f9ba71dcd084bdc03d6d7c4e160f2176/Screenshot_2022-08-24_at_17-59-37_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 2](https://images.ctfassets.net/alneenqid6w5/4owv76x3alggHV7HJsHgt8/f9ba71dcd084bdc03d6d7c4e160f2176/Screenshot_2022-08-24_at_17-59-37_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 
 Para realizar as configurações com a ajuda dos nossos tutoriais, escolha na lista abaixo o CRM que deseja configurar.  
 
@@ -49,13 +49,13 @@ Não encontrou o seu CRM na lista?
 Não se preocupe, você pode avisar nossa equipe qual o CRM deseja integrar para avaliarmos a possibilidade de incluí-lo na nossa lista de integração automática. Por enquanto você pode exportar todos os leads para um arquivo CSV e inserir manualmente no seu CRM. 
 
 1. Para fazer isso basta acessar **Capturar**.
-![Levar os contatos do WhatsApp para um CRM 3](//images.ctfassets.net/alneenqid6w5/1iOqIAZHaz9d52kE8HCoct/4ad9945d7f72a7638b316b4661d0d90c/Screenshot_2022-08-25_at_14-44-55_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 3](https://images.ctfassets.net/alneenqid6w5/1iOqIAZHaz9d52kE8HCoct/4ad9945d7f72a7638b316b4661d0d90c/Screenshot_2022-08-25_at_14-44-55_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 2. Clique na opção _**“Leads”**_ 
-![Levar os contatos do WhatsApp para um CRM 4](//images.ctfassets.net/alneenqid6w5/5WBulBLvIz16GiZj2JDzig/ea13b87c7ba52c9e36979a41abff368c/Screenshot_2022-08-24_at_17-59-58_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 4](https://images.ctfassets.net/alneenqid6w5/5WBulBLvIz16GiZj2JDzig/ea13b87c7ba52c9e36979a41abff368c/Screenshot_2022-08-24_at_17-59-58_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 
 Nesta tela você terá as seguintes informações: 
 
-![Levar os contatos do WhatsApp para um CRM 5](//images.ctfassets.net/alneenqid6w5/2i2zwDDmuYMaMA37SjRnd7/754db443e0b63af943c32959c0dfa0f7/Screenshot_2022-08-25_at_14-46-39_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
+![Levar os contatos do WhatsApp para um CRM 5](https://images.ctfassets.net/alneenqid6w5/2i2zwDDmuYMaMA37SjRnd7/754db443e0b63af943c32959c0dfa0f7/Screenshot_2022-08-25_at_14-46-39_Levar_os_contatos_do_WhatsApp_para_um_CRM.png)
 
 **1 Exportar** : Você exporta em CSV toda a lista de leads cadastrados na captura. 
 
diff --git a/docs/tracks/pt/live-support.md b/docs/tracks/pt/live-support.md
index b616c29a3..c90e4679c 100644
--- a/docs/tracks/pt/live-support.md
+++ b/docs/tracks/pt/live-support.md
@@ -19,7 +19,7 @@ Atendimento Humano é a configuração que auxiliará sua loja no suporte ao cli
 Para a ativação do Atendimento Humano, é necessário seguir os passos de integração descritos em [Configuração da estrutura para atendimento humano](https://help.vtex.com/pt/tracks/conversational-commerce-vtex--5UZ9BdvwwtZm2t9QTXcbZs/SxhYiiqUJYiQX4CIWxmVE).
 
 Para configurar os horários de funcionamento do Atendimento Humano na sua loja, siga os passos abaixo.
-![Live Support pt](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
+![Live Support pt](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
 
 1. Visite seu Admin > Apps > Conversational Commerce > Configurações> Atendimento Humano.
 2. Ative o Atendimento Humano em sua loja.
@@ -29,11 +29,11 @@ Para configurar os horários de funcionamento do Atendimento Humano na sua loja,
 # Configurações Gerais
 
 1. Defina se deseja ativar o Atendimento Humano em sua loja. 
-![Live Support pt](//images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
+![Live Support pt](https://images.ctfassets.net/alneenqid6w5/LUYDZvr1wopIGPIxieLPh/cf276b86b26aaa97131b381e7d47aff0/image1.png)
 Se optar por não utilizar, é necessário definir uma mensagem de indisponibilidade indicando o melhor canal de atendimento para seu cliente. 
-![Mensagem de indisponibilidade](//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/893fc8739cf19e9160a37c650614af2b/Mensagem_de_indisponibilidade.png)
+![Mensagem de indisponibilidade](https://images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/893fc8739cf19e9160a37c650614af2b/Mensagem_de_indisponibilidade.png)
 2. Defina o fuso horário que será utilizado em seu atendimento. 
-![Fuso horário](//images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/70da2f837c8ace1dcf4f03196d03eeb6/Hor__rios_de_funcionamento.png)
+![Fuso horário](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/70da2f837c8ace1dcf4f03196d03eeb6/Hor__rios_de_funcionamento.png)
 3. Selecione os dias e defina os horários de funcionamento do seu Atendimento Humano. É possível definir mais de um período de atendimento por dia de semana. 
 
 <div class="alert alert-info">
diff --git a/docs/tracks/pt/livelo-integration-overview.md b/docs/tracks/pt/livelo-integration-overview.md
index 0f06f56b1..c7fa31b4b 100644
--- a/docs/tracks/pt/livelo-integration-overview.md
+++ b/docs/tracks/pt/livelo-integration-overview.md
@@ -16,7 +16,7 @@ trackSlugPT: integracao-livelo
 
 A Livelo é a plataforma de marketplace com o maior programa de recompensas do Brasil. Atualmente, a Livelo comercializa produtos diversos, com destaque para as categorias de eletrônicos, eletrodomésticos, eletroportáteis e utilidades domésticas.
 
-![Logo Livelo](//images.ctfassets.net/alneenqid6w5/3pndHEvgehYKfuzlg2Zk7Y/ad11bd007d297906f52fc650fcbe197d/logo-livelo.jpg)  
+![Logo Livelo](https://images.ctfassets.net/alneenqid6w5/3pndHEvgehYKfuzlg2Zk7Y/ad11bd007d297906f52fc650fcbe197d/logo-livelo.jpg)  
 
 A configuração com a Livelo tem como objetivo conectar sua loja VTEX com o marketplace, permitindo que você anuncie seus produtos, aumente suas vendas e atingindo novos clientes a partir deste novo canal.   
 
diff --git a/docs/tracks/pt/login-e-senha.md b/docs/tracks/pt/login-e-senha.md
index 943845d48..4f990033c 100644
--- a/docs/tracks/pt/login-e-senha.md
+++ b/docs/tracks/pt/login-e-senha.md
@@ -20,7 +20,7 @@ Para conseguir o login e senha para acessar o adaptador, você deve abrir um cha
 
 Em seu navegador preferido, digite `https://adapterstaging.ciashop.com.br/`. Sugerimos adicionar este link na pasta favoritos do seu navegador preferido.
 
-![login-adaptador](//images.ctfassets.net/alneenqid6w5/4toFGLYSg26MGGWMf3kHDc/4fbb56d3ebf3f7dca51ea3aa9bd623c0/login-adaptador.png)
+![login-adaptador](https://images.ctfassets.net/alneenqid6w5/4toFGLYSg26MGGWMf3kHDc/4fbb56d3ebf3f7dca51ea3aa9bd623c0/login-adaptador.png)
 
 ## Efetuando login (ambiente de homologação) com os dados enviados pela equipe de atendimento
 
diff --git a/docs/tracks/pt/magazine-luiza-marketplace.md b/docs/tracks/pt/magazine-luiza-marketplace.md
index 5b6489d41..f0cb158e1 100644
--- a/docs/tracks/pt/magazine-luiza-marketplace.md
+++ b/docs/tracks/pt/magazine-luiza-marketplace.md
@@ -16,6 +16,6 @@ trackSlugPT: configurar-integracao-com-o-magazine-luiza
 
 O [Magazine Luiza](https://www.magazineluiza.com.br/) foi criado há mais de 60 anos, e se consolidou como uma das maiores empresas varejistas do Brasil. Atualmente são mais de 900 lojas físicas distribuídas por todo o país e desde 2019, o Magalu vem se posicionando como uma plataforma digital de varejo.
 
-![Logo Magazine Luiza](//images.ctfassets.net/alneenqid6w5/2gWxg3UR4Hxf0XeLIx3QA0/d8a0ed0314ab90c39acff73fef5f8ea9/magazine-luiza-redimensionado-2.jpg)
+![Logo Magazine Luiza](https://images.ctfassets.net/alneenqid6w5/2gWxg3UR4Hxf0XeLIx3QA0/d8a0ed0314ab90c39acff73fef5f8ea9/magazine-luiza-redimensionado-2.jpg)
 
 Por meio da integração da Plataforma VTEX com o Magalu, você pode aumentar a visibilidade dos seus produtos e alavancar suas vendas. O primeiro passo para isso é fazer seu [cadastro no portal Magazine Luiza Marketplace](https://marketplace-vendamais.magazineluiza.com.br/).
diff --git a/docs/tracks/pt/managing-accounts.md b/docs/tracks/pt/managing-accounts.md
index 731b94384..0a4cfe8f6 100644
--- a/docs/tracks/pt/managing-accounts.md
+++ b/docs/tracks/pt/managing-accounts.md
@@ -26,7 +26,7 @@ Ao clicar sobre o nome de uma conta específica, a tela __Detalhes da conta__ ex
 - [Encerramento de conta](#encerramento-da-conta)
 <br>
 <br>
-![Conta_PT](//images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/7a4da3fc9797c2256f03e5811b06475d/Contas_PT.png)
+![Conta_PT](https://images.ctfassets.net/alneenqid6w5/3Wu6HcL5NbC5XS5YdiF3Dx/7a4da3fc9797c2256f03e5811b06475d/Contas_PT.png)
 
 ## Titular
 
diff --git a/docs/tracks/pt/managing-customer-credit-invoices.md b/docs/tracks/pt/managing-customer-credit-invoices.md
index 4d86e031a..1ce9b84f7 100644
--- a/docs/tracks/pt/managing-customer-credit-invoices.md
+++ b/docs/tracks/pt/managing-customer-credit-invoices.md
@@ -21,7 +21,7 @@ A tela de __Títulos__ no Admin VTEX (__Aplicativos > Customer Credit > Títulos
 - [Liquidar títulos](#liquidar-titulos)
 <br>
 <br>
-![Invoices_PT](//images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/3ac50b7bdade789abccccda8abe14352/Invoices_PT.JPG)
+![Invoices_PT](https://images.ctfassets.net/alneenqid6w5/6otbbLNAHn0hHmKvkYmrj2/3ac50b7bdade789abccccda8abe14352/Invoices_PT.JPG)
 
 ## Filtro de títulos
 
diff --git a/docs/tracks/pt/managing-sales-associates-in-instore.md b/docs/tracks/pt/managing-sales-associates-in-instore.md
index 30020b774..ceb6967dc 100644
--- a/docs/tracks/pt/managing-sales-associates-in-instore.md
+++ b/docs/tracks/pt/managing-sales-associates-in-instore.md
@@ -17,7 +17,7 @@ trackSlugPT: instore-primeiros-passos-e-configuracoes
 Após realizar as [configurações básicas do VTEX Sales App no Admin](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/4L5SoLxE8O3YkxF7FKymrO), é possível adicionar novos vendedores ao sistema ou gerenciar os vendedores já cadastrados. 
 A categoria Vendedores representa uma seção dentro das Configurações da loja do Admin VTEX, exibindo a lista completa dos vendedores registrados no aplicativo [VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) da loja. Dentro dessa página, é possível administrar as informações dos vendedores em todas as [contas franquias](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) da sua loja, realizando operações de [cadastrar](#cadastrar-vendedor), [buscar](#buscar-vendedor), [filtrar](#filtrar-vendedores), [editar](#editar-vendedor) e [excluir](#excluir-vendedor)].
 
-![vendedores-pt](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/fbd82da71cf7d2e4a8936b2fd2aac877/PT.png)
+![vendedores-pt](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/fbd82da71cf7d2e4a8936b2fd2aac877/PT.png)
 
 A página apresenta as seguintes informações: 
 
diff --git a/docs/tracks/pt/managing-shipping-rates.md b/docs/tracks/pt/managing-shipping-rates.md
index 223cf5401..4856d5852 100644
--- a/docs/tracks/pt/managing-shipping-rates.md
+++ b/docs/tracks/pt/managing-shipping-rates.md
@@ -18,7 +18,7 @@ Para a correta configuração de uma nova transportadora, é importante detalhar
 
 Ela é usada para registrar os CEPs atendidos, os valores cobrados, as faixas de peso consideradas e os valores adicionais de cada transportadora.
 
-![planilha-frete-pt](//images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
+![planilha-frete-pt](https://images.ctfassets.net/alneenqid6w5/xwa6iEK6ekMSeLLEZhBZL/325dda4a071d57baaf8dd8e3299cec41/planilha-frete-pt.png)
 
 ## Como montar a planilha
 
diff --git a/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index ba09d36ad..91401ca71 100644
--- a/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -18,7 +18,7 @@ Após instalar e configurar o TikTok for Business, você poderá gerenciar a int
 
 Qualquer usuário logado no Admin VTEX poderá acessar essa área de gerenciamento do TikTok. Porém, ao interagir com os botões dessa área, o usuário será redirecionado para ambientes do TikTok – TikTok Business Center, TikTok Ads Manager e TikTok Catalog Manager – onde precisam das permissões necessárias para visualizar o conteúdo e realizar alterações.
 
-![manage-tiktok-integration](//images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
+![manage-tiktok-integration](https://images.ctfassets.net/alneenqid6w5/6E7w4iV9rZX57u2AlG610O/0467f2bd0f4885991ec571a38218a2fb/image1.png)
 
 A partir dessa página, é possível:
 
diff --git a/docs/tracks/pt/mapping-colors-and-sizes.md b/docs/tracks/pt/mapping-colors-and-sizes.md
index e7d34dba5..b3b706bf7 100644
--- a/docs/tracks/pt/mapping-colors-and-sizes.md
+++ b/docs/tracks/pt/mapping-colors-and-sizes.md
@@ -65,7 +65,7 @@ Deve-se escolher a cor disponível mais próxima que, no caso da Wish, "Gelo" po
   OBS: o cabeçalho da tabela deve ser preenchida exatamente como está no exemplo abaixo. Lembre-se de não adicionar caracteres especiais como enter ou espaço no preenchimento dessa tabela. 
   </div>
 
-![PT - Tabela Wish](//images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
+![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
 ## Fazendo o upload
 
diff --git a/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
index 9ffa447c9..16ec1a5dd 100644
--- a/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -57,7 +57,7 @@ Para finalizar o mapeamento da categoria, você deve seguir o passo a passo abai
 
 ## Mapear atributos
 
-![Início (13)](//images.ctfassets.net/alneenqid6w5/owf1A0SnYfOkoNCGDlTFj/ca731b95328853d12ee9872ef14b8aaf/In__cio__13_.gif)
+![Início (13)](https://images.ctfassets.net/alneenqid6w5/owf1A0SnYfOkoNCGDlTFj/ca731b95328853d12ee9872ef14b8aaf/In__cio__13_.gif)
 
 O mapeamento dos atributos permite que exista uma correspondência entre o padrão da sua loja VTEX e o padrão utilizado pelo Mercado Livre. Cada categoria possui seus atributos obrigatórios pelo Mercado Livre e é necessário preenchê-los para que o mapeamento seja concluído. Os campos não mapeados não impedem que o mapeamento ocorra, porém quanto mais atributos enviados para o Mercado Livre seu produto tiver, melhor rankeado ele será no marketplace.
 
diff --git a/docs/tracks/pt/mercado-libre-marketplace.md b/docs/tracks/pt/mercado-libre-marketplace.md
index 1c17507bc..b0fa18430 100644
--- a/docs/tracks/pt/mercado-libre-marketplace.md
+++ b/docs/tracks/pt/mercado-libre-marketplace.md
@@ -18,7 +18,7 @@ O [Mercado Livre](https://www.mercadolivre.com.br/) é um dos líderes do e-comm
 
 Sua operação está presente nos países: Argentina, Brasil, Chile, Colômbia,  México, Uruguai e Venezuela.
 
-![mercado-livre-reproducao-w-970x550](//images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/9f13547ee20c96383f18e8151f98177e/mercado-livre-reproducao-w-970x550.jpg)
+![mercado-livre-reproducao-w-970x550](https://images.ctfassets.net/alneenqid6w5/2oy6tDlTCV5xKtYinxqr3G/9f13547ee20c96383f18e8151f98177e/mercado-livre-reproducao-w-970x550.jpg)
 
 O marketplace do Mercado Livre oferece um ambiente de negociação on-line totalmente automatizado, organizado por tópicos e fácil de usar. Esse serviço oferece aos compradores uma grande variedade de itens novos e usados, permitindo que empresas e indivíduos anunciem itens e realizem suas vendas e compras no maior mercado da América Latina.
 
diff --git a/docs/tracks/pt/merchandising-rules.md b/docs/tracks/pt/merchandising-rules.md
index 3e3cceb25..2e53defd2 100644
--- a/docs/tracks/pt/merchandising-rules.md
+++ b/docs/tracks/pt/merchandising-rules.md
@@ -32,7 +32,7 @@ No Admin VTEX, a página **Storefront** > **Intelligent Search** > **Regras de m
 * [Editar regra de merchandising](#editar-regras-de-merchandising)
 * [Excluir regra de merchandising](#excluir-regras-de-merchandising)
 
-![regras-merch-pt](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/725d7d991d98ca633d7efd56ec14a254/regras-merch-pt.PNG)
+![regras-merch-pt](https://images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/725d7d991d98ca633d7efd56ec14a254/regras-merch-pt.PNG)
 
 | Coluna | Descrição |
 | - | - |
diff --git a/docs/tracks/pt/monitor-da-integracao.md b/docs/tracks/pt/monitor-da-integracao.md
index d12500080..f97b4c67e 100644
--- a/docs/tracks/pt/monitor-da-integracao.md
+++ b/docs/tracks/pt/monitor-da-integracao.md
@@ -20,7 +20,7 @@ Quando o ERP envia as mensagens ao e-commerce, estas são enviadas em **LOTE** c
 
 Em alguns casos, um registro pode ser quebrado em partes para ser enviado corretamente para **VTEX**. Exemplo: o método de atualização de estoque que em alguns casos envia também o preço. Neste caso, o adaptador gera um registro para o estoque e outro registro para o preço, como ilustrado abaixo:
 
-![aa1-adaptador](//images.contentful.com/alneenqid6w5/6vuuIwtsVdgG9Qg1xKwQag/02b250ab85f489bda094ea042ddd24c5/aa1-adaptador.png)
+![aa1-adaptador](https://images.contentful.com/alneenqid6w5/6vuuIwtsVdgG9Qg1xKwQag/02b250ab85f489bda094ea042ddd24c5/aa1-adaptador.png)
 
 ## Usando o monitor de integração
 
@@ -36,16 +36,16 @@ Na área de filtros você pode:
 - Filtrar pela Operação executada. Exemplos: **AtualizaPreco**, **AtualizaEstoque**, **AtualizaPrecoArmazem**, **Comprador**, **confirmaComprador**.
 - Filtrar pelo Status da troca de mensagens. Exemplo: somente apresentar as mensagens que apresentaram erro no sincronismo com a VTEX.
 
-![loginformacoeslote-adaptador](//images.contentful.com/alneenqid6w5/dxiurfl0kbtKnxiQCOb4K/e5ed3deb0bfed3c9fcbef65b232f86a4/loginformacoeslote-adaptador.png)
+![loginformacoeslote-adaptador](https://images.contentful.com/alneenqid6w5/dxiurfl0kbtKnxiQCOb4K/e5ed3deb0bfed3c9fcbef65b232f86a4/loginformacoeslote-adaptador.png)
 
 - Você pode acompanhar a quantidade de registros processados em cada lote, olhando as colunas de **Pendentes** (registros que ainda não foram processados pela VTEX), **Sucesso** (Registros processados pela VTEX com sucesso), **Erro** (registros que apresentaram falha no processamento pela VTEX).
 - Você pode fazer download do arquivo XML do lote que foi enviado pelo ERP clicando no link **Baixar XML**.
 - Clicando no link registro, você pode consultar os registros que foram enviado no lote.
 
-![loteRegistro-adaptador](//images.contentful.com/alneenqid6w5/3ksmvOO1wYuDbj9p5nEFUr/71d3d9d7c9ea8ba9e9329b9d5a3f02c1/loteRegistro-adaptador.png)
+![loteRegistro-adaptador](https://images.contentful.com/alneenqid6w5/3ksmvOO1wYuDbj9p5nEFUr/71d3d9d7c9ea8ba9e9329b9d5a3f02c1/loteRegistro-adaptador.png)
 
 - Você pode filtrar a lista pelo conteúdo da mensagem retornada através do campo **Palavras Chave na Mensagem**.
 - Você pode ordenar as linhas do relatório clicando no nome da coluna desejada. Ex: ordenar a coluna de **Status**.
 - Você pode clicar nos links da coluna de **Detalhes** para visualizar o `JSON` enviado pela VTEX e o retorno oferecido pela VTEX.
 
-![detalhesregistros-adaptador](//images.contentful.com/alneenqid6w5/66la9GGlwZFkkApkolMuL9/beb4a6710d5fc799c8e2aba570c8fb31/detalhesregistros-adaptador.png)
+![detalhesregistros-adaptador](https://images.contentful.com/alneenqid6w5/66la9GGlwZFkkApkolMuL9/beb4a6710d5fc799c8e2aba570c8fb31/detalhesregistros-adaptador.png)
diff --git a/docs/tracks/pt/netshoes-marketplace.md b/docs/tracks/pt/netshoes-marketplace.md
index f9b290425..9611d1595 100644
--- a/docs/tracks/pt/netshoes-marketplace.md
+++ b/docs/tracks/pt/netshoes-marketplace.md
@@ -20,6 +20,6 @@ A [Netshoes](https://www.netshoes.com.br/) é o maior e-commerce de lifestyle es
 
 Lojas que operam no Brasil podem usar a integração nativa com o Marketplace da Netshoes para expor e vender produtos de categorias como Calçados, Roupas, Acessórios, Equipamentos, Suplementos, Beleza e Eletrônicos. 
 
-![Netshoes Marketplace - Passo a Passo](//images.ctfassets.net/alneenqid6w5/4l5uEyMSlfB55VHEmbm1sD/0bb6d4d15b6b7f586de32c899e208e2e/Screen_Shot_2020-06-04_at_23.24.51.png)
+![Netshoes Marketplace - Passo a Passo](https://images.ctfassets.net/alneenqid6w5/4l5uEyMSlfB55VHEmbm1sD/0bb6d4d15b6b7f586de32c899e208e2e/Screen_Shot_2020-06-04_at_23.24.51.png)
 
 Antes de começar, é importante que você cadastre sua loja no [Netshoes Marketplace](https://www.netshoes.com.br/marketplace), aguarde a aprovação e prepare os documentos solicitados para preparação do seu contrato. Uma vez cadastrado, você poderá seguir os passos deste tutorial para montar seu catálogo e começar a vender.
diff --git a/docs/tracks/pt/opening-tickets.md b/docs/tracks/pt/opening-tickets.md
index 5255027f6..bf4ef83af 100644
--- a/docs/tracks/pt/opening-tickets.md
+++ b/docs/tracks/pt/opening-tickets.md
@@ -20,7 +20,7 @@ O acesso a uma conta VTEX possibilita acessar o [painel de suporte](https://supp
 - Acessando qualquer página do [Help Center](https://help.vtex.com/) e clicando em `Suporte`, no topo, ou em `Entrar em contato` no canto inferior da página.
 - Acessando o Admin VTEX, clicando no ícone interrogação `?` de **Central de Informações** e escolhendo a opção **Fale com nossos especialistas**.
 
-![Support imagem 1 - PT](//images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/8b56af5455d0c5ce1879a98aaa6b6768/support_imagem1_PT.gif)
+![Support imagem 1 - PT](https://images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/8b56af5455d0c5ce1879a98aaa6b6768/support_imagem1_PT.gif)
 
 <div class = "alert alert-info">
 Para obter mais informações sobre como abrir um chamado e sobre tipos de chamado, basta acessar o artigo <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex">Abrir chamados para o suporte VTEX</a>.
diff --git a/docs/tracks/pt/order-delivery.md b/docs/tracks/pt/order-delivery.md
index dbef57750..fa0ec4adf 100644
--- a/docs/tracks/pt/order-delivery.md
+++ b/docs/tracks/pt/order-delivery.md
@@ -23,7 +23,7 @@ Veja dois exemplos desse cenário:
 
 Nesse caso, é comum que os itens partam do estoque de um Centro de Distribuição, conforme ilustrado abaixo.
 
-![PT Conceitos Logística](//images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
+![PT Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
 
 Outra possibilidade de entrega que pode otimizar a operação e reduzir custos é implementar a estratégia [Ship From Store](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/50GAmxxFsJoLWqcnMysWdl), para que os itens também possam ser enviados a partir do estoque das lojas físicas.
 
diff --git a/docs/tracks/pt/order-flow.md b/docs/tracks/pt/order-flow.md
index 391579689..d803ce08d 100644
--- a/docs/tracks/pt/order-flow.md
+++ b/docs/tracks/pt/order-flow.md
@@ -33,7 +33,7 @@ Toda loja que vende produtos em seu próprio ambiente e realiza suas próprias e
 
 ## Fluxo do pedido no Marketplace
 
-![Screen Shot Fluxo de Marketplace](//images.ctfassets.net/alneenqid6w5/51d58fXMpuxCTqFCyLkdaV/21d945a4e3d519e1500a8b73f7c24c02/Screen_Shot_Fluxo_de_Marketplace.png)
+![Screen Shot Fluxo de Marketplace](https://images.ctfassets.net/alneenqid6w5/51d58fXMpuxCTqFCyLkdaV/21d945a4e3d519e1500a8b73f7c24c02/Screen_Shot_Fluxo_de_Marketplace.png)
 
 Ocorre quando a loja atua apenas como Marketplace no pedido. Ou seja, quando a loja vende produtos de outra loja - seu Seller.
 
@@ -47,7 +47,7 @@ Então, o despacho é autorizado e logo em seguida entra-se no status `Carência
 
 ## Fluxo do pedido no Seller
 
-![screenshoot fluxo seller PT](//images.ctfassets.net/alneenqid6w5/19xYHIDMJf3wClpHAnTwuf/8adf145a324fdbc36db70785f55675c0/screenshoot_fluxo_seller_PT.JPG)
+![screenshoot fluxo seller PT](https://images.ctfassets.net/alneenqid6w5/19xYHIDMJf3wClpHAnTwuf/8adf145a324fdbc36db70785f55675c0/screenshoot_fluxo_seller_PT.JPG)
 
 Ocorre quando a loja atua como Seller. Ou seja, quando ela é a dona do produto.
 
@@ -61,7 +61,7 @@ O próximo status é então o de `Preparando entrega`, quando o Seller prepara a
 
 ## Fluxo completo do pedido
 
-![Screen Shot Fluxo completo](//images.ctfassets.net/alneenqid6w5/7A1IWqoCQw4INm34u6lOWF/f21882fb0c337fbaf2ebb462ebb197f7/Screen_Shot_Fluxo_completo.png)
+![Screen Shot Fluxo completo](https://images.ctfassets.net/alneenqid6w5/7A1IWqoCQw4INm34u6lOWF/f21882fb0c337fbaf2ebb462ebb197f7/Screen_Shot_Fluxo_completo.png)
 
 Ocorre quando a loja é ao mesmo tempo Marketplace e Seller. Ou seja, é quando o pedido foi fechado na loja e a própria loja é a dona do produto, sendo responsável pelo fulfillment.
 
diff --git a/docs/tracks/pt/other-vtex-module-settings.md b/docs/tracks/pt/other-vtex-module-settings.md
index 61490fa10..c80f38512 100644
--- a/docs/tracks/pt/other-vtex-module-settings.md
+++ b/docs/tracks/pt/other-vtex-module-settings.md
@@ -78,7 +78,7 @@ O [VTEX DO](https://help.vtex.com/pt/tutorial/vtex-do-interface--7KMbRL4OslN8DTX
 - Acesso a detalhes e informações para conclusão de cada tarefa.
 - Atribuição de [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) responsável pela tarefa.
 
-![vtex-do-pt](//images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/61ec58213dff43bd94d98b757087249d/next_steps_image12_PT.JPG)
+![vtex-do-pt](https://images.ctfassets.net/alneenqid6w5/3E0pKwhLDI9VjAUPsPgykJ/61ec58213dff43bd94d98b757087249d/next_steps_image12_PT.JPG)
 
 ### VTEX Social Selling
 
diff --git a/docs/tracks/pt/payment.md b/docs/tracks/pt/payment.md
index e73683d23..028e312cf 100644
--- a/docs/tracks/pt/payment.md
+++ b/docs/tracks/pt/payment.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Na etapa de pagamento do VTEX Sales App, aparecerão as [opções de pagamento que foram configuradas](https://help.vtex.com/pt/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy) na sua loja.
 
-![instore-payment-pt](//images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/fd64b98d229c0079b017f9e926306b13/original_31f07de6-319b-454b-8c64-62dcc8ccc736_Screenshot_20220926-142455_instore.jpg)
+![instore-payment-pt](https://images.ctfassets.net/alneenqid6w5/1Kka7eQvf03YXWR5DA2NEJ/fd64b98d229c0079b017f9e926306b13/original_31f07de6-319b-454b-8c64-62dcc8ccc736_Screenshot_20220926-142455_instore.jpg)
 
 A barra superior da tela de pagamento exibe as opções a seguir:
 
@@ -45,7 +45,7 @@ Para configurar um método de pagamento, siga as instruções da track [VTEX Sal
 
 O cliente deve selecionar a opção **Dinheiro** e clicar em `Finalizar venda`. 
 
-![instore-dinheiro-pt](//images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/1baf8b97937e9f9b627f0122598c382b/original_f0a5c2c8-72da-4961-b146-380416922fb4_Screenshot_20220926-142511_instore.jpg)
+![instore-dinheiro-pt](https://images.ctfassets.net/alneenqid6w5/1Tz1XMpd6ObLZbyBcluOti/1baf8b97937e9f9b627f0122598c382b/original_f0a5c2c8-72da-4961-b146-380416922fb4_Screenshot_20220926-142511_instore.jpg)
 
 Após isso, o cliente deve realizar a transação com o vendedor. A aprovação da venda pode ser [manual ou automática](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), dependendo da configuração da loja.
 
@@ -53,21 +53,21 @@ Após isso, o cliente deve realizar a transação com o vendedor. A aprovação
 
 O cliente deve selecionar a opção **Pix** e clicar em `Finalizar venda`. 
 
-![instore-pix-pt](//images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/caf7224236509a0d185a680af077cfb6/image.png)
+![instore-pix-pt](https://images.ctfassets.net/alneenqid6w5/1A1uD4bC5JfDii4ih7gdED/caf7224236509a0d185a680af077cfb6/image.png)
 
 Após finalizar a venda, será exibido o QR Code na tela do VTEX Sales App. O cliente deve escanear esse QR Code com o celular para realizar o pagamento. 
 
-![instore-pix2-pt](//images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/cc329d7a9d6c46f61292fe5255a1cc0b/image.png)
+![instore-pix2-pt](https://images.ctfassets.net/alneenqid6w5/3hZIPLWRJoOPnh5Pw5N8vK/cc329d7a9d6c46f61292fe5255a1cc0b/image.png)
 
 Depois que o cliente realizar o pagamento, a venda será processada e, por fim, confirmada na página do pedido, conforme a imagem abaixo.
 
-![instore-pix3-pt](//images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/31173482d2636ba795335dd542e97818/image.png)
+![instore-pix3-pt](https://images.ctfassets.net/alneenqid6w5/4lRaRqYX4eqB07IMj7IGay/31173482d2636ba795335dd542e97818/image.png)
 
 ### Boleto bancário
 
 O cliente deve selecionar a opção **Boleto Bancário** e clicar em `Finalizar venda`. 
 
-![instore-boleto-pt](//images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/ebcafe3b1d49b11780d1587e9ff2d2d6/Screenshot_20220926-142519_instore__1_.jpg)
+![instore-boleto-pt](https://images.ctfassets.net/alneenqid6w5/3OonA4B8NNyKrINN0SY2Q/ebcafe3b1d49b11780d1587e9ff2d2d6/Screenshot_20220926-142519_instore__1_.jpg)
 
 O boleto será enviado para o email do cliente. Uma vez que o pagamento do boleto for confirmado, a venda será confirmada. 
 
@@ -75,7 +75,7 @@ O boleto será enviado para o email do cliente. Uma vez que o pagamento do bolet
 
 O cliente deve selecionar a opção **Cartão de crédito**, selecionar a quantidade de parcelas da compra e clicar em `Finalizar venda`. 
 
-![instore-credito-pt](//images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/21a3fa6635db72c129ba08e7f7ceb56f/Screenshot_20220926-143755_instore.jpg)
+![instore-credito-pt](https://images.ctfassets.net/alneenqid6w5/4GGFgdlEpYIKYbdjG74C4g/21a3fa6635db72c129ba08e7f7ceb56f/Screenshot_20220926-143755_instore.jpg)
 
 O VTEX Sales App exibirá uma tela de espera enquanto o pagamento é realizado na máquina de cartão da loja. Uma vez que o pagamento é reconhecido pelo sistema, a venda será confirmada.
 
@@ -83,7 +83,7 @@ O VTEX Sales App exibirá uma tela de espera enquanto o pagamento é realizado n
 
 O cliente deve selecionar a opção **Cartão de débito** e clicar em `Finalizar venda`. 
 
-![instore-debito-pt](//images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4ac0e0e71fe105df9c93d5d068d5cd98/Screenshot_20220926-142524_instore__1_.jpg)
+![instore-debito-pt](https://images.ctfassets.net/alneenqid6w5/6XEmL7UR7K7L3YdfsPLY8q/4ac0e0e71fe105df9c93d5d068d5cd98/Screenshot_20220926-142524_instore__1_.jpg)
 
 O VTEX Sales App exibirá uma tela de espera enquanto o pagamento é realizado na máquina de cartão da loja. Uma vez que o pagamento é reconhecido pelo sistema, a venda será confirmada.
 
diff --git a/docs/tracks/pt/planning-the-go-live.md b/docs/tracks/pt/planning-the-go-live.md
index 93b72d860..1b62d83f8 100644
--- a/docs/tracks/pt/planning-the-go-live.md
+++ b/docs/tracks/pt/planning-the-go-live.md
@@ -34,7 +34,7 @@ O processo para realizar o go-live de uma loja, incluindo as configurações e t
 
 A imagem a seguir apresenta as etapas de planejamento envolvidas no go-live de uma loja VTEX:
 
-![go-live-pt](//images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/a758f107911697856c856d70192d2912/go-live-pt.png)
+![go-live-pt](https://images.ctfassets.net/alneenqid6w5/3AA13R58ffQhNjBBoJm2kS/a758f107911697856c856d70192d2912/go-live-pt.png)
 
 ### Definir MVP
 
@@ -54,7 +54,7 @@ Nesse caso, portanto, todo o processo de planejamento precisa iniciar no mínimo
 
 Para organizar as equipes envolvidas e realizar o go-live na data desejada, é importante criar um _roadmap_, ou seja, um documento com o roteiro de ações necessárias para o go-live, indicando os responsáveis por cada etapa e os prazos acordados. A imagem a seguir mostra um exemplo de cronograma:
 
-![golive 2 PT](//images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/a15338a9461674d2069c56d02388f742/golive_2_PT.png)
+![golive 2 PT](https://images.ctfassets.net/alneenqid6w5/Z0MHCvHc0dMND8dOCk7JJ/a15338a9461674d2069c56d02388f742/golive_2_PT.png)
 
 Recomendamos planejar reuniões periódicas com as [equipes de implementação](warm-up-heading-parceiros-de-implementacao) para manter um alinhamento frequente e, se necessário, criar uma _war room_ para resolver assuntos pendentes na semana que antecede o go-live.
 
diff --git a/docs/tracks/pt/preco-base-definicao-de-conceito.md b/docs/tracks/pt/preco-base-definicao-de-conceito.md
index c850f30c1..47804b0ea 100644
--- a/docs/tracks/pt/preco-base-definicao-de-conceito.md
+++ b/docs/tracks/pt/preco-base-definicao-de-conceito.md
@@ -18,7 +18,7 @@ trackSlugPT: precos-101
 
 Preço Base de um SKU é o valor calculado através da combinação entre o **Preço de Custo** e o **Markup**, a margem de lucro desejada com a venda do SKU. É o __preço de referência__ de um SKU para todas as tabelas de preço. 
 
-![base-price-pt](//images.ctfassets.net/alneenqid6w5/5tamTR4dro1URUdIvMkp93/f5103d68e1230e853496b49a9211852e/base-price-pt.png)
+![base-price-pt](https://images.ctfassets.net/alneenqid6w5/5tamTR4dro1URUdIvMkp93/f5103d68e1230e853496b49a9211852e/base-price-pt.png)
 
 Esse **preço base** pode ser combinado com uma **regra de preço** aplicada à tabela de preços. Caso não exista regra de preço cadastrada, o preço de venda em uma tabela será o próprio preço base.
 
diff --git a/docs/tracks/pt/preco-fixo-definicao-de-conceito.md b/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
index f55ece39a..a60b9918d 100644
--- a/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
@@ -73,7 +73,7 @@ Digamos que dois preços fixos sejam cadastrados para o mesmo SKU. Além disso,
 
 Por exemplo: o primeiro preço fixo é de __R$ 50,00__ e seu agendamento vai das __10h às 16h__. Já o segundo é de __R$ 25,00__, só que está programado das __12h às 20h do mesmo dia__. Neste caso, *entre 12h e 16h*, os dois preços fixos competem entre si. Desse modo, o valor de __R$ 25,00__ será o preço de venda do SKU neste horário em comum.
 
-![fixed price - example2](//images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
+![fixed price - example2](https://images.ctfassets.net/alneenqid6w5/1GR4ZZSlxREEGHno3VXorQ/b014a5ed36bf608e9f582775ca06e507/fixed_price_-_example2.svg)
 
 ### Concorrência pelo critério de Itens mínimos no carrinho
 
@@ -83,7 +83,7 @@ Imagine que cadastramos um preço fixo de R$ 200,00 para __dois ou mais itens no
 
 Qual seria o preço aplicado para 5 ou mais itens? O preço de venda será de R$ 100,00, visto que o sistema prioriza o menor valor.
 
-![fixed price - example1](//images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
+![fixed price - example1](https://images.ctfassets.net/alneenqid6w5/60d7Vr6w08B8XZt9FCk4AG/8a577583a2df4290c2acfaa08b97b71f/fixed_price_-_example1.svg)
 
 ## Exemplos
 
diff --git a/docs/tracks/pt/pricing-system-architecture.md b/docs/tracks/pt/pricing-system-architecture.md
index 34ead7a2d..16746589f 100644
--- a/docs/tracks/pt/pricing-system-architecture.md
+++ b/docs/tracks/pt/pricing-system-architecture.md
@@ -50,7 +50,7 @@ O módulo de preços considera 4 critérios para calcular o preço computado par
 
 2. Se o SKU tiver uma *regra de preço* configurada para uma determinada tabela de preços, o preço computado será igual ao **preço-base modificado pela regra de preço**.![enter image description here](https://images.ctfassets.net/alneenqid6w5/7k9mOk5hOngCaAvzn0c7Wt/89fedbfc75f32e977bf75509f4c7d1fa/rule2.svg)
 
-3. Em um outro cenário, vamos considerar um SKU com *preço-base*, *regra de preço* e *arredondamento de preços*. **O preço computado para uma determinada tabela de preço será calculado por uma combinação entre esses três fatores**. Primeiro, o preço base será modificado pela regra de preço. Depois disso, ocorrerá o arredondamento pela regra de preço psicológico.![rule3-pt](//images.ctfassets.net/alneenqid6w5/3hpO858nn2Ln3rWizXP5uS/7b66e899d6ac3bbac7e5f1d53b814652/rule3.svg)
+3. Em um outro cenário, vamos considerar um SKU com *preço-base*, *regra de preço* e *arredondamento de preços*. **O preço computado para uma determinada tabela de preço será calculado por uma combinação entre esses três fatores**. Primeiro, o preço base será modificado pela regra de preço. Depois disso, ocorrerá o arredondamento pela regra de preço psicológico.![rule3-pt](https://images.ctfassets.net/alneenqid6w5/3hpO858nn2Ln3rWizXP5uS/7b66e899d6ac3bbac7e5f1d53b814652/rule3.svg)
 
 4. Por fim, se um SKU tiver um *preço fixo* cadastrado, **o preço computado para uma determinada tabela de preços será igual ao preço fixo**. Este preço tem um peso superior aos outros preços. Desta maneira, o módulo de preços *ignora os outros preços* caso encontre um preço fixo associado a um SKU.![enter image description here](https://images.ctfassets.net/alneenqid6w5/1ztpeUQ5BDqR5ZTLtVAEia/e7472b2be59efd63dbd04faf90e312b3/rule4.svg)
 
diff --git a/docs/tracks/pt/printing-an-order-summary.md b/docs/tracks/pt/printing-an-order-summary.md
index b80199e36..22736dc52 100644
--- a/docs/tracks/pt/printing-an-order-summary.md
+++ b/docs/tracks/pt/printing-an-order-summary.md
@@ -18,7 +18,7 @@ Ao concluir um pedido pelo VTEX Sales App, é possível imprimir um resumo do pe
 
 Para isso, o vendedor pode clicar no botão `Imprimir Pedido`, na tela de pedido finalizado, conforme ilustrado abaixo. Outra opção é configurar o VTEX Sales App para imprimir o resumo do pedido automaticamente, assim que o pedido for finalizado.
 
-![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/30253b60272652b911a9dfd03c9fe8ae/Group_1.png)
+![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/30253b60272652b911a9dfd03c9fe8ae/Group_1.png)
 
 Para habilitar a impressão do resumo do pedido, é necessário seguir as etapas descritas abaixo.
 
@@ -50,13 +50,13 @@ Com o AppKey e o AppToken em mãos, siga os passos abaixo.
 2. Abra o aplicativo do VTEX Sales App e informe o nome da loja onde você deseja configurar a impressora.
 3. No menu principal do VTEX Sales App, na seção **Configurações**, clique na opção <i class="fas fa-cog"></i> **Configurar o dispositivo**, ilustrada abaixo.
 
-![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/8a5a3ec9f8a845292f549bbaf3831756/Group_2.png)
+![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/8a5a3ec9f8a845292f549bbaf3831756/Group_2.png)
 
 <ol start="4">
   <li>Em seguida, você verá o resumo do dispositivo configurado. Se essa for a primeira vez em que essa configuração é realizada, os campos da tela estarão vazios, conforme a imagem abaixo. Se um dispositivo já tiver sido configurado anteriormente, você verá o <b>Nome do dispositivo</b> e <b>Impressora padrão</b>. Clique no botão <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4" style="word-break: break-word; overflow-wrap: break-word;">Editar</span>.</li>
 </ol>
 
-![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 <ol start="5">
   <li>Preencha o formulário contendo os campos descritos abaixo.
diff --git a/docs/tracks/pt/product-details.md b/docs/tracks/pt/product-details.md
index b9477961b..7051411d6 100644
--- a/docs/tracks/pt/product-details.md
+++ b/docs/tracks/pt/product-details.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Ao clicar nos detalhes de um produto que aparece nos resultados da busca do VTEX Sales App, ou ao bipar um produto, o vendedor é direcionado à tela de detalhes do produto.
 
-![instore-pdp-pt](//images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/91062ff9c3840a3095bb96b36dc73136/pdp-pt.png)
+![instore-pdp-pt](https://images.ctfassets.net/alneenqid6w5/fSLOfLn7bnpFyAfujZ8GN/91062ff9c3840a3095bb96b36dc73136/pdp-pt.png)
 
 Essa tela mostra o nome do produto, sua galeria de fotos, variações, descrição e disponibilidade. O vendedor pode, nessa tela, adicionar o produto ao carrinho.
 
diff --git a/docs/tracks/pt/promotions-for-specific-scenarios.md b/docs/tracks/pt/promotions-for-specific-scenarios.md
index 93df9d5f0..857b7d4c4 100644
--- a/docs/tracks/pt/promotions-for-specific-scenarios.md
+++ b/docs/tracks/pt/promotions-for-specific-scenarios.md
@@ -38,7 +38,7 @@ A tela de configuração da promoção oferece duas listas de SKUs, que podem se
 
 Você pode, então, definir um valor de desconto para a cada uma dessas listas. Se, por exemplo, a lista 1 tem 10% de desconto e a lista 2 tem 5% de desconto, quando o carrinho tiver pelo menos um produto de cada uma dessas listas, será concedido um total de 10% sobre o valor dos itens da lista 1 e um desconto de 5% sobre o valor dos itens da lista 2.
 
-![5 1](//images.ctfassets.net/alneenqid6w5/365uWey6OG9w1jMlIbi11L/108d507cd3957a5e9c6b128cd920d543/5_1.png)
+![5 1](https://images.ctfassets.net/alneenqid6w5/365uWey6OG9w1jMlIbi11L/108d507cd3957a5e9c6b128cd920d543/5_1.png)
 
 Dois exemplos desse tipo de promoção seriam "Compre uma calça e ganhe 10% na compra de um cinto" e "Compre um par de tênis + um par de meias e ganhe 15% de desconto".
 
@@ -50,7 +50,7 @@ A promoção do tipo Leve Mais por Menos é usada para conceder desconto quando
 
 Na configuração da promoção Leve Mais por Menos, a loja deve definir a quais coleções ou SKUs ela será aplicada. Em seguida, escolha o número de itens no carrinho para ela funcionar e o número de itens com desconto.
 
-![Leve mais por menos](//images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/88a65536af3f8ee11f7fb7881056176b/Promo__es.png)
+![Leve mais por menos](https://images.ctfassets.net/alneenqid6w5/5LQErZWrN4WyX8ZuIBEMPM/88a65536af3f8ee11f7fb7881056176b/Promo__es.png)
 
 Por exemplo:
 - A cada `3` produtos, o cliente levará `1` produto `grátis`.
@@ -68,7 +68,7 @@ Na configuração da promoção de Desconto Progressivo, a loja deve definir a q
 
 Para continuar a progressão do desconto, clique no botão de "+". Uma nova linha será adicionada, e então você poderá adicionar um novo desconto. Por exemplo: para os próximos 2 produtos, o cliente receberá mais 5% de desconto. E assim por diante.
 
-![5 3](//images.ctfassets.net/alneenqid6w5/28KPsHCVKBF9ZgRUzwHudZ/81dcb7a88df530c81a8468e572aec43c/5_3.png)
+![5 3](https://images.ctfassets.net/alneenqid6w5/28KPsHCVKBF9ZgRUzwHudZ/81dcb7a88df530c81a8468e572aec43c/5_3.png)
 
 Para entender a promoção de Desconto Progressivo em mais detalhes, veja o artigo [Como funciona o desconto progressivo](https://help.vtex.com/pt/tutorial/desconto-progressivo--tutorials_324).
 
@@ -78,7 +78,7 @@ A promoção do tipo Compre e Ganhe é usada para oferecer frete grátis ou um b
 
 O desconto aplicado (frete grátis ou brinde) deve ser definido nos dados gerais da promoção. Depois, a loja deve escolher as coleções ou SKUs aos quais ela será aplicada. E, por fim, deve definir a quantidade mínima de itens no carrinho para a promoção funcionar.
 
-![5 4](//images.ctfassets.net/alneenqid6w5/59ir5nkFky3fqbvr6fh4ht/156bd36222aaf26eeae18644e8ef2075/5_4.png)
+![5 4](https://images.ctfassets.net/alneenqid6w5/59ir5nkFky3fqbvr6fh4ht/156bd36222aaf26eeae18644e8ef2075/5_4.png)
 
 Para entender a promoção do tipo Compre e Ganhe em mais detalhes, veja o artigo [Como funciona a promoção Compre e Ganhe](https://help.vtex.com/pt/tutorial/compre-e-ganhe--tutorials_322).
 
@@ -92,22 +92,22 @@ Esta configuração define quantos itens do carrinho serão afetados pela promo
 
 Depois de preencher todos [os campos de uma promoção regular](https://help.vtex.com/pt/tutorial/regular-promotion--tutorials_327) com desconto percentual, você pode selecionar a opção __Definir quantidade máxima de itens afetados por carrinho__ na seção __Restrições e limites de uso__.
 
-![Limite itens - PT](//images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/efa4913d768b6c60a738ade38b36250c/Limite_itens_-_PT.png)
+![Limite itens - PT](https://images.ctfassets.net/alneenqid6w5/1W6ZYterIepCud41XJr4UQ/efa4913d768b6c60a738ade38b36250c/Limite_itens_-_PT.png)
 
 Por default, a seleção __ilimitado__ está ativa, aplicando a promoção em todos os itens do carrinho, como ilustrado no diagrama abaixo:
 
-![Caso ilimitado - PT](//images.ctfassets.net/alneenqid6w5/ryqePV18B6yVGLoUnqHdg/406ea14fc3a931027876309e46cb6afa/Caso_ilimitado.png)
+![Caso ilimitado - PT](https://images.ctfassets.net/alneenqid6w5/ryqePV18B6yVGLoUnqHdg/406ea14fc3a931027876309e46cb6afa/Caso_ilimitado.png)
 
 Para restringir o número de itens do carrinho que receberão o desconto, você pode escolher entre uma das seguintes opções:
 
 - __Itens por carrinho__: essa configuração limita a aplicação da promoção a um número de itens do carrinho. Assim que o limite for atingido, a promoção não será aplicada para o restante do carrinho. O sistema utiliza o preço como critério de escolha, dessa forma, os itens com preço menor serão os primeiros a serem afetados.
 
-![Caso por item - PT](//images.ctfassets.net/alneenqid6w5/7yXbUrBWdqkcWyvXaLa7Hc/5de06c1250b310850722f31a63c36418/Caso_por_item.png)
+![Caso por item - PT](https://images.ctfassets.net/alneenqid6w5/7yXbUrBWdqkcWyvXaLa7Hc/5de06c1250b310850722f31a63c36418/Caso_por_item.png)
 
 - __Itens por produto__: essa configuração limita a promoção a um número de unidades de cada produto. Como no exemplo abaixo, apenas duas unidades por produto serão elegíveis para a promoção. O preço mais baixo define os itens de cada produto elegíveis para a promoção.
 
-![Caso por produto - PT](//images.ctfassets.net/alneenqid6w5/55wWvZwHyjvrfk01vA9PRX/972beb813354aafcfa65c25ae5d37135/Caso_por_produto.png)
+![Caso por produto - PT](https://images.ctfassets.net/alneenqid6w5/55wWvZwHyjvrfk01vA9PRX/972beb813354aafcfa65c25ae5d37135/Caso_por_produto.png)
 
 - __Itens por SKU__: essa configuração limita a promoção a um número de unidades para cada SKU no carrinho. Como no exemplo abaixo, apenas duas unidades de cada SKU serão elegíveis para a promoção. Assim como no caso anterior, será o preço mais baixo que definirá os itens elegíveis para a promoção.
 
-![Caso por SKU - PT](//images.ctfassets.net/alneenqid6w5/2UCLkXZNHNKJtecRIeoYuF/c73bd02637a38ed2693ba5d2f74a8efa/Caso_por_SKU.png)
+![Caso por SKU - PT](https://images.ctfassets.net/alneenqid6w5/2UCLkXZNHNKJtecRIeoYuF/c73bd02637a38ed2693ba5d2f74a8efa/Caso_por_SKU.png)
diff --git a/docs/tracks/pt/rappi-integration-overview.md b/docs/tracks/pt/rappi-integration-overview.md
index 87d399920..7d9a9930f 100644
--- a/docs/tracks/pt/rappi-integration-overview.md
+++ b/docs/tracks/pt/rappi-integration-overview.md
@@ -16,7 +16,7 @@ trackSlugPT: integracao-rappi
 
 A Rappi é uma plataforma que funciona como marketplace conectando compradores a produtos dos mais diversos segmentos. Acompanhando a experiência do cliente da compra à entrega.
 
-![Logo Rappi](//images.ctfassets.net/alneenqid6w5/INsIz4tJzR7MR8JsKPKjt/4264529e186ed1aa18d6e75352719dfe/logo-rappi.jpg)
+![Logo Rappi](https://images.ctfassets.net/alneenqid6w5/INsIz4tJzR7MR8JsKPKjt/4264529e186ed1aa18d6e75352719dfe/logo-rappi.jpg)
 
 A configuração com a Rappi tem o objetivo conectar sua loja VTEX com a plataforma, permitindo que você anuncie seus produtos, aumente suas vendas e alcance novos clientes a partir deste canal.
 
diff --git a/docs/tracks/pt/relevance.md b/docs/tracks/pt/relevance.md
index c5828b81e..fa471b97b 100644
--- a/docs/tracks/pt/relevance.md
+++ b/docs/tracks/pt/relevance.md
@@ -23,7 +23,7 @@ Existem dois cenários possíveis de configurações de relevância:
 - **Critérios prioritários:** é a forma de forçar que um ou mais critérios terão prioridade maior entre os demais. Nessa situação não existem pesos, pois todos os produtos que possuírem essa característica serão apresentados primeiro no resultado de busca.
 - **Composição de critérios:** é a forma de distribuir pesos para cada opção, variando de 0 a 10. Aqui, não existe uma ordem entre os critérios, serão os pesos que vão definir a relevância.
 
-![criterios-pt](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/faefb674583084511a114faf0c39cdbd/criterios-pt.png)
+![criterios-pt](https://images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/faefb674583084511a114faf0c39cdbd/criterios-pt.png)
 
 As informações aplicadas para compor a relevância são:
 
@@ -109,5 +109,5 @@ Para alterar a configuração de relevância, siga os passos abaixo.
 
    Caso você queira mudar a posição de um critério de **Composição de critérios** para **Critérios prioritários**, arraste-o pelo ícone <i class="fas fa-grip-vertical"></i> para a área superior, conforme ilustrado na imagem abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso. 
 
-    ![criterios-prioritarios-pt](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/43155e1e110f6ec8eaff5debf9d8a2df/criterios-prioritarios-pt.gif)
+    ![criterios-prioritarios-pt](https://images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/43155e1e110f6ec8eaff5debf9d8a2df/criterios-prioritarios-pt.gif)
 5. Para finalizar, clique em `Salvar`.
diff --git a/docs/tracks/pt/reports-vtex-intelligent-search.md b/docs/tracks/pt/reports-vtex-intelligent-search.md
index c9e9d6742..0a4f0a70e 100644
--- a/docs/tracks/pt/reports-vtex-intelligent-search.md
+++ b/docs/tracks/pt/reports-vtex-intelligent-search.md
@@ -79,8 +79,8 @@ Para exportar um relatório no formato CSV, você deve seguir os passos abaixo.
 
 O relatório CSV baixado apresenta duas tabelas. A primeira tabela, ilustrada abaixo, contém informações sobre termos pesquisados e as métricas de funil (da coluna **ProductsClick** até a coluna **ProductsSold**), caso essa opção tenha sido selecionada.
 
-![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
+![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
 
 A segunda tabela, ilustrada abaixo, mostra dados referentes ao período selecionado, exibindo a coluna Date, que informa a data da busca.
 
-![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
+![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
diff --git a/docs/tracks/pt/sale-confirmed.md b/docs/tracks/pt/sale-confirmed.md
index 019a4f94b..863a8512f 100644
--- a/docs/tracks/pt/sale-confirmed.md
+++ b/docs/tracks/pt/sale-confirmed.md
@@ -16,4 +16,4 @@ trackSlugPT: instore-usando-o-app
 
 O vendedor pode ver a tela __Venda confirmada__ com o resumo do pedido quando terminar uma venda, ou clicando em uma venda na página __Últimas vendas__, que pode ser acessada através do menu principal do VTEX Sales App. Na página __Últimas vendas__, é possível procurar a venda pelo número do pedido ou pelo nome do cliente.
 
-![order-placed-pt](//images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/8c3cc031c6f1b86c2f6cfbc31c53c1ec/order-placed-pt.png)
+![order-placed-pt](https://images.ctfassets.net/alneenqid6w5/1WzildtkElOIkalZuY3hkI/8c3cc031c6f1b86c2f6cfbc31c53c1ec/order-placed-pt.png)
diff --git a/docs/tracks/pt/search-settings.md b/docs/tracks/pt/search-settings.md
index 9ea44356b..df945f456 100644
--- a/docs/tracks/pt/search-settings.md
+++ b/docs/tracks/pt/search-settings.md
@@ -36,7 +36,7 @@ As configurações gerais apresentam as opções a seguir, relacionadas a [espec
 
 As configurações de filtros apresentam ajustes relacionados aos filtros exibidos para os clientes da sua loja durante a busca:
 
-![Configurações de filtros](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
+![Configurações de filtros](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
 
 * **Ordenação dos filtros:** ordem em que os filtros serão exibidos na loja. Caso não tenha nenhum filtro selecionado na área, a ordem padrão é alfabética.
 
diff --git a/docs/tracks/pt/sending-products-to-amazon.md b/docs/tracks/pt/sending-products-to-amazon.md
index d0f873eb4..22feecf28 100644
--- a/docs/tracks/pt/sending-products-to-amazon.md
+++ b/docs/tracks/pt/sending-products-to-amazon.md
@@ -42,10 +42,10 @@ A lista de categorias da sua loja VTEX inclui o status de seu mapeamento por mei
 
 | **Ícone** | **Status** | **Descrição** |
 |:---:|:---:|:---:|
-| ![mapeado mapper](//images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/43ace44c1e31c69157dc8ad5ec12529d/mapeado_mapper.jpg) | **Mapeado** | Indica que o mapeamento da categoria foi concluído. |
-| ![mapeamentoincompleto mapper](//images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/3cc09ec0f77d42f3277dd90e2f3167f9/mapeamentoincompleto_mapper.jpg) | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. |
-| ![erromapeamento mapper](//images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/136543f594ca05eec7be6bfc545cd10f/erromapeamento_mapper.jpg) | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto. Para solucionar esse problema basta refazer o mapeamento da categoria. |
-| ![não mapeado mapper](//images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/79bf968ab2d73471ee6e96b41b6a75d9/incompleto_mapper.jpg) | **Não mapeado** | Indica que a categoria não foi mapeada. |  
+| ![mapeado mapper](https://images.ctfassets.net/alneenqid6w5/3ZYriZU76d9cneJceH3ljb/43ace44c1e31c69157dc8ad5ec12529d/mapeado_mapper.jpg) | **Mapeado** | Indica que o mapeamento da categoria foi concluído. |
+| ![mapeamentoincompleto mapper](https://images.ctfassets.net/alneenqid6w5/pHYXqYM9WBjmR0uYpwrFC/3cc09ec0f77d42f3277dd90e2f3167f9/mapeamentoincompleto_mapper.jpg) | **Mapeamento incompleto** | A categoria está parcialmente mapeada, necessitando preencher seus atributos obrigatórios, indicados por meio de um asterisco, para mapeá-la. |
+| ![erromapeamento mapper](https://images.ctfassets.net/alneenqid6w5/1wyY50BdeT8YA7y7XAb7Sd/136543f594ca05eec7be6bfc545cd10f/erromapeamento_mapper.jpg) | **Erro no mapeamento** | O erro no mapeamento ocorre quando o marketplace exclui ou muda a categoria do produto. Para solucionar esse problema basta refazer o mapeamento da categoria. |
+| ![não mapeado mapper](https://images.ctfassets.net/alneenqid6w5/7wXO0cZBKZD7PWbbP9y877/79bf968ab2d73471ee6e96b41b6a75d9/incompleto_mapper.jpg) | **Não mapeado** | Indica que a categoria não foi mapeada. |  
 
 Para realizar o mapeamento de categorias:  
 
@@ -54,7 +54,7 @@ Para realizar o mapeamento de categorias:
 3. Selecione a categoria correspondente na Amazon do produto que deseja enviar.  
 4. Faça a correspondência dos atributos na janela lateral, conforme imagem abaixo:  
 
-![Mapper Amazon Atributos](//downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/7724063f4b499153958aadf44ee0a704/mapper_amazon_atributos.gif)
+![Mapper Amazon Atributos](https://downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/7724063f4b499153958aadf44ee0a704/mapper_amazon_atributos.gif)
 
 5. Clique no botão __`Salvar Alterações`__.  
 
@@ -120,13 +120,13 @@ Para configurar a categoria global no seu ambiente VTEX, a partir das categorias
 #### Exemplo de consulta das planilhas 
 
 Na Planilha de atributos obrigatórios da Amazon, iremos utilizar a categoria **Health** focando em produtos para saúde:
-![categoriageral01](//images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
+![categoriageral01](https://images.contentful.com/alneenqid6w5/154htyPg3K3IZ6Wxej3kek/a446c9815c249dda3084aa1773b76b3a/categoriageral01.JPG)
 
 Na Planilha de categorias gerais da Amazon, filtre a coluna “I” Cat-Amazon-Geral, clicando em **Filtro > Health > OK**.
-![categoriageral02](//images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
+![categoriageral02](https://images.contentful.com/alneenqid6w5/2PTS1fxztRjYHaAicwVH7W/f44b94c30ca7401ec08a19c467ee8912/categoriageral02.JPG)
 
 Seguindo o exemplo anterior, filtre as colunas B, C e D da árvore de **Saúde e beleza> Cuidados pessoais > Massagem e relaxamento**.
-![categoriageral03](//images.contentful.com/alneenqid6w5/1p0cIHz7bp8HHuzud1H4zE/e79bf00cbe09f7b1fb155730cfc401f8/categoriageral03.JPG)
+![categoriageral03](https://images.contentful.com/alneenqid6w5/1p0cIHz7bp8HHuzud1H4zE/e79bf00cbe09f7b1fb155730cfc401f8/categoriageral03.JPG)
 
 Agora que você encontrou a categoria geral da Amazon, volte ao Admin para [configurar a categoria global](https://help.vtex.com/pt/tutorial/configurando-a-categoria-global--tutorials_188) da VTEX de acordo com a categoria geral da Amazon.
 
diff --git a/docs/tracks/pt/set-a-price-for-the-sku.md b/docs/tracks/pt/set-a-price-for-the-sku.md
index a010506ea..966b717ab 100644
--- a/docs/tracks/pt/set-a-price-for-the-sku.md
+++ b/docs/tracks/pt/set-a-price-for-the-sku.md
@@ -22,7 +22,7 @@ Mesmo um SKU que será oferecido como brinde precisa ter um preço cadastrado.
 
 Para cadastrar o preço, siga os passos abaixo.
 1. No módulo __Catalog__, passe o mouse sobre __Cadastro de Produtos__, vá até __Produtos e SKUs__ e clique na opção __Cadastro de Produtos e SKUs__.
-2. Na linha do SKU desejado, clique no símbolo de cifrão (você será levado ao módulo Pricing).![SKUprice1](//images.contentful.com/alneenqid6w5/2JbgHp3MuciccYsiAIqwki/ec0d7871c26758bd28d40e51f130edda/SKUprice1.png)
+2. Na linha do SKU desejado, clique no símbolo de cifrão (você será levado ao módulo Pricing).![SKUprice1](https://images.contentful.com/alneenqid6w5/2JbgHp3MuciccYsiAIqwki/ec0d7871c26758bd28d40e51f130edda/SKUprice1.png)
 3. Na coluna SKU, clique na célula com o nome do SKU.
 
 Na barra lateral que aparece à esquerda, você verá algumas informações de preço para serem preenchidas. As mais importantes são:
@@ -31,6 +31,6 @@ Na barra lateral que aparece à esquerda, você verá algumas informações de p
 
 Ao preencher esses dois valores, o sistema lhe dará automaticamente o __preço base__ do produto.
 
-![SKUprice3](//images.contentful.com/alneenqid6w5/lvdNQdSq52emikM8QGImA/801b0e9fce71acbd0f923bf3db13187c/SKUprice3.gif)
+![SKUprice3](https://images.contentful.com/alneenqid6w5/lvdNQdSq52emikM8QGImA/801b0e9fce71acbd0f923bf3db13187c/SKUprice3.gif)
 
 Agora só falta definir o estoque desse SKU para que ele fique disponível aos seus clientes.
diff --git a/docs/tracks/pt/set-the-sku-quantity-in-inventory.md b/docs/tracks/pt/set-the-sku-quantity-in-inventory.md
index 400345384..e4d5e67cb 100644
--- a/docs/tracks/pt/set-the-sku-quantity-in-inventory.md
+++ b/docs/tracks/pt/set-the-sku-quantity-in-inventory.md
@@ -18,12 +18,12 @@ Você já tem um produto associado a uma categoria e a uma marca, tem um SKU par
 
 Para cadastrar o estoque, siga os passos abaixo.
 1. No módulo __Catalog__, passe o mouse sobre __Cadastro de Produtos__, vá até __Produtos e SKUs__ e clique na opção __Cadastro de Produtos e SKUs__.
-2. Na linha do SKU desejado, clique no símbolo de caminhão (você será levado ao módulo Logistics).![SKUstock](//images.contentful.com/alneenqid6w5/5HArBLp1qoq6cyUk8Oc8mO/473c1415e082ee2c644f5ab95f24ff73/SKUstock.png)
+2. Na linha do SKU desejado, clique no símbolo de caminhão (você será levado ao módulo Logistics).![SKUstock](https://images.contentful.com/alneenqid6w5/5HArBLp1qoq6cyUk8Oc8mO/473c1415e082ee2c644f5ab95f24ff73/SKUstock.png)
 
 Você verá uma tabela com informações sobre:
 - O SKU cujo estoque você está editando.
-- As quantidades desse SKU para cada um dos seus estoques (é provável que por enquanto você tenha somente 1 estoque).![SKUstock3](//images.contentful.com/alneenqid6w5/1L6j4KnLm80OGIeamy2G6S/c0e141d79feed20965dd038e06ad21b7/SKUstock3.png)
+- As quantidades desse SKU para cada um dos seus estoques (é provável que por enquanto você tenha somente 1 estoque).![SKUstock3](https://images.contentful.com/alneenqid6w5/1L6j4KnLm80OGIeamy2G6S/c0e141d79feed20965dd038e06ad21b7/SKUstock3.png)
 
-Na coluna __Atualizar contagem__, insira a quantidade de itens do SKU. Depois, clique em __Salvar__.![SKUstock2](//images.contentful.com/alneenqid6w5/vOnvVfbYHIu6yEgoe0gwS/2de31b3086df606783c38ded788733ae/SKUstock2.gif)
+Na coluna __Atualizar contagem__, insira a quantidade de itens do SKU. Depois, clique em __Salvar__.![SKUstock2](https://images.contentful.com/alneenqid6w5/vOnvVfbYHIu6yEgoe0gwS/2de31b3086df606783c38ded788733ae/SKUstock2.gif)
 
 Pronto, seu SKU agora tem estoque e já está disponível para seus clientes.
diff --git a/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md b/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md
index f2226b64c..cfc748593 100644
--- a/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md
+++ b/docs/tracks/pt/setting-instore-up-in-a-store-easy-setup.md
@@ -26,31 +26,31 @@ Você pode encontrar links para download em: [http://instore.vtex.com/#download]
 
 Ao abrir o inStore pela primeira vez, você precisará digitar a conta VTEX onde deseja configurar o inStore e clicar em __Confirmar__.
 
-![01 inStore selecione conta](//images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
+![01 inStore selecione conta](https://images.ctfassets.net/alneenqid6w5/4XB9P7AD4ICSyWqCo0MmKA/b654a9607224ee02376f65485edbbf45/01_inStore_selecione_conta.png)
 
 Ao identificar que o inStore não está configurado nessa conta, você será redirecionado para a VTEX App Store onde precisará efetuar o login com sua conta de admin na VTEX.
 
 Após o login, você conseguirá instalar o inStore na sua conta.
 
-![02 inStore instalar](//images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
+![02 inStore instalar](https://images.ctfassets.net/alneenqid6w5/2Fb8nICP8IEk62mO8yOSKg/e7ae4a24ba325b34b90e0abd92b51e03/02_inStore_instalar.png)
 
 Um formulário de configuração será exibido, sendo a primeira etapa a informação de endereço.
 
-![03 inStore endereco](//images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
+![03 inStore endereco](https://images.ctfassets.net/alneenqid6w5/ZdkjzNMxs2iOsCCSWECQm/8c696c8f7c96894b75c68ea89acf0a3e/03_inStore_endereco.png)
 
 Depois você deve definir um email e senha a serem utilizados como login de vendedor.
 
 > __IMPORTANTE__: esse e-mail __NÃO__ pode ser o mesmo utilizado na plataforma VTEX, isso porque o seu e-mail de admin possui permissões que um vendedor não deveria ter, por isso é necessário utilizar algum outro e-mail sem privilégios na plataforma.
 
-![04 inStore registre vendedor](//images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
+![04 inStore registre vendedor](https://images.ctfassets.net/alneenqid6w5/1sWVQqJBU8aKQCcS2U8I4S/9bb4e876b020c39598d7b3ebab3cd2a1/04_inStore_registre_vendedor.png)
 
 Depois de configurar o vendedor e confirmar o código de ativação recebido por e-mail, você poderá definir as formas de pagamento.
 
-![05 inStore configure pagamento](//images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
+![05 inStore configure pagamento](https://images.ctfassets.net/alneenqid6w5/3xd7WlTuRiKWSgaMMimCaQ/6d10e2dca27e2d2370c12f6b9926a119/05_inStore_configure_pagamento.png)
 
 Caso ainda não tenha contrato com uma adquirente, você pode manter apenas a opção __Dinheiro__ ativa. Ao clicar em __Confirmar__ verá a tela de sucesso.
 
-![06 inStore sucesso](//images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
+![06 inStore sucesso](https://images.ctfassets.net/alneenqid6w5/7JnAUV1oIwie4c84g8wC6C/df253c5a2d85701945f8b036b7bc09e1/06_inStore_sucesso.png)
 
 Agora basta voltar para o aplicativo, logar com as credenciais de vendedor e começar a vender!
 
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
index b9a03dfb5..7f5068ca0 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
@@ -18,11 +18,11 @@ O primeiro passo de qualquer integração é definir a política comercial que s
 
 Uma das funções da política comercial é fazer uma diferenciação de __catálogo__ e/ou __logística__ entre os diferentes canais de venda da loja. Ou seja, uma nova política comercial só é necessária quando um desses fatores for diferente entre os canais de venda.
 
-![marketplace-v2](//images.ctfassets.net/alneenqid6w5/6wy87Eq81O6ksOoq4EsAyG/29f6801d23163b8bef6d6fa30a68b4f1/marketplace-v2.png)
+![marketplace-v2](https://images.ctfassets.net/alneenqid6w5/6wy87Eq81O6ksOoq4EsAyG/29f6801d23163b8bef6d6fa30a68b4f1/marketplace-v2.png)
 
 Uma única política comercial pode ser compartilhada por mais de um marketplace ou entre loja principal e marketplace. Para isso, basta que se use o mesmo ID de política comercial nas [configurações](/pt/tutorial/integrando-com-marketplace). Fazendo isso, o mesmo catálogo e a mesma logística vão ser usados para as lojas ou canais que estão configurados com a mesma política comercial.
 
-![marketplace-politica-compartilhada](//images.ctfassets.net/alneenqid6w5/6ur6jWd8hG4wew4GO4YWS6/60624ed33a2b4765c4f8de3d064526f3/marketplace-politica-compartilhada.png)
+![marketplace-politica-compartilhada](https://images.ctfassets.net/alneenqid6w5/6ur6jWd8hG4wew4GO4YWS6/60624ed33a2b4765c4f8de3d064526f3/marketplace-politica-compartilhada.png)
 
 A partir desse entendimento, avalie se é necessário configurar uma nova política comercial na sua loja. Se a resposta for sim, siga as orientações [deste artigo](https://help.vtex.com/pt/faq/como-contratar-nova-politica-comercial--frequentlyAskedQuestions_700) antes de passar para a próxima etapa de configuração. Caso sua política comercial já atenda às condições que precisa para a integração com o marketplace, siga as próximas instruções.
 
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md
index 087fad5eb..713eb0c7c 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md
@@ -18,15 +18,15 @@ O primeiro passo de qualquer integração é definir a política comercial que s
 
 Uma das funções da política comercial é fazer uma diferenciação de __catálogo__ e/ou __logística__ entre os diferentes canais de venda da loja. Ou seja, uma nova política comercial só é necessária quando um desses fatores for diferente entre os canais de venda.
 
-![marketplace-v2](//images.contentful.com/alneenqid6w5/6wy87Eq81O6ksOoq4EsAyG/29f6801d23163b8bef6d6fa30a68b4f1/marketplace-v2.png)
+![marketplace-v2](https://images.contentful.com/alneenqid6w5/6wy87Eq81O6ksOoq4EsAyG/29f6801d23163b8bef6d6fa30a68b4f1/marketplace-v2.png)
 
 Uma única política comercial pode ser compartilhada por mais de um marketplace ou entre loja principal e marketplace. Para isso, basta que se use o mesmo ID de política comercial nas [configurações](/pt/tutorial/integrando-com-marketplace). Fazendo isso, o mesmo catálogo e a mesma logística vão ser usados para as lojas ou canais que estão configurados com a mesma política comercial.
 
-![marketplace-politica-compartilhada](//images.contentful.com/alneenqid6w5/6ur6jWd8hG4wew4GO4YWS6/60624ed33a2b4765c4f8de3d064526f3/marketplace-politica-compartilhada.png)
+![marketplace-politica-compartilhada](https://images.contentful.com/alneenqid6w5/6ur6jWd8hG4wew4GO4YWS6/60624ed33a2b4765c4f8de3d064526f3/marketplace-politica-compartilhada.png)
 
 Em outras palavras, se não houver necessidade de definir um catálogo ou um tipo de logística específicos para canais de venda diferentes, você também não vai precisar usar políticas comerciais separadas. Basta associar à sua integração com o marketplace o ID da política comercial que já existe. 
 
-![marketplace-politica-comercial-principal-e-compartilhada](//images.contentful.com/alneenqid6w5/30zkOOnOPYcCemUqmYE4Aw/48513228708cee71378543755a0fbbad/marketplace-politica-comercial-principal-e-compartilhada.png)
+![marketplace-politica-comercial-principal-e-compartilhada](https://images.contentful.com/alneenqid6w5/30zkOOnOPYcCemUqmYE4Aw/48513228708cee71378543755a0fbbad/marketplace-politica-comercial-principal-e-compartilhada.png)
 
 A partir desse entendimento, avalie se é necessário configurar uma nova política comercial na sua loja. Se a resposta for sim, siga as orientações [deste artigo](https://help.vtex.com/pt/faq/como-contratar-nova-politica-comercial--frequentlyAskedQuestions_700) antes de passar para a próxima etapa de configuração. Caso sua política comercial já atenda às condições que precisa para a integração com o marketplace, siga as próximas instruções.
 
diff --git a/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
index 65774ff45..16ce79347 100644
--- a/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
@@ -16,7 +16,7 @@ trackSlugPT:
 
 Este artigo tem como objetivo explicar como a app do inStore configura o AppLinking para as ações de `payment` e `payment-reversal` com as apps dos adquirentes.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuração
 
diff --git a/docs/tracks/pt/setting-up-the-app.md b/docs/tracks/pt/setting-up-the-app.md
index 6c9cfbe46..d622ab9d3 100644
--- a/docs/tracks/pt/setting-up-the-app.md
+++ b/docs/tracks/pt/setting-up-the-app.md
@@ -34,7 +34,7 @@ Para realizar as configurações iniciais do Customer Credit, siga os passos aba
   	<li><b>Appkey e appToken da afiliação não definidos</b>: clique em <b>Autenticar</b> para ser redirecionado a tela de configuração onde você deverá preencher as informações <b>Application Key</b> e <b>Application Token</b>. Esta ação permitirá que pagamentos realizados por meio de Customer Credit possam ser processados em sua loja. Saiba mais em <a href="https://developers.vtex.com/docs/guides/authentication">Authentication</a>.</li>
 </ul>
 
-![CC_Configurações_1_PT](//images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/b1505293c33db8cd9f7d8cf1d7802496/CC_Configura__es_1_PT.JPG)
+![CC_Configurações_1_PT](https://images.ctfassets.net/alneenqid6w5/6cDl5QeEatvpLW3kYxV7Yd/b1505293c33db8cd9f7d8cf1d7802496/CC_Configura__es_1_PT.JPG)
 
 ## Configurações da app
 
@@ -56,13 +56,13 @@ Por exemplo, para uma conta criada com o limite de crédito de R$ 1.000,00 e tol
 Os valores de tolerância são configurados em números decimais, sendo 0 a representação de 0% e 1, a representação de 100%. Exemplo: para utilizar uma tolerância de 5%, o valor a ser configurado é de 0.05.
 </div>
 
-![CC_Configurações_2_PT](//images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/1fde698cc193dda7e6ed82de51f7c19e/CC_Configura__es_2_PT.JPG)
+![CC_Configurações_2_PT](https://images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/1fde698cc193dda7e6ed82de51f7c19e/CC_Configura__es_2_PT.JPG)
 
 ### Criação automática de conta 
 
 Esta opção permite que qualquer cliente da loja possa utilizar o Customer Credit como meio de pagamento, mesmo que o você não tenha previamente criado uma conta para ele no app do Customer Credit. Ao ativar esta funcionalidade, você também deve definir qual o limite de crédito inicial poderá ser utilizado para pedidos realizados por clientes sem conta no Customer Credit.
 
-![CC_Configurações_3_PT](//images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/692229716909844ecc30b605e629301e/CC_Configura__es_3_PT.JPG)
+![CC_Configurações_3_PT](https://images.ctfassets.net/alneenqid6w5/1TX1ArtNwm8toa84UqNCHZ/692229716909844ecc30b605e629301e/CC_Configura__es_3_PT.JPG)
 
 ### Página Meus Créditos
 
@@ -70,7 +70,7 @@ Ao realizar a instalação da página __Meus Créditos__, você permitirá que o
 
 O cliente poderá acessar esta página no site da sua loja em __Minha Conta > Meus Créditos__.
 
-![CC_Configurações_4_PT](//images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/8bf45b5c1708a3861ea92a729c2b9d22/CC_Configura__es_4_PT.JPG)
+![CC_Configurações_4_PT](https://images.ctfassets.net/alneenqid6w5/59SuH9h84mmgaHmcDB2Bbl/8bf45b5c1708a3861ea92a729c2b9d22/CC_Configura__es_4_PT.JPG)
 
 ### Instruções de pagamento  
 
@@ -80,15 +80,15 @@ Esta configuração permite você possa inserir instruções relacionadas ao pag
 A mensagem cadastrada nessa configuração será replicada em todos os títulos emitidos para todas as contas de clientes do Customer Credit. Não é possível configurar uma mensagem única para cada cliente ou título específico.
 </div>
 
-![CC_Configurações_5_PT](//images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/b2c97be162320e8ed8ef2da3729ecedd/CC_Configura__es_5_PT.JPG)
+![CC_Configurações_5_PT](https://images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/b2c97be162320e8ed8ef2da3729ecedd/CC_Configura__es_5_PT.JPG)
 
 ### Informações de identificação
 
 Esta opção permite selecionar quais informações de identificação da loja devem ser exibidas na parte superior dos títulos emitidos.
 
-![CC_Configurações_6_PT](//images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/d85d0bf4bf69a520f923844d36f304bb/CC_Configura__es_6_PT.JPG)
+![CC_Configurações_6_PT](https://images.ctfassets.net/alneenqid6w5/6ADAtBnrZQS6sCzkwPSqFt/d85d0bf4bf69a520f923844d36f304bb/CC_Configura__es_6_PT.JPG)
 
-![CC_Configuration_8_PT](//images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/ec7b597cdf26bc9aeb17012047849f44/CC_Configuration_8_PT.JPG)
+![CC_Configuration_8_PT](https://images.ctfassets.net/alneenqid6w5/54WcXTGpAGppAyGxxoa8gx/ec7b597cdf26bc9aeb17012047849f44/CC_Configuration_8_PT.JPG)
 
 ## Condições de pagamento 
 
@@ -103,7 +103,7 @@ Para criar as condições de pagamento de títulos do Customer Credit, siga os p
 5. Ative a condição no campo __Status__.
 6. Em __Configure as condições de prazo e parcelamento__, indique o número de parcelas, período de vencimento (em dias) e a taxa de juros simples a ser aplicada em cada parcela. Para criar mais de uma condição de pagamento, clique em `Adicionar nova condição`.
 
-![CC_Configuration_9_PT](//images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/337edcc2678c80f6e1504def51efceaf/CC_Configuration_9_PT.JPG)
+![CC_Configuration_9_PT](https://images.ctfassets.net/alneenqid6w5/3P3JMnSiAPXNprYvgaNFNh/337edcc2678c80f6e1504def51efceaf/CC_Configuration_9_PT.JPG)
 
 <blockquote><ui>7. Se desejar, você também pode <a href="https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456">configurar condições especiais de pagamento</a>.</ui>
 
diff --git a/docs/tracks/pt/setting-up-the-order-summary-printing.md b/docs/tracks/pt/setting-up-the-order-summary-printing.md
index a679e89ec..5faf6eac9 100644
--- a/docs/tracks/pt/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/pt/setting-up-the-order-summary-printing.md
@@ -16,7 +16,7 @@ trackSlugPT: instore-customizacoes
 
 Quando o vendedor conclui um pedido com o inStore, ele pode imprimir um resumo desse pedido. Mas, para habilitar essa funcionalidade, você precisa fazer algumas configurações.
 
-![15. Configurar impressão de resumo do pedido - 1](//images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
+![15. Configurar impressão de resumo do pedido - 1](https://images.ctfassets.net/alneenqid6w5/I5tu0upqIMUVTCxTHFfmL/d25cd88a3601658aabea48fcee8e97f0/15._Configurar_impress__o_de_resumo_do_pedido_-_1.png)
 
 São necessárias duas etapas:
 
@@ -50,7 +50,7 @@ window.INSTORE_CONFIG = {
 
 Essa alteração fará aparecer no menu principal do inStore a opção __Configurar o dispositivo__, como mostra a imagem abaixo. É por meio dessa opção que vamos configurar a impressora.
 
-![15. Configurar impressão de resumo do pedido - 2](//images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
+![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> Há uma opção para imprimir automaticamente o resumo do pedido, assim que o pedido for concluído. Para habilitar, basta adicionar a propriedade <code>printPageAutomatically</code> com o valor <code>true</code> dentro do objeto printingConfig. Veja abaixo como ficaria o trecho de código neste caso.
@@ -84,11 +84,11 @@ Tendo o AppKey e o AppToken em mãos, siga os passos abaixo:
 2. Abra o aplicativo do inStore e entre na loja onde deseja configurar a impressora.
 3. No menu principal do inStore, na seção Configurações, agora deve constar a opção __Configurar o dispositivo__. Clique nessa opção.
 
-![15. Configurar impressão de resumo do pedido - 3](//images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
+![15. Configurar impressão de resumo do pedido - 3](https://images.ctfassets.net/alneenqid6w5/4BZ0V5CVUYA2Kwv49PfTYS/4fa9c04035ef00f8a0df9a9ae71b326b/15._Configurar_impress__o_de_resumo_do_pedido_-_3.png)
 
 Você encontrará o resumo do dispositivo configurado. Se essa for a primeira vez em que você realiza essa configuração, os campos dessa tela estarão vazios. Se um dispositivo já tiver sido configurado anteriormente, algumas informações sobre o dispositivo serão exibidas (Nome do dispositivo e Impressora padrão). Clique no botão __Editar__.
 
-![15. Configurar impressão de resumo do pedido - 4](//images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
+![15. Configurar impressão de resumo do pedido - 4](https://images.ctfassets.net/alneenqid6w5/4Xrv2WFGkaQ5ejAYZlF3ly/10e8b6b922cd7ee0f970f8db15cae1f9/15._Configurar_impress__o_de_resumo_do_pedido_-_4.png)
 
 Será exibido um formulário contendo os campos __AppKey__, __AppToken__ e o __nome__ com o qual você deseja identificar o dispositivo. Após inserir esses dados, clique em __Configurar__.
 
diff --git a/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
index 32e573ce5..a075c1f19 100644
--- a/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
@@ -37,7 +37,7 @@ Essa opção possibilita compartilhar um carrinho preenchido com um ou mais clie
 
 Veja o passo a passo ilustrado a seguir.
 
-![socialselling-sugestaocarrinho-pt](//images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/e0ce46b332549816ac9ff81a99d39879/socialselling-sugestaocarrinho-pt.gif)
+![socialselling-sugestaocarrinho-pt](https://images.ctfassets.net/alneenqid6w5/4UJM2FglGqcJGdFJqZ9AQg/e0ce46b332549816ac9ff81a99d39879/socialselling-sugestaocarrinho-pt.gif)
 
 O vendedor pode enviar o mesmo link para vários clientes, quantas vezes desejar. Cada vez que uma pessoa acessar esse link, um novo carrinho será gerado, exatamente igual ao criado no inStore. Cada carrinho acessado também fica associado à conta do vendedor e, se houver, ao código do vendedor.
 
@@ -63,4 +63,4 @@ Nesse caso, o vendedor precisa colocar itens no carrinho, preencher as informaç
 
 Veja o passo a passo ilustrado abaixo.
 
-![socialselling-paymentlink-pt](//images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/c00c97d9a8eec83b259d30793879d019/socialselling-paymentlink-pt.gif)
+![socialselling-paymentlink-pt](https://images.ctfassets.net/alneenqid6w5/hCgVTtE5YrsUFA2WHKrny/c00c97d9a8eec83b259d30793879d019/socialselling-paymentlink-pt.gif)
diff --git a/docs/tracks/pt/shipping-strategies.md b/docs/tracks/pt/shipping-strategies.md
index 1e3064b43..ae91a4909 100644
--- a/docs/tracks/pt/shipping-strategies.md
+++ b/docs/tracks/pt/shipping-strategies.md
@@ -18,7 +18,7 @@ As opções de envio que ficam disponíveis para o cliente no checkout da sua lo
 
 A estratégia de envio define como os estoques, as docas e as políticas de envio interagem para atender às necessidades dos seus clientes e do seu negócio. 
 
-![Estrategia Envio](//images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/3b4eb756f2c833f5b3fa7726c3cbdce7/Estrategia_Envio.png)
+![Estrategia Envio](https://images.ctfassets.net/alneenqid6w5/a0tXw0SPa0zFg5o0byFeS/3b4eb756f2c833f5b3fa7726c3cbdce7/Estrategia_Envio.png)
 
 A estratégia de envio é definida por três entidades logísticas:
 
diff --git a/docs/tracks/pt/size-chart.md b/docs/tracks/pt/size-chart.md
index 908261505..825e31eb4 100644
--- a/docs/tracks/pt/size-chart.md
+++ b/docs/tracks/pt/size-chart.md
@@ -18,7 +18,7 @@ Ao comprar roupas ou calçados on-line, muitos usuários costumam ter dúvidas s
 
 O guia de tamanhos do Mercado Livre é uma tabela de medidas ou equivalências que permite aos usuários visualizar as medidas exatas para que possam escolher o produto que melhor se adaptem. 
 
-![MLB tamanos1](//images.ctfassets.net/alneenqid6w5/3kHkmPhrh50s9QhJQurtcD/f4ca7decdd70609953dbd842b55c24f7/MLB_tamanos1.gif)
+![MLB tamanos1](https://images.ctfassets.net/alneenqid6w5/3kHkmPhrh50s9QhJQurtcD/f4ca7decdd70609953dbd842b55c24f7/MLB_tamanos1.gif)
 
 ## Entendendo o guia de tamanhos
 
@@ -46,7 +46,7 @@ Feita a escolha das categorias, preencha a coluna `CategoryID` com o ID da Categ
 
 Na segunda etapa do preenchimento escolha os nomes que deseja dar para as suas tabelas. Você deve definir um nome para cada tabela que será criada. É possível vincular a mesma tabela a várias categorias. A imagem abaixo ilustra como este nome aparece na criação manual no Mercado Livre - neste caso, a tabela seria Camisetas esportivas.
 
-![Screen Shot 2020-10-06 at 12.07.57](//images.ctfassets.net/alneenqid6w5/1gGCEZMpgye7A26vQF2faX/61530c84cd32534c8ec26f92a19bde52/Screen_Shot_2020-10-06_at_12.07.57.png)
+![Screen Shot 2020-10-06 at 12.07.57](https://images.ctfassets.net/alneenqid6w5/1gGCEZMpgye7A26vQF2faX/61530c84cd32534c8ec26f92a19bde52/Screen_Shot_2020-10-06_at_12.07.57.png)
 
 Feita a escolha das tabelas, preencha a coluna `TableName` com o nome do guia de tamanhos que será usado para cada categoria.
 
@@ -54,7 +54,7 @@ Feita a escolha das tabelas, preencha a coluna `TableName` com o nome do guia de
 
 Na terceira etapa do preenchimento escolha o nome que desejar dar para os tamanhos da sua tabela. A imagem abaixo ilustra como estes tamanhos aparecem na criação manual no Mercado Livre - neste caso, os tamanhos seriam P e M.
 
-![Screen Shot 2020-10-06 at 12.08.39](//images.ctfassets.net/alneenqid6w5/6KvJFDknNoKqgL32Rs9R58/9f29afbc7690b6e67bde3201e88112b0/Screen_Shot_2020-10-06_at_12.08.39.png)
+![Screen Shot 2020-10-06 at 12.08.39](https://images.ctfassets.net/alneenqid6w5/6KvJFDknNoKqgL32Rs9R58/9f29afbc7690b6e67bde3201e88112b0/Screen_Shot_2020-10-06_at_12.08.39.png)
 
 Feita a escolha das tabelas, preencha a coluna `SizeName` com o nome dos tamanhos que serão usados para cada guia de tamanhos. 
 
@@ -62,7 +62,7 @@ Feita a escolha das tabelas, preencha a coluna `SizeName` com o nome dos tamanho
 
 Na quarta etapa do preenchimento é definir as colunas que gostaria de incluir no guia de tamanhos.  A imagem abaixo ilustra como estes tamanhos aparecem na criação manual no Mercado Livre - note que é possível vincular até 5 colunas por tabela.
 
-![Screen Shot 2020-10-06 at 12.07.49](//images.ctfassets.net/alneenqid6w5/190jdCD4Tgmp6xGfLm0nlT/c387fda654105b81532fcc79e64087da/Screen_Shot_2020-10-06_at_12.07.49.png)
+![Screen Shot 2020-10-06 at 12.07.49](https://images.ctfassets.net/alneenqid6w5/190jdCD4Tgmp6xGfLm0nlT/c387fda654105b81532fcc79e64087da/Screen_Shot_2020-10-06_at_12.07.49.png)
 
 Na planilha de mapeamento, é necessário utilizar códigos específicos para indicar as colunas que devem ser incluídas no Guia de Tamanhos:
 
@@ -185,4 +185,4 @@ Agora, é necessário acessar sua conta do Mercado Livre para ativar o guia de t
 6. Na opção Guia de Tamanhos, selecione a tabela que você criou.
 7. Clique em **Confirmar**.
 
-![Início (2)](//images.ctfassets.net/alneenqid6w5/4hTDDEGYuZscACtdLiYNhW/d8781adfeab2a6c7326fba9aed7aa52b/Mercado_Livre_Brasil.gif)
+![Início (2)](https://images.ctfassets.net/alneenqid6w5/4hTDDEGYuZscACtdLiYNhW/d8781adfeab2a6c7326fba9aed7aa52b/Mercado_Livre_Brasil.gif)
diff --git a/docs/tracks/pt/store-development.md b/docs/tracks/pt/store-development.md
index 6812283f3..3a95f659e 100644
--- a/docs/tracks/pt/store-development.md
+++ b/docs/tracks/pt/store-development.md
@@ -19,7 +19,7 @@ Em uma loja de ecommerce, tanto a interface que os usuários veem e interagem qu
 - **Frontend**: O frontend compreende a camada visual de uma aplicação, como por exemplo, a interface de um website ou de um aplicativo mobile. É através dela que os usuários interagem com uma loja. Na VTEX, existem três tecnologias diferentes que podem ser utilizadas para o desenvolvimento de fronts de loja. São elas: o CMS Portal (Legado), o Store Framework e a FastStore.
 - **Backend**: O backend é a camada responsável por computar e processar todos os dados nescessários para executar as funcionalidades oferecidas por uma determinada aplicação. Na VTEX, o desenvolvimento de integrações e aplicações de backend se dá principalmente através do VTEX IO e das APIs da VTEX.
 
-![storefront mockup](//images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/89990fd9837da63e881a4fee92ce9787/image1.png)
+![storefront mockup](https://images.ctfassets.net/alneenqid6w5/35wyRHhSz4TC8CRjLQAhFF/89990fd9837da63e881a4fee92ce9787/image1.png)
 
 Nas seções a seguir, exploraremos melhor os principais aspectos e tecnologias relacionadas ao desenvolvimento de loja na VTEX.
 
diff --git a/docs/tracks/pt/technical-support.md b/docs/tracks/pt/technical-support.md
index 570451a09..df0f8e8cf 100644
--- a/docs/tracks/pt/technical-support.md
+++ b/docs/tracks/pt/technical-support.md
@@ -28,6 +28,6 @@ A tabela a seguir apresenta os principais tópicos relacionados a suporte técni
 
 Se o usuário precisar de um suporte técnico e não encontrar respostas nos portais e documentações mencionados, é possível fazer o contato através da [página de suporte](https://support.vtex.com/hc/pt-br/requests) e escolher **Técnico** como opção através do VTEX IA Suporte Bot, chatbot com foco em assistência técnica, como na imagem abaixo:
 
-![Support imagem 2 -PT](//images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/63300c9dbb7480b31b24085eb5ed7181/support_imagem2_PT.png)
+![Support imagem 2 -PT](https://images.ctfassets.net/alneenqid6w5/6rCMM1fwSMHqDJFtaP4IF2/63300c9dbb7480b31b24085eb5ed7181/support_imagem2_PT.png)
 
 Caso o usuário necessite de suporte além do VTEX IA Suporte Bot, ela pode abrir um ticket clicando em `ABRIR TICKET`. Para mais informações de como preencher o ticket para suporte técnico, basta acessar o artigo [Abrir chamados para o suporte VTEX - Técnico](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt#tecnico).
diff --git a/docs/tracks/pt/the-reservation.md b/docs/tracks/pt/the-reservation.md
index 01f18ebde..defb5ed73 100644
--- a/docs/tracks/pt/the-reservation.md
+++ b/docs/tracks/pt/the-reservation.md
@@ -35,7 +35,7 @@ Este é o fluxo da reserva na VTEX:
  
  3. Finalmente, uma vez que o pedido está na etapa de preparo para a entrega, os itens passam para o status `Reserva reconhecida`. Esse status indica que o item já não existe mais no estoque físico.      
 
-![reservation pt](//images.ctfassets.net/alneenqid6w5/7nDqT6kSvWTESRqZLzZutZ/9009856b729712a613d4d6c36612fd9a/reservation_pt.png)
+![reservation pt](https://images.ctfassets.net/alneenqid6w5/7nDqT6kSvWTESRqZLzZutZ/9009856b729712a613d4d6c36612fd9a/reservation_pt.png)
 
 <div class="alert alert-warning">
 A VTEX não desconta automaticamente os itens dos estoques, mesmo depois que eles passam para o status <code>Reserva reconhecida</code>. Os itens comprados continuarão nesse status até que o ERP ou o lojista realizem a baixa no estoque.
diff --git a/docs/tracks/pt/the-transaction-flow.md b/docs/tracks/pt/the-transaction-flow.md
index 9c2686be2..47fcaa3b8 100644
--- a/docs/tracks/pt/the-transaction-flow.md
+++ b/docs/tracks/pt/the-transaction-flow.md
@@ -22,7 +22,7 @@ As transações realizadas pelo módulo de pagamentos da VTEX passam por diverso
 
 Veja abaixo um exemplo de linha do tempo com os status da transação.
 
-![Transaction Flow](//images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
+![Transaction Flow](https://images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
 
 1. __Authorizing__: Este é o primeiro status de uma transação no Pagamentos. Neste estágio, o Pagamentos indica que teve início o processo de envio de informações para um adquirente ou para um outro gateway.
 2. __Authorized__: Após o início do processo de autorização, o adquirente ou o outro gateway envia as informações da transação para o banco emissor. O banco responde se a transação deve ser ou não autorizada. Caso negue a transação, o pagamento é __cancelado__. Caso autorize, o status da transação passa a ser __Authorized__.
diff --git a/docs/tracks/pt/unified-commerce-101.md b/docs/tracks/pt/unified-commerce-101.md
index 6772bc85c..dbf72acd4 100644
--- a/docs/tracks/pt/unified-commerce-101.md
+++ b/docs/tracks/pt/unified-commerce-101.md
@@ -16,7 +16,7 @@ trackSlugPT: estrategias-de-comercio-unificado
 
 A evolução do varejo online trouxe uma série de melhorias à experiência do cliente, e uma das mais relevantes talvez seja a que transformou a relação multicanal entre cliente e loja em uma relação de omnicanalidade.
 
-![32. Unified Commerce 101 - 2](//images.ctfassets.net/alneenqid6w5/hZLcXdCI6EXa4lR4cNShc/1bb91baac796afbdedb890b1c6362e90/32._Unified_Commerce_101_-_2.png)
+![32. Unified Commerce 101 - 2](https://images.ctfassets.net/alneenqid6w5/hZLcXdCI6EXa4lR4cNShc/1bb91baac796afbdedb890b1c6362e90/32._Unified_Commerce_101_-_2.png)
 
 Em uma arquitetura __multicanal__, cada canal se comunica de forma independente com a loja, seja o ecomerce, as lojas físicas, o SAC, as mídias sociais etc. Quando um cliente interage com um desses canais, a loja não tem conhecimento algum sobre quem é esse cliente.
 
@@ -26,7 +26,7 @@ No omnichannel, entretanto, os pedidos ainda são processados de forma isolada.
 
 O __Comércio Unificado__ resolve esse problema.
 
-![32. Unified Commerce 101 - 1](//images.ctfassets.net/alneenqid6w5/4JVV00Jk5F0P5S27c9BLCo/71bbbb249454b39188d08a87d2de0761/32._Unified_Commerce_101_-_1.png)
+![32. Unified Commerce 101 - 1](https://images.ctfassets.net/alneenqid6w5/4JVV00Jk5F0P5S27c9BLCo/71bbbb249454b39188d08a87d2de0761/32._Unified_Commerce_101_-_1.png)
 
 O Comércio Unificado é uma evolução do omnichannel: além do compartilhamento de dados, nessa estratégia acontece também a __unificação do sistema de processamento e gerenciamento dos pedidos__. Na prática, isso significa que todo pedido realizado em um canal da loja fica não apenas visível por outros canais como pode ser processado por eles.
 
diff --git a/docs/tracks/pt/unified-commerce.md b/docs/tracks/pt/unified-commerce.md
index 7a2853642..705c4005d 100644
--- a/docs/tracks/pt/unified-commerce.md
+++ b/docs/tracks/pt/unified-commerce.md
@@ -20,7 +20,7 @@ trackSlugPT: proximos-passos-apos-o-go-live
 
 [Contas franquias](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) são contas associadas a uma [conta principal](https://help.vtex.com/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl). Para empresas que possuam múltiplas lojas físicas, franqueados ou multimarcas, é possível criar contas-franquia vinculadas à conta principal da marca.
 
-![Conta principal](//images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/f6dc3d52f41b4acbf54704f177df49f4/next_steps_image1_PT.png)
+![Conta principal](https://images.ctfassets.net/alneenqid6w5/5LB8M0ZLnlb9dIQuZEQh3A/f6dc3d52f41b4acbf54704f177df49f4/next_steps_image1_PT.png)
 
 Esse modelo compartilha as informações do Catálogo e [frente de loja](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ), permitindo que o inventário das contas franquia seja disponibilizado para venda na loja principal e que diversas estratégias de comércio unificado possam ser utilizadas, tais como, [Ship from store](#ship-from-store), [lojas físicas como pontos de retirada](#pontos-de-retirada) e [prateleira infinita](https://help.vtex.com/en/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm).
 
diff --git a/docs/tracks/pt/unified-search.md b/docs/tracks/pt/unified-search.md
index 672d79e0c..44151cdeb 100644
--- a/docs/tracks/pt/unified-search.md
+++ b/docs/tracks/pt/unified-search.md
@@ -20,13 +20,13 @@ Com a [prateleira infinita](https://help.vtex.com/pt/tracks/estrategias-de-comer
 Para melhorar a experiência em cenários em que a conexão com a internet esteja em baixa velocidade, esta funcionalidade conta com recursos otimizados que fazem uso do cache do navegador para otimizar a busca.
 </div>
 
-![Barra busca - PT](//images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/3c7031056980ae911e2436933bee89fa/Tela_1_barra_busca.gif)
+![Barra busca - PT](https://images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/3c7031056980ae911e2436933bee89fa/Tela_1_barra_busca.gif)
 
 A busca do VTEX Sales App é unificada, o que significa que ao fazer uma busca no aplicativo a pesquisa é feita tanto no estoque local (da sua loja física) quanto no de outras lojas físicas e nos centros de distribuição associados ao ecommerce.
 
 Os resultados da busca mostram os produtos organizados para melhorar a experiência do cliente, com imagens que facilitam a identificação dos produtos e informações relevantes para o vendedor.
 
-![Busca unificada - PT](//images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/c918c2a6179fc8899f9bc3d899b60121/Busca_unificada_VTEX_Sales_App.png)
+![Busca unificada - PT](https://images.ctfassets.net/alneenqid6w5/2xcAiK7XONko8bTJrQPRNR/c918c2a6179fc8899f9bc3d899b60121/Busca_unificada_VTEX_Sales_App.png)
 
 Ao clicar na opção `Adicionar ao carrinho`, as seguintes informações do produto serão exibidas:
 
@@ -36,7 +36,7 @@ Ao clicar na opção `Adicionar ao carrinho`, as seguintes informações do prod
 
 Para adicionar o produto ao carrinho, selecione a variação, entrega e quantidade desejada e clique em `Adicionar ao carrinho`.
 
-![Carrinho - PT](//images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/f4a3612b1e625a03b446831229bbf605/Adicionar_ao_carrinho_VTEX_Sales_App.png)
+![Carrinho - PT](https://images.ctfassets.net/alneenqid6w5/3lUWtqtEAZZCsJhTYVkYBO/f4a3612b1e625a03b446831229bbf605/Adicionar_ao_carrinho_VTEX_Sales_App.png)
 
 ## Filtros
 
diff --git a/docs/tracks/pt/using-custom-controls.md b/docs/tracks/pt/using-custom-controls.md
index a426f132c..0f0426983 100644
--- a/docs/tracks/pt/using-custom-controls.md
+++ b/docs/tracks/pt/using-custom-controls.md
@@ -31,7 +31,7 @@ Para criar um controle customizado, siga o passo a passo abaixo:
 2. Clique em __Layout__
 3. Clique na pasta __CMS__
 4. Logo abaixo, clique na pasta __Custom Elements__
-5. Clique no botão __Add__![8 1](//images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
+5. Clique no botão __Add__![8 1](https://images.ctfassets.net/alneenqid6w5/2O1QkWg7UoaHzM7r1kZetq/aae42e4de48ea2bb9845f5607d14332c/8_1.png)
 6. Preencha o campo __Name__ com o nome do controle customizado
 7. Preencha o campo __Tag name__. É este nome que será usado no controle no momento de adicioná-lo ao template.
 8. Selecione o tipo do controle em __Type__
diff --git a/docs/tracks/pt/via-varejo-marketplace.md b/docs/tracks/pt/via-varejo-marketplace.md
index 01b608211..59460ffd3 100644
--- a/docs/tracks/pt/via-varejo-marketplace.md
+++ b/docs/tracks/pt/via-varejo-marketplace.md
@@ -18,6 +18,6 @@ A [Casas Bahia Marketplace](https://marketplace.via.com.br/) é uma das líderes
 
 Usando a integração nativa com a Casas Bahia Marketplace, você poderá expor e vender seus produtos nas lojas online das [Casas Bahia](https://www.casasbahia.com.br/), [Ponto](http://pontofrio.com.br/) e [Extra](http://extra.com.br/).
 
-![Casas Bahia Marketplace](//images.ctfassets.net/alneenqid6w5/nBFPh57qyKQcaPmseMIcj/9fd735f8bd3a713d26e3655aa0419601/Casas_Bahia_Marketplace.jpg)  
+![Casas Bahia Marketplace](https://images.ctfassets.net/alneenqid6w5/nBFPh57qyKQcaPmseMIcj/9fd735f8bd3a713d26e3655aa0419601/Casas_Bahia_Marketplace.jpg)  
 
 A configuração com a Casas Bahia Marketplace tem como objetivo enviar o catálogo de produtos da sua loja VTEX para os 3 marketplaces que fazem parte do Grupo Casas Bahia, permitindo que você anuncie seus produtos para milhões de clientes e aumente suas vendas.  
diff --git a/docs/tracks/pt/vtex-modules-i.md b/docs/tracks/pt/vtex-modules-i.md
index 25bb7eb78..96153b5a5 100644
--- a/docs/tracks/pt/vtex-modules-i.md
+++ b/docs/tracks/pt/vtex-modules-i.md
@@ -40,7 +40,7 @@ Não existem configurações prévias que devam ser realizadas antes das configu
 
 A arquitetura do Catálogo apresenta alguns conceitos fundamentais: categoria, marca, produto, SKU (_Stock Keeping Unit_) e especificação. A imagem abaixo ilustra a relação entre esses conceitos:
 
-![arquitetura-catalogo-PT](//images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
+![arquitetura-catalogo-PT](https://images.ctfassets.net/alneenqid6w5/4P3TCN2sjS3EuMdNO6Rrkb/76c3c87942fb93c1022b4eacb748c6f8/PT.png)
 
 O catálogo da loja deve ser criado seguindo a ordem dos passos abaixo:
 
@@ -77,7 +77,7 @@ Recomendamos a criação de uma hierarquia de até três níveis, incluindo [Dep
 
 Antes de importar o catálogo da loja para a VTEX, recomendamos começar a trabalhar na árvore de categorias criando uma tabela como a ilustrada abaixo. Isto permite uma melhor visualização de como a árvore está organizada e como as especificações serão apresentadas.
 
-![catalog_arquitecture_table_PT](//images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/d28bf46e6d7b444f994f986068a3b49f/catalog_arquitecture_table_PT.png)
+![catalog_arquitecture_table_PT](https://images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/d28bf46e6d7b444f994f986068a3b49f/catalog_arquitecture_table_PT.png)
 
 <div class="alert alert-info">
 Informações sobre como importar especificações para back-office podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
@@ -158,7 +158,7 @@ Os preços são as informações dos valores de venda dos seus SKUs. Estes preç
 
 O relacionamento entre preços, tabela de preço e o contexto que será aplicado está representado na imagem abaixo:
 
-![Conceito de Preços-PT](//images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/19ea7c2075d1a752b4001e652dff58c3/Conceito_de_Pre_os-PT.png)
+![Conceito de Preços-PT](https://images.ctfassets.net/alneenqid6w5/5xPmlWSbROFajhSkaUt7ya/19ea7c2075d1a752b4001e652dff58c3/Conceito_de_Pre_os-PT.png)
 
 É possível cadastrar tabelas de preços para os SKUs da loja de três maneiras:
 
@@ -278,7 +278,7 @@ O conjunto de configurações essenciais de logística de uma loja VTEX é chama
 
 A imagem abaixo mostra como esses conceitos se relacionam entre si na venda de um produto:
 
-![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
+![shipping_strategy_PT](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
 
 A tabela a seguir apresenta as principais configurações de logística da loja na VTEX:
 
@@ -330,7 +330,7 @@ Dentre os [principais casos de uso](https://help.vtex.com/pt/tutorial/lead_time-
 
 Para [calcular o prazo de envio](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) de pedidos, a plataforma VTEX considera as seguintes configurações:
 
-![Envio de Pedidos_PT](//images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/a9d7b3e4fcaf73e11e3d3d4d9e2a3e28/Envio_de_Pedidos_PT.png)
+![Envio de Pedidos_PT](https://images.ctfassets.net/alneenqid6w5/CwtKVwOkH8NMV0v2IYjlX/a9d7b3e4fcaf73e11e3d3d4d9e2a3e28/Envio_de_Pedidos_PT.png)
 
 - [Lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B): quantidade de tempo configurável para o SKU de um estoque. A configuração é opcional e, por padrão, está definida como zero dias.
 - [Tempo de estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137): tempo que o SKU leva para sair de um estoque para uma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Essa configuração é obrigatória, mas o tempo pode ser definido igual a zero.
diff --git a/docs/tracks/pt/vtex-modules-ii.md b/docs/tracks/pt/vtex-modules-ii.md
index 70f12cbd2..b14f3dea4 100644
--- a/docs/tracks/pt/vtex-modules-ii.md
+++ b/docs/tracks/pt/vtex-modules-ii.md
@@ -56,11 +56,11 @@ A tabela a seguir apresenta os principais agentes e termos utilizados no context
 
 Quando uma compra é finalizada na VTEX, uma nova transação é criada e o fluxo de pagamento é iniciado. No exemplo abaixo, é possível verificar um fluxo de pagamento para uma compra realizada por cartão de crédito:
 
-![payments-pt](//images.ctfassets.net/alneenqid6w5/5QPFkvZhpZzRWuq15zlMoz/c40d02d7dd6be8f01dc8b9ed03c4741e/payments_image1_PT.jpg)
+![payments-pt](https://images.ctfassets.net/alneenqid6w5/5QPFkvZhpZzRWuq15zlMoz/c40d02d7dd6be8f01dc8b9ed03c4741e/payments_image1_PT.jpg)
 
 Conforme as informações vão sendo transmitidas entre os agentes responsáveis pelo processamento dos dados, o status da transação de pagamento é atualizado para indicar em qual momento do fluxo os recursos se encontram. Para o fluxo de pagamento por cartão de crédito, temos o seguinte exemplo de status da transação:
 
-![payments-flow-pt](//images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/9419c03573e34455c5a97f08982be8fd/payments_image2_ALL.JPG)
+![payments-flow-pt](https://images.ctfassets.net/alneenqid6w5/6fsbJZ07a18ea8I1pk7UFo/9419c03573e34455c5a97f08982be8fd/payments_image2_ALL.JPG)
 
 Mais informações sobre cada etapa podem ser encontradas no artigo [Fluxo da transação no Pagamentos](https://help.vtex.com/pt/tutorial/transaction-flow-in-payments--Er2oWmqPIWWyeIy4IoEoQ). Para saber como acessar mais informações sobre as transações no Admin VTEX, bas conferir o artigo [Ver detalhes da transação](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
 
@@ -183,7 +183,7 @@ No Admin VTEX, em **Pedidos > [Todos os pedidos](https://help.vtex.com/pt/tutori
 
 Na página de detalhes do pedido, também é possível acompanhar a evolução do [fluxo do pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196). A imagem a seguir é um exemplo de fluxo quando a loja atua simultaneamente como marketplace e seller:
 
-![order-flow-pt](//images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/65a4533c0b089dd2792a21383f913393/pedido_fluxo_completo_pt.png)
+![order-flow-pt](https://images.ctfassets.net/alneenqid6w5/5ObTRbhlsYxoaW0Lzw7RmS/65a4533c0b089dd2792a21383f913393/pedido_fluxo_completo_pt.png)
 
 Para localizar o registro de uma compra no Admin VTEX, além de poder [filtrar pedidos](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192) na página **Todos os pedidos**, existe a opção de pesquisar pela barra de busca global, que aparece em todas as páginas do Admin VTEX. Para realizar a pesquisa, basta selecionar a opção `Pedidos`, no canto direito da barra de busca, e utilizar algum dos seguintes valores:
 
@@ -235,7 +235,7 @@ O checkout é a etapa final no processo de compras online e contribui de maneira
 
 Para assegurar o correto funcionamento do checkout, é necessário que os seguintes módulos estejam devidamente configurados pela loja: [Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), [Logística](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx), [Preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP#), [Promoções](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N#), [Pagamentos](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#) e [Pedidos](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2sl6hj2eqwgqbDgTF6y5qE).
 
-![checkout-pt](//images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/df639ea0697ca3e01b99963acd509b4f/checkout_image_PT.jpg)
+![checkout-pt](https://images.ctfassets.net/alneenqid6w5/57AJQIGKk5fuwN8SRMenM0/df639ea0697ca3e01b99963acd509b4f/checkout_image_PT.jpg)
 
 Este compartilhamento de informações permite que sejam processadas informações de disponibilidade, preços, promoções aplicáveis, métodos de envio e de pagamento.
 
diff --git a/docs/tracks/pt/what-is-a-logistics-route.md b/docs/tracks/pt/what-is-a-logistics-route.md
index a5432e8c3..8d3bbc1d7 100644
--- a/docs/tracks/pt/what-is-a-logistics-route.md
+++ b/docs/tracks/pt/what-is-a-logistics-route.md
@@ -33,4 +33,4 @@ Para cadastrar uma doca no admin da loja, siga os passos indicados neste [link](
 ### Transportadora
 É a partir daqui que os pedidos são distribuídos para seus destinos finais. Uma transportadora se compõe pela frota de veículos que farão as entregas. Assim, os pedidos saem do centro de distribuição direto para a transportadora que finaliza o processo até o cliente final. 
 
-![PT Conceitos Logística](//images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
+![PT Conceitos Logística](https://images.ctfassets.net/alneenqid6w5/aZMHlLUkOUDuN0vEITGy1/10a2b5b7d0ce301dc4c9fa2aa7bf236f/PT_Conceitos_Log__stica.png)
diff --git a/docs/tracks/pt/what-is-conversational-commerce-vtex.md b/docs/tracks/pt/what-is-conversational-commerce-vtex.md
index 808916649..a29f83a0c 100644
--- a/docs/tracks/pt/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/pt/what-is-conversational-commerce-vtex.md
@@ -20,7 +20,7 @@ Com ele, é possível realizar compras utilizando uma lista de compras, ideal pa
 
 Para utilização do suporte humano, o Message-to-Order já está pré integrado com as plataformas de mercado Zenvia (produto Zenvia Chat) e Zendesk. Para clientes que não tenham essas plataformas ou não desejem atendimento humano, também é possível redirecionar o cliente aos canais de atendimento padrões da marca através de mensagem personalizada. 
 
-![chatbot-PT](//images.ctfassets.net/alneenqid6w5/5w2PKYYmrGDYuiP0t4jQXU/2e05dae6dd79cd1352cade3533624f68/Captura_de_Tela_2022-07-28_a__s_11.13.08.png)
+![chatbot-PT](https://images.ctfassets.net/alneenqid6w5/5w2PKYYmrGDYuiP0t4jQXU/2e05dae6dd79cd1352cade3533624f68/Captura_de_Tela_2022-07-28_a__s_11.13.08.png)
 
 <div class="alert alert-info">
 O Message-to-Order é um produto em fase de início de operação com escopo reduzido (Alpha). Portanto o perfil de cliente e mercados que abrange ainda é limitado a BR e LATAM e às capacidades disponibilizadas pelo cliente nesse estágio.
diff --git a/docs/tracks/pt/what-is-the-cms.md b/docs/tracks/pt/what-is-the-cms.md
index 81689101f..9cdc17885 100644
--- a/docs/tracks/pt/what-is-the-cms.md
+++ b/docs/tracks/pt/what-is-the-cms.md
@@ -14,7 +14,7 @@ trackId: 2YcpgIljVaLVQYMzxQbc3z
 trackSlugPT: cms
 ---
 
-![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System, em Português, Sistema de Gerenciamento de Conteúdo) é uma funcionalidade voltada para o gerenciamento de conteúdo de forma prática e constante.
 
diff --git a/docs/tracks/pt/what-is-the-master-user.md b/docs/tracks/pt/what-is-the-master-user.md
index f16be61e1..e4f953539 100644
--- a/docs/tracks/pt/what-is-the-master-user.md
+++ b/docs/tracks/pt/what-is-the-master-user.md
@@ -26,7 +26,7 @@ Se seu usuário tem perfil de acesso ao módulo Gerenciamento da conta, você po
 
 Ao clicar na loja desejada, o nome e o e-mail do usuário Titular encontram-se na seção __Contato__.
 
-![usuario-master-contato pt](//images.ctfassets.net/alneenqid6w5/HuUChkUJYyg2wi0gqua6c/015b91c77fd19f159117db66298c79aa/contato_usuario_master.png)
+![usuario-master-contato pt](https://images.ctfassets.net/alneenqid6w5/HuUChkUJYyg2wi0gqua6c/015b91c77fd19f159117db66298c79aa/contato_usuario_master.png)
 
 Entre as ações que somente o usuário Titular pode tomar, estão:
 - Reindexar o catálogo.
diff --git a/docs/tracks/pt/whatsapp-integration.md b/docs/tracks/pt/whatsapp-integration.md
index 85d518bf3..6798d01de 100644
--- a/docs/tracks/pt/whatsapp-integration.md
+++ b/docs/tracks/pt/whatsapp-integration.md
@@ -62,16 +62,16 @@ Após a instalação do aplicativo, a VTEX compartilhará a URL do Admin do Conv
 Com essas informações, siga os passos abaixo:
 
 1. Acesse o Admin VTEX via URL enviada pelo time de suporte. Você será encaminhado para a tela abaixo:
-![Track 101 - Conversational Commerce 1 - PT](//images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 1 - PT](https://images.ctfassets.net/alneenqid6w5/Zg2VTR41pSMleFi6bpcLT/cf9fb66691f9ec8f18a184099c70f3bf/Screenshot_2022-10-04_at_18-05-46_Track_101_-_Conversational_Commerce.png)
 2. Clique no botão `Configurar conta WhatsApp Business`.
 3. Uma janela do Facebook será aberta para configuração. Efetue o login com o perfil de Administração do Business Manager desejado.
 4. Selecione a opção `Criar uma conta WhatsApp Business`.
 5. Insira o nome da conta que será exibido como nome do perfil no WhatsApp.
 6. Selecione a categoria e cadastre a descrição da conta. 
-![Track 101 - Conversational Commerce 2 - PT](//images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 2 - PT](https://images.ctfassets.net/alneenqid6w5/1DbUwuYgXSleNYBzDnS72n/e935883f195905d78f9c2209b1cc324b/Screenshot_2022-10-04_at_18-07-00_Track_101_-_Conversational_Commerce.png)
 7. Verifique o número de telefone a ser associado à conta por meio do código enviado para o telefone.
 8. Notifique o suporte da VTEX para finalizar a configuração.
 
 Uma vez que a configuração seja concluída, o alerta abaixo será exibido no Admin. 
 
-![Track 101 - Conversational Commerce 3 - PT](//images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
+![Track 101 - Conversational Commerce 3 - PT](https://images.ctfassets.net/alneenqid6w5/3RkQDfGaL3r5KV7j8uTXRH/6f32bb6973f7762a6eb06f12cd596e32/Screenshot_2022-10-04_at_18-07-47_Track_101_-_Conversational_Commerce.png)
diff --git a/docs/tutorials/en/accessing-a-client-abandoned-cart.md b/docs/tutorials/en/accessing-a-client-abandoned-cart.md
index 115127076..2d46a5eab 100644
--- a/docs/tutorials/en/accessing-a-client-abandoned-cart.md
+++ b/docs/tutorials/en/accessing-a-client-abandoned-cart.md
@@ -29,26 +29,26 @@ Viewing these fields is very simple. Once logged in to your store Admin, just fo
 
 1. In the Admin sidebar, click __Master Data__;
 
-  ![Carrinho Abandonado - 1 - EN](//images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/4e22ff4da9abc1b692ee236082a1c85d/4GdZSkwtm9f76BIVFnC65D_Masterdata_EN.jpg)
+  ![Carrinho Abandonado - 1 - EN](https://images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/4e22ff4da9abc1b692ee236082a1c85d/4GdZSkwtm9f76BIVFnC65D_Masterdata_EN.jpg)
 
 2. Click the __Profile System__ Settings icon (gear);
 
-  ![Carrinho Abandonado - 2 - EN](//images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/b22ea9f10722d249dd6bbda4ab6f43ac/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
+  ![Carrinho Abandonado - 2 - EN](https://images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/b22ea9f10722d249dd6bbda4ab6f43ac/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
 
 3. Make sure you are in the __Applications__ tab;
 
-  ![Carrinho Abandonado - 3 - EN](//images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/2cba845e608d8d2c577542351afebe1f/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
+  ![Carrinho Abandonado - 3 - EN](https://images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/2cba845e608d8d2c577542351afebe1f/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
 
 4. Click Edit (Pencil icon) in the __Customers__ category;
 
-  ![Carrinho Abandonado - 4 - EN](//images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/e2ec5bfae66b41f7b882a30510d08c51/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
+  ![Carrinho Abandonado - 4 - EN](https://images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/e2ec5bfae66b41f7b882a30510d08c51/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
 
 5. Select __"Last Cart"__ and __"Cart"__ from the __Listing Options__;
 
-  ![Carrinho Abandonado - 5 - EN](//images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/e74e93b98db80fd40db53d38efd7436a/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 5 - EN](https://images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/e74e93b98db80fd40db53d38efd7436a/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
 
 6. Click __Save__.
 
-  ![Carrinho Abandonado - 6 - EN](//images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/75c67997d3547b16653b09030778d91e/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
+  ![Carrinho Abandonado - 6 - EN](https://images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/75c67997d3547b16653b09030778d91e/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
 
 With this, you can see the parameters of your customers' abandoned carts.
diff --git a/docs/tutorials/en/account-management.md b/docs/tutorials/en/account-management.md
index 2ca076027..7db59a6c2 100644
--- a/docs/tutorials/en/account-management.md
+++ b/docs/tutorials/en/account-management.md
@@ -85,7 +85,7 @@ After a user has filled in and saved the **Name** and **E-mail** in the contacts
 The template for this automatic email can be changed in the <a href="https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84">Message Center</a> by modifying the <i>account registration</i> template.
 </div>
 
-![account registration](//images.ctfassets.net/alneenqid6w5/I0CttFz6ayQW2Q8uOkKmc/19184a55a9a8de5cb3e04088251a9c93/account_registration.jpg)
+![account registration](https://images.ctfassets.net/alneenqid6w5/I0CttFz6ayQW2Q8uOkKmc/19184a55a9a8de5cb3e04088251a9c93/account_registration.jpg)
 
 ## Security
 
diff --git a/docs/tutorials/en/account-settings-overview.md b/docs/tutorials/en/account-settings-overview.md
index 11cf14d43..781d2e4df 100644
--- a/docs/tutorials/en/account-settings-overview.md
+++ b/docs/tutorials/en/account-settings-overview.md
@@ -21,7 +21,7 @@ In the **Account Settings** section, you can control access to the Admin and cha
 
 To access the _Account Settings_ page, click on your **profile avatar**, which can be identified by the first letter of your email address, and click on **Account Settings**.
 
-![Admin v4 account settings menu EN](//images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/c9f9e17c63ce76c40d01a650920ce5ff/Admin_v4_account_settings_menu_EN.jpg)
+![Admin v4 account settings menu EN](https://images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/c9f9e17c63ce76c40d01a650920ce5ff/Admin_v4_account_settings_menu_EN.jpg)
 
 This section includes the following pages, soon to be included in Admin v4.
 
diff --git a/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md b/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md
index b922ed3c6..6d38247f3 100644
--- a/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md
+++ b/docs/tutorials/en/activating-the-complete-list-link-on-the-category-menu.md
@@ -20,7 +20,7 @@ The **Lista Completa** link on the Categorias menu is frequently used in stores
 
 Look at the following example, for "Departamento 2":
 
-![categoria.en](//images.ctfassets.net/alneenqid6w5/2GfnTZfCAPr9Baxn4dy1s/a6c97388bf36b6adc233112586d3e012/categoria.en.png)
+![categoria.en](https://images.ctfassets.net/alneenqid6w5/2GfnTZfCAPr9Baxn4dy1s/a6c97388bf36b6adc233112586d3e012/categoria.en.png)
 
 The store has preferred to show only a few of its many categories in the menu.
 
@@ -29,6 +29,6 @@ You can configure this when registering the category, selecting **Menu with acti
 - If it is checked, the category appears in the menu.
 - If it is not checked, the category does not appear and the Lista Completa option will appear on the site.
 
-![categoria2.en](//images.ctfassets.net/alneenqid6w5/3KtFDmEUqs71YobX8VOibJ/6b3709cb7741069a6ead068b9eb40a4c/categoria2.en.png)
+![categoria2.en](https://images.ctfassets.net/alneenqid6w5/3KtFDmEUqs71YobX8VOibJ/6b3709cb7741069a6ead068b9eb40a4c/categoria2.en.png)
 
 
diff --git a/docs/tutorials/en/activating-the-new-order-placed.md b/docs/tutorials/en/activating-the-new-order-placed.md
index 436af5ac6..98845b78f 100644
--- a/docs/tutorials/en/activating-the-new-order-placed.md
+++ b/docs/tutorials/en/activating-the-new-order-placed.md
@@ -17,10 +17,10 @@ subcategory:
 
 The new Order Placed page brings an enhanced and fully mobile-friendly layout.
 
-![Nova página de Order Placed em versão desktop e mobile](//images.contentful.com/alneenqid6w5/6li99MH1AIqmOECuy8K4Ec/635952ed77d4630e1bd8c08f7761920d/cconf-announcement-0.png)
+![Nova página de Order Placed em versão desktop e mobile](https://images.contentful.com/alneenqid6w5/6li99MH1AIqmOECuy8K4Ec/635952ed77d4630e1bd8c08f7761920d/cconf-announcement-0.png)
 
 To activate it, go to the **Orders** tab the Portal module and activate the opt-in _Order Placed Upgrade_. The new version will be activated by default on 12/20/2017 and the old version will be discontinued.
 
-![Opt in no Portal V2](//images.contentful.com/alneenqid6w5/Ce7a3zePdIkEWcMy8m2w8/396ecacbc62a5a1883d2faf0197f4090/cconf-announcement-1.png)
+![Opt in no Portal V2](https://images.contentful.com/alneenqid6w5/Ce7a3zePdIkEWcMy8m2w8/396ecacbc62a5a1883d2faf0197f4090/cconf-announcement-1.png)
 
 To learn how to upgrade your customization, check the tutorial [Customizing the Checkout Confirmation pages](http://help.vtex.com/en/tutorial/customizing-the-checkout-confirmation-pages).
diff --git a/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md b/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md
index e75e021b8..67b949282 100644
--- a/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md
+++ b/docs/tutorials/en/add-or-edit-a-url-mapping-through-worksheet-import.md
@@ -26,4 +26,4 @@ The file structure must be as follows:
 - Column D: Data Inicial (DD/MM /YYYY format)
 - Column E: Data Final (DD/MM /YYYY format)
 
-![urlbuilder en](//images.ctfassets.net/alneenqid6w5/4rLD4jAM0oaq6CqQam6U4y/895ec67d0ac775529a71b8536e4b03bd/urlbuilder_en.png)
+![urlbuilder en](https://images.ctfassets.net/alneenqid6w5/4rLD4jAM0oaq6CqQam6U4y/895ec67d0ac775529a71b8536e4b03bd/urlbuilder_en.png)
diff --git a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
index b34697e78..f54507ae9 100644
--- a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
+++ b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 To enable login via Facebook, in your VTEX Admin, go to **Account Settings > Authentication** and complete the **Client ID** and **Client Secret** fields, as described in the [Configuring login with Facebook and Google](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513) article.
 
-![Facebook OAuth EN](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/7daac156505a588b95fc0e90fbc08e2d/1-login-fb-en.PNG)
+![Facebook OAuth EN](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/7daac156505a588b95fc0e90fbc08e2d/1-login-fb-en.PNG)
 
 To get these credentials, follow the instructions below:
 
@@ -35,12 +35,12 @@ To begin, you need to create a Facebook application by following the steps below
 4. Click `Create App`.
 5. Click **Allow people to log in with their Facebook** account from the options shown below.
 
-   ![2-login-fb-en](//images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/18115fc2fab3b2efa194681f5f46d1cc/2-login-fb-en.png)
+   ![2-login-fb-en](https://images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/18115fc2fab3b2efa194681f5f46d1cc/2-login-fb-en.png)
 
 6. Click `Next`.
 7. Enter the app name and the email address of the person in charge of the app in the fields illustrated below.
 
-   ![3-login-fb-en](//images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/6a66ed67c5576d710573f0ab9642b9eb/3-login-fb-en.png)
+   ![3-login-fb-en](https://images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/6a66ed67c5576d710573f0ab9642b9eb/3-login-fb-en.png)
 
 8. Click `Create app`.
 
@@ -50,15 +50,15 @@ The next step is to set up the Facebook Login product in the app you created. To
 
 1.	Click **Products** in the side menu or the Meta for Developers **Dashboard**, as in the image below.
 
-   ![4-login-fb-en](//images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/ee51c9db1b9c5d6c8f9298a901b74d5c/4-login-fb-en.png)
+   ![4-login-fb-en](https://images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/ee51c9db1b9c5d6c8f9298a901b74d5c/4-login-fb-en.png)
 
 2. Click `Configure` and select `Settings`.
 
-   ![5-login-fb-en](//images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/0c913b1d202594789f0986427c404a7e/5-login-fb-en.png)
+   ![5-login-fb-en](https://images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/0c913b1d202594789f0986427c404a7e/5-login-fb-en.png)
 
 3. Set the options as in the image below:
 
-   ![Configuração URI OAuth Facebook EN](//images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/ef5ad727b07d41fdd907cef762788dd6/configuracoes_Oauth_EN.png)
+   ![Configuração URI OAuth Facebook EN](https://images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/ef5ad727b07d41fdd907cef762788dd6/configuracoes_Oauth_EN.png)
 
    Insert the following URLs in **Valid OAuth Redirect URIs**, replacing `{{HOST_URL}}`  with your store's base URL and e `{{accountName}}` with your VTEX account name as described in the store's Admin:
 
@@ -74,7 +74,7 @@ Finally, you must complete specific information about the app to finish the regi
 
 1.	In the Meta for Developers side menu, go to **App settings** and click **Basic:**
 
-   ![7-login-fb-en](//images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/a572a3a7fea37cbec1cded5f5bd95ca4/7-login-fb-en.png)
+   ![7-login-fb-en](https://images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/a572a3a7fea37cbec1cded5f5bd95ca4/7-login-fb-en.png)
 
 2. Copy the value from the **App ID** field. You must enter this value in the **Client ID** field when[ configuring Facebook Login in the VTEX Admin](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513).
 3. Under **App Secret**, click the **Show** button, and then copy the value from the field. You must enter this value in the **Client Secret** field when [configuring Facebook Login in the VTEX Admin](https://help.vtex.com/en/tutorial/configuring-login-with-facebook-and-google--tutorials_513).
diff --git a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
index e2fa73315..7e475d2a5 100644
--- a/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
+++ b/docs/tutorials/en/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 To activate Google login with OAuth2, you must access the VTEX ID in your admin and fill in the `Client ID` and `Client Secret` fields, as described [in this article](/en/tutorial/configuring-user-id-with-facebook-and-google).
 
-![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
+![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)
 
 These values are derived from a project that needs to be created in the Google Cloud Platform API service.
 
@@ -30,17 +30,17 @@ The steps mentioned below describe a third-party platform and may therefore be o
 1. Access the link [`https://console.developers.google.com/`](https://console.developers.google.com/);
 2. In the side tab, click on __Credentials__;
 3. Click on __Create Project__;
-    ![Criar Projeto Google EN](//images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/6aa68d7e981fd534a35ef3046b8d4cc2/Criar_Projeto_Google_EN.png)
+    ![Criar Projeto Google EN](https://images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/6aa68d7e981fd534a35ef3046b8d4cc2/Criar_Projeto_Google_EN.png)
 4. Name the project and click on __Create__;
-    ![Novo Projeto Google EN](//images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/aba1e15eee652b262a3932ffa87cdf02/Novo_Projeto_Google_EN.png)
+    ![Novo Projeto Google EN](https://images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/aba1e15eee652b262a3932ffa87cdf02/Novo_Projeto_Google_EN.png)
 5. Click on __Create credentials__;
-    ![Criar Credenciais Google EN](//images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/b5916fc567067ef1c3dcb464d392be4f/Criar_Credenciais_Google_EN.png)
+    ![Criar Credenciais Google EN](https://images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/b5916fc567067ef1c3dcb464d392be4f/Criar_Credenciais_Google_EN.png)
 6. Select the __OAuth client ID__ option;
-    ![ID cliente OAuth Google EN](//images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/66104a80f14e2ea12cd894435ddf0843/ID_cliente_OAuth_Google_EN.png)
+    ![ID cliente OAuth Google EN](https://images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/66104a80f14e2ea12cd894435ddf0843/ID_cliente_OAuth_Google_EN.png)
 7. Click on __Configure consent screen__;
-    ![Configurar Tela Consentimento Google EN](//images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/5b057c3ce55c3207415d1b37117b5ac1/Configurar_Tela_Consentimento_Google_EN.png)
+    ![Configurar Tela Consentimento Google EN](https://images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/5b057c3ce55c3207415d1b37117b5ac1/Configurar_Tela_Consentimento_Google_EN.png)
 8. Choose the type of user for your store(__Internal__ or __External__) and click on __Create__;
-    ![Tipo usuário Google EN](//images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/2f15aac33884886b494137342ebadaf6/Tipo_usu__rio_EN.png)
+    ![Tipo usuário Google EN](https://images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/2f15aac33884886b494137342ebadaf6/Tipo_usu__rio_EN.png)
 9. __Application name__: will be shown to clients when logging in;
 10. __User support email__: for users to contact you with question about their consent;
 11. __App logo__: corresponds to your store logo;
@@ -49,19 +49,19 @@ The steps mentioned below describe a third-party platform and may therefore be o
     - `vtex.com.br`, regarding our backend servers
 13. __Developer contact information__: these email addresses are for Google to notify you about any changes to your project;
 14. Click on __Save and continue__;
-    ![Configurações Tela Consentimento EN](//images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4d3a9c16d4a83dfc8559f8ddab04cd6f/Configura____es_Tela_Consentimento_EN.png)
+    ![Configurações Tela Consentimento EN](https://images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4d3a9c16d4a83dfc8559f8ddab04cd6f/Configura____es_Tela_Consentimento_EN.png)
 13. In the left side menu, click on __Credentials__;
 14. In Type of application, click on __Web Application__;
-    ![Credenciais Aplicativo Web Google EN](//images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/68c4968faa050c891f7501420d7fc6c8/Credenciais_Aplicativo_Web_Google_EN.png)
+    ![Credenciais Aplicativo Web Google EN](https://images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/68c4968faa050c891f7501420d7fc6c8/Credenciais_Aplicativo_Web_Google_EN.png)
 15. __Name__: for internal identification;
 16.  __Authorized JavaScript origins__: add the exact addresses that can use this authentication method, corresponding to your site; for example `https://www.mystore.com`. We also recommended that you add the address `https://{{accountName}}}.myvtex.com` of your account, where `{{accountName}}` is your account name as described in the store's admin menu;
 17. __Authorized redirect URIs__: add the VTEX service URL:
     -`https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
-    ![Configurações Aplicativo Web Google EN](//images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/9e9b216146ef6285903e647722080234/Configura____es_Aplicativo_Web_EN.png)
+    ![Configurações Aplicativo Web Google EN](https://images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/9e9b216146ef6285903e647722080234/Configura____es_Aplicativo_Web_EN.png)
 
 18. After you complete these steps, your credentials will be displayed:
-    ![Cliente OAuth criado Google EN](//images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/b2db65f7598baba9de8f6ecd7d3aa70e/Cliente_OAuth_criado_Google_EN.png)
+    ![Cliente OAuth criado Google EN](https://images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/b2db65f7598baba9de8f6ecd7d3aa70e/Cliente_OAuth_criado_Google_EN.png)
     - Copy the __Client ID__ from Google and paste it into the `Client Id' field in the VTEX ID admin.
     - Copy the __client secret key__ from Google and paste it into the `Client Secret` field in the VTEX ID admin.
-    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)    
+    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/1dd69d7f89b79cbca4c0d3265e800c3c/google_EN.png)    
     Then, save the changes.
diff --git a/docs/tutorials/en/adding-an-attachment.md b/docs/tutorials/en/adding-an-attachment.md
index 946485328..aed618f2d 100644
--- a/docs/tutorials/en/adding-an-attachment.md
+++ b/docs/tutorials/en/adding-an-attachment.md
@@ -31,7 +31,7 @@ Attachments can be used to [complement a product with custom information](https:
 After adding the attachment, you need to add the keys and **permitted values** related to it. You can add as many keys as you wish. To add the keys and **permitted values**, follow the steps below.
 
 1. On the **Custom product attributes** page, find the row of the attachment you have created and click `Modify`, as illustrated in the image below.
-  ![anexos.pt](//images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/0088408090cd1bec84c4826676af8cb8/custom-product-attributes-en.PNG)
+  ![anexos.pt](https://images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/0088408090cd1bec84c4826676af8cb8/custom-product-attributes-en.PNG)
 2. Fill in the fields listed below.
     * **Key Name:** name of the custom information. This field is required and must contain only letters, numbers, or periods. For example, if the customizable product is a U.S. soccer jersey, its key names can be `Name` and `Number`.
     * **Maximum Number of Characters:** the maximum number of characters the customer can type to add custom information to the product. For example, in this field you could set the character limit for the name that will be printed on a shirt. This field is required. If you do not fill it in, the attachment will not be displayed to your customer as a selection option in the cart.
diff --git a/docs/tutorials/en/adding-bin-information.md b/docs/tutorials/en/adding-bin-information.md
index 20b23411b..c77d16bfc 100644
--- a/docs/tutorials/en/adding-bin-information.md
+++ b/docs/tutorials/en/adding-bin-information.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 The Bank Identification Number (BIN) consists of the first six or eight digits of a credit or debit card and identifies the card's issuing institution.
 
-![BIN_image_digits_EN_2](//images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/1e44ba9fd9c075edcc4042470c40af1a/BIN_image_digits_EN_2.png)
+![BIN_image_digits_EN_2](https://images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/1e44ba9fd9c075edcc4042470c40af1a/BIN_image_digits_EN_2.png)
 
 When a banking institution wants to create new card profiles or issue new cards for an existing model, new BINs are required. This also applies when a card [brand](https://help.vtex.com/en/tutorial/what-is-a-credit-card-brand--4bNba5QYuIwKEmac88KwyI) is acquired by another.
 
@@ -39,4 +39,4 @@ In the ticket, you should attach a spreadsheet with the following information:
 
 Template example:
 
-![Bin_spreadsheet](//images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/3c5b160ad784b2fdf80b57f99a375050/Bin_spreadsheet.PNG)
+![Bin_spreadsheet](https://images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/3c5b160ad784b2fdf80b57f99a375050/Bin_spreadsheet.PNG)
diff --git a/docs/tutorials/en/adding-collections-cms.md b/docs/tutorials/en/adding-collections-cms.md
index cdbf2bbf1..3d044614a 100644
--- a/docs/tutorials/en/adding-collections-cms.md
+++ b/docs/tutorials/en/adding-collections-cms.md
@@ -33,7 +33,7 @@ When the number of created collections surpasses twenty, those exceeding that nu
 
 Choosing the products that will make up a collection is done by clicking on __New Group__ in the desired collection, creating a __group__.
 
-![new-group-collection en](//images.ctfassets.net/alneenqid6w5/7tJUzscKOqsDSLv64f71KJ/49434a9c33f677cf4632f2145d4064b4/new-group-collection_en.png)
+![new-group-collection en](https://images.ctfassets.net/alneenqid6w5/7tJUzscKOqsDSLv64f71KJ/49434a9c33f677cf4632f2145d4064b4/new-group-collection_en.png)
 
 Before choosing which products to add to a group, you will need to give it a name and specify which type the created group falls under.
 
@@ -75,17 +75,17 @@ For example: When selecting a category `A` and a brand `B`, only products pertai
 
 To add the products of a specific department to a group, select the desired department and click on __Save Group__, as shown in the image below.
 
-![seleção-departamento EN](//images.ctfassets.net/alneenqid6w5/2CWCcsikNQciGdeJrN4ffV/3419aae384eec69319a0fd199decc16a/sele____o-departamento_EN.png)
+![seleção-departamento EN](https://images.ctfassets.net/alneenqid6w5/2CWCcsikNQciGdeJrN4ffV/3419aae384eec69319a0fd199decc16a/sele____o-departamento_EN.png)
 
 The same applies for products of a specific Category or Subcategory.
 
-![seleção-categoria-subcategoria EN](//images.ctfassets.net/alneenqid6w5/2Z3mfoWo65F6fJM22sZEqi/c5dc354968d5bb690fadff1da9316e96/sele____o-categoria-subcategoria_EN.png)
+![seleção-categoria-subcategoria EN](https://images.ctfassets.net/alneenqid6w5/2Z3mfoWo65F6fJM22sZEqi/c5dc354968d5bb690fadff1da9316e96/sele____o-categoria-subcategoria_EN.png)
 
 ## Product by Brand
 
 To create a group containing products from one or more brands, select the desired brand from the corresponding list.
 
-![seleção-marca-coleção en](//images.ctfassets.net/alneenqid6w5/1wjrZ0Oa0n2ZwdB8QXAWAS/8386ab974309a4ffe652011ab1a312f4/sele____o-marca-cole____o_en.png)
+![seleção-marca-coleção en](https://images.ctfassets.net/alneenqid6w5/1wjrZ0Oa0n2ZwdB8QXAWAS/8386ab974309a4ffe652011ab1a312f4/sele____o-marca-cole____o_en.png)
 
 Brands are displayed in alphabetical order. When clicking on the first letter corresponding to the desired brand, the list expands and displays the existing brands.
 
@@ -95,7 +95,7 @@ Brands are displayed in alphabetical order. When clicking on the first letter co
 
 When adding a SKU to a group, the product to which it is linked is also added. If the product is linked to more than one SKU, adding one SKU would also add all other SKUs to the group.
 
-![selecao-sku-manual en & es](//images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
+![selecao-sku-manual en & es](https://images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
 
 In the __find SKUs__ field, you can type in as many SKU IDs as needed, separating each one by a comma. 
 
@@ -117,21 +117,21 @@ Get the file template for adding SKUs to or removing them from a collection <a h
 
 You can __Bulk insert SKUs__ by importing an `.xls` format spreadsheet to list SKUs that will be part of a group.
 
-![selecao-sku-planilha-insert en & es](//images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
+![selecao-sku-planilha-insert en & es](https://images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
 
 In the imported spreadsheet, all SKU IDs must be listed in the first column, with a header, as shown in the example below:
 
-![exemplo-planilha-seleção-sku-coleção](//images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png) 
+![exemplo-planilha-seleção-sku-coleção](https://images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png) 
 
 After selecting the desired spreadsheet, click on the __Import SKUs__ option to sent the information.
 
-![Import SKUs](//images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
+![Import SKUs](https://images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
 
 #### Bulk remove
 
 To avoid having to remove SKUs one at a time, you can use the import function of a spreadsheet to bulk remove them.
 
-![exclusao-skus-manualmente-planilha-coleção-cms en & es](//images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
+![exclusao-skus-manualmente-planilha-coleção-cms en & es](https://images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
 
 In this specific case, the SKUs listed in the imported spreadsheet will be excluded from the group. Do this by clicking on __remove SKUs__ after the file has been loaded. 
 
@@ -147,7 +147,7 @@ In the <strong>Other options</strong> section, the <strong>Pre-sales</strong> an
 
 Note that you can only select one of the two options. Should you want both add-ons, create two groups and configure each one with the respective option.
 
-![other-options-cms-coleções EN](//images.ctfassets.net/alneenqid6w5/4kHHhPDUSBSdjkYaApxayp/ef552cf4e72bb119f0b080605927a2b9/other-options-cms-cole____es_EN.png)
+![other-options-cms-coleções EN](https://images.ctfassets.net/alneenqid6w5/4kHHhPDUSBSdjkYaApxayp/ef552cf4e72bb119f0b080605927a2b9/other-options-cms-cole____es_EN.png)
 
 ### Pre-sales
 
diff --git a/docs/tutorials/en/adding-sku-specifications-or-fields.md b/docs/tutorials/en/adding-sku-specifications-or-fields.md
index 4c8d2d1e1..827a866b0 100644
--- a/docs/tutorials/en/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/en/adding-sku-specifications-or-fields.md
@@ -43,7 +43,7 @@ Before creating any specifications, it's important to understand that they follo
 
 Example: consider a **Men's shirt** product. In __Catalog > Products and SKUs > SKU > Specifications__, as illustrated in the page below, we can see that the specification group called **Characteristics** is associated with the Shirt category. This group includes a field named **Color** and a field named **Size**.
 
-![heranca-especificacoes-sku-en](//images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/1dd8ca5d13bf8f288cac031795bf85ea/sku-specifications-inheritance-en.PNG)
+![heranca-especificacoes-sku-en](https://images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/1dd8ca5d13bf8f288cac031795bf85ea/sku-specifications-inheritance-en.PNG)
 
 Since this is an SKU specification, the information selected on that page will apply only to the **Men's Shirt** product variations. All SKUs added to the **Men's Shirt** category and all product SKUs of the same category must also have these specifications filled out.
 
@@ -85,7 +85,7 @@ To create an SKU field, follow the instructions below:
     * **Active**: Inserts or removes this field when adding an SKU.
 7. Click `Save`.
 
-![sku-spec-1](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/3c508d340371923bcc233d8737197b66/en-sku-spec-2.gif)
+![sku-spec-1](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/3c508d340371923bcc233d8737197b66/en-sku-spec-2.gif)
 
 #### SKU Field types
 
@@ -130,13 +130,13 @@ The **Values** of the SKU fields will vary according to the selected field type:
 
     Insert one value per row and press `Enter` after each value, as illustrated in the image below.
 
-    ![valores-campo-sku-en](//images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/f7aa05de7fb5964660b912f2aa2f0b24/valores-especificacoes-sku-en.PNG)
+    ![valores-campo-sku-en](https://images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/f7aa05de7fb5964660b912f2aa2f0b24/valores-especificacoes-sku-en.PNG)
 
 8. Click `Save`.
 
     The added values will be displayed in the [SKU registration interface](#sku-registration).
 
-![sku-spec-2](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/a6da423b96ac0edb46837b590e7a030f/en-sku-spec-2.gif)
+![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/a6da423b96ac0edb46837b590e7a030f/en-sku-spec-2.gif)
 
 <div class = "alert alert-info">
   <p>If you are adding values for the first time in a field, you must return to the form of that specific field and check the <strong>Active</strong> option.</p>
@@ -180,7 +180,7 @@ To fill in the specifications for each SKU individually, follow the instructions
 
 8. Click `Save`.
 
-![sku-spec-3](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/caa7782074d6311b0ac3b7182258464d/en-sku-spec-3.gif)
+![sku-spec-3](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/caa7782074d6311b0ac3b7182258464d/en-sku-spec-3.gif)
 
 #### Spreadsheet
 
@@ -203,7 +203,7 @@ To fill in SKU specifications in bulk using a spreadsheet, first you must export
 9. Click **Select** to select the file with the filled out spreadsheet from your computer.
 10. Click `Import`.
 
-![sku-spec-4](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/9fb7eb05a187b6cd90ad963067ca1223/en-sku-spec-4.gif)
+![sku-spec-4](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/9fb7eb05a187b6cd90ad963067ca1223/en-sku-spec-4.gif)
 
 ## Learn more
 - [Adding product specifications or fields](https://help.vtex.com/en/tutorial/adding-specifications-or-product-fields--tutorials_106)
diff --git a/docs/tutorials/en/adding-specifications-or-product-fields.md b/docs/tutorials/en/adding-specifications-or-product-fields.md
index 3419c3771..bc27f7264 100644
--- a/docs/tutorials/en/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/en/adding-specifications-or-product-fields.md
@@ -43,7 +43,7 @@ Before creating any specifications, it's important to understand that they follo
 
 Consider the **TV** product for example. In __Catalog > All products > Edit > Specifications__, as illustrated in the page below, we can see that the specification group called **Characteristics** is associated with the TV's category. This group includes a field named **Inches** and a field named **Age group**, which are mandatory.
 
-![specifications-en](//images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/abd1962c5063aa7f66d4ca8c743216c9/specifications-en.PNG)
+![specifications-en](https://images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/abd1962c5063aa7f66d4ca8c743216c9/specifications-en.PNG)
 
 Since this is a product specification, the information selected on that page will apply to all **TV** product variations. All products added to the TV's category must have these specifications filled out, since they are required fields.
 
@@ -80,7 +80,7 @@ To create a product field, follow the steps below:
     * **Active**: Inserts or removes this field when adding the product (**Specifications** tab).
 7. Click `Save`. 
 
-![product-spec-1](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/d63d7b135d47717c567f77769ded7998/EN_ProdutoGif_1_Alterado.gif)
+![product-spec-1](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/d63d7b135d47717c567f77769ded7998/EN_ProdutoGif_1_Alterado.gif)
 
 #### Product field types
 
@@ -146,7 +146,7 @@ For the **Combo**, **Radio** and **CheckBox** field types, you must add preset v
 
     The created values will be displayed in the Product **Specifications** tab.
 
-![product-spec-2](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/c8c76e2f734ee038be20a6c273fdf987/EN_ProdutoGif_2_Alterado.gif)
+![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/c8c76e2f734ee038be20a6c273fdf987/EN_ProdutoGif_2_Alterado.gif)
 
 <div class = "alert alert-info">
   <p>If you are adding values for the first time in a field, you must return to the form of that specific field and check the <strong>Active</strong> option.</p>
@@ -188,7 +188,7 @@ To fill in the specifications for each product individually, follow the instruct
 
 6. Click `Save`.
 
-![product-spec-3](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/80503bcee1eddc3c30cc9b6eee05a4f5/EN_ProdutoGif_3_Alterado.gif)
+![product-spec-3](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/80503bcee1eddc3c30cc9b6eee05a4f5/EN_ProdutoGif_3_Alterado.gif)
 
 #### Spreadsheet
 
@@ -211,7 +211,7 @@ To fill in product specifications in bulk by spreadsheet, you need to export the
 9. Click **Select** to select the file with the completed spreadsheet on your computer.
 10. Click `Import`.
 
-![product-spec-4](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/0bc27b7b0d9e41dc649b057c20aaf90f/EN_ProdutoGif_4_Alterado.gif)
+![product-spec-4](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/0bc27b7b0d9e41dc649b057c20aaf90f/EN_ProdutoGif_4_Alterado.gif)
 
 ## Learn more
 - [Adding SKU specifications or fields](https://help.vtex.com/en/tutorial/adding-sku-specifications-or-fields--tutorials_119)
diff --git a/docs/tutorials/en/adding-your-brands.md b/docs/tutorials/en/adding-your-brands.md
index 0b710aaa6..f9ec0afd5 100644
--- a/docs/tutorials/en/adding-your-brands.md
+++ b/docs/tutorials/en/adding-your-brands.md
@@ -19,4 +19,4 @@ subcategory:
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
 
-<video class="wp-video-shortcode" id="video-2561-9" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4?_=9" />[//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4](//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4 "//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4")</video>
+<video class="wp-video-shortcode" id="video-2561-9" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4?_=9" />[//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4](https://assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4 "//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4")</video>
diff --git a/docs/tutorials/en/additional-shipping-costs.md b/docs/tutorials/en/additional-shipping-costs.md
index 59ce37a98..451d5e381 100644
--- a/docs/tutorials/en/additional-shipping-costs.md
+++ b/docs/tutorials/en/additional-shipping-costs.md
@@ -17,7 +17,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Additional shipping costs are extra charges added to the shipping rate as established in [shipping policies](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140). So, when configuring costs for shipping items, you can set a fixed rate and include additional charges. Together, these values will compose the [shipping rate](https://help.vtex.com/en/tutorial/gerenciar-valores-de-frete--tutorials_141). 
 
-![Tarifa envio EN](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
+![Tarifa envio EN](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
 
 You can configure the following additional costs:
 
@@ -26,7 +26,7 @@ You can configure the following additional costs:
 * [Insurance charge](https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV#additional-insurance-charge);
 * [Extra shipping charge](https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV#additional-shipping-charge).
 
-![adicionais frete EN](//images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/eee27446335556a96fece61f8d2f0e8f/adicionais_frete_EN.svg)
+![adicionais frete EN](https://images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/eee27446335556a96fece61f8d2f0e8f/adicionais_frete_EN.svg)
 
 <div class="alert alert-danger">
 Note that all of them can be simultaneously considered for composing the shipping rate. The final calculation of the <a href="https://help.vtex.com/en/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">shipping rate</a> is the sum of all additional charges plus the flat rate. 
@@ -69,7 +69,7 @@ There are two ways to configure the weight-based additional charge:
 
 To learn more, access their tutorials.
 
-![faixa-peso EN](//images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/df911253923073437cf3708e1d2b753b/faixa-peso_EN.png)
+![faixa-peso EN](https://images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/df911253923073437cf3708e1d2b753b/faixa-peso_EN.png)
 
 ## Price-based additional charge
 
@@ -163,4 +163,4 @@ To configure the additional shipping charge, go to the left-side menu in the VTE
     If you want to include a 10% fee, fill in the field with 10. Use a period to indicate the decimal place, such as 1.67.
 3. Click on `Save`.
 
-![adicional configuracoes EN](//images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/2a2708eaac81731568792959f167bdd9/adicional_configuracoes_EN.png)
+![adicional configuracoes EN](https://images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/2a2708eaac81731568792959f167bdd9/adicional_configuracoes_EN.png)
diff --git a/docs/tutorials/en/admin-v4-getting-started.md b/docs/tutorials/en/admin-v4-getting-started.md
index b11d3090d..aa365a462 100644
--- a/docs/tutorials/en/admin-v4-getting-started.md
+++ b/docs/tutorials/en/admin-v4-getting-started.md
@@ -24,22 +24,22 @@ To achieve this, we are redesigning multiple parts of the experience and making
 ## Improved navigation 
 Everything you need to manage your VTEX store is still available in Admin v4, only now with a more straightforward organization. Our left and top navigation menu were rebuilt from scratch, grouping similar categories in a clearer way to reduce distractions and help your team find what they need faster. It is also possible to use the search bar to find specific sections on the menu.
 
-![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Information Center
 This is where we group all useful links from our VTEX ecosystem, to help you get the best out of our VTEX platform. By clicking on the `?` button on the top bar, you can access our Help Center, blog, Developer Portal, Platform Status and support pages.    
 
-![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Store Settings
 For this new experience, we have grouped all settings, from all sections under a specific tab: Store Settings. Through this improvement, you can easily access all settings that affect every service in your account.
 
-![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Profile Settings
 Your profile avatar, on the upper right corner now hosts all the settings related to your user and account. Through the avatar you can access user settings, account settings, billing information, change your Admin’s locale,  switch to the Admin’s previous version and logout of your account and logout. Through this improvement, we separated your profile settings from the configurations that affect your actual store. Now you have more control and visibility over actions that affect your business, and those that affect your profile. 
 
-![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 ## Refreshed home page
 
@@ -47,7 +47,7 @@ Our admin home page was redesigned to give you a high level overview of your sto
 
 As soon as you log in to Admin v4, you will see useful metrics and charts to monitor your store's performance, such as revenue and number of orders, sales funnel and conversion rates, and your top 10 highest grossing products. Check out all components on the new Dashboard, and learn how they work, looking through the list below.
 
-![Dashboard v4](//images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
+![Dashboard v4](https://images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
 
 - **Orders:**  number of orders placed.  All data about orders and revenue comes from VTEX’s Order Management System.  
 - **Sessions:** Number of visits to store  
diff --git a/docs/tutorials/en/ads-from-vtex-sales-app.md b/docs/tutorials/en/ads-from-vtex-sales-app.md
index d69f2ddd0..290c4e256 100644
--- a/docs/tutorials/en/ads-from-vtex-sales-app.md
+++ b/docs/tutorials/en/ads-from-vtex-sales-app.md
@@ -59,17 +59,17 @@ To create an offer page for VTEX Sales App, follow the steps below:
 4. In the **Sections** tab, click the + button to add a new section. Each section is a collection of products or search terms. Each section will be displayed as a carousel. You can reorder custom displays by clicking the Move down or Move up buttons.
 5. Select an offer type, either products or search results.
   - **Product custom display:** It will display each product and SKU (optional) that you specify. Add the following information: - **Custom display title:** Name of the custom display that will be displayed on the page. - **Product ID:** Identifier number of the product you want to display. Required field. - **Product SKU ID:** Iidentifier number of the product's SKU you want to display. Optional field.
-![vitrine-produto-en](//images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/055391c146dbfe153d0161eb1f9af701/image.png)
+![vitrine-produto-en](https://images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/055391c146dbfe153d0161eb1f9af701/image.png)
 After completing the fields, the product image will be displayed with the "starting at" price. If you include the SKU, the price and promotion of the indicated SKU will be displayed. You can add more products by clicking + NEW PRODUCT. You can add up to 10 products in each custom display. The result of the product custom display will be displayed as shown in the image below.
-![vitrine-produto-2-en](//images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/f288b81bbd6f3f9e788afdccead5286e/image.png)
+![vitrine-produto-2-en](https://images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/f288b81bbd6f3f9e788afdccead5286e/image.png)
   - **Search results custom display:** It will display products from a search result that you define. Add the following information: 
 Custom display title: Name of the custom display that will be displayed on the page.
     - **Search image:** image that will represent the selection of products in the showcase.
     - **Search name:** Name of the search that will be displayed on the page.
     - **Search term:** Search term: Search term that will be used as a reference for the products.
-![vitrine-busca-en](//images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/79a8cc3b08dd79d76d402456e47a62ac/image.png)
+![vitrine-busca-en](https://images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/79a8cc3b08dd79d76d402456e47a62ac/image.png)
 When the seller clicks the search term, they will be directed to the search result determined in the Search term. You can also include up to 10 searches in each custom display. See the result in the image below:
-![vitrine-busca-2-en](//images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/58073fd76945673090d787622ebcc09a/image.png)
+![vitrine-busca-2-en](https://images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/58073fd76945673090d787622ebcc09a/image.png)
 <ol start="6">
   <li>After creating the sections, click <code>Save</code>, then click <code>Publish</code> and <code>Publish Now</code> to finalize.</li>
 </ol> 
@@ -80,7 +80,7 @@ The publication of the custom display will enter the indexing queue and will be
     - **Custom display title:** Name of the custom display as it will appear on the page.
     - **Collection ID:** The collection identifier number that will be displayed on the page.
 
-![Vitrine - EN](//images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/c3f21920a6ac94d53a3097b8a7b3ad72/Vitrine_-_EN.png)
+![Vitrine - EN](https://images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/c3f21920a6ac94d53a3097b8a7b3ad72/Vitrine_-_EN.png)
 
 ## Activate the offer menu in VTEX Sales App
 
@@ -90,12 +90,12 @@ Access the technical settings of VTEX Sales App at:
 1. Click the <i class="fas fa-cog"></i> button.
 2. Select the **Code** tab.
 3. Select the `checkout-instore-custom-js` file in the side tab.
-![checkout-instore-custom-js-file](//images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/8f4cdc9e643abd06f8b3ef4ecc906040/image.png)
+![checkout-instore-custom-js-file](https://images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/8f4cdc9e643abd06f8b3ef4ecc906040/image.png)
 5. In the `window.INSTORE_CONFIG` object, add the flag `enableExplore: true,`.
-![window.INSTORE_CONFIG](//images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/e2984ba814f55a81a0b4263ff9d1a694/image.png)
+![window.INSTORE_CONFIG](https://images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/e2984ba814f55a81a0b4263ff9d1a694/image.png)
 6. Click <i class="fas fa-save"></i> `Save`.
 7. Optionally, you can set the offer page as the seller's homepage. To do this, add the flag `initialPage: 'advertisements',` to the `window.INSTORE_CONFIG` object.
-![initialPage : advertisements](//images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/57c885204ca51226610e97e88f2e85e4/image.png)
+![initialPage : advertisements](https://images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/57c885204ca51226610e97e88f2e85e4/image.png)
 
 ## Accessing offers in VTEX Sales App
 
@@ -105,4 +105,4 @@ In VTEX Sales App, the seller will can access the offer page in two different wa
 
 * **Explore Menu:** If the offer page is not set as the seller's homepage, it can still be easily accessed through the Explore menu. To access the offer page, the seller should click the Explore menu. This will directly take the seller to the offer page, where they can view and interact with the available products and promotions.
 
-![vitrine-sale-app-en](//images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/b1924f30b51e02d7c4fa4ca057b162bb/image.png)
+![vitrine-sale-app-en](https://images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/b1924f30b51e02d7c4fa4ca057b162bb/image.png)
diff --git a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
index 7b30c5db1..4274e1086 100644
--- a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
@@ -47,7 +47,7 @@ VTEX currently offers a single ad format: search results. Learn more about this
 6. Select the products you want to advertise using one of the following options:
 
    * __Search products by EAN:__ Search for products in your catalog by EAN.
-   * __Upload File:__ Upload a CSV file with a list of EAN codes, as in [this example](//assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/75958f41bc4628e283ab1d8e060a01ab/teste-ads.csv). EANs are mandatory and bids are optional in the file.
+   * __Upload File:__ Upload a CSV file with a list of EAN codes, as in [this example](https://assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/75958f41bc4628e283ab1d8e060a01ab/teste-ads.csv). EANs are mandatory and bids are optional in the file.
 
 7. In the *Budget, bid, and schedule* section, click the edit button <i class="fas fa-pencil-alt"></i>.
 8. Set the bid amount for each product. You can set each value individually.
@@ -102,7 +102,7 @@ You can pause a specific product in your campaign,  which will stop the correspo
 
 On the [VTEX Ad Network](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) app's home screen, you'll also find details about ongoing campaigns.
 
-![vtex_ad_network_create_campaign_EN](//images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/353d1cb7a0d73b40594ec358a5ecbffa/vtex_ad_network_create_campaign.png)
+![vtex_ad_network_create_campaign_EN](https://images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/353d1cb7a0d73b40594ec358a5ecbffa/vtex_ad_network_create_campaign.png)
 
 At the top of the page, you'll find aggregated data:
 
diff --git a/docs/tutorials/en/affiliates-program-app.md b/docs/tutorials/en/affiliates-program-app.md
index 11bdae5da..9db445376 100644
--- a/docs/tutorials/en/affiliates-program-app.md
+++ b/docs/tutorials/en/affiliates-program-app.md
@@ -40,11 +40,11 @@ The app creates three types of affiliate pages, available to them without any ac
 
 The **affiliate page** is the VTEX store URL that they will share with the customers. The following image shows an example:
 
-![print_affiliates_url_en](//images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/6d0e53ff26c4f9c7f3d9fbd3cebf4db9/print_affiliates_url_en.png)
+![print_affiliates_url_en](https://images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/6d0e53ff26c4f9c7f3d9fbd3cebf4db9/print_affiliates_url_en.png)
 
 The **affiliate profile page** is an interface where the affiliate can track and manage their orders and commissions. The image below shows an example:
 
-![affiliate_profile_page_en](//images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/9f11c3ffaa7aac74fe70ab6268679b74/print_profile_en.png)
+![affiliate_profile_page_en](https://images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/9f11c3ffaa7aac74fe70ab6268679b74/print_profile_en.png)
 
 The **registration page** allows those who are interested in becoming affiliates to fill in their information to apply for VTEX store registration. 
 
@@ -74,7 +74,7 @@ The **Affiliate Management** page allows you to do the following:
 - [View affiliate details](#viewing-affiliate-details)
 - [Edit an affiliate](#editing-an-affiliate)
 
-![affiliates_management_page_en](//images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6ea891b6bd27373375fb3d808b26d97c/affiliates_management_page_en.png)
+![affiliates_management_page_en](https://images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6ea891b6bd27373375fb3d808b26d97c/affiliates_management_page_en.png)
 
 ### Adding an affiliate
 
@@ -121,7 +121,7 @@ The **Order Management** page allows you to do the following:
 - [Export order spreadsheet](#exporting-the-order-list)
 - [View order details](#viewing-order-details)
 
-![orders_management_page_en](//images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/9f63b76106915d023708574ad68f3d18/orders_management_page_en.jpg)
+![orders_management_page_en](https://images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/9f63b76106915d023708574ad68f3d18/orders_management_page_en.jpg)
 
 ### Monitoring data
 
@@ -174,7 +174,7 @@ The **Commission Management** page allows you to do the following:
 - [Import commissions](#importing-commissions)
 - [Download last import](#downloading-the-last-import)
 
-![commissions_ management_page_en](//images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/73d8406a30e628474923dfb098dc53da/commissions__management_page_en.png)
+![commissions_ management_page_en](https://images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/73d8406a30e628474923dfb098dc53da/commissions__management_page_en.png)
 
 ### Searching for commissions
 
diff --git a/docs/tutorials/en/all-orders.md b/docs/tutorials/en/all-orders.md
index a6c1f46b8..e6e01a007 100644
--- a/docs/tutorials/en/all-orders.md
+++ b/docs/tutorials/en/all-orders.md
@@ -28,7 +28,7 @@ The **All Orders** page allows retailers to track their store's orders and extra
 
 The following sections provide more details about each page component and its actions.
 
-![Order Listing EN](//images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/e39aa9ff8eab7e0a031c2d7464dc2e87/Order_Listing_EN.gif)
+![Order Listing EN](https://images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/e39aa9ff8eab7e0a031c2d7464dc2e87/Order_Listing_EN.gif)
 
 Besides searching for orders in **Orders > All Orders**, you can search for orders from any page in the VTEX Admin using the global search bar at the top bar. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
 
@@ -166,7 +166,7 @@ Learn more about each column.
 
 ## VTEX DO
 
-![VTEX Do overview EN](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
+![VTEX Do overview EN](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
 
 [VTEX DO](https://help.vtex.com/en/tutorial/vtex-do-beta--7KMbRL4OslN8DTX9oiuCiu) manages tasks automatically created by the VTEX Admin that require manual action by the ecommerce team. 
 
diff --git a/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md
index 30cfc2a78..99b4a0292 100644
--- a/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md
@@ -108,7 +108,7 @@ To install the app, go to the VTEX App Store:
 The configurations made in the Automatic Invoice field will be applied to all orders.
 </div>
 
-![MCF](//images.contentful.com/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/e26c0d8fc1ec3a9069d09e027e36aa98/Amazon_MCF_EN.PNG)
+![MCF](https://images.contentful.com/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/e26c0d8fc1ec3a9069d09e027e36aa98/Amazon_MCF_EN.PNG)
 
 ### Integrating the catalog
 
diff --git a/docs/tutorials/en/amazon-offer-matching.md b/docs/tutorials/en/amazon-offer-matching.md
index 4a627d3af..539e7bf7c 100644
--- a/docs/tutorials/en/amazon-offer-matching.md
+++ b/docs/tutorials/en/amazon-offer-matching.md
@@ -19,7 +19,7 @@ Every time a [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIF
 
 On VTEX, the EAN is used to map the products with the corresponding [ASINs](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (*Amazon Standard Identification Number*) on Amazon. To map the equivalence between the EAN and the ASIN, manual matching is required. EAN and ASIN matches need to be exact for the offers to be linked correctly.  
 
-![Offer match overview](//images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/263c3f6248e2b8d2cc07807c4800fd97/Match-an__ncios-Amazon.gif)
+![Offer match overview](https://images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/263c3f6248e2b8d2cc07807c4800fd97/Match-an__ncios-Amazon.gif)
 
 ## Opportunity tab  
 
@@ -75,7 +75,7 @@ To approve the match, the seller must follow the steps below.
 1. 	In the `Opportunities` tab, click the icon <i class="fas fa-ellipsis-v"></i>.
 2. 	Click `View Details`.
 3. 	Check out the information displayed on the page.
-![Single Offer Match](//images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/11d1054047295a3b8b03a687bb1201be/Match_individual_AMZ.png)  
+![Single Offer Match](https://images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/11d1054047295a3b8b03a687bb1201be/Match_individual_AMZ.png)  
 
 4. 	Then, click one of the available buttons: `Publish`, `Reject and request review`, or `Reject`.  
 
@@ -86,13 +86,13 @@ On the `Opportunity` tab, all listed products matching Your Offer and Amazon Sug
 1. On the `Opportunity` tab, select the checkbox next to the offer title that has a matching SKU <> ASIN.
 As you select the products, the following pop-up will appear on the screen showing the number of selected products.  
 
-![popupEN](//images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/41058f81c65b88b1b8d48c9018e6e1ee/MATCH_AMZ_EN.png)
+![popupEN](https://images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/41058f81c65b88b1b8d48c9018e6e1ee/MATCH_AMZ_EN.png)
 
 2. When you have finished selecting the products, click `Publish Selected Offers`.  
 
 3. In the match confirmation pop-up, check the selected offers and click `Confirm Publish`.  
 
-![Matching confirmation](//images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4ebd22582c42cb2f5cd1a53f2311c2d4/MATCH_CONFIRMATION.png)
+![Matching confirmation](https://images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4ebd22582c42cb2f5cd1a53f2311c2d4/MATCH_CONFIRMATION.png)
 
 Once confirmed, your offers will be sent and queued for processing. After approval, they will appear in the __Offers tab__, where you can __"View details of your offer"__, __"View offer suggested by Amazon"__, and __search for__ offers using the search bar.  
 
diff --git a/docs/tutorials/en/analytics.md b/docs/tutorials/en/analytics.md
index b126954d2..60fb417fb 100644
--- a/docs/tutorials/en/analytics.md
+++ b/docs/tutorials/en/analytics.md
@@ -80,8 +80,8 @@ To export a report in .csv format, you must follow the steps below:
 
 The report (CSV file) you have downloaded contains two tables. The first table contains information about searched terms, as illustrated below. It also shows funnel metrics (from the **ProductsClick** column to the **ProductsSold** column) if you have selected this option.
 
-![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
+![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/a16b574485adf9cb41ab258a3c169881/search-report-term.png)
 
 The second table shows data for the selected period, as illustrated below. In the __Date__ column, you can see the date of the search.
 
-![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
+![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/354c3c4357d578dc2492b89a78c2a272/search-report-date.png)
diff --git a/docs/tutorials/en/analyze-a-products-reservations.md b/docs/tutorials/en/analyze-a-products-reservations.md
index f0b14197d..518a2c4ba 100644
--- a/docs/tutorials/en/analyze-a-products-reservations.md
+++ b/docs/tutorials/en/analyze-a-products-reservations.md
@@ -23,4 +23,4 @@ To check the authorized reservations, that is, those that have not yet had an or
 
 To view orders with the status `Billed`, that is, payment already approved, just click on the number displayed in the column **Itens em manuseio** (Items being handled).
 
-![Reservations GIF](//images.contentful.com/alneenqid6w5/4xUy1O7pUA66UaQkcuU0au/53f39fe9b3cbe2f4c3e2a8e6316e66a9/Reservations.gif)
+![Reservations GIF](https://images.contentful.com/alneenqid6w5/4xUy1O7pUA66UaQkcuU0au/53f39fe9b3cbe2f4c3e2a8e6316e66a9/Reservations.gif)
diff --git a/docs/tutorials/en/antifraud-provider.md b/docs/tutorials/en/antifraud-provider.md
index d9cd807bf..26844ca04 100644
--- a/docs/tutorials/en/antifraud-provider.md
+++ b/docs/tutorials/en/antifraud-provider.md
@@ -46,14 +46,14 @@ Before setting up the VTEX environment, the provider must implement the back-end
 ### 3. Antifraud Provider Administration Panel
 After receiving the access data and deploying the backend, the provider can access the approval tool through VTEX Admin. To do this, you must install the Anti-Fraud Provider App from the Apps menu:
 
-![print5](//images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
+![print5](https://images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
 
 Click on the installed app or access `https://{{AccountName}}.myvtex.com/admin/antifraud-provider`, replacing `{{AccountName}}` with the name of your account on the platform. In this environment, you can register the provider back-end configuration data and perform integration tests.
 
-![print6](//images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
+![print6](https://images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
 
 ### 4. Initial settings
-![print1](//images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
+![print1](https://images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
 
 When you access the environment through the link described in the previous item, you will see a form. Fill in the fields as indicated below:
 
@@ -77,7 +77,7 @@ After completing the fields correctly, the system will check the approved transa
 
 The tests that should be done in your integration before sending it to VTEX evaluation are displayed in the next module. You can select which tests you want to run, but for your integration to go through the analysis of our team, __all tests need to be done__. Therefore, we recommend that all of them remain selected.
 
-![print2](//images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
+![print2](https://images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
 
 ### 5. Testing
 When you click the __Execute tests__ button, the Antifraud Provider will apply the tests in your integration to the different possible scenarios. It's important to remember that __all of them are required__. To run them your service must be in HTTPS. The tests are:
@@ -107,11 +107,11 @@ For each Antifraud Provider Protocol test, we send a specific ID end to return t
 ### 6. Results
 After running the tests, the system returns the results, both positive and negative. The system also provides information on the expected results for each test. Thus, you have more visibility of what should be corrected in case of error.
 
-![print3](//images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
+![print3](https://images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
 
 To visualize in detail each action performed by the integration (and thus to identify possible errors), just click on the __Show logs__ link. A list of the complete information about the events that happened during the test will be displayed below the results.
 
-![print4](//images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
+![print4](https://images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
 
 When your integration has successfully passed all tests, please open a ticket in our [VTEX support](https://help.vtex.com/pt/support "VTEX Help"). However, before opening the ticket, make sure you have the following information:
 
@@ -135,7 +135,7 @@ Use the `https://{{AccountName}}.myvtex.com/admin/license-manager/#/home` URL, r
 Once the integration with your anti-fraud is approved, a connector will be made available for VTEX merchants to configure it on their respective websites. To do this, in addition to the contract with your company, the store will need two keys in hand: "X-PROVIDER-API-AppKey" and "X-PROVIDER-API-AppToken".
 
 An example of how the antifraud settings screen will look for the VTEX store:
-![print8](//images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
+![print8](https://images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
 
 These keys should be made available by you and will serve to identify the store that hired and is using your anti-fraud service.
 
diff --git a/docs/tutorials/en/application-keys.md b/docs/tutorials/en/application-keys.md
index 1de2490c0..988405f84 100644
--- a/docs/tutorials/en/application-keys.md
+++ b/docs/tutorials/en/application-keys.md
@@ -62,7 +62,7 @@ To create internal app keys in your account, follow the steps below:
 
 	You will be redirected to the **My Keys** page, as shown below. This page lists all [internal app keys](#internal-application-keys).
 
-    ![My Keys](//images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/1c98224b6f50673c4567f21e22de4978/image3.png)
+    ![My Keys](https://images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/1c98224b6f50673c4567f21e22de4978/image3.png)
 
     These are the visible fields on the **My Keys** page:
 
@@ -114,7 +114,7 @@ When editing an application key, you can:
 
 Once you have added roles to an application key, it will be displayed on the **Application Keys** page.
 
-![Application Keys](//images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/4ca25e35b379a4a71370c1e07221cf1a/appkeys-en.png)
+![Application Keys](https://images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/4ca25e35b379a4a71370c1e07221cf1a/appkeys-en.png)
 
 These are the visible fields on the **Application Keys** page:
 
diff --git a/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
index 02e8f9701..164eeee4c 100644
--- a/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
@@ -25,7 +25,7 @@ This approval can be done manually through the Orders Management module as shown
 2. Click on the transaction.
 3. Click on **Notify Payment** button.
 
-![NotificarEN](//images.ctfassets.net/alneenqid6w5/19t11NnJzs40wGQqkaeKIu/1d7fee23772ca875bccb59286859c415/NotificarEN.png)
+![NotificarEN](https://images.ctfassets.net/alneenqid6w5/19t11NnJzs40wGQqkaeKIu/1d7fee23772ca875bccb59286859c415/NotificarEN.png)
 
 **After approval of the payment, the order will go through the normal purchase flow.**
 
diff --git a/docs/tutorials/en/apps-overview.md b/docs/tutorials/en/apps-overview.md
index df2bff066..f18886afe 100644
--- a/docs/tutorials/en/apps-overview.md
+++ b/docs/tutorials/en/apps-overview.md
@@ -36,7 +36,7 @@ The Apps menu allows merchants to download new apps directly from the App Store
 
 These operations can be found in the Apps menu of your redesigned Admin.
 
-![Apps Overview menu EN](//images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/76a9830a08af07c0cdd5ebecfb7a5ca9/Apps_Overview_menu_EN.jpg)
+![Apps Overview menu EN](https://images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/76a9830a08af07c0cdd5ebecfb7a5ca9/Apps_Overview_menu_EN.jpg)
 
 See below for more details on the different sections and pages of this feature, which will soon be available in the redesigned Admin. 
 
diff --git a/docs/tutorials/en/assembly-options-app.md b/docs/tutorials/en/assembly-options-app.md
index eaeac0b8d..0a596bef5 100644
--- a/docs/tutorials/en/assembly-options-app.md
+++ b/docs/tutorials/en/assembly-options-app.md
@@ -37,7 +37,7 @@ After installation, the **Catalog > Assembly Options** page will become availabl
 
 In the VTEX Admin, go to **Catalog > Assembly Options** to access a list with all the assembly options available in your store.
 
-![assembly-options-app-en](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
+![assembly-options-app-en](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/b65d786da2a92266eb107b3eeac0f048/assembly-options-app-en.PNG)
 
 Below, you will find the information displayed in the list:
 
diff --git a/docs/tutorials/en/assembly-options-in-vtex-sales-app.md b/docs/tutorials/en/assembly-options-in-vtex-sales-app.md
index d64ee4521..d1b6fb481 100644
--- a/docs/tutorials/en/assembly-options-in-vtex-sales-app.md
+++ b/docs/tutorials/en/assembly-options-in-vtex-sales-app.md
@@ -35,9 +35,9 @@ There are two scenarios for adding services to products in a single cart:
 2. Select the service option you want and click the **Continue to Cart** button.
 3. After completing the process, you can view the selected services in your cart, along with the total order amount.
 
-![Garantia estendida - EN](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/f81df1f138065b8954e3120a7fc0b4b7/Cen_rio_1__T1__-_EN.png)
+![Garantia estendida - EN](https://images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/f81df1f138065b8954e3120a7fc0b4b7/Cen_rio_1__T1__-_EN.png)
 
-![Carrinho - EN](//images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/cec8bd9e2deaac996bf5dbe8af8ab620/Cen_rio_1__T2__-_EN.png)
+![Carrinho - EN](https://images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/cec8bd9e2deaac996bf5dbe8af8ab620/Cen_rio_1__T2__-_EN.png)
 
 **Scenario 2:** Selecting multiple services
 
@@ -53,8 +53,8 @@ There are two scenarios for adding services to products in a single cart:
 
 6.	Click the **Apply** button.
 
-![Garantia estendida - EN](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/f81df1f138065b8954e3120a7fc0b4b7/Cen_rio_1__T1__-_EN.png)
+![Garantia estendida - EN](https://images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/f81df1f138065b8954e3120a7fc0b4b7/Cen_rio_1__T1__-_EN.png)
 
-![Seguro - EN](//images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/09bc8e283906d9472ddc71e79ac3e492/Cen_rio_2__T2__-_EN.png)
+![Seguro - EN](https://images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/09bc8e283906d9472ddc71e79ac3e492/Cen_rio_2__T2__-_EN.png)
 
-![Ordem pedido - EN](//images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/92e7055b292e8e3385e0ee3b1814c38b/Cen_rio_2__T3__-_EN.png)
+![Ordem pedido - EN](https://images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/92e7055b292e8e3385e0ee3b1814c38b/Cen_rio_2__T3__-_EN.png)
diff --git a/docs/tutorials/en/assembly-options.md b/docs/tutorials/en/assembly-options.md
index 9c39b6162..de0561d14 100644
--- a/docs/tutorials/en/assembly-options.md
+++ b/docs/tutorials/en/assembly-options.md
@@ -23,7 +23,7 @@ An assembly option is an [attachment](https://help.vtex.com/en/tutorial/what-is-
 
 In the example below, a store offers multiple assembly options for the Custom Bell product. These options are shown on the product page, where the customer can select the desired options. Depending on the choices, there may be an additional cost for the SKU.
 
-![assembly-option-EN](//images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/585aace6b147a8107f0f5d03faa5db5f/image.png)
+![assembly-option-EN](https://images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/585aace6b147a8107f0f5d03faa5db5f/image.png)
 
 You can combine [SKUs](https://help.vtex.com/en/tutorial/what-is-an-sku--1K75s4RXAQyOuGUYKMM68u) to provide assembly options, such as the Bells add-ons Roman or the Bells add-ons 1-3 lines in the example above. If an item is out of stock, it will be shown as unavailable.
 
@@ -61,7 +61,7 @@ The first elements `[x-y]` are group rules, and between each `#` and `;` are SKU
 | \[0-3\]#10000\[1-2\]**\[1\]**pricetable1;#20000\[0-2\]**\[0\]**pricetable2;#30000\[0-2\]**\[0\]**pricetable3 | This segment defines the default selected quantity for each SKU.  |
 | \[0-3\]#10000\[1-2\]\[1\]**pricetable1**;#20000\[0-2\]\[0\]**pricetable2**;#30000\[0-2\]\[0\]**pricetable3** | The final segment indicates the price table for each item.  | 
 
-![assembly-option-exemplo-EN](//images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/939c084743ddf02d3903af57104f0b39/image.png)
+![assembly-option-exemplo-EN](https://images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/939c084743ddf02d3903af57104f0b39/image.png)
 
 #### Attachment Settings
 
diff --git a/docs/tutorials/en/associating-a-template-with-a-layout.md b/docs/tutorials/en/associating-a-template-with-a-layout.md
index 472f8b351..fddaa01c7 100644
--- a/docs/tutorials/en/associating-a-template-with-a-layout.md
+++ b/docs/tutorials/en/associating-a-template-with-a-layout.md
@@ -35,4 +35,4 @@ This association is made in the layout properties setting. To get there, follow
 6. Select the template you want to associate with this layout.
 7. Type `yes` to confirm the change (this step is necessary because this is a critical change for the site, as the page's front-end will be replaced).
 
-![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tutorials/en/audit.md b/docs/tutorials/en/audit.md
index fe2dc95bc..40a8ece2b 100644
--- a/docs/tutorials/en/audit.md
+++ b/docs/tutorials/en/audit.md
@@ -26,7 +26,7 @@ To access the Audit page in the VTEX Admin, go to **Apps > Installed Apps > Audi
   <p>To view Audit events, you must have a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> associated with the <em>Insights Metrics</em>  <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">resource</a>.</p>
 </div>
 
-![audit-ui-en (1)](//images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/9e040c47cb3220175bf368155f438813/audit-ui-en__1_.png)
+![audit-ui-en (1)](https://images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/9e040c47cb3220175bf368155f438813/audit-ui-en__1_.png)
 
 ## Querying events in Audit
 
@@ -52,7 +52,7 @@ Follow the instructions to search for an event using the filters available in Au
 
     For example, the query in the image below returns results for `Change Promotion Configuration` or `Change Coupon Configuration` actions whose author is `email@mail.com`.
 
-    ![filtros-en (1)](//images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/266db3f0a88fe7e35268d8e2410c0052/filtros-en__1_.png)
+    ![filtros-en (1)](https://images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/266db3f0a88fe7e35268d8e2410c0052/filtros-en__1_.png)
 
 7. Click the `Apply` button to obtain the events found.
 
diff --git a/docs/tutorials/en/authentication.md b/docs/tutorials/en/authentication.md
index 15363d0a5..0096727d4 100644
--- a/docs/tutorials/en/authentication.md
+++ b/docs/tutorials/en/authentication.md
@@ -47,7 +47,7 @@ You need to configure which authentication method will be available in each cont
 
 On the **Authentication** page, you can choose which login methods you want to offer for your store's customers and administrative users accessing the Admin.
 
-![Authentication page](//images.ctfassets.net/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/06ed0a952614213a04bc68fc8fa5fa4e/Tela_de_Autentica____o_EN.png)
+![Authentication page](https://images.ctfassets.net/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/06ed0a952614213a04bc68fc8fa5fa4e/Tela_de_Autentica____o_EN.png)
 
 Follow the steps below to enable the desired login methods:
 
diff --git a/docs/tutorials/en/autocomplete.md b/docs/tutorials/en/autocomplete.md
index e4cac2866..21482684f 100644
--- a/docs/tutorials/en/autocomplete.md
+++ b/docs/tutorials/en/autocomplete.md
@@ -56,22 +56,22 @@ Another advantage for the store's manager is the increase in conversion due to t
 
 This section displays the most searched terms on the website by other customers.
 
-![top-busca-EN](//images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
+![top-busca-EN](https://images.ctfassets.net/alneenqid6w5/2gToQi6Nms00oiWUKUbARZ/a935147445ee66de24f43b5c27498119/top-busca-EN.png)
 
 ## Last searches
 
 This section displays the last searches performed by the customer. This way, it is possible to start the interaction with the search instantly.
 
-![historico-EN](//images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
+![historico-EN](https://images.ctfassets.net/alneenqid6w5/4MGjASLdfoocOJUHqNQZ3S/a1f82e4d16a67dd446bd8b00117a3744/historico-EN.png)
 
 ## Search suggestions
 
 This section displays the terms and categories other users searched related to the search performed at that time. 
 
-![sugest-EN](//images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
+![sugest-EN](https://images.ctfassets.net/alneenqid6w5/1yoepV91SSqKxLr0VVD8AX/4b80f72d4c5c5352c2399a1fbec2489e/sugest-EN.png)
 
 ## Product suggestion
 
 This section shows the products that correspond to the search carried out at that moment. By displaying products related to your search while you are typing, it reduces dropouts and gives the user the possibility to make a more dynamic purchase.
 
-![produtos-EN](//images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
+![produtos-EN](https://images.ctfassets.net/alneenqid6w5/5QMMNF3iCB2428Ycmswtvd/40062662cd777497d54a86eadb13a1d0/produtos-EN.png)
diff --git a/docs/tutorials/en/b2b-organization-general-settings.md b/docs/tutorials/en/b2b-organization-general-settings.md
index 3cbbbdea2..2e44969e5 100644
--- a/docs/tutorials/en/b2b-organization-general-settings.md
+++ b/docs/tutorials/en/b2b-organization-general-settings.md
@@ -29,6 +29,6 @@ In the VTEX Admin, go to **Apps > B2B Organizations and Cost Centers > Organizat
     - Status: Indicates whether the buyer organization is active.
     - Custom fields: Contains additional fields for an organization.
 
-![Configurações gerais organizações - EN](//images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/c2c35b3eb340e1aa5603eafd55c0568a/Configura__es_gerais_organiza__es_-_EN.gif)
+![Configurações gerais organizações - EN](https://images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/c2c35b3eb340e1aa5603eafd55c0568a/Configura__es_gerais_organiza__es_-_EN.gif)
 
 Make sure you click the `Save` button at the top right corner to apply the changes.
diff --git a/docs/tutorials/en/b2b-store-settings.md b/docs/tutorials/en/b2b-store-settings.md
index 97ef5ca54..35698aaae 100644
--- a/docs/tutorials/en/b2b-store-settings.md
+++ b/docs/tutorials/en/b2b-store-settings.md
@@ -28,13 +28,13 @@ On this page, you will see the instructions on how to configure the general sett
 ## Payment Terms
 You can add payment methods by selecting them based on your business needs.  
 Example: debit card, credit card, promissory.
-![ B2B Store Settings - General Settings + Payment Terms](//images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/4efe4d1a37c7b2858fb8f528388e45e5/image1.jpg)
+![ B2B Store Settings - General Settings + Payment Terms](https://images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/4efe4d1a37c7b2858fb8f528388e45e5/image1.jpg)
 
 ## Price Tables
 You can add default prices for the stores you add. Learn more about Price Tables on [Pricing](https://developers.vtex.com/docs/guides/pricing-overview).
 
 ## Trade Policies
- ![ B2B - Políticas comerciais EN](//images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/7d93cbc41f2011d2ca1f1f3090458b2d/image2.jpg)
+ ![ B2B - Políticas comerciais EN](https://images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/7d93cbc41f2011d2ca1f1f3090458b2d/image2.jpg)
 You can directly link your store to trade policies and sales channels.
 
 1. In the **Available trade policies** list, click the trade policy you want to add to your store and then click `Add to Trade Policy`, which will then be displayed in the **Selected trade policies** list.
diff --git a/docs/tutorials/en/b2b-suite-overview.md b/docs/tutorials/en/b2b-suite-overview.md
index 52646340c..cb40caa27 100644
--- a/docs/tutorials/en/b2b-suite-overview.md
+++ b/docs/tutorials/en/b2b-suite-overview.md
@@ -48,7 +48,7 @@ To install B2B Suite, follow the steps below:
 
 3. Click Get App to install.
 
-![Instalação B2B Suite - EN](//images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/fbf0baa072a40dfdf9f89f5130eb82bf/Instala__o_B2B_Suite_-_EN.gif)
+![Instalação B2B Suite - EN](https://images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/fbf0baa072a40dfdf9f89f5130eb82bf/Instala__o_B2B_Suite_-_EN.gif)
 
 ## B2B Suite apps
 
diff --git a/docs/tutorials/en/bank-reconciliations.md b/docs/tutorials/en/bank-reconciliations.md
index eebe6d25d..d541f52e1 100644
--- a/docs/tutorials/en/bank-reconciliations.md
+++ b/docs/tutorials/en/bank-reconciliations.md
@@ -36,7 +36,7 @@ After receiving the bank file and saving it on your machine, as mentioned above
 
 Once you select the file, the platform will begin to process it, and record in the history how many payments were reconciled, with success or error. Payments that have been successfully reconciled will update the status of the orders to Approved Payment.
 
-![upload-file-ret](//images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7dd94c343503e88caa9430ba9319e39/uploadret_EN.JPG)
+![upload-file-ret](https://images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7dd94c343503e88caa9430ba9319e39/uploadret_EN.JPG)
 
 ## View history
 
@@ -48,7 +48,7 @@ Among the details, it is possible to know the bank to which the slip belongs, th
 3. In **History**, click on one of the dates of the bank reconciliation operations performed.
 4. In **More Details**, click **Successfully Reconciled** or **Not Able to Reconcile** to check the details of the transactions carried out in a particular bank. 
 
-![historic-conciliation](//images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/2e2ebac6f5612baa7935e99758612f66/historico_conciliacao_EN.jpg)
+![historic-conciliation](https://images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/2e2ebac6f5612baa7935e99758612f66/historico_conciliacao_EN.jpg)
 
 ## Payclub
 
@@ -59,4 +59,4 @@ Here you can download the payments on the day they were made through redirection
 4. Select the date you want from the calendar.
 5. Click on **Download file**.
 
-![donwload-file-conciliation](//images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/fa25f9754480cf2e41b72b70f95d5740/Download_Concilia____o_EN.JPG)
+![donwload-file-conciliation](https://images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/fa25f9754480cf2e41b72b70f95d5740/Download_Concilia____o_EN.JPG)
diff --git a/docs/tutorials/en/banners.md b/docs/tutorials/en/banners.md
index b128c9f86..c4b758fd9 100644
--- a/docs/tutorials/en/banners.md
+++ b/docs/tutorials/en/banners.md
@@ -34,7 +34,7 @@ On VTEX Admin, the page **Storefront** > **Banners** shows the full list of regi
 * [Edit a banner](#editing-a-banner)
 * [Delete a banner](#deleting-a-banner) 
 
-![banners-intro-en](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
+![banners-intro-en](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/cfc3d93dba914a7a22961741c637c8a7/image.png)
 
 The page shows the following information:
 
diff --git a/docs/tutorials/en/beta-price-configuration.md b/docs/tutorials/en/beta-price-configuration.md
index 48616b423..7ecbe2899 100644
--- a/docs/tutorials/en/beta-price-configuration.md
+++ b/docs/tutorials/en/beta-price-configuration.md
@@ -73,11 +73,11 @@ To create a new rule, follow the steps below:
 
   b. **Activate in specific conditions:** the price table will be activated according to the conditions set in the rule. See the configuration possibilities on the following images:
 
-  ![config-preco-EN](//images.ctfassets.net/alneenqid6w5/2sDqS10pMIv7tmDTgP96si/10028ff45ae241863445061a871e98dd/config-preco-EN.png)
+  ![config-preco-EN](https://images.ctfassets.net/alneenqid6w5/2sDqS10pMIv7tmDTgP96si/10028ff45ae241863445061a871e98dd/config-preco-EN.png)
 
-  ![config-preco2-EN](//images.ctfassets.net/alneenqid6w5/13jaqi9EY1SZ7CdShElb7r/e9ce4f8ca7b2322aacd556fbf5f7cd50/config-preco2-EN.png)
+  ![config-preco2-EN](https://images.ctfassets.net/alneenqid6w5/13jaqi9EY1SZ7CdShElb7r/e9ce4f8ca7b2322aacd556fbf5f7cd50/config-preco2-EN.png)
 
-![config-preco3-EN](//images.ctfassets.net/alneenqid6w5/3EC7hLAQO43LoPlijbXFKM/42d35e6f525408f2920da790b08bd88d/config-preco3-EN.png)
+![config-preco3-EN](https://images.ctfassets.net/alneenqid6w5/3EC7hLAQO43LoPlijbXFKM/42d35e6f525408f2920da790b08bd88d/config-preco3-EN.png)
 
   7. Click on **Confirm**.
 
diff --git a/docs/tutorials/en/billing-module-overview.md b/docs/tutorials/en/billing-module-overview.md
index 7b932a39b..5fbdf33b8 100644
--- a/docs/tutorials/en/billing-module-overview.md
+++ b/docs/tutorials/en/billing-module-overview.md
@@ -23,7 +23,7 @@ To access this section, click on your **profile avatar**, which can be identifie
 Only users with the access profiles of <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> or with <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> resources linked to their access profile can view this section of the VTEX Admin.
   </div>     
 
-![Admin v4 Faturas menu EN](//images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/efc4c8a58bed888f975fa5aa2b0f2fad/Admin_v4_Faturas_menu_EN.jpg)
+![Admin v4 Faturas menu EN](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/efc4c8a58bed888f975fa5aa2b0f2fad/Admin_v4_Faturas_menu_EN.jpg)
 
 See below for more details on the different sections and pages of this feature.
 
diff --git a/docs/tutorials/en/brands.md b/docs/tutorials/en/brands.md
index 6dafd3dfa..64cc2c792 100644
--- a/docs/tutorials/en/brands.md
+++ b/docs/tutorials/en/brands.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Brands** page allows you to view, manage and add brands on Seller Portal. To access the page on VTEX Admin, go to **Catalog** > **Brands**.
 
-![brands-en](//images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/a5d64115e686cda5ebe5e11a8c8b7aa8/brands-en.PNG)
+![brands-en](https://images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/a5d64115e686cda5ebe5e11a8c8b7aa8/brands-en.PNG)
 
 ## Creating a Brand
 To create a new brand, click on the `Create brand` button. Fill in the fields on the __New brand__ modal according to the information below.
diff --git a/docs/tutorials/en/breadcrumb-control.md b/docs/tutorials/en/breadcrumb-control.md
index fdb23b5d8..0183c39c6 100644
--- a/docs/tutorials/en/breadcrumb-control.md
+++ b/docs/tutorials/en/breadcrumb-control.md
@@ -19,7 +19,7 @@ Breadbrumbs improve the in-store browsing experience by encouraging users to exp
 
 In VTEX, the `<vtex.cmc:breadCrumb/>` control is responsible for rendering breadcrumbs like the one below.
 
-![breadcrumb1](//images.contentful.com/alneenqid6w5/4UnYdunXh6MI28k8sS0w8Y/9883ba3a0d5f9f5826313832f9c5a2d0/breadcrumb1.png)
+![breadcrumb1](https://images.contentful.com/alneenqid6w5/4UnYdunXh6MI28k8sS0w8Y/9883ba3a0d5f9f5826313832f9c5a2d0/breadcrumb1.png)
 
 If, as in this example, the user directly accesses the page of a product of the category *Camisetas*, the breadcrumb displayed on the product page will give you the information that the user is in this category (*Camisetas*), which is below the department *Moda masculina*.
 
@@ -42,4 +42,4 @@ Here is an example of the HTML code rendered by the breadcrumb control:
 
 The code above renders the following breadcrumb in the site:
 
-![breadcrumb2](//images.contentful.com/alneenqid6w5/1PxrLYlhNaaUYYoi6oOCe6/06d276039e7e73a39fa15061befffd38/breadcrumb2.png)
+![breadcrumb2](https://images.contentful.com/alneenqid6w5/1PxrLYlhNaaUYYoi6oOCe6/06d276039e7e73a39fa15061befffd38/breadcrumb2.png)
diff --git a/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md b/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md
index 91e953659..234590622 100644
--- a/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md
+++ b/docs/tutorials/en/bringing-app-content-into-the-admin-panel.md
@@ -25,7 +25,7 @@ Open up your favorite text editor and navigate to your project’s folder.
 
 Adding a simple `“admin/“` to the beginning of the page name as well as to the route path should make it look like this:
 
-![2 pages](//images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
+![2 pages](https://images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
 
 ## Fixing dependencies
 
@@ -33,7 +33,7 @@ We must now navigate to the manifest.json file where we list all of our dependan
 
 Let’s add `vtex.admin: “1.x”` to out dependencies. VTEX IO is strict about requiring explicit version.
 
-![3 manifest](//images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
+![3 manifest](https://images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
 
 ## The final touches
 
@@ -47,5 +47,5 @@ Navigate to index.js and add the `componentDidMount()` lifecycle method above th
 
 Your React application should now have the proper URL path, the correct dependencies and an index.js that makes use of React’s lifecycle method to communicate with VTEX (through `window.postmessage`) to terminate the loading process.
 
-![4 final touches](//images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
-![5 completo](//images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
+![4 final touches](https://images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
+![5 completo](https://images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
diff --git a/docs/tutorials/en/buy-one-get-one.md b/docs/tutorials/en/buy-one-get-one.md
index 8e2ea500d..5f5726450 100644
--- a/docs/tutorials/en/buy-one-get-one.md
+++ b/docs/tutorials/en/buy-one-get-one.md
@@ -52,7 +52,7 @@ In this section, we provide information on the promotion overview.
 - **Additional information (optional):** Allows you to add name and value details to the promotion.
 - **Promotion is highlighted:** Adds a tag with the promotion name,  which is displayed in the window display and on the product page. This tag will only be added if you use the right promotion display control in the template. `<vtex.cmc:discountHightLight>`.
 
-![Promotion Overview](//images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/fb5019d7359026929f45631e94e2f454/Promotion_Overview.png)
+![Promotion Overview](https://images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/fb5019d7359026929f45631e94e2f454/Promotion_Overview.png)
 
 ## Restrict this promotion to seller products
 
@@ -67,7 +67,7 @@ For the promotion to be valid for all sellers, leave the field blank.
   <p>It is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:</p><ol>1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.</ol><ol>2. Leave the field blank.  In this way, all sellers will be included in the promotion.</ol>
 </div>
 
-![Restrict this promotion to seller products](//images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/32b26e784595d4551700c022fc539598/Restrict_this_promotion_to_seller_products.png)
+![Restrict this promotion to seller products](https://images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/32b26e784595d4551700c022fc539598/Restrict_this_promotion_to_seller_products.png)
 
 ## Trade policy
 
@@ -80,7 +80,7 @@ In this section, you can set the trade policies valid for the promotion. You can
 
 For the promotion to be valid for all trade policies, leave the selection empty.
 
-![Trade Policy](//images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/2d378d9c081945a7128525036ed1f9e4/Trade_policy.png)
+![Trade Policy](https://images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/2d378d9c081945a7128525036ed1f9e4/Trade_policy.png)
 
 # 2. Buy One Get One
 
@@ -98,7 +98,7 @@ In this section, you can define the collections, SKUs, and minimum quantity for
 <p>A Buy One Get One promotion can be created with a maximum of 100 different SKUs at the same time.<p>
 </div>
 
-![Buy One Get One](//images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c521b34d5694bf3712f5450f32839a91/Buy_One_Get_One.png)
+![Buy One Get One](https://images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c521b34d5694bf3712f5450f32839a91/Buy_One_Get_One.png)
 
 # 3. Conditions for the promotion to be valid
 
@@ -111,7 +111,7 @@ In this section, we will detail the conditions you must apply for a promotion to
 - **Utm_source:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion.
 - **Utm_campaign:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion.
 
-![What are the conditions for the promotion to be valid?](//images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/935d35fb86b2e6931c238d60e14f2872/What_are_the_conditions_for_the_promotion_to_be_valid.png)
+![What are the conditions for the promotion to be valid?](https://images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/935d35fb86b2e6931c238d60e14f2872/What_are_the_conditions_for_the_promotion_to_be_valid.png)
 
 # 4. Restrictions and limitations of use
 
@@ -122,4 +122,4 @@ In this section, you will find important information about the promotion conditi
 - Only for the same items: If this option is activated, the promotion is only applied if the minimum quantity of items (previously added) is reached using the same SKU in the cart. If this option is deactivated, the promotion will be applied even when the minimum quantity of items is added to the cart, regardless of whether the SKUs are different or the same.
 - Apply with other promotions: Allows this promotion to be applied to the cart in combination with other promotions that give the same discount type.
 
-![Restrictions and limitations of use](//images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/3786a7a5b6067de6410cabfe402325b4/Restrictions_and_limitations_of_use.png)
+![Restrictions and limitations of use](https://images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/3786a7a5b6067de6410cabfe402325b4/Restrictions_and_limitations_of_use.png)
diff --git a/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md b/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
index d0adcf697..05aa9acd4 100644
--- a/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
+++ b/docs/tutorials/en/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
@@ -25,4 +25,4 @@ To do this, follow the steps below:
 For White Label Sellers there is a limit of 50 items with the same SKU in the shopping cart. You can change this limit upon request to customer
  [support](https://help.vtex.com/en/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe).
 
-![Carrinho Max EN](//images.ctfassets.net/alneenqid6w5/2NKRULRqqck8QmGg8oOSCs/d7b5c44cca5cc1e4ca19abcb80dfd379/Carrinho_Max_EN.png)
+![Carrinho Max EN](https://images.ctfassets.net/alneenqid6w5/2NKRULRqqck8QmGg8oOSCs/d7b5c44cca5cc1e4ca19abcb80dfd379/Carrinho_Max_EN.png)
diff --git a/docs/tutorials/en/campaign-audiences-list.md b/docs/tutorials/en/campaign-audiences-list.md
index d39e43ad8..3e3d8cb92 100644
--- a/docs/tutorials/en/campaign-audiences-list.md
+++ b/docs/tutorials/en/campaign-audiences-list.md
@@ -17,7 +17,7 @@ subcategory: 2cI57eZ3ZiWSeaQs26Gwys
 
 Your store's campaign audience list is available in the VTEX Admin, on the *Promotions > Campaign audience* page, illustrated below.
 
-![lista-audiencias-campanha-en](//images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/cec59b7c69282287586b1db574aedfe7/lista-audiencias-campanha-en.png)
+![lista-audiencias-campanha-en](https://images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/cec59b7c69282287586b1db574aedfe7/lista-audiencias-campanha-en.png)
 
 On this page, you can perform the following actions:
 
@@ -50,7 +50,7 @@ The campaign audiences are displayed in _cards_ containing the following informa
 
 To view the [archived](#archiving-a-campaign-audience) campaign audiences, next to the **Show** option, click **Archived**, as illustrated below:
 
-![toggle-audiencias-campanha-arquivadas-en](//images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/853066310add51cccf742dc10ea0283b/toggle-audiencias-campanha-arquivadas-en.png)
+![toggle-audiencias-campanha-arquivadas-en](https://images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/853066310add51cccf742dc10ea0283b/toggle-audiencias-campanha-arquivadas-en.png)
 
 To return to the campaign audiences which have not been archived, click **Not Archived**.
 
diff --git a/docs/tutorials/en/campaign-audiences.md b/docs/tutorials/en/campaign-audiences.md
index 2475bf9a0..e3bf0698c 100644
--- a/docs/tutorials/en/campaign-audiences.md
+++ b/docs/tutorials/en/campaign-audiences.md
@@ -27,7 +27,7 @@ For example: When creating a campaign audience for the fashion segment, you can
 
 The target audience segments the campaign audience's eligible users and conditions. If the campaign audience is active, the promotions associated with the campaign audience will be activated by meeting all the criteria defined for the target audience.
 
-![campanha-en](//images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/5f7c4bb9f35c674f4959d136943b6808/campanha-en.png)
+![campanha-en](https://images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/5f7c4bb9f35c674f4959d136943b6808/campanha-en.png)
 
 When the campaign is activated, eligible for the purchase context and all its restrictions are met, it does not necessarily mean that all the campaign audience promotions associated with it will be applied. The restrictions defined in the[ campaign promotion](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume) must also be met.
 
diff --git a/docs/tutorials/en/campaign-promotion.md b/docs/tutorials/en/campaign-promotion.md
index b1c66924d..a08e0c890 100644
--- a/docs/tutorials/en/campaign-promotion.md
+++ b/docs/tutorials/en/campaign-promotion.md
@@ -122,7 +122,7 @@ For the promotion to be valid for all trade policies, leave it blank.
 
 In this section, you need to choose whether this promotion will apply to all products in your store or only to specific products, as illustrated below.
 
-![promocoes-restricao-en](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
+![promocoes-restricao-en](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
 
 If you want the promotion to apply to your entire catalog, select the **Apply to all products** option.
 
@@ -132,7 +132,7 @@ You can add or remove **Categories**, **Brands**, **Collections**, **Products**
 
 See an example below. In this case, the promotion includes all products from the category **Home Appliances** whose brand is **Brastemp**, except the product **Refrigerator 100**.
 
-![exemplo-en](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
+![exemplo-en](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
 
 In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
 
diff --git a/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md
index 593ed70d3..afa76347c 100644
--- a/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/en/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -21,7 +21,7 @@ In the tab *Shipping strategy* you can register your logistics route, including
 The new features on the **Shipping policy** registration page give you more flexibility when setting up your delivery strategy. In the previous version, there was the section *Time setup*, in which you could select the *Working hours*, *Cut-off times* or *Scheduled Delivery* for a carrier. 
 
 **Previous version**
-![EN Configurações de tempo versão antiga](//images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/5c6dfcad4a2511c33c6f2a5a0f0d358a/EN_Configura____es_de_tempo_vers__o_antiga.jpg)
+![EN Configurações de tempo versão antiga](https://images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/5c6dfcad4a2511c33c6f2a5a0f0d358a/EN_Configura____es_de_tempo_vers__o_antiga.jpg)
 
 In the new version, we’ve:  
 - Changed option names to make it more clear to users.  
@@ -29,7 +29,7 @@ In the new version, we’ve:
 - Added an option to define your delivery capacity, in order to schedule deliveries based on your operation reality.   
 
 **Beta version**
-![EN Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/f4883976b951e19591b4b75b228f9a10/EN_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![EN Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/f4883976b951e19591b4b75b228f9a10/EN_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 ## Pickup time
 
@@ -46,7 +46,7 @@ Just like in the previous version, you can't set up the “Shipping time window
 Previously, you could only choose the *Scheduled Delivery* function deprived of the *Business hours*. You can now set up the *Scheduled Delivery* option together with *Business hours* for your client to choose the most suitable shipping method during the order checkout. Please check the fields to fill-in when setting up this option.
 
 **Beta version**
-![EN entrega agendada](//images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/7165d0778182cb771f137637ef8e2a2b/EN_entrega_agendada.jpg)
+![EN entrega agendada](https://images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/7165d0778182cb771f137637ef8e2a2b/EN_entrega_agendada.jpg)
 
 - **Max. range of delivery**: this field must be filled according to your logistics operation. Please define the time period that the carrier takes to do a scheduled delivery, from the order to the delivery confirmation.  
 - **Set operational capacity**: depending on the characteristics of your operation, and on how the carrier sends its products, you might prefer to define a delivery capacity in the number of items or number of orders. For example, if your store is in the supermarket sector, and the means of transportation for the scheduled delivery is by motorcycle, only a limited number of items will fit into the motorcycle storage. For this reason, we recommend that you select “items” as units. However, if your operation already has a few items per order, you might prefer to define `orders` as units, for example.  
diff --git a/docs/tutorials/en/catalog-overview.md b/docs/tutorials/en/catalog-overview.md
index bd3b27cce..bc54f8de1 100644
--- a/docs/tutorials/en/catalog-overview.md
+++ b/docs/tutorials/en/catalog-overview.md
@@ -15,7 +15,7 @@ legacySlug: catalog-overview
 subcategory: 
 ---
 
-![Catalog overview (header)](//images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/ecec695214ce50acf65453efb6668247/image1.jpg)
+![Catalog overview (header)](https://images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/ecec695214ce50acf65453efb6668247/image1.jpg)
 Catalog is your store's administration module for configuring the features related to your ecommerce products. To make products available for customers on your website, you need to add them to this module. 
 
 In this article, you will find an overview of the catalog items and its features.
@@ -25,7 +25,7 @@ Category is the second categorization level of your store, under [Departments](h
 
 The **Categories** page allows you to view and manage your store's category trees, as illustrated below.
 
-![Catalog structure](//images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/1716c9232b7a09d5477021ac875fe690/image4.png)
+![Catalog structure](https://images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/1716c9232b7a09d5477021ac875fe690/image4.png)
 
 Learn how to add a category in the tutorial [Registering a category](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206). If you want to change or disable a category, follow the steps in the tutorial [Disabling and reorganizing categories](https://help.vtex.com/en/tutorial/disabling-and-reorganizing-categories--tutorials_264).
 
diff --git a/docs/tutorials/en/categories.md b/docs/tutorials/en/categories.md
index ba5108b37..766528d62 100644
--- a/docs/tutorials/en/categories.md
+++ b/docs/tutorials/en/categories.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Categories** page allows you to view and manage the category trees registered on Seller Portal. To access the page on VTEX Admin, go to **Catalog** > **Categories**.
 
-![categorias-en](//images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/d9d795232e14fe8300461c0d32dfb10e/categorias-en.PNG)
+![categorias-en](https://images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/d9d795232e14fe8300461c0d32dfb10e/categorias-en.PNG)
 
 From the category tree, you can:
 
@@ -51,7 +51,7 @@ To find a category, you must type the name of the category in the search bar abo
 ## Browsing the category tree
 The categories page displays the outermost levels of the categories. Click on the <i class="fas fa-angle-right"></i> icon to access the subcategories, as shown below.
 
-![arvore-categoria-EN](//images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/362b5e61773ad44d2e00d7f0813339d0/arvore-categoria-EN.gif)
+![arvore-categoria-EN](https://images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/362b5e61773ad44d2e00d7f0813339d0/arvore-categoria-EN.gif)
 
 To view the information for a category, click on its name. 
 
diff --git a/docs/tutorials/en/category-registration-fields.md b/docs/tutorials/en/category-registration-fields.md
index d9e5ba82c..2d9513c6b 100644
--- a/docs/tutorials/en/category-registration-fields.md
+++ b/docs/tutorials/en/category-registration-fields.md
@@ -43,8 +43,8 @@ To better understand the meaning of each category registration field, see the fu
 - __Score (used for search ordering):__ value used to set the priority on the search result page. To understand more about Score, access our article: [How does the score field work?](https://help.vtex.com/en/tutorial/how-does-the-score-field-work--1BUZC0mBYEEIUgeQYAKcae).
 - __Product display mode:__ defines how SKUs will be displayed on the product page. See below the options for this field:
   - __List of SKUs:__ All SKUs in the department or category in question will be displayed in list format. Each one with its Buy button on the side.
-  ![1Lista.en](//images.ctfassets.net/alneenqid6w5/52RUiCTYT5JeL6Huo53nSh/1b3c9713709f10be3e88ae5925128de5/Lista.en.png)
+  ![1Lista.en](https://images.ctfassets.net/alneenqid6w5/52RUiCTYT5JeL6Huo53nSh/1b3c9713709f10be3e88ae5925128de5/Lista.en.png)
   - __Icons with radio selection (radio box)__ All SKUs in this department/category will need to be selected through radio selection.
-  ![RadioBox.en](//images.ctfassets.net/alneenqid6w5/bbx5D8m5cXuac0w1LZGc2/9c91af75ed6af97eebf70207880e7708/RadioBox.en.png)
+  ![RadioBox.en](https://images.ctfassets.net/alneenqid6w5/bbx5D8m5cXuac0w1LZGc2/9c91af75ed6af97eebf70207880e7708/RadioBox.en.png)
   - __Following definition of the SKU specification:__ all SKUs in this department/category will be selected according to the specification tab on the SKU registration form. The preconfigured options are Combo or Radio.
-  ![Campos.en](//images.ctfassets.net/alneenqid6w5/4opYmeQPk3r8uux4ldosbh/d14bec6c5bdb9d6b0e6b4ab87bd20ef6/Campos.en.png)
+  ![Campos.en](https://images.ctfassets.net/alneenqid6w5/4opYmeQPk3r8uux4ldosbh/d14bec6c5bdb9d6b0e6b4ab87bd20ef6/Campos.en.png)
diff --git a/docs/tutorials/en/category-variations-and-attributes-mapping.md b/docs/tutorials/en/category-variations-and-attributes-mapping.md
index 6630bc6bf..26ebed524 100644
--- a/docs/tutorials/en/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/en/category-variations-and-attributes-mapping.md
@@ -25,7 +25,7 @@ With this feature, you can categorize your products in Mercado Livre and also cr
 
 The mapping will only be done once for each category. This means that once you have done the mapping, new products will be integrated directly into the correct category (and their variations and attributes).
 
-- [Download here](//assets.ctfassets.net/alneenqid6w5/qyDp7OSL5YAGaGKagWiK0/07900f41a952a460185e18f9db190eb1/Planilha_de_Mapeamento_do_Mercado_Livre.xlsx) the __Mercado Livre Mapping Spreadsheet__ in the format `.xlsx`.
+- [Download here](https://assets.ctfassets.net/alneenqid6w5/qyDp7OSL5YAGaGKagWiK0/07900f41a952a460185e18f9db190eb1/Planilha_de_Mapeamento_do_Mercado_Livre.xlsx) the __Mercado Livre Mapping Spreadsheet__ in the format `.xlsx`.
 
 The same spreadsheet will be used in the three steps described below (categorization, variations and attributes). Follow the step by step, filling in the fields of the mapping spreadsheet as follows.
 
@@ -34,7 +34,7 @@ The same spreadsheet will be used in the three steps described below (categoriza
 Here we will do the correspondence between your categories in VTEX with those used by Mercado Livre.
 
 1. __CategoryId:__ it is the category ID in VTEX. You can find it next to the name of each category as you expand the categories tree.
-2. __MeliCategoryId:__ it is the category ID in Mercado Livre. [Click here](//assets.ctfassets.net/alneenqid6w5/4IGh23L6buEm8s8IWYwISS/f8f1e862f39f8f0052b1b60a696aadd6/MercadoLivre_CategoriasFixas.xlsx) to download the worksheet where these values are available. If you prefer, access this [Mercado Livre API](https://api.mercadolibre.com/sites/MLB/categories) to query the categories, which are always updated there.
+2. __MeliCategoryId:__ it is the category ID in Mercado Livre. [Click here](https://assets.ctfassets.net/alneenqid6w5/4IGh23L6buEm8s8IWYwISS/f8f1e862f39f8f0052b1b60a696aadd6/MercadoLivre_CategoriasFixas.xlsx) to download the worksheet where these values are available. If you prefer, access this [Mercado Livre API](https://api.mercadolibre.com/sites/MLB/categories) to query the categories, which are always updated there.
 
 >_`Ex:` you have the following tree in __VTEX __:_
 
@@ -64,7 +64,7 @@ In Mercado Livre, there are two types of variation: the __mandatory__ ones and t
 
 - Mandatory Variations
 
-If your product is a `Footwear`, `Clothing`, `Bag`, `Belt` or `Home Appliance`, __you will need to map the required variations__. Their name must follow exactly the values accepted by the marketplace. [Download here](//assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/d338d66ed72d2183802c546e88ce1f3e/Planilha_de_Variac__o__es_do_Mercado_Livre.xlsx) the __Mercado Livre Variations Spreadsheet__ to check the accepted values according to each type of product.
+If your product is a `Footwear`, `Clothing`, `Bag`, `Belt` or `Home Appliance`, __you will need to map the required variations__. Their name must follow exactly the values accepted by the marketplace. [Download here](https://assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/d338d66ed72d2183802c546e88ce1f3e/Planilha_de_Variac__o__es_do_Mercado_Livre.xlsx) the __Mercado Livre Variations Spreadsheet__ to check the accepted values according to each type of product.
 
 - Customizable Variations
 
diff --git a/docs/tutorials/en/change-a-placeholder-title.md b/docs/tutorials/en/change-a-placeholder-title.md
index 16e91821c..af1b6e194 100644
--- a/docs/tutorials/en/change-a-placeholder-title.md
+++ b/docs/tutorials/en/change-a-placeholder-title.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 The title of a placeholder is what appears in the right corner of the object, as the image below indicates.
 
-![cms-placeholder en](//images.ctfassets.net/alneenqid6w5/7kCsbNAZZ6kGiGe6IMGGye/02545dd609ed095ee074d85134668028/placeholder_destaque_EN.png)
+![cms-placeholder en](https://images.ctfassets.net/alneenqid6w5/7kCsbNAZZ6kGiGe6IMGGye/02545dd609ed095ee074d85134668028/placeholder_destaque_EN.png)
 
 The text that is entered in this field is what will be displayed as a placeholder title on the store's website.
 
@@ -26,7 +26,7 @@ To change the title of a placeholder, just follow the steps below:
 1. Click the title.
 
 2. Insert the new title.
-![placeholder-change-name en](//images.ctfassets.net/alneenqid6w5/2T3rBaF3RYIukMyeWOacI/e17ee1fd57027e899f409194f9bfe99e/change_name_E.png)
+![placeholder-change-name en](https://images.ctfassets.net/alneenqid6w5/2T3rBaF3RYIukMyeWOacI/e17ee1fd57027e899f409194f9bfe99e/change_name_E.png)
 
 3. Click __Rename__.
 
diff --git a/docs/tutorials/en/change-seller.md b/docs/tutorials/en/change-seller.md
index 68c37628c..316ce5216 100644
--- a/docs/tutorials/en/change-seller.md
+++ b/docs/tutorials/en/change-seller.md
@@ -26,13 +26,13 @@ Sellers can be changed in two situations:
 - Seller cancels the order.
 - Marketplace decides to change the seller.
 
-![seller_cancela_pedido_EN](//images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/de157152dd35da3598e6345114c7e90e/seller_cancela_pedido_EN.png)
+![seller_cancela_pedido_EN](https://images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/de157152dd35da3598e6345114c7e90e/seller_cancela_pedido_EN.png)
 
 You can [set the time window to change seller from 0 to 30 days](https://developers.vtex.com/vtex-rest-api/reference/updatewindowtochangeseller); by default, it is two days. When the window to change seller is set to 0 days, there is not an actual period for switching sellers, so even though the feature is configured, it does not work in practice, and the order proceeds to cancellation.
 
 Upon being notified by the seller about the order cancellation, the marketplace can configure how many days they have to decide whether to cancel the purchase or change the seller. But pay attention: if the marketplace chooses to change sellers, the decision to inform customers of such changes is the marketplace’s responsibility.
 
-![mkt_cancela_seller_EN](//images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/7a5c5687cb444e4ddf4a41a64dec6ff4/mkt_cancela_seller_EN.png)
+![mkt_cancela_seller_EN](https://images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/7a5c5687cb444e4ddf4a41a64dec6ff4/mkt_cancela_seller_EN.png)
 
 ## Limitations
 
diff --git a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
index dec01d3a2..b44617708 100644
--- a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -34,7 +34,7 @@ After [enabling the functionality](https://developers.vtex.com/vtex-rest-api/doc
 3. Change the price to the desired value and press `ENTER`.
 4. Click `Close order`.
 
-![manualprice](//images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/56a551927294fedcaf127cfdb3a8f2a1/manualprice.gif)
+![manualprice](https://images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/56a551927294fedcaf127cfdb3a8f2a1/manualprice.gif)
 
 In addition to the configuration on the Checkout screen, the price of a product can also be modified through the [Change Price](https://developers.vtex.com/vtex-rest-api/reference/pricechange) API, learn more in [Setting the price of an item manually](https://developers.vtex.com/vtex-rest-api/docs/enable-the-manual-price#setting-the-price-of-an-item-manually).
 
diff --git a/docs/tutorials/en/changing-a-pages-body-class.md b/docs/tutorials/en/changing-a-pages-body-class.md
index 76a527222..55f3e114a 100644
--- a/docs/tutorials/en/changing-a-pages-body-class.md
+++ b/docs/tutorials/en/changing-a-pages-body-class.md
@@ -23,13 +23,13 @@ The templates used by store layouts, by default, don't carry any class in their
 
 See, for example, the Department template code.
 
-![changeBodyClass1](//images.contentful.com/alneenqid6w5/pbQCDMUz3qO0q4SuwYaq4/7ebd6ca8a0af6cbce899535b83cd719a/changeBodyClass1.jpg)
+![changeBodyClass1](https://images.contentful.com/alneenqid6w5/pbQCDMUz3qO0q4SuwYaq4/7ebd6ca8a0af6cbce899535b83cd719a/changeBodyClass1.jpg)
 
 It has an `id`, but not a `class`.
 
 However, when loading a layout that uses this template, we note that the `departmento` class has been added to the body of the page.
 
-![changeBodyClass2](//images.contentful.com/alneenqid6w5/132c4r8rtGowUkOYe4YUaM/6b4a3bd0a9fc5f65fe1d950484088ba1/changeBodyClass2.jpg)
+![changeBodyClass2](https://images.contentful.com/alneenqid6w5/132c4r8rtGowUkOYe4YUaM/6b4a3bd0a9fc5f65fe1d950484088ba1/changeBodyClass2.jpg)
 
 That is, the system inserts this class automatically.
 
diff --git a/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
index 225ef50ab..1a9a60afb 100644
--- a/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
@@ -51,8 +51,8 @@ That is, I'm using the variables `preposicaonomeloja2` and `nomeloja`.
 When using variables to compose a text, replace the <code>#</code> symbol with <code>@</code>. That is, <b>#variable#</b> becomes <b>@variable@</b>.
 </div>
 
-![textos-importantes en](//images.ctfassets.net/alneenqid6w5/3ck7V4j6wgygm0qE2ia2m8/ec2d596e8fbee37f53d38568d797a401/textos_importantes_en.png)
-![exemplos-textos-importantes en](//images.ctfassets.net/alneenqid6w5/3qJmU7aPIcUowc6SkaYoSS/4c7d666cf29ef651c19ee837c9f42a75/3_en.png)
+![textos-importantes en](https://images.ctfassets.net/alneenqid6w5/3ck7V4j6wgygm0qE2ia2m8/ec2d596e8fbee37f53d38568d797a401/textos_importantes_en.png)
+![exemplos-textos-importantes en](https://images.ctfassets.net/alneenqid6w5/3qJmU7aPIcUowc6SkaYoSS/4c7d666cf29ef651c19ee837c9f42a75/3_en.png)
 
 As I defined the content of the first variable to be "to" and the second one is "World Shopping", the final text rendered on the site will be "Welcome to World Shopping".
 
diff --git a/docs/tutorials/en/changing-the-total-cost-of-the-order.md b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
index 35290d784..c5de941a9 100644
--- a/docs/tutorials/en/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
@@ -28,13 +28,13 @@ To make the change, follow the steps below:
 3. Click the order to access the **Order details page**.        
 4. Go to the **Total cost of the order** section on the right side of the Order Details page.    
 5. Click `Change final cost`.    
-![valorfinalEN](//images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/22a8836f14fd64c2f17257c60e711a8a/valorfinalEN__1_.png)  
+![valorfinalEN](https://images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/22a8836f14fd64c2f17257c60e711a8a/valorfinalEN__1_.png)  
 6. On the **Change value** page, fill in the required fields.  
 7. Fill in the required fields:  
     * **Value:** Select Discount or Increase and enter the amount corresponding to what you want to change.    
     * **Reason:** indicate why you are making this change.  
 8. On the right side of the page click `Submit`.  
-![Alterar valorEN](//images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/91ea6db5cdf47879f616f2a17e31c542/Alterar_valorEN.png)
+![Alterar valorEN](https://images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/91ea6db5cdf47879f616f2a17e31c542/Alterar_valorEN.png)
 
 Changes to the order cost will be updated in the "Items to invoice" and "Order History" sections. Note that the order total will also change.
 
diff --git a/docs/tutorials/en/changing-tracking-data.md b/docs/tutorials/en/changing-tracking-data.md
index 717657ba0..91fd2a88e 100644
--- a/docs/tutorials/en/changing-tracking-data.md
+++ b/docs/tutorials/en/changing-tracking-data.md
@@ -38,4 +38,4 @@ To manually change an order's data, follow the steps below:
     * **Select carrier:** select which carrier will deliver the order.
 7. Click `Save`.
 
-![FaturaEN](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
+![FaturaEN](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
diff --git a/docs/tutorials/en/check-order-delivery-details.md b/docs/tutorials/en/check-order-delivery-details.md
index 67688bd1f..91e0d1835 100644
--- a/docs/tutorials/en/check-order-delivery-details.md
+++ b/docs/tutorials/en/check-order-delivery-details.md
@@ -45,7 +45,7 @@ To see these details, do a [shipping simulation](/en/tutorial/freight-simulation
 6. Enter the zip code of the order.
 7. Click on __Shipping Simulation__.
 
-![gerenciamento-pedidos-filtro-hoje en](//images.ctfassets.net/alneenqid6w5/9qtBlqEOicqQMqqGmuOWU/86e3bb19ce13e8880561f715f1d4b0d8/simular-frete_en.png)
+![gerenciamento-pedidos-filtro-hoje en](https://images.ctfassets.net/alneenqid6w5/9qtBlqEOicqQMqqGmuOWU/86e3bb19ce13e8880561f715f1d4b0d8/simular-frete_en.png)
 
 For each carrier considered in the simulation, you can see the details of the corresponding order. To do this, click __show details__. 
 
diff --git a/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md b/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md
index 0431a1f81..c6e62b3a3 100644
--- a/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md
+++ b/docs/tutorials/en/checking-how-an-order-delivery-deadline-was-calculated.md
@@ -23,7 +23,7 @@ Let's say you want to know what criteria the platform used to calculate the deli
 
 First, let's enter the __All Orders__ module to see the order.
 
-![1](//images.ctfassets.net/alneenqid6w5/2tlBnsKXyuMxuCI2U2Ekyi/35c860bb303a575b221fd1662e749867/1.png)
+![1](https://images.ctfassets.net/alneenqid6w5/2tlBnsKXyuMxuCI2U2Ekyi/35c860bb303a575b221fd1662e749867/1.png)
 
 >In the upper right corner, you see the __date in which the order was made__ (MAY 6 2019).
 >And in the bottom of the screen, you see the __order delivery deadline__ (MAY 22 2019).
@@ -33,25 +33,25 @@ Now let's enter the __Inventory & shipping__ module and simulate the freight of
 To do this, follow the steps below:
 
 1. In the VTEX Admin, go to **Shipping > Shipping Simulator**, or type *Shipping Simulator* in the search bar at the top of the page.  
-2. Enter the name or ID of each SKU that was in the shopping cart of the order that you want to investigate, including the quantity of each of them.![2](//images.ctfassets.net/alneenqid6w5/SCHsOOepDsyafXnm2pWJW/58cb84906928bb1295fad1d807bd737d/2.png)
+2. Enter the name or ID of each SKU that was in the shopping cart of the order that you want to investigate, including the quantity of each of them.![2](https://images.ctfassets.net/alneenqid6w5/SCHsOOepDsyafXnm2pWJW/58cb84906928bb1295fad1d807bd737d/2.png)
 3. Enter the purchase order's zip code.
 4. Click __Shipping simulation__.
 
 In the example below, note that 4 carriers were considered, and 12 were disregarded.
 
-![3](//images.ctfassets.net/alneenqid6w5/1iMnSymiQdjkdd8uC2RRGN/be814f59861f03bea128f4307151c457/3.png)
+![3](https://images.ctfassets.net/alneenqid6w5/1iMnSymiQdjkdd8uC2RRGN/be814f59861f03bea128f4307151c457/3.png)
 
 Checking again the order details page, we see that the type of delivery chosen by the customer for this order was __Expressa__, and that the carrier chosen by the platform to make the delivery was __Expressa & CO__.
 
-![4](//images.ctfassets.net/alneenqid6w5/5CnczmPwairE2lypuLgeUM/64ee3a9cffba79370182c935e5d44073/4.png)
+![4](https://images.ctfassets.net/alneenqid6w5/5CnczmPwairE2lypuLgeUM/64ee3a9cffba79370182c935e5d44073/4.png)
 
 Therefore, returning to the freight simulation, in the Shipping menu, we conclude that the first option was chosen for this delivery - and that therefore the total delivery time for the order was 12 days.
 
-![5](//images.ctfassets.net/alneenqid6w5/euQuUd8FDcK5NE9wsLbp7/498df87eb1a5eaa10d1c32f63c63e7f6/5.png)
+![5](https://images.ctfassets.net/alneenqid6w5/euQuUd8FDcK5NE9wsLbp7/498df87eb1a5eaa10d1c32f63c63e7f6/5.png)
 
 Now just click __show details__ to see the cost times that were used to calculate this deadline.
 
-![2019-06-05 17 52 13-Shipping simulator](//images.ctfassets.net/alneenqid6w5/3nsjSgTBJEhVTGZr90nFXa/bd883156e87ede57fae70c3d05d516f5/2019-06-05_17_52_13-Shipping_simulator.png)
+![2019-06-05 17 52 13-Shipping simulator](https://images.ctfassets.net/alneenqid6w5/3nsjSgTBJEhVTGZr90nFXa/bd883156e87ede57fae70c3d05d516f5/2019-06-05_17_52_13-Shipping_simulator.png)
 
 Each of the three cost times corresponds to what was defined for the three steps of the logistics route: stock, dock and carrier.
 
diff --git a/docs/tutorials/en/checkout-vtex-overview.md b/docs/tutorials/en/checkout-vtex-overview.md
index da54d3d79..dd6bf5758 100644
--- a/docs/tutorials/en/checkout-vtex-overview.md
+++ b/docs/tutorials/en/checkout-vtex-overview.md
@@ -35,7 +35,7 @@ The steps below describe the customer's purchase experience and the way that Che
 
 Every time a customer changes something in the cart (adds or removes items), or every time the Checkout screen is updated, the following Checkout internal process chain is performed.
 
-![Checkout overview](//images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/1c2b515127000db8b88c3a2cfa5996d0/Checkout_Overview_EN.png)
+![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/1c2b515127000db8b88c3a2cfa5996d0/Checkout_Overview_EN.png)
 
 <div class="alert alert-info">
 If one or more items selected by the customer are eligible for delivery by a <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#">Seller white label</a>, the seller responsible for delivering the items will be chosen based on shipping simulations, as shown in the right side of the picture. Learn more in <a href="https://help.vtex.com/en/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Selecting white label sellers</a>.
diff --git a/docs/tutorials/en/cms-folder-structure.md b/docs/tutorials/en/cms-folder-structure.md
index a0b766c1e..3b1638a52 100644
--- a/docs/tutorials/en/cms-folder-structure.md
+++ b/docs/tutorials/en/cms-folder-structure.md
@@ -33,7 +33,7 @@ These are the folders that every store needs to have in the CMS to ensure the co
 
 See below these basic folders in the CMS:
 
-![pastasObrigatorias](//images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
+![pastasObrigatorias](https://images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
 
 These folders come by default in the environment of all VTEX stores.
 
diff --git a/docs/tutorials/en/cms-overview.md b/docs/tutorials/en/cms-overview.md
index c040def75..9783435ba 100644
--- a/docs/tutorials/en/cms-overview.md
+++ b/docs/tutorials/en/cms-overview.md
@@ -15,7 +15,7 @@ legacySlug: cms-overview
 subcategory: 3PNmhq67KMmGTBSfIWJdcQ
 ---
 
-![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/19a53d3f1e02f7f01e1a4a6250da2b20/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System) is a feature dedicated to manage content in a constant and practical manner.
 
diff --git a/docs/tutorials/en/cms-store-overview.md b/docs/tutorials/en/cms-store-overview.md
index 43e21848d..d7cde92f6 100644
--- a/docs/tutorials/en/cms-store-overview.md
+++ b/docs/tutorials/en/cms-store-overview.md
@@ -19,7 +19,7 @@ The **Store** page allows you to set up your SEO configurations, enable performa
 
 In the VTEX Admin, access **Store Settings > Storefront > Store**, and take a look at the main tools available on the interface.
 
-![CMS Store](//images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/19924b9aeffed7d9cba408245a46d365/store-en-overview.png)
+![CMS Store](https://images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/19924b9aeffed7d9cba408245a46d365/store-en-overview.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Before making changes in the <b>Advanced</b> tab, please contact your developer team and read our documentation <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-best-practices-for-optimizing-performance#enabling-store-settings">Optimizing performance</a> para mais informações.
diff --git a/docs/tutorials/en/collection-highlight-control.md b/docs/tutorials/en/collection-highlight-control.md
index 2647bee69..4579b4cad 100644
--- a/docs/tutorials/en/collection-highlight-control.md
+++ b/docs/tutorials/en/collection-highlight-control.md
@@ -29,7 +29,7 @@ First, let's see where the Highlight flag is:
 4. Click a collection.
 5. Check the __Highlight__ flag, which is on the collection screen, and then click __Save Product Cluster__.
 
-![CollectionHighlightFlag](//images.contentful.com/alneenqid6w5/4ced6Gcbeg662KewckyQka/77aaef77fc87cf8112f759c867a6bd4b/CollectionHighlightFlag.png)
+![CollectionHighlightFlag](https://images.contentful.com/alneenqid6w5/4ced6Gcbeg662KewckyQka/77aaef77fc87cf8112f759c867a6bd4b/CollectionHighlightFlag.png)
 
 By flagging it, you inform the system that whenever the highlight control is used in a page template, the products displayed on that page that are part of the collection must appear with the HTML element below, where in place of `{CollectionName}` appears the name of the collection registered in the CMS:
 
diff --git a/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md b/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
index 7d92e8fd9..d562708d1 100644
--- a/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
+++ b/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
@@ -29,7 +29,7 @@ To find this line of code, go to the front-end of your store, enter the browser'
 
 See below the relationship between the folder in the CMS and the store's source code.
 
-![CommerceContext](//images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
+![CommerceContext](https://images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
 
 <div class="alert alert-info">
 This line of code is always commented out. Therefore, it has only informative function. That is, it does not take any action.
diff --git a/docs/tutorials/en/conditions-builder-usage-examples.md b/docs/tutorials/en/conditions-builder-usage-examples.md
index d0a04ee9c..aa910f214 100644
--- a/docs/tutorials/en/conditions-builder-usage-examples.md
+++ b/docs/tutorials/en/conditions-builder-usage-examples.md
@@ -25,7 +25,7 @@ To understand __what__ to create the conditions for, see the article [Create Con
 
 UTM (Marketing tag) is an information that relates to the origin of the customer's traffic. Therefore, the app has a block that checks for this type of information. 
 
-![utm_source_english](//images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
+![utm_source_english](https://images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
 
 <div class="alert alert-warning"><strong>Note: </strong>
 It is possible that your store employs customizations and thereby the UTM information contained in the URL is not being passed on to our system. If you use JavaScript customization, read the article <a href="https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho">Por que as utms não estão sendo aplicadas ao carrinho</a>
@@ -43,7 +43,7 @@ __utm_campaign__ informs in __which campaign__ your customer specifically clicke
 
 __utm_medium__ informs which __advertising channel__ , that can be E-mail or a Banner on a site, reached your customer. In the case of images, the block checks if the channel was *email*.  
 
-![utmenglish](//images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
+![utmenglish](https://images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
   
 For each one of these blocks, you can check to see if: 
 
@@ -88,7 +88,7 @@ This block analyzes the total value which exists in the cart.
 Let’s assume that your wanted to put a cheaper price on a shampoo if your customer would buy __exactly 3 units__, but apart from this would also buy __at least 150 reais__ worth of goods.
 The condition to be created will be: 
 
-![Exemplo2](//images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
+![Exemplo2](https://images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
 
 *quantity of this item in the cart is **exactly** 3 
 **and** 
diff --git a/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md b/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
index b084f092a..4d367904a 100644
--- a/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
+++ b/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
@@ -29,7 +29,7 @@ In this scenario, if a Mercado Libre customer makes a purchase with products fro
 
 VTEX does not recommend this type of configuration because orders will not be integrated.
 
-![cenario problemaENN](//images.contentful.com/alneenqid6w5/1kGjXEcmRvASXHl0WBrgXh/26449573e080d2c6e11953cdc9eeefae/cenario_problemaENN.JPG)
+![cenario problemaENN](https://images.contentful.com/alneenqid6w5/1kGjXEcmRvASXHl0WBrgXh/26449573e080d2c6e11953cdc9eeefae/cenario_problemaENN.JPG)
 
 However, in the integration of VTEX stores with Mercado Libre, two scenarios can prevent this error. To fit within those scenarios, your store must have the following configurations:
 
@@ -42,7 +42,7 @@ The seller uses a single VTEX subaccount and integrates with a single account on
 
 In this scenario, if a user makes a purchase on Mercado Libre with products from two or more of the seller's official stores, the order will be correctly imported into VTEX. This happens because the products listed on Mercado Libre are from the catalog of a single VTEX subaccount.
 
-![cenario singleuser](//images.contentful.com/alneenqid6w5/3ibZG93KjAsKqfXmyTBVqj/1b049c0266e29706c38b2e03b0e98a91/cenario_singleuser.JPG)
+![cenario singleuser](https://images.contentful.com/alneenqid6w5/3ibZG93KjAsKqfXmyTBVqj/1b049c0266e29706c38b2e03b0e98a91/cenario_singleuser.JPG)
 
 ## Multiple VTEX subaccounts and multiple official stores
 
@@ -50,5 +50,5 @@ The VTEX seller has two or more subaccounts and uses each of them to integrate w
 
 In this scenario, if a user makes a purchase on Mercado Libre with two or more products from different subaccounts in the same cart, orders will be integrated normally into each VTEX subaccount. This happens because each order generated on Mercado Libre is linked to a different VTEX subaccount, so the products sold correspond to the catalogs of each subaccount.
 
-![cenario multiplesotre](//images.contentful.com/alneenqid6w5/nwcJEB4dNrEn9aEEMDWBX/026214b8bfffe1374e4acc7eda0dd79f/cenario_multiplesotre.JPG)
+![cenario multiplesotre](https://images.contentful.com/alneenqid6w5/nwcJEB4dNrEn9aEEMDWBX/026214b8bfffe1374e4acc7eda0dd79f/cenario_multiplesotre.JPG)
 
diff --git a/docs/tutorials/en/configure-cartman.md b/docs/tutorials/en/configure-cartman.md
index cf0e62dbc..5960eb1a1 100644
--- a/docs/tutorials/en/configure-cartman.md
+++ b/docs/tutorials/en/configure-cartman.md
@@ -58,7 +58,7 @@ To learn more about this tool, check the [Promotion Simulator](https://help.vtex
 
 By accessing the **View cart details** menu, it is possible to check the specific information of each of the selected products in the cart.
 
-![Item detail](//images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/82b5f6305c4ea397b5aaaed9168e6d74/Item_detail.PNG)
+![Item detail](https://images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/82b5f6305c4ea397b5aaaed9168e6d74/Item_detail.PNG)
 
 ### Add specific items to cart
 
@@ -68,7 +68,7 @@ In **Add items by SKU ID**, new items can be added to the cart according to thei
 - **Quantity of each item**: indication of how many SKU units will be added to the cart.
 - **Seller ID**: identification number of the seller who will deliver the item.
 
-![Add items by SKU ID](//images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/969209879fc26ab3ea769e75c8730bda/Add_items_by_SKU_ID.PNG)
+![Add items by SKU ID](https://images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/969209879fc26ab3ea769e75c8730bda/Add_items_by_SKU_ID.PNG)
 
 ### Add random items to cart
 
@@ -82,7 +82,7 @@ In **Add random items**, new items from the store catalog can be added to the ca
 - Seller ID
 - Price range (Price from / Price up to)
 
-![Add random items](//images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/66f12cfd13a5abb0e4e50251a719ccee/Add_random_items.PNG)
+![Add random items](https://images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/66f12cfd13a5abb0e4e50251a719ccee/Add_random_items.PNG)
 
 ### Define marketing data
 
@@ -94,7 +94,7 @@ In the **Set marketing data option**, you can apply discount coupons to specific
 - **utmi_cp**: internal utm used to define when a certain promotion will be applied, according to the utm described in the order URL. 
 - **Cupom**: discount coupon code to be added to cart.
 
-![Set marketing data](//images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/03ea65c5ca723df8a38ab99dc78301c5/Set_marketing_data.PNG)
+![Set marketing data](https://images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/03ea65c5ca723df8a38ab99dc78301c5/Set_marketing_data.PNG)
 
 To learn more about UTMs and UTMIs, go to [What are utm_source, utm_campaign, and utm_medium](https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii#) and [What are the internal UTMs utmi_cp, utmi_pc and utmi_p](https://help.vtex.com/en/tutorial/o-que-sao-as-utms-internas-utmi_cp-utmi_pc-e-utmi_p#).
 
diff --git a/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
index d10d9e14e..1e8b26a32 100644
--- a/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
@@ -45,7 +45,7 @@ Here, the common property of the clients will be that they are also employees of
 This article assumes that the employees are properly registered with a boolean field `isEmployee` set to true in their respective documents for the CL data entity, as shown in the figure below. 
 
 If they are not, check the article [Creating a field in Master Data](https://help.vtex.com/en/tutorial/how-can-i-create-field-in-master-data) to create a field that identifies the employees and properly configure it for each document corresponding to the employees.
-![Employee field](//images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
+![Employee field](https://images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
 
 <div class="alert alert-info" role="alert">There are many details to completely configure a benefit. If you need additional information on this matter, check out the article <a href="https://help.vtex.com/en/tutorial/creating-promotions-2">Creating promotions</a>.</div>
 
@@ -60,4 +60,4 @@ With the field configured, the benefit can be created by following the steps bel
 7. In the end of the page, click on the **Save** button.
 
 After that, the benefit should already be working as configured. The discount is shown only in the shopping cart. The image below shows an example with 99% off.
-![Shopping cart with discount](//images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
+![Shopping cart with discount](https://images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
diff --git a/docs/tutorials/en/configure-template-in-smartcheckout-update.md b/docs/tutorials/en/configure-template-in-smartcheckout-update.md
index eb70119e8..3c6b90fa1 100644
--- a/docs/tutorials/en/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/en/configure-template-in-smartcheckout-update.md
@@ -37,11 +37,11 @@ Each registered site corresponds to a multidomain (if the account has contracted
 
 Creation of the new website:
 
-![en.smartcheckout1](//images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png)
+![en.smartcheckout1](https://images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png)
 
 Account Name Access:
 
- ![en.smartcheckout2](//images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
+ ![en.smartcheckout2](https://images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
 
 ## Editing and configuring website 
 
@@ -56,14 +56,14 @@ Account Name Access:
    - __Pages__: display existing pages for the website.
 
 Example of existing sites in the same account:
-![EN Cards Portal](//images.ctfassets.net/alneenqid6w5/3PYf4oomjW0HmBznIBYi2N/2e81a23b6f03bcb847fd7407baf58c1a/EN_Cards_Portal.png)
+![EN Cards Portal](https://images.ctfassets.net/alneenqid6w5/3PYf4oomjW0HmBznIBYi2N/2e81a23b6f03bcb847fd7407baf58c1a/EN_Cards_Portal.png)
 
 Example of available pages for a website:
-![en.smartcheckout3](//images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
+![en.smartcheckout3](https://images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
 
 If you want to __delete__ a site, click on the delete button for the desired site, as in the example below:
 
-![en.smartcheckout5](//images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/020a02fc80da75fbf27794714b6d7c2c/en.smartcheckout5.png)
+![en.smartcheckout5](https://images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/020a02fc80da75fbf27794714b6d7c2c/en.smartcheckout5.png)
 
 We'll now have a more in-depth look at the following options menu settings: __Code__ and __Checkout__, being responsible for configuring the pages *checkout* and *order placed* pages.
 
@@ -80,7 +80,7 @@ We'll now have a more in-depth look at the following options menu settings: __Co
   <li><b>Calculation of Delivery Options (Beta and Stable)</b>: select whether the freight calculation will be done from the spreadsheet or by geolocation.</li>
   </ul>
 
-![en.smartcheckout6](//images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
+![en.smartcheckout6](https://images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
 
 ## Configure code
 
@@ -90,7 +90,7 @@ We'll now have a more in-depth look at the following options menu settings: __Co
 
 Example:
 
-![en.smartcheckout7](//images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
+![en.smartcheckout7](https://images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
 
 ### Configuring templates from the "Code" menu
 
@@ -110,27 +110,27 @@ Below are examples of how the codes present in the __checkout-header__, __checko
 
 - Template __checkout-header__ and website page header:
 
-![en.smartcheckout10](//images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) 
+![en.smartcheckout10](https://images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) 
 
-![en.smartcheckout11](//images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
+![en.smartcheckout11](https://images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
 
 - Template __checkout-footer__ and website page footer:
 
-![en.smartcheckout8](//images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png)
+![en.smartcheckout8](https://images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png)
 
- ![en.smartcheckout9](//images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
+ ![en.smartcheckout9](https://images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
 
 - Template __vtex-checkout__ and cart page at Checkout:
 
-![en.smartcheckout12](//images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) 
+![en.smartcheckout12](https://images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) 
 
-![en.smartcheckout13](//images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
+![en.smartcheckout13](https://images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
 
 - Template __vtex-orderPlaced__ and confirmed order page:
 
-![en.smartcheckout18](//images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png)
+![en.smartcheckout18](https://images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png)
 
-![en.smartcheckout19](//images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
+![en.smartcheckout19](https://images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
 
 ### Multi-domain accounts
 
@@ -138,5 +138,5 @@ Multi-domain accounts can use just one site if no specifics configuration requir
 
 An example of a "body" tag that's inserted according to the accessed domain:
 
-![](//images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
+![](https://images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
 
diff --git a/docs/tutorials/en/configure-template-in-the-smartcheckout.md b/docs/tutorials/en/configure-template-in-the-smartcheckout.md
index 68032186a..e4f0b0b42 100644
--- a/docs/tutorials/en/configure-template-in-the-smartcheckout.md
+++ b/docs/tutorials/en/configure-template-in-the-smartcheckout.md
@@ -32,7 +32,7 @@ Now fill out the following fields according to the instructions:
 
 See picture below:
 
-![en.smartcheckout1](//images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png) ![en.smartcheckout2](//images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
+![en.smartcheckout1](https://images.ctfassets.net/alneenqid6w5/3AYhqb6FiwUChorOlxafDS/4d675c4f1310ba14a041f36ee49911ee/en.smartcheckout1.png) ![en.smartcheckout2](https://images.ctfassets.net/alneenqid6w5/rm9LNEvgCOJvKAWpGf5XI/f520942d072cd958262f4c9961e7d9d7/en.smartcheckout2.png)
 
 Click on Save to conclude the registration of the new site.
 
@@ -47,17 +47,17 @@ As shown in the next picture, on clicking the Site name the system displays all
 - Code: Site-related templates
 - Pages: Displays the pages that exist for the site. By default, two pages are created, **checkout **and **checkout/orderPlaced**. As already mentioned at the beginning of this post, the **checkout **page represents the shopping basket, personal data, address and payment method pages. The **checkout/orderPlaced **page represents the Purchase Confirmation page**
 
-![en.smartcheckout3](//images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
+![en.smartcheckout3](https://images.ctfassets.net/alneenqid6w5/2PxJMMiYwBshQTFDnXToDB/b173e24b993d3896c40c06de20683dea/en.smartcheckout3.png)
 
 In **Pages**, it is possible to** Create **new pages, **Edit** and **Exclude **existing pages. See the following two pictures illustrating **Editing **and **Exclusion**. Creation follows the same rules as editing.
 
 Editing pages:
 
-![en.smartcheckout4](//images.ctfassets.net/alneenqid6w5/7to0u1evDi9wENUr7bObaq/17162c0dc68db11895017d4d75d273f9/en.smartcheckout4.png)
+![en.smartcheckout4](https://images.ctfassets.net/alneenqid6w5/7to0u1evDi9wENUr7bObaq/17162c0dc68db11895017d4d75d273f9/en.smartcheckout4.png)
 
 Excluding pages:
 
-![en.smartcheckout5](//images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/e10b9a0784b5061594b3690ed6a43ca3/en.smartcheckout5.png)
+![en.smartcheckout5](https://images.ctfassets.net/alneenqid6w5/1L3XIITqW0hUMRb9kCRU65/e10b9a0784b5061594b3690ed6a43ca3/en.smartcheckout5.png)
 
 In **Checkout**, we can edit the fields below:
 
@@ -68,44 +68,44 @@ In **Checkout**, we can edit the fields below:
 
 Below is a picture illustrating how to fill out this form:
 
-![en.smartcheckout6](//images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
+![en.smartcheckout6](https://images.ctfassets.net/alneenqid6w5/2aSyfs2iSk8k282tzvD5ad/2134352be985fe4f527ffd65f87cb7c7/en.smartcheckout6.png)
 
 In **Code**, on the right, all the Site-related templates will be displayed. By default, the system configures the templates exemplified in the picture below:
 
-![en.smartcheckout7](//images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
+![en.smartcheckout7](https://images.ctfassets.net/alneenqid6w5/1x7W9GEAPhuX48I1iEQghm/ec00ebd04a4326d63182dd58acacc202/en.smartcheckout7.png)
 
 Of these templates, the only ones that cannot be changed are **vtex-checkout **and **vtex-orderPlaced**. These templates correspond to the native operation of the platform, that is, they render the main content of these pages, both the checkout and the orderPlaced.
 
 In the next picture, we show the area affected at the checkout by the setting of the **checkout-footer **template. This is merely an example of an empty template.
 
-![en.smartcheckout8](//images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png) ![en.smartcheckout9](//images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
+![en.smartcheckout8](https://images.ctfassets.net/alneenqid6w5/SWI577sEU85XKjwtAOURD/4a6c0cf38aa2c80666eb972ed9ca3528/en.smartcheckout8.png) ![en.smartcheckout9](https://images.ctfassets.net/alneenqid6w5/6ntrDKAHUd6l9dfopU63Z7/d870b01102fd965c76c530279dbc1654/en.smartcheckout9.png)
 
 In the next picture, we have an equivalent example to the previous one; however, this time with the HTML code filled out. Note that the code filled out on the left corresponds to the upper right-hand area. This is the **checkout-header **template.
 
-![en.smartcheckout10](//images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) ![en.smartcheckout11](//images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
+![en.smartcheckout10](https://images.ctfassets.net/alneenqid6w5/2wkWd5eLmhEjF0qrtYt09O/639eefb3539d9ceac3483cb36ce1daf6/en.smartcheckout10.png) ![en.smartcheckout11](https://images.ctfassets.net/alneenqid6w5/wE8y5BGPJ98vqY5uWBK88/0a357d212ba62e0627dd2348bd6c56de/en.smartcheckout11.png)
 
 As we can see in the next picture, all templates with the **checkout** prefix will be used on all Checkout pages. In this example, we are on the Forma de Pagamento page. Note that the header loaded is the same as in the previous example.
 
-![en.smartcheckout12](//images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) ![en.smartcheckout13](//images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
+![en.smartcheckout12](https://images.ctfassets.net/alneenqid6w5/3eQbQDODquTDApkbuMZeik/7b692e4dac58e13e41578263a1e739ac/en.smartcheckout12.png) ![en.smartcheckout13](https://images.ctfassets.net/alneenqid6w5/241khOdkptYYcD9wLqd3Xk/db163752009b17887990cd4272541e89/en.smartcheckout13.png)
 
 Just as in the **checkout **templates, the same happens with the orderPlaced templates. In other words, templates with the **orderPlaced** prefix only correspond to the OrderPlaced (Purchase Confirmation) page.
 
-![en.smartcheckout14](//images.ctfassets.net/alneenqid6w5/3R5BgiNGjgvwGord10U26t/567703d54d381bd197a5e674b035802b/en.smartcheckout14.png) ![en.smartcheckout15](//images.ctfassets.net/alneenqid6w5/pzZig7wTU8YNCBG9wqFYe/d6c1c563cc7ebad9df6cfa1878cd8730/en.smartcheckout15.png)
+![en.smartcheckout14](https://images.ctfassets.net/alneenqid6w5/3R5BgiNGjgvwGord10U26t/567703d54d381bd197a5e674b035802b/en.smartcheckout14.png) ![en.smartcheckout15](https://images.ctfassets.net/alneenqid6w5/pzZig7wTU8YNCBG9wqFYe/d6c1c563cc7ebad9df6cfa1878cd8730/en.smartcheckout15.png)
 
 As explained above, the only templates where alterations are not permitted are **vtex-checkout** and **vtex-orderPlaced**. These templates render the basic content of the Checkout and OrderPlaced pages. Below are examples of the content rendered by the templates.
 
 **vtex-checkout **template:
 
-![en.smartcheckout16](//images.ctfassets.net/alneenqid6w5/57XEgJ13YRpGLREovFUyNU/8a842c82fb418f9df729202bc52c7548/en.smartcheckout16.png) ![en.smartcheckout17](//images.ctfassets.net/alneenqid6w5/4XmnSmdoN3DugDECxgbeOD/0082a842c288dad52d577bb52722822b/en.smartcheckout17.png)
+![en.smartcheckout16](https://images.ctfassets.net/alneenqid6w5/57XEgJ13YRpGLREovFUyNU/8a842c82fb418f9df729202bc52c7548/en.smartcheckout16.png) ![en.smartcheckout17](https://images.ctfassets.net/alneenqid6w5/4XmnSmdoN3DugDECxgbeOD/0082a842c288dad52d577bb52722822b/en.smartcheckout17.png)
 
 **vtex-orderPlaced **template:
 
-![en.smartcheckout18](//images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png) ![en.smartcheckout19](//images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
+![en.smartcheckout18](https://images.ctfassets.net/alneenqid6w5/3bYwEo8B9sI9IEw024oIvi/df9818cfec61bbfc5847dbbbfd611b98/en.smartcheckout18.png) ![en.smartcheckout19](https://images.ctfassets.net/alneenqid6w5/34ypWrIjyTvUf1GZJP8YpC/49b3c81844d0543664af9104b1e985d8/en.smartcheckout19.png)
 
 Multi-domain accounts can only use one site, if the need arises for specific configurations. This is because, although only one Site exists, the platform includes a class in the tag &lt;body&gt; according to the domain accessed. This makes it simple to apply different layouts to the same site.
 
 Class inserted in the tag &lt;body&gt; according to the domain accessed:
 
-![](//images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
+![](https://images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
 
 Important: Any JavaScript included directly in any Portal template will be ignored by the platform, that is, when the page is rendered the platform will remove it. This is because the SmartCheckout only accepts scripts that originated in Google Tag Manager. Thus, whenever the need arises to undertake some customization (or even to insert specific tags) using JavaScript, do the inclusion using Google Tag Manager.
diff --git a/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md b/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md
index 1f368c1e4..684629e6f 100644
--- a/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md
+++ b/docs/tutorials/en/configuring-a-discount-for-orders-prepaid-in-full.md
@@ -34,7 +34,7 @@ After you determine the discount at Checkout, you need to link the SKU to the pa
 3. Select the template of your product page.
 4. In the `skuPrice` property, add the `paymentSystemId` variable with the ID of the chosen payment method.
 
-![Screenshot 2020-12-18 Criar preço à vista](//images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
+![Screenshot 2020-12-18 Criar preço à vista](https://images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
 
 6. Click on __Save Template__ in the upper right corner.
 
diff --git a/docs/tutorials/en/configuring-a-marketplace-trade-policy.md b/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
index c9c338c91..a51a24038 100644
--- a/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
@@ -39,14 +39,14 @@ Creating a new trade policy is the first step in defining the conditions that ap
 
 This configuration can be done in the *Store setup* module, on the *Trade policies* page. You must [create a new trade policy](https://help.vtex.com/en/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) when the settings for catalog, price, promotions, logistics and payments are different between the marketplaces in which sellers sell their products. 
 
-![EN Add Politica comercial](//images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e74c92388925fad7a099da236e616122/EN_Add_Politica_comercial.jpg)
+![EN Add Politica comercial](https://images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e74c92388925fad7a099da236e616122/EN_Add_Politica_comercial.jpg)
 
 ## Orders management
 After creating a trade policy, you must associate it with each marketplace in which the seller sells products by adding them as [affiliates](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). This is how sellers identify which trade policy operates in each marketplace. If your store sells products in three different marketplaces, you must create three affiliates: one for each marketplace.
 
 This can be configured in the *Settings* page of the *Order management* module, where you can add affiliates. Even if you create several, it is important to note that only one trade policy will operate in the marketplace at a time. 
 
-![EN Afiliado](//images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/9f59fda62a85e1df3ac2c14737853493/EN_Afiliado.jpg)
+![EN Afiliado](https://images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/9f59fda62a85e1df3ac2c14737853493/EN_Afiliado.jpg)
 *In the example above, the affiliate "Amazon" is associated with trade policy "1".* 
 
 ## Promotions
@@ -59,7 +59,7 @@ This configuration can be done in the *Promotions* module in all [promotions](ht
 
 If no trade policy is selected, the promotion will be available in all sales channels.
 
-![EN Promoções Politica Comercial](//images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/e0e31dc018a61402bbacd629a4632275/EN_Promo____es_Politica_Comercial.jpg)
+![EN Promoções Politica Comercial](https://images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/e0e31dc018a61402bbacd629a4632275/EN_Promo____es_Politica_Comercial.jpg)
 
 *In the example above, the promotion will only apply to orders from the "Marketplace-BRL" and "Argentina-ARS" trade policies, where the store operates as a seller. The promotion will not be available on the VTEX storefront.* 
 
@@ -68,7 +68,7 @@ Sellers who process payment for their product sales in a marketplace can create
 
 This configuration can be done in the *Payments* module by [creating a special condition](https://help.vtex.com/en/tutorial/condicoes-especiais--tutorials_456) and associating it with the trade policies of your choice.
 
-![EN Pagamento Politica comercial](//images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/f7ca24768f12e60df2f86469dd380fe4/EN_Pagamento_Politica_comercial.jpg)
+![EN Pagamento Politica comercial](https://images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/f7ca24768f12e60df2f86469dd380fe4/EN_Pagamento_Politica_comercial.jpg)
 
 *In the example above, the payment condition is associated with the "Marketplace" trade policy. This makes the payment condition available only to sales channels associated with this commercial policy.*
 
@@ -81,7 +81,7 @@ This configuration can be done in the VTEX *Catalog*, when [adding products](htt
 We do not recommend attaching trade policies to collections, when determining the product assortment, especially for external marketplaces. When a product is withdrawn from the collection associated to a trade policy, the VTEX system does not warn the marketplace of that update, making the product still available in the marketplace.
   </div>
 
-![EN Catálogo Politica](//images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/43607a48ab2590d2f58a50c8281f4879/EN_Cat__logo_Politica.jpg)
+![EN Catálogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/43607a48ab2590d2f58a50c8281f4879/EN_Cat__logo_Politica.jpg)
 
 *In the example above, the product will only be available to sales channels using the "Carrefour" and "Marketplace" trade policies.*
 
@@ -93,7 +93,7 @@ This configuration can be done in the *Prices* module by means of trade policies
 - [Price rules](https://help.vtex.com/en/tutorial/configurar-regra-de-preco-para-politica-comercial--5LQMLwcUcEGCWK6SMI6cEM): to determine a markup for specific categories and brands.
 - [Fixed prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy): to differentiate prices for specific products.
 
-![EN Regra de preço](//images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/1e299eba8c5e102543d8db27175a9086/EN_Regra_de_pre__o.jpg)
+![EN Regra de preço](https://images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/1e299eba8c5e102543d8db27175a9086/EN_Regra_de_pre__o.jpg)
 
 *In the example above, the price rule applied a markup to the "Marketplace" trade policy for products in the "Fera-Fashion category".*
 
@@ -103,11 +103,11 @@ Sellers can set up specific [logistics routes](https://help.vtex.com/en/tracks/l
 
 Both settings can be configured on the *Shipping strategy* page. When creating a [loading dock](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj), you must indicate which trade policies will be associated with it. This makes the shipping policies associated with this loading dock available to the linked trade policies. Then, you must link the desired [inventory](https://help.vtex.com/en/tutorial/gerenciar-estoque) to a loading dock to make the inventory available to the trade policies associated with the loading dock.
 
-![EN Doca politica](//images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/55d339d25b6d5e94095f237f87fe0246/EN_Doca_politica.jpg)
+![EN Doca politica](https://images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/55d339d25b6d5e94095f237f87fe0246/EN_Doca_politica.jpg)
 
 *In the example above, the loading dock is associated with the commercial policy "Marketplace", which will be linked to the carrier "Carrier A".*
 
-![EN Estoque Politica](//images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/ad0a2568d1f7be56399c798d274d526a/EN_Estoque_Politica.jpg)
+![EN Estoque Politica](https://images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/ad0a2568d1f7be56399c798d274d526a/EN_Estoque_Politica.jpg)
 *In the example above, the inventory is associated with "Dock A", so this will be the inventory used by the trade policies linked to "Dock A".* 
 
 ## Integrations
@@ -115,7 +115,7 @@ Trade policies also apply to all integrations in which your store sells products
 
 [Integrations](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#vender-em-marketplace) can be configured in the *Settings* page of the *Integrations* module. Usually, each channel requires specific commercial conditions, but it is possible that different channels share the same trade policy.
 
-![EN Integracao Politica](//images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/dd3b2b730cfd16c4a9bbcca8b253c473/EN_Integracao_Politica.jpg)
+![EN Integracao Politica](https://images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/dd3b2b730cfd16c4a9bbcca8b253c473/EN_Integracao_Politica.jpg)
 *In the example above, the "Marketplace" trade policy applies to the Google Shopping integration.*
 
 ## Learn more
diff --git a/docs/tutorials/en/configuring-banners.md b/docs/tutorials/en/configuring-banners.md
index e2e60f986..003dc18c6 100644
--- a/docs/tutorials/en/configuring-banners.md
+++ b/docs/tutorials/en/configuring-banners.md
@@ -29,7 +29,7 @@ After configuring the banner, you have to add it to a page on your store. To do
 <p> This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: Multilanguage settings (Beta)</a>.</p>
 </div>
 
-![banner-form-en](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
+![banner-form-en](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
 
 ## Banner fields
 
@@ -60,7 +60,7 @@ To add a banner, the following fields need to be completed:
 
 Click <i class="fas-solid fa-link"></i> `Autofill from URL` to add the URL of the search page to the trigger rules that will be applied.
 
-![banner-url-en](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
+![banner-url-en](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/326bfe62f7a49e6f1bd34c7cbe5f6b6a/image.png)
 
 Click <i class="fas fa-plus"></i> `Add condition` to create a rule. Rules can be of two types:
 
diff --git a/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index 6ddcc365e..d9b17743f 100644
--- a/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -43,7 +43,7 @@ If the platform detects any errors, check the section <b>Import errors</b>.
 	<li>Once the import process is complete, you can click View Import Details to access the import report.</li>
 </ol>
 
-![Importação em massa - EN](//images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/255b9bf809653b7f66bdeff7e22c0c49/Bulk_import_vers_o_original-gif-EN.gif)
+![Importação em massa - EN](https://images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/255b9bf809653b7f66bdeff7e22c0c49/Bulk_import_vers_o_original-gif-EN.gif)
 
 # Import errors
 
@@ -59,7 +59,7 @@ To get a detailed overview of the detected problems, follow the steps below:
 Make sure you only upload the file with corrections to the previously detected errors to ensure a successful import.
 </div>
 
-![Bulk import - EN](//images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/f15af7d4180b8949ef33c25c761122a8/Bulk_import_vers_o_error-gif-EN.gif)
+![Bulk import - EN](https://images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/f15af7d4180b8949ef33c25c761122a8/Bulk_import_vers_o_error-gif-EN.gif)
 
 # Bulk Import via API
 
diff --git a/docs/tutorials/en/configuring-cargo-splitting.md b/docs/tutorials/en/configuring-cargo-splitting.md
index 79c81c6ce..48bc9f355 100644
--- a/docs/tutorials/en/configuring-cargo-splitting.md
+++ b/docs/tutorials/en/configuring-cargo-splitting.md
@@ -19,7 +19,7 @@ Cargo splitting is the configuration that allows a purchase to be divided into m
 
 This configuration is very important because, if cargo splitting is not allowed, the closing of a purchase may preclude. So, use it if the total weight of all products in the shopping cart is bigger than the maximum weight registered in shipping policies.
 
-![divisao-carga-desenho en](//images.ctfassets.net/alneenqid6w5/6wSYatCGzeEq2o68IIMIkc/1b86e66b1882c4f41815f642b152446b/divisao-carga_en.png)
+![divisao-carga-desenho en](https://images.ctfassets.net/alneenqid6w5/6wSYatCGzeEq2o68IIMIkc/1b86e66b1882c4f41815f642b152446b/divisao-carga_en.png)
 
 ### How to configure
 
diff --git a/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
index 9c91f6dfd..16e5c6773 100644
--- a/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
@@ -79,7 +79,7 @@ To configure ClearSale Global, you will need to:
 <br>  
   <ui>11. In the top right corner, click on <b>Publish</b>.</ui>
 
-![Fingerprint ClearSalve_Screen](//images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/030e58c5ff8495926031bead9fd13b0e/Fingerprint_ClearSalve_Screen.png)
+![Fingerprint ClearSalve_Screen](https://images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/030e58c5ff8495926031bead9fd13b0e/Fingerprint_ClearSalve_Screen.png)
 
 For more details about the code entered in Google Tag Manager, we recommend reading [this documentation](https://api.clearsale.com.br/docs/behavior-analytics) from ClearSale.
 
diff --git a/docs/tutorials/en/configuring-clearsale-v3-antifraud.md b/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
index b860ff26f..f519d1736 100644
--- a/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
@@ -74,7 +74,7 @@ Configuring ClearSale v3 anti-fraud solution requires creating a tag in Google T
 10. Click on the __Create Tag__ button, enter a name for this tag and save.
 11. In the top right corner, click on __Publish__.
 
-![Pasted image at 2017 10 20 01 11 PM](//images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
+![Pasted image at 2017 10 20 01 11 PM](https://images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
 
 <div class="alert alert-info"> See the <a href="https://api.clearsale.com.br/docs/finger-print" target="_blank"> FingerPrint documentation</a> on ClearSale for more information on the above script. </div>
 
diff --git a/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md b/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md
index 5782a4a78..aec947d83 100644
--- a/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md
+++ b/docs/tutorials/en/configuring-functions-in-the-message-center-templates.md
@@ -35,7 +35,7 @@ _classe.atributo_ are obtained using the JSON Data field. E.g.:
 **Template HTML**
 `<strong>{{_accountInfo.HostName}}</strong> => lojavirtual`
 
-![exemplohtml](//images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
+![exemplohtml](https://images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
 
 The above example can have different values when comparing Sellers and Marketplaces.
 
@@ -130,4 +130,4 @@ em até{{#hasSubStr shippingEstimate 'bd'}}
 ```
 
 **Result:**
-![](//images.contentful.com/alneenqid6w5/5cRmcM2692G60Ok6gSAWmo/f7196556f5360f632dbccf47f837b5b9/3.1.jpg)
+![](https://images.contentful.com/alneenqid6w5/5cRmcM2692G60Ok6gSAWmo/f7196556f5360f632dbccf47f837b5b9/3.1.jpg)
diff --git a/docs/tutorials/en/configuring-greenlist.md b/docs/tutorials/en/configuring-greenlist.md
index ebef09970..2693b24a2 100644
--- a/docs/tutorials/en/configuring-greenlist.md
+++ b/docs/tutorials/en/configuring-greenlist.md
@@ -45,7 +45,7 @@ The more signature data you ask for, the stricter will be your rules, and the fe
 
 To mark a customer as trustworthy, the store owner uses certain criteria. These criteria are __purchase details making up the signature of an order__:
 
-![Greenlist - signature](//images.contentful.com/alneenqid6w5/3CvVVFRIJ22wS6o8sq6ok6/45cdf4a8259437d36aa74a40a8a04715/Greenlist_-_assinatura.png)
+![Greenlist - signature](https://images.contentful.com/alneenqid6w5/3CvVVFRIJ22wS6o8sq6ok6/45cdf4a8259437d36aa74a40a8a04715/Greenlist_-_assinatura.png)
 
 Let’s say you select three options from the above screen: __Email address__, __Delivery address__ and __Credit card number__. This means that for new orders from this customer not to have to pass through the antifraud, he will have to use the same email address, delivery address and credit card number for new purchases. 
 
@@ -57,7 +57,7 @@ The recurrence of a signature defines the number of orders a customer must make
 
 This number must be defined by the store owner, and can vary from __1 to 10__.
 
-![Greenlist - recurrence](//images.contentful.com/alneenqid6w5/2TFJUnw1Cw8I0KcqCcAsmS/6aaec62228ec8ff5a38093e743a4229b/Greenlist_-_recorrencia.png)
+![Greenlist - recurrence](https://images.contentful.com/alneenqid6w5/2TFJUnw1Cw8I0KcqCcAsmS/6aaec62228ec8ff5a38093e743a4229b/Greenlist_-_recorrencia.png)
 
 If you set recurrence at 6, for example, every customer of your store who makes six purchases using the same details for the signature will not have to pass through antifraud on subsequent purchases.
 
@@ -65,7 +65,7 @@ If you set recurrence at 6, for example, every customer of your store who makes
 
 You can set a maximum value for the Greenlist to operate. This is because even if a customer has been marked as trustworthy, you may prefer that – for very large amounts, where the risk of loss is greater – the antifraud should operate irrespective of the customer’s purchase record.
 
-![Greenlist – maximum value](//images.contentful.com/alneenqid6w5/1CG6Wm74qIu4Qam2WekkE4/02f3e165b7970651406d667ae66e4589/Greenlist_-_valor_maximo.png)
+![Greenlist – maximum value](https://images.contentful.com/alneenqid6w5/1CG6Wm74qIu4Qam2WekkE4/02f3e165b7970651406d667ae66e4589/Greenlist_-_valor_maximo.png)
 
 ### Security period for Chargeback
 
@@ -73,7 +73,7 @@ Sometimes, after an order has been placed and the antifraud has approved the pur
 
 In this case, it is good to define a margin of security for the Greenlist analysis. If, for example, you select a security period of 30 days, you are saying that every order approved by the antifraud will be assessed for the Greenlist only after 30 days.
 
-![Greenlist - chargeback](//images.contentful.com/alneenqid6w5/314Ig5HLCU2uy0kyYEu4gC/105ed241ac49923035a7b4d441d698e0/Greenlist_-_chargeback.png)
+![Greenlist - chargeback](https://images.contentful.com/alneenqid6w5/314Ig5HLCU2uy0kyYEu4gC/105ed241ac49923035a7b4d441d698e0/Greenlist_-_chargeback.png)
 
 ### Activating a Greenlist
 
@@ -92,6 +92,6 @@ If you find that an order from a customer on the Greenlist (or any other custome
 2. In the list of transactions, click on the one you want to mark as fraudulent;
 3. Click on __Mark the payment as fraudulent__.
 
-![Mark as fraudulent](//images.contentful.com/alneenqid6w5/3EiAcGulosCgQq4qCIGqQE/d0be6c70e7129f63b189c56bdb79012b/fraud.png)
+![Mark as fraudulent](https://images.contentful.com/alneenqid6w5/3EiAcGulosCgQq4qCIGqQE/d0be6c70e7129f63b189c56bdb79012b/fraud.png)
 
 Once this is done, the customer that placed the order is removed from the Greenlist.
diff --git a/docs/tutorials/en/configuring-login-with-facebook-and-google.md b/docs/tutorials/en/configuring-login-with-facebook-and-google.md
index 57d4f018a..475016df3 100644
--- a/docs/tutorials/en/configuring-login-with-facebook-and-google.md
+++ b/docs/tutorials/en/configuring-login-with-facebook-and-google.md
@@ -37,14 +37,14 @@ After completing the configuration on Facebook and/or Google, you must configure
 
   You will be redirected to the **Webstore** tab of the **Authentication** page, which lists the login methods available in your store.
 
-  ![List Authentication](//images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/fdb1252e98fd1284278e4c83100ec111/autenticacao-en.png)
+  ![List Authentication](https://images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/fdb1252e98fd1284278e4c83100ec111/autenticacao-en.png)
 3. In the row of the desired login provider, click `Configure`.
 4. Complete the form with the `Client ID` and `Client Secret` from the [previous step](#obtaining-credentials-from-providers) and click `Save`.
 
-  ![Facebook OAuth EN](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/7daac156505a588b95fc0e90fbc08e2d/1-login-fb-en.PNG)
+  ![Facebook OAuth EN](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/7daac156505a588b95fc0e90fbc08e2d/1-login-fb-en.PNG)
 6. On the **Authentication** page, enable the provider by clicking the toggle switch.
 
-  ![List Authentication Switch On Highlight](//images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/02ec0a744eb98636917b144e09cc9b3c/switch_On_highlight_EN.png)
+  ![List Authentication Switch On Highlight](https://images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/02ec0a744eb98636917b144e09cc9b3c/switch_On_highlight_EN.png)
 
 ## Validating the configuration
 
diff --git a/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
index e9374f296..1700c1c1a 100644
--- a/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -59,7 +59,7 @@ To configure the automatic settlement feature, follow the step-by-step instructi
 8. In the __Payment with anticipated capture authorization__ field, select one of the available time options.
 9. Fill in the __Change maximum time for automatic payment capture__ field with the period agreed with the acquirer. __If you leave this field blank, the default time of 4 days will be considered. __
 
-![captura_automatica_EN](//images.ctfassets.net/alneenqid6w5/4OXaQvc9dAoPs1lsPXmigk/3351cf6cd959943406edcf967ad4492c/image.png)
+![captura_automatica_EN](https://images.ctfassets.net/alneenqid6w5/4OXaQvc9dAoPs1lsPXmigk/3351cf6cd959943406edcf967ad4492c/image.png)
 10. Click on __Save__ 
 
 The new payment settlement feature will then be implemented in your store.
diff --git a/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
index 369910507..8811a448b 100644
--- a/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
@@ -63,13 +63,13 @@ To ensure the Device Fingerprint feature is operating properly, you must analyze
 4. Click on __+ Information__.
 5. Search for the __deviceFingerprint__ field and check if the code starts with the word armor, as illustrated below.
 
-![Device Fingerprint Armor](//images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/e4183659ac15c29fec5611d96b0b1b52/DEVICEFINGERPRINTARMOR.png)
+![Device Fingerprint Armor](https://images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/e4183659ac15c29fec5611d96b0b1b52/DEVICEFINGERPRINTARMOR.png)
 
 <ui>
 6. Then, send the transaction ID to the Mercado Pago support team. You can find this ID in the <b>authorizationConnectorResponse</b> field.
   </ui>
 
-![Authorization](//images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/1d84e9df5bb987aa4b3acf9a0f1904e1/AUTHORIZATION.png)
+![Authorization](https://images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/1d84e9df5bb987aa4b3acf9a0f1904e1/AUTHORIZATION.png)
 
 <ui>
 7. Copy the ID and <a href=https://www.mercadopago.com.br/developers/en/support>send an email</a> with this information to Mercado Pago requesting them to validate the transaction. 
diff --git a/docs/tutorials/en/configuring-my-account-conversational-commerce.md b/docs/tutorials/en/configuring-my-account-conversational-commerce.md
index 78af32f90..75a9b151d 100644
--- a/docs/tutorials/en/configuring-my-account-conversational-commerce.md
+++ b/docs/tutorials/en/configuring-my-account-conversational-commerce.md
@@ -24,7 +24,7 @@ subcategory: 5bBAgUbHdh6ovdZ4kGsN7O
 
 ## Conversational Settings Fields
 
-![my account - conversational commerce - EN](//images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/2329e5c54977ddb95a7fd6fd4ad01b47/image.png)
+![my account - conversational commerce - EN](https://images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/2329e5c54977ddb95a7fd6fd4ad01b47/image.png)
 
 * **Language:** The default language for bot messages to customers in VTEX Conversational Commerce. Required field.
 * **Welcome message:** The first message that VTEX Conversational Commerce will send in its initial interaction with the customer. This message is followed by explanatory messages about the purchase process and human support from your customer service team. Required field. Our default suggestion is: 
diff --git a/docs/tutorials/en/configuring-payment-gateways.md b/docs/tutorials/en/configuring-payment-gateways.md
index f6c21cdbe..e2845984e 100644
--- a/docs/tutorials/en/configuring-payment-gateways.md
+++ b/docs/tutorials/en/configuring-payment-gateways.md
@@ -18,5 +18,5 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 Payment gateways are essential to turn the key to take your store live. To do so, access the [PCI Gateway](/tutorial/afiliacoes-de-gateway/ "PCI Gateway"), our module certified by PCI DSS that guarantees the satefy your customers’ payment information.
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3011-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4?_=1" />[//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4](//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4 "//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3011-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4?_=1" />[//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4](https://downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4 "//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4")</video>
 
diff --git a/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index 8a025d1e8..6654f7c3a 100644
--- a/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -51,7 +51,7 @@ To enable VTEX access to the Adyen environment, follow the instructions below:
 2. In the left sidebar, copy and save the information shown above **Company**. This is your Company account.
 3. In the list below Company, search for the Merchant Account that will be used (highlighted in white). Copy and save this information.
 
-![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Getting the POS Live URL
 
@@ -70,7 +70,7 @@ The steps below assume that the API Key has been previously generated in the Ady
 2. Select your API credential.
 3. In **Server Settings > Authentication**, select **API key**. 
 
-![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Click <b>Generate key</b> and store the generated key in a safe location.</ui>
 
@@ -86,7 +86,7 @@ Follow the steps below to configure a webhook:
 4. In **General > Description**, add a description for the new webhook. Example: "Webhook Adyen Connector Provider v3".
 5. In **General > Server configuration > URL**, enter the URL of your VTEX account. Example: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Click <b>Apply</b>.</ui>
 
@@ -94,11 +94,11 @@ Follow the steps below to configure a webhook:
 
 <blockquote><ui>8. Click <b>Save changes</b>.</ui>
 
-![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 If you have several stores, you need to configure a webhook for each of them.
diff --git a/docs/tutorials/en/configuring-payment-with-adyenv3.md b/docs/tutorials/en/configuring-payment-with-adyenv3.md
index 3d5a4107d..3e19ecac6 100644
--- a/docs/tutorials/en/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/en/configuring-payment-with-adyenv3.md
@@ -42,7 +42,7 @@ To enable VTEX access to the Adyen environment, follow the instructions below:
 2. In the left sidebar, copy and save the information shown above __Company__. This is your Company account.
 3. In the list below Company, search for the Merchant Account that will be used (highlighted in white). Copy and save this information.
 
-![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Getting the Live URL
 
@@ -59,7 +59,7 @@ The steps below assume that the API Key and Client Key have been previously gene
 2. Select your API credential.
 3. In __Server Settings > Authentication__, select __API key__. 
 
-![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Click <b>Generate Key</b> and store the created key in a safe location.</ui>
 
@@ -67,7 +67,7 @@ The steps below assume that the API Key and Client Key have been previously gene
 
 <blockquote><ui>6. Click <b>Generate Client Key</b> and store the generated key in a safe location.
 
-![Adyenv3_3](//images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
+![Adyenv3_3](https://images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
 
 ### Configuring a webhook
 
@@ -81,7 +81,7 @@ Follow the steps below to configure a webhook:
 4. In **General > Description**, add a description for the new webhook. Example "Webhook Adyen Connector Provider v3".
 5. Em **General > Server configuration > URL**, enter the URL of your VTEX account. Example: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Click <b>Apply</b>.</ui>
 
@@ -89,11 +89,11 @@ Follow the steps below to configure a webhook:
 
 <blockquote><ui>8. Click <b>Save changes</b>.</ui>
 
-![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 If you have several stores, you need to configure a webhook for each of them.
diff --git a/docs/tutorials/en/configuring-price-divergence-rule.md b/docs/tutorials/en/configuring-price-divergence-rule.md
index a5609b196..a8eaa0cf2 100644
--- a/docs/tutorials/en/configuring-price-divergence-rule.md
+++ b/docs/tutorials/en/configuring-price-divergence-rule.md
@@ -45,13 +45,13 @@ To create a price divergence rule, follow the steps below:
 
 You will see the following screen:
 
-![print_01_EN](//images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/fa9641527537c42b23341371afd4952c/print_01_EN.png)
+![print_01_EN](https://images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/fa9641527537c42b23341371afd4952c/print_01_EN.png)
 
 The **All** tab displays all configured authorization rules.
 
 To create the first authorization rule, click on **CREATE RULES**. A new tab named **1st rule** will be displayed. Clicking on this tab will display the configuration options.
 
-![print_02_EN](//images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/624e56c9b13d8208d9415b0645b4745a/print_02_EN.png)
+![print_02_EN](https://images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/624e56c9b13d8208d9415b0645b4745a/print_02_EN.png)
 
 To configure the **1st rule**, you can increase or decrease the divergence percentage by dragging the ends of the bar. The > sign determines the start of the range, and the < sign determines its end. The range can be from 0% to 100%.
 
@@ -67,7 +67,7 @@ To configure a hierarchy of users responsible for approving orders, you must ent
 
 To create the **2nd rule**, click on the `<img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" />` plus sign. The same applies to creating a third or fourth rule, and so on. Once you click on the icon, the following interface is displayed:
 
-![print_03_EN](//images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/9c85616fd03154cf6130dc5addc22cc4/print_03_EN.png)
+![print_03_EN](https://images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/9c85616fd03154cf6130dc5addc22cc4/print_03_EN.png)
 
 Configure the new authorization rule and, once you have configured all the rules you want, click on the **SAVE RULES** button. You will see the following message: _After saving, you can still edit or delete them at any time_. Click **OK** to confirm. Once this is done, the Price Divergence rule will be created.
 
diff --git a/docs/tutorials/en/configuring-prices-v2.md b/docs/tutorials/en/configuring-prices-v2.md
index 014e2f040..5fcfac0b3 100644
--- a/docs/tutorials/en/configuring-prices-v2.md
+++ b/docs/tutorials/en/configuring-prices-v2.md
@@ -20,7 +20,7 @@ The functions described in this article are not yet available for all clients.
 
 Price configurations are accessed by the **Settings** button in the **Prices** module.
 
-![Preco24](//images.contentful.com/alneenqid6w5/5Wm20idGbCG0uKei00QQOi/5e18f35d0dd0790e5be98341c67ab4a6/Preco24.gif)
+![Preco24](https://images.contentful.com/alneenqid6w5/5Wm20idGbCG0uKei00QQOi/5e18f35d0dd0790e5be98341c67ab4a6/Preco24.gif)
 
 &nbsp;
 
@@ -43,4 +43,4 @@ Minimum markup is entered on the Configurações screen as a benchmark for two s
 
 The initial minimum markup, for each commercial policy, is always zero, and can be freely adjusted to positive or negative values.
 
-![Preco25](//images.contentful.com/alneenqid6w5/12nLR9a2AMwCeuYmmIagCI/94ff929a610a22b1fec685acfc0aec7c/Preco25.gif)
+![Preco25](https://images.contentful.com/alneenqid6w5/12nLR9a2AMwCeuYmmIagCI/94ff929a610a22b1fec685acfc0aec7c/Preco25.gif)
diff --git a/docs/tutorials/en/configuring-product-visited.md b/docs/tutorials/en/configuring-product-visited.md
index cb84f99bc..1b3693e63 100644
--- a/docs/tutorials/en/configuring-product-visited.md
+++ b/docs/tutorials/en/configuring-product-visited.md
@@ -21,7 +21,7 @@ Tutorial valid only for Legacy CMS Stores.
 
 Product visited is a function that sends emails to customers who viewed a product on your site but did not complete a purchase. The purpose of this email is to recover the sale, by sending details of the product abandoned and suggestions for others. You can do all this through your Master Data.
 
-[![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
+[![ExemploProdutoVisitado](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
 
 _For this feature to work properly, your store must have a high flow of visits and purchases, since the shelves are generated by relating browsing data to a specific product._
 
@@ -49,21 +49,21 @@ Click on the **Salvar** button.
 After creating a field in the entity, you have to configure it so that it appears in the form – this way it is possible to see the data registered in it. This is also valid for fields created automatically by VTEX which have not been marked for showing in the form. Below we give instructions on how to show the fields that are important in the case of a Product Visited.
 
 1. Access the **Master Data **module;
-2. In the application **Profile System**, click on the **gear** symbol; [![aplicacaoEditar](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png "![aplicacaoEditar](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)")
+2. In the application **Profile System**, click on the **gear** symbol; [![aplicacaoEditar](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png "![aplicacaoEditar](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)")
 3. Click on the **pencil** symbol over the **Cliente **form;
 4. Click on the **Schemas de Layout **tab;
 5. Click on the **Incluir Nova seção **button;
 6. Give this section a name;
-7. In the **Campos disponíveis** column, drag the field you want to the **Campos da coluna 1** area, below the name of the section created; [![arrastandoCampo](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png "![arrastandoCampo](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)") [![arrastandoCampo2](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png "![arrastandoCampo2](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)") [![seçãoCriada](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png "![seçãoCriada](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)")
+7. In the **Campos disponíveis** column, drag the field you want to the **Campos da coluna 1** area, below the name of the section created; [![arrastandoCampo](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png "![arrastandoCampo](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)") [![arrastandoCampo2](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png "![arrastandoCampo2](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)") [![seçãoCriada](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png "![seçãoCriada](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)")
 8. Click on the **Salvar** button.
 
 ### Creating an email template
 
-The template of the email to be sent, as for Abandoned Cart, is configured in the CMS module. For help with configuration, [use our model template](//assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "use our model template").
+The template of the email to be sent, as for Abandoned Cart, is configured in the CMS module. For help with configuration, [use our model template](https://assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "use our model template").
 
 1. Access the **CMS** module;
 2. Click on **Portal**;
-3. [Click here to download the model template](//assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html);
+3. [Click here to download the model template](https://assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html);
 4. Click on **Templates de página**;
 5. Click on **novo template**;
 6. Enter the name and paste the code of your template. Attention: If you are using the model template, remember to change the `TEMPLATE_DE_PRATELEIRA` code for the id of your shelf template and the `NOME_DA_LOJA` code to the URL of your store.
@@ -103,7 +103,7 @@ Click on the **Salvar Pasta** button.
 After creating a folder, associate the page template with the page layout.
 
 1. Click on the folder created;
-2. Click on **novo layout**;[![novoLayout](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png "![novoLayout](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)")
+2. Click on **novo layout**;[![novoLayout](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png "![novoLayout](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)")
 3. Select the template created previously;
 4. Click on the **Salvar** button.
 
@@ -123,7 +123,7 @@ In **Filtro adicional**, configure as follows:
 
 Click on the **Incluir grupo** button, then click on **Incluir filtro** and complete as follows:
 - **Data do último trigger enviado** Menor ou igual `DATAL ATUAL` &#8211; `Subtrair dias` &#8211; `7` or
-- **Data do último trigger enviado** Está nulo [![CondicoesTrigger](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png "![CondicoesTrigger](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)")
+- **Data do último trigger enviado** Está nulo [![CondicoesTrigger](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png "![CondicoesTrigger](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)")
 
 Then, follow these steps:
 
diff --git a/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md b/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md
index ecf51b933..af94aa25e 100644
--- a/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md
+++ b/docs/tutorials/en/configuring-promotions-with-a-highlightflag.md
@@ -21,7 +21,7 @@ Tutorial valid only for Legacy CMS Stores.
 
 The promotion highlight is a notice that can be placed on shelves and product pages stating that the product is eligible for a promotion. A common example is an image below a product picture indicating free shipping.
 
-![ExemploPromocaoDestaque2](//images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
+![ExemploPromocaoDestaque2](https://images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
 
 Not all promotions are eligible to be featured. This possibility is limited to the types below:
 
@@ -67,9 +67,9 @@ This configuration consists of editing the page template used for the product pa
 9. On the right side of the screen, click on **New Layout**.
 10. In the side menu, click on the layout with a red check mark, and in the __Template__ field check the name of the template used.
 
-![Layout com check - PT](//images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
+![Layout com check - PT](https://images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
 
-![Template](//images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
+![Template](https://images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
 
 11. Go back to the side menu and click on the **HTML Templates** folder.
 12. Click on the template you found in @Product@.
diff --git a/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md b/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md
index c4c24f134..62f97b332 100644
--- a/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md
+++ b/docs/tutorials/en/configuring-pwa-in-your-store-framework-store.md
@@ -26,11 +26,11 @@ To configure a PWA in your store, go to **Store Settings > Storefront > Store**
 1. Click the **PWA** tab.
 2. Set the **Theme color**, **Background color** and add the **Android logo icon (512x512, PNG)** and **iOS logo icon (512x512, PNG)**. The colors must be specified in hexadecimal code (e.g., #F71963), and the icons must have a size of 512x512 px and a `.png` extension.
 
-  ![pwa-settings-1-en](//images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/8b7909e47d4ebe3906f12fc997dec948/pwa-settings-1-en.png)
+  ![pwa-settings-1-en](https://images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/8b7909e47d4ebe3906f12fc997dec948/pwa-settings-1-en.png)
 
 3. Scroll down and go to the **Other PWA settings** field. Click the arrow to show the other settings.
 
-  ![pwa-settings-2-en](//images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/7e6e92b83cdc7af103e35f19d740343d/pwa-settings-2-en.png)
+  ![pwa-settings-2-en](https://images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/7e6e92b83cdc7af103e35f19d740343d/pwa-settings-2-en.png)
 
 4. In **Other PWA settings**, complete the fields as indicated below:
 
@@ -60,7 +60,7 @@ To configure a PWA in your store, go to **Store Settings > Storefront > Store**
     - **Add to home screen**: When activated, it allows the user to install the PWA.
     - **"Add to home screen" prompt**: Defines the moment when the PWA installation will be recommended to the user. One of the following values can be assigned: On the first visit, On the first item added to the cart, or On the first order. This option only applies when **Add to Home Screen** is activated.
 
-   ![pwa-settings-3-en](//images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/8496511fdfbe7d9bdd30915bd0d4e3b9/pwa-settings-3-en.png)
+   ![pwa-settings-3-en](https://images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/8496511fdfbe7d9bdd30915bd0d4e3b9/pwa-settings-3-en.png)
 
 5. Save changes by clicking `SAVE`.
 
diff --git a/docs/tutorials/en/configuring-redirects.md b/docs/tutorials/en/configuring-redirects.md
index 754999136..ca2d45e69 100644
--- a/docs/tutorials/en/configuring-redirects.md
+++ b/docs/tutorials/en/configuring-redirects.md
@@ -27,7 +27,7 @@ To configure a redirect, follow the steps below.
 
 You must fill in the fields below.
 
-![redirecionamentos-adminv4-EN](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
+![redirecionamentos-adminv4-EN](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/c67dd6c3ebe5563f2a32492db7a94298/image.png)
 
 ### General information
 
diff --git a/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
index db6c61f7b..9e3990a35 100644
--- a/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
+++ b/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
@@ -30,15 +30,15 @@ To assign sellers to a particular buying organization, follow the steps below:
 <li>In the VTEX Admin, go to <b>Apps > B2B Organizations & Cost Centers > Organizations</b>, or type <b>Organizations</b> in the search bar at the top of the page.</li>
 <li>In the <b>Organizations</b> tab, click the name of the desired buying organization.</li>
 
-![Organization](//images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/c127c65c00d63077e2a61463b8fcc2d7/ORGANIZACOES_-_EN.jpg)
+![Organization](https://images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/c127c65c00d63077e2a61463b8fcc2d7/ORGANIZACOES_-_EN.jpg)
 
 <li>In the <b>Sellers</b> tab, under <b>Disponible</b>, select the desired sellers.</li>
 
-![Details Organization](//images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/860e494a5cb6ed7c25ed7f7423ae082e/ORGANIZACOES-DETALHES2_-_EN__com_clique_.jpg)
+![Details Organization](https://images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/860e494a5cb6ed7c25ed7f7423ae082e/ORGANIZACOES-DETALHES2_-_EN__com_clique_.jpg)
 
 <li>Click the <b>ADD TO ORG</b> button.</li>
 
-![Details Organizations 2](//images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/ba7c7629dda12d95e114ecb0570e4927/ORGANIZACOES-DETALHES2_-_EN.jpg)
+![Details Organizations 2](https://images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/ba7c7629dda12d95e114ecb0570e4927/ORGANIZACOES-DETALHES2_-_EN.jpg)
 
 <li>Click <b>Save</b>.</li>
 
diff --git a/docs/tutorials/en/configuring-seo-in-your-store.md b/docs/tutorials/en/configuring-seo-in-your-store.md
index 84b86c211..b2b472c1d 100644
--- a/docs/tutorials/en/configuring-seo-in-your-store.md
+++ b/docs/tutorials/en/configuring-seo-in-your-store.md
@@ -35,7 +35,7 @@ In all VTEX IO stores, you can configure these parameters natively by following
   - **Meta description tag**: Provide a brief description of the page's content. It should be informative and contain relevant keywords.
   - **Meta robots tag**: Specify how search engines should crawl and index a specific page. The default values are `index, follow`. For additional values compatible with Google, see the [list of valid rules](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag#directives). 
 
-  ![seo-en](//images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/b545a83de82a94a5551a222f9b15b5a5/seo-en.png)
+  ![seo-en](https://images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/b545a83de82a94a5551a222f9b15b5a5/seo-en.png)
 
 ### Favicons
 
@@ -43,7 +43,7 @@ In all VTEX IO stores, you can configure these parameters natively by following
 2. Click the **General** tab.
 3. Click **Add**.
 
-  ![favicon-en](//images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/bba39b30bedfe404b3111a06853a42de/favicons-en.png)
+  ![favicon-en](https://images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/bba39b30bedfe404b3111a06853a42de/favicons-en.png)
 
 4. A new screen will open for completion based on the following guidelines:
 
@@ -54,7 +54,7 @@ In all VTEX IO stores, you can configure these parameters natively by following
 
     See the example below:
 
-    ![relacao-favicon-en](//images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/9d4f662c2be71d1d33ec68495b594049/relacao-favicon-en.png)
+    ![relacao-favicon-en](https://images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/9d4f662c2be71d1d33ec68495b594049/relacao-favicon-en.png)
 
 5. Click **Apply** to reflect the settings in your store. This process may take a few minutes.
 
diff --git a/docs/tutorials/en/configuring-shipping-promotions.md b/docs/tutorials/en/configuring-shipping-promotions.md
index 49fb76aca..e0c0ec091 100644
--- a/docs/tutorials/en/configuring-shipping-promotions.md
+++ b/docs/tutorials/en/configuring-shipping-promotions.md
@@ -40,40 +40,40 @@ Below you will find some of the scenarios you can configure on the VTEX platform
 If you enable the option **Apply discount only to the cheapest shipping rate**, the discount will be applied only to the lowest estimated shipping rate. This option is enabled by default, but you can disable it if you prefer to configure the promotion according to [Scenario 3](#scenario-3) or [Scenario 4](#scenario-4). 
 
 #### Configuration
-![Apply the discount only to the cheapest shipping option - EN](//images.ctfassets.net/alneenqid6w5/7MjVSslJUZjkcKepNjene6/630faf430976850a15d833f09919e515/image.png)
+![Apply the discount only to the cheapest shipping option - EN](https://images.ctfassets.net/alneenqid6w5/7MjVSslJUZjkcKepNjene6/630faf430976850a15d833f09919e515/image.png)
 
 #### Result
-![saggin frete ingles.PNG?h=250](//images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
+![saggin frete ingles.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
 
 ### Scenario 2
 
 If you disable the option **Apply discount only to the cheapest shipping rate**, the discount will be applied to all available shipping rates.
 
 #### Configuration
-![Nenhum frete selecionado - EN](//images.contentful.com/alneenqid6w5/3hN4Ed2L4VP3us5NBQpEfV/ff352c5a835e77ed19dc2d5c33cddc73/image.png)
+![Nenhum frete selecionado - EN](https://images.contentful.com/alneenqid6w5/3hN4Ed2L4VP3us5NBQpEfV/ff352c5a835e77ed19dc2d5c33cddc73/image.png)
 
 #### Result
-![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Scenario 3
 
 If you enable only the **Shipping Method** option and select the shipping types you want, the shipping discount will be applied to all selected shipping types.
 
 #### Configuration
-![Shipping Method - EN](//images.ctfassets.net/alneenqid6w5/3dR7FNv3WNUMeX6o97RywQ/8711094472ac78e3843290d769ad9c26/image.png)
+![Shipping Method - EN](https://images.ctfassets.net/alneenqid6w5/3dR7FNv3WNUMeX6o97RywQ/8711094472ac78e3843290d769ad9c26/image.png)
 
 #### Result
-![saggin frete ingles.PNG?h=250](//images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
+![saggin frete ingles.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
 
 ### Scenario 4
 
 If you enable the options **Shipping Method** and **Apply discount only when one of the above carriers is selected by the customer** and select the shipping types you want, the shipping discount will be applied to all selected shipping types only when the customer chooses the shipping type at checkout.
 
 #### Configuration
-![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - EN](//images.ctfassets.net/alneenqid6w5/3hxzt9qlLT4oWzBiAUUUrr/f64db376da1db7005848382bd2d2d532/image.png)
+![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - EN](https://images.ctfassets.net/alneenqid6w5/3hxzt9qlLT4oWzBiAUUUrr/f64db376da1db7005848382bd2d2d532/image.png)
 
 #### Result
-![saggin frete ingles.PNG?h=250](//images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
+![saggin frete ingles.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/fbTenTsRWQULggd7ET5Ng/6e0b5e52a20fe99e01ed786b4f90f5e6/saggin_frete_ingles.PNG_h_250)
 
 In summary, the purpose of the option **Apply discount only when one of the above carriers is selected by the customer** is to apply the discount only when the carrier is selected.
 
diff --git a/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
index 1f2e9a958..5282753ad 100644
--- a/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
+++ b/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
@@ -56,7 +56,7 @@ Once you have registered with Apple, enable the option of logging in to your sto
 
     Check out the [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login) developer guide to learn how to get these credentials.
 
-    ![apple-id-setup-en](//images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/aa8a24c6942c41dc122db4172e6730f6/apple-id-setup-en.png)
+    ![apple-id-setup-en](https://images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/aa8a24c6942c41dc122db4172e6730f6/apple-id-setup-en.png)
 
 5. Click `Save`.
 6. Click `Webstore Providers` to go back to the previous page.
diff --git a/docs/tutorials/en/configuring-the-past-prices-control.md b/docs/tutorials/en/configuring-the-past-prices-control.md
index 5041f42f2..f33f78125 100644
--- a/docs/tutorials/en/configuring-the-past-prices-control.md
+++ b/docs/tutorials/en/configuring-the-past-prices-control.md
@@ -33,7 +33,7 @@ See the complete list of controls for templates [here](http://help.vtex.com/tuto
 
 The default exhibition method for the values looks like the image below. The year, month and lowest amount invoiced this month are shown in sequence.
 
-![HistPrecos](//images.contentful.com/alneenqid6w5/2AX7uKU4zW66sA0AICcEM2/81042cedd7d0ef937b1c56a8878d8d0c/HistPrecos.png)
+![HistPrecos](https://images.contentful.com/alneenqid6w5/2AX7uKU4zW66sA0AICcEM2/81042cedd7d0ef937b1c56a8878d8d0c/HistPrecos.png)
 
 If you want to show these details in another way, you will have to get a layout agency to customize the model.
 
diff --git a/docs/tutorials/en/configuring-the-pickup-in-store.md b/docs/tutorials/en/configuring-the-pickup-in-store.md
index 5da12c9c8..d597b6638 100644
--- a/docs/tutorials/en/configuring-the-pickup-in-store.md
+++ b/docs/tutorials/en/configuring-the-pickup-in-store.md
@@ -29,17 +29,17 @@ The store pickup configuration enables the customer to opt not to receive the pr
 3. For these carriers, it is recommended not to charge for freight.
 4. After creating all the carriers, you must create a carrier with the generic name _Retirada no local _to be used in programming the store front-end (in the freight selection option).
 
-![](//images.contentful.com/alneenqid6w5/1aPl4HkPD8IagOICkCuigu/185dffc5b9bfd322697b6bf7ae0e7942/1.jpg)
+![](https://images.contentful.com/alneenqid6w5/1aPl4HkPD8IagOICkCuigu/185dffc5b9bfd322697b6bf7ae0e7942/1.jpg)
 
 ## Visual Customization (Front-end)
 
 A _JavaScript_ file must be included in the store checkout, as shown below.
 
 1. The user makes a normal purchase of products up to the checkout page.
-2. After completing personal details, the user reaches the carrier selection area. The tool will normally show all the available methods of delivery configured. However after configuring them, the _JavaScript_ must “conceal” the options for stores available and show only the generic transporter, created in step 4 above, called **Retirada no local** (or Retirada en Sucursal – in Spanish).![OpcoesdeEnvio](//images.contentful.com/alneenqid6w5/3YpLqm1q2ckOm4i4g8KWAQ/edc9d9ff1e32352306c1b152c12997e7/OpcoesdeEnvio.png)
-3. When the user selects the store pickup _(_retirada no local or retirada en sucursal) option, the JavaScript opens a lightbox on the screen with a list of stores for the user to select. The options appearing here are the transporters registered with admin in steps 1 and 2. The image below shows how the store chose to present visually the selection of stores for pickup.![](//images.contentful.com/alneenqid6w5/XZ0kevBW6sEK2sGKsYsGm/84c5681cf6c9cf923e90d337d3a727d8/3.jpg)
-4. When the user selects an option, the _JavaScript _closes the _Lightbox_ and returns to the freight selection option, indicating that the selection has been successfully saved.![](//assets.contentful.com/alneenqid6w5/4ekRwP5Hy0yE8ckaWGCAQG/b358a05721f4ce0cc0221fd6eb0ff955/4.bmp)
-5. After returning to the selection, the _JavaScript _must alter the generic delivery option to the real option of the store registered, which up to that moment was not visible in the front-end.![](//images.contentful.com/alneenqid6w5/3DlztWQIEUOqoomMeA8yiq/15f3ffa1fe1a10d004ab0c13938ec7fe/5.jpg)
+2. After completing personal details, the user reaches the carrier selection area. The tool will normally show all the available methods of delivery configured. However after configuring them, the _JavaScript_ must “conceal” the options for stores available and show only the generic transporter, created in step 4 above, called **Retirada no local** (or Retirada en Sucursal – in Spanish).![OpcoesdeEnvio](https://images.contentful.com/alneenqid6w5/3YpLqm1q2ckOm4i4g8KWAQ/edc9d9ff1e32352306c1b152c12997e7/OpcoesdeEnvio.png)
+3. When the user selects the store pickup _(_retirada no local or retirada en sucursal) option, the JavaScript opens a lightbox on the screen with a list of stores for the user to select. The options appearing here are the transporters registered with admin in steps 1 and 2. The image below shows how the store chose to present visually the selection of stores for pickup.![](https://images.contentful.com/alneenqid6w5/XZ0kevBW6sEK2sGKsYsGm/84c5681cf6c9cf923e90d337d3a727d8/3.jpg)
+4. When the user selects an option, the _JavaScript _closes the _Lightbox_ and returns to the freight selection option, indicating that the selection has been successfully saved.![](https://assets.contentful.com/alneenqid6w5/4ekRwP5Hy0yE8ckaWGCAQG/b358a05721f4ce0cc0221fd6eb0ff955/4.bmp)
+5. After returning to the selection, the _JavaScript _must alter the generic delivery option to the real option of the store registered, which up to that moment was not visible in the front-end.![](https://images.contentful.com/alneenqid6w5/3DlztWQIEUOqoomMeA8yiq/15f3ffa1fe1a10d004ab0c13938ec7fe/5.jpg)
 6. After leaving this selection area, the customer follows the normal purchase flow.
 
 _Insert a caption indicating how soon the order will be available for pickup at the physical store._
@@ -48,6 +48,6 @@ _Insert a caption indicating how soon the order will be available for pickup at
 
 On the OMS it will be possible to view the customer’s order, showing which store was selected for the pickup. You can find this information in the area where the products are shown.
 
-![](//images.contentful.com/alneenqid6w5/5LIVnwfutq826ciMOOcmUQ/6b1e5180ff186b6199460eb0d7a456c2/6.jpg)
+![](https://images.contentful.com/alneenqid6w5/5LIVnwfutq826ciMOOcmUQ/6b1e5180ff186b6199460eb0d7a456c2/6.jpg)
 
 Don’t forget! The JavaScript required for this situation must be developed by the store development team or by one of our [accredited partners](http://store.vtex.com "accredited partners").
diff --git a/docs/tutorials/en/configuring-the-scheduled-delivery.md b/docs/tutorials/en/configuring-the-scheduled-delivery.md
index 0b1198e17..0c21f2256 100644
--- a/docs/tutorials/en/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/en/configuring-the-scheduled-delivery.md
@@ -31,7 +31,7 @@ On **Inventory & shipping**, access **Dashboard** and select the desired **Carri
 Then on **Shipping method**, click on **Scheduled Delivery**.
 
 
-![entrega-agendada en](//images.ctfassets.net/alneenqid6w5/5o3hYPSCha8IuYs2QOIgIc/09756c4259fc66808dafd6ce07e39eb8/entrega-agendada_en.png)
+![entrega-agendada en](https://images.ctfassets.net/alneenqid6w5/5o3hYPSCha8IuYs2QOIgIc/09756c4259fc66808dafd6ce07e39eb8/entrega-agendada_en.png)
 For a better understandment about this sectin fields fulfillments, check out our document on how to [register a carrier](http://help.vtex.com/en/tutorial/registering-a-carrier).
 
 In this area, we have the following data:
@@ -45,7 +45,7 @@ In this area, we have the following data:
 Using the same situation of the store mentioned above, this would be the carrier configuration suitable to their demand:
 
 
-![entrega-agendada-exemplo en](//images.ctfassets.net/alneenqid6w5/1VBGSFNpZ6KcM6wU0y62k0/956e0301532b9d2d615572e215d47e81/entrega-agendada-exemplo_en.png)
+![entrega-agendada-exemplo en](https://images.ctfassets.net/alneenqid6w5/1VBGSFNpZ6KcM6wU0y62k0/956e0301532b9d2d615572e215d47e81/entrega-agendada-exemplo_en.png)
 
 Assuming that Inventory time is 2 days, Dock time is 1 day, and Freight Timetable previews 5 days, the first day available for delivery will be **8** days after the date the request was made and, since the maximum delivery time is 10 days, the last day available for customer's choice will be the **18th** day after the date the request was made.
 
diff --git a/docs/tutorials/en/configuring-the-store-domain.md b/docs/tutorials/en/configuring-the-store-domain.md
index c9aca438f..4ce19a67a 100644
--- a/docs/tutorials/en/configuring-the-store-domain.md
+++ b/docs/tutorials/en/configuring-the-store-domain.md
@@ -26,7 +26,7 @@ Domain-related settings are necessary for a web address to be correctly routed t
 
 The store's address is composed of the following elements:
 
-![url-diagram-en](//images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/ad84010eef6bab7fae5123f18ab0887d/url-diagram-en.png)
+![url-diagram-en](https://images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/ad84010eef6bab7fae5123f18ab0887d/url-diagram-en.png)
 
 | Element | Description | Example |
 |---|---|---|
diff --git a/docs/tutorials/en/configuring-your-layout.md b/docs/tutorials/en/configuring-your-layout.md
index 9dd0ae1dc..3fe7f914d 100644
--- a/docs/tutorials/en/configuring-your-layout.md
+++ b/docs/tutorials/en/configuring-your-layout.md
@@ -21,5 +21,5 @@ If your store doesn't have a team of front-end developers, we suggest you purch
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
 
-<video class="wp-video-shortcode" id="video-2571-5" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4?_=5" />[//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4](//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4 "//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4")</video>
+<video class="wp-video-shortcode" id="video-2571-5" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4?_=5" />[//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4](https://downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4 "//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4")</video>
 
diff --git a/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md b/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md
index f2fab78b2..2f6f6e6a7 100644
--- a/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md
+++ b/docs/tutorials/en/copying-a-layout-from-one-web-site-to-another.md
@@ -25,9 +25,9 @@ To do this, in the VTEX Admin, access **Storefront > Layout > CMS** and click on
 
 The button is in the upper right corner, as shown in the image below.
 
-!![copiar layout](//images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
+!![copiar layout](https://images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
 The system will ask you which web site you want to copy the layout to.
 
 Select the web site and click __Copy Layout__.
 
-![copyLayout2](//images.contentful.com/alneenqid6w5/1KPGgtczwMmKEeQKOM44yk/3e74ac50ac9a0fbe89f0de3fbd4a4d7a/copyLayout2.png)
+![copyLayout2](https://images.contentful.com/alneenqid6w5/1KPGgtczwMmKEeQKOM44yk/3e74ac50ac9a0fbe89f0de3fbd4a4d7a/copyLayout2.png)
diff --git a/docs/tutorials/en/coupons-list-beta.md b/docs/tutorials/en/coupons-list-beta.md
index 0ce3a6460..3dc72ef1f 100644
--- a/docs/tutorials/en/coupons-list-beta.md
+++ b/docs/tutorials/en/coupons-list-beta.md
@@ -31,7 +31,7 @@ On this page, you can:
 
 To access this page in the VTEX Admin, click **Promotions > Coupons**.
 
-![lista-cupons](//images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/d525a4dd9ed00d8895cd6be9fc96b538/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_15_22_1.png)
+![lista-cupons](https://images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/d525a4dd9ed00d8895cd6be9fc96b538/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_15_22_1.png)
 
 Below you will find a description of the page components and the actions you can perform.
 
@@ -83,7 +83,7 @@ The generated file contains the information described below.
 
 Here is an example of an exported CSV file:
 
-![cupons-exportados](//images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
+![cupons-exportados](https://images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
 
 #### Exporting coupon batch codes
 
@@ -100,13 +100,13 @@ To view or export all the codes within a coupon batch, you must follow the steps
     * <i class="far fa-clone"></i> **Copy all:** Allows you to copy the generated codes to your clipboard. You can also copy each code individually by clicking it.
     * **Export:** Allows exporting the generated coupons to a CSV file. The exported file contains a single column, with one code per row.
 
-![export-coupons](//images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/92c61578ca7684d4f9a80dbcf0b5f690/image_7.png)
+![export-coupons](https://images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/92c61578ca7684d4f9a80dbcf0b5f690/image_7.png)
 
 ### View coupon usage
 
 To view the total number of active coupons and the remaining available space for new coupons, click <i class="fas fa-chart-line"></i> `Coupon usage`.
 
-![coupon-usage](//images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7773a8f9dc9f68d349183cad1dcc082a/image_8.png)
+![coupon-usage](https://images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7773a8f9dc9f68d349183cad1dcc082a/image_8.png)
 
 You are allowed a maximum of five thousand active coupons. To free up space, you can archive coupons in the [Coupon list](#coupon-list). If you need to increase the limit of active coupons, please contact our [Support team](https://support.vtex.com/hc/en-us/requests).
 
@@ -155,13 +155,13 @@ The **View usage details** modal presents information on how each coupon was use
 
     This section presents the list of orders in which a coupon has been used and allows you to search by order number. When you click on the order number, you will be redirected to the order details page in **Orders management**.
 
-![view-usage-details](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
+![view-usage-details](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
 
 * **General usage of the coupon codes** (coupon batches): Displays the total amount of times of the codes in a coupon batch have been used and the amount of remaining uses, if you have set a usage limit.
 
    This section also displays the list of codes in the coupon batch and allows you to search for a specific code. When you click on a code, you have access to the list of orders where the code has been used and you can search by an order number. Clicking on an order number will take you to the order details page in **Orders management**.
 
-![select-the-code-coupon-batch](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
+![select-the-code-coupon-batch](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
 
 ## Learn more
 * [Coupons](https://help.vtex.com/en/tutorial/coupons-beta--1aAEN3ADpz19ss5JCIEBdL)
diff --git a/docs/tutorials/en/create-a-talk-to-us-form-using-master-data.md b/docs/tutorials/en/create-a-talk-to-us-form-using-master-data.md
index 26c7a0021..93bd7e4a9 100644
--- a/docs/tutorials/en/create-a-talk-to-us-form-using-master-data.md
+++ b/docs/tutorials/en/create-a-talk-to-us-form-using-master-data.md
@@ -117,6 +117,6 @@ The plug-in has been developed to help you install the form on the template. To
 - jQuery
 - Bootstrap
 
-[For more details access the attached example](//assets.contentful.com/alneenqid6w5/4rfOv1xQoEuwWYS0sq24QM/3099aa480d85a9ca4d2ce50dfef64a68/contactMasterData.zip "For more details access the attached example").
+[For more details access the attached example](https://assets.contentful.com/alneenqid6w5/4rfOv1xQoEuwWYS0sq24QM/3099aa480d85a9ca4d2ce50dfef64a68/contactMasterData.zip "For more details access the attached example").
 
 __Important__: This plug-in has been developed to help you create the Talk to Us form using Master Data. VTEX **DOES NOT** offer support for this extension and its code is open, so it can be altered and adapted.
diff --git a/docs/tutorials/en/creating-a-campaign-audience.md b/docs/tutorials/en/creating-a-campaign-audience.md
index 0a28bd351..633f5344c 100644
--- a/docs/tutorials/en/creating-a-campaign-audience.md
+++ b/docs/tutorials/en/creating-a-campaign-audience.md
@@ -69,7 +69,7 @@ After clicking `Create New Target Audience`, you must follow the instructions be
     * **or:** The campaign audience will consist of customers fitting any target audience.
     * **and:** The campaign audience will consist of customers fitting all the target audiences, summing up all their criteria.
 
-![publico-alvo-e-ou-en](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
+![publico-alvo-e-ou-en](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/655312e51c8e30a847cb012d4382de39/en-publico-alvo.gif)
 
 ### Define your target audience
 
@@ -85,7 +85,7 @@ After clicking `Create New Target Audience`, you must follow the instructions be
 
 For example: The target audience includes items whose brand is **Nike**, as illustrated below. The configuration also indicates that at least 3 items must meet the criteria. Therefore, a customer must have at least **3** items in the shopping cart to be included in the target audience.
 
-![exemplo-marca-publico-alvo-en](//images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7aeb73bd45e025ca84337c37d6800991/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_10_40_1.png)
+![exemplo-marca-publico-alvo-en](https://images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7aeb73bd45e025ca84337c37d6800991/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_10_40_1.png)
 
 ### Conditions for your target audience to be applied
 
diff --git a/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md b/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
index 4cd412223..9dc6e817f 100644
--- a/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
+++ b/docs/tutorials/en/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
@@ -21,7 +21,7 @@ If your end customer buys a product on any of your channels (online or physical
 
 However, you may prefer this store to work as a pickup point __even in a stockout scenario__. For this, your logistics must make sure that the product will reach that store from another stock - for example, from the e-commerce one. In this case, you need to have an e-commerce shipping policy in which the pickup point of the physical store is configured.
 
-![Creating a contingency pickup point to guarantee it as an option at checkout](//images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/962f5bd2fb48459656477102f81644c2/diagrama-como-criar-um-ponto-de_contigencia-en.jpg)
+![Creating a contingency pickup point to guarantee it as an option at checkout](https://images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/962f5bd2fb48459656477102f81644c2/diagrama-como-criar-um-ponto-de_contigencia-en.jpg)
 
 ## How to set up a contingency pickup point
 
diff --git a/docs/tutorials/en/creating-a-coupon-beta.md b/docs/tutorials/en/creating-a-coupon-beta.md
index 2f373532a..338b2c9da 100644
--- a/docs/tutorials/en/creating-a-coupon-beta.md
+++ b/docs/tutorials/en/creating-a-coupon-beta.md
@@ -42,7 +42,7 @@ The form for creating or editing a coupon has the following fields:
 
 The top dashboard of the form for creating and editing coupons indicates the number of times a coupon has been used, the number of remaining uses of that coupon, and the number of promotions associated with the coupon, as illustrated below.
 
-![create-coupon-1](//images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/12a3cfbee85e20584d8f110a419c6cfe/create-coupon-1.png)
+![create-coupon-1](https://images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/12a3cfbee85e20584d8f110a419c6cfe/create-coupon-1.png)
 
 By clicking on the information on the dashboard, you may access the modal **View usage details**, which displays the following details.
 
@@ -54,11 +54,11 @@ By clicking on the information on the dashboard, you may access the modal **View
 
     If the coupon is a single coupon, this section presents the list of orders in which a coupon has been used and allows you to search by order number. When you click on the order number, you will be redirected to the order details page in **Orders management**.
 
-    ![view-usage-details](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
+    ![view-usage-details](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/628adb058ee54d89dc271d31abb9e26c/view-usage-details.png)
 
     If it is a coupon batch, this section displays the list of codes from the batch and allows you to search for a specific code. If you click on a code,  you will see the list of orders where the code has been used and allows you to search for an order number. Clicking on the order number will then take you to the order details page in __Orders management__.
 
-![select-the-code-coupon-batch](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
+![select-the-code-coupon-batch](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/e30ef211427e536244083f5ad2045fba/selecione-o-codigo-grupo-en.PNG)
 
 ### General
 
@@ -94,7 +94,7 @@ If you have created a [coupon batch](https://help.vtex.com/en/tutorial/coupons-b
 * <i class="far fa-clone"></i> **Copy all:** Allows you to copy the generated codes to your clipboard. After that, you can paste them in a spreadsheet editor, such as Excel or Google Sheets. You can also copy each code individually by clicking it.
 * **Export:** Allows exporting the generated coupons to a CSV file. The exported file contains a single column, with one code per row.
 
-![cupons-gerados-en](//images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/640d534c61c09cae6bb345bbbca25173/cupons-gerados-en.gif)
+![cupons-gerados-en](https://images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/640d534c61c09cae6bb345bbbca25173/cupons-gerados-en.gif)
 
 ## Associating a coupon with a promotion 
 
diff --git a/docs/tutorials/en/creating-a-more-for-less-promotion.md b/docs/tutorials/en/creating-a-more-for-less-promotion.md
index f5b5ca82e..16fbeade2 100644
--- a/docs/tutorials/en/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/en/creating-a-more-for-less-promotion.md
@@ -51,7 +51,7 @@ In this section, we provide information on the promotion overview.
 - **Additional information (optional):**: Allows you to add a name and value to the promotion.
 - **Promotion is highlighted:** Adds a tag with the promotion name to the window display and the product page. This tag will only be added if you use the right promotion display control in the template.<vtex.cmc:discountHightLight/>. Required field.
 
-![Dados gerais 1 - EN](//images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/244f3cfaeed58c7d6b5ae309ca815089/Dados_gerais_1_-_EN.png)
+![Dados gerais 1 - EN](https://images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/244f3cfaeed58c7d6b5ae309ca815089/Dados_gerais_1_-_EN.png)
 
 ### Restrict this promotion to products from sellers
 
@@ -68,7 +68,7 @@ For the promotion to be valid for all sellers, leave the field blank.
 </ol>
 </div>
 
-![Restringir - EN](//images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/8dba06aef0da8ce4d546c0e2fea91917/Restringir_-_EN.png)
+![Restringir - EN](https://images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/8dba06aef0da8ce4d546c0e2fea91917/Restringir_-_EN.png)
 
 ### Trade Policy
 
@@ -81,7 +81,7 @@ In this section, you can set the trade policies valid for the promotion. You can
 
 For the promotion to be valid for all trade policies, leave the selection empty.
 
-![Politica - ES](//images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/50371b6897f37bce42ac8e70110ca90b/Politica_-_EN.png)
+![Politica - ES](https://images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/50371b6897f37bce42ac8e70110ca90b/Politica_-_EN.png)
 
 ## 2. More for Less
 
@@ -99,7 +99,7 @@ In this section, you can define the products, number of items, and discounts inc
    - **With a discount of**: the percentage discount the customer will receive if they buy the number of items defined in the promotion.
    - **With a maximum price per item of**: the maximum price per item the customer will pay if they buy the number of items defined in the promotion.
 
-![Leve Mais - EN](//images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/8e4b955432b5d2d10ab57e8de7a79b9d/Leve_mais_-_EN.png)
+![Leve Mais - EN](https://images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/8e4b955432b5d2d10ab57e8de7a79b9d/Leve_mais_-_EN.png)
 
 ### Advanced settings
 In this section, you can specify how the discount will be applied.
@@ -112,7 +112,7 @@ The discount must be applied:
   - **The lowest-priced products**: the discount will be applied to the cheapest items in the promotion.
   - **The highest-priced products**: the discount will be applied to the most expensive items in the promotion.
 
-![Leve Mais por menos - EN](//images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/09d9ff06ee5085c52862aa85e5f8baa5/Leve_Mais_por_menos_-_EN.png)
+![Leve Mais por menos - EN](https://images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/09d9ff06ee5085c52862aa85e5f8baa5/Leve_Mais_por_menos_-_EN.png)
 
 #### How must the discount be distributed?
 
@@ -136,7 +136,7 @@ In this section, we will detail the conditions you must apply for a promotion to
   <p> By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
  </div>
 
-![Condições de promoção - EN](//images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/8efc11e8c289f9777a22e3b7d29362d5/Condi__es_de_promo__o_-_EN.png)
+![Condições de promoção - EN](https://images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/8efc11e8c289f9777a22e3b7d29362d5/Condi__es_de_promo__o_-_EN.png)
 
 ## 4. Restrictions and limitations of use
 
@@ -148,4 +148,4 @@ In this section, you will find important information about the promotion conditi
 - **Apply with other promotions**: if selected, more than one promotion can be applied simultaneously, regardless of the discount type. Learn more in the [How promotion competition works](https://help.vtex.com/en/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270) article.
 - **Apply with manual prices**: allows the promotion to apply to products whose prices were manually added via telesales. To enable the manual pricing feature, use the [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm) endpoint.
 
-![Restrições e limitações - EN](//images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/4c779dc8723b31d77e1c36871d1bb051/Restri__es_e_limita__es_-_EN.png)
+![Restrições e limitações - EN](https://images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/4c779dc8723b31d77e1c36871d1bb051/Restri__es_e_limita__es_-_EN.png)
diff --git a/docs/tutorials/en/creating-a-personalized-master-data-query.md b/docs/tutorials/en/creating-a-personalized-master-data-query.md
index 855f4cb11..bc330e29c 100644
--- a/docs/tutorials/en/creating-a-personalized-master-data-query.md
+++ b/docs/tutorials/en/creating-a-personalized-master-data-query.md
@@ -21,15 +21,15 @@ To create a query, it is necessary to [apply a filter to the list](/en/tutorial/
 
 After filtering, _click on the button **Salvar Consulta** -> give the query a name -> click on the button **Salvar**_.
 
-![image00(3)](//images.contentful.com/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/6698a619ebf6041e828b61ef657ceb89/image003.png)
+![image00(3)](https://images.contentful.com/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/6698a619ebf6041e828b61ef657ceb89/image003.png)
 
 Thus, in order for the enquiry to appear as an option for viewing the list, just reload the application in the **Aplicações** tab. Clicking on the button **Recarregar aplicações**.
 
-![image02(2)](//images.contentful.com/alneenqid6w5/23qCsgXVSYQYmsS6Ya6eAs/99c65c0009dd7f9e75c1ba4a2cea50cc/image022.png)
+![image02(2)](https://images.contentful.com/alneenqid6w5/23qCsgXVSYQYmsS6Ya6eAs/99c65c0009dd7f9e75c1ba4a2cea50cc/image022.png)
 
 Moreover, to view all the queries saved, click on the button **Consultas**, on the form list.
 
-![consulta3](//images.contentful.com/alneenqid6w5/4h0zjZuAc8W8eUaqImo2qg/b1c06c13603d398d1f83bef9f7deb19b/image012.png)
+![consulta3](https://images.contentful.com/alneenqid6w5/4h0zjZuAc8W8eUaqImo2qg/b1c06c13603d398d1f83bef9f7deb19b/image012.png)
 
 It is also interesting to configure a form, so that it always presents the list with the query filter. To do so, follow these steps:
 
@@ -40,4 +40,4 @@ It is also interesting to configure a form, so that it always presents the list
 5. In the option **Consulta Padrão**, select the personalized query you want to display whenever you click on the form.
 6. Click on the **Salvar**** **button.
 
-![consulta5](//images.contentful.com/alneenqid6w5/66y0WU112osUwkwuyMquMW/a9143a8ca1aa05bc49cc69d1dd102002/image032.png)
+![consulta5](https://images.contentful.com/alneenqid6w5/66y0WU112osUwkwuyMquMW/a9143a8ca1aa05bc49cc69d1dd102002/image032.png)
diff --git a/docs/tutorials/en/creating-a-product-collection.md b/docs/tutorials/en/creating-a-product-collection.md
index 007f1f36b..0a64d12b6 100644
--- a/docs/tutorials/en/creating-a-product-collection.md
+++ b/docs/tutorials/en/creating-a-product-collection.md
@@ -25,7 +25,7 @@ To create a collection, follow the instructions below.
 2. Click **Layout**.
 3. Click the folder **Product Clusters (Collections)**.
 4. Click `new collection`, illustrated below.
-	![Layout 4](//images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
+	![Layout 4](https://images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
 5. Fill in the required information:
 	- **Product Cluster Id:** collection identifier code. This field should not be filled in as it is automatically generated by the system when saving.
 	- **Name:** name of the collection.
@@ -49,17 +49,17 @@ Each group can be of one of the following types: __Inclusion__ or __Exclusion__.
 
 To create the Group, just click on the _new group_ button, as shown in the following picture.
 
-![Layout 5](//images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
+![Layout 5](https://images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
 
 To add all the products of a given Department to a Group, just select the Department in question as shown in item 1 of the following figure. This also applies to the products of a given Category (item 2) or sub-category (item 3).
 
-![Filtro_por_categoria](//images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
+![Filtro_por_categoria](https://images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
 
 ### Creating groups by brand
 
 To create a product group with one of more brands, just select the brand desired on the corresponding list. The brands are available in alphabetical order, and by clicking on the letter corresponding to the initial of the brand, the list expands to show the existing brands.
 
-![FIltro_por_marca](//images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
+![FIltro_por_marca](https://images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
 
 ### Creating groups by products in the pre-sale or launch period
 
@@ -73,17 +73,17 @@ These flags are a <em>complement</em> to the choice of products. It is important
 
 Unlike the previous version, where specific products were included using the Product ID, in the new module the manual inclusions are done using the SKU of a product. In the corresponding field, it is possible to type in the ID of one or several SKUs, separating the values with commas. E.g.: `2000004,2000009,2000005`. In spite of the difference in the manner of registration, in practice the effect will be the same, since by associating an SKU with a group, the "father" product of that SKU will also be added to the collection. Where a product has more than one SKU, just add one of the SKUs to the group, and all associated SKUs will be included in it. The field for including the IDs does not permit the typing of alphanumerical characters or the use of combinations of the keys `Control + C` and `Control + V`. Also, when the number of SKUs on the list exceeds 10 items, a pagination control will become available. To exclude an SKU from the list, just click on the red button beside the corresponding SKU.
 
-![Inserir_sku_espec_fico](//images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
+![Inserir_sku_espec_fico](https://images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
 
 ### Importing an SKU list to the group
 
 Although group filters are very practical for automatically creating product groupings, there is a possibility that they might not meet your requirements in specific situations. To get around this, you can import a list of the SKUs that will comprise the group and, consequently, the collection. The Collections module accepts files in the Excel spreadsheet (.xls) or CSV (.csv) formats. In the case of Excel files, all SKU IDs must be arranged in the first column, with no header, as shown in the figure below:
 
-![](//images.contentful.com/alneenqid6w5/6t9b1mIYmsSewCEu8yOagi/c0f73dc7b921e0f7cc65cea1ae572b7b/Importar_lista_de_skus.jpg)
+![](https://images.contentful.com/alneenqid6w5/6t9b1mIYmsSewCEu8yOagi/c0f73dc7b921e0f7cc65cea1ae572b7b/Importar_lista_de_skus.jpg)
 
 After the spreadsheet has been imported by the system, the SKUs are displayed in the following manner:
 
-![Importar_lista_de_skus](//images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
+![Importar_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
 
 The IDs of inactive SKUs will not be imported, even if they are included in the spreadsheet.
 
@@ -93,12 +93,12 @@ _Remember that when one or more groups are selected, only the products in the in
 
 So the Administrator won't have to manually exclude several SKUs one by one, it is possible to also use the SKU importation resource in the same manner as exemplified above. In this case, after the file has been loaded, click on the option _excluir skus_ (item 1 in the picture).
 
-![Excluir_lista_de_skus](//images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
+![Excluir_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
 
-Obtain a model of a file for importation, both for including and excluding items from the collection [here](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "here").
+Obtain a model of a file for importation, both for including and excluding items from the collection [here](https://assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "here").
 
 ## Searching collections
 
 When the quantity of collections exceeds the display limit, which is twenty items, the collections may be found using the search field. The search must be done using the name of the collection.
 
-![Pesquisar_cole__o](//images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
+![Pesquisar_cole__o](https://images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
diff --git a/docs/tutorials/en/creating-a-subscription-plan.md b/docs/tutorials/en/creating-a-subscription-plan.md
index 63bb7afbf..f202df03a 100644
--- a/docs/tutorials/en/creating-a-subscription-plan.md
+++ b/docs/tutorials/en/creating-a-subscription-plan.md
@@ -91,7 +91,7 @@ On this page, you can perform the following actions:
 
 * **Select**: by clicking on the <i class="far fa-square"></i> in the row of each product, you can select products or SKUs individually. Another option is to click on the first <i class="far fa-square"></i> and select all the products and SKUs displayed on the page to add them to the subscription plan, as illustrated in the example below.
 
-![selecionarskus EN](//images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/f833322d9519810cbdd0d1b7e17e4551/selecionarskus_EN.gif)
+![selecionarskus EN](https://images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/f833322d9519810cbdd0d1b7e17e4551/selecionarskus_EN.gif)
 
 * <i class="fas fa-chevron-down"></i> __button__: displays the SKUs, i.e., product variations.
 * **Add**: click on this button to add products or SKUs to the subscription plan.
diff --git a/docs/tutorials/en/creating-a-subscription-promotion.md b/docs/tutorials/en/creating-a-subscription-promotion.md
index 2c0fa9393..c1c042b04 100644
--- a/docs/tutorials/en/creating-a-subscription-promotion.md
+++ b/docs/tutorials/en/creating-a-subscription-promotion.md
@@ -23,7 +23,7 @@ In this article, you will find the step-by-step instructions to create subscript
 4. Select the `Regular` option.
 5. In the **What are the conditions for the promotion to be valid?** section, select the **Is a subscription order** field. This option specifies that the promotion will apply to subscription orders. Only products with a subscription in the cart will receive the discount. To understand configuration possibilities, see the following conditions:
 
-![frequenciaenglish](//images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/a13420f2bd7a22e963097a6e9d415e46/image2__2_.png)
+![frequenciaenglish](https://images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/a13420f2bd7a22e963097a6e9d415e46/image2__2_.png)
 
 - **First orders**: orders that generate subscriptions but are not part of subscription cycles yet.
 - **Recurring orders**: orders from subscription cycles.
diff --git a/docs/tutorials/en/creating-a-type-of-list.md b/docs/tutorials/en/creating-a-type-of-list.md
index ac593c77b..676847439 100644
--- a/docs/tutorials/en/creating-a-type-of-list.md
+++ b/docs/tutorials/en/creating-a-type-of-list.md
@@ -61,7 +61,7 @@ The store owner decides if a list will be related to an event. Once the type of
 
 When **Have an event** is selected, the form offers other configuration options for the event, including all the deadlines for creating this type of list, as shown below.
 
-![eventos.en](//images.ctfassets.net/alneenqid6w5/2ThHmo4PQitWv6EJAoVIdF/7eb8e5c05fee152945b70b3844f63ac0/eventos.en.png)
+![eventos.en](https://images.ctfassets.net/alneenqid6w5/2ThHmo4PQitWv6EJAoVIdF/7eb8e5c05fee152945b70b3844f63ac0/eventos.en.png)
 
 The events area must determine whether a list has a fixed date for the event. Wish lists and purchases lists do not require a fixed date. On the other hand, wedding lists or baby showers must take the date of the event into account, with all the products purchased being delivered in advance.
 
@@ -79,7 +79,7 @@ The following options are available:
 
 After creating the type of list, you will be directed to the screen showing the types of list already registered in the store. This screen provides the following information and functions:
 
-![listagem.en](//images.ctfassets.net/alneenqid6w5/4vHN91gXTrDhXKKa5hEc42/2f28b377bbfcb2cc548b3ce80155037f/listagem.en.png)
+![listagem.en](https://images.ctfassets.net/alneenqid6w5/4vHN91gXTrDhXKKa5hEc42/2f28b377bbfcb2cc548b3ce80155037f/listagem.en.png)
 
 - **Export to Excel**: Allows data for list types to be exported to Excel;
 - **Version**: Identifies lists created in a previous version, with limited functions. The latest version is the “V2”;
diff --git a/docs/tutorials/en/creating-an-oauth2-authentication.md b/docs/tutorials/en/creating-an-oauth2-authentication.md
index 190fa016f..7f8e4739e 100644
--- a/docs/tutorials/en/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/en/creating-an-oauth2-authentication.md
@@ -38,7 +38,7 @@ Have a look at the OAuth2 protocol official guide on https://tools.ietf.org/html
 ### Integrating OAuth2 with VTEX ID
 
 Based on the official documentation, have a look at the illustration below explaining how to integrate OAuth2 with VTEX ID:
-![Fluxo OAuth2 VTEX ID (EN)](//images.ctfassets.net/alneenqid6w5/3qrMFrsucwq2eWSmSAe6yY/ee05f4dafad5d0e2005293274d8f30f8/Fluxo_OAuth2_VTEX_ID__EN_.png)
+![Fluxo OAuth2 VTEX ID (EN)](https://images.ctfassets.net/alneenqid6w5/3qrMFrsucwq2eWSmSAe6yY/ee05f4dafad5d0e2005293274d8f30f8/Fluxo_OAuth2_VTEX_ID__EN_.png)
 
 Keeping the illustration in mind, let's have a closer look at some of the things you'll need to know.
 
diff --git a/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
index e6972b926..afaf02dbb 100644
--- a/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -22,7 +22,7 @@ To apply different prices to products via XML, you must associate a SKU price ta
   2. Find the XML file you want to edit and click on `Modify`. If you want to create a new file, please read our article [Configuring XML](https://help.vtex.com/en/tutorial/configuring-xml--tutorials_242).
   3. Here, you must check if the fields related to SKU price (lowest product price, highest product price, original SKU price, current SKU price and current SKU price + taxes) are filled in. For the operation to work correctly, at least one of these fields must contain information.
   4. Fill in the **Price tables ** field with the name of the desired price table. Then, click on the check box corresponding to the tag in the column **Show content**. The selected price table must have fixed prices registered. Otherwise, the configuration will not be performed.
-![PT-tabela de precos](//images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
+![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
 <div class="alert alert-warning">
   <p>Once the price table is included in the XML, all price fields will be overwritten.</p>
 </div>
@@ -35,4 +35,4 @@ After finishing the XML registration and saving the changes, you can check the i
 
 Example of updated XML:
 
-![XML-exemplo](//images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
+![XML-exemplo](https://images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
diff --git a/docs/tutorials/en/creating-collections-beta.md b/docs/tutorials/en/creating-collections-beta.md
index 042ec4ae8..8f4f0bb52 100644
--- a/docs/tutorials/en/creating-collections-beta.md
+++ b/docs/tutorials/en/creating-collections-beta.md
@@ -88,23 +88,23 @@ Selecting products through the VTEX Admin can be made using the product list, se
 
 There are many filters that can be selected to reduce the number of products displayed on the list.
 
-![Collections-EN](//images.ctfassets.net/alneenqid6w5/7j4kfkpKZfrc6QwVNjrV6Z/5d19956173c19af3e823eec2b24869f3/Screenshot_2020-08-28_Collections.png)
+![Collections-EN](https://images.ctfassets.net/alneenqid6w5/7j4kfkpKZfrc6QwVNjrV6Z/5d19956173c19af3e823eec2b24869f3/Screenshot_2020-08-28_Collections.png)
 
 You can create new filters based on other criteria not covered by the predetermined filters. The images below show a few examples of these options:
 
-![Novo filtro - EN](//images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/4b679fbc6cfd2242327c9d6df77e555c/novo_filtro_-en.PNG)
+![Novo filtro - EN](https://images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/4b679fbc6cfd2242327c9d6df77e555c/novo_filtro_-en.PNG)
 
-![Filtro Colecao detalhes - EN](//images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/ce198baa55d995431c3cc77efb799920/Filtro_Colecao_detalhes_-_EN.png)
+![Filtro Colecao detalhes - EN](https://images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/ce198baa55d995431c3cc77efb799920/Filtro_Colecao_detalhes_-_EN.png)
 
 To add a product to a collection, click on the icon <i class="fas fa-plus-circle" title = "check circle"></i> related to the product, thereby saving it in the collection automatically.
 
 For more information about the item, click on the icon <i class="fas fa-external-link-alt" title = "external link"></i> to open the product page or click on the image to enlarge it.
 
-![EN-colecao-adicionar](//images.ctfassets.net/alneenqid6w5/4pb2cOOWDwe4g5ToGz0kvp/fbc71e22012ce56237470c4edfc7975e/EN-colecao-adicionar.gif)
+![EN-colecao-adicionar](https://images.ctfassets.net/alneenqid6w5/4pb2cOOWDwe4g5ToGz0kvp/fbc71e22012ce56237470c4edfc7975e/EN-colecao-adicionar.gif)
 
 If you want to add in bulk, apply one of the filters and click on the `Add All` button. It is worth noting that the product must have at least one existing SKU to be included in a collection.
 
-![EN-colecao-adicionar-todos](//images.ctfassets.net/alneenqid6w5/3Ftzj2gJy9qIskElyIE6u/f638b1ae74f9d545fe74ea8c15cec9f8/EN-colecao-adicionar-todos.png)
+![EN-colecao-adicionar-todos](https://images.ctfassets.net/alneenqid6w5/3Ftzj2gJy9qIskElyIE6u/f638b1ae74f9d545fe74ea8c15cec9f8/EN-colecao-adicionar-todos.png)
 
 <div class = "alert alert-danger" >
   <p> Do not bulk add more than 150,000 products. This may affect the indexing of the Catalog and the operation of your store.
@@ -119,7 +119,7 @@ You can also add items to a collection using a spreadsheet by following the step
   1. In your collection's dashboard, click on the `Import` button.
   2. Click on the **Include products in collection** option.
   3. Click on the `Import` button.
-  4. Click on `Download Template` to have the correct spreadsheet template as the example below: ![colecao-planilha-EN](//images.ctfassets.net/alneenqid6w5/6liweo59r1TKnt8wWyELwN/8416f5bccd00dd42b5d326ba7cafca70/colecao-planilha.png)
+  4. Click on `Download Template` to have the correct spreadsheet template as the example below: ![colecao-planilha-EN](https://images.ctfassets.net/alneenqid6w5/6liweo59r1TKnt8wWyELwN/8416f5bccd00dd42b5d326ba7cafca70/colecao-planilha.png)
   5. Fill in the spreadsheet with the Product IDs, RefIDs, or SKUs. Add a single ID on each line. Regardless of which ID you fill in, all SKUs for the selected product will be added to the collection after import.
   6. After filling out the spreadsheet, save the changes, and import the document into the VTEX Admin. You can drop the file in the indicated area or click on **Choose a file**. Files in CSV or XML format are accepted.
   7. To finish, click on `Import`.
@@ -136,11 +136,11 @@ Products can be removed either by selecting items from the __Collections__ modul
 
 To remove an item from the collection, simply click on the product's <i class="fas fa-check-circle" title="check circle"></i>.
 
-![EN-coleao-remover](//images.ctfassets.net/alneenqid6w5/58uEn8gQKd7lr6KVqz0TTq/eb982d2665fc13dccb9e2beb08bebc0b/EN-colecao-remover.gif)
+![EN-coleao-remover](https://images.ctfassets.net/alneenqid6w5/58uEn8gQKd7lr6KVqz0TTq/eb982d2665fc13dccb9e2beb08bebc0b/EN-colecao-remover.gif)
 
 If you wish to remove in bulk, apply one of the filters and click on the `Remove All` button.
 
-![EN-colecao-remover-todos](//images.ctfassets.net/alneenqid6w5/5KE4KYqKWTAT2S5kqwpiKv/28e9b2b7a12e0a51d676a6af810c194a/EN-colecao-remover-todos.png)
+![EN-colecao-remover-todos](https://images.ctfassets.net/alneenqid6w5/5KE4KYqKWTAT2S5kqwpiKv/28e9b2b7a12e0a51d676a6af810c194a/EN-colecao-remover-todos.png)
 
 You can also click on the button <i class="far fa-check-circle" title = "check in circle"></i> (**Products in this collection**) in the top bar and then click `Remove All`.
 
@@ -173,7 +173,7 @@ To change your collection's order, follow the steps below:
 
   b. Select the box of products you wish to change and click on `Move to Position`. Enter the number of the new position and click on `Move` to complete the change. These options allows you to rearrange items in bulk.
 
-![EN-mover-colecao](//images.ctfassets.net/alneenqid6w5/4YOgWuUHzotJ2MOcFkQYFr/92212011dad70b167ae2d2d7c4a0baf6/EN-mover-colecao.png)
+![EN-mover-colecao](https://images.ctfassets.net/alneenqid6w5/4YOgWuUHzotJ2MOcFkQYFr/92212011dad70b167ae2d2d7c4a0baf6/EN-mover-colecao.png)
 
 ### Export collection spreadsheet
 
diff --git a/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md b/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md
index a9aeb638e..2808723cf 100644
--- a/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md
+++ b/docs/tutorials/en/creating-custom-queries-in-master-data-v1.md
@@ -42,11 +42,11 @@ Follow the steps below to filter the form records and save a custom query.
 
 After following the instructions above, the query will appear as a display option in the form list.
 
-![queries-2-en](//images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/adb4b03eeb9c6060ac18eece60b2fff8/queries-2-en__1_.png)
+![queries-2-en](https://images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/adb4b03eeb9c6060ac18eece60b2fff8/queries-2-en__1_.png)
 
 You can also access the saved queries by clicking the __Queries__ button in the form list:
 
-![queries-en](//images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/5f6ac592a3157c4285e4f818a20f349b/queries-en__1_.png)
+![queries-en](https://images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/5f6ac592a3157c4285e4f818a20f349b/queries-en__1_.png)
 
 ## Configuring a default query
 
diff --git a/docs/tutorials/en/creating-data-entity.md b/docs/tutorials/en/creating-data-entity.md
index ecd205c6d..53d83a265 100644
--- a/docs/tutorials/en/creating-data-entity.md
+++ b/docs/tutorials/en/creating-data-entity.md
@@ -19,7 +19,7 @@ Data entity is a representation of a set of information about a given concept. E
 
 For example, imagine the system that controls a library. This system controls books than can be borrowed by customers. So, we can notice that these 3 concepts (book, customer, borrowing) are entities that include information about each one of them. Thus, “data entity” is a set of information about a given concept.
 
-![exemploBiblioteca](//images.contentful.com/alneenqid6w5/4WFfw93mlykqGCMSyAKcW2/27a0fd02aba4dd22df42a00fd506b75e/new-infographic.png)
+![exemploBiblioteca](https://images.contentful.com/alneenqid6w5/4WFfw93mlykqGCMSyAKcW2/27a0fd02aba4dd22df42a00fd506b75e/new-infographic.png)
 
 Considering these concepts, it is possible to set up several data control scenarios in the Master Data. By default, the following data entities are considered: Customer, Address, Stores etc. You may create as many data entities as you wish in order to develop a customized environment according to the needs of your store.
 
diff --git a/docs/tutorials/en/creating-form-in-master-data.md b/docs/tutorials/en/creating-form-in-master-data.md
index b375c71a6..8caae07c8 100644
--- a/docs/tutorials/en/creating-form-in-master-data.md
+++ b/docs/tutorials/en/creating-form-in-master-data.md
@@ -40,7 +40,7 @@ To create a form, follow the steps below:
 
    If the acronym of the __Shopping List__ entity is __SL__, and the name of the field is __Customer__, you must enter: `SL.Customer` to upload the customer service that is being viewed in the form.
 
-   ![relatedRecords-en](//images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/b63c13d0278c701cce402b77c567f843/image_2.png)
+   ![relatedRecords-en](https://images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/b63c13d0278c701cce402b77c567f843/image_2.png)
 
 After filling out the mandatory fields, the tabs available for configuration will be displayed. See below the fields of these tabs.
 
diff --git a/docs/tutorials/en/creating-landing-pages-per-binding.md b/docs/tutorials/en/creating-landing-pages-per-binding.md
index 2c4a3e32d..66598b267 100644
--- a/docs/tutorials/en/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/en/creating-landing-pages-per-binding.md
@@ -23,7 +23,7 @@ In the Admin, you can create customized landing pages by [binding](https://help.
 2. Select the desired binding in which the new landing page should be created using the dropdown menu on the page.
 3. Click on the `Create New` button.
 
-  ![en-landing-page-binding](//images.ctfassets.net/alneenqid6w5/5c1IxR9QguR726Urdu0du8/afe633c2ca2758a3af1191c269219aed/en-landing-page-binding.png)
+  ![en-landing-page-binding](https://images.ctfassets.net/alneenqid6w5/5c1IxR9QguR726Urdu0du8/afe633c2ca2758a3af1191c269219aed/en-landing-page-binding.png)
 
 4. In the `Page` details section, fill out the fields to define your new landing page's metadata, according to the expected values:
 
diff --git a/docs/tutorials/en/creating-landing-pages.md b/docs/tutorials/en/creating-landing-pages.md
index 2d7ecb611..f3eb5a0d8 100644
--- a/docs/tutorials/en/creating-landing-pages.md
+++ b/docs/tutorials/en/creating-landing-pages.md
@@ -28,7 +28,7 @@ In the Admin, you can create customized landing pages, such as pages for special
 
 2.Click **CREATE NEW**.
 
-![Creating Landing pages](//images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/5b59a487ca74b9d420f754ec5ab9fa18/cms-pages-en.png)
+![Creating Landing pages](https://images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/5b59a487ca74b9d420f754ec5ab9fa18/cms-pages-en.png)
 
 3.In the Page details section, fill in the fields below to define the page metadata:
 
diff --git a/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
index cf613d67d..ff81e260e 100644
--- a/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
@@ -56,7 +56,7 @@ To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.co
 
 The Visual Editor for merchandising rules in VTEX Intelligent Search allows you to perform the actions shown in the image below:
 
-![visual-merch-rules-EN-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
+![visual-merch-rules-EN-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Edit the name of the merchandising rule.</li>
diff --git a/docs/tutorials/en/creating-merchandising-rules-visual-editor.md b/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
index 1380e6d30..aa33eadd7 100644
--- a/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
+++ b/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
@@ -52,7 +52,7 @@ To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.co
 
 The Visual Editor for merchandising rules in VTEX Intelligent Search allows you to perform the actions shown in the image below:
 
-![visual-merch-rules-EN-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
+![visual-merch-rules-EN-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/2f765817f537bc8477b0d6fddfb171b8/visual-merch-rules-EN-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Edit the name of the merchandising rule.</li>
diff --git a/docs/tutorials/en/creating-price-tables.md b/docs/tutorials/en/creating-price-tables.md
index d08ff4225..771d25aa0 100644
--- a/docs/tutorials/en/creating-price-tables.md
+++ b/docs/tutorials/en/creating-price-tables.md
@@ -23,7 +23,7 @@ To create a new Price Table, follow the steps below:
 4. Choose the name of the pricing table you want to create.
 5. Click on button **Create price table**.
 
-![creating-price-tables](//images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/5fabe5c47940372d29b45d2718c34b68/criar-tabela-precos-en.gif)
+![creating-price-tables](https://images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/5fabe5c47940372d29b45d2718c34b68/criar-tabela-precos-en.gif)
 
 To find a Price Table: 
 
diff --git a/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
index 1250d1ae6..1690ae7f6 100644
--- a/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
@@ -54,9 +54,9 @@ In the configuration below, for example, only `employee` entries with the value
 
 You could also configure `employee=false`, where only `employee` entries with the value `false` in the field would receive the promotion.
 
-![Campo funcionário Master Data EN](//images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/929dce6e74118345a2c9f17a9605e572/Campo_funcion__rio_Master_Data_EN.png)
+![Campo funcionário Master Data EN](https://images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/929dce6e74118345a2c9f17a9605e572/Campo_funcion__rio_Master_Data_EN.png)
 
-![Cluster de clientes EN](//images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/653b3bf0087c0b78268a1231ebfcbf5f/Cluster_de_clientes_EN.png)
+![Cluster de clientes EN](https://images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/653b3bf0087c0b78268a1231ebfcbf5f/Cluster_de_clientes_EN.png)
 
 Given a field of type **[Varchar](https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265)**, we could configure `employee="yes"` so that only customers with the value `"yes"` in the field receive the promotion.
 
@@ -72,8 +72,8 @@ The expression `{propertyname} contains {value}` must be used when the informati
 
 For example, if you want to create a cluster with only customers whose emails contain `@test.com`, the configuration will follow the example below.
 
-![Campo Email Master Data](//images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4d8feac02a228d44de71cb2fa28e954f/Campo_Email_Master_Data.png)
+![Campo Email Master Data](https://images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4d8feac02a228d44de71cb2fa28e954f/Campo_Email_Master_Data.png)
 
-![cluster email EN](//images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/85c04dff4d5ebf184cd9bd1f82f1bdfb/cluster_email.png)
+![cluster email EN](https://images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/85c04dff4d5ebf184cd9bd1f82f1bdfb/cluster_email.png)
 
 In this case, `email contains test.com` will be `true`, for example, when the value is `john@test.com`, and `false` when the value is `john@test.org`.
diff --git a/docs/tutorials/en/creating-promotions.md b/docs/tutorials/en/creating-promotions.md
index 7e218651f..654197d75 100644
--- a/docs/tutorials/en/creating-promotions.md
+++ b/docs/tutorials/en/creating-promotions.md
@@ -86,7 +86,7 @@ A promotion is scheduled when it is created (or modified) with a valid date and
 
 These promotions can be easily identified on the main Promotions page: they have an orange stripe with the word scheduled in the upper right corner of the card, as shown below.
 
-![scheduleded](//images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/eb514999e99bff1bb64c9b21ca93fd9c/scheduled.png)
+![scheduleded](https://images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/eb514999e99bff1bb64c9b21ca93fd9c/scheduled.png)
 
 To schedule a promotion, follow the steps described in the [Scheduling promotions](https://help.vtex.com/en/tutorial/scheduling-features-for-special-events--2nd50tPWdKK4waXRZLg0JI#scheduling-promotions) section of the article [Scheduling features for special events](https://help.vtex.com/en/tutorial/scheduling-features-for-special-events--2nd50tPWdKK4waXRZLg0JI).
 
diff --git a/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md
index 2109b210c..efddca412 100644
--- a/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/en/creating-relationships-between-master-data-entities-using-admin.md
@@ -33,23 +33,23 @@ In the example below, there is an entity called `Lista de compras` (Shopping lis
 
 1. In the Master Data, click on the **Aplicações** (Applications) tab.
 2. Then click on the **Advanced settings** button.  
-![Configurações Avançadas](//images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
+![Configurações Avançadas](https://images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
 3. Select the option **Estrutura de dados** (Data structure). You will be redirected to the Dynamic Storage (DS).  
-![Estrutura de dados](//images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
+![Estrutura de dados](https://images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
 4. In the Dynamic Storage, click on the **Data Entities** tab.
 5. If you want to create a relationship in a new entity, click on **Add new** to create a new data entity. _If you want to create a relationship in an existing entity, locate it and click on the **Edit** button next to it. Go to step 7_.  
-![Adicionar nova entidade de dados](//images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
-![Editar entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
+![Adicionar nova entidade de dados](https://images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
+![Editar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
 6. Configure the new entity by filling in the fields **Acronym** and **Name**, and add the fields of your choice. In this example, the entity will receive the name `Lista de compras`, the acronym `LC` and the `compras` field of `Varchar 750` type.
 7. Add a `Relationship` type field and name it. In this example, it will be called `Cliente`.
 8. Then click on the button **Edit** (gear icon) to configure it in the relationship field. 
 9. In **Custom field type settings**, select the entity you want to refer to and the field that will be displayed in the relationship. In this example, the relationship will be established with the “Cliente” entity and shown in the “email” field.  
-![Relacionamento entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
+![Relacionamento entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
 10. Click on the **Save** button.
-![Salvar entidade de dados](//images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
+![Salvar entidade de dados](https://images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
 11. Go back to the entity list. Remember that you must publish the entity with the relationship by clicking on the **Publish** button (floppy disk icon). You may also need to update the applications for the changes to be implemented. For that, go to **Aplicações** (Applications) and click on the **Reload applications** button.  
-![Publicar entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
-![Master Data Reload applications](//images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
+![Publicar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
+![Master Data Reload applications](https://images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
 
 ## How to create a relationship between documents?
 
@@ -58,44 +58,44 @@ You can also apply relationships to specific documents of the data entity. The `
 1. To relate the documents, add the relationship field to the form of the entity that contains the reference. You can set the field as a combo box to show all the available values. For more details, read our article [Creating a field in Master Data](https://help.vtex.com/en/tutorial/how-can-i-create-a-field-in-master-data--frequentlyAskedQuestions_1829#crm).
 
 2. Select a value (in this case, the client to be related to this shopping list).
-![Selecionar relacionamento de documento Master Data](//images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
+![Selecionar relacionamento de documento Master Data](https://images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
 3. Click on **Salvar** (Save).
 
 After adding the field to the table, check out the values that were defined. 
-![Tabela de relacionamento de documentos Master Data](//images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/5658949f4c0a72a5ed7bdd9af7819896/Tabela_de_relacionamento_de_documentos_Master_Data.png)
+![Tabela de relacionamento de documentos Master Data](https://images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/5658949f4c0a72a5ed7bdd9af7819896/Tabela_de_relacionamento_de_documentos_Master_Data.png)
 
 ## How to add filters to relationship fields?
 
 Relationships are stored in the system as document IDs. So, suppose you enter the value of the relationship field as a filter in the form. In that case, the result will return only the ID values of the referred documents—instead of the values of the field selected for each document. You can see this result in the pictures below. For more information, read our article on [How to filter data in Master Data](https://help.vtex.com/en/tutorial/filtering-data-on-master-data--tutorials_778).
 
-![Selecionar filtro relacionamento](//images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
+![Selecionar filtro relacionamento](https://images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
 
-![Filtro relacionamento ID](//images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
+![Filtro relacionamento ID](https://images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
 
 If you want to see the field values instead of their IDs, you can filter using an automatic field. See the instructions below:
 
 1. In the Master Data, go to **Aplicações** (Applications) > **Advanced settings** > **Estrutura de dados** (Data structure) to access the Dynamic Storage.
 2. Access **Data Entities**.
 3. Click on the **Edit** button next to the entity that contains the relationship (in this case, `Lista de Compras`). 
-![Editar entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/01edd05338b039279672d9cfc4a49164/Editar_entidade_Lista_de_Compras.png)
+![Editar entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/01edd05338b039279672d9cfc4a49164/Editar_entidade_Lista_de_Compras.png)
 4. Select the **Automatic fields** tab.
 5. Click on **New field**.    
-![Relacionamento automatic fields](//images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
+![Relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
 6.  Fill in the **Name**, **Display Name**, and **Type** fields. In this example, they are `emailCliente`, `E-mail cliente`, and Varchar 50.
 7. Select the gear icon to adjust additional settings.   
-![Name automatic field](//images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/9aed2f322c02ab0c3991f1d28c199676/Nome_automatic_field.png)
+![Name automatic field](https://images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/9aed2f322c02ab0c3991f1d28c199676/Nome_automatic_field.png)
 8. Enter additional settings to the formula, and select the field value, as in the picture below. 
-![Configurar relacionamento automatic fields](//images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/8605aa25dbc22ba6d28674472fc80232/Configurar_relacionamento_automatic_fields.png)
+![Configurar relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/8605aa25dbc22ba6d28674472fc80232/Configurar_relacionamento_automatic_fields.png)
 9. Click on **Validate**.
 10. A new window will open and you’ll be asked to add an email address. Enter a generic email address and click **Ok**.   
-![Validar automatic field](//images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
+![Validar automatic field](https://images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
 11. Subsequently, a warning will be displayed indicating that the formula is valid, as in the image below. Then click **Ok**. 
-![Fórmula válida automatic field](//images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
+![Fórmula válida automatic field](https://images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
 12. Click on **Save**.
 
 After following the steps above, the filter will be applied to the relationship. In the entity form (`Lista de Compras`), add the new field to the filter after updating the records.
-![Selecionar filtro relacionamento valor](//images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/731c3fa19a7a8c3d9cf91a3733d86c7c/Selecionar_filtro_relacionamento_valor.png)
+![Selecionar filtro relacionamento valor](https://images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/731c3fa19a7a8c3d9cf91a3733d86c7c/Selecionar_filtro_relacionamento_valor.png)
 
 Now the filters are named with values instead of their IDs.
-![Filtro relacionamento valor](//images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/5c63307856159af60995094fa6e99f42/Filtro_relacionamento_valor.png)
+![Filtro relacionamento valor](https://images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/5c63307856159af60995094fa6e99f42/Filtro_relacionamento_valor.png)
 
diff --git a/docs/tutorials/en/creating-roles.md b/docs/tutorials/en/creating-roles.md
index c133e40f9..858583bd1 100644
--- a/docs/tutorials/en/creating-roles.md
+++ b/docs/tutorials/en/creating-roles.md
@@ -44,12 +44,12 @@ To start using a predefined role, follow the instructions below:
 
     For example, the **Call center operator** profile has a _Catalog_ product resource that allows operations to be carried out in a store on behalf of a customer and an _OMS_ resource that allows verifying an order status:
 
-    ![New role saved](//images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/a4452a13454d847c991800db970f0a7e/New_role_saved.png)
+    ![New role saved](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/a4452a13454d847c991800db970f0a7e/New_role_saved.png)
 
     Learn more about the available predefined roles and their associated resources in [Predefined roles](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy).
 4. Add admin users to the role by entering the user email address in **Add users to this role** and click `Add`.
 
-    ![Role users](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
+    ![Role users](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
 
     If the user does not exist, a new user will be created using the email as the name, i.e., the name and email will be the same.
 5. Click `Save`.
@@ -67,7 +67,7 @@ To create a custom role that meets the access needs of a group of users, follow
 
     You will see a list of all the resources available for the product:
 
-    ![Configuring product](//images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/956aa2dfc15f9e2adedd6efc90af039f/configurar-produto-en.png)
+    ![Configuring product](https://images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/956aa2dfc15f9e2adedd6efc90af039f/configurar-produto-en.png)
 
 5. Check the resources to which the role should grant access. Check the complete [License Manager resources](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) list for more information on each one.
 6. If you want to add resources from another product, click the **Configure Another Product** button at the bottom of the product and resource list and repeat steps 4 and 5.
@@ -80,7 +80,7 @@ To create a custom role that meets the access needs of a group of users, follow
   </div>
 8. Add admin users to the role by entering the user email address in **Add users to this role** and then click `Add`.
 
-    ![Role users](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
+    ![Role users](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
 
     If the user does not exist, a new user will be created using the email as the name, i.e., the name and email will be the same.
 
diff --git a/docs/tutorials/en/creating-service-for-a-sku.md b/docs/tutorials/en/creating-service-for-a-sku.md
index 306854a9c..6dc030015 100644
--- a/docs/tutorials/en/creating-service-for-a-sku.md
+++ b/docs/tutorials/en/creating-service-for-a-sku.md
@@ -79,7 +79,7 @@ To link a service to a SKU, please follow the steps below:
   <p>The size of the template file cannot exceed 4Mb (4096KB).</p>
 </div>
 8. Click on the bar next to the `Select` button, as shown below.
-  ![Anexos - EN](//images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/6d834bfa0595150d8c6a5b69c6088e23/sku-services.png)
+  ![Anexos - EN](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/6d834bfa0595150d8c6a5b69c6088e23/sku-services.png)
 9. Select the updated CSV template.
 10. Click on the button `Link service values to SKU`.
 
diff --git a/docs/tutorials/en/creating-surchargestaxes.md b/docs/tutorials/en/creating-surchargestaxes.md
index ada9e8ad5..469e3a8c3 100644
--- a/docs/tutorials/en/creating-surchargestaxes.md
+++ b/docs/tutorials/en/creating-surchargestaxes.md
@@ -58,4 +58,4 @@ The surcharge is applied in accordance with the registration done on the seller.
 
 Scheduling of a surcharge occurs when it is created with an expiration date and time, beginning after the current one. Visually, it is possible to identify these surcharges on the home page of the Promotions & Taxes module by an orange strip in the upper right-hand corner of the surcharge card with the word ‘scheduled’. See below an example of how the surcharge card looks when scheduled.
 
-![agendamento.en](//images.ctfassets.net/alneenqid6w5/6XrW3s1vW86EPSvcMufVcg/3b64aad76af6a36adc278405163fc7aa/agendamento.en.png)
+![agendamento.en](https://images.ctfassets.net/alneenqid6w5/6XrW3s1vW86EPSvcMufVcg/3b64aad76af6a36adc278405163fc7aa/agendamento.en.png)
diff --git a/docs/tutorials/en/creating-the-category-tree.md b/docs/tutorials/en/creating-the-category-tree.md
index 7714ce399..a4ffa1998 100644
--- a/docs/tutorials/en/creating-the-category-tree.md
+++ b/docs/tutorials/en/creating-the-category-tree.md
@@ -19,4 +19,4 @@ The category tree is the relation of categories that will be used in your stor
 
 [The definition of your category tree](http://help.vtex.com/tutorial/cadastrando-categoria/ "The definition of your category tree") must be made in the beginning of your project and must be well planed, considering your product catalogue and SEO.
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3004-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4](//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4 "//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3004-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4](https://assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4 "//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4")</video>
diff --git a/docs/tutorials/en/creating-trigger-in-master-data.md b/docs/tutorials/en/creating-trigger-in-master-data.md
index f297df314..fa454b318 100644
--- a/docs/tutorials/en/creating-trigger-in-master-data.md
+++ b/docs/tutorials/en/creating-trigger-in-master-data.md
@@ -44,7 +44,7 @@ Below are the main characteristics of triggers:
 
 Before [creating a trigger](#configuring-triggers), it's important to understand that configuring a trigger has four parts, which are explained below.
 
-![trigger](//images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/7c3bad97c814b7cb52393616ef58fa47/trigger-en.png)
+![trigger](https://images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/7c3bad97c814b7cb52393616ef58fa47/trigger-en.png)
 
 ### Action that fires the trigger
 
@@ -120,7 +120,7 @@ In this section, you must set the conditions that will fire the event(s) configu
 
    Select which fields and values are accepted or not for the trigger to be fired.
 
-   ![filters-en](//images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/c0d93fda52ba199ee2101c62028d1c33/filters-en.png)
+   ![filters-en](https://images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/c0d93fda52ba199ee2101c62028d1c33/filters-en.png)
 
 <div class="alert alert-info">
   <p>Master Data v1 does not allow the configuration of trigger reattempts, unlike Master Data v2.</p>
@@ -142,7 +142,7 @@ In this tab, you must configure the events to be triggered if the record that tr
 
 Sends an email to dynamic (specified in the record) or static recipients. The email content can be customized to include text, HTML, or even URL content. You can also add attachments, and the **Valid tags** field shows how to enter field values in the record.
 
-![send-email-en](//images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/ed63e14a042e2e8b9ec80cc7303b7f00/send-email-en.png)
+![send-email-en](https://images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/ed63e14a042e2e8b9ec80cc7303b7f00/send-email-en.png)
 
 #### Send an email using a VTEX Message Center template
 
@@ -158,7 +158,7 @@ Sends an HTTP request, allowing you to save the response details in Master Data.
 
 Complete the **Request information** section with the request details you want to send. In the **Response action** section, you can indicate how the response details should be saved in Master Data.
 
-![http-request-en](//images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/63d495ea6217ad26f62c5d1f26b4d299/http-request-en.png)
+![http-request-en](https://images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/63d495ea6217ad26f62c5d1f26b4d299/http-request-en.png)
 
 To configure the **Response action**, select the desired data entity and set the corresponding JSON path in the response for each field to be saved.
 
diff --git a/docs/tutorials/en/creating-your-promotions.md b/docs/tutorials/en/creating-your-promotions.md
index d4bd8a3af..e912a8eb9 100644
--- a/docs/tutorials/en/creating-your-promotions.md
+++ b/docs/tutorials/en/creating-your-promotions.md
@@ -18,5 +18,5 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 [Creating promotions](/topic/promocoes-cupons/ "Creating promotions") is not a required step to make your store live, but it&#8217;s largely used by VTEX stores, so it&#8217;s in our recommended first steps. Take the time to configure a launch promotion. 😋
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3002-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4](//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4 "//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3002-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4](https://assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4 "//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4")</video>
 
diff --git a/docs/tutorials/en/credit-card-basic-payment-flow.md b/docs/tutorials/en/credit-card-basic-payment-flow.md
index 2680ff15b..bf3128afc 100644
--- a/docs/tutorials/en/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/en/credit-card-basic-payment-flow.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 This article aims to explain how the basic flow of a __credit card__ payment works:
 
-![EN Credit Card Flow](//images.ctfassets.net/alneenqid6w5/5uiKlzNdkvbaN0u8pYltiv/6fadc7c928fd8974e8398c410b6716c7/EN_Credit_Card_Flow.svg)
+![EN Credit Card Flow](https://images.ctfassets.net/alneenqid6w5/5uiKlzNdkvbaN0u8pYltiv/6fadc7c928fd8974e8398c410b6716c7/EN_Credit_Card_Flow.svg)
 
 1. On the Checkout screen, the customer chooses the credit card __Payment Method__ to pay for their purchase.
 2. Payment information is passed to the __Payment Gateway__. The [gateway](/en/tutorial/what-is-a-payment-gateway) is the player responsible for ensuring that this payment is successful.
diff --git a/docs/tutorials/en/credit-control-overview.md b/docs/tutorials/en/credit-control-overview.md
index ea17524cd..426881b0f 100644
--- a/docs/tutorials/en/credit-control-overview.md
+++ b/docs/tutorials/en/credit-control-overview.md
@@ -35,7 +35,7 @@ That's why we created Credit Control - so that it's done within the VTEX system,
 
 ## How it works
 
-![Credit Control basic flow](//images.contentful.com/alneenqid6w5/35jUk6EVksKUQi8EaU6caO/2f8f3ddb5ead2d2c9379fc340fb070f9/credit-control-flow_en.gif)
+![Credit Control basic flow](https://images.contentful.com/alneenqid6w5/35jUk6EVksKUQi8EaU6caO/2f8f3ddb5ead2d2c9379fc340fb070f9/credit-control-flow_en.gif)
 *Basic flow of how Credit Control works on VTEX stores.*
 
 Because it was developed in VTEX, Credit Control is fully integrated with the existing SmartCheckout system through its connector - which means that your customers' shopping experience remains the same. Credit Control's admin can be accessed through the main menu of the VTEX modules panel.
diff --git a/docs/tutorials/en/criar-um-produto-beta.md b/docs/tutorials/en/criar-um-produto-beta.md
index 0d862642e..eba98f530 100644
--- a/docs/tutorials/en/criar-um-produto-beta.md
+++ b/docs/tutorials/en/criar-um-produto-beta.md
@@ -43,7 +43,7 @@ After that, the product will be activated and available in your store.
 In this tab, complete the fields described below to create the product.
 
 ### General information
-![image9](//images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
+![image9](https://images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
 - **Name:** Enter the product name. Use simple words, avoiding other languages or complex writing. This field is crucial for SEO and must respect the 150-character limit. Required field. **Example**: Ultralight Running Shoes.
 - **Substitute words:** Enter synonyms of terms related to the product name, separated by commas (`,`). This field is essential for a more comprehensive search and must respect the 8,000-character limit. **Example**: for the product `Ultralight Running Shoes`, synonyms could include `Light Running Shoes,Ultra Running Shoes`. If your store uses VTEX Intelligent Search, do not complete this field and read the[Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) article.
 
@@ -60,7 +60,7 @@ In this step, you must write a description with the main information about the p
 Example: "The Ultralight Running Shoes are the perfect choice for athletes looking for high performance and comfort. Their innovative design and high-tech materials provide the utmost lightness and resistance during physical activity."
 
 The text editor for the description is a _rich text_ editor, which means you can use different formatting tools in its toolbar, as shown in the image below.
-![image10](//images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
+![image10](https://images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
 
 See the tools available in the toolbar:
 
@@ -93,7 +93,7 @@ See the tools available in the toolbar:
 - **Source code:** Displays the source code of the HTML description. You can edit the description directly from the source code if you want. To go back to the previous view, click the source button again.
 
 ### SEO 
-![image11](//images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
+![image11](https://images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
 
 - **Product URL:** Enter the URL to access the product page in the store. You cannot use spaces or special characters in this field. If the URL consists of more than one word, you must separate them with a hyphen (-). Required field. **Example**: ultralight-running-shoes.
 
@@ -108,7 +108,7 @@ See the tools available in the toolbar:
 - **Tax code:** Enter the fiscal identification number of the product.
 
 ### Visibility 
-![image4](//images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)
+![image4](https://images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)
 
 - **Display on website:** Enable or disable the product visibility in your store. For example, if the product is a gift that cannot be purchased, you should disable this option.
 
@@ -124,7 +124,7 @@ Depending on the product category you create, you may have to complete some fiel
 If you have created any required product fields, the product will only be activated once this specification has been completed.
 
 Under **Attributes**, the [specification groups](https://help.vtex.com/en/tutorial/criando-grupo-de-especificacoes-em-uma-categoria--tutorials_246) will be displayed with the specifications you entered. In the image below, the specification group is **Characteristics**, and the specifications are **Video** and **See More**.
-![image3](//images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
+![image3](https://images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
 
 ## SKUs
 
@@ -136,7 +136,7 @@ In this tab, you will add the [SKUs](https://help.vtex.com/en/tracks/catalog-101
 This is where the previously created [specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) for the SKUs will be displayed. If you have created any required SKU fields, the SKU will only be activated once this specification has been completed.
 
 ### Basic Information
-![image2](//images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
+![image2](https://images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
 - **Name:** The SKU name, which will be displayed in the store. Required field.
 - **Reference code:** Code that the store will use internally to identify the SKU. Required field if the **EAN/UPC** is empty.
 - **EAN/UPC**: Field that must have the barcode information. Required field if the **Reference code** field is empty.
@@ -151,8 +151,8 @@ SKUs must have at least one image to be active.</div>
 
 To add an image to your SKU, follow the steps below:
 
-1. Click the `+` button.![image8](//images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
-2. Add the link to your image in the 🔗 field. You can add more than one image to your SKU. To do this, click `+ Add Image` and add the new link. ![image6](//images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
+1. Click the `+` button.![image8](https://images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
+2. Add the link to your image in the 🔗 field. You can add more than one image to your SKU. To do this, click `+ Add Image` and add the new link. ![image6](https://images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
 3. Click `Save`.
 
 <div class="alert alert-info">The first image added will be the main image of the SKU and will be displayed in the store and search results.
@@ -163,7 +163,7 @@ You can edit an image's metadata by clicking the &lt;i class="fas fa-ellipsis-v"
 You can also delete an image by clicking the <i class="fas fa-ellipsis-v"></i> button and selecting <i class="fas fa-trash-alt"></i>`Remove`
 
 ### Weight and Dimensions
-![image1](//images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
+![image1](https://images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
 #### Shipping weight and dimensions
 
 - **Package weight:** Weight of the empty package in kilos. Required field.
@@ -187,7 +187,7 @@ You can also delete an image by clicking the <i class="fas fa-ellipsis-v"></i> b
 - **Unit multiplier:** Numerical unit that multiplies the selected quantity of the product when it is added to the cart. If the multiplier is 5, the product will be added in multiple quantities of 5, such as 5, 10, 15, 20, and so on.
 
 ### Advanced Settings 
-![image5](//images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
+![image5](https://images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
 
 - **Activate bundle:** Determines if SKUs within a bundle can only be sold together. You can make the SKU part of a bundle &lt;i class="fas fa-toggle-on">&lt;/i> or not &lt;i class="fas fa-toggle-off">&lt;/i>.
 
diff --git a/docs/tutorials/en/customer-credit-overview.md b/docs/tutorials/en/customer-credit-overview.md
index 886d32614..b192e8da5 100644
--- a/docs/tutorials/en/customer-credit-overview.md
+++ b/docs/tutorials/en/customer-credit-overview.md
@@ -40,7 +40,7 @@ When installed, Customer Credit appears as a payment option at Checkout only for
 
 See below the basic flow of how Customer Credit works in VTEX stores:
 
-![GIF_CC_EN](//images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/28fd6b4db8e48a99115fd02e00273b54/GIF_CC_EN.gif)
+![GIF_CC_EN](https://images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/28fd6b4db8e48a99115fd02e00273b54/GIF_CC_EN.gif)
 
 ## Customer Credit definitions
 
diff --git a/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md b/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md
index 3e48e6229..db0ef9fe3 100644
--- a/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md
+++ b/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md
@@ -15,7 +15,7 @@ legacySlug: customizing-the-checkout-confirmation-pages
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-![Página de confirmação de pedido (Order Placed)](//images.contentful.com/alneenqid6w5/n7VvdVmseGQyGwCEQAIiW/90bd066111747fe05d722e6fad172d14/cconf-hml1.png) 
+![Página de confirmação de pedido (Order Placed)](https://images.contentful.com/alneenqid6w5/n7VvdVmseGQyGwCEQAIiW/90bd066111747fe05d722e6fad172d14/cconf-hml1.png) 
 
 The new My Orders section comes with a new Order Placed page, which now integrates **Checkout Confirmation**, feature responsible for confirmation pages.
 
@@ -25,7 +25,7 @@ As well as the Order Placed, another page is the Order Confirmation, wich shows
 
 As in previous versions, the Order Placed (as well as the Order Changed) page accepts **HTML templates**:
 
-![Página de confirmação de pedido com imports de HTML](//images.contentful.com/alneenqid6w5/2HXuJJE5yMCUIaeCMoOOa8/1e947bf46ec9202214867219ba36677a/cconf-html-2.png)
+![Página de confirmação de pedido com imports de HTML](https://images.contentful.com/alneenqid6w5/2HXuJJE5yMCUIaeCMoOOa8/1e947bf46ec9202214867219ba36677a/cconf-html-2.png)
 
 To add your code to these templates, all you have to do is access the Portal module and, in the **Code** tab, edit the following files:
 
@@ -36,7 +36,7 @@ To add your code to these templates, all you have to do is access the Portal mod
 
 It's important to notice that the customization with templates is the same for Order Placed and Order Confirmation.
 
-![Página do Portal v2 com arquivos de template corretos destacados](//images.contentful.com/alneenqid6w5/5jGk1WbMqkkggyAog66iAs/c1162190ef431b8c96462fb34355aa98/cconf-html3.png)
+![Página do Portal v2 com arquivos de template corretos destacados](https://images.contentful.com/alneenqid6w5/5jGk1WbMqkkggyAog66iAs/c1162190ef431b8c96462fb34355aa98/cconf-html3.png)
 
 ### Customizing styles
 
@@ -44,7 +44,7 @@ It's important to notice that the customization with templates is the same for O
 
 You can also edit the Checkout Confirmation interface via CSS classes. Your styles should be added in a `<style>` tag in one of the HTML templates loaded on the page.
 
-![Página de OrderPlaced do Checkout Confirmation com classes de customização marcadas](//images.contentful.com/alneenqid6w5/OgLXDC0eyaOc4iKGmSkgS/a698e4da05726f33659d0ea88d0b1278/cconf-doc-2.png)
+![Página de OrderPlaced do Checkout Confirmation com classes de customização marcadas](https://images.contentful.com/alneenqid6w5/OgLXDC0eyaOc4iKGmSkgS/a698e4da05726f33659d0ea88d0b1278/cconf-doc-2.png)
 
 To customize the Checkout Confirmation styles, use the following classes:
 
diff --git a/docs/tutorials/en/customizing-the-my-orders-section.md b/docs/tutorials/en/customizing-the-my-orders-section.md
index fc757f218..51db7d144 100644
--- a/docs/tutorials/en/customizing-the-my-orders-section.md
+++ b/docs/tutorials/en/customizing-the-my-orders-section.md
@@ -34,7 +34,7 @@ If you already have a customization file for the previous version of the My Orde
 
 ### Order list
 
-![Order list with customization classes highlighted on top of the elements](//images.contentful.com/alneenqid6w5/1P5JMzt3jGIAKIOmC4ka4e/d7511d7273f4a957acc6f7e1322a81e6/my-orders-doc-1.png) 
+![Order list with customization classes highlighted on top of the elements](https://images.contentful.com/alneenqid6w5/1P5JMzt3jGIAKIOmC4ka4e/d7511d7273f4a957acc6f7e1322a81e6/my-orders-doc-1.png) 
 
 CSS:
 ```
@@ -69,7 +69,7 @@ CSS:
 
 ### Order detail
 
-![Order details page with customization classes highlighted on top of the elements](//images.contentful.com/alneenqid6w5/5szHUT7x9CAOseYGkcEskS/e8a846072846d20648c65a1cd00059c4/my-orders-doc-2.png)
+![Order details page with customization classes highlighted on top of the elements](https://images.contentful.com/alneenqid6w5/5szHUT7x9CAOseYGkcEskS/e8a846072846d20648c65a1cd00059c4/my-orders-doc-2.png)
 
 CSS:
 ```
@@ -84,7 +84,7 @@ CSS:
 
 ### Order cancellation
 
-![Order cancellation page with customization classes highlighted on top of the elements](//images.contentful.com/alneenqid6w5/5mUVzR5n7aMScoSs4auem4/05bfeea119bb4fc42afe448c66c9674f/my-orders-doc-3.png)
+![Order cancellation page with customization classes highlighted on top of the elements](https://images.contentful.com/alneenqid6w5/5mUVzR5n7aMScoSs4auem4/05bfeea119bb4fc42afe448c66c9674f/my-orders-doc-3.png)
 
 CSS:
 ```
diff --git a/docs/tutorials/en/customizing-your-stores-typography.md b/docs/tutorials/en/customizing-your-stores-typography.md
index e3d52537b..7b717cf84 100644
--- a/docs/tutorials/en/customizing-your-stores-typography.md
+++ b/docs/tutorials/en/customizing-your-stores-typography.md
@@ -27,7 +27,7 @@ In the Admin, you have the flexibility to customize your store’s typography to
 1. In the VTEX Admin, access **Storefront > Styles**.
 2. Select the kebab menu icon (three dots).
 
-![Styles - More Options](//images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/3bc40e3e3a439475b4f0998a3af56854/styles-two-en.png)
+![Styles - More Options](https://images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/3bc40e3e3a439475b4f0998a3af56854/styles-two-en.png)
 
 3. Click **Edit > Typography > Font Family**.
 
@@ -51,7 +51,7 @@ Refer to the section [Type tokens](#type-tokens) for more information about them
 2. Select the kebab menu icon (three dots).
 3. Click on **Edit > Typography > Type Tokens**.
 
-![Styles - Type tokens EN](//images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/dbb378f7b8e11fa1217276626dd6f008/styles-three-en.gif)
+![Styles - Type tokens EN](https://images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/dbb378f7b8e11fa1217276626dd6f008/styles-three-en.gif)
 
 4. Choose the type token you want to customize, for example, **Heading 1**, and click it.
 
diff --git a/docs/tutorials/en/data-entity.md b/docs/tutorials/en/data-entity.md
index 696e815d1..5ae081492 100644
--- a/docs/tutorials/en/data-entity.md
+++ b/docs/tutorials/en/data-entity.md
@@ -19,7 +19,7 @@ A data entity is a representation of a set of information about a given concept.
 
 For example, imagine a system that controls a library. This system controls books that customers can borrow. Thus, we can notice that these three concepts (book, customer, borrowing) are entities that contain information about each one. 
 
-![data-entity-en](//images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/1b24a20995e073f17e492e8d80ae4031/data-entity-en.png)
+![data-entity-en](https://images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/1b24a20995e073f17e492e8d80ae4031/data-entity-en.png)
 
 With these concepts in mind, you can set up several data control scenarios in Master Data. By default, the following data entities are considered: customer, address, stores, etc. You can create as many data entities as you want to develop a customized environment tailored to your store's needs.
 
diff --git a/docs/tutorials/en/data-subject-rights.md b/docs/tutorials/en/data-subject-rights.md
index 3190c4672..8f2cdf9b7 100644
--- a/docs/tutorials/en/data-subject-rights.md
+++ b/docs/tutorials/en/data-subject-rights.md
@@ -50,7 +50,7 @@ To export data from the Master Data v1 through the Admin dashboard, follow these
 1. In the VTEX Admin, go to **Store Settings** > **Storefront** > **Master Data.**
 2. Click the **Applications** tab.
 3. Click the view icon (on the right) of the desired data entity.
-![Master Data view button](//images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/601df52aab81d94c5ad3afc75103fde3/visualizar_bot__o_master_data_EN.png)
+![Master Data view button](https://images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/601df52aab81d94c5ad3afc75103fde3/visualizar_bot__o_master_data_EN.png)
 4. Use the [Master Data v1 filter](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) to filter only the data for the desired user. Use the `email` or `user ID` as the filter field.
 5. Click `Export XLS`.
 6. Select the `Select all fields` option.
diff --git a/docs/tutorials/en/deactivating-store-skus-and-products.md b/docs/tutorials/en/deactivating-store-skus-and-products.md
index 3719bea88..c409140b6 100644
--- a/docs/tutorials/en/deactivating-store-skus-and-products.md
+++ b/docs/tutorials/en/deactivating-store-skus-and-products.md
@@ -25,4 +25,4 @@ To deactivate the SKU of a product, proceed as follows:
 4. Click on the SKU which you want to deactivate.
 5. Deselect the option __Activate the SKU if possible__.
 
-![deactivateSKU](//images.contentful.com/alneenqid6w5/4On7ZXJXPyAUqqy2GaGEuu/04ebceeab81b47272be45f16679c7597/inativarSKU.png)
+![deactivateSKU](https://images.contentful.com/alneenqid6w5/4On7ZXJXPyAUqqy2GaGEuu/04ebceeab81b47272be45f16679c7597/inativarSKU.png)
diff --git a/docs/tutorials/en/declining-order-cancelation.md b/docs/tutorials/en/declining-order-cancelation.md
index 620bbd3d6..6486ccbbf 100644
--- a/docs/tutorials/en/declining-order-cancelation.md
+++ b/docs/tutorials/en/declining-order-cancelation.md
@@ -35,7 +35,7 @@ Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8J
 
 The following image shows the flow of declining an order’s cancellation request outside the cancellation window:
 
-![cancel_api_improvements_help_center_EN](//images.ctfassets.net/alneenqid6w5/6qU0tP4gQxa2qh6JLjleoK/abdfe44471ce04c695bc0b1c50463afb/cancel_api_improvements_help_center_EN.png)
+![cancel_api_improvements_help_center_EN](https://images.ctfassets.net/alneenqid6w5/6qU0tP4gQxa2qh6JLjleoK/abdfe44471ce04c695bc0b1c50463afb/cancel_api_improvements_help_center_EN.png)
 
 The description of each step is the following:
 
@@ -71,11 +71,11 @@ To decline an order cancellation request via the VTEX Admin, follow the steps be
 2. Select the desired order to access the [Order Details page](https://help.vtex.com/en/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl).
 3. At the top of the page, click `Decline`.
 
-  ![deny_cancel_request_EN](//images.ctfassets.net/alneenqid6w5/3TpCmA2PEdtVb5ru8Ed2va/253a91677769d1b3617f6a8714fc3603/deny_cancel_request_EN.png)
+  ![deny_cancel_request_EN](https://images.ctfassets.net/alneenqid6w5/3TpCmA2PEdtVb5ru8Ed2va/253a91677769d1b3617f6a8714fc3603/deny_cancel_request_EN.png)
 
 4. Complete the **Cancellation Request** box with the reason why the cancel order request has been declined.
 
-  ![deny_cancel_request_reason_EN](//images.ctfassets.net/alneenqid6w5/5UUueX5kuj7OkBCHVhe0oL/022f068cefdd1e6588560d5bcba94ea3/deny_cancel_request_reason_EN.png)
+  ![deny_cancel_request_reason_EN](https://images.ctfassets.net/alneenqid6w5/5UUueX5kuj7OkBCHVhe0oL/022f068cefdd1e6588560d5bcba94ea3/deny_cancel_request_reason_EN.png)
 
   <div class="alert alert-warning">
 Keep in mind that the message written in this field can be displayed to the customer via <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, or sent by the marketplace.
diff --git a/docs/tutorials/en/defining-product-prices.md b/docs/tutorials/en/defining-product-prices.md
index e5995ce9c..55d93ee21 100644
--- a/docs/tutorials/en/defining-product-prices.md
+++ b/docs/tutorials/en/defining-product-prices.md
@@ -18,5 +18,5 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 With the products already registered, now it's time to define their sales price. They can be limited by UTMs or even have start and end dates.
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3026-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4](//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4 "//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3026-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4](https://assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4 "//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4")</video>
 
diff --git a/docs/tutorials/en/defining-window-displays.md b/docs/tutorials/en/defining-window-displays.md
index c94be10bb..cd9ea4d9b 100644
--- a/docs/tutorials/en/defining-window-displays.md
+++ b/docs/tutorials/en/defining-window-displays.md
@@ -27,25 +27,25 @@ After defining this, link the collection to the window display in **Storefront >
 
 In the example below, we will define a window display on the home page, and to do so the following layout has to be changed:
 
-![cms_layout_home ](//images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
+![cms_layout_home ](https://images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
 
 In the selected layout, add the control for the window display where you want to display the collection by clicking on **Add Object**
 After selecting the type of control you want, set its name and click **Adicionar** (Add)
 
 __Do not forget to click on the "Save Settings" button so that you can later edit the created control.__
 
-![ed](//images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
+![ed](https://images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
 
 ### Editing created control
 
 To edit your controls, click on the **pencil symbol**, as shown in the example image below:
 
-![banner_edit_cms](//images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
+![banner_edit_cms](https://images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
 
 When you editing the control you must add its contents by clicking **Add content**, which represent each set of items to be displayed.
 
-![cadastro_conteudo_cms ](//images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
-![cadastro_conteudo_cms 2](//images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
+![cadastro_conteudo_cms ](https://images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
+![cadastro_conteudo_cms 2](https://images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
 
 - **"Adicionar arquivo" (add file):** to select the collection that will be displayed in this content.
 - **Partner / Campaign / Source:** defines the display of this content if the visitor has a corresponding UTM in its source URL.
@@ -61,7 +61,7 @@ Check **Active Content** box and click on **Add content list**. Do not forget to
 
 If it is necessary to update the created content after saving it, just click on the second pencil symbol as shown below:
 
-![edit_content_cms](//images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
+![edit_content_cms](https://images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
 
 Click **Update Content List** after all changes were made and clicking on **Save Settings** afterwards.
 
diff --git a/docs/tutorials/en/deleting-a-category.md b/docs/tutorials/en/deleting-a-category.md
index 3f983c1dc..648c7d194 100644
--- a/docs/tutorials/en/deleting-a-category.md
+++ b/docs/tutorials/en/deleting-a-category.md
@@ -26,7 +26,7 @@ If you do not want to display a specific category to your customers, you can dea
 3. Select the category you want to deactivate.
 4. Click on the `Actions` button.
 5. Click on `Edit`.
-6. Uncheck the box that says __Active | Category is active on site__, as illustrated in the image below: ![img inativarcategoria EN](//images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/b1056e64bedc8a7f495dde49b87b735e/img_inativarcategoria_EN.png)
+6. Uncheck the box that says __Active | Category is active on site__, as illustrated in the image below: ![img inativarcategoria EN](https://images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/b1056e64bedc8a7f495dde49b87b735e/img_inativarcategoria_EN.png)
 7. Click on `Save`.
 
 ## Deleting all categories
diff --git a/docs/tutorials/en/deleting-a-folder-from-cms.md b/docs/tutorials/en/deleting-a-folder-from-cms.md
index 5fa96d1b0..c78d2f31e 100644
--- a/docs/tutorials/en/deleting-a-folder-from-cms.md
+++ b/docs/tutorials/en/deleting-a-folder-from-cms.md
@@ -26,7 +26,7 @@ To delete a CMS folder, follow the steps below:
 3. Click the website that contains the folder you want to delete and then click the root folder (/).
 4. In the line corresponding to the folder you want to delete, click __delete__.
 
-![erroDeletarPasta2](//images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
+![erroDeletarPasta2](https://images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
 
 <div class = "alert alert-danger">
 Some folders are required. Your store will not function properly without them. Others are important, so it's not a good idea to delete them.<br><br>Understand this theme deeper by reading the article <a href="http://help.vtex.com/en/tutorial/cms-folder-structure">CMS folder structure</a>.
@@ -34,6 +34,6 @@ Some folders are required. Your store will not function properly without them. O
 
 If a folder contains other folders, you must delete all internal folders before deleting the more external one. Otherwise, the system will return the error "Object reference not set to an instance of an object", as in the image below.
 
-![erroDeletarPasta](//images.contentful.com/alneenqid6w5/6g2MBbZJUQUQM2YQQ88MQE/9159df93c82fc1e89199aaf1922a5044/erroDeletarPasta.png)
+![erroDeletarPasta](https://images.contentful.com/alneenqid6w5/6g2MBbZJUQUQM2YQQ88MQE/9159df93c82fc1e89199aaf1922a5044/erroDeletarPasta.png)
 
 For example, if you want to delete folder A, and within it are folders A1 and A2, first delete folders A1 and A2, and then delete folder A.
diff --git a/docs/tutorials/en/detaching-skus-by-specification.md b/docs/tutorials/en/detaching-skus-by-specification.md
index ab84cc537..3df959678 100644
--- a/docs/tutorials/en/detaching-skus-by-specification.md
+++ b/docs/tutorials/en/detaching-skus-by-specification.md
@@ -25,7 +25,7 @@ This tool is useful for clothing stores as it allows you to display the products
 
 See the following example of detaching SKUs by color. In the image below, the featured sandals are available in two different colors in the search results:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.</p></div>
diff --git a/docs/tutorials/en/disable-cloudflare-proxy.md b/docs/tutorials/en/disable-cloudflare-proxy.md
index c20d5618b..2211ede9b 100644
--- a/docs/tutorials/en/disable-cloudflare-proxy.md
+++ b/docs/tutorials/en/disable-cloudflare-proxy.md
@@ -23,7 +23,7 @@ To disable the CloudFlare proxy (and therefore disable CloudFlare's CDN and WAF
 
 If the proxy is enabled, the icon will be orange with the text **Proxied**. If it is disabled, the icon will be gray with the text **DNS Only**.
 
-![Cloudflare proxy configuration](//images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/80ac72636596307b289d75cf6ca6c2fd/DNS_Management.png)
+![Cloudflare proxy configuration](https://images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/80ac72636596307b289d75cf6ca6c2fd/DNS_Management.png)
 
 Please note that it may take a while to see the result of disabling the CloudFlare proxy, as it requires the cache to be refreshed.
 
diff --git a/docs/tutorials/en/displaying-the-store-in-another-language.md b/docs/tutorials/en/displaying-the-store-in-another-language.md
index fac270534..d2f8dc56c 100644
--- a/docs/tutorials/en/displaying-the-store-in-another-language.md
+++ b/docs/tutorials/en/displaying-the-store-in-another-language.md
@@ -17,7 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 In order to display your website in another language, a [new sales policy](/en/tutorial/configuring-a-marketplace-sales-policy/) must be created and assigned to the intended language through the __Culture Info__ field. 
 
-![exibição-loja-idioma-diferente en](//images.ctfassets.net/alneenqid6w5/38da6HQyM0Sq2KaeoQUemC/0a14f342af87aaf865431e95a2ebad36/exibi____o-loja-outra-l__ngua_en.png)
+![exibição-loja-idioma-diferente en](https://images.ctfassets.net/alneenqid6w5/38da6HQyM0Sq2KaeoQUemC/0a14f342af87aaf865431e95a2ebad36/exibi____o-loja-outra-l__ngua_en.png)
 
 With the sales policy already created, you will need to adjust the front-end of the store to enable changing the language and, consequently, the trade policies. 
 To do so, you must define that for each language the URL must include the parameter `?sc=salespolicyid`, changing the __salespolicyid__ value for the sales policy Id that was set up and assigned to the desired language. 
diff --git a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
index ebe8f97ac..04319be01 100644
--- a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -31,7 +31,7 @@ Currently, VTEX stores can only offer ad space on stores using <a href="https://
 
 On the initial screen of the [VTEX Ad Network for stores app](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#merchants), you can monitor the results of ads in your store.
 
-![vtex_ad_network_admin_EN](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/434685bba26278166e6b5192a7b198d1/vtex_ad_network_admin.png)
+![vtex_ad_network_admin_EN](https://images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/434685bba26278166e6b5192a7b198d1/vtex_ad_network_admin.png)
 
 At the top of the page, you'll find aggregated data:
 
@@ -62,7 +62,7 @@ You can also use the filters available at the top of the table:
 
 In the table on the initial screen of the [VTEX Ad Network for stores app](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#merchants), you can click the campaign row to see more details:
 
-![vtex_ad_network_details_EN](//images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/b81424e85fc704593e7f5bb86bf55409/vtex_ad_network_details.png)
+![vtex_ad_network_details_EN](https://images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/b81424e85fc704593e7f5bb86bf55409/vtex_ad_network_details.png)
 
 - **Views/Clicks:** Ad views and clicks.
 - **CTR:** Click-through rate, calculated by dividing the number of clicks by the number of views.
diff --git a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
index cd88db022..633e2a838 100644
--- a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
@@ -39,7 +39,7 @@ Manual relevance is configured by distributing the weights on the **Relevance Ru
 
 1. In the VTEX Admin, go to **Storefront > Intelligent Search >** **Relevance Rules** or type **Relevance Rules** in the search bar at the top of the page.
 2. Select the **Manual Relevance** option.
-![relevancia-manual-en](//images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/c66c5e883e20fd0711400e63d9a18423/image.png)
+![relevancia-manual-en](https://images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/c66c5e883e20fd0711400e63d9a18423/image.png)
 3. Click `Save`.
 
 To configure manual relevance, see the [Relevance](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS) article.
@@ -57,7 +57,7 @@ To enable dynamic relevance, follow these steps:
 1. In the VTEX Admin, go to **Storefront > Intelligent Search > Relevance Rules** or type **Relevance Rules** in the search bar at the top of the page.
 2. Read the information about dynamic relevance and click `Next`.
 3. Select the **Dynamic Relevance** option.
-![relevancia-dinamica-en](//images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/75b719ed30b77a99b0f9c9a5d7a62371/image.png)
+![relevancia-dinamica-en](https://images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/75b719ed30b77a99b0f9c9a5d7a62371/image.png)
 4. Click `Save`.
 5. Wait for the loading bar to reach 100%. This process may take a few hours. You will receive an email when the loading is complete.
 6. Click `Enable`.
diff --git a/docs/tutorials/en/enable-checkout-v6.md b/docs/tutorials/en/enable-checkout-v6.md
index f59086000..acd779806 100644
--- a/docs/tutorials/en/enable-checkout-v6.md
+++ b/docs/tutorials/en/enable-checkout-v6.md
@@ -28,7 +28,7 @@ To update your store's checkout to the latest version (Checkout v6), you must en
 5. Click `Save`.
 6. [Access your store in beta/test environment](/tutorial/access-beta-environment-through-myvtex-com-domain--3BHM289568gcSwk2O80Asu) and implement the necessary style adjustments. Checkout v6 has new _CSS_ classes that you need to be mindful of when performing style customizations.
 
-![Checkoutv6_box](//images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/f185469ae22029d00f5d19f3b6a8cf1b/CheckoutV6_box_EN.png)
+![Checkoutv6_box](https://images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/f185469ae22029d00f5d19f3b6a8cf1b/CheckoutV6_box_EN.png)
 
 ## Activate Checkout v6 in Production Environment
 
@@ -42,7 +42,7 @@ After the necessary adjustments are completed, you can activate Checkout v6 in t
 
 After this step, Checkout v6 would be installed in your store.
 
-![checkoutv6_box_2](//images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/f38745c904dfcb233ec0b09d3c01b2a2/CheckoutV6_box2_EN.png)
+![checkoutv6_box_2](https://images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/f38745c904dfcb233ec0b09d3c01b2a2/CheckoutV6_box2_EN.png)
 
 ## How to ascertain whether Checkout v6 was properly installed?
 
diff --git a/docs/tutorials/en/enabling-2-factor-authentication-login.md b/docs/tutorials/en/enabling-2-factor-authentication-login.md
index 0afd79c66..8c7395f56 100644
--- a/docs/tutorials/en/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/en/enabling-2-factor-authentication-login.md
@@ -34,7 +34,7 @@ There are two authentication options:
 - Using a key that's generated by an authentication app.
 - Using a key sent by __SMS__.
 
-![2FA - Select - EN](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
+![2FA - Select - EN](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
 
 <div class="alert alert-danger">
 We strongly recommend that you <strong>choose the app authentication option</strong>, since, with SMS authentication, you will depend on your network provider. By using an app, you can generate an access key whenever you need it.
@@ -49,13 +49,13 @@ If you chose 2FA through SMS, and the SMS code doesn't appear, your network oper
 To use the key generated by the authentication app:
 
 1. Download the __Google Authenticator__ app ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)).
-  ![2FA - App Download - EN](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
+  ![2FA - App Download - EN](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/25e3209b0c0bb098f828284e3c7cffb0/2FA_-_App_Download_-_EN.png)
 2. Use the application to scan the QR Code with your cell phone's camera.
-   ![mfa qr code](//images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/ec1e00707e20e7f6ab295123c71f9c0d/mfa_qr_code_correction_en.jpg)
+   ![mfa qr code](https://images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/ec1e00707e20e7f6ab295123c71f9c0d/mfa_qr_code_correction_en.jpg)
 3. Your VTEX account will be added to the application, and a 6-digit code will be displayed. Enter the code to complete your login.
 
   *The app code is updated periodically. No need to memorize it; access the app whenever you need an access code.*
-  ![2FA - App Insert Code - EN](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
+  ![2FA - App Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
 
 <div class="alert alert-info">
 If you log in with your email and password on the same computer, the access key will be requested <strong> every three days</strong>. When this happens, check the code in the application.
@@ -67,11 +67,11 @@ To use a key sent by SMS:
 
 1. Enter your cell phone number to receive the code by SMS - do not forget to enter the country and area code.
 
-  ![2FA - SMS Insert Phone - EN](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
+  ![2FA - SMS Insert Phone - EN](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/62abcd5ec500ed253b31d999eb4cb398/2FA_-_SMS_Insert_Phone_-_EN.png)
 
 2. You will receive a text message from VTEX on the given cell phone. Enter the 6-digit key to finish your login.
 
-   ![2FA - SMS Insert Code - EN](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
+   ![2FA - SMS Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
 
 <div class="alert alert-warning">
 We cannot guarantee that your network operator will be able to deliver the access key whenever necessary. If the text message does not arrive, try resending the code or <a href="#habilitate-o-2fa-per-application" >enable 2FA through the application</a>.
@@ -87,10 +87,10 @@ To change the verification settings, follow these two steps:
 
 1. Access your user settings by clicking on the circle with your initials on the top-right corner of the Admin.
 
-  ![2FA - User Initials - EN](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
+  ![2FA - User Initials - EN](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/08247b82c616d2bb40f2707838327857/2FA_-_User_Initials_-_EN.png)
 
 2. Click on **2-step verification** to see the settings.
 
-  ![2FA - My User - EN](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
+  ![2FA - My User - EN](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/223cd4da346f380558a103dfeb2f8c73/2FA_-_My_User_-_EN.png)
 
 3. You can then change the settings by following similar steps, as shown in the sections above, to enable 2FA through [SMS](#enable-o-2fa-by-sms) and [application](#enable-o-2fa-by-application). 
diff --git a/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
index 90782d150..ab16d4fb4 100644
--- a/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
@@ -35,7 +35,7 @@ In this tutorial, you will learn how to add the 3DS2 authentication to the Reds
 4. Scroll down the screen and select __Yes__ for the __3DS Enabled__ option.
 5. Click on __Save__.
 
-![RedsysV2 EN](//images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/d1671b87629fbc5d59dd8c0298f9a90f/Redsys_3DS2_-_EN.png)
+![RedsysV2 EN](https://images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/d1671b87629fbc5d59dd8c0298f9a90f/Redsys_3DS2_-_EN.png)
 
 It’s done! Now the solution is enabled for Redsýs’s transactions with credit cards.
 
diff --git a/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
index 0ef0f67ad..dbedf9b2f 100644
--- a/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -77,7 +77,7 @@ You will need to select a sales associate from the store where you want to test
 1. With a [sales associate selected](https://help.vtex.com/en/tutorial/vendedores-instore-beta--4rzit1pzp28km4HSDEdrEC), open Sales App and log in.
 2. Search for an item that exists in the franchise account warehouse. The item should display the available quantity that corresponds to the seller inventory.
 
-![instore-pdp-en](//images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/064cb3f0b499da4533cacdbea0fee4eb/image.png)
+![instore-pdp-en](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/064cb3f0b499da4533cacdbea0fee4eb/image.png)
 
 <div class="alert alert-info">
 <p>If you enabled Infinite inventory, the item quantity will display as a number greater than one million, which can't be changed when a sale is completed.</p>
@@ -92,9 +92,9 @@ You can also enable On Hands to ignore stock quantity and force item availabilit
 2. Click the gear <i class="fas fa-cog"></i> button to edit.
 3. Select the **Code** tab.
 4. In the side tab, select the `checkout-instore-custom-js` file.
-![instore-custom-js-en](//images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/45e6d1e73997a0ff4a4872fdc502a17c/image.png)
+![instore-custom-js-en](https://images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/45e6d1e73997a0ff4a4872fdc502a17c/image.png)
 5. In the `window.INSTORE_CONFIG` key, add the `sellWithoutStockInHands: true` flag.
-![sellWithoutStockInHands-en](//images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/642bf1e6d79d00ce46275ac1924d03c0/image.png)
+![sellWithoutStockInHands-en](https://images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/642bf1e6d79d00ce46275ac1924d03c0/image.png)
 6. Click <i class="fas fa-save"></i> `Save`.
 
 ## Enabling mixed cart sales (optional)
diff --git a/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md b/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md
index 5baec9caf..05909ca23 100644
--- a/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md
+++ b/docs/tutorials/en/enabling-pwa-push-notifications-in-your-store.md
@@ -16,7 +16,7 @@ subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
 All VTEX IO stores natively have a Progressive Web App (PWA) at their disposal. A PWA is a web app used to natively promote beneficial features to users, such as offline functionalities or a home screen icon.
-![pwa-noticeen](//images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/f47f6817eb995c32b186be1ebd320300/Screenshot_162.png)
+![pwa-noticeen](https://images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/f47f6817eb995c32b186be1ebd320300/Screenshot_162.png)
 The PWA can be made available for installation in three distinct moments of users’ browsing experience: during their first visit to your store's website, when adding the first item to the shopping cart, or when completing their first purchase.
 To configure the prompt in your store, follow the steps below.
 
diff --git a/docs/tutorials/en/entering-tax-receipts-in-the-order.md b/docs/tutorials/en/entering-tax-receipts-in-the-order.md
index a4aa3847e..a0c630e73 100644
--- a/docs/tutorials/en/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/en/entering-tax-receipts-in-the-order.md
@@ -19,7 +19,7 @@ Entering the tax receipt in the order is a mandatory step so that the status bec
 
 To do this manually using the **Orders management**,  click on the `Invoice package` button, as shown in the image below.
 
-![faturar-pedido-ex en](//images.ctfassets.net/alneenqid6w5/3xGII9E1x6Iogai8qYyWYw/d50b5a145891ac1766882dabdf35a371/ex_1_en.png)
+![faturar-pedido-ex en](https://images.ctfassets.net/alneenqid6w5/3xGII9E1x6Iogai8qYyWYw/d50b5a145891ac1766882dabdf35a371/ex_1_en.png)
 
 Once the tax receipt is entered with the total amount of the order, the status changes to **Invoiced**.
 
diff --git a/docs/tutorials/en/excluding-a-product-from-the-store.md b/docs/tutorials/en/excluding-a-product-from-the-store.md
index 34817d513..38dcb9dea 100644
--- a/docs/tutorials/en/excluding-a-product-from-the-store.md
+++ b/docs/tutorials/en/excluding-a-product-from-the-store.md
@@ -27,6 +27,6 @@ However, if the product in question has some link to another area of the system
 
 In this case, the following error message will appear if you try to delete it:
 
-![errorDelete](//images.contentful.com/alneenqid6w5/19vbt8GlfOK0IMEMEo86Gu/75d44c69a5d553d485daa668d1ab19bc/erroExcluir.png)
+![errorDelete](https://images.contentful.com/alneenqid6w5/19vbt8GlfOK0IMEMEo86Gu/75d44c69a5d553d485daa668d1ab19bc/erroExcluir.png)
 
 The solution is to deactivate the product. See how to do this in the article [Deactivating store SKUs and products](/en/tutorial/deactivating-store-skus-and-products).
diff --git a/docs/tutorials/en/explained-search.md b/docs/tutorials/en/explained-search.md
index dfc93dfb1..17362550a 100644
--- a/docs/tutorials/en/explained-search.md
+++ b/docs/tutorials/en/explained-search.md
@@ -27,5 +27,5 @@ Follow the steps below to access it:
 1. In the VTEX Admin, go to __Storefront__, or type __Storefront__ in the search bar at the top of the page.
 2. Under **Intelligent Search**, click __Explained Search__. 
 
-![Explained Search](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
+![Explained Search](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/826ba767da8acaa0cad6990bfdf36ca8/explained_search_em.png)
 
diff --git a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
index f497bcf59..411c1a26e 100644
--- a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
@@ -28,14 +28,14 @@ In this article, we explain how to export and import spreadsheets with product a
 1. In the VTEX Admin, go to **Catalog**, or type **Catalog** in the search bar at the top of the page.
 2. Click **Import and export**.
 3. Click the **Product Specifications** or the **SKU Specifications** tab, according to your need.
-    ![skuexport1.en](//images.ctfassets.net/alneenqid6w5/2bM5OviaFXKxXxM8ggXEr3/8f45b5a59425898d0a66697480526899/skuexport1.en.png)
+    ![skuexport1.en](https://images.ctfassets.net/alneenqid6w5/2bM5OviaFXKxXxM8ggXEr3/8f45b5a59425898d0a66697480526899/skuexport1.en.png)
 4. Right-click on the desired category.
     You cannot export specifications from all categories at once. You must choose only one category whose specifications you want to export. 
 5. Click on `Export...`.
     A green rectangle will appear on the screen.
 6. Click `Click here to download the file` to export the spreadsheet.
 
-![skuexport2.en](//images.ctfassets.net/alneenqid6w5/6oBhxWWjktsofR8XGRzl3E/87e1859f2f3ece16f3c0e1c527a392ee/skuexport2.en.png)
+![skuexport2.en](https://images.ctfassets.net/alneenqid6w5/6oBhxWWjktsofR8XGRzl3E/87e1859f2f3ece16f3c0e1c527a392ee/skuexport2.en.png)
 
 <div class = "alert alert-info">
   <p>The exported spreadsheet will be available in your email for one week. If you exceed this period, follow the export step-by-step again to generate a new spreadsheet.</p>
@@ -59,7 +59,7 @@ Follow the steps below to import the spreadsheet:
 2. Click **Select** to select the file with the completed spreadsheet on your computer.
 3. Click `Import`.
 
-![skuexport3.en](//images.ctfassets.net/alneenqid6w5/3xrInPyr70kdXCGgVfj4q1/8b4ff4d98df714f62d97d765edee8600/skuexport3.en.png)
+![skuexport3.en](https://images.ctfassets.net/alneenqid6w5/3xrInPyr70kdXCGgVfj4q1/8b4ff4d98df714f62d97d765edee8600/skuexport3.en.png)
 
 ## Learn more
 - [Product and SKU Specifications](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
diff --git a/docs/tutorials/en/facebook-faq.md b/docs/tutorials/en/facebook-faq.md
index 268c20bbe..02f8dbfc7 100644
--- a/docs/tutorials/en/facebook-faq.md
+++ b/docs/tutorials/en/facebook-faq.md
@@ -36,7 +36,7 @@ The first step in this scenario is to investigate whether the SKU in fact does n
 
 If the SKU does have a price, check its status, as the error may also be related to its active/inactive status. The best way to do this is by performing a checkout simulation:
 
-![face faq01](//images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
+![face faq01](https://images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
 
 In this simulation, it is important to analyze the following fields:
 
diff --git a/docs/tutorials/en/facilitating-b2b-store-operation.md b/docs/tutorials/en/facilitating-b2b-store-operation.md
index 15273e385..9a898ec9c 100644
--- a/docs/tutorials/en/facilitating-b2b-store-operation.md
+++ b/docs/tutorials/en/facilitating-b2b-store-operation.md
@@ -91,7 +91,7 @@ All VTEX stores have the [My account](https://help.vtex.com/en/tutorial/como-fun
 
 This tool allows you to monitor the order status in the after-sales flow and carry out operations such as: “Order again”, which allows placing the same order again.  
 
-![Order again](//images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
+![Order again](https://images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
 
 For more details on “My Account,” check out the tutorial on [how to configure this feature](https://help.vtex.com/en/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1 "").
 
diff --git a/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
index be207fb35..0f4ac127f 100644
--- a/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -17,7 +17,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 For a better understanding of what each fixed price spreadsheet field means, read the full description below.
 
-![tabela.preço.fixo](//images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
+![tabela.preço.fixo](https://images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
 
 - **SKU ID:** the ID of the SKU to which you want to add the fixed price.
 - **Trade policy:** the name or ID of the trade policy to which the fixed price will be applied.
diff --git a/docs/tutorials/en/filtering-all-orders.md b/docs/tutorials/en/filtering-all-orders.md
index d6f3c742d..f7d06cda3 100644
--- a/docs/tutorials/en/filtering-all-orders.md
+++ b/docs/tutorials/en/filtering-all-orders.md
@@ -21,7 +21,7 @@ You can only access information from orders created in the last two years, and t
 
 In the **Orders** module, the **All Orders** page allows you to access your store's orders, search and filter them, as shown in the image below:
 
-![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 This article explains how to use these resources, and it is divided into:
 
@@ -63,7 +63,7 @@ Searching on All orders returns all orders related to the criteria used, regardl
 
 Enter the desired term in the search bar to search on All orders. This will make <i class="fas fa-toggle-on"></i> `Remove date limit` option visible. Then, activate it to search.
 
-![search_bar_without_time_limit_EN](//images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c861b2b825068d861850bce56660aa30/search_bar_without_time_limit_EN.png)
+![search_bar_without_time_limit_EN](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c861b2b825068d861850bce56660aa30/search_bar_without_time_limit_EN.png)
 
 <div class="alert alert-danger">
 The search on All orders cannot be combined with other filters. So, once you remove the date limit from the search, any active filters become inactive. If the search term is removed or the <i class="fas fa-toggle-off"></i> <b>Remove date limit</b> is disabled, the previously configured filters become active again.
@@ -81,7 +81,7 @@ Searching by associated filters allows you to combine different filters, which a
 
 On the **Orders > All Orders** page, there is `Filters` option, as shown in the image below: 
 
-![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 When you click `Filters`, a modal is displayed with the following options:
 
@@ -197,7 +197,7 @@ Click `Filters` to use these filters and select **Other**. You can find the opti
 
 On the **Orders > All Orders** page, there is the `Filter by Status` <i class="fas fa-angle-down"></i> option, as shown in the image below:
 
-![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 When clicking `Filter by Status` <i class="fas fa-angle-down"></i>, your store's [order status](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196) options are displayed. For example, if among all your orders, there are no canceled ones, this option will not be visible. 
 
@@ -209,7 +209,7 @@ For more status filter options, go to the section <a href="https://help.vtex.com
 
 On the **Orders > All Orders** page, there is the option `Created: Today` <i class="fas fa-angle-down"></i>, as shown in the image below:
 
-![search_bar_EN](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
+![search_bar_EN](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/c5d9141fa1eb3389ff779b8f169d4d59/search_bar_EN.png)
 
 This filter has the **Today** date enabled by default, but by clicking it, the following options are displayed:
 
diff --git a/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
index e2cdcf9ef..358166f32 100644
--- a/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -21,7 +21,7 @@ Note that Marketplace Network is a tool that promotes interaction between potent
 
 ## Finding Sellers and Marketplaces
 
-![Marketplace network tour EN](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
+![Marketplace network tour EN](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/146b86b33573496be15b712459570277/Marketplace_network_tour_EN.gif)
 To see the list of available marketplaces and sellers, go to *Marketplace > Marketplace Network > Find Sellers / Find Marketplaces*. On both pages, you can search by keyword and filter the list for more exact results, as well as contact potential partners.
 
 ## Contact
@@ -43,7 +43,7 @@ The potential business partner will receive an email with the information you en
 </div>
 
 ## Store Profile
-![Network profile EN](//images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/17a2b46b39a8fc853755fc91e974b904/Marketplace_store_profile_EN.gif)
+![Network profile EN](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/17a2b46b39a8fc853755fc91e974b904/Marketplace_store_profile_EN.gif)
 
 1. In the *Marketplace* section of your store, click __Marketplace Network__.      
 2. Click the __Store Profile__ page.      
diff --git a/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
index 28f0cef96..7f34eef22 100644
--- a/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
@@ -26,7 +26,7 @@ From February 1st, 2023, the new interface will be the default for all VTEX stor
 
 You can see the sections and fields correspondence between the old version of the **Order Details** page and the new version in the image below:
 
-![board_comparativo_interface_pedido_v2_en](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
+![board_comparativo_interface_pedido_v2_en](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/c0bd90681544108bd26da14f7091fc1d/board_comparativo_interface_pedido_v2_en.png)
 
 ## What happened to the six-month search filter?
 
@@ -38,17 +38,17 @@ The search in All Orders cannot be combined with other filters. So, once you rem
 
 Enter the desired term in the search bar to search all orders. This will make the <i class="fas fa-toggle-off"></i> `Remove date limit` option visible. Then, activate it to search.
 
-![busca_sem_limite_data_all_en](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
+![busca_sem_limite_data_all_en](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/38b0d6578851aa2dedf8ef6914aff921/busca_sem_limite_data_all_en.png)
 
 ## How to view the order flow diagram?
 
 By default, in the new interface, a timeline with the **Order status** events is displayed, as in the image below:
 
-![timeline_pedido_en](//images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/4ed7055d4dd820fcb5d2ff9d70e7c3c4/timeline_pedido_en.png)
+![timeline_pedido_en](https://images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/4ed7055d4dd820fcb5d2ff9d70e7c3c4/timeline_pedido_en.png)
 
 If you want to see the **Order diagram** as in the old interface, click `View diagram` and a modal like the one in the image below will display: 
 
-![diagrama_pedido_en](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
+![diagrama_pedido_en](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/cd9d746e2ac2104e5657ec55c1229bb0/diagrama_pedido_en.png)
 
 ## How do I invoice an order?
 
@@ -56,7 +56,7 @@ In the **Items to invoice** section of the new interface, you can access all inv
 
 * **Submit invoice referencing items: **This option is exclusive to the new interface. It allows you to issue the invoice for all or specific items identified by SKU, inventory, and price. The following image shows an example:
 
-![faturar_referenciar_pedidos_final_en](//images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/bf24faab5137854a28d9c2e7dd972c54/faturar_referenciar_pedidos_final_en.png)
+![faturar_referenciar_pedidos_final_en](https://images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/bf24faab5137854a28d9c2e7dd972c54/faturar_referenciar_pedidos_final_en.png)
 
 * **Submit single invoice:** This option corresponds to the old _Submit invoice_ and allows you to invoice the full or partial order amount. The page layout is different, but the fields remain the same.
 
@@ -75,6 +75,6 @@ In the new interface, in the **Order history** section, there is a timeline with
 
 To resend an email to the client, click the sent email event or the arrow icon <i class="fas fa-angle-right"></i> to see the event details, which will display as in the following image:
 
-![enviar_email_en](//images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/b5b4d755b4b1cab066217b2ce58d6218/enviar_email_en.png)
+![enviar_email_en](https://images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/b5b4d755b4b1cab066217b2ce58d6218/enviar_email_en.png)
 
 Click the `Resend Email` button, and it will be immediately sent to the customer, and the following confirmation message should be displayed: _Email was successfully resent to the customer_. 
diff --git a/docs/tutorials/en/fulfillment-logistics-vtex.md b/docs/tutorials/en/fulfillment-logistics-vtex.md
index 371db3f12..e6a94b2b0 100644
--- a/docs/tutorials/en/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/en/fulfillment-logistics-vtex.md
@@ -48,7 +48,7 @@ Once the order is placed, the [reservation of the products is authorized](https:
 Please note that the shipping process depends on the configuration made on the platform. Here, we present the scenarios for each type of shipping (delivery and pickup), but there are other possible flows in the shipping process. For example, when the customer chooses pickup and the selected pickup point is the warehouse, there is no need to transport the packages.
 </div>
 
-![Envio EN](//images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/2cf59529b64fd641f61b1afdb807d136/Envio_EN.svg)
+![Envio EN](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/2cf59529b64fd641f61b1afdb807d136/Envio_EN.svg)
 
 ## Configuring the logistics process
 
diff --git a/docs/tutorials/en/general-configurations-on-the-oms.md b/docs/tutorials/en/general-configurations-on-the-oms.md
index 813d06bd6..ef9caa24c 100644
--- a/docs/tutorials/en/general-configurations-on-the-oms.md
+++ b/docs/tutorials/en/general-configurations-on-the-oms.md
@@ -19,7 +19,7 @@ It is possible to execute configurations directly related to the conditions of t
 
 In the VTEX Admin, go to **Store Settings > Orders > Settings**, or type *Orders* in the search bar at the top of the page and select *Store Settings / Orders*.
 
-![configuracoes_pedidos_en](//images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/5f485e4f43fa2df4305a1f4ad9b7dd40/configuracoes_pedidos_en.png)
+![configuracoes_pedidos_en](https://images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/5f485e4f43fa2df4305a1f4ad9b7dd40/configuracoes_pedidos_en.png)
 
 ## Cart
 
diff --git a/docs/tutorials/en/generating-a-har-file.md b/docs/tutorials/en/generating-a-har-file.md
index c3eeaadc1..ac1483932 100644
--- a/docs/tutorials/en/generating-a-har-file.md
+++ b/docs/tutorials/en/generating-a-har-file.md
@@ -35,11 +35,11 @@ Using Google Chrome, follow the steps below to generate the HAR file.
 
 1. Navigate to the URL where the problem is occurring.
 2. Right-click anywhere on the screen and then click __Inspect__.
-3. Dev Tools will open, so click the __Network__ tab.![HARfile2](//images.contentful.com/alneenqid6w5/7vSYRmkjduq6iCaiGgyIo/fd3f3eb23fa57582f8c8f5cd1ac725b5/HARfile2.png)
-4. The recording button should be red, which indicates it's enabled. If it's not, click it.![HARfile3](//images.contentful.com/alneenqid6w5/6YnW3ebd1mq2kQsm8uKG2q/97000a534abfabc66931d27ff9cd28b8/HARfile3.png)
-5. Check the __Preserve log__ flag.![HARfile5](//images.contentful.com/alneenqid6w5/xQAIiEuHIsaoSCUkSsOEE/e6dc32f580a2f50a5789ae39babfb540/HARfile5.png)
+3. Dev Tools will open, so click the __Network__ tab.![HARfile2](https://images.contentful.com/alneenqid6w5/7vSYRmkjduq6iCaiGgyIo/fd3f3eb23fa57582f8c8f5cd1ac725b5/HARfile2.png)
+4. The recording button should be red, which indicates it's enabled. If it's not, click it.![HARfile3](https://images.contentful.com/alneenqid6w5/6YnW3ebd1mq2kQsm8uKG2q/97000a534abfabc66931d27ff9cd28b8/HARfile3.png)
+5. Check the __Preserve log__ flag.![HARfile5](https://images.contentful.com/alneenqid6w5/xQAIiEuHIsaoSCUkSsOEE/e6dc32f580a2f50a5789ae39babfb540/HARfile5.png)
 6. Reload the page and repeat the navigation in which the problem occurs.
-7. Right-click anywhere within the Network area, and then click __Save as HAR with content__.![HARfile4](//images.contentful.com/alneenqid6w5/hR0VTzzNFmyQc4A4KS02G/b1f15e2131e21b80f5f2c97023cd0a5b/HARfile4.png)
+7. Right-click anywhere within the Network area, and then click __Save as HAR with content__.![HARfile4](https://images.contentful.com/alneenqid6w5/hR0VTzzNFmyQc4A4KS02G/b1f15e2131e21b80f5f2c97023cd0a5b/HARfile4.png)
 
 A file with HAR extension, whose name is the address of the page, will be generated.
 
diff --git a/docs/tutorials/en/geolocation-at-checkout.md b/docs/tutorials/en/geolocation-at-checkout.md
index 874eb1ed0..d96ced230 100644
--- a/docs/tutorials/en/geolocation-at-checkout.md
+++ b/docs/tutorials/en/geolocation-at-checkout.md
@@ -42,7 +42,7 @@ Once you have an API Key, proceed as follows:
 1. In the VTEX Admin, go to __Store Settings > Shipping > Geolocation Shipping__, or type __Geolocation Shipping__ in the search bar at the top of the page.
 2. Enter the API Key in the field indicated and click on __Register Key__.
 
-![Geolocalizacao 1 EN](//images.ctfassets.net/alneenqid6w5/6pPXB9VKz6aQIA8YUWyyKk/ae4f7acd4ed20feac7edf6d27960c902/Geolocalizacao_1_EN.png)
+![Geolocalizacao 1 EN](https://images.ctfassets.net/alneenqid6w5/6pPXB9VKz6aQIA8YUWyyKk/ae4f7acd4ed20feac7edf6d27960c902/Geolocalizacao_1_EN.png)
 
 <div class="alert alert-info">
 In some countries, Google Maps does not provide high quality mapping. Therefore it is possible that some addresses will be written wrongly, or Google may indicate an incorrect address. In these cases, you must correct the address on the map itself.
@@ -61,7 +61,7 @@ Once you've created the polygon and entered your ID in the shipping worksheet, y
 3. In the blue options menu located at the top of the page, click on __Checkout__.
 4. In the __Google Maps API Key__ field insert the API Key given in the logistics step.
 
-![Google map keys](//images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/a0449abd0a356e5afa7cbb87a7101fc5/google_maps_api_key_en.PNG)
+![Google map keys](https://images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/a0449abd0a356e5afa7cbb87a7101fc5/google_maps_api_key_en.PNG)
 
 Once the API Key has been included in the Checkout configuration, the geolocation will be visible in your store checkout.
 
diff --git a/docs/tutorials/en/google-pay-beta.md b/docs/tutorials/en/google-pay-beta.md
index 85ce94aaa..d6a2d738f 100644
--- a/docs/tutorials/en/google-pay-beta.md
+++ b/docs/tutorials/en/google-pay-beta.md
@@ -38,7 +38,7 @@ To enable Google Pay, follow the steps below.
 <p>The issuing banks supported by the Google Pay extension are the ones configured in the payment conditions.</p>
 </div>
 
-![google pay - EN](//images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/c1848f1deba2af0d837f96f21eae86a5/image.png)
+![google pay - EN](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/c1848f1deba2af0d837f96f21eae86a5/image.png)
 
 Google Pay will then be available in your VTEX store's checkout as a new payment method. It may take around 10 minutes to be implemented.
 
diff --git a/docs/tutorials/en/google-search-console-tracking-sitemap.md b/docs/tutorials/en/google-search-console-tracking-sitemap.md
index 0bda05148..e3ab2184d 100644
--- a/docs/tutorials/en/google-search-console-tracking-sitemap.md
+++ b/docs/tutorials/en/google-search-console-tracking-sitemap.md
@@ -34,11 +34,11 @@ Follow the steps below to register your Sitemap:
 Go to your store’s Search Console panel: 
 [https://search.google.com/search-console/sitemaps?resource_id=sc-domain%YOURDOMAIN.com&hl=en**]
 
-![Sitemaps](//images.ctfassets.net/alneenqid6w5/5VQWkkJc0TvsouCQ1Pts4e/646f489829a2854caad27ac326de0e2e/Screen_Shot_2019-08-08_at_15.25.23.png_h_250)
+![Sitemaps](https://images.ctfassets.net/alneenqid6w5/5VQWkkJc0TvsouCQ1Pts4e/646f489829a2854caad27ac326de0e2e/Screen_Shot_2019-08-08_at_15.25.23.png_h_250)
 
 Add your new sitemap and click on submit. The Search Console will access the XML and verify it.
  
-After successfully adding the sitemap to Search Console, the tool will show you a list of all the URLs:![Sitemap URL List](//images.ctfassets.net/alneenqid6w5/6CHMG0wWwSoEmGJSrYhxua/79d8edd09363539cd5cf196e2e35d61e/Screen_Shot_2019-08-08_at_15.46.59.png_h_250)
+After successfully adding the sitemap to Search Console, the tool will show you a list of all the URLs:![Sitemap URL List](https://images.ctfassets.net/alneenqid6w5/6CHMG0wWwSoEmGJSrYhxua/79d8edd09363539cd5cf196e2e35d61e/Screen_Shot_2019-08-08_at_15.46.59.png_h_250)
 
 
 
diff --git a/docs/tutorials/en/headless-cms-overview.md b/docs/tutorials/en/headless-cms-overview.md
index 58521d55a..92a10ced1 100644
--- a/docs/tutorials/en/headless-cms-overview.md
+++ b/docs/tutorials/en/headless-cms-overview.md
@@ -35,7 +35,7 @@ The headless CMS allows you to:
 
 [Projects](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) is a feature in Headless CMS that allows you to create and manage multiple frontend projects like mobile apps, websites, and email marketing from a single control panel.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
 
 For more information, refer to [Managing Projects](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM). 
 
diff --git a/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
index 66af3431c..734a76e40 100644
--- a/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
@@ -26,7 +26,7 @@ The VTEX platform is prepared to support domain changes without adverse impacts.
 ### 1. Create new HOST entries in the License Manager
 In the License Manager, under “Contas,” enter the new domain as the HOST of your store. At this moment, the DNS of the new domain should not be pointed to VTEX yet. 
 See below an image illustrating and giving examples of the inclusion of new HOSTs to be applied:
-![Change Domain](//images.ctfassets.net/alneenqid6w5/4FfqogdPy0UokEe2G2CICk/d044f0e997870688f9fec8163c508f73/626-en.png)
+![Change Domain](https://images.ctfassets.net/alneenqid6w5/4FfqogdPy0UokEe2G2CICk/d044f0e997870688f9fec8163c508f73/626-en.png)
 
 ### 2. Check the settings of the new Portal
 This step is crucial for the Checkout to continue operating after the change. You must check whether the Sites set up are connected to some inexisting Account Name created in License Manager. [Learn more about the portal settings here](/en/faq/configure-template-in-the-smartcheckout).
diff --git a/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
index db5265430..861716ecc 100644
--- a/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
@@ -44,7 +44,7 @@ Follow the step-by-step below:
 
 <div class="alert alert-info">More information about <strong>General Settings</strong> and <strong>Search and Filter Configurations</strong> can be found in our article on <a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Creating a data entity</a>, subsection <strong>How to set up</strong>.</div>
 
-![criar campo master data ds](//images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
+![criar campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
 You will then return to the main Data Entity page. To complete the process, you need to publish the field. Locate the entity line in which the field was added and click on the disk icon.
 
@@ -69,6 +69,6 @@ To achieve this, follow the instructions below:
 7. Drag the field from the list entitled "available fields" to the columns entitled "column Fields 1" or "column Fields 2";
 8. In the lower part of the screen, click on the blue Save button.
 
-![criar campo master data CRM](//images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
+![criar campo master data CRM](https://images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
 
 Done! The fields will be displayed on the form.
diff --git a/docs/tutorials/en/how-can-i-create-callcenter-user.md b/docs/tutorials/en/how-can-i-create-callcenter-user.md
index 32b63dce8..2e31c31a1 100644
--- a/docs/tutorials/en/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/en/how-can-i-create-callcenter-user.md
@@ -41,7 +41,7 @@ To create a user with the telesales role, follow the steps below.
 
 7. Click on **Save**.
 
-![Animated GIF showing how to create call center operator ](//images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/c41d49badebeb869d2e9d4cef73c74b0/Adicionar_perfil_EN.gif)
+![Animated GIF showing how to create call center operator ](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/c41d49badebeb869d2e9d4cef73c74b0/Adicionar_perfil_EN.gif)
 
 <div class="alert alert-warning">
 When creating a  <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">role</a>, avoid including call center <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">resources</a> with other resources. Otherwise, the role might not work as expected.
diff --git a/docs/tutorials/en/how-can-my-customer-login-to-my-store.md b/docs/tutorials/en/how-can-my-customer-login-to-my-store.md
index 352cbb63d..192e1af72 100644
--- a/docs/tutorials/en/how-can-my-customer-login-to-my-store.md
+++ b/docs/tutorials/en/how-can-my-customer-login-to-my-store.md
@@ -28,7 +28,7 @@ The purpose of this article is to show you how your customers should log in to a
 
 When clicking on a link to authenticate, the client will see the login screen.
 
-![vtex-id-pt](//images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/cfeadc0b744855b307b02718f7d4493f/vtex-id-en.png)
+![vtex-id-pt](https://images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/cfeadc0b744855b307b02718f7d4493f/vtex-id-en.png)
 
 There are three standard ways to log in to a VTEX store:
 
@@ -42,9 +42,9 @@ This login type __sends an access token to the user’s email__ so he or she can
 
 For the client to sign in using this method, they must follow the steps below:
 1. On the login screen, the user should click on __Receive quick access key by email__;
-2. On the next screen, the user must fill out their email and click on the button __Confirm__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-3. __An access token will be sent to the email they entered in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should to check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-4. Return to the login screen and __enter the access key__ received in the previous step and click __Enter__ ![fill-access-token-pt](//images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
+2. On the next screen, the user must fill out their email and click on the button __Confirm__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+3. __An access token will be sent to the email they entered in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should to check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+4. Return to the login screen and __enter the access key__ received in the previous step and click __Enter__ ![fill-access-token-pt](https://images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
 
 ### Login with email and password
 
@@ -54,11 +54,11 @@ This type of login __ requests email and password__ so that the client can authe
 
 - If the client needs to __register a password__, they must follow the steps below:
 1. On the login screen, the user must click on __Login with email and password__;
-2. On the next screen, the user should click on __Don’t you have a password? Register now!__ ![register-password-pt](//images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
-3. The user must fill in their email and click on the button __Confirm__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-4. On the next screen, the user must enter their new password in the fields __New password__ and __Confirm new password__ and then click on the button __Create new password__  ![register-new-password-pt](//images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
-5. __An access token will be sent to the email informed in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-6. Return to the login screen and __enter the access key__ received in the previous step and then click __Change Password__ ![change-password-pt](//images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)
+2. On the next screen, the user should click on __Don’t you have a password? Register now!__ ![register-password-pt](https://images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
+3. The user must fill in their email and click on the button __Confirm__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+4. On the next screen, the user must enter their new password in the fields __New password__ and __Confirm new password__ and then click on the button __Create new password__  ![register-new-password-pt](https://images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
+5. __An access token will be sent to the email informed in the previous step__. If the customer does not receive the email, ask them to verify that they’ve typed the email correctly. In addition, the customer should check the junk mail to ensure that the access key has not fallen into the spam filter. The token has 6 numbers. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+6. Return to the login screen and __enter the access key__ received in the previous step and then click __Change Password__ ![change-password-pt](https://images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)
 
 ### Social media login
 
diff --git a/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index 788dc3916..f358a847f 100644
--- a/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -32,16 +32,16 @@ You can change the protocol in all folders at once by using our API, documented
 2. Access **Sites and channels**.
 3. Access the desired website.
 4. Open the root folder of the website.
-![CMS instrução - EN](//images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
+![CMS instrução - EN](https://images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
 5. The screen that was opened displays all the folders that are on the first level of the site. For each pertinent folder, click **Edit** - for home, consider the top button;
-![edit cms - EN](//images.ctfassets.net/alneenqid6w5/6ijmcqCYCIOmi2oeSSEaiy/c6f229d2a4727d5fbeb368e6b8282b2f/edit_CMS_EN.png)
+![edit cms - EN](https://images.ctfassets.net/alneenqid6w5/6ijmcqCYCIOmi2oeSSEaiy/c6f229d2a4727d5fbeb368e6b8282b2f/edit_CMS_EN.png)
 6. In the checkbox **Protocol**, select the option **HTTPS**;
-![cms-protocol-https EN](//images.ctfassets.net/alneenqid6w5/6QfX3kETJeqI2Iu0wKECys/2296b1dff11262501fbc20b2ff70afe2/cms_protocol_HTTPS_EN.png)
+![cms-protocol-https EN](https://images.ctfassets.net/alneenqid6w5/6QfX3kETJeqI2Iu0wKECys/2296b1dff11262501fbc20b2ff70afe2/cms_protocol_HTTPS_EN.png)
 7. Click in **Save Folder**.
 
 Attention to folders that have subfolders, such as Departamento, Categoria, Produto, and other folders, including also those created for store customization. 
 
 In the following example, the folder **Orders**, contained in **Account**, which also must be edited: 
-![cms-subcategoria-edit EN](//images.ctfassets.net/alneenqid6w5/6ugtIHxBSgMMeMgCeA040c/51521187a54845179835e410d76294d4/subcategoria_edit_EN.png)
+![cms-subcategoria-edit EN](https://images.ctfassets.net/alneenqid6w5/6ugtIHxBSgMMeMgCeA040c/51521187a54845179835e410d76294d4/subcategoria_edit_EN.png)
 
 After a cache of up to 10 minutes the changes will take effect.
diff --git a/docs/tutorials/en/how-do-you-calculate-payments-in-installments-with-compound-interest.md b/docs/tutorials/en/how-do-you-calculate-payments-in-installments-with-compound-interest.md
index b2040cccc..24b15b6eb 100644
--- a/docs/tutorials/en/how-do-you-calculate-payments-in-installments-with-compound-interest.md
+++ b/docs/tutorials/en/how-do-you-calculate-payments-in-installments-with-compound-interest.md
@@ -26,7 +26,7 @@ Collection at the beginning of the period is calculated as follows:
 1. i = Interest rate
 2. n = Number of installments
 3. PV = Present Value (total amount of the purchase without interest)
-4. Installment = ![juros-inicio-periodo](//images.contentful.com/alneenqid6w5/3JkoK4GMLYAWIwUcAC8W2G/59d18849c4ee9e59ff37cb09ac661c89/juros-inicio-periodo.png)
+4. Installment = ![juros-inicio-periodo](https://images.contentful.com/alneenqid6w5/3JkoK4GMLYAWIwUcAC8W2G/59d18849c4ee9e59ff37cb09ac661c89/juros-inicio-periodo.png)
 
 ## End of the period
 
@@ -35,7 +35,7 @@ Collection at the end of the period is calculated as follows:
 1. i = Interest rate
 2. n = Number of installments
 3. PV = Present Value (total amount of the purchase without interest)
-4. Cash Flow Multiplier =![cash-flow](//images.contentful.com/alneenqid6w5/2xvT7uQ8ccGoCUw8ouOEoK/936546d7e46be7b9ce984c531daf5e8b/cash-flow.png)
+4. Cash Flow Multiplier =![cash-flow](https://images.contentful.com/alneenqid6w5/2xvT7uQ8ccGoCUw8ouOEoK/936546d7e46be7b9ce984c531daf5e8b/cash-flow.png)
 5. Installment = `PV x Cash Flow Multiplier`
 
 ## Examples
@@ -45,11 +45,11 @@ Collection at the end of the period is calculated as follows:
 1. i = 1%
 2. n = 12
 3. PV = 1000
-![conta0](//images.contentful.com/alneenqid6w5/3AhidhqtTaCqiuGMKK2c64/8c5e8f0067ad5ec80685bdcca8d79c95/conta0.png)
+![conta0](https://images.contentful.com/alneenqid6w5/3AhidhqtTaCqiuGMKK2c64/8c5e8f0067ad5ec80685bdcca8d79c95/conta0.png)
 
 ### End of the period
 
 1. i = 1%
 2. n = 12
 3. PV = 1000
-4. ![conta1](//images.contentful.com/alneenqid6w5/4CaAz5DKdaUSY0OwaGEsUu/4afb38b8c7a78977d011f2d6333800d6/conta1.png)![conta2](//images.contentful.com/alneenqid6w5/3hQTOBVJqgMAyMWWia0aAY/5f7fbb82ebeb8b5e912baca35ea39b9b/conta2.png)
+4. ![conta1](https://images.contentful.com/alneenqid6w5/4CaAz5DKdaUSY0OwaGEsUu/4afb38b8c7a78977d011f2d6333800d6/conta1.png)![conta2](https://images.contentful.com/alneenqid6w5/3hQTOBVJqgMAyMWWia0aAY/5f7fbb82ebeb8b5e912baca35ea39b9b/conta2.png)
diff --git a/docs/tutorials/en/how-does-promotion-proration-work.md b/docs/tutorials/en/how-does-promotion-proration-work.md
index 22006422b..1253dbd01 100644
--- a/docs/tutorials/en/how-does-promotion-proration-work.md
+++ b/docs/tutorials/en/how-does-promotion-proration-work.md
@@ -38,7 +38,7 @@ Let's say a nominal discount promotion of US$ 156.00 will be applied to a cart w
 
 Considering the calculation logic above, the proration would be like this:
 
-![tabelaex.en](//images.ctfassets.net/alneenqid6w5/2mLv3HI7hgSRXkGyNwQRtT/1e529a7d90cc02e13cfdf07f488f56e8/tabelaex.en.png)
+![tabelaex.en](https://images.ctfassets.net/alneenqid6w5/2mLv3HI7hgSRXkGyNwQRtT/1e529a7d90cc02e13cfdf07f488f56e8/tabelaex.en.png)
 
 
 This calculation is applied to unitary products, such as a blouse or a table, but some products have a configuration called multiplier unit, such as a floor box with 2.5 m², for example.
diff --git a/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index 7e26f4ac0..5c51a4d60 100644
--- a/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -29,7 +29,7 @@ Instead of using the IDs of each item (which would generate separate orders in o
 
 You can find both IDs through the report generated on the integration's panel on VTEX Admin.
 
-![mercalo-livre-pedido-id-en](//images.ctfassets.net/alneenqid6w5/5CZg21BumbrNw5QjimjuGt/67fefe0993b7ca80eb365428f389fd4d/mercalo-livre-pedido-id.png)
+![mercalo-livre-pedido-id-en](https://images.ctfassets.net/alneenqid6w5/5CZg21BumbrNw5QjimjuGt/67fefe0993b7ca80eb365428f389fd4d/mercalo-livre-pedido-id.png)
 
 
 <div class="alert alert-warning">
diff --git a/docs/tutorials/en/how-does-the-delivery-flow-work.md b/docs/tutorials/en/how-does-the-delivery-flow-work.md
index 8959e64ac..a733d1a9a 100644
--- a/docs/tutorials/en/how-does-the-delivery-flow-work.md
+++ b/docs/tutorials/en/how-does-the-delivery-flow-work.md
@@ -27,4 +27,4 @@ VTEX platform gives you the freedom to use these settings in a variety of ways,
 
 But for now, let's stick to the most basic scenario, illustrated by the image below:
 
-![Logistics Concept English](//images.ctfassets.net/alneenqid6w5/4dxX4SvwV2SuCekgeM480w/2a69059d4efd30c0610ef04df02cc49c/Component__19_.png)
+![Logistics Concept English](https://images.ctfassets.net/alneenqid6w5/4dxX4SvwV2SuCekgeM480w/2a69059d4efd30c0610ef04df02cc49c/Component__19_.png)
diff --git a/docs/tutorials/en/how-does-the-search-context-on-website-folders-operate.md b/docs/tutorials/en/how-does-the-search-context-on-website-folders-operate.md
index 1c5088942..a2f3fc242 100644
--- a/docs/tutorials/en/how-does-the-search-context-on-website-folders-operate.md
+++ b/docs/tutorials/en/how-does-the-search-context-on-website-folders-operate.md
@@ -39,7 +39,7 @@ Using the same previous example, if we create a folder named **my-landing-page**
 
 ### Setup
 
-![](//images.contentful.com/alneenqid6w5/ZvEGMDPUs0OsuCkoUsqqS/4411604b8b78124edcbacd46cc45ed53/ContextoDeBusca.PNG "Search Context")
+![](https://images.contentful.com/alneenqid6w5/ZvEGMDPUs0OsuCkoUsqqS/4411604b8b78124edcbacd46cc45ed53/ContextoDeBusca.PNG "Search Context")
 
 **Important**:
 
diff --git a/docs/tutorials/en/how-does-the-type-of-delivery-work.md b/docs/tutorials/en/how-does-the-type-of-delivery-work.md
index c700ca12a..5886d81df 100644
--- a/docs/tutorials/en/how-does-the-type-of-delivery-work.md
+++ b/docs/tutorials/en/how-does-the-type-of-delivery-work.md
@@ -29,7 +29,7 @@ On the cart area, the delivery options are separated by shipping type, not by ca
 
 The following picture shows how the shipping options would be displayed on the checkout according to the example mentioned before: 
 
-![Transportadoras Checkout EN](//images.ctfassets.net/alneenqid6w5/4cCgmqCPRS8ou84UOuQege/53fdf91f37084eedf58eb9b0def2c355/Transportadoras_Checkout_EN.png)
+![Transportadoras Checkout EN](https://images.ctfassets.net/alneenqid6w5/4cCgmqCPRS8ou84UOuQege/53fdf91f37084eedf58eb9b0def2c355/Transportadoras_Checkout_EN.png)
 
 Notice that, even though five carriers are registered (in the **Regular** and **Express** categories), only two freight options are displayed to the customer. This is not because the other carriers do not fulfill the cart requirement, but because, within the same type of freight, only the carrier with the lowest price or the shortest delivery time will be displayed.
 
diff --git a/docs/tutorials/en/how-does-vtex-search-work.md b/docs/tutorials/en/how-does-vtex-search-work.md
index b5cb98574..986c807dd 100644
--- a/docs/tutorials/en/how-does-vtex-search-work.md
+++ b/docs/tutorials/en/how-does-vtex-search-work.md
@@ -73,7 +73,7 @@ To understand VTEX search, we must first become familiar with the indexer and it
 
 The catalog indexer is a quick access scalable database, with configurable algorithms for result prioritization. It is positioned between conventional database and user. See the outline below:
 
-![database](//images.ctfassets.net/alneenqid6w5/5ACXw5iwhZP4iT1DwuEVOi/3c3b66551bf05d00042ed3babdfc004f/database.JPG)
+![database](https://images.ctfassets.net/alneenqid6w5/5ACXw5iwhZP4iT1DwuEVOi/3c3b66551bf05d00042ed3babdfc004f/database.JPG)
 
 The indexer contains all the information referring to the product catalog (products, SKUs, brands, departments, categories). The search engine uses this information to locate products and to display these in shop windows and search results. However, __only already indexed products can be found by the search__.
 
diff --git a/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md b/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md
index 711dcfa4b..36819908d 100644
--- a/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md
+++ b/docs/tutorials/en/how-is-pro-rata-calculated-in-vtex.md
@@ -21,6 +21,6 @@ The discount calculation goes like this: `monthly fee divided by the number of d
 
 So if your monthly payment had a value of $ 750 in May - 31 days - and you hired VTEX on May 6, you would be deducted $ 145.16 on your next bill.
 
-![prorata PT](//images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
+![prorata PT](https://images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
 
 The calculation was: `$ 750/31 = $ 24,19 x 3 (days) = $ 145,16`
diff --git a/docs/tutorials/en/how-is-taxhub-api-rest-structure.md b/docs/tutorials/en/how-is-taxhub-api-rest-structure.md
index 63cef087d..8d4e5418b 100644
--- a/docs/tutorials/en/how-is-taxhub-api-rest-structure.md
+++ b/docs/tutorials/en/how-is-taxhub-api-rest-structure.md
@@ -53,7 +53,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubAPIGetTax](//images.contentful.com/alneenqid6w5/4CaoACwzqEYcUQem6okKQO/0e295bc9101cc0b46e7669a49b6f99e3/TaxHubAPIGetTax.jpg)
+![TaxHubAPIGetTax](https://images.contentful.com/alneenqid6w5/4CaoACwzqEYcUQem6okKQO/0e295bc9101cc0b46e7669a49b6f99e3/TaxHubAPIGetTax.jpg)
 
 __2 Occupation Area__
 
@@ -99,7 +99,7 @@ Response:
 ```
  
 Evidence:
-![TaxHubOccupationArea](//images.contentful.com/alneenqid6w5/2lJDIuKFz6AwgM62eI6aWA/c0bab0f8e5016e3ced947cfb94050d43/TaxHubOccupationArea.jpg)
+![TaxHubOccupationArea](https://images.contentful.com/alneenqid6w5/2lJDIuKFz6AwgM62eI6aWA/c0bab0f8e5016e3ced947cfb94050d43/TaxHubOccupationArea.jpg)
 
 __3 FiscalRegion__
 
@@ -137,7 +137,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubFiscalRegion](//images.contentful.com/alneenqid6w5/3i7TuC4rJYwoIWY62UwgE0/5cfc50a55c0e068a2dea68573a636a1b/TaxHubFiscalRegion.jpg)
+![TaxHubFiscalRegion](https://images.contentful.com/alneenqid6w5/3i7TuC4rJYwoIWY62UwgE0/5cfc50a55c0e068a2dea68573a636a1b/TaxHubFiscalRegion.jpg)
 
 __4	CustomerCode__
 - Host: http://api.beta.vtex.com
@@ -171,7 +171,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubCustomerCode](//images.contentful.com/alneenqid6w5/5ANPppLxvikIK4Kkaoe6qM/3d5033469dc13154c1bae8ddaeb02c06/TaxHubCustomerCode.jpg)
+![TaxHubCustomerCode](https://images.contentful.com/alneenqid6w5/5ANPppLxvikIK4Kkaoe6qM/3d5033469dc13154c1bae8ddaeb02c06/TaxHubCustomerCode.jpg)
 
 __5	ItemCode__
 
@@ -207,7 +207,7 @@ Response:
 
 Evidence:
 
-![TaxHubItemCode](//images.contentful.com/alneenqid6w5/4im391LOekSmYIgWgeqIIK/078dbcbb83861e5b90d9b0b9519778e5/TaxHubItemCode.jpg)
+![TaxHubItemCode](https://images.contentful.com/alneenqid6w5/4im391LOekSmYIgWgeqIIK/078dbcbb83861e5b90d9b0b9519778e5/TaxHubItemCode.jpg)
 
 __6 Aliquot__
 - Host: http://api.beta.vtex.com
@@ -244,7 +244,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubAliquot](//images.contentful.com/alneenqid6w5/6d6Kgove5GaWM2As0EAqmg/6959389c39c4d0c69cccd1982ccf7c6e/TaxHubAliquot.jpg)
+![TaxHubAliquot](https://images.contentful.com/alneenqid6w5/6d6Kgove5GaWM2As0EAqmg/6959389c39c4d0c69cccd1982ccf7c6e/TaxHubAliquot.jpg)
 
 __7 TaxValue__
 
@@ -292,6 +292,6 @@ Response:
 ```
 
 Evidence:
-![TaxHubTaxValue](//images.contentful.com/alneenqid6w5/53rujXNKTYs0kugAMwSca8/53b29d1078e0960a39360bdad84e4b7e/TaxHubTaxValue.jpg)
+![TaxHubTaxValue](https://images.contentful.com/alneenqid6w5/53rujXNKTYs0kugAMwSca8/53b29d1078e0960a39360bdad84e4b7e/TaxHubTaxValue.jpg)
 
 [Continue reading about TaxHub with our article about its JS Structure](https://taxhub-estructura-de-app-en-js "TaxHub Estructura de App en JS")
diff --git a/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md b/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md
index d522a9e0e..30d8d37b6 100644
--- a/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md
+++ b/docs/tutorials/en/how-is-the-order-delivery-deadline-calculated.md
@@ -22,7 +22,7 @@ The shipping time calculation for an order takes into account the following aspe
 - [Dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
 - [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
 
-![lead_time_image_total_time_EN](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
+![lead_time_image_total_time_EN](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
 
 You configure e time frame for each one of them and what your customer sees at checkout is a shipping time calculated adding those configurationn.
 
diff --git a/docs/tutorials/en/how-is-the-taxhub-app-structure-in-js.md b/docs/tutorials/en/how-is-the-taxhub-app-structure-in-js.md
index 76121f2f5..56d08c2a5 100644
--- a/docs/tutorials/en/how-is-the-taxhub-app-structure-in-js.md
+++ b/docs/tutorials/en/how-is-the-taxhub-app-structure-in-js.md
@@ -34,7 +34,7 @@ Define the name of the initial file with the same country of the store.
 Example: argentina.js or mexico.js, the .js file of the main folder and folder must have the same name. The IVA folder can have any name. 
 
 The call order should be also followed for development:
-![TaxHubTree](//images.contentful.com/alneenqid6w5/5hPFG8m6pUCMuIg8e2Iymm/957b9c89844099db690e82abe53c2b7a/TxHubTree.jpg)
+![TaxHubTree](https://images.contentful.com/alneenqid6w5/5hPFG8m6pUCMuIg8e2Iymm/957b9c89844099db690e82abe53c2b7a/TxHubTree.jpg)
 
 After the changes, the file should be uploaded to VTEX in the .zip format always with the same folder structure.
 
diff --git a/docs/tutorials/en/how-my-account-works.md b/docs/tutorials/en/how-my-account-works.md
index 8292cb5b3..fe8f41f35 100644
--- a/docs/tutorials/en/how-my-account-works.md
+++ b/docs/tutorials/en/how-my-account-works.md
@@ -34,7 +34,7 @@ To learn about <b>My Account</b> customization, see our developer documentation
 
 In this section, customers can manage their personal data saved in the store. They can [edit their profile information](#edit),[ set a new password](#password), and [choose whether to receive emails with promotions](#newsletter).
 
-![profile EN](//images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/a9f2ca072b2a08cb6cb1bc196b9c9f1e/profile_EN.png)
+![profile EN](https://images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/a9f2ca072b2a08cb6cb1bc196b9c9f1e/profile_EN.png)
 
 ### Edit
 
@@ -83,7 +83,7 @@ In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJT
 
 This section displays a list of all orders placed by the customer in your store. The list is sorted by creation date and displays details such as order date, total price of the order, order ID, status, and items purchased.
 
-![orders EN](//images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/29e797af3e99000a06d906bf5e3ae0d1/orders_EN.png)
+![orders EN](https://images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/29e797af3e99000a06d906bf5e3ae0d1/orders_EN.png)
 
 The **Orders** section allows customers to track the progress of their orders and offers options such as cancel or change orders. See below all available options.
 
@@ -107,7 +107,7 @@ By clicking on an order in the list, the customer will be able to view the detai
 
 Customers can also use the option [Order again](#order-again) in this page. By clicking on [More options](#more-options), the [Change order](#change-order) and [Request cancellation](#request-cancellation) features will be displayed (if enabled in your store and the order is in the `Handling shipping` status).
 
-![order details EN](//images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/ee071c1cc75a884c9daecb85072d3453/order_details_EN.png)
+![order details EN](https://images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/ee071c1cc75a884c9daecb85072d3453/order_details_EN.png)
 
 #### Change order
 
@@ -134,7 +134,7 @@ To add new cards, follow the steps below:
 6. Solve the reCaptcha challenge.
 7. The card validation process will happen automatically. If there is no problem, you will be redirected to the card list and the new card will appear on the list.
 
-![Card ReCaptcha](//images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/ab1e37db8b01f154e80f8d2f4f562d7d/Card_ReCaptcha_EN.gif)
+![Card ReCaptcha](https://images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/ab1e37db8b01f154e80f8d2f4f562d7d/Card_ReCaptcha_EN.gif)
 
 However, there are limitations for stores using [3DS](https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) authentication (V1 or V2) in their acquirers:
 
@@ -156,7 +156,7 @@ In this section, customers can manage all their subscriptions, as well as modify
 
 This section can be accessed on the left side menu by clicking on **Authentication** in the user profile settings. It offers options for password and session management.
 
-![My Authentication app EN](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
+![My Authentication app EN](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/945cc2ade2766758e484814c3e380708/My_Authentication_app_EN.png)
 
 ### Password management
 
@@ -166,7 +166,7 @@ The **Password** component allows users to create their passwords, if they do no
 2. In the **Code** field, enter the verification code received by email.
 3. In the **New password** field, enter a new password. Below those fields, you will see the requirements for setting a valid password. As the user types the password meeting those requirements, their symbols will change from red to green. The password will be valid only if all symbols are green.
 4. Once you have entered a valid password, click on the `SAVE PASSWORD` button.  
-![My Authentication create password EN](//images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/fb226bc32cfc48422cec830332d10762/My_Authentication_create_password_EN.png)
+![My Authentication create password EN](https://images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/fb226bc32cfc48422cec830332d10762/My_Authentication_create_password_EN.png)
 
 To change an existing password, follow the instructions below:
 
@@ -174,7 +174,7 @@ To change an existing password, follow the instructions below:
 2. Enter the current password in the corresponding field.
 3. Enter the new password in the corresponding field, following all the requirements.
 4. Click on `SAVE PASSWORD`.
-![My Authentication change password EN](//images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/4a055c06066c293502ffb9652d220c93/My_Authentication_change_password_EN.png)
+![My Authentication change password EN](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/4a055c06066c293502ffb9652d220c93/My_Authentication_change_password_EN.png)
 
 <div class="alert alert-info">
 If you have forgotten your password, you cannot recover it using the option for resetting passwords. To recover your password, you must log out of your current session, try to log in using your email address and password, and click on <strong>I forgot my password</strong>.
@@ -188,7 +188,7 @@ To view active sessions, click on the `VIEW SESSIONS` button, and you will be re
 
 To revoke access from other sessions, click on the `LOG OUT` button of that session.
 
-![My Authentication Session Management EN](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
+![My Authentication Session Management EN](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/ebcd1548b887d23b0fd661a0e05a0a73/My_Authentication_Session_Management_EN_blur.png)
 
 ## Basic settings 
 
@@ -199,7 +199,7 @@ In **My Orders**, you determine which sections will be visible to the customer i
 * In **ORDERS**, the <a class="far fa-check-square"></a> _Visible_ option determines whether the customer has the [Orders](#orders) section to track their orders. 
 * In **ADDRESSES**, the <a class="far fa-check-square"></a> _Visible_ option defines whether the customer will have the [Addresses](#addresses) section with their address’ details.
 
-![vtex-my-account_EN](//images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/9605097215fa1591bfc7e49de4b48735/vtex-my-account_EN.png)
+![vtex-my-account_EN](https://images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/9605097215fa1591bfc7e49de4b48735/vtex-my-account_EN.png)
 
 By default, the **CARDS** and **ORDERS** options are configured as visible. To change these settings or enable others, follow the steps below: 
 
diff --git a/docs/tutorials/en/how-order-authorization-works.md b/docs/tutorials/en/how-order-authorization-works.md
index 31263e9b2..ad51b3a1b 100644
--- a/docs/tutorials/en/how-order-authorization-works.md
+++ b/docs/tutorials/en/how-order-authorization-works.md
@@ -17,7 +17,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 In the VTEX Admin, in **Store Settings > Orders > Order Authorization**, you can control and approve orders that have a price divergence in your store.
 
-![print_autorizacao_pedidos_EN](//images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/4fc80cda8d50acff5ed646a00dc5f01f/print_autorizacao_pedidos_EN.png)
+![print_autorizacao_pedidos_EN](https://images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/4fc80cda8d50acff5ed646a00dc5f01f/print_autorizacao_pedidos_EN.png)
 
 Price divergence errors may occur in two main scenarios:
 
diff --git a/docs/tutorials/en/how-order-authorization-workss.md b/docs/tutorials/en/how-order-authorization-workss.md
index c4527672b..5bb84e9a9 100644
--- a/docs/tutorials/en/how-order-authorization-workss.md
+++ b/docs/tutorials/en/how-order-authorization-workss.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 In the Order Management module, __Order Authorization__ allows you to control approvals for orders in your store that have a price divergence.
 
-![autorização-de-pedidos EN](//images.ctfassets.net/alneenqid6w5/2lbMgKkD1d4Bm7jJwPECqg/a8959ca6d3690c3a53d2e6a34fbc4fa6/autoriza____o-de-pedidos__EN.png)
+![autorização-de-pedidos EN](https://images.ctfassets.net/alneenqid6w5/2lbMgKkD1d4Bm7jJwPECqg/a8959ca6d3690c3a53d2e6a34fbc4fa6/autoriza____o-de-pedidos__EN.png)
 
 This divergence in price between orders may occur in two main scenarios:
 
diff --git a/docs/tutorials/en/how-promotion-competition-works.md b/docs/tutorials/en/how-promotion-competition-works.md
index 00a840a85..07836cf2a 100644
--- a/docs/tutorials/en/how-promotion-competition-works.md
+++ b/docs/tutorials/en/how-promotion-competition-works.md
@@ -82,7 +82,7 @@ However, they will be applied to the amount that has already been discounted by
 
 Therefore, promotions will be applied in the following order:
 
-![promocao3 EN](//images.ctfassets.net/alneenqid6w5/6nz2KJuFk4aS0eU0OGg0sM/7cf285654ec80894e0a346c90918cd33/promocao3_EN.png)
+![promocao3 EN](https://images.ctfassets.net/alneenqid6w5/6nz2KJuFk4aS0eU0OGg0sM/7cf285654ec80894e0a346c90918cd33/promocao3_EN.png)
 
 <div class="alert alert-warning">
 Orders originating from the <a href="https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> (provided by the store) or Fulfillment (delivered by the store) do not support cumulative promotions. This is because the use of promotions is restricted to specific types on both VTEX and external marketplaces.</div>
diff --git a/docs/tutorials/en/how-recursive-marketplace-works.md b/docs/tutorials/en/how-recursive-marketplace-works.md
index 09b112d2e..3b9b38900 100644
--- a/docs/tutorials/en/how-recursive-marketplace-works.md
+++ b/docs/tutorials/en/how-recursive-marketplace-works.md
@@ -33,7 +33,7 @@ Thus:
 
 - __When a VTEX store is intermediate in the order flow__: chain order with __Chain Workflow__:
 
-![marketplace-recursivo-chain-order-workflow](//images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
+![marketplace-recursivo-chain-order-workflow](https://images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
 
 
 ## Setup
diff --git a/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md b/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
index 413c745ad..eb899a697 100644
--- a/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
+++ b/docs/tutorials/en/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
@@ -44,7 +44,7 @@ As with the OMS interface, the API shows `vtex:fob_1111` in the selectedSla, del
 
 It is important that the ERP is able to accept data in this format.
 
-![](//images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
+![](https://images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
 
 ## Label
 
@@ -52,6 +52,6 @@ The order is mailed under an agreement between Correios (national postal service
 
 The label can be accessed directly through OMS, under the order list. Just click on the link and a new window will open with the label in PDF format.
 
-![Delivery label by Correios (BR) - Marketplace](//images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/4b1c70652ae5dc8248c829527d733c65/Screen_Shot_2020-03-25_at_11.43.43.png)
+![Delivery label by Correios (BR) - Marketplace](https://images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/4b1c70652ae5dc8248c829527d733c65/Screen_Shot_2020-03-25_at_11.43.43.png)
 
 If you want to make use of the label in your ERP, it is also available in the [Marketplace Protocol API](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/order-integration/orders), more information in [New Order Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-collect-orders#scenario-12-order-with-tracking-hints).
diff --git a/docs/tutorials/en/how-the-automatic-compacting-of-images-works.md b/docs/tutorials/en/how-the-automatic-compacting-of-images-works.md
index 15ac7cfc6..d67d6778d 100644
--- a/docs/tutorials/en/how-the-automatic-compacting-of-images-works.md
+++ b/docs/tutorials/en/how-the-automatic-compacting-of-images-works.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 VTEX stores have automatic compacting of images for __WebP__. This tool cuts the weight of the site by up to 25%.
 
-![webplogo](//images.contentful.com/alneenqid6w5/1HsHoCbkyM86KKA4sCWucO/0e6f078eb62b773cc927da79b8ea6f1e/webplogo.png)
+![webplogo](https://images.contentful.com/alneenqid6w5/1HsHoCbkyM86KKA4sCWucO/0e6f078eb62b773cc927da79b8ea6f1e/webplogo.png)
 
 The format, developed by Google, is more efficient than JPG or PNG, without necessarily reducing the quality of the images. It easily affords a gain of 1 or 2 seconds in page loading time (varying according to the layout).
 
diff --git a/docs/tutorials/en/how-the-documents-saving-flow-works.md b/docs/tutorials/en/how-the-documents-saving-flow-works.md
index 2c317c428..810ee4718 100644
--- a/docs/tutorials/en/how-the-documents-saving-flow-works.md
+++ b/docs/tutorials/en/how-the-documents-saving-flow-works.md
@@ -17,7 +17,7 @@ subcategory: 5gtjaqCG7eIseyCI0aSqc2
 
 The image below shows the flow of the saving of documents in Master Data. We'll explain each step.
 
-![Save flow](//images.contentful.com/alneenqid6w5/5klqkN1OEwMEq0aEQeMyIY/2ba2b7cc8e29a5ee0baad8be92aeef9a/MDSaveDiagram.png)
+![Save flow](https://images.contentful.com/alneenqid6w5/5klqkN1OEwMEq0aEQeMyIY/2ba2b7cc8e29a5ee0baad8be92aeef9a/MDSaveDiagram.png)
 
 #### Save API call
 It happens when the user calls the saving documents APIs (POST, PUT or PATCH).
diff --git a/docs/tutorials/en/how-the-order-replacement-works.md b/docs/tutorials/en/how-the-order-replacement-works.md
index 567ebaac1..0c78d4615 100644
--- a/docs/tutorials/en/how-the-order-replacement-works.md
+++ b/docs/tutorials/en/how-the-order-replacement-works.md
@@ -61,13 +61,13 @@ Also, it's not possible to replace orders in the following statuses:
 
 With this feature, your store users get a redesigned My Orders page with change and cancellation options:
 
-![meus pedidos1 EN](//images.contentful.com/alneenqid6w5/6qCTCcaC2WSE8AgcGuI2YM/c435205525f59c10f5c04c664229044b/meus_pedidos1_EN.png)
+![meus pedidos1 EN](https://images.contentful.com/alneenqid6w5/6qCTCcaC2WSE8AgcGuI2YM/c435205525f59c10f5c04c664229044b/meus_pedidos1_EN.png)
 
-![meus pedidos3 EN](//images.ctfassets.net/alneenqid6w5/r8wqLRzyGOEmGcMuWQYMg/3fa6aaad6bd888246457d9e96e704516/meus_pedidos3_EN.png)
+![meus pedidos3 EN](https://images.ctfassets.net/alneenqid6w5/r8wqLRzyGOEmGcMuWQYMg/3fa6aaad6bd888246457d9e96e704516/meus_pedidos3_EN.png)
 
 When you select **Change order**, the customers are taken to a screen where they choose which information they would like to replace:
 
-![meus pedidos2 EN](//images.contentful.com/alneenqid6w5/5ivhWzwvD2UMGEmiWUkcM2/888904d626fd46212329ab5ca423019f/meus_pedidos2_EN.png)
+![meus pedidos2 EN](https://images.contentful.com/alneenqid6w5/5ivhWzwvD2UMGEmiWUkcM2/888904d626fd46212329ab5ca423019f/meus_pedidos2_EN.png)
 
 To complete the change, customers are taken to the cart and the Checkout, where they can alter address, freight, payment method and SKU.
 
diff --git a/docs/tutorials/en/how-the-seller-portal-catalog-works.md b/docs/tutorials/en/how-the-seller-portal-catalog-works.md
index 0ed56b524..80d0172d6 100644
--- a/docs/tutorials/en/how-the-seller-portal-catalog-works.md
+++ b/docs/tutorials/en/how-the-seller-portal-catalog-works.md
@@ -21,7 +21,7 @@ The Seller Portal Catalog is the module where you configure your store's product
 
 The Seller Portal Catalogue architecture is based on fundamental concepts distributed throughout the following hierarchy:
 
-![ilustra-catalogoEN](//images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/0b0ac21f576210cc1acc7acac5391a93/ilustra-catalogoEN.png)
+![ilustra-catalogoEN](https://images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/0b0ac21f576210cc1acc7acac5391a93/ilustra-catalogoEN.png)
 
 - **Categories:** ways in which your products can be organized. You cannot add your own categories; the marketplace defines the categories that are available to classify your products under. Each product will necessarily be linked to an already existing category.  
 - **Brands:** part of the attributes that characterize your store's products, allowing your customers to also find what they are looking for in a more specific way. You cannot add your own brands, the ones shown in the *Brands* tab have already been imported from the marketplace.    
diff --git a/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md b/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md
index 669d0d2e4..e0ab0bd52 100644
--- a/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md
+++ b/docs/tutorials/en/how-to-activate-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 The [Shareable Cart](https://apps.vtex.com/vtex-social-selling/p) app allows sales assistants to select products for their customers and share the cart through channels such as WhatsApp, Facebook Messenger and email.
 
-![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 This article explains how to install the app and configure this functionality in your store. After completing the activation steps, your sales assistants will be able to [follow the instructions](https://help.vtex.com/en/tutorial/como-usar-o-app-carrinho-compartilhavel--3ePPpkmeZ96GXbeIoGZbTN) to start your Social Selling strategies.
 
@@ -84,7 +84,7 @@ You can change the button colors on your store's cart sharing interface through
 
 In the image below, option A shows the original colors and option B shows one possible customization.
 
-![shareable-cart-ui-customization](//images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
+![shareable-cart-ui-customization](https://images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
 
 The code below must be added at the end of the `checkout5-custom.css` or `checkout6-custom.css` file, available for customization in *Store Settings > Checkout > Code*. The file that should be edited depends on the version of the Checkout used by your store.
 
diff --git a/docs/tutorials/en/how-to-alter-a-banner.md b/docs/tutorials/en/how-to-alter-a-banner.md
index 683c39540..c35735d5e 100644
--- a/docs/tutorials/en/how-to-alter-a-banner.md
+++ b/docs/tutorials/en/how-to-alter-a-banner.md
@@ -22,14 +22,14 @@ We will use a banner on the Home Page as an example, but these step-by-step inst
 3. Click the **Sites and Channels** folder.
 4. Click the **name of your store**.
 5. Click the **"/" folder**.
-![CMS instrução - EN](//images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
+![CMS instrução - EN](https://images.ctfassets.net/alneenqid6w5/4hp4fJ22GIWmEQ2ggQGCaE/910148475de19dfac0b0bd451cee1f7a/CMS_instru____o_-_EN.png)
 6. Click on the **Home** file.
 7. Click on the **Settings** tab.
 8. Click on the “pencil” for editing.
-![cms-home-settings EN](//images.ctfassets.net/alneenqid6w5/1Gs6bDdZs4eqaiQmK6qScC/272aa7943884746f32c66b75bb86b58d/banner_home_settings_-_EN.png)
+![cms-home-settings EN](https://images.ctfassets.net/alneenqid6w5/1Gs6bDdZs4eqaiQmK6qScC/272aa7943884746f32c66b75bb86b58d/banner_home_settings_-_EN.png)
 9. The banner window will open.
 10. Click on the pencil that appears on the screen.
-![cms_home_settings_lapis EN](//images.ctfassets.net/alneenqid6w5/5Js48igaXuycwYaMEkSG2k/80d3bcf1f1fa41134cd65bacfd9cda6d/cms_settings_lapis_EN.png)
+![cms_home_settings_lapis EN](https://images.ctfassets.net/alneenqid6w5/5Js48igaXuycwYaMEkSG2k/80d3bcf1f1fa41134cd65bacfd9cda6d/cms_settings_lapis_EN.png)
 11. This will open the banner form.
 
 **Change the content of the form:**
diff --git a/docs/tutorials/en/how-to-archive-ratestaxes.md b/docs/tutorials/en/how-to-archive-ratestaxes.md
index f599f2d4a..023af18cf 100644
--- a/docs/tutorials/en/how-to-archive-ratestaxes.md
+++ b/docs/tutorials/en/how-to-archive-ratestaxes.md
@@ -18,7 +18,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 If you want to remove a rate created from the main list, for example, because it is not being used, you can move it to the list of archived taxes. By doing this, the status of the rate will be automatically changed to inactive. To do so, follow the steps below:
 
-![example 1](//images.ctfassets.net/alneenqid6w5/14f4EpASB8c2m2kMEcES0c/7e83ef6235c1d6bb8071fb4a2ae0dea4/example_1.png)
+![example 1](https://images.ctfassets.net/alneenqid6w5/14f4EpASB8c2m2kMEcES0c/7e83ef6235c1d6bb8071fb4a2ae0dea4/example_1.png)
 
 1. In the VTEX Admin, go to *Promotions > Taxes*, or type *Taxes* in the search bar at the top of the page.
 2. Search the rate that you intend to archive.
diff --git a/docs/tutorials/en/how-to-assemble-a-look-kit.md b/docs/tutorials/en/how-to-assemble-a-look-kit.md
index 03c25f459..a5a7fb6b4 100644
--- a/docs/tutorials/en/how-to-assemble-a-look-kit.md
+++ b/docs/tutorials/en/how-to-assemble-a-look-kit.md
@@ -33,13 +33,13 @@ Differences between kit and kit look:
 
 This term is widely known in the Fashion Segment. A Kit Look is a way through which you can buy several products viewing only one product screen. 
 
-![](//images.contentful.com/alneenqid6w5/2WA6REAMecCaUiSEk2uoC6/999c983b772d8025d86f6ca2d1ebf3e4/kit-look-donadolook-exemplo.gif)
+![](https://images.contentful.com/alneenqid6w5/2WA6REAMecCaUiSEk2uoC6/999c983b772d8025d86f6ca2d1ebf3e4/kit-look-donadolook-exemplo.gif)
 
 In the layout above, it is possible to choose the kit items the customer would like to buy and then click on “Comprar Produtos Selecionados”.
 
 Alternatively, if you prefer, you may buy the complete kit, with all selected items.
 
-![](//images.contentful.com/alneenqid6w5/4ol1nKNyx2WYw26wQscgEE/986c00a0096dd93ac7c3ce206ecf049e/kit-look-jackthebarber-exemplo.gif)
+![](https://images.contentful.com/alneenqid6w5/4ol1nKNyx2WYw26wQscgEE/986c00a0096dd93ac7c3ce206ecf049e/kit-look-jackthebarber-exemplo.gif)
 
 In this layout, for each item there is a button “Comprar Separadamente”.
 
diff --git a/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
index 3843d4751..08edfdd16 100644
--- a/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
@@ -21,11 +21,11 @@ To retrieve the IP of a customer that placed an order at your store, you can ana
 
 When you open an order, click "See transaction details" in the payment box:
 
-![ip pedido1 EN](//images.ctfassets.net/alneenqid6w5/23018S94Qgws4swwoUUmSW/37a40268c64fb2306cdb236f552d3e20/ip_pedido1_EN.png)
+![ip pedido1 EN](https://images.ctfassets.net/alneenqid6w5/23018S94Qgws4swwoUUmSW/37a40268c64fb2306cdb236f552d3e20/ip_pedido1_EN.png)
 
 Finally, the IP is visualized on the top right corner:
 
-![ip pedido2 EN](//images.ctfassets.net/alneenqid6w5/5TFz9FxDAQiwcuGCmcYoCu/315612e531df7562d33b80398bc80ef9/ip_pedido2_EN.png)
+![ip pedido2 EN](https://images.ctfassets.net/alneenqid6w5/5TFz9FxDAQiwcuGCmcYoCu/315612e531df7562d33b80398bc80ef9/ip_pedido2_EN.png)
 
 See more details on [How to visualize the order detail](/en/tutorial/how-to-view-the-orders-details)
 
diff --git a/docs/tutorials/en/how-to-change-orders-beta.md b/docs/tutorials/en/how-to-change-orders-beta.md
index d12c4ac50..0d13aa715 100644
--- a/docs/tutorials/en/how-to-change-orders-beta.md
+++ b/docs/tutorials/en/how-to-change-orders-beta.md
@@ -93,7 +93,7 @@ To add one or more items to the order, follow these steps:
 2. In the **Pending invoicing** section, click `Change Items`.
 3. On the **Manage order items** page, click the up arrow <i class="fas fa-angle-up"></i> to the number you want, or enter the number in the field. Then, the page will display the price and the previous number with a strikethrough, followed by the message: _"Item edited"_.
 
-    ![change_order_adding_items_EN](//images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/d1f2ff7078f9a72db8ab25b8dda60e7c/change_order_adding_items_EN.png)
+    ![change_order_adding_items_EN](https://images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/d1f2ff7078f9a72db8ab25b8dda60e7c/change_order_adding_items_EN.png)
 
 4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
 5. Click `Review and Apply`.
@@ -114,7 +114,7 @@ To add one or more products to an order, follow these steps:
   > If you click the product name, you will be redirected to the product page on the store's website.
 6. Then click `Add Selected Items`, and the following message will be displayed: _"Items added"_.
 
-    ![change_order_adding_product_EN](//images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/30f4bc58081e982190d44bb730a9ca25/change_order_adding_product_EN.png)
+    ![change_order_adding_product_EN](https://images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/30f4bc58081e982190d44bb730a9ca25/change_order_adding_product_EN.png)
 
 4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
 5. Click `Review and Apply`.
@@ -131,7 +131,7 @@ To remove one or more items from an order, follow these steps:
 2. In the **Pending invoicing** section, click `Change Items`.
 3. On the **Manage order items** page, click the down arrow <i class="fas fa-angle-down"></i> to the number you want, or enter the number in the field. Then, the page will display the price and the previous number with a strikethrough, followed by the message: _"Item edited"_.
 
-    ![change_order_removing_items_EN](//images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/d2ebd588be0ed9b83aec51767bd263e3/change_order_removing_items_EN.png)
+    ![change_order_removing_items_EN](https://images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/d2ebd588be0ed9b83aec51767bd263e3/change_order_removing_items_EN.png)
 
 4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
 5. Then click `Review and Apply`.
@@ -148,7 +148,7 @@ To remove a product from an order, follow these steps:
 2. In the **Pending invoicing** section, click `Change Items`.
 3. On the **Manage order items** page, click the trash can icon <i class="far fa-trash-alt"></i> and `Remove Item`. The following confirmation message will appear: _"Item removed"_.
 
-    ![change_order_removing_product_EN](//images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/7d5515c38ca48467dbaabe0123d8b14d/change_order_removing_product_EN.png)
+    ![change_order_removing_product_EN](https://images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/7d5515c38ca48467dbaabe0123d8b14d/change_order_removing_product_EN.png)
 
 4. Review the [details of the amount change](#viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
 5. Then click `Review and Apply`.
@@ -183,7 +183,7 @@ To change the weight of an item, follow these steps:
 3. On the **Manage order items** page, enter the new weight in the row of the desired product. The unit of measure will be specified based on the Catalog settings.
 4. Then, the page will display the previous price and weight number with a strikethrough, followed by the message _"Item edited"_.
 
-    ![change_order_changing_weight_EN](//images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/c57d6801d560764df71a72e0593358f9/change_order_changing_weight_EN.png)
+    ![change_order_changing_weight_EN](https://images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/c57d6801d560764df71a72e0593358f9/change_order_changing_weight_EN.png)
 
 5. Review the [details of the amount change](##viewing-details-of-the-amount-change). You can [undo a change](#undoing-actions) if necessary.
 6. Click `Review and Apply`.
@@ -204,7 +204,7 @@ On the **Manage order items** page, as you change the order, the **Total amount*
 
 On the **Manage order items** page, you can undo a change if you want. To do this, click the curved arrow icon `Undo Action`. After this, a confirmation message will be displayed: _"Change undone"_, indicating that the action has been successfully reversed.
 
-![change_order_undoing_actions_EN](//images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/ceee7cdae26eddb1da3588d1e5af4d0e/change_order_undoing_actions_EN.png)
+![change_order_undoing_actions_EN](https://images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/ceee7cdae26eddb1da3588d1e5af4d0e/change_order_undoing_actions_EN.png)
 
 ## Processing errors
 
diff --git a/docs/tutorials/en/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md b/docs/tutorials/en/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
index 9afa3c893..8964ddbee 100644
--- a/docs/tutorials/en/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
+++ b/docs/tutorials/en/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
@@ -17,8 +17,8 @@ subcategory: 1luKrYptdi8WoMYckakUaM
 
 In order to have the access to **Search Console** data, you must check the ownership of your store. After some simple steps, you will have access to data on your store indexation performance on Google.
 
-1. Access the Search Console using a Google account through the URL: [https://www.google.com/webmasters/tools/](https://www.google.com/webmasters/tools/ "https://www.google.com/webmasters/tools/")![Primeiro passo - Verificação de Propriedade Google Search Console](//images.contentful.com/alneenqid6w5/53nfBOKjXOMGacqQIGuYKY/5d9bed2fd41df4956e89a5e52c00acc4/step_1.jpg)
-2. Select the option **Add property** and enter the URL of your store:![](//images.contentful.com/alneenqid6w5/5z5kYNIrzUo2mumc6WU6sC/d5e408a19b2ec6cf3c261ce490b43cab/step_2.jpg)
-3. Checking method: the Search Console makes available several methods for checking the ownership of your stores. The method indicated for VTEX stores is the **HTML Tag**, in the option **Alternate methods**.![](//images.contentful.com/alneenqid6w5/5QvujnxhluSkW8UOkOwUOM/86022ea4ffb6dad43f421af5ea130568/step_3.jpg)
-4. **HTML Tag** will generate a meta tag that must be entered in the template of your store’s homepage. Copy the tag shown, and enter it on the `<head>` of your store’s template:![](//images.contentful.com/alneenqid6w5/3uDOqrv56oMGUK6mAewgSO/bd820d0abd57ef29c88cccc5669e314f/step_4.jpg)
-5. After including the meta tag in the template, wait approximately 10 minutes to check the ownership on the Search Console. Once the checking is completed, you will already have access to all indexation data for your store:![](//images.contentful.com/alneenqid6w5/225MhXRikEygYCyagUY4MQ/11f0f693fa62a9700d6cec050267e98b/step_5.jpg)
+1. Access the Search Console using a Google account through the URL: [https://www.google.com/webmasters/tools/](https://www.google.com/webmasters/tools/ "https://www.google.com/webmasters/tools/")![Primeiro passo - Verificação de Propriedade Google Search Console](https://images.contentful.com/alneenqid6w5/53nfBOKjXOMGacqQIGuYKY/5d9bed2fd41df4956e89a5e52c00acc4/step_1.jpg)
+2. Select the option **Add property** and enter the URL of your store:![](https://images.contentful.com/alneenqid6w5/5z5kYNIrzUo2mumc6WU6sC/d5e408a19b2ec6cf3c261ce490b43cab/step_2.jpg)
+3. Checking method: the Search Console makes available several methods for checking the ownership of your stores. The method indicated for VTEX stores is the **HTML Tag**, in the option **Alternate methods**.![](https://images.contentful.com/alneenqid6w5/5QvujnxhluSkW8UOkOwUOM/86022ea4ffb6dad43f421af5ea130568/step_3.jpg)
+4. **HTML Tag** will generate a meta tag that must be entered in the template of your store’s homepage. Copy the tag shown, and enter it on the `<head>` of your store’s template:![](https://images.contentful.com/alneenqid6w5/3uDOqrv56oMGUK6mAewgSO/bd820d0abd57ef29c88cccc5669e314f/step_4.jpg)
+5. After including the meta tag in the template, wait approximately 10 minutes to check the ownership on the Search Console. Once the checking is completed, you will already have access to all indexation data for your store:![](https://images.contentful.com/alneenqid6w5/225MhXRikEygYCyagUY4MQ/11f0f693fa62a9700d6cec050267e98b/step_5.jpg)
diff --git a/docs/tutorials/en/how-to-check-your-balance.md b/docs/tutorials/en/how-to-check-your-balance.md
index b959831d7..7740b6e1e 100644
--- a/docs/tutorials/en/how-to-check-your-balance.md
+++ b/docs/tutorials/en/how-to-check-your-balance.md
@@ -28,7 +28,7 @@ To check your account balance, follow the step by step:
 - Click on __Account Overview__;
 - On the left side of the screen, find the __Balance__ box.
 
-![saldodisponivelEN](//images.ctfassets.net/alneenqid6w5/1nnABtiycAQhExwdQcbbHD/fe145d3e68fcab0ab97b53713244df1c/image.png_h_250)
+![saldodisponivelEN](https://images.ctfassets.net/alneenqid6w5/1nnABtiycAQhExwdQcbbHD/fe145d3e68fcab0ab97b53713244df1c/image.png_h_250)
 
 Two different values are shown in the box. The first, __Available__, shows the account balance that is available for transactions. The second, __Balance due__, refers to future payments that will be deposited into your corporate digital account.
 
diff --git a/docs/tutorials/en/how-to-configure-extra-fields-in-instore-cart.md b/docs/tutorials/en/how-to-configure-extra-fields-in-instore-cart.md
index 4899f4de0..b76736bab 100644
--- a/docs/tutorials/en/how-to-configure-extra-fields-in-instore-cart.md
+++ b/docs/tutorials/en/how-to-configure-extra-fields-in-instore-cart.md
@@ -22,9 +22,9 @@ To create the extra fields, follow the steps below:
 1. Check current store configuration via GET request on endpoint [Get orderForm configuration](https://developers.vtex.com/vtex-rest-api/reference/getorderformconfiguration). Save the JSON information returned from the request.
 
 Example used for the "inStore" store:
-![2017-08-14 20 12 34-Postman](//images.contentful.com/alneenqid6w5/6I61we4oF2AMkgcIAMgEo/772e7d2b045312f1f5c76b4d8eb9d30f/2017-08-14_20_12_34-Postman.png)
+![2017-08-14 20 12 34-Postman](https://images.contentful.com/alneenqid6w5/6I61we4oF2AMkgcIAMgEo/772e7d2b045312f1f5c76b4d8eb9d30f/2017-08-14_20_12_34-Postman.png)
     2. Make a POST request using the endpoint [Update orderForm configuration](https://developers.vtex.com/vtex-rest-api/reference/updateorderformconfiguration) cwith the same saved JSON data, and add the extra fields (`fields`) with the information inside the `apps` property.
 
 Example of POST request:
 
-![2017-08-14 20 11 18-Postman](//images.contentful.com/alneenqid6w5/6QIwIi5IBiy4qCyu2qseey/538d03ceb7f47ea0e47eb8047b931da6/2017-08-14_20_11_18-Postman.png)
+![2017-08-14 20 11 18-Postman](https://images.contentful.com/alneenqid6w5/6QIwIi5IBiy4qCyu2qseey/538d03ceb7f47ea0e47eb8047b931da6/2017-08-14_20_11_18-Postman.png)
diff --git a/docs/tutorials/en/how-to-configure-mercado-pago-transparente-in-the-payments-module.md b/docs/tutorials/en/how-to-configure-mercado-pago-transparente-in-the-payments-module.md
index f6ebbe43e..586be1fd5 100644
--- a/docs/tutorials/en/how-to-configure-mercado-pago-transparente-in-the-payments-module.md
+++ b/docs/tutorials/en/how-to-configure-mercado-pago-transparente-in-the-payments-module.md
@@ -18,13 +18,13 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 The purpose of this article is to describe the steps for adding and configuring the Mercado Pago Transparente connector.
 
 First, you'll need to access the Payments module and click on **Settings**, at the right on the top bar.
-![2017-01-26 19_04_37-Transações _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/6Gxdu2Z0NqyggYkEe8A8q0/7fd3e1c15fd89ec76c90473329ff1439/2017-01-26-19_04_37-Transa_C3_A7_C3_B5es-_-VTEX-PCI-Gateway-300x105.png)
+![2017-01-26 19_04_37-Transações _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/6Gxdu2Z0NqyggYkEe8A8q0/7fd3e1c15fd89ec76c90473329ff1439/2017-01-26-19_04_37-Transa_C3_A7_C3_B5es-_-VTEX-PCI-Gateway-300x105.png)
 
 After that, you'll have to click on **Gateway Affiliations** and then on the **+** icon, on the right. You'll see a collection of connectors and will just need to select the Mercado Pago Transparente card (__MercadoPagoV1__).
-![2017-01-26 19_12_51-Conectores _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/69Wai0Un0A0S4C0EyuCsme/8bcdc06f9863147fb04c403e83125fea/2017-01-26-19_12_51-Conectores-_-VTEX-PCI-Gateway-300x245.png)
+![2017-01-26 19_12_51-Conectores _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/69Wai0Un0A0S4C0EyuCsme/8bcdc06f9863147fb04c403e83125fea/2017-01-26-19_12_51-Conectores-_-VTEX-PCI-Gateway-300x245.png)
 
 You will be redirected to the page where you have to edit the fields related to the connector. We recommend you to rename the field **Affiliation name**, so it will be easier to find in **Payment conditions**.
-![2017-01-26 20_00_11-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/3oiEcYJ3LGCGiGA0Uq2ucm/2e15790c707b2496e38d2d89fc88687f/2017-01-26-20_00_11-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x208.png)
+![2017-01-26 20_00_11-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/3oiEcYJ3LGCGiGA0Uq2ucm/2e15790c707b2496e38d2d89fc88687f/2017-01-26-20_00_11-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x208.png)
 
 You should then [configure the anti-fraud](/en/faq/how-to-configure-mercadopago-transparente) and [enter the credentials](/en/faq/where-can-i-see-my-mercado-pago-transparente-credentials/). Remember that the **Client Id** and **Client Secret** values must not start with **APP_USR**.
 
diff --git a/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index 4cdcd958b..c82847ed5 100644
--- a/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -30,7 +30,7 @@ In B2B operations, there is a need to maintain relationships with buyers who req
 2. On the tab __General__, fill in the desired value in the field __Minimum total amount in cart__.
 3. Click `Save`.
 
-![Minimum Order Value - EN](//images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/871fa991d270c1e64c12f0cdf3c5a4ab/Minimum_Order_Value_-_EN.png)
+![Minimum Order Value - EN](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/871fa991d270c1e64c12f0cdf3c5a4ab/Minimum_Order_Value_-_EN.png)
 
 <div class="alert alert-warning">
 The customer is allowed to assemble a cart with a value less than that specified in the "Minimum total amount in cart" rule. However, at the time of closing the purchase, only orders that are equal to or greater than the specified amount will be completed.
@@ -42,7 +42,7 @@ The customer is allowed to assemble a cart with a value less than that specified
 2. On the tab __General__, fill in the desired value in the field __Max quantity of the same SKU in cart__.
 3. Click `Save`.
 
-![Max quantity of the same SKU in cart](//images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/0a8cf8d7955ae90cea6332cafb6990ed/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_EN.png)
+![Max quantity of the same SKU in cart](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/0a8cf8d7955ae90cea6332cafb6990ed/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_EN.png)
 
 <div class="alert alert-warning">
 There are no limits on the maximum number of <b>same SKU</b> items per cart. The only restriction refers to the maximum number of items from <b>different SKUs</b>, which must be a maximum of 300 items per cart.
diff --git a/docs/tutorials/en/how-to-configure-payment-conditions.md b/docs/tutorials/en/how-to-configure-payment-conditions.md
index fe683f862..0a871aac8 100644
--- a/docs/tutorials/en/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/en/how-to-configure-payment-conditions.md
@@ -85,7 +85,7 @@ In Step 5. you can choose other payment methods such as debit cards, cobranded,
 14. To choose between compound interest and simple interest, select __Compound Interest applied. Change__. A selection box will appear allowing you to choose between the two options. 
 15. Click on __Save*__.
 
-![Juros - en](//images.ctfassets.net/alneenqid6w5/7IPLydgcKCsQUItYhn4LgD/efa95228eb34354425a0064491122b46/Juros_-_en.png)
+![Juros - en](https://images.ctfassets.net/alneenqid6w5/7IPLydgcKCsQUItYhn4LgD/efa95228eb34354425a0064491122b46/Juros_-_en.png)
 
 #### External Interest
 
@@ -101,4 +101,4 @@ In some countries, interest on installment purchases is charged directly by the
 2. In the __Payment Conditions__ tab, click on the payment term you wish to remove.
 3. Click on the trash can icon.
 
-![Remove payment condition](//images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/8fc094a085a51f3b24d705956c14e052/remove_payment_condition.png)
+![Remove payment condition](https://images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/8fc094a085a51f3b24d705956c14e052/remove_payment_condition.png)
diff --git a/docs/tutorials/en/how-to-configure-rating-and-review-controls.md b/docs/tutorials/en/how-to-configure-rating-and-review-controls.md
index 4bcc50553..4422dad2a 100644
--- a/docs/tutorials/en/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/en/how-to-configure-rating-and-review-controls.md
@@ -41,10 +41,10 @@ These controls, unlike the others, will only work if specifically configured, as
 
 In registering the Category, there is the option to configure the Rating feature, and this is normally done in the root category:
 
-![avaliação-categoria EN](//images.ctfassets.net/alneenqid6w5/QRc6IqC0gMkGMGyuces2S/91d41a3275a79250d08d375ba86add28/avalia____o_en.png)
+![avaliação-categoria EN](https://images.ctfassets.net/alneenqid6w5/QRc6IqC0gMkGMGyuces2S/91d41a3275a79250d08d375ba86add28/avalia____o_en.png)
 
 Click on **new rating** and fill in the Name and Text fields, then save.
 
-![new-rating-categorias EN](//images.ctfassets.net/alneenqid6w5/k7zFwGh3bM8C6io8yicYU/7568bf49b49455acbf564e33146b2396/new_rating.png)
+![new-rating-categorias EN](https://images.ctfassets.net/alneenqid6w5/k7zFwGh3bM8C6io8yicYU/7568bf49b49455acbf564e33146b2396/new_rating.png)
 
 Now your Review and Rating controls are ready to be used.
diff --git a/docs/tutorials/en/how-to-configure-taxhub.md b/docs/tutorials/en/how-to-configure-taxhub.md
index 47007272c..5658543e6 100644
--- a/docs/tutorials/en/how-to-configure-taxhub.md
+++ b/docs/tutorials/en/how-to-configure-taxhub.md
@@ -25,5 +25,5 @@ To set up the tax systems, TaxHub, follow these steps:
 6.	In “Authorization Token” fill in with the service token of the previous step. Note: In certain cases, it may be unnecessary;
 7.	Click on __Save__.
 
-![TaxHub Configuration](//images.contentful.com/alneenqid6w5/RG3lWrwAOAyQYwk6gwGgq/7f291339357dac4cf07fbee9f5e0a649/TaxHubConfiguration.gif)
+![TaxHub Configuration](https://images.contentful.com/alneenqid6w5/RG3lWrwAOAyQYwk6gwGgq/7f291339357dac4cf07fbee9f5e0a649/TaxHubConfiguration.gif)
 
diff --git a/docs/tutorials/en/how-to-configure-the-favicon.md b/docs/tutorials/en/how-to-configure-the-favicon.md
index 998fac3e0..96ec51ad1 100644
--- a/docs/tutorials/en/how-to-configure-the-favicon.md
+++ b/docs/tutorials/en/how-to-configure-the-favicon.md
@@ -19,7 +19,7 @@ The favicon is the icon displayed on the browser tab next to the page title. The
 
 Example:
 
-![favicon_2](//images.contentful.com/alneenqid6w5/2azvX7m3asGckkU6c8WAcM/2e66d9a107c0394c3f1a63afff7f3149/favicon_2-1024x537.png "Favicon 2")
+![favicon_2](https://images.contentful.com/alneenqid6w5/2azvX7m3asGckkU6c8WAcM/2e66d9a107c0394c3f1a63afff7f3149/favicon_2-1024x537.png "Favicon 2")
 
 I have used Google as an example, only to reiterate that this resource is not exclusive to VTEX and can be used in any content reproduced in a browser. Read more about this issue on Google. 🙂
 
@@ -33,4 +33,4 @@ On VTEX, to ensure that the favicon will be loaded during the customer’s entir
 
 **Note 2:** The {STORENAME} variable must be replaced with the name of the store, as it is registered in the Account management.
 
-![fav](//images.contentful.com/alneenqid6w5/6j5eZzVMEE6E2KgqGgsOwU/c2292316f75f3620cd870c96df9e65fc/fav-1024x554.png)
+![fav](https://images.contentful.com/alneenqid6w5/6j5eZzVMEE6E2KgqGgsOwU/c2292316f75f3620cd870c96df9e65fc/fav-1024x554.png)
diff --git a/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md b/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md
index c2a7626f0..bdf3f5c45 100644
--- a/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md
+++ b/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md
@@ -32,7 +32,7 @@ The configurations documented in this article are done in an environment outside
 To enter the scripts that Stelo requires for the fingerprint device, you must use Google Tag Manager. To do this, log into your account at [http://www.google.com/tagmanager](http://www.google.com/tagmanager "http://www.google.com/tagmanager"). Then proceed as follows:
 
 1. In the opening menu in Google Tag Manager, click on **Nova tag**.
-2. Select **Configuração da tag** and then type **HTML personalizado**.![Tela1](//images.contentful.com/alneenqid6w5/2VjcP3lQ9aqceC82kgaAU8/68bffad6d79e91e7286c780ac16fffc7/Tela1.jpg)
+2. Select **Configuração da tag** and then type **HTML personalizado**.![Tela1](https://images.contentful.com/alneenqid6w5/2VjcP3lQ9aqceC82kgaAU8/68bffad6d79e91e7286c780ac16fffc7/Tela1.jpg)
 3. Enter the following script:
 
 ```
@@ -48,13 +48,13 @@ window.vtex.deviceFingerprint = match[1];
 </script>
 ```
 
-1. Click on **Acionamento**, Novo acionador (**+** symbol in the top right corner) and on **Configuração do acionador.**![Tela2](//images.contentful.com/alneenqid6w5/6uwEr6KGJyOCcigIMCcUoS/4142ad24f3121bee1fea9d55069d10a6/Tela2.jpg)
+1. Click on **Acionamento**, Novo acionador (**+** symbol in the top right corner) and on **Configuração do acionador.**![Tela2](https://images.contentful.com/alneenqid6w5/6uwEr6KGJyOCcigIMCcUoS/4142ad24f3121bee1fea9d55069d10a6/Tela2.jpg)
 2. Select **Evento personalizado** and enter the name **payment**.
 2. Select the flag **Alguns eventos personalizados**.
-3. In the first two boxes underneath, select: **Event** and **é igual a**. In the third one, type **payment**.![Tela3](//images.contentful.com/alneenqid6w5/5sbXgbm4g0yysWKSwmYWI0/e7d605639093f30aff58bff0efef2ae4/Tela3.jpg)
+3. In the first two boxes underneath, select: **Event** and **é igual a**. In the third one, type **payment**.![Tela3](https://images.contentful.com/alneenqid6w5/5sbXgbm4g0yysWKSwmYWI0/e7d605639093f30aff58bff0efef2ae4/Tela3.jpg)
 4. Save the trigger and the tag.
 5. In the side menu, click on **Variáveis** and then **Nova**.
-6. Click on **Configuração da variável** and select **JavaScript personalizado**.![Tela4](//images.contentful.com/alneenqid6w5/3I7Eq6Jt2wkYg6EoKAkCqC/91cca1c81534bbbc76e70db8f94be13a/Tela4.jpg)
+6. Click on **Configuração da variável** and select **JavaScript personalizado**.![Tela4](https://images.contentful.com/alneenqid6w5/3I7Eq6Jt2wkYg6EoKAkCqC/91cca1c81534bbbc76e70db8f94be13a/Tela4.jpg)
 
 Enter the following script:
 
diff --git a/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md b/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md
index 0d72d971d..84d62881c 100644
--- a/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md
+++ b/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md
@@ -37,7 +37,7 @@ You can set up Google Shopping via VTEX Admin by following the steps below:
   The URL to access the XML will be generated automatically.
 9. Save this XML to a .txt file and send the file to Google.
 
-![](//images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
+![](https://images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
 
 <div class = "alert alert-warning">
   <p>If the option <strong>Show unavailable SKUs</strong> is unchecked, out-of-stock products or SKUs will not be shown in the XML. Inactive products also do not appear in the XML.</p>
diff --git a/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md b/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
index 93040d52d..56820b965 100644
--- a/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
+++ b/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
@@ -21,7 +21,7 @@ According to the [2015 Update of the Specification for the Google Shopping feed
 
 The tags on the standard configuration of our XML form have been updated to create a new Google Merchant / Shopping feed; just select the option “Feed: Atom 1”:
 
-![](//images.contentful.com/alneenqid6w5/2ugQUy4xlaaUEOIYuu6UMe/41fd01c32b6954b14e1ef5818b94ca0c/atom1_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/2ugQUy4xlaaUEOIYuu6UMe/41fd01c32b6954b14e1ef5818b94ca0c/atom1_xml_vtex_google.gif)
 
 Proper integration with Google Merchant / Shopping requires updating the xml with the new fields, beginning September 15, 2015.
 
@@ -31,7 +31,7 @@ Find out more about the new fields on the XML form:
 
 The option responsible for defining the taxonomy of the “_Categoria_” and “_Departamento_ + _Categoria_” fields. Normally used for filling out the [g:product_type].
 
-![](//images.contentful.com/alneenqid6w5/3dgBcIJZgcKSW2YKCaksmW/653d517228e7d303e7326dfa1dcedbc1/separador_categoria_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/3dgBcIJZgcKSW2YKCaksmW/653d517228e7d303e7326dfa1dcedbc1/separador_categoria_xml_vtex_google.gif)
 
 Default (e.g.: Father Category – Child Category – Grandchild Category)
 
@@ -47,7 +47,7 @@ The field responsible for the relationship between your store’s categories and
 
 Should be filled out with the [g:google_product_category] tag
 
-![](//images.contentful.com/alneenqid6w5/307z7lsmEMgQMWIOUQWk8K/9d854eb77bb73e1c79d5307c78fb0215/categoria_global_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/307z7lsmEMgQMWIOUQWk8K/9d854eb77bb73e1c79d5307c78fb0215/categoria_global_xml_vtex_google.gif)
 
 For this field to function properly, it is necessary to verify whether the Global Category field has been filled out in the VTEX catalog.
 
diff --git a/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md b/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md
index b384584ef..ecc29a212 100644
--- a/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md
+++ b/docs/tutorials/en/how-to-create-a-development-environment-with-a-mobile-version.md
@@ -38,7 +38,7 @@ To develop a mobile version for a new website, you must proceed as follows:
 
 Storefront > Layout > CMS folder > Sites and Channels > New Website
 
-![cms-new-website](//images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
+![cms-new-website](https://images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
 
 3. Create a folder structure for the Mobile website: at this stage, you will have to create the default system folders to be used in the mobile version (search, department, category, brand, product etc.)
 
diff --git a/docs/tutorials/en/how-to-create-a-financial-access-profile.md b/docs/tutorials/en/how-to-create-a-financial-access-profile.md
index 65584dd68..79dac99a8 100644
--- a/docs/tutorials/en/how-to-create-a-financial-access-profile.md
+++ b/docs/tutorials/en/how-to-create-a-financial-access-profile.md
@@ -31,7 +31,7 @@ To create a financial role, follow the walkthrough below:
 6. (Optional) Before saving, you can **add users to this role**.
 7. Click on **Save**.
 
-![gif perfildeacessoEN](//images.ctfassets.net/alneenqid6w5/6s1lN2aC88o56Ps2OSD9jy/1c0fbd165d803a9a6c0fddac7ce8d477/gif_perfildeacessoEN.gif)
+![gif perfildeacessoEN](https://images.ctfassets.net/alneenqid6w5/6s1lN2aC88o56Ps2OSD9jy/1c0fbd165d803a9a6c0fddac7ce8d477/gif_perfildeacessoEN.gif)
 
 After you’ve created the financial role, you can associate it with your existing users.
 
@@ -47,7 +47,7 @@ To associate a user with the Finance role you’ve created, follow the steps bel
 6. Click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> button, next to the role, to add it.
 7. Click on **Save**.
 
-![gif usuárioEN](//images.ctfassets.net/alneenqid6w5/4UkPeH2Sfsp2KiSvozclnk/ef5a0fe13d88461cc9057e75cce09151/gif_usu__rioEN.gif)
+![gif usuárioEN](https://images.ctfassets.net/alneenqid6w5/4UkPeH2Sfsp2KiSvozclnk/ef5a0fe13d88461cc9057e75cce09151/gif_usu__rioEN.gif)
 
 The selected user is now associated with the Financial role and will be able to access invoices, contract information, charges and other financial information.
 
diff --git a/docs/tutorials/en/how-to-create-a-page-template.md b/docs/tutorials/en/how-to-create-a-page-template.md
index 7f1cadbc9..e24a0c678 100644
--- a/docs/tutorials/en/how-to-create-a-page-template.md
+++ b/docs/tutorials/en/how-to-create-a-page-template.md
@@ -47,7 +47,7 @@ Check out the walk-through:
 </ul></p>
 </div>
 6. Then fill in the __Template XHTML__ box with your template code. 
-![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. Click on the __Save Template__ button.
 
 To edit an existing template, the process is almost identical.
diff --git a/docs/tutorials/en/how-to-create-a-product.md b/docs/tutorials/en/how-to-create-a-product.md
index 513370858..5b3433e62 100644
--- a/docs/tutorials/en/how-to-create-a-product.md
+++ b/docs/tutorials/en/how-to-create-a-product.md
@@ -56,7 +56,7 @@ In this section, you need to add at least one trade policy to apply to the produ
 
 In this step, you must write a description with the main information related to the product. The text should contain a clear and simple product description. This is a rich text editor, which means that you can use several formatting features using the toolbar, as illustrated below.
 
-![richtext-EN](//images.contentful.com/alneenqid6w5/5qza9JxGS1DIAKpZ6LkAwC/2e79ac8b7ddffefc466714db3046c29c/richttext-EN.gif)
+![richtext-EN](https://images.contentful.com/alneenqid6w5/5qza9JxGS1DIAKpZ6LkAwC/2e79ac8b7ddffefc466714db3046c29c/richttext-EN.gif)
 
 Here are the features available:
 
@@ -89,7 +89,7 @@ To add images to the product, follow the instructions below:
 
 To rearrange the images and change their display order on the product page, you can click on an image and then drag and drop it to a certain position, as shown below.
 
-![imagens-sku-EN](//images.contentful.com/alneenqid6w5/oJHgJiv7E7RZFb7XeubfA/dba3c742cdb200d0a65cd0aa5ad70b1b/imagens-sku-EN.gif)
+![imagens-sku-EN](https://images.contentful.com/alneenqid6w5/oJHgJiv7E7RZFb7XeubfA/dba3c742cdb200d0a65cd0aa5ad70b1b/imagens-sku-EN.gif)
 
 You can change information by clicking the <i class="fas fa-ellipsis-v"></i> button in the row of each image, which opens a menu with the following options:
 
@@ -124,7 +124,7 @@ For example, a cosmetic store could configure attribute groups of a perfume as s
   1. Fixation time: long
   2. Application type: spray
 
-![atributo-EN](//images.contentful.com/alneenqid6w5/4k55tsjwIBJU1f5e2ifTmW/d083207baba781dccb4f8166f08820fc/atributo-EN.gif)
+![atributo-EN](https://images.contentful.com/alneenqid6w5/4k55tsjwIBJU1f5e2ifTmW/d083207baba781dccb4f8166f08820fc/atributo-EN.gif)
 
 After you have made the desired changes in the attribute dashboard, save the information.
 
@@ -167,7 +167,7 @@ The specifications you’ve created and their respective options will be listed
 
 By combining these different options, the system automatically generates a list of SKUs and displays it in the **[Variations](#variations)** section.
 
-![variations EN](//images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/c37697e3259b102f8292be8378cf6e2b/variations_EN.png)
+![variations EN](https://images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/c37697e3259b102f8292be8378cf6e2b/variations_EN.png)
 
 ## Specifications
 
@@ -198,7 +198,7 @@ By clicking on the button, you can perform the following actions:
   * **Select images:** select images corresponding to the variation. To select an image, just click on it. If you want to select all images at once, use the keyboard shortcut `Ctrl` + `A`.
   * **Apply to multiple variations:** you can add the selected images to multiple variations. To do so, click on `Apply to multiple variations +` and select the values of the specifications your image relates to. For example, for an image of beige sneakers, you should select the `beige` option from the `color` specification. The image will then apply to all variations whose `color` specification has the value `beige`, regardless of any other specifications you have set. 
 
-![variacoes-EN](//images.contentful.com/alneenqid6w5/1CNiASM7uobd4NUXK6Q4Wy/3c7324d43747404d6a2b09690dce2f49/variacoes-EN.gif)
+![variacoes-EN](https://images.contentful.com/alneenqid6w5/1CNiASM7uobd4NUXK6Q4Wy/3c7324d43747404d6a2b09690dce2f49/variacoes-EN.gif)
 
   * **Add images:** on this page, you can also upload new images by clicking on the `Add images` button or by dropping image files into the dotted space.
 * **Deactivate:** deactivate the SKU.
@@ -211,7 +211,7 @@ By clicking on the button, you can perform the following actions:
 
 You can view and edit all information and images related to each product variation in the variations advanced editing dashboard, illustrated below.
 
-![Advanced editing EN](//images.contentful.com/alneenqid6w5/11lFaBFxSswNbDDqgdcMbi/8a1bd4a197cb37abb2c609fad88cb1b4/Screenshot_13.png)
+![Advanced editing EN](https://images.contentful.com/alneenqid6w5/11lFaBFxSswNbDDqgdcMbi/8a1bd4a197cb37abb2c609fad88cb1b4/Screenshot_13.png)
 
 In the **Variations** section on the left side of the dashboard, you will find the list of variations of your product. To edit a specific variation, click on it.
 
@@ -222,7 +222,7 @@ To edit a large number of variations at once, you can use the Bulk edit feature
 
 1. Click on the `Bulk editing` button to open the variation editing spreadsheet.
 2. To edit information, double-click on the field you want to change.
-![edicao-massa-SKU-EN](//images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/279480fdf223ea60584f27ba4b8c2e05/image.png)
+![edicao-massa-SKU-EN](https://images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/279480fdf223ea60584f27ba4b8c2e05/image.png)
 
 You can edit the following information:
 - **Active:** whether the variation is active or not.
@@ -238,7 +238,7 @@ You can edit the following information:
 To filter the columns displayed in the spreadsheet, click on `Filter columns` and select the columns you want to hide.
 
 You can replicate information from one cell to other rows and columns. To do this, click on the blue square in the lower right corner of the cell and drag to the cells where you want to automatically replicate the value, as shown in the image below.
-![Formatacao-celula-EN](//images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/b0171c41044f0a8653d13a696a33534f/Formatacao-celula-EN.gif)
+![Formatacao-celula-EN](https://images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/b0171c41044f0a8653d13a696a33534f/Formatacao-celula-EN.gif)
 3.  After editing, click on `Apply` to save the changes.
 
 ## SEO
@@ -251,7 +251,7 @@ The way you fill in the fields in this section affects how the product will be r
 
 By filling out the SEO fields, a preview of your product in Google's results will be displayed. See an example in the image below.
 
-![SEO-EN](//images.contentful.com/alneenqid6w5/3oL8DjR85z8zbkhBcjO1sW/1fcfa63c213107f343d80f01871eeed6/Screenshot_9.png)
+![SEO-EN](https://images.contentful.com/alneenqid6w5/3oL8DjR85z8zbkhBcjO1sW/1fcfa63c213107f343d80f01871eeed6/Screenshot_9.png)
 
 ## Storefront
 
diff --git a/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
index 523162475..5462dd46d 100644
--- a/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
@@ -21,7 +21,7 @@ If you want regular promotion to be applied only for a limited number of times,
 <p>Orders with status <code>Canceling</code> or <code>Canceled</code> do not count in the defined limit.</p>
 </div>
 
-![promotion-with-restriction-en](//images.ctfassets.net/alneenqid6w5/5yz4Gzh3nao86gISu8OsCu/d7a18088185d781c140916bc1bf2299e/Promotion_with_restriction_-_EN.png)
+![promotion-with-restriction-en](https://images.ctfassets.net/alneenqid6w5/5yz4Gzh3nao86gISu8OsCu/d7a18088185d781c140916bc1bf2299e/Promotion_with_restriction_-_EN.png)
 
 You can also set the limit per customer, rather than a general usage limit. To do so, simply perform the configuration above, then click on **Enable usage limit per customer**.
 
diff --git a/docs/tutorials/en/how-to-create-a-store-name.md b/docs/tutorials/en/how-to-create-a-store-name.md
index 9cfd3d261..5e86e505d 100644
--- a/docs/tutorials/en/how-to-create-a-store-name.md
+++ b/docs/tutorials/en/how-to-create-a-store-name.md
@@ -23,7 +23,7 @@ To create or edit a [store name](https://help.vtex.com/pt/tutorial/o-que-e-store
 4. Access [Account management](https://help.vtex.com/en/tutorial/visao-geral-do-modulo-license-manager) > **Account**.
 5. In the Store section, you will see the store names that already exist in your account. You can edit the information for each store or create a new store name by clicking the **Configure this store** button.
 
-![Store name configuration](//images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/fd371329c163b0611c188cd6816e8ccf/EN.PNG)
+![Store name configuration](https://images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/fd371329c163b0611c188cd6816e8ccf/EN.PNG)
 
 Learn how to set up your stores' domain in the article [Changing the domain of the store](https://help.vtex.com/en/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
diff --git a/docs/tutorials/en/how-to-create-a-subscription-attachment.md b/docs/tutorials/en/how-to-create-a-subscription-attachment.md
index a9a389211..3377d8f8d 100644
--- a/docs/tutorials/en/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/en/how-to-create-a-subscription-attachment.md
@@ -71,11 +71,11 @@ Follow the step-by-step instructions below to configure available frequencies an
 
         * **Weekly**: possible values for this field are `0`, `1`, `2`, `3`, `4`, `5`, and `6`, representing the days of the week. Consider `0` = Sunday, `1` = Monday, `2` = Tuesday, and so on until `6` = Saturday. Separate the values by `,`, as illustrated below.
 
-        ![EN Assinatura Exemplo Valores week](//images.ctfassets.net/alneenqid6w5/3pNwE8MSIe9GevIiLZxBOf/ecba3debced2525d6cd3ab3cbbdf4a5f/EN_Assinatura_Exemplo_Valores_week.png) 
+        ![EN Assinatura Exemplo Valores week](https://images.ctfassets.net/alneenqid6w5/3pNwE8MSIe9GevIiLZxBOf/ecba3debced2525d6cd3ab3cbbdf4a5f/EN_Assinatura_Exemplo_Valores_week.png) 
 
         * **Monthly**: possible values for filling in this field at checkout are = `1`, `2`, `3`, (...) until `28`, representing the days of the month. Consider `1` = the first day of the month, `2` = the second day of the month, and so on until `28` = the twenty-eighth day of the month. Separate the values by `,`, as illustrated below.
 
-        ![EN Assinatura Exemplo Valores month](//images.ctfassets.net/alneenqid6w5/15AueDNpKyx3yBVjP0q7tY/415def684e81619e96155a1fb390a4f4/EN_Assinatura_Exemplo_Valores_month.png)
+        ![EN Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/15AueDNpKyx3yBVjP0q7tY/415def684e81619e96155a1fb390a4f4/EN_Assinatura_Exemplo_Valores_month.png)
 
 <div class="alert alert-info">
   <p>If the <strong>Permitted Values</strong> field is left blank, the date of the subscription cycle will be the same day of the week (if the frequency is weekly) or the same day of the month (if the frequency is monthly) as the original order.</p>
diff --git a/docs/tutorials/en/how-to-create-conditional-prices.md b/docs/tutorials/en/how-to-create-conditional-prices.md
index dfbd362d3..69ead8238 100644
--- a/docs/tutorials/en/how-to-create-conditional-prices.md
+++ b/docs/tutorials/en/how-to-create-conditional-prices.md
@@ -34,4 +34,4 @@ So here is a step by step showing how you can use this feature :
 6. You can define a short message, called *Teaser*, to promote this condition to your customers. (To learn more, see [Teasers - Coming Soon])
 7. Save it
 
-![conditionalPrice](//images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
+![conditionalPrice](https://images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
diff --git a/docs/tutorials/en/how-to-create-the-script-customization-file-for-vtex-instore.md b/docs/tutorials/en/how-to-create-the-script-customization-file-for-vtex-instore.md
index 5863fc4c9..0b8c39eb4 100644
--- a/docs/tutorials/en/how-to-create-the-script-customization-file-for-vtex-instore.md
+++ b/docs/tutorials/en/how-to-create-the-script-customization-file-for-vtex-instore.md
@@ -17,20 +17,20 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 
 To create the customization file, access the Portal through the topbar and create a new file named `checkout-instore-custom.js` This file will be loaded by inStore automatically. 
 
-![topbar-portal](//images.contentful.com/alneenqid6w5/2Xenr5P0EMKCAyOq2Qmiaw/98fa99c841313072099b11553785660e/topbar-portal.png)
+![topbar-portal](https://images.contentful.com/alneenqid6w5/2Xenr5P0EMKCAyOq2Qmiaw/98fa99c841313072099b11553785660e/topbar-portal.png)
 
 Open the Portal module and click on the button to edit the default site.  In the example below, the store’s accountname is  __Omniera__.
 
-![portal-default-website](//images.contentful.com/alneenqid6w5/7GHyB8nH6o62e4MWsskgCI/e5066603fe42d311f30b47055cca9cbf/portal-default-website.png)
+![portal-default-website](https://images.contentful.com/alneenqid6w5/7GHyB8nH6o62e4MWsskgCI/e5066603fe42d311f30b47055cca9cbf/portal-default-website.png)
 
 Then, click on the `Code` tag, and on the `New` button to select the option for a new `File`.
 
-![portal-add-file](//images.contentful.com/alneenqid6w5/1qDZc7Yj6wyaAkIaIEMEeI/461efb062c3cc02c11084908bbb01ecc/portal-add-file.png)
+![portal-add-file](https://images.contentful.com/alneenqid6w5/1qDZc7Yj6wyaAkIaIEMEeI/461efb062c3cc02c11084908bbb01ecc/portal-add-file.png)
 
 Enter the `checkout-instore-custom.js` file name, and click on `Create`.
 
-![portal-add-file-filename](//images.contentful.com/alneenqid6w5/6vdp46Cv0AgG6caSgQOe2i/3026dfc7f1de5e7b828863b5435a99c1/portal-add-file-filename.png)
+![portal-add-file-filename](https://images.contentful.com/alneenqid6w5/6vdp46Cv0AgG6caSgQOe2i/3026dfc7f1de5e7b828863b5435a99c1/portal-add-file-filename.png)
 
 Now you can add the file content and save it.  inStore will load the customization file automatically. 
 
-![portal-edit-file](//images.contentful.com/alneenqid6w5/7HxG61bw1aW0yuK6OIycyU/dde5f00b9aeec4bbc05b7b18ebd1b0f3/portal-edit-file.png)
+![portal-edit-file](https://images.contentful.com/alneenqid6w5/7HxG61bw1aW0yuK6OIycyU/dde5f00b9aeec4bbc05b7b18ebd1b0f3/portal-edit-file.png)
diff --git a/docs/tutorials/en/how-to-customize-a-page-using-placeholders.md b/docs/tutorials/en/how-to-customize-a-page-using-placeholders.md
index 66b3998f1..faf52d8f1 100644
--- a/docs/tutorials/en/how-to-customize-a-page-using-placeholders.md
+++ b/docs/tutorials/en/how-to-customize-a-page-using-placeholders.md
@@ -39,9 +39,9 @@ Please remember that `htmlSeo` is the name of the control created above. This
 
 **Examples**
 
-![](//images.contentful.com/alneenqid6w5/5LY7pZwZpe8iQiWccqCc26/d4c10dc57a8f6091dd5c23ec3fdad12e/2016-04-05_17_15_29-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5LY7pZwZpe8iQiWccqCc26/d4c10dc57a8f6091dd5c23ec3fdad12e/2016-04-05_17_15_29-Index.png)
 
-![](//images.contentful.com/alneenqid6w5/45kPL4QTfqMkYuAYQEeuC2/aed1934b3268ccb8310226e0e6ce9ff3/2016-04-05_17_15_58-Index.png)
+![](https://images.contentful.com/alneenqid6w5/45kPL4QTfqMkYuAYQEeuC2/aed1934b3268ccb8310226e0e6ce9ff3/2016-04-05_17_15_58-Index.png)
 
 **Note.:** Placeholders can be applied in different manners, as long as they comply with the place and the format, that is, the store owner’s needs.
 
@@ -51,21 +51,21 @@ To include a description for the Category (Categoria), follow the steps below:
 
 1. Go to Configurações > Portal
 2. Click on Portal > Web-sites > [nomedaloja] > / > categoria > @categoria@ > categoria
-![](//images.contentful.com/alneenqid6w5/5IrVEkqOlyy644oAwGS0Ou/b82465f649790ab7bbbce5ea4d416265/2016-04-05_16_21_49-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5IrVEkqOlyy644oAwGS0Ou/b82465f649790ab7bbbce5ea4d416265/2016-04-05_16_21_49-Index.png)
 3. Go to the **Configurações** tab
-![](//images.contentful.com/alneenqid6w5/bhebyo6cBaKy2wa8O4moA/fe1f57b2ef00101ba21effb442206043/2016-04-05_16_25_11-Index.png)
+![](https://images.contentful.com/alneenqid6w5/bhebyo6cBaKy2wa8O4moA/fe1f57b2ef00101ba21effb442206043/2016-04-05_16_25_11-Index.png)
 4. Click on **Adicionar Controle**
 5. Choose the type of control of your preference, in general, HTML.
-![](//images.contentful.com/alneenqid6w5/42vmuVKKdWSwcc0gsuwimi/91fe4618316504de9ea0fb385e46df6b/2016-04-05_16_34_31-Index.png)
+![](https://images.contentful.com/alneenqid6w5/42vmuVKKdWSwcc0gsuwimi/91fe4618316504de9ea0fb385e46df6b/2016-04-05_16_34_31-Index.png)
 6. Click on **Adicionar**
 7. Click on **Salvar Configurações**
 8. Click on **Editar**
 9. Click on **Adicionar Conteúdo**
-![](//images.contentful.com/alneenqid6w5/6Ou1gOdTZCWKqIwUA682C6/6f241a6ad96fc83cf6830622ababe08f/2016-04-05_16_34_58-Index.png)
+![](https://images.contentful.com/alneenqid6w5/6Ou1gOdTZCWKqIwUA682C6/6f241a6ad96fc83cf6830622ababe08f/2016-04-05_16_34_58-Index.png)
 10. Create the HTML that you want to be seen on the website.
 11. In the **Preview** tab, you can see a preview of the HTML.
 12. The **Condições de Exibição** fields can be set up according to your needs, for example, select a Category in which the contents will be made available.
 13. Click on the **Conteúdo Ativo** checkbox
 14. Click on **Adicionar na Lista de Conteúdo**
-![](//images.contentful.com/alneenqid6w5/5tqciHrAD6aAgiSIwiKSKE/8ba1d1a683c168257e16dd949133809b/2016-04-05_16_28_19-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5tqciHrAD6aAgiSIwiKSKE/8ba1d1a683c168257e16dd949133809b/2016-04-05_16_28_19-Index.png)
 15. Click on **Salvar Configurações**
diff --git a/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md b/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md
index a5a2df870..f47edb331 100644
--- a/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md
+++ b/docs/tutorials/en/how-to-customize-the-checkout-ui-custom-in-the-admin.md
@@ -63,24 +63,24 @@ In this tab, you can configure the following:
 
 The Colors tab allows you to customize the checkout colors in your store, including backgrounds, buttons, text, and more. This standardization ensures consistent design.
 
-![Colors](//images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/82c33725eabb61f10ba13b8d2406e4d8/Colors_-_EN.png)
+![Colors](https://images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/82c33725eabb61f10ba13b8d2406e4d8/Colors_-_EN.png)
 
 ## JavaScript
 
 The JavaScript tab adds an additional layer of customization to the interface by allowing you to add scripts.
 
-![Java - EN](//images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/045facf9e300f701eb07395dbfbb1570/Java_-_EN.png)
+![Java - EN](https://images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/045facf9e300f701eb07395dbfbb1570/Java_-_EN.png)
 
 ## CSS
 
 The CSS tab allows the store layout customization by adding CSS code.
 
-![CSS - EN](//images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/6911348bbacbba2fee4c7bc0bfd8a1df/CSS_-_EN.png)
+![CSS - EN](https://images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/6911348bbacbba2fee4c7bc0bfd8a1df/CSS_-_EN.png)
 
 ## History
 
 It allows you to view and restore previously created and published customizations.
 
-![Histórico - EN](//images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/85741110e6bd7c7ad0914adce2124bcb/Hist_rico_-_EN.png)
+![Histórico - EN](https://images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/85741110e6bd7c7ad0914adce2124bcb/Hist_rico_-_EN.png)
 
 To ensure that your configuration is successfully applied, complete the necessary settings and click `Publish`.
diff --git a/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
index 1694aead9..d5cf9adb3 100644
--- a/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
@@ -23,7 +23,7 @@ You can change the **textLink** of existing products anytime in the VTEX Admin,
 
 Check out the [Filling rules](#filling-rules) section to understand the restrictions on this field.
 
-![textlink.en](//images.ctfassets.net/alneenqid6w5/2FDLvlMqvZNRCAiCoFNbfB/3485de69b69d5245045063e617177c70/textlink.en.png)
+![textlink.en](https://images.ctfassets.net/alneenqid6w5/2FDLvlMqvZNRCAiCoFNbfB/3485de69b69d5245045063e617177c70/textlink.en.png)
 
 <div class="alert alert-info">
   <p>You can also change a product's page URL using the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview">Catalog API</a>. In this case, you must change the field <code>LinkId</code>. See <a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product">Update Product</a> for more information.</p>
diff --git a/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md b/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md
index 7cafe8dac..a6d914239 100644
--- a/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md
+++ b/docs/tutorials/en/how-to-deprecate-and-undeprecate-your-app.md
@@ -19,4 +19,4 @@ In the unfortunate event that you need to rollback your app to the previous vers
 
 If you realize that the deprecation was unecessary and need to republish highest version of your app, you can run `vtex undeprecate`.
 
-![image (2)](//images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
+![image (2)](https://images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
diff --git a/docs/tutorials/en/how-to-disable-a-transactional-email.md b/docs/tutorials/en/how-to-disable-a-transactional-email.md
index abb4f3f0b..6909688ee 100644
--- a/docs/tutorials/en/how-to-disable-a-transactional-email.md
+++ b/docs/tutorials/en/how-to-disable-a-transactional-email.md
@@ -28,7 +28,7 @@ Proceed with the following steps:
 3. Type in __Payment Pending__ in the search box.
 4. Uncheck the __Enable email sending__ option.
 
-  ![Message Center - Desativar - EN](//images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d09c9060f369f1f0dbe90706047d8bc3/dlSCQPRLKf46SnYGl7X9a_EN_Payment_Pending.jpg)
+  ![Message Center - Desativar - EN](https://images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d09c9060f369f1f0dbe90706047d8bc3/dlSCQPRLKf46SnYGl7X9a_EN_Payment_Pending.jpg)
 
 5. Click on __Save__.
 
diff --git a/docs/tutorials/en/how-to-download-the-vtex-invoices.md b/docs/tutorials/en/how-to-download-the-vtex-invoices.md
index 6bce905d5..5590cdd81 100644
--- a/docs/tutorials/en/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/en/how-to-download-the-vtex-invoices.md
@@ -46,7 +46,7 @@ To download your invoice, follow the steps below:
 
 The invoice will then be appear in another tab.
 
-![baixar faturas en](//images.ctfassets.net/alneenqid6w5/4kge4ovIXcBv8EYizjg2ro/cd75e5882e47da9114a87979c13c1f9b/baixar_faturas_en.gif)
+![baixar faturas en](https://images.ctfassets.net/alneenqid6w5/4kge4ovIXcBv8EYizjg2ro/cd75e5882e47da9114a87979c13c1f9b/baixar_faturas_en.gif)
 
 ## Brazil 
 
@@ -66,7 +66,7 @@ To download your "boleto", follow the steps below:
 
 <div class="alert alert-info">In Brazil, a purple invoice can indicate that it is overdue but that a new "boleto" with an upcoming due date has already been issued. In such cases, the invoice will continue as overdue until it's paid. If no payment is made, the invoice color will switch to red again.</div>
 
-![baixar boletos en](//images.ctfassets.net/alneenqid6w5/4NxkYNfPImdKOMzCkuUAmp/4e545d21ada8b602c02ea337ff209d40/baixar_boletos_en.gif)
+![baixar boletos en](https://images.ctfassets.net/alneenqid6w5/4NxkYNfPImdKOMzCkuUAmp/4e545d21ada8b602c02ea337ff209d40/baixar_boletos_en.gif)
 
 ### Download "Nota Fiscal"
 
@@ -83,7 +83,7 @@ The Nota Fiscal will be opened in another tab on your browser. Click on **Print
 1. In the Save as option, select **Save as PDF**.
 2. To conclude, click on **Save**.
 
-![baixar notafiscal en](//images.ctfassets.net/alneenqid6w5/2LhJUKdHjNziL9OXoqvWQg/cbe309a9e1695dc74b7345e74c80882b/baixar_notafiscal_en.gif)
+![baixar notafiscal en](https://images.ctfassets.net/alneenqid6w5/2LhJUKdHjNziL9OXoqvWQg/cbe309a9e1695dc74b7345e74c80882b/baixar_notafiscal_en.gif)
 
 If you have questions about the amount charged on the invoice, read the article on [understanding the value of approved revenues](https://help.vtex.com/tutorial/understanding-the-value-of-approved-revenues--tutorials_4322).
 
diff --git a/docs/tutorials/en/how-to-find-an-sku-id.md b/docs/tutorials/en/how-to-find-an-sku-id.md
index b4170cf90..53cc025b8 100644
--- a/docs/tutorials/en/how-to-find-an-sku-id.md
+++ b/docs/tutorials/en/how-to-find-an-sku-id.md
@@ -34,7 +34,7 @@ To find the ID of a SKU through the VTEX Admin, follow the steps below:
 
 In the example below, the SKU ID is __18__.
 
-![skuId-1](//images.contentful.com/alneenqid6w5/3CEFOn0h8Ac6ciGgi6gmEK/2d64944b8added0ec12d5cdc7ebe9d9c/skuId-1.png)
+![skuId-1](https://images.contentful.com/alneenqid6w5/3CEFOn0h8Ac6ciGgi6gmEK/2d64944b8added0ec12d5cdc7ebe9d9c/skuId-1.png)
 
 ## SKU registration URL
 
diff --git a/docs/tutorials/en/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md b/docs/tutorials/en/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
index f61d6365c..644ac4711 100644
--- a/docs/tutorials/en/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
+++ b/docs/tutorials/en/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
@@ -19,17 +19,17 @@ This article will help you complement your URL mapping. If your store did not se
 
 Access your Google Web Master Tools account. On this screen, you will already be able to check the numbers of pages that contain errors.
 
-![locateURL1](//images.contentful.com/alneenqid6w5/qEYJuUx2hweIuuMCsQWmE/4667542aeafdfd92daecce10dd7853a6/locateURL1.jpg)
+![locateURL1](https://images.contentful.com/alneenqid6w5/qEYJuUx2hweIuuMCsQWmE/4667542aeafdfd92daecce10dd7853a6/locateURL1.jpg)
 
 Click on **Tracking** and then on **Tracking Errors** as shown below:
 
-![locateURL2](//images.contentful.com/alneenqid6w5/2bcdyY8KJqO6EwQOMKys8k/61845c81da0a9718bb46b9df40dff91c/locateURL2.jpg)
+![locateURL2](https://images.contentful.com/alneenqid6w5/2bcdyY8KJqO6EwQOMKys8k/61845c81da0a9718bb46b9df40dff91c/locateURL2.jpg)
 
 In this area, you will be able to view when the error occurred, the corresponding URL, and the type of error. Now, you will be able to export a worksheet (\*.csv).
 
-![locateURL3](//images.contentful.com/alneenqid6w5/5pmI5i6RFK4Icku40ua22S/43135af03b16a77ca55bdc3fb53207ea/locateURL3.jpg)
-![locateURL4](//images.contentful.com/alneenqid6w5/6QLDHdNJpCgWgAM6eO8QEi/8f5f07ce59f07c34cefa48b893767ac4/locateURL4.jpg)
+![locateURL3](https://images.contentful.com/alneenqid6w5/5pmI5i6RFK4Icku40ua22S/43135af03b16a77ca55bdc3fb53207ea/locateURL3.jpg)
+![locateURL4](https://images.contentful.com/alneenqid6w5/6QLDHdNJpCgWgAM6eO8QEi/8f5f07ce59f07c34cefa48b893767ac4/locateURL4.jpg)
 
 You will be able to include these links in the worksheet by referring to Home or collection, whichever is more appropriate to your store. After correcting these links, go back to the Web Master Tools and click on **Tracking** and then on **Tracking Errors**.
 
-![locateURL5](//images.contentful.com/alneenqid6w5/54CtZsR9SM2Q8QSEoUaUmy/6a77ef45455da13bb84c8ce005ddaa29/locateURL5.jpg)
+![locateURL5](https://images.contentful.com/alneenqid6w5/54CtZsR9SM2Q8QSEoUaUmy/6a77ef45455da13bb84c8ce005ddaa29/locateURL5.jpg)
diff --git a/docs/tutorials/en/how-to-identify-a-page-template.md b/docs/tutorials/en/how-to-identify-a-page-template.md
index 4ca1cdeb3..51901207e 100644
--- a/docs/tutorials/en/how-to-identify-a-page-template.md
+++ b/docs/tutorials/en/how-to-identify-a-page-template.md
@@ -27,7 +27,7 @@ VTEX uses the same principle. The directory (folder) is where all the informatio
 
 We can create any number of templates but we have to specify in the directory which template is to be exhibited. Using the __Account__ page as an example:
 
-![cms-template-pagina EN](//images.ctfassets.net/alneenqid6w5/4Zu301bdyU2EsSIK0aGycG/1118a06dfeed0f9e11f6669c1bdef337/Produto_CMS_EN.png)
+![cms-template-pagina EN](https://images.ctfassets.net/alneenqid6w5/4Zu301bdyU2EsSIK0aGycG/1118a06dfeed0f9e11f6669c1bdef337/Produto_CMS_EN.png)
 
 Storefront > Layout > CMS Foulder > Sites and channels > Account Name > (/) Foulder > Account *(following the example)* > Click on the link with the red "ok" arrow.
 
@@ -39,13 +39,13 @@ To make this more flexible, it is also possible to include subtemplates and any
 
 Now a real example: I want to know what page I am browsing on right now:
 
-![página-loja EN](//images.ctfassets.net/alneenqid6w5/8rd8A3NxvOeaSYqqa2Wyy/75863ff3536180f32ed8388435175940/exemplo_loja_em_ingles.png)
+![página-loja EN](https://images.ctfassets.net/alneenqid6w5/8rd8A3NxvOeaSYqqa2Wyy/75863ff3536180f32ed8388435175940/exemplo_loja_em_ingles.png)
 
 The domain itself often helps me identify it, but some stores may customize this, making this identification more difficult. If I am unsure if I am on a __Departament__ or __Category__ page, this may well be that the shelf has been customized. 
 
 The best way is checking the Source Code for the page (Ctrl + U). VTEX stores will have an indication of the directory to which the page belongs.
 
-![template-cms-exemplo en](//images.ctfassets.net/alneenqid6w5/emC1qyMArCYWKcKg0M2UM/3cb37ecc2ae2f01f265d8b4dd25cbfff/exemplo_loja_em_ingles_PRODUCT.png)
+![template-cms-exemplo en](https://images.ctfassets.net/alneenqid6w5/emC1qyMArCYWKcKg0M2UM/3cb37ecc2ae2f01f265d8b4dd25cbfff/exemplo_loja_em_ingles_PRODUCT.png)
 
 In the example above: `<!-- CommerceContext.Current.VirtualFolder.Name: @Produto@ -->`
 Now that we know that it is a category page, we have to find out which template is active for Categoria. To this, you need only repeat the process described in the previous example.
diff --git a/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md b/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md
index 0e57909d6..f7418b7fb 100644
--- a/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md
+++ b/docs/tutorials/en/how-to-identify-layout-errors-caused-by-javascript-files.md
@@ -26,7 +26,7 @@ To do so, follow the steps below:
 1. To disable the JS of the page, just add `/tools.html` at the end of the URL. E.g.: {AccountName}.myvtex.com/tools.html
 2. Click on __Disable__ in the __Client JavaScript is__ tab. 
 
-![javascript-disable ](//images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
+![javascript-disable ](https://images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
 
 3. Next, remove `/tools.html` from the URL and update the page.
 
diff --git a/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
index f873ef416..5af3d1c78 100644
--- a/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
@@ -42,7 +42,7 @@ In the cart, you can move your mouse over the question mark icon below the price
 
 However, if more than one promotion is applied, what appears will be the sum of the discounts, making it difficult to analyze the scenario.
 
-![example-cart](//images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/324846b73794d9a19305cfb4d9486ab1/image6.png)
+![example-cart](https://images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/324846b73794d9a19305cfb4d9486ab1/image6.png)
 
 ## orderForm
 
@@ -58,7 +58,7 @@ Follow the step-by-step instructions to find the `orderForm` and identify the pr
 2. Click on `Network`.
 3. Check the **Preserve log** option.
 4. Reload the page.
-5. After loading, press `Ctrl+F` to perform the search in the **Developer Tools**. Type `orderForm` in the search bar. ![order-form](//images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
+5. After loading, press `Ctrl+F` to perform the search in the **Developer Tools**. Type `orderForm` in the search bar. ![order-form](https://images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
 6. Click on the `orderForm` line. A new window will open next to it.
 7. Click on `Preview`.
 8. Search for `ratesAndBenefitsData` and click on the item.
diff --git a/docs/tutorials/en/how-to-identify-promotions-attributed-to-an-sku.md b/docs/tutorials/en/how-to-identify-promotions-attributed-to-an-sku.md
index a4bc982ab..bd4dd8ca8 100644
--- a/docs/tutorials/en/how-to-identify-promotions-attributed-to-an-sku.md
+++ b/docs/tutorials/en/how-to-identify-promotions-attributed-to-an-sku.md
@@ -24,12 +24,12 @@ We have written this article in response to a frequent query from users of the V
 To find out what promotions are being attributed to an SKU, we have to analyze its `priceTags`.
 
 1. Go to the product shopping cart.
-2. In Google Chrome, go to **Developer Tools** (`Ctrl+Shift+I`).![ferramentas-do-desenvolvedor](//images.contentful.com/alneenqid6w5/3NBGEPjXEkkSqA2WOYs8us/5219ffe6515a120ac0e6d489c78e5820/ferramentas-do-desenvolvedor.png)
-3. Select the tab **Network** and press `F5` to record the reload.![network-f5](//images.contentful.com/alneenqid6w5/1TZRay17qkEO8As8w0MKOS/f4d88d06f2a3fd656aa41e3809f35d45/network-f5.png)
-4. After loading, press `Ctrl+F` to search in the Developer Tools window, and look for “orderform”. ![order-form](//images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
-5. Click on `orderform` and go to `items` After clicking on `items`, click on the numbers (`0`, `1`, `2` etc.) to see the details of the product you want. In our example, since there is only one item, it is represented by the number `0` in the array.![items-0](//images.contentful.com/alneenqid6w5/DUtSiCdnrwSmoKqqYW8E6/ec7335a0c9308b17b9d8aa2274057220/items-0.png)
-6. After clicking on the  number, scroll down to `priceTags` Click on `priceTags` and then on the numbers (`0`, `1`, `2` etc.) to see the details of the promotion you want. In our example, since there is only one promotion, it is represented by the number `0` in the array. After this, look for the `identifier` of the promotion.![priceTags-0-identifier](//images.contentful.com/alneenqid6w5/5MCOrSJPaMSYQcimY8CKos/ca8960a1a98f680406daf7879d241987/priceTags-0-identifier.png)
-7. Open another tab, and go to URL `https://{accountName}.vtexcommercestable.com.br/admin/rnb/#/benefit/{identifier}`. This is the promotion that is being applied to the product in the cart. Check the configurations of the promotion and see whether the conditions apply to the SKU in question.![promo-debug-help](//images.contentful.com/alneenqid6w5/5G2eJ4AilySK0o8ugaOMq4/b4dba231e9812906a45af5a4432d9783/promo-debug-help.png)
+2. In Google Chrome, go to **Developer Tools** (`Ctrl+Shift+I`).![ferramentas-do-desenvolvedor](https://images.contentful.com/alneenqid6w5/3NBGEPjXEkkSqA2WOYs8us/5219ffe6515a120ac0e6d489c78e5820/ferramentas-do-desenvolvedor.png)
+3. Select the tab **Network** and press `F5` to record the reload.![network-f5](https://images.contentful.com/alneenqid6w5/1TZRay17qkEO8As8w0MKOS/f4d88d06f2a3fd656aa41e3809f35d45/network-f5.png)
+4. After loading, press `Ctrl+F` to search in the Developer Tools window, and look for “orderform”. ![order-form](https://images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
+5. Click on `orderform` and go to `items` After clicking on `items`, click on the numbers (`0`, `1`, `2` etc.) to see the details of the product you want. In our example, since there is only one item, it is represented by the number `0` in the array.![items-0](https://images.contentful.com/alneenqid6w5/DUtSiCdnrwSmoKqqYW8E6/ec7335a0c9308b17b9d8aa2274057220/items-0.png)
+6. After clicking on the  number, scroll down to `priceTags` Click on `priceTags` and then on the numbers (`0`, `1`, `2` etc.) to see the details of the promotion you want. In our example, since there is only one promotion, it is represented by the number `0` in the array. After this, look for the `identifier` of the promotion.![priceTags-0-identifier](https://images.contentful.com/alneenqid6w5/5MCOrSJPaMSYQcimY8CKos/ca8960a1a98f680406daf7879d241987/priceTags-0-identifier.png)
+7. Open another tab, and go to URL `https://{accountName}.vtexcommercestable.com.br/admin/rnb/#/benefit/{identifier}`. This is the promotion that is being applied to the product in the cart. Check the configurations of the promotion and see whether the conditions apply to the SKU in question.![promo-debug-help](https://images.contentful.com/alneenqid6w5/5G2eJ4AilySK0o8ugaOMq4/b4dba231e9812906a45af5a4432d9783/promo-debug-help.png)
 
 ## Learn more
 
diff --git a/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
index 45ec9c276..01a05e5ca 100644
--- a/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
@@ -17,7 +17,7 @@ subcategory: 1c5Btie9ou2Gg2iUo0ggqM
 
 Pickup points are a very important aspect of any [omnichannel](/en/announcement/shift-your-business-with-vtexs-omnichannel-experience) strategy.
 
-You can [setup pickup points one by one](/en/tutorial/registering-pickup-points) or in bulk, through an XLS spreadsheet [(like this example file)](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). By choosing to upload an XLS file, you can register all your pickup points at once (as long as it doesn't exceed 10 MB).
+You can [setup pickup points one by one](/en/tutorial/registering-pickup-points) or in bulk, through an XLS spreadsheet [(like this example file)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). By choosing to upload an XLS file, you can register all your pickup points at once (as long as it doesn't exceed 10 MB).
 
 <div class="alert alert-info">
 A <strong>10 MB</strong> XLS file allows you to register an average <strong>50.000 pickup points</strong>. If you have more pickup points to import, you'll need to split them into different spreadsheets and upload them separately.
@@ -28,8 +28,8 @@ A <strong>10 MB</strong> XLS file allows you to register an average <strong>50.0
 ## How to upload the spreadsheet
 1. Click on __Inventory & shipping__, on the __Orders__ section of the sidebar.
 2. On the options that open up, click on __Pickup points__.
-3. Click on the __Upload an XLS__ link, located on the top-right corner of the page. ![Upload XLS](//images.ctfassets.net/alneenqid6w5/4rUkTvzcqso46aGcsOYwMc/e8cf57f6c1ee560062dc8c1bfd7767ba/Upload_XLS.png)
-4. A modal window will appear, allowing you to upload your `.xls` extension file or to download the [example spreadsheet](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Remember that it comes with lines filled with example values, so you must replace them with your pickup points' actual data. ![modal (EN)](//images.ctfassets.net/alneenqid6w5/52EN8SmteU0kQK4U0YKy8a/1129dc87228d86800e06b455d5ccddf2/modal__EN_.png)
+3. Click on the __Upload an XLS__ link, located on the top-right corner of the page. ![Upload XLS](https://images.ctfassets.net/alneenqid6w5/4rUkTvzcqso46aGcsOYwMc/e8cf57f6c1ee560062dc8c1bfd7767ba/Upload_XLS.png)
+4. A modal window will appear, allowing you to upload your `.xls` extension file or to download the [example spreadsheet](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Remember that it comes with lines filled with example values, so you must replace them with your pickup points' actual data. ![modal (EN)](https://images.ctfassets.net/alneenqid6w5/52EN8SmteU0kQK4U0YKy8a/1129dc87228d86800e06b455d5ccddf2/modal__EN_.png)
 5. With all set, your new pickup points will be available to your clients.
 
 
diff --git a/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md
index 67ce0c68e..ceeb40150 100644
--- a/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/en/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -27,30 +27,30 @@ After the proper definitions, the collection is linked to the shop window at **S
 
 In the example below, we will define a shop window shown on the Home page. Therefore, select **Settings**, then **add object**, as in the following image.
 
-![coleção2](//images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
+![coleção2](https://images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
 
 This command will open the **Visual Controls**, that correspond to the showcase where you want to display the collection. Add a _Collection_, but be sure to set a name for it.
 
-![coleção3](//images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
+![coleção3](https://images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
 
-![coleção4](//images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
+![coleção4](https://images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
 
 Remember to save the settings so that you can edit the control created.
 
-![coleção5](//images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
+![coleção5](https://images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
 
-![coleção6](//images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
+![coleção6](https://images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
 
 To edit the control, it is necessary to add its contents, which represent each set of items to be displayed.
 Are they:
 _Layout_: Select the shelf template used in the showcase.
 _Number of Columns, Number of Items, Show Unavailable_ and _Ramdom ad Paged_: Define the layout, quantity, and the criteria for displaying the items.
 
-![coleção7](//images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
+![coleção7](https://images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
 
 Remember to save your changes before you search or change pages.
 The next step is to add the content by selecting **Add Content**.
-![coleção8](//images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
+![coleção8](https://images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
 
 It is possible to define each content by using collections or search results, by using search parameters (further details [here](/en/tutorial/search-parameters "here"))
 
@@ -60,7 +60,7 @@ _QueryString_: The parameters entered in this field define the search result tha
 
 In the **Product Cluster (Collection)** field, you must select the collection that will be displayed by completing the following step:
 
-![coleção10](//images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
+![coleção10](https://images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
 
 The contents to be filled in the **Display Condition** part:
 _Partner, Campaign_ and _Source_: Define the display of this content if the visitor has a corresponding UTM in its source URL.
@@ -72,7 +72,7 @@ After the settings, check **Active Content** and add to the content list, saving
 
 The example below shows a standard shop window, with no display conditions, and another one exclusive for visits arising from Google sponsored campaign audiences (utm_source=**google**/utm_medium=**cpc**): 
 
-![coleção9](//images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
+![coleção9](https://images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
 
 In the scenario above, if the customer came from the sponsored campaign audience, the products corresponding to the result of a search for ID 200000 Brand will be displayed on the **Lançamentos** shop window, located on Home; otherwise, the products corresponding to ID 8 collection will be displayed.
 
diff --git a/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md b/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
index c517655fe..4afcf80b1 100644
--- a/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
+++ b/docs/tutorials/en/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
@@ -18,12 +18,12 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 To include metadata when exporting a SKU prices spreadsheet, follow the steps below:
 
 1. Click on **Prices**, in the menu on the left side of the page
-![2019 05 27 18 56 22 Price list.jpg?h=250](//images.ctfassets.net/alneenqid6w5/084YLwZ0JF1ptBlurtbNQ/15c9ed54e664eac0eebd3af720494acb/2019_05_27_18_56_22_Price_list.jpg_h_250)
+![2019 05 27 18 56 22 Price list.jpg?h=250](https://images.ctfassets.net/alneenqid6w5/084YLwZ0JF1ptBlurtbNQ/15c9ed54e664eac0eebd3af720494acb/2019_05_27_18_56_22_Price_list.jpg_h_250)
 2. Click on **Price List**
 3. In the  upper left side of the page, select the **arrow down** button
 4. In the newly opened tab, on the left side, hover over and click on the **Export Prices Spreadsheet** button
 5. A new window will slide onto the screen, mark the box next to **include metadata in exported tables**
 6. Click on the blue **export table** button
-![2019 05 27 18 57 59 Price list.jpg?h=250](//images.ctfassets.net/alneenqid6w5/3fhLCNPgh0gZO03Hwd9doY/a9dca1de548aa67081bbe578ac75d57d/2019_05_27_18_57_59_Price_list.jpg_h_250)
+![2019 05 27 18 57 59 Price list.jpg?h=250](https://images.ctfassets.net/alneenqid6w5/3fhLCNPgh0gZO03Hwd9doY/a9dca1de548aa67081bbe578ac75d57d/2019_05_27_18_57_59_Price_list.jpg_h_250)
 
 You'll receive an email with the exported table shortly.
diff --git a/docs/tutorials/en/how-to-install-the-masterpass-in-the-vtex-app-store.md b/docs/tutorials/en/how-to-install-the-masterpass-in-the-vtex-app-store.md
index 9369e7b74..05222049d 100644
--- a/docs/tutorials/en/how-to-install-the-masterpass-in-the-vtex-app-store.md
+++ b/docs/tutorials/en/how-to-install-the-masterpass-in-the-vtex-app-store.md
@@ -23,7 +23,7 @@ This article will show you the steps required to install the Masterpass extensio
 
 First, go to the **Explore** screen and click on the **Masterpass** extension.
 
-![Extension Store 1](//images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
+![Extension Store 1](https://images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
 
 Then, you will have access to the extension details page, where the following information will be displayed:
 
@@ -38,17 +38,17 @@ To install the Masterpass, just click on the green button on the right side of t
 
 The installation button will lead you to the permissions screen, where you will be able to view all data and locations to which the extension intends to have access. 
 
-![Masterpass1](//images.contentful.com/alneenqid6w5/qxOKuZ9dZY2Gy8osWg26A/f553a03370fb198e8dd38d95bd20bb35/Masterpass1.gif)
+![Masterpass1](https://images.contentful.com/alneenqid6w5/qxOKuZ9dZY2Gy8osWg26A/f553a03370fb198e8dd38d95bd20bb35/Masterpass1.gif)
 
 Once you accept the permissions, the extension will be installed.
 
-![Masterpass2](//images.contentful.com/alneenqid6w5/4rxdPuNq0oO2QuCiMaISAy/e8cca1acea0db1e87a0573b8c23f2013/Masterpass2.png)
+![Masterpass2](https://images.contentful.com/alneenqid6w5/4rxdPuNq0oO2QuCiMaISAy/e8cca1acea0db1e87a0573b8c23f2013/Masterpass2.png)
 
 ## Configuration
 
 For the settings to work correctly, you must complete one setup phase. Just fill out some fields, such as those shown in the image below, and click on **Criar conta**.
 
-![Masterpass3](//images.contentful.com/alneenqid6w5/5XbYGeSd2gy4QEaIiMeqQ0/a20d27e9aa18af9a95767fb604e82d7c/Masterpass3.png)
+![Masterpass3](https://images.contentful.com/alneenqid6w5/5XbYGeSd2gy4QEaIiMeqQ0/a20d27e9aa18af9a95767fb604e82d7c/Masterpass3.png)
 
 ## Preview
 
@@ -58,7 +58,7 @@ The Extension Store will also make available a Masterpass preview environment wh
 
 This environment works as a draft.  Changes made will not affect the production of your store. 
 
-![Masterpass4](//images.contentful.com/alneenqid6w5/7Ki5CoHPvUusGuU4UEE2U4/7d8d02434118b7c3b6c295edc9efbb18/Masterpass4.gif)
+![Masterpass4](https://images.contentful.com/alneenqid6w5/7Ki5CoHPvUusGuU4UEE2U4/7d8d02434118b7c3b6c295edc9efbb18/Masterpass4.gif)
 
 ## Publication
 
@@ -66,4 +66,4 @@ To move the Masterpass to the production environment (where your customers will
 
 To do this, just click on the **Publicar** button on the top bar.
 
-![Extension Store 3 - Publishing](//images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
+![Extension Store 3 - Publishing](https://images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
diff --git a/docs/tutorials/en/how-to-install-the-taxhub.md b/docs/tutorials/en/how-to-install-the-taxhub.md
index cc3264ed8..a23f77693 100644
--- a/docs/tutorials/en/how-to-install-the-taxhub.md
+++ b/docs/tutorials/en/how-to-install-the-taxhub.md
@@ -25,4 +25,4 @@ To install TaxHub, our tax system, follow these steps:
 6.	On the same screen, install your App developed in node.js zipped in .zip format (the file name should be jurisdiction.zip)
 7.	The system will save the file automatically.
 
-![TaxHub Instalation](//images.contentful.com/alneenqid6w5/7LfwQ6CzIIEYqSwmcoUMCG/7508ba6496d5fedb913c85357a8a632e/Instalacion_TaxHub.gif)
+![TaxHub Instalation](https://images.contentful.com/alneenqid6w5/7LfwQ6CzIIEYqSwmcoUMCG/7508ba6496d5fedb913c85357a8a632e/Instalacion_TaxHub.gif)
diff --git a/docs/tutorials/en/how-to-integrate-with-dafiti.md b/docs/tutorials/en/how-to-integrate-with-dafiti.md
index 9fa74fd9a..167bb5605 100644
--- a/docs/tutorials/en/how-to-integrate-with-dafiti.md
+++ b/docs/tutorials/en/how-to-integrate-with-dafiti.md
@@ -55,11 +55,11 @@ With this feature, it is possible to correctly categorize and also create variat
 The mapping should be done every time a product is sent to Dafiti for the first time. This means that, having already concluded the mapping once, the products that were already integrated do not need to repeat this process. At the same time, new products should always undergo mapping.
 
 1. According to __your country__, download the __Dafiti Mapping Spreadsheet__ in `.xlsx` format.
-<br/>&bull; [Brazil](//assets.ctfassets.net/alneenqid6w5/2Vbi7VaYIowaaOYCCucsQq/fa94cd636b38e9810dd6a708c95e26ac/Planilha_de_Mapeamento_da_Dafiti.xlsx)
-<br/>&bull; [Colombia](//assets.ctfassets.net/alneenqid6w5/4d5y0N09IsKmy4MuAGygqs/0e43349d309fb556179dfac5f2f6c885/Planilha_de_Mapeamento_da_Dafiti_COL.xlsx)
+<br/>&bull; [Brazil](https://assets.ctfassets.net/alneenqid6w5/2Vbi7VaYIowaaOYCCucsQq/fa94cd636b38e9810dd6a708c95e26ac/Planilha_de_Mapeamento_da_Dafiti.xlsx)
+<br/>&bull; [Colombia](https://assets.ctfassets.net/alneenqid6w5/4d5y0N09IsKmy4MuAGygqs/0e43349d309fb556179dfac5f2f6c885/Planilha_de_Mapeamento_da_Dafiti_COL.xlsx)
 
 2. Depending on __your country__, download the __Dafiti Query Spreadsheet__ to check the accepted value of each column of the Mapping Spreadsheet from the previous step. This spreadsheet is __exclusively to check__.
-<br/>&bull; [Brazil](//assets.ctfassets.net/alneenqid6w5/1gGYn5lo3qSe0iOaoKs0oa/fc1aa02e2761474f0235fcb489f930ff/Planilha_de_Consulta_Dafiti.xlsx)
+<br/>&bull; [Brazil](https://assets.ctfassets.net/alneenqid6w5/1gGYn5lo3qSe0iOaoKs0oa/fc1aa02e2761474f0235fcb489f930ff/Planilha_de_Consulta_Dafiti.xlsx)
 <br/>&bull; [Colombia](https://s3.amazonaws.com/Marketplace-Integration/SellerCenterIntegration/Colombia.zip)
 
 Follow the steps below, doing the to/from on the __Mapping Spreadsheet__ between what VTEX has registered with regards to your product and the specific values found in the Dafiti __Query Spreadsheet__.
diff --git a/docs/tutorials/en/how-to-manage-subscriptions.md b/docs/tutorials/en/how-to-manage-subscriptions.md
index 1ef0cd6aa..00ef53cfe 100644
--- a/docs/tutorials/en/how-to-manage-subscriptions.md
+++ b/docs/tutorials/en/how-to-manage-subscriptions.md
@@ -35,7 +35,7 @@ The **Unique Subscriptions** section allows you to:
 - View a **dynamic chart** with the *active*, *canceled* and *all* subscriptions within the selected period. By hovering the cursor over the chart lines, you can see in detail the subscriptions variation per day.
 - **Export subscriptions** within the filtered period by clicking on the button in the upper right corner of the screen.
 
- ![EN Dashboard Assinatura única](//images.ctfassets.net/alneenqid6w5/1UiNoDxKut3m9UUbhDBZoa/5d6af9bbfcc2d46e751050f5c848f206/EN_Dashboard_Assinatura___nica.png)
+ ![EN Dashboard Assinatura única](https://images.ctfassets.net/alneenqid6w5/1UiNoDxKut3m9UUbhDBZoa/5d6af9bbfcc2d46e751050f5c848f206/EN_Dashboard_Assinatura___nica.png)
 
 ### Subscription Orders
 
@@ -49,12 +49,12 @@ The **Subscription Orders** section allows you to:
 - Monitor the **absolute number and corresponding percentage** of Subscription Orders that were *scheduled*, *processed*, *generated* and *completed* per period.
 - View a **chart** with the percentage of *skipped* orders, *cycles with an issue* and *payment errors*.
 
-![EN Dashboard Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/hZxhtReMjrrwi4VQl8Pyu/bb2e62f626072108fba24e78db87dc15/EN_Dashboard_Pedidos_Assinatura.png)
+![EN Dashboard Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/hZxhtReMjrrwi4VQl8Pyu/bb2e62f626072108fba24e78db87dc15/EN_Dashboard_Pedidos_Assinatura.png)
 
 - When accessing each tab of the **Subscription Orders** table, you can view the flow and details of the orders that were *skipped*, those that presented *Cycles with an issue*, those that contain a *Payment Error* and the *Completed* orders. 
 - In addition to listing the details of the errors that occurred during the  Subscription orders flow, it is also possible to perform a **manual retry** of orders with errors. Check out our article on [Troubleshooting of Subscription orders issues](https://help.vtex.com/tutorial/como-solucionar-pedidos-de-assinatura-com-erros--uLL8AYBGdtAmbbdL5gRCf) to learn more.
 
-![EN Log Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/X9H4zlZTb6t7hpAKvbJ7L/9592cb74a6690ea5c76001bfa0218c33/EN_Log_Pedidos_Assinatura.png)
+![EN Log Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/X9H4zlZTb6t7hpAKvbJ7L/9592cb74a6690ea5c76001bfa0218c33/EN_Log_Pedidos_Assinatura.png)
 
 ### Subscribers
 
diff --git a/docs/tutorials/en/how-to-manage-the-kit-stock.md b/docs/tutorials/en/how-to-manage-the-kit-stock.md
index 7e37d9401..1297e3874 100644
--- a/docs/tutorials/en/how-to-manage-the-kit-stock.md
+++ b/docs/tutorials/en/how-to-manage-the-kit-stock.md
@@ -27,7 +27,7 @@ The kit with components is the idea of a kit product whose SKU is a "cluster" of
 
 For example, a kit product called Colorido is composed by other 10 SKUs. Each, with its required amount of 1 (one) SKU item to compose the kit.
 
-![](//images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
+![](https://images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
 
 So, if there is at least 1 (one) unit of each component in stock, the kit will be considered in stock, as it depends on the stock quantities registered for each of its components.
 
diff --git a/docs/tutorials/en/how-to-manually-invoice-an-order.md b/docs/tutorials/en/how-to-manually-invoice-an-order.md
index 430b759c2..00135b12e 100644
--- a/docs/tutorials/en/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/en/how-to-manually-invoice-an-order.md
@@ -34,7 +34,7 @@ To send the invoice via VTEX Admin, follow the steps below:
 2. Search for the order by using the search bar [or the filters](https://help.vtex.com/en/tutorial/como-filtrar-pedidos--tutorials_192).  
 3. Click the desired order.     
 4. Scroll down to the Invoice to items section, and click on the arrow icon <i class="fas fa-chevron-right"></i> to expand.  
-![Itens faturarEN](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
+![Itens faturarEN](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
 5. Click the `Invoice` button. 
 6. Click the desired billing option:      
     * **Submit invoice referencing items:** to invoice the order referencing the package items.  
@@ -64,7 +64,7 @@ To send the invoice via VTEX Admin, follow the steps below:
 
 After the order is `Invoiced`, go to the **Invoice** section to check the invoices added, as shown in the image below:
 
-![FaturaEN](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
+![FaturaEN](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
 
 For [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe), when [changing or removing items from an order](https://help.vtex.com/en/tutorial/how-to-change-order-items--7jekq618QxgbsOxKkXBjE8), the order total will be updated after invoicing and will correspond to what is captured by the VTEX payment gateway.
 
diff --git a/docs/tutorials/en/how-to-register-a-store-in-vtex-instore.md b/docs/tutorials/en/how-to-register-a-store-in-vtex-instore.md
index 8db392840..9c1303ca7 100644
--- a/docs/tutorials/en/how-to-register-a-store-in-vtex-instore.md
+++ b/docs/tutorials/en/how-to-register-a-store-in-vtex-instore.md
@@ -30,7 +30,7 @@ This guidebook will help you customize your store settings, so that it can run b
 
 When opened for the first time, the application will ask for the name of the store that will be used. Based on the table below, just type in the name of your store, and the settings will be loaded to the app.
 
-![instore-identificacao-loja](//images.contentful.com/alneenqid6w5/20IMJOo5Kc8Kw4OqicCQyc/8a76ed7d6c16d6b269518d430998ec44/instore-identificacao-loja.png)
+![instore-identificacao-loja](https://images.contentful.com/alneenqid6w5/20IMJOo5Kc8Kw4OqicCQyc/8a76ed7d6c16d6b269518d430998ec44/instore-identificacao-loja.png)
 
 ### How to register a physical store
 
@@ -40,14 +40,14 @@ To manage the registration of your physical stores, simply access your Masterdat
 
 * If you are not able to find this application, it means that your environment has not been set up correctly. In this case, we recommend using the environment settings tutorial for use by inStore.*
 
-![masterdata-home-loja](//images.contentful.com/alneenqid6w5/2uBujqshwgCUkKkeEKWaEU/121417a9d25e998c8bb7a29f85ab1830/masterdata-home-loja.png)
+![masterdata-home-loja](https://images.contentful.com/alneenqid6w5/2uBujqshwgCUkKkeEKWaEU/121417a9d25e998c8bb7a29f85ab1830/masterdata-home-loja.png)
 
 By clicking on “listar”, a list of registered stores will be displayed as shown in the image below. Click on “Novo” to register a new store.
 
-![cadastrar-loja](//images.contentful.com/alneenqid6w5/2UxKo2u6CsEagsIYuo8Emy/8c922392c6f0b9373f497575af2cefaf/cadastrar-loja.png)
+![cadastrar-loja](https://images.contentful.com/alneenqid6w5/2UxKo2u6CsEagsIYuo8Emy/8c922392c6f0b9373f497575af2cefaf/cadastrar-loja.png)
 
 Fill out the form with the store’s data and click on “salvar”. 
 
-![cadastrar-loja-formulario](//images.contentful.com/alneenqid6w5/3t3edGHxuo8WoYqkeYmIou/98d23008f916793e6cab618e33905dc2/cadastrar-loja-formulario.png)
+![cadastrar-loja-formulario](https://images.contentful.com/alneenqid6w5/3t3edGHxuo8WoYqkeYmIou/98d23008f916793e6cab618e33905dc2/cadastrar-loja-formulario.png)
 
 Done!  Your store is registered! 😃 Now you can continue to register the salespersons! See [here](/en/tutorial/how-to-register-your-salespersons-on-vtex-instore) how to do this.
diff --git a/docs/tutorials/en/how-to-request-receivables-anticipation.md b/docs/tutorials/en/how-to-request-receivables-anticipation.md
index 56edb8f7b..36af65e58 100644
--- a/docs/tutorials/en/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/en/how-to-request-receivables-anticipation.md
@@ -31,7 +31,7 @@ Now that you have checked the balance, it is important to keep in mind that the
 
 For example, if your lowest receivable is R$ 10, this is the minimum amount you can anticipate. The maximum amount is informed in the Admin’s “Anticipate receivables” page - the balance you just checked.
 
-![antecipaçãoEN](//images.ctfassets.net/alneenqid6w5/655LHSr6GS2RpCvCKYfAup/bade73d74e819b410247130a7662df03/image.png_h_250)
+![antecipaçãoEN](https://images.ctfassets.net/alneenqid6w5/655LHSr6GS2RpCvCKYfAup/bade73d74e819b410247130a7662df03/image.png_h_250)
 
 <div class="alert alert-info">
 <strong>Warning</strong>: receivables in dispute or expected for the next business day cannot be anticipated.
diff --git a/docs/tutorials/en/how-to-retrieve-the-access-password.md b/docs/tutorials/en/how-to-retrieve-the-access-password.md
index 80d29bf4b..d974cf89c 100644
--- a/docs/tutorials/en/how-to-retrieve-the-access-password.md
+++ b/docs/tutorials/en/how-to-retrieve-the-access-password.md
@@ -18,12 +18,12 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 All access passwords are managed by __VTEX ID__. Accordingly, you must access the login page, and enter your email and password to request the creation of a new password.
 
 1. In some login screen, click on **Login using your email and password;**
-![forgot-password-step1 en](//images.ctfassets.net/alneenqid6w5/1DMWGiuOukwOYUAc0KCQmc/6dfa7485f88c61ea5dc49536edff3bb6/login_1.png)
-2. Click on **Forgot my password;**![forgot-password-step2 en](//images.ctfassets.net/alneenqid6w5/6t3ChxuWHYkaooUiKi0OOO/6092c99fbbbc6c4acddd218e24a3abb1/login_2.png)
-3. Fill out the field with your email;![forgot-password-step3 en](//images.ctfassets.net/alneenqid6w5/1kKj8C5zlKg6uuSyOImGEM/debf868fd9a81176e9c11a8cc9ad7f07/login_3.png)
-4. Fill out the field with the new password and click on **Register a new password**;![forgot-password-step4 en](//images.ctfassets.net/alneenqid6w5/z7KbKetc3uMkWQgmiaQis/645c8e95657829d49e43d456625891f7/login_4.png)
+![forgot-password-step1 en](https://images.ctfassets.net/alneenqid6w5/1DMWGiuOukwOYUAc0KCQmc/6dfa7485f88c61ea5dc49536edff3bb6/login_1.png)
+2. Click on **Forgot my password;**![forgot-password-step2 en](https://images.ctfassets.net/alneenqid6w5/6t3ChxuWHYkaooUiKi0OOO/6092c99fbbbc6c4acddd218e24a3abb1/login_2.png)
+3. Fill out the field with your email;![forgot-password-step3 en](https://images.ctfassets.net/alneenqid6w5/1kKj8C5zlKg6uuSyOImGEM/debf868fd9a81176e9c11a8cc9ad7f07/login_3.png)
+4. Fill out the field with the new password and click on **Register a new password**;![forgot-password-step4 en](https://images.ctfassets.net/alneenqid6w5/z7KbKetc3uMkWQgmiaQis/645c8e95657829d49e43d456625891f7/login_4.png)
 5. Wait for the access code to be sent to you by email;
 6. Paste it on the field requested.
-7. Click on **Change password**.![forgot-password-step5 en](//images.ctfassets.net/alneenqid6w5/3Fqh9NYhIImo8k86UKGSwa/4e38214443a88d0d1230c5ce8aca2223/login_5.png)
+7. Click on **Change password**.![forgot-password-step5 en](https://images.ctfassets.net/alneenqid6w5/3Fqh9NYhIImo8k86UKGSwa/4e38214443a88d0d1230c5ce8aca2223/login_5.png)
 
 Done! The password was retrieved, and the access is released.
diff --git a/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md b/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md
index 5b6342485..4c5b1aa01 100644
--- a/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md
+++ b/docs/tutorials/en/how-to-see-orders-closed-with-benefits.md
@@ -20,7 +20,7 @@ In the section __Orders management__ you can filter the orders made in a certain
 If you want to see the orders that were closed with this benefit applied, just follow the steps below:
 
 1. In the admin menu, click on __Orders management__
-2. Click the filter button and, under the __Others__ section, click the __Promotions & Taxes__ option.![promo-filter-en](//images.ctfassets.net/alneenqid6w5/1JFiP4ZNhmu4cWcOK4Ugs8/cdebe29a683b1561ddaacd034bbaeb1b/promo-filter-en.png)
+2. Click the filter button and, under the __Others__ section, click the __Promotions & Taxes__ option.![promo-filter-en](https://images.ctfassets.net/alneenqid6w5/1JFiP4ZNhmu4cWcOK4Ugs8/cdebe29a683b1561ddaacd034bbaeb1b/promo-filter-en.png)
 3. Select this benefit and click on __Confirm__
 
 In the order list, you'll see all orders closed with this benefit.
diff --git a/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md b/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
index 40ef81f9a..490aface6 100644
--- a/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
+++ b/docs/tutorials/en/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
@@ -30,7 +30,7 @@ Just include an attribute with the name `salesChannel`, as illustrated in the se
 
 Thereafter, the next orders will be created using the sales channel that was set up. In the event there is no stock for a given item in this channel, the item will be excluded from the order.   
 
-![posicao.en](//images.ctfassets.net/alneenqid6w5/8TLvzlzTkt2yUtr5Lmj5z/507d00037f92756ddc01008590350a7b/posicao.en.png)
+![posicao.en](https://images.ctfassets.net/alneenqid6w5/8TLvzlzTkt2yUtr5Lmj5z/507d00037f92756ddc01008590350a7b/posicao.en.png)
 
 *The screen showing the salesChannel ID*
 
@@ -40,5 +40,5 @@ Just include an attribute with the name `defaultSLA`, as illustrated in the setu
 
 Thereafter, the SLA set up will take preference over the cheaper SLA for the next orders created – whereby, if it has a delivery window, the first interval available will be selected.
 
-![transportadora.en](//images.ctfassets.net/alneenqid6w5/5qOOw2KsCHgxP5XmbjmEMd/7b6d0aa40ae6f9e28c269ac42f5313d5/transportadora.en.png)
+![transportadora.en](https://images.ctfassets.net/alneenqid6w5/5qOOw2KsCHgxP5XmbjmEMd/7b6d0aa40ae6f9e28c269ac42f5313d5/transportadora.en.png)
 *The screen showing the ID of the SLA*
diff --git a/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
index 6de3fe121..d79ea05cf 100644
--- a/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
@@ -29,7 +29,7 @@ This article will explain how to associate the Device Fingerprint feature with t
 
 1. Login on http://www.google.com/tagmanager/ for the stored to be set up;
 2. Enter the tags section to set up the device session id;
-3. Crete an “HTML Personalized” product with the following image:![payU 1](//images.contentful.com/alneenqid6w5/8Kc8zBKQFOmwK6G8ekgMa/2a26fa73a709b116cfdf899d4aee7a23/payU_1.png)
+3. Crete an “HTML Personalized” product with the following image:![payU 1](https://images.contentful.com/alneenqid6w5/8Kc8zBKQFOmwK6G8ekgMa/2a26fa73a709b116cfdf899d4aee7a23/payU_1.png)
 4. In the HTML field of the setup, find the HTML code that calls the code to send information to PayU:
 
 ```
@@ -75,25 +75,25 @@ This article will explain how to associate the Device Fingerprint feature with t
 <div id="maf"></div>
 ```
 
-![payU 2](//images.contentful.com/alneenqid6w5/4Y60ayHwaQa8ykaUQUmqgq/4a8ad711a25542b1513a75e94725c464/payU_2.png)
+![payU 2](https://images.contentful.com/alneenqid6w5/4Y60ayHwaQa8ykaUQUmqgq/4a8ad711a25542b1513a75e94725c464/payU_2.png)
 
-It is then necessary to continue on to advanced set up in accordance with the following image:![payU 3](//images.contentful.com/alneenqid6w5/2tZRZWcwFWgq6IueAKWQ4o/c64a7a0f2b6dbaad9405e3e55408fb8c/payU_3.png)
+It is then necessary to continue on to advanced set up in accordance with the following image:![payU 3](https://images.contentful.com/alneenqid6w5/2tZRZWcwFWgq6IueAKWQ4o/c64a7a0f2b6dbaad9405e3e55408fb8c/payU_3.png)
 
 To set up the event, follow these steps:
 
-1. Click on the tab More:![payU 4](//images.contentful.com/alneenqid6w5/1NyDU3X1EseWcCisO04okg/66d6593915e933c22768633a76b4bf92/payU_4.png)
-2. Create a personalized event:![payU 5](//images.contentful.com/alneenqid6w5/Xip98CFhokwoCs22GsUyK/a1c70a419c84d2f4fa2bb0908e0336cd/payU_5.png)
-3. Fill it in as follows:![payU 6](//images.contentful.com/alneenqid6w5/6Rdhtn8quA2IaqKSKeGa0u/0f7a6ed573a438475c477b5c09c331ad/payU_6.png)
-4. We save the event and subsequently save the tag (tag):![payU 7](//images.contentful.com/alneenqid6w5/2AcLzAcwgMs2SwgkEqEmo2/941c852d50622d570e8fab6534780e33/payU_7.png)
-5. Once the tag has been saved, it is necessary to publish it:![payU 8](//images.contentful.com/alneenqid6w5/6mpOQSBwzYq844A8uCuWck/125894734e6996cc1521b46c3562a8a7/payU_8.png)
+1. Click on the tab More:![payU 4](https://images.contentful.com/alneenqid6w5/1NyDU3X1EseWcCisO04okg/66d6593915e933c22768633a76b4bf92/payU_4.png)
+2. Create a personalized event:![payU 5](https://images.contentful.com/alneenqid6w5/Xip98CFhokwoCs22GsUyK/a1c70a419c84d2f4fa2bb0908e0336cd/payU_5.png)
+3. Fill it in as follows:![payU 6](https://images.contentful.com/alneenqid6w5/6Rdhtn8quA2IaqKSKeGa0u/0f7a6ed573a438475c477b5c09c331ad/payU_6.png)
+4. We save the event and subsequently save the tag (tag):![payU 7](https://images.contentful.com/alneenqid6w5/2AcLzAcwgMs2SwgkEqEmo2/941c852d50622d570e8fab6534780e33/payU_7.png)
+5. Once the tag has been saved, it is necessary to publish it:![payU 8](https://images.contentful.com/alneenqid6w5/6mpOQSBwzYq844A8uCuWck/125894734e6996cc1521b46c3562a8a7/payU_8.png)
 
 Once the tag has been set up, it is necessary to save the JS captured from the code. This is saved in the VTEX file manager. To do this, follow these steps:
 
 - Accessing the VTEX panel in the CMS menu >> Layout >> File Manager >> .js File Management >> Add.
 
-![cms js](//images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
+![cms js](https://images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
 
-__Attachment__: [md5.js](//assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
+__Attachment__: [md5.js](https://assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
 
 ### Validation
 
@@ -104,4 +104,4 @@ To validate it, it is necessary to enter the store and to complete the purchase
 3. Search for the word MAF
 
 If the result is found, it means that the setup is correct and that Fingerprint is working properly. For example:
-![payU 9](//images.contentful.com/alneenqid6w5/66H4gkLslyuk0sgOgm8IWC/3d04eca1fdb8ed6a7b4cbf7065a73ec3/payU_9.png)
+![payU 9](https://images.contentful.com/alneenqid6w5/66H4gkLslyuk0sgOgm8IWC/3d04eca1fdb8ed6a7b4cbf7065a73ec3/payU_9.png)
diff --git a/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 35de21e36..5d1b0a247 100644
--- a/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -70,7 +70,7 @@ Next, you'll just need to collect information from Adyen to register on VTEX. St
 5. Remember to write down the username and password that appear in the Password field, since it can't be viewed again!
 6. Click on the **Save** button, located in the page footer.
 7. By following these steps, your user will be successfully set up. In the image below number 1 (highlighted in red) is the username and number 2 is the password that you will have to enter on VTEX’s environment.
-![Adyen - Image 2](//images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
+![Adyen - Image 2](https://images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
 8. Send an email to Adyen support (suporte@adyen.com), requesting the permissions listed in the model below:
 
 > Subject: Setting VTEX web-service user permissions for `{accountName}`
@@ -96,7 +96,7 @@ If you intend Adyen's platform to manually revise the anti-fraud analysis of imp
 
 <ui>5. The configuration should appear as in the image below. Don't forget to click on **Save configuration** to save the changes.</ui>
 
-![Adyen - Image 1](//images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
+![Adyen - Image 1](https://images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
 
 ## VTEX Configuration
 
diff --git a/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
index 440d9609a..08f55288b 100644
--- a/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -31,7 +31,7 @@ To enter the device fingerprint scripts required by Braspag/CyberSource, you wil
 
 ## Creation of variables (macros) and driver
 
-- Create a variable named `trasactionPaymentId`, ype **Variável da camada de dados**, by reading the detalayer `transactionPayment.id` variable.[]![](//images.contentful.com/alneenqid6w5/2iGloCXR32IMAyWAKe8qWy/cf1108ad17e944adc63f189e67cfa93d/gtm-cybersource-variavel1-1.png)
+- Create a variable named `trasactionPaymentId`, ype **Variável da camada de dados**, by reading the detalayer `transactionPayment.id` variable.[]![](https://images.contentful.com/alneenqid6w5/2iGloCXR32IMAyWAKe8qWy/cf1108ad17e944adc63f189e67cfa93d/gtm-cybersource-variavel1-1.png)
 - Create a variable named `cs_sessionId`, of type **JavaScript personalizado** and the following code:
 
 ```
@@ -43,11 +43,11 @@ function() {
 
 - Create the variables `cs_orgId` and `cs_merchantId` of type **Permanente.** The values of these two variables should be filled out with the contents informed by Braspag.
 
-![gtm-cybersource-variavel3-permanente](//images.contentful.com/alneenqid6w5/5EFSTIM6TCKUE4GEOA66kc/8c2f37cdd8cc94571f6f2ac72ec1d35b/gtm-cybersource-variavel3-permanente.png)
+![gtm-cybersource-variavel3-permanente](https://images.contentful.com/alneenqid6w5/5EFSTIM6TCKUE4GEOA66kc/8c2f37cdd8cc94571f6f2ac72ec1d35b/gtm-cybersource-variavel3-permanente.png)
 
 - Create or edit a driver for the orderPlaced screen (screen that shows purchases successfully closed) for it to be compatible with the **Evento personalizado** type and the **orderPlaced** value.
 
-![gtm-cybersource-acionador-orderplaced](//images.contentful.com/alneenqid6w5/51IPOyaAjmowkEQ24sYyw4/7b11cddfb71c200dd1cd2c85149c7726/gtm-cybersource-acionador-orderplaced.png)
+![gtm-cybersource-acionador-orderplaced](https://images.contentful.com/alneenqid6w5/51IPOyaAjmowkEQ24sYyw4/7b11cddfb71c200dd1cd2c85149c7726/gtm-cybersource-acionador-orderplaced.png)
 
 ## Creation of a Braspag tag
 
@@ -66,6 +66,6 @@ Fill it out with the HTML below:
 <script src="https://h.online-metrix.net/fp/check.js?org_id={{cs_orgId}}&amp;session_id={{cs_merchantId}}{{cs_sessionId}}" type="text/javascript"></script>
 ```
 
-![braspag fingerprint](//images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/84f93e14dac3c4471bb1d30b09fbf62e/image.png_h_250)
+![braspag fingerprint](https://images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/84f93e14dac3c4471bb1d30b09fbf62e/image.png_h_250)
 
 At last, post the changes.
diff --git a/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
index 52c28f030..82ba26cf0 100644
--- a/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -31,7 +31,7 @@ The customer schedules the appointment using a form created by Indeva. Then you
 
 Your customer’s schedule flow starts by choosing the physical store of his preference. In the image below, there is only one registered store. But you can register as many physical stores as you want.
 
-![indeva1](//images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
+![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
 <div class="alert alert-info">
 You can also provide your customers a link that takes them directly to a specific physical store form. You just have to add the store ID at the end of the URL. Hence, your seller can share your store’s link—for example, using a QR Code or on social media.
@@ -48,7 +48,7 @@ By clicking on a store, your customer is automatically redirected to the form. T
 
 Finally, your customer must click on the Schedule appointment button. Now this visit will be in the appointment queue displayed in the seller’s app.
 
-![indeva2](//images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
+![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
 <div class=”alert alert-warning”>
 For now, you will have to confirm the appointment manually in the store. Your customer does not receive automatic messages.
@@ -58,13 +58,13 @@ For now, you will have to confirm the appointment manually in the store. Your cu
 
 Indeva Store’s app organizes the appointment queue for every physical store. Sellers and managers can use it to control the next appointments and view the history of already done visits. 
 
-![indeva3](//images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
+![indeva3](https://images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
 
 By selecting a specific appointment, the seller can see all appointment details: date and time of the visit, customer’s name, the message they sent, the number of people, and the customer’s phone number.
 
 If you want to contact your customer through this screen, you just have to click on the Open WhatsApp button. Then you will be redirected to a chat with that specific customer on the messaging app.
 
-![indeva4](//images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
+![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
 <div class=”alert alert-info”>
 You can install the app on multiple devices of the same store, but we recommend that your team use one app per store, not one per seller. 
@@ -114,7 +114,7 @@ The app for store’s sellers and managers is available for both Android and iOS
 
 After installing and opening the app, the seller must inform a 10-digit token to synchronize the device and log in.
 
-![indeva5](//images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
+![indeva5](https://images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
 
 To receive the token, please contact the Indeva support team via:
 - __Phone__: +55(21)3609-2830
diff --git a/docs/tutorials/en/how-to-set-up-the-zoom.md b/docs/tutorials/en/how-to-set-up-the-zoom.md
index f0435037a..5d83691b6 100644
--- a/docs/tutorials/en/how-to-set-up-the-zoom.md
+++ b/docs/tutorials/en/how-to-set-up-the-zoom.md
@@ -19,7 +19,7 @@ A tool very commonly used in online stores is the zoom.
 
 It allows the customer to see a detailed image by passing the mouse over a photo of the product. Let us see how to set up and implement this function.
 
-![zoom-configurações](//images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
+![zoom-configurações](https://images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
 
 ## Setting up the CSS
 
@@ -35,7 +35,7 @@ Next we are going to send the saved CSS file to the server. To do this, click on
 
 Then find the CSS file you saved and send it to the server, clicking on **Localizar** ("Find") and then on **Salvar arquivo** ("Save File")
 
-![add-cms-.css ](//images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
+![add-cms-.css ](https://images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
 
 Your file will then be listed in the window, as shown above.
 
@@ -52,4 +52,4 @@ Now all you have to do is insert `zoom="on"` in the product tag, like this:
 
 You also have to set up the standard size for the zoom image. You can do this in **CMS** module > **Settings** > **File Types**. By default, this type of zoom image is set up with 1000×1000 pixels.
 
-![zoom-tiposdearquivos EN](//images.ctfassets.net/alneenqid6w5/36CmHtsFyg0Ue2wuwYw8QG/de092d8f46a6e304744482144561747d/zoom_file_types.png)
+![zoom-tiposdearquivos EN](https://images.ctfassets.net/alneenqid6w5/36CmHtsFyg0Ue2wuwYw8QG/de092d8f46a6e304744482144561747d/zoom_file_types.png)
diff --git a/docs/tutorials/en/how-to-set-up-visa-debit.md b/docs/tutorials/en/how-to-set-up-visa-debit.md
index a15bc3d39..430540307 100644
--- a/docs/tutorials/en/how-to-set-up-visa-debit.md
+++ b/docs/tutorials/en/how-to-set-up-visa-debit.md
@@ -22,17 +22,17 @@ To set up payments made with Visa Debit at your store, in the VTEX Admin, go to
 First, you need to create a payment condition to enable Visa Debit in the Checkout.
 To do so, in **Settings** access the menu of **Payment conditions** options:
 
-![2.2](//images.ctfassets.net/alneenqid6w5/3chvXc20lyciSmoSEgmqqk/51bbbbe0bb0de7e4a63b9e4ce239b4c7/2.2.png)
+![2.2](https://images.ctfassets.net/alneenqid6w5/3chvXc20lyciSmoSEgmqqk/51bbbbe0bb0de7e4a63b9e4ce239b4c7/2.2.png)
 
 Select Visa Electron to create the payment condition:
 
-![4.2](//images.ctfassets.net/alneenqid6w5/4e2znPWITSSKSmumCyaeG2/d655f5b0b44f4a48fb7236a6f8d46a1a/4.2.png)
+![4.2](https://images.ctfassets.net/alneenqid6w5/4e2znPWITSSKSmumCyaeG2/d655f5b0b44f4a48fb7236a6f8d46a1a/4.2.png)
 
 ### Configure payment condition
 
 Select the desired affiliation to transact the payments; enable the payment condition; and, finally, save the changes: 
 
-![3.2](//images.ctfassets.net/alneenqid6w5/7lW3rrIqbYcgsW8agM00qk/a8309e05cde5ac3f72ca724da4142e48/3.2.png)
+![3.2](https://images.ctfassets.net/alneenqid6w5/7lW3rrIqbYcgsW8agM00qk/a8309e05cde5ac3f72ca724da4142e48/3.2.png)
 
 ### Display credit cards in Checkout
 
diff --git a/docs/tutorials/en/how-to-use-conditions-builder-app.md b/docs/tutorials/en/how-to-use-conditions-builder-app.md
index ae6c6e722..ef1c49fe1 100644
--- a/docs/tutorials/en/how-to-use-conditions-builder-app.md
+++ b/docs/tutorials/en/how-to-use-conditions-builder-app.md
@@ -36,12 +36,12 @@ After installing it, you can access it from the sidebar (installed apps section)
 4. (Optional) Write a short description. This is for internal control only and will not be visible to your customers.
 5. Click on "Start Building".
 
-![createCondition](//images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
+![createCondition](https://images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
 
 After you hit the "Create button", you are going to see a workspace with a block list on the left side of the screen.  
 Now you only have to drag the blocks onto the workspace and conect them, and finally creating your logic. 
 
-![creating](//images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
+![creating](https://images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
 
 
 ### Editing a condition
@@ -55,4 +55,4 @@ If you want a condition to no longer be applied, you can simply disable it inste
 - When toggle button is blue -> it is enabled
 - When toggle button is gray -> it is disabled
 
-![enableDisableEnglish](//images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
+![enableDisableEnglish](https://images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
diff --git a/docs/tutorials/en/how-to-use-the-index-report.md b/docs/tutorials/en/how-to-use-the-index-report.md
index 55e6e4e2f..97e42bab2 100644
--- a/docs/tutorials/en/how-to-use-the-index-report.md
+++ b/docs/tutorials/en/how-to-use-the-index-report.md
@@ -17,7 +17,7 @@ subcategory: 5yDQmr18K4GgQAeGwq8USa
 
 The **Index Report** shows the indexing status of all products of the store. 
 
-![Indexingreport](//images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
+![Indexingreport](https://images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
 
 <div class="alert alert-info">
 <strong>Notice:</strong> For more information, access <a href="/en/tutorial/understanding-how-indexation-works">Understanding the operation of the indexation.</a>
diff --git a/docs/tutorials/en/how-to-use-the-search-result-control.md b/docs/tutorials/en/how-to-use-the-search-result-control.md
index 657713e05..867ad38c5 100644
--- a/docs/tutorials/en/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/en/how-to-use-the-search-result-control.md
@@ -46,14 +46,14 @@ See below the list of all attributes of the Search Result control:
 
 The code rendered by the Search Result control has the following structure by default:
 
-![searchResult1](//images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
+![searchResult1](https://images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
 
 And the corresponding elements that are rendered by the control in its non-customized version follow the pattern below:
 
-![searchResult2](//images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
+![searchResult2](https://images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
 
-![searchResult3](//images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
+![searchResult3](https://images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
 
-![searchResult4](//images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
+![searchResult4](https://images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
 
-![searchResult5](//images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
+![searchResult5](https://images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
diff --git a/docs/tutorials/en/how-to-use-the-shareable-cart-app.md b/docs/tutorials/en/how-to-use-the-shareable-cart-app.md
index b66126c2f..267af51a9 100644
--- a/docs/tutorials/en/how-to-use-the-shareable-cart-app.md
+++ b/docs/tutorials/en/how-to-use-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 The [Shareable Cart](https://apps.vtex.com/vtex-social-selling/p) app allows sales assistants to select products for their customers and share the cart through channels such as WhatsApp, Facebook Messenger and email (Social Selling).
 
-![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 This article details the steps needed to use this feature: activate the app, choose products, add sales assistant code, share and create a new cart. Before you start, you need to [activate this feature in your store](https://help.vtex.com/en/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg).
 
@@ -31,25 +31,25 @@ You must activate the app in your first access, by accessing the store from the
 
 The cart sharing interface should appear on the screen, including some of the icons below. The options available depend on the configuration chosen by the store.
 
-![Screen Shot 2020-05-03 at 17.37.11](//images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
+![Screen Shot 2020-05-03 at 17.37.11](https://images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
 
 ## Choosing products
 
 Once the app is activated, it is not necessary to log in to start browsing and to select products. Just browse the store as usual, as if you were making an online purchase. After choosing all products for the customer, open the cart and follow the next steps in the cart sharing interface.
 
-![shareable-cart-chooseproducts](//images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
+![shareable-cart-chooseproducts](https://images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
 
 ## Adding a sales assistant code
 
 After selecting the products, click on the <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> button to add your sales assistant code. Follow the store's instructions for filling out, as each store can choose different ways to identify sales assistants and add discounts to their carts.
 
-![shareable-cart-addcode](//images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
+![shareable-cart-addcode](https://images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
 
 ## Filling in personal data and address (optional)
 
 Depending on the customer's preference and your store’s guidelines, you can fill in the personal and shipping data for the order. Payment data must always be filled in by the customer.
 
-![shareable-cart-customerdetails](//images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
+![shareable-cart-customerdetails](https://images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
 
 <div class="alert alert-danger" role="alert"><strong>Never ask for payment details when sending the cart.</strong> Even if the customer insists, explain that they should fill in the payment details for security reasons.</div>
 
@@ -57,7 +57,7 @@ Depending on the customer's preference and your store’s guidelines, you can fi
 
 After adding your sales assistant code, click on the button corresponding to the desired option. See below the steps for each sharing option.
 
-![shareable-cart-sharecart](//images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
+![shareable-cart-sharecart](https://images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
 
 ### Whatsapp
 
diff --git a/docs/tutorials/en/how-to-use-the-unavailable-product-class.md b/docs/tutorials/en/how-to-use-the-unavailable-product-class.md
index f9ce94aa0..00be9bf8a 100644
--- a/docs/tutorials/en/how-to-use-the-unavailable-product-class.md
+++ b/docs/tutorials/en/how-to-use-the-unavailable-product-class.md
@@ -29,7 +29,7 @@ __If an SKU with a certain specification is not available in stock, the store ma
 
 In the example below, sizes P and G are not available.
 
-![classeIndisponivel](//images.contentful.com/alneenqid6w5/6dTacclHvqeaMwws8kqU8K/2d0d79d95dc521626eb1ba5c1c056da2/classeIndisponivel.png)
+![classeIndisponivel](https://images.contentful.com/alneenqid6w5/6dTacclHvqeaMwws8kqU8K/2d0d79d95dc521626eb1ba5c1c056da2/classeIndisponivel.png)
 
 ## Including the unavailable product class
 
diff --git a/docs/tutorials/en/how-to-use-vtex-predictor-bot.md b/docs/tutorials/en/how-to-use-vtex-predictor-bot.md
index 6fb206458..17cf6252f 100644
--- a/docs/tutorials/en/how-to-use-vtex-predictor-bot.md
+++ b/docs/tutorials/en/how-to-use-vtex-predictor-bot.md
@@ -28,18 +28,18 @@ By combining data from different sources it's able to predict how your sales sho
 ## How Predictor Bot works
 
 We start off by getting an idea of how your store is performing.
-![sales data](//images.contentful.com/alneenqid6w5/4LVuTVHevYw6eaykMwQY4M/8b9a06a17479a1595c05d879071ad320/sales_data.png)
+![sales data](https://images.contentful.com/alneenqid6w5/4LVuTVHevYw6eaykMwQY4M/8b9a06a17479a1595c05d879071ad320/sales_data.png)
 
 As depicted by the image above, every typical store has a pattern - even on a daily basis, or hourly. We must identify that pattern to start any analysis.
 
 But not all are sunshine and flowers. Many times we see something like this:
-![crazy sales data](//images.contentful.com/alneenqid6w5/K7vwyviY4S6Q4CwSOSsaW/a644e1f182e82da152d69c661f3f44b7/crazy_sales_data.png)
+![crazy sales data](https://images.contentful.com/alneenqid6w5/K7vwyviY4S6Q4CwSOSsaW/a644e1f182e82da152d69c661f3f44b7/crazy_sales_data.png)
 
 So we must remove outliers and compare new sets of data against other periods. We keep iterating that way until our algorithm knows we have a safe set of data. At that point we can analyse and __identify events that offset the pattern__.
 
 In the end our predicted graph is something like the curve below. The blue line is the result of our model. This curve is contained within a confidence interval (blue area).
 
-![unnamed](//images.contentful.com/alneenqid6w5/4dyeHM6ycoSGs0kgMUSQqo/56ff4ea1a3478dfea3fc8c4d9860280c/unnamed.png)
+![unnamed](https://images.contentful.com/alneenqid6w5/4dyeHM6ycoSGs0kgMUSQqo/56ff4ea1a3478dfea3fc8c4d9860280c/unnamed.png)
 
 Whenever we find something, we let you know! So if your current performance strays from our model but is within the intervals we only send a __WARNING__. If it goes beyond then you receive a __CRITICAL__ notice.
 
@@ -47,7 +47,7 @@ Whenever we find something, we let you know! So if your current performance stra
 
 We may send you three types of e-mails. Here is a sneak peek:
 
-![Vtex Predictor Bot template](//images.contentful.com/alneenqid6w5/1Ft1I0ibI4g86okS4IYKy0/293929eb488252dabe8cdadee29c86e7/Vtex_Predictor_Bot_template.png)
+![Vtex Predictor Bot template](https://images.contentful.com/alneenqid6w5/1Ft1I0ibI4g86okS4IYKy0/293929eb488252dabe8cdadee29c86e7/Vtex_Predictor_Bot_template.png)
 
 As you may see this is an example of a notification sent when the anomaly has gone by and your store's sales are back on track.
 
diff --git a/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md b/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md
index c400e2804..c3af6c7e0 100644
--- a/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md
+++ b/docs/tutorials/en/how-to-view-taxes-information-in-taxhub.md
@@ -17,6 +17,6 @@ subcategory:
 
 When a product is added to the cart, the amounts charged for each tax previously set up will be charged. To calculate the tax, it is necessary to fill in the customer’s data and purchase delivery data. Taxes will be always specified on the checkout page. The party responsible for the store will also have the information on Orders Management.
 
-![Screenshot 2](//images.ctfassets.net/alneenqid6w5/6I5qA3ZzMWuC4gMeoi628W/a5a3d1a6fdae11ca486d1fef33157c6a/Screenshot_2.png)
+![Screenshot 2](https://images.ctfassets.net/alneenqid6w5/6I5qA3ZzMWuC4gMeoi628W/a5a3d1a6fdae11ca486d1fef33157c6a/Screenshot_2.png)
 
 [Continue reading about TaxHub with the article about its API REST structure](/en/tutorial/how-is-taxhub-api-rest-structure)
diff --git a/docs/tutorials/en/how-to-view-the-orders-details.md b/docs/tutorials/en/how-to-view-the-orders-details.md
index 5bb398841..9fa160351 100644
--- a/docs/tutorials/en/how-to-view-the-orders-details.md
+++ b/docs/tutorials/en/how-to-view-the-orders-details.md
@@ -30,7 +30,7 @@ On the right side there's a box containing the total value of the order, the cus
 
 The ID refers to the transaction on VTEX gateway, and it's part of the URL.
 
-![pci](//images.contentful.com/alneenqid6w5/65oy7tCoAoCMgGIi4CYau6/69e8caa34812349a09014157d0d27e33/pci.png)
+![pci](https://images.contentful.com/alneenqid6w5/65oy7tCoAoCMgGIi4CYau6/69e8caa34812349a09014157d0d27e33/pci.png)
 
 Above this box is a link to the order in the **Orders** module.
 
@@ -51,19 +51,19 @@ The following are examples of how to view the most common scenarios that require
 
 ### Approval event
 
-![](//images.contentful.com/alneenqid6w5/2P90PVqJl6qOWGkc6icoss/fba44bb1bd12c7e42d1658d91d6edd73/2.jpg)
+![](https://images.contentful.com/alneenqid6w5/2P90PVqJl6qOWGkc6icoss/fba44bb1bd12c7e42d1658d91d6edd73/2.jpg)
 
 In this example, we see a payment approval. That is, we see that the operator authorized the closing of the purchase with this payment data.
 
 ### Anti-fraud approval event
 
-![](//images.contentful.com/alneenqid6w5/2kCKR8mx3KUGW60cSs0wmo/d4cb6c1271069fd4f85e8ccb0813ef27/3.jpg)
+![](https://images.contentful.com/alneenqid6w5/2kCKR8mx3KUGW60cSs0wmo/d4cb6c1271069fd4f85e8ccb0813ef27/3.jpg)
 
 Here we see the return of the antifraud receiving the transaction and then the return with the risk analysis that was performed, and which approved the transaction. In case of failure, the log will display the information `RiskRejected`.
 
 ### Invoice event
 
-![](//images.contentful.com/alneenqid6w5/5v6fzCwSCkeqO8g24kSkqS/5e8d39795949ce428153a0e18bcdf558/4.jpg)
+![](https://images.contentful.com/alneenqid6w5/5v6fzCwSCkeqO8g24kSkqS/5e8d39795949ce428153a0e18bcdf558/4.jpg)
 
 In this example, the carrier returns the value settlement event, that is, it informs that it made the order invoice.
 
@@ -71,7 +71,7 @@ In this example, the carrier returns the value settlement event, that is, it inf
 
 The example below shows a credit card transaction that generated an error while being processed by the Redecard acquirer. Affiliates usually return a code (`ConnectorCode`) next to a message. For detailed error information, we recommend refering to the purchaser's documentation. Through a quick Google search you can find the list of codes and messages of each affiliate.
 
-![2017-01-26 20_23_37-634883 _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/4CR2xqOZMkEEKoq0Q4008W/0088088b1a2167314ee31ab1078435b6/2017-01-26-20_23_37-634883-_-VTEX-PCI-Gateway.png)
+![2017-01-26 20_23_37-634883 _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/4CR2xqOZMkEEKoq0Q4008W/0088088b1a2167314ee31ab1078435b6/2017-01-26-20_23_37-634883-_-VTEX-PCI-Gateway.png)
 
 ## Scheduled automatic settlement
 
@@ -81,7 +81,7 @@ If the order is canceled, the chargeback will occur normally.
 
 Here's how to view the automatic settlement schedule date:
 
-![](//images.contentful.com/alneenqid6w5/3cUrT8OgtiiiKGiaySoO4Q/5abbea075f47b3c3334954a3fa53f006/5.jpg)
+![](https://images.contentful.com/alneenqid6w5/3cUrT8OgtiiiKGiaySoO4Q/5abbea075f47b3c3334954a3fa53f006/5.jpg)
 
 ## Payment TID
 
@@ -91,22 +91,22 @@ This information is important whenever you need to confirm something with the op
 
 To find this code in the transaction, see the illustration below.
 
-![](//images.contentful.com/alneenqid6w5/4UGw2BvqvewicmA4sYq64a/488e64d672529ed30b56e364efd4e89f/6.jpg)
+![](https://images.contentful.com/alneenqid6w5/4UGw2BvqvewicmA4sYq64a/488e64d672529ed30b56e364efd4e89f/6.jpg)
 
 ## Client's IP
 
 The client's IP is collected at the time of the purchase and can be seen in the upper field of the transaction screen, as shown below.
 
-![](//images.contentful.com/alneenqid6w5/3luCOyDKZ2a22y2q26S6E/1b77e158a83d51f43a4e9bb74981a512/7.jpg)
+![](https://images.contentful.com/alneenqid6w5/3luCOyDKZ2a22y2q26S6E/1b77e158a83d51f43a4e9bb74981a512/7.jpg)
 
 ## Antifraud ID
 
 This is the transaction ID for the antifraud. For antifraud searches, you should check this value on the PCI Gateway.
 
-![IDAntifraude](//images.contentful.com/alneenqid6w5/6KrRXQocKWy6kQosaOgiyU/77e8ae4f52c586280a17a08373675301/IDAntifraude-1.gif)
+![IDAntifraude](https://images.contentful.com/alneenqid6w5/6KrRXQocKWy6kQosaOgiyU/77e8ae4f52c586280a17a08373675301/IDAntifraude-1.gif)
 
 ## More information
 
 In addition to the above information, there are other data taken from interactions with the carrier, with the gateway and/or the anti-fraud that are identified and made available more clearly in the box **+ information**. Check its location in the image below:
 
-![](//images.contentful.com/alneenqid6w5/2fHaJACApyyUsIGueGkckU/edade2f60187dc9aed87942e8030d938/8.jpg)
+![](https://images.contentful.com/alneenqid6w5/2fHaJACApyyUsIGueGkckU/edade2f60187dc9aed87942e8030d938/8.jpg)
diff --git a/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md b/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md
index a4a8c1409..f4ff904d6 100644
--- a/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md
+++ b/docs/tutorials/en/how-to-view-transactions-on-pci-gateway.md
@@ -21,7 +21,7 @@ On the main interface, you can find all transactions listed, from the most rece
 
 This listing indicates the current status, the start (date and time) of the transaction, the customer's name, the order's ID, the payment method used to close the order and the value transacted.
 
-![payment_en](//images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/1ea0a2b0479a1d411935a9e873213252/payment_en.jpg)
+![payment_en](https://images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/1ea0a2b0479a1d411935a9e873213252/payment_en.jpg)
 
 Each order registration will its data restricted to the payment conditions used for its closure. Authorization, transaction and NSU codes, among others, [are available within each record.](http://help.vtex.com/tutorial/como-visualizar-detalhes-do-pedido/ "are available within each record.")
 
diff --git a/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
index 3bb392cf2..e143164c2 100644
--- a/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
@@ -37,7 +37,7 @@ After that a new section will be available and you can define through the fields
 
 It is possible to limit the availability of the template to a predetermined period of time by filling in the __From__ and __To__ fields as well as to define in which categories, products, brands and collections the chosen template will be applied.
 
-![template-condicionado-cms](//images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
+![template-condicionado-cms](https://images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
 
 After filling in all the needed fields, do not forget to save the changes made by clicking on __Save Layout__.
 
diff --git a/docs/tutorials/en/i-cant-import-the-price-table.md b/docs/tutorials/en/i-cant-import-the-price-table.md
index 169a44f8c..c9cd01d54 100644
--- a/docs/tutorials/en/i-cant-import-the-price-table.md
+++ b/docs/tutorials/en/i-cant-import-the-price-table.md
@@ -56,7 +56,7 @@ Make sure that all fields in your table are properly populated based on the guid
 
 Example of a table with filters applied and __Error Code__ and __Error Message__ fields:
 
-![Price spreadsheet](//images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/a88f798c1962786dadfd35573453242e/Price_spreadsheet.PNG)
+![Price spreadsheet](https://images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/a88f798c1962786dadfd35573453242e/Price_spreadsheet.PNG)
 
 #### File size
 
diff --git a/docs/tutorials/en/i-cant-receive-emails-from-vtex.md b/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
index 80b31ad29..7075ac80d 100644
--- a/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
+++ b/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
@@ -95,4 +95,4 @@ You can also check whether the email is registered as a copy in any of the store
 3. Check if the email does not appear in the template's __Cc:__ or __Bcc:__ fields. If it does, remove it and click `Save`.
 4. Do this for each store's template card and test sending an email to the desired address.
 
-![copia_email_en](//images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/60df1d00ff23e4a1847d76a09e4dd44b/copia_email_en.png)
+![copia_email_en](https://images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/60df1d00ff23e4a1847d76a09e4dd44b/copia_email_en.png)
diff --git a/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
index 390c5d0af..f35c34c95 100644
--- a/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
+++ b/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
@@ -21,9 +21,9 @@ When the user searches in a VTEX store using [Intelligent Search](https://help.v
 
 Example scenario: When searching the store's website for products containing the term "Pendleton," the search results return 6 products. However, when we access the VTEX Admin (__Storefront > Intelligent Search > Explained Search__) and enter the same term, 9 products are displayed.
 
-![Filter_1](//images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/568f6f3868b13d54ed4335b4574ac434/Filter_1.png)
+![Filter_1](https://images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/568f6f3868b13d54ed4335b4574ac434/Filter_1.png)
 
-![Filter_2](//images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/06017d321b1996515da01c11ea53403c/Filter_2.png)
+![Filter_2](https://images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/06017d321b1996515da01c11ea53403c/Filter_2.png)
 
 This behavior can occur due to the following reasons:
 
@@ -83,7 +83,7 @@ To remove the restriction on searching by *brand* and allow products to be found
 
 <blockquote><ui>4. Under <b>Choose an app</b>, click the Rewriter app option (<b>vtex.rewriter@{app-version-number}</b>).</ui>
 
-![Graphql_ide_en](//images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/6e0774e72b9a6e4a6b85a4c47986fe84/Graphql_ide_en.png)
+![Graphql_ide_en](https://images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/6e0774e72b9a6e4a6b85a4c47986fe84/Graphql_ide_en.png)
 
 <blockquote><ui>5. In the query input field (below <b>GraphiQL</b>), enter the details of the <i>saveInternal</i> mutation function.<ui>
 
diff --git a/docs/tutorials/en/identifying-whether-marketing-utms-are-being-passed-to-checkout.md b/docs/tutorials/en/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
index 0103b9da4..513990208 100644
--- a/docs/tutorials/en/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
+++ b/docs/tutorials/en/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
@@ -27,13 +27,13 @@ With that, checkout will be able to assemble the orderForm considering the marke
 
 To make sure the content of the `utm_source` parameter, for example, is being passed to the checkout, you can follow the steps below:
 1. Access any page of the store with the utm in the querystring (eg: {AccountName}.com.br`?utm_source=facebook`)
-2. Enter the __developer tools__ (F12 in Chrome, if you are in Windows, or Cmd+Opt+I on a Mac), go to the __Application__ tab, open the store's website cookies and look for the __IPS__ cookie.![utmSource1](//images.contentful.com/alneenqid6w5/2tGleKs2b2Gge8oEoquSGm/17efaf14e42cd655b037c2bd009eb0d6/utmSource1.png)
+2. Enter the __developer tools__ (F12 in Chrome, if you are in Windows, or Cmd+Opt+I on a Mac), go to the __Application__ tab, open the store's website cookies and look for the __IPS__ cookie.![utmSource1](https://images.contentful.com/alneenqid6w5/2tGleKs2b2Gge8oEoquSGm/17efaf14e42cd655b037c2bd009eb0d6/utmSource1.png)
 3. Enter a product page and insert a product into the cart.
 4. Enter the cart.
 5. Refresh the page, and on the developer tools __Network__ tab, monitor the requests.
 6. Select the request __orderForm__.
 7. In the preview, open the `marketingData` node.
-8. Check the value of the `utmSource` field.![utmSource2](//images.contentful.com/alneenqid6w5/3k5685cAUwy4uk4S2I6qGm/6595f50415b17965047c2023ffb46658/utmSource2.png)
+8. Check the value of the `utmSource` field.![utmSource2](https://images.contentful.com/alneenqid6w5/3k5685cAUwy4uk4S2I6qGm/6595f50415b17965047c2023ffb46658/utmSource2.png)
 
 In the example above, note that the value of the `utm_source` parameter was correctly passed to the checkout, which entered this parameter in the orderForm, within the `utmSource` field.
 
diff --git a/docs/tutorials/en/image-compression.md b/docs/tutorials/en/image-compression.md
index 5178f89e3..e74f1880b 100644
--- a/docs/tutorials/en/image-compression.md
+++ b/docs/tutorials/en/image-compression.md
@@ -44,7 +44,7 @@ Additionally, PNG images are optimized with [pngquant](https://pngquant.org/), w
 
 Finally, VTEX delivers the smallest file between the lossless WebP and the optimized PNG, as illustrated in the diagram below.
 
-![png-image-compression](//images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/c3f60b063fbfa38ed197d44d6e7da014/png-image-compression.PNG)
+![png-image-compression](https://images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/c3f60b063fbfa38ed197d44d6e7da014/png-image-compression.PNG)
 
 ## JPG / JPEG
 
@@ -52,7 +52,7 @@ For images in the **JPG/JPEG** formats, which are ideal for photos, the conversi
 
 VTEX delivers the image with the smallest file size to the customer, choosing between the original and the one converted to lossless WebP, as illustrated in the diagram below.
 
-![webp-image-compression](//images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/0a711ec8fb9135cbddeada05f9191d95/webp-image-compression.PNG)
+![webp-image-compression](https://images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/0a711ec8fb9135cbddeada05f9191d95/webp-image-compression.PNG)
 
 ## Related articles
 
diff --git a/docs/tutorials/en/importing-data-into-master-data.md b/docs/tutorials/en/importing-data-into-master-data.md
index 1ddbac22a..95d45dc53 100644
--- a/docs/tutorials/en/importing-data-into-master-data.md
+++ b/docs/tutorials/en/importing-data-into-master-data.md
@@ -48,4 +48,4 @@ Keep the same format of the worksheet (xls) for the import to be successful.
 5. Select the file.
 6. Click on the **Import** button at the bottom of the screen.
 
-![Importando](//images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
+![Importando](https://images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
diff --git a/docs/tutorials/en/improving-the-performance-of-product-images.md b/docs/tutorials/en/improving-the-performance-of-product-images.md
index 54d447f8e..46f91b2a9 100644
--- a/docs/tutorials/en/improving-the-performance-of-product-images.md
+++ b/docs/tutorials/en/improving-the-performance-of-product-images.md
@@ -64,7 +64,7 @@ In our previous example, all you have to do is to write the URL of the image in
 
 In this way, VTEX Img will deliver the image with a size of 50×50. This will make it much quicker to load.
 
-![tamanhosImg](//images.contentful.com/alneenqid6w5/p4aDcgaE4SmyYkCwaW0CI/189307d29c86dae17beabde67780d907/tamanhosImg.png)
+![tamanhosImg](https://images.contentful.com/alneenqid6w5/p4aDcgaE4SmyYkCwaW0CI/189307d29c86dae17beabde67780d907/tamanhosImg.png)
 _Sending images of a size larger than will be shown damages your store’s performance._
 
 ## Rectangular images
diff --git a/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md b/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md
index e7d866f9d..665b4f99c 100644
--- a/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md
+++ b/docs/tutorials/en/improving-the-seo-of-product-listing-pages.md
@@ -21,7 +21,7 @@ The PLPs are correlated as each product links back to a category page — Appare
 
 To improve the SEO performance of PLPs, you must allow web crawlers such as Google to notice this connection between PLPs. This way,  these crawlers will be able to browse different pages and access other products they show. 
 
-![Show more button](//images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/ec462ab024d44052f0eba3ddd360c00d/bt-show-more.png)
+![Show more button](https://images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/ec462ab024d44052f0eba3ddd360c00d/bt-show-more.png)
 
 See the section below on how to improve the SEO performance of PLPs [using the Site Editor](#using-the-site-editor).
 
@@ -39,7 +39,7 @@ To improve the SEO performance of PLPs via Site Editor, you have to configure th
 4. Click on __Fetch more.__
 5. On __Button behavior,__ select the option __Link to page - Improves SEO, may change how the button looks.__
 
-![bt-config-en](//images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/4ac3a699c734b39ebc5bfae46c27696a/bt-config-en.gif)
+![bt-config-en](https://images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/4ac3a699c734b39ebc5bfae46c27696a/bt-config-en.gif)
 
 6. Click on `SAVE`.
 7. To configure the __Fetch previous__ item, expand the __Search Result Flexible Layout__ block.
diff --git a/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md b/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md
index 032d3678f..1d7904cbe 100644
--- a/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md
+++ b/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md
@@ -36,7 +36,7 @@ Let's say you want to enter the name of the carrier in the "product sent" email.
 
 To do this, enter the "product sent" template ("pedido enviado") and, in the __JSON Data__ field, search for the `courier` property.
 
-![templateCourierMC](//images.contentful.com/alneenqid6w5/5bUVtrYTugUiqKimU6COEK/a21db5630ee6febbd43493b2357c8172/templateCourierMC.png)
+![templateCourierMC](https://images.contentful.com/alneenqid6w5/5bUVtrYTugUiqKimU6COEK/a21db5630ee6febbd43493b2357c8172/templateCourierMC.png)
 
 The filled-in value for this property is just an example, but you can use it in the __HTML__ field so that when the email is sent the customer sees the carrier that is actually responsible for the order delivery.
 
@@ -44,7 +44,7 @@ Note that the `courier` property is inside the `package` object. Therefore, you
 
 `{{package.courier}}`
 
-![courier3](//images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
+![courier3](https://images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
 
 As you see, the sample value ("Transportadora Teste Courier S.A.") was inserted in the preview screen, below the __HTML__ and __JSON Data__ fields.
 
diff --git a/docs/tutorials/en/indexes-in-master-data.md b/docs/tutorials/en/indexes-in-master-data.md
index e92bbde33..013919532 100644
--- a/docs/tutorials/en/indexes-in-master-data.md
+++ b/docs/tutorials/en/indexes-in-master-data.md
@@ -56,11 +56,11 @@ If only one field is configured as an index, the alternative key will not allow
 
 For example, the **Customer** table has two columns: **ID** and **Name**. To make searching easier, the **Name** field (`firstName`) can be configured as an index and marked as **Unique values**, as illustrated below:
 
-![indices-1-en](//images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/73cc5f6e47530f8a25b428b858c3d0df/indices-1-en.png)
+![indices-1-en](https://images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/73cc5f6e47530f8a25b428b858c3d0df/indices-1-en.png)
 
 As a result, it will not be possible to enter a name that has already been entered in **Customer**:
 
-![indices-2-en](//images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/8caded1ca96fdf9c0bcd93a5afc12d27/indices-2-en.png)
+![indices-2-en](https://images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/8caded1ca96fdf9c0bcd93a5afc12d27/indices-2-en.png)
 
 In the example above, as there is already a record with the **Name** equal to **Mary**, you cannot add another one with the same value.
 
@@ -74,11 +74,11 @@ If there is more than one field in the index, the alternative key will prevent a
 
 For example, imagine that the **Customer** entity has three fields: **ID**, **Name** and **Document**. In the index configuration, under **Fields**, you enter Name (`firstName`) and Document (`document`), as shown below:
 
-![indices-3-en](//images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/6dfd99a8e88c85ea424e31bafd163572/indices-3-en.png)
+![indices-3-en](https://images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/6dfd99a8e88c85ea424e31bafd163572/indices-3-en.png)
 
 In this case, the **Name** value can be repeated, or the **Document** value can be repeated, but the combination of the two values cannot be repeated. In other words, there can be no record that repeats the same pair of values (such as identical **Name** and **Document**).
 
-![indices-4-en](//images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/f56a0b860946eec272c8973d57eb6368/indices-4-en.png)
+![indices-4-en](https://images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/f56a0b860946eec272c8973d57eb6368/indices-4-en.png)
 
 In the example above, there is already a record with the **Name** as **Mary**. You can include another record with the same **Name** as long as the **Document** value is different.
 
diff --git a/docs/tutorials/en/indexing-history-beta.md b/docs/tutorials/en/indexing-history-beta.md
index e9bb12d8e..9208f1870 100644
--- a/docs/tutorials/en/indexing-history-beta.md
+++ b/docs/tutorials/en/indexing-history-beta.md
@@ -21,12 +21,12 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 
 **Indexing history** is the page that monitors the synchronization status of all products in the Catalog sent to Intelligent Search. It provides a broad view of the indexing progress of your store.
 
-![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+![Histórico da Indexação 1 - EN](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
 
 The **Indexing status** section displays the following information:
 
 * **Average indexing time:** The average time for products to be indexed, from the time the system received the change notification to the in-store update. Indexing time performance is measured by a green (healthy) or red (bad) dot. 
-![Historico Indexação 2 - EN](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
+![Historico Indexação 2 - EN](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
 * **Products in store:** Quantity of products with up-to-date information currently displayed in the store.
 * **Indexing status share:** The percentage of products in each indexing step. Status breakdown performance is measured by a green (healthy) or red (bad) dot. The steps displayed are:
     * **Updated:** Latest product update has been entered in the store.
@@ -37,15 +37,15 @@ You can filter the list of indexed products for a custom view. It is important t
 
 To filter the list of indexed products, click on `Filter` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
 
 If you filter by `Status` you can select which status you want to filter by, which could be `Updated`, `Updating`, `Error`.
 
-![Historico indexação 4 - EN](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
+![Historico indexação 4 - EN](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
 
 If you filter by `Indexing time` you can select whether the time interval `Is greater than`, `Is equal to or greater than`, `Is shorter than` or `Is equal to or less than` a defined time.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
 
 After defining the filter, click `Apply` to activate it. 
 
@@ -55,17 +55,17 @@ You can also filter the products displayed in the listing by **ID**, **Last upda
 
 If you want more information about the indexing of a specific product, you can click on the product row in the table to access a page that contains more details, as illustrated below.
 
-![Historico indexação 6 - EN](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
+![Historico indexação 6 - EN](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
 
 In addition to the information displayed in the product list, you can also see:
 
 * **Indexing time:** Is an entry of how long the product indexing lasted using the `hh:mm:ss` format`.
 * **Indexing timeline:** Shows a log of every status change with date and time. You can view more details of each step by clicking the <i class="fa-solid fa-chevron-down"></i> icon.
 
-![Historico indexação 7 - EN](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
+![Historico indexação 7 - EN](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
 
 It is possible to manually reindex a product without having to update the entry. To reindex a product, click <i class="fa-solid fa-arrows-rotate"></i> `Reindex`. Only products in **Updated** status can be indexed.
 
 You can access the product **Indexing history**, a list with the date and time of each update performed. Therefore, it is possible to have a record of every change that was made to the product. To access it, click <i class="fa-solid fa-arrows-rotate"></i> `History`. 
 
-![Histórico da Indexação 8 - EN](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
+![Histórico da Indexação 8 - EN](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
diff --git a/docs/tutorials/en/indexing-history.md b/docs/tutorials/en/indexing-history.md
index c6c8f4768..f21883a3e 100644
--- a/docs/tutorials/en/indexing-history.md
+++ b/docs/tutorials/en/indexing-history.md
@@ -17,12 +17,12 @@ subcategory: l3DubpOCHBfKyF2ueg2Vs
 
 **Indexing history** is the page that monitors the synchronization status of all products in the Catalog sent to Intelligent Search. It provides a broad view of the indexing progress of your store.
 
-![Histórico da Indexação 1 - EN](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
+![Histórico da Indexação 1 - EN](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/4c8e68f1fe949820607fa47d9ed5f549/Screenshot_2022-09-01_at_12-51-24_Indexing_History.png)
 
 The **Indexing status** section displays the following information:
 
 * **Average indexing time:** The average time for products to be indexed, from the time the system received the change notification to the in-store update. Indexing time performance is measured by a green (healthy) or red (bad) dot. 
-![Historico Indexação 2 - EN](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
+![Historico Indexação 2 - EN](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/9c5ec23fd8ffa11210af003a51e5cb56/Captura_de_Tela_2022-09-01_a__s_12.56.07.png)
 * **Products in store:** Quantity of products with up-to-date information currently displayed in the store.
 * **Indexing status share:** The percentage of products in each indexing step. Status breakdown performance is measured by a green (healthy) or red (bad) dot. The steps displayed are:
     * **Updated:** Latest product update has been entered in the store.
@@ -33,15 +33,15 @@ You can filter the list of indexed products for a custom view. It is important t
 
 To filter the list of indexed products, click on `Filter` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Select `Status` or `Indexing time` to set the filtering criteria. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/09caff4ffeaa1012d0827b8748a52a58/Captura_de_Tela_2022-09-01_a__s_13.12.32.png)
 
 If you filter by `Status` you can select which status you want to filter by, which could be `Updated`, `Updating`, `Error`.
 
-![Historico indexação 4 - EN](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
+![Historico indexação 4 - EN](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/7ed5fc757d20d3d07952d0385c232e90/Captura_de_Tela_2022-09-01_a__s_13.13.49.png)
 
 If you filter by `Indexing time` you can select whether the time interval `Is greater than`, `Is equal to or greater than`, `Is shorter than` or `Is equal to or less than` a defined time.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/3fd6848c357c8f6a5e2466b916032194/Captura_de_Tela_2022-09-01_a__s_13.17.24.png)
 
 After defining the filter, click `Apply` to activate it. 
 
@@ -51,17 +51,17 @@ You can also filter the products displayed in the listing by **ID**, **Last upda
 
 If you want more information about the indexing of a specific product, you can click on the product row in the table to access a page that contains more details, as illustrated below.
 
-![Historico indexação 6 - EN](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
+![Historico indexação 6 - EN](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/19fab2fceab8d295516bcb28e3682511/Screenshot_2022-09-01_at_13-19-22_Indexing_History.png)
 
 In addition to the information displayed in the product list, you can also see:
 
 * **Indexing time:** Is an entry of how long the product indexing lasted using the `hh:mm:ss` format`.
 * **Indexing timeline:** Shows a log of every status change with date and time. You can view more details of each step by clicking the <i class="fa-solid fa-chevron-down"></i> icon.
 
-![Historico indexação 7 - EN](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
+![Historico indexação 7 - EN](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/aea6679f994ad55f2b66ee3e50472014/Screenshot_2022-09-01_at_13-23-51_Indexing_History.png)
 
 It is possible to manually reindex a product without having to update the entry. To reindex a product, click <i class="fa-solid fa-arrows-rotate"></i> `Reindex`. Only products in **Updated** status can be indexed.
 
 You can access the product **Indexing history**, a list with the date and time of each update performed. Therefore, it is possible to have a record of every change that was made to the product. To access it, click <i class="fa-solid fa-arrows-rotate"></i> `History`. 
 
-![Histórico da Indexação 8 - EN](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
+![Histórico da Indexação 8 - EN](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/19bb63c8ed3d288213641d45ba702741/Screenshot_2022-09-01_at_13-41-59_Indexing_History.png)
diff --git a/docs/tutorials/en/install-visa-checkout-in-the-extension-store.md b/docs/tutorials/en/install-visa-checkout-in-the-extension-store.md
index fa8370dbe..7fcd62db8 100644
--- a/docs/tutorials/en/install-visa-checkout-in-the-extension-store.md
+++ b/docs/tutorials/en/install-visa-checkout-in-the-extension-store.md
@@ -21,7 +21,7 @@ The purpose of this article is a step-by-step demonstration of how to install th
 
 First, on the **Explore** screen, click on the **Visa Checkout** extension.
 
-![Extension Store 1](//images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
+![Extension Store 1](https://images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
 
 You will then have access to the page with the extension details, where the following information is displayed:
 
@@ -76,4 +76,4 @@ To move the Visa Checkout to the production environment (where you customers can
 
 To do this, just click on the **Publish** button of the top bar.
 
-![Extension Store 3 - Publishing](//images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
+![Extension Store 3 - Publishing](https://images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
diff --git a/docs/tutorials/en/installing-my-orders-through-the-extension-store.md b/docs/tutorials/en/installing-my-orders-through-the-extension-store.md
index c8b4f1c2a..e3be5f950 100644
--- a/docs/tutorials/en/installing-my-orders-through-the-extension-store.md
+++ b/docs/tutorials/en/installing-my-orders-through-the-extension-store.md
@@ -19,7 +19,7 @@ Following the evolution of VTEX platform, the viewpart of __My Orders__ is now a
 
 In order to perform the installation, you need to access the [VTEX App Store.](https://extensions.vtex.com/)
 
-![app store1 EN](//images.ctfassets.net/alneenqid6w5/4TNMg7DSxWco4KCyO6yaYU/941ee734d6e7a6ee93f85a6d59d8324c/app_store1_EN.png)
+![app store1 EN](https://images.ctfassets.net/alneenqid6w5/4TNMg7DSxWco4KCyO6yaYU/941ee734d6e7a6ee93f85a6d59d8324c/app_store1_EN.png)
 
 __After installing the app, you already have the following updates:__
 
@@ -29,7 +29,7 @@ __After installing the app, you already have the following updates:__
 - Trace information for multiple items.
 - Minor Bug Fix.
 
-![app store2 EN](//images.ctfassets.net/alneenqid6w5/uWM5x8qG5ia6okQ0kgIak/1caf4e8275bb8e8514b7073396553b6a/app_store2_EN.png)
+![app store2 EN](https://images.ctfassets.net/alneenqid6w5/uWM5x8qG5ia6okQ0kgIak/1caf4e8275bb8e8514b7073396553b6a/app_store2_EN.png)
 
 In addition, with the new app you can perform version tests and update it whenever a new version is available, receiving continuous improvements and updates of new features.
 
@@ -42,4 +42,4 @@ To test the customizations on your page, you may work on a different workspace w
 5. Ready! Now you will see how your page will behave before you upload it.
 6. To move My Orders to the production environment (where your customers can actually use it), you must publish the change. To do that, just click on the __Publish__ button.
 
-![app store3 EN](//images.ctfassets.net/alneenqid6w5/Dhrybc8B7qCwacYMmAwcC/7970fef7fc718f082683ad218603a829/app_store3_EN.png)
+![app store3 EN](https://images.ctfassets.net/alneenqid6w5/Dhrybc8B7qCwacYMmAwcC/7970fef7fc718f082683ad218603a829/app_store3_EN.png)
diff --git a/docs/tutorials/en/integrate-with-carrefour.md b/docs/tutorials/en/integrate-with-carrefour.md
index f2752e0b6..32ae5a864 100644
--- a/docs/tutorials/en/integrate-with-carrefour.md
+++ b/docs/tutorials/en/integrate-with-carrefour.md
@@ -28,7 +28,7 @@ On the upper right-hand corner, click on the e-mail (the same that you used for
 
 The key that appears on the screen is the information that you will need to register the integration in the VTEX Bridge module.
 
-![Carrefour1](//images.contentful.com/alneenqid6w5/3J1VMlsGsMswagSeG2y0EK/d054fac671b13f5dca7f627aa5121c97/Carrefour1.png)
+![Carrefour1](https://images.contentful.com/alneenqid6w5/3J1VMlsGsMswagSeG2y0EK/d054fac671b13f5dca7f627aa5121c97/Carrefour1.png)
 
 ### Configuring integration in Bridge
 
diff --git a/docs/tutorials/en/integrating-with-farmacias-app.md b/docs/tutorials/en/integrating-with-farmacias-app.md
index 4b92a6746..1f66b9e20 100644
--- a/docs/tutorials/en/integrating-with-farmacias-app.md
+++ b/docs/tutorials/en/integrating-with-farmacias-app.md
@@ -35,7 +35,7 @@ _**Attention**: these fields must be filled out exactly as described above._
 
 The **role** will be: IntegrationProfile-Fulfillment_Oms, IntegrationProfile-Fulfillment_Gateway
 
-![Farmacias1](//images.contentful.com/alneenqid6w5/2rkEOHXVIEk4q8WiOWCsSs/46449655d8c76e01903a29ec6ed5492d/Farmacias1.png)
+![Farmacias1](https://images.contentful.com/alneenqid6w5/2rkEOHXVIEk4q8WiOWCsSs/46449655d8c76e01903a29ec6ed5492d/Farmacias1.png)
 
 Then, click on **Save**.
 
@@ -51,7 +51,7 @@ Afterwards, you will have to:
 Lastly, the affiliate must be registered, as it is the unique identity of the marketplace in your store. To do this, follow the steps below:
 
 1. Access the **Orders Managment** module;
-2. Click on the **Settings** button;![Farmacias2](//images.contentful.com/alneenqid6w5/7Mekt0KzpmaS4M4uoEu2kC/d0b13138a044072b6ba2c7c89808eacc/Farmacias2.png)
+2. Click on the **Settings** button;![Farmacias2](https://images.contentful.com/alneenqid6w5/7Mekt0KzpmaS4M4uoEu2kC/d0b13138a044072b6ba2c7c89808eacc/Farmacias2.png)
 3. Click on the **Affiliates** tab;
 4. Click on the **New Affiliate** button;
 5. Complete the fields as follows:
@@ -62,7 +62,7 @@ Lastly, the affiliate must be registered, as it is the unique identity of the ma
 **E-mail for notifications**: _e-mail of the person responsible for the integration_;
 **Search Endpoint**: https://integrador.farmaciasapp.com.br/Vtex/api/notification
 
-![Farmacias3](//images.contentful.com/alneenqid6w5/6pnQjxLuhO8cUogU6oYoig/953a840b59416974f9a3baeff39d47cd/Farmacias3.png)
+![Farmacias3](https://images.contentful.com/alneenqid6w5/6pnQjxLuhO8cUogU6oYoig/953a840b59416974f9a3baeff39d47cd/Farmacias3.png)
 
 _When the payments are processed using Farmácias App, the **Usar meu meio de pagamento** option must be disabled. Check this option only for payments processed in different environments, such as payments processed on the VTEX platform._
 
diff --git a/docs/tutorials/en/integration-guide-for-erps-express-catalog.md b/docs/tutorials/en/integration-guide-for-erps-express-catalog.md
index 3cccf6c85..21d8ac19f 100644
--- a/docs/tutorials/en/integration-guide-for-erps-express-catalog.md
+++ b/docs/tutorials/en/integration-guide-for-erps-express-catalog.md
@@ -32,7 +32,7 @@ After the variations and the store marketing structure be defined, the next step
 
 _Flow:_
 
-![image (4)](//images.contentful.com/alneenqid6w5/10TgLjH21wY0c8Q4Ok0Muw/1118844559962f711d34b953f11ebfaf/Component__16_.png)
+![image (4)](https://images.contentful.com/alneenqid6w5/10TgLjH21wY0c8Q4Ok0Muw/1118844559962f711d34b953f11ebfaf/Component__16_.png)
 
 ### Product
 
diff --git a/docs/tutorials/en/integration-guide-for-erps-full-catalog.md b/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
index 8df50aa70..07db17751 100644
--- a/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
+++ b/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
@@ -19,7 +19,7 @@ subcategory: 5fKgQZhrCw88ACy6Su6GUc
 
 This document is intended to assist on the catalog integration (department, category, brand, images, fields, field values, SKUs activation) of the ERP for a store hosted in VTEX. In this type of integration most of the store's management is ERP.
 
-![ERParchitecture](//images.ctfassets.net/alneenqid6w5/zUnuBAtUoo6CQcmCwkoEs/91110c5c16af13c0b9c4fa56f1a8d70b/ERParchitecture.png)
+![ERParchitecture](https://images.ctfassets.net/alneenqid6w5/zUnuBAtUoo6CQcmCwkoEs/91110c5c16af13c0b9c4fa56f1a8d70b/ERParchitecture.png)
 
 In this scenario of complete flow, most of product data and SKUs are handled through the ERP (brand, images, category, activation, etc). The handling of specification fields in this model can be done through REST API, but the best practice would be for the VTEX admin.
 
diff --git a/docs/tutorials/en/integration-guide-for-erps-orders.md b/docs/tutorials/en/integration-guide-for-erps-orders.md
index 3beeb6057..38b105436 100644
--- a/docs/tutorials/en/integration-guide-for-erps-orders.md
+++ b/docs/tutorials/en/integration-guide-for-erps-orders.md
@@ -25,7 +25,7 @@ In this article you will find the primary method for getting the orders you rece
 
 An order integration comprises four moments, each one being a small process in itself.
 
-![ERP Orders 1](//images.contentful.com/alneenqid6w5/7MtCGP7jpKOO2gKa8muGwO/481c6346e0d216f1cbe0588dc79eb617/ERP_Orders_1.png) 
+![ERP Orders 1](https://images.contentful.com/alneenqid6w5/7MtCGP7jpKOO2gKa8muGwO/481c6346e0d216f1cbe0588dc79eb617/ERP_Orders_1.png) 
 
 # Order integration steps
 
@@ -39,7 +39,7 @@ After deciding it is time to take an order into your fulfillment platform, you j
 
 In the end, for the processed orders, you send a “Start Handling” message the OMS.
 
-![ERP Orders 2](//images.contentful.com/alneenqid6w5/3SUWupt48gSG2iqM2q8qEA/28a578fa22944fac74f7f9d9121506ca/orders-integration-download.png) 
+![ERP Orders 2](https://images.contentful.com/alneenqid6w5/3SUWupt48gSG2iqM2q8qEA/28a578fa22944fac74f7f9d9121506ca/orders-integration-download.png) 
 
 ### API calls
 
@@ -112,7 +112,7 @@ Now the order is being processed by your fulfillment platform. During this proce
 
 When you are ready to deliver the order, it is time to tell VTEX you are ready, so that payment authorization may be captured and your customer be notified about the progress.
 
-![ERP Orders 3](//images.contentful.com/alneenqid6w5/5UGtFvC0UwoEoEcqQk8kGa/249a691293a7f195257f5c161565cf5c/ERP_Orders_3.png)
+![ERP Orders 3](https://images.contentful.com/alneenqid6w5/5UGtFvC0UwoEoEcqQk8kGa/249a691293a7f195257f5c161565cf5c/ERP_Orders_3.png)
 
 ### API calls
 
@@ -185,7 +185,7 @@ There is no hard limit in the number of tracking messages that can be added to a
 
 It's important to notice that this information is actually a set of attributes of the invoice. So, it can be sent together with the invoice, when sending it to the web store in case you have this information at that time.
 
-![ERP Orders 4](//images.contentful.com/alneenqid6w5/1v0Mk0y5a0uAmgcGmgAks4/6d416ec4b79faa89330d683a32c6905c/ERP_Orders_4.png) 
+![ERP Orders 4](https://images.contentful.com/alneenqid6w5/1v0Mk0y5a0uAmgcGmgAks4/6d416ec4b79faa89330d683a32c6905c/ERP_Orders_4.png) 
 
 ### API calls
 
diff --git a/docs/tutorials/en/integration-interfaces.md b/docs/tutorials/en/integration-interfaces.md
index 74dade901..507c159a7 100644
--- a/docs/tutorials/en/integration-interfaces.md
+++ b/docs/tutorials/en/integration-interfaces.md
@@ -19,7 +19,7 @@ Integration with an ERP system enables control of your inventory regarding order
 
 On the VTEX system, you will be able to integrate your ERP through several interfaces: __API REST__ (JSON language) and __WebService__ (SOAP – XML language) – which is already out of use.
 
-![ERP-VTEX-Integration](//images.contentful.com/alneenqid6w5/2wnH4XIbPmqqkCIKGMywo/aacb3904d7c7af2dbee7a182459d9203/ERP-VTEX-Integration.png)
+![ERP-VTEX-Integration](https://images.contentful.com/alneenqid6w5/2wnH4XIbPmqqkCIKGMywo/aacb3904d7c7af2dbee7a182459d9203/ERP-VTEX-Integration.png)
 
 In addition to ERP, for the transmission to occur, there must be a system in place to support the communication between ERP and VTEX. This system is named as “__Integrator__”. In general, ERP develops its own integrator, but it may also be developed by the store itself, or by an agency contracted by the store.
 
diff --git a/docs/tutorials/en/integration-with-google-tag-manager.md b/docs/tutorials/en/integration-with-google-tag-manager.md
index 95e2ec095..0e289971a 100644
--- a/docs/tutorials/en/integration-with-google-tag-manager.md
+++ b/docs/tutorials/en/integration-with-google-tag-manager.md
@@ -48,7 +48,7 @@ After this, you have to set up the store identification code from Tag Manager on
 4. In the __Google Tag Manager__ field, enter the store identification code in `GTM-XXXX` format, as shown in the image below.
 5. Click `Save`. 
 
-![Google Tag Manager](//images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/c16814591d79d4165f6c6c7954c0c48a/Google_Tag_Manager_-_EN.PNG)
+![Google Tag Manager](https://images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/c16814591d79d4165f6c6c7954c0c48a/Google_Tag_Manager_-_EN.PNG)
 
 To check available events (triggers) and variables on the pages, which will be used in the tags, you can use the Google Tag Manager preview mode. For more information, check the [Google Tag Manager documentation](https://support.google.com/tagmanager/answer/6107056?hl=pt-BR).
 
diff --git a/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
index f1f0b5094..adfe3f1ef 100644
--- a/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
@@ -33,7 +33,7 @@ The suggestions are displayed in two categories in the list of synonyms, as show
 * **New suggestions:** Suggestions generated by the platform that have not yet been viewed.
 * **Saved suggestions:** Suggestions saved for later, as described in step 5 of the [Reviewing suggestions](#revisar-sugestoes) section.
 
-![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
+![synonym-suggestion-list-es](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
 
 You can review the suggestions and choose to save for later, decline, edit, or approve. See the steps in the next section.
 
@@ -48,7 +48,7 @@ Follow these instructions to view the synonym suggestions and choose whether to
     If you click `Not Now`, the suggestions will remain in the **New suggestions** box, indicating the number of generated suggestions. To review them, click `Review`. 
 4. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
 
-   ![synonym-suggestion-en](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
+   ![synonym-suggestion-en](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
 
 5. To review each suggestion, choose one of the following actions:
     * <i class="fas fa-bookmark"></i> **Save for Later:** Removes the suggestion from the **New suggestions** count and stores it in the **Saved suggestions** box. To review the saved suggestions later, click `Review`.
diff --git a/docs/tutorials/en/intelligent-synonyms.md b/docs/tutorials/en/intelligent-synonyms.md
index 85171b8df..a5065203e 100644
--- a/docs/tutorials/en/intelligent-synonyms.md
+++ b/docs/tutorials/en/intelligent-synonyms.md
@@ -33,7 +33,7 @@ The suggestions are displayed in two categories in the list of synonyms, as show
 * **New suggestions:** Suggestions generated by the platform that have not yet been viewed.
 * **Saved suggestions:** Suggestions saved for later, as described in step 5 of the [Reviewing suggestions](#revisar-sugestoes) section.
 
-![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
+![synonym-suggestion-list-es](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/abd9312a5c10df0cfd77e01effd2225b/synonym-suggestion-list-es.png)
 
 You can review the suggestions and choose to save for later, decline, edit, or approve. See the steps in the next section.
 
@@ -48,7 +48,7 @@ Follow these instructions to view the synonym suggestions and choose whether to
     If you click `Not Now`, the suggestions will remain in the **New suggestions** box, indicating the number of generated suggestions. To review them, click `Review`. 
 4. A modal will display the first synonym suggestion. Each suggestion shows the searched term, the proposed synonym, and the number of times customers have used the second term to replace the original term in the last 30 days.
 
-   ![synonym-suggestion-en](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
+   ![synonym-suggestion-en](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/0937f850f1c2f9b0eae863065f486d1b/synonym-suggestion-en.png)
 
 5. To review each suggestion, choose one of the following actions:
     * <i class="fas fa-bookmark"></i> **Save for Later:** Removes the suggestion from the **New suggestions** count and stores it in the **Saved suggestions** box. To review the saved suggestions later, click `Review`.
diff --git a/docs/tutorials/en/interacting-with-masterdata-through-graphql.md b/docs/tutorials/en/interacting-with-masterdata-through-graphql.md
index 5ca765ee0..d7b413796 100644
--- a/docs/tutorials/en/interacting-with-masterdata-through-graphql.md
+++ b/docs/tutorials/en/interacting-with-masterdata-through-graphql.md
@@ -27,7 +27,7 @@ Start off by making sure you have the latest version of the VTEX CLI and cloning
 
 run `vtex init` and select `graphql getting-started`
 
-![Screen Shot 2019-01-16 at 15.00.29](//images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
+![Screen Shot 2019-01-16 at 15.00.29](https://images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
 
 We'll be using it's basic structure to adapt to our needs.
 
@@ -149,15 +149,15 @@ Open up Postman and type in the following search:
 
 Choose an ID, copy it.  We'll be pasting it in our query.
 
-![Screen Shot 2019-01-16 at 16.14.31](//images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
+![Screen Shot 2019-01-16 at 16.14.31](https://images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
 
-![Screen Shot 2019-01-16 at 17.34.04](//images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
+![Screen Shot 2019-01-16 at 17.34.04](https://images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
 
 You should now see the output light up on the right. 
 Congratulations! You've already acomplished a simple query in record time.
 
 You can look under the hood by switching back to the terminal and seeing GraphQL resolving the queries how you normally would have.
-![Screen Shot 2019-01-16 at 16.29.03](//images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
+![Screen Shot 2019-01-16 at 16.29.03](https://images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
 
 
 **But what if we want to SEARCH by using all possible filters?**
@@ -269,6 +269,6 @@ query{
 
 ```
 
-![Screen Shot 2019-01-16 at 17.23.00](//images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
+![Screen Shot 2019-01-16 at 17.23.00](https://images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
 
 And there you have it :) Happy coding!
diff --git a/docs/tutorials/en/interaction-details.md b/docs/tutorials/en/interaction-details.md
index 57b542d31..bcddf1712 100644
--- a/docs/tutorials/en/interaction-details.md
+++ b/docs/tutorials/en/interaction-details.md
@@ -39,7 +39,7 @@ In <b>Offer Management</b> , you can track offers using <a href="https://help.vt
 </div>
 
 ## Header
-![Interaction details PT cabeçalho](//images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/d28534c5926b61794e3b16ac91636f86/Interaction_details_EN_cabe__alho.jpg)
+![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/d28534c5926b61794e3b16ac91636f86/Interaction_details_EN_cabe__alho.jpg)
 The *header* summarizes the offer’s main information for quick viewing, such as the SKU name, the logo of the channel it was sent to, its ID on the VTEX platform and on the channel.
 
 ## Interaction result
@@ -48,23 +48,23 @@ The *header* summarizes the offer’s main information for quick viewing, such a
 The *Interaction result* block provides information on the effect of the interaction on the offer, based on the combination of logs in the interaction. The status of an offer is determined by the result of its interactions. It indicates whether it was possible to send the offer to the channel and sync it. Here are possible interaction results: 
 
 ### Result: Success
-![Interaction details PT resultado sucesso](//images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/e0f5c0733c6ad25cc3eda476500bcd6a/Interaction_details_EN_resultado_sucesso.jpg)
+![Interaction details PT resultado sucesso](https://images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/e0f5c0733c6ad25cc3eda476500bcd6a/Interaction_details_EN_resultado_sucesso.jpg)
 The *Success* result indicates that the interaction fulfilled its expected effect. It means that the offer has been sent to the channel correctly, or that the offer’s price, inventory, or catalog information has been updated. 
 
 ### Result: Failure
-![Interaction details PT resultado falha](//images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/c7dce5355ca57a597664740779478344/Interaction_details_ES_resultado_falha.jpg)
+![Interaction details PT resultado falha](https://images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/c7dce5355ca57a597664740779478344/Interaction_details_ES_resultado_falha.jpg)
 The *Failure* result indicates that the system could not complete the interaction due to an issue. This result leads to the *Error* status in the offer, preventing it from being sent or updated on the channel. When the interaction result is *Failure*, the issues detected will be listed and you can expand them for more information.
 
 ### Result: Notification
-![Interaction details PT resultado aviso](//images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/f9983790af5371a5412ba1127390655e/Interaction_details_EN_resultado_aviso.jpg)
+![Interaction details PT resultado aviso](https://images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/f9983790af5371a5412ba1127390655e/Interaction_details_EN_resultado_aviso.jpg)
 The *Notification* result provides information about the offer’s sending and syncing processes, making it easier for the seller to monitor it.
 
 ### Result: Processing
-![Interaction details PT resultado processing](//images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/e9a13da08b1a3e1b572c6363182d15e9/Interaction_details_EN_resultado_processing.jpg)
+![Interaction details PT resultado processing](https://images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/e9a13da08b1a3e1b572c6363182d15e9/Interaction_details_EN_resultado_processing.jpg)
 The *Processing* result means the interaction has not been completed and is still in progress. This is a temporary status because once the interaction's process is completed, it can only result in `success`, `failure`, or `notification`. 
 
 ## Timeline
-![Interaction details EN linha do tempo](//images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/67355b2fccc741b3774e3789a17773e5/Interaction_details_EN_linha_do_tempo.jpg)
+![Interaction details EN linha do tempo](https://images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/67355b2fccc741b3774e3789a17773e5/Interaction_details_EN_linha_do_tempo.jpg)
 The system generates interactions to update information, and they use logs to make the necessary actions during the process. 
 
 The timeline on the **Interaction details** page displays the logs generated for the interaction in chronological order, and the information is available for consultation for ten days. Once the interaction objective is achieved and no further logs are to be generated, the interaction is automatically closed. The timeline displays the following data:
diff --git a/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
index 003f5e460..1eaf06bc0 100644
--- a/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
@@ -26,7 +26,7 @@ The following data set is displayed on the __All orders__ screen in the __Orders
 
 Alongside each of these values, a percentage representing the variation against today's orders will appear.
 
-![order-metric-en](//images.ctfassets.net/alneenqid6w5/6gLFOziUnYEGuyU6S8iUuA/58c55d9286f28db09faf423fa6c5d2da/order-metric-en.png)
+![order-metric-en](https://images.ctfassets.net/alneenqid6w5/6gLFOziUnYEGuyU6S8iUuA/58c55d9286f28db09faf423fa6c5d2da/order-metric-en.png)
 
 In the screenshot of the metrics above, the following information will be displayed:
 
diff --git a/docs/tutorials/en/introduction-to-vtex-apis.md b/docs/tutorials/en/introduction-to-vtex-apis.md
index 88756363c..61592b17a 100644
--- a/docs/tutorials/en/introduction-to-vtex-apis.md
+++ b/docs/tutorials/en/introduction-to-vtex-apis.md
@@ -62,7 +62,7 @@ It must contain:
  
 In Postman, the URL must be included in the field informed below:
 
-![APIs1](//images.contentful.com/alneenqid6w5/f53Sv9BCZqK4EI0sYmW8A/63e512b825d47daa2f685ae5bb9df553/APIs1.png)
+![APIs1](https://images.contentful.com/alneenqid6w5/f53Sv9BCZqK4EI0sYmW8A/63e512b825d47daa2f685ae5bb9df553/APIs1.png)
 
 
 ****
@@ -81,7 +81,7 @@ But you do not need to come to this conclusion alone.  When making an API availa
  
 In Postman, the method is selected on the left of the URL field.
 
-![APIs2](//images.contentful.com/alneenqid6w5/wDClzNRJDiCE6OKecOAs4/8545dbce3bc2ee546b8cf497750360b5/APIs2.png)
+![APIs2](https://images.contentful.com/alneenqid6w5/wDClzNRJDiCE6OKecOAs4/8545dbce3bc2ee546b8cf497750360b5/APIs2.png)
 
 ****
 
@@ -93,7 +93,7 @@ When a new user is created for your store, a specific profile of access to the m
  
 In Postman, AppKey and AppToken must be entered in the **Headers** tab. In the first header, enter `X-VTEX-API-AppKey` and then AppKey. In the second line, enter `X-VTEX-API-AppToken` and then your AppToken. To know how to generate your AppKey and your AppToken, read the article [Creating appKeys and appTokens to authenticate integrations](/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations).
 
-![APIs3](//images.contentful.com/alneenqid6w5/4z9W9DYJEcYa2WGIoSceEE/166d8adc70a8176af1a7fb04e5cdbb65/APIs3.png)
+![APIs3](https://images.contentful.com/alneenqid6w5/4z9W9DYJEcYa2WGIoSceEE/166d8adc70a8176af1a7fb04e5cdbb65/APIs3.png)
 
 ****
 
@@ -113,11 +113,11 @@ VTEX’s APIs are available at our Help Center, in section [Developer Docs](/en/
  
 They are divided by module or functionality.  Click on one of them to find the corresponding APIs, as well as indications about their relevant method, URL and Headers. Some APIs also include the code that must be informed in the Body.
  
-![APIs4](//images.contentful.com/alneenqid6w5/1JZCBHsm6UGS2EwuGqoGm4/a61e000b81acd2f06a1021f70c12e31b/APIs4.png)
+![APIs4](https://images.contentful.com/alneenqid6w5/1JZCBHsm6UGS2EwuGqoGm4/a61e000b81acd2f06a1021f70c12e31b/APIs4.png)
  
 On the right side of these indications, Postman displays one Sample Request for each API. In accordance with the wording selected on the check box placed above it, the Sample Request shows the application of the request in the code.
 
-![sample request](//images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
+![sample request](https://images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
  
 Some APIs also have a Sample Response, which is an example of a response to that request.
  
diff --git a/docs/tutorials/en/kit-registration.md b/docs/tutorials/en/kit-registration.md
index aca0e8dcd..eb48426ab 100644
--- a/docs/tutorials/en/kit-registration.md
+++ b/docs/tutorials/en/kit-registration.md
@@ -26,7 +26,7 @@ A kit may or may not allow for its components to be sold separately. See the dif
 
 To set up the kit, all its products – that is, its components – must have already been created. See the example below:
 
-![01-components EN](//images.ctfassets.net/alneenqid6w5/3pQ4a93uZi8sqQA2oGywi4/4c0acd198d16920872025de5d95ed61f/01-components_EN.png)
+![01-components EN](https://images.ctfassets.net/alneenqid6w5/3pQ4a93uZi8sqQA2oGywi4/4c0acd198d16920872025de5d95ed61f/01-components_EN.png)
 
 After creating all component products, we can move on to defining the kit’s settings.
 
@@ -37,7 +37,7 @@ After creating all component products, we can move on to defining the kit’s se
 5. If you would like a look kit, click on the option __Bundle with SKUs sold separately__.
 6. Click on `Save`.
 
-![02-kit EN](//images.ctfassets.net/alneenqid6w5/5O4ZP4iGI0YE60aMOkAI4Q/830694f23e7b6b7d2e4b0cd6c2438c41/02-kit_EN.png)
+![02-kit EN](https://images.ctfassets.net/alneenqid6w5/5O4ZP4iGI0YE60aMOkAI4Q/830694f23e7b6b7d2e4b0cd6c2438c41/02-kit_EN.png)
 
 ## Associating components
 
@@ -52,9 +52,9 @@ After the kit product has been created, you must associate the components, accor
 7. Enter the SKU unit price inside the kit.
 6. Click on `Save`.
 
-![03-add component to kit EN](//images.ctfassets.net/alneenqid6w5/1qBz4qjkAQ8OE8kMMeiw0o/eb5437d1d8a7c40e30998f2ad3723c5e/03-add_component_to_kit_EN.gif)
+![03-add component to kit EN](https://images.ctfassets.net/alneenqid6w5/1qBz4qjkAQ8OE8kMMeiw0o/eb5437d1d8a7c40e30998f2ad3723c5e/03-add_component_to_kit_EN.gif)
 
-![04-kit in cart ALL](//images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
+![04-kit in cart ALL](https://images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
 
 ## Kit Weight
 
@@ -83,7 +83,7 @@ You may only change the final price of the kit by directly accessing the pricing
 Please note that any change in any component will generate a new final price, updating what had been previously registered. 
 
 Merely changing the final price will not update the price of the components.
-![06-price list EN](//images.ctfassets.net/alneenqid6w5/1OFwACSPPuCiiWA4YqYa28/5b4ef3a2e50e78b0be869c97288e5778/06-price_list_EN.png)
+![06-price list EN](https://images.ctfassets.net/alneenqid6w5/1OFwACSPPuCiiWA4YqYa28/5b4ef3a2e50e78b0be869c97288e5778/06-price_list_EN.png)
 
 ### Learn more
 
diff --git a/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
index f1d606981..3e68138f7 100644
--- a/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
+++ b/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
@@ -35,7 +35,7 @@ To configure lead time via API, see <a href="https://developers.vtex.com/docs/ap
 
 When configured, the lead time is an additional time comprising the shipping time for the order displayed to the customer at checkout. The image below shows how the total time is calculated:
 
-![lead_time_image_total_time_EN](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
+![lead_time_image_total_time_EN](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/8a3f64f6c30a7a513bb98d0c97b355a3/lead_time_image_total_time_EN.png)
 
 - **Lead time:** The amount of time that can be configured for a warehouse SKU. For example, this period could correspond to the item's handling or manufacturing time. This configuration is optional and, by default, is set as zero days
 - [Warehouse time:](https://help.vtex.com/en/tutorial/gerenciar-estoque--tutorials_137) Time the SKU takes to leave a warehouse and arrive at a [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). This configuration is required, but you can set the time to zero.
@@ -80,7 +80,7 @@ To configure the lead time for a SKU, follow the steps below:
 1. In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type **Inventory Management** in the search bar at the top of the page.
 2. Select the SKU you want to configure. You can use the search bar and filters.
 3. In the SKU row and the **Lead time (days)** column, enter the days you want.
-  ![lead_time_inventory_management_EN](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png)
+  ![lead_time_inventory_management_EN](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png)
 4. Click `Save` at the bottom of the page.
 
 <div class = "alert alert-info">
diff --git a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
index 7b384020a..049acfb82 100644
--- a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
+++ b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -48,7 +48,7 @@ After creating a cluster, you must include a rule in the trade policy allowing a
 3. In the **Conditional Rule** field, enter the value **ClusterName=”true”**. Note that the value **ClusterName** must be changed to the name of the field in the data entity.
 4. Click on the **Save** button.
 
-![Catalog EN](//images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/8d11cabbb359f20a73667b2a787e1ee4/politicas_comerciais_EN.png)
+![Catalog EN](https://images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/8d11cabbb359f20a73667b2a787e1ee4/politicas_comerciais_EN.png)
 
 In the above configuration, only customers with the value “true” (using a Boolean field – where values are either true or false) can access the site.
 
diff --git a/docs/tutorials/en/linking-an-account-name-to-a-website-binding.md b/docs/tutorials/en/linking-an-account-name-to-a-website-binding.md
index 578febd7d..848e5d093 100644
--- a/docs/tutorials/en/linking-an-account-name-to-a-website-binding.md
+++ b/docs/tutorials/en/linking-an-account-name-to-a-website-binding.md
@@ -21,9 +21,9 @@ One of the first things you have to do in your web site is to link it to a store
 1. In the VTEX Admin, access **Storefront > Layout**.
 2. Click the __CMS__ folder.
 3. Click the __Sites and channels__ folder.
-4. Click on the desired Website.![websites](//images.contentful.com/alneenqid6w5/56BRjkYWyIwKogAI0oMmSM/0910a749d03b6fd8d596ce6361a21045/websites.png)
+4. Click on the desired Website.![websites](https://images.contentful.com/alneenqid6w5/56BRjkYWyIwKogAI0oMmSM/0910a749d03b6fd8d596ce6361a21045/websites.png)
 5. Click on __Save Website__.
-6. Click __Add__.![addBinding](//images.contentful.com/alneenqid6w5/r0P8ZE9LNesKoeGewcWOu/527511bc3ae48875fe1a6421a1db5f42/addBinding.png)
-7. Select the store name.![chooseBinding](//images.contentful.com/alneenqid6w5/3nFPaDlnaEG2EqIMM8gCe0/188754ebaa172cef01a9212eea168e46/chooseBinding.png)
-8. Check the trade policy or trade policies that will be tied to this store.![bindingSalesPolicy](//images.contentful.com/alneenqid6w5/5FFxnelVTyCu04a6EkiEkS/30905c7f368a1393100f118fd70fcb02/bindingSalesPolicy.png)
+6. Click __Add__.![addBinding](https://images.contentful.com/alneenqid6w5/r0P8ZE9LNesKoeGewcWOu/527511bc3ae48875fe1a6421a1db5f42/addBinding.png)
+7. Select the store name.![chooseBinding](https://images.contentful.com/alneenqid6w5/3nFPaDlnaEG2EqIMM8gCe0/188754ebaa172cef01a9212eea168e46/chooseBinding.png)
+8. Check the trade policy or trade policies that will be tied to this store.![bindingSalesPolicy](https://images.contentful.com/alneenqid6w5/5FFxnelVTyCu04a6EkiEkS/30905c7f368a1393100f118fd70fcb02/bindingSalesPolicy.png)
 9. Click __Save Binding__.
diff --git a/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md b/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md
index a8e27f9cb..1900ac4da 100644
--- a/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md
+++ b/docs/tutorials/en/linking-urls-to-banners-using-the-site-editor.md
@@ -19,7 +19,7 @@ You can configure one of your store’s banners to redirect users to a page of y
 
 ## Internal URLs
 
-![internal-url](//images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3a727394e2f315558ccb783aa9cccb20/image2.png)
+![internal-url](https://images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3a727394e2f315558ccb783aa9cccb20/image2.png)
 
 1. In the VTEX Admin, access **Storefront > Site Editor**.
 2. Select a __Carousel__ block and choose the banner whose content you want to edit.
@@ -33,7 +33,7 @@ The <i>Banner target page</i> and <i>Params</i> fields have been deprecated. The
 
 ## External URLs
 
-![external-url](//images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/43eece9d63ba77a5e63945c17bc74e7c/image1.png)
+![external-url](https://images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/43eece9d63ba77a5e63945c17bc74e7c/image1.png)
 
 1. In the VTEX Admin, access **Storefront > Site Editor**.
 2. Select a __Carousel__ block and choose the banner whose content you want to edit.
diff --git a/docs/tutorials/en/list-the-account-workspaces.md b/docs/tutorials/en/list-the-account-workspaces.md
index 712731574..249750ef3 100644
--- a/docs/tutorials/en/list-the-account-workspaces.md
+++ b/docs/tutorials/en/list-the-account-workspaces.md
@@ -21,7 +21,7 @@ To see the workspaces that currently exist in an account, simply use the followi
 
 Check out this example:
 
-![workspace list](//images.contentful.com/alneenqid6w5/2au4D7r6YkmskO0Ko8esC6/aa635baf0e6f543c0e08ee2613e20127/workspace_list.png)
+![workspace list](https://images.contentful.com/alneenqid6w5/2au4D7r6YkmskO0Ko8esC6/aa635baf0e6f543c0e08ee2613e20127/workspace_list.png)
 
 The columns that will appear are as follows:
 
diff --git a/docs/tutorials/en/listing-apps-installed-in-the-store.md b/docs/tutorials/en/listing-apps-installed-in-the-store.md
index 382f2556c..a85fcfe5a 100644
--- a/docs/tutorials/en/listing-apps-installed-in-the-store.md
+++ b/docs/tutorials/en/listing-apps-installed-in-the-store.md
@@ -26,6 +26,6 @@ You will see a table with the following columns:
 - __Version__: version of the app.
 - __Linked__: whether or not the app is linked.
 
-![appList](//images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
+![appList](https://images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
 
 There are no limits for apps that can be created for an account.
diff --git a/docs/tutorials/en/loading-dock.md b/docs/tutorials/en/loading-dock.md
index f24d80b6d..fd04d290b 100644
--- a/docs/tutorials/en/loading-dock.md
+++ b/docs/tutorials/en/loading-dock.md
@@ -20,7 +20,7 @@ The loading dock is part of the logistics system and usually acts as an intermed
 
 On VTEX, the loading dock is an intermediary between storing items and delivering orders. The loading dock integrates the necessary parts for your store’s logistics system: [Warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb), [Trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) and [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140).
 
-![Doca EN](//images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/0e98be333d982b352836b24b72f65997/Doca_EN.svg)
+![Doca EN](https://images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/0e98be333d982b352836b24b72f65997/Doca_EN.svg)
 
 <div class = "alert alert-info">
 The Warehouse is the physical storage for the goods sold by the store; the Trade policy is the configuration of the store's sales strategies; and the Shipping policy is a set of rules that define the shipping options and conditions.
diff --git a/docs/tutorials/en/log-in-to-the-account.md b/docs/tutorials/en/log-in-to-the-account.md
index 33155525f..25b1f8758 100644
--- a/docs/tutorials/en/log-in-to-the-account.md
+++ b/docs/tutorials/en/log-in-to-the-account.md
@@ -21,6 +21,6 @@ To sign in to the store account, enter the terminal and type:
 
 The terminal will request the Account, that is, the account name of the store.
 
-![vtex login](//images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
+![vtex login](https://images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
 
 After entering the Account, inform the password, if necessary, and that's it: you're signed in to your account!
diff --git a/docs/tutorials/en/logging-in-to-the-account-with-vtex-io.md b/docs/tutorials/en/logging-in-to-the-account-with-vtex-io.md
index c78dae7f9..9d7e63d3e 100644
--- a/docs/tutorials/en/logging-in-to-the-account-with-vtex-io.md
+++ b/docs/tutorials/en/logging-in-to-the-account-with-vtex-io.md
@@ -19,6 +19,6 @@ To sign in to the store account, enter the terminal and type `vtex login`.
 
 The terminal will request the Account, that is, the account name of the store.
 
-![vtex login](//images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
+![vtex login](https://images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
 
 After entering the Account, inform the password if necessary and that's it: you're signed in to your account!
diff --git a/docs/tutorials/en/logistics-in-the-grocery-segment-supermarkets.md b/docs/tutorials/en/logistics-in-the-grocery-segment-supermarkets.md
index 0e97f88f3..fcc38fce6 100644
--- a/docs/tutorials/en/logistics-in-the-grocery-segment-supermarkets.md
+++ b/docs/tutorials/en/logistics-in-the-grocery-segment-supermarkets.md
@@ -27,7 +27,7 @@ Fulfillment is nothing else than the process of analysis of orders, separation (
 
 In most conventional e-commerce operations, we have a warehouse that represents the stock. But, on the majority of grocery operations, this warehouse is not practiced due to perishability, fast detriment of goods (validity) and the wide variety of product mix.
 
-![](//images.contentful.com/alneenqid6w5/5VsYaqLOz6iq2Q6KEGiOIw/ccca0432aef12d539de3d6d9301383df/mapaARMAZEM1.jpg)
+![](https://images.contentful.com/alneenqid6w5/5VsYaqLOz6iq2Q6KEGiOIw/ccca0432aef12d539de3d6d9301383df/mapaARMAZEM1.jpg)
 
 In this context, the existence of a warehouse that represents the stock would demand almost twice of the required space, together with a major order flow before the detriment of the products.
 
@@ -53,7 +53,7 @@ From average volumes (over 30 daily requests) on, the most recommended picking m
 1. Group all products, without order distinction. This reduces changes in product addressing.
 2. After the separation of the products, direct them to the area where orders are assembled. These waves can be organized by carrier, routes, docks or lot.
 
-![](//images.contentful.com/alneenqid6w5/5rrGJF8WL60uOmgeEia08o/5b66179fe04f4fd6c1cddcd9c12f774f/pickingonda2.jpg)
+![](https://images.contentful.com/alneenqid6w5/5rrGJF8WL60uOmgeEia08o/5b66179fe04f4fd6c1cddcd9c12f774f/pickingonda2.jpg)
 
 ## _Wave_ Picking _by lot_ favors packing
 
@@ -67,7 +67,7 @@ Due to the wide range of salable products in the grocery, "wave picking by lot"
 6. Fragile
 7. Frozen
 
-![](//images.contentful.com/alneenqid6w5/tepJVna9uoiKUqeUeOQM4/e9b1e3bca826f9a4bb8f662d34108339/mapa.jpg)
+![](https://images.contentful.com/alneenqid6w5/tepJVna9uoiKUqeUeOQM4/e9b1e3bca826f9a4bb8f662d34108339/mapa.jpg)
 
 Besides being essential for separation, the lot is very important for Packing, once each lot type has its particular characteristics and requirements:
 
@@ -86,7 +86,7 @@ Examples: eggs, fruits, bomboniere, potatoes etc
 **7. Frozen: **must be transported in coolers, and remain preserved for up to 6 hours with the aid of ice. Ice should preferably be sealed in plastic containers in order to avoid water contact and to allow input reuse.
 Examples: Ice cream, desserts, breaded products, ready meals, burgers, snacks, etc.
 
-![](//images.contentful.com/alneenqid6w5/ptgKUEgHBu4syuiuS46mS/ae31c4cbd90a04a8d0dc19a3e2a6b669/packing.jpg)
+![](https://images.contentful.com/alneenqid6w5/ptgKUEgHBu4syuiuS46mS/ae31c4cbd90a04a8d0dc19a3e2a6b669/packing.jpg)
 
 ## Dispatch, transport and delivery
 
diff --git a/docs/tutorials/en/logistics-module-overview.md b/docs/tutorials/en/logistics-module-overview.md
index aa95c230e..f777d567a 100644
--- a/docs/tutorials/en/logistics-module-overview.md
+++ b/docs/tutorials/en/logistics-module-overview.md
@@ -27,7 +27,7 @@ That's where you can register the relation between **[Warehouse](https://help.vt
 
 That's where you can register the set prices and delivery time for a particular ZIP code range, considering cubic weight, dimensions, among other factors.
 
-![tarifas-envioEN](//images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/217dcd115a91f09f1e2fd9735a1a6326/tarifas_envioEN.png)
+![tarifas-envioEN](https://images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/217dcd115a91f09f1e2fd9735a1a6326/tarifas_envioEN.png)
 
 - [Shipping rates](https://help.vtex.com/en/tutorial/shipping-rates--1Balpg3rv0854udEPedvMM)
 
@@ -37,35 +37,35 @@ Here you can play with different scenarios for the delivery of your product, cho
 
 this section then shows the values and the carriers related to the delivery, dimension and weight of the products, price of the delivery and estimated time, besides additional details on the Zip Code range values, percentages that vary according to the product weight range, volume, additional value per gram, cost to the dock, cubic factor and cubic weight.
 
-![simulador envioEN](//images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/3defae0446513bfa01b1a2c9b648492c/simulador_envioEN.png)
+![simulador envioEN](https://images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/3defae0446513bfa01b1a2c9b648492c/simulador_envioEN.png)
 - [How to simulate a shipping](http://help.vtex.com/en/tutorial/freight-simulation)
 
 ## Inventory
 
 A place to manage and track the stock movement held in store products. It registers the reservations made on a product so far and if they have been confirmed or not.
 
-![gerenciar inventarioEN](//images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/e2938a93d57002ec668b1e99726a9b30/gerenciar_inventarioEN.png)
+![gerenciar inventarioEN](https://images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/e2938a93d57002ec668b1e99726a9b30/gerenciar_inventarioEN.png)
 - [Managing inventory](http://help.vtex.com/en/tutorial/managing-stock-items)
 
 ## Geolocation shipping
 
 Here you can build polygons for a specific logistic service. That’s typically used in rural and industrial areas, for example, where the division is made by lots, or in hazardous areas, where it's necessary to avoid determined sites. The feature’s structure is dynamic, so that you can easily draw on the map the area to be delimited.
 
-![geolocalizaçaoEN](//images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/192f4e00b0517e5ee00249a3de300125/geolocaliza__aoEN.png)
+![geolocalizaçaoEN](https://images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/192f4e00b0517e5ee00249a3de300125/geolocaliza__aoEN.png)
 - [Geolocation](http://help.vtex.com/en/tutorial/registering-geolocation)
 
 ## Pickup points
 
 Here you can delete, edit and register a Pickup Point. As a new delivery channel option, the Pickup Point feature provides greater flexibility and purchase experience to the customer as it allows the order pickup to be made in a physical point.
 
-![pontos retiradaEN](//images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/43fa5c2895d2e53ea19c6ac2a60dd93e/pontos_retiradaEN.png)
+![pontos retiradaEN](https://images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/43fa5c2895d2e53ea19c6ac2a60dd93e/pontos_retiradaEN.png)
 - [Registering Pickup Points](http://help.vtex.com/en/tutorial/registering-pickup-points)
 
 ## Holidays
 
 Here it is possible to register the days that **will not** be considered as useful for your store. The module will consider the holidays registered on this section and these days will not be counted in the delivery deadline.
 
-![feriadoEN](//images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/0b78db315a91567102ebeb81f864cdef/feriadoEN.png)
+![feriadoEN](https://images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/0b78db315a91567102ebeb81f864cdef/feriadoEN.png)
 - [Registering Holidays](http://help.vtex.com/en/tutorial/registering-holidays)
 
 ## General settings
diff --git a/docs/tutorials/en/making-a-master-data-field-editable.md b/docs/tutorials/en/making-a-master-data-field-editable.md
index 9abdaadfa..d9fb959bc 100644
--- a/docs/tutorials/en/making-a-master-data-field-editable.md
+++ b/docs/tutorials/en/making-a-master-data-field-editable.md
@@ -23,7 +23,7 @@ By default, not all the Master Data fields can be edited. To change this, procee
 2. Choose the application you want, and click on the cog symbol <i class="fas fa-cog"></i>.
 3. Click on the edition icon <i class="fas fa-edit"></i> for the form you want to change.
 4. Click on the tab **Layout Schemas**.
-5. Click on the edition icon <i class="fas fa-edit"></i> beside the field you want to change. ![master-data-edit-field-layout](//images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/b369c1c29a118ce9a9a1d11d78d3bede/Group_2.png)
+5. Click on the edition icon <i class="fas fa-edit"></i> beside the field you want to change. ![master-data-edit-field-layout](https://images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/b369c1c29a118ce9a9a1d11d78d3bede/Group_2.png)
 6. Uncheck the option **Display field as read-only**.
 7. Click on the `OK` button.
 8. Click on the `Save` button.
diff --git a/docs/tutorials/en/manage-the-sales-comissions-report.md b/docs/tutorials/en/manage-the-sales-comissions-report.md
index cd2163639..d634351a6 100644
--- a/docs/tutorials/en/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/en/manage-the-sales-comissions-report.md
@@ -61,7 +61,7 @@ Generating the report may take a while if the volume of data is big. In such cas
 Leaving the page will not affect the operation.
 </div>
 
-![Sales Comission Report EN](//images.ctfassets.net/alneenqid6w5/3WoTE8ibcuYshdJf5sT6KV/e30dfb7f7de7b6dbcd506782e405d470/image.png)
+![Sales Comission Report EN](https://images.ctfassets.net/alneenqid6w5/3WoTE8ibcuYshdJf5sT6KV/e30dfb7f7de7b6dbcd506782e405d470/image.png)
 
 Later, you can also download the recently generated report using a link provided in the list of reports.  
 
diff --git a/docs/tutorials/en/managing-b2b-organizations.md b/docs/tutorials/en/managing-b2b-organizations.md
index 53a451ea8..6a9842adc 100644
--- a/docs/tutorials/en/managing-b2b-organizations.md
+++ b/docs/tutorials/en/managing-b2b-organizations.md
@@ -47,7 +47,7 @@ Each organization can have one of the following status:
 
 - **Inactive:** Store admins have deactivated the organization, so your users won't be able to log in.
 
-![Status- EN](//images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/075f575659ca723e1fd8ac6f1400eb5c/Status-_EN.gif)
+![Status- EN](https://images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/075f575659ca723e1fd8ac6f1400eb5c/Status-_EN.gif)
 
 ## Adding a new organization
 
@@ -71,7 +71,7 @@ To add a new organization, follow the steps below:
     - **Recipient:** Name of the person who will receive the orders at the address provided.
 4. Click the `Add` button.
 
-![Adiconar organização- EN](//images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/9f298b8d96c542d3c45aadef5cc67b80/Adiconar_organiza__o-_EN.gif)
+![Adiconar organização- EN](https://images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/9f298b8d96c542d3c45aadef5cc67b80/Adiconar_organiza__o-_EN.gif)
 
 ## Email notifications
 
diff --git a/docs/tutorials/en/managing-credit-with-customer-credit.md b/docs/tutorials/en/managing-credit-with-customer-credit.md
index 2e0377b6d..84b89b40e 100644
--- a/docs/tutorials/en/managing-credit-with-customer-credit.md
+++ b/docs/tutorials/en/managing-credit-with-customer-credit.md
@@ -75,11 +75,11 @@ For a small number of registrations, the customer can create accounts one by one
 - Email
 - Credit limit
 
-![CustomerCredit1-EN.png?h=250](//images.ctfassets.net/alneenqid6w5/5nCFYt3M86PvAR6XYQkOjM/3dbfd3dcd28b1f6463be48f237092636/CustomerCredit1-EN.png_h_250)
+![CustomerCredit1-EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/5nCFYt3M86PvAR6XYQkOjM/3dbfd3dcd28b1f6463be48f237092636/CustomerCredit1-EN.png_h_250)
 
 If the database has a large number of accounts, it is best to import a spreadsheet in CSV format. You can download a template in the Accounts section and fill it with the required information. To do this, click on the Import button.
 
-![CustomerCredit2-EN.png?h=250](//images.ctfassets.net/alneenqid6w5/3dOP4y1k14B70DhB07n7zx/f2bd8cb4463b5132c176875373b5daf7/CustomerCredit2-EN.png_h_250)
+![CustomerCredit2-EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/3dOP4y1k14B70DhB07n7zx/f2bd8cb4463b5132c176875373b5daf7/CustomerCredit2-EN.png_h_250)
 
 ### Large databases
 
diff --git a/docs/tutorials/en/managing-page-and-template-content.md b/docs/tutorials/en/managing-page-and-template-content.md
index 6224e8027..27f1d70a1 100644
--- a/docs/tutorials/en/managing-page-and-template-content.md
+++ b/docs/tutorials/en/managing-page-and-template-content.md
@@ -32,7 +32,7 @@ In the VTEX Admin:
 
 1. Select the block to which you desire to create a new content. You can select it using the list on your right corner or through the interface:
 
-![seta-interface-en](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
+![seta-interface-en](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
 
 2. Click on `Versions` on your top-right corner.
 
@@ -59,7 +59,7 @@ The Site Editor applies content configurations according to the parameter hierar
 
 1. Select the desired block whose content will be overwritten. You can select it using the list on your right corner or through the interface:
 
-![seta-interface-en](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
+![seta-interface-en](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
 
 2. The available content is from the current active one. Edit the fields with the new values or click on `Versions` to edit other contents' configurations. 
 3. Save your changes.
@@ -72,7 +72,7 @@ Contents derived from the source code, i.e., the Store Theme app, can not have t
 
 1. Select the desired block whose content will be deleted or reset. You can select it using the list on your right corner or through the interface:
 
-![seta-interface-en](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
+![seta-interface-en](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/7969df97b1d05d70fe0a555052cf4011/img-two-en.png)
 
 2. Click on `Versions` on your top-right corner. 
 3. Click on the desired content's kebab menu (three points). 
diff --git a/docs/tutorials/en/managing-pages.md b/docs/tutorials/en/managing-pages.md
index dc72577ce..6a3cabac4 100644
--- a/docs/tutorials/en/managing-pages.md
+++ b/docs/tutorials/en/managing-pages.md
@@ -19,7 +19,7 @@ In **Headless CMS**, you can manage all the URL routes and page templates for yo
 
 ## Overview
 
-![New pages](//images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/7171a74a194bd96221f481de02d5599f/new_pages_-_en.png)
+![New pages](https://images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/7171a74a194bd96221f481de02d5599f/new_pages_-_en.png)
 
 | Option         | Description                                           |
 | -------------- | ----------------------------------------------------- |
@@ -42,7 +42,7 @@ To create and manage a page, follow these steps:
 3. Under `Untitled`, name the page.
 
 4. Click on `Sections` and select the desired section.
-![Gif - Pages](//images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/d35ca90a8b65f2f436173375fee0bf9d/Ingles_gif_da_pag.gif)
+![Gif - Pages](https://images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/d35ca90a8b65f2f436173375fee0bf9d/Ingles_gif_da_pag.gif)
 5. Add more sections if needed and fill them out.
 
 6. Click `Publish`. 
diff --git a/docs/tutorials/en/managing-placeholders.md b/docs/tutorials/en/managing-placeholders.md
index f6fd9b0f8..fc98b5148 100644
--- a/docs/tutorials/en/managing-placeholders.md
+++ b/docs/tutorials/en/managing-placeholders.md
@@ -35,14 +35,14 @@ It creates a configurable element in the part of the code where it is inserted.
 
 It is important to enter an `id` value. It will be the identifier of that placeholder in the system.
 
-![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configuring the placeholder
 
 Once the placeholder control has been inserted into the template, you can configure it in the settings of the layout that uses this template.
 
 1. Open the layout and then click on the **Settings** tab. The new placeholder should appear there, with the name equal to the id value defined in the control. For now, this placeholder is empty, meaning there are no objects inside it.
-![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. To insert an object, click on **add object**.
 3. Then choose the object type and click on the **Add** button.
 4. Finally, click on the **Save Settings** button.
@@ -51,7 +51,7 @@ You can now edit the object inserted in the placeholder.
 
 To do this, click on the pencil icon inside the object, and then click on **add content**.
 
-![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 You can now name this object, upload images to it and configure the conditions under which it will be rendered.
 
diff --git a/docs/tutorials/en/managing-projects.md b/docs/tutorials/en/managing-projects.md
index 83f26779a..8dd17bf7e 100644
--- a/docs/tutorials/en/managing-projects.md
+++ b/docs/tutorials/en/managing-projects.md
@@ -17,7 +17,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 
 Projects is a feature in the VTEX Headless CMS that simplifies the management of multiple frontend projects like mobile apps, websites, and email marketing from one control panel.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/9d484d193a357cf0a0ac5e8a3aa16e9a/projects-one-en.gif)
 
 Each project is customized with its own settings, content, and branding according to specific audiences or purposes. 
 
@@ -33,7 +33,7 @@ For the Headless CMS management, make sure the [resources](https://help.vtex.com
 ## Overview
 To access **Projects**, go to the VTEX Admin and access **Storefront > Headless CMS**.
 
-![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c7ccee21dc6cae85a41886c49d9a3d8f/projects-two-en.png)
+![Projects overview](https://images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c7ccee21dc6cae85a41886c49d9a3d8f/projects-two-en.png)
 
 | Option         | Description                                           |
 | -------------- | ----------------------------------------------------- |
@@ -113,7 +113,7 @@ To archive a project, follow the steps below:
 1. Go to **Storefront > Projects**.
 2. Choose the project you want to archive and click **Settings** (⚙️) to open a modal.
 3. Click `Archive project` on the `General` page. A pop-up message will appear to confirm that you want to archive the project.
-![Archive project](//images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/018e5e76e204d63fd86fdb9abe8ee82c/projects-three-en.png)
+![Archive project](https://images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/018e5e76e204d63fd86fdb9abe8ee82c/projects-three-en.png)
 4. Click `Archive`. A message informing that the project was successfully archived will appear.
 
 If you want to restore an archived project, follow the steps in [Restoring a project](#restoring-the-project).
diff --git a/docs/tutorials/en/managing-redirects-per-binding.md b/docs/tutorials/en/managing-redirects-per-binding.md
index e9ac20e1a..b0506bf1c 100644
--- a/docs/tutorials/en/managing-redirects-per-binding.md
+++ b/docs/tutorials/en/managing-redirects-per-binding.md
@@ -30,7 +30,7 @@ In VTEX Admin:
 1. Access **Storefront > Pages**.
 2. Click on the `Redirects` tab.
 
-![en-redirecttab](//images.ctfassets.net/alneenqid6w5/7G20PhFKWBFNKmvN2T8MFo/4b88bd44abc30aa3af4e0f9ca8557e3e/new-redirect.png)
+![en-redirecttab](https://images.ctfassets.net/alneenqid6w5/7G20PhFKWBFNKmvN2T8MFo/4b88bd44abc30aa3af4e0f9ca8557e3e/new-redirect.png)
 
 ## Manually creating redirects
 
@@ -40,7 +40,7 @@ In VTEX Admin:
 4. Check whether your redirect will be permanent or temporary — in case it is temporary, you can toggle the `This redirect has an end date` button to set an end date for it. 
 5. Save your changes.
 
-![en-novoredirect](//images.ctfassets.net/alneenqid6w5/4CdPssJV4wAfbvr0ZB2ugi/2d3efd147908ec9e1da471403cba2cf9/redirect-novo.png)
+![en-novoredirect](https://images.ctfassets.net/alneenqid6w5/4CdPssJV4wAfbvr0ZB2ugi/2d3efd147908ec9e1da471403cba2cf9/redirect-novo.png)
 
 ## Manually deleting redirects
 
@@ -48,7 +48,7 @@ In VTEX Admin:
 2. Click on the `Remove` button.
 3. Confirm your action. 
 
-![en-remove-redirect](//images.ctfassets.net/alneenqid6w5/4Ki1noxgrPgStT4wZGbrCk/7de9c0c5b3a4b9c734657c96ae20cccf/remove-redirect.png)
+![en-remove-redirect](https://images.ctfassets.net/alneenqid6w5/4Ki1noxgrPgStT4wZGbrCk/7de9c0c5b3a4b9c734657c96ae20cccf/remove-redirect.png)
 
 <div class="alert alert-warning">
 A bug may be found when trying to click on redirects with query strings. The VTEX product team is already aware of this unexpected behavior and working on the fix. If you cannot click on the desired redirect to delete it, opt to do it through the spreadsheet while the issue is not resolved. 
@@ -77,7 +77,7 @@ The spreadsheet's inputs will be mandatorily created or deleted from the store's
 4. Click on the `Import` button.
 5. Check the `Save` or the `Delete` button according to your scenario.
 
-  ![en-redirect-planilha](//images.ctfassets.net/alneenqid6w5/1LA0kpUcu5NhfUgWWhkjea/b83ae63b44fa2367877b00daf47467c7/redirect-planilha.png)
+  ![en-redirect-planilha](https://images.ctfassets.net/alneenqid6w5/1LA0kpUcu5NhfUgWWhkjea/b83ae63b44fa2367877b00daf47467c7/redirect-planilha.png)
 
   <div class="alert alert-warning">
 By clicking on the <code>Save</code> button, you will create all the redirects listed in your spreadsheet, whereas clicking on the <code>Delete</code> button will remove all of them from your store's redirect database.
diff --git a/docs/tutorials/en/managing-shipping-policies.md b/docs/tutorials/en/managing-shipping-policies.md
index 770714923..e5dbcbfbf 100644
--- a/docs/tutorials/en/managing-shipping-policies.md
+++ b/docs/tutorials/en/managing-shipping-policies.md
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) is a set of rules and settings that define the shipping options displayed to customers at checkout. The relationship between shipping policy, [warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb), and [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) makes up your [shipping strategy](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) on VTEX, as shown in the image below:
 
-![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
+![shipping_strategy_EN](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
 
 This article explains how to monitor and manage your shipping policies. In the VTEX Admin, under **Shipping > Shipping Strategy**, the **Shipping Policies** tab is where you can do the following:
 
@@ -35,7 +35,7 @@ You can also create shipping policies. Read the instructions in the [Creating a
 
 In the VTEX Admin, by going to **Shipping > Shipping Strategy** in the **Shipping Policies** tab, you will see a list as shown in the image below:
 
-![shipping_policy_EN](//images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/68d66c99a43db25f4e297fbc238f0375/shipping_policy_EN.png)
+![shipping_policy_EN](https://images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/68d66c99a43db25f4e297fbc238f0375/shipping_policy_EN.png)
 
 The information displayed on this page is described in the table below:
 
diff --git a/docs/tutorials/en/managing-singleton-content-types.md b/docs/tutorials/en/managing-singleton-content-types.md
index 2558f3c73..7e83eb6e1 100644
--- a/docs/tutorials/en/managing-singleton-content-types.md
+++ b/docs/tutorials/en/managing-singleton-content-types.md
@@ -18,7 +18,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 Singleton content types allow creating and managing a single page, ensuring that only one page of this content type exists in Headless CMS.
 
 This content type avoids potential conflicts and inconsistencies when multiple pages of the same content type are created. For example, you can use Singleton for your store's Home page to ensure that there is only one Home page and that all updates and requests to this page always return the same result.
-![singleton-en](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
+![singleton-en](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
 
 <div class="alert alert-warning">
   To create the Singleton content type, check with your developer team if the <i>isSingleton</i> property is implemented or ask them to follow the instructions in <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> to add it to the desired content type.
diff --git a/docs/tutorials/en/managing-url-redirects.md b/docs/tutorials/en/managing-url-redirects.md
index d6a96c2c3..9f8b6ccd0 100644
--- a/docs/tutorials/en/managing-url-redirects.md
+++ b/docs/tutorials/en/managing-url-redirects.md
@@ -31,7 +31,7 @@ Multiple redirects are possible in a single URL. To create a redirect, follow th
 4. In the checkbox, indicate whether this redirect is temporary or permanent. If it is temporary, you need to set an end date.
 5. Click `Save`.
 
-![gerenciando redirecionamentos en 1](//images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/342b99d95882506fce9b9e3be1205bac/image6.png)
+![gerenciando redirecionamentos en 1](https://images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/342b99d95882506fce9b9e3be1205bac/image6.png)
 ## Importing redirects
 Follow the steps below to import a redirect.
 
diff --git a/docs/tutorials/en/managing-users.md b/docs/tutorials/en/managing-users.md
index ed8286814..22f95b393 100644
--- a/docs/tutorials/en/managing-users.md
+++ b/docs/tutorials/en/managing-users.md
@@ -19,7 +19,7 @@ The user management with access to the administrative environment of your VTEX s
 
 This page displays the list of users with their __Name__, __Email__ and __MFA__ configuration. There are also options to search for users, export users and create new ones. Other options available on this interface are to edit or delete each user.
 
-![Lista Usuários User Management EN](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
+![Lista Usuários User Management EN](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
 
 <div class="alert alert-warning">
 Any user that wants to manage users or application keys must have a profile with the <b>Save User</b> <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete">resource</a>. You can use the default profile <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, for example.
@@ -30,10 +30,10 @@ Any user that wants to manage users or application keys must have a profile with
 1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
 2. Click on the `+ New` button.  
 3. Fill in the **Email**.  
-  ![Add new User Management EN](//images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/1c78fe3f13064af0b12685dba1ab85a0/Cadastro_Novo_usu__rio_User_Management_EN.png)
+  ![Add new User Management EN](https://images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/1c78fe3f13064af0b12685dba1ab85a0/Cadastro_Novo_usu__rio_User_Management_EN.png)
 4. Click on `+ Add roles`.
 5. Add the desired [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).  
-  ![Select User Management roles EN](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/b06bd642bf1763e915d49e3016ab845a/select-roles.PNG)
+  ![Select User Management roles EN](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/b06bd642bf1763e915d49e3016ab845a/select-roles.PNG)
 6. Click on `Add roles` to confirm the selection.
 7. Click on `Save`.  
 
@@ -45,10 +45,10 @@ The password must have at least eight characters and a number, a capital letter
 
 1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
 2. To edit an existing user, click on their name in the list of users. Another possibility is to click on the menu button <i class="fas fa-ellipsis-v"></i> next to the desired user and then on **Edit**.
-  ![Botão Editar Usuário User Management EN](//images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/03aa67401cc9eb46480cd9a6bbb9a65e/Bot__o_Editar_Usu__rio_User_Management_EN.png)
+  ![Botão Editar Usuário User Management EN](https://images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/03aa67401cc9eb46480cd9a6bbb9a65e/Bot__o_Editar_Usu__rio_User_Management_EN.png)
    <div class="alert alert-warning" role="alert">It is not possible to change the email of an existing user. In this case, it is necessary to delete the user and create them again with the new email.</div>
 3. In the editing page you can add and remove the [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) of the user, as shown in the image below. 
-  ![Select User Management roles EN](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/b06bd642bf1763e915d49e3016ab845a/select-roles.PNG)
+  ![Select User Management roles EN](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/b06bd642bf1763e915d49e3016ab845a/select-roles.PNG)
 4. Click on `Add roles` to confirm the selection.
 5. Click on `Save`.
 
@@ -61,10 +61,10 @@ The password must have at least eight characters and a number, a capital letter
 1. Click on your **profile avatar** on the VTEX Admin top bar, marked by the initial of your email, and click on **Account settings** > __Users__ .
 2. Click on the menu button <i class="fas fa-ellipsis-v"></i> next to the user you want to remove.
 3. Click on the **Delete** option.
-  ![Delete a User Management button EN](//images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/da5bdd0600085cb4b8e4203308c89f36/Bot__o_Excluir_Usu__rio_User_Management_EN.png)
+  ![Delete a User Management button EN](https://images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/da5bdd0600085cb4b8e4203308c89f36/Bot__o_Excluir_Usu__rio_User_Management_EN.png)
   A message will appear to confirm the removal of the user.
 4. To confirm, click on the button `YES, REVOKE ALL ACCESS`.  
-  ![Confirmar Remover Acesso User Management EN](//images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/9773084eac472c468e94d67f575a92e0/Confirmar_Remover_Acesso_User_Management_EN.png)
+  ![Confirmar Remover Acesso User Management EN](https://images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/9773084eac472c468e94d67f575a92e0/Confirmar_Remover_Acesso_User_Management_EN.png)
 
 ## Exporting user data
 
diff --git a/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md b/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md
index d07804bd6..f95b66f20 100644
--- a/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md
+++ b/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md
@@ -17,7 +17,7 @@ subcategory: 1vwB9FtTSQmcSewQw02QoW
 
 The Web Service interface enables access of storeowners in charge to practically all data shown in the admin interface, as well as to additional and exclusive data. Before using it, follow our [ERP Integration Guide](https://help.vtex.com/tutorial/integration-guide-for-erps--3VuOwNLmb624ImooEIIkmO).
 
-[Download the manual of classes and methods.](//assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
+[Download the manual of classes and methods.](https://assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
 
 <div class="alert alert-danger"><p>Important: only the SOAP methods relevent to the <strong>catalog</strong> are valid.</p>
 <p><strong>All other methods will be deprecated as of 02/28/2017.</strong></p>
diff --git a/docs/tutorials/en/marketplace-invited-sellers.md b/docs/tutorials/en/marketplace-invited-sellers.md
index 633c8a9f0..4d98066f0 100644
--- a/docs/tutorials/en/marketplace-invited-sellers.md
+++ b/docs/tutorials/en/marketplace-invited-sellers.md
@@ -27,7 +27,7 @@ In addition to sending invitations, the page also displays a list of sellers to
 
 For new sellers to integrate with your marketplace, you must perform the following actions on the VTEX platform: [Invite](#inviting-sellers) and [Connect](#connecting-sellers).
 
-![EN seller invite](//images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/48e7ae5bdb892b7e0b0811c2d868a8b4/EN_Seller_invite.jpg)
+![EN seller invite](https://images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/48e7ae5bdb892b7e0b0811c2d868a8b4/EN_Seller_invite.jpg)
 
 ## Inviting sellers
 
diff --git a/docs/tutorials/en/marketplace-strategies-at-vtex.md b/docs/tutorials/en/marketplace-strategies-at-vtex.md
index 7da47d820..86481db6a 100644
--- a/docs/tutorials/en/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/en/marketplace-strategies-at-vtex.md
@@ -17,7 +17,7 @@ subcategory: 4uqMnZjwBO04uWgCom8QiA
 
 A marketplace is a virtual platform through which different sellers offer their products. In addition to owning products, sellers are often responsible for the [fulfillment process](https://help.vtex.com/en/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP).  
 
-![Marketplace strategies](//images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/8f611e6a89c168b7322aa14e1f6b7024/Ecommerce_web_page-pana.png)  
+![Marketplace strategies](https://images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/8f611e6a89c168b7322aa14e1f6b7024/Ecommerce_web_page-pana.png)  
 
 [VTEX promotes digital collaboration](https://vtex.com/en-us/marketplace/) in different scenarios. For example, besides selling your products on other marketplaces, you can also act as a marketplace and sell products from other sellers on your website.  
 
@@ -72,7 +72,7 @@ The process to configure your store as [a VTEX marketplace](https://help.vtex.co
 
 See below for the main VTEX marketplaces:  
 
-![mkt br](//images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
+![mkt br](https://images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
 
 The __Marketplaces and Integrations__ module also promotes and enables contact between VTEX marketplaces and certified VTEX sellers interested in collaborations.  
 
diff --git a/docs/tutorials/en/marketplaces-and-integrations.md b/docs/tutorials/en/marketplaces-and-integrations.md
index 73a522b00..49c8919e0 100644
--- a/docs/tutorials/en/marketplaces-and-integrations.md
+++ b/docs/tutorials/en/marketplaces-and-integrations.md
@@ -33,7 +33,7 @@ If you want to act as a VTEX marketplace, read the <a href="https://help.vtex.co
 
 To access the page, in the VTEX Admin, click __Marketplace > Connections > Marketplaces and Integrations__. On the page, you can see the recommended marketplaces to connect to and the complete list of all available or already connected marketplaces.  
 
-![Marketplaces and Integrations](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
+![Marketplaces and Integrations](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/e4382e0c375781f8f1029ffe29e6738a/Captura_de_tela_2023-04-17_110739.png)
 
 The table listing the marketplaces has the following columns:  
 
diff --git a/docs/tutorials/en/master-data-v2.md b/docs/tutorials/en/master-data-v2.md
index 2be2abed3..27713b9cb 100644
--- a/docs/tutorials/en/master-data-v2.md
+++ b/docs/tutorials/en/master-data-v2.md
@@ -25,10 +25,10 @@ This document will guide you to save, validate and get documents at VTEX Master
 It's not necessary to create a JSON Schema to save documents. You can save to any data entity if the content is a valid JSON.
 
 The JSON Schema indicates how to validate and index. A data entity may or may not have multiple JSON Schemas.
-![master-data-data-entity-schemas](//images.contentful.com/alneenqid6w5/5Ms8eS24xOsGWcEGY0WKwu/724d0585090ee2d3bf6fc47dad7a3859/master-data-data-entity-schemas.jpg)
+![master-data-data-entity-schemas](https://images.contentful.com/alneenqid6w5/5Ms8eS24xOsGWcEGY0WKwu/724d0585090ee2d3bf6fc47dad7a3859/master-data-data-entity-schemas.jpg)
 
 A document could be compliant with none or multiple schemas.
-![master-data-documents-compliant](//images.contentful.com/alneenqid6w5/7m7NMV5Hc4Wq8aKeGeWiAY/29301b6873e1549c244d56e15cf4caf7/master-data-documents-compliant.jpg)
+![master-data-documents-compliant](https://images.contentful.com/alneenqid6w5/7m7NMV5Hc4Wq8aKeGeWiAY/29301b6873e1549c244d56e15cf4caf7/master-data-documents-compliant.jpg)
 
 This means that JSON Schema is a format of documents in data entities.
 
diff --git a/docs/tutorials/en/master-data.md b/docs/tutorials/en/master-data.md
index 6c98951a8..2a65a2f62 100644
--- a/docs/tutorials/en/master-data.md
+++ b/docs/tutorials/en/master-data.md
@@ -297,7 +297,7 @@ Learn more about <a href=https://json-schema.org/>JSON schemas</a>.
 
 You can save a document to any data entity if the content is a valid JSON. A data entity may or may not have multiple JSON schemas associated with it.
 
-![Master Data schemas](//images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/72f691a72fe0166b1e16a38c6bf89d11/schemas_en.jpg)
+![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/72f691a72fe0166b1e16a38c6bf89d11/schemas_en.jpg)
 
 <div class = "alert alert-info">
 A document can be compatible with multiple JSON Schemas, but also with none.
diff --git a/docs/tutorials/en/media-overview.md b/docs/tutorials/en/media-overview.md
index 7b8147eed..b1c312aad 100644
--- a/docs/tutorials/en/media-overview.md
+++ b/docs/tutorials/en/media-overview.md
@@ -21,7 +21,7 @@ Media is a feature responsible for managing your store's media files, such as im
   For upload, files must have a lowercase extension (e.g., <code>store.png</code>) and be up to <b>5 MB</b>.
 </div>
 
-![Media Overview](//images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4151c07cdf6675310b41607256633894/en-media-overview.png)
+![Media Overview](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4151c07cdf6675310b41607256633894/en-media-overview.png)
 
 In addition, Media is integrated with **Site Editor** and **Headless CMS**. This integration allows you to access and manage Media directly through VTEX CMS solutions.
 
@@ -45,7 +45,7 @@ Note that the section must use the <a href="https://developers.vtex.com/docs/gui
 
 In the following image, you can see an overview of the Media interface and the actions available for managing your media files:
 
-![Media Features](//images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/7466fed34ed8183fde0b9d61e68b9e1f/en-media-features.png)
+![Media Features](https://images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/7466fed34ed8183fde0b9d61e68b9e1f/en-media-features.png)
 
 | Field | Description |
 | ---------- | ------------- |
diff --git a/docs/tutorials/en/merchandising-rules-list.md b/docs/tutorials/en/merchandising-rules-list.md
index 392f619a2..ed4dcde84 100644
--- a/docs/tutorials/en/merchandising-rules-list.md
+++ b/docs/tutorials/en/merchandising-rules-list.md
@@ -22,7 +22,7 @@ On VTEX Admin, the page **Storefront** > **Intelligent Search** > **Merchandisin
 * [Edit](#editing-merchandising-rules)
 * [Delete](#deleting-merchandising-rules)
 
-![merch-rules-en](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/6b6dc34a4127cd654dab40fa17a70664/merch-rules-en.PNG)
+![merch-rules-en](https://images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/6b6dc34a4127cd654dab40fa17a70664/merch-rules-en.PNG)
 
 The page displays the following information: 
 
diff --git a/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md b/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md
index 3e6fa6c03..6b03dfdb7 100644
--- a/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md
+++ b/docs/tutorials/en/metrics-are-not-displayed-in-the-order-dashboard.md
@@ -23,7 +23,7 @@ When accessing the Admin dashboard, it may fail to load metrics in the **Overvie
 - **Inadequate comparison period:** The period selected in the top right corner of the dashboard may not contain sufficient order data for comparison.
 - **Insufficient access permissions:** You might not have the necessary role to view certain information on the dashboard.
 
-![Visão geral - EN](//images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/92d249251094dd01515b571876066e7c/Vis_o_geral_-_EN.png)
+![Visão geral - EN](https://images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/92d249251094dd01515b571876066e7c/Vis_o_geral_-_EN.png)
 
 ## Solution
 To solve inconsistencies in the initial dashboard of the Admin, you can try the following:
@@ -34,7 +34,7 @@ Adjusting the comparison period can solve the issue by displaying relevant metri
 1. In the VTEX Admin, go to **Dashboard > Overview**.
 2. In the top right corner, select the comparison period.
 
-![Dashboard - EN](//images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/a8aee6d86d8db48453f20cc8d9be48b7/Dashboard_-_EN.png)
+![Dashboard - EN](https://images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/a8aee6d86d8db48453f20cc8d9be48b7/Dashboard_-_EN.png)
 
 ### Wait for information to be updated
 Please allow 10 to 80 minutes for the information to be updated on the dashboard. This period is necessary for the data to be processed and displayed correctly. For more information about the waiting time, see [Comparing periods](https://help.vtex.com/en/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ?&utm_source=autocomplete).
diff --git a/docs/tutorials/en/multilevel-omnichannel-inventory.md b/docs/tutorials/en/multilevel-omnichannel-inventory.md
index ca4a36a48..25a89a2f2 100644
--- a/docs/tutorials/en/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/en/multilevel-omnichannel-inventory.md
@@ -38,7 +38,7 @@ The main seller may also sell its products in a marketplace.
 
 In this case, there is a three-tier architecture between the marketplace, the main seller, and its white-label sellers, as shown in the image below.
 
-![Arquitetura Multilevel omichannel inventory](//images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/fd36e953d3a8f70d068bcd69991e998c/Screen_Shot_2022-09-30_at_18.57.26.png)
+![Arquitetura Multilevel omichannel inventory](https://images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/fd36e953d3a8f70d068bcd69991e998c/Screen_Shot_2022-09-30_at_18.57.26.png)
 
 By default, products from physical stores, or white-label sellers (level 3 in the image), are not available for selling in the marketplace (level 1 in the image). But you can make them available using the _Multilevel Omnichannel Inventory_ capability. 
 
diff --git a/docs/tutorials/en/names-of-vtex-branches-worldwide.md b/docs/tutorials/en/names-of-vtex-branches-worldwide.md
index 1678094f4..48bd58f59 100644
--- a/docs/tutorials/en/names-of-vtex-branches-worldwide.md
+++ b/docs/tutorials/en/names-of-vtex-branches-worldwide.md
@@ -29,4 +29,4 @@ VTEX is proud to have offices and clients around the world. Each country office
 
 To know which country office you are invoiced from, consult your contract or [download your invoice](https://help.vtex.com/en/tutorial/como-fazer-download-faturas-da-VTEX--tutorials_653). When you open an invoice, you will find the company name and address from which your store is being invoiced in the left corner of your invoice, below VTEX’s logo.  
 
-![reconhecimento fatura](//images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
+![reconhecimento fatura](https://images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
diff --git a/docs/tutorials/en/new-integration-with-erede-erederest.md b/docs/tutorials/en/new-integration-with-erede-erederest.md
index 2e4bc45be..127960f2a 100644
--- a/docs/tutorials/en/new-integration-with-erede-erederest.md
+++ b/docs/tutorials/en/new-integration-with-erede-erederest.md
@@ -25,11 +25,11 @@ To set up the new version, you must first request Rede to activate the __ERede__
 
 Once notified, go to the menu and then navigate through __e.Rede > Settings > Token generation__.
 
-![GerarToken](//images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
+![GerarToken](https://images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
 
 Then, click the button to create the token.
 
-![GerarToken Click](//images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
+![GerarToken Click](https://images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
 
 With this, you will have access to the token that must be informed in the ERedeRest gateway affiliation configuration form. In addition to the token, you will also need to inform the PV, which is  the identification number of the establishment on Rede's website.
 
@@ -39,10 +39,10 @@ To do this configuration in VTEX, follow the steps below:
 2. Click on __Settings__ and access __Gateways Affiliations__; 
 3. Click on the green button __+__ _I want to receive payment by the connector..._ and search for the connector __ERedeRest .__
 
-![erederestEN](//images.ctfassets.net/alneenqid6w5/6LI5jh2u5OcYaGQ4cikuE2/29031380ce30470072c9b06db0d14118/erederestEN.jpg) 
+![erederestEN](https://images.ctfassets.net/alneenqid6w5/6LI5jh2u5OcYaGQ4cikuE2/29031380ce30470072c9b06db0d14118/erederestEN.jpg) 
 
-![erederestEN-config](//images.ctfassets.net/alneenqid6w5/2I770mrYbeueky266cqooO/cf6ffb075ece540e7b3224c99e9c415c/erederestEN-config.jpg)
+![erederestEN-config](https://images.ctfassets.net/alneenqid6w5/2I770mrYbeueky266cqooO/cf6ffb075ece540e7b3224c99e9c415c/erederestEN-config.jpg)
 
-![PegarPV](//images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
+![PegarPV](https://images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
 
 This new connector offers a number of configuration options, including ApplePay support. 
diff --git a/docs/tutorials/en/new-my-orders-area.md b/docs/tutorials/en/new-my-orders-area.md
index 6cad592c7..6fc6d173a 100644
--- a/docs/tutorials/en/new-my-orders-area.md
+++ b/docs/tutorials/en/new-my-orders-area.md
@@ -24,28 +24,28 @@ Because the new page structure is completely different, it will be necessary to
 
 VTEX is always looking to use a modern stack to create products that deliver more value to the ecosystem. For this reason, we started using the React JS library in our most recent systems and features: the new **My Orders** feature is one example. The newest version comes with new features and design, and was created from scratch using React.
 
-![Order listing in the new My Orders](//images.contentful.com/alneenqid6w5/5iEOW4etrGO208I4gMiqmq/3db31b5565b297daff34247be23dc7f0/my-orders-blog-1.png)
+![Order listing in the new My Orders](https://images.contentful.com/alneenqid6w5/5iEOW4etrGO208I4gMiqmq/3db31b5565b297daff34247be23dc7f0/my-orders-blog-1.png)
 
 ### New navigation experience
 
 React wasn't chosen only so this release was aligned with the remaining of the VTEX platform — because it's a single-page application loaded within the store, the new orders area has a fluid navigation, improving the user experience.
 
-![My Orders navigation with instant loading between pages](//images.contentful.com/alneenqid6w5/6LN7wTA0k8maaaGGwicqkG/cb11a2c95c14d9c707e5c2a50de3ffd5/MOg.gif)
+![My Orders navigation with instant loading between pages](https://images.contentful.com/alneenqid6w5/6LN7wTA0k8maaaGGwicqkG/cb11a2c95c14d9c707e5c2a50de3ffd5/MOg.gif)
 
 ### Features
 
 This update in the My Orders will be the starting point for new features, but this one already brings improvements, like a mobile-ready layout and order timeline — a feature lots of agencies implemented on their own.
 
-![Mobile & desktop My Orders](//images.contentful.com/alneenqid6w5/5PiNAlG8LekCssuiq2kuQ2/28b4d60785682b7b4a53a1583b11c9bf/my-orders-blog-2.png) 
+![Mobile & desktop My Orders](https://images.contentful.com/alneenqid6w5/5PiNAlG8LekCssuiq2kuQ2/28b4d60785682b7b4a53a1583b11c9bf/my-orders-blog-2.png) 
 
-![Order details](//images.contentful.com/alneenqid6w5/1p3u7cATQAIgyEMAQCsyKa/151bd1aa2063456420a6716b4f6c57ad/my-orders-blog-3.png) 
+![Order details](https://images.contentful.com/alneenqid6w5/1p3u7cATQAIgyEMAQCsyKa/151bd1aa2063456420a6716b4f6c57ad/my-orders-blog-3.png) 
 
 
 Another new feature are the pre-defined cancelling reasions that the client can choose when cancelling an order. These reasons can be easily customized and translated in Portal v2:
 
-![Cancelamento do pedido](//images.contentful.com/alneenqid6w5/4KBPK3bXf2e8aO2MYkikAY/ce0f45e9fc81f778cfbf6c5904b9f39e/my-orders-blog-4.png) 
+![Cancelamento do pedido](https://images.contentful.com/alneenqid6w5/4KBPK3bXf2e8aO2MYkikAY/ce0f45e9fc81f778cfbf6c5904b9f39e/my-orders-blog-4.png) 
 
-![Customizando razões de cancelamento](//images.contentful.com/alneenqid6w5/3Na3wIvSRG6ygy4YgkgICC/24e1ad1513b367326c46a481c0d79bcc/my-orders-blog-5.png)
+![Customizando razões de cancelamento](https://images.contentful.com/alneenqid6w5/3Na3wIvSRG6ygy4YgkgICC/24e1ad1513b367326c46a481c0d79bcc/my-orders-blog-5.png)
 
 For the first time, we're also supporting native translation of the My Orders to french, right from the interface!
 
@@ -53,7 +53,7 @@ For the first time, we're also supporting native translation of the My Orders to
 
 To avoid compatibility issues and reduce the chance of breaking customizations, the new My Orders comes with an opt-in, that allows stores to migrate on the speed they wish. This opt-in checkbox is in the Portal v2, in the same section as the cancelling reasons:
 
-![Opt-in to activate the new version](//images.contentful.com/alneenqid6w5/Nf4NJcrnMWQEay0YmW0IU/af155d35e2db7ab7a8fa8f8e0ec8462e/MO6.png)
+![Opt-in to activate the new version](https://images.contentful.com/alneenqid6w5/Nf4NJcrnMWQEay0YmW0IU/af155d35e2db7ab7a8fa8f8e0ec8462e/MO6.png)
 
 Before activating the new version, you can see it accessing your store through the beta environment: `accountname.vtexcommercestable.com.br/account/orders`.
 
diff --git a/docs/tutorials/en/offer-details.md b/docs/tutorials/en/offer-details.md
index 6596a3a67..181e56f8b 100644
--- a/docs/tutorials/en/offer-details.md
+++ b/docs/tutorials/en/offer-details.md
@@ -41,7 +41,7 @@ In <b>Offer Management</b> , you can track offers using <a href="https://help.vt
 
 ## Header
 
-![Offer details EN cabecalho](//images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/95810a56417e12b9296cd728ac3cb326/Offer_details_EN_cabecalho.jpg)
+![Offer details EN cabecalho](https://images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/95810a56417e12b9296cd728ac3cb326/Offer_details_EN_cabecalho.jpg)
 
 The header displays the main information about the offer for quick viewing, such as its image, channel, name, status, ID on VTEX, and ID on the channel. You can also make the following changes by clicking on the `Edit` button:
 
@@ -57,13 +57,13 @@ The Status block shows details about the offer status, which can be Synched, Err
 
 ### Status: Synched
 
-![Offer details PT status sucesso](//images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/c2968ed1f70e475991cf6ab432099d7d/Offer_details_EN_status_sucesso.jpg)
+![Offer details PT status sucesso](https://images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/c2968ed1f70e475991cf6ab432099d7d/Offer_details_EN_status_sucesso.jpg)
 
 The *Synched* status indicates that the offer has been successfully received on a channel and is being updated by both the marketplace and the seller in real time.   
 
 ### Status: Error
 
-![Offer details PT status erro](//images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/482919e396734cfdc6e1ccc0ba1a555b/Offer_details_EN_status_erro.jpg)
+![Offer details PT status erro](https://images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/482919e396734cfdc6e1ccc0ba1a555b/Offer_details_EN_status_erro.jpg)
 
 The *Error* status indicates that the system identified an issue that prevents an offer from being sent or updated on a channel, and the seller needs to take action to fix it. Errors can be generated on the VTEX seller side, such as product descriptions that exceed the character limit, and on the marketplace side, such as failed API calls.   
 
@@ -81,19 +81,19 @@ If there are still errors to be fixed, or if all errors have been fixed but the
 
 ### Status: Unavailable
 
-![Offer details PT status indisponivel](//images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/5631d49b42f0b71ae84b5f6892657c7b/Offer_details_EN_status_indisponivel.jpg)
+![Offer details PT status indisponivel](https://images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/5631d49b42f0b71ae84b5f6892657c7b/Offer_details_EN_status_indisponivel.jpg)
 
 The *Unavailable* status indicates that the offer has been discarded for being inactive or not included in the [sales channel](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) (or trade policy) determined for the channel.
 
 ### Status: Sending
 
-![Offer details PT status enviando](//images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1f50f1f4b63b5a94ab6747fd70ab8df5/Offer_details_EN_status_enviando.jpg)
+![Offer details PT status enviando](https://images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1f50f1f4b63b5a94ab6747fd70ab8df5/Offer_details_EN_status_enviando.jpg)
 
 The *Sending* status indicates that the offer is being submitted to the channel. This status refers to offers that: are being submitted to the marketplace for the first time; are migrating to a new channel; or have been resent after being discarded in another channel.   
 
 ## List of interactions
 
-![Offer details PT lista interacoes](//images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/6a9970fc7c50d001f4bc1df358247641/Offer_details_EN_lista_interacoes.jpg)
+![Offer details PT lista interacoes](https://images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/6a9970fc7c50d001f4bc1df358247641/Offer_details_EN_lista_interacoes.jpg)
 
 The *Interactions* tab lists all `inventory`, `price` or `catalog` updates that that SKU has undergone. You can filter them by origin or status and adjust the number of items displayed per page. Each row corresponds to an interaction regarding that offer and includes the following data:
 
diff --git a/docs/tutorials/en/offer-management.md b/docs/tutorials/en/offer-management.md
index 1d6cde9f3..916d69e88 100644
--- a/docs/tutorials/en/offer-management.md
+++ b/docs/tutorials/en/offer-management.md
@@ -23,17 +23,17 @@ For connectors interested in starting the integration, we ask you to wait for th
 
 The **Offer Management** module allows sellers to track the sending and syncing of their offers on all sales channels integrated with the store. On the VTEX platform, an offer is a SKU from a seller that has been sent to a sales channel and whose price and inventory information have been configured.
 
-![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 In **Offer Management**, you can track offers sent to the following channels: [Mercado Libre](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic and Premium), [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) and VTEX marketplaces. For connectors to integrate via API, see [Offer Management Integration Guide](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 To access the module, in the VTEX Admin go to **Marketplace > Connections > Offer Management**. The following interface is displayed:
 
-![sent-offers-en_2](//images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/ab112c902aff07dd90b1271dbac0cfae/sent-offers-en_2.png)
+![sent-offers-en_2](https://images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/ab112c902aff07dd90b1271dbac0cfae/sent-offers-en_2.png)
 
 The **Offer Management** interface displays a list of your offers, and you can click on any of the offers to access the [offer details](https://help.vtex.com/en/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) and check the [interaction details](https://help.vtex.com/en/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf). Interactions are the offer logs when sending and syncing them with the sales channel and are available for consultation for ten days.
 
-![diagrama ju meyer sent offers en](//images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/4537ebb6b68838ee6ee4d1bc03dd87c8/diagrama_ju_meyer_sent_offers_en.png)
+![diagrama ju meyer sent offers en](https://images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/4537ebb6b68838ee6ee4d1bc03dd87c8/diagrama_ju_meyer_sent_offers_en.png)
 
 On the **Offer Management** page, you can perform the following actions:
 
diff --git a/docs/tutorials/en/offer-quality-filters.md b/docs/tutorials/en/offer-quality-filters.md
index 8a2f4b38f..f12ef8eb2 100644
--- a/docs/tutorials/en/offer-quality-filters.md
+++ b/docs/tutorials/en/offer-quality-filters.md
@@ -21,7 +21,7 @@ Quality criteria are important for the marketplace's operation so that the offer
 
 **Offer quality filters** is the page where marketplaces add and manage the requirement groups applied to the received SKU cataloging process. To access it, in your VTEX Admin, go to **Marketplace > Offer Quality** or type __"Offer Quality"__ in the search bar.
 
-![EN offer quality](//images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/73ac6313be9a602772446d24f0dbd8ba/EN_offer_quality.png)
+![EN offer quality](https://images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/73ac6313be9a602772446d24f0dbd8ba/EN_offer_quality.png)
 
 In this article, learn how to:
 
@@ -46,7 +46,7 @@ The feature allows the marketplace operator to perform many actions, each offeri
 | Bring more transparency to the cataloging criteria for submitted offers and how sellers and offers do or do not comply.                                                                     | It allows you to identify which sellers and offer types do not meet the requirements, speeding up corrections.         |
 
 ## Viewing Default requirements
-![EN Default requirements](//images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/83dd62ff723ec843269ea0919c31633d/EN_Default_requirements.png)
+![EN Default requirements](https://images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/83dd62ff723ec843269ea0919c31633d/EN_Default_requirements.png)
 
 The page, by default, has some pre-configured requirements that will apply to all categories, sellers, and brands, called _Default requirements_. Some of these criteria are natively configured in [VTEX Matcher](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), the tool applied to VTEX marketplaces to support the cataloging process of submitted offers.
 
diff --git a/docs/tutorials/en/offer-status.md b/docs/tutorials/en/offer-status.md
index 948f5f20c..ec41fc8d4 100644
--- a/docs/tutorials/en/offer-status.md
+++ b/docs/tutorials/en/offer-status.md
@@ -19,11 +19,11 @@ The **Offer Status** module allows sellers to track the sending and syncing of t
 
 **Offer Status** allows you to track offers sent only to VTEX marketplaces. To access the module, in the VTEX Admin, go to **Marketplace > Connections > Offer Status**, or type **Offer Status** in the search bar.
 
-![Offer Status Screen](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/2de2b349e1c114b7b50db65533eee1df/-EN-_Offer_Status_-_GIF.gif)
+![Offer Status Screen](https://downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/2de2b349e1c114b7b50db65533eee1df/-EN-_Offer_Status_-_GIF.gif)
 
 The **Offer Status** page comprises three tabs: [**Published**](#published-tab), [**Issues**](#issue-tab), and [**Awaiting Completion**](#awaiting-completion-tab), all listing your offers according to their status. You can access and view details of each offer, such as their status, inventory, price, update date, and reasons for being rejected by the marketplace.
 
-![Offer Status schema](//images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/4d8fe1a14fdcfc61f9ec87be31fa2c0a/offer-status-schema-en.png)
+![Offer Status schema](https://images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/4d8fe1a14fdcfc61f9ec87be31fa2c0a/offer-status-schema-en.png)
 
 ## Published tab
 
@@ -50,7 +50,7 @@ To filter the offers by **Marketplace**, click the down arrow, select the desire
 
 To filter the offers by **Inventory**, click the down arrow, enter the minimum and/or maximum inventory, and click **Apply**.
 
-![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/48708c0e98b5c01060748b5def3c6184/inventory-filter.png)
+![Filtro estoque offer status](https://images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/48708c0e98b5c01060748b5def3c6184/inventory-filter.png)
 
 To filter the offers by **Update**, click the down arrow, select one of the options, and then click **Apply.**
 
@@ -59,7 +59,7 @@ See below the options available for this filter:
 - **Updated**: Offers that had their price and/or inventory updated by the seller and have been processed successfully.
 - **Error updating:** Offers that had inconsistencies and failed to update.
 
-![Filtro atualizado offer status](//images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/92bc3b3358618470087e57c1566215ae/update-filter.png)
+![Filtro atualizado offer status](https://images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/92bc3b3358618470087e57c1566215ae/update-filter.png)
 
 You can use a single filter or combine them in a single search. The filters are not selected by default, so the home page displays the total number of existing offers.
 
@@ -102,7 +102,7 @@ To update any details of an already published offer, you must do the following:
 
 You will be redirected to the corresponding page to make the necessary changes.
 
-![Ações offer status](//images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/990566155ec8712979614688eb549ad0/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.006.jpeg)
+![Ações offer status](https://images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/990566155ec8712979614688eb549ad0/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.006.jpeg)
 
 ### Export published offer list
 
@@ -141,7 +141,7 @@ To filter the offers by **Marketplace**, click the down arrow, select the desire
 To filter the offers by **Sent**, click the down arrow, select one of the options, and then click **Apply.**  
 
 To filter the offers by **Inventory**, click the down arrow, enter the minimum and/or maximum inventory, and click **Apply**.  
-![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/48708c0e98b5c01060748b5def3c6184/inventory-filter.png)
+![Filtro estoque offer status](https://images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/48708c0e98b5c01060748b5def3c6184/inventory-filter.png)
 
 You can use a single filter or combine them in a single search. The filters are not selected by default, so the home page displays the total number of existing offers.  
 
diff --git a/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md b/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
index 7a0856475..4d8fe77b0 100644
--- a/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
+++ b/docs/tutorials/en/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
@@ -23,7 +23,7 @@ By default, the product that will be shipped from the seller must also be in [st
 
 The following image is an example in which Seller A sends a product to Marketplace A. Only after Marketplace A has added to its inventory the product sent by Seller A can the item be sent to Marketplace B.
 
-![erro-envio-skus-sellers-marketplaces-docnovo](//images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
+![erro-envio-skus-sellers-marketplaces-docnovo](https://images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
 
 Marketplaces based on this business model have more advantages, as they are able to expand their product assortment in third-party sales channels, generating more sales opportunities.
 
diff --git a/docs/tutorials/en/oms-page-structure.md b/docs/tutorials/en/oms-page-structure.md
index fa2016137..0ca4bf129 100644
--- a/docs/tutorials/en/oms-page-structure.md
+++ b/docs/tutorials/en/oms-page-structure.md
@@ -37,7 +37,7 @@ For all the data of order variations, and also for the numbers of evolution in t
 Important: If the order comparison is done based on 0 orders in the past, the variation is 0%.
 </div>
 
-![barra-status-oms en](//images.ctfassets.net/alneenqid6w5/3B36BC5ZO8q66GYEOoeOK4/051f7dea8deea96f4bdc321251cfca31/status_bar_en.png)
+![barra-status-oms en](https://images.ctfassets.net/alneenqid6w5/3B36BC5ZO8q66GYEOoeOK4/051f7dea8deea96f4bdc321251cfca31/status_bar_en.png)
 
 ### Filters
 
@@ -45,7 +45,7 @@ Allows you to apply multiple filters to see only the list of orders you want. Th
 
 - [How to filter requests](/en/tutorial/filtering-orders-on-the-oms/)
 
-![botão-filtro-oms en](//images.ctfassets.net/alneenqid6w5/UOgfCVBLUakMIOyKYMCuI/bfb88ea859e7c45fe3435048286d14de/filter_en.png)
+![botão-filtro-oms en](https://images.ctfassets.net/alneenqid6w5/UOgfCVBLUakMIOyKYMCuI/bfb88ea859e7c45fe3435048286d14de/filter_en.png)
 
 ### Search Bar
 
@@ -53,7 +53,7 @@ The search bar is used to search for the terms found in the order, such as order
 
 - [How to search for orders](http://help.vtex.com/en/tutorial/searching-for-orders-on-the-oms)
 
-![barra-search-oms en](//images.ctfassets.net/alneenqid6w5/2G2huhosg8iuG2a2uwKgme/f4a281931a68cf6866cb71838a336b11/search_bar_en.png)
+![barra-search-oms en](https://images.ctfassets.net/alneenqid6w5/2G2huhosg8iuG2a2uwKgme/f4a281931a68cf6866cb71838a336b11/search_bar_en.png)
 
 ### Information Bar
 
@@ -63,7 +63,7 @@ It also brings the store's sales ranking in relation to all other VTEX stores. T
 
 - [Interpreting the data of the order bar on the All Orders screen](http://help.vtex.com/en/tutorial/interpreting-the-data-of-the-oms-order-bar)
 
-![barra-info-oms en](//images.ctfassets.net/alneenqid6w5/6bcXNGPCDus62Y86ICu6ke/d660ca280398c5cd98415051f40ce1e0/info_bar_en.png)
+![barra-info-oms en](https://images.ctfassets.net/alneenqid6w5/6bcXNGPCDus62Y86ICu6ke/d660ca280398c5cd98415051f40ce1e0/info_bar_en.png)
 
 ### Export button
 
@@ -71,7 +71,7 @@ Used to export the orders brought by the search, always considering the filters
 
 - [Exporting orders with Orders Management](http://help.vtex.com/en/tutorial/exporting-orders-with-oms)
 
-![botão-export-oms en](//images.ctfassets.net/alneenqid6w5/2RGkY0fZjyG8yAWeM0cI2/885b73c5a94c50d94bf9d0ac9139249a/botao_export._en.png)
+![botão-export-oms en](https://images.ctfassets.net/alneenqid6w5/2RGkY0fZjyG8yAWeM0cI2/885b73c5a94c50d94bf9d0ac9139249a/botao_export._en.png)
 
 ### List of Orders
 
@@ -79,7 +79,7 @@ It is the main area of Orders Management. It brings the last orders made in the
 
 - [List of orders](/en/tutorial/list-of-orders/)
 
-![all-orders-oms en](//images.ctfassets.net/alneenqid6w5/GKQ3gsB6aAMAAiyWAWQSQ/d91077f73672ba17a4c026496c275b9b/orders_list_en.png)
+![all-orders-oms en](https://images.ctfassets.net/alneenqid6w5/GKQ3gsB6aAMAAiyWAWQSQ/d91077f73672ba17a4c026496c275b9b/orders_list_en.png)
 
 ### VTEX DO
 
@@ -87,7 +87,7 @@ It brings together the store's pending tasks and is generated by the different V
 
 - [How VTEX Do task list works.](http://help.vtex.com/en/tutorial/understanding-the-task-list-vtex-do)
 
-![VTEX-do-oms en](//images.ctfassets.net/alneenqid6w5/5JdvIU3YiIaKIYsWuIWKYa/524090c1e26b1319138bcc47e900ce77/vtex_do_en.png)
+![VTEX-do-oms en](https://images.ctfassets.net/alneenqid6w5/5JdvIU3YiIaKIYsWuIWKYa/524090c1e26b1319138bcc47e900ce77/vtex_do_en.png)
 
 ## Subscriptions
 
@@ -105,5 +105,5 @@ The second tab, **Affiliates**, is intended for affiliate configurations in your
 
 - [Configuring affiliates.](http://help.vtex.com/en/tutorial/configuring-affiliates/) 
 
-![settings-oms en](//images.ctfassets.net/alneenqid6w5/51iFkeJMnSWk4oswQOICoM/c119aa472d2f0db29b1c2db2a5e29bd2/settings_oms.png)
+![settings-oms en](https://images.ctfassets.net/alneenqid6w5/51iFkeJMnSWk4oswQOICoM/c119aa472d2f0db29b1c2db2a5e29bd2/settings_oms.png)
 
diff --git a/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
index 934f8ddd4..ceaa39883 100644
--- a/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
@@ -35,7 +35,7 @@ Once you have authenticated using the chosen method, you enter the support panel
 
 To open a ticket, simply click the __Send a request__ red button.
 
-![chamado financeiro1 EN](//images.ctfassets.net/alneenqid6w5/fJpJBPNaKcMSkuKau28eA/16c703c7fe792f12fd996f557a21651d/chamado_financeiro1_EN.png)
+![chamado financeiro1 EN](https://images.ctfassets.net/alneenqid6w5/fJpJBPNaKcMSkuKau28eA/16c703c7fe792f12fd996f557a21651d/chamado_financeiro1_EN.png)
 
 You will be taken to the ticket opening form, where you must fill in:
 - Your name.
@@ -45,7 +45,7 @@ You will be taken to the ticket opening form, where you must fill in:
 - The subject.
 - The question or problem.
 
-![chamado financeiro2 EN](//images.ctfassets.net/alneenqid6w5/1HAPK6tTKE2isE4KUuYuQ6/857347142afec501604095328eb785de/chamado_financeiro2_EN.png)
+![chamado financeiro2 EN](https://images.ctfassets.net/alneenqid6w5/1HAPK6tTKE2isE4KUuYuQ6/857347142afec501604095328eb785de/chamado_financeiro2_EN.png)
 
 You can also include attachments, such as screenshots or animated gifs, that help you describe the context of your request.
 
@@ -85,7 +85,7 @@ By clicking __My Requests__, you'll see the history of tickets opened by your ow
 
 If you click __All Requests__, you can see the history of tickets opened by any employees in your store.
 
-![chamado financeiro3 EN](//images.ctfassets.net/alneenqid6w5/2KBx2P4jCUkOyWkcSkMAKe/fb734b3e0dd80c2362d769f3336eec7f/chamado_financeiro3_EN.png)
+![chamado financeiro3 EN](https://images.ctfassets.net/alneenqid6w5/2KBx2P4jCUkOyWkcSkMAKe/fb734b3e0dd80c2362d769f3336eec7f/chamado_financeiro3_EN.png)
 
 ## The ticket statuses
 
@@ -100,4 +100,4 @@ After that, it goes through the statuses `Pending`, `Solved` and `Closed`.
 
 In your support panel, you can filter the tickets search by status. To do this, simply use the checkbox below the request button.
 
-![chamado financeiro4 EN](//images.ctfassets.net/alneenqid6w5/3Wy8oPFBYQO6KEQ0uQiy0y/a28356d8e2742fa8065b1bf097ea76c1/chamado_financeiro4_EN.png)
+![chamado financeiro4 EN](https://images.ctfassets.net/alneenqid6w5/3Wy8oPFBYQO6KEQ0uQiy0y/a28356d8e2742fa8065b1bf097ea76c1/chamado_financeiro4_EN.png)
diff --git a/docs/tutorials/en/opening-tickets-to-vtex-support.md b/docs/tutorials/en/opening-tickets-to-vtex-support.md
index e7347d696..c0c061bff 100644
--- a/docs/tutorials/en/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/en/opening-tickets-to-vtex-support.md
@@ -65,7 +65,7 @@ If you choose this option, you are required to fill in the information described
    * *I have a concern and would like to ask a question*
    * *I would like to request a setup*
 2. In the **Request subject** field, fill in the information about the type of problem you need help with. Based on your problem description, we will indicate some articles from the [Help Center](https://help.vtex.com/en/) that might help you solve your problem. If none of these articles can help you solve your problem, please move on to the next step.
-![https help.vtex.com en support](//images.ctfassets.net/alneenqid6w5/2HMCgvH7smDk0aRpZqbNx7/0daa37d669331fdeeea4c91ff8e41684/https___help.vtex.com_en_support.gif)
+![https help.vtex.com en support](https://images.ctfassets.net/alneenqid6w5/2HMCgvH7smDk0aRpZqbNx7/0daa37d669331fdeeea4c91ff8e41684/https___help.vtex.com_en_support.gif)
 3. Click `Continue`.
 You will be redirected to another page.
 4. In the Problem impact field, select the option that best describes the scenario:
diff --git a/docs/tutorials/en/operational-capacity-beta.md b/docs/tutorials/en/operational-capacity-beta.md
index 7fe75d9f1..48013a078 100644
--- a/docs/tutorials/en/operational-capacity-beta.md
+++ b/docs/tutorials/en/operational-capacity-beta.md
@@ -29,7 +29,7 @@ A good seller operational capacity management leads to the following advantages:
 
 When you go to the VTEX Admin under **Shipping > Operational Capacity**, you will find a page like the one below:
 
-![operational_capacity_image1_EN](//images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/87f03e4f1a667a76349095e450244602/operational_capacity_image1_EN.png)
+![operational_capacity_image1_EN](https://images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/87f03e4f1a667a76349095e450244602/operational_capacity_image1_EN.png)
 
 <div class="alert alert-warning">
 The sellers displayed on the interface are your operation's sellers, previously configured by our team. To add a new seller, contact <a href="https://help.vtex.com/en/support">our Support</a> team.
@@ -127,7 +127,7 @@ The platform has some restrictions regarding <a href="https://help.vtex.com/en/t
 
 The **Operational Capacity Status** chart shows, in real time, the percentage of the seller's capacity that has already been used, as in the image below:
 
-![operational_capacity_image2_EN](//images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/0bed6fad834c5b5ab6d22ce713abd11d/operational_capacity_image2_EN.png)
+![operational_capacity_image2_EN](https://images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/0bed6fad834c5b5ab6d22ce713abd11d/operational_capacity_image2_EN.png)
 
 The chart shows the following periods:
 
@@ -149,7 +149,7 @@ To edit the seller's address or identification name in **Operational Capacity**,
 
 In the **Operational Capacity** section, you can see the seller's current operational capacity settings for each day of the week, as in the following image:
 
-![operational_capacity_image3_EN](//images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/7aa99cf4ff1a7deb322671c5e1961537/operational_capacity_image3_EN.png)
+![operational_capacity_image3_EN](https://images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/7aa99cf4ff1a7deb322671c5e1961537/operational_capacity_image3_EN.png)
 
 To change these settings, follow the steps below:
 
diff --git a/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
index 17b554621..191e26055 100644
--- a/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
@@ -53,7 +53,7 @@ To disable the __Optimized Shipping Options__ function, follow the steps below:
 3. In the blue options menu located at the top of the page, click on __Checkout__.
 4. Under __Optimized Shipping Options__, click the <i class="fas fa-toggle-off"></i> to disable the __Optimize Shipping options display option__.
 
-![Optimized shipping options](//images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/838428bac6e785ad6472fd87c18f1e1c/Optimized_shipping_options_EN.PNG)
+![Optimized shipping options](https://images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/838428bac6e785ad6472fd87c18f1e1c/Optimized_shipping_options_EN.PNG)
 
 <ul>
   5. Click <b>Save</b>.
diff --git a/docs/tutorials/en/order-details-page.md b/docs/tutorials/en/order-details-page.md
index 6bd12e2f1..7acc134da 100644
--- a/docs/tutorials/en/order-details-page.md
+++ b/docs/tutorials/en/order-details-page.md
@@ -50,7 +50,7 @@ You will find below a list of all possible sections for the <b>Order details pag
 
 ## Top bar
 
-![BarrasuperiorEN](//images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/ee97e23a21b0ba350ee47cf6ded14cde/BarrasuperiorEN.jpg)
+![BarrasuperiorEN](https://images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/ee97e23a21b0ba350ee47cf6ded14cde/BarrasuperiorEN.jpg)
 
 The top bar contains the following information and actions:
 
@@ -64,7 +64,7 @@ The top bar contains the following information and actions:
 
 ## General information 
 
-![Informacao geraisEN](//images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/5a4a537da2ec23a9153aa7027a4b2c49/Informacao_geraisEN.jpg)
+![Informacao geraisEN](https://images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/5a4a537da2ec23a9153aa7027a4b2c49/Informacao_geraisEN.jpg)
 
 General order information is displayed at the top of the page, just below the top bar, and includes:
 
@@ -88,7 +88,7 @@ To learn more about the order flow and when to handle an order, read the article
 
 ### Items to invoice
 
-![Itens faturarEN](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
+![Itens faturarEN](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/c88e7dc843b651ed6b703ed4cd05ba3c/Itens_faturarEN.png)
 
 The block **Items to Invoice** contains packages with items for which payment has been approved but not yet [invoiced](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), i.e. their invoices have not been uploaded to the platform.
 
@@ -101,7 +101,7 @@ In the top left corner, the following actions are available:
 
 ###  Invoices
 
-![FaturaEN](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
+![FaturaEN](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/1f68c545e4a42383d85aa82b7dd6ba96/FaturaEN.png)
 
 This block displays the invoiced items with their respective invoices and the packages that make up the deliveries.
 
@@ -114,7 +114,7 @@ In this block, the retailer can:
 
 ### Returned items
 
-![Itens devolvidosEN](//images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/d6354bb77f2ab0ffa3f01f81afe5de19/Itens_devolvidosEN.png)
+![Itens devolvidosEN](https://images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/d6354bb77f2ab0ffa3f01f81afe5de19/Itens_devolvidosEN.png)
 
 The block **Returned Items** is displayed when order items are returned. See the information and actions available in this block:
 
@@ -128,7 +128,7 @@ The block **Returned Items** is displayed when order items are returned. See the
 
 ### History of changed items
 
-![Historico Itens alteradosEN](//images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/d96c4ca6d673fd5222086070ea9c64ae/Historico_Itens_alteradosEN.png)
+![Historico Itens alteradosEN](https://images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/d96c4ca6d673fd5222086070ea9c64ae/Historico_Itens_alteradosEN.png)
 
 This block is displayed when changes are made to order items. The **History of changed items** displays the details of the changes made, such as which items were added or removed, the date the change occurred, and the prices of the products (the price of the returned item, the price of the added item, and the difference between the two).
 
@@ -136,7 +136,7 @@ If there are changes in the final amount of the order, the difference will be di
 
 ### Order history
 
-![Historico pedidoEN](//images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/3d9701b380306223f795295b4ecf3cae/Historico_pedidoEN.jpg)
+![Historico pedidoEN](https://images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/3d9701b380306223f795295b4ecf3cae/Historico_pedidoEN.jpg)
 
 This block displays all the order activity and  interactions that took place within the order, with date and time information. 
 
@@ -150,7 +150,7 @@ You can also view details of notifications emailed to the customer by clicking o
 
 ### Comments
 
-![ComentariosEN](//images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/89520a487885e12fbacf0b7b614c1347/ComentariosEN.png)
+![ComentariosEN](https://images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/89520a487885e12fbacf0b7b614c1347/ComentariosEN.png)
 
 This section allows you to add internal comments with remarks about the order. To do this, you can type in the text box and click on `Send`.
 
@@ -158,7 +158,7 @@ Comments are recorded on the order details page with the date, time, and email a
 
 ## Financial details
 
-![Lateral](//images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/c9be1169615d4c8c08d6108fd4171395/LateralEN.png)
+![Lateral](https://images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/c9be1169615d4c8c08d6108fd4171395/LateralEN.png)
 
 On the right side of the page, you can view the financial details of the order. This information is updated automatically as the order progresses. 
 
diff --git a/docs/tutorials/en/order-flow-and-status.md b/docs/tutorials/en/order-flow-and-status.md
index e308e76fe..6f0fba9ef 100644
--- a/docs/tutorials/en/order-flow-and-status.md
+++ b/docs/tutorials/en/order-flow-and-status.md
@@ -41,7 +41,7 @@ For incomplete orders, check out the article <a href="https://help.vtex.com/en/t
 
 ### Marketplace flow
 
-![pedido_marketplace_en](//images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/315b6d8c70b8631d2be02c4dd659af98/pedido_marketplace_en.png)
+![pedido_marketplace_en](https://images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/315b6d8c70b8631d2be02c4dd659af98/pedido_marketplace_en.png)
 
 The marketplace flow is integrated with the seller flow. When an order delivered by an external seller (which is not the main seller) is finalized, this is the flow visible to the marketplace:
 
@@ -58,7 +58,7 @@ Learn how to identify orders from marketplaces in the article [Viewing marketpla
 
 ### Seller flow
 
-![pedido_fluxo_seller_en](//images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/9cc2dbb00ed43160d6e4699594107b22/pedido_fluxo_seller_en.png)
+![pedido_fluxo_seller_en](https://images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/9cc2dbb00ed43160d6e4699594107b22/pedido_fluxo_seller_en.png)
 
 This is the order flow visible to the store responsible for shipping the order products. In this case, the order was placed through another store (online marketplace), and the seller flow starts once the order is confirmed.
 
@@ -97,7 +97,7 @@ Please note that:
 
 ### Complete flow
 
-![pedido_fluxo_completo_en_2](//images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/4dffff0e3ad8bd51e4bdcacb14a10b50/pedido_fluxo_completo_en.png)
+![pedido_fluxo_completo_en_2](https://images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/4dffff0e3ad8bd51e4bdcacb14a10b50/pedido_fluxo_completo_en.png)
 
 The complete order flow is visible to the store that sells and delivers the order. It is composed of the marketplace flow followed by the seller flow.
 
@@ -142,7 +142,7 @@ Learn more about order cancellation in the article [Why was my order cancelled?]
 
 ### Chain flow
 
-![pedido_fluxo_chain_en](//images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/7617928cd9328c928ecd09d05b08af2e/pedido_fluxo_chain_en.png)
+![pedido_fluxo_chain_en](https://images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/7617928cd9328c928ecd09d05b08af2e/pedido_fluxo_chain_en.png)
 
 The order flow seen by the intermediate store in a [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) is similar to the marketplace order flow, except for receiving the payment for orders. In the `Payment pending` stage, instead of the chain receiving payment directly from the gateway, the marketplace informs the chain it has received the payment confirmation. 
 
diff --git a/docs/tutorials/en/order-in-the-name-of-a-customer-using-the-callcenter.md b/docs/tutorials/en/order-in-the-name-of-a-customer-using-the-callcenter.md
index 595124c92..ad1518e4e 100644
--- a/docs/tutorials/en/order-in-the-name-of-a-customer-using-the-callcenter.md
+++ b/docs/tutorials/en/order-in-the-name-of-a-customer-using-the-callcenter.md
@@ -21,11 +21,11 @@ The toolbar appears once the registered operator logs on to the store environmen
 
 To order in the name of a customer using the callcenter, the operator needs to click on **Login as**, in the right-hand corner of the toolbar.
 
-![Callcenter operator personifying the customer with the toolbar](//images.contentful.com/alneenqid6w5/3rWoDmY4paceYWKEW2cg2S/c7edba682c7fd97b25d0fdc01faf1f9b/toolbar-1-1.png)
+![Callcenter operator personifying the customer with the toolbar](https://images.contentful.com/alneenqid6w5/3rWoDmY4paceYWKEW2cg2S/c7edba682c7fd97b25d0fdc01faf1f9b/toolbar-1-1.png)
 
 Having done this, the customer’s e-mail is displayed in this same area.
 
 To log on as another user, just click on the **Change customer** button.
 
-![Customer personified with the toolbar](//images.contentful.com/alneenqid6w5/TwHPvbhB8Os02kO4IaS66/d70f2a05303502043ae4d7be3dfce59f/Toolbar2.png)
+![Customer personified with the toolbar](https://images.contentful.com/alneenqid6w5/TwHPvbhB8Os02kO4IaS66/d70f2a05303502043ae4d7be3dfce59f/Toolbar2.png)
 
diff --git a/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md b/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
index 5d3a6b20d..0b7fed995 100644
--- a/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
+++ b/docs/tutorials/en/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
@@ -29,6 +29,6 @@ Among all SKU images, the principal image will be that marked as the principal i
 
 As you can see in the example below, even not being the first image registered, the image defined as principal appears on the product page when the SKU is selected.
 
-![sku_imagem_principal en](//images.ctfassets.net/alneenqid6w5/391ITg389WwqEsUYe2sUe8/0b7ae4c9e54ce81ef067a4bba83712e3/ex_2__en.png)
+![sku_imagem_principal en](https://images.ctfassets.net/alneenqid6w5/391ITg389WwqEsUYe2sUe8/0b7ae4c9e54ce81ef067a4bba83712e3/ex_2__en.png)
 
 - When uploading the image spreadsheet, the platform considers line by line; then, the first line of a sku will be considered the main one and so on.
diff --git a/docs/tutorials/en/orders-list.md b/docs/tutorials/en/orders-list.md
index d4d49a290..e6c292693 100644
--- a/docs/tutorials/en/orders-list.md
+++ b/docs/tutorials/en/orders-list.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Using the list of orders from the Orders Managment, stores owner can monitor purchases made in their store. The list is available on the first screen of the Orders Managment module.
 
-![todosospedidos.en](//images.ctfassets.net/alneenqid6w5/4ovDqNLqLNMUxrwjgQ8oDx/2557b8aa39c07af3ce23f85508b49de3/todosospedidos.en.png)
+![todosospedidos.en](https://images.ctfassets.net/alneenqid6w5/4ovDqNLqLNMUxrwjgQ8oDx/2557b8aa39c07af3ce23f85508b49de3/todosospedidos.en.png)
 
 The standard view lists all store orders, beginning with the most recent. You can change the order by clicking on the column names, as well as by searching or filtering the orders using specific data, in addition to exporting this data.
 
@@ -30,7 +30,7 @@ By clicking on any order, the user is directed to the order details page.
 
 Whenever Orders Managment is open and new orders are placed, a notice will be displayed, allowing you to click and update the list of orders.
 
-![novopedido.en](//images.ctfassets.net/alneenqid6w5/7c1NoN8MjO6b9jI6YAUVzM/6b461e799f1dd8f7039bf9a8b1755ae5/novopedido.en.png)
+![novopedido.en](https://images.ctfassets.net/alneenqid6w5/7c1NoN8MjO6b9jI6YAUVzM/6b461e799f1dd8f7039bf9a8b1755ae5/novopedido.en.png)
 
 See more details about the columns on the list below:
 
@@ -38,7 +38,7 @@ See more details about the columns on the list below:
 
 Nothing more than the order number (displayed to the customer), with the suffix and the sequential transaction code (for in-house use).
 
-![nsequencial.en](//images.ctfassets.net/alneenqid6w5/4BOiejle8VtmGM364EiKXl/bb1e5d5d8b1020ce6d89c01262ef644c/nsequencial.en.png)
+![nsequencial.en](https://images.ctfassets.net/alneenqid6w5/4BOiejle8VtmGM364EiKXl/bb1e5d5d8b1020ce6d89c01262ef644c/nsequencial.en.png)
 
 ### Order number
 
@@ -75,7 +75,7 @@ Always contains the name and surname of the customer who made the purchase, even
 
 Shows how many different products the order contains (without taking into account the quantity of each item purchased). Moving the mouse makes it possible to see which products were purchased.
 
-![oms produtos do pedido](//images.contentful.com/alneenqid6w5/4fTIEf2ywwc2U2IuwSkg8U/82b81b00387db8959cf18ae392e5e1f0/oms-produtos-do-pedido.png)
+![oms produtos do pedido](https://images.contentful.com/alneenqid6w5/4fTIEf2ywwc2U2IuwSkg8U/82b81b00387db8959cf18ae392e5e1f0/oms-produtos-do-pedido.png)
 
 ## Amount
 
diff --git a/docs/tutorials/en/overview-pricing-module.md b/docs/tutorials/en/overview-pricing-module.md
index ff2529e27..2cc6014fc 100644
--- a/docs/tutorials/en/overview-pricing-module.md
+++ b/docs/tutorials/en/overview-pricing-module.md
@@ -21,7 +21,7 @@ There are four departments within this module responsible for configuring each o
 
 ## Campaign Audiences
 
-![campanha-en](//images.ctfassets.net/alneenqid6w5/5K7LSd8kVJ6Zq1EnDUPxHF/17299aa9e8c91b40b427b402e6c09e70/campanha-en.png)
+![campanha-en](https://images.ctfassets.net/alneenqid6w5/5K7LSd8kVJ6Zq1EnDUPxHF/17299aa9e8c91b40b427b402e6c09e70/campanha-en.png)
 
 A campaign audience is a way of defining the target audience to which a benefit can be applied. In other words, you can create customer segments based on the definition of some criteria that will be eligible for a given campaign audience and consequently one or more benefits. A campaign audience can be associated with one or more campaign benefits.
 
@@ -29,7 +29,7 @@ A campaign audience is a way of defining the target audience to which a benefit
 
 ## Benefits
 
-![promoções.en](//images.ctfassets.net/alneenqid6w5/23MV9Zb4N0CLUcyoeZaP1r/08a7f435db69a7a826ba336b58603a45/promo____es.en.png)
+![promoções.en](https://images.ctfassets.net/alneenqid6w5/23MV9Zb4N0CLUcyoeZaP1r/08a7f435db69a7a826ba336b58603a45/promo____es.en.png)
 
 Here, the discounts that your store will offer are created. You can also view, filter, search and file all promotions. According to each store configuration, there is a limit of promotions that can be enabled at the same time. To find out how many, read the message that appears on the upper right corner, below the paging. The types of promotions that can be created are:
 
@@ -42,12 +42,12 @@ Here, the discounts that your store will offer are created. You can also view, f
 
 ## Coupons
 
-![cupons.en](//images.ctfassets.net/alneenqid6w5/4dFwRo3yG2ZLWwFosYJBRI/5a717e969314bd7492d9a6d1d4f24f7a/cupons.en.png)
+![cupons.en](https://images.ctfassets.net/alneenqid6w5/4dFwRo3yG2ZLWwFosYJBRI/5a717e969314bd7492d9a6d1d4f24f7a/cupons.en.png)
 
 It's in this department that the coupons are created, but you can also search and file them. [Learn how to create coupons in our documentation](/en/tutorial/creating-a-coupon/).
 
 ## Taxes
 
-![taxas.en](//images.ctfassets.net/alneenqid6w5/4kQJ4px0w7kUgDdzmc1lR0/f9ee86721f6888e957be3db820f3afbb/taxas.en.png)
+![taxas.en](https://images.ctfassets.net/alneenqid6w5/4kQJ4px0w7kUgDdzmc1lR0/f9ee86721f6888e957be3db820f3afbb/taxas.en.png)
 
 Here, you can define the incidence of taxes on your products. You can also filter, search and file fees. [To better understand the characteristics of this configuration, check out our article about fees.](/en/tutorial/creating-surchargestaxes)
diff --git a/docs/tutorials/en/partner-program-intranet-and-vtex-store-manual.md b/docs/tutorials/en/partner-program-intranet-and-vtex-store-manual.md
index 6cf235f6d..690229600 100644
--- a/docs/tutorials/en/partner-program-intranet-and-vtex-store-manual.md
+++ b/docs/tutorials/en/partner-program-intranet-and-vtex-store-manual.md
@@ -21,40 +21,40 @@ Access URL: http://extrato.vtex.com
 
 ## Profile
 This is the first step, you must fill out the information about your company. This is the information that will be displayed on the VTEX Store.
-![partner intranet 1](//images.contentful.com/alneenqid6w5/6n5cqrsG3uEuqE0w88882M/87f7eb33ae50e6d0783dc1ea5a121aca/partner_intranet_1.png)
+![partner intranet 1](https://images.contentful.com/alneenqid6w5/6n5cqrsG3uEuqE0w88882M/87f7eb33ae50e6d0783dc1ea5a121aca/partner_intranet_1.png)
 
 ### Header color
 In the first step there are some fields that deserve your attention, such as the header color. Where will it be applied? On your company’s page on the VTEX Store, as it is demonstrated in the image.
-![partner intranet 2](//images.contentful.com/alneenqid6w5/13tICp7cXoiOseM2AOYYEc/aaf98faa4e33f47e517f2204fec9dcd2/partner_intranet_2.png)
+![partner intranet 2](https://images.contentful.com/alneenqid6w5/13tICp7cXoiOseM2AOYYEc/aaf98faa4e33f47e517f2204fec9dcd2/partner_intranet_2.png)
 
 ### Offices
 Another point that deserves attention is the inclusion of the company’s offices, ex: New York, San Francisco, or abroad. After adding each one of the offices, you will need to list the services they provide.
-![partner intranet 3](//images.contentful.com/alneenqid6w5/6JZIkI0N5SKgySUW46W2Yc/64069026123057856b3430bf4e4e5344/partner_intranet_3.png)
+![partner intranet 3](https://images.contentful.com/alneenqid6w5/6JZIkI0N5SKgySUW46W2Yc/64069026123057856b3430bf4e4e5344/partner_intranet_3.png)
 
 ## My team
 In this step you will register the company staff that needs access to our VTEX Partner training program and sandbox (VTEX academy)
-![partner intranet 4](//images.contentful.com/alneenqid6w5/4AmT9EOi6AC6CUIa6gK8uq/c79b462dad40ededc388903d6de2535c/partner_intranet_4.png)
+![partner intranet 4](https://images.contentful.com/alneenqid6w5/4AmT9EOi6AC6CUIa6gK8uq/c79b462dad40ededc388903d6de2535c/partner_intranet_4.png)
 
 ## Certifications
 After your team gets certified, you will need to update this page with the certifications your company has. The VTEX team will verify if the certifications have been properly completed and upon confirmation, the certification badge will be display as show in the image.
-![partner intranet 5](//images.contentful.com/alneenqid6w5/1Iq4VXwlUQimW0kQmqsIe8/9038bd2510ba516cbc72596a41d7a25f/partner_intranet_5.png)
+![partner intranet 5](https://images.contentful.com/alneenqid6w5/1Iq4VXwlUQimW0kQmqsIe8/9038bd2510ba516cbc72596a41d7a25f/partner_intranet_5.png)
 
 ## Services
 In this step you must enter the services your company provides, generally classified as: Layout Design and Implementation, Project Management and Postlaunch Support. These services will be shown on the VTEX Store for our clients to find.
-![partner intranet 6](//images.contentful.com/alneenqid6w5/1x3zqdaxMgGU4CKsKi4i8c/8484f7197c8643388a716e0e595f9763/partner_intranet_6.png)
+![partner intranet 6](https://images.contentful.com/alneenqid6w5/1x3zqdaxMgGU4CKsKi4i8c/8484f7197c8643388a716e0e595f9763/partner_intranet_6.png)
 
 ### VTEX Store
 In the image it is possible to see the shelf of the services/solutions according to what you have selected.
-![partner intranet 7](//images.contentful.com/alneenqid6w5/3jJA8IyIkgcEmSYy8W6wam/34407ce97bfcc75431fdc9960d91fd2b/partner_intranet_7.png)
+![partner intranet 7](https://images.contentful.com/alneenqid6w5/3jJA8IyIkgcEmSYy8W6wam/34407ce97bfcc75431fdc9960d91fd2b/partner_intranet_7.png)
 
 ## Earnings
 On Earnings the company's accounting team will be able to keep track of fees that were earned by reselling the VTEX platform, which are granted only to certified Resellers.
-![partner intranet 8](//images.contentful.com/alneenqid6w5/2TB5pCAgr6qKqQmsuY0kgU/47bcbdbf15c7101612dddbc8901a8f99/partner_intranet_8.png)
+![partner intranet 8](https://images.contentful.com/alneenqid6w5/2TB5pCAgr6qKqQmsuY0kgU/47bcbdbf15c7101612dddbc8901a8f99/partner_intranet_8.png)
 
 ## User management
 In this page you must register everyone from your company that needs access to the VTEX Intranet. We recommend that you limit the access to one person from accounting and one or two more people as administrators.
-![partner intranet 9](//images.contentful.com/alneenqid6w5/2aFx9YxuAMOEAEIOOos6Gg/82e8c287becc9b2ccbd9590ce4a6fb6e/partner_intranet_9.png)
+![partner intranet 9](https://images.contentful.com/alneenqid6w5/2aFx9YxuAMOEAEIOOos6Gg/82e8c287becc9b2ccbd9590ce4a6fb6e/partner_intranet_9.png)
 
 ## VTEX Channels
 In the top menu you can find all the communication channels you have access to as our partner.
-![partner intranet 10](//images.contentful.com/alneenqid6w5/5Pa8OjOuyWwigKwmqCSK66/96fb124b8400feb3abd78317be03037c/partner_intranet_10.png)
+![partner intranet 10](https://images.contentful.com/alneenqid6w5/5Pa8OjOuyWwigKwmqCSK66/96fb124b8400feb3abd78317be03037c/partner_intranet_10.png)
diff --git a/docs/tutorials/en/payment-provider-protocol.md b/docs/tutorials/en/payment-provider-protocol.md
index c36e6d7a0..70a76eb6a 100644
--- a/docs/tutorials/en/payment-provider-protocol.md
+++ b/docs/tutorials/en/payment-provider-protocol.md
@@ -95,7 +95,7 @@ In some cases, connectors can be built for a specific solution. The references b
 
 After getting access information and implementing the backend, the provider has to install the Payment Provider Test Suite app to access the testing tool. The installation is done through the VTEX App Store.
 
-![ppp-vtex-store-en](//images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/ea2026578b79d3c5edd33c997b62efa9/image.png)
+![ppp-vtex-store-en](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/ea2026578b79d3c5edd33c997b62efa9/image.png)
 
 <div class="alert alert-warning">
 <p>To pass the homologation process, you need to implement specific logic to handle the test requirements. When sending requests to Test Suite, use the extra header <code>X-VTEX-API-Is-TestSuite = true</code> to identify them and mask any required case.<br><br>All communication with servers, whether during the homologation process or in production, must be via HTTPS, which by default uses port 443. Note that all HTTPS communication must be exclusively over TLS 1.2.
@@ -118,7 +118,7 @@ Then, you will find a form with three sections: Service information, Payment met
 </p>
 </div>
 
-![Payment Provider Test Suite 0](//images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
+![Payment Provider Test Suite 0](https://images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
 
 #### Payment method
 
@@ -128,7 +128,7 @@ After completing the Service URL field, Test Suite will validate the[ Manifest e
 
 In this section, you need to select the cases you want to test. If you are testing a credit card method, your integration must pass the Approved, Denied, Cancellation, Async Approved, and Async Denied cases. Only the Redirect flow is required for a payment method with [redirect](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows#redirect).
 
-![ppp-config-en](//images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/d49d66d80caa61f70720395a5dfca49b/image.png)
+![ppp-config-en](https://images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/d49d66d80caa61f70720395a5dfca49b/image.png)
 
 ### 4. Testing
 
@@ -159,18 +159,18 @@ Use the following numbers to identify how to correctly respond to each credit ca
 
 After running the tests, the system will display the Test Report, where you can see the detailed results of each test case. This way, you can have more visibility into what should be adjusted if an error occurs.
 
-![Payment Provider Test Suite 2_EN](//images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/ee1f759bf436aa38fff080f561ce4eb7/Payment_Provider_Test_Suite_2_EN.JPG)
+![Payment Provider Test Suite 2_EN](https://images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/ee1f759bf436aa38fff080f561ce4eb7/Payment_Provider_Test_Suite_2_EN.JPG)
 
 To see the messages exchanged between Test Suite and the payment provider implementation, click the Inspect Log button for the test case you want. A modal will open showing the message list and the payload of each request and response. The button in the upper right corner allows you to copy the code to the clipboard.
 
-![Payment Provider Test Suite Logs_EN](//images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/87c2ba89961c5bf5a73532ea073b4083/Payment_Provider_Test_Suite_Logs_en.JPG)
+![Payment Provider Test Suite Logs_EN](https://images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/87c2ba89961c5bf5a73532ea073b4083/Payment_Provider_Test_Suite_Logs_en.JPG)
 
 ## Payment protocol flow
 Here we explain the integrated payment stream in detail. The image below illustrates the entire flow, showing VTEX Payments and the responsibilities of your supplier.
 
 It all starts with requesting a new payment after the creation of a new order. VTEX creates a new payment representation and proceeds to the payments processing.
 
-![fluxo-atualizado-ppp](//images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
 
 <div class="alert alert-info">
   The default period of 7 days for asynchronous payment retries is only applied when the user does not specify a value in the <code>delayToCancel</code> field of the <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> endpoint or when sending the callbackURL.</div>
@@ -188,7 +188,7 @@ In any case, once the processing is completed and the provider has a final statu
 
 The complete flow with __undefined__ status and use of notification can be seen below:
 
-![Payment authorization callback notification flow](//images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/a72be587d650da053ecbe220a5daa642/image1.png)
+![Payment authorization callback notification flow](https://images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/a72be587d650da053ecbe220a5daa642/image1.png)
 
 1. The payment authorization is initiated when the gateway calls the Create Payment (__/payment__) endpoint for the provider. The `callbackUrl` field is submitted in the body of the request and contains the URL to send the notification.
 2. The payment occurs asynchronously (it does not generate the final status when the transaction is initiated). The gateway then receives the response with __undefined__ status and waits for the payment processing to be completed. Finally, once the processing is completed, the final status (__approved__ or __denied__) is updated.
@@ -197,7 +197,7 @@ The complete flow with __undefined__ status and use of notification can be seen
 
 The complete flow with __undefined__ status and use of __retry__ can be seen below:
 
-![Payment authorization callback retry flow](//images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/3f43bcbf5d48a9c459b553ca6ad7b216/image2.png)
+![Payment authorization callback retry flow](https://images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/3f43bcbf5d48a9c459b553ca6ad7b216/image2.png)
 
 1. The payment authorization is initiated when the gateway calls the Create Payment (__/payment__) endpoint for the provider. The `callbackUrl` field is submitted in the body of the request and contains the URL of the retry endpoint.
 2. The payment occurs asynchronously (it does not generate the final status when the transaction is initiated). The gateway then receives the response with __undefined__ status and waits for the payment processing to be completed. Finally, once the processing is completed, the final status (__approved__ or __denied__) is updated.
diff --git a/docs/tutorials/en/payu-romania-refund-details.md b/docs/tutorials/en/payu-romania-refund-details.md
index 3ad0c60d5..c9c63a1b9 100644
--- a/docs/tutorials/en/payu-romania-refund-details.md
+++ b/docs/tutorials/en/payu-romania-refund-details.md
@@ -38,7 +38,7 @@ If the Delete button is not active and the timeout has not expired, you can quic
 
 If the void or refund request has already been sent by the system to the issuing bank, we will no longer be able to delete/stop it in any way.
 
-![PayU Romania](//images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
+![PayU Romania](https://images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
 
 Once PayU has sent the void or refund request to the issuing bank, the status of the order will be updated in the PayU cPanel as `REVERSE` (for voids) or `REFUND`. And VTEX is going to receive a webhook from PaymentsOS, so the order status can also be updated on the platform (on Payments and consequently reflected in the OMS).
 
diff --git a/docs/tutorials/en/pci-gateway-overview.md b/docs/tutorials/en/pci-gateway-overview.md
index 8c820615b..3081d97ad 100644
--- a/docs/tutorials/en/pci-gateway-overview.md
+++ b/docs/tutorials/en/pci-gateway-overview.md
@@ -19,7 +19,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 # Starting to use
 
-![new-admin-payments](//images.ctfassets.net/alneenqid6w5/7w2PFtni9ykY0qGuasgU84/32d9c5341fb170a8b02abbea0ee3c628/NEW_ADMIN_PAGAMENTOS_EN.png)
+![new-admin-payments](https://images.ctfassets.net/alneenqid6w5/7w2PFtni9ykY0qGuasgU84/32d9c5341fb170a8b02abbea0ee3c628/NEW_ADMIN_PAGAMENTOS_EN.png)
 
 Designed to provide maximum flexibility when it comes to payment configurations, VTEX Payments module processes transactions based on some business concepts. Understand each one:
 
diff --git a/docs/tutorials/en/permissions-management-in-b2b-suite.md b/docs/tutorials/en/permissions-management-in-b2b-suite.md
index 72ac8b27e..9e03a0180 100644
--- a/docs/tutorials/en/permissions-management-in-b2b-suite.md
+++ b/docs/tutorials/en/permissions-management-in-b2b-suite.md
@@ -63,6 +63,6 @@ Click a role available in the store.
 
 5. Click `Save`.
 
-![Gerenciamento de permissões - EN](//images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/8cab9bcae960a2f30d855789b065a0ee/Gerenciamento_de_permiss_es_-_EN.gif)
+![Gerenciamento de permissões - EN](https://images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/8cab9bcae960a2f30d855789b065a0ee/Gerenciamento_de_permiss_es_-_EN.gif)
 
 Once you have associated the roles with the desired permissions, you can assign them to users. Learn more in [B2B Organizations](https://developers.vtex.com/docs/guides/vtex-b2b-organizations#users).
diff --git a/docs/tutorials/en/physical-store-instore-beta.md b/docs/tutorials/en/physical-store-instore-beta.md
index 2047b0ec1..224622d5c 100644
--- a/docs/tutorials/en/physical-store-instore-beta.md
+++ b/docs/tutorials/en/physical-store-instore-beta.md
@@ -28,7 +28,7 @@ This page allows you to perform the following actions:
 * [Edit](#editing-a-store)
 * [Delete](#editing-a-store)
 
-![loja-fisica-EN](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
+![loja-fisica-EN](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/516078c3146ebc1f4a7905faed445098/image.png)
 
 The page displays the following information: 
 
@@ -53,7 +53,7 @@ You can add a physical store by following the steps below:
 
 ### Physical store fields
 
-![loja-fisica2-en](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
+![loja-fisica2-en](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/6a50e8a8cd3f452b4102af5871ede996/image.png)
 
 #### Identification
 
diff --git a/docs/tutorials/en/pickup-points-for-subscription-orders.md b/docs/tutorials/en/pickup-points-for-subscription-orders.md
index 91f074ac0..f3dd39c32 100644
--- a/docs/tutorials/en/pickup-points-for-subscription-orders.md
+++ b/docs/tutorials/en/pickup-points-for-subscription-orders.md
@@ -41,7 +41,7 @@ To offer pickup points for subscription orders, you must fulfill the logistical
 
 Customers can choose pickup points for items in a subscription order at checkout, as illustrated in the image below.
 
-![subscriptionspickup EN](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
+![subscriptionspickup EN](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/4b70cfdbea58f1b53f482f61ef57d285/subscriptionspickup_EN.gif)
 
 You can also assign pickup points when [creating new subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#post_api-rns-pub-subscriptions) via the [Subscriptions API](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1). For existing subscriptions, you can change the delivery address by using the [API subscription upgrade route](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#patch_api-rns-pub-subscriptions-id) to start using a pickup point.
 
diff --git a/docs/tutorials/en/pickup-points.md b/docs/tutorials/en/pickup-points.md
index e1adf41c4..5f4f397d6 100644
--- a/docs/tutorials/en/pickup-points.md
+++ b/docs/tutorials/en/pickup-points.md
@@ -72,7 +72,7 @@ VTEX considers the pickup point to be a shipping method, and therefore the setti
     - Step 2: On the **Shipping Policies** tab, select the shipping policy created for the pickup point.
     - Step 3: In the **Actions** column, click on the <i class="fas fa-pen"></i> icon for editing.
     - Step 4: Enable the <i class="fas fa-toggle-on"></i> of the **Link pickup points** field.
-    - Step 5: Select the pickup point from the available fields. ![relacionarpontosretiradaEN](//images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/6df4f0848577031ee8dcab4898061a62/relacionarpontosretiradaEN.png)<div class = "alert alert-info">For stores that have more than 50 pick points, we recommend using the Pickup Point Tags field when creating a pick point. Using tags makes it easier to find the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140#adding-a-shipping-policy">pickup points when linking them to the shipping policy.</a> Also remember that the shipping policy that is linked to a pickup point will not be available for any other shipping method. We recommend creating a shipping policy that is exclusive to the pickup point.</div>
+    - Step 5: Select the pickup point from the available fields. ![relacionarpontosretiradaEN](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/6df4f0848577031ee8dcab4898061a62/relacionarpontosretiradaEN.png)<div class = "alert alert-info">For stores that have more than 50 pick points, we recommend using the Pickup Point Tags field when creating a pick point. Using tags makes it easier to find the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140#adding-a-shipping-policy">pickup points when linking them to the shipping policy.</a> Also remember that the shipping policy that is linked to a pickup point will not be available for any other shipping method. We recommend creating a shipping policy that is exclusive to the pickup point.</div>
 
 4. [Registering geolocation](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): for greater accuracy of the location of the pickup points at the checkout.<div class = "alert alert-info">Viewing pickup points with map and time at checkout is only available for Checkout V6.</div>
 
@@ -80,7 +80,7 @@ VTEX considers the pickup point to be a shipping method, and therefore the setti
     - Step 1: In the VTEX Admin, go to **Store settings > Storefront > Checkout**, or type *Checkout* in the search bar at the top of the page.  
     - Step 2: Select the configuration used in the store and click the <i class="fas fa-cog"></i> icon.
     - Step 3: Click the **Checkout** tab in the top bar.
-    - Step 4: Select the <i class="fas fa-toggle-on"></i> from the **Invoice address in pickup**.![NFpontoretiradaEN](//images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/a221ea377c5b7629eba243f55cf80058/NFpontoretiradaEN.png)<div class="alert alert-warning">The option of <b>Invoice address in pickup</b> must be enabled in all stores in Brazil, as it is a requirement that the invoice issued contains the customer's address information, even if the option to delivery of the order is at the pick-up point. The address filled in by the customer will be recorded in the `invoiceData` field of the <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - Step 4: Select the <i class="fas fa-toggle-on"></i> from the **Invoice address in pickup**.![NFpontoretiradaEN](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/a221ea377c5b7629eba243f55cf80058/NFpontoretiradaEN.png)<div class="alert alert-warning">The option of <b>Invoice address in pickup</b> must be enabled in all stores in Brazil, as it is a requirement that the invoice issued contains the customer's address information, even if the option to delivery of the order is at the pick-up point. The address filled in by the customer will be recorded in the `invoiceData` field of the <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
 
 6. Set the amount of pickup points that are displayed at checkout:
     - Step 1: In the VTEX Admin, go to **Store settings > Shipping > Settings**, or type *Shipping* in the search bar at the top of the page and select *Store settings / Shipping*.    
diff --git a/docs/tutorials/en/planner-calendar-page-beta.md b/docs/tutorials/en/planner-calendar-page-beta.md
index a3a55b0aa..3c32dbdd5 100644
--- a/docs/tutorials/en/planner-calendar-page-beta.md
+++ b/docs/tutorials/en/planner-calendar-page-beta.md
@@ -40,7 +40,7 @@ You can view the **Calendar** page in three ways:
 
 In the following image, you will see the view per month and what you can do in the interface:
 
-![releases-calendar-monthly-view-en](//images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6dc0c1f3eef1fa4aef0bbd7a6f462f63/releases-calendar-monthly-view-en.png)
+![releases-calendar-monthly-view-en](https://images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6dc0c1f3eef1fa4aef0bbd7a6f462f63/releases-calendar-monthly-view-en.png)
 
 In this page, you can:
 
@@ -58,7 +58,7 @@ In this page, you can:
 
 In the following image, you'll see the view per week and what you can do in the interface:
 
-![releases-calendar-weekly-view-en](//images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/a968361f0e0d1f0eece420ff190c1a94/releases-calendar-weekly-view-en.png)
+![releases-calendar-weekly-view-en](https://images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/a968361f0e0d1f0eece420ff190c1a94/releases-calendar-weekly-view-en.png)
 
 In this page, you can:
 
@@ -76,7 +76,7 @@ In this page, you can:
 
 In the following image, you'll see the view per day and what you can do in the interface:
 
-![daily view v2 en](//images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/b41cc39641404cceacfee3fb47d35615/daily_view_v2_en.png)
+![daily view v2 en](https://images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/b41cc39641404cceacfee3fb47d35615/daily_view_v2_en.png)
 
 Apart from viewing information about the release, in this page, you can:
 
diff --git a/docs/tutorials/en/planner-releases-page-beta.md b/docs/tutorials/en/planner-releases-page-beta.md
index 96b5a19a8..cf3c530f4 100644
--- a/docs/tutorials/en/planner-releases-page-beta.md
+++ b/docs/tutorials/en/planner-releases-page-beta.md
@@ -35,7 +35,7 @@ The order of the scheduled releases is based on the publication date: The furthe
 
 Go to the **Releases** navigation menu to access the **Releases** page in the VTEX Admin. In the following image, you'll see the interface and what you can do in it:
 
-![Releases list view v2 - EN](//images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/431af585bfbfef7f3920e38aca9aab6b/Releases_list_view_v2_-_EN.png)
+![Releases list view v2 - EN](https://images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/431af585bfbfef7f3920e38aca9aab6b/Releases_list_view_v2_-_EN.png)
 
 | **Field** | **Description** |
 |---|---|
diff --git a/docs/tutorials/en/price-divergence-rule.md b/docs/tutorials/en/price-divergence-rule.md
index 38db6e3f8..df0de45d0 100644
--- a/docs/tutorials/en/price-divergence-rule.md
+++ b/docs/tutorials/en/price-divergence-rule.md
@@ -29,7 +29,7 @@ The Price Divergence rule is composed of one or more order authorization rules.
 - **Automatically deny:** Orders with a price difference within the defined range are automatically rejected and are not integrated.
 - **Create a task in VTEX DO for approval:** For price differences within the defined range, the order is integrated but needs to be [manually approved](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#approving-orders-manually) by an authorized user.
 
-![price_divergence_rules_EN](//images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/813c44996850c4bd68a5ea4be1a92f41/price_divergence_rules_EN.png)
+![price_divergence_rules_EN](https://images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/813c44996850c4bd68a5ea4be1a92f41/price_divergence_rules_EN.png)
 
 When the [Price Divergence rule configuration](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) was not made, orders with price divergence errors are automatically approved. This applies to VTEX marketplaces, external marketplaces, and certified connectors (partners), but not to [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex).
 
diff --git a/docs/tutorials/en/price-divergence-rules-beta.md b/docs/tutorials/en/price-divergence-rules-beta.md
index eedbdc967..049ed51de 100644
--- a/docs/tutorials/en/price-divergence-rules-beta.md
+++ b/docs/tutorials/en/price-divergence-rules-beta.md
@@ -23,7 +23,7 @@ Integrations between VTEX sellers and [native connectors](https://help.vtex.com/
 
 Orders whose price difference is greater than the values configured in the integration are not automatically sent to the OMS. This causes orders to remain on “error” status in the `Orders` section, in the *INTEGRATIONS* module of the Admin, waiting to be manually approved.
 
-![divergenciadepreçosEN-01](//images.contentful.com/alneenqid6w5/4mjfgTHC1DrhmprHMU4akp/7085908f63fefc87357e95f6bb363dd9/divergenciadepre__osEN-01.gif)
+![divergenciadepreçosEN-01](https://images.contentful.com/alneenqid6w5/4mjfgTHC1DrhmprHMU4akp/7085908f63fefc87357e95f6bb363dd9/divergenciadepre__osEN-01.gif)
 
 To send orders with price divergence to the OMS, we have created the price divergence rule (Beta). According to this rule, all orders that diverge in price are sent to the OMS and must be manually approved by the individual in charge — the person whose email address is listed under *Account management > Accounts*. You can add more than one email address.
 
@@ -44,7 +44,7 @@ You can configure the price divergence rule by:
 
 ### Creating rules
 
-![barra regradivergenciaEN](//images.contentful.com/alneenqid6w5/DqcEZulHBr5XuNbF8LWDn/3aa409e8d104ed4beb73a5dd33886d97/barra_regradivergenciaEN.JPG)
+![barra regradivergenciaEN](https://images.contentful.com/alneenqid6w5/DqcEZulHBr5XuNbF8LWDn/3aa409e8d104ed4beb73a5dd33886d97/barra_regradivergenciaEN.JPG)
 
 To create a rule, follow the steps below:
 
@@ -76,7 +76,7 @@ To edit existing rules, follow the steps below:
 5. Edit the rule you want by changing the percentage bar.
 6. Then click on `Save rules`.
 
-![divergenciadepreçosEN-02](//images.contentful.com/alneenqid6w5/19JIIISSI8aKitR5Alvzfy/9f0135552d26f4353df30374a361c6a6/divergenciadepre__osEN-02.gif)
+![divergenciadepreçosEN-02](https://images.contentful.com/alneenqid6w5/19JIIISSI8aKitR5Alvzfy/9f0135552d26f4353df30374a361c6a6/divergenciadepre__osEN-02.gif)
 
 ## Order authorization
 
@@ -99,7 +99,7 @@ To authorize orders manually, follow the steps below:
 4. Select the order with the status `Waiting for manual authorization` that you want to approve. 
 5. Click on `Approve order`.
 
-![divergenciadepreçosEN-03](//images.contentful.com/alneenqid6w5/5HVasmtuyHSGDmVAlPnl8T/3f1e507a2f00ca82e1ebc43dcdc5809c/divergenciadepre__osEN-03.gif)
+![divergenciadepreçosEN-03](https://images.contentful.com/alneenqid6w5/5HVasmtuyHSGDmVAlPnl8T/3f1e507a2f00ca82e1ebc43dcdc5809c/divergenciadepre__osEN-03.gif)
 
 ### Authorizing orders via VTEX DO
 
@@ -113,4 +113,4 @@ To authorize orders manually, follow the steps below:
 6. Click on `Close`.
 7. Click on `Authorize`.
 
-![divergenciadepreçosEN-04](//images.contentful.com/alneenqid6w5/4Hy0li6MdpqLRQiDqkQOyi/055b6a1120bc50793625319db6aa30d4/divergenciadepre__osEN-04.gif)
+![divergenciadepreçosEN-04](https://images.contentful.com/alneenqid6w5/4Hy0li6MdpqLRQiDqkQOyi/055b6a1120bc50793625319db6aa30d4/divergenciadepre__osEN-04.gif)
diff --git a/docs/tutorials/en/price-waterfall.md b/docs/tutorials/en/price-waterfall.md
index 7582c3fe4..8834531c2 100644
--- a/docs/tutorials/en/price-waterfall.md
+++ b/docs/tutorials/en/price-waterfall.md
@@ -21,7 +21,7 @@ With this new feature, we now have a new price entity called *Conditional Prices
 
 Below we have an illustration showing how this price waterfall works:
 
-![priceWaterfall](//images.ctfassets.net/alneenqid6w5/5SSTp5o3VS4eucykWG4wo2/6699e0bd2c023a46cfc322fd89b0b04c/Screen_Shot_2018-08-27_at_14.01.54.png)
+![priceWaterfall](https://images.ctfassets.net/alneenqid6w5/5SSTp5o3VS4eucykWG4wo2/6699e0bd2c023a46cfc322fd89b0b04c/Screen_Shot_2018-08-27_at_14.01.54.png)
 
 When a price for a specific SKU is requested to the *Pricing* module:
 1. A *Fixed Price* is selected according to its criteria like **scheduling** and **minimum quantity**.
diff --git a/docs/tutorials/en/pricing-rules-v2.md b/docs/tutorials/en/pricing-rules-v2.md
index 4a850001b..30b7362d6 100644
--- a/docs/tutorials/en/pricing-rules-v2.md
+++ b/docs/tutorials/en/pricing-rules-v2.md
@@ -20,7 +20,7 @@ The functions described in this article are not yet available for all clients.
 
 A pricing rule is a modifier of the base price, registered on the Price List screen.
 
-![new-dashboard-pricing-en](//images.contentful.com/alneenqid6w5/3OrKTf9XKE0WEAw2IW2Mae/696d2244b31a1858f42b48a88af9d780/new-dashboard-pricing-en.gif)
+![new-dashboard-pricing-en](https://images.contentful.com/alneenqid6w5/3OrKTf9XKE0WEAw2IW2Mae/696d2244b31a1858f42b48a88af9d780/new-dashboard-pricing-en.gif)
 
 ## How it works
 
@@ -34,7 +34,7 @@ In addition, it is important to note that pricing rules are applied to the price
 
 **Only the first** pricing rule that is valid for the SKU conditions (category; brand; and the markup range) will be applied. Even if there are other valid pricing rules, only the first one in the order will be used to calculate the price of the SKU.
 
-![new-dashboard-pricing-rule-reordering-en](//images.contentful.com/alneenqid6w5/4E63yq87du4wWaCkMwwIyi/1d547309fe17e23ee260448d895e4176/new-dashboard-pricing-rule-reordering-en.gif)
+![new-dashboard-pricing-rule-reordering-en](https://images.contentful.com/alneenqid6w5/4E63yq87du4wWaCkMwwIyi/1d547309fe17e23ee260448d895e4176/new-dashboard-pricing-rule-reordering-en.gif)
 
 _We recommend that the order should start with the most specific rules and end with the most comprehensive ones._
 
@@ -42,7 +42,7 @@ _We recommend that the order should start with the most specific rules and end w
 
 The step-by-step procedure for registering is very simple, and is illustrated below:
 
-![new-dashboard-pricing-add-rule-en](//images.contentful.com/alneenqid6w5/4pswVlLUXeuaqUESyakQwo/749e46b278c883e95f4f41b03b4328d1/new-dashboard-pricing-add-rule-en.gif)
+![new-dashboard-pricing-add-rule-en](https://images.contentful.com/alneenqid6w5/4pswVlLUXeuaqUESyakQwo/749e46b278c883e95f4f41b03b4328d1/new-dashboard-pricing-add-rule-en.gif)
 
 1. The **Price rules** will show a list of all the commercial policies. Each of these policies will contain rules. Click on the button **New rule**, above the list, to create a rule.
 2. Select the commercial policy which is to contain this rule.
@@ -53,8 +53,8 @@ The step-by-step procedure for registering is very simple, and is illustrated be
 
 Below you can see examples of the flows of editing and deleting pricing rules. 
 
-![new-dashboard-pricing-edit-rule-en](//images.contentful.com/alneenqid6w5/3N1ZqQ2bSww8wmYAs84yeS/998ade54241f0544b88840d0577898e4/new-dashboard-pricing-edit-rule-en.gif)
+![new-dashboard-pricing-edit-rule-en](https://images.contentful.com/alneenqid6w5/3N1ZqQ2bSww8wmYAs84yeS/998ade54241f0544b88840d0577898e4/new-dashboard-pricing-edit-rule-en.gif)
 _Procedure for modifying a rule_
 
-![new-dashboard-pricing-remove-rule-en](//images.contentful.com/alneenqid6w5/1oA1m0LkgI6uIeaYquoCIA/4e34d4baefd7bc3c31170701d5101bf8/new-dashboard-pricing-remove-rule-en.gif)
+![new-dashboard-pricing-remove-rule-en](https://images.contentful.com/alneenqid6w5/1oA1m0LkgI6uIeaYquoCIA/4e34d4baefd7bc3c31170701d5101bf8/new-dashboard-pricing-remove-rule-en.gif)
 _Procedure for deleting a rule_
diff --git a/docs/tutorials/en/product-list.md b/docs/tutorials/en/product-list.md
index 46f4cf59e..824023bf4 100644
--- a/docs/tutorials/en/product-list.md
+++ b/docs/tutorials/en/product-list.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Products** page allows you to view and manage the complete list of products added to your store, simplifying catalog management on Seller Portal. You can access this page through the **Catalog** menu on VTEX Admin.
 
-![product-list-en](//images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/db6872b42868dbe018b1f85c1a4d9da1/product-list-en.png)
+![product-list-en](https://images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/db6872b42868dbe018b1f85c1a4d9da1/product-list-en.png)
 
 On the **Products** page, you can:
 
diff --git a/docs/tutorials/en/products-and-skus-beta.md b/docs/tutorials/en/products-and-skus-beta.md
index b2d4313a3..c417193a9 100644
--- a/docs/tutorials/en/products-and-skus-beta.md
+++ b/docs/tutorials/en/products-and-skus-beta.md
@@ -21,7 +21,7 @@ subcategory: 6XPsLadoT3moZ7eTduCg3c
 
 The **Products and SKUs** page allows you to view and manage the list of all products in your store, including information about SKUs, last updated, and status. To access it, go to **Catalog > Products and SKUs**.
 
-![products-skus-en](//images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/f02b69940302cf42cf3eefd80ec56445/products-skus-en.png)
+![products-skus-en](https://images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/f02b69940302cf42cf3eefd80ec56445/products-skus-en.png)
 
 <div class="alert alert-info">
   <p>This page is only available to stores operating with the <a href="https://help.vtex.com/en/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">New VTEX Admin</a>. To access this page and be part of the new experience, join the New VTEX Admin <a href="https://content.vtex.com/participe-do-programa-beta-en/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">Beta program</a>.</p>
@@ -63,7 +63,7 @@ To find a specific product, you can type one of the following in the search bar:
 
 Then, click on the criteria you want to use for the search, as illustrated in the following image:
 
-![products-skus-search-en](//images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/f0f028bb188ed98868f4fc9738e96511/search-en.gif)
+![products-skus-search-en](https://images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/f0f028bb188ed98868f4fc9738e96511/search-en.gif)
 
 The list of products displayed will then be refreshed according to your search. 
 
@@ -103,7 +103,7 @@ To view the status of a product's SKUs, read the section [Viewing the SKU List](
 
 When you click the arrow <i class="fas fa-chevron-right"></i> in the product row in the list, the platform displays a list with all the SKUs of that product: 
 
-![sku-actions-en](//images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/06822a59851d6f677c47c4cd3d1d4230/sku-actions-en.gif)
+![sku-actions-en](https://images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/06822a59851d6f677c47c4cd3d1d4230/sku-actions-en.gif)
 
 In the SKU list, you will find the following information:
 
@@ -148,7 +148,7 @@ When clicking the menu on a product line and choosing **View indexed info**, you
 
 This modal tab displays the SKU list associated with the product and its corresponding indexed information.
 
-![catalog-price-inventory-en](//images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/b3968e801767f2d06423bc507f2ea6b5/price-inventory-en.PNG)
+![catalog-price-inventory-en](https://images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/b3968e801767f2d06423bc507f2ea6b5/price-inventory-en.PNG)
 
 By clicking the arrow `>` in each SKU row, you can view a table with the following information:
 
@@ -163,7 +163,7 @@ By clicking the arrow `>` in each SKU row, you can view a table with the followi
 
 This modal tab displays the log, in other words, the detailed technical indexing record for the product and related SKUs.
 
-![indexed-log-en](//images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/4c2095af6dec446e27db570e067b4d5f/indexed-log-en.PNG)
+![indexed-log-en](https://images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/4c2095af6dec446e27db570e067b4d5f/indexed-log-en.PNG)
 
 ## Learn more
 
diff --git a/docs/tutorials/en/promotion-alerts-beta.md b/docs/tutorials/en/promotion-alerts-beta.md
index 527498de4..08b28b161 100644
--- a/docs/tutorials/en/promotion-alerts-beta.md
+++ b/docs/tutorials/en/promotion-alerts-beta.md
@@ -29,7 +29,7 @@ Suppose you only configure the email alert action, further orders with the unwan
 
 To access the page in the VTEX Admin, go to *Promotions > Promotion Alert*. You will see the following interface:
 
-![simuladordepromocoes gerenciar](//images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
+![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
 
 The table below shows the column descriptions for the promotion list:
 
diff --git a/docs/tutorials/en/promotion-list-beta.md b/docs/tutorials/en/promotion-list-beta.md
index 2ce5b7f10..c9f3421d2 100644
--- a/docs/tutorials/en/promotion-list-beta.md
+++ b/docs/tutorials/en/promotion-list-beta.md
@@ -30,7 +30,7 @@ The page displays the list of your store's promotions and their basic informatio
 | `To` | Promotion end date. |
 | `Status` | Promotion status, which can be: <p> __Active:__ when a promotion is active.</p> <p>__Scheduled:__ when the promotion was scheduled.</p> <p>__Paused:__ when the promotion is paused. <p>__Completed:__ when the promotion ended.</p> |
 
-![listadepromocoes en](//images.ctfassets.net/alneenqid6w5/3QkCDSGnYVvzz6ygn3ZUm8/c790e13db5f9ce7b8e9fa276478813d1/listadepromocoes_en.gif)
+![listadepromocoes en](https://images.ctfassets.net/alneenqid6w5/3QkCDSGnYVvzz6ygn3ZUm8/c790e13db5f9ce7b8e9fa276478813d1/listadepromocoes_en.gif)
 
 You can sort the promotions by name, date, or status. To do this, click on the title of the column with the information you want to use as sorting criteria.
 
@@ -82,7 +82,7 @@ The file contains the following information about each promotion:
 
 ## Promotion usage
 
-![usodaspromoções en](//images.ctfassets.net/alneenqid6w5/5cvRZbj2TqwHuQcx6jjqm4/d94a8916fcd88257d83f8c8edd0a0dbf/usodaspromo____es_en.JPG)
+![usodaspromoções en](https://images.ctfassets.net/alneenqid6w5/5cvRZbj2TqwHuQcx6jjqm4/d94a8916fcd88257d83f8c8edd0a0dbf/usodaspromo____es_en.JPG)
 
 To view the total of your active promotions and the remaining quota for new promotions, click `Promotion usage`. 
 
@@ -90,7 +90,7 @@ By default, the maximum number of active promotions is 100. If you need to incre
 
 ## Filter promotions
 
-![filtrodepromocoes en](//images.ctfassets.net/alneenqid6w5/5ejpdUDVPbixeLp6nmDB1q/d637dba80b4cbda6194cae7cbf630785/filtrodepromocoes_en.gif)
+![filtrodepromocoes en](https://images.ctfassets.net/alneenqid6w5/5ejpdUDVPbixeLp6nmDB1q/d637dba80b4cbda6194cae7cbf630785/filtrodepromocoes_en.gif)
 
 The promotion list can be filtered according to your needs by using the following filters:
 
diff --git a/docs/tutorials/en/promotion-summary.md b/docs/tutorials/en/promotion-summary.md
index 99c8f8ae7..8b328098b 100644
--- a/docs/tutorials/en/promotion-summary.md
+++ b/docs/tutorials/en/promotion-summary.md
@@ -64,19 +64,19 @@ High-risk alerts indicate that critical configurations or registration errors mu
 
 Example:
 
-![alert-alto-risco-EN](//images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/6024c1bf2aee399450f05cbf2648798c/image.png)
+![alert-alto-risco-EN](https://images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/6024c1bf2aee399450f05cbf2648798c/image.png)
 
 ### Medium risk
 Medium-risk alerts indicate that there are configurations that may cause undesired effects on the promotion.
 
 Example:
 
-![alert-medio-risco-EN](//images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/38a07c0774736c5005638e78987d4a23/image.png)
+![alert-medio-risco-EN](https://images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/38a07c0774736c5005638e78987d4a23/image.png)
 
 ### Low risk
 Low-risk alerts present relevant information about the promotion configuration, which can contribute to better performance.
 
 Example:
 
-![alert-baixo-risco-EN](//images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/65f04416a92b8c5bd606064165803313/image.png)
+![alert-baixo-risco-EN](https://images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/65f04416a92b8c5bd606064165803313/image.png)
 
diff --git a/docs/tutorials/en/promotions-beta.md b/docs/tutorials/en/promotions-beta.md
index 3847c9501..e6958a9e4 100644
--- a/docs/tutorials/en/promotions-beta.md
+++ b/docs/tutorials/en/promotions-beta.md
@@ -32,20 +32,20 @@ The home page displays the promotions list in a grid that allows you to easily v
 - Duplicate or archive promotions using the <i class="fas fa-ellipsis-v"></i>  button;
 - Manage promotion conditions by clicking anywhere in the grid row (see [New promotion](#new-promotion) for more details about promotion conditions).
 
-![promobeta1 acoes lista promocoes EN](//images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b3f2216333e8dd4cbd084b6408524541/promobeta1_acoes_lista_promocoes_EN.gif)
+![promobeta1 acoes lista promocoes EN](https://images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b3f2216333e8dd4cbd084b6408524541/promobeta1_acoes_lista_promocoes_EN.gif)
 
 You can filter and sort your promotion list according to your needs. The VTEX platform allows you to filter your promotions by *Effects*, *Status*, *Starting date*, *Ending date*, or *Trade policy*.
 
-![promobeta2 filtros lista promocoes EN](//images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/e1e802f323d8eba2e296a27ae0f27135/promobeta2_filtros_lista_promocoes_EN.gif)
+![promobeta2 filtros lista promocoes EN](https://images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/e1e802f323d8eba2e296a27ae0f27135/promobeta2_filtros_lista_promocoes_EN.gif)
 
 You can also sort your list in ascending or descending order based on the basic information of the promotion by clicking on the filter title.
 
-![promobeta3 ordenacao lista promocoes EN](//images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5f56351941377f0829b3582324ed347f/promobeta3_ordenacao_lista_promocoes_EN.gif)
+![promobeta3 ordenacao lista promocoes EN](https://images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5f56351941377f0829b3582324ed347f/promobeta3_ordenacao_lista_promocoes_EN.gif)
 
 ## New promotion
 On the Promotions page, click on the __NEW PROMOTION__ button to access the promotion creation page, where you will fill in a series of fields to configure the desired conditions for your promotion. 
 
-![promobeta4 botao novapromocao EN](//images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/29b06b468de480f45adef9896a7eabe4/promobeta4_botao_novapromocao_EN.png)
+![promobeta4 botao novapromocao EN](https://images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/29b06b468de480f45adef9896a7eabe4/promobeta4_botao_novapromocao_EN.png)
 
 The new promotion conditions and fields are divided into the following groups:
 
diff --git a/docs/tutorials/en/promotions-simulator-beta.md b/docs/tutorials/en/promotions-simulator-beta.md
index 498258894..e490c89b0 100644
--- a/docs/tutorials/en/promotions-simulator-beta.md
+++ b/docs/tutorials/en/promotions-simulator-beta.md
@@ -35,7 +35,7 @@ The **Promotion Simulator** is available for all VTEX stores through [Cartman](h
 
    In the new window, you will find a list of the products in your cart and all the promotions that have been applied and are applicable to each item.
 
-![Simulator-promo-en-gif-1](//images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/c05b0c30d34a029e4bff69dff70de0d5/simulador-promo-en-230706.gif)
+![Simulator-promo-en-gif-1](https://images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/c05b0c30d34a029e4bff69dff70de0d5/simulador-promo-en-230706.gif)
 
 The **Promotion Simulator** interface displays the following information:
 
@@ -79,7 +79,7 @@ To edit a promotion, follow the steps below:
 
 The **Promotion Simulator** allows you to test the application of another promotion or simulate the effects of deactivating applied promotions. To do this, click the `Select Promotions` button at the top right of the page, as shown in the image below.
 
-![ui-Simulator-promo-en-gif-2](//images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/31e593dbdb4fed07df101576ecc63f20/ui-simulador-promo-en-230706.gif)
+![ui-Simulator-promo-en-gif-2](https://images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/31e593dbdb4fed07df101576ecc63f20/ui-simulador-promo-en-230706.gif)
 
 To run a simulation, follow the instructions below:
 
diff --git a/docs/tutorials/en/promotions-simulator.md b/docs/tutorials/en/promotions-simulator.md
index 3480b6de6..b54965c02 100644
--- a/docs/tutorials/en/promotions-simulator.md
+++ b/docs/tutorials/en/promotions-simulator.md
@@ -27,9 +27,9 @@ To use this feature, you need to [configure Cartman](https://help.vtex.com/en/tu
 2. In the cart, click the following button <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> to open Cartman.
 3. Select `View promotion details`.
 4. This window displays the promotions applied to the cart. For more details, click <i class="fas fa-search"></i>`View details`.
-![cartman-analisador-promoção-EN](//images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/5e79f607478f8e4174edde1e1a1d6028/Screen_Shot_2022-03-07_at_11.13.45.png)
+![cartman-analisador-promoção-EN](https://images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/5e79f607478f8e4174edde1e1a1d6028/Screen_Shot_2022-03-07_at_11.13.45.png)
 5. The **Promotions Simulator** window will be displayed.
-![analisador-promoção-EN](//images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/2c0cc35c6a27d25365dc925faf204af4/image.png)
+![analisador-promoção-EN](https://images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/2c0cc35c6a27d25365dc925faf204af4/image.png)
 
 In this window, you can view the following information:
 
diff --git a/docs/tutorials/en/protection-against-transaction-attacks.md b/docs/tutorials/en/protection-against-transaction-attacks.md
index 6c29c465b..c2a1b0b6a 100644
--- a/docs/tutorials/en/protection-against-transaction-attacks.md
+++ b/docs/tutorials/en/protection-against-transaction-attacks.md
@@ -36,9 +36,9 @@ To enable the protection, please follow the instructions below:
 4. In the upper right corner, click on the Settings icon.
 5. Under __Attack protection__, click on the button to enable it (green color indicates "enabled").
 
-![proteção-botao-configurações](//images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
+![proteção-botao-configurações](https://images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
 
-![protection-option-enable1](//images.ctfassets.net/alneenqid6w5/QSVTQfbO9BDFUB33KXgj7/9ee748c43264183f31f071514862a068/protection-option-enable1.png)
+![protection-option-enable1](https://images.ctfassets.net/alneenqid6w5/QSVTQfbO9BDFUB33KXgj7/9ee748c43264183f31f071514862a068/protection-option-enable1.png)
 
 ### How to disable protection against transaction attacks?
 
@@ -69,13 +69,13 @@ To access this information, please follow the instructions below.
 6. To select __Detected threats__ or __Neutralized threats__, click on one of the arrows on the right.
 7. Check the details of the events in the popup window displayed.
 
-![protection-option-historic1](//images.ctfassets.net/alneenqid6w5/6oUr155OKf1tKDw3O3i2ZD/a0a2156aa0b0b791992c67cc21f71279/protection-option-historic1.png)
+![protection-option-historic1](https://images.ctfassets.net/alneenqid6w5/6oUr155OKf1tKDw3O3i2ZD/a0a2156aa0b0b791992c67cc21f71279/protection-option-historic1.png)
 
-![protection-screen-historic1](//images.ctfassets.net/alneenqid6w5/6mjiUMYjTQ2nmU7NZKGnyk/c92c6fe16f49fab604337c8749c10657/protection-screen-historic1.png)
+![protection-screen-historic1](https://images.ctfassets.net/alneenqid6w5/6mjiUMYjTQ2nmU7NZKGnyk/c92c6fe16f49fab604337c8749c10657/protection-screen-historic1.png)
 
-![screen-threat-potential1](//images.ctfassets.net/alneenqid6w5/4ZyYbA7qHIc5PvpxxiHlKk/22a6858af2e7a5acac9ef3d5bb6ff106/screen-threat-potential1.png)
+![screen-threat-potential1](https://images.ctfassets.net/alneenqid6w5/4ZyYbA7qHIc5PvpxxiHlKk/22a6858af2e7a5acac9ef3d5bb6ff106/screen-threat-potential1.png)
 
-![screen-threat-neutralized1](//images.ctfassets.net/alneenqid6w5/EhBQQcXklgecc5X2dwHR7/d67780094c2c7cfeaacd2935c2516854/screen-threat-neutralized1.png)
+![screen-threat-neutralized1](https://images.ctfassets.net/alneenqid6w5/EhBQQcXklgecc5X2dwHR7/d67780094c2c7cfeaacd2935c2516854/screen-threat-neutralized1.png)
 
 ### Related Articles
 - [What is an anti-fraud solution?](https://help.vtex.com/en/tutorial/o-que-e-antifraude)
diff --git a/docs/tutorials/en/received-skus-beta.md b/docs/tutorials/en/received-skus-beta.md
index c5203bb96..f69ccd278 100644
--- a/docs/tutorials/en/received-skus-beta.md
+++ b/docs/tutorials/en/received-skus-beta.md
@@ -33,7 +33,7 @@ The Received SKUs page is divided in tabs that correspond to the different offer
 
 Each tab displays a SKU list, offer SKU specifications, and the percentage of offers that have that status. Additionally, the tab has filter options that you can apply to the offers.  
 
-![received-skus-tabs-en](//images.ctfassets.net/alneenqid6w5/4jNrRvJsZgja1LuSz204P1/09fa16e993ba58dffa27b8809bb22c8f/received-skus-tabs-en.png)
+![received-skus-tabs-en](https://images.ctfassets.net/alneenqid6w5/4jNrRvJsZgja1LuSz204P1/09fa16e993ba58dffa27b8809bb22c8f/received-skus-tabs-en.png)
 
 ### Pending
 
@@ -50,7 +50,7 @@ Each row in the list represents a product and contains the following information
 
 To check all the specifications of a product, click the name of the product. This will open a window that contains all the product information.  
 
-![received-skus-tabs-en](//images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/ff94df985c2cc930548645ac0fbd5e98/received-skus-analyse-product-en.png)
+![received-skus-tabs-en](https://images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/ff94df985c2cc930548645ac0fbd5e98/received-skus-analyse-product-en.png)
 
 ### Issues  
 
@@ -62,7 +62,7 @@ The __Issues__ tab contains all the offers that haven't been approved because th
 
 To identify the issue of an offer, simply click the name of the product. This will open a window with the product information, an error message, and the offer reviewer.  
 
-![received-skus-problems-tab](//images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/58d57ab4904c6794299855c91bfa6ef1/received-skus-problems-tab.png)
+![received-skus-problems-tab](https://images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/58d57ab4904c6794299855c91bfa6ef1/received-skus-problems-tab.png)
 
 ### Approved  
 
@@ -121,7 +121,7 @@ By default, the items that were submitted most recently are displayed at the top
 
 In this case, the items will be sorted in ascending or descending order when you click the __Price__ or __Inventory__ column headers.  
 
-![received-skus-ord-en](//images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/585afe9679294087fe9351cea7f0799a/received-skus-ord-en.png)
+![received-skus-ord-en](https://images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/585afe9679294087fe9351cea7f0799a/received-skus-ord-en.png)
 
 ## Cataloging items  
 
@@ -152,7 +152,7 @@ The available cataloging actions are:
 This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
 </div>
 
-![received-skus-create-new-product-en](//images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/2d18fb18e7711cb4cd341795ac0820b4/received-skus-create-new-product-en.png)
+![received-skus-create-new-product-en](https://images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/2d18fb18e7711cb4cd341795ac0820b4/received-skus-create-new-product-en.png)
 
 - __Link to an existing product:__ Creates a relationship between the seller product and a product in the marketplace catalog. To apply this action, follow the steps below:  
 
@@ -171,7 +171,7 @@ Creating a new link groups the new sizes with the existing ones. After this, the
 This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
 </div>  
 
-![received-skus-bind-to-product-en](//images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/fc02d18fe2771b0603f861f8516ab7ae/received-skus-bind-to-product-en.png)
+![received-skus-bind-to-product-en](https://images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/fc02d18fe2771b0603f861f8516ab7ae/received-skus-bind-to-product-en.png)
 
 - __Link to an existing SKU:__ Creates a relationship between the new seller SKU and a SKU in the marketplace catalog. To apply this action, follow the steps below:  
 
@@ -190,7 +190,7 @@ Now, let's say the marketplace received the same 128 GB SKU from Seller 2. To av
 This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
 </div>
 
-![received-skus-bind-to-sku-en](//images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/8bc6c9b98e03afe02252bd69342005d1/received-skus-bind-to-sku-en.png)
+![received-skus-bind-to-sku-en](https://images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/8bc6c9b98e03afe02252bd69342005d1/received-skus-bind-to-sku-en.png)
 
 - __Block:__ Blocks the selected offers. This will prevent them from being automatically processed again. To apply this action, follow the steps below:  
 
@@ -205,7 +205,7 @@ When the marketplace blocks a SKU, it won't be included with other submitted off
 This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>. Blocked offers can be viewed in the <b>Blocked</b> tab.
 </div>
 
-![received-skus-reject-and-block-en](//images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/247d5dcfb554755d091b1367d84db2d5/received-skus-reject-and-block-en.png)
+![received-skus-reject-and-block-en](https://images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/247d5dcfb554755d091b1367d84db2d5/received-skus-reject-and-block-en.png)
 
 - __Reject for correction:__ Rejects the offer and sends an information correction request to the seller. To apply this action, follow the steps below:  
 
@@ -218,7 +218,7 @@ This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>. B
 	<p>This action can be applied in the offer tab <b>Pending</b>. The offers that need correction will show in the <b>Issues</b> tab.</p>
 </div>  
 
-![received-skus-reject-for-correction-en](//images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/7d456cf95d5a4ed7011accdfe0550fba/received-skus-reject-for-correction-en.png)
+![received-skus-reject-for-correction-en](https://images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/7d456cf95d5a4ed7011accdfe0550fba/received-skus-reject-for-correction-en.png)
 
 - __Automatic approval:__ You can also set up automatic approval for SKUs from a specific seller regardless of their Matcher score. This action can only be applied through a REST API. To learn more, see [Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions).  
 
diff --git a/docs/tutorials/en/registered-ticket-flow.md b/docs/tutorials/en/registered-ticket-flow.md
index b94950b9b..116ac4201 100644
--- a/docs/tutorials/en/registered-ticket-flow.md
+++ b/docs/tutorials/en/registered-ticket-flow.md
@@ -23,7 +23,7 @@ Here's how the basic flow of a registered ticket payment works. The flow is divi
  
 ## Ticket Issue
 
-![processo-boleto-registrado-en ex 2](//images.ctfassets.net/alneenqid6w5/3QIX0MyLCgqcmcsGgEAwsU/e7530c4c911dd93a995425db4a9e5fff/paint_bank_en_2.png)
+![processo-boleto-registrado-en ex 2](https://images.ctfassets.net/alneenqid6w5/3QIX0MyLCgqcmcsGgEAwsU/e7530c4c911dd93a995425db4a9e5fff/paint_bank_en_2.png)
 
 1. Your __e-commerce__ informs the __Gateway__ that an order will be paid via registered ticket.
 2. The gateway contacts the __Bank__ to register the ticket.
@@ -35,7 +35,7 @@ At this time, the ticket has not yet been paid by the customer.
 
 ## Ticket Payment and Bank Reconciliation
 
-![processo-boleto-registrado-en ex 1](//images.ctfassets.net/alneenqid6w5/1c6VvblROiioeMmacWkuii/37a83bad6931c6ae6a8fa89a5b773127/paint_bank_en.png)
+![processo-boleto-registrado-en ex 1](https://images.ctfassets.net/alneenqid6w5/1c6VvblROiioeMmacWkuii/37a83bad6931c6ae6a8fa89a5b773127/paint_bank_en.png)
 
 1. the __Client__ pays the ticket directly to the __Bank__.
 2. The bank sends the [bank reconciliation](/en/tutorial/bank-reconciliations) files to the __Gateway__ with information on the tickets payment status.
diff --git a/docs/tutorials/en/registering-brands.md b/docs/tutorials/en/registering-brands.md
index f3e75fe65..b6b694dad 100644
--- a/docs/tutorials/en/registering-brands.md
+++ b/docs/tutorials/en/registering-brands.md
@@ -23,4 +23,4 @@ To register a brand, follow these steps:
 4. Fill in the [Brand registration fields](https://help.vtex.com/en/tutorial/brand-registration-fields--37Ky7lTbEkiWIAYA80EMyI).
 5. Click on `Save`.
 
-![ENcadastrarmarcas3.PNG?h=250](//images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
+![ENcadastrarmarcas3.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
diff --git a/docs/tutorials/en/registering-gateway-affiliations.md b/docs/tutorials/en/registering-gateway-affiliations.md
index b2dedecb1..89ff2b913 100644
--- a/docs/tutorials/en/registering-gateway-affiliations.md
+++ b/docs/tutorials/en/registering-gateway-affiliations.md
@@ -23,7 +23,7 @@ The provider management screen allows you to:
 - [View added providers](#viewing-added-providers)
 - [Edit provider settings](#editing-provider-settings)
 
-![interface_provedor_EN_1](//images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/7a033eb73b124608c07471301501da64/artigo_interface_provedor_EN_1.jpg)
+![interface_provedor_EN_1](https://images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/7a033eb73b124608c07471301501da64/artigo_interface_provedor_EN_1.jpg)
 
 ## Adding providers
 
@@ -48,7 +48,7 @@ To configure the payment methods that will be processed by your chosen payment p
 
 To set special conditions for payment methods, read [Configuring payment special  conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
 
-![interface_provedor_EN_2](//images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/06ebd4ed620be2fd6a2ea7f3b61e25e7/artigo_interface_provedor_EN_2.JPG)
+![interface_provedor_EN_2](https://images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/06ebd4ed620be2fd6a2ea7f3b61e25e7/artigo_interface_provedor_EN_2.JPG)
 
 ## Viewing added providers
 
@@ -58,7 +58,7 @@ The main provider management screen, available in the VTEX Admin under __Store S
 
 To search for providers by name, go to the provider management page and enter the name of the provider you want to find.
 
-![interface_provedor_EN_3](//images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/1c93dc9bbf26acf87e54224c5471407f/artigo_interface_provedor_EN_3.JPG)
+![interface_provedor_EN_3](https://images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/1c93dc9bbf26acf87e54224c5471407f/artigo_interface_provedor_EN_3.JPG)
 
 ### Filtering providers
 
@@ -66,15 +66,15 @@ To select the providers using filters, go to the provider management page and ap
 
 - __Name__: Select the payment provider using the name by checking the box or using the menu search bar.
 
-![interface_provedor_EN_4](//images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/c5e5aa3880b070e45a891d477906b78d/artigo_interface_provedor_EN_4.JPG)
+![interface_provedor_EN_4](https://images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/c5e5aa3880b070e45a891d477906b78d/artigo_interface_provedor_EN_4.JPG)
 
 - __Type__: Select to display payment providers, antifraud providers, or both.
 
-![interface_provedor_EN_5](//images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/2dde50a266e104a6f1652e7d7294d560/artigo_interface_provedor_EN_5.JPG)
+![interface_provedor_EN_5](https://images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/2dde50a266e104a6f1652e7d7294d560/artigo_interface_provedor_EN_5.JPG)
 
 - __Environment__: Select the providers by type of operating environment (production or test).
 
-![interface_provedor_EN_6](//images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/bb0b07f72dac4a7b01f5e94aa388899c/artigo_interface_provedor_EN_6.JPG)
+![interface_provedor_EN_6](https://images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/bb0b07f72dac4a7b01f5e94aa388899c/artigo_interface_provedor_EN_6.JPG)
 
 <div class = "alert alert-danger">
 To clear the applied filters and see all the providers in the store again, click the <code>Clear All</code> button.</div>
@@ -88,7 +88,7 @@ To edit the settings of existing payment or antifraud providers in the store, fo
 3. On the provider configuration screen, click `Edit`.
 4. Make the necessary changes and click `Save`.
 
-![interface_provedor_EN_7](//images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/6dffc24a68b01dd43309f119907ed1d0/artigo_interface_provedor_EN_7.JPG)
+![interface_provedor_EN_7](https://images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/6dffc24a68b01dd43309f119907ed1d0/artigo_interface_provedor_EN_7.JPG)
 
 <div class = "alert alert-danger">
 Before changing the provider's settings, such as authorization details, processing mode, or refund type, ensure the new information entered will not affect your store's performance.</div>
diff --git a/docs/tutorials/en/registering-sku-price.md b/docs/tutorials/en/registering-sku-price.md
index 06a0a6849..b99dd9a85 100644
--- a/docs/tutorials/en/registering-sku-price.md
+++ b/docs/tutorials/en/registering-sku-price.md
@@ -21,7 +21,7 @@ The manual process is more appropriate when the storeowner wants to alter the pr
 
 ## Manual registration or change
 
-![](//images.contentful.com/alneenqid6w5/62eMKlDZ04As4ey46yiOeK/2d689eb25d9945a532d4447ba770649f/Tabela_de_Valores.gif)
+![](https://images.contentful.com/alneenqid6w5/62eMKlDZ04As4ey46yiOeK/2d689eb25d9945a532d4447ba770649f/Tabela_de_Valores.gif)
 
 ### Registration for a new value
 
@@ -58,7 +58,7 @@ _If you click on the “Novo Valor de Tabela” button after filtering an SKU, t
 
 ## Registration or change by importing Excel spreadsheets
 
-![](//images.contentful.com/alneenqid6w5/5Pbm0WFO12QmEwW88OM2iU/453748487c805f0ef7bd20887e454670/Altera__o_de_pre_o_Importa__o.gif)
+![](https://images.contentful.com/alneenqid6w5/5Pbm0WFO12QmEwW88OM2iU/453748487c805f0ef7bd20887e454670/Altera__o_de_pre_o_Importa__o.gif)
 
 ### To register new prices
 
@@ -86,7 +86,7 @@ _If you click on the “Novo Valor de Tabela” button after filtering an SKU, t
 
 ### Excel spreadsheet fields for Import
 
-![](//images.contentful.com/alneenqid6w5/1wTiiJMsUcUGMoI6GGWsOw/b31f627d1a8d642532d475fd72e23ff6/Como_cadastrar_preco_SKU_2.jpg)
+![](https://images.contentful.com/alneenqid6w5/1wTiiJMsUcUGMoI6GGWsOw/b31f627d1a8d642532d475fd72e23ff6/Como_cadastrar_preco_SKU_2.jpg)
 
 - **StockKeepingUnitId: **ID of the SKU to be registered or whose price is to be changed;
 - **Source**: value of utm\_source;
diff --git a/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
index 9657b8aec..6226e7d03 100644
--- a/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -20,7 +20,7 @@ When you create a [regular promotion](https://help.vtex.com/en/tutorial/regular-
 
 By selecting this type of discount, you need to create a formula defining how the applied discount will be calculated. In this article, we’ll explain how to build a formula which meets your promotion's objectives.
 
-![discount-type-formula](//images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/c7e753bddc57ad9ec18b30f05f654688/desc.PNG)
+![discount-type-formula](https://images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/c7e753bddc57ad9ec18b30f05f654688/desc.PNG)
 
 The formula used to calculate the nominal discount generally follows the same logic as the [Microsoft Excel formulas](https://support.microsoft.com/pt-br/office/f%C3%B3rmulas-e-fun%C3%A7%C3%B5es-294d9486-b332-48ed-b489-abe7d0f9eda9), which means you can use [variables](#variables) (`total`, `freight` and `quantity`), make [operations](#operations) (sum, subtraction, multiplication and division) and apply (`min` and `max` [functions](#functions).
 
@@ -79,19 +79,19 @@ The promotion will apply the lowest discount in each case, comparing the 20% cal
 
 A customer added a $ 45 item to the cart. By calculating 20% of the total price, the result is 9, as per `total * 0.2 = 9`. Since 9 is below the discount limit value, the applied discount will be $ 9.
 
-![scenario1-en](//images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/7cedfaa3ffa9b54192807f47a4b1fe18/scenario1-en.png)
+![scenario1-en](https://images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/7cedfaa3ffa9b54192807f47a4b1fe18/scenario1-en.png)
 
 #### Scenario 2
 
 Another customer added a $ 2600 item to the cart. By calculating 20% of this amount, the result is 520, as per `total * 0.2 = 520`. Since this value is above the limit ($ 10), the discount will be $ 10.
 
-![scenario2-en](//images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/7bd025f1787a20a9fdc1332c54e73568/scenario2-en.png)
+![scenario2-en](https://images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/7bd025f1787a20a9fdc1332c54e73568/scenario2-en.png)
 
 #### Scenario 3
 
 A third customer added two items to the cart: One costs $ 100 and the other $ 2600. Their sum is $ 2700, as per `total = 2700`. By calculating 20% of the total amount, the result is 540, according to `total * 0.2 = 540`. Since this value is above the limit ($ 10), the applied discount will be $ 10.
 
-![scenario3-en](//images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/11a3e761ff2194ad9e63ee9a575cd62c/scenario3-en.png)
+![scenario3-en](https://images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/11a3e761ff2194ad9e63ee9a575cd62c/scenario3-en.png)
 
 The total discount of $ 10 is proportionally distributed among the items, based on each item's price and quantity. The platform makes this distribution automatically, as explained below.
 
diff --git a/docs/tutorials/en/regular-promotion-with-reward-value.md b/docs/tutorials/en/regular-promotion-with-reward-value.md
index cca5d3560..a7dff9bab 100644
--- a/docs/tutorials/en/regular-promotion-with-reward-value.md
+++ b/docs/tutorials/en/regular-promotion-with-reward-value.md
@@ -38,7 +38,7 @@ The **nominal reward value** adds a fixed credit amount to the user's account in
 
 In the following example, the customers will earn R$10,00 in store credit when the order status changes to **Invoiced**.
 
-![vf-nominal-en](//images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/fc3a24297d99657c141f3b8d295f6f69/vf-nominal-en.png)
+![vf-nominal-en](https://images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/fc3a24297d99657c141f3b8d295f6f69/vf-nominal-en.png)
 
 ### Percentage reward value
 
@@ -49,7 +49,7 @@ The **percentage reward value** adds a percentage credit amount based on the pri
 
 In the following example, customers will earn 20% of the purchase value when the order status changes to **Payment Approved**.
 
-![vf-percentual-en](//images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4b8f2e869e868607f53e9d8dae42b175/vf-percentual-en.png)
+![vf-percentual-en](https://images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4b8f2e869e868607f53e9d8dae42b175/vf-percentual-en.png)
 
 ## How to set up restrictions
 
@@ -93,11 +93,11 @@ The name of the promotion applied to the order appears in the **Sales and market
 
 In the **Order flow** section, you can check the reward value applied:
 
-![fluxo-oms-en](//images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/cd08683f3137aa01fd0e88138865a36e/fluxo-oms-en.png)
+![fluxo-oms-en](https://images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/cd08683f3137aa01fd0e88138865a36e/fluxo-oms-en.png)
 
 If you use the new [Order details (Beta)](https://help.vtex.com/en/tutorial/order-details-page-beta--2Y75n54Cc9VizrlG1N6ZNl) interface, go to `See interactions` to check the applied value:
 
-![interacoes-neworders-en](//images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/111404a4067208154e3eb05fe28df3aa/interacoes-neworders-en.png)
+![interacoes-neworders-en](https://images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/111404a4067208154e3eb05fe28df3aa/interacoes-neworders-en.png)
 
 Consider that the promotion applied to the order illustrated offers a **percentage reward value** of **50%**. Therefore, the client earned a credit of `R$ 54.28` for  future purchases, which is equivalent to **50%** of `R$ 108.55`, the total value of the order.
 
@@ -105,13 +105,13 @@ Consider that the promotion applied to the order illustrated offers a **percenta
 
 The reward value available for use is displayed to your store customers at the **Payment** stage during checkout, as shown below.
 
-![checkout-pt (1)](//images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
+![checkout-pt (1)](https://images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
 
 The applied value can be used to calculate the payment. To do so, the customer must click on `use credit` and then enter the value they want to use.
 
 Note that the value will be discounted from the other method of payment selected. In the following example, the _boleto_ shows the amount of `R$ 113.50`, which corresponds to `R$ 167.80` minus the reward value used (`R$ 54.30`).
 
-![checkout-2-pt (1)](//images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
+![checkout-2-pt (1)](https://images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
 
 ## Learn more
 
diff --git a/docs/tutorials/en/regular-promotion.md b/docs/tutorials/en/regular-promotion.md
index 657e11de0..0b97366ba 100644
--- a/docs/tutorials/en/regular-promotion.md
+++ b/docs/tutorials/en/regular-promotion.md
@@ -89,7 +89,7 @@ For the promotion to be valid for all sales policies, leave the checkboxes empty
 
 In this section, you need to choose whether this promotion will apply to all products in your store or only to specific products, as illustrated below.
 
-![promocoes-restricao-en](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
+![promocoes-restricao-en](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/adc5cdd25eb79636530e31e668b765e3/image.png)
 
 If you want the promotion to apply to your entire catalog, select the **Apply to all products** option.
 
@@ -99,7 +99,7 @@ You can add or remove **Categories**, **Brands**, **Collections**, **Products**
 
 See an example below. In this case, the promotion includes all products from the category **Home Appliances** whose brand is **Brastemp**, except the product **Refrigerator 100**.
 
-![exemplo-en](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
+![exemplo-en](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/b3d7c4dff6f1039056bbd2a246f05b19/image.png)
 
 In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
 
diff --git a/docs/tutorials/en/releases-module-beta.md b/docs/tutorials/en/releases-module-beta.md
index a432c5ea9..7a462055e 100644
--- a/docs/tutorials/en/releases-module-beta.md
+++ b/docs/tutorials/en/releases-module-beta.md
@@ -72,7 +72,7 @@ In this stage, the fields <b>Day to publish</b> and <b>Time</b> are not required
 
 8. Click `Create`.
 
-![print_cms_beta_en](//images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/9c938423b576e80d181f0cc8d32a6b46/print_cms_beta_en.png)
+![print_cms_beta_en](https://images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/9c938423b576e80d181f0cc8d32a6b46/print_cms_beta_en.png)
 
 ### How to create a release using the Releases module
 
@@ -92,7 +92,7 @@ In this stage, the fields <b>Day to publish</b> and <i>Time</i> are not required
 
 All the releases are listed in the VTEX Admin, in **Store Settings > Releases**. The page displays two tabs, `SCHEDULED` and `UNSCHEDULED`, depending on whether the release has been created with a set publish date. 
 
-![print_releases_en](//images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/4895efa9b36315602d5b877de0a8a60c/print_releases_en.png)
+![print_releases_en](https://images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/4895efa9b36315602d5b877de0a8a60c/print_releases_en.png)
 
 On the `SCHEDULED` tab, each column is described as follows:
 
diff --git a/docs/tutorials/en/releasing-the-store-for-production.md b/docs/tutorials/en/releasing-the-store-for-production.md
index 1b68e4d29..8ffc8de42 100644
--- a/docs/tutorials/en/releasing-the-store-for-production.md
+++ b/docs/tutorials/en/releasing-the-store-for-production.md
@@ -30,7 +30,7 @@ Then, you have to place your store on a production status on its relevant Licens
 4. On the option **Is it n production, **click on the **No button**, to change it to **Yes**;
 5. Click on the **Save** button.
 
-![accounts.en](//images.ctfassets.net/alneenqid6w5/5VattCUDKiUuh4fFbZUUZH/2cf97d683b28608f863ffcb803348a2e/accounts.en.png)
+![accounts.en](https://images.ctfassets.net/alneenqid6w5/5VattCUDKiUuh4fFbZUUZH/2cf97d683b28608f863ffcb803348a2e/accounts.en.png)
 
 After this is set up, the access to the final URL of the store will be redirected to your e-commerce!
 
diff --git a/docs/tutorials/en/relevance-rules.md b/docs/tutorials/en/relevance-rules.md
index a64bec3be..ec9a4a041 100644
--- a/docs/tutorials/en/relevance-rules.md
+++ b/docs/tutorials/en/relevance-rules.md
@@ -24,7 +24,7 @@ You can configure relevance in two ways:
   - __Priority Criteria__: it imposes that one or more criteria has a higher priority among the others. In this situation, there are no weights; all products that have this feature will be shown first in the search results.
   - __Criteria Composition__: it is a way to distribute weights for each option, ranging from 0 to 10. Here, there is no order between the criteria; the weights will define the relevance.
 
-![criterios-en](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/56c8163ed9b449419c17db066dd4506e/criterios-en.png)
+![criterios-en](https://images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/56c8163ed9b449419c17db066dd4506e/criterios-en.png)
 
 The information considered for the relevance is:
 
@@ -103,6 +103,6 @@ To change relevance settings, follow the steps below.
 
    If you want to change a criterion from **Criteria Composition** to **Priority Criteria**, click on the <i class="fas fa-grip-vertical"></i> icon and drag it to the top of the page, as shown below. Note that when the criterion is set as a priority, you can no longer change its weight. 
 
-   ![criterios-prioritarios-en](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/326edf2ab5b2c2ee3050a97a98090dd9/criterios-prioritarios-en.gif)
+   ![criterios-prioritarios-en](https://images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/326edf2ab5b2c2ee3050a97a98090dd9/criterios-prioritarios-en.gif)
 5. Click `Save` to finish.
 
diff --git a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
index 21933dbd4..2835aae6f 100644
--- a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -21,7 +21,7 @@ The message "__Request headers must contain only ASCII characters__" can be disp
 
 This scenario occurs if the requested page or feature contains a cookie with special characters (non-ASCII).
 
-![ascii_1](//images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/d2137c6c3021d640daf3631e02f941a8/ascii_1.png)
+![ascii_1](https://images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/d2137c6c3021d640daf3631e02f941a8/ascii_1.png)
 
 Per [IETF](https://www.ietf.org/) (Internet Engineering Task Force) standards, the institution that documents the standards used on the internet, cookies should not contain special characters (non-ASCII). For more information on the characters accepted in cookies and headers, see [IETF - Request for Comments 7230 - Section 3.2.6 - Field Value Components](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6).
 
@@ -41,19 +41,19 @@ On the page where the message "__Request headers must contain only ASCII charact
 
   <blockquote><ui>2. In the top bar of the screen, go to the <b>Network</b> tab and sort the requests by clicking <b>Status</b>. The <b>400</b> information in the status indicates that a request has not been processed correctly, and there may be incorrect cookies among the possible errors.</ui>  
 
-![ascii 2](//images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/eb74d2c115b78d65dd60b70da67bfd5b/ascii_2.png)
+![ascii 2](https://images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/eb74d2c115b78d65dd60b70da67bfd5b/ascii_2.png)
 
 <blockquote><ui>3. Click a request and then the <b>Preview</b> tab to identify whether the error found refers to the message "<b>Request headers must contain only ASCII characters</b>".</ui>
 
-![ascii 3](//images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/2151b1260e9f10a1327b5b6f4441ef23/ascii_3.png)
+![ascii 3](https://images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/2151b1260e9f10a1327b5b6f4441ef23/ascii_3.png)
 
 <blockquote><ui>4. Click the <b>Headers</b> tab and copy the cookie details.</ui>
 
-![ascii 4](//images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/305a23cbb5b90bfde1ca139c83978a92/ascii_4.png) 
+![ascii 4](https://images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/305a23cbb5b90bfde1ca139c83978a92/ascii_4.png) 
 
 <blockquote><ui>5. Go to <a href="https://pages.cs.wisc.edu/~markm/ascii.html">online ASCII character validator</a> and enter the cookie information. If one or more special characters are identified, the types and positions will be displayed at the bottom of the character validator.</ui>     
 
-![ascii 5](//images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/917872a195c9cce233a183a4f44b4677/ascii_5.png)  
+![ascii 5](https://images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/917872a195c9cce233a183a4f44b4677/ascii_5.png)  
 
 <blockquote><ui>6. Repeat steps 3 to 5 with all the requests that have errors to identify which of them contain cookies with special characters.</ui>      
 
diff --git a/docs/tutorials/en/requering-authentication-on-store-pages.md b/docs/tutorials/en/requering-authentication-on-store-pages.md
index 423358c2f..3cf5740b0 100644
--- a/docs/tutorials/en/requering-authentication-on-store-pages.md
+++ b/docs/tutorials/en/requering-authentication-on-store-pages.md
@@ -19,15 +19,15 @@ You may require that for certain pages of the store users need to authenticate t
 
 Some pages come with this setting by default. For example, the `/Account` and `/Account/Orders` pages.
 
-![authenticationRequired](//images.contentful.com/alneenqid6w5/60cIIkiKDSEs2ocmqescgM/3f5a0c46d61c1002c22bc7b5469db7eb/authenticationRequired.png)
+![authenticationRequired](https://images.contentful.com/alneenqid6w5/60cIIkiKDSEs2ocmqescgM/3f5a0c46d61c1002c22bc7b5469db7eb/authenticationRequired.png)
 
 But you can either remove the authentication requirement for these pages or insert it into other pages.
 
 To do this, follow the steps below:
 1. Access the __CMS__ module.
 2. Click the folder for the desired page.
-3. Click the __Edit__ button.![editFolder](//images.contentful.com/alneenqid6w5/2DSRmQFQxeAYcoiWCAaU62/bc08bd32b394545d8af716338d55a0be/editFolder.png)
-4. Check or uncheck the __Authentication Required__ flag.![authenticationRequiredFlag](//images.contentful.com/alneenqid6w5/3iK3iGguAUg84KuAsC4MYW/1dcdae221b886b4a4d1cdc4eb87af9a4/authenticationRequiredFlag.png)
+3. Click the __Edit__ button.![editFolder](https://images.contentful.com/alneenqid6w5/2DSRmQFQxeAYcoiWCAaU62/bc08bd32b394545d8af716338d55a0be/editFolder.png)
+4. Check or uncheck the __Authentication Required__ flag.![authenticationRequiredFlag](https://images.contentful.com/alneenqid6w5/3iK3iGguAUg84KuAsC4MYW/1dcdae221b886b4a4d1cdc4eb87af9a4/authenticationRequiredFlag.png)
 5. Click __Save Folder__.
 
 Note that whenever the __Authentication Required__ flag is checked for a folder, the URL of this page will be created with the `_secure` route. Ex: `http://{AccountName}.vtexcommercestable.com.br/_secure/account/`
diff --git a/docs/tutorials/en/requesting-the-ssl-certificate.md b/docs/tutorials/en/requesting-the-ssl-certificate.md
index aefdce502..82af2878a 100644
--- a/docs/tutorials/en/requesting-the-ssl-certificate.md
+++ b/docs/tutorials/en/requesting-the-ssl-certificate.md
@@ -19,7 +19,7 @@ The SSL certificate will protect the transfer of sensitive data by your custome
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
 
-<video class="wp-video-shortcode" id="video-2558-10" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4?_=10" />[//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4](//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4 "//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4")</video>
+<video class="wp-video-shortcode" id="video-2558-10" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4?_=10" />[//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4](https://assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4 "//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4")</video>
 
 [See in details how to acquire the security certificate (SSL).](/en/tutorial/hiring-the-security-certificate-sll)
 
diff --git a/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
index 0a5277650..542ae575a 100644
--- a/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
+++ b/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
@@ -30,7 +30,7 @@ During the initial setup on VTEX, if your store uses[ external integrations with
 
 Once the initial product, price, and inventory integration has been set up and the middleware built, the information flow will be as shown in the diagram below.
 
-![back-office-en](//images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/1d2fe04cb3d2bd6c09b2fd000544d3e4/back-office-en.PNG)
+![back-office-en](https://images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/1d2fe04cb3d2bd6c09b2fd000544d3e4/back-office-en.PNG)
 
 During routine operations, responsibilities are divided as follows:
 
@@ -196,6 +196,6 @@ To understand the right support to request in case of issues with updating the o
 2. Click the desired order to go to the [order details page](https://help.vtex.com/en/tutorial/order-details-page--2Y75n54Cc9VizrlG1N6ZNl).
 3. In the **Order History** section, click `View Interactions` (button illustrated below) and check for any error messages.
 
-![view-interactions-en](//images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/0f0830c6ea1439877301be64f17c0ccf/view-interactions-en.png)
+![view-interactions-en](https://images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/0f0830c6ea1439877301be64f17c0ccf/view-interactions-en.png)
 
 If the error message does not provide sufficient information, the merchant can contact [VTEX Support](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe), providing the interaction screen and order ID as evidence, and our team of experts will help identify the source of the issue.
diff --git a/docs/tutorials/en/responsive-vs-mobile-version.md b/docs/tutorials/en/responsive-vs-mobile-version.md
index 1e2dd06f5..1f3d7bd7f 100644
--- a/docs/tutorials/en/responsive-vs-mobile-version.md
+++ b/docs/tutorials/en/responsive-vs-mobile-version.md
@@ -23,7 +23,7 @@ The design is the same for accesses made from desktops, smartphones, tablets or
 
 The design of the mobile version, as well as its whole programming, are only intended for mobile devices, being a second application. In other words, there is one application for usual browsers, and another one for mobile browsers. Upon accessing the store, the device will be identified and the specific programming will be redirected.
 
-![Main mobile and desktop screen resolutions currently used](//images.contentful.com/alneenqid6w5/4tOHOVzZO8w6a0mUAuqSk6/770a9f0ff450163bd3e30f32e8e56cd6/RESOLUTION.jpg)
+![Main mobile and desktop screen resolutions currently used](https://images.contentful.com/alneenqid6w5/4tOHOVzZO8w6a0mUAuqSk6/770a9f0ff450163bd3e30f32e8e56cd6/RESOLUTION.jpg)
 
 Main mobile and desktop screen resolutions currently in use (there can be variations according to the device used):
 
@@ -55,7 +55,7 @@ Main mobile and desktop screen resolutions currently in use (there can be variat
 
 #### Main visual elements seen in mobile devices
 
-![menu_mobile_version en](//images.ctfassets.net/alneenqid6w5/6Q1KNePAFUUOKEIyswQcA2/2288e7aeef0d78d51391a1d658333cd6/modelo_menu_ingles.png)
+![menu_mobile_version en](https://images.ctfassets.net/alneenqid6w5/6Q1KNePAFUUOKEIyswQcA2/2288e7aeef0d78d51391a1d658333cd6/modelo_menu_ingles.png)
 
 #### Quality is the same regardless of the size!
 
diff --git a/docs/tutorials/en/restrict-public-access-to-master-data-fields.md b/docs/tutorials/en/restrict-public-access-to-master-data-fields.md
index 69a6e4ece..fde6378d0 100644
--- a/docs/tutorials/en/restrict-public-access-to-master-data-fields.md
+++ b/docs/tutorials/en/restrict-public-access-to-master-data-fields.md
@@ -27,24 +27,24 @@ Depending on the data stored, public access without authentication can pose a ri
 2. In Master Data, click **Applications**.
 3. Click the gear <i class="fas fa-cog"></i> next to **Profile System**:
 
-   ![1-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/60f8fe775c03019223c0efb4c4b1974f/1-master-data-confidential-data-en.png)
+   ![1-master-data-confidential-data-en](https://images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/60f8fe775c03019223c0efb4c4b1974f/1-master-data-confidential-data-en.png)
 4. In **Settings**, click **Data structure**.
 
-   ![2-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/43d3dad46261ca9248a3f0d1f0486045/2-master-data-confidential-data-en.png)
+   ![2-master-data-confidential-data-en](https://images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/43d3dad46261ca9248a3f0d1f0486045/2-master-data-confidential-data-en.png)
 5. Click the **Data Entities** tab.
 6. In the data entity row, click the edit <i class="fas fa-edit"></i> button.
 
-   ![3-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/ede7660d491b4a499894812f929baf02/3-master-data-confidential-data-en.png)
+   ![3-master-data-confidential-data-en](https://images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/ede7660d491b4a499894812f929baf02/3-master-data-confidential-data-en.png)
 7. Click the gear icon <i class="fas fa-cog"></i> in the row of a field that contains confidential data.
 
-   ![4-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/5f85332ba75a41caa9d1dc30040ed4c7/4-master-data-confidential-data-en.png)
+   ![4-master-data-confidential-data-en](https://images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/5f85332ba75a41caa9d1dc30040ed4c7/4-master-data-confidential-data-en.png)
 8. Uncheck the following options:
 
    * **Make readable without credentials**
    * **Allow editing without credentials**
    * **Allow filtering without credentials**
 
-   ![5-master-data-confidential-data-en](//images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/df29906627fc7f068ad13733a6d18dc2/5-master-data-confidential-data-en.png)
+   ![5-master-data-confidential-data-en](https://images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/df29906627fc7f068ad13733a6d18dc2/5-master-data-confidential-data-en.png)
 9. Click `Save`.
 10. In the row of the changed data entity, click the Publish button <i class="fas fa-save"></i> to publish the saved settings.
 11. Click `OK`.
diff --git a/docs/tutorials/en/roles.md b/docs/tutorials/en/roles.md
index 2cfdda83a..66b5c8774 100644
--- a/docs/tutorials/en/roles.md
+++ b/docs/tutorials/en/roles.md
@@ -25,7 +25,7 @@ From the **Roles** page, you can do the following:
 * [Edit a role](#editing-a-role)
 * [Delete a role](#deleting-a-role)
 
-![roles-en](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/d0c8e68b433a987fb1d0c9f031726d6f/roles-en.png)
+![roles-en](https://images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/d0c8e68b433a987fb1d0c9f031726d6f/roles-en.png)
 
 The page displays a list of all roles added to the account and their respective information in a table:
 
diff --git a/docs/tutorials/en/rounding-rules.md b/docs/tutorials/en/rounding-rules.md
index 0ba0027f5..2de7197f6 100644
--- a/docs/tutorials/en/rounding-rules.md
+++ b/docs/tutorials/en/rounding-rules.md
@@ -60,16 +60,16 @@ Below you can see examples of the flows of adding, editing and deleting rounding
 
 *_Procedure for creating a rule_*
 
-![config-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/77tOZFjGCbkDjfCbPVeg4c/cf07a45f811bd5bfd6c80ddbc478c2a4/config-arrendodamento-EN.gif)
+![config-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/77tOZFjGCbkDjfCbPVeg4c/cf07a45f811bd5bfd6c80ddbc478c2a4/config-arrendodamento-EN.gif)
 
 *_Procedure for modifying a rule_*
 
-![editar-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/4vuF4QJxVCoTc4iatE1MSZ/728e6875c0ed2787808b5cd9be46a2d3/editar-arrendodamento-EN.gif)
+![editar-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/4vuF4QJxVCoTc4iatE1MSZ/728e6875c0ed2787808b5cd9be46a2d3/editar-arrendodamento-EN.gif)
 
 *_Procedure for deleting a rule_*
 
-![deletar-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/6fDPWVbwtpyCYixRinlkxp/a5420a0633b35607bb4cca0b309c4b89/deletar-arrendodamento-EN.gif)
+![deletar-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/6fDPWVbwtpyCYixRinlkxp/a5420a0633b35607bb4cca0b309c4b89/deletar-arrendodamento-EN.gif)
 
 *_Price simulation for a rule_*
 
-![teste-arrendodamento-EN](//images.ctfassets.net/alneenqid6w5/66dsqzAfz27KJgAUAaXYFp/b3d61dcf614d390d72c7e3d5418ff86e/teste-arrendodamento-EN.gif)
+![teste-arrendodamento-EN](https://images.ctfassets.net/alneenqid6w5/66dsqzAfz27KJgAUAaXYFp/b3d61dcf614d390d72c7e3d5418ff86e/teste-arrendodamento-EN.gif)
diff --git a/docs/tutorials/en/sales-app-sales-performance.md b/docs/tutorials/en/sales-app-sales-performance.md
index 9e07c9cd6..1e917897c 100644
--- a/docs/tutorials/en/sales-app-sales-performance.md
+++ b/docs/tutorials/en/sales-app-sales-performance.md
@@ -23,7 +23,7 @@ You can access your store sales performance metrics by following the steps below
 2. 	Click the <i class="fas fa-bars"></i> button.
 3. 	Click **Sales Performance**.
 
-![Sales Performance (Store)](//images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/dafd378b97bb9b972d78cd86879f6dc2/analytics_en.png)
+![Sales Performance (Store)](https://images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/dafd378b97bb9b972d78cd86879f6dc2/analytics_en.png)
 
 On this page, you will have access to the following metrics:
 
@@ -37,7 +37,7 @@ On this page, you will have access to the following metrics:
 
 To view specific metrics for a sales associate, follow the steps below:
 
-![Bruna's Sales - VTEX Sales App](//images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/5919666bcebd4123cd176461d667da02/Kate_Stewart-s_Sales.png)
+![Bruna's Sales - VTEX Sales App](https://images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/5919666bcebd4123cd176461d667da02/Kate_Stewart-s_Sales.png)
 
 1. 	Click the <i class="far fa-id-badge"></i> icon.
 2. 	Select the sales associate profile and enter the password.
diff --git a/docs/tutorials/en/sales-associate-code-field-at-checkout.md b/docs/tutorials/en/sales-associate-code-field-at-checkout.md
index 375c48fba..4c8d6bee2 100644
--- a/docs/tutorials/en/sales-associate-code-field-at-checkout.md
+++ b/docs/tutorials/en/sales-associate-code-field-at-checkout.md
@@ -61,7 +61,7 @@ After creating the salesassociatecode entity, you need to link it to a promotion
 
 <blockquote><ui>3. In <b>To which items will this promotion apply?</b>, click the <b>utm_campaign</b> option and type <i>salesassociatecode</i>.</ui>
 
-![utm campaign codigovendedor](//images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/4886ffbd85e8e08257a5d8249a734a4f/UTM_Campaign_codigovendedor_en.PNG)
+![utm campaign codigovendedor](https://images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/4886ffbd85e8e08257a5d8249a734a4f/UTM_Campaign_codigovendedor_en.PNG)
 
 <blockquote><ui>4. In <b>Restrictions and limitations of use</b>, add the other available restrictions if desired. Select the <b>Apply with other promotions</b> option.</ui>
 
@@ -93,4 +93,4 @@ Additionally, you need to complete the following steps:
 
 After completing all the above steps, the **Sales associate code** field will be available on the Checkout page.
 
-![Sales associate code](//images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/6f6627b73ef728a83841ed4017256925/Checkout_UI_-_EN_2.png)  
+![Sales associate code](https://images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/6f6627b73ef728a83841ed4017256925/Checkout_UI_-_EN_2.png)  
diff --git a/docs/tutorials/en/sales-associates-instore-beta.md b/docs/tutorials/en/sales-associates-instore-beta.md
index c6fc8a123..70beca28e 100644
--- a/docs/tutorials/en/sales-associates-instore-beta.md
+++ b/docs/tutorials/en/sales-associates-instore-beta.md
@@ -29,7 +29,7 @@ This page allows you to manage your sellers from the following actions:
 * [Edit](#editing-sales-associate-information)
 * [Delete](#deleting-a-sales-associate)
 
-![vendedores-en](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/da3c90c0dfb50c0b5c40b9743b421c8b/image.png)
+![vendedores-en](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/da3c90c0dfb50c0b5c40b9743b421c8b/image.png)
 
 The page displays the following information: 
 
@@ -52,7 +52,7 @@ You can add a sales associate by following the steps below:
 
 After creation, the sales associate will receive a confirmation email and will be redirected to the sales associate's login option in the inStore app.
 
-![email-vendedor-pt](//images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
 <div class ="alert alert-warning">
 <p>Sales associates registered in inStore cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.</p> 
diff --git a/docs/tutorials/en/sales-performance.md b/docs/tutorials/en/sales-performance.md
index 95f643701..631b0647e 100644
--- a/docs/tutorials/en/sales-performance.md
+++ b/docs/tutorials/en/sales-performance.md
@@ -26,7 +26,7 @@ To access the page, go to __Dashboards__ and click on __Sales performance__.
 
 You can customize the view of chart and list data by filtering by period, dimensions and metrics.
 
-![Sales Perf Dash EN](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
+![Sales Perf Dash EN](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/2e794d37d8b2afe1d2d2b89d805ae736/Sales_Perf_Dash_EN.gif)
 
 ## Data 
 
@@ -154,7 +154,7 @@ In addition to applying filters, you can also perform the actions below.
 
 ## Views
 
-![Sales perf update EN](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
+![Sales perf update EN](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/c2573e700f0400eb44176cb4cee696bf/Sales_perf_update_EN.gif)
 
 The Sales Performance dashboard can be customized by applying different filters and selecting the metrics that will be displayed in the chart and in the list. To facilitate your data exploration on a daily basis, we have created views, which save the filters and metrics applied on the page for your direct viewing. You can save, edit, and share different dashboard views. The page comes with the following views configured by default:
 
diff --git a/docs/tutorials/en/scheduling-features-for-special-events.md b/docs/tutorials/en/scheduling-features-for-special-events.md
index 7b8f7930e..369c96241 100644
--- a/docs/tutorials/en/scheduling-features-for-special-events.md
+++ b/docs/tutorials/en/scheduling-features-for-special-events.md
@@ -70,7 +70,7 @@ To schedule content, follow the steps below:
 3. Use the URL field in the top corner to navigate to the page that displays the block whose content you want to overwrite.
 4. Select the block for which you want to create new content. You can select it using the list on the right side or the interface:
 
-![seta-interface](//images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
+![seta-interface](https://images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
 
 5. Click `Configurations` in the upper right corner.
 6. Click the `New content` button.
diff --git a/docs/tutorials/en/scheduling-prices.md b/docs/tutorials/en/scheduling-prices.md
index 62a285b68..026b91523 100644
--- a/docs/tutorials/en/scheduling-prices.md
+++ b/docs/tutorials/en/scheduling-prices.md
@@ -58,7 +58,7 @@ You can also schedule prices by importing a fixed price template. To do this, pl
 
 1. In the VTEX Admin, go to *Prices > Price list*, or type *Price list* in the search bar at the top of the page.
 2. Click on the 📥 icon to export the template to be filled in.
-![Agendar preços - EN](//images.contentful.com/alneenqid6w5/5pBmnKfaoig59962PcNFQq/1fea4935c2c88aebabfa0a505fe4245d/image.png)
+![Agendar preços - EN](https://images.contentful.com/alneenqid6w5/5pBmnKfaoig59962PcNFQq/1fea4935c2c88aebabfa0a505fe4245d/image.png)
 3. Select only the **Fixed prices table** option.
 4. Click on `Export 1 table`.
 
@@ -72,7 +72,7 @@ The template will be sent to your email and you can download it. After downloadi
 - **Date from:** the date and time from which the fixed price will be valid, in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) format. -
 - **Date to:** the date and time from which the fixed price will no longer be valid, in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) format.
 
-![Agendar preço fixo planilha PT](//images.contentful.com/alneenqid6w5/7g3wkpsDPcdjYHT2xSqGhS/1895766def1ed02971f47f003d115491/Screenshot_2021-08-05_at_17-17-11_-EDU-4229-_Agendar_pre__o_fixo.png)
+![Agendar preço fixo planilha PT](https://images.contentful.com/alneenqid6w5/7g3wkpsDPcdjYHT2xSqGhS/1895766def1ed02971f47f003d115491/Screenshot_2021-08-05_at_17-17-11_-EDU-4229-_Agendar_pre__o_fixo.png)
 
 Once you have finished filling in the template, you must import it into the store. Please follow the steps below:
 
diff --git a/docs/tutorials/en/search-configuration.md b/docs/tutorials/en/search-configuration.md
index ad183ed96..e6c6b48b5 100644
--- a/docs/tutorials/en/search-configuration.md
+++ b/docs/tutorials/en/search-configuration.md
@@ -37,7 +37,7 @@ The general settings display the following options related to[ product and SKU s
 
 The facet settings have settings related to the[ filters](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) displayed to your customers during the search:
 
-![Facet configurations](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
+![Facet configurations](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/2f421fca7b4914deb993bb84e731a2d7/facet_settings_admin_v4.png)
 
 * **Facet order:** Order in which the facets will be displayed in the store. If no facet is selected, the default order is alphabetical.
 
diff --git a/docs/tutorials/en/search-control-fulltextsearchbox.md b/docs/tutorials/en/search-control-fulltextsearchbox.md
index b5ea80577..fe01bf7d8 100644
--- a/docs/tutorials/en/search-control-fulltextsearchbox.md
+++ b/docs/tutorials/en/search-control-fulltextsearchbox.md
@@ -21,7 +21,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 The `<vtex.cmc:fullTextSearchBox />` control is responsible for generating the search box. Besides the search filed, the control renders a combo for restricting a search in one department. Below we have an example of the control with no application of css:
 
-![](//images.contentful.com/alneenqid6w5/4tvtNt1u0Mw8sgmwyAaOuW/2375499b868cfe4c24b3425fa0f33a8c/controle-busca-cru.png)
+![](https://images.contentful.com/alneenqid6w5/4tvtNt1u0Mw8sgmwyAaOuW/2375499b868cfe4c24b3425fa0f33a8c/controle-busca-cru.png)
 
 Search is a functionality that must be available on all the pages of a store. That is why it is suggested inserting the control inside a [subtemplate](/hc/pt-br/articles/204868718 "subtemplate"). The search control is used within the sub-template of the store header.
 
@@ -75,9 +75,9 @@ The autocomplete functionality is already provided for in this control, and it i
 
 Examples of how the control can be customized:
 
-![](//images.contentful.com/alneenqid6w5/BMzmz8NA0o4SQqUO8ow4Y/5c6d179a8fca8a3efaf981c05203c061/controle-busca-autocomplete-560x318.png)
+![](https://images.contentful.com/alneenqid6w5/BMzmz8NA0o4SQqUO8ow4Y/5c6d179a8fca8a3efaf981c05203c061/controle-busca-autocomplete-560x318.png)
 
-![](//images.contentful.com/alneenqid6w5/5TiDgTywScWuAcC24wmeIu/58acad8f8151f8803251679453627968/controle-busca-exemplo-560x43.png)
+![](https://images.contentful.com/alneenqid6w5/5TiDgTywScWuAcC24wmeIu/58acad8f8151f8803251679453627968/controle-busca-exemplo-560x43.png)
 
-![](//images.contentful.com/alneenqid6w5/2X2lkCGHdSIaok08yYKCYO/6bef8f3e0c0b11313479226c0174e093/controle-busca-exemplo1.png)
+![](https://images.contentful.com/alneenqid6w5/2X2lkCGHdSIaok08yYKCYO/6bef8f3e0c0b11313479226c0174e093/controle-busca-exemplo1.png)
 
diff --git a/docs/tutorials/en/search-navigator-control.md b/docs/tutorials/en/search-navigator-control.md
index 23a061c25..2b2c073a3 100644
--- a/docs/tutorials/en/search-navigator-control.md
+++ b/docs/tutorials/en/search-navigator-control.md
@@ -44,7 +44,7 @@ For a collection to be rendered in the menu by the Search Navigator control, it
 
 This flag can be found in the collection's settings, inside CMS.
 
-![searchNavigator2](//images.contentful.com/alneenqid6w5/30xKS65fWMuoiQO4ac2EKM/921be3bc19a8cdff48dade515c354908/searchNavigator2.jpg)
+![searchNavigator2](https://images.contentful.com/alneenqid6w5/30xKS65fWMuoiQO4ac2EKM/921be3bc19a8cdff48dade515c354908/searchNavigator2.jpg)
 
 ## Categories
 
@@ -52,7 +52,7 @@ For a category to be rendered by this control, it must be marked with the __Menu
 
 This flag can be found on the category registration screen.
 
-![How Search Navigator control works EN 2](//images.ctfassets.net/alneenqid6w5/4lSSrBSvyUqEGUEw0oMiac/f132379724b8855996e6f41c2e195ce6/2018-10-23_2233_EN_2.png)
+![How Search Navigator control works EN 2](https://images.ctfassets.net/alneenqid6w5/4lSSrBSvyUqEGUEw0oMiac/f132379724b8855996e6f41c2e195ce6/2018-10-23_2233_EN_2.png)
 
 <div class="alert alert-info">
   <strong>Important</strong>: The <code>&lt;vtex.cmc:searchNavigator/&gt;</code> control displays, by default, only the primary-level categories (root) and the lowest-level sub-categories, within the current context. Intermediate splits in the categories tree are omitted. 
@@ -85,7 +85,7 @@ For a product field or SKU field to be displayed on the menu by the Search Navig
 
 Both are found on the field registration screen.
 
-![How Search Navigator control works EN 3](//images.ctfassets.net/alneenqid6w5/2qjmz7DHFaSUq00CGy0cQw/1794e1b088a4ee376627e856dab2cd86/2018-10-23_22-24-47_EN_3.png)
+![How Search Navigator control works EN 3](https://images.ctfassets.net/alneenqid6w5/2qjmz7DHFaSUq00CGy0cQw/1794e1b088a4ee376627e856dab2cd86/2018-10-23_22-24-47_EN_3.png)
 
 ## Price ranges
 
diff --git a/docs/tutorials/en/search-parameters.md b/docs/tutorials/en/search-parameters.md
index 0a519f858..9dd8491f9 100644
--- a/docs/tutorials/en/search-parameters.md
+++ b/docs/tutorials/en/search-parameters.md
@@ -21,7 +21,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 When making a search on VTEX, there are different possibilities of urls. The urls of Departments and Categories are made up as follows:
 
-![](//images.contentful.com/alneenqid6w5/1MhPmB1yxKS426UCsASUsY/eeaf45262ccde7b0a50ee6ef6b787afb/arvore_categoria.png)
+![](https://images.contentful.com/alneenqid6w5/1MhPmB1yxKS426UCsASUsY/eeaf45262ccde7b0a50ee6ef6b787afb/arvore_categoria.png)
 
 In the categories tree above, the links are as follows:
 
@@ -35,7 +35,7 @@ www.store.com/artes-e-entretenimento/festas-e-comemoracoes/artigos-para-festas
 
 The url will always be made up with the term entered in the search field:
 
-![](//images.contentful.com/alneenqid6w5/tJYda31CZUUOCii0EcwmE/89481a9321a61fb50fd5463217d6760d/campo_busca.png)
+![](https://images.contentful.com/alneenqid6w5/tJYda31CZUUOCii0EcwmE/89481a9321a61fb50fd5463217d6760d/campo_busca.png)
 
 www.loja.com.br/cama
 
@@ -49,13 +49,13 @@ Where:
 
 **C:\[DepartmentId/CategoryId/SubcategoryId\]**: Shows products of a specific category, according to the IDs informeds for the department, category and subcategory. This code appears next to category names on **Cadastro de Produtos -> Categoria**:
 
-![](//images.contentful.com/alneenqid6w5/44i8Rue6hiMmMs64wiks86/8f31981e162596d825190865cefd121e/id_categoria1.png)
+![](https://images.contentful.com/alneenqid6w5/44i8Rue6hiMmMs64wiks86/8f31981e162596d825190865cefd121e/id_categoria1.png)
 
 **NOTE: The category ID can also be found on your editing page, at the end of the url.**
 
 **B:\[IdMarca\]: **Shows products of a specific brand, according to the ID informed. This code is shown at the end of the URL, on the page used for changing the brand, in **Cadastro de Produtos &gt; Marca**:
 
-![](//images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
+![](https://images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
 
 <div class = "alert alert-warning" >
   <p><b>Warning:</b> there are two ways to configure collections, through the CMS or the Collection module (Beta). This article is about how to <a href = "https://help.vtex.com/en/tutorial/adding-collections-cms--2YBy6P6X0NFRpkD2ZBxF6L">configure collections through the CMS</a>.</p>
@@ -63,11 +63,11 @@ Where:
 
 **H:\[IdColeção\]**: Shows products of a specific collection, according to the ID informed. This code is informed in collection editing, in **Configurações &gt; Portal &gt; Portal folder &gt; Coleções subfolder:**
 
-![](//images.contentful.com/alneenqid6w5/2vqAbADq0cUQO224YoOQAQ/7eef524621cbf80d9c37b37c9cc4099e/id_colecao.png)
+![](https://images.contentful.com/alneenqid6w5/2vqAbADq0cUQO224YoOQAQ/7eef524621cbf80d9c37b37c9cc4099e/id_colecao.png)
 
 **spec\_fct\_\[IdCampoProduto/Sku\]:\[ValorBuscado\]: **Shows products whose product/sku field value, with the indicated ID, is equal to the value informed. This code can be found on the page used for changing a product/sku field, at the end of the url:
 
-![](//images.contentful.com/alneenqid6w5/7noRXDnenuSU4ugc8mmoSg/7a85e4ab97b87c00d4306c57c2462ecc/id_campo-560x386.png)
+![](https://images.contentful.com/alneenqid6w5/7noRXDnenuSU4ugc8mmoSg/7a85e4ab97b87c00d4306c57c2462ecc/id_campo-560x386.png)
 
 See below an example of use of this field:
 
diff --git a/docs/tutorials/en/searching-for-old-orders.md b/docs/tutorials/en/searching-for-old-orders.md
index 490e8b870..5a7a9f977 100644
--- a/docs/tutorials/en/searching-for-old-orders.md
+++ b/docs/tutorials/en/searching-for-old-orders.md
@@ -19,7 +19,7 @@ To search through your old orders, follow the steps below:
 
 1. In the admin's side menu, click on __Orders Management__
 2. Select __All Orders__
-3. Click on the filter button ![filter](//images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
+3. Click on the filter button ![filter](https://images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
 4. Choose a filter *by period*: __Invoiced date__, __Order date__, __Authorized date__ or **Shipping estimate**
 5. Within the chosen filter, click on the __calendar icon__, next to the text __All dates__
 6. Choose a starting date/hour and an end date/hour
diff --git a/docs/tutorials/en/searching-for-transactions-on-payments.md b/docs/tutorials/en/searching-for-transactions-on-payments.md
index ebbc82dc2..a9fd391db 100644
--- a/docs/tutorials/en/searching-for-transactions-on-payments.md
+++ b/docs/tutorials/en/searching-for-transactions-on-payments.md
@@ -35,13 +35,13 @@ To return to the original list of transactions, just delete the value previously
 
 In the Orders Management, if you click on a given order, you'll see a page with its main information. There you'll find the link _See transaction details_. Click on it to know more about the order:
 
-![Link transação OMS (EN)](//images.ctfassets.net/alneenqid6w5/2CgW46clF6cSU0uQYGyA4s/7b61faff11c95caab8b01d65e7460c33/Link_transa____o_OMS__EN_.png)
+![Link transação OMS (EN)](https://images.ctfassets.net/alneenqid6w5/2CgW46clF6cSU0uQYGyA4s/7b61faff11c95caab8b01d65e7460c33/Link_transa____o_OMS__EN_.png)
 
 ## Payment TID and Payment ID
 
 The search using these codes must necessarily contain all digits, or your search will return empty. Here's how to find them:
 
-![Códigos EN](//images.ctfassets.net/alneenqid6w5/3TyYDhqphmKCCEGce8o6EE/6a2fe4bb481b991e2d9c0d8d25d3c3d3/C__digos_EN.png)
+![Códigos EN](https://images.ctfassets.net/alneenqid6w5/3TyYDhqphmKCCEGce8o6EE/6a2fe4bb481b991e2d9c0d8d25d3c3d3/C__digos_EN.png)
 
 These values, within the transaction detail, represent the communication with the respective connector. At [transaction events](/en/tutorial/how-to-view-the-orders-details), it is possible to validate each contact made.
 
diff --git a/docs/tutorials/en/security-monitor.md b/docs/tutorials/en/security-monitor.md
index 402520dc4..bb9224004 100644
--- a/docs/tutorials/en/security-monitor.md
+++ b/docs/tutorials/en/security-monitor.md
@@ -26,7 +26,7 @@ To access the dashboard, follow the steps below:
 1. In the VTEX Admin, go to **Dashboards**, or type **Dashboards** in the search bar.
 2. Under **Security Monitor**, click **Security Monitor Dashboard**.
 
-![1-security-monitor-en](//images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/1593b6df63e997d6933dcfd3215d72b0/1-security-monitor-en__2_.png)
+![1-security-monitor-en](https://images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/1593b6df63e997d6933dcfd3215d72b0/1-security-monitor-en__2_.png)
 
 Security Monitor displays the findings in three tabs based on their status:
 
@@ -48,7 +48,7 @@ The **Open** tab displays the threats detected by the Security Monitor that have
 
 The top bar displays the total number of findings and the number of threats by severity level (high, medium, or low).
 
-![2-findings-en](//images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/08aac5eda3f4d38354ba6a003b72016d/2-findings-en.png)
+![2-findings-en](https://images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/08aac5eda3f4d38354ba6a003b72016d/2-findings-en.png)
 
 The tab displays the full list of open findings in a table, from the most recent to the oldest:
 
@@ -79,7 +79,7 @@ To move a finding to the **Snoozed** tab, removing it temporarily from the **Ope
 3. Choose the number of days you want the finding to remain in the **Snoozed** tab. The options available are: **7**, **90**, or **120** days.
 4. Click `Snooze`.
 
-![3-snooze-finding-en](//images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/ae0ac9742c235ac0bc1299efd0017521/3-snooze-finding-en.png)
+![3-snooze-finding-en](https://images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/ae0ac9742c235ac0bc1299efd0017521/3-snooze-finding-en.png)
 
 ## Snoozed
 
@@ -108,7 +108,7 @@ In the search bar, enter the user's email address or the name of the application
 
 By clicking `Type` <i class="fas fa-chevron-down"></i>, you can choose one of the finding types to filter the results displayed in the list. Click `Apply` to confirm the chosen filter, and the list will be updated.
 
-![4-filter-findings-en](//images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/f6f39af22a936af16bde30ed57f35f99/4-filter-findings-en.png)
+![4-filter-findings-en](https://images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/f6f39af22a936af16bde30ed57f35f99/4-filter-findings-en.png)
 
 ## Editing notification settings
 
@@ -120,7 +120,7 @@ To edit the admin users who will be notified about the findings, follow the step
    To remove a user, click the `X` next to their email.
 3. Click `Save`.
 
-![5-edit-notifications-en](//images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/0c5ecc5bccd18569a94b72781632d3f2/5-edit-notifications-en.png)
+![5-edit-notifications-en](https://images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/0c5ecc5bccd18569a94b72781632d3f2/5-edit-notifications-en.png)
 
 ## Learn more
 
diff --git a/docs/tutorials/en/seller-management.md b/docs/tutorials/en/seller-management.md
index 6e6c973aa..3d75c1d84 100644
--- a/docs/tutorials/en/seller-management.md
+++ b/docs/tutorials/en/seller-management.md
@@ -17,7 +17,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 **Seller Management** is the page where marketplace operators [add sellers](https://help.vtex.com/en/tutorial/adicionar-seller--tutorials_392), input their information, and manage their status. The page features metrics that allow marketplaces to assess their operation. It is also possible to apply filters to the seller list and group sellers using the _Group_ option. 
 
-![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 ## Metrics
 
@@ -47,7 +47,7 @@ This feature allows merchants to better monitor their operations by:
 
 You can create groups manually by clicking on Add sellers or Manage groups. Once created, you can edit and delete each one.  
 
-![Seller management](//images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/fc25e05f46cc203be9777110c6bacbde/seller_management_en.png)  
+![Seller management](https://images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/fc25e05f46cc203be9777110c6bacbde/seller_management_en.png)  
 
 ## Managing groups  
 
diff --git a/docs/tutorials/en/seller-portal-creating-a-promotion.md b/docs/tutorials/en/seller-portal-creating-a-promotion.md
index a1df04050..ec94659e6 100644
--- a/docs/tutorials/en/seller-portal-creating-a-promotion.md
+++ b/docs/tutorials/en/seller-portal-creating-a-promotion.md
@@ -22,7 +22,7 @@ To create a new promotion as a seller in the Seller Portal, follow the steps bel
 3. Complete the [Promotion fields](#promotion-fields).
 4. Click `Save`.
 5. Review your promotion configuration before publishing it.
-![seller-portal-promo-revisao-en](//images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/cde8b71b347ade7c49aed0056cb8f134/image.png)
+![seller-portal-promo-revisao-en](https://images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/cde8b71b347ade7c49aed0056cb8f134/image.png)
 6. After reviewing the details, click `Confirm`.
 
 Then, the promotion will be activated and applied to your store.
@@ -37,7 +37,7 @@ When multiple promotions apply to the same cart items, the Promotions module app
 
 In this section, you need to configure your promotion's general information.
 
-![seller-portal-promo-geral-en](//images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/c1148e5222e0a6e990c10371a00547f0/image.png)
+![seller-portal-promo-geral-en](https://images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/c1148e5222e0a6e990c10371a00547f0/image.png)
 
 * **Name:** Promotion name.
 * **Status:** Option that defines whether the promotion is active <i class="fas-toggle-on"></i> or inactive <i class="fas-toggle-off"></i>.
@@ -51,7 +51,7 @@ In this section, you need to configure your promotion's general information.
 
 Section that defines the discount type and amount that will be applied in the promotion. See the discount options below:
 
-![seller-portal-promo-tipo-desconto-en](//images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/d9d72c7fc562111e4e454a4b2df35b09/image.png)
+![seller-portal-promo-tipo-desconto-en](https://images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/d9d72c7fc562111e4e454a4b2df35b09/image.png)
 
 #### Price
 
@@ -68,7 +68,7 @@ Section that defines the discount type and amount that will be applied in the pr
 
 In this section, you need to choose whether the promotion will apply to all your store products or only specific products, as in the image below.
 
-![seller-portal-promo-produtos-elegiveis-en](//images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/dacb5c26ee3d3fd9f066617340a7d861/image.png)
+![seller-portal-promo-produtos-elegiveis-en](https://images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/dacb5c26ee3d3fd9f066617340a7d861/image.png)
 
 * **All products:** Applies the promotion to your whole catalog.
 * **Products that meet all the following rules:** Limits your promotion to specific products based on the following rules:
@@ -86,7 +86,7 @@ To remove a rule, click <i class="fas-trash-can"></i> `Remove rule`.
 
 The order must meet all the conditions specified in this section for the promotion to apply.
 
-![seller-portal-promo-condicoes-en](//images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/08cb480d481c4787c8e077b6055980a3/image.png)
+![seller-portal-promo-condicoes-en](https://images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/08cb480d481c4787c8e077b6055980a3/image.png)
 
 * **Item price:** The discount will apply only to items within the specified price range.
 * **Shipping method:** The discount will apply only if the customer selects the same shipping method specified in the promotion.
@@ -97,6 +97,6 @@ The order must meet all the conditions specified in this section for the promoti
 
 The promotion will be limited by the following criteria:
 
-![seller-portal-promo-restricoes-en](//images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/8aab96f2312f7a40532d717b51e355bb/image.png)
+![seller-portal-promo-restricoes-en](https://images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/8aab96f2312f7a40532d717b51e355bb/image.png)
 
 * **Limit the number of eligible items per cart:** Defines the maximum number of items in the cart that will be affected by the promotion. If the cart has more items than the limit, the discount will only be applied to the number of items configured in this field.
diff --git a/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
index 1a6afd936..a9bee80b6 100644
--- a/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
@@ -27,7 +27,7 @@ The Seller Portal enables marketplaces to:
 - Decrease sales conversion time with self-service onboarding of new sellers, which is now faster and frictionless.  
 - Easily share product assortment with the seller and quickly manage shared product offers.  
 
-![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 ## Seller and marketplace interaction in the Seller Portal
 
diff --git a/docs/tutorials/en/seller-portal-product-details.md b/docs/tutorials/en/seller-portal-product-details.md
index 01484736f..ff553bb26 100644
--- a/docs/tutorials/en/seller-portal-product-details.md
+++ b/docs/tutorials/en/seller-portal-product-details.md
@@ -15,7 +15,7 @@ legacySlug: seller-portal-product-details
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
-![Shared products product details EN](//images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/cc3f300460749e515607a49f6e6d2bc2/Shared_products_product_details_EN.jpg)
+![Shared products product details EN](https://images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/cc3f300460749e515607a49f6e6d2bc2/Shared_products_product_details_EN.jpg)
 
 On the product details page of the [Shared Products](https://help.vtex.com/en/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) module, you can view all information about a specific product, including: 
 
diff --git a/docs/tutorials/en/seller-portal-promotions.md b/docs/tutorials/en/seller-portal-promotions.md
index 060fb08de..c78969cb0 100644
--- a/docs/tutorials/en/seller-portal-promotions.md
+++ b/docs/tutorials/en/seller-portal-promotions.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 The **Promotions** page in the Seller Portal allows you to view and manage the complete list of existing promotions, streamlining seller promotion management. Go to **Promotions > Promotions** in the VTEX Admin to access the page.
 
-![seller-portal-promo-en](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/9bef7119b64fec9b074b7f20f6659985/image.png)
+![seller-portal-promo-en](https://images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/9bef7119b64fec9b074b7f20f6659985/image.png)
 
 From the promotion list in the Seller Portal, you can do the following:
 
@@ -75,7 +75,7 @@ To view the number of active promotions in your store and the remaining quota fo
 
 By default, the maximum number of active promotions is 100. If you need to increase this limit, please contact [our Support](https://support.vtex.com/hc/en-us/requests) team.
 
- ![seller-portal-promo-ativas-en](//images.ctfassets.net/alneenqid6w5/3tnyz6u3HxC6Qjezn9PvLr/6e62fdd0fa7a104df792d27d8a4496e1/image.png)
+ ![seller-portal-promo-ativas-en](https://images.ctfassets.net/alneenqid6w5/3tnyz6u3HxC6Qjezn9PvLr/6e62fdd0fa7a104df792d27d8a4496e1/image.png)
 
 ## Accessing the promotion action menu
 
diff --git a/docs/tutorials/en/seller-portal-shared-products.md b/docs/tutorials/en/seller-portal-shared-products.md
index fa232480a..e2e3411f0 100644
--- a/docs/tutorials/en/seller-portal-shared-products.md
+++ b/docs/tutorials/en/seller-portal-shared-products.md
@@ -29,7 +29,7 @@ In the Shared Products page you will find two tabs:
 - Available  
 
  ## Imported
- ![Shared products Importados EN](//images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/00980934a6d88d6aeccc1d1ed66778a2/Shared_products_Importados_EN.jpg)
+ ![Shared products Importados EN](https://images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/00980934a6d88d6aeccc1d1ed66778a2/Shared_products_Importados_EN.jpg)
 
 The *Imported* tab displays products from the marketplace catalog that you have already imported and are ready to become offers. This is also where you activate your products. Above the list there is a search bar where you can search for products by name or SKU.  
 
@@ -38,7 +38,7 @@ The first time you access the Seller Portal the *Imported* tab will be empty bec
 When you click on a product in the list, you will be redirected to a page containing the [Product's Details](https://help.vtex.com/en/tutorial/seller-portal-detalhes-do-produto--K0WWsERWj7aQtmZinhYoP).
 
 ## Available
-![Shared products Disponíveis EN](//images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/5511033385ff07608a9eb279f1dae94f/Shared_products_Dispon__veis_EN.jpg)
+![Shared products Disponíveis EN](https://images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/5511033385ff07608a9eb279f1dae94f/Shared_products_Dispon__veis_EN.jpg)
 
 The *Available* tab displays products from the marketplace catalog that have been made available to the seller but which have not been added to the their catalog.  You can filter the available products by brand or category to facilitate the import process.
 
diff --git a/docs/tutorials/en/send-item-price-with-tax-shown-separately.md b/docs/tutorials/en/send-item-price-with-tax-shown-separately.md
index c2747bc01..367fcc1a8 100644
--- a/docs/tutorials/en/send-item-price-with-tax-shown-separately.md
+++ b/docs/tutorials/en/send-item-price-with-tax-shown-separately.md
@@ -23,10 +23,10 @@ In this article we will show how the system works in these cases.
 
 **Scenario 1**: My ERP sends the price including VAT to VTEX, so I do not need to calculate it.
 
-1. Category page![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
-2. Product page![PRODUCTOSINIVA](//images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
-3. Shopping cart![CARRITOSINIVA](//images.ctfassets.net/alneenqid6w5/xX5Coy1UVUc0weEoY4Gik/c7131a671b35316aba28aaf7e8bbbb75/3_cart.png)
-4. Checkout![CHECKOUTSINIVA](//images.ctfassets.net/alneenqid6w5/5QoFlwnTGg0WG86a6ekYu4/20de3c81acb0967787aaa10565e13d2f/4_check.png)
+1. Category page![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
+2. Product page![PRODUCTOSINIVA](https://images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
+3. Shopping cart![CARRITOSINIVA](https://images.ctfassets.net/alneenqid6w5/xX5Coy1UVUc0weEoY4Gik/c7131a671b35316aba28aaf7e8bbbb75/3_cart.png)
+4. Checkout![CHECKOUTSINIVA](https://images.ctfassets.net/alneenqid6w5/5QoFlwnTGg0WG86a6ekYu4/20de3c81acb0967787aaa10565e13d2f/4_check.png)
 
 **Scenario 2**: My ERP sends the price *without* VAT to VTEX.
 
@@ -38,7 +38,7 @@ Then to create a JS and add the amount of tax in the store window, you can also
 
 __Attention__: On the product page you have to enter a JavaScript to add the values.
 
-1. Category page![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
-2. Product page![PRODUCTOCONIVA](//images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
-3. Shopping cart![CARRITOCONIVA](//images.ctfassets.net/alneenqid6w5/2cVDEuAgwoMYOSegQeQUiO/1b2666371b65289bb3956029b2911742/3a_cart.png)
-4. Checkout![CHECKOUTCONIVA](//images.ctfassets.net/alneenqid6w5/6G4BksRmNO4giagOGga8Sq/7a3c7dd3426abc549ea6b61284a14fe0/4a_check.png)
+1. Category page![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/jdugsMibXU6SO6momcYka/ecfb35f914fe9bbdc137ef5a5e932da4/1_cat.png)
+2. Product page![PRODUCTOCONIVA](https://images.ctfassets.net/alneenqid6w5/hoE9OYL65aaiaqyuUssAI/cdc7633cc4eb4ac2c4ea033e2e0e25c5/2_prod.png)
+3. Shopping cart![CARRITOCONIVA](https://images.ctfassets.net/alneenqid6w5/2cVDEuAgwoMYOSegQeQUiO/1b2666371b65289bb3956029b2911742/3a_cart.png)
+4. Checkout![CHECKOUTCONIVA](https://images.ctfassets.net/alneenqid6w5/6G4BksRmNO4giagOGga8Sq/7a3c7dd3426abc549ea6b61284a14fe0/4a_check.png)
diff --git a/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md b/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
index 05d640807..1497d2305 100644
--- a/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
+++ b/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
@@ -31,10 +31,10 @@ The values accepted by Mercado Livre can be found in the following links. Click
 
 __Links with the values accepted by Mercado Livre__:
 
-- [Brazil](//assets.contentful.com/alneenqid6w5/6BHWQLL9bGuMq2ycMye0uc/76e64b67cb7352d95d6bb977b33394d4/Brasil-2.zip)
-- [Argentina](//assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
-- [Colombia](//assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
-- [Mexico](//assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+- [Brazil](https://assets.contentful.com/alneenqid6w5/6BHWQLL9bGuMq2ycMye0uc/76e64b67cb7352d95d6bb977b33394d4/Brasil-2.zip)
+- [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
+- [Colombia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
+- [Mexico](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
 
 When your spreadsheet is filled with the correct values, just do the __upload on VTEX Bridge__. To do this, follow these steps:
 
@@ -49,7 +49,7 @@ __That's it!__ Now the attributes of your products of types __Clothes__, __Shoes
 
 In Brazil, for example, a *yellow* footwear with *blue* details of *size 39* must be sent to Mercado Livre with the corresponding __SKU ID__ and the codes __33000_Amarelo_52007__, __43000_Azul_52092__ and __23000_39_22039__, relating to *main color*, *secondary color* and *size*. See more examples in the image below:
 
-![Planilha modelo ML](//images.contentful.com/alneenqid6w5/1Z4UPfR5beG6SoMucASAm0/132e8316128421a2c98da7ee8fdb81b4/Planilha-modelo-ML.png)
+![Planilha modelo ML](https://images.contentful.com/alneenqid6w5/1Z4UPfR5beG6SoMucASAm0/132e8316128421a2c98da7ee8fdb81b4/Planilha-modelo-ML.png)
 
 ## Go further
 
diff --git a/docs/tutorials/en/sending-products-to-the-marketplace.md b/docs/tutorials/en/sending-products-to-the-marketplace.md
index 22a2bacfc..766ae809e 100644
--- a/docs/tutorials/en/sending-products-to-the-marketplace.md
+++ b/docs/tutorials/en/sending-products-to-the-marketplace.md
@@ -21,7 +21,7 @@ When integrating with a marketplace, you have to define which products are to be
 
 One possibility is to work with the entire product catalog on the marketplace. To do this, just associate the main store’s sales policy ID which will always be **ID 1**, [when asked to do so during configuration](/en/tutorial/integrating-with-marketplace/).
 
-![ExemploPoliticaComercial](//images.contentful.com/alneenqid6w5/37CzxbrZ9KciYm4G2gK0MK/54a58d8fa3a53dcf310caa2769e53174/ExemploPoliticaComercial.png)
+![ExemploPoliticaComercial](https://images.contentful.com/alneenqid6w5/37CzxbrZ9KciYm4G2gK0MK/54a58d8fa3a53dcf310caa2769e53174/ExemploPoliticaComercial.png)
 
 This sales policy does not require a configured collection of products, since the system already understands that it refers to all products.
 
@@ -33,7 +33,7 @@ Another possibility is to work with a specific mix. Through some differentiated
 4. Check the checkbox of the sales policies to which this product should belong.
 5. Click on **Save**.
 
-![](//images.contentful.com/alneenqid6w5/2Fp2Y3qFF6SCwQaQI2iEiC/fae0654d1685f1f625794180044ae6a6/loja-cadastro-produto.gif)
+![](https://images.contentful.com/alneenqid6w5/2Fp2Y3qFF6SCwQaQI2iEiC/fae0654d1685f1f625794180044ae6a6/loja-cadastro-produto.gif)
 _If there are products that have no value indicated in the **loja** field in the product register or price register, such products will be send to all sales policies configured without a collection._
 
 ## Product indexation
diff --git a/docs/tutorials/en/sending-sku-attributes-to-amazon.md b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
index 474a924f8..5fbf0172d 100644
--- a/docs/tutorials/en/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
@@ -19,7 +19,7 @@ Having done the initial settings for the [Amazon integration](/en/tutorial/integ
 
 The mapping will only be done once for each category. With that, even once you have done the mapping, when new products are created, they will be directly integrated. A __from/to__ of the attributes registered in VTEX will be made with the attributes accepted by Amazon.
 
-1. Create an __upload spreadsheet__ in the format ".xlsx" and fill in the columns title as shown below.![Modelo Atributos Amazon](//images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
+1. Create an __upload spreadsheet__ in the format ".xlsx" and fill in the columns title as shown below.![Modelo Atributos Amazon](https://images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
 
 2. Fill in the fields of the mapping spreadsheet as follows:
 
@@ -46,7 +46,7 @@ Note: If <strong>none</strong> of the category attributes is required by Amazon,
 
 Sample spreadsheet using the Clothing & Accessories category:
 
-![Amazon Mapeamento ](//images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
+![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
 <div class = "alert alert-danger">
 Note that these values must conform to the ones from Amazon. Check which terms are allowed and make the From/To between what is registered in your SKU field in VTEX and the values accepted by Amazon.
diff --git a/docs/tutorials/en/sent-offers-beta.md b/docs/tutorials/en/sent-offers-beta.md
index ade99a2bb..a86329de3 100644
--- a/docs/tutorials/en/sent-offers-beta.md
+++ b/docs/tutorials/en/sent-offers-beta.md
@@ -21,7 +21,7 @@ The Sent Offers module allows sellers to monitor their offers’ submission and
 - [Offers](https://help.vtex.com/en/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#offers)            
 - [Channels](https://help.vtex.com/en/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#channels)          
 
-![Anuncios enviados Home EN](//images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/a9028554a465b67e3dec924aa11d0afa/Anuncios_enviados_Home_EN.jpg)
+![Anuncios enviados Home EN](https://images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/a9028554a465b67e3dec924aa11d0afa/Anuncios_enviados_Home_EN.jpg)
 
 ## Offers
 
diff --git a/docs/tutorials/en/sent-offers-buybox-opportunities.md b/docs/tutorials/en/sent-offers-buybox-opportunities.md
index 3574b3a13..fa44d6bd8 100644
--- a/docs/tutorials/en/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/en/sent-offers-buybox-opportunities.md
@@ -39,13 +39,13 @@ On the [Offer Management](https://help.vtex.com/en/tutorial/offers-listing--7MRb
 
 ## Offer details
 
-![EN Oportunidades Offer details](//images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/6ed62b0628ffc356995b4aa59321f28c/EN_Oportunidades_Offer_details.jpg)
+![EN Oportunidades Offer details](https://images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/6ed62b0628ffc356995b4aa59321f28c/EN_Oportunidades_Offer_details.jpg)
 
 The [Offer details](https://help.vtex.com/en/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) page displays a message about the `Opportunity` at the top of the page. By clicking on `View opportunity`, you will be redirected to the following page.
 
 ## Offer opportunities
 
-![EN Oportunidades oportunidades do anúncio](//images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/f4ca300fea32688a1dcb606f92104cb9/EN_Oportunidades_oportunidades_do_an__ncio.jpg)
+![EN Oportunidades oportunidades do anúncio](https://images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/f4ca300fea32688a1dcb606f92104cb9/EN_Oportunidades_oportunidades_do_an__ncio.jpg)
 
 The **Offer opportunities** page displays the Buybox-eligible offer next to the one already available for sale on the marketplace. On this page, you can compare the data of both offers, such as their brand information, specifications, and dimensions.
 
diff --git a/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md b/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md
index 9b1167eeb..4421d2d12 100644
--- a/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md
+++ b/docs/tutorials/en/set-up-user-authentication-for-recurring-payments.md
@@ -27,6 +27,6 @@ To configure this authentication, follow the steps below.
 2. Acces **Settings**
 3. Activate the flag __Require user authentication for automatically authorized payments__.
 
-![autenticação-usuario-pagamento-recorrencia en](//images.ctfassets.net/alneenqid6w5/2BF2Kr1kowiCAIWOgmqSAA/d65d2bd11d5ac0a2019b9737685a2471/autentica____o-usuario-pagamento-recorrencia_en.png)
+![autenticação-usuario-pagamento-recorrencia en](https://images.ctfassets.net/alneenqid6w5/2BF2Kr1kowiCAIWOgmqSAA/d65d2bd11d5ac0a2019b9737685a2471/autentica____o-usuario-pagamento-recorrencia_en.png)
 
 4. Click on the __Save__ button.
diff --git a/docs/tutorials/en/setting-up-a-personal-gift-message.md b/docs/tutorials/en/setting-up-a-personal-gift-message.md
index 7e794b333..309a82264 100644
--- a/docs/tutorials/en/setting-up-a-personal-gift-message.md
+++ b/docs/tutorials/en/setting-up-a-personal-gift-message.md
@@ -44,11 +44,11 @@ On the website, it is possible to confirm whether the settings are correct. To d
 3. Here, the type of service must be make available for selection. The text must have a maximum of 150 characters.
 4. Select the service in the cart and click on the link to add a message.
 
-![](//images.contentful.com/alneenqid6w5/3txxLHOWtqguWu4qmAqumA/e68ef2cf4881d3b9a01199244567c790/mensagem-carrinho.png)
+![](https://images.contentful.com/alneenqid6w5/3txxLHOWtqguWu4qmAqumA/e68ef2cf4881d3b9a01199244567c790/mensagem-carrinho.png)
 
 You can view the written message on __My Account > My Orders__:
 
-![](//images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
+![](https://images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
 
 <div class="alert alert-info">
   <p>After setting up the SKU service, wait for the indexing process for the registration to be effective on the website. Once the service is active, you will be able to test the purchase.</p>
diff --git a/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md b/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md
index ce6ffee89..056fc20bb 100644
--- a/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md
+++ b/docs/tutorials/en/setting-up-a-similar-product-suggestions-accessories-and-generics.md
@@ -35,7 +35,7 @@ To help you use the above techniques, we can use the fields in the register of p
 4. Fill out the fields correctly as indicated below.
 5. Click on the `Save` button.
 
-![produto-similar-sugestão-acessório-exemplo en](//images.ctfassets.net/alneenqid6w5/4HXcbiIWFGY4eum8MSWwYs/ab6fde2f960fdca559c6a2ec3419fa55/produto-simular-sugest__o-acess__rio-exemplo_en.png)
+![produto-similar-sugestão-acessório-exemplo en](https://images.ctfassets.net/alneenqid6w5/4HXcbiIWFGY4eum8MSWwYs/ab6fde2f960fdca559c6a2ec3419fa55/produto-simular-sugest__o-acess__rio-exemplo_en.png)
 
 **Acessories:** in this field we register the products that must be sold to complement another product. In this option, the products registered as accessories are shown as a purchase option by enabling the selection checkbox (function included in the layout).
 
diff --git a/docs/tutorials/en/setting-up-abandoned-carts.md b/docs/tutorials/en/setting-up-abandoned-carts.md
index cd536272a..108d8a310 100644
--- a/docs/tutorials/en/setting-up-abandoned-carts.md
+++ b/docs/tutorials/en/setting-up-abandoned-carts.md
@@ -40,7 +40,7 @@ You can create your own custom email template or use the default template option
 4. Fill in the __Template XHTML__ field with the template codes.
 5. Click on `Save Template`.
 
-![template xhtml](//images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/d48bd1624a47451e2314e2296237992f/Template_XHTML.PNG)
+![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/d48bd1624a47451e2314e2296237992f/Template_XHTML.PNG)
 
 <div class="alert alert-warning">
 We recommend that template customization should be performed by professionals with experience in the CMS module, and preferably, who have already configured other page and shelf templates.
@@ -50,7 +50,7 @@ We recommend that template customization should be performed by professionals wi
 2. Under __CMS > HTML__ Templates, click on the `CEM-Abandoned-Cart` icon.
 3. Check the information of the template codes present in the __Template XHTML__ field.
 
-![CEM-Abandoned-Cart](//images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/45690f27bc8825ff3819ac3204d168e8/CEM-Abandoned-Cart.PNG)
+![CEM-Abandoned-Cart](https://images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/45690f27bc8825ff3819ac3204d168e8/CEM-Abandoned-Cart.PNG)
 
 #### Configuring email template in Message Center
 
@@ -69,7 +69,7 @@ Once the new email template has been created or the data from the default templa
 The JSON Data field must not be filled or its data used in the email template. It only contains information to allow a preview of the format in which the data will be viewed in the email.
 </div>
 
-![New template - message center](//images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/72c7499b2fdc65ee661c3cb45a387a60/new_template.PNG)
+![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/72c7499b2fdc65ee661c3cb45a387a60/new_template.PNG)
 
 #### SPF Release
 
@@ -77,7 +77,7 @@ The SPF release is essential to avoid problems with email deliverability and mus
 
 As a good practice for configuring DNS for a generic domain (not mandatory), follow the example below:
 
-![Hostnames - SPF](//images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/1ca34737e3275712b51c45283ec5b0c5/Hostnames_-_SPF.PNG)
+![Hostnames - SPF](https://images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/1ca34737e3275712b51c45283ec5b0c5/Hostnames_-_SPF.PNG)
 
 Learn more at [Setting up DNS pointing to VTEX](https://help.vtex.com/en/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280#).
 
@@ -126,7 +126,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><blockquote><ui>-> Último Carrinho - Não está nulo (Last cart - is not null)</ui>   
 
-![Filter master data 2](//images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/6408ac4ab3b36d015790bcf1b1b5d667/Filter_Master_Data.PNG)
+![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/6408ac4ab3b36d015790bcf1b1b5d667/Filter_Master_Data.PNG)
 
 <div class="alert alert-warning">
   In addition to the filters indicated above, it is recommended to insert another filter in the following format: <code>Receives newsletter? - Equal to - True</code>. This ensures compliance with <a href="https://help.vtex.com/en/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">data subject rights</a>, as only customers subscribed to the newsletter will receive abandoned cart emails. Subscription to your store's newsletter can be managed at checkout or in the <a href="https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">My Account</a> section of your store.
@@ -134,7 +134,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><ui> 10. Click on the <b>Schedule</b> tab and select whether to send the email on a specific date or on a dynamic date.</ui>
 
-![Schedule date](//images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/6956b67734b6b7c3970d193c03e8fefc/Schedule_date.PNG)
+![Schedule date](https://images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/6956b67734b6b7c3970d193c03e8fefc/Schedule_date.PNG)
 
 <blockquote><ui>11. In the <b>If positive</b> tab:</ui>
 
@@ -157,7 +157,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><blockquote><ui>h. In <b>URL</b>, enter your store’s address, including the folders in which the layout of the abandoned cart was set up, followed by the cart tag (?refs={!carttag_SCORE}). Ex.: storename.com/CEM/Abandoned-Cart?refs={!carttag_SCORE}.</ui>  
 
-![PastasCarrinhoAbandonado](//images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)  
+![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)  
 
 <div class="alert alert-warning">The URL address must be the real one of the store, not the URL with vtexcommercestable.
 </div>
@@ -171,7 +171,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 <div class="alert-warning">A page’s session expires in 30 minutes. Only after that time, the system schedules the abandoned cart trigger. In other words, the time to be considered is the session's time + the trigger schedule.
 </div>  
 
-![If positive tab](//images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/44d05312148341427e720b76d8a1f24f/If_positive_Tab.PNG)  
+![If positive tab](https://images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/44d05312148341427e720b76d8a1f24f/If_positive_Tab.PNG)  
 
 ### Configuration for VTEX IO stores
 
@@ -182,7 +182,7 @@ To configure the abandoned cart functionality in VTEX IO stores, follow these st
 3. Perform the [SPF release](#spf-release).
 4. [Configure the trigger](#trigger-configuration) the same way as in Legado stores up to Step 10. From Step 11 (__If positive__ tab), follow the instructions available at [Trigger configuration information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#trigger-configuration-information).
 
-  ![If positive tab IO](//images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/1b177fab2726c1d05d39608727cc2057/If_positive_Tab_IO.PNG)
+  ![If positive tab IO](https://images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/1b177fab2726c1d05d39608727cc2057/If_positive_Tab_IO.PNG)
 
 ## Frequently Asked Questions (FAQ)
 
diff --git a/docs/tutorials/en/setting-up-amazonpay-beta.md b/docs/tutorials/en/setting-up-amazonpay-beta.md
index 597f6b404..d9321c906 100644
--- a/docs/tutorials/en/setting-up-amazonpay-beta.md
+++ b/docs/tutorials/en/setting-up-amazonpay-beta.md
@@ -28,40 +28,40 @@ Before setting up the affiliation in VTEX Admin, first you need to have your **S
 
 1. Go to the [Amazon seller central website](https://sellercentral.amazon.com) and login in your account.
 2. Open the menu on the left side.  
-![AmazonPay Panel EN](//images.contentful.com/alneenqid6w5/6KFdDouUaoD4UJaLQAsqSz/3297af465b1ae0ee5d6fad4deb750b56/AmazonPay_Panel_EN.png)
+![AmazonPay Panel EN](https://images.contentful.com/alneenqid6w5/6KFdDouUaoD4UJaLQAsqSz/3297af465b1ae0ee5d6fad4deb750b56/AmazonPay_Panel_EN.png)
 3. Go to **Integration** > **Integration Central**.  
-![AmazonPay Integration Central Menu EN](//images.contentful.com/alneenqid6w5/7DmM4Mih9CvaetzlZhRqzS/fe6bdc50584f121e913383f15c111b51/AmazonPay_Integration_Central_Menu_EN.png)
+![AmazonPay Integration Central Menu EN](https://images.contentful.com/alneenqid6w5/7DmM4Mih9CvaetzlZhRqzS/fe6bdc50584f121e913383f15c111b51/AmazonPay_Integration_Central_Menu_EN.png)
 4. In this screen, fill it with the following options:
   - **Connect to:** Website or Mobile tab.
   - **Ecommerce provider:** Self-developed.
   - **Payment-Type:** One-time Payments.  
-![AmazonPay Integration Central Settings 1 EN](//images.contentful.com/alneenqid6w5/6KaER70LjnMU7WugdDIgIr/04ad489b186796ded30cc41a61c23648/AmazonPay_Integration_Central_Settings_1_EN.png)
+![AmazonPay Integration Central Settings 1 EN](https://images.contentful.com/alneenqid6w5/6KaER70LjnMU7WugdDIgIr/04ad489b186796ded30cc41a61c23648/AmazonPay_Integration_Central_Settings_1_EN.png)
 5. Click on **Generate Key**. A certificate will be downloaded, which will be used later as a Private Key.
 6. Your Public Key is generated with an **Store ID** and **Merchant ID**. Save them to set up the affiliation in your VTEX store.  
-![AmazonPay Integration Central Settings 2 EN](//images.contentful.com/alneenqid6w5/1fiAgbd7Rs1HI6rVrKmY0L/7e193f35adce0d2c0d226cb419e94aa8/AmazonPay_Integration_Central_Settings_2_EN.png)
+![AmazonPay Integration Central Settings 2 EN](https://images.contentful.com/alneenqid6w5/1fiAgbd7Rs1HI6rVrKmY0L/7e193f35adce0d2c0d226cb419e94aa8/AmazonPay_Integration_Central_Settings_2_EN.png)
 
 ## Setting up the gateway affiliation
 
 1. Access the **Payments** module on the left panel of VTEX Admin.  
-![Admin Payments Menu EN](//images.contentful.com/alneenqid6w5/5dtD9EndAckFLKEyPwA5Mc/d7e4968eb5f493d47b0236be7800c2c3/Admin_Payments_Menu_EN.png)
+![Admin Payments Menu EN](https://images.contentful.com/alneenqid6w5/5dtD9EndAckFLKEyPwA5Mc/d7e4968eb5f493d47b0236be7800c2c3/Admin_Payments_Menu_EN.png)
 2. Click on **Settings**.  
-![Admin Payments Settings Menu EN](//images.contentful.com/alneenqid6w5/1peuzMZTDlNeVuY8N9qZQL/9765c2737e4f7f0bddffa86318fb4cbf/Admin_Payments_Settings_Menu_EN.png)
+![Admin Payments Settings Menu EN](https://images.contentful.com/alneenqid6w5/1peuzMZTDlNeVuY8N9qZQL/9765c2737e4f7f0bddffa86318fb4cbf/Admin_Payments_Settings_Menu_EN.png)
 3. Access the **Gateways Affiliations** tab.
 4. Click on the **+** button.  
-![Admin Gateway Affiliations EN](//images.contentful.com/alneenqid6w5/3CDQN4yhyAypTvtneOGKZ1/17c55af763dab4dae8c2ef8fcd4651c9/Admin_Gateway_Affiliations_EN.png)
+![Admin Gateway Affiliations EN](https://images.contentful.com/alneenqid6w5/3CDQN4yhyAypTvtneOGKZ1/17c55af763dab4dae8c2ef8fcd4651c9/Admin_Gateway_Affiliations_EN.png)
 5. Search for the **AmazonPay** affiliation card and click on it.  
-![Gateway Affiliations AmazonPay EN](//images.contentful.com/alneenqid6w5/3eKvBqrNHEDFk0x9gXybJ8/5b86a113c1a110f0629649e315b4c25e/Gateway_Affiliations_AmazonPay_EN.png)
+![Gateway Affiliations AmazonPay EN](https://images.contentful.com/alneenqid6w5/3eKvBqrNHEDFk0x9gXybJ8/5b86a113c1a110f0629649e315b4c25e/Gateway_Affiliations_AmazonPay_EN.png)
 6. Fill the **Application Key** field with your **Merchant ID** and the **Application Token** field with your **Store ID**.  
-![AmazonPay Configuration EN](//images.contentful.com/alneenqid6w5/1rvQhMNYbJJINHjQkvofYp/82d1a5ce3745eb2b227eb1bbbfad920a/AmazonPay_Configuration_EN.png)
+![AmazonPay Configuration EN](https://images.contentful.com/alneenqid6w5/1rvQhMNYbJJINHjQkvofYp/82d1a5ce3745eb2b227eb1bbbfad920a/AmazonPay_Configuration_EN.png)
 7. Click on **Save**.
 
 ## Setting up the AmazonPay app
 
 1. Access the **Apps** module on the left panel of VTEX Admin.
 2. Click on **My apps**.  
-![My apps menu EN](//images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
+![My apps menu EN](https://images.ctfassets.net/alneenqid6w5/4oRHARlS6i4lZac17nyHhC/b912df890af790633a2ada35b504e653/My_apps_menu_EN.png)
 3. Find the AmazonPay app installed by VTEX and click on **Settings**.  
-![Admin My apps AmazonPay EN](//images.contentful.com/alneenqid6w5/4oy769BIF5gz08hPMeFdRv/92a6cb38ddb94d4e76078959642cc57c/Admin_My_apps_AmazonPay_EN.png)
+![Admin My apps AmazonPay EN](https://images.contentful.com/alneenqid6w5/4oy769BIF5gz08hPMeFdRv/92a6cb38ddb94d4e76078959642cc57c/Admin_My_apps_AmazonPay_EN.png)
 4. Fill the settings according to the table below:
 
 | Field | Description |
diff --git a/docs/tutorials/en/setting-up-an-index-on-master-data.md b/docs/tutorials/en/setting-up-an-index-on-master-data.md
index 3e2514e4d..6670620b6 100644
--- a/docs/tutorials/en/setting-up-an-index-on-master-data.md
+++ b/docs/tutorials/en/setting-up-an-index-on-master-data.md
@@ -39,9 +39,9 @@ The alternate key prevents registration of a value that has already been registe
 The ID is a number that cannot be repeated, since it identifies the customer. “Nome” is the customer name.
 However, to facilitate the search, the column “Nome” was set up as an index and classified as a **Valores Únicos **column. 
 
-[![indice1](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png "![indice1](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)")As a result, you will not be able to enter a name that is already registered in Cliente. 
+[![indice1](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png "![indice1](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)")As a result, you will not be able to enter a name that is already registered in Cliente. 
 
-[![indice2](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png "![indice2](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)")
+[![indice2](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png "![indice2](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)")
 The example above shows that the **Valores Únicos** option must be used carefully, or, in case a value is repeated, it will not be registered with the settings chosen.
 
 ### Several fields in the Index
@@ -52,9 +52,9 @@ In this case, the alternate key will prevent a combination of the fields selecte
 
 In the same example, imagine that the cliente entity has one more column: CPF. Accordingly, in the settings of the index, the columns nome and CPF were included in **Composição de campos.**
 
-[![indice3](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png "![indice3](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)")
+[![indice3](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png "![indice3](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)")
 Now, it is possible to include the name “Marcos” from the previous example, as long as he does not have the same CPF number as the “Marcos” previously registered. That is, just the combination of fields cannot be repeated. Records may have the same CPFs or names, but registering the same CPF and name in one record is not allowed.
 
-[![indice4](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png "![indice4](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)")
+[![indice4](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png "![indice4](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)")
 
 __Remember!__ This situation also requires attention, since the same combination of values cannot be repeated, and the record will not be saved. We recommend that the attribute **Valores Únicos**, in the Index, is used only when the repetition of values is not possible.
diff --git a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
index 5288765b8..d4751af23 100644
--- a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -17,7 +17,7 @@ subcategory:
 
 This article aims to explain how the inStore app configures AppLinking for `payment` and `payment-reversal` actions with the acquirers' apps.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Setting fields
 
diff --git a/docs/tutorials/en/setting-up-b2b-on-vtex.md b/docs/tutorials/en/setting-up-b2b-on-vtex.md
index abd5b3fca..a1bad3d28 100644
--- a/docs/tutorials/en/setting-up-b2b-on-vtex.md
+++ b/docs/tutorials/en/setting-up-b2b-on-vtex.md
@@ -35,7 +35,7 @@ This is the most important step to activate the B2B. Upon setting up the B2B Com
 
 Usually, in traditional B2Bs, this field is filled out with the value `approved="true"` (where `approved` is the name of a field of the Client entity, in Master Data). Using this rule, only authenticated and approved users will be able to browse the website.
 
-![](//images.contentful.com/alneenqid6w5/34rM0gmlgQOoqwwEG2c0ck/a506984d2e7c23381e05a6ad16306d9f/1.png)
+![](https://images.contentful.com/alneenqid6w5/34rM0gmlgQOoqwwEG2c0ck/a506984d2e7c23381e05a6ad16306d9f/1.png)
 
 ## 2.Customize the layout of B2B directories
 
@@ -49,13 +49,13 @@ Check out the basic characteristics of each type of user:
 
 Thus, to have a B2B environment, the **401** and **403** folders, under the **system** folder, must be customized.
 
-![](//images.contentful.com/alneenqid6w5/4eOGUWH7nWqyQGCmIou6WO/1910b62f54515007e85aa3a82d04fb9e/2.png)
+![](https://images.contentful.com/alneenqid6w5/4eOGUWH7nWqyQGCmIou6WO/1910b62f54515007e85aa3a82d04fb9e/2.png)
 
 Browsing by Anonymous users (when attempting to access any page, they will be redirected to 401):
-![](//images.contentful.com/alneenqid6w5/1bxTbhKatws2mgGiOGSUYW/8bf8e626bf53a8e785ffdcc5f2ffc813/3.png)
+![](https://images.contentful.com/alneenqid6w5/1bxTbhKatws2mgGiOGSUYW/8bf8e626bf53a8e785ffdcc5f2ffc813/3.png)
 
 Browsing by non-approved users (when attempting to access any page, they will be redirected to 403):
-![](//images.contentful.com/alneenqid6w5/1Ep24Fgl1SIG6Uw8Wmkq42/2a995f8d9c2be0e92629447c1e6d3948/4.png)
+![](https://images.contentful.com/alneenqid6w5/1Ep24Fgl1SIG6Uw8Wmkq42/2a995f8d9c2be0e92629447c1e6d3948/4.png)
 
 ## 3. Define pre-registration fields
 
@@ -69,7 +69,7 @@ Accordingly, all pre-registration fields must be defined. B2B usually uses clien
 
 ## 4. Create a pre-registration form
 
-Upon the definition of fields, the pre-registration form must be created on the **system/401** folder, since this is the only folder to which anonymous users will be redirected. The information included in the form will be sent to CRM through the Master Data APIs ([see documentation](https://developers.vtex.com/reference/master-data-api-v2-overview)), that is, the development of a JavaScript file will be required for using this function. Check out [examples of HTML and JavaScript files](//assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar "Example of HTML and JS")[ templates](//assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar " templates") serving this purpose.
+Upon the definition of fields, the pre-registration form must be created on the **system/401** folder, since this is the only folder to which anonymous users will be redirected. The information included in the form will be sent to CRM through the Master Data APIs ([see documentation](https://developers.vtex.com/reference/master-data-api-v2-overview)), that is, the development of a JavaScript file will be required for using this function. Check out [examples of HTML and JavaScript files](https://assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar "Example of HTML and JS")[ templates](https://assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar " templates") serving this purpose.
 
 ## 5. Operation
 
diff --git a/docs/tutorials/en/setting-up-cache-for-queries-to-master-data.md b/docs/tutorials/en/setting-up-cache-for-queries-to-master-data.md
index 6b2efdef7..54b415ca4 100644
--- a/docs/tutorials/en/setting-up-cache-for-queries-to-master-data.md
+++ b/docs/tutorials/en/setting-up-cache-for-queries-to-master-data.md
@@ -26,7 +26,7 @@ To configure this cache layer, follow the steps below:
 2. Click __Novo__ to create a new entity or the pencil icon of an existing entity if you want to edit it.
 3. Click the __Tempo de cache para consultas paginadas__ check box ("Cache time for paged queries") and choose the cache time for the entity.
 
-![cacheMD](//images.contentful.com/alneenqid6w5/7EJ8s7Z3uE0coc4QUkQcQC/0efbe18c6bd8018165e18f6d87da765f/cacheMD.jpg)
+![cacheMD](https://images.contentful.com/alneenqid6w5/7EJ8s7Z3uE0coc4QUkQcQC/0efbe18c6bd8018165e18f6d87da765f/cacheMD.jpg)
 
 The cache time options are:
 - 5 hours
diff --git a/docs/tutorials/en/setting-up-cybersource-gateway.md b/docs/tutorials/en/setting-up-cybersource-gateway.md
index 117369757..d07646e9d 100644
--- a/docs/tutorials/en/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/en/setting-up-cybersource-gateway.md
@@ -64,7 +64,7 @@ Follow the steps below:
 
 Once you have obtained the available authentication keys, it is time to configure the Cybersource IO app in the Admin. 
 
-![Cybersource Admin settings EN](//images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/9d036d1151c88215344459a3ae57fd91/Cybersource_Admin_settings_EN.JPG)
+![Cybersource Admin settings EN](https://images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/9d036d1151c88215344459a3ae57fd91/Cybersource_Admin_settings_EN.JPG)
 
 Follow the steps below to configure the Cybersource IO app:
 
@@ -189,7 +189,7 @@ document.body.appendChild(noScript);
 
 Additionally, you can define custom fields that will be included in orders forwarded from VTEX to Cybersource. 
 
-![Cybersource Admin merchant define fields EN](//images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/176d6380fb7ef021d18822973f392ab0/Cybersource_Admin_merchant_define_fields_EN.JPG)
+![Cybersource Admin merchant define fields EN](https://images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/176d6380fb7ef021d18822973f392ab0/Cybersource_Admin_merchant_define_fields_EN.JPG)
 
 See below how to create these fields:
 
diff --git a/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md b/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md
index 606077827..cc507336b 100644
--- a/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md
+++ b/docs/tutorials/en/setting-up-intelligent-search-integration-with-the-catalog.md
@@ -25,7 +25,7 @@ Follow the instructions to start the integration process:
 
 The indexing process will start. Once completed, the screen shown below will be displayed.
 
-![integracoes-is-en](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/20ef33f4ff2b33fca08a777d6c3c90c2/integracoes-is-en.PNG)
+![integracoes-is-en](https://images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/20ef33f4ff2b33fca08a777d6c3c90c2/integracoes-is-en.PNG)
 
 You don't need to repeat this process. After starting the integration, you can follow the indexing status on the [Indexing History](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) page.
 
diff --git a/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
index 13f353ff4..dded50683 100644
--- a/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
@@ -35,16 +35,16 @@ Let's now turn our attention to the step-by-step process below:
 
 1. Access your Apple __developer account__ at `https://developer.apple.com/account/#/overview/`;
 2. Select the __Certificates, IDs & Profiles__ option.
-![AP1](//images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
+![AP1](https://images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
 3. Select __Identifiers__;
- ![AP2](//images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
+ ![AP2](https://images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
 4. Next to Identifiers, click on the __blue + button__;
-![AP3](//images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
+![AP3](https://images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
 5. Select the __Merchant IDs__ option;
-6. Click on the blue __Continue__ button; ![AP4](//images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
+6. Click on the blue __Continue__ button; ![AP4](https://images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
 7. Fill on the __description__ field;
 8. Fill in the __identifier__ field;
-9. Click on __continue__; ![AP5](//images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
+9. Click on __continue__; ![AP5](https://images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
 
 You will have created your __Merchant ID__.
 
@@ -58,13 +58,13 @@ Thereafter, the retailer can submit the file to Apple Pay's system.
 
 Follow the instructions below to proceed to this step:
 
-1. On the left-hand side, open __Certificates__ from the menu; ![AP6](//images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
+1. On the left-hand side, open __Certificates__ from the menu; ![AP6](https://images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
 2. Type in your newly created __Merchant ID__ in the search bar;
-3. Select the desired __Merchant ID__; ![AP7](//images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
+3. Select the desired __Merchant ID__; ![AP7](https://images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
 4. Under __Apple Pay Payment Processing Certificate__, click the __Create Certificate__ button. 
-![AP8](//images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
+![AP8](https://images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
 5. Ensure that the question *"Will payments associated with this Merchant ID be processed exclusively in China?"* is ticked with the __default option (No)__.
-![AP9](//images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
+![AP9](https://images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
 
 You'll then be redirected to a screen with instructions on creating the Certificate Signing Request (CSR). 
 
@@ -77,9 +77,9 @@ With the {{merchantID}}.csr. that you've received, complete the following:
 1. Click on __Choose File__;
 2.  Select the desired __CSR file__;
 3.  Click on __Continue__; 
-![AP10](//images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
+![AP10](https://images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
 4. Click on __Download__;
-![AP11](//images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
+![AP11](https://images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
 5. Click on __Done__.
 
 ## Adding domains to Merchant ID
@@ -97,16 +97,16 @@ Lastly, you need to import this file to VTEX's system through Postman - an [API]
 Follow these steps:
 
 1. Search for the recently created __MerchantID__ in the search bar;
-![AP12](//images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
+![AP12](https://images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
 2. Click on the desired __MerchantID__;
 3. In the __Merchant Domain__ module, click on __Add Domain__;
-![AP13](//images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
+![AP13](https://images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
 4. Add the domain in the __Enter the domain you wish to register__ field;  5. Click on __save__.
 
 Thereafter, to upload the `.txt` file by API, follow these instructions:
 
 1. Click on __Download__ and make no changes to the file.
-![AP14](//images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
+![AP14](https://images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
 2. Open the `.txt` file and __copy__ all the content.
 
 Then, start a Postman session. You perform a call to VTEX's CDN using the POST method:
@@ -118,7 +118,7 @@ Then, start a Postman session. You perform a call to VTEX's CDN using the POST m
 Now, when making the _POST_ call, the response will inform you that your certificate will be saved for 60 minutes. During this time, you should complete the domain validation.
 
 Head back to the Apple's website. On the same screen where you downloaded the `.txt` file, click on __Verify__.
-![AP15](//images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
+![AP15](https://images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
 
 If you've followed the step-by-step correctly, your domain will be registered with the __verified__ status. If you want, you can repeat the process to add more domains by using the __Add Domain__ button in the __Merchant Domains__ section. 
 
@@ -134,12 +134,12 @@ Notice: we recommend an easy to remember password, since it will be filled into
 
 1. Access the __Certificate, Identifiers & Profilers__ module;
 2. From the left side menu, choose __Identifiers__;
-3. In the upper right corner, filter by __Merchant IDs__; ![AP16](//images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
+3. In the upper right corner, filter by __Merchant IDs__; ![AP16](https://images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
 4. Select the desired __Merchant Identifier__;
-5. Click on __Create Certificate__; ![AP17](//images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
+5. Click on __Create Certificate__; ![AP17](https://images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
 6. Follow the __instructions__ displayed on the screen to create a certificate;
-7. Click on __Continue__;  ![AP18](//images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
-8. Click on __Download__.  ![AP19](//images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
+7. Click on __Continue__;  ![AP18](https://images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
+8. Click on __Download__.  ![AP19](https://images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
 
 After the file has been downloaded, double-click it to install it in Keychain Access.
 
@@ -147,7 +147,7 @@ Afterwards, proceed to the following steps:
 
 1. Open __Keychain Access__;
 2. Locate the __certificate__ created in step 4 above;
-3. Right click on the __key__ icon; ![AP20](//images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
+3. Right click on the __key__ icon; ![AP20](https://images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
 4. Click on __Export__;
 5. Give the __certificate__ a name;
 6. Select the __.p12__ export format;
diff --git a/docs/tutorials/en/setting-up-payments-with-easypay-seller.md b/docs/tutorials/en/setting-up-payments-with-easypay-seller.md
index 70793f19d..9ed192262 100644
--- a/docs/tutorials/en/setting-up-payments-with-easypay-seller.md
+++ b/docs/tutorials/en/setting-up-payments-with-easypay-seller.md
@@ -45,7 +45,7 @@ After installing the easypay Seller Account app, you need to configure it. To ac
 
 <blockquote><ui>- <b>Easypay Account UID</b>: Identification of your seller account where purchase amounts from store sales will be deposited. To get this information, access the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo at the top of the screen, and click the desired account. Copy and save the <b>Account UID</b> information.</ui> 
 
-![easypay_en_18](//images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/2e4dd4665f90512068d9f145b7a81caa/easypay_en_18.png)
+![easypay_en_18](https://images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/2e4dd4665f90512068d9f145b7a81caa/easypay_en_18.png)
 
 <blockquote><ui>4. Click <b>Save</b>.</ui>
 
diff --git a/docs/tutorials/en/setting-up-payments-with-easypay.md b/docs/tutorials/en/setting-up-payments-with-easypay.md
index afc5fa306..e893751f8 100644
--- a/docs/tutorials/en/setting-up-payments-with-easypay.md
+++ b/docs/tutorials/en/setting-up-payments-with-easypay.md
@@ -48,7 +48,7 @@ Configuration is divided in four sections:
 - [easypay checkout customization (required)](#easypay-checkout-customization)
 - [Sandbox mode](#sandbox-mode)
 
-![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+![easypay_pt_1](https://images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
 
 <div class="alert alert-warning" role="alert">You must set up the following configurations in the <a href="https://backoffice.easypay.pt/">easypay environment</a>. easypay controls these settings, therefore, VTEX does not guarantee that the steps below will be permanently updated. Use this document as a reference and check your <a href="https://backoffice.easypay.pt/">easypay environment</a> for up-to-date information.</div>
 
@@ -60,25 +60,25 @@ __Key ID e Key Value__: easypay key value and ID.
 
 <blockquote><ui>1. In the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo in the top left corner of the screen and the arrow of the desired account.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
 <blockquote><ui>2. Go to <b>Web Services > Configuration API 2.0 > Keys</b>.</ui>
 
-![easypay_en_3](//images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/7a37b868b1d80e24001ad58e3debeee8/easypay_en_3.png)
+![easypay_en_3](https://images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/7a37b868b1d80e24001ad58e3debeee8/easypay_en_3.png)
 
 <blockquote><ui>3. Copy and save the <b>ID</b> and <b>Key</b> information.</ui>
 
-![easypay_en_4](//images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/9cd6f593c3f473726fc0380c0688d219/easypay_en_4.png)
+![easypay_en_4](https://images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/9cd6f593c3f473726fc0380c0688d219/easypay_en_4.png)
 
 __Merchant account UID__: identification of the merchant account where purchase amounts from store sales will be deposited. If there is no separate merchant account, you can use the "Account UID" of the payment account.
 
 <blockquote><ui>1. In the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo in the top left corner of the screen, then click the arrow on the "MERCHANT 1" account.</ui>
 
-![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+![easypay_pt_5](https://images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
 
 <blockquote><ui>2. Copy and save the <b>Account UID</b> information.</ui>
 
-![easypay_en_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/e15357e9cfb846850ada8bfeda405d48/easypay_en_6.png)
+![easypay_en_6](https://images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/e15357e9cfb846850ada8bfeda405d48/easypay_en_6.png)
 
 __Margin account UID__: identification of the margin account. 
 
@@ -90,7 +90,7 @@ __Refund account ID and Refund account key__: If there is no specific refund acc
 
 In this section, you must indicate whether your store will use asynchronous and/or synchronous payments. See the easypay documentation to check the available [payment methods](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) and their identification [acronyms](https://docs.quality-utility.aws.easypay.pt/checkout/reference).
 
-![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+![easypay_pt_7](https://images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
 
 __Accepted asynchronous payment types__: asynchronous payment methods available to the customer. Only enter the acronyms of the asynchronous payment types, separated by commas without periods or spaces.
 
@@ -122,7 +122,7 @@ Example:
 
 easypay has a native checkout layout configured in the app. See below:
 
-![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+![easypay_pt_8](https://images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
 
 If you want to customize easypay's native checkout, complete one or more fields in this section:
 
@@ -174,7 +174,7 @@ To configure the easypay webhook, follow the steps below:
 
 <blockquote><ui>1. In the <a href="https://backoffice.easypay.pt/">easypay environment</a>, click the easypay logo in the top left corner of the screen, then click the arrow of the desired account.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
 <blockquote><ui>2. Go to <b>Web Services > URL Configuration</b>.</ui>
 
@@ -182,7 +182,7 @@ To configure the easypay webhook, follow the steps below:
 
 `https://{your-account-name}.myvtex.com/_v/easypaypartnerpt.payment-provider-easypay/webhook`
 
-![easypay_en_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/a07d223716625952489b062874cf0aab/easypay_en_9.png)
+![easypay_en_9](https://images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/a07d223716625952489b062874cf0aab/easypay_en_9.png)
 
 <blockquote><ui>4. Click <b>Submit</b>.</ui>
 
diff --git a/docs/tutorials/en/setting-up-payments-with-itau-rede.md b/docs/tutorials/en/setting-up-payments-with-itau-rede.md
index 989b31c85..97e75cac9 100644
--- a/docs/tutorials/en/setting-up-payments-with-itau-rede.md
+++ b/docs/tutorials/en/setting-up-payments-with-itau-rede.md
@@ -35,27 +35,27 @@ To obtain the __App key__ and __App token__ credentials necessary to configure I
 
 <blockquote><ui>2. Select the account in which you want to transact payments at VTEX and click <b>Aplicar</b>. Save the account number, as it must be used in the <b>App key</b> field in the <a href="#setting-up-itau-rede-on-vtex">Setting up Itaú Rede on VTEX</a>.</ui> 
 
-![Itaú Rede_1](//images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
+![Itaú Rede_1](https://images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
 
 <blockquote><ui>3. After the screen updates to the desired account, in the <b>para vender</b> menu, select the <b>e-commerce</b> option.
 
-![Itaú Rede_2](//images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
+![Itaú Rede_2](https://images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
 
 <blockquote><ui>4. On the <b>e-commerce</b> page, click on the <b>chave de integração</b> card.
 
-![Itaú Rede_3](//images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
+![Itaú Rede_3](https://images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
 
 <blockquote><ui>5. After reading the "chave de integração" information, click <b>li, estou ciente</b>.
 
-![Itaú Rede_4](//images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
+![Itaú Rede_4](https://images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
 
 <blockquote><ui>6. Click the <b>gerar nova chave</b> button.
 
-![Itaú Rede_5](//images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
+![Itaú Rede_5](https://images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
 
 <blockquote><ui>7. Check the information described in the <b>gerar nova chave de integração</b> window and click <b>gerar nova chave</b>.
 
-![Itaú Rede_6](//images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
+![Itaú Rede_6](https://images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
 
 <blockquote><ui>8. After creating the new key, click <b>copiar</b> and preserve the information in a safe location. This key must be used in the <b>Token de aplicação</b> field in the section <a href="#setting-up-itau-rede-on-vtex">Setting up Itaú Rede on VTEX</a>.
 
diff --git a/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md b/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md
index 6cd79f969..31b5f106d 100644
--- a/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md
+++ b/docs/tutorials/en/setting-up-personal-data-on-the-users-screen.md
@@ -21,18 +21,18 @@ To access it, follow the steps below:
 
 1. In the top bar of the Admin, in the right corner, click on the button with your initials;
 2. Select the __User Settings__ option.  
-![User Settings option User Management EN](//images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/f3e6f932c1db9f19103b8e0f4679e557/Op____o_Configura____es_de_usu__rio_User_Management_EN.png)
+![User Settings option User Management EN](https://images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/f3e6f932c1db9f19103b8e0f4679e557/Op____o_Configura____es_de_usu__rio_User_Management_EN.png)
 
 There are two menu options:
 
 - In __Personal__, you can see your name, your e-mail that is used in the Admin, and you can also edit your phone number.  
-![Personal Configuration User Management EN](//images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/977702361ea9b9eab8b64e5bd7136e75/Configura____o_Pessoal_User_Management_EN.png)
+![Personal Configuration User Management EN](https://images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/977702361ea9b9eab8b64e5bd7136e75/Configura____o_Pessoal_User_Management_EN.png)
 - In __Name__, you can edit your first and last name.  
-  ![Configuração Nome User Management EN](//images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/7a96df88e5d4eda5f1059efb854e7e89/Configura____o_Nome_User_Management_EN.png)
+  ![Configuração Nome User Management EN](https://images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/7a96df88e5d4eda5f1059efb854e7e89/Configura____o_Nome_User_Management_EN.png)
 In __Mobile number__, you can edit your cell phone number with the country code.  
-  ![Configuração Celular User Management EN](//images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/87437ca6668c91e16964aeb519575f03/Configura____o_Celular_User_Management_EN.png)
+  ![Configuração Celular User Management EN](https://images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/87437ca6668c91e16964aeb519575f03/Configura____o_Celular_User_Management_EN.png)
 - In __Authentication__, you can find the password options, 2-factor authentication (2FA) for your VTEX Admin login and session management. See the options in detail below.  
-![Configuration User Management Authentication EN](//images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/1fd6875c57e30b7b6957e306a3426b30/Configura____o_Autentica____o_User_Management_EN.png)
+![Configuration User Management Authentication EN](https://images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/1fd6875c57e30b7b6957e306a3426b30/Configura____o_Autentica____o_User_Management_EN.png)
 
 ## 2-step verification
 
@@ -50,4 +50,4 @@ Here you must configure the application that will provide the authentication key
 
 See in detail how to configure the application in the article on [Enabling two-factor authentication login](https://help.vtex.com/en/tutorial/habilitar-login-por-autenticacao-de-2-fatores#habilitar-o-2fa-por-aplicativo).
 
-![Configuration 2-step User Management EN](//images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/6882baabe4044696de7b6016c0397b07/Configura____o_Verifica____o_em_2_passos_User_Management_EN.png)
+![Configuration 2-step User Management EN](https://images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/6882baabe4044696de7b6016c0397b07/Configura____o_Verifica____o_em_2_passos_User_Management_EN.png)
diff --git a/docs/tutorials/en/setting-up-price-tables-for-specific-users.md b/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
index 336402697..6a411246b 100644
--- a/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
@@ -77,11 +77,11 @@ In the Admin, go to __Prices__ > __Price List__.
 
 In the search filter, enter the names of the tables created in __Master Data__.
 
-![Filters](//images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
+![Filters](https://images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
 
 Price tables are shown as columns of the price list, as are trade policies.
 
-![Prices](//images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
+![Prices](https://images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
 
 To update a fixed price in a specific table, on the column corresponding to that table, and then on __Define fixed prices__. 
 
@@ -98,7 +98,7 @@ When a user is not logged into your store, the default prices set by the trade p
 If the user is logged in, they will see the prices corresponding to the price table with which their email is associated.
 
 For example, these two clients are linked to different price tables:
-![Clients](//images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
+![Clients](https://images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
 
 When Daniel, who is linked to the Silver price table, is logged into the store, he will see the prices set on this table. The backpack in the example above will cost USD 50.00.
 
diff --git a/docs/tutorials/en/setting-up-shipment.md b/docs/tutorials/en/setting-up-shipment.md
index eae01a26d..37ebd03ce 100644
--- a/docs/tutorials/en/setting-up-shipment.md
+++ b/docs/tutorials/en/setting-up-shipment.md
@@ -27,7 +27,7 @@ The first box with a total time of __2 days__ will wait for the item represented
 
 The period considers T = 0 as the date of the order.
 
-![Configuração em estoque e entrega EN](//images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/c529a129854fed2bf8c6309e132bb0c4/Configura____o_em_estoque_e_entrega_EN.png)
+![Configuração em estoque e entrega EN](https://images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/c529a129854fed2bf8c6309e132bb0c4/Configura____o_em_estoque_e_entrega_EN.png)
 
 ## How to set up the shipment
 
diff --git a/docs/tutorials/en/setting-up-sms-password-recovery.md b/docs/tutorials/en/setting-up-sms-password-recovery.md
index 441f3a239..07c175f16 100644
--- a/docs/tutorials/en/setting-up-sms-password-recovery.md
+++ b/docs/tutorials/en/setting-up-sms-password-recovery.md
@@ -26,13 +26,13 @@ That being said, check out the step-by-step on how to set it up:
 1. Enter the __Message Center__.
 2. Click __Templates__.
 
-  ![5NrtBpFRTxInFl4aY2FrVz-en](//images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/588f1c7842ebdfce815de1890a561264/5NrtBpFRTxInFl4aY2FrVzt-en.png)
+  ![5NrtBpFRTxInFl4aY2FrVz-en](https://images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/588f1c7842ebdfce815de1890a561264/5NrtBpFRTxInFl4aY2FrVzt-en.png)
 
 3. Click on the __Password Recovery__ template.
 4. Click the __SMS__ tab.
 5. Choose the option __"Enable SMS sending?"__.
 
-  ![password-recovery-sms-tab-en](//images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/68638513852254018741915f68cfa795/password-recovery-sms-tab-en.gif)
+  ![password-recovery-sms-tab-en](https://images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/68638513852254018741915f68cfa795/password-recovery-sms-tab-en.gif)
 
   *After clicking on "Enable SMS sending", the platform presents the other sending settings.*
 
@@ -40,7 +40,7 @@ That being said, check out the step-by-step on how to set it up:
 7. Fill in the __Destination__ field with the variable `{{_accountInfo.Telephone}}`.
 8. Fill in the __Message Text__ field with the message content. The information `Name: {{name}}`, `Login: {{login}}` and `Password: {{password}}` are essential.
 
-  ![password-recovery-sms-fields-en](//images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ab09b49184ae0bc382ab26bc551d4b6e/password-recovery-sms-fields-en.png)
+  ![password-recovery-sms-fields-en](https://images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ab09b49184ae0bc382ab26bc551d4b6e/password-recovery-sms-fields-en.png)
 
 9. Review the SMS content in __Preview__.
 10. Click __Save__.
diff --git a/docs/tutorials/en/setting-up-the-css-for-the-product-zoom.md b/docs/tutorials/en/setting-up-the-css-for-the-product-zoom.md
index 5850de166..8e7888a72 100644
--- a/docs/tutorials/en/setting-up-the-css-for-the-product-zoom.md
+++ b/docs/tutorials/en/setting-up-the-css-for-the-product-zoom.md
@@ -25,7 +25,7 @@ Below we reproduce an excerpt of CSS that you can use as a starting point for th
 
 Next we are going to send the saved CSS file to the server. To do this, click on the _Configurações&gt; Portal_ menu in Admin.
 
-![](//images.contentful.com/alneenqid6w5/3uLeF6wpvq4m4Wis48eeE8/4f79bf7753fb25309b670e9ea702a3ad/configuracao_zoom.gif)
+![](https://images.contentful.com/alneenqid6w5/3uLeF6wpvq4m4Wis48eeE8/4f79bf7753fb25309b670e9ea702a3ad/configuracao_zoom.gif)
 
 In the window that opens on the right, click on **Adicionar**.
 
@@ -33,4 +33,4 @@ Then find the CSS file you saved and send it to the server, clicking on **Locali
 
 Your file will then be listed in the window, as shown below:
 
-![](//images.contentful.com/alneenqid6w5/2pWBIqL3So2wm04oU8CyQ8/ab9f623fd28f15e2708cc3fcbecafe03/gerenciador_arq_css-560x373.jpg)
+![](https://images.contentful.com/alneenqid6w5/2pWBIqL3So2wm04oU8CyQ8/ab9f623fd28f15e2708cc3fcbecafe03/gerenciador_arq_css-560x373.jpg)
diff --git a/docs/tutorials/en/setting-up-the-notify-me-option.md b/docs/tutorials/en/setting-up-the-notify-me-option.md
index d7cc3f641..99988f3a0 100644
--- a/docs/tutorials/en/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/en/setting-up-the-notify-me-option.md
@@ -23,7 +23,7 @@ When a product is out of [stock](https://help.vtex.com/en/tutorial/managing-stoc
 
 See below an example of how the **Notify me** option is displayed in a store. To receive a notification when the item is back in store, the customer must type in the name and the email in the marked fields and then click on the `Send` button.
 
-![aviseme-en](//images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/1ae27f3cae7404d1ba86d4e06c231fd6/132012045-06c65073-2692-4827-b08a-7be5730b6422.png)
+![aviseme-en](https://images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/1ae27f3cae7404d1ba86d4e06c231fd6/132012045-06c65073-2692-4827-b08a-7be5730b6422.png)
 
 As soon as the item is back in stock, the system automatically sends an email to the customer informing them that the product is available for purchase again. 
 
diff --git a/docs/tutorials/en/setting-up-the-price-range-filter.md b/docs/tutorials/en/setting-up-the-price-range-filter.md
index 9fcf7feef..89f9e775f 100644
--- a/docs/tutorials/en/setting-up-the-price-range-filter.md
+++ b/docs/tutorials/en/setting-up-the-price-range-filter.md
@@ -20,7 +20,7 @@ They are very important for browsing and searching products in the store.
 
 The registration is simple, and different price ranges may be determined for categories, as shown below:
 
-![faixa-de-preço en](//images.ctfassets.net/alneenqid6w5/1Xj5nkiiYgugKioamYQEs4/6aa1023fbcda148c33b73fa52890b1b7/faixa-de-pre__o_en.png)
+![faixa-de-preço en](https://images.ctfassets.net/alneenqid6w5/1Xj5nkiiYgugKioamYQEs4/6aa1023fbcda148c33b73fa52890b1b7/faixa-de-pre__o_en.png)
 
 In Price Ranges, click on “New Price Range” and fill in the fields below:
 
diff --git a/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
index 0777c9720..76fa6773a 100644
--- a/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
@@ -25,23 +25,23 @@ To make it easier, the entire setup in this article can be <a href="https://supp
 
 For manual configuration or editing of an existing goal, the first step is to access Analytics and click on the __Administrator__ button in the lower left corner. Then go to the __Goals__ option, from the "View" column.
 
-![image](//images.ctfassets.net/alneenqid6w5/2lSqr5sq9cEJqQ8OrYeMrO/8bb8294a785ec55c4bc812780d010377/Screenshot_2019-10-28_14.59.53.png)
+![image](https://images.ctfassets.net/alneenqid6w5/2lSqr5sq9cEJqQ8OrYeMrO/8bb8294a785ec55c4bc812780d010377/Screenshot_2019-10-28_14.59.53.png)
 
 In the goal administration screen, choose to create a new goal or to edit an existing one.
 
 __In step 1__ you can follow with a custom type goal:
 
-![image](//images.ctfassets.net/alneenqid6w5/5vv17y3LYwEZ99E531Rw8E/0e73bbfed92a27dbc893aa1ab3f6cb2e/Screenshot_2019-10-28_15.01.15.png)
+![image](https://images.ctfassets.net/alneenqid6w5/5vv17y3LYwEZ99E531Rw8E/0e73bbfed92a27dbc893aa1ab3f6cb2e/Screenshot_2019-10-28_15.01.15.png)
 
 __In step 2__ you can define the name you prefer for your goal and a position code (for internal Google Analytics use). In type, let's use "Destination":
 
-![image](//images.ctfassets.net/alneenqid6w5/3TSWIxs5EPBQAfPYY4DKeD/f937330ad2fc5496c44a58acbc05f99d/Screenshot_2019-10-28_15.03.02.png)
+![image](https://images.ctfassets.net/alneenqid6w5/3TSWIxs5EPBQAfPYY4DKeD/f937330ad2fc5496c44a58acbc05f99d/Screenshot_2019-10-28_15.03.02.png)
 
 __In step 3__ we have the most sensitive settings. In it we set the page that determines the completion of the goal and the path the clients will take to reach it.
 
 In the "Destination" field select the regular expression option and enter the URL of the order placed page: `^/checkout/orderPlaced`
 
-![image](//images.ctfassets.net/alneenqid6w5/7foRf9TbRzb0pUNlXpqATQ/593d9162dfe76f4f8ab6a59eadbb330e/Screenshot_2019-10-28_15.04.07.png)
+![image](https://images.ctfassets.net/alneenqid6w5/7foRf9TbRzb0pUNlXpqATQ/593d9162dfe76f4f8ab6a59eadbb330e/Screenshot_2019-10-28_15.04.07.png)
 
 Then configure the path that the client will go through until an order is finished. In such case, we're taking into account that the purchase process starts on the product screen; then my funnel will serve to measure the number of customers who access this screen, how many orders have been finished and at which step customers are giving up the purchase.
 
@@ -54,7 +54,7 @@ Still __in step 3__, enable the __Funnel__ option with the following steps:
 5. __Delivery__ = `^/checkout/(\?.*)?#/shipping$`
 6. __Payment__ = `^/checkout/(\?.*)?#/payment$`
 
-![image](//images.ctfassets.net/alneenqid6w5/6W1evwkmfds3ok1h8Hjzsx/da9bef2d395db2170446ebd7d1df1dda/Screenshot_2019-10-28_15.06.24.png)
+![image](https://images.ctfassets.net/alneenqid6w5/6W1evwkmfds3ok1h8Hjzsx/da9bef2d395db2170446ebd7d1df1dda/Screenshot_2019-10-28_15.06.24.png)
 
 One way to verify that the goal is set correctly is to use the "Check this goal" link. Google will generate a goal conversion simulation within the last 7 days.
 
diff --git a/docs/tutorials/en/setting-up-the-type-of-interest-rate.md b/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
index 7150488a9..82973edf4 100644
--- a/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
@@ -25,7 +25,7 @@ The payment method's ID can be configured to have Simple Interest Rates and is o
 - Select the Payment Condition that should be configured to use Simple Interest Rates
 - Copy the last URL parameter, which shows the ID of this Payment Method (see image)
 
-![ENjuros](//images.ctfassets.net/alneenqid6w5/27ScAtFzUYwYm8y5zGqsEP/ae3915ad736e96121017aba11d87a522/ENjuros.png)
+![ENjuros](https://images.ctfassets.net/alneenqid6w5/27ScAtFzUYwYm8y5zGqsEP/ae3915ad736e96121017aba11d87a522/ENjuros.png)
 
 ## Setting up the interest rate type using API
 
diff --git a/docs/tutorials/en/setting-up-the-voucher-list.md b/docs/tutorials/en/setting-up-the-voucher-list.md
index b272e4129..09fda0744 100644
--- a/docs/tutorials/en/setting-up-the-voucher-list.md
+++ b/docs/tutorials/en/setting-up-the-voucher-list.md
@@ -26,14 +26,14 @@ To create this type of list, an SKU must be set up as follows:
 - The SKU price must be R$0.01.
 - The SKU must be set up to generate a credit voucher.
 
-![sku-opção-credito-vale en](//images.ctfassets.net/alneenqid6w5/4CQusNMh8csmAs6qOkYAIi/07ea9ef632ca04b3e8b39c170732e18b/sku-op____o-credito-vale_en.png)
+![sku-opção-credito-vale en](https://images.ctfassets.net/alneenqid6w5/4CQusNMh8csmAs6qOkYAIi/07ea9ef632ca04b3e8b39c170732e18b/sku-op____o-credito-vale_en.png)
 
 
 ## List Types Settings
 
 The creation of this type of list requires that in the List Types settings the delivery is marked as “Value of products purchased will be converted into a gift card voucher”. See the example image.
 
-![entrega-tipos-lista en](//images.ctfassets.net/alneenqid6w5/3WBtZ9m8zSsUmaIgYaIUSq/00be0c7191f283fa2f4ef1abdab917b6/entrega-tipos-lista_en.png)
+![entrega-tipos-lista en](https://images.ctfassets.net/alneenqid6w5/3WBtZ9m8zSsUmaIgYaIUSq/00be0c7191f283fa2f4ef1abdab917b6/entrega-tipos-lista_en.png)
 
 
 Save your list after you have defined all settings.
diff --git a/docs/tutorials/en/setting-up-vtex-instore-logistics.md b/docs/tutorials/en/setting-up-vtex-instore-logistics.md
index c87b31785..5afb16eea 100644
--- a/docs/tutorials/en/setting-up-vtex-instore-logistics.md
+++ b/docs/tutorials/en/setting-up-vtex-instore-logistics.md
@@ -21,6 +21,6 @@ The check-in route of the Checkout calls Logistics in its flow. What does this m
 
 After registering your stores on MasterData ([see here how to do this](/en/tutorial/how-to-register-a-store-in-vtex-instore)), you can choose the store you would like to associate with this dock, as shown in the image below:
 
-![2017-06-16 16 43 14-VTEX - Logística](//images.contentful.com/alneenqid6w5/2NIbvde6HSK6OUCWUcwigq/879c7de324037ebb2ffbc64d768d7404/2017-06-16_16_43_14-VTEX_-_Log__stica.png)
+![2017-06-16 16 43 14-VTEX - Logística](https://images.contentful.com/alneenqid6w5/2NIbvde6HSK6OUCWUcwigq/879c7de324037ebb2ffbc64d768d7404/2017-06-16_16_43_14-VTEX_-_Log__stica.png)
 
 For each registered store, a corresponding dock should exist.
diff --git a/docs/tutorials/en/sharing-your-store-access-to-google-webmaster-tools.md b/docs/tutorials/en/sharing-your-store-access-to-google-webmaster-tools.md
index de482e927..193ab1376 100644
--- a/docs/tutorials/en/sharing-your-store-access-to-google-webmaster-tools.md
+++ b/docs/tutorials/en/sharing-your-store-access-to-google-webmaster-tools.md
@@ -19,18 +19,18 @@ For our consultancy and operations teams to do a better job and give you better
 
 After accessing your account, you will be directed to the list of your websites; so, just select the website whose access you intend to share by clicking on your website link.
 
-![web1](//images.contentful.com/alneenqid6w5/3sjO5gPjcA2uCms8KskmU4/484df9e2d251c709169c88a626e2b575/web1.png)
+![web1](https://images.contentful.com/alneenqid6w5/3sjO5gPjcA2uCms8KskmU4/484df9e2d251c709169c88a626e2b575/web1.png)
 
 Now, go to the admin panel of our page. There are several options available on the left-side menu, however, to share the access, you must select the gear icon on the top menu, and click on **Site users and owners.**
 
-![web2](//images.contentful.com/alneenqid6w5/kk9u4aygFyAG4EkKsYIw0/67bd8a6966fafea49f6c50f81d36c49d/web2.png)
+![web2](https://images.contentful.com/alneenqid6w5/kk9u4aygFyAG4EkKsYIw0/67bd8a6966fafea49f6c50f81d36c49d/web2.png)
 
 The list of users already authorized to access the website will be displayed; then, in order to add a new user, just click on the top of the screen on the **Add New User** button.
 
-![web3](//images.contentful.com/alneenqid6w5/1MLOKUoQliKsMc88EQUcmK/3e7dc118b07c2f23282ba48e63c1aee0/web3.png)
+![web3](https://images.contentful.com/alneenqid6w5/1MLOKUoQliKsMc88EQUcmK/3e7dc118b07c2f23282ba48e63c1aee0/web3.png)
 
 Then, a pop-up will be displayed requesting information about the e-mail of the user that will be added, and the type of authorization &#8211; full or restricted – that the user will have.
 
-![web4](//images.contentful.com/alneenqid6w5/hINzOyisNy0GyaMSOMEMq/b629abc8ff70a3820ab37f8a57f974e2/web4.png)
+![web4](https://images.contentful.com/alneenqid6w5/hINzOyisNy0GyaMSOMEMq/b629abc8ff70a3820ab37f8a57f974e2/web4.png)
 
 Do not forget to click on **Add** to save the information.
diff --git a/docs/tutorials/en/shipping-options-beta.md b/docs/tutorials/en/shipping-options-beta.md
index 041b7bf3c..becc474d3 100644
--- a/docs/tutorials/en/shipping-options-beta.md
+++ b/docs/tutorials/en/shipping-options-beta.md
@@ -93,7 +93,7 @@ Follow the steps below to create a shipping option:
     - **Free shipping:** Free of charge for the consumer; no additional configuration is required.
 8. Click `Save`.
 
-![opcoes_envio_criacao_en](//images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/3f6e3be89d0d3b4c22216df25aa2c875/opcoes_envio_criacao_en.png)
+![opcoes_envio_criacao_en](https://images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/3f6e3be89d0d3b4c22216df25aa2c875/opcoes_envio_criacao_en.png)
 
 ## Editing a shipping option
 
@@ -117,7 +117,7 @@ Besides editing a shipping option from the menu icon <i class="fas fa-ellipsis-v
 
 Once you have configured the shipping options, they will be listed under **Store Settings > Shipping > Shipping Options**, as shown in the following image:
 
-![opcoes_envio_listagem_en](//images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/7c6c0928864ee46602bdf7799c9f00b1/opcoes_envio_listagem_en.png)
+![opcoes_envio_listagem_en](https://images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/7c6c0928864ee46602bdf7799c9f00b1/opcoes_envio_listagem_en.png)
 
 The table below contains the description of the columns shown:
 
diff --git a/docs/tutorials/en/shipping-policy.md b/docs/tutorials/en/shipping-policy.md
index b93d62436..a2a6916b5 100644
--- a/docs/tutorials/en/shipping-policy.md
+++ b/docs/tutorials/en/shipping-policy.md
@@ -23,7 +23,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 The image below shows how these concepts relate to each other:
 
-![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
+![shipping_strategy_EN](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
 
 **Shipping policy** is a set of rules and settings that specify the shipping options that will be displayed to customers at checkout. When calculating the [shipping time for an order](https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116), the VTEX platform takes into account several settings from the shipping policy, including:
 
diff --git a/docs/tutorials/en/shipping-rate-template.md b/docs/tutorials/en/shipping-rate-template.md
index 1d19bca35..46540cf9c 100644
--- a/docs/tutorials/en/shipping-rate-template.md
+++ b/docs/tutorials/en/shipping-rate-template.md
@@ -179,7 +179,7 @@ We used the term "weight" when referring to "mass" in this documentation for rea
 </div>
 
 Here is an example of how to fill in the fields in the spreadsheet.
-![modelo_planilhanumerica](//images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
+![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
 
 ## Upload the spreadsheet in VTEX Admin
 
@@ -192,7 +192,7 @@ Follow the steps below:
 4. In both cases, download the spreadsheet and [complete its fields](#fill-in-the-fields-in-the-spreadsheet). Then, upload the file in the **Upload shipping rates** section, as illustrated in the image below.
 5. After completing these steps, click on `Save changes`.
 
-![upload tarifas envioEN](//images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/38cfc78b89a4e0e68bfec882af0ea9f4/upload_tarifas_envioEN.png)
+![upload tarifas envioEN](https://images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/38cfc78b89a4e0e68bfec882af0ea9f4/upload_tarifas_envioEN.png)
 
 <div class="alert alert-warning">
 For <b>new</b> shipping policies, other steps are required. Check out the article <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy</a> for more information.
diff --git a/docs/tutorials/en/shipping-rates.md b/docs/tutorials/en/shipping-rates.md
index 24aa4d24b..c9aeb74d5 100644
--- a/docs/tutorials/en/shipping-rates.md
+++ b/docs/tutorials/en/shipping-rates.md
@@ -21,7 +21,7 @@ Shipping rates are the shipping options your store offers to customers, and they
 The <a href="https://help.vtex.com/en/tutorial/total-shipping-cost--5bwhIO108VA5Y2YOpef9lV">total shipping cost</a> to the customer includes the shipping rate, <a href="https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV">additional shipping costs</a> and, a loading dock fee.
 </div>
 
-![Tarifa envio EN](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
+![Tarifa envio EN](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
 
 You can add shipping rates in the Admin by using:
 
diff --git a/docs/tutorials/en/shipping-strategy.md b/docs/tutorials/en/shipping-strategy.md
index d46e3627d..c4aca929d 100644
--- a/docs/tutorials/en/shipping-strategy.md
+++ b/docs/tutorials/en/shipping-strategy.md
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 The shipping strategy refers to the relationship between inventory, loading dock and shipping policy. The way they communicate will define the structure combination for shipping your customers’ orders. 
 
-![shipping_strategy_EN](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
+![shipping_strategy_EN](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/9f3db7829e85f1c910daf1b81bacd127/shipping_strategy_EN.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
    <tr class="bb b--muted-3">
diff --git a/docs/tutorials/en/site-editor-overview.md b/docs/tutorials/en/site-editor-overview.md
index b1cc2d9d5..411e6ca17 100644
--- a/docs/tutorials/en/site-editor-overview.md
+++ b/docs/tutorials/en/site-editor-overview.md
@@ -23,7 +23,7 @@ Site Editor is a graphical interface for managing your storefront content. It al
 
 In your VTEX Admin, access **Storefront > Site Editor** and you’ll see the main tools available in the graphical interface.
 
-![Site Editor - EN](//images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/216b3664d5d3f8b6d901a0b8cf427906/site-editor-ui-en.png)
+![Site Editor - EN](https://images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/216b3664d5d3f8b6d901a0b8cf427906/site-editor-ui-en.png)
 
 | **Tool**    | **Description** |
 | ----------  | ----------    |
diff --git a/docs/tutorials/en/sku-bindings.md b/docs/tutorials/en/sku-bindings.md
index 2e08621d7..f0e862f1e 100644
--- a/docs/tutorials/en/sku-bindings.md
+++ b/docs/tutorials/en/sku-bindings.md
@@ -27,7 +27,7 @@ By default, <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlG
 
 The **SKU Bindings** page allows the marketplace to track and manage the binding relationship between the seller’s SKUs and the ones from the marketplace. To access the page, go to the VTEX Admin, **Marketplace > Sellers > SKU Bindings**. You'll see the following interface:
 
-![sku-bindings-en](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/9a76d4471db1707286f7464e19cadcb8/sku-bindings-en.png)
+![sku-bindings-en](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/9a76d4471db1707286f7464e19cadcb8/sku-bindings-en.png)
 
 The following table contains a description of the columns in the SKU binding list:
 
diff --git a/docs/tutorials/en/special-conditions.md b/docs/tutorials/en/special-conditions.md
index 028f18ebf..d3aba478b 100644
--- a/docs/tutorials/en/special-conditions.md
+++ b/docs/tutorials/en/special-conditions.md
@@ -19,7 +19,7 @@ Special conditions are part of the configuration of payment conditions which all
 
 To identify the special conditions applicable to each payment method, in the VTEX Admin, access  __Payments > Settings > Payment Conditions__, select the desired payment method and check the options as shown in the illustration below.
 
-![special payment conditions](//images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/5f674ce32524424a33df81b671e04e5c/Special_payment_conditions.png)
+![special payment conditions](https://images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/5f674ce32524424a33df81b671e04e5c/Special_payment_conditions.png)
 
 ## Commercial condition
 
@@ -29,7 +29,7 @@ To learn how to add a new commercial condition, and link it to a SKU, read the d
 
 ## How to configure a commercial condition on the payment condition
 
-![condicao-comercial en](//images.ctfassets.net/alneenqid6w5/2YSz1udqP6YCgSQ6u2c8II/1b9ec111a6f65a1a254908fd141a97f7/commercial-condition.png)
+![condicao-comercial en](https://images.ctfassets.net/alneenqid6w5/2YSz1udqP6YCgSQ6u2c8II/1b9ec111a6f65a1a254908fd141a97f7/commercial-condition.png)
 
 1. Inside the payment condition, click on `Add special condition`.
 3. Then, click on `Commercial Condition`.
@@ -89,7 +89,7 @@ Allows a payment condition to be applied to a specific trade policy, or as many
 
 How to configure a trade policy for the payment condition
 
-![politica-comercial en](//images.ctfassets.net/alneenqid6w5/4FEkjd6rSMuA6mKOQ6O0aC/3d100357b97b18b7f073adc686ad0a1a/sales-policy.png)
+![politica-comercial en](https://images.ctfassets.net/alneenqid6w5/4FEkjd6rSMuA6mKOQ6O0aC/3d100357b97b18b7f073adc686ad0a1a/sales-policy.png)
 
 1. Inside Payment Conditions, click on `Add special condition`.
 3. Then, click on `Trade Policy (Sales Channel)`.
@@ -114,7 +114,7 @@ How to configure the issuing bank in the payment condition
 6. If you want to segment by co-brand, select the desired option in __Co-brand__ (this box will only appear if VTEX was made aware of the co-brand card list beforehand).
 7. Save changes.
 
-![banco-emissor en](//images.ctfassets.net/alneenqid6w5/6q6yz9BnLaAkCCkCOy2EYS/9129d3e6448169fa3f940b627a31160c/issuing-bank.png)
+![banco-emissor en](https://images.ctfassets.net/alneenqid6w5/6q6yz9BnLaAkCCkCOy2EYS/9129d3e6448169fa3f940b627a31160c/issuing-bank.png)
 
 ### Examples
 
@@ -146,7 +146,7 @@ Allow you to set up an expiration date for the payment condition, so that its ap
 
 How to configure the payment condition period:
 
-![periodo en](//images.ctfassets.net/alneenqid6w5/1SHkE4MhWYke8YAuiu0gii/cebe25c6535946b788e28bd24afa3c18/period.png)
+![periodo en](https://images.ctfassets.net/alneenqid6w5/1SHkE4MhWYke8YAuiu0gii/cebe25c6535946b788e28bd24afa3c18/period.png)
 
 1. In Payment Conditions, click on `Add special condition`.
 2. Then, click on `Period`.
diff --git a/docs/tutorials/en/split-payment.md b/docs/tutorials/en/split-payment.md
index 31eaf9783..1dd91166e 100644
--- a/docs/tutorials/en/split-payment.md
+++ b/docs/tutorials/en/split-payment.md
@@ -55,11 +55,11 @@ For example, a shopper adds two products to the same shopping cart. One of them
 
 __The payment is distributed as follows:__
 
-![Payout Split](//images.ctfassets.net/alneenqid6w5/2Pqz4t4XkfA1WGZOi1VCX0/1694e5c9947473a360e50010881fee70/PAYOUT.png)
+![Payout Split](https://images.ctfassets.net/alneenqid6w5/2Pqz4t4XkfA1WGZOi1VCX0/1694e5c9947473a360e50010881fee70/PAYOUT.png)
 
 As you can see, our Gateway calculates and distributes payouts for each recipient when the order is invoiced and sends that info to the payment provider. The distribution is done according to the amount destined to each merchant in the order and the commissions taken by the marketplace.
 
-![Receivables](//images.ctfassets.net/alneenqid6w5/1rJ1dG3TMX9UqjPr5H4GMR/1b024e71291ab003f9b6379d0ffcecca/RECEBIVEIS.png)
+![Receivables](https://images.ctfassets.net/alneenqid6w5/1rJ1dG3TMX9UqjPr5H4GMR/1b024e71291ab003f9b6379d0ffcecca/RECEBIVEIS.png)
 
 Our __Payout Split__ solution has some limitations that are important to consider:
 
@@ -86,11 +86,11 @@ Meaning that the marketplace has less control over the payment flow. Unlike the
 
 For example, a shopper adds two products to the same shopping cart. One of them will be fulfilled by the marketplace itself and the other one belongs to a seller called __Seller A__.
 
-![Transaction Split](//images.ctfassets.net/alneenqid6w5/3uiBeqiyYlaneMksnW4G0v/8a47d871bdc64ccec3d812b4449b053e/TRANSACTION.png)
+![Transaction Split](https://images.ctfassets.net/alneenqid6w5/3uiBeqiyYlaneMksnW4G0v/8a47d871bdc64ccec3d812b4449b053e/TRANSACTION.png)
 
 In the __Transaction Split__, the marketplace has no need to make any configuration. The seller is the one that needs to configure their own payment method in the affiliation with a given marketplace. Check our documentation [Send the Seller White Label payment methods to the Marketplace](https://help.vtex.com/en/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW) for more details. 
 
-![Report](//images.ctfassets.net/alneenqid6w5/3YX8MmCPvAWyJpZ7tFAHt4/7276a3b6c1ff1cf1d4d6fe5ccd7bdba9/REPORT.png)
+![Report](https://images.ctfassets.net/alneenqid6w5/3YX8MmCPvAWyJpZ7tFAHt4/7276a3b6c1ff1cf1d4d6fe5ccd7bdba9/REPORT.png)
 
 The transaction split has a few __limitations__ that must be taken into account:
 
diff --git a/docs/tutorials/en/store-access-permission.md b/docs/tutorials/en/store-access-permission.md
index bae7bfe1a..23fef3b1c 100644
--- a/docs/tutorials/en/store-access-permission.md
+++ b/docs/tutorials/en/store-access-permission.md
@@ -25,4 +25,4 @@ To configure this feature in your store, access the Admin and follow the instruc
 4. Select the __VTEX Store__ option.
 5. Check the box next to __"Enables B2B behavior"__ and save the changes.
 
-![Enable B2B scenario](//images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
+![Enable B2B scenario](https://images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
diff --git a/docs/tutorials/en/store-overview-beta.md b/docs/tutorials/en/store-overview-beta.md
index c902edbf5..a9e6e56e4 100644
--- a/docs/tutorials/en/store-overview-beta.md
+++ b/docs/tutorials/en/store-overview-beta.md
@@ -23,7 +23,7 @@ The Store Overview (Beta) page in your VTEX Admin provides real-time tracking of
 
 This tool is available on the homepage of the VTEX Admin. To view it, click **Dashboards > Overview** in the navigation menu, or type _Overview_ in the search bar at the top of the page.
 
-![EN visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/88b40023b0c9d38dae93d2ccb563e378/EN_visa__o_geral_beta.png)
+![EN visão geral beta](https://images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/88b40023b0c9d38dae93d2ccb563e378/EN_visa__o_geral_beta.png)
 
 In this article, we describe the main page sections and actions. You will learn more about:
 
@@ -77,7 +77,7 @@ If you want to analyze the results generated by campaigns, promotions, or new pr
 3. Select the `Accumulated` [view](#views).
 4. Track the hourly performance of metrics.
 
-![EN visão geral Beta acumulado](//images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/787362a926aa9a3b503353d1f691fd49/EN_visa__o_geral_Beta_acumulado.png)
+![EN visão geral Beta acumulado](https://images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/787362a926aa9a3b503353d1f691fd49/EN_visa__o_geral_Beta_acumulado.png)
 
 ### Tracking the impact of changes in the store
 
@@ -90,7 +90,7 @@ If you want to see the impact of store changes, either to identify negative effe
 3. Check the pulse of the metrics or inflection points in the chart in the last two hours.
 4. [Compare the times](#comparing-periods) of the inflection points with the applied changes to identify their cause and impact.
 
-![EN visão geral Beta ultimas duas horas](//images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/b0d5752df79f525b07d023b5e984fd18/EN_visa__o_geral_Beta_ultimas_duas_horas.png)
+![EN visão geral Beta ultimas duas horas](https://images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/b0d5752df79f525b07d023b5e984fd18/EN_visa__o_geral_Beta_ultimas_duas_horas.png)
 
 ## Comparing periods
 
@@ -133,7 +133,7 @@ The table below describes the charts included in the _Monitoring_ section of the
 
 ## Metrics
 
-![EN visão geral Beta metricas](//images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/479e453368ec833c2c88109f606ae488/EN_visa__o_geral_Beta_metricas.png)
+![EN visão geral Beta metricas](https://images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/479e453368ec833c2c88109f606ae488/EN_visa__o_geral_Beta_metricas.png)
 
 The table below describes the metrics available on the home dashboard. All metrics are related to purchase flows in VTEX stores during the selected period.
 
diff --git a/docs/tutorials/en/store-overview.md b/docs/tutorials/en/store-overview.md
index 65561d1ff..98fcd956c 100644
--- a/docs/tutorials/en/store-overview.md
+++ b/docs/tutorials/en/store-overview.md
@@ -17,7 +17,7 @@ subcategory: 1TIJqw8kV2Yok4iQe4SAkq
 
 VTEX Admin’s Overview page is where store owners can get a quick overview of key metrics that impact the store’s revenue. Through this dashboard, you can track the evolution of your sales through order trend analysis, conversion rate and sales funnel charts. You can access this tool in the VTEX Admin, by clicking on **Dashboards > Overview** in the navigation menu, or type *Overview* in the search bar at the top of the page.
 
-![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
  The Overview page provides a summary of your business with VTEX. For deeper analysis of your store's metrics, visit [Sales Performance](https://help.vtex.com/en/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp).
 
@@ -55,7 +55,7 @@ To compare data from different periods, on the top of the page, select the date
 
 ## Metrics
 
-![Store overview Metricas EN](//images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/e607a9f5f31572420c0e149195f17f3a/Metricas_EN.png)
+![Store overview Metricas EN](https://images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/e607a9f5f31572420c0e149195f17f3a/Metricas_EN.png)
 The table below describes the key metrics available in the homepage dashboard. All metrics refer to purchase flows made in VTEX stores in a given time frame.
 
 | Metric                               | Description                                                                                                                                                                                                                                                                               |
@@ -69,7 +69,7 @@ The table below describes the key metrics available in the homepage dashboard. A
 | Orders in the past hour              | Orders placed in your store in the past hour. By clicking on this metric, you are redirected to the All Orders page.                                                                                                                                                                      |
 
 ## Highest grossing products
-![Store overview Growing products PT](//images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/12b76c6938510fc269a4fe561021690a/Store_overview_Growing_products_EN.jpg)  
+![Store overview Growing products PT](https://images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/12b76c6938510fc269a4fe561021690a/Store_overview_Growing_products_EN.jpg)  
 
 This component lists your highest grossing products and products with the highest number of units sold in the selected period. 
 
@@ -80,16 +80,16 @@ Know more about the metrics:
 - __Highest sold units products:__ the products with most units sold in the selected period. This list shows the quantity of sold units, and a percentage indicating the increase or decrease in sold units, comparing the selected periods.
 
 ## Performed orders
-![Store overview Pedidos realizados EN](//images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/b10ae305893dc43f313b412731c7d356/Pedidos_realizados_EN.png)
+![Store overview Pedidos realizados EN](https://images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/b10ae305893dc43f313b412731c7d356/Pedidos_realizados_EN.png)
 
 This chart displays the number of orders that were received by your store in the selected period. The thick blue line represents the orders placed in the more recent period. The thin gray line represents the orders placed in the period selected for comparison. By hovering the mouse over the chart, the number of orders captured at a specific time is displayed.
 
 ## Canceled orders
-![Store overview Pedidos cancelados EN](//images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/fff4e13c813fd3daf99aa0cd839a2259/Pedidos_cancelados_EN.png)
+![Store overview Pedidos cancelados EN](https://images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/fff4e13c813fd3daf99aa0cd839a2259/Pedidos_cancelados_EN.png)
 This chart displays the number of orders that have been canceled in your store in the selected period. The thick blue line represents the orders canceled in the more recent period. The thin gray line represents the orders canceled in the period selected for comparison. By hovering the mouse over the chart, the number of canceled orders at a specific time is displayed.  
 
 ## Order trend analysis
-![Store overview Order trend EN](//images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/694055732b0c694049732420163291a8/Store_overview_Order_trend_EN.jpg)  
+![Store overview Order trend EN](https://images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/694055732b0c694049732420163291a8/Store_overview_Order_trend_EN.jpg)  
 
 This chart shows your store’s order trend, indicating the number of orders placed by shoppers in the selected period.
 
@@ -98,13 +98,13 @@ The line indicates the order curve for the selected period. By hovering the mous
 The number shown on top of the chart refers to the orders placed in the last hour and it is updated every five minutes.  The label on top of the chart indicates whether orders are being placed at a `normal`, `low` or `high` rate when compared to your store’s usual performance for that period. 
 
 ## Conversion rate
-![Store overview Conversion rate EN](//images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/f6435fce96325abc0e8c4f11021234bf/Store_overview_Conversion_rate_EN.jpg)  
+![Store overview Conversion rate EN](https://images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/f6435fce96325abc0e8c4f11021234bf/Store_overview_Conversion_rate_EN.jpg)  
 
 This chart shows your store’s conversion rate in the selected periods you wish to compare. The conversion rate is calculated by dividing the total number of orders by the total number of sessions in your store. The thick blue line indicates the conversion rate for the most recent period. The thin blue line indicates the conversion rate for the the period selected for comparison. The chart also indicates the percentage (%) and percentual points (p.p) of increase or decrease for this metric. By hovering the mouse over the chart, you can see the value of that metric at specific times. 
 
 ## Sales funnel
 
-![Store overview sales funnel EN](//images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/a477554ecdb6d2e8eccc427f06503b2b/Store_overview_sales_funnel_EN.jpg)  
+![Store overview sales funnel EN](https://images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/a477554ecdb6d2e8eccc427f06503b2b/Store_overview_sales_funnel_EN.jpg)  
 
 This chart allows you to track the volume of sessions in the intermediate stages of the purchase flow and view opportunities for optimizing the store's conversion rate. The table below describes the intermediate stages of the purchase flow.
 
@@ -120,7 +120,7 @@ This chart allows you to track the volume of sessions in the intermediate stages
 Each blue bar in the chart represents the volume of sessions that have reached a certain stage of the purchase flow. This volume is represented as an absolute value (above), and as a percentage of the number of sessions (below), together with the percentual points (p.p) of increase or decrease in the sales funnel. By hovering the mouse over the percentage, you can view more details about that intermediate stage.
 
 ## Highest grossing categories
-![Categorias EN](//images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/0bd3ce0bde40ba19ea5f6c246236878f/Categorias_EN.png)
+![Categorias EN](https://images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/0bd3ce0bde40ba19ea5f6c246236878f/Categorias_EN.png)
 
 This chart indicates the ten categories in your store which generated the most revenue in the selected period. The blue bar indicates the revenue generated on the most recent date. The gray bar indicates the revenue generated on the period selected for comparison. By hovering the mouse over the chart, the conversion rate for each compared period is displayed. 
 By clicking on the chart title it is possible to change the view to __Highest sold categories by orders__.
diff --git a/docs/tutorials/en/structured-data-through-google-search-console-data-markers.md b/docs/tutorials/en/structured-data-through-google-search-console-data-markers.md
index b4d6ecf81..978002788 100644
--- a/docs/tutorials/en/structured-data-through-google-search-console-data-markers.md
+++ b/docs/tutorials/en/structured-data-through-google-search-console-data-markers.md
@@ -66,15 +66,15 @@ With this type of information, users are able to send to Google information abou
 
 **
 ****Step 1**
-****![](//images.contentful.com/alneenqid6w5/2auEIkvBGMO8gqWqgA4u8q/0c53485d350f622ae184852c88688f0c/marcadordedados_step1.gif)****
+****![](https://images.contentful.com/alneenqid6w5/2auEIkvBGMO8gqWqgA4u8q/0c53485d350f622ae184852c88688f0c/marcadordedados_step1.gif)****
 
 ****Step 2****
 
-****![](//images.contentful.com/alneenqid6w5/62T28aRiUM0cOwOmiOQ2UA/8584923dd2b3c1f9f9bc7a782caee223/marcadordedados_step2_url_type.gif)****
+****![](https://images.contentful.com/alneenqid6w5/62T28aRiUM0cOwOmiOQ2UA/8584923dd2b3c1f9f9bc7a782caee223/marcadordedados_step2_url_type.gif)****
 
 ****Step 3****
 
-****![](//images.contentful.com/alneenqid6w5/5YhbETD9mMMgsAeKGE2SMG/622bccd0df4e05462f7db9ae7bb05cf9/marcadordedados_step3_markup_business.gif)****
+****![](https://images.contentful.com/alneenqid6w5/5YhbETD9mMMgsAeKGE2SMG/622bccd0df4e05462f7db9ae7bb05cf9/marcadordedados_step3_markup_business.gif)****
 
 ## Products
 
@@ -94,11 +94,11 @@ With this type of information, users are able to send to Google information abou
 
 **** Step 1****
 
-****![](//images.contentful.com/alneenqid6w5/5ARq4O3nna8gqGM8KasC4K/57999e6c592e985550758aaab1c15c06/marcadordedados_step2_url_type_product.gif)****
+****![](https://images.contentful.com/alneenqid6w5/5ARq4O3nna8gqGM8KasC4K/57999e6c592e985550758aaab1c15c06/marcadordedados_step2_url_type_product.gif)****
 
 ****Step 2****
 
-****![](//images.contentful.com/alneenqid6w5/1TNyUZzqLSOOO48gmCOQ26/d78f4f460a7d6caf864498db7f1ce2b2/marcadordedados_step3_markup_product.gif)****
+****![](https://images.contentful.com/alneenqid6w5/1TNyUZzqLSOOO48gmCOQ26/d78f4f460a7d6caf864498db7f1ce2b2/marcadordedados_step3_markup_product.gif)****
 
 ****Step 3****
 
diff --git a/docs/tutorials/en/styles-overview.md b/docs/tutorials/en/styles-overview.md
index 8e75345b8..552c620e6 100644
--- a/docs/tutorials/en/styles-overview.md
+++ b/docs/tutorials/en/styles-overview.md
@@ -19,7 +19,7 @@ The **Styles** page allows you to define the typography and color palette of you
 
 To access it, log in to VTEX Admin, access **Storefront > Styles**, and check out the main tools available in the interface.
 
-![Styles - Overview](//images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/f87ba6014f0f8bee71aedf4b7c24c66b/EN.png)
+![Styles - Overview](https://images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/f87ba6014f0f8bee71aedf4b7c24c66b/EN.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   To apply and preview the changes in your store's styles, make sure to use a workspace that supports production traffic, i.e., <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace)">production workspaces</a>. 
diff --git a/docs/tutorials/en/subscription-plans.md b/docs/tutorials/en/subscription-plans.md
index df3e99994..5895aeca2 100644
--- a/docs/tutorials/en/subscription-plans.md
+++ b/docs/tutorials/en/subscription-plans.md
@@ -21,7 +21,7 @@ To offer subscription plans for your customers, you need to install the Subscrip
 
 On the **Plans** page, you can view and manage the subscription plans available to your customers, as illustrated below.
 
-![planslist EN](//images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/0355551976bbb3465d4ddad5ca8cd254/planslist_EN.png)
+![planslist EN](https://images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/0355551976bbb3465d4ddad5ca8cd254/planslist_EN.png)
 
 Here are the main features of this page:
 
diff --git a/docs/tutorials/en/synonym-list.md b/docs/tutorials/en/synonym-list.md
index a3b283cc5..7aa517732 100644
--- a/docs/tutorials/en/synonym-list.md
+++ b/docs/tutorials/en/synonym-list.md
@@ -17,7 +17,7 @@ subcategory: BBzMtJan1UTxC9QZODnlN
 
 The **Synonyms** page allows you to view and manage all Intelligent Search [synonyms](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) added to your store. You can access it in the VTEX Admin by clicking **Storefront > Intelligent Search > Synonyms**.
 
-![lista-sinonimos-en](//images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/7803ace6dbfd3804a8decfa1081ee08e/lista-sinonimos-en.PNG)
+![lista-sinonimos-en](https://images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/7803ace6dbfd3804a8decfa1081ee08e/lista-sinonimos-en.PNG)
 
 The page displays the following information in a table: 
 
diff --git a/docs/tutorials/en/telesales-toolbar.md b/docs/tutorials/en/telesales-toolbar.md
index c1d99be78..5bf3c84ed 100644
--- a/docs/tutorials/en/telesales-toolbar.md
+++ b/docs/tutorials/en/telesales-toolbar.md
@@ -19,7 +19,7 @@ The telesales toolbar is displayed at the top of your store's website for users
 
 Once the registered operator logs into the store environment, the toolbar will be displayed at the top of all sections of the website.
 
-![toolbartelevendas EN](//images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ab7894a0dc03568e5e1745a0adbec2f3/toolbartelevendas_EN.png)
+![toolbartelevendas EN](https://images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ab7894a0dc03568e5e1745a0adbec2f3/toolbartelevendas_EN.png)
 
 See below the main features of the telesales toolbar:
 *   [Log in as customer](#log-in-as-customer)
diff --git a/docs/tutorials/en/testing-webservice-using-soapui.md b/docs/tutorials/en/testing-webservice-using-soapui.md
index eabbe036b..8ad5143fe 100644
--- a/docs/tutorials/en/testing-webservice-using-soapui.md
+++ b/docs/tutorials/en/testing-webservice-using-soapui.md
@@ -33,11 +33,11 @@ The step-by-step utilization is as follows:
  
 Substitute the value {STORENAME} with the name of your store.
 
-![](//images.contentful.com/alneenqid6w5/WMZnCJCLg2WGSIesMOMKu/efed51a5c0e151d1ac1f7902600e522a/1.png)
+![](https://images.contentful.com/alneenqid6w5/WMZnCJCLg2WGSIesMOMKu/efed51a5c0e151d1ac1f7902600e522a/1.png)
 
 Log in using the data of the webservice desired. After logging in, you will view all the methods to be found in the [Web Service manual](/en/tutorial/manual-of-classes-and-methods-used-on-webservice/)
 
-![](//images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
+![](https://images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
 
 1. Locate the desired method. e.g.: the ImageInsertUpdate method, which is the method used for adding images;
 2. Fill out the fields referring to the method (these fields are the ImageDTO type, references are in the manual);
diff --git a/docs/tutorials/en/total-shipping-cost.md b/docs/tutorials/en/total-shipping-cost.md
index f87eedf91..70983c834 100644
--- a/docs/tutorials/en/total-shipping-cost.md
+++ b/docs/tutorials/en/total-shipping-cost.md
@@ -31,7 +31,7 @@ See how they are calculated:
 
 So, in general, the total shipping cost is calculated as follows:
 
-![Custo-final-envio-EN](//images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/4b04d0319eb18cd1ee0e9c03858c5bc1/Custo-final-envio-EN.svg)
+![Custo-final-envio-EN](https://images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/4b04d0319eb18cd1ee0e9c03858c5bc1/Custo-final-envio-EN.svg)
 
 <div class="alert alert-danger">
 If the <b>price-based charge</b> is lower than the <b>insurance charge</b>, the system only considers the insurance charge. The price-based charge will not be taken into account for the total shipping cost.<p>
diff --git a/docs/tutorials/en/transaction-flow-in-payments.md b/docs/tutorials/en/transaction-flow-in-payments.md
index c3db48557..e97a58577 100644
--- a/docs/tutorials/en/transaction-flow-in-payments.md
+++ b/docs/tutorials/en/transaction-flow-in-payments.md
@@ -19,7 +19,7 @@ Transactions performed by VTEX Payments go through a variety of statuses, from t
 
 See below an example timeline with the transaction statuses.
 
-![Transaction Flow](//images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
+![Transaction Flow](https://images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
 
 1. __Authorizing__: This is the first status of a Payments transaction. At this stage, Payments indicates that the process of sending information to an acquirer or to another gateway has begun.
 2. __Authorized__: Upon initiation of the authorization process, the acquirer or other gateway sends the transaction information to the issuing bank. The bank responds whether or not the transaction should be authorized. If it denies the transaction, the payment is __canceled__. If it authorizes, the transaction status changes to __Authorized__.
diff --git a/docs/tutorials/en/transactions-events.md b/docs/tutorials/en/transactions-events.md
index 16464b342..d3188071e 100644
--- a/docs/tutorials/en/transactions-events.md
+++ b/docs/tutorials/en/transactions-events.md
@@ -31,14 +31,14 @@ Below are examples of where to find the most common information to analyze the s
 
 In this event, we see that VTEX began the authorization process with the payment gateway and sent the response that the operation may begin:
 
-![transação-autorizando](//images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
+![transação-autorizando](https://images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
 
 
 ## Transaction authorized and approved
 
 After an authorization request, the gateway will authorize/pre-authorize the transaction in case of success in the flow. With its authorization, the transaction status will become _approved_ and the order flow will be able to continue:
 
-![transação-autorizada-aprovada](//images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
+![transação-autorizada-aprovada](https://images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
 
 If the authorization doesn't happen due to an issue from outside the flow, the details will be logged in the timeline, according to the information returned by the payment gateway.
 
@@ -46,7 +46,7 @@ If the authorization doesn't happen due to an issue from outside the flow, the d
 
 In the order flow, you can send the payment to an anti-fraud (directly integrated into VTEX) in order to have a risk analysis. Once you have requested an analysis, the order will have a status indicating the start of the analysis and the return of the anti-fraud, along with the result:
 
-![transação -antifraude](//images.contentful.com/alneenqid6w5/3MjNaFOEJyiumaUyO2owSa/84130c11335612c4d982c016cc160616/transaccion-antifraude.png)
+![transação -antifraude](https://images.contentful.com/alneenqid6w5/3MjNaFOEJyiumaUyO2owSa/84130c11335612c4d982c016cc160616/transaccion-antifraude.png)
 
 If the analysis doesn't happen due to an issue from outside the flow, the details will be logged in the timeline, according to the information returned by the payment gateway.
 
@@ -56,11 +56,11 @@ When the transaction pre-authorization mode is used, after having performed the
 
 When the capture process is started, the _Settlement_ event is displayed, indicating that the capture was requested to the payment gateway:
 
-![transação-captura-solicitação](//images.contentful.com/alneenqid6w5/4ZnegfgNcA4MQsgMuQaAsE/478d66d4b763730762637cc75a1aaea4/transaccion-captura-solicitud.png)
+![transação-captura-solicitação](https://images.contentful.com/alneenqid6w5/4ZnegfgNcA4MQsgMuQaAsE/478d66d4b763730762637cc75a1aaea4/transaccion-captura-solicitud.png)
 
 While the capture has been started successfully, the _Settling_ event will be displayed. And at the end of the capture, the _Settled_ event will be displayed:
 
-![transação-captura-iniciada-capturada](//images.contentful.com/alneenqid6w5/2Z2fPSYG5WK0YqSCuWGAQi/42f03171a702ada307bd85b21614757f/transaccion-captura-iniciada-capturada.png)
+![transação-captura-iniciada-capturada](https://images.contentful.com/alneenqid6w5/2Z2fPSYG5WK0YqSCuWGAQi/42f03171a702ada307bd85b21614757f/transaccion-captura-iniciada-capturada.png)
 
 If the capture doesn't happen due to an issue from outside the flow, the details will be logged in the timeline, according to the information returned by the payment gateway.
 
@@ -68,7 +68,7 @@ If the capture doesn't happen due to an issue from outside the flow, the details
 
 Upon completion of the transaction, VTEX will indicate it as shown in the image below:
 
-![transação-concluida](//images.contentful.com/alneenqid6w5/68PjN2ChyMWqYQ4Owm8Yk6/0a440ea3cf6e5190b7b03e72d6a7e7e8/transaccion-finalizada.png)
+![transação-concluida](https://images.contentful.com/alneenqid6w5/68PjN2ChyMWqYQ4Owm8Yk6/0a440ea3cf6e5190b7b03e72d6a7e7e8/transaccion-finalizada.png)
 
 ## Transaction scheduled for automatic capture
 
@@ -76,4 +76,4 @@ Generally, affiliations allow you to set a capture date to force a capture and a
 
 Here you can see the automatic capture schedule date:
 
-![captura-auto-agendada pt](//images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
+![captura-auto-agendada pt](https://images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
diff --git a/docs/tutorials/en/transferring-store-ownership.md b/docs/tutorials/en/transferring-store-ownership.md
index 52fa4d55d..f06b399db 100644
--- a/docs/tutorials/en/transferring-store-ownership.md
+++ b/docs/tutorials/en/transferring-store-ownership.md
@@ -25,7 +25,7 @@ The Sponsor management page allows you to identify the current Sponsor user, tra
 
 You should see a screen that is similar to the image below, with contact information for the current Sponsor user, a disclaimer indicating the risks associated with transferring store ownership and a button that allows you to acknowledge the risks and transfer ownership anyway.
 
-![Sponsor management panel](//images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/b4b9533827aeb3d03960c24eb092cb98/Sponsor_Management_en.png)
+![Sponsor management panel](https://images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/b4b9533827aeb3d03960c24eb092cb98/Sponsor_Management_en.png)
 
 ## Steps in the ownership transfer flow
 
@@ -51,7 +51,7 @@ This will complete the ownership transfer – cancelling the invitation will no
 
 The Sponsor user is responsible for critical maintenance and authorization actions, and mistakes made by this user role can have drastic consequences. Therefore, it is essential to track  changes related to this user role. To monitor and audit  account ownership transfers, you can access the activity log on the Sponsor management page by clicking on the **Activity Log** button. 
 
-![Activity Log](//images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/a4d638c4dac1442a317acc1e40686326/Activity_Log_en.gif)
+![Activity Log](https://images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/a4d638c4dac1442a317acc1e40686326/Activity_Log_en.gif)
 
 All events related to the transfer of account ownership are logged in the activity log with the date they occurred and the user associated with the event.
 
diff --git a/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
index bcb3302c2..a1d87aa7a 100644
--- a/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
@@ -32,7 +32,7 @@ Issues in subscription cycles indicate that an obstacle prevented a subscription
 
 The **Cycles with an issue** tab displays subscription orders with such problems, as illustrated in the image below.
 
-![cicloscomproblema EN](//images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/8985fa930def4ec541d9127bc855740d/cicloscomproblema_EN.png)
+![cicloscomproblema EN](https://images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/8985fa930def4ec541d9127bc855740d/cicloscomproblema_EN.png)
 
 In this tab, you can manage orders with issues in subscription cycles and retry placing orders manually. For example, when a product is unavailable, you can edit its inventory and then try to order it again.
 
@@ -189,7 +189,7 @@ Payment errors occur during the payment approval flow, such as having a credit c
 
 You can view orders with this error on the **Payment Error** tab, as shown in the image below.
 
-![errosdepagamento EN](//images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/4bea9e2c3fa3385e1fd1b1c0add2b0f0/errosdepagamento_EN.png)
+![errosdepagamento EN](https://images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/4bea9e2c3fa3385e1fd1b1c0add2b0f0/errosdepagamento_EN.png)
 
 To analyze payment errors, follow the steps below:
 
@@ -197,7 +197,7 @@ To analyze payment errors, follow the steps below:
 2. Click on the **Dashboards** tab.
 3. In the **Subscription Orders** section, click on the **Payment Error** tab.
 4. Identify the order you want to analyze and click on its ID, as illustrated in the image below. You will be redirected to the order details page in the **All Orders** module.
-  ![EN Log Erro de pagamento](//images.ctfassets.net/alneenqid6w5/2Bb1XYgaZEdNMVhcnX5lF3/a10c69783d57d09b70234c6dda18542d/EN_Log_Erro_de_pagamento.png)
+  ![EN Log Erro de pagamento](https://images.ctfassets.net/alneenqid6w5/2Bb1XYgaZEdNMVhcnX5lF3/a10c69783d57d09b70234c6dda18542d/EN_Log_Erro_de_pagamento.png)
 5. Then, click on **View transaction details** under the **Payment** card. You will be redirected to the **Transactions** page in the **Payments** module.
 6. On the **Transactions** page, you can view and analyze the order transaction events. Read the article [Viewing the order's details in Payments](https://help.vtex.com/en/tutorial/como-visualizar-detalhes-do-pedido) for more information.
 
diff --git a/docs/tutorials/en/understanding-b2b-orders.md b/docs/tutorials/en/understanding-b2b-orders.md
index 28ec99bc7..882862ea5 100644
--- a/docs/tutorials/en/understanding-b2b-orders.md
+++ b/docs/tutorials/en/understanding-b2b-orders.md
@@ -19,7 +19,7 @@ In B2B e-commerce operations, it is often necessary to inform an order's status
 
 The **B2B Orders** app makes this process simple, allowing any employee to consult the company's orders through its online store.
 
-![orders VTEX B2B](//images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
+![orders VTEX B2B](https://images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
 
 This self-service experience is possible, thanks to API integration with the ERP. With this, the employee can search for orders by:
 
diff --git a/docs/tutorials/en/understanding-how-indexation-works.md b/docs/tutorials/en/understanding-how-indexation-works.md
index 0ffb0b27b..06f3205df 100644
--- a/docs/tutorials/en/understanding-how-indexation-works.md
+++ b/docs/tutorials/en/understanding-how-indexation-works.md
@@ -33,7 +33,7 @@ Every time product listing data is altered as shown below, the database is reind
 
 Once a product is marked for reindexing, the text _pending indexing_ is included in the product listing in admin. The indexer places these products in a queue for processing, with a 2-minute waiting time. After the 2 minutes, the product is available for indexing. In this process, all the VTEX modules are consulted, with prices and availability updated for every sales policy. This process takes an average of 4 minutes.
 
-![indexaçao.en](//images.ctfassets.net/alneenqid6w5/1OCaCwIsLA1CeKVqnwIU7E/b014aa1be9f142f208b3c000b3e80998/indexa__ao.en.png)
+![indexaçao.en](https://images.ctfassets.net/alneenqid6w5/1OCaCwIsLA1CeKVqnwIU7E/b014aa1be9f142f208b3c000b3e80998/indexa__ao.en.png)
 
 ## Indexing Report
 
@@ -48,7 +48,7 @@ The products are divided according to each step of the indexing process and to t
 - **Total Indexed**, **Not yet in queue** and **Total in Queue**: relate to the stages of the product in the process **Not yet in queue** are those that were changed in less than 2 minutes, and _Total na fila_ (Total in queue) are those that have started the indexing process, after these 2 minutes.
 - **In queue from 1 to 2 hours** and **In queue from 2 to 4 hours**, **In queue from 4 to 8 hours**: represent the periods for which the products have been in the indexing process.
 
-![Indexingreport](//images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
+![Indexingreport](https://images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
 
 The indexing report also indicates the time the last item took to be reindexed. This is shown in the upper right side of the report (see the image above). 
 
diff --git a/docs/tutorials/en/understanding-how-the-cache-works.md b/docs/tutorials/en/understanding-how-the-cache-works.md
index 82447429f..7e1d4ac92 100644
--- a/docs/tutorials/en/understanding-how-the-cache-works.md
+++ b/docs/tutorials/en/understanding-how-the-cache-works.md
@@ -25,11 +25,11 @@ The browser submits a **request** and the server’s reply is its **response**.
 
 See the schematic chart shown below:
 
-![How the cache works - communication between server and browser](//images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/c0dd7b6c39dd72bc71c60185e926fa67/1_EN.png)
+![How the cache works - communication between server and browser](https://images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/c0dd7b6c39dd72bc71c60185e926fa67/1_EN.png)
 
 The cache is represented by a layer between the browser and server. So when a **request** is made, instead of the system going straight to the server to find the information, it first goes to this layer, which makes the response much quicker. A schematic diagram is shown below:
 
-![How cache works - communication with cache (without expiring)](//images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/fa4aaef1190355a31e8afb5b08a85630/2_EN.png)
+![How cache works - communication with cache (without expiring)](https://images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/fa4aaef1190355a31e8afb5b08a85630/2_EN.png)
 
 However, since the latest information is in the server, the cache has to be updated from time to time. The frequency varies according to the type of **request**: it is different for a single page, for a java script or CSS file, or for an image.
 
@@ -58,7 +58,7 @@ As mentioned the cache duration time varies for each type of **request**. The fo
 
 When a **request** cache (page or file) expires, and you make a new request (i.e. load the URL again) the system goes to the server, collects the latest information and updates the content of the URL in the cache. Once updated, the cached version will be returned for a new request for the URL. The following illustrates how this works:
 
-![How cache works - communication with cache (expired)](//images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/5ab850cc08928054e7c5133016702c17/3_EN.png)
+![How cache works - communication with cache (expired)](https://images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/5ab850cc08928054e7c5133016702c17/3_EN.png)
 
 So we can separate responses into two groups: cached and not cached.
 
@@ -71,7 +71,7 @@ When you click on the request, upon the first page reload, find among the header
 
 If the value is “MISS”, it means that the content is not cached but was returned directly by the server. Another important detail that can be found from the **request** headers is the date when the cache was created. This is shown in the property `X-vtex-processed-at`.
 
-![](//images.contentful.com/alneenqid6w5/5GPSsb4UWA28QS4soyguSI/8772946997cc979ddf9c2297f2ca8bb6/cache.png)
+![](https://images.contentful.com/alneenqid6w5/5GPSsb4UWA28QS4soyguSI/8772946997cc979ddf9c2297f2ca8bb6/cache.png)
 
 JavaScript and CSS files also have a fixed cache duration, but as they are used in formatting layouts and thus sometimes need to work more quickly, the portal is able to identify changes in their content, and break through the cache layer. 
 
diff --git a/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md b/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md
index a908c0b2c..2a64e004f 100644
--- a/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md
+++ b/docs/tutorials/en/understanding-storebuilder-and-stylesbuilder.md
@@ -15,7 +15,7 @@ legacySlug: understanding-storebuilder-and-stylesbuilder
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-![UI Blocks Voando.mp4](//images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
+![UI Blocks Voando.mp4](https://images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
 
 This documentation is structured to explain Store 2.xx's StoreBuilder and StyleBuilder.  Throughout the documentation we will be using DreamStore (a `Store 2.xx` template) to understand key concepts that will allow you to successfully structure and style your store.
 
@@ -39,7 +39,7 @@ Store 2 makes big paradigm shifts from Store 1 by introducing the concept of **b
 
 Let's look inside DreamStore's `/manifest.json` in order to see what our app requires to function properly:
 
-![Screen Shot 2019-01-25 at 16.40.06](//images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
+![Screen Shot 2019-01-25 at 16.40.06](https://images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
 
 Notice how we have two `builders` specified:
 
@@ -62,7 +62,7 @@ Since every theme app (a store) makes use of the `Store` app (through the `"vtex
 
 Let's `vtex link` and send our DreamStore app to a workspace so we can study it for a minute.
 
-![Screen Shot 2019-01-27 at 22.24.47](//images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
+![Screen Shot 2019-01-27 at 22.24.47](https://images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
 
 
 If you're familiar  with React or other modern JavaScript frameworks, you will be familiar with the concept of components on a webpage. As you can quickly tell, our webpage has a `header`, `carousel` and a `shelf`.  How were these components inserted? 
@@ -101,7 +101,7 @@ In order to better understand this, we should look into how `Store 2.xx` app wor
 
 Let's look inside Store2.xx's `/manifest.json` file to see what the `Store` app brings to the table.
 
-![Screen Shot 2019-01-25 at 17.18.56](//images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
+![Screen Shot 2019-01-25 at 17.18.56](https://images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
 
 As we can see it's structured similarly to `Dreamstore`'s `manifest.json`.  
 
@@ -146,7 +146,7 @@ Let's now explore how the blocks inside a page (a page is just a block containin
 Open the `store` folder and open `interfaces.json`.
 
 ### Interfaces
-![Screen Shot 2019-01-25 at 17.35.10](//images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
+![Screen Shot 2019-01-25 at 17.35.10](https://images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
 
 An interface is a conjunction of `blocks` and exists exclusively inside `Store2.xx`. It serves as a contract, using well defined constraits explaining how the blocks will work together.
 
@@ -203,7 +203,7 @@ Let's continue analyzing `store.home`.  I'll be commenting inline.
 ```
 
 If we scroll we can see the same JSON objects defining and setting the block organization. Another example is the search results page:
-![Screen Shot 2019-01-25 at 18.22.12](//images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
+![Screen Shot 2019-01-25 at 18.22.12](https://images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
 
 The information describes the following interface information:
   
@@ -224,7 +224,7 @@ It's time to visit  Dreamstore app's blocks.json and understand how the entire s
 
 ### Structuring and configuring our store with `StoreBuilder`
 
-![Codigo voando blocks.mp4](//images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
+![Codigo voando blocks.mp4](https://images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
 
 Open up `/blocks.json` and find our trusty `store.home.`Let's begin by analyzing the first block inside `store.home`: `carousel#home`.
 
@@ -246,12 +246,12 @@ Scroll down until we find `carousel#home`. Through `props` our `carousel#home` h
   
   
 ### Styling our store with `StylesBuilder`
-![StyleBuilder.mp4](//images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
+![StyleBuilder.mp4](https://images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
 
 
 StylesBuilder takes your styles.json file when building and generates uses [Tachyons](https://tachyons.io/) generator to produce your store's CSS.  
 
 We designed StylesBuilder to be extremely intuitive and self explanatory.  It's as simple as adjusting the hexcodes accordingly and seeing the results permeate throughout the store.  
 
-![Screen Shot 2019-01-28 at 00.40.17](//images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
+![Screen Shot 2019-01-28 at 00.40.17](https://images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
 
diff --git a/docs/tutorials/en/understanding-the-additional-shipping-cost.md b/docs/tutorials/en/understanding-the-additional-shipping-cost.md
index ad3498598..e402bb0ae 100644
--- a/docs/tutorials/en/understanding-the-additional-shipping-cost.md
+++ b/docs/tutorials/en/understanding-the-additional-shipping-cost.md
@@ -29,7 +29,7 @@ There are three possible ways to add a value to the shipping rate: additional c
 
 In this field, a percentage of the product's price must be set, which will then be added to the shipping value.
 
-![adicionalfrete1 EN](//images.ctfassets.net/alneenqid6w5/OqyvMFeOU6OmsMGAMQ2km/ba3c318b0b158ccbccb511863dc7fc57/adicionalfrete1_EN.png)
+![adicionalfrete1 EN](https://images.ctfassets.net/alneenqid6w5/OqyvMFeOU6OmsMGAMQ2km/ba3c318b0b158ccbccb511863dc7fc57/adicionalfrete1_EN.png)
 
 In the example above, the product's price $ 80.00, and the percentage set in the __Additional value__ field is 10%. Therefore, $ 8.00 will be added to the shipping rate. The shipping rate plus this first additional fee results in a $ 18.00 total fee.
 
@@ -43,7 +43,7 @@ The calculation of this field considers the product's weight and its difference
 
 __It looks as follows:__
 
-![adicionalfrete2 EN](//images.ctfassets.net/alneenqid6w5/1FbPWgvxpuOQeImAS0S6uS/2a9740e4bff83d1a1e3c51d77729bede/adicionalfrete2_EN.png)
+![adicionalfrete2 EN](https://images.ctfassets.net/alneenqid6w5/1FbPWgvxpuOQeImAS0S6uS/2a9740e4bff83d1a1e3c51d77729bede/adicionalfrete2_EN.png)
 
 In the example above, the product's lower weight limit range is 100g. The value set in the **Additional value per weight** field is 0.1. Therefore, the amount to be added to the shipping rate total is $ 10.00. As the shipping calculation previously totaled $ 14.00, the final value is now $ 24.00.
 
@@ -58,7 +58,7 @@ This additional fee is calculated on top of the final shipping rate, as opposed
 
 The additional percentage fee is the last shipping calculation made, which means that it's added to the shipping price table value + the other additional fees above * the value set in the field.
 
-![adicionalfrete3 EN](//images.ctfassets.net/alneenqid6w5/1K03RGdwsMsuQGe8Awqsua/8ffe9ec0b094914ed4d14be361542cad/adicionalfrete3_EN.png)
+![adicionalfrete3 EN](https://images.ctfassets.net/alneenqid6w5/1K03RGdwsMsuQGe8Awqsua/8ffe9ec0b094914ed4d14be361542cad/adicionalfrete3_EN.png)
 
 In this case, the value entered in the field __Additional value__ will be the percentage fee that is to be added to the final shipping rate calculation. For example, if shipping, with all its additional fees included, is $ 20.00, and the value set in the Additional Shipping fee field is 10, $ 2.00 would be added to those original $ 20.00, totaling $ 22.00 that the customer would pay for shipping. This is a simple way of having a profit margin on shipping.
 
diff --git a/docs/tutorials/en/understanding-the-cubic-weight-factor.md b/docs/tutorials/en/understanding-the-cubic-weight-factor.md
index 9c25cdcc5..23d6f3f86 100644
--- a/docs/tutorials/en/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/en/understanding-the-cubic-weight-factor.md
@@ -40,7 +40,7 @@ When calculating the cubic weight factor, VTEX platform does not consider measur
 
 Check out the following example:
 
-![example_cubic_weight_en](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
+![example_cubic_weight_en](https://images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
 
 - __Package size:__ `50cm x 15cm x 60cm`
 - __Minimum weight:__ `9kg`
@@ -55,7 +55,7 @@ That is, if the value offered by your carrier is `6,000`, you must perform the d
 
 This is the value you must fill out the **Cubic weight factor** field in your [shipping policy](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![cubic_weight_EN](//images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/dc63a437a83448eaafd90e0fb545879e/cubic_weight_EN.png)
+![cubic_weight_EN](https://images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/dc63a437a83448eaafd90e0fb545879e/cubic_weight_EN.png)
 
 Therefore, the final calculation will be:
 
diff --git a/docs/tutorials/en/understanding-the-message-center.md b/docs/tutorials/en/understanding-the-message-center.md
index 7a847b4d2..7093c5f4e 100644
--- a/docs/tutorials/en/understanding-the-message-center.md
+++ b/docs/tutorials/en/understanding-the-message-center.md
@@ -31,7 +31,7 @@ Understand the information that each template card contains:
 
 To facilitate browsing, in addition to the free text search field, the interface provided filters per application (modules) and type (standard/default and/or personalized/amended message).
 
-![busca-templates-central-mensagens en](//images.ctfassets.net/alneenqid6w5/6unXvbEcUgaQAucsKCcm8W/9aebebd28a45aea02949470c429fe4db/busca-templates-central-mensagens_en.png)
+![busca-templates-central-mensagens en](https://images.ctfassets.net/alneenqid6w5/6unXvbEcUgaQAucsKCcm8W/9aebebd28a45aea02949470c429fe4db/busca-templates-central-mensagens_en.png)
 
 After understanding the basic about the templates, you can see how to edit them. This step is not mandatory, since VTEX provides a basic and responsive layout for all messages, with information needed to communicate properly with your customer, but it is natural that the stores adapt the brand communication standard they already use.
 
diff --git a/docs/tutorials/en/understanding-the-price-change-rule.md b/docs/tutorials/en/understanding-the-price-change-rule.md
index a824a5ee2..16fd19339 100644
--- a/docs/tutorials/en/understanding-the-price-change-rule.md
+++ b/docs/tutorials/en/understanding-the-price-change-rule.md
@@ -26,6 +26,6 @@ All other options to update prices will also be blocked.
 
 The price limits percentages can be removed or redefined by accessing the __Settings__ tab on the __Prices__ module. 
 
-![trava-variação-preço en](//images.ctfassets.net/alneenqid6w5/7q0Dp7AIQokuGIGcIKOmqm/e1798e4757cba658c2dd5b5bde1a69bf/trava-varia____o-pre__o_en.png)
+![trava-variação-preço en](https://images.ctfassets.net/alneenqid6w5/7q0Dp7AIQokuGIGcIKOmqm/e1798e4757cba658c2dd5b5bde1a69bf/trava-varia____o-pre__o_en.png)
 
 Some marketplaces also have this price variation limit. If you wish to change prices beyond the limit ranges, contact the marketplace asking for the change.
diff --git a/docs/tutorials/en/understanding-the-security-report.md b/docs/tutorials/en/understanding-the-security-report.md
index a7246e018..900e214c5 100644
--- a/docs/tutorials/en/understanding-the-security-report.md
+++ b/docs/tutorials/en/understanding-the-security-report.md
@@ -31,7 +31,7 @@ Several filters are available, beginning with the fields below, bearing in mind
 
 In the example, I set up a filter for a change (whether creation or updating) to the price of an SKU. To do this I have used the fields __Data__ with the SKU Id, __Screen__, with the location of the platform where the change is happening and a specific time frame. According to the report you want, you may have to use other fields at the same time, or as a replacement for those I have used in the example.
 
-![relatorioseguran aPT.gif?h=250](//images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/ef82dec5acc0f07090f01d3484407e75/relatorio-seguranca-en.gif)
+![relatorioseguran aPT.gif?h=250](https://images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/ef82dec5acc0f07090f01d3484407e75/relatorio-seguranca-en.gif)
 
 Read the section below to understand all the available fields for filtering the report.
 
diff --git a/docs/tutorials/en/understanding-the-suspicious-purchase-notice-on-vtex-do.md b/docs/tutorials/en/understanding-the-suspicious-purchase-notice-on-vtex-do.md
index 5a343792d..76254e0c9 100644
--- a/docs/tutorials/en/understanding-the-suspicious-purchase-notice-on-vtex-do.md
+++ b/docs/tutorials/en/understanding-the-suspicious-purchase-notice-on-vtex-do.md
@@ -27,7 +27,7 @@ When SherlockBOT identifies a closed order that may indicate a malware, the reta
 
 See an example of this alert in the screenshot below:
 
-![sherlock (1)](//images.contentful.com/alneenqid6w5/6CsvYu9nfG0E4QowAEu86/c69b772065781ddc98bc85eeee37ef01/sherlock-1.png)
+![sherlock (1)](https://images.contentful.com/alneenqid6w5/6CsvYu9nfG0E4QowAEu86/c69b772065781ddc98bc85eeee37ef01/sherlock-1.png)
 
 The retailer may also be included in the Gateway’s security barriers, that is, VTEX may apply protection rules to your store to protect it against credit card tests.  
 
diff --git a/docs/tutorials/en/understanding-the-task-list-vtex-do.md b/docs/tutorials/en/understanding-the-task-list-vtex-do.md
index 0428e0e13..4d7fd76b5 100644
--- a/docs/tutorials/en/understanding-the-task-list-vtex-do.md
+++ b/docs/tutorials/en/understanding-the-task-list-vtex-do.md
@@ -19,13 +19,13 @@ VTEX DO manages tasks generated by the platform modules to be carried out by the
 
 To view the list of tasks, just click on the lower right-hand corner of the Orders Management screen.  Some examples of these tasks are: __review payment for cancelation; reverse payment out; approve order under authority limit; cancellation requested and many others,__ since each module existing on VTEX has the autonomy and permission to post any information.
 
-![](//images.contentful.com/alneenqid6w5/6CypzWJhLye2OOW6QqEKu0/fce59ed1fedbb5f8889b1cb5f3ec4bf2/VtexDO_GifAbrir.gif)
+![](https://images.contentful.com/alneenqid6w5/6CypzWJhLye2OOW6QqEKu0/fce59ed1fedbb5f8889b1cb5f3ec4bf2/VtexDO_GifAbrir.gif)
 
 This functionality allows users the following actions: allocating tasks to someone (even to themselves), marking them as completed, adding a comment and seeing more details, which redirects them to where the task needs to be done. “adiar” and “ignorar” buttons exist, but they are future actions still under development.
 
 ## Assign and unassign a task to yourself
 
-![](//images.contentful.com/alneenqid6w5/hSiaD565VuWwKUmWuwucO/a7f7a04e378a43e14cc0ed8469deb573/VtexDO_GifAtribuirTarefaProprio.gif)
+![](https://images.contentful.com/alneenqid6w5/hSiaD565VuWwKUmWuwucO/a7f7a04e378a43e14cc0ed8469deb573/VtexDO_GifAtribuirTarefaProprio.gif)
 
 ### Assign a task
 Open **VTEX DO**;
@@ -38,7 +38,7 @@ Open **VTEX DO**;
 
 ## Assign and unassign a task to other user
 
-![](//images.contentful.com/alneenqid6w5/xTb2Dtb79ueKEiESCWi2y/05af0e238ac055a992b612381d3acd42/VtexDO_GifAtribuirTarefaTerceiros.gif)
+![](https://images.contentful.com/alneenqid6w5/xTb2Dtb79ueKEiESCWi2y/05af0e238ac055a992b612381d3acd42/VtexDO_GifAtribuirTarefaTerceiros.gif)
 
 ### Assign a task
 - Open **VTEX DO**;
@@ -55,7 +55,7 @@ _The tasks assigned to you appear in the tab entitled “MINHAS”. Another deta
 
 ## Filter a task
 
-![](//images.contentful.com/alneenqid6w5/1o6DK8SFHiuWwcESKScaqE/a616812c5d48431cf5383dbd204c511f/VtexDO_GifFiltro.gif)
+![](https://images.contentful.com/alneenqid6w5/1o6DK8SFHiuWwcESKScaqE/a616812c5d48431cf5383dbd204c511f/VtexDO_GifFiltro.gif)
 
 Filtering is possible through the search bar by using the name of the task and the name of the user attributed to them or by entering observations. It also permits filtering according to the module that posted the task.
 
@@ -73,7 +73,7 @@ Filtering is possible through the search bar by using the name of the task and t
 
 Since the purpose of the functionality is to perform the tasks, one facility it provides is that of redirecting to the module that posted the task within the order, transaction or any other specific address of the respective module that created the task.
 
-![](//images.contentful.com/alneenqid6w5/5nxobC9IVUGUe8CQoaI02I/84ac62df3673e85a379d3c9f409ef999/VtexDO_GifFazerTarefa.gif)
+![](https://images.contentful.com/alneenqid6w5/5nxobC9IVUGUe8CQoaI02I/84ac62df3673e85a379d3c9f409ef999/VtexDO_GifFazerTarefa.gif)
 
 1. Open VTEX DO;
 2. Click on the task you wish to perform;
@@ -85,7 +85,7 @@ Since the purpose of the functionality is to perform the tasks, one facility it
 
 In order to maintain VTEX DO organized, the ideal is to conclude the task after performing it, so as to avoid reworking or wasting time in the future when revisiting the list of tasks. Another possibility would be to conclude a task even without performing it, for example, if cancellation of an order is requested, but you managed to turn the situation around. Should you need to reopen a task that was improperly concluded, don’t worry, because you can reopen it at any time. Just search for it on the list and follow the steps of the following gif.
 
-![](//images.contentful.com/alneenqid6w5/5Uc9dUfGusGcoAW6iw4EOa/52d9aa14d083b08e66fd4f9453cf1813/VtexDO_GifFinalizarTarefa.gif)
+![](https://images.contentful.com/alneenqid6w5/5Uc9dUfGusGcoAW6iw4EOa/52d9aa14d083b08e66fd4f9453cf1813/VtexDO_GifFinalizarTarefa.gif)
 
 ### Conclude a task
 - Open **VTEX DO**;
@@ -101,7 +101,7 @@ In order to maintain VTEX DO organized, the ideal is to conclude the task after
 
 Also with a view to organizing these tasks and using them to formalize communication, there is a function for entering comments, as needed, on a case-by-case basis.
 
-![](//images.contentful.com/alneenqid6w5/5SrDSFwNIkokms4ayga2oo/86862b1896fabd96b34344318fd553fb/VtexDO_GifInserirComentario.gif)
+![](https://images.contentful.com/alneenqid6w5/5SrDSFwNIkokms4ayga2oo/86862b1896fabd96b34344318fd553fb/VtexDO_GifInserirComentario.gif)
 
 1. Open **VTEX DO**;
 2. Click on the task on which you wish to comment;
@@ -110,4 +110,4 @@ Also with a view to organizing these tasks and using them to formalize communica
 
 Since it is possible to execute VTEX DO actions with it open, to close it you have to click on the down arrow, as shown in the gif below:
 
-![](//images.contentful.com/alneenqid6w5/6N34IAYvdKyYAa6KCIM2AO/670277853327aa793c851d8a0ce99b2a/VtexDO_GifFechar.gif)
+![](https://images.contentful.com/alneenqid6w5/6N34IAYvdKyYAa6KCIM2AO/670277853327aa793c851d8a0ce99b2a/VtexDO_GifFechar.gif)
diff --git a/docs/tutorials/en/understanding-the-topbar.md b/docs/tutorials/en/understanding-the-topbar.md
index 725282789..195c8d4da 100644
--- a/docs/tutorials/en/understanding-the-topbar.md
+++ b/docs/tutorials/en/understanding-the-topbar.md
@@ -19,18 +19,18 @@ The sidebar is the starting point for all admin areas. See below the details reg
 
 **Browse the modules**: to do so, just click on the desired module in the Admin sidebar with all available module.
 
-![paginainicial.en](//images.ctfassets.net/alneenqid6w5/68DVYFXEFfShDhVJLoP90E/ab49f60e0a7fccda830f4f7cfccdc32b/paginainicial.en.png)
+![paginainicial.en](https://images.ctfassets.net/alneenqid6w5/68DVYFXEFfShDhVJLoP90E/ab49f60e0a7fccda830f4f7cfccdc32b/paginainicial.en.png)
 
 **Browse the sub-domains:** To browse the sub-domains of your store, just click on the current domain. You will view all options. To go to the admin of a sub-domain, just click on it on the menu.
-![subdominios.en](//images.ctfassets.net/alneenqid6w5/14NnbogRz9imPMypMsSFSF/6c19b199374901b350a95eedf7094372/subdominios.en.png)
+![subdominios.en](https://images.ctfassets.net/alneenqid6w5/14NnbogRz9imPMypMsSFSF/6c19b199374901b350a95eedf7094372/subdominios.en.png)
 
 **Select the admin language:** to select a language, just click on the language icon and select a language.
-![idioma.en](//images.ctfassets.net/alneenqid6w5/3wBMDVQVe1C1lILiOFPSG8/ec5ff60fd97703e88e229190f8d65d17/idioma.en.png)
+![idioma.en](https://images.ctfassets.net/alneenqid6w5/3wBMDVQVe1C1lILiOFPSG8/ec5ff60fd97703e88e229190f8d65d17/idioma.en.png)
 
 
 **Access new knowledge bases: **to access one of our bases, click on your support profile and select the site you intend to access just clicking on it.
 
-![support.en](//images.ctfassets.net/alneenqid6w5/4SvEqHGVINK4P0gwGaZlXB/139f810e98f3f1ef0ca45d767d1e4aab/support.en.png)
+![support.en](https://images.ctfassets.net/alneenqid6w5/4SvEqHGVINK4P0gwGaZlXB/139f810e98f3f1ef0ca45d767d1e4aab/support.en.png)
 
 
 **Logging off: **to log off, click on your name and then on the link **Sair.**
diff --git a/docs/tutorials/en/understanding-the-updating-of-the-xml.md b/docs/tutorials/en/understanding-the-updating-of-the-xml.md
index 163c2debf..b6e11b0ce 100644
--- a/docs/tutorials/en/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/en/understanding-the-updating-of-the-xml.md
@@ -21,6 +21,6 @@ This query means that the XML was called in less than 48 hours. Those XMLs not c
 
 You can view the date of the latest XML update. This information is shown in UTC time at the foot of the document, as illustrated below.
 
-[![xml](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
+[![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
 
 <div class="alert alert-info">If the option “Display SKUs without available stock (out of stock) in Inventory among the results” is not checked, out-of-stock products/SKUs will NOT be shown in the XML. Inactive products also do <strong>not</strong> appear in the XML.</div>
diff --git a/docs/tutorials/en/understanding-vtexs-email-capture-system.md b/docs/tutorials/en/understanding-vtexs-email-capture-system.md
index 561d186f0..a04ecceb6 100644
--- a/docs/tutorials/en/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/en/understanding-vtexs-email-capture-system.md
@@ -51,5 +51,5 @@ So that the <a href="https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandon
 Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
 </div>
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/tutorials/en/updating-quantity-of-skus-in-inventory.md b/docs/tutorials/en/updating-quantity-of-skus-in-inventory.md
index 3f2c6fba6..ddb06c390 100644
--- a/docs/tutorials/en/updating-quantity-of-skus-in-inventory.md
+++ b/docs/tutorials/en/updating-quantity-of-skus-in-inventory.md
@@ -56,7 +56,7 @@ Remember that an order can have an active product reservation. If this product h
 
 Order containing booked items will continue to be listed as reserved and will not be available for sale. In the example given below, we have ten Gatorade units booked but not yet invoiced. As we update inventory item availability, the system gives the results in real-time. In our example,  we may end up with a negative inventory of up to 10 items, since the ongoing reserved orders will continue to be listed. [Find out more about reservations](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona/). 
 
-![Atualizar Estoque GIF](//images.contentful.com/alneenqid6w5/1lorbuip9ewo8gY8qg8wU0/07e97e612b4711f0f21c205b50e74867/InventoryUpdate.gif)
+![Atualizar Estoque GIF](https://images.contentful.com/alneenqid6w5/1lorbuip9ewo8gY8qg8wU0/07e97e612b4711f0f21c205b50e74867/InventoryUpdate.gif)
 
 
 
diff --git a/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md b/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md
index 9f96d7fb9..e5e25a74c 100644
--- a/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md
+++ b/docs/tutorials/en/updating-the-quantity-of-items-in-inventory.md
@@ -45,7 +45,7 @@ _Available units = updated quantity of units - reserved units_
 
 Negative stock usually occurs when an SKU corresponding to an order that already has a reservation is removed from inventory. To avoid this situation, it is important that the SKU quantity update takes place  once the [status of the orders](https://help.vtex.com/en/tutorial/order-flow-on-the-oms--tutorials_196) has changed from `Preparing for delivery`. At this point, the platform has already [acknowledged the reservation](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#acknowledged-reservation), and it won't interpret the SKU quantity update as a reduction in the quantity of units of a product that hasn't been sold yet.
 
-![Inventory management](//images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/d591d4682810d9f6549772a0e03f7f32/Inventory_management.gif)
+![Inventory management](https://images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/d591d4682810d9f6549772a0e03f7f32/Inventory_management.gif)
 
 ## Related articles
 
diff --git a/docs/tutorials/en/uploading-a-product-xml.md b/docs/tutorials/en/uploading-a-product-xml.md
index 5f379a361..80c0e0f49 100644
--- a/docs/tutorials/en/uploading-a-product-xml.md
+++ b/docs/tutorials/en/uploading-a-product-xml.md
@@ -19,5 +19,5 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 _The video presented in this tutorial has not yet been translated to english. We are working to offer more english-language content. Thank you for the comprehension._
 
-<video class="wp-video-shortcode" id="video-2573-4" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4?_=4" />[//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4](//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4 "//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4")</video>
+<video class="wp-video-shortcode" id="video-2573-4" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4?_=4" />[//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4](https://assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4 "//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4")</video>
 
diff --git a/docs/tutorials/en/url-mapping-301-redirect.md b/docs/tutorials/en/url-mapping-301-redirect.md
index c21bfd742..b23442a86 100644
--- a/docs/tutorials/en/url-mapping-301-redirect.md
+++ b/docs/tutorials/en/url-mapping-301-redirect.md
@@ -57,7 +57,7 @@ There are two ways to add and change URL mapping:
 3. Click on the **URL Builder** folder.
 4. Click on `Import` to import the spreadsheet.
 5. Download the spreadsheet template illustrated below by clicking on `Export`.
-![exemplo-planilha](//images.contentful.com/alneenqid6w5/2Z63gJkADcR2gveT3lncQb/9bbd790becd99acb7b647537eb71c6a9/Screenshot_5.png)
+![exemplo-planilha](https://images.contentful.com/alneenqid6w5/2Z63gJkADcR2gveT3lncQb/9bbd790becd99acb7b647537eb71c6a9/Screenshot_5.png)
 6. Fill in the [spreadsheet fields](#spreadsheet-fields).
 7. After populating the spreadsheet template, click on the `Localize` button on the import page to upload the template.
 8. Select the file you want to upload. The filename extension must be `.xls` in the format `Excel 97-2003 Workbook`.
diff --git a/docs/tutorials/en/using-orders-managment-filters-in-api.md b/docs/tutorials/en/using-orders-managment-filters-in-api.md
index 22aefc660..619db71b7 100644
--- a/docs/tutorials/en/using-orders-managment-filters-in-api.md
+++ b/docs/tutorials/en/using-orders-managment-filters-in-api.md
@@ -28,18 +28,18 @@ The example used is the query API related to orders: [http://{STORENAME}.vtexcom
 
 We will use a filter based on the date of creation of the order, within a range that may bring all orders marked as “**há um mês**” and whose status is “**pronto para manuseio.”**
 
-![](//images.contentful.com/alneenqid6w5/53zjSDeDBe20MkAQa2iqk0/ba1b8b24ddb63e121dd060a79aa1a534/OMS_Filtro5.png)
+![](https://images.contentful.com/alneenqid6w5/53zjSDeDBe20MkAQa2iqk0/ba1b8b24ddb63e121dd060a79aa1a534/OMS_Filtro5.png)
 
-![](//images.contentful.com/alneenqid6w5/3AS1rSk36MAwSIMGkaqsSm/1c496620f9c9669b7c9ccd6078681f8e/OMS_Filtro.png)
+![](https://images.contentful.com/alneenqid6w5/3AS1rSk36MAwSIMGkaqsSm/1c496620f9c9669b7c9ccd6078681f8e/OMS_Filtro.png)
 
-![](//images.contentful.com/alneenqid6w5/jj5tYpFP8WkYicAAIymCa/5157cf41ab647f31e20db895669eabea/OMS_Filtro2.png)
+![](https://images.contentful.com/alneenqid6w5/jj5tYpFP8WkYicAAIymCa/5157cf41ab647f31e20db895669eabea/OMS_Filtro2.png)
 
-After checking the filters, a URL will be generated in the browser with the parameters selected:![](//images.contentful.com/alneenqid6w5/WYPqJKIjwkuCO86SMU6sy/d5ad173798f8103c19990eed35709ecf/OMS_Filtro3.png)
+After checking the filters, a URL will be generated in the browser with the parameters selected:![](https://images.contentful.com/alneenqid6w5/WYPqJKIjwkuCO86SMU6sy/d5ad173798f8103c19990eed35709ecf/OMS_Filtro3.png)
 
 Then, you will need to decode the URL so that it can be interpreted by the REST interface.
 Using the [URL dencoder](http://meyerweb.com/eric/tools/dencoder/ "URL dencoder") tool, you can make adjustments manually and quickly.
 
-![](//images.contentful.com/alneenqid6w5/4j6WPSCXq084cMaIcQ8QsE/8dcab3bc07fd714af788cea586293f57/OMS_Filtro4.png)
+![](https://images.contentful.com/alneenqid6w5/4j6WPSCXq084cMaIcQ8QsE/8dcab3bc07fd714af788cea586293f57/OMS_Filtro4.png)
 
 Then, just copy the URL extension from “?” and paste it in the structure of origin to the URL of request.
 Ex.:` http://nomedaloja.vtexcommercestable.com.br/api/oms/pvt/orders/?orderBy=creationDate,desc&amp;f_creationDate=creationDate:[2014-09-03T03:00:00.000Z TO 2014-10-04T02:59:59.999Z]&amp;f_statusDescription=Pronto para o manuseio`
diff --git a/docs/tutorials/en/using-recaptcha-at-checkout.md b/docs/tutorials/en/using-recaptcha-at-checkout.md
index 559226624..cf3a9cb6b 100644
--- a/docs/tutorials/en/using-recaptcha-at-checkout.md
+++ b/docs/tutorials/en/using-recaptcha-at-checkout.md
@@ -53,16 +53,16 @@ You can use reCAPTCHA checkbox (v2). So, when applicable, the user should click
 ### Shopping experience with VTEX Criteria and reCAPTCHA v2
 
 The shopping experience with debit or credit cards tends to follow the flow below. It minimizes the occurrence of some types of fraud and attacks with minimal friction for the user.
-![reCAPTCHA scenariosEN](//images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/21964354890c244b42bc479983335b9d/reCAPTCHA_scenarios__1_.jpg)
+![reCAPTCHA scenariosEN](https://images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/21964354890c244b42bc479983335b9d/reCAPTCHA_scenarios__1_.jpg)
 As shown in the image above, there are different possible results in this flow:
 
 1. If the VTEX Criteria algorithm does not consider the session suspicious, the platform proceeds normally with the purchase.
 
 2. If the session is considered suspicious, the interface will display the reCAPTCHA Checkbox for the customer to select it. If reCAPTCHA does not consider the behavior suspicious when the Checkbox is selected, the purchase proceeds normally.
-![newCaptchaAnchor](//images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/10ed6d11b50a947a6186b549e27c4723/newCaptchaAnchor.gif)
+![newCaptchaAnchor](https://images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/10ed6d11b50a947a6186b549e27c4723/newCaptchaAnchor.gif)
 
 3. If reCAPTCHA considers the behavior suspicious, the interface will display the challenge.
-![desafio recaptcha](//images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/3156077db9ee243bea20308c304d183c/desafio_recaptcha.png)
+![desafio recaptcha](https://images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/3156077db9ee243bea20308c304d183c/desafio_recaptcha.png)
 
 4. If the challenge is successfully solved, the platform proceeds with the purchase. Otherwise, the behavior is considered compatible with that of a bot and the platform does not conclude the purchase.
 
diff --git a/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 350c2af95..1f84fe31d 100644
--- a/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -41,7 +41,7 @@ Apps that have a session dependency monitor changes to their inputs and modify s
 
 Transforms often trigger other transforms, repeating until no further parameter updates are sent by apps. This operation is, naturally, carefully monitored for loop conditions. The diagram below illustrates one such transform cycle:
 
-![EN - Session Manager](//images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
+![EN - Session Manager](https://images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
 
 1. A change was made to session parameter X
 2. App A was monitoring session parameter X, so that triggered Transform 1
diff --git a/docs/tutorials/en/using-the-homepage-of-the-admin-panel.md b/docs/tutorials/en/using-the-homepage-of-the-admin-panel.md
index 3b4df3aa2..9af9d7af2 100644
--- a/docs/tutorials/en/using-the-homepage-of-the-admin-panel.md
+++ b/docs/tutorials/en/using-the-homepage-of-the-admin-panel.md
@@ -28,7 +28,7 @@ The metrics section is divided into three large groups:
 - Payment data;
 - Catalog Data.
 
-![Action Dashboard](//images.contentful.com/alneenqid6w5/5ir6pwnlyMeQEeSOmOyisw/dcad530fb9c0004d32a89a3a6d5492ef/Action_Dashboard.png)
+![Action Dashboard](https://images.contentful.com/alneenqid6w5/5ir6pwnlyMeQEeSOmOyisw/dcad530fb9c0004d32a89a3a6d5492ef/Action_Dashboard.png)
 
 ### Bridge
 
@@ -64,4 +64,4 @@ It shows new VTEX Help articles, or those that have been updated recently.  We c
 
 Right below the articles, the **Info e Eventos** section shows the novelties about the platform, e-commerce hints, information on electronic commerce events and other disclosures made by VTEX. 
 
-![APIDocs](//images.contentful.com/alneenqid6w5/1GzmJz7qIwgm0kMq4smSk4/fb98a1d430346f559ada7800ad6cc321/APIDocs.png)
+![APIDocs](https://images.contentful.com/alneenqid6w5/1GzmJz7qIwgm0kMq4smSk4/fb98a1d430346f559ada7800ad6cc321/APIDocs.png)
diff --git a/docs/tutorials/en/validating-a-layout-before-moving-it-to-production.md b/docs/tutorials/en/validating-a-layout-before-moving-it-to-production.md
index 1e0bb650e..6205d6b38 100644
--- a/docs/tutorials/en/validating-a-layout-before-moving-it-to-production.md
+++ b/docs/tutorials/en/validating-a-layout-before-moving-it-to-production.md
@@ -34,7 +34,7 @@ With that you can:
 
 To find the `LID`, simply access the layout in the CMS module Admin. It's in the __Properties__ section, as the image below indicates:
 
-![lid](//images.contentful.com/alneenqid6w5/4FISyY6wwg2asGE4Mog2sK/991b8c634b474c336de1754acdb414de/lid.png)
+![lid](https://images.contentful.com/alneenqid6w5/4FISyY6wwg2asGE4Mog2sK/991b8c634b474c336de1754acdb414de/lid.png)
 
 To access the store page with the new layout, you must enter a question mark at the end of the URL and then the `LID` parameter.
 
@@ -53,7 +53,7 @@ Another alternative that allows you to test layout changes before moving to prod
 
 To find the `WID`, visit the web site. It sits on the first field of the webpage screen: __WebSite Id__.
 
-![wid](//images.contentful.com/alneenqid6w5/ghvd0wl9HqGu2KCWW2Yu2/5e27a13e79134f7ba89863ccd54031a6/wid.png)
+![wid](https://images.contentful.com/alneenqid6w5/ghvd0wl9HqGu2KCWW2Yu2/5e27a13e79134f7ba89863ccd54031a6/wid.png)
 
 Remember that although with the duplication of the web site you can change the layouts of the new web site independently, they will consume the same templates as the original web site. 
 
diff --git a/docs/tutorials/en/view-reindex-log.md b/docs/tutorials/en/view-reindex-log.md
index 52a3c928b..b2dfb9246 100644
--- a/docs/tutorials/en/view-reindex-log.md
+++ b/docs/tutorials/en/view-reindex-log.md
@@ -21,7 +21,7 @@ You may consult the log of when and who reindexed the base using the Full Clean
 
 In fact, any action taken on Full Clean Up is recorded on this page.
 
-![fullcleanupLog](//images.contentful.com/alneenqid6w5/4imYxqJjWwog0UYwCIcWY4/a036d799b6de9d34a2e2f810f3780929/fullcleanupLog.png)
+![fullcleanupLog](https://images.contentful.com/alneenqid6w5/4imYxqJjWwog0UYwCIcWY4/a036d799b6de9d34a2e2f810f3780929/fullcleanupLog.png)
 
 The log displays the following information for each action:
 - __Data__: date and time of action.
diff --git a/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md b/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md
index 58e2810db..a1ccd8930 100644
--- a/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md
+++ b/docs/tutorials/en/visao-geral-configuracoes-de-usuario.md
@@ -17,7 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 *User settings* is the name of a set of configurations applied to your personal profile in the Admin. It is not related to your store or your VTEX business account. To access this page, click on your __profile avatar__, which can be identified by the first letter of your email address, and click on __User Settings__.
 
-![Admin v4 User settings menu EN](//images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/3c37c9c64a2ff1832734671556b359b9/Admin_v4_User_settings_menu_EN.jpg)
+![Admin v4 User settings menu EN](https://images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/3c37c9c64a2ff1832734671556b359b9/Admin_v4_User_settings_menu_EN.jpg)
 
 On this page, soon to be included in Admin v4, you can perform the following actions:
 
diff --git a/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md b/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md
index 3474c45ba..0d7e2beb6 100644
--- a/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md
+++ b/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md
@@ -21,7 +21,7 @@ In the Catalog, products are organized by categories, and categories are organiz
 
 An example of a catalog structure would be as follows:
 
-![img como funciona o catalogo](//images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
+![img como funciona o catalogo](https://images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
 
 <div class = "alert alert-warning">
 Your categories tree does not need to have three levels. The hierarchy shown above is just an example. The amount of category levels to be created depends very much on the sector of activity of each store.
diff --git a/docs/tutorials/en/vtex-ad-network-beta.md b/docs/tutorials/en/vtex-ad-network-beta.md
index 19b1d8af1..87c960c8b 100644
--- a/docs/tutorials/en/vtex-ad-network-beta.md
+++ b/docs/tutorials/en/vtex-ad-network-beta.md
@@ -45,7 +45,7 @@ VTEX currently offers a single ad format: sponsored products. This means that pr
 
 Below, there's an example of how sponsored products are displayed:
 
-![vtex_ad_network_sponsored_EN](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/1abdea32c119ed4890e414ad7dbc8fea/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_EN](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/1abdea32c119ed4890e414ad7dbc8fea/vtex_ad_network_sponsored.png)
 
 Stores participating in **VTEX Ad Network** will be able to [configure the amount of ad space](https://help.vtex.com/en/tutorial/advertising-with-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse#creating-campaigns) available in each store context.
 
diff --git a/docs/tutorials/en/vtex-admin-start-here.md b/docs/tutorials/en/vtex-admin-start-here.md
index ed03e3000..e739ad2b7 100644
--- a/docs/tutorials/en/vtex-admin-start-here.md
+++ b/docs/tutorials/en/vtex-admin-start-here.md
@@ -18,7 +18,7 @@ subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 VTEX Admin allows merchants to manage their entire digital commerce experience in one place, in a simple and smart way. This is where they track orders, add products, set up fulfillment, and all the other aspects of a unified commerce operation.
 
 ## Homepage
-![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
 The homepage provides a high-level overview of your store, like a cockpit for your digital commerce operations, and for this reason it’s called  [Overview](https://help.vtex.com/en/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -28,7 +28,7 @@ As soon as you log in to the Admin, you will see useful metrics and charts to mo
 
 Our side navigation menu and top bar group similar categories together to reduce distractions and help your team find what they need faster. You can also use the search bar to find specific sections in the side menu.
 
-![admin navigation menu SEP2023](//images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/2569ef82429dd4bab5131004749acf22/admin-navigation.png)
+![admin navigation menu SEP2023](https://images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/2569ef82429dd4bab5131004749acf22/admin-navigation.png)
 
 You can use the global search bar on the topbar to search for VTEX Admin pages or orders from your store. By default, the search is configured as `Pages`. To search for an order, click on the bar, select `Orders`, and use one of the following criteria:
 
@@ -58,7 +58,7 @@ You can also use the search bar at the top of the VTEX Admin to find specific pa
 
 ### Information Center
 
-![information center admin SEP2023](//images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/3fe0b6fb2ef2ec7a54d546217515052c/Information_center.gif)
+![information center admin SEP2023](https://images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/3fe0b6fb2ef2ec7a54d546217515052c/Information_center.gif)
 
 This is where you can find all the useful links regarding the VTEX ecosystem to help you make the most of our platform. By clicking the <i class='fa fa-question-circle-o'></i> button on the top bar, you can access [Help Center](https://help.vtex.com), [Developer Portal](https://developers.vtex.com/), [Plataform Status](https://status.vtex.com/), [blog](https://vtex.com/en/blog/) and support pages.
 
@@ -69,7 +69,7 @@ The Give Feedback button allows users to send feedback about their experience on
 
 You will be directed to a Google form where you can give your feedback. After submitting it, you will receive a confirmation email.
 
-![Botão feedback - EN](//images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/90f7b35d3923b55047dfa200c2a1e7e1/Bot_o_feedback_-_EN.gif)
+![Botão feedback - EN](https://images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/90f7b35d3923b55047dfa200c2a1e7e1/Bot_o_feedback_-_EN.gif)
 
 #### Feedback form
 The main purpose of the feedback form questions is to collect detailed information about experiences and insights about the product in the VTEX Admin.
@@ -97,7 +97,7 @@ This feedback process should not be used to create a ticket or technical support
 
 ### User and Account Settings
 
-![avatar settings admin SEP2023](//images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/ee5a09f9a303042e1e83bb6ffa4e7982/Avatar_settings2.gif)
+![avatar settings admin SEP2023](https://images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/ee5a09f9a303042e1e83bb6ffa4e7982/Avatar_settings2.gif)
 
 Your profile avatar is a central hub for all your user and account settings. By clicking it, you can access your [User settings](https://help.vtex.com/en/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Account settings](https://help.vtex.com/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), and [Billing](https://help.vtex.com/en/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC) information, as well as change the language of your Admin, and log out.
 
diff --git a/docs/tutorials/en/vtex-admin-start-here1.md b/docs/tutorials/en/vtex-admin-start-here1.md
index 4dcb7597b..eee5e771d 100644
--- a/docs/tutorials/en/vtex-admin-start-here1.md
+++ b/docs/tutorials/en/vtex-admin-start-here1.md
@@ -18,30 +18,30 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 The Admin allows merchants to manage their entire digital commerce experience in one place, in a simple and smart way. 
 
 ## Homepage
-![Store Overview gif EN](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
+![Store Overview gif EN](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/27b257963a3bcd2e24374c78e8bcbc4a/Store_Overview_gif_EN.gif)
 
 The Admin homepage has been redesigned to provide a high-level overview of your store, like a cockpit for your digital commerce operations, and is now called [Overview](https://help.vtex.com/en/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
 As soon as you log in to the Admin, you will see useful metrics and charts to monitor your store's performance, such as revenue and number of orders, sales funnel and conversion rate, and the 10 highest grossing products.
 
 ## Enhanced Navigation 
-![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 Everything you need to manage your VTEX store is still available in the Admin, but now with a simpler interface. The side navigation menu and the top bar have been completely redesigned. Now, similar categories are grouped more clearly to reduce distractions and help your team find what they need faster. You can also use the search bar to find specific sections in the side menu.
 
 ### Information Center
-![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 This is where you can find all the useful links regarding the VTEX ecosystem to help you make the most of our platform. By clicking on the `?` button on the top bar, you can access the Help Center, Developer Portal, Platform Status, Blog, and support pages.
 
 ### Store Settings
 
-![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 For this experience, we have grouped the settings of all the Admin sections in one tab: [Store Settings](https://help.vtex.com/en/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Now, you can easily access all the settings that affect each service in your account.
 
 ### User and Account Settings
-![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 Your profile avatar, in the upper right corner, now displays all the settings related to your user and account. By clicking on your avatar, you can access your [User settings](https://help.vtex.com/en/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Account settings](https://help.vtex.com/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), and [Billing](https://help.vtex.com/en/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC) information, and you can also change the language of your Admin panel and logout. 
 
diff --git a/docs/tutorials/en/vtex-agreement.md b/docs/tutorials/en/vtex-agreement.md
index 219f06249..b381676ce 100644
--- a/docs/tutorials/en/vtex-agreement.md
+++ b/docs/tutorials/en/vtex-agreement.md
@@ -17,7 +17,7 @@ subcategory: 22TaEgFhwE6a6CG2KASYkC
 
 The VTEX Agreement, or Commercial Agreement, consists of two parts: the [MSA (Master Service Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/) and the **Appendix 1 Order** Form for the provision of services to companies, or the [MPA (Master Partner Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) and the **specific Terms and Conditions tailored for the partnership**.
 
-![VTEX Agreement](//images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/0927a3945c933046bc6eae8ba1fd0ced/En.png)
+![VTEX Agreement](https://images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/0927a3945c933046bc6eae8ba1fd0ced/En.png)
 
 The [Master Service Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/) and the [Master Partner Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) are the main service and partnership agreements, respectively. They regulate the relationship between VTEX and its customers or partners. Both vary based on the region in which the company or partner is located.
 
diff --git a/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
index 6ce3ed4ac..b25fd7022 100644
--- a/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
+++ b/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
@@ -34,7 +34,7 @@ Below are some tips to best leverage this feature:
 
 Start by setting the desired time zone and selecting the store you want to monitor in the real-time Overview.    
 
-![timezone-en](//images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/3693d76ead0495c35a66f8c099d60f9c/timezone-en.png)  
+![timezone-en](https://images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/3693d76ead0495c35a66f8c099d60f9c/timezone-en.png)  
 
 ### Reference filter  
 
@@ -51,19 +51,19 @@ To configure the reference filter, follow these steps:
 A useful comparison during Black Week is with the same date last year. In the reference filter, select a date between November 21, 2022 and November 27, 2022, ideally the same days of the week. <br>This option is available for clients who were already using the VTEX platform during that period last year.</br>
 </div>
 
-![reference-en](//images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/2d4ca5424f4c45e4e8104f37ca11186d/reference-en.png)
+![reference-en](https://images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/2d4ca5424f4c45e4e8104f37ca11186d/reference-en.png)
 
 ### View filter  
 
 - **Track the day’s performance with the cumulative view:** Use the **cumulative view** to monitor the sales performance of your ecommerce website minute by minute. This will provide insights that will enable quick operation adjustments.  
 To select the **cumulative view** in the dashboard, click **View<i class="fas fa-angle-down"></i> > Accumulated.**  
 
-![accumulated-en](//images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/573168bd8086f888f6f98cddc84c0e6c/accumulated-en.png)
+![accumulated-en](https://images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/573168bd8086f888f6f98cddc84c0e6c/accumulated-en.png)
 
 - **Track performance in the last hours:** **The Last 2 hours view** shows the metrics isolated minute by minute, which is important for guaranteeing the operational stability of your store during the event.  
 To select **Last 2 hours** in the dashboard, click **View<i class="fas fa-angle-down"></i> > Last 2 hours.**  
 
-![hours-en](//images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/119053d48e6874dcfd5905473e754c17/hours-en.png)
+![hours-en](https://images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/119053d48e6874dcfd5905473e754c17/hours-en.png)
 
 ### Metrics  
 
@@ -71,7 +71,7 @@ The real-time Overview provides important insights into your sales strategy. For
 
 To view the best-selling products, in the **Metrics** section click the <i class="fas fa-ellipsis-v"></i> button and select **Best-selling products.**  
 
-![best-selling-en](//images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/61ac987b15602d8dfd633019a448fa04/best-selling-en.png)
+![best-selling-en](https://images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/61ac987b15602d8dfd633019a448fa04/best-selling-en.png)
 
 <div class="alert alert-warning">
 For analyzing or monitoring longer periods, we recommend using our Sales Performance dashboard, which will be explained in the next question.
@@ -86,7 +86,7 @@ The VTEX Sales Performance dashboard is the right tool for normal monitoring of
 - **Date**  
 When you go to the dashboard, the first step is to set the date for **Main period** and **Compared with.** If you’re running an analysis after Black Week, select Last week to compare with last year's Black Week (available if you were a VTEX client at that time). During Black Week, select Custom date and set the specific days to analyze.  
 
-![sales-date-en](//images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/05805210036ffecd73251cc0d8581eb7/sales-date-en.png)  
+![sales-date-en](https://images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/05805210036ffecd73251cc0d8581eb7/sales-date-en.png)  
 
 - **Combined filters**  
 The data displayed on the Sales Performance dashboard can be segmented using combined filters, such as category. To add a new filter, follow the steps below:  
@@ -98,7 +98,7 @@ The data displayed on the Sales Performance dashboard can be segmented using com
 
 You can explore other filters based on the needs and specific aspects of your ecommerce operation.  
 
-![add-filter-en](//images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/fa01df4adc0b1a05a20225da3ccb7bc8/add-filter-en.png)  
+![add-filter-en](https://images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/fa01df4adc0b1a05a20225da3ccb7bc8/add-filter-en.png)  
 
 ### Metrics  
 
@@ -111,22 +111,22 @@ During Black Week, this dashboard can be used to analyze the following performan
 - Average ticket (approved)
 - Orders (canceled)  
 
-![change-metric-en](//images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/c08adbff229f6ff0116568228b741bdf/change-metric-en.png)  
+![change-metric-en](https://images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/c08adbff229f6ff0116568228b741bdf/change-metric-en.png)  
 
 - **Week’s performance**  
 After making adjustments, compare the current week's performance with last year's Black Week to identify trends and opportunities.  
 
-![week-performance-en](//images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/993675a67d0bb68327994f5250fa8d9d/week-performance-en.png)    
+![week-performance-en](https://images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/993675a67d0bb68327994f5250fa8d9d/week-performance-en.png)    
 
 - **Table analysis**  
 Analyze the breakdown table for deeper insights. For example, SKU analysis can reveal which products should be highlighted in future campaigns.  
 
-![table-analysis-en](//images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/c9a20889c76d79221b42972fd1c1dc5c/table-analysis-en.png)  
+![table-analysis-en](https://images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/c9a20889c76d79221b42972fd1c1dc5c/table-analysis-en.png)  
 
 - **Save your view**  
 Save your dashboard configuration for future queries. Click **Sales Management > <i class="fas fa-plus"></i>  > Add a name > `Create`** to save your custom view.  
 
-![create-view-en](//images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/aefb269aa88b6c50dcf98fa2a92ad197/create-view-en.png)    
+![create-view-en](https://images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/aefb269aa88b6c50dcf98fa2a92ad197/create-view-en.png)    
 
 ## Why are my metrics different from the Orders page in the Admin?  
 
@@ -137,7 +137,7 @@ There are several reasons why metrics in the real-time Overview might differ fro
 - Different refresh rates: The Overview page refreshes every 1 to 3 minutes. Therefore, a slight discrepancy (1 to 3% of the total) between the two pages is common.  
 - Revenue calculation formula: The metrics in Overview don’t consider discounts, shipping, surcharges, and promotions in the revenue calculation, while the Orders page does take these factors into account.  
 
-![change-store-en](//images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/1951bcca25915d306c0062c2d69ed361/change-store-en.png)
+![change-store-en](https://images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/1951bcca25915d306c0062c2d69ed361/change-store-en.png)
 
 To see the data from all stores, use the Sales Performance page, which shows aggregated data with an approximate refresh rate of 90 minutes.  
 
@@ -145,11 +145,11 @@ To see the data from all stores, use the Sales Performance page, which shows agg
   If your operation uses more than one currency, the <b>Overview dashboard</b> will sum your orders in the currency that is most used in your sales. <br>To make a comparison with the <b>Orders</b> page, you need to sum the order total from all your currencies.</br>
   </div>
 
-![all-orders-en](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
+![all-orders-en](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
 
 - **Time zone:** This filter is available in **Overview.** If you use a time zone that is different from the Orders page default (which is your current time zone), the metrics will not match. Adjust the time zone as needed.  
 
-![timezone-en](//images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/2a62c6b5c8883593286347b27a87fb6d/sales-timezone-en.png)  
+![timezone-en](https://images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/2a62c6b5c8883593286347b27a87fb6d/sales-timezone-en.png)  
 
 ## Why don't I have session or conversion rate data?  
 
@@ -159,7 +159,7 @@ However, it’s important to note that our script does not capture data from ses
 
 If you notice this data is missing, it may be due to these limitations. We recommend checking the script settings and any frontend customizations that might be affecting data capture.  
 
-![sales-overview-en](//images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/a3b342736ed0ba9f09c79eed98be6066/sales-overview-en.png)  
+![sales-overview-en](https://images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/a3b342736ed0ba9f09c79eed98be6066/sales-overview-en.png)  
 
 ## Why don't my conversion rate, new sessions, or sales funnel metrics match the numbers from my internal tools?  
 
@@ -177,8 +177,8 @@ To determine which currency to display, we assess the most used currency in onli
 
 As a result, if you operate with more than one currency, you need to sum the total orders from the Admin Orders page across all your currencies to match the order data shown in the real-time Overview.  
 
-![all-orders-en](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
-![monitoring-en](//images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/97d4da4d04313aec7d1cdd95de40378b/monitoring-en.png)  
+![all-orders-en](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
+![monitoring-en](https://images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/97d4da4d04313aec7d1cdd95de40378b/monitoring-en.png)  
 
 ## Why doesn’t the number of orders in the sales funnel analysis match the Monitoring section?  
 
@@ -188,8 +188,8 @@ On the other hand, the data from the sales funnel is collected from the site's n
 
 As a result, it is common for the number of orders in the sales funnel to be lower than the Monitoring section, which provides a broader view of store sales, including channels outside the VTEX platform.  
 
-![conversation-rate-en](//images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/0e640c18f48f1d6576b2b366e5a26f34/conversation-rate-en.png)  
-![new-sessions-en](//images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/fd44b2bc0036ac47ea0421bcb74b36b8/new-sessions-en.png)  
+![conversation-rate-en](https://images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/0e640c18f48f1d6576b2b366e5a26f34/conversation-rate-en.png)  
+![new-sessions-en](https://images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/fd44b2bc0036ac47ea0421bcb74b36b8/new-sessions-en.png)  
 
 ## Why is the new Overview in a separate URL?  
 
diff --git a/docs/tutorials/en/vtex-do-interface.md b/docs/tutorials/en/vtex-do-interface.md
index 1db8b2e6a..bad5bf9be 100644
--- a/docs/tutorials/en/vtex-do-interface.md
+++ b/docs/tutorials/en/vtex-do-interface.md
@@ -17,7 +17,7 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 VTEX DO manages tasks automatically created by the VTEX Admin that require manual action by the ecommerce team. To access it, log in to your VTEX Admin, go to **Orders > [All orders](https://help.vtex.com/en/tutorial/lista-de-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**, and click on the inbox icon in the bottom right corner of the page. By clicking on the icon, a modal will display the list of tasks related to the store's orders. 
 
-![VTEX Do overview EN](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
+![VTEX Do overview EN](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
 
 <div class = "alert alert-info">
 Only users with the <a href = "https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> role can perform tasks through VTEX DO.
@@ -115,7 +115,7 @@ Tasks managed through VTEX DO can include messages from all VTEX systems. Some e
 
 ## Task details
 
-![VTEX Do details EN](//images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/9bb5a8bb66f10645c751d11ae95b4ee0/VTEX_Do_details_EN.jpg)
+![VTEX Do details EN](https://images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/9bb5a8bb66f10645c751d11ae95b4ee0/VTEX_Do_details_EN.jpg)
 
 By clicking on the name of a task in the list, you are redirected to the task details modal, which displays more information about the task and actions to solve it. The following fields are displayed:
 
diff --git a/docs/tutorials/en/vtex-insurance.md b/docs/tutorials/en/vtex-insurance.md
index 302c73d66..133a613ed 100644
--- a/docs/tutorials/en/vtex-insurance.md
+++ b/docs/tutorials/en/vtex-insurance.md
@@ -61,7 +61,7 @@ After installing VTEX Insurance, you need to complete the Catalog setup to cover
 
 7. [Create an insurance product](https://help.vtex.com/en/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By).
 
-8. [Create insurance SKUs](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY). We recommend creating more than three SKUs for each insurance.![Insurance - SKUs](//images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/e1b53a46f844d679277074c59386b0de/image3.png)
+8. [Create insurance SKUs](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY). We recommend creating more than three SKUs for each insurance.![Insurance - SKUs](https://images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/e1b53a46f844d679277074c59386b0de/image3.png)
 
 9. [Bind the created SKUs](https://help.vtex.com/en/tutorial/sku-bindings--1SmrVgNwjJX17hdqwLa0TX) to the Assurant seller.
 
@@ -77,7 +77,7 @@ After setting up the catalog, your store will have the products bound to insuran
 Follow the steps below to set up your VTEX Insurance app.
 
 ### Company Information
-![Insurance Configuration](//images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/b779f15fc609605bb8c26452fa596251/image5.png)
+![Insurance Configuration](https://images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/b779f15fc609605bb8c26452fa596251/image5.png)
 1. Complete the following information:
 - **Email**: Store email.
 - **Name**: Store name.
@@ -92,7 +92,7 @@ Follow the steps below to set up your VTEX Insurance app.
 
 ### Items bound to insurance items
 
-![Items Bound to Source Items](//images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/3aa3ac21584d7226965e0584eb738150/image2.png)
+![Items Bound to Source Items](https://images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/3aa3ac21584d7226965e0584eb738150/image2.png)
 
 1. Select the codes that correspond to the insurance types you want for the collection you have created.
 
@@ -102,14 +102,14 @@ If you want to bind more than one insurance plan, such as **Theft and Qualified
 
 ### Warranty field name
 
-![Warranty Field Name](//images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/c7440e8c3189d41c05d3a837cec3e273/image8.png)
+![Warranty Field Name](https://images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/c7440e8c3189d41c05d3a837cec3e273/image8.png)
 
 1.  Specify the manufacturer's warranty field, indicating the name of the warranty used in the catalog.
 
 2.  Click `Submit`.
 
 ### Insurance attachment setup
-![Insurance Attachement Setup](//images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/0cc20efa1f556b1cd5ed82e97f456ced/insurance_attachement_setup.png)
+![Insurance Attachement Setup](https://images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/0cc20efa1f556b1cd5ed82e97f456ced/insurance_attachement_setup.png)
 
 1. [Add an](https://help.vtex.com/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU) attachment for Assurant with the information received from the support team when contracting the service.
 
@@ -120,7 +120,7 @@ If you want to bind more than one insurance plan, such as **Theft and Qualified
 4. Click `Save`.
 
 ### Manual pricing setup
-![Manual Pricing](//images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/c35b802ce82a4b0ddb077c7d62cae53e/image11.png)
+![Manual Pricing](https://images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/c35b802ce82a4b0ddb077c7d62cae53e/image11.png)
 
 1. [Activate the manual pricing](https://help.vtex.com/en/tutorial/change-the-price-of-an-item-in-the-shopping-cart--7Cd37aCAmtL1qmoZJJvjNf) in your store.
 
diff --git a/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
index 1f669d450..a9402080e 100644
--- a/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -43,7 +43,7 @@ VTEX Intelligent Search: Multilanguage allows you to customize the search experi
 ### Merchandising rules
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Merchandising Rules — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Merchandising rules__ —  will contain the additional __Locales__ field, which allows you to choose the locales to which the Merchandising Rules will apply, as shown in the image below.
 
-![img regrasmerch intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/1ff4219f9c71ad2dfe0ed7b897268a94/01-merchrules-en.png)
+![img regrasmerch intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/1ff4219f9c71ad2dfe0ed7b897268a94/01-merchrules-en.png)
 
 To learn more about this field, read our article on [how to configure Merchandising rules in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8).
 
@@ -57,7 +57,7 @@ You can configure Synonyms for a multi-language store in the Admin by filling ou
 #### Creating Synonyms via form
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Synonyms (available through — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Synonyms__ —  will contain the additional __Locales__ field, which allows you to choose the locales to which the Synonyms will apply, as illustrated in the image below. Click on the languages you want to select.
 
-![img sinonimos intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/eea0dbf7bf687c0c952599a555ef35fd/image_3.png)
+![img sinonimos intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/eea0dbf7bf687c0c952599a555ef35fd/image_3.png)
 
 To learn more about this field, read our article on [how to configure Synonyms in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
@@ -81,7 +81,7 @@ To learn more about importing Synonyms spreadsheets, read our article on [how to
 
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Redirects — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Redirects__ —  will contain the additional __Locales__ field, which allows you to choose which locales the Redirects will apply to, as illustrated in the image below. Click on the languages you want to select.
 
-![img redirecionamentos intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/abd1dc44643c8c89b6165e5c304ba97b/03-redirecionamento-es.png)
+![img redirecionamentos intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/abd1dc44643c8c89b6165e5c304ba97b/03-redirecionamento-es.png)
 
 To learn more about this field, read our article on [how to configure Redirects in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4Gd2wLQFbCwTsh8RUDwSoL).
 
@@ -89,6 +89,6 @@ To learn more about this field, read our article on [how to configure Redirects
 
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Banners — available on VTEX Admin through __Storefront__ > __Banners__ —  will contain the additional __Locales__ field, which allows you to choose which locales the Banners will apply to, as illustrated in the image below. Click on the languages you want to select.
 
-![img banner intelligentsearchmultilanguage EN](//images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8c927f2f9eb629778e628333ce788575/image_10.png)
+![img banner intelligentsearchmultilanguage EN](https://images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8c927f2f9eb629778e628333ce788575/image_10.png)
 
 To learn more about this field, read our article on [how to configure Banners in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
diff --git a/docs/tutorials/en/vtex-invoice-notifier.md b/docs/tutorials/en/vtex-invoice-notifier.md
index e5f15d01b..a6d3ab7a8 100644
--- a/docs/tutorials/en/vtex-invoice-notifier.md
+++ b/docs/tutorials/en/vtex-invoice-notifier.md
@@ -15,7 +15,7 @@ legacySlug: vtex-invoice-notifier
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-![chart EN](//images.ctfassets.net/alneenqid6w5/3OMTqAs3Zhp1GFeBEtX8q0/4bcd68580be161fc3e98fc2877357e1a/chart.jpg_h_250)
+![chart EN](https://images.ctfassets.net/alneenqid6w5/3OMTqAs3Zhp1GFeBEtX8q0/4bcd68580be161fc3e98fc2877357e1a/chart.jpg_h_250)
 
 ## App installation - VTEX Invoice Notifier
 
@@ -25,7 +25,7 @@ User should install the App from VTEX App Store - app.vtex.com
 
 When proceeding with the installation, a setup page will appear, in which the user should insert the endpoint responsible for communication with the invoice issuing system.
 
-![install-app](//images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
+![install-app](https://images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
 
 ## OMS notify invoice issuer
 
@@ -33,9 +33,9 @@ Once the endpoint is added to the App, OMS recognizes that the store is able to
 
 In the order, the operator must select the already invoiced package or items and create a new notification: 
 
-![notify-invoicer1](//images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
+![notify-invoicer1](https://images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
 
-![notify-invoicer2](//images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
+![notify-invoicer2](https://images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
 
 When the OMS user clicks the __Request Invoice__ button, the app would perform a POST request to the registered App endpoint with the following BODY example:
 
@@ -57,7 +57,7 @@ This property should be used to know which address sends the Invoice.
 
 Once successfully notified, the APP records this notification in VBASE (databank).
 
-![callBackProperty](//images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
+![callBackProperty](https://images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
 
 ## Invoice issuer gets invoice details
 
@@ -168,7 +168,7 @@ Pickup orders may or may not contain a client's identification. An order placed
 
 The way to identify if an order is Delivery or Pickup is by looking at the __shippingData.logisticsInfo[0].deliveryChannel__ object.
 
-![shipping-type](//images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
+![shipping-type](https://images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
 
 ## Inserting the tax invoice into an order
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-insights.md b/docs/tutorials/en/vtex-pick-and-pack-insights.md
index 83227437a..cc0cb685e 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-insights.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-insights.md
@@ -21,7 +21,7 @@ This feature is in closed beta, so only selected customers can access it now. If
 
 **Insights** is a VTEX Admin page that displays information about your store's performance regarding VTEX Pick and Pack.
 
-![pick-pack-insights-en](//images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/147307180023927ebf3a6b7fce67583e/image.png)
+![pick-pack-insights-en](https://images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/147307180023927ebf3a6b7fce67583e/image.png)
 
 This page includes the following sections:
 
@@ -40,7 +40,7 @@ In this section, you will see the total number of orders or worksheets for a giv
 * Last 3 months
 * Last 6 months
 
-![pick-pack-insights-2-en](//images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/78201db1138e08681fd53e5e1936bcd2/image.png)
+![pick-pack-insights-2-en](https://images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/78201db1138e08681fd53e5e1936bcd2/image.png)
 
 ## Time on each step
 
@@ -50,16 +50,16 @@ In this section, you will find information regarding the duration of each step i
 * Time in Packing
 * Time in Shipping
 
-![pick-pack-insights-3-en](//images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/bbe1920023985fcaeb319696c4990efe/image.png)
+![pick-pack-insights-3-en](https://images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/bbe1920023985fcaeb319696c4990efe/image.png)
 
 ## Orders - Order Performance
 
 In this section, you will see information on the overall order performance and the average fulfillment time for each order.
 
-![pick-pack-insights-4-en](//images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/d94b159d309b0412229a89e7c5901a7e/image.png)
+![pick-pack-insights-4-en](https://images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/d94b159d309b0412229a89e7c5901a7e/image.png)
 
 ## Items
 
 In this section, you will see information about the order items managed in VTEX Pick and Pack, the average picking time per item, the number of items picked by picker, and the order fulfillment rate.
 
-![pick-pack-insights-5-en](//images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/eb0fceee067533570ddbf10ec4f3a0fd/image.png)
+![pick-pack-insights-5-en](https://images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/eb0fceee067533570ddbf10ec4f3a0fd/image.png)
diff --git a/docs/tutorials/en/vtex-pick-and-pack-mobile.md b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
index 3945b240a..21c404a0e 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
@@ -21,7 +21,7 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 
 The [VTEX Pick and Pack](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) mobile app helps the picker — the person who picks and packs items in the facility — handle orders, from picking to shipping. This makes the store's order picking and delivery flow smoother and more efficient.
 
-![pickpack-mobile-en](//images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/c130518e5a14f76ca2ee9268bc298d92/image.png)
+![pickpack-mobile-en](https://images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/c130518e5a14f76ca2ee9268bc298d92/image.png)
 
 Order handling is divided into four steps, following the usual store order flow:
 
@@ -55,7 +55,7 @@ Worksheets only apply to the order picking and packing steps. You must ship each
 
 The __Unassigned__ tab lists the orders that should be selected for [worksheets](#worksheets). 
 
-![pickpack-ordemservico-en](//images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/fe3519449de97380728a84ea34d7ba86/image.png)
+![pickpack-ordemservico-en](https://images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/fe3519449de97380728a84ea34d7ba86/image.png)
 
 To create a worksheet, follow the steps below:
 
@@ -71,7 +71,7 @@ The picking step consists of manually selecting the items listed in a [worksheet
 
 The Pending tab displays the list of worksheets that have not been picked yet.
 
-![pickpack-pendente-en](//images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/0b818a175fc5f290de6f37e1cff2d16f/image.png)
+![pickpack-pendente-en](https://images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/0b818a175fc5f290de6f37e1cff2d16f/image.png)
 
 In this tab, you can select the worksheet ID if you only want to see the picked items from that order.
 
@@ -87,7 +87,7 @@ When clicking a worksheet, the following information is displayed:
 - __Info:__ General information about the worksheet and the order.
 - __Summary:__ Products that have already been picked.
 
-![pickpack-em-separacao-en](//images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/53ee187d9cf252ce233ab2c5b5c2b9ea/image.png)
+![pickpack-em-separacao-en](https://images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/53ee187d9cf252ce233ab2c5b5c2b9ea/image.png)
 
 By clicking the <i class="fas fa-ellipsis-v"></i> menu, the following options will be displayed:
 
@@ -103,7 +103,7 @@ To pick a product, follow the steps below:
 1. On the Picking screen, go to the __Items__ tab.
 2. Click the product you want to pick or drag the product to the right. If the product has more than one unit, you need to click the number of units. For products with weight or volume, confirm the measurements first, then confirm your selection, as shown in the example below.
 
-![pickpack-item-en](//images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/de6e921ac69b112aee8ac14a81810c60/image.png)
+![pickpack-item-en](https://images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/de6e921ac69b112aee8ac14a81810c60/image.png)
 
 To pick all the products from the worksheet at once, follow these steps:
 
@@ -166,14 +166,14 @@ After all items on the worksheet have been picked, rejected, or replaced, click
 
 During packing, the picker organizes order items into their respective shipping packages.  The Pick and Pack mobile app allows you to organize all the packages needed for multiple orders easily.
 
-![pickpack-empacotamento-en](//images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/a12a99b9e9988032ac4b4950d1f85f01/image.png)
+![pickpack-empacotamento-en](https://images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/a12a99b9e9988032ac4b4950d1f85f01/image.png)
 
 You can access the Packing page once you have [completed picking](#completing-the-picking-process) the items on a worksheet or by following these steps:
 
 1. On the app's initial screen, click **To pack**. A list will be displayed with the [worksheets](#worksheets) assigned to the picker in the packing step.
 2. Click the worksheet you want to start picking. 
 
-![pickpack-item-pendente-en](//images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/e3b58759bf7b7dfed1a7232f302bda2b/image.png)
+![pickpack-item-pendente-en](https://images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/e3b58759bf7b7dfed1a7232f302bda2b/image.png)
 
 Follow the steps below to pack items:
 
@@ -190,10 +190,10 @@ You need to repeat this procedure as many times as necessary to pack all the ite
 The packed items will be displayed on the **Packed Items** tab. You can switch between viewing items as a list or by orders and packages by clicking <i class="fas fa-toggle-on"></i>.
 
 __Item list__
-![pickpack-item-empacotado-en](//images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/ec354b5f4e8e0dbce8102dac4bdc554e/image.png)
+![pickpack-item-empacotado-en](https://images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/ec354b5f4e8e0dbce8102dac4bdc554e/image.png)
 
 __Orders and packages__
-![pickpack-item-empacotado-2-en](//images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/893b8268f9e01e764ca6f952852af1d1/image.png)
+![pickpack-item-empacotado-2-en](https://images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/893b8268f9e01e764ca6f952852af1d1/image.png)
 
 After packing all items listed in the worksheet, complete the packing process on the Packed Items tab by clicking the `Confirm Packing` button.
 
@@ -215,7 +215,7 @@ To ship packages using the Pick and Pack app, follow the steps below:
 4. Complete all shipping information:
     - **Expected pickup date**
     - **Expected delivery date**
-    ![pickpack-envio-en](//images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/91bf904272cdd0c22037fafa64e273a4/image.png)
+    ![pickpack-envio-en](https://images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/91bf904272cdd0c22037fafa64e273a4/image.png)
 5. Select a carrier.
 6. Click `Select and Continue`.
 7. Confirm the shipping information. If no corrections are needed, click the `Create Service` button. If not, click `Back` and go back to step 5. 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-orders.md b/docs/tutorials/en/vtex-pick-and-pack-orders.md
index 52eeffe0e..c8d691118 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-orders.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-orders.md
@@ -28,7 +28,7 @@ This page allows you to:
 - [Filter orders](#filtering-orders)
 - [Export orders](#exporting-orders)
 
-![pick-and-pack-pedidos-EN](//images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/3ffa21f585d6c45e374ac2fb9c42f8aa/image.png)
+![pick-and-pack-pedidos-EN](https://images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/3ffa21f585d6c45e374ac2fb9c42f8aa/image.png)
 
 The page displays the following information in a table:
 
@@ -55,7 +55,7 @@ You can optimize order search by using the following tabs:
 
 You can also find more detailed information about each order by clicking the respective order in the table.
 
-![pick-and-pack-pedidos-2-EN](//images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/3f3ba4f4f9caac0b31d041afb33ce8b0/image.png)
+![pick-and-pack-pedidos-2-EN](https://images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/3f3ba4f4f9caac0b31d041afb33ce8b0/image.png)
 
 By selecting the desired order, you will see the following information:
 
@@ -90,5 +90,5 @@ You can export orders by following the steps below:
 1. Click `Export`.
 2. Select the information you want to export: `Package Report` or `Order Report`.
     * For the `Package Report`, select the date range you want to export, the shipping type, and the shipping method.
-![pick-and-pack-pedidos-3-EN](//images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/391f380bce100cf14645602f81b3fc9f/image.png)
+![pick-and-pack-pedidos-3-EN](https://images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/391f380bce100cf14645602f81b3fc9f/image.png)
 3.  Click `Export`.
diff --git a/docs/tutorials/en/vtex-pick-and-pack-settings.md b/docs/tutorials/en/vtex-pick-and-pack-settings.md
index 4b0210899..4ec3db685 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-settings.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-settings.md
@@ -34,7 +34,7 @@ This feature is in closed beta, so only selected customers can access it now. If
 
 In this tab, you'll find the settings related to the picking of order items. Here, you can set actions the picker can take during the picking process, including notifying you that an order item is unavailable and suggesting replacements.
 
-![pick-and-pack-separacao-en](//images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/0b5dd839ffadbb4fc7670bae7b6a1e27/image.png)
+![pick-and-pack-separacao-en](https://images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/0b5dd839ffadbb4fc7670bae7b6a1e27/image.png)
 
 ### Picking Strategy
 
@@ -93,7 +93,7 @@ Click `Save` to save the changes.
 
 On this tab, you can configure the order of the categories in which the orders will be picked. This enables the picker to manage the order picking process efficiently.
 
-![pick-pack-categorias-en](//images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/1399599a366ab0232398093187d11eaa/image.png)
+![pick-pack-categorias-en](https://images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/1399599a366ab0232398093187d11eaa/image.png)
 
 * **Fast configuration**: Applies the settings to all facilities. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
 * **Facility**: Determines the facility to which the category settings will be applied.
@@ -105,7 +105,7 @@ You can import a CSV file or export the already configured list.
 ## Packing
 In this tab, you will find the packing settings for order items.
 
-![pick-pack-empacotamento-en](//images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/af91942f280c2312c521db86060c706e/image.png)
+![pick-pack-empacotamento-en](https://images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/af91942f280c2312c521db86060c706e/image.png)
 * **Allow package reports**: Enables the visualization of the package report, which will be displayed on the Orders screen. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
 * **Allow automatic packing**: Allows automatic packaging of orders. You can enable <i class="fas fa-toggle-on"></i> or disable <i class="fas fa-toggle-off"></i> this option.
 
@@ -172,7 +172,7 @@ Click `Save` to save the changes.
 
 In this tab, you will find settings for orders processed by VTEX Pick and Pack.
 
-![pick-pack-config-pedidos-en](//images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/557e12764b6dc82064c62cc8e9f6a405/image.png)
+![pick-pack-config-pedidos-en](https://images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/557e12764b6dc82064c62cc8e9f6a405/image.png)
 
 * **Download Orders From OMS**: Allows exporting orders from the OMS.
 * **Payment methods**: Payment methods used in the orders being exported.
@@ -186,7 +186,7 @@ Click `Save` to save the changes.
 
 In this tab, you will find the automation settings for VTEX Pick and Pack processes.
 
-![pick-pack-automacao-en](//images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/5bdf2473a93291bf2c839415872f4805/image.png)
+![pick-pack-automacao-en](https://images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/5bdf2473a93291bf2c839415872f4805/image.png)
 
 To create a new automation, follow the steps below:
 
@@ -198,7 +198,7 @@ To create a new automation, follow the steps below:
 
 In this tab, you can manage users, admins, and pickers from your VTEX Pick and Pack operation. Users with Admin permission will have access to the VTEX Admin and be able to make changes within the tool. Users with Picker permission can only access the VTEX Pick and Pack app.
 
-![pick-pack-usuarios-en](//images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/445bb2e98986273d4fbd0afba11a6310/image.png)
+![pick-pack-usuarios-en](https://images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/445bb2e98986273d4fbd0afba11a6310/image.png)
 
 To create a new user, follow the steps below:
 
@@ -208,7 +208,7 @@ To create a new user, follow the steps below:
   * __Admin__ permission
     1. Select the listed user you want to add as __Admin__.
     2. Click `Create`.
-    ![pick-pack-usuarios-2-en](//images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/b91e3d2d4268d779b7df0453d8cbf7c1/image.png)
+    ![pick-pack-usuarios-2-en](https://images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/b91e3d2d4268d779b7df0453d8cbf7c1/image.png)
   * __Picker__ permission
     1. Complete the form with the following information:
        * User name
@@ -219,13 +219,13 @@ To create a new user, follow the steps below:
        * Allow shipping packages
        * Categories
     2. Click `Create`.
-    ![pick-pack-usuarios-3-en](//images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/5ab7dd935ac929c4c3bd2c2f7feac3af/image.png)
+    ![pick-pack-usuarios-3-en](https://images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/5ab7dd935ac929c4c3bd2c2f7feac3af/image.png)
 
 ## Catalog
 
 In this tab, you can access information about items in orders that are currently in the shipping stage.
 
-![pick-pack-catalogo-en](//images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/846976dd5b8fab2a93d32264334f9686/image.png)
+![pick-pack-catalogo-en](https://images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/846976dd5b8fab2a93d32264334f9686/image.png)
 
 The page displays the following information in a table:
 
@@ -258,7 +258,7 @@ Indexing the catalog will delete and recreate all its contents, so you could los
 
 In this tab, you will be able to add and view your store's facilities.
 
-![pick-pack-instalacoes-en](//images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/3c3a6b90a27abf2d6144ae505a64d46c/image.png)
+![pick-pack-instalacoes-en](https://images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/3c3a6b90a27abf2d6144ae505a64d46c/image.png)
 
 To create a new facility, follow these steps:
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-worksheets.md b/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
index 09a1bdf1f..6ce73ba93 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
@@ -27,11 +27,11 @@ This page allows you to:
 * [Search for worksheets](#search-for-worksheets)
 * [Filter worksheets](#filter-worksheets)
 
-![pick-pack-ordem-servico-en](//images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/f2df0910a4b7c2b1be73553b20394536/image.png)
+![pick-pack-ordem-servico-en](https://images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/f2df0910a4b7c2b1be73553b20394536/image.png)
 
 Orders are displayed in cards with the following information:
 
-![pick-pack-ordem-servico-2-en](//images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/d0d6b35257db31e3b166b8a30edd83ed/image.png)
+![pick-pack-ordem-servico-2-en](https://images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/d0d6b35257db31e3b166b8a30edd83ed/image.png)
 
 * Worksheet ID.
 * Number of orders in the worksheet.
@@ -49,7 +49,7 @@ You can create a new worksheet by following the steps below:
 3. Click the **Manual** tab to create the worksheet manually.
 4. Click the `+` icon to create a worksheet. You can create more than one worksheet.
 5. Drag the orders you want to add to the worksheet.
-  ![pick-pack-ordem-servico-3-en](//images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/e0acc7025f39b107b668caca52555544/image.png)
+  ![pick-pack-ordem-servico-3-en](https://images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/e0acc7025f39b107b668caca52555544/image.png)
 6. Click `Create`.
 
 ## Viewing worksheets
@@ -64,7 +64,7 @@ You can optimize the worksheet query from the following tabs:
 
 You can also view more worksheet details by clicking the <i class="fas fa-chevron-down"></i> button on the card.
 
-![pick-pack-ordem-servico-4-en](//images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/bdf69bd28c64d9ff9e855c08d9e26645/image.png)
+![pick-pack-ordem-servico-4-en](https://images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/bdf69bd28c64d9ff9e855c08d9e26645/image.png)
 
 ## Searching for a worksheet
 
diff --git a/docs/tutorials/en/vtex-shipping-network-dashboard.md b/docs/tutorials/en/vtex-shipping-network-dashboard.md
index e37c646a1..722e45ce3 100644
--- a/docs/tutorials/en/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/en/vtex-shipping-network-dashboard.md
@@ -59,7 +59,7 @@ For calculating the performance, the system considers all packages for delivery.
 
 Carrier performance is presented as a percentage and is calculated by dividing the number of packages delivered on time by the total number of packages delivered. Thus, the performance calculation only takes into account the packages that have been delivered.
 
-![equation EN performance](//images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/f899c821db95eef10472ae180e5b74e4/equation_EN_performance.gif)
+![equation EN performance](https://images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/f899c821db95eef10472ae180e5b74e4/equation_EN_performance.gif)
 
  The VTEX Shipping Network Performance tool allows you to:
 
@@ -95,4 +95,4 @@ You can download a report with data from the carriers and package deliveries. To
 2. Wait until you receive the spreadsheet by email.
 3.  Download the spreadsheet.
 
-![Resumo de performance EN](//images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/786e60dd75dc0118711259b8ab4bbd7d/Resumo_de_performance_EN.png)
+![Resumo de performance EN](https://images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/786e60dd75dc0118711259b8ab4bbd7d/Resumo_de_performance_EN.png)
diff --git a/docs/tutorials/en/vtex-status-page.md b/docs/tutorials/en/vtex-status-page.md
index 8d928b8a8..5cb14aae5 100644
--- a/docs/tutorials/en/vtex-status-page.md
+++ b/docs/tutorials/en/vtex-status-page.md
@@ -19,7 +19,7 @@ On the [VTEX Status](https://status.vtex.com/) page, you can monitor the platfor
 
 Our team reports events whenever our automatic monitoring system identifies an instability in the platform modules. Scheduled maintenance is also reported in detail on this page.
 
-![statuspage-1](//images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/d8aea2fa393bfb699b6ea71b9b59d7a9/statuspage-1.png)
+![statuspage-1](https://images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/d8aea2fa393bfb699b6ea71b9b59d7a9/statuspage-1.png)
 
 Below, you can find details of the VTEX platform's status page elements, developed with the [incident.io](https://incident.io/) tool:
 
@@ -41,7 +41,7 @@ The status page displays the `Subscribe to updates` button in the top right corn
 
 By choosing the email subscription option, you can receive notifications only for certain components. To do so, select the **Subscribe to specific components** option. Then, check the components you want to monitor.
 
-![statuspage-2](//images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/2e3c6f8f076298d91e2ff5b8139325e0/statuspage-2.png)
+![statuspage-2](https://images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/2e3c6f8f076298d91e2ff5b8139325e0/statuspage-2.png)
 
 ## General status
 
@@ -49,23 +49,23 @@ In this section, you can view the platform's general status, which can be _fully
 
 When problems or maintenance affect a system, the impacted component and the incident description are displayed. See examples below.
 
-![statuspage-3](//images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/21bc090adf8b43e7579831a500e4b627/statuspage-3.png)
+![statuspage-3](https://images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/21bc090adf8b43e7579831a500e4b627/statuspage-3.png)
 
-![statuspage-4](//images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/80950f0d2faadb58b813eddc64eec7bc/statuspage-4.png)
+![statuspage-4](https://images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/80950f0d2faadb58b813eddc64eec7bc/statuspage-4.png)
 
-![statuspage-5](//images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/6d7fb7f4ffbf645810e4ade63efa9e64/statuspage-5.png)
+![statuspage-5](https://images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/6d7fb7f4ffbf645810e4ade63efa9e64/statuspage-5.png)
 
 ## System status
 
 In this section, you can check the status of each platform system and its components in real time.
 
-![statuspage-6](//images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/fdc22b9eff6d4bf11bfba43a283da409/statuspage-6.png)
+![statuspage-6](https://images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/fdc22b9eff6d4bf11bfba43a283da409/statuspage-6.png)
 
 By clicking the arrow <i class="fas fa-chevron-down"></i> next to the number of components, you can view the status of specific components for each system.
 
 If maintenance is scheduled for a future date, you will also see the `Upcoming maintenance scheduled` button, as shown below. Hovering over this button will display the scheduled maintenance event. You can click to view its log.
 
-![statuspage-7](//images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/1fbf5de5c36e02ec2bfd6204471a2ebf/statuspage-7.png)
+![statuspage-7](https://images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/1fbf5de5c36e02ec2bfd6204471a2ebf/statuspage-7.png)
 
 The possible statuses for each component are:
 
@@ -123,7 +123,7 @@ To navigate to previous months, click the arrow `<`.
 
 To view incidents from a specific day, hover over the date. To access the page with the complete event log, click the listed incident or maintenance.
 
-![statuspage-8](//images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/8ca30c0cd6d89aaca8d92dc21af7274e/statuspage-8.png)
+![statuspage-8](https://images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/8ca30c0cd6d89aaca8d92dc21af7274e/statuspage-8.png)
 
 <div class="alert alert-warning">
   <p>If the scheduled maintenance lasts longer than a day, only the start date will be selected in the calendar. You must open the <a href="#scheduled-maintenance-logs"> maintenance log</a> to see the start and end dates.</p>
@@ -135,7 +135,7 @@ Below, we detail the information available in the [incident log](#incident-logs)
 
 The incident details page displays the following information:
 
-![status-page-9-en](//images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/6cacbbfc2e5b7e99bf4309e3622edda4/status-page-9-en.png)
+![status-page-9-en](https://images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/6cacbbfc2e5b7e99bf4309e3622edda4/status-page-9-en.png)
 
 * **Title:** Title describing the incident.
 * **Status:** Each incident has a defined cycle in which our team works to identify and solve problems. These are stages of this cycle:
@@ -164,6 +164,6 @@ The scheduled maintenance log displays the same information as the incident logs
 
 Below are some examples illustrating the status and timeline of scheduled maintenance events.
 
-![statuspage-10](//images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/7dc874395f5b13ba6e1ce62b76913398/statuspage-10.png)
+![statuspage-10](https://images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/7dc874395f5b13ba6e1ce62b76913398/statuspage-10.png)
 
-![statuspage-11](//images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/9900eb1dd6b9086a6c6049855dbc17c9/statuspage-11.png)
+![statuspage-11](https://images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/9900eb1dd6b9086a6c6049855dbc17c9/statuspage-11.png)
diff --git a/docs/tutorials/en/warehouse.md b/docs/tutorials/en/warehouse.md
index e493ca86c..96feb8b9a 100644
--- a/docs/tutorials/en/warehouse.md
+++ b/docs/tutorials/en/warehouse.md
@@ -20,7 +20,7 @@ On the VTEX platform, warehouses are physical storage spaces for goods sold by t
 
 It is important to pay attention to the inventory logistics and how the settings on the VTEX platform affect order delivery. From the warehouse, orders are sent to loading docks, where they are picked up by the carriers. 
 
-![EstrategiaEnvio_EN](//images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/950f5a0342bba5b62dcd0bee100e8a71/Frame_2__3_.svg)
+![EstrategiaEnvio_EN](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/950f5a0342bba5b62dcd0bee100e8a71/Frame_2__3_.svg)
 
 <div class="alert alert-info">
 The carrier that will deliver a certain order is defined by the <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">shipping policy</a>. For a carrier to be selected to deliver the order, its shipping policy must meet the conditions required for the delivery of the order. The shipping policy is linked to the warehouse by the Loading dock.
diff --git a/docs/tutorials/en/web-application-firewall-waf.md b/docs/tutorials/en/web-application-firewall-waf.md
index 5b530990f..827aaf49e 100644
--- a/docs/tutorials/en/web-application-firewall-waf.md
+++ b/docs/tutorials/en/web-application-firewall-waf.md
@@ -23,7 +23,7 @@ The Web Application Firewall (WAF) is a security layer designed to protect web a
 
 The WAF is aimed at HTTP (Hypertext Transfer Protocol) and HTTPS (HTTP Secure) communications, scanning inbound and outbound data to detect and block possible threats.
 
-![waf-en](//images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/19c4af7d54a4e27985a697270e5ea662/waf-en.png)
+![waf-en](https://images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/19c4af7d54a4e27985a697270e5ea662/waf-en.png)
 
 The WAF's operation begins with the VTEX Security team defining [security rules](#security-rules) based on the analysis of information flow patterns. Based on these rules, the WAF continuously monitors web traffic. When it detects potentially harmful activity, it can block the traffic, thus preventing vulnerabilities in the web application.
 
diff --git a/docs/tutorials/en/web-page-performance.md b/docs/tutorials/en/web-page-performance.md
index 5dfa2cbab..8a05ef0fd 100644
--- a/docs/tutorials/en/web-page-performance.md
+++ b/docs/tutorials/en/web-page-performance.md
@@ -25,7 +25,7 @@ Web Page Performance brings Google's [PageSpeed Insights](https://developers.goo
 
 Although the Web Page Performance dashboard offers the same features as Google's PageSpeed Insights tool, it is only on the VTEX Admin that merchants will be able to add multiple URLs and assess them constantly. 
 
-![Web page performance Dash EN](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
+![Web page performance Dash EN](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/83d8891b5441de2d1c4c36b9b4c00317/Screen_Shot_2022-06-29_at_15.49.56.png)
 
 ## Why should you track a web page's performance?
 
@@ -108,7 +108,7 @@ Note that the top 10 most accessed pages in your ecommerce cannot be deleted. Yo
 
 ## Core Web Vitals
 
-![Core web vitals EN](//images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/b135473eb67bc50d6d504f74da8bf111/Screen_Shot_2022-06-29_at_16.00.41.png)
+![Core web vitals EN](https://images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/b135473eb67bc50d6d504f74da8bf111/Screen_Shot_2022-06-29_at_16.00.41.png)
 
  For each URL, the Web Page Performance page displays the score of [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals) for that web page. 
 
diff --git a/docs/tutorials/en/welcome-message-control.md b/docs/tutorials/en/welcome-message-control.md
index ee3eeb67d..c15c6b17f 100644
--- a/docs/tutorials/en/welcome-message-control.md
+++ b/docs/tutorials/en/welcome-message-control.md
@@ -19,7 +19,7 @@ The control `<vtex.cmc:welcomeMessage/>` renders a welcome message, which should
 
 See an example in the image below.
 
-![welcome1](//images.contentful.com/alneenqid6w5/2z4iyUDAm0muKc4OCOUOa2/9e6f37d39596161bfe1721effdceb692/welcome1.png)
+![welcome1](https://images.contentful.com/alneenqid6w5/2z4iyUDAm0muKc4OCOUOa2/9e6f37d39596161bfe1721effdceb692/welcome1.png)
 
 ## HTML code rendered
 
diff --git a/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md b/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
index a26d02ff6..c4df83b67 100644
--- a/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
+++ b/docs/tutorials/en/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
@@ -19,7 +19,7 @@ By accessing the section __All orders__, in __Orders management__, it is possibl
 
 The column __Origin__ indicates where the order came from, distinguishing each other in two possible origins: __Marketplace__ and __Fulfillment__.
 
-![orders-list-origin-en](//images.ctfassets.net/alneenqid6w5/3uvgTmIP1uEnAs0E4idyvb/832dd7e9618de51ffd8d2c56ab988f53/oders-list-origin-en.png)
+![orders-list-origin-en](https://images.ctfassets.net/alneenqid6w5/3uvgTmIP1uEnAs0E4idyvb/832dd7e9618de51ffd8d2c56ab988f53/oders-list-origin-en.png)
 
 
 ## Marketplace
diff --git a/docs/tutorials/en/what-are-shelves.md b/docs/tutorials/en/what-are-shelves.md
index bbf2296af..fd2f278c1 100644
--- a/docs/tutorials/en/what-are-shelves.md
+++ b/docs/tutorials/en/what-are-shelves.md
@@ -23,7 +23,7 @@ Shelves are configurable elements that display a grouping of products on the pag
 
 Shelves are structured with HTML code, organized into specific [templates](/en/tutorial/what-are-templates), called __Shelves Templates__. They are located in the folder **CMS**, in the [Layout module](/en/faq/what-is-cms). It is in this folder that you may create new templates and edit those that already exist.
 
-![Shelves Templates](//images.contentful.com/alneenqid6w5/4pIuR3BWKQisWuos4gcCWS/ade52c1df88c9e371169df99776b0779/Shelves_Template-min.png)
+![Shelves Templates](https://images.contentful.com/alneenqid6w5/4pIuR3BWKQisWuos4gcCWS/ade52c1df88c9e371169df99776b0779/Shelves_Template-min.png)
 
 Because it is an element that can be used on more than one page, this special type of template (Shelf Template) is stored in folders that are different from other types (HTML Templates and Sub Templates). This way, it's possible to maintain the organization of the files and, consequently, of your web site's code.
 
diff --git a/docs/tutorials/en/what-are-templates.md b/docs/tutorials/en/what-are-templates.md
index a69059c98..5b20511eb 100644
--- a/docs/tutorials/en/what-are-templates.md
+++ b/docs/tutorials/en/what-are-templates.md
@@ -32,7 +32,7 @@ In addition to these two basic types, there is also a subdivision of the __page
 
 And speaking of organization, you will find all templates in **Storefront > Layout > CMS**, gathered in folders according to their type (HTML or Shelves). __Sub Templates__ are in the folder of the same name, which is inside the __HTML Templates__ directory. There, you will be able to create new templates and edit the ones that already exist.
 
-![cms](//images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
+![cms](https://images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
 
 ### Related articles
 - [What is CMS?](/en/tutorial/what-is-cms)
diff --git a/docs/tutorials/en/what-are-the-internal-utms.md b/docs/tutorials/en/what-are-the-internal-utms.md
index b21ba68c1..7c0ea1867 100644
--- a/docs/tutorials/en/what-are-the-internal-utms.md
+++ b/docs/tutorials/en/what-are-the-internal-utms.md
@@ -19,11 +19,11 @@ subcategory: 7ogirQ8NClawO2X6xdgCKc
 
 Therefore, they do not aim to track traffic coming from external sites or services for purposes related to the marketing context. This is a function performed by the UTMs, as explained in the article [What are utm_source, utm_campaign and utm_medium](/en/faq/what-are-utm-source-utm-campaign-and-utm-medium).
 
-Normally, the internal UTMs are used as __cause of benefit__. In the Promotions & Taxes module, you can define that only closed orders with a given UTM applied to the URL will receive a certain benefit. See below the field to choose or create this internal UTM in the registration of a regular benefit.![utmi1](//images.contentful.com/alneenqid6w5/16CfZDMc1A2IiiU2UcayS2/aaf51be21c48ee58b10066e7cb70c063/utmi1.jpg)
+Normally, the internal UTMs are used as __cause of benefit__. In the Promotions & Taxes module, you can define that only closed orders with a given UTM applied to the URL will receive a certain benefit. See below the field to choose or create this internal UTM in the registration of a regular benefit.![utmi1](https://images.contentful.com/alneenqid6w5/16CfZDMc1A2IiiU2UcayS2/aaf51be21c48ee58b10066e7cb70c063/utmi1.jpg)
 
 In the Orders Management module, within the order details screen, you can rotate the Total Value card to view the data for __Sales and Marketing__. It contains the value of the internal UTM parameter used in the benefit.
 
-![utmi2](//images.contentful.com/alneenqid6w5/41RwzsUqdOYWaYAokS6YiC/5774226a9a53769566cdefbcb2c0b171/utmi2.jpg)
+![utmi2](https://images.contentful.com/alneenqid6w5/41RwzsUqdOYWaYAokS6YiC/5774226a9a53769566cdefbcb2c0b171/utmi2.jpg)
 
 VTEX works with three types of internal UTMs:
 - `utmi_cp`
diff --git a/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md b/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
index 8b0f7fd03..e55b07296 100644
--- a/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
+++ b/docs/tutorials/en/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
@@ -24,4 +24,4 @@ When configuring a **Buy one and Get one** promotion, it’s possible to **Activ
 For both scenarios it is necessary to fill out the maximum selectable quantity. With the **active** gift multiplier, choose the **maximum quantity** of gifts for the condition. For the **inactive** gift multiplier, the quantity is **always 1**.
 
 
-![ativar-multiplicador-brinde en](//images.ctfassets.net/alneenqid6w5/42NpoBzyXCuagoceC0IAgQ/15fd07baa0eddbd1086831ec6e9440b7/gift_multi_en.png)
+![ativar-multiplicador-brinde en](https://images.ctfassets.net/alneenqid6w5/42NpoBzyXCuagoceC0IAgQ/15fd07baa0eddbd1086831ec6e9440b7/gift_multi_en.png)
diff --git a/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md b/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
index fb472c171..df8401eb0 100644
--- a/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
+++ b/docs/tutorials/en/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
@@ -33,7 +33,7 @@ To learn how to access the orders that were considered for revenues calculation,
 All financially approved orders will receive this status, which can be seen in the orders management module:
 
 
-![image (2)](//images.ctfassets.net/alneenqid6w5/1Q14q5mtiayBLRBSupsKGs/53c5555a68359b9fd3dd882336beccb7/image__2_.png)
+![image (2)](https://images.ctfassets.net/alneenqid6w5/1Q14q5mtiayBLRBSupsKGs/53c5555a68359b9fd3dd882336beccb7/image__2_.png)
 
 
 To access this module, follow the step by step below:
diff --git a/docs/tutorials/en/what-is-a-franchise-account.md b/docs/tutorials/en/what-is-a-franchise-account.md
index 4ddd9587c..84f2cf395 100644
--- a/docs/tutorials/en/what-is-a-franchise-account.md
+++ b/docs/tutorials/en/what-is-a-franchise-account.md
@@ -19,7 +19,7 @@ On the VTEX platform, you have the option to register physical stores, franchise
 
 The franchise account is associated with a main account. In the case of a brand that has several physical stores, franchisees or representatives, each of them can have a franchise account linked to the brand's main account. This allows them to deliver the products sold by the brand's ecommerce.
 
-![diagrama contas v2 - en](//images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/bf1a348a817eb6a839db435d5dce1a9c/diagrama_contas_v2_-_en.png)
+![diagrama contas v2 - en](https://images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/bf1a348a817eb6a839db435d5dce1a9c/diagrama_contas_v2_-_en.png)
 
 In this article, we will cover the following topics:
 
@@ -38,7 +38,7 @@ In addition, when using the franchise account you can manage prices and payment
 
 A franchise account does not have its own website. Consumers browse directly on the main account website, which functions as a marketplace in this situation. Customer data is stored in the Master Data of the main account.
 
-![diagrama admin contas - en](//images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/34a3ac170c1d3f7db9f4f03d27fa2a03/diagrama_admin_contas_-_en.png)
+![diagrama admin contas - en](https://images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/34a3ac170c1d3f7db9f4f03d27fa2a03/diagrama_admin_contas_-_en.png)
 
 ## Relationship between franchise account and White Label Seller
 
diff --git a/docs/tutorials/en/what-is-binding.md b/docs/tutorials/en/what-is-binding.md
index bdee94581..4a567e8fe 100644
--- a/docs/tutorials/en/what-is-binding.md
+++ b/docs/tutorials/en/what-is-binding.md
@@ -19,7 +19,7 @@ Website binding is what bridges the CMS (Portal) with the information defined in
 
 That is, it sets that an __account name__ (configured in the License Manager module) is linked to the folder and files structure of a particular __Website__ (defined in the CMS module).
 
-![Binding](//images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
+![Binding](https://images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
 
 This is the setting made when an account wants to have more than one store. For each of these stores (which we call [multistores](/en/tutorial/creating-multi-store-multi-domain)), you make a binding.
 
diff --git a/docs/tutorials/en/what-is-cms-layout.md b/docs/tutorials/en/what-is-cms-layout.md
index 8c3f93844..0e1ef1b7d 100644
--- a/docs/tutorials/en/what-is-cms-layout.md
+++ b/docs/tutorials/en/what-is-cms-layout.md
@@ -37,7 +37,7 @@ Before you begin to organize the content of your Web Site, it must be linked to
 
 This is a fundamental process for the perfect functioning of your store, but it is also very simple. Just follow the steps [of this article](/en/tutorial/linking-an-account-name-to-a-website-binding).
 
-![Binding](//images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
+![Binding](https://images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
 
 ## Layouts and templates
 
diff --git a/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md b/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md
index 4e45d0b7f..33be7b580 100644
--- a/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md
+++ b/docs/tutorials/en/what-is-the-difference-between-inventory-and-warehouse-dock.md
@@ -25,7 +25,7 @@ __The three stages of logistics are represented by the following structure:__
 
 __They can be illustrated by this flow:__
 
-![EN Conceitos Logistics](//images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/614cb763d596936df13033e89067f7f4/EN_Conceitos_Logistics.png)
+![EN Conceitos Logistics](https://images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/614cb763d596936df13033e89067f7f4/EN_Conceitos_Logistics.png)
 
 ## Warehouse
 It's the physical space used to store the goods of an e-commerce, functioning as the repository of the items of your store.
diff --git a/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
index 7e8af8311..1d635a630 100644
--- a/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
@@ -31,7 +31,7 @@ The types include Banner, BannerDHTML Collection or HTML.
 
 To create a customized control tag, click on Add, enter a name, a tag name, and select the type.
 
-![cms-custom-elements EN / ES](//images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
+![cms-custom-elements EN / ES](https://images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
 
 <div class="alert alert-warning">
   <p><b>Warning:</b> do not create an HTML type control with an element <code>title</code>. This may interfere with your store operation.</p>
diff --git a/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md b/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md
index ab3e0d2f0..75dbf1b3a 100644
--- a/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md
+++ b/docs/tutorials/en/what-to-do-when-my-report-does-not-reach-my-inbox.md
@@ -24,7 +24,7 @@ However, there is a way to extract this report manually by accessing Master Data
 Let's see how in the following step-by-step:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
-2. Click __Exports__. ![exports-md](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/1ac3c2bd600edaac1440899274a8005b/exportaciones.png)
+2. Click __Exports__. ![exports-md](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/1ac3c2bd600edaac1440899274a8005b/exportaciones.png)
 3. Make sure that the tab currently open is __Applications__.
 4. Under __Export Status__, identify the row of the report you want to download.
 5. If the __Status__ is __Completed - Download__, click **Download** to download the file.
diff --git a/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md b/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md
index 361aa6c9b..9792c8222 100644
--- a/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md
+++ b/docs/tutorials/en/whatsapp-ai-campaigns-management-and-details.md
@@ -80,7 +80,7 @@ To pause sending messages from a campaign, follow the steps below:
 
 You can find information about your active campaigns in the VTEX Admin.
 
-![Visão geral-EN](//images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/0ec14467b481aeba99f2d0f3fc461ff4/Vis_o_geral-EN.png)
+![Visão geral-EN](https://images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/0ec14467b481aeba99f2d0f3fc461ff4/Vis_o_geral-EN.png)
 
 Below are the details of the available metrics:
 
diff --git a/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md b/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md
index 98f79c281..010db0c56 100644
--- a/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md
+++ b/docs/tutorials/en/where-do-i-see-clients-that-use-recurrence.md
@@ -22,4 +22,4 @@ But remember: a subscribers only appears in the listing after the payment is app
 1. Access the __Orders Management__ module.
 2. Click the __Subscriptions__ tab.
 
-![subscriptions EN](//images.ctfassets.net/alneenqid6w5/jT7LGvlNOS2iQGIQIqEi/591dc39ef6d0f5824956f819817520fd/subscriptions_EN.png)
+![subscriptions EN](https://images.ctfassets.net/alneenqid6w5/jT7LGvlNOS2iQGIQIqEi/591dc39ef6d0f5824956f819817520fd/subscriptions_EN.png)
diff --git a/docs/tutorials/en/where-do-i-see-the-payment-capture-date.md b/docs/tutorials/en/where-do-i-see-the-payment-capture-date.md
index 8bb6a9625..bc589c761 100644
--- a/docs/tutorials/en/where-do-i-see-the-payment-capture-date.md
+++ b/docs/tutorials/en/where-do-i-see-the-payment-capture-date.md
@@ -23,4 +23,4 @@ To do that, follow the steps below:
 2. Find the desired transaction and click on it.
 3. In the __Transaction Events__, look for the settlement event:
 
-![settlementEvent](//images.contentful.com/alneenqid6w5/2svl4ROF5OoG4G62QeQaAg/8f45a34ccbe4c03a178a89bcd8468957/settlementEvent.png)
+![settlementEvent](https://images.contentful.com/alneenqid6w5/2svl4ROF5OoG4G62QeQaAg/8f45a34ccbe4c03a178a89bcd8468957/settlementEvent.png)
diff --git a/docs/tutorials/en/white-label-sellers-selection.md b/docs/tutorials/en/white-label-sellers-selection.md
index e297c9365..ceccf5d2d 100644
--- a/docs/tutorials/en/white-label-sellers-selection.md
+++ b/docs/tutorials/en/white-label-sellers-selection.md
@@ -112,13 +112,13 @@ If there is a tie between sellers on the best cost or time, the tiebreaker crite
 
 A customer added five SKUs to the shopping cart. Each of the sellers delivering in the customer's region (sellers A, B, C, and D) has only part of the ordered items in [stock](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139), as illustrated below: 
 
-![print_selecao_seller_white_label_1](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
+![print_selecao_seller_white_label_1](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
 
 The VTEX platform selects the seller that has available in stock the maximum quantity of the SKUs added to the shopping cart. In this case, it's Seller B, the only one that can deliver three SKUs. 
 
 After Seller B is selected, there are two SKUs still to be delivered. If a single seller were able to deliver both items, it would be a decisive selection factor because the objective is to find the lowest number of sellers to cover the shopping cart. However, Sellers A and C will be selected for delivering SKUs 1 and 4, as illustrated in the image below:
 
-![print_selecao_seller_white_label_2](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
+![print_selecao_seller_white_label_2](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
 
 In the first image, Seller C was able to deliver SKUs 3 and 4, and Seller D could deliver SKU 5. But Seller B has already been selected to deliver those items, so those SKUs will be disregarded in the following steps of the selection. This is represented by removing the arrow connecting Seller C to SKU 3 and Seller D to SKU 5.
 
@@ -128,7 +128,7 @@ The selection result for the delivery method is a combination between sellers A,
 
 A customer added five SKUs to the shopping cart and there are four sellers delivering in their region: sellers A, B, C, and D. None of them has all of the items in [stock](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139), as illustrated below:
 
-![print_selecao_seller_white_label_3](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
 
 The VTEX platform selects the seller that has available in stock the highest number of the SKUs added to the shopping cart. Seller B and Seller D are able to deliver three items. Because both can deliver SKU 3, they are in competition.
 
@@ -141,11 +141,11 @@ Suppose Seller B has the cheapest shipping and Seller D has the fastest shipping
 
 - **Fastest shipping:** After Seller D is selected, SKUs 3 and 4 remain to be delivered. Seller C is able to deliver both, therefore it will be selected. The selection result is a combination of sellers D and C.
 
-![print_selecao_seller_white_label_4](//images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
+![print_selecao_seller_white_label_4](https://images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
 
 - **Cheapest shipping cost:** After Seller B is selected, SKUs 1 and 4 remain to be delivered. Since only Seller A is able to deliver SKU 1 and Seller C SKU 4, the selection result is a combination of sellers A, B, and C. 
 
-![print_selecao_seller_white_label_5](//images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
+![print_selecao_seller_white_label_5](https://images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
 
 In the images showing the fastest shipping and the cheapest shipping, the arrows pointing repeatedly to sellers which delivered SKUs covered by sellers B and D were removed. During the selection process, SKUs that are already covered are disregarded.
 
diff --git a/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 36f575a75..2dd6b5ba4 100644
--- a/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -37,7 +37,7 @@ Follow the steps below to validate the information:
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
 2. In the __Profile System__ box, click __Customers__.
-3. Select the option __Email__ and search the client's email.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+3. Select the option __Email__ and search the client's email.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 4. Click the customer record to access the profile details.
 
 In the __Contact__ section, you will see that the `Is Company?` option is filled with the value `No`. At the same time, in the section __Company Data__, you will see that the `Document Type` field is filled with the value `cnpj`.
diff --git a/docs/tutorials/en/wow-to-integrate-with-multiplus.md b/docs/tutorials/en/wow-to-integrate-with-multiplus.md
index c3d25bc24..4b4dff749 100644
--- a/docs/tutorials/en/wow-to-integrate-with-multiplus.md
+++ b/docs/tutorials/en/wow-to-integrate-with-multiplus.md
@@ -28,7 +28,7 @@ Another option for the steps above is to access your store’s marketplace setti
 
 Replace NOMEDALOJA with the accountName of your store.
 
-![Multiplus1](//images.contentful.com/alneenqid6w5/2NxVrnsnZCOuQOqEOIusOq/d5cd381241a842c29e81763ea6f8f506/Multiplus1.png)
+![Multiplus1](https://images.contentful.com/alneenqid6w5/2NxVrnsnZCOuQOqEOIusOq/d5cd381241a842c29e81763ea6f8f506/Multiplus1.png)
 
 After clicking on **Integrate**, a form will be displayed with some fields that must be filled in. Be attentive to mandatory fields: these show “/*” next to the text box.
 
@@ -41,7 +41,7 @@ After clicking on **Integrate**, a form will be displayed with some fields that
 - **Código Parceiro que será utilizado na Multiplus**: This code should have from 1 to 30 digits of your choice.  To qualify your sales, you must inform this code to Multiplus after carrying out the setup in Bridge. If you change this code, the new code must also be informed to Multiplus, for update purposes. Otherwise, the store will not be able to sell;
 - **E-mails para a criação do Afiliado**: After saving the settings, the integration will generate the Affiliate in VTEX, and include this information in the register.
 
-![Multiplus2](//images.contentful.com/alneenqid6w5/4lTWbmFiGcOoIkUK8KSIAm/501d2f8e79300fc814d08ac600d7b0be/Multiplus2.png)
+![Multiplus2](https://images.contentful.com/alneenqid6w5/4lTWbmFiGcOoIkUK8KSIAm/501d2f8e79300fc814d08ac600d7b0be/Multiplus2.png)
 
 
 After filling in the information, click on **Save** and wait for the “success” message to show up.
diff --git a/docs/tutorials/es/accessing-a-client-abandoned-cart.md b/docs/tutorials/es/accessing-a-client-abandoned-cart.md
index 3bf4c7983..e36b5ad2e 100644
--- a/docs/tutorials/es/accessing-a-client-abandoned-cart.md
+++ b/docs/tutorials/es/accessing-a-client-abandoned-cart.md
@@ -28,26 +28,26 @@ Ver estos campos es muy simple. Una vez registrado en el Admin de su tienda, só
 
 1. En la _sidebar_ del Admin, haga clic en __Master Data__;
 
-  ![Carrinho Abandonado - 1 - ES](//images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/76369f4dd2d1483fe5e4d3a501bc9d53/4GdZSkwtm9f76BIVFnC65D_Masterdata_ES.jpg)
+  ![Carrinho Abandonado - 1 - ES](https://images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/76369f4dd2d1483fe5e4d3a501bc9d53/4GdZSkwtm9f76BIVFnC65D_Masterdata_ES.jpg)
 
 2. Haga clic en el icono de configuración (engranaje) del __Profile System__.
 
-  ![Carrinho Abandonado - 2 - ES](//images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/6515d98ac1ca841647e50989854ca0cf/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
+  ![Carrinho Abandonado - 2 - ES](https://images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/6515d98ac1ca841647e50989854ca0cf/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
 
 3. Asegúrese de que está en la pestaña __Aplicaciones__.
 
-  ![Carrinho Abandonado - 3 - ES](//images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/32716ff3964171724751aebc9536efca/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
+  ![Carrinho Abandonado - 3 - ES](https://images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/32716ff3964171724751aebc9536efca/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
 
 4. Acceda a Editar (Lápiz) en la categoría __Clientes__.
 
-  ![Carrinho Abandonado - 4 - ES](//images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/87cb6addecfe6afd4f4135ca89e02df8/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
+  ![Carrinho Abandonado - 4 - ES](https://images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/87cb6addecfe6afd4f4135ca89e02df8/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
 
 5. Seleccione __"Último carrito"__ y __"Carrito"__ entre las opciones de __Campos de Listados__;
 
-  ![Carrinho Abandonado - 5 - ES](//images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/786f5d9a8362fd704daa2b8a88596ad0/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 5 - ES](https://images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/786f5d9a8362fd704daa2b8a88596ad0/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
 
 6. Haga clic en __Guardar__.
 
-  ![Carrinho Abandonado - 6 - ES](//images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/40b0c1cc04474521d0f89ac54e9ab961/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
+  ![Carrinho Abandonado - 6 - ES](https://images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/40b0c1cc04474521d0f89ac54e9ab961/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
 
 Con eso, usted ya podrá ver los parámetros de los carritos abandonados de sus clientes.
diff --git a/docs/tutorials/es/account-management.md b/docs/tutorials/es/account-management.md
index cdb24e315..429433801 100644
--- a/docs/tutorials/es/account-management.md
+++ b/docs/tutorials/es/account-management.md
@@ -84,7 +84,7 @@ Después que un usuario llena y guarda **Nombre** e **E-mail**, en los campos de
 La plantilla para este correo electrónico automático se puede cambiar en el <a href="https://help.vtex.com/es/tutorial/understanding-the-message-center--tutorials_84">Centro de mensajes</a> modificando la plantilla de <i>registro de cuenta</i>.
 </div>
 
-![registro de cuenta](//images.ctfassets.net/alneenqid6w5/7uIJliLTJ6wEMeeoqiSMQ/6c37511bd70d8035b11e18abc99b36d0/registro_de_cuenta.jpg)
+![registro de cuenta](https://images.ctfassets.net/alneenqid6w5/7uIJliLTJ6wEMeeoqiSMQ/6c37511bd70d8035b11e18abc99b36d0/registro_de_cuenta.jpg)
 
 ## Seguridad
 
diff --git a/docs/tutorials/es/account-settings-overview.md b/docs/tutorials/es/account-settings-overview.md
index aab05b6d9..bd081bf5e 100644
--- a/docs/tutorials/es/account-settings-overview.md
+++ b/docs/tutorials/es/account-settings-overview.md
@@ -21,7 +21,7 @@ En **Configuración de la cuenta**, puedes controlar el acceso al Admin y modifi
 
 Para acceder a la _Configuración de la cuenta_, haz clic en tu **avatar de perfil**, marcado con la inicial de tu email, y luego haz clic en el botón **Configuración de la cuenta**.  
 
-![Admin v4 account settings menu ES](//images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/db9e1eb25c423a3c797521dad3658d9b/Admin_v4_account_settings_menu_ES.jpg)
+![Admin v4 account settings menu ES](https://images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/db9e1eb25c423a3c797521dad3658d9b/Admin_v4_account_settings_menu_ES.jpg)
 
 La sección incluye las siguientes páginas, que pronto se incluirán en el diseño del Admin v4.
 
diff --git a/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md b/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md
index 55f3cf6a3..f0d7c5376 100644
--- a/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md
+++ b/docs/tutorials/es/activating-the-complete-list-link-on-the-category-menu.md
@@ -20,7 +20,7 @@ El link de **Lista Completa** en el menu de categorias categorías es muy usado
 
 Como, por ejemplo, en el caso abajo, el "Departamento 2":
 
-![categoria.es](//images.ctfassets.net/alneenqid6w5/7JXmPnw1lzfdGxgkshSztX/56e6b6587d0076dfb156867a953dd0e6/categoria.es.png)
+![categoria.es](https://images.ctfassets.net/alneenqid6w5/7JXmPnw1lzfdGxgkshSztX/56e6b6587d0076dfb156867a953dd0e6/categoria.es.png)
 
 De todas las categorías, la tienda prefirió exhibir en el menú solamente algunas.
 
@@ -29,5 +29,5 @@ Esta configuración se hace en el registro de categoría, en la opción **Menu c
 - Si está marcada, la categoría aparece en el menú.
 - Si no está marcada, la categoría no aparece y se muestra opción Lista Completa en el sitio.
 
-![categoria2.es](//images.ctfassets.net/alneenqid6w5/5fQJfwQpdMCpfE7s1P1Nx2/d8e05f4023ffbe92a7db72086af1dbf2/categoria2.es.png)
+![categoria2.es](https://images.ctfassets.net/alneenqid6w5/5fQJfwQpdMCpfE7s1P1Nx2/d8e05f4023ffbe92a7db72086af1dbf2/categoria2.es.png)
 
diff --git a/docs/tutorials/es/activating-the-new-order-placed.md b/docs/tutorials/es/activating-the-new-order-placed.md
index 16c2f349a..27e9a5c83 100644
--- a/docs/tutorials/es/activating-the-new-order-placed.md
+++ b/docs/tutorials/es/activating-the-new-order-placed.md
@@ -17,10 +17,10 @@ subcategory:
 
 El nuevo Order Placed trae un layout mejorado y totalmente mobile-friendly.
 
-![Nova página de Order Placed em versão desktop e mobile](//images.contentful.com/alneenqid6w5/6li99MH1AIqmOECuy8K4Ec/635952ed77d4630e1bd8c08f7761920d/cconf-announcement-0.png)
+![Nova página de Order Placed em versão desktop e mobile](https://images.contentful.com/alneenqid6w5/6li99MH1AIqmOECuy8K4Ec/635952ed77d4630e1bd8c08f7761920d/cconf-announcement-0.png)
 
 Para activarlo, es necesario acceder a la pestaña **Mis Pedidos** del módulo Portal y activar el opt-in _Order Placed Upgrade_. La nueva versión será activada por defecto el día 20/12/17 y la antigua será descontinuada.
 
-![Opt in no Portal V2](//images.contentful.com/alneenqid6w5/Ce7a3zePdIkEWcMy8m2w8/396ecacbc62a5a1883d2faf0197f4090/cconf-announcement-1.png)
+![Opt in no Portal V2](https://images.contentful.com/alneenqid6w5/Ce7a3zePdIkEWcMy8m2w8/396ecacbc62a5a1883d2faf0197f4090/cconf-announcement-1.png)
 
 Para saber como atualizar sua customização, veja o tutorial [Customizando as páginas do Checkout Confirmation](http://help.vtex.com/es/tutorial/personalizando-las-paginas-del-checkout-confirmation).
diff --git a/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md b/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md
index 6c82f8051..b98f65b05 100644
--- a/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md
+++ b/docs/tutorials/es/add-or-edit-a-url-mapping-through-worksheet-import.md
@@ -24,4 +24,4 @@ La estructura del archivo debe de ser la siguiente:
 - Columna D: Fecha Inicial (Formato: DD/MM/AAAA)
 - Columna E: Fecha Final (Formato: DD/MM/AAAA)
 
-![urlbuilder es](//images.ctfassets.net/alneenqid6w5/3R4XJx8UHekUASMY6euqAy/24705df3a75db5c4fcc780102689c322/urlbuilder_es.png)
+![urlbuilder es](https://images.ctfassets.net/alneenqid6w5/3R4XJx8UHekUASMY6euqAy/24705df3a75db5c4fcc780102689c322/urlbuilder_es.png)
diff --git a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
index 8680c1bf9..b50018e07 100644
--- a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
+++ b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Para activar el inicio de sesión por OAuth2 a través de Facebook, accede al Admin VTEX > **Configuración de cuenta > Autenticación** y completa los campos **Client ID** y **Secreto del cliente**, tal como se describe en el artículo [Configurar inicio de sesión con Facebook y Google](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
 
-![Facebook OAuth ES](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/e85e70614c1ff706937104c8f5ec917c/1-login-fb-es.PNG)
+![Facebook OAuth ES](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/e85e70614c1ff706937104c8f5ec917c/1-login-fb-es.PNG)
 
 Para obtener las credenciales, sigue las instrucciones en las secciones a continuación:
 
@@ -35,12 +35,12 @@ Para empezar, debes registrar una aplicación en Facebook siguiendo los pasos a
 4. Haz clic en `Crear app`.
 5. Haz clic en **Permitir que las personas inicien sesión con su cuenta de Facebook** entre las opciones que se ilustran a continuación.
 
-   ![2-login-fb-es](//images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/077ab05e546169ba636a59aca0281498/2-login-fb-es.png)
+   ![2-login-fb-es](https://images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/077ab05e546169ba636a59aca0281498/2-login-fb-es.png)
 
 6. Haz clic en `Siguiente`.
 7. Añade el nombre de la aplicación y el correo electrónico de contacto de la persona responsable de la aplicación en los campos que se ilustran a continuación.
 
-   ![3-login-fb-es](//images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/d2dc7a5cb5d859f25a892ad3e93575fe/3-login-fb-es.png)
+   ![3-login-fb-es](https://images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/d2dc7a5cb5d859f25a892ad3e93575fe/3-login-fb-es.png)
 
 8. Haz clic en `Crear app`.
 
@@ -50,15 +50,15 @@ El siguiente paso es configurar el producto Inicio de sesión con Facebook en la
 
 1. Haz clic en **Productos** en el menú lateral o en el **panel **de Meta for Developers, resaltado en la imagen siguiente.
 
-   ![4-login-fb-es](//images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/967682b6e1942ed15ab2c40d75f8a4f0/4-login-fb-es.png)
+   ![4-login-fb-es](https://images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/967682b6e1942ed15ab2c40d75f8a4f0/4-login-fb-es.png)
 
 2. Haz clic en `Configurar` y después selecciona `Configurar` en el menú desplegable.
 
-   ![5-login-fb-es](//images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/3c181d675c97d893402af45974d65e95/5-login-fb-es.png)
+   ![5-login-fb-es](https://images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/3c181d675c97d893402af45974d65e95/5-login-fb-es.png)
 
 3. Define los estados como se detalla a continuación:
 
-   ![Configuração URI OAuth Facebook ES](//images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/1e318e6f8fb6c7465445f7c25fddf883/configuracoes_Oauth_ES.png)
+   ![Configuração URI OAuth Facebook ES](https://images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/1e318e6f8fb6c7465445f7c25fddf883/configuracoes_Oauth_ES.png)
 
    Inserta las URL siguientes en **URI de redireccionamieno de OAuth válidos**, sustituyendo `{{HOST_URL}}`  por la URL base de tu tienda y `{{accountName}}` por el nombre de tu cuenta tal y como se describe en el menú de administración de la tienda:   
 
@@ -74,7 +74,7 @@ Por último, debes rellenar algunos datos sobre la aplicación para completar el
 
 1. En el menú lateral de Meta for Developers, haz clic en **Configuración de la aplicación** y después en **Básica:**
 
-   ![7-login-fb-es](//images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/f84756573e40f40e8f94c062e68da397/7-login-fb-es.png)
+   ![7-login-fb-es](https://images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/f84756573e40f40e8f94c062e68da397/7-login-fb-es.png)
 
 2. Copia el valor del campo **Identificador de la aplicación**. Debes ingresar este valor en el campo **Client ID** al [configurar el Inicio de sesión con Facebook en el Admin VTEX](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
 3. En **Clave secreta de aplicación**, haz clic en el botón **Mostrar** y, a continuación, copia el valor del campo. Debes ingresar este valor en el campo **Secreto del cliente** al [configurar el inicio de sesión con Facebook en el Admin VTEX](https://help.vtex.com/es/tutorial/configurar-inicio-de-sesion-con-facebook-y-google--tutorials_513).
diff --git a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
index 329e7d5e8..1b05e2bec 100644
--- a/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
+++ b/docs/tutorials/es/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Para habilitar el inicio de sesión por OAuth2 vía Google, usted necesita acceder al VTEX ID por su Admin y rellenar los campos `Client ID` y `Client Secret`, como se detalla en [este artículo](/pt/tutorial/integracao-google-e-facebook-para-login).
 
-![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
+![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
 
 Estos valores se obtienen de un proyecto que debe ser creado en el servicio de APIs de la plataforma de Google Cloud Platform.
 
@@ -30,17 +30,17 @@ Los siguientes pasos describen procedimientos en una plataforma externa y pueden
 1. Entre en el enlace [`https://console.developers.google.com/`](https://console.developers.google.com/);
 2. Haga clic en __Credenciales__, en la pestaña lateral;
 3. Haga clic en __Crear Proyecto__;
-    ![Criar Projeto Google ES](//images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/7ae1980ea25092ef02e7f1952370fbd9/Criar_Projeto_Google_ES.png)
+    ![Criar Projeto Google ES](https://images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/7ae1980ea25092ef02e7f1952370fbd9/Criar_Projeto_Google_ES.png)
 4. Defina el nombre del proyecto y haga clic en __Crear__;
-    ![Novo Projeto Google ES](//images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/56b4d080ea4da99a5d626fc3c0329261/Novo_Projeto_Google_ES.png)
+    ![Novo Projeto Google ES](https://images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/56b4d080ea4da99a5d626fc3c0329261/Novo_Projeto_Google_ES.png)
 5. En la parte superior de la página, haga clic en el botón __Crear credenciales__;
-    ![Criar Credenciais Google ES](//images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/25ac7be759c40d281dc4bd2cb817ecc4/Criar_Credenciais_Google_ES.png)
+    ![Criar Credenciais Google ES](https://images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/25ac7be759c40d281dc4bd2cb817ecc4/Criar_Credenciais_Google_ES.png)
 6. Haga clic en la opción __ID de cliente de OAuth__;
-    ![ID cliente OAuth Google ES](//images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/4a2d0e88620740449f9240d87e8dec7e/ID_cliente_OAuth_Google_ES.png)
+    ![ID cliente OAuth Google ES](https://images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/4a2d0e88620740449f9240d87e8dec7e/ID_cliente_OAuth_Google_ES.png)
 7. Haga clic en el botón __Configurar página de consentimiento__;
-    ![Configurar Tela Consentimento Google ES](//images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/9db551614331a844bf870661fac5d7bf/Configurar_Tela_Consentimento_Google_ES.png)
+    ![Configurar Tela Consentimento Google ES](https://images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/9db551614331a844bf870661fac5d7bf/Configurar_Tela_Consentimento_Google_ES.png)
 8. Elija el tipo de usuario que desea para su tienda (__Interno__ o __Externo__) y haga clic en el botón __Crear__;
-    ![Tipo usuário Google ES](//images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/f153fed0cf0864141b55c83932558d28/Tipo_usu__rio_ES.png)
+    ![Tipo usuário Google ES](https://images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/f153fed0cf0864141b55c83932558d28/Tipo_usu__rio_ES.png)
 9.  __Nombre de aplicación__: se mostrará a sus clientes al iniciar sesión;
 10. __Correo electrónico de asistencia del usuario__: para que los usuarios se comuniquen contigo si tienen preguntas sobre su consentimiento;
 11. __Logotipo de la app__: corresponde al logotipo de su tienda;
@@ -49,19 +49,19 @@ Los siguientes pasos describen procedimientos en una plataforma externa y pueden
     - `vtex.com.br`, referente a nuestros servidores BackEnd.
 13. __Información de contacto del desarrollador__: Google enviará notificaciones sobre cualquier cambio en tu proyecto a estas direcciones de correo electrónico;
 14. Haga clic en el botón  __Guardar y continuar__;
-    ![Configurações Tela Consentimento ES](//images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4db11d3ef54d615651a84aafe086df4c/Configura____es_Tela_Consentimento_ES.png)
+    ![Configurações Tela Consentimento ES](https://images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/4db11d3ef54d615651a84aafe086df4c/Configura____es_Tela_Consentimento_ES.png)
 13. Haga clic en __Credenciales__, en el menú lateral izquierdo;
 14. Elija __Aplicación web__, en Tipo de aplicación;
-    ![Credenciais Aplicativo Web Google ES](//images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/7253773b80efb5e1c5d1074dec6a578e/Credenciais_Aplicativo_Web_Google_ES.png)
+    ![Credenciais Aplicativo Web Google ES](https://images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/7253773b80efb5e1c5d1074dec6a578e/Credenciais_Aplicativo_Web_Google_ES.png)
 15. __Nombre__: para identificación interna;
 16. __Orígenes de JavaScript autorizados__: registrar las direcciones exactas que podrán usar este método de autenticación, lo que corresponde a su sitio web; por ejemplo, `https://www.tienda.com`. También se recomienda registrar la dirección `https://{{accountName}}.myvtex.com` de su cuenta, `{{accountName}}` es el nombre de la cuenta como se describe en el menú de administración de la tienda;
 17. __URIs de redireccionamiento autorizados__: registrar la URL de servicio de VTEX:
     -`https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
-    ![Configurações Aplicativo Web Google ES](//images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/56174b702c831b3154fac9e2dbc45e21/Configura____es_Aplicativo_Web_ES.png)
+    ![Configurações Aplicativo Web Google ES](https://images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/56174b702c831b3154fac9e2dbc45e21/Configura____es_Aplicativo_Web_ES.png)
 
 18. Después de completar este ajuste, se presentarán sus credenciales:
-    ![Cliente OAuth criado Google ES](//images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/7d36d109c612b4efa19410bd65da54c1/Cliente_OAuth_criado_Google_ES.png)
+    ![Cliente OAuth criado Google ES](https://images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/7d36d109c612b4efa19410bd65da54c1/Cliente_OAuth_criado_Google_ES.png)
     - Copie el __ID de cliente__ de Google y péguelo en el campo `Client Id` en el Admin de VTEX ID.
     - Copie su __clave secreta de cliente__ de Google y péguelo en el campo `Client Secret` en el Admin de VTEX ID.
-    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
+    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/cc91e8a5001c41693ea671d5da3c690e/google_ES.png)
     Una vez que haya completado todos estos pasos, guarde los cambios. 
diff --git a/docs/tutorials/es/adding-an-attachment.md b/docs/tutorials/es/adding-an-attachment.md
index c97a9cf78..c0989ff5f 100644
--- a/docs/tutorials/es/adding-an-attachment.md
+++ b/docs/tutorials/es/adding-an-attachment.md
@@ -31,7 +31,7 @@ El objetivo de un anexo es [complementar el producto con una información person
 Después de realizar el registro inicial del anexo, es necesario añadir las claves y los **Valores permitidos** relacionados con el anexo creado. Puede añadir las claves que desee. Para añadir las claves y los **Valores permitidos**, realice los siguientes pasos.
 
 1. En la página **Campos personalizados**, identifique la línea del anexo creado y haga clic en `Editar`, como se ilustra en la siguiente imagen.
-    ![anexos.pt](//images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/e56ba5ba51d3c9e60593faa82eb4d790/custom-product-attributes-es.PNG)
+    ![anexos.pt](https://images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/e56ba5ba51d3c9e60593faa82eb4d790/custom-product-attributes-es.PNG)
 2. Complete los campos indicados a continuación.
     * **Nombre de la clave:** nombre de la información personalizada. Este campo es obligatorio y no puede contener caracteres especiales, solo letras, números o puntos. Ejemplo: si el producto personalizable es una camiseta de la selección brasileña, los nombres de sus claves pueden ser `Nombre` y `Número`.
     * **Máximo de caracteres:** número máximo de caracteres que el cliente puede digitar para introducir una información personalizada en el producto. Este campo es obligatorio. Ejemplo: en este campo puede definir el límite de caracteres para el nombre que se imprimirá en una camiseta.
diff --git a/docs/tutorials/es/adding-bin-information.md b/docs/tutorials/es/adding-bin-information.md
index 930d62e0c..a0f15f30b 100644
--- a/docs/tutorials/es/adding-bin-information.md
+++ b/docs/tutorials/es/adding-bin-information.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 El número de identificación bancaria (BIN) se compone de los primeros seis u ocho dígitos de una tarjeta de crédito o débito y caracteriza la entidad emisora de la tarjeta.
 
-![BIN_image_digits_ES_2](//images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/474de4b5b02f9be016dd9aae13d83b4a/BIN_image_digits_ES_2.png)
+![BIN_image_digits_ES_2](https://images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/474de4b5b02f9be016dd9aae13d83b4a/BIN_image_digits_ES_2.png)
 
 Cuando la entidad emisora desea crear nuevos perfiles de tarjetas o emitir nuevas tarjetas para un modelo existente, debe crear nuevos BIN. Esto también se aplica cuando una [bandera de tarjeta](https://help.vtex.com/es/tutorial/que-es-una-bandera-de-tarjeta-de-credito--4bNba5QYuIwKEmac88KwyI) es adquirida por otra.
 
@@ -39,4 +39,4 @@ El ticket debe incluir como adjunto una plantilla rellenada con la siguiente inf
 
 Modelo de plantilla rellenada:
 
-![Bin_spreadsheet](//images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/34d0045e509662b159b442818a9854f6/Bin_spreadsheet.PNG)
+![Bin_spreadsheet](https://images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/34d0045e509662b159b442818a9854f6/Bin_spreadsheet.PNG)
diff --git a/docs/tutorials/es/adding-collections-cms.md b/docs/tutorials/es/adding-collections-cms.md
index 6e8e8e34c..609090740 100644
--- a/docs/tutorials/es/adding-collections-cms.md
+++ b/docs/tutorials/es/adding-collections-cms.md
@@ -33,7 +33,7 @@ Cuando la cantidad de colecciones creadas supera el límite de veinte, las colec
 
 La elección de los productos que van a hacer parte de una colección se hace a través de la creación de un __grupo__. Para esto, basta con hacer clic en __New Group__ dentro de la colección deseada. 
 
-![2019-06-06 16 22 46-Layout](//images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
+![2019-06-06 16 22 46-Layout](https://images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
 
 Antes de escoger qué productos harán parte del grupo, como veremos a continuación, es necesario atribuir un nombre y especificar el tipo de grupo creado.
 
@@ -75,17 +75,17 @@ Por ejemplo: al seleccionar la categoría `A` y la marca `B`, apenas los product
 
 Para agregar todos los productos de un determinado Departamento a un grupo, basta con seleccionar el Departamento deseado y hacer clic en __Save Group__, como muestra la imagen a continuación. 
 
-![seleção-departamento ES](//images.ctfassets.net/alneenqid6w5/dpKPktmtrMoOqVwdkTgGe/6c5ecc0f0446688acbe62f725811830b/sele____o-departamento_ES.png)
+![seleção-departamento ES](https://images.ctfassets.net/alneenqid6w5/dpKPktmtrMoOqVwdkTgGe/6c5ecc0f0446688acbe62f725811830b/sele____o-departamento_ES.png)
 
 Lo mismo aplica para los productos de una determinada Categoría o Subcategoría.
 
-![seleção-categoria-subcategoria ES](//images.ctfassets.net/alneenqid6w5/669cvCxhxCDtUObugHirqT/41a3b8cccc9e832a74452ce97256f8d5/sele____o-categoria-subcategoria_ES.png)
+![seleção-categoria-subcategoria ES](https://images.ctfassets.net/alneenqid6w5/669cvCxhxCDtUObugHirqT/41a3b8cccc9e832a74452ce97256f8d5/sele____o-categoria-subcategoria_ES.png)
 
 ## Productos por Marca
 
 Para crear un grupo con productos de una o más marcas, basta con seleccionar la marca deseada en la lista correspondiente. 
 
-![seleção-marca-coleção ES](//images.ctfassets.net/alneenqid6w5/7iBwt7BrU46rtjQagSZCtg/9b061b4b72ae669caa7b510e7db8f29f/sele____o-marca-cole____o_ES.png)
+![seleção-marca-coleção ES](https://images.ctfassets.net/alneenqid6w5/7iBwt7BrU46rtjQagSZCtg/9b061b4b72ae669caa7b510e7db8f29f/sele____o-marca-cole____o_ES.png)
 
 Las marcas se encuentran dispuestas en orden alfabética. Al hacer clic en la letra correspondiente a la inicial de la marca deseada, la lista se expande y exhibe las marcas existentes. 
 
@@ -95,7 +95,7 @@ Las marcas se encuentran dispuestas en orden alfabética. Al hacer clic en la le
 
 Al agregar un SKU a un grupo, el producto al cual está vinculado también será agregado. En un escenario en el que un producto tenga más de un SKU atribuido, agregar un único SKU hará con que todos los otros también sean agregados al grupo.  
 
-![selecao-sku-manual en & es](//images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
+![selecao-sku-manual en & es](https://images.ctfassets.net/alneenqid6w5/1GZTDTmU26MOuQ5u3dpOe7/04f1623d9c52bd939e4fabb455fab8ff/selecao-sku-manual_en.png)
 
 En el campo __Find SKUs__, es posible digitar el ID de cuantos SKUs se deseen, escribiendo los valores entre comas. 
 
@@ -117,21 +117,21 @@ Obtenga el modelo de archivo para la inclusión y exclusión de SKUs de la colec
 
 En el campo __Bulk Insert SKUs__, es posible importar por plantilla (formato `.xls`) una lista de SKUs que harán parte del grupo.
 
-![selecao-sku-planilha-insert en & es](//images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
+![selecao-sku-planilha-insert en & es](https://images.ctfassets.net/alneenqid6w5/9SITcqeeZNYTlAz5wi6IA/6765c51947698f35bf4ad198a51bcdc0/selecao-sku-planilha-insert_en.png)
 
 En la plantilla importada, todos los IDs de los SKUs deben estar dispuestos en la primera columna, con el encabezado, como se ejemplifica en la siguiente figura: 
 
-![exemplo-planilha-seleção-sku-coleção](//images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
+![exemplo-planilha-seleção-sku-coleção](https://images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
 
 Después de seleccionar la plantilla deseada, haga clic en la opción __import skus__ para enviar la información.
 
-![Import SKUs](//images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
+![Import SKUs](https://images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
 
 #### Exclusión masiva 
 
 Para evitar la exclusión manual de un SKU a la vez, también es posible usar el recurso de importación de plantilla para la exclusión masiva.
 
-![exclusao-skus-manualmente-planilha-coleção-cms en & es](//images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
+![exclusao-skus-manualmente-planilha-coleção-cms en & es](https://images.ctfassets.net/alneenqid6w5/moziGpjShzDpFw63tyDOa/ebfb61d2a2d2e09d494690ad0dc0ab62/exclusao-skus-manualmente-planilha-cole____o-cms_EN.png)
 
 En este caso específico, los SKUs listados en la plantilla importada se excluirán del  grupo. Para esto, haga clic en la opción __remove skus__ después que el archivo sea cargado.
 
@@ -147,7 +147,7 @@ En la sección de <strong>Other options</strong>, las opciones <strong>Pre-sales
 
 Note que apenas es posible seleccionar una de las dos opciones. Si quiere que se contemplen ambos escenarios, cree dos grupos y configure cada uno con la respectiva opción.
 
-![other-options-cms-coleções ES](//images.ctfassets.net/alneenqid6w5/4MijWxcZbcIjsVvHl3AcCB/14a9f700d992c28b2afb959829609bd1/other-options-cms-cole____es_ES.png)
+![other-options-cms-coleções ES](https://images.ctfassets.net/alneenqid6w5/4MijWxcZbcIjsVvHl3AcCB/14a9f700d992c28b2afb959829609bd1/other-options-cms-cole____es_ES.png)
 
 ### Pre-sales
 
diff --git a/docs/tutorials/es/adding-sku-specifications-or-fields.md b/docs/tutorials/es/adding-sku-specifications-or-fields.md
index 4085ff0c8..bdcb454e3 100644
--- a/docs/tutorials/es/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/es/adding-sku-specifications-or-fields.md
@@ -43,7 +43,7 @@ Antes de crear especificaciones, es importante entender que las especificaciones
 
 Por ejemplo: tomemos el producto **Camisa masculina**. En __Catálogo > Productos y SKU > SKU > Especificaciones__ (en la imagen a continuación), se puede ver que el grupo de especificaciones llamado **Características** está asociado a la categoría de la camisa. Ese grupo incluye un campo llamado **Color** y un campo llamado **Tamaño**.
 
-![heranca-especificacoes-sku-es](//images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/da96d3be83a3131b2eb3af35cb7f40fc/sku-specifications-inheritance-es.PNG)
+![heranca-especificacoes-sku-es](https://images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/da96d3be83a3131b2eb3af35cb7f40fc/sku-specifications-inheritance-es.PNG)
 
 Como se trata de una especificación del SKU, la información seleccionada en esa página se validará únicamente para esa variación del producto **Camisa masculina**. Se deben haber ingresado esas especificaciones de todos los SKU registrados en el producto **Camisa masculina** y todos los SKU de productos de la misma categoría.
 
@@ -85,7 +85,7 @@ Para crear un campo del SKU, sigue las instrucciones a continuación:
     * **Activo**: inserta o elimina este campo en el registro del SKU.
 7. Haz clic en `Guardar`.
 
-![sku-spec-1](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/849a49c91c0d22674c810c59e025ece3/es-sku-spec-2.gif)
+![sku-spec-1](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/849a49c91c0d22674c810c59e025ece3/es-sku-spec-2.gif)
 
 #### Tipos de campo de SKU
 
@@ -130,13 +130,13 @@ Los **valores** de los campos del SKU variarán según el tipo de campo elegido:
 
     Inserta un valor por línea y haz clic en la tecla `Enter` entre un valor y otro, tal como se muestra en la imagen a continuación.
 
-    ![valores-campo-sku-es](//images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/07d380bbf447d55bab05d846b4202501/valores-especificacoes-sku-es.PNG)
+    ![valores-campo-sku-es](https://images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/07d380bbf447d55bab05d846b4202501/valores-especificacoes-sku-es.PNG)
 
 8. Haz clic en `Guardar`.
 
     Los valores registrados se mostrarán en la [interfaz del registro del SKU](#registro-del-sku).
 
-![sku-spec-2](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/157aeb729b88c61a3341697b60008c7c/es-sku-spec-2.gif)
+![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/157aeb729b88c61a3341697b60008c7c/es-sku-spec-2.gif)
 
 <div class = "alert alert-info">
   <p>Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción <strong>Activo</strong>.</p>
@@ -181,7 +181,7 @@ Para completar las especificaciones de cada SKU de forma individual, sigue las i
 
 8. Haz clic en `Guardar`.
 
-![sku-spec-3](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/60cd4ea95d71f88edc9df50717d96ab7/es-sku-spec-3.gif)
+![sku-spec-3](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/60cd4ea95d71f88edc9df50717d96ab7/es-sku-spec-3.gif)
 
 #### Plantilla
 
@@ -204,7 +204,7 @@ Para rellenar las especificaciones del SKU de forma masiva por plantilla, debes
 9. Haz clic en **Seleccionar** para seleccionar el archivo con la plantilla completa en la computadora.
 10.  Haz clic en `Importar`.
 
-![sku-spec-4](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/0f468d1b9b92ac4b64aee8251491aaf1/es-sku-spec-4.gif)
+![sku-spec-4](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/0f468d1b9b92ac4b64aee8251491aaf1/es-sku-spec-4.gif)
 
 ## Más información
 - [Registrar especificaciones o campos de producto](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-producto--tutorials_106)
diff --git a/docs/tutorials/es/adding-specifications-or-product-fields.md b/docs/tutorials/es/adding-specifications-or-product-fields.md
index f9ebb9b52..e87f6d0cd 100644
--- a/docs/tutorials/es/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/es/adding-specifications-or-product-fields.md
@@ -43,7 +43,7 @@ Antes de crear especificaciones, es importante entender que las especificaciones
 
 Tomemos como ejemplo el producto **Televisor**. En __Catálogo > Productos y SKU > Modificar > Especificaciones__, en la imagen que vemos a continuación, se puede ver que el grupo de especificaciones llamado **Características** está asociado a la categoría de televisor. Ese grupo incluye un campo llamado **Pulgadas** y un campo llamado **Rango etario** que son obligatorios.
 
-![especificaciones-es](//images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/1dba4d4f967811f7b3f0a22872a2734d/especificaciones-es.PNG)
+![especificaciones-es](https://images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/1dba4d4f967811f7b3f0a22872a2734d/especificaciones-es.PNG)
 
 Como se trata de una especificación de producto, la información seleccionada en esa página será válida para todas las variaciones del producto **Televisor**. Estas especificaciones también deben haber sido rellenadas en todos los productos registrados en la misma categoría de televisor porque son campos obligatorios.
 
@@ -80,7 +80,7 @@ Para crear un campo de producto, sigue los pasos a continuación:
     * **Activo**: inserta o elimina este campo en el registro del producto (pestaña **Especificaciones**).
 7. Haz clic en `Guardar`.
 
-![product-spec-1](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/26805d3f463bbfeb47e8cbcb7a023005/ES_ProdutoGif_1_Alterado.gif)
+![product-spec-1](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/26805d3f463bbfeb47e8cbcb7a023005/ES_ProdutoGif_1_Alterado.gif)
 
 #### Tipos de campo de producto
 
@@ -146,7 +146,7 @@ Sin embargo, para los campos **Combo**, **Radio** y **Checkbox** es necesario re
 
     Los valores creados se mostrarán en la pestaña **Especificaciones** en el registro de Producto.
 
-![product-spec-2](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/35fc1b6e4edc189e4d4195d35f777514/ES_ProdutoGif_2_Alterado.gif)
+![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/35fc1b6e4edc189e4d4195d35f777514/ES_ProdutoGif_2_Alterado.gif)
 
 <div class = "alert alert-info">
   <p>Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción <strong>Activo</strong>.</p>
@@ -188,7 +188,7 @@ Para rellenar las especificaciones de cada producto individualmente, siga las  i
 
 6. Haz clic en `Guardar`.
 
-![product-spec-3](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/2f3c1e78b21f035b190aa3adcc55c8c2/ES_ProdutoGif_3_Alterado.gif)
+![product-spec-3](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/2f3c1e78b21f035b190aa3adcc55c8c2/ES_ProdutoGif_3_Alterado.gif)
 
 #### Plantilla
 
@@ -211,7 +211,7 @@ Para rellenar las especificaciones de los productos de forma masiva mediante una
 9. Haz clic en **Seleccionar** para seleccionar el archivo con la plantilla completada en su ordenador.
 10. Haz clic en `Importar`.
 
-![product-spec-4](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/fbb88c9ededec1bef032d9276837059e/ES_ProdutoGif_4_Alterado.gif)
+![product-spec-4](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/fbb88c9ededec1bef032d9276837059e/ES_ProdutoGif_4_Alterado.gif)
 
 ## Más información
 - [Registrar especificaciones o campos de SKU](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-sku--tutorials_119)
diff --git a/docs/tutorials/es/adding-your-brands.md b/docs/tutorials/es/adding-your-brands.md
index 881e60858..184aa28e0 100644
--- a/docs/tutorials/es/adding-your-brands.md
+++ b/docs/tutorials/es/adding-your-brands.md
@@ -19,4 +19,4 @@ Se requiere el [registro de marca](/es/tutorial/registrando-marcas) para la acti
 
 _El video presentado en este artículo aún no se ha traducido al español. Estamos trabajando para ofrecer más contenido en español. Gracias por la comprensión._
 
-<video class="wp-video-shortcode" id="video-2561-9" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4?_=9" />[//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4](//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4 "//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4")</video>
+<video class="wp-video-shortcode" id="video-2561-9" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4?_=9" />[//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4](https://assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4 "//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4")</video>
diff --git a/docs/tutorials/es/additional-shipping-costs.md b/docs/tutorials/es/additional-shipping-costs.md
index 9134e04bc..f72441610 100644
--- a/docs/tutorials/es/additional-shipping-costs.md
+++ b/docs/tutorials/es/additional-shipping-costs.md
@@ -17,7 +17,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Los adicionales de flete son importes que se añaden al costo de envío mediante las [políticas de envío](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Así, al configurar un valor de costo para la entrega de los ítems de su tienda, puede establecer una tarifa fija e incluir valores adicionales. El costo de envío fijo más los adicionales constituyen el costo de la [tarifa de envío](https://help.vtex.com/pt/tutorial/gerenciar-valores-de-frete--tutorials_141).
 
-![Tarifa envio ES](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
+![Tarifa envio ES](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
 
 Los valores adicionales pueden configurarse según:
 
@@ -29,7 +29,7 @@ Los valores adicionales pueden configurarse según:
 * El costo de envío: 
 [adicional de flete](https://help.vtex.com/es/tutorial/adicionales-de-flete--2vqGwMn0LabkOHY6zSHYNV#adicional-de-flete).
 
-![adicionais frete ES](//images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/9aef6304664af38fa0a9c03ed1916f7e/adicionais_frete_ES.svg)
+![adicionais frete ES](https://images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/9aef6304664af38fa0a9c03ed1916f7e/adicionais_frete_ES.svg)
 
 <div class="alert alert-danger">
 Es posible tener todos los adicionales configurados al mismo tiempo para una única tarifa de envío. El cálculo final de la <a href="https://help.vtex.com/es/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">tarifa de envío</a> es la suma de todos los adicionales registrados más la tarifa fija del flete. 
@@ -62,7 +62,7 @@ Adicional de flete: ($10+$0+$2+$5)x10%=$1,70
 Adicionales de flete: ($2+$5+$1,7)=$8,70  
 Tarifa de envío: ($10+$8,70)=$18,70  
 
-![faixa-peso ES](//images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/2af51a115ce00bd21c47e0d38fbea3d1/faixa-peso_ES.png)
+![faixa-peso ES](https://images.ctfassets.net/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/2af51a115ce00bd21c47e0d38fbea3d1/faixa-peso_ES.png)
 
 ### Configuración 
 
@@ -162,5 +162,5 @@ Para configurar el adicional de flete, vaya al menú del Admin.
     1. Si desea incluir una tasa del 10%, rellene el campo con 10. Para los números decimales, utilice puntos en lugar de comas, como en 1.67.
 3. Haga clic en `Guardar`.
 
-![adicional configuracoes ES](//images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/9e15747bc9585ee7467ecad7c06ecc7e/adicional_configuracoes_ES.png)
+![adicional configuracoes ES](https://images.ctfassets.net/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/9e15747bc9585ee7467ecad7c06ecc7e/adicional_configuracoes_ES.png)
 
diff --git a/docs/tutorials/es/admin-v4-getting-started.md b/docs/tutorials/es/admin-v4-getting-started.md
index 31cf72442..9fdd93eb2 100644
--- a/docs/tutorials/es/admin-v4-getting-started.md
+++ b/docs/tutorials/es/admin-v4-getting-started.md
@@ -24,24 +24,24 @@ Para lograrlo, estamos rediseñando múltiples partes de la experiencia y realiz
 ## Mejora en la navegación
 Todo lo que necesita para gestionar su tienda VTEX sigue presente en el Admin v4, solo que ahora con una organización más sencilla. Nuestro menú de navegación superior y lateral izquierdo se ha reestructurado desde cero, agrupando categorías similares de una manera más clara para reducir distracciones y ayudar a su equipo a encontrar lo que necesita con mayor rapidez. También puede utilizar la barra de búsqueda para encontrar secciones específicas en el menú lateral.
 
-![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Centro de información
 Aquí es donde reunimos todos los enlaces útiles de nuestro ecosistema VTEX, para ayudarlo a obtener lo mejor de nuestra plataforma VTEX. Al hacer clic en el botón «?» de la barra superior, puede acceder a nuestro Centro de ayuda, Blog, Portal del desarrollador, Status de la plataforma y página de soporte.    
-![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Configuración de la tienda
 Para esta nueva experiencia, hemos concentrado todas las configuraciones de todas las secciones en una pestaña específica: Configuración de la tienda. A través de esta mejora, puede acceder fácilmente a todas las configuraciones que afectan a cada servicio de su cuenta.
-![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Configuración del perfil
 El avatar de su perfil, en la esquina superior derecha, alberga ahora toda la configuración relacionada con su usuario y su cuenta. A través del avatar puede acceder a la configuración del usuario, la configuración de la cuenta, la información de facturación, cambiar la configuración regional de su administrador, cambiar a la versión anterior y cerrar la sesión. Con esta mejora, hemos separado la configuración de su perfil de las configuraciones que afectan a su tienda en sí. Ahora tiene más control y visibilidad sobre las acciones que afectan a su negocio y las que afectan a su perfil.
-![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 ## Página de inicio renovada
 Nuestra página de inicio del panel administrativo ha sido rediseñada para ofrecerle una visión general de alto nivel de su tienda, como una cabina de mando para sus operaciones de comercio digital. Por eso ahora se llama **Dashboard**.
 Tan pronto como inicie sesión en Admin v4, verá métricas y gráficos útiles para monitorear el rendimiento de su tienda, como los ingresos y el número de pedidos, el embudo de ventas y las tasas de conversión, y sus 10 productos de mayor venta. Vea todos los componentes del nuevo Dashboard y aprenda cómo funcionan en la siguiente lista.
-![Dashboard v4](//images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
+![Dashboard v4](https://images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
 
 - **Pedidos:**  número de pedidos realizados.  Todos los datos sobre pedidos e ingresos que proceden del Sistema de Gestión de Pedidos de VTEX.  
 - **Sesiones:** número de visitas a la tienda.  
diff --git a/docs/tutorials/es/ads-from-vtex-sales-app.md b/docs/tutorials/es/ads-from-vtex-sales-app.md
index 54baf9acb..c29c806b5 100644
--- a/docs/tutorials/es/ads-from-vtex-sales-app.md
+++ b/docs/tutorials/es/ads-from-vtex-sales-app.md
@@ -63,18 +63,18 @@ Para crear una página de anuncios para VTEX Sales App, sigue los pasos a contin
     - **Título de la vitrina:** nombre de la vitrina que se mostrará en la página.
     - **ID del producto:** número identificador del producto que deseas mostrar. Campo obligatorio.
     - **ID del SKU del producto:** número identificador del SKU del producto que deseas mostrar. Campo opcional.
-![vitrine-produto-es](//images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/99d80481198a5789b864e7b3cc621c9f/image.png)
+![vitrine-produto-es](https://images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/99d80481198a5789b864e7b3cc621c9f/image.png)
 Después de rellenar los campos, se mostrará la imagen del producto con precio "a partir de". Si incluyes el SKU, se mostrará el precio y la promoción del SKU indicado. Puedes incluir más productos al hacer clic en `+ NUEVO PRODUCTO`. Puedes agregar hasta 10 productos en cada vitrina.
 El resultado de la vitrina de productos se mostrará como en la siguiente imagen.
-![vitrine-produto-2-es](//images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/2b1605234e989064a7c188b6f3ce31a8/image.png)
+![vitrine-produto-2-es](https://images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/2b1605234e989064a7c188b6f3ce31a8/image.png)
   - **Vitrina de resultados de búsqueda:** mostrará los productos de resultados de búsqueda que determines. Rellena la siguiente información:
     - **Título de la vitrina:** nombre de la vitrina que se mostrará en la página.
     - **Imagen de búsqueda:** imagen que mostrará la selección de productos en la vitrina.
     - **Nombre de la búsqueda:** nombre de la búsqueda que se mostrará en la página.
     - **Término de búsqueda:** término de búsqueda que servirá de referencia para los productos.
-![vitrine-busca-es](//images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/832a5b243a2a82f170eebb8d77574009/image.png)
+![vitrine-busca-es](https://images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/832a5b243a2a82f170eebb8d77574009/image.png)
 Cuando el vendedor haga clic en el término de búsqueda, se le redirigirá a los resultados de búsqueda que se hayan establecido en **Término de búsqueda**. Puedes incluir hasta 10 búsquedas en cada vitrina. El resultado del ejemplo se muestra en la siguiente imagen:
-![vitrine-busca-2-es](//images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/2381c9859c4adeaec5953b0ac87d7b42/image.png)
+![vitrine-busca-2-es](https://images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/2381c9859c4adeaec5953b0ac87d7b42/image.png)
 <ol start="6">
   <li>Después de crear las secciones, haz clic en <code>Guardar</code> y, luego, haz clic en <code>Publicar</code> y <code>Publicar ahora</code> para finalizar.</li>
 </ol> 
@@ -83,7 +83,7 @@ La publicación de la vitrina se añadirá a la fila de indexación y se publica
 - **Vitrina de colección:** mostrará los productos de la colección que definas. Rellena la siguiente información: 
   - **Título de la vitrina:** nombre de la vitrina que se mostrará en la página.   - **ID de la colección:** número del identificador de la colección que se mostrará en la página.
 
-![Vitrine - ES](//images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/b512969705a8d78857febbdbbc892fc8/Vitrine_-_ES.png)
+![Vitrine - ES](https://images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/b512969705a8d78857febbdbbc892fc8/Vitrine_-_ES.png)
 
 ## Activar el menú de anuncios en VTEX Sales App
 
@@ -94,12 +94,12 @@ https://{account}.myvtex.com/admin/portal/#/sites
 2. Haz clic en el botón del engranaje <i class="fas fa-cog"></i>.
 3. Selecciona la pestaña **Código**.
 4. En la pestaña lateral, selecciona `checkout-instore-custom-js`.
-![checkout-instore-custom-js-file](//images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/a09ddfdf23851e0ada81931af2ed5b19/image.png)
+![checkout-instore-custom-js-file](https://images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/a09ddfdf23851e0ada81931af2ed5b19/image.png)
 5. En el objeto `window.INSTORE_CONFIG`, agrega la flag `enableExplore: true,`.
-![window.INSTORE_CONFIG](//images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/c0003c9637209f503401fea07db839cb/image.png)
+![window.INSTORE_CONFIG](https://images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/c0003c9637209f503401fea07db839cb/image.png)
 6. Haz clic en <i class="fas fa-save"></i> `Guardar`. 
 7. Opcionalmente, puedes determinar que la página de inicio del vendedor sea la página de anuncios. Para lograrlo, agrega la flag `initialPage : 'advertisements',` en el objeto `window.INSTORE_CONFIG`.
-![initialPage : advertisements](//images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/88e4f64f2707fd1dbbe95d6b9861e712/image.png)
+![initialPage : advertisements](https://images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/88e4f64f2707fd1dbbe95d6b9861e712/image.png)
 
 ## Acceder a los anuncios en VTEX Sales App
 
@@ -108,4 +108,4 @@ En VTEX Sales App, el vendedor podrá acceder a la página de anuncios de dos ma
 * **Página de inicio:** si el administrador de la tienda previamente registró la página de anuncios como la página de inicio del vendedor, al iniciar sesión en la plataforma, se redirigirá al vendedor directamente a la página de anuncios. Esta configuración garantiza que los vendedores siempre estén al día sobre los anuncios y promociones relevantes, de manera inmediata y en cuanto acceden al sistema.
 * **Menú Explorar:** si la página de anuncios no es la página de inicio, el vendedor puede acceder a ella fácilmente desde el menú **Explorar**. Para acceder a la página de anuncios, el vendedor debe hacer clic en el menú **Explorar**. Luego, se redirigirá al vendedor a la página de anuncios, donde podrá ver e interactuar con los productos y promociones disponibles.
 
-![vitrine-sale-app-es](//images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/ffca39f0f0a2b0bdc59c39ebd88ddc71/image.png)
+![vitrine-sale-app-es](https://images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/ffca39f0f0a2b0bdc59c39ebd88ddc71/image.png)
diff --git a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
index 5b160f79c..70470127d 100644
--- a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
@@ -47,7 +47,7 @@ Actualmente, VTEX cuenta con un único formato de anuncio: resultados de búsque
 6. Selecciona los productos que deseas anunciar utilizando una de las siguientes opciones:
 
    * __Buscar productos por EAN:__ buscar productos de tu catálogo por EAN.
-   * __Cargar archivo:__ enviar un archivo CSV con una lista de códigos EAN y ofertas, según [este ejemplo](//assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/c61c4a27f462bb3fa85457eed1bad0b8/teste-ads.csv). Los EAN son obligatorios y las ofertas son opcionales en el archivo.
+   * __Cargar archivo:__ enviar un archivo CSV con una lista de códigos EAN y ofertas, según [este ejemplo](https://assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/c61c4a27f462bb3fa85457eed1bad0b8/teste-ads.csv). Los EAN son obligatorios y las ofertas son opcionales en el archivo.
 
 7. En la sección **Presupuesto, oferta y cronograma**, haz clic en el botón de editar <i class="fas fa-pencil-alt"></i>.
 8. Define los valores de las ofertas para cada producto. Puedes definir cada valor individualmente.
@@ -100,7 +100,7 @@ Puedes pausar un producto específico de tu campaña para que el anuncio corresp
 
 En la pantalla de inicio de la aplicación [VTEX Ad Network](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), también encontrarás información sobre tus campañas en curso.
 
-![vtex_ad_network_create_campaign_ES](//images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/1d60c965f3c6e4cf92a2f7487e938cb9/vtex_ad_network_create_campaign.png)
+![vtex_ad_network_create_campaign_ES](https://images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/1d60c965f3c6e4cf92a2f7487e938cb9/vtex_ad_network_create_campaign.png)
 
 En la parte superior se muestran los datos agregados:
 
diff --git a/docs/tutorials/es/affiliates-program-app.md b/docs/tutorials/es/affiliates-program-app.md
index d86916f29..dd34260f9 100644
--- a/docs/tutorials/es/affiliates-program-app.md
+++ b/docs/tutorials/es/affiliates-program-app.md
@@ -40,11 +40,11 @@ La aplicación crea tres tipos de páginas para los afiliados, que disponen de e
 
 La **página del afiliado** es la URL de la tienda VTEX que comparten con los clientes. Ve un ejemplo en la siguiente imagen:
 
-![url_pagina_es_3](//images.ctfassets.net/alneenqid6w5/3BxA8DMUUHVt7qZs5mYUhx/72903370216b4def73a08cc485c3c81d/url_pagina_es.png)
+![url_pagina_es_3](https://images.ctfassets.net/alneenqid6w5/3BxA8DMUUHVt7qZs5mYUhx/72903370216b4def73a08cc485c3c81d/url_pagina_es.png)
 
 La **página del perfil del afiliado** es una interfaz a través de la cual pueden seguir y gestionar sus pedidos y comisiones. Ve un ejemplo en la siguiente imagen:
 
-![profile_pagina_es_3](//images.ctfassets.net/alneenqid6w5/37jFSHHD7RweXxkvOzelPL/25c11f8c83fe7871282c513bef26c2ee/profile_pagina_es.png)
+![profile_pagina_es_3](https://images.ctfassets.net/alneenqid6w5/37jFSHHD7RweXxkvOzelPL/25c11f8c83fe7871282c513bef26c2ee/profile_pagina_es.png)
 
 La página de **registro** permite que los interesados en convertirse en afiliados completen sus datos para solicitar el registro en su tienda VTEX.
 
@@ -72,7 +72,7 @@ La página **de Gestión de afiliados** permite realizar las siguientes acciones
 - [Ver detalles del afiliado](#ver-detalles-del-afiliado)
 - [Editar afiliado](#editar-afiliado)
 
-![affiliates_management_page_es](//images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/de5a0b8ff2c25569692f4c2eb99c730d/affiliates_management_page_es.jpg)
+![affiliates_management_page_es](https://images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/de5a0b8ff2c25569692f4c2eb99c730d/affiliates_management_page_es.jpg)
 
 ### Agregar afiliado
 
@@ -119,7 +119,7 @@ La página de **Gestión de pedidos** permite realizar las siguientes acciones:
 - [Exportar plantilla de pedidos](#exportar-lista-de-pedidos)
 - [Ver detalles del pedido](#ver-detalles-del-pedido)
 
-![orders_management_page_es](//images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/56d938c239cb62d2396e4152adf5df08/orders_management_page_es.jpg)
+![orders_management_page_es](https://images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/56d938c239cb62d2396e4152adf5df08/orders_management_page_es.jpg)
 
 ### Seguir dashboard
 
@@ -172,7 +172,7 @@ La página de **Gestión de comisiones** permite realizar las siguientes accione
 - [Importar comisiones](#importar-comisiones)
 - [Descargar la última importación](#descargar-la-ultima-importacion)
 
-![commissions_ management_page_es](//images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/a87a79d01580e58605e0a21461d8a381/commissions__management_page_en.png)
+![commissions_ management_page_es](https://images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/a87a79d01580e58605e0a21461d8a381/commissions__management_page_en.png)
 
 ### Buscar comisiones
 
diff --git a/docs/tutorials/es/all-orders.md b/docs/tutorials/es/all-orders.md
index 9bd41a43e..f6ba9d8ff 100644
--- a/docs/tutorials/es/all-orders.md
+++ b/docs/tutorials/es/all-orders.md
@@ -28,7 +28,7 @@ La página **Todos los pedidos** permite a los administradores de la tienda hace
 
 Las siguientes secciones proporcionan más detalles sobre cada componente de la página y sus acciones.
 
-![Order Listing EN](//images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/458efe24f7fcb7653eb23d1ea1d7110b/Order_Listing_EN.gif)
+![Order Listing EN](https://images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/458efe24f7fcb7653eb23d1ea1d7110b/Order_Listing_EN.gif)
 
 Además de buscar pedidos en **Pedidos > Todos los pedidos**, puede buscar pedidos desde cualquier página del Admin VTEX utilizando la barra de búsqueda global en la parte superior de la página. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
 
@@ -167,7 +167,7 @@ A continuación, encontrarás más detalles sobre cada columna:
 
 ## VTEX DO
 
-![VTEX Do overview ES](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
+![VTEX Do overview ES](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
 
 [VTEX DO](https://help.vtex.com/es/tutorial/vtex-do-beta--7KMbRL4OslN8DTX9oiuCiu) es un gestor de tareas creadas por el Admin VTEX automáticamente y que requieren una acción manual por parte del equipo de _ecommerce_. 
 
diff --git a/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
index bc2642bed..99ea9573b 100644
--- a/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
@@ -110,7 +110,7 @@ Para instalar la aplicación, accede a VTEX App Store:
 Las configuraciones realizadas en el campo Automatic Invoice se aplicarán a todos los pedidos.
 </div>
 
-![MCF](//images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/604c465dd3344b9cc04b722d03cb5005/Amazon_MCF_EN.PNG)
+![MCF](https://images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/604c465dd3344b9cc04b722d03cb5005/Amazon_MCF_EN.PNG)
 
 ### Integración del catálogo
 
diff --git a/docs/tutorials/es/amazon-offer-matching.md b/docs/tutorials/es/amazon-offer-matching.md
index 0554299bb..67a8c8059 100644
--- a/docs/tutorials/es/amazon-offer-matching.md
+++ b/docs/tutorials/es/amazon-offer-matching.md
@@ -19,7 +19,7 @@ Cada vez que se envía a Amazon un [SKU](https://help.vtex.com/es/tracks/catalog
 
 El EAN registrado en VTEX se utiliza para hacer la equivalencia con los [ASIN](https://afiliados.amazon.com.mx/) (*Amazon Standard Identification Number, o número de identificación estándar de Amazon*) correspondientes en Amazon. Para hacer el emparejamiento entre EAN y ASIN, es necesario realizar el matching manualmente. La correspondencia entre EAN y ASIN debe ser exacta para que los anuncios se vinculen correctamente.  
 
-![Presentación match de anuncios](//images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/4c1f3a16c14e3201bd0724e0c6907cad/Match-an__ncios-Amazon.gif)
+![Presentación match de anuncios](https://images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/4c1f3a16c14e3201bd0724e0c6907cad/Match-an__ncios-Amazon.gif)
 
 ## Pestaña Oportunidad  
 
@@ -78,7 +78,7 @@ Para aprobar el match, el seller debe seguir los pasos a continuación:
 1. En la pestaña `Oportunidad`, haz clic en el ícono <i class="fas fa-ellipsis-v"></i>.  
 2. Haz clic en la opción `Ver detalles`.  
 3. Consulta la información que aparece en la página.    
-![Match individual de anuncios](//images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/eac88bc236fafb26cf67f89276e6162f/Match_individual_AMZ.png)
+![Match individual de anuncios](https://images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/eac88bc236fafb26cf67f89276e6162f/Match_individual_AMZ.png)
 
 4. Según la conclusión del análisis, haz clic en uno de los botones disponibles: `Publicar`, `Rechazar y pedir revisión` o `Rechazar`.
 
@@ -91,13 +91,13 @@ En la pestaña `Oportunidad`, todos los productos listados que presenten equival
 1. En la pestaña `Oportunidad`, marca la casilla situada junto al título de los anuncios con equivalencia SKU <> ASIN.  
 Al seleccionar los productos, aparecerá en la pantalla el siguiente pop up indicando cuántos productos se han seleccionado.  
 
-![popupES](//images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/4b97de7bb44236561a9474189936cb4c/MATCHAMZ_ES.png)
+![popupES](https://images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/4b97de7bb44236561a9474189936cb4c/MATCHAMZ_ES.png)
 
 2. Al finalizar la selección de productos, haz clic en `Publicar seleccionados`.  
 
 3. En el pop up de confirmación del matching, comprueba los anuncios elegidos y haz clic en `Publicar seleccionados`.  
 
-![Confirmacioin del matching](//images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/5762aa090ef7e6e3137fd99e81cba8f5/CONFIRMACION_MATCH.png)
+![Confirmacioin del matching](https://images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/5762aa090ef7e6e3137fd99e81cba8f5/CONFIRMACION_MATCH.png)
 
 Tras la confirmación, tus anuncios se enviarán y se pondrán en cola para su procesamiento. Una vez aprobado, el anuncio aparecerá en la pestaña __Anuncios__, donde podrás __"ver detalles" de tu anuncio__, __ver "anuncio sugerido" por Amazon__ y __buscar__ anuncios en la barra de búsqueda.  
 
diff --git a/docs/tutorials/es/analytics.md b/docs/tutorials/es/analytics.md
index 92798fc89..261b5b2f4 100644
--- a/docs/tutorials/es/analytics.md
+++ b/docs/tutorials/es/analytics.md
@@ -80,8 +80,8 @@ Para exportar un informe en formato CSV, debe seguir los pasos que se indican a
 
 El informe CSV descargado tiene dos tablas. La primera tabla, que se muestra a continuación, contiene información sobre los términos de búsqueda y las métricas de embudo (desde la columna **ProductsClick** hasta la columna **ProductsSold**), si se ha seleccionado esa opción.
 
-![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
+![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/5910a3f67d31b5270841e5d4ef2f31bd/search-report-term.png)
 
 La segunda tabla, que se muestra a continuación, muestra los datos del periodo seleccionado, mostrando la columna **Date**, que indica la fecha de la búsqueda.
 
-![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
+![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/50c65ac3ba4741c35fe820fd265b78de/search-report-date.png)
diff --git a/docs/tutorials/es/analyze-a-products-reservations.md b/docs/tutorials/es/analyze-a-products-reservations.md
index eaaf9296a..a4daf42c9 100644
--- a/docs/tutorials/es/analyze-a-products-reservations.md
+++ b/docs/tutorials/es/analyze-a-products-reservations.md
@@ -23,4 +23,4 @@ Para consultar las reservas autorizadas, es decir, aquellas que aún no han teni
 
 Para consultar los pedidos con status `Faturado`, es decir, pago ya aprobado, basta con hacer clic en el número mostrado en la columna **Itens em manuseio** (Ítems en manejo).
 
-![Reservations GIF](//images.contentful.com/alneenqid6w5/4xUy1O7pUA66UaQkcuU0au/53f39fe9b3cbe2f4c3e2a8e6316e66a9/Reservations.gif)
+![Reservations GIF](https://images.contentful.com/alneenqid6w5/4xUy1O7pUA66UaQkcuU0au/53f39fe9b3cbe2f4c3e2a8e6316e66a9/Reservations.gif)
diff --git a/docs/tutorials/es/antifraud-provider.md b/docs/tutorials/es/antifraud-provider.md
index 75eef0170..cc3f16499 100644
--- a/docs/tutorials/es/antifraud-provider.md
+++ b/docs/tutorials/es/antifraud-provider.md
@@ -46,14 +46,14 @@ Antes de configurar el ambiente VTEX, el proveedor debe implementar el servicio
 ### 3. Portal de administración del Antifraud Provider
 Después de recibir los datos de acceso e implementar el back-end, el proveedor puede acceder a la herramienta de aprobación a través del Admin de VTEX. Para ello, debe instalar el App del Antifraud Provider en el menú Apps:
 
-![print5](//images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
+![print5](https://images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
 
 Haga clic en la App instalada o acceda a `https://{{AccountName}}.myvtex.com/admin/antifraud-provider`, sustituyendo `{{AccountName}}` por el nombre de su cuenta en la plataforma. En este ambiente, es posible registrar los datos de configuración de back-end del proveedor y realizar pruebas de integración.
 
-![print6](//images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
+![print6](https://images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
 
 ### 4. Configuración inicial
-![print1](//images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
+![print1](https://images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
 
 Al acceder al ambiente por el enlace descrito arriba, usted verá un formulario. Rellene los campos de acuerdo con las siguientes indicaciones:
 
@@ -77,7 +77,7 @@ Después de llenar los campos correctamente, el sistema comprobará las transacc
 
 Las pruebas que se deben realizar en su integración antes de mandarla para la evaluación de VTEX se muestran abajo. Usted puede seleccionar qué pruebas desea ejecutar, pero para que su integración pase por el análisis de nuestro equipo, __todas ellas necesitan ser realizadas__. Por lo tanto, recomendamos que todos ellos permanezcan seleccionados.
 
-![print2](//images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
+![print2](https://images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
 
 ### 5. Pruebas
 Al hacer clic en el botón __Execute tests__, el Antifraud Provider aplicará las pruebas en su integración para los diferentes escenarios posibles. Es importante recordar que __todos ellos son obligatorios__ y, para ejecutarlos, su servicio necesita estar en HTTPS. Las pruebas son:
@@ -107,11 +107,11 @@ Para cada prueba del Antifraud Provider Protocol, enviamos un final de ID espec
 ### 6. Resultados
 Después de ejecutar las pruebas, el sistema devuelve los resultados, tanto positivos como negativos. El sistema también trae la información de los resultados esperados para cada prueba. Así, usted tiene más visibilidad de lo que debe ser ajustado en caso de error.
 
-![print3](//images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
+![print3](https://images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
 
 Para visualizar de forma detallada cada acción realizada por la integración (y, así, identificar posibles errores), basta con hacer clic en el enlace __Show logs__. Una lista con la información completa de los eventos que ocurrieron durante la prueba se mostrará por debajo de los resultados.
 
-![print4](//images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
+![print4](https://images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
 
 Cuando su integración ha pasado todas las pruebas con éxito, sólo tiene que abrir un ticket en el [help de VTEX](/es/support) informando la conclusión. Sin embargo, antes de abrir el ticket, asegúrese de tener la siguiente información:
 
@@ -135,7 +135,7 @@ Utilice la URL `https://{{AccountName}}.myvtex.com/admin/license-manager/#/home`
 Una vez que la integración con su antifraude está aprobada, un conector se pondrá a disposición para que las tiendas VTEX lo configuren en sus respectivos sitios web. Para hacer esto, además del contrato con su empresa, la tienda deberá tener en las manos dos claves: "X-PROVIDER-API-AppKey" y "X-PROVIDER-API-AppToken".
 
 Un ejemplo de cómo va a quedar la pantalla de configuración del antifraude para la tienda VTEX:
-![print8](//images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
+![print8](https://images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
 
 Estas llaves deben estar disponibles por usted y van a servir para identificar la tienda que ha contratado y está utilizando su servicio de antifraude.
 
diff --git a/docs/tutorials/es/application-keys.md b/docs/tutorials/es/application-keys.md
index cf5cff2de..14ab791b9 100644
--- a/docs/tutorials/es/application-keys.md
+++ b/docs/tutorials/es/application-keys.md
@@ -62,7 +62,7 @@ Para crear claves de aplicación internas en tu cuenta sigue los pasos a continu
 
     Se te redirigirá a la página **Mis claves**, ilustrada a continuación,  donde podrás consultar todas las [claves de aplicación internas](#claves-de-aplicacion-internas).
 
-    ![Mis Claves](//images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/68300cda392cc27ff02bc50af0bc2b7e/mis-claves-es.png)
+    ![Mis Claves](https://images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/68300cda392cc27ff02bc50af0bc2b7e/mis-claves-es.png)
 
     Estos son los campos visibles en la página **Mis claves**:
 
@@ -114,7 +114,7 @@ Al editar una clave de aplicación, puedes:
 
 Tras agregar los roles de acceso a una clave de aplicación, esta aparecerá en la página **Claves de aplicación**.
 
-![Claves de aplicación](//images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/931a3bd780840b11e47bf7d2a84ff718/claves-es.png)
+![Claves de aplicación](https://images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/931a3bd780840b11e47bf7d2a84ff718/claves-es.png)
 
 Consulta a continuación los campos visibles en la página **Claves de aplicación**:
 
diff --git a/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
index e0492085b..66fae1618 100644
--- a/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
@@ -25,7 +25,7 @@ Se puede hacer esa aprobación manualmente por el OMS de forma simple, conforme
 2. Haga clic en la transaccione.
 3. Haga clic en el botón __Notificar el pago__.
 
-![NotificarES](//images.ctfassets.net/alneenqid6w5/3IfQ1FNhluYWWgcMUEaUq0/ea25ce5d59b8ff98c593bc9382312f85/NotificarES.png)
+![NotificarES](https://images.ctfassets.net/alneenqid6w5/3IfQ1FNhluYWWgcMUEaUq0/ea25ce5d59b8ff98c593bc9382312f85/NotificarES.png)
 
 **Después de la aprobación del pago, el pedido entrará en el flujo normal de compra.**
 
diff --git a/docs/tutorials/es/apps-overview.md b/docs/tutorials/es/apps-overview.md
index 4a4419b85..b92ee8f46 100644
--- a/docs/tutorials/es/apps-overview.md
+++ b/docs/tutorials/es/apps-overview.md
@@ -36,7 +36,7 @@ El menú de Apps permite a los comerciantes descargar nuevas aplicaciones direct
 
 Puedes encontrar estas operaciones en el menú Apps de tu Admin actualizado.
 
-![Apps Overview menu ES](//images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/ae534adadd4b3455ed9ba7827f367a2d/Apps_Overview_menu_ES.jpg)
+![Apps Overview menu ES](https://images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/ae534adadd4b3455ed9ba7827f367a2d/Apps_Overview_menu_ES.jpg)
 
 A continuación encontrarás más detalles sobre las diferentes secciones y páginas de esta funcionalidad, que pronto estará disponible en el Admin actualizado. 
 
diff --git a/docs/tutorials/es/assembly-options-app.md b/docs/tutorials/es/assembly-options-app.md
index 1928fe4b4..bff13cdd0 100644
--- a/docs/tutorials/es/assembly-options-app.md
+++ b/docs/tutorials/es/assembly-options-app.md
@@ -37,7 +37,7 @@ Una vez instalada, la página **Catálogo > Opciones de ensamblaje** estará dis
 
 En el Admin VTEX, en **Catálogo > Opciones de ensamblaje**, tendrás acceso a una lista con todas las Opciones de ensamblaje registradas en tu tienda cuando uses la aplicación.
 
-![assembly-options-app-es](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
+![assembly-options-app-es](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/322bc4f9209983c3fc2f5c7bc85321d6/assembly-options-app-es.PNG)
 
 La información que aparecerá en la lista será:
 
diff --git a/docs/tutorials/es/assembly-options-in-vtex-sales-app.md b/docs/tutorials/es/assembly-options-in-vtex-sales-app.md
index 16463ee8b..c9a1655b4 100644
--- a/docs/tutorials/es/assembly-options-in-vtex-sales-app.md
+++ b/docs/tutorials/es/assembly-options-in-vtex-sales-app.md
@@ -35,9 +35,9 @@ Existen dos escenarios en los que se pueden agregar servicios a productos presen
 2. Selecciona la opción de servicio que deseas y haz clic en el botón **Continuar al carrito**.
 3. Una vez finalizado el proceso, podrás ver en tu carrito el servicio seleccionado, con el valor total del pedido.
 
-![Garantia estendida - ES](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/700c85400ed179eb7aaeecfd963160ee/Cen_rio_1__T1__-_ES.png)
+![Garantia estendida - ES](https://images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/700c85400ed179eb7aaeecfd963160ee/Cen_rio_1__T1__-_ES.png)
 
-![Carrinho - ES](//images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/2b1f4c689a2f9ff02705f9e2772c799f/Cen_rio_1__T2__-_ES.png)
+![Carrinho - ES](https://images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/2b1f4c689a2f9ff02705f9e2772c799f/Cen_rio_1__T2__-_ES.png)
 
 **Escenario 2:** selección de múltiples servicios
 
@@ -48,8 +48,8 @@ Existen dos escenarios en los que se pueden agregar servicios a productos presen
 5. Haz clic en el botón Continuar. Si alguno de los servicios requiere información adicional, rellena los campos necesarios para vincular esta información al servicio adquirido.
 6. Haz clic en el botón Aplicar.
 
-![Garantia estendida - ES](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/700c85400ed179eb7aaeecfd963160ee/Cen_rio_1__T1__-_ES.png)
+![Garantia estendida - ES](https://images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/700c85400ed179eb7aaeecfd963160ee/Cen_rio_1__T1__-_ES.png)
 
-![Seguro - ES](//images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/dae714edffa7f98926c9b86a321a2170/Cen_rio_2__T2__-_ES.png)
+![Seguro - ES](https://images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/dae714edffa7f98926c9b86a321a2170/Cen_rio_2__T2__-_ES.png)
 
-![Ordem pedido - ES](//images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/7cab56abab6aa79d6f1483bb492486c2/Cen_rio_2__T3__-_ES.png)
+![Ordem pedido - ES](https://images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/7cab56abab6aa79d6f1483bb492486c2/Cen_rio_2__T3__-_ES.png)
diff --git a/docs/tutorials/es/assembly-options.md b/docs/tutorials/es/assembly-options.md
index 173584d1d..600d5d101 100644
--- a/docs/tutorials/es/assembly-options.md
+++ b/docs/tutorials/es/assembly-options.md
@@ -23,7 +23,7 @@ Una assembly option es un [anexo](https://help.vtex.com/es/tutorial/que-es-un-an
 
 En el siguiente ejemplo, una tienda ofrece múltiples assembly options para el producto _custom bell_ (campana personalizada). Estas opciones se muestran en la página de producto, donde el cliente puede seleccionar las opciones deseadas. Dependiendo de las opciones, puede haber un coste adicional para el SKU.
 
-![assembly-option-ES](//images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/a4598c720776d55966ff96a0423af592/image.png)
+![assembly-option-ES](https://images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/a4598c720776d55966ff96a0423af592/image.png)
 
 Puedes combinar distintos [SKU](https://help.vtex.com/es/tutorial/que-es-un-sku--1K75s4RXAQyOuGUYKMM68u) para ofrecer assembly options, como los _Bells add-ons Roman_ o los _Bells add-ons 1-3 lines_ en el ejemplo anterior. Si un ítem está agotado, se mostrará como no disponible.
 
@@ -61,7 +61,7 @@ El primer `[x-y]` corresponde a las reglas que se aplican al grupo, y entre cada
 | \[0-3\]#10000\[1-2\]**\[1\]**pricetable1;#20000\[0-2\]**\[0\]**pricetable2;#30000\[0-2\]**\[0\]**pricetable3 | Este segmento define la cantidad seleccionada por defecto para cada SKU.  |
 | \[0-3\]#10000\[1-2\]\[1\]**pricetable1**;#20000\[0-2\]\[0\]**pricetable2**;#30000\[0-2\]\[0\]**pricetable3** | El último segmento indica la tabla de precios de cada ítem.                    |
 
-![assembly-option-exemplo-ES](//images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/3f3dbae528ee506cf1eddf109168bf1a/image.png)
+![assembly-option-exemplo-ES](https://images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/3f3dbae528ee506cf1eddf109168bf1a/image.png)
 
 #### Configuración del anexo
 
diff --git a/docs/tutorials/es/associating-a-template-with-a-layout.md b/docs/tutorials/es/associating-a-template-with-a-layout.md
index 505d89abd..a04378485 100644
--- a/docs/tutorials/es/associating-a-template-with-a-layout.md
+++ b/docs/tutorials/es/associating-a-template-with-a-layout.md
@@ -30,4 +30,4 @@ Esta asociación se realiza en la configuración de las propiedades del layout.
 5. Haga clic en el menú desplegable **Template**. Ahí se listarán los templates configurados en HTML Templates.
 6. Seleccione el template que desea asociar a este layout.
 7. Digite `yes` para confirmar el cambio (este paso es necesario porque se trata de un cambio crítico para el sitio web, ya que el front-end de la página será reemplazado). 
-![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tutorials/es/audit.md b/docs/tutorials/es/audit.md
index 2a9bc689e..c635d9bb8 100644
--- a/docs/tutorials/es/audit.md
+++ b/docs/tutorials/es/audit.md
@@ -26,7 +26,7 @@ Para acceder a la página de Audit en el Admin VTEX, ve a **Apps > Apps instalad
   <p>Para visualizar los eventos de Audit, debe tener un <a href="https://help.vtex.com/es/tutorial/perfis-de-acceso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acceso</a> asociado al <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <em>Insights Metrics</em>.</p>
 </div>
 
-![audit-ui-es](//images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/7c0a482122fe0605d75492f02b44f20d/audit-ui-es__1_.png)
+![audit-ui-es](https://images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/7c0a482122fe0605d75492f02b44f20d/audit-ui-es__1_.png)
 
 ## Consultar eventos en Audit
 
@@ -54,7 +54,7 @@ Para consultar un evento utilizando los filtros disponibles en Audit, sigue esto
 
     Por ejemplo, la consulta que corresponde a la siguiente imagen devuelve resultados cuyas acciones son _Change Promotion Configuration_ o _Change Coupon Configuration_ y cuyo autor es `email@mail.com`.
 
-    ![filtros-es (1)](//images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/2898f4f9247621f62bbe7fa00a65a313/filtros-es__1_.png)
+    ![filtros-es (1)](https://images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/2898f4f9247621f62bbe7fa00a65a313/filtros-es__1_.png)
 
 7. Haz clic en el botón `Aplicar` para obtener los eventos encontrados.
 
diff --git a/docs/tutorials/es/authentication.md b/docs/tutorials/es/authentication.md
index 095bfcf32..e6b5a4a73 100644
--- a/docs/tutorials/es/authentication.md
+++ b/docs/tutorials/es/authentication.md
@@ -47,7 +47,7 @@ Es necesario configurar el método de autenticación que se ofrecerá en cada co
 
 En la página **Autenticación**, puedes elegir las opciones de inicio de sesión que deseas ofrecer a los clientes de tu tienda y a los usuarios administrativos que tendrán acceso al Admin de tu cuenta.
 
-![Página de autenticación](//images.ctfassets.net/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/ed710d537b491e8a182de685fa8d0d97/Tela_de_Autentica____o_ES.png)
+![Página de autenticación](https://images.ctfassets.net/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/ed710d537b491e8a182de685fa8d0d97/Tela_de_Autentica____o_ES.png)
 
 Sigue estos pasos para activar las opciones de inicio de sesión que desees:
 
diff --git a/docs/tutorials/es/autocomplete.md b/docs/tutorials/es/autocomplete.md
index 3ca439981..430edca19 100644
--- a/docs/tutorials/es/autocomplete.md
+++ b/docs/tutorials/es/autocomplete.md
@@ -54,22 +54,22 @@ Otra ventaja para el administrador de la tienda es el aumento de conversión, qu
 
 En esta sección se muestran los términos más buscados por otros clientes dentro del sitio web.
 
-![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+![PT - Autocomplete termos mais pesquisados](https://images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
 
 ## Últimas búsquedas realizadas
 
 En esta sección se muestran las últimas búsquedas realizadas por el cliente. Así, es posible comenzar la interacción con la búsqueda instantáneamente.
 
-![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+![PT - Autocomplete historico](https://images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
 
 ## Sugerencia de búsquedas
 
 En esta sección se muestran los términos buscados por otros usuarios que se relacionan con la búsqueda realizada en ese momento. Además de términos, también se sugieren categorías relacionadas con la búsqueda.
 
-![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+![PT - Autocomplete sugestao termos](https://images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
 
 ## Sugerencia de productos
 
 En esta sección se muestran los productos que coinciden con la búsqueda realizada en ese momento. Así, al mostrar productos relacionados con su búsqueda durante la escritura, se reducen las interrupciones y se le permite al usuario realizar una compra más dinámica.
 
-![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
+![PT - Autocomplete sugestao de produtos](https://images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tutorials/es/b2b-organization-general-settings.md b/docs/tutorials/es/b2b-organization-general-settings.md
index bea90537d..252f1e095 100644
--- a/docs/tutorials/es/b2b-organization-general-settings.md
+++ b/docs/tutorials/es/b2b-organization-general-settings.md
@@ -29,6 +29,6 @@ En el Admin VTEX, accede a **Apps > Organizaciones y centros de costos B2B > Org
     - **Status:** indica si la organización compradora está activa.
     - **Campos personalizados:** campos adicionales de una organización.
 
-![Configurações gerais organizações - ES](//images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/274406c28db0e41c23bfee501214b547/Configura__es_gerais_organiza__es_-_ES.gif)
+![Configurações gerais organizações - ES](https://images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/274406c28db0e41c23bfee501214b547/Configura__es_gerais_organiza__es_-_ES.gif)
 
 Asegúrate de hacer clic en el botón `Guardar` en la parte superior derecha de la página al realizar cualquier cambio.
diff --git a/docs/tutorials/es/b2b-store-settings.md b/docs/tutorials/es/b2b-store-settings.md
index b0ece9789..3d4bd2c72 100644
--- a/docs/tutorials/es/b2b-store-settings.md
+++ b/docs/tutorials/es/b2b-store-settings.md
@@ -26,7 +26,7 @@ Consulta en esta página los pasos para realizar la configuración general de tu
 - __Use modal to switch company:__ esta opción mejorará la experiencia del usuario al facilitar el mantenimiento de las tiendas. 
 - __Clear cart when switching company or logging in:__ al seleccionar esta opción, si cambias de tienda o inicias sesión en otras cuentas se limpiará el carrito automáticamente.
 ## Términos de pago
-![Tiendas B2B - General Settings + Payment Terms](//images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/2fe3ea82f74231488ec3b9d0d3ce3d57/image1.jpg)
+![Tiendas B2B - General Settings + Payment Terms](https://images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/2fe3ea82f74231488ec3b9d0d3ce3d57/image1.jpg)
 Puedes agregar medios de pago seleccionándolos según las necesidades de tu negocio.   
 Ejemplo: tarjeta de crédito, débito o pagarés. 
 ## Tablas de precios
@@ -35,7 +35,7 @@ Puedes agregar un patrón predeterminado de precios para las tiendas añadidas.
 ## Políticas comerciales
 
 Puedes vincular tu tienda directamente con políticas comerciales y canales de venta.
-![Tiendas B2B -  Políticas comerciais ES](//images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/348fed16a33c05d72acf883315d48c6d/image2.jpg)
+![Tiendas B2B -  Políticas comerciais ES](https://images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/348fed16a33c05d72acf883315d48c6d/image2.jpg)
 
 1. En la lista **Políticas comerciales disponibles**, haz clic en la política comercial que deseas incluir en tu tienda y luego haz clic en `Agregar a política comercial`; esta se mostrará en la lista **Políticas comerciales seleccionadas**.
 2. Haz clic en `Guardar` al finalizar los ajustes.
diff --git a/docs/tutorials/es/b2b-suite-overview.md b/docs/tutorials/es/b2b-suite-overview.md
index fd715c5b9..9300e66a1 100644
--- a/docs/tutorials/es/b2b-suite-overview.md
+++ b/docs/tutorials/es/b2b-suite-overview.md
@@ -47,7 +47,7 @@ Para instalar B2B Suite, sigue los pasos que se indican a continuación:
 
 3. A continuación, haz clic para instalar la aplicación.
 
-![Instalação B2B Suite - ES](//images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/c127f17208e4daeb0746bbb38f1c93b9/Instala__o_B2B_Suite_-_ES.gif)
+![Instalação B2B Suite - ES](https://images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/c127f17208e4daeb0746bbb38f1c93b9/Instala__o_B2B_Suite_-_ES.gif)
 
 ## Conjunto de aplicaciones B2B Suite
 
diff --git a/docs/tutorials/es/bank-reconciliations.md b/docs/tutorials/es/bank-reconciliations.md
index 14f4afc92..e63f6c69e 100644
--- a/docs/tutorials/es/bank-reconciliations.md
+++ b/docs/tutorials/es/bank-reconciliations.md
@@ -36,7 +36,7 @@ Después de recibir el archivo del banco y guardarlo en su máquina, conforme ci
 
 Luego que seleccione el archivo, la plataforma empezará a procesarlo y registrará en histórico cuántos pagos se conciliaron con éxito o error. Los pagos que se concilien con éxito actualizarán los status de los pedidos para Pago Aprobado.
 
-![upload-archivo-ret](//images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7ee6df418b9638eaab055282675b9f6/uploadret_ES.JPG)
+![upload-archivo-ret](https://images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/b7ee6df418b9638eaab055282675b9f6/uploadret_ES.JPG)
 
 ## Visualizar el histórico
 
@@ -48,7 +48,7 @@ De entre los detalles es posible saber el banco al cual el boleto pertenece, el
 2. En **Historial**, haga clic en una de las fechas de las operaciones de conciliación bancaria realizadas.
 3. En **Más detalles**, haga clic en **Conciliado Satisfactoriamente** o **No conciliados** para verificar los detalles de las transacciones realizadas en un banco en particular. 
 
-![historico-conciliacion](//images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/3f2bc9203d264a3b45523211ea06ccb2/historico_conciliacao_ES.jpg)
+![historico-conciliacion](https://images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/3f2bc9203d264a3b45523211ea06ccb2/historico_conciliacao_ES.jpg)
 
 ## Payclub
 
@@ -59,4 +59,4 @@ Aquí es posible hacer el download de los pagos del día que se han hecho a trav
 3. Seleccione la fecha que desee del calendario.
 4. Haga clic en **Descargar archivo**.
 
-![descarga-archivo-conciliación](//images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/6c23d0bf478fdbf20d1176271a29840e/Download_Concilia____o_ES.JPG)
+![descarga-archivo-conciliación](https://images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/6c23d0bf478fdbf20d1176271a29840e/Download_Concilia____o_ES.JPG)
diff --git a/docs/tutorials/es/banners.md b/docs/tutorials/es/banners.md
index 85bcb83b1..1b86a443b 100644
--- a/docs/tutorials/es/banners.md
+++ b/docs/tutorials/es/banners.md
@@ -34,7 +34,7 @@ En VTEX Admin, la página **Storefront** > **Banners** muestra la lista completa
 * [Editar banner](#editar-banner)
 * [Eliminar banner](#eliminar-banner) 
 
-![banners-intro-es](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
+![banners-intro-es](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/eab33921ebea3c1b09cf74f57f0701aa/image.png)
 
 La página contiene la siguiente información:
 
diff --git a/docs/tutorials/es/beta-price-configuration.md b/docs/tutorials/es/beta-price-configuration.md
index 55a96bf88..c61b9b402 100644
--- a/docs/tutorials/es/beta-price-configuration.md
+++ b/docs/tutorials/es/beta-price-configuration.md
@@ -72,11 +72,11 @@ Para crear una nueva regla, siga los pasos a continuación:
 
   b. **Activar en condiciones específicas:** la tabla de precios se activará según las condiciones configuradas en la regla. Vea las alternativas de configuración en las siguientes imágenes: 
 
-  ![config-preco-ES](//images.ctfassets.net/alneenqid6w5/yNbbBH6crnGlgSflYJOuI/443a122a3b4909c114898816ae27e9b8/config-preco-ES.png)
+  ![config-preco-ES](https://images.ctfassets.net/alneenqid6w5/yNbbBH6crnGlgSflYJOuI/443a122a3b4909c114898816ae27e9b8/config-preco-ES.png)
 
-  ![config-preco2-ES](//images.ctfassets.net/alneenqid6w5/4TUUMNundZb1RjgBDKHNUn/4b279c50a93f6911b705e83b3970f2c2/config-preco2-ES.png)
+  ![config-preco2-ES](https://images.ctfassets.net/alneenqid6w5/4TUUMNundZb1RjgBDKHNUn/4b279c50a93f6911b705e83b3970f2c2/config-preco2-ES.png)
 
-  ![config-preco3-ES](//images.ctfassets.net/alneenqid6w5/1MUMEqGPxoW6XBr6Yfp9L1/52b2a01a72eef3cb0caa6881dff491ac/config-preco3-ES.png)
+  ![config-preco3-ES](https://images.ctfassets.net/alneenqid6w5/1MUMEqGPxoW6XBr6Yfp9L1/52b2a01a72eef3cb0caa6881dff491ac/config-preco3-ES.png)
 
 7. Haga clic en **Confirmar**. 
 
diff --git a/docs/tutorials/es/billing-module-overview.md b/docs/tutorials/es/billing-module-overview.md
index 0db8b4846..5d6426a91 100644
--- a/docs/tutorials/es/billing-module-overview.md
+++ b/docs/tutorials/es/billing-module-overview.md
@@ -23,7 +23,7 @@ Para acceder a esta sección, haz clic en tu **avatar de perfil**, que se puede
 Solo los usuarios con perfil de acceso <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> o con recursos de <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> vinculadas a su Perfil de acceso tendrán acceso a esta sección del VTEX Admin.         
 </div>            
 
-![Admin v4 Faturas menu ES](//images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/369081b189fa73fa6f87aa849e21ec58/Admin_v4_Faturas_menu_ES.jpg)
+![Admin v4 Faturas menu ES](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/369081b189fa73fa6f87aa849e21ec58/Admin_v4_Faturas_menu_ES.jpg)
 
 A continuación encontrarás más detalles sobre las diferentes secciones y páginas de esta funcionalidad.
 
diff --git a/docs/tutorials/es/brands.md b/docs/tutorials/es/brands.md
index b93e4e9a2..d6b7efadc 100644
--- a/docs/tutorials/es/brands.md
+++ b/docs/tutorials/es/brands.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 La página **Marcas** te permite ver, gestionar y registrar marcas en Seller Portal. Puedes acceder a la página en el Admin VTEX en **Catálogo** > **Marcas**.
 
-![brands-es](//images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/b663576009bbc4719d4091ba8ef46b5d/brands-es.PNG)
+![brands-es](https://images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/b663576009bbc4719d4091ba8ef46b5d/brands-es.PNG)
 
 ## Crear marcas 
 Para registrar una nueva marca, haz clic en el botón `Crear marca`. Mira a continuación cómo rellenar los campos en la pantalla __Nueva marca__.
diff --git a/docs/tutorials/es/breadcrumb-control.md b/docs/tutorials/es/breadcrumb-control.md
index c51350385..12331067e 100644
--- a/docs/tutorials/es/breadcrumb-control.md
+++ b/docs/tutorials/es/breadcrumb-control.md
@@ -19,7 +19,7 @@ Breadbrumbs mejoran la experiencia de navegación en la tienda por llevar a los
 
 En VTEX, el control `<vtex.cmc:breadCrumb/>` es responsable de renderizar breadcrumbs como el del ejemplo abajo.
 
-![breadcrumb1](//images.contentful.com/alneenqid6w5/4UnYdunXh6MI28k8sS0w8Y/9883ba3a0d5f9f5826313832f9c5a2d0/breadcrumb1.png)
+![breadcrumb1](https://images.contentful.com/alneenqid6w5/4UnYdunXh6MI28k8sS0w8Y/9883ba3a0d5f9f5826313832f9c5a2d0/breadcrumb1.png)
 
 Si, como en este ejemplo, el usuario accede directamente a la página de un producto de la categoría *Camisetas*, el breadcrumb exhibido en la página del producto le dará la información de que el usuario se encuentra en esa categoría (*Camisetas*), que a su vez está por debajo del departamento *Moda masculina*.
 
@@ -42,4 +42,4 @@ A continuación se muestra un ejemplo del código HTML renderizado por el contro
 
 El código anterior renderiza el siguiente breadcrumb en el sitio:
 
-![breadcrumb2](//images.contentful.com/alneenqid6w5/1PxrLYlhNaaUYYoi6oOCe6/06d276039e7e73a39fa15061befffd38/breadcrumb2.png)
+![breadcrumb2](https://images.contentful.com/alneenqid6w5/1PxrLYlhNaaUYYoi6oOCe6/06d276039e7e73a39fa15061befffd38/breadcrumb2.png)
diff --git a/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md b/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md
index bd712adee..cc05ca15d 100644
--- a/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md
+++ b/docs/tutorials/es/bringing-app-content-into-the-admin-panel.md
@@ -25,13 +25,13 @@ Navegue hasta el proyecto y abra el archivo `pages.json`.
 
 Añadimos el `"admin/"` al nombre de la página, así como a la ruta. Es importante también añadir `"admin/"` al principio del nombre de todas las extensiones que se utilizarán. Su `pages.json` debe quedar así:
 
-![2 pages](//images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
+![2 pages](https://images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
 
 ## Actualizar las dependencias para usar vtex.admin
 
 Ahora necesitamos actualizar el archivo manifest.json para listar el `vtex.admin` como dependencia. Recuerde que en VTEX IO siempre especificamos la versión que se utilizará. El manifest.json debe quedar así:
 
-![3 manifest](//images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
+![3 manifest](https://images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
 
 ## Los toques finales
 
@@ -43,5 +43,5 @@ Utilizaremos el `componentDidMount()` para comprobar que la string se ha renderi
 
 Sólo hay que navegar a `index.js` y añadir el `componentDidMount()` por encima de nuestro render. Se va a quedar así:
 
-![4 final touches](//images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
-![5 completo](//images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
+![4 final touches](https://images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
+![5 completo](https://images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
diff --git a/docs/tutorials/es/buy-one-get-one.md b/docs/tutorials/es/buy-one-get-one.md
index f2edf97a1..240075ca4 100644
--- a/docs/tutorials/es/buy-one-get-one.md
+++ b/docs/tutorials/es/buy-one-get-one.md
@@ -54,7 +54,7 @@ En esta sección se proporciona información detallada sobre los datos generales
 - **Información adicional (opcional):** permite incluir en la promoción información adicional que incluye un nombre y un valor.
 - **Promoción resaltada:** al elegir esta opción, se crea una tag que destaca el nombre de la promoción. Se implementa en la vitrina y en la página de producto, siempre y cuando se utilice el control de visualización de promociones correcto en la plantilla. `<vtex.cmc:discountHightLight>`.
 
-![Resumen de la promoción](//images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/e10d90b18e8ce27fda6345f72b86a802/Resumen_de_la_promocion.png)
+![Resumen de la promoción](https://images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/e10d90b18e8ce27fda6345f72b86a802/Resumen_de_la_promocion.png)
 
 ## Restringir esta promoción a los productos de los sellers
 
@@ -69,7 +69,7 @@ Para que la promoción sea válida para todos los sellers, deja la selección si
   <p>No es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:</p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.</ol>
 </div>
 
-![Restringir esta promoción a los productos de los sellers](//images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/2b00df355cb9670e4a5b799e5c9482e7/Restringir_esta_promoci_n_a_los_productos_de_los_sellers.png)
+![Restringir esta promoción a los productos de los sellers](https://images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/2b00df355cb9670e4a5b799e5c9482e7/Restringir_esta_promoci_n_a_los_productos_de_los_sellers.png)
 
 ## Política comercial
 Esta sección establece las políticas comerciales válidas para la promoción. Puedes incluir o excluir políticas comerciales del descuento.
@@ -81,7 +81,7 @@ Esta sección establece las políticas comerciales válidas para la promoción.
 
 Para que la promoción sea válida para todas las políticas comerciales, deja la selección sin marcar.
 
-![Política comercial-ES](//images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/3580c9712e545dbd89b07b473e7409fb/Politica_comercial-ES.png)
+![Política comercial-ES](https://images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/3580c9712e545dbd89b07b473e7409fb/Politica_comercial-ES.png)
 
 # 2. Compra uno y lleva uno gratis
 
@@ -99,7 +99,7 @@ En esta sección se definen las colecciones, SKU y cantidad mínima que deben re
  <p>Se puede crear una promoción Compra uno y lleva uno gratis con un máximo de 100 SKU diferentes al mismo tiempo.<p>
 </div>
 
-![Compra uno y lleva uno gratis](//images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c37f45ddde8ac8ddab99cae1500a951d/Compra_uno_y_lleva_uno_gratis.png)
+![Compra uno y lleva uno gratis](https://images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c37f45ddde8ac8ddab99cae1500a951d/Compra_uno_y_lleva_uno_gratis.png)
 
 # 3. Condiciones de la promoción
 
@@ -112,7 +112,7 @@ En esta sección se proporciona información detallada sobre las condiciones que
 - **Utm_source:** el descuento se concederá si la navegación utiliza un parámetro utm_source con el valor registrado.
 - **Utm_campaign:** el descuento se concederá si la navegación utiliza un parámetro utm_campaign con el valor registrado.
 
-![Cuáles son las condiciones para que la promoción sea válida?](//images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/feb16501d81f3fc85591b837bf06b42d/Cu_les_son_las_condiciones_para_que_la_promoci_n_sea_v_lida.png)
+![Cuáles son las condiciones para que la promoción sea válida?](https://images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/feb16501d81f3fc85591b837bf06b42d/Cu_les_son_las_condiciones_para_que_la_promoci_n_sea_v_lida.png)
 
 # 4. Restricciones y limitaciones de uso
 
@@ -123,4 +123,4 @@ En esta sección se proporciona información importante sobre las condiciones y
 - **Solo para los mismos ítems:** si se activa esta opción, la promoción solo se aplica si se alcanza la cantidad mínima de ítems (previamente registrados) con el mismo SKU en el carrito. Si la opción está desactivada, la promoción se aplicará incluso cuando se agregue la cantidad mínima de ítems en el carrito, independientemente de si los SKU son diferentes o iguales.
 - **Aplicar con otras promociones:** permite aplicar esta promoción en el carrito simultáneamente con otras promociones que ofrezcan el mismo tipo de descuento.
 
-![Restricciones y limitaciones de uso](//images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/9f8d369b64e79bc40aad64c2464112c8/Restricciones_y_limitaciones_de_uso.png)
+![Restricciones y limitaciones de uso](https://images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/9f8d369b64e79bc40aad64c2464112c8/Restricciones_y_limitaciones_de_uso.png)
diff --git a/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md b/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
index f5b91bf54..a02cb1252 100644
--- a/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
+++ b/docs/tutorials/es/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
@@ -24,4 +24,4 @@ Para ello, siga los pasos abajo:
 
 Para los sellers White Label, existe un límite de 50 unidades con el mismo SKU en el carrito. Se puede ajustar este límite a través de una solicitud al equipo de [soporte](https://help.vtex.com/es/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe).
 
-![Carrinho Max ES](//images.ctfassets.net/alneenqid6w5/E8mj8DGIKcWKMAACse4CM/eee01547a76ce8f486a0b315e139d478/Carrinho_Max_ES.png)
+![Carrinho Max ES](https://images.ctfassets.net/alneenqid6w5/E8mj8DGIKcWKMAACse4CM/eee01547a76ce8f486a0b315e139d478/Carrinho_Max_ES.png)
diff --git a/docs/tutorials/es/campaign-audiences-list.md b/docs/tutorials/es/campaign-audiences-list.md
index 0ccb615c7..074c5a63f 100644
--- a/docs/tutorials/es/campaign-audiences-list.md
+++ b/docs/tutorials/es/campaign-audiences-list.md
@@ -17,7 +17,7 @@ subcategory: 2cI57eZ3ZiWSeaQs26Gwys
 
 Tal como se muestra a continuación, podrás ver la lista de audiencias de campañas registradas en tu tienda desde la página *Promociones > Audiencia de campañas* del Admin VTEX.
 
-![lista-audiencias-campanha-es](//images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/e4d2a074233382a8563b46391f15f446/lista-audiencias-campanha-es.png)
+![lista-audiencias-campanha-es](https://images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/e4d2a074233382a8563b46391f15f446/lista-audiencias-campanha-es.png)
 
 Desde esta página, puedes realizar las acciones a continuación:
 
@@ -50,7 +50,7 @@ Las audiencias de campaña se presentan en _tarjetas_ que incluyen la informaci
 
 Para ver las audiencias de campaña [archivadas](#archivar-audiencias-de-campana), dirígete a la opción **Presentar** y haz clic en **Archivados**, tal como se muestra a continuación:
 
-![toggle-audiencias-campanha-arquivadas-es](//images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/8c1426c228b3415d28557c63bb7efc27/toggle-audiencias-campanha-arquivadas-es.png)
+![toggle-audiencias-campanha-arquivadas-es](https://images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/8c1426c228b3415d28557c63bb7efc27/toggle-audiencias-campanha-arquivadas-es.png)
 
 Para volver a ver las audiencias de campaña no archivadas, haz clic en **No archivados**.
 
diff --git a/docs/tutorials/es/campaign-audiences.md b/docs/tutorials/es/campaign-audiences.md
index 6b1a69b23..459f5724b 100644
--- a/docs/tutorials/es/campaign-audiences.md
+++ b/docs/tutorials/es/campaign-audiences.md
@@ -27,7 +27,7 @@ Ejemplo: en el segmento de moda, al registrar una audiencia de campaña, puedes
 
 El público objetivo segmenta los usuarios y las condiciones elegibles de la audiencia de campaña. Si la audiencia de la campaña está activa, al cumplir todos los criterios definidos en el público objetivo, se activarán las promociones asociadas a la audiencia de la campaña.
 
-![campanha-es](//images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/dc2f1ab65b1a442f47a5542bccc7786e/campanha-es.png)
+![campanha-es](https://images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/dc2f1ab65b1a442f47a5542bccc7786e/campanha-es.png)
 
 Cuando la campaña está activada, es elegible para el contexto de compra y se cumplen todas sus restricciones, no significa necesariamente que se aplicarán todas las promociones de audiencia de la campaña asociadas a ella. Para ello, también deben cumplirse las restricciones definidas en [promoción de campaña](https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume).
 
diff --git a/docs/tutorials/es/campaign-promotion.md b/docs/tutorials/es/campaign-promotion.md
index 58bf3054d..2591f53b2 100644
--- a/docs/tutorials/es/campaign-promotion.md
+++ b/docs/tutorials/es/campaign-promotion.md
@@ -121,7 +121,7 @@ Para que la promoción sea válida para todas las políticas comerciales, deje l
 
 En esta sección, debe elegir si la promoción se aplicará a todos los productos registrados en su tienda o solo a productos específicos, como se ilustra a continuación.
 
-![promocoes-restricao-es](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/9219ee59e0e23d8a881a2ea678ff0249/promocoes-restricao-es.PNG)
+![promocoes-restricao-es](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/9219ee59e0e23d8a881a2ea678ff0249/promocoes-restricao-es.PNG)
 
 Si desea aplicar la promoción a todo su catálogo, seleccione la opción **Aplicar a todos los productos<b>**</b>.
 
@@ -131,7 +131,7 @@ Puede incluir o excluir **categorías**, **marcas**, **colecciones** y **product
 
 Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en la promoción todos los productos de la categoría **Vestido** cuya marca es **Farm**, con la excepción del producto **Vestido Rosas**.
 
-![exemplo-es](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/4b294969b056e682bd853a323e213b33/exemplo-es.PNG)
+![exemplo-es](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/4b294969b056e682bd853a323e213b33/exemplo-es.PNG)
 
 En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
 
diff --git a/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md
index bcc018810..02284fdac 100644
--- a/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/es/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -20,7 +20,7 @@ El módulo *Inventario y envío* es donde usted realiza toda la gestión de la l
 Algunas secciones de la página de registro **Política de envío** cambiaron, para darle una mayor flexibilidad cuando configure su estrategia de entrega. En la anterior versión, había una sección denominada *Configuración de tiempo*, en la que era posible seleccionar *Horario de operación*, *Horario de corte* o *Entrega agendada* para cada transportadora. 
 
 __Anterior versión__
-![ES Configurações de tempo versão antiga](//images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/6afb6a15f8cc04c2167bc2a33ccf510d/ES_Configura____es_de_tempo_vers__o_antiga.jpg)
+![ES Configurações de tempo versão antiga](https://images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/6afb6a15f8cc04c2167bc2a33ccf510d/ES_Configura____es_de_tempo_vers__o_antiga.jpg)
 
 En la nueva versión:  
 - Cambiamos los nombres de las opciones para que sean más fáciles de entender.   
@@ -28,7 +28,7 @@ En la nueva versión:
 - Añadimos la opción Configurar capacidad de entrega, para que la entrega programada se base en la realidad de su operación.   
 
 __Versión Beta__
-![ES Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/de667ba6adbdcd826ed90da21a6aa385/ES_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![ES Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/de667ba6adbdcd826ed90da21a6aa385/ES_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 ## Horario de recolección
 
@@ -45,7 +45,7 @@ Al igual que en la versión anterior, no es posible configurar las opciones de *
 Esta funcionalidad se denominaba *Entrega agendada* en la anterior versión y ahora se denomina *Entrega programada*. Además, antes solo era posible optar por esta funcionalidad omitiendo la configuración de *Horario de operación*. Sin embargo, ahora es posible configurar *Entrega programada* junto con la opción *Horario de atención* para que su cliente elija este método de entrega durante el checkout del pedido. Vea los campos que se deben completar para configurar esta opción.
 
 **Versión Beta**
-![ES entrega agendada](//images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/62dcaef0097e846366826ae301a35714/ES_entrega_agendada.jpg)
+![ES entrega agendada](https://images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/62dcaef0097e846366826ae301a35714/ES_entrega_agendada.jpg)
 
 - **Tiempo máximo de entrega**:  este campo se debe completar de acuerdo con su operación logística. Defina cuál es el mayor periodo de tiempo que la transportadora emplea para realizar una entrega programada, desde la confirmación del pedido hasta la confirmación de la entrega.
 - **Configurar capacidad de entrega**: dependiendo de las características de su operación y de cómo la transportadora envía sus productos, puede tener más sentido definir la capacidad de entrega en número de ítems o en número de pedidos. Por ejemplo, si su tienda es del segmento de supermercados y el medio de transporte para la entrega programada es una motocicleta, hay un número límite de ítems que ese vehículo puede almacenar y por eso recomendamos que seleccione «ítems» como unidad. Por otro lado, si su operación tiene pocos ítems por pedido, tendrá más sentido definir «pedidos» como unidad, por ejemplo.
diff --git a/docs/tutorials/es/catalog-overview.md b/docs/tutorials/es/catalog-overview.md
index a920d2697..21b0f95b8 100644
--- a/docs/tutorials/es/catalog-overview.md
+++ b/docs/tutorials/es/catalog-overview.md
@@ -15,7 +15,7 @@ legacySlug: catalogo-vision-general
 subcategory: 
 ---
 
-![Catalogo overview (tapa)](//images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/acb839745dcafabbe9cfa2dfbd529484/image1.jpg)
+![Catalogo overview (tapa)](https://images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/acb839745dcafabbe9cfa2dfbd529484/image1.jpg)
 El catálogo es el módulo de administración de tu tienda que te permite configurar las funcionalidades relacionadas con los productos de tu ecommerce. Para que tu cliente pueda ver los productos en el sitio web, debes registrarlos en este módulo. 
 
 En este artículo, encontrarás una visión general de los ítems del catálogo y su funcionalidad.
@@ -25,7 +25,7 @@ La categoría es el segundo nivel de categorización de tu tienda, debajo del ni
 
 El módulo **Categorías** te permite ver y gestionar el árbol de categorías registradas en tu tienda, como se muestra en el ejemplo a continuación.
 
-![Estructura del catalogo](//images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/6f11799fa0f016fa0429a2e49e757f27/image5.png)
+![Estructura del catalogo](https://images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/6f11799fa0f016fa0429a2e49e757f27/image5.png)
 
 Puedes registrar una categoría siguiendo el tutorial [Registrar una categoría](https://help.vtex.com/es/tutorial/registrando-categoria--tutorials_206). Si deseas gestionar o desactivar una categoría, sigue los pasos del tutorial [Desactivar y reorganizar categorías](https://help.vtex.com/es/tutorial/desactivando-y-reorganizando-categorias--tutorials_264).
 
diff --git a/docs/tutorials/es/categories.md b/docs/tutorials/es/categories.md
index 06467c9fc..03a006220 100644
--- a/docs/tutorials/es/categories.md
+++ b/docs/tutorials/es/categories.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 La página **Categorías** te permite ver y gestionar el árbol de categorías registradas en Seller Portal. Puedes acceder a la página en VTEX Admin en **Productos** > **Categorías**.
 
-![categorias-es](//images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/efff0f39ab9b9e36ed69ec8f9cf928ec/categorias-es.PNG)
+![categorias-es](https://images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/efff0f39ab9b9e36ed69ec8f9cf928ec/categorias-es.PNG)
 
 En el árbol de categorías, puedes realizar diversas acciones:
 
@@ -51,7 +51,7 @@ Para encontrar una categoría, debes escribir su nombre en la barra de búsqueda
 ## Navegar por el árbol de categorías
 La página de categorías muestra los niveles más externos de las categorías. Haz clic en el ícono <i class="fas fa-angle-right"></i> para acceder a las subcategorías, como se muestra a continuación.
 
-![arvore-categoria-ES](//images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/d28b34e0bc719c604dcfbbb3f28a2956/arvore-categoria-ES.gif)
+![arvore-categoria-ES](https://images.ctfassets.net/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/d28b34e0bc719c604dcfbbb3f28a2956/arvore-categoria-ES.gif)
 
 Para ver la información de registro de una categoría, haz clic en su nombre.
 
diff --git a/docs/tutorials/es/category-registration-fields.md b/docs/tutorials/es/category-registration-fields.md
index 20a5b9f55..6cc172dd3 100644
--- a/docs/tutorials/es/category-registration-fields.md
+++ b/docs/tutorials/es/category-registration-fields.md
@@ -43,9 +43,9 @@ Para entender mejor el significado de cada campo del registro de categoría, vea
 - __Score (utilizado para ordenación de búsqueda):__ valor utilizado para definir la prioridad en la página de resultados de búsqueda. Para entender más sobre Score, accede a nuestro artículo [¿Cómo funciona el campo Score?](https://help.vtex.com/es/tutorial/como-funciona-el-campo-score--1BUZC0mBYEEIUgeQYAKcae).
 - __Modo de visualización de los productos:__ define cómo se mostrarán los SKUs en la página del producto. Vea abajo las opciones de relleno de este campo:
   - __Lista de SKUs:__ todos los SKUs del departamento o categoría en cuestión se mostrarán en el formato de lista. Cada uno con su botón de Comprar al lado.
-  ![1Lista.es](//images.ctfassets.net/alneenqid6w5/37tngqcxF8hJTzWqxUG8jA/1c5f90c33525bfaf34b6ab729a9d02b5/Lista.es.png)
+  ![1Lista.es](https://images.ctfassets.net/alneenqid6w5/37tngqcxF8hJTzWqxUG8jA/1c5f90c33525bfaf34b6ab729a9d02b5/Lista.es.png)
   - __Ingeles de selección de radio (radioBox):__ todos los SKUs de ese departamento/categoría necesitarán ser seleccionados a través de selección de radio.
-  ![RadioBox.es](//images.ctfassets.net/alneenqid6w5/F33F8dSkcV2SePNONlGb2/d0029323d5f7f07f2d1c53fb5d784ccc/RadioBox.es.png)
+  ![RadioBox.es](https://images.ctfassets.net/alneenqid6w5/F33F8dSkcV2SePNONlGb2/d0029323d5f7f07f2d1c53fb5d784ccc/RadioBox.es.png)
   - __Sigue la definición de la especificación SKU:__ todos los SKUs de ese departamento/categoría serán seleccionados de acuerdo con la pestaña Especificación, en el formulario de registro de SKU. Las opciones preconfiguradas son Combo o Radio.
-  ![Campos.es](//images.ctfassets.net/alneenqid6w5/17S7QKJpvr31r3LGRRCSSn/c3350ddfca051df6be8592fad107410f/Campos.es.png)
+  ![Campos.es](https://images.ctfassets.net/alneenqid6w5/17S7QKJpvr31r3LGRRCSSn/c3350ddfca051df6be8592fad107410f/Campos.es.png)
 
diff --git a/docs/tutorials/es/category-variations-and-attributes-mapping.md b/docs/tutorials/es/category-variations-and-attributes-mapping.md
index 7f5d2faf8..2d21eaab3 100644
--- a/docs/tutorials/es/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/es/category-variations-and-attributes-mapping.md
@@ -21,7 +21,7 @@ A través de esta, será posible categorizar correctamente sus productos en Merc
 
 La asignación sólo se realizará una vez para cada categoría. De esta forma, aun habiendo hecho un mapeo, cuando nuevos productos sean creados, ellos serán integrados directamente en la categoría correcta y con sus respectivas variaciones y atributos.
 
-- [Descargue aquí](//assets.ctfassets.net/alneenqid6w5/qyDp7OSL5YAGaGKagWiK0/07900f41a952a460185e18f9db190eb1/Planilha_de_Mapeamento_do_Mercado_Livre.xlsx) la __Planilla de Mapeo del Mercado Libre__ en el formato `.xlsx`.
+- [Descargue aquí](https://assets.ctfassets.net/alneenqid6w5/qyDp7OSL5YAGaGKagWiK0/07900f41a952a460185e18f9db190eb1/Planilha_de_Mapeamento_do_Mercado_Livre.xlsx) la __Planilla de Mapeo del Mercado Libre__ en el formato `.xlsx`.
 
 La misma planilla se utilizará en las tres macroetapas siguientes (categorización, variaciones y atributos). Siga el paso a paso llenando los campos de la hoja de asignación de acuerdo con las indicaciones siguientes.
 
@@ -62,7 +62,7 @@ En Mercado Libre existen dos tipos de variación, las __obligatorias__ y las __p
 
 - Variaciones obligatorias
 	
-Si su producto es un `calzado`, `ropa`, o `electrodoméstico`, será necesario asignar las variaciones obligatorias. Su nombre debe estar exactamente de acuerdo con los valores aceptados por marketplace. [Descargue aquí](//assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/28d9a8e7ce08b03d243b43bb6b759c5d/Planilha_de_Atributos_do_Mercado_Livre.xlsx) la __Planilla de Variaciones de Mercado Libre__ para verificar los valores aceptados de acuerdo con cada tipo de producto.
+Si su producto es un `calzado`, `ropa`, o `electrodoméstico`, será necesario asignar las variaciones obligatorias. Su nombre debe estar exactamente de acuerdo con los valores aceptados por marketplace. [Descargue aquí](https://assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/28d9a8e7ce08b03d243b43bb6b759c5d/Planilha_de_Atributos_do_Mercado_Livre.xlsx) la __Planilla de Variaciones de Mercado Libre__ para verificar los valores aceptados de acuerdo con cada tipo de producto.
   
 - Variaciones personalizadas
 
diff --git a/docs/tutorials/es/change-a-placeholder-title.md b/docs/tutorials/es/change-a-placeholder-title.md
index 6eb14a2d2..778b5e23d 100644
--- a/docs/tutorials/es/change-a-placeholder-title.md
+++ b/docs/tutorials/es/change-a-placeholder-title.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 El título de un placeholder es el que aparece en la esquina derecha del objeto, como indica la imagen abajo.
 
-![cms-placeholder es](//images.ctfassets.net/alneenqid6w5/UWClcSxWUKaG4qwSiSekQ/3c19965a673d3d5904b0098cad0da60a/placeholder_destaque_es.png)
+![cms-placeholder es](https://images.ctfassets.net/alneenqid6w5/UWClcSxWUKaG4qwSiSekQ/3c19965a673d3d5904b0098cad0da60a/placeholder_destaque_es.png)
 
 El texto que se inserta en ese campo es el que se mostrará como título del placeholder en el sitio de la tienda.
 
@@ -26,7 +26,7 @@ Para cambiar el título de un placeholder, basta con seguir los pasos abajo:
 1. Haga clic en el título.
 
 2. Introduzca el nuevo título.
-![placeholder-change-name es](//images.ctfassets.net/alneenqid6w5/6gMl2GzVlY8gwyWQ4SA0me/96ede6e52392d55358cf786e932e899f/change_name_es.png)
+![placeholder-change-name es](https://images.ctfassets.net/alneenqid6w5/6gMl2GzVlY8gwyWQ4SA0me/96ede6e52392d55358cf786e932e899f/change_name_es.png)
 
 3. Haga clic en __Rename__.
 
diff --git a/docs/tutorials/es/change-seller.md b/docs/tutorials/es/change-seller.md
index fcc455301..d49c13ef8 100644
--- a/docs/tutorials/es/change-seller.md
+++ b/docs/tutorials/es/change-seller.md
@@ -26,13 +26,13 @@ Un cambio de <i>seller</i> puede ocurrir en dos situaciones:
 - <i>Seller</i> cancela un pedido.
 - <i>Marketplace</i> decide cambiar el <i>seller</i>.
 
-![seller_cancela_pedido_ES](//images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/9a1899752e5df76040cbcbdb12aaf456/seller_cancela_pedido_ES.png)
+![seller_cancela_pedido_ES](https://images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/9a1899752e5df76040cbcbdb12aaf456/seller_cancela_pedido_ES.png)
 
 Puede [configurar el periodo para cambiar de seller de 0 a 30 días](https://developers.vtex.com/vtex-rest-api/reference/updatewindowtochangeseller), por defecto, la ventana de cambio es de dos días. Al configurar la ventana a 0 días, no hay un período efectivo para el cambio de _sellers_ y la _feature_, aunque configurada, no funciona en la práctica, lo que provoca que el pedido proceda a la cancelación.
 
 Cuando el <i>seller</i> le notifica la cancelación, el <i>marketplace</i> puede configurar el número de días para actuar y decidir entre cancelar la compra o cambiar de <i> seller.</i> Tenga en cuenta que si opta por el cambio, el <i>marketplace</i> es el responsable de comunicarlo al cliente final.
 
-![mkt_cancela_seller_ES](//images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/28c420f005191ccba061053f44833275/mkt_cancela_seller_ES.png)
+![mkt_cancela_seller_ES](https://images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/28c420f005191ccba061053f44833275/mkt_cancela_seller_ES.png)
 
 ## Limitaciones
 
diff --git a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
index 90ff72846..23bdf3150 100644
--- a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -33,7 +33,7 @@ Después de [habilitar la funcionalidad](https://developers.vtex.com/vtex-rest-a
 3. Cambie el precio al valor deseado y presione `ENTER`.
 4. Haga clic en `Cerrar pedido`.
 
-![manualprice](//images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/a2c63f9fd22cbc180cb95ca790ab7b61/manualprice.gif)
+![manualprice](https://images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/a2c63f9fd22cbc180cb95ca790ab7b61/manualprice.gif)
 
 Además de la configuración en la pantalla de Checkout , el precio de un producto también se puede modificar a través de la API [Change Price](https://developers.vtex.com/vtex-rest-api/reference/pricechange), obtenga más información en [Setting the price of an item manually](https://developers.vtex.com/vtex-rest-api/docs/enable-the-manual-price#setting-the-price-of-an-item-manually).
 
diff --git a/docs/tutorials/es/changing-a-pages-body-class.md b/docs/tutorials/es/changing-a-pages-body-class.md
index 69d5b578c..a270331a6 100644
--- a/docs/tutorials/es/changing-a-pages-body-class.md
+++ b/docs/tutorials/es/changing-a-pages-body-class.md
@@ -23,13 +23,13 @@ Los templates utilizados por los layouts de la tienda, de forma predeterminada,
 
 Vea, por ejemplo, el código del template Department.
 
-![changeBodyClass1](//images.contentful.com/alneenqid6w5/pbQCDMUz3qO0q4SuwYaq4/7ebd6ca8a0af6cbce899535b83cd719a/changeBodyClass1.jpg)
+![changeBodyClass1](https://images.contentful.com/alneenqid6w5/pbQCDMUz3qO0q4SuwYaq4/7ebd6ca8a0af6cbce899535b83cd719a/changeBodyClass1.jpg)
 
 Tiene un `id`, pero no una `class`.
 
 Sin embargo, al cargar un layout que use ese template, vemos que la clase `departamento` fue agregada al body de la página.
 
-![changeBodyClass2](//images.contentful.com/alneenqid6w5/132c4r8rtGowUkOYe4YUaM/6b4a3bd0a9fc5f65fe1d950484088ba1/changeBodyClass2.jpg)
+![changeBodyClass2](https://images.contentful.com/alneenqid6w5/132c4r8rtGowUkOYe4YUaM/6b4a3bd0a9fc5f65fe1d950484088ba1/changeBodyClass2.jpg)
 
 Es decir, el sistema inserta automáticamente esta clase.
 
diff --git a/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
index 8846b1286..924fbfc0a 100644
--- a/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
@@ -51,9 +51,9 @@ Es decir, estoy usando las variables `preposicaonomeloja2` y `nomeloja`.
 Al utilizar variables para crear un texto, reemplace el símbolo <code>#</code> por <code>@</code>. Es decir, <b>#variable#</b> se convierte <b>@variable@</b>.
 </div>
 
-![textos-importantes es](//images.ctfassets.net/alneenqid6w5/3Trct11oXCGe0EigiUA4g0/f701207101145a1222f5e45cb61d4073/textos_importantes_es.png)
+![textos-importantes es](https://images.ctfassets.net/alneenqid6w5/3Trct11oXCGe0EigiUA4g0/f701207101145a1222f5e45cb61d4073/textos_importantes_es.png)
 
-![exemplo-textos-da-loja es](//images.ctfassets.net/alneenqid6w5/vKgZfyW6dieKAqUy242OC/f57ed59d90b2db3ae86d77b62dea3a69/3_es.png)
+![exemplo-textos-da-loja es](https://images.ctfassets.net/alneenqid6w5/vKgZfyW6dieKAqUy242OC/f57ed59d90b2db3ae86d77b62dea3a69/3_es.png)
 
 Como defini que el contenido de la primera variable es "a" y el de la segunda es "VtexArgentina", el texto final renderizado en el sitio será "Bienvenido a VtexArgentina".
 
diff --git a/docs/tutorials/es/changing-the-total-cost-of-the-order.md b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
index 48dbb21fb..8dd951d3d 100644
--- a/docs/tutorials/es/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
@@ -28,13 +28,13 @@ Para hacer el cambio, sigue los pasos a continuación:
 3. Haz clic en el pedido para acceder a la página de **Detalles del pedido**.   
 4. En la página *Detalles del pedido*, ve a la sección **Costo total del pedido**.
 5. Haz clic en `Cambiar el costo final`.  
-![valorfinalES](//images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/625d67dbe3011b8aea8574e247f9a2d4/valorfinalES__1_.png)  
+![valorfinalES](https://images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/625d67dbe3011b8aea8574e247f9a2d4/valorfinalES__1_.png)  
 6. Se abrirá la página **Cambiar el valor**, en la que debes rellenar los siguientes campos obligatorios:  
 7.  Rellena los campos obligatorios:
     * **Valor:** Selecciona Descuento o Aumentar e introduce el valor que deseas modificar.  
     * **Razón**: indica los motivos del cambio.  
 8. En la parte derecha de la página, haz clic en `Enviar`;
-![Alterar valorES](//images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/8488873894611990391d7bb132ab9c04/Alterar_valorES.png)
+![Alterar valorES](https://images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/8488873894611990391d7bb132ab9c04/Alterar_valorES.png)
 
 Los cambios en el pedido se actualizarán en la sección *Ítems a Facturar*, y en el *Historial de Pedidos*. Ten en cuenta que el valor total del pedido también cambiará.
 
diff --git a/docs/tutorials/es/changing-tracking-data.md b/docs/tutorials/es/changing-tracking-data.md
index b0139cb81..838d519e3 100644
--- a/docs/tutorials/es/changing-tracking-data.md
+++ b/docs/tutorials/es/changing-tracking-data.md
@@ -38,4 +38,4 @@ Para cambiar los datos de un pedido manualmente, sigue los pasos a continuación
     * **Seleccionar transportadora: **selecciona la transportadora que realizará la entrega.
 7. Haz clic en `Guardar`.
 
-![FaturaES](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
+![FaturaES](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
diff --git a/docs/tutorials/es/check-order-delivery-details.md b/docs/tutorials/es/check-order-delivery-details.md
index ffe0a4d27..ee84c0a9a 100644
--- a/docs/tutorials/es/check-order-delivery-details.md
+++ b/docs/tutorials/es/check-order-delivery-details.md
@@ -45,6 +45,6 @@ Para ver estos detalles, basta con hacer una [simulación de flete](/es/tutorial
 6. Introduzca el código postal del pedido.
 7. Haga clic en __Simular Flete__.
 
-![simular-frete es](//images.ctfassets.net/alneenqid6w5/4uPm4LFmr6wGSwOMu800kW/e7dbece799e4f3920ef3e82f7ea56220/simular-frete_es.png)
+![simular-frete es](https://images.ctfassets.net/alneenqid6w5/4uPm4LFmr6wGSwOMu800kW/e7dbece799e4f3920ef3e82f7ea56220/simular-frete_es.png)
 
 Para cada transportista considerado en la simulación, usted puede ver los detalles del pedido correspondiente. Para ello, haga clic en __detallar__.
diff --git a/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md b/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md
index 62cf0def8..808c3dfe5 100644
--- a/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md
+++ b/docs/tutorials/es/checking-how-an-order-delivery-deadline-was-calculated.md
@@ -23,7 +23,7 @@ Digamos que usted desea saber cuáles fueron los criterios que la plataforma uti
 
 En primer lugar, vamos a acceder a la página Todos los Pedidos para ver el pedido.
 
-![1](//images.ctfassets.net/alneenqid6w5/xkTs21R8sUe67U2UynJDC/047786ceb646c4545fd1bada4dec38a0/1.png)
+![1](https://images.ctfassets.net/alneenqid6w5/xkTs21R8sUe67U2UynJDC/047786ceb646c4545fd1bada4dec38a0/1.png)
 > En la esquina superior derecha, está la __fecha en la que se realizó el pedido__ (06 MAYO).
 > Y en el inferior, se puede ver el __plazo de entrega del pedido__ (22 MAYO).
 
@@ -31,25 +31,25 @@ Ahora vamos a entrar en el módulo __Envío__ y simular el flete de ese pedido.
 
 Para ello, siga los pasos abajo:
 1. En el Admin VTEX, accede a **Envío > Simulador de envío**, o escribe *Simulador de envío* en la barra de búsqueda en la parte superior de la página.  
-2. Introduzca el nombre o el ID de cada SKU que estaba en el carrito del pedido que usted desea investigar, incluyendo la cantidad de cada uno de ellos.![2](//images.ctfassets.net/alneenqid6w5/4imJypzFvYSmMeQij3XLjp/429d397d9bec73f104cff43053b3c6a0/2.png)
+2. Introduzca el nombre o el ID de cada SKU que estaba en el carrito del pedido que usted desea investigar, incluyendo la cantidad de cada uno de ellos.![2](https://images.ctfassets.net/alneenqid6w5/4imJypzFvYSmMeQij3XLjp/429d397d9bec73f104cff43053b3c6a0/2.png)
 3. Introduzca el código postal del pedido.
 4. Haga clic en __Simular envío__.
 
 En el ejemplo siguiente, tenga en cuenta que 4 transportistas fueron considerados, y 12 fueron desconsiderados.
 
-![3](//images.ctfassets.net/alneenqid6w5/5k78O44E8Nr8nrTkBoe6MX/5d17f0a86264d1d09befbba43b0b1339/3.png)
+![3](https://images.ctfassets.net/alneenqid6w5/5k78O44E8Nr8nrTkBoe6MX/5d17f0a86264d1d09befbba43b0b1339/3.png)
 
 Al consultar una vez más la pantalla del pedido en el módulo OMS, vemos que el tipo de entrega elegido por el cliente para ese pedido fue el __Expressa__, y que la transportista elegida por la plataforma para realizar la entrega fue __Expressa & CO__.
 
-![4](//images.ctfassets.net/alneenqid6w5/2LjWMpCXtfH3lMYgAAjc7s/b62a52b045292c305143286ebcf93b88/4.png)
+![4](https://images.ctfassets.net/alneenqid6w5/2LjWMpCXtfH3lMYgAAjc7s/b62a52b045292c305143286ebcf93b88/4.png)
 
 Por lo tanto, volviendo a la simulación de flete, en el menu Envío, concluimos que la tercera opción fue la elegida en ese pedido - y que, por lo tanto, el plazo de entrega total del pedido fue de 12 días.
 
-![5](//images.ctfassets.net/alneenqid6w5/25KVkamW576ta3MkOpuYaN/2ae8577822b36650afe8153ebe4c6127/5.png)
+![5](https://images.ctfassets.net/alneenqid6w5/25KVkamW576ta3MkOpuYaN/2ae8577822b36650afe8153ebe4c6127/5.png)
 
 Ahora basta con hacer clic en __detallar__ para ver los tiempos de costo que se utilizaron para calcular el plazo de entrega.
 
-![6](//images.ctfassets.net/alneenqid6w5/42029fSPhJS5KKdio01gzh/dd0d9612093783f0cddf259f1b2e5798/6.png)
+![6](https://images.ctfassets.net/alneenqid6w5/42029fSPhJS5KKdio01gzh/dd0d9612093783f0cddf259f1b2e5798/6.png)
 
 Cada uno de los tres tiempos de costo corresponde a lo que se definió para las tres etapas de la ruta de logística: stock, muelle y transportadora.
 
diff --git a/docs/tutorials/es/checkout-vtex-overview.md b/docs/tutorials/es/checkout-vtex-overview.md
index 4d712c47e..18078746b 100644
--- a/docs/tutorials/es/checkout-vtex-overview.md
+++ b/docs/tutorials/es/checkout-vtex-overview.md
@@ -35,7 +35,7 @@ A continuación, se describe la experiencia de compra de un cliente, además de
 
 Siempre que el cliente realiza un cambio en el carrito (agrega o elimina ítems), o cuando se actualiza la pantalla del checkout, se ejecuta la siguiente cadena de procesos internos en el módulo Checkout.
 
-![Checkout overview](//images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/435f909fb3e5493329a6a76fcb398134/Checkout_Overview_ES.png)
+![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/435f909fb3e5493329a6a76fcb398134/Checkout_Overview_ES.png)
 
 <div class="alert alert-info">
 Si un <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#">Seller white label</a>, puede entregar uno o más ítems de los que eligió el cliente, se realizarán simulaciones (tal como se muestra a la derecha de la imagen) para determinar qué sellers serán los responsables de entregar los ítems. Obtén más información en <a href="https://help.vtex.com/es/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Selección de sellers white label</a>.
diff --git a/docs/tutorials/es/cms-folder-structure.md b/docs/tutorials/es/cms-folder-structure.md
index 312cf6778..003146a2b 100644
--- a/docs/tutorials/es/cms-folder-structure.md
+++ b/docs/tutorials/es/cms-folder-structure.md
@@ -33,7 +33,7 @@ Estas son las carpetas que toda tienda necesita tener en el CMS para garantizar
 
 A continuación, vea estas carpetas básicas en el CMS:
 
-![pastasObrigatorias](//images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
+![pastasObrigatorias](https://images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
 
 Estas carpetas vienen de forma predeterminada en el ambiente de todas las tiendas VTEX.
 
diff --git a/docs/tutorials/es/cms-overview.md b/docs/tutorials/es/cms-overview.md
index cea545a63..52b951740 100644
--- a/docs/tutorials/es/cms-overview.md
+++ b/docs/tutorials/es/cms-overview.md
@@ -15,7 +15,7 @@ legacySlug: cms-descripcion-general
 subcategory: 3PNmhq67KMmGTBSfIWJdcQ
 ---
 
-![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/4d6d76df74914b87f0f47e986ea7b405/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/4d6d76df74914b87f0f47e986ea7b405/CAPA_OVERVIEW_CMS.png)
 El CMS (Content Management System) es una funcionalidad dedicada a la gestión de contenido de manera práctica y constante.
 
 En VTEX, el CMS se encarga de gestionar las páginas que conforman el sitio web de tu tienda, ofreciéndote autonomía para crear, organizar, editar y definir toda la estructura de las carpetas, los archivos y los componentes de tu vitrina.
diff --git a/docs/tutorials/es/cms-store-overview.md b/docs/tutorials/es/cms-store-overview.md
index 0e2603424..4204c70fa 100644
--- a/docs/tutorials/es/cms-store-overview.md
+++ b/docs/tutorials/es/cms-store-overview.md
@@ -19,7 +19,7 @@ La página **Tienda** te permite realizar configuraciones de SEO, habilitar las
 
 En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Tienda** y descubre las principales herramientas disponibles en la interfaz.
 
-![CMS Tienda](//images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/1493fec4898f2f28e98bdd749b507fbf/store-es-overview.png)
+![CMS Tienda](https://images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/1493fec4898f2f28e98bdd749b507fbf/store-es-overview.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Antes de realizar cambios en la <b>pestaña Advanced (Avanzado)</b>, ponte en contacto con tu equipo de desarrolladores y consulta nuestra <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-best-practices-for-optimizing-performance#enabling-store-settings">documentación sobre la optimización del rendimiento</a> para mais informações.
diff --git a/docs/tutorials/es/collection-highlight-control.md b/docs/tutorials/es/collection-highlight-control.md
index 3439feba1..fe9aef535 100644
--- a/docs/tutorials/es/collection-highlight-control.md
+++ b/docs/tutorials/es/collection-highlight-control.md
@@ -28,7 +28,7 @@ En primer lugar, vamos a ver dónde se encuentra la flag Highlight:
 3. Haga clic en una colección.
 4. Marque la flag __Highlight__, que se encuentra en la pantalla de la colección, y haga clic en __Save Product Cluster__.
 
-![CollectionHighlightFlag](//images.contentful.com/alneenqid6w5/4ced6Gcbeg662KewckyQka/77aaef77fc87cf8112f759c867a6bd4b/CollectionHighlightFlag.png)
+![CollectionHighlightFlag](https://images.contentful.com/alneenqid6w5/4ced6Gcbeg662KewckyQka/77aaef77fc87cf8112f759c867a6bd4b/CollectionHighlightFlag.png)
 
 Al marcar la flag, usted informa al sistema que siempre que el control de destaque se utilice en el template de una página, los productos mostrados en esa página que formen parte de la colección deben aparecer con el elemento HTML abajo, donde en lugar de `{nombreDeLaColeccion}` aparece el nombre de la colección registrada en el CMS:
 
diff --git a/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md b/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
index 325ec849e..a396ec0a2 100644
--- a/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
+++ b/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
@@ -29,7 +29,7 @@ Para encontrar esta línea de código, acceda al front-end de su tienda, entre e
 
 A continuación se muestra la relación entre la carpeta en el CMS y el código fuente de la tienda.
 
-![CommerceContext](//images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
+![CommerceContext](https://images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
 
 <div class="alert alert-info">
 Esta línea de código está siempre comentada. Por lo tanto, tiene función sólo informativa. Es decir, no realiza ninguna acción.
diff --git a/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md b/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
index 17ea95885..8e8dd460f 100644
--- a/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
+++ b/docs/tutorials/es/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
@@ -31,7 +31,7 @@ Ahora que ha verificado el saldo, es importante tener en cuenta que el valor mí
 
 Por ejemplo, si el menor valor que puede recibir es R$10, ese es el valor mínimo que puede anticipar. El valor máximo se informa en el propio Admin - el saldo que usted acabó de verificar - en la página "Anticipar cuentas por cobrar".
 
-![anteciparpaymentES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/2tIGxzUGlbr3JwUMKFIKqu/57222cbc6c044d15be5e3a46f583e3e1/anteciparpaymentES.png_h_250_h_250)
+![anteciparpaymentES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/2tIGxzUGlbr3JwUMKFIKqu/57222cbc6c044d15be5e3a46f583e3e1/anteciparpaymentES.png_h_250_h_250)
 
 <div class=”alert alert-info”>
 <strong>Atención</strong>: las cuentas por cobrar en disputa o programadas para el siguiente día hábil no pueden ser anticipadas.
diff --git a/docs/tutorials/es/conditions-builder-usage-examples.md b/docs/tutorials/es/conditions-builder-usage-examples.md
index 5b38bdea8..dea047382 100644
--- a/docs/tutorials/es/conditions-builder-usage-examples.md
+++ b/docs/tutorials/es/conditions-builder-usage-examples.md
@@ -24,7 +24,7 @@ Para entender __para qué__ crear condiciones, vea el artículo [Crear Precios C
 
 UTM (Marketing tag) es una información que se refiere al origen del tráfico del cliente. Entonces, en el app existe un bloque que comprueba este tipo de información.
 
-![utm_source_english](//images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
+![utm_source_english](https://images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
 
 <div class="alert alert-warning"><strong>Nota: </strong>
 Es posible que su tienda utilice personalización y, por eso, las informaciones de UTM contenidas en la URL no se están pasando a nuestro sistema. Si utiliza personalización de Javascript, lea el artículo <a href="https://help.vtex.com/es/faq/por-que-las-utms-no-se-aplican-al-carrito">¿Por qué las UTMs no se aplican al carrito?</a>
@@ -42,7 +42,7 @@ __utm_campaign__ informa en __cuál campaña__ específicamente su cliente ha he
 
 __utm_medium__ informa cuál __canal de propaganda__ alcanzó a su cliente que puede ser, por ejemplo, Email o Banner en un website. En el caso de la imagen, el bloque comprueba si el canal fue *email*.
 
-![utmenglish](//images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
+![utmenglish](https://images.ctfassets.net/alneenqid6w5/4lFJ73jp9Cysoes6igUKO2/6e099fe8ff1600fc165ef4c1b008bdaa/utmenglish.png)
   
 Para cada uno de estos bloques, usted tiene la opción de verificar si:
 
@@ -86,7 +86,7 @@ Este bloque analiza el valor total que existe en el carrito.
 
 Vamos a suponer que usted quiera dar un precio más barato a un champú si el cliente está llevando __exactamente 3 unidades__, pero, además de eso, debe estar llevando __como mínimo 150 reales__ en compras. La condición que se creará será:
 
-![Exemplo2](//images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
+![Exemplo2](https://images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
 
 *cantidad de este artículo en el carrito es **exactamente** 3
 **Y**
diff --git a/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md b/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
index ae8cae30e..ba59fa880 100644
--- a/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
+++ b/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
@@ -29,7 +29,7 @@ En este escenario, si un cliente de Mercado Libre realiza una compra con dos o m
 
 VTEX no recomienda este tipo de configuración porque los pedidos no se integrarán.
 
-![cenario problemaES](//images.contentful.com/alneenqid6w5/7Dq2eWaMl08r5O0ntzRRGM/5c9f9c1c94a09c75ad3b22da4988942e/cenario_problemaES.JPG)
+![cenario problemaES](https://images.contentful.com/alneenqid6w5/7Dq2eWaMl08r5O0ntzRRGM/5c9f9c1c94a09c75ad3b22da4988942e/cenario_problemaES.JPG)
 
 Sin embargo, en la integración de las tiendas VTEX con Mercado Libre, hay dos escenarios para evitar este error. Por eso es necesario que su tienda tenga la siguiente configuración:
 
@@ -42,7 +42,7 @@ El seller utiliza una única subcuenta en VTEX y solo se integra con una cuenta
 
 En este escenario, si un cliente de Mercado Libre realiza una compra y el carrito contiene dos o más productos de diferentes tiendas oficiales del seller, el pedido se importará en VTEX correctamente. Esto se debe a que los productos que se anuncian en Mercado Libre forman parte del catálogo de una única subcuenta VTEX.
 
-![cenario unicousuarioES](//images.contentful.com/alneenqid6w5/2ioz7uT9i8krPZEmXC9HVw/7fafd490d3be84cdb63270afde292b27/cenario_unicousuarioES.JPG)
+![cenario unicousuarioES](https://images.contentful.com/alneenqid6w5/2ioz7uT9i8krPZEmXC9HVw/7fafd490d3be84cdb63270afde292b27/cenario_unicousuarioES.JPG)
 
 ## Múltiples subaccounts VTEX y diversas tiendas oficiales
 
@@ -50,4 +50,4 @@ El seller VTEX tiene dos o varias subaccounts y utiliza cada una de ellas para i
 
 En este escenario, si un usuario realiza una compra en Mercado Libre y el carrito contiene dos o más productos que pertenecen a diferentes subaccounts, los pedidos se integrarán normalmente en cada subcuenta VTEX. Esto ocurre porque cada pedido generado en Mercado Libre está vinculado a una subcuenta diferente en VTEX, por eso los productos vendidos coinciden con el catálogo de cada subcuenta.
 
-![cenario multiplosES](//images.contentful.com/alneenqid6w5/2CEz1Aa9kesmkS0BU8A1HH/8f42b09ce80f940eb6280555d3f600c0/cenario_multiplosES.JPG)
+![cenario multiplosES](https://images.contentful.com/alneenqid6w5/2CEz1Aa9kesmkS0BU8A1HH/8f42b09ce80f940eb6280555d3f600c0/cenario_multiplosES.JPG)
diff --git a/docs/tutorials/es/configure-cartman.md b/docs/tutorials/es/configure-cartman.md
index a0c303c01..d6651207c 100644
--- a/docs/tutorials/es/configure-cartman.md
+++ b/docs/tutorials/es/configure-cartman.md
@@ -58,7 +58,7 @@ Para más información sobre esta herramienta, consulta el artículo [Simulador
 
 Accediendo al **Ver detalles del carrito**, es posible consultar la información específica de cada uno de los productos seleccionados en el carrito.
 
-![Detalles del ítem](//images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/a643ad49b22b39430ab5b671288c4f7f/Detalles_del___tem.PNG)
+![Detalles del ítem](https://images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/a643ad49b22b39430ab5b671288c4f7f/Detalles_del___tem.PNG)
 
 ### Agregar ítems específicos al carrito
 
@@ -68,7 +68,7 @@ En **Agregar ítems por ID de SKU**, se pueden agregar nuevos ítems al carrito
 - **Cantidad de cada ítem**: indicación de cuántas unidades SKU se agregarán al carrito.
 - **ID do seller**: indicación de cuántas unidades SKU se agregarán al carrito. 
 
-![Agregar ítems por ID de SKU](//images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/784f07a4ade0a1cc3ac1f2bc2e5face2/Agregar___tems_por_ID_de_SKU.PNG)
+![Agregar ítems por ID de SKU](https://images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/784f07a4ade0a1cc3ac1f2bc2e5face2/Agregar___tems_por_ID_de_SKU.PNG)
 
 ### Agregar ítems aleatorios al carrito
 
@@ -82,7 +82,7 @@ En **Agregar ítems al azar**, nuevos ítems del catálogo de la tienda se puede
 - ID do seller
 - Gama de precios (Precio desde / Precio hasta)
 
-![Agregar ítems al azar](//images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/06250c93160b6506a130e4e7f34c3f9f/Agregar___tems_al_azar.PNG)
+![Agregar ítems al azar](https://images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/06250c93160b6506a130e4e7f34c3f9f/Agregar___tems_al_azar.PNG)
 
 ### Establecer datos de marketing
 
@@ -94,7 +94,7 @@ En la opción **Establecer datos de marketing**, puede aplicar cupones de descue
 - **utmi_cp**: utm interna utilizada para definir cuándo se aplicará una determinada promoción, según la utm descrita en la URL del pedido.  
 - **Cupón**: código de cupón de descuento para agregar al carrito.
 
-![Establecer datos de marketing](//images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/77827b5abd6f7cddb1c431468317589c/Establecer_datos_de_marketing.PNG)
+![Establecer datos de marketing](https://images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/77827b5abd6f7cddb1c431468317589c/Establecer_datos_de_marketing.PNG)
 
 Para obtener más información sobre UTMs y UTMIs, vaya a [Qué son utm_source, utm_campaign y utm_medium](https://help.vtex.com/es/tutorial/que-son-utm-source-utm-campaign-y-utm-medium--2wTz7QJ8KUG6skGAoAQuii#) y [Qué son las UTMs internas utmi_cp, utmi_pc y utmi_p](https://help.vtex.com/es/tutorial/o-que-sao-as-utms-internas-utmi_cp-utmi_pc-e-utmi_p#).
 
diff --git a/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
index 6686a9908..dd59caa7e 100644
--- a/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
@@ -45,7 +45,7 @@ Aquí, la propiedad común de los clientes será que también son empleados de l
 En este artículo se asume que los empleados están debidamente registrados con un campo booleano `isEmployee` establecido como true en sus respectivos documentos para la entidad de datos CL, como se muestra en la siguiente imagen.
 
 Si no lo están, revise el artículo [Crear un campo en Master Data](https://help.vtex.com/es/tutorial/how-can-i-create-field-in-master-data) para crear un campo que identifique a los empleados y configurarlo adecuadamente para cada documento correspondiente a los mismos.
-![Campo empleado](//images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/a66c5d5bdd16ae4152d7f07b1483d5f2/Campo_empleado.png)
+![Campo empleado](https://images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/a66c5d5bdd16ae4152d7f07b1483d5f2/Campo_empleado.png)
 
 <div class="alert alert-info" role="alert">Hay muchos detalles para configurar completamente una promoción. Si necesita información adicional sobre este asunto, consulte el artículo <a href="https://help.vtex.com/es/tutorial/creating-promotions-2">Crear promociones</a>.</div>
 
@@ -59,5 +59,5 @@ Con el campo configurado, la promoción puede crearse siguiendo los siguientes p
 6. En el campo inferior a **Clúster de clientes**, ingrese el clúster que identifica que los clientes son empleados (un par `{field}={value}`). En este caso, se usa `isEmployee=true` .
 7. Al final de la página, haga clic en **Guardar**.
 
-Después de esta configuración, la promoción ya debería estar funcionando como fue configurada. El descuento se muestra solo en el carrito de compra. La siguiente imagen muestra un ejemplo con 99% de descuento. ![Carrito con descuento](//images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/856ec8d08b57e045760ad5e2eb76efa3/Carrinho_com_desconto.png)
+Después de esta configuración, la promoción ya debería estar funcionando como fue configurada. El descuento se muestra solo en el carrito de compra. La siguiente imagen muestra un ejemplo con 99% de descuento. ![Carrito con descuento](https://images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/856ec8d08b57e045760ad5e2eb76efa3/Carrinho_com_desconto.png)
 
diff --git a/docs/tutorials/es/configure-template-in-smartcheckout-update.md b/docs/tutorials/es/configure-template-in-smartcheckout-update.md
index 024966ca5..8c362447f 100644
--- a/docs/tutorials/es/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/es/configure-template-in-smartcheckout-update.md
@@ -37,11 +37,11 @@ Cada sitio registrado corresponde a un multidominio (si la cuenta tiene multidom
 
 Creación del nuevo sitio web: 
 
-![ses.smartchackout1](//images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) 
+![ses.smartchackout1](https://images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) 
 
 Acceso a __Nombre de cuenta__:
 
-![ses.smartchackout2](//images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
+![ses.smartchackout2](https://images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
 
 ## Editar y configurar sitio
 
@@ -56,14 +56,14 @@ Acceso a __Nombre de cuenta__:
    - __Páginas__: mostrar páginas existentes para el sitio. 
 
 Ejemplo de sitios existentes en la misma cuenta:
-![ES Cards Portal](//images.ctfassets.net/alneenqid6w5/lHivoZotqDLXjLShaqv2i/a60e8f0fba49b962fd33f6d56652bec7/ES_Cards_Portal.png)
+![ES Cards Portal](https://images.ctfassets.net/alneenqid6w5/lHivoZotqDLXjLShaqv2i/a60e8f0fba49b962fd33f6d56652bec7/ES_Cards_Portal.png)
 
 Si desea __eliminar__ un sitio web, haga clic en el botón Eliminar del sitio web deseado, como en el siguiente ejemplo:
-![ses.smartchackout3](//images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
+![ses.smartchackout3](https://images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
 
 Si desea __eliminar__ una página existente, haga clic en el botón indicado en la imagen de abajo:
 
-![ses.smartchackout5](//images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
+![ses.smartchackout5](https://images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
 
 A continuación, pasaremos a la configuración paso a paso de las opciones del menú: __Código__ y __Checkout__ - pues configuran las páginas de *Checkout* y *Order Placed*.
 
@@ -80,7 +80,7 @@ A continuación, pasaremos a la configuración paso a paso de las opciones del m
   <li><b>Cálculo de las Opciones de Entrega (Beta y Stable)</b>: seleccione si el cálculo del flete se hará desde la hoja de cálculo o por geolocalización.</li>
   </ul>
 
-![ses.smartchackout6](//images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
+![ses.smartchackout6](https://images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
 
 ## Configurar código
 
@@ -90,7 +90,7 @@ A continuación, pasaremos a la configuración paso a paso de las opciones del m
 
 Ejemplo:
 
-![ses.smartchackout7](//images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
+![ses.smartchackout7](https://images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
 
 ### Configurar templates del menú "Código"
 
@@ -110,27 +110,27 @@ A continuación se muestran ejemplos de cómo se pueden llenar los códigos pres
 
 - Template __checkout-header__ y la cabecera de página del sitio web:
 
-![ses.smartchackout10](//images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) 
+![ses.smartchackout10](https://images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) 
 
-![checkout-header-page-es](//images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/d98e30e3889f5c94d509c6c3cf4c586e/smartcheckout11.pt.png)
+![checkout-header-page-es](https://images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/d98e30e3889f5c94d509c6c3cf4c586e/smartcheckout11.pt.png)
 
 - Template __checkout-footer__ y pie de página del sitio web:
 
-![checkout-footer-codigo-pt](//images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
+![checkout-footer-codigo-pt](https://images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
 
-![checkout-footer-cesta-es](//images.ctfassets.net/alneenqid6w5/4P9DSkLsgPN8F2x5JM1dQM/b71853e444095cbacba1b45a6f6110b6/checkout_footer_cesta.es.png)
+![checkout-footer-cesta-es](https://images.ctfassets.net/alneenqid6w5/4P9DSkLsgPN8F2x5JM1dQM/b71853e444095cbacba1b45a6f6110b6/checkout_footer_cesta.es.png)
 
 - Template __vtex-checkout__ y página de carrito al finalizar la compra:
 
-![smartcheckout16.pt](//images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
+![smartcheckout16.pt](https://images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
 
-![vtex-checkout-pagina-es](//images.ctfassets.net/alneenqid6w5/6yT3yPkqatyVRLQ4Cn0TVb/643e0bc15c803d5d50053e7eabc2fb29/ses.smartchackout17.png)
+![vtex-checkout-pagina-es](https://images.ctfassets.net/alneenqid6w5/6yT3yPkqatyVRLQ4Cn0TVb/643e0bc15c803d5d50053e7eabc2fb29/ses.smartchackout17.png)
 
 - Template __vtex-orderPlaced__ y página de pedido confirmado:
 
-![ses.smartchackout18](//images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) 
+![ses.smartchackout18](https://images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) 
 
-![vtex-orderplaced-paginas-es](//images.ctfassets.net/alneenqid6w5/2gFpnjs8tsTfOvmAgKQ3hh/8adc2c384b5ed34fbc5b02a82850c03e/ses.smartchackout19.png)
+![vtex-orderplaced-paginas-es](https://images.ctfassets.net/alneenqid6w5/2gFpnjs8tsTfOvmAgKQ3hh/8adc2c384b5ed34fbc5b02a82850c03e/ses.smartchackout19.png)
 
 ### Cuentas con multidominio 
 
@@ -138,5 +138,5 @@ Las cuentas que tengan multidominio pueden usar apenas un sitio web, si no hay n
 
 Clase insertada en el tag "body" de acuerdo al dominio accedido:
 
-![](//images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
+![](https://images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
 
diff --git a/docs/tutorials/es/configure-template-in-the-smartcheckout.md b/docs/tutorials/es/configure-template-in-the-smartcheckout.md
index 89828722b..086596ebc 100644
--- a/docs/tutorials/es/configure-template-in-the-smartcheckout.md
+++ b/docs/tutorials/es/configure-template-in-the-smartcheckout.md
@@ -32,7 +32,7 @@ Ahora, rellene los campos abajo siguiendo las instrucciones:
 
 Vea imagen abajo:
 
-![ses.smartchackout1](//images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) ![ses.smartchackout2](//images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
+![ses.smartchackout1](https://images.ctfassets.net/alneenqid6w5/KyggI6FeMn1nhKkrKekDj/55be5d1156b71333e640f7c75c693045/ses.smartchackout1.png) ![ses.smartchackout2](https://images.ctfassets.net/alneenqid6w5/2NH2v4bG5DZZucsAYKLt3o/bf6bee1d305b72c30045e717d3d229aa/ses.smartchackout2.png)
 
 Haga clic em Salvar para concluir el registro del nuevo sitio.
 
@@ -47,17 +47,17 @@ Como se indica en la próxima imagen, al hacer clic en el nombre del Sitio, el s
 - Código: Templates relacionados al sitio
 - Páginas: Exhibe las páginas que existen para el sitio: De modo estándar, se crean dos páginas, **checkout **y **checkout/orderPlaced**. Como fue dicho, al inicio de este post, la página** checkout **corresponde a las páginas de carrito, datos personales, dirección y forma de pago. La página **checkout/orderPlaced** corresponde a la página de Confirmación de Compra
 
-![ses.smartchackout3](//images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
+![ses.smartchackout3](https://images.ctfassets.net/alneenqid6w5/6PIZEMRdKproPnIFvHaNcG/d116b65f10aba502d0a9e21fee41cbfb/ses.smartchackout3.png)
 
 En** Páginas** es posible **Crear** nuevas páginas, **Editar** y **Excluir** páginas existentes. Vea las dos imágenes siguientes demostrando **Edición** y **Exclusión**. La creación sigue las mismas reglas de edición.
 
 Edición de página:
 
-![ses.smartchackout4](//images.ctfassets.net/alneenqid6w5/RtUdwXSva1HNq5LO4MMxN/726dacd630de7e3ec6372238b020b0a8/ses.smartchackout4.png)
+![ses.smartchackout4](https://images.ctfassets.net/alneenqid6w5/RtUdwXSva1HNq5LO4MMxN/726dacd630de7e3ec6372238b020b0a8/ses.smartchackout4.png)
 
 Exclusión de Página:
 
-![ses.smartchackout5](//images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
+![ses.smartchackout5](https://images.ctfassets.net/alneenqid6w5/6ruS0mUjxfgB9AdoXsucCh/72bf1ed75dde2ffa0bfe2558fdf41734/ses.smartchackout5.png)
 
 En **Checkout** podemos editar los campos abajo:
 
@@ -68,44 +68,44 @@ En **Checkout** podemos editar los campos abajo:
 
 Sigue imagen con ejemplos de cómo rellenar este formulário:
 
-![ses.smartchackout6](//images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
+![ses.smartchackout6](https://images.ctfassets.net/alneenqid6w5/5sUaemiWXUvCQ7nLeWyvE2/4c30814fa4d2db0360bb83ee2c124ef5/ses.smartchackout6.png)
 
 En **Código**, se exhibirán a la derecha todos los templates relacionados al Sitio. Como estándar, el sistema configura los templates que figuran como ejemplo en la imagen abajo:
 
-![ses.smartchackout7](//images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
+![ses.smartchackout7](https://images.ctfassets.net/alneenqid6w5/1PD1qlTDCj1Ckdp1BukJDf/1b5cdeabc1ff8fce27a5a4ff64cd39da/ses.smartchackout7.png)
 
 De esos templates, los únicos que no pueden modificarse son **vtex-checkout **e **vtex-orderPlaced**. Esos templates corresponden al funcionamiento nativo de la plataforma, o sea, son los que renderizan el contenido principal de esas páginas, tanto el checkout como el orderPlaced.
 
 En la siguiente imagen, demostramos el área afatada en el checkout por la configuración del template **checkout-footer**. Este es sólo un ejemplo de template vacío.
 
-![ses.smartchackout8](//images.ctfassets.net/alneenqid6w5/5xl9GdBzkLtWnJJXurEDuF/9c3d6c2c0499727c315aff8e085481d1/ses.smartchackout8.png) ![ses.smartchackout9](//images.ctfassets.net/alneenqid6w5/4bcDYXgUTPhSTEs98ptJe1/b807afcb4bf3eeb63d754646f074b321/ses.smartchackout9.png)
+![ses.smartchackout8](https://images.ctfassets.net/alneenqid6w5/5xl9GdBzkLtWnJJXurEDuF/9c3d6c2c0499727c315aff8e085481d1/ses.smartchackout8.png) ![ses.smartchackout9](https://images.ctfassets.net/alneenqid6w5/4bcDYXgUTPhSTEs98ptJe1/b807afcb4bf3eeb63d754646f074b321/ses.smartchackout9.png)
 
 En la próxima imagen, tenemos un ejemplo equivalente al anterior, pero, esta vez, con código HTML rellenado. Note que el código rellenado a la izquierda corresponde al área superior de la derecha. Ese es el template** checkout-header**.
 
-![ses.smartchackout10](//images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) ![ses.smartchackout11](//images.ctfassets.net/alneenqid6w5/3rQkwWZiERd3L9Js6DqHoj/5f724a23f6951f069f368b346ff7c206/ses.smartchackout11.png)
+![ses.smartchackout10](https://images.ctfassets.net/alneenqid6w5/5laYto6t3IYF5YjJNmlo7t/457f048f5b8450cf5b3e925f72e9e971/ses.smartchackout10.png) ![ses.smartchackout11](https://images.ctfassets.net/alneenqid6w5/3rQkwWZiERd3L9Js6DqHoj/5f724a23f6951f069f368b346ff7c206/ses.smartchackout11.png)
 
 Como podemos ver en la próxima imagen, todos los templates que tengan el prefijo** checkout **se usarán en todas las páginas del Checkout. En este ejemplo ya estamos en la página Forma de Pagamento y note que el header cargado es el mismo del ejemplo anterior.
 
-![ses.smartchackout12](//images.ctfassets.net/alneenqid6w5/3xZgBYnuTjYcwQDop5eYxT/f2120bdf05a5883ee11d91f7c308a41e/ses.smartchackout12.png) ![ses.smartchackout13](//images.ctfassets.net/alneenqid6w5/2PZAzsLIwAp1wL6YiXuidN/913d83cb447406bd2597029808818880/ses.smartchackout13.png)
+![ses.smartchackout12](https://images.ctfassets.net/alneenqid6w5/3xZgBYnuTjYcwQDop5eYxT/f2120bdf05a5883ee11d91f7c308a41e/ses.smartchackout12.png) ![ses.smartchackout13](https://images.ctfassets.net/alneenqid6w5/2PZAzsLIwAp1wL6YiXuidN/913d83cb447406bd2597029808818880/ses.smartchackout13.png)
 
 Como en los templates del **checkout**, lo mismo ocurre con los templates de orderPlaced. O sea, los templates con prefijo **orderPlaced** corresponden solamente a la página OrderPlaced (Confirmación de Compra).
 
-![ses.smartchackout14](//images.ctfassets.net/alneenqid6w5/4EfbPzpvD6Buwn71HNchoC/7437e0cf4506f83c59587511f78f6d39/ses.smartchackout14.png) ![ses.smartchackout15](//images.ctfassets.net/alneenqid6w5/5XEhlCcJKuXETy1z5P2cMu/aa70c832db354d9f4060e0771efeafcc/ses.smartchackout15.png)
+![ses.smartchackout14](https://images.ctfassets.net/alneenqid6w5/4EfbPzpvD6Buwn71HNchoC/7437e0cf4506f83c59587511f78f6d39/ses.smartchackout14.png) ![ses.smartchackout15](https://images.ctfassets.net/alneenqid6w5/5XEhlCcJKuXETy1z5P2cMu/aa70c832db354d9f4060e0771efeafcc/ses.smartchackout15.png)
 
 Como se ha explicado arriba, los únicos templates en que no se permiten modificaciones son **vtex-checkout** y **vtex-orderPlaced**. Esos templates renderizan al contenido básico de las páginas Checkout y OrderPlaced. A continuación, ejemplos del contenido renderizado por los templates.
 
 Template **vtex-checkout**:
 
-![ses.smartchackout16](//images.ctfassets.net/alneenqid6w5/6YRb9FuRRmLJStVlx6giuY/40569c34738b82ccf51296f6dbf92272/ses.smartchackout16.png) ![ses.smartchackout17](//images.ctfassets.net/alneenqid6w5/4vYztmiow2QijU3rPh9tET/77bfd5e4bea43fc71657f44b3cbb46bf/ses.smartchackout17.png)
+![ses.smartchackout16](https://images.ctfassets.net/alneenqid6w5/6YRb9FuRRmLJStVlx6giuY/40569c34738b82ccf51296f6dbf92272/ses.smartchackout16.png) ![ses.smartchackout17](https://images.ctfassets.net/alneenqid6w5/4vYztmiow2QijU3rPh9tET/77bfd5e4bea43fc71657f44b3cbb46bf/ses.smartchackout17.png)
 
 Template **vtex-orderPlaced**:
 
-![ses.smartchackout18](//images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) ![ses.smartchackout19](//images.ctfassets.net/alneenqid6w5/1Atqv6If7ZP9N5PgrYZlMH/8f38382856a04c34d6cc6570e7f55797/ses.smartchackout19.png)
+![ses.smartchackout18](https://images.ctfassets.net/alneenqid6w5/7v3DAlrUo8B4uFwn8G0NI8/b2859b32f480e91e8142969e6975cb43/ses.smartchackout18.png) ![ses.smartchackout19](https://images.ctfassets.net/alneenqid6w5/1Atqv6If7ZP9N5PgrYZlMH/8f38382856a04c34d6cc6570e7f55797/ses.smartchackout19.png)
 
 Las cuentas que tengan multi dominio pueden usar sólo un sitio, si no hay necesidad de configuraciones específicas. Esto porque, aunque existe sólo un Sitio, la plataforma incluye una clase en la tag "body" de acuerdo al dominio accedido. Así, es sencillo aplicar layouts diferentes para el mismo sitio.
 
 Clase insertada en la tag &lt;body&gt; de acuerdo al dominio accedido:
 
-![](//images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
+![](https://images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
 
 Importante: Todo javascript que se incluya directamente en cualquier template del Portal será ignorado por la plataforma, o sea, al renderizar la página, la plataforma lo removerá. Esto porque el SmartCheckout sólo acepta scripts originados en el Google Tag Manager. Entonces, siempre que sea necesario realizar alguna personalización (o aun inserción de tags específicas) vía javascript, haga esa inclusión vía Google Tag Manager.
diff --git a/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md b/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md
index 28f89f5e8..ddf000ef1 100644
--- a/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md
+++ b/docs/tutorials/es/configuring-a-discount-for-orders-prepaid-in-full.md
@@ -33,7 +33,7 @@ Después de determinar el descuento en Checkout, se debe vincular el SKU al medi
 3. Haga clic en el template de su página de producto en la lista de templates.
 4. En la propiedad `skuPrice`, añada la variable `paymentSystemId` con el ID del medio de pago deseado. 
 
-![Screenshot 2020-12-18 Crear precio al contado](//images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
+![Screenshot 2020-12-18 Crear precio al contado](https://images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
 
 6. Luego, haga clic en __Save Template__ en el campo superior, para guardar la alteración.
 
diff --git a/docs/tutorials/es/configuring-a-marketplace-trade-policy.md b/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
index 60a12ba75..41d2504b1 100644
--- a/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
@@ -39,14 +39,14 @@ La creación de una nueva política comercial es el primer paso para definir las
 
 Esta configuración se realiza en el módulo «Configuración de la tienda», en la página «Políticas comerciales». Debe crear [una nueva política comercial](https://help.vtex.com/es/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) cuando la configuración de catálogo, precios, promociones, logística y pagos sean diferentes entre los *marketplaces* en que los *sellers* venden sus productos. 
 
-![ES Add Politica comercial](//images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e6ae3d0e4f32b580ebda4800b173e981/ES_Add_Politica_comercial.jpg)
+![ES Add Politica comercial](https://images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/e6ae3d0e4f32b580ebda4800b173e981/ES_Add_Politica_comercial.jpg)
 
 ## Gestión de pedidos
 Después de crear una política comercial, debe asociarla a cada *marketplace* en que el *seller* venda productos al registrar [afiliados](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). Así es como los *sellers* identifican la política comercial que opera en cada *marketplace*. Si su tienda vende productos en tres *marketplaces* diferentes, deberá crear tres afiliados, cada uno de los cuales representará un *marketplace*. 
 
 Esto se hace en la página *Configuración* del módulo *Gestión de pedidos* de su tienda al registrar afiliados. Incluso si crea varias, es importante tener en cuenta que solamente se aplicará una política comercial a la vez en el *marketplace*. 
 
-![PT Afiliado](//images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/0db945d3f87f491d66023b8cd25c2c03/PT_Afiliado.jpg)
+![PT Afiliado](https://images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/0db945d3f87f491d66023b8cd25c2c03/PT_Afiliado.jpg)
 
 *En el ejemplo anterior, el afiliado «Amazon» está vinculado a la política comercial «1».* 
 
@@ -60,7 +60,7 @@ La configuración se realiza en el módulo *Promociones* en todas las [promocion
 
 Si no selecciona ninguna política comercial, la promoción estará disponible en todos los canales de venta.
 
-![ES Promoções Politica Comercial](//images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/b1ff93abd371c23100c5447f48ed1452/ES_Promo____es_Politica_Comercial.jpg)
+![ES Promoções Politica Comercial](https://images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/b1ff93abd371c23100c5447f48ed1452/ES_Promo____es_Politica_Comercial.jpg)
 
 *En el ejemplo anterior, la promoción solo se aplicará a los pedidos de las políticas comerciales «Marketplace-BRL» y «Argentina-ARS», donde la tienda opera como seller. La promoción no estará disponible en el storefront de VTEX.* 
 
@@ -69,7 +69,7 @@ Los *sellers* que tramitan el pago de las ventas de sus productos en un *marketp
 
 La configuración se realiza en el módulo *Pagos* al [crear una condición especial](https://help.vtex.com/es/tutorial/condicoes-especiais--tutorials_456) y asociarla a las políticas comerciales deseadas. Si no establece ninguna restricción, la política comercial se aplicará a todos los canales de venta. 
 
-![ES Pagamento Politica comercial](//images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/0873eeb5985892804d08ad32da2c0ef4/ES_Pagamento_Politica_comercial.jpg)
+![ES Pagamento Politica comercial](https://images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/0873eeb5985892804d08ad32da2c0ef4/ES_Pagamento_Politica_comercial.jpg)
 
 *En el ejemplo anterior, el plazo de pago está asociado a la política comercial «Marketplace». Esto hace que la condición de pago esté disponible solo en los canales de venta asociados a esta política comercial.*
 
@@ -82,7 +82,7 @@ Esta configuración se realiza en el módulo *Catálogo*, al [registrar producto
   No recomendamos vincular políticas comerciales a colecciones para determinar el surtido de productos, especialmente para los marketplaces fuera de VTEX. Cuando se elimina un producto de la colección de políticas comerciales, el sistema VTEX no notifica al marketplace de esta actualización, lo que hace que el producto continúe disponible en el marketplace.
   </div>
 
-[![ES Catalogo Politica](//images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/7be99b14d44e2f31d29e740e71954830/ES_Catalogo_Politica.jpg)
+[![ES Catalogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/7be99b14d44e2f31d29e740e71954830/ES_Catalogo_Politica.jpg)
 
 *En el ejemplo anterior, el producto solo estará disponible para los canales de venta que utilicen las políticas comerciales «Carrefour» y «Marketplace».* 
 
@@ -94,7 +94,7 @@ Esta configuración se realiza en el módulo *Precios* mediante políticas comer
 - [Reglas de precio](https://help.vtex.com/es/tutorial/configurar-regra-de-preco-para-politica-comercial--5LQMLwcUcEGCWK6SMI6cEM): para determinar un *markup* para categorías y marcas específicas;
 - [Precios fijos](https://help.vtex.com/es/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy): para diferenciar precios en productos específicos.
 
-![ES Regra de preço](//images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/29127a3e4000ccab87c352d3f1366d88/ES_Regra_de_pre__o.jpg)
+![ES Regra de preço](https://images.ctfassets.net/alneenqid6w5/5088id7auaoQLD6AMxS30F/29127a3e4000ccab87c352d3f1366d88/ES_Regra_de_pre__o.jpg)
 
 *En el ejemplo anterior, la regla de precios aplicó un *markup* a la política comercial «Marketplace» para los productos de la categoría «Fera-Fashion».* 
 
@@ -104,10 +104,10 @@ Los *sellers* pueden configurar [rutas logísticas](https://help.vtex.com/es/tra
 
 Ambas configuraciones se realizan en el módulo *Estrategia de envío*. Al crear un [muelle](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj), debe indicar las políticas comerciales a las que servirá. Esto hace que las políticas de envío que estén asociadas a ese muelle estén disponibles para las políticas comerciales vinculadas. Luego, debe asociar el [stock](https://help.vtex.com/es/tutorial/gerenciar-estoque) deseado a un muelle para que el inventario esté disponible para las políticas comerciales asociadas a ese muelle. 
 
-![ES Doca Politica](//images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/3e55a5e475674fd88cbf71df09daaca7/ES_Doca_Politica.jpg)
+![ES Doca Politica](https://images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/3e55a5e475674fd88cbf71df09daaca7/ES_Doca_Politica.jpg)
 *En el ejemplo anterior, el muelle está asociado a la política comercial «Marketplace», que recibirá servicio de la transportadora «Transportadora A».*
 
-![ES Estoque Politica](//images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/152ee7c4c467347a3276be98cd2c55f6/ES_Estoque_Politica.jpg)
+![ES Estoque Politica](https://images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/152ee7c4c467347a3276be98cd2c55f6/ES_Estoque_Politica.jpg)
 *En el ejemplo anterior, el stock está asociadao al "Muelle A", por lo que este será el *stock* que utilizarán las políticas comerciales vinculadas al "Muelle A".* 
 
 ## Integraciones
@@ -115,7 +115,7 @@ Las políticas comerciales también se aplican a todas las integraciones en las
 
 Las [integraciones](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#vender-em-marketplace) se realizan en la página *Configuración* del módulo *Integraciones*. Cada canal suele requerir condiciones comerciales específicas, aunque es posible que diferentes canales compartan la misma política comercial. 
 
-![ES Integracao Politica](//images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/46985758c94413183a675ee1993162f8/ES_Integracao_Politica.jpg)
+![ES Integracao Politica](https://images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/46985758c94413183a675ee1993162f8/ES_Integracao_Politica.jpg)
 *En el ejemplo anterior, la política comercial «Marketplace» se aplica a la integración con Google Shopping.*
 
 ## Sepa más
diff --git a/docs/tutorials/es/configuring-banners.md b/docs/tutorials/es/configuring-banners.md
index 38f7dec6d..5c014ca79 100644
--- a/docs/tutorials/es/configuring-banners.md
+++ b/docs/tutorials/es/configuring-banners.md
@@ -29,7 +29,7 @@ Después de configurar el banner, debes agregarlo a una página de tu tienda. Pa
 <p> Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configuración Multidioma (Beta)</a>para saber más.</p>
 </div>
 
-![banner-form-es](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
+![banner-form-es](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
 
 ## Campos de registro del banner
 
@@ -60,7 +60,7 @@ Para registrar el banner, debes rellenar los siguientes campos:
 
 Haz clic en <i class="fa-solid fa-link"></i> `Autocompletar desde URL` para agregar la URL de la página de búsqueda donde se aplicarán las reglas de activación.
 
-![banner-url-es](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
+![banner-url-es](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/c7c8d7edfb83b4bb4f1e829b4aa50dc9/image.png)
 
 Haz clic en <i class="fas fa-plus"></i> `Agregar condición` para crear una regla. Pueden ser de los siguientes tipos:
 
diff --git a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index ab0909160..4c9f05117 100644
--- a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -43,7 +43,7 @@ Puedes bajar un archivo de plantilla haciendo clic en VTEX file template en la p
 	<li>Una vez finalizado el proceso de importación, puedes hacer clic en Ver detalles de la importación para acceder al informe de importación.</li>
 </ol>
 
-![Importação em massa - ES](//images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/b8c5a8462d5e9f330a9601975ef2fca9/Bulk_import_vers_o_original-gif-ES.gif)
+![Importação em massa - ES](https://images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/b8c5a8462d5e9f330a9601975ef2fca9/Bulk_import_vers_o_original-gif-ES.gif)
 
 # Errores de importación
 
@@ -61,7 +61,7 @@ Para ver los detalles de los problemas encontrados, sigue los pasos a continuaci
 Asegúrate de que el archivo que cargues solo contenga las correcciones de los errores previamente identificados para garantizar que la importación se realice correctamente.
 </div>
 
-![Bulk import - ES](//images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/2cdc7eb8e0710fff44a55b1a2619c58b/Bulk_import_vers_o_error-gif-ES.gif)
+![Bulk import - ES](https://images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/2cdc7eb8e0710fff44a55b1a2619c58b/Bulk_import_vers_o_error-gif-ES.gif)
 
 # Importación vía API
 
diff --git a/docs/tutorials/es/configuring-cargo-splitting.md b/docs/tutorials/es/configuring-cargo-splitting.md
index 58b052b2b..2f1d4f601 100644
--- a/docs/tutorials/es/configuring-cargo-splitting.md
+++ b/docs/tutorials/es/configuring-cargo-splitting.md
@@ -19,7 +19,7 @@ El reparto de carga es la configuración que permite que se divida una compra en
 
 No tener esta configuración puede imposibilitar el cierre de una compra, pues, caso la suma del peso de los productos del carrito sea mayor que el límite máximo de peso catastrado en las políticas de envío, no será posible la finalización de la compra.
 
-![divisao-carga-desenho es](//images.ctfassets.net/alneenqid6w5/13LOZvGLCCIm8YKSg2oeiI/186189daff4771ee6368096b8d267394/divisao-carga_es.png)
+![divisao-carga-desenho es](https://images.ctfassets.net/alneenqid6w5/13LOZvGLCCIm8YKSg2oeiI/186189daff4771ee6368096b8d267394/divisao-carga_es.png)
 
 ### Cómo configurar el reparto de carga
 
diff --git a/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
index c9a2a432b..3929e3a13 100644
--- a/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
@@ -78,7 +78,7 @@ Para configurar ClearSale Global, deberá:
 <br>  
   <ui>11. En la esquina superior derecha, hacer clic en <b>Publicar</br>.</ui>
 
-![Fingerprint ClearSalve_Pantalla](//images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/2f5d30cbf3147be7da09d3f86186dafc/Fingerprint_ClearSalve_Pantalla.png)
+![Fingerprint ClearSalve_Pantalla](https://images.ctfassets.net/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/2f5d30cbf3147be7da09d3f86186dafc/Fingerprint_ClearSalve_Pantalla.png)
 
 Para más detalles sobre el código introducido en Google Tag Manager, recomendamos leer [esta documentación](https://api.clearsale.com.br/docs/behavior-analytics) de ClearSale.
 
diff --git a/docs/tutorials/es/configuring-clearsale-v3-antifraud.md b/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
index 50b09a38d..378aaa90d 100644
--- a/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
@@ -73,7 +73,7 @@ La configuración del antifraude ClearSale v3 requiere la creación de una etiqu
 10. Hacer clic en el botón __Crear Tag__, insertar un nombre para esta tag y guardar.
 11. En la esquina superior derecha, hacer clic en __Publicar__.
 
-![Pasted image at 2017 10 20 01 11 PM](//images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
+![Pasted image at 2017 10 20 01 11 PM](https://images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
 
 ## Detalles del campo customSLA
 
diff --git a/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md b/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md
index 65986e287..caa394f4b 100644
--- a/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md
+++ b/docs/tutorials/es/configuring-functions-in-the-message-center-templates.md
@@ -35,7 +35,7 @@ La utlización de esas variables en los Layouts de email poseen la siguiente sin
 **HTML del template**
 `<strong>{{_accountInfo.HostName}}</strong> => lojavirtual`
 
-![exemplohtml](//images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
+![exemplohtml](https://images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
 
 El ejemplo arriba puede tener diferentes valores cuando se comparan Sellers y Marketplaces.
 
@@ -130,4 +130,4 @@ em até{{#hasSubStr shippingEstimate 'bd'}}
 ```
 
 **Resultado**:
-![](//images.contentful.com/alneenqid6w5/5cRmcM2692G60Ok6gSAWmo/f7196556f5360f632dbccf47f837b5b9/3.1.jpg)
+![](https://images.contentful.com/alneenqid6w5/5cRmcM2692G60Ok6gSAWmo/f7196556f5360f632dbccf47f837b5b9/3.1.jpg)
diff --git a/docs/tutorials/es/configuring-greenlist.md b/docs/tutorials/es/configuring-greenlist.md
index ea809e070..5f6697251 100644
--- a/docs/tutorials/es/configuring-greenlist.md
+++ b/docs/tutorials/es/configuring-greenlist.md
@@ -45,7 +45,7 @@ Cuanto más datos de suscripción exijas, más estrictas serán tus reglas, y me
 
 Para marcar un cliente como confiable, el propietario de la tienda usa algunos criterios. Estos criterios son los __datos de compra que componen la firma de un pedido__
 
-![Greenlist - suscripción](//images.contentful.com/alneenqid6w5/3CvVVFRIJ22wS6o8sq6ok6/45cdf4a8259437d36aa74a40a8a04715/Greenlist_-_assinatura.png) 
+![Greenlist - suscripción](https://images.contentful.com/alneenqid6w5/3CvVVFRIJ22wS6o8sq6ok6/45cdf4a8259437d36aa74a40a8a04715/Greenlist_-_assinatura.png) 
 
 Digamos que marques tres de las opciones arriba: __E-mail__, __Dirección de entrega__ y __Tarjeta de crédito__. Esto significa que, para que nuevos pedidos de ese cliente no pasen por el antifraude, él tiene que usar en nuevas compras los mismos datos de email, dirección y tarjeta de crédito. 
 
@@ -57,7 +57,7 @@ La recurrencia de la firma define el número de pedidos que un cliente debe hace
 
 Este número debe definirlo el propio propietario de la tienda, y puede variar de __1 a 10__.
 
-![Greenlist - recurrencia](//images.contentful.com/alneenqid6w5/2TFJUnw1Cw8I0KcqCcAsmS/6aaec62228ec8ff5a38093e743a4229b/Greenlist_-_recorrencia.png)
+![Greenlist - recurrencia](https://images.contentful.com/alneenqid6w5/2TFJUnw1Cw8I0KcqCcAsmS/6aaec62228ec8ff5a38093e743a4229b/Greenlist_-_recorrencia.png)
 
 Si defines la recurrencia en 6, por ejemplo, todos los clientes de tu tienda que hagan seis compras usando los mismos datos definidos en la firma dejan de pasar por el antifraude a partir de la próxima compra.
 
@@ -65,7 +65,7 @@ Si defines la recurrencia en 6, por ejemplo, todos los clientes de tu tienda que
 
 Puedes configurar un valor máximo para que la Greenlist sea válida. Esto porque aun si un cliente ya ha sido marcado como confiable, puedes preferir que - para valores muy altos, en los que es mayor el riesgo de pérdida – el antifraude actúe independientemente del historial de compras de ese cliente.
 
-![Greenlist - valor maximo](//images.contentful.com/alneenqid6w5/1CG6Wm74qIu4Qam2WekkE4/02f3e165b7970651406d667ae66e4589/Greenlist_-_valor_maximo.png)
+![Greenlist - valor maximo](https://images.contentful.com/alneenqid6w5/1CG6Wm74qIu4Qam2WekkE4/02f3e165b7970651406d667ae66e4589/Greenlist_-_valor_maximo.png)
 
 ### Plazo de seguridad para Chargeback
 
@@ -73,7 +73,7 @@ Algunas veces, después de efectuado un pedido y aprobada la compra por el antif
 
 En este caso, es interesante definir un margen de seguridad para el análisis de la Greenlist. Por ejemplo, al elegir un plazo de seguridad de 30 días, el comerciante está diciendo que todo pedido aprobado por el antifraude será evaluado por la Greenlist solamente después de 30 días.
 
-![Greenlist - chargeback](//images.contentful.com/alneenqid6w5/314Ig5HLCU2uy0kyYEu4gC/105ed241ac49923035a7b4d441d698e0/Greenlist_-_chargeback.png)
+![Greenlist - chargeback](https://images.contentful.com/alneenqid6w5/314Ig5HLCU2uy0kyYEu4gC/105ed241ac49923035a7b4d441d698e0/Greenlist_-_chargeback.png)
 
 ### Activando la Greenlist
 
@@ -92,6 +92,6 @@ Si identificas que el pedido de un cliente integrante de la Greenlist (o cualqui
 2. En la lista de transacciones, hacer clic en la transacción que se desea marcar como fraude;
 3. Hacer clic en el botón __Marcar el pago como fraude__.
 
-![Marcar como fraude](//images.contentful.com/alneenqid6w5/3EiAcGulosCgQq4qCIGqQE/d0be6c70e7129f63b189c56bdb79012b/fraud.png)
+![Marcar como fraude](https://images.contentful.com/alneenqid6w5/3EiAcGulosCgQq4qCIGqQE/d0be6c70e7129f63b189c56bdb79012b/fraud.png)
 
 Una vez que se marca una transacción como fraude, se remueve del Greenlist el cliente que hizo el pedido. 
diff --git a/docs/tutorials/es/configuring-login-with-facebook-and-google.md b/docs/tutorials/es/configuring-login-with-facebook-and-google.md
index e325ab6ac..928a96ef2 100644
--- a/docs/tutorials/es/configuring-login-with-facebook-and-google.md
+++ b/docs/tutorials/es/configuring-login-with-facebook-and-google.md
@@ -39,14 +39,14 @@ Después de realizar la configuración en Facebook y Google, debes configurar la
 
   Se te redirigirá a la pestaña **Tienda virtual** de la página **Autenticación**, que lista los métodos de inicio de sesión disponibles en tu tienda.
 
-  ![Lista Autenticación](//images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/814b27712f00a7a00bcc3c717a3aee5f/autenticacao-es.png)
+  ![Lista Autenticación](https://images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/814b27712f00a7a00bcc3c717a3aee5f/autenticacao-es.png)
 3. En la fila del proveedor de inicio de sesión deseado, haz clic en `Configurar`.
 4. Rellena el formulario con el `Client ID` y el `Secreto del cliente` registrados en la [etapa anterior](#obtener-credenciales-de-los-proveedores) y haz clic en `Guardar`.
 
-  ![Facebook OAuth ES](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/e85e70614c1ff706937104c8f5ec917c/1-login-fb-es.PNG)
+  ![Facebook OAuth ES](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/e85e70614c1ff706937104c8f5ec917c/1-login-fb-es.PNG)
 5. En la página **Autenticación**, activa el uso del proveedor haciendo clic en el botón de alternancia. 
 
-  ![Lista Autenticación Switch On Highlight](//images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/7567505995ce1af975d6b5c69159a323/switch_On_highlight_ES.png)
+  ![Lista Autenticación Switch On Highlight](https://images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/7567505995ce1af975d6b5c69159a323/switch_On_highlight_ES.png)
 
 ## Validar la configuración
 
diff --git a/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
index 838917b43..faadeb13e 100644
--- a/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -58,7 +58,7 @@ Para configurar esta liquidación, siga los pasos a continuación:
 8. En el campo __Captura anticipada__, seleccione una de las opciones de tiempo disponibles. 
 9. Rellene el  campo __Cambiar el tiempo máximo de captura automática__ con el periodo acordado con el adquirente. __Si usted prefiere dejar el campo en blanco, se utilizará el estándar de 4 días.__
 
-![captura_automatica_ES](//images.ctfassets.net/alneenqid6w5/4jX317pC0aLgMXygXxd1XU/6a7d21e16d4ef26e0076ad7b641e877f/image.png)
+![captura_automatica_ES](https://images.ctfassets.net/alneenqid6w5/4jX317pC0aLgMXygXxd1XU/6a7d21e16d4ef26e0076ad7b641e877f/image.png)
 10. Haga clic en el __botón Salva__ para guardar.
 
 De esta manera, se implementará el nuevo recurso de liquidación.
diff --git a/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
index 8cc4b8229..56f548b03 100644
--- a/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
@@ -63,13 +63,13 @@ Para asegurarse de que este recurso funciona, es necesario revisar los detalles
 4. En la siguiente página, haga clic en __+Información__.
 5. Al hacer clic en __+Información__, busque el campo __deviceFingerprint__ y verifique si el  código disponible inicia con la palabra __armor__, según el siguiente ejemplo. 
 
-![Device Fingerprint Armor](//images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/ea05aa211a85d6731b7eb6308ebfd192/DEVICEFINGERPRINTARMOR.png)
+![Device Fingerprint Armor](https://images.ctfassets.net/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/ea05aa211a85d6731b7eb6308ebfd192/DEVICEFINGERPRINTARMOR.png)
 
 <ui>
 6. Después de confirmar que la información es correcta, el paso final para la verificación deDevice Fingerprint es enviar el ID de la transacción al equipo de Mercado Pago. Este ID puede encontrarse en el campo <b>authorizationConnectorResponse</b>, en el detalle de la transacción.
   </ui>
 
-  ![Autorización](//images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/5c71d9b8d1eed010b71ddb838fd47f19/AUTHORIZATION.png)
+  ![Autorización](https://images.ctfassets.net/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/5c71d9b8d1eed010b71ddb838fd47f19/AUTHORIZATION.png)
 
 <ui>
   7. Copie el ID y <a href=https://www.mercadopago.com.ar/developers/es/support>envíe un email</a> a Mercado Pago con esta información y pídales que validen la transacción. De esta manera, Mercado Pago podrá evaluar si el Dispositivo Fingerprint está funcionando correctamente.
diff --git a/docs/tutorials/es/configuring-my-account-conversational-commerce.md b/docs/tutorials/es/configuring-my-account-conversational-commerce.md
index 8c16a6bf4..4abb8fc80 100644
--- a/docs/tutorials/es/configuring-my-account-conversational-commerce.md
+++ b/docs/tutorials/es/configuring-my-account-conversational-commerce.md
@@ -24,7 +24,7 @@ subcategory: 5bBAgUbHdh6ovdZ4kGsN7O
 
 ## Campos de configuración de conversación
 
-![my account - conversational commerce - ES](//images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/78adcfa1fc6e5d221e9bcd57aee82a28/image.png)
+![my account - conversational commerce - ES](https://images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/78adcfa1fc6e5d221e9bcd57aee82a28/image.png)
 
 - **Idioma: **el idioma predeterminado para los mensajes del bot con los clientes en VTEX Conversational Commerce. Campo obligatorio.
 
diff --git a/docs/tutorials/es/configuring-payment-gateways.md b/docs/tutorials/es/configuring-payment-gateways.md
index 8668e583d..5168dfbdd 100644
--- a/docs/tutorials/es/configuring-payment-gateways.md
+++ b/docs/tutorials/es/configuring-payment-gateways.md
@@ -18,5 +18,5 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 Los medios de pago son esenciales para llevar la tienda a producción. Para eso, acceda al [PCI Gateway](http://help.vtex.com/es/tutorial/pci-gateway-vision-general), que es el módulo certificado por el PCI DSS, garantizando la seguridad de los datos de pago de sus clientes.
 
 _El video abajo todavía no ha sido traduccido al español._
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3011-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4?_=1" />[//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4](//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4 "//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3011-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4?_=1" />[//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4](https://downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4 "//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4")</video>
 
diff --git a/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index 5eca3a143..2c809ff5b 100644
--- a/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -51,7 +51,7 @@ Para habilitar el acceso de VTEX en el entorno Adyen, sigue los pasos a continua
 2. En la barra lateral izquierda, copia y guarda la información descrita antes de **Company**. Esta es tu Company Account.
 3. En la lista de abajo, busca el nombre de la Merchant Account a utilizar (resaltada en blanco). Copia y guarda esta información.
 
-![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtener la POS Live URL
 
@@ -70,7 +70,7 @@ La información a continuación supone que la API Key se ha generado previamente
 2. Selecciona tu credencial API.
 3. En **Server Settings > Authentication**, selecciona **API key**. 
 
-![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Haz clic en <b>Generate Key</b> y anota la información creada en un lugar seguro.</ui>
 
@@ -86,7 +86,7 @@ Configura el webhook según los pasos a continuación:
 4. En **General > Description**, agrega una descripción para el nuevo webhook. Ejemplo: "Webhook Adyen Connector Provider v3".
 5. En **General > Server configuration > URL**, introduce la URL de tu cuenta VTEX. Ejemplo https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Haz clic en <b>Apply</b>.</ui>
 
@@ -94,11 +94,11 @@ Configura el webhook según los pasos a continuación:
 
 <blockquote><ui>8. Haz clic en <b>Save changes</b>.</ui>
 
-![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
diff --git a/docs/tutorials/es/configuring-payment-with-adyenv3.md b/docs/tutorials/es/configuring-payment-with-adyenv3.md
index bd4d4f466..6dec40150 100644
--- a/docs/tutorials/es/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/es/configuring-payment-with-adyenv3.md
@@ -42,7 +42,7 @@ Para habilitar el acceso de VTEX en el entorno Adyen, sigue los pasos a continua
 2. En la barra lateral izquierda, copia y guarda la información descrita antes de __Company__. Esta es tu Company Account.
 3. En la lista de abajo, busca el nombre de la Merchant Account a utilizar (resaltada en blanco). Copia y guarda esta información.
 
-![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtener la Live URL
 
@@ -59,7 +59,7 @@ La información a continuación supone que la API Key y la Client Key se han gen
 2. Selecciona tu credencial API.
 3. En __Server Settings > Authentication__, selecciona __API key__. 
 
-![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Haz clic en <b>Generate Key</b> y anota la información creada en un lugar seguro.</ui>
 
@@ -67,7 +67,7 @@ La información a continuación supone que la API Key y la Client Key se han gen
 
 <blockquote><ui>6. Haz clic en <b>Generate Client Key</b> y anota la información creada en un lugar seguro.
 
-![Adyenv3_3](//images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
+![Adyenv3_3](https://images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
 
 ### Configura el webhook
 
@@ -81,7 +81,7 @@ Configura el webhook según los pasos a continuación:
 4. En __General > Description__, agrega una descripción para el nuevo webhook. Ejemplo: "Webhook Adyen Connector Provider v3".
 5. En __General > Server configuration > URL__ introduce la URL de tu cuenta VTEX. Ejemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Haz clic en <b>Apply</b>.</ui>
 
@@ -89,11 +89,11 @@ Configura el webhook según los pasos a continuación:
 
 <blockquote><ui>8. Haz clic en <b>Save changes</b>.</ui>
 
-![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
diff --git a/docs/tutorials/es/configuring-price-divergence-rule.md b/docs/tutorials/es/configuring-price-divergence-rule.md
index 251da6535..aaabe3953 100644
--- a/docs/tutorials/es/configuring-price-divergence-rule.md
+++ b/docs/tutorials/es/configuring-price-divergence-rule.md
@@ -45,13 +45,13 @@ Para crear una regla de divergencia de precios, sigue los pasos a continuación:
 
 Verás la siguiente pantalla:
 
-![print_01_ES](//images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/9f087e8080a0a18dbb9caeb890a4beae/print_01_ES.png)
+![print_01_ES](https://images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/9f087e8080a0a18dbb9caeb890a4beae/print_01_ES.png)
 
 La pestaña **Todas** muestra todas las reglas de autorización configuradas.
 
 Para crear la primera regla de autorización, haz clic en **CREAR REGLAS**. Se mostrará una nueva pestaña, llamada **1ª regla**. Al clicar en esta pestaña, aparecerán las opciones de configuración.
 
-![print_02_ES](//images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/b44238cace132525165ab84ba6eacf7c/print_02_ES.png)
+![print_02_ES](https://images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/b44238cace132525165ab84ba6eacf7c/print_02_ES.png)
 
 Para configurar la **1ª regla**, puedes aumentar o disminuir el porcentaje de divergencia arrastrando los extremos de la barra. El signo > define el inicio del intervalo y el signo < determina su fin. El intervalo elegido puede ser del 0% al 100%.
 
@@ -67,7 +67,7 @@ Para configurar una jerarquía de usuarios responsables de aprobar los pedidos,
 
 Para crear la **segunda regla**, haz clic en el `<img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" />` signo más. Lo mismo se aplica a la creación de una tercera o cuarta regla, y así en adelante. Tras hacer clic en el ícono, se mostrará la siguiente interfaz:
 
-![print_03_ES](//images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/4c61f021b61f9147dbf87ff2a68b474f/print_03_ES.png)
+![print_03_ES](https://images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/4c61f021b61f9147dbf87ff2a68b474f/print_03_ES.png)
 
 Configura la nueva regla de autorización y, después de definir todas las reglas que desees, haz clic en el botón **GUARDAR REGLAS**. Verás el siguiente mensaje: _Después de guardar las reglas, puedes editarlas o eliminarlas cuando quieras_. Haz clic en **OK** para confirmar. Una vez que hayas hecho esto, se creará la regla de divergencia de precios.
 
diff --git a/docs/tutorials/es/configuring-prices-v2.md b/docs/tutorials/es/configuring-prices-v2.md
index 23404edd0..9e93bdac1 100644
--- a/docs/tutorials/es/configuring-prices-v2.md
+++ b/docs/tutorials/es/configuring-prices-v2.md
@@ -20,7 +20,7 @@ Las funcionalidades descritas en este artículo aún no están disponibles para
 
 Se accede a las configuraciones de precios a través del botón **Configuración**, en el módulo **Precios**.
 
-![Preco24](//images.contentful.com/alneenqid6w5/5Wm20idGbCG0uKei00QQOi/5e18f35d0dd0790e5be98341c67ab4a6/Preco24.gif)
+![Preco24](https://images.contentful.com/alneenqid6w5/5Wm20idGbCG0uKei00QQOi/5e18f35d0dd0790e5be98341c67ab4a6/Preco24.gif)
 
 En esta pantalla, se puede hacer el registro del markup mínimo. Conozca en este artículo qué es el markup y como configurarlo.
 
@@ -41,4 +41,4 @@ El registro del markup mínimo, realizado en la pantalla de Configuraciones, ser
 
 El markup mínimo inicial por política comercial, es siempre cero y puede ser libremente ajustado a valores positivos o negativos.
 
-![Preco25](//images.contentful.com/alneenqid6w5/12nLR9a2AMwCeuYmmIagCI/94ff929a610a22b1fec685acfc0aec7c/Preco25.gif)
+![Preco25](https://images.contentful.com/alneenqid6w5/12nLR9a2AMwCeuYmmIagCI/94ff929a610a22b1fec685acfc0aec7c/Preco25.gif)
diff --git a/docs/tutorials/es/configuring-product-visited.md b/docs/tutorials/es/configuring-product-visited.md
index d98221244..4f641edd5 100644
--- a/docs/tutorials/es/configuring-product-visited.md
+++ b/docs/tutorials/es/configuring-product-visited.md
@@ -21,7 +21,7 @@ Tutorial válido solo para tiendas CMS Portal Legado.
 
 El producto visitado es la funcionalidad que envía emails a los clientes que navegaron por un producto en su site pero que no finalizaron compra. Ese email tiene como objetivo la recuperación de la venta, enviando, además del producto abandonado, sugerencias de nuevos productos. Todo ello es posible a través de su Master Data.
 
-[![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
+[![ExemploProdutoVisitado](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
 
 _Para que este recurso funcione de manera adecuada es necesario que su tienda tenga un alto flujo de visitas y compras, ya que los expositores se generan relacionando datos de navegación a un producto específico._
 
@@ -49,21 +49,21 @@ Haga clic en el botón **Salvar**.
 Tras crear un campo en la entidad, es necesario configurar para que el campo sea exhibido en el formulario &#8211; así, es posible ver los datos registrados en el mismo. Esto también es válido para campos que creados automáticamente por VTEX pero que no fueron marcados para ser exhibidos en el formulario. Sigue a continuación un manual sobre cómo exhibir los campos que serán importantes para el escenario de Producto Visitado.
 
 1. Acceda al módulo **Master Data**;
-2. En la aplicación **Profile System**, haga clic en el símbolo de **engrenagem**; [![aplicacaoEditar](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png "![aplicacaoEditar](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)")
+2. En la aplicación **Profile System**, haga clic en el símbolo de **engrenagem**; [![aplicacaoEditar](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png "![aplicacaoEditar](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)")
 3. Haga clic en el símbolo del **lápis** sobre el formulario **Cliente**;
 4. Haga clic en la pestaña **Schemas de Layout**;
 5. Haga clic en el botón **Incluir Nova seção**;
 6. Dele un nombre a esa sección;
-7. En la columna **Campos disponíveis **, arrastre el campo deseado hasta el área **Campos da columna 1**, abajo del nombre de la sección creada; [![arrastandoCampo](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png "![arrastandoCampo](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)") [![arrastandoCampo2](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png "![arrastandoCampo2](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)") [![seçãoCriada](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png "![seçãoCriada](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)")
+7. En la columna **Campos disponíveis **, arrastre el campo deseado hasta el área **Campos da columna 1**, abajo del nombre de la sección creada; [![arrastandoCampo](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png "![arrastandoCampo](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)") [![arrastandoCampo2](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png "![arrastandoCampo2](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)") [![seçãoCriada](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png "![seçãoCriada](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)")
 8. Haga clic en el botón **Salvar**.
 
 ### Cree el template de email
 
-El template del e-mail que será enviado, al igual que en el Carrito Abandonado, se configura en el módulo CMS. Para auxiliar en la configuración, [use nuestro template de ejemplo](//assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "use nuestro template de ejemplo").
+El template del e-mail que será enviado, al igual que en el Carrito Abandonado, se configura en el módulo CMS. Para auxiliar en la configuración, [use nuestro template de ejemplo](https://assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "use nuestro template de ejemplo").
 
 1. Acceda al módulo **CMS**;
 2. Haga clic en **Portal**;
-3. [Haga clic aquí para descargar el template de ejemplo](//assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "Clique aqui para baixar o template de exemplo");
+3. [Haga clic aquí para descargar el template de ejemplo](https://assets.contentful.com/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/bf28c1d0d7d6618d5eb1231a578934f1/produtoVisitadoExemplo.html "Clique aqui para baixar o template de exemplo");
 4. Haga clic en **Templates de página**;
 5. Haga clic en **novo template**;
 6. Llene el nombre y pegue el código de su template. ¡Atención! Si está usted usando el template de ejemplo, recuerde modificar el código `TEMPLATE_DE_EXPOSITOR` por el id de su template de expositor y el código `NOMBRE_DE_TIENDA` por la URL de su tienda.
@@ -103,7 +103,7 @@ Haga clic en el botón **Salvar Pasta**.
 Tras la creación de la carpeta, asocie el template de página al layout de la página.
 
 1. Haga clic en la carpeta creada;
-2. Haga clic en **novo layout**; [![novoLayout](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png "![novoLayout](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)")
+2. Haga clic en **novo layout**; [![novoLayout](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png "![novoLayout](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)")
 3. Seleccione el template creado anteriormente;
 4. Haga clic en el botón **Salvar**.
 
@@ -123,7 +123,7 @@ En **Filtro adicional**, configure conforme lo que sigue:
 
 Luego, haga clic en el botón **Incluir grupo**, y haga clic en **Incluir filtro** y complete como sigue:
 - **Fecha del último trigger enviado** Menor o igual `FECHA ACTUAL` &#8211; `Sustraer días` &#8211; `7` or
-- **Fecha del último trigger enviado** Está nulo [![CondicoesTrigger](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png "![CondicoesTrigger](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)")
+- **Fecha del último trigger enviado** Está nulo [![CondicoesTrigger](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png "![CondicoesTrigger](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)")
 
 Luego, siga los pasos siguientes:
 
diff --git a/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md b/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md
index 6429b0e23..caadfb233 100644
--- a/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md
+++ b/docs/tutorials/es/configuring-promotions-with-a-highlightflag.md
@@ -21,7 +21,7 @@ Tutorial válido solo para tiendas CMS Portal Legado.
 
 El destaque en la promoción es un aviso que puede ser colocado en los estantes y en las páginas de los productos, informando que el producto es elegible para una promoción. Un ejemplo muy común es una imagen debajo de la imagen del producto indicando flete gratis.
 
-![ExemploPromocaoDestaque2](//images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
+![ExemploPromocaoDestaque2](https://images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
 
 No todas las promociones son elegibles para tener destaque. Esta posibilidad está disponible para los siguientes tipos:
 - Porcentaje
@@ -66,9 +66,9 @@ Esta configuración consiste en la edición de la plantilla de la página utiliz
 9. En la ventana, haga clic en la opción **New Layout**.
 10. En el menú lateral, haga clic sobre el layout marcado con un check rojo y en el campo __template__, verifique cuál es el nombre de la plantilla utilizada.
 
-![Layout com check - PT](//images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
+![Layout com check - PT](https://images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
 
-![Template](//images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
+![Template](https://images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
 
 11. Vuelva al menú lateral y haga clic en la carpeta **HTML Templates**.
 12. Haga clic en la plantilla encontrada en @producto@.
diff --git a/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md b/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md
index 611a2cd91..dab2000bd 100644
--- a/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md
+++ b/docs/tutorials/es/configuring-pwa-in-your-store-framework-store.md
@@ -26,11 +26,11 @@ Para configurar una PWA en tu tienda, accede a Configuración de la tienda > **S
 1. Haz clic en la pestaña **PWA**.
 2. Define **Color del tema**, **Color de fondo**, y agrega el **ícono del logotipo Android (512x512, PNG)** y **el del logotipo iOS (512x512, PNG)**. Los colores deben especificarse en código hexadecimal (por ejemplo, #F71963) y los íconos deben tener un tamaño de 512x512 px y una extensión `.png`.
 
-  ![pwa-settings-1-es](//images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/b3547450cdd0b02c68e36806bf78410f/pwa-settings-1-es.png)
+  ![pwa-settings-1-es](https://images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/b3547450cdd0b02c68e36806bf78410f/pwa-settings-1-es.png)
 
 3. Desplázate hacia abajo hasta el campo **Otras configuraciones de PWA**. Haz clic en la flecha para mostrarlas.
 
-  ![pwa-settings-2-es](//images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/90ef8a3581aabdb1078872a6afcffd53/pwa-settings-2-es.png)
+  ![pwa-settings-2-es](https://images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/90ef8a3581aabdb1078872a6afcffd53/pwa-settings-2-es.png)
 
 4. En **Otras configuraciones de PWA**, rellena los campos según las directrices que se indican a continuación:
 
@@ -60,7 +60,7 @@ Para configurar una PWA en tu tienda, accede a Configuración de la tienda > **S
     - **Agregar a la pantalla de inicio**: cuando se activa, permite que la PWA la instale el usuario.
     - **Mostrar promt "Agregar a la pantalla de inicio"**: define el momento en que se le sugerirá al usuario instalar la PWA. Se puede asignar uno de los siguientes valores: En la primera visita, En el primer ítem agregado al carrito o Al finalizar la primera compra. Esta opción solo es aplicable cuando la opción **Agregar a pantalla de inicio** está activada.
 
-    ![pwa-settings-3-es](//images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/d5c70b92839c1f5ff880c00c98d93307/pwa-settings-3-es.png)
+    ![pwa-settings-3-es](https://images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/d5c70b92839c1f5ff880c00c98d93307/pwa-settings-3-es.png)
 
 5. Haz clic en `Guardar`.
 
diff --git a/docs/tutorials/es/configuring-redirects.md b/docs/tutorials/es/configuring-redirects.md
index a4f128cc9..53e9d909d 100644
--- a/docs/tutorials/es/configuring-redirects.md
+++ b/docs/tutorials/es/configuring-redirects.md
@@ -27,7 +27,7 @@ Para configurar un redireccionamiento, es necesario seguir los siguientes pasos:
 
 Debes rellenar los siguientes campos:
 
-![redirecionamentos-adminv4-ES](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
+![redirecionamentos-adminv4-ES](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/41f7ae70f06576fe650bb84d379f5288/image.png)
 
 ### Informaciones generales
 
diff --git a/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
index 57517ba93..ba3907bc6 100644
--- a/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
+++ b/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
@@ -29,15 +29,15 @@ Para asignar sellers a una determinada organización compradora sigue los pasos
 <li>En el Admin VTEX, accede a <b>Apps > Organizaciones y centros de costos B2B > Organizaciones</b>, o ingresa <b>Organizaciones</b> en la barra de búsqueda de la parte superior de la página.</li>
 <li>En la pestaña <b>Organizaciones</b>, haz clic en el nombre de la organización compradora deseada.</li>
 
-![Organizacion](//images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/998262e5b1c591ad1aa65ed5ca7f40b3/ORGANIZACOES_-_ES.jpg)
+![Organizacion](https://images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/998262e5b1c591ad1aa65ed5ca7f40b3/ORGANIZACOES_-_ES.jpg)
 
 <li>En la pestaña <b>Sellers</b>, en <b>Disponible</b>, selecciona los sellers deseados.</li>
 
-![Detalles Organización](//images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/cf1fba7aa6959bccfcb91e87a20393ef/ORGANIZACOES-DETALHES_-_ES__com_clique_.jpg)
+![Detalles Organización](https://images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/cf1fba7aa6959bccfcb91e87a20393ef/ORGANIZACOES-DETALHES_-_ES__com_clique_.jpg)
 
 <li>Haz clic en el botón <b>AGREGAR A LA ORG.</b></li>
 
-![Detalles Organización 2](//images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/1ab4089682ebc12c99c766be8de507a4/ORGANIZACOES-DETALHES2_-_ES.jpg)
+![Detalles Organización 2](https://images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/1ab4089682ebc12c99c766be8de507a4/ORGANIZACOES-DETALHES2_-_ES.jpg)
 
 <li>Haz clic en el botón <b>Guardar</b>.</li>
 
diff --git a/docs/tutorials/es/configuring-seo-in-your-store.md b/docs/tutorials/es/configuring-seo-in-your-store.md
index b4fd21a2f..bd0d44aa2 100644
--- a/docs/tutorials/es/configuring-seo-in-your-store.md
+++ b/docs/tutorials/es/configuring-seo-in-your-store.md
@@ -35,7 +35,7 @@ En todas las tiendas VTEX IO se pueden configurar estos parámetros de forma nat
   - **Metatag de descripción**: ingresa una descripción breve del contenido de la página que sea informativa y contenga palabras clave relevantes.
   - **Metatag robots**: define cómo los motores de búsqueda deben rastrear e indexar una página específica. Los valores predeterminados son `index, follow`. Para ver los otros valores compatibles con Google, consulta la [lista de reglas válidas](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag?hl=es-419#directives).
 
-  ![seo-es](//images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/614ecc04bb0994fbab579bc917aeaafa/seo-es.png)
+  ![seo-es](https://images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/614ecc04bb0994fbab579bc917aeaafa/seo-es.png)
 
 #### Faviconos
 
@@ -43,7 +43,7 @@ En todas las tiendas VTEX IO se pueden configurar estos parámetros de forma nat
 2. Haz clic en la pestaña **General**.
 3. Haz clic en **Agregar**.
 
-  ![favicon-es](//images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/1befbd1af3f398f6ef7d7bc575f32f5b/favicons-es.png)
+  ![favicon-es](https://images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/1befbd1af3f398f6ef7d7bc575f32f5b/favicons-es.png)
 
 4. Rellena la pantalla que se abre según se describe a continuación:
 
@@ -54,7 +54,7 @@ En todas las tiendas VTEX IO se pueden configurar estos parámetros de forma nat
 
     A continuación se muestra un ejemplo:
 
-    ![relacao-favicon-es](//images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/a400fa8cb893d6012d400210198b3963/relacao-favicon-es.png)
+    ![relacao-favicon-es](https://images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/a400fa8cb893d6012d400210198b3963/relacao-favicon-es.png)
 
 5. Haz clic en **Aplicar** para que la configuración se refleje en tu tienda. Esto puede demorar unos minutos.
 
diff --git a/docs/tutorials/es/configuring-shipping-promotions.md b/docs/tutorials/es/configuring-shipping-promotions.md
index 679e8684c..d50959e69 100644
--- a/docs/tutorials/es/configuring-shipping-promotions.md
+++ b/docs/tutorials/es/configuring-shipping-promotions.md
@@ -37,40 +37,40 @@ A continuación, explicamos algunos escenarios que se pueden configurar en la pl
 Si habilita la opción **Aplicar el descuento solo para la opción de envío más barata**, el descuento del flete se aplicará únicamente al valor de flete estimado más bajo. Esta opción ya aparece habilitada de manera predeterminada, pero la puede desactivar si prefiere configurar la promoción según el [Escenario 3](#escenario-3) o el [Escenario 4](escenario-4). 
 
 #### Configuración
-![Aplicar el descuento solo para la opción de envío más barata - ES](//images.contentful.com/alneenqid6w5/4dO4pM8BrIVl4r27K5xgqT/d8a5a9992eb31f05591aaf88c79f4268/image.png)
+![Aplicar el descuento solo para la opción de envío más barata - ES](https://images.contentful.com/alneenqid6w5/4dO4pM8BrIVl4r27K5xgqT/d8a5a9992eb31f05591aaf88c79f4268/image.png)
 
 #### Resultado
-![saggincaso1.2](//images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
+![saggincaso1.2](https://images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
 
 ### Escenario 2
 
 Si desactiva la opción **Aplicar el descuento solo para la opción de envío más barata**, el descuento se aplicará a todos los fletes disponibles.
 
 #### Configuración
-![Nenhum frete selecionado - ES](//images.contentful.com/alneenqid6w5/7a7lDpKd56Md9xIlJQF9tX/4a3dc46a38e0d43a3d4947af0368c191/image.png)
+![Nenhum frete selecionado - ES](https://images.contentful.com/alneenqid6w5/7a7lDpKd56Md9xIlJQF9tX/4a3dc46a38e0d43a3d4947af0368c191/image.png)
 
 #### Resultado
-![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Escenario 3
 
 Si solo habilita la opción **Tipo de carga** y selecciona los tipos de flete deseados, el descuento de flete se aplicará a todos los tipos de flete seleccionados.
 
 #### Configuración
-![Tipo de carga - ES](//images.ctfassets.net/alneenqid6w5/MkF8ImPwJ04FtN5DoJINV/e72d10be17632100b45beba4ba056d50/image.png)
+![Tipo de carga - ES](https://images.ctfassets.net/alneenqid6w5/MkF8ImPwJ04FtN5DoJINV/e72d10be17632100b45beba4ba056d50/image.png)
 
 #### Resultado
-![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Escenario 4
 
 Si habilita las opciones **Tipo de carga** y **Aplique el descuento solo cuando el cliente seleccione uno de los transportistas anteriores** y selecciona los tipos de flete deseados, el descuento de flete se aplicará a todos los tipos de flete seleccionados solamente cuando el cliente elija el tipo de flete en el checkout.
 
 #### Configuración
-![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - ES](//images.ctfassets.net/alneenqid6w5/3asUPbHRyLXbY57HqCahA0/d042659aba597af795a1c6e1ae5ede4e/image.png)
+![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - ES](https://images.ctfassets.net/alneenqid6w5/3asUPbHRyLXbY57HqCahA0/d042659aba597af795a1c6e1ae5ede4e/image.png)
 
 #### Resultado
-![saggincaso3.2](//images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
+![saggincaso3.2](https://images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
 
 En resumen, la casilla **Aplique el descuento solo cuando el cliente seleccione uno de los transportistas anteriores** se utiliza para aplicar el descuento solamente cuando se selecciona la transportadora.
 
diff --git a/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
index cbddd5779..a6ae4697d 100644
--- a/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
+++ b/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
@@ -56,7 +56,7 @@ Después de registrarte en Apple, debes activar la opción de inicio de sesión
 
     Para más información sobre cómo obtener estas credenciales, consulta nuestra guía para desarrolladores [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login).
 
-    ![apple-id-setup-es](//images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/83719fc4ecc831b785e06d485eb13188/apple-id-setup-pt.png)
+    ![apple-id-setup-es](https://images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/83719fc4ecc831b785e06d485eb13188/apple-id-setup-pt.png)
 
 5. Haz clic en `Guardar`.
 6. Haz clic en `Proveedores de tienda virtual` para volver a la página anterior.
diff --git a/docs/tutorials/es/configuring-the-marketplace-between-vtex-stores.md b/docs/tutorials/es/configuring-the-marketplace-between-vtex-stores.md
index dd399ee63..567d0c456 100644
--- a/docs/tutorials/es/configuring-the-marketplace-between-vtex-stores.md
+++ b/docs/tutorials/es/configuring-the-marketplace-between-vtex-stores.md
@@ -36,7 +36,7 @@ Después de las configuraciones, es necesario realizar la indexación de todos l
 1. Con el [usuario titular](https://help.vtex.com/es/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA), acceda al link `{nombredelatienda}.vtexcommercestable.com.br/admin/Site/FullCleanUp.aspx`.
 2. Haga clic en el botón __Reindexar Base__.
 
-[![ReindexarBase](//images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)](//images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png "![ReindexarBase](//images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)")
+[![ReindexarBase](https://images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)](https://images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png "![ReindexarBase](https://images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)")
 
 Tenga en cuenta que, en la URL, debe cambiar el término `{nombredelatienda}` por el nombre de su tienda.
 
diff --git a/docs/tutorials/es/configuring-the-past-prices-control.md b/docs/tutorials/es/configuring-the-past-prices-control.md
index 4454a35f6..fcd27c3cd 100644
--- a/docs/tutorials/es/configuring-the-past-prices-control.md
+++ b/docs/tutorials/es/configuring-the-past-prices-control.md
@@ -33,7 +33,7 @@ Vea [aqui](http://help.vtex.com/tutorial/lista-de-controles-para-templates/ "aqu
 
 El modo de exhibición standard de los valores sigue el modelo de la imagen debajo. Se muestran de manera continuada el año, el mes y el menor valor facturado en este mes.
 
-![HistPrecos](//images.contentful.com/alneenqid6w5/2AX7uKU4zW66sA0AICcEM2/81042cedd7d0ef937b1c56a8878d8d0c/HistPrecos.png)
+![HistPrecos](https://images.contentful.com/alneenqid6w5/2AX7uKU4zW66sA0AICcEM2/81042cedd7d0ef937b1c56a8878d8d0c/HistPrecos.png)
 
 En el caso de que la tienda desee exhibir los datos de otra manera, será necesario realizar la customización a través de una agencia de layout.
 
diff --git a/docs/tutorials/es/configuring-the-pickup-in-store.md b/docs/tutorials/es/configuring-the-pickup-in-store.md
index 1ad2ecc19..60f20fb0f 100644
--- a/docs/tutorials/es/configuring-the-pickup-in-store.md
+++ b/docs/tutorials/es/configuring-the-pickup-in-store.md
@@ -28,17 +28,17 @@ La configuración de retirada en la tienda permite que el cliente opte por no re
 3. Para esas transportadores, se recomienda que no se cobre valor de flete.
 4. Una vez creadas todas las transportadoras, es necesario crear una transportadora con el nombre genérico de _Retirada no local _la que será usada en la programación del front-end de la tienda (en la opción de selección de flete).
 
-![](//images.contentful.com/alneenqid6w5/1aPl4HkPD8IagOICkCuigu/185dffc5b9bfd322697b6bf7ae0e7942/1.jpg)
+![](https://images.contentful.com/alneenqid6w5/1aPl4HkPD8IagOICkCuigu/185dffc5b9bfd322697b6bf7ae0e7942/1.jpg)
 
 ## Customización visual (Front-end)
 
 Deberá implementarse un archivo _javascript_ en el checkout de la tienda, de acuerdo a las orientaciones abajo.
 
 1. El usuario hará la compra normal de los productos hasta la página de checkout.
-2. Después de rellenar los datos personales, el usuario llega al área de selección de la transportadora. El comportamiento normal de la herramienta es el de presentar todas las transportadoras disponibles configuradas. Por lo tanto, después de configurarlas, el _javascript_ deberá “esconder” las opciones de las tiendas disponibles y presentar solo la transportadora genérica que fue creada en el punto 4 arriba llamada de **Retirada en Sucursal**.![OpcoesdeEnvio](//images.contentful.com/alneenqid6w5/3YpLqm1q2ckOm4i4g8KWAQ/edc9d9ff1e32352306c1b152c12997e7/OpcoesdeEnvio.png)
-3. Cuando el usuario seleccione la opción retirada en sucursal, el _javascript _abre un _lightbox _presentando en la pantalla las opciones de tiendas para que el usuario seleccione. Las opciones que aparecen aquí son las transportadoras registradas en el admin en los pasos 1 y 2. La imagen abajo muestra cómo optó la tienda por presentar visualmente la selección de las tiendas para retirada.![](//images.contentful.com/alneenqid6w5/XZ0kevBW6sEK2sGKsYsGm/84c5681cf6c9cf923e90d337d3a727d8/3.jpg)
-4. Cuando el usuario elige alguna de las opciones, el _javascript _cierra el_ lightbox_ y vuelve_ a_ la opción de selección de flete, informando que la selección se grabó con éxito.![](//assets.contentful.com/alneenqid6w5/4ekRwP5Hy0yE8ckaWGCAQG/b358a05721f4ce0cc0221fd6eb0ff955/4.bmp)
-5. Después de esa vuelta a selección, el _javascript _debe modificar la opción de entrega genérica por la opción real de la tienda registrada, ésta que hasta el momento no estaba visible en el front-end.![](//images.contentful.com/alneenqid6w5/3DlztWQIEUOqoomMeA8yiq/15f3ffa1fe1a10d004ab0c13938ec7fe/5.jpg)
+2. Después de rellenar los datos personales, el usuario llega al área de selección de la transportadora. El comportamiento normal de la herramienta es el de presentar todas las transportadoras disponibles configuradas. Por lo tanto, después de configurarlas, el _javascript_ deberá “esconder” las opciones de las tiendas disponibles y presentar solo la transportadora genérica que fue creada en el punto 4 arriba llamada de **Retirada en Sucursal**.![OpcoesdeEnvio](https://images.contentful.com/alneenqid6w5/3YpLqm1q2ckOm4i4g8KWAQ/edc9d9ff1e32352306c1b152c12997e7/OpcoesdeEnvio.png)
+3. Cuando el usuario seleccione la opción retirada en sucursal, el _javascript _abre un _lightbox _presentando en la pantalla las opciones de tiendas para que el usuario seleccione. Las opciones que aparecen aquí son las transportadoras registradas en el admin en los pasos 1 y 2. La imagen abajo muestra cómo optó la tienda por presentar visualmente la selección de las tiendas para retirada.![](https://images.contentful.com/alneenqid6w5/XZ0kevBW6sEK2sGKsYsGm/84c5681cf6c9cf923e90d337d3a727d8/3.jpg)
+4. Cuando el usuario elige alguna de las opciones, el _javascript _cierra el_ lightbox_ y vuelve_ a_ la opción de selección de flete, informando que la selección se grabó con éxito.![](https://assets.contentful.com/alneenqid6w5/4ekRwP5Hy0yE8ckaWGCAQG/b358a05721f4ce0cc0221fd6eb0ff955/4.bmp)
+5. Después de esa vuelta a selección, el _javascript _debe modificar la opción de entrega genérica por la opción real de la tienda registrada, ésta que hasta el momento no estaba visible en el front-end.![](https://images.contentful.com/alneenqid6w5/3DlztWQIEUOqoomMeA8yiq/15f3ffa1fe1a10d004ab0c13938ec7fe/5.jpg)
 6. Después de esa área de selección, el cliente sigue el flujo normal de compra.
 
 _Inserte una leyenda informando en cuántos el pedido estará disponible para búsqueda en la tienda física._
@@ -47,6 +47,6 @@ _Inserte una leyenda informando en cuántos el pedido estará disponible para b
 
 En el OMS será posible visualizar el pedido del cliente, en el que aparecerá cuál tienda seleccionó él para retirar el pedido. Esa información la puede encontrar en el área donde se presentan los productos.
 
-![](//images.contentful.com/alneenqid6w5/5LIVnwfutq826ciMOOcmUQ/6b1e5180ff186b6199460eb0d7a456c2/6.jpg)
+![](https://images.contentful.com/alneenqid6w5/5LIVnwfutq826ciMOOcmUQ/6b1e5180ff186b6199460eb0d7a456c2/6.jpg)
 
 ¡Recuerde! El javascript necesario para este escenario debe ser desarrollado por el equipo de desarrollo de la tienda o por uno de nuestros [asociado acreditado](http://store.vtex.com/ "asociado acreditado").
diff --git a/docs/tutorials/es/configuring-the-scheduled-delivery.md b/docs/tutorials/es/configuring-the-scheduled-delivery.md
index 02792acac..eb1a73936 100644
--- a/docs/tutorials/es/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/es/configuring-the-scheduled-delivery.md
@@ -29,7 +29,7 @@ En **Inventario y envío**, acceda **Paneles** y haga clic en la **Transportador
 
 En **Tipo de Entrega**, haga clic en **Entrega agendada**.
 
-![entrega-agendada es](//images.ctfassets.net/alneenqid6w5/PF5fC5oPoiAmsK0KAW2G2/aee508bb7392ef5c0dfd62d3a607f25d/entrega-agendada_es.png)
+![entrega-agendada es](https://images.ctfassets.net/alneenqid6w5/PF5fC5oPoiAmsK0KAW2G2/aee508bb7392ef5c0dfd62d3a607f25d/entrega-agendada_es.png)
 Para compreender mejor sobre la cumplimentación del resto de los campos, vea también nuestro documento de cómo [registrar una transportadora](http://help.vtex.com/es/tutorial/gestionar-transportista).
 
 
@@ -44,7 +44,7 @@ En esta estructura, tenemos los siguientes datos:
 Utilizando igual ejemplo de la tienda más arriba, sigue la configuración de la transportadora según su demanda:
 
 
-![entrega-agendada-exemplo es](//images.ctfassets.net/alneenqid6w5/1kwunX9pCYUUQUSQ8QO42u/bab6a450319e8ddcd081db0aebb9b9fe/entrega-agendada-exemplo_es.png)
+![entrega-agendada-exemplo es](https://images.ctfassets.net/alneenqid6w5/1kwunX9pCYUUQUSQ8QO42u/bab6a450319e8ddcd081db0aebb9b9fe/entrega-agendada-exemplo_es.png)
 
 
 Suponiendo que el Inventario tiene 2 días de plazo, el Muelle 1 día y la Tabla de Flete 5 días, el primer día que se pondrá a disposición será 8 días después de la fecha en que se está realizando el pedido y cómo el Tiempo máximo de entrega es de 10 días, el último día disponible para la elección será el 18º día después de la fecha en que se está efectuando el pedido.
diff --git a/docs/tutorials/es/configuring-the-store-domain.md b/docs/tutorials/es/configuring-the-store-domain.md
index e56035df4..d0dd91f88 100644
--- a/docs/tutorials/es/configuring-the-store-domain.md
+++ b/docs/tutorials/es/configuring-the-store-domain.md
@@ -26,7 +26,7 @@ La configuración relacionada con el dominio es necesaria para que una direcció
 
  La dirección de la tienda se compone de los elementos ilustrados a continuación:
 
-![url-diagram-es](//images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/70d9e55fc1f035bfb1b8733aa0cfdec4/url-diagram-es.png)
+![url-diagram-es](https://images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/70d9e55fc1f035bfb1b8733aa0cfdec4/url-diagram-es.png)
 
 | Elemento | Descripción | Ejemplo |
 |---|---|---|
diff --git a/docs/tutorials/es/configuring-your-layout.md b/docs/tutorials/es/configuring-your-layout.md
index c64ab3978..de6839cb3 100644
--- a/docs/tutorials/es/configuring-your-layout.md
+++ b/docs/tutorials/es/configuring-your-layout.md
@@ -21,5 +21,5 @@ Si la tienda no tiene equipo de desarrolladores front-end, le recomendamos que
 
 _El video presentado en este tutorial aún no se ha traducido al español. Estamos trabajando para ofrecer más contenido en español. Gracias por la comprensión._
 
-<video class="wp-video-shortcode" id="video-2571-5" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4?_=5" />[//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4](//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4 "//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4")</video>
+<video class="wp-video-shortcode" id="video-2571-5" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4?_=5" />[//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4](https://downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4 "//downloads.contentful.com/alneenqid6w5/2J4oMfae0UoMw6QGKqc466/ddf5f15cb2d4d52e0a0b4f85c033c594/Portal-CMS.mp4")</video>
 
diff --git a/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md b/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md
index 3b474b6ed..82d6fcde6 100644
--- a/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md
+++ b/docs/tutorials/es/copying-a-layout-from-one-web-site-to-another.md
@@ -25,10 +25,10 @@ Para ello, en el Admin VTEX, accede a **Storefront > Layout > CMS** y hacer clic
 
 El botón se encuentra en la esquina superior derecha, como se muestra en la siguiente imagen.
 
-!![copiar layout](//images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
+!![copiar layout](https://images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
 
 El sistema le preguntará a qué web site desea copiar el layout.
 
 Seleccione el web site y haga clic en __Copiar Layout__.
 
-![copyLayout2](//images.contentful.com/alneenqid6w5/1KPGgtczwMmKEeQKOM44yk/3e74ac50ac9a0fbe89f0de3fbd4a4d7a/copyLayout2.png)
+![copyLayout2](https://images.contentful.com/alneenqid6w5/1KPGgtczwMmKEeQKOM44yk/3e74ac50ac9a0fbe89f0de3fbd4a4d7a/copyLayout2.png)
diff --git a/docs/tutorials/es/coupons-list-beta.md b/docs/tutorials/es/coupons-list-beta.md
index 226ba7dd4..01ad690e7 100644
--- a/docs/tutorials/es/coupons-list-beta.md
+++ b/docs/tutorials/es/coupons-list-beta.md
@@ -31,7 +31,7 @@ Desde esta página puedes:
 
 Para acceder a la página desde el Admin VTEX, haz clic en **Promociones > Cupones**.
 
-![lista-cupons](//images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/1526330ae6f09ee70d1250a5c6ac0082/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_13_40_1.png)
+![lista-cupons](https://images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/1526330ae6f09ee70d1250a5c6ac0082/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-29-18_13_40_1.png)
 
 Luego, verás la descripción de las acciones y los componentes incluidos en la página.
 
@@ -83,7 +83,7 @@ El archivo que se genera contiene la siguiente información:
 
 A continuación, puedes ver un ejemplo del archivo CSV exportado:
 
-![cupons-exportados](//images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
+![cupons-exportados](https://images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
 
 #### Exportar códigos del lote de cupones
 
@@ -100,13 +100,13 @@ Para ver o exportar todos los códigos de un lote de cupones, sigue los pasos a
     * <i class="far fa-clone"></i> **Copiar todos:** permite copiar los códigos generados a su área de transferencia. También puedes copiar cada código haciendo clic sobre él.
     * **Exportar:** permite exportar los códigos generados a un archivo CSV. El archivo exportado tiene una columna con un código por línea.
 
-![exportar-cupones](//images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/e41e4a9922531597949431314c41ed5d/image_6.png)
+![exportar-cupones](https://images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/e41e4a9922531597949431314c41ed5d/image_6.png)
 
 ### Ver uso de cupones
 
 Para ver el total de los cupones activos y el espacio disponible restante para los cupones nuevos, haz clic en <i class="fas fa-chart-line"></i> `Uso de los cupones`.
 
-![uso-de-cupones](//images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/0ed73731ce39d27daf747bae02757a81/image_9.png)
+![uso-de-cupones](https://images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/0ed73731ce39d27daf747bae02757a81/image_9.png)
 
 La cantidad máxima de cupones activos que puedes tener es de 5000. Para liberar espacio, puedes archivar cupones desde la [Lista de cupones](#lista-de-cupones). Si necesitas aumentar el límite de los cupones activos, ponte en contacto con [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
@@ -155,13 +155,13 @@ La ventana **Ver detalles de uso** muestra los datos de uso de cada cupón, que
 
     Esta sección muestra la lista de pedidos en que se usó el cupón y permite buscar por número de pedido. Al hacer clic en el número de un pedido, serás redirigido a la página de detalles del pedido en **Gestión de pedidos**.
 
-![ver-detalles-de-uso](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
+![ver-detalles-de-uso](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
 
 * **Uso general de códigos de cupon** (lotes de cupones): muestra la cantidad total de usos de los códigos de un grupo de cupones y la cantidad de usos restantes, si ha limitado la cantidad de usos.
 
     Esta sección también muestra la lista de códigos en el lote de cupones y le permite buscar un código específico. Al hacer clic en un código, se accede a la lista de pedidos en los que se ha utilizado el código y se puede buscar por un número de pedido. Al hacer clic en un número de pedido, accederá a la página de detalles del pedido en **Gestión de pedidos**.
 
-![selecciona-el-codigo-lotes-cupones](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
+![selecciona-el-codigo-lotes-cupones](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
 
 ## Más información
 
diff --git a/docs/tutorials/es/create-a-talk-to-us-form-using-master-data.md b/docs/tutorials/es/create-a-talk-to-us-form-using-master-data.md
index e3a513df3..79d278c22 100644
--- a/docs/tutorials/es/create-a-talk-to-us-form-using-master-data.md
+++ b/docs/tutorials/es/create-a-talk-to-us-form-using-master-data.md
@@ -117,6 +117,6 @@ El plugin fue desarrollado para facilitar la instalación del formulario en el t
 - jQuery
 - Bootstrap
 
-[Para más detalles, acceda al ejemplo en anexo](//assets.contentful.com/alneenqid6w5/4rfOv1xQoEuwWYS0sq24QM/3099aa480d85a9ca4d2ce50dfef64a68/contactMasterData.zip "Para más detalles, acceda al ejemplo en anexo").
+[Para más detalles, acceda al ejemplo en anexo](https://assets.contentful.com/alneenqid6w5/4rfOv1xQoEuwWYS0sq24QM/3099aa480d85a9ca4d2ce50dfef64a68/contactMasterData.zip "Para más detalles, acceda al ejemplo en anexo").
 
 __Importante__: Este plugin fue desarrollado para ayudar a desarrollar el formulario de Contáctenos usando Master Data. VTEX **NO** ofrece soporte a esa extensión y su código es abierto, pudendo sufrir modificaciones y adaptaciones.
diff --git a/docs/tutorials/es/creating-a-campaign-audience.md b/docs/tutorials/es/creating-a-campaign-audience.md
index e632caa58..3f3f54936 100644
--- a/docs/tutorials/es/creating-a-campaign-audience.md
+++ b/docs/tutorials/es/creating-a-campaign-audience.md
@@ -69,7 +69,7 @@ Luego de hacer clic en `Crear nuevo público-objetivo`, debes seguir las instruc
     * **o:** la audiencia de campaña estará compuesta por clientes que encajen en cualquiera de los públicos-objetivo.
     * **y:** la audiencia de campaña estará compuesta por clientes que encajen en todos los públicos-objetivo y sumen todos sus criterio
 
-![publico-alvo-e-ou-es](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
+![publico-alvo-e-ou-es](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/a3b67e255c3d65380455c6baeae20ad8/es-publico-alvo.gif)
 
 ### Define a tu público-objetivo
 
@@ -85,7 +85,7 @@ Luego de hacer clic en `Crear nuevo público-objetivo`, debes seguir las instruc
 
 Ejemplo: en la imagen a continuación, los ítems cuya marca es **Nike** forman parte del público-objetivo. La configuración también indica que, al menos, 3 ítems deben cumplir con estos criterios. Por ende, un cliente debe tener en el carrito al menos **3** ítems que cumplan con estos criterios para ser parte del público-objetivo.
 
-![exemplo-marca-publico-alvo-es](//images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7f6a8b503e122d865d8c0f6ae78a6c4e/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_02_43_1__1_.png)
+![exemplo-marca-publico-alvo-es](https://images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/7f6a8b503e122d865d8c0f6ae78a6c4e/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_02_43_1__1_.png)
 
 ### Condiciones para que se aplique tu público-objetivo
 
diff --git a/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md b/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
index d6ea23aec..ccbcc5990 100644
--- a/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
+++ b/docs/tutorials/es/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
@@ -21,7 +21,7 @@ Si su cliente final compra un producto en cualquiera de sus canales (en línea o
 
 Sin embargo, usted puede preferir que esa tienda funcione como un punto de recogida __ incluso si no tiene stock__. Para esto, su logística necesita asegurar que el producto llegará a esa tienda desde otro stock, por ejemplo, desde el stock del comercio electrónico. En este caso, necesita tener una política de envío en el comercio electrónico en el que esté configurado el punto de recogida de la tienda física.
 
-![Crear punto de retiro de contingencia para garantizarlo como opción en checkout](//images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/aebc9c8a6dded36f5b31496626099186/diagrama-como-criar-um-ponto-de_contigencia-es.jpg)
+![Crear punto de retiro de contingencia para garantizarlo como opción en checkout](https://images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/aebc9c8a6dded36f5b31496626099186/diagrama-como-criar-um-ponto-de_contigencia-es.jpg)
 
 ## Cómo implementar un punto de recogida de contingencia
 
diff --git a/docs/tutorials/es/creating-a-coupon-beta.md b/docs/tutorials/es/creating-a-coupon-beta.md
index eead12525..76e4d11dc 100644
--- a/docs/tutorials/es/creating-a-coupon-beta.md
+++ b/docs/tutorials/es/creating-a-coupon-beta.md
@@ -40,7 +40,7 @@ El formulario para crear o editar un cupón consta de las siguientes secciones:
 
 El panel superior del formulario de creación y edición del cupón, ilustrado a continuación, muestra el número de usos del cupón y el número de promociones vinculadas a él.
 
-![crear-cupon-1](//images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/e17457a01186b62c3b011796d0167c67/crear-cupon-1.png)
+![crear-cupon-1](https://images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/e17457a01186b62c3b011796d0167c67/crear-cupon-1.png)
 
 Al hacer clic sobre cualquier información del panel, tendrás acceso a la ventana __Ver detalles de uso__, donde aparecen los datos que se describen a continuación.
 
@@ -52,11 +52,11 @@ Al hacer clic sobre cualquier información del panel, tendrás acceso a la venta
 
     Si el cupón es sencillo, Esta sección muestra la lista de pedidos en que se usó el cupón y permite buscar por número de pedido. Al hacer clic en el número de un pedido, serás redirigido a la página de detalles del pedido en **Gestión de pedidos**.
 
-    ![ver-detalles-de-uso](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
+    ![ver-detalles-de-uso](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/5ce20bfb2a8105f006dc649682b5221a/ver-detalles-de-uso.png)
 
     Si se trata de un grupo de cupones, esta sección muestra la lista de códigos del grupo de cupones y permite buscar un código específico. Al hacer clic en un código, se accede a la lista de pedidos en los que se ha utilizado el código y se puede buscar un número de pedido. Al hacer clic en un número de pedido, accederá a la página de detalles del pedido en **Gestión de pedidos**.
 
-![selecciona-el-codigo-lotes-cupones](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
+![selecciona-el-codigo-lotes-cupones](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/7ea64df31330da8be8002f373451f262/selecione-o-codigo-grupo-es.PNG)
 
 ### General
 
@@ -92,7 +92,7 @@ Si creaste un [lote de cupones](https://help.vtex.com/es/tutorial/cupones-beta--
 * <i class="far fa-clone"></i> **Copiar todos:** permite copiar los códigos generados a su área de transferencia. Luego, si lo deseas, puedes pegarlos en un editor de planillas como Excel o Google Sheets. También puedes copiar cada código haciendo clic sobre él.
 * **Exportar:** permite exportar los códigos generados a un archivo CSV. El archivo exportado tiene una columna con un código por línea.
 
-![cupons-gerados-es](//images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/8e8d4674d5df0558a76a9c3b1bc72af6/cupons-gerados-es.gif)
+![cupons-gerados-es](https://images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/8e8d4674d5df0558a76a9c3b1bc72af6/cupons-gerados-es.gif)
 
 ## Asociar el cupón con una promoción
 
diff --git a/docs/tutorials/es/creating-a-form-to-record-information-using-master-data-newsletter.md b/docs/tutorials/es/creating-a-form-to-record-information-using-master-data-newsletter.md
index fb2238dca..cf8a05c36 100644
--- a/docs/tutorials/es/creating-a-form-to-record-information-using-master-data-newsletter.md
+++ b/docs/tutorials/es/creating-a-form-to-record-information-using-master-data-newsletter.md
@@ -30,6 +30,6 @@ Luego de haber realizado las configuraciones anteriores, es necesario incluir en
  
 En este enlace podrán encontrar un ejemplo de un HTML y JS que sirve de guía para la implementación en el CMS.
  
-[Código de ejemplo](//assets.contentful.com/alneenqid6w5/xC0HA56uzIO8Ueca2c02g/eb126bee0a1618dff60da75c997a85e2/newsletterMasterData.rar).
+[Código de ejemplo](https://assets.contentful.com/alneenqid6w5/xC0HA56uzIO8Ueca2c02g/eb126bee0a1618dff60da75c997a85e2/newsletterMasterData.rar).
  
 IMPORTANTE: Este plugin fue desarrollado para ayudar a desarrollar un formulario básico usando Master Data (MD). VTEX NO ofrece soporte a esa extensión y su código es abierto, pudiendo sufrir modificaciones y adaptaciones.
diff --git a/docs/tutorials/es/creating-a-more-for-less-promotion.md b/docs/tutorials/es/creating-a-more-for-less-promotion.md
index 734fcc06c..955cbe4d9 100644
--- a/docs/tutorials/es/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/es/creating-a-more-for-less-promotion.md
@@ -51,7 +51,7 @@ En esta sección se proporciona información detallada sobre los datos generales
 - **Información adicional (opcional):** permite incluir en la promoción información adicional compuesta por un nombre y un valor.
 - **Promoción resaltada:** inserta una tag con el nombre de la promoción utilizada en la vitrina y en la página del producto. La tag solo se inserta si se utiliza el control de visualización de promociones correcto en la plantilla: `<vtex.cmc:discountHightLight/>`. Campo obligatorio.
 
-![Dados gerais 1 - ES](//images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/9a0848ea2c4741f7fbba52db0138e7fb/Dados_gerais_1_-_ES.png)
+![Dados gerais 1 - ES](https://images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/9a0848ea2c4741f7fbba52db0138e7fb/Dados_gerais_1_-_ES.png)
 
 ### Restringir esta promoción a los productos de los sellers
 
@@ -66,7 +66,7 @@ Para que la promoción sea válida para todos los sellers, deja la selección si
   <p>No es posible seleccionar directamente un <i>seller white label</i>. Hay dos opciones para incluir un <i>seller white label</i> en la promoción: </p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de tu tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir todos los <i>sellers</i>. En este caso, todos los tipos de <i>sellers, white label</i> y otros, se agregan a la promoción.</ol>
 </div>
 
-![Restringir - ES](//images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/709b4d87b04c6bcdb845f948e27f46ed/Restringir_-_ES.png)
+![Restringir - ES](https://images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/709b4d87b04c6bcdb845f948e27f46ed/Restringir_-_ES.png)
 
 ### Política comercial
 
@@ -79,7 +79,7 @@ Esta sección establece las políticas comerciales válidas para la promoción.
 
 Para que la promoción sea válida en todas las políticas comerciales, deja la selección sin marcar.
 
-![Politica - ES](//images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/df186b6fa5750448e15cf7cae1e5c2bf/Politica_-_ES.png)
+![Politica - ES](https://images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/df186b6fa5750448e15cf7cae1e5c2bf/Politica_-_ES.png)
 
 ## 2. Más por Menos
 
@@ -97,7 +97,7 @@ En esta sección se definen los productos, la cantidad y el descuento que serán
     - **Con un descuento de:**  el cliente se llevará la cantidad seleccionada de productos con un descuento porcentual definido en el campo.
     - **Con un precio máximo por ítem de:**  el cliente se llevará la cantidad seleccionada de productos con un precio máximo por ítem definido en el campo.
 
-![Leve Mais -ES](//images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/c765ca884eede6552e6f29c55e25aa8c/Leva_Mais_-_ES.png)
+![Leve Mais -ES](https://images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/c765ca884eede6552e6f29c55e25aa8c/Leva_Mais_-_ES.png)
 
 ### Configuración avanzada
 En esta sección puede especificar la aplicación del descuento.
@@ -110,7 +110,7 @@ Se debe aplicar el descuento:
         - **Los productos más baratos:** el descuento se aplicará a los ítems más baratos de la promoción.
         - **Los productos más caros:** el descuento se aplicará a los ítems más caros de la promoción.
 
-![Leve Mais por menos - ES](//images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/676669ab0baa7690e4097ad39325bb66/Leve_Mais_por_menos_-_ES.png)
+![Leve Mais por menos - ES](https://images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/676669ab0baa7690e4097ad39325bb66/Leve_Mais_por_menos_-_ES.png)
 
 #### ¿Cómo debe distribuirse el descuento?
 
@@ -134,7 +134,7 @@ En esta sección se proporciona información detallada sobre las condiciones que
   <p> El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con <a href="https://support.vtex.com/hc/es-419/requests">nuestro equipo de soporte</a>.</p>
  </div>
 
- ![Condições de promoção - ES](//images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/13714c02ac6369e9274f4045af6b208b/Condi__es_de_promo__o_-_ES.png)
+ ![Condições de promoção - ES](https://images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/13714c02ac6369e9274f4045af6b208b/Condi__es_de_promo__o_-_ES.png)
 
  ## 4. Restricciones y limitaciones de uso
 
@@ -146,5 +146,5 @@ En esta sección se proporciona información detallada sobre las condiciones que
 - **Aplicar con otras promociones:** permite que se conceda más de una promoción al mismo tiempo sin importar el tipo de descuento. Aprende más sobre cómo [funciona la competencia de promociones](https://help.vtex.com/es/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270#).
 - **Aplicar con precios manuales:** permite aplicar la promoción a productos cuyos precios hayan sido ingresados manualmente por el agente de televentas. Para activar la funcionalidad de precios manuales, utiliza el endpoint [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
 
-![Restrições e limitações - ES](//images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/4c29419ba1d3639afcf175d3639b5ee2/Restri__es_e_limita__es_-_ES.png)
+![Restrições e limitações - ES](https://images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/4c29419ba1d3639afcf175d3639b5ee2/Restri__es_e_limita__es_-_ES.png)
 
diff --git a/docs/tutorials/es/creating-a-personalized-master-data-query.md b/docs/tutorials/es/creating-a-personalized-master-data-query.md
index 7965c5d94..5eeef7e35 100644
--- a/docs/tutorials/es/creating-a-personalized-master-data-query.md
+++ b/docs/tutorials/es/creating-a-personalized-master-data-query.md
@@ -19,15 +19,15 @@ Consulta customizada es un filtro o un conjunto de filtros que, para serem utili
 
 Para crear una consulta, se hace necesario que [sea realizado un filtro en el listado](/es/tutorial/filtrar-datos-en-el-master-data). Luego de filtrar, _hacer click en el botón **Salvar Consulta** (Guardar Consulta) -> poner un nombre para su consulta -> hacer click en el botón **Salvar** (Guardar)_.
 
-![image00(3)](//images.contentful.com/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/6698a619ebf6041e828b61ef657ceb89/image003.png)
+![image00(3)](https://images.contentful.com/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/6698a619ebf6041e828b61ef657ceb89/image003.png)
 
 Luego, para que la consulta aparezca como una opción de visualización en el listado, hay que recargar la aplicación, en la pestaña **Aplicações**. Haciendo click en el botón **Recarregar aplicações**.
 
-![image02(2)](//images.contentful.com/alneenqid6w5/23qCsgXVSYQYmsS6Ya6eAs/99c65c0009dd7f9e75c1ba4a2cea50cc/image022.png)
+![image02(2)](https://images.contentful.com/alneenqid6w5/23qCsgXVSYQYmsS6Ya6eAs/99c65c0009dd7f9e75c1ba4a2cea50cc/image022.png)
 
 Además de eso, es posible ver todas las consultas guardadas haciendo click en el botón **Consultas**, en el listado del form.
 
-![consulta3](//images.contentful.com/alneenqid6w5/4h0zjZuAc8W8eUaqImo2qg/b1c06c13603d398d1f83bef9f7deb19b/image012.png)
+![consulta3](https://images.contentful.com/alneenqid6w5/4h0zjZuAc8W8eUaqImo2qg/b1c06c13603d398d1f83bef9f7deb19b/image012.png)
 
 También es importante configurar un form para que él siempre te traiga el listado de filtros de consulta. Para eso, ver el paso a paso abajo:
 
@@ -38,4 +38,4 @@ También es importante configurar un form para que él siempre te traiga el list
 5. En la opción **Consulta Padrão**, seleccione la consulta customizada que desea exibir siempre que ingresar en el form.
 6. Hacer click en el botón **Salvar**.
 
-![consulta5](//images.contentful.com/alneenqid6w5/66y0WU112osUwkwuyMquMW/a9143a8ca1aa05bc49cc69d1dd102002/image032.png)
+![consulta5](https://images.contentful.com/alneenqid6w5/66y0WU112osUwkwuyMquMW/a9143a8ca1aa05bc49cc69d1dd102002/image032.png)
diff --git a/docs/tutorials/es/creating-a-product-collection.md b/docs/tutorials/es/creating-a-product-collection.md
index 8c647e907..a04b7816d 100644
--- a/docs/tutorials/es/creating-a-product-collection.md
+++ b/docs/tutorials/es/creating-a-product-collection.md
@@ -25,7 +25,7 @@ Para crear una colección, siga las siguientes instrucciones:
 2. Haga clic en **Layout**.
 3. Haga clic en **Product Clusters (Collections)**.
 4. Haga clic en el botón `new collection`, como se muestra a continuación.
-	![Layout 4](//images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
+	![Layout 4](https://images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
 5. Rellene la información requerida:
 	- **Product Cluster Id:** código identificador de la colección. Este campo no debe rellenarse ya que el sistema lo genera automáticamente al guardar.
 	- **Nombre:** nombre de la colección.
@@ -49,17 +49,17 @@ Cada grupo puede ser de uno de los siguientes tipos: __Inclusión__ o __Exclusi
 
 Para crear el Grupo, basta hacer clic en el botón _new group_ como en el ejemplo de la imagen abajo.
 
-![Layout 5](//images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
+![Layout 5](https://images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
 
 Para agregar todos los productos de un determinado Departamento a un grupo, basta con seleccionar el Departamento en cuestión, como indica el ítem 1 de la figura a seguir. Lo mismo se aplica a los productos de una determinada Categoría (ítem 2) o subcategoría (ítem 3).
 
-![Filtro_por_categoria](//images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
+![Filtro_por_categoria](https://images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
 
 ### Crear Grupo por Marca
 
 Para crear un grupo con productos de una o más marcas, basta con seleccionar la marca deseada en la lista correspondiente. Las marcas se encuentran dispuestas en orden alfabética y al hacer clic en la letra correspondiente a la inicial de la marca, la lista se despliega y exhibe las marcas existentes.
 
-![FIltro_por_marca](//images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
+![FIltro_por_marca](https://images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
 
 ### Definir Grupo por productos en preventa o en periodo de lanzamiento
 
@@ -73,15 +73,15 @@ Estas opcciones son un <em>complemento</ em> a la elección de los productos. Es
 
 Al contrario de la versión anterior, en la que la inclusión de productos específicos se hacía a partir del ID del Producto, en el nuevo módulo, las inclusiones manuales se hacen usándose el SKU de un producto. En el campo correspondiente es posible digitar el ID de un SKU o de varios, separando los valores con una coma. Ej: `2000004,2000009,2000005`. Pese a la diferencia en la forma del registro, en la práctica, el efecto será el mismo, ya que al asociar un SKU a un grupo, el producto “padre” de este también será agregado a la colección. En caso que un producto tenga más de un SKU, basta con agregar uno de los SKUs al grupo, que todos los SKUs asociados se incluirán en él. El campo de inclusión de los IDs no permite la digitación de caracteres alfanuméricos, ni la utilización de la combinación de teclas `Control + C` y `Control + V`. Además, cuando el número de SKUs en el listado ultrapase los 10 ítems, un control de paginación se hará disponible. Para excluir un SKU de la lista, basta con hacer clic en el botón rojo al lado del SKU correspondiente.
 
-![Inserir_sku_espec_fico](//images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
+![Inserir_sku_espec_fico](https://images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
 
 ### Importar un listado de SKUS para el grupo
 
 Pese a que los filtros de grupos son muy prácticos para crear agrupamientos de productos en forma automática, es posible que ellos no atiendan sus necesidades en situaciones específicas. Para resolver eso, es posible importar un listado con los SKUs que formarán parte del grupo y consecuentemente, de la colección. El módulo de colecciones acepta archivos en los formatos planilla de Excel (.xls) o CSV (.csv). En el caso de archivos en formato Excel, todos los IDs de los SKUs deben estar dispuestos en la primera columna, sin encabezado, como ejemplifica la figura abajo:
 
-![](//images.contentful.com/alneenqid6w5/6t9b1mIYmsSewCEu8yOagi/c0f73dc7b921e0f7cc65cea1ae572b7b/Importar_lista_de_skus.jpg)
+![](https://images.contentful.com/alneenqid6w5/6t9b1mIYmsSewCEu8yOagi/c0f73dc7b921e0f7cc65cea1ae572b7b/Importar_lista_de_skus.jpg)
 
-Después que el sistema importa la planilla, los SKUs se presentan de la siguiente forma: ![Importar_lista_de_skus](//images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
+Después que el sistema importa la planilla, los SKUs se presentan de la siguiente forma: ![Importar_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
 
 SKUs que estén inactivos no tendrán sus IDs importados, aunque estén incluidos en la planilla.
 
@@ -91,12 +91,12 @@ Recuerde que, cuando se selecciona más de un tipo de grupos, sólo los producto
 
 Para evitar que un administrador tenga que excluir manualmente diversos SKUs, uno por uno, es posible usar también el recurso de importación de SKUs de la misma forma como en el ejemplo arriba. En este caso, después que el archivo se cargue, haga clic en la opción _excluir skus_ (ítem 1 de la imagen).
 
-![Excluir_lista_de_skus](//images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
+![Excluir_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
 
-Obtenga un modelo de archivo para importación tanto para inclusión como para exclusión de ítems en la colección [aquí](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "aquí").
+Obtenga un modelo de archivo para importación tanto para inclusión como para exclusión de ítems en la colección [aquí](https://assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "aquí").
 
 ## Búsqueda de coleciones
 
 Cuando la cantidad de colecciones creadas exceda el límite de exhibición, que es veinte ítems, las colecciones podrán ser encontradas a través del campo de búsqueda. La búsqueda debe hacerse con base en el nombre de la colección.
 
-![Pesquisar_cole__o](//images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
+![Pesquisar_cole__o](https://images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
diff --git a/docs/tutorials/es/creating-a-subscription-plan.md b/docs/tutorials/es/creating-a-subscription-plan.md
index 4addb36c6..2742bb126 100644
--- a/docs/tutorials/es/creating-a-subscription-plan.md
+++ b/docs/tutorials/es/creating-a-subscription-plan.md
@@ -92,7 +92,7 @@ En esta pantalla, puede realizar las siguientes acciones:
 
 * **Seleccionar:** al hacer clic en la casilla (<i class="far fa-square"></i>) en la fila de cada producto, puede seleccionar productos o SKU individualmente. Otra opción es hacer clic en la primera casilla (<i class="far fa-square"></i>) y seleccionar todos los productos y SKU que aparecen en la página para añadirlos al plan, según se ilustra en la siguiente imagen.
 
-![selecionarskus ES](//images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/9786f043859be876f63855568e6d00d3/selecionarskus_ES.gif)
+![selecionarskus ES](https://images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/9786f043859be876f63855568e6d00d3/selecionarskus_ES.gif)
 
 * __Botón de flecha__ (<i class="fas fa-chevron-down"></i>): muestra los SKU, es decir, las variaciones del producto.
 * **Añadir:** al hacer clic en este botón, se añaden los productos o SKU al plan de suscripción.
diff --git a/docs/tutorials/es/creating-a-subscription-promotion.md b/docs/tutorials/es/creating-a-subscription-promotion.md
index e4c4824a5..4bd2d8973 100644
--- a/docs/tutorials/es/creating-a-subscription-promotion.md
+++ b/docs/tutorials/es/creating-a-subscription-promotion.md
@@ -23,7 +23,7 @@ En este artículo, encontrará el paso a paso para crear promociones por suscrip
 4. Seleccione `Promoción Regular`.
 5. En la sección **¿Cuáles son las condiciones para que la promoción sea válida?**, seleccione la casilla **Es un pedido de suscripción**.  Así, la promoción se aplicará a los pedidos por suscripción. Sólo los productos con una suscripción en la cesta recibirán el descuento. Para entender las posibilidades de configuración, vea las siguientes condiciones:
 
-![frequencia1](//images.ctfassets.net/alneenqid6w5/3Tg0ujk38ip94YogUGdD9M/ca5cd9a587aaff53b054efb27bf04008/image__3_.png)
+![frequencia1](https://images.ctfassets.net/alneenqid6w5/3Tg0ujk38ip94YogUGdD9M/ca5cd9a587aaff53b054efb27bf04008/image__3_.png)
 
 - **Pedido original**: pedidos que generan las suscripciones, pero que aún no forman parte de los ciclos de suscripción.
 - **Pedidos recurrentes**: pedidos que forman parte de los ciclos de suscripción.
diff --git a/docs/tutorials/es/creating-a-type-of-list.md b/docs/tutorials/es/creating-a-type-of-list.md
index 1f2c9a081..e4f07245f 100644
--- a/docs/tutorials/es/creating-a-type-of-list.md
+++ b/docs/tutorials/es/creating-a-type-of-list.md
@@ -61,7 +61,7 @@ El dueño de la tienda decide si la lista tendrá o no evento. Una vez grabado e
 
 Al seleccionar **Posee evento**, el formulario hace disponibles otras opciones de configuración para el evento, donde será posible configurar todas las fechas límites para la creación de ese tipo de lista, conforme a la imagen abajo.
 
-![eventos.es](//images.ctfassets.net/alneenqid6w5/Q48lA7Ybjz6mQ8wH27hms/85a9a1f23758f6e1fdc3a016dadeb68b/eventos.es.png)
+![eventos.es](https://images.ctfassets.net/alneenqid6w5/Q48lA7Ybjz6mQ8wH27hms/85a9a1f23758f6e1fdc3a016dadeb68b/eventos.es.png)
 
 El área de evento es responsable de definir si la lista creada tiene o no un período preestablecido para la fecha del evento. Listas de desejo o listas de compras no necesitan un período determinado para ocurrencia del evento. En cambio, listas de casamento o de chá de bebe, deben tener en cuenta la fecha del evento, para que así, todos los productos comprados se entreguen al dueño en período hábil según la fecha del evento.
 
@@ -77,7 +77,7 @@ El área de evento es responsable de definir si la lista creada tiene o no un pe
 
 Después de crear el tipo de lista, usted será dirigido a la pantalla donde aparecen los tipos de listas ya registrados en la tienda. Esa pantalla ofrece las siguientes informaciones y funciones:
 
-![listagem.es](//images.ctfassets.net/alneenqid6w5/3BTiBXCbQovhe3duPewHZx/410066a38327a8a69a3ffc1ed7bd2029/listagem.es.png)
+![listagem.es](https://images.ctfassets.net/alneenqid6w5/3BTiBXCbQovhe3duPewHZx/410066a38327a8a69a3ffc1ed7bd2029/listagem.es.png)
 
 - **Exportar a Excel**: Permite exportar los datos de tipos de listas para Excel.
 - **Versión**:Identificación de listas creadas en la versión antigua de la funcionalidad, con limitaciones. La versión más actual es la “v2”.
diff --git a/docs/tutorials/es/creating-an-oauth2-authentication.md b/docs/tutorials/es/creating-an-oauth2-authentication.md
index 51bde355a..ab982c90b 100644
--- a/docs/tutorials/es/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/es/creating-an-oauth2-authentication.md
@@ -38,7 +38,7 @@ Puede consultar la guía oficial del protocolo OAuth2 en esta dirección: https:
 ### Flujo de integración de OAuth2 con VTEX ID
 
 Con base en la documentación oficial, vea a continuación una ilustración que explica la integración de OAuth2 con VTEX ID:
-![oauth2](//images.ctfassets.net/alneenqid6w5/ZIsxie9YMmuWgWcgkeUis/313ac04141d8975528a273f1d2d47023/Fluxo_OAuth2_VTEX_ID__ES_.png)
+![oauth2](https://images.ctfassets.net/alneenqid6w5/ZIsxie9YMmuWgWcgkeUis/313ac04141d8975528a273f1d2d47023/Fluxo_OAuth2_VTEX_ID__ES_.png)
 
 A partir de esta ilustración, vamos a detallar los pasos a seguir.  
 
diff --git a/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
index 7ad341cdd..dc341b1b1 100644
--- a/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -23,7 +23,7 @@ Para aplicar un precio diferenciado a los productos por XML, es necesario asocia
   2. Busque el archivo XML que se modificará y haga clic en `Editar`. Si quiere crear uno nuevo, lea nuestro artículo [Configurar XML](https://help.vtex.com/es/tutorial/como-configurar-xml--tutorials_242).
   3. Aquí debe verificar si los campos relacionados con el precio del SKU (menor precio del producto, mayor precio del producto, precio original del SKU, precio actual del SKU y precio actual del SKU + tasas) se rellenaron. Al menos uno de los campos debe contener información para que la operación funcione correctamente.
   4. Rellene el campo __Tablas de precios__ con el nombre de la tabla de precios deseada. A continuación, haga clic en la casilla correspondiente al tag en la columna __Exhibe contenido__. La tabla de precios seleccionada debe tener registrados los precios fijos. De lo contrario, la configuración no se realizará.
-![PT-tabela de precos](//images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
+![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
 <div class="alert alert-warning">
   <p>Cuando se incluya la tabla de precios en el XML, se sobrescribirán todos los campos de precios.</p>
 </div>
@@ -37,5 +37,5 @@ Luego de terminar el registro del XML y guardar los cambios, puede verificar la
 
 Ejemplo de XML actualizado:
 
-![XML-exemplo](//images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/febf8db73d3de4579799de5a70e93de3/XML-exemplo.png)
+![XML-exemplo](https://images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/febf8db73d3de4579799de5a70e93de3/XML-exemplo.png)
 
diff --git a/docs/tutorials/es/creating-collections-beta.md b/docs/tutorials/es/creating-collections-beta.md
index 4419de250..fd590a264 100644
--- a/docs/tutorials/es/creating-collections-beta.md
+++ b/docs/tutorials/es/creating-collections-beta.md
@@ -88,23 +88,23 @@ La selección de productos vía Admin VTEX se puede realizar a través de la lis
 
 Hay una variedad de filtros que se pueden seleccionar para reducir la cantidad de productos que se muestran en la lista. 
 
-![Colecciones - ES](//images.ctfassets.net/alneenqid6w5/3FPMxYUHhfXCFgdJ1YaWBA/01b312b5cec4047135e06017b227eec3/Colecciones_-_ES.PNG)
+![Colecciones - ES](https://images.ctfassets.net/alneenqid6w5/3FPMxYUHhfXCFgdJ1YaWBA/01b312b5cec4047135e06017b227eec3/Colecciones_-_ES.PNG)
 
 Usted puede crear nuevos filtros a partir de otros criterios que no se incluyen en los filtros predeterminados. Las siguientes imágenes muestran algunas opciones:
 
-![Novo filtro - ES](//images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/fd2f6536dba1a15e56d64a94df9f66f8/Novo_filtro_-_ES.PNG)
+![Novo filtro - ES](https://images.ctfassets.net/alneenqid6w5/5CBl4UWLGKo9sf5CqoOIRD/fd2f6536dba1a15e56d64a94df9f66f8/Novo_filtro_-_ES.PNG)
 
-![Filtro Colecao detalhes - ES](//images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/5426ac9eab57f5e5b9241ec8525140e8/Filtro_Colecao_detalhes_-_ES.PNG)
+![Filtro Colecao detalhes - ES](https://images.ctfassets.net/alneenqid6w5/7E4dl1gucqIaCUMGEfZIK1/5426ac9eab57f5e5b9241ec8525140e8/Filtro_Colecao_detalhes_-_ES.PNG)
 
 Para agregar un producto a la colección, solo haga clic en el ícono <i class="fas fa-plus-circle" title = "símbolo de agregar en círculo"></i> del producto. De esa forma, se guardará en la colección automáticamente.  
 
 Si desea más información sobre el ítem, haga clic en el ícono <i class="fas fa-external-link-alt" title = "enlace externo"></i> para abrir la página del producto, o haga clic en la imagen para verla de forma ampliada. 
 
-![ES-colecao-adicionar](//images.ctfassets.net/alneenqid6w5/301ci58WsAbhxqAjczEVwj/1683d83db5dfa0526adef94f3c2bc7b0/ES-colecao-adicionar.gif)
+![ES-colecao-adicionar](https://images.ctfassets.net/alneenqid6w5/301ci58WsAbhxqAjczEVwj/1683d83db5dfa0526adef94f3c2bc7b0/ES-colecao-adicionar.gif)
 
 Si desea incluir productos de forma masiva, aplique uno de los filtros y haga clic en el botón `Agregar Todo`. Es importante destacar que el producto debe tener al menos un SKU registrado para ser incluido en una colección.
 
-![ES-colecao-adicionar-todos](//images.ctfassets.net/alneenqid6w5/1Qtj7Lq2xPebiPh4SrSV4R/6e66d5f68b4ffe07f6d1dd86bf16726c/ES-colecao-adicionar-todos.png)
+![ES-colecao-adicionar-todos](https://images.ctfassets.net/alneenqid6w5/1Qtj7Lq2xPebiPh4SrSV4R/6e66d5f68b4ffe07f6d1dd86bf16726c/ES-colecao-adicionar-todos.png)
 
 <div class = "alert alert-danger">
 <p>No agregue de forma masiva una cantidad superior a 150 mil productos. Eso puede comprometer la indexación del catálogo y el funcionamiento de la tienda.</p>
@@ -121,7 +121,7 @@ Para eso, realice los siguientes pasos:
   2. Haga clic en la opción **Incluir productos a la colección**, y luego en el botón `Importar`.
   3. Haga clic en `Descargar la plantilla` para obtener la plantilla correcta como se muestra aquí:
 
-![colecao-planilha -ES](//images.ctfassets.net/alneenqid6w5/4Mqxv9SSr8WynEiEah45ix/fa56634539212f663c2a3f36782b5f66/colecao-planilha_-ES.png)
+![colecao-planilha -ES](https://images.ctfassets.net/alneenqid6w5/4Mqxv9SSr8WynEiEah45ix/fa56634539212f663c2a3f36782b5f66/colecao-planilha_-ES.png)
 
   4. Complete la plantilla con los IDs o los RefIDs de los productos o de los SKUs. Solo agregue un ID en cada fila. Independientemente del ID que ingrese, todos los SKUs del producto seleccionado se añadirán a la colección después de la importación.
   5. Después de completar la plantilla, guarde las modificaciones e importe el documento en el Admin. Usted puede arrastrar y soltar el archivo en el área indicada o hacer clic en **Selecciona un archivo**. Se aceptan archivos en formato CSV o XML. En caso de que utilice un arquivo CSV, use , para delimitar los campos.
@@ -139,11 +139,11 @@ Los productos se pueden eliminar mediante la selección de los ítems en la list
 
 Para eliminar un ítem de la colección, solo debe hacer clic en el ícono <i class="fas fa-check-circle" title = "check en círculo"></i> del producto. 
 
-![ES-colecao-remover](//images.ctfassets.net/alneenqid6w5/4FcChdnT9NIYu69aS13TgM/f0b6c63d35ec92f9eb18f005b49d8d8a/ES-colecao-remover.gif)
+![ES-colecao-remover](https://images.ctfassets.net/alneenqid6w5/4FcChdnT9NIYu69aS13TgM/f0b6c63d35ec92f9eb18f005b49d8d8a/ES-colecao-remover.gif)
 
 Si desea eliminar productos de forma masiva, aplique uno de los filtros y haga clic en el botón `Eliminar Todo`.
 
-![ES-colecao-remover-todos](//images.ctfassets.net/alneenqid6w5/7s9ZJCnRkWSeY8xMJ5DelL/a2ca949f1e3d59fe49a2428b27c0d86e/ES-colecao-remover-todos.png)
+![ES-colecao-remover-todos](https://images.ctfassets.net/alneenqid6w5/7s9ZJCnRkWSeY8xMJ5DelL/a2ca949f1e3d59fe49a2428b27c0d86e/ES-colecao-remover-todos.png)
 
 También puede hacer clic en el botón <i class="far fa-check-circle" title = "produtos nesta coleção"></i> (Productos nen esta colección) en la barra superior y después seleccionar `Eliminar Todo`. 
 
@@ -176,7 +176,7 @@ Para alterar el orden de su colección, siga estos pasos:
 
   b. Seleccione la caja de los productos que desea alterar y haga clic en `Mover a la posición`. Indique el número de la nueva posición y, para finalizar, haga clic en `Mover`. De esta manera, puede ordenar todos los ítems de la lista de forma masiva. 
 
-![mover-colecao-ES](//images.ctfassets.net/alneenqid6w5/2fhHZIuCwN7aysjh78tOae/20aa235a1c6afa1a6c3504b0110a2b9d/mover-colecao-ES.png)
+![mover-colecao-ES](https://images.ctfassets.net/alneenqid6w5/2fhHZIuCwN7aysjh78tOae/20aa235a1c6afa1a6c3504b0110a2b9d/mover-colecao-ES.png)
 
 ### Exportar la plantilla de la colección
 
diff --git a/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md b/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md
index e99608de1..ae867db32 100644
--- a/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md
+++ b/docs/tutorials/es/creating-custom-queries-in-master-data-v1.md
@@ -44,11 +44,11 @@ Sigue los pasos a continuación para filtrar los registros de un formulario y gu
 
 Tras seguir las instrucciones anteriores, la consulta aparecerá como una opción de vista en la lista del formulario.
 
-![consultas-2-es](//images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/5e6ce3c1f84ca1d99e8c2761a66c6954/consultas-2-es.png)
+![consultas-2-es](https://images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/5e6ce3c1f84ca1d99e8c2761a66c6954/consultas-2-es.png)
 
 También puedes acceder a las consultas guardadas haciendo clic en el botón **Consultas**, en la lista del formulario:
 
-![consultas-es](//images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/22fd8166b6442947fd09734856ac675a/consultas-es__1_.png)
+![consultas-es](https://images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/22fd8166b6442947fd09734856ac675a/consultas-es__1_.png)
 
 ## Configuración de consulta predeterminada
 
diff --git a/docs/tutorials/es/creating-data-entity.md b/docs/tutorials/es/creating-data-entity.md
index eaf4a56bc..067659517 100644
--- a/docs/tutorials/es/creating-data-entity.md
+++ b/docs/tutorials/es/creating-data-entity.md
@@ -19,7 +19,7 @@ Entidad de datos es una representación de un conjunto de información sobre un
 
 Para ejemplificar, imagine un sistema de control de una biblioteca. Este sistema controla los libros que pueden ser alquilados por los clientes. Así, vemos que estos tres conceptos (libro, cliente y alquiler) son entidades que poseen informaciones sobre cada una de ellas. Entidad de datos, por lo tanto, es un grupo de información sobre un determinado concepto.
 
-![exemploBiblioteca](//images.contentful.com/alneenqid6w5/4WFfw93mlykqGCMSyAKcW2/27a0fd02aba4dd22df42a00fd506b75e/new-infographic.png)
+![exemploBiblioteca](https://images.contentful.com/alneenqid6w5/4WFfw93mlykqGCMSyAKcW2/27a0fd02aba4dd22df42a00fd506b75e/new-infographic.png)
 
 Con estos conceptos, es posible configurar los más diversos escenarios de control de datos por el Master Data. De forma predeterminada, se insertan las siguientes entidades de datos: Cliente, Dirección, Tiendas, etc. Es posible crear cuántas más entidades de datos desee, posibilitando un ambiente personalizado, orientado a las necesidades de cada tienda.
 
diff --git a/docs/tutorials/es/creating-form-in-master-data.md b/docs/tutorials/es/creating-form-in-master-data.md
index 1dff55900..6596444e9 100644
--- a/docs/tutorials/es/creating-form-in-master-data.md
+++ b/docs/tutorials/es/creating-form-in-master-data.md
@@ -40,7 +40,7 @@ Para crear un formulario, sigue los pasos a continuación:
 
    Si el acrónimo de la entidad __Lista de compras__ es __LC__ y el nombre del campo es __Cliente__, se debe insertar: `LC.Cliente`. Así serán cargados los atendimientos del cliente que se está visualizando en el formulario:
 
-   ![registrosRelacionados-es](//images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/e5f7e4a9c173af6654b4e7123d3c79c2/Untitled.png)
+   ![registrosRelacionados-es](https://images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/e5f7e4a9c173af6654b4e7123d3c79c2/Untitled.png)
 
 Después de llenar los campos requeridos, aparecerán las fichas disponibles para configuración. Los siguientes son los campos para cada una de ellas.
 
diff --git a/docs/tutorials/es/creating-landing-pages-per-binding.md b/docs/tutorials/es/creating-landing-pages-per-binding.md
index 4e133ec85..eb2e73d10 100644
--- a/docs/tutorials/es/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/es/creating-landing-pages-per-binding.md
@@ -23,7 +23,7 @@ En el Admin, puede crear páginas de destino personalizadas según el [*binding*
 2. Seleccione el *binding* en el que debe crearse la nueva página de destino en el menú desplegable de la página.
 3. Haga clic en el botón `Crear nueva`.
 
-  ![es-landing-page-binding](//images.ctfassets.net/alneenqid6w5/4VS1mFcJKaXeex3Cwr8V2/f22a1f99d5fe04ec192e8467ff7957cb/es-landing-page-binding.png)
+  ![es-landing-page-binding](https://images.ctfassets.net/alneenqid6w5/4VS1mFcJKaXeex3Cwr8V2/f22a1f99d5fe04ec192e8467ff7957cb/es-landing-page-binding.png)
 
 4. En la sección `Detalles de la página`, rellene los campos y defina los metadatos de su nueva página de destino según los valores esperados:
 
diff --git a/docs/tutorials/es/creating-landing-pages.md b/docs/tutorials/es/creating-landing-pages.md
index 20abdce60..abee2719a 100644
--- a/docs/tutorials/es/creating-landing-pages.md
+++ b/docs/tutorials/es/creating-landing-pages.md
@@ -27,7 +27,7 @@ En el Admin puedes crear páginas de destino personalizadas, como páginas para
 
 2.Haz clic en **CREAR NUEVA**.
 
-![Crear Landing Pages](//images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/b02f8122f28275b8e93a3241a7b7ba3f/cms-pages-es.png)
+![Crear Landing Pages](https://images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/b02f8122f28275b8e93a3241a7b7ba3f/cms-pages-es.png)
 
 3.En la sección **Detalles de la página**, rellena los siguientes campos para definir los metadatos de la página:
 
diff --git a/docs/tutorials/es/creating-lists-on-the-site.md b/docs/tutorials/es/creating-lists-on-the-site.md
index c153f939f..6b6e56b8d 100644
--- a/docs/tutorials/es/creating-lists-on-the-site.md
+++ b/docs/tutorials/es/creating-lists-on-the-site.md
@@ -27,11 +27,11 @@ Abajo va un ejemplo de cómo aparece el link, cuando su tienda sea creada y aún
 
 El link “Minha Lista” hace disponibles tres opciones: Buscar uma lista, Criar uma nova lista y Gerenciar minhas listas. Entienda las particularidades de cada una de ellas:
 
-![](//images.contentful.com/alneenqid6w5/3lEYA5uyJGSuMkMGqOmi0c/55f5091aa3eeff82db785b283518b3f3/Como_criar_lista_no_site_1.jpg)
+![](https://images.contentful.com/alneenqid6w5/3lEYA5uyJGSuMkMGqOmi0c/55f5091aa3eeff82db785b283518b3f3/Como_criar_lista_no_site_1.jpg)
 
 ## **Buscar una Lista**
 
-![](//images.contentful.com/alneenqid6w5/IP0hyIHPEse28MIKKYwwQ/ee54d32cf1cefcf6c92912c2ebb007af/Como_criar_lista_no_site_2.gif)
+![](https://images.contentful.com/alneenqid6w5/IP0hyIHPEse28MIKKYwwQ/ee54d32cf1cefcf6c92912c2ebb007af/Como_criar_lista_no_site_2.gif)
 
 Para buscar una lista en el sitio, haga clic en el link “Minha lista” y rellene uno de los campos disponibles para filtro, conforme a los de abajo. Esa página puede variar de acuerdo a la personalización que se haga en el sitio, la que puede, por ejemplo, limitarse a usar sólo los campos “Nome”, “Sobrenome” y “Data do Evento”.
 
diff --git a/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
index 703b2c9b0..99849f184 100644
--- a/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
@@ -55,7 +55,7 @@ Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vte
 
 El Editor visual de reglas de merchandising de VTEX Intelligent Search permite realizar las acciones que se ilustran en la imagen siguiente:
 
-![visual-merch-rules-ES-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
+![visual-merch-rules-ES-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Editar nombre de la regla de merchandising.</li>
@@ -90,7 +90,7 @@ El Editor visual de reglas de merchandising de VTEX Intelligent Search permite r
 
 El filtro es un atributo seleccionable predefinido que restringe los resultados de la búsqueda, por ejemplo, permite filtrar por todos los productos de una categoría o marca, entre otras condiciones. Puedes agregar una o más condiciones a un filtro, tal como se muestra a continuación.
 
-![filtros-merchrules-es](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
+![filtros-merchrules-es](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
 
 Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
 
diff --git a/docs/tutorials/es/creating-merchandising-rules-visual-editor.md b/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
index 4ba815a79..a007ccbe7 100644
--- a/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
+++ b/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
@@ -51,7 +51,7 @@ Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vte
 
 El Editor visual de reglas de merchandising de VTEX Intelligent Search permite realizar las acciones que se ilustran en la imagen siguiente:
 
-![visual-merch-rules-ES-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
+![visual-merch-rules-ES-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/717c18f418806f9cda88166167928548/visual-merch-rules-ES-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Editar nombre de la regla de merchandising.</li>
@@ -86,7 +86,7 @@ El Editor visual de reglas de merchandising de VTEX Intelligent Search permite r
 
 El filtro es un atributo seleccionable predefinido que restringe los resultados de la búsqueda, por ejemplo, permite filtrar por todos los productos de una categoría o marca, entre otras condiciones. Puedes agregar una o más condiciones a un filtro, tal como se muestra a continuación.
 
-![filtros-merchrules-es](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
+![filtros-merchrules-es](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/cff18739dd40a27d303df3b5664e4d63/filtros-es.gif)
 
 Si deseas agregar una condición en el Editor visual, sigue cada uno de los pasos que se indican a continuación. 
 
diff --git a/docs/tutorials/es/creating-price-tables.md b/docs/tutorials/es/creating-price-tables.md
index 918751b92..07cb62a86 100644
--- a/docs/tutorials/es/creating-price-tables.md
+++ b/docs/tutorials/es/creating-price-tables.md
@@ -23,7 +23,7 @@ Para crear una Tabla de Precios siga estos pasos:
  4. Elija el nombre de la tabla de precios que desea crear.
  5. Clic **Crear tabla de precios**.
 
-![creacion-de-tablas-de-precios](//images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/fdc959523e5c2608a20bb3f454d064a3/criar-tabela-precos-es.gif)
+![creacion-de-tablas-de-precios](https://images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/fdc959523e5c2608a20bb3f454d064a3/criar-tabela-precos-es.gif)
 
 Para encontrar una Tabla de Precio:
 
diff --git a/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
index 55ebb15d5..ee9fca67a 100644
--- a/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
@@ -62,9 +62,9 @@ En la siguiente configuración, por ejemplo, solo los registros de ``empleados``
 
 De esta manera también se podría establecer `empleado=false`, donde solo los registros de `empleado` con un valor `false` en el campo obtendrían la promoción.
 
-![Campo funcionário Master Data ES](//images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/8fdaea6b5ced25c76bea649ccc0e9e12/Campo_funcion__rio_Master_Data_ES.png)
+![Campo funcionário Master Data ES](https://images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/8fdaea6b5ced25c76bea649ccc0e9e12/Campo_funcion__rio_Master_Data_ES.png)
 
-![Cluster de clientes ES](//images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/cb74a3f5ecba7fe987381e62543a13de/Cluster_de_clientes_ES.png)
+![Cluster de clientes ES](https://images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/cb74a3f5ecba7fe987381e62543a13de/Cluster_de_clientes_ES.png)
 
 Dado un campo **[Varchar](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#)**, podríamos configurar `empleado="sí"` para que solo los clientes con el valor `"sí"` en el campo recibieran la promoción.
 
@@ -82,8 +82,8 @@ La expresión `{nombredelapropiedad} contains {valor}` debe utilizarse cuando la
 
 Por ejemplo, si quiere crear un clúster sólo con clientes cuyas direcciones de correo electrónico contengan `@test.com`, la configuración sería igual a la representada en la imagen siguiente.
 
-![Campo Email Master Data](//images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
+![Campo Email Master Data](https://images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
 
-![cluster email ES](//images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/8139bb8d0546b62edf917418c5c92c5b/cluster_email_ES.PNG)
+![cluster email ES](https://images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/8139bb8d0546b62edf917418c5c92c5b/cluster_email_ES.PNG)
 
 En este caso, `email contains test.com` será verdadero, por ejemplo, cuando el valor sea `joao@test.com` y falso cuando el valor sea `joao@test.org`.
diff --git a/docs/tutorials/es/creating-promotions.md b/docs/tutorials/es/creating-promotions.md
index 1ba006a07..5d84817d2 100644
--- a/docs/tutorials/es/creating-promotions.md
+++ b/docs/tutorials/es/creating-promotions.md
@@ -78,7 +78,7 @@ Puedes cambiar las configuraciones y los datos de cualquier promoción siguiendo
 La programación de una promoción se produce cuando esta se crea (o modifica) con una fecha y hora de validez posteriores al momento actual. La hora considerada es la del sistema del computador en el que se creó la promoción, sin tener en cuenta los ajustes de zona horaria.
 Estas promociones se pueden identificar fácilmente en la página principal de Promociones, ya que tienen una franja naranja con la palabra programada en la esquina superior derecha de la tarjeta, como se muestra a continuación:
 
-![programada](//images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/cc495af0c2c31c27cc53870ed7a95aee/programada..png)
+![programada](https://images.ctfassets.net/alneenqid6w5/illvXlc6M10IO8p8IfL7J/cc495af0c2c31c27cc53870ed7a95aee/programada..png)
 
 Para programar una promoción, sigue los pasos descritos en la sección [Programar promociones](https://help.vtex.com/es/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI?&utm_source=autocomplete#programar-promociones) del artículo [Programación de funcionalidades para eventos especiales](https://help.vtex.com/pt/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI).
 
diff --git a/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md
index 0e5b152ec..b8bc31a46 100644
--- a/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/es/creating-relationships-between-master-data-entities-using-admin.md
@@ -31,23 +31,23 @@ En este ejemplo se crea una entidad denominada `Lista de Compras` que se relacio
 
 1. Haga clic en la pestaña **Aplicações**.
 2. Después, haga clic en el botón **Advanced settings**.  
-![Configuraciones Avanzadas](//images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
+![Configuraciones Avanzadas](https://images.ctfassets.net/alneenqid6w5/6wFQw4Qk1qjan3kff0slhB/f35565fd34625205f1e28006292fc110/Advanced_settings.png)
 3. Haga clic en la opción **Estrutura de dados**. Eso abrirá una nueva pestaña a Dynamic Storage (DS).  
-![Estructura de datos](//images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
+![Estructura de datos](https://images.ctfassets.net/alneenqid6w5/24pLSQHFkz2TnB0VMU6yKk/04a32ffbeeedc0f615b2adb42038e676/Estrutura_de_dados.png)
 4. En Dynamic Storage, haga clic en la pestaña **Data Entities**.
 5. Si desea crear una relación en una nueva entidad, haga clic en el botón **Add new** para crear una nueva entidad de datos. _En caso de que quiera crear una relación en una entidad existente, haga clic en el botón **Edit** de dicha entidad, y continue a partir del paso 7_.  
-![Agregar nueva entidad de datos](//images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
-![Editar entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
+![Agregar nueva entidad de datos](https://images.ctfassets.net/alneenqid6w5/6RnSgkbz7LF0S8kwMHBReK/7895df7b2ac14d5fea332040a40977d8/Adicionar_nova_entidade_dados.png)  
+![Editar entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
 6. Configure la entidad que será creada completando los campos **Acronym** y **Name** y agregando los campos deseados. En este ejemplo, la entidad utilizará el nombre `Lista de compras`, acrónimo `LC` y campo `compras` de tipo `Varchar 750`.
 7. Agregue un campo de tipo `Relationship` y defina su nombre. En el ejemplo, este se denominará `Cliente`.
 8. Luego, haga clic en el botón **Edit** (ícono de engranaje) del campo de relación para configurarlo.
 9. En la configuración **Custom field type settings** seleccione la entidad a la que desea hacer referencia y el campo que se mostrará en esa relación. En este ejemplo, la relación se hará en la entidad "Cliente" y se mostrará el campo "email".  
-![Relación entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
+![Relación entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
 10. Haga clic en **Save** para guardar los ajustes.  
-![Guardar entidad de datos](//images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
+![Guardar entidad de datos](https://images.ctfassets.net/alneenqid6w5/3HaACxzYeRsUE5i8jLRGf/c96ed109ce54f70138489cf25cb87cd8/Salvar_entidade_de_dados.png)
 11. Vuelva a la lista de entidades. Recuerde que tiene que publicar la nueva entidad haciendo clic en el botón **Publish** (ícono de disquete) de la misma. También puede ser necesario actualizar las aplicaciones para que se implementen las alteraciones, para eso vaya a **Aplicações** y haga clic en el botón **Reload applications**.  
-![Publicar entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
-![Master Data Reload applications](//images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
+![Publicar entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/4R9mLqBcx8Vq2JaurbmLkG/6ace79062a37f8a0ecd24f95a6ec2c2d/Publicar_entidade_Lista_de_Compras.png)  
+![Master Data Reload applications](https://images.ctfassets.net/alneenqid6w5/6gud9kq3gpHbU9a23xzzSZ/e3e9f10a22b7567b1698342374f10bb6/Master_Data_Reload_applications.png)
 
 ## ¿Cómo crear una relación entre documentos?
 
@@ -55,45 +55,45 @@ Las relaciones también se pueden aplicar a documentos específicos de las entid
 
 1. Para relacionar los documentos agregue el campo de relación en el formulario de la entidad que contiene la referencia. Para facilitar eso, puede definir el campo como un cuadro combinado para mostrar todos los valores disponibles. Puede ver más detalles en el artículo [Crear un campo en Master Data](https://help.vtex.com/es/tutorial/como-crear-un-campo-en-master-data--frequentlyAskedQuestions_1829#crm).
 2. Seleccione el valor deseado (en este caso, el cliente al que se relacionará la lista de compras).  
-![Seleccionar relación de documento Master Data](//images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/0db9c1fe76beb2a136ed446e72982438/Selecionar_relacionamento_de_documento_Master_Data.png)
+![Seleccionar relación de documento Master Data](https://images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/0db9c1fe76beb2a136ed446e72982438/Selecionar_relacionamento_de_documento_Master_Data.png)
 3. Haga clic en **Salvar** para guardar la configuración.
 
 Cuando agregue el campo en la tabla, verifique los valores que se definieron.
-![Tabla de relaciones de documentos Master Data](//images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/d120164f9a1d553be92eb2eefb6cf251/Tabela_de_relacionamento_de_documentos_Master_Data.png)
+![Tabla de relaciones de documentos Master Data](https://images.ctfassets.net/alneenqid6w5/43607tgaCHpBOeKQ3w9VUd/d120164f9a1d553be92eb2eefb6cf251/Tabela_de_relacionamento_de_documentos_Master_Data.png)
 
 ## ¿Cómo agregar filtros a los campos de relación?
 
 Las relaciones se mantienen a través de los IDs de los documentos. Por tanto, cuando intente ingresar el valor del campo de relación como filtro en el formulario solo obtendrá los valores de los IDs de los documentos referenciados, y no los valores del campo elegido para cada documento. Las siguientes imágenes muestran ese resultado. Puede encontrar más información sobre filtros en el artículo [Filtrar datos en Master Data](https://help.vtex.com/es/tutorial/filtrando-dados-no-master-data--tutorials_778)
 
-![Seleccionar filtro de relación](//images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/715c368b1c0d3ed81a5eb25f06bb3bcc/Selecionar_filtro_relacionamento.png)
+![Seleccionar filtro de relación](https://images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/715c368b1c0d3ed81a5eb25f06bb3bcc/Selecionar_filtro_relacionamento.png)
 
-![Filtro de relación ID](//images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/1218b7078443c3666502a20333970467/Filtro_relacionamento_ID.png)
+![Filtro de relación ID](https://images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/1218b7078443c3666502a20333970467/Filtro_relacionamento_ID.png)
 
 En caso de que desee ver los valores de los campos, y no sus IDs, se puede filtrar estos mediante un campo automático. Para eso: 
 
 1. En el Master Data, vaya a **Aplicações** > **Advanced settings** > **Estrutura de dados** para acceder a Dynamic Storage.
 2. Luego, acceda a las entidades de datos en **Data Entities**.
 3. En la entidad que contiene la relación (en este caso `Lista de Compras`), haga clic en el botón **Editar**.  
-![Editar entidad Lista de Compras](//images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
+![Editar entidad Lista de Compras](https://images.ctfassets.net/alneenqid6w5/1NMNJbWq3qnVjc0nt4x8ok/4a9f852803c1c3cc391c572bd61ba8a9/Editar_entidade_Lista_de_Compras.png)
 4. Haga clic en la pestaña **Automatic fields**.
 5. Luego, clic en el botón **New Calculated field**.  
-![Relacionamento automatic fields](//images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
+![Relacionamento automatic fields](https://images.ctfassets.net/alneenqid6w5/5StRAtwfrzUWnSzOLrHJqM/603a35102ef272d3c5b633eaa3e757e7/Relacionamento_automatic_fields.png)
 6. Complete los campos **Name**, **Display Name** y **Type** según lo deseado. En este ejemplo se utilizarán `emailCliente`, `E-mail cliente` y Varchar 50.
 7. Haga clic en el ícono de engranaje para realizar una configuración adicional.  
-![Nombre automatic field](//images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/38f68d5ee8cc3d06b6e26cc571f047f0/Nome_automatic_field.png)
+![Nombre automatic field](https://images.ctfassets.net/alneenqid6w5/4lAatUDVlXMOpNLKX1kx0J/38f68d5ee8cc3d06b6e26cc571f047f0/Nome_automatic_field.png)
 8. Realice los ajustes que desea y utilice la fórmula para elegir el campo de la entidad relacionada que desea mostrar en el fitro. En este ejemplo, se utilizará el correo electrónico del cliente.
 
-![Configurar relación automatic fields](//images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/79d487b39c0ca6abdc98826232dc17d0/Configurar_relacionamento_automatic_fields.png)
+![Configurar relación automatic fields](https://images.ctfassets.net/alneenqid6w5/1cmXmQDZaepVddzoExEl1r/79d487b39c0ca6abdc98826232dc17d0/Configurar_relacionamento_automatic_fields.png)
 9. Haga clic en el botón **Validate**.
 10. En la ventana que se abrirá, ingrese un email genérico y haga clic en **Ok**.  
-![Validar automatic field](//images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
+![Validar automatic field](https://images.ctfassets.net/alneenqid6w5/5nLfBVHL6YfedIALJsf6QX/127bfc77d276c61ccd0346bcb8d6e6e2/Validar_automatic_field.png)
 11. Luego, aparecerá un aviso indicando que la fórmula es válida, como se muestra en la siguiente imagen. Haga clic en **Ok**.  
-![Fórmula válida automatic field](//images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
+![Fórmula válida automatic field](https://images.ctfassets.net/alneenqid6w5/79A6B2D9TMjkpkj6gkez9Y/ee9e905339c9cbb8343a8809fb38a9e6/F__rmula_v__lida_automatic_field.png)
 12. Para finalizar, guarde los ajustes haciendo clic en **Save**.
 
 Luego de los anteriores pasos el filtro se aplica a la relación. En el formulario de la entidad (`Lista de Compras`), agregue el campo al filtro después de actualizar los registros.
-![Seleccionar filtro de relación valor](//images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/17f4b5b4e9a5a67c197f9351501a8598/Selecionar_filtro_relacionamento_valor.png)
+![Seleccionar filtro de relación valor](https://images.ctfassets.net/alneenqid6w5/6KQwyXBZ0VaK2srXFiupmv/17f4b5b4e9a5a67c197f9351501a8598/Selecionar_filtro_relacionamento_valor.png)
 
 De esta forma podemos ver el filtro con los valores en vez de los IDs.
-![Filtro relación valor](//images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/2c5f45e9e00c7a9c37cec54dea7c35eb/Filtro_relacionamento_valor.png)
+![Filtro relación valor](https://images.ctfassets.net/alneenqid6w5/2mcBmzqxJLm7L3GrZuFeVa/2c5f45e9e00c7a9c37cec54dea7c35eb/Filtro_relacionamento_valor.png)
 
diff --git a/docs/tutorials/es/creating-roles.md b/docs/tutorials/es/creating-roles.md
index 1ec4d8562..6ba50a900 100644
--- a/docs/tutorials/es/creating-roles.md
+++ b/docs/tutorials/es/creating-roles.md
@@ -45,12 +45,12 @@ Para empezar a utilizar un rol predefinido sigue las instrucciones a continuaci
 
     Por ejemplo, el rol **Call center operator** contiene un recurso del producto _Catálogo_ que permite realizar operaciones en una tienda en nombre de un cliente, y un recurso de _OMS_ que permite consultar el status de un pedido:
 
-    ![Nuevo perfil de acceso](//images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/377d5de0c9b4af5667a4e8f10c171ae0/last_with_shadow_Wed_Apr__8_17_06_18_-03_2020.png)
+    ![Nuevo perfil de acceso](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/377d5de0c9b4af5667a4e8f10c171ae0/last_with_shadow_Wed_Apr__8_17_06_18_-03_2020.png)
 
     Consulta más información sobre los roles predefinidos disponibles y los recursos asociados en [Roles de usuario predefinidos](https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy).
 4. Agrega usuarios administrativos al rol rellenando el email del usuario en **Agregar usuarios para este rol** y haciendo clic en `Agregar`.
 
-    ![Usuarios de perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/5d76addf0b92724ac97f66aa517a110d/usuarios-es.PNG)
+    ![Usuarios de perfil](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/5d76addf0b92724ac97f66aa517a110d/usuarios-es.PNG)
 
     Si el usuario no existe, se creará uno nuevo utilizando el email como nombre, es decir, el nombre y el email serán iguales.
 
@@ -70,7 +70,7 @@ Sigue las instrucciones a continuación para crear un rol personalizado que resp
 
     Verás una lista de todos los recursos disponibles para ese producto:
 
-    ![Configurando producto](//images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/0393d07c7e603da3fab9a589adf8e58c/configurar-produto-es.png)
+    ![Configurando producto](https://images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/0393d07c7e603da3fab9a589adf8e58c/configurar-produto-es.png)
 5. Marca los recursos a los que el rol tendrá acceso. Para más información sobre [Recursos, consulta la lista completa de License Manager](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3).
 6. Si deseas agregar recursos de otro producto, haz clic en el botón **Configurar otro producto** situado en la parte inferior de la lista de productos y recursos y repite los pasos 4 y 5.
 
@@ -84,7 +84,7 @@ Sigue las instrucciones a continuación para crear un rol personalizado que resp
 
 8. Agrega usuarios administrativos al rol rellenando el email del usuario en **Agregar usuarios para este rol** y haciendo clic en `Agregar`.
 
-      ![Usuarios de perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/5d76addf0b92724ac97f66aa517a110d/usuarios-es.PNG)
+      ![Usuarios de perfil](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/5d76addf0b92724ac97f66aa517a110d/usuarios-es.PNG)
 
       Si el usuario no existe, se creará uno nuevo utilizando el email como nombre, es decir, el nombre y el email serán iguales.
 9. Haz clic en `Guardar`.
diff --git a/docs/tutorials/es/creating-service-for-a-sku.md b/docs/tutorials/es/creating-service-for-a-sku.md
index 1a2cf2396..0e6c0a6dc 100644
--- a/docs/tutorials/es/creating-service-for-a-sku.md
+++ b/docs/tutorials/es/creating-service-for-a-sku.md
@@ -79,7 +79,7 @@ Para vincular un servicio a un SKU, sigue los pasos a continuación:
   <p>El tamaño del archivo de la plantilla no debe superar los 4Mb (4096KB).</p>
 </div>
 8. Haz clic en la barra que se encuentra junto al botón `Select`, que se muestra a continuación.
-  ![Anexos - ES](//images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/844c4cb0282e3b4e32c9b494906b0597/sku-services-ES.png)
+  ![Anexos - ES](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/844c4cb0282e3b4e32c9b494906b0597/sku-services-ES.png)
 9. Selecciona la plantilla CSV actualizada.
 10. Haz clic en `Vincular valores de servicios a SKU` para finalizar.
 
diff --git a/docs/tutorials/es/creating-surchargestaxes.md b/docs/tutorials/es/creating-surchargestaxes.md
index 89f5744f8..770f80e8a 100644
--- a/docs/tutorials/es/creating-surchargestaxes.md
+++ b/docs/tutorials/es/creating-surchargestaxes.md
@@ -58,4 +58,4 @@ El impuesto se aplica conforme al registro que hará el vendedor. A continuaci
 
 La planificación de un impuesto se produce cuando es creado o modificado con el tiempo y la fecha de validación más adelante del actual. Visualmente se pueden identificar estos impuestos en la página principal del módulo de Tsas y Promociones a través de una franja naranja en la esquina superior derecha de la lista de precios con la palabra programado. A continuación se muestra un ejemplo de cómo se identifica el impuesto cuando está programado.
 
-![agendamento.es](//images.ctfassets.net/alneenqid6w5/2DPKlUdsr38TTIwc3e9GH5/31b3319951c14c8faa6ab3558cebf19b/agendamento.es.png)
+![agendamento.es](https://images.ctfassets.net/alneenqid6w5/2DPKlUdsr38TTIwc3e9GH5/31b3319951c14c8faa6ab3558cebf19b/agendamento.es.png)
diff --git a/docs/tutorials/es/creating-the-category-tree.md b/docs/tutorials/es/creating-the-category-tree.md
index 60f97fcb4..f45322c38 100644
--- a/docs/tutorials/es/creating-the-category-tree.md
+++ b/docs/tutorials/es/creating-the-category-tree.md
@@ -19,4 +19,4 @@ El árbol de categorias es la estructura de categorias que será utilizada en s
 
 [La definición del árbol de categorias](/es/tutorial/cadastrando-categoria/ "La definición del árbol de categorias") debe ser realizada en el comienzo del proyeto y debe ser muy planeada, pensando en su catalogo de productos y en el SEO.
 
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-6334-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4](//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4 "//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-6334-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4?_=1" />[//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4](https://assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4 "//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4")</video>
diff --git a/docs/tutorials/es/creating-trigger-in-master-data.md b/docs/tutorials/es/creating-trigger-in-master-data.md
index daddb1c6a..7c17d0687 100644
--- a/docs/tutorials/es/creating-trigger-in-master-data.md
+++ b/docs/tutorials/es/creating-trigger-in-master-data.md
@@ -44,7 +44,7 @@ Las principales características de los triggers son las siguientes:
 
 Antes de [crear un trigger](#configurar-trigger), es necesario comprender que su configuración consta de cuatro partes, que se explican a continuación.
 
-![trigger](//images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/4dee23f7b89e1ce4acd9479dcd0babd9/trigger-es.png)
+![trigger](https://images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/4dee23f7b89e1ce4acd9479dcd0babd9/trigger-es.png)
 
 ### Acción que activa el trigger
 
@@ -121,7 +121,7 @@ Aquí debes definir las condiciones que activarán el evento o eventos configura
 
    Selecciona los campos y los valores que activarán o no el trigger.
 
-   ![filters-es](//images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/ce8019b7300c8c857ac71ffb4f0091c9/filters-es.png)
+   ![filters-es](https://images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/ce8019b7300c8c857ac71ffb4f0091c9/filters-es.png)
 
 <div class="alert alert-info">
   <p>Master Data v1 no permite la configuración de reintentos de trigger, a diferencia de Master Data v2.</p>
@@ -143,7 +143,7 @@ En esta pestaña debes configurar los eventos que deben dispararse si el registr
 
 Envía un email a destinatarios dinámicos (contenidos en el registro) o estáticos. El email puede personalizarse y estar en formato de texto, HTML o incluir el contenido de una URL. Se pueden ingresar archivos adjuntos y el campo **Tags válidas** muestra cómo ingresar valores de campos del registro.
 
-![send-email-es](//images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/e413677641a756923fa9fd6e477002e2/send-email-es.png)
+![send-email-es](https://images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/e413677641a756923fa9fd6e477002e2/send-email-es.png)
 
 #### Enviar un email utilizando una plantilla de VTEX Message Center
 
@@ -159,7 +159,7 @@ Envía un request HTTP con la posibilidad de guardar la información de la respu
 
 Rellena el apartado **Información del request** con los datos de la solicitud que deseas enviar. En la sección **Acción de respuesta**, puedes indicar cómo debe guardarse la información de la respuesta en Master Data.
 
-![http-request-es](//images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/a24d038b06e2153e667a90c9a42920d9/http-request-es.png)
+![http-request-es](https://images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/a24d038b06e2153e667a90c9a42920d9/http-request-es.png)
 
 Para configurar la **Acción de respuesta** selecciona la entidad de datos deseada y especifica la ruta JSON correspondiente para cada campo que se debe guardar en la respuesta.
 
diff --git a/docs/tutorials/es/creating-users.md b/docs/tutorials/es/creating-users.md
index 1a68ce0b0..27eda0a38 100644
--- a/docs/tutorials/es/creating-users.md
+++ b/docs/tutorials/es/creating-users.md
@@ -20,5 +20,5 @@ Después de la creación del ambiente, sólo el usuario que ha firmado el contra
 Para eso, es necesario accesar su License Manager y [asociar usuarios](http://help.vtex.com/es/tutorial/guia-para-crear-usuarios/).
 
 El video abajo enseña todo el flujo de esta configuración:
-<video class="wp-video-shortcode" id="video-2548-13" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4?_=13" />[//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4](//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4 "//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4")</video>
+<video class="wp-video-shortcode" id="video-2548-13" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4?_=13" />[//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4](https://assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4 "//assets.contentful.com/alneenqid6w5/2WUdIzl9y8q6y8uaOSgOKA/cc3541d7834f8b2b8f8eaf09672361bf/2b-CriandoUsuario.mp4")</video>
 
diff --git a/docs/tutorials/es/creating-your-promotions.md b/docs/tutorials/es/creating-your-promotions.md
index d79b2f649..062e45bd5 100644
--- a/docs/tutorials/es/creating-your-promotions.md
+++ b/docs/tutorials/es/creating-your-promotions.md
@@ -18,4 +18,4 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 La [creación de procomociones](http://help.vtex.com/es/tutorial/como-crear-promociones) no es un paso obligatorio para subir la tienda, pero es muy utilizado por las tiendas y, por eso, está en nuestros primeros pasos. Aproveche y configure una promoción de lanzamiento. 😋
 
 _El video presentado abajo todavía no ha sido traducido. Gracias por la comprensión._
-<video class="wp-video-shortcode" id="video-2576-3" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4?_=3" />[//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4](//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4 "//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4")</video>
+<video class="wp-video-shortcode" id="video-2576-3" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4?_=3" />[//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4](https://assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4 "//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4")</video>
diff --git a/docs/tutorials/es/credit-card-basic-payment-flow.md b/docs/tutorials/es/credit-card-basic-payment-flow.md
index 9cedd29dd..ff1f881c9 100644
--- a/docs/tutorials/es/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/es/credit-card-basic-payment-flow.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 Este artículo tiene como objetivo explicar cómo funciona el flujo básico de un pago por __tarjeta de crédito__:
 
-![ES Flujo Tarjeta de Credito](//images.ctfassets.net/alneenqid6w5/JziB4sI4XzTW0lpAwt1xL/dcd6a342402fc2f003fe76b6f1d38c8e/ES_Flujo_Tarjeta.svg)
+![ES Flujo Tarjeta de Credito](https://images.ctfassets.net/alneenqid6w5/JziB4sI4XzTW0lpAwt1xL/dcd6a342402fc2f003fe76b6f1d38c8e/ES_Flujo_Tarjeta.svg)
 
 1. En la pantalla de Checkout, el cliente elige el __Medio de Pago__ tarjeta de crédito para realizar el pago de su compra.
 2. La información de este pago se pasa al __Gateway de Pagos__. El [gateway](/es/tutorial/que-es-un-gateway-de-pagos) es el player responsable de garantizar que este pago se realice con éxito.
diff --git a/docs/tutorials/es/credit-control-overview.md b/docs/tutorials/es/credit-control-overview.md
index cfd682480..dc8609b66 100644
--- a/docs/tutorials/es/credit-control-overview.md
+++ b/docs/tutorials/es/credit-control-overview.md
@@ -35,7 +35,7 @@ Por eso creamos el Credit Control - para que el control de crédito sea hecho de
 
 ## Como funciona
 
-![Credit Control basic flow](//images.contentful.com/alneenqid6w5/35jUk6EVksKUQi8EaU6caO/2f8f3ddb5ead2d2c9379fc340fb070f9/credit-control-flow_en.gif)
+![Credit Control basic flow](https://images.contentful.com/alneenqid6w5/35jUk6EVksKUQi8EaU6caO/2f8f3ddb5ead2d2c9379fc340fb070f9/credit-control-flow_en.gif)
 *Flujo básico de cómo funciona el Credit Control en las tiendas VTEX.*
 
 1. La tienda enciende el conector de control de crédito y realiza las configuraciones iniciales.
diff --git a/docs/tutorials/es/criar-um-produto-beta.md b/docs/tutorials/es/criar-um-produto-beta.md
index 4ba8d98e5..39e02aa0f 100644
--- a/docs/tutorials/es/criar-um-produto-beta.md
+++ b/docs/tutorials/es/criar-um-produto-beta.md
@@ -40,7 +40,7 @@ Una vez hecho esto, el producto se activará y estará disponible en tu tienda.
 En esta pestaña se realiza el registro del producto, para lo que es necesario rellenar los campos que se describen a continuación con las características del ítem.
 
 ### Información general
-![image9](//images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
+![image9](https://images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
 **- Nombre**: ingresa el título del producto en la tienda. Utiliza vocabulario sencillo y evita términos en otro idioma o redacción compleja. Este campo es importante para SEO y se debe respetar el límite de 150 caracteres. Campo obligatorio. Ejemplo: Calzado deportivo Ultralight.
 
 **- Palabras sustitutas**: ingresa sinónimos de términos relacionados con el nombre asignado al producto, separados por comas (`,`). Este campo es importante para ampliar el alcance de las búsquedas y debe respetarse el límite de 8000 caracteres.
@@ -61,7 +61,7 @@ En este paso, debes ingresar una descripción de la información más importante
 
 El editor de texto de la descripción es de tipo texto enriquecido, es decir, tienes a tu disposición varios recursos de formato utilizando la barra de herramientas de este campo, ilustrada a continuación.
 
-![image10](//images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
+![image10](https://images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
 Estos son los recursos disponibles en la barra de herramientas:
 
 - __Estilos__: define el estilo del texto seleccionado. Las opciones son: **Normal** y **Título 1** hasta **Título 6**.
@@ -85,13 +85,13 @@ Estos son los recursos disponibles en la barra de herramientas:
 - **Código fuente**: muestra el código fuente de la descripción en HTML. Si lo deseas, puedes editar la descripción directamente desde el código fuente. Para regresar a la vista anterior, debes volver a hacer clic en el botón del código fuente.
 
 ## SEO
-![image11](//images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
+![image11](https://images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
 - **URL del producto**: ingresa la URL a través de la cual se podrá acceder al producto en la tienda. En este campo no se pueden utilizar espacios ni caracteres especiales. Si la URL está compuesta por más de una palabra, debes separarlas con un `-`. Campo obligatorio. Ejemplo: calzado-deportivo-ultralight.
 - **Título de la página**: ingresa el título de la página del producto. Para optimizar la posición de tu producto en los resultados de búsqueda, es recomendable no exceder los 60 caracteres. Campo obligatorio. Ejemplo: Calzado deportivo 
 Ultralight.
 - **Metadescripción**: ingresa el título de la página del producto. Para optimizar la posición de tu producto en los resultados de búsqueda, es recomendable no exceder los 60 caracteres. Campo obligatorio. Ejemplo: Te presentamos el calzado deportivo Ultralight de SportXtreme, perfecto para atletas que buscan ligereza y máxima resistencia durante la actividad física.
 ## Operaciones y logística
-![image7](//images.ctfassets.net/alneenqid6w5/7u4kwyRsDBKFi1WVu5nV2q/3372b498b4d49932670575ea0b8211ab/image7.png)
+![image7](https://images.ctfassets.net/alneenqid6w5/7u4kwyRsDBKFi1WVu5nV2q/3372b498b4d49932670575ea0b8211ab/image7.png)
 - **Políticas comerciales**: selecciona una o más [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) para relacionarlas con el producto y determinar en qué marketplaces estará disponible. 
 Si no seleccionas ninguna política comercial, el producto se vinculará a todas ellas de manera predeterminada. Ejemplo: B2C.
 - **Proveedor**: selecciona un proveedor ya registrado en tu tienda para relacionarlo con el producto.
@@ -99,7 +99,7 @@ Si no seleccionas ninguna política comercial, el producto se vinculará a todas
 - **Código fiscal**: ingresa el número de identificación fiscal del producto.
 
 ## Visibilidad
-![image4](//images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)- **Mostrar en el sitio web**: activa o desactiva la visibilidad del producto en tu tienda. Si, por ejemplo, el producto es un regalo que no está disponible para la compra, es importante desactivar esta opción.
+![image4](https://images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)- **Mostrar en el sitio web**: activa o desactiva la visibilidad del producto en tu tienda. Si, por ejemplo, el producto es un regalo que no está disponible para la compra, es importante desactivar esta opción.
 
 - **Mostrar cuando no tenga stock**: activa o desactiva la opción de mostrar el producto en la tienda incluso si está fuera de stock. Si está activada, el producto agotado se mostrará en tu tienda en el formato [Avísame](https://help.vtex.com/es/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e), campo en que el cliente informa su email para ser avisado cuando el producto vuelva a estar disponible.
  Si la opción está desactivada, el producto no se mostrará en la tienda cuando esté agotado.
@@ -112,7 +112,7 @@ Dependiendo de la categoría a la que pertenece el producto que creaste, en la p
 Si creaste algún campo de producto que sea obligatorio, el producto solo podrá activarse una vez que se haya rellenado la especificación.
 
 En la pestaña Atributos se mostrarán los grupos de especificaciones con las especificaciones que registres. Como se puede observar en la imagen, el grupo de especificación es **Características** y las especificaciones registradas son **Video** y **Ver más**.
-![image3](//images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
+![image3](https://images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
 ## SKUs
 
 En esta pestaña, registrarás los [SKUs](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA#) que estarán vinculados al producto que creaste anteriormente. 
@@ -124,7 +124,7 @@ El producto debe tener al menos un SKU activo para estar disponible en tu tienda
 Aquí se mostrarán las especificaciones anteriormente creadas para los SKU. Si creaste algún campo de SKU obligatorio, el SKU solo podrá activarse una vez que se haya rellenado esa especificación. 
 
 ## Información general
-![image2](//images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
+![image2](https://images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
 - **Nombre**: el nombre del SKU que se mostrará en la tienda. Campo obligatorio.
 - **Código de referencia**: código que utilizará la tienda internamente para identificar el SKU. Campo obligatorio si no se ha rellenado el EAN/UPC del SKU.
 - **EAN/UPC**: campo que debe contener la información del código de barras. Campo obligatorio si no se ha rellenado el Código de referencia del SKU.
@@ -138,8 +138,8 @@ Aquí se mostrarán las especificaciones anteriormente creadas para los SKU. Si
 
 Para agregar una imagen al SKU, sigue los pasos a continuación:
 
-1. Haz clic en el botón +.![image8](//images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
-2. Agrega el link a la imagen en el campo 🔗. Puedes añadir más de una imagen a tu SKU. Para hacerlo, haz clic en + Agregar imagen e inserta el nuevo link.![image6](//images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
+1. Haz clic en el botón +.![image8](https://images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
+2. Agrega el link a la imagen en el campo 🔗. Puedes añadir más de una imagen a tu SKU. Para hacerlo, haz clic en + Agregar imagen e inserta el nuevo link.![image6](https://images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
 3. Haz clic en `Guardar`.
 
 La primera imagen agregada será la imagen principal del SKU, la que se mostrará en la tienda y en los resultados de búsqueda.</div>
@@ -149,7 +149,7 @@ Para editar los metadatos de una imagen haz clic en el botón <i class="fas fa-e
 También puedes eliminar una imagen haciendo clic en el botón <i class="fas fa-ellipsis-v"></i> y seleccionando<i class="fas fa-trash-alt"></i> `Eliminar`.
 
 ## Peso y dimensiones
-![image1](//images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
+![image1](https://images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
 ### Peso y dimensiones de envío
 - **Peso del paquete**: peso del paquete vacío en kilogramos. Campo obligatorio.
 - **Anchura del paquete**: ancho del paquete en centímetros. Campo obligatorio.
@@ -168,7 +168,7 @@ También puedes eliminar una imagen haciendo clic en el botón <i class="fas fa-
 - **Multiplicador de unidad**: unidad numérica que multiplica la cantidad seleccionada del producto cuando se agrega al carrito. Si el multiplicador es 5, el producto se añadirá en múltiplos de 5, es decir, 5, 10, 15, 20, sucesivamente. 
 
 ## Configuración avanzada
-![image5](//images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
+![image5](https://images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
 - **Activar kit**: los SKU que componen un kit solo pueden venderse juntos. Puedes hacer que un SKU forme parte de un kit <i class="fas fa-toggle-on"></i> o no <i class="fas fa-toggle-off"></i>.
 - **Generar crédito en tarjeta de regalo**: crédito que recibe el cliente al completar la compra de un SKU determinado. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
 
diff --git a/docs/tutorials/es/customer-credit-overview.md b/docs/tutorials/es/customer-credit-overview.md
index fcfa845d8..781f9df91 100644
--- a/docs/tutorials/es/customer-credit-overview.md
+++ b/docs/tutorials/es/customer-credit-overview.md
@@ -40,7 +40,7 @@ Cuando se instala, el Customer Credit aparece como una opción de pago en el mom
 
 Vea a continuación el flujo básico de cómo funciona el Customer Credit en las tiendas VTEX:
 
-![GIF_CC_ES](//images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/99a8ceaf503fd3154ab5e2aa9b2f3021/GIF_CC_ES.gif)
+![GIF_CC_ES](https://images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/99a8ceaf503fd3154ab5e2aa9b2f3021/GIF_CC_ES.gif)
 
 ## Definiciones en Customer Credit
 
diff --git a/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md b/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md
index 13ec4ba7a..e3d9403fb 100644
--- a/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md
+++ b/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md
@@ -15,7 +15,7 @@ legacySlug: personalizando-las-paginas-del-checkout-confirmation
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-![Página de confirmação de pedido (Order Placed)](//images.contentful.com/alneenqid6w5/n7VvdVmseGQyGwCEQAIiW/90bd066111747fe05d722e6fad172d14/cconf-hml1.png) 
+![Página de confirmação de pedido (Order Placed)](https://images.contentful.com/alneenqid6w5/n7VvdVmseGQyGwCEQAIiW/90bd066111747fe05d722e6fad172d14/cconf-hml1.png) 
 
 Con la nueva sección de Mis Pedidos viene una nueva página de confirmación de pedido, que ahora es parte del **Checkout Confirmation**, feature responsable por las páginas de confirmación del Checkout.
 
@@ -25,7 +25,7 @@ Además de la orden colocada, otra página es el Order Changed, que muestra la c
 
 Al igual que en versiones anteriores, la página de Order Placed (y también la de Order Changed) acepta **templates de HTML**:
 
-![Página de confirmação de pedido com imports de HTML](//images.contentful.com/alneenqid6w5/2HXuJJE5yMCUIaeCMoOOa8/1e947bf46ec9202214867219ba36677a/cconf-html-2.png)
+![Página de confirmação de pedido com imports de HTML](https://images.contentful.com/alneenqid6w5/2HXuJJE5yMCUIaeCMoOOa8/1e947bf46ec9202214867219ba36677a/cconf-html-2.png)
  
 Para añadir su código a estes templates, basta con acceder al módulo Portal y, en la pestaña **Code**, editar los siguientes archivos:
 
@@ -34,7 +34,7 @@ Para añadir su código a estes templates, basta con acceder al módulo Portal y
 - **checkout-confirmation-header**
 - **checkout-confirmation-top**
 
-![Página do Portal v2 com arquivos de template corretos destacados](//images.contentful.com/alneenqid6w5/5jGk1WbMqkkggyAog66iAs/c1162190ef431b8c96462fb34355aa98/cconf-html3.png)
+![Página do Portal v2 com arquivos de template corretos destacados](https://images.contentful.com/alneenqid6w5/5jGk1WbMqkkggyAog66iAs/c1162190ef431b8c96462fb34355aa98/cconf-html3.png)
 
 Es importante recordar que los templates para personalización son los mismos para Order Placed y Order Confirmation.
 
@@ -44,7 +44,7 @@ Es importante recordar que los templates para personalización son los mismos pa
 
 También se puede editar la interfaz del Checkout Confirmation mediante clases CSS. Sus estilos se deben agregar en una tag `<style>` en uno de los templates HTML cargadas en la página.
 
-![Página de OrderPlaced do Checkout Confirmation com classes de customização marcadas](//images.contentful.com/alneenqid6w5/OgLXDC0eyaOc4iKGmSkgS/a698e4da05726f33659d0ea88d0b1278/cconf-doc-2.png)
+![Página de OrderPlaced do Checkout Confirmation com classes de customização marcadas](https://images.contentful.com/alneenqid6w5/OgLXDC0eyaOc4iKGmSkgS/a698e4da05726f33659d0ea88d0b1278/cconf-doc-2.png)
 
 Para personalizar los estilos del Checkout Confirmation, utilize las clases abajo:
 
diff --git a/docs/tutorials/es/customizing-the-my-orders-section.md b/docs/tutorials/es/customizing-the-my-orders-section.md
index 617b1baad..176cccc5d 100644
--- a/docs/tutorials/es/customizing-the-my-orders-section.md
+++ b/docs/tutorials/es/customizing-the-my-orders-section.md
@@ -34,7 +34,7 @@ En el caso de que poseas un archivo de customización para la antigua versión d
 
 ### Lista de pedidos
 
-![Página de lista del pedido con clases para customización en destaque](//images.contentful.com/alneenqid6w5/1P5JMzt3jGIAKIOmC4ka4e/d7511d7273f4a957acc6f7e1322a81e6/my-orders-doc-1.png)
+![Página de lista del pedido con clases para customización en destaque](https://images.contentful.com/alneenqid6w5/1P5JMzt3jGIAKIOmC4ka4e/d7511d7273f4a957acc6f7e1322a81e6/my-orders-doc-1.png)
 
 CSS:
 ```
@@ -69,7 +69,7 @@ CSS:
 
 ### Detalle del Pedido
 
-![Página de detalles del pedido con clases para customización en destaque](//images.contentful.com/alneenqid6w5/CF8gDhZGeG2qYK44AKW68/6a46176cb65fa479f1687fd82a3bfd12/my-orders-doc-2.png)
+![Página de detalles del pedido con clases para customización en destaque](https://images.contentful.com/alneenqid6w5/CF8gDhZGeG2qYK44AKW68/6a46176cb65fa479f1687fd82a3bfd12/my-orders-doc-2.png)
 
 CSS:
 ```
@@ -84,7 +84,7 @@ CSS:
 
 ### Cancelación de pedido
 
-![Página de cancelación del pedido con clases para customización en destaque](//images.contentful.com/alneenqid6w5/1WTQWTszjSqasKY82KuemC/56ca4c3e5a1264d35d40b8753f473065/my-orders-doc-3.png)
+![Página de cancelación del pedido con clases para customización en destaque](https://images.contentful.com/alneenqid6w5/1WTQWTszjSqasKY82KuemC/56ca4c3e5a1264d35d40b8753f473065/my-orders-doc-3.png)
 
 CSS:
 ```
diff --git a/docs/tutorials/es/customizing-your-stores-typography.md b/docs/tutorials/es/customizing-your-stores-typography.md
index 38870d9c2..447eecea4 100644
--- a/docs/tutorials/es/customizing-your-stores-typography.md
+++ b/docs/tutorials/es/customizing-your-stores-typography.md
@@ -27,7 +27,7 @@ En el Admin, tienes la flexibilidad de personalizar la tipografía de tu tienda
 1. En el Admin VTEX, accede a **Storefront > Styles (Estilos)**.
 2. Selecciona el ícono de kebab (tres puntos).
 
-![Styles - More Options ES](//images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/f58a158cd09d76ad56efc3876b742e2e/styles-two-es.png)
+![Styles - More Options ES](https://images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/f58a158cd09d76ad56efc3876b742e2e/styles-two-es.png)
 
 3. Haz clic en **Edit (Editar) > Typography (Tipografía) > Font Family (Familia de fuentes)**.
 
@@ -51,7 +51,7 @@ Consulta la sección [Tokens de tipo](#type-tokens) para ver más información s
 2. Selecciona el ícono de kebab (tres puntos).
 3. Haz clic en **Edit (Editar) > Typography (Tipografía) >Type Tokens (Tokens de tipo)**.
 
-![Styles - Type tokens ES](//images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/45b1dfaa49adb3535975be65b03938bf/styles-three-es.gif)
+![Styles - Type tokens ES](https://images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/45b1dfaa49adb3535975be65b03938bf/styles-three-es.gif)
 
 4. Elige el token de tipo que deseas personalizar como, por ejemplo, **Heading 1** y haz clic en él.
 
diff --git a/docs/tutorials/es/data-entity.md b/docs/tutorials/es/data-entity.md
index 313daaa0a..e7ac33dab 100644
--- a/docs/tutorials/es/data-entity.md
+++ b/docs/tutorials/es/data-entity.md
@@ -19,7 +19,7 @@ Una entidad de datos es una representación de un conjunto de información sobre
 
 Para ilustrarlo, imaginemos un sistema de control de bibliotecas. Este sistema controla los libros que los clientes pueden tomar prestados. En este ejemplo, los conceptos libro, cliente y préstamo (alquiler) son entidades que poseen informaciones sobre cada una de ellas. Una entidad de datos, por lo tanto, es un grupo de información sobre un determinado concepto.
 
-![data-entity-es](//images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/be338269e04b9d5835cda9a16ec9b601/data-entity-es.png)
+![data-entity-es](https://images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/be338269e04b9d5835cda9a16ec9b601/data-entity-es.png)
 
 Estos conceptos permiten configurar los más diversos escenarios de control de datos en Master Data. De forma predeterminada, se ingresan las siguientes entidades de datos: Cliente, Dirección, Tiendas, etc. Puedes crear todas las entidades de datos que desees para personalizar el entorno de acuerdo con las necesidades de cada tienda.
 
diff --git a/docs/tutorials/es/data-subject-rights.md b/docs/tutorials/es/data-subject-rights.md
index ac8e0f693..08eed48be 100644
--- a/docs/tutorials/es/data-subject-rights.md
+++ b/docs/tutorials/es/data-subject-rights.md
@@ -50,7 +50,7 @@ Para exportar datos de Master Data v1 a través del dashboard del Admin, sigue l
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Storefront** > **Master Data**.
 2. Haz clic en la pestaña **Applications**.
 3. Haz clic en el ícono de visualizar (derecha) de la entidad de datos deseada.
-![Master Data botón](//images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/fe25569f2fe5847e02eefdd165c3f95e/visualizar_bot__o_master_data_EN.png)
+![Master Data botón](https://images.ctfassets.net/alneenqid6w5/oYSaPi7x9Vlr4EAiufbew/fe25569f2fe5847e02eefdd165c3f95e/visualizar_bot__o_master_data_EN.png)
 4. Utiliza el [filtro de Master Data v1](https://help.vtex.com/es/tutorial/filtering-data-on-master-data--tutorials_778) para obtener solo los datos del usuario deseado. Utiliza `email` o `User ID` como campo del filtro.
 5. Haz clic en el botón `Export XLS`.
 6. Selecciona la opción `Select all fields`.
diff --git a/docs/tutorials/es/deactivating-store-skus-and-products.md b/docs/tutorials/es/deactivating-store-skus-and-products.md
index 0d934a302..f4fcc0627 100644
--- a/docs/tutorials/es/deactivating-store-skus-and-products.md
+++ b/docs/tutorials/es/deactivating-store-skus-and-products.md
@@ -25,4 +25,4 @@ Para desactivar el SKU de un producto, seguir los pasos a continuación:
 4. Haga clic en el SKU que se desea desactivar.
 5. Desmarque la opción __Activar el SKU si es posible__.
 
-![inactivarSKU](//images.contentful.com/alneenqid6w5/4On7ZXJXPyAUqqy2GaGEuu/04ebceeab81b47272be45f16679c7597/inativarSKU.png)
+![inactivarSKU](https://images.contentful.com/alneenqid6w5/4On7ZXJXPyAUqqy2GaGEuu/04ebceeab81b47272be45f16679c7597/inativarSKU.png)
diff --git a/docs/tutorials/es/declining-order-cancelation.md b/docs/tutorials/es/declining-order-cancelation.md
index 486e3a06e..6af90b769 100644
--- a/docs/tutorials/es/declining-order-cancelation.md
+++ b/docs/tutorials/es/declining-order-cancelation.md
@@ -35,7 +35,7 @@ No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--t
 
 En la siguiente imagen puedes consultar cómo se desarrolla la denegación de las solicitudes de cancelación del pedido, una vez finalizado el periodo de cancelación:
 
-![cancel_api_improvements_help_center_ES_v2](//images.ctfassets.net/alneenqid6w5/68eCO8cFvRz9NsvLaalNMe/716a0f4775bc8418b72578fd1e384130/cancel_api_improvements_help_center_ES_v2.png)
+![cancel_api_improvements_help_center_ES_v2](https://images.ctfassets.net/alneenqid6w5/68eCO8cFvRz9NsvLaalNMe/716a0f4775bc8418b72578fd1e384130/cancel_api_improvements_help_center_ES_v2.png)
 
 La descripción de cada paso es la siguiente:
 
@@ -71,11 +71,11 @@ Para denegar una solicitud de cancelación del pedido a través del Admin VTEX,
 2. Selecciona el pedido deseado para acceder a la [página de información del pedido](https://help.vtex.com/es/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl).
 3. En la parte superior de la página, haz clic en `Denegar`.
 
-  ![deny cancel request](//images.ctfassets.net/alneenqid6w5/53kKd5oNkEjeziq9XR4yvO/19f9b7716df1f0e011b11850d3866e13/deny_cancel_request_ES.png)
+  ![deny cancel request](https://images.ctfassets.net/alneenqid6w5/53kKd5oNkEjeziq9XR4yvO/19f9b7716df1f0e011b11850d3866e13/deny_cancel_request_ES.png)
 
 4. Ingresa en el campo Solicitud de cancelación el motivo por el que se deniega la solicitud de cancelación del pedido.
 
-  ![deny cancel request reason](//images.ctfassets.net/alneenqid6w5/1okkX2L4JdZ57qcdZ758O4/fae33faa395d0aa0c51b2cd645bbf2f8/deny_cancel_request_reason_ES.png)
+  ![deny cancel request reason](https://images.ctfassets.net/alneenqid6w5/1okkX2L4JdZ57qcdZ758O4/fae33faa395d0aa0c51b2cd645bbf2f8/deny_cancel_request_reason_ES.png)
 
   <div class="alert alert-warning">
 Atención: el cliente puede recibir el mensaje que ingreses en este campo a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi cuenta</a> o a través del marketplace.
diff --git a/docs/tutorials/es/defining-product-prices.md b/docs/tutorials/es/defining-product-prices.md
index a43aea421..7d2135ebb 100644
--- a/docs/tutorials/es/defining-product-prices.md
+++ b/docs/tutorials/es/defining-product-prices.md
@@ -17,4 +17,4 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Ya con los productos registrados, es necesario definir sus precios de venta. Ellos pueden ser limitados por UTMs o incluso tener fechas de inicio y fin.
 
-<video class="wp-video-shortcode" id="video-2553-12" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4?_=12" />[//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4](//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4 "//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4")</video>
+<video class="wp-video-shortcode" id="video-2553-12" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4?_=12" />[//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4](https://assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4 "//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4")</video>
diff --git a/docs/tutorials/es/defining-window-displays.md b/docs/tutorials/es/defining-window-displays.md
index deee3799a..ff3b7f976 100644
--- a/docs/tutorials/es/defining-window-displays.md
+++ b/docs/tutorials/es/defining-window-displays.md
@@ -27,7 +27,7 @@ Realizadas las debidas definiciones, el vínculo de la colección con la vitrina
 
 En el ejemplo abajo, vamos a definir la vitrina presentada en la Home, siendo así, se debe realizar la modificación en el siguiente layout:
 
-![cms_layout_home ](//images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
+![cms_layout_home ](https://images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
 
 En el layout seleccionado, agregue el control correspondiente a la vitrina en la que desea exhibir la colección haciendo clic en **Add object**.
 
@@ -35,19 +35,19 @@ Después de seleccionar el tipo de control deseado, defina su nombre y haga clic
 
 **No olvide guardar las configuraciones hechas en "Save Settings" para que pueda editar el control creado.**
 
-![ed](//images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
+![ed](https://images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
 
 ### Edición del control
 
 Para editar sus controles, haga clic en el **símbolo de lápiz**, como se muestra en la siguiente imagen de ejemplo:
 
-![banner_edit_cms](//images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
+![banner_edit_cms](https://images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
 
 Al editar el control es necesario agregar sus contenidos, que representan cada conjunto de ítems que será exhibido.
 Para eso, haga clic en **Add content**
 
-![cadastro_conteudo_cms ](//images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
-![cadastro_conteudo_cms 2](//images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
+![cadastro_conteudo_cms ](https://images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
+![cadastro_conteudo_cms 2](https://images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
 
 - **"Adicionar arquivo" (Agregar archivo):** para seleccionar la colección que aparecerá en ese contenido.
 - **Partner / Campaign / Source:** define la visualización de ese contenido si el visitante tiene alguna UTM correspondiente en su URL de origen.
@@ -63,7 +63,7 @@ Se debe marcar la opción **Active Content** y hacer clic en **Add content list*
 
 si el contenido necesita ser editado, basta con hacer clic en el segundo símbolo de lápiz como se muestra en la siguiente imagen:
 
-![edit_content_cms](//images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
+![edit_content_cms](https://images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
 
 Al realizar los cambios deseados, haga clic en **Update Content List** y guarda todas las configuraciones hechas haciendo clic en **Save Settings** después.
 
diff --git a/docs/tutorials/es/deleting-a-category.md b/docs/tutorials/es/deleting-a-category.md
index 73375c2cc..f26bffe6e 100644
--- a/docs/tutorials/es/deleting-a-category.md
+++ b/docs/tutorials/es/deleting-a-category.md
@@ -26,7 +26,7 @@ Para que una categoría no les aparezca a los clientes de la tienda, puede inact
 3. Haga clic en la categoría que desea inactivar.
 4. Haga clic en el botón `Acciones`.
 5. Haga clic en `Editar`.
-6. Desmarque el campo __Activo | Categoría está activa en la tienda__, según se muestra en esta imagen: ![img inativarcategoria ES](//images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/32994a6c1018db2d24e5acca0e2dcce0/img_inativarcategoria_ES.png)
+6. Desmarque el campo __Activo | Categoría está activa en la tienda__, según se muestra en esta imagen: ![img inativarcategoria ES](https://images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/32994a6c1018db2d24e5acca0e2dcce0/img_inativarcategoria_ES.png)
 7. Haga clic en `Guardar`.
 
 ## Eliminar todas las categorías
diff --git a/docs/tutorials/es/deleting-a-folder-from-cms.md b/docs/tutorials/es/deleting-a-folder-from-cms.md
index e55610b99..8c149548b 100644
--- a/docs/tutorials/es/deleting-a-folder-from-cms.md
+++ b/docs/tutorials/es/deleting-a-folder-from-cms.md
@@ -25,7 +25,7 @@ Para borrar una carpeta de CMS, siga los pasos abajo:
 3. Haga clic en el web site que contiene la carpeta que desea borrar y luego en la carpeta raíz (/).
 4. En la línea de la carpeta que desea borrar, haga clic en __delete__.
 
-![erroDeletarPasta2](//images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
+![erroDeletarPasta2](https://images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
 
 <div class = "alert alert-danger">
 Algunas carpetas son obligatorias. Su tienda no funcionará correctamente sin ellas. Otras son importantes, así que no es una buena idea borrarlas.<br><br>Para entender mejor este asunto, lea el artículo <a href="http://help.vtex.com/es/tutorial/estructura-de-carpetas-de-cms">Estructura de carpetas de CMS</a>.
@@ -33,6 +33,6 @@ Algunas carpetas son obligatorias. Su tienda no funcionará correctamente sin el
 
 Si una carpeta contiene otras carpetas, antes de borrarla es necesario borrar todas las carpetas internas. En caso contrario, el sistema devuelve el error "Object reference not set to an instance of an object", como en la siguiente imagen.
 
-![erroDeletarPasta](//images.contentful.com/alneenqid6w5/6g2MBbZJUQUQM2YQQ88MQE/9159df93c82fc1e89199aaf1922a5044/erroDeletarPasta.png)
+![erroDeletarPasta](https://images.contentful.com/alneenqid6w5/6g2MBbZJUQUQM2YQQ88MQE/9159df93c82fc1e89199aaf1922a5044/erroDeletarPasta.png)
 
 Por ejemplo, si desea borrar la carpeta A, y dentro de ella quedan las carpetas A1 y A2, primero borre las carpetas A1 y A2, y luego borre la carpeta A.
diff --git a/docs/tutorials/es/detaching-skus-by-specification.md b/docs/tutorials/es/detaching-skus-by-specification.md
index 0d0048ea2..e60cfe626 100644
--- a/docs/tutorials/es/detaching-skus-by-specification.md
+++ b/docs/tutorials/es/detaching-skus-by-specification.md
@@ -25,7 +25,7 @@ Esta herramienta se recomienda, principalmente, para las tiendas de ropa, porque
 
 A continuación, vea un ejemplo de separación de SKUs por color. La sandalia que se destaca en la siguiente imagen se exhibe en dos colores en el resultado de la búsqueda:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.</p></div>
diff --git a/docs/tutorials/es/disable-cloudflare-proxy.md b/docs/tutorials/es/disable-cloudflare-proxy.md
index 6d0d3c171..6e275e8c2 100644
--- a/docs/tutorials/es/disable-cloudflare-proxy.md
+++ b/docs/tutorials/es/disable-cloudflare-proxy.md
@@ -21,7 +21,7 @@ Como consecuencia, el sitio web puede quedar fuera de línea. Si el dominio est
 
 Para desactivar el proxy de CloudFlare (y, en consecuencia, deshabilite los servicios CDN y WAF de CloudFlare), entra en tu cuenta de Cloudflare y haz clic en el botón **DNS**. En el __*panel DNS management*__, haz clic en el ícono de la nube naranja debajo de __*Proxy status*__ para cada entrada de DNS que debe apuntar a VTEX. 
 
-![Configuración de proxy de Cloudflare](//images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/7b76e3396ed5b27b0c14ae76bb77b76a/DNS_Management.png)
+![Configuración de proxy de Cloudflare](https://images.ctfassets.net/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/7b76e3396ed5b27b0c14ae76bb77b76a/DNS_Management.png)
 
 Observa que si el proxy está activado, el ícono será de color naranja con el texto __*Proxied*__. De lo contrario, el ícono se mostrará en gris con el texto __*DNS Only*__.
 
diff --git a/docs/tutorials/es/displaying-the-store-in-another-language.md b/docs/tutorials/es/displaying-the-store-in-another-language.md
index 8ad9b7e5f..da0645426 100644
--- a/docs/tutorials/es/displaying-the-store-in-another-language.md
+++ b/docs/tutorials/es/displaying-the-store-in-another-language.md
@@ -17,7 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 Para exhibir la tienda en otro idioma es necesario [crear una nueva Politica Comercial](/es/tutorial/configurar-politica-comercial-para-marketplace/) y relacionarla al idioma deseado por el campo __Culture Info__.
 
-![exibição-loja-idioma-diferente es](//images.ctfassets.net/alneenqid6w5/38du9gVEQomS0Y2sGqMYeW/3abd36c8b8714cb4297c58680499ad62/exibi____o-loja-outra-l__ngua_es.png)
+![exibição-loja-idioma-diferente es](https://images.ctfassets.net/alneenqid6w5/38du9gVEQomS0Y2sGqMYeW/3abd36c8b8714cb4297c58680499ad62/exibi____o-loja-outra-l__ngua_es.png)
 
 Desupués de configurar la política comercial, es necesario un tratamiento en el front-end de su tienda para que cambie el idioma y pronto cambie también la Politicas Comercial. 
 Para eso, es necesario configurar que cada cambio de idioma incluya en la URL el parámetro `?sc=iddelapolíticacomercial` reemplazando __iddelapolíticacomercial__ por el Id de la política comercial registrada que sea relacionada al idioma deseado.
diff --git a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
index 895c2533a..aa8c2a8c5 100644
--- a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -31,7 +31,7 @@ Por el momento, los retailers VTEX solo pueden disponibilizar inventario de anun
 
 En la pantalla de inicio de la aplicación [VTEX Ad Network para retailers](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#retailers), puedes dar seguimiento a los resultados de los anuncios en tu tienda.
 
-![vtex_ad_network_admin_ES](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/2bc7abac921ebb2cf334a5cdaf855e9a/vtex_ad_network_admin.png)
+![vtex_ad_network_admin_ES](https://images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/2bc7abac921ebb2cf334a5cdaf855e9a/vtex_ad_network_admin.png)
 
 En la parte superior se muestran los datos agregados:
 
@@ -62,7 +62,7 @@ También puedes utilizar los filtros disponibles en la parte superior de la tabl
 
 En la tabla de la pantalla principal de la aplicación [VTEX Ad Network para retailers](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#retailers) también puedes hacer clic en la fila de una campaña para ver detalles más específicos.
 
-![vtex_ad_network_details_ES](//images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/f46649cbecca07932a31eaf0216ccb82/vtex_ad_network_details.png)
+![vtex_ad_network_details_ES](https://images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/f46649cbecca07932a31eaf0216ccb82/vtex_ad_network_details.png)
 
 - **Vistas/Clics:** vistas y clics en anuncios.
 - **CTR:** tasa de clics, calculada dividiendo el número de clics entre el número de vistas.
diff --git a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
index 5a9705909..3b112a485 100644
--- a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
@@ -41,7 +41,7 @@ La relevancia manual se configura distribuyendo los pesos en la página **Reglas
 
 1. En el Admin VTEX, accede a **Storefront > Intelligent Search >** **Reglas de relevancia**  o ingresa **Reglas de relevancia** en la barra de búsqueda de la parte superior de la página.
 2. Selecciona la opción **Relevancia manual**.
-![relevancia-manual-es](//images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/eedc0f4e7adac60ba0e457a525c5e642/image.png)
+![relevancia-manual-es](https://images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/eedc0f4e7adac60ba0e457a525c5e642/image.png)
 3. Haz clic en `Guardar`.
 
 Para configurar la relevancia manual, consulta el artículo [Relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
@@ -59,7 +59,7 @@ Para activar la relevancia dinámica, sigue estos pasos:
 1. En el Admin VTEX, accede a **Storefront > Intelligent Search > Reglas de relevancia**  o ingresa **Reglas de relevancia** en la barra de búsqueda de la parte superior de la página.
 2. Lee la información sobre relevancia dinámica y haz clic en `Siguiente`.
 3. Selecciona la opción **Relevancia dinámica**.
-![relevancia-dinamica-es](//images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/d4b2d75e6d45e40ddd06bc9cf1332bcc/image.png)
+![relevancia-dinamica-es](https://images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/d4b2d75e6d45e40ddd06bc9cf1332bcc/image.png)
 4. Haz clic en `Guardar`.
 5. Espera a que la barra de progreso alcance el 100 %. Este proceso puede demorar algunas horas, pero recibirás un email cuando haya finalizado.
 6. Haz clic en `Activar`.
diff --git a/docs/tutorials/es/enable-checkout-v6.md b/docs/tutorials/es/enable-checkout-v6.md
index 5176f1f42..316ca1c90 100644
--- a/docs/tutorials/es/enable-checkout-v6.md
+++ b/docs/tutorials/es/enable-checkout-v6.md
@@ -28,7 +28,7 @@ Para actualizar el checkout de su tienda a la última versión (Checkout v6), de
 5. Haga clic en __Guardar__. 
 6. [Acceda a su tienda en ambiente beta](/tutorial/acceder-al-ambiente-beta--3BHM289568gcSwk2O80Asu) y haga los ajustes de estilo necesarios. El Checkout v6 posee nuevas clases _CSS_ que debem ser llevadas en consideración para personalización del estilo.
 
-![Checkoutv6_box](//images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/dbef571b8ec2baed5bbc8546effaed82/CheckoutV6_box_ES.png)
+![Checkoutv6_box](https://images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/dbef571b8ec2baed5bbc8546effaed82/CheckoutV6_box_ES.png)
 
 ## Activar el Checkout v6 en Ambiente de Producción
 
@@ -42,7 +42,7 @@ Después de realizar los ajustes necesarios en el ambiente de prueba, puede inic
 
 Después de este paso, el Checkout v6 estará instalado en su tienda.
 
-![checkoutv6_box_2](//images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/a3606a1f0b82a825c4625e19c83086de/CheckoutV6_box2_ES.png)
+![checkoutv6_box_2](https://images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/a3606a1f0b82a825c4625e19c83086de/CheckoutV6_box2_ES.png)
 
 ## ¿Cómo verificar si el Checkout v6 fue instalado correctamente?
 
diff --git a/docs/tutorials/es/enabling-2-factor-authentication-login.md b/docs/tutorials/es/enabling-2-factor-authentication-login.md
index 688de1d50..4351f5e97 100644
--- a/docs/tutorials/es/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/es/enabling-2-factor-authentication-login.md
@@ -34,7 +34,7 @@ Existen dos opciones de autenticación, a través de:
 - Clave generada por una __aplicación__ de autenticación.
 - Clave enviada por mensaje de celular (__SMS__).
 
-![2FA - Select - ES](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
+![2FA - Select - ES](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
 
 <div class="alert alert-danger">
 Recomendamos enfáticamente que <strong>elija la opción de autenticación por aplicación</strong>, toda vez que en la autenticación por SMS usted depende de que no haya fallas en el servicio de su operador de telefonía. A través de la aplicación, la clave de acceso siempre estará disponible cuando sea necesaria.
@@ -49,17 +49,17 @@ Si configuró 2FA por SMS y el código está tardando en llegar, posiblemente es
 Para utilizar una clave generada a través de la aplicación de autenticación:
 1. Descargue la aplicación **Google Autenticator** ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)). 
 
-![2FA - App Download - ES](//images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
+![2FA - App Download - ES](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/69d034a2d68aad9a59febf1e29fc2b5b/2FA_-_App_Download_-_ES.png)
 
 2. Utilice la aplicación para leer el código QR a través de la cámara del celular.
 
-![mfa código](//images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/d930110f1a75a7cdb78f8650e0771df8/mfa_qr_code_correction_es.jpg)
+![mfa código](https://images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/d930110f1a75a7cdb78f8650e0771df8/mfa_qr_code_correction_es.jpg)
 
 3. Su cuenta VTEX se agregará a la aplicación, que generará un código de 6 dígitos. Ingrese ese código para finalizar su inicio de sesión.
 
   *El código de la app se actualiza periódicamente. No es necesario que lo memorice, solo debe consultar la aplicación cuando lo necesite.*
 
-![2FA - App Insert Code - ES](//images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
+![2FA - App Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
 
 <div class="alert alert-info">
 Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso <strong> cada 3 días</strong>. Cuando eso suceda, basta con consultar el código en la aplicación.
@@ -71,11 +71,11 @@ Para utilizar una clave enviada a través de mensaje de texto:
 
 1. Ingrese su número de celular para que le enviemos el código por SMS, no olvide colocar el código de país y área. 
 
-![2FA - SMS Insert Phone - ES](//images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
+![2FA - SMS Insert Phone - ES](https://images.ctfassets.net/alneenqid6w5/116sok6Zd8sq69UPSSzs1w/283dc2bac7fe017b977ea1c801364837/2FA_-_SMS_Insert_Phone_-_ES.png)
 
 2. Usted recibirá un mensaje de texto de VTEX en el celular indicado. Ingrese la clave de 6 dígitos para finalizar su inicio de sesión.
 
-![2FA - SMS Insert Code - ES](//images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
+![2FA - SMS Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
 
 <div class="alert alert-warning">
 No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o <a href="#habilitar-o-2fa-por-aplicativo">habilitar 2FA a través de la aplicación</a>.
@@ -91,11 +91,11 @@ Para modificar la configuración de la verificación en dos etapas:
 
 1. Acceda a su configuración de usuario, haciendo clic en el círculo con sus iniciales en el lado superior derecho del Admin. 
 
-![2FA - User Initials - ES](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
+![2FA - User Initials - ES](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/21a91ab5aa3cb4c24c2cdc4fbcdba433/2FA_-_User_Initials_-_ES.png)
 
 2. Haga clic en **Verificación en 2 pasos** para ver su configuración.
 
-![2FA - My User - ES](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
+![2FA - My User - ES](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/cce01cd4ece9a83cfae7d8fdbdf9b286/2FA_-_My_User_-_ES.png)
 
 3. Usted también puede modificar su configuración siguiendo pasos similares a los anteriores para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) y por [aplicación](#habilitar-o-2fa-por-aplicativo).
 
diff --git a/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
index 0714f394e..8ebafd4e5 100644
--- a/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
@@ -35,6 +35,6 @@ En este tutorial, le explicaremos cómo realizar esta integración a través del
 4. Desplácese hacia abajo y active la opción __3DS Enabled__. 
 5. Haga clic en __Salva__.
 
-![RedsysV2 ES](//images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/6e85fe90224d28365930fe21c4c673aa/Redsys_3DS2_-_ES.png)
+![RedsysV2 ES](https://images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/6e85fe90224d28365930fe21c4c673aa/Redsys_3DS2_-_ES.png)
 
 Una vez hecho esto, la solución se habilitará para las transacciones con tarjeta de crédito de Redsýs.
diff --git a/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
index 11d88b787..df836ef06 100644
--- a/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -77,7 +77,7 @@ Deberás seleccionar un vendedor de la tienda en la que quieras probar Venta en
 1. Tras [seleccionar un vendedor](https://help.vtex.com/es/tutorial/vendedores-instore-beta--4rzit1pzp28km4HSDEdrEC), accede a Sales App e inicia sesión.
 2. Busca un ítem que exista en el almacén de la cuenta franquicia registrada. Este ítem debe mostrar la cantidad disponible correspondiente en el stock del seller.
 
-![instore-pdp-es](//images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/b2feab0b2eb3c3893ed654801743e5cd/image.png)
+![instore-pdp-es](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/b2feab0b2eb3c3893ed654801743e5cd/image.png)
 
 <div class="alert alert-info">
 <p>Si has habilitado el stock infinito, el número mostrado será superior a 1 millón de ítems y no cambiará cuando se complete una venta.</p>
@@ -92,9 +92,9 @@ También puedes configurar la Venta en mano para ignorar la cantidad de ítems e
 2. Haz clic en el botón del engranaje <i class="fas fa-cog"></i> para editar.
 3. Selecciona la pestaña **Código**.
 4. En la pestaña lateral, selecciona `checkout-instore-custom-js`.
-![instore-custom-js-es](//images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/50b77b80f4cba77048ea3454cda557bc/image.png)
+![instore-custom-js-es](https://images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/50b77b80f4cba77048ea3454cda557bc/image.png)
 5. En la clave `window.INSTORE_CONFIG`, agrega la flag `venderSinStockEnMano: true`.
-![sellWithoutStockInHands-es](//images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/d4f24d0e6eef4783be120f6533c3a6f0/image.png)
+![sellWithoutStockInHands-es](https://images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/d4f24d0e6eef4783be120f6533c3a6f0/image.png)
 6. Haz clic en <i class="fas fa-save"></i> `Guardar`.
 
 ### Habilitar la venta con carrito mixto (opcional)
diff --git a/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md b/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md
index 09bcb2249..f6e49d082 100644
--- a/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md
+++ b/docs/tutorials/es/enabling-pwa-push-notifications-in-your-store.md
@@ -17,7 +17,7 @@ subcategory: 7ogirQ8NClawO2X6xdgCKc
 
 Todas las tiendas VTEX IO disponen de forma nativa de una Progressive Web App (PWA). Una PWA es un tipo de aplicación web que se utiliza para promover de forma nativa recursos beneficiosos para los usuarios, como funcionalidades offline o un ícono en la pantalla de inicio.
 
-![pwa-noticees](//images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/85250a88ec6b95a39839de71dfdf60ef/Screenshot_162.png)
+![pwa-noticees](https://images.ctfassets.net/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/85250a88ec6b95a39839de71dfdf60ef/Screenshot_162.png)
 
 La PWA puede estar disponible para instalación en tres momentos distintos de la experiencia de navegación del usuario: durante la primera visita al sitio web de su tienda, al añadir el primer ítem al carrito o al finalizar la primera compra.
 Vea cómo configurar la notificación en su tienda siguiendo los pasos a continuación.
diff --git a/docs/tutorials/es/entering-tax-receipts-in-the-order.md b/docs/tutorials/es/entering-tax-receipts-in-the-order.md
index 7a0130794..1363efdd2 100644
--- a/docs/tutorials/es/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/es/entering-tax-receipts-in-the-order.md
@@ -19,7 +19,7 @@ Ese es el procedimiento después del manejo del pedido: la creación de la nota
 
 Para hacerlo manualmente por **Gestión de pedidos**, basta hacer clic en el botón `Facturar Paqueta`, como en la imagen abajo.
 
-![faturar-pedido-ex es](//images.ctfassets.net/alneenqid6w5/3JeHgjEDtmm4ksSwamsW2W/d49ebe8fa3ea9e920e8d52f530182895/ex_1_es.png)
+![faturar-pedido-ex es](https://images.ctfassets.net/alneenqid6w5/3JeHgjEDtmm4ksSwamsW2W/d49ebe8fa3ea9e920e8d52f530182895/ex_1_es.png)
 
 Con la inserción de la nota fiscal con el valor completo del pedido, él pasará para el status **Facturado.**
 
diff --git a/docs/tutorials/es/excluding-a-product-from-the-store.md b/docs/tutorials/es/excluding-a-product-from-the-store.md
index b2ce5082f..715de9c6d 100644
--- a/docs/tutorials/es/excluding-a-product-from-the-store.md
+++ b/docs/tutorials/es/excluding-a-product-from-the-store.md
@@ -27,6 +27,6 @@ Sin embargo, una vez que el producto en cuestión tenga alguna referencia a otra
 
 En este caso, el siguiente mensaje de error aparece al intentar excluirlo:
 
-![erroExcluir](//images.contentful.com/alneenqid6w5/19vbt8GlfOK0IMEMEo86Gu/75d44c69a5d553d485daa668d1ab19bc/erroExcluir.png)
+![erroExcluir](https://images.contentful.com/alneenqid6w5/19vbt8GlfOK0IMEMEo86Gu/75d44c69a5d553d485daa668d1ab19bc/erroExcluir.png)
 
 La solución es desactivar el producto. Ver cómo en el artículo [Desactivar SKUs y productos de la tienda](/es/tutorial/desactivar-skus-y-productos-de-la-tienda).
diff --git a/docs/tutorials/es/explained-search.md b/docs/tutorials/es/explained-search.md
index 65d936fe7..6b87ee0eb 100644
--- a/docs/tutorials/es/explained-search.md
+++ b/docs/tutorials/es/explained-search.md
@@ -27,5 +27,5 @@ Siga las instrucciones a continuación para acceder a la página:
 1. En el Admin VTEX, acceda a __Storefront__, o escribe __Storefront__ en la barra de búsqueda en la parte superior de la página.
 2. En **Intelligent Search**, haga clic en **Explicación de la búsqueda**. 
 
-![Explicación de Búsqueda](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
+![Explicación de Búsqueda](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/589679e005025dbb372ce53223940673/explicacion_de_la_busqueda.png)
 
diff --git a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
index c6ba19cd0..b5060d309 100644
--- a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
@@ -32,14 +32,14 @@ Vea a continuación cómo exportar la plantilla con las especificaciones del pro
 1. En el Admin VTEX, accede a **Catálogo**, o escribe **Catálogo** en la barra de búsqueda en la parte superior de la página.
 2. Haz clic en **Importación y exportación**.
 3. Haz clic en la pestaña __Especificaciones de producto__ o **Especificaciones de SKU**, en función de sus necesidades.
-    ![skuexport1.es](//images.ctfassets.net/alneenqid6w5/6dlUefWP7lw3FzqWZjcLet/1d604f16ca07a32db13bdb1a3d52836a/skuexport1.es.png)
+    ![skuexport1.es](https://images.ctfassets.net/alneenqid6w5/6dlUefWP7lw3FzqWZjcLet/1d604f16ca07a32db13bdb1a3d52836a/skuexport1.es.png)
 4. Haz clic con el botón derecho en la categoría deseada.
     No puede exportar especificaciones de todas las categorías a la vez. Debe elegir sólo una categoría cuyas especificaciones desee exportar. 
 5. Haz clic en `Exportar`.
     Aparecerá un rectángulo verde en pantalla.
 6. Haz clic en `Haz clic aquí para descargar el archivo` para exportar la plantilla.
 
-![skuexport2.es](//images.ctfassets.net/alneenqid6w5/6aQThG8rLVv6c48ZAO1in4/eeb2118c25334f4b18d485b2c2127cd5/skuexport2.es.png)
+![skuexport2.es](https://images.ctfassets.net/alneenqid6w5/6aQThG8rLVv6c48ZAO1in4/eeb2118c25334f4b18d485b2c2127cd5/skuexport2.es.png)
 
 <div class = "alert alert-info">
   <p>La hoja de plantilla exportada estará disponible en tu email durante una semana. Si supera este periodo, vuelva a seguir la exportación paso a paso para generar una nueva hoja de plantilla.</p>
@@ -63,7 +63,7 @@ Siga los pasos a continuación para importar la plantilla:
 2. Haz clic en **Seleccionar** para seleccionar el archivo con la plantilla completa en la computadora.
 3.  Haz clic en `Importar`.
 
-![skuexport3.es](//images.ctfassets.net/alneenqid6w5/5IJmGafmCsB9tawXSYAyz1/473921b906075a53364a0018aaf08176/skuexport3.es.png)
+![skuexport3.es](https://images.ctfassets.net/alneenqid6w5/5IJmGafmCsB9tawXSYAyz1/473921b906075a53364a0018aaf08176/skuexport3.es.png)
 
 ## Más información
 - [Especificaciones de producto e de SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
diff --git a/docs/tutorials/es/facebook-faq.md b/docs/tutorials/es/facebook-faq.md
index d713039fa..02e4f3693 100644
--- a/docs/tutorials/es/facebook-faq.md
+++ b/docs/tutorials/es/facebook-faq.md
@@ -37,7 +37,7 @@ Lo primero que debe verificar en este escenario es si el SKU realmente no posee
 
 En el caso de que el SKU posea un precio, verifique el status del SKU porque el error también puede estar relacionado con la situación de activo/inactivo. La mejor manera de hacerlo es realizando una simulación de checkout:
 
-![face faq01](//images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
+![face faq01](https://images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
 
 En esta simulación es importante analizar los campos:  
 
diff --git a/docs/tutorials/es/facilitating-b2b-store-operation.md b/docs/tutorials/es/facilitating-b2b-store-operation.md
index 03fb9626d..3efe0f5df 100644
--- a/docs/tutorials/es/facilitating-b2b-store-operation.md
+++ b/docs/tutorials/es/facilitating-b2b-store-operation.md
@@ -91,7 +91,7 @@ VTEX cuenta con [My account](https://help.vtex.com/es/tutorial/como-funciona-o-m
 
 Esta herramienta permite al consumidor seguir el status de su pedido en el flujo de posventa, así como realizar algunas operaciones. Entre estas, «Pedir nuevamente» para volver a realizar un pedido que se efectuó anteriormente.  
 
-![reorder ES](//images.ctfassets.net/alneenqid6w5/53BeeU3MFPuA26NepAhXrI/708213aadff4d416977f6e5dc6b18638/reorder_ES.png)
+![reorder ES](https://images.ctfassets.net/alneenqid6w5/53BeeU3MFPuA26NepAhXrI/708213aadff4d416977f6e5dc6b18638/reorder_ES.png)
 
 Para saber más detalles de My Account, lea el tutorial sobre [cómo configurar esta funcionalidad](https://help.vtex.com/pt/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1 "cómo configurar esta funcionalidad").
 
diff --git a/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 22c55e9a8..9f427c9b9 100644
--- a/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -17,7 +17,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Para comprender mejor el significado de cada campo de la plantilla de registro de precio fijo, vea la descripción completa de los ítems.
 
-![tabela.preço.fixo](//images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
+![tabela.preço.fixo](https://images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
 
 - **SKU ID:** el ID del SKU al que quiere añadir el precio fijo.
 - **Trade Policy:** el nombre o el ID de la política comercial a la que se aplicará el precio fijo.
diff --git a/docs/tutorials/es/filtering-all-orders.md b/docs/tutorials/es/filtering-all-orders.md
index 81e9cfec9..35cf3072b 100644
--- a/docs/tutorials/es/filtering-all-orders.md
+++ b/docs/tutorials/es/filtering-all-orders.md
@@ -21,7 +21,7 @@ Solo puedes acceder a la información de los pedidos creados en los últimos añ
 
 En el módulo **Pedidos**, la página **Todos los pedidos** permite acceder a todos los pedidos de la tienda y buscar utilizando la barra de búsqueda y filtros según se muestra en la imagen a continuación:
 
-![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Este artículo explica cómo utilizar estos recursos y se divide en:
 
@@ -63,7 +63,7 @@ La búsqueda en todos los pedidos devuelve todos los pedidos relacionados con el
 
 Para buscar en todos los pedidos, ingresa el término deseado en la casilla de búsqueda. Se mostrará la opción <i class="fas fa-toggle-on"></i> `Remover límite de fechas`. Solo hay que activarla para iniciar la búsqueda.
 
-![search_bar_without_time_limit_ES](//images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/3e96ddad7e6e25df9bfc57510655390b/search_bar_without_time_limit_ES.png)
+![search_bar_without_time_limit_ES](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/3e96ddad7e6e25df9bfc57510655390b/search_bar_without_time_limit_ES.png)
 
 <div class="alert alert-danger">
 La búsqueda en todos los pedidos no se puede asociar a otros filtros. Es decir, al remover el límite de fechas de búsqueda, cualquier filtro activo pasa a estar inactivo. Si se remueve el término de búsqueda o se desactiva el botón de alternancia <i class="fas fa-toggle-off"></i>, los filtros configurados anteriormente se vuelven a activar.
@@ -81,7 +81,7 @@ Realizar una búsqueda con filtros permite combinar diferentes filtros que se de
 
 La página **Pedidos > Todos los pedidos** tiene la opción `Filtros` según se muestra en la imagen a continuación:
 
-![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Al hacer clic en `Filtros`, se muestra una ventana modal que presenta las siguientes opciones:
 
@@ -197,7 +197,7 @@ Para utilizar estos filtros, haz `Filtros` y selecciona **Otros**. Puedes buscar
 
 La página **Pedidos > Todos los pedidos** tiene la opción `Filtrar por status` <i class="fas fa-angle-down"></i> según se muestra en la siguiente imagen:
 
-![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Al hacer clic en `Filtrar por status` <i class="fas fa-angle-down"></i>, se muestran las opciones de [status de pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196) de tu tienda. Por ejemplo, si no hay pedidos cancelados entre todos tus pedidos, esta opción no estará visible.
 
@@ -209,7 +209,7 @@ Para más opciones de filtros de status, consulta la sección <a href="https://h
 
 La página **Pedidos > Todos los pedidos** tiene la opción `Creado: Hoy` <i class="fas fa-angle-down"></i> según se muestra en la siguiente imagen:
 
-![search_bar_ES](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
+![search_bar_ES](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/daa7bf97f15445140cba0433da887aa5/search_bar_ES.png)
 
 Este filtro tiene la fecha **Hoy** activada como estándar, pero al hacer clic aparecen las siguientes opciones:
 
diff --git a/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
index e6157f294..e88b290e6 100644
--- a/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -20,7 +20,7 @@ Marketplace Network facilita el encuentro y la comunicación entre marketplaces
 Tenga en cuenta que *Marketplace Network* es una herramienta que promueve el contacto entre partners potenciales, pero no es una etapa obligatoria para convertirse en un *marketplace* o *seller* en VTEX. Sepa más sobre las [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
 ## Encontrar sellers y marketplaces
-![Marketplace network tour](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
+![Marketplace network tour](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
 
 Para acceder a la lista de marketplaces y sellers registrados, vaya a *Marketplace > Marketplace Network > Encontrar sellers / Encontrar marketplaces*. En ambas pestañas, puedes buscar por palabras clave y filtrar la lista para obtener resultados más precisos, así como contactar con potenciales partners.
 
@@ -43,7 +43,7 @@ El potencial partner comercial recibirá un email con la información ingresada.
 </div>
 
 ## Perfil de la tienda
-![Network profile ES](//images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/ae9aa04caa553c344ab6e5f958469e68/Marketplace_store_profile_ES.gif)
+![Network profile ES](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/ae9aa04caa553c344ab6e5f958469e68/Marketplace_store_profile_ES.gif)
 
 1. En la sección «Marketplace» de su tienda, haga clic en __Marketplace Network__.    
 2. Haga clic en la pestaña __Perfil de la tienda__.    
diff --git a/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
index 15d8d7731..bfd39f900 100644
--- a/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
@@ -26,7 +26,7 @@ A partir del 17 de enero de 2023, la nueva interfaz será el estándar de todas
 
 En la imagen a continuación, puedes ver la correspondencia de secciones y campos entre la versión antigua de la página **Detalles del pedido** y la nueva versión:
 
-![board_comparativo_interface_pedido_v2_es](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
+![board_comparativo_interface_pedido_v2_es](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/4a3658c6c470856c0dd37cd708761ff6/board_comparativo_interface_pedido_v2_es.png)
 
 ## ¿Qué pasó con el filtro de búsqueda de seis meses?
 
@@ -38,17 +38,17 @@ La búsqueda en todos los pedidos no puede asociarse a otros filtros, por lo que
 
 Para buscar en todos los pedidos, ingresa el término deseado en la casilla de búsqueda. Se mostrará la opción <i class="fas fa-toggle-off"></i> `Remover límite de fechas`. Solo tienes que activarla para iniciar la búsqueda.
 
-![busca_sem_limite_data_all_es](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
+![busca_sem_limite_data_all_es](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/0a765124f8477dac5a676b872f2a2e7c/busca_sem_limite_data_all_es.png)
 
 ## ¿Cómo ver el diagrama de flujo del pedido?
 
 En la nueva interfaz, el estándar es mostrar una línea de tiempo con los eventos de **Status del pedido** según ilustrado en la siguiente imagen:
 
-![timeline_pedido_es](//images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/60bd22f37e038db53247d83f3252efe1/timeline_pedido_es.png)
+![timeline_pedido_es](https://images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/60bd22f37e038db53247d83f3252efe1/timeline_pedido_es.png)
 
 Si deseas ver el **Diagrama del pedido** como en la interfaz anterior, haz clic en `Ver diagrama` y aparecerá una ventana modal según se muestra en la imagen a continuación:
 
-![diagrama_pedido_es](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
+![diagrama_pedido_es](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/c539ec37111500a217eb429e33a1c9e1/diagrama_pedido_es.png)
 
 ## ¿Cómo facturar el pedido?
 
@@ -56,7 +56,7 @@ En la sección **Ítems a facturar** de la nueva interfaz, se puede acceder a to
 
 * **Enviar factura con la referencia de los ítems:** esta opción solo aparece en la nueva interfaz y permite emitir la factura total o parcial de determinados ítems, que se identifican por SKU, stock y precio. Ve un ejemplo en la siguiente imagen:
 
-![faturar_referenciar_pedidos_final_es](//images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/2427b16f419457736699f1cae0cf3dd3/faturar_referenciar_pedidos_final_es.png)
+![faturar_referenciar_pedidos_final_es](https://images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/2427b16f419457736699f1cae0cf3dd3/faturar_referenciar_pedidos_final_es.png)
 
 * **Enviar una sola factura:** esta opción corresponde a la antigua _Enviar factura_ y permite facturar el valor total o parcial del pedido. La presentación de la página es diferente, pero los campos siguen siendo los mismos.
 
@@ -75,6 +75,6 @@ En la sección **Historial del pedido**, hay una línea de tiempo que presenta l
 
 Para reenviar un email al cliente, haz clic en el evento de email enviado o en el ícono de flecha <i class="fas fa-angle-right"></i> para ver los detalles del evento, que aparecerán como se muestra en la siguiente imagen:
 
-![enviar_email_es](//images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/a4d25f7e071dd7f4c23cbcd157d8008a/enviar_email_es.png)
+![enviar_email_es](https://images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/a4d25f7e071dd7f4c23cbcd157d8008a/enviar_email_es.png)
 
 Haz clic en el botón Reenviar email y se reenviará el email inmediatamente al cliente y se mostrará el siguiente mensaje de confirmación: _El email se reenvió con éxito al cliente_.
diff --git a/docs/tutorials/es/fulfillment-logistics-vtex.md b/docs/tutorials/es/fulfillment-logistics-vtex.md
index 99bbcd7fc..2ee8a8aa3 100644
--- a/docs/tutorials/es/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/es/fulfillment-logistics-vtex.md
@@ -47,7 +47,7 @@ Para saber qué configuraciones logísticas son necesarias y cómo realizarlas,
 <div class = "alert alert-info">Ten en cuenta que el proceso de envío dependerá de la configuración realizada en la plataforma. Aquí presentamos los escenarios para cada tipo de envío (entrega y recogida), pero hay otros flujos posibles en el proceso de envío. Por ejemplo, cuando se realiza el envío por recogida y el almacén coincide con el punto de recogida, no es necesario transportar los paquetes entre estos lugares.
 </div>
 
-![Envio ES](//images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/b45650074aea4947a048e8140434fa46/Envio_ES.svg)
+![Envio ES](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/b45650074aea4947a048e8140434fa46/Envio_ES.svg)
 ## Configuración del proceso logístico
 
 El proceso logístico debe configurarse según las necesidades de tu tienda. Estas configuraciones se hacen en el módulo **Envío**. Mira las funcionalidades disponibles en el módulo y cómo afecta cada una de ellas a tu negocio:
diff --git a/docs/tutorials/es/general-configurations-on-the-oms.md b/docs/tutorials/es/general-configurations-on-the-oms.md
index f8315ce12..de9feefb3 100644
--- a/docs/tutorials/es/general-configurations-on-the-oms.md
+++ b/docs/tutorials/es/general-configurations-on-the-oms.md
@@ -19,7 +19,7 @@ Es posible realizar configuraciones directamente relacionadas con las condicione
 
 En el Admin VTEX, accede a **Configuración de la tienda > Pedidos > Configuración**, o escribe *Pedidos* en la barra de búsqueda en la parte superior de la página, y haga clic en *Configuración de la tienda / Pedidos*.  
 
-![configuracoes_pedidos_es](//images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/228fb71ccb74cc99cb820bac2b5a94d1/configuracoes_pedidos_es.png)
+![configuracoes_pedidos_es](https://images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/228fb71ccb74cc99cb820bac2b5a94d1/configuracoes_pedidos_es.png)
 
 ## Carrito
 
diff --git a/docs/tutorials/es/generating-a-har-file.md b/docs/tutorials/es/generating-a-har-file.md
index 3cdf64439..cf9e6a67e 100644
--- a/docs/tutorials/es/generating-a-har-file.md
+++ b/docs/tutorials/es/generating-a-har-file.md
@@ -34,11 +34,11 @@ Usando Google Chrome, siga estos pasos para generar el archivo HAR.
 
 1. Vaya a la dirección URL donde se produce el problema.
 2. Haga clic con el botón derecho en cualquier lugar de la pantalla y luego en __Inspect__.
-3. El Dev Tools será abierto, entonces haga clic en la pestaña __Network__.![HARfile2](//images.contentful.com/alneenqid6w5/7vSYRmkjduq6iCaiGgyIo/fd3f3eb23fa57582f8c8f5cd1ac725b5/HARfile2.png)
-4. El botón de grabación debe estar rojo, lo que indica que está activado. Si no está, haga clic en él.![HARfile3](//images.contentful.com/alneenqid6w5/6YnW3ebd1mq2kQsm8uKG2q/97000a534abfabc66931d27ff9cd28b8/HARfile3.png)
-5. Marque la flag __Preserve log__.![HARfile5](//images.contentful.com/alneenqid6w5/xQAIiEuHIsaoSCUkSsOEE/e6dc32f580a2f50a5789ae39babfb540/HARfile5.png)
+3. El Dev Tools será abierto, entonces haga clic en la pestaña __Network__.![HARfile2](https://images.contentful.com/alneenqid6w5/7vSYRmkjduq6iCaiGgyIo/fd3f3eb23fa57582f8c8f5cd1ac725b5/HARfile2.png)
+4. El botón de grabación debe estar rojo, lo que indica que está activado. Si no está, haga clic en él.![HARfile3](https://images.contentful.com/alneenqid6w5/6YnW3ebd1mq2kQsm8uKG2q/97000a534abfabc66931d27ff9cd28b8/HARfile3.png)
+5. Marque la flag __Preserve log__.![HARfile5](https://images.contentful.com/alneenqid6w5/xQAIiEuHIsaoSCUkSsOEE/e6dc32f580a2f50a5789ae39babfb540/HARfile5.png)
 6. Vuelva a cargar la página y reproduzca la navegación en la que se produce el problema.
-7. Haga clic con el botón derecho en cualquier lugar dentro del área del Network y, a continuación, haga clic en la opción __Save as HAR with content__.![HARfile4](//images.contentful.com/alneenqid6w5/hR0VTzzNFmyQc4A4KS02G/b1f15e2131e21b80f5f2c97023cd0a5b/HARfile4.png)
+7. Haga clic con el botón derecho en cualquier lugar dentro del área del Network y, a continuación, haga clic en la opción __Save as HAR with content__.![HARfile4](https://images.contentful.com/alneenqid6w5/hR0VTzzNFmyQc4A4KS02G/b1f15e2131e21b80f5f2c97023cd0a5b/HARfile4.png)
 
 Se generará un archivo con extensión HAR, cuyo nombre es la dirección de la página.
 
diff --git a/docs/tutorials/es/geolocation-at-checkout.md b/docs/tutorials/es/geolocation-at-checkout.md
index b389d9a34..8138f7492 100644
--- a/docs/tutorials/es/geolocation-at-checkout.md
+++ b/docs/tutorials/es/geolocation-at-checkout.md
@@ -42,7 +42,7 @@ Cuando tengas la API, siga los pasos adelante:
 1. En el Admin VTEX, accede a __Configuración de la tienda > Envío > Envío por geolocalización__, o escribe __Envío por geolocalización__ en la barra de búsqueda en la parte superior de la página.
 2. Ponga la API Key en el campo disponible y haga un click en __Registrar Llave__.
 
-![Geolocalizacao 1 ES](//images.ctfassets.net/alneenqid6w5/3XL4C5B5SM48uGaeocUiw4/22560c9c40cc587cb7fa0884e48fcd5f/Geolocalizacao_1_ES.png)
+![Geolocalizacao 1 ES](https://images.ctfassets.net/alneenqid6w5/3XL4C5B5SM48uGaeocUiw4/22560c9c40cc587cb7fa0884e48fcd5f/Geolocalizacao_1_ES.png)
 
 <div class="alert alert-info">
 En algunos paises, el Google Maps no hace un mapping de buena calidad, lo que hace con que las direcciones queden mal escritas o incorrectas. En estes casos, la dirección debe ser alterada directamente en el mapa.
@@ -61,7 +61,7 @@ Después de crear el poligono y insertar el ID en la planilla de flete de la tra
 3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Checkout__.
 4. En el campo **Google Maps API Key**, inserte la misma API Key utilizada en la etapa de logística.
 
-![Google map keys](//images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/687470ae8e86c210d778e34057af2a5c/google_maps_api_key_es.PNG)
+![Google map keys](https://images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/687470ae8e86c210d778e34057af2a5c/google_maps_api_key_es.PNG)
 
 Asi que la API Key sea informada en las configuraciónes del Checkout, la geolocalización ya va estar visible en el checkout de la tienda.
 
diff --git a/docs/tutorials/es/google-pay-beta.md b/docs/tutorials/es/google-pay-beta.md
index 8a3e5769b..047935aa9 100644
--- a/docs/tutorials/es/google-pay-beta.md
+++ b/docs/tutorials/es/google-pay-beta.md
@@ -40,7 +40,7 @@ Para activar Google Pay, sigue los pasos a continuación.
 
 Una vez hecho esto, Google Pay estará disponible en el checkout de tu tienda VTEX como nuevo medio de pago. La configuración puede demorarse alrededor de 10 minutos en aparecer en el checkout.
 
-![google pay - ES](//images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/fc1aa919d82b228ed26d2a967f4a4064/image.png)
+![google pay - ES](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/fc1aa919d82b228ed26d2a967f4a4064/image.png)
 
 <div class = "alert alert-warning">
 <p>Google Pay, por el momento, no admite suscripciones.</p>
diff --git a/docs/tutorials/es/google-search-console-tracking-sitemap.md b/docs/tutorials/es/google-search-console-tracking-sitemap.md
index 9ddae98eb..805ad9230 100644
--- a/docs/tutorials/es/google-search-console-tracking-sitemap.md
+++ b/docs/tutorials/es/google-search-console-tracking-sitemap.md
@@ -36,7 +36,7 @@ Para registrar el Sitemap usted deberá de ejecutar las siguientes acciones:
 
 **2. Seleccione la opción de &#8220;Sitemaps&#8221; en el apartado llamado &#8220;Rastreo&#8221;**
 
-****![](//images.contentful.com/alneenqid6w5/4ZbMabhWNO6cWaqOKQauGA/e0a6c544f7990e7203a89c63761ce7ea/image00.png)****
+****![](https://images.contentful.com/alneenqid6w5/4ZbMabhWNO6cWaqOKQauGA/e0a6c544f7990e7203a89c63761ce7ea/image00.png)****
 
 **3. Haga click en el boton &#8220;Añadir o Probar Sitemap&#8221;**
 
@@ -44,13 +44,13 @@ Para registrar el Sitemap usted deberá de ejecutar las siguientes acciones:
 
 **5. **Click en &#8220;Enviar&#8221; **
 
-****![](//images.contentful.com/alneenqid6w5/5WlIFTSGm4MGc6Wg6a24qY/8b1ae91bbedfdd5bcae4e255cd649784/image01.png)****
+****![](https://images.contentful.com/alneenqid6w5/5WlIFTSGm4MGc6Wg6a24qY/8b1ae91bbedfdd5bcae4e255cd649784/image01.png)****
 
 **6. El Search Console tendrá acceso al XML y lo verificara. Haga click en la opcion &#8220;Actualizar pagina&#8221; para ir visualizando los resultados y los status de las urls enviadas por el Sitemap.**
 
-**![](//images.contentful.com/alneenqid6w5/4H9Cm60mooYeeeEy0cOOaW/9d714db622a05eeda0dc52042b83aaf8/image02.png)**
+**![](https://images.contentful.com/alneenqid6w5/4H9Cm60mooYeeeEy0cOOaW/9d714db622a05eeda0dc52042b83aaf8/image02.png)**
 
 **7. Después de agregar con éxito el Sitemap en Search Console, se disponibilizara un reporte de las URLs enviadas versus las URLs indexadas, segmentadas por &#8220;Paginas web&#8221; e &#8220;Imagenes&#8221;**
 
-**![](//images.contentful.com/alneenqid6w5/6e0WHJD0YMCaWIkE4Kcgm/db32fa9488506be988d648554c3e3c42/image03.png)**
+**![](https://images.contentful.com/alneenqid6w5/6e0WHJD0YMCaWIkE4Kcgm/db32fa9488506be988d648554c3e3c42/image03.png)**
 
diff --git a/docs/tutorials/es/headless-cms-overview.md b/docs/tutorials/es/headless-cms-overview.md
index cfa99d44b..13a8ad027 100644
--- a/docs/tutorials/es/headless-cms-overview.md
+++ b/docs/tutorials/es/headless-cms-overview.md
@@ -35,7 +35,7 @@ Con Headless CMS puedes:
 
 [Proyectos](https://help.vtex.com/es/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) es una funcionalidad de Headless CMS que permite crear y gestionar varios proyectos frontend, como aplicaciones móviles, sitios web e email marketing desde un único panel de control. 
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
 
 Para más información, consulta Gestionar Proyectos. 
 
diff --git a/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
index 78ec667e7..eef69f568 100644
--- a/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
@@ -25,7 +25,7 @@ La plataforma VTEX está lista para cambios de domínio sin impactos negativos.
 
 ### 1. Crear nuevas entradas HOST en el License Manager
 En el License Manager, en “Contas”, será necesario incluir el nuevo dominio cómo HOST de la tienda. Todavía el DNS del nuevo dominio no debe estar apuntado para VTEX. En secuencia la imágenes con ejemplo de cómo se hace la inclusión de nuevos HOSTs:
-![Cambiar dominio](//images.ctfassets.net/alneenqid6w5/2mejT2jclm4MSwCoy8SwGo/c305404cae53e6c3bc7e4077f125c366/626-es.png)
+![Cambiar dominio](https://images.ctfassets.net/alneenqid6w5/2mejT2jclm4MSwCoy8SwGo/c305404cae53e6c3bc7e4077f125c366/626-es.png)
 
 ### 2. Fijar las configuraciones del nuevo Portal
 Es paso es fundamental para que el Checkout funcione correctamente.
diff --git a/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
index d2036eaf8..6cfa250f4 100644
--- a/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
@@ -45,7 +45,7 @@ Verifique el procedimiento:
 
 <div class="alert alert-info">Puede encontrar más información sobre <strong>Configuraciones generales</strong> y <strong>Configuraciones de búsqueda y filtro</strong> en la sesión <strong>Cómo configurar</strong> del artículo <a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Crear entidad de datos</a>.</div>
 
-![crear campo master data ds](//images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
+![crear campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
 De este modo, volverá a la página principal de la pestaña Entidad de Datos. Para finalizar, es necesario publicar el campo. Basta localizar la línea de la entidad en la que se agregó el campo y hacer clic en el ícono de disquete.
 
@@ -70,6 +70,6 @@ Dicho esto, prosiga con las instrucciones:
 7. Arrastre el campo de la lista Campos disponibles para las columnas Campos de la columna 1 o Campos de la columna 2.
 8. En la esquina inferior derecha de la pantalla, haga clic en el botón azul Guardar.
 
-![criar campo master data CRM](//images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
+![criar campo master data CRM](https://images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
 
 ¡Listo! Así, los campos se mostrarán en el formulario.
diff --git a/docs/tutorials/es/how-can-i-create-callcenter-user.md b/docs/tutorials/es/how-can-i-create-callcenter-user.md
index d22d469c4..07301148c 100644
--- a/docs/tutorials/es/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/es/how-can-i-create-callcenter-user.md
@@ -41,7 +41,7 @@ Para crear un usuario con el rol de televentas, sigue los pasos a continuación:
 
 7. Haz clic en el botón **Guardar**.
 
-![GIF animado que muestra cómo crear un usuario de televentas](//images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/4d432b47fca70a6203a566bbe9d61abc/Adicionar_perfil_ES.gif)
+![GIF animado que muestra cómo crear un usuario de televentas](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/4d432b47fca70a6203a566bbe9d61abc/Adicionar_perfil_ES.gif)
 
 <div class="alert alert-warning">Al crear un <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evita incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televentas junto con otros recursos. De lo contrario, puede que el perfil no funcione de forma esperada.
 </div>
diff --git a/docs/tutorials/es/how-can-my-customer-login-to-my-store.md b/docs/tutorials/es/how-can-my-customer-login-to-my-store.md
index 78f7a7dfd..ea87611d4 100644
--- a/docs/tutorials/es/how-can-my-customer-login-to-my-store.md
+++ b/docs/tutorials/es/how-can-my-customer-login-to-my-store.md
@@ -28,7 +28,7 @@ El objetivo de este artículo es mostrar cómo el cliente de su tienda debe hace
 
 Al hacer clic en un enlace para autenticarse, el cliente verá la pantalla de login.
 
-![vtex-id-pt](//images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/f856e8dbe763a72e566f65a00c45be6c/vtex-id-en.png)
+![vtex-id-pt](https://images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/f856e8dbe763a72e566f65a00c45be6c/vtex-id-en.png)
 
 Hay tres formas estándar de entrar en una tienda VTEX:
 
@@ -43,9 +43,9 @@ En este tipo de login se envía __un token de acceso para el e-mail del usuario
 Para que el cliente inicie sesión por este método, debe seguir los pasos abajo:
 
 1. En la pantalla de inicio de sesión, el usuario debe hacer clic en __Recibir clave de acceso rápido por email__.
-2. En la pantalla siguiente, el usuario debe rellenar su correo electrónico y hacer clic en el botón __Confirmar__![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-3. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si la ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-4. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Entrar__. ![fill-access-token-pt](//images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
+2. En la pantalla siguiente, el usuario debe rellenar su correo electrónico y hacer clic en el botón __Confirmar__![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+3. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si la ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+4. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Entrar__. ![fill-access-token-pt](https://images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
 
 ### Hacer login con email y contraseña
 
@@ -56,11 +56,11 @@ Este tipo de login __solicita email y contraseña__ para que el cliente pueda au
 - Si el cliente necesita __registrar una contraseña__, debe seguir los pasos abajo:
 
 1. En la pantalla de inicio de sesión, el usuario debe hacer clic en __Entrar con email y contraseña__.
-2. En la pantalla siguiente, debe hacer clic en __No tiene una contraseña? Registrela ahora__![register-password-pt](//images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
-3. El usuario debe llenar su email y hacer clic en el botón __Confirmar__![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-4. En la pantalla siguiente, debe escribir su nueva contraseña en los campos __Nueva contraseña__ y __Confirmar nueva contraseña__ y, a continuación, hacer clic en el botón __Registrar nueva contraseña__![register-new-password-pt](//images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
-5. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si lo ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-6. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Cambiar contraseña__ ![change-password-pt](//images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)   
+2. En la pantalla siguiente, debe hacer clic en __No tiene una contraseña? Registrela ahora__![register-password-pt](https://images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
+3. El usuario debe llenar su email y hacer clic en el botón __Confirmar__![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+4. En la pantalla siguiente, debe escribir su nueva contraseña en los campos __Nueva contraseña__ y __Confirmar nueva contraseña__ y, a continuación, hacer clic en el botón __Registrar nueva contraseña__![register-new-password-pt](https://images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
+5. __Un token de acceso será enviado al email informado en el paso anterior__. Si el cliente no ha recibido el e-mail, pídale que compruebe si lo ha introducido correctamente. Además, es necesario que el cliente verifique la basura electrónica para garantizar que la clave de acceso no haya caído en el filtro de *spam*. El token tiene 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+6. Vuelva a la pantalla de inicio de sesión y __escriba la clave de acceso__ recibida en el paso anterior y haga clic en __Cambiar contraseña__ ![change-password-pt](https://images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)   
 
 ### Inicio de sesión con redes sociales
 
diff --git a/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index d4ca3e0c4..1b3023b50 100644
--- a/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -32,16 +32,16 @@ Es posible cambiar el protocolo en todas las carpetas de una sola vez con el uso
 2. Acceda a **Sites and channels**;
 3. Acceda el website deseado;
 4. Abra la carpeta raíz del website;
-![cms_instrução ES](//images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
+![cms_instrução ES](https://images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
 5. La pantalla que se abre muestra todas las carpetas que están en el primer nivel del sitio. Para cada carpeta pertinente, haga clic en **Edit** - para la home, considera el botón superior;
-![cms_edit ES](//images.ctfassets.net/alneenqid6w5/5w8bfK8O3egookYkO80uum/af60a80fbf62a154124b05496c1773cf/edit_CMS_ES.png)
+![cms_edit ES](https://images.ctfassets.net/alneenqid6w5/5w8bfK8O3egookYkO80uum/af60a80fbf62a154124b05496c1773cf/edit_CMS_ES.png)
 6. En el cuadro de selección **Protocol**, seleccione la opción **HTTPS**;
-![cms-protocol-https ES](//images.ctfassets.net/alneenqid6w5/6iKmkVgCKkeEu6uqygUs4s/778574a06a8ec5bb2d8fdfe871af0763/cms_protocol_HTTPS_ES.png)
+![cms-protocol-https ES](https://images.ctfassets.net/alneenqid6w5/6iKmkVgCKkeEu6uqygUs4s/778574a06a8ec5bb2d8fdfe871af0763/cms_protocol_HTTPS_ES.png)
 7. Haga clic en **Save Folder**.
 
 Atención a las carpetas que tienen subcarpetas, como Departamento, Categoria, Produto y otras carpetas, incluyendo también las creadas para la personalización de la tienda. 
 
 En el siguiente ejemplo, la carpeta **@Orders@**, contenida en **Account**, que también debe ser editada: 
-![cms_subcategoria_edit ES](//images.ctfassets.net/alneenqid6w5/DugouRmlRQKqAI66eCYww/5bdea3c5bf8305e1693433b1adc14747/subcategoria_edit_ES.png)
+![cms_subcategoria_edit ES](https://images.ctfassets.net/alneenqid6w5/DugouRmlRQKqAI66eCYww/5bdea3c5bf8305e1693433b1adc14747/subcategoria_edit_ES.png)
 
 Después del cache de hasta 10 minutos los cambios estarán en vigor.
diff --git a/docs/tutorials/es/how-do-you-calculate-payments-in-installments-with-compound-interest.md b/docs/tutorials/es/how-do-you-calculate-payments-in-installments-with-compound-interest.md
index 6bf9d6724..dcbd83b9b 100644
--- a/docs/tutorials/es/how-do-you-calculate-payments-in-installments-with-compound-interest.md
+++ b/docs/tutorials/es/how-do-you-calculate-payments-in-installments-with-compound-interest.md
@@ -26,7 +26,7 @@ La cobranza al inicio del periodo se calcula como sigue:
 1. i = Tasa de Intereses
 2. n = Número de Cuotas
 3. PV = Valor Presente (valor total de la compra sin intereses)
-4. Cuota = ![juros-inicio-periodo](//images.contentful.com/alneenqid6w5/3JkoK4GMLYAWIwUcAC8W2G/59d18849c4ee9e59ff37cb09ac661c89/juros-inicio-periodo.png)
+4. Cuota = ![juros-inicio-periodo](https://images.contentful.com/alneenqid6w5/3JkoK4GMLYAWIwUcAC8W2G/59d18849c4ee9e59ff37cb09ac661c89/juros-inicio-periodo.png)
 
 ## Fin del periodo
 
@@ -35,7 +35,7 @@ La cobranza al fin del periodo se calcula como sigue:
 1. i = Tasa de Intereses
 2. n = Número de Cuotas
 3. PV = Valor Presente (valor total da compra sin intereses)
-4. Multiplicador Cash Flow =![cash-flow](//images.contentful.com/alneenqid6w5/2xvT7uQ8ccGoCUw8ouOEoK/936546d7e46be7b9ce984c531daf5e8b/cash-flow.png)
+4. Multiplicador Cash Flow =![cash-flow](https://images.contentful.com/alneenqid6w5/2xvT7uQ8ccGoCUw8ouOEoK/936546d7e46be7b9ce984c531daf5e8b/cash-flow.png)
 5. Cuota = `PV x Multiplicador Cash Flow`
 
 ## Ejemplos
@@ -45,7 +45,7 @@ La cobranza al fin del periodo se calcula como sigue:
 1. i = 1%
 2. n = 12
 3. PV = 1000
-![conta0](//images.contentful.com/alneenqid6w5/3AhidhqtTaCqiuGMKK2c64/8c5e8f0067ad5ec80685bdcca8d79c95/conta0.png)
+![conta0](https://images.contentful.com/alneenqid6w5/3AhidhqtTaCqiuGMKK2c64/8c5e8f0067ad5ec80685bdcca8d79c95/conta0.png)
 
 ---
 
@@ -54,4 +54,4 @@ La cobranza al fin del periodo se calcula como sigue:
 1. i = 1%
 2. n = 12
 3. PV = 1000
-4. ![conta1](//images.contentful.com/alneenqid6w5/4CaAz5DKdaUSY0OwaGEsUu/4afb38b8c7a78977d011f2d6333800d6/conta1.png)![conta2](//images.contentful.com/alneenqid6w5/3hQTOBVJqgMAyMWWia0aAY/5f7fbb82ebeb8b5e912baca35ea39b9b/conta2.png)
+4. ![conta1](https://images.contentful.com/alneenqid6w5/4CaAz5DKdaUSY0OwaGEsUu/4afb38b8c7a78977d011f2d6333800d6/conta1.png)![conta2](https://images.contentful.com/alneenqid6w5/3hQTOBVJqgMAyMWWia0aAY/5f7fbb82ebeb8b5e912baca35ea39b9b/conta2.png)
diff --git a/docs/tutorials/es/how-does-promotion-proration-work.md b/docs/tutorials/es/how-does-promotion-proration-work.md
index 0d28d9aed..7793e0766 100644
--- a/docs/tutorials/es/how-does-promotion-proration-work.md
+++ b/docs/tutorials/es/how-does-promotion-proration-work.md
@@ -38,7 +38,7 @@ Digamos que tenemos una promoción de descuento nominal de $ 156,00 para ser apl
 
 Considerando la lógica del cálculo anterior, quedaría como sigue:
 
-![tabelaex.es](//images.ctfassets.net/alneenqid6w5/5G6XOjSgYmXK29ODCJf58A/077a633df92bc68da6b5032e493a6157/tabelaex.es.png)
+![tabelaex.es](https://images.ctfassets.net/alneenqid6w5/5G6XOjSgYmXK29ODCJf58A/077a633df92bc68da6b5032e493a6157/tabelaex.es.png)
 
 Este cálculo se aplica a productos unitarios, como una blusa o una mesa, pero también hay productos que tienen en su registro una configuración llamada unidad multiplicadora, como una caja de piso de 2,5 m², por ejemplo.
 
diff --git a/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index 1045fd2e9..d16093e9b 100644
--- a/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -29,7 +29,7 @@ En lugar de usar los IDs de cada artículo (lo que generaría pedidos separados
 
 Usted puede encontrar los dos IDs a través del informe enviado desde el panel de integraciones en el Admin de VTEX.
 
-![mercalo-livre-pedido-id-es](//images.ctfassets.net/alneenqid6w5/5JOUHJijbIVncRSfvx5lnC/6cceef1724619d4cd8d332d0e5aad89b/mercalo-livre-pedido-id-es.png)
+![mercalo-livre-pedido-id-es](https://images.ctfassets.net/alneenqid6w5/5JOUHJijbIVncRSfvx5lnC/6cceef1724619d4cd8d332d0e5aad89b/mercalo-livre-pedido-id-es.png)
 
 <div class="alert alert-warning">
 Esta lógica de funcionamiento se aplica a todos los tipos de entrega, con excepción de aquellos que incluyen pickup points. En estos casos, la plataforma sigue utilizando el identificador antiguo.
diff --git a/docs/tutorials/es/how-does-the-delivery-flow-work.md b/docs/tutorials/es/how-does-the-delivery-flow-work.md
index 4570857c6..84e0e9276 100644
--- a/docs/tutorials/es/how-does-the-delivery-flow-work.md
+++ b/docs/tutorials/es/how-does-the-delivery-flow-work.md
@@ -27,4 +27,4 @@ La plataforma VTEX le da libertad para que su tienda utilice estas configuracion
 
 Pero, por ahora, vamos a atenerse al escenario más básico, ilustrado por la figura abajo:
 
-![Logistics Flow Espanhol](//images.ctfassets.net/alneenqid6w5/586A760DbOKiaeSiuO0wW0/09da81662ed4e1865d8f8c7cab9da054/Component__21_.png)
+![Logistics Flow Espanhol](https://images.ctfassets.net/alneenqid6w5/586A760DbOKiaeSiuO0wW0/09da81662ed4e1865d8f8c7cab9da054/Component__21_.png)
diff --git a/docs/tutorials/es/how-does-the-search-context-on-website-folders-operate.md b/docs/tutorials/es/how-does-the-search-context-on-website-folders-operate.md
index 78156ce43..527c32fa3 100644
--- a/docs/tutorials/es/how-does-the-search-context-on-website-folders-operate.md
+++ b/docs/tutorials/es/how-does-the-search-context-on-website-folders-operate.md
@@ -39,7 +39,7 @@ Usando el mismo ejemplo anterior, si creamos una carpeta denominada **mi-landing
 
 ### Configuración
 
-![](//images.contentful.com/alneenqid6w5/ZvEGMDPUs0OsuCkoUsqqS/4411604b8b78124edcbacd46cc45ed53/ContextoDeBusca.PNG "Contexto de Busca")
+![](https://images.contentful.com/alneenqid6w5/ZvEGMDPUs0OsuCkoUsqqS/4411604b8b78124edcbacd46cc45ed53/ContextoDeBusca.PNG "Contexto de Busca")
 
 **Importante**:
 
diff --git a/docs/tutorials/es/how-does-the-type-of-delivery-work.md b/docs/tutorials/es/how-does-the-type-of-delivery-work.md
index b4860e00c..f323ee779 100644
--- a/docs/tutorials/es/how-does-the-type-of-delivery-work.md
+++ b/docs/tutorials/es/how-does-the-type-of-delivery-work.md
@@ -29,7 +29,7 @@ En el checkout, no se exhiben los nombres de los transportistas, y sí los tipos
 
 Siguiendo en el ejemplo más arriba, sigue la imagen de cómo se exhibirían las opciones de flete en el cierre de compra:
 
-![Transportadoras Checkout ES](//images.ctfassets.net/alneenqid6w5/3JEcAUPVTOsSsUCqiMSCUM/6085c74c27b51a0ffcfc5552d1a80eff/Transportadoras_Checkout_ES.png)
+![Transportadoras Checkout ES](https://images.ctfassets.net/alneenqid6w5/3JEcAUPVTOsSsUCqiMSCUM/6085c74c27b51a0ffcfc5552d1a80eff/Transportadoras_Checkout_ES.png)
 
 O sea, aunque se tenga cinco transportistas catastrados (en las categorías **Normal**, **Expresa** y **Programada**), sólo se exhiben tres opciones de flete para el cliente. Y el motivo no es porque los demás transportistas no atienden al carrito, es porque dentro de un mismo tipo sólo se exhibirá el transportista de mayor ventaja al cliente.
 
diff --git a/docs/tutorials/es/how-does-vtex-search-work.md b/docs/tutorials/es/how-does-vtex-search-work.md
index 2bb98b9f6..ca3e42555 100644
--- a/docs/tutorials/es/how-does-vtex-search-work.md
+++ b/docs/tutorials/es/how-does-vtex-search-work.md
@@ -73,7 +73,7 @@ Para entender la búsqueda de VTEX, inicialmente es necesario saber cómo funcio
 
 El indexador del catálogo es una base de datos escalable de acceso rápido, con algoritmos configurables de priorización de resultados. Está posicionado entre la base de datos convencional y el usuario. Vea el siguiente esquema:
 
-![](//images.contentful.com/alneenqid6w5/4PSR97lU5y2iac2QkoUAKg/10b9097341faf0de317fa6984104da95/indexacao.png)
+![](https://images.contentful.com/alneenqid6w5/4PSR97lU5y2iac2QkoUAKg/10b9097341faf0de317fa6984104da95/indexacao.png)
 
 En el indexador encontramos todas las informaciones referentes al catálogo de productos (productos, SKUs, marcas, departamentos, categorías). El buscador utiliza estas informaciones para localizar los productos y mostrarlos en las vitrinas y los resultados de búsqueda. Por lo tanto, __solamente los productos indexados pueden ser encontrados por la búsqueda__.
 
diff --git a/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md b/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md
index 27a40a658..10764309b 100644
--- a/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md
+++ b/docs/tutorials/es/how-is-pro-rata-calculated-in-vtex.md
@@ -21,6 +21,6 @@ La cuenta del descuento es: `average fee dividido por el número de días del me
 
 Entonces, si su mensualidad tuvo un valor de $ 750 en el mes de mayo - 31 días - y usted contrató a VTEX el día 06 de mayo, serán descontados $ 145,16 en su próxima factura.
 
-![prorata PT](//images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
+![prorata PT](https://images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
 
 La cuenta fue: `$ 750/31 = $ 24,19 x 3 (días) = $ 145,16`
diff --git a/docs/tutorials/es/how-is-taxhub-api-rest-structure.md b/docs/tutorials/es/how-is-taxhub-api-rest-structure.md
index b4ea2f1db..ff392e63e 100644
--- a/docs/tutorials/es/how-is-taxhub-api-rest-structure.md
+++ b/docs/tutorials/es/how-is-taxhub-api-rest-structure.md
@@ -52,7 +52,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubAPIGetTax](//images.contentful.com/alneenqid6w5/4CaoACwzqEYcUQem6okKQO/0e295bc9101cc0b46e7669a49b6f99e3/TaxHubAPIGetTax.jpg)
+![TaxHubAPIGetTax](https://images.contentful.com/alneenqid6w5/4CaoACwzqEYcUQem6okKQO/0e295bc9101cc0b46e7669a49b6f99e3/TaxHubAPIGetTax.jpg)
 
 __2 Occupation Area__
 
@@ -99,7 +99,7 @@ Response:
 ```
  
 Evidence:
-![TaxHubOccupationArea](//images.contentful.com/alneenqid6w5/2lJDIuKFz6AwgM62eI6aWA/c0bab0f8e5016e3ced947cfb94050d43/TaxHubOccupationArea.jpg)
+![TaxHubOccupationArea](https://images.contentful.com/alneenqid6w5/2lJDIuKFz6AwgM62eI6aWA/c0bab0f8e5016e3ced947cfb94050d43/TaxHubOccupationArea.jpg)
 
 __3 FiscalRegion__
 
@@ -137,7 +137,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubFiscalRegion](//images.contentful.com/alneenqid6w5/3i7TuC4rJYwoIWY62UwgE0/5cfc50a55c0e068a2dea68573a636a1b/TaxHubFiscalRegion.jpg)
+![TaxHubFiscalRegion](https://images.contentful.com/alneenqid6w5/3i7TuC4rJYwoIWY62UwgE0/5cfc50a55c0e068a2dea68573a636a1b/TaxHubFiscalRegion.jpg)
 
 __4	CustomerCode__
 - Host: http://api.beta.vtex.com
@@ -172,7 +172,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubCustomerCode](//images.contentful.com/alneenqid6w5/5ANPppLxvikIK4Kkaoe6qM/3d5033469dc13154c1bae8ddaeb02c06/TaxHubCustomerCode.jpg)
+![TaxHubCustomerCode](https://images.contentful.com/alneenqid6w5/5ANPppLxvikIK4Kkaoe6qM/3d5033469dc13154c1bae8ddaeb02c06/TaxHubCustomerCode.jpg)
 
 __5	ItemCode__
 
@@ -208,7 +208,7 @@ Response:
 
 Evicence:
 
-![TaxHubItemCode](//images.contentful.com/alneenqid6w5/4im391LOekSmYIgWgeqIIK/078dbcbb83861e5b90d9b0b9519778e5/TaxHubItemCode.jpg)
+![TaxHubItemCode](https://images.contentful.com/alneenqid6w5/4im391LOekSmYIgWgeqIIK/078dbcbb83861e5b90d9b0b9519778e5/TaxHubItemCode.jpg)
 
 __6 Aliquot__
 - Host: http://api.beta.vtex.com
@@ -245,7 +245,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubAliquot](//images.contentful.com/alneenqid6w5/6d6Kgove5GaWM2As0EAqmg/6959389c39c4d0c69cccd1982ccf7c6e/TaxHubAliquot.jpg)
+![TaxHubAliquot](https://images.contentful.com/alneenqid6w5/6d6Kgove5GaWM2As0EAqmg/6959389c39c4d0c69cccd1982ccf7c6e/TaxHubAliquot.jpg)
 
 __7 TaxValue__
 
@@ -294,6 +294,6 @@ Response:
 ```
  
 Evidence:
-![TaxHubTaxValue](//images.contentful.com/alneenqid6w5/53rujXNKTYs0kugAMwSca8/53b29d1078e0960a39360bdad84e4b7e/TaxHubTaxValue.jpg)
+![TaxHubTaxValue](https://images.contentful.com/alneenqid6w5/53rujXNKTYs0kugAMwSca8/53b29d1078e0960a39360bdad84e4b7e/TaxHubTaxValue.jpg)
 
 [Continua con TaxHub Estructura de App en JS](/es/tutorial/taxhub-estructura-de-app-en-js)
diff --git a/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md b/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md
index c410b1a19..59854cb93 100644
--- a/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md
+++ b/docs/tutorials/es/how-is-the-order-delivery-deadline-calculated.md
@@ -22,7 +22,7 @@ El plazo de envío de un pedido es calculado considerando los seguientes aspecto
 - [Muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
 - [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140)
 
-![lead_time_image_total_time_ES](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
+![lead_time_image_total_time_ES](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
 
 Usted define una duración para cada una de esas etapas y su cliente en checkout vé um plazo de envío que es la suma de estos tiempos.  
 
diff --git a/docs/tutorials/es/how-is-the-taxhub-app-structure-in-js.md b/docs/tutorials/es/how-is-the-taxhub-app-structure-in-js.md
index c64855865..551129d24 100644
--- a/docs/tutorials/es/how-is-the-taxhub-app-structure-in-js.md
+++ b/docs/tutorials/es/how-is-the-taxhub-app-structure-in-js.md
@@ -34,7 +34,7 @@ Defina el nombre del archivo inicial, con el mismo país de la tienda.
 Ejemplo: argentina.js o mexico.js, el archivo .js de la carpeta principal y la carpeta tienen que tener el mismo nombre. La carpeta IVA puede tener cualquier nombre.
 
 El orden de llamada que debe seguir también para el desarrollo:
-![TaxHubTree](//images.contentful.com/alneenqid6w5/5hPFG8m6pUCMuIg8e2Iymm/957b9c89844099db690e82abe53c2b7a/TxHubTree.jpg)
+![TaxHubTree](https://images.contentful.com/alneenqid6w5/5hPFG8m6pUCMuIg8e2Iymm/957b9c89844099db690e82abe53c2b7a/TxHubTree.jpg)
 
 Después de hacer los cambios deberá subir el archivo a VTEX en el formato `.zip` siempre con la misma estructura de carpetas.
 
diff --git a/docs/tutorials/es/how-my-account-works.md b/docs/tutorials/es/how-my-account-works.md
index 0ac03b6a1..4428be054 100644
--- a/docs/tutorials/es/how-my-account-works.md
+++ b/docs/tutorials/es/how-my-account-works.md
@@ -34,7 +34,7 @@ Para saper sobre cómo personalizar la funcionalidad <b>Mi cuenta</b>, consulte
 
 En esta pestaña, el cliente puede gestionar sus datos personales registrados en la tienda. Es posible [editar la información del perfil](#editar), [definir una nueva contraseña](#contrasena) y [elegir si desea recibir emails con promociones](#boletin-informativo).
 
-![profile ES](//images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/98d696bdb6ca27fdcb6125d6ad83d60c/profile_ES.png)
+![profile ES](https://images.ctfassets.net/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/98d696bdb6ca27fdcb6125d6ad83d60c/profile_ES.png)
 
 ### Editar
 
@@ -83,7 +83,7 @@ En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJT
 
 Esta pestaña proporciona una lista completa de los pedidos realizados por un cliente en su tienda. La lista se ordena por fecha de creación y muestra detalles como la fecha del pedido, el valor total de la compra, el ID del pedido, el _status_ y los ítems comprados.
 
-![orders ES](//images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/c6d01d4becb2a0f1173e34a82f83cb90/orders_ES.png)
+![orders ES](https://images.ctfassets.net/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/c6d01d4becb2a0f1173e34a82f83cb90/orders_ES.png)
 
 La pestaña **Pedidos** permite que el cliente haga el seguimiento del progreso del pedido y realice solicitudes como la cancelación y la modificación. Consulte a continuación todas las opciones disponibles.
 
@@ -108,7 +108,7 @@ Al hacer clic en un pedido del listado, el cliente podrá visualizar todos los d
 
 El cliente también puede [Hacer pedido de nuevo](#hacer-pedido-de-nuevo) desde esta página. Al hacer clic en `Más opciones`, se muestran las funcionalidades de [Modificar pedido](#modificar-pedido) (en caso de que esté habilitada y el _status_ del pedido sea `Preparando el pedido`) y [Solicitar cancelación](#solicitar-cancelacion).
 
-![order details ES](//images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/d29f723e144d008ee0fc142db264a4a0/order_details_ES.png)
+![order details ES](https://images.ctfassets.net/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/d29f723e144d008ee0fc142db264a4a0/order_details_ES.png)
 
 #### Modificar pedido
 
@@ -135,7 +135,7 @@ Para agregar nuevas tarjetas, sigue los pasos a continuación:
 6. Resuelve el desafío de reCaptcha.
 7. Automáticamente se producirá un proceso de validación de tarjeta. Si no hay ningún problema, serás redirigido a la lista de tarjetas y la nueva tarjeta aparecerá en la lista.
 
-![Card ReCaptcha](//images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/eb678f63dc5c69a402bae6db631c5ba8/Card_ReCaptcha_EN.gif)
+![Card ReCaptcha](https://images.ctfassets.net/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/eb678f63dc5c69a402bae6db631c5ba8/Card_ReCaptcha_EN.gif)
 
 Sin embargo, hay **limitaciones** que las tiendas que utilizan la autenticación [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) (V1 o V2) en sus adquirentes deben considerar:
 
@@ -157,7 +157,7 @@ En esta pestaña, el cliente puede gestionar todas sus suscripciones registradas
 
 Esta pestaña se puede acceder a ella en el panel izquierdo a través de **Autenticación** en la configuración del perfil del usuario. En la pestaña encontrará opciones para la gestión de contraseña y gestión de sesiones.
 
-![My Authentication app ES](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
+![My Authentication app ES](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/3ac0c69ccace5c9b274318b06bea409f/My_Authentication_app_ES.png)
 
 ### Gestión de contraseña 
 
@@ -167,7 +167,7 @@ El componente **Contraseña** permite al usuario crear una contraseña (si aún
 2. En el campo **Código**, introduzca el código de verificación que recibió por email.
 3. En el campo **Nueva contraseña**, introduzca la nueva contraseña que desea asignar a su cuenta. Debajo del campo aparecen los requisitos que debe cumplir la contraseña para ser válida. A medida que escriba la contraseña, los símbolos de cada requisito cambiarán de rojo a verde. La contraseña solo será válida si todos los símbolos aparecen en verde.
 4. Una vez que haya introducido una contraseña válida, haga clic en el botón `GUARDAR CONTRASEÑA` para completar la creación de la contraseña.  
-![My Authentication create password ES](//images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/c8f8a07de5442b0ffbc49c3b6a66de29/My_Authentication_create_password_ES.png)
+![My Authentication create password ES](https://images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/c8f8a07de5442b0ffbc49c3b6a66de29/My_Authentication_create_password_ES.png)
 
 Para cambiar la contraseña actual:
 
@@ -175,7 +175,7 @@ Para cambiar la contraseña actual:
 2. Introduzca la contraseña actual en el campo correspondiente.
 3. Introduzca la nueva contraseña en el campo correspondiente, cumpliendo todos los requisitos.
 4. Haga clic en el botón `GUARDAR CONTRASEÑA` para completar el cambio de contraseña.  
-![My Authentication change password ES](//images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/55e5cdfbb4f5daeb591eadbbccf82183/My_Authentication_change_password_ES.png)
+![My Authentication change password ES](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/55e5cdfbb4f5daeb591eadbbccf82183/My_Authentication_change_password_ES.png)
 
 <div class="alert alert-info">
 Si ha olvidado su contraseña, no podrá recuperarla a través del componente de gestión de contraseña. Para ello, debe cerrar la sesión actual, hacer un intento de inicio de sesión con el email y la contraseña, y hacer clic en el link <strong>Olvidé mi contraseña</strong>.
@@ -189,7 +189,7 @@ Para ver sus sesiones activas, haga clic en el botón `VER SESIONES` y accederá
 
 Para cancelar el acceso a las demás sesiones, haga clic en el botón `CIERRE DE SESIÓN` de la sesión deseada.
 
-![My Authentication Session Management ES](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
+![My Authentication Session Management ES](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/1fe19f90a71681bf3f46a5d8ab52aabb/My_Authentication_Session_Management_ES_blur.png)
 
 ## Configuraciones básicas
 
@@ -200,7 +200,7 @@ En **My Orders**, puedes determinar qué secciones estarán visibles para el cli
 * En **ORDERS**, la opción <a class="far fa-check-square"></a> _Visible_ determina si el cliente tiene la sección [Pedidos](#pedidos) para seguir sus pedidos.
 * En **ADDRESSES**, la opción <a class="far fa-check-square"></a> _Visible_ define si el cliente tendrá la sección [Direcciones](#direcciones) con detalles de su dirección. 
 
-![vtex-my-account_ES](//images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/95b29a5b64c84fe70b4dc01e4a36b26a/vtex-my-account_ES.png)
+![vtex-my-account_ES](https://images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/95b29a5b64c84fe70b4dc01e4a36b26a/vtex-my-account_ES.png)
 
 Por defecto, las opciones **CARDS** y **ORDERS** vienen configuradas como visibles. Para cambiarlas o habilitar otras configuraciones, realiza los pasos a continuación:
 
diff --git a/docs/tutorials/es/how-order-authorization-works.md b/docs/tutorials/es/how-order-authorization-works.md
index a07c223b8..e96d9dc24 100644
--- a/docs/tutorials/es/how-order-authorization-works.md
+++ b/docs/tutorials/es/how-order-authorization-works.md
@@ -17,7 +17,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 En el Admin VTEX, en **Configuración de la tienda > Pedidos > Autorización de pedidos**, es posible controlar la aprobación de pedidos con divergencia de precios en su tienda.
 
-![print_autorizacao_pedidos_ES](//images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/f0ce68dc289044000a20ec391475c4c9/print_autorizacao_pedidos_ES.png)
+![print_autorizacao_pedidos_ES](https://images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/f0ce68dc289044000a20ec391475c4c9/print_autorizacao_pedidos_ES.png)
 La divergencia de precios en pedidos se pueden encontrar en dos escenarios principales:
 
 - [Descuentos manuales](https://help.vtex.com/es/tutorial/como-funciona-a-autorizacao-de-pedidos--3MBK6CmKHAuUjMBieDU0pn#descuentos-manuales)
diff --git a/docs/tutorials/es/how-order-authorization-workss.md b/docs/tutorials/es/how-order-authorization-workss.md
index 10a42b2ff..ee586311f 100644
--- a/docs/tutorials/es/how-order-authorization-workss.md
+++ b/docs/tutorials/es/how-order-authorization-workss.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 En el módulo de gestión de pedidos, __La Autorización de pedidos__ permite el control y la aprobación de pedidos con divergencias de precios en su tienda.
 
-![autorização-de-pedidos ES](//images.ctfassets.net/alneenqid6w5/7bov7XWzWzQ2qFPZ5OnJg7/3044ddd44a533fbd7a5d2499e7353374/autoriza____o-de-pedidos__ES.png)
+![autorização-de-pedidos ES](https://images.ctfassets.net/alneenqid6w5/7bov7XWzWzQ2qFPZ5OnJg7/3044ddd44a533fbd7a5d2499e7353374/autoriza____o-de-pedidos__ES.png)
  
 Las divergencias de precios entre pedidos se pueden encontrar en dos escenarios principales:
 
diff --git a/docs/tutorials/es/how-promotion-competition-works.md b/docs/tutorials/es/how-promotion-competition-works.md
index 6aaebfc34..1f452c9e1 100644
--- a/docs/tutorials/es/how-promotion-competition-works.md
+++ b/docs/tutorials/es/how-promotion-competition-works.md
@@ -82,7 +82,7 @@ Además, todas ellas inciden sobre el valor que ya se descontó al aplicarse la
 
 Por lo tanto, la secuencia de aplicación es:
 
-![promocao3 ES](//images.ctfassets.net/alneenqid6w5/1CAcjiuVQECwqcoA288Aey/251351f394db394a008ccdd699e47c6f/promocao3_ES.png)
+![promocao3 ES](https://images.ctfassets.net/alneenqid6w5/1CAcjiuVQECwqcoA288Aey/251351f394db394a008ccdd699e47c6f/promocao3_ES.png)
 
 <div class="alert alert-warning">
 Los pedidos de origen <a href="https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> ((proporcionados por la tienda) y Fulfillment (entregados por la tienda) no permiten la acumulación de promociones, ya que el uso de las mismas en marketplaces VTEX o externos se limita a algunos tipos específicos.</div> 
diff --git a/docs/tutorials/es/how-recursive-marketplace-works.md b/docs/tutorials/es/how-recursive-marketplace-works.md
index 541d7ae7d..74c16f55e 100644
--- a/docs/tutorials/es/how-recursive-marketplace-works.md
+++ b/docs/tutorials/es/how-recursive-marketplace-works.md
@@ -33,7 +33,7 @@ Con eso:
 
 - __Cuando una tienda VTEX es intermediaria en el flujo de un pedido__: pedido de cadena con __Chain Workflow__:
 
-![marketplace-recursivo-chain-order-workflow](//images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
+![marketplace-recursivo-chain-order-workflow](https://images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
 
 
 ## Configuración
diff --git a/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md b/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
index b5c0fffc9..6e7dff5fe 100644
--- a/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
+++ b/docs/tutorials/es/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
@@ -44,7 +44,7 @@ Al igual que en la interfaz del OMS, la API trae la información `vtex:fob_1111`
 
 Es importante que el ERP sea adecuado para recibir los datos en este formato.
 
-![](//images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
+![](https://images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
 
 ## Etiqueta
 
@@ -52,6 +52,6 @@ El pedido se envía en un contrato con la oficina de correos del propio marketpl
 
 Es posible acceder a la etiqueta directamente por el OMS, debajo de los ítems del pedido. Basta hacer clic en el link y se abrirá una nueva ventana ya con el PDF de la etiqueta.
 
-![Etiqueta de entrega por Correios (BR) - Marketplace](//images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/f715c425b47359c8d8735cde8aac8377/Screen_Shot_2020-03-25_at_11.44.05.png)
+![Etiqueta de entrega por Correios (BR) - Marketplace](https://images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/f715c425b47359c8d8735cde8aac8377/Screen_Shot_2020-03-25_at_11.44.05.png)
 
 En el caso de que se quiera aprovechar la etiqueta dentro del ERP, esta también está disponible en la [Marketplace Protocol API](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/order-integration/orders), sepa más en [New Order Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-collect-orders#scenario-12-order-with-tracking-hints).
diff --git a/docs/tutorials/es/how-the-automatic-compacting-of-images-works.md b/docs/tutorials/es/how-the-automatic-compacting-of-images-works.md
index 0df45c8d1..d19840200 100644
--- a/docs/tutorials/es/how-the-automatic-compacting-of-images-works.md
+++ b/docs/tutorials/es/how-the-automatic-compacting-of-images-works.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 Las tiendas VTEX cuentan con compactación automática de imágenes para __WebP__. Este recurso posibilita una reducción hasta del 25% en el peso del sitio.
 
-![webplogo](//images.contentful.com/alneenqid6w5/1HsHoCbkyM86KKA4sCWucO/0e6f078eb62b773cc927da79b8ea6f1e/webplogo.png)
+![webplogo](https://images.contentful.com/alneenqid6w5/1HsHoCbkyM86KKA4sCWucO/0e6f078eb62b773cc927da79b8ea6f1e/webplogo.png)
 
 El formato, desarrollado por Google, es más eficiente que el JPG o el PNG, sin necesariamente reducir la calidad de las imágenes. Genera fácilmente una ganancia de 1 ó 2 segundos en el tiempo de carga de las páginas (variando según el layout).
 
diff --git a/docs/tutorials/es/how-the-documents-saving-flow-works.md b/docs/tutorials/es/how-the-documents-saving-flow-works.md
index e9da74d23..ecd5d0422 100644
--- a/docs/tutorials/es/how-the-documents-saving-flow-works.md
+++ b/docs/tutorials/es/how-the-documents-saving-flow-works.md
@@ -17,7 +17,7 @@ subcategory: 5gtjaqCG7eIseyCI0aSqc2
 
 La siguiente imagen muestra el flujo para guardar documentos en Master Data. Vamos a explicar cada paso.
 
-![Save flow](//images.contentful.com/alneenqid6w5/5klqkN1OEwMEq0aEQeMyIY/2ba2b7cc8e29a5ee0baad8be92aeef9a/MDSaveDiagram.png)
+![Save flow](https://images.contentful.com/alneenqid6w5/5klqkN1OEwMEq0aEQeMyIY/2ba2b7cc8e29a5ee0baad8be92aeef9a/MDSaveDiagram.png)
 
 #### Guardar llamada de API
 Ocurre cuando el usuario llama a la API para guardar documentos (POST, PUT o PATCH).
diff --git a/docs/tutorials/es/how-the-order-replacement-works.md b/docs/tutorials/es/how-the-order-replacement-works.md
index be45a7e8d..7e71e9fcc 100644
--- a/docs/tutorials/es/how-the-order-replacement-works.md
+++ b/docs/tutorials/es/how-the-order-replacement-works.md
@@ -60,13 +60,13 @@ Además de eso, no es posible realizar la sustitución en los siguientes status
 
 Con esta funcionalidad, los usuarios de su tienda ganan una página de Mis Pedidos rediseñada, con opciones de modificación y cancelación:
 
-![meus pedidos1 ES](//images.contentful.com/alneenqid6w5/2ebQjrhfvOOCQMY486QSy4/3bc4cd2897dd9414e0a8b42c56bed1ff/meus_pedidos1_ES.png)
+![meus pedidos1 ES](https://images.contentful.com/alneenqid6w5/2ebQjrhfvOOCQMY486QSy4/3bc4cd2897dd9414e0a8b42c56bed1ff/meus_pedidos1_ES.png)
 
-![meus pedidos3 ES](//images.ctfassets.net/alneenqid6w5/6yYHPkdA8EeIyAU4iUEKOI/f7fa26cebb8d40dce657324941fcc02e/meus_pedidos3_ES.png)
+![meus pedidos3 ES](https://images.ctfassets.net/alneenqid6w5/6yYHPkdA8EeIyAU4iUEKOI/f7fa26cebb8d40dce657324941fcc02e/meus_pedidos3_ES.png)
 
 Al seleccionar **Alterar pedido**, el cliente es llevado a una pantalla en la que elige qué información le gustaría sustituir:
 
-![meus pedidos2 ES](//images.contentful.com/alneenqid6w5/2OC2x7ypIQ0kgwGS8SuAY0/799dffcb0ebe3a6c4073abbe12ae13f3/meus_pedidos2_ES.png)
+![meus pedidos2 ES](https://images.contentful.com/alneenqid6w5/2OC2x7ypIQ0kgwGS8SuAY0/799dffcb0ebe3a6c4073abbe12ae13f3/meus_pedidos2_ES.png)
 
 Para concluir la modificación, él es llevado al carrito y el Checkout, donde puede modificar dirección, tipo de flete, forma de pago y SKU.
 
diff --git a/docs/tutorials/es/how-the-seller-portal-catalog-works.md b/docs/tutorials/es/how-the-seller-portal-catalog-works.md
index fdd064611..5230aa96f 100644
--- a/docs/tutorials/es/how-the-seller-portal-catalog-works.md
+++ b/docs/tutorials/es/how-the-seller-portal-catalog-works.md
@@ -21,7 +21,7 @@ El Catálogo del Seller Portal es un módulo donde usted configura el surtido de
 
 La arquitectura del Catálogo del Seller Portal se basa en algunos conceptos fundamentales que se distribuyen según la siguiente jerarquía:
 
-![ilustra-catalogoES](//images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/372a36eabdf9dec772108dcffa655814/ilustra-catalogoES.png)
+![ilustra-catalogoES](https://images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/372a36eabdf9dec772108dcffa655814/ilustra-catalogoES.png)
 
 - **Categorías:** formas de organizar sus productos. Usted no puede agregar sus propias Categorías, ya que el marketplace define cuáles estarán disponibles para categorizar sus productos. Es obligatorio que cada producto esté relacionado con una de las categorías que fueron creadas por el marketplace.   
 - **Marcas:**  parte de los atributos que caracterizan a los Productos de su tienda. Permite que sus clientes puedan encontrar lo que buscan de forma más específica.   
diff --git a/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md b/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md
index c0e801261..fac36e637 100644
--- a/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md
+++ b/docs/tutorials/es/how-to-activate-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 La app [Carrito Compartido](https://apps.vtex.com/vtex-social-selling/p) permite a los vendedores seleccionar productos para sus clientes y compartir el carrito lleno por canales como WhatsApp, Facebook Messenger y correo electrónico.
 
-![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artículo explica cómo instalar la app y configurar la funcionalidad en su tienda. Una vez completados los pasos de activación, sus vendedores podrán seguir las [instrucciones de uso](https://help.vtex.com/es/tutorial/como-usar-o-app-carrinho-compartilhavel--3ePPpkmeZ96GXbeIoGZbTN) para comenzar sus estrategias de Social Selling.
 
@@ -84,7 +84,7 @@ Si desea personalizar los colores de los botones de la interfaz de carrito compa
 
 En la siguiente imagen, la opción A muestra los colores originales y la opción B una posible personalización.
 
-![shareable-cart-ui-customization](//images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
+![shareable-cart-ui-customization](https://images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
 
 El código que figura a continuación debe añadirse al final del archivo `checkout5-custom.css` o `checkout6-custom.css`, disponible para su personalización en *Configuración de la tienda > Checkout > Código*. El archivo que debe editarse depende de la versión de Checkout utilizada por su tienda.
 
diff --git a/docs/tutorials/es/how-to-alter-a-banner.md b/docs/tutorials/es/how-to-alter-a-banner.md
index 1dec958d1..51cdfc53b 100644
--- a/docs/tutorials/es/how-to-alter-a-banner.md
+++ b/docs/tutorials/es/how-to-alter-a-banner.md
@@ -22,14 +22,14 @@ Para ejemplo, usaremos un banner de la Home en el paso a paso, pero estas instru
 3. Haga clic en la carpeta **“Sites and Channels”**
 4. Haga clic en el **nombre de su tienda**.
 5. Haga clic en la **carpeta "/"**
-![cms_instrução ES](//images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
+![cms_instrução ES](https://images.ctfassets.net/alneenqid6w5/Eh2zwnOd0GqY0oGCw4Y6Y/b89d5aa3092d8d964469668cda783d9a/CMS_instru____o_-_ES.png)
 6. Haga clic en el archivo **“home”**
 7. Haga clic en la pestaña **Settings**
 8. Haga clic en el “lápiz” de edición. 
-![cms-home-settings ES](//images.ctfassets.net/alneenqid6w5/2NaTvILk6k06CqmmWmQC8i/7e962cbf2fe343cb97dca469259b01ef/banner_home_settings_-_es.png)
+![cms-home-settings ES](https://images.ctfassets.net/alneenqid6w5/2NaTvILk6k06CqmmWmQC8i/7e962cbf2fe343cb97dca469259b01ef/banner_home_settings_-_es.png)
 9. Se abrirá la ventana de banners
 10. Haga clic en el "lápiz" que aparecerá
-![cms_home_settings_lapis ES](//images.ctfassets.net/alneenqid6w5/1XGZSbmX4MEs2kCcaKaaGu/8861c836393525c7d4f10fd688018816/cms_settings_lapis_es.png)
+![cms_home_settings_lapis ES](https://images.ctfassets.net/alneenqid6w5/1XGZSbmX4MEs2kCcaKaaGu/8861c836393525c7d4f10fd688018816/cms_settings_lapis_es.png)
 11. Se abrirá el formulario de banner;
 
 **Modificar los contenidos del formulario:**
diff --git a/docs/tutorials/es/how-to-archive-ratestaxes.md b/docs/tutorials/es/how-to-archive-ratestaxes.md
index 9a573ffd0..b8a326c0f 100644
--- a/docs/tutorials/es/how-to-archive-ratestaxes.md
+++ b/docs/tutorials/es/how-to-archive-ratestaxes.md
@@ -17,7 +17,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 Si quiere usted que una tasa creada no permanezca en la lista principal por no ser más utilizada, por ejemplo, puede desplazarla a la lista de archivadas. Al hacerlo, la tasa tendrá automáticamente alterado su status para inactivo. Para hacerlo siga los pasos siguientes:
 
-![ejemplo 1](//images.ctfassets.net/alneenqid6w5/58rtXjsuvCsCyoyCUmUk4w/4a8253c930bdb09e01886162148e5cf7/ejemplo_1.png)
+![ejemplo 1](https://images.ctfassets.net/alneenqid6w5/58rtXjsuvCsCyoyCUmUk4w/4a8253c930bdb09e01886162148e5cf7/ejemplo_1.png)
 
 1. En el Admin VTEX, accede a *Promociones > Impuestos*, o escribe *Impuestos* en la barra de búsqueda en la parte superior de la página.
 2. Busque la tasa que desea archivar.
diff --git a/docs/tutorials/es/how-to-assemble-a-look-kit.md b/docs/tutorials/es/how-to-assemble-a-look-kit.md
index 4496ef5b5..81d3dcf4e 100644
--- a/docs/tutorials/es/how-to-assemble-a-look-kit.md
+++ b/docs/tutorials/es/how-to-assemble-a-look-kit.md
@@ -33,13 +33,13 @@ Las diferencias entre el KIT y el KIT LOOK:
 
 Este término es muy conocido en el rubro de la Moda. Un Kit Look es un modo en el que se puede comprar varios productos visualizando solamente la pantalla de un solo producto.
 
-![](//images.contentful.com/alneenqid6w5/2WA6REAMecCaUiSEk2uoC6/999c983b772d8025d86f6ca2d1ebf3e4/kit-look-donadolook-exemplo.gif)
+![](https://images.contentful.com/alneenqid6w5/2WA6REAMecCaUiSEk2uoC6/999c983b772d8025d86f6ca2d1ebf3e4/kit-look-donadolook-exemplo.gif)
 
 En el layout arriba se pueden seleccionar los ítems del kit que el cliente quisiera comprar y luego hacer clic en “Comprar Produtos Selecionados”.
 
 O si prefiere, puede comprar el kit completo manteniendo todos los ítems seleccionados.
 
-![](//images.contentful.com/alneenqid6w5/4ol1nKNyx2WYw26wQscgEE/986c00a0096dd93ac7c3ce206ecf049e/kit-look-jackthebarber-exemplo.gif)
+![](https://images.contentful.com/alneenqid6w5/4ol1nKNyx2WYw26wQscgEE/986c00a0096dd93ac7c3ce206ecf049e/kit-look-jackthebarber-exemplo.gif)
 
 En este layout cada ítem tiene un botón de “Comprar Separadamente”.
 
diff --git a/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
index 134cfd45d..7dd61d8d8 100644
--- a/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
@@ -21,11 +21,11 @@ Para recuperar la IP de un cliente que realizó un pedido en su tienda, basta an
 
 Al abrir una ordén, haga clic en "Ver detalles de la transacción" en la caja de pagos:
 
-![ip pedido1 ES](//images.ctfassets.net/alneenqid6w5/57bJimzndm6e0US0GywG6e/7830e3b7c8b98544013781daacc949d5/ip_pedido1_ES.png)
+![ip pedido1 ES](https://images.ctfassets.net/alneenqid6w5/57bJimzndm6e0US0GywG6e/7830e3b7c8b98544013781daacc949d5/ip_pedido1_ES.png)
 
 Finalmente, la IP se visualiza en la parte superior derecha:
 
-![ip pedido2 ES](//images.ctfassets.net/alneenqid6w5/3M7hIdC8la28CCkq2g0Wou/a3eb0f89c0f1b1c8112c533ba059c3a2/ip_pedido2_ES.png)
+![ip pedido2 ES](https://images.ctfassets.net/alneenqid6w5/3M7hIdC8la28CCkq2g0Wou/a3eb0f89c0f1b1c8112c533ba059c3a2/ip_pedido2_ES.png)
 
 Ver más detalles en [Cómo visualizar detalle del pedido](/es/tutorial/como-visualizar-detalle-del-pedido)
 
diff --git a/docs/tutorials/es/how-to-change-orders-beta.md b/docs/tutorials/es/how-to-change-orders-beta.md
index f751e6133..96212978f 100644
--- a/docs/tutorials/es/how-to-change-orders-beta.md
+++ b/docs/tutorials/es/how-to-change-orders-beta.md
@@ -93,7 +93,7 @@ Para agregar uno o más ítems al pedido, sigue estos pasos:
 2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
 3. En la página **Gestionar ítems del pedido**, haz clic en la flecha hacia arriba <i class="fas fa-angle-up"></i> hasta alcanzar la cantidad que desees, o ingresa el número en el campo. Después, la página mostrará el precio y la cantidad anterior tachados y aparecerá el siguiente mensaje: _"Ítem editado"_. 
 
-    ![change_order_adding_items_ES](//images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/9ed7c426af47193fb9a731a9cfe9911e/change_order_adding_items_ES.png)
+    ![change_order_adding_items_ES](https://images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/9ed7c426af47193fb9a731a9cfe9911e/change_order_adding_items_ES.png)
 
 4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
 5. Haz clic en `Revisar y aplicar`.
@@ -114,7 +114,7 @@ Para agregar uno o más productos al pedido, sigue estos pasos:
   > Si haces clic en el nombre del producto, se te redirigirá a la página del producto en el sitio web de la tienda.
 6. A continuación, haz clic en `Agregar ítems seleccionados`. Aparecerá el siguiente mensaje: _"Ítems agregados"_.
 
-    ![change_order_adding_product_ES](//images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/24eff795e29b14252157be1dd0b510e1/change_order_adding_product_ES.png)
+    ![change_order_adding_product_ES](https://images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/24eff795e29b14252157be1dd0b510e1/change_order_adding_product_ES.png)
 
 4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
 8. Haz clic en `Revisar y aplicar`.
@@ -131,7 +131,7 @@ Para remover uno o más ítems del pedido, sigue estos pasos:
 2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
 3. En la página **Gestionar ítems del pedido**, haz clic en la flecha hacia abajo <i class="fas fa-angle-down"></i> hasta alcanzar la cantidad que desees, o ingresa el número en el campo. Después, la página mostrará el precio y la cantidad anterior tachados y aparecerá el siguiente mensaje: _“Ítem editado”_.
 
-    ![change_order_removing_items_ES](//images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/113a96a1c4ea5ade7dad11d4955fa648/change_order_removing_items_ES.png)
+    ![change_order_removing_items_ES](https://images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/113a96a1c4ea5ade7dad11d4955fa648/change_order_removing_items_ES.png)
 
 4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
 5. A continuación, haz clic en `Revisar y aplicar`.
@@ -148,7 +148,7 @@ Para remover un producto de un pedido, sigue estos pasos:
 2. En la sección **Facturación pendiente**, haz clic en `Modificar ítems`.
 3. En la página **Gestionar ítems del pedido**, haz clic en el ícono de la papelera <i class="far fa-trash-alt"></i> `Remover ítem`. Aparecerá el siguiente mensaje de confirmación: _“Ítem removido”_.
 
-    ![change_order_removing_product_ES](//images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/71e1b2125064618c40ba8703c94cfd0c/change_order_removing_product_ES.png)
+    ![change_order_removing_product_ES](https://images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/71e1b2125064618c40ba8703c94cfd0c/change_order_removing_product_ES.png)
 
 4. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
 5. A continuación, haz clic en `Revisar y aplicar`.
@@ -183,7 +183,7 @@ Para modificar el peso de un ítem, sigue estos pasos:
 3. En la página **Gestionar ítems del pedido**, en la fila del producto deseado, ingresa el nuevo peso en el campo. La unidad de medida especificada se basa en los ajustes del Catálogo. 
 4. Una vez hecho esto, en la página se muestra el precio y el peso anterior tachados, seguido del mensaje _“Ítem editado”_.
 
-    ![change_order_changing_weight_ES](//images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/8013c321665ef7545a865b9583018d07/change_order_changing_weight_ES.png)
+    ![change_order_changing_weight_ES](https://images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/8013c321665ef7545a865b9583018d07/change_order_changing_weight_ES.png)
 
 5. Revisa los [detalles del valor modificado](#consultar-detalles-de-los-valores-modificados). Si es necesario, puedes [revertir una modificación](#deshacer-acciones).
 6. Haz clic en `Revisar y aplicar`.
@@ -204,7 +204,7 @@ En la página **Gestionar ítems del pedido**, al modificar el pedido, el valor
 
 En la página **Gestionar ítems del pedido**, puedes deshacer las modificaciones si así lo deseas. Haz clic en el ícono de flecha curva `Deshacer acción`. Una vez hecho esto, aparecerá un mensaje de confirmación: _"Modificación deshecha"_, y la acción se habrá revertido.
 
-![change_order_undoing_actions_ES](//images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/46d482469764b19f63f778309f1c08b0/change_order_undoing_actions_ES.png)
+![change_order_undoing_actions_ES](https://images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/46d482469764b19f63f778309f1c08b0/change_order_undoing_actions_ES.png)
 
 ## Errores de procesamiento
 
diff --git a/docs/tutorials/es/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md b/docs/tutorials/es/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
index 0993a7c42..b69e941a1 100644
--- a/docs/tutorials/es/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
+++ b/docs/tutorials/es/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
@@ -17,8 +17,8 @@ subcategory: 1luKrYptdi8WoMYckakUaM
 
 Para habilitar el acceso a los datos del **Search Console**, usted necesita verificar la propiedad sobre su tienda. A través de etapas sencills, usted ya tendrá accesos a los datos de la performance de la indexación de su tienda en el Google.
 
-1. Acceda al Search Console utilizando una cuenta Google a través de la url: [https://www.google.com/webmasters/tools/](https://www.google.com/webmasters/tools/ "https://www.google.com/webmasters/tools/")![Primeiro passo - Verificação de Propriedade Google Search Console](//images.contentful.com/alneenqid6w5/53nfBOKjXOMGacqQIGuYKY/5d9bed2fd41df4956e89a5e52c00acc4/step_1.jpg) 
-2. Seleccione la opción **Añadir una propiedad** e inserte la URL de su tienda:![](//images.contentful.com/alneenqid6w5/5z5kYNIrzUo2mumc6WU6sC/d5e408a19b2ec6cf3c261ce490b43cab/step_2.jpg)
-3. Método de verificación, el Search Console pone a disposición diversos métodos para verificación de propiedad de su tienda, el método indicado para tiendas VTEX es el **Tag HTML** en la opción **Métodos alternativos**![](//images.contentful.com/alneenqid6w5/5QvujnxhluSkW8UOkOwUOM/86022ea4ffb6dad43f421af5ea130568/step_3.jpg)
-4. El método **Tag HTML** genera una meta tag que deberá insertarse en el template de la página inicial de su tienda. Copie el tag exhibido e insértelo entre el `<head>` del template de sua loja:![](//images.contentful.com/alneenqid6w5/3uDOqrv56oMGUK6mAewgSO/bd820d0abd57ef29c88cccc5669e314f/step_4.jpg)
-5. Luego de la inserción de la meta tag en el template, espere por cerca de 10 minutos para verificar la propiedad en el Search Console, con la verificación concluida usted ya tendrá acceso a todos los datos de indexación de la tienda:![](//images.contentful.com/alneenqid6w5/225MhXRikEygYCyagUY4MQ/11f0f693fa62a9700d6cec050267e98b/step_5.jpg)
+1. Acceda al Search Console utilizando una cuenta Google a través de la url: [https://www.google.com/webmasters/tools/](https://www.google.com/webmasters/tools/ "https://www.google.com/webmasters/tools/")![Primeiro passo - Verificação de Propriedade Google Search Console](https://images.contentful.com/alneenqid6w5/53nfBOKjXOMGacqQIGuYKY/5d9bed2fd41df4956e89a5e52c00acc4/step_1.jpg) 
+2. Seleccione la opción **Añadir una propiedad** e inserte la URL de su tienda:![](https://images.contentful.com/alneenqid6w5/5z5kYNIrzUo2mumc6WU6sC/d5e408a19b2ec6cf3c261ce490b43cab/step_2.jpg)
+3. Método de verificación, el Search Console pone a disposición diversos métodos para verificación de propiedad de su tienda, el método indicado para tiendas VTEX es el **Tag HTML** en la opción **Métodos alternativos**![](https://images.contentful.com/alneenqid6w5/5QvujnxhluSkW8UOkOwUOM/86022ea4ffb6dad43f421af5ea130568/step_3.jpg)
+4. El método **Tag HTML** genera una meta tag que deberá insertarse en el template de la página inicial de su tienda. Copie el tag exhibido e insértelo entre el `<head>` del template de sua loja:![](https://images.contentful.com/alneenqid6w5/3uDOqrv56oMGUK6mAewgSO/bd820d0abd57ef29c88cccc5669e314f/step_4.jpg)
+5. Luego de la inserción de la meta tag en el template, espere por cerca de 10 minutos para verificar la propiedad en el Search Console, con la verificación concluida usted ya tendrá acceso a todos los datos de indexación de la tienda:![](https://images.contentful.com/alneenqid6w5/225MhXRikEygYCyagUY4MQ/11f0f693fa62a9700d6cec050267e98b/step_5.jpg)
diff --git a/docs/tutorials/es/how-to-check-your-balance.md b/docs/tutorials/es/how-to-check-your-balance.md
index 788d20c0d..8ffa03c7d 100644
--- a/docs/tutorials/es/how-to-check-your-balance.md
+++ b/docs/tutorials/es/how-to-check-your-balance.md
@@ -28,7 +28,7 @@ Para consultar el saldo de su cuenta, realice los siguientes pasos:
 - Haga clic en __Resumen de la Cuenta__.
 - En el lado izquierdo de la pantalla, busque el recuadro __Saldo__.
 
-![saldodisponivelES](//images.ctfassets.net/alneenqid6w5/7uDrErDTN4Crvs1CGfU0eE/193d46204f73726cbb3941e7e6592c84/image.png_h_250_h_250)
+![saldodisponivelES](https://images.ctfassets.net/alneenqid6w5/7uDrErDTN4Crvs1CGfU0eE/193d46204f73726cbb3941e7e6592c84/image.png_h_250_h_250)
 
 El recuadro tiene dos valores. El primero, __Disponible__, presenta el saldo en cuenta libre para transacciones. El segundo, __Saldo a recibir__, muestra la suma de los pagos futuros que se registrarán en la cuenta digital corporativa.
 
diff --git a/docs/tutorials/es/how-to-configure-extra-fields-in-instore-cart.md b/docs/tutorials/es/how-to-configure-extra-fields-in-instore-cart.md
index 26cccc8d3..8552d97c9 100644
--- a/docs/tutorials/es/how-to-configure-extra-fields-in-instore-cart.md
+++ b/docs/tutorials/es/how-to-configure-extra-fields-in-instore-cart.md
@@ -22,9 +22,9 @@ Para crear los campos adicionales, siga los pasos a continuación:
 1. Verifique la configuración actual de la tienda a través del request GET en el endpoint [Get orderForm configuration](https://developers.vtex.com/vtex-rest-api/reference/getorderformconfiguration). Guarde la información JSON recebida del request.
 
 Ejemplo utilizado para la tienda "inStore":
-![2017-08-14 20 12 34-Postman](//images.contentful.com/alneenqid6w5/6I61we4oF2AMkgcIAMgEo/772e7d2b045312f1f5c76b4d8eb9d30f/2017-08-14_20_12_34-Postman.png)
+![2017-08-14 20 12 34-Postman](https://images.contentful.com/alneenqid6w5/6I61we4oF2AMkgcIAMgEo/772e7d2b045312f1f5c76b4d8eb9d30f/2017-08-14_20_12_34-Postman.png)
     2. Hacer un request POST usando el endpoint [Update orderForm configuration](https://developers.vtex.com/vtex-rest-api/reference/updateorderformconfiguration) con los mismos datos JSON guardados y agregue los campos adicionales (`fields`) con la información dentro de la propiedad `apps`.
 
 Ejemplo de request POST:
 
-![2017-08-14 20 11 18-Postman](//images.contentful.com/alneenqid6w5/6QIwIi5IBiy4qCyu2qseey/538d03ceb7f47ea0e47eb8047b931da6/2017-08-14_20_11_18-Postman.png)
+![2017-08-14 20 11 18-Postman](https://images.contentful.com/alneenqid6w5/6QIwIi5IBiy4qCyu2qseey/538d03ceb7f47ea0e47eb8047b931da6/2017-08-14_20_11_18-Postman.png)
diff --git a/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index 9568c7764..48ec8dd93 100644
--- a/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -30,7 +30,7 @@ En las operaciones B2B, existe la necesidad de mantener relaciones con los compr
 2. En la pestaña __General__, complete el valor deseado en el campo __Valor total mínimo en el carrito__.
 3. Haga clic en `Guardar`.
 
-![Minimum Order Value - ES](//images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/3571a12b0a5367cc62e982c04e8e7ece/Minimum_Order_Value_-_ES.png)
+![Minimum Order Value - ES](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/3571a12b0a5367cc62e982c04e8e7ece/Minimum_Order_Value_-_ES.png)
 
 <div class="alert alert-warning">
 El cliente tiene permitido armar un carrito con un valor menor al especificado en la regla "Valor mínimo total de la compra". Sin embargo, en el momento de finalizar la compra, sólo se completarán los pedidos que sean iguales o superiores al valor especificado.
@@ -42,7 +42,7 @@ El cliente tiene permitido armar un carrito con un valor menor al especificado e
 2. En la pestaña __General__, complete el valor deseado en el campo __Cantidad máxima de un mismo SKU en el carrito__.
 3. Haga clic en `Guardar`.
 
-![Cantidad máxima de un mismo SKU en el carrito](//images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/cfcc10ac1d2bccfb10fcd174d832f3f3/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_ES.png)
+![Cantidad máxima de un mismo SKU en el carrito](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/cfcc10ac1d2bccfb10fcd174d832f3f3/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_ES.png)
 
 <div class="alert alert-warning">
 No hay límites en el número máximo de ítems <b>del mismo SKU</b> por carrito. La única restricción se refiere al número máximo de ítems de <b>SKUs diferentes</b>, que debe ser un máximo de 300 ítems por carrito.
diff --git a/docs/tutorials/es/how-to-configure-payment-conditions.md b/docs/tutorials/es/how-to-configure-payment-conditions.md
index 037c2be71..e0d74ed92 100644
--- a/docs/tutorials/es/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/es/how-to-configure-payment-conditions.md
@@ -38,7 +38,7 @@ En los pasos siguientes, utilizaremos la tarjeta de crédito como ejemplo de con
 
 ### A vista
 
-![pagamento-a-vista es](//images.ctfassets.net/alneenqid6w5/2nH3F7oSW4OMiMQKcoAWeM/a5a96ec62da667f4f853cfc70d2def29/pago-a-vista.png)
+![pagamento-a-vista es](https://images.ctfassets.net/alneenqid6w5/2nH3F7oSW4OMiMQKcoAWeM/a5a96ec62da667f4f853cfc70d2def29/pago-a-vista.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
@@ -56,7 +56,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 
 ### En cuotas sin interés
 
-![parcelamento-sem-juros es](//images.ctfassets.net/alneenqid6w5/185SM0Kebg4S2a8IcysEsG/d0ec61a4b01dd19d2a9bcca5394d50a0/cuotas-sin-interes.png)
+![parcelamento-sem-juros es](https://images.ctfassets.net/alneenqid6w5/185SM0Kebg4S2a8IcysEsG/d0ec61a4b01dd19d2a9bcca5394d50a0/cuotas-sin-interes.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
@@ -73,7 +73,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 
 ### En cuotas con interés
 
-![parcelamento-com-juros es](//images.ctfassets.net/alneenqid6w5/3ZdPenx28oK0yG4QyeIq0c/b7184b8eeeda1573eaa60cf167be0e2c/cuotas-com-interes.png)
+![parcelamento-com-juros es](https://images.ctfassets.net/alneenqid6w5/3ZdPenx28oK0yG4QyeIq0c/b7184b8eeeda1573eaa60cf167be0e2c/cuotas-com-interes.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. En la pestana __Condiciones de pago__, haga clic en el botón __+__.
@@ -91,7 +91,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 14. Para elegir entre interés compuesto e interés simple, haga clic en __Interés compuesto aplicado. Cambiar__. Aparecerá una casilla de verificación que ofrece ambas opciones.
 15. Haga clic en __Guardar__.
 
-![Juros - es](//images.ctfassets.net/alneenqid6w5/5DQndlL3ixGVYBKBOTsVM7/70c11c8cbf6fa5d088c381c34d63454b/Juros_-_es.png)
+![Juros - es](https://images.ctfassets.net/alneenqid6w5/5DQndlL3ixGVYBKBOTsVM7/70c11c8cbf6fa5d088c381c34d63454b/Juros_-_es.png)
 
 #### Intereses Externos
 
@@ -107,4 +107,4 @@ En algunos países, los intereses de las compras parceladas son cobrados directa
 2. En la pestana __Condiciones de pago__, haga clic en el condición de pago que desea eliminar.
 3. Haga clic en el icono de la papelera.
 
-![Remover condición de pago](//images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/76f4023f4e0262ebaefa8318e46330b3/remover_condicion_pago.png)
+![Remover condición de pago](https://images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/76f4023f4e0262ebaefa8318e46330b3/remover_condicion_pago.png)
diff --git a/docs/tutorials/es/how-to-configure-rating-and-review-controls.md b/docs/tutorials/es/how-to-configure-rating-and-review-controls.md
index 1cc59bf07..aa0b8306f 100644
--- a/docs/tutorials/es/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/es/how-to-configure-rating-and-review-controls.md
@@ -42,10 +42,10 @@ Diferente de los demás, estos controles necesitan una configuración imprescind
 
 En el registro de Categoria existe la opción de configurar la Avaliação (Evaluación) y normalmente esta configuración se hace en la categoría raíz:
 
-![avaliação-categoria ES](//images.ctfassets.net/alneenqid6w5/2iOensHpjSW8aYCqi2o2O8/548b7ff362e70275c73dbc9b0b2239d6/avalia____o_es.png)
+![avaliação-categoria ES](https://images.ctfassets.net/alneenqid6w5/2iOensHpjSW8aYCqi2o2O8/548b7ff362e70275c73dbc9b0b2239d6/avalia____o_es.png)
 
 Haga click en **Nueva Calificación** y rellene los datos Nome (Nombre) y Texto y después grabe.
 
-![nueva-calificacion-categorias ES](//images.ctfassets.net/alneenqid6w5/5A1DGDfYGI4syYkYGkAI86/c9fd86d9e6bbe8c61828e28e4cd0f5de/Nueva_calificacion.png)
+![nueva-calificacion-categorias ES](https://images.ctfassets.net/alneenqid6w5/5A1DGDfYGI4syYkYGkAI86/c9fd86d9e6bbe8c61828e28e4cd0f5de/Nueva_calificacion.png)
 
 ¡Listo! Sus controles de Reseña y Evaluación están listos para usarse.
diff --git a/docs/tutorials/es/how-to-configure-taxhub.md b/docs/tutorials/es/how-to-configure-taxhub.md
index fa4e2d19c..86f8d3848 100644
--- a/docs/tutorials/es/how-to-configure-taxhub.md
+++ b/docs/tutorials/es/how-to-configure-taxhub.md
@@ -25,4 +25,4 @@ Para configurar el sistema de impuestos TaxHub, siga los pasos abajo:
 6.	En **Token de Autorización** llene con el token del servicio del paso anterior. Nota: En algunos casos puede no ser necesario;
 7.	Haga clic en **Salvar**.
 
-![TaxHub Configuration](//images.contentful.com/alneenqid6w5/RG3lWrwAOAyQYwk6gwGgq/7f291339357dac4cf07fbee9f5e0a649/TaxHubConfiguration.gif)
+![TaxHub Configuration](https://images.contentful.com/alneenqid6w5/RG3lWrwAOAyQYwk6gwGgq/7f291339357dac4cf07fbee9f5e0a649/TaxHubConfiguration.gif)
diff --git a/docs/tutorials/es/how-to-configure-the-favicon.md b/docs/tutorials/es/how-to-configure-the-favicon.md
index 31a3a79ff..29af2d2ab 100644
--- a/docs/tutorials/es/how-to-configure-the-favicon.md
+++ b/docs/tutorials/es/how-to-configure-the-favicon.md
@@ -19,7 +19,7 @@ El favicon es el icono exhibido en la pestaña del browser, al lado del título
 
 Ejemplo:
 
-![favicon_2](//images.contentful.com/alneenqid6w5/2azvX7m3asGckkU6c8WAcM/2e66d9a107c0394c3f1a63afff7f3149/favicon_2-1024x537.png "Favicon 2")
+![favicon_2](https://images.contentful.com/alneenqid6w5/2azvX7m3asGckkU6c8WAcM/2e66d9a107c0394c3f1a63afff7f3149/favicon_2-1024x537.png "Favicon 2")
 
 Utilicé Google como ejemplo solamente para reforzar que ese recurso no es exclusivo de VTEX y se puede utilizarlo en cualquier contenido reproducido en un browser. Lea más sobre este asunto en Google. 🙂
 
@@ -33,4 +33,4 @@ En VTEX, para asegurar que el favicon esté cargado durante toda la navegación
 
 **Obs. 2:** La variable `{NOMBREDELATIENDA}` debe ser sustituida por el nombre de la tienda según esté registrado en el Gestión de la cuenta.
 
-![fav](//images.contentful.com/alneenqid6w5/6j5eZzVMEE6E2KgqGgsOwU/c2292316f75f3620cd870c96df9e65fc/fav-1024x554.png)
+![fav](https://images.contentful.com/alneenqid6w5/6j5eZzVMEE6E2KgqGgsOwU/c2292316f75f3620cd870c96df9e65fc/fav-1024x554.png)
diff --git a/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md b/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md
index 3fee6d112..42b5bd6b1 100644
--- a/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md
+++ b/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md
@@ -32,7 +32,7 @@ Las configuraciones documentadas en este artículo se realizan en un ambiente ex
 Para insertar los scripts que exige Stelo al device fingerprint, es necessário usar el Google Tag Manager. Para ello, haga login en su cuenta en [http://www.google.com/tagmanager](http://www.google.com/tagmanager). Después, siga los pasos a continuación:
 
 1. En el menú inicial del Google Tag Manager, haga clic en **Nova tag**;
-2. Seleccione ** Configuração da tag ** y elija el tipo **HTML personalizado**.![Tela1](//images.contentful.com/alneenqid6w5/2VjcP3lQ9aqceC82kgaAU8/68bffad6d79e91e7286c780ac16fffc7/Tela1.jpg);
+2. Seleccione ** Configuração da tag ** y elija el tipo **HTML personalizado**.![Tela1](https://images.contentful.com/alneenqid6w5/2VjcP3lQ9aqceC82kgaAU8/68bffad6d79e91e7286c780ac16fffc7/Tela1.jpg);
 
 Entonces, inserte el script a continuación:
 
@@ -51,13 +51,13 @@ window.vtex.deviceFingerprint = match[1];
 
 Después, siga los pasos a continuación:
 
-1. Haga clic en **Acionamento**, Novo acionador (símbolo de **+** en la esquina superior derecha) y en ** Configuração do acionador.**![Tela2](//images.contentful.com/alneenqid6w5/6uwEr6KGJyOCcigIMCcUoS/4142ad24f3121bee1fea9d55069d10a6/Tela2.jpg);
+1. Haga clic en **Acionamento**, Novo acionador (símbolo de **+** en la esquina superior derecha) y en ** Configuração do acionador.**![Tela2](https://images.contentful.com/alneenqid6w5/6uwEr6KGJyOCcigIMCcUoS/4142ad24f3121bee1fea9d55069d10a6/Tela2.jpg);
 2. Elija el tipo **Evento personalizado** e inserte el nombre **payment**;
 3. Seleccione la flag **Alguns eventos personalizados**;
-4. En las dos primeras cajas abajo, seleccione: **Event** y **é igual a**. En la tercera, escriba **payment**.![Tela3](//images.contentful.com/alneenqid6w5/5sbXgbm4g0yysWKSwmYWI0/e7d605639093f30aff58bff0efef2ae4/Tela3.jpg)
+4. En las dos primeras cajas abajo, seleccione: **Event** y **é igual a**. En la tercera, escriba **payment**.![Tela3](https://images.contentful.com/alneenqid6w5/5sbXgbm4g0yysWKSwmYWI0/e7d605639093f30aff58bff0efef2ae4/Tela3.jpg)
 5. Guarde el accionador y la tag;
 6. En el menú lateral, haga clic en la opción **Variables** y después en **Nueva**;
-7. Haga clic en **Configuração da variável** y elija el tipo **JavaScript personalizado**;![Tela4](//images.contentful.com/alneenqid6w5/3I7Eq6Jt2wkYg6EoKAkCqC/91cca1c81534bbbc76e70db8f94be13a/Tela4.jpg)
+7. Haga clic en **Configuração da variável** y elija el tipo **JavaScript personalizado**;![Tela4](https://images.contentful.com/alneenqid6w5/3I7Eq6Jt2wkYg6EoKAkCqC/91cca1c81534bbbc76e70db8f94be13a/Tela4.jpg)
 
 Finalmente, inserte el script a continuación:
 
diff --git a/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md b/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md
index 6ffc0e6c9..1bd9873a8 100644
--- a/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md
+++ b/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md
@@ -37,7 +37,7 @@ Puede configurar Google Shopping a través de VTEX Admin siguiendo los siguiente
   El enlace de acceso XML se generará automáticamente.
 9. Guarde este XML en un archivo .txt y envíe el archivo a Google.
 
-![](//images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
+![](https://images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
 
 <div class = "alert alert-warning">
   <p>Si la opción <strong>Mostrar SKU no disponibles</strong> está desmarcada, los productos o SKU que estén agotados no aparecerán en el XML. Los productos inactivos tampoco aparecerán en el XML.</p>
diff --git a/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md b/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
index 111430164..e52c8627f 100644
--- a/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
+++ b/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
@@ -21,7 +21,7 @@ Siguiendo la [Actualización de 2015 de la Especificación del feed del Google S
 
 La configuración patrón de nuestro formulario de XML ya está con las tags actualizadas, para crear un nuevo feed Google Merchant / Shopping basta seleccionar la opción “Feed: Atom 1”:
 
-![](//images.contentful.com/alneenqid6w5/2ugQUy4xlaaUEOIYuu6UMe/41fd01c32b6954b14e1ef5818b94ca0c/atom1_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/2ugQUy4xlaaUEOIYuu6UMe/41fd01c32b6954b14e1ef5818b94ca0c/atom1_xml_vtex_google.gif)
 
 Para la correcta integración con el Google Merchant / Shopping será necesario actualizar el xml con los nuevos campos a partir del 15 de septiembre de 2015.
 
@@ -31,7 +31,7 @@ Conozca los nuevos campos del formulario de XML:
 
 Opción responsable de la definición de la taxonomía de los campos “Categoría” y “Departamento + Categoría”. Comúnmente utilizado para el llenado de la tag [g:product\_type].
 
-![](//images.contentful.com/alneenqid6w5/3dgBcIJZgcKSW2YKCaksmW/653d517228e7d303e7326dfa1dcedbc1/separador_categoria_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/3dgBcIJZgcKSW2YKCaksmW/653d517228e7d303e7326dfa1dcedbc1/separador_categoria_xml_vtex_google.gif)
 
 Patrón (Ej.: Categoría Padre – Categoría Hija – Categoría Nieta)
 
@@ -47,7 +47,7 @@ Campo responsable de la relación de las categorías de su tienda con las catego
 
 Deberá llenarse con la tag [g:google\_product\_category]
 
-![](//images.contentful.com/alneenqid6w5/307z7lsmEMgQMWIOUQWk8K/9d854eb77bb73e1c79d5307c78fb0215/categoria_global_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/307z7lsmEMgQMWIOUQWk8K/9d854eb77bb73e1c79d5307c78fb0215/categoria_global_xml_vtex_google.gif)
 
 Para el correcto funcionamiento de este campo es necesario verificar si el producto tiene el campo **Categoría Global** llenado en el catálogo VTEX.
 
diff --git a/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md b/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md
index 57843fe60..4175c2ee2 100644
--- a/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md
+++ b/docs/tutorials/es/how-to-create-a-development-environment-with-a-mobile-version.md
@@ -38,7 +38,7 @@ Para desarrollar una versión mobile con un nuevo WebSite, debe seguir los sigui
 
 Storefront > Layout > Carpeta de CMS > Sites and Channels > New Website
 
-![cms-new-website](//images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
+![cms-new-website](https://images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
 
 3. Crear estructura de carpetas del WebSite Mobile: en este paso será necesario crear las carpetas estándar del sistema que se usarán en la versión mobile (búsqueda, departamento, categoría, marca, producto, etc.)
 
diff --git a/docs/tutorials/es/how-to-create-a-financial-access-profile.md b/docs/tutorials/es/how-to-create-a-financial-access-profile.md
index 954719d89..4de4269a4 100644
--- a/docs/tutorials/es/how-to-create-a-financial-access-profile.md
+++ b/docs/tutorials/es/how-to-create-a-financial-access-profile.md
@@ -31,7 +31,7 @@ Para crear un rol financiero:
 6. (Opcional) Antes de guardar, usted puede **Agregar usuarios a este rol**.
 7. Haga clic en **Guardar**.
 
-![gif perfildeacessoES](//images.ctfassets.net/alneenqid6w5/3JYWgBIlkkg4VFG1AgFHoc/9d68fb02cf08d64dda981ea3d1ff3935/gif_perfildeacessoES.gif)
+![gif perfildeacessoES](https://images.ctfassets.net/alneenqid6w5/3JYWgBIlkkg4VFG1AgFHoc/9d68fb02cf08d64dda981ea3d1ff3935/gif_perfildeacessoES.gif)
 
 El rol financiero ahora está creado y está disponible para asociarlo con usuarios existentes.
 
@@ -47,7 +47,7 @@ Es posible asociar un usuario con el rol Finance ya existente:
 6. Haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> al lado del rol seleccionado para agregarlo.
 7. Para finalizar, haga clic en **Guardar**.
 
-![gif usuárioES](//images.ctfassets.net/alneenqid6w5/gRA4oVVbG7Z8ksFX4QiWm/f097214bc3c314a36dc384efcbc51980/gif_usu__rioES.gif)
+![gif usuárioES](https://images.ctfassets.net/alneenqid6w5/gRA4oVVbG7Z8ksFX4QiWm/f097214bc3c314a36dc384efcbc51980/gif_usu__rioES.gif)
 
 El usuario seleccionado ahora está asociado con el rol Financiero y podrá acceder a facturas, información sobre contratos, cobros y otra información financiera.
 
diff --git a/docs/tutorials/es/how-to-create-a-page-template.md b/docs/tutorials/es/how-to-create-a-page-template.md
index b3ed441ce..a8a1e9552 100644
--- a/docs/tutorials/es/how-to-create-a-page-template.md
+++ b/docs/tutorials/es/how-to-create-a-page-template.md
@@ -46,7 +46,7 @@ Vea a continuación el procedimiento:
 <li><code>app</code></li>
 </ul></p>
 </div>
-6. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+6. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. En la esquina superior derecha, haga clic en el botón  __Save Template__.
 
 Para editar un template ya existente, el proceso es casi idéntico.
diff --git a/docs/tutorials/es/how-to-create-a-product.md b/docs/tutorials/es/how-to-create-a-product.md
index 1a63b52f8..f227aeac2 100644
--- a/docs/tutorials/es/how-to-create-a-product.md
+++ b/docs/tutorials/es/how-to-create-a-product.md
@@ -87,7 +87,7 @@ Para agregar imágenes al producto, siga las instrucciones a continuación:
 
 Puede hacer clic en una imagen y arrastrarla para posicionarla antes o después de las otras si desea reorganizar las imágenes y cambiar el orden de visualización en la página del producto, como se ilustra a continuación.
 
-![imagens-sku-ES](//images.contentful.com/alneenqid6w5/ePL8umUhPBzy7RCTx6blG/75dba8571076bf8e2d972da51a02c224/imagens-sku-ES.gif)
+![imagens-sku-ES](https://images.contentful.com/alneenqid6w5/ePL8umUhPBzy7RCTx6blG/75dba8571076bf8e2d972da51a02c224/imagens-sku-ES.gif)
 
 Puede modificar la información de cada imagen haciendo clic en el botón <i class="fas fa-ellipsis-v"></i> en la fila de cada una, esto abre un menú con las siguientes opciones.
 
@@ -122,7 +122,7 @@ Ejemplo: una tienda de cosméticos puede configurar los grupos de atributos de u
   1. Tiempo de fijación: largo.
   2. Tipo de aplicación: spray.
 
-![atributo-ES](//images.contentful.com/alneenqid6w5/8NYBzqEEONslutbIBciw1/6ecfe23b8462b39921ce748bef78e640/atributo-ES.gif)
+![atributo-ES](https://images.contentful.com/alneenqid6w5/8NYBzqEEONslutbIBciw1/6ecfe23b8462b39921ce748bef78e640/atributo-ES.gif)
 
 Después de realizar los cambios deseados en el panel de atributos, haga clic en `Aplicar`.
 
@@ -165,7 +165,7 @@ Después de llevar a cabo este procedimiento, las especificaciones creadas y sus
 
 Además, a partir de las opciones creadas, la lista de SKU posibles se genera automáticamente y se muestra en la sección **[Variaciones](#variaciones)**.
 
-![variations ES](//images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/74c9b1a069394f60e647acd42130f24c/variations_ES.png)
+![variations ES](https://images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/74c9b1a069394f60e647acd42130f24c/variations_ES.png)
 
 ## Especificaciones
 
@@ -196,7 +196,7 @@ Al hacer clic en el botón <i class="fas fa-ellipsis-v"></i>, puede realizar las
   * **Seleccionar imágenes:** seleccione las imágenes correspondientes a la variación. Para seleccionar una imagen, basta con hacer clic en ella. Si quiere seleccionar todas las imágenes a la vez, puede utilizar el acceso directo pulsando `Ctrl` + `A` en el teclado.
   * **Aplicar a múltiples variaciones:** si lo desea, puede aplicar las imágenes seleccionadas a múltiples variaciones. Para eso, haga clic en `Aplicar a múltiples variaciones +` y seleccione los valores de las especificaciones relacionadas con su imagen. Por ejemplo: si la imagen es de una zapatilla deportiva de color beige, debe seleccionar la opción `beige` de la especificación `color` en este campo. Con esta configuración, la imagen se aplicará a todas las variaciones cuya especificación de `color` tenga el valor `beige`, independientemente de otras especificaciones configuradas, como el `tamaño`. La siguiente imagen ilustra este flujo de configuración.
 
-![variacoes-ES](//images.contentful.com/alneenqid6w5/3xeQNRanqPwUZazIEdPjT6/5ddd5e6421a9edd14151e4fd893af09c/variacoes-ES.gif)
+![variacoes-ES](https://images.contentful.com/alneenqid6w5/3xeQNRanqPwUZazIEdPjT6/5ddd5e6421a9edd14151e4fd893af09c/variacoes-ES.gif)
 
   * **Agregar imágenes:** en este panel, también se puede cargar nuevas imágenes haciendo clic en el botón `Agregar imágenes` o arrastrando y soltando los archivos de imagen en el espacio delimitado por la línea punteada.
 * **Desactivar:** desactive la variación en su tienda. 
@@ -208,7 +208,7 @@ Al hacer clic en el botón <i class="fas fa-ellipsis-v"></i>, puede realizar las
 ### Edición avanzada
 El panel de edición avanzada de variaciones, que se ilustra a continuación, permite ver y editar toda la información y las imágenes relacionadas con cada variación del producto. 
 
-![Edición avanzada ES](//images.contentful.com/alneenqid6w5/3euZICBWkiKr0l6qu4bZ5R/11d449c231ffefe0794b93c6d395ef92/Screenshot_14.png)
+![Edición avanzada ES](https://images.contentful.com/alneenqid6w5/3euZICBWkiKr0l6qu4bZ5R/11d449c231ffefe0794b93c6d395ef92/Screenshot_14.png)
 
 En la sección **Variaciones**, en el lado izquierdo del panel, encontrará la lista de variaciones de su producto. Para editar una variación específica, debe hacer clic en ella.
 
@@ -219,7 +219,7 @@ Para editar un gran número de variaciones a la vez, puede utilizar la funcional
 
 1. Haga clic en el botón `Edición en masa` para abrir la plantilla de edición de variaciones.
 2. Para editar la información en la plantilla, debe hacer doble clic en el campo que desee modificar.
-![edicao-massa-SKU-ES](//images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/def837067f47c559d8199af8c9de8169/image.png)
+![edicao-massa-SKU-ES](https://images.ctfassets.net/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/def837067f47c559d8199af8c9de8169/image.png)
 
 En la plantilla puede editar la siguiente información:
 - **Activo:** indica si la variación está activa o no.
@@ -235,7 +235,7 @@ En la plantilla puede editar la siguiente información:
 Para filtrar las columnas mostradas en la plantilla, haga clic en `Filtrar columnas` y seleccione las columnas que desee ocultar.
 
 Puede replicar la información de una celda a otras filas y columnas. Para ello, haga clic en el cuadrado azul en la esquina inferior derecha de la celda y arrástrelo a las celdas en las que desee replicar automáticamente el valor, como se muestra en la imagen a continuación.
-![Formatacao-celula-ES](//images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/bc801e55c612036ff1c0481bb1cc3bc3/Formatacao-celula-ES.gif)
+![Formatacao-celula-ES](https://images.ctfassets.net/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/bc801e55c612036ff1c0481bb1cc3bc3/Formatacao-celula-ES.gif)
 3. Después de editar, haga clic en `Aplicar` para guardar los cambios.
 
 ## SEO
@@ -248,7 +248,7 @@ La manera de completar los campos de esta sección influye en la posición que e
 
 Al rellenar los campos de SEO, se puede observar, en el lado derecho, la vista previa del producto en los resultados de Google. A continuación, vea un ejemplo de cómo completar tales campos.
 
-![SEO-ES](//images.contentful.com/alneenqid6w5/1Mf7tKJD1xvZt4sieGdBSc/2c2d8a5672aa52dc79fb56671c1ca0bb/Screenshot_11.png)
+![SEO-ES](https://images.contentful.com/alneenqid6w5/1Mf7tKJD1xvZt4sieGdBSc/2c2d8a5672aa52dc79fb56671c1ca0bb/Screenshot_11.png)
 
 ## Storefront
 
diff --git a/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
index 642d3aca2..a2ead9ef7 100644
--- a/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
@@ -21,7 +21,7 @@ Para que una promoción del tipo regular sea aplicada por un número limitado de
 <p>Los pedidos con status <code>Iniciando cancelación</code> o <code>Cancelado</code> no cuentan para el límite establecido.</p>
 </div>
 
-![Promocion con limite de uso](//images.ctfassets.net/alneenqid6w5/6RuP1uG4Cc8MWm2OikwimK/9a4d5dcdf67edbd058cf1dae705fa1e9/Promocion_con_limite_de_uso.png)
+![Promocion con limite de uso](https://images.ctfassets.net/alneenqid6w5/6RuP1uG4Cc8MWm2OikwimK/9a4d5dcdf67edbd058cf1dae705fa1e9/Promocion_con_limite_de_uso.png)
 
 También es posible configurar el límite por cliente, en vez de límite por promoción. Para ello, basta hacer la configuración arriba y hacer clic en la opción **Habilitar límite de uso por cliente**.
 
diff --git a/docs/tutorials/es/how-to-create-a-store-name.md b/docs/tutorials/es/how-to-create-a-store-name.md
index 877348425..0059b89f9 100644
--- a/docs/tutorials/es/how-to-create-a-store-name.md
+++ b/docs/tutorials/es/how-to-create-a-store-name.md
@@ -23,7 +23,7 @@ Para crear o editar un [nombre de la tienda](https://help.vtex.com/es/tutorial/o
 4. En el dashboard de la tienda, verás los nombres de la tienda que ya hay en tu cuenta. Puedes editar la información de cada tienda, o crear un nuevo nombre de la tienda, al hacer clic en el botón **Configurar esta tienda**.
 5. Para saber cómo configurar el dominio de tus tiendas, consulta el artículo [Cambiar el dominio de la tienda](https://help.vtex.com/es/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
-![Configuracion de nombre de tienda](//images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/95ef9845c325ed8b55632be5ac1c3bab/ES.PNG)
+![Configuracion de nombre de tienda](https://images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/95ef9845c325ed8b55632be5ac1c3bab/ES.PNG)
 
 Para saber cómo configurar el dominio de tus tiendas, consulta el artículo [Cambiar el dominio de la tienda](https://help.vtex.com/es/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
diff --git a/docs/tutorials/es/how-to-create-a-subscription-attachment.md b/docs/tutorials/es/how-to-create-a-subscription-attachment.md
index 38220709f..34e5cc0dd 100644
--- a/docs/tutorials/es/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/es/how-to-create-a-subscription-attachment.md
@@ -71,11 +71,11 @@ Siga las instrucciones a continuación para configurar la frecuencia y fechas de
 
         * **Semanalmente:** los valores posibles para completar este campo son = `0`, `1`, `2`, `3`, `4`, `5` y `6`, que equivalen a los días de la semana. Considere `0` = domingo, `1` = lunes, `2` = martes, y así sucesivamente hasta `6` = sábado. Separe los valores con `,`, según se muestra a continuación.
 
-        ![ES Assinatura Exemplo Valores week](//images.ctfassets.net/alneenqid6w5/1KDaD3iRFBwt7xrikkB8V9/ecfe9cb9da8bb798d410f5d709c8b04d/ES_Assinatura_Exemplo_Valores_week.png)
+        ![ES Assinatura Exemplo Valores week](https://images.ctfassets.net/alneenqid6w5/1KDaD3iRFBwt7xrikkB8V9/ecfe9cb9da8bb798d410f5d709c8b04d/ES_Assinatura_Exemplo_Valores_week.png)
 
         * **Mensualmente:** los valores posibles para rellenar este campo en el _checkout_ son = `1`, `2`, `3`, `4`, `5`, `6`, `7`, `8`, `9`, (...) hasta `28`, que equivalen a los días del mes. Considere `1` = primer día del mes, `2` = segundo día del mes, `3` = tercer día del mes, y así sucesivamente hasta `28` = vigésimo octavo día del mes. Separe los valores con `,`, según se muestra a continuación.
 
-        ![ES Assinatura Exemplo Valores month](//images.ctfassets.net/alneenqid6w5/5tbntKlv4WeYUXQtM8EMGz/84d58a31d1b449fdbdfad60fae5dec0d/ES_Assinatura_Exemplo_Valores_month.png)
+        ![ES Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/5tbntKlv4WeYUXQtM8EMGz/84d58a31d1b449fdbdfad60fae5dec0d/ES_Assinatura_Exemplo_Valores_month.png)
 
 <div class="alert alert-info">
   <p>Si no se introduce ningún valor en el campo <strong>Valores permitidos</strong>, la fecha del ciclo de suscripción será el mismo día de la semana (si la frecuencia es semanal) o día del mes (si la frecuencia es mensual) del pedido original.</p>
diff --git a/docs/tutorials/es/how-to-create-conditional-prices.md b/docs/tutorials/es/how-to-create-conditional-prices.md
index 781a8113c..736d3ac21 100644
--- a/docs/tutorials/es/how-to-create-conditional-prices.md
+++ b/docs/tutorials/es/how-to-create-conditional-prices.md
@@ -33,4 +33,4 @@ El siguiente es un paso a paso de cómo usar estos precios condicionales:
 6. Usted puede definir un pequeño mensaje, llamado *Teaser*, para promover esa condición a su cliente. (Para entender mejor, vea [Teasers - En breve])
 7. Guarde.
 
-![conditionalPrice](//images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
+![conditionalPrice](https://images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
diff --git a/docs/tutorials/es/how-to-create-the-script-customization-file-for-vtex-instore.md b/docs/tutorials/es/how-to-create-the-script-customization-file-for-vtex-instore.md
index 531aa09cc..9daacd7e3 100644
--- a/docs/tutorials/es/how-to-create-the-script-customization-file-for-vtex-instore.md
+++ b/docs/tutorials/es/how-to-create-the-script-customization-file-for-vtex-instore.md
@@ -17,20 +17,20 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 
 Para crear el archivo de personalización basta acceder al Portal por la topbar y crear un nuevo archivo con el nombre `checkout-instore-custom.js`. Ese archivo lo cargará el inStore automáticamente.
 
-![topbar-portal](//images.contentful.com/alneenqid6w5/2Xenr5P0EMKCAyOq2Qmiaw/98fa99c841313072099b11553785660e/topbar-portal.png)
+![topbar-portal](https://images.contentful.com/alneenqid6w5/2Xenr5P0EMKCAyOq2Qmiaw/98fa99c841313072099b11553785660e/topbar-portal.png)
 
 Al abrir el módulo del Portal debe hacer clic en el botón de editar el site default. En el ejemplo a continuación el accountname de la tienda es __Omniera__.
 
-![portal-default-website](//images.contentful.com/alneenqid6w5/7GHyB8nH6o62e4MWsskgCI/e5066603fe42d311f30b47055cca9cbf/portal-default-website.png)
+![portal-default-website](https://images.contentful.com/alneenqid6w5/7GHyB8nH6o62e4MWsskgCI/e5066603fe42d311f30b47055cca9cbf/portal-default-website.png)
 
 Ahora debe hacer clic en la pestaña `Código` y luego en el botón de `Nuevo` donde debe seleccionar la opción de nuevo `Archivo`
 
-![portal-add-file](//images.contentful.com/alneenqid6w5/1qDZc7Yj6wyaAkIaIEMEeI/461efb062c3cc02c11084908bbb01ecc/portal-add-file.png)
+![portal-add-file](https://images.contentful.com/alneenqid6w5/1qDZc7Yj6wyaAkIaIEMEeI/461efb062c3cc02c11084908bbb01ecc/portal-add-file.png)
 
 Rellene el nombre del archivo como `checkout-instore-custom.js` y haga clic en `Crear`
 
-![portal-add-file-filename](//images.contentful.com/alneenqid6w5/6vdp46Cv0AgG6caSgQOe2i/3026dfc7f1de5e7b828863b5435a99c1/portal-add-file-filename.png)
+![portal-add-file-filename](https://images.contentful.com/alneenqid6w5/6vdp46Cv0AgG6caSgQOe2i/3026dfc7f1de5e7b828863b5435a99c1/portal-add-file-filename.png)
 
 Ya está, ahora usted puede adicionar el contenido del archivo y guardar. Automáticamente el inStore cargará el archivo de personalización.
 
-![portal-edit-file](//images.contentful.com/alneenqid6w5/7HxG61bw1aW0yuK6OIycyU/dde5f00b9aeec4bbc05b7b18ebd1b0f3/portal-edit-file.png)
+![portal-edit-file](https://images.contentful.com/alneenqid6w5/7HxG61bw1aW0yuK6OIycyU/dde5f00b9aeec4bbc05b7b18ebd1b0f3/portal-edit-file.png)
diff --git a/docs/tutorials/es/how-to-customize-a-page-using-placeholders.md b/docs/tutorials/es/how-to-customize-a-page-using-placeholders.md
index 55907c55f..6d2f7b063 100644
--- a/docs/tutorials/es/how-to-customize-a-page-using-placeholders.md
+++ b/docs/tutorials/es/how-to-customize-a-page-using-placeholders.md
@@ -39,8 +39,8 @@ Recordando que el `htmlSeo` es el nombre del control creado arriba. Este contro
 ```
 **Ejemplos**
 
-![](//images.contentful.com/alneenqid6w5/5LY7pZwZpe8iQiWccqCc26/d4c10dc57a8f6091dd5c23ec3fdad12e/2016-04-05_17_15_29-Index.png) 
-![](//images.contentful.com/alneenqid6w5/45kPL4QTfqMkYuAYQEeuC2/aed1934b3268ccb8310226e0e6ce9ff3/2016-04-05_17_15_58-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5LY7pZwZpe8iQiWccqCc26/d4c10dc57a8f6091dd5c23ec3fdad12e/2016-04-05_17_15_29-Index.png) 
+![](https://images.contentful.com/alneenqid6w5/45kPL4QTfqMkYuAYQEeuC2/aed1934b3268ccb8310226e0e6ce9ff3/2016-04-05_17_15_58-Index.png)
 
 **Obs.:** la aplicación del placeholder puede ser realizada de otras maneras hasta que atienda el local, el formato, o sea, la necesidad del dueño de la tienda.
 
@@ -50,23 +50,23 @@ Para incluir una descripción para Categoria (Categoria), siga los pasos abajo:
 
 1. Entre en Configurações > Portal
 2. Haga clic en Portal > Web-sites > [nomedaloja] > / > categoria > @categoria@ > categoria
-![](//images.contentful.com/alneenqid6w5/5IrVEkqOlyy644oAwGS0Ou/b82465f649790ab7bbbce5ea4d416265/2016-04-05_16_21_49-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5IrVEkqOlyy644oAwGS0Ou/b82465f649790ab7bbbce5ea4d416265/2016-04-05_16_21_49-Index.png)
 3. Entre en la pestaña **Configurações**
-![](//images.contentful.com/alneenqid6w5/bhebyo6cBaKy2wa8O4moA/fe1f57b2ef00101ba21effb442206043/2016-04-05_16_25_11-Index.png)
+![](https://images.contentful.com/alneenqid6w5/bhebyo6cBaKy2wa8O4moA/fe1f57b2ef00101ba21effb442206043/2016-04-05_16_25_11-Index.png)
 4. Haga clic en **Adicionar Controle**
 5. Seleccione el tipo de control que desea, generalmente HTML
-![](//images.contentful.com/alneenqid6w5/42vmuVKKdWSwcc0gsuwimi/91fe4618316504de9ea0fb385e46df6b/2016-04-05_16_34_31-Index.png)
+![](https://images.contentful.com/alneenqid6w5/42vmuVKKdWSwcc0gsuwimi/91fe4618316504de9ea0fb385e46df6b/2016-04-05_16_34_31-Index.png)
 6. Haga clic en **Adicionar**
 7. Haga clic en **Salvar Configurações**
 8. Haga clic en **Editar**
 9. Haga clic en **Adicionar Conteúdo**
-![](//images.contentful.com/alneenqid6w5/6Ou1gOdTZCWKqIwUA682C6/6f241a6ad96fc83cf6830622ababe08f/2016-04-05_16_34_58-Index.png)
+![](https://images.contentful.com/alneenqid6w5/6Ou1gOdTZCWKqIwUA682C6/6f241a6ad96fc83cf6830622ababe08f/2016-04-05_16_34_58-Index.png)
 10. Cree el HTML que le gustaría que aparezca en el sitio
 11. En la pestaña **Preview** podrá tener una visualización previa del HTML
 12. En los campos **Condições de Exibição**, configure de acuerdo a su necesidad, por ejemplo, seleccione una Categoría en la que este contenido estará disponible.
 13. Haga clic en el checkbox **Conteúdo Ativo**
 14. Haga clic en **Adicionar na Lista de Conteúdo**
-![](//images.contentful.com/alneenqid6w5/5tqciHrAD6aAgiSIwiKSKE/8ba1d1a683c168257e16dd949133809b/2016-04-05_16_28_19-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5tqciHrAD6aAgiSIwiKSKE/8ba1d1a683c168257e16dd949133809b/2016-04-05_16_28_19-Index.png)
 15. Haga clic en **Salvar Configurações**
 
 
diff --git a/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md b/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md
index 80d2512a6..953b21d97 100644
--- a/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md
+++ b/docs/tutorials/es/how-to-customize-the-checkout-ui-custom-in-the-admin.md
@@ -63,25 +63,25 @@ En esta pestaña puedes configurar los siguientes ajustes:
 
 La pestaña Colores facilita la personalización de los colores del checkout de tu tienda, lo que incluye la modificación de los colores del fondo, de los botones o del texto, por ejemplo. Esta estandarización garantiza una armonía visual consistente.
 
-![Colores](//images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/a6ded356e1627c5cc91465aaca09c047/Colores_-_ES.png)
+![Colores](https://images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/a6ded356e1627c5cc91465aaca09c047/Colores_-_ES.png)
 
 ## JavaScript
 
 La pestaña JavaScript agrega un nivel adicional de personalización de la interfaz al posibilitar la inserción de scripts.
 
-![Java - ES](//images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/828e33a5b4a8a02130e3c63de6588dfe/Java_-_ES.png)
+![Java - ES](https://images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/828e33a5b4a8a02130e3c63de6588dfe/Java_-_ES.png)
 
 ## CSS
 
 La pestaña CSS permite ajustar el aspecto visual de la tienda mediante la inclusión de código CSS.
 
-![CSS - ES](//images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/415c6d4c0d23401f7293a94b585da15c/CSS_-_ES.png)
+![CSS - ES](https://images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/415c6d4c0d23401f7293a94b585da15c/CSS_-_ES.png)
 
 ## Historial
 
 Permite ver y restaurar las personalizaciones creadas y publicadas anteriormente.
 
-![Histórico - ES](//images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/5f06f5a14093fa8f112e0fc08b3f686a/Hist_rico_-_ES.png)
+![Histórico - ES](https://images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/5f06f5a14093fa8f112e0fc08b3f686a/Hist_rico_-_ES.png)
 
 Para asegurarte de que la configuración se aplique correctamente, solo tienes que configurar los ajustes necesarios y hacer clic en el botón `Publicar`.
 
diff --git a/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
index 61784f456..790d81879 100644
--- a/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
@@ -23,7 +23,7 @@ Puedes cambiar el campo **textLink** de un producto existente en cualquier momen
 
 Consulta la sección [Reglas de llenado](#reglas-de-llenado) para conocer las restricciones de este campo.
 
-![textlink.es](//images.ctfassets.net/alneenqid6w5/7Fn3c82EFti8PUc2qME3Xa/74abc336ae433344083479d28014696d/textlink.es.png)
+![textlink.es](https://images.ctfassets.net/alneenqid6w5/7Fn3c82EFti8PUc2qME3Xa/74abc336ae433344083479d28014696d/textlink.es.png)
 
 <div class="alert alert-info">
   <p>También puedes cambiar la URL de un producto utilizando la<a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview"> API del Catálogo</a>. En este caso, el campo a modificar es <code>LinkId</code>. Consulta el artículo<a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product"> Update product</a> para obtener más información.</p>
diff --git a/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md b/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md
index a7b27f1a6..bb5695a60 100644
--- a/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md
+++ b/docs/tutorials/es/how-to-deprecate-and-undeprecate-your-app.md
@@ -19,4 +19,4 @@ Si usted necesita realizar un rollback de su aplicación, ejecute el comando `vt
 
 Si percibe enseguida que será necesario deshacer el rollback, usted podrá realizar el comando `vtex undeprecate`.
 
-![image (2)](//images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
+![image (2)](https://images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
diff --git a/docs/tutorials/es/how-to-disable-a-transactional-email.md b/docs/tutorials/es/how-to-disable-a-transactional-email.md
index a1d71603a..9be7636f4 100644
--- a/docs/tutorials/es/how-to-disable-a-transactional-email.md
+++ b/docs/tutorials/es/how-to-disable-a-transactional-email.md
@@ -28,7 +28,7 @@ Se muestra a continuación:
 3. Busque __Payment Pending__ en el cuadro de búsqueda.
 4. Desactive la opción __"Activar envío de e-mail"__.
 
-  ![Message Center - Desativar - ES](//images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d000be57bdf906c957380992d497ddb6/dlSCQPRLKf46SnYGl7X9a_ES_Payment_Pending.jpg)
+  ![Message Center - Desativar - ES](https://images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/d000be57bdf906c957380992d497ddb6/dlSCQPRLKf46SnYGl7X9a_ES_Payment_Pending.jpg)
 
 5. Haga clic en __Guardar__.
 
diff --git a/docs/tutorials/es/how-to-download-the-vtex-invoices.md b/docs/tutorials/es/how-to-download-the-vtex-invoices.md
index c0afd3919..b8726923c 100644
--- a/docs/tutorials/es/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/es/how-to-download-the-vtex-invoices.md
@@ -46,7 +46,7 @@ Para descargar su factura, realice los siguientes pasos:
 
 Una vez hecho esto, su factura estará disponible en otra pestaña.
 
-![baixar faturas es](//images.ctfassets.net/alneenqid6w5/5sIBQUq8c2OKi0PHOb7qhs/8554b546c31d52e5f1a897a99c9341eb/baixar_faturas_es.gif)
+![baixar faturas es](https://images.ctfassets.net/alneenqid6w5/5sIBQUq8c2OKi0PHOb7qhs/8554b546c31d52e5f1a897a99c9341eb/baixar_faturas_es.gif)
 
 ## Brasil 
 
@@ -66,7 +66,7 @@ Para descargar su boleto, realice los siguientes pasos:
 
 <div class="alert alert-info">En Brasil, una factura púrpura puede indicar que está atrasada pero se ha generado un nuevo boleto para una fecha cercana. En este caso, la factura permanecerá atrasada hasta que se realice el pago. Si no se paga el nuevo boleto, la factura se pondrá en rojo.</div>
 
-![baixar boletos es](//images.ctfassets.net/alneenqid6w5/6JSRhGjBxWs4KDpVm9P5LL/57eb4cb973d27d600710cd8a91f7f4a6/baixar_boletos_es.gif)
+![baixar boletos es](https://images.ctfassets.net/alneenqid6w5/6JSRhGjBxWs4KDpVm9P5LL/57eb4cb973d27d600710cd8a91f7f4a6/baixar_boletos_es.gif)
 
 ### Descargar la Nota Fiscal
 
@@ -83,6 +83,6 @@ De esta forma, la Nota Fiscal se abrirá en otra pestaña de su navegador. Haga
 1. En Destino, seleccione la opción **Guardar en PDF**.
 2. Para finalizar, haga clic en **Guardar**.
 
-![baixar notafiscal es](//images.ctfassets.net/alneenqid6w5/y5FNSwSwYBOrMvX6mvHeO/c1f091d98df99caa716e3e2ad352b230/baixar_notafiscal_es.gif)
+![baixar notafiscal es](https://images.ctfassets.net/alneenqid6w5/y5FNSwSwYBOrMvX6mvHeO/c1f091d98df99caa716e3e2ad352b230/baixar_notafiscal_es.gif)
 
 Si tiene dudas sobre el valor de la factura, lea el artículo [comprenda el valor de los ingresos aprobados](https://help.vtex.com/es/tutorial/como-acessar-o-valor-da-receita-aprovada--tutorials_4322) para entender el valor que se cobró.
diff --git a/docs/tutorials/es/how-to-find-an-sku-id.md b/docs/tutorials/es/how-to-find-an-sku-id.md
index 844dd5d90..f1852f50b 100644
--- a/docs/tutorials/es/how-to-find-an-sku-id.md
+++ b/docs/tutorials/es/how-to-find-an-sku-id.md
@@ -34,7 +34,7 @@ Para descubrir el ID de un SKU por el Admin VTEX, siga estos pasos:
 
 En el ejemplo siguiente, el ID del SKU es __18__.
 
-![skuId-1](//images.contentful.com/alneenqid6w5/3CEFOn0h8Ac6ciGgi6gmEK/2d64944b8added0ec12d5cdc7ebe9d9c/skuId-1.png)
+![skuId-1](https://images.contentful.com/alneenqid6w5/3CEFOn0h8Ac6ciGgi6gmEK/2d64944b8added0ec12d5cdc7ebe9d9c/skuId-1.png)
 
 ## URL de registro de SKU
 
diff --git a/docs/tutorials/es/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md b/docs/tutorials/es/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
index 7c4224b7b..f6490cf16 100644
--- a/docs/tutorials/es/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
+++ b/docs/tutorials/es/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
@@ -23,18 +23,18 @@ De lo contrario, las páginas indexadas por Google con el contenido antiguo ser
 
 Usted necesitará acceder a su cuenta en el Web Master Tools de Google. Allí usted podrá verificar los números de páginas con errores.
 
-![locateURL1](//images.contentful.com/alneenqid6w5/qEYJuUx2hweIuuMCsQWmE/4667542aeafdfd92daecce10dd7853a6/locateURL1.jpg)
+![locateURL1](https://images.contentful.com/alneenqid6w5/qEYJuUx2hweIuuMCsQWmE/4667542aeafdfd92daecce10dd7853a6/locateURL1.jpg)
 
 
 Haga clic en **Rastreo** y luego en **Errores de Rastreos**, como en la imagen a continuación:
 
-![locateURL2](//images.contentful.com/alneenqid6w5/2bcdyY8KJqO6EwQOMKys8k/61845c81da0a9718bb46b9df40dff91c/locateURL2.jpg)
+![locateURL2](https://images.contentful.com/alneenqid6w5/2bcdyY8KJqO6EwQOMKys8k/61845c81da0a9718bb46b9df40dff91c/locateURL2.jpg)
 
 En esa área usted podrá visualizar cuándo ocurrió el error y con qué URL, y cuál es el error presentado. Y entonces podrá exportar una planilla (\*.csv)
 
-![locateURL3](//images.contentful.com/alneenqid6w5/5pmI5i6RFK4Icku40ua22S/43135af03b16a77ca55bdc3fb53207ea/locateURL3.jpg)
-![locateURL4](//images.contentful.com/alneenqid6w5/6QLDHdNJpCgWgAM6eO8QEi/8f5f07ce59f07c34cefa48b893767ac4/locateURL4.jpg)
+![locateURL3](https://images.contentful.com/alneenqid6w5/5pmI5i6RFK4Icku40ua22S/43135af03b16a77ca55bdc3fb53207ea/locateURL3.jpg)
+![locateURL4](https://images.contentful.com/alneenqid6w5/6QLDHdNJpCgWgAM6eO8QEi/8f5f07ce59f07c34cefa48b893767ac4/locateURL4.jpg)
 
 Usted podrá incluir esos links en la planilla, mencionando la Home, o la colección, lo que sea más adecuado a su tienda. Tras la corrección de esos links usted necesitará volver al Web Master Tools, hacer clic en **Rastreo** y luego en **Errores de Rastreos**.
 
-![locateURL5](//images.contentful.com/alneenqid6w5/54CtZsR9SM2Q8QSEoUaUmy/6a77ef45455da13bb84c8ce005ddaa29/locateURL5.jpg)
+![locateURL5](https://images.contentful.com/alneenqid6w5/54CtZsR9SM2Q8QSEoUaUmy/6a77ef45455da13bb84c8ce005ddaa29/locateURL5.jpg)
diff --git a/docs/tutorials/es/how-to-identify-a-page-template.md b/docs/tutorials/es/how-to-identify-a-page-template.md
index 0a2a68656..3b4e6b1c6 100644
--- a/docs/tutorials/es/how-to-identify-a-page-template.md
+++ b/docs/tutorials/es/how-to-identify-a-page-template.md
@@ -19,7 +19,7 @@ Esa duda es muy común entre los comerciantes VTEX. Como el CMS es un módulo an
 
 Antes es necesario explicar rápidamente la estructura del CMS Layout, que queda en `{AccountName}.myvtex.com/admin/a`
 
-![cms_newadmin ES](//images.ctfassets.net/alneenqid6w5/3t6uV7zLoAmIyYWSckwgOK/bbbad86f93506d49757da4aef80ce6d6/CMS__newadmin_ES.png)
+![cms_newadmin ES](https://images.ctfassets.net/alneenqid6w5/3t6uV7zLoAmIyYWSckwgOK/bbbad86f93506d49757da4aef80ce6d6/CMS__newadmin_ES.png)
 
 La principal función del CMS Layout es permitir la administración del layout de su tienda. En él se crearán los Directorios y Templates que darán vida a su e-commerce.
 
@@ -29,7 +29,7 @@ VTEX usa el mismo principio. El directorio (carpeta) es donde debe guardarse tod
 
 Podemos crear innúmeros templates pero debemos especificar en el directorio qué template se exhibirá. Usando la página de __Account__ como ejemplo:
 
-![cms-template-pagina ES](//images.ctfassets.net/alneenqid6w5/3AGqfnX5agco4McoGWOKIW/591aa19d419d552c23c9652cf87b8048/account_CMS_ES.png) 
+![cms-template-pagina ES](https://images.ctfassets.net/alneenqid6w5/3AGqfnX5agco4McoGWOKIW/591aa19d419d552c23c9652cf87b8048/account_CMS_ES.png) 
 
 Storefront > Layout > Carpeta CMS > Sites and channels > Account Nombre > Carpeta (/) > Account *(como en el ejemplo)* > Haga clic en el link que presente la flecha roja de "ok".
 
@@ -41,13 +41,13 @@ Para dar flexibilidad es posible aún incluir subtemplates e innúmeros otros re
 
 Ahora un ejemplo real. Quiero identificar qué página es ésta en la que estoy navegando:
 
-![pagina-loja ES](//images.ctfassets.net/alneenqid6w5/54CZB8Gt1CaY6W0MKG0u0S/df59e087977c87d972f78b4a689971ee/exemplo_loja_em_ES.png)
+![pagina-loja ES](https://images.ctfassets.net/alneenqid6w5/54CZB8Gt1CaY6W0MKG0u0S/df59e087977c87d972f78b4a689971ee/exemplo_loja_em_ES.png)
 
 El propio dominio muchas veces ya me ayuda a identificar, pero algunas tiendas pueden customizar esto, lo que puede dificultar el trabajo. En el caso, tengo duda sobre si es una página de __Departamento__ o __Categoría__, tal vez pueda incluso ser una customización de anaquel.
 
 El mejor camino es por el cotejo en el Código Fuente de la página (ctrl + U). Tiendas VTEX van a tener un indicativo de a qué directorio pertenece la página.
 
-![exemplo-codigo-template-loja ES](//images.ctfassets.net/alneenqid6w5/7ciwzN1BLOsg0KU46SaWQW/b7dd7f1a16cd6aedf0bb48dc74f45d40/exemplo_loja_em_espanhol_departamento.png)
+![exemplo-codigo-template-loja ES](https://images.ctfassets.net/alneenqid6w5/7ciwzN1BLOsg0KU46SaWQW/b7dd7f1a16cd6aedf0bb48dc74f45d40/exemplo_loja_em_espanhol_departamento.png)
 
 En el ejemplo anterior: `<!-- CommerceContext.Current.VirtualFolder.Name: @Departamento@ -->`
 Ahora que sabemos que es una página de categoría, necesitamos identificar qué template está activo para la Categoría. Para ello, basta repetir el proceso aplicado en el ejemplo anterior.
diff --git a/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md b/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md
index 67ccd9c7b..4be171335 100644
--- a/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md
+++ b/docs/tutorials/es/how-to-identify-layout-errors-caused-by-javascript-files.md
@@ -25,7 +25,7 @@ Para eso, siga los siguientes pasos:
 
 1. Para deshabilitar el JavaScript de la página basta colocar el `/tools.html` al final de la URL. Ej: {AccountName}.myvtex.com/tools.html
 2. Haga clic en __Disable__ en la pestaña __Client JavaScript is__.
-![javascript-disable ](//images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
+![javascript-disable ](https://images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png)
 
 3. Después retirar el `/tools.html` da URL y actualizar la página.
 
diff --git a/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
index 06ac35e0b..7aa59d8d9 100644
--- a/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
@@ -40,7 +40,7 @@ En el carrito, puedes pasar el mouse sobre el ícono de interrogación que está
 
 Sin embargo, si se aplicó más de una promoción, aparecerá solo la sumatoria de todos los descuentos, lo cual dificultará el análisis del escenario.
 
-![example-cart](//images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/8d5f5572c67f308480e9e4b1f65dc9e7/image6.png)
+![example-cart](https://images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/8d5f5572c67f308480e9e4b1f65dc9e7/image6.png)
 
 ## orderForm
 
@@ -56,7 +56,7 @@ Sigue estos pasos para encontrar el `orderForm` e identificar las promociones ap
 2. Haz clic en `Network`.
 3. Selecciona la opción **Mantener registro**.
 4. Actualiza la página.
-5. Una vez que cargue, presiona `Ctrl+F` para hacer una búsqueda en la ventana **Herramientas de desarrollador**. Escribe `orderForm` en la barra de búsqueda. ![order-form](//images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
+5. Una vez que cargue, presiona `Ctrl+F` para hacer una búsqueda en la ventana **Herramientas de desarrollador**. Escribe `orderForm` en la barra de búsqueda. ![order-form](https://images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
 6. Haz clic sobre la línea de `orderForm`. Se abrirá una nueva ventana al costado.
 7. Haz clic en `Preview (Previsualizar)`.
 8. Busca `ratesAndBenefitsData` y haz clic en el ítem.
diff --git a/docs/tutorials/es/how-to-identify-promotions-attributed-to-an-sku.md b/docs/tutorials/es/how-to-identify-promotions-attributed-to-an-sku.md
index a7569f999..8e3e3fb2f 100644
--- a/docs/tutorials/es/how-to-identify-promotions-attributed-to-an-sku.md
+++ b/docs/tutorials/es/how-to-identify-promotions-attributed-to-an-sku.md
@@ -24,12 +24,12 @@ Hemos escrito este artículo para responder a una pregunta recurrente de los usu
 Para descubrir qué promociones están siendo asignadas a un SKU, hay que analizar sus `priceTags`.
 
 1. Acceder al carrito con el producto.
-2. En Google Chrome, acceder a las **Herramientas de Desarolladores** (`Ctrl+Shift+I`).![ferramentas-do-desenvolvedor](//images.contentful.com/alneenqid6w5/3NBGEPjXEkkSqA2WOYs8us/5219ffe6515a120ac0e6d489c78e5820/ferramentas-do-desenvolvedor.png)
-3. Seleccione **Network** y presione `F5` para registrar la carga de la página.![network-f5](//images.contentful.com/alneenqid6w5/1TZRay17qkEO8As8w0MKOS/f4d88d06f2a3fd656aa41e3809f35d45/network-f5.png)
-4. Después de la carga, presione `Ctrl+F` para hacer búsqueda en la ventana de Herramientas de Desarolladores y busque por `orderForm`.![order-form](//images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
-5. Hacer click en `orderForm` y ir a `items`. Después de hacer click en `items`, hacer click en los números (0, 1, 2 etc.) para ver las características del producto deseado. En nuestro ejemplo, ya que tenemos sólo un elemento, este se representa por el número `0` en el array.![items-0](//images.contentful.com/alneenqid6w5/DUtSiCdnrwSmoKqqYW8E6/ec7335a0c9308b17b9d8aa2274057220/items-0.png)
-6. Después de hacer click en el número, hacia abajo el scroll hasta `priceTags`. Haga click en `priceTags` y luego haga click en los números (`0`, `1`, `2` etc.) para ver las características de la promocion deseada. En nuestro ejemplo, ya que tenemos solamente una promoción, esta se representa por el número `0` en el array. Después de eso, búsqueda por `identifier` de la promoción.![priceTags-0-identifier](//images.contentful.com/alneenqid6w5/5MCOrSJPaMSYQcimY8CKos/ca8960a1a98f680406daf7879d241987/priceTags-0-identifier.png)
-7. En otra pestaña, acceder a la URL `https://{accountName}.vtexcommercestable.com.br/admin/rnb/#/benefit/{numero-del-identifier}`. Esta es la promoción que se aplica efectivamente al producto en el carrito. Comprueba la configuración de la promoción y vea si las condiciones son aplicables al SKU en cuestión.![promo-debug-help](//images.contentful.com/alneenqid6w5/5G2eJ4AilySK0o8ugaOMq4/b4dba231e9812906a45af5a4432d9783/promo-debug-help.png)
+2. En Google Chrome, acceder a las **Herramientas de Desarolladores** (`Ctrl+Shift+I`).![ferramentas-do-desenvolvedor](https://images.contentful.com/alneenqid6w5/3NBGEPjXEkkSqA2WOYs8us/5219ffe6515a120ac0e6d489c78e5820/ferramentas-do-desenvolvedor.png)
+3. Seleccione **Network** y presione `F5` para registrar la carga de la página.![network-f5](https://images.contentful.com/alneenqid6w5/1TZRay17qkEO8As8w0MKOS/f4d88d06f2a3fd656aa41e3809f35d45/network-f5.png)
+4. Después de la carga, presione `Ctrl+F` para hacer búsqueda en la ventana de Herramientas de Desarolladores y busque por `orderForm`.![order-form](https://images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
+5. Hacer click en `orderForm` y ir a `items`. Después de hacer click en `items`, hacer click en los números (0, 1, 2 etc.) para ver las características del producto deseado. En nuestro ejemplo, ya que tenemos sólo un elemento, este se representa por el número `0` en el array.![items-0](https://images.contentful.com/alneenqid6w5/DUtSiCdnrwSmoKqqYW8E6/ec7335a0c9308b17b9d8aa2274057220/items-0.png)
+6. Después de hacer click en el número, hacia abajo el scroll hasta `priceTags`. Haga click en `priceTags` y luego haga click en los números (`0`, `1`, `2` etc.) para ver las características de la promocion deseada. En nuestro ejemplo, ya que tenemos solamente una promoción, esta se representa por el número `0` en el array. Después de eso, búsqueda por `identifier` de la promoción.![priceTags-0-identifier](https://images.contentful.com/alneenqid6w5/5MCOrSJPaMSYQcimY8CKos/ca8960a1a98f680406daf7879d241987/priceTags-0-identifier.png)
+7. En otra pestaña, acceder a la URL `https://{accountName}.vtexcommercestable.com.br/admin/rnb/#/benefit/{numero-del-identifier}`. Esta es la promoción que se aplica efectivamente al producto en el carrito. Comprueba la configuración de la promoción y vea si las condiciones son aplicables al SKU en cuestión.![promo-debug-help](https://images.contentful.com/alneenqid6w5/5G2eJ4AilySK0o8ugaOMq4/b4dba231e9812906a45af5a4432d9783/promo-debug-help.png)
 
 ## Más información
 
diff --git a/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
index 2278cb786..4b345dc27 100644
--- a/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
@@ -17,7 +17,7 @@ subcategory: 1c5Btie9ou2Gg2iUo0ggqM
 
 Los puntos de recogida, también conocidos como pickup points, son parte importante de cualquier estrategia [omnichannel](/es/announcement/cambie-su-negocio-con-la-experiencia-omnichannel-vtex).
 
-Puede [configurar puntos de recogida uno a uno](/es/tutorial/configurar-puntos-de-recogida-pickup-points) o hacer esto mediante la importación de una planilla XLS [(como la de este ejemplo)](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Usando un archivo XLS, usted registra todos los pickup points de una sola vez (siempre que no supere los 10 MB).
+Puede [configurar puntos de recogida uno a uno](/es/tutorial/configurar-puntos-de-recogida-pickup-points) o hacer esto mediante la importación de una planilla XLS [(como la de este ejemplo)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Usando un archivo XLS, usted registra todos los pickup points de una sola vez (siempre que no supere los 10 MB).
 
 <div class="alert alert-info">
 Un archivo XLS de <strong>10 MB</strong> permite el registro de, aproximadamente, <strong>50 mil</strong> puntos de recogida. Para importar un número mayor, es necesario dividirlos en más de una planilla y hacer un upload a la vez.
@@ -28,8 +28,8 @@ Un archivo XLS de <strong>10 MB</strong> permite el registro de, aproximadamente
 ## Cómo subir la planilla
 1. En el menú lateral, haga clic en __Inventario y envío__, en la sección __Pedidos__.
 2. En las opciones que se abren, haga clic en __Puntos de recogida__.
-3. Haga clic en __Subir un XLS__, en la esquina superior derecha de la página. ![Subir XLS (ES)](//images.ctfassets.net/alneenqid6w5/33W20ReDnWc4U4gIgeaOUW/b2eada442c781b9b21397aeb60deb127/Subir_XLS__ES_.png)
-4. Un modal va a surgir, permitiendo que usted envíe su archivo (con extensión `.xls`) o baje la [planilla de ejemplo](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Recuerde que esta planilla viene con valores de ejemplo rellenados, que deben ser borrados y reemplazados por los datos de sus propios puntos de recogida. ![modal (ES)](//images.ctfassets.net/alneenqid6w5/2CxrD2w27CYIAwqYGwUEqu/ca5cebd0c3c7bc457f4f93fbee98178d/modal__ES_.png)
+3. Haga clic en __Subir un XLS__, en la esquina superior derecha de la página. ![Subir XLS (ES)](https://images.ctfassets.net/alneenqid6w5/33W20ReDnWc4U4gIgeaOUW/b2eada442c781b9b21397aeb60deb127/Subir_XLS__ES_.png)
+4. Un modal va a surgir, permitiendo que usted envíe su archivo (con extensión `.xls`) o baje la [planilla de ejemplo](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Recuerde que esta planilla viene con valores de ejemplo rellenados, que deben ser borrados y reemplazados por los datos de sus propios puntos de recogida. ![modal (ES)](https://images.ctfassets.net/alneenqid6w5/2CxrD2w27CYIAwqYGwUEqu/ca5cebd0c3c7bc457f4f93fbee98178d/modal__ES_.png)
 5. Con todo hecho correctamente, los nuevos puntos de recogida estarán configurados y disponibles para sus clientes.
 
 
diff --git a/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
index 723d45f9b..c0b0b315c 100644
--- a/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -27,30 +27,30 @@ Realizadas las debidas definiciones, se hace el vínculo de la colección con la
 
 En el ejemplo abajo, vamos a definir la vitrina presentada en la Home. Por lo tanto, seleccione **Settings**, luego **add object**, como en la siguiente imagen.
 
-![coleção2](//images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
+![coleção2](https://images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
 
 Este comando abrirá **Visual Controls**, que corresponden al escaparate en el que desea mostrar la colección. Agregue una _Collection_, pero asegúrese de establecer un nombre para ella.
 
-![coleção3](//images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
+![coleção3](https://images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
 
-![coleção4](//images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
+![coleção4](https://images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
 
 Acuérdese de grabar las configuraciones para que sea posible editar el control creado!
 
-![coleção5](//images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
+![coleção5](https://images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
 
-![coleção6](//images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
+![coleção6](https://images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
 
 Al editar el control es necesario agregar sus contenidos, que representan cada conjunto de ítems que se exhibirán.
 Son ellos:
 _Layout_: seleccione la plantilla de estante utilizada en la muestra.
 _Number of Columns, Number of Items, Show Unavailable_ y _Ramdom ad Paged_: Defina el diseño, la cantidad y los criterios para mostrar los elementos.
 
-![coleção7](//images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
+![coleção7](https://images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
 
 Recuerde guardar antes de buscar o cambiar páginas.
 El siguiente paso es agregar el contenido seleccionando **Add Content**.
-![coleção8](//images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
+![coleção8](https://images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
 
 Es posible definir cada contenido usando colecciones o resultados de búsqueda, usando parámetros de búsqueda (más detalles [aquí](/es/tutorial/parametros-de-busqueda "aquí"))
 
@@ -60,7 +60,7 @@ _QueryString_: los parámetros ingresados en este campo definen el resultado de
 
 En el campo **Product Cluster (Collection)**, debe seleccionar la colección que se mostrará completando el siguiente paso:
 
-![coleção10](//images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
+![coleção10](https://images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
 
 Los contenidos a rellenar en la parte **Condición de visualización**:
 _Partner, Campaign_ y _Source_: definen la visualización de este contenido si el visitante tiene un UTM correspondiente en su URL de origen.
@@ -72,7 +72,7 @@ Después de la configuración, marque **Active Content** y agregue a la lista de
 
 En el ejemplo abajo tenemos una vitrina estándar, sin condiciones de exhibición y otra exclusiva para las visitas originadas de las audiencias de campañas patrocinadas de Google (utm_source=**google**/utm_medium=**cpc**):
 
-![coleção9](//images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)![](//images.contentful.com/alneenqid6w5/28YV17bwwUyca6YyMo2Ckk/6d3d464c50b000d4a88c4132881d6236/exemplo_cpc-560x269.png)
+![coleção9](https://images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)![](https://images.contentful.com/alneenqid6w5/28YV17bwwUyca6YyMo2Ckk/6d3d464c50b000d4a88c4132881d6236/exemplo_cpc-560x269.png)
 
 En el escenario arriba, si el cliente tiene origen en la audiencia de campaña patrocinada se exhibirán en la vitrina **Lançamentos**, ubicada en la Home, los productos que corresponden al resultado de una búsqueda por la Marca de ID 200000, en caso contrario, se exhibirán los productos de la colección de ID 8.
 
diff --git a/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md b/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
index bf8adafd5..c40c4847d 100644
--- a/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
+++ b/docs/tutorials/es/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
@@ -18,7 +18,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 Para incluir metadatos al exportar una plantilla de precios de SKUs, siga los siguientes pasos:
 
 1. Haga clic en **Precios** en el menú de la izquierda de la página 
-![ESRefID 1.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/5VDIMnTlKtroiaZQtAwEsK/b9c0339593c7769260b2e57892e41d7c/ESRefID_1.png_h_250_h_250)
+![ESRefID 1.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/5VDIMnTlKtroiaZQtAwEsK/b9c0339593c7769260b2e57892e41d7c/ESRefID_1.png_h_250_h_250)
 
 2. Haga clic en **lista de precios** 
 
@@ -29,6 +29,6 @@ Para incluir metadatos al exportar una plantilla de precios de SKUs, siga los si
 5. Haga clic en **incluir metadados en las tablas exportadas**
 
 6. Haga clic en el botón **Exportar tabla**
-![ESRefID 2.png?h=250](//images.ctfassets.net/alneenqid6w5/Yk3jKU2ZaUuZGoKkNjMhb/2cb1f11e7f8b26a401f77f3aa2d238a2/ESRefID_2.png_h_250)
+![ESRefID 2.png?h=250](https://images.ctfassets.net/alneenqid6w5/Yk3jKU2ZaUuZGoKkNjMhb/2cb1f11e7f8b26a401f77f3aa2d238a2/ESRefID_2.png_h_250)
 
 En algunos minutos usted recibirá un e-mail con la tabla exportada.
diff --git a/docs/tutorials/es/how-to-install-the-masterpass-in-the-vtex-app-store.md b/docs/tutorials/es/how-to-install-the-masterpass-in-the-vtex-app-store.md
index 5c5eea6bf..20c5f6ce1 100644
--- a/docs/tutorials/es/how-to-install-the-masterpass-in-the-vtex-app-store.md
+++ b/docs/tutorials/es/how-to-install-the-masterpass-in-the-vtex-app-store.md
@@ -23,7 +23,7 @@ Este artículo tiene el objetivo de mostrar el paso a paso para instalación de
 
 En primer lugar, en la pantalla **Explorar**, haga clic en la extensión **Masterpass**.
 
-![Extension Store 1](//images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
+![Extension Store 1](https://images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
 
 Usted tendrá, entonces, acceso a la página de detalles de la extensión, en la que se muestra la siguiente información:
 
@@ -38,17 +38,17 @@ Para instalar el Masterpass, basta hacer clic en el botón verde a la derecha de
 
 El botón de instalación lleva a la pantalla de permisiones, donde es posible visualizar los datos y lugares a los que la extensión desea tener acceso.
 
-![Masterpass1](//images.contentful.com/alneenqid6w5/qxOKuZ9dZY2Gy8osWg26A/f553a03370fb198e8dd38d95bd20bb35/Masterpass1.gif)
+![Masterpass1](https://images.contentful.com/alneenqid6w5/qxOKuZ9dZY2Gy8osWg26A/f553a03370fb198e8dd38d95bd20bb35/Masterpass1.gif)
 
 Una vez que usted acepte las permisiones, la extensión será instalada.
 
-![Masterpass2](//images.contentful.com/alneenqid6w5/4rxdPuNq0oO2QuCiMaISAy/e8cca1acea0db1e87a0573b8c23f2013/Masterpass2.png)
+![Masterpass2](https://images.contentful.com/alneenqid6w5/4rxdPuNq0oO2QuCiMaISAy/e8cca1acea0db1e87a0573b8c23f2013/Masterpass2.png)
 
 ## Configuración
 
 Para funcionar correctamente, usted necesita cumplir una etapa de configuración. Basta llenar algunos campos, como los mostrados en la imagen a continuación, y hacer clic en **Crear cuenta**.
 
-![Masterpass3](//images.contentful.com/alneenqid6w5/5XbYGeSd2gy4QEaIiMeqQ0/a20d27e9aa18af9a95767fb604e82d7c/Masterpass3.png)
+![Masterpass3](https://images.contentful.com/alneenqid6w5/5XbYGeSd2gy4QEaIiMeqQ0/a20d27e9aa18af9a95767fb604e82d7c/Masterpass3.png)
 
 ## Preview
 
@@ -58,7 +58,7 @@ Además, la Extension Store pone a disposición un ambiente de preview del Maste
 
 Este ambiente funciona como un borrador. Ninguna modificación hecha en él afecta su tienda en producción.
 
-![Masterpass4](//images.contentful.com/alneenqid6w5/7Ki5CoHPvUusGuU4UEE2U4/7d8d02434118b7c3b6c295edc9efbb18/Masterpass4.gif)
+![Masterpass4](https://images.contentful.com/alneenqid6w5/7Ki5CoHPvUusGuU4UEE2U4/7d8d02434118b7c3b6c295edc9efbb18/Masterpass4.gif)
 
 ## Publicación
 
@@ -66,4 +66,4 @@ Para desplazar el Masterpass hacia el ambiente en producción (donde sus cliente
 
 Para isso, basta hacer clic en el botón **Publicar** de la top bar.
 
-![Extension Store 3 - Publishing](//images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
+![Extension Store 3 - Publishing](https://images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
diff --git a/docs/tutorials/es/how-to-install-the-taxhub.md b/docs/tutorials/es/how-to-install-the-taxhub.md
index 9f02f91b2..f1f8da5ce 100644
--- a/docs/tutorials/es/how-to-install-the-taxhub.md
+++ b/docs/tutorials/es/how-to-install-the-taxhub.md
@@ -25,4 +25,4 @@ Para instalar el sistema de impuesto TaxHub, siga los pasos abajo:
 6.	En la misma pantalla instale su App desarrollada en node.js comprimido en formato .zip (el nombre del archivo debe ser jurisdiction.zip);
 7.	El sistema guardara el archivo automáticamente.
  
-![TaxHub Instalation](//images.contentful.com/alneenqid6w5/7LfwQ6CzIIEYqSwmcoUMCG/7508ba6496d5fedb913c85357a8a632e/Instalacion_TaxHub.gif)
+![TaxHub Instalation](https://images.contentful.com/alneenqid6w5/7LfwQ6CzIIEYqSwmcoUMCG/7508ba6496d5fedb913c85357a8a632e/Instalacion_TaxHub.gif)
diff --git a/docs/tutorials/es/how-to-integrate-with-dafiti.md b/docs/tutorials/es/how-to-integrate-with-dafiti.md
index da6ff4dd9..fa71fbd2d 100644
--- a/docs/tutorials/es/how-to-integrate-with-dafiti.md
+++ b/docs/tutorials/es/how-to-integrate-with-dafiti.md
@@ -53,11 +53,11 @@ Con esta *feature*, será posible categorizar correctamente y también crear var
 El mapeo debe realizarse siempre que un producto se envíe por primera vez a Dafiti. Esto significa que, ya habiendo hecho el mapeo una vez, los productos que ya fueron integrados no necesitará rehacer el mapeo. Y también que, los nuevos productos siempre deben hacer el mapeo.
 
 1. De acuerdo con __su país__, descargue abajo la __Planilla de Mapeo de Dafiti__ en el formato `.xlsx`.
-<br/>&bull; [Brasil](//assets.ctfassets.net/alneenqid6w5/2Vbi7VaYIowaaOYCCucsQq/fa94cd636b38e9810dd6a708c95e26ac/Planilha_de_Mapeamento_da_Dafiti.xlsx))
-<br/>&bull; [Colombia](//assets.ctfassets.net/alneenqid6w5/4d5y0N09IsKmy4MuAGygqs/0e43349d309fb556179dfac5f2f6c885/Planilha_de_Mapeamento_da_Dafiti_COL.xlsx)
+<br/>&bull; [Brasil](https://assets.ctfassets.net/alneenqid6w5/2Vbi7VaYIowaaOYCCucsQq/fa94cd636b38e9810dd6a708c95e26ac/Planilha_de_Mapeamento_da_Dafiti.xlsx))
+<br/>&bull; [Colombia](https://assets.ctfassets.net/alneenqid6w5/4d5y0N09IsKmy4MuAGygqs/0e43349d309fb556179dfac5f2f6c885/Planilha_de_Mapeamento_da_Dafiti_COL.xlsx)
 
 2. De acuerdo con __su país__, descargue abajo la __Planilla de Consulta de Dafiti__ para verificar los valores aceptados de acuerdo con cada columna de la Planilla de Mapeo del paso anterior. Esta hoja de trabajo se utilizará exclusivamente como __consulta__.
-<br/>&bull; [Brasil](//assets.ctfassets.net/alneenqid6w5/1gGYn5lo3qSe0iOaoKs0oa/fc1aa02e2761474f0235fcb489f930ff/Planilha_de_Consulta_Dafiti.xlsx)
+<br/>&bull; [Brasil](https://assets.ctfassets.net/alneenqid6w5/1gGYn5lo3qSe0iOaoKs0oa/fc1aa02e2761474f0235fcb489f930ff/Planilha_de_Consulta_Dafiti.xlsx)
 <br/>&bull; [Colombia](https://s3.amazonaws.com/Marketplace-Integration/SellerCenterIntegration/Colombia.zip)
 
 Siga el paso a paso siguiente, haciendo el de/para en la __Planilla de Mapeo__ entre el que está registrado en su producto en VTEX y los valores especificados de acuerdo con la __Planilla de Consulta__ de Dafiti.
diff --git a/docs/tutorials/es/how-to-manage-subscriptions.md b/docs/tutorials/es/how-to-manage-subscriptions.md
index 762c20abc..3586902c0 100644
--- a/docs/tutorials/es/how-to-manage-subscriptions.md
+++ b/docs/tutorials/es/how-to-manage-subscriptions.md
@@ -35,7 +35,7 @@ La sección de **Suscripciones Únicas** permite:
 - Visualizar un **gráfico dinámico** con la relación entre las *suscripciones activas*, *canceladas*, y *total de suscripciones*, dentro del período filtrado. - Al pasar el cursor sobre las líneas del gráfico, se puede ver en detalle el movimiento de las suscripciones por día.   
 - **Exportar suscripciones**  únicas dentro del período filtrado pulsando el botón de la esquina superior derecha de la pantalla.
 
-![ES Dashboard Assinatura única](//images.ctfassets.net/alneenqid6w5/3BEDDrOsEARRJ1XfuwABDd/ecc8168966e3379654269a2d47b405c0/ES_Dashboard_Assinatura___nica.png)
+![ES Dashboard Assinatura única](https://images.ctfassets.net/alneenqid6w5/3BEDDrOsEARRJ1XfuwABDd/ecc8168966e3379654269a2d47b405c0/ES_Dashboard_Assinatura___nica.png)
 
 ### Pedidos de Suscripción
 
@@ -49,12 +49,12 @@ La sección **Pedidos de Suscripción** permite:
 - Acompañe el **número absoluto y porcentaje** correspondiente de Pedidos de Suscripción que han sido *programados*, *procesados*, *generados* y *completados* por período.  
 - Visualizar un **gráfico** con el porcentaje de pedidos *omitidos*, *ciclos con problemas* y *error de pago*. 
 
-![ES Dashboard Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/7s8Mp2U4qAUAxpiTQbJGy6/c24aea7486e45591e83591e452535db9/ES_Dashboard_Pedidos_Assinatura.png)
+![ES Dashboard Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/7s8Mp2U4qAUAxpiTQbJGy6/c24aea7486e45591e83591e452535db9/ES_Dashboard_Pedidos_Assinatura.png)
 
 - Al acceder a cada pestaña de la sección **Pedidos de Suscripción**, es posible visualizar el flujo y los detalles de los pedidos que fueron *omitidos*, los que presentaron *ciclos problemáticos*, aquellos que contienen un *error de pago* y  pedidos *completos*.  
 - Además de listar detalles de los errores que se produjeron durante el flujo de pedidos de suscripción, también es posible realizar el **reintento manual** de los pedidos con errores. Revise nuestro artículo sobre la [Resolución de problemas de  pedidos con suscripción](https://help.vtex.com/es/tutorial/como-solucionar-pedidos-de-assinatura-com-erros--uLL8AYBGdtAmbbdL5gRCf) para saber más. 
 
-![pedidos_assinaturas_print_es](//images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
+![pedidos_assinaturas_print_es](https://images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
 
 ### Suscriptores
 
diff --git a/docs/tutorials/es/how-to-manage-the-kit-stock.md b/docs/tutorials/es/how-to-manage-the-kit-stock.md
index 0fa7ce14b..5e307836d 100644
--- a/docs/tutorials/es/how-to-manage-the-kit-stock.md
+++ b/docs/tutorials/es/how-to-manage-the-kit-stock.md
@@ -27,7 +27,7 @@ El kit con componentes se fundamenta en un Producto kit que posee un SKU que es
 
 Por ejemplo, un producto Kit Colorido se compone por otros diez SKUs. Cada uno con su precio y la cantidad necesaria de 1 ítem de cada SKU para que se pueda componer el Kit:
 
-![](//images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
+![](https://images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
 
 En este tipo de kit, el precio y el Inventario del kit en sí es la suma de estos valores de sus respectivos componentes. Esto es, no se actualiza directamente el SKU del kit, pero sus respectivos componentes.
 
diff --git a/docs/tutorials/es/how-to-manually-invoice-an-order.md b/docs/tutorials/es/how-to-manually-invoice-an-order.md
index 22d740271..fa1ae2c1d 100644
--- a/docs/tutorials/es/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/es/how-to-manually-invoice-an-order.md
@@ -34,7 +34,7 @@ Para enviar una factura a través del Admin VTEX, siga los pasos a continuación
 2. Busca el pedido en la barra de búsqueda o [usa los filtros](https://help.vtex.com/es/tutorial/como-filtrar-pedidos--tutorials_192).  
 3. Haz clic en el pedido deseado.
 4. Desplázate hacia abajo hasta la sección **Ítems a facturar** y haz clic en<i class = "fas fa-chevron-right"> </i> para ampliar.   
-![FaturaES](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)  
+![FaturaES](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)  
 5. Haz clic en el botón `Facturar`. 
 6. Haz clic en la opción de facturación deseada:    
     * **Enviar factura con referencia a los ítems:** para facturar el pedido haciendo referencia a los ítems del paquete.
@@ -64,7 +64,7 @@ Para enviar una factura a través del Admin VTEX, siga los pasos a continuación
 
 Una vez `facturado` el pedido, comprueba las facturas introducidas en la sección **Factura** como se muestra en la figura siguiente.
 
-![Itens faturarES](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
+![Itens faturarES](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
 
 En los casos de envío de [facturas parciales](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe), al [modificar o eliminar ítems de un pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190), el valor total del pedido se actualizará después de la facturación, y corresponderá al valor capturado por el _gateway_ de pagos de VTEX.
 
diff --git a/docs/tutorials/es/how-to-register-a-store-in-vtex-instore.md b/docs/tutorials/es/how-to-register-a-store-in-vtex-instore.md
index 364f9d5db..b50b42e50 100644
--- a/docs/tutorials/es/how-to-register-a-store-in-vtex-instore.md
+++ b/docs/tutorials/es/how-to-register-a-store-in-vtex-instore.md
@@ -30,7 +30,7 @@ Este guía le ayudará a usted a personalizar la configuración de su tienda par
 
 Al abrirse la aplicación por primera vez, ella pregunta cuál es el nombre de la tienda que será usada. Conforme a la pantalla a continuación, basta digitar el nombre de su tienda para tener cargadas para el app las configuraciónes.
 
-![instore-identificacao-loja](//images.contentful.com/alneenqid6w5/20IMJOo5Kc8Kw4OqicCQyc/8a76ed7d6c16d6b269518d430998ec44/instore-identificacao-loja.png)
+![instore-identificacao-loja](https://images.contentful.com/alneenqid6w5/20IMJOo5Kc8Kw4OqicCQyc/8a76ed7d6c16d6b269518d430998ec44/instore-identificacao-loja.png)
 
 ### Cómo registrar una tienda física
 
@@ -40,14 +40,14 @@ Para gestionar su registro de tiendas físicas basta acceder a su Masterdata. Cu
 
 *Si usted no encuentra esa aplicación, significa que su ambiento no fue todavía correctamente configurado. Para tanto, recomendamos el tutorial de configuración de ambiente para uso del inStore.*
 
-![masterdata-home-loja](//images.contentful.com/alneenqid6w5/2uBujqshwgCUkKkeEKWaEU/121417a9d25e998c8bb7a29f85ab1830/masterdata-home-loja.png)
+![masterdata-home-loja](https://images.contentful.com/alneenqid6w5/2uBujqshwgCUkKkeEKWaEU/121417a9d25e998c8bb7a29f85ab1830/masterdata-home-loja.png)
 
 Cuando usted haga clic en listar, va a aparecer una lista de tiendas registradas, como muestra la imagen a continuación. Haga clic en "Nuevo" para registrar una nueva tienda.
 
-![cadastrar-loja](//images.contentful.com/alneenqid6w5/2UxKo2u6CsEagsIYuo8Emy/8c922392c6f0b9373f497575af2cefaf/cadastrar-loja.png)
+![cadastrar-loja](https://images.contentful.com/alneenqid6w5/2UxKo2u6CsEagsIYuo8Emy/8c922392c6f0b9373f497575af2cefaf/cadastrar-loja.png)
 
 Rellene los datos de la tienda en el formulario y después haga clic en "salvar".
 
-![cadastrar-loja-formulario](//images.contentful.com/alneenqid6w5/3t3edGHxuo8WoYqkeYmIou/98d23008f916793e6cab618e33905dc2/cadastrar-loja-formulario.png)
+![cadastrar-loja-formulario](https://images.contentful.com/alneenqid6w5/3t3edGHxuo8WoYqkeYmIou/98d23008f916793e6cab618e33905dc2/cadastrar-loja-formulario.png)
 
 Ya está. ¡Su tienda está registrada! 😃 ¡Ahora usted puede continuar registrando a los vendedores! Vea [aquí](/es/tutorial/como-registrar-vendedores-en-el-vtex-instore) cómo hacerlo.
diff --git a/docs/tutorials/es/how-to-request-receivables-anticipation.md b/docs/tutorials/es/how-to-request-receivables-anticipation.md
index 9addc8edf..7fcf4ce0d 100644
--- a/docs/tutorials/es/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/es/how-to-request-receivables-anticipation.md
@@ -31,7 +31,7 @@ Ahora que ha verificado el saldo, es importante tener en cuenta que el valor mí
 
 Por ejemplo, si el menor valor que puede recibir es R$10, ese es el valor mínimo que puede anticipar. El valor máximo se informa en el propio Admin - el saldo que usted acaba de verificar - en la página "Anticipar cuentas por cobrar". 
 
-![antecipação](//images.ctfassets.net/alneenqid6w5/2DQKbFjERNOa8wLmFq3nr9/ae2cced48c5774ced4415db9ab9756b6/image.png_h_250_h_250)
+![antecipação](https://images.ctfassets.net/alneenqid6w5/2DQKbFjERNOa8wLmFq3nr9/ae2cced48c5774ced4415db9ab9756b6/image.png_h_250_h_250)
 
 <div class="alert alert-info">
 <strong>Atención</strong>: las cuentas por cobrar en disputa o programadas para el siguiente día hábil no pueden ser anticipadas.
diff --git a/docs/tutorials/es/how-to-retrieve-the-access-password.md b/docs/tutorials/es/how-to-retrieve-the-access-password.md
index 12eba5feb..efaf85536 100644
--- a/docs/tutorials/es/how-to-retrieve-the-access-password.md
+++ b/docs/tutorials/es/how-to-retrieve-the-access-password.md
@@ -17,12 +17,12 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 Todas las contraseñas son gestionadas por __VTEX ID__. Por lo tanto, se debe acceder a la página de login y seguir con el acceso por mail y contraseña para solicitar la creación de una nueva.
 
-1. En alguna pantalla de login, haga clic en **Ingresar con mail y contraseña;**![vtexid-es](//images.contentful.com/alneenqid6w5/2FPNwTHlCMoYueuuIGqkIu/391902bfdf5b805ba186e920adedf7f0/vtexid-es.png)
-2. Haga clic en **Olvidé mi contraseña;**![olvidé-mi-contrasena](//images.contentful.com/alneenqid6w5/4JL4D8b6kEYQ0MUmq0qemO/2cbb829575dd2064eefdc1b42964083f/olvid_C3_A9-mi-contrasena.png)
-3. Complete el campo con su mail;![mail-vtex-id](//images.contentful.com/alneenqid6w5/5V4YYXbZQWQUgGqyACGaso/fbd55b4ff6b5107beca6dbbba0c8f418/mail-vtex-id.png)
-4. Complete el campo con la nueva contraseña  y haga clic en **Registrar una nueva contraseña;**![registrar-una-nueva-contrasena](//images.contentful.com/alneenqid6w5/4pTzjoqENO4smcG0wQOIOM/d5c7d719d8303ee755398e49cde52307/registrar-una-nueva-contrasena.png)
+1. En alguna pantalla de login, haga clic en **Ingresar con mail y contraseña;**![vtexid-es](https://images.contentful.com/alneenqid6w5/2FPNwTHlCMoYueuuIGqkIu/391902bfdf5b805ba186e920adedf7f0/vtexid-es.png)
+2. Haga clic en **Olvidé mi contraseña;**![olvidé-mi-contrasena](https://images.contentful.com/alneenqid6w5/4JL4D8b6kEYQ0MUmq0qemO/2cbb829575dd2064eefdc1b42964083f/olvid_C3_A9-mi-contrasena.png)
+3. Complete el campo con su mail;![mail-vtex-id](https://images.contentful.com/alneenqid6w5/5V4YYXbZQWQUgGqyACGaso/fbd55b4ff6b5107beca6dbbba0c8f418/mail-vtex-id.png)
+4. Complete el campo con la nueva contraseña  y haga clic en **Registrar una nueva contraseña;**![registrar-una-nueva-contrasena](https://images.contentful.com/alneenqid6w5/4pTzjoqENO4smcG0wQOIOM/d5c7d719d8303ee755398e49cde52307/registrar-una-nueva-contrasena.png)
 5. Espere el código de acceso será enviado por mail;
 6. Pegarlo en el campo solicitado;
-7. Haga  clic en **Cambiar contraseña**.![cambiar-contrasena](//images.contentful.com/alneenqid6w5/4UWg3SW3HaqcScM6g2ACQy/637c416291ed89e6c070108f183e7b40/cambiar-contrasena.png)
+7. Haga  clic en **Cambiar contraseña**.![cambiar-contrasena](https://images.contentful.com/alneenqid6w5/4UWg3SW3HaqcScM6g2ACQy/637c416291ed89e6c070108f183e7b40/cambiar-contrasena.png)
 
 Listo! Contraseña recuperada y acceso autorizado.
diff --git a/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md b/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md
index ffd2feb0d..29121c531 100644
--- a/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md
+++ b/docs/tutorials/es/how-to-see-orders-closed-with-benefits.md
@@ -20,7 +20,7 @@ En la sección de __Gestión de pedidos__ es posible filtrar los pedidos realiza
 Si desea ver los pedidos que se han cerrado con esta promoción aplicada, basta con seguir los pasos abajo:
 
 1. En el menú del admin, haga clic en __Gestión de pedidos__.
-2. Haga clic en el botón de filtro y, dentro de la sección __Otros__, haga clic en la opción __Promociones__.![promo-filter-es](//images.ctfassets.net/alneenqid6w5/4XQZ3Rs60MEQe0GOG2UUSu/ee14a01ab48b01b570445565a1979405/promo-filter-es.png)
+2. Haga clic en el botón de filtro y, dentro de la sección __Otros__, haga clic en la opción __Promociones__.![promo-filter-es](https://images.ctfassets.net/alneenqid6w5/4XQZ3Rs60MEQe0GOG2UUSu/ee14a01ab48b01b570445565a1979405/promo-filter-es.png)
 3. Seleccione esta promoción y haga clic en __Confirmar__
 
 En la lista de pedidos, usted verá todos los pedidos cerradas con esta promoción.
diff --git a/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md b/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
index ef9246401..9d239d65b 100644
--- a/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
+++ b/docs/tutorials/es/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
@@ -30,7 +30,7 @@ Basta incluir un atributo con el nombre `salesChannel`, conforme a lo ilustrado
 
 Y entonces, los siguientes pedidos se crearán con el canal de ventas configurado. Si no hay stock para determinado ítem en este canal el ítem será excluido del pedido.  
 
-![posicao.es](//images.ctfassets.net/alneenqid6w5/1lTacScACYmqyzHKSZCydV/7a6e296f63afec40cf30c97a6a61e1ec/posicao.es.png)
+![posicao.es](https://images.ctfassets.net/alneenqid6w5/1lTacScACYmqyzHKSZCydV/7a6e296f63afec40cf30c97a6a61e1ec/posicao.es.png)
 
 *Pantalla donde se encuentra el ID del salesChannel*
 
@@ -40,6 +40,6 @@ Basta incluir un atributo con el nombre `defaultSLA`, conforme a lo ilustrado en
 
 Y entonces, el SLA configurado tendrá precedencia sobre el SLA más barato para los siguientes pedidos que se crearán – y si éste tiene una ventana de entrega, será seleccionado el primer intervalo disponible.
 
-![transportadora.es](//images.ctfassets.net/alneenqid6w5/41hy7FOGA3p94j3YX5kwiW/66ddd21e4f2ec65ae4a2ede3af059bbf/transportadora.es.png)
+![transportadora.es](https://images.ctfassets.net/alneenqid6w5/41hy7FOGA3p94j3YX5kwiW/66ddd21e4f2ec65ae4a2ede3af059bbf/transportadora.es.png)
 
 *Pantalla donde se encuentra el ID del SLA*
diff --git a/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md
index 3febb0c9e..912e8fd90 100644
--- a/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md
@@ -29,7 +29,7 @@ En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliaci
 
 1. Hacer login en http://www.google.com/tagmanager/ para la tienda que vamos a configurar;
 2. Ingresar al apartado etiquetas (tags) para configurar el device sesión id;
-3. Crear un producto de “HTML Personalizado” como se en la siguiente imagen:![payU 1](//images.contentful.com/alneenqid6w5/8Kc8zBKQFOmwK6G8ekgMa/2a26fa73a709b116cfdf899d4aee7a23/payU_1.png)
+3. Crear un producto de “HTML Personalizado” como se en la siguiente imagen:![payU 1](https://images.contentful.com/alneenqid6w5/8Kc8zBKQFOmwK6G8ekgMa/2a26fa73a709b116cfdf899d4aee7a23/payU_1.png)
 4. En el campo HTML de la configuración debemos pegar el código HTML que manda a llamar el código para mandar la información a PayU:
 
 ```
@@ -75,23 +75,23 @@ En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliaci
 <div id="maf"></div>
 ```
 
-![payU 2](//images.contentful.com/alneenqid6w5/4Y60ayHwaQa8ykaUQUmqgq/4a8ad711a25542b1513a75e94725c464/payU_2.png)
+![payU 2](https://images.contentful.com/alneenqid6w5/4Y60ayHwaQa8ykaUQUmqgq/4a8ad711a25542b1513a75e94725c464/payU_2.png)
 
-Después hay que realizar la configuración avanzada tal cual está en la siguiente imagen:![payU 3](//images.contentful.com/alneenqid6w5/2tZRZWcwFWgq6IueAKWQ4o/c64a7a0f2b6dbaad9405e3e55408fb8c/payU_3.png)
+Después hay que realizar la configuración avanzada tal cual está en la siguiente imagen:![payU 3](https://images.contentful.com/alneenqid6w5/2tZRZWcwFWgq6IueAKWQ4o/c64a7a0f2b6dbaad9405e3e55408fb8c/payU_3.png)
 
 Para configurar el evento, siga los pasos abajo:
 
-1. Entrar en la pestaña More:![payU 4](//images.contentful.com/alneenqid6w5/1NyDU3X1EseWcCisO04okg/66d6593915e933c22768633a76b4bf92/payU_4.png)
-2. Crear un evento personalizado:![payU 5](//images.contentful.com/alneenqid6w5/Xip98CFhokwoCs22GsUyK/a1c70a419c84d2f4fa2bb0908e0336cd/payU_5.png)
-3. Llenarlo de la siguiente manera:![payU 6](//images.contentful.com/alneenqid6w5/6Rdhtn8quA2IaqKSKeGa0u/0f7a6ed573a438475c477b5c09c331ad/payU_6.png)
-4. Guardamos el evento y posteriormente le damos guardar a la etiqueta (tag):![payU 7](//images.contentful.com/alneenqid6w5/2AcLzAcwgMs2SwgkEqEmo2/941c852d50622d570e8fab6534780e33/payU_7.png)
-5. Una vez que ya se guardó la etiqueta es necesario publicarla:![payU 8](//images.contentful.com/alneenqid6w5/6mpOQSBwzYq844A8uCuWck/125894734e6996cc1521b46c3562a8a7/payU_8.png)
+1. Entrar en la pestaña More:![payU 4](https://images.contentful.com/alneenqid6w5/1NyDU3X1EseWcCisO04okg/66d6593915e933c22768633a76b4bf92/payU_4.png)
+2. Crear un evento personalizado:![payU 5](https://images.contentful.com/alneenqid6w5/Xip98CFhokwoCs22GsUyK/a1c70a419c84d2f4fa2bb0908e0336cd/payU_5.png)
+3. Llenarlo de la siguiente manera:![payU 6](https://images.contentful.com/alneenqid6w5/6Rdhtn8quA2IaqKSKeGa0u/0f7a6ed573a438475c477b5c09c331ad/payU_6.png)
+4. Guardamos el evento y posteriormente le damos guardar a la etiqueta (tag):![payU 7](https://images.contentful.com/alneenqid6w5/2AcLzAcwgMs2SwgkEqEmo2/941c852d50622d570e8fab6534780e33/payU_7.png)
+5. Una vez que ya se guardó la etiqueta es necesario publicarla:![payU 8](https://images.contentful.com/alneenqid6w5/6mpOQSBwzYq844A8uCuWck/125894734e6996cc1521b46c3562a8a7/payU_8.png)
 
 Una vez que ya configuramos la etiqueta tenemos que guardar el JS que se manda a llamar desde el código. Este se guarda dentro del gestor de archivo de VTEX. Para hacerlo es necesario seguir los siguientes pasos:
 
 - Acceder al panel VTEX en el menú CMS >> Diseño >> Administrador de archivos >> Administración de archivos .js >> Agregar.
 
-__Anexo__: [md5.js](//assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
+__Anexo__: [md5.js](https://assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
 
 ### Validación
 
@@ -102,4 +102,4 @@ Para hacer la validación es necesario ingresar en la tienda, hacer todo el proc
 3. Hacer la búsqueda de la palabra MAF
 
 Si el resultado se encuentra quiere decir que la configuración esta correcta y el Fingerprint se están mandando correctamente, aquí un ejemplo:
-![payU 9](//images.contentful.com/alneenqid6w5/66H4gkLslyuk0sgOgm8IWC/3d04eca1fdb8ed6a7b4cbf7065a73ec3/payU_9.png)
+![payU 9](https://images.contentful.com/alneenqid6w5/66H4gkLslyuk0sgOgm8IWC/3d04eca1fdb8ed6a7b4cbf7065a73ec3/payU_9.png)
diff --git a/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 91d743bef..4225298d1 100644
--- a/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -71,7 +71,7 @@ Luego, solo tiene que recoger las informaciones de Adyen para registrarlas en VT
 5. ¡Recuerde anotar el nombre de usuario y la contraseña que aparecerá en el campo Password, ya que no volverá a estar visible!
 6. Haga clic en el botón **Save**, que está al final de la página.
 7. Después de estos pasos, su usuario debería haber sido creado con éxito. El número 1 (indicado en la imagen en rojo) es el username. El número 2 es la contraseña (password) que deberá ingresarse en el ambiente VTEX.
-![Adyen - Image 2](//images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
+![Adyen - Image 2](https://images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
 8. Envíe un e-mail para el soporte de Adyen (suporte@adyen.com) solicitando las habilitaciones listadas en el siguiente modelo:
 
 > Asunto: Configuración de los permisos de usuario webservice de VTEX para `{accountName}`
@@ -96,7 +96,7 @@ Si pretende utilizar la plataforma de Adyen para hacer análisis antifraude con
 
 <ui>5. La configuración deberá verse conforme sigue abajo. Asegúrese de hacer clic en **Save configuration** después de completar las alteraciones.</ui>
 
-![Adyen - Image 1](//images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
+![Adyen - Image 1](https://images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
 
 ## Configuraciones en VTEX
 
diff --git a/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
index 1d9f75046..bdc99adbe 100644
--- a/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -31,7 +31,7 @@ Para insertar  los scripts que Braspag/CyberSource requiere para el device finge
 
 ## Creación de variables (macros) y disparadores
 
-- Cree la variable de nombre `trasactionPaymentId`, tipo **Variable de la capa de datos**, leyendo la variable `transactionPayment.id` del datalayer.![](//images.contentful.com/alneenqid6w5/2iGloCXR32IMAyWAKe8qWy/cf1108ad17e944adc63f189e67cfa93d/gtm-cybersource-variavel1-1.png)
+- Cree la variable de nombre `trasactionPaymentId`, tipo **Variable de la capa de datos**, leyendo la variable `transactionPayment.id` del datalayer.![](https://images.contentful.com/alneenqid6w5/2iGloCXR32IMAyWAKe8qWy/cf1108ad17e944adc63f189e67cfa93d/gtm-cybersource-variavel1-1.png)
 - Cree la variable de nombre `cs_sessionId`, con el tipo **JavaScript personalizado** y el siguiente código:
 
 ```
@@ -41,15 +41,15 @@ function() {
   }
 ```
 
-![](//images.contentful.com/alneenqid6w5/2qhm00B2d2guyeqIU4gCCc/15c42813f5a0ad04937da7aebcc2e5b2/gtm-cybersource-variavel2-javascript-3.png)
+![](https://images.contentful.com/alneenqid6w5/2qhm00B2d2guyeqIU4gCCc/15c42813f5a0ad04937da7aebcc2e5b2/gtm-cybersource-variavel2-javascript-3.png)
 
 - Cree las variables `cs_orgId` y `cs_merchantId` con el tipo **Permanente**. El valor de estas dos variables deberá rellenarse con el contenido proporcionado por Braspag.
 
-![gtm-cybersource-variavel3-permanente](//images.contentful.com/alneenqid6w5/5EFSTIM6TCKUE4GEOA66kc/8c2f37cdd8cc94571f6f2ac72ec1d35b/gtm-cybersource-variavel3-permanente.png)
+![gtm-cybersource-variavel3-permanente](https://images.contentful.com/alneenqid6w5/5EFSTIM6TCKUE4GEOA66kc/8c2f37cdd8cc94571f6f2ac72ec1d35b/gtm-cybersource-variavel3-permanente.png)
 
 - Cree o edite un disparador para la pantalla de OrderPlaced (pantalla de compra finalizada con éxito), para que sea compatible con el evento de tipo **Evento personalizado** y de valor **orderPlaced**.
 
-![gtm-cybersource-acionador-orderplaced](//images.contentful.com/alneenqid6w5/51IPOyaAjmowkEQ24sYyw4/7b11cddfb71c200dd1cd2c85149c7726/gtm-cybersource-acionador-orderplaced.png)
+![gtm-cybersource-acionador-orderplaced](https://images.contentful.com/alneenqid6w5/51IPOyaAjmowkEQ24sYyw4/7b11cddfb71c200dd1cd2c85149c7726/gtm-cybersource-acionador-orderplaced.png)
 
 ## Creación de la tag para Braspag
 
@@ -68,6 +68,6 @@ Rellene con el siguiente código HTML:
 <script src="https://h.online-metrix.net/fp/check.js?org_id={{cs_orgId}}&amp;session_id={{cs_merchantId}}{{cs_sessionId}}" type="text/javascript"></script>
 ```
 
-![braspag fingerprint](//images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/f801a007a7d98773d06c741691a2e1ad/image.png_h_250_h_250)
+![braspag fingerprint](https://images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/f801a007a7d98773d06c741691a2e1ad/image.png_h_250_h_250)
 
 Por último, publique los cambios.
diff --git a/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
index d8665e158..130867c4c 100644
--- a/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -31,7 +31,7 @@ El consumidor programa una atención por medio de un formulario preparado por In
 
 El flujo de la programación que recorre el cliente comienza en la elección de la tienda física donde prefiere ser atendido. En la siguiente imagen, solo observamos una tienda registrada; sin embargo, su marca puede registrar las tiendas físicas que desee.
 
-![indeva1](//images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
+![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
 <div class="alert alert-info">
 También es posible proporcionar al cliente un enlace que conduce directamente al formulario de una tienda física específica. Simplemente agregue el ID de la tienda al final de la URL. Con eso, el vendedor puede compartir el enlace de su tienda, por ejemplo, a través de un código QR o en los medios sociales.
@@ -48,7 +48,7 @@ Al hacer clic en la tienda deseada, el cliente es conducido al formulario. Allí
 
 Finalmente, el cliente simplemente hace clic en Programar horario. Con eso, esta visita entrará en la fila de atención programada mostrada por la aplicación de los vendedores.
 
-![indeva2](//images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
+![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
 <div class="alert alert-warning">
 Por el momento, la confirmación de la programación debe ser realizada de forma manual por la tienda. El cliente no recibirá ningún mensaje automático.
@@ -58,13 +58,13 @@ Por el momento, la confirmación de la programación debe ser realizada de forma
 
 La aplicación de Indeva Store organiza la fila de programaciones realizadas para cada tienda física. Este puede ser usado por vendedores o gerentes tanto para controlar las próximas atenciones programadas como para la visualización del historial de visitas ya atendidas.
 
-![indeva3](//images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
+![indeva3](https://images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
 
 Al hacer clic en una programación específica, el vendedor tiene acceso a sus detalles: fecha, hora de la visita, nombre del cliente, mensaje enviado, cantidad de personas y el número de teléfono del cliente.
 
 Si desea entrar en contacto con el cliente a partir de esa pantalla, el vendedor puede hacer clic en el botón Abrir Whatsapp. Será direccionado directamente a una ventana de conversación con el cliente específico en la aplicación de mensajes.
 
-![indeva4](//images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
+![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
 <div class="alert alert-info">
 La aplicación puede ser instalada en diversos dispositivos de la misma tienda, pero recomendamos que su equipo utilice una app por tienda, y no por vendedor.
@@ -118,7 +118,7 @@ La aplicación para los vendedores y gerentes de la tienda está disponible tant
 
 Después de instalar y abrir la aplicación, el vendedor deberá informar el token de 10 dígitos de la tienda para sincronizar el dispositivo e iniciar sesión.
 
-![indeva5](//images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
+![indeva5](https://images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
 
 Para recibir el token, entre en contacto con el equipo de Indeva por los canales de soporte:
 
diff --git a/docs/tutorials/es/how-to-set-up-the-zoom.md b/docs/tutorials/es/how-to-set-up-the-zoom.md
index 351498c9c..2773e7608 100644
--- a/docs/tutorials/es/how-to-set-up-the-zoom.md
+++ b/docs/tutorials/es/how-to-set-up-the-zoom.md
@@ -19,7 +19,7 @@ Un recurso muy común en tiendas online es el zoom.
 
 Esto permite ver detalles de una imagen cuando el cliente va pasando el mouse sobre las fotos de un producto. Vamos a ver cómo configurar e implementar esta funcionalidad.
 
-![zoom-configurações](//images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
+![zoom-configurações](https://images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
 
 ## Configurando el CSS
 
@@ -33,7 +33,7 @@ Abajo reproducimos un trecho de CSS que puede usar como punto de partida para es
 
 Luego, vamos a enviar el archivo CSS grabado al servidor. Para eso, haga clic en el módulo de *CMS* > **Layout** > Haga click en la carpeta **CMS** > **Files Manager** > Haga click en **.css** > En la ventana que se despliega a la derecha, haga clic en el botón **Add**.
 
-![add-cms-.css ](//images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
+![add-cms-.css ](https://images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
 
 Luego, localice el archivo CSS grabado arriba y envíelo al servidor haciendo clic en el botón **Localizar** y luego en el botón **Salvar arquivo** ("salvar archivo").
 
@@ -52,4 +52,4 @@ Ahora sólo hay que insertar `zoom="on"` en la tag del producto. Como se ve abaj
 
 Usted debe también configurar el tamaño estándar de la imagen de zoom. Puede definir eso en el módulo de **CMS** > **Configuraciones** > **Tipos de archivos**. Como estándar, ese tipo de imagen de zoom ya viene configurada con 1000×1000 pixels.
 
-![zoom-tiposdearquivos ES](//images.ctfassets.net/alneenqid6w5/4Re3BTK1hSSMOQcsWwQy8k/0eea4e4c0e26855df5a1e5346fff421f/zoom_tipo_de_archivos.png)
+![zoom-tiposdearquivos ES](https://images.ctfassets.net/alneenqid6w5/4Re3BTK1hSSMOQcsWwQy8k/0eea4e4c0e26855df5a1e5346fff421f/zoom_tipo_de_archivos.png)
diff --git a/docs/tutorials/es/how-to-set-up-visa-debit.md b/docs/tutorials/es/how-to-set-up-visa-debit.md
index 8441c06d7..9e6e04447 100644
--- a/docs/tutorials/es/how-to-set-up-visa-debit.md
+++ b/docs/tutorials/es/how-to-set-up-visa-debit.md
@@ -21,20 +21,20 @@ Para configurar el pago por Visa Débito en su tienda, en el Admin VTEX, accede
 En primer lugar, deberemos crear un plan de pagos para habilitar Visa Débito en el Checkout.
 Para eso, en **Configuración** acceda al menú de opciones de **Planes de pago**:
 
-![2.3](//images.ctfassets.net/alneenqid6w5/42TQNxEPPO8c0wW8k64U2E/862916e5d2a003018fd37d03a470adbc/2.3.png)
+![2.3](https://images.ctfassets.net/alneenqid6w5/42TQNxEPPO8c0wW8k64U2E/862916e5d2a003018fd37d03a470adbc/2.3.png)
 
 Seleccione Visa Electron para crear el plan de pagos:
 
-![4.3](//images.ctfassets.net/alneenqid6w5/2XPKxgRKhWkGoqeUa0qmSS/ad23305902a49316570c5ac8f9b3cf7d/4.3.png)
+![4.3](https://images.ctfassets.net/alneenqid6w5/2XPKxgRKhWkGoqeUa0qmSS/ad23305902a49316570c5ac8f9b3cf7d/4.3.png)
 
 ### Configurar Plan de Pagos
 Se deberá seleccionar la afiliación deseada para transaccionar los pagos, activar el plan de pagos y finalmente salvar los cambios:
 
-![3.3](//images.ctfassets.net/alneenqid6w5/4dI5gmauwMGuukI2wCSMOO/89fa814df4dd450410ed5cabe0cb89b8/3.3.png)
+![3.3](https://images.ctfassets.net/alneenqid6w5/4dI5gmauwMGuukI2wCSMOO/89fa814df4dd450410ed5cabe0cb89b8/3.3.png)
 
 ### Visualizando las tarjetas de débito en Checkout
 Luego de finalizar la configuración del plan de pagos de Visa Débito, se verá una nueva pestaña en el Checkout, llamada Tarjeta de Débito. Dicha pestaña contendrá la opción de Visa Débito para ser elegida por el cliente y pagar online.
 
-![Visa Debito 5](//images.contentful.com/alneenqid6w5/4M77qvnjhuWs8OA4goc4Ko/c58df4158183914589390e364cb0d7ed/Visa_Debito_5.png)
+![Visa Debito 5](https://images.contentful.com/alneenqid6w5/4M77qvnjhuWs8OA4goc4Ko/c58df4158183914589390e364cb0d7ed/Visa_Debito_5.png)
 
 **Importante**: El cliente debe contar con un gateway de pagos que permita transaccionar con tarjetas de débito y estar integrado con VTEX.
diff --git a/docs/tutorials/es/how-to-use-conditions-builder-app.md b/docs/tutorials/es/how-to-use-conditions-builder-app.md
index d7b97c7aa..5bc58e663 100644
--- a/docs/tutorials/es/how-to-use-conditions-builder-app.md
+++ b/docs/tutorials/es/how-to-use-conditions-builder-app.md
@@ -36,11 +36,11 @@ Después de instalar, usted puede acceder a la app desde la barra lateral (secci
 4. (Opcional) Escriba una pequeña descripción de su condición. Esta descripción es sólo para control interno, no será visible a sus clientes.
 5. Haga clic en "Empezar a construir".
 
-![createCondition](//images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
+![createCondition](https://images.ctfassets.net/alneenqid6w5/WkXz29OvGmQgEAYOGwiQk/68b1dea792bc5c988553d6ae4c5dbd58/createCondition.gif)
 
 Después de presionar el botón "Empezar a construir", usted verá un editor y una lista de bloques en el lado izquierdo de la pantalla. Ahora sólo tiene que arrastrar los bloques al editor y conectarlos, creando así su lógica.
 
-![creating](//images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
+![creating](https://images.ctfassets.net/alneenqid6w5/3L05PChLgkmiA6qs2a8i8c/227b9d1db75b7c6e7d261995bb14c359/creating.gif)
 
 ### Edición de una condición
 
@@ -53,4 +53,4 @@ Si desea que una condición ya no se aplique, usted puede simplemente deshabilit
 - Cuando el botón al lado de la condición es __azul__, está __habilitado__.
 - Cuando el botón al lado de la condición es __gris__, está __deshabilitado__.
 
-![enableDisableEnglish](//images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
+![enableDisableEnglish](https://images.ctfassets.net/alneenqid6w5/2HggPrXyekKGsuQWaiOCeW/625164be436cff27794209d2735262d1/enableDisableEnglish.gif)
diff --git a/docs/tutorials/es/how-to-use-the-index-report.md b/docs/tutorials/es/how-to-use-the-index-report.md
index 7389ace68..7d4a0d677 100644
--- a/docs/tutorials/es/how-to-use-the-index-report.md
+++ b/docs/tutorials/es/how-to-use-the-index-report.md
@@ -17,7 +17,7 @@ subcategory: 5yDQmr18K4GgQAeGwq8USa
 
 El **Informe de Indexación** es el reporte que indica el status de indexación de todos los productos de la tienda. 
 
-![productosindexados](//images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
+![productosindexados](https://images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> Acceda a ver más información en <a href="/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion">Entendiendo el funcionamiento de la indexación.</a>
diff --git a/docs/tutorials/es/how-to-use-the-search-result-control.md b/docs/tutorials/es/how-to-use-the-search-result-control.md
index 8d1889b3d..46fc722cb 100644
--- a/docs/tutorials/es/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/es/how-to-use-the-search-result-control.md
@@ -46,14 +46,14 @@ A continuación se muestra la lista de todos los atributos del control Search Re
 
 El código renderizado por el control Search Result tiene, de forma predeterminada, la siguiente estructura:
 
-![searchResult1](//images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
+![searchResult1](https://images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
 
 Y los elementos correspondientes que son renderizados por el control en su versión no personalizada siguen el patrón abajo:
 
-![searchResult2](//images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
+![searchResult2](https://images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
 
-![searchResult3](//images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
+![searchResult3](https://images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
 
-![searchResult4](//images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
+![searchResult4](https://images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
 
-![searchResult5](//images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
+![searchResult5](https://images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
diff --git a/docs/tutorials/es/how-to-use-the-shareable-cart-app.md b/docs/tutorials/es/how-to-use-the-shareable-cart-app.md
index 2c12eb90f..0daadcc64 100644
--- a/docs/tutorials/es/how-to-use-the-shareable-cart-app.md
+++ b/docs/tutorials/es/how-to-use-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 La app [Carrito Compartible](https://apps.vtex.com/vtex-social-selling/p) permite a los vendedores seleccionar productos para sus clientes y compartir el carrito lleno por canales como WhatsApp, Facebook Messenger y correo electrónico (Social Selling).
 
-![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artículo explica todos los pasos para utilizar esta funcionalidad: activar app, elegir los productos, agregar el código del vendedor, compartir y crear un nuevo carrito. Antes de comenzar, tienes que [activar esta funcionalidad en su tienda](https://help.vtex.com/es/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg).
 
@@ -31,25 +31,25 @@ Donde `{Dirección web de su tienda}` debe ser reemplazada por la dirección del
 
 La interfaz de carrito compartible debe aparecer en la pantalla, incluyendo algunos de los íconos que se muestran a continuación. Las opciones disponibles dependen de la configuración elegida por la tienda.
 
-![Screen Shot 2020-05-03 at 17.37.11](//images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
+![Screen Shot 2020-05-03 at 17.37.11](https://images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
 
 ## Escoger los productos
 
 Una vez activada la app, no es necesario iniciar sesión para empezar a navegar y seleccionar productos. Basta con navegar por la tienda con normalidad, como si estuviera haciendo una compra en línea. Una vez que haya elegido todos los productos para el cliente, simplemente abra el carrito y siga los siguientes pasos en la interfaz de carrito compartible.
 
-![shareable-cart-chooseproducts](//images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
+![shareable-cart-chooseproducts](https://images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
 
 ## Agregar código de vendedor
 
 Después de seleccionar los productos, haga clic en el botón <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> para agregar su código de vendedor. Siga las instrucciones de la tienda al rellenar, pues cada tienda puede elegir diferentes formas de identificar a los vendedores y añadir descuentos a su carrito.
 
-![shareable-cart-addcode](//images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
+![shareable-cart-addcode](https://images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
 
 ## Rellene los datos personales y la dirección (opcional)
 
 Según la preferencia del cliente y la orientación de su tienda, podrá rellenar los datos personales y de entrega del pedido. **Los datos de pago siempre deben ser ingresados por el cliente**.
 
-![shareable-cart-customerdetails](//images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
+![shareable-cart-customerdetails](https://images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
 
 <div class="alert alert-danger" role="alert"><strong>Nunca pida los datos de pago al enviar el carrito.</strong> Incluso si el cliente insiste, informe que es por la seguridad de todos que él debe ingresar los datos de pago.</div>
 
@@ -57,7 +57,7 @@ Según la preferencia del cliente y la orientación de su tienda, podrá rellena
 
 Después de agregar su código de vendedor, haga clic en el botón correspondiente a la opción deseada. A continuación, detallamos los pasos para cada forma en la que se puede compartir.
 
-![shareable-cart-sharecart](//images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
+![shareable-cart-sharecart](https://images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
 
 ### WhatsApp
 
diff --git a/docs/tutorials/es/how-to-use-the-unavailable-product-class.md b/docs/tutorials/es/how-to-use-the-unavailable-product-class.md
index 19e8bad81..b005a4de7 100644
--- a/docs/tutorials/es/how-to-use-the-unavailable-product-class.md
+++ b/docs/tutorials/es/how-to-use-the-unavailable-product-class.md
@@ -29,7 +29,7 @@ __Caso un SKU con determinada especificación no esté disponible en stock, la t
 
 En el ejemplo siguiente, los tamaños P y G del producto no están disponibles.
 
-![classeIndisponivel](//images.contentful.com/alneenqid6w5/6dTacclHvqeaMwws8kqU8K/2d0d79d95dc521626eb1ba5c1c056da2/classeIndisponivel.png)
+![classeIndisponivel](https://images.contentful.com/alneenqid6w5/6dTacclHvqeaMwws8kqU8K/2d0d79d95dc521626eb1ba5c1c056da2/classeIndisponivel.png)
 
 ## Incluir la clase de producto no disponible
 
diff --git a/docs/tutorials/es/how-to-use-vtex-predictor-bot.md b/docs/tutorials/es/how-to-use-vtex-predictor-bot.md
index b56e80b48..3cb41e260 100644
--- a/docs/tutorials/es/how-to-use-vtex-predictor-bot.md
+++ b/docs/tutorials/es/how-to-use-vtex-predictor-bot.md
@@ -28,18 +28,18 @@ Al combinar datos de diferentes fuentes, el bot es capaz de predecir cómo sus v
 ## Como el Predictor Bot funciona
 
 Comenzamos por una idea general de cómo está el rendimiento de su tienda.
-![sales data](//images.contentful.com/alneenqid6w5/4LVuTVHevYw6eaykMwQY4M/8b9a06a17479a1595c05d879071ad320/sales_data.png)
+![sales data](https://images.contentful.com/alneenqid6w5/4LVuTVHevYw6eaykMwQY4M/8b9a06a17479a1595c05d879071ad320/sales_data.png)
 
 Como se muestra en la imagen de arriba, cada tienda típica tiene un patrón - incluso sobre una base diaria, o por hora. Debemos identificar este patrón para iniciar cualquier análisis.
 
 Pero no todo es fácil. Muchas veces vemos algo más o menos así:
-![crazy sales data](//images.contentful.com/alneenqid6w5/K7vwyviY4S6Q4CwSOSsaW/a644e1f182e82da152d69c661f3f44b7/crazy_sales_data.png)
+![crazy sales data](https://images.contentful.com/alneenqid6w5/K7vwyviY4S6Q4CwSOSsaW/a644e1f182e82da152d69c661f3f44b7/crazy_sales_data.png)
 
 En este caso, debemos quitar discrepancias y comparar nuevos conjuntos de datos contra otros períodos. Continuamos iterando así hasta que nuestro algoritmo sepa que tenemos un conjunto seguro de datos. En ese punto, podemos analizar y __identificar los eventos que huyen al patrón.__
 
 Al final, nuestro gráfico previsto es algo como la curva abajo. La línea azul es el resultado de nuestro modelo. Esta curva está contenida en un intervalo de confianza (área azul).
 
-![unnamed](//images.contentful.com/alneenqid6w5/4dyeHM6ycoSGs0kgMUSQqo/56ff4ea1a3478dfea3fc8c4d9860280c/unnamed.png)
+![unnamed](https://images.contentful.com/alneenqid6w5/4dyeHM6ycoSGs0kgMUSQqo/56ff4ea1a3478dfea3fc8c4d9860280c/unnamed.png)
 
 Siempre que encontramos algo, le informamos! Si su rendimiento actual se aleja de nuestro modelo pero está dentro de los intervalos, enviamos sólo un __ALERTA__. Si está más allá, usted recibe una advertencia __CRÍTICA__.
 
@@ -47,7 +47,7 @@ Siempre que encontramos algo, le informamos! Si su rendimiento actual se aleja d
 
 Podemos mandar tres tipos de correos electrónicos. Aquí hay un ejemplo:
 
-![Vtex Predictor Bot template](//images.contentful.com/alneenqid6w5/1Ft1I0ibI4g86okS4IYKy0/293929eb488252dabe8cdadee29c86e7/Vtex_Predictor_Bot_template.png)
+![Vtex Predictor Bot template](https://images.contentful.com/alneenqid6w5/1Ft1I0ibI4g86okS4IYKy0/293929eb488252dabe8cdadee29c86e7/Vtex_Predictor_Bot_template.png)
 
 Este es un ejemplo de notificación enviada cuando la anomalía ya no existe y las ventas de su tienda se han vuelto a la normalidad.
 
diff --git a/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md b/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md
index 6c3a5fef9..b3746f7d6 100644
--- a/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md
+++ b/docs/tutorials/es/how-to-view-taxes-information-in-taxhub.md
@@ -17,6 +17,6 @@ subcategory:
 
 Cuando un producto es agregado en el carrito serán destacados los valores cobrados de cada impuesto configurado anteriormente. Para el cálculo de impuesto es necesario el llenado de los datos del cliente y los datos de entrega de compra. En la página de finalizar compra, los impuestos estarán siempre destacados. El encargado de la tienda también tendrá la información destacada en el Gestión de Pedidos.
 
-![Screenshot 3 -Taxes](//images.ctfassets.net/alneenqid6w5/1yksMys16QmgYSsa6SqCIC/3f71427d0e6c02d48db88c52da9dfe04/Screenshot_3.png)
+![Screenshot 3 -Taxes](https://images.ctfassets.net/alneenqid6w5/1yksMys16QmgYSsa6SqCIC/3f71427d0e6c02d48db88c52da9dfe04/Screenshot_3.png)
 
 [Vea la estructura de API Rest para TaxHub](/es/tutorial/taxhub-estructura-del-api-rest)
diff --git a/docs/tutorials/es/how-to-view-the-orders-details.md b/docs/tutorials/es/how-to-view-the-orders-details.md
index 42f8a77c3..519084791 100644
--- a/docs/tutorials/es/how-to-view-the-orders-details.md
+++ b/docs/tutorials/es/how-to-view-the-orders-details.md
@@ -30,7 +30,7 @@ En el lado derecho hay un cuadro que contiene el valor total del pedido, los dat
 
 El ID se refiere a la transacción en el Pagos de la plataforma VTEX, y es incluso parte de la URL.
 
-![pci](//images.contentful.com/alneenqid6w5/65oy7tCoAoCMgGIi4CYau6/69e8caa34812349a09014157d0d27e33/pci.png)
+![pci](https://images.contentful.com/alneenqid6w5/65oy7tCoAoCMgGIi4CYau6/69e8caa34812349a09014157d0d27e33/pci.png)
 
 Por encima de esta caja, hay un enlace al pedido en el módulo **Pedidos**.
 
@@ -51,19 +51,19 @@ A continuación se muestran ejemplos de cómo ver los escenarios más comunes qu
 
 ### Evento de aprobación
 
-![](//images.contentful.com/alneenqid6w5/2P90PVqJl6qOWGkc6icoss/fba44bb1bd12c7e42d1658d91d6edd73/2.jpg)
+![](https://images.contentful.com/alneenqid6w5/2P90PVqJl6qOWGkc6icoss/fba44bb1bd12c7e42d1658d91d6edd73/2.jpg)
 
 En este ejemplo, vemos la aprobación de un pago. Es decir, vemos que la operadora autorizó el cierre de la compra con estos datos de pago.
 
 ### Evento de aprobación de antifraude
 
-![](//images.contentful.com/alneenqid6w5/2kCKR8mx3KUGW60cSs0wmo/d4cb6c1271069fd4f85e8ccb0813ef27/3.jpg)
+![](https://images.contentful.com/alneenqid6w5/2kCKR8mx3KUGW60cSs0wmo/d4cb6c1271069fd4f85e8ccb0813ef27/3.jpg)
 
 En este ejemplo, vemos el retorno del antifraude recibiendo la transacción y posteriormente el retorno con el análisis de riesgo realizado, aprobando la misma. En casos de reprobación, el registro mostrará la información `RiskRejected`.
 
 ### Evento de factura
 
-![](//images.contentful.com/alneenqid6w5/5v6fzCwSCkeqO8g24kSkqS/5e8d39795949ce428153a0e18bcdf558/4.jpg)
+![](https://images.contentful.com/alneenqid6w5/5v6fzCwSCkeqO8g24kSkqS/5e8d39795949ce428153a0e18bcdf558/4.jpg)
 
 En este ejemplo, la operadora regresa con el evento de liquidación del valor, o sea, informa que realizó la factura del pedido.
 
@@ -71,7 +71,7 @@ En este ejemplo, la operadora regresa con el evento de liquidación del valor, o
 
 El ejemplo siguiente muestra una transacción de tarjeta de crédito que generó un error al procesar el adquirente Redecard. Los afiliados suelen devolver un código (`ConnectorCode`) junto a un mensaje. Para encontrar información detallada del error, se recomienda consultar la documentación del adquirente. A través de una búsqueda rápida en Google, usted puede encontrar la lista de códigos y mensajes de cada afiliado.
 
-![2017-01-26 20_23_37-634883 _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/4CR2xqOZMkEEKoq0Q4008W/0088088b1a2167314ee31ab1078435b6/2017-01-26-20_23_37-634883-_-VTEX-PCI-Gateway.png)
+![2017-01-26 20_23_37-634883 _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/4CR2xqOZMkEEKoq0Q4008W/0088088b1a2167314ee31ab1078435b6/2017-01-26-20_23_37-634883-_-VTEX-PCI-Gateway.png)
 
 ## Liquidación automática programada
 
@@ -81,7 +81,7 @@ Si se cancela el pedido, la anulación se producirá normalmente.
 
 Vea abajo la fecha de la programación de la liquidación automática:
 
-![](//images.contentful.com/alneenqid6w5/3cUrT8OgtiiiKGiaySoO4Q/5abbea075f47b3c3334954a3fa53f006/5.jpg)
+![](https://images.contentful.com/alneenqid6w5/3cUrT8OgtiiiKGiaySoO4Q/5abbea075f47b3c3334954a3fa53f006/5.jpg)
 
 ## TID de pago
 
@@ -91,22 +91,22 @@ Esta información es importante siempre que sea necesario confirmar algo con la
 
 Para encontrar este código en la transacción, vea la siguiente ilustración.
 
-![](//images.contentful.com/alneenqid6w5/4UGw2BvqvewicmA4sYq64a/488e64d672529ed30b56e364efd4e89f/6.jpg)
+![](https://images.contentful.com/alneenqid6w5/4UGw2BvqvewicmA4sYq64a/488e64d672529ed30b56e364efd4e89f/6.jpg)
 
 ## IP del cliente
 
 El IP del cliente se recolecta en el momento de la compra y puede ser visto en el campo superior de la pantalla de la transacción, conforme imagen abajo.
 
-![](//images.contentful.com/alneenqid6w5/3luCOyDKZ2a22y2q26S6E/1b77e158a83d51f43a4e9bb74981a512/7.jpg)
+![](https://images.contentful.com/alneenqid6w5/3luCOyDKZ2a22y2q26S6E/1b77e158a83d51f43a4e9bb74981a512/7.jpg)
 
 ## ID del antifraude
 
 Es el ID de la transacción para el antifraude. Para las búsquedas en el antifraude, se debe consultar este valor en el PCI Gateway.
 
-![IDAntifraude](//images.contentful.com/alneenqid6w5/6KrRXQocKWy6kQosaOgiyU/77e8ae4f52c586280a17a08373675301/IDAntifraude-1.gif)
+![IDAntifraude](https://images.contentful.com/alneenqid6w5/6KrRXQocKWy6kQosaOgiyU/77e8ae4f52c586280a17a08373675301/IDAntifraude-1.gif)
 
 ## Más informaciones
 
 Además de la información anterior, hay otros datos extraídos de las interacciones con la operadora, el gateway y/o con el antifraude que se identifican y se ofrecen de forma más clara en el cuadro **+ información** justo debajo de la parte superior de la información. En la siguiente imagen se muestra cómo:
 
-![](//images.contentful.com/alneenqid6w5/2fHaJACApyyUsIGueGkckU/edade2f60187dc9aed87942e8030d938/8.jpg)
+![](https://images.contentful.com/alneenqid6w5/2fHaJACApyyUsIGueGkckU/edade2f60187dc9aed87942e8030d938/8.jpg)
diff --git a/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md b/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md
index e1ca2b4a4..654926db5 100644
--- a/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md
+++ b/docs/tutorials/es/how-to-view-transactions-on-pci-gateway.md
@@ -23,7 +23,7 @@ Aquí ya tendremos indicado su status actual, el inicio (fecha y hora) de la tra
 
 Cada inscripción de Pedido tendrá sus datos restrictos a las condiciones de pago utilizadas para su cierre. Esto es, códigos de autorización, transacción, NSU, entre otros, están puestos a disposición dentro de cada registro.
 
-![payment_es](//images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/f87572b076ab9705c62219316daa72d7/payment_es.jpg)
+![payment_es](https://images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/f87572b076ab9705c62219316daa72d7/payment_es.jpg)
 
 Para mayores informaciones sobre los eventos generados en las transacciones, acceda: [Eventos de la transacción](/hc/es-419/articles/215876397 "Eventos de la transacción").
 
diff --git a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
index 1bb48a014..4170b30b9 100644
--- a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
@@ -38,7 +38,7 @@ Después de eso, una nueva sección estará disponible y podrá definir a travé
 
 Es posible limitar la disponibilidad del template a un período de tiempo predeterminado rellenando los campos __From__ y __To__, así como definir en qué categorías, productos, marcas y colecciones se aplicará el template elegido.
 
-![template-condicionado-cms](//images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
+![template-condicionado-cms](https://images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
 
 Después de llenar todos los campos, asegúrese de guardar los cambios realizados haciendo clic en __Save Layout__.
 
diff --git a/docs/tutorials/es/i-cant-import-the-price-table.md b/docs/tutorials/es/i-cant-import-the-price-table.md
index 2e112235b..af2d01514 100644
--- a/docs/tutorials/es/i-cant-import-the-price-table.md
+++ b/docs/tutorials/es/i-cant-import-the-price-table.md
@@ -56,7 +56,7 @@ Comprueba que los campos de tu plantilla estén rellenados según las guías de
 
 Ejemplo de plantilla con filtros aplicados y con los campos __Error Code__ y __Error Messages__:
 
-![Hoja de precios](//images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/2412a0609e152f55f147e4c05e76e2be/Price_spreadsheet.PNG)
+![Hoja de precios](https://images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/2412a0609e152f55f147e4c05e76e2be/Price_spreadsheet.PNG)
 
 #### Tamaño de archivo
 
diff --git a/docs/tutorials/es/i-cant-receive-emails-from-vtex.md b/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
index 334894921..84b04326c 100644
--- a/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
+++ b/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
@@ -95,4 +95,4 @@ También puedes comprobar si la dirección de email está registrada como copia
 3. Comprueba que en los campos __CC:__ o __CCO:__ de la plantilla no figura ninguna dirección de email. En caso contrario, elimina la información y haz clic en `Save`.
 4. Realiza este procedimiento con cada una de las plantillas de la tienda y haz una prueba de envío de email a la dirección deseada.
 
-![copia_email_es](//images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/a31ab802e560774fa1ef533d50dffd88/copia_email_es.png)
+![copia_email_es](https://images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/a31ab802e560774fa1ef533d50dffd88/copia_email_es.png)
diff --git a/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
index 3fc1fbc8f..3d42d555e 100644
--- a/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
+++ b/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
@@ -21,9 +21,9 @@ Cuando el usuario realiza una búsqueda en una tienda VTEX utilizando [Intellige
 
 Ejemplo: al buscar en el sitio web de la tienda productos que contengan el término "Pendleton", los resultados de la búsqueda muestran 6 productos. Sin embargo, cuando accedemos al Admin VTEX (__Storefront > Intelligent Search > Explicación de la búsqueda__) e ingresamos el mismo término, se muestran 9 productos.
 
-![Filter_1](//images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/fd5b87b16752fbec8cfaec8258bf22d4/Filter_1.png)
+![Filter_1](https://images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/fd5b87b16752fbec8cfaec8258bf22d4/Filter_1.png)
 
-![Filter_2](//images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/d06e5b6d2114ea99424449d66eb3b887/Filter_2.png)
+![Filter_2](https://images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/d06e5b6d2114ea99424449d66eb3b887/Filter_2.png)
 
 Este comportamiento puede ocurrir debido a los siguientes escenarios:
 
@@ -83,7 +83,7 @@ Para remover la restricción de búsqueda por marca (brand) y permitir que los p
 
 <blockquote><ui>4. En <b>Selecciona una aplicación</b>, chaz clic en la opción de Rewriter (<b>vtex.rewriter@{app-version-number}</b>).</ui>
 
-![Graphql_ide_es](//images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/2751cf7c83a8d37216f82a532d77c3a7/Graphql_ide_es.png)
+![Graphql_ide_es](https://images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/2751cf7c83a8d37216f82a532d77c3a7/Graphql_ide_es.png)
 
 <blockquote><ui>5. En el campo de entrada de datos de la consulta (debajo de <b>GraphiQL</b>), ingresa los datos de la función mutación <i>saveInternal</i>.<ui>
 
diff --git a/docs/tutorials/es/identifying-whether-marketing-utms-are-being-passed-to-checkout.md b/docs/tutorials/es/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
index 4542b3f15..9b847a3bc 100644
--- a/docs/tutorials/es/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
+++ b/docs/tutorials/es/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
@@ -27,13 +27,13 @@ Con eso el checkout podrá montar el orderForm considerando el marketingData usa
 
 Para asegurarse de que el contenido del parámetro `utm_source`, por ejemplo, se está pasando al checkout, usted puede seguir estos pasos:
 1. Acceda a cualquier página de la tienda con una utm en la querystring (ej: {AccountName}.com.br`?utm_source=facebook`).
-2. Ingrese al __developer tools__ (F12 en Chrome, si está en Windows, o Cmd+Opt+I, en el Mac), acceda a la pestaña __Application__, abra los cookies del sitio de la tienda y busque el cookie __IPS__.![utmSource1](//images.contentful.com/alneenqid6w5/2tGleKs2b2Gge8oEoquSGm/17efaf14e42cd655b037c2bd009eb0d6/utmSource1.png)
+2. Ingrese al __developer tools__ (F12 en Chrome, si está en Windows, o Cmd+Opt+I, en el Mac), acceda a la pestaña __Application__, abra los cookies del sitio de la tienda y busque el cookie __IPS__.![utmSource1](https://images.contentful.com/alneenqid6w5/2tGleKs2b2Gge8oEoquSGm/17efaf14e42cd655b037c2bd009eb0d6/utmSource1.png)
 3. Entre en una página de producto e inserte un producto en el carrito.
 4. Entre en el carrito.
 5. Actualice la página y, en la pestaña __Network__ de developer tools, monitoree los requests.
 6. Seleccione el request __orderForm__.
 7. En el preview, abra el nodo `marketingData`.
-8. Compruebe el valor del campo `utmSource`.![utmSource2](//images.contentful.com/alneenqid6w5/3k5685cAUwy4uk4S2I6qGm/6595f50415b17965047c2023ffb46658/utmSource2.png)
+8. Compruebe el valor del campo `utmSource`.![utmSource2](https://images.contentful.com/alneenqid6w5/3k5685cAUwy4uk4S2I6qGm/6595f50415b17965047c2023ffb46658/utmSource2.png)
 
 En el ejemplo de la imagen anterior, usted puede ver que el valor del parámetro `utm_source` fue correctamente pasado al checkout, que introdujo ese parámetro en el orderForm, dentro del campo `utmSource`.
 
diff --git a/docs/tutorials/es/image-compression.md b/docs/tutorials/es/image-compression.md
index f23430981..17ad3ac4a 100644
--- a/docs/tutorials/es/image-compression.md
+++ b/docs/tutorials/es/image-compression.md
@@ -44,7 +44,7 @@ Al mismo tiempo, las imágenes PNG se optimizan utilizando[ pngquant](https://pn
 
 Por último, VTEX entrega el archivo más compacto de entre el WebP sin pérdida y el PNG optimizado, como se ilustra en el siguiente diagrama.
 
-![png-image-compression-es](//images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/ea1861651c0c3576bb865f2c050a3792/png-image-compression-es.PNG)
+![png-image-compression-es](https://images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/ea1861651c0c3576bb865f2c050a3792/png-image-compression-es.PNG)
 
 ## JPG/JPEG
 
@@ -52,7 +52,7 @@ Para imágenes en formato **JPG/JPEG**, indicado para fotos, la conversión a We
 
 VTEX entrega al cliente la imagen que tenga el tamaño de archivo más pequeño de entre la original y la convertida a WebP sin pérdida, como se ilustra en el siguiente diagrama.
 
-![webp-image-compression-es](//images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/7213c5a45d35166c492201c6e8487d3f/webp-image-compression-es.PNG)
+![webp-image-compression-es](https://images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/7213c5a45d35166c492201c6e8487d3f/webp-image-compression-es.PNG)
 
 ## Artículos relacionados
 
diff --git a/docs/tutorials/es/importing-data-into-master-data.md b/docs/tutorials/es/importing-data-into-master-data.md
index 349b35869..f743f8de3 100644
--- a/docs/tutorials/es/importing-data-into-master-data.md
+++ b/docs/tutorials/es/importing-data-into-master-data.md
@@ -49,4 +49,4 @@ Mantenga el mismo formato de la planilla (xls) para realizar la importación con
 5. Elija el archivo.
 6. Haga clic en el botón **Importar** en la esquina inferior de la pantalla.
 
-[![Importando](//images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
+[![Importando](https://images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
diff --git a/docs/tutorials/es/improving-the-performance-of-product-images.md b/docs/tutorials/es/improving-the-performance-of-product-images.md
index edd90c4e3..26602166d 100644
--- a/docs/tutorials/es/improving-the-performance-of-product-images.md
+++ b/docs/tutorials/es/improving-the-performance-of-product-images.md
@@ -64,7 +64,7 @@ En nuestro ejemplo anterior, basta escribir de la siguiente manera la URL de la
 
 De esta forma, el VTEX Img entregara la imagen con un tamaño de 50&#215;50. Esto realizara la carga de su site mucho más rápido.
 
-![tamanhosImg](//images.contentful.com/alneenqid6w5/p4aDcgaE4SmyYkCwaW0CI/189307d29c86dae17beabde67780d907/tamanhosImg.png)
+![tamanhosImg](https://images.contentful.com/alneenqid6w5/p4aDcgaE4SmyYkCwaW0CI/189307d29c86dae17beabde67780d907/tamanhosImg.png)
 _Entregar imágenes un tamaño mayor que el de exhibición perjudica la performance de su tienda._
 
 ## Imagenes rectangulares
diff --git a/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md b/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md
index 1398f1e57..832ee0d02 100644
--- a/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md
+++ b/docs/tutorials/es/improving-the-seo-of-product-listing-pages.md
@@ -21,7 +21,7 @@ Las PLP están correlacionadas porque cada producto tiene un enlace a una págin
 
 Para mejorar el rendimiento SEO de las PLP, debes permitir que los rastreadores web, como Google, noten esta conexión entre las PLP. De esta manera, estos rastreadores podrán navegar por diferentes páginas y acceder a los diferentes productos que muestran.
 
-![Button mostrar más](//images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/8723224ebef9b883e645b3d366e54d48/bt-mostrar-m__s.png)
+![Button mostrar más](https://images.ctfassets.net/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/8723224ebef9b883e645b3d366e54d48/bt-mostrar-m__s.png)
 
 Ve a continuación cómo mejorar el rendimiento SEO de las PLP [utilizando el Site Editor](#utilizando-site-editor).
 
@@ -39,7 +39,7 @@ Para mejorar el rendimiento SEO de las PLP a través del Site Editor, debes conf
 4. Haz clic en __Mostrar más.__
 5. En __Comportamiento del botón,__ selecciona la opción __Link a la página - Mejora el SEO, puede cambiar el aspecto del botón.__
 
-![bt-config-es](//images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/528fc1e6393d25e09346b28e93aedd97/bt-config-es.gif)
+![bt-config-es](https://images.ctfassets.net/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/528fc1e6393d25e09346b28e93aedd97/bt-config-es.gif)
 
 6. Haz clic en `GUARDAR`.
 7.  Para configurar el ítem __Mostrar anterior,__ amplíe el bloque Resultado de búsqueda flexible.
diff --git a/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md b/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md
index 55e87c222..d2b442d24 100644
--- a/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md
+++ b/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md
@@ -36,7 +36,7 @@ Digamos que usted desea insertar el nombre del transportista en el e-mail de ped
 
 Para ello, entre en la plantilla de pedido enviado y, en el campo __JSON Data__, busque la propiedad `courier`.
 
-![templateCourierMCEspanhol](//images.contentful.com/alneenqid6w5/5bUVtrYTugUiqKimU6COEK/d73394e8e6f37fe56ea7ec6718c7edf6/templateCourierMCEspanhol.png)
+![templateCourierMCEspanhol](https://images.contentful.com/alneenqid6w5/5bUVtrYTugUiqKimU6COEK/d73394e8e6f37fe56ea7ec6718c7edf6/templateCourierMCEspanhol.png)
 
 El valor llenado para esta propiedad es sólo un ejemplo, pero puede utilizarlo en el campo __HTML__ para que, cuando se envía el e-mail, el cliente vea el transportista de hecho responsable de la entrega del pedido.
 
@@ -44,7 +44,7 @@ Tenga en cuenta que la propiedad `courier` está dentro del objeto `package`. Po
 
 `{{package.courier}}`
 
-![courier3](//images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
+![courier3](https://images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
 
 Vea que el valor de ejemplo ("Transportadora Teste Courier S.A.") se ha insertado en la pantalla de vista previa, debajo de los campos __HTML__ y __JSON Data__.
 
diff --git a/docs/tutorials/es/indexes-in-master-data.md b/docs/tutorials/es/indexes-in-master-data.md
index 18affe23a..7b2c7aa3f 100644
--- a/docs/tutorials/es/indexes-in-master-data.md
+++ b/docs/tutorials/es/indexes-in-master-data.md
@@ -56,11 +56,11 @@ Si solo hay un campo configurado como índice, la clave alternativa evitará que
 
 Por ejemplo, la tabla **Cliente** tiene dos columnas: **ID** y **nombre**. Para facilitar la búsqueda, el campo **Nombre** (`name`) puede configurarse como índice y marcarse como **Valores únicos**, como se ilustra a continuación:
 
-![indices-1-es](//images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/2a87ed75f094011598e43f6b019b9aac/indices-1-es.png)
+![indices-1-es](https://images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/2a87ed75f094011598e43f6b019b9aac/indices-1-es.png)
 
 Como resultado, no será posible ingresar un nombre que ya haya sido registrado en **Cliente**:
 
-![indices-2-es](//images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/d6142ece91ab5f6db03a8e97d7adb57c/indices-2-es.png)
+![indices-2-es](https://images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/d6142ece91ab5f6db03a8e97d7adb57c/indices-2-es.png)
 
 En el ejemplo anterior, como ya existe un registro con el **Nombre** igual a **María**, no es posible registrar otro con el mismo valor.
 
@@ -74,11 +74,11 @@ Si hay más de un campo en el índice, la clave alternativa evitará que un conj
 
 Por ejemplo, considera que la entidad **Cliente** tiene tres campos: **ID**, **Nombre** y **Documento**. En la configuración del índice, en **Campos**, se ingresaron los términos Nombre (`firstName`) y Documento (`document`), como se ilustra a continuación:
 
-![indices-3-es](//images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/bdd2956a7232c41559937286463a9c4b/indices-3-es.png)
+![indices-3-es](https://images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/bdd2956a7232c41559937286463a9c4b/indices-3-es.png)
 
 En este caso, se puede repetir o el valor del **Nombre** o el valor del **Documento**. Sin embargo, la combinación de ambos valores no puede repetirse; es decir, no puede existir ningún registro con el mismo par (**Nombre** y **Documento**).
 
-![indices-4-es](//images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/3f47ce97a3d99c3109bdcb9d421b036f/indices-4-es.png)
+![indices-4-es](https://images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/3f47ce97a3d99c3109bdcb9d421b036f/indices-4-es.png)
 
 En el ejemplo anterior, ya existe un registro con el **Nombre** igual a **María**. Es posible incluir otro registro con el mismo **Nombre**, siempre que el valor del **Documento** sea diferente.
 
diff --git a/docs/tutorials/es/indexing-history-beta.md b/docs/tutorials/es/indexing-history-beta.md
index 508022eae..cad41b869 100644
--- a/docs/tutorials/es/indexing-history-beta.md
+++ b/docs/tutorials/es/indexing-history-beta.md
@@ -21,12 +21,12 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 
 El **Historial de indexación** es la página que monitorea el estado de sincronización de todos los productos del catálogo que se envían a Intelligent Search. Allí se puede ver ampliamente el progreso de la indexación de tu tienda.
 
-![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+![Histórico da Indexação 1 - ES](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
 
 La sección **Status de la indexación** muestra la siguiente información:
 
 * **Tiempo promedio de indexación:** tiempo promedio para la indexación de los productos, desde el momento en que el sistema recibió la notificación de un cambio, hasta la actualización en la tienda. El desempeño del tiempo de indexación se mide por un punto verde (saludable) o rojo (no saludable). 
-![Historico Indexação 2 - ES](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
+![Historico Indexação 2 - ES](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
 * **Productos en tienda:** cantidad de productos con información actualizada que se muestran actualmente en la tienda.
 * **División de status de indexación:** porcentaje de productos en cada etapa de indexación. El desempeño de los estados compartidos se mide por un punto verde (saludable) o rojo (no saludable). Las etapas que se muestran son:
     * **Actualizado:** la actualización más reciente del producto que se introdujo en la tienda.
@@ -37,15 +37,15 @@ Puedes filtrar la lista de productos indexados para tener una vista personalizad
 
 Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
 
 Si filtras por `Status`, puedes seleccionar el estado por el que deseas filtrar: `Actualizado`, `Actualizando`, `Error`.
 
-![Historico indexação 4 - ES](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
+![Historico indexação 4 - ES](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
 
 Si filtras por `Tiempo de indexación`, puedes seleccionar si el intervalo de tiempo `Es mayor que`, `Es igual o mayor que`, `Es menor que` o `Es igual o menor que` un horario definido.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
 
 Luego de definir el filtro, haz clic en `Aplicar` para activarlo. 
 
@@ -55,17 +55,17 @@ También puedes filtrar los productos exhibidos en la lista por **ID**, **Últim
 
 Si deseas obtener más información sobre la indexación de un producto específico, puedes hacer clic en la línea del producto en la lista para acceder a una ventana con más detalles, tal como se muestra a continuación.
 
-![Historico indexação 6 - ES](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
+![Historico indexação 6 - ES](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
 
 Además de los datos que se muestran en la lista de productos, también puedes ver:
 
 * **Tiempo de indexación:** registro de cuánto tiempo duró la última actualización del producto, en el formato `hh:mm:ss`.
 * **Cronología de indexación:** registro de cada cambio de estado con fecha y hora. Puedes ver más detalles de cada etapa haciendo clic en el ícono <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - ES](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
+![Historico indexação 7 - ES](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
 
 Puedes reindexar un producto manualmente sin tener que ingresar una actualización en su registro. Para reindexar un producto, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Reintentar la indexación`. Solo se pueden reindexar los productos en el estado **Actualizado**.
 
 Puedes acceder al **Historial de indexación** del producto, una lista con los datos y la hora de cada actualización realizada. De esta manera, puedes llevar un registro de todas las modificaciones que se le hicieron al producto. Para acceder al historial, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Historial`. 
 
-![Histórico da Indexação 8 - ES](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
+![Histórico da Indexação 8 - ES](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
diff --git a/docs/tutorials/es/indexing-history.md b/docs/tutorials/es/indexing-history.md
index e5ec2141b..e2968e01a 100644
--- a/docs/tutorials/es/indexing-history.md
+++ b/docs/tutorials/es/indexing-history.md
@@ -17,12 +17,12 @@ subcategory: l3DubpOCHBfKyF2ueg2Vs
 
 El **Historial de indexación** es la página que monitorea el estado de sincronización de todos los productos del catálogo que se envían a Intelligent Search. Allí se puede ver ampliamente el progreso de la indexación de tu tienda.
 
-![Histórico da Indexação 1 - ES](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
+![Histórico da Indexação 1 - ES](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/89edd8125cb7ba75422cd923886126df/Screenshot_2022-09-01_at_12-50-55_Historial_de_indexaci__n.png)
 
 La sección **Status de la indexación** muestra la siguiente información:
 
 * **Tiempo promedio de indexación:** tiempo promedio para la indexación de los productos, desde el momento en que el sistema recibió la notificación de un cambio, hasta la actualización en la tienda. El desempeño del tiempo de indexación se mide por un punto verde (saludable) o rojo (no saludable). 
-![Historico Indexação 2 - ES](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
+![Historico Indexação 2 - ES](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4ad2a5231418109514e3e19750318a79/Captura_de_Tela_2022-09-01_a__s_12.56.45.png)
 * **Productos en tienda:** cantidad de productos con información actualizada que se muestran actualmente en la tienda.
 * **División de status de indexación:** porcentaje de productos en cada etapa de indexación. El desempeño de los estados compartidos se mide por un punto verde (saludable) o rojo (no saludable). Las etapas que se muestran son:
     * **Actualizado:** la actualización más reciente del producto que se introdujo en la tienda.
@@ -33,15 +33,15 @@ Puedes filtrar la lista de productos indexados para tener una vista personalizad
 
 Para filtrar la lista de productos indexados, haz clic en `Filtrar` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecciona `Status` o `Tiempo de indexación` para definir el criterio de filtrado. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/382ba7a8177427afd252d481fadb50f2/Captura_de_Tela_2022-09-01_a__s_13.11.42.png)
 
 Si filtras por `Status`, puedes seleccionar el estado por el que deseas filtrar: `Actualizado`, `Actualizando`, `Error`.
 
-![Historico indexação 4 - ES](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
+![Historico indexação 4 - ES](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/d7cb059d0bbf81091223d6fcabdab984/Captura_de_Tela_2022-09-01_a__s_13.14.31.png)
 
 Si filtras por `Tiempo de indexación`, puedes seleccionar si el intervalo de tiempo `Es mayor que`, `Es igual o mayor que`, `Es menor que` o `Es igual o menor que` un horario definido.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/b4c83aa8c3234d0c50a4f43d1ef78458/Captura_de_Tela_2022-09-01_a__s_13.16.16.png)
 
 Luego de definir el filtro, haz clic en `Aplicar` para activarlo. 
 
@@ -51,17 +51,17 @@ También puedes filtrar los productos exhibidos en la lista por **ID**, **Últim
 
 Si deseas obtener más información sobre la indexación de un producto específico, puedes hacer clic en la línea del producto en la lista para acceder a una ventana con más detalles, tal como se muestra a continuación.
 
-![Historico indexação 6 - ES](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
+![Historico indexação 6 - ES](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/7fafb8add5b26f93deb0778da410c235/Screenshot_2022-09-01_at_13-20-16_Historial_de_indexaci__n.png)
 
 Además de los datos que se muestran en la lista de productos, también puedes ver:
 
 * **Tiempo de indexación:** registro de cuánto tiempo duró la última actualización del producto, en el formato `hh:mm:ss`.
 * **Cronología de indexación:** registro de cada cambio de estado con fecha y hora. Puedes ver más detalles de cada etapa haciendo clic en el ícono <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - ES](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
+![Historico indexação 7 - ES](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/0a1eda83412c9a2c25fdbb5a927fe5e2/Screenshot_2022-09-01_at_13-23-14_Historial_de_indexaci__n.png)
 
 Puedes reindexar un producto manualmente sin tener que ingresar una actualización en su registro. Para reindexar un producto, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Reintentar la indexación`. Solo se pueden reindexar los productos en el estado **Actualizado**.
 
 Puedes acceder al **Historial de indexación** del producto, una lista con los datos y la hora de cada actualización realizada. De esta manera, puedes llevar un registro de todas las modificaciones que se le hicieron al producto. Para acceder al historial, haz clic en <i class="fa-solid fa-arrow-rotate-left"></i> `Historial`. 
 
-![Histórico da Indexação 8 - ES](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
+![Histórico da Indexação 8 - ES](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/c936f2416a2224f4b10a3d59435ad892/Screenshot_2022-09-01_at_13-42-21_Historial_de_indexaci__n.png)
diff --git a/docs/tutorials/es/install-visa-checkout-in-the-extension-store.md b/docs/tutorials/es/install-visa-checkout-in-the-extension-store.md
index 30c4b3b80..1517b44f4 100644
--- a/docs/tutorials/es/install-visa-checkout-in-the-extension-store.md
+++ b/docs/tutorials/es/install-visa-checkout-in-the-extension-store.md
@@ -21,7 +21,7 @@ Este artículo tiene el objetivo de mostrar el paso a paso para instalación de
 
 En primer lugar, en la pantalla **Explorar**, haga clic en la extensión **Visa Checkout**.
 
-![Extension Store 1](//images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
+![Extension Store 1](https://images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
 
 Usted tendrá entonces acceso a la página de detalles de la extensión, donde se muestra la siguiente información:
 
@@ -76,4 +76,4 @@ Para mover el Visa Checkout para el ambiente en producción (donde sus clientes
 
 Para tanto, basta hacer clic en el botón **Publicar** de la top bar.
 
-![Extension Store 3 - Publishing](//images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
+![Extension Store 3 - Publishing](https://images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
diff --git a/docs/tutorials/es/installing-my-orders-through-the-extension-store.md b/docs/tutorials/es/installing-my-orders-through-the-extension-store.md
index d2275eee5..bef31cfc9 100644
--- a/docs/tutorials/es/installing-my-orders-through-the-extension-store.md
+++ b/docs/tutorials/es/installing-my-orders-through-the-extension-store.md
@@ -19,7 +19,7 @@ Acompañando la evolución de la plataforma VTEX, la viewpart de __Mis Pedidos__
 
 Para hacer la instalación, es necesario acceder a la [VTEX App Store.](https://extensions.vtex.com/)
 
-![app store1 ES](//images.ctfassets.net/alneenqid6w5/2GobyKLKZGwMwUCEG4EK4M/f0c80ce9e43715e0c095ffba7bfe7c86/app_store1_ES.png)
+![app store1 ES](https://images.ctfassets.net/alneenqid6w5/2GobyKLKZGwMwUCEG4EK4M/f0c80ce9e43715e0c095ffba7bfe7c86/app_store1_ES.png)
 
 __Al instalar la aplicación, uested ya cuenta con las siguientes actualizaciones:__
 
@@ -29,7 +29,7 @@ __Al instalar la aplicación, uested ya cuenta con las siguientes actualizacione
 - Información de rastreo para varios items.
 - Corrección de pequeños errores.
 
-![app store2 ES](//images.ctfassets.net/alneenqid6w5/3lD83GV6Y0EAewCOmU2Gc2/c25bdcc4aa23d9389c673e3b9d288115/app_store2_ES.png)
+![app store2 ES](https://images.ctfassets.net/alneenqid6w5/3lD83GV6Y0EAewCOmU2Gc2/c25bdcc4aa23d9389c673e3b9d288115/app_store2_ES.png)
 
 Además, con la nueva aplicación usted puede realizar pruebas de versiones y actualizarla cada vez que una nueva versión esté disponible, recibiendo mejoras continuas y actualizaciones de nuevas features.
 
@@ -42,4 +42,4 @@ Para realizar las pruebas de personalización en su página, usted puede trabaja
 5. ¡Listo! Ahora usted ve, antes de subir su página, cómo se comportará.
 6. Para mover My Orders al ambiente en producción (donde sus clientes pueden usarlo), usted debe publicar la modificación. Para ello, simplemente haga clic en el botón __Publicar__.
 
-![app store3 ES](//images.ctfassets.net/alneenqid6w5/3TusFkUgZOEOEmGQguwSia/a58831055ce0618e0164685ff655cbd1/app_store3_ES.png)
+![app store3 ES](https://images.ctfassets.net/alneenqid6w5/3TusFkUgZOEOEmGQguwSia/a58831055ce0618e0164685ff655cbd1/app_store3_ES.png)
diff --git a/docs/tutorials/es/integrate-with-carrefour.md b/docs/tutorials/es/integrate-with-carrefour.md
index 02e5f6ffd..5e41bdd6e 100644
--- a/docs/tutorials/es/integrate-with-carrefour.md
+++ b/docs/tutorials/es/integrate-with-carrefour.md
@@ -27,7 +27,7 @@ En la esquina superior derecha, haga clic en el email (es aquél que usted utili
 
 La clave que aparece en la pantalla es el dato que usted necesitará para registrar la integración dentro del módulo Bridge de VTEX.
 
-![Carrefour1](//images.contentful.com/alneenqid6w5/3J1VMlsGsMswagSeG2y0EK/d054fac671b13f5dca7f627aa5121c97/Carrefour1.png)
+![Carrefour1](https://images.contentful.com/alneenqid6w5/3J1VMlsGsMswagSeG2y0EK/d054fac671b13f5dca7f627aa5121c97/Carrefour1.png)
 
 ### Configurando la integración en el Bridge
 
diff --git a/docs/tutorials/es/integrating-with-farmacias-app.md b/docs/tutorials/es/integrating-with-farmacias-app.md
index 7fd437fae..0dd1ee3ad 100644
--- a/docs/tutorials/es/integrating-with-farmacias-app.md
+++ b/docs/tutorials/es/integrating-with-farmacias-app.md
@@ -35,7 +35,7 @@ _**Atención**: hay que llenar estos campos exactamente según lo descrito arrib
 
 El **perfil de acceso** será: IntegrationProfile-Fulfillment_Oms, IntegrationProfile-Fulfillment_Gateway
 
-![Farmacias1](//images.contentful.com/alneenqid6w5/2rkEOHXVIEk4q8WiOWCsSs/46449655d8c76e01903a29ec6ed5492d/Farmacias1.png)
+![Farmacias1](https://images.contentful.com/alneenqid6w5/2rkEOHXVIEk4q8WiOWCsSs/46449655d8c76e01903a29ec6ed5492d/Farmacias1.png)
 
 Finalmente, haga clic en el botón **Guardar**.
 
@@ -51,7 +51,7 @@ Después, será necesario:
 Finalmente, debe realizarse el registro del afiliado, que sirve como identificación única del marketplace en su tienda. Para hacerlo, siga los pasos a continuación:
 
 1. Acceda al módulo **Gestión de Pedidos**;
-2. Haga clic en el botón **Configuración**;![Farmacias2](//images.contentful.com/alneenqid6w5/7Mekt0KzpmaS4M4uoEu2kC/d0b13138a044072b6ba2c7c89808eacc/Farmacias2.png)
+2. Haga clic en el botón **Configuración**;![Farmacias2](https://images.contentful.com/alneenqid6w5/7Mekt0KzpmaS4M4uoEu2kC/d0b13138a044072b6ba2c7c89808eacc/Farmacias2.png)
 3. Haga clic en la pestaña **Afiliados**;
 4. Haga clic en el botón **Nuevo afiliado**;
 5. Llene los campos de la siguiente forma:
@@ -62,7 +62,7 @@ Finalmente, debe realizarse el registro del afiliado, que sirve como identificac
 **Email de follow up**: _email de la persona responsable de la integración_;
 **Endpoint de Search**: https://integrador.farmaciasapp.com.br/Vtex/api/notification
 
-![Farmacias3](//images.contentful.com/alneenqid6w5/6pnQjxLuhO8cUogU6oYoig/953a840b59416974f9a3baeff39d47cd/Farmacias3.png)
+![Farmacias3](https://images.contentful.com/alneenqid6w5/6pnQjxLuhO8cUogU6oYoig/953a840b59416974f9a3baeff39d47cd/Farmacias3.png)
 
 _Cuando se procesen los pagos a través del Farmácias App, la opción **Usar mi medio de pago** debe estar desmarcada. Marque esa opción sólo para pagos procesados en ambientes diferentes, como pagos procesados en la plataforma VTEX._
 
diff --git a/docs/tutorials/es/integration-guide-for-erps-orders.md b/docs/tutorials/es/integration-guide-for-erps-orders.md
index f2c943670..c021ffea8 100644
--- a/docs/tutorials/es/integration-guide-for-erps-orders.md
+++ b/docs/tutorials/es/integration-guide-for-erps-orders.md
@@ -25,7 +25,7 @@ En este artículo, usted encontrará el método principal para la entrada de los
 
 La integración de un pedido comprende cuatro momentos distintos, cada uno de ellos siendo un pequeño proceso por sí solo.
 
-![ERP Orders 1](//images.contentful.com/alneenqid6w5/7MtCGP7jpKOO2gKa8muGwO/481c6346e0d216f1cbe0588dc79eb617/ERP_Orders_1.png) 
+![ERP Orders 1](https://images.contentful.com/alneenqid6w5/7MtCGP7jpKOO2gKa8muGwO/481c6346e0d216f1cbe0588dc79eb617/ERP_Orders_1.png) 
 
 # Pasos de la integración de pedidos
 
@@ -39,7 +39,7 @@ Después de decidir que es hora de llevar un pedido a su plataforma de fulfillme
 
 Al final, para los pedidos procesados, usted envía al OMS un mensaje de "Start Handling".
 
-![ERP Orders 2](//images.contentful.com/alneenqid6w5/3SUWupt48gSG2iqM2q8qEA/28a578fa22944fac74f7f9d9121506ca/orders-integration-download.png) 
+![ERP Orders 2](https://images.contentful.com/alneenqid6w5/3SUWupt48gSG2iqM2q8qEA/28a578fa22944fac74f7f9d9121506ca/orders-integration-download.png) 
 
 ### Llamadas de API
 
@@ -111,7 +111,7 @@ Ahora el pedido está siendo procesado por su plataforma de fulfillment. Durante
 
 Cuando esté listo para la entrega del pedido, es el momento de informarle a VTEX. Así, la autorización de pago podrá ser capturada y el consumidor será notificado sobre el progreso.
 
-![ERP Orders 3](//images.contentful.com/alneenqid6w5/5UGtFvC0UwoEoEcqQk8kGa/249a691293a7f195257f5c161565cf5c/ERP_Orders_3.png)
+![ERP Orders 3](https://images.contentful.com/alneenqid6w5/5UGtFvC0UwoEoEcqQk8kGa/249a691293a7f195257f5c161565cf5c/ERP_Orders_3.png)
 
 ### Llamadas de API
 
@@ -187,7 +187,7 @@ No hay límite para el número de mensajes de rastreo que se pueden agregar a un
 
 Es importante resaltar que esa información es, en realidad, un conjunto de atributos de una factura. Por lo tanto, puede ser enviada junto a la factura, en el momento de envío a la tienda, si usted tiene esa información en esa etapa.
 
-![ERP Orders 4](//images.contentful.com/alneenqid6w5/1v0Mk0y5a0uAmgcGmgAks4/6d416ec4b79faa89330d683a32c6905c/ERP_Orders_4.png) 
+![ERP Orders 4](https://images.contentful.com/alneenqid6w5/1v0Mk0y5a0uAmgcGmgAks4/6d416ec4b79faa89330d683a32c6905c/ERP_Orders_4.png) 
 
 ### Llamadas de API
 
diff --git a/docs/tutorials/es/integration-interfaces.md b/docs/tutorials/es/integration-interfaces.md
index d1041131b..a370c42ef 100644
--- a/docs/tutorials/es/integration-interfaces.md
+++ b/docs/tutorials/es/integration-interfaces.md
@@ -19,7 +19,7 @@ La integración con un ERP le permite realizar el control de stock con relación
 
 En el sistema de VTEX, usted conseguirá realizar las integraciones de su ERP por diferentes Interfaces: __API REST__ (lenguaje en JSON) y __Web Service__ (lenguaje en SOAP - XML) - que está en desuso.
 
-![Interface de integração ES](//images.ctfassets.net/alneenqid6w5/1qC18Uk3YAIWiesmEco8us/72aaeac0b223b07ab69d2d6df38f2eb2/Interface_de_integra____o.png)
+![Interface de integração ES](https://images.ctfassets.net/alneenqid6w5/1qC18Uk3YAIWiesmEco8us/72aaeac0b223b07ab69d2d6df38f2eb2/Interface_de_integra____o.png)
 
 Además del ERP, para que el intercambio de información ocurra, es necesario que exista un sistema para hacer la comunicación entre el ERP y VTEX. Este sistema se llama __Integrador__. Generalmente, el propio ERP desarrolla su integrador, pero también puede ser desarrollado por la propia tienda o por una agencia contratada por la tienda.
 
diff --git a/docs/tutorials/es/integration-with-google-tag-manager.md b/docs/tutorials/es/integration-with-google-tag-manager.md
index f481e3185..fb2cd89a1 100644
--- a/docs/tutorials/es/integration-with-google-tag-manager.md
+++ b/docs/tutorials/es/integration-with-google-tag-manager.md
@@ -48,7 +48,7 @@ Después, debes configurar el código de identificación de la tienda en Tag Man
 4. En el campo __Google Tag Manager__, ingresa el código de identificación de la tienda, en el formato `GTM-XXXX`, ilustrado en la imagen siguiente.
 5. Haz clic en `Guardar`.
 
-![Google Tag Manager](//images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/3689bbdd56348b8bfd8bb9689db86434/Google_Tag_Manager_-_ES.PNG)
+![Google Tag Manager](https://images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/3689bbdd56348b8bfd8bb9689db86434/Google_Tag_Manager_-_ES.PNG)
 
 Para verificar eventos (activadores) y variables disponibles en las páginas que se utilizarán en las etiquetas, puedes utilizar el modo de vista previa de Google Tag Manager. Consulta este artículo en [Google Tag Manager](https://support.google.com/tagmanager/answer/6261285?hl=es) para más información.
 
diff --git a/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
index 27f0a7f28..3c0724f12 100644
--- a/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
@@ -32,7 +32,7 @@ Las sugerencias se muestran en dos categorías en la lista de sinónimos, como s
 * **Nuevas sugerencias:** son aquellas generadas por la plataforma que aún no se han revisado.
 * **Sugerencias guardadas:** son aquellas que se guardaron para su posterior revisión, tal como se describe en el paso 5 de la sección [Revisar sugerencias](#revisar-sugestoes).
 
-![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
+![synonym-suggestion-list-es](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
 
 Puedes revisar las sugerencias generadas y elegir guardar para más tarde, rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
 
@@ -48,7 +48,7 @@ Sigue las instrucciones para visualizar las sugerencias de sinónimos y definir
 
 4. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
 
-   ![synonym-suggestion-es](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
+   ![synonym-suggestion-es](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
 
 4. Para revisar cada sugerencia, elige una de las siguientes opciones:
     * <i class="fas fa-bookmark"></i> **Guardar para más tarde:** remueve la sugerencia del recuento **Nuevas sugerencias** y la almacena en **Sugerencias guardadas**. Para analizarla posteriormente, haz clic en `Revisar`.
diff --git a/docs/tutorials/es/intelligent-synonyms.md b/docs/tutorials/es/intelligent-synonyms.md
index ba8f5559f..b59ea3187 100644
--- a/docs/tutorials/es/intelligent-synonyms.md
+++ b/docs/tutorials/es/intelligent-synonyms.md
@@ -32,7 +32,7 @@ Las sugerencias se muestran en dos categorías en la lista de sinónimos, como s
 * **Nuevas sugerencias:** son aquellas generadas por la plataforma que aún no se han revisado.
 * **Sugerencias guardadas:** son aquellas que se guardaron para su posterior revisión, tal como se describe en el paso 5 de la sección [Revisar sugerencias](#revisar-sugestoes).
 
-![synonym-suggestion-list-es](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
+![synonym-suggestion-list-es](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/71bad7a9a6282275bc001b9c2437d2fd/synonym-suggestion-list-es.png)
 
 Puedes revisar las sugerencias generadas y elegir guardar para más tarde, rechazar, editar o aprobar. Consulta el paso a paso en la siguiente sección.
 
@@ -48,7 +48,7 @@ Sigue las instrucciones para visualizar las sugerencias de sinónimos y definir
 
 4. Verás un modal con la primera sugerencia de sinónimo. Cada sugerencia indica el término buscado y el término que se agregará como sinónimo, y también el número de veces que los clientes de tu tienda reescribieron el término original por el segundo término en los últimos 30 días.
 
-   ![synonym-suggestion-es](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
+   ![synonym-suggestion-es](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/78ebffca01e145e64411537d176ada30/synonym-suggestion-es.png)
 
 4. Para revisar cada sugerencia, elige una de las siguientes opciones:
     * <i class="fas fa-bookmark"></i> **Guardar para más tarde:** remueve la sugerencia del recuento **Nuevas sugerencias** y la almacena en **Sugerencias guardadas**. Para analizarla posteriormente, haz clic en `Revisar`.
diff --git a/docs/tutorials/es/interacting-with-masterdata-through-graphql.md b/docs/tutorials/es/interacting-with-masterdata-through-graphql.md
index 4cf4e95c8..73340edaf 100644
--- a/docs/tutorials/es/interacting-with-masterdata-through-graphql.md
+++ b/docs/tutorials/es/interacting-with-masterdata-through-graphql.md
@@ -26,7 +26,7 @@ Comienze asegurándose de tener la versión más reciente de la VTEX CLI y clona
 
 Ejecute el comando `vtex init` y seleccione `graphql get-started`.
 
-![Screen Shot 2019-01-16 at 15.00.29](//images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
+![Screen Shot 2019-01-16 at 15.00.29](https://images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
 
 Vamos a usar su estructura básica y adaptarla a nuestras necesidades.
 
@@ -157,15 +157,15 @@ Abra el Postman y escriba la siguiente búsqueda:
 
 Seleccione un ID y cópielo. Vamos a pegarlo en nuestra consulta.
 
-![Screen Shot 2019-01-16 at 16.14.31](//images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
+![Screen Shot 2019-01-16 at 16.14.31](https://images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
 
-![Screen Shot 2019-01-16 at 17.34.04](//images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
+![Screen Shot 2019-01-16 at 17.34.04](https://images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
 
 Ahora usted debe ver la luz de salida a la derecha.
 Muy bien! Usted realizó su primera consulta simple en tiempo récord.
 
 Volviendo al terminal, usted puede mirar debajo del capó y percibir el GraphQL resolviendo las consultas, como normalmente usted habría hecho.
-![Screen Shot 2019-01-16 at 16.29.03](//images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
+![Screen Shot 2019-01-16 at 16.29.03](https://images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
 
 **Pero ¿y si queremos buscar utilizando todos los filtros posibles?**
 Vamos a seguir adelante para definir una nueva estructura de consulta y crear un nuevo resolver para manejar los nuevos parámetros.
@@ -279,6 +279,6 @@ query{
 
 ```
 
-![Screen Shot 2019-01-16 at 17.23.00](//images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
+![Screen Shot 2019-01-16 at 17.23.00](https://images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
 
 Y esto es todo :) Happy coding!
diff --git a/docs/tutorials/es/interaction-details.md b/docs/tutorials/es/interaction-details.md
index 6e950dc45..91aac4820 100644
--- a/docs/tutorials/es/interaction-details.md
+++ b/docs/tutorials/es/interaction-details.md
@@ -40,7 +40,7 @@ La página **Detalles de la interacción** cuenta con las siguientes secciones:
 </div>  
 
 ## Encabezado
-![Interaction details PT cabeçalho](//images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/cc97295e6fa0f0d1cfaa76cd755904cb/Interaction_details_ES_cabe__alho.jpg)
+![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/cc97295e6fa0f0d1cfaa76cd755904cb/Interaction_details_ES_cabe__alho.jpg)
 El *encabezado* contiene la información principal del anuncio para la visualización rápida, como nombre del SKU, logo del canal al que fue enviado, su ID en VTEX e ID en el canal.
 
 ## Resultado de la interacción
@@ -49,23 +49,23 @@ Las interacciones, o actualizaciones de un [anuncio](https://help.vtex.com/es/tu
 El bloque *Resultado de la interacción* informa el efecto que la interacción tuvo sobre el anuncio, calculado a partir de la combinación de registros que forman la interacción. El resultado de una interacción permite que el sistema determine el status del anuncio, indicando si fue posible enviarlo o sincronizarlo al canal, o no. Los resultados de la interacción incluyen:
 
 ### Resultado: Satisfactorio
-![Interaction details PT resultado sucesso](//images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/35d67af0da667655b5643e3509ccc427/Interaction_details_ES_resultado_sucesso.jpg)
+![Interaction details PT resultado sucesso](https://images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/35d67af0da667655b5643e3509ccc427/Interaction_details_ES_resultado_sucesso.jpg)
 El status de una interacción es *Satisfactorio* cuando las interacciones cumplen con su efecto esperado. Eso significa que el anuncio se pudo enviar al canal correctamente, o que las interacciones generaron atualizaciones en un anuncio en términos de precio, stock o catálogo. 
 
 ### Resultado: Falla
-![Interaction details PT resultado falha](//images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/8af1ee83533f4108433214dc2c3f0964/Interaction_details_ES_resultado_falha.jpg)
+![Interaction details PT resultado falha](https://images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/8af1ee83533f4108433214dc2c3f0964/Interaction_details_ES_resultado_falha.jpg)
 El status de una interacción es *Falla* cuando las interacciones no se realizan debido a un error identificado por el sistema. Los resultados de ese tipo acaban generando el status *Con error* en un anuncio, impidiendo que el anuncio se envíe o actualice correctamente en el canal.  En caso de que el resultado de la interacción sea *Falla*, el bloque indica una lista con las fallas detectadas y donde cada una se puede expandir para que el seller acceda a más información sobre lo que ocurrió. 
 
 ### Resultado: Notificación
-![Interaction details PT resultado aviso](//images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/28e3c2b39fc2740880338efcfb3d2729/Interaction_details_ES_resultado_aviso.jpg)
+![Interaction details PT resultado aviso](https://images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/28e3c2b39fc2740880338efcfb3d2729/Interaction_details_ES_resultado_aviso.jpg)
 El status de una interacción es *Notificación* cuando hay interacciones que dan una mayor visibilidad a las etapas que se produjeron en el proceso de envío y actualización de un anuncio, pero que no generaron actualizaciones como tal. 
 
 ### Resultado: Procesando
-![Interaction details PT resultado processing](//images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/d4f5b881db18ed358e6386c06e4cc2a8/Interaction_details_ES_resultado_processing.jpg)
+![Interaction details PT resultado processing](https://images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/d4f5b881db18ed358e6386c06e4cc2a8/Interaction_details_ES_resultado_processing.jpg)
 El status de una interacción es *Procesando* cuando una interacción no fue finalizada y aún debe recibir más acciones. Es un status transitorio, considerando que cuando un evento se cierra, su resultado solo puede ser `satisfactorio`, `falla`, o `notificación`.
 
 ## Línea de tiempo
-![Interaction details ES linha do tempo](//images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/b95c1753d211144af9336c13bd2002bf/Interaction_details_ES_linha_do_tempo.jpg)
+![Interaction details ES linha do tempo](https://images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/b95c1753d211144af9336c13bd2002bf/Interaction_details_ES_linha_do_tempo.jpg)
 El sistema abre una interacción para iniciar una actualización y contiene una serie de registros para realizar las acciones necesarias para que eso suceda. 
 
 La línea de tiempo de la página **Detalles de la interacción** organiza cronológicamente los registros que se producen en cada interacción, e están disponibles para consulta durante diez días. El sistema cierra la interacción cuando cumple su objetivo y no hay más registros por realizar. La línea de tiempo de la interacción muestra los siguientes datos: 
diff --git a/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
index 765226eae..f1e2029db 100644
--- a/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
@@ -26,7 +26,7 @@ El siguiente conjunto de datos es presentado en la pantalla de __Todos los pedid
 
 Al lado de cada uno de esos valores, se puede ver un porcentaje que representa la variación relativa a los pedidos de hoy.
 
-![order-metric-es](//images.ctfassets.net/alneenqid6w5/39O5tZyXnGgEsYccEYcQiS/d790e5a55b8f10f9296ed2dfa8bf2328/order-metric-es.png)
+![order-metric-es](https://images.ctfassets.net/alneenqid6w5/39O5tZyXnGgEsYccEYcQiS/d790e5a55b8f10f9296ed2dfa8bf2328/order-metric-es.png)
 
 En el screenshot de las métricas arriba, podemos ver la siguiente información:
 
diff --git a/docs/tutorials/es/introduction-to-vtex-apis.md b/docs/tutorials/es/introduction-to-vtex-apis.md
index 140463a5d..017e0d497 100644
--- a/docs/tutorials/es/introduction-to-vtex-apis.md
+++ b/docs/tutorials/es/introduction-to-vtex-apis.md
@@ -62,7 +62,7 @@ En ella deben incluirse:
  
 En el Postman, debe insertarse la URL en el campo destacado a continuación:
 
-![APIs1](//images.contentful.com/alneenqid6w5/f53Sv9BCZqK4EI0sYmW8A/63e512b825d47daa2f685ae5bb9df553/APIs1.png)
+![APIs1](https://images.contentful.com/alneenqid6w5/f53Sv9BCZqK4EI0sYmW8A/63e512b825d47daa2f685ae5bb9df553/APIs1.png)
 
 ****
 
@@ -80,7 +80,7 @@ Sin embargo, usted no necesita deducir esto solo. Al poner a disposición una AP
  
 En el Postman, el método es seleccionado a la izquierda del campo de URL.
 
-![APIs2](//images.contentful.com/alneenqid6w5/wDClzNRJDiCE6OKecOAs4/8545dbce3bc2ee546b8cf497750360b5/APIs2.png)
+![APIs2](https://images.contentful.com/alneenqid6w5/wDClzNRJDiCE6OKecOAs4/8545dbce3bc2ee546b8cf497750360b5/APIs2.png)
 
 
 ****
@@ -96,7 +96,7 @@ En el postman, la AppKey y el AppToken deben insertarse en la pestaña **Headers
 
 Para saber como generar su AppKey y su AppToken, ler el artículo [Crear appKey y appToken para autenticar las integraciones](/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones).
 
-![APIs3](//images.contentful.com/alneenqid6w5/4z9W9DYJEcYa2WGIoSceEE/166d8adc70a8176af1a7fb04e5cdbb65/APIs3.png)
+![APIs3](https://images.contentful.com/alneenqid6w5/4z9W9DYJEcYa2WGIoSceEE/166d8adc70a8176af1a7fb04e5cdbb65/APIs3.png)
 
 ****
 
@@ -117,11 +117,11 @@ Las APIs de VTEX están disponibles en nuestro Help Center, en la sección [Deve
  
 Ellas quedan divididas por módulo o funcionalidad. Ingresando a uno de éstos, usted encuentra las APIs correspondientes, cada una de ellas acompañada de la indicación del método correcto, URL y Headers. Algunas APIs tienen también el código que debe pasarse en el Body.
  
-![APIs4](//images.contentful.com/alneenqid6w5/1JZCBHsm6UGS2EwuGqoGm4/a61e000b81acd2f06a1021f70c12e31b/APIs4.png)
+![APIs4](https://images.contentful.com/alneenqid6w5/1JZCBHsm6UGS2EwuGqoGm4/a61e000b81acd2f06a1021f70c12e31b/APIs4.png)
  
 A la derecha de esas indicaciones, el Postman exhibe, para cada API, un Sample Request. De acuerdo con el lenguaje elegido en la caja de selección por encima de él, el Sample Request muestra cómo sería la aplicación de la solicitud en el código.
 
-![sample request](//images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
+![sample request](https://images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
  
 Para algunas APIs, hay también una Sample Response, que es un ejemplo de respuesta a aquel request.
  
diff --git a/docs/tutorials/es/kit-registration.md b/docs/tutorials/es/kit-registration.md
index f894bb785..5c821c679 100644
--- a/docs/tutorials/es/kit-registration.md
+++ b/docs/tutorials/es/kit-registration.md
@@ -26,7 +26,7 @@ Un kit puede permitir o no que sus componentes se vendan por separado, entienda
 
 Para configurar el Kit es necesario que los productos que harán parte de este – sus componentes – ya estén creados. Como en el siguiente ejemplo:
 
-![01-Componentes ES](//images.ctfassets.net/alneenqid6w5/1cgf40SaniUaYUIg4wuKyo/0f124e3ab1d1f881f5d0fe225b64d746/01-components_ES.png)
+![01-Componentes ES](https://images.ctfassets.net/alneenqid6w5/1cgf40SaniUaYUIg4wuKyo/0f124e3ab1d1f881f5d0fe225b64d746/01-components_ES.png)
 
 Luego de crear los productos componentes, podemos continuar con la configuración del Kit.
 
@@ -38,7 +38,7 @@ Luego de crear los productos componentes, podemos continuar con la configuració
 5. Si quiere un Kit Look, haga clic en la opción __Kit con ítems vendidos por separado__.
 6. Haga clic en `Guardar`.
 
-![02-kit ES](//images.ctfassets.net/alneenqid6w5/6PUdHiV1UAuMC6A80QYOQI/e14209f28e53d84e8f1af4ecb6261bac/02-kit_ES.png)
+![02-kit ES](https://images.ctfassets.net/alneenqid6w5/6PUdHiV1UAuMC6A80QYOQI/e14209f28e53d84e8f1af4ecb6261bac/02-kit_ES.png)
 
 ## Asociar componentes
 
@@ -53,9 +53,9 @@ Después de crear el producto que se convertirá en el Kit, deben asociarse los
 7. Rellene el precio unitario del SKU dentro del Kit.
 6. Haga clic en `Guardar`.
 
-![03-agregar componente al Kit ES](//images.ctfassets.net/alneenqid6w5/2ghV5EOOAQ4kQOIomsmusE/5f7f3a94ffb0df4b4cdb74f71373445a/03-add_component_to_kit_ES.gif)
+![03-agregar componente al Kit ES](https://images.ctfassets.net/alneenqid6w5/2ghV5EOOAQ4kQOIomsmusE/5f7f3a94ffb0df4b4cdb74f71373445a/03-add_component_to_kit_ES.gif)
 
-![04-Kit en el carrito  TODO](//images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
+![04-Kit en el carrito  TODO](https://images.ctfassets.net/alneenqid6w5/4yJVbkTnDyIC2c682UskYw/8cad5dc5512f49e73a10abb31184ba8e/04-kit_in_cart_ALL.png)
 
 ## Peso del Kit
 
@@ -84,7 +84,7 @@ También podrá modificar únicamente el precio final del Kit directamente desde
 Pero tenga en cuenta que al cambiar cualquier componente se generará un nuevo precio final, actualizando lo que se había registrado anteriormente.
 Alterar solo el precio final no actualiza el precio de los componentes.
 
-![06-Lista de precios ES](//images.ctfassets.net/alneenqid6w5/4lM2ecWDE40Ooa44scKIq6/6fa14fb364430e3bfc2fa3fff64c8e96/06-price_list_ES.png)
+![06-Lista de precios ES](https://images.ctfassets.net/alneenqid6w5/4lM2ecWDE40Ooa44scKIq6/6fa14fb364430e3bfc2fa3fff64c8e96/06-price_list_ES.png)
 
 ### Más información
 
diff --git a/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
index bf506f653..87a2d626a 100644
--- a/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
+++ b/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
@@ -35,7 +35,7 @@ Para configurar el lead time vía API, accede a <a href="https://developers.vtex
 
 Cuando se configura, el lead time es un tiempo adicional que compone el plazo de envío del pedido que se muestra al cliente en el checkout. En la imagen a continuación, se muestran los elementos que componen el plazo total:
 
-![lead_time_image_total_time_ES](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
+![lead_time_image_total_time_ES](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/f9610838cce53ee740054bee68e634d1/lead_time_image_total_time_ES.png)
 
 * **Lead time:** cantidad de tiempo configurable para el SKU de un almacén. Este periodo puede corresponder al tiempo de procesamiento o fabricación del ítem, por ejemplo. Esta configuración es opcional y se establece en cero días de forma predeterminada.
 * [Tiempo de almacén:](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137) tiempo que tarda el SKU en pasar del almacén al [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Este ajuste es obligatorio, pero puedes configurar el tiempo como cero.
@@ -80,7 +80,7 @@ Para configurar el lead time de un SKU sigue los pasos a continuación:
 1. En el Admin VTEX, accede a **Catálogo > Stock > Gestión del stock**, o ingresa **Gestión del stock** en la barra de búsqueda de la parte superior de la página.
 2. Selecciona el SKU que deseas configurar. Puedes utilizar la barra y los filtros de búsqueda.
 3. Ingresa el número de días en la fila del SKU y en la columna **Lead time (días)**.
-  ![lead_time_inventory_management_ES](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
+  ![lead_time_inventory_management_ES](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
 4. Haz clic en `Guardar` en la parte inferior de la página.
 
 <div class = "alert alert-info">
diff --git a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
index c0a026e3c..f8998892d 100644
--- a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
+++ b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -48,7 +48,7 @@ Después de crear el clúster, debe crear la regla en la política comercial de
 3. En el campo de la **Regla condicional**, rellene el valor **NombreDelCluster=”true”**. Tenga en cuenta que el valor **NombreDelCluster** debe de ser cambiado por el nombre del campo en la entidad de datos.
 4. Haga click en el botón **Guardar**.
 
-![Catálogo ES](//images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/d748769c9e6b3aa2f001942ed51d6e53/pol__ticas_comerciais_ES.png)
+![Catálogo ES](https://images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/d748769c9e6b3aa2f001942ed51d6e53/pol__ticas_comerciais_ES.png)
 
 En la configuración anterior, sólo los clientes con el valor verdadero (utilizando un campo booleano - cuando los datos son verdaderos o falsos) tendrán acceso al sitio.
 
diff --git a/docs/tutorials/es/linking-an-account-name-to-a-website-binding.md b/docs/tutorials/es/linking-an-account-name-to-a-website-binding.md
index 0bc3796f8..c1f8ab955 100644
--- a/docs/tutorials/es/linking-an-account-name-to-a-website-binding.md
+++ b/docs/tutorials/es/linking-an-account-name-to-a-website-binding.md
@@ -20,9 +20,9 @@ Una de las primeras acciones que usted necesita realizar en su web site es enlaz
 1. En el Admin VTEX, accede a **Storefront > Layout**.
 2. Haga clic en la carpeta __CMS__.
 3. Haga clic en la carpeta __Sites and channels__.
-4. Haga clic en el Website deseado.![websites](//images.contentful.com/alneenqid6w5/56BRjkYWyIwKogAI0oMmSM/0910a749d03b6fd8d596ce6361a21045/websites.png)
+4. Haga clic en el Website deseado.![websites](https://images.contentful.com/alneenqid6w5/56BRjkYWyIwKogAI0oMmSM/0910a749d03b6fd8d596ce6361a21045/websites.png)
 5. Haga clic en __Save Website__.
-6. Haga clic en __Add__.![addBinding](//images.contentful.com/alneenqid6w5/r0P8ZE9LNesKoeGewcWOu/527511bc3ae48875fe1a6421a1db5f42/addBinding.png)
-7. Seleccione el nombre de la tienda.![chooseBinding](//images.contentful.com/alneenqid6w5/3nFPaDlnaEG2EqIMM8gCe0/188754ebaa172cef01a9212eea168e46/chooseBinding.png)
-8. Marque la política comercial o las políticas comerciales que quedarán vinculadas a esa tienda.![bindingSalesPolicy](//images.contentful.com/alneenqid6w5/5FFxnelVTyCu04a6EkiEkS/30905c7f368a1393100f118fd70fcb02/bindingSalesPolicy.png)
+6. Haga clic en __Add__.![addBinding](https://images.contentful.com/alneenqid6w5/r0P8ZE9LNesKoeGewcWOu/527511bc3ae48875fe1a6421a1db5f42/addBinding.png)
+7. Seleccione el nombre de la tienda.![chooseBinding](https://images.contentful.com/alneenqid6w5/3nFPaDlnaEG2EqIMM8gCe0/188754ebaa172cef01a9212eea168e46/chooseBinding.png)
+8. Marque la política comercial o las políticas comerciales que quedarán vinculadas a esa tienda.![bindingSalesPolicy](https://images.contentful.com/alneenqid6w5/5FFxnelVTyCu04a6EkiEkS/30905c7f368a1393100f118fd70fcb02/bindingSalesPolicy.png)
 9. Haga clic en __Save Binding__.
diff --git a/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md b/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md
index 526a55412..eddeee1ae 100644
--- a/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md
+++ b/docs/tutorials/es/linking-urls-to-banners-using-the-site-editor.md
@@ -19,7 +19,7 @@ Puede configurar uno de los banners de su tienda para un redireccionamiento de p
 
 ## URLs Internas
 
-![url-interna](//images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3d5a31e246e7525d91009ed3f1e77af1/image5.png)
+![url-interna](https://images.ctfassets.net/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/3d5a31e246e7525d91009ed3f1e77af1/image5.png)
 
 1. En el Admin VTEX, accede a **Storefront > Site Editor**.
 2. Seleccione el bloque __Carrusel__ deseado y elija el banner cuyo contenido será editado.
@@ -33,7 +33,7 @@ Puede configurar uno de los banners de su tienda para un redireccionamiento de p
 
 ## URLs Externas
 
-![url-externa-es](//images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/42317522340b78b7ce0a36ef8bb8163d/image3.png)
+![url-externa-es](https://images.ctfassets.net/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/42317522340b78b7ce0a36ef8bb8163d/image3.png)
 
 1. En el Admin VTEX, accede a **Storefront > Site Editor**.
 2.  Seleccione el bloque __Carrusel__ deseado y elija el banner cuyo contenido será editado.
diff --git a/docs/tutorials/es/list-the-account-workspaces.md b/docs/tutorials/es/list-the-account-workspaces.md
index d21a5a67a..5ad75b770 100644
--- a/docs/tutorials/es/list-the-account-workspaces.md
+++ b/docs/tutorials/es/list-the-account-workspaces.md
@@ -21,7 +21,7 @@ Para ver los workspaces que existen actualmente en una cuenta, basta con usar el
 
 Vea el siguiente ejemplo:
 
-![workspace list](//images.contentful.com/alneenqid6w5/2au4D7r6YkmskO0Ko8esC6/aa635baf0e6f543c0e08ee2613e20127/workspace_list.png)
+![workspace list](https://images.contentful.com/alneenqid6w5/2au4D7r6YkmskO0Ko8esC6/aa635baf0e6f543c0e08ee2613e20127/workspace_list.png)
 
 Las columnas que aparecen son las siguientes:
 
diff --git a/docs/tutorials/es/listing-apps-installed-in-the-store.md b/docs/tutorials/es/listing-apps-installed-in-the-store.md
index bfa7c3c42..ef72e4041 100644
--- a/docs/tutorials/es/listing-apps-installed-in-the-store.md
+++ b/docs/tutorials/es/listing-apps-installed-in-the-store.md
@@ -26,6 +26,6 @@ Usted verá una tabla con las siguientes columnas:
 - __Version__: versión de la aplicación.
 - __Linked__: muestra si la aplicación está o no vinculada ("vtex link").
 
-![appList](//images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
+![appList](https://images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
 
 No hay límite de aplicaciones que se pueden crear para una cuenta.
diff --git a/docs/tutorials/es/loading-dock.md b/docs/tutorials/es/loading-dock.md
index 98fb5c453..627e64e9b 100644
--- a/docs/tutorials/es/loading-dock.md
+++ b/docs/tutorials/es/loading-dock.md
@@ -20,7 +20,7 @@ El muelle forma parte del sistema logístico y representa un punto intermedio en
 
 En VTEX, el muelle es un intermediario entre el almacenamiento de ítems y la entrega de los pedidos de tu negocio. Es a través del muelle que se produce la integración de las partes necesarias para la logística de tu tienda, a saber: el [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb), la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![Doca ES](//images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/e3f7d64c72c143e395895e7bf2865663/Doca_ES.svg)
+![Doca ES](https://images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/e3f7d64c72c143e395895e7bf2865663/Doca_ES.svg)
 
 <div class = "alert alert-info">
 El almacén es el espacio físico de almacenamiento de los productos vendidos por la tienda; la política comercial es la configuración de las estrategias de venta de la tienda; y la política de envío es un conjunto de reglas que definen las opciones y condiciones de envío.
diff --git a/docs/tutorials/es/logging-in-to-the-account-with-vtex-io.md b/docs/tutorials/es/logging-in-to-the-account-with-vtex-io.md
index 6959df476..04db9af98 100644
--- a/docs/tutorials/es/logging-in-to-the-account-with-vtex-io.md
+++ b/docs/tutorials/es/logging-in-to-the-account-with-vtex-io.md
@@ -19,6 +19,6 @@ Para acceder a la cuenta de la tienda, entre en el terminal y escriba `vtex logi
 
 El terminal solicitará el Account, es decir, el nombre de la cuenta de la tienda.
 
-![vtex login](//images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
+![vtex login](https://images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
 
 Después de insertar la cuenta, escriba la contraseña si es necesario y listo. Usted ha entrado en su cuenta!
diff --git a/docs/tutorials/es/logistics-in-the-grocery-segment-supermarkets.md b/docs/tutorials/es/logistics-in-the-grocery-segment-supermarkets.md
index f9f67379b..7db1281dd 100644
--- a/docs/tutorials/es/logistics-in-the-grocery-segment-supermarkets.md
+++ b/docs/tutorials/es/logistics-in-the-grocery-segment-supermarkets.md
@@ -27,7 +27,7 @@ El fulfillment nada más es que el proceso del análisis de los pedidos, separac
 
 En la mayoría de las operaciones convencionales de eCommerce, tenemos un almacén que representa el inventario. Ya en la mayoría de las operaciones de grocery, ese almacén no es practicado debido a su capacidad de perecer, rápido detrimento de las mercancías (validez) y la gran variedad del mix de productos.
 
-![](//images.contentful.com/alneenqid6w5/5VsYaqLOz6iq2Q6KEGiOIw/ccca0432aef12d539de3d6d9301383df/mapaARMAZEM1.jpg)
+![](https://images.contentful.com/alneenqid6w5/5VsYaqLOz6iq2Q6KEGiOIw/ccca0432aef12d539de3d6d9301383df/mapaARMAZEM1.jpg)
 
 En este contexto, para la existencia de un almacén que represente el inventario es prácticamente necesario el doble del espacio físico y un gran flujo de pedidos para desagüe antes del detrimento de los productos.
 
@@ -53,7 +53,7 @@ A partir de volúmenes medianos (superior a 30 pedidos diarios), el método de p
 1. Se agrupan todos los productos, sin embargo, sin distinción de pedidos. Reduciendo, así, los movimientos de entre las direcciones de las mercancías.
 2. Después de la separación de los productos, envíelos a un área donde se montan los pedidos. Es posible realizar esas olas por transportadora, rutas, muelles o lote.
 
-![](//images.contentful.com/alneenqid6w5/5rrGJF8WL60uOmgeEia08o/5b66179fe04f4fd6c1cddcd9c12f774f/pickingonda2.jpg)
+![](https://images.contentful.com/alneenqid6w5/5rrGJF8WL60uOmgeEia08o/5b66179fe04f4fd6c1cddcd9c12f774f/pickingonda2.jpg)
 
 ## Picking _por ola lote_ favorece el Packing
 
@@ -67,7 +67,7 @@ Debido a los distintos tipos de mercancías vendibles en el grocery, podemos atr
 6. Frágiles
 7. Congelados
 
-![](//images.contentful.com/alneenqid6w5/tepJVna9uoiKUqeUeOQM4/e9b1e3bca826f9a4bb8f662d34108339/mapa.jpg)
+![](https://images.contentful.com/alneenqid6w5/tepJVna9uoiKUqeUeOQM4/e9b1e3bca826f9a4bb8f662d34108339/mapa.jpg)
 
 Además de que es imprescindible para la separación, el lote es muy importante en el packing, una vez que los tipos de lotes tienen necesidades características y particulares:
 
@@ -91,7 +91,7 @@ __7. Congelados:__ Deben ser transportados en cajas térmicas, en hasta 6 horas
 
 Ejemplos: Helados, postres, empanados, platos listos, hamburguesas, tapas, etc.
 
-![](//images.contentful.com/alneenqid6w5/ptgKUEgHBu4syuiuS46mS/ae31c4cbd90a04a8d0dc19a3e2a6b669/packing.jpg)
+![](https://images.contentful.com/alneenqid6w5/ptgKUEgHBu4syuiuS46mS/ae31c4cbd90a04a8d0dc19a3e2a6b669/packing.jpg)
 
 ## Despacho, transporte y entrega
 
diff --git a/docs/tutorials/es/logistics-module-overview.md b/docs/tutorials/es/logistics-module-overview.md
index bbbd0bc6f..becc1d9d5 100644
--- a/docs/tutorials/es/logistics-module-overview.md
+++ b/docs/tutorials/es/logistics-module-overview.md
@@ -27,7 +27,7 @@ Aquí podremos registrar la relación de **[Almacén](https://help.vtex.com/es/t
 
 Aquí conseguiremos levantar la definición de valores de precio y tiempo de entrega para una determinada rango de código ZIP con relación al peso cúbico del producto, dimensiones, entre otros factores. 
 
-![tarifas-envioES](//images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/c390be3b109d17a73293fc3e7b3a9105/tarifas_envioES.png)
+![tarifas-envioES](https://images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/c390be3b109d17a73293fc3e7b3a9105/tarifas_envioES.png)
 
 - [Tarifas de envío](https://help.vtex.com/es/tutorial/shipping-rates--1Balpg3rv0854udEPedvMM)
 
@@ -37,35 +37,35 @@ Aquí será posible reproducir diversos escenarios para la entrega del producto,
 
 Éste regresará los valores a los Transportistas que atienden a la entrega, las dimensiones y pesos de los productos, el precio de la entrega y el tiempo estimado para que se lleve a cabo. Además de los detalles adicionales sobre los valores del rango del código ZIP, porcentuales que varían de acuerdo con el rango de peso del Producto, volumen, valores adicionales por gramo excedente, costo para la Muelle, factor cúbico y Peso cubado.
 
-![simulador envioES](//images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/6cc66af540be3895ae3af7c9c842dde7/simulador_envioES.png)
+![simulador envioES](https://images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/6cc66af540be3895ae3af7c9c842dde7/simulador_envioES.png)
 - [Simulador de Envío](/es/tutorial/simulacion-de-flete)
 
 ## Inventario
 
 Aquí es posible gestionar y acompañar el movimiento de inventario realizada en los productos de la Tienda. Tanto cuánto las reservas que el producto posee en aquel momento y si ya fueron confirmadas o no.
 
-![gerenciar inventarioES](//images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/7e629760904e66633a91146d74539a2c/gerenciar_inventarioES.png)
+![gerenciar inventarioES](https://images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/7e629760904e66633a91146d74539a2c/gerenciar_inventarioES.png)
 - [Gestionar Inventario](/es/tutorial/gestionar-items-en-inventario)
 
 ## Envío por Geolocalización
 
 Aquí podremos montar “polígonos” para una atención logística específica, normalmente utilizado en zonas rurales e industriales, donde si hay la división por lotes, por ejemplo, o en áreas de riesgo, se hace necesario excluir determinados lugares dentro de una misma región. Su estructuración es dinámica, puede ser fácilmente y literalmente diseñada en el mapa la región a delimitarse. 
 
-![geolocalizaçaoE](//images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/9e7f47a52db4e4234728b526cebdda4f/geolocaliza__aoES.png)
+![geolocalizaçaoE](https://images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/9e7f47a52db4e4234728b526cebdda4f/geolocaliza__aoES.png)
 - [Geolocalización](/es/tutorial/gestionar-geolocalizacion)
 
 ## Puntos de recogida
 
 En Puntos de recogira es posible eliminar, editar y agregar un *Pickup Point*. La feature de Puntos de Rcogida agrega mayor flexibilidad y mejor experiencia de compra para el cliente al permitirle la retirada del pedido en un punto físico.
 
-![pontos retiradaES](//images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/87f4cf5a13e62bccf5980e93e4f440ee/pontos_retiradaES.png)
+![pontos retiradaES](https://images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/87f4cf5a13e62bccf5980e93e4f440ee/pontos_retiradaES.png)
 - [Configurar Puntos de Recogida](http://help.vtex.com/es/tutorial/configurar-puntos-de-recogida-pickup-points)
 
 ## Festivos
 
 Aquí es posible registrar los días que **no** se considerarán útiles para su tienda. El módulo considerará los días festivos registrados en esta sección y estos días no se contabilizarán en el plazo de entrega.
 
-![feriadoES](//images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/8de4f976d60f5668a12c8537cff0b9d8/feriadoES.png)
+![feriadoES](https://images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/8de4f976d60f5668a12c8537cff0b9d8/feriadoES.png)
 - [Registrar Feriados](http://help.vtex.com/es/tutorial/registrar-feriados)
 
 ## Configuraciones Generales
diff --git a/docs/tutorials/es/making-a-master-data-field-editable.md b/docs/tutorials/es/making-a-master-data-field-editable.md
index 233e7f80c..cbf8da79a 100644
--- a/docs/tutorials/es/making-a-master-data-field-editable.md
+++ b/docs/tutorials/es/making-a-master-data-field-editable.md
@@ -23,7 +23,7 @@ Por estándar, no todos los campos tienen esa configuración en el Master Data y
 2. En la aplicación deseada, haga clic en el símbolo de engranaje <i class="fas fa-cog"></i>.
 3. Haga clic en el símbolo de edición <i class="fas fa-edit"></i> sobre el formulario que desea modificar.
 4. Haga clic en la pestaña **Esquemas de layout**.
-5. En el campo deseado, haga clic en el símbolo de edición <i class="fas fa-edit"></i>. ![master-data-modificar-campo-layout](//images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/87a10b5ef1435c74fb86ad88bcf5f54c/Group_1__1_.png)
+5. En el campo deseado, haga clic en el símbolo de edición <i class="fas fa-edit"></i>. ![master-data-modificar-campo-layout](https://images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/87a10b5ef1435c74fb86ad88bcf5f54c/Group_1__1_.png)
 6. Desmarque la opción **Mostrar campo como solo lectura**.
 7. Haga clic en el botón `OK`.
 8. Haga clic en el botón `Guardar`.
diff --git a/docs/tutorials/es/manage-the-sales-comissions-report.md b/docs/tutorials/es/manage-the-sales-comissions-report.md
index c42e88dbe..2115d72e8 100644
--- a/docs/tutorials/es/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/es/manage-the-sales-comissions-report.md
@@ -63,7 +63,7 @@ La creación del informe puede demorarse si el volumen de datos analizados es ex
 Salir de la página no afectará la operación.
 </div>
 
-![Informe de Comisiones](//images.ctfassets.net/alneenqid6w5/1VW72vERimVjQn1cXy5TRM/0bcdb6a335b163625ebee90c5b2ea467/image.png)
+![Informe de Comisiones](https://images.ctfassets.net/alneenqid6w5/1VW72vERimVjQn1cXy5TRM/0bcdb6a335b163625ebee90c5b2ea467/image.png)
 
 Posteriormente, usted también puede descargar el informe recién generado mediante un link de descarga en el listado de informes.
 
diff --git a/docs/tutorials/es/managing-b2b-organizations.md b/docs/tutorials/es/managing-b2b-organizations.md
index 4670598e8..37bb72250 100644
--- a/docs/tutorials/es/managing-b2b-organizations.md
+++ b/docs/tutorials/es/managing-b2b-organizations.md
@@ -48,7 +48,7 @@ Los status son los siguientes:
 
 - **Inactivo:** la organización ha sido desactivada por los administradores de la tienda, por lo que sus usuarios no podrán iniciar sesión.
 
-![Status- ES](//images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/c3472217083893e427bd505924a3317a/Status-_ES.gif)
+![Status- ES](https://images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/c3472217083893e427bd505924a3317a/Status-_ES.gif)
 
 ## Agregar una nueva organización 
 
@@ -72,7 +72,7 @@ Para agregar una nueva organización accede al Admin VTEX, Apps > Organizaciones
     - **Destinatario:** nombre de la persona que recibirá los pedidos en la dirección informada.
 4. Haz clic en el botón `Agregar`.
 
-![Adiconar organização- ES](//images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/5af4c08cc7df3765ee76eb20a1028e93/Adiconar_organiza__o-_ES.gif)
+![Adiconar organização- ES](https://images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/5af4c08cc7df3765ee76eb20a1028e93/Adiconar_organiza__o-_ES.gif)
 
 ## Notificaciones por email
 
diff --git a/docs/tutorials/es/managing-content-versions.md b/docs/tutorials/es/managing-content-versions.md
index a3c4043a1..653c11fba 100644
--- a/docs/tutorials/es/managing-content-versions.md
+++ b/docs/tutorials/es/managing-content-versions.md
@@ -19,7 +19,7 @@ La versión de un bloque es una copia de su contenido en un momento determinado.
 
 Con el recurso **Versiones**, puedes crear, programar y experimentar con diferentes contenidos para un bloque determinado, sin comprometer la versión publicada de tu tienda. Cada bloque disponible en el Site Editor puede tener varias versiones.
 
-![Activating Versions - Versiones](//images.ctfassets.net/alneenqid6w5/2W6NS7tRlWMcUdSunI2ifx/72d7fa2f8c892de190e1e2a62f087490/activating-first-es.png)
+![Activating Versions - Versiones](https://images.ctfassets.net/alneenqid6w5/2W6NS7tRlWMcUdSunI2ifx/72d7fa2f8c892de190e1e2a62f087490/activating-first-es.png)
 
 Ve en las siguientes secciones cómo:
 
diff --git a/docs/tutorials/es/managing-credit-with-customer-credit.md b/docs/tutorials/es/managing-credit-with-customer-credit.md
index dd54d3402..793e13128 100644
--- a/docs/tutorials/es/managing-credit-with-customer-credit.md
+++ b/docs/tutorials/es/managing-credit-with-customer-credit.md
@@ -69,11 +69,11 @@ Para un número reducido de registros, el cliente puede crear las cuentas una po
 - Correo electrónico
 - Límite de crédito
 
-![CustomerCredit1-ES.png h 250?h=250](//images.ctfassets.net/alneenqid6w5/5i2WziEg0CmHZ1yZGSId6q/88cc7d5c78daa86685773aa3ce28da38/CustomerCredit1-ES.png_h_250_h_250)
+![CustomerCredit1-ES.png h 250?h=250](https://images.ctfassets.net/alneenqid6w5/5i2WziEg0CmHZ1yZGSId6q/88cc7d5c78daa86685773aa3ce28da38/CustomerCredit1-ES.png_h_250_h_250)
 
 Si, por otro lado, la base tiene un gran número de cuentas, lo más indicado es importar una plantilla en formato CSV. Puede descargar un modelo de este documento en la sección de Cuentas y rellenarlo con la información necesaria. Para esto, haga clic en el botón __Importar__.
 
-![CustomerCredit2-ES.png?h=250](//images.ctfassets.net/alneenqid6w5/2kPzHCdKHPtdTRISkPpBP5/1d8832a989213974eff370027c655b3c/CustomerCredit2-ES.png_h_250)
+![CustomerCredit2-ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/2kPzHCdKHPtdTRISkPpBP5/1d8832a989213974eff370027c655b3c/CustomerCredit2-ES.png_h_250)
 
 ### Bases grandes
 
diff --git a/docs/tutorials/es/managing-page-and-template-content.md b/docs/tutorials/es/managing-page-and-template-content.md
index 906964b8c..b396db9bd 100644
--- a/docs/tutorials/es/managing-page-and-template-content.md
+++ b/docs/tutorials/es/managing-page-and-template-content.md
@@ -34,7 +34,7 @@ Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una p
 
 1. Seleccione el bloque para el que desea crear nuevo contenido. Puede seleccionarlo utilizando la lista en la esquina derecha o a través de la interfaz:
 
-![seta-interface-es](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
+![seta-interface-es](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
 
 2. Haga clic en `Versiones` en la esquina superior derecha. 
 
@@ -61,7 +61,7 @@ Site Editor aplica la configuración de contenido según la jerarquía de parám
 
 1. Seleccione el bloque cuyo contenido desea sobrescribir. Puede seleccionarlo utilizando la lista en la esquina derecha o a través de la interfaz:
 
-![seta-interface-es](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
+![seta-interface-es](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
 
 2. El contenido disponible corresponde al que está activo ahora. Modifique los campos con los nuevos valores o haga clic en `Versiones` para cambiar la configuración de otro contenido. 
 3. Guarde los cambios.
@@ -74,7 +74,7 @@ No puede actualizar la visibilidad del contenido que se derive del código fuent
 
 1. Seleccione el bloque cuyo contenido desea eliminar o restablecer. Puede seleccionarlo utilizando la lista en la esquina derecha o a través de la interfaz:
 
-![seta-interface-es](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
+![seta-interface-es](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/a3e4c77ec2b3203740be27c7e8f150b7/img-two-es.png)
 
 2. Haga clic en `Versiones` en la esquina superior derecha. 
 3. Haga clic en el menú del contenido deseado (tres puntos verticales). 
diff --git a/docs/tutorials/es/managing-pages.md b/docs/tutorials/es/managing-pages.md
index 50273d960..5f4424668 100644
--- a/docs/tutorials/es/managing-pages.md
+++ b/docs/tutorials/es/managing-pages.md
@@ -19,7 +19,7 @@ En **Headless CMS**, puedes gestionar todas las rutas de URL y los modelos de p
 
 ## Visión general
 
-![New pages - es](//images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/76783d200466eafd99f1972a60068298/novas_pgs._es.png)
+![New pages - es](https://images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/76783d200466eafd99f1972a60068298/novas_pgs._es.png)
 
 | Opção               | Descrição                                              |
 | ------------------- | ------------------------------------------------------ |
@@ -40,7 +40,7 @@ Para crear y gestionar una página, sigue estos pasos:
 2. Haz clic en `Crear documento` y selecciona el tipo de página deseado.
 3. En `Untitled`, nombra la página.
 4. Haz clic en `Secciones` y selecciona la sección deseada.
-![Gif - Páginas](//images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/e7e804bd75245d2571668725dfd82aba/Espanhol_gif_das_p__ginas.gif)
+![Gif - Páginas](https://images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/e7e804bd75245d2571668725dfd82aba/Espanhol_gif_das_p__ginas.gif)
 5. Agrega más secciones si es necesario y llénalas.
 6. Haz clic en `Publicar`.
 
diff --git a/docs/tutorials/es/managing-placeholders.md b/docs/tutorials/es/managing-placeholders.md
index bef342f9d..424a0e711 100644
--- a/docs/tutorials/es/managing-placeholders.md
+++ b/docs/tutorials/es/managing-placeholders.md
@@ -35,7 +35,7 @@ Lo que hace es crear un elemento configurable en el lugar del código donde se i
 
 Es importante ingresar un valor de `id`. Este será el identificador para este placeholder en el sistema.
 
-![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando el placeholder
 
@@ -43,7 +43,7 @@ Ahora que el control de placeholder se ha ingresado en el template, vamos a conf
 
 Esto se hace en las configuraciones del layout que utiliza este template.
 
-1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra el layout y luego haga clic en la pestaña **Settings**. El nuevo placeholder debería aparecer allí, con el nombre igual al valor del id  definido en el control. Por ahora, este placeholder está vacío; es decir, no hay ningún objeto dentro de este.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para ingresar un objeto, haga clic en **add object**. 
 3. A continuación, seleccione el tipo de objeto y haga clic en **Añadir**.
 4. Finalmente, haga clic en el botón  **Save Settings**, en la parte superior de la página.
@@ -52,7 +52,7 @@ Ahora puede editar el objeto que ha ingresado en el placeholder.
 
 Para esto, haga clic en el lápiz que se encuentra dentro del objeto y, a continuación, haga clic en **add content**.
 
-![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Ahora puede definir el nombre de este objeto, subir imágenes y configurar las condiciones en las que se renderizará, tales como el período. 
 
diff --git a/docs/tutorials/es/managing-projects.md b/docs/tutorials/es/managing-projects.md
index 6df958192..ff382283f 100644
--- a/docs/tutorials/es/managing-projects.md
+++ b/docs/tutorials/es/managing-projects.md
@@ -17,7 +17,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 
 Proyectos es una funcionalidad de VTEX Headless CMS que simplifica la gestión de varios proyectos de frontend, como aplicaciones móviles, páginas web y email marketing, desde un único dashboard.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/28a48f587a491e87481d837595130e0d/projects-one-es.gif)
 
 Cada proyecto cuenta con sus propios ajustes, contenido y marca, pudiendo personalizarse en función de públicos u objetivos específicos. 
 
@@ -33,7 +33,7 @@ Para gestionar el Headless CMS, asegúrese de que los [recursos](https://help.vt
 ## Visión general
 Para acceder a **Proyectos**, en el Admin VTEX ve a **Storefront > Headless CMS**.
 
-![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/fa66fd00d9a29e3eeb835369c70277d7/projects-two-es-outro.png)
+![Projects overview](https://images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/fa66fd00d9a29e3eeb835369c70277d7/projects-two-es-outro.png)
 
 | Opciones     | Descripción     |
 | ---------- | ---------- |
@@ -113,7 +113,7 @@ Para archivar un proyecto sigue los pasos a continuación:
 1. Accede a **Storefront > Proyectos**.
 2. Selecciona el proyecto que deseas archivar y haz clic en **Configuración** (⚙️). 
 3. Haz clic en `Archivar proyecto` en la página `General`. Aparecerá un mensaje emergente para confirmar que deseas archivar el proyecto.
-![Arquivar projeto - ES](//images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/a7f9e04f4b9dc6161bd3f9a9c683f99c/projects-three-es.png)
+![Arquivar projeto - ES](https://images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/a7f9e04f4b9dc6161bd3f9a9c683f99c/projects-three-es.png)
 4. Haz clic en `Archivar`. A continuación aparecerá un mensaje informando que el proyecto se archivó con éxito.
 
 Para restaurar un proyecto archivado, sigue los pasos descritos en [Restaurar proyecto] (#restaurar-proyecto).
diff --git a/docs/tutorials/es/managing-redirects-per-binding.md b/docs/tutorials/es/managing-redirects-per-binding.md
index f7fbe0818..9876c9020 100644
--- a/docs/tutorials/es/managing-redirects-per-binding.md
+++ b/docs/tutorials/es/managing-redirects-per-binding.md
@@ -30,7 +30,7 @@ En el Admin VTEX:
 1. Acceda al módulo **Storefront > Páginas**.
 2. Haga clic en la pestaña `Redirecciones`.
 
-![es-redirect-tab](//images.ctfassets.net/alneenqid6w5/5TkQzPBMxi9Wh4SCBgVWZ1/ca140110fbe426d775814a1fd5ae4350/redirect-tab.png)
+![es-redirect-tab](https://images.ctfassets.net/alneenqid6w5/5TkQzPBMxi9Wh4SCBgVWZ1/ca140110fbe426d775814a1fd5ae4350/redirect-tab.png)
 
 ## Crear redirecciones manualmente
 
@@ -42,7 +42,7 @@ En la pestaña Redirecciones del módulo Páginas:
 4. Indique si la redirección será permanente o temporal. Si es temporal, puede activar el botón `Esta redirección tiene una fecha final` y definir la fecha final. 
 5. Guarde los cambios.
 
-![es-novoredirect](//images.ctfassets.net/alneenqid6w5/1XJSvEL4ozDdupa3j0mcx8/95ddbd08e7902a6c7aa7f30a4af85120/nuevo-redirect.png)
+![es-novoredirect](https://images.ctfassets.net/alneenqid6w5/1XJSvEL4ozDdupa3j0mcx8/95ddbd08e7902a6c7aa7f30a4af85120/nuevo-redirect.png)
 
 ## Eliminar redirecciones manualmente
 
@@ -52,7 +52,7 @@ En la pestaña Redirecciones del módulo Páginas:
 2. Haga clic en el botón `Remover`.
 3. Confirme la acción. 
 
-![es-remover-redirect](//images.ctfassets.net/alneenqid6w5/5khhDBT5o6ESJjwlaFClr5/a6d978fecd07eba1007ea1b28d2675b6/remover-redirect.png)
+![es-remover-redirect](https://images.ctfassets.net/alneenqid6w5/5khhDBT5o6ESJjwlaFClr5/a6d978fecd07eba1007ea1b28d2675b6/remover-redirect.png)
 
 <div class="alert alert-warning">
 Puede ocurrir un error al intentar hacer clic en las redirecciones que tienen cadenas de query. El equipo de producto de VTEX está al tanto de este comportamiento inesperado y está trabajando en la corrección. Si no puede hacer clic en la redirección que desea eliminar, puede utilizar la hoja de cálculo para eliminarla mientras arreglamos el error. 
@@ -83,7 +83,7 @@ En la pestaña Redirecciones del módulo Páginas:
 4. Haga clic en el botón `Importar`. 
 5. Haga clic en el botón `Guardar` o `Eliminar` según sea el caso. 
 
-  ![es-redirect-planilha](//images.ctfassets.net/alneenqid6w5/4jcHxndX1LyV74UdFJgWNV/7efcfc5207e0972a2b31a4be847b7000/planilha-redirect.png)
+  ![es-redirect-planilha](https://images.ctfassets.net/alneenqid6w5/4jcHxndX1LyV74UdFJgWNV/7efcfc5207e0972a2b31a4be847b7000/planilha-redirect.png)
 
   <div class="alert alert-warning">
 Al seleccionar la opción <code>Guardar</code>, creará todas las redirecciones enumeradas en la plantilla, mientras que seleccionar la opción <code>Eliminar</code> las eliminará todas de la base de datos de su tienda.
diff --git a/docs/tutorials/es/managing-shipping-policies.md b/docs/tutorials/es/managing-shipping-policies.md
index e2db080ec..c7a80ee49 100644
--- a/docs/tutorials/es/managing-shipping-policies.md
+++ b/docs/tutorials/es/managing-shipping-policies.md
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 La [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) es un conjunto de reglas y ajustes que definen las opciones de envío que se mostrarán a los clientes en el checkout. La relación entre la política de envío, [almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) y [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) es lo que conforma la [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) en VTEX, como se muestra en la siguiente imagen:
 
-![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
+![shipping_strategy_ES](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
 
 Este artículo describe cómo monitorear y gestionar las políticas de envío. La pestaña **Políticas de envío** en el Admin VTEX, accesible en **Envío > Estrategia de envío**, te permite realizar las siguientes acciones:
 
@@ -35,7 +35,7 @@ También puedes crear políticas de envío. Consulta [Crear una política de env
 
 La pestaña **Políticas de envío** del Admin VTEX, accesible a través de **Envío > Estrategia de envío**, muestra una lista como se ilustra a continuación:
 
-![shipping_policy_ES](//images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/04e7831e6af05ee2312eb51720c4e7f1/shipping_policy_ES.png)
+![shipping_policy_ES](https://images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/04e7831e6af05ee2312eb51720c4e7f1/shipping_policy_ES.png)
 
 La información de la lista se describe en la siguiente tabla:
 
diff --git a/docs/tutorials/es/managing-singleton-content-types.md b/docs/tutorials/es/managing-singleton-content-types.md
index ff01b9ea2..bbe45e103 100644
--- a/docs/tutorials/es/managing-singleton-content-types.md
+++ b/docs/tutorials/es/managing-singleton-content-types.md
@@ -18,7 +18,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 El content type de tipo Singleton permite la creación y gestión de una única página garantizando que en el Headless CMS solo exista una página de dicho content type.
 
 Su uso evita conflictos e incoherencias que pueden ocurrir cuando se crean varias páginas del mismo content type. Por ejemplo, puedes utilizar Singleton para la página de inicio (Home) de tu tienda, asegurándote de que solo haya una página de inicio y todas las actualizaciones y solicitudes realizadas en ella siempre devuelvan el mismo resultado.
-![singleton-es](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
+![singleton-es](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
 
 <div class="alert alert-warning">
   Para crear un content type Singleton, verifica con tu equipo de desarrolladores que la propiedad <i>isSingleton</i> ya esté implementada o solicita que sigan las instrucciones en <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> para agregarla al content type deseado.
diff --git a/docs/tutorials/es/managing-url-redirects.md b/docs/tutorials/es/managing-url-redirects.md
index fa3a17dfd..95c198670 100644
--- a/docs/tutorials/es/managing-url-redirects.md
+++ b/docs/tutorials/es/managing-url-redirects.md
@@ -27,7 +27,7 @@ Para crear, editar o eliminar redirecciones, el usuario del Admin VTEX debe tene
 4. En la casilla de selección, indica si la redirección es temporal o permanente. Si es temporal, debes definir la fecha de fin.
 5. Haz clic en `Guardar` para finalizar.
 
-![gerenciando redirecionamentos es 1](//images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/ca2f417ea225d8d6875f37c31d0847a7/image5.png)
+![gerenciando redirecionamentos es 1](https://images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/ca2f417ea225d8d6875f37c31d0847a7/image5.png)
 
 ## Importar redirección
 Para importar una redirección, sigue los pasos a continuación.
diff --git a/docs/tutorials/es/managing-users.md b/docs/tutorials/es/managing-users.md
index cb697aa1d..7475de4a1 100644
--- a/docs/tutorials/es/managing-users.md
+++ b/docs/tutorials/es/managing-users.md
@@ -19,7 +19,7 @@ La gestión de los usuarios con acceso al ambiente administrativo de su tienda V
 
 En esta sección, se mostrará la lista de usuarios con sus respectivos __Nombre__, __Email__ y configuración de __MFA__. También pueden verse las presentes opciones de búsqueda, exportación y creación de nuevos usuarios, así como editar y eliminar usuarios.
 
-![Lista Usuários User Management ES](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
+![Lista Usuários User Management ES](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
 
 <div class="alert alert-warning">
 Cualquier usuario que desee gestionar usuarios o claves de aplicación debe tener un perfil que contenga el <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <b>Save User</b>. Puedes utilizar, por ejemplo, el perfil predeterminado <a href="https://help.vtex.com/es/tutorial/roles-de-usuario-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>.
@@ -30,10 +30,10 @@ Cualquier usuario que desee gestionar usuarios o claves de aplicación debe tene
 1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
 2. Haga clic en el botón `+ Nuevo`.  
 3. Rellene el campo **Email**.  
-  ![Cadastro Novo usuário User Management ES](//images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/c25703eb8635123358251772d94e147a/Cadastro_Novo_usu__rio_User_Management_ES.png)
+  ![Cadastro Novo usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/c25703eb8635123358251772d94e147a/Cadastro_Novo_usu__rio_User_Management_ES.png)
 4. Haga clic en `+ Agregar roles`.
 5. Seleccione los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) deseados, como se muestra en la imagen: 
-  ![Selecionar perfis User Management ES](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/fed2df535522db7b5d7288845497b8d4/seleccionar-roles.PNG)
+  ![Selecionar perfis User Management ES](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/fed2df535522db7b5d7288845497b8d4/seleccionar-roles.PNG)
 6. Haga clic en `Agregar rol` para confirmar la selección.
 7. Haga clic en `Guardar`.  
 
@@ -45,10 +45,10 @@ La contraseña debe tener al menos 8 caracteres, incluyendo un número, una letr
 
 1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
 2. Para editar un usuario ya registrado, haga clic en su nombre. Esto también es posible haciendo clic en los tres puntos al lado derecho del usuario en la lista y luego en la opción **Editar**.
-  ![Botão Editar Usuário User Management ES](//images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/6063958f0625ce0beabac99f407a3b87/Bot__o_Editar_Usu__rio_User_Management_ES.png)
+  ![Botão Editar Usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/6063958f0625ce0beabac99f407a3b87/Bot__o_Editar_Usu__rio_User_Management_ES.png)
   <div class="alert alert-warning" role="alert">El email no puede ser cambiado. Si desea hacer esto, se deberá realizar un nuevo registro.</div>
 3. En la pantalla de edición, se pueden agregar o eliminar los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) de los usuarios.  
-  ![Selecionar perfis User Management ES](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/fed2df535522db7b5d7288845497b8d4/seleccionar-roles.PNG)
+  ![Selecionar perfis User Management ES](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/fed2df535522db7b5d7288845497b8d4/seleccionar-roles.PNG)
 4. Haga clic en `Agregar rol` para confirmar la selección.
 5. Haga clic en `Guardar`.
 
@@ -61,9 +61,9 @@ La contraseña debe tener al menos 8 caracteres, incluyendo un número, una letr
 1. En la barra superior de VTEX Admin, haga clic en el **avatar de tu perfil**, marcado con la inicial de tu correo electrónico, y luego en **Configuración de la cuenta** > **Cuenta**.
 2. Para remover el acceso de un usuario, haga clic en botón con tres puntos <i class="fas fa-ellipsis-v"></i> al lado del usuario que desea eliminar.
 3. Haga clic en la opción **Eliminar**.  
-  ![Botão Excluir Usuário User Management ES](//images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/fe34b8820154abc988ee1317cf75da3a/Bot__o_Excluir_Usu__rio_User_Management_ES.png)
+  ![Botão Excluir Usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/fe34b8820154abc988ee1317cf75da3a/Bot__o_Excluir_Usu__rio_User_Management_ES.png)
 4. Confirme haciendo clic en `SÍ, ELIMINAR TODO ACCESO`.  
-  ![Confirmar Remover Acesso User Management ES](//images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/2e0ecc32f578b0da6f0698fb136a8a21/Confirmar_Remover_Acesso_User_Management_ES.png)
+  ![Confirmar Remover Acesso User Management ES](https://images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/2e0ecc32f578b0da6f0698fb136a8a21/Confirmar_Remover_Acesso_User_Management_ES.png)
 
 ## Exportando datos de usuarios
 
diff --git a/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md b/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md
index 0122e9ca6..d6efbd0b8 100644
--- a/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md
+++ b/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md
@@ -17,7 +17,7 @@ subcategory: 1vwB9FtTSQmcSewQw02QoW
 
 La interfaz de Web Service permite que el responsable de la tienda acceda prácticamente todos los datos que son ilustrados en la interfaz de admin además de datos adicionales y exclusivos. Antes de usarlo, lea nuestra guía [Integration Guide](https://help.vtex.com/tutorial/guia-de-integracion-de-erps--3VuOwNLmb624ImooEIIkmO)
 
-[Download](//assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
+[Download](https://assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
 
 <div class="alert alert-danger"><p>Atenção: sólo los métodos SOAP correspondientes al <strong>catálogo</strong> son válidos.</p>
 <p><strong>Todos los demás métodos serán descontinuados a partir del 28/02/2017.</strong></p>
diff --git a/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md b/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
index 1b05e373f..237fae886 100644
--- a/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
+++ b/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
@@ -77,7 +77,7 @@ La segunda etapa para rellenar la plantilla de mapeo es hacer la correspondencia
 
 Las variaciones obligatorias son atributos indispensables para el mapeo de determinadas categorías del producto. Si se trata de un `calzado`, `ropa`, `bolsa`, `cinturón` o `electrodoméstico`, será necesario mapear las variaciones obligatorias. 
 
-El nombre de estas debe estar exactamente de acuerdo con los valores aceptados por el marketplace. [Descargue aquí](//assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/28d9a8e7ce08b03d243b43bb6b759c5d/Planilha_de_Atributos_do_Mercado_Livre.xlsx) la __Plantilla de Variaciones de Mercado Libre__ para verificar los valores aceptados de acuerdo con cada tipo de producto.
+El nombre de estas debe estar exactamente de acuerdo con los valores aceptados por el marketplace. [Descargue aquí](https://assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/28d9a8e7ce08b03d243b43bb6b759c5d/Planilha_de_Atributos_do_Mercado_Livre.xlsx) la __Plantilla de Variaciones de Mercado Libre__ para verificar los valores aceptados de acuerdo con cada tipo de producto.
 
 ### Variaciones personalizables 
 
diff --git a/docs/tutorials/es/marketplace-invited-sellers.md b/docs/tutorials/es/marketplace-invited-sellers.md
index 1a31e6290..1ef9726a6 100644
--- a/docs/tutorials/es/marketplace-invited-sellers.md
+++ b/docs/tutorials/es/marketplace-invited-sellers.md
@@ -27,7 +27,7 @@ Además de permitir enviar invitaciones, la página tiene una lista de sellers,
 
 Para que nuevos sellers se integren en su marketplace, es necesario realizar algunas acciones en su entorno VTEX: [Invitar](#invitar-seller) y [Conectar](#conectar-seller).
 
-![ES Seller invite](//images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/7c9dd1931913f57b7bef76df6faad117/ES_seller_invite.jpg)
+![ES Seller invite](https://images.ctfassets.net/alneenqid6w5/3kCM8CHXpzssH5MWf6txLh/7c9dd1931913f57b7bef76df6faad117/ES_seller_invite.jpg)
 
 ## Invitar Seller
 
diff --git a/docs/tutorials/es/marketplace-strategies-at-vtex.md b/docs/tutorials/es/marketplace-strategies-at-vtex.md
index df4821402..a24c30359 100644
--- a/docs/tutorials/es/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/es/marketplace-strategies-at-vtex.md
@@ -17,7 +17,7 @@ subcategory: 4uqMnZjwBO04uWgCom8QiA
 
 Un marketplace es una plataforma virtual en la que diferentes vendedores anuncian sus productos. Estos vendedores se denominan sellers y, además, de ser propietarios de los productos, muchas veces también son los responsables del [proceso de fulfillment del producto](https://help.vtex.com/es/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP).  
 
-![Estrategias de marketplace](//images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/9558d99b892b53aa723f408d29734435/Ecommerce_web_page-pana.png)
+![Estrategias de marketplace](https://images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/9558d99b892b53aa723f408d29734435/Ecommerce_web_page-pana.png)
 
 [VTEX promueve la colaboración digital](https://vtex.com/ar-es/marketplace/) en diferentes escenarios: no solo tienes la posibilidad de vender tus productos en otros marketplaces, sino que también puedes ofrecer los productos de otros sellers en tu propio entorno, convirtiéndote así en un marketplace.  
 
@@ -71,7 +71,7 @@ Es posible que un seller que no está integrado con VTEX quiera vender productos
 La configuración para [convertirse en un marketplace VTEX](https://help.vtex.com/es/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb) elimina algunos de los pasos requeridos en otras integraciones. Una vez configurado tu marketplace, consulta las [acciones para la operación de marketplaces VTEX](https://help.vtex.com/es/tutorial/acoes-para-a-operacao-de-marketplaces-vtex--2SdIflvwywiOqCpczKCfev).  
 
 A continuación, se presentan los principales marketplaces VTEX:  
-![mkt br](//images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
+![mkt br](https://images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
 
 Además, la página __Marketplaces e integraciones__ promueve y facilita el contacto entre marketplaces VTEX y marketplace certificados con sellers VTEX interesados en colaboraciones.  
 
diff --git a/docs/tutorials/es/marketplaces-and-integrations.md b/docs/tutorials/es/marketplaces-and-integrations.md
index 511214931..e510d7093 100644
--- a/docs/tutorials/es/marketplaces-and-integrations.md
+++ b/docs/tutorials/es/marketplaces-and-integrations.md
@@ -33,7 +33,7 @@ Si quieres actuar como marketplace VTEX, lee el artículo <a href="https://help.
 
 Para acceder a la página, en el Admin VTEX haz clic en *__Marketplace > Conexiones > Marketplaces e integraciones__*. Esta página, además de ofrecer sugerencias de marketplaces a los que conectarse, muestra la lista completa de todos los marketplaces disponibles o ya conectados.  
 
-![Marketplaces e integraciones](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
+![Marketplaces e integraciones](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/d3e6e73c3ea8afb1def6c94c0bf67ee5/Captura_de_tela_2023-04-17_110453.png)  
 
 La tabla donde figuran los marketplaces consta de las siguientes columnas:  
 
diff --git a/docs/tutorials/es/master-data-v2.md b/docs/tutorials/es/master-data-v2.md
index c8262716c..54de0beaf 100644
--- a/docs/tutorials/es/master-data-v2.md
+++ b/docs/tutorials/es/master-data-v2.md
@@ -25,10 +25,10 @@ Este artículo explica cómo guardar, validar y obtener documentos en el Master
 No es necesario crear un JSON Schema para guardar documentos. Usted puede guardar en cualquier entidad de datos si el contenido es un JSON válido.
 
 JSON Schema indica cómo validar e indizar. Una entidad de datos puede o no tener varios JSON Schemas.
-![master-data-data-entity-schemas](//images.contentful.com/alneenqid6w5/5Ms8eS24xOsGWcEGY0WKwu/724d0585090ee2d3bf6fc47dad7a3859/master-data-data-entity-schemas.jpg)
+![master-data-data-entity-schemas](https://images.contentful.com/alneenqid6w5/5Ms8eS24xOsGWcEGY0WKwu/724d0585090ee2d3bf6fc47dad7a3859/master-data-data-entity-schemas.jpg)
 
 Un documento puede ser compatible con varios JSON Schemas, pero también con ninguno.
-![master-data-documents-compliant](//images.contentful.com/alneenqid6w5/7m7NMV5Hc4Wq8aKeGeWiAY/29301b6873e1549c244d56e15cf4caf7/master-data-documents-compliant.jpg)
+![master-data-documents-compliant](https://images.contentful.com/alneenqid6w5/7m7NMV5Hc4Wq8aKeGeWiAY/29301b6873e1549c244d56e15cf4caf7/master-data-documents-compliant.jpg)
 
 Esto significa que JSON Schema es un formato de documentos en entidades de datos.
 
diff --git a/docs/tutorials/es/master-data.md b/docs/tutorials/es/master-data.md
index 6342d05db..f63f8ed3e 100644
--- a/docs/tutorials/es/master-data.md
+++ b/docs/tutorials/es/master-data.md
@@ -313,7 +313,7 @@ Obtén más información en <a href=https://json-schema.org/>esquemas JSON</a>.
 
 Puedes guardar un documento en cualquier entidad de datos si el contenido es un JSON válido. Una entidad de datos puede tener asociados o no varios esquemas JSON.
 
-![Master Data schemas](//images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/3b032813aed32ec745e01d4d32cf4e87/schemas_es.jpg)
+![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/3b032813aed32ec745e01d4d32cf4e87/schemas_es.jpg)
 
 <div class = "alert alert-info">
 Un documento puede ser compatible con varios esquemas JSON, o con ninguno.
diff --git a/docs/tutorials/es/match-offers-mercado-livre.md b/docs/tutorials/es/match-offers-mercado-livre.md
index 8698d53e0..c1046dca1 100644
--- a/docs/tutorials/es/match-offers-mercado-livre.md
+++ b/docs/tutorials/es/match-offers-mercado-livre.md
@@ -36,7 +36,7 @@ En este artículo, puedes explorar los siguientes temas:
 - [Tipos de oportunidades](#tipos-de-oportunidades)  
 - [Analizar oportunidades](#analizar-oportunidad)  
 
-![overview-match-anuncios-meli](//images.ctfassets.net/alneenqid6w5/1H13oiY7fPnalkV6rn7fY2/9f50b70e2f52e4f14fa70104b085c6cc/overview-match-anuncios-meli-pt.png)
+![overview-match-anuncios-meli](https://images.ctfassets.net/alneenqid6w5/1H13oiY7fPnalkV6rn7fY2/9f50b70e2f52e4f14fa70104b085c6cc/overview-match-anuncios-meli-pt.png)
 
 ## Estructura de la página
 
@@ -67,7 +67,7 @@ En la lista de catálogos activos, cada fila corresponde a un anuncio y presenta
 
 En la parte superior de la pantalla, se muestra el número de catálogos activos que están en cada status de relevancia.  
 
-![relevancia](//images.ctfassets.net/alneenqid6w5/4ktn7U1Dbqt7AhwdK1gtGn/3749ff23cf3e871dd8ae50941f806ae1/relevancia-pt.png)
+![relevancia](https://images.ctfassets.net/alneenqid6w5/4ktn7U1Dbqt7AhwdK1gtGn/3749ff23cf3e871dd8ae50941f806ae1/relevancia-pt.png)
 
 <div class=”alert alert-info>
 Los anuncios adquieren relevancia cuando ofrecen mejores precios y condiciones logísticas.
@@ -84,13 +84,13 @@ La relevancia de un anuncio registra si la oferta del seller se muestra como la
 Los tres tipos de oportunidades que pueden mostrarse para los anuncios de un seller son: **Preaviso, Requerido** y **Opcional**. En todas las oportunidades listadas por Mercado Libre, el seller puede vincular el producto a un anuncio. Si el anuncio del seller no tiene una correspondencia con una oferta del catálogo, debe abrirse un ticket con el equipo de soporte de Mercado Libre.  
 
 - **Preaviso:** este tipo de oportunidades son obligatorias y tienen un plazo para ser vinculadas. Esto quiere decir que el seller deberá asociar el producto a una oferta del catálogo de Mercado Libre. Si no se realiza la asociación en el plazo determinado por Mercado Libre, el marketplace moderará el anuncio del seller.  
-![aviso](//images.ctfassets.net/alneenqid6w5/ZuWyKDvUpqIS4BEUzdnnd/3cc4b009ff17e214ac5f6914b680ae2c/Captura_de_tela_2024-04-30_184708.png)
+![aviso](https://images.ctfassets.net/alneenqid6w5/ZuWyKDvUpqIS4BEUzdnnd/3cc4b009ff17e214ac5f6914b680ae2c/Captura_de_tela_2024-04-30_184708.png)
 
 - **Requerido:** este tipo de oportunidades son obligatorias, pero no tienen un plazo para asociarlas. Si no se vincula el anuncio, Mercado Libre puede moderar el anuncio del seller en el marketplace.  
-![anuncio obligatorio](//images.ctfassets.net/alneenqid6w5/62kOh7xJ7zOxc8StS33BA/b12e5711b67e4597a5161cf676e69c15/obrigatorio-pt.png)
+![anuncio obligatorio](https://images.ctfassets.net/alneenqid6w5/62kOh7xJ7zOxc8StS33BA/b12e5711b67e4597a5161cf676e69c15/obrigatorio-pt.png)
 
 - **Opcional:** este tipo de oportunidades son opcionales. Si no se realiza la asociación, el anuncio del seller no pierde relevancia ni será moderado por el marketplace.  
-![anuncio opcional](//images.ctfassets.net/alneenqid6w5/3Df2PgW8zBl7GKh32W0L07/c6ef9e482d18a074a5e93dc9e9e93204/opcional-pt.png)
+![anuncio opcional](https://images.ctfassets.net/alneenqid6w5/3Df2PgW8zBl7GKh32W0L07/c6ef9e482d18a074a5e93dc9e9e93204/opcional-pt.png)
 
 ## Analizar oportunidad
 
@@ -100,7 +100,7 @@ Para analizar una oportunidad, el seller utiliza la página **Match de anuncios*
 
 La pantalla **Analizar oportunidad** se muestra cuando el seller hace clic en el botón `Analizar oportunidad` de uno de los anuncios disponibles en la pestaña **Oportunidades**.  
 En el lado izquierdo de esta pantalla se muestra el producto registrado del seller en el catálogo VTEX y en el lado derecho el producto del catálogo de Mercado Libre sugerido para la asociación.  
-![análisis de anuncios](//images.ctfassets.net/alneenqid6w5/3hEW8BHsxqSQ6DZFsyn29n/566860d4c95d6ea12073abdcf838ecb2/sugestao-individual-ii-pt.png)
+![análisis de anuncios](https://images.ctfassets.net/alneenqid6w5/3hEW8BHsxqSQ6DZFsyn29n/566860d4c95d6ea12073abdcf838ecb2/sugestao-individual-ii-pt.png)
 
 ### Asociación individual
 
@@ -110,14 +110,14 @@ Para asociar las oportunidades individualmente, sigue los pasos a continuación
 2. Comprueba que los datos del anuncio sugerido por Mercado Libre sean compatibles con los datos de tu producto.  
 3. Haz clic en el botón `Aceptar sugerencia`.  
 4. Haz clic en el botón `Confirmar`.  
-![aceptar sugerencia individual](//images.ctfassets.net/alneenqid6w5/1QKVIvkdadoicf7TsjfhRQ/b5de58ececcf925df1090c4b96f8d081/sugestao-individual-pt.png)
+![aceptar sugerencia individual](https://images.ctfassets.net/alneenqid6w5/1QKVIvkdadoicf7TsjfhRQ/b5de58ececcf925df1090c4b96f8d081/sugestao-individual-pt.png)
 
 Después de realizar la asociación, el anuncio se publica en el catálogo de Mercado Libre y se envía a la pestaña **Catálogos activos** con el status **Procesando relevancia**.  
 
 Si los productos no coinciden, el seller debe buscar un anuncio del catálogo de Mercado Libre que corresponda a su producto para asociarlo.  
 
 Para buscar otros anuncios en el catálogo de Mercado Libre, el seller debe ingresar el nombre de su producto en la barra de búsqueda que está debajo de la foto principal del producto en la página **`Analizar oportunidad`**.  
-![búsqueda de anuncios](//images.ctfassets.net/alneenqid6w5/2T5bvbMUTF9BeOGdIYtJ58/829ebd40c08e4ecdfde73902f32e917a/Captura_de_tela_2024-04-30_194057.png)
+![búsqueda de anuncios](https://images.ctfassets.net/alneenqid6w5/2T5bvbMUTF9BeOGdIYtJ58/829ebd40c08e4ecdfde73902f32e917a/Captura_de_tela_2024-04-30_194057.png)
 
 ### Asociación en masa
 
@@ -126,6 +126,6 @@ Para asociar las oportunidades en masa, sigue los pasos a continuación desde la
 1. Selecciona las oportunidades que deseas asociar. En la parte inferior de la pantalla se muestra un panel con el número de oportunidades seleccionadas.  
 2. Haz clic en el botón `Aceptar sugerencias`.  
 3. Haz clic en el botón `Confirmar`.  
-![sugerencia-masiva](//images.ctfassets.net/alneenqid6w5/52VZCcnHAOMdyA1GWrFpH/982157da7e94b3b5dd80e171d5090c61/sugestao-massiva-pt.png)
+![sugerencia-masiva](https://images.ctfassets.net/alneenqid6w5/52VZCcnHAOMdyA1GWrFpH/982157da7e94b3b5dd80e171d5090c61/sugestao-massiva-pt.png)
 
 Después de realizar la asociación, los anuncios se publican en el catálogo de Mercado Libre y se envían a la pestaña **Catálogos activos** con el status **Procesando relevancia**.  
diff --git a/docs/tutorials/es/media-overview.md b/docs/tutorials/es/media-overview.md
index 8a223d74b..d1c52907a 100644
--- a/docs/tutorials/es/media-overview.md
+++ b/docs/tutorials/es/media-overview.md
@@ -21,7 +21,7 @@ En la página Multimedia puedes gestionar los archivos multimedia de tu tienda,
 Para cargar, los archivos deben tener una extensión en minúsculas, por ejemplo, <code>store.png</code>, y el límite de tamaño de archivo para cargar en Multimedia es de <b>5 MB</b>.
 </div>
 
-![Multimedia Visión general](//images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4b7fca26bb4f3b1f72d3a6fff9eca887/es-multimedia-overview.png)
+![Multimedia Visión general](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4b7fca26bb4f3b1f72d3a6fff9eca887/es-multimedia-overview.png)
 
 demás, Multimedia está integrada con **Site Editor** y **Headless CMS**. Esta integración te permite acceder y gestionar archivos multimedia directamente a través de las soluciones de CMS de VTEX.
 
@@ -45,7 +45,7 @@ Ten en cuenta que la sección debe utilizar la <a href="https://developers.vtex.
 
 En la siguiente imagen se muestra una visión general de la interfaz de Multimedia y las acciones disponibles para gestionar tus archivos multimedia:
 
-![Multimedia Features](//images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/db95f45451326e0664992cefa1cd8a6f/es-multimedia-features.png)
+![Multimedia Features](https://images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/db95f45451326e0664992cefa1cd8a6f/es-multimedia-features.png)
 
 | Campo | Descripción |
 | ---------- | ------------- |
diff --git a/docs/tutorials/es/mercado-libre-promotions.md b/docs/tutorials/es/mercado-libre-promotions.md
index c4d805f4e..cf84bfeb5 100644
--- a/docs/tutorials/es/mercado-libre-promotions.md
+++ b/docs/tutorials/es/mercado-libre-promotions.md
@@ -21,7 +21,7 @@ Para proporcionar mayor agilidad a la operación del seller, en la barra de bús
 
 Para acceder a la página de promociones disponibles en el Admin VTEX, debes ir a __Marketplace > Mercado Libre > Promociones.__  
 
-![Promociones de Mercado Libre](//images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
+![Promociones de Mercado Libre](https://images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
 
 ## Tipos de promociones
 
diff --git a/docs/tutorials/es/mercado-livre-automobilist-compatibility.md b/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
index e5d0ed24c..3d6be0520 100644
--- a/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
+++ b/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
@@ -29,7 +29,7 @@ En los anuncios enviados a Mercado Libre, se pueden identificar los que tengan e
 Los anuncios que tengan error no se envían a Mercado Libre hasta que se corrijan.
 </div>  
 
-![Mercado Libre: compatibilidad de autopartes](//images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/df37ddb666928a86c4199ce98bfe7af6/comp_automobilistica.png) 
+![Mercado Libre: compatibilidad de autopartes](https://images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/df37ddb666928a86c4199ce98bfe7af6/comp_automobilistica.png) 
 
 Para acceder al módulo Gestión de anuncios, en el Admin VTEX, ve a __Marketplace > Integraciones > Gestión de anuncios.__ En esta página puedes filtrar por canal, marca, categoría o status.  
 
@@ -39,7 +39,7 @@ Para corregir los errores de `Compatibilidad con MELI` sigue los pasos a continu
 2.	Haz clic en __Error de asociación de autopartes.__  
 3.	Haz clic en __Gestionar compatibilidad.__  
 4.	Rellena los campos __Marca, Modelo, Año, Versión__ según la compatibilidad del accesorio.  
-![Mercado Libre: compatibilidad de autopartes 2](//images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/73b751561077eb819e5044443f184f2d/compatibilidad_automobilistica_2.png)  
+![Mercado Libre: compatibilidad de autopartes 2](https://images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/73b751561077eb819e5044443f184f2d/compatibilidad_automobilistica_2.png)  
 5.	Agrega todos los modelos de vehículos compatibles haciendo clic en +.  
 6.	Haz clic en el botón __Agregar excepción__ y espera el mensaje «Excepción enviada con éxito».  
 7.	Haz clic en Confirmar y aparecerá el mensaje "Compatibilidad asociada con éxito" en la pantalla.  
diff --git a/docs/tutorials/es/mercado-livre-faq.md b/docs/tutorials/es/mercado-livre-faq.md
index f8f309611..07f1b9a67 100644
--- a/docs/tutorials/es/mercado-livre-faq.md
+++ b/docs/tutorials/es/mercado-livre-faq.md
@@ -96,7 +96,7 @@ Al registrar un producto, es necesario establecer una cantidad mínima de stock
 
 La categoría en cuestión exige el mapeo de marca y modelo. Esta información debe estar presente en la plantilla de mapeo. Formato de ejemplo:
 
-![mercadolivre faq erro](//images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
+![mercadolivre faq erro](https://images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
 
 ## ¿Por qué mi anuncio está desactivado en Mercado Libre?
 
@@ -136,12 +136,12 @@ Sin embargo, estos atributos son bastante claros (Color principal, Color secunda
 
 Si alguno de estos atributos se completa de forma incorrecta (por ejemplo, si se asignó un código relativo a Talla de cinturón para un zapato), Integraciones va a mostrar un error con el siguiente formato:
 
-![mercadolivre faq erro2](//images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
+![mercadolivre faq erro2](https://images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
 
 En este caso, tenemos dos ejemplos de errores en el mismo mensaje.
 El primero de estos indica que el atributo cuyo código comienza con el número `113000` es necesario para la categoría escogida y no fue ingresado en la plantilla de mapeo. Vea la plantilla a continuación:
 
-![mercadolivre faq erro3](//images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
+![mercadolivre faq erro3](https://images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
 
 El segundo error muestra que el atributo cuyo código empieza con el número `63000`, ingresado en la última columna de la plantilla anterior, es inválido para la categoría escogida.
 
@@ -186,7 +186,7 @@ Existe el elemento principal del anuncio y este contiene las variaciones (que so
 
 Cada categoría tiene su propia especificación de cuántas imágenes pueden ser añadidas, en la categoría MLA3697 solo se permite 12 imágenes para este elemento principal. Vea en el enlace las condiciones de esta [categoría](https://api.mercadolibre.com/categories/MLA3697)
 
-![mercadolivre faq erro4](//images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
+![mercadolivre faq erro4](https://images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
 
 `SKU no integrado, pues el mismo no posee descripción`
 
diff --git a/docs/tutorials/es/merchandising-rules-list.md b/docs/tutorials/es/merchandising-rules-list.md
index 0f0cc6e3e..c3fa40fd2 100644
--- a/docs/tutorials/es/merchandising-rules-list.md
+++ b/docs/tutorials/es/merchandising-rules-list.md
@@ -22,7 +22,7 @@ En el Admin VTEX, la página **Storefront** > **Intelligent Search** > **Reglas
 * [Editar](#editar-reglas-de-merchandising)
 * [Eliminar](#eliminar-reglas-de-merchandising)
 
-![reglas-merch-es](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/4624acb4cd7dbe4e2a4d858e570f1f92/reglas-merch-es.PNG)
+![reglas-merch-es](https://images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/4624acb4cd7dbe4e2a4d858e570f1f92/reglas-merch-es.PNG)
 
 La página contiene la siguiente información: 
 
diff --git a/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md b/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md
index 6ee406e97..d21729869 100644
--- a/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md
+++ b/docs/tutorials/es/metrics-are-not-displayed-in-the-order-dashboard.md
@@ -23,7 +23,7 @@ Al acceder al Admin, es posible que tu tienda no cargue las métricas presentes
 - **Periodo de comparación inadecuado:** es posible que el periodo seleccionado en la esquina superior derecha del dashboard no contenga suficientes datos de pedidos para realizar la comparación.
 - **Permisos de acceso limitados:** es posible que no dispongas del rol necesario para ver determinada información en el dashboard.
 
-![Visão geral - ES](//images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/ab4d1113340d7b941580edc9dc7dacc5/Vis_o_geral_-_ES.png)
+![Visão geral - ES](https://images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/ab4d1113340d7b941580edc9dc7dacc5/Vis_o_geral_-_ES.png)
 
 ## Solución
 Para resolver inconsistencias en el dashboard inicial del panel administrativo, prueba a realizar las acciones que se describen a continuación:
@@ -34,7 +34,7 @@ Ajustar correctamente el periodo de comparación puede resolver el problema, ya
 1. En el VTEX Admin, accede a **Dashboard > Vista general**.
 2. En la esquina superior derecha selecciona el periodo de comparación.
 
-![Dashboard - ES](//images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/352e042a451953fe735d06b1160ae2d9/Dashboard_-_ES.png)
+![Dashboard - ES](https://images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/352e042a451953fe735d06b1160ae2d9/Dashboard_-_ES.png)
 
 ### Esperar a que la información se actualice
 El tiempo de espera para la actualización de la información del dashboard puede variar entre 10 y 80 minutos. Este periodo es necesario para que los datos se procesen y se muestren correctamente. Para más información sobre el tiempo de espera, accede a [Comparar periodos](https://help.vtex.com/es/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ?&utm_source=autocomplete#comparacao-de-periodos).
diff --git a/docs/tutorials/es/migrating-ads-in-mercado-livre.md b/docs/tutorials/es/migrating-ads-in-mercado-livre.md
index 6417bd5f8..71ae3cedf 100644
--- a/docs/tutorials/es/migrating-ads-in-mercado-livre.md
+++ b/docs/tutorials/es/migrating-ads-in-mercado-livre.md
@@ -41,7 +41,7 @@ Si usas el ID de una política comercial ya existente, la integración creará n
 
 En esta etapa, deberás hacer la equivalencia entre tus anuncios en Mercado Libre y los SKU de tu tienda. Esta información se envía a través de la plantilla de migración.
 
-Primero, descarga la [plantilla de migración](//assets.ctfassets.net/alneenqid6w5/4tgBiQQeiAQGyys4OAuIGc/1bf6f64f485de43d2329db270c1303de/Planilha_de_Migrac__a__o_de_Anu__ncios_-_Mercado_Livre_BR.xlsx) y usa este archivo como modelo para rellenarla. Esta es la plantilla que rellenarás y enviarás a Mercado Libre.
+Primero, descarga la [plantilla de migración](https://assets.ctfassets.net/alneenqid6w5/4tgBiQQeiAQGyys4OAuIGc/1bf6f64f485de43d2329db270c1303de/Planilha_de_Migrac__a__o_de_Anu__ncios_-_Mercado_Livre_BR.xlsx) y usa este archivo como modelo para rellenarla. Esta es la plantilla que rellenarás y enviarás a Mercado Libre.
 
 El producto registrado en VTEX solo se podrá mapear con un anuncio en Mercado Libre. En el caso de los [anuncios Clásicos y Premium](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/2MR2USqcvDGaoAkGNdCfGi), el mismo producto podrá anunciarse en ambos tipos de anuncios, ya que tienen configuraciones separadas.
 
diff --git a/docs/tutorials/es/multilevel-omnichannel-inventory.md b/docs/tutorials/es/multilevel-omnichannel-inventory.md
index 6887cbfe0..06734f1bb 100644
--- a/docs/tutorials/es/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/es/multilevel-omnichannel-inventory.md
@@ -38,7 +38,7 @@ También es posible que este _seller_ principal venda sus productos en un _marke
 
 Cuando esto ocurre, tenemos una arquitectura de tres niveles entre el _marketplace_, el _seller_ principal y sus _sellers white label_, como se ilustra en la imagen de abajo.
 
-![Arquitetura Multilevel omichannel inventory](//images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/abf2341444442ee6ef770afdfd044a06/Screen_Shot_2022-09-30_at_18.57.26.png)
+![Arquitetura Multilevel omichannel inventory](https://images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/abf2341444442ee6ef770afdfd044a06/Screen_Shot_2022-09-30_at_18.57.26.png)
 
 De forma predeterminada, los productos de las tiendas físicas, o _sellers white label_ (nivel 3 en la imagen), no están disponibles para ser vendidos por el _marketplace_ de nivel 1, pero con la funcionalidad _Multilevel Omnichannel Inventory_ puedes disponibilizarlos.
 
diff --git a/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md b/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md
index c4f3ea92f..eb06e0008 100644
--- a/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md
+++ b/docs/tutorials/es/my-ad-is-not-displayed-on-mercado-livre.md
@@ -35,7 +35,7 @@ Para comprobar que la política comercial esté configurada correctamente en el
 3. En la página de registro del producto, comprueba que la política comercial que se utiliza para Mercado Libre esté seleccionada.
 4. Si no lo está, marca la casilla de la política comercial.
 
-  ![politicas-comerciales-es](//images.ctfassets.net/alneenqid6w5/dRDUjjHbk3Ui0ZQEX7SYd/0840562553e4b05d584a9d0a0d453c4b/politicas-comerciales-es.png)
+  ![politicas-comerciales-es](https://images.ctfassets.net/alneenqid6w5/dRDUjjHbk3Ui0ZQEX7SYd/0840562553e4b05d584a9d0a0d453c4b/politicas-comerciales-es.png)
 
  5. Haz clic en el botón `Guardar`.
 
@@ -51,7 +51,7 @@ Para comprobar la configuración del stock mínimo, accede a Marketplace > Conex
 2. En la fila de la integración deseada, haz clic en `Editar`.
 3. En `Configuración`, comprueba que el campo Stock mínimo tenga un valor.
 
-  ![inventario-minimo-es](//images.ctfassets.net/alneenqid6w5/wy7Bz5Dcm2pt24HNVHYdZ/bb8666c71a6e0e52f4b6317e14f49ed7/inventario-minimo-es.png)
+  ![inventario-minimo-es](https://images.ctfassets.net/alneenqid6w5/wy7Bz5Dcm2pt24HNVHYdZ/bb8666c71a6e0e52f4b6317e14f49ed7/inventario-minimo-es.png)
 
  4. Asegúrate de que este campo esté configurado correctamente según se explica en el artículo [Control de stock mínimo para integraciones](https://help.vtex.com/es/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D).
 
diff --git a/docs/tutorials/es/new-integration-with-erede-erederest.md b/docs/tutorials/es/new-integration-with-erede-erederest.md
index 0df73a2b4..c8965dc5a 100644
--- a/docs/tutorials/es/new-integration-with-erede-erederest.md
+++ b/docs/tutorials/es/new-integration-with-erede-erederest.md
@@ -25,11 +25,11 @@ Para configurar la nueva versión, primero usted debe solicitar a Rede la activa
 
 Una vez notificado, acceda al menú __e.Rede > Ajustes > Generar token__.
 
-![GerarToken](//images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
+![GerarToken](https://images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
 
 A continuación, basta con hacer clic en el botón de __Gerar Token__.
 
-![GerarToken Click](//images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
+![GerarToken Click](https://images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
 
 Con eso, usted podrá ver el token que deberá ser informado en el formulario de configuración de la afiliación de gateway ERedeRest. Además del token, usted también necesitará informar el PV, que es el número de identificación del establecimiento en el sitio de Rede.
 
@@ -39,10 +39,10 @@ Para hacer esta configuración en VTEX,
 2. En __Configuración__, acceda __Afiliaciones__;
 3. Haga clic en el botón verde __+__ _Quiero recibir pagos por este conector..._ y busque el conector __ERedeRest.__
 
-![erederestES](//images.ctfassets.net/alneenqid6w5/33o1Nwlo0geAy2yIUkUuG4/92c3a9d28f7bc35ca9f5652dc2679fe9/erederestES.jpg) 
+![erederestES](https://images.ctfassets.net/alneenqid6w5/33o1Nwlo0geAy2yIUkUuG4/92c3a9d28f7bc35ca9f5652dc2679fe9/erederestES.jpg) 
 
-![erederestES-config](//images.ctfassets.net/alneenqid6w5/tTuJ0rmx44aggkAssQSsi/63f9539d9db6bdf6bb73276be63c5fa8/erederestES-config.jpg)
+![erederestES-config](https://images.ctfassets.net/alneenqid6w5/tTuJ0rmx44aggkAssQSsi/63f9539d9db6bdf6bb73276be63c5fa8/erederestES-config.jpg)
 
-![PegarPV](//images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
+![PegarPV](https://images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
 
 Este nuevo conector ofrece una serie de opciones de configuración, entre ellas está el soporte al ApplePay.
diff --git a/docs/tutorials/es/new-my-orders-area.md b/docs/tutorials/es/new-my-orders-area.md
index d7ad9ca23..2484ee8f3 100644
--- a/docs/tutorials/es/new-my-orders-area.md
+++ b/docs/tutorials/es/new-my-orders-area.md
@@ -24,27 +24,27 @@ Dado que la nueva estrutura de páginas es completamente diferente, será neces
 
 VTEX busca usar estrategias modernas para crear productos que atiendan cada vez mejor al mercado de e-commerce. Por esa razón, comenzamos a usar las librerías de desarrollo React JS en nuestras features más recientes: la nueva página de **Mis Pedidos** es un ejemplo. Ella viene con nuevas features y nuevo diseño, y fue creada de cero usando React.
 
-![Pantalla de lista del nuevo mis pedidos](//images.contentful.com/alneenqid6w5/6qzQL3eb7iAiMSqoMYkAKy/0d23fe714fd46a18e1372d4c2aa54356/MO1.png)
+![Pantalla de lista del nuevo mis pedidos](https://images.contentful.com/alneenqid6w5/6qzQL3eb7iAiMSqoMYkAKy/0d23fe714fd46a18e1372d4c2aa54356/MO1.png)
 
 ### Nueva experiencia de navegación
 
 React no fue escogido solo para estar alineados con la nueva plataforma VTEX — por ser una single-page application cargada dentro de la tienda -, sino que la nueva área de pedidos posee una navegación suave, con una experiencia mucho mejor para el usuario.
 
-![Navegación Mis Pedidos com carga instantânea entre páginas](//images.contentful.com/alneenqid6w5/6LN7wTA0k8maaaGGwicqkG/cb11a2c95c14d9c707e5c2a50de3ffd5/MOg.gif)
+![Navegación Mis Pedidos com carga instantânea entre páginas](https://images.contentful.com/alneenqid6w5/6LN7wTA0k8maaaGGwicqkG/cb11a2c95c14d9c707e5c2a50de3ffd5/MOg.gif)
 
 ### Features
 
 Este update en Mis Pedidos servirá de punto de partida para nuevas features en esta sección, más ya trae mejorías en esta primera versión, comoun  layout mobile-ready y el timeline de pedido — que muchas agencias implementabam como una customización.
 
-![Mis Pedidos Mobile y Desktop](//images.contentful.com/alneenqid6w5/ESy6qfL91AK6Sg4EOqEOc/0ce3d9beaffd06c3dd27ddc7fe2ef6b4/MO2.png)
+![Mis Pedidos Mobile y Desktop](https://images.contentful.com/alneenqid6w5/ESy6qfL91AK6Sg4EOqEOc/0ce3d9beaffd06c3dd27ddc7fe2ef6b4/MO2.png)
 
-![Detalles del pedido](//images.contentful.com/alneenqid6w5/3W4TIsXbAQ4K0GGoQkiOeg/3d0d6bd97d292bf52938c4bc5c7bdc35/MO3.png) 
+![Detalles del pedido](https://images.contentful.com/alneenqid6w5/3W4TIsXbAQ4K0GGoQkiOeg/3d0d6bd97d292bf52938c4bc5c7bdc35/MO3.png) 
 
 Otra feature nueva es las Razones predefinidas de Cancelació, que el cliente podrá escoger en caso de que no quiera escribir una razón. Estas opciones pueden ser fácilmente customizadas y traducidas en las configuraciones del Portal:
 
-![Cancelación de pedido](//images.contentful.com/alneenqid6w5/2xKijTKi3SIOm8kQ2QY2Sk/bf2addae6991b6c0a96d46c510c57d95/MO4.png)
+![Cancelación de pedido](https://images.contentful.com/alneenqid6w5/2xKijTKi3SIOm8kQ2QY2Sk/bf2addae6991b6c0a96d46c510c57d95/MO4.png)
 
-![Customización de razones de cancelación](//images.contentful.com/alneenqid6w5/69XLrh4ObY4e8ES00EYAim/1b21c3628851459685f1719e78654ea9/MO5.png)
+![Customización de razones de cancelación](https://images.contentful.com/alneenqid6w5/69XLrh4ObY4e8ES00EYAim/1b21c3628851459685f1719e78654ea9/MO5.png)
 
 ¡Ahora también estamos soportando traducción nativa del Mis Pedidos para el francês!
 
@@ -53,7 +53,7 @@ Otra feature nueva es las Razones predefinidas de Cancelació, que el cliente po
 
 Para no causar problemas de compatibilidad y quebrar las customizaciones actuales, la nueva sección de Mis Pedidos viene con un opt-in, que permite a las tiendas inicialmente migrar a la velocidad que deseen. Este opt-in se encuentra en el Portal, en la misma sección que la customización de las Razones de Cancelación:
 
-![Activando el nuevo mis pedidos](//images.contentful.com/alneenqid6w5/Nf4NJcrnMWQEay0YmW0IU/af155d35e2db7ab7a8fa8f8e0ec8462e/MO6.png)
+![Activando el nuevo mis pedidos](https://images.contentful.com/alneenqid6w5/Nf4NJcrnMWQEay0YmW0IU/af155d35e2db7ab7a8fa8f8e0ec8462e/MO6.png)
 
 Antes de activar la nueva versión, se puede ver que el acceso a su tienda por el ambiente beta `accountname.vtexcommercestable.com.br/account/orders`.
 
diff --git a/docs/tutorials/es/offer-details.md b/docs/tutorials/es/offer-details.md
index db0d9d5ee..7545f63cb 100644
--- a/docs/tutorials/es/offer-details.md
+++ b/docs/tutorials/es/offer-details.md
@@ -43,7 +43,7 @@ La página **Detalles del anuncio** incluye las siguientes secciones:
 
 ## Encabezado
 
-![Offer details ES cabecalho](//images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/7daa6c6a14fa3f1bdb959526d5f33157/Offer_details_ES_cabecalho.jpg)
+![Offer details ES cabecalho](https://images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/7daa6c6a14fa3f1bdb959526d5f33157/Offer_details_ES_cabecalho.jpg)
 
 El encabezado presenta la información principal del anuncio para su rápida visualización, como imagen, nombre del canal, status, ID en VTEX e ID en el canal. También permite realizar las siguientes interacciones mediante el botón `Editar`:
 
@@ -59,13 +59,13 @@ En este bloque, se presenta información sobre los status posibles para un  dete
 
 ### Status: sincronizado
 
-![Offer details PT status sucesso](//images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/f9aae1830daa0fe200e2f7ec5b470d7e/Offer_details_ES_status_sucesso.jpg)
+![Offer details PT status sucesso](https://images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/f9aae1830daa0fe200e2f7ec5b470d7e/Offer_details_ES_status_sucesso.jpg)
 
 El status *Sincronizado* significa que el anuncio ha sido recibido con éxito en un canal y está siendo actualizado tanto por el marketplace como por el seller, en tiempo real.   
 
 ### Status: error
 
-![Offer details PT status erro](//images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/cba423c498f0003a3990768c22a993a4/Offer_details_ES_status_erro.jpg)
+![Offer details PT status erro](https://images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/cba423c498f0003a3990768c22a993a4/Offer_details_ES_status_erro.jpg)
 
 El status *Error* significa que el sistema ha encontrado un problema que impide el envío o la actualización de un anuncio en un canal, de modo que se requiere que el seller lo solucione. Los errores pueden originarse tanto del lado del seller VTEX, como descripciones de productos que exceden el límite de caracteres, como del lado del marketplace, como llamadas de API con errores.   
 
@@ -83,19 +83,19 @@ Si todavía hay errores por corregir, o si están todos corregidos pero se está
 
 ### Status: indisponible
 
-![Offer details PT status indisponivel](//images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/3fcfa6c8636db3979e7e23b4af740da4/Offer_details_ES_status_indisponivel.jpg)
+![Offer details PT status indisponivel](https://images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/3fcfa6c8636db3979e7e23b4af740da4/Offer_details_ES_status_indisponivel.jpg)
 
 El status *Indisponible* se produce cuando el anuncio es descartado, por estar inactivo o no estar incluido en la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) determinada para el canal.
 
 ### Status: enviando
 
-![Offer details PT status enviando](//images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1a7b65d75c2fe5ca1025663298f97970/Offer_details_ES_status_enviando.jpg)
+![Offer details PT status enviando](https://images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/1a7b65d75c2fe5ca1025663298f97970/Offer_details_ES_status_enviando.jpg)
 
 El status *Enviando* es un estado intermedio, cuando los anuncios aún están en proceso de ser enviados al canal. Este status comprende anuncios que se envían al marketplace por primera vez, que están migrando a un nuevo canal o que han sido reenviados después de haber sido descartados en un canal.   
 
 ## Lista de interacciones
 
-![Offer details PT lista interacoes](//images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/3b825866f07b646c065df4004c802ff3/Offer_details_ES_lista_interacoes.jpg)
+![Offer details PT lista interacoes](https://images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/3b825866f07b646c065df4004c802ff3/Offer_details_ES_lista_interacoes.jpg)
 
 La pestaña *Interacciones* de la página **Detalles del anuncio** muestra todas las actualizaciones de `stock`, `precio` o `catálogo` que sufrió el SKU. Cada fila corresponde a una interacción producida en el anuncio, e incluye los siguientes datos:
 
diff --git a/docs/tutorials/es/offer-management.md b/docs/tutorials/es/offer-management.md
index 8865b8335..89ab911e6 100644
--- a/docs/tutorials/es/offer-management.md
+++ b/docs/tutorials/es/offer-management.md
@@ -24,17 +24,17 @@ Para los conectores interesados en comenzar la integración, les pedimos que esp
 
 El módulo **Gestión de anuncios** permite a los _sellers_ hacer el seguimiento del envío y la sincronización de los anuncios de las integraciones con los canales de venta. En VTEX, un anuncio es un SKU cuyo precio y stock fueron configurados por un _seller_ y que fue enviado a un canal de ventas.
 
-![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 **Gestión de anuncios** permite hacer un seguimiento de los anuncios con [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic y Premium), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y marketplaces VTEX. Para los conectores que desean integrarse a través de API, existe la [Guía de integración de Gestión de anuncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 Para acceder al módulo, en el Admin VTEX, ingresa en **Marketplace > Conexiones > Gestión de anuncios**. Una vez hecho esto, aparecerá la siguiente interfaz:
 
-![sent-offers-es_2](//images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/a4b532bd1367cc8f15e25afe1ce78fa0/sent-offers-es_2.png)
+![sent-offers-es_2](https://images.ctfassets.net/alneenqid6w5/4NEuTkSW9kSb6SQa3I7QPc/a4b532bd1367cc8f15e25afe1ce78fa0/sent-offers-es_2.png)
 
 La interfaz de **Gestión de anuncios** mostrará una lista con tus anuncios y podrás hacer clic sobre cada uno de ellos para acceder a los [detalles del anuncio](https://help.vtex.com/es/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) y verificar los [detalles de la interacción](https://help.vtex.com/es/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf). Las interacciones son los registros del anuncio durante todo el proceso de sincronización y el envío al canal de ventas. Los registros de los detalles de la interacción están disponibles durante diez días para consulta.
 
-![diagrama ju meyer sent offers es](//images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/a3cae86d4d8a5126d448471e37b037b1/diagrama_ju_meyer_sent_offers_es.png)
+![diagrama ju meyer sent offers es](https://images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/a3cae86d4d8a5126d448471e37b037b1/diagrama_ju_meyer_sent_offers_es.png)
 
 En la página **Gestión de anuncios**, puedes realizar las siguientes acciones:
 
diff --git a/docs/tutorials/es/offer-quality-filters.md b/docs/tutorials/es/offer-quality-filters.md
index 5c1940d90..ea3a4edf2 100644
--- a/docs/tutorials/es/offer-quality-filters.md
+++ b/docs/tutorials/es/offer-quality-filters.md
@@ -21,7 +21,7 @@ Es importante para la operación del marketplace que haya criterios de calidad p
 
 **Calidad de anuncios** es la página donde los marketplaces registran y gestionan los grupos de requisitos aplicados al proceso de catalogación de SKU recibidos. Para accederla, en su VTEX Admin, haz clic en **Marketplace > Calidad de anuncios**, o escriba __"Calidad del anuncio"__ en la barra de búsqueda.
 
-![ES offer quality](//images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/890bb24504e8f6b809cd318fb85ed53a/ES_offer_quality.png)
+![ES offer quality](https://images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/890bb24504e8f6b809cd318fb85ed53a/ES_offer_quality.png)
 
 Con este tutorial, sepa cómo:
 
@@ -46,7 +46,7 @@ La funcionalidad permite que el operador del marketplace pueda realizar una seri
 | Aportar más transparencia a los criterios de catalogación de anuncios recibidos y a la medida en que los sellers y anuncios los cumplen.                                                            | Permite identificar los sellers y los tipos de anuncios que no cumplen los requisitos, lo que acelera la corrección de problemas.                 |
 
 ## Ver "Default requirements" 
-![ESDefault requirements](//images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/b86fb58a9c6b454c31fb0bf0829adf4f/ESDefault_requirements.png)
+![ESDefault requirements](https://images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/b86fb58a9c6b454c31fb0bf0829adf4f/ESDefault_requirements.png)
 
 La página estándar tiene algunos requisitos preestablecidos que se aplicarán a todas las categorías, sellers y marcas, conocidas como «Default requirements». Algunos de estos criterios se configuran de forma nativa en [VTEX Matcher](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), la herramienta aplicada a los marketplaces VTEX para ayudar en el proceso de catalogación de los anuncios recibidos.
 
diff --git a/docs/tutorials/es/offer-status.md b/docs/tutorials/es/offer-status.md
index 8e1fb66e3..458730b32 100644
--- a/docs/tutorials/es/offer-status.md
+++ b/docs/tutorials/es/offer-status.md
@@ -19,11 +19,11 @@ El módulo **Status de los anuncios** permite a los sellers realizar un seguimie
 
 En **Status de los anuncios** se puede llevar a cabo un seguimiento de los anuncios enviados únicamente a los marketplaces VTEX. Para acceder al módulo en el Admin VTEX, ve a **Marketplace > Conexiones > Status de los anuncios,** o ingresa **Status de los anuncios** en la barra de búsqueda.  
 
-![Pantalla de estado de la oferta](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/91b3ae83719e933617324f74223d736b/-ES-_Offer_Status_-_GIF.gif)
+![Pantalla de estado de la oferta](https://downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/91b3ae83719e933617324f74223d736b/-ES-_Offer_Status_-_GIF.gif)
 
 La página **Status de los anuncios** está compuesta por tres pestañas: **[Publicados](#pestana-publicados)**, **[Problemas](#pestana-problemas)** y **[A la espera de finalización.](#pestana-a-la-espera-de-finalizacion)** Todas ellas presentan una lista de tus anuncios de acuerdo con su status actual. Accede y consulta los detalles de cada anuncio, como status, stock, precio, fecha de actualización y los motivos de rechazo en el marketplace.
 
-![Estado de los anuncios shcema](//images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/9e17eeb599bb0d5e3dec1933097d4af0/offer-status-schema-es.png)
+![Estado de los anuncios shcema](https://images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/9e17eeb599bb0d5e3dec1933097d4af0/offer-status-schema-es.png)
 
 ## Pestaña Publicados
 
@@ -50,7 +50,7 @@ Para filtrar los anuncios por **Marketplace**, haz clic en la flecha hacia abajo
 
 Para filtrar los anuncios por **Stock**, haz clic en la flecha hacia abajo situada junto al filtro, ingresa el número de stock mínimo, stock máximo, o ambos, y haz clic en **Aplicar**.
 
-![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/0cc494ba4b34b71a2aaf21cfb3ed1a21/inventario-offer-status.png)
+![Filtro estoque offer status](https://images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/0cc494ba4b34b71a2aaf21cfb3ed1a21/inventario-offer-status.png)
 
 Para filtrar los anuncios por **Actualización**, haz clic en la flecha hacia abajo situada junto al filtro, selecciona una de las opciones y haz clic en **Aplicar.**
 
@@ -59,7 +59,7 @@ Consulta a continuación las opciones disponibles para este filtro:
 - **Actualizados**: son anuncios cuyo precio y/o stock han sido actualizados por el seller y se procesaron con éxito.
 - **Error al actualizar:** anuncios que presentaban inconsistencias y, por lo tanto, no pudieron ser actualizados.
 
-![Filtro atualizado offer status](//images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/fa8829e63abbb196a93296e24d12a960/actualizaci_n-offer-status.png)
+![Filtro atualizado offer status](https://images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/fa8829e63abbb196a93296e24d12a960/actualizaci_n-offer-status.png)
 
 Puedes utilizar un único filtro o combinarlos en una misma búsqueda. Los filtros no vienen preseleccionados de manera predeterminada, lo que significa que la página inicial mostrará la cantidad total de anuncios existentes.
 
@@ -102,7 +102,7 @@ Para actualizar la información de un anuncio ya publicado el seller debe realiz
 
 Serás redirigido a la página correspondiente para realizar los cambios necesarios.
 
-![Ações offer status](//images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/b17744a4b3b202fc28490eda7ff16663/a__es-offer-status.png)
+![Ações offer status](https://images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/b17744a4b3b202fc28490eda7ff16663/a__es-offer-status.png)
 
 ### Exportar la lista de anuncios publicados
 
@@ -142,7 +142,7 @@ Para filtrar los anuncios por **Enviados**, haz clic en la flecha hacia abajo si
 
 Para filtrar los anuncios por **Stock**, haz clic en la flecha hacia abajo situada junto al filtro, ingresa el número de stock mínimo, stock máximo, o ambos, y haz clic en **Aplicar**.
 
-![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/0cc494ba4b34b71a2aaf21cfb3ed1a21/inventario-offer-status.png)
+![Filtro estoque offer status](https://images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/0cc494ba4b34b71a2aaf21cfb3ed1a21/inventario-offer-status.png)
 
 Puedes utilizar un único filtro o combinarlos en una misma búsqueda. Los filtros no vienen preseleccionados de manera predeterminada, lo que significa que la página inicial mostrará la cantidad total de anuncios existentes.
 
diff --git a/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md b/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
index 4a6bf51bc..5c74cde91 100644
--- a/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
+++ b/docs/tutorials/es/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
@@ -23,7 +23,7 @@ Por defecto, es necesario que, en el marketplace, haya [stock](https://help.vtex
 
 En la imagen que aparece a continuación se muestra un ejemplo en el cual el seller A envió un producto al marketplace A. Si el marketplace A tiene en stock el mismo producto que recibió del seller A, puede enviar ese ítem al marketplace B.
 
-![erro-envio-skus-sellers-marketplaces-docnovo](//images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
+![erro-envio-skus-sellers-marketplaces-docnovo](https://images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
 
 Los marketplaces que cuentan con este modelo de negocio se ven beneficiados porque pueden ofrecer su gama de productos en canales de venta de terceros y así generar más oportunidades de venta.
 
diff --git a/docs/tutorials/es/oms-page-structure.md b/docs/tutorials/es/oms-page-structure.md
index 6d3d84759..e8dfd81ba 100644
--- a/docs/tutorials/es/oms-page-structure.md
+++ b/docs/tutorials/es/oms-page-structure.md
@@ -37,7 +37,7 @@ Para todos los datos de variaciones de pedidos, y también para los números de
 Importante: si la comparación de pedidos se realiza en base a 0 pedidos en el pasado, la variación es de 0%.
 </div>
 
-![barra-status-oms es](//images.ctfassets.net/alneenqid6w5/6fv6Fd07ra6KMOwS0ecgUm/02d1b532b5fb183d420ced0ecbb6d235/barra_de_status.png)
+![barra-status-oms es](https://images.ctfassets.net/alneenqid6w5/6fv6Fd07ra6KMOwS0ecgUm/02d1b532b5fb183d420ced0ecbb6d235/barra_de_status.png)
 
 ### Filtros
 
@@ -45,7 +45,7 @@ Permiten aplicar varios filtros para ver sólo la lista de pedidos deseados. El
 
 - [Cómo filtrar pedidos](/es/tutorial/como-filtrar-pedidos/)
 
-![botão-filtro-oms es](//images.ctfassets.net/alneenqid6w5/4NsNMVbov66KmWuM4cuYaw/d041c92d257680f6904b9e51f1a49e07/filtro_esp.png)
+![botão-filtro-oms es](https://images.ctfassets.net/alneenqid6w5/4NsNMVbov66KmWuM4cuYaw/d041c92d257680f6904b9e51f1a49e07/filtro_esp.png)
 
 ### Barra de búsqueda
 
@@ -53,7 +53,7 @@ Se utiliza para realizar búsquedas sobre los términos encontrados en el pedido
 
 - [Cómo buscar pedidos](/es/tutorial/como-buscar-el-pedido/)
 
-![barra-busca-oms es](//images.ctfassets.net/alneenqid6w5/4NQi3UjfPiqsS00AgyaMAO/528adcb5032b6e613bd7eef6e6251826/barra_de_busca_esp.png)
+![barra-busca-oms es](https://images.ctfassets.net/alneenqid6w5/4NQi3UjfPiqsS00AgyaMAO/528adcb5032b6e613bd7eef6e6251826/barra_de_busca_esp.png)
 
 ### Barra de información
 
@@ -63,7 +63,7 @@ También trae el ranking de ventas de la tienda en relación a todas las otras t
 
 - [Interpretando los datos de la barra de pedidos en la pantalla de Todos los Pedidos.](http://help.vtex.com/es/tutorial/interpretando-los-datos-de-la-barra-de-pedidos-del-oms)
 
-![barra-info-oms es](//images.ctfassets.net/alneenqid6w5/5Z5H9agm9qewyOGqCg0Cim/e535b7690c3d21ff1803981fbf0feff2/barra_de_info.png)
+![barra-info-oms es](https://images.ctfassets.net/alneenqid6w5/5Z5H9agm9qewyOGqCg0Cim/e535b7690c3d21ff1803981fbf0feff2/barra_de_info.png)
 
 ### Botón de exportación
 
@@ -71,7 +71,7 @@ Utilizado para exportar los pedidos que trae la búsqueda, considerando los filt
 
 - [Exportar pedidos en Gestión de pedidos. ](http://help.vtex.com/es/tutorial/exportacion-de-pedidos-en-oms)
 
-![botão-exportar-oms es](//images.ctfassets.net/alneenqid6w5/4sL2BuR5LO4Qamsgwsagss/47a5f99522b5f16b5fe57c487fa31fd9/botao_de_exportar_es.png)
+![botão-exportar-oms es](https://images.ctfassets.net/alneenqid6w5/4sL2BuR5LO4Qamsgwsagss/47a5f99522b5f16b5fe57c487fa31fd9/botao_de_exportar_es.png)
 
 ### Lista de pedidos
 
@@ -79,7 +79,7 @@ Principal área de Gestión de pedidos. Trae los últimos pedidos realizados en
 
 - [Lista de pedidos](/es/tutorial/listado-de-pedidos)
 
-![todos-pedidos-oms es](//images.ctfassets.net/alneenqid6w5/54hTspElLOKW2m4oi46ceU/ed5cd9c6b3b7272108f2c317533bfc11/orders_list_esp.png)
+![todos-pedidos-oms es](https://images.ctfassets.net/alneenqid6w5/54hTspElLOKW2m4oi46ceU/ed5cd9c6b3b7272108f2c317533bfc11/orders_list_esp.png)
 
 ### VTEX DO
 
@@ -87,7 +87,7 @@ Reúne tareas pendientes para la tienda, generadas por los diferentes módulos d
 
 -[ Cómo funciona el listado de tareas del VTEX DO.](http://help.vtex.com/es/tutorial/vtex-do)
 
-![vtex-do-exemplo-oms es](//images.ctfassets.net/alneenqid6w5/73Jca1gQ00a8e0gE8iAwCE/1380b478cd1836eac15289825de2b8e9/vtex_do_es.png)
+![vtex-do-exemplo-oms es](https://images.ctfassets.net/alneenqid6w5/73Jca1gQ00a8e0gE8iAwCE/1380b478cd1836eac15289825de2b8e9/vtex_do_es.png)
 
 ## Suscripciones
 
@@ -105,5 +105,5 @@ La segunda pestaña, **Afiliados**, está destinada para configuraciones de afil
 
 - [Configurar afiliado.](http://help.vtex.com/es/tutorial/como-configurar-afiliado/)
 
-![configurações-oms es](//images.ctfassets.net/alneenqid6w5/1j5ORpKc6MEa4GSIGcC2q4/75e49a2d0e6572047f10acc1c82f3900/configuracion_esp_OMS.png)
+![configurações-oms es](https://images.ctfassets.net/alneenqid6w5/1j5ORpKc6MEa4GSIGcC2q4/75e49a2d0e6572047f10acc1c82f3900/configuracion_esp_OMS.png)
 
diff --git a/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
index a52b356b1..8f0a12974 100644
--- a/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
@@ -35,7 +35,7 @@ Una vez que se haya autenticado por el método elegido, usted accederá al panel
 
 Para abrir un ticket, simplemente haga clic en el botón __Enviar una solicitud__.
 
-![chamado financeiro1 ES](//images.ctfassets.net/alneenqid6w5/5yMKtmj6Hm4IiIuwmW0yiw/ae68f5d5b54c92aa65e57774501e6c26/chamado_financeiro1_ES.png)
+![chamado financeiro1 ES](https://images.ctfassets.net/alneenqid6w5/5yMKtmj6Hm4IiIuwmW0yiw/ae68f5d5b54c92aa65e57774501e6c26/chamado_financeiro1_ES.png)
 
 Usted será llevado al formulario de envío de ticket, donde debe llenar:
 - Su nombre.
@@ -45,7 +45,7 @@ Usted será llevado al formulario de envío de ticket, donde debe llenar:
 - El tema.
 - La descripción de la pregunta o del problema.
 
-![chamado financeiro2 ES](//images.ctfassets.net/alneenqid6w5/yV71aHHNYskkeWUWA8UIO/9be3291fa9596dd9ab9479093798a8d6/chamado_financeiro2_ES.png)
+![chamado financeiro2 ES](https://images.ctfassets.net/alneenqid6w5/yV71aHHNYskkeWUWA8UIO/9be3291fa9596dd9ab9479093798a8d6/chamado_financeiro2_ES.png)
 
 Usted también puede incluir adjuntos, como capturas de pantallas o gifs animados que ayuden a describir el contexto de su solicitud.
 
@@ -85,7 +85,7 @@ Al hacer clic en __Mis solicitudes__, usted verá el historial de tickets abiert
 
 Si hace clic en __Todas las solicitudes__, puede ver el historial de tickets abiertos por cualquier empleado de su tienda.
 
-![chamado financeiro3 ES](//images.ctfassets.net/alneenqid6w5/319yZLbjOgCeKiUU6kEakE/93c02c46b8b85358eb2942243f8f3ba1/chamado_financeiro3_ES.png)
+![chamado financeiro3 ES](https://images.ctfassets.net/alneenqid6w5/319yZLbjOgCeKiUU6kEakE/93c02c46b8b85358eb2942243f8f3ba1/chamado_financeiro3_ES.png)
 
 ## Los status de los tickets
 
@@ -100,4 +100,4 @@ Después, el ticket pasa por los status `Esperando respuesta`, `Resuelto` y `Cer
 
 En su panel de soporte, usted puede filtrar la búsqueda de tickets por status. Para ello, simplemente utilice la casilla de verificación debajo del botón de envío de solicitud.
 
-![chamado financeiro4 ES](//images.ctfassets.net/alneenqid6w5/2gyz4xXSessueWkkoUwwQG/fa8bbe2215456264f86e80735a38ac50/chamado_financeiro4_ES.png)
+![chamado financeiro4 ES](https://images.ctfassets.net/alneenqid6w5/2gyz4xXSessueWkkoUwwQG/fa8bbe2215456264f86e80735a38ac50/chamado_financeiro4_ES.png)
diff --git a/docs/tutorials/es/opening-tickets-to-vtex-support.md b/docs/tutorials/es/opening-tickets-to-vtex-support.md
index 0270c29e7..4a521ba22 100644
--- a/docs/tutorials/es/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/es/opening-tickets-to-vtex-support.md
@@ -65,7 +65,7 @@ Al seleccionar esta opción de soporte, deberás rellenar la información que se
    * *Tengo una duda y quisiera hacer una pregunta*
    * *Quisiera solicitar una configuración*
 2. En el campo **Asunto de la solicitud**, rellena con la información relacionada con el tipo de problema para el que necesitas ayuda. En base a la descripción de tu problema, te indicaremos algunos artículos del [Centro de Ayuda](https://help.vtex.com/es/) que podrían serte útiles para solucionar tu problema. Si crees que ninguno de los artículos puede ayudarte a resolver el problema, avanza al paso siguiente.
-![https help.vtex.com es support](//images.ctfassets.net/alneenqid6w5/6th3vu5w61nnzp8NE1Xiza/e1e53143d8559adad86d03e8550ba258/https___help.vtex.com_es_support.gif)
+![https help.vtex.com es support](https://images.ctfassets.net/alneenqid6w5/6th3vu5w61nnzp8NE1Xiza/e1e53143d8559adad86d03e8550ba258/https___help.vtex.com_es_support.gif)
 3. Haz clic en el botón `Seguir`.
 Serás direccionado a otra página.
 4. .En el campo **Impacto del problema**, selecciona la opción que mejor se adapte al impacto del problema:
diff --git a/docs/tutorials/es/operational-capacity-beta.md b/docs/tutorials/es/operational-capacity-beta.md
index 33910c4c2..a3040e98d 100644
--- a/docs/tutorials/es/operational-capacity-beta.md
+++ b/docs/tutorials/es/operational-capacity-beta.md
@@ -29,7 +29,7 @@ Una buena gestión de la capacidad operativa de los sellers tiene los siguientes
 
 Al acceder a **Envío > Capacidad operativa** en el Admin VTEX, verás una página según se ilustra a continuación:
 
-![operational_capacity_image1_ES](//images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/defaa51c729689fdd70aa1e00e018d40/operational_capacity_image1_ES.png)
+![operational_capacity_image1_ES](https://images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/defaa51c729689fdd70aa1e00e018d40/operational_capacity_image1_ES.png)
 
 <div class="alert alert-warning">
 Los sellers que aparecen en la interfaz son los sellers de tu operación, configurados previamente por nuestro equipo. Para agregar un nuevo seller, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro soporte</a>.
@@ -127,7 +127,7 @@ La plataforma tiene algunas restricciones en relación con <a href="https://help
 
 El gráfico **Status de la capacidad operativa** muestra en tiempo real el porcentaje utilizado de la capacidad del seller, como se ilustra a continuación:
 
-![operational_capacity_image2_ES](//images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/1c6046c4c098cca52060888b61f53fa9/operational_capacity_image2_ES.png)
+![operational_capacity_image2_ES](https://images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/1c6046c4c098cca52060888b61f53fa9/operational_capacity_image2_ES.png)
 
 El gráfico muestra los siguientes periodos:
 
@@ -149,7 +149,7 @@ Para editar la dirección o el nombre de identificación del seller en **Capacid
 
 En la sección **Capacidad operativa**, puedes ver la configuración actual de la capacidad operativa del seller para cada día de la semana, como se muestra a continuación:
 
-![operational_capacity_image3_ES](//images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/d4019f9c94ab752050d6387e48b88a5c/operational_capacity_image3_ES.png)
+![operational_capacity_image3_ES](https://images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/d4019f9c94ab752050d6387e48b88a5c/operational_capacity_image3_ES.png)
 
 Para modificar la configuración, sigue estos pasos:
 
diff --git a/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
index 78b3caddf..813cac91f 100644
--- a/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
@@ -53,7 +53,7 @@ Para deshabilitar la función __Opciones de entrega optimizadas__, siga los paso
 3. En el menú de opciones azul ubicado en la parte superior de la página, haga clic en __Checkout__.
 4. En __Opciones de entrega optimizadas__, haga clic en el botón <i class="fas fa-toggle-off"></i> para deshabilitar la opción de visualización de las __Opciones de entrega optimizadas__.
 
-![Opciones de entrega optimizadas](//images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/94ea6b1f59944005c687713e08d86962/Opciones_de_entrega_optimizadas.PNG)
+![Opciones de entrega optimizadas](https://images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/94ea6b1f59944005c687713e08d86962/Opciones_de_entrega_optimizadas.PNG)
 
 <ul>
   5. Haga clic en <b>Guardar</b>.
diff --git a/docs/tutorials/es/order-details-page.md b/docs/tutorials/es/order-details-page.md
index 0a03fd9ae..6f4e46736 100644
--- a/docs/tutorials/es/order-details-page.md
+++ b/docs/tutorials/es/order-details-page.md
@@ -50,7 +50,7 @@ A continuación, se detallan todas las secciones posibles de la página <b>Detal
 
 ## Barra superior
 
-![BarrasuperiorES](//images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/a5a4369cfa3231a289e6e40e606b53b8/BarrasuperiorES.jpg)
+![BarrasuperiorES](https://images.ctfassets.net/alneenqid6w5/4iRT7cRVqHuZ7BzKScT76O/a5a4369cfa3231a289e6e40e606b53b8/BarrasuperiorES.jpg)
 
 La barra superior de la página contiene la siguiente información y acciones:
 
@@ -64,7 +64,7 @@ La barra superior de la página contiene la siguiente información y acciones:
 
 ## Información general 
 
-![Informacao geraisES](//images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/08c3f4586217f281477c87b60ac10520/Informacao_geraisES.jpg)
+![Informacao geraisES](https://images.ctfassets.net/alneenqid6w5/33MvPNsMEzss1dgk5qaakl/08c3f4586217f281477c87b60ac10520/Informacao_geraisES.jpg)
 
 La información general del pedido se muestra en la parte superior de la página, debajo de la barra superior, e incluye:
 
@@ -86,7 +86,7 @@ Este bloque muestra el status actual del pedido en el [flujo de pedidos](https:/
 
 ### Ítems a facturar
 
-![Itens faturarES](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
+![Itens faturarES](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/bd9f368f2ac4a319c490bd3c84fe88d3/Itens_faturarES__1_.png)
 
 El bloque **Ítems a facturar** contiene paquetes con ítems cuyo pago ha sido aprobado pero que aún no han sido [facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT), es decir, sus facturas no se no se emitieron a la plataforma.
 
@@ -99,7 +99,7 @@ En la esquina superior izquierda aparecen las siguientes acciones:
 
 ### Facturas
 
-![FaturaES](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
+![FaturaES](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/a94ecc1266048ad8f4c973a0b9042c5a/FaturaES.png)
 
 Este bloque muestra los ítems facturados con sus respectivas facturas y los paquetes que componen las entregas. En este bloque tú puedes:
 
@@ -110,7 +110,7 @@ Este bloque muestra los ítems facturados con sus respectivas facturas y los paq
 
 ### Ítems devueltos
 
-![Itens devolvidosES](//images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/2c0eeac373646a73f4f79686d5f8d55f/Itens_devolvidosES__1_.png)
+![Itens devolvidosES](https://images.ctfassets.net/alneenqid6w5/318Sl1C9ih6QCltdfps82D/2c0eeac373646a73f4f79686d5f8d55f/Itens_devolvidosES__1_.png)
 
 El bloque de **Ítems devueltos** se muestra cuando se devuelven ítems del pedido. Mira qué información y acciones están disponibles en este bloque:
 
@@ -124,7 +124,7 @@ El bloque de **Ítems devueltos** se muestra cuando se devuelven ítems del pedi
 
 ### Historial de ítems modificados
 
-![Historico Itens alteradosES](//images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/52ab970237d69819a43c8c40621dd712/Historico_Itens_alteradosES.png)
+![Historico Itens alteradosES](https://images.ctfassets.net/alneenqid6w5/2iaeorSz55zPeXnjaGZdPm/52ab970237d69819a43c8c40621dd712/Historico_Itens_alteradosES.png)
 
 Este bloque está disponible cuando hay un cambio de ítems en el pedido. El **Historial de ítems modificados** contiene los detalles del cambio: qué ítems se añadieron o eliminaron, la fecha en que se produjo el cambio y los valores de los productos (el precio del ítem devuelto, el precio del ítem agregado y la diferencia entre los dos).
 
@@ -132,7 +132,7 @@ Si hay cambios en el valor final del pedido, la diferencia de valor se mostrará
 
 ## Historial del pedido
 
-![Historico pedidoES](//images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/0e9e5ab253e4b902fa99438c725deb56/Historico_pedidoES.jpg)
+![Historico pedidoES](https://images.ctfassets.net/alneenqid6w5/1x2CvQpxrGD48YdmebHVsu/0e9e5ab253e4b902fa99438c725deb56/Historico_pedidoES.jpg)
 
 Este bloque muestra las interaciones dentro del pedido, con sus respectivas fechas y horas. 
 
@@ -146,7 +146,7 @@ También puedes ver los detalles de las notificaciones enviadas por email al cli
 
 ## Comentarios
 
-![ComentariosES](//images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/e8b25905f968644d3346d14109b528d0/ComentariosES.png)
+![ComentariosES](https://images.ctfassets.net/alneenqid6w5/6Rqz8dZ1DzcY6nE7juDELC/e8b25905f968644d3346d14109b528d0/ComentariosES.png)
 
 Esta sección te permite añadir comentarios internos con observaciones sobre el pedido. Para ello, escribe en la caja de texto y haz clic en `Enviar`.
 
@@ -154,7 +154,7 @@ Los comentarios enviados se registran en la página de detalles del pedido con l
 
 ## Detalles financieros
 
-![LateralES](//images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/cb09b4e443df18a1f4af4971718e568a/LateralES.png)
+![LateralES](https://images.ctfassets.net/alneenqid6w5/1oYh572kbKHKoqODLnmNyD/cb09b4e443df18a1f4af4971718e568a/LateralES.png)
 
 En la parte derecha de la página, puedes consultar los detalles financieros del pedido. Esta información se actualiza automáticamente a medida que avanza el pedido. 
 
diff --git a/docs/tutorials/es/order-flow-and-status.md b/docs/tutorials/es/order-flow-and-status.md
index 0da50e538..99916f0a3 100644
--- a/docs/tutorials/es/order-flow-and-status.md
+++ b/docs/tutorials/es/order-flow-and-status.md
@@ -40,7 +40,7 @@ Para los casos de pedidos incompletos, consulta el artículo <a href="https://he
 
 ### Flujo de marketplace
 
-![pedido_marketplace_es](//images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/390a09b29e0385c23be5ce5228e8b9f4/pedido_marketplace_es.png)
+![pedido_marketplace_es](https://images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/390a09b29e0385c23be5ce5228e8b9f4/pedido_marketplace_es.png)
 
 El flujo del _marketplace_ está integrado con el flujo del _seller_. Cuando se finaliza un pedido que será enviado por un _seller_ externo (que no es el _seller_ principal), el flujo visto por el _marketplace_ es el siguiente: 
 
@@ -57,7 +57,7 @@ Para saber cómo identificar pedidos que provienen de _marketplaces_, consulta e
 
 ### Flujo de seller
 
-![pedido_fluxo_seller_es](//images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/51c2f48ff1629813b469311d8c867ec9/pedido_fluxo_seller_es.png)
+![pedido_fluxo_seller_es](https://images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/51c2f48ff1629813b469311d8c867ec9/pedido_fluxo_seller_es.png)
 
 Este es el flujo del pedido visto por la tienda responsable de enviar los productos que componen el pedido. El pedido se realiza a través de otra tienda (o _marketplace_) y el flujo del _seller_ se inicia después de la confirmación del pedido.
 
@@ -96,7 +96,7 @@ Ten en cuenta que:
 
 ### Flujo completo
 
-![pedido_fluxo_completo_es_2](//images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/ccb76d6a281ae006d08b4d060866073a/pedido_fluxo_completo_es.png)
+![pedido_fluxo_completo_es_2](https://images.ctfassets.net/alneenqid6w5/hQ09aEM1eaW28N7TRG0PY/ccb76d6a281ae006d08b4d060866073a/pedido_fluxo_completo_es.png)
 
 El flujo completo del pedido es visto por la tienda que realiza la venta y el envío del pedido. El flujo completo está compuesto por el flujo del _marketplace_ y el flujo del _seller_ de forma secuencial.
 
@@ -144,7 +144,7 @@ Para saber más sobre la cancelación de pedidos, consulta el artículo [¿Por q
 
 ### Flujo de cadena
 
-![pedido_fluxo_chain_es](//images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/86fb6d87fbe872f1f81aa5219a7f92d6/pedido_fluxo_chain_es.png)
+![pedido_fluxo_chain_es](https://images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/86fb6d87fbe872f1f81aa5219a7f92d6/pedido_fluxo_chain_es.png)
 
 El flujo de pedidos visto por la tienda intermediaria en una venta [Multinivel Omnichannel Inventory](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) es similar al flujo de pedidos del _marketplace_, excepto al recibir el pago de los pedidos. En la etapa de `Pago pendiente`, en lugar de la cadena recibir el pago directamente del _gateway_, el _marketplace_ informa a la cadena que recibió la confirmación del pago. 
 
diff --git a/docs/tutorials/es/order-in-the-name-of-a-customer-using-the-callcenter.md b/docs/tutorials/es/order-in-the-name-of-a-customer-using-the-callcenter.md
index 0fc99698e..ca6fa7100 100644
--- a/docs/tutorials/es/order-in-the-name-of-a-customer-using-the-callcenter.md
+++ b/docs/tutorials/es/order-in-the-name-of-a-customer-using-the-callcenter.md
@@ -21,10 +21,10 @@ La toolbar aparece una vez que el operador registrado haga login en el ambiente
 
 Para comprar en nombre del cliente por el televentas, el operador debe hacer clic en **Entrar como**, ubicado en la esquina derecha de la toolbar.
 
-![Operador de televentas personificando el cliente con la barra](//images.contentful.com/alneenqid6w5/3rWoDmY4paceYWKEW2cg2S/c7edba682c7fd97b25d0fdc01faf1f9b/toolbar-1-1.png)
+![Operador de televentas personificando el cliente con la barra](https://images.contentful.com/alneenqid6w5/3rWoDmY4paceYWKEW2cg2S/c7edba682c7fd97b25d0fdc01faf1f9b/toolbar-1-1.png)
 
 Después, el e-mail del cliente será exibido en esta misma área.
 
 Para hacer login como otro usuario, solo hay que hacer clic en el botón **Cambiar**** de cliente**.
 
-![Cliente personificado con la barra](//images.contentful.com/alneenqid6w5/TwHPvbhB8Os02kO4IaS66/d70f2a05303502043ae4d7be3dfce59f/Toolbar2.png)
+![Cliente personificado con la barra](https://images.contentful.com/alneenqid6w5/TwHPvbhB8Os02kO4IaS66/d70f2a05303502043ae4d7be3dfce59f/Toolbar2.png)
diff --git a/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md b/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
index e06572106..e0470eb1b 100644
--- a/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
+++ b/docs/tutorials/es/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
@@ -29,6 +29,6 @@ Entre las imágenes del SKU, la principal será aquella flechada en el registro
 
 Vea, en nuestro ejemplo, que aunque no sea la primera imagen registrada, la imagen definida como principal es la que se asume en la página de producto al seleccionar el SKU.
 
-![sku_imagem_principal es](//images.ctfassets.net/alneenqid6w5/4NAI7uGKy4aYq6qeKW6I6y/a3290a6d910a321c57ac58349a9d78b1/ex_3_es.png)
+![sku_imagem_principal es](https://images.ctfassets.net/alneenqid6w5/4NAI7uGKy4aYq6qeKW6I6y/a3290a6d910a321c57ac58349a9d78b1/ex_3_es.png)
 
 - Al subir la planilla de imágenes, la plataforma considera línea a línea luego la primera línea de un sku será considerada la principal y así sucesivamente.
diff --git a/docs/tutorials/es/orders-list.md b/docs/tutorials/es/orders-list.md
index 575cadecf..72fe59837 100644
--- a/docs/tutorials/es/orders-list.md
+++ b/docs/tutorials/es/orders-list.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Es a través de la lista de pedidos de Gestión de Pedidos que el administrador de la tienda puede acompañar las compras concretadas en su tienda. La lista está disponible en la primera pantalla del módulo de __Gestión de pedidos__.
 
-![todosospedidos.es](//images.ctfassets.net/alneenqid6w5/61CuVQRq34KRRF3snvvKaE/f0fefc688ca00abd418c042d01a655da/todosospedidos.es.png)
+![todosospedidos.es](https://images.ctfassets.net/alneenqid6w5/61CuVQRq34KRRF3snvvKaE/f0fefc688ca00abd418c042d01a655da/todosospedidos.es.png)
 
 En la vista predeterminada se muestran todos los pedidos de la tienda desde el más reciente. Usted puede cambiar el orden haciendo clic en el nombre de las columnas, así como buscar o filtrar los pedidos por datos específicos, y también exportar estos datos.
 
@@ -30,7 +30,7 @@ Al hacer clic en cualquier pedido, el usuario es dirigido a la página de detall
 
 Siempre que el módulo de Gestión de Pedidos esté abierto y se hayan realizado nuevos pedidos, se mostrará una indicación, permitiendo que se haga clic para actualizar la lista de pedidos.
 
-![novopedido.es](//images.ctfassets.net/alneenqid6w5/2xSXOyFF91NG1U1T0jlu32/75b80899d88f814136f28e80d070015a/novopedido.es.png)
+![novopedido.es](https://images.ctfassets.net/alneenqid6w5/2xSXOyFF91NG1U1T0jlu32/75b80899d88f814136f28e80d070015a/novopedido.es.png)
 
 A continuación, se muestran más detalles sobre las columnas de la lista:
 
@@ -38,7 +38,7 @@ A continuación, se muestran más detalles sobre las columnas de la lista:
 
 No es nada más que el número de pedido (mostrado al cliente), el sufijo y el código secuencial de la transacción (para uso interno).
 
-![nsequecial.es](//images.ctfassets.net/alneenqid6w5/X5TM9ww79vrqUWk8NaJPG/f45cba83a8faeb03c1ecadc1c7d24e19/nsequecial.es.png)
+![nsequecial.es](https://images.ctfassets.net/alneenqid6w5/X5TM9ww79vrqUWk8NaJPG/f45cba83a8faeb03c1ecadc1c7d24e19/nsequecial.es.png)
 
 ### Número del pedido
 
@@ -77,7 +77,7 @@ Trae siempre el nombre y el apellido del cliente que efectuó la compra, aunque
 
 Expone cuántos productos diferentes existen en el pedido (sin considerar la cantidad comprada de cada ítem). Al pasar el ratón es posible ver cuáles fueron los productos comprados.
 
-![oms produtos do pedido](//images.contentful.com/alneenqid6w5/4fTIEf2ywwc2U2IuwSkg8U/82b81b00387db8959cf18ae392e5e1f0/oms-produtos-do-pedido.png)
+![oms produtos do pedido](https://images.contentful.com/alneenqid6w5/4fTIEf2ywwc2U2IuwSkg8U/82b81b00387db8959cf18ae392e5e1f0/oms-produtos-do-pedido.png)
 
 ## Valor
 
diff --git a/docs/tutorials/es/overview-pricing-module.md b/docs/tutorials/es/overview-pricing-module.md
index 5976d4771..2f27d5dc4 100644
--- a/docs/tutorials/es/overview-pricing-module.md
+++ b/docs/tutorials/es/overview-pricing-module.md
@@ -21,7 +21,7 @@ Hay tres departamentos dentro del módulo que son responsables de la configuraci
 
 ## Audiencia de Campañas
 
-![campanha-es](//images.ctfassets.net/alneenqid6w5/78eGGuLQ9U5X8nJd21K46T/16b42ea9ae089696a8fab6986cf078ee/campanha-es.png)
+![campanha-es](https://images.ctfassets.net/alneenqid6w5/78eGGuLQ9U5X8nJd21K46T/16b42ea9ae089696a8fab6986cf078ee/campanha-es.png)
 
 La audiencia de campañas es una forma de definir el público objetivo al que una promoción puede ser aplicada. Es decir, usted puede crear segmentos de clientes basados en la definición de algunos criterios que serán elegibles para una determinada audiencia de campaña y consecuentemente a una o más promociones. Una audiencia de campaña puede asociarse a una o más [promociones de audiencias de campañas](https:///tutorial/promocao-de-campanha?locale=es "Crear promoción de campaña").
 
@@ -29,7 +29,7 @@ La audiencia de campañas es una forma de definir el público objetivo al que un
 
 ## Promociones
 
-![promoções.es](//images.ctfassets.net/alneenqid6w5/1zFONiDeeUvKA1Cyj5zY1c/dc438c0f2f3a786b3efceb8665ecde57/promo____es.es.png)
+![promoções.es](https://images.ctfassets.net/alneenqid6w5/1zFONiDeeUvKA1Cyj5zY1c/dc438c0f2f3a786b3efceb8665ecde57/promo____es.es.png)
 
 Aquí es donde los descuentos que su tienda va a ofrecer se crean. Usted también puede ver, filtrar, buscar y archivar todas las promociones. De acuerdo con la configuración de cada tienda, existe un límite de promociones que pueden estar activas al mismo tiempo. 
 
@@ -44,12 +44,12 @@ Para comprobar esta cantidad, observe el mensaje que aparece en la esquina super
 
 ## Cupones
 
-![cupons.es](//images.ctfassets.net/alneenqid6w5/6DMoadJ7T4npiiWir48bCQ/ce25ad3832e5098993ed05eb06cb7d84/cupons.es.png)
+![cupons.es](https://images.ctfassets.net/alneenqid6w5/6DMoadJ7T4npiiWir48bCQ/ce25ad3832e5098993ed05eb06cb7d84/cupons.es.png)
 
 Es en esta sección que se crean los cupones. Usted también puede recogerlos y archivarlos. [Aprenda cómo crear cupones](/es/tutorial/crear-cupon-de-descuento).
 
 ## Impuestos
 
-![taxas.es](//images.ctfassets.net/alneenqid6w5/2pHx00EwpCj3fatVpnfPui/83121098980fd0f608d9d808a4acd417/taxas.es.png)
+![taxas.es](https://images.ctfassets.net/alneenqid6w5/2pHx00EwpCj3fatVpnfPui/83121098980fd0f608d9d808a4acd417/taxas.es.png)
 
 En esta área se crearán los impuestos que inciden sobre sus productos. También se permite filtrar, buscar y archivar las tasas. [Entienda mejor las particularidades de esta configuración en el artículo sobre tasas](/es/tutorial/creando-la-tasaimpuesto).
diff --git a/docs/tutorials/es/pages-overview.md b/docs/tutorials/es/pages-overview.md
index 640011cd1..3ab0431ba 100644
--- a/docs/tutorials/es/pages-overview.md
+++ b/docs/tutorials/es/pages-overview.md
@@ -25,7 +25,7 @@ En Páginas, también puedes crear redirecciones de URL para redirigir a los vis
 
 En el Admin VTEX, accede **Storefront > Páginas** y descubre las principales herramientas disponibles en la interfaz.
 
-![Páginas UI - ES](//images.ctfassets.net/alneenqid6w5/p6829cewqlsLC0XfCnHsC/dc75d5dcbe1d3ff9d02d710718961fba/pages-ui-es.png)
+![Páginas UI - ES](https://images.ctfassets.net/alneenqid6w5/p6829cewqlsLC0XfCnHsC/dc75d5dcbe1d3ff9d02d710718961fba/pages-ui-es.png)
 
 | **Herramienta** | **Descripción** |
 | ---------- | ---------- |
diff --git a/docs/tutorials/es/partner-program-intranet-and-vtex-store-manual.md b/docs/tutorials/es/partner-program-intranet-and-vtex-store-manual.md
index ba1de9a00..7f29c988a 100644
--- a/docs/tutorials/es/partner-program-intranet-and-vtex-store-manual.md
+++ b/docs/tutorials/es/partner-program-intranet-and-vtex-store-manual.md
@@ -21,40 +21,40 @@ El acceso URL: http://extrato.vtex.com
 
 ## Datos de registro
 Este es el primer paso. En él deberá completar todos los datos de registro de su agencia, los cuales serán replicados en el VTEX STORE.
-![partner intranet 1](//images.contentful.com/alneenqid6w5/6n5cqrsG3uEuqE0w88882M/87f7eb33ae50e6d0783dc1ea5a121aca/partner_intranet_1.png)
+![partner intranet 1](https://images.contentful.com/alneenqid6w5/6n5cqrsG3uEuqE0w88882M/87f7eb33ae50e6d0783dc1ea5a121aca/partner_intranet_1.png)
 
 ### Color del header
 En el primer paso tenemos algunos campos que requieren atención, como por ejemplo el color del header. ¿Dónde se solicita? En el VTEX STORE dentro de la página de su agencia como se muestra a continuación.
-![partner intranet 2](//images.contentful.com/alneenqid6w5/13tICp7cXoiOseM2AOYYEc/aaf98faa4e33f47e517f2204fec9dcd2/partner_intranet_2.png)
+![partner intranet 2](https://images.contentful.com/alneenqid6w5/13tICp7cXoiOseM2AOYYEc/aaf98faa4e33f47e517f2204fec9dcd2/partner_intranet_2.png)
 
 ### Oficinas
 El segundo punto que merece atención es el registro de oficinas, ej: São Paulo, Salvador o fuera de Brasil. Para cada oficina registrada deberá ser hecho el registro de los servicios prestados. Atención: deben ser oficinas físicas locales.
-![partner intranet 3](//images.contentful.com/alneenqid6w5/6JZIkI0N5SKgySUW46W2Yc/64069026123057856b3430bf4e4e5344/partner_intranet_3.png)
+![partner intranet 3](https://images.contentful.com/alneenqid6w5/6JZIkI0N5SKgySUW46W2Yc/64069026123057856b3430bf4e4e5344/partner_intranet_3.png)
 
 ## Mi equipo
 En este paso se registrarán todas las personas de su agencia que deben tener acceso a nuestro ambiente de capacitación y certificación VTEX Partner. (VTEX Academy)
-![partner intranet 4](//images.contentful.com/alneenqid6w5/4AmT9EOi6AC6CUIa6gK8uq/c79b462dad40ededc388903d6de2535c/partner_intranet_4.png)
+![partner intranet 4](https://images.contentful.com/alneenqid6w5/4AmT9EOi6AC6CUIa6gK8uq/c79b462dad40ededc388903d6de2535c/partner_intranet_4.png)
 
 ## Certificaciones
 Una vez que su equipo se certifique, es necesario informar cuales certificaciones que usted Partner posee. Es importante resaltar que VTEX verificará la existencia de dichas certificaciones. En caso de tenerlas, será exhibido conforme la lupa que aparece al lado.
-![partner intranet 5](//images.contentful.com/alneenqid6w5/1Iq4VXwlUQimW0kQmqsIe8/9038bd2510ba516cbc72596a41d7a25f/partner_intranet_5.png)
+![partner intranet 5](https://images.contentful.com/alneenqid6w5/1Iq4VXwlUQimW0kQmqsIe8/9038bd2510ba516cbc72596a41d7a25f/partner_intranet_5.png)
 
 ## Servicios
 En este paso se deben registrar los servicios proporcionados por su agencia, los cuales agrupamos en: Creación e Implementación de layout, gestión de proyectos y el soporte en ongoing. Estos servicios van a aparecer en el VTEX STORE para los clientes VTEX.
-![partner intranet 6](//images.contentful.com/alneenqid6w5/1x3zqdaxMgGU4CKsKi4i8c/8484f7197c8643388a716e0e595f9763/partner_intranet_6.png)
+![partner intranet 6](https://images.contentful.com/alneenqid6w5/1x3zqdaxMgGU4CKsKi4i8c/8484f7197c8643388a716e0e595f9763/partner_intranet_6.png)
 
 ### VTEX Store
 Al lado podemos ver la vitrina de servicios / soluciones de acuerdo con lo que fue escogido.
-![partner intranet 7](//images.contentful.com/alneenqid6w5/3jJA8IyIkgcEmSYy8W6wam/34407ce97bfcc75431fdc9960d91fd2b/partner_intranet_7.png)
+![partner intranet 7](https://images.contentful.com/alneenqid6w5/3jJA8IyIkgcEmSYy8W6wam/34407ce97bfcc75431fdc9960d91fd2b/partner_intranet_7.png)
 
 ## Extracto
 Y en el extracto, quien es responsable por el financiero de la agencia, debe acompañar los valores de comisiones de reventa de la plataforma VTEX, que son liberadas apenas para las agencias certificadas Reseller.
-![partner intranet 8](//images.contentful.com/alneenqid6w5/2TB5pCAgr6qKqQmsuY0kgU/47bcbdbf15c7101612dddbc8901a8f99/partner_intranet_8.png)
+![partner intranet 8](https://images.contentful.com/alneenqid6w5/2TB5pCAgr6qKqQmsuY0kgU/47bcbdbf15c7101612dddbc8901a8f99/partner_intranet_8.png)
 
 ## Acceso a usuarios
 Aquí podrá registrar a todos los usuarios que tendrán acceso a esta herramienta. Sugerimos que se trate de una persona del financiero y una o dos personas como administradores.
-![partner intranet 9](//images.contentful.com/alneenqid6w5/2aFx9YxuAMOEAEIOOos6Gg/82e8c287becc9b2ccbd9590ce4a6fb6e/partner_intranet_9.png)
+![partner intranet 9](https://images.contentful.com/alneenqid6w5/2aFx9YxuAMOEAEIOOos6Gg/82e8c287becc9b2ccbd9590ce4a6fb6e/partner_intranet_9.png)
 
 ## Canales VTEX
 En el menú superior se pueden ver todos nuestros canales de comunicación con nuestros partners.
-![partner intranet 10](//images.contentful.com/alneenqid6w5/5Pa8OjOuyWwigKwmqCSK66/96fb124b8400feb3abd78317be03037c/partner_intranet_10.png)
+![partner intranet 10](https://images.contentful.com/alneenqid6w5/5Pa8OjOuyWwigKwmqCSK66/96fb124b8400feb3abd78317be03037c/partner_intranet_10.png)
diff --git a/docs/tutorials/es/payment-provider-protocol.md b/docs/tutorials/es/payment-provider-protocol.md
index 0f1a03705..9b8b449b2 100644
--- a/docs/tutorials/es/payment-provider-protocol.md
+++ b/docs/tutorials/es/payment-provider-protocol.md
@@ -95,7 +95,7 @@ Hay casos en que se pueden crear conectores para atender alguna solución espec
 
 Después de recibir los datos de acceso e implementar el backend, el proveedor debe instalar la aplicación Payment Provider Test Suite para acceder a la herramienta de pruebas. La instalación se realiza a través de la VTEX App Store.
 
-![ppp-vtex-store-es](//images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/aa2d1e30c83c7d35c7313c112a5b69d1/image.png)
+![ppp-vtex-store-es](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/aa2d1e30c83c7d35c7313c112a5b69d1/image.png)
 
 <div class="alert alert-warning">
 <p>
@@ -149,7 +149,7 @@ Después de rellenar URL de servicio, Test Suite validará el  [Endpoint Manifes
 
 En esta sección, debes seleccionar los casos que deseas probar. Si estás probando un medio de tarjeta de crédito, tu integración debe pasar los casos Aprobado, Denegado, Cancelación, Aprobado asíncrono y Denegado asíncrono. Los medios de pago con [redirección](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows#redirect) solo necesitan el Flujo de redirección.
 
-![ppp-config-es](//images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/f15364fc9a837883d8d1f022fe646014/image.png)
+![ppp-config-es](https://images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/f15364fc9a837883d8d1f022fe646014/image.png)
 
 ### 4. Pruebas
 Cuando haces clic en el botón `Ejecutar prueba`, Test Suite llama la URL de servicio proporcionada y ejecuta los casos de prueba seleccionados. Las pruebas son:
@@ -179,18 +179,18 @@ Para identificar cómo responder a cada una de las pruebas con tarjetas de créd
 
 Después de ejecutar las pruebas, el sistema mostrará el Informe de prueba que presenta los resultados detallados de cada caso de prueba. De este modo, tendrás más visibilidad sobre lo que debes ajustar si se produce un error.
 
-![Payment Provider Test Suite 2_ES](//images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/6d5d097d5f50587f6a69d8932a81f78f/Payment_Provider_Test_Suite_2_ES.JPG)
+![Payment Provider Test Suite 2_ES](https://images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/6d5d097d5f50587f6a69d8932a81f78f/Payment_Provider_Test_Suite_2_ES.JPG)
 
 Para ver los mensajes transmitidos entre Test Suite y la implementación de tu proveedor de pagos, haz clic en el botón Inspeccionar logs. Se abrirá una ventana modal que muestra la lista de mensajes transmitidos y la carga de cada request y respuesta. El botón situado en la esquina superior derecha de la sección de código facilita la copia del código al portapapeles.
 
-![Payment Provider Test Suite Logs_ES](//images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/9f1a6c56c4c53d51a3e403b4665338dc/Payment_Provider_Test_Suite_Logs_ES.JPG)
+![Payment Provider Test Suite Logs_ES](https://images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/9f1a6c56c4c53d51a3e403b4665338dc/Payment_Provider_Test_Suite_Logs_ES.JPG)
 
 ## Flujo del protocolo de pago
 Aquí vamos a explicar el flujo de pago integrado en detalle. La siguiente imagen muestra todo el flujo, mostrando VTEX Payments y las responsabilidades de su proveedor.
 
 Todo comienza con la solicitud de un nuevo pago, después de la creación de un nuevo pedido. VTEX crea una nueva representación del pago y avanza para el procesamiento de los pagos.
 
-![fluxo-atualizado-ppp](//images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
 
 <div class="alert alert-info">
   El período predeterminado de 7 días para reintentos (retries) de pago asíncronos solo se aplica cuando el usuario no especifica un valor en el campo <code>delayToCancel</code> del endpoint <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> o al enviar la URL de devolución de llamada.</div>
@@ -207,7 +207,7 @@ En cualquiera de los casos, una vez que termine el procesamiento y el proveedor
 
 El flujo completo con status undefined y uso de notificación se puede ver a continuación:
 
-![Payment authorization callback notification flow](//images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/39a8e76973fe6127741c1a34b9230c82/image1.png)
+![Payment authorization callback notification flow](https://images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/39a8e76973fe6127741c1a34b9230c82/image1.png)
 
 1. La autorización del pago se inicia cuando el _gateway_ hace una llamada al endpoint Create Payment (__/payment__) para el proveedor. El campo `callbackUrl` se envía dentro del cuerpo del _request_ y contiene la URL para hacer la notificación.
 2. El pago se produce de forma asíncrona (no genera el status definitivo cuando se inicia la transacción). A continuación, el _gateway_ recibe la respuesta con status __undefined__ y espera a que se complete el procesamiento del pago. Más adelante, el pago se completará y el _gateway_ recibirá el status definitivo (__approved__ o __denied__).
@@ -216,7 +216,7 @@ El flujo completo con status undefined y uso de notificación se puede ver a con
 
 El flujo completo con status __undefined__ y uso del __retry__ se puede ver a continuación:
 
-![Payment authorization callback retry flow](//images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/b78e54e17e7971aa4385f025b8eca4a4/image2.png)
+![Payment authorization callback retry flow](https://images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/b78e54e17e7971aa4385f025b8eca4a4/image2.png)
 
 1. La autorización del pago se inicia cuando el _gateway_ hace una llamada al _endpoint_ Create Payment (__/payment__) para el proveedor. El campo `callbackUrl` se envía dentro del cuerpo del _request_ y contiene la URL del endpoint __retry__.
 2. El pago se produce de forma asíncrona (no genera el status definitivo cuando se inicia la transacción). A continuación, el _gateway_ recibe la respuesta con status __undefined__ y espera a que se complete el procesamiento del pago. Más adelante, el pago se completará y el _gateway_ recibirá el status definitivo (__approved__ o __denied__).
diff --git a/docs/tutorials/es/payu-romania-refund-details.md b/docs/tutorials/es/payu-romania-refund-details.md
index 0898c1626..da0c201d6 100644
--- a/docs/tutorials/es/payu-romania-refund-details.md
+++ b/docs/tutorials/es/payu-romania-refund-details.md
@@ -38,7 +38,7 @@ Si el botón Eliminar no está activo y el tiempo de espera no ha caducado, pued
 
 Si el sistema ya ha enviado la solicitud de reembolso o anulación al banco emisor, ya no podremos eliminarlo / detenerlo de ninguna manera.
 
-![PayU Romania](//images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
+![PayU Romania](https://images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
 
 Una vez que PayU haya enviado la solicitud de cancelación o reembolso al banco emisor, el estado de la orden se actualizará en el panel de PayU como "REVERSE" (para anulaciones) o "REFUND". Y VTEX va a recibir un webhook de PaymentsOS, por lo que el estado del pedido también puede actualizarse en la plataforma (en Pagos y, por lo tanto, reflejado en el OMS).
 
diff --git a/docs/tutorials/es/pci-gateway-overview.md b/docs/tutorials/es/pci-gateway-overview.md
index 4610e9e3c..37d16130f 100644
--- a/docs/tutorials/es/pci-gateway-overview.md
+++ b/docs/tutorials/es/pci-gateway-overview.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 **Pagos** es el módulo responsable por intermediar y gestionar todas las transacciones y pagos entre su tienda VTEX, operadoras financieras y sus clientes. En él usted hace consultas como status de las transacciones, extornos, cancelaciones, liquidaciones y también configuraciones como condiciones para las formas de pago.
 
-![new-admin-pagos](//images.ctfassets.net/alneenqid6w5/CPFZboq2pqOUSI0CAuQgW/bb254d7dd631b1983cb4fb6e7d01f244/NEW_ADMIN_PAGAMENTOS_ES.png)
+![new-admin-pagos](https://images.ctfassets.net/alneenqid6w5/CPFZboq2pqOUSI0CAuQgW/bb254d7dd631b1983cb4fb6e7d01f244/NEW_ADMIN_PAGAMENTOS_ES.png)
 
 # Empezando a usar
 
diff --git a/docs/tutorials/es/permissions-management-in-b2b-suite.md b/docs/tutorials/es/permissions-management-in-b2b-suite.md
index 94bf1c50c..4b84e470c 100644
--- a/docs/tutorials/es/permissions-management-in-b2b-suite.md
+++ b/docs/tutorials/es/permissions-management-in-b2b-suite.md
@@ -61,6 +61,6 @@ Para gestionar roles y permisos de aplicaciones, configura los permisos siguiend
 
 5. Haz clic en `Guardar`.
 
-![Gerenciamento de permissões - ES](//images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/fdf3c362f0300198da41af04681d3239/Gerenciamento_de_permiss_es_-_ES.gif)
+![Gerenciamento de permissões - ES](https://images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/fdf3c362f0300198da41af04681d3239/Gerenciamento_de_permiss_es_-_ES.gif)
 
 Después de asociar los perfiles con los roles deseados, puedes atribuir funciones a los usuarios. Para más información, consulta [B2B Organizations](https://developers.vtex.com/docs/guides/vtex-b2b-organizations#users).
diff --git a/docs/tutorials/es/physical-store-instore-beta.md b/docs/tutorials/es/physical-store-instore-beta.md
index 82695406e..31c8835b3 100644
--- a/docs/tutorials/es/physical-store-instore-beta.md
+++ b/docs/tutorials/es/physical-store-instore-beta.md
@@ -28,7 +28,7 @@ Esta página te permite realizar las siguientes acciones:
 * [Editar](#editar-tienda)
 * [Eliminar](#eliminar-tienda)
 
-![loja-fisica-ES](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
+![loja-fisica-ES](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/df72ba565c1eff2f92a4b6b74f27ad8d/image.png)
 
 La página contiene la siguiente información:
 
@@ -53,7 +53,7 @@ Puedes crear una tienda física siguiendo los pasos a continuación:
 
 ### Campos de registro de la tienda física
 
-![loja-fisica2-es](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
+![loja-fisica2-es](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/d27ac78354af709db771a00656578353/image.png)
 
 #### Identificación
 
diff --git a/docs/tutorials/es/pickup-points-for-subscription-orders.md b/docs/tutorials/es/pickup-points-for-subscription-orders.md
index e61f200ca..d422511d2 100644
--- a/docs/tutorials/es/pickup-points-for-subscription-orders.md
+++ b/docs/tutorials/es/pickup-points-for-subscription-orders.md
@@ -41,7 +41,7 @@ Para habilitar los puntos de recogida para los pedidos de suscripción, se deben
 
 El cliente final puede elegir los puntos de recogida para ítems de un pedido de suscripción cuando realiza el _checkout_, como se muestra en la siguiente imagen.
 
-![subscriptionspickup ES](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
+![subscriptionspickup ES](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/0be6afd36b5bb8966096600810768bbe/subscriptionspickup_ES.gif)
 
 También puede asignar puntos de recogida al [crear nuevas suscripciones](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#post_api-rns-pub-subscriptions) a través de la [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1). En el caso de las suscripciones existentes, puede modificar la dirección de entrega a través de la [ruta de actualización de suscripciones de la API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#patch_api-rns-pub-subscriptions-id) para empezar a utilizar un punto de recogida.
 
diff --git a/docs/tutorials/es/pickup-points.md b/docs/tutorials/es/pickup-points.md
index d56f3dc3a..c8cc678a0 100644
--- a/docs/tutorials/es/pickup-points.md
+++ b/docs/tutorials/es/pickup-points.md
@@ -68,7 +68,7 @@ VTEX considera que el punto de recogida es una forma de envío. Es por eso que l
     - Paso 2: Haz clic en la pestaña **Políticas de envío**, selecciona la política de envío creada para el punto de recogida.
     - Paso 3: En la columna **Acciones**, haz clic en el ícono <i class="fas fa-pen"></i> para editar.
     - Paso 4: Activa el botón <i class="fas fa-toggle-on"></i> del campo **Asociar puntos de recogida**.
-    - Paso 5: Selecciona el punto de recogida mediante los campos disponibles.![relacionarpontosretiradaES](//images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/d72f0278d6fdbb3041d883fa4685f436/relacionarpontosretiradaES.png) <div class = "alert alert-info">Para las tiendas que tienen más de 50 puntos de recogida, recomendamos utilizar el campo Tags de <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140#registrar-politica-de-envio">los puntos de recogida al crear un punto de recogida</a>. Utilizar tags facilita la búsqueda de los puntos de recogida al asociarlos con la política de envío.También recuerda que la política de envío que está asociada a un punto de recogida no estará disponible para otros tipos de envíos. Recomendamos crear una política de envío dedicada al punto de recogida.</div>
+    - Paso 5: Selecciona el punto de recogida mediante los campos disponibles.![relacionarpontosretiradaES](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/d72f0278d6fdbb3041d883fa4685f436/relacionarpontosretiradaES.png) <div class = "alert alert-info">Para las tiendas que tienen más de 50 puntos de recogida, recomendamos utilizar el campo Tags de <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140#registrar-politica-de-envio">los puntos de recogida al crear un punto de recogida</a>. Utilizar tags facilita la búsqueda de los puntos de recogida al asociarlos con la política de envío.También recuerda que la política de envío que está asociada a un punto de recogida no estará disponible para otros tipos de envíos. Recomendamos crear una política de envío dedicada al punto de recogida.</div>
 
 4. [Registrar la geolocalización](https://help.vtex.com/es/tutorial/gestionar-geolocalizacion--tutorials_138): para una mayor precisión de la ubicación de los puntos de recogida en el _checkout_.<div class = "alert alert-info">La visualización de los puntos de recogida con el mapa y la hora en el checkout solo está disponible para Checkout V6.</div>
 
@@ -76,7 +76,7 @@ VTEX considera que el punto de recogida es una forma de envío. Es por eso que l
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Checkout**, o escribe *Checkout* en la barra de búsqueda en la parte superior de la página.  
     - Paso 2: Selecciona la configuración utilizada en la tienda y haz clic en el ícono <i class="fas fa-cog"></i>.
     - Paso 3: Haz clic en la pestaña **Checkout** en la barra superior.
-    - Paso 4: Selecciona el botón <i class="fas fa-toggle-on"></i> del campo **Dirección de la factura para recogida en la tienda**. ![NFpontoretiradaES](//images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/c81afd5e90d05deec1684dba401f569e/NFpontoretiradaES.png)<div class="alert alert-warning">La opción de <b>Dirección en la factura para recogida en la tienda</b> debe estar habilitada en todas las tiendas en Brasil, ya que es requisito que la factura emitida contenga la información de la dirección del cliente, incluso si la opción de entrega de el pedido está en el punto de recogida. La dirección ingresada por el cliente se registrará en el campo `invoiceData` del <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - Paso 4: Selecciona el botón <i class="fas fa-toggle-on"></i> del campo **Dirección de la factura para recogida en la tienda**. ![NFpontoretiradaES](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/c81afd5e90d05deec1684dba401f569e/NFpontoretiradaES.png)<div class="alert alert-warning">La opción de <b>Dirección en la factura para recogida en la tienda</b> debe estar habilitada en todas las tiendas en Brasil, ya que es requisito que la factura emitida contenga la información de la dirección del cliente, incluso si la opción de entrega de el pedido está en el punto de recogida. La dirección ingresada por el cliente se registrará en el campo `invoiceData` del <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
 
 6. Para configurar la cantidad de puntos de recogida que se muestran en el checkout:
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Envío > Configuración**, o escribe *Envío* en la barra de búsqueda en la parte superior de la página, y haga clic en *Configuración de la tienda / Envío*.    
diff --git a/docs/tutorials/es/planner-calendar-page-beta.md b/docs/tutorials/es/planner-calendar-page-beta.md
index d03773b09..56355e857 100644
--- a/docs/tutorials/es/planner-calendar-page-beta.md
+++ b/docs/tutorials/es/planner-calendar-page-beta.md
@@ -38,7 +38,7 @@ El **Calendario** muestra solamente [releases programados](https://help.vtex.com
 
 La imagen a continuación muestra la vista por mes y señala qué puedes hacer en esta interfaz:
 
-![releases-calendar-monthly-view-es](//images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/8b589697f708bf34d7eac2b15c832b67/releases-calendar-monthly-view-es.png)
+![releases-calendar-monthly-view-es](https://images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/8b589697f708bf34d7eac2b15c832b67/releases-calendar-monthly-view-es.png)
 
 En esta pantalla, puedes:
 
@@ -56,7 +56,7 @@ En esta pantalla, puedes:
 
 La imagen a continuación muestra la vista por semana y señala qué puedes hacer en esta interfaz:
 
-![releases-calendar-weekly-view-es](//images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/56000b0f86260f9e461695eab592be75/releases-calendar-weekly-view-es.png)
+![releases-calendar-weekly-view-es](https://images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/56000b0f86260f9e461695eab592be75/releases-calendar-weekly-view-es.png)
 
 En esta pantalla, puedes:
 
@@ -74,7 +74,7 @@ En esta pantalla, puedes:
 
 La imagen a continuación muestra la vista por día y señala qué puedes hacer en esta interfaz:
 
-![daily view v2 es](//images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/91fa4db8315a31fdf1187edf74e19d61/daily_view_v2_es.png)
+![daily view v2 es](https://images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/91fa4db8315a31fdf1187edf74e19d61/daily_view_v2_es.png)
 
 Además de ver información sobre el release, en esta pantalla, puedes:
 
diff --git a/docs/tutorials/es/planner-releases-page-beta.md b/docs/tutorials/es/planner-releases-page-beta.md
index 20bf05ceb..45307a25a 100644
--- a/docs/tutorials/es/planner-releases-page-beta.md
+++ b/docs/tutorials/es/planner-releases-page-beta.md
@@ -36,7 +36,7 @@ El orden de los releases programados se basa en la fecha de publicación: cuanto
 
 Para acceder a la página **Releases** en el Admin VTEX, dirígete al menú de navegación del **Releases**. La imagen a continuación muestra la interfaz e identifica qué puedes hacer en ella:
 
-![Releases list view v3 - ES](//images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/94f9712e23df3f3e28c126acd4367d8f/Releases_list_view_v3_-_ES.png)
+![Releases list view v3 - ES](https://images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/94f9712e23df3f3e28c126acd4367d8f/Releases_list_view_v3_-_ES.png)
 
 | **Campo** | **Descripción** |
 |---|---|
diff --git a/docs/tutorials/es/price-divergence-rule.md b/docs/tutorials/es/price-divergence-rule.md
index dd749f188..2597b77da 100644
--- a/docs/tutorials/es/price-divergence-rule.md
+++ b/docs/tutorials/es/price-divergence-rule.md
@@ -29,7 +29,7 @@ La regla de Divergencia de precios se compone de una o varias reglas de autoriza
 - **Negar automáticamente:** los pedidos con una diferencia de precio dentro del rango definido se rechazan automáticamente y no se integran.
 - **Crear una tarea en VTEX DO para aprobación:** para diferencias de precio dentro del rango configurado, el pedido se integra pero queda pendiente de [autorización manual](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#autorizar-pedidos-manualmente) por parte de un usuario autorizado.
 
-![price_divergence_rules_ES](//images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/8563ada94d5218580e946f92f1f7b210/price_divergence_rules_ES.png)
+![price_divergence_rules_ES](https://images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/8563ada94d5218580e946f92f1f7b210/price_divergence_rules_ES.png)
 
 Cuando no se ha [configurado la regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), los pedidos con errores de divergencia de precios se aprueban automáticamente. Esto se aplica a los _marketplaces_ VTEX, a los _marketplaces_ externos y a los conectores certificados (_partners_), pero no a los [conectores nativos](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex).
 
diff --git a/docs/tutorials/es/price-divergence-rules-beta.md b/docs/tutorials/es/price-divergence-rules-beta.md
index eef1906c5..39305bd8c 100644
--- a/docs/tutorials/es/price-divergence-rules-beta.md
+++ b/docs/tutorials/es/price-divergence-rules-beta.md
@@ -23,7 +23,7 @@ Las integraciones entre los sellers VTEX y los [conectores nativos](https://help
 
 Los pedidos que presentan errores por divergencia de valores mayores que los valores configurados en la integración con el marketplace, no se cargan automáticamente en el OMS. Por tanto, permanecen con el status de error en la sección `Pedidos` del módulo *INTEGRACIONES* del Admin, a la espera de ser reprocesados manualmente.
 
-![divergenciadepreçosES-01](//images.contentful.com/alneenqid6w5/2he3DSbVXaIpDMuAQu4094/66781d82b678c9b312bbd508cc6c2b92/divergenciadepre__osES-01.gif)
+![divergenciadepreçosES-01](https://images.contentful.com/alneenqid6w5/2he3DSbVXaIpDMuAQu4094/66781d82b678c9b312bbd508cc6c2b92/divergenciadepre__osES-01.gif)
 
 Para que los pedidos con divergencia de valores se carguen al OMS, se creó la regla de autorización (Beta). En esta regla, todos los pedidos con divergencia de valores se envían al OMS y deben ser aprobados manualmente por el administrador de la tienda, con el email registrado en *Gestión de la cuenta > Cuenta*. Se puede tener más de un email registrado.
 
@@ -45,7 +45,7 @@ Hay dos opciones de configuración en la regla de autorización:
 
 ### Crear reglas
 
-![barra regradivergenciaES](//images.contentful.com/alneenqid6w5/31XPGn5RQPGtJRoaXabiRL/16f13095fe5760e51d249d7b55f18f80/barra_regradivergenciaES.JPG)
+![barra regradivergenciaES](https://images.contentful.com/alneenqid6w5/31XPGn5RQPGtJRoaXabiRL/16f13095fe5760e51d249d7b55f18f80/barra_regradivergenciaES.JPG)
 
 Para crear las reglas, realice los siguientes pasos:
 
@@ -78,7 +78,7 @@ Para editar las reglas existentes, realice los siguientes pasos:
 6. Edite la regla que desee modificando la barra de porcentaje.
 7. Haga clic en `Guardar reglas`.
 
-![divergenciadepreçosES-02](//images.contentful.com/alneenqid6w5/2AUFOv0VJLYU5hJvBUgSfH/75f22616f278d53efacd9457ff737e38/divergenciadepre__osES-02.gif)
+![divergenciadepreçosES-02](https://images.contentful.com/alneenqid6w5/2AUFOv0VJLYU5hJvBUgSfH/75f22616f278d53efacd9457ff737e38/divergenciadepre__osES-02.gif)
 
 ## Autorización de pedidos 
 
@@ -101,7 +101,7 @@ Para autorizar manualmente los pedidos, realice los siguientes pasos:
 4. Seleccione el pedido que tiene el status `Esperando autorización manual` que desea autorizar.
 5. Haga clic en `Confirmar pedido`.
 
-![divergenciadepreçosES-03](//images.contentful.com/alneenqid6w5/3dNZ1HQF0Nl979OmPkszEv/56de42e69dea0dea0efed9630c054a8d/divergenciadepre__osES-03.gif)
+![divergenciadepreçosES-03](https://images.contentful.com/alneenqid6w5/3dNZ1HQF0Nl979OmPkszEv/56de42e69dea0dea0efed9630c054a8d/divergenciadepre__osES-03.gif)
 
 ### Autorización por VTEX DO
 
@@ -115,4 +115,4 @@ Para autorizar manualmente los pedidos, realice los siguientes pasos:
 6. Haga clic en `Cerrar`.
 7. Haga clic en `Autorizar`.
 
-![divergenciadepreçosES-04](//images.contentful.com/alneenqid6w5/3yOoU6kEwFcMZAEZC0tAvA/a84b0c0fbdb948e93a9dfdf2b8b22c1e/divergenciadepre__osES-04.gif)
+![divergenciadepreçosES-04](https://images.contentful.com/alneenqid6w5/3yOoU6kEwFcMZAEZC0tAvA/a84b0c0fbdb948e93a9dfdf2b8b22c1e/divergenciadepre__osES-04.gif)
diff --git a/docs/tutorials/es/price-waterfall.md b/docs/tutorials/es/price-waterfall.md
index 024510eff..b131acdeb 100644
--- a/docs/tutorials/es/price-waterfall.md
+++ b/docs/tutorials/es/price-waterfall.md
@@ -21,7 +21,7 @@ Con esta nueva feature, tenemos ahora una nueva entidad de precio llamada *Preci
 
 El siguiente gráfico explica cómo funciona la cascada de precios:
 
-![tabelapreco.es](//images.ctfassets.net/alneenqid6w5/2rzzOs9CVogu74GM8Sih9s/9d095bddd449170787604aa602c9bb64/tabelapreco.es.png)
+![tabelapreco.es](https://images.ctfassets.net/alneenqid6w5/2rzzOs9CVogu74GM8Sih9s/9d095bddd449170787604aa602c9bb64/tabelapreco.es.png)
 
 Cuando un precio para un SKU se solicita al módulo de precios:
 1. Un *Precio fijo* se selecciona segun sus criterios como **programación** y **cantidad mínima**.
diff --git a/docs/tutorials/es/pricing-rules-v2.md b/docs/tutorials/es/pricing-rules-v2.md
index 33c237537..09f8f45fc 100644
--- a/docs/tutorials/es/pricing-rules-v2.md
+++ b/docs/tutorials/es/pricing-rules-v2.md
@@ -20,7 +20,7 @@ Las funcionalidades descritas en este artículo todavía no están disponibles
 
 Una regla de precio es un modificador del precio base registrado en la Lista de precios.
 
-![new-dashboard-pricing-es](//images.contentful.com/alneenqid6w5/3EB6csYrKUiwQGGuikW0MA/ada36ea5a53b0d864561093817b76bf9/new-dashboard-pricing-es.gif)
+![new-dashboard-pricing-es](https://images.contentful.com/alneenqid6w5/3EB6csYrKUiwQGGuikW0MA/ada36ea5a53b0d864561093817b76bf9/new-dashboard-pricing-es.gif)
 
 ## Como funciona
 
@@ -34,7 +34,7 @@ Más allá de esto, es importante resaltar que las reglas de precios se aplican
 
 Será aplicada **sólo la primera** regla de precio que sea válida para as condiciones de SKU (categoría; marca; y rango de markup). Incluso si existen otras relas de precio válidas, apenas la primeira en el orden será utilizada para el cálculo del precio del SKU.
 
-![new-dashboard-pricing-rule-reordering-es](//images.contentful.com/alneenqid6w5/3qFR7a9G2kCO6IMSACoKki/be7a36609e25db3e3e4da99f5b116c71/new-dashboard-pricing-rule-reordering-es.gif)
+![new-dashboard-pricing-rule-reordering-es](https://images.contentful.com/alneenqid6w5/3qFR7a9G2kCO6IMSACoKki/be7a36609e25db3e3e4da99f5b116c71/new-dashboard-pricing-rule-reordering-es.gif)
 
 _Recomendamos que el orden parta de las reglas más específicas a las reglas más generales._
 
@@ -42,7 +42,7 @@ _Recomendamos que el orden parta de las reglas más específicas a las reglas m
 
 El paso a paso para el registro es bien simple, y está expuesto aquí:
 
-![new-dashboard-pricing-add-rule-es](//images.contentful.com/alneenqid6w5/1WE61W9Hvu8GMIoywGeqOG/97efe02874306a266793385ef984c32d/new-dashboard-pricing-add-rule-es.gif)
+![new-dashboard-pricing-add-rule-es](https://images.contentful.com/alneenqid6w5/1WE61W9Hvu8GMIoywGeqOG/97efe02874306a266793385ef984c32d/new-dashboard-pricing-add-rule-es.gif)
 
 1. En la pantalla **Reglas de precios** será exhibida una lista con todas las políticas comerciales. Dentro de cada una, estarán las reglas. Haga click en el botón **Nueva regla**, arriba de la lista para crear una regla.
 2. Elija en qué política comercial estará incluida esta regla.
@@ -53,8 +53,8 @@ El paso a paso para el registro es bien simple, y está expuesto aquí:
 
 Debajo se muestran ejemplos de los flujos de edición y exclusión de reglas de precio.
 
-![new-dashboard-pricing-edit-rule-es](//images.contentful.com/alneenqid6w5/61kaPdcYbCkwYGa0IeQoOg/5620702e4eb27233d0bbc8a3e60e7c11/new-dashboard-pricing-edit-rule-es.gif)
+![new-dashboard-pricing-edit-rule-es](https://images.contentful.com/alneenqid6w5/61kaPdcYbCkwYGa0IeQoOg/5620702e4eb27233d0bbc8a3e60e7c11/new-dashboard-pricing-edit-rule-es.gif)
 *Flujo de alteración de una regla*
 
-![new-dashboard-pricing-remove-rule-es](//images.contentful.com/alneenqid6w5/1iiu0BkGmgSC0Awgoacmq0/dedb479cfb8745277bad3e8f8d4e93ff/new-dashboard-pricing-remove-rule-es.gif)
+![new-dashboard-pricing-remove-rule-es](https://images.contentful.com/alneenqid6w5/1iiu0BkGmgSC0Awgoacmq0/dedb479cfb8745277bad3e8f8d4e93ff/new-dashboard-pricing-remove-rule-es.gif)
 *Fluxo de exclusión de una regla*
diff --git a/docs/tutorials/es/product-list.md b/docs/tutorials/es/product-list.md
index 6aa6e1027..3a9a6c353 100644
--- a/docs/tutorials/es/product-list.md
+++ b/docs/tutorials/es/product-list.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 La página **Productos** le permite ver y gestionar la lista completa de productos registrados en su tienda, lo que simplifica la gestión del catálogo en Seller Portal. Puede acceder a la página a través del menú **Catálogo** en el Admin VTEX.
 
-![product-list-es](//images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/2ae859a5052ac86fee7b4938ead9a6a8/product-list-es.png)
+![product-list-es](https://images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/2ae859a5052ac86fee7b4938ead9a6a8/product-list-es.png)
 
 Desde la lista de productos puede llevar a cabo varias acciones:
 
diff --git a/docs/tutorials/es/products-and-skus-beta.md b/docs/tutorials/es/products-and-skus-beta.md
index 505caa7c2..f840589ec 100644
--- a/docs/tutorials/es/products-and-skus-beta.md
+++ b/docs/tutorials/es/products-and-skus-beta.md
@@ -21,7 +21,7 @@ subcategory: 6XPsLadoT3moZ7eTduCg3c
 
 La página **Productos y SKUs** permite ver y gestionar toda la lista de productos registrados en la tienda, incluyendo la información de los SKU, fecha de actualización y status. Para acceder a la página, ve a **Catálogo > Productos y SKUs**. 
 
-![products-skus-es](//images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/1d07f47ff5411ae7b264cd9c74fbb21a/products-skus-es.png)
+![products-skus-es](https://images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/1d07f47ff5411ae7b264cd9c74fbb21a/products-skus-es.png)
 
 <div class="alert alert-info">
   <p>Esta página solo está disponible para las tiendas que operan con el <a href="https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">nuevo Admin VTEX</a>. Para acceder a esta página y formar parte de una nueva experiencia, únete al <a href="https://content.vtex.com/participe-do-programa-beta-es/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> del nuevo Admin VTEX.</p>
@@ -63,7 +63,7 @@ Para encontrar un producto específico, puedes ingresar uno de los siguientes da
 
 A continuación, haga clic en los criterios que desea utilizar para la búsqueda, como se ilustra en la imagen siguiente:
 
-![products-skus-search-es](//images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/e533bd234ce131fe2b6eb8f6705f77ba/search-es.gif)
+![products-skus-search-es](https://images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/e533bd234ce131fe2b6eb8f6705f77ba/search-es.gif)
 
 La lista de productos mostrados se actualizará en función de su búsqueda. 
 
@@ -103,7 +103,7 @@ Para ver el status de los SKU de un producto, consulta la sección [Ver la lista
 
 Al hacer clic en la flecha <i class="fas fa-chevron-right"></i> en la fila de un producto de la lista, la plataforma muestra una lista con todos los SKU registrados para ese producto.
 
-![sku-actions-es](//images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/5e99e7874f909914f6c489f40f336152/sku-actions-es.gif)
+![sku-actions-es](https://images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/5e99e7874f909914f6c489f40f336152/sku-actions-es.gif)
 
 En la lista de SKU, se puede ver la siguiente información:
 
@@ -148,7 +148,7 @@ Al hacer clic en el menú  de la fila de un producto y seleccionar **Ver detalle
 
 Esta pestaña de la ventana modal muestra la lista de SKU asociados al producto y sus detalles de indexación.
 
-![catalog-price-inventory-es](//images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/5c7748263994690cfb4ab39922ca19a9/preco-inventario-es.PNG)
+![catalog-price-inventory-es](https://images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/5c7748263994690cfb4ab39922ca19a9/preco-inventario-es.PNG)
 
 Al hacer clic en la flecha `>` en la fila de cada SKU, puedes ver una tabla con la siguiente información:
 
@@ -163,7 +163,7 @@ Al hacer clic en la flecha `>` en la fila de cada SKU, puedes ver una tabla con
 
 Esta pestaña de la ventana modal muestra el log, es decir, el registro técnico que detalla la indexación referente al producto y los SKU relacionados.
 
-![indexed-log-es](//images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/f1925d2f1b8ed02bae5b34254e8f7a39/log-indexacao-es.PNG)
+![indexed-log-es](https://images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/f1925d2f1b8ed02bae5b34254e8f7a39/log-indexacao-es.PNG)
 
 ## Más información
 
diff --git a/docs/tutorials/es/promotion-alerts-beta.md b/docs/tutorials/es/promotion-alerts-beta.md
index 301af1db5..6606c4d1c 100644
--- a/docs/tutorials/es/promotion-alerts-beta.md
+++ b/docs/tutorials/es/promotion-alerts-beta.md
@@ -29,7 +29,7 @@ Si solo se configura la acción de alerta por email, es posible que se realicen
 
 Para acceder a la página en el Admin VTEX, ve a *Promociones > Alerta de promociones*. Se mostrará la interfaz a continuación:
 
-![simuladordepromocoes gerenciar](//images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
+![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
 
 La siguiente tabla proporciona la descripción de las columnas de la lista de promociones:
 
diff --git a/docs/tutorials/es/promotion-list-beta.md b/docs/tutorials/es/promotion-list-beta.md
index bb933ebb0..fe985ca20 100644
--- a/docs/tutorials/es/promotion-list-beta.md
+++ b/docs/tutorials/es/promotion-list-beta.md
@@ -30,7 +30,7 @@ La página muestra la lista con las promociones registradas en tu tienda y su in
 | `Hasta` | Fecha de fin de la promoción.  |
 | `Status` | Status de la promoción, que puede ser: <p> __Activa:__ la promoción está activada.</p> <p>__Programada:__ la promoción está programada.</p> <p>__Pausada:__ la promoción está pausada. <p>__Completada:__ la promoción ha finalizado.</p> |
 
-![listadepromocoes es](//images.ctfassets.net/alneenqid6w5/223hOuKKb0a23uFeYIr7UU/ae1fa5b782b350cdda3458e28459d51e/listadepromocoes_es.gif)
+![listadepromocoes es](https://images.ctfassets.net/alneenqid6w5/223hOuKKb0a23uFeYIr7UU/ae1fa5b782b350cdda3458e28459d51e/listadepromocoes_es.gif)
 
 Puedes ordernar la lista de promociones por nombre, fechas o status. Para ordenarlas, haz clic en el título de la columna que tiene la información que deseas utilizar como criterio de ordenación.
 
@@ -82,7 +82,7 @@ El archivo contiene la siguiente información sobre cada promoción:
 
 ## Uso de las promociones
 
-![usodaspromoções en](//images.ctfassets.net/alneenqid6w5/51IiIaxilx3SqfVdRtiX1A/15a27215629ed81ae47e6582bd6d9261/usodaspromo____es_en.JPG)
+![usodaspromoções en](https://images.ctfassets.net/alneenqid6w5/51IiIaxilx3SqfVdRtiX1A/15a27215629ed81ae47e6582bd6d9261/usodaspromo____es_en.JPG)
 
 Para ver el total de promociones activas en tu tienda y el espacio restante para nuevas promociones, haz clic en <i class="fas fa-chart-line"></i> `Uso de las promociones`.
 
@@ -90,7 +90,7 @@ El número máximo de promociones activas por defecto es de 100. Si necesitas au
 
 ## Filtrar promociones
 
-![filtrodepromocoes es](//images.ctfassets.net/alneenqid6w5/6EuQui1lZ8MfnkvdvXh87S/2e90d2071d83698429988c2124acf67f/filtrodepromocoes_es.gif)
+![filtrodepromocoes es](https://images.ctfassets.net/alneenqid6w5/6EuQui1lZ8MfnkvdvXh87S/2e90d2071d83698429988c2124acf67f/filtrodepromocoes_es.gif)
 
 La lista de promociones se puede filtrar según tus necesidades, utilizando los siguientes filtros:  
 
diff --git a/docs/tutorials/es/promotion-summary.md b/docs/tutorials/es/promotion-summary.md
index 438aa84cb..e64807207 100644
--- a/docs/tutorials/es/promotion-summary.md
+++ b/docs/tutorials/es/promotion-summary.md
@@ -63,17 +63,17 @@ El resumen de la promoción puede mostrar tres tipos diferentes de alertas. Mira
 Las alertas de riesgo alto indican configuraciones o errores de registro importantes que deben ser revisados, ya que pueden comprometer el rendimiento de la promoción y, en consecuencia, el margen de la operación de la tienda.
 
 Ejemplo:
-![alert-alto-risco-ES](//images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/380a8e538396c9210c5b741a8cc3bc38/image.png)
+![alert-alto-risco-ES](https://images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/380a8e538396c9210c5b741a8cc3bc38/image.png)
 
 ### Riesgo medio
 Las alertas de riesgo medio muestran avisos de configuraciones que pueden causar efectos no deseados en la promoción.
 
 Ejemplo:
-![alert-medio-risco-ES](//images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/7b21608671db91c4e1bc0a00f9ccfa31/image.png)
+![alert-medio-risco-ES](https://images.ctfassets.net/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/7b21608671db91c4e1bc0a00f9ccfa31/image.png)
 
 ### Riesgo bajo 
 Las alertas de riesgo bajo presentan información relevante sobre la configuración de la promoción, lo que puede contribuir a mejorar el rendimiento.
 
 Ejemplo:
-![alert-baixo-risco-ES](//images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/b5c1d499a549c2c56f84a4b286ce1a84/image.png)
+![alert-baixo-risco-ES](https://images.ctfassets.net/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/b5c1d499a549c2c56f84a4b286ce1a84/image.png)
 
diff --git a/docs/tutorials/es/promotions-beta.md b/docs/tutorials/es/promotions-beta.md
index 48460ed9a..8e7812ce7 100644
--- a/docs/tutorials/es/promotions-beta.md
+++ b/docs/tutorials/es/promotions-beta.md
@@ -32,20 +32,20 @@ La página de inicio presenta la lista de promociones en una malla que permite v
 - Duplicar o archivar promociones a través del botón <i class="fas fa-ellipsis-v"></i>
 - Gestionar las condiciones de la promoción haciendo clic en cualquier lugar de la línea de la malla (consulte la sección [Nueva promoción](#nueva-promocion) para obtener detalles sobre las condiciones de la promoción).
 
-![promobeta1 acoes lista promocoes ES](//images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b8b32c9c2d6f39763ade1630fc34023f/promobeta1_acoes_lista_promocoes_ES.gif)
+![promobeta1 acoes lista promocoes ES](https://images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/b8b32c9c2d6f39763ade1630fc34023f/promobeta1_acoes_lista_promocoes_ES.gif)
 
 La lista de promociones se puede filtrar y ordenar según sus necesidades. Es posible filtrar por *Efecto*, *Estado*, *Fecha de inicio*, *Fecha de caducidad* o *Política comercial*.
 
-![promobeta2 filtros lista promocoes ES](//images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/28326256cde9d433ece9b634ceab8205/promobeta2_filtros_lista_promocoes_ES.gif)
+![promobeta2 filtros lista promocoes ES](https://images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/28326256cde9d433ece9b634ceab8205/promobeta2_filtros_lista_promocoes_ES.gif)
 
 El orden puede ser ascendente o descendente a partir de la información básica de la promoción, simplemente haciendo clic en el título.
 
-![promobeta3 ordenacao lista promocoes ES](//images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5660b538ad60cc95faa676c4aa724d76/promobeta3_ordenacao_lista_promocoes_ES.gif)
+![promobeta3 ordenacao lista promocoes ES](https://images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/5660b538ad60cc95faa676c4aa724d76/promobeta3_ordenacao_lista_promocoes_ES.gif)
 
 ## Nueva promoción
 Las variedades de condiciones para crear promociones se traducen en campos presentes en la pantalla de __Nueva Promoción__. La creación de una promoción que se ajuste a los estándares deseados se realiza de forma sencilla, rellenando los campos en una única pantalla a la que se accede a través del botón __NUEVA PROMOCIÓN__ de la página de inicio.
 
-![promobeta4 botao novapromocao ES](//images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/cf5363e79041f050f0b164735e8244cd/promobeta4_botao_novapromocao_ES.png)
+![promobeta4 botao novapromocao ES](https://images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/cf5363e79041f050f0b164735e8244cd/promobeta4_botao_novapromocao_ES.png)
 
 Tanto las condiciones de la nueva promoción como los campos de la pantalla están separados por grupos, que son:
 
diff --git a/docs/tutorials/es/promotions-simulator-beta.md b/docs/tutorials/es/promotions-simulator-beta.md
index eab4a279b..ee161192f 100644
--- a/docs/tutorials/es/promotions-simulator-beta.md
+++ b/docs/tutorials/es/promotions-simulator-beta.md
@@ -36,7 +36,7 @@ El **Simulador de promociones** está disponible para todas las tiendas VTEX med
 
    En la nueva ventana, verás una lista de los productos que están en tu carrito. Podrás ver todas las promociones aplicadas y aplicables a cada uno de los ítems.
 
-![Simulator-promo-es-gif-1](//images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/61187eee812b80ec80769704578aad35/simulador-promo-es-230706.gif)
+![Simulator-promo-es-gif-1](https://images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/61187eee812b80ec80769704578aad35/simulador-promo-es-230706.gif)
 
 La interfaz del **Simulador de promociones** presenta la siguiente información:
 
@@ -77,7 +77,7 @@ Para editar una promoción, sigue los pasos a continuación:
 
 El **Simulador de promociones** permite probar la aplicación de otra promoción o simular lo que sucedería al desactivar promociones aplicadas. Para utilizarlo, haz clic en el botón `Seleccionar promociones` en la parte superior derecha de la página según se muestra en la imagen a continuación.
 
-![ui-Simulator-promo-es-gif-2](//images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/488e9025886fa184fa38c06b55129139/ui-simulador-promo-es-230706.gif)
+![ui-Simulator-promo-es-gif-2](https://images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/488e9025886fa184fa38c06b55129139/ui-simulador-promo-es-230706.gif)
 
 Para ejecutar una simulación, sigue estos pasos:
 
diff --git a/docs/tutorials/es/promotions-simulator.md b/docs/tutorials/es/promotions-simulator.md
index 5d5a66131..fa37591d1 100644
--- a/docs/tutorials/es/promotions-simulator.md
+++ b/docs/tutorials/es/promotions-simulator.md
@@ -27,9 +27,9 @@ Para utilizar esta funcionalidad, primero debes [configurar Cartman](https://hel
 2. En el carrito, haz clic en el botón <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para abrir Cartman.
 3. Haz clic en la opción `Ver detalles de la promoción`.
 4. Esta ventana muestra las promociones aplicadas al carrito. Para más detalles, haz clic en <i class="fas fa-search"></i>`Ver detalles`.
-![cartman-analisador-promoção-ES](//images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/f4cd037dc329105e0dd0cc2a08bfb75c/Screen_Shot_2022-03-07_at_11.14.14.png)
+![cartman-analisador-promoção-ES](https://images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/f4cd037dc329105e0dd0cc2a08bfb75c/Screen_Shot_2022-03-07_at_11.14.14.png)
 5. Luego se mostrará la ventana **Simulador de Promociones**.
-![analisador-promoção-ES](//images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/37b6391ca94a73ffaed7618a5b15dcb6/image.png)
+![analisador-promoção-ES](https://images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/37b6391ca94a73ffaed7618a5b15dcb6/image.png)
 
 En esta ventana, puedes consultar la siguiente información:
 
diff --git a/docs/tutorials/es/protection-against-transaction-attacks.md b/docs/tutorials/es/protection-against-transaction-attacks.md
index b39797e22..c96a347c8 100644
--- a/docs/tutorials/es/protection-against-transaction-attacks.md
+++ b/docs/tutorials/es/protection-against-transaction-attacks.md
@@ -36,9 +36,9 @@ Para activar la protección, mira el paso a paso que se muestra a continuación.
 4. En la esquina superior derecha, haz clic en el ícono de configuración;
 5. En __Protección contra ataques__, haz clic en el botón para activarla (el color verde indica "activada").
 
-![proteção-botao-configurações](//images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
+![proteção-botao-configurações](https://images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
 
-![opción-de-protección-habilitada1](//images.ctfassets.net/alneenqid6w5/6svPWoUMebewsgVcBGkig5/c5aa662b0d3f17f6131e1bf702f0e49a/opci__n-de-protecci__n-habilitada1.png)
+![opción-de-protección-habilitada1](https://images.ctfassets.net/alneenqid6w5/6svPWoUMebewsgVcBGkig5/c5aa662b0d3f17f6131e1bf702f0e49a/opci__n-de-protecci__n-habilitada1.png)
 
 ### ¿Cómo desactivar la protección contra los ataques a las transacciones?
 
@@ -69,13 +69,13 @@ Para acceder a esta información, mira el paso a paso que se muestra a continuac
 6. Para seleccionar __Amenazas detectadas__ o __Amenazas neutralizadas__, haga clic en una de las flechas de la derecha. 
 7. Verifica los detalles de los eventos en la ventana emergente que aparece.
 
-![opción-protección-histórico1](//images.ctfassets.net/alneenqid6w5/49x3IUoxJ7uydixZWsrzAJ/250619d85b728b32e7d8db8faaa1cfbe/opci__n-protecci__n-hist__rico1.png)
+![opción-protección-histórico1](https://images.ctfassets.net/alneenqid6w5/49x3IUoxJ7uydixZWsrzAJ/250619d85b728b32e7d8db8faaa1cfbe/opci__n-protecci__n-hist__rico1.png)
 
-![pantalla-protección-histórico1](//images.ctfassets.net/alneenqid6w5/7pybJ37CWRAnquFaSHXtYE/1f2e631ac9836dd9ef0f239a262ba205/pantalla-protecci__n-hist__rico1.png)
+![pantalla-protección-histórico1](https://images.ctfassets.net/alneenqid6w5/7pybJ37CWRAnquFaSHXtYE/1f2e631ac9836dd9ef0f239a262ba205/pantalla-protecci__n-hist__rico1.png)
 
-![pantalla-amenaza-potencial1](//images.ctfassets.net/alneenqid6w5/78mfTPLB4MFJfpJ7EAkJtY/0a00d39504db054aa5961d856b86a342/pantalla-amenaza-potencial1.png)
+![pantalla-amenaza-potencial1](https://images.ctfassets.net/alneenqid6w5/78mfTPLB4MFJfpJ7EAkJtY/0a00d39504db054aa5961d856b86a342/pantalla-amenaza-potencial1.png)
 
-![pantalla-amenaza-neutralizada1](//images.ctfassets.net/alneenqid6w5/1TAQRzC5ef1bmdZ3CFEIMa/384388f887f08d882df4da136ba34dd8/pantalla-amenaza-neutralizada1.png)
+![pantalla-amenaza-neutralizada1](https://images.ctfassets.net/alneenqid6w5/1TAQRzC5ef1bmdZ3CFEIMa/384388f887f08d882df4da136ba34dd8/pantalla-amenaza-neutralizada1.png)
 
 ### Artículos relacionados
 - [¿Qué es una solución antifraude?](https://help.vtex.com/es/tutorial/o-que-e-antifraude)
diff --git a/docs/tutorials/es/received-skus-beta.md b/docs/tutorials/es/received-skus-beta.md
index b7ce9a9d8..92a1da972 100644
--- a/docs/tutorials/es/received-skus-beta.md
+++ b/docs/tutorials/es/received-skus-beta.md
@@ -33,7 +33,7 @@ La página SKUs recibidos se organiza en pestañas correspondientes a los distin
 
 Dentro de cada pestaña, además de visualizar la lista de SKU, es posible filtrar anuncios, revisar las especificaciones de cada uno y verificar el porcentaje de SKUs recibidos que se encuentran en ese status específico.  
 
-![skus-recibidos-pestanas-es](//images.ctfassets.net/alneenqid6w5/4jNrRvJsZgja1LuSz204P1/3757c1f533031f535b2c233eb55f3d08/skus-recibidos-pestanas-es.png)
+![skus-recibidos-pestanas-es](https://images.ctfassets.net/alneenqid6w5/4jNrRvJsZgja1LuSz204P1/3757c1f533031f535b2c233eb55f3d08/skus-recibidos-pestanas-es.png)
 
 ### Pendientes
 
@@ -50,7 +50,7 @@ Cada fila de la lista representa un producto con la siguiente información:
 
 Para consultar todas las especificaciones de un producto, haz clic en el nombre del producto deseado y se abrirá una nueva ventana con toda la información.  
 
-![skus-recibidos-analisis-es](//images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/d789b0d0ad6be43a7eb75ee0b6a0c637/skus-recibidos-analisis-es.png)
+![skus-recibidos-analisis-es](https://images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/d789b0d0ad6be43a7eb75ee0b6a0c637/skus-recibidos-analisis-es.png)
 
 ### Problemas
 
@@ -62,7 +62,7 @@ La acción de solicitar corrección no está disponible en la pestaña <b>Proble
 
 Para identificar el problema de un anuncio solo hay que hacer clic en el nombre del producto deseado. Se mostrará una nueva ventana con la información del producto, el mensaje de error y el revisor del anuncio.  
 
-![skus-recibidos-problemas-analisis-es](//images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/9209d4817cfdb057283cb12a6bdb99a6/skus-recibidos-problemas-analisis-es.png)
+![skus-recibidos-problemas-analisis-es](https://images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/9209d4817cfdb057283cb12a6bdb99a6/skus-recibidos-problemas-analisis-es.png)
 
 ### Aprobados
 
@@ -121,7 +121,7 @@ De manera predeterminada, los ítems más recientemente agregados se muestran pr
 
 En este caso, los ítems se ordenarán de forma ascendente o descendente al hacer clic en __Precio__ o __Stock.__
 
-![skus-recibidos-ord-es](//images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/a44da25a3176f26b0ab2e318ef171375/skus-recibidos-ord-es.png)
+![skus-recibidos-ord-es](https://images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/a44da25a3176f26b0ab2e318ef171375/skus-recibidos-ord-es.png)
 
 ## Catalogación de ítems  
 
@@ -151,7 +151,7 @@ Las acciones disponibles para la catalogación son:
 Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
 </div>
 
-![skus-recibidos-crear-nuevo-producto-es](//images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/4b686bea24c2df091c8739ecc398a645/skus-recibidos-crear-nuevo-producto-es.png)
+![skus-recibidos-crear-nuevo-producto-es](https://images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/4b686bea24c2df091c8739ecc398a645/skus-recibidos-crear-nuevo-producto-es.png)
 
 - __Asociar a un producto existente:__ crea una relación entre el producto del seller y un producto que ya existe en el catálogo del marketplace. Para llevar a cabo esta acción, sigue los pasos a continuación:  
 
@@ -170,7 +170,7 @@ Al crear una nueva asociación, las nuevas tallas se agrupan con las demás que
 Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
 </div>
 
-![skus-recibidos-vincular-al-producto-es](//images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/7bf8dee7e2b09fa4c36aefa485a461c8/skus-recibidos-vincular-al-producto-es.png)
+![skus-recibidos-vincular-al-producto-es](https://images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/7bf8dee7e2b09fa4c36aefa485a461c8/skus-recibidos-vincular-al-producto-es.png)
 
 - __Asociar a un SKU existente:__ crea una relación entre el SKU del seller y un SKU que ya existe en el catálogo del marketplace. Para llevar a cabo esta acción, sigue los pasos a continuación:  
 
@@ -189,7 +189,7 @@ No obstante, es posible que este marketplace reciba el mismo SKU de 128 GB del S
 Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
 </div>
 
-![skus-recibidos-vincular-al-sku-es](//images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/5d8fc3e9ba0d93b2c2f9186d73f4f69b/skus-recibidos-vincular-al-sku-es.png)
+![skus-recibidos-vincular-al-sku-es](https://images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/5d8fc3e9ba0d93b2c2f9186d73f4f69b/skus-recibidos-vincular-al-sku-es.png)
 
 - __Bloquear:__ esta acción bloquea los anuncios seleccionados, impidiendo su reprocesamiento automático. Para llevar a cabo esta acción, sigue los pasos a continuación:  
 
@@ -204,7 +204,7 @@ Cuando el marketplace bloquea un SKU, significa que la próxima vez que el selle
 Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>. Los anuncios bloqueados se mostrarán en la pestaña <b>Bloqueados</b>.
 </div>
 
-![skus-recibidos-rechazar-y-bloquear-es](//images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/bb22e0cfd4ff98513d5da66696b2e5d5/skus-recibidos-rechazar-y-bloquear-es.png)
+![skus-recibidos-rechazar-y-bloquear-es](https://images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/bb22e0cfd4ff98513d5da66696b2e5d5/skus-recibidos-rechazar-y-bloquear-es.png)
 
 - Rechazar para corrección: rechaza el anuncio y envía al seller una solicitud para corregir la información. Para llevar a cabo esta acción, sigue los pasos a continuación:  
 
@@ -217,6 +217,6 @@ Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas<
 Esta acción puede realizarse en la pestaña <b>Pendientes</b>. Los anuncios que necesitan corrección se mostrarán en la pestaña <b>Problemas</b>.
 </div>  
 
-![skus-recibidos-rechazar-para-correccion-es](//images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/bc526e9f64a729781f5ebebcd6a62ee0/skus-recibidos-rechazar-para-correccion-es.png)
+![skus-recibidos-rechazar-para-correccion-es](https://images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/bc526e9f64a729781f5ebebcd6a62ee0/skus-recibidos-rechazar-para-correccion-es.png)
 
 - __Aprobación automática:__ también puedes configurar la aprobación automática de SKU de un seller específico, independientemente de la puntuación asignada por Matcher. Esta acción solo puede realizarse a través de la API REST. Para saber más, consulta la documentación de [Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions).  
diff --git a/docs/tutorials/es/registered-ticket-flow.md b/docs/tutorials/es/registered-ticket-flow.md
index 87faebced..6fe9c56f1 100644
--- a/docs/tutorials/es/registered-ticket-flow.md
+++ b/docs/tutorials/es/registered-ticket-flow.md
@@ -23,7 +23,7 @@ A continuación, veremos cómo funciona el flujo básico de un pago con boleto r
  
 ## Emisión del Boleto
 
-![Frame 2](//images.contentful.com/alneenqid6w5/2CqwPgtFuIkgkkus2y8gg0/69c19ff0cf7116579b3e3b91342189b3/Frame_2.png)
+![Frame 2](https://images.contentful.com/alneenqid6w5/2CqwPgtFuIkgkkus2y8gg0/69c19ff0cf7116579b3e3b91342189b3/Frame_2.png)
 
 1. Su __e-commerce__ le informa al __Gateway__ que un pedido será pagado a través de boleto bancario.
 2. El gateway entra en contacto con el __Banco__ para realizar el registro del boleto.
@@ -35,7 +35,7 @@ En este momento, el boleto aún no ha sido pagado por el cliente.
 
 ## Pago del Boleto y Conciliación Bancaria
 
-![Frame 2.1](//images.contentful.com/alneenqid6w5/8xi6DVozxSiWi2sWegG4c/b23a178d5c8ddcc3b8c6196df22119af/Frame_2.1.png)
+![Frame 2.1](https://images.contentful.com/alneenqid6w5/8xi6DVozxSiWi2sWegG4c/b23a178d5c8ddcc3b8c6196df22119af/Frame_2.1.png)
 
 1. El __Cliente__ paga el boleto directamente al __Banco__.
 2. El banco envía al __Gateway__ los archivos de [conciliación bancaria](/es/tutorial/conciliaciones-bancarias) con la información sobre el estado de pago de los boletos.
diff --git a/docs/tutorials/es/registering-brands.md b/docs/tutorials/es/registering-brands.md
index a43c4563e..6fbce62c1 100644
--- a/docs/tutorials/es/registering-brands.md
+++ b/docs/tutorials/es/registering-brands.md
@@ -23,4 +23,4 @@ Para registrar una marca, siga los pasos abajo:
 4. Llene los [Campos de registro de marca](https://help.vtex.com/es/tutorial/campos-de-registro-de-marca--37Ky7lTbEkiWIAYA80EMyI).
 5. Haga clic en el botón `Guardar`.
 
-![ENcadastrarmarcas3.PNG?h=250](//images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
+![ENcadastrarmarcas3.PNG?h=250](https://images.ctfassets.net/alneenqid6w5/5TTFejR7WZ2F7i150fdgbM/6f923d6a96e4e36c6aae76dc39b036e3/ENcadastrarmarcas3.PNG_h_250)
diff --git a/docs/tutorials/es/registering-gateway-affiliations.md b/docs/tutorials/es/registering-gateway-affiliations.md
index ed3b62b7e..0c9991e65 100644
--- a/docs/tutorials/es/registering-gateway-affiliations.md
+++ b/docs/tutorials/es/registering-gateway-affiliations.md
@@ -22,7 +22,7 @@ En la página de gestión de proveedores puedes:
 - [Registrar un nuevo proveedor](#registrar-proveedor)
 - [Ver los provedores registrados](#ver-proveedores-registrados)
 - [Editar la configuración de proveedores](#editar-configuracion-de-un-proveedor)  
-![interface_provedor_ES_1](//images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/776404f95b88a2baef59270471016a6d/interface_provedor_ES_1.JPG)
+![interface_provedor_ES_1](https://images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/776404f95b88a2baef59270471016a6d/interface_provedor_ES_1.JPG)
 
 ## Registrar proveedor
 
@@ -47,7 +47,7 @@ Para configurar los medios de pago que el proveedor escogido procesará, accede
 
 Para definir condiciones especiales para los medios de pago, accede a [Configurar condiciones especiales de Pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456).
 
-![interface_provedor_ES_2](//images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/eb61a668aee146f72207b08ff3f93b3a/artigo_interface_provedor_ES_2.JPG)
+![interface_provedor_ES_2](https://images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/eb61a668aee146f72207b08ff3f93b3a/artigo_interface_provedor_ES_2.JPG)
 
 ## Ver proveedores registrados
 
@@ -57,7 +57,7 @@ La pantalla principal de gestión de proveedores, disponible en __Configuración
 
 Para buscar proveedores por nombre, accede a la página de gestión de proveedores e ingresa el nombre del proveedor deseado.
 
-![interface_provedor_ES_3](//images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/f8ab3035ab037e74c6b08e5f4054f686/interface_provedor_ES_3.JPG)
+![interface_provedor_ES_3](https://images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/f8ab3035ab037e74c6b08e5f4054f686/interface_provedor_ES_3.JPG)
 
 ### Filtrar proveedores
 
@@ -65,15 +65,15 @@ Para cambiar la lista de proveedores usando filtros, accede a la página de gest
 
 - __Nombre__: filtra la lista de proveedores de pago por el nombre al marcar la casilla o ingresándolo en la barra de búsqueda del menú.
 
-![interface_provedor_ES_4](//images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/966cf9c4d726bb4e3fe3f140b4205472/interface_provedor_ES_4.JPG)
+![interface_provedor_ES_4](https://images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/966cf9c4d726bb4e3fe3f140b4205472/interface_provedor_ES_4.JPG)
 
 - __Tipo__: filtra la lista de proveedores por tipo, ya sea antifraude o de pago, o ambos.
 
-![interface_provedor_ES_5](//images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/76411e11c78028aac232b9b8d8a79534/interface_provedor_ES_5.JPG)
+![interface_provedor_ES_5](https://images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/76411e11c78028aac232b9b8d8a79534/interface_provedor_ES_5.JPG)
 
 - __Entorno__: filtra la lista de proveedores por tipo de entorno de operación registrado (producción o prueba).
 
-![interface_provedor_ES_6](//images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/5aae0659cf9128a58fe3ce02d03a6023/interface_provedor_ES_6.JPG)
+![interface_provedor_ES_6](https://images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/5aae0659cf9128a58fe3ce02d03a6023/interface_provedor_ES_6.JPG)
 
 <div class = "alert alert-danger">
 Para remover los filtros aplicados y ver todos los proveedores registrados en la tienda, haz clic en el botón <code>Limpiar todo</code>.</div>
@@ -87,7 +87,7 @@ Para editar la configuración de un proveedor de pago o antifraude registrado en
 3. En la pantalla de configuración del proveedor, haz clic en `Editar`.
 4. Realiza los cambios necesarios y haz clic en `Guardar`.
 
-![interface_provedor_ES_7](//images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/4931462bfe35657876f4a5e6c63d5386/artigo_interface_provedor_ES_7.JPG)
+![interface_provedor_ES_7](https://images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/4931462bfe35657876f4a5e6c63d5386/artigo_interface_provedor_ES_7.JPG)
 
 <div class = "alert alert-danger">
 Antes de editar la configuración de un proveedor, como datos de autorización, modo de procesamiento o tipo de reembolso, asegúrate de verificar que la nueva información no afecte el rendimiento operativo de la tienda.</div>
diff --git a/docs/tutorials/es/registering-sku-price.md b/docs/tutorials/es/registering-sku-price.md
index a37944fc7..6cbe3c842 100644
--- a/docs/tutorials/es/registering-sku-price.md
+++ b/docs/tutorials/es/registering-sku-price.md
@@ -21,7 +21,7 @@ El proceso manual es el más indicado para cuando el operador de la tienda des
 
 ## Registro o alteración manual
 
-![](//images.contentful.com/alneenqid6w5/62eMKlDZ04As4ey46yiOeK/2d689eb25d9945a532d4447ba770649f/Tabela_de_Valores.gif)
+![](https://images.contentful.com/alneenqid6w5/62eMKlDZ04As4ey46yiOeK/2d689eb25d9945a532d4447ba770649f/Tabela_de_Valores.gif)
 
 ### Registrar un valor nuevo
 
@@ -58,7 +58,7 @@ _Si usted hace click en el valor “Nuevo Valor de Tabla” luego de filtrar un
 
 ## Registro o alteración vía importación de planilla de Excel
 
-![](//images.contentful.com/alneenqid6w5/5Pbm0WFO12QmEwW88OM2iU/453748487c805f0ef7bd20887e454670/Altera__o_de_pre_o_Importa__o.gif)
+![](https://images.contentful.com/alneenqid6w5/5Pbm0WFO12QmEwW88OM2iU/453748487c805f0ef7bd20887e454670/Altera__o_de_pre_o_Importa__o.gif)
 
 ### Para registrar nuevos precios
 
@@ -86,7 +86,7 @@ _Si usted hace click en el valor “Nuevo Valor de Tabla” luego de filtrar un
 
 ### Campos de la planilla del Excel para importación
 
-![](//images.contentful.com/alneenqid6w5/1wTiiJMsUcUGMoI6GGWsOw/b31f627d1a8d642532d475fd72e23ff6/Como_cadastrar_preco_SKU_2.jpg)
+![](https://images.contentful.com/alneenqid6w5/1wTiiJMsUcUGMoI6GGWsOw/b31f627d1a8d642532d475fd72e23ff6/Como_cadastrar_preco_SKU_2.jpg)
 
 - **StockKeepingUnitId: **Id del SKU que desea registrar o alterar el precio;
 - **Source: **valor de utm\_source;
diff --git a/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
index a485f382d..3a6f455ae 100644
--- a/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -19,7 +19,7 @@ Al crear una [promoción regular](https://help.vtex.com/es/tutorial/registro-pro
 
 Al seleccionar este tipo de descuento, deberás crear una fórmula para definir cuál será el cálculo del descuento que se aplicará. En este artículo, explicaremos cómo crear una fórmula que cumpla con los objetivos de tu promoción.
 
-![tipo-descuento-formula](//images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/cb74d4e22b46f159aee6f51a09fe4646/desc-es.PNG)
+![tipo-descuento-formula](https://images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/cb74d4e22b46f159aee6f51a09fe4646/desc-es.PNG)
 
 En general, la fórmula para calcular el descuento nominal de la promoción sigue la misma lógica que las [fórmulas de Microsoft Excel](https://support.microsoft.com/pt-br/office/f%C3%B3rmulas-e-fun%C3%A7%C3%B5es-294d9486-b332-48ed-b489-abe7d0f9eda9), es decir que puedes usar [variables](#variables) (`total`, ` freight` y `quantity`), hacer [operaciones](#operaciones) (suma, resta, multiplicación y división) y aplicar [funciones](#funciones) (`min` y `max`).
 
@@ -78,19 +78,19 @@ De esta manera, la promoción aplicará el valor de descuento más bajo en cada
 
 Un cliente agregó al carrito un ítem cuyo precio es $ 45. Al calcular el 20% del total del precio, el resultado es 9, ya que `total * 0.2 = 9.` Como 9 está por debajo del valor límite de descuento, el descuento que se aplicará será de $ 9.
 
-![scenario1-es](//images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/d85aee72b0ba9e25aa9174d1adfa8bd6/scenario1-es.png)
+![scenario1-es](https://images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/d85aee72b0ba9e25aa9174d1adfa8bd6/scenario1-es.png)
 
 #### Escenario 2
 
 Otro cliente agregó al carrito un ítem cuyo precio es de $ 2600. Al calcular el 20% de ese valor, el resultado es 520, ya que `total * 0.2 = 520.` Como este valor está por encima del límite ($ 10), el descuento aplicado será de $ 10.
 
-![scenario2-es](//images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/281dfb618c4116d64023a38182f775ae/scenario2-es.png)
+![scenario2-es](https://images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/281dfb618c4116d64023a38182f775ae/scenario2-es.png)
 
 #### Escenario 3
 
 Un tercer cliente agregó dos ítems al carrito: un ítem tiene un precio de $ 100, y el otro, $ 2600. La suma de estos valores da como resultado $ 2700, por lo tanto, `total = 2700`. Al calcular el 20% del valor total, obtenemos un resultado de 540, ya que `total * 0.2 =  540`. Como este valor está por encima del límite ($ 10), el descuento total aplicado será de $ 10.
 
-![scenario3-es](//images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/bc0bd5ef72252b31779b9b6df92fbdf4/scenario3-es.png)
+![scenario3-es](https://images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/bc0bd5ef72252b31779b9b6df92fbdf4/scenario3-es.png)
 
 El descuento total de $ 10 se distribuye proporcionalmente entre los ítems, teniendo en cuenta el precio y la cantidad de cada uno. Esta distribución la realiza la plataforma de manera automática, siguiendo la lógica que se explica a continuación:
 
diff --git a/docs/tutorials/es/regular-promotion-with-reward-value.md b/docs/tutorials/es/regular-promotion-with-reward-value.md
index 5a2eddb71..708359ccf 100644
--- a/docs/tutorials/es/regular-promotion-with-reward-value.md
+++ b/docs/tutorials/es/regular-promotion-with-reward-value.md
@@ -38,7 +38,7 @@ El **valor de fidelidad nominal** agrega un valor fijo como crédito a la cuenta
 
 En el ejemplo que se muestra a continuación, los clientes obtendrán un crédito de USD 10 en la tienda cuando el status del pedido cambie a **Facturado**.
 
-![vf-nominal-es](//images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/e281a28760551bfc2a2b2b270f61de9e/vf-nominal-es.png)
+![vf-nominal-es](https://images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/e281a28760551bfc2a2b2b270f61de9e/vf-nominal-es.png)
 
 ### Valor de fidelidad porcentual
 
@@ -49,7 +49,7 @@ El **valor de fidelidad porcentual** agrega un valor porcentual como crédito de
 
 En el ejemplo a continuación, los clientes obtendrán un crédito del 20 % del valor de la compra cuando el status del pedido cambie a **Pago aprobado**.
 
-![vf-percentual-es](//images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/68508961c6c3efc9495e79062c73a343/vf-percentual-es.png)
+![vf-percentual-es](https://images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/68508961c6c3efc9495e79062c73a343/vf-percentual-es.png)
 
 ## Configuración de las restricciones
 
@@ -91,11 +91,11 @@ En la sección **Ventas y marketing**, aparece el nombre de la promoción que se
 
 En la sección **Flujo del pedido**, puedes verificar el valor de fidelidad otorgado:
 
-![fluxo-oms-es](//images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/b9c7949cb68192d24c61ff0b855c751e/fluxo-oms-es.png)
+![fluxo-oms-es](https://images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/b9c7949cb68192d24c61ff0b855c751e/fluxo-oms-es.png)
 
 Si utilizas la nueva interfaz de [Detalles del pedido (Beta)](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido-beta--2Y75n54Cc9VizrlG1N6ZNl), accede a `Ver interacciones` para verificar el valor otorgado:
 
-![interacoes-neworders-es](//images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/c99a1b288b2d25931d695c19865731dd/interacoes-neworders-es.png)
+![interacoes-neworders-es](https://images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/c99a1b288b2d25931d695c19865731dd/interacoes-neworders-es.png)
 
 Ten en cuenta que la promoción aplicada en el pedido del ejemplo brinda un **valor de fidelidad porcentual** del **50 %**. Gracias a esto, el cliente obtuvo un crédito de `R$ 54,28` para las próximas compras en la tienda, lo cual equivale al **50 %** de `R$ 108,55`, que es el valor total del pedido.
 
@@ -103,13 +103,13 @@ Ten en cuenta que la promoción aplicada en el pedido del ejemplo brinda un **va
 
 Los clientes de tu tienda ven el valor de fidelidad disponible para usar en la etapa de **Pago** durante el _checkout_, tal como se muestra a continuación.
 
-![checkout-pt (1)](//images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
+![checkout-pt (1)](https://images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
 
 El valor otorgado se puede usar como parte de pago. Para hacerlo, el cliente debe hacer clic en `Utilizar crédito` e ingresar el valor que desea usar.
 
 El valor se descontará de la otra forma de pago seleccionada. En el ejemplo a continuación, la factura pasó a tener un valor de `R$ 113,50`, que corresponde a `R$ 167,80` menos el valor de fidelidad utilizado (`R$ 54,30`).
 
-![checkout-2-pt (1)](//images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
+![checkout-2-pt (1)](https://images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
 
 ## Más información
 
diff --git a/docs/tutorials/es/regular-promotion.md b/docs/tutorials/es/regular-promotion.md
index 34a4d90b5..bd8bc7d08 100644
--- a/docs/tutorials/es/regular-promotion.md
+++ b/docs/tutorials/es/regular-promotion.md
@@ -89,7 +89,7 @@ Para que la promoción sea válida para todas las políticas comerciales, deje l
 
 En esta sección, debe elegir si la promoción se aplicará a todos los productos registrados en su tienda o solo a productos específicos, como se ilustra a continuación.
 
-![promocoes-restricao-es](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/83e378ce4788febd839ee10395e02f9f/image.png)
+![promocoes-restricao-es](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/83e378ce4788febd839ee10395e02f9f/image.png)
 
 Si desea aplicar la promoción a todo su catálogo, seleccione la opción **Aplicar a todos los productos.**
 
@@ -99,7 +99,7 @@ Puede incluir o excluir **categorías, marcas, colecciones**, **productos** y **
 
 Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en la promoción todos los productos de la categoría **Vestido **cuya marca es **Farm**, con la excepción del producto **Vestido Rosas**.
 
-![exemplo-es](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/89c3e52e137f7856cb49628954217ff9/image.png)
+![exemplo-es](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/89c3e52e137f7856cb49628954217ff9/image.png)
 
 En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
 
diff --git a/docs/tutorials/es/releases-module-beta.md b/docs/tutorials/es/releases-module-beta.md
index 8959239ff..4e81def91 100644
--- a/docs/tutorials/es/releases-module-beta.md
+++ b/docs/tutorials/es/releases-module-beta.md
@@ -72,7 +72,7 @@ En esta etapa, no es obligatorio rellenar los campos <b>Día de publicación</b>
 
 8. Haz clic en `Crear`.
 
-![print_cms_beta_es](//images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/ed3b5cf5eb3020123112b9d7aee2d34a/print_cms_beta_es.png)
+![print_cms_beta_es](https://images.ctfassets.net/alneenqid6w5/3E9inm1oqSRWqfBly8puW6/ed3b5cf5eb3020123112b9d7aee2d34a/print_cms_beta_es.png)
 
 ### Crear lanzamiento a través del módulo Lanzamientos
 
@@ -92,7 +92,7 @@ En esta etapa, no es obligatorio rellenar los campos Día de publicación y Hora
 
 Todos los lanzamientos creados aparecen en una lista en el Admin VTEX en **Configuración de la tienda > Lanzamientos**. La página muestra dos pestañas, `PROGRAMADOS` y `NO PROGRAMADOS`, dependiendo de si el lanzamiento se creó con una fecha de publicación o no. 
 
-![print_releases_es](//images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/687594e054953398b1e1973375e00709/print_releases_es.png)
+![print_releases_es](https://images.ctfassets.net/alneenqid6w5/14ZhiyhghBKjaoHuab8bcH/687594e054953398b1e1973375e00709/print_releases_es.png)
 
 En la pestaña `PROGRAMADOS`, la descripción de cada columna es la siguiente:
 
diff --git a/docs/tutorials/es/releasing-the-store-for-production.md b/docs/tutorials/es/releasing-the-store-for-production.md
index 924579b11..c71fe1826 100644
--- a/docs/tutorials/es/releasing-the-store-for-production.md
+++ b/docs/tutorials/es/releasing-the-store-for-production.md
@@ -30,7 +30,7 @@ Luego, será necesario poner la tienda con un estado de producción en el Licens
 4. En la opción **Está en producción**, clic en el botón **No**, y quedará como **Si**;
 5. Clic en el botón **Guardar**.
 
-![cuentas.es](//images.ctfassets.net/alneenqid6w5/4UvPtCEjci7qcSWAnq9Zb2/28637e20f24ddaa9c34c717fc5fbecbe/cuentas.es.png)
+![cuentas.es](https://images.ctfassets.net/alneenqid6w5/4UvPtCEjci7qcSWAnq9Zb2/28637e20f24ddaa9c34c717fc5fbecbe/cuentas.es.png)
 
 Después de esa configuración, al acceder la UL final de la tienda, la misma ya va a ser direccionada para su e-commerce!
 
diff --git a/docs/tutorials/es/relevance-rules.md b/docs/tutorials/es/relevance-rules.md
index 8b550355c..c1cf456a6 100644
--- a/docs/tutorials/es/relevance-rules.md
+++ b/docs/tutorials/es/relevance-rules.md
@@ -24,7 +24,7 @@ Hay dos posibles escenarios de configuración de relevancia:
 - **Criterios de prioridad:** es la forma de forzar que uno o más criterios tengan mayor prioridad entre los demás. En esta situación no hay pesos, porque todos los productos que tienen esta característica se presentarán primero en el resultado de la búsqueda.
 - **Composición de criterios:** es la forma de distribuir los pesos de cada opción, que van de 0 a 10. Aquí no hay un orden entre los criterios, serán los pesos los que definan la relevancia.
 
-![criterios-es](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/0b54c302ffac20ed831392a3c7d5135d/criterios-es.png)
+![criterios-es](https://images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/0b54c302ffac20ed831392a3c7d5135d/criterios-es.png)
 
 La información aplicada para establecer la relevancia es:
 
@@ -110,5 +110,5 @@ Para cambiar la configuración de Reglas de relevancia, sigue los pasos a contin
 
    Si deseas cambiar la posición de un criterio de **Composición de criterios** a **Criterios de prioridad**, solo tienes que arrastrarlo por el ícono <i class="fas fa-grip-vertical"></i> a la parte superior según se muestra aquí. Ten en cuenta que cuando el criterio cambia a criterio de prioridad, no se le puede cambiar el peso.
 
-   ![criterios-prioritarios-es](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/1bdaef8e82e1e1801a439a45acb2e4e3/criterios-prioritarios-es.gif)
+   ![criterios-prioritarios-es](https://images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/1bdaef8e82e1e1801a439a45acb2e4e3/criterios-prioritarios-es.gif)
 5. Para terminar, haz clic en  `Guardar`.
diff --git a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
index b3dcaa9aa..8f12920e8 100644
--- a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -21,7 +21,7 @@ El mensaje "__Request headers must contain only ASCII characters__" puede mostra
 
 Este escenario se produce si la página o funcionalidad solicitada contiene una cookie con caracteres especiales (no ASCII).
 
-![ascii_1](//images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/2018e90b25b45797270e5daa28032eab/ascii_1.png)
+![ascii_1](https://images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/2018e90b25b45797270e5daa28032eab/ascii_1.png)
 
 Según las normas de la [IETF](https://www.ietf.org/) (Internet Engineering Task Force), institución responsable de documentar los estándares utilizados en internet, las cookies deben estar compuestas únicamente por caracteres ASCII estándar y deben evitar incluir caracteres especiales (no ASCII). Para más información sobre los caracteres aceptados en cookies y encabezados, accede a [IETF - Request for Comments 7230 - Section 3.2.6 - Field Value Components](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6). 
 
@@ -41,19 +41,19 @@ En la página en la que se muestra el mensaje "__Request headers must contain on
 
   <blockquote><ui>2. En la barra superior de la pantalla, accede a la pestaña <b>Network</b> y ordena los requests haciendo clic en <b>Status</b>. La información <b>400</b> en el estado indica que la solicitud no se procesó correctamente, lo que puede deberse a errores como cookies incorrectas.</ui>  
 
-![ascii 2ascii_2](//images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/b3e881fcbf68abf42df7b6f45d8cf103/ascii_2.png) 
+![ascii 2ascii_2](https://images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/b3e881fcbf68abf42df7b6f45d8cf103/ascii_2.png) 
 
 <blockquote><ui>3. Haz clic en un request y después en la pestaña <b>Preview</b> para identificar si el error encontrado se refiere al mensaje "<b>Request headers must contain only ASCII characters</b>".</ui>
 
-![ascii 3](//images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/06de7bb790b762dbd6b720e45a09e0ab/ascii_3.png)
+![ascii 3](https://images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/06de7bb790b762dbd6b720e45a09e0ab/ascii_3.png)
 
 <blockquote><ui>4. Haz clic en la pestaña <b>Headers</b> y copia los datos de la cookie.</ui>  
 
-![ascii 4](//images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/5b2bfeb184598aa2c32af65f14e4a058/ascii_4.png)
+![ascii 4](https://images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/5b2bfeb184598aa2c32af65f14e4a058/ascii_4.png)
 
 <blockquote><ui>5. Accede a un <a href="https://pages.cs.wisc.edu/~markm/ascii.html">validador online de caracteres ASCII</a> e ingresa la información de la cookie. Si se identifican uno o varios caracteres especiales, los tipos y posiciones se mostrarán en la parte inferior del validador de caracteres.</ui>     
 
-![ascii 5](//images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/86447a853ffa7bd68e097831acdbf1e5/ascii_5.png)
+![ascii 5](https://images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/86447a853ffa7bd68e097831acdbf1e5/ascii_5.png)
 
 <blockquote><ui>6. Repite los pasos 3 a 5 con todos los requests de error para identificar los que contienen cookies con caracteres especiales.</ui>      
 
diff --git a/docs/tutorials/es/requering-authentication-on-store-pages.md b/docs/tutorials/es/requering-authentication-on-store-pages.md
index 06ec3c14d..7bf16cdce 100644
--- a/docs/tutorials/es/requering-authentication-on-store-pages.md
+++ b/docs/tutorials/es/requering-authentication-on-store-pages.md
@@ -19,15 +19,15 @@ Es posible que, para ciertas páginas de la tienda, los usuarios tengan que aute
 
 Algunas páginas vienen con esta configuración de forma predeterminada. Por ejemplo, las páginas `/Account` y `/Account/Orders`.
 
-![authenticationRequired](//images.contentful.com/alneenqid6w5/60cIIkiKDSEs2ocmqescgM/3f5a0c46d61c1002c22bc7b5469db7eb/authenticationRequired.png)
+![authenticationRequired](https://images.contentful.com/alneenqid6w5/60cIIkiKDSEs2ocmqescgM/3f5a0c46d61c1002c22bc7b5469db7eb/authenticationRequired.png)
 
 Pero usted puede tanto quitar el requisito de autenticación para estas páginas como insertarlo en otras páginas.
 
 Para ello, siga los pasos abajo:
 1. Acceda al módulo __CMS__.
 2. Haga clic en la carpeta correspondiente a la página deseada.
-3. Haga clic en el botón __Edit __.![editFolder](//images.contentful.com/alneenqid6w5/2DSRmQFQxeAYcoiWCAaU62/bc08bd32b394545d8af716338d55a0be/editFolder.png)
-4. Marque o desmarque la flag __Authentication Required__.![authenticationRequiredFlag](//images.contentful.com/alneenqid6w5/3iK3iGguAUg84KuAsC4MYW/1dcdae221b886b4a4d1cdc4eb87af9a4/authenticationRequiredFlag.png)
+3. Haga clic en el botón __Edit __.![editFolder](https://images.contentful.com/alneenqid6w5/2DSRmQFQxeAYcoiWCAaU62/bc08bd32b394545d8af716338d55a0be/editFolder.png)
+4. Marque o desmarque la flag __Authentication Required__.![authenticationRequiredFlag](https://images.contentful.com/alneenqid6w5/3iK3iGguAUg84KuAsC4MYW/1dcdae221b886b4a4d1cdc4eb87af9a4/authenticationRequiredFlag.png)
 5. Haga clic en __Save Folder__.
 
 Tenga en cuenta que cada vez que la flag __Authentication Required__ está marcada en una carpeta, la dirección URL de esta página se montará con la ruta `_secure`. Ex: `http://{AccountName}.vtexcommercestable.com.br/_secure/account/`
diff --git a/docs/tutorials/es/requesting-the-ssl-certificate.md b/docs/tutorials/es/requesting-the-ssl-certificate.md
index 30f2990dd..0511d7b09 100644
--- a/docs/tutorials/es/requesting-the-ssl-certificate.md
+++ b/docs/tutorials/es/requesting-the-ssl-certificate.md
@@ -19,6 +19,6 @@ El certificado SSL protegerá la transferencia de datos importantes de sus clien
 
 _El video presentado en este tutorial todavía no ha sido traducido para español. Estamos trabajando para ofrecer más contenido en español. Gracias por la comprensión_
 
-<video class="wp-video-shortcode" id="video-2558-10" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4?_=10" />[//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4](//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4 "//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4")</video>
+<video class="wp-video-shortcode" id="video-2558-10" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4?_=10" />[//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4](https://assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4 "//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4")</video>
 
 [Vea en más detalles cómo contratar el certificado de seguridad (SSL).](/es/tutorial/como-contratar-el-certificado-de-seguridad/)
diff --git a/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
index a1bbd645e..ee3bf6fc0 100644
--- a/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
+++ b/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
@@ -30,7 +30,7 @@ Durante la configuración inicial de VTEX, si tu tienda utiliza [integraciones e
 
 Después de configurar la integración de productos, precios y stock, así como de desarrollar el middleware, el flujo de información se dará como se ilustra en el diagrama a continuación.
 
-![back-office-en](//images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/0a0be8f8112538def94277ec0e3f176a/integracoes-es-1.PNG)
+![back-office-en](https://images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/0a0be8f8112538def94277ec0e3f176a/integracoes-es-1.PNG)
 
 Durante las operaciones rutinarias, las responsabilidades se dividen de la siguiente manera:
 
@@ -197,6 +197,6 @@ Sigue los pasos que se indican a continuación para identificar al soporte con e
 2. Haz clic en el pedido deseado para acceder a la [página de detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido--2Y75n54Cc9VizrlG1N6ZNl).
 3. En la sección **Historial de pedidos**, haz clic en `Ver interacciones` (botón ilustrado a continuación), y comprueba si hay algún mensaje de error. 
 
-![ver-interacciones-es](//images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/6608d46e87166eda8f12b46e69986260/ver-interacciones-es.png)
+![ver-interacciones-es](https://images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/6608d46e87166eda8f12b46e69986260/ver-interacciones-es.png)
 
 Si el mensaje de error no es autoexplicativo, el retailer puede ponerse en contacto con el [equipo de soporte VTEX](https://help.vtex.com/es/faq/como-funciona-el-suporte-de-vtex--3kACEfni4m8Yxa1vnf2ebe) adjuntando capturas de pantalla de las interacciones y el ID del pedido, y el equipo de expertos lo ayudará a identificar el origen del problema.
diff --git a/docs/tutorials/es/responsive-vs-mobile-version.md b/docs/tutorials/es/responsive-vs-mobile-version.md
index d51fa8fba..8c42b7276 100644
--- a/docs/tutorials/es/responsive-vs-mobile-version.md
+++ b/docs/tutorials/es/responsive-vs-mobile-version.md
@@ -23,7 +23,7 @@ Sea del computador, smartphone, tablet o notebook, el design es el mismo. Lo que
 
 El design de la versión mobile y toda su programación se hace pensando solamente en el mobile, siendo una segunda aplicación, o sea, una para navegadores comunes y otra para navegadores mobile. Al acceder a la tienda, se identifica el dispositivo y se dirige a programación específica.
 
-![Principales pantallas mobile utilizadas](//images.contentful.com/alneenqid6w5/4tOHOVzZO8w6a0mUAuqSk6/770a9f0ff450163bd3e30f32e8e56cd6/RESOLUTION.jpg)
+![Principales pantallas mobile utilizadas](https://images.contentful.com/alneenqid6w5/4tOHOVzZO8w6a0mUAuqSk6/770a9f0ff450163bd3e30f32e8e56cd6/RESOLUTION.jpg)
 
 Principales pantallas mobile utilizadas (puede haber variaciones según el dispositivo utilizado):
 
@@ -55,7 +55,7 @@ Principales pantallas mobile utilizadas (puede haber variaciones según el dispo
 
 #### Principales elementos visuales reconocidos en los dispositivos móviles
 
-![menu_mobile_version es](//images.ctfassets.net/alneenqid6w5/4mispPtTBC2yCoAWQcMQkw/cd547422d5bba04fb7ed04e744229625/modelo_menu_ESPANHOL.png)
+![menu_mobile_version es](https://images.ctfassets.net/alneenqid6w5/4mispPtTBC2yCoAWQcMQkw/cd547422d5bba04fb7ed04e744229625/modelo_menu_ESPANHOL.png)
 
 #### ¡La calidad es indiferente al tamaño!
 
diff --git a/docs/tutorials/es/restrict-public-access-to-master-data-fields.md b/docs/tutorials/es/restrict-public-access-to-master-data-fields.md
index 8dffe1c36..98211a63d 100644
--- a/docs/tutorials/es/restrict-public-access-to-master-data-fields.md
+++ b/docs/tutorials/es/restrict-public-access-to-master-data-fields.md
@@ -27,24 +27,24 @@ Dependiendo de los datos almacenados, el acceso público sin autenticación pued
 2. En Master Data, haz clic en **Aplicaciones**.
 3. Haz clic en el engranaje <i class="fas fa-cog"></i> al lado de **Profile System**:
 
-   ![1-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/74b070908ad01d2f304ef85b3336d90a/1-master-data-confidential-data-es.png)
+   ![1-master-data-confidential-data-es](https://images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/74b070908ad01d2f304ef85b3336d90a/1-master-data-confidential-data-es.png)
 4. En **Configuración**, haz clic en **Estructura de datos**.
 
-   ![2-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/af70a12de57c62150baa2889bfcbbeb3/2-master-data-confidential-data-es.png)
+   ![2-master-data-confidential-data-es](https://images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/af70a12de57c62150baa2889bfcbbeb3/2-master-data-confidential-data-es.png)
 5. Haz clic en la pestaña **Entidades de datos**.
 6. En la fila de la entidad de datos, haz clic en el botón de edición <i class="fas fa-edit"></i>.
 
-   ![3-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/7807d93ab778a6f4634f7e1a5eb7a38d/3-master-data-confidential-data-es.png)
+   ![3-master-data-confidential-data-es](https://images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/7807d93ab778a6f4634f7e1a5eb7a38d/3-master-data-confidential-data-es.png)
 7. En la fila del campo que contiene datos personales (o que, cuando se utiliza junto con otros campos, constituye datos personales) haz clic en el engranaje <i class="fas fa-cog"></i>. 
 
-   ![4-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/a6f2536154ec9a8dba14d237a00da7db/4-master-data-confidential-data-es.png)
+   ![4-master-data-confidential-data-es](https://images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/a6f2536154ec9a8dba14d237a00da7db/4-master-data-confidential-data-es.png)
 8. Desmarca las siguientes opciones:
 
    * **Permitir la lectura sin credenciales**
    * **Permitir editar sin credenciales**
    * **Permitir filtrar sin credenciales**
 
-   ![5-master-data-confidential-data-es](//images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/d59c8ed7478226d25f870226b421068c/5-master-data-confidential-data-es.png)
+   ![5-master-data-confidential-data-es](https://images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/d59c8ed7478226d25f870226b421068c/5-master-data-confidential-data-es.png)
 9. Haz clic en `Guardar`.
 10. En la fila de la entidad de datos modificada, haz clic en el botón Publicar <i class="fas fa-save"></i> para que se publique la configuración guardada.
 11. Haz clic en `OK`.
diff --git a/docs/tutorials/es/roles.md b/docs/tutorials/es/roles.md
index f2afd70ac..97b351b51 100644
--- a/docs/tutorials/es/roles.md
+++ b/docs/tutorials/es/roles.md
@@ -24,7 +24,7 @@ En la página **Roles** puedes realizar las siguientes acciones:
 * [Editar rol](#editar-rol)
 * [Eliminar rol](#eliminar-rol)
 
-![roles-es](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/61435c94a6654fd066e3b0f5f8cd2fd0/roles-es.png)
+![roles-es](https://images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/61435c94a6654fd066e3b0f5f8cd2fd0/roles-es.png)
 
 La página muestra en formato de tabla una lista con todos los roles registrados en la cuenta y su respectiva información: 
 
diff --git a/docs/tutorials/es/rounding-rules.md b/docs/tutorials/es/rounding-rules.md
index aeeaabf63..a1f342e1a 100644
--- a/docs/tutorials/es/rounding-rules.md
+++ b/docs/tutorials/es/rounding-rules.md
@@ -60,16 +60,16 @@ Debajo se muestran ejemplos de los flujos de inclusión, edición y exclusión d
 
 *Flujo de creación de una regla*
 
-![config-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/7wgWLaW6Dkkbzv5TwcRmkB/e03d3e914bc8d0caa79b9f01cceabf6a/config-arrendodamento-ES.gif)
+![config-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/7wgWLaW6Dkkbzv5TwcRmkB/e03d3e914bc8d0caa79b9f01cceabf6a/config-arrendodamento-ES.gif)
 
 *Flujo de alteración de una regla*
 
-![editar-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/pISHBzFVs6U43naiHWtBl/2565b7cbb0c125bd06d7f794fb143e45/editar-arrendodamento-ES.gif)
+![editar-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/pISHBzFVs6U43naiHWtBl/2565b7cbb0c125bd06d7f794fb143e45/editar-arrendodamento-ES.gif)
 
 *Flujo de exclusión de una regla*
 
-![deletar-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/5r2727EBpFCZTdCWf37pX5/94da5c889815498eba18317d8917b696/deletar-arrendodamento-ES.gif)
+![deletar-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/5r2727EBpFCZTdCWf37pX5/94da5c889815498eba18317d8917b696/deletar-arrendodamento-ES.gif)
 
 *Simulación de precio para una regla*
 
-![teste-arrendodamento-ES](//images.ctfassets.net/alneenqid6w5/7reSTtuZZ5YNJOhynvGhFo/d8669c171fd5e5fd0d2e75eb49582fff/teste-arrendodamento-ES.gif)
+![teste-arrendodamento-ES](https://images.ctfassets.net/alneenqid6w5/7reSTtuZZ5YNJOhynvGhFo/d8669c171fd5e5fd0d2e75eb49582fff/teste-arrendodamento-ES.gif)
diff --git a/docs/tutorials/es/sales-app-sales-performance.md b/docs/tutorials/es/sales-app-sales-performance.md
index 61ffa0584..4e321b93b 100644
--- a/docs/tutorials/es/sales-app-sales-performance.md
+++ b/docs/tutorials/es/sales-app-sales-performance.md
@@ -23,7 +23,7 @@ Puedes acceder a las métricas de ventas de tu tienda que indican el desempeño
 2. Haz clic en el botón <i class="fas fa-bars"></i>.
 3. Después, en **Desempeño de ventas**.
 
-![Sales Performance (Store)](//images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/befba785d99d38ac7ae16e4a045ab32a/analytics_en.png)
+![Sales Performance (Store)](https://images.ctfassets.net/alneenqid6w5/2YMohTrMzA23P64djqnLWb/befba785d99d38ac7ae16e4a045ab32a/analytics_en.png)
 
 En esa página, tendrás acceso a las siguientes métricas:
 
@@ -37,7 +37,7 @@ En esa página, tendrás acceso a las siguientes métricas:
 
 Para acceder a las métricas específicas de un vendedor, sigue los pasos a continuación:
 
-![Ventas de Bruna - VTEX Sales App](//images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/0742350774cffb176c09e1597d24270d/Ventas_de_bruna_-.png)
+![Ventas de Bruna - VTEX Sales App](https://images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/0742350774cffb176c09e1597d24270d/Ventas_de_bruna_-.png)
 
 1. Haz clic en el ícono <i class="far fa-id-badge"></i>.
 2. Selecciona el perfil de un vendedor e introduce la contraseña.
diff --git a/docs/tutorials/es/sales-associate-code-field-at-checkout.md b/docs/tutorials/es/sales-associate-code-field-at-checkout.md
index 3363b31ff..12c96cdee 100644
--- a/docs/tutorials/es/sales-associate-code-field-at-checkout.md
+++ b/docs/tutorials/es/sales-associate-code-field-at-checkout.md
@@ -61,7 +61,7 @@ Después de crear la entidad *codigovendedor*, debes asociarla a una promoción.
 
 <blockquote><ui>3. En <b>¿Cuáles son las condiciones para que la promoción sea válida?</b>, haz clic en la opción <b>utm_campaign</b> e ingresa <i>codigovendedor</i> en el campo.</ui>
 
-![utm campaign codigovendedor](//images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/5fac14ad4842791589bab32d955f480f/UTM_Campaign_codigovendedor.PNG)
+![utm campaign codigovendedor](https://images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/5fac14ad4842791589bab32d955f480f/UTM_Campaign_codigovendedor.PNG)
 
 <blockquote><ui>4. En <b>Restricciones y limitaciones de uso</b>, agrega las demás restricciones disponibles, si así lo deseas. Selecciona la opción <b>Aplicar con otras promociones</b>.</ui>
 
@@ -93,4 +93,4 @@ También debes completar los siguientes pasos:
 
 Después de ejecutar todos los pasos descritos anteriormente, el campo **Código de vendedor** estará disponible en la pantalla del Checkout.
 
-![Código de vendedor](//images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/8f7156a46e01ad6715f446aad5e2bd7e/Checkout_UI_-_ES_2.png)
+![Código de vendedor](https://images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/8f7156a46e01ad6715f446aad5e2bd7e/Checkout_UI_-_ES_2.png)
diff --git a/docs/tutorials/es/sales-associates-instore-beta.md b/docs/tutorials/es/sales-associates-instore-beta.md
index b01ec5640..56bca92b5 100644
--- a/docs/tutorials/es/sales-associates-instore-beta.md
+++ b/docs/tutorials/es/sales-associates-instore-beta.md
@@ -31,7 +31,7 @@ Esta página te permite gestionar tus vendedores a través de las siguientes acc
 * [Editar](#editar-vendedor)
 * [Eliminar](#eliminar-vendedor)
 
-![vendedores-es](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
+![vendedores-es](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/7ca04713635ff6b9975ebbdddcd2ccc8/image.png)
 
 La página contiene la siguiente información:
 
@@ -54,7 +54,7 @@ Puedes crear un vendedor siguiendo los pasos a continuación:
 
 Después de registrado, el vendedor recibirá un email de confirmación y se le redirigirá a la opción de inicio de sesión del vendedor en la aplicación inStore.
 
-![email-vendedor-pt](//images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
 <div class ="alert alert-warning">
 <p>Los vendedores registrados en inStore no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.</p> 
diff --git a/docs/tutorials/es/sales-performance.md b/docs/tutorials/es/sales-performance.md
index 00d51d64f..ac4d1bee7 100644
--- a/docs/tutorials/es/sales-performance.md
+++ b/docs/tutorials/es/sales-performance.md
@@ -26,7 +26,7 @@ Para acceder a la pagina, en __Dashboards__, haz clic en __Desempeño de Ventas_
 
 Puedes personalizar la visualización de los datos del gráfico y de la lista filtrando por periodo, dimensiones y métricas. 
 
-![Sales Perf Dash ES](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
+![Sales Perf Dash ES](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/49985a1bc354e18e3dce208e12bfbdb5/Sales_Perf_Dash_ES.gif)
 
 ## Datos 
 Los datos de la página proceden del [sistema de Gestión de pedidos](https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa) de VTEX. El Desempeño de Ventas es una solución analítica, que utiliza heurística y fórmulas creadas a partir de nuestra experiencia, llevando a nuestros clientes de ecommerce al siguiente nivel para calcular sus métricas. La página no debe utilizarse como un sustituto de los datos del OMS, sino como una herramienta de análisis y de insights de negocio.
@@ -153,7 +153,7 @@ Además de aplicar filtros, también puedes realizar las acciones a continuació
 
 ## Vistas
 
-![Sales perf update ES](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
+![Sales perf update ES](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/e91f5f473a5d10b757c7a93a235ee9d9/Sales_perf_update_ES.gif)
 
 El *dashboard* Desempeño de Ventas se puede personalizar aplicando diferentes filtros y seleccionando las métricas que aparecerán en el gráfico y la lista. Para facilitar la exploración diaria de los datos, hemos creado vistas que registran los filtros y las métricas aplicadas en la página para tu visualización directa. Puedes guardar, editar y compartir las diferentes vistas del dashboard. La página viene con las siguientes vistas configuradas por defecto:
 
diff --git a/docs/tutorials/es/scheduling-features-for-special-events.md b/docs/tutorials/es/scheduling-features-for-special-events.md
index 5ea4582ed..e074f9f4d 100644
--- a/docs/tutorials/es/scheduling-features-for-special-events.md
+++ b/docs/tutorials/es/scheduling-features-for-special-events.md
@@ -70,7 +70,7 @@ Para programar un contenido, siga los pasos a continuación:
 3. Utilice el campo de la URL en la esquina superior para navegar a la página que muestra el bloque cuyo contenido será sobrescrito.
 4. Seleccione el bloque para el que desea crear un nuevo contenido. Puede seleccionarlo en lista de la derecha o en la interfaz:
 
-![seta-interface](//images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
+![seta-interface](https://images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
 
 5. Haga clic en `Configuración` en la esquina superior derecha.
 6. Haga clic en el botón `Nuevo contenido`.
diff --git a/docs/tutorials/es/scheduling-prices.md b/docs/tutorials/es/scheduling-prices.md
index f3938ab94..d29797337 100644
--- a/docs/tutorials/es/scheduling-prices.md
+++ b/docs/tutorials/es/scheduling-prices.md
@@ -58,7 +58,7 @@ También puede hacer la programación de precios importando una plantilla de pre
 
 1. En el Admin VTEX, accede a *Precios > Lista de precios* , o escribe *Lista de precios* en la barra de búsqueda en la parte superior de la página.
 2. Haz clic en el ícono 📥 para exportar la plantilla que se rellenará.
-![Agendar preço fixo - ES](//images.contentful.com/alneenqid6w5/71nENEY0RAQO9VKRdlQRiG/815eca5b71065052b89c8411af1a7329/image.png)
+![Agendar preço fixo - ES](https://images.contentful.com/alneenqid6w5/71nENEY0RAQO9VKRdlQRiG/815eca5b71065052b89c8411af1a7329/image.png)
 3. Seleccione solo la opción **Tabla de precios fijos**.
 4. Haga clic en `Exportar 1 tabla`.
 
@@ -72,7 +72,7 @@ La plantilla se enviará a su email y podrá descargarla allí. Después de desc
 - **Date From:** la fecha y la hora de inicio, en formato [RFC3339](https://www.ietf.org/rfc/rfc3339.txt), de la programación del precio fijo. 
 - **Date To:** la fecha y la hora de término, en formato [RFC3339](https://www.ietf.org/rfc/rfc3339.txt), de la programación del precio fijo. 
 
-![Agendar preço fixo planilha PT](//images.contentful.com/alneenqid6w5/7g3wkpsDPcdjYHT2xSqGhS/1895766def1ed02971f47f003d115491/Screenshot_2021-08-05_at_17-17-11_-EDU-4229-_Agendar_pre__o_fixo.png)
+![Agendar preço fixo planilha PT](https://images.contentful.com/alneenqid6w5/7g3wkpsDPcdjYHT2xSqGhS/1895766def1ed02971f47f003d115491/Screenshot_2021-08-05_at_17-17-11_-EDU-4229-_Agendar_pre__o_fixo.png)
 
 Una vez que haya terminado de rellenar la plantilla, debe importarla a la tienda. Siga los pasos a continuación.
 
diff --git a/docs/tutorials/es/search-configuration.md b/docs/tutorials/es/search-configuration.md
index dc414e742..300b54536 100644
--- a/docs/tutorials/es/search-configuration.md
+++ b/docs/tutorials/es/search-configuration.md
@@ -37,7 +37,7 @@ La configuración general presenta las siguientes opciones relativas a [las espe
 
 La configuración de facetas presenta ajustes relacionados con las [facetas](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/50Dh4mpv0Sax0XpbvsjAtP) mostradas a los clientes de tu tienda durante la búsqueda:
 
-![Configuracion del filtro](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
+![Configuracion del filtro](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/9da57a4e5ca6deae770e223ab7fae366/configuraciones_de_filtro_es.png)
 
 * **Orden de las facetas:** orden en el que se mostrarán las facetas en la tienda. Si no hay ninguna faceta seleccionada en la sección, el orden predeterminado es alfabético.
 
diff --git a/docs/tutorials/es/search-control-fulltextsearchbox.md b/docs/tutorials/es/search-control-fulltextsearchbox.md
index 016755592..ee133c684 100644
--- a/docs/tutorials/es/search-control-fulltextsearchbox.md
+++ b/docs/tutorials/es/search-control-fulltextsearchbox.md
@@ -21,7 +21,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 El control `<vtex.cmc:fullTextSearchBox />`es responsable de generar la caja de búsqueda. Además del campo de búsqueda, el control renderiza un combo para restringir una búsqueda en un departamento. Tenemos abajo un ejemplo del control sin ninguna aplicación de css:
 
-![Contról de búsqueda default](//images.contentful.com/alneenqid6w5/4tvtNt1u0Mw8sgmwyAaOuW/2375499b868cfe4c24b3425fa0f33a8c/controle-busca-cru.png)
+![Contról de búsqueda default](https://images.contentful.com/alneenqid6w5/4tvtNt1u0Mw8sgmwyAaOuW/2375499b868cfe4c24b3425fa0f33a8c/controle-busca-cru.png)
 
 La búsqueda es una funcionalidad que debe estar disponible en todas las páginas de una tienda, por eso se sugiere que el control sea insertado dentro de un [subtemplate](http://help.vtex.com/es/tutorial/subtemplates). Normalmente el controle de busca se usa dentro del subtemplate del header de la tienda.
 
@@ -75,9 +75,9 @@ La funcionalidad de autocomplete ya está prevista en este control y sólo se de
 
 Ejemplos de cómo se puede personalizar el control:
 
-![](//images.contentful.com/alneenqid6w5/BMzmz8NA0o4SQqUO8ow4Y/5c6d179a8fca8a3efaf981c05203c061/controle-busca-autocomplete-560x318.png)
+![](https://images.contentful.com/alneenqid6w5/BMzmz8NA0o4SQqUO8ow4Y/5c6d179a8fca8a3efaf981c05203c061/controle-busca-autocomplete-560x318.png)
 
-![](//images.contentful.com/alneenqid6w5/5TiDgTywScWuAcC24wmeIu/58acad8f8151f8803251679453627968/controle-busca-exemplo-560x43.png)
+![](https://images.contentful.com/alneenqid6w5/5TiDgTywScWuAcC24wmeIu/58acad8f8151f8803251679453627968/controle-busca-exemplo-560x43.png)
 
-![](//images.contentful.com/alneenqid6w5/2X2lkCGHdSIaok08yYKCYO/6bef8f3e0c0b11313479226c0174e093/controle-busca-exemplo1.png)
+![](https://images.contentful.com/alneenqid6w5/2X2lkCGHdSIaok08yYKCYO/6bef8f3e0c0b11313479226c0174e093/controle-busca-exemplo1.png)
 
diff --git a/docs/tutorials/es/search-navigator-control.md b/docs/tutorials/es/search-navigator-control.md
index 29ad86568..497e475e7 100644
--- a/docs/tutorials/es/search-navigator-control.md
+++ b/docs/tutorials/es/search-navigator-control.md
@@ -44,7 +44,7 @@ Para que una colección se muestre en el menú por el control Search Navigator,
 
 Este flag se encuentra en la configuración de la propia colección dentro del CMS.
 
-![searchNavigator2](//images.contentful.com/alneenqid6w5/30xKS65fWMuoiQO4ac2EKM/921be3bc19a8cdff48dade515c354908/searchNavigator2.jpg)
+![searchNavigator2](https://images.contentful.com/alneenqid6w5/30xKS65fWMuoiQO4ac2EKM/921be3bc19a8cdff48dade515c354908/searchNavigator2.jpg)
 
 ## Categorías
 
@@ -52,7 +52,7 @@ Para que una categoría sea exhibida por acción de ese control, debe estar con
 
 Este flag está en la pantalla de registro de la categoría.
 
-![Cómo funciona el control Search Navigator ES 2](//images.ctfassets.net/alneenqid6w5/5Qg0LcxqSc6e2UuEo2M0me/457a81b3196c932f1d3f157582598599/2018-10-23_22-41-18_ES_2.png)
+![Cómo funciona el control Search Navigator ES 2](https://images.ctfassets.net/alneenqid6w5/5Qg0LcxqSc6e2UuEo2M0me/457a81b3196c932f1d3f157582598599/2018-10-23_22-41-18_ES_2.png)
 
 <div class="alert alert-info">
   <strong>Importante</strong>: El control  <code>&lt;vtex.cmc:searchNavigator/&gt;</code> exhibe, por estándar, apenas la categoría base (primer nivel) y la subcategoría más específica (último nivel) dentro del contexto actual. Se omiten las divisiones intermedias en el árbol de categorías. Además, el control solo funciona en los primeros tres niveles, que son tradicionalmente Departamento, Categoría y Subcategoría. Si su  <a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">arquitectura de catálogo</a> contiene subdivisiones más allá del tercer nivel, no se mostrarán con el control nativo.
@@ -85,7 +85,7 @@ Para que un campo de producto o un campo de SKU se muestre en el menú por el co
 
 Ambos se encuentran en la pantalla de registro del campo.
 
-![Cómo funciona el control Search Navigator ES 3](//images.ctfassets.net/alneenqid6w5/25TT9lYqHamqoaS6iIeQKk/a5bf18a4d4779df84dc68a40742fd55e/2018-10-23_2243_ES_3.png)
+![Cómo funciona el control Search Navigator ES 3](https://images.ctfassets.net/alneenqid6w5/25TT9lYqHamqoaS6iIeQKk/a5bf18a4d4779df84dc68a40742fd55e/2018-10-23_2243_ES_3.png)
 
 ## Rangos de precio
 
diff --git a/docs/tutorials/es/search-parameters.md b/docs/tutorials/es/search-parameters.md
index 50ac0a5cb..38450bad3 100644
--- a/docs/tutorials/es/search-parameters.md
+++ b/docs/tutorials/es/search-parameters.md
@@ -21,7 +21,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Al realizar búsquedas en la VTEX, existen algunas posibilidades de urls. Tenemos las urls de Departamentos y Categorías, que son formadas de la siguiente forma:
 
-![](//images.contentful.com/alneenqid6w5/1MhPmB1yxKS426UCsASUsY/eeaf45262ccde7b0a50ee6ef6b787afb/arvore_categoria.png)
+![](https://images.contentful.com/alneenqid6w5/1MhPmB1yxKS426UCsASUsY/eeaf45262ccde7b0a50ee6ef6b787afb/arvore_categoria.png)
 
 En el árbol de categorías arriba, los links quedarían así:
 
@@ -35,7 +35,7 @@ www.tienda.com/artes-e-entretenimento/festas-e-comemoracoes/artigos-para-festas
 
 Al usar el campo de búsqueda, la url siempre será formada por el término buscado:
 
-![](//images.contentful.com/alneenqid6w5/tJYda31CZUUOCii0EcwmE/89481a9321a61fb50fd5463217d6760d/campo_busca.png)
+![](https://images.contentful.com/alneenqid6w5/tJYda31CZUUOCii0EcwmE/89481a9321a61fb50fd5463217d6760d/campo_busca.png)
 
 www.loja.com.br/cama
 
@@ -49,13 +49,13 @@ Donde:
 
 **C:\[IdDepartamento/IdCategoria/IdSubcategoria\]**: Retorna productos de una determinada categoría, de acuerdo con los IDs informados para departamento, categoría y subcategoría. Este código es presentado al lado de los nombres de las categorías en **Cadastro de Produtos &gt; Categoria**:
 
-![](//images.contentful.com/alneenqid6w5/44i8Rue6hiMmMs64wiks86/8f31981e162596d825190865cefd121e/id_categoria1.png)
+![](https://images.contentful.com/alneenqid6w5/44i8Rue6hiMmMs64wiks86/8f31981e162596d825190865cefd121e/id_categoria1.png)
 
 **OBS: El ID de la categoría también puede ser encontrado en su página de edición, al final de la url.**
 
 **B:\[IdMarca\]: **Retorna productos de una determinada marca, de acuerdo al ID informado. Este código se presenta al final de la URL, en la página de modificación de una marca, en **Cadastro de Produtos &gt; Marca**:
 
-![](//images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
+![](https://images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
 
 <div class = "alert alert-warning">
   <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
@@ -63,11 +63,11 @@ Donde:
 
 **H:\[IdColeção\]**: Retorna productos de una determinada colección, de acuerdo al ID informado. Este código se informa en la edición de la colección, en **Configurações &gt; Portal &gt; Pasta Portal &gt; Subpasta Coleções:**
 
-![](//images.contentful.com/alneenqid6w5/2vqAbADq0cUQO224YoOQAQ/7eef524621cbf80d9c37b37c9cc4099e/id_colecao.png)
+![](https://images.contentful.com/alneenqid6w5/2vqAbADq0cUQO224YoOQAQ/7eef524621cbf80d9c37b37c9cc4099e/id_colecao.png)
 
 **spec\_fct\_\[IdCampoProduto/Sku\]:\[ValorBuscado\]:** Retorna productos cuyo valor de campo producto/sku con el ID indicado sea igual al valor informado. Este código puede obtenerse en la página de modificación de un campo producto/sku, al final de la url:
 
-![](//images.contentful.com/alneenqid6w5/7noRXDnenuSU4ugc8mmoSg/7a85e4ab97b87c00d4306c57c2462ecc/id_campo-560x386.png)
+![](https://images.contentful.com/alneenqid6w5/7noRXDnenuSU4ugc8mmoSg/7a85e4ab97b87c00d4306c57c2462ecc/id_campo-560x386.png)
 
 Un ejemplo de utilización de este campo sería:
 
diff --git a/docs/tutorials/es/searching-for-old-orders.md b/docs/tutorials/es/searching-for-old-orders.md
index 8aa2cf5fb..a289c1566 100644
--- a/docs/tutorials/es/searching-for-old-orders.md
+++ b/docs/tutorials/es/searching-for-old-orders.md
@@ -18,7 +18,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 Para buscar sus pedidos antiguos, siga los pasos a continuación:
 1. En el menú lateral del admin, haga clic en __Gestión de pedidos__.
 2. Haga clic en __Todos los pedidos__.
-3. Haga clic en el botón de filtro ![filter](//images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png).
+3. Haga clic en el botón de filtro ![filter](https://images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png).
 4. Escoja un filtro *por periodos*: __Fecha de factura__, __Fecha de pedido__, __Fecha de autorización__ o **Fecha de entrega**.
 5. En el filtro escogido, haga clic en el __ícono de calendario__, al lado del texto __Todas las fechas__.
 6. Escoja una fecha/hora inicial y una fecha/hora final. 
diff --git a/docs/tutorials/es/searching-for-transactions-on-payments.md b/docs/tutorials/es/searching-for-transactions-on-payments.md
index 10bb2b81a..687ed0e6a 100644
--- a/docs/tutorials/es/searching-for-transactions-on-payments.md
+++ b/docs/tutorials/es/searching-for-transactions-on-payments.md
@@ -35,13 +35,13 @@ Para volver a la lista original de las transacciones, basta apagar el valor ante
 
 Al hacer clic en una solicitud en el Gestión de Pedidos, usted va a la página que trae un resumen sobre él. Las principales informaciones están ahí, pero usted puede ver aún más detalles si hace clic en el enlace _Ver detalles de la transacción_:
 
-![Link transação OMS (ES)](//images.ctfassets.net/alneenqid6w5/4lCG7cxc8MacMYQgmecqG6/33669bc2490b6732d50b1e9769129c33/Link_transa____o_OMS__ES_.png)
+![Link transação OMS (ES)](https://images.ctfassets.net/alneenqid6w5/4lCG7cxc8MacMYQgmecqG6/33669bc2490b6732d50b1e9769129c33/Link_transa____o_OMS__ES_.png)
 
 ## TID del Pago e ID del Pago
 
 La búsqueda utilizando esos códigos necesariamente necesita contener todos los dígitos, o su búsqueda regresará vacía. Vea abajo como encontrarlo:
 
-![Códigos ES](//images.ctfassets.net/alneenqid6w5/X1c6jZ4yomYGoE8U4o86u/d68575f5fa61a6b38517920f247cc460/C__digos_ES.png)
+![Códigos ES](https://images.ctfassets.net/alneenqid6w5/X1c6jZ4yomYGoE8U4o86u/d68575f5fa61a6b38517920f247cc460/C__digos_ES.png)
 
 Estos valores, dentro del detalle de la transacción representarán la comunicación junto al respectivo conector. En los Eventos de la transacción será posible validar cada contacto hecho utilizando estos como identificador.
 
diff --git a/docs/tutorials/es/security-monitor.md b/docs/tutorials/es/security-monitor.md
index 298e85b54..9456cef89 100644
--- a/docs/tutorials/es/security-monitor.md
+++ b/docs/tutorials/es/security-monitor.md
@@ -26,7 +26,7 @@ Para acceder al dashboard sigue los pasos a continuación:
 1. En el Admin VTEX, accede a **Dashboards**, o ingresa **Dashboards** en la barra de búsqueda.
 2. En **Security Monitor**, haz clic en **Security Monitor Dashboard**.
 
-![1-security-monitor-es](//images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/fb2b0e5a7758c15f7a85a28d6092e119/1-security-monitor-es__2_.png)
+![1-security-monitor-es](https://images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/fb2b0e5a7758c15f7a85a28d6092e119/1-security-monitor-es__2_.png)
 
 Security Monitor presenta los resultados en tres pestañas, divididas por status:
 
@@ -48,7 +48,7 @@ La pestaña **Abiertos** muestra las amenazas identificadas por Security Monitor
 
 La barra superior muestra el número total de hallazgos y el número de amenazas por nivel de gravedad (alto, medio o bajo).
 
-![2-findings-es](//images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/630a7a558c2c57d07e6b8b68de359a4b/2-findings-es.png)
+![2-findings-es](https://images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/630a7a558c2c57d07e6b8b68de359a4b/2-findings-es.png)
 
 La pestaña muestra la lista completa de hallazgos abiertos en una tabla, del más reciente al más antiguo: 
 
@@ -79,7 +79,7 @@ Para mover un hallazgo a la pestaña **Pospuestos**, es decir, removerlo de la p
 3. Elige el periodo de tiempo, en días, durante el cual deseas mantener este hallazgo en la pestaña **Pospuestos**. Las opciones disponibles son: **7**, **90** o **120** días.
 4. Haz clic en `Posponer`.
 
-![3-snooze-finding-es](//images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/38af2109f1f98bfcb771fbb654b4113b/3-snooze-finding-es.png)
+![3-snooze-finding-es](https://images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/38af2109f1f98bfcb771fbb654b4113b/3-snooze-finding-es.png)
 
 ## Pospuestos
 
@@ -108,7 +108,7 @@ En la barra de búsqueda, ingresa la dirección de email del usuario o el nombre
 
 Al hacer clic en `Tipo` <i class="fas fa-chevron-down"></i>, puedes elegir uno de los tipos de hallazgo para filtrar los resultados mostrados en la lista. Haz clic en `Aplicar` para confirmar el filtro elegido y la lista se actualizará.
 
-![4-filter-findings-es](//images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/9718adf02a9fe3d71842848d87dca37c/4-filter-findings-es.png)
+![4-filter-findings-es](https://images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/9718adf02a9fe3d71842848d87dca37c/4-filter-findings-es.png)
 
 ## Editar configuración de las notificaciones
 
@@ -120,7 +120,7 @@ Para editar aquellos usuarios administrativos que recibirán notificaciones en c
    Para remover un usuario, haz clic en la `X` junto al email relacionado.
 3. Haz clic en `Guardar`.
 
-![5-edit-notifications-es](//images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/b68c5dab3fabde1021d0c41db8ba2673/5-edit-notifications-es__1_.png)
+![5-edit-notifications-es](https://images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/b68c5dab3fabde1021d0c41db8ba2673/5-edit-notifications-es__1_.png)
 
 ## Más información
 
diff --git a/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md b/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md
index e4eb1b7d5..2a8ab9915 100644
--- a/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md
+++ b/docs/tutorials/es/selecting-stock-for-orders-mercado-envios-full.md
@@ -31,4 +31,4 @@ Cuando el stock esté registrado, realice los siguientes pasos:
 6. Ingrese el ID del stock seleccionado en el campo **Almacén Mercado Full**.
 7. Para finalizar, haga clic en **Guardar Configuración**.
 
-![Início (3)](//images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
+![Início (3)](https://images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
diff --git a/docs/tutorials/es/seller-management.md b/docs/tutorials/es/seller-management.md
index 168d32164..e12b6914e 100644
--- a/docs/tutorials/es/seller-management.md
+++ b/docs/tutorials/es/seller-management.md
@@ -17,7 +17,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 **Gestión de sellers** es la página donde los operadores del marketplace [agregan sellers](https://help.vtex.com/es/tutorial/adicionar-seller--tutorials_392), registran su información y gestionan sus status. La página incluye métricas para que los marketplaces evalúen su operación. También pueden aplicar filtros a los resultados de la lista de sellers y agruparlos a través de la opción Grupos, tags que le permiten filtrar los resultados más fácilmente.  
 
-![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 ## Métricas
 La página muestra las métricas generales de los sellers:
@@ -46,7 +46,7 @@ Esta funcionalidad permite a los marketplaces optimizar los escenarios de seguim
 
 Los grupos se crean manualmente en __Agregar seller__ o al hacer clic en __Gestionar grupos.__ También se puede editar o eliminar los grupos después de crearlos.  
 
-![Gestión de seller](//images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/c74c7c6069bb8e6e4908a10c4e208827/gestionador_de_seller_es.png)  
+![Gestión de seller](https://images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/c74c7c6069bb8e6e4908a10c4e208827/gestionador_de_seller_es.png)  
 
 ## Gestionar grupos  
 
diff --git a/docs/tutorials/es/seller-portal-creating-a-promotion.md b/docs/tutorials/es/seller-portal-creating-a-promotion.md
index 2b37bd7a4..fcdd5b23f 100644
--- a/docs/tutorials/es/seller-portal-creating-a-promotion.md
+++ b/docs/tutorials/es/seller-portal-creating-a-promotion.md
@@ -22,7 +22,7 @@ Para crear una nueva promoción como seller en el Seller Portal, sigue los pasos
 3. Rellena los datos solicitados en los [Campos de registro de la promoción](#campos-de-registro-de-la-promocion).
 4. Haz clic en `Guardar`
 5. Revisa la configuración de tu promoción antes de publicarla.
-![seller-portal-promo-revisao-es](//images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/29c086e5c167c63b97438bec6410a865/image.png)
+![seller-portal-promo-revisao-es](https://images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/29c086e5c167c63b97438bec6410a865/image.png)
 6. Haz clic en `Confirmar`.
 
 Después, se activará la promoción y se aplicará a tu tienda.
@@ -37,7 +37,7 @@ Las promociones que puedan aplicarse a los mismos ítems del carrito se comparan
 
 En esta sección, debes configurar la información general de la promoción.
 
-![seller-portal-promo-geral-es](//images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/23a283361433a809c30668b5143f6fc6/image.png)
+![seller-portal-promo-geral-es](https://images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/23a283361433a809c30668b5143f6fc6/image.png)
 
 * **Nombre:** nombre de la promoción.
 * **Status:** botón de alternancia que define si la promoción está activa <i class="fas-toggle-on"></i> o inactiva <i class="fas-toggle-off"></i>.
@@ -51,7 +51,7 @@ En esta sección, debes configurar la información general de la promoción.
 
 Sección que define el tipo y valor del descuento que se aplicará en la promoción. Consulta las opciones de descuento a continuación:
 
-![seller-portal-promo-tipo-desconto-es](//images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/f74488e8864f4b7a0134835dc4fe114e/image.png)
+![seller-portal-promo-tipo-desconto-es](https://images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/f74488e8864f4b7a0134835dc4fe114e/image.png)
 
 #### Precio
 
@@ -68,7 +68,7 @@ Sección que define el tipo y valor del descuento que se aplicará en la promoci
 
 En esta sección, debes seleccionar si la promoción se aplicará a todos los productos registrados en tu tienda o solo a productos específicos, como se ilustra a continuación.
 
-![seller-portal-promo-produtos-elegiveis-es](//images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/c281d0d00239a39cb1411e8fc88d73af/image.png)
+![seller-portal-promo-produtos-elegiveis-es](https://images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/c281d0d00239a39cb1411e8fc88d73af/image.png)
 
 * **Todos los productos:** aplica la promoción a todo tu catálogo.
 * **Productos que cumplan las siguientes reglas:** limita la aplicación de la promoción a productos específicos respecto a las siguientes reglas de selección:
@@ -86,7 +86,7 @@ Para eliminar una regla, haz clic en <i class="fas-trash-can"></i> `Remover regl
 
 El pedido del cliente debe cumplir todas las condiciones registradas en esta sección para que la promoción pueda aplicarse.
 
-![seller-portal-promo-condicoes-es](//images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/72e08a40feda1f058cf41f733062adc8/image.png)
+![seller-portal-promo-condicoes-es](https://images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/72e08a40feda1f058cf41f733062adc8/image.png)
 
 * **Precio del ítem:** el descuento solo se concederá a los ítems dentro del rango de precios establecido. 
 * **Tipo de envío:** el descuento se concederá si el tipo de envío elegido por el cliente es el mismo que el registrado en la promoción. 
@@ -97,6 +97,6 @@ El pedido del cliente debe cumplir todas las condiciones registradas en esta sec
 
 La acción de la promoción estará limitada por el siguiente criterio:
 
-![seller-portal-promo-restricoes-es](//images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/b3c27968580ad91841f76bcffa707eee/image.png)
+![seller-portal-promo-restricoes-es](https://images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/b3c27968580ad91841f76bcffa707eee/image.png)
 
 * **Limitar el número de ítems elegibles por carrito: **define el número máximo de ítems del carrito a los que puede aplicarse la promoción. Si el carrito contiene más ítems que los estipulados en el límite, el descuento solo se aplicará a la cantidad configurada en este campo.
diff --git a/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
index 212d8ab4c..d84e11b26 100644
--- a/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
@@ -27,7 +27,7 @@ A través del *Seller Portal*, los *marketplaces* pueden:
 - Reducir el tiempo de conversión de las ventas con una incorporación self-service de nuevos sellers ahora más rápida y sin fricciones.  
 - Compartir el surtido de productos con el seller de forma sencilla y gestionar rápidamente los anuncios de productos compartidos.  
 
-![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/442d951b3a76c47f43249b3f544389be/Seller_Portal.gif)
 
 ## Interacción entre el seller y el marketplace en el Seller Portal
 
diff --git a/docs/tutorials/es/seller-portal-product-details.md b/docs/tutorials/es/seller-portal-product-details.md
index f511f673b..6c3986794 100644
--- a/docs/tutorials/es/seller-portal-product-details.md
+++ b/docs/tutorials/es/seller-portal-product-details.md
@@ -15,7 +15,7 @@ legacySlug: seller-portal-detalles-del-producto
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
-![Shared products product details ES](//images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/03a548e0bc52ff9953b51621583da3c9/Shared_products_product_details_ES.jpg)
+![Shared products product details ES](https://images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/03a548e0bc52ff9953b51621583da3c9/Shared_products_product_details_ES.jpg)
 
 En la página «Detalles del producto» en la funcionalidad [Produtos Compartidos](https://help.vtex.com/es/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) se puede ver toda la información sobre un producto específico. A partir de ella el seller puede: 
 
diff --git a/docs/tutorials/es/seller-portal-promotions.md b/docs/tutorials/es/seller-portal-promotions.md
index 64d3be4d9..ea9cc693b 100644
--- a/docs/tutorials/es/seller-portal-promotions.md
+++ b/docs/tutorials/es/seller-portal-promotions.md
@@ -27,7 +27,7 @@ A partir de la lista de promociones del Seller Portal puedes llevar a cabo diver
 * [Acceder al menú de acciones de la promoción](#acceder-al-menu-de-acciones-de-la-promocion)
 * [Acceder a promociones archivadas](#acceder-a-promociones-archivadas)
 
-![seller-portal-promo-es](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/a65cab7ea0ee0983f80894668ca050d0/image.png)
+![seller-portal-promo-es](https://images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/a65cab7ea0ee0983f80894668ca050d0/image.png)
 
 En la siguiente tabla puedes consultar la información de la página **Promociones**: 
 
@@ -71,7 +71,7 @@ El archivo contiene la siguiente información sobre cada promoción:
 
 ## Verificar datos de uso de las promociones
 
-![seller-portal-promo-es](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/a65cab7ea0ee0983f80894668ca050d0/image.png)
+![seller-portal-promo-es](https://images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/a65cab7ea0ee0983f80894668ca050d0/image.png)
 
 Para ver el total de promociones activas en tu tienda y la cuota restante para nuevas promociones, haz clic en `Uso de las promociones`.
 
diff --git a/docs/tutorials/es/seller-portal-shared-products.md b/docs/tutorials/es/seller-portal-shared-products.md
index 0a4fc8dc9..1211ce4c5 100644
--- a/docs/tutorials/es/seller-portal-shared-products.md
+++ b/docs/tutorials/es/seller-portal-shared-products.md
@@ -29,7 +29,7 @@ Para acceder a la funcionalidad «Productos compartidos», acceda a la pestaña
 
 ## Importados
 
-![Shared products Importados EN](//images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/cde09ee87d8f119009fbc0b8cb8c5fef/Shared_products_Importados_ES.jpg)
+![Shared products Importados EN](https://images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/cde09ee87d8f119009fbc0b8cb8c5fef/Shared_products_Importados_ES.jpg)
 
 La pestaña «Importados» reúne los productos del catálogo del marketplace que ya han sido importados por el seller, es decir, que ya pueden convertirse en anuncios. La lista contiene una barra de búsqueda que permite buscar productos por nombre o SKU. А través de esta pestaña se activan los productos.  
 
@@ -39,7 +39,7 @@ Al hacer clic en un producto de la lista, accederá a la página [Detalles del P
 
 ## Disponibles
 
-![Shared products Disponíveis ES](//images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/0568df604b5d3754bd8f3b802dd646b1/Shared_products_Dispon__veis_ES.jpg)
+![Shared products Disponíveis ES](https://images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/0568df604b5d3754bd8f3b802dd646b1/Shared_products_Dispon__veis_ES.jpg)
 
 La pestaña «Disponibles» reúne los productos del catálogo del marketplace que se han puesto a disposición del seller para su venta y que aún no se han incorporado a su catálogo. Puede filtrar los productos disponibles por marca o categoría para agilizar el proceso de importación de los productos seleccionados. 
 
diff --git a/docs/tutorials/es/send-item-price-with-tax-shown-separately.md b/docs/tutorials/es/send-item-price-with-tax-shown-separately.md
index 2e43ebf88..685ab6d76 100644
--- a/docs/tutorials/es/send-item-price-with-tax-shown-separately.md
+++ b/docs/tutorials/es/send-item-price-with-tax-shown-separately.md
@@ -23,10 +23,10 @@ En este artículo vamos a mostrar como el sistema funciona para estos casos.
 
 **Escenario 1**: Mi ERP envía el precio ya con IVA a VTEX, entonces no necesito hacer el cálculo.
 
-1. Página de Categoría![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
-2. Página de Producto![PRODUCTOSINIVA](//images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
-3. Carrito![CARRITOSINIVA](//images.ctfassets.net/alneenqid6w5/3khmyZuLjWycCs6eSgUmci/0f466b0981d5f982db6ee79ed9a1f2a0/3_CART_E.png)
-4. Checkout![CHECKOUTSINIVA](//images.ctfassets.net/alneenqid6w5/6CAjPrEJG0Gm2oGwoekYW4/a5281e57a934b1845357a2af9725e48c/4_CHECK_E.png)
+1. Página de Categoría![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
+2. Página de Producto![PRODUCTOSINIVA](https://images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
+3. Carrito![CARRITOSINIVA](https://images.ctfassets.net/alneenqid6w5/3khmyZuLjWycCs6eSgUmci/0f466b0981d5f982db6ee79ed9a1f2a0/3_CART_E.png)
+4. Checkout![CHECKOUTSINIVA](https://images.ctfassets.net/alneenqid6w5/6CAjPrEJG0Gm2oGwoekYW4/a5281e57a934b1845357a2af9725e48c/4_CHECK_E.png)
 
 **Escenario 2**: Mi ERP envía el precio *sin* IVA a VTEX.
 
@@ -38,7 +38,7 @@ O entonces para crear un JS y sumar el valor del impuesto en las vitrinas, tambi
 
 __Atención__: En la pagina de producto es necesario poner un JavaScript para hacer la suma del valor.
 
-1. Página de Categoría![CATEGORIASINIVA](//images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
-2. Página de Producto![PRODUCTOCONIVA](//images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
-3. Carrito![CARRITOCONIVA](//images.ctfassets.net/alneenqid6w5/2Vqy71JAUMEKKMi6agQA6G/182ba9783f0a47e07e0ce9c91c7dec50/3A_CART_E.png)
-4. Checkout![CHECKOUTCONIVA](//images.ctfassets.net/alneenqid6w5/6rsFbUYg4Ee0sKIyai6Ooy/199adee53185253d4248d8a279fbbbf9/4A_CHECK_E.png)
+1. Página de Categoría![CATEGORIASINIVA](https://images.ctfassets.net/alneenqid6w5/5yDcEKh4VGYUuIu0W82A4o/15b1c183819fb83926b1f4dd88d9aace/1_CAT_E.png)
+2. Página de Producto![PRODUCTOCONIVA](https://images.ctfassets.net/alneenqid6w5/68zLscaDssq4WiAqYGkusc/1e0ec4b93ad2c7ff959094c1fef534fe/2_PROD_E.png)
+3. Carrito![CARRITOCONIVA](https://images.ctfassets.net/alneenqid6w5/2Vqy71JAUMEKKMi6agQA6G/182ba9783f0a47e07e0ce9c91c7dec50/3A_CART_E.png)
+4. Checkout![CHECKOUTCONIVA](https://images.ctfassets.net/alneenqid6w5/6rsFbUYg4Ee0sKIyai6Ooy/199adee53185253d4248d8a279fbbbf9/4A_CHECK_E.png)
diff --git a/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md b/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
index 5033b9e5a..500692826 100644
--- a/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
+++ b/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
@@ -31,10 +31,10 @@ Los valores aceptados por Mercado Libre se pueden encontrar en los siguientes ab
 
 __Links con los valores aceptados por Mercado Libre__:
 
-- [Brasil](//assets.contentful.com/alneenqid6w5/6BHWQLL9bGuMq2ycMye0uc/76e64b67cb7352d95d6bb977b33394d4/Brasil-2.zip)
-- [Argentina](//assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
-- [Colômbia](//assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
-- [México](//assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+- [Brasil](https://assets.contentful.com/alneenqid6w5/6BHWQLL9bGuMq2ycMye0uc/76e64b67cb7352d95d6bb977b33394d4/Brasil-2.zip)
+- [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
+- [Colômbia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
+- [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
 
 Después que la planilla se llene con los valores correctos, basta con hacer el __upload en Bridge__ de VTEX. Para ello, siga estos pasos:
 
@@ -49,7 +49,7 @@ __Listo!__ Ahora los atributos de sus productos de los tipos __Ropa__, __Calzado
 
 En Brasil, por ejemplo, un calzado *amarillo* con *detalles azules* de *tamaño 39* debe ser enviado al Mercado Libre con el __ID del SKU__ correspondiente y los códigos __33000_Amarelo_52007__, __43000_Azul_52092__ y __23000_39_22039__, relativos a *color principal*, *color secundario* y *talla*. Ver más ejemplos en la siguiente imagen:
 
-![Planilha modelo ML](//images.contentful.com/alneenqid6w5/1Z4UPfR5beG6SoMucASAm0/132e8316128421a2c98da7ee8fdb81b4/Planilha-modelo-ML.png)
+![Planilha modelo ML](https://images.contentful.com/alneenqid6w5/1Z4UPfR5beG6SoMucASAm0/132e8316128421a2c98da7ee8fdb81b4/Planilha-modelo-ML.png)
 
 ## Para saber más
 
diff --git a/docs/tutorials/es/sending-products-to-the-marketplace.md b/docs/tutorials/es/sending-products-to-the-marketplace.md
index 1d3460eb7..130e27c8c 100644
--- a/docs/tutorials/es/sending-products-to-the-marketplace.md
+++ b/docs/tutorials/es/sending-products-to-the-marketplace.md
@@ -21,7 +21,7 @@ Al integrarse con un marketplace, es necesario definir qué productos serán env
 
 Una posibilidad es trabajar todo el catálogo de productos junto al marketplace. Para ello, basta con asociar el ID de la política comercial de la tienda principal, que será siempre la de **ID 1**, [cuando solicitado en la configuración](/es/tutorial/integrando-con-marketplace).
 
-![ExemploPoliticaComercial](//images.contentful.com/alneenqid6w5/37CzxbrZ9KciYm4G2gK0MK/54a58d8fa3a53dcf310caa2769e53174/ExemploPoliticaComercial.png)
+![ExemploPoliticaComercial](https://images.contentful.com/alneenqid6w5/37CzxbrZ9KciYm4G2gK0MK/54a58d8fa3a53dcf310caa2769e53174/ExemploPoliticaComercial.png)
 
 Esta política comercial no demanda una colección de productos configurada, porque el sistema ya entiende que se refiere a todos los productos.
 
@@ -33,7 +33,7 @@ Otra posibilidad es trabajar con un surtido específico por alguna política com
 4. Marque el checkbox de las políticas comerciales a las que este producto deberá pertenecer.
 5. Haga clic en __Guardar__.
 
-![](//images.contentful.com/alneenqid6w5/2Fp2Y3qFF6SCwQaQI2iEiC/fae0654d1685f1f625794180044ae6a6/loja-cadastro-produto.gif)
+![](https://images.contentful.com/alneenqid6w5/2Fp2Y3qFF6SCwQaQI2iEiC/fae0654d1685f1f625794180044ae6a6/loja-cadastro-produto.gif)
 
 _Cuando existan productos que no tienen ningún valor marcado en el campo **tienda** en el registro de productos o en el registro de precios, esos productos serán enviados a todas las políticas comerciales configuradas sin colección.
 
diff --git a/docs/tutorials/es/sending-sku-attributes-to-amazon.md b/docs/tutorials/es/sending-sku-attributes-to-amazon.md
index 671d09d91..fabe5fd80 100644
--- a/docs/tutorials/es/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/es/sending-sku-attributes-to-amazon.md
@@ -19,7 +19,7 @@ Hechas las configuraciones iniciales para la [integración con Amazon](/es/tutor
 
 La asignación sólo se realizará una vez para cada categoría. De esta forma, incluso ya habiendo hecho un mapeo, cuando nuevos productos sean creados, ellos serán integrados directamente. Se hará un __de/para__ de los atributos registrados en VTEX con los atributos aceptados por Amazon.
 
-1. Cree una __planilla de upload__ en el formato `.xlsx` y rellene el título de las columnas según la imagen abajo.![Modelo Atributos Amazon](//images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
+1. Cree una __planilla de upload__ en el formato `.xlsx` y rellene el título de las columnas según la imagen abajo.![Modelo Atributos Amazon](https://images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
 
 2. Rellene los campos de la hoja de asignación de acuerdo con las indicaciones siguientes:
 
@@ -45,7 +45,7 @@ Nota: si <strong>ningún</strong> de los atributos de su categoría es requerido
 
 Planilla de ejemplo usando la categoría Clothing & Accessories:
 
-![Amazon Mapeamento ](//images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
+![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
 <div class="alert alert-danger">
 Recuerde que estos valores deben estar de acuerdo con los valores acceptados por Amazon. Consulte los términos permitidos y haga el De/Para entre lo que está registrado en su campo SKU en VTEX y los valores acceptador por Amazon.
diff --git a/docs/tutorials/es/sent-offers-beta.md b/docs/tutorials/es/sent-offers-beta.md
index 25802dbc2..c232e7f3c 100644
--- a/docs/tutorials/es/sent-offers-beta.md
+++ b/docs/tutorials/es/sent-offers-beta.md
@@ -21,7 +21,7 @@ El módulo «Anuncios enviados» permite a los sellers supervisar el envío de a
 - [Anúncios](https://help.vtex.com/es/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#anuncios)            
 - [Canales](https://help.vtex.com/es/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#canales) 
 
-![Anuncios enviados Home ES](//images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/b75456e0477b7025707752d87438b49a/Anuncios_enviados_Home_ES.jpg)
+![Anuncios enviados Home ES](https://images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/b75456e0477b7025707752d87438b49a/Anuncios_enviados_Home_ES.jpg)
 
 ## Anuncios
 Cuando un seller configura condiciones de precios y stock, prepara su producto para que se convierta en un anuncio y se venda en el estante del marketplace. En el componente *Anuncios*, se puede ver el número total de anuncios, y los status:
diff --git a/docs/tutorials/es/sent-offers-buybox-opportunities.md b/docs/tutorials/es/sent-offers-buybox-opportunities.md
index 2091699b7..dd529c3c7 100644
--- a/docs/tutorials/es/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/es/sent-offers-buybox-opportunities.md
@@ -40,19 +40,19 @@ En la página [Gestión de anuncios](https://help.vtex.com/es/tutorial/offers-li
 
 ## Detalles del anuncio
 
-![ES Oportunidades Offer details](//images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/b27410f2f77ff4b0f4e2faa689cc2cf6/ES_Oportunidades_Offer_details.jpg)
+![ES Oportunidades Offer details](https://images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/b27410f2f77ff4b0f4e2faa689cc2cf6/ES_Oportunidades_Offer_details.jpg)
 
 La página [Detalles del anuncio](https://help.vtex.com/es/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) presenta una tarjeta de `Oportunidad` en la parte superior de la página. Al hacer clic en `Ver oportunidad`, será redirigido a la siguiente página.
 
 ## Oportunidades del anuncio
 
-![ES Oportunidades oportunidades do anúncio](//images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/1a9aa381135ca8eb4298195fd7140ad9/ES_Oportunidades_oportunidades_do_an__ncio.jpg)
+![ES Oportunidades oportunidades do anúncio](https://images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/1a9aa381135ca8eb4298195fd7140ad9/ES_Oportunidades_oportunidades_do_an__ncio.jpg)
 
 La página **Oportunidades del anuncio** presenta el anuncio elegible para la Catálogo MeLi al lado del anuncio que está presente en el marketplace. La página le permite comparar los datos de los dos anuncios, incluida la información de la marca, especificaciones y dimensiones.
 
 Además de la oportunidad de agregar anuncios, existe __Auto Optin (creación automática de anuncios de Catálogo MeLi)__, en esta opción el Mercado Livre evaluará las publicaciones de los vendedores, si cumple con todos los requisitos para convertirse en un anuncio de Catálogo MeLi, será hecho automáticamente y el vendedor verá el siguiente mensaje.
 
-![Auto Optin MELI](//images.ctfassets.net/alneenqid6w5/2Hiw11uUW5n5QHvwIlpo0C/a0866adadfae08101dcb84cdfcc87ef7/Captura_de_tela_2023-06-27_175316.png)
+![Auto Optin MELI](https://images.ctfassets.net/alneenqid6w5/2Hiw11uUW5n5QHvwIlpo0C/a0866adadfae08101dcb84cdfcc87ef7/Captura_de_tela_2023-06-27_175316.png)
 
 ## Añadir anuncios a la Catálogo MeLi
 
diff --git a/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md b/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md
index d98f83a23..22b2ab7f8 100644
--- a/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md
+++ b/docs/tutorials/es/set-up-user-authentication-for-recurring-payments.md
@@ -27,6 +27,6 @@ Para configurar esta autenticación, siga los pasos abajo.
 2. Acceda **Configuración**
 3. Active la flag __Exigir autenticación del usuario para los pagos autorizados automáticamente__
 
-![autenticação-usuario-pagamento-recorrencia es](//images.ctfassets.net/alneenqid6w5/1W670r1zO4EQOUUqY2MmAs/1644f9c9e1fe370662ad9c2dfedea2f4/autentica____o-usuario-pagamento-recorrencia_es.png)
+![autenticação-usuario-pagamento-recorrencia es](https://images.ctfassets.net/alneenqid6w5/1W670r1zO4EQOUUqY2MmAs/1644f9c9e1fe370662ad9c2dfedea2f4/autentica____o-usuario-pagamento-recorrencia_es.png)
 
 4. Haga clic en el botón __Guardar__.
diff --git a/docs/tutorials/es/setting-up-a-personal-gift-message.md b/docs/tutorials/es/setting-up-a-personal-gift-message.md
index 45b379b54..66acede0a 100644
--- a/docs/tutorials/es/setting-up-a-personal-gift-message.md
+++ b/docs/tutorials/es/setting-up-a-personal-gift-message.md
@@ -44,11 +44,11 @@ En el sitio es posible validar si la configuración se ha efectuado correctament
 3. En este momento el tipo de servicio debe estar disponible para selección. El mensaje debe ser escrito en hasta 150 caracteres.
 4. Seleccione el servicio en el carrito y haga clic en el link para agregar mensaje.
 
-![](//images.contentful.com/alneenqid6w5/3txxLHOWtqguWu4qmAqumA/e68ef2cf4881d3b9a01199244567c790/mensagem-carrinho.png)
+![](https://images.contentful.com/alneenqid6w5/3txxLHOWtqguWu4qmAqumA/e68ef2cf4881d3b9a01199244567c790/mensagem-carrinho.png)
 
 Puede ver el mensaje escrito en la página de __Mi Cuenta > Mis Pedidos__:
 
-![](//images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
+![](https://images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
 
 <div class="alert alert-info">
   <p>Después de configurar el servicio en el SKU aguarde la indexación para que el registro tenga efecto en el sitio. Después de esto ya será posible probar la compra con este servicio activo.</p>
diff --git a/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md b/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md
index 35ff934cc..d8525cf6e 100644
--- a/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md
+++ b/docs/tutorials/es/setting-up-a-similar-product-suggestions-accessories-and-generics.md
@@ -35,7 +35,7 @@ Para ayudarlo a utilizar las técnicas arriba, podemos usar los campos en el reg
 4. Rellene los campos, como indicado abajo.
 5. Haga clic en el botón `Guardar`.
 
-![produto-similar-sugestão-acessório-exemplo es](//images.ctfassets.net/alneenqid6w5/5ZqMyFekmcoAggmAww44w6/a6bbabc539865f8b82fdc583469864d5/produto-simular-sugest__o-acess__rio-exemplo_es.png)
+![produto-similar-sugestão-acessório-exemplo es](https://images.ctfassets.net/alneenqid6w5/5ZqMyFekmcoAggmAww44w6/a6bbabc539865f8b82fdc583469864d5/produto-simular-sugest__o-acess__rio-exemplo_es.png)
 
 **Accesorios:** En este campo registramos los productos que deben venderse como complemento de otro producto. En esta opción, los productos registrados como accesorios se muestran como opción de compra con el checkbox de selección habilitado (función hecha en el layout).
 
diff --git a/docs/tutorials/es/setting-up-abandoned-carts.md b/docs/tutorials/es/setting-up-abandoned-carts.md
index 44d3a57a5..7ecb5270e 100644
--- a/docs/tutorials/es/setting-up-abandoned-carts.md
+++ b/docs/tutorials/es/setting-up-abandoned-carts.md
@@ -40,7 +40,7 @@ Puede crear su propio template de email personalizado o utilizar la opción de e
 4. Rellene el campo __Template XHTML__ con los códigos de template.
 5. Haga clic en `Save Template`.
 
-![template xhtml](//images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
+![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
 
 <div class="alert alert-warning">
 Recomendamos que lo realicen profesionales familiarizados con el módulo CMS, que ya hayan realizado la configuración de otros templates de página y expositor.
@@ -50,7 +50,7 @@ Recomendamos que lo realicen profesionales familiarizados con el módulo CMS, qu
 2. En __CMS > HTML Templates__, haga clic en el icono `CEM-Abandoned-Cart`.
 3. Verifique la información de los códigos de template presentes en el campo __Template XHTML__.
 
-![CEM-Abandoned-Cart](//images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
+![CEM-Abandoned-Cart](https://images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
 
 #### Configurar modelo de email en el Centro de mensajes
 
@@ -69,7 +69,7 @@ Una vez que se haya creado el nuevo template de email o se hayan utilizado los d
 El campo JSON Data no debe completarse ni sus datos deben usarse en el template de email. Solo contiene información para permitir una vista previa del formato en el que se verán los datos en el email.
 </div>
 
-![New template - message center](//images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
+![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
 
 #### Liberación del SPF
 
@@ -77,7 +77,7 @@ La liberación del SPF es fundamental para evitar problemas de entregabilidad de
 
 Como buena práctica para configurar DNS para un dominio genérico (no obligatorio), siga el siguiente ejemplo:
 
-![Hostnames - SPF](//images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
+![Hostnames - SPF](https://images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
 
 Para obtener más información sobre este asunto, consulte [Configurar el apuntamiento del DNS para VTEX](https://help.vtex.com/es/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280#).
 
@@ -126,7 +126,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><blockquote><ui>-> Último Carrinho - Não está nulo</ui> 
 
-![Filter master data 2](//images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/d6c7e5d4e84c5d2b8b870de4ee0db4bc/Filter_Master_Data.PNG)
+![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/d6c7e5d4e84c5d2b8b870de4ee0db4bc/Filter_Master_Data.PNG)
 
 <div class="alert alert-warning">
   Además de los filtros indicados anteriormente, se recomienda insertar otro filtro en el siguiente formato: <code>Receives newsletter? - Equal to - True</code>. Esto garantiza el cumplimiento de los <a href="https://help.vtex.com/es/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">derechos de los titulares de datos</a>, ya que solo los clientes suscritos al boletín recibirán correos electrónicos de carritos abandonados. La suscripción al boletín de su tienda se puede realizar en el momento de la compra o en la sección <a href="https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">Mi Cuenta</a> de su tienda.
@@ -134,7 +134,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><ui> 10. Haga clic en pestaña <b>Schedule</b> (Programación) y seleccione si desea enviar el correo electrónico en una fecha específica o en una fecha dinámica.</ui>
 
-![Schedule date](//images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/840f17bdc08c9703fdc972b2c8793668/Schedule_date.PNG)
+![Schedule date](https://images.ctfassets.net/alneenqid6w5/3SiaNvXMctzVtBzSjzsg3E/840f17bdc08c9703fdc972b2c8793668/Schedule_date.PNG)
 
 <blockquote><ui>11. En la pestaña <b>If positive</b> (Si es positivo):</ui>
 
@@ -157,7 +157,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><blockquote><ui>h. En <b>URL</b>, ingrese la dirección de su tienda con las carpetas en las que el layout del carrito abandonado fue configurado, con el tag del carrito después (?refs={!carttag_SCORE}). Ex.: nomedaloja.com.br/CEM/Abandoned-Cart?refs={!carttag_SCORE}.</ui>
 
-  ![PastasCarrinhoAbandonado](//images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)
+  ![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)
 
 <div class="alert alert-warning">Esta URL debe ser la final de la tienda, y no la URL con vtexcommercestable.
 </div>
@@ -171,7 +171,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 <div class="alert alert-warning">La sesión de una página expira en 30 minutos. Solamente después de ese tiempo consideramos la programación del disparo de trigger de Carrito Abandonado. Es decir, el tiempo a ser considerado es el tiempo de la sesión + la programación de trigger. 
 </div>
 
-![If positive tab](//images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/d863f83956f876035351cd222a0482ad/If_positive_Tab.PNG)
+![If positive tab](https://images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/d863f83956f876035351cd222a0482ad/If_positive_Tab.PNG)
 
 ### Configuración para tiendas VTEX IO
 
@@ -182,7 +182,7 @@ Para configurar la funcionalidad de carrito abandonado en las tiendas VTEX IO, s
 3. Realice la [liberación del SPF](#liberacion-del-spf).
 4. [Configure el trigger](#configuracion-de-trigger) de la misma manera que en las tiendas Legacy hasta el Paso 10. A partir del Paso 11 (pestaña __Si es positivo__), siga las instrucciones disponibles en [Trigger configuration information](https://developers.vtex.com/vtex-developer-docs/docs/vtex-abandoned-cart-service#trigger-configuration-information).
 
-![If positive tab IO](//images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/ce32f7997824f648690edefe77ad03c0/If_positive_Tab_IO.PNG)
+![If positive tab IO](https://images.ctfassets.net/alneenqid6w5/4kuuU7JySZQVklXS2jtfsp/ce32f7997824f648690edefe77ad03c0/If_positive_Tab_IO.PNG)
 
 ## Dudas frecuentes
 
diff --git a/docs/tutorials/es/setting-up-an-index-on-master-data.md b/docs/tutorials/es/setting-up-an-index-on-master-data.md
index dd0e2157e..bd71e8ffc 100644
--- a/docs/tutorials/es/setting-up-an-index-on-master-data.md
+++ b/docs/tutorials/es/setting-up-an-index-on-master-data.md
@@ -38,9 +38,9 @@ La tabla cliente posee 2 columnas: ID y &#8220;nome&#8221;(nombre).
 ID es un número que no se repite, pues es el número que identifica el cliente. Nome (Nombre) es el nombre del cliente.
 Sin embargo, para facilitar la búsqueda, la columna nome (nombre) fue creada como índice y configurada como **Valores Únicos**. 
 
-[![indice1](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png "![indice1](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)")Con eso, en caso de que quiera insertar un nombre que ya haya sido registrado en Cliente, no será posible.
+[![indice1](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png "![indice1](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)")Con eso, en caso de que quiera insertar un nombre que ya haya sido registrado en Cliente, no será posible.
 
-[![indice2](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png "![indice2](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)")
+[![indice2](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png "![indice2](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)")
 Este ejemplo no muestra que la opción **Valores Únicos** debe ser utilizada con mucho cuidado, pues, en caso de que el valor pueda ser repetido, no será permitido registrar dicho valor de acuerdo a la configuración hecha.
 
 ### Vários campos en el Índice
@@ -49,9 +49,9 @@ En este caso, la llave alternativa va a bloquear que la combinación de los camp
 
 Seguindo el mismo ejemplo, imagine que la entidad cliente tiene una columna más: CPF (DNI). Luego, la configuración del índice, en **Composição de campos**, fueron insertadas las columnas nome (nombre) y CPF (DNI).
 
-[![indice3](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png "![indice3](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)")
+[![indice3](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png "![indice3](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)")
 Con eso, es posible incluir el &#8220;Marcos&#8221; del ejemplo anterior, sin embargo no puede tener el mismo CPF (DNI) ya insertado anteriormente, o sea, solamente la combinación de campos es que no podrá repetirse. Pueden haver CPFs (DNIs) repetidos entre ellos y pueden haber nombres repetidos entre ellos, pero, jamás nombre + CPF iguales en registros diferentes.
 
-[![indice4](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png "![indice4](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)")
+[![indice4](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png "![indice4](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)")
 
 __Lembre-se!__ En este caso, también es necesario tener atención pues la misma combinación de valores no podrán repetirse y el registro será impedido de ser guardado. Sugerimos que el atributo **Valores Únicos** en el índice sea utilizado solamente cuando los valores no tienen la posibilidad de repetirse.
diff --git a/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
index 58a4cef79..193bdaf91 100644
--- a/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
@@ -17,7 +17,7 @@ subcategory:
 
 Este artículo tiene como objetivo explicar cómo la aplicación de inStore configura el AppLinking para las acciones de `payment` y `payment-reversal` con las apps de los adquirentes.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuración
 
diff --git a/docs/tutorials/es/setting-up-b2b-on-vtex.md b/docs/tutorials/es/setting-up-b2b-on-vtex.md
index aa44602b5..ba8568ce6 100644
--- a/docs/tutorials/es/setting-up-b2b-on-vtex.md
+++ b/docs/tutorials/es/setting-up-b2b-on-vtex.md
@@ -35,7 +35,7 @@ Este es el paso más importante para activar el B2B. Al configurar la Política
 
 Normalmente, en los B2Bs convencionales, este campo se rellena con el valor `approved="true"` (`approved` es el nombre de un campo en la entidad __Cliente__, en el Master Data). Con esa regla, el sistema sólo dejará que usuarios autenticados y aprobados naveguen en el sitio.
 
-![](//images.contentful.com/alneenqid6w5/34rM0gmlgQOoqwwEG2c0ck/a506984d2e7c23381e05a6ad16306d9f/1.png)
+![](https://images.contentful.com/alneenqid6w5/34rM0gmlgQOoqwwEG2c0ck/a506984d2e7c23381e05a6ad16306d9f/1.png)
 
 ## 2. Personalizar layout de directorios B2B
 
@@ -49,15 +49,15 @@ Vea las características básicas de cada tipo de usuario:
 
 Así, para tener un ambiente B2B, será necesario personalizar las carpetas **401** y **403**, hijas de la carpeta **sistema**.
 
-![](//images.contentful.com/alneenqid6w5/4eOGUWH7nWqyQGCmIou6WO/1910b62f54515007e85aa3a82d04fb9e/2.png)
+![](https://images.contentful.com/alneenqid6w5/4eOGUWH7nWqyQGCmIou6WO/1910b62f54515007e85aa3a82d04fb9e/2.png)
 
 Navegación por un usuario Anónimo (al intentar acceder cualquier página, será dirigido al 401):
 
-![](//images.contentful.com/alneenqid6w5/1bxTbhKatws2mgGiOGSUYW/8bf8e626bf53a8e785ffdcc5f2ffc813/3.png)
+![](https://images.contentful.com/alneenqid6w5/1bxTbhKatws2mgGiOGSUYW/8bf8e626bf53a8e785ffdcc5f2ffc813/3.png)
 
 Navegación por un usuario no aprobado (al intentar acceder cualquier página, será dirigido al 403):
 
-![](//images.contentful.com/alneenqid6w5/1Ep24Fgl1SIG6Uw8Wmkq42/2a995f8d9c2be0e92629447c1e6d3948/4.png)
+![](https://images.contentful.com/alneenqid6w5/1Ep24Fgl1SIG6Uw8Wmkq42/2a995f8d9c2be0e92629447c1e6d3948/4.png)
 
 ## 3. Definir campos de registro previo
 
@@ -73,7 +73,7 @@ Así, es necesario definir los campos de este registro previo. Normalmente, los
 
 Luego de definir los campos, deberá crear el formulario de registro previo en la carpeta **/sistema/401**, que es la única carpeta adonde el usuario anónimo siempre será dirigido.
 
-La información colocada en el formulario deberá ser enviada al CRM a través de las APIs del Master Data ([vea documentación](https://developers.vtex.com/reference/master-data-api-v2-overview)), o sea, será necesario desarrollar un JavaScript para aplicar esta función. Para ello, consulte un [ejemplo de plantilla HTML y JavaScript](//assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar "Ejemplo de plantilla HTML y JavaScript").
+La información colocada en el formulario deberá ser enviada al CRM a través de las APIs del Master Data ([vea documentación](https://developers.vtex.com/reference/master-data-api-v2-overview)), o sea, será necesario desarrollar un JavaScript para aplicar esta función. Para ello, consulte un [ejemplo de plantilla HTML y JavaScript](https://assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar "Ejemplo de plantilla HTML y JavaScript").
 
 ## 5. Operación
 
diff --git a/docs/tutorials/es/setting-up-cache-for-queries-to-master-data.md b/docs/tutorials/es/setting-up-cache-for-queries-to-master-data.md
index 3db79bfd9..012e0bbd6 100644
--- a/docs/tutorials/es/setting-up-cache-for-queries-to-master-data.md
+++ b/docs/tutorials/es/setting-up-cache-for-queries-to-master-data.md
@@ -26,7 +26,7 @@ Para configurar esta capa de caché, siga los pasos abajo:
 2. Haga clic en __Novo__ para crear una nueva entidad o en el icono de lápiz de una entidad existente si desea editarla.
 3. Haga clic en la casilla de verificación __Tempo de cache para consultas paginadas__ ("Tiempo de caché para consultas paginadas") y elija el tiempo de caché para la entidad.
 
-![cacheMD](//images.contentful.com/alneenqid6w5/7EJ8s7Z3uE0coc4QUkQcQC/0efbe18c6bd8018165e18f6d87da765f/cacheMD.jpg)
+![cacheMD](https://images.contentful.com/alneenqid6w5/7EJ8s7Z3uE0coc4QUkQcQC/0efbe18c6bd8018165e18f6d87da765f/cacheMD.jpg)
 
 Las opciones de tiempo de caché son:
 - 5 horas
diff --git a/docs/tutorials/es/setting-up-cybersource-gateway.md b/docs/tutorials/es/setting-up-cybersource-gateway.md
index 2dcd38cbd..a3cd5e592 100644
--- a/docs/tutorials/es/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/es/setting-up-cybersource-gateway.md
@@ -64,7 +64,7 @@ Siga los pasos a continuación:
 
 Con las claves de autenticación disponibles, es hora de configurar la aplicación Cybersource IO en el Admin. 
 
-![Cybersource Admin settings ES](//images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/ea8ae3e57058eb5c6da45af22a652ebd/Cybersource_Admin_settings_ES.JPG)
+![Cybersource Admin settings ES](https://images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/ea8ae3e57058eb5c6da45af22a652ebd/Cybersource_Admin_settings_ES.JPG)
 
 Siga los pasos a continuación para configurar la aplicación Cybersource IO:
 
@@ -190,7 +190,7 @@ document.body.appendChild(noScript);
 
 Además, puede definir campos personalizados que se incluirán en los pedidos enviados desde VTEX a Cybersource. 
 
-![Cybersource Admin merchant define fields ES](//images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/b9aa1888660f6fb63c77923243821125/Cybersource_Admin_merchant_define_fields_ES.JPG)
+![Cybersource Admin merchant define fields ES](https://images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/b9aa1888660f6fb63c77923243821125/Cybersource_Admin_merchant_define_fields_ES.JPG)
 
 Vea a continuación cómo crear estos campos:
 
diff --git a/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md b/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md
index 843feb6ed..f24c1ada2 100644
--- a/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md
+++ b/docs/tutorials/es/setting-up-intelligent-search-integration-with-the-catalog.md
@@ -25,6 +25,6 @@ Sigue las instrucciones a continuación para iniciar el proceso de integración:
 
 Se dará inicio al proceso de indexación. Una vez completado, se mostrará la siguiente pantalla:
 
-![integracoes-es](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/0e53cf7952ac60b089bbcb5f6441640e/integracoes-es.PNG)
+![integracoes-es](https://images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/0e53cf7952ac60b089bbcb5f6441640e/integracoes-es.PNG)
 
 No es necesario repetir este proceso. Una vez iniciada la integración, puedes realizar un seguimiento del status de indexación en la página [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
index 41c9f467a..1e010b856 100644
--- a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
@@ -36,18 +36,18 @@ Dicho esto, verifique el siguiente procedimiento:
 
 1. Acceda a su __cuenta de desarrollador__ Apple en `https://developer.apple.com/account/#/overview/`.
 2. Seleccione la opción __Certificates, ID & Profiles__.
-![AP1](//images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
+![AP1](https://images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
 3. Haga clic en __ Identifiers__.
- ![AP2](//images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
+ ![AP2](https://images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
 4. Al lado de Identifiers, haga clic en __botón azul +__.
-![AP3](//images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
+![AP3](https://images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
 5. Seleccione la opción __Merchant IDs__.
 6. Haga clic en el botón azul __Continue__.
-![AP4](//images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
+![AP4](https://images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
 7. Rellene el campo __Description__.
 8. Rellene el campo __Identifier__.
 9. Haga clic en el botón __Continue__.
-![AP5](//images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
+![AP5](https://images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
 
 De este modo, se creará el __Merchant ID__. 
 
@@ -62,14 +62,14 @@ En seguida, el administrador de la tienda puede enviarlo al sistema Apple Pay.
 Para comenzar esta etapa, continúe con las instrucciones:
 
 1. En el menú del lado izquierdo, seleccione __Certificates__.
-![AP6](//images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
+![AP6](https://images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
 2. Digite su __Merchant ID__ creado recientemente en la barra de búsqueda.
 3. Seleccione el __Merchant ID__ deseado.
-![AP7](//images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
+![AP7](https://images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
 4. En el ítem __ Apple Pay Payment Processing Certificate__, haga clic en el botón __Create Certificate__.
-![AP8](//images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
+![AP8](https://images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
 5. Asegúrese de que la pregunta *"Will payments associated with this Merchant ID be processed exclusively in China?"* esté marcada con __la opción default (No)__.
-![AP9](//images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
+![AP9](https://images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
 
 En seguida, será redirigido a una pantalla con instrucciones sobre la creación del CRS (Certificate Signing Request). 
 
@@ -82,9 +82,9 @@ Con el {{merchantID}}.csr. que recibió, finalice:
 1. Haga clic en __Choose File__.
 2. Seleccione el __archivo CSR__ deseado.
 3. Haga clic en el botón __Continue__.
-![AP10](//images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
+![AP10](https://images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
 4. Haga clic en __Download__.
-![AP11](//images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
+![AP11](https://images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
 5. Haga clic en __Done__.
 
 ## Registrando dominios en el Merchant ID
@@ -101,17 +101,17 @@ Finalmente, es necesario importar este archivo al sistema de VTEX a través de P
 Verifique las instrucciones:
 
 1. Digite el __Merchant ID__ creado recientemente en la barra de búsqueda.
-![AP12](//images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
+![AP12](https://images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
 2. Haga clic en el __Merchant ID__ deseado.
 3. En el módulo __Merchant Domains__, haga clic en el botón __Add Domain__.
-![AP13](//images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
+![AP13](https://images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
 4. Agregue el dominio en el campo __Enter the domain you wish to register__.
 5. Haga clic en __Save__.
 
 Ahora, para hacer upload del archivo `.txt` por medio de la API, prosiga con las instrucciones:   
 
 1. Haga clic en __Download__ y no realice ninguna alteración en el archivo.  
-![AP14](//images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
+![AP14](https://images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
 2. Abra el archivo `.txt` y __copie__ todo el contenido.
 
 En seguida, inicie una sesión en el Postman. Usted realizará una llamada vía POST para la CDN de VTEX:  
@@ -123,7 +123,7 @@ En seguida, inicie una sesión en el Postman. Usted realizará una llamada vía
 Al realizar la llamada *POST*, la respuesta debe informar que el certificado se guardará durante 60 minutos. Durante este tiempo, debe completar la validación del dominio.
 
 Ahora, regrese al sitio web de Apple. En la misma pantalla donde descargó el archivo `.txt`, haga clic en __Verify__.
-![AP15](//images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
+![AP15](https://images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
 
 Así, si el procedimiento se realiza correctamente, el dominio se registrará con el estado __Verified__. Si lo desea, puede repetir todo el proceso para registrar más dominios utilizando el botón __Add Domain__ en la sección __Merchant Domains__.
 
@@ -140,15 +140,15 @@ Atención: Recomendamos que la contraseña sea fácil de recordar, ya que se ing
 1. Acceda al módulo __Certificates, Identifiers & Profilers__.
 2. En el menú del lado izquierdo, haga clic en __Identifiers__.
 3. En la esquina superior derecha, filtre por __Merchant IDs__.
-![AP16](//images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
+![AP16](https://images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
 4. Seleccione el __Merchant Identifier__ deseado.
 5. Haga clic en __Create Certificate__.
-![AP17](//images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
+![AP17](https://images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
 6. Siga las __instrucciones__ que se muestran en la pantalla para crear un certificado. 
 7. Haga clic en el botón __Continue__.
-![AP18](//images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
+![AP18](https://images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
 8. Haga clic en __Download__.    
-![AP19](//images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
+![AP19](https://images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
 
 Ahora, cuando se descargué el archivo, haga doble clic para instalarlo en Keychain Access.
 
@@ -156,7 +156,7 @@ Luego, continúe con el procedimiento:
 
 1. Abra el __Keychain Access__.
 2. Localice el __certificado__ creado en el paso cuatro anterior.
-3. Haga clic derecho en el ícono __llave__. ![AP20](//images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
+3. Haga clic derecho en el ícono __llave__. ![AP20](https://images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
 4. Haga clic en __Export__.
 5. Nombre el __certificado__.
 6. Seleccione el formato de exportación __.p12__.
diff --git a/docs/tutorials/es/setting-up-payments-with-easypay-seller.md b/docs/tutorials/es/setting-up-payments-with-easypay-seller.md
index dabcc7020..fa75b66b0 100644
--- a/docs/tutorials/es/setting-up-payments-with-easypay-seller.md
+++ b/docs/tutorials/es/setting-up-payments-with-easypay-seller.md
@@ -45,7 +45,7 @@ Después de instalar la aplicación easypay seller account, debes configurarla.
 
 <blockquote><ui>- <b>Easypay Account UID</b>: identificación de la cuenta seller en la que se abonarán los valores de la compra de productos adquiridos en la tienda. Para obtener esta información, accede al <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la esquina superior de la pantalla y, a continuación, en la cuenta deseada. Copia y guarda la información <b>Account UID</b>.</ui> 
 
-![easypay_pt_18](//images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/e9218fcccf92ed76e45024aa1c4c2285/easypay_pt_18.PNG)
+![easypay_pt_18](https://images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/e9218fcccf92ed76e45024aa1c4c2285/easypay_pt_18.PNG)
 
 <blockquote><ui>4. Haz clic en <b>Guardar</b>.</ui>
 
diff --git a/docs/tutorials/es/setting-up-payments-with-easypay.md b/docs/tutorials/es/setting-up-payments-with-easypay.md
index af54e40ef..b160fba8c 100644
--- a/docs/tutorials/es/setting-up-payments-with-easypay.md
+++ b/docs/tutorials/es/setting-up-payments-with-easypay.md
@@ -48,7 +48,7 @@ La información de configuración se divide en cuatro secciones:
 - [Personalización del checkout de easypay (opcional)](#personalizacion-del-checkout-de-easypay)
 - [Modo sandbox](#modo-sandbox)
 
-![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+![easypay_pt_1](https://images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
 
 <div class="alert alert-warning" role="alert">Debes realizar la configuración en <a href="https://backoffice.easypay.pt/">el entorno easypay</a>. El control de estas configuraciones es responsabilidad de easypay, por lo tanto, VTEX no garantiza que los pasos a continuación estén siempre actualizados. Utiliza este documento como referencia y consulta tu cuenta en el <a href="https://backoffice.easypay.pt/">entorno de easypay</a> para obtener información actualizada.</div>
 
@@ -60,25 +60,25 @@ __Key ID y Key Value__: valor e ID de la clave easypay.
 
 <blockquote><ui>1. En el <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la parte superior izquierda de la pantalla, y en el ícono de la flecha que señala la cuenta deseada.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
 <blockquote><ui>2. Accede a <b>Web Services > Configuración API 2.0 > Keys</b>.</ui>
 
-![easypay_es_3](//images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/b52af6fe6df6694a8ee073bd0561167f/easypay_en_3.png)
+![easypay_es_3](https://images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/b52af6fe6df6694a8ee073bd0561167f/easypay_en_3.png)
 
 <blockquote><ui>3. Copia y guarda la información <b>ID</b> y <b>Key</b>.</ui>
 
-![easypay_es_4](//images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/57f61df73ca3ea38e4cb3d9234e5e3c6/easypay_en_4.png)
+![easypay_es_4](https://images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/57f61df73ca3ea38e4cb3d9234e5e3c6/easypay_en_4.png)
 
 __Merchant account UID__: identificación de la cuenta del comerciante en la que se abonarán los valores de la compra de productos adquiridos en la tienda. Si no dispones de una cuenta comerciante independiente, puedes utilizar el "Account UID" de la cuenta donde recibirás los pagos.
 
 <blockquote><ui>1. En el <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la esquina superior izquierda de la pantalla y, a continuación, en la cuenta "COMERCIANTE 1", haz clic en la flecha.</ui>
 
-![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+![easypay_pt_5](https://images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
 
 <blockquote><ui>2. Copia y guarda la información del <b>Account UID</b>.</ui>
 
-![easypay_es_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/ca21af021e53fe89b50f0f650ecb0db1/easypay_en_6.png)
+![easypay_es_6](https://images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/ca21af021e53fe89b50f0f650ecb0db1/easypay_en_6.png)
 
 __Margin account UID__: identificación de la cuenta de margen.
 
@@ -90,7 +90,7 @@ __Refund account ID e Refund account key__: si no existe una cuenta específica
 
 En esta sección, debes indicar si tu tienda utilizará pagos asíncronos, síncronos o ambos. Accede a la documentación de easypay para consultar los [medios de pagos](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) disponibles y sus respectivas [siglas](https://docs.quality-utility.aws.easypay.pt/checkout/reference) de identificación.
 
-![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+![easypay_pt_7](https://images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
 
 __Tipos de pago asíncronos aceptados__: medios de pago asíncronos disponibles para el cliente. Ingresa solamente las siglas de los tipos de asíncronos, separadas por comas, sin puntos ni espacios.
 
@@ -122,7 +122,7 @@ Ejemplo:
 
 easypay tiene un diseño de checkout nativo configurado en la aplicación, como se muestra a continuación:
 
-![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+![easypay_pt_8](https://images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
 
 Si deseas realizar algún tipo de personalización en el checkout nativo de easypay, rellena uno o más campos de esta sección:
 
@@ -174,7 +174,7 @@ Para configurar el webhook de easypay, sigue los pasos que se indican a continua
 
 <blockquote><ui>1. En el <a href="https://backoffice.easypay.pt/">entorno easypay</a>, haz clic en el logotipo de easypay situado en la parte superior izquierda de la pantalla, y en el ícono de la flecha que señala la cuenta deseada.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
 <blockquote><ui>2. Accede a <b>Web Services > URL Configuration</b>.</ui>
 
@@ -182,7 +182,7 @@ Para configurar el webhook de easypay, sigue los pasos que se indican a continua
 
 `https://{nombre-de-tu-cuenta}.myvtex.com/_v/easypaypartnerpt.payment-provider-easypay/webhook`
 
-![easypay_es_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/82c01b7233e55da18bd664f274dba813/easypay_en_9.png)
+![easypay_es_9](https://images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/82c01b7233e55da18bd664f274dba813/easypay_en_9.png)
 
 <blockquote><ui>4. Haz clic en <b>Submit</b>.</ui>
 
diff --git a/docs/tutorials/es/setting-up-payments-with-itau-rede.md b/docs/tutorials/es/setting-up-payments-with-itau-rede.md
index 90426548a..2b946b3e2 100644
--- a/docs/tutorials/es/setting-up-payments-with-itau-rede.md
+++ b/docs/tutorials/es/setting-up-payments-with-itau-rede.md
@@ -35,27 +35,27 @@ Para obtener las credenciales __Clave de aplicación__ y __Token de aplicación_
 
 <blockquote><ui>2. Seleccione la cuenta en la que desea realizar pagos en VTEX y haga clic en <b>Aplicar</b>. Guarde el número de cuenta, ya que debe ser utilizado en el campo <b>Clave de aplicación</b> de la sección <a href="#configurar-itau-rede-en-vtex">Configurar Itaú Rede en VTEX</a>.</ui>
 
-![Itaú Rede_1](//images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
+![Itaú Rede_1](https://images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
 
 <blockquote><ui>3. Después de que la pantalla se actualice a la cuenta deseada, en el menú <b>para vender</b>, seleccione la opción <b>e-commerce</b>.</ui>
 
-![Itaú Rede_2](//images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
+![Itaú Rede_2](https://images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
 
 <blockquote><ui>4. En la página <b>e-commerce</b>, haga clic en la tarjeta <b>chave de integração</b>.</ui>
 
-![Itaú Rede_3](//images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
+![Itaú Rede_3](https://images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
 
 <blockquote><ui>5. Después de leer la información de la "chave de integração", haga clic en <b>li, estou ciente</b>.</ui>
 
-![Itaú Rede_4](//images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
+![Itaú Rede_4](https://images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
 
 <blockquote><ui>6. Haga clic en el botón <b>gerar nova chave</b>.</ui>
 
-![Itaú Rede_5](//images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
+![Itaú Rede_5](https://images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
 
 <blockquote><ui>7. Verifique la información descrita en la ventana <b>gerar nova chave de integração</b> y haga clic en <b>gerar nova chave</b>.</ui>
 
-![Itaú Rede_6](//images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
+![Itaú Rede_6](https://images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
 
 <blockquote><ui>8. Después de crear la nueva clave, haga clic en <b>copiar</b> y conserve la información en un lugar seguro. Esta clave debe ser utilizada en el campo <b>Token de aplicación</b> de la sección <a href="#configurar-itau-rede-en-vtex">Configurar Itaú Rede en VTEX</a>.</ui>
 
diff --git a/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md b/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md
index acf33ae30..06dae3ddd 100644
--- a/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md
+++ b/docs/tutorials/es/setting-up-personal-data-on-the-users-screen.md
@@ -21,21 +21,21 @@ Para acceder a esta, siga los pasos a continuación:
 
 1. En la barra superior del Admin, en la esquina derecha, haga clic en el botón con la inicial de su nombre.
 2. Haga clic en la opción __Ajustes de usuario__.  
-![Opção Configurações de usuário User Management ES](//images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/78a9966c5f845964155876b5eaaad046/Op____o_Configura____es_de_usu__rio_User_Management_ES.png)
+![Opção Configurações de usuário User Management ES](https://images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/78a9966c5f845964155876b5eaaad046/Op____o_Configura____es_de_usu__rio_User_Management_ES.png)
 
 Hay dos opciones en el menú:
 
 - En __Personal__, usted puede ver su nombre, su email y su número de teléfono registrado en el Admin.  
-![Configuração Pessoal User Management ES](//images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/f4de16a2eac3bcd839457bb27b3a6600/Configura____o_Pessoal_User_Management_ES.png)
+![Configuração Pessoal User Management ES](https://images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/f4de16a2eac3bcd839457bb27b3a6600/Configura____o_Pessoal_User_Management_ES.png)
 
 - Al hacer clic en __Nombre__, tendrá la opción de editar su nombre y apellido.  
-![Configuração Nome User Management ES](//images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/497b4fda29df1738e4e82443746cff93/Configura____o_Nome_User_Management_ES.png)
+![Configuração Nome User Management ES](https://images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/497b4fda29df1738e4e82443746cff93/Configura____o_Nome_User_Management_ES.png)
 
 - Al hacer clic en __Número de celular__, tendrá la opción de editar su número de celular con el código del país.  
-![Configuração Celular User Management ES](//images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/216dedc0b6cd726ffcc0842662d24cab/Configura____o_Celular_User_Management_ES.png)
+![Configuração Celular User Management ES](https://images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/216dedc0b6cd726ffcc0842662d24cab/Configura____o_Celular_User_Management_ES.png)
 
 - En __Autenticación__, usted encuentra las opciones de cambio de contraseña, gestión de la verificación en 2 pasos (2FA) para su inicio de sesión en el Admin VTEX y gestión de sesiones. A continuación, vea cuáles son esas opciones.  
-![Configuração Autenticação User Management ES](//images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/3612591bcfcf2283125311c8defad942/Configura____o_Autentica____o_User_Management_ES.png)
+![Configuração Autenticação User Management ES](https://images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/3612591bcfcf2283125311c8defad942/Configura____o_Autentica____o_User_Management_ES.png)
 
 ## Verificación en 2 pasos
 
@@ -53,5 +53,5 @@ Aquí, usted debe configurar la aplicación que proporcionará la clave de auten
 
 Vea en detalle cómo configurar la aplicación en el artículo [Habilitar inicio de sesión por autenticación de 2 factores](https://help.vtex.com/es/tutorial/habilitar-login-por-autenticacao-de-2-fatores).
 
-![Configuração Verificação em 2 passos User Management ES](//images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2977fce5188bebcc443d4bed4b58afb3/Configura____o_Verifica____o_em_2_passos_User_Management_ES.png)
+![Configuração Verificação em 2 passos User Management ES](https://images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2977fce5188bebcc443d4bed4b58afb3/Configura____o_Verifica____o_em_2_passos_User_Management_ES.png)
 
diff --git a/docs/tutorials/es/setting-up-price-tables-for-specific-users.md b/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
index e0be9d526..dd2316c21 100644
--- a/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
@@ -92,7 +92,7 @@ Cuando un usuario de su tienda no ha iniciado sesión, los precios que se le mue
 Si el usuario ha iniciado sesión, verá los precios correspondientes a la tabla de precios a la que está asociado su e-mail.
 
 Por ejemplo, estos dos clientes están vinculados a tablas de precios diferentes:
-![Clients](//images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
+![Clients](https://images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
 
 Cuando el cliente Daniel, que está vinculado a la tabla Silver, inicie sesión en la tienda, verá los precios establecidos en dicha tabla. La mochila del ejemplo anterior aparecerá a USD 50.
 En cambio, el cliente Breno, que está vinculado a la tabla Gold, verá los precios definidos en esta otra tabla. Para él, la mochila costará USD 60,50.
diff --git a/docs/tutorials/es/setting-up-shipment.md b/docs/tutorials/es/setting-up-shipment.md
index db168a712..9b43e4118 100644
--- a/docs/tutorials/es/setting-up-shipment.md
+++ b/docs/tutorials/es/setting-up-shipment.md
@@ -27,7 +27,7 @@ La primera caja con tiempo total de __2 días__ esperará el item representado p
 
 El período considera T = 0 como la fecha del pedido.
 
-![Configuração em estoque e entrega ES](//images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/79aa792b4179662cb5e55a00b1523851/Configura____o_em_estoque_e_entrega_ES.png)
+![Configuração em estoque e entrega ES](https://images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/79aa792b4179662cb5e55a00b1523851/Configura____o_em_estoque_e_entrega_ES.png)
 
 ## Cómo configurar el envío en grupo
 
diff --git a/docs/tutorials/es/setting-up-sms-password-recovery.md b/docs/tutorials/es/setting-up-sms-password-recovery.md
index 81415f034..2278e67bc 100644
--- a/docs/tutorials/es/setting-up-sms-password-recovery.md
+++ b/docs/tutorials/es/setting-up-sms-password-recovery.md
@@ -26,13 +26,13 @@ Dicho esto, eche un vistazo al paso a paso de cómo configurar esta modalidad:
 1. Acceda a la __Central de Mensajes__.
 2. Haga clic en __Templates__.
 
-  ![5NrtBpFRTxInFl4aY2FrVz-es](//images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/afff0b3f7b7b84e4379f55bd2cc05d7e/5NrtBpFRTxInFl4aY2FrVz-es.png)
+  ![5NrtBpFRTxInFl4aY2FrVz-es](https://images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/afff0b3f7b7b84e4379f55bd2cc05d7e/5NrtBpFRTxInFl4aY2FrVz-es.png)
 
 3. Haga clic en el template __Password Recovery__.
 4. Haga clic en la pestaña __SMS__;
 5. Seleccione la opción __"Activar envío de SMS?"__.
 
-  ![password-recovery-sms-tab-es](//images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/3d53d4e4586a14e5e7b34b5f9c8df84b/password-recovery-sms-tab-es.gif)
+  ![password-recovery-sms-tab-es](https://images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/3d53d4e4586a14e5e7b34b5f9c8df84b/password-recovery-sms-tab-es.gif)
 
   *En el momento en que el usuario hace clic en "Activar envío de SMS", la plataforma muestra las demás configuraciones de envío.*
 
@@ -40,7 +40,7 @@ Dicho esto, eche un vistazo al paso a paso de cómo configurar esta modalidad:
 7. Rellene el campo __Destination__ con la variable `{{_accountInfo.Telephone}}`.
 8. Rellene el campo __Message Text__ con el contenido del mensaje. Las informaciones `Nombre: {{nombre}}`, `Login: {{login}}` y `Contraseña: {{contraseña}}` son esenciales.
 
-  ![password-recovery-sms-fields-es](//images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/46e9fa31dd9a4be8bdd3840ddd51eb92/password-recovery-sms-fields-es.png)
+  ![password-recovery-sms-fields-es](https://images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/46e9fa31dd9a4be8bdd3840ddd51eb92/password-recovery-sms-fields-es.png)
 
 9. Revise el contenido del SMS en __Preview__.
 10. Haga clic en __Guardar__.
diff --git a/docs/tutorials/es/setting-up-the-critical-stock-alert.md b/docs/tutorials/es/setting-up-the-critical-stock-alert.md
index 718cf7bef..e70a737e7 100644
--- a/docs/tutorials/es/setting-up-the-critical-stock-alert.md
+++ b/docs/tutorials/es/setting-up-the-critical-stock-alert.md
@@ -23,7 +23,7 @@ La alerta de inventario crítico es una funcionalidad de logística que tiene el
 2. En **Configuración**, rellena lo campo de **Alerta de inventario crítico**.  
 3. Haga clic en **Salvar**.
 
-![alerta-estoque-critico es](//images.ctfassets.net/alneenqid6w5/3sIAJKB8AogSyQeEqYokCe/f696e3e2cc5ab214eeda18b7ce5f7098/alerta-estoque-critico_es.png)
+![alerta-estoque-critico es](https://images.ctfassets.net/alneenqid6w5/3sIAJKB8AogSyQeEqYokCe/f696e3e2cc5ab214eeda18b7ce5f7098/alerta-estoque-critico_es.png)
 
 Como usted puede ver por la imagen, ella puede ser marcada con flecha por cantidad de ítems o por porcentual.
 
diff --git a/docs/tutorials/es/setting-up-the-css-for-the-product-zoom.md b/docs/tutorials/es/setting-up-the-css-for-the-product-zoom.md
index 85fb06a9c..9e2a0314a 100644
--- a/docs/tutorials/es/setting-up-the-css-for-the-product-zoom.md
+++ b/docs/tutorials/es/setting-up-the-css-for-the-product-zoom.md
@@ -25,7 +25,7 @@ Abajo reproducimos un trecho de CSS que puede usar como punto de partida para es
 
 Luego, vamos a enviar el archivo CSS grabado al servidor. Para eso, haga clic en el menú _Configurações__&gt; Portal_ dentro del Admin.
 
-![](//images.contentful.com/alneenqid6w5/3uLeF6wpvq4m4Wis48eeE8/4f79bf7753fb25309b670e9ea702a3ad/configuracao_zoom.gif)
+![](https://images.contentful.com/alneenqid6w5/3uLeF6wpvq4m4Wis48eeE8/4f79bf7753fb25309b670e9ea702a3ad/configuracao_zoom.gif)
 
 En la ventana que se despliega a la derecha, haga clic en el botón **Adicionar**.
 
@@ -33,4 +33,4 @@ Luego, localice el archivo CSS grabado arriba y envíelo al servidor haciendo cl
 
 Así, su archivo figurará en la ventana, como en la imagen abajo:
 
-![](//images.contentful.com/alneenqid6w5/2pWBIqL3So2wm04oU8CyQ8/ab9f623fd28f15e2708cc3fcbecafe03/gerenciador_arq_css-560x373.jpg)
+![](https://images.contentful.com/alneenqid6w5/2pWBIqL3So2wm04oU8CyQ8/ab9f623fd28f15e2708cc3fcbecafe03/gerenciador_arq_css-560x373.jpg)
diff --git a/docs/tutorials/es/setting-up-the-notify-me-option.md b/docs/tutorials/es/setting-up-the-notify-me-option.md
index c08d945e8..45ba498de 100644
--- a/docs/tutorials/es/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/es/setting-up-the-notify-me-option.md
@@ -23,7 +23,7 @@ Cuando no hay [stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inven
 
 A continuación, puedes ver un ejemplo de cómo se visualiza la opción **Avísame** en una tienda. Para recibir una notificación cuando el ítem esté disponible para la venta, el cliente debe ingresar su nombre e email en los campos resaltados y luego hacer clic en el botón `Enviar`.
 
-![aviseme-es](//images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/a00bc93c8475050d5861859016a8915c/Group_2__2_.png)
+![aviseme-es](https://images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/a00bc93c8475050d5861859016a8915c/Group_2__2_.png)
 
 En cuanto el ítem ingrese de nuevo al stock de la tienda, el sistema envía automáticamente un email al cliente informándo le que el producto ya está disponible para la compra. 
 
diff --git a/docs/tutorials/es/setting-up-the-price-range-filter.md b/docs/tutorials/es/setting-up-the-price-range-filter.md
index 24750617d..55e22c170 100644
--- a/docs/tutorials/es/setting-up-the-price-range-filter.md
+++ b/docs/tutorials/es/setting-up-the-price-range-filter.md
@@ -20,7 +20,7 @@ Importantísimas para navegación y búsqueda de los productos deseados en la ti
 
 El registro es sencillo y se pueden determinar diferentes rangos de precios para categorías, conforme a la imagen abajo:
 
-![faixa-de-preço es](//images.ctfassets.net/alneenqid6w5/2j45MP5kMsA02YeMgMCy2y/9fa923fbae98e90882fabff0e2f7cf17/faixa-de-pre__o_es.png)
+![faixa-de-preço es](https://images.ctfassets.net/alneenqid6w5/2j45MP5kMsA02YeMgMCy2y/9fa923fbae98e90882fabff0e2f7cf17/faixa-de-pre__o_es.png)
 
 Dentro de Fajas de Precio, haga clic en “Nuevo rango de precio” y rellene los campos:
 
diff --git a/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
index d008c6d60..e02454f26 100644
--- a/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
@@ -25,23 +25,23 @@ Para facilitar, toda la configuración que se muestra en este artículo se puede
 
 Para la configuración manual o la edición de una meta existente, el primer paso es acceder a Analytics y hacer clic en el botón __Administrador__ en la esquina inferior izquierda. A continuación, vaya a la opción __Metas__, de la columna "Vista".
 
-![image](//images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
 
 En la pantalla de administración de metas, opte por crear una nueva o editar una ya existente.
 
 __En el paso 1__ usted puede seguir con una meta de tipo personalizado:
 
-![image](//images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
 
 __En el paso 2__ usted puede definir el nombre que prefiera para su meta y un código de posición (de uso interno de Google Analytics). En el tipo, vamos a usar "Destino":
 
-![image](//images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
 
 __En el paso 3__ tenemos las configuraciones más sensibles. En él configuramos la página que determina la conclusión de la meta y el camino que los clientes van a recorrer para alcanzarla.
 
 En el campo "Destino" seleccione la opción de expresión regular e introduzca la dirección URL de la página de pedido completa: `^/checkout/orderPlaced`
 
-![image](//images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
 
 Luego configure la ruta que el cliente va a recorrer hasta que finalice un pedido. En este caso, tenemos en cuenta que el proceso de compra se inicia en la pantalla del producto; entonces mi embudo servirá para medir la cantidad de clientes que accede a esa pantalla, cuántos pedidos se han finalizado y en qué paso los clientes están desistiendo de la compra.
 
@@ -54,7 +54,7 @@ Aún en el paso 3, active la opción __Embudo__ con los siguientes pasos:
  - __Envío__ = `^/checkout/(\?.*)?#/shipping$`
  - __Pago__ =  `^/checkout/(\?.*)?#/payment$`
 
-![image](//images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
 
 Una forma de comprobar si la meta está configurada correctamente es usar el enlace "Compruebe esta meta". Google va a generar una simulación de la conversión de la meta en los últimos 7 días.
 
diff --git a/docs/tutorials/es/setting-up-the-type-of-interest-rate.md b/docs/tutorials/es/setting-up-the-type-of-interest-rate.md
index 84c8c659f..b7b782ed2 100644
--- a/docs/tutorials/es/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/es/setting-up-the-type-of-interest-rate.md
@@ -25,7 +25,7 @@ El ID de la forma de pago que se configurará a Interés Simple se obtiene del s
 - Ingresar a la Forma de Pago que se desea configurar para que utilice Interés Simple
 - Copiar el último parámetro de la URL, que indica el ID de esa Forma de Pago (ver imagen)
 
-![Interes Simple - Obtener ID Transaccion](//images.contentful.com/alneenqid6w5/19PugiXjNssA6c48WoqoSC/808db9360d3dbb5dd12466882ce3e852/interes-simple-id-transaccion.png)
+![Interes Simple - Obtener ID Transaccion](https://images.contentful.com/alneenqid6w5/19PugiXjNssA6c48WoqoSC/808db9360d3dbb5dd12466882ce3e852/interes-simple-id-transaccion.png)
 
 ## Configurar el tipo de interés mediante la API
 
diff --git a/docs/tutorials/es/setting-up-the-voucher-list.md b/docs/tutorials/es/setting-up-the-voucher-list.md
index fc9584987..5e70cef16 100644
--- a/docs/tutorials/es/setting-up-the-voucher-list.md
+++ b/docs/tutorials/es/setting-up-the-voucher-list.md
@@ -26,13 +26,13 @@ Es necesaria una configuración de SKU con las siguientes características para
 - El SKU debe tener el precio de R$0,01.
 - El SKU debe ser configurado para generar crédito en vale.
 
-![sku-opção-credito-vale es](//images.ctfassets.net/alneenqid6w5/5jtCFBYaME4muoOKg8eWQE/9f8da92008fd49aa99fc123b8141a0fc/sku-op____o-credito-vale_es.png)
+![sku-opção-credito-vale es](https://images.ctfassets.net/alneenqid6w5/5jtCFBYaME4muoOKg8eWQE/9f8da92008fd49aa99fc123b8141a0fc/sku-op____o-credito-vale_es.png)
 
 ## Configuraciones en el Tipos de Lista
 
 La creación de este tipo de lista pide, en las configuraciones, que la entrega se marque como "Valor de los productos comprados será convertido en un vale de compras". Vea la imagen de ejemplo:
 
-![entrega-tipos-lista ew](//images.ctfassets.net/alneenqid6w5/5vtZiXaAPS0iWow2EgA4OE/6cf83c7a2402bdf95233cfe0729f54e7/entrega-tipos-lista_ew.png)
+![entrega-tipos-lista ew](https://images.ctfassets.net/alneenqid6w5/5vtZiXaAPS0iWow2EgA4OE/6cf83c7a2402bdf95233cfe0729f54e7/entrega-tipos-lista_ew.png)
 
 Grabe su lista después de realizar las demás configuraciones deseadas.
 
diff --git a/docs/tutorials/es/setting-up-vtex-instore-logistics.md b/docs/tutorials/es/setting-up-vtex-instore-logistics.md
index 688db5bef..5b1034626 100644
--- a/docs/tutorials/es/setting-up-vtex-instore-logistics.md
+++ b/docs/tutorials/es/setting-up-vtex-instore-logistics.md
@@ -21,6 +21,6 @@ La ruta de check-in do Checkout llama en su flujo el Logistics. ¿Qué quiere de
 
 Tras el registro de su(s) tienda(s) en el MasterData [vea aquí cómo hacerlo](/es/tutorial/como-registrar-tiendas-en-el-vtex-instore), usted podrá elegir la tienda que le gustaría asociar a esa dársena por el dropdown conforme a la imagen a continuación:
 
-![2017-06-16 16 43 14-VTEX - Logística](//images.contentful.com/alneenqid6w5/2NIbvde6HSK6OUCWUcwigq/879c7de324037ebb2ffbc64d768d7404/2017-06-16_16_43_14-VTEX_-_Log__stica.png)
+![2017-06-16 16 43 14-VTEX - Logística](https://images.contentful.com/alneenqid6w5/2NIbvde6HSK6OUCWUcwigq/879c7de324037ebb2ffbc64d768d7404/2017-06-16_16_43_14-VTEX_-_Log__stica.png)
 
 Para cada tienda registrada deberá existir una dársena correspondiente.
diff --git a/docs/tutorials/es/sharing-your-store-access-to-google-webmaster-tools.md b/docs/tutorials/es/sharing-your-store-access-to-google-webmaster-tools.md
index 22f7f83a2..4a480782c 100644
--- a/docs/tutorials/es/sharing-your-store-access-to-google-webmaster-tools.md
+++ b/docs/tutorials/es/sharing-your-store-access-to-google-webmaster-tools.md
@@ -19,18 +19,18 @@ Para posibilitar un trabajo más eficiente de nuestro equipo de consultoría y o
 
 Luego de acceder a su cuenta, usted será direccionado a la lista de sus sites, y así basta seleccionar el site cuyo acceso desea compartir haciendo clic sobre el link de su site,
 
-![web1](//images.contentful.com/alneenqid6w5/3sjO5gPjcA2uCms8KskmU4/484df9e2d251c709169c88a626e2b575/web1.png)
+![web1](https://images.contentful.com/alneenqid6w5/3sjO5gPjcA2uCms8KskmU4/484df9e2d251c709169c88a626e2b575/web1.png)
 
 Así, ahora accedemos al panel administrativo de nuestra página. Diversas opciones son posibles en el menú lateral izquierdo, pero para compartir al acceso, debemos seleccionar el engranaje en el menú superior y hacer clic en **Usuarios y proprietarios de sitio**.
 
-![web2](//images.contentful.com/alneenqid6w5/kk9u4aygFyAG4EkKsYIw0/67bd8a6966fafea49f6c50f81d36c49d/web2.png)
+![web2](https://images.contentful.com/alneenqid6w5/kk9u4aygFyAG4EkKsYIw0/67bd8a6966fafea49f6c50f81d36c49d/web2.png)
 
 Se exhibirá ahora la lista de los usuarios ya autorizados a este site, por lo tanto, para adicionar un nuevo usuario basta hacer clic en la parte superior de la pantalla, sobre el botón **Añadir Nuevo Usuario**.
 
-![web3](//images.contentful.com/alneenqid6w5/1MLOKUoQliKsMc88EQUcmK/3e7dc118b07c2f23282ba48e63c1aee0/web3.png)
+![web3](https://images.contentful.com/alneenqid6w5/1MLOKUoQliKsMc88EQUcmK/3e7dc118b07c2f23282ba48e63c1aee0/web3.png)
 
 Tras el clic, se abre un pop-up solicitando como información o email del usuario a ser adicionado y el tipo de permiso, Total o restricto, que recibirá este usuario.
 
-![web4](//images.contentful.com/alneenqid6w5/hINzOyisNy0GyaMSOMEMq/b629abc8ff70a3820ab37f8a57f974e2/web4.png)
+![web4](https://images.contentful.com/alneenqid6w5/hINzOyisNy0GyaMSOMEMq/b629abc8ff70a3820ab37f8a57f974e2/web4.png)
 
 No se olvide de hacer clic en **Añadir** para guardar.
diff --git a/docs/tutorials/es/shipping-options-beta.md b/docs/tutorials/es/shipping-options-beta.md
index 27ce05e5a..eb1934972 100644
--- a/docs/tutorials/es/shipping-options-beta.md
+++ b/docs/tutorials/es/shipping-options-beta.md
@@ -93,7 +93,7 @@ Para agregar una opción de envío, sigue los pasos a continuación:
     - **Envío gratis:** libre de costo para el consumidor y no requiere configuración adicional.
 8. Haz clic en el botón `Guardar`.
 
-![opcoes_envio_criacao_es](//images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/0ef83d6a102d79c74a7d87c42c53c5eb/opcoes_envio_criacao_es.png)
+![opcoes_envio_criacao_es](https://images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/0ef83d6a102d79c74a7d87c42c53c5eb/opcoes_envio_criacao_es.png)
 
 ## Editar opción de envío
 
@@ -117,7 +117,7 @@ Además de editar una opción de envío, desde el ícono de menú <i class="fas
 
 Después de configurar las opciones de envío, aparecerán en una lista en **Configuración de la tienda > Envío > Opciones de envío**, según se muestra en la siguiente imagen:
 
-![opcoes_envio_listagem_es](//images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/eda44ef73871de786a4c6fc8d106923a/opcoes_envio_listagem_es.png)
+![opcoes_envio_listagem_es](https://images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/eda44ef73871de786a4c6fc8d106923a/opcoes_envio_listagem_es.png)
 
 La tabla siguiente contiene la descripción de las columnas mostradas:
 
diff --git a/docs/tutorials/es/shipping-policy.md b/docs/tutorials/es/shipping-policy.md
index d1a87ccad..c3a42b80f 100644
--- a/docs/tutorials/es/shipping-policy.md
+++ b/docs/tutorials/es/shipping-policy.md
@@ -23,7 +23,7 @@ La [estrategia de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio-
 
 La siguiente imagen muestra cómo se relacionan estos conceptos entre sí:
 
-![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
+![shipping_strategy_ES](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
 
 La **política de envío** es un conjunto de reglas y ajustes que definen las opciones de envío que se mostrarán a los clientes en el checkout. Al [calcular el tiempo de envío](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) del pedido, la plataforma VTEX toma en consideración los ajustes establecidos en las políticas de envío, entre los que destacan:
 
diff --git a/docs/tutorials/es/shipping-rate-template.md b/docs/tutorials/es/shipping-rate-template.md
index 442081d51..b18688507 100644
--- a/docs/tutorials/es/shipping-rate-template.md
+++ b/docs/tutorials/es/shipping-rate-template.md
@@ -181,7 +181,7 @@ Para facilitar el uso de los términos en nuestra documentación utilizamos «pe
 
 Vea el siguiente ejemplo de cómo rellenar los campos, teniendo en cuenta el formato aceptado en cada columna. 
 
-![modelo_planilhanumerica](//images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
+![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
 
 ## Enviar el archivo por el Admin VTEX
 
@@ -194,7 +194,7 @@ El envío de la plantilla se realiza en el registro o en la edición de la _Pol
 3. Después de descargar la plantilla modelo y [completar los campos](#completar-los-campos-de-la-plantilla), cargue el archivo en la sección Cargar tarifas de envío, como se ilustra en la siguiente imagen. 
 4. Al finalizar, haga clic en `Guardar cambios`.
 
-  ![upload tarifas envioES](//images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/b788e6926bffa8aa5a70db06ca1ccba7/upload_tarifas_envioES.png)
+  ![upload tarifas envioES](https://images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/b788e6926bffa8aa5a70db06ca1ccba7/upload_tarifas_envioES.png)
 
 <div class="alert alert-warning">
 Para registrar una <b>nueva</b> Política de envío se debe completar otros campos además de la plantilla de flete.  Aprenda cómo crear, editar y completar todos los campos necesarios en el artículo <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">Política de envío</a>.
diff --git a/docs/tutorials/es/shipping-rates.md b/docs/tutorials/es/shipping-rates.md
index f319c1ddb..ea8346772 100644
--- a/docs/tutorials/es/shipping-rates.md
+++ b/docs/tutorials/es/shipping-rates.md
@@ -22,7 +22,7 @@ Las tarifas de envío son los costos de envío que su tienda ofrece a los client
 El <a href="https://help.vtex.com/es/tutorial/costo-final-del-envio--5bwhIO108VA5Y2YOpef9lV">costo final del envío</a> para el cliente incluye la tarifa de envío, los <a href="https://help.vtex.com/es/tutorial/adicionales-de-flete--2vqGwMn0LabkOHY6zSHYNV">adicionales de flete</a> y el costo del muelle con stock.
 </div>
 
-![Tarifa envio ES](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
+![Tarifa envio ES](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
 
 En el Admin VTEX, hay dos maneras de registrar las tarifas de envío:
 
diff --git a/docs/tutorials/es/shipping-strategy.md b/docs/tutorials/es/shipping-strategy.md
index 92fbfa1f0..7291d7d1c 100644
--- a/docs/tutorials/es/shipping-strategy.md
+++ b/docs/tutorials/es/shipping-strategy.md
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Estrategia de envío es la relación entre stock, muelle y política de envío; es decir, la forma en que se comunican el stock, el muelle y la política de envío definirá la coordinación de la estructura de entrega de los pedidos de la tienda. 
 
-![shipping_strategy_ES](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
+![shipping_strategy_ES](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/ebc72f36e25bc9e6000d7d0b275bd1be/shipping_strategy_ES.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
    <tr class="bb b--muted-3">
diff --git a/docs/tutorials/es/site-editor-overview.md b/docs/tutorials/es/site-editor-overview.md
index d5791d237..c3b863489 100644
--- a/docs/tutorials/es/site-editor-overview.md
+++ b/docs/tutorials/es/site-editor-overview.md
@@ -23,7 +23,7 @@ El Site Editor es una interfaz gráfica para la gestión de contenidos de tu sto
 
 En el Admin VTEX, accede **Storefront > Site Editor** y verifica las principales herramientas disponibles en la interfaz gráfica.
 
-![Site Editor - ES](//images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/2c015dae64ff236deade75f75990f9bc/site-editor-ui-es.png)
+![Site Editor - ES](https://images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/2c015dae64ff236deade75f75990f9bc/site-editor-ui-es.png)
 
 | **Herramienta**    | **Descripción** |
 | ----------        | ----------    |
diff --git a/docs/tutorials/es/sku-bindings.md b/docs/tutorials/es/sku-bindings.md
index c59791aed..506b5fa73 100644
--- a/docs/tutorials/es/sku-bindings.md
+++ b/docs/tutorials/es/sku-bindings.md
@@ -27,7 +27,7 @@ Por defecto, para los <a href="https://help.vtex.com/es/tutorial/seller-white-la
 
 La página **Vínculos de SKU** le permite al _marketplace_ seguir y gestionar la vinculación entre los SKU del _seller_ y los del _marketplace_. Para acceder a la página, en el Admin VTEX, ingresa a **Marketplace > Sellers > Vínculos de SKU**. Aparecerá la siguiente interfaz:
 
-![sku-bindings-es](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/fcca860e97e41d512f9f88d53d6d09fd/sku-bindings-es.png)
+![sku-bindings-es](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/fcca860e97e41d512f9f88d53d6d09fd/sku-bindings-es.png)
 
 La tabla a continuación contiene la descripción de las columnas de la lista de vínculos de SKU:
 
diff --git a/docs/tutorials/es/special-conditions.md b/docs/tutorials/es/special-conditions.md
index 341b05b32..1b260f437 100644
--- a/docs/tutorials/es/special-conditions.md
+++ b/docs/tutorials/es/special-conditions.md
@@ -19,7 +19,7 @@ Las condiciones especiales forman parte de la configuración de las condiciones
 
 Para identificar las condiciones especiales aplicables a cada método de pago, en VTEX Admin, acceda a __Pago > Configuraçión > Condiciones de Pago__, seleccione el método de pago deseado y verifique las opciones como se muestra en la siguiente ilustración.
 
-![condiciones especiales de pago](//images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/1f9aaa7975a61f40c575db834c163a6b/Condiciones_especiales_de_pago.png)
+![condiciones especiales de pago](https://images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/1f9aaa7975a61f40c575db834c163a6b/Condiciones_especiales_de_pago.png)
 
 ## Condición Comercial
 
@@ -29,7 +29,7 @@ Para saber cómo catastrar una nueva condición comercial y asociarla a un SKU,
 
 ## Cómo configurar la condición comercial en la condición de pago
 
-![condicao-comercial es](//images.ctfassets.net/alneenqid6w5/4Cgc0FUB6oumYi88MOgsYY/359a21a1aa8610eded88339b0ea45f62/condicion-comercial.png)
+![condicao-comercial es](https://images.ctfassets.net/alneenqid6w5/4Cgc0FUB6oumYi88MOgsYY/359a21a1aa8610eded88339b0ea45f62/condicion-comercial.png)
 
 1. Dentro de la condición de pago, haga clic en `Añadir condición especial`.
 3. A continuación, haga clic en `Condición Comercial`.
@@ -89,7 +89,7 @@ Permite poner a disposición una condición de pago para una política comercial
 
 Cómo configurar la política comercial en la condición de pago
 
-![politica-comercial es](//images.ctfassets.net/alneenqid6w5/kfa8VsYOR26c2kkuumcCY/5a94b3b98926e993bd9914eb39deb0d6/venta-politica.png)
+![politica-comercial es](https://images.ctfassets.net/alneenqid6w5/kfa8VsYOR26c2kkuumcCY/5a94b3b98926e993bd9914eb39deb0d6/venta-politica.png)
 
 1. Dentro de la condición de pago, haga clic en `Añadir condición especial`.
 2. A continuación, haga clic en `Política Comercial (Canal de Ventas)`.
@@ -114,7 +114,7 @@ Cómo configurar el banco emisor en la condición de pago:
 6. Si desea segmentar por co-brand, seleccione la opción deseada en Co-brand (esta casilla de selección solo aparecerá si su tienda ha informado a VTEX la lista de tarjetas con co-brand).
 7. Guarde los cambios.
 
-![banco-emissor es](//images.ctfassets.net/alneenqid6w5/2mgaZy8JoY0O06UIGAsAoy/4000a63524a0ce2e2f86bdb3b0902511/banco-emisor.png)
+![banco-emissor es](https://images.ctfassets.net/alneenqid6w5/2mgaZy8JoY0O06UIGAsAoy/4000a63524a0ce2e2f86bdb3b0902511/banco-emisor.png)
 
 ### Ejemplos
 
@@ -146,7 +146,7 @@ Permite configurar una validez en la condición de pago, para que deje de ser ap
 
 Cómo configurar el período en la condición de pago
 
-![periodo es](//images.ctfassets.net/alneenqid6w5/6NORGuNOZUegEc0sm6YOQC/788aedda7526d5b7395aa504a15a5b48/periodo-es.png)
+![periodo es](https://images.ctfassets.net/alneenqid6w5/6NORGuNOZUegEc0sm6YOQC/788aedda7526d5b7395aa504a15a5b48/periodo-es.png)
 
 1. Dentro de la condición de pago, haga clic en `Añadir condición especial`.
 3. A continuación, haga clic en `Período`.
diff --git a/docs/tutorials/es/split-payment.md b/docs/tutorials/es/split-payment.md
index b37ac31bc..526206c17 100644
--- a/docs/tutorials/es/split-payment.md
+++ b/docs/tutorials/es/split-payment.md
@@ -55,11 +55,11 @@ Por ejemplo, un comprador agrega dos productos al mismo carrito de compras. El m
 
 El pago se distribuye de la siguiente manera.
 
-![Split de cobros](//images.ctfassets.net/alneenqid6w5/Vz2aNof4GnIVftr4EYDQy/a0545942f5605403edc0dba83a170963/Split_de_cobros.png)
+![Split de cobros](https://images.ctfassets.net/alneenqid6w5/Vz2aNof4GnIVftr4EYDQy/a0545942f5605403edc0dba83a170963/Split_de_cobros.png)
 
 Como puede ver, nuestro gateway calcula y distribuye los cobros de cada parte cuando se factura el pedido y se envía la información al proveedor de pagos. La distribución se realiza según la cantidad destinada a cada comerciante en el pedido y la comisión del marketplace.
 
-![Afiliaciones](//images.ctfassets.net/alneenqid6w5/4BE5K8TxKtGxDGgs1UwPHk/1b919ccf365965f061df91798e0ed869/Afiliaciones.png)
+![Afiliaciones](https://images.ctfassets.net/alneenqid6w5/4BE5K8TxKtGxDGgs1UwPHk/1b919ccf365965f061df91798e0ed869/Afiliaciones.png)
 
 Nuestra solución de split de cobros tiene algunas limitaciones que se deben tener en cuenta:
 
@@ -87,11 +87,11 @@ Lo que significa que el marketplace tiene menos control sobre el flujo de pago.
 
 Por ejemplo, un comprador agrega dos productos al mismo carrito de compras. El marketplace entregará uno de ellos y el otro le pertenece al seller llamado Seller A.
 
-![Transacción](//images.ctfassets.net/alneenqid6w5/2uC4hZkbbq4w5WuxZS5LaP/33d5406e2d18da8290edaa3621edc7c6/Transacci__n.png)
+![Transacción](https://images.ctfassets.net/alneenqid6w5/2uC4hZkbbq4w5WuxZS5LaP/33d5406e2d18da8290edaa3621edc7c6/Transacci__n.png)
 
 En el split de transacción, el marketplace no tiene que realizar ninguna configuración. El seller es el que tiene que configurar su medio de pago en la afiliación con un determinado marketplace. Para más detalles, consulte nuestra documentación [Enviar los medios de pago del Seller White Label al Marketplace](https://help.vtex.com/es/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW).
 
-![Afiliación1](//images.ctfassets.net/alneenqid6w5/4e8047JCOgEoswkj280gI5/421b393c522456e882ceaed27f73cb8c/Afiliados2.png)
+![Afiliación1](https://images.ctfassets.net/alneenqid6w5/4e8047JCOgEoswkj280gI5/421b393c522456e882ceaed27f73cb8c/Afiliados2.png)
 
 El split de transacción tiene algunas limitaciones que deben tomarse en cuenta.
 
diff --git a/docs/tutorials/es/store-access-permission.md b/docs/tutorials/es/store-access-permission.md
index 24e42dbdb..72b1ae852 100644
--- a/docs/tutorials/es/store-access-permission.md
+++ b/docs/tutorials/es/store-access-permission.md
@@ -25,4 +25,4 @@ Para realizar esta configuración, en el panel administrativo (Admin) de la cuen
 4. Seleccione la opción __VTEX Store__.
 5. Marque la casilla de selección __“Enables B2B behaviour”__ y guarde las alteraciones.
 
-![Habilitar escenario B2B](//images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
+![Habilitar escenario B2B](https://images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
diff --git a/docs/tutorials/es/store-overview-beta.md b/docs/tutorials/es/store-overview-beta.md
index 6c728cfa2..0b15015d1 100644
--- a/docs/tutorials/es/store-overview-beta.md
+++ b/docs/tutorials/es/store-overview-beta.md
@@ -23,7 +23,7 @@ La página Vista general (Beta) de tu Admin VTEX proporciona un seguimiento en t
 
 Esta herramienta está disponible en el Admin VTEX, en la página de inicio. Para acceder, haz clic en **Dashboards > Vista general** en el menú de navegación, o escribe _Vista general_ en la barra de búsqueda de la parte superior de la página.
 
-![ES Visão geral beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/5b97a2cf1346f1c95fc32512c95da972/ES_Visa__o_geral_beta.png)
+![ES Visão geral beta](https://images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/5b97a2cf1346f1c95fc32512c95da972/ES_Visa__o_geral_beta.png)
 
 En este artículo, presentamos las principales secciones y acciones presentes en la página. Aquí verás más información sobre:
 
@@ -78,7 +78,7 @@ Si deseas analizar los resultados de campañas, promociones o lanzamientos de nu
 3. Selecciona la [vista](#vista) `Acumulado`.
 4. Haz un seguimiento de las métricas hora a hora.
 
-![ES Visão geral beta acumulado](//images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/610b38ec888e48078998c5f51a9ade4e/ES_Visa__o_geral_beta_acumulado.png)
+![ES Visão geral beta acumulado](https://images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/610b38ec888e48078998c5f51a9ade4e/ES_Visa__o_geral_beta_acumulado.png)
 
 ### Monitorear impactos de cambios en la tienda
 
@@ -91,7 +91,7 @@ Si deseas ver el impacto de los cambios realizados en tu tienda, para identifica
 3. Evalúa el pulso en las métricas, o puntos de inflexión en el gráfico, que se han producido en las dos últimas horas. 
 4. Compara los horarios de los puntos de inflexión con los cambios generados para identificar su causa e impacto. 
 
-![ES Visão geral beta ultimas duas horas](//images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/e0cd80f9405e7736ee1c53ada5c8f97c/ES_Visa__o_geral_beta_ultimas_duas_horas.png)
+![ES Visão geral beta ultimas duas horas](https://images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/e0cd80f9405e7736ee1c53ada5c8f97c/ES_Visa__o_geral_beta_ultimas_duas_horas.png)
 
 ## Comparar periodos
 
@@ -134,7 +134,7 @@ La siguiente tabla describe los gráficos incluidos en la sección _Monitoreo_ d
 
 ## Métricas
 
-![ES Visão geral beta metricas](//images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/91ced2dd646ee9cdc9c1869f523ad1fd/ES_Visa__o_geral_beta_metricas.png)
+![ES Visão geral beta metricas](https://images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/91ced2dd646ee9cdc9c1869f523ad1fd/ES_Visa__o_geral_beta_metricas.png)
 
 La siguiente tabla describe las métricas disponibles en el panel de la página de inicio. Todas las métricas se refieren a flujos de compra realizados en tiendas VTEX en el periodo seleccionado.
 
diff --git a/docs/tutorials/es/store-overview.md b/docs/tutorials/es/store-overview.md
index 0f774b767..08c61069e 100644
--- a/docs/tutorials/es/store-overview.md
+++ b/docs/tutorials/es/store-overview.md
@@ -17,7 +17,7 @@ subcategory: 1TIJqw8kV2Yok4iQe4SAkq
 
 En la página de Vista general del Admin VTEX los propietarios de las tiendas pueden obtener una rápida visión general de las métricas clave que afectan a sus ingresos. A través de este panel, puedes seguir la evolución de tus ventas mediante el análisis de tendencia de pedidos, la tasa de conversión y los gráficos de embudo de ventas. Puedes acceder a esta herramienta en el Admin VTEX, haciendo clic en **Dashboards > Vista general** en el menú de navegación, o escribe *Vista general* en la barra de búsqueda en la parte superior de la página.
 
-![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 La página Vista General proporciona un resumen de su negocio con VTEX. Para un análisis más profundo de las métricas de su tienda, visite [Desenpeño de ventas](https://help.vtex.com/es/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp).
 
@@ -54,7 +54,7 @@ Para comparar datos de diferentes periodos, en la parte superior de la página s
 | Últimos 28 días | 00:00 del 29º día anterior al día actual    | 23:59 del día anterior al día actual                                                                                         |
 
 ## Métricas
-![Store overview Métricas ES](//images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/fa0a742830add36b15347a667b46a740/Me__tricas_ES.png)
+![Store overview Métricas ES](https://images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/fa0a742830add36b15347a667b46a740/Me__tricas_ES.png)
 La siguiente tabla describe las métricas clave disponibles en el panel de la página de inicio. Todas las métricas se refieren a los flujos de compra realizados en tiendas VTEX en un periodo de tiempo determinado.
 
 | Métrica                          | Descripción                                                                                                                                                                                                                                                                             |
@@ -69,7 +69,7 @@ La siguiente tabla describe las métricas clave disponibles en el panel de la p
 
 ## Productos con mayores ingresos / Productos con más unidades vendidas
 
-![Store overview Growing products ES](//images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/71288c48523af26b98d46501a1822105/Store_overview_Growing_products_ES.jpg)
+![Store overview Growing products ES](https://images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/71288c48523af26b98d46501a1822105/Store_overview_Growing_products_ES.jpg)
 
 Este componente muestra tus productos más rentables y los productos con mayor número de unidades vendidas en el periodo seleccionado. 
 
@@ -79,18 +79,18 @@ Puedes alternar entre estas dos opciones haciendo clic en el título o en el íc
 - **Productos con más unidades vendidas:** los productos con más unidades vendidas en el periodo seleccionado. Indica la cantidad de ítems vendidos y un porcentaje que muestra el aumento o la disminución de los ítems vendidos, comparando los periodos seleccionados.
 
 ## Pedidos realizados
-![Store overview Pedidos realizados EN](//images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/fab0eca29780027e7eef5a53ccdc803b/Pedidos_realizados_EN.png)
+![Store overview Pedidos realizados EN](https://images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/fab0eca29780027e7eef5a53ccdc803b/Pedidos_realizados_EN.png)
 
 Este gráfico muestra el número de pedidos que recibió la tienda en el periodo seleccionado. La línea azul más gruesa indica los pedidos que se realizaron en el periodo más reciente. La línea gris más delgada indica los pedidos que se realizaron en el periodo que estás comparando. Al pasar el *mouse* sobre las líneas, el gráfico muestra el número de pedidos captados en cada fecha.
 
 ## Pedidos cancelados
-![Store overview Pedidos cancelados PT](//images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/5a3f4d78000475bae4d2a62ec1c7c4bd/Pedidos_cancelados_PT.png)
+![Store overview Pedidos cancelados PT](https://images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/5a3f4d78000475bae4d2a62ec1c7c4bd/Pedidos_cancelados_PT.png)
 
 Este gráfico muestra el número de pedidos cancelados en la tienda en el periodo seleccionado. La línea azul más gruesa indica los pedidos cancelados en el periodo más reciente. La línea gris más delgada indica los pedidos cancelados en el periodo que estás comparando. Al pasar el *mouse* sobre las líneas, el gráfico muestra el número de pedidos cancelados en cada fecha.
 
 ## Análisis de tendencia de pedidos
 
-![Store overview Order trend ES](//images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/0eafd1eeb6423749827c8cfec524858a/Store_overview_Order_trend_ES.jpg)
+![Store overview Order trend ES](https://images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/0eafd1eeb6423749827c8cfec524858a/Store_overview_Order_trend_ES.jpg)
 
 Este gráfico muestra la tendencia de pedidos de tu tienda, indicando el número de pedidos realizados por los compradores en el periodo seleccionado.
 
@@ -100,13 +100,13 @@ El número que aparece en la parte superior del gráfico se refiere a los pedido
 
 ## Tasa de conversión
 
-![Store overview Conversion rate ES](//images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/92756d2a2a7f4165f4312f2c81bc08e6/Store_overview_Conversion_rate_ES.jpg)
+![Store overview Conversion rate ES](https://images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/92756d2a2a7f4165f4312f2c81bc08e6/Store_overview_Conversion_rate_ES.jpg)
 
 Este gráfico muestra la tasa de conversión de tu tienda en los períodos seleccionados que quieres comparar. La tasa de conversión se calcula dividiendo el número total de pedidos por el número total de sesiones en tu tienda. La línea azul más gruesa indica la tasa de conversión para el periodo más reciente. La línea gris más delgada indica la tasa para el periodo que estás comparando. Al pasar el mouse por encima del gráfico, se visualiza la tasa de conversión para cada periodo comparado. El gráfico también indica el porcentaje (%) y los puntos porcentuales (p.p) de aumento o reducción de esta métrica. Al pasar el mouse por encima del gráfico, puedes ver el valor de esa métrica en momentos específicos. 
 
 ## Embudo de ventas
 
-![Store overview sales funnel ES](//images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/d767479ae6fd2f51af5327b80527d883/Store_overview_sales_funnel_ES.jpg)
+![Store overview sales funnel ES](https://images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/d767479ae6fd2f51af5327b80527d883/Store_overview_sales_funnel_ES.jpg)
 
 Este gráfico permite seguir el volumen de sesiones en las etapas intermedias del flujo de compra y ver oportunidades para optimizar la tasa de conversión de la tienda. La siguiente tabla describe las etapas intermedias del flujo de compra.
 
@@ -122,7 +122,7 @@ Este gráfico permite seguir el volumen de sesiones en las etapas intermedias de
 Cada barra azul del gráfico representa el volumen de sesiones que han alcanzado una determinada etapa del flujo de compra. Este volumen se representa como valor absoluto (arriba), y como porcentaje del número de sesiones (abajo), junto con los puntos porcentuales (p.p) de aumento o reducción en el embudo de ventas. Al pasar el mouse por encima del porcentaje, puedes ver más detalles sobre esa etapa intermedia.
 
 ## Categorías con mayores ingresos
-![Categorias PT](//images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/7cf1e540189c28ec0d3286179d0d2774/Categorias_PT.png)
+![Categorias PT](https://images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/7cf1e540189c28ec0d3286179d0d2774/Categorias_PT.png)
 
 Este gráfico muestra las diez categorías de tu tienda que más ingresos generaron en el periodo seleccionado. La barra azul indica los ingresos generados en la fecha más reciente y la barra gris indica los ingresos generados en el periodo comparado. Al pasar el mouse sobre el gráfico, se visualiza la tasa de conversión para cada periodo comparado. Al hacer clic en el título del gráfico, es posible cambiar la vista a las __Categorías más vendidas por pedido__.
 
diff --git a/docs/tutorials/es/storefront-overview.md b/docs/tutorials/es/storefront-overview.md
index 31484c573..00ab12cdc 100644
--- a/docs/tutorials/es/storefront-overview.md
+++ b/docs/tutorials/es/storefront-overview.md
@@ -21,7 +21,7 @@ El _storefront_ también incluye VTEX Intelligent Search, una herramienta que ay
 
 Estas operaciones se realizan en el menú _Storefront_ de tu Admin VTEX. 
 
-![Storefront overview menu ES](//images.ctfassets.net/alneenqid6w5/2vIJXsLuEsAOqgOxb9umYZ/b950fe38232e7fdb3603c1c344830d8a/Storefront_overview_menu_ES.jpg)
+![Storefront overview menu ES](https://images.ctfassets.net/alneenqid6w5/2vIJXsLuEsAOqgOxb9umYZ/b950fe38232e7fdb3603c1c344830d8a/Storefront_overview_menu_ES.jpg)
 
 A continuación, encontrarás más detalles sobre las diferentes secciones y páginas de este menú.
 
diff --git a/docs/tutorials/es/structured-data-through-google-search-console-data-markers.md b/docs/tutorials/es/structured-data-through-google-search-console-data-markers.md
index 1dc12d492..654a9be75 100644
--- a/docs/tutorials/es/structured-data-through-google-search-console-data-markers.md
+++ b/docs/tutorials/es/structured-data-through-google-search-console-data-markers.md
@@ -65,13 +65,13 @@ Con ese tipo de información, el usuario indicará a Google información sobre l
 - <en style="color: gray">Fecha de la re-contraseña:_
 
 **Paso 1**
-![](//images.contentful.com/alneenqid6w5/2auEIkvBGMO8gqWqgA4u8q/0c53485d350f622ae184852c88688f0c/marcadordedados_step1.gif)****
+![](https://images.contentful.com/alneenqid6w5/2auEIkvBGMO8gqWqgA4u8q/0c53485d350f622ae184852c88688f0c/marcadordedados_step1.gif)****
 
 **Paso 2**
-![](//images.contentful.com/alneenqid6w5/62T28aRiUM0cOwOmiOQ2UA/8584923dd2b3c1f9f9bc7a782caee223/marcadordedados_step2_url_type.gif)
+![](https://images.contentful.com/alneenqid6w5/62T28aRiUM0cOwOmiOQ2UA/8584923dd2b3c1f9f9bc7a782caee223/marcadordedados_step2_url_type.gif)
 
 **Paso 3**
-![](//images.contentful.com/alneenqid6w5/5YhbETD9mMMgsAeKGE2SMG/622bccd0df4e05462f7db9ae7bb05cf9/marcadordedados_step3_markup_business.gif)
+![](https://images.contentful.com/alneenqid6w5/5YhbETD9mMMgsAeKGE2SMG/622bccd0df4e05462f7db9ae7bb05cf9/marcadordedados_step3_markup_business.gif)
 
 ### Productos
 
@@ -90,10 +90,10 @@ Con este tipo de información el usuario indicará a Google información sobre l
 - <en style="color: gray">Fecha de la re-contraseña:_
 
 **Paso 1**
-![](//images.contentful.com/alneenqid6w5/5ARq4O3nna8gqGM8KasC4K/57999e6c592e985550758aaab1c15c06/marcadordedados_step2_url_type_product.gif)
+![](https://images.contentful.com/alneenqid6w5/5ARq4O3nna8gqGM8KasC4K/57999e6c592e985550758aaab1c15c06/marcadordedados_step2_url_type_product.gif)
 
 **Paso 2**
-![](//images.contentful.com/alneenqid6w5/1TNyUZzqLSOOO48gmCOQ26/d78f4f460a7d6caf864498db7f1ce2b2/marcadordedados_step3_markup_product.gif)
+![](https://images.contentful.com/alneenqid6w5/1TNyUZzqLSOOO48gmCOQ26/d78f4f460a7d6caf864498db7f1ce2b2/marcadordedados_step3_markup_product.gif)
 
 **Paso 3**
 Recordando que el **Marcador de Datos** sólo identifica los datos para Google, para las demás herramientas de búsqueda será necesario estructurar los datos a través de tags insertadas en el código fuente.
diff --git a/docs/tutorials/es/styles-overview.md b/docs/tutorials/es/styles-overview.md
index f644a77f4..bd61aa043 100644
--- a/docs/tutorials/es/styles-overview.md
+++ b/docs/tutorials/es/styles-overview.md
@@ -19,7 +19,7 @@ La página **Estilos** te permite definir la tipografía y la paleta de colores
 
 Para acceder a Estilos, inicia sesión en el Admin VTEX, accede a **Storefront > Estilos** y descubre las principales herramientas disponibles en la interfaz.
 
-![Estilos - Visión general](//images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/7b916baa31c3fe37cb946ac9afacd908/ES.png)
+![Estilos - Visión general](https://images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/7b916baa31c3fe37cb946ac9afacd908/ES.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Para aplicar y obtener una vista previa de los cambios en los estilos de tu tienda, asegúrate de utilizar un espacio de trabajo que soporte el tráfico de producción, por ejemplo, <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">espacios de trabajo de producción</a>. 
diff --git a/docs/tutorials/es/subscription-plans.md b/docs/tutorials/es/subscription-plans.md
index 7a53da8d3..20dda4ffd 100644
--- a/docs/tutorials/es/subscription-plans.md
+++ b/docs/tutorials/es/subscription-plans.md
@@ -21,7 +21,7 @@ Para que los planes de suscripción estén disponibles, primero debe instalar la
 
 En la página de **Planes**, puede ver y gestionar los planes de suscripción disponibles para los clientes de su tienda, según se ilustra a continuación.
 
-![planslist ES](//images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/d5e90eb8a6d31b3d0b66d01f0a9839e8/planslist_ES.png)
+![planslist ES](https://images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/d5e90eb8a6d31b3d0b66d01f0a9839e8/planslist_ES.png)
 
 Las principales funcionalidades de esta página son:
 
diff --git a/docs/tutorials/es/synonym-list.md b/docs/tutorials/es/synonym-list.md
index 02a4a20d6..301379b99 100644
--- a/docs/tutorials/es/synonym-list.md
+++ b/docs/tutorials/es/synonym-list.md
@@ -17,7 +17,7 @@ subcategory: BBzMtJan1UTxC9QZODnlN
 
 La página **Sinónimos** te permite ver y gestionar todos los [sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de Intelligent Search registrados en tu tienda. Accede a través del Admin VTEX, haciendo clic en **Storefront > Intelligent Search > Sinónimos**.
 
-![lista-sinonimos-es](//images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/7dcff1482a82ff95a77a3aa783157069/lista-sinonimos-es.PNG)
+![lista-sinonimos-es](https://images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/7dcff1482a82ff95a77a3aa783157069/lista-sinonimos-es.PNG)
 
 La página presenta la siguiente información en forma de tabla:
 
diff --git a/docs/tutorials/es/telesales-toolbar.md b/docs/tutorials/es/telesales-toolbar.md
index 3fcb04d3d..add71d64e 100644
--- a/docs/tutorials/es/telesales-toolbar.md
+++ b/docs/tutorials/es/telesales-toolbar.md
@@ -19,7 +19,7 @@ La barra de herramientas de televentas es una barra superior que se muestra en e
 
 La barra de herramientas aparece una vez que el operador registrado inicia sesión en el ambiente de la tienda y esta se muestra en todas las áreas del sitio web.
 
-![toolbartelevendas ES](//images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ac84e4fa98ca225195dae8890f04333b/toolbartelevendas_ES.png)
+![toolbartelevendas ES](https://images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/ac84e4fa98ca225195dae8890f04333b/toolbartelevendas_ES.png)
 
 Estos son los principales recursos de la barra de herramientas:
 *   [Entrar como cliente](#entrar-como-cliente)
diff --git a/docs/tutorials/es/testing-webservice-using-soapui.md b/docs/tutorials/es/testing-webservice-using-soapui.md
index 4bd520e63..13bb64f0c 100644
--- a/docs/tutorials/es/testing-webservice-using-soapui.md
+++ b/docs/tutorials/es/testing-webservice-using-soapui.md
@@ -33,11 +33,11 @@ El paso a paso de utilización es el siguiente:
 
 Sustitúa {AMBIENTEDELATIENDA} por el nombre de su tienda.
 
-![](//images.contentful.com/alneenqid6w5/WMZnCJCLg2WGSIesMOMKu/efed51a5c0e151d1ac1f7902600e522a/1.png)
+![](https://images.contentful.com/alneenqid6w5/WMZnCJCLg2WGSIesMOMKu/efed51a5c0e151d1ac1f7902600e522a/1.png)
 
 Efectúe el login con los datos de webservice deseado. Después de efectuar el login, se visualizarán todos los métodos existentes en el [manual de Webservice](/es/tutorial/manual-de-clases-y-metodos-utilizados-en-webservice/).
 
-![](//images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
+![](https://images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
 
 1. Localice el método deseado. Ej: el método ImageInsertUpdate, que es el método utilizado para agregar imágenes;
 2. Cargue los campos referentes al método (estos campos son de tipo ImageDTO. Las referencias están en el manual);
diff --git a/docs/tutorials/es/total-shipping-cost.md b/docs/tutorials/es/total-shipping-cost.md
index a169d6bea..61bc5e138 100644
--- a/docs/tutorials/es/total-shipping-cost.md
+++ b/docs/tutorials/es/total-shipping-cost.md
@@ -31,7 +31,7 @@ Vea cómo se calcula cada tarifa:
 
 Así que, en general, el costo final del envío puede calcularse así:
 
-![Custo-final-envio-ES](//images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/48b3d941065ab47cb55c7b4590b993bd/Custo-final-envio-ES.svg)
+![Custo-final-envio-ES](https://images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/48b3d941065ab47cb55c7b4590b993bd/Custo-final-envio-ES.svg)
 
 <div class="alert alert-danger">
 Si el <b>adicional de precio</b> es inferior al <b>adicional de seguro,</b> la tarifa considerada es el adicional de seguro. El adicional de precio no se tomará en cuenta en el cálculo de la tarifa final.<p>
diff --git a/docs/tutorials/es/transaction-flow-in-payments.md b/docs/tutorials/es/transaction-flow-in-payments.md
index d25cdb2b9..ad38e3b12 100644
--- a/docs/tutorials/es/transaction-flow-in-payments.md
+++ b/docs/tutorials/es/transaction-flow-in-payments.md
@@ -19,7 +19,7 @@ Las transacciones realizadas por el Pagos de VTEX pasan por diversos status, des
 
 Vea abajo un ejemplo de la línea de tiempo con los estados de la transacción.
 
-![Transaction Flow](//images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
+![Transaction Flow](https://images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
 
 1. __Authorizing__: Este es el primer status de una transacción en Pagos. En esta etapa, Pagos indica que se ha iniciado el proceso de envío de información a un adquirente o a otro gateway.
 2. __Authorized__: Después del inicio del proceso de autorización, el adquirente o otro gateway envía la información de la transacción al banco emisor. El banco responde si la transacción debe ser o no autorizada. Si se niega la transacción, el pago es __cancelado__. Si lo permite, el status de la transacción pasa a __Authorized__.
diff --git a/docs/tutorials/es/transactional-emails-for-subscription-orders.md b/docs/tutorials/es/transactional-emails-for-subscription-orders.md
index c45362578..0c3e9887c 100644
--- a/docs/tutorials/es/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/es/transactional-emails-for-subscription-orders.md
@@ -43,7 +43,7 @@ No es necesario activar el envío de correos electrónicos manualmente, pues se
 5. Desactive la casilla `¿Activar envío de e-mail?`, que por defecto está marcada como activa.
 6. Haga clic en **Guardar**.
 
-![PT Subscription Message Center](//images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
+![PT Subscription Message Center](https://images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
 
 ## Plantillas Estándar del Centro de Mensajes 
 
diff --git a/docs/tutorials/es/transactions-events.md b/docs/tutorials/es/transactions-events.md
index 664e515c8..911389e32 100644
--- a/docs/tutorials/es/transactions-events.md
+++ b/docs/tutorials/es/transactions-events.md
@@ -31,13 +31,13 @@ Más abajo se comparten ejemplos de donde encontrar las informaciones más comun
 
 En este evento vemos que VTEX comenzó el proceso de autorización con el gateway de pagos y este respondió que podemos comenzar la operación:
 
-![transaccion-autorizando](//images.contentful.com/alneenqid6w5/5t9nrVLHG0ImUq6KoG0kWS/cb760295e335e209642495a72f8a6c3a/transaccion-autorizando.png)
+![transaccion-autorizando](https://images.contentful.com/alneenqid6w5/5t9nrVLHG0ImUq6KoG0kWS/cb760295e335e209642495a72f8a6c3a/transaccion-autorizando.png)
 
 ## Transacción autorizada y aprobada
 
 Después de la solicitación de autorización, el gateway de pagos nos autorizará/preautorizará la transacción en caso de flujo exitoso. Con la autorización del gateway, la transacción será _aprobada_ para continuar con el flujo del pedido:
 
-![transaccion-autorizada-aprobada](//images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
+![transaccion-autorizada-aprobada](https://images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
 
 En caso que no ocurra la autorización por algún problema fuera del flujo, el log del será detallado en el timeline, según las informaciones devueltas por el gateway de pagos.
 
@@ -45,7 +45,7 @@ En caso que no ocurra la autorización por algún problema fuera del flujo, el l
 
 En el flujo del pedido, existe la posibilidad de enviar el pago a un antifraude (integrado directamente a VTEX) para aplicarle un análisis de riesgo. Luego de haber solicitado un análisis, el pedido contará con un estado que indique el inicio del análisis y la devolución del antifraude, junto con el resultado:
 
-![transaccion-antifraude](//images.contentful.com/alneenqid6w5/3MjNaFOEJyiumaUyO2owSa/84130c11335612c4d982c016cc160616/transaccion-antifraude.png)
+![transaccion-antifraude](https://images.contentful.com/alneenqid6w5/3MjNaFOEJyiumaUyO2owSa/84130c11335612c4d982c016cc160616/transaccion-antifraude.png)
 
 En caso que no ocurra el análisis por algún problema fuera del flujo, el log del será detallado en el timeline, según las informaciones devueltas por el gateway de pagos.
 
@@ -55,11 +55,11 @@ Cuando se utiliza la modalidad de Preautorización de las transacciones, luego d
 
 Cuando se inicie el proceso de captura, se verá el evento _Settlement_, que indica que la captura fue solicitada al gateway de pagos:
 
-![transaccion-captura-solicitud](//images.contentful.com/alneenqid6w5/4ZnegfgNcA4MQsgMuQaAsE/478d66d4b763730762637cc75a1aaea4/transaccion-captura-solicitud.png)
+![transaccion-captura-solicitud](https://images.contentful.com/alneenqid6w5/4ZnegfgNcA4MQsgMuQaAsE/478d66d4b763730762637cc75a1aaea4/transaccion-captura-solicitud.png)
 
 Mientras se haya iniciado con éxito la captura, se verá el evento _Settling_. Y al finalizar la captura, se indicará el evento _Settled_:
 
-![transaccion-captura-iniciada-capturada](//images.contentful.com/alneenqid6w5/2Z2fPSYG5WK0YqSCuWGAQi/42f03171a702ada307bd85b21614757f/transaccion-captura-iniciada-capturada.png)
+![transaccion-captura-iniciada-capturada](https://images.contentful.com/alneenqid6w5/2Z2fPSYG5WK0YqSCuWGAQi/42f03171a702ada307bd85b21614757f/transaccion-captura-iniciada-capturada.png)
 
 En caso que no ocurra la captura por algún problema fuera del flujo, el log del será detallado en el timeline, según las informaciones devueltas por el gateway de pagos.
 
@@ -67,7 +67,7 @@ En caso que no ocurra la captura por algún problema fuera del flujo, el log del
 
 Al finalizar la transacción, VTEX indicará como muestra la siguiente imagen:
 
-![transaccion-finalizada](//images.contentful.com/alneenqid6w5/68PjN2ChyMWqYQ4Owm8Yk6/0a440ea3cf6e5190b7b03e72d6a7e7e8/transaccion-finalizada.png)
+![transaccion-finalizada](https://images.contentful.com/alneenqid6w5/68PjN2ChyMWqYQ4Owm8Yk6/0a440ea3cf6e5190b7b03e72d6a7e7e8/transaccion-finalizada.png)
 
 ## Transacción programada para captura automática
 
@@ -75,5 +75,5 @@ Generalmente, las afiliaciones permiten configurar una fecha programada de captu
 
 Aquí se logra visualizar la fecha de la programación de la captura automática:
 
-![captura-auto-agendada es](//images.ctfassets.net/alneenqid6w5/6aACu6LopG4OUC6AWIAMuC/957305614367791a46fe152d021b3430/transa____o_programada_cap_auto_es.png)
+![captura-auto-agendada es](https://images.ctfassets.net/alneenqid6w5/6aACu6LopG4OUC6AWIAMuC/957305614367791a46fe152d021b3430/transa____o_programada_cap_auto_es.png)
 
diff --git a/docs/tutorials/es/transferring-store-ownership.md b/docs/tutorials/es/transferring-store-ownership.md
index 9700d1c84..1d91a7b0c 100644
--- a/docs/tutorials/es/transferring-store-ownership.md
+++ b/docs/tutorials/es/transferring-store-ownership.md
@@ -25,7 +25,7 @@ La página de «Gestión de titular» le permite identificar al usuario titular
 
 Debe ver una pantalla similar a la imagen a continuación que tiene la información del usuario titular actual, un descargo de responsabilidad que indica los riesgos asociados a la transferencia de la propiedad de la tienda y un botón para aceptar los riesgos y transferir la propiedad de todas maneras.
 
-![Panel de gestión de titular](//images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/8220a9866df4786fcff4fb3b5a29f6ca/Sponsor_Management_es.png)
+![Panel de gestión de titular](https://images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/8220a9866df4786fcff4fb3b5a29f6ca/Sponsor_Management_es.png)
 
 ## Pasos de la transferencia de propiedad
 
@@ -51,7 +51,7 @@ Esto completa la transferencia de propiedad y ya no se podrá cancelar la invita
 
 El usuario titular es responsable de importantes acciones de mantenimiento y autorización, y los errores cometidos por él pueden tener consecuencias graves. Por lo tanto, es esencial seguir los cambios relacionados con este rol de usuario. Para monitorizar y auditar las transferencias de propiedad de la cuenta, puede acceder al registro de actividades haciendo clic en el botón Registro de Actividades en la página Gestión de Titular.
 
-![Registro de Actividades](//images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/65400ca2fe5cf04983b4b774327de310/Activity_Log_es.gif)
+![Registro de Actividades](https://images.ctfassets.net/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/65400ca2fe5cf04983b4b774327de310/Activity_Log_es.gif)
 
 Todos los eventos relacionados con la transferencia de propiedad de la cuenta se registran en el registro de actividades con la fecha en que se produjeron y el usuario asociado al evento.
 
diff --git a/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
index cfe033d09..bb44dd4d4 100644
--- a/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
@@ -32,7 +32,7 @@ Los problemas en ciclos de suscripción se producen cuando hay un impedimento pa
 
 La pestaña **Ciclos con un problema**, que se ilustra en la siguiente imagen, recoge los pedidos de suscripción que tienen este tipo de problemas.
 
-![pedidos_assinaturas_print_es](//images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
+![pedidos_assinaturas_print_es](https://images.ctfassets.net/alneenqid6w5/1dhCAuymIdeS4JyaxC7ep2/018f9060f82320eada25f385328cbd3a/pedidos_assinaturas_print_es.png)
 
 Desde esta pestaña se puede gestionar los pedidos que presentan ciclos con un problema y realizar reintentos manuales de creación de pedidos. Por ejemplo, cuando un producto no está disponible, puede ajustar el stock y volver a intentarlo.
 
@@ -189,7 +189,7 @@ Los errores de pago se producen durante el flujo de aprobación del pago, como e
 
 Los pedidos con este tipo de error pueden visualizarse en la pestaña **Error de pago**, ilustrada en la siguiente imagen.
 
-![pedidos_assinaturas_print_erro_pagamento_es](//images.ctfassets.net/alneenqid6w5/2Cc9hhcSr6CjeU3tDIerqo/adfef0d0054bb88ef52d32d6ce7d81fd/pedidos_assinaturas_print_erro_pagamento_es.png)
+![pedidos_assinaturas_print_erro_pagamento_es](https://images.ctfassets.net/alneenqid6w5/2Cc9hhcSr6CjeU3tDIerqo/adfef0d0054bb88ef52d32d6ce7d81fd/pedidos_assinaturas_print_erro_pagamento_es.png)
 
 Para analizar errores de pago, realice el siguiente procedimiento.
 
diff --git a/docs/tutorials/es/understanding-b2b-orders.md b/docs/tutorials/es/understanding-b2b-orders.md
index 87f3a0a83..3f04e8b27 100644
--- a/docs/tutorials/es/understanding-b2b-orders.md
+++ b/docs/tutorials/es/understanding-b2b-orders.md
@@ -19,7 +19,7 @@ En una operación de comercio electrónico B2B, habitualmente se necesita inform
 
 La app **Pedidos B2B** simplifica este proceso y permite que cualquier colaborador de la empresa que realizó la compra  pueda consultar los pedidos realizados accediendo a la tienda virtual.
 
-![orders VTEX B2B](//images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
+![orders VTEX B2B](https://images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
 
 Esa experiencia de autoservicio es posible gracias a una integración vía API con el ERP. De esta forma, el colaborador puede buscar pedidos por: 
 
diff --git a/docs/tutorials/es/understanding-how-indexation-works.md b/docs/tutorials/es/understanding-how-indexation-works.md
index 29d308466..394450912 100644
--- a/docs/tutorials/es/understanding-how-indexation-works.md
+++ b/docs/tutorials/es/understanding-how-indexation-works.md
@@ -32,7 +32,7 @@ Cada vez que se modifican los datos del listado de productos como se muestra a c
 
 Una vez que el producto esté marcado para reindexar, éste queda con el texto _indexação pendente_ en el listado de productos del admin. El indexador toma esos productos y los coloca en una fila, con un tiempo de espera de 2 minutos, para que sean procesados. Pasados los 2 minutos el producto queda disponible para el consumo de la indexación. En ese proceso, todos los módulos de VTEX son consultados, actualizando precio y disponibilidad para cada política comercial. El tempo medio hasta finalizar este proceso es de 4 minutos.
 
-![diagramaespanhol](//images.ctfassets.net/alneenqid6w5/SR9YuOnYK2Ku0CW2K2iEO/26f0b18db9ec54d5055cc377d911c2b0/diagramaespanhol.png)
+![diagramaespanhol](https://images.ctfassets.net/alneenqid6w5/SR9YuOnYK2Ku0CW2K2iEO/26f0b18db9ec54d5055cc377d911c2b0/diagramaespanhol.png)
 
 ## Informe de Indexación
 
@@ -47,7 +47,7 @@ En él, se dividen los productos en cada paso del proceso de indexación y en pe
 - **Total Indexado**, **Aún no en la fila** y **Total en la fila**: : se refiere a las etapas del producto dentro del proceso &#8211; Ainda não enfileirado son los productos que se modificaron en menos de 2 minutos y Total na fila son aquellos que ya entraron en proceso de indexación, tras esos 2 minutos.
 - **En la fila recientemente**, **En la fila entre 1 y 2 hs**, **En la fila de 2 a 4 hs** y **En la fila de 4 a 8 hs**: son los períodos en que los productos están en el proceso de indexación.
 
-![productosindexados](//images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
+![productosindexados](https://images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
 
 En el informe de indexación, también existe el tiempo que el último ítem tardó para ser re indexado. Queda al lado derecho superior del informe, conforme a la imagen arriba.
 
diff --git a/docs/tutorials/es/understanding-how-the-cache-works.md b/docs/tutorials/es/understanding-how-the-cache-works.md
index 7d59ffded..2230a4930 100644
--- a/docs/tutorials/es/understanding-how-the-cache-works.md
+++ b/docs/tutorials/es/understanding-how-the-cache-works.md
@@ -19,11 +19,11 @@ El concepto de cache es bastante difundido como siendo un dispositivo de acceso
 
 Cuando una página o archivo inicia su carga, a través de la URL, el browser realiza una solicitud para el servidor que, por su parte, tiene la función de responder con información relevante para aquella solicitud. La solicitud del browser se conoce como **request** y la respuesta del servidor como **response**. Esos términos serán bastante utilizados en el transcurso de este artículo. Vea el esquema abajo:
 
-![Como o cache funciona - comunicação entre servidor e navegador](//images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/1d05717d54faede0fc00d75716d7def4/1_ES.png)
+![Como o cache funciona - comunicação entre servidor e navegador](https://images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/1d05717d54faede0fc00d75716d7def4/1_ES.png)
 
 El cache está representado a través de una capa entre el browser y el servidor y, así, cuando un **request** ocurre, en vez del sistema ir a buscar la información directamente en el servidor, primero va a esa capa, lo que vuelve mucho más ágil a la respuesta. Vea el esquema abajo:
 
-![Cómo funciona el caché: comunicación con el caché (sin caducar)](//images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/3d375c19c114eecdbe75decac28e2df3/2_PT.png)
+![Cómo funciona el caché: comunicación con el caché (sin caducar)](https://images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/3d375c19c114eecdbe75decac28e2df3/2_PT.png)
 
 Sin embargo, como el dato actualizado está en el servidor, de tiempo en tiempo es necesario actualizar el cache. Ese tiempo varía de acuerdo al tipo de **request, **o sea, si el **request** es una página, el tiempo es uno, si es un archivo javascript o CSS, es otro y aún, si es una imagen, será otro.
 
@@ -50,7 +50,7 @@ Como ya se ha dicho, tempo de duração del cache varía para cada tipo de **req
 
 Cuando el cache de un **request** (página o archivo) expira, al realizar una nueva solicitud, o sea, al cargar nuevamente la URL, el sistema va al servidor, rescata la información actualizada para aquella solicitud y actualiza el contenido de aquella URL en el cache. Después de actualizada, la versión cacheada vuelve a ser retornada para nuevas solicitudes de URL. Vea el esquema ilustrando ese caso:
 
-![Cómo funciona la caché: comunicación con la caché (caducada)](//images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/36d452de8975e10cbb847787bddaf1e1/3_ES.png)
+![Cómo funciona la caché: comunicación con la caché (caducada)](https://images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/36d452de8975e10cbb847787bddaf1e1/3_ES.png)
 
 En ese aspecto, podemos separar las respuestas en dos grupos: Cacheadas y no cacheadas.
 
@@ -63,7 +63,7 @@ Si el valor está rellenado con “HIT”, significa que el contenido exhibido e
 
 Otra información relevante que puede ser identificada en los headers de los **requests** es la fecha en la que el cache fue creado. Esa información está disponible en la propiedad `X-vtex-processed-at`.
 
-![](//images.contentful.com/alneenqid6w5/5GPSsb4UWA28QS4soyguSI/8772946997cc979ddf9c2297f2ca8bb6/cache.png)
+![](https://images.contentful.com/alneenqid6w5/5GPSsb4UWA28QS4soyguSI/8772946997cc979ddf9c2297f2ca8bb6/cache.png)
 
 Pese a que archivos javascript y CSS también tienen la duración de cache establecida, como este tipo de archivos se usa en la dormitación de los layouts y, por eso, en algunos casos, necesitan una actualización más ágil, el portal posee una inteligencia que identifica modificaciones en sus contenidos, rompiendo con la capa de cache. 
 
diff --git a/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md b/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md
index a5723ce3d..32a220f4c 100644
--- a/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md
+++ b/docs/tutorials/es/understanding-storebuilder-and-stylesbuilder.md
@@ -15,7 +15,7 @@ legacySlug: conociendo-el-storebuilder-y-el-stylesbuilder
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-![UI Blocks Voando.mp4](//images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
+![UI Blocks Voando.mp4](https://images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
 
 Esta documentación se ha estructurado para explicar los conceptos detrás del StoreBuilder y StyleBuilder de la Store 2.xx. Durante toda la documentación, utilizaremos la DreamStore (una tienda template que utiliza la `Store 2.xx`) para entender los principales conceptos que le permitirán estructurar y estilizar su tienda.
 
@@ -39,7 +39,7 @@ La Store 2 hace grandes cambios de paradigma en la Store 1, introduciendo el con
 
 Vamos a mirar dentro del `/manifest.json` de DreamStore para ver lo que nuestra aplicación necesita para funcionar correctamente:
 
-![Screen Shot 2019-01-25 at 16.40.06](//images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
+![Screen Shot 2019-01-25 at 16.40.06](https://images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
 
 Observe cómo tenemos dos builders especificados:
 
@@ -59,7 +59,7 @@ Como cualquier theme app (una tienda) hace uso de la aplicación `Store` (a trav
 
 Ejecute "vtex link" y envie la app DreamStore a un workspace para que podamos estudiarla.
 
-![Screen Shot 2019-01-27 at 22.24.47](//images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
+![Screen Shot 2019-01-27 at 22.24.47](https://images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
 
 Si está familiarizado con React o otros frameworks modernos de Javascript, usted estará familiarizado con el concepto de componentes en una página web. Como podemos observar, nuestra página web tiene un "header", un "carrusel" y un "estante". ¿Cómo se insertaron estos componentes?
 
@@ -97,7 +97,7 @@ _Tenga en cuenta que usted no estará desarrollando en la aplicación Store 2, p
 
 Vamos a mirar dentro del archivo `/manifest.json` de la Store2.xx para ver lo que importa la aplicación.
 
-![Screen Shot 2019-01-25 at 17.18.56](//images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
+![Screen Shot 2019-01-25 at 17.18.56](https://images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
 
 Podemos ver que es una estructura similar a la del `manifest.json` de la `Dreamstore`.
 
@@ -142,7 +142,7 @@ __Como cada página es definida por bloques y organizada por interfaces__, es ho
 Abra la carpeta `store` y después el archivo `interfaces.json`.
 
 ### Interfaces
-![Screen Shot 2019-01-25 at 17.35.10](//images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
+![Screen Shot 2019-01-25 at 17.35.10](https://images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
 
 Una interfaz es un conjunto de `blocks` y existe exclusivamente dentro de la `Store2.xx`. Sirve como un contrato entre los bloques y determina cómo van a trabajar juntos.
 
@@ -199,7 +199,7 @@ Vamos a seguir analizando el `store.home`. Tenga atención a los comentarios inl
 ```
 
 Si descendemos podemos ver los mismos objetos JSON definiendo y configurando la organización de la página. Otro ejemplo es la página de resultados de la búsqueda:
-![Screen Shot 2019-01-25 at 18.22.12](//images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
+![Screen Shot 2019-01-25 at 18.22.12](https://images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
 
 La información describe la siguiente información de interfaz:
 
@@ -221,7 +221,7 @@ Es hora de visitar el archivo blocks.json de Dreamstore y entender cómo todo el
 
 ### Estructurando y configurando nuestra tienda con el `StoreBuilder`
 
-![Codigo voando blocks.mp4](//images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
+![Codigo voando blocks.mp4](https://images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
 
 Abra `/ blocks.json` y encuentre nuestro ya conocido `store.home`. Vamos a empezar analizando el primer bloque dentro de `store.home : carrossel#home`.
 
@@ -244,12 +244,12 @@ Es fácil ver cuán poderoso el constructor de tiendas puede ser cuando añadimo
   ```
 
 ### Estilizando nuestra tienda con el `StylesBuilder`
-![StyleBuilder.mp4](//images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
+![StyleBuilder.mp4](https://images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
 
 
 El StylesBuilder es simple de entender porque toma su archivo styles.json durante el build y utiliza el generador de [Tachyons](https://tachyons.io/) para producir el CSS de su tienda.
 
 Diseñamos el StylesBuilder para ser extremadamente intuitivo y autoexplicativo. Es tan simple como ajustar los códigos hexadecimales adecuadamente y ver los resultados en toda la tienda.
 
-![Screen Shot 2019-01-28 at 00.40.17](//images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
+![Screen Shot 2019-01-28 at 00.40.17](https://images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
 
diff --git a/docs/tutorials/es/understanding-the-additional-shipping-cost.md b/docs/tutorials/es/understanding-the-additional-shipping-cost.md
index 960517ad1..1d8148448 100644
--- a/docs/tutorials/es/understanding-the-additional-shipping-cost.md
+++ b/docs/tutorials/es/understanding-the-additional-shipping-cost.md
@@ -28,7 +28,7 @@ Existen tres formas de agregar un valor extra sobre el flete: valor adicional po
 
 El valor adicional por precio se calcula a partir del precio del producto. Se define un porcentaje que se aplicará al precio de este, y ese valor resultante se agrega al valor del flete inicialmente calculado.
 
-![adicionalfrete1 ES](//images.ctfassets.net/alneenqid6w5/7iLxQxdxAWMcm22yieiyc0/310afec9d0940032a726e33b47e490d4/adicionalfrete1_ES.png)
+![adicionalfrete1 ES](https://images.ctfassets.net/alneenqid6w5/7iLxQxdxAWMcm22yieiyc0/310afec9d0940032a726e33b47e490d4/adicionalfrete1_ES.png)
 
 En el caso anterior, el valor de los productos totaliza $ 80,00 y el valor registrado como __Valor adicional__ es de 10%. Es así que, el valor calculado que se agrega al valor del flete es de $ 8,00. La suma del valor final del flete y el valor adicional es de $18,00.
 
@@ -44,7 +44,7 @@ El valor adicional por peso se calcula con base en el peso del producto. Este ca
 
 El cálculo es el siguiente:
 
-![adicionalfrete2 ES](//images.ctfassets.net/alneenqid6w5/2bPpmLHucko8eGOEMUKEsQ/52029655a5f69fd3f358f780a3f89cc3/adicionalfrete2_ES.png)
+![adicionalfrete2 ES](https://images.ctfassets.net/alneenqid6w5/2bPpmLHucko8eGOEMUKEsQ/52029655a5f69fd3f358f780a3f89cc3/adicionalfrete2_ES.png)
 
 Es decir, en el ejemplo, la diferencia del valor mínimo del rango de peso registrado y el peso del producto es de 100 gramos. El valor registrado en el campo __Valor adicional por peso__ es de 0,1. Entonces, el valor que debe agregarse al cálculo es de 14,00. El valor final sería $ 24,00.
 
@@ -58,7 +58,7 @@ Revise nuestra documentación sobre [cómo montar la plantilla de flete](https:/
 
 Este valor adicional se calcula sobre el valor final del flete, y no sobre el valor del producto. El valor porcentual es lo último que se calcula en el flete.
 
-![adicionalfrete3 ES](//images.ctfassets.net/alneenqid6w5/7oQJz0N7qMuqyCWWm02KS6/3d1fceaaae7a96a930b81fa304dcc128/adicionalfrete3_ES.png)
+![adicionalfrete3 ES](https://images.ctfassets.net/alneenqid6w5/7oQJz0N7qMuqyCWWm02KS6/3d1fceaaae7a96a930b81fa304dcc128/adicionalfrete3_ES.png)
 
 En ese caso, el valor ingresado en el campo __Valor adicional__ será el valor porcentual que debe sumarse al valor final calculado del flete. Por ejemplo: si el flete, con todos sus valores adicionales ya calculados totaliza $20,00 y el valor registrado en el campo Adicional en los Fletes es 10, significa que se añadirán $2,00 a los $20,00 del flete, totalizando $ 22,00 que se cobrarán al cliente por el flete. Esa es una manera simple de lograr un margen sobre los fletes de las compras.
 
diff --git a/docs/tutorials/es/understanding-the-cubic-weight-factor.md b/docs/tutorials/es/understanding-the-cubic-weight-factor.md
index ae0aca52a..d1687b7b6 100644
--- a/docs/tutorials/es/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/es/understanding-the-cubic-weight-factor.md
@@ -40,7 +40,7 @@ Al calcular el factor de peso volumétrico, la plataforma VTEX no utiliza unidad
 
 Vea el ejemplo siguiente:
 
-![example_cubic_weight_es](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
+![example_cubic_weight_es](https://images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
 
 - __Dimensiones del paquete:__ `50cm x 60cm x 15cm`
 - __Peso mínimo del paquete:__ `9kg`
@@ -55,7 +55,7 @@ O sea, si el valor ofrecido por su compañía es `6.000`, es necesario realizar
 
 Ese es el valor que usted debe llenar en el campo Factor de peso volumétrico en su [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-![cubic_weight_ES](//images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/034836d577be3c7f920c2b195b255adb/cubic_weight_ES.png)
+![cubic_weight_ES](https://images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/034836d577be3c7f920c2b195b255adb/cubic_weight_ES.png)
 
 Por lo tanto, el cálculo final sería:
 
diff --git a/docs/tutorials/es/understanding-the-message-center.md b/docs/tutorials/es/understanding-the-message-center.md
index e5dd14eba..950b98c0d 100644
--- a/docs/tutorials/es/understanding-the-message-center.md
+++ b/docs/tutorials/es/understanding-the-message-center.md
@@ -31,7 +31,7 @@ Entienda la información que trae cada _card_ de plantilla :
 
 Para facilitar la navegación, la interfaz pone a disposición, además del campo de búsqueda por texto libre, filtros por aplicaciones (módulos) y tipo (mensaje estándar o personalizado/modificado).
 
-![busca-templates-central-mensagens es](//images.ctfassets.net/alneenqid6w5/7LOOmw6SWIaY0SQO28Oc2k/b5b9e138dd014e087d34d75a57c96bf2/busca-templates-central-mensagens_es.png)
+![busca-templates-central-mensagens es](https://images.ctfassets.net/alneenqid6w5/7LOOmw6SWIaY0SQO28Oc2k/b5b9e138dd014e087d34d75a57c96bf2/busca-templates-central-mensagens_es.png)
 
 Después de entender lo básico sobre los templates, usted ya puede ver cómo editarlos. Este paso no es obligatorio, pues VTEX suministra un layout básico y responsivo para todos los mensajes, con los datos necesarios para una buena comunicación con su cliente, pero es natural que las tiendas los adapten al estándar de comunicación ya usado para la marca.
 
diff --git a/docs/tutorials/es/understanding-the-price-change-rule.md b/docs/tutorials/es/understanding-the-price-change-rule.md
index f484d4ad2..0809587ac 100644
--- a/docs/tutorials/es/understanding-the-price-change-rule.md
+++ b/docs/tutorials/es/understanding-the-price-change-rule.md
@@ -26,6 +26,6 @@ Este bloqueo se realiza también para todas las demás formas de alteración del
 
 El porcentaje de limite de precio puede ser retirado o reformulado en la pestaña __Configuración__ del módulo __Precios__. 
 
-![trava-variação-preço es](//images.ctfassets.net/alneenqid6w5/7Gl4ECosVim4Si8GweU00e/6344add1a28b426b43f8af0219473fb0/trava-varia____o-pre__o_es.png)
+![trava-variação-preço es](https://images.ctfassets.net/alneenqid6w5/7Gl4ECosVim4Si8GweU00e/6344add1a28b426b43f8af0219473fb0/trava-varia____o-pre__o_es.png)
 
 Algunos marketplaces también utilizan este límite de variación de precios. Si desea cambiar los precios más allá de los límites configurados, basta ponerse en contacto con el marketplace solicitando el cambio.
diff --git a/docs/tutorials/es/understanding-the-security-report.md b/docs/tutorials/es/understanding-the-security-report.md
index 9c6096acd..aec905227 100644
--- a/docs/tutorials/es/understanding-the-security-report.md
+++ b/docs/tutorials/es/understanding-the-security-report.md
@@ -31,7 +31,7 @@ Es posible filtrarlo de diversas formas, a partir de las casillas abajo, conside
 
 En el ejemplo abajo hago el filtro para una alteración (ya sea creación o actualización) de precio de un SKU. Para eso, utilicé las casillas “Datos” con el Id del SKU, “Pantalla” con el lugar de la plataforma donde ocurre esa alteración y un período de tiempo específico. De acuerdo con el informe que se desea, puede ser necesario utilizar otras casillas en conjunto o en sustitución a esos que utilizo en el ejemplo.
 
-![relatorioseguran aPT.gif h 250?h=250](//images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/bfa1170fd5dbf3fe62f736a136db18b5/relatorio-seguranca-es.gif)
+![relatorioseguran aPT.gif h 250?h=250](https://images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/bfa1170fd5dbf3fe62f736a136db18b5/relatorio-seguranca-es.gif)
 
 ## Campos disponibles para el filtro
 
diff --git a/docs/tutorials/es/understanding-the-suspicious-purchase-notice-on-vtex-do.md b/docs/tutorials/es/understanding-the-suspicious-purchase-notice-on-vtex-do.md
index 1e2f6cb9f..2f8293323 100644
--- a/docs/tutorials/es/understanding-the-suspicious-purchase-notice-on-vtex-do.md
+++ b/docs/tutorials/es/understanding-the-suspicious-purchase-notice-on-vtex-do.md
@@ -27,7 +27,7 @@ Cuando el SherlockBOT identifica un pedido cerrado de manera que puede indicar a
 
 Vea un ejemplo de esa alerta en el screenshot a continuación:
 
-![sherlock (1)](//images.contentful.com/alneenqid6w5/6CsvYu9nfG0E4QowAEu86/c69b772065781ddc98bc85eeee37ef01/sherlock-1.png)
+![sherlock (1)](https://images.contentful.com/alneenqid6w5/6CsvYu9nfG0E4QowAEu86/c69b772065781ddc98bc85eeee37ef01/sherlock-1.png)
 
 El comerciante puede aún ser incluido en las barreras de seguridad del Gateway, o sea, VTEX puede aplicar a su tienda unas reglas de protección contra pruebas de tarjeta de crédito. 
 
diff --git a/docs/tutorials/es/understanding-the-task-list-vtex-do.md b/docs/tutorials/es/understanding-the-task-list-vtex-do.md
index 76f90697b..9c5c4e3ed 100644
--- a/docs/tutorials/es/understanding-the-task-list-vtex-do.md
+++ b/docs/tutorials/es/understanding-the-task-list-vtex-do.md
@@ -19,13 +19,13 @@ Vtex DO es un administrador de tareas generadas por los módulos de la plataform
 
 Para visualizar el listado de tareas, basta hacer clic en el canto inferior derecho de la pantalla del Gestión de Pedidos.  Algunos ejemplos de esas tareas son: __revisar pago para cancelar; extornar pago; autorizar pedido con alzada, cancelación requerida y muchas otras,__ pues cada módulo existente en Vtex tiene la autonomía y permiso para publicar cualquier información.
 
-![](//images.contentful.com/alneenqid6w5/6CypzWJhLye2OOW6QqEKu0/fce59ed1fedbb5f8889b1cb5f3ec4bf2/VtexDO_GifAbrir.gif)
+![](https://images.contentful.com/alneenqid6w5/6CypzWJhLye2OOW6QqEKu0/fce59ed1fedbb5f8889b1cb5f3ec4bf2/VtexDO_GifAbrir.gif)
 
 Esa funcionalidad permite al usuario las siguientes acciones: asignar las tareas a alguien (hasta para sí propio), señalarlas como resueltas, añadir un comentario y ver más detalles, que es la redirección para donde es necesario hacer la tarea. Existen los botones adiar e ignorar, pero son futuras acciones que se están desarrollándose todavía.
 
 ## Asignar y desasignar una tarea a sí propio
 
-![](//images.contentful.com/alneenqid6w5/hSiaD565VuWwKUmWuwucO/a7f7a04e378a43e14cc0ed8469deb573/VtexDO_GifAtribuirTarefaProprio.gif)
+![](https://images.contentful.com/alneenqid6w5/hSiaD565VuWwKUmWuwucO/a7f7a04e378a43e14cc0ed8469deb573/VtexDO_GifAtribuirTarefaProprio.gif)
 
 ### Asignar una tarea:
 - Abra el Vtex DO;
@@ -38,7 +38,7 @@ Esa funcionalidad permite al usuario las siguientes acciones: asignar las tareas
 
 ## Asignar y desasignar una tarea a otro usuario
 
-![](//images.contentful.com/alneenqid6w5/xTb2Dtb79ueKEiESCWi2y/05af0e238ac055a992b612381d3acd42/VtexDO_GifAtribuirTarefaTerceiros.gif)
+![](https://images.contentful.com/alneenqid6w5/xTb2Dtb79ueKEiESCWi2y/05af0e238ac055a992b612381d3acd42/VtexDO_GifAtribuirTarefaTerceiros.gif)
 
 ### Asignar una tarea:
 - Abra el VTEX DO;
@@ -55,7 +55,7 @@ _Las tareas que son asignadas a usted surgen en la pestaña denominada “MÍAS
 
 ## Filtrar una tarea
 
-![](//images.contentful.com/alneenqid6w5/1o6DK8SFHiuWwcESKScaqE/a616812c5d48431cf5383dbd204c511f/VtexDO_GifFiltro.gif)
+![](https://images.contentful.com/alneenqid6w5/1o6DK8SFHiuWwcESKScaqE/a616812c5d48431cf5383dbd204c511f/VtexDO_GifFiltro.gif)
 
 Es posible filtrar a través de la barra de búsqueda utilizando: el nombre de la tarea, nombre del usuario que está asignado a ellas o comentario insertado. Permite aún filtrar de acuerdo con el módulo que publicó la tarea.
 
@@ -73,7 +73,7 @@ Como el objetivo de la funcionalidad es realizar las tareas, una facilidad que e
 
 ## Realizar la tarea
 
-![](//images.contentful.com/alneenqid6w5/5nxobC9IVUGUe8CQoaI02I/84ac62df3673e85a379d3c9f409ef999/VtexDO_GifFazerTarefa.gif)
+![](https://images.contentful.com/alneenqid6w5/5nxobC9IVUGUe8CQoaI02I/84ac62df3673e85a379d3c9f409ef999/VtexDO_GifFazerTarefa.gif)
 
 1. Abra el Vtex DO;
 2. Haga clic sobre la tarea que desea realizar;
@@ -85,7 +85,7 @@ Para que se mantenga el VTEX DO de forma organizada, el ideal es finalizar la ta
 
 ## Finalizar o reabrir una tarea
 
-![](//images.contentful.com/alneenqid6w5/5Uc9dUfGusGcoAW6iw4EOa/52d9aa14d083b08e66fd4f9453cf1813/VtexDO_GifFinalizarTarefa.gif)
+![](https://images.contentful.com/alneenqid6w5/5Uc9dUfGusGcoAW6iw4EOa/52d9aa14d083b08e66fd4f9453cf1813/VtexDO_GifFinalizarTarefa.gif)
 
 ### Para finalizar una tarea:
 - Abra el VTEX DO;
@@ -101,7 +101,7 @@ Aún con el intuito de organizar esas tareas y formalizar la comunicación a tra
 
 ## Insertar un comentario
 
-![](//images.contentful.com/alneenqid6w5/5SrDSFwNIkokms4ayga2oo/86862b1896fabd96b34344318fd553fb/VtexDO_GifInserirComentario.gif)
+![](https://images.contentful.com/alneenqid6w5/5SrDSFwNIkokms4ayga2oo/86862b1896fabd96b34344318fd553fb/VtexDO_GifInserirComentario.gif)
 
 1. Abra el VTEX DO;
 2. Haga clic sobre la tarea que desea realizar un comentario;
@@ -110,4 +110,4 @@ Aún con el intuito de organizar esas tareas y formalizar la comunicación a tra
 
 Como hay la posibilidad de ejecutar las acciones del Vtex DO con él abierto, para cerrarlo es necesario hacer clic en la saeta para bajo, conforme en el gif abajo:
 
-![](//images.contentful.com/alneenqid6w5/6N34IAYvdKyYAa6KCIM2AO/670277853327aa793c851d8a0ce99b2a/VtexDO_GifFechar.gif)
+![](https://images.contentful.com/alneenqid6w5/6N34IAYvdKyYAa6KCIM2AO/670277853327aa793c851d8a0ce99b2a/VtexDO_GifFechar.gif)
diff --git a/docs/tutorials/es/understanding-the-topbar.md b/docs/tutorials/es/understanding-the-topbar.md
index 91b3f0e95..751f00ba6 100644
--- a/docs/tutorials/es/understanding-the-topbar.md
+++ b/docs/tutorials/es/understanding-the-topbar.md
@@ -19,17 +19,17 @@ La topbar es el punto de partida para todas las áreas del admin VTEX. A continu
 
 **Navegue entre los módulos**: Para ir a uno de los módulos, basta hacer clci sobre él en la sidebar del Admin.
 
-![paginainicial.es](//images.ctfassets.net/alneenqid6w5/207OIMwxY2Ilv2GgkiYWEj/05adb8d83d4038462a72912363e3ccd2/paginainicial.es.png)
+![paginainicial.es](https://images.ctfassets.net/alneenqid6w5/207OIMwxY2Ilv2GgkiYWEj/05adb8d83d4038462a72912363e3ccd2/paginainicial.es.png)
 
 **Navegue entre los sub-dominios**: Para navegar entre los sub-dominios de su tienda, basta hacer clic sobre el dominio actual. Usted visualizará todas las opciones. Para ir al admin de uno de los sub-dominios, basta hacer clic sobre él en el menú.
 
-![subdominios.es](//images.ctfassets.net/alneenqid6w5/61YQjUjUfJWRKgjHmnkpUc/883631d0aeadce6b51dc08d537d9ce70/subdominios.es.png)
+![subdominios.es](https://images.ctfassets.net/alneenqid6w5/61YQjUjUfJWRKgjHmnkpUc/883631d0aeadce6b51dc08d537d9ce70/subdominios.es.png)
 
 **Seleccione el idioma de admin**: Para seleccionar el idioma, basta hacer clic sobre el icono de idioma y seleccionar el idioma deseado.
-![idioma.es](//images.ctfassets.net/alneenqid6w5/axPKcMoKDJRxAqIn0QF8J/7d30ce95cfd5211a8db2dd606e4e737b/idioma.es.png)
+![idioma.es](https://images.ctfassets.net/alneenqid6w5/axPKcMoKDJRxAqIn0QF8J/7d30ce95cfd5211a8db2dd606e4e737b/idioma.es.png)
 
 **Acceda a nuestras bases de conocimiento**: Para acceder a una de nuestras bases, haga clic sobre su perfil de soporte y seleccione el lugar al que desea acceder, haciendo clic sobre él.
-![support.es](//images.ctfassets.net/alneenqid6w5/4M9na7OVRQqq68D9AUeV80/12751ce1d4656b7081e4be98bd7ea1c7/support.es.png)
+![support.es](https://images.ctfassets.net/alneenqid6w5/4M9na7OVRQqq68D9AUeV80/12751ce1d4656b7081e4be98bd7ea1c7/support.es.png)
 
 
 **Haga el logoff**: Para realizar el logoff, basta hacer clic sobre su nombre y hacer clic sobre el link **Sair**.
diff --git a/docs/tutorials/es/understanding-the-updating-of-the-xml.md b/docs/tutorials/es/understanding-the-updating-of-the-xml.md
index f7aa1130b..ff3f4739f 100644
--- a/docs/tutorials/es/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/es/understanding-the-updating-of-the-xml.md
@@ -21,6 +21,6 @@ Esa consulta significa que se convocó el XML en menos de 48 horas. Aquellos XML
 
 Es posible visualizar la última fecha de actualización del XML. Esa información queda en horario UTC al final del documento, conforme imagen abajo.
 
-![](//images.contentful.com/alneenqid6w5/5YwPKBeb5ekeGEu6gcQgUG/585efc76d9e56c5ed434d4faa6e526f0/xml.png)
+![](https://images.contentful.com/alneenqid6w5/5YwPKBeb5ekeGEu6gcQgUG/585efc76d9e56c5ed434d4faa6e526f0/xml.png)
 
 <div class="alert alert-info">Caso la opción "Exhibir los SKUs sin saldo disponible (agotados) en Stock entre los resultados" no esté señalada, los productos/SKUs que estén agotados <strong>no</strong> surgirán en el XML. Productos inactivos también <strong>no</strong> surgen en el XML.</div>
diff --git a/docs/tutorials/es/understanding-vtexs-email-capture-system.md b/docs/tutorials/es/understanding-vtexs-email-capture-system.md
index 52012a368..09c86a001 100644
--- a/docs/tutorials/es/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/es/understanding-vtexs-email-capture-system.md
@@ -51,5 +51,5 @@ Para que se pueda utilizar la función <a href="https://help.vtex.com/es/tutoria
 Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
 </div>
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/tutorials/es/untitled-entry-2017-07-03-at-03-49-03.md b/docs/tutorials/es/untitled-entry-2017-07-03-at-03-49-03.md
index cecb9bf84..713d9cea6 100644
--- a/docs/tutorials/es/untitled-entry-2017-07-03-at-03-49-03.md
+++ b/docs/tutorials/es/untitled-entry-2017-07-03-at-03-49-03.md
@@ -16,13 +16,13 @@ subcategory:
 ---
 
 Para registrar un attachment primero ingrese al módulo “E-commerce”, después al menu Registro de productos y entonces a Anexos de servicio y SKU conforme el print abajo.
-![PRINT1](//images.contentful.com/alneenqid6w5/2COCe9qS3iaaQWQIUQm4um/823e4c93ba405b26c8aa9ec2c92ab1c8/PRINT1.png)
+![PRINT1](https://images.contentful.com/alneenqid6w5/2COCe9qS3iaaQWQIUQm4um/823e4c93ba405b26c8aa9ec2c92ab1c8/PRINT1.png)
 
 Para crear un nuevo, haga click en **Novo Anexo**
-![PRINT2](//images.contentful.com/alneenqid6w5/1JB8o3N6MMwqQeoSCgYMOW/67dceded6d349782c8427ecc3c50c797/PRINT2.png)
+![PRINT2](https://images.contentful.com/alneenqid6w5/1JB8o3N6MMwqQeoSCgYMOW/67dceded6d349782c8427ecc3c50c797/PRINT2.png)
 
 En la pantalla de creación, usted tendrá los campos abajo:
-![Print3](//images.contentful.com/alneenqid6w5/3TbEtz9cSsioKYqycEOWsW/5517fe351b83be0e0e972eab5c8def5c/Print3.png)
+![Print3](https://images.contentful.com/alneenqid6w5/3TbEtz9cSsioKYqycEOWsW/5517fe351b83be0e0e972eab5c8def5c/Print3.png)
 
 __ID __= el ID VTEX  crea automáticamente  
 __Nombre__: su attachment adjunto debe tener un nombre único  o sea no puede tener otro con el mismo nombre.
@@ -30,10 +30,10 @@ __Anexo Obrigatorio__: sí o no, este campo define si este campo debe ser rellen
 __Status__: activo o no, esta opción indica si el campo está activado o no para vincular  a los productos de la tienda.
 
 Después de crear el attachment  haga clic en guardar, ahora tiene que crear los campos que aparecen en el attachment, haga clic en el cambio como en la image abajo.
-![Print4](//images.contentful.com/alneenqid6w5/51cwVnColGWau4yoGEiOYa/3d0b8225b68fea28eea5faf11ae28c00/Print4.png)
+![Print4](https://images.contentful.com/alneenqid6w5/51cwVnColGWau4yoGEiOYa/3d0b8225b68fea28eea5faf11ae28c00/Print4.png)
 
 Creando los campos, estos campos se mostrarán en el carrito del cliente una vez que tenga el producto que esta vinculado el attachment.
-![Print5](//images.contentful.com/alneenqid6w5/5u971r7L5CqKKwGU40Cqgo/6721f3915d2f01563c2d2f35f3362410/Print5.png)
+![Print5](https://images.contentful.com/alneenqid6w5/5u971r7L5CqKKwGU40Cqgo/6721f3915d2f01563c2d2f35f3362410/Print5.png)
 
 __Ejemplo Campo 1:__ You liked this item ?? En este campo no tenemos ningún límite de caracteres porque hemos seleccionado la opción true, false, o es este campo se convertirá automáticamente en un campo de casilla de verificación.
 
@@ -48,10 +48,10 @@ Ahora para asociar los attachments al Sku, debe regresar al menú y elegir el Re
 Elija uno de la lista SKU de SKU para asociar
 
 En el registro de la SKU va en configuración avanzada.
-![print8](//images.contentful.com/alneenqid6w5/5uM2lJknVSmMSa2O642S64/33b5d9d87256ab5e164cf058e7fb3adb/print8.png)
+![print8](https://images.contentful.com/alneenqid6w5/5uM2lJknVSmMSa2O642S64/33b5d9d87256ab5e164cf058e7fb3adb/print8.png)
 
 Al final de esta página que se enumeran las opciones de attachments registrados en la tienda, solo tienes que asignarlos a el Sku.
-![print9](//images.contentful.com/alneenqid6w5/3dvDRtRwHSeWG0koMsouu2/7d150a416ebae66c446db1d9b38c5520/print9.png)
+![print9](https://images.contentful.com/alneenqid6w5/3dvDRtRwHSeWG0koMsouu2/7d150a416ebae66c446db1d9b38c5520/print9.png)
 
 Después de hacer clic en guardar, el producto se enviará para la fila de indexación, después de se podrá ver el archivo adjunto asociado del carrito.
-![print10](//images.contentful.com/alneenqid6w5/4GQzaiothm8oEWuMgyAo22/ed069eccbe12b3b1a2949501650c6e38/print10.png)
+![print10](https://images.contentful.com/alneenqid6w5/4GQzaiothm8oEWuMgyAo22/ed069eccbe12b3b1a2949501650c6e38/print10.png)
diff --git a/docs/tutorials/es/updating-quantity-of-skus-in-inventory.md b/docs/tutorials/es/updating-quantity-of-skus-in-inventory.md
index 443346ecd..06ddba444 100644
--- a/docs/tutorials/es/updating-quantity-of-skus-in-inventory.md
+++ b/docs/tutorials/es/updating-quantity-of-skus-in-inventory.md
@@ -58,7 +58,7 @@ Recordando que un pedido puede tener una reserva del producto activa. Si el prod
 
 Los pedidos con ítems reservados seguirán figurando como reservados y no podrán venderse. En el siguiente ejemplo tenemos un caso en el que se reservan 10 unidades de Gatorade y los pedidos aún no se han facturado. A medida que actualizamos el conteo en stock, el sistema ya simula cuál será el resultado. En el ejemplo, hasta 10 ítems tienen un stock negativo, porque los pedidos con reserva activa siguen figurando en la lista. [Entienda mejor cómo funcionan las reservas](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona/). 
 
-![Atualizar Estoque GIF](//images.contentful.com/alneenqid6w5/1lorbuip9ewo8gY8qg8wU0/07e97e612b4711f0f21c205b50e74867/InventoryUpdate.gif)
+![Atualizar Estoque GIF](https://images.contentful.com/alneenqid6w5/1lorbuip9ewo8gY8qg8wU0/07e97e612b4711f0f21c205b50e74867/InventoryUpdate.gif)
 
 
 ## Actualización masiva de SKUs por plantilla
diff --git a/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md b/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md
index c6cb9209c..5f2dd6afa 100644
--- a/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md
+++ b/docs/tutorials/es/updating-the-quantity-of-items-in-inventory.md
@@ -45,7 +45,7 @@ _Unidades disponibles = unidades de la última actualización - unidades reserva
 
 El stock negativo suele producirse cuando se cancela el SKU de un pedido que ya tiene una reserva.  Para evitar esta situación, es importante que la actualización de la cantidad de SKU se realice en pedidos con _status_ posterior a `Preparando entrega`. De este modo, la [reserva ya habrá sido reconocida](https://help.vtex.com/es/tutorial/como-se-maneja-la-reserva--tutorials_92#reserva-reconocida) y no habrá conflicto entre los ítems en stock y los ítems que realmente están disponibles para la venta.
 
-![gerenciar inventarioES](//images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/51be4f67a41cec8ee04d4772d94a735e/gerenciar_inventarioES.gif)
+![gerenciar inventarioES](https://images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/51be4f67a41cec8ee04d4772d94a735e/gerenciar_inventarioES.gif)
 
 ## Artículos relacionados
 
diff --git a/docs/tutorials/es/uploading-a-product-xml.md b/docs/tutorials/es/uploading-a-product-xml.md
index 073d694b0..39ccde6e1 100644
--- a/docs/tutorials/es/uploading-a-product-xml.md
+++ b/docs/tutorials/es/uploading-a-product-xml.md
@@ -19,4 +19,4 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 _El video presentado en este tutorial aún no se ha traducido al español. Estamos trabajando para ofrecer más contenido en español. Gracias por la comprensión._
 
-<video class="wp-video-shortcode" id="video-2573-4" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4?_=4" />[//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4](//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4 "//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4")</video>
+<video class="wp-video-shortcode" id="video-2573-4" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4?_=4" />[//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4](https://assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4 "//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4")</video>
diff --git a/docs/tutorials/es/url-mapping-301-redirect.md b/docs/tutorials/es/url-mapping-301-redirect.md
index 8904dd0c0..2c27a9c9e 100644
--- a/docs/tutorials/es/url-mapping-301-redirect.md
+++ b/docs/tutorials/es/url-mapping-301-redirect.md
@@ -56,7 +56,7 @@ Hay dos maneras de añadir y cambiar un Mapeo de URL:
 3. Haga clic en la carpeta **URL Builder**.
 4. Haga clic en el botón `Import` para importar la plantilla.
 5. Descargue el modelo de plantilla que se ilustra a continuación haciendo clic en el botón `Click here`.
-![exemplo-planilha](//images.contentful.com/alneenqid6w5/2Z63gJkADcR2gveT3lncQb/9bbd790becd99acb7b647537eb71c6a9/Screenshot_5.png)
+![exemplo-planilha](https://images.contentful.com/alneenqid6w5/2Z63gJkADcR2gveT3lncQb/9bbd790becd99acb7b647537eb71c6a9/Screenshot_5.png)
 6. Rellene los [campos de la plantilla](#campos-de-la-plantilla).
 7. Después de rellenar la plantilla, haga clic en el botón `Browse for file` en la página de importación.
 8. Seleccione el archivo que desea importar desde su ordenador. El archivo debe tener la extensión `.xls` en formato `Excel 97-2003 Workbook`.
diff --git a/docs/tutorials/es/using-orders-managment-filters-in-api.md b/docs/tutorials/es/using-orders-managment-filters-in-api.md
index bb196dc4d..905f98dfd 100644
--- a/docs/tutorials/es/using-orders-managment-filters-in-api.md
+++ b/docs/tutorials/es/using-orders-managment-filters-in-api.md
@@ -28,19 +28,19 @@ El ejemplo utilizado es la API de consulta a los pedidos: http://{NOMBRETIENDA}.
 
 Utilizaremos el filtro por la fecha de creación del pedido en un intervalo que traiga todos los pedidos realizados **hace un mes** y que estén en el estado **listo para el manejo.**
 
-![](//images.contentful.com/alneenqid6w5/53zjSDeDBe20MkAQa2iqk0/ba1b8b24ddb63e121dd060a79aa1a534/OMS_Filtro5.png)
+![](https://images.contentful.com/alneenqid6w5/53zjSDeDBe20MkAQa2iqk0/ba1b8b24ddb63e121dd060a79aa1a534/OMS_Filtro5.png)
 
-![](//images.contentful.com/alneenqid6w5/3AS1rSk36MAwSIMGkaqsSm/1c496620f9c9669b7c9ccd6078681f8e/OMS_Filtro.png)
+![](https://images.contentful.com/alneenqid6w5/3AS1rSk36MAwSIMGkaqsSm/1c496620f9c9669b7c9ccd6078681f8e/OMS_Filtro.png)
 
-![](//images.contentful.com/alneenqid6w5/jj5tYpFP8WkYicAAIymCa/5157cf41ab647f31e20db895669eabea/OMS_Filtro2.png)
+![](https://images.contentful.com/alneenqid6w5/jj5tYpFP8WkYicAAIymCa/5157cf41ab647f31e20db895669eabea/OMS_Filtro2.png)
 
 Cuando se realizan los filtros, se generará una URL en el propio navegador con los parámetros seleccionados:
-![](//images.contentful.com/alneenqid6w5/WYPqJKIjwkuCO86SMU6sy/d5ad173798f8103c19990eed35709ecf/OMS_Filtro3.png)
+![](https://images.contentful.com/alneenqid6w5/WYPqJKIjwkuCO86SMU6sy/d5ad173798f8103c19990eed35709ecf/OMS_Filtro3.png)
 
 Por lo tanto, es necesario descodificar la dirección URL para ser interpretada por la interfaz de REST. Una herramienta ágil para ajustar esto manualmente es la [URL del dencoder]
 (http://meyerweb.com/eric/tools/dencoder/ "URL dencoder").
 
-![](//images.contentful.com/alneenqid6w5/4j6WPSCXq084cMaIcQ8QsE/8dcab3bc07fd714af788cea586293f57/OMS_Filtro4.png)
+![](https://images.contentful.com/alneenqid6w5/4j6WPSCXq084cMaIcQ8QsE/8dcab3bc07fd714af788cea586293f57/OMS_Filtro4.png)
 
 Hecho esto, basta con copiar la extensión de la URL desde el "?" Y pegar en la estructura de origen a la URL de solicitud.
 Por ejemplo: `http://{accountName}.vtexcommercestable.com.br/api/oms/pvt/orders?orderBy=creationDate,desc&f_creationDate=creationDate:[2017-01-01T03:00:00.000Z TO 2017-07-10T02:59:59.999Z]&f_statusDescription=Pronto+para+o+manuseio`
diff --git a/docs/tutorials/es/using-recaptcha-at-checkout.md b/docs/tutorials/es/using-recaptcha-at-checkout.md
index f18b1f8a9..2feb8a3cd 100644
--- a/docs/tutorials/es/using-recaptcha-at-checkout.md
+++ b/docs/tutorials/es/using-recaptcha-at-checkout.md
@@ -53,17 +53,17 @@ Puedes utilizar reCAPTCHA checkbox (v2). Es decir, cuando corresponda, el usuari
 
 Teniendo en cuenta los factores mencionados anteriormente, la experiencia de compra con tarjeta de débito o crédito suele seguir el flujo a continuación. Esto minimiza la incidencia de algunos tipos de fraude y ataques con una fricción mínima para el usuario.
 
-![reCAPTCHA scenariosES](//images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/596d96e2fd5ba06a1c390dc9d8d0ca68/reCAPTCHA_scenarios__2_.jpg)
+![reCAPTCHA scenariosES](https://images.ctfassets.net/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/596d96e2fd5ba06a1c390dc9d8d0ca68/reCAPTCHA_scenarios__2_.jpg)
 Como se ilustra en la imagen anterior, hay varios resultados posibles en este flujo:
 
 1. Si el algoritmo de VTEX Criteria no clasifica la sesión como sospechosa, la plataforma sigue con la compra de forma normal.
 
 2. De lo contrario, la interfaz debe mostrar la casilla de reCAPTCHA, que el cliente debe marcar. Si el reCAPTCHA no clasifica el comportamiento al marcar la casilla como sospechoso, la compra sigue de forma normal.
 
-![newCaptchaAnchor](//images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/9b8cf067c590a48d2560e9a170fa2022/newCaptchaAnchor.gif)
+![newCaptchaAnchor](https://images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/9b8cf067c590a48d2560e9a170fa2022/newCaptchaAnchor.gif)
 3. Si el reCAPTCHA clasifica el comportamiento como sospechoso, la interfaz mostrará el desafío.
 
-![desafio recaptcha](//images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/e820adf7252e86a94e79fc72eae1f536/desafio_recaptcha.png)
+![desafio recaptcha](https://images.ctfassets.net/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/e820adf7252e86a94e79fc72eae1f536/desafio_recaptcha.png)
 4. Si el desafío se resuelve con éxito, la plataforma sigue con la compra. Si no, el comportamiento se clasifica como compatible con un _bot_ y la plataforma no finaliza la compra.
 
 ## reCAPTCHA v3
diff --git a/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 9e11469bc..be09dedba 100644
--- a/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -43,7 +43,7 @@ Apps que tienen una dependencia de sesión monitorean cambios en sus entradas y
 
 Transforms frecuentemente disparan otros transforms, repitiendo hasta que ninguna actualización de parámetro adicional sea enviada por apps. Esta operación es, por supuesto, cuidadosamente monitoreada para evitar condiciones de loop. El siguiente diagrama ilustra un ejemplo de un ciclo de transform:
 
-![EN - Session Manager](//images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
+![EN - Session Manager](https://images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
 
 1. Se realizó un cambio en el parámetro de sesión X
 2. App A monitoreaba el parámetro de sesión X, lo que disparó el Transform 1
diff --git a/docs/tutorials/es/using-the-homepage-of-the-admin-panel.md b/docs/tutorials/es/using-the-homepage-of-the-admin-panel.md
index 62e2bb610..a64cb6c88 100644
--- a/docs/tutorials/es/using-the-homepage-of-the-admin-panel.md
+++ b/docs/tutorials/es/using-the-homepage-of-the-admin-panel.md
@@ -28,7 +28,7 @@ La sección de métricas está organizada en tres grandes grupos:
 - Datos de Pago;
 - Datos del Catálogo.
 
-![Action Dashboard](//images.contentful.com/alneenqid6w5/5ir6pwnlyMeQEeSOmOyisw/dcad530fb9c0004d32a89a3a6d5492ef/Action_Dashboard.png)
+![Action Dashboard](https://images.contentful.com/alneenqid6w5/5ir6pwnlyMeQEeSOmOyisw/dcad530fb9c0004d32a89a3a6d5492ef/Action_Dashboard.png)
 
 ### Bridge
 
@@ -64,4 +64,4 @@ Son exhibidos los artículos nuevos del Help VTEX o aquéllos que fueron actuali
 
 Bien debajo de los artículos, está la sección **Info e Eventos**, donde exhibimos novedades sobre la plataforma, consejos sobre e-commerce, informaciones sobre eventos de comercio electrónico y todo lo restante que sea divulgado por VTEX.
 
-![APIDocs](//images.contentful.com/alneenqid6w5/1GzmJz7qIwgm0kMq4smSk4/fb98a1d430346f559ada7800ad6cc321/APIDocs.png)
+![APIDocs](https://images.contentful.com/alneenqid6w5/1GzmJz7qIwgm0kMq4smSk4/fb98a1d430346f559ada7800ad6cc321/APIDocs.png)
diff --git a/docs/tutorials/es/validating-a-layout-before-moving-it-to-production.md b/docs/tutorials/es/validating-a-layout-before-moving-it-to-production.md
index 3fd1371d8..3454a5c86 100644
--- a/docs/tutorials/es/validating-a-layout-before-moving-it-to-production.md
+++ b/docs/tutorials/es/validating-a-layout-before-moving-it-to-production.md
@@ -34,7 +34,7 @@ Con esto, usted puede:
 
 Para encontrar el `LID`, basta con acceder al layout por el Admin, en el módulo CMS. Se encuentra en la sección __Properties__, como indica la siguiente imagen:
 
-![lid](//images.contentful.com/alneenqid6w5/4FISyY6wwg2asGE4Mog2sK/991b8c634b474c336de1754acdb414de/lid.png)
+![lid](https://images.contentful.com/alneenqid6w5/4FISyY6wwg2asGE4Mog2sK/991b8c634b474c336de1754acdb414de/lid.png)
 
 Para acceder a la página de la tienda con el nuevo layout, usted debe insertar un signo de interrogación al final de la URL y luego el parámetro `LID`.
 
@@ -53,7 +53,7 @@ Otra alternativa que le permite probar cambios en el layout antes de ir a produc
 
 Para encontrar el `WID`, acceda al web site. Se queda en el primer campo de la pantalla del web site: __Id de WebSite__.
 
-![wid](//images.contentful.com/alneenqid6w5/ghvd0wl9HqGu2KCWW2Yu2/5e27a13e79134f7ba89863ccd54031a6/wid.png)
+![wid](https://images.contentful.com/alneenqid6w5/ghvd0wl9HqGu2KCWW2Yu2/5e27a13e79134f7ba89863ccd54031a6/wid.png)
 
 Recuerde que, aunque con la duplicación del web site usted puede cambiar los layouts del nuevo web site de manera independiente, éstos van a consumir los mismos layouts del web site original. 
 
diff --git a/docs/tutorials/es/view-reindex-log.md b/docs/tutorials/es/view-reindex-log.md
index 63ef1827c..99032704b 100644
--- a/docs/tutorials/es/view-reindex-log.md
+++ b/docs/tutorials/es/view-reindex-log.md
@@ -21,7 +21,7 @@ Es posible consultar el registro de cuándo y quién realizó una reindexación
 
 En realidad, cualquier acción tomada en Full Clean Up está registrada en esta página.
 
-![fullcleanupLog](//images.contentful.com/alneenqid6w5/4imYxqJjWwog0UYwCIcWY4/a036d799b6de9d34a2e2f810f3780929/fullcleanupLog.png)
+![fullcleanupLog](https://images.contentful.com/alneenqid6w5/4imYxqJjWwog0UYwCIcWY4/a036d799b6de9d34a2e2f810f3780929/fullcleanupLog.png)
 
 El registro muestra la siguiente información para cada acción:
 - __Data__: fecha y hora de la acción.
diff --git a/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md b/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md
index d5c964ae0..419115717 100644
--- a/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md
+++ b/docs/tutorials/es/visao-geral-configuracoes-de-usuario.md
@@ -17,7 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 La *Configuración del usuario* es el conjunto de configuraciones aplicadas a tu perfil personal en el Admin, y no están relacionadas con tu tienda o la cuenta de tu negocio en VTEX. Para acceder a esta página, haz clic en tu **avatar de perfil**, marcado con la inicial de tu email, y luego haz clic en el botón **Configuración del usuario**. 
 
-![Admin v4 User settings menu ES](//images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/906a71481f7c64887b63187e9a1f2952/Admin_v4_User_settings_menu_ES.jpg)
+![Admin v4 User settings menu ES](https://images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/906a71481f7c64887b63187e9a1f2952/Admin_v4_User_settings_menu_ES.jpg)
 
 En esta página, que pronto se incluirá en el diseño del Admin v4, puedes realizar las siguientes acciones:
 
diff --git a/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md b/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md
index 7db4ce51c..10b03de33 100644
--- a/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md
+++ b/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md
@@ -21,7 +21,7 @@ En el Catálogo, los productos se organizan por categorías, y las categorías e
 
 Un ejemplo de la estructura de catálogo sería el siguiente:
 
-![img como funciona o catalogo](//images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
+![img como funciona o catalogo](https://images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
 
 <div class = "alert alert-warning">
 No es necesario que su árbol de categorías tenga tres niveles. La jerarquía que se muestra arriba es sólo un ejemplo. La cantidad de niveles de categorías a ser creados depende mucho del sector de actuación de cada tienda.
diff --git a/docs/tutorials/es/vtex-ad-network-beta.md b/docs/tutorials/es/vtex-ad-network-beta.md
index f7470595b..600e226b1 100644
--- a/docs/tutorials/es/vtex-ad-network-beta.md
+++ b/docs/tutorials/es/vtex-ad-network-beta.md
@@ -45,7 +45,7 @@ Actualmente, VTEX ofrece un único formato de anuncio: productos patrocinados. E
 
 Consulta a continuación un ejemplo del modo de exhibición de este formato:
 
-![vtex_ad_network_sponsored_ES](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/bfec823e3960cac69bf878395437cdec/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_ES](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/bfec823e3960cac69bf878395437cdec/vtex_ad_network_sponsored.png)
 
 Los retailers participantes en **VTEX Ad Network** podrán [configurar la cantidad de espacios para anuncios](https://help.vtex.com/es/tutorial/anunciando-com-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse#crear-campana) que disponibilizarán en cada uno de estos contextos en la tienda.
 
diff --git a/docs/tutorials/es/vtex-admin-start-here.md b/docs/tutorials/es/vtex-admin-start-here.md
index c8ae6504e..5bfb9aca9 100644
--- a/docs/tutorials/es/vtex-admin-start-here.md
+++ b/docs/tutorials/es/vtex-admin-start-here.md
@@ -18,7 +18,7 @@ subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 El Admin VTEX permite a los administradores de la tienda gestionar todas sus experiencias de comercio digital en un solo lugar, de forma sencilla e inteligente. Aquí dan seguimiento a los pedidos, registran productos, configuran fulfillment y llevan a cabo los demás aspectos de una operación de comercio unificado.
 
 ## Página de inicio
-![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 La página de inicio proporciona una vista de alto nivel de tu tienda, como una cabina de mando para tus operaciones de comercio digital, y por eso se llama [Vista general](https://help.vtex.com/es/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -28,7 +28,7 @@ Una vez que accedas al Admin, verás métricas y gráficos útiles para monitore
 
 Nuestros menús laterales de navegación y la barra superior agrupan categorías similares de forma más clara para reducir las distracciones y ayudar a tu equipo a encontrar lo que necesita más rápidamente. 
 
-![menu de navegación admin SEP2023](//images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/76b32915010a0dc372fe94ba378e690e/admin-navigation.png)
+![menu de navegación admin SEP2023](https://images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/76b32915010a0dc372fe94ba378e690e/admin-navigation.png)
 
 Puede utilizar la barra de búsqueda global para buscar páginas en el Admin VTEX o pedidos de su tienda. Por defecto, la búsqueda está configurada en `Páginas`. Para buscar un pedido, haga clic en la barra, seleccione la opción `Pedidos` y utilice cualquiera de los siguientes criterios:
 
@@ -58,7 +58,7 @@ También puedes utilizar la barra de búsqueda en la parte superior del Admin VT
 
 ### Centro de información
 
-![centro de información admin SEP2023](//images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/b1146f7ef7eec57f4f2a9c7a5f3e25c1/Information_center.gif)
+![centro de información admin SEP2023](https://images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/b1146f7ef7eec57f4f2a9c7a5f3e25c1/Information_center.gif)
 
 Allí hemos reunido todos los enlaces útiles de nuestro ecosistema VTEX para ayudarte a sacar el máximo partido a nuestra plataforma. Haciendo clic en el botón <i class='fa fa-question-circle-o'></i>  en la barra superior, puedes acceder a nuestro [Help Center](https://help.vtex.com), [Developer Portal](https://developers.vtex.com/), [Plataform Status](https://status.vtex.com/), [blog](https://vtex.com/es/blog/) y a las páginas de soporte.
 
@@ -68,7 +68,7 @@ El botón Dar feedback permite al usuario compartir su opinión sobre su experie
 2. Haz clic en la opción **Dar feedback**.
 
 Se abrirá un formulario de Google donde podrás enviar tus comentarios. Tras el envío, recibirás un email de confirmación.
-![Botão feedback - ES](//images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/38ed137e7d5d226361bee4ecd98a1f18/Bot_o_feedback_-_ES.gif)
+![Botão feedback - ES](https://images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/38ed137e7d5d226361bee4ecd98a1f18/Bot_o_feedback_-_ES.gif)
 
 #### Formulario de feedback
 El objetivo principal de las preguntas presentes en el formulario de feedback es obtener información detallada sobre la experiencia y las percepciones con respecto al producto en el Admin VTEX.
@@ -97,7 +97,7 @@ Este proceso de feedback no debe utilizarse para abrir un ticket o solicitud de
 
 ### Configuración de la cuenta y del usuario
 
-![configuraciones de avatar admin SEP2023](//images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/bd3df394bdf8c173763d8df481cf3a52/Avatar_settings2.gif)
+![configuraciones de avatar admin SEP2023](https://images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/bd3df394bdf8c173763d8df481cf3a52/Avatar_settings2.gif)
 
 El avatar de tu perfil reúne todas las configuraciones relacionadas con tu usuario y tu cuenta. A través del avatar, puedes acceder a la [Configuración del usuario](https://help.vtex.com/es/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), a la [Configuración de la cuenta](https://help.vtex.com/es/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), y a la información de las [Facturas](https://help.vtex.com/es/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC).  También puedes cambiar el idioma del Admin y cerrar la sesión.
 
diff --git a/docs/tutorials/es/vtex-admin-start-here1.md b/docs/tutorials/es/vtex-admin-start-here1.md
index 9b17b7d58..67cb41ca0 100644
--- a/docs/tutorials/es/vtex-admin-start-here1.md
+++ b/docs/tutorials/es/vtex-admin-start-here1.md
@@ -18,7 +18,7 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 El Admin renovado permite a los comerciantes gestionar todas sus experiencias de comercio digital en un solo lugar, de forma sencilla e inteligente.
 
 ## Página de inicio
-![Store Overview gif ES](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
+![Store Overview gif ES](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b91a459e41bac28866c1165ca8fcc208/Store_Overview_gif_ES.gif)
 
 La página de inicio del admin ha sido rediseñada para proporcionar una visión general de alto nivel de tu tienda, como una cabina de mando para tus operaciones de comercio digital, y ahora se llama [Vista general](https://help.vtex.com/es/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -26,24 +26,24 @@ Una vez que accedas al Admin, verás métricas y gráficos útiles para monitore
 
 ## Navegación mejorada 
 
-![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/6b08cbf42beadbe9f8d58e345285b93b/New_Admin_Shell__1_.png)
+![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/6b08cbf42beadbe9f8d58e345285b93b/New_Admin_Shell__1_.png)
 
 Todo lo que necesitas para gestionar tu tienda VTEX sigue estando disponible en el Admin, pero ahora con una organización más sencilla. Nuestros menús laterales de navegación y la barra superior han sido completamente rediseñados, y ahora agrupan categorías similares de forma más clara para reducir las distracciones y ayudar a tu equipo a encontrar lo que necesita más rápidamente. También puedes utilizar la barra de búsqueda para encontrar secciones específicas en el menú lateral.
 
 ### Centro de información
 
-![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/2a2b0054854d4b726fa4a502b6e3db52/Information_center.gif)
+![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/2a2b0054854d4b726fa4a502b6e3db52/Information_center.gif)
 
 Allí hemos reunido todos los enlaces útiles de nuestro ecosistema VTEX para ayudarte a sacar el máximo partido a nuestra plataforma. Haciendo clic en el botón `?` en la barra superior, puedes acceder a nuestro Centro de ayuda, al Portal del desarrollador, al Status de la plataforma, al blog y a las páginas de soporte.
 
 ## Configuración de la tienda
-![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/b96a55b9faaffc3b604c74fa5a128d61/Store_settings.gif)
+![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/b96a55b9faaffc3b604c74fa5a128d61/Store_settings.gif)
 
 Para esta experiencia, hemos reunido las configuraciones de todas las secciones del Admin en una pestaña específica: [Configuración de la tienda](https://help.vtex.com/es/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Gracias a esta mejora, puedes acceder fácilmente a todas las configuraciones que afectan a cada servicio de tu cuenta.
 
 ### Configuración de la cuenta y del usuario
 
-![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/c560ccf053bfcf4f127db55ec088f7f9/Avatar_settings.gif)
+![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/c560ccf053bfcf4f127db55ec088f7f9/Avatar_settings.gif)
 
 El avatar de tu perfil, en la esquina superior derecha, reúne ahora todas las configuraciones relacionadas con tu usuario y tu cuenta. A través del avatar, puedes acceder a la [Configuración del usuario](https://help.vtex.com/es/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), a la [Configuración de la cuenta](https://help.vtex.com/es/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), y a la información de las [Facturas](https://help.vtex.com/es/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC).  También puedes cambiar el idioma de tu Admin y cerrar la sesión.
 
diff --git a/docs/tutorials/es/vtex-agreement.md b/docs/tutorials/es/vtex-agreement.md
index a5f9cdc69..c7f738a59 100644
--- a/docs/tutorials/es/vtex-agreement.md
+++ b/docs/tutorials/es/vtex-agreement.md
@@ -17,7 +17,7 @@ subcategory: 22TaEgFhwE6a6CG2KASYkC
 
 El contrato VTEX o acuerdo comercial consta de dos partes, el [MSA (Master Service Agreement)](https://vtex.com/mx-es/privacy-and-agreements/agreements/) y el **Anexo 1 Order Form** para la prestación de servicios a empresas o [MPA (Master Partner Agreement)](https://vtex.com/mx-es/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) y **Términos y condiciones específicos de la asociación**.
 
-![Contrato VTEX](//images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/8c31246d19b7238ab6c87db7e2521ffe/es.png)
+![Contrato VTEX](https://images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/8c31246d19b7238ab6c87db7e2521ffe/es.png)
 
 El [Master Services Agreement](https://vtex.com/mx-es/privacy-and-agreements/agreements/) y el [Master Partner Agreement](https://vtex.com/mx-es/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) son los contratos marco de servicio y de asociación, respectivamente, que regulan la relación entre VTEX y el cliente o VTEX y el partner. Ambos varían en función de la región en la que se encuentra la empresa o el partner. 
 
diff --git a/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
index efe82d340..7db8ee7c2 100644
--- a/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
+++ b/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
@@ -34,7 +34,7 @@ A continuación puedes consultar algunos consejos para aprovechar al máximo est
 
 Empieza ajustando la zona horaria deseada y selecciona la tienda que deseas monitorear en Vista general en tiempo real.  
 
-![zona-horaria-es](//images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/7d760ad2226fec81b75c0e524b6a8220/zona-horaria-es.png)
+![zona-horaria-es](https://images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/7d760ad2226fec81b75c0e524b6a8220/zona-horaria-es.png)
 
 ### Filtro de referencia  
 
@@ -51,26 +51,26 @@ Para configurar la referencia sigue los pasos a continuación:
 Una comparación valiosa durante la Black Week se realiza al contrastar datos con la misma fecha del año anterior. En la configuración de referencia, se recomienda establecer preferiblemente una fecha entre el 21/11/2022 y el 27/11/2022, preferentemente los mismos días de la semana. <br>Esta opción está dirigida a clientes que utilizaron el Admin VTEX durante ese periodo el año pasado.</br>
 </div>  
 
-![referencia-es](//images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/4466f9301343f19f0ff79d89f5c44821/referencia-es.png)  
+![referencia-es](https://images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/4466f9301343f19f0ff79d89f5c44821/referencia-es.png)  
 
 ### Filtro de vista  
 
 - **Realiza un seguimiento del desempeño del día con la Vista Acumulado:** esta vista muestra el monitoreo del desempeño de ventas de tu tienda online minuto a minuto, proporcionando insights para ajustes rápidos en la operación.  
 Para seleccionar el modo **Acumulado** en el dashboard, haz clic en **Vista<i class="fas fa-angle-down"></i> > Acumulado.**   
 
-![acumulado-es](//images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/754d3fdb3071c9daef2acd282b8d3733/acumulado-es.png)  
+![acumulado-es](https://images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/754d3fdb3071c9daef2acd282b8d3733/acumulado-es.png)  
 
 - **Monitorea el desempeño de las últimas horas:** la **vista Últimas 2 horas** presenta las métricas minuto a minuto, importante para garantizar la estabilidad operacional de tu tienda durante el evento.  
 Para seleccionar el modo **Últimas 2 Horas** en el dashboard, haz clic en **Vista<i class="fas fa-angle-down"></i> > Últimas 2 horas.**
 
-![horas-es](//images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/368a2857ec9b9636011031ae989f8bb9/horas-es.png)  
+![horas-es](https://images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/368a2857ec9b9636011031ae989f8bb9/horas-es.png)  
 
 ### Métricas  
 
 La **Vista general en tiempo real** otorga insights importantes sobre tu estrategia de ventas. Por ejemplo, puedes utilizar los datos presentes en Productos más vendidos como referencia para impulsar campañas y potenciar aún más tus resultados.  
 Para consultar los productos más vendidos, en la sección **Métricas**  haz clic en  <i class="fas fa-ellipsis-v"></i> y selecciona **Productos más vendidos.**  
 
-![mas-vendidos-es](//images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/22b06efc2dd15dded404a1c4b1f23f2c/mas-vendidos-es.png)   
+![mas-vendidos-es](https://images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/22b06efc2dd15dded404a1c4b1f23f2c/mas-vendidos-es.png)   
 
 <div class="alert alert-danger">
 Para análisis o seguimientos de periodos más extensos, recomendamos el uso de nuestro dashboard Desempeño de ventas, que se detalla en la siguiente pregunta.
@@ -84,7 +84,7 @@ Para un seguimiento efectivo de tu tienda online más allá del día actual, el
 
 - **Fecha**  
 Al acceder al dashboard, el primer paso es definir el **Periodo principal** y **Comparar con.** Si estás realizando el análisis una vez finalizada la Black Week, selecciona Semana pasada para comparar con la Black Week del año anterior (opción disponible si ya eras cliente de VTEX). Durante la Black Week, elige Personalizar y selecciona los días específicos para el análisis.  
-![ventas-fecha-es](//images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/2b20340d6c7237d5d9b1056ea3371896/ventas-fecha-es.png)   
+![ventas-fecha-es](https://images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/2b20340d6c7237d5d9b1056ea3371896/ventas-fecha-es.png)   
 
 - **Filtros combinados**  
 La información proporcionada en el dashboard de ventas se puede segmentar mediante filtros combinados, como, por ejemplo, el filtro Categorías. Si deseas agregar un nuevo filtro, sigue los pasos que se detallan a continuación:  
@@ -95,7 +95,7 @@ La información proporcionada en el dashboard de ventas se puede segmentar media
 
 Puedes explorar diferentes filtros de acuerdo con las necesidades y aspectos específicos de tu tienda online.  
 
-![agregar-filtro-es](//images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/ddc34564c2379083779ead2e8eb36f9f/agregar-filtro-es.png)   
+![agregar-filtro-es](https://images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/ddc34564c2379083779ead2e8eb36f9f/agregar-filtro-es.png)   
 
 ### Métricas  
 
@@ -109,22 +109,22 @@ Durante la Black Week, este dashboard es una herramienta clave para analizar las
 - Ticket promedio (aprobado)  
 - Pedidos (cancelados)  
 
-![cambio-de-metrica-es](//images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/10826d203b100064613c3c8df5cecd07/cambio-de-metrica-es.png)  
+![cambio-de-metrica-es](https://images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/10826d203b100064613c3c8df5cecd07/cambio-de-metrica-es.png)  
 
 - **Desempeño de la semana**   
 Después de realizar los ajustes, compara el desempeño de la semana actual con la Black Week del año pasado para identificar tendencias y oportunidades.  
 
-![desenpeno-de-la-semana-es](//images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/6e7b2320f5a89ea5f1873d5655e60ea9/desenpeno-de-la-semana-es.png)  
+![desenpeno-de-la-semana-es](https://images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/6e7b2320f5a89ea5f1873d5655e60ea9/desenpeno-de-la-semana-es.png)  
 
 - **Análisis de la tabla**   
 Analiza los datos de la tabla para obtener insights más profundos. Por ejemplo, el análisis por SKU puede revelar qué productos deben destacarse en futuras campañas.  
 
-![analisis-de-la-tabla-es](//images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/d584956e1fb744a7a006a3128ecd0fb4/analisis-de-la-tabla-es.png)  
+![analisis-de-la-tabla-es](https://images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/d584956e1fb744a7a006a3128ecd0fb4/analisis-de-la-tabla-es.png)  
 
 - **Guarda la vista de tu interés**  
 Guarda la configuración de tu dashboard para futuras consultas. Haz clic en **Gestión de ventas > <i class="fas fa-plus"></i>  > Nombre de la vista > `Crear`,** para guardar tu vista personalizada.  
 
-![crear-vista-es](//images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/635dfd2f1cb8b7f6f31e95e36704baa3/crear-vista-es.png)    
+![crear-vista-es](https://images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/635dfd2f1cb8b7f6f31e95e36704baa3/crear-vista-es.png)    
 
 ## ¿Por qué mis métricas son diferentes de las del menú Pedidos del Admin?  
 
@@ -135,7 +135,7 @@ Hay varias razones por las cuales las métricas de la Vista general en tiempo re
 - **Tiempo de actualización diferente:** la pantalla Vista general en tiempo real puede demorar en actualizarse de 1 a 3 minutos. Por lo tanto, es normal que haya una pequeña discrepancia (de 1 a 3 % del total) entre ambas pantallas.  
 - **Fórmula de cálculo de ingresos:** las métricas en Vista general en tiempo real no consideran descuentos, envíos, tarifas ni promociones en el cálculo de ingresos, mientras que las métricas presentes en Pedidos sí que tienen en cuenta esos factores.  
 
-![selecion-de-tiendas-es](//images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/6921089644b0d5821da2692011534c9e/selecion-de-tiendas-es.png)  
+![selecion-de-tiendas-es](https://images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/6921089644b0d5821da2692011534c9e/selecion-de-tiendas-es.png)  
 
 Para obtener una visión completa de las métricas combinadas de todas las tiendas, te recomendamos acceder al dashboard Desempeño de ventas. Este dashboard ofrece datos agregados con una tasa de actualización de aproximadamente 90 minutos.  
 
@@ -143,11 +143,11 @@ Para obtener una visión completa de las métricas combinadas de todas las tiend
 Si tu tienda online opera con más de una moneda puedes consultar los pedidos en el <b>dashboard Vista general;</b> el total de los mismos se presentan sumados en la moneda más utilizada en tus ventas. <br>Para comparar con la pantalla <b>Pedidos,</b> debes sumar el total de pedidos en todas las monedas.</br>
 </div>    
 
-![todos-los-pedidos-es](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
+![todos-los-pedidos-es](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
 
 - **Zona horaria:** este filtro puede aplicarse en el dashboard **Vista general** en tiempo real; en caso de que la zona horaria sea diferente a la definida en la pantalla Pedidos (que es tu zona horaria actual), las métricas no serán iguales. Ajusta la zona horaria si fuera necesario.  
 
-![ventas-zona-horaria](//images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/26a44df390eaf73e4e16889540dd46ab/ventas-zona-horaria.png)   
+![ventas-zona-horaria](https://images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/26a44df390eaf73e4e16889540dd46ab/ventas-zona-horaria.png)   
 
 ## ¿Por qué no tengo datos de sesiones o tasas de conversión?  
 
@@ -157,7 +157,7 @@ Sin embargo, es importante saber que nuestro script no captura datos de sesiones
 
 Si percibes la ausencia de estos datos, podría deberse a una de las limitaciones anteriormente mencionadas. Recomendamos verificar las configuraciones del script y cualquier personalización en el frontend que pueda estar afectando la captura de datos.  
 
-![vision-general-es](//images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/ac409a2e6f8df8dd575f67aea6cac85c/vision-general-es.png)
+![vision-general-es](https://images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/ac409a2e6f8df8dd575f67aea6cac85c/vision-general-es.png)
 
 ## ¿Por qué mis métricas de tasa de conversión, nuevas sesiones o embudo de ventas no coinciden con los números de mis herramientas internas?  
 
@@ -175,9 +175,9 @@ Para determinar qué moneda mostrar, evaluamos cuál es la moneda más utilizada
 
 Como resultado, si operas con más de una moneda, es importante sumar el total de pedidos de la sección Pedidos del Admin en todas tus monedas para que coincida con los datos mostrados en los pedidos dentro de Vista general en tiempo real.  
 
-![todos-los-pedidos-es](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
+![todos-los-pedidos-es](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
 
-![monitoreo-es](//images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/03430c27c5ed46f970ad711c18b8042a/monitoreo-es.png)    
+![monitoreo-es](https://images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/03430c27c5ed46f970ad711c18b8042a/monitoreo-es.png)    
 
 ## ¿Por qué el número de pedidos en el análisis del embudo de ventas no coincide con el de la sección Monitoreo?  
 
@@ -187,8 +187,8 @@ Por otro lado, los datos del embudo de ventas se recopilan de la base de navegac
 
 Como resultado, es común que el número de pedidos en el embudo de ventas sea menor que en la sección Monitoreo, que proporciona una visión más amplia de las ventas de la tienda, incluyendo canales externos a la plataforma VTEX.  
 
-![tasa-de-conversion-es](//images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/43cf092b352a825a20d12692909c6f1c/tasa-de-conversion-es.png)  
-![nuevas-sesiones-es](//images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/8b3df33b3054de0743e95db323eeefd2/nuevas-sesiones-es.png)  
+![tasa-de-conversion-es](https://images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/43cf092b352a825a20d12692909c6f1c/tasa-de-conversion-es.png)  
+![nuevas-sesiones-es](https://images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/8b3df33b3054de0743e95db323eeefd2/nuevas-sesiones-es.png)  
 
 ## ¿Por qué la nueva Vista general se encuentra en una URL separada?  
 
diff --git a/docs/tutorials/es/vtex-do-interface.md b/docs/tutorials/es/vtex-do-interface.md
index 6758afe52..1e455b4df 100644
--- a/docs/tutorials/es/vtex-do-interface.md
+++ b/docs/tutorials/es/vtex-do-interface.md
@@ -17,7 +17,7 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 VTEX DO es un gestor de tareas creadas automáticamente por el Admin VTEX para que el equipo de _ecommerce_ de tu tienda las realice manualmente. Para acceder a VTEX DO, en el menú del Admin VTEX, ve a **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/lista-de-pedidos--2QTduKHAJMFIZ3BAsi6Pi)** y haz clic en el ícono de bandeja de entrada, ubicado en la esquina inferior derecha de la página. Al hacer clic en el ícono, se abrirá un modal con la lista de tareas relacionadas con los pedidos de la tienda.
 
-![VTEX Do overview ES](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
+![VTEX Do overview ES](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
 
 <div class = "alert alert-info">
 Solo los usuarios con el perfil de acceso <a href = "https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> pueden realizar tareas a través de VTEX DO.
@@ -115,7 +115,7 @@ Las tareas gestionadas a través de VTEX DO pueden incluir mensajes de todos los
 
 ## Detalles de la tarea
 
-![VTEX Do details ES](//images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/d72c3000996192d5f687c6adf8b0b381/VTEX_Do_details_ES.jpg)
+![VTEX Do details ES](https://images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/d72c3000996192d5f687c6adf8b0b381/VTEX_Do_details_ES.jpg)
 
 Al hacer clic en el nombre de una tarea de la lista, se te redirige al modal de detalles de la tarea que presenta más información sobre la misma y las acciones para resolverla. Se muestran los siguientes campos:
 
diff --git a/docs/tutorials/es/vtex-insurance.md b/docs/tutorials/es/vtex-insurance.md
index aa6b4e8e7..8cd7116d9 100644
--- a/docs/tutorials/es/vtex-insurance.md
+++ b/docs/tutorials/es/vtex-insurance.md
@@ -55,7 +55,7 @@ Después de instalar VTEX Insurance, necesitas preparar el catálogo para inclui
 5. Después de crear el campo **Garantía del fabricante**, establece el período de garantía deseado. En el campo **Valor predeterminado**, se recomienda el valor 12, que representa un rango de 12 meses.
 6. [Crea una categoría]https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1) específica para el producto del seguro. 
 7. [Crea el producto](https://help.vtex.com/es/tutorial/productos-y-skus-beta--2ig7TmROlirWirZjFWZ3B) del seguro.
-8. [Crea los SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY) del seguro. Se recomienda crear más de tres SKU para cada seguro.![Valores Permitidos](//images.ctfassets.net/alneenqid6w5/7DTx1xSHfrWWPCCvVHjJ8z/db89bae8fd2b247707a557c9aa253285/image1.png)
+8. [Crea los SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY) del seguro. Se recomienda crear más de tres SKU para cada seguro.![Valores Permitidos](https://images.ctfassets.net/alneenqid6w5/7DTx1xSHfrWWPCCvVHjJ8z/db89bae8fd2b247707a557c9aa253285/image1.png)
 9. [Vincula los SKU](https://help.vtex.com/es/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX) creados con el seller de Assurant.
 10. [Vincula el seguro con el producto](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-producto--tutorials_106) deseado.
 
@@ -70,7 +70,7 @@ Una vez preparado el catálogo, los productos de tu tienda ya estarán vinculado
 Sigue los pasos a continuación para configurar la aplicación VTEX Insurance.
 
 ### Información de la empresa
-![Insurance Configuration](//images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/1158b7f84241410fbd3edc81400ff5a5/image5.png)
+![Insurance Configuration](https://images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/1158b7f84241410fbd3edc81400ff5a5/image5.png)
 1. Rellena los siguientes campos:
 - **Email**: email de la tienda
 - **Nombre**: nombre de la tienda
@@ -84,7 +84,7 @@ Sigue los pasos a continuación para configurar la aplicación VTEX Insurance.
 2. Haz clic en `Enviar`.
 
 ### Ítems vinculados a seguros
-![Items Bound to Source Items](//images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/7fd57ef26b0320e745bb81736d76707e/image2.png)
+![Items Bound to Source Items](https://images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/7fd57ef26b0320e745bb81736d76707e/image2.png)
 
 1. Selecciona los códigos que representan los tipos de seguro deseados para la colección creada. 
 
@@ -93,13 +93,13 @@ Si deseas vincular más de un tipo de seguro, como el de **Robo y hurto agravado
 3. Haz clic en `Enviar`.
 
 ### Nombre del campo de la garantía
-![Warranty Field Name](//images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/90a5985112d73bbd552e553353790899/image8.png)
+![Warranty Field Name](https://images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/90a5985112d73bbd552e553353790899/image8.png)
 
 1. En el campo de garantía del fabricante ingresa el nombre de la garantía utilizado en el catálogo.
 2. Haz clic en `Enviar`.
 
 ### Configuración de anexos VTEX Insurance 
-![Attachement Setup](//images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/853b158cfce470f32cceb2489564ac54/insurance_attachement_setup.png)
+![Attachement Setup](https://images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/853b158cfce470f32cceb2489564ac54/insurance_attachement_setup.png)
 
 1. [Crea un anexo](https://help.vtex.com/es/tutorial/registrar-un-anexo--7zHMUpuoQE4cAskqEUWScU) para Assurant con la información enviada por el equipo de soporte al contratar el servicio.
 
@@ -113,7 +113,7 @@ Si deseas vincular más de un tipo de seguro, como el de **Robo y hurto agravado
 
 ### Configuración de precios manual
 
-![Manual Pricing](//images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/fa85e9cdf6064218cf182242475056c8/image11.png)
+![Manual Pricing](https://images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/fa85e9cdf6064218cf182242475056c8/image11.png)
 
 1. [Activa la configuración de precios manual](https://help.vtex.com/es/tutorial/cambiar-el-precio-de-un-item-en-el-carrito-de-compras--7Cd37aCAmtL1qmoZJJvjNf) en tu tienda.
 2. Haz clic en `Continuar`.
diff --git a/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
index 5cc09c836..d32c24455 100644
--- a/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -43,7 +43,7 @@ VTEX Intelligent Search Multidioma permite que personalice la experiencia de bú
 ### Reglas de merchandising
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la página de edición o creación de Reglas de merchandising — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Reglas de merchandising__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará la regla de merchandising mediante la selección de los idiomas deseados, como se muestra en la siguiente imagen.  
 
-![img regrasmerch intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/a0f959bcd8d52fe586e7b4ab4d91c63a/01-merchrules-es.png)
+![img regrasmerch intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/a0f959bcd8d52fe586e7b4ab4d91c63a/01-merchrules-es.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Reglas de merchandising en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8).
 
@@ -57,7 +57,7 @@ Hay dos formas de configurar Sinónimos en una tienda multidioma en el Admin: co
 #### Crear Sinónimos vía formulario
 Cuando tiene VTEX Intelligent Search Multidioma instalada,  la página de edición o creación de Sinónimos — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Sinónimos__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará los sinónimos registrados, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
 
-![img sinonimos intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/3fe16ea17b2f435094c2cb823831e57b/image_4.png)
+![img sinonimos intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/3fe16ea17b2f435094c2cb823831e57b/image_4.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Sinónimos en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
@@ -81,7 +81,7 @@ Para saber más sobre la importación de una plantilla de Sinónimos, lea nuestr
 
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la página de edición o creación de Redireccionamientos  — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Redireccionamientos__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará las redirecciones registradas, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
 
-![img redirecionamentos intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/84213b8bd9f82c318b08f54813358fa4/03-redirecionamento-en.png)
+![img redirecionamentos intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/84213b8bd9f82c318b08f54813358fa4/03-redirecionamento-en.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Redireccionamientos en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4Gd2wLQFbCwTsh8RUDwSoL).
 
@@ -89,6 +89,6 @@ Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar
 
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la página de edición o creación de Banners — que se accede en el Admin VTEX en __Storefront__ > __Banners__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará los banners registrados, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
 
-![img banner intelligentsearchmultilanguage ES](//images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8231d24b62009bf4afeb9ce8299650a7/image_9.png)
+![img banner intelligentsearchmultilanguage ES](https://images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/8231d24b62009bf4afeb9ce8299650a7/image_9.png)
 
 Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar Banners en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
diff --git a/docs/tutorials/es/vtex-invoice-notifier.md b/docs/tutorials/es/vtex-invoice-notifier.md
index bfa6dcdcf..8f613fb0c 100644
--- a/docs/tutorials/es/vtex-invoice-notifier.md
+++ b/docs/tutorials/es/vtex-invoice-notifier.md
@@ -29,9 +29,9 @@ Con el endpoint registrado en el APP, el OMS comienza a reconocer que se habilit
 
 El operador debe, en el pedido, seleccionar el paquete o los ítems que desea facturar y generar una nueva notificación:
 
-![notify-invoicer1](//images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
+![notify-invoicer1](https://images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
 
-![notify-invoicer2](//images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
+![notify-invoicer2](https://images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
 
 Cuando el usuario del OMS presione el botón __Request Invoice__, el app realizará un request POST en el endpoint registrado en el APP con el siguiente BODY, ejemplo:
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
index 445dc2bcc..6fc3f866b 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
@@ -56,13 +56,13 @@ Para empezar a utilizar Pick and Pack, es necesario tener acceso a la [aplicaci
 
 Ingresa tu usuario debidamente registrado, contraseña y haz clic en  **iniciar sesión**.
 
-![pick and pack 1](//images.ctfassets.net/alneenqid6w5/3tIH46Q7spSVEa1nDMBaHU/6c9cf04d64fe02a4a4e27c0cbcfe9ea2/image26.png)
+![pick and pack 1](https://images.ctfassets.net/alneenqid6w5/3tIH46Q7spSVEa1nDMBaHU/6c9cf04d64fe02a4a4e27c0cbcfe9ea2/image26.png)
 
 ## Página de inicio
 
 Al acceder, se habilita el dashboard del alistador, que te permitirá monitorizar, analizar y visualizar los indicadores clave de desempeño del alistador.
 
-![pick and pack 2](//images.ctfassets.net/alneenqid6w5/3Hx3ir28gfSdv60DupqIpj/d169addf3e5162f53fd4ffae4fabf172/image3.png)
+![pick and pack 2](https://images.ctfassets.net/alneenqid6w5/3Hx3ir28gfSdv60DupqIpj/d169addf3e5162f53fd4ffae4fabf172/image3.png)
 
 - Permite visualizar de manera gráfica la cantidad de pedidos alistados durante los últimos días.
 - Puedes consultar la cantidad de pedidos con alistamiento finalizado.
@@ -74,11 +74,11 @@ En la sección superior de la aplicación podrás encontrar las siguientes funci
 
 - **Selección de instalación,** ubicada a la derecha del ícono del usuario alistador. Al tocar, indica las instalaciones asociadas al usuario.
 
-![pick and pack 3](//images.ctfassets.net/alneenqid6w5/7KTcPX2RJjmo7QMfZxsxx8/b5b10100395ac08bc6cb78575e3eeaed/image15.png)
+![pick and pack 3](https://images.ctfassets.net/alneenqid6w5/7KTcPX2RJjmo7QMfZxsxx8/b5b10100395ac08bc6cb78575e3eeaed/image15.png)
 
 - **Menú**, donde figuran los accesos directos a las funcionalidades principales de la aplicación.
 
-![pick and pack 4](//images.ctfassets.net/alneenqid6w5/2633eMzDne2LCpYWqksCUm/e09e4962d5a17b8b68993387b2fcb719/image17.png)
+![pick and pack 4](https://images.ctfassets.net/alneenqid6w5/2633eMzDne2LCpYWqksCUm/e09e4962d5a17b8b68993387b2fcb719/image17.png)
 
 ## Proceso de alistamiento
 
@@ -96,9 +96,9 @@ Las hojas de trabajo permitirán combinar varios pedidos, de modo que todos los
 
 Elige los pedidos que deseas gestionar y haz clic en la opción  **Empezar a alistar.** En ese momento el sistema crea las hojas de trabajo, con su respectivo número de identificación, que estarán compuestas por los ítems de los pedidos seleccionados.
 
-![pick and pack 5](//images.ctfassets.net/alneenqid6w5/3ibz0RB8PSB3NdQnfVmXny/dc584f577881dbe47ff343a05ea0c528/image43.png)
+![pick and pack 5](https://images.ctfassets.net/alneenqid6w5/3ibz0RB8PSB3NdQnfVmXny/dc584f577881dbe47ff343a05ea0c528/image43.png)
 
-![pick and pack 6](//images.ctfassets.net/alneenqid6w5/79AdZNyZkpj3dK8uLfFUnz/ee0bd30e3073345a515d46c7e0de1019/image11.png)
+![pick and pack 6](https://images.ctfassets.net/alneenqid6w5/79AdZNyZkpj3dK8uLfFUnz/ee0bd30e3073345a515d46c7e0de1019/image11.png)
 
 De igual manera, se  habilitarán las acciones de alistamiento para cada producto que compone los pedidos asociados a las hojas de trabajo.
 
@@ -108,7 +108,7 @@ Hay varias formas de iniciar el alistamiento de los productos:
 
 Sitúate sobre el producto que deses alistar, y desliza hacia la izquierda.
 
-![pick and pack 7](//images.ctfassets.net/alneenqid6w5/1hGlv0xBZbzSxviLzKXHTW/05f428c28ca4faff07d563b48a8e60e6/image39.png)
+![pick and pack 7](https://images.ctfassets.net/alneenqid6w5/1hGlv0xBZbzSxviLzKXHTW/05f428c28ca4faff07d563b48a8e60e6/image39.png)
 
 Si se pulsa una vez sobre el producto, solo será alistada una unidad. Si se pulsa dos veces, se alistarán todas las unidades.
 
@@ -118,15 +118,15 @@ Existen varias formas de rechazar un producto:
 
 Sitúate en el producto que deseas alistar, y desliza hacia el lado derecho.
 
-![pick and pack 8](//images.ctfassets.net/alneenqid6w5/57QUYlKaUtl360QlxWC4kt/af1d8ca336a5f911568f9ec948461bf4/image7.png)
+![pick and pack 8](https://images.ctfassets.net/alneenqid6w5/57QUYlKaUtl360QlxWC4kt/af1d8ca336a5f911568f9ec948461bf4/image7.png)
 
 Mantén pulsado el producto y se desplegará un menú, donde puedes seleccionar Descartar ítem.
 
-![pick and pack 9](//images.ctfassets.net/alneenqid6w5/2zRTW81m8FsoFpvNl70O4/b6b7f8ebe0d37d6439a348ed0735a5f0/image25.png)
+![pick and pack 9](https://images.ctfassets.net/alneenqid6w5/2zRTW81m8FsoFpvNl70O4/b6b7f8ebe0d37d6439a348ed0735a5f0/image25.png)
 
 Después, debe incluirse el motivo del rechazo. Si lo deseas, puedes rechazar una cantidad específica, ingresando la cifra para después pulsar la opción Descartar unidades. También puedes descartarlas todas, como se muestra en la captura de pantalla a continuación.
 
-![pick and pack 10](//images.ctfassets.net/alneenqid6w5/78Ghr0v7Dp1PkKqLF1Q4pZ/2fc6d278277e1aa09c19ffad4c05935d/image23.png)
+![pick and pack 10](https://images.ctfassets.net/alneenqid6w5/78Ghr0v7Dp1PkKqLF1Q4pZ/2fc6d278277e1aa09c19ffad4c05935d/image23.png)
 
 ### Reemplazar ítems
 
@@ -134,17 +134,17 @@ La opción **Reemplazar ítem** se encuentra en el menú que se despliega al toc
 
 Si se accede a **Reemplaza ítem**, el sistema valida los pedidos a los que pertenece el producto. Si existen pedidos que comparten productos el sistema habilita el listado de los pedidos asociados.
 
-![pick and pack 11](//images.ctfassets.net/alneenqid6w5/2fFFzKLeIp6dNgknXAYuC/efdcba4627eadd592938dc8d4419218c/image21.png)
+![pick and pack 11](https://images.ctfassets.net/alneenqid6w5/2fFFzKLeIp6dNgknXAYuC/efdcba4627eadd592938dc8d4419218c/image21.png)
 
 Selecciona los pedidos deseados y toca la opción **Reemplazar en los pedidos seleccionados.** Después, el sistema habilitará la pantalla **Reemplazar ítem.**
 
 La pantalla Reemplazar ítem habilita los productos asociados al producto a reemplazar. Puedes utilizar el filtro de búsqueda.
 
-![pick and pack 12](//images.ctfassets.net/alneenqid6w5/3lGf61iDMk0nXqPtpIjTvM/3ff3f40f5609d481d8ee1d844a586a5a/image57.png)
+![pick and pack 12](https://images.ctfassets.net/alneenqid6w5/3lGf61iDMk0nXqPtpIjTvM/3ff3f40f5609d481d8ee1d844a586a5a/image57.png)
 
 Selecciona el producto deseado y haz clic en  la opción Reemplazar ítem: el sistema habilitará los campos de reemplazo.
 
-![pick and pack 13](//images.ctfassets.net/alneenqid6w5/1pYNdI9Az53pRgdg1cYTnm/aef41d13dbcfa7534c36fe94de3733ff/image35.png)
+![pick and pack 13](https://images.ctfassets.net/alneenqid6w5/1pYNdI9Az53pRgdg1cYTnm/aef41d13dbcfa7534c36fe94de3733ff/image35.png)
 
 Se pueden ingresar los siguientes datos:
 - Precio.
@@ -159,7 +159,7 @@ Toca la opción **Confirmar reemplazo.**
 
 Para ingresar observaciones sobre el producto, accede al menú del ítem y después a la opción **Agregar observaciones.**
 
-![pick and pack 14](//images.ctfassets.net/alneenqid6w5/1r3yi390cfL6GxMcbEAWyj/1f8138ce000a1408441d5f77dbed2d2b/image31.png)
+![pick and pack 14](https://images.ctfassets.net/alneenqid6w5/1r3yi390cfL6GxMcbEAWyj/1f8138ce000a1408441d5f77dbed2d2b/image31.png)
 
 Si existen pedidos que comparten producto, selecciona el pedido al que debe asociarse la observación. Ingresa la observación y toca la opción **Agregar observación.**
 
@@ -171,7 +171,7 @@ Para ingresar observaciones a la hoja de trabajo, nos ubicamos en el menú y sel
 - **Pausar alistamiento:** al hacer clic sobre esta opción, la hoja de trabajo queda en estado de pausa para no afectar el rendimiento del alistador.
 - **Imprimir lista de alistamiento:** disponibiliza un documento que enumera los ítems alistados de cada pedido.
 
-![pick and pack 15](//images.ctfassets.net/alneenqid6w5/7D4oZ5bWzb5BPeN43xH7HV/002a586863b4e1044aeac477b165cc2e/image45.png)
+![pick and pack 15](https://images.ctfassets.net/alneenqid6w5/7D4oZ5bWzb5BPeN43xH7HV/002a586863b4e1044aeac477b165cc2e/image45.png)
 
 ## Proceso de empaquetado
 
@@ -181,13 +181,13 @@ Existen varias formas de iniciar el empaque.
 
 En el dashboard se encuentra la opción **Para empaquetar;** al acceder, nos redirige a la lista de hojas de trabajo pendientes por empacar. Desde el menú, accedemos a la lista de **Empaquetado** ubicada dentro de la opción **Pendiente.**
 
-![pick and pack 15](//images.ctfassets.net/alneenqid6w5/5wiF37YnG1uwyR3j3SjB50/f3634ddeab5a581319b18252955ae4b3/image9.png)
+![pick and pack 15](https://images.ctfassets.net/alneenqid6w5/5wiF37YnG1uwyR3j3SjB50/f3634ddeab5a581319b18252955ae4b3/image9.png)
 
 Dentro de la pestaña **Empaquetado** seleccionamos la hoja de trabajo que se encuentre en estado Listo para empaquetar o Empaquetado para iniciar o continuar el proceso de empaque.
 
 Al acceder encontramos la lista de productos, donde podemos realizar un empaque individual o en masa.
 
-![pick and pack 16](//images.ctfassets.net/alneenqid6w5/76b06UUuKR7apFSGFXfetA/2a2b5bdfd1377b631e33102676adc9d3/image14.png)
+![pick and pack 16](https://images.ctfassets.net/alneenqid6w5/76b06UUuKR7apFSGFXfetA/2a2b5bdfd1377b631e33102676adc9d3/image14.png)
 
 ### Empaquetado individual o en masa
 
@@ -199,7 +199,7 @@ Al tocar, se abre una ventana donde seleccionar el pedido para hacer el empaque
 
 Verifica los productos del pedido que seleccionaste y toca la opción Empaquetar producto.
 
-![pick and pack 17](//images.ctfassets.net/alneenqid6w5/4cTjjNy4p1dcFjTFklDhhi/ccb4a42627f2d3e78a3ef26f23f9ee28/image5.png)
+![pick and pack 17](https://images.ctfassets.net/alneenqid6w5/4cTjjNy4p1dcFjTFklDhhi/ccb4a42627f2d3e78a3ef26f23f9ee28/image5.png)
 
 #### Empaquetado individual
 
@@ -215,7 +215,7 @@ Agrega las unidades y selecciona la opción **Empaquetar producto.**
 
 Una vez alistados todos los ítems, debes realizar el proceso de envío seleccionando desde el menú la opción **Para enviar.**
 
-![pick and pack 18](//images.ctfassets.net/alneenqid6w5/3JqIlsCpWHul7ou3md1N4h/8307b7628684191dfa7f712ca4293808/image18.png)
+![pick and pack 18](https://images.ctfassets.net/alneenqid6w5/3JqIlsCpWHul7ou3md1N4h/8307b7628684191dfa7f712ca4293808/image18.png)
 
 Se abrirá el listado de pedidos que se encuentran listos para envío, organizados por fecha de empaque. Haz clic sobre el pedido que deseas enviar.
 
@@ -229,7 +229,7 @@ Para crear el servicio de envío, deben proporcionarse los siguientes datos:
 
 Al terminar, toca en la opción **Seleccionar y continuar.**
 
-![pick and pack 18](//images.ctfassets.net/alneenqid6w5/7mvhayvPfwyNkHgq5DMCWk/24ad3596a5d163694abc38f6b858a226/image16.png)
+![pick and pack 18](https://images.ctfassets.net/alneenqid6w5/7mvhayvPfwyNkHgq5DMCWk/24ad3596a5d163694abc38f6b858a226/image16.png)
 
 Verifica los datos del servicio y haz clic en la opción **Crear servicio.**
 
@@ -257,7 +257,7 @@ Posee un filtro de búsqueda configurable según la necesidad de resultado del u
 
 Cuenta con un botón para **cerrar** ventana, o en su defecto, para **borrar todos** los filtros seleccionados.
 
-![pick and pack 20](//images.ctfassets.net/alneenqid6w5/2cCfB2KdjWyRdvD8q9z4BF/3710266548a474dff6516120945ed626/image4.png)
+![pick and pack 20](https://images.ctfassets.net/alneenqid6w5/2cCfB2KdjWyRdvD8q9z4BF/3710266548a474dff6516120945ed626/image4.png)
 
 La  sección Pedidos muestra la tabla de datos sin filtrar, con las opciones:
 
@@ -315,7 +315,7 @@ También posee la opción de Fijado, donde el usuario puede acceder a los pedido
 
 Además, cuenta con un filtro de búsqueda que permite encontrar los pedidos según la necesidad del usuario.
 
-![pick and pack 21](//images.ctfassets.net/alneenqid6w5/T6d3roLMCvoOMi52X7KMJ/3faf3580c22a2c289ff7aeef7c2ffc7f/image59.png)
+![pick and pack 21](https://images.ctfassets.net/alneenqid6w5/T6d3roLMCvoOMi52X7KMJ/3faf3580c22a2c289ff7aeef7c2ffc7f/image59.png)
 
 ## Configuración de la aplicación
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-insights.md b/docs/tutorials/es/vtex-pick-and-pack-insights.md
index 4196670b0..d7c1d9859 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-insights.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-insights.md
@@ -21,7 +21,7 @@ Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes s
 
 **Análisis** es una página del Admin VTEX que muestra información sobre el desempeño de tu tienda en relación con VTEX Pick and Pack.
 
-![pick-pack-insights-es](//images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/acdc7944f550df2f4aef7ed7102deb7a/image.png)
+![pick-pack-insights-es](https://images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/acdc7944f550df2f4aef7ed7102deb7a/image.png)
 
 La página presenta las siguientes secciones:
 
@@ -40,7 +40,7 @@ En esta sección puedes consultar el número total de pedidos y hojas de trabajo
 * Últimos tres meses
 * Últimos seis meses
 
-![pick-pack-insights-2-es](//images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/53d44d3093593ddea822acdeffd09776/image.png)
+![pick-pack-insights-2-es](https://images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/53d44d3093593ddea822acdeffd09776/image.png)
 
 ## Tiempo de las etapas
 
@@ -50,17 +50,17 @@ En esta sección puedes consultar información sobre la duración de cada etapa
 * Tiempo de empaque
 * Tiempo de envío
 
-![pick-pack-insights-3-es](//images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/e30499f47212c9a0019715c6d9dfb927/image.png)
+![pick-pack-insights-3-es](https://images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/e30499f47212c9a0019715c6d9dfb927/image.png)
 
 ## Pedidos - Desempeño de pedidos
 
 En esta sección tendrás acceso a información sobre el rendimiento global de los pedidos y el tiempo promedio de fulfillment de cada uno.
 
-![pick-pack-insights-4-es](//images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/5bd9362932a056895c1c10b6973ce6a8/image.png)
+![pick-pack-insights-4-es](https://images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/5bd9362932a056895c1c10b6973ce6a8/image.png)
 
 ## Ítems
 
 En esta sección puedes consultar información sobre los ítems de pedidos gestionados en VTEX Pick and Pack, el tiempo promedio de alistamiento por ítem, el número de ítems seleccionados por alistador y la tasa de fulfillment de pedidos.
 
-![pick-pack-insights-5-es](//images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/d81f53b9f063002e607e358ac645d3f3/image.png)
+![pick-pack-insights-5-es](https://images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/d81f53b9f063002e607e358ac645d3f3/image.png)
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-mobile.md b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
index fd26c9de1..d0f0be66c 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
@@ -21,7 +21,7 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 
 La aplicación móvil de [VTEX Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) ayuda al alistador (profesional responsable de seleccionar y empacar los ítems en la instalación) en la preparación de los pedidos, desde el alistamiento de los ítems hasta el envío. Esto hace que el flujo de alistamiento y envío de los pedidos de la tienda sea más organizado y fluido.
 
-![pickpack-mobile-es](//images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/b4c69a98c2576d0f90e9b676d41b7ac6/image.png)
+![pickpack-mobile-es](https://images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/b4c69a98c2576d0f90e9b676d41b7ac6/image.png)
 
 La preparación de pedidos se divide en cuatro etapas, que siguen el flujo habitual de los pedidos en la tienda:
 
@@ -56,7 +56,7 @@ Las hojas de trabajo solo se aplican a las etapas de alistamiento y empaque de l
 
 La pestaña Sin asignar muestra en una lista los pedidos que deben seleccionarse para agregarlos a las hojas de trabajo. 
 
-![pickpack-ordemservico-es](//images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/d09cf0ea6e858d28afebb79b55999e31/image.png)
+![pickpack-ordemservico-es](https://images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/d09cf0ea6e858d28afebb79b55999e31/image.png)
 
 Para agregar una hoja de trabajo sigue los pasos a continuación:
 
@@ -72,7 +72,7 @@ La etapa de alistamiento consiste en seleccionar físicamente los ítems de una
 
 La pestaña __Pendientes__ muestra la lista de hojas de trabajo cuyo alistamiento no ha finalizado.
 
-![pickpack-pendente-es](//images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/ff9f1a49db76f2032e7021971bf15cad/image.png)
+![pickpack-pendente-es](https://images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/ff9f1a49db76f2032e7021971bf15cad/image.png)
 
 En esta pestaña, puedes seleccionar por el ID de una hoja de trabajo si deseas que se muestren solamente los ítems ya alistados de ese pedido.
 
@@ -87,7 +87,7 @@ Al hacer clic en una hoja de trabajo se mostrará la siguiente información:
 - __Información:__ información general sobre la hoja de trabajo y el pedido.
 - __Resumen:__ productos ya alistados por el alistador.
 
-![pickpack-em-separacao-es](//images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/acafdfb2d52a575eb150dbd8ad3e4bc8/image.png)
+![pickpack-em-separacao-es](https://images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/acafdfb2d52a575eb150dbd8ad3e4bc8/image.png)
 
 Al hacer clic en el menú <i class="fas fa-ellipsis-v"></i>, se mostrarán las siguientes acciones:
 
@@ -102,7 +102,7 @@ Para alistar un producto sigue estos pasos:
 
 1. En la pantalla de __Alistamiento__, accede a la pestaña __Ítems__.
 2. Haz clic en el producto que deseas alistar o desliza el producto hacia la derecha. Si el producto tiene más de una unidad, haz clic en la cantidad de unidades del producto. Para productos que contienen peso o volumen, debes confirmar la medida y, a continuación, confirmar la selección, como en el ejemplo a seguir:
-![pickpack-item-es](//images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/efdd37c986299e346a325606885a1218/image.png)
+![pickpack-item-es](https://images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/efdd37c986299e346a325606885a1218/image.png)
 
 ## Para alistar todos los productos de la hoja de trabajo de una sola vez, sigue estos pasos:
 
@@ -165,14 +165,14 @@ Una vez alistados, rechazados o reemplazados todos los ítems de la hoja de trab
 
 En la etapa de empaque, el alistador selecciona los ítems de cada pedido en los respectivos embalajes de envío. La aplicación móvil de Pick and Pack permite la organización de todos los paquetes necesarios para los diversos pedidos de manera rápida y sencilla.
 
-![pickpack-empacotamento-es](//images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/282dc96e07df744684a5775a4c711d92/image.png)
+![pickpack-empacotamento-es](https://images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/282dc96e07df744684a5775a4c711d92/image.png)
 
 Puedes acceder a la página Empaque al [concluir el alistamiento](#finalizar-alistamiento) de una hoja de trabajo o siguiendo los pasos a continuación:
 
 1. En la pantalla de inicio de la aplicación, haz clic en **Empaque **. Aparecerá una lista con las [hojas de trabajo](#hojas-de-trabajo) asignadas al alistador que están en la etapa de empaque.
 2. Haz clic en la hoja de trabajo cuyos productos deseas empacar. 
 
-![pickpack-item-pendente-es](//images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/d1a0dff72b963012706819c39a88d8c3/image.png)
+![pickpack-item-pendente-es](https://images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/d1a0dff72b963012706819c39a88d8c3/image.png)
 
 Sigue los pasos que se indican a continuación para empacar ítems:
 
@@ -191,10 +191,10 @@ Repite este procedimiento tantas veces como sea necesario para empacar todos los
 Los ítems ya empacados están disponibles en la pestaña **Ítems empacados**. Puedes alternar la vista de los ítems entre una lista de ítems o de pedidos y empaques haciendo clic en <i class="fas fa-toggle-on"></i>.
 
 __Lista de ítems__
-![pickpack-item-empacotado-es](//images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/bc3bfe853b3fe8c2f2e7f728f71a67f5/image.png)
+![pickpack-item-empacotado-es](https://images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/bc3bfe853b3fe8c2f2e7f728f71a67f5/image.png)
 
 __Pedidos y paquetes__
-![pickpack-item-empacotado-2-es](//images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/9d3600f0ac99fe235eb017d0879e0a4a/image.png)
+![pickpack-item-empacotado-2-es](https://images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/9d3600f0ac99fe235eb017d0879e0a4a/image.png)
 
 Una vez empacados todos los ítems de la hoja de trabajo, puedes finalizar el empaque en la pestaña __Ítems empacados__ haciendo clic en el botón `Confirmar empaque`.
 
@@ -216,7 +216,7 @@ Para enviar paquetes desde la aplicación Pick and Pack, sigue los pasos que se
 4. Rellena los datos de envío:
     - **Fecha prevista de recolección**
     - **Fecha prevista de entrega**
-    ![pickpack-envio-es](//images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/bf144c5d0a68fef03cab3c2a7db92d33/image.png)
+    ![pickpack-envio-es](https://images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/bf144c5d0a68fef03cab3c2a7db92d33/image.png)
 5. Selecciona una transportadora disponible.
 6. Haz clic en `Seleccionar y continuar`.
 7. Confirma la información de envío. Si no es necesario hacer correcciones, haz clic en el botón `Crear servicio`. En caso contrario, haz clic en `Atrás` y vuelve al paso 5. 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-orders.md b/docs/tutorials/es/vtex-pick-and-pack-orders.md
index 9505fc371..b20acb442 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-orders.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-orders.md
@@ -28,7 +28,7 @@ Esta página te permite realizar las siguientes acciones:
 * [Filtrar pedidos](#filtrar-pedidos) 
 * [Exportar pedidos](#exportar-pedidos)
 
-![pick-and-pack-pedidos-ES](//images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/0b19e96e2057462deca476086792e17d/image.png)
+![pick-and-pack-pedidos-ES](https://images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/0b19e96e2057462deca476086792e17d/image.png)
 
 La página presenta la siguiente información en forma de tabla: 
 
@@ -56,7 +56,7 @@ Puedes optimizar la consulta de pedidos desde las siguientes secciones:
 
 También puedes acceder a información más detallada sobre cada pedido haciendo clic en el pedido en la tabla.
 
-![pick-and-pack-pedidos-2-ES](//images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/8307fcdea5832aa1a653f812c0eaba02/image.png)
+![pick-and-pack-pedidos-2-ES](https://images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/8307fcdea5832aa1a653f812c0eaba02/image.png)
 
 Al seleccionar el pedido deseado, se mostrará la siguiente información:
 
@@ -91,5 +91,5 @@ Puedes exportar pedidos siguiendo los pasos a continuación:
 1. Haz clic en `Exportar`.
 2. Selecciona los datos que deseas exportar: `Informe de paquetes` o `Informe de pedidos`.
     - En el caso de `Informe de paquetes`, debes seleccionar el periodo que deseas exportar, el tipo y el método de envío.
-    ![pick-and-pack-pedidos-3-ES](//images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/ab4c8bcb38a8ab892c57aeeec869dac8/image.png)
+    ![pick-and-pack-pedidos-3-ES](https://images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/ab4c8bcb38a8ab892c57aeeec869dac8/image.png)
 3.  Haz clic en `Exportar`.
diff --git a/docs/tutorials/es/vtex-pick-and-pack-settings.md b/docs/tutorials/es/vtex-pick-and-pack-settings.md
index 425899098..289a771b0 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-settings.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-settings.md
@@ -34,7 +34,7 @@ __Configuración__ es una página del Admin VTEX donde puedes realizar los ajust
 
 En esta sección se encuentran los ajustes relativos a la etapa de alistamiento, donde puedes definir las acciones que el alistador puede realizar durante el proceso de alistamiento, incluyendo la notificación de la falta de disponibilidad de un ítem del pedido y la sugerencia de otro para su sustitución.
 
-![pick-and-pack-separacao-es](//images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/c9c4916113ccf7f6252cb17d736a0ba9/image.png)
+![pick-and-pack-separacao-es](https://images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/c9c4916113ccf7f6252cb17d736a0ba9/image.png)
 
 ### Estrategia de alistamiento
 
@@ -93,7 +93,7 @@ Haz clic en `Guardar` para registrar los cambios realizados.
 
 En esta sección puedes configurar el orden de las categorías en las que se alistarán los pedidos. De este modo, el alistador puede organizar el flujo de alistamiento de productos para completar los pedidos con eficacia.
 
-![pick-pack-categorias-es](//images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/2bfcf15ac98f4a83428b918bee4b609b/image.png)
+![pick-pack-categorias-es](https://images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/2bfcf15ac98f4a83428b918bee4b609b/image.png)
 
 * **Configuración rápida:** los ajustes se aplican en todas las instalaciones. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
 * **Instalación**: determina a qué instalación se aplicarán los ajustes de las categorías.
@@ -106,7 +106,7 @@ Puedes importar un archivo CSV o exportar la lista que ya está configurada.
 
 En esta sección se encuentran los ajustes relativos a la etapa de empaque de los ítems del pedido. 
 
-![pick-pack-empacotamento-es](//images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/22169dfbbb7de2d7cb7303533322b609/image.png)
+![pick-pack-empacotamento-es](https://images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/22169dfbbb7de2d7cb7303533322b609/image.png)
 
 * **Permitir informe de paquetes:** permite la visualización de informe de paquetes. El informe se mostrará en la pantalla **Pedidos**. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
 * **Permitir empaque automático:** permite el empaque automático. Puedes activar <i class="fas fa-toggle-on"></i> o desactivar <i class="fas fa-toggle-off"></i> esta opción.
@@ -174,7 +174,7 @@ Haz clic en `Guardar` para registrar los cambios realizados.
 
 En esta sección puedes configurar los ajustes relacionados con los pedidos procesados por VTEX Pick and Pack.
 
-![pick-pack-config-pedidos-es](//images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/0be9f8f989de78cff2f46369bd1aaa1d/image.png)
+![pick-pack-config-pedidos-es](https://images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/0be9f8f989de78cff2f46369bd1aaa1d/image.png)
 
 * **Descargar pedidos del OMS:** permite exportar pedidos desde el OMS.
 * **Medios de pago:** medios de pago utilizados en los pedidos a exportar.
@@ -188,7 +188,7 @@ Haz clic en `Guardar` para registrar los cambios realizados.
 
 En esta sección puedes configurar los ajustes de automatización de procesos de VTEX Pick and Pack.
 
-![pick-pack-automacao-es](//images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/4bb00e8ac0cbbf07c676b744771372d6/image.png)
+![pick-pack-automacao-es](https://images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/4bb00e8ac0cbbf07c676b744771372d6/image.png)
 
 Sigue los pasos a continuación para crear una nueva automatización:
 
@@ -200,7 +200,7 @@ Sigue los pasos a continuación para crear una nueva automatización:
 
 En esta sección puedes realizar la gestión de usuarios, admins y alistadores de tu operación en VTEX Pick and Pack. Los usuarios con el permiso **Admin** tendrán acceso al Admin VTEX y podrán realizar cambios en la herramienta. Los usuarios con el permiso **Alistador** solo tendrán acceso a la aplicación VTEX Pick and Pack. 
 
-![pick-pack-usuarios-es](//images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/cd858240c58bc74387f052d3fc7fd983/image.png)
+![pick-pack-usuarios-es](https://images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/cd858240c58bc74387f052d3fc7fd983/image.png)
 
 Para crear un nuevo usuario sigue los pasos a continuación:
 
@@ -210,7 +210,7 @@ Para crear un nuevo usuario sigue los pasos a continuación:
   - Permiso de __Admin__
     1. De la lista, selecciona al usuario que deseas registrar como Admin.
     2. Haz clic en Crear.
-    ![pick-pack-usuarios-2-es](//images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/17eeb5d76b1d00afcee928845e3ee0b8/image.png)
+    ![pick-pack-usuarios-2-es](https://images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/17eeb5d76b1d00afcee928845e3ee0b8/image.png)
   - Permiso de __Alistador__
     1. Rellena los siguientes campos del formulario:
        * Nombre de usuario
@@ -221,13 +221,13 @@ Para crear un nuevo usuario sigue los pasos a continuación:
        * Permitir el envío de paquetes
        * Categorías
     2. Haz clic en `Crear`.
-    ![pick-pack-usuarios-3-es](//images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/b5cac2035cbd75270e61a8dcbf7a32ae/image.png)
+    ![pick-pack-usuarios-3-es](https://images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/b5cac2035cbd75270e61a8dcbf7a32ae/image.png)
 
 ## Catálogo
 
 En esta sección puedes consultar la información de ítems de pedidos que se encuentran en la etapa de entrega al cliente.
 
-![pick-pack-catalogo-es](//images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/a7ba2ed1eb52f8e6f8ad1616679564b9/image.png)
+![pick-pack-catalogo-es](https://images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/a7ba2ed1eb52f8e6f8ad1616679564b9/image.png)
 
 La página presenta la siguiente información en forma de tabla:
 
@@ -260,7 +260,7 @@ También puedes indexar el catálogo para actualizar la lista de productos. Para
 
 En esta sección podrás agregar y consultar las instalaciones de tu tienda.
 
-![pick-pack-instalacoes-es](//images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/eb4cd39623ec2363f3c21a2624480fac/image.png)
+![pick-pack-instalacoes-es](https://images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/eb4cd39623ec2363f3c21a2624480fac/image.png)
 
 Para crear una nueva instalación sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-worksheets.md b/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
index b3754408e..5d2dfda98 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
@@ -27,11 +27,11 @@ Esta página te permite realizar las siguientes acciones:
 * [Buscar hoja de trabajo](#buscar-hoja-de-trabajo)
 * [Filtrar hojas de trabajo](#filtrar-hojas-de-trabajo)
 
-![pick-pack-ordem-servico-es](//images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/2f8d4456ad29068827c6eea06c74792a/image.png)
+![pick-pack-ordem-servico-es](https://images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/2f8d4456ad29068827c6eea06c74792a/image.png)
 
 Los pedidos se presentan en tarjetas que contienen la siguiente información:
 
-![pick-pack-ordem-servico-2-es](//images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/a1ae5432062574530f6cd465a35c752a/image.png)
+![pick-pack-ordem-servico-2-es](https://images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/a1ae5432062574530f6cd465a35c752a/image.png)
 
 * ID de la hoja de trabajo.
 * Número de pedidos en la hoja de trabajo.
@@ -49,7 +49,7 @@ Puedes crear una nueva hoja de trabajo siguiendo los pasos que se indican a cont
 3. Haz clic en la pestaña **Manual** para crear manualmente la hoja de trabajo.
 4. Haz clic en `+` para crear una hoja de trabajo. Puedes crear más de una hoja de trabajo.
 5. Arrastra los pedidos que desees a la hoja de trabajo.
-  ![pick-pack-ordem-servico-3-es](//images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/f828572d27ac5915b8561762e0be1210/image.png)
+  ![pick-pack-ordem-servico-3-es](https://images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/f828572d27ac5915b8561762e0be1210/image.png)
 6. Haz clic en `Crear` para finalizar.
 
 ## Consultar hojas de trabajo
@@ -64,7 +64,7 @@ Puedes optimizar la consulta de las hojas de trabajo desde las siguientes seccio
 
 También puedes acceder a más información sobre cada hoja de trabajo particular haciendo clic en el botón <i class="fas fa-chevron-down"></i> en la tarjeta.
 
-![pick-pack-ordem-servico-4-es](//images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/8070f319c3af85bbc61babfd5fb1014a/image.png)
+![pick-pack-ordem-servico-4-es](https://images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/8070f319c3af85bbc61babfd5fb1014a/image.png)
 
 ## Buscar hoja de trabajo
 
diff --git a/docs/tutorials/es/vtex-shipping-network-dashboard.md b/docs/tutorials/es/vtex-shipping-network-dashboard.md
index 96e835acc..da1f4fa64 100644
--- a/docs/tutorials/es/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/es/vtex-shipping-network-dashboard.md
@@ -59,7 +59,7 @@ En el cálculo del rendimiento, se consideran todos los paquetes que forman part
 
 El rendimiento es el resultado porcentual del cálculo entre la relación de paquetes entregados a tiempo y el total de paquetes entregados. Por lo tanto, el cálculo del rendimiento solo toma en cuenta los paquetes entregados. Veamos:
 
-![equation ES performance](//images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/a7c32e054f2b328ee9cbbf83a54a4c09/equation_ES_performance.gif)
+![equation ES performance](https://images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/a7c32e054f2b328ee9cbbf83a54a4c09/equation_ES_performance.gif)
 
  La herramienta de rendimiento de VTEX Shipping Network permite:
 
@@ -95,4 +95,4 @@ Puede descargar el informe con los datos de las transportadoras y las entregas d
 2. Espere hasta recibir la plantilla por email.
 3. Descargue la plantilla.
 
-![Resumo de performance ES](//images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/4d3875da23f323f9d03a5eb6139fd0c1/Resumo_de_performance_ES.png)
+![Resumo de performance ES](https://images.ctfassets.net/alneenqid6w5/7Ml4WafUUCfuL5zCQeICqk/4d3875da23f323f9d03a5eb6139fd0c1/Resumo_de_performance_ES.png)
diff --git a/docs/tutorials/es/vtex-status-page.md b/docs/tutorials/es/vtex-status-page.md
index d359b754b..bba43b9f2 100644
--- a/docs/tutorials/es/vtex-status-page.md
+++ b/docs/tutorials/es/vtex-status-page.md
@@ -19,7 +19,7 @@ La página [VTEX Status](https://status.vtex.com/) te permite monitorear la esta
 
 Nuestro equipo informa los eventos cada vez que nuestro sistema de monitoreo automático identifica una inestabilidad en los módulos de la plataforma. Cualquier mantenimiento programado también se comunica en detalle.
 
-![statuspage-1](//images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/59648457b075dea1768cb9c76f0be1f5/statuspage-1.png)
+![statuspage-1](https://images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/59648457b075dea1768cb9c76f0be1f5/statuspage-1.png)
 
 En este artículo, se describen los elementos de la página de status de la plataforma VTEX, desarrollada con la herramienta [incident.io](https://incident.io/):
 
@@ -41,7 +41,7 @@ El botón `Subscribe to updates` en la parte superior derecha de la página te d
 
 La opción de inscripción por email te permite decidir los componentes específicos para los que deseas recibir notificaciones. Solo tienes que marcar la opción **Subscribe to specific components** y, luego, los componentes que deseas monitorear.
 
-![statuspage-2](//images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/bfdc48e6aa471800a4655b4bea99f87e/statuspage-2.png)
+![statuspage-2](https://images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/bfdc48e6aa471800a4655b4bea99f87e/statuspage-2.png)
 
 ## Status general
 
@@ -49,23 +49,23 @@ Esta sección te permite ver el status general de la plataforma: fully operation
 
 Cuando algún problema o mantenimiento está afectando un componente, se indica dicho componente y se incluye una explicación del evento.  A continuación se muestran algunos ejemplos.
 
-![statuspage-3](//images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/889faae502219e1a0da31bdb3c2f00c6/statuspage-3.png)
+![statuspage-3](https://images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/889faae502219e1a0da31bdb3c2f00c6/statuspage-3.png)
 
-![statuspage-4](//images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/89ea44b8e93b93ed7d45fa19767de9eb/statuspage-4.png)
+![statuspage-4](https://images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/89ea44b8e93b93ed7d45fa19767de9eb/statuspage-4.png)
 
-![statuspage-5](//images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/38b3b92371b0a04090f912e2598c21a6/statuspage-5.png)
+![statuspage-5](https://images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/38b3b92371b0a04090f912e2598c21a6/statuspage-5.png)
 
 ## Status de los sistemas
 
 Esta sección te permite verificar en tiempo real el status de cada sistema de la plataforma y de sus componentes.
 
-![statuspage-6](//images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/1df94b99be002d4ecb574c9e4bb59d4c/statuspage-6.png)
+![statuspage-6](https://images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/1df94b99be002d4ecb574c9e4bb59d4c/statuspage-6.png)
 
 Al hacer clic en la flecha <i class="fas fa-chevron-down"></i> al lado del número de componentes, verás el status de los componentes específicos de cada sistema.
 
 Si se trata de un mantenimiento programado para una fecha futura, también verás el botón `Upcoming maintenance scheduled`, como se ilustra a continuación. Al pasar el mouse sobre el botón, se mostrará el evento de mantenimiento programado. Puedes hacer clic en el evento para ver su registro.
 
-![statuspage-7](//images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/ce633e4e4728d717c14c0f2daa1eddf8/statuspage-7.png)
+![statuspage-7](https://images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/ce633e4e4728d717c14c0f2daa1eddf8/statuspage-7.png)
 
 Los posibles status para cada componente son:
 
@@ -123,7 +123,7 @@ Para navegar a meses anteriores, haz clic en la flecha `<`.
 
 Para ver los eventos ocurridos en un día específico, pasa el mouse sobre la fecha. Para acceder a la página que contiene el registro completo del evento, haz clic en el incidente o el mantenimiento indicado en la fecha.
 
-![statuspage-8](//images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/0fff21b4393a61f149857c0bb353ef4a/statuspage-8.png)
+![statuspage-8](https://images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/0fff21b4393a61f149857c0bb353ef4a/statuspage-8.png)
 
 <div class="alert alert-warning">
   <p>Si un mantenimiento programado dura más de un día, solo se marcará la fecha de inicio en el calendario. Debes abrir el <a href="#registro-de-mantenimiento-programado">registro de mantenimiento</a> para ver la fecha de inicio y la fecha de fin.</p>
@@ -135,7 +135,7 @@ A continueación, describimos la información disponible en el registro del inci
 
 La página de detalles del incidente contiene la siguiente información:
 
-![status-page-9-es](//images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/7d7565c3a5baaf600033d9ad096bb0a2/status-page-9-es.png)
+![status-page-9-es](https://images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/7d7565c3a5baaf600033d9ad096bb0a2/status-page-9-es.png)
 
 * **Título:** título que describe el incidente.
 * **Status:** cada incidente tiene un ciclo definido en que nuestro equipo trabaja para identificar y solucionar los problemas. Las etapas del ciclo son:
@@ -164,6 +164,6 @@ El registro de mantenimiento programado muestra la misma información que el reg
 
 A continuación, se muestran ejemplos del status y la línea de tiempo de un mantenimiento programado.
 
-![statuspage-10](//images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/25713a87ae2dc76ac750dff3d5bc078b/statuspage-10.png)
+![statuspage-10](https://images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/25713a87ae2dc76ac750dff3d5bc078b/statuspage-10.png)
 
-![statuspage-11](//images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/c71e1785f62f7e32db69fc23eb951200/statuspage-11.png)
+![statuspage-11](https://images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/c71e1785f62f7e32db69fc23eb951200/statuspage-11.png)
diff --git a/docs/tutorials/es/warehouse.md b/docs/tutorials/es/warehouse.md
index 3fc536d8c..6fa067952 100644
--- a/docs/tutorials/es/warehouse.md
+++ b/docs/tutorials/es/warehouse.md
@@ -20,7 +20,7 @@ Para la plataforma VTEX, el almacén es la identificación del espacio de almace
 
 Es importante prestar atención a la etapa logística del almacén y al modo en que la configuración de la plataforma VTEX influye en la entrega de los pedidos. Del almacén salen los pedidos a los muelles, y en los muelles los recogen las transportadoras. 
 
-![EstrategiaEnvio_ES](//images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/ed9784e5cbc67a42358ad4f37c3baa00/Frame_2__2_.svg)
+![EstrategiaEnvio_ES](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/ed9784e5cbc67a42358ad4f37c3baa00/Frame_2__2_.svg)
 
 <div class="alert alert-info">
 La transportadora que llevará a cabo la entrega de un determinado pedido es definida por la <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">política de envío</a>. Para que una transportadora sea elegida para efectuar la entrega del pedido, es necesario que la política de envío de esa transportadora cumpla con las condiciones necesarias para la entrega del pedido. La política de envío está vinculada al almacén por el muelle.
diff --git a/docs/tutorials/es/web-application-firewall-waf.md b/docs/tutorials/es/web-application-firewall-waf.md
index 9802c8f0d..c990efe10 100644
--- a/docs/tutorials/es/web-application-firewall-waf.md
+++ b/docs/tutorials/es/web-application-firewall-waf.md
@@ -23,7 +23,7 @@ Web Application Firewall (WAF) es una capa de seguridad diseñada para proteger
 
 WAF se enfoca en las comunicaciones que se llevan a cabo a través de los protocolos HTTP (Hypertext Transfer Protocol) y HTTPS (HTTP Secure), analizando los datos de entrada y salida para detectar y bloquear posibles amenazas.
 
-![waf-es](//images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/c54a99dcdc86451d6cfcd72bc7b9cf07/waf-es.png)
+![waf-es](https://images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/c54a99dcdc86451d6cfcd72bc7b9cf07/waf-es.png)
 
 WAF opera a partir de la configuración de [reglas de seguridad](#reglas-de-seguridad) definidas por el equipo de seguridad de VTEX basándose en el análisis de patrones de circulación de datos. Dichas reglas sirven para que WAF monitoree constantemente el tráfico web y cuando detecte una actividad potencialmente perjudicial, pueda bloquear el tráfico, impidiendo que los atacantes aprovechen las vulnerabilidades en la aplicación web.
 
diff --git a/docs/tutorials/es/web-page-performance.md b/docs/tutorials/es/web-page-performance.md
index da26252a7..3c91d137b 100644
--- a/docs/tutorials/es/web-page-performance.md
+++ b/docs/tutorials/es/web-page-performance.md
@@ -25,7 +25,7 @@ El dashboard Rendimiento de las páginas web incorpora la herramienta [PageSpeed
 
 Aunque el _dashboard_ Rendimiento de las páginas web ofrece las mismas funcionalidades que PageSpeed Insights de Google, los comerciantes pueden agregar varias URL y hacerles un seguimiento constante únicamente en el Admin VTEX. 
 
-![Web page performance Dash ES](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
+![Web page performance Dash ES](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/32c901997b6a96b00b197ce99d2dd146/Screen_Shot_2022-06-29_at_15.47.04.png)
 
 ## ¿Por qué deberías hacer un seguimiento del rendimiento de una página web?
 
@@ -104,7 +104,7 @@ Ten en cuenta que no podrás eliminar las 10 páginas más visitadas de tu _ecom
 
 ## Métricas web principales
 
-![Core web vitals ES](//images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/16028a64c956d2461f1fc1f5c924beda/Screen_Shot_2022-06-29_at_15.47.45.png)
+![Core web vitals ES](https://images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/16028a64c956d2461f1fc1f5c924beda/Screen_Shot_2022-06-29_at_15.47.45.png)
 
 Para cada URL, la página Rendimiento de las páginas web muestra la puntuación de las [Métricas web principales de Google](https://web.dev/vitals/#core-web-vitals) para esa página web. 
 
diff --git a/docs/tutorials/es/welcome-message-control.md b/docs/tutorials/es/welcome-message-control.md
index 8c7479638..5ccc7d89c 100644
--- a/docs/tutorials/es/welcome-message-control.md
+++ b/docs/tutorials/es/welcome-message-control.md
@@ -19,7 +19,7 @@ El control `<vtex.cmc:welcomeMessage/>` renderiza un mensaje de bienvenida, que
 
 Vea un ejemplo en la siguiente imagen.
 
-![welcome1](//images.contentful.com/alneenqid6w5/2z4iyUDAm0muKc4OCOUOa2/9e6f37d39596161bfe1721effdceb692/welcome1.png)
+![welcome1](https://images.contentful.com/alneenqid6w5/2z4iyUDAm0muKc4OCOUOa2/9e6f37d39596161bfe1721effdceb692/welcome1.png)
 
 ## Código HTML renderizado
 
diff --git a/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md b/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
index 0ac209ab3..f8d77bd50 100644
--- a/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
+++ b/docs/tutorials/es/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
@@ -19,7 +19,7 @@ Al acceder la sección __Todos los pedidos__, en __Gestión de pedidos__, es pos
 
 La columna __Origin__ indica de dónde proviene los pedidos, distinguiéndo ellos entre en dos posibles orígenes: __Marketplace__ y __Fulfillment__.
 
-![orders-list-origin-es](//images.ctfassets.net/alneenqid6w5/1rflCsjI1vIGnb7juYOJJa/8e060cea0849e422a060526bf2fe81e2/oders-list-origin-es.png)
+![orders-list-origin-es](https://images.ctfassets.net/alneenqid6w5/1rflCsjI1vIGnb7juYOJJa/8e060cea0849e422a060526bf2fe81e2/oders-list-origin-es.png)
 
 ## Marketplace
 
diff --git a/docs/tutorials/es/what-are-shelves.md b/docs/tutorials/es/what-are-shelves.md
index 39829f022..d6c806a4a 100644
--- a/docs/tutorials/es/what-are-shelves.md
+++ b/docs/tutorials/es/what-are-shelves.md
@@ -23,7 +23,7 @@ Estantes son elementos configurables que muestran una agrupación de productos e
 
 Los estantes se estructuran a partir de código HTML, organizados en [templates](/es/tutorial/que-son-templates) específicos, llamados Templates de Estante ("__Shelves Templates__"). Se encuentran en la carpeta **CMS**, en el [módulo Layout](/es/faq/que-es-el-cms). Es en esta carpeta que usted podrá crear nuevos templates y editar los que ya existen.
 
-![Shelves Templates](//images.contentful.com/alneenqid6w5/4pIuR3BWKQisWuos4gcCWS/ade52c1df88c9e371169df99776b0779/Shelves_Template-min.png)
+![Shelves Templates](https://images.contentful.com/alneenqid6w5/4pIuR3BWKQisWuos4gcCWS/ade52c1df88c9e371169df99776b0779/Shelves_Template-min.png)
 
 Por ser un elemento que puede ser utilizado en más de una página, este tipo especial de template (Template de Estante) se almacena en carpetas diferentes de los otros tipos (HTML Templates y Sub Templates). Así, es posible mantener la organización de los archivos y, consecuentemente, del código de su web site.
 
diff --git a/docs/tutorials/es/what-are-templates.md b/docs/tutorials/es/what-are-templates.md
index 7f27165e6..949292530 100644
--- a/docs/tutorials/es/what-are-templates.md
+++ b/docs/tutorials/es/what-are-templates.md
@@ -32,7 +32,7 @@ Además de estos dos tipos básicos, todavía hay una subdivisión de los __temp
 
 Y hablando en organización, usted encuentra todos los templates en el **Storefront > Layout > CMS**, reunidos en carpetas de acuerdo a su tipo (HTML o Shelves). Los __Sub Templates__ están en la carpeta del mismo nombre, que se encuentra dentro del directorio __HTML Templates__. En estos lugares, usted podrá crear nuevos templates y editar los que ya existen.
 
-![cms](//images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
+![cms](https://images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
 
 ### Artículos relacionados
 - [¿Qué es el CMS?](/es/tutorial/que-es-el-cms)
diff --git a/docs/tutorials/es/what-are-the-internal-utms.md b/docs/tutorials/es/what-are-the-internal-utms.md
index 40cf97968..02b0268c0 100644
--- a/docs/tutorials/es/what-are-the-internal-utms.md
+++ b/docs/tutorials/es/what-are-the-internal-utms.md
@@ -19,11 +19,11 @@ Las `UTMi`s son UTMs internas, es decir, parámetros de URL que tienen el objeti
 
 Por lo tanto, no tienen el objetivo de rastrear el tráfico que viene de sitios o servicios externos, con propósitos relacionados con el contexto de marketing. Esta es una función ejercida por las UTMs, como se explica en el artículo [Qué son utm_source, utm_campaign y utm_medium](/es/faq/que-son-utm-source-utm-campaign-y-utm-medium).
 
-Normalmente, las UTMs internas se utilizan como __causa de promoción__. En el módulo Tasas y Promociones, usted puede definir que sólo los pedidos cerrados con determinada UTM aplicada en la URL recibirán la promoción. Vea abajo el campo para elegir o crear esta UTM interna en el registro de una promoción regular.![utmi1](//images.contentful.com/alneenqid6w5/16CfZDMc1A2IiiU2UcayS2/aaf51be21c48ee58b10066e7cb70c063/utmi1.jpg)
+Normalmente, las UTMs internas se utilizan como __causa de promoción__. En el módulo Tasas y Promociones, usted puede definir que sólo los pedidos cerrados con determinada UTM aplicada en la URL recibirán la promoción. Vea abajo el campo para elegir o crear esta UTM interna en el registro de una promoción regular.![utmi1](https://images.contentful.com/alneenqid6w5/16CfZDMc1A2IiiU2UcayS2/aaf51be21c48ee58b10066e7cb70c063/utmi1.jpg)
 
 En el modulo Gestión de Pedidos, dentro de la pantalla de detalles del pedido, usted puede girar la carta de Valor Total para ver los datos de __Promociones y Marketing__. En él figura el valor del parámetro de la UTM interna usada en la promoción.
 
-![utmi2](//images.contentful.com/alneenqid6w5/41RwzsUqdOYWaYAokS6YiC/5774226a9a53769566cdefbcb2c0b171/utmi2.jpg)
+![utmi2](https://images.contentful.com/alneenqid6w5/41RwzsUqdOYWaYAokS6YiC/5774226a9a53769566cdefbcb2c0b171/utmi2.jpg)
 
 VTEX trabaja con tres tipos de UTMs internas:
 - `utmi_cp`
diff --git a/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md b/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
index e586c22ef..db152fa55 100644
--- a/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
+++ b/docs/tutorials/es/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
@@ -24,4 +24,4 @@ Al configurar una promoción **Comprar y obtener**, es posible **Activar multipl
 Para ambos escenarios, se necesita rellenar la cantidad máxima de seleccionable. Con el multiplicador de regalos **activado**, determine la **cantidad máxima** de regalos para la condición. Para el multiplicador de regalos **desactivado**, la cantidad es **siempre 1**.
 
 
-![ativar-multiplicador-brinde es](//images.ctfassets.net/alneenqid6w5/23jsNGW0DCc6CEmgGYmOms/ad3128579334e186a434b21b04455ee6/gift_multi_es.png)
+![ativar-multiplicador-brinde es](https://images.ctfassets.net/alneenqid6w5/23jsNGW0DCc6CEmgGYmOms/ad3128579334e186a434b21b04455ee6/gift_multi_es.png)
diff --git a/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md b/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
index 57f42977c..b08be812b 100644
--- a/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
+++ b/docs/tutorials/es/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
@@ -33,7 +33,7 @@ Para saber cómo acceder a los pedidos que se consideraron en el cálculo de los
 Para facilitar su visualización, todos los pedidos aprobados financieramente estarán marcados de esta forma, que se puede ver en el módulo de gestión de pedidos. 
 
 
-![image (4)](//images.ctfassets.net/alneenqid6w5/6HOwNB7DXzMr3pCPmeZkGS/4088a657730d190f8e4e2388295fd827/image__4_.png)
+![image (4)](https://images.ctfassets.net/alneenqid6w5/6HOwNB7DXzMr3pCPmeZkGS/4088a657730d190f8e4e2388295fd827/image__4_.png)
 
 
 Para acceder al módulo, realice el siguiente procedimiento:
diff --git a/docs/tutorials/es/what-is-a-franchise-account.md b/docs/tutorials/es/what-is-a-franchise-account.md
index 8901e3521..bdf19f2d4 100644
--- a/docs/tutorials/es/what-is-a-franchise-account.md
+++ b/docs/tutorials/es/what-is-a-franchise-account.md
@@ -19,7 +19,7 @@ En la plataforma VTEX, tienes la opción de registrar tiendas físicas, franquic
 
 La cuenta franquicia está asociada a una cuenta principal. En el caso de una marca que tenga varias tiendas físicas, franquiciados o representantes, cada uno de ellos puede tener una cuenta franquicia vinculada a la cuenta principal de la marca. Esto les permite entregar los productos vendidos por el ecommerce de la marca.
 
-![diagrama contas v2 - es](//images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/38f2bac55f9150f6049aaa20193aa97e/diagrama_contas_v2_-_es.png)
+![diagrama contas v2 - es](https://images.ctfassets.net/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/38f2bac55f9150f6049aaa20193aa97e/diagrama_contas_v2_-_es.png)
 
 En este artículo, trataremos los siguientes temas:
 
@@ -38,7 +38,7 @@ Además, utilizando la cuenta franquicia, puedes gestionar precios y medios de p
 
 Una cuenta franquicia no tiene su propio sitio web. Los consumidores navegan directamente en el sitio web de la cuenta principal, que funciona como un _marketplace_ en esta situación. Los datos de los clientes se almacenan en el Master Data de la cuenta principal.
 
-![diagrama admin contas - es](//images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/b30710b00e3a9a898fe2cd1fb5dd96c5/diagrama_admin_contas_-_es.png)
+![diagrama admin contas - es](https://images.ctfassets.net/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/b30710b00e3a9a898fe2cd1fb5dd96c5/diagrama_admin_contas_-_es.png)
 
 ## Relación entre la cuenta franquicia y el _Seller White Label_
 
diff --git a/docs/tutorials/es/what-is-binding.md b/docs/tutorials/es/what-is-binding.md
index 56755c9ca..6eb532695 100644
--- a/docs/tutorials/es/what-is-binding.md
+++ b/docs/tutorials/es/what-is-binding.md
@@ -19,7 +19,7 @@ Website binding es lo que hace el puente entre el CMS (Portal) y la información
 
 Es decir, es lo que define que un __account name__ (configurado en el License Manager) está vinculado a la estructura de carpetas y archivos de determinado __Website__ (construido en el CMS).
 
-![Binding](//images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
+![Binding](https://images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
 
 Esta es la configuración realizada cuando una cuenta desea tener más de una tienda. Para cada una de esas tiendas (que llamamos [multitiendas](/es/tutorial/como-crear-multiloja-multidominio)), se hace un binding.
 
diff --git a/docs/tutorials/es/what-is-cms-layout.md b/docs/tutorials/es/what-is-cms-layout.md
index 32245a900..beecb698d 100644
--- a/docs/tutorials/es/what-is-cms-layout.md
+++ b/docs/tutorials/es/what-is-cms-layout.md
@@ -36,7 +36,7 @@ Antes de comenzar a organizar el contenido de su Web Site, este Web Site debe es
 
 Este es un proceso fundamental para el perfecto funcionamiento de su tienda, pero también es muy simple. Sólo tienes que seguir los pasos [de este artículo](/es/tutorial/vincular-un-account-name-a-un-website-binding).
 
-![Binding](//images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
+![Binding](https://images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
 
 ## Layouts y templates
 
diff --git a/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md b/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md
index bbbe6e302..44c427767 100644
--- a/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md
+++ b/docs/tutorials/es/what-is-the-difference-between-inventory-and-warehouse-dock.md
@@ -25,7 +25,7 @@ __Las tres etapas de la logística se representan por la siguiente estructura: _
 
 __Pueden ser ilustradas por el flujo abajo: __
 
-![ES Conceitos Logistics](//images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/b610da20dede4d2536abe9b3a7f07890/ES_Conceitos_Logistics.png)
+![ES Conceitos Logistics](https://images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/b610da20dede4d2536abe9b3a7f07890/ES_Conceitos_Logistics.png)
 
 ## Almacene
 Es el espacio físico utilizado para el almacenamiento de los productos de un e-commerce, funcionando como el repositorio de los ítems de su tienda.
diff --git a/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
index 408bcd8f9..fa1dbf2d1 100644
--- a/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
@@ -35,7 +35,7 @@ Estos tipos son:
 
 Para crear una tag de control personalizado, basta hacer clic en __Add__, registrar un nombre y una tag, luego seleccionar el tipo.
 
-![cms-custom-elements EN / ES](//images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
+![cms-custom-elements EN / ES](https://images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
 
 <div class="alert alert-warning">
   <p><b>Atención:</b> no cree un control del tipo HTML con un elemento <code>title</code>. Esto puede interferir con el buen funcionamiento de su tienda.</p>
diff --git a/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md b/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md
index 92258dee6..a83a66b35 100644
--- a/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md
+++ b/docs/tutorials/es/what-to-do-when-my-report-does-not-reach-my-inbox.md
@@ -24,7 +24,7 @@ Pero existe una manera de extraer manualmente este informe accediendo al Master
 A continuación, entienda el paso a paso para hacerlo:
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
-2. Haga clic en __Exportaciones__. ![exportaciones-md](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/b47b9d6d497864bf45547f77c3bdd927/exportaciones.png)
+2. Haga clic en __Exportaciones__. ![exportaciones-md](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/b47b9d6d497864bf45547f77c3bdd927/exportaciones.png)
 3. Asegúrese de que la pestaña abierta es la de __Aplicaciones__.
 4. En __Status de las exportaciones__, identifique la línea del informe que desea descargar.
 5. Si el __Status__ es __Realizado - Descargar__, haga clic en **Descargar** para descargar el archivo.
diff --git a/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md b/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md
index c38251318..8208ff529 100644
--- a/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md
+++ b/docs/tutorials/es/whatsapp-ai-campaigns-management-and-details.md
@@ -80,7 +80,7 @@ Para pausar el envío de mensajes de una campaña:
 
 Puedes encontrar información sobre tus campañas en curso en el Admin VTEX.
 
-![Visão geral-ES](//images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/27df78b45cdda1fd0aa89bde051172a3/Vis_o_geral-ES.png)
+![Visão geral-ES](https://images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/27df78b45cdda1fd0aa89bde051172a3/Vis_o_geral-ES.png)
 
 A continuación se detallan las métricas disponibles:
 
diff --git a/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md b/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md
index 3c56714c6..69ff3ddf1 100644
--- a/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md
+++ b/docs/tutorials/es/where-do-i-see-clients-that-use-recurrence.md
@@ -22,4 +22,4 @@ Pero recuerde: la suscripción sólo aparece en las propiedades después de que
 1. Acceda al __Gestión de Pedidos__.
 2. Haga clic en la pestaña __Assinaturas__.
 
-![subscription ES](//images.ctfassets.net/alneenqid6w5/2ujHgxMGUwiuWCq4kaKc4C/def14c61a1d2f5ec940db40a6062a540/subscription_ES.png)
+![subscription ES](https://images.ctfassets.net/alneenqid6w5/2ujHgxMGUwiuWCq4kaKc4C/def14c61a1d2f5ec940db40a6062a540/subscription_ES.png)
diff --git a/docs/tutorials/es/where-do-i-see-the-payment-capture-date.md b/docs/tutorials/es/where-do-i-see-the-payment-capture-date.md
index 8f02863ae..a7113f6ab 100644
--- a/docs/tutorials/es/where-do-i-see-the-payment-capture-date.md
+++ b/docs/tutorials/es/where-do-i-see-the-payment-capture-date.md
@@ -23,4 +23,4 @@ Sólo tiene que seguir los pasos abajo:
 2. Busque la transacción deseada y haga clic en ella.
 3. En los __Eventos de la transacción__, busque el evento de captura ("settlement"):
 
-![settlementEvent](//images.contentful.com/alneenqid6w5/2svl4ROF5OoG4G62QeQaAg/8f45a34ccbe4c03a178a89bcd8468957/settlementEvent.png)
+![settlementEvent](https://images.contentful.com/alneenqid6w5/2svl4ROF5OoG4G62QeQaAg/8f45a34ccbe4c03a178a89bcd8468957/settlementEvent.png)
diff --git a/docs/tutorials/es/white-label-sellers-selection.md b/docs/tutorials/es/white-label-sellers-selection.md
index 6e565b270..1c613de59 100644
--- a/docs/tutorials/es/white-label-sellers-selection.md
+++ b/docs/tutorials/es/white-label-sellers-selection.md
@@ -112,13 +112,13 @@ Si hay un empate entre los _sellers_ con los criterios de menor costo o mejor pl
 
 Un cliente agregó cinco SKU al carrito. Cada uno de los _sellers_ que ofrece la opción de entrega en su región (_sellers_ A, B, C y D) tiene en su [inventario](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) solo una parte de los _ítems_, tal como se muestra en la imagen a continuación:
 
-![print_selecao_seller_white_label_1](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
+![print_selecao_seller_white_label_1](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
 
 La plataforma VTEX selecciona al _seller_ que tiene disponible en su _stock_ el número máximo de SKU del carrito. En este caso, el _seller_ B es el único que entrega tres SKU. 
 
 Luego de seleccionar al _seller_ B, aún quedan dos SKU sin entregar. Si un único _seller_ enviara ambos, ese sería el factor decisivo para la selección, ya que el objetivo es reunir la menor cantidad de _sellers_ para cubrir el carrito. Sin embargo, y de acuerdo con la imagen a continuación, se necesitan a los _sellers_ A y C para entregar los SKU 1 y 4:
 
-![print_selecao_seller_white_label_2](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
+![print_selecao_seller_white_label_2](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
 
 En la primera imagen, el _seller_ C podía entregar los SKU 3 y 4, y el _seller_ D entregaría el SKU 5. No obstante, se seleccionó al _seller_ B para entregar esos _ítems_, entonces, no se tienen en cuenta esos SKU en las otras etapas de selección. Esto se representó eliminando la flecha del _seller_ C hacia el SKU 3, y la flecha del _seller_ D hacia el SKU 5.
 
@@ -128,7 +128,7 @@ El resultado de la selección para la entrega es una combinación entre los _sel
 
 Un cliente agregó cinco SKU al carrito y hay cuatro _sellers_ (A, B, C y D) que entregan los pedidos en su región. Ninguno de ellos tiene en su [inventario](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) todos los _ítems_, tal como se muestra en la imagen a continuación:
 
-![print_selecao_seller_white_label_3](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
 
 La plataforma VTEX selecciona al _seller_ que tiene disponible en su _stock_ el mayor número de los SKU del carrito. Tanto el _seller_ B como el _seller_ D pueden entregar tres _ítems_, y como ambos entregan el SKU 3, compiten entre ellos.
 
@@ -141,11 +141,11 @@ Supongamos que el _seller_ B tiene la entrega más económica, y que el _seller_
 
 - **Entrega más rápida:** cuando se selecciona al _seller_ D, quedan sin entregar los SKU 3 y 4. El _seller_ C puede entregar ambos, por lo que resulta elegido y el resultado de la selección es la combinación de los _sellers_ D y C.
 
-![print_selecao_seller_white_label_4](//images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
+![print_selecao_seller_white_label_4](https://images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
 
 - **Entrega más económica:** cuando se selecciona al _seller_ B, quedan sin entregar los SKU 1 y 4. Como solo el _seller_ A entrega el SKU 1, y solo el _seller_ C entrega el SKU 4, el resultado de la selección es una combinación de los _sellers_ A, B y C. 
 
-![print_selecao_seller_white_label_5](//images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
+![print_selecao_seller_white_label_5](https://images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
 
 Las flechas repetidas de los _sellers_ que entregaban los SKU ya cubiertos por los _sellers_ B y D se eliminaron de las imágenes que contemplaban las opciones de entrega más económica y más rápida. Esto se debe a que en las etapas de selección sucesivas, los SKU ya cubiertos no se tienen en cuenta.
 
diff --git a/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index b6d4ce5b1..a8b5bab15 100644
--- a/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -37,7 +37,7 @@ Siga estos pasos para validar la información:
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
 2. En el cuadro __Profile System__, haga clic en __Clientes__.
-3. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+3. Seleccione la opción __E-mail__ y busque el correo electrónico del cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 4. Haga clic en el registro del cliente para acceder a los detalles del perfil.
 
 En la sección __Contato__, usted verá que la opción `Es Empresa?` Se llena con el valor `No`. Al mismo tiempo, en la sección __Datos de la empresa__, usted verá que el campo `Tipo documento` tiene el valor `cnpj`.
diff --git a/docs/tutorials/es/wow-to-integrate-with-multiplus.md b/docs/tutorials/es/wow-to-integrate-with-multiplus.md
index adaf0f87d..6924c6f63 100644
--- a/docs/tutorials/es/wow-to-integrate-with-multiplus.md
+++ b/docs/tutorials/es/wow-to-integrate-with-multiplus.md
@@ -28,7 +28,7 @@ Una alternativa para los pasos precedentes es acceder al panel de configuración
 
 Sustituya {NOMBREDELATIENDA} por el Account Name de su tienda.
 
-![Multiplus1](//images.contentful.com/alneenqid6w5/2NxVrnsnZCOuQOqEOIusOq/d5cd381241a842c29e81763ea6f8f506/Multiplus1.png)
+![Multiplus1](https://images.contentful.com/alneenqid6w5/2NxVrnsnZCOuQOqEOIusOq/d5cd381241a842c29e81763ea6f8f506/Multiplus1.png)
 
 Tras hacer clic en **Integrar**, se abrirá un formulario con algunos campos a llenar. Preste atención a los campos obligatorios: son aquéllos en los que aparece un “\*” al lado de la caja de texto.
 
@@ -41,7 +41,7 @@ Tras hacer clic en **Integrar**, se abrirá un formulario con algunos campos a l
 - **Código Aliado que será utilizado en Multiplus**: Este código debe contener de 1 a 30 dígitos, de su elección. Para habilitar sus ventas, usted deberá informar ese código a Multiplus después de realizar la configuración en el Bridge. En el caso de que usted modifique ese código, el nuevo también deberá ser informado a Multiplus, a fin de que sea hecha la actualización. Si esto no ocurre, la tienda quedará impedida de realizar ventas;
 - **Emails para la creación del Afiliado**: Después que sea guardada la configuración, la integración creará el Afiliado en VTEX e insertará esa información en el registro.
 
-![Multiplus2](//images.contentful.com/alneenqid6w5/4lTWbmFiGcOoIkUK8KSIAm/501d2f8e79300fc814d08ac600d7b0be/Multiplus2.png)
+![Multiplus2](https://images.contentful.com/alneenqid6w5/4lTWbmFiGcOoIkUK8KSIAm/501d2f8e79300fc814d08ac600d7b0be/Multiplus2.png)
 
 
 Tras estar llenada la información, haga clic en **Salvar** y espere que aparezca el mensaje de éxito.
diff --git a/docs/tutorials/pt/accessing-a-client-abandoned-cart.md b/docs/tutorials/pt/accessing-a-client-abandoned-cart.md
index a35f7a64e..cd34967e4 100644
--- a/docs/tutorials/pt/accessing-a-client-abandoned-cart.md
+++ b/docs/tutorials/pt/accessing-a-client-abandoned-cart.md
@@ -29,26 +29,26 @@ Visualizar esses campos é bem simples. Uma vez logado no Admin da sua loja, bas
 
 1. Clique em __Master Data__
 
-  ![Carrinho Abandonado - 1 - PT](//images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/deed48c41ae2ab64a4aa53c1b53d1962/4GdZSkwtm9f76BIVFnC65D_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 1 - PT](https://images.ctfassets.net/alneenqid6w5/4GdZSkwtm9f76BIVFnC65D/deed48c41ae2ab64a4aa53c1b53d1962/4GdZSkwtm9f76BIVFnC65D_Masterdata_PT.jpg)
 
 2. Clique no ícone de Configurações (engrenagem) de __Profile System__
 
-  ![Carrinho Abandonado - 2 - PT](//images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/e7911e88ba6acba63e50fc8689e25c09/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
+  ![Carrinho Abandonado - 2 - PT](https://images.ctfassets.net/alneenqid6w5/2lT6TyHXyqprOVrVWKcrXL/e7911e88ba6acba63e50fc8689e25c09/2lT6TyHXyqprOVrVWKcrXL_Masterdata.jpg)
 
 3. Certifique-se que você está na aba __Aplicações__
 
-  ![Carrinho Abandonado - 3 - PT](//images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/48cf309c46a6484afaa40896e519e5ee/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
+  ![Carrinho Abandonado - 3 - PT](https://images.ctfassets.net/alneenqid6w5/7uNmvjaX9n2fEyS6qrqBs5/48cf309c46a6484afaa40896e519e5ee/7uNmvjaX9n2fEyS6qrqBs5_Masterdata.jpg)
 
 4. Acesse Editar (Lápis) na categoria __Clientes__ 
 
-  ![Carrinho Abandonado - 4 - PT](//images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/20e963f2ee94ba72e2124b063b9a7a02/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
+  ![Carrinho Abandonado - 4 - PT](https://images.ctfassets.net/alneenqid6w5/3ea3rmBM3CGMla7fngViDb/20e963f2ee94ba72e2124b063b9a7a02/3ea3rmBM3CGMla7fngViDb_Masterdata.jpg)
 
 5. Selecione as opções __“Último carrinho”__ e __“Carrinho”__ dentre as opções de __Campos de Listagens__
 
-  ![Carrinho Abandonado - 5 - PT](//images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/fc241bda582d78cd43bda4b7384976ca/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
+  ![Carrinho Abandonado - 5 - PT](https://images.ctfassets.net/alneenqid6w5/1jjfpJH15yyTILbKIJqVaH/fc241bda582d78cd43bda4b7384976ca/1jjfpJH15yyTILbKIJqVaH_Masterdata_PT.jpg)
 
 6. Clique em __Salvar__
 
-  ![Carrinho Abandonado - 6 - PT](//images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/7bc0ae209e1075586c29571998b23e5a/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
+  ![Carrinho Abandonado - 6 - PT](https://images.ctfassets.net/alneenqid6w5/5NUGVb2W2Jq98vbJgF1UcN/7bc0ae209e1075586c29571998b23e5a/5NUGVb2W2Jq98vbJgF1UcN_Masterdata.jpg)
 
 Assim, você poderá conferir os parâmetros do carrinhos abandonados de seus clientes.
diff --git a/docs/tutorials/pt/account-management.md b/docs/tutorials/pt/account-management.md
index b02d942f7..8ab57771b 100644
--- a/docs/tutorials/pt/account-management.md
+++ b/docs/tutorials/pt/account-management.md
@@ -84,7 +84,7 @@ Depois que um usuário preenche e salva **Nome** e **E-mail**, nos campos de co
 O template deste e-mail automático pode ser alterado na <a href="https://help.vtex.com/pt/tutorial/understanding-the-message-center--tutorials_84">Central de mensagens</a> modificando o template <i>account registration</i>.
 </div>
 
-![cadastro de conta](//images.ctfassets.net/alneenqid6w5/5tBCNxqBxeWkqOgiIcEaQw/4e044e1f46911db85da4e5ea0a195226/cadastro_de_conta.jpg)
+![cadastro de conta](https://images.ctfassets.net/alneenqid6w5/5tBCNxqBxeWkqOgiIcEaQw/4e044e1f46911db85da4e5ea0a195226/cadastro_de_conta.jpg)
 
 ## Segurança
 
diff --git a/docs/tutorials/pt/account-settings-overview.md b/docs/tutorials/pt/account-settings-overview.md
index eb61ff971..06f21d5e8 100644
--- a/docs/tutorials/pt/account-settings-overview.md
+++ b/docs/tutorials/pt/account-settings-overview.md
@@ -20,7 +20,7 @@ Todo contratante da VTEX recebe uma conta que dá acesso ao Admin, onde é poss
 Nas **Configurações da conta,** é possível controlar  o acesso ao Admin e alterar outras configurações relacionadas à conta, como editar informações de contato e vincular lojas à sua conta.
 
 Para acessar as _Configurações da conta_, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e clique no botão **Configurações da conta**.  
-![Admin v4 account settings menu PT](//images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/09a38ba629307a07ac8a37bb79d8c812/Admin_v4_account_settings_menu_PT.jpg)
+![Admin v4 account settings menu PT](https://images.ctfassets.net/alneenqid6w5/gMscIoImNJt51634ZQsRD/09a38ba629307a07ac8a37bb79d8c812/Admin_v4_account_settings_menu_PT.jpg)
 
 A seção inclui as seguintes páginas, em breve no design do Admin v4.
 
diff --git a/docs/tutorials/pt/account-summary.md b/docs/tutorials/pt/account-summary.md
index e8f805c92..39ced09d2 100644
--- a/docs/tutorials/pt/account-summary.md
+++ b/docs/tutorials/pt/account-summary.md
@@ -36,23 +36,23 @@ Por fim, o lojista pode conferir os próximos recebíveis e suas últimas movime
 
 Esta seção é dividida em duas partes: a de recebíveis consolidados - para recebimentos já liquidados - e a de lançamentos futuros, para compras que ainda serão liquidadas. 
 
-![extrato_financeiro_vtex_payment](//images.ctfassets.net/alneenqid6w5/ylj1J2TQfTs24IyrxKJrI/884f3d2ad018b1d2888465818565a2f8/image.png)
+![extrato_financeiro_vtex_payment](https://images.ctfassets.net/alneenqid6w5/ylj1J2TQfTs24IyrxKJrI/884f3d2ad018b1d2888465818565a2f8/image.png)
 
 Vale ressaltar que a aba Lançamentos Futuros oferece a conciliação entre os recebíveis e seus respectivos pedidos. Caso o lojista clique em um dos recebimentos, uma tela contendo todas as transações referentes àquela movimentação financeira será exibida. 
 
-![tela_extrato-financeiro](//images.ctfassets.net/alneenqid6w5/5vpMPvl2dz4fT8OvgjYrAC/a9a8e07e94b40dffd714c3b317d35111/image.png)
+![tela_extrato-financeiro](https://images.ctfassets.net/alneenqid6w5/5vpMPvl2dz4fT8OvgjYrAC/a9a8e07e94b40dffd714c3b317d35111/image.png)
 
 Além disso, para consultar os detalhes do pedido que compõe a transação, basta clicar na linha correspondente. Assim, a tela apresentará dados como: produto vendido, data e número de parcelas, por exemplo.
 
-![tela_extrato_financeiro](//images.ctfassets.net/alneenqid6w5/3OjfgHkS4kMDX7zEhoaHMF/27d2fabc1014e9371475b8aea1c0f2ba/image.png)
+![tela_extrato_financeiro](https://images.ctfassets.net/alneenqid6w5/3OjfgHkS4kMDX7zEhoaHMF/27d2fabc1014e9371475b8aea1c0f2ba/image.png)
 
 O lojista pode ainda consultar o pedido diretamente no módulo Gerenciamento de Pedidos, caso clique em "Ver detalhes do pedido".
 
-![items_pedido](//images.ctfassets.net/alneenqid6w5/1IiebFvYL9GfppgW77E6op/0df3ba415c65662c08d6ff329970555b/image.png)
+![items_pedido](https://images.ctfassets.net/alneenqid6w5/1IiebFvYL9GfppgW77E6op/0df3ba415c65662c08d6ff329970555b/image.png)
 
 Por fim, ainda nessa tela, o lojista pode baixar dois relatórios: extrato financeiro e recebimentos de vendas. Para isso, basta clicar no botão "Exportar", selecionar o documento e o mês desejado.
 
-![image](//images.ctfassets.net/alneenqid6w5/I8zH7rdrRmiDoFYzSEgMh/5bcc566709369dc12904e7e95c31a725/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/I8zH7rdrRmiDoFYzSEgMh/5bcc566709369dc12904e7e95c31a725/image.png)
 
 Os dados são:
 
@@ -65,13 +65,13 @@ Por mais que em “Resumo de Contas” a plataforma apresente uma pequena sínte
 
 Ao clicar nessa seção, o lojista pode conferir suas disputas em aberto. Contudo, ao clicar em uma transação específica, a plataforma o direciona para uma página que mostra o extrato do pedido.
 
-![tela_disputas](//images.ctfassets.net/alneenqid6w5/1SdbVyFFMPrsn5IvCeGK7T/aa82183f3bfadbd9aa5a450cf903512c/image.png)
+![tela_disputas](https://images.ctfassets.net/alneenqid6w5/1SdbVyFFMPrsn5IvCeGK7T/aa82183f3bfadbd9aa5a450cf903512c/image.png)
 
 São quatro quadros que detalham o recebível em disputa. Em “Transação”, o lojista confere os dados da compra. Assim como acessa a descrição do pedido em si no quadro logo abaixo, “Itens do Pedido”.
 
 Do lado esquerdo, temos os quadros “Recebíveis”, que apresentam os detalhes das parcelas daquela transação, e “Valor Total”. Este último detalha o histórico, assim como a soma de todos os recebíveis que compõem o pedido.
 
-![disputa_extrato](//images.ctfassets.net/alneenqid6w5/7x3zwBsaDR6VEItmoSzWhy/21b909bf626e7a1e17c97d32957cf86f/image.png)
+![disputa_extrato](https://images.ctfassets.net/alneenqid6w5/7x3zwBsaDR6VEItmoSzWhy/21b909bf626e7a1e17c97d32957cf86f/image.png)
 
 ## Antecipação avulsa de recebíveis
 
diff --git a/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md b/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md
index 5dea36bbe..3eadd730b 100644
--- a/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md
+++ b/docs/tutorials/pt/activating-the-complete-list-link-on-the-category-menu.md
@@ -20,7 +20,7 @@ O link de **Lista Completa** no menu de categorias é muito usado em lojas que
 
 Como, por exemplo, no caso abaixo, o "Departamento 2" :
 
-![categoria.pt](//images.ctfassets.net/alneenqid6w5/Z4sxAcNhnYK8zHQ46Viti/809614206fc51a87a108432c546ce5a3/categoria.pt.png)
+![categoria.pt](https://images.ctfassets.net/alneenqid6w5/Z4sxAcNhnYK8zHQ46Viti/809614206fc51a87a108432c546ce5a3/categoria.pt.png)
 
 De todas as categorias, a loja preferiu exibir no menu somente algumas.
 
@@ -29,5 +29,5 @@ Esta configuração é feita no cadastro de categoria, na opção **Menu com lin
 - Se tiver marcada, a categoria aparece no menu.
 - Se não tiver marcada, a categoria não aparece e é mostrado opção  Lista Completa no site.
 
-![categoria2.pt](//images.ctfassets.net/alneenqid6w5/3zMivOdJB2tn6E8qE7I43M/9a9f35f14c56b8082723a63c7ba2f7bd/categoria2.pt.png)
+![categoria2.pt](https://images.ctfassets.net/alneenqid6w5/3zMivOdJB2tn6E8qE7I43M/9a9f35f14c56b8082723a63c7ba2f7bd/categoria2.pt.png)
 
diff --git a/docs/tutorials/pt/activating-the-new-order-placed.md b/docs/tutorials/pt/activating-the-new-order-placed.md
index 2d7691de5..ed85aaceb 100644
--- a/docs/tutorials/pt/activating-the-new-order-placed.md
+++ b/docs/tutorials/pt/activating-the-new-order-placed.md
@@ -17,10 +17,10 @@ subcategory:
 
 O novo Order Placed traz um layout melhorado e totalmente mobile-friendly.
 
-![Nova página de Order Placed em versão desktop e mobile](//images.contentful.com/alneenqid6w5/6li99MH1AIqmOECuy8K4Ec/635952ed77d4630e1bd8c08f7761920d/cconf-announcement-0.png)
+![Nova página de Order Placed em versão desktop e mobile](https://images.contentful.com/alneenqid6w5/6li99MH1AIqmOECuy8K4Ec/635952ed77d4630e1bd8c08f7761920d/cconf-announcement-0.png)
 
 Para ativá-lo, vá até a aba **Meus Pedidos** do módulo Portal e acione o opt-in _Order Placed Upgrade_. A nova versão será ativada por default no dia 20/12/2017 e a antiga será descontinuada.
 
-![Opt in no Portal V2](//images.contentful.com/alneenqid6w5/Ce7a3zePdIkEWcMy8m2w8/396ecacbc62a5a1883d2faf0197f4090/cconf-announcement-1.png)
+![Opt in no Portal V2](https://images.contentful.com/alneenqid6w5/Ce7a3zePdIkEWcMy8m2w8/396ecacbc62a5a1883d2faf0197f4090/cconf-announcement-1.png)
 
 Para saber como atualizar sua customização, veja o tutorial [Customizando as páginas do Checkout Confirmation](http://help.vtex.com/tutorial/customizando-o-checkout-confirmation).
diff --git a/docs/tutorials/pt/active-campaign-suiteshare.md b/docs/tutorials/pt/active-campaign-suiteshare.md
index 9310eebc3..33238333a 100644
--- a/docs/tutorials/pt/active-campaign-suiteshare.md
+++ b/docs/tutorials/pt/active-campaign-suiteshare.md
@@ -21,23 +21,23 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Active Campaign**.
 
-   ![CRM Zen_1](//images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
+   ![CRM Zen_1](https://images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
 
 2. Acesse **Configurações > Integrações > Active Campaign > Integrar**.
 
-![Active Campaign_1](//images.ctfassets.net/alneenqid6w5/2O2PvYfjd1TnhPH4vqvmSB/3f102059931a13e25ff64b32c339e0dc/Active_Campaign_1.png)
+![Active Campaign_1](https://images.ctfassets.net/alneenqid6w5/2O2PvYfjd1TnhPH4vqvmSB/3f102059931a13e25ff64b32c339e0dc/Active_Campaign_1.png)
 
 Selecione o [Formulário de captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseja conectar.
 
-![Active Campaign_2](//images.ctfassets.net/alneenqid6w5/1yOIZh4WgIcRbSqPcN4VZd/4e01f427e104b683be8e69f395db7d55/Active_Campaign_2.png)
+![Active Campaign_2](https://images.ctfassets.net/alneenqid6w5/1yOIZh4WgIcRbSqPcN4VZd/4e01f427e104b683be8e69f395db7d55/Active_Campaign_2.png)
 
 Dentro do painel admin da Active Campaing, acesse **Configurações > Desenvolvedor**. 
 
-![Active Campaign_3](//images.ctfassets.net/alneenqid6w5/1deHM7z9nXPAUfXBqHCeyV/3d0359ed82be742cca273d7c9365aa80/Active_Campaign_3.png)
+![Active Campaign_3](https://images.ctfassets.net/alneenqid6w5/1deHM7z9nXPAUfXBqHCeyV/3d0359ed82be742cca273d7c9365aa80/Active_Campaign_3.png)
 
 Copie a URL e a chave dentro da VTEX Assisted Sales (SuiteShare). 
 
-![Active Campaign_4](//images.ctfassets.net/alneenqid6w5/1ViCB3Aj2mQZ9KS1ofuUgk/b4d8237d53c86d75cc9a2e61f298b4ed/Active_Campaign_4.png)
+![Active Campaign_4](https://images.ctfassets.net/alneenqid6w5/1ViCB3Aj2mQZ9KS1ofuUgk/b4d8237d53c86d75cc9a2e61f298b4ed/Active_Campaign_4.png)
 
 Clique em **Salvar**.
 
diff --git a/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md b/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md
index 44bcc7a4d..fcffc6286 100644
--- a/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md
+++ b/docs/tutorials/pt/add-or-edit-a-url-mapping-through-worksheet-import.md
@@ -26,4 +26,4 @@ A estrutura do arquivo deve ser a seguinte:
 - Coluna D: Data Inicial (Formato: DD/MM/AAAA)
 - Coluna E: Data Final (Formato: DD/MM/AAAA)
 
-![urlbuilder1](//images.ctfassets.net/alneenqid6w5/5lgNG0muqcMmS2coOkyKgw/f96b218bfbe58e04ae16869a11f174e8/urlbuilder1.png)
+![urlbuilder1](https://images.ctfassets.net/alneenqid6w5/5lgNG0muqcMmS2coOkyKgw/f96b218bfbe58e04ae16869a11f174e8/urlbuilder1.png)
diff --git a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
index e7504c37a..b348be661 100644
--- a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
+++ b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-facebook.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Para ativar o login via Facebook, é necessário acessar **Configurações da conta > Autenticação** pelo Admin VTEX e preencher os campos **Client ID** e **Segredo do cliente**, conforme detalhado no artigo [Configurar login com Facebook e Google](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
 
-![Facebook OAuth PT](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/1dcbc9286c0245740194026e19ba5c9b/1-login-fb-pt.png)
+![Facebook OAuth PT](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/1dcbc9286c0245740194026e19ba5c9b/1-login-fb-pt.png)
 
 Para obter essas credenciais, siga as instruções de cada etapa abaixo:
 
@@ -35,12 +35,12 @@ Para começar, você precisa cadastrar um aplicativo no Facebook, seguindo os pa
 4. Clique em `Criar aplicativo`.
 5. Clique em **Permitir que as pessoas entrem com a própria conta do Facebook**, dentre as opções ilustradas abaixo.
 
-   ![2-login-fb-pt](//images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/c5d74282b8459d40d3a0ac9026591787/2-login-fb-pt.png)
+   ![2-login-fb-pt](https://images.ctfassets.net/alneenqid6w5/3zv1li5neUPsSK8VhPaRy0/c5d74282b8459d40d3a0ac9026591787/2-login-fb-pt.png)
 
 6. Clique em `Avançar`.
 7. Preencha o nome do app e o email de contato do responsável pelo aplicativo, nos campos ilustrados abaixo.
 
-   ![3-login-fb-pt](//images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/2cf04b1ea40c6e4e4ed2d843296bb256/3-login-fb-pt.png)
+   ![3-login-fb-pt](https://images.ctfassets.net/alneenqid6w5/1Yg8Du8HKxU7rW15ZsL6vD/2cf04b1ea40c6e4e4ed2d843296bb256/3-login-fb-pt.png)
 
 8. Clique em `Criar aplicativo`.
 
@@ -50,15 +50,15 @@ O próximo passo é configurar o produto Login do Facebook no aplicativo que voc
 
 1. Clique em **Produtos** no menu lateral ou no **Painel **do Meta for Developers, destacado a seguir.
 
-   ![4-login-fb-pt](//images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/9b7ff04d05523c1d9ec09f5b3f563d34/4-login-fb-pt.png)
+   ![4-login-fb-pt](https://images.ctfassets.net/alneenqid6w5/2wNKd6gswgFQAghpNdvEVq/9b7ff04d05523c1d9ec09f5b3f563d34/4-login-fb-pt.png)
 
 2. Clique em `Configurar` e, em seguida, na opção `Configurações`.
 
-   ![5-login-fb-pt](//images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/f64b512f3583de4ab35032ec1f3dcb23/5-login-fb-pt.png)
+   ![5-login-fb-pt](https://images.ctfassets.net/alneenqid6w5/vMQDtOfYgSZfo7EOYuNel/f64b512f3583de4ab35032ec1f3dcb23/5-login-fb-pt.png)
 
 3. Defina os estados como na imagem abaixo:
 
-   ![Configuração URI OAuth Facebook PT](//images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/8aeaa64b10c388f9ac5aec145bcc3055/configuracoes_Oauth_PT.png)
+   ![Configuração URI OAuth Facebook PT](https://images.ctfassets.net/alneenqid6w5/5Y82HZJjF3ZDIVE5WD4Lvt/8aeaa64b10c388f9ac5aec145bcc3055/configuracoes_Oauth_PT.png)
 
    Insira as URLs abaixo em **URIs de redirecionamento do OAuth válidos**, substituindo `{{HOST_URL}}` pela URL base de sua loja e `{{accountName}}` pelo nome da sua conta VTEX como descrito no Admin:
 
@@ -74,7 +74,7 @@ Por fim, você precisa preencher algumas informações sobre o app para concluir
 
 1. No menu lateral do Meta for Developers, vá em **Configurações do app** e clique em **Básico:**
 
-   ![7-login-fb-pt](//images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/e0a0037af04e1e1d8b465520f804d9a0/7-login-fb-pt.png)
+   ![7-login-fb-pt](https://images.ctfassets.net/alneenqid6w5/4rhVhY9V6N117s3XwZ59No/e0a0037af04e1e1d8b465520f804d9a0/7-login-fb-pt.png)
 
 2. Copie o valor do campo **ID do Aplicativo**. Você deverá informar este valor no campo **Client ID** ao [configurar o login com Facebook no Admin VTEX](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
 3. Em **Chave Secreta do Aplicativo**, clique no botão **Mostrar** e, em seguida, copie o valor do campo. Você deverá informar este valor no campo **Segredo do cliente** ao [configurar o login com Facebook no Admin VTEX](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513).
diff --git a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
index e81a38547..5fab72078 100644
--- a/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
+++ b/docs/tutorials/pt/adding-a-client-id-and-a-client-secret-to-log-in-with-google.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Para ativar o funcionamento de login por OAuth2 via Google, é necessário acessar o VTEX ID pelo seu admin e preencher os campos `Client ID` e `Client Secret`, conforme detalhado [neste artigo](/pt/tutorial/integracao-google-e-facebook-para-login).
 
-![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
+![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
 
 Esses valores são obtidos a partir de um projeto que precisa ser criado no serviço de APIs do Google Cloud Platform.
 
@@ -30,18 +30,18 @@ Os passos abaixo descrevem procedimentos em uma plataforma externa e podem estar
 1. Entrar no link [`https://console.developers.google.com/`](https://console.developers.google.com/);
 2. Clicar em __Credenciais__, na aba lateral;
 3. Clique em __Criar Projeto__;
-    ![Criar Projeto Google PT](//images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/15e9e1be0ef0b9bfd4f6cd23833f52a6/Criar_Projeto_Google_PT.png)
+    ![Criar Projeto Google PT](https://images.ctfassets.net/alneenqid6w5/7d7axXgcKs8SKcG0YekU8m/15e9e1be0ef0b9bfd4f6cd23833f52a6/Criar_Projeto_Google_PT.png)
 
 4. Dê um nome ao projeto e clique em __Criar__;
-    ![Novo Projeto Google PT](//images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/dcb58074e3fb0668c4ea336bee08870a/Novo_Projeto_Google_PT.png)
+    ![Novo Projeto Google PT](https://images.ctfassets.net/alneenqid6w5/1PB6BTeU4I6YOqySuwcS4W/dcb58074e3fb0668c4ea336bee08870a/Novo_Projeto_Google_PT.png)
 5. No topo da página, clicar no botão __Criar credenciais__;
-    ![Criar Credenciais Google PT](//images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/e5cbd9523888845caa07211cdec356cf/Criar_Credenciais_Google_PT.png)
+    ![Criar Credenciais Google PT](https://images.ctfassets.net/alneenqid6w5/5bGcIsahuvFskIQBn8X8bl/e5cbd9523888845caa07211cdec356cf/Criar_Credenciais_Google_PT.png)
 6. Clicar na opção __ID do cliente OAuth__;
-    ![ID cliente OAuth Google PT](//images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/68b13531dab5020ea4e40f69f34a58e2/ID_cliente_OAuth_Google_PT.png)
+    ![ID cliente OAuth Google PT](https://images.ctfassets.net/alneenqid6w5/5CBmKjKYTYOMkkQImIMcI4/68b13531dab5020ea4e40f69f34a58e2/ID_cliente_OAuth_Google_PT.png)
 7. Clicar no botão __Configurar tela de consentimento__;
-    ![Configurar Tela Consentimento Google PT](//images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/2c7660f7dea9b320ca24df57e89910a2/Configurar_Tela_Consentimento_Google_PT.png)
+    ![Configurar Tela Consentimento Google PT](https://images.ctfassets.net/alneenqid6w5/3mprVJpYy6wdtJJEhhbi1s/2c7660f7dea9b320ca24df57e89910a2/Configurar_Tela_Consentimento_Google_PT.png)
 8. Escolha o tipo de usuário desejado para a sua loja (__Interno__ ou __Externo__) e clique no botão __Criar__;
-    ![Tipo usuário Google PT](//images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/7579b27f325d7e2c31444ba21a29a017/Tipo_usu__rio_PT.png)
+    ![Tipo usuário Google PT](https://images.ctfassets.net/alneenqid6w5/yxxE4AdTY0yuNClfZwXHL/7579b27f325d7e2c31444ba21a29a017/Tipo_usu__rio_PT.png)
 9.  __Nome do app__: será exibido aos seus clientes no momento do login;
 10. __E-mail para suporte do usuário__: para que os usuários contatem você com perguntas sobre o consentimento;
 11. __Logotipo do app__: corresponde ao logotipo da sua loja;
@@ -50,21 +50,21 @@ Os passos abaixo descrevem procedimentos em uma plataforma externa e podem estar
     - `vtex.com.br`, relativo aos nossos servidores de backend
 13. __Dados de contato do desenvolvedor__: o Google usa esses endereços de e-mail para notificar você sore todas as alterações do projeto;
 14. Clicar no botão __Salvar e continuar__;
-    ![Configurações Tela Consentimento PT](//images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/db5c3ff4f9ca43f8a50e51bfb49376ac/Configura____es_Tela_Consentimento_PT.png)
+    ![Configurações Tela Consentimento PT](https://images.ctfassets.net/alneenqid6w5/2jKyTCl5FeeMsS2iAw0aKa/db5c3ff4f9ca43f8a50e51bfb49376ac/Configura____es_Tela_Consentimento_PT.png)
 13. Clicar no item do menu lateral esquerdo __Credenciais__;
 14. Escolher __Aplicativo da Web__, em Tipo de aplicativo;
-    ![Credenciais Aplicativo Web Google PT](//images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/1b63eaf43364a7d6f1ebe2330b396a72/Credenciais_Aplicativo_Web_Google_PT.png)
+    ![Credenciais Aplicativo Web Google PT](https://images.ctfassets.net/alneenqid6w5/1sq6ByDBoYtGLeiU3Xsmgx/1b63eaf43364a7d6f1ebe2330b396a72/Credenciais_Aplicativo_Web_Google_PT.png)
 15. __Nome__: para identificação interna;
 16. __Origens JavaScript autorizadas__: cadastrar os endereços exatos que poderão usar este método de autenticação, o que corresponde ao seu site; exemplo `https://www.loja.com`. Também é recomendado cadastrar o endereço `https://{{accountName}}.myvtex.com` de sua conta, onde `{{accountName}}` é o nome da sua conta como descrito no menu administrativo da loja;
 17. __URIs de redirecionamento autorizados__: cadastrar a URL de serviço da VTEX:
 
     -`https://vtexid.vtex.com.br/VtexIdAuthSiteKnockout/ReceiveAuthorizationCode.ashx`
 
-    ![Configurações Aplicativo Web Google PT](//images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/91105aa43df17443cfecdcad79acc3a4/Configura____es_Aplicativo_Web_PT.png)
+    ![Configurações Aplicativo Web Google PT](https://images.ctfassets.net/alneenqid6w5/4HsRII0LeoGMYqWoioWi0o/91105aa43df17443cfecdcad79acc3a4/Configura____es_Aplicativo_Web_PT.png)
 
 18. Após concluído, serão apresentadas suas credenciais:
-    ![Cliente OAuth criado Google PT](//images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/2aea225da796a27ea6974766b984a493/Cliente_OAuth_criado_Google_PT.png)
+    ![Cliente OAuth criado Google PT](https://images.ctfassets.net/alneenqid6w5/58KAqlnXhKoAqgq6Gcc80K/2aea225da796a27ea6974766b984a493/Cliente_OAuth_criado_Google_PT.png)
     - Copie o __ID do cliente__ do Google e cole no campo `Client Id` no admin do VTEX ID.
     - Copie a __chave secreta do cliente__ do Google e cole no campo `Client Secret` no admin do VTEX ID.
-    ![Google OAuth](//images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
+    ![Google OAuth](https://images.ctfassets.net/alneenqid6w5/67wXwVN1RaDZ5oOy6XrTSe/a508065cf5028f3a806edad050a0f6e6/google_PT.png)
     Depois de cumprir esses passos, salve as alterações.    
diff --git a/docs/tutorials/pt/adding-an-attachment.md b/docs/tutorials/pt/adding-an-attachment.md
index c342d7afd..da54f571e 100644
--- a/docs/tutorials/pt/adding-an-attachment.md
+++ b/docs/tutorials/pt/adding-an-attachment.md
@@ -31,7 +31,7 @@ O objetivo de um anexo é [complementar o produto com uma informação personali
 Após realizar o cadastro inicial do anexo, você precisa adicionar as chaves e os **Valores Permitidos** relacionados ao anexo criado. Você pode adicionar quantas chaves desejar. Para adicionar as chaves e os **Valores Permitidos**, siga os passos a seguir.
 
 1. Na página **Campos personalizados**, identifique a linha do anexo criado e clique em `Alterar`, conforme ilustrado na imagem abaixo.
-   ![anexos.pt](//images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/cfb0a116c7f139d84ba256cab5b649cd/anexos.pt.png)
+   ![anexos.pt](https://images.ctfassets.net/alneenqid6w5/4hSZgKMwFjJ3fE2Tfek60C/cfb0a116c7f139d84ba256cab5b649cd/anexos.pt.png)
 2. Preencha os campos listados a seguir.
     * **Nome da Chave:** nome da informação personalizada. Este campo é obrigatório e não pode conter caracteres especiais, apenas letras, números ou pontos. Exemplo: se o produto personalizável for uma Camisa da Seleção Brasileira, os nomes das suas chaves podem ser `Nome` e `Numero`.
     * **Máximo de Caracteres:** máximo de caracteres que o cliente pode digitar para inserir uma informação personalizada no produto. Este campo é obrigatório. Exemplo: neste campo você poderia estipular o limite de caracteres para o nome que será impresso em uma camisa.
diff --git a/docs/tutorials/pt/adding-bin-information.md b/docs/tutorials/pt/adding-bin-information.md
index bd0d44ac7..5936d58dc 100644
--- a/docs/tutorials/pt/adding-bin-information.md
+++ b/docs/tutorials/pt/adding-bin-information.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 O Número de Identificação Bancária (BIN) é composto pelos primeiros seis ou oito dígitos de um cartão de crédito ou débito e caracteriza a instituição responsável pela emissão do cartão.  
 
-![BIN_image_digits_PT_2](//images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/7ea68dacd8491fba2022ccb608efd3fd/BIN_image_digits_PT_2.png)
+![BIN_image_digits_PT_2](https://images.ctfassets.net/alneenqid6w5/56E0fyyarcKE5C68SXt7xQ/7ea68dacd8491fba2022ccb608efd3fd/BIN_image_digits_PT_2.png)
 
 Quando a instituição bancária deseja criar novos perfis de cartões ou emitir novos cartões para um modelo já existente, é necessário criar novos BINs. Isso também se aplica quando uma [bandeira](https://help.vtex.com/pt/tutorial/o-que-e-uma-bandeira-de-cartao-de-credito--4bNba5QYuIwKEmac88KwyI) é comprada por outra.
 
@@ -39,5 +39,5 @@ No ticket, você deve encaminhar em anexo uma planilha preenchida com as seguint
 
 Modelo de planilha preenchida:
 
-![Bin_spreadsheet](//images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/f28a04568922f6e08425ae177b26b0fe/Bin_spreadsheet.PNG)
+![Bin_spreadsheet](https://images.ctfassets.net/alneenqid6w5/1bYkI1ppRO3r7VtpFyDPfA/f28a04568922f6e08425ae177b26b0fe/Bin_spreadsheet.PNG)
 
diff --git a/docs/tutorials/pt/adding-collections-cms.md b/docs/tutorials/pt/adding-collections-cms.md
index 38db87410..dedb8c959 100644
--- a/docs/tutorials/pt/adding-collections-cms.md
+++ b/docs/tutorials/pt/adding-collections-cms.md
@@ -33,7 +33,7 @@ Siga o passo a passo abaixo para cadastrar uma nova coleção:
 
 A escolha dos produtos que vão compor uma coleção é feita através da criação de um __grupo__. Para isso, basta clicar em __New Group__ dentro da coleção desejada. 
 
-![2019-06-06 16 22 46-Layout](//images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
+![2019-06-06 16 22 46-Layout](https://images.ctfassets.net/alneenqid6w5/1HELFm1eBsSZVpq6EEQQJ4/29c77be34d91e4eac14b7bf3d4597fa4/2019-06-06_16_22_46-Layout.png)
 
 Antes de escolher quais produtos farão parte do grupo, como veremos a seguir, é necessário atribuir um nome e especificar o tipo de grupo criado. 
 
@@ -75,17 +75,17 @@ Por exemplo: ao selecionar a categoria `A` e a marca `B`, apenas os produtos que
 
 Para adicionar todos os produtos de um determinado Departamento a um grupo, basta selecionar o Departamento desejado e clicar em __Save Group__, como mostra a imagem abaixo. 
 
-![selecionar-departamento-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/577w3KpNuahKOiY0iQTYrp/6f036e35d347f1f9dbf66e347e151ca6/selecionar-departamento-colecoes-cms_PT.png)
+![selecionar-departamento-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/577w3KpNuahKOiY0iQTYrp/6f036e35d347f1f9dbf66e347e151ca6/selecionar-departamento-colecoes-cms_PT.png)
 
 O mesmo se aplica aos produtos de uma determinada Categoria ou Subcategoria.
 
-![selecionar-categoria-subcategoria-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/6bV3ick7BunjS5QOnMVpED/d5f4b348b405f6e05248f088cba664c5/selecionar-categoria-subcategoria-colecoes-cms_PT.png)
+![selecionar-categoria-subcategoria-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/6bV3ick7BunjS5QOnMVpED/d5f4b348b405f6e05248f088cba664c5/selecionar-categoria-subcategoria-colecoes-cms_PT.png)
 
 ## Produtos por Marca
 
 Para criar um grupo com produtos de uma ou mais marcas, basta selecionar a marca desejada na lista correspondente. 
 
-![selecionar-marcas-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/2f4nqqF2CWFbw5Cgjmc32f/d6c7c8ce8f198255cd744e5e60668962/selecionar-marcas-colecoes-cms_PT.png)
+![selecionar-marcas-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/2f4nqqF2CWFbw5Cgjmc32f/d6c7c8ce8f198255cd744e5e60668962/selecionar-marcas-colecoes-cms_PT.png)
 
 As marcas encontram-se dispostas em ordem alfabética. Ao clicar na letra correspondente à inicial da marca desejada, a lista se expande e exibe as marcas existentes.
 
@@ -95,7 +95,7 @@ As marcas encontram-se dispostas em ordem alfabética. Ao clicar na letra corres
 
 Ao adicionar um SKU a um grupo, o produto ao qual ele está vinculado também será adicionado. Em um cenário em que um produto tenha mais de um SKU atribuido a ele, a adição de um único SKU fará com que todos os outros também sejam adicionados ao grupo.
 
-![add-skus-manualmente-coleção-cms](//images.ctfassets.net/alneenqid6w5/4DWiR2pUd1U40fWTAqmwG1/96f1f747f2250c98cec87b6d7e02e6d3/add-skus-manualmente-cole____o-cms.png)
+![add-skus-manualmente-coleção-cms](https://images.ctfassets.net/alneenqid6w5/4DWiR2pUd1U40fWTAqmwG1/96f1f747f2250c98cec87b6d7e02e6d3/add-skus-manualmente-cole____o-cms.png)
 
 No campo __Find SKUs__, é possível digitar o ID de quantos SKUs forem desejados, escrevendo os valores entre vírgulas. 
 
@@ -117,21 +117,21 @@ Obtenha o modelo de arquivo para a inclusão e exclusão de SKUs da coleção <a
 
 No campo __Bulk Insert SKUs__, é possível inserir por planilha (formato `.xls`) uma listagem de SKUs que farão parte do grupo.
 
-![add-skus-manualmente-planilha-coleção-cms](//images.ctfassets.net/alneenqid6w5/46dZS1m8ISWP68SMNZrMlm/2b733ea38c3f62d7c503a44c6f55fb56/add-skus-manualmente-planilha-cole____o-cms.png)
+![add-skus-manualmente-planilha-coleção-cms](https://images.ctfassets.net/alneenqid6w5/46dZS1m8ISWP68SMNZrMlm/2b733ea38c3f62d7c503a44c6f55fb56/add-skus-manualmente-planilha-cole____o-cms.png)
 
 Na planilha, todos os IDs dos SKUs devem estar dispostos na primeira coluna, com o cabeçalho, como exemplifica a figura abaixo:
 
-![exemplo-planilha-seleção-sku-coleção](//images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
+![exemplo-planilha-seleção-sku-coleção](https://images.ctfassets.net/alneenqid6w5/5E2rtjyWArzeGjr27smF4o/bd66f1ea64d4e0d104471fac71bd98ab/exemplo-planilha-sele____o-sku-cole____o.png)
 
 Depois de selecionar a planilha desejada, clique na opção de __Import skus__ para enviar as informações.
 
-![Import SKUs](//images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
+![Import SKUs](https://images.ctfassets.net/alneenqid6w5/61tifMGQaUdD1MAsfdblo8/2ecfd6edbba468740f23ccc53c3e1eba/Import_SKUs.png)
 
 #### Exclusão massiva
 
 Para evitar a exclusão manual de um SKU por vez, também é possível usar o recurso de importação de planilha para a exclusão massiva. 
 
-![exclusao-skus-manualmente-planilha-coleção-cms](//images.ctfassets.net/alneenqid6w5/2LVbuzlmh0nmgY4z21i9Be/f55707ea917364ed1732a4050b98a7a3/exclusao-skus-manualmente-planilha-cole____o-cms.png)
+![exclusao-skus-manualmente-planilha-coleção-cms](https://images.ctfassets.net/alneenqid6w5/2LVbuzlmh0nmgY4z21i9Be/f55707ea917364ed1732a4050b98a7a3/exclusao-skus-manualmente-planilha-cole____o-cms.png)
 
 Nesse caso em específico, os SKUs listados na planilha importada serão excluídos do grupo. Para isso, clique na opção __excluir skus__ depois que o arquivo for carregado.
 
@@ -147,7 +147,7 @@ Na seção de <strong>Other options</strong>, as opções <strong>Pre-sales</str
 
 Note que apenas é possível selecionar uma das duas opções. Caso queira que ambos os cenários sejam contemplados, crie dois grupos e configure cada um deles com a respectiva opção.
 
-![selecionar-other-options-colecoes-cms PT](//images.ctfassets.net/alneenqid6w5/2SrWIT3WZdqgYe2m6NUvhP/c0b4a98dd766dc27c63f706f4592ec40/selecionar-other-options-colecoes-cms_PT.png)
+![selecionar-other-options-colecoes-cms PT](https://images.ctfassets.net/alneenqid6w5/2SrWIT3WZdqgYe2m6NUvhP/c0b4a98dd766dc27c63f706f4592ec40/selecionar-other-options-colecoes-cms_PT.png)
 
 ### Pre-sales
 
diff --git a/docs/tutorials/pt/adding-sku-specifications-or-fields.md b/docs/tutorials/pt/adding-sku-specifications-or-fields.md
index 8bdc2453d..218bb4050 100644
--- a/docs/tutorials/pt/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/pt/adding-sku-specifications-or-fields.md
@@ -43,7 +43,7 @@ Antes de criar especificações, é importante compreender que elas seguem uma l
 
 Exemplo: considere o produto **Camisa Masculina**. Em __Catálogo > Produtos e SKUs > SKU > Especificações__, página ilustrada a seguir, podemos ver que o grupo de especificações chamado **Características** está associado à categoria da camisa. Esse grupo inclui um campo de nome **Cor** e um campo de nome **Tamanho**.
 
-![heranca-especificacoes-sku-pt](//images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/559bba5b55428ce03d7f1cda2c943b3a/image5.png)
+![heranca-especificacoes-sku-pt](https://images.ctfassets.net/alneenqid6w5/1KPyqwiasQnbeEhBZ8K5ZJ/559bba5b55428ce03d7f1cda2c943b3a/image5.png)
 
 Por se tratar de uma especificação de SKU, as informações selecionadas nessa página valerão somente para essa variação do produto **Camisa Masculina**. Todos os SKUs cadastrados no produto **Camisa Masculina** e todos os SKUs de produtos da mesma categoria devem ter essas especificações preenchidas também.
 
@@ -85,7 +85,7 @@ Para criar um campo de SKU, siga as instruções abaixo:
     * **Ativo**: insere ou remove este campo no cadastro do SKU.
 7. Clique em `Salvar`.
 
-![sku-spec-1](//images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/f79bf71a242604110e96e435c58d1170/pt-sku-spec-1.gif)
+![sku-spec-1](https://images.ctfassets.net/alneenqid6w5/5b2UFRxvAQ6BoL6eStxf0D/f79bf71a242604110e96e435c58d1170/pt-sku-spec-1.gif)
 
 #### Tipos de campo de SKU
 
@@ -130,13 +130,13 @@ Os **Valores** dos campos de SKU irão variar de acordo com o tipo do campo esco
 
     Insira um valor por linha e tecle `Enter` entre cada valor, conforme ilustrado na imagem a seguir.
 
-    ![valores-campo-sku-pt](//images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/c513840f0f21b2f76ec2215b239f3395/image9.png)
+    ![valores-campo-sku-pt](https://images.ctfassets.net/alneenqid6w5/7puatHudsAbkAY9NUKpWYh/c513840f0f21b2f76ec2215b239f3395/image9.png)
 
 8. Clique em `Salvar`.
 
     Os valores cadastrados serão exibidos na [interface do cadastro de SKU](#preencher-especificacoes-de-sku).
 
-![sku-spec-2](//images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/066317aa51dbd5521e83f85d9923782f/pt-sku-spec-2.gif)
+![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/066317aa51dbd5521e83f85d9923782f/pt-sku-spec-2.gif)
 
 <div class = "alert alert-info">
   <p>Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção <strong>Ativo</strong>.</p>
@@ -181,7 +181,7 @@ Para preencher as especificações de cada SKU de forma individual, siga as inst
 
 8. Clique em `Salvar`.
 
-![sku-spec-3](//images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/448631dcf3653ce0af8373b24e353a5a/pt-sku-spec-3.gif)
+![sku-spec-3](https://images.ctfassets.net/alneenqid6w5/6mV0lyVG6Z2ywmtNheePEf/448631dcf3653ce0af8373b24e353a5a/pt-sku-spec-3.gif)
 
 #### Planilha
 
@@ -204,7 +204,7 @@ Para preencher especificações de SKUs em massa por planilha, você precisa exp
 9. Clique em **Selecionar** para selecionar o arquivo com a planilha preenchida no seu computador.
 10. Clique em `Importar`.
 
-![sku-spec-4](//images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/d71e8d6726d70416fa50bba58fcb1cfc/pt-sku-spec-4.gif)
+![sku-spec-4](https://images.ctfassets.net/alneenqid6w5/6apU0Qp7SqnH6ZfPT5lzrr/d71e8d6726d70416fa50bba58fcb1cfc/pt-sku-spec-4.gif)
 
 ## Saiba mais
 - [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106)
diff --git a/docs/tutorials/pt/adding-specifications-or-product-fields.md b/docs/tutorials/pt/adding-specifications-or-product-fields.md
index 483c63aab..c285561c4 100644
--- a/docs/tutorials/pt/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/pt/adding-specifications-or-product-fields.md
@@ -43,7 +43,7 @@ Antes de criar especificações, é importante compreender que as especificaçõ
 
 Considere o produto **Televisão** como exemplo. Em **Catálogo > Todos os produtos > Alterar > Especificações**, página ilustrada a seguir, podemos ver que o grupo de especificações chamado **Características** está associado à categoria da televisão. Esse grupo inclui um campo de nome **Polegadas** e um campo de nome **Faixa etária**, que são obrigatórios.
 
-![especificacoes-caracteristicas-pt](//images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/ac89c8d88e3188da9d6af758d0e6992a/image6.png)
+![especificacoes-caracteristicas-pt](https://images.ctfassets.net/alneenqid6w5/3ZMzwADYCl7QnNomdpGnoH/ac89c8d88e3188da9d6af758d0e6992a/image6.png)
 
 Por se tratar de uma especificação de produto, as informações selecionadas nessa página valerão para todas as variações do produto __Televisão__. Todos os produtos cadastrados na mesma categoria da televisão precisam ter essas especificações preenchidas também, visto que os campos são obrigatórios.
 
@@ -80,7 +80,7 @@ Para criar um campo de produto, siga os passos abaixo:
     * **Ativo**: insere ou remove este campo no cadastro do produto (aba **Especificações**).
 7. Clique em `Salvar`. 
 
-![product-spec-1](//images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/7d508a1ad7465143efe1465d19275e19/PT_ProdutoGif_1_Alterado.gif)
+![product-spec-1](https://images.ctfassets.net/alneenqid6w5/5Y8LnWHVXSvRbqtMNBLSRq/7d508a1ad7465143efe1465d19275e19/PT_ProdutoGif_1_Alterado.gif)
 
 #### Tipos de campo de produto
 
@@ -146,7 +146,7 @@ Já para os campos de tipo **Combo**, **Radio** e **CheckBox**, é necessário c
 
     Os valores criados serão exibidos na aba **Especificação** no cadastro de Produto.
 
-![product-spec-2](//images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/283b1aca04c1790b548ee51438fe132f/PT_ProdutoGif_2_Alterado.gif)
+![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/283b1aca04c1790b548ee51438fe132f/PT_ProdutoGif_2_Alterado.gif)
 
 <div class = "alert alert-info">
   <p>Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção <strong>Ativo</strong>.</p>
@@ -188,7 +188,7 @@ Para preencher as especificações de cada produto de forma individual, siga as
 
 6. Clique em `Salvar`.
 
-![product-spec-3](//images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/f54f61f82531c5be837a8516278103df/PT_ProdutoGif_3_Alterado.gif)
+![product-spec-3](https://images.ctfassets.net/alneenqid6w5/7B2L2oEoPQkPU2EJDowsxx/f54f61f82531c5be837a8516278103df/PT_ProdutoGif_3_Alterado.gif)
 
 #### Planilha
 
@@ -211,7 +211,7 @@ Para preencher especificações de produtos em massa por planilha, é necessári
 9. Clique em **Select** para selecionar o arquivo com a planilha preenchida no seu computador.
 10. Clique em `Importar`.
 
-![product-spec-4](//images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/e25821cf11d4b27e9142389fbd207d85/PT_ProdutoGif_4_Alterado.gif)
+![product-spec-4](https://images.ctfassets.net/alneenqid6w5/747pr0ISwE9GrNBjC4kKjL/e25821cf11d4b27e9142389fbd207d85/PT_ProdutoGif_4_Alterado.gif)
 
 ## Saiba mais
 - [Cadastrar especificações ou campos de SKU](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119)
diff --git a/docs/tutorials/pt/adding-your-brands.md b/docs/tutorials/pt/adding-your-brands.md
index 711e8cf75..2b5a873d7 100644
--- a/docs/tutorials/pt/adding-your-brands.md
+++ b/docs/tutorials/pt/adding-your-brands.md
@@ -17,4 +17,4 @@ subcategory:
 
 O [cadastro de marca](/pt/tutorial/cadastrando-marcas/) é obrigatório para a ativação de seus produtos e SKUs. Caso sua loja não trabalhe com marcas, é possível cadastrar uma marca padrão e associar todos os produtos a esta marca.
 
-<video class="wp-video-shortcode" id="video-2561-9" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4?_=9" />[//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4](//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4 "//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4")</video>
+<video class="wp-video-shortcode" id="video-2561-9" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4?_=9" />[//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4](https://assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4 "//assets.contentful.com/alneenqid6w5/GRMPNnK8WQYiKG8UaYEYG/a4f0c0ffdf38f049b4a993ae96c3d95e/CriandoMarca.mp4")</video>
diff --git a/docs/tutorials/pt/additional-shipping-costs.md b/docs/tutorials/pt/additional-shipping-costs.md
index 52aedea1e..e5e54569f 100644
--- a/docs/tutorials/pt/additional-shipping-costs.md
+++ b/docs/tutorials/pt/additional-shipping-costs.md
@@ -18,7 +18,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Os adicionais de frete são valores extras adicionados ao custo de envio pelas [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Então, ao configurar um valor de custo para a entrega dos itens da sua loja, é possível configurar uma tarifa fixa e incluir valores adicionais. O custo fixo de entrega somado aos adicionais compõem os custos da [tarifa de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM).
 
-![Tarifa envio PT](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
+![Tarifa envio PT](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
 
 Os valores adicionais podem ser configurados conforme:
 
@@ -27,7 +27,7 @@ Os valores adicionais podem ser configurados conforme:
 * O seguro do produto: [adicional de seguro](https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV#adicional-de-seguro).
 * O valor do frete:  [adicional de frete](ahttps://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV#adicional-de-frete).
 
-![adicionais frete PT](//images.contentful.com/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/32b53f2163eed7c9497bacfb95101b65/adicionais_frete_PT.svg)
+![adicionais frete PT](https://images.contentful.com/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/32b53f2163eed7c9497bacfb95101b65/adicionais_frete_PT.svg)
 
 <div class="alert alert-danger">
 É importante ressaltar que é possível ter todos os adicionais configurados simultaneamente para uma única tarifa de envio. O cálculo final da <a href="https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">tarifa de envio</a> é a soma de todos os adicionais cadastrados mais a tarifa fixa do frete. 
@@ -92,7 +92,7 @@ Tarifa de envio: ($10+$16,4)=$26,4
 É importante lembrar que o cálculo do adicional por preço não considera possíveis descontos e promoções, e sim o valor cheio do carrinho. Se o adicional por preço for menor que o adicional de seguro, o adicional por preço é desconsiderado no cálculo final da tarifa de envio.
 </div>
 
-![faixa-peso PT](//images.contentful.com/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/dbe9c301826e8e91104cd7a8ded70690/faixa-peso_PT.png)
+![faixa-peso PT](https://images.contentful.com/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/dbe9c301826e8e91104cd7a8ded70690/faixa-peso_PT.png)
 
 ### Configuração 
 
@@ -159,4 +159,4 @@ Para configurar o adicional de frete, acesse o menu esquerdo do Admin VTEX:
     Se quer incluir uma taxa de 10% preencha o campo com 10. Para números decimais utilize pontos ao invés de vírgula (como em 1.67).
 3. Clique em `Salvar`.
 
-![adicional configuracoes PT](//images.contentful.com/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/2c2619466363bd20447cd0f783d07691/adicional_configuracoes_PT.png)
+![adicional configuracoes PT](https://images.contentful.com/alneenqid6w5/2pVEQFyDHdXcZYpkQW85m0/2c2619466363bd20447cd0f783d07691/adicional_configuracoes_PT.png)
diff --git a/docs/tutorials/pt/admin-v4-getting-started.md b/docs/tutorials/pt/admin-v4-getting-started.md
index 479fe5f1a..d541e261a 100644
--- a/docs/tutorials/pt/admin-v4-getting-started.md
+++ b/docs/tutorials/pt/admin-v4-getting-started.md
@@ -26,29 +26,29 @@ Enquanto ainda estamos migrando as páginas para o Admin v4, você pode encontra
 ## Navegação aprimorada 
 Tudo que você precisa para administrar sua loja VTEX continua disponível no Admin v4, mas agora com uma organização mais simples. Nossos menus de navegação lateral e barra superior foram reformulados do zero, agrupando categorias similares de forma mais clara para reduzir as distrações e ajudar a sua equipe a encontrar o que precisa mais rapidamente. Também é possível utilizar a barra de busca para encontrar seções específicas no menu lateral.
 
-![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Central de Informações
 É aqui que reunimos todos os links úteis do nosso ecossistema VTEX, para ajudá-lo a aproveitar a nossa plataforma ao máximo. Clicando no botão `?` na barra superior, você pode acessar nosso Help Center, Developer Portal, Status da Plataforma, blog e páginas de suporte.
 
-![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Configurações da Loja
 Para esta nova experiência, reunimos todas as configurações de todas as seções do seu Admin em uma guia específica: Configurações da Loja. Através dessa melhoria, você pode acessar facilmente todas as configurações que afetam cada serviço da sua conta.
 
-![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Configurações de Perfil
 Seu avatar de perfil, no canto superior direito, agora reúne todas as configurações relacionadas ao seu usuário e à sua conta. Através do avatar, você pode acessar as configurações do usuário, as configurações da conta, as informações de faturas, alterar o idioma do seu Admin, voltar para a versão anterior do Admin e encerrar a sessão. Com essa melhoria, separamos as configurações do seu perfil das configurações que afetam a sua loja em si. Agora você tem mais controle e visibilidade sobre as ações que afetam o seu negócio e as que afetam o seu perfil.
 
-![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 ## Página inicial renovada
 A página inicial do nosso admin foi redesenhada para oferecer uma visão geral de alto nível da sua loja, como uma cabine de comando para as suas operações de comércio digital. Por isso, ela agora se chama **Dashboard**.
 
 Assim que você fizer login no Admin v4, verá métricas e gráficos úteis para monitorar o desempenho da sua loja, como a receita gerada e o número de pedidos, o funil de vendas e a taxa de conversão, além dos 10 produtos que geraram maior receita. Veja todos os componentes do novo Dashboard e aprenda como eles funcionam na lista abaixo.
 
-![Dashboard v4](//images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
+![Dashboard v4](https://images.ctfassets.net/alneenqid6w5/4BdhVile9g8esXtlAt2wfd/51be029026157f666f83e4df1cf08519/Dashboard_v4.gif)
 
 - **Pedidos:** número de pedidos realizados. Todos os dados sobre pedidos e receita vêm do Sistema de Gerenciamento de Pedidos da VTEX.
 - **Sessões:** número de visitas à loja.  
diff --git a/docs/tutorials/pt/ads-from-vtex-sales-app.md b/docs/tutorials/pt/ads-from-vtex-sales-app.md
index 172e92662..7dec09fd6 100644
--- a/docs/tutorials/pt/ads-from-vtex-sales-app.md
+++ b/docs/tutorials/pt/ads-from-vtex-sales-app.md
@@ -64,24 +64,24 @@ Para criar uma página de anúncios para o VTEX Sales App, siga os passos abaixo
     * **Título da vitrine:** nome da vitrine que  será exibido na página.
     * **ID do produto:** número identificador do produto que você deseja exibir. Campo obrigatório.
     * **SKU ID do produto:** número identificador do  SKU do produto que você deseja exibir. Campo opcional.
-![vitrine-produto-pt](//images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/6a0001784a5ba632dfa4a39078e5293a/image.png)
+![vitrine-produto-pt](https://images.ctfassets.net/alneenqid6w5/6SREOFdog1AfNXqyhH0I5Z/6a0001784a5ba632dfa4a39078e5293a/image.png)
 Após preencher os campos, será exibido a imagem do produto com o preço com a "partir de". Caso você inclua o SKU, será exibido o preço e promoção do SKU indicado. Você pode incluir mais produtos clicando em `+ NOVO PRODUTO`. É possível adicionar até 10 produtos em cada vitrine. 
 O resultado da vitrine de produtos será exibido conforme imagem abaixo.
-![vitrine-produto-2-pt](//images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/df73bbed63b08096c0d2269918d11731/image.png)
+![vitrine-produto-2-pt](https://images.ctfassets.net/alneenqid6w5/3SY8POqXIAK0Qi2lWax8qq/df73bbed63b08096c0d2269918d11731/image.png)
   - **Vitrine de resultado de buscas:** exibirá produtos de um resultado de busca que você definir. Adicione as  seguintes informações:
     * **Título da vitrine:** nome da vitrine que  será exibido na página.
     * **Imagem da busca:** imagem que representará a seleção de produtos na vitrine.
     * **Nome da busca:** nome da busca que será exibido na página.
     * **Termo de busca:** termo de busca que será referência dos produtos.
-![vitrine-busca-pt](//images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/5c7a481b24a5639cb70fbfc91df13a5d/image.png)
+![vitrine-busca-pt](https://images.ctfassets.net/alneenqid6w5/2nOoe8dF1IaF1YPIr3N3dV/5c7a481b24a5639cb70fbfc91df13a5d/image.png)
 Quando o vendedor clicar no termo de busca, ele será direcionado para o resultado de buscas que foi determinado em **Termo de busca**. Você também poderá incluir até 10 buscas em cada vitrine. Veja o resultado na imagem abaixo:
-![vitrine-busca-2-pt](//images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/ed37b9e0861094d9b2b74c3f28e1a41b/image.png)
+![vitrine-busca-2-pt](https://images.ctfassets.net/alneenqid6w5/s6MJ80nGy16Ex39NnPwnT/ed37b9e0861094d9b2b74c3f28e1a41b/image.png)
 <ol start="6">
   <li>Depois de criar as seções, clique em <code>Salvar</code>, em seguida, clique em <code>Publicar</code> e <code>Publicar agora</code> para finalizar.</li>
 </ol> 
 - **Vitrine de coleção:** exibirá produtos da coleção que você definir. Adicione as seguintes informações: **Título da vitrine:** nome da vitrine que será exibido na página. **ID da coleção:** número do identificador da coleção que será exibido na página.
 
-![Vitrine-PT](//images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/d83fcc5ea60cc763f33f1cc3bab74c6f/Vitrine-PT.png)
+![Vitrine-PT](https://images.ctfassets.net/alneenqid6w5/4hppMA8Zky77l93af8W6ks/d83fcc5ea60cc763f33f1cc3bab74c6f/Vitrine-PT.png)
 
 A publicação da vitrine entrará na fila de indexação e estará publicada em torno de alguns  segundos.
 
@@ -92,13 +92,13 @@ A publicação da vitrine entrará na fila de indexação e estará publicada em
 2. Clique no botão <i class="fas fa-cog"></i>. 
 3. Selecione a aba **Código**.
 4. Selecione na aba lateral o arquivo `checkout-instore-custom-js`.
-![checkout-instore-custom-js-file](//images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/5a409dc3b01459cb8957e398f79a8c42/image.png)
+![checkout-instore-custom-js-file](https://images.ctfassets.net/alneenqid6w5/6JgOUD4YUDyArNzUkgzIVJ/5a409dc3b01459cb8957e398f79a8c42/image.png)
 5. No objeto `window.INSTORE_CONFIG`, adicione a flag `enableExplore: true,`.
-![window.INSTORE_CONFIG](//images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/08b22d0623a7e72a032872e838c114f6/image.png)
+![window.INSTORE_CONFIG](https://images.ctfassets.net/alneenqid6w5/6kpTp7g4zRuIsyYGdo5Bio/08b22d0623a7e72a032872e838c114f6/image.png)
 6. Clique em <i class="fas fa-save"></i> `Salvar`. 
 7. Opcionalmente, você pode determinar que a página inicial do vendedor seja a página de anúncios. Para isso, adicione a flag `initialPage : 'advertisements',` no objeto `window.INSTORE_CONFIG`.
 
-![initialPage : advertisements](//images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/eaac77cd87a26f72436209229c733fa4/image.png)
+![initialPage : advertisements](https://images.ctfassets.net/alneenqid6w5/1zS4dgPnw7Q0ZP2w0thQdt/eaac77cd87a26f72436209229c733fa4/image.png)
 
 ## Acessar os anúncios no VTEX Sales App
 
@@ -107,4 +107,4 @@ No VTEX Sales App, o vendedor terá a possibilidade de acessar a página de anú
 * **Página inicial:** se o administrador da loja cadastrou previamente a página de anúncios como a página inicial do vendedor, ao efetuar login na plataforma, o vendedor será direcionado diretamente para a página de anúncios. Essa configuração garante que os vendedores estejam sempre atualizados sobre os anúncios e promoções relevantes, assim que acessarem o sistema.
 * **Menu Explorar:** caso a página de anúncios não seja a página inicial do vendedor, ela ainda pode ser facilmente acessada por meio do menu **Explorar**. Para acessar a página de anúncios, o vendedor deve clicar no menu **Explorar**. Isso levará o vendedor diretamente à página de anúncios, onde poderá visualizar e interagir com os produtos e promoções disponíveis.
 
-![vitrine-sale-app-pt](//images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/40b0fd419c940ec568889b2cb4f004eb/image.png)
+![vitrine-sale-app-pt](https://images.ctfassets.net/alneenqid6w5/3YddBVVXNGJiVWfDK1xUrg/40b0fd419c940ec568889b2cb4f004eb/image.png)
diff --git a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
index 6b16f7591..06992835a 100644
--- a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
@@ -48,7 +48,7 @@ Atualmente a VTEX disponibiliza um único formato de anúncio: resultados de pes
 6. Selecione os produtos que deseja anunciar por meio de uma das opções a seguir:
 
    * __Procurar produtos por EAN:__ buscar produtos do seu catálogo por EAN.
-   * __Carregar arquivo:__ enviar um arquivo CSV com uma lista de códigos EAN e lances, conforme [este exemplo](//assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/ca7ebe3a7ac8cc99bd8f9e843a7bdf98/teste-ads.csv). Os EANs são obrigatórios e os lances opcionais no arquivo.
+   * __Carregar arquivo:__ enviar um arquivo CSV com uma lista de códigos EAN e lances, conforme [este exemplo](https://assets.ctfassets.net/alneenqid6w5/37tlx8GVGFxhOS48l73Ehz/ca7ebe3a7ac8cc99bd8f9e843a7bdf98/teste-ads.csv). Os EANs são obrigatórios e os lances opcionais no arquivo.
 
 7. Clique em `Salvar`.
 8. Na seção *Orçamento, bid e cronograma*, clique no botão de editar <i class="fas fa-pencil-alt"></i>.
@@ -104,7 +104,7 @@ Você pode pausar um produto específico da sua campanha. Desta forma, o anúnci
 
 Na tela inicial do app [VTEX Ad Network](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), você também encontra informações relativas às suas campanhas em andamento.
 
-![vtex_ad_network_create_campaign_PT](//images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/93a50fdced1479a4deea8072a6a9ca6b/vtex_ad_network_create_campaign.png)
+![vtex_ad_network_create_campaign_PT](https://images.ctfassets.net/alneenqid6w5/3b6zZAI4R3cC9Jd1rGPwtn/93a50fdced1479a4deea8072a6a9ca6b/vtex_ad_network_create_campaign.png)
 
 Na parte superior, estão dados agregados:
 
diff --git a/docs/tutorials/pt/affiliates-program-app.md b/docs/tutorials/pt/affiliates-program-app.md
index ad2d0a429..db8b7c58d 100644
--- a/docs/tutorials/pt/affiliates-program-app.md
+++ b/docs/tutorials/pt/affiliates-program-app.md
@@ -40,11 +40,11 @@ O aplicativo cria três tipos de páginas para os afiliados, que dispõem delas
 
 A **página do afiliado** é a URL da loja VTEX que ele compartilha com os clientes. Veja um exemplo na imagem a seguir:
 
-![print_affiliates_url_pt](//images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/1e1373a555c8f61b2e4b4af691f4246c/affiliate-url.png)
+![print_affiliates_url_pt](https://images.ctfassets.net/alneenqid6w5/63BnppaNSakcI7YJVX2mAV/1e1373a555c8f61b2e4b4af691f4246c/affiliate-url.png)
 
 A **página de perfil do afiliado** é uma interface pela qual ele pode acompanhar e gerenciar seus pedidos e comissões. Veja um exemplo na imagem a seguir:
 
-![affiliate_profile_page_pt](//images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/1d8a0e06794d7ea915fcb3c12154f3a3/affiliate-profile-page.png)
+![affiliate_profile_page_pt](https://images.ctfassets.net/alneenqid6w5/7kNS1iqcYLpB7roih4QdiF/1d8a0e06794d7ea915fcb3c12154f3a3/affiliate-profile-page.png)
 
 A **página de cadastro** permite que os próprios interessados em se tornar afiliados preencham seus dados para solicitar registro junto a sua loja VTEX.
 
@@ -72,7 +72,7 @@ A página **Gerenciamento de afiliados **permite realizar as seguintes ações:
 - [Visualizar detalhes do afiliado](#visualizar-detalhes-do-afiliado)
 - [Editar afiliado](#editar-afiliado)
 
-![affiliates_management_page_pt](//images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6bf53421511963ec9f96265646c3c0e5/affiliates_management_page_pt.jpg)
+![affiliates_management_page_pt](https://images.ctfassets.net/alneenqid6w5/7E41Gki569BjcMFnhsttH9/6bf53421511963ec9f96265646c3c0e5/affiliates_management_page_pt.jpg)
 
 ### Adicionar afiliado
 
@@ -119,7 +119,7 @@ A página **Gerenciamento de pedidos** permite realizar as seguintes ações:
 - [Exportar lista de pedidos](#exportar-lista-de-pedidos)
 - [Visualizar detalhes do pedido](#visualizar-detalhes-do-pedido)
 
-![orders_management_page_pt](//images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/ef737b1a333add24b39bad8a1b75d12e/orders_management_page_pt.jpg)
+![orders_management_page_pt](https://images.ctfassets.net/alneenqid6w5/4oecP3rDffWqrP0KtvOhrp/ef737b1a333add24b39bad8a1b75d12e/orders_management_page_pt.jpg)
 
 ### Acompanhar dashboard
 
@@ -172,7 +172,7 @@ A página **Gerenciamento de comissões** permite realizar as seguintes ações:
 - [Importar comissões](#importar-comissoes)
 - [Fazer o download da última importação](#fazer-o-download-da-ultima-importacao)
 
-![commissions_ management_page_pt](//images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/edebf47b68608fb0c12200421c79b770/commissions__management_page_pt.jpg)
+![commissions_ management_page_pt](https://images.ctfassets.net/alneenqid6w5/4sPaoOQE8vAbN9tsCMS7zt/edebf47b68608fb0c12200421c79b770/commissions__management_page_pt.jpg)
 
 ### Pesquisar comissões
 
diff --git a/docs/tutorials/pt/all-orders.md b/docs/tutorials/pt/all-orders.md
index c6d043d15..16ba6e8a7 100644
--- a/docs/tutorials/pt/all-orders.md
+++ b/docs/tutorials/pt/all-orders.md
@@ -28,7 +28,7 @@ A página **Todos os Pedidos** permite que lojistas acompanhem os pedidos da sua
 
 A seguir exploraremos os componentes e ações incluídos na página.
 
-![Order Listing EN](//images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/90dad9da099d53164009d4a428d2f731/Order_Listing_EN.gif)
+![Order Listing EN](https://images.ctfassets.net/alneenqid6w5/683JysQxHoXao2zRxQCJ6x/90dad9da099d53164009d4a428d2f731/Order_Listing_EN.gif)
 
 Além de pesquisar pedidos em **Pedidos > Todos os pedidos**, você pode buscar pedidos a partir de qualquer página no Admin VTEX usando a barra de busca global no topo da página. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
 
@@ -164,7 +164,7 @@ Confira a seguir mais detalhes sobre cada coluna:
 
 ## VTEX DO
 
-![VTEX Do overview PT](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
+![VTEX Do overview PT](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
 
 O [VTEX DO](https://help.vtex.com/pt/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu) é um gerenciador de tarefas criadas automaticamente pelo Admin VTEX, que requerem uma ação manual da equipe de ecommerce. 
 
diff --git a/docs/tutorials/pt/amaro-integration.md b/docs/tutorials/pt/amaro-integration.md
index 67bcb3a5b..ef71b0559 100644
--- a/docs/tutorials/pt/amaro-integration.md
+++ b/docs/tutorials/pt/amaro-integration.md
@@ -17,7 +17,7 @@ subcategory: 4uqMnZjwBO04uWgCom8QiA
 
 Fundada em 2012, a [AMARO](https://amaro.com/br/pt/) é uma marca brasileira de varejo digital especializada em moda feminina. Desde 2020, a empresa atua como marketplace por meio de uma curadoria de marcas da própria empresa.
 
-![Integração AMARO](//images.ctfassets.net/alneenqid6w5/2hQ76hgXTPOwEuP4Upq1vO/125a089a5f04ad2f910a6ff3c3f69f7b/Amaro_Logo.png)
+![Integração AMARO](https://images.ctfassets.net/alneenqid6w5/2hQ76hgXTPOwEuP4Upq1vO/125a089a5f04ad2f910a6ff3c3f69f7b/Amaro_Logo.png)
 
 A Amaro é agora [conector certificado](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro), disponível para parceria com clientes VTEX. Este guia orienta o seller a configurar a integração, sendo parte do processo no Admin VTEX e parte da AMARO. Para isso, as etapas são as seguintes:
 
diff --git a/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
index 9782e35d7..2d85f99d8 100644
--- a/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
@@ -111,7 +111,7 @@ Para instalar o aplicativo, acesse a App Store VTEX:
 As configurações feitas no campo Automatic Invoice serão aplicadas a todos os pedidos.
 </div>
 
-![MCF](//images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/7e61a4ea7adc5595f583f55dd644b99d/Amazon_MCF_PT.PNG)
+![MCF](https://images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/7e61a4ea7adc5595f583f55dd644b99d/Amazon_MCF_PT.PNG)
 
 ### Integração do catálogo
 
diff --git a/docs/tutorials/pt/amazon-offer-matching.md b/docs/tutorials/pt/amazon-offer-matching.md
index 151206b0a..733e52cde 100644
--- a/docs/tutorials/pt/amazon-offer-matching.md
+++ b/docs/tutorials/pt/amazon-offer-matching.md
@@ -19,7 +19,7 @@ Toda vez que um [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeo
 
 O EAN cadastrado na VTEX é utilizado para fazer a equivalência com os [ASINs](https://associados.amazon.com.br/resource-center/asin-amazon?ac-ms-src=rc-home-card) (*Amazon Standard Identification Number, ou, Número de Identificação Padrão da Amazon*) correspondentes na Amazon. Para realizar o pareamento entre o EAN e o ASIN, é necessário realizar o matching manual. A correspondência entre EAN e ASINs precisa ser exata para que os anúncios sejam vinculados corretamente.   
 
-![Overview match de anúncios](//images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/61c986c2318575171d6f248e70aa7f15/Match-an__ncios-Amazon.gif)
+![Overview match de anúncios](https://images.ctfassets.net/alneenqid6w5/3SrhTyS3Cpy2xxWvEA3M88/61c986c2318575171d6f248e70aa7f15/Match-an__ncios-Amazon.gif)
 
 ## Aba Oportunidade  
 Na aba __Oportunidade__, o seller pode realizar o match dos produtos enviados à Amazon individualmente ou em massa, realizar busca por nome do produto e clicando no ícone <i class="fas fa-ellipsis-v"></i> o seller poderá escolher entre `ver detalhes` dos produtos e `ver anúncio` do produto correspondente na Amazon. 
@@ -75,7 +75,7 @@ Para aprovar a correspondência o seller deve seguir os passos abaixo.
 1. Na aba `Oportunidade`, clique no ícone <i class="fas fa-ellipsis-v"></i>. 
 2. Clique no botão `Ver detalhes`.  
 3. Confira as informações que aparecerão na página.  
-![Match individual de anúncios](//images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/1ecb1d4de4389b5a6794d7e899fa4712/Match_individual_AMZ.png)  
+![Match individual de anúncios](https://images.ctfassets.net/alneenqid6w5/11Kd50vfsJccpDoHH8pSQ9/1ecb1d4de4389b5a6794d7e899fa4712/Match_individual_AMZ.png)  
 4. Conforme a análise das informações, clique em um dos botões disponíveis, `Publicar`, `Rejeitar e solicitar revisão` ou `Rejeitar`.
 
 ### Match massivo de anúncios  
@@ -85,13 +85,13 @@ Na aba de `Oportunidade`, todos os produtos listados que possuem equivalência e
 1. Na aba `Oportunidade`, marque a caixa de seleção ao lado do título dos anúncios com equivalência SKU <> ASIN.  
 Ao selecionar os produtos, aparecerá na tela o seguinte pop-up mostrando quantos produtos foram selecionados.
 
-![popup seleção mtach Amazon](//images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/7cf1452afbaa25640210af435d2e0f8b/popup_sele____o_PT.png)
+![popup seleção mtach Amazon](https://images.ctfassets.net/alneenqid6w5/3MTOQgMftiT5rsbJgKVpAD/7cf1452afbaa25640210af435d2e0f8b/popup_sele____o_PT.png)
 
 2. Ao finalizar a seleção de produtos, clique em  `Publicar selecionados`.  
 
 3. No pop-up de confirmação do *matching*, confira os anúncios selecionados e clique em `Confirmar publicação`.  
 
-![confirmação do matching Amazon](//images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4a3cd9f22575382fb03d4c8aab476048/confirma____o_do_matching_PT.png)
+![confirmação do matching Amazon](https://images.ctfassets.net/alneenqid6w5/7IWcW7ozGbMmZAH4Prec3M/4a3cd9f22575382fb03d4c8aab476048/confirma____o_do_matching_PT.png)
 
 Quando confirmado, os seus anúncios serão enviados e enfileirados para processamento. Após aprovado, o anúncio aparecerá na aba __Anúncios__, onde você pode __“ver detalhes do seu anúncio”__, __“ver anúncio sugerido pela Amazon”__ e __pesquisar anúncios__ na barra de busca.  
 
diff --git a/docs/tutorials/pt/analytics.md b/docs/tutorials/pt/analytics.md
index d70b6f16a..ed548ebe1 100644
--- a/docs/tutorials/pt/analytics.md
+++ b/docs/tutorials/pt/analytics.md
@@ -80,8 +80,8 @@ Para exportar um relatório no formato CSV, você deve seguir os passos abaixo.
 
 O relatório CSV baixado apresenta duas tabelas. A primeira tabela, ilustrada abaixo, contém informações sobre termos pesquisados e as métricas de funil (da coluna **ProductsClick** até a coluna **ProductsSold**), caso essa opção tenha sido selecionada.
 
-![search-report-term](//images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
+![search-report-term](https://images.ctfassets.net/alneenqid6w5/5b8DWfBkXE9hZzugQ2LoaP/8288fcbbc3e063a58a5118e0e582d5b8/search-report-term.png)
 
 A segunda tabela, ilustrada abaixo, mostra dados referentes ao período selecionado, exibindo a coluna Date, que informa a data da busca.
 
-![search-report-date](//images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
+![search-report-date](https://images.ctfassets.net/alneenqid6w5/1B1hwv5X36tvAv4Nt2Nxz1/005823242a5a2a258b9e3513a34bd5eb/search-report-date.png)
diff --git a/docs/tutorials/pt/analyze-a-products-reservations.md b/docs/tutorials/pt/analyze-a-products-reservations.md
index a19746ff4..f09860975 100644
--- a/docs/tutorials/pt/analyze-a-products-reservations.md
+++ b/docs/tutorials/pt/analyze-a-products-reservations.md
@@ -23,4 +23,4 @@ Para consultar as reservas autorizadas, ou seja, aquelas que ainda não tiveram
 
 Para consultar os pedidos com status `Faturado`, ou seja, pagamento já aprovado, basta clicar no número exibido na coluna **Itens em manuseio**.
 
-![Reservations GIF](//images.contentful.com/alneenqid6w5/4xUy1O7pUA66UaQkcuU0au/53f39fe9b3cbe2f4c3e2a8e6316e66a9/Reservations.gif)
+![Reservations GIF](https://images.contentful.com/alneenqid6w5/4xUy1O7pUA66UaQkcuU0au/53f39fe9b3cbe2f4c3e2a8e6316e66a9/Reservations.gif)
diff --git a/docs/tutorials/pt/analyze-suiteshare.md b/docs/tutorials/pt/analyze-suiteshare.md
index 750cb1f6e..5a15f4b3f 100644
--- a/docs/tutorials/pt/analyze-suiteshare.md
+++ b/docs/tutorials/pt/analyze-suiteshare.md
@@ -23,11 +23,11 @@ Para começar a utilizar o “**Analisar**” você precisa ter pelo menos um li
 
 Acesse dentro do painel da **VTEX Assisted Sales (SuiteShare)** a opção de _**“Analisar”**_. 
 
-![Analisar 1](//images.ctfassets.net/alneenqid6w5/XOt7xPapUQ3iYaRLYsQQK/c3c07991814af5cc1e22cebabae6fe87/image.png)
+![Analisar 1](https://images.ctfassets.net/alneenqid6w5/XOt7xPapUQ3iYaRLYsQQK/c3c07991814af5cc1e22cebabae6fe87/image.png)
 
 Acessando o painel, você terá as seguintes opções:
 
-![Analisar 2](//images.ctfassets.net/alneenqid6w5/48TT5uIth5qpUc2DG9cVWV/be55b7a75b930988a13125ca54337577/image.png)
+![Analisar 2](https://images.ctfassets.net/alneenqid6w5/48TT5uIth5qpUc2DG9cVWV/be55b7a75b930988a13125ca54337577/image.png)
 
 **1 Geral:** Uma análise geral de todos os links criados na sua conta sem diferenciar por links.
 
@@ -43,30 +43,30 @@ Clicando em geral ou no link você terá o seguinte relatório: 
 
 ## Opção de filtrar por período
 
-![Analisar 3](//images.ctfassets.net/alneenqid6w5/1tMhqp6iaxzBHrB6PBJdKH/3532a9535d8592409b681ea22af5a06a/Screenshot_2022-08-30_at_15-49-58_Analisar.png)
+![Analisar 3](https://images.ctfassets.net/alneenqid6w5/1tMhqp6iaxzBHrB6PBJdKH/3532a9535d8592409b681ea22af5a06a/Screenshot_2022-08-30_at_15-49-58_Analisar.png)
 
 **Estatísticas total, mês, semana e dia.** 
 
-![Analisar 4](//images.ctfassets.net/alneenqid6w5/2DZluzvUBtUoMY9wUdjwUF/0c2e372fdf47e2dc242a8b9d0eed8cc0/Screenshot_2022-08-30_at_15-50-06_Analisar.png)
+![Analisar 4](https://images.ctfassets.net/alneenqid6w5/2DZluzvUBtUoMY9wUdjwUF/0c2e372fdf47e2dc242a8b9d0eed8cc0/Screenshot_2022-08-30_at_15-50-06_Analisar.png)
 
 E o Tracking que está relacionado aos períodos. Você mudando os períodos altera o gráfico abaixo.
 
-![Analisar 5](//images.ctfassets.net/alneenqid6w5/3rX7ajgRqtwoN4nOUHSRDq/55f816b883428504ef08f0d6a0037c07/Screenshot_2022-08-30_at_15-50-11_Analisar.png)
+![Analisar 5](https://images.ctfassets.net/alneenqid6w5/3rX7ajgRqtwoN4nOUHSRDq/55f816b883428504ef08f0d6a0037c07/Screenshot_2022-08-30_at_15-50-11_Analisar.png)
 
 **Você também tem o relatório geográfico dividido por Países, Estados e Cidades.** 
 
-![Analisar 6](//images.ctfassets.net/alneenqid6w5/5RfLQis64rfCy3ANOqhJPP/48f8adc0ecf35cffb1f5f692bb61142b/Screenshot_2022-08-30_at_15-50-15_Analisar.png)
+![Analisar 6](https://images.ctfassets.net/alneenqid6w5/5RfLQis64rfCy3ANOqhJPP/48f8adc0ecf35cffb1f5f692bb61142b/Screenshot_2022-08-30_at_15-50-15_Analisar.png)
 
 **Referência de onde veio os cliques** - Sites (domínios) onde os seus clientes viram seus links e clicaram (aqui você descobrirá qual rede social ou canal de aquisição que você compartilhou os seus link ou utiliza seu chat e está tendo melhor conversão). Agora também é possível monitorar os acessos via QRcode.
 
-![Analisar 7](//images.ctfassets.net/alneenqid6w5/1a0BpP3gTuD31CCkWLP5tJ/033e1a5fcc4df17b3fb1eee67eac5c7d/Screenshot_2022-08-30_at_15-50-21_Analisar.png)
+![Analisar 7](https://images.ctfassets.net/alneenqid6w5/1a0BpP3gTuD31CCkWLP5tJ/033e1a5fcc4df17b3fb1eee67eac5c7d/Screenshot_2022-08-30_at_15-50-21_Analisar.png)
 
 **Páginas URL de onde vieram os acessos** - Inclusive os QRcodes. 
 
-![Analisar 8](//images.ctfassets.net/alneenqid6w5/4aoekMLr0yXq1ip706jHbm/1c014e91910e44276d0722b0b86b7fe4/Screenshot_2022-08-30_at_15-50-25_Analisar.png)
+![Analisar 8](https://images.ctfassets.net/alneenqid6w5/4aoekMLr0yXq1ip706jHbm/1c014e91910e44276d0722b0b86b7fe4/Screenshot_2022-08-30_at_15-50-25_Analisar.png)
 
 - **Navegadores** (Chrome, Firefox, Safari e etc) e **Dispositivos** (Desktop - Windows, Macbook, Mobile - Android e IOS) utilizados pelos usuários.
 
-![Analisar 9](//images.ctfassets.net/alneenqid6w5/1kIISQHtXhbUYfzARwmUvP/55d79bc433500613da6dc478969de56f/Screenshot_2022-08-30_at_15-50-29_Analisar.png)
+![Analisar 9](https://images.ctfassets.net/alneenqid6w5/1kIISQHtXhbUYfzARwmUvP/55d79bc433500613da6dc478969de56f/Screenshot_2022-08-30_at_15-50-29_Analisar.png)
 
 Pronto, agora você já sabe analisar os seus dados.
diff --git a/docs/tutorials/pt/anapro-suiteshare.md b/docs/tutorials/pt/anapro-suiteshare.md
index 6b3bc0f9e..065b94eb9 100644
--- a/docs/tutorials/pt/anapro-suiteshare.md
+++ b/docs/tutorials/pt/anapro-suiteshare.md
@@ -21,7 +21,7 @@ Para realizar a integração acesse no seu painel da Suiteshare as integrações
 
 Na dashboard em **“Integrações”**.
 
-![Anapro 1](//images.ctfassets.net/alneenqid6w5/5Rx0RJ9BWA8p57KcBZcUSL/0c3e8ca37ea8e9cea03e89393101d19a/Screenshot_2022-08-31_at_14-42-19_Anapro.png)
+![Anapro 1](https://images.ctfassets.net/alneenqid6w5/5Rx0RJ9BWA8p57KcBZcUSL/0c3e8ca37ea8e9cea03e89393101d19a/Screenshot_2022-08-31_at_14-42-19_Anapro.png)
 
 Ou clique em _**"configurações > Integrações"**_.
 
@@ -29,15 +29,15 @@ Em vendas, selecione **Anapro CRM** e clique em **“habilitar"**.
 
 O próximo passo é acessar sua conta da **Anapro** e fazer login:
 
-![Anapro 2](//images.ctfassets.net/alneenqid6w5/27nMiiFZJwLcoZnKWUwrLc/7e2684133221c84007617fea997561d3/Screenshot_2022-08-31_at_14-42-30_Anapro.png)
+![Anapro 2](https://images.ctfassets.net/alneenqid6w5/27nMiiFZJwLcoZnKWUwrLc/7e2684133221c84007617fea997561d3/Screenshot_2022-08-31_at_14-42-30_Anapro.png)
 
 Agora, acesse o menu  **_"Configurações>Campanhas"_**.
 
-![Anapro 3](//images.ctfassets.net/alneenqid6w5/5xLCEcL4Edbf0X6wVo8k9E/d56c880d56fb273673d9899cd9cead2d/Screenshot_2022-08-31_at_14-42-35_Anapro.png)
+![Anapro 3](https://images.ctfassets.net/alneenqid6w5/5xLCEcL4Edbf0X6wVo8k9E/d56c880d56fb273673d9899cd9cead2d/Screenshot_2022-08-31_at_14-42-35_Anapro.png)
 
 Escolha a campanha da qual deseja gerar os links , clique em **"Editar"** e vá na aba **"Integração"**.
 
-![Anapro 4](//images.ctfassets.net/alneenqid6w5/SN8dBsn48blUAbY3D5A8E/840181abb9bb1a35961329dcb94248b9/Screenshot_2022-08-31_at_14-42-41_Anapro.png)
+![Anapro 4](https://images.ctfassets.net/alneenqid6w5/SN8dBsn48blUAbY3D5A8E/840181abb9bb1a35961329dcb94248b9/Screenshot_2022-08-31_at_14-42-41_Anapro.png)
 
 Na tela de **integração**, selecione a Empresa integradora e a Agência (Agente responsável pela geração do lead. Pode ser a própria incorporadora ou a Agência de marketing).
 
@@ -51,6 +51,6 @@ Agora que você tem acesso aos chaves, basta selecionar o link que deseja integr
 
 Selecione o link de captura que deseja integrar com o CRM:
 
-![Anapro 5](//images.ctfassets.net/alneenqid6w5/4oxPYJKk1ZwYJ55JOHB4JE/171a1bdd5065e46a69addcd3eabf2c66/Screenshot_2022-08-31_at_14-42-47_Anapro.png)
+![Anapro 5](https://images.ctfassets.net/alneenqid6w5/4oxPYJKk1ZwYJ55JOHB4JE/171a1bdd5065e46a69addcd3eabf2c66/Screenshot_2022-08-31_at_14-42-47_Anapro.png)
 
 Agora preencha todos os outros campos, e pronto, aproveite a integração!
diff --git a/docs/tutorials/pt/antifraud-provider.md b/docs/tutorials/pt/antifraud-provider.md
index 27ae1778a..1aff25212 100644
--- a/docs/tutorials/pt/antifraud-provider.md
+++ b/docs/tutorials/pt/antifraud-provider.md
@@ -46,14 +46,14 @@ Antes de configurar o ambiente VTEX, o provedor deve implementar o serviço back
 ### 3. Portal de administração do Antifraud Provider
 Depois de receber os dados de acesso e implementar o back-end, o provedor pode acessar a ferramenta de aprovação por meio do Admin da VTEX. Para fazer isso, você deve intalar a App do Antifraud Provider no menu Apps:
 
-![print5](//images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
+![print5](https://images.ctfassets.net/alneenqid6w5/50yLGa6LOU0cuIMUOeSOKq/c236baf425467b8e14aabff5d8655c05/print5.png)
 
 Clique na App instalada ou acesse `https://{{AccountName}}.myvtex.com/admin/antifraud-provider`, substituindo `{{AccountName}}` pelo nome da sua conta na plataforma. Nesse ambiente, é possível registrar os dados de configuração do back-end do provedor e fazer testes de integração.
 
-![print6](//images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
+![print6](https://images.ctfassets.net/alneenqid6w5/2ziFhnDDHWMKE6QSIOIW4W/a0d3301c92157971275546ca2745f7b1/print6.png)
 
 ### 4. Configurações iniciais
-![print1](//images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
+![print1](https://images.ctfassets.net/alneenqid6w5/2RbsDjzeIgas064w8AKqS2/c0dc76877d74758ed5976bc729d26774/print1.png)
 
 Ao acessar  o ambiente pelo link descrito no item anterior, você verá um formulário. Preencha os campos de acordo com as indicações abaixo:
 
@@ -77,7 +77,7 @@ Depois de preencher os campos corretamente, o sistema vai verificar as transaç
 
 Os testes que deverão ser feitos na sua integração antes de mandá-la para a avaliação da VTEX são exibidos no módulo seguinte. Você pode selecionar quais testes deseja rodar, mas para que sua integração passe pela análise da nossa equipe, __todos eles precisam ser realizados__. Portanto, recomendamos que todos eles permaneçam selecionados.
 
-![print2](//images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
+![print2](https://images.ctfassets.net/alneenqid6w5/5EVuBF31ramsiYuKa2wkwO/91a84f94f4030507b9635b150067965f/print2.png)
 
 ### 5. Testes
 Ao clicar no botão __Execute tests__, o Antifraud Provider vai aplicar os testes na sua integração para os diferentes cenários possíveis. É importante lembrar que __todos eles são obrigatórios__ e, para executá-los, seu serviço precisa estar em HTTPS. Os testes são:
@@ -107,11 +107,11 @@ Para cada teste do Antifraud Provider Protocol, enviamos um final de ID específ
 ### 6. Resultados
 Depois de executar os testes, o sistema retorna os resultados, tanto positivos quanto negativos. O sistema também traz a informação dos resultados esperados para cada teste. Assim, você tem mais visibilidade do que deve ser ajustado em caso de erro.
 
-![print3](//images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
+![print3](https://images.ctfassets.net/alneenqid6w5/4k4uoEtGb6CeoAAWasM4Ya/c718a92d5196f553c5531511a7e14b92/print3.png)
 
 Para visualizar de forma detalhada cada ação realizada pela integração (e, assim, identificar possíveis erros), basta clicar no link __Show logs__. Uma lista com as informações completas dos eventos que aconteceram durante o teste vai ser exibida abaixo dos resultados.
 
-![print4](//images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
+![print4](https://images.ctfassets.net/alneenqid6w5/FeHanjGPxQqG8eoUw2MG0/a804453e7cc01ef7ef8d1b35e8960b94/print4.png)
 
 Quando sua integração tiver passado em todos os testes com sucesso, basta abrir um ticket no [Help da VTEX](https://help.vtex.com/pt/support "VTEX Help") informando a conclusão. Porém, antes de abrir o ticket, certifique-se que você possui as seguintes informações:
 
@@ -135,7 +135,7 @@ Use a URL `https://{{AccountName}}.myvtex.com/admin/license-manager/#/home`, sub
 Depois que a integração com seu antifraude estiver aprovada, um conector será disponibilizado para que os lojistas VTEX o configurem em seus respectivos websites. Para fazer isso, além do contrato com sua empresa, o lojista vai precisar ter em mãos duas chaves: "X-PROVIDER-API-AppKey" e "X-PROVIDER-API-AppToken". 
 
 Um exemplo de como vai ficar a tela de configuração do antifraude para o lojista VTEX:
-![print8](//images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
+![print8](https://images.ctfassets.net/alneenqid6w5/2v00lYz2UsW4YsaSycESio/1dc399bea5e2a75a04d1867646c4e223/print8.png)
 
 Essas chaves devem ser disponibilizadas por você e vão servir para identificar a loja que contratou e está usando seu serviço de antifraude.
 
diff --git a/docs/tutorials/pt/application-keys.md b/docs/tutorials/pt/application-keys.md
index 07266f570..290a78422 100644
--- a/docs/tutorials/pt/application-keys.md
+++ b/docs/tutorials/pt/application-keys.md
@@ -62,7 +62,7 @@ Para criar chaves de aplicação internas na sua conta, siga os passos abaixo.
 
     Você será redirecionado(a) para a página **Minhas chaves**, ilustrada abaixo. Essa página lista todas as [chaves de aplicação internas](#chaves-de-aplicacao-internas).
 
-    ![Minhas chaves](//images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/56384e78cd25d545b8bfb8ee603a4c59/minhas-chaves-pt.png)
+    ![Minhas chaves](https://images.ctfassets.net/alneenqid6w5/1pSqVIzYaiCJO3RkJUoXZQ/56384e78cd25d545b8bfb8ee603a4c59/minhas-chaves-pt.png)
 
     Estes são os campos visíveis na página **Minhas chaves**:
 
@@ -114,7 +114,7 @@ Ao editar uma chave de aplicação, você pode:
 
 Após ter adicionado perfis de acesso à chave de aplicação, ela será exibida na página **Chaves de aplicação**.
 
-![Chaves de aplicação](//images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/b21ce0058da588e889f23ef46582b91c/appkeys-pt.png)
+![Chaves de aplicação](https://images.ctfassets.net/alneenqid6w5/2wGtLJjEnzTf1VJmkFcRhm/b21ce0058da588e889f23ef46582b91c/appkeys-pt.png)
 
 Estes são os campos visíveis na página **Chaves de aplicação**:
 
diff --git a/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
index b6999c991..3cb3e73bd 100644
--- a/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
@@ -25,7 +25,7 @@ Essa aprovação pode ser feita manualmente no módulo Pedidos, conforme abaixo.
 2. Clique sobre a transação desejada.
 3. Clique no botão **Notificar Pagamento**.
 
-![NotificarPT](//images.ctfassets.net/alneenqid6w5/6jQnmZtHygY4csKym2kC0e/f48943b3a025d87ab59a724e17188df3/NotificarPT.png)
+![NotificarPT](https://images.ctfassets.net/alneenqid6w5/6jQnmZtHygY4csKym2kC0e/f48943b3a025d87ab59a724e17188df3/NotificarPT.png)
 
 **Após a aprovação do pagamento, o pedido entrará no fluxo normal de compra.**
 
diff --git a/docs/tutorials/pt/apps-overview.md b/docs/tutorials/pt/apps-overview.md
index 34a2d550b..f66d35b0f 100644
--- a/docs/tutorials/pt/apps-overview.md
+++ b/docs/tutorials/pt/apps-overview.md
@@ -36,7 +36,7 @@ O menu Aplicativos permite que os comerciantes baixem novos aplicativos diretame
 
 Essas operações podem ser realizadas no menu Aplicativos do seu Admin repaginado.
 
-![Apps Overview menu PT](//images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/46e4dce503c39c70978460a967bd34b0/Apps_Overview_menu_PT.jpg)
+![Apps Overview menu PT](https://images.ctfassets.net/alneenqid6w5/2Bj2bz36YQcD1Q6cl4Pf44/46e4dce503c39c70978460a967bd34b0/Apps_Overview_menu_PT.jpg)
 
 Veja abaixo mais detalhes sobre as diferentes seções e páginas deste recurso, que em breve estará disponível no Admin repaginado.
 
diff --git a/docs/tutorials/pt/assembly-options-app.md b/docs/tutorials/pt/assembly-options-app.md
index a11ba47d6..06964b494 100644
--- a/docs/tutorials/pt/assembly-options-app.md
+++ b/docs/tutorials/pt/assembly-options-app.md
@@ -37,7 +37,7 @@ Após a instalação, a página **Catálogo > Assembly Options** se torna dispon
 
 No Admin VTEX, em **Catálogo > Assembly options**, você tem acesso a uma lista com todas as Assembly Options cadastradas na sua loja utilizando o aplicativo.
 
-![assembly-options-app](//images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
+![assembly-options-app](https://images.ctfassets.net/alneenqid6w5/7AoMYLduvKisAxKMho64m0/e2166df5fd26a7dba75c2420c19e43e9/image1.png)
 
 As informações exibidas na lista são:
 
diff --git a/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md b/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md
index b28787f6c..5ff50fd81 100644
--- a/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/assembly-options-in-vtex-sales-app.md
@@ -37,9 +37,9 @@ Existem dois cenários nos quais é possível adicionar serviços a produtos pre
 
 3. Após finalizar o processo, é possível visualizar em seu carrinho o serviço que foi selecionado, com o valor total do pedido.
 
-![Garantia estendida - PT](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/d7ed484879b2e99209db45d784227559/Cen_rio_1__T1__PT.png)
+![Garantia estendida - PT](https://images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/d7ed484879b2e99209db45d784227559/Cen_rio_1__T1__PT.png)
 
-![Carrinho - PT](//images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/c208432eab7761f4b3ace4cd75ef30db/Cen_rio_1__T2__PT.png)
+![Carrinho - PT](https://images.ctfassets.net/alneenqid6w5/2w3D5PYdqlPZs4gtGOY0VM/c208432eab7761f4b3ace4cd75ef30db/Cen_rio_1__T2__PT.png)
 
 **Cenário 2:** Seleção de múltiplos serviços
 
@@ -55,8 +55,8 @@ Existem dois cenários nos quais é possível adicionar serviços a produtos pre
 
 6. Clique no botão **Aplicar**.
 
-![Garantia estendida - PT](//images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/d7ed484879b2e99209db45d784227559/Cen_rio_1__T1__PT.png)
+![Garantia estendida - PT](https://images.ctfassets.net/alneenqid6w5/6x9bCRVpOcGLa8bilRpZ7I/d7ed484879b2e99209db45d784227559/Cen_rio_1__T1__PT.png)
 
-![Seguro - PT](//images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/be5cd06bb77bb828040cb44b8604b10b/Cen_rio_2__T2__-_PT.png)
+![Seguro - PT](https://images.ctfassets.net/alneenqid6w5/7MQkGqCSarYQTpAKT365r3/be5cd06bb77bb828040cb44b8604b10b/Cen_rio_2__T2__-_PT.png)
 
-![Ordem pedido - PT](//images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/e7f7178cf8f4c30faf5cca4bda49dcc2/Cen_rio_2__T3__-_PT.png)
+![Ordem pedido - PT](https://images.ctfassets.net/alneenqid6w5/DKPaBz21QHRDmfVoJxWs0/e7f7178cf8f4c30faf5cca4bda49dcc2/Cen_rio_2__T3__-_PT.png)
diff --git a/docs/tutorials/pt/assembly-options.md b/docs/tutorials/pt/assembly-options.md
index 70726da16..eee80ef6f 100644
--- a/docs/tutorials/pt/assembly-options.md
+++ b/docs/tutorials/pt/assembly-options.md
@@ -23,7 +23,7 @@ Uma Assembly Option é um [anexo](https://help.vtex.com/pt/tutorial/o-que-e-um-a
 
 No exemplo abaixo, uma loja oferece várias Assembly Options para o produto _Custom Bell_. Essas opções são mostradas na página do produto, onde o cliente pode selecionar as opções desejadas. Dependendo das escolhas, pode haver um custo adicional.
 
-![assembly-option-PT](//images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/4d0d0db168c8a984a69fb6462ccc9084/image.png)
+![assembly-option-PT](https://images.ctfassets.net/alneenqid6w5/3A5QzqwSI6Z9CZk3EqPrZs/4d0d0db168c8a984a69fb6462ccc9084/image.png)
 
 Você pode combinar [SKUs](https://help.vtex.com/pt/tutorial/o-que-e-um-sku--1K75s4RXAQyOuGUYKMM68u) para oferecer Assembly Options, como o _Bells add-ons Roman_ ou o _Bells add-ons 1-3 lines_ no exemplo acima. Se um item estiver esgotado, ele será exibido como indisponível.
 
@@ -61,7 +61,7 @@ O primeiro trecho`[x-y]` se refere às regras aplicadas ao grupo, e entre cada `
 |\[0-3\]#10000\[1-2\]**\[1\]**pricetable1;#20000\[0-2\]**\[0\]**pricetable2;#30000\[0-2\]**\[0\]**pricetable3 | Esse segmento define a quantidade padrão selecionada para cada SKU.                                    |
 | \[0-3\]#10000\[1-2\]\[1\]**pricetable1**;#20000\[0-2\]\[0\]**pricetable2**;#30000\[0-2\]\[0\]**pricetable3** | O segmento final indica a tabela de preços para cada item. |
 
-![assembly-option-exemplo-PT](//images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/ff463ce52bf53d528a1127d81a36eb38/image.png)
+![assembly-option-exemplo-PT](https://images.ctfassets.net/alneenqid6w5/2c4cfwQo0KisXQhlzYoxGC/ff463ce52bf53d528a1127d81a36eb38/image.png)
 
 #### Configuração do Anexo
 
diff --git a/docs/tutorials/pt/associating-a-template-with-a-layout.md b/docs/tutorials/pt/associating-a-template-with-a-layout.md
index 1f99e0475..6f4a3f1e6 100644
--- a/docs/tutorials/pt/associating-a-template-with-a-layout.md
+++ b/docs/tutorials/pt/associating-a-template-with-a-layout.md
@@ -35,4 +35,4 @@ Essa associação é feita na configuração de propriedades do layout. Para che
 6. Selecione o template que você deseja associar a esse layout.
 7. Digite `yes` para confirmar a mudança. (Este passo é necessário porque esta é uma alteração crítica para o site, já que o front-end da página será substituído.) 
 
-![CMS 4 1](//images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
+![CMS 4 1](https://images.ctfassets.net/alneenqid6w5/6ZaVxrZUn0cegcQni61zsc/58fd2f24e7b8b36636b0088d945c1204/CMS_4_1.png)
diff --git a/docs/tutorials/pt/audit.md b/docs/tutorials/pt/audit.md
index 8a6776649..7ccc82dd7 100644
--- a/docs/tutorials/pt/audit.md
+++ b/docs/tutorials/pt/audit.md
@@ -26,7 +26,7 @@ Para acessar a página do Audit no Admin VTEX, acesse **Apps > Apps instalados >
   <p>Para visualizar os eventos do Audit, é necessário ter um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> associado ao <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <em>Insights Metrics</em>.</p>
 </div>
 
-![audit-ui-pt 1](//images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/42032a1aa1700f58ffaf92b1e00ecfd2/audit-ui-pt_1.png)
+![audit-ui-pt 1](https://images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/42032a1aa1700f58ffaf92b1e00ecfd2/audit-ui-pt_1.png)
 
 ## Buscar eventos no Audit
 
@@ -52,7 +52,7 @@ Confira o passo a passo para buscar por um evento utilizando os filtros disponí
 
     Por exemplo, a busca correspondente à figura abaixo encontra resultados cujas ações são _Change Promotion Configuration_ ou _Change Coupon Configuration_ e cujo autor é `email@email.com`.
 
-    ![filtros-pt](//images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/3f1ad9727d1f0eb54168e9e68895533b/filtros-pt.png)
+    ![filtros-pt](https://images.ctfassets.net/alneenqid6w5/LQkBnce7aFlx8T1zjXYdm/3f1ad9727d1f0eb54168e9e68895533b/filtros-pt.png)
 
 7. Clique no botão `Aplicar` para obter os eventos que foram encontrados.
 
diff --git a/docs/tutorials/pt/authentication-page.md b/docs/tutorials/pt/authentication-page.md
index af810a1e6..13d45cf25 100644
--- a/docs/tutorials/pt/authentication-page.md
+++ b/docs/tutorials/pt/authentication-page.md
@@ -17,7 +17,7 @@ subcategory: 14V5ezEX0cewOMg0o0cYM6
 
 Na página Autenticação, é possível escolher quais formas de login você deseja oferecer aos compradores e operadores da sua loja VTEX. Esta página está disponível em _Configurações da conta_ > _Autenticação_.
 
-![Página de autenticação](//images.contentful.com/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/986b144c0704f780d774f8f3790ba8e6/Tela_de_Autentica____o_PT.png)
+![Página de autenticação](https://images.contentful.com/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/986b144c0704f780d774f8f3790ba8e6/Tela_de_Autentica____o_PT.png)
 
 ## Formas de login
 
diff --git a/docs/tutorials/pt/authentication.md b/docs/tutorials/pt/authentication.md
index 6372a6b65..515bd7de7 100644
--- a/docs/tutorials/pt/authentication.md
+++ b/docs/tutorials/pt/authentication.md
@@ -47,7 +47,7 @@ Na VTEX, a autenticação por login ocorre em dois contextos: na loja virtual, q
 
 Na página **Autenticação**, é possível escolher quais formas de login você deseja oferecer aos clientes da sua loja e aos usuários administrativos que terão acesso ao Admin da sua conta.
 
-![Página de autenticação](//images.contentful.com/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/986b144c0704f780d774f8f3790ba8e6/Tela_de_Autentica____o_PT.png)
+![Página de autenticação](https://images.contentful.com/alneenqid6w5/6cbXmuu9GiTfuYnIsuFKQp/986b144c0704f780d774f8f3790ba8e6/Tela_de_Autentica____o_PT.png)
 
 Confira o passo a passo a seguir para habilitar os métodos de login desejados:
 
diff --git a/docs/tutorials/pt/autocomplete.md b/docs/tutorials/pt/autocomplete.md
index 7ab448830..6d40c219e 100644
--- a/docs/tutorials/pt/autocomplete.md
+++ b/docs/tutorials/pt/autocomplete.md
@@ -53,22 +53,22 @@ Outra vantagem para o gestor da loja é o aumento de conversão, resultado dessa
 
 Essa seção exibe os termos mais buscados por outros clientes dentro do site.
 
-![PT - Autocomplete termos mais pesquisados](//images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
+![PT - Autocomplete termos mais pesquisados](https://images.ctfassets.net/alneenqid6w5/6gBULnYzroBY96Ler918qJ/de1f57f6942d1c1ec554246917f524a0/PT_-_Autocomplete_termos_mais_pesquisados.png)
 
 ## Últimas buscas efetuadas
 
 Essa seção exibe as últimas buscas efetuadas pelo cliente. Assim, é possível  iniciar a interação com a busca instantaneamente.
 
-![PT - Autocomplete historico](//images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
+![PT - Autocomplete historico](https://images.ctfassets.net/alneenqid6w5/1GXQ879Y9rEMXFKjVquys1/4f68e9d2277b02d56cb155ecf29fcfc6/PT_-_Autocomplete_historico.png)
 
 ## Sugestão de buscas
 
 Essa seção apresenta os termos pesquisados por outros usuários que se relacionam com a busca efetuada naquele momento. Além de termos, também são sugeridas categorias que estejam relacionadas com a busca.
 
-![PT - Autocomplete sugestao termos](//images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
+![PT - Autocomplete sugestao termos](https://images.ctfassets.net/alneenqid6w5/2rOg8Q94A0F8VEbueLkXDS/34faeaa87bbf7989072e3dddec7f9b04/PT_-_Autocomplete_sugestao_termos.png)
 
 ## Sugestão de produtos
 
 Essa seção apresenta os produtos que correspondem a busca efetuada naquele momento. Dessa forma, ao mostrar produtos relacionados a sua busca durante a sua digitação, diminui as desistências e dá a possibilidade do usuário efetuar uma compra mais dinâmica.
 
-![PT - Autocomplete sugestao de produtos](//images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
+![PT - Autocomplete sugestao de produtos](https://images.ctfassets.net/alneenqid6w5/1wXXgJr59cCCjz00DHA3nU/49288947b9326f3309ed7bea482a2331/PT_-_Autocomplete_sugestao_de_produtos.png)
diff --git a/docs/tutorials/pt/b2b-organization-general-settings.md b/docs/tutorials/pt/b2b-organization-general-settings.md
index 0119bd7ae..f4fccd07d 100644
--- a/docs/tutorials/pt/b2b-organization-general-settings.md
+++ b/docs/tutorials/pt/b2b-organization-general-settings.md
@@ -28,6 +28,6 @@ No Admin VTEX, acesse **Aplicativos > Organizações e centros de custo B2B > Or
     - **Status:** indica se o cadastro desta organização compradora está ativa.
     - **Campos personalizados:** contém campos adicionais de uma organização.
 
-![Configurações gerais organizações - PT](//images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/a430fb63e7953d706e1a2a60bdd4a339/Configura__es_gerais_organiza__es_-_PT.gif)
+![Configurações gerais organizações - PT](https://images.ctfassets.net/alneenqid6w5/27AqRCa9LbipRF1iFa0kXT/a430fb63e7953d706e1a2a60bdd4a339/Configura__es_gerais_organiza__es_-_PT.gif)
 
 Certifique-se de clicar em `Salvar` no canto superior direito da página após realizar qualquer alteração.
diff --git a/docs/tutorials/pt/b2b-store-settings.md b/docs/tutorials/pt/b2b-store-settings.md
index e2c7759ca..716bea9c9 100644
--- a/docs/tutorials/pt/b2b-store-settings.md
+++ b/docs/tutorials/pt/b2b-store-settings.md
@@ -30,7 +30,7 @@ Nesta página, você verá o passo a passo de como realizar as configurações g
 É possível adicionar métodos de pagamento que façam sentido para o seu negócio. Basta selecionar os métodos que deseja incluir em sua loja. 
 
 __Exemplo:__ Boleto, Cartão de Débito e Crédito, Crédito da loja. 
-![Configurando lojas B2B - General Settings + Payment Terms](//images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/96c225444f6aec8c294d0cf836c1ead1/image1.jpg)
+![Configurando lojas B2B - General Settings + Payment Terms](https://images.ctfassets.net/alneenqid6w5/7wvxJVXraGTFAheCAp8tGP/96c225444f6aec8c294d0cf836c1ead1/image1.jpg)
 ## Tabelas de preço
 Você poderá adicionar um padrão de preços das lojas adicionadas. Os valores serão default. Para entender mais sobre a criação de tabelas, acesse [Pricing](https://developers.vtex.com/docs/guides/pricing-overview).
 
@@ -38,6 +38,6 @@ Você poderá adicionar um padrão de preços das lojas adicionadas. Os valores
 
 É possível vincular sua loja diretamente a políticas comerciais e canais de vendas.
 1. Na tabela **Políticas comerciais disponíveis**, clique no vínculo que deseja incluir em sua loja e depois clique em `Adicionar Política Comercial`, e ela aparecerá na tabela **Políticas comerciais Selecionadas**.
-![Configurando lojas B2B -  Políticas comerciais ](//images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/632b5c714318cf0d613393c2d39083dd/image2.jpg)
+![Configurando lojas B2B -  Políticas comerciais ](https://images.ctfassets.net/alneenqid6w5/AsCTmvTHbdWfOnVeIiGkj/632b5c714318cf0d613393c2d39083dd/image2.jpg)
 2. Ao finalizar as configurações, clique em `Salvar`.
 
diff --git a/docs/tutorials/pt/b2b-suite-overview.md b/docs/tutorials/pt/b2b-suite-overview.md
index fd8dfb3e5..85fc18b1d 100644
--- a/docs/tutorials/pt/b2b-suite-overview.md
+++ b/docs/tutorials/pt/b2b-suite-overview.md
@@ -43,7 +43,7 @@ Para instalar o B2B Suite, siga os passos abaixo:
 2. Na página do App Store, localize o **B2B Suite** na lista de Apps exibidos ou digite **B2B Suite** na barra de busca da página.
 3. Em seguida, clique para instalar o App.
 
-![Instalação B2B Suite - PT](//images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/26332dc3085e6ff753cb644524a0ec61/Instala__o_B2B_Suite_-_PT.gif)
+![Instalação B2B Suite - PT](https://images.ctfassets.net/alneenqid6w5/6FXd6YnL0yCzDalN9BlOTO/26332dc3085e6ff753cb644524a0ec61/Instala__o_B2B_Suite_-_PT.gif)
 
 ## Conjunto de aplicativos do B2B Suite
 
diff --git a/docs/tutorials/pt/bank-reconciliations.md b/docs/tutorials/pt/bank-reconciliations.md
index 5f274baff..f4e53b749 100644
--- a/docs/tutorials/pt/bank-reconciliations.md
+++ b/docs/tutorials/pt/bank-reconciliations.md
@@ -36,7 +36,7 @@ Após receber o arquivo do banco e salvá-lo em sua máquina, conforme citado ac
 
 Assim que selecionar o arquivo, a plataforma começará a processá-lo e registrará no histórico quantos pagamentos foram conciliados com sucesso ou erro. Os pagamentos que forem conciliados com sucesso, atualizarão os status dos pedidos para Pagamento Aprovado.
 
-![upload-arquivo-ret](//images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/73a25815cf3bd17cb7c92f6f01407f7e/uploadret.JPG)
+![upload-arquivo-ret](https://images.ctfassets.net/alneenqid6w5/3KDKXLTwzYy1W9PNKGfIyT/73a25815cf3bd17cb7c92f6f01407f7e/uploadret.JPG)
 
 ## Visualizar o histórico
 
@@ -48,7 +48,7 @@ Dentre os detalhes, é possível saber: o banco ao qual o boleto pertence, o tot
 2. Em **Histórico**, clique em uma das datas das operações de conciliação bancária realizadas.
 3. Em **Mais detalhes dos pagamentos**, clique em **Conciliados com Sucesso** ou **Não conciliados** para verificar os detalhes das operações realizadas em um determinado banco. 
 
-![historico-conciliacao](//images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/f349ccb45ed613af59dca2de908fa01a/historico_conciliacao.jpg)
+![historico-conciliacao](https://images.ctfassets.net/alneenqid6w5/7K6sF9KZlBA00tbSp4q0pC/f349ccb45ed613af59dca2de908fa01a/historico_conciliacao.jpg)
 
 ## Payclub
 
@@ -59,4 +59,4 @@ Aqui é possível fazer o download dos pagamentos do dia que foram feitos atrav
 3. Selecione a data que desejar no calendário.
 4. Clique em **Baixar arquivo**.
 
-![donwload-arquivo-conciliação](//images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/61af99bfe4978eea981dfe694308f8f4/Download_Concilia____o.JPG)
+![donwload-arquivo-conciliação](https://images.ctfassets.net/alneenqid6w5/78K7wW5QAaA0tVCJTBwpDH/61af99bfe4978eea981dfe694308f8f4/Download_Concilia____o.JPG)
diff --git a/docs/tutorials/pt/banners.md b/docs/tutorials/pt/banners.md
index 2ec153c42..29d04dc21 100644
--- a/docs/tutorials/pt/banners.md
+++ b/docs/tutorials/pt/banners.md
@@ -34,7 +34,7 @@ No Admin VTEX, a página **Storefront** > **Banners** exibe a listagem dos banne
 * [Editar um banner](#editar-banner)
 * [Deletar um banner](#deletar-banner) 
 
-![banners-intro-pt](//images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
+![banners-intro-pt](https://images.ctfassets.net/alneenqid6w5/1MDMMN6lidEIiDwaDalvNU/76b18f06e75a40e33c5a84882a247ac2/image.png)
 
 A página apresenta as seguintes informações: 
 
diff --git a/docs/tutorials/pt/beta-price-configuration.md b/docs/tutorials/pt/beta-price-configuration.md
index 3b94d1c91..fbf546876 100644
--- a/docs/tutorials/pt/beta-price-configuration.md
+++ b/docs/tutorials/pt/beta-price-configuration.md
@@ -72,11 +72,11 @@ Para criar uma nova regra, siga os passos a seguir:
 
   b. **Ativar em condições específicas:** a tabela de preço será ativada segundo as condições configuradas na regra. Veja as possibilidades de configuração com as imagens a seguir:
 
-  ![config-preco-PT](//images.ctfassets.net/alneenqid6w5/4U3RNX4VaQm3EPUO3JX0Pu/d8ef577cd574c3bf765b38c63f08bd7b/config-preco-PT.png)
+  ![config-preco-PT](https://images.ctfassets.net/alneenqid6w5/4U3RNX4VaQm3EPUO3JX0Pu/d8ef577cd574c3bf765b38c63f08bd7b/config-preco-PT.png)
 
-  ![config-preco2-PT](//images.ctfassets.net/alneenqid6w5/3RYREfiFKxAPqodf8uCAy6/3500e92785edeef7184e5f4f273f1f38/config-preco2-PT.png)
+  ![config-preco2-PT](https://images.ctfassets.net/alneenqid6w5/3RYREfiFKxAPqodf8uCAy6/3500e92785edeef7184e5f4f273f1f38/config-preco2-PT.png)
 
-  ![config-preco3-PT](//images.ctfassets.net/alneenqid6w5/56mqdIxfxQMDOzzod8Juc5/e14da5f91d1b77a354ee9319ab5d6470/config-preco3-PT.png)
+  ![config-preco3-PT](https://images.ctfassets.net/alneenqid6w5/56mqdIxfxQMDOzzod8Juc5/e14da5f91d1b77a354ee9319ab5d6470/config-preco3-PT.png)
 
 7. Clique em **Confirmar**. 
 
diff --git a/docs/tutorials/pt/billing-module-overview.md b/docs/tutorials/pt/billing-module-overview.md
index af16c2237..72bf0c224 100644
--- a/docs/tutorials/pt/billing-module-overview.md
+++ b/docs/tutorials/pt/billing-module-overview.md
@@ -23,7 +23,7 @@ Para acessar essa página, clique no seu **avatar**, que pode ser identificado p
 Somente usuários com o perfil de acesso <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> ou com recursos de <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> vinculados ao seu perfil de acesso terão acesso a essa seção do Admin VTEX.
             </div>
 
-![Admin v4 Faturas menu PT](//images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/3102e348f966683a32c36512bdf2ba16/Admin_v4_Faturas_menu_PT.jpg)
+![Admin v4 Faturas menu PT](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/3102e348f966683a32c36512bdf2ba16/Admin_v4_Faturas_menu_PT.jpg)
 
 Veja abaixo mais detalhes sobre as diferentes seções e páginas deste recurso.
 
diff --git a/docs/tutorials/pt/bitrix24.md b/docs/tutorials/pt/bitrix24.md
index 9993acd58..789b0e35c 100644
--- a/docs/tutorials/pt/bitrix24.md
+++ b/docs/tutorials/pt/bitrix24.md
@@ -21,38 +21,38 @@ Para realizar a integração acesse no seu painel da VTEX Assisted Sales (Suite
 
 Na dashboard em **Integrações”**, clique em **Ver todas as integrações**. Ou clique em _**Configurações > Integrações**_.
 
-![Bitrix24_1](//images.ctfassets.net/alneenqid6w5/1FNycssXpEsblACNCy0eJx/5c5a7b399d4c6051e312e1b3b897a257/Bitrix24_1.png)
+![Bitrix24_1](https://images.ctfassets.net/alneenqid6w5/1FNycssXpEsblACNCy0eJx/5c5a7b399d4c6051e312e1b3b897a257/Bitrix24_1.png)
 
 Selecione o Bitrix24 sales e clique em **Integrar**.
 
 Selecione o [formulário de captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseja conectar.
 
-![Bitrix24_2](//images.ctfassets.net/alneenqid6w5/12eiYCSAdxKWQnXnG5TAGT/d2f2331416d7815b2ebb4cf6441637b6/Bitrix24_2.png)
+![Bitrix24_2](https://images.ctfassets.net/alneenqid6w5/12eiYCSAdxKWQnXnG5TAGT/d2f2331416d7815b2ebb4cf6441637b6/Bitrix24_2.png)
 
 Dentro do Bitrix24, no menu a esquerda, clique em _**Aplicativos > Market**_.
 
-![Bitrix24_3](//images.ctfassets.net/alneenqid6w5/2fy2TlaXC9OJ4x9m8OT7Fw/a78dc1307d0865f1f05bc9c134d650d3/Bitrix24_3.png)
+![Bitrix24_3](https://images.ctfassets.net/alneenqid6w5/2fy2TlaXC9OJ4x9m8OT7Fw/a78dc1307d0865f1f05bc9c134d650d3/Bitrix24_3.png)
 
 No menu superior, clique em **Recursos para desenvolvedores**.
 
-![Bitrix24_4](//images.ctfassets.net/alneenqid6w5/5ICON3qpUxJ6gvoJWrmWC6/82d44a2fb708c421aa4b05a5095ae5f6/Bitrix24_4.png)
+![Bitrix24_4](https://images.ctfassets.net/alneenqid6w5/5ICON3qpUxJ6gvoJWrmWC6/82d44a2fb708c421aa4b05a5095ae5f6/Bitrix24_4.png)
 
 Na página a seguir, clique em **Outro**.
 
-![Bitrix24_5](//images.ctfassets.net/alneenqid6w5/1gUel7t9l6x8DleZL10MFI/9afa3e49bf93432d0417b87621ff23d8/Bitrix24_5.png)
+![Bitrix24_5](https://images.ctfassets.net/alneenqid6w5/1gUel7t9l6x8DleZL10MFI/9afa3e49bf93432d0417b87621ff23d8/Bitrix24_5.png)
 
 Na página a seguir, clique em **Webhook de entrada**.
 
-![Bitrix24_6](//images.ctfassets.net/alneenqid6w5/6hUYhcVQE2qC2NclWfRXR7/0a2e1bfeca200c8efd6d5b10a7f0e5a5/Bitrix24_6.png)
+![Bitrix24_6](https://images.ctfassets.net/alneenqid6w5/6hUYhcVQE2qC2NclWfRXR7/0a2e1bfeca200c8efd6d5b10a7f0e5a5/Bitrix24_6.png)
 
 Na página a seguir, troque o **Criador de pedido** para `crm.lead.add`.
 
-![Bitrix24_7](//images.ctfassets.net/alneenqid6w5/4HUNOCnKRZQPS0HfB5cTR9/0aeae79037ae3093e2f1cef6623cd124/Bitrix24_7.png)
+![Bitrix24_7](https://images.ctfassets.net/alneenqid6w5/4HUNOCnKRZQPS0HfB5cTR9/0aeae79037ae3093e2f1cef6623cd124/Bitrix24_7.png)
 
 Copie a URL gerada no campo URL e clique em salvar. 
 
 A URL copiada deve ser colada no campo **URL do Webhook** painel da VTEX Assisted Sales (SuiteShare) para cada um dos links que deseja integrar:
 
-![Bitrix24_8](//images.ctfassets.net/alneenqid6w5/5ApW3fkTAHVrbhrbmbPqf8/8e04b9411b8cba3be9a26b51a26bfeda/Bitrix24_8.png)
+![Bitrix24_8](https://images.ctfassets.net/alneenqid6w5/5ApW3fkTAHVrbhrbmbPqf8/8e04b9411b8cba3be9a26b51a26bfeda/Bitrix24_8.png)
 
 Pronto, integração finalizada!
diff --git a/docs/tutorials/pt/black-friday-checklist.md b/docs/tutorials/pt/black-friday-checklist.md
index 7a744537e..3164ea452 100644
--- a/docs/tutorials/pt/black-friday-checklist.md
+++ b/docs/tutorials/pt/black-friday-checklist.md
@@ -23,7 +23,7 @@ Mas a Black Friday é também uma data que traz boa dose de medo para os lojista
 
 Foi por isso que fizemos este post: para te ajudar a garantir que tudo esteja em ordem no tempo certo, de modo que seu negócio fique livre das pegadinhas em que todos os anos caem os lojistas menos preparados.
 
-![mike-petrucci-131817](//images.contentful.com/alneenqid6w5/5gCILEKQ80u0qWwo0SES6e/0d94e9fb47cbf373ec64f4209e202518/mike-petrucci-131817.jpg)
+![mike-petrucci-131817](https://images.contentful.com/alneenqid6w5/5gCILEKQ80u0qWwo0SES6e/0d94e9fb47cbf373ec64f4209e202518/mike-petrucci-131817.jpg)
 
 ### 1. A Black Friday já começou
 
@@ -93,7 +93,7 @@ Entre outros motivos, isso é importante porque – devido ao tempo de atualiza
 
 De fato, a principal queixa dos consumidores durante a Black Friday é a mudança de preço ao finalizar a compra, o que mostra que muitas lojas ainda enfrentam esse problema.
 
-![BF1](//images.contentful.com/alneenqid6w5/47Do1iY4gwqsgIIeeYeuKE/75120669c5cc26106ccdba6b9db4013e/BF1.png)
+![BF1](https://images.contentful.com/alneenqid6w5/47Do1iY4gwqsgIIeeYeuKE/75120669c5cc26106ccdba6b9db4013e/BF1.png)
 
 Para evitar mal-entendidos com seus clientes, recomendamos que você insira um aviso no rodapé da loja de que o preço válido será aquele apresentado na finalização da compra.
 
@@ -148,7 +148,7 @@ Tamanha volatilidade significa também uma enorme oportunidade para lojistas pre
 
 Garanta que seus clientes serão avisados por e-mail sobre pedidos incompletos.
 
-![BF3](//images.contentful.com/alneenqid6w5/nFjCLZiRkOMsA8gAIkEw0/481b1b669973eb4f6285f8c562f31a5e/BF3.png)
+![BF3](https://images.contentful.com/alneenqid6w5/nFjCLZiRkOMsA8gAIkEw0/481b1b669973eb4f6285f8c562f31a5e/BF3.png)
 
 
 ### 12. Use ferramentas de medição
@@ -214,7 +214,7 @@ Uma dica é instalar um add-on como o Ghostery em seu navegador. Ele identifica
 
 Na Black Friday do ano passado, 19,8% das compras online foram feitas em dispositivos móveis. E, para 2017, não há por que duvidar que esse número continuará crescendo consideravelmente.
 
-![BF4 (1)](//images.contentful.com/alneenqid6w5/5pQ24DnsycCeOYw4uasu28/dca829ad79b54f6ea8fe71c052526550/BF4__1_.png)
+![BF4 (1)](https://images.contentful.com/alneenqid6w5/5pQ24DnsycCeOYw4uasu28/dca829ad79b54f6ea8fe71c052526550/BF4__1_.png)
 
 Portanto, ser mobile-first não é mais apenas uma boa ideia – é uma necessidade para qualquer profissional que leve e-commerce a sério.
 
diff --git a/docs/tutorials/pt/black-week.md b/docs/tutorials/pt/black-week.md
index 1c09f26e1..f8b6626f0 100644
--- a/docs/tutorials/pt/black-week.md
+++ b/docs/tutorials/pt/black-week.md
@@ -29,7 +29,7 @@ Caso você utilize o novo Admin VTEX, para acessá-la, vá para **Dashboards > B
 
 Para ter acesso à pagina, é necessário conter o [recurso](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) *Insights Metrics* com a chave `view_metrics` em seu [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Sem esse recurso configurado em seu perfil de acesso, você receberá um erro *403 - Não autorizado* ao tentar visualizar a página. 
 
-![Black Week](//images.ctfassets.net/alneenqid6w5/3IM9M6IwfycwTmUzJDEzem/2ce38a00422d16e12016eb0ba58edd9b/Screen_Shot_2022-11-18_at_16.11.09.png)
+![Black Week](https://images.ctfassets.net/alneenqid6w5/3IM9M6IwfycwTmUzJDEzem/2ce38a00422d16e12016eb0ba58edd9b/Screen_Shot_2022-11-18_at_16.11.09.png)
 
 Este artigo inclui as seguintes seções:
 
@@ -93,7 +93,7 @@ A Black Week inclui os seguintes gráficos para a análise dos resultados do seu
 
 ### Total de pedidos
 
-![Total de pedidos](//images.ctfassets.net/alneenqid6w5/7mYLy1HXJVjiBm923PRQmm/d6eaef3b046627bca6fa55147221b1d2/Screen_Shot_2022-11-18_at_16.00.21.png)
+![Total de pedidos](https://images.ctfassets.net/alneenqid6w5/7mYLy1HXJVjiBm923PRQmm/d6eaef3b046627bca6fa55147221b1d2/Screen_Shot_2022-11-18_at_16.00.21.png)
 
 O gráfico _Total de Pedidos_ apresenta a quantidade de pedidos captados pela loja, agregado por dia e comparado com os anos anteriores selecionados. Saiba mais em [Dados](#dados).
 
@@ -123,7 +123,7 @@ Para ler os gráficos, note que:
 
 #### Total do dia 
 
-![Total do dia](//images.ctfassets.net/alneenqid6w5/3PMiZmAt84euZIrmu7gy35/77de595d36fab0672ba75d626acae658/Screen_Shot_2022-11-18_at_16.00.40.png)
+![Total do dia](https://images.ctfassets.net/alneenqid6w5/3PMiZmAt84euZIrmu7gy35/77de595d36fab0672ba75d626acae658/Screen_Shot_2022-11-18_at_16.00.40.png)
 
 A visualização _Total do Dia_ indica na tela:
 
@@ -134,7 +134,7 @@ Essa visualização é útil para acompanhar o somatório de vendas no dia, send
 
 #### Últimas 2 horas
 
-![Últimas 2 horas](//images.ctfassets.net/alneenqid6w5/7tBr0SR2wP9lD9SvJF6jpj/5be2166e0dd369b2a3b980ccfb90cf47/Screen_Shot_2022-11-18_at_16.00.54.png)
+![Últimas 2 horas](https://images.ctfassets.net/alneenqid6w5/7tBr0SR2wP9lD9SvJF6jpj/5be2166e0dd369b2a3b980ccfb90cf47/Screen_Shot_2022-11-18_at_16.00.54.png)
 
 A visualização _Últimas 2 horas_ indica na tela:
 
diff --git a/docs/tutorials/pt/brands.md b/docs/tutorials/pt/brands.md
index 88366f218..bafb98f20 100644
--- a/docs/tutorials/pt/brands.md
+++ b/docs/tutorials/pt/brands.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 A página **Marcas** permite visualizar, gerenciar e cadastrar marcas no Seller Portal. Você pode acessar a página no Admin VTEX em **Catálogo** > **Marcas**.
 
-![brands-pt](//images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/4556bc8cc6f367453b4bf4ccbe2bf145/brands-pt.PNG)
+![brands-pt](https://images.ctfassets.net/alneenqid6w5/5fhVobFAoo4vZiNqjEIh8u/4556bc8cc6f367453b4bf4ccbe2bf145/brands-pt.PNG)
 
 ## Criar marca 
 Para cadastrar uma nova marca, clique no botão `Criar marca`. Veja abaixo como preencher os campos da tela __Nova marca__.
diff --git a/docs/tutorials/pt/breadcrumb-control.md b/docs/tutorials/pt/breadcrumb-control.md
index db7cfe270..e21741efd 100644
--- a/docs/tutorials/pt/breadcrumb-control.md
+++ b/docs/tutorials/pt/breadcrumb-control.md
@@ -19,7 +19,7 @@ Breadbrumbs melhoram a experiência de navegação na loja por incentivarem os u
 
 Na VTEX, o controle `<vtex.cmc:breadCrumb/>` é responsável por renderizar breadcrumbs como o do exemplo abaixo.
 
-![breadcrumb1](//images.contentful.com/alneenqid6w5/4UnYdunXh6MI28k8sS0w8Y/9883ba3a0d5f9f5826313832f9c5a2d0/breadcrumb1.png)
+![breadcrumb1](https://images.contentful.com/alneenqid6w5/4UnYdunXh6MI28k8sS0w8Y/9883ba3a0d5f9f5826313832f9c5a2d0/breadcrumb1.png)
 
 Se, como neste exemplo, o usuário acessar diretamente a página de um produto da categoria *Camisetas*, o breadcrumb exibido na página do produto lhe dará a informação de que o usuário se encontra nessa categoria (*Camisetas*), que por sua vez está abaixo do departamento *Moda masculina*.
 
@@ -45,4 +45,4 @@ Veja abaixo um exemplo de código HTML renderizado pelo controle de breadcrumb:
 
 O código acima renderiza o seguinte breadcrumb no site:
 
-![breadcrumb2](//images.contentful.com/alneenqid6w5/1PxrLYlhNaaUYYoi6oOCe6/06d276039e7e73a39fa15061befffd38/breadcrumb2.png)
+![breadcrumb2](https://images.contentful.com/alneenqid6w5/1PxrLYlhNaaUYYoi6oOCe6/06d276039e7e73a39fa15061befffd38/breadcrumb2.png)
diff --git a/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md b/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md
index b7e1cef38..c79582a4f 100644
--- a/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md
+++ b/docs/tutorials/pt/bringing-app-content-into-the-admin-panel.md
@@ -25,13 +25,13 @@ Navegue até o projeto e abra o arquivo `pages.json`.
 
 Adicionamos o `“admin/“` ao nome da página, assim como à rota. É importante também adicionar `“admin/“` ao início do nome de todas as extensoes que serão usadas. Seu `pages.json` deve ficar assim:
 
-![2 pages](//images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
+![2 pages](https://images.ctfassets.net/alneenqid6w5/1JbyPjpfd2m2Qg6YuIG0WG/c2e98ed69b39f41703c49cda8ee6f578/2_pages.png)
 
 ## Atualizar as dependências para usar o vtex.admin
 
 Agora precisamos atualizar o arquivo manifest.json para listar o `vtex.admin` como dependência. Lembre-se que no VTEX IO sempre especificamos a versão que será ultilizada. O manifest.json deve ficar assim:
 
-![3 manifest](//images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
+![3 manifest](https://images.ctfassets.net/alneenqid6w5/m02IxioqqcMgEygiOkakI/1bf3d7cf52f72a46a5d3f2a9afaeb40a/3_manifest.png)
 
 ## Os toques finais
 
@@ -43,5 +43,5 @@ Usaremos o `componentDidMount()` para verificar que a string renderizou corretam
 
 Basta navegar até `index.js` e adicionar o `componentDidMount()` acima do nosso render. Vai ficar assim:
 
-![4 final touches](//images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
-![5 completo](//images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
+![4 final touches](https://images.ctfassets.net/alneenqid6w5/3FhYXrK6qAeW6U8AK8S2uI/adca7a874c3a7fd5f1d0558c1664a54b/4_final_touches.png) 
+![5 completo](https://images.ctfassets.net/alneenqid6w5/2u3bfIpopSSeqiq6o0KW2q/1173fb70b77505ec92ab126efd908d63/5_completo.png)
diff --git a/docs/tutorials/pt/buy-one-get-one.md b/docs/tutorials/pt/buy-one-get-one.md
index fb3ba1213..adbd6068d 100644
--- a/docs/tutorials/pt/buy-one-get-one.md
+++ b/docs/tutorials/pt/buy-one-get-one.md
@@ -53,7 +53,7 @@ Nesta seção, fornecemos informações detalhadas sobre os dados gerais desta p
 - **Informações adicionais (opcional):** permite incluir informações adicionais a promoção composto de um nome e valor.
 - **Destaque nos produtos:** insere uma tag com o nome da promoção. Utilizada na vitrine e na página do produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template. <vtex.cmc:discountHightLight>.
 
-![Dados gerais da promoção](//images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/131b38791a109e9629dcbfd9b203e80f/Dados_gerais_da_promo__o-PT.png)
+![Dados gerais da promoção](https://images.ctfassets.net/alneenqid6w5/4s7Zxlvv0aIThx2WW2JMO3/131b38791a109e9629dcbfd9b203e80f/Dados_gerais_da_promo__o-PT.png)
 
 ## Restringir esta promoção a produtos dos sellers
 
@@ -68,7 +68,7 @@ Para que a promoção seja válida para todos os sellers, deixe a seleção vazi
   <p>Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
 </div>
 
-![Restringir esta promoção a produtos dos sellers](//images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/cf6fdde6e939077f04001cb3e76f02b5/Restringir_esta_promo__o_a_produtos_dos_sellers.png)
+![Restringir esta promoção a produtos dos sellers](https://images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/cf6fdde6e939077f04001cb3e76f02b5/Restringir_esta_promo__o_a_produtos_dos_sellers.png)
 
 ## Política comercial
 
@@ -81,7 +81,7 @@ Esta seção estabelece as políticas comerciais válidas para a promoção. Voc
 
 Para que a promoção seja válida para todas as políticas comerciais, deixe a seleção vazia.
 
-![Política comercial-PT](//images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/8810800a350cb0b9688d296e3f985fef/Politica_comerical-PT.png)
+![Política comercial-PT](https://images.ctfassets.net/alneenqid6w5/1EUrXEMs0tyZ6J1ulXco9i/8810800a350cb0b9688d296e3f985fef/Politica_comerical-PT.png)
 
 # 2. Compre e Ganhe
 
@@ -99,7 +99,7 @@ Esta seção define as coleções, SKUs e quantidade mínima que devem ser preen
 <p>Uma promoção Compre e Ganhe pode ser criada com o máximo de 100 SKUs diferentes ao mesmo tempo.</p>
 </div>
 
-![Compre e Ganhe](//images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/e818e8a1252f1b46032be2d043fa62cb/Compre_e_Ganhe.png)
+![Compre e Ganhe](https://images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/e818e8a1252f1b46032be2d043fa62cb/Compre_e_Ganhe.png)
 
 # 3. Quais condições para a promoção ser válida?
 
@@ -112,7 +112,7 @@ Nesta seção, detalharemos as condições em que você deve aplicar para que um
 - **Utm_source:** o desconto será concedido caso a navegação seja realizada com a utm_source com o valor cadastrado.
 - **Utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
 
-![Quais as condições para a promoção ser válida?](//images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/dfad1e2b79fbcc2381cb4474d2674ad6/Quais_as_condi__es_para_a_promo__o_ser_v_lida.png)
+![Quais as condições para a promoção ser válida?](https://images.ctfassets.net/alneenqid6w5/4zOT1bHe70Z1wbN2wQjCXD/dfad1e2b79fbcc2381cb4474d2674ad6/Quais_as_condi__es_para_a_promo__o_ser_v_lida.png)
 
 # 4. Restrições e Limitações de uso
 
@@ -123,4 +123,4 @@ Nesta seção você encontrará informações importantes sobre quais condiçõe
 - **Somente para itens iguais:** Se esta opção estiver habilitada, a promoção é aplicada somente se a quantidade mínima de itens (cadastrados anteriormente) for atingida utilizando o mesmo SKU no carrinho. Caso a opção esteja desabilitada, a promoção será aplicada mesmo quando a quantidade mínima de itens for adicionada no carrinho, independentemente dos SKUs serem diferentes ou iguais.
 - **Permitir acumular promoções:** permite que essa promoção possa ser aplicada no carrinho em conjunto com outras promoções que ofereçam o mesmo tipo de desconto.
 
-![Restrições e limitações de uso](//images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/5d83ca212086a91d2f672e520e69e7e8/Restri__es_e_limita__es_de_uso.png)
+![Restrições e limitações de uso](https://images.ctfassets.net/alneenqid6w5/71kLc3PWSLecGA49Iytuyd/5d83ca212086a91d2f672e520e69e7e8/Restri__es_e_limita__es_de_uso.png)
diff --git a/docs/tutorials/pt/call-to-action-suiteshare.md b/docs/tutorials/pt/call-to-action-suiteshare.md
index 5e74d613f..98ee5bff9 100644
--- a/docs/tutorials/pt/call-to-action-suiteshare.md
+++ b/docs/tutorials/pt/call-to-action-suiteshare.md
@@ -19,29 +19,29 @@ Não perca clientes que acessam o seu site, ou sua página de vendas e tenha ale
 
 Para configurar, acesse seu painel do VTEX Assisted Sales (SuiteShare) e clique em Atrair > Call to Action.
 
-![Call to Action 1](//images.ctfassets.net/alneenqid6w5/797KHplQqNwIEOwQLzPAO8/425cc4da8f450beb2543b27b65cfd817/Screenshot_2022-08-29_at_17-35-16_Call_to_Action.png)
+![Call to Action 1](https://images.ctfassets.net/alneenqid6w5/797KHplQqNwIEOwQLzPAO8/425cc4da8f450beb2543b27b65cfd817/Screenshot_2022-08-29_at_17-35-16_Call_to_Action.png)
 
 Clique em _**“Novo”**_.
 
-![Call to Action 2](//images.ctfassets.net/alneenqid6w5/2Ea8itxFI6MPKuI8jBcWLz/042d319264111791139e7c0f374643ca/Screenshot_2022-08-29_at_17-35-22_Call_to_Action.png)
+![Call to Action 2](https://images.ctfassets.net/alneenqid6w5/2Ea8itxFI6MPKuI8jBcWLz/042d319264111791139e7c0f374643ca/Screenshot_2022-08-29_at_17-35-22_Call_to_Action.png)
 
 Selecione o modelo.
 
-![Call to Action 3](//images.ctfassets.net/alneenqid6w5/48mDM3kOJj3WD78mbAG6Nh/8a9f405dbc19fc50d0e66bc8fd7b774a/Screenshot_2022-08-29_at_17-35-27_Call_to_Action.png)
+![Call to Action 3](https://images.ctfassets.net/alneenqid6w5/48mDM3kOJj3WD78mbAG6Nh/8a9f405dbc19fc50d0e66bc8fd7b774a/Screenshot_2022-08-29_at_17-35-27_Call_to_Action.png)
 
 Clique na opção de selecionar o modelo e escolha uma das opções.
 
-![Call to Action 4](//images.ctfassets.net/alneenqid6w5/4R7nYhIZUi1L0gD5oVOFEA/00d8afb7e4959e859085cc19b554925f/Screenshot_2022-08-29_at_17-35-31_Call_to_Action.png)
+![Call to Action 4](https://images.ctfassets.net/alneenqid6w5/4R7nYhIZUi1L0gD5oVOFEA/00d8afb7e4959e859085cc19b554925f/Screenshot_2022-08-29_at_17-35-31_Call_to_Action.png)
 
 Defina o _**“Layout”**_.
 
-![Call to Action 5](//images.ctfassets.net/alneenqid6w5/1LL2HrisybDEMXQbBaNHye/30bd353dda1aa5d18274262febc0334a/Screenshot_2022-08-29_at_17-35-37_Call_to_Action.png)
+![Call to Action 5](https://images.ctfassets.net/alneenqid6w5/1LL2HrisybDEMXQbBaNHye/30bd353dda1aa5d18274262febc0334a/Screenshot_2022-08-29_at_17-35-37_Call_to_Action.png)
 
 **Imagem**: Você pode editar a imagem inserindo uma imagem com URL válida. Defina o **Título** que irá chamar o cliente e a **Descrição do CTA.** 
 
 Defina as configurações do **Botão**. 
 
-![Call to Action 6](//images.ctfassets.net/alneenqid6w5/1s8LJePgvvseJLLi80C2lQ/47747ae384541680890ad9a451fb3bf0/Screenshot_2022-08-29_at_17-35-41_Call_to_Action.png)
+![Call to Action 6](https://images.ctfassets.net/alneenqid6w5/1s8LJePgvvseJLLi80C2lQ/47747ae384541680890ad9a451fb3bf0/Screenshot_2022-08-29_at_17-35-41_Call_to_Action.png)
 
 Qual será o **link** que ele será encaminhado quando o cliente clicar. 
 
@@ -49,29 +49,29 @@ O **Texto do botão** que irá atrair o seu cliente. 
 
 Defina **configurações**, como por exemplo: Se o botão será centralizado ou não e também o tipo de animação.
 
-![Call to Action  7](//images.ctfassets.net/alneenqid6w5/72uHGFMsaFZp8uqD4TzgFR/25681bd034fed264b34ddf688d1ba066/Screenshot_2022-08-29_at_17-35-46_Call_to_Action.png)
+![Call to Action  7](https://images.ctfassets.net/alneenqid6w5/72uHGFMsaFZp8uqD4TzgFR/25681bd034fed264b34ddf688d1ba066/Screenshot_2022-08-29_at_17-35-46_Call_to_Action.png)
 
 Defina se irá habilitar o **Overlay** , ou seja , se vai sobressair a tela (deixando o restante da tela escura). 
 
-![Call to Action 8](//images.ctfassets.net/alneenqid6w5/63cr6nJEmIWGbD52fAAiu/d285fd2fec06e4617da564d71eeb8afc/Screenshot_2022-08-29_at_17-35-49_Call_to_Action.png)
+![Call to Action 8](https://images.ctfassets.net/alneenqid6w5/63cr6nJEmIWGbD52fAAiu/d285fd2fec06e4617da564d71eeb8afc/Screenshot_2022-08-29_at_17-35-49_Call_to_Action.png)
 
 Faça a configuração para **mobile**.
 
-![Call to Action 9](//images.ctfassets.net/alneenqid6w5/2Eu4ZBzfPlJc4ixGq9rMiv/4115aa9f05f8139a8660015807fe6600/Screenshot_2022-08-29_at_17-35-53_Call_to_Action.png)
+![Call to Action 9](https://images.ctfassets.net/alneenqid6w5/2Eu4ZBzfPlJc4ixGq9rMiv/4115aa9f05f8139a8660015807fe6600/Screenshot_2022-08-29_at_17-35-53_Call_to_Action.png)
 
 Defina os **gatilhos** de exibição do seu CTA.
 
-![Call to Action 10](//images.ctfassets.net/alneenqid6w5/2syIIyZv2sUW261YP5i2Sr/3469c820d1784ab881e6934fe48536eb/Screenshot_2022-08-29_at_17-35-59_Call_to_Action.png)
+![Call to Action 10](https://images.ctfassets.net/alneenqid6w5/2syIIyZv2sUW261YP5i2Sr/3469c820d1784ab881e6934fe48536eb/Screenshot_2022-08-29_at_17-35-59_Call_to_Action.png)
 
 Defina em quais locais do seu site irá aparecer a mensagem ou onde não irá aparecer: 
 
-![Call to Action 11](//images.ctfassets.net/alneenqid6w5/6L5KjcTvz4DyPOKyuMI0i4/4e7b4f92f6394c984dd3fd9f7680ba22/Screenshot_2022-08-29_at_17-36-04_Call_to_Action.png)
+![Call to Action 11](https://images.ctfassets.net/alneenqid6w5/6L5KjcTvz4DyPOKyuMI0i4/4e7b4f92f6394c984dd3fd9f7680ba22/Screenshot_2022-08-29_at_17-36-04_Call_to_Action.png)
 
 Antes de clicar em “_**Salvar**_” clique em “_**preview**_” para confirmar todas as alterações.
 
-![Call to Action 12](//images.ctfassets.net/alneenqid6w5/5sCyq6lSK5nTONwckiQfV4/1fe29ac73a3edb8276dabd0a5756350f/Screenshot_2022-08-29_at_17-36-10_Call_to_Action.png)
+![Call to Action 12](https://images.ctfassets.net/alneenqid6w5/5sCyq6lSK5nTONwckiQfV4/1fe29ac73a3edb8276dabd0a5756350f/Screenshot_2022-08-29_at_17-36-10_Call_to_Action.png)
 
-![Call to Action 13](//images.ctfassets.net/alneenqid6w5/2lWYEhJyn43e4UElheF0Ga/909281d3af2ac2ad9f0449dc2a93149a/Screenshot_2022-08-29_at_17-36-18_Call_to_Action.png)
+![Call to Action 13](https://images.ctfassets.net/alneenqid6w5/2lWYEhJyn43e4UElheF0Ga/909281d3af2ac2ad9f0449dc2a93149a/Screenshot_2022-08-29_at_17-36-18_Call_to_Action.png)
 
 Se não houver nenhuma alteração, clique em _**“Salvar”**_. 
 
diff --git a/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md b/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
index d97b040d6..7003b5f7f 100644
--- a/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
+++ b/docs/tutorials/pt/cambiar-el-limite-de-articulos-del-mismo-sku-en-el-carrito.md
@@ -25,4 +25,4 @@ Para isso, siga os passos abaixo:
 
 Para casos de Sellers White Label  há um limite de 50 unidades com o mesmo SKU no carrinho. É possível alterar esse limite mediante uma solicitação no [suporte](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9).
 
-![Carrinho Max PT](//images.ctfassets.net/alneenqid6w5/3SIx4hvYxGuUkcUs44Us0s/340ea46f5c1bdfd593dc0c87d3b5536a/Carrinho_Max_PT.png)
+![Carrinho Max PT](https://images.ctfassets.net/alneenqid6w5/3SIx4hvYxGuUkcUs44Us0s/340ea46f5c1bdfd593dc0c87d3b5536a/Carrinho_Max_PT.png)
diff --git a/docs/tutorials/pt/campaign-audiences-list.md b/docs/tutorials/pt/campaign-audiences-list.md
index 52d7db0e0..4cb14ba63 100644
--- a/docs/tutorials/pt/campaign-audiences-list.md
+++ b/docs/tutorials/pt/campaign-audiences-list.md
@@ -17,7 +17,7 @@ subcategory: 2cI57eZ3ZiWSeaQs26Gwys
 
 A lista de audiências de campanhas cadastradas na sua loja está disponível no Admin VTEX, na página *Promoções > Audiências de campanhas*, ilustrada a seguir.
 
-![lista-audiencias-campanha-pt](//images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/5c50543b3dc5698d0362a696b91302d2/lista-audiencias-campanha-pt.png)
+![lista-audiencias-campanha-pt](https://images.ctfassets.net/alneenqid6w5/3OyfWyVN0MMA5qpgjxtGyM/5c50543b3dc5698d0362a696b91302d2/lista-audiencias-campanha-pt.png)
 
 A partir desta página, você pode realizar as seguintes ações:
 
@@ -50,7 +50,7 @@ As audiências de campanhas são apresentadas em _cards_ com as seguintes inform
 
 Para visualizar as Audiências de campanhas que estão [arquivadas](#arquivar-audiencia-de-campanha), na opção **Exibir**, clique em **Arquivados**, conforme ilustrado a seguir:
 
-![toggle-audiencias-campanha-arquivadas-pt](//images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/87dca32f5de3ef43c405cad2bda5894b/toggle-audiencias-campanha-arquivadas-pt.png)
+![toggle-audiencias-campanha-arquivadas-pt](https://images.ctfassets.net/alneenqid6w5/7CMyMTQVHoWU7h8NMGlmwA/87dca32f5de3ef43c405cad2bda5894b/toggle-audiencias-campanha-arquivadas-pt.png)
 
 Para voltar a visualizar as Audiências de campanhas não arquivadas, clique em **Não Arquivados**.
 
diff --git a/docs/tutorials/pt/campaign-audiences.md b/docs/tutorials/pt/campaign-audiences.md
index c14510fb5..4623a2371 100644
--- a/docs/tutorials/pt/campaign-audiences.md
+++ b/docs/tutorials/pt/campaign-audiences.md
@@ -27,7 +27,7 @@ Exemplo: no segmento de moda, ao cadastrar uma audiência de campanha, é possí
 
 O público-alvo segmenta os usuários e condições elegíveis da audiência de campanha. Caso a audiência de campanha esteja ativa, ao atender todos os critérios definidos no público-alvo, as promoções associadas à audiência de campanha serão ativadas.
 
-![campanha-pt](//images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/d8bfd2a4e7f082f2cd1b865bda2f85b0/campanha-pt.png)
+![campanha-pt](https://images.ctfassets.net/alneenqid6w5/6Cxe95BqKrrMxwMiEVSvTJ/d8bfd2a4e7f082f2cd1b865bda2f85b0/campanha-pt.png)
 
 Quando todas as restrições da campanha forem atingidas e ela estiver ativada e elegível ao contexto de compra, não significa necessariamente que as promoções de audiências de campanhas associadas a ela serão aplicadas. Para isso, as restrições definidas na [promoção de campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) também devem ser atendidas.
 
diff --git a/docs/tutorials/pt/campaign-promotion.md b/docs/tutorials/pt/campaign-promotion.md
index 2e6521433..9d0aeddcd 100644
--- a/docs/tutorials/pt/campaign-promotion.md
+++ b/docs/tutorials/pt/campaign-promotion.md
@@ -122,7 +122,7 @@ Para que a promoção seja válida para todas as políticas comerciais, deixe a
 
 Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
 
-![promocoes-restricao-pt](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
+![promocoes-restricao-pt](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
 
 Caso deseje aplicar a promoção a todo o seu catálogo, selecione a opção **Aplicar a todos os produtos**.
 
@@ -132,7 +132,7 @@ Você pode incluir ou excluir **Categorias**, **Marcas**, **Coleções**, **Prod
 
 Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção todos os produtos da categoria **Home Appliances** cuja marca é **Brastemp**, com exceção do produto **Refrigerator 100**.
 
-![exemplo-pt](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/df98627884fc75e822e742473131299d/image.png)
+![exemplo-pt](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/df98627884fc75e822e742473131299d/image.png)
 
 Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
 
diff --git a/docs/tutorials/pt/capture-form-suiteshare.md b/docs/tutorials/pt/capture-form-suiteshare.md
index 2a4cbb3ab..123711c04 100644
--- a/docs/tutorials/pt/capture-form-suiteshare.md
+++ b/docs/tutorials/pt/capture-form-suiteshare.md
@@ -23,54 +23,54 @@ Para criar um formulário de Captura é preciso ter o link criado, se você não
 
 Acesse o painel do **VTEX Assisted Sales (SuiteShare)** e clique em _**“Capturar”**_.
 
-![Formulário de Captura 1](//images.ctfassets.net/alneenqid6w5/a7m5uiN0a4g2Sp0o8oU5H/c7f814fde6c2497d9521b99c9e7cf10c/Screenshot_2022-08-31_at_12-47-31_Formul__rio_de_Captura.png)
+![Formulário de Captura 1](https://images.ctfassets.net/alneenqid6w5/a7m5uiN0a4g2Sp0o8oU5H/c7f814fde6c2497d9521b99c9e7cf10c/Screenshot_2022-08-31_at_12-47-31_Formul__rio_de_Captura.png)
 
 Clique no botão _**“Novo”**_.
 
-![Formulário de Captura 2](//images.ctfassets.net/alneenqid6w5/51nLM13T99dZrNJUZ0kiU7/7959f68fe647d4d88ae2823bcf3aab1e/Screenshot_2022-08-31_at_12-47-36_Formul__rio_de_Captura.png)
+![Formulário de Captura 2](https://images.ctfassets.net/alneenqid6w5/51nLM13T99dZrNJUZ0kiU7/7959f68fe647d4d88ae2823bcf3aab1e/Screenshot_2022-08-31_at_12-47-36_Formul__rio_de_Captura.png)
 
 Na opção **Anchor link**, escolha qual é o link que os usuários deverão clicar para aparecer o formulário que eles devem preencher.
 
 **Atenção**:  Esse é o link que você irá compartilhar nas redes sociais e afins.
 
-![Formulário de Captura 3](//images.ctfassets.net/alneenqid6w5/4om3BBLLz3GZTINDZvFGlK/097fc32cae90ac75da30317b24577ebc/Screenshot_2022-08-31_at_12-47-41_Formul__rio_de_Captura.png)
+![Formulário de Captura 3](https://images.ctfassets.net/alneenqid6w5/4om3BBLLz3GZTINDZvFGlK/097fc32cae90ac75da30317b24577ebc/Screenshot_2022-08-31_at_12-47-41_Formul__rio_de_Captura.png)
 
 Após selecionar o link, clique em _**"avançar"**_.
 
-![Formulário de Captura 4](//images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
+![Formulário de Captura 4](https://images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
 
 Selecione o link de destino que os usuários serão direcionados após preencher o formulário. 
 
  **NOTA:** Você pode selecionar um link seletivo, sequencial ou geolocalizado, caso queira direcionar para mais de um atendente/número.
 
-![Formulário de Captura 5](//images.ctfassets.net/alneenqid6w5/6brAJH7YJQpkR3QRUgYA3j/91b30663f009576bf5cd7ddead169f6a/Screenshot_2022-08-31_at_12-47-51_Formul__rio_de_Captura.png)
+![Formulário de Captura 5](https://images.ctfassets.net/alneenqid6w5/6brAJH7YJQpkR3QRUgYA3j/91b30663f009576bf5cd7ddead169f6a/Screenshot_2022-08-31_at_12-47-51_Formul__rio_de_Captura.png)
 
 Se você não sabe como criar esse link de central seletiva, sequencial ou geolocalizado,acesse nossos artigos. 
 
 Clique no botão _**\\"avançar\\".**_
 
-![Formulário de Captura 4](//images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
+![Formulário de Captura 4](https://images.ctfassets.net/alneenqid6w5/1OWFaIf85deXBE6CfqJa3u/b9722aa3b3ab480c8a48163af7d278d2/Screenshot_2022-08-31_at_12-47-46_Formul__rio_de_Captura.png)
 
 Selecione quais campos você quer capturar. Nesse caso selecionamos todos os campos: Nome, Telefone e Email.
 
-![Formulário de Captura 6](//images.ctfassets.net/alneenqid6w5/2BLC4i3qKEsilm7c25H9oe/9088afbd85e94020dcf5050b7fe8a689/Screenshot_2022-08-31_at_12-48-00_Formul__rio_de_Captura.png)
+![Formulário de Captura 6](https://images.ctfassets.net/alneenqid6w5/2BLC4i3qKEsilm7c25H9oe/9088afbd85e94020dcf5050b7fe8a689/Screenshot_2022-08-31_at_12-48-00_Formul__rio_de_Captura.png)
 
 Na opção **Modo Robô**, você pode tornar o formulário muito mais intuitivo para os clientes preencherem. Ao ativar essa função, você substitui os campos tradicionais do formulário por um robô que fará as mesmas perguntas. 
 
-![Formulário de Captura 7](//images.ctfassets.net/alneenqid6w5/5NHkNYGVXMDMucRWB9aO4Y/c466e84c48104b7adfd0701e9e58c8f3/Screenshot_2022-08-31_at_12-48-22_Formul__rio_de_Captura.png)
+![Formulário de Captura 7](https://images.ctfassets.net/alneenqid6w5/5NHkNYGVXMDMucRWB9aO4Y/c466e84c48104b7adfd0701e9e58c8f3/Screenshot_2022-08-31_at_12-48-22_Formul__rio_de_Captura.png)
 
 Clique em _**“avançar”**_.
 
 **Atenção!** Se sua captura for a tela inicial do seu chat, escolha o texto da tela do chat.
 
-![Formulário de Captura 8](//images.ctfassets.net/alneenqid6w5/2ocbRZxxG9j4FGp53ekhO3/5b9c2951dd4b1eb4535677de1c2c2ef5/Screenshot_2022-08-31_at_12-48-29_Formul__rio_de_Captura.png)
+![Formulário de Captura 8](https://images.ctfassets.net/alneenqid6w5/2ocbRZxxG9j4FGp53ekhO3/5b9c2951dd4b1eb4535677de1c2c2ef5/Screenshot_2022-08-31_at_12-48-29_Formul__rio_de_Captura.png)
 
 Clique em _**“Finalizar”**_.
 
-![Formulário de Captura 9](//images.ctfassets.net/alneenqid6w5/VA68YLtSMCEcdytQjELR1/fc449d58ad97c893b882fbd57c76967f/Screenshot_2022-08-31_at_12-48-37_Formul__rio_de_Captura.png)
+![Formulário de Captura 9](https://images.ctfassets.net/alneenqid6w5/VA68YLtSMCEcdytQjELR1/fc449d58ad97c893b882fbd57c76967f/Screenshot_2022-08-31_at_12-48-37_Formul__rio_de_Captura.png)
 
 Configure a [aparência](\https://help.vtex.com/pt/tutorial/personalizar--sG7FAksOsU1EW9vcbPgIe), você pode clicar no botão _**“Clique aqui”**_ ou acessar  **Configurações > Minha conta > Aparência**.
 
-![Formulário de Captura 10](//images.ctfassets.net/alneenqid6w5/7KFaI3M4SiGc8MaOSGjdFM/92ad3df486fa395348cff8dc6056208a/Screenshot_2022-08-31_at_12-48-42_Formul__rio_de_Captura.png)
+![Formulário de Captura 10](https://images.ctfassets.net/alneenqid6w5/7KFaI3M4SiGc8MaOSGjdFM/92ad3df486fa395348cff8dc6056208a/Screenshot_2022-08-31_at_12-48-42_Formul__rio_de_Captura.png)
 
 Pronto! Seu formulário de captura foi criado com sucesso e todos os dados preenchidos pelos clientes serão salvos e exibidos no botão Leads. 
diff --git a/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
index 4fe6823a1..03c859255 100644
--- a/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -24,7 +24,7 @@ O módulo *Estoque & Entrega* é onde você faz todo o gerenciamento da logísti
 Algumas seções da página de cadastro de **Política de Envio** mudaram, para te dar mais flexibilidade ao configurar sua estratégia de entrega. Na versão anterior, havia uma seção chamada *Configuração de Tempo*, na qual era possível selecionar *Horário de Funcionamento*, *Horário de Corte* ou *Entrega Agendada* para cada transportadora. 
 
 **Versão anterior**
-![PT Configurações de tempo versão antiga](//images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/853e5c8125a87076697643bbb62848a0/PT_Configura____es_de_tempo_vers__o_antiga.jpg)
+![PT Configurações de tempo versão antiga](https://images.ctfassets.net/alneenqid6w5/2n9RGrhtYEYrGsnsBN3Qlj/853e5c8125a87076697643bbb62848a0/PT_Configura____es_de_tempo_vers__o_antiga.jpg)
 
 Na nova versão:
 - Mudamos os nomes das opções para facilitar seu entendimento.   
@@ -32,7 +32,7 @@ Na nova versão:
 - Adicionamos a opção de configurar capacidade de entrega, para que a entrega agendada seja feita com base na realidade da sua operação.   
 
 **Versão Beta**
-![PT Horário de funcionamento transportadora beta](//images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
+![PT Horário de funcionamento transportadora beta](https://images.ctfassets.net/alneenqid6w5/7p1pOc8ng4KJCVIUUOZMtJ/e5ae82ee60854de23f4b3142720c3aa7/PT_Hor__rio_de_funcionamento_transportadora_beta.jpg)
 
 ## Horário de coleta
 
@@ -49,7 +49,7 @@ Assim como na versão anterior, não é possível configurar as opções de *Per
 Antes só era possível optar pela funcionalidade de *Entrega Agendada* abrindo mão do *Horário de Funcionamento*. Agora é possível configurar a opção de *Entrega Agendada* juntamente com o *Horário de Funcionamento* para que seu cliente opte por esse método de entrega durante o checkout de seu pedido. Confira os campos de preenchimento para configurar essa opção.
 
 **Versão Beta**
-![PT entrega agendada](//images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/2de3b092c9265fce7aa6d5478f2de5dd/PT_entrega_agendada.jpg)
+![PT entrega agendada](https://images.ctfassets.net/alneenqid6w5/5NEf2aJHHPmQTIFgvDt19H/2de3b092c9265fce7aa6d5478f2de5dd/PT_entrega_agendada.jpg)
 
 - **Tempo máximo de entrega**: esse campo deve ser preenchido de acordo com a sua operação logística. Defina qual é o maior período de tempo que aquela transportadora gasta para realizar uma entrega agendada, entre a confirmação do pedido e a confirmação da entrega.
 - **Configurar capacidade de entrega**: dependendo das características da sua operação, e de como a transportadora envia os seus produtos, pode fazer mais sentido definir uma capacidade de entrega em número de itens, ou em número de pedidos. Se sua loja for do segmento de supermercado, por exemplo, e o meio de transporte para a entrega agendada for por moto, existe um número limite de itens que cabem na armazenagem daquele veículo, portanto sugerimos que selecione `itens` como unidade. Já se sua operação tiver poucos itens por pedido, fará mais sentido determinar `pedidos` como unidade, por exemplo.
diff --git a/docs/tutorials/pt/catalog-overview.md b/docs/tutorials/pt/catalog-overview.md
index 9f86babf7..b0fce7bd7 100644
--- a/docs/tutorials/pt/catalog-overview.md
+++ b/docs/tutorials/pt/catalog-overview.md
@@ -15,7 +15,7 @@ legacySlug: catalogo-visao-geral
 subcategory: 
 ---
 
-![Overview do catálogo (capa)](//images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/381c53d2f596018d117c044d38d70ab4/image1.jpg)
+![Overview do catálogo (capa)](https://images.ctfassets.net/alneenqid6w5/1OkPBtIH7KNPWFpCYVv89Y/381c53d2f596018d117c044d38d70ab4/image1.jpg)
 Catálogo é o módulo de administração da sua loja que possibilita configurar as funcionalidades referentes aos produtos do seu ecommerce. Para que o seu cliente veja os produtos no site, você precisa cadastrá-los neste módulo. 
 
 Neste artigo você encontrará uma visão geral dos itens do catálogo e suas funcionalidades.
@@ -25,7 +25,7 @@ A Categoria é o segundo nível de categorização da sua loja, logo abaixo do n
 
 O módulo **Categorias** permite visualizar e gerenciar a árvore de categorias cadastradas na sua loja, como mostrado no exemplo abaixo.
 
-![Estrutura do catálogo](//images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/66d1260822745c13cc2771f79289a131/image3.png)
+![Estrutura do catálogo](https://images.ctfassets.net/alneenqid6w5/6x2Nbxv5BvPZ9XW2Q4pTHa/66d1260822745c13cc2771f79289a131/image3.png)
 
 Você pode cadastrar uma categoria seguindo o tutorial [Cadastrar uma Categoria](https://help.vtex.com/pt/tutorial/cadastrando-categoria--tutorials_206). Se deseja gerenciar ou inativar uma categoria, siga os passos do tutorial [Inativar e reorganizar categorias](https://help.vtex.com/pt/tutorial/inativando-e-reorganizando-categorias--tutorials_264).
 
diff --git a/docs/tutorials/pt/categories.md b/docs/tutorials/pt/categories.md
index 959aca637..31fc74a4d 100644
--- a/docs/tutorials/pt/categories.md
+++ b/docs/tutorials/pt/categories.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 A página **Categorias** permite visualizar e gerenciar a árvore de categorias cadastradas no Seller Portal. Você pode acessar a página no Admin VTEX em **Catálogo** > **Categorias**.
 
-![categorias-pt](//images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/8bbda2aa615c249815bae0424ead68c7/categorias-pt.PNG)
+![categorias-pt](https://images.ctfassets.net/alneenqid6w5/1ViCOvDbtriF91lt0Z6ztZ/8bbda2aa615c249815bae0424ead68c7/categorias-pt.PNG)
 
 A partir da árvore de categorias, você pode realizar uma variedade de ações:
 
@@ -57,7 +57,7 @@ Para localizar uma categoria, você deve digitar o nome da categoria na barra de
 ## Navegar pela árvore de categorias
 A página de categorias apresenta os níveis mais externos das categorias. Clique no ícone <i class="fas fa-angle-right"></i> para acessar as subcategorias, como demonstrado abaixo.
 
-![arvore-categoria-PT](//images.contentful.com/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/a3cacb293c5c5ce3ded311ab85468a04/arvore-categoria-PT.gif)
+![arvore-categoria-PT](https://images.contentful.com/alneenqid6w5/4bcSzxVEs4GAn1INLdjP8E/a3cacb293c5c5ce3ded311ab85468a04/arvore-categoria-PT.gif)
 
 Para visualizar as informações do cadastro de uma categoria, clique no nome dela.
 
diff --git a/docs/tutorials/pt/category-registration-fields.md b/docs/tutorials/pt/category-registration-fields.md
index 5258df30f..8a3406496 100644
--- a/docs/tutorials/pt/category-registration-fields.md
+++ b/docs/tutorials/pt/category-registration-fields.md
@@ -43,8 +43,8 @@ Para entender melhor o significado de cada campo do cadastro de categoria, veja
 - __Score (usado para ordenação de busca):__ valor utilizado para definir a prioridade na página de resultado de busca. Para entender mais sobre Score, acesse o nosso artigo [Como funciona o campo score](https://help.vtex.com/pt/tutorial/como-funciona-o-campo-score--1BUZC0mBYEEIUgeQYAKcae).
 - __Modo de exibição dos produtos:__ define como os SKUs serão exibidos na página do produto. Veja abaixo as opções de preenchimento deste campo:
   - __Lista de SKUs:__ todos os SKUs do departamento ou categoria em questão serão exibidos no formato de lista. Cada um com seu botão Comprar do lado.
-  ![1Lista.pt](//images.ctfassets.net/alneenqid6w5/6mWjVoqS6SVTNngaDC2s0f/833590ef9a7ca23a80ca3064158eacf4/Lista.pt.png)
+  ![1Lista.pt](https://images.ctfassets.net/alneenqid6w5/6mWjVoqS6SVTNngaDC2s0f/833590ef9a7ca23a80ca3064158eacf4/Lista.pt.png)
   - __Ícones de seleção de radio (radioBox):__ todos os SKUs do departamento ou categoria em questão precisarão ser selecionados através de seleção de radio.
-  ![RadioBox.pt](//images.ctfassets.net/alneenqid6w5/6KPwMsYzYcdbLSaxuaXujO/da99f6ea4f3c41846d7370bd334e67d9/RadioBox.pt.png)
+  ![RadioBox.pt](https://images.ctfassets.net/alneenqid6w5/6KPwMsYzYcdbLSaxuaXujO/da99f6ea4f3c41846d7370bd334e67d9/RadioBox.pt.png)
   - __Segue definição da especificação do SKU:__ todos os SKUs do departamento ou categoria em questão serão selecionados de acordo com a aba Especificação, no formulário de SKU. As opções pré-configuradas são Combo ou Radio.
-  ![Campos.pt](//images.ctfassets.net/alneenqid6w5/U6fp5beQoHb9N8NFfbzJE/737de2d0a29e27ca99e8e3199e6cc4cd/Campos.pt.png)
+  ![Campos.pt](https://images.ctfassets.net/alneenqid6w5/U6fp5beQoHb9N8NFfbzJE/737de2d0a29e27ca99e8e3199e6cc4cd/Campos.pt.png)
diff --git a/docs/tutorials/pt/category-variations-and-attributes-mapping.md b/docs/tutorials/pt/category-variations-and-attributes-mapping.md
index cd7f66c5d..50fc63670 100644
--- a/docs/tutorials/pt/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/pt/category-variations-and-attributes-mapping.md
@@ -21,7 +21,7 @@ Com essa feature, será possível categorizar corretamente os seus produtos no M
 
 O mapeamento só será feito uma vez para cada categoria. Isso significa que, já tendo feito o mapeamento uma vez, os novos produtos que forem criados vão ser integrados diretamente na categoria correta (e com suas respectivas variações e atributos).
 
-- [Baixe aqui](//assets.ctfassets.net/alneenqid6w5/qyDp7OSL5YAGaGKagWiK0/07900f41a952a460185e18f9db190eb1/Planilha_de_Mapeamento_do_Mercado_Livre.xlsx) a __Planilha de Mapeamento do Mercado Livre__ no formato `.xlsx`.
+- [Baixe aqui](https://assets.ctfassets.net/alneenqid6w5/qyDp7OSL5YAGaGKagWiK0/07900f41a952a460185e18f9db190eb1/Planilha_de_Mapeamento_do_Mercado_Livre.xlsx) a __Planilha de Mapeamento do Mercado Livre__ no formato `.xlsx`.
 
 A mesma planilha será usada nas três macroetapas, descritas a seguir (categorização, variações e atributos). Siga o passo a passo, preenchendo os campos da planilha de mapeamento conforme as indicações abaixo.
 
@@ -30,7 +30,7 @@ A mesma planilha será usada nas três macroetapas, descritas a seguir (categori
 Aqui será feito o de/para das suas categorias na VTEX com as usadas pelo Mercado Livre. 
 
 1. __CategoryId:__ é o ID da categoria na VTEX. Você consegue encontrá-lo do lado do nome de cada categoria ao expandir a árvore.
-2. __MeliCategoryId:__ é o ID da categoria no Mercado Livre. [Clique aqui](//assets.ctfassets.net/alneenqid6w5/4IGh23L6buEm8s8IWYwISS/f8f1e862f39f8f0052b1b60a696aadd6/MercadoLivre_CategoriasFixas.xlsx) para fazer o download da planilha em que esses valores estão disponibilizados. Se preferir, acesse esta [API do Mercado Livre](https://api.mercadolibre.com/sites/MLB/categories) para consultar as categorias, que estão sempre atualizadas por lá.
+2. __MeliCategoryId:__ é o ID da categoria no Mercado Livre. [Clique aqui](https://assets.ctfassets.net/alneenqid6w5/4IGh23L6buEm8s8IWYwISS/f8f1e862f39f8f0052b1b60a696aadd6/MercadoLivre_CategoriasFixas.xlsx) para fazer o download da planilha em que esses valores estão disponibilizados. Se preferir, acesse esta [API do Mercado Livre](https://api.mercadolibre.com/sites/MLB/categories) para consultar as categorias, que estão sempre atualizadas por lá.
 
 >_`Ex:` você tem a seguinte árvore na __VTEX__:_
 
@@ -60,7 +60,7 @@ No Mercado Livre, existem dois tipos de variação: as __obrigatórias__ e as __
 
 - Variações obrigatórias
 
-Caso seu produto seja um `Calçado`, `Roupa`, `Bolsa`, `Cinto` ou `Eletrodoméstico`, __será necessário mapear as variações obrigatórias__. O nome delas deve seguir exatamente os valores aceitos pelo marketplace. [Baixe aqui](//assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/11965d535fbb660d698cd73cc2109df1/Planilha_de_Variac__o__es_do_Mercado_Livre.xlsx) a __Planilha de Variações do Mercado Livre__ para verificar os valores aceitos de acordo com cada tipo de produto.
+Caso seu produto seja um `Calçado`, `Roupa`, `Bolsa`, `Cinto` ou `Eletrodoméstico`, __será necessário mapear as variações obrigatórias__. O nome delas deve seguir exatamente os valores aceitos pelo marketplace. [Baixe aqui](https://assets.ctfassets.net/alneenqid6w5/5nLnBUVonS8qgWqqeck4MQ/11965d535fbb660d698cd73cc2109df1/Planilha_de_Variac__o__es_do_Mercado_Livre.xlsx) a __Planilha de Variações do Mercado Livre__ para verificar os valores aceitos de acordo com cada tipo de produto.
 
 - Variações customizáveis
 
diff --git a/docs/tutorials/pt/change-a-placeholder-title.md b/docs/tutorials/pt/change-a-placeholder-title.md
index 71976c8bc..dc428e4c9 100644
--- a/docs/tutorials/pt/change-a-placeholder-title.md
+++ b/docs/tutorials/pt/change-a-placeholder-title.md
@@ -17,20 +17,20 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 O título de um placeholder é o que aparece no canto direito do objeto, como indica a imagem abaixo.
 
-![cms-placeholder pt](//images.ctfassets.net/alneenqid6w5/2B81NqQBPqi6MgEAawOU4I/00578c25664eab1bded200712d574959/placeholder_destaque.png)
+![cms-placeholder pt](https://images.ctfassets.net/alneenqid6w5/2B81NqQBPqi6MgEAawOU4I/00578c25664eab1bded200712d574959/placeholder_destaque.png)
 
 O texto que for inserido nesse campo é o que será exibido como título do placeholder no site da loja.
 
 Seguindo o exemplo acima, teríamos o seguinte na loja:
 
-![exemplo-placeholder pt](//images.ctfassets.net/alneenqid6w5/3J1Xr0TrkQU8EoYsss26Ke/84287c72e31c8246e5c3f2d96a1ab740/loja_pedro_exemplo_placeholder.png)
+![exemplo-placeholder pt](https://images.ctfassets.net/alneenqid6w5/3J1Xr0TrkQU8EoYsss26Ke/84287c72e31c8246e5c3f2d96a1ab740/loja_pedro_exemplo_placeholder.png)
 
 Para alterar o título de um placeholder, basta seguir os passos abaixo:
 
 1. Clique no título.
 
 2. Insira o novo título.
-![placeholder-change-name pt](//images.ctfassets.net/alneenqid6w5/59J7ZEZe4w8uAS2kGa4qIW/9f8adbf11d44c3ffe54d9178fbb363dc/change_name_pt.png)
+![placeholder-change-name pt](https://images.ctfassets.net/alneenqid6w5/59J7ZEZe4w8uAS2kGa4qIW/9f8adbf11d44c3ffe54d9178fbb363dc/change_name_pt.png)
 
 3. Clique em __Rename__.
 
diff --git a/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md b/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
index 8e22e69d5..061290260 100644
--- a/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
+++ b/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
@@ -34,7 +34,7 @@ Existem duas possibilidades de troca de seller:
 
 | **Ativo** | **Desativo** |
 |----|
-| ![Recusar](//images.ctfassets.net/alneenqid6w5/3ko5d7jnhUZh4HDxx3hr6d/3acaa50706a0938f0cbd30446cfebff1/Recusar.png) | ![Cancelar](//images.ctfassets.net/alneenqid6w5/2ZS1DTLiKFlHJYBVyuYMhQ/4f13f9c482acaa7e7baddb7b4c0070eb/Cancelar.png) |
+| ![Recusar](https://images.ctfassets.net/alneenqid6w5/3ko5d7jnhUZh4HDxx3hr6d/3acaa50706a0938f0cbd30446cfebff1/Recusar.png) | ![Cancelar](https://images.ctfassets.net/alneenqid6w5/2ZS1DTLiKFlHJYBVyuYMhQ/4f13f9c482acaa7e7baddb7b4c0070eb/Cancelar.png) |
 
 ## Troca automática de seller
 
@@ -42,7 +42,7 @@ Após a recusa de um pedido no VTEX Sales App, o sistema irá procurar automatic
 
 Recomendamos que, caso um seller não seja encontrado automaticamente, seja realizada a [troca de seller manualmente](#troca-manual-de-seller). Para habilitar essa funcionalidade, entre em contato com o [Suporte da VTEX](https://support.vtex.com/hc/pt-br/requests). 
 
-![pedidos recusados PT](//images.ctfassets.net/alneenqid6w5/5goolXgsNzyW6iIomwQViD/8dc2cf8b5ed5e14ef4df62d71d290514/image.png)
+![pedidos recusados PT](https://images.ctfassets.net/alneenqid6w5/5goolXgsNzyW6iIomwQViD/8dc2cf8b5ed5e14ef4df62d71d290514/image.png)
 
 ## Troca manual de seller
 
@@ -52,10 +52,10 @@ Para trocar manualmente o seller de um pedido no VTEX Sales App, siga os passos
 2. Na seção **Pedidos recusados**, clique no pedido que deseja trocar o seller. Caso a sua loja não tenha nenhum pedido recusado, essa seção ficará oculta.
 3. Na página do pedido, clique em `Trocar seller`.
 4. Selecione o seller desejado para o pedido. Na janela será apresentado o prazo de entrega e preço do frete de cada seller, além de indicar qual seller apresenta menor prazo.
-![trocar seller PT](//images.ctfassets.net/alneenqid6w5/5qXGxdwH7F6uJfpL1jVSiT/d88d155df80d7664e3afe56c0fc9e709/image.png)
+![trocar seller PT](https://images.ctfassets.net/alneenqid6w5/5qXGxdwH7F6uJfpL1jVSiT/d88d155df80d7664e3afe56c0fc9e709/image.png)
 5. Após selecionar o seller, clique em `Continuar`.
 6. Confira as informações da troca de seller e clique em `Confirmar` para finalizar.
-![trocar seller 2 PT](//images.ctfassets.net/alneenqid6w5/7DLR4MFL58OoL4tmQNAgJf/6ff588942b260ec8585a7fc7350dcaa3/image.png)
+![trocar seller 2 PT](https://images.ctfassets.net/alneenqid6w5/7DLR4MFL58OoL4tmQNAgJf/6ff588942b260ec8585a7fc7350dcaa3/image.png)
 
 <div class ="alert alert-info">
 <p>O cliente só será notificado da troca de seller por email caso o prazo de entrega seja diferente do que o original.</p>
diff --git a/docs/tutorials/pt/change-seller.md b/docs/tutorials/pt/change-seller.md
index 9cb6d7dd2..8c6701eac 100644
--- a/docs/tutorials/pt/change-seller.md
+++ b/docs/tutorials/pt/change-seller.md
@@ -26,13 +26,13 @@ A troca de seller pode ocorrer em duas situações:
 - Seller cancela o pedido.
 - Marketplace decide trocar o seller.
 
-![seller_cancela_pedido_PT](//images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/ec1baf2bf28bddace01121efce7c05a8/seller_cancela_pedido_PT.png)
+![seller_cancela_pedido_PT](https://images.ctfassets.net/alneenqid6w5/1w1If5Xirav4fZKLQlpkPn/ec1baf2bf28bddace01121efce7c05a8/seller_cancela_pedido_PT.png)
 
 Você pode [configurar a janela de tempo para mudar seller de 0 a 30 dias](https://developers.vtex.com/vtex-rest-api/reference/updatewindowtochangeseller), sendo que, por padrão, são dois dias. Ao configurar a janela em 0 dias, não existe um período efetivo para a troca de sellers e a feature, apesar de configurada, não funciona na prática, fazendo com que o pedido siga para cancelamento.
 
 Ao ser notificado pelo seller sobre o cancelamento, o marketplace pode configurar quantos dias deseja para tomar uma ação e decidir entre cancelar a compra ou mudar de seller. Mas atenção: caso escolha pela troca, é de responsabilidade do próprio marketplace a decisão de informar a mudança ao cliente final.
 
-![mkt_cancela_seller_PT](//images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/55e6407af7ab3ffc3adec059e393f45c/mkt_cancela_seller_PT.png)
+![mkt_cancela_seller_PT](https://images.ctfassets.net/alneenqid6w5/3jMZldSV2RLu4P0xoUyrE/55e6407af7ab3ffc3adec059e393f45c/mkt_cancela_seller_PT.png)
 
 ## Limitações
 
diff --git a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
index 20d0f0c96..d930f0e51 100644
--- a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -34,7 +34,7 @@ Após [habilitar a funcionalidade](https://developers.vtex.com/vtex-rest-api/doc
 3. Modifique o preço para o valor desejado e aperte `ENTER`.
 4. Clique em `Fechar pedido`.
 
-![manualprice](//images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/286bde9df13e523ada732e2d89d70101/manualprice.gif)
+![manualprice](https://images.ctfassets.net/alneenqid6w5/6lKNt1yT41wOQCRv5Yv6ge/286bde9df13e523ada732e2d89d70101/manualprice.gif)
 
 Além da configuração na tela do Checkout, o preço de um produto também pode ser modificado por meio da API [Change Price](https://developers.vtex.com/vtex-rest-api/reference/pricechange), saiba mais em [Setting the price of an item manually](https://developers.vtex.com/vtex-rest-api/docs/enable-the-manual-price#setting-the-price-of-an-item-manually).
 
diff --git a/docs/tutorials/pt/changing-a-pages-body-class.md b/docs/tutorials/pt/changing-a-pages-body-class.md
index 5c6f166a3..7df4f6f9d 100644
--- a/docs/tutorials/pt/changing-a-pages-body-class.md
+++ b/docs/tutorials/pt/changing-a-pages-body-class.md
@@ -23,13 +23,13 @@ Os templates usados pelos layouts da loja, por padrão, não carregam nenhuma cl
 
 Veja, por exemplo, o código do template Department.
 
-![changeBodyClass1](//images.contentful.com/alneenqid6w5/pbQCDMUz3qO0q4SuwYaq4/7ebd6ca8a0af6cbce899535b83cd719a/changeBodyClass1.jpg)
+![changeBodyClass1](https://images.contentful.com/alneenqid6w5/pbQCDMUz3qO0q4SuwYaq4/7ebd6ca8a0af6cbce899535b83cd719a/changeBodyClass1.jpg)
 
 Ele tem um `id`, mas não uma `class`.
 
 No entanto, ao carregar um layout que use esse template, vemos que a classe `departamento` foi adicionada ao body da página.
 
-![changeBodyClass2](//images.contentful.com/alneenqid6w5/132c4r8rtGowUkOYe4YUaM/6b4a3bd0a9fc5f65fe1d950484088ba1/changeBodyClass2.jpg)
+![changeBodyClass2](https://images.contentful.com/alneenqid6w5/132c4r8rtGowUkOYe4YUaM/6b4a3bd0a9fc5f65fe1d950484088ba1/changeBodyClass2.jpg)
 
 Ou seja, o sistema insere essa classe automaticamente.
 
diff --git a/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
index 3a0891ae9..aef809a91 100644
--- a/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
@@ -51,9 +51,9 @@ Ou seja, estou usando as variáveis `preposicaonomeloja2` e `nomeloja`.
 Ao usar variáveis para compor um texto, substitua o símbolo <code>#</code> por <code>@</code>. Ou seja, <b>#variavel#</b> torna-se <b>@variavel@</b>.
 </div>
 
-![textos-importante pt](//images.ctfassets.net/alneenqid6w5/6B5XvqyDYI4G4eaC8OGEUw/8e55774262373bc01757e12736fe8f39/textos_importantes_pt.png)
+![textos-importante pt](https://images.ctfassets.net/alneenqid6w5/6B5XvqyDYI4G4eaC8OGEUw/8e55774262373bc01757e12736fe8f39/textos_importantes_pt.png)
 
-![exemplo-texto-importante pt ](//images.ctfassets.net/alneenqid6w5/3cyb4MfQGIu0kc424oYSqo/4d0e1d3bc0bb4af90feaad9398c6a807/3_pt.png)
+![exemplo-texto-importante pt ](https://images.ctfassets.net/alneenqid6w5/3cyb4MfQGIu0kc424oYSqo/4d0e1d3bc0bb4af90feaad9398c6a807/3_pt.png)
 
 Como defini que o conteúdo da primeira variável é "à" e o da segunda é "Loja Exemplo", o texto final renderizado no site será "Seja bem-vindo à Loja Exemplo".
 
diff --git a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
index 85327ff55..2f908bcb0 100644
--- a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
@@ -28,12 +28,12 @@ Para fazer a alteração, siga os passos abaixo:
 3. Clique no pedido para acessar a página de **Detalhes do pedido**.   
 4. Vá à seção **Valor total do pedido**, localizada no lado direito da página Detalhes do pedido.
 5. Clique em `Alterar valor final`. A página **Alterar valor** ficará disponível
-![valorfinal](//images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/9165c911db34e8067f90734077f67080/valorfinal__2_.png)
+![valorfinal](https://images.ctfassets.net/alneenqid6w5/5VwpodKoIiDSWBwYQs2rDc/9165c911db34e8067f90734077f67080/valorfinal__2_.png)
 6. Preencha os campos obrigatórios: 
     *  **Valor:** Selecione entre Desconto e Aumento, e insira o valor correspondente ao que deseja alterar.  
     * **Motivo:** escreva as razões para a mudança.  
 7. Clique em `Enviar`.
-![Alterar valor](//images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/5bd41102367f310c7c5e70626496d8cb/Alterar_valor__1_.png)
+![Alterar valor](https://images.ctfassets.net/alneenqid6w5/15TldKoBz42ds5fJswW13O/5bd41102367f310c7c5e70626496d8cb/Alterar_valor__1_.png)
 
 As alterações no pedido serão atualizadas na seção *Itens para Faturar, e Histórico do pedido*. Note que o valor total do pedido também será alterado.
 
diff --git a/docs/tutorials/pt/changing-tracking-data.md b/docs/tutorials/pt/changing-tracking-data.md
index b4320f9eb..4722a024a 100644
--- a/docs/tutorials/pt/changing-tracking-data.md
+++ b/docs/tutorials/pt/changing-tracking-data.md
@@ -38,4 +38,4 @@ Para alterar os dados de um pedido manualmente, siga os passos abaixo:
     * **Selecionar transportadora:** selecione qual transportadora realizará a entrega.
 7. Clique em `Salvar`.
 
-![Fatura](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
+![Fatura](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
diff --git a/docs/tutorials/pt/chat.md b/docs/tutorials/pt/chat.md
index 322eb1e3a..f68c923a5 100644
--- a/docs/tutorials/pt/chat.md
+++ b/docs/tutorials/pt/chat.md
@@ -25,46 +25,46 @@ Para começar você [deve ter criado os links](https://help.vtex.com/pt/tutoria
 
 Acesse “_**Atrair**_” > “_**Chat**_”  
 
-![Chat 1](//images.ctfassets.net/alneenqid6w5/7QkjjcJQEBynDhVtqSQHi/4a33ad632ba4d0c0913d2778e852cd6d/Screenshot_2022-08-29_at_17-02-02_Chat.png)
+![Chat 1](https://images.ctfassets.net/alneenqid6w5/7QkjjcJQEBynDhVtqSQHi/4a33ad632ba4d0c0913d2778e852cd6d/Screenshot_2022-08-29_at_17-02-02_Chat.png)
 
 Clique em “_**Novo**_”
 
-![Chat  2](//images.ctfassets.net/alneenqid6w5/3i0wj6QgqLwd1mqpIrN9Cj/e1951a2c9a93477b4c96f1b4afee0cc3/Screenshot_2022-08-29_at_17-02-07_Chat.png)
+![Chat  2](https://images.ctfassets.net/alneenqid6w5/3i0wj6QgqLwd1mqpIrN9Cj/e1951a2c9a93477b4c96f1b4afee0cc3/Screenshot_2022-08-29_at_17-02-07_Chat.png)
 
 Selecione qual será o **_link_** do seu chat :
 
-![Chat 3](//images.ctfassets.net/alneenqid6w5/5lcQyorVcU4ZFXsKJlerd5/7bb744985853675460e4775b1019d4d8/Screenshot_2022-08-29_at_17-02-12_Chat.png)
+![Chat 3](https://images.ctfassets.net/alneenqid6w5/5lcQyorVcU4ZFXsKJlerd5/7bb744985853675460e4775b1019d4d8/Screenshot_2022-08-29_at_17-02-12_Chat.png)
 
 **Lembre-se**: Ele pode ser uma _**Captura**_ ou um _**Seletivo**_.
 
 Defina o _Layout_: 
 
-![Chat 4](//images.ctfassets.net/alneenqid6w5/45MgsdFohomYzP2atFignF/0bfab8a649f076cead3547d17957890d/Screenshot_2022-08-29_at_17-02-19_Chat.png)
+![Chat 4](https://images.ctfassets.net/alneenqid6w5/45MgsdFohomYzP2atFignF/0bfab8a649f076cead3547d17957890d/Screenshot_2022-08-29_at_17-02-19_Chat.png)
 
 Você pode escolher as cores, mensagens e ir visualizando todas as alterações simultaneamente.
 
-![Chat 5](//images.ctfassets.net/alneenqid6w5/6v1BUpIM5UsdYmDisRjrLF/043369a7399ffd66dc76a97a088e570b/Screenshot_2022-08-29_at_17-02-28_Chat.png)
+![Chat 5](https://images.ctfassets.net/alneenqid6w5/6v1BUpIM5UsdYmDisRjrLF/043369a7399ffd66dc76a97a088e570b/Screenshot_2022-08-29_at_17-02-28_Chat.png)
 
 Você também pode configurar o CTAs do seu chat, ou seja, definir quando ele vai abrir automaticamente para o seu cliente. 
 
-![Chat 6](//images.ctfassets.net/alneenqid6w5/fBbGQGQ0idJ21232uW63u/dc35acc6cac9ee80a7ba1d6d36552d50/Screenshot_2022-08-29_at_17-02-34_Chat.png)
+![Chat 6](https://images.ctfassets.net/alneenqid6w5/fBbGQGQ0idJ21232uW63u/dc35acc6cac9ee80a7ba1d6d36552d50/Screenshot_2022-08-29_at_17-02-34_Chat.png)
 
 Veja um exemplo de “_Houver uma intenção de sair da página_” 
 
-![Chat 7](//images.ctfassets.net/alneenqid6w5/4mhPnDPQXDhbBAGXb3mVyw/be5f484fcca61f4b2f9553e51bd9e4a6/Screenshot_2022-08-29_at_17-02-42_Chat.png)
+![Chat 7](https://images.ctfassets.net/alneenqid6w5/4mhPnDPQXDhbBAGXb3mVyw/be5f484fcca61f4b2f9553e51bd9e4a6/Screenshot_2022-08-29_at_17-02-42_Chat.png)
 
 Defina onde mostrar o chat no seu site ou quando ele não irá aparecer: 
 
-![Chat 8](//images.ctfassets.net/alneenqid6w5/2dodZaa9eN1w5OszTVRgxp/88cc53edda282f4c0954aaae18dc9915/Screenshot_2022-08-29_at_17-02-49_Chat.png)
+![Chat 8](https://images.ctfassets.net/alneenqid6w5/2dodZaa9eN1w5OszTVRgxp/88cc53edda282f4c0954aaae18dc9915/Screenshot_2022-08-29_at_17-02-49_Chat.png)
 
 Depois de definir o layout e os gatilhos, clique em “**_Salvar_**”
 
 Para inserir o chat no seu site, acesse na aba “**_Chat_**” e clique no seletor e clique em “_**instruções de instalação**_” :
 
-![Chat 9](//images.ctfassets.net/alneenqid6w5/6AOJ9KqJxYgGtIG8b856Bu/81d1968ccebbfb72e35193a4a12150b4/Screenshot_2022-08-29_at_17-02-57_Chat.png)
+![Chat 9](https://images.ctfassets.net/alneenqid6w5/6AOJ9KqJxYgGtIG8b856Bu/81d1968ccebbfb72e35193a4a12150b4/Screenshot_2022-08-29_at_17-02-57_Chat.png)
 
 Basta copiar e colar o código fornecido no “**_Body_**” do painel administrativo do seu site:
 
-![Chat 10](//images.ctfassets.net/alneenqid6w5/5VggBGuNNuPxGkNS6RtMQR/4b3b14a171a47d9aad8cf73cff31faac/Screenshot_2022-08-29_at_17-03-03_Chat.png)
+![Chat 10](https://images.ctfassets.net/alneenqid6w5/5VggBGuNNuPxGkNS6RtMQR/4b3b14a171a47d9aad8cf73cff31faac/Screenshot_2022-08-29_at_17-03-03_Chat.png)
 
 E pronto, qualquer alteração feita no Chat dentro do painel da Suiteshare, já será alterado automaticamente no chat do seu site.
diff --git a/docs/tutorials/pt/check-order-delivery-details.md b/docs/tutorials/pt/check-order-delivery-details.md
index 0f39f547f..86515f2c3 100644
--- a/docs/tutorials/pt/check-order-delivery-details.md
+++ b/docs/tutorials/pt/check-order-delivery-details.md
@@ -45,7 +45,7 @@ Para ver esses detalhes, basta fazer uma [simulação de frete](/pt/tutorial/sim
 6. Informe o CEP do pedido.
 7. Clique em __Simular frete__.
 
-![simular-frete-pt](//images.ctfassets.net/alneenqid6w5/6TPVNOKh1uKmmMGGQAoeY2/e437d4fcd8f91d28f05813f936d30f4a/simular-frete-pt.png)
+![simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/6TPVNOKh1uKmmMGGQAoeY2/e437d4fcd8f91d28f05813f936d30f4a/simular-frete-pt.png)
 
 Para cada transportadora considerada na simulação, você pode ver os detalhes do pedido correspondente. Para isso, clique em __detalhar__.
 
diff --git a/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md b/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md
index 7a6ecb4a4..a996691d8 100644
--- a/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md
+++ b/docs/tutorials/pt/checking-how-an-order-delivery-deadline-was-calculated.md
@@ -23,7 +23,7 @@ Digamos que você deseja saber quais foram os critérios que a plataforma usou p
 
 Em primeiro lugar, vamos entrar no módulo __Todos os pedidos__ para ver o pedido.
 
-![2019-06-05 13 51 56-Todos os pedidos](//images.ctfassets.net/alneenqid6w5/1v711UNCK6lLyGvqXkDkRs/046e6d1af8cb038a15bf1674ea86081c/2019-06-05_13_51_56-Todos_os_pedidos.png) 
+![2019-06-05 13 51 56-Todos os pedidos](https://images.ctfassets.net/alneenqid6w5/1v711UNCK6lLyGvqXkDkRs/046e6d1af8cb038a15bf1674ea86081c/2019-06-05_13_51_56-Todos_os_pedidos.png) 
 
 >No canto superior direito, você vê a __data em que o pedido foi realizado__ (6 MAI 2019).
 >E na seção de Itens a Faturar em baixo, você vê o __prazo de entrega do pedido__ (22 MAI 2019).
@@ -33,25 +33,25 @@ Agora vamos entrar no módulo __Envio__ e simular o frete desse pedido.
 Para isso, siga os passos abaixo:
 
 1. No Admin VTEX, acesse **Envio > Simulação de Envio**, ou digite *Simulação de Envio* na barra de busca no topo da página.  
-2. Insira o nome ou o ID de cada SKU que estava no carrinho do pedido que você deseja investigar, incluindo a quantidade de cada um deles.![2019-06-05 14 07 20-Simulador de envio](//images.ctfassets.net/alneenqid6w5/2AAUbA9NuAlLWW6tW2eFo8/8499c3f8f6185c2f1f8568fbada87d4e/2019-06-05_14_07_20-Simulador_de_envio.png)
+2. Insira o nome ou o ID de cada SKU que estava no carrinho do pedido que você deseja investigar, incluindo a quantidade de cada um deles.![2019-06-05 14 07 20-Simulador de envio](https://images.ctfassets.net/alneenqid6w5/2AAUbA9NuAlLWW6tW2eFo8/8499c3f8f6185c2f1f8568fbada87d4e/2019-06-05_14_07_20-Simulador_de_envio.png)
 3. Insira o CEP do pedido.
 4. Clique em __Simular frete__.
 
 No exemplo abaixo, note que 4 transportadoras foram consideradas, e 12 foram desconsideradas.
 
-![2](//images.ctfassets.net/alneenqid6w5/GFpG6fdmrpIubx6AClQIx/34d23cc1b849becdf34d0c10ed4d0c54/2.png)
+![2](https://images.ctfassets.net/alneenqid6w5/GFpG6fdmrpIubx6AClQIx/34d23cc1b849becdf34d0c10ed4d0c54/2.png)
 
 Consultando mais uma vez a tela de detalhes do pedido, vemos que o tipo de entrega escolhido pelo cliente para esse pedido foi o __Expressa__, e que a transportadora escolhida pela plataforma para realizar esse pedido foi a __Expressa & CO__.
 
-![3](//images.ctfassets.net/alneenqid6w5/5cfMvMBQJ2PH6MSXEPWC8E/42e5889646c37d4ee1595866e3a797f3/3.png)
+![3](https://images.ctfassets.net/alneenqid6w5/5cfMvMBQJ2PH6MSXEPWC8E/42e5889646c37d4ee1595866e3a797f3/3.png)
 
 Portanto, voltando à simulação de frete, no módulo Envio, concluímos que a primeira opção foi a escolhida nesse pedido - e que, portanto, o prazo de entrega total do pedido foi de 12 dias.
 
-![4](//images.ctfassets.net/alneenqid6w5/51uwhtB3nSKyMtXY2zVbic/a7d28ccb49dd18b1bb60d6e8d9bff73c/4.png)
+![4](https://images.ctfassets.net/alneenqid6w5/51uwhtB3nSKyMtXY2zVbic/a7d28ccb49dd18b1bb60d6e8d9bff73c/4.png)
 
 Agora basta clicar em __detalhar__ para ver os tempos de custo que foram usados no cálculo desse prazo de entrega.
 
-![5](//images.ctfassets.net/alneenqid6w5/3USKpGaWgl6qHuYqE7iqrY/6158faed327f8bafc30fee04e464f16c/5.png)
+![5](https://images.ctfassets.net/alneenqid6w5/3USKpGaWgl6qHuYqE7iqrY/6158faed327f8bafc30fee04e464f16c/5.png)
 
 Cada um dos três tempos de custo corresponde ao que foi definido para as três etapas da rota de logística: estoque, doca e transportadora.
 
diff --git a/docs/tutorials/pt/checkout-vtex-overview.md b/docs/tutorials/pt/checkout-vtex-overview.md
index 406a90f3a..87889095d 100644
--- a/docs/tutorials/pt/checkout-vtex-overview.md
+++ b/docs/tutorials/pt/checkout-vtex-overview.md
@@ -35,7 +35,7 @@ Os passos abaixo demonstram a experiência de compra de um cliente e o papel do
 
 Sempre que o cliente realiza uma modificação no carrinho (adição ou remoção de itens), ou que a tela do Checkout é atualizada, a seguinte cadeia de processos internos no Checkout é executada.
 
-![Checkout overview](//images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/c25d968b81626de55ab890ef67834bb8/Checkout_Overview_PT.png)
+![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/c25d968b81626de55ab890ef67834bb8/Checkout_Overview_PT.png)
 
 <div class="alert alert-info">
 Caso um ou mais itens escolhidos pelo cliente sejam elegíveis para entrega por um <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#o-que-e-um-seller-white-label">Seller white label</a>, serão realizadas simulações (conforme exibido no lado direito da figura), de modo a determinar quais sellers serão responsáveis pela entrega dos itens. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Seleção de sellers white label</a>.
diff --git a/docs/tutorials/pt/cms-folder-structure.md b/docs/tutorials/pt/cms-folder-structure.md
index a4d705366..5cc1ee3e6 100644
--- a/docs/tutorials/pt/cms-folder-structure.md
+++ b/docs/tutorials/pt/cms-folder-structure.md
@@ -33,7 +33,7 @@ Estas são as pastas que toda loja precisa ter no CMS para garantir o correto fu
 
 Veja abaixo estas pastas básicas no CMS:
 
-![pastasObrigatorias](//images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
+![pastasObrigatorias](https://images.contentful.com/alneenqid6w5/2yLeJGvd48WcA6egy2kSSC/43e22907371f954df25d5fd7e5dd116b/pastasObrigatorias.png)
 
 Estas pastas vêm por padrão no ambiente de todas as lojas VTEX.
 
diff --git a/docs/tutorials/pt/cms-overview.md b/docs/tutorials/pt/cms-overview.md
index bf51bc099..d24c22652 100644
--- a/docs/tutorials/pt/cms-overview.md
+++ b/docs/tutorials/pt/cms-overview.md
@@ -15,7 +15,7 @@ legacySlug: cms-visao-geral
 subcategory: 3PNmhq67KMmGTBSfIWJdcQ
 ---
 
-![CMS Capa overview](//images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
+![CMS Capa overview](https://images.ctfassets.net/alneenqid6w5/5FaFzk5z2vdyWIKl5AlCby/e241b8b8231499bfec4c8ce67fb27d0b/CAPA_OVERVIEW_CMS.png)
 
 CMS (Content Management System) é uma funcionalidade voltada para o gerenciamento de conteúdo de forma prática e constante.
 
diff --git a/docs/tutorials/pt/cms-store-overview.md b/docs/tutorials/pt/cms-store-overview.md
index 3aa5eff31..7dd0db1af 100644
--- a/docs/tutorials/pt/cms-store-overview.md
+++ b/docs/tutorials/pt/cms-store-overview.md
@@ -19,7 +19,7 @@ A página **Loja** permite que você realize configurações de SEO, habilite fl
 
 No Admin VTEX, acesse **Configurações da loja > Storefront > Loja*** e descubra as principais ferramentas disponíveis na interface.
 
-![CMS Loja](//images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/40e653a93a4543bff834816c38ec018b/store-pt-overview.png)
+![CMS Loja](https://images.ctfassets.net/alneenqid6w5/7tUjcDHM8LXijxN9i5Oll0/40e653a93a4543bff834816c38ec018b/store-pt-overview.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Antes de fazer alterações na aba <b>Avançado</b>, entre em contato com a sua equipe de desenvolvedores e consulte a nossa <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-best-practices-for-optimizing-performance#enabling-store-settings">documentação sobre a otimização de desempenho</a> para mais informações.
diff --git a/docs/tutorials/pt/collection-highlight-control.md b/docs/tutorials/pt/collection-highlight-control.md
index 68076bdc4..4cbc78231 100644
--- a/docs/tutorials/pt/collection-highlight-control.md
+++ b/docs/tutorials/pt/collection-highlight-control.md
@@ -28,7 +28,7 @@ Em primeiro lugar, vamos ver onde se encontra a flag Highlight:
 3. Clique em uma coleção.
 4. Marque a flag __Highlight__, que fica na tela da coleção, e clique em __Save Product Cluster__.
 
-![CollectionHighlightFlag](//images.contentful.com/alneenqid6w5/4ced6Gcbeg662KewckyQka/77aaef77fc87cf8112f759c867a6bd4b/CollectionHighlightFlag.png)
+![CollectionHighlightFlag](https://images.contentful.com/alneenqid6w5/4ced6Gcbeg662KewckyQka/77aaef77fc87cf8112f759c867a6bd4b/CollectionHighlightFlag.png)
 
 Ao marcar a flag, você informa ao sistema que sempre que o controle de destaque for usado no template de uma página, os produtos exibidos nessa página que fizerem parte da coleção em questão devem aparecer com o elemento HTML abaixo, onde no lugar de `{nomeDaColecao}` aparece o nome da coleção cadastrada no CMS:
 
diff --git a/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md b/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
index 0c7b72d35..9766f67cd 100644
--- a/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
+++ b/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
@@ -29,7 +29,7 @@ Para encontrar essa linha de código, acesse o front-end da sua loja, entre nas
 
 Veja abaixo a relação entre a pasta no CMS e o código-fonte da loja.
 
-![CommerceContext](//images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
+![CommerceContext](https://images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
 
 <div class="alert alert-info">
 Essa linha de código está sempre comentada. Portanto, ela tem função apenas informativa. Ou seja, não realiza nenhuma ação.
diff --git a/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md b/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
index 4d52f0fbb..aa052ecdc 100644
--- a/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
+++ b/docs/tutorials/pt/como-solicitar-uma-antecipacao-dos-recebiveis-pelo-vtex-payment.md
@@ -31,7 +31,7 @@ Agora que você já conferiu o saldo, é importante ter em mente que o valor mí
 
 Por exemplo, caso o seu menor recebível seja de R$10, esse é o valor mínimo que você pode antecipar. Já o valor máximo é informado no próprio Admin - o saldo que você acabou de conferir - na página de “Antecipar recebíveis”. 
 
-![anteciparpaymentPT](//images.ctfassets.net/alneenqid6w5/25BWOQcUJ4RHHefod0IkFw/3d4ba6ba362db2362e870420dd3653a3/anteciparpaymentPT.png)
+![anteciparpaymentPT](https://images.ctfassets.net/alneenqid6w5/25BWOQcUJ4RHHefod0IkFw/3d4ba6ba362db2362e870420dd3653a3/anteciparpaymentPT.png)
 
 <div class=”alert alert-info”>
 <strong>Atenção</strong>: recebíveis em disputa ou previstos para o próximo dia útil não podem ser antecipados.
diff --git a/docs/tutorials/pt/conditions-builder-usage-examples.md b/docs/tutorials/pt/conditions-builder-usage-examples.md
index 1154c96b9..9b578ea90 100644
--- a/docs/tutorials/pt/conditions-builder-usage-examples.md
+++ b/docs/tutorials/pt/conditions-builder-usage-examples.md
@@ -23,7 +23,7 @@ Para entender __para que__ criar condições, veja o artigo [Criar Preços Condi
 
 UTM (Marketing tag) é uma informação que diz respeito a origem do tráfego do cliente. Então, no app existe um bloco que verifica esse tipo de informação.    
 
-![utm_source_port](//images.ctfassets.net/alneenqid6w5/1X8rOnz0wwOgMWKE2IccGe/97a3907728c129ec075f425c9e221230/utm_source_port.png)  
+![utm_source_port](https://images.ctfassets.net/alneenqid6w5/1X8rOnz0wwOgMWKE2IccGe/97a3907728c129ec075f425c9e221230/utm_source_port.png)  
 
 <div class="alert alert-warning"><strong>Nota: </strong>
 É possível que sua loja utilize customização e por isso as informações de UTM contidas na URL não estão sendo passadas para o nosso sistema. Caso use customização de Javascript, leia o artigo <a href="https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho">Por que as utms não estão sendo aplicadas ao carrinho</a>
@@ -42,7 +42,7 @@ __utm_campaign__ informa em __qual campanha__ especificamente o seu cliente clic
 __utm_medium__ informa qual __canal de propaganda__ atingiu seu cliente que pode ser, por exemplo, Email ou Banner em um site. No caso da imagem, o bloco verifica se o canal foi o *email*.  
   
   
-![utmport](//images.ctfassets.net/alneenqid6w5/6dRgQcTn68eU8gOIIeu42o/4563858ba898bde92103408d12a9403d/utmport.png)  
+![utmport](https://images.ctfassets.net/alneenqid6w5/6dRgQcTn68eU8gOIIeu42o/4563858ba898bde92103408d12a9403d/utmport.png)  
   
 Para cada um desses blocos, você têm a opção de verificar se:  
 
@@ -57,7 +57,7 @@ Para cada um desses blocos, você têm a opção de verificar se:
 Vamos supor que você queira que, para um certo produto, o preço seja especial caso o seu cliente clicou no *banner* do dia das mães que recebeu por email.  
 Logo você tem que criar uma condição que verifica se o __utm_medium__ é `email` e se o __utm_campaign__ é `dia_das_maes`. Então vai parecer algo como isso :  
 
-![exemplo](//images.ctfassets.net/alneenqid6w5/4MTxq9CBK0EooyyGo4uKck/b5de55ca5990655b855760ea9138d91a/exemplo.png)  
+![exemplo](https://images.ctfassets.net/alneenqid6w5/4MTxq9CBK0EooyyGo4uKck/b5de55ca5990655b855760ea9138d91a/exemplo.png)  
 
 ## Condições pelo carrinho de compra
 
@@ -66,7 +66,7 @@ Há 3 blocos que dizem respeito aos itens contidos carrinho de compra do usuári
 ### Quantidade Total
 Esse bloco analisa a quantidade de itens no carrinho como um todo.
 
-![qtdItens](//images.ctfassets.net/alneenqid6w5/5CG8dotStaeC628gCWCUGO/4fbc8f8b107c2725d671c63a999ad189/qntdItens.png)  
+![qtdItens](https://images.ctfassets.net/alneenqid6w5/5CG8dotStaeC628gCWCUGO/4fbc8f8b107c2725d671c63a999ad189/qntdItens.png)  
 
 - __pelo menos__ -> verifica se no carrinho de compra do usuário existe __3 ou mais itens__.
 - __no máximo__ -> verifica se no carrinho de compra do usuário existe __3 ou menos itens__.
@@ -74,7 +74,7 @@ Esse bloco analisa a quantidade de itens no carrinho como um todo.
 ### Quantidade de um SKU específico
 Esse bloco analisa a quantidade do item específico ao qual ele será atrelado no [*Conditional Price*](http://help.vtex.com/pt/tutorial/como-criar-precos-condicionais)
 
-![itemEspecifico](//images.ctfassets.net/alneenqid6w5/7Hi9CZ1as8Oi8YkawgIKcs/5a8f7e4f5b7b9a9af64a70735c14f7df/itemEspecifico.png)  
+![itemEspecifico](https://images.ctfassets.net/alneenqid6w5/7Hi9CZ1as8Oi8YkawgIKcs/5a8f7e4f5b7b9a9af64a70735c14f7df/itemEspecifico.png)  
 
 - __pelo menos__ -> verifica se no carrinho de compra do usuário existe __3 ou mais daquele item__.
 - __no máximo__ -> verifica se no carrinho de compra do usuário existe __3 ou menos daquele item__.
@@ -84,7 +84,7 @@ Esse bloco analisa a quantidade do item específico ao qual ele será atrelado n
 ### Valor total
 Esse bloco analisa o valor total que existe no carrinho.
 
-![valorTotal](//images.ctfassets.net/alneenqid6w5/1fWh5tYsxSC60Ii8EgUWwe/830305c6df9657768663588e5b660f5d/valorTotal.png)  
+![valorTotal](https://images.ctfassets.net/alneenqid6w5/1fWh5tYsxSC60Ii8EgUWwe/830305c6df9657768663588e5b660f5d/valorTotal.png)  
 
 - __pelo menos__ -> verifica se a __soma dos valores__ dos itens no carrinho vale __100 reais ou mais__.
 - __no máximo__ -> verifica se a __soma dos valores__ dos itens existrrinho vale __100 reais ou menos__.
@@ -94,7 +94,7 @@ Esse bloco analisa o valor total que existe no carrinho.
 Vamos supor que você queira dar um preço mais barato a um shampoo caso o cliente esteja levando __exatamente 3 unidades__, mas além disso precisa estar levando __no mínimo 150 reais__ em compras.
 A condição a ser criada será : 
 
-![Exemplo2](//images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
+![Exemplo2](https://images.ctfassets.net/alneenqid6w5/11Z9LujUl66G80yGQyKI6S/fa33819d9e0ef37113466e3612d370d5/exemplo2.png)  
 
 
 
diff --git a/docs/tutorials/pt/configuracao-de-precos.md b/docs/tutorials/pt/configuracao-de-precos.md
index 1d2c054a9..73c9f9797 100644
--- a/docs/tutorials/pt/configuracao-de-precos.md
+++ b/docs/tutorials/pt/configuracao-de-precos.md
@@ -54,11 +54,11 @@ Para criar uma nova regra, siga os passos a seguir:
     - **Sempre ativar:** a tabela de preço está constantemente ativada, independente de condições.
     - **Ativar em condições específicas:** a tabela de preço será ativada segundo as condições configuradas na regra. Veja as possibilidades de configuração com as imagens a seguir:
     
-    ![PT-regra-tabela-de-preco3](//images.ctfassets.net/alneenqid6w5/45Vklz3dKi6SH0o1Rcz33I/93beeac027a6f9ab037f348a63d2ba03/PT-regra-tabela-de-preco3.png)
+    ![PT-regra-tabela-de-preco3](https://images.ctfassets.net/alneenqid6w5/45Vklz3dKi6SH0o1Rcz33I/93beeac027a6f9ab037f348a63d2ba03/PT-regra-tabela-de-preco3.png)
     
-    ![PT-regra-tabela-de-preco](//images.ctfassets.net/alneenqid6w5/3ClC00TNkMXFIgflRdepP/d46d2298cf13f37cbbbd71acca0d39ae/PT-regra-tabela-de-preco.png)
+    ![PT-regra-tabela-de-preco](https://images.ctfassets.net/alneenqid6w5/3ClC00TNkMXFIgflRdepP/d46d2298cf13f37cbbbd71acca0d39ae/PT-regra-tabela-de-preco.png)
   
-    ![PT-regra-tabela-de-preco2](//images.ctfassets.net/alneenqid6w5/3M4QVimY2pgh2NBuuO9u7s/3aa68e1602f16548be024f29448fa21a/PT-regra-tabela-de-preco2.png)
+    ![PT-regra-tabela-de-preco2](https://images.ctfassets.net/alneenqid6w5/3M4QVimY2pgh2NBuuO9u7s/3aa68e1602f16548be024f29448fa21a/PT-regra-tabela-de-preco2.png)
     
 7. Clique em Confirmar.
 
diff --git a/docs/tutorials/pt/configurar-o-cartman.md b/docs/tutorials/pt/configurar-o-cartman.md
index 6226878fb..f96d99408 100644
--- a/docs/tutorials/pt/configurar-o-cartman.md
+++ b/docs/tutorials/pt/configurar-o-cartman.md
@@ -26,9 +26,9 @@ Por padrão, o Cartman já vem habilitado e disponível para uso no Checkout de
 Para desabilitar o Cartman, siga o passo a passo a seguir:
 
 1. Clique no ícone azul no canto inferior direito da tela
-![cartmantuto1](//images.ctfassets.net/alneenqid6w5/1DWwcldpXDu4fplLm6aLjD/6c588311f60b01e5cd1e76aceb257743/cartmantuto1.PNG)
+![cartmantuto1](https://images.ctfassets.net/alneenqid6w5/1DWwcldpXDu4fplLm6aLjD/6c588311f60b01e5cd1e76aceb257743/cartmantuto1.PNG)
 2. Clique em `Desativar o Cartman` na parte inferior da janela
-![cartmantuto2](//images.ctfassets.net/alneenqid6w5/pzjFEx27xjbsRc1rWCotI/504771d0251a952769b043d17412250f/cartmantuto2.PNG)
+![cartmantuto2](https://images.ctfassets.net/alneenqid6w5/pzjFEx27xjbsRc1rWCotI/504771d0251a952769b043d17412250f/cartmantuto2.PNG)
 
 Desse modo, a ferramenta será interrompida. Porém, se for preciso habilitá-la novamente, o processo “reverso” é semelhante ao primeiro passo a passo.
 
@@ -38,7 +38,7 @@ Existem duas formas de “reabilitar” o Cartman.
 
 - Domínio de site
 Para que o Cartman seja reativado para o site inteiro, basta clicar em `Reativar Agora` na mesma janela de configuração. Automaticamente, a ferramenta retoma o seu funcionamento.
-![cartmantuto3](//images.ctfassets.net/alneenqid6w5/2YR5bMxxzhMjsRDbmSHHsG/862261ed7433e068cbf2b19f2d8bb652/cartmantuto3.PNG)
+![cartmantuto3](https://images.ctfassets.net/alneenqid6w5/2YR5bMxxzhMjsRDbmSHHsG/862261ed7433e068cbf2b19f2d8bb652/cartmantuto3.PNG)
 
 - Navegador de uso 
 Se o interesse for exibir o Cartman apenas no navegador do usuário de e-commerce, é preciso incluir a query string `?cartman=on` no final da URL desejada - `https://accountname.vtex.com/checkout?cartman=on` - e reiniciar o domínio. Desse modo, o ícone azul aparecerá novamente no canto inferior direito da página.
diff --git a/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md b/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
index cc163bbb6..2442f9388 100644
--- a/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
+++ b/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
@@ -29,7 +29,7 @@ Nesse cenário, caso um cliente do Mercado Livre faça uma compra com dois ou ma
 
 A VTEX não recomenda esse tipo de configuração porque os pedidos nesse cenário não irão integrar.
 
-![cenario problema](//images.contentful.com/alneenqid6w5/5DYri1Pw4wLdVV2g6kIUTP/11dad204a77517227931d73f5f2bb100/cenario_problema.JPG)
+![cenario problema](https://images.contentful.com/alneenqid6w5/5DYri1Pw4wLdVV2g6kIUTP/11dad204a77517227931d73f5f2bb100/cenario_problema.JPG)
 
 Entretanto, existem dois cenários na integração das lojas VTEX com o Mercado Livre que podem evitar que esse conflito aconteça. Para isso é necessário que sua loja tenha as seguintes configurações:
 
@@ -42,7 +42,7 @@ O seller utiliza uma única subaccount na VTEX e integra com uma única conta no
 
 Nesse cenário, caso um usuário faça uma compra no Mercado Livre com dois ou mais produtos no carrinho das diferentes lojas oficiais da conta do seller, o pedido será importado na VTEX sem problemas. Isso acontece porque os produtos que estão sendo anunciados no Mercado Livre fazem parte do catálogo de uma única subaccount VTEX.
 
-![cenario ideal](//images.contentful.com/alneenqid6w5/6aVRPYSaLIYnIknsdqzCFz/8b8f5380a55d4b0e494f6599918e073f/cenario_ideal.JPG)
+![cenario ideal](https://images.contentful.com/alneenqid6w5/6aVRPYSaLIYnIknsdqzCFz/8b8f5380a55d4b0e494f6599918e073f/cenario_ideal.JPG)
 
 ## Múltiplas subaccounts VTEX e múltiplas lojas oficiais
 
@@ -50,4 +50,4 @@ O seller VTEX possui duas ou várias sub accounts e utiliza cada uma delas para
 
 Nesse cenário, caso um usuário faça uma compra no Mercado Livre com dois ou mais produtos no mesmo carrinho pertencentes a subaccounts diferentes, os pedidos serão integrados normalmente em cada sub account na VTEX. Isso ocorre já que cada pedido gerado no Mercado Livre está vinculado a uma subaccount diferente na VTEX, portanto  os produtos vendidos coincidem com o catálogo de cada subaccount.
 
-![cenario atual](//images.contentful.com/alneenqid6w5/73HsUcU7h3BwDNlTGeB1kq/7a52aa2da4fb12abfbad86abd70bc9d2/cenario_atual.JPG)
+![cenario atual](https://images.contentful.com/alneenqid6w5/73HsUcU7h3BwDNlTGeB1kq/7a52aa2da4fb12abfbad86abd70bc9d2/cenario_atual.JPG)
diff --git a/docs/tutorials/pt/configure-cartman.md b/docs/tutorials/pt/configure-cartman.md
index 4f2adefb6..511f08ced 100644
--- a/docs/tutorials/pt/configure-cartman.md
+++ b/docs/tutorials/pt/configure-cartman.md
@@ -58,7 +58,7 @@ Para saber usar essa ferramenta, leia o guia [Simulador de Promoções](https://
 
 Ao acessar o menu **Ver detalhes do item**, é possível verificar as informações específicas de cada um dos produtos selecionados no carrinho.
 
-![Detalhes do item](//images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/be488177768aa068425cd4fe3bfe9186/Detalhes_do_item.PNG)
+![Detalhes do item](https://images.ctfassets.net/alneenqid6w5/1EH9jYZZwOSTcCDKqoQocj/be488177768aa068425cd4fe3bfe9186/Detalhes_do_item.PNG)
 
 ### Adicionar itens específicos no carrinho
 
@@ -68,7 +68,7 @@ Em **Adicionar itens pelo ID do SKU**, novos itens podem ser inseridos no carrin
 - **Quantidade de cada item**: indicação de quantas unidades do SKU serão adicionadas no carrinho.
 - **ID do seller**: número de identificação do seller que realizará a entrega do item.
 
-![Adicionar itens pelo ID do SKU](//images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/d77dd07bcc3886f41bad702ac74da401/Adicionar_itens_pelo_ID_do_SKU.PNG)
+![Adicionar itens pelo ID do SKU](https://images.ctfassets.net/alneenqid6w5/3HfuNsrFblpnncoUW2UQl2/d77dd07bcc3886f41bad702ac74da401/Adicionar_itens_pelo_ID_do_SKU.PNG)
 
 ### Adicionar itens aleatórios no carrinho
 
@@ -82,7 +82,7 @@ Em **Adicionar itens aleatórios**, novos itens do catálogo da loja podem ser i
 - ID do seller
 - Faixa de preço (Preço de / Preço até)
 
-![Adicionar itens aleatórios](//images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/805100572b36c043100c941fda45b732/Adicionar_itens_aleat__rios.PNG)
+![Adicionar itens aleatórios](https://images.ctfassets.net/alneenqid6w5/3vHoO3Pm1Vnsc2QXYOJMQW/805100572b36c043100c941fda45b732/Adicionar_itens_aleat__rios.PNG)
 
 ### Definir dados de marketing
 
@@ -94,7 +94,7 @@ Na opção **Definir dados de marketing**, é possível aplicar cupons de descon
 - **utmi_cp**: utm interna utilizada para definir quando será aplicada uma determinada promoção, de acordo com a utm descrita na URL do pedido. 
 - **Cupom**: código do cupom de desconto a ser adicionado no carrinho.
 
-![Definir dados de marketing](//images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/ae8e80765f7ff1255f03e5f48a4b4edb/Definir_dados_de_marketing.PNG)
+![Definir dados de marketing](https://images.ctfassets.net/alneenqid6w5/5jutuQsztAkNGjFHdPk27a/ae8e80765f7ff1255f03e5f48a4b4edb/Definir_dados_de_marketing.PNG)
 
 Para saber mais sobre UTMs e UTMIs , acesse [O que são utm_source, utm_campaign e utm_medium](https://help.vtex.com/pt/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii#) e [O que são as UTMs internas utmi_cp, utmi_pc e utmi_p](https://help.vtex.com/pt/tutorial/o-que-sao-as-utms-internas-utmi_cp-utmi_pc-e-utmi_p#).
 
diff --git a/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md b/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md
index bf2278c37..263f1c955 100644
--- a/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md
+++ b/docs/tutorials/pt/configure-direct-consumer-credit-cdc-by-losango.md
@@ -44,9 +44,9 @@ Tendo em mãos o script pré-aprovado de customização, siga as instruções ab
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Checkout**, ou digite **Checkout** na barra de busca no topo da página.
 2. Clique no ícone <img src="https://images.ctfassets.net/alneenqid6w5/3d4KBPLr2piZGC48KD3qgh/6f808efc5450f36faa773d4c7d848b68/CDC-Losango-1.png" style="width: 23px;" /> correspondente ao site que será customizado
-    ![CDC-Losango-2](//images.ctfassets.net/alneenqid6w5/7iUE1B4xlYF96gMs0oMfUn/2a55fcd4cc8f0239a0785634e29a18df/CDC-Losango-2.png)
+    ![CDC-Losango-2](https://images.ctfassets.net/alneenqid6w5/7iUE1B4xlYF96gMs0oMfUn/2a55fcd4cc8f0239a0785634e29a18df/CDC-Losango-2.png)
 3. Clique na aba Código e selecione o arquivo `checkout6-custom.js`.
-    ![CDC-Losango-3](//images.ctfassets.net/alneenqid6w5/248J5RJvoSq2olzQoPsNKn/3598c85f81649667f21d4d5fa40d71b4/CDC-Losango-3.png)
+    ![CDC-Losango-3](https://images.ctfassets.net/alneenqid6w5/248J5RJvoSq2olzQoPsNKn/3598c85f81649667f21d4d5fa40d71b4/CDC-Losango-3.png)
 4. Cole o script pré-aprovado de customização __no fim do campo de texto__.
 5. Clique no botão __Salvar__ para confirmar as alterações.
 
@@ -74,7 +74,7 @@ Para finalizar a configuração do CDC Online Losango e disponibilizar este meio
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página. 
 2. Acesse a aba **Condições de Pagamento**. Clique no ícone <img src="https://images.ctfassets.net/alneenqid6w5/3VXFXGXxCMc9cRMehCiuth/6ae901b40c89d05d4c252feb8df14f5a/CDC-Losango-5.png" style="width: 23px;" /> e escolha __Losango__.
 
-    ![CDC-Losango-8](//images.ctfassets.net/alneenqid6w5/1sGB3vlu73A9Ms6EmbIeeG/e22c65c4e528e23f2c00caef0a930323/CDC-Losango-8.png)
+    ![CDC-Losango-8](https://images.ctfassets.net/alneenqid6w5/1sGB3vlu73A9Ms6EmbIeeG/e22c65c4e528e23f2c00caef0a930323/CDC-Losango-8.png)
 
 3. Configure e ative a [condição de pagamento](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) com as regras desejadas. Não se esqueça de __Salvar__ ao concluir o preenchimento.
 
diff --git a/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
index a16e049fb..6a36a777d 100644
--- a/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
@@ -45,7 +45,7 @@ Aqui, a propriedade comum dos clientes é que eles também são funcionários da
 Este artigo assume que os colaboradores estão devidamente registrados com um campo booleano `é funcionário` definido como verdadeiro em seus respectivos documentos para a entidade de dados CL, como demonstrado na figura abaixo. 
 
 Caso contrário, verifique o artigo [Criando um campo no Master Data](https://help.vtex.com/pt/tutorial/como-crio-um-campo-no-master-data--frequentlyAskedQuestions_1829) para criar um campo que identifique os funcionários e configure-o adequadamente para cada documento correspondente aos funcionários.
-![Campo do colaborador](//images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
+![Campo do colaborador](https://images.ctfassets.net/alneenqid6w5/58zHOX5joCiSGRfGH1QcVS/550d4899318a5728eb0d73f04a32b710/Employee_field.png)
 
 <div class="alert-info" role="alert">São muitos os detalhes para configurar uma promoção. Se você precisar de informações adicionais sobre este assunto, consulte o artigo <a href="https://help.vtex.com/pt/tutorial/como-criar-promocoes--tutorials_320">Criar promoções</a>.</div>
 
@@ -60,4 +60,4 @@ Com o campo configurado, a promoção pode ser criada seguindo os passos abaixo:
 7. No final da página, clique no botão **Salvar***.
 
 Depois disso, a promoção já funcionará conforme configurada. O desconto é mostrado apenas no carrinho de compras. A imagem abaixo mostra um exemplo com 99% de desconto.
-![carrinho de compras com desconto](//images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
+![carrinho de compras com desconto](https://images.ctfassets.net/alneenqid6w5/475MwMGUzp7GzqF0xYFVUq/599d65a4eb894d02d8cfb0a6c1a55463/Carrinho_com_desconto.png)
diff --git a/docs/tutorials/pt/configure-template-in-smartcheckout-update.md b/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
index 07ff95dcf..80900dcf8 100644
--- a/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
@@ -37,11 +37,11 @@ Cada site cadastrado corresponde a um multidomínio (caso a conta possua multido
 
 Criação do novo site: 
 
-![Novo Site](//images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
+![Novo Site](https://images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
 
 Acesso ao __Nome da Conta__: 
 
-![PT Configuração da Conta Nome Loja](//images.ctfassets.net/alneenqid6w5/5SDjJWbYx8qiYMuvaKNEF/7c3b2eaa76035f0d2682fb07053dc3a1/PT_Paint_Nome_da_Conta.png)
+![PT Configuração da Conta Nome Loja](https://images.ctfassets.net/alneenqid6w5/5SDjJWbYx8qiYMuvaKNEF/7c3b2eaa76035f0d2682fb07053dc3a1/PT_Paint_Nome_da_Conta.png)
 
 ## Editar e configurar site
 
@@ -56,13 +56,13 @@ Acesso ao __Nome da Conta__:
    - __Páginas__: exibir as páginas existentes para o site. 
 
 Exemplo de sites existentes em uma mesma conta:
-![PT Cards Portal](//images.ctfassets.net/alneenqid6w5/3662yoC7zsRw8ME8bI7Efo/f3c845f13ea5586364b28b807cc3c3fa/PT_Cards_Portal.png)
+![PT Cards Portal](https://images.ctfassets.net/alneenqid6w5/3662yoC7zsRw8ME8bI7Efo/f3c845f13ea5586364b28b807cc3c3fa/PT_Cards_Portal.png)
 
 Exemplo de páginas disponíveis para um site:
-![PT Paginas Cropped (2)](//images.ctfassets.net/alneenqid6w5/4d5vICcJDiNZFR8fIpn9j0/fb8cf9adceae47b99eac9f352b1b912f/PT_Paginas_Cropped__2_.png)
+![PT Paginas Cropped (2)](https://images.ctfassets.net/alneenqid6w5/4d5vICcJDiNZFR8fIpn9j0/fb8cf9adceae47b99eac9f352b1b912f/PT_Paginas_Cropped__2_.png)
 
 Caso deseje __excluir__ um site, clique no botão de exclusão do site desejado, como no exemplo indicado abaixo:
-![PT Card Croppped Delete](//images.ctfassets.net/alneenqid6w5/2c4FWLHb0TLa8mEJXOdmg4/71a9f95969d7e8cfe6c9d1379b4e5071/PT_Card_Croppped_Delete.png)
+![PT Card Croppped Delete](https://images.ctfassets.net/alneenqid6w5/2c4FWLHb0TLa8mEJXOdmg4/71a9f95969d7e8cfe6c9d1379b4e5071/PT_Card_Croppped_Delete.png)
 
 A seguir, vamos aprofundar o passo a passo da configuração das oções de menu: __Código__ e __Checkout__, sendo estas responsáveis por configurar as páginas de *Checkout* e *Order Placed*.
 
@@ -79,7 +79,7 @@ A seguir, vamos aprofundar o passo a passo da configuração das oções de menu
   <li><b>Cálculo das opções de Entrega (Beta e Stable)</b>: selecione se o cálculo do frete será feito a partir da planilha ou por geolocalização.</li>
   </ul>
 
-![PT Editar Checkout](//images.ctfassets.net/alneenqid6w5/nzvyVXocA6pW8l9pBvRzg/1059880c29b9e57e4505b654c9a40013/PT_Editar_Checkout.png)
+![PT Editar Checkout](https://images.ctfassets.net/alneenqid6w5/nzvyVXocA6pW8l9pBvRzg/1059880c29b9e57e4505b654c9a40013/PT_Editar_Checkout.png)
 
 ## Configurar código
 
@@ -87,7 +87,7 @@ A seguir, vamos aprofundar o passo a passo da configuração das oções de menu
 2. Clique no ícone <i class="fas fa-cog" alt="engrenagem azul"></i> do site desejado.
 3. No menu de opções azul localizado na parte superior da página, clique em __Código__. Será exibido, à direita, um menu de __Arquivos__ e __Templates__ com todos os templates de seu site, configurados pelo sistema.
 
-![PT Lista Código Templates](//images.ctfassets.net/alneenqid6w5/57N9pQSWVF2e09URYV2avm/7cda1ca4cfe42d9c4fd503741121607d/PT_Lista_C__digo_Templates.PNG)
+![PT Lista Código Templates](https://images.ctfassets.net/alneenqid6w5/57N9pQSWVF2e09URYV2avm/7cda1ca4cfe42d9c4fd503741121607d/PT_Lista_C__digo_Templates.PNG)
 
 ### Configurar templates do menu "Código"
 
@@ -107,27 +107,27 @@ Abaixo temos exemplos de como os códigos presentes nos templates do __checkout-
 
 - Template __checkout-header__ e cabeçalho da página do site:
 
-![checkout-header-codigo-pt](//images.ctfassets.net/alneenqid6w5/4VRv3IKpL8ZOSpANmu0gTG/072b530037076e75f17ebd809de557e3/PT_C__digo_Checkout_Header_Preenchido.png)
+![checkout-header-codigo-pt](https://images.ctfassets.net/alneenqid6w5/4VRv3IKpL8ZOSpANmu0gTG/072b530037076e75f17ebd809de557e3/PT_C__digo_Checkout_Header_Preenchido.png)
 
-![checkout-header-page-pt](//images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/791259e534c7a081a5791b1e0c508df5/smartcheckout11.pt.png)
+![checkout-header-page-pt](https://images.ctfassets.net/alneenqid6w5/4jO17CaVCHEn2mFRUu4smR/791259e534c7a081a5791b1e0c508df5/smartcheckout11.pt.png)
 
 - Template __checkout-footer__ e rodapé da página do site:
 
-![checkout-footer-codigo-pt](//images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
+![checkout-footer-codigo-pt](https://images.ctfassets.net/alneenqid6w5/h9oan75Htfkd7JCIReZQx/65cb5c227d520f6a6ff3e4e732a920c5/PT_C__digo_Checkout_Footer_preenchido.png)
 
-![checkout-footer-page-pt](//images.ctfassets.net/alneenqid6w5/7yiOKZsTi9n48HhTIj5pId/7784d3a57075f60888ba66acb5710ea9/checkout_footer.pt.png)
+![checkout-footer-page-pt](https://images.ctfassets.net/alneenqid6w5/7yiOKZsTi9n48HhTIj5pId/7784d3a57075f60888ba66acb5710ea9/checkout_footer.pt.png)
 
 - Template __vtex-checkout__ e página do carrinho no Checkout:
 
-![smartcheckout16.pt](//images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
+![smartcheckout16.pt](https://images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) 
 
-![vtex-checkout-page-pt](//images.ctfassets.net/alneenqid6w5/3X1KG01hUMDyVxvEAXDoeP/57e0e59e1dfd762cb8cea27de5b55c31/smartcheckout17.pt.png)
+![vtex-checkout-page-pt](https://images.ctfassets.net/alneenqid6w5/3X1KG01hUMDyVxvEAXDoeP/57e0e59e1dfd762cb8cea27de5b55c31/smartcheckout17.pt.png)
 
 - Template __vtex-orderPlaced__ e página do pedido confirmado:
 
-![smartcheckout18.pt](//images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) 
+![smartcheckout18.pt](https://images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) 
 
-![vtex-orderplaced-page-pt](//images.ctfassets.net/alneenqid6w5/6bJ25wGbKqO1KkFsJ5qtSF/291283a570adbe29b64c6076e2a197ec/smartcheckout19.pt.png)
+![vtex-orderplaced-page-pt](https://images.ctfassets.net/alneenqid6w5/6bJ25wGbKqO1KkFsJ5qtSF/291283a570adbe29b64c6076e2a197ec/smartcheckout19.pt.png)
 
 ### Contas com multidomínio
 
@@ -135,4 +135,4 @@ As contas que possuem multidomínio podem usar apenas um site, caso não haja ne
 
 Classe inserida na tag "body" de acordo com o domínio acessado:
 
-![](//images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
+![](https://images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
diff --git a/docs/tutorials/pt/configure-template-in-the-smartcheckout.md b/docs/tutorials/pt/configure-template-in-the-smartcheckout.md
index e2858f3b0..44761fe79 100644
--- a/docs/tutorials/pt/configure-template-in-the-smartcheckout.md
+++ b/docs/tutorials/pt/configure-template-in-the-smartcheckout.md
@@ -34,9 +34,9 @@ Agora, preencha os campos abaixo seguindo as instruções:
 
 Veja a imagem abaixo:
 
-![Novo Site](//images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
+![Novo Site](https://images.ctfassets.net/alneenqid6w5/3PE7SFAdM4qIpXtPrxC7oV/9404083232d8cae1101fd1e4e4a18b98/Novo_Site.png)
 
-![smartcheckout2.pt](//images.ctfassets.net/alneenqid6w5/6klkJKS7Jegp0YvISd4UFz/c84e643fa16420603a40a09f1942356f/smartcheckout2.pt.png)
+![smartcheckout2.pt](https://images.ctfassets.net/alneenqid6w5/6klkJKS7Jegp0YvISd4UFz/c84e643fa16420603a40a09f1942356f/smartcheckout2.pt.png)
 
 Clique em __Salvar__ para concluir o cadastro do novo site.
 
@@ -51,17 +51,17 @@ Com isto, o sistema exibe todas as informações de configuração e permite nav
 - Código: Templates relacionados ao site.
 - Páginas: Exibe as páginas existentes para o site. Por padrão, são criadas duas páginas: **checkout **e **checkout/orderPlaced**. Como já dito, no inicio desse post, a página **checkout**corresponde às páginas de carrinho, dados pessoais, endereço e forma de pagamento. A página **checkout/orderPlaced** corresponde à página de Confirmação de Compra.
 
-![smartcheckout3.pt](//images.ctfassets.net/alneenqid6w5/6j24QAEDzt7QdGc5wC5ENH/c0d27ea44a8cb300ed4c87755f6a940f/smartcheckout3.pt.png)
+![smartcheckout3.pt](https://images.ctfassets.net/alneenqid6w5/6j24QAEDzt7QdGc5wC5ENH/c0d27ea44a8cb300ed4c87755f6a940f/smartcheckout3.pt.png)
 
 Em **Páginas** é possível **Criar** novas páginas, **Editar** e **Excluir** páginas existentes. Veja as duas imagens seguintes demonstrando **Edição** e **Exclusão**. A criação segue mesmas regras de edição.
 
 Edição de Página:
 
-![smartcheckout4.pt](//images.ctfassets.net/alneenqid6w5/5CeBH7XHH2YZ73KORrJ5JA/0469b81979a8b9d1194294c6c6a0963d/smartcheckout4.pt.png)
+![smartcheckout4.pt](https://images.ctfassets.net/alneenqid6w5/5CeBH7XHH2YZ73KORrJ5JA/0469b81979a8b9d1194294c6c6a0963d/smartcheckout4.pt.png)
 
 Exclusão de Página:
 
-![smartcheckout5.pt](//images.ctfassets.net/alneenqid6w5/4Nk7FXMSfMGtez5YzSFi42/d0199266c1344098581d330982770b14/smartcheckout5.pt.png)
+![smartcheckout5.pt](https://images.ctfassets.net/alneenqid6w5/4Nk7FXMSfMGtez5YzSFi42/d0199266c1344098581d330982770b14/smartcheckout5.pt.png)
 
 Em **Configurações** podemos editar os campos abaixo:
 
@@ -72,44 +72,44 @@ Em **Configurações** podemos editar os campos abaixo:
 
 Segue imagem exemplificando preenchimento desse formulário:
 
-![smartcheckout6.pt](//images.ctfassets.net/alneenqid6w5/42MYGPJflf6kIhOvY05Mky/1e3354e60bc02de5ad0988e9a59d0928/smartcheckout6.pt.png)
+![smartcheckout6.pt](https://images.ctfassets.net/alneenqid6w5/42MYGPJflf6kIhOvY05Mky/1e3354e60bc02de5ad0988e9a59d0928/smartcheckout6.pt.png)
 
 Em **Código**, serão exibidos, a direita, todos os templates relacionados ao Site. Por padrão, o sistema configura os templates exemplificados na imagem abaixo:
 
-![smartcheckout7.pt](//images.ctfassets.net/alneenqid6w5/6bJ9cMwGj9dEoXFrm8M1hP/45f5c580f98366f6ed8eeb1ad6186a54/smartcheckout7.pt.png)
+![smartcheckout7.pt](https://images.ctfassets.net/alneenqid6w5/6bJ9cMwGj9dEoXFrm8M1hP/45f5c580f98366f6ed8eeb1ad6186a54/smartcheckout7.pt.png)
 
 Desses templates, os únicos que não podem ser alterados são **vtex-checkout **e **vtex-orderPlaced**. Esses templates correspondem ao funcionamento nativo da plataforma, ou seja, são eles que renderizam o conteúdo principal dessas páginas, tanto o checkout quanto o orderPlaced.
 
 Na imagem seguinte, demonstramos a área afetada, no checkout, pela configuração do template **checkout-footer**. Esse é apenas um exemplo de template vazio.
 
-![smartcheckout8.pt](//images.ctfassets.net/alneenqid6w5/5zOhjcWGREbNGMMQcByTQe/a10257507cc13def1c061de57f71abcc/smartcheckout8.pt.png) ![smartcheckout9.pt](//images.ctfassets.net/alneenqid6w5/1cz4RwceNJi7fTgxTaYVkH/3ec8f3b5362a74b0ab25a3baf1fb0cd1/smartcheckout9.pt.png)
+![smartcheckout8.pt](https://images.ctfassets.net/alneenqid6w5/5zOhjcWGREbNGMMQcByTQe/a10257507cc13def1c061de57f71abcc/smartcheckout8.pt.png) ![smartcheckout9.pt](https://images.ctfassets.net/alneenqid6w5/1cz4RwceNJi7fTgxTaYVkH/3ec8f3b5362a74b0ab25a3baf1fb0cd1/smartcheckout9.pt.png)
 
 Na próxima imagem, temos um exemplo equivalente ao anterior, porém, dessa vez, com código HTML preenchido. Note que o código preenchido na esquerda corresponde a área superior da direita. Esse é o template **checkout-header**.
 
-![smartcheckout10.pt](//images.ctfassets.net/alneenqid6w5/3Y0fVHj9U5zvSJAAtRQ3Nd/159735c9a5a79fa274bc0a3c63377f24/smartcheckout10.pt.png) ![smartcheckout11.pt](//images.ctfassets.net/alneenqid6w5/16Ivg9yAPkvSRDzQ2JLG9h/bd1bb45eb3524f8312a82edc2da71656/smartcheckout11.pt.png)
+![smartcheckout10.pt](https://images.ctfassets.net/alneenqid6w5/3Y0fVHj9U5zvSJAAtRQ3Nd/159735c9a5a79fa274bc0a3c63377f24/smartcheckout10.pt.png) ![smartcheckout11.pt](https://images.ctfassets.net/alneenqid6w5/16Ivg9yAPkvSRDzQ2JLG9h/bd1bb45eb3524f8312a82edc2da71656/smartcheckout11.pt.png)
 
 Como podemos ver na próxima imagem, todos os templates que possuem o prefixo **checkout**serão utilizados em todas as páginas do Checkout. Nesse exemplo, já estamos na página Forma de Pagamento e note que o header carregado é o mesmo do exemplo anterior.
 
-![smartcheckout12.pt](//images.ctfassets.net/alneenqid6w5/5To5Y80RxE0NNan0zocQiV/16e89c5e0b13175285dcfa59025bc061/smartcheckout12.pt.png) ![smartcheckout13.pt](//images.ctfassets.net/alneenqid6w5/3FWj22GAEYMHzssrZxcgze/8c823c3f6df9f0cc15ee050028a1247e/smartcheckout13.pt.png)
+![smartcheckout12.pt](https://images.ctfassets.net/alneenqid6w5/5To5Y80RxE0NNan0zocQiV/16e89c5e0b13175285dcfa59025bc061/smartcheckout12.pt.png) ![smartcheckout13.pt](https://images.ctfassets.net/alneenqid6w5/3FWj22GAEYMHzssrZxcgze/8c823c3f6df9f0cc15ee050028a1247e/smartcheckout13.pt.png)
 
 Como nos templates do **checkout**, o mesmo acontece com os templates de orderPlaced. Ou seja, os templates com prefixo **orderPlaced** correspondem unicamente a página OrderPlaced (Confirmação de Compra).
 
-![smartcheckout14.pt](//images.ctfassets.net/alneenqid6w5/1BKz1PqcVmyrmmxOJe3SW7/11badcd39ab3011e994ba7ef2f73c72b/smartcheckout14.pt.png) ![smartcheckout15.pt](//images.ctfassets.net/alneenqid6w5/6eCGmlImxDRmGRpIyfvFDs/97ecf1e0821f9b33ca3a4764b456777c/smartcheckout15.pt.png)
+![smartcheckout14.pt](https://images.ctfassets.net/alneenqid6w5/1BKz1PqcVmyrmmxOJe3SW7/11badcd39ab3011e994ba7ef2f73c72b/smartcheckout14.pt.png) ![smartcheckout15.pt](https://images.ctfassets.net/alneenqid6w5/6eCGmlImxDRmGRpIyfvFDs/97ecf1e0821f9b33ca3a4764b456777c/smartcheckout15.pt.png)
 
 Como explicado acima, os únicos templates que não são permitidas alterações são **vtex-checkout** e **vtex-orderPlaced**. Esses templates renderizam ao conteúdo básico das páginas Checkout e OrderPlaced. A seguir, exemplos do conteúdo renderizado pelos templates.
 
 Template **vtex-checkout**:
 
-![smartcheckout16.pt](//images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) ![smartcheckout17.pt](//images.ctfassets.net/alneenqid6w5/qWTeYs6xpCvSSHJxRjOTq/df1d297f88bcabd7a31659bf8a615bd3/smartcheckout17.pt.png)
+![smartcheckout16.pt](https://images.ctfassets.net/alneenqid6w5/syu2Ul4PbhWNaCWbLQY84/a49ebebfaa7fd9df54cf6b2e757ffb9b/smartcheckout16.pt.png) ![smartcheckout17.pt](https://images.ctfassets.net/alneenqid6w5/qWTeYs6xpCvSSHJxRjOTq/df1d297f88bcabd7a31659bf8a615bd3/smartcheckout17.pt.png)
 
 Template **vtex-orderPlaced**:
 
-![smartcheckout18.pt](//images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) ![smartcheckout19.pt](//images.ctfassets.net/alneenqid6w5/59SQfj6KKy9kWKKFla3YyV/e7625167d5ed26fe8394e5c6b559f8c5/smartcheckout19.pt.png)
+![smartcheckout18.pt](https://images.ctfassets.net/alneenqid6w5/cPYudq4bv8TpU8dkcndvB/f31f680cf8c4f9ae3ed049c11de03bae/smartcheckout18.pt.png) ![smartcheckout19.pt](https://images.ctfassets.net/alneenqid6w5/59SQfj6KKy9kWKKFla3YyV/e7625167d5ed26fe8394e5c6b559f8c5/smartcheckout19.pt.png)
 
 As contas que possuem multi domínio podem usar apenas um site, se não houver necessidade de configurações específicas. Isso porque, ainda que exista apenas um Site, a plataforma inclui uma classe na tag &lt;body&gt; de acordo com o domínio acessado. Dessa forma, é simples aplicar layouts diferentes para o mesmo site.
 
 Classe inserida na tag &lt;body&gt; de acordo com o domínio acessado:
 
-![](//images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
+![](https://images.contentful.com/alneenqid6w5/4YAbMPcyqA8eqMM8ycokoU/836778d23afee9b0e793b27d9ab8cc0c/Portal16.jpg)
 
 **Importante**: Todo javascript que for incluído diretamente em qualquer template do Portal será ignorado pela plataforma, ou seja, no momento da renderização da página, a plataforma o removerá. Isso porque o SmartCheckout apenas aceita scripts originados no Google Tag Manager. Assim, sempre que houver necessidade de realizar alguma customização (ou mesmo inserção de tags específicas) via javascript, faça essa inclusão via Google Tag Manager.
diff --git a/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md b/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md
index c8f2fb333..bddedcb7c 100644
--- a/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md
+++ b/docs/tutorials/pt/configuring-a-discount-for-orders-prepaid-in-full.md
@@ -33,7 +33,7 @@ Depois de determinar o desconto no Checkout, é preciso atrelar o SKU ao meio de
 3. Clique no template da sua página de produto na lista de templates.
 4. Na propriedade `skuPrice`, adicione a variável `paymentSystemId` com o ID do meio de pagamento desejado.
 
-![Screenshot 2020-12-18 Criar preço à vista](//images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
+![Screenshot 2020-12-18 Criar preço à vista](https://images.ctfassets.net/alneenqid6w5/4X9sxu1jruXPgpJc5AthbD/ce74271f2f7ca41fa3f762b12a226bcb/Screenshot_2020-12-18_Criar_pre__o____vista.png)
 
 6. Após a alteração, clique em __Save Template__ no campo superior para salvar.
 
diff --git a/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md b/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
index 78338ee11..2009e5da0 100644
--- a/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
@@ -40,14 +40,14 @@ Criar uma nova política comercial é o primeiro passo para definir as condiçõ
 
 Essa configuração é feita no módulo Configurações da Loja, na aba Políticas comerciais. É necessário [criar uma nova política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) quando as configurações de catálogo, preços, promoções, logística e pagamentos forem diferentes entre os marketplaces em que os sellers vendem seus produtos. 
 
-![PT Add Politica comercial](//images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/a9be66bd901619b68280ad8ceec4d552/PT_Add_Politica_comercial.jpg)
+![PT Add Politica comercial](https://images.ctfassets.net/alneenqid6w5/7sIaT2Sf52QFfZ5qOfESLa/a9be66bd901619b68280ad8ceec4d552/PT_Add_Politica_comercial.jpg)
 
 ## Gerenciamento de Pedidos
 Após a criação de uma política comercial, é preciso associá-la a cada marketplace em que o seller vende produtos ao cadastrar [afiliados](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). É assim que sellers identificam qual política comercial está atuando em cada marketplace. Se sua loja vende produtos em três marketplaces diferentes, é necessário criar três afiliados, cada um representando um marketplace. 
 
 Essa ação é feita na aba *Configurações* do módulo *Gerenciamento de Pedidos* da sua loja ao cadastrar afiliados. Mesmo criando várias, é importante notar que somente uma política comercial atuará no marketplace por vez. 
 
-![PT Afiliado](//images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/3004320aeb44502e68cceac90c472d6c/PT_Afiliado.jpg)
+![PT Afiliado](https://images.ctfassets.net/alneenqid6w5/44WIEfxcntAXCrsoveWKv2/3004320aeb44502e68cceac90c472d6c/PT_Afiliado.jpg)
 
 *No exemplo acima o afiliado "Amazon" está vinculado à política comercial "1".* 
 
@@ -61,7 +61,7 @@ Essa configuração é feita no módulo de *Promoções* em todas as [promoçõe
 
 Se nenhuma política comercial for selecionada, a promoção estará disponível em todos os canais de venda.
 
-![PT Promoções Politica Comercial](//images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/8d011fccf8af4cf5bc088cbd77a7b914/PT_Promo____es_Politica_Comercial.jpg)
+![PT Promoções Politica Comercial](https://images.ctfassets.net/alneenqid6w5/78iUQ59I9DDJS1lI4mJjA1/8d011fccf8af4cf5bc088cbd77a7b914/PT_Promo____es_Politica_Comercial.jpg)
 
 *No exemplo acima, a promoção será aplicada somente a pedidos das políticas comerciais "Marketplace-BRL" e "Argentina-ARS", onde a loja atua como seller. A promoção não estará disponível no storefront da loja VTEX.* 
 
@@ -70,7 +70,7 @@ Sellers que transacionam o pagamento das vendas de seus produtos em um marketpla
 
 Essa configuração é feita no módulo de *Pagamentos*, ao [criar uma condição especial](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456) e ao associá-la às políticas comerciais desejadas. Se nenhuma restrição é feita, a política comercial será aplicada em todos os canais de venda. 
 
-![PT Pagamento Politica comercial](//images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/bd8e088166a9fa0f1fabc0c410f18409/PT_Pagamento_Politica_comercial.jpg)
+![PT Pagamento Politica comercial](https://images.ctfassets.net/alneenqid6w5/1B0eL9YPiRsRSgQUSgHqBJ/bd8e088166a9fa0f1fabc0c410f18409/PT_Pagamento_Politica_comercial.jpg)
 
 *No exemplo acima, a condição de pagamento está associada à política comercial "Marketplace". Isso torna a condição de pagamento disponível apenas aos canais de venda associados a essa política comercial.*
 
@@ -83,7 +83,7 @@ Essa configuração é feita no *Catálogo* da VTEX, ao [cadastrar produtos](htt
 Não é recomendado vincular políticas comerciais a coleções, para determinar o sortimento de produtos, sobretudo em casos de marketplaces externos à VTEX. Quando um produto é retirado da coleção da política comercial, o sistema VTEX não avisa o marketplace dessa atualização, fazendo com que o produto continue disponível no marketplace. 
 </div>  
 
-![Pt Catálogo Politica](//images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/63eea6b22e93fa4e94840a5c9a88db94/Pt_Cat__logo_Politica.jpg)
+![Pt Catálogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/63eea6b22e93fa4e94840a5c9a88db94/Pt_Cat__logo_Politica.jpg)
 
 *No exemplo acima, o produto estará disponível apenas para canais de venda utilizando as políticas comerciais "Carrefour" e "Marketplace".* 
 
@@ -95,7 +95,7 @@ Essa configuração é feita no módulo de *Preços* da VTEX, utilizando políti
 - [Regras de preço](https://help.vtex.com/pt/tutorial/configurar-regra-de-preco-para-politica-comercial--5LQMLwcUcEGCWK6SMI6cEM): para determinar um markup para categorias e marcas específicas
 - [Preços fixos](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy): para diferenciar preços em produtos específicos
 
-![PT Regra de preço](//images.ctfassets.net/alneenqid6w5/lBoM4E1z07YLbsZfJhP1V/6344b89e4698e8834febd6dcbc4374cc/PT_Regra_de_pre__o.jpg)
+![PT Regra de preço](https://images.ctfassets.net/alneenqid6w5/lBoM4E1z07YLbsZfJhP1V/6344b89e4698e8834febd6dcbc4374cc/PT_Regra_de_pre__o.jpg)
 
 *No exemplo acima, a regra de preço aplicou um markup à política comercial "Marketplace" para produtos dentro da categoria "Fera-Fashion*. 
 
@@ -105,10 +105,10 @@ Sellers podem configurar [rotas logísticas](https://help.vtex.com/pt/tracks/log
 
 Ambas configurações são realizadas no módulo *Estratégia de Envio*. Ao criar uma [doca](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/4Rr5XpzAzUPv2Eo9Mh7cEj), é preciso indicar quais políticas comerciais ela atenderá. Isso torna as políticas de envio associadas a essa doca disponíveis para as políticas comerciais vinculadas. Em seguida, é necessário relacionar o [estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque) desejado a uma doca, para tornar seu inventário disponível para todas as políticas comerciais associadas à doca. 
 
-![PT Doca Politica](//images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/2f40ca4bb8723eff8218e24ad2b81c8f/PT_Doca_Politica.jpg)
+![PT Doca Politica](https://images.ctfassets.net/alneenqid6w5/1peTICHA1NJwPUAvPbsoMb/2f40ca4bb8723eff8218e24ad2b81c8f/PT_Doca_Politica.jpg)
 *No exemplo acima, a doca está associada à política comercial "Marketplace", que serão atendidas pela transportadora "Transportadora A".*
 
-![PT Estoque Politica](//images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/634a9269e2b94cc8102fe4037f8b7136/PT_Estoque_Politica.jpg)
+![PT Estoque Politica](https://images.ctfassets.net/alneenqid6w5/6ZyxXxLtPVaFgkb5LY9cVi/634a9269e2b94cc8102fe4037f8b7136/PT_Estoque_Politica.jpg)
 *No exemplo acima, o estoque está associado a "Doca A", portanto esse será o estoque que as políticas comerciais vinculadas à "Doca A" utilizarão.* 
 
 ## Integrações
@@ -116,7 +116,7 @@ As políticas comerciais também são aplicadas em todas as integrações em que
 
 Essas [integrações](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402?&utm_source=autocomplete#vender-em-marketplace) são feitas na aba de *Configurações* do módulo *Integrações*. Cada canal costuma requerer condições comerciais específicas, porém, é possível que canais diferentes compartilhem da mesma política comercial. 
 
-![PT integracao politica](//images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/50d0f55f7ed3ab4c1a776224151fb6bf/PT_integracao_politica.jpg)
+![PT integracao politica](https://images.ctfassets.net/alneenqid6w5/2Zg5NRNmE30MNvB7cxXyso/50d0f55f7ed3ab4c1a776224151fb6bf/PT_integracao_politica.jpg)
 
 *No exemplo acima, a política comercial "Marketplace" está aplicada na integração com o Google Shopping.*
 
diff --git a/docs/tutorials/pt/configuring-banners.md b/docs/tutorials/pt/configuring-banners.md
index 708e9a6d2..ce9fe2a57 100644
--- a/docs/tutorials/pt/configuring-banners.md
+++ b/docs/tutorials/pt/configuring-banners.md
@@ -29,7 +29,7 @@ Depois de realizar as configurações do banner, você deve adicioná-lo a uma p
   <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
 </div>
 
-![banner-form-pt](//images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
+![banner-form-pt](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
 
 ## Campos de cadastro do banner
 
@@ -60,7 +60,7 @@ Para cadastrar o banner, é necessário preencher os seguintes campos:
 
 Clique em <i class="fa-solid fa-link"></i> `Preencher a partir de uma URL` para adicionar a URL da página de busca em as regras de ativação serão aplicadas. 
 
-![banner-url-pt](//images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
+![banner-url-pt](https://images.ctfassets.net/alneenqid6w5/2ldGnmahkPao4EbISls3gu/eb9677cd365433d38a4459c7877bb646/image.png)
 
 Clique em <i class="fas fa-plus"></i> `Adicionar condição` para criar uma regra. Elas podem ser dos seguintes tipos:
 
diff --git a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index 9701b8e30..cb07b16e9 100644
--- a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -43,7 +43,7 @@ Caso necessário, baixe um arquivo modelo clicando em VTEX file template no roda
 	<li>Após o processo de importação ser concluído, você pode clicar em  Exibir detalhes de importação para acessar o relatório de importação.</li>
 </ol>
 
-![Importação em massa - PT](//images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/5957afd8831ee93e55609e2b55b5b552/Bulk_import_vers_o_original-PT.gif)
+![Importação em massa - PT](https://images.ctfassets.net/alneenqid6w5/3sWvUytkkonIe01tnvXwpK/5957afd8831ee93e55609e2b55b5b552/Bulk_import_vers_o_original-PT.gif)
 
 # Erros de importação
 
@@ -61,7 +61,7 @@ Para obter uma visão detalhada dos problemas encontrados, siga os passos abaixo
  Certifique-se de carregar apenas o arquivo contendo as correções dos erros previamente identificados para garantir uma importação bem-sucedida.
 </div>
 
-![Bulk import - PT](//images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/4ebe7b4b5b1c0d5b2d7feb36134d9a5e/Bulk_import_vers_o_error-gif-PT.gif)
+![Bulk import - PT](https://images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/4ebe7b4b5b1c0d5b2d7feb36134d9a5e/Bulk_import_vers_o_error-gif-PT.gif)
 
 # Importação via API
 
diff --git a/docs/tutorials/pt/configuring-cargo-splitting.md b/docs/tutorials/pt/configuring-cargo-splitting.md
index 5e49fe3a7..77572b132 100644
--- a/docs/tutorials/pt/configuring-cargo-splitting.md
+++ b/docs/tutorials/pt/configuring-cargo-splitting.md
@@ -19,7 +19,7 @@ A divisão de carga é a configuração que permite que uma compra seja dividida
 
 Essa configuração é muito importante pois, caso a divisão de carga não seja permitida, pode impossibilitar o fechamento de uma compra se a soma do peso de todos os produtos do carrinho for maior que o limite máximo de peso cadastrado nas políticas de envio.
 
-![](//images.contentful.com/alneenqid6w5/g0pDcU4oy4WaoQ0e8C0Im/d349266bd8ab36c137894b4b8cb0374d/divisaoCarga.png)
+![](https://images.contentful.com/alneenqid6w5/g0pDcU4oy4WaoQ0e8C0Im/d349266bd8ab36c137894b4b8cb0374d/divisaoCarga.png)
 
 ### Como configurar
 
diff --git a/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md
index d8c42d97d..16db2b525 100644
--- a/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md
@@ -78,7 +78,7 @@ Para configurar a __ClearSale Global__, será necessário:
 <br>  
   <ui>11. No canto superior direito, clique em <b>Publicar</b>.</ui> 
 
-![Fingerprint ClearSalve_Tela](//images.contentful.com/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/314960d342aad03b56da4affe46439f8/Fingerprint_ClearSalve_Tela.png)
+![Fingerprint ClearSalve_Tela](https://images.contentful.com/alneenqid6w5/1cCBNxfRXCGQr4QxBsPgg6/314960d342aad03b56da4affe46439f8/Fingerprint_ClearSalve_Tela.png)
 
 Para mais detalhes sobre o código inserido no Google Tag Manager, recomendamos a leitura [desta documentação](https://api.clearsale.com.br/docs/behavior-analytics), da ClearSale. 
 
diff --git a/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md b/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
index e695ff3c5..8348fe82a 100644
--- a/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
@@ -73,7 +73,7 @@ A configuração do antifraude ClearSale v3 exige a criação de uma tag no Goog
 10. Clique no botão __Criar Tag__, insira um nome para esta tag e salve.
 11. No canto superior direito, clique em __Publicar__.
 
-![Pasted image at 2017 10 20 01 11 PM](//images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
+![Pasted image at 2017 10 20 01 11 PM](https://images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
 
 ## Detalhes do campo customSLA
 
diff --git a/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md b/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md
index 8bc8a3e8e..a51b1413f 100644
--- a/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md
+++ b/docs/tutorials/pt/configuring-functions-in-the-message-center-templates.md
@@ -35,7 +35,7 @@ _classe.atributo_ são obtidos do JSON. No MessageCenter exibimos o JSON espec
 **HTML do template**
 `<strong>{{_accountInfo.HostName}}</strong> => lojavirtual`
 
-![exemplohtml](//images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
+![exemplohtml](https://images.ctfassets.net/alneenqid6w5/2L8EnLX9I4gqOyaKUY4wGw/47d7e0db874a73e9569d6ddabe69b470/exemplohtml.png)
 
 Para o exemplo acima, uma loja seller pode possuir um hostname diferente de uma loja marketplace. Sempre leve em conta as suas configurações!
 
@@ -131,4 +131,4 @@ em até{{#hasSubStr shippingEstimate 'bd'}}
 ```
 
 **Resultado:**
-![](//images.contentful.com/alneenqid6w5/5cRmcM2692G60Ok6gSAWmo/f7196556f5360f632dbccf47f837b5b9/3.1.jpg)
+![](https://images.contentful.com/alneenqid6w5/5cRmcM2692G60Ok6gSAWmo/f7196556f5360f632dbccf47f837b5b9/3.1.jpg)
diff --git a/docs/tutorials/pt/configuring-greenlist.md b/docs/tutorials/pt/configuring-greenlist.md
index 6fd26ed5f..41558a383 100644
--- a/docs/tutorials/pt/configuring-greenlist.md
+++ b/docs/tutorials/pt/configuring-greenlist.md
@@ -45,7 +45,7 @@ Quanto mais dados de assinatura você exigir, mais rígidas serão suas regras,
 
 Para marcar um cliente como confiável, o lojista usa alguns critérios. Estes critérios são os __dados de compra que compõem a assinatura de um pedido__:
 
-![Greenlist - assinatura](//images.contentful.com/alneenqid6w5/3CvVVFRIJ22wS6o8sq6ok6/45cdf4a8259437d36aa74a40a8a04715/Greenlist_-_assinatura.png)
+![Greenlist - assinatura](https://images.contentful.com/alneenqid6w5/3CvVVFRIJ22wS6o8sq6ok6/45cdf4a8259437d36aa74a40a8a04715/Greenlist_-_assinatura.png)
 
 Digamos que você marque três das opções da tela acima: __E-mail__, __Endereço de entrega__ e __Cartão de crédito__. Isso significa que, para que novos pedidos desse cliente não passem pelo antifraude, ele precisa usar em novas compras os mesmos dados de e-mail, endereço e cartão de crédito. 
 
@@ -57,7 +57,7 @@ A recorrência da assinatura define o número de pedidos que um cliente deve faz
 
 Este número deve ser definido pelo próprio lojista, e pode variar de __1 a 10__.
 
-![Greenlist - recorrencia](//images.contentful.com/alneenqid6w5/2TFJUnw1Cw8I0KcqCcAsmS/6aaec62228ec8ff5a38093e743a4229b/Greenlist_-_recorrencia.png)
+![Greenlist - recorrencia](https://images.contentful.com/alneenqid6w5/2TFJUnw1Cw8I0KcqCcAsmS/6aaec62228ec8ff5a38093e743a4229b/Greenlist_-_recorrencia.png)
 
 Se você definir a recorrência para 6, por exemplo, todos os clientes da sua loja que fizerem seis compras usando os mesmos dados definidos na assinatura deixam de passar pelo antifraude a partir da próxima compra.
 
@@ -65,7 +65,7 @@ Se você definir a recorrência para 6, por exemplo, todos os clientes da sua lo
 
 Você pode configurar um valor máximo para que a Greenlist seja válida. Isto porque mesmo que um cliente já tenha sido marcado como confiável, você pode preferir que - para valores muito altos, em que o risco de perda é maior - o antifraude atue independentemente do histórico de compras desse cliente.
 
-![Greenlist - valor maximo](//images.contentful.com/alneenqid6w5/1CG6Wm74qIu4Qam2WekkE4/02f3e165b7970651406d667ae66e4589/Greenlist_-_valor_maximo.png)
+![Greenlist - valor maximo](https://images.contentful.com/alneenqid6w5/1CG6Wm74qIu4Qam2WekkE4/02f3e165b7970651406d667ae66e4589/Greenlist_-_valor_maximo.png)
 
 ### Prazo de segurança para Chargeback
 
@@ -73,7 +73,7 @@ Você pode configurar um valor máximo para que a Greenlist seja válida. Isto p
 
 Neste caso, é interessante definir uma margem de segurança para a análise do Greenlist. Ao escolher, por exemplo, um prazo de segurança de 30 dias, o lojista está dizendo que todo pedido aprovado pelo antifraude será avaliado pela Greenlist apenas depois de 30 dias.
 
-![Greenlist - chargeback](//images.contentful.com/alneenqid6w5/314Ig5HLCU2uy0kyYEu4gC/105ed241ac49923035a7b4d441d698e0/Greenlist_-_chargeback.png)
+![Greenlist - chargeback](https://images.contentful.com/alneenqid6w5/314Ig5HLCU2uy0kyYEu4gC/105ed241ac49923035a7b4d441d698e0/Greenlist_-_chargeback.png)
 
 ### Ativando a Greenlist
 
@@ -92,6 +92,6 @@ Se você identificar o pedido de um cliente integrante da Greenlist (ou qualquer
 2. Na lista de transações, clique na transação que você deseja marcar como fruade;
 3. Clique no botão __Marcar o pagamento como fraude__.
 
-![Marcar como fraude](//images.contentful.com/alneenqid6w5/3EiAcGulosCgQq4qCIGqQE/d0be6c70e7129f63b189c56bdb79012b/fraud.png)
+![Marcar como fraude](https://images.contentful.com/alneenqid6w5/3EiAcGulosCgQq4qCIGqQE/d0be6c70e7129f63b189c56bdb79012b/fraud.png)
 
 Uma vez que uma transação é marcada como fraude, o cliente que fez o pedido é retirado da Greenlist. 
diff --git a/docs/tutorials/pt/configuring-login-with-facebook-and-google.md b/docs/tutorials/pt/configuring-login-with-facebook-and-google.md
index 2d137ccbf..04f50bdae 100644
--- a/docs/tutorials/pt/configuring-login-with-facebook-and-google.md
+++ b/docs/tutorials/pt/configuring-login-with-facebook-and-google.md
@@ -38,12 +38,12 @@ Após a configuração no Facebook ou Google, é preciso configurar no Admin VTE
 2. Clique em **Configurações da conta > Autenticação**.
 
     Você será direcionado(a) para a aba **Loja virtual** da página **Autenticação**, que lista os métodos de login disponíveis na sua loja.
-    ![Lista Autenticação](//images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/5656de06dc15a094bea726c3d7f6e370/autenticacao-pt.png)
+    ![Lista Autenticação](https://images.ctfassets.net/alneenqid6w5/3Bnb1ifcL7krcXEnAHzxu1/5656de06dc15a094bea726c3d7f6e370/autenticacao-pt.png)
 3. Na linha do provedor de login desejado, clique em `Configurar`.
 4. Preencha o formulário com o `Client ID` e o `Segredo do cliente` cadastrado e clique em `Salvar`.
-    ![Facebook OAuth PT](//images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/1dcbc9286c0245740194026e19ba5c9b/1-login-fb-pt.png)
+    ![Facebook OAuth PT](https://images.ctfassets.net/alneenqid6w5/2mWEocn4zdG0BJVMaujzk8/1dcbc9286c0245740194026e19ba5c9b/1-login-fb-pt.png)
 5. Na página **Autenticação**, ative o uso do provedor clicando no interruptor.  
-    ![Lista Autenticação Switch On Highlight](//images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/c079f95b7833c2bdba7e5a86860f03cd/switch_On_highlight_PT.png)
+    ![Lista Autenticação Switch On Highlight](https://images.ctfassets.net/alneenqid6w5/4devCJpXnMWF3TV6xMDiUT/c079f95b7833c2bdba7e5a86860f03cd/switch_On_highlight_PT.png)
 
 ## Validar a configuração
 
diff --git a/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
index cdc4d53df..000367c5a 100644
--- a/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -58,7 +58,7 @@ Para configurar essa liquidação, siga o passo a passo:
 8. No campo __Captura antecipada__, selecione uma das opções de tempo disponíveis. 
 9. Preencha o campo __Alterar tempo máximo para captura__ com o período definido com a adquirente. __Caso você prefira deixar o campo em branco, o padrão de 4 dias será utilizado__.
 
-![captura_automatica_PT](//images.ctfassets.net/alneenqid6w5/50rTz4DncUN9gOUZ9JWmMk/c5eb2f4759254eb1b8425bcee7267503/captura_automatica_atualizado_PT.png)
+![captura_automatica_PT](https://images.ctfassets.net/alneenqid6w5/50rTz4DncUN9gOUZ9JWmMk/c5eb2f4759254eb1b8425bcee7267503/captura_automatica_atualizado_PT.png)
 10. Clique no __botão Salvar__. 
 
 Desse modo, o novo recurso de liquidação será implementado.
diff --git a/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md
index 9c9322e0f..b4d3e0cf8 100644
--- a/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md
@@ -63,13 +63,13 @@ Para garantir o funcionamento deste recurso, é preciso analisar os detalhes de
 4. Na página seguinte, clique em __+Informações__.
 5. Ao clicar em __+Informações__, busque pelo campo __deviceFingerprint__ e confira se o código disponível inicia com a palavra __armor__, conforme exemplo abaixo. 
 
-![Device Fingerprint Armor](//images.contentful.com/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/a16e2a10a8bbe0d6ae256267baeb92cc/DEVICEFINGERPRINTARMOR.png)
+![Device Fingerprint Armor](https://images.contentful.com/alneenqid6w5/2py5aLnSL2AZD9U29Bj9Nw/a16e2a10a8bbe0d6ae256267baeb92cc/DEVICEFINGERPRINTARMOR.png)
 
 <ui>
 6. Ao confirmar que as informações estão corretas, a etapa final para verificação do Device Fingerprint é o envio do ID da transação para a equipe do Mercado Pago. Esse ID pode ser encontrado no campo, <b>authorizationConnectorResponse</b>, no detalhe da transação.
 </ui>
 
-![Autorização](//images.contentful.com/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/e103a0d75ecc17f79510e0f9b32c1b49/AUTHORIZATION.png)
+![Autorização](https://images.contentful.com/alneenqid6w5/5FTRfpgGc7HJZUNaZicEb4/e103a0d75ecc17f79510e0f9b32c1b49/AUTHORIZATION.png)
 
 <ui>
 7. Copie o ID e <a href="https://www.mercadopago.com.br/developers/pt/support">encaminhe um e-mail</a> para o Mercado Pago com esta informação e solicite a validação da transação. Dessa forma, a equipe do Mercado Pago poderá avaliar se o Device Fingerprint está operando corretamente.
diff --git a/docs/tutorials/pt/configuring-my-account-conversational-commerce.md b/docs/tutorials/pt/configuring-my-account-conversational-commerce.md
index 3fe4c5166..10f168e2b 100644
--- a/docs/tutorials/pt/configuring-my-account-conversational-commerce.md
+++ b/docs/tutorials/pt/configuring-my-account-conversational-commerce.md
@@ -24,7 +24,7 @@ O [Conversational Commerce VTEX](https://help.vtex.com/pt/tracks/conversational-
 
 ## Campos das configurações de conversação
 
-![my account - conversational commerce - PT](//images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/5e3c881eb854b74a4b36625ee3de43a7/image.png)
+![my account - conversational commerce - PT](https://images.ctfassets.net/alneenqid6w5/6HpER9MIEWSWz1ULYD22h8/5e3c881eb854b74a4b36625ee3de43a7/image.png)
 
 * **Idioma:** idioma que será o padrão para mensagens do bot com o cliente no Conversational Commerce VTEX. Campo obrigatório.
 * **Mensagem de boas-vindas:** primeira mensagem que o Conversational Commerce VTEX enviará em sua interação inicial com o cliente. Essa mensagem é seguida de mensagens explicativas do processo de compra e suporte humano da sua equipe de atendimento. Campo obrigatório. A sugestão de padrão é: 
diff --git a/docs/tutorials/pt/configuring-payment-gateways.md b/docs/tutorials/pt/configuring-payment-gateways.md
index 18f2e1516..5c337edf3 100644
--- a/docs/tutorials/pt/configuring-payment-gateways.md
+++ b/docs/tutorials/pt/configuring-payment-gateways.md
@@ -17,5 +17,5 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Os meios de pagamento são essenciais para a virada da loja em produção. Para isso, acesse o [PCI Gateway](/tutorial/afiliacoes-de-gateway/ "PCI Gateway"), que é o módulo certificado pelo PCI DSS, garantindo a segurança dos dados de pagamento dos seus clientes.
 
-<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3011-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4?_=1" />[//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4](//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4 "//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4")</video>
+<!--[if lt IE 9]><script>document.createElement('video');</script><![endif]--><video class="wp-video-shortcode" id="video-3011-1" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4?_=1" />[//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4](https://downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4 "//downloads.contentful.com/alneenqid6w5/5pK30xQ8TKsmQi6WmmweaQ/8b8f70d26e2f79cc403283394df1fe01/Pagamento.mp4")</video>
 
diff --git a/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index 8447e03c2..307335d49 100644
--- a/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -51,7 +51,7 @@ Para habilitar o acesso da VTEX no ambiente Adyen, siga as instruções abaixo:
 2. Na barra lateral esquerda, copie e salve a informação descrita acima de **Company**. Esta é a sua Company Account.
 3. Na lista abaixo, busque o nome da Merchant Account a ser utilizada (ressaltada em branco). Copie e salve esta informação.
 
-![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtenha a POS Live URL
 
@@ -70,7 +70,7 @@ As informações abaixo consideram que a API Key já foi previamente gerada no a
 2. Selecione a sua credencial API.
 3. Em **Server Settings > Authentication**, selecione **API key**. 
 
-![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Clique em <b>Generate Key</b> e anote a informação criada em um local seguro.</ui>
 
@@ -86,7 +86,7 @@ Configure o webhook conforme os passos abaixo:
 4. Em **General > Description**, adicione uma descrição para o novo webhook. Exemplo: "Webhook Adyen Connector Provider v3".
 5. Em **General > Server configuration > URL**, preencha a URL da sua conta VTEX. Exemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Clique em <b>Apply</b>.</ui>
 
@@ -94,11 +94,11 @@ Configure o webhook conforme os passos abaixo:
 
 <blockquote><ui>8. Clique em <b>Save changes</b>.</ui>
 
-![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
diff --git a/docs/tutorials/pt/configuring-payment-with-adyenv3.md b/docs/tutorials/pt/configuring-payment-with-adyenv3.md
index c77087cbf..7a36365a6 100644
--- a/docs/tutorials/pt/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/pt/configuring-payment-with-adyenv3.md
@@ -42,7 +42,7 @@ Para habilitar o acesso da VTEX no ambiente Adyen, siga as instruções abaixo:
 2. Na barra lateral esquerda, copie e salve a informação descrita acima de __Company__. Esta é a sua Company Account.
 3. Na lista abaixo, busque o nome da Merchant Account a ser utilizada (ressaltada em branco). Copie e salve esta informação.
 
-![Adyenv3_1](//images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
+![Adyenv3_1](https://images.ctfassets.net/alneenqid6w5/4BHwn5SIUl6AuiiEjreluk/a7404c85f6fda7f7ccbae66070d0db0d/Adyenv3_1.PNG)
 
 ### Obtenha a Live URL
 
@@ -59,7 +59,7 @@ As informações abaixo consideram que a API Key e Client Key já foram previame
 2. Selecione a sua credencial API.
 3. Em __Server Settings > Authentication__, selecione __API key__. 
 
-![Adyenv3_2](//images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
+![Adyenv3_2](https://images.ctfassets.net/alneenqid6w5/5y5TAeZmhsKrn2nZTJexIw/bfbe2587739f39fa70c4e1f08e86bd71/Adyenv3_2.PNG)
 
 <blockquote><ui>4. Clique em <b>Generate Key</b> e anote a informação criada em um local seguro.</ui>
 
@@ -67,7 +67,7 @@ As informações abaixo consideram que a API Key e Client Key já foram previame
 
 <blockquote><ui>6. Clique em <b>Generate Client Key</b> e anote a informação criada em um local seguro.
 
-![Adyenv3_3](//images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
+![Adyenv3_3](https://images.ctfassets.net/alneenqid6w5/1HlZV1tWNXS4ME0B7LYsHR/ca6b2a69d637574b2885286ccaed30b4/Adyenv3_3.PNG)
 
 ### Configure o webhook
 
@@ -81,7 +81,7 @@ Configure o webhook conforme os passos abaixo:
 4. Em __General > Description__, adicione uma descrição para o novo webhook. Exemplo: "Webhook Adyen Connector Provider v3".
 5. Em __General > Server configuration > URL__, preencha a URL da sua conta VTEX. Exemplo: https://{{account}}.myvtex.com/_v3/api/webhook/notification.
 
-![Adyenv3_4](//images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
+![Adyenv3_4](https://images.ctfassets.net/alneenqid6w5/1gAXlQfBoEUm5qnfSsHJkl/c18036816afbfe9ed8434d1211679879/Adyenv3_4.PNG)
 
 <blockquote><ui>6. Clique em <b>Apply</b>.</ui>
 
@@ -89,11 +89,11 @@ Configure o webhook conforme os passos abaixo:
 
 <blockquote><ui>8. Clique em <b>Save changes</b>.</ui>
 
-![Adyenv3_5](//images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
+![Adyenv3_5](https://images.ctfassets.net/alneenqid6w5/4dNUcUg9OKni8eT1wXcjO1/19eddc41d854adb8976e6e90ed54589c/Adyenv3_5.PNG)
 
-![Adyenv3_6](//images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
+![Adyenv3_6](https://images.ctfassets.net/alneenqid6w5/2ocxDKULle6hnu2fFPnjfZ/7787ff93f023d3ec17c669758aefb82f/Adyenv3_6.PNG)
 
-![Adyenv3_7](//images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
+![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
 <div class="alert alert-info">
 Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
diff --git a/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md b/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md
index 24a548ccd..3654da069 100644
--- a/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md
+++ b/docs/tutorials/pt/configuring-physical-stores-integration-with-b2w.md
@@ -23,7 +23,7 @@ Existem duas modalidades de retirada em loja: **Pickup** e **Ship Store**. Nessa
 
 Os pedidos realizados e que utilizam a opção de retirada em loja, quando chegam à VTEX, são atribuídos à conta franquia que possui o ponto de retirada escolhido pelo cliente e o ponto de retirada terá seu estoque modificado.
 
-![fluxocriacaopup](//images.ctfassets.net/alneenqid6w5/1ifP8Kk4uQQu3jW2vuZpPK/32e76d55a97a98461889c3a2d7ee26ec/fluxocriacaopup.JPG)
+![fluxocriacaopup](https://images.ctfassets.net/alneenqid6w5/1ifP8Kk4uQQu3jW2vuZpPK/32e76d55a97a98461889c3a2d7ee26ec/fluxocriacaopup.JPG)
 
 Para criar os pontos de retirada, você vai precisar:
 
@@ -67,13 +67,13 @@ Para verificar se o ponto de retirada foi enviado a B2W:
 
 Na listagem dos pontos de retirada enviados, você conseguirá visualizar quais foram enviados com sucesso e quais possuem erro de configuração.
 
-![Início (4)](//images.ctfassets.net/alneenqid6w5/NHUOSgg4hXhVapftBxIGJ/a6c17c27284c4220fcefc07ef47def2a/In__cio__4_.gif)
+![Início (4)](https://images.ctfassets.net/alneenqid6w5/NHUOSgg4hXhVapftBxIGJ/a6c17c27284c4220fcefc07ef47def2a/In__cio__4_.gif)
 
 ## Confirmação da associação do ponto de retirada x anúncio 
 
 É possível confirmar se o ponto de retirada foi corretamente associado ao anúncio da B2W. O que define essa associação é a quantidade de estoque do produto, enviada para o ponto de retirada.
 
-![fluxoestoquepup](//images.ctfassets.net/alneenqid6w5/120QcMpvS0nLSqPPor23ex/2d98326ca3f1d91bbf99fe97bb7f84c7/fluxoestoquepup.JPG)
+![fluxoestoquepup](https://images.ctfassets.net/alneenqid6w5/120QcMpvS0nLSqPPor23ex/2d98326ca3f1d91bbf99fe97bb7f84c7/fluxoestoquepup.JPG)
 
 Para confirmar a associação, você deve verificar quais pontos de retirada estão sincronizados com o SKU e seus respectivos estoques. Siga os passos abaixo:
 
@@ -82,6 +82,6 @@ Para confirmar a associação, você deve verificar quais pontos de retirada est
 4. Filtre a listagem com a opção SkyHub/B2W.
 5. Localize o SKU desejado na caixa de pesquisa.
 
-![Início (5)](//images.ctfassets.net/alneenqid6w5/7zVX7T1t17RWcNtJVsNXcd/768de551c0b4a955735fbbafcbf58a13/In__cio__5_.gif)
+![Início (5)](https://images.ctfassets.net/alneenqid6w5/7zVX7T1t17RWcNtJVsNXcd/768de551c0b4a955735fbbafcbf58a13/In__cio__5_.gif)
 
 Os pontos de retirada estão sincronizados com o SKU e seus respectivos estoques serão apresentados na lista.
diff --git a/docs/tutorials/pt/configuring-price-divergence-rule.md b/docs/tutorials/pt/configuring-price-divergence-rule.md
index 1b409da31..48dda8607 100644
--- a/docs/tutorials/pt/configuring-price-divergence-rule.md
+++ b/docs/tutorials/pt/configuring-price-divergence-rule.md
@@ -45,13 +45,13 @@ Para criar uma regra de Divergência de valores, siga os passos abaixo:
 
 Você verá a seguinte tela:
 
-![print_01_PT](//images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/97a35d8b97cc9bd3a9ccd7c9db67b87a/print_01_PT.png)
+![print_01_PT](https://images.ctfassets.net/alneenqid6w5/6lp2IKdU8VvaFgOUhHv5GA/97a35d8b97cc9bd3a9ccd7c9db67b87a/print_01_PT.png)
 
 A aba **Todas** apresenta todas as regras de autorização configuradas.
 
 Para criar a 1ª regra de autorização, clique em **CRIAR REGRAS**. A partir disso, será possível identificar uma nova aba, chamada **1ª regra**. Clique sobre ela e opções de configuração vão aparecer.
 
-![print_02_PT](//images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/a8a96047fce4c061362d5a22ada0d2c0/print_02_PT.png)
+![print_02_PT](https://images.ctfassets.net/alneenqid6w5/Q8TwzIWNwQPg13tcaALd6/a8a96047fce4c061362d5a22ada0d2c0/print_02_PT.png)
 
 Para configurar a **1ª regra**, você pode aumentar ou diminuir o percentual de divergência, arrastando as extremidades da barra, sendo o sinal > para definir o início do intervalo, e < para determinar até onde ele vai. O intervalo percentual escolhido pode variar de 0% a 100%.
 
@@ -67,7 +67,7 @@ Para configurar uma hierarquia de usuários responsáveis por aprovações de pe
 
 Para criar a **2ª regra**, clique no `<img class="shadow-4" src="https:////images.ctfassets.net/alneenqid6w5/7E2BhdEapQ5Lmm4fLRKxpp/2770eaaa5af9653a71416c2f9677eb37/__cone_regras.JPG" />` sinal de adição. Esse mesmo procedimento vale para criar uma terceira ou quarta regra, e assim por diante. Após clicar no ícone, aparece a seguinte interface:
 
-![print_03_PT](//images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/15b1a362d2184c3e8a09f65796ea9db2/print_03_PT.png)
+![print_03_PT](https://images.ctfassets.net/alneenqid6w5/6Yxvh93ja2V69Yywn3CyWt/15b1a362d2184c3e8a09f65796ea9db2/print_03_PT.png)
 
 Configure a nova regra de autorização e, após definir todas as regras desejadas, clique no botão **SALVAR REGRAS**. Você verá a seguinte mensagem: _Após salvar, você ainda poderá editá-las ou excluí-las quando quiser_. Clique em **OK** para  confirmar. Feito isso, você terá concluído a criação da regra de Divergência de valores.
 
diff --git a/docs/tutorials/pt/configuring-prices-v2.md b/docs/tutorials/pt/configuring-prices-v2.md
index 96b604f5f..de2a125d5 100644
--- a/docs/tutorials/pt/configuring-prices-v2.md
+++ b/docs/tutorials/pt/configuring-prices-v2.md
@@ -20,7 +20,7 @@ As funcionalidades descritas neste artigo ainda não estão disponíveis para to
 
 As configurações dos Preços são acessadas pelo botão **Configurações**, do módulo **Preços**.
 
-![Preco24](//images.contentful.com/alneenqid6w5/5Wm20idGbCG0uKei00QQOi/5e18f35d0dd0790e5be98341c67ab4a6/Preco24.gif)
+![Preco24](https://images.contentful.com/alneenqid6w5/5Wm20idGbCG0uKei00QQOi/5e18f35d0dd0790e5be98341c67ab4a6/Preco24.gif)
 
 Nessa tela, é possível fazer o cadastro do markup mínimo. Entenda a seguir o que é markup e como configurá-lo.
 
@@ -41,4 +41,4 @@ O cadastro do markup mínimo, realizado na tela de Configurações, servirá com
 
 O markup mínimo inicial, por política comercial, é sempre zero e pode ser livremente ajustado para valores positivos ou negativos.
 
-![Preco25](//images.contentful.com/alneenqid6w5/12nLR9a2AMwCeuYmmIagCI/94ff929a610a22b1fec685acfc0aec7c/Preco25.gif)
+![Preco25](https://images.contentful.com/alneenqid6w5/12nLR9a2AMwCeuYmmIagCI/94ff929a610a22b1fec685acfc0aec7c/Preco25.gif)
diff --git a/docs/tutorials/pt/configuring-product-visited.md b/docs/tutorials/pt/configuring-product-visited.md
index 94c2a7661..d24c56aaf 100644
--- a/docs/tutorials/pt/configuring-product-visited.md
+++ b/docs/tutorials/pt/configuring-product-visited.md
@@ -21,7 +21,7 @@ Tutorial válido apenas para lojas CMS Portal Legado.
 
 O produto visitado é a funcionalidade que envia e-mails para os clientes que navegaram por um produto em seu site mas não finalizaram compra. Esse e-mail tem como objetivo a recuperação da venda, enviando, além do produto abandonado, sugestões de novos produtos. Tudo isso é possível através de seu Master Data.
 
-[![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](//images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
+[![ExemploProdutoVisitado](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png "![ExemploProdutoVisitado](https://images.contentful.com/alneenqid6w5/3S5FjnFRl6SUoqAkIY84sI/1f6913ec8cd925c89906500a923de0c2/ExemploProdutoVisitado.png)")
 
 _Para esse recurso funcionar de forma adequada é necessário que sua loja possua um alto fluxo de visitas e compras, uma vez que as prateleiras são geradas relacionando dados de navegação a um produto específico._
 
@@ -49,21 +49,21 @@ Por fim, clique no botão **Salvar**.
 Após criar um campo na entidade, é preciso configurar para que o campo seja exibido no formulário &#8211; assim, é possível ver os dados cadastrados nele. Isso também é válido para campos que criados automaticamente pela VTEX mas que não foram marcados para serem exibidos no formulário. Segue abaixo um manual de como exibir os campos que serão importantes para o cenário de Produto Visitado.
 
 1. Acesse o módulo **Master Data**;
-2. Na aplicação **Profile System**, clique no símbolo de **engrenagem**; [![aplicacaoEditar](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png "![aplicacaoEditar](//images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)")
+2. Na aplicação **Profile System**, clique no símbolo de **engrenagem**; [![aplicacaoEditar](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png "![aplicacaoEditar](https://images.contentful.com/alneenqid6w5/5EGLrHpiY8MOcEsUCUCaqS/7edf07ca138296670b0e2b7a0455bbef/aplicacaoEditar.png)")
 3. Clique no símbolo do **lápis** sobre o formulário **Cliente**;
 4. Clique na aba **Schemas de Layout**;
 5. Clique no botão **Incluir Nova seção**;
 6. Dê um nome para esta seção;
-7. Na coluna **Campos disponíveis**, arraste o campo desejado até a área **Campos da coluna 1**, abaixo do nome da seção criada; [![arrastandoCampo](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png "![arrastandoCampo](//images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)") [![arrastandoCampo2](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png "![arrastandoCampo2](//images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)") [![seçãoCriada](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png "![seçãoCriada](//images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)")
+7. Na coluna **Campos disponíveis**, arraste o campo desejado até a área **Campos da coluna 1**, abaixo do nome da seção criada; [![arrastandoCampo](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png "![arrastandoCampo](https://images.contentful.com/alneenqid6w5/57Ridc88Te6kIo2CO4sOEI/80f6dd2602600841e62b666e88a2bd38/arrastandoCampo.png)") [![arrastandoCampo2](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png "![arrastandoCampo2](https://images.contentful.com/alneenqid6w5/4TQBONq7tKoEuEqCSoAS44/967247336bbb61ca775f7dd2488ae4f0/arrastandoCampo2.png)") [![seçãoCriada](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png "![seçãoCriada](https://images.contentful.com/alneenqid6w5/6DwxZSd692YAweEwQs64C4/ed5a48459e501cf8f57ff180ba96dc73/se_C3_A7_C3_A3oCriada.png)")
 8. Clique no botão **Salvar**.
 
 ### Crie o template de e-mail
 
-O template do e-mail que será enviado, assim como no Carrinho Abandonado, é configurado no módulo CMS. Para auxiliar a configuração, [use nosso template de exemplo](//assets.ctfassets.net/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/90018592126fff6bd0d7a9a4ae8568d7/produtovisitadoexemplo.zip).
+O template do e-mail que será enviado, assim como no Carrinho Abandonado, é configurado no módulo CMS. Para auxiliar a configuração, [use nosso template de exemplo](https://assets.ctfassets.net/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/90018592126fff6bd0d7a9a4ae8568d7/produtovisitadoexemplo.zip).
 
 1. Acesse o módulo **CMS**;
 2. Clique em **Portal**;
-3. [Clique aqui para baixar o template de exemplo](//assets.ctfassets.net/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/90018592126fff6bd0d7a9a4ae8568d7/produtovisitadoexemplo.zip)
+3. [Clique aqui para baixar o template de exemplo](https://assets.ctfassets.net/alneenqid6w5/6TloqmkC76AAauQ4e4SWmA/90018592126fff6bd0d7a9a4ae8568d7/produtovisitadoexemplo.zip)
 4. Clique em **Templates de página**;
 5. Clique em **novo template**;
 6. Preencha o nome e cole o código de seu template. Atenção! Se estiver usando o template de exemplo, lembre-se de alterar o código `TEMPLATE_DE_PRATELEIRA` pelo id de seu template de prateleira e o código `NOME_DA_LOJA` pela URL de sua loja.
@@ -103,7 +103,7 @@ Por fim, clique no botão **Salvar Pasta**.
 Após a criação da pasta, associe o template de página ao layout da página.
 
 1. Clique na pasta criada;
-2. Clique em **novo layout**; [![novoLayout](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png "![novoLayout](//images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)")
+2. Clique em **novo layout**; [![novoLayout](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png "![novoLayout](https://images.contentful.com/alneenqid6w5/7x9hPRCKsgwOgk4iQ4IAsq/2eeb7573f284daf0429c7d129a8eaf26/novoLayout.png)")
 3. Selecione o template criado anteriormente;
 4. Clique no botão **Salvar**.
 
@@ -123,7 +123,7 @@ Em **Filtro adicional**, configure conforme abaixo:
 
 Clique no botão **Incluir grupo**, então clique em **Incluir filtro** e preencha conforme abaixo:
 - **Data do último trigger enviado** Menor ou igual `DATAL ATUAL` &#8211; `Subtrair dias` &#8211; `7` or
-- **Data do último trigger enviado** Está nulo [![CondicoesTrigger](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png "![CondicoesTrigger](//images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)")
+- **Data do último trigger enviado** Está nulo [![CondicoesTrigger](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png "![CondicoesTrigger](https://images.contentful.com/alneenqid6w5/2fU6mJE1asQiQ4agmCSSaG/ff6148cbe2f6f07a8e01aea1ee0a68f1/CondicoesTrigger.png)")
 
 Depois, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md b/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md
index 63509e9a1..1bd766c95 100644
--- a/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md
+++ b/docs/tutorials/pt/configuring-promotions-with-a-highlightflag.md
@@ -21,7 +21,7 @@ Tutorial válido apenas para lojas CMS Portal Legado.
 
 O destaque na promoção é um aviso que pode ser inserido nas prateleiras e nas páginas de produto, informando que ele é elegível para uma promoção. Um exemplo bem comum é uma imagem abaixo da imagem do produto indicando frete grátis.
 
-![ExemploPromocaoDestaque2](//images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
+![ExemploPromocaoDestaque2](https://images.contentful.com/alneenqid6w5/jS31HBOW3YWsIYyUOE8o/3d0c108c84b2a7c5e6ae2d4254425e4b/ExemploPromocaoDestaque2.png)
 
 Nem todas as promoções são elegíveis para ter destaque. Esta possibilidade está liberada para os tipos abaixo:
 
@@ -68,9 +68,9 @@ Essa configuração consiste da edição do template de página utilizado para o
 9. Na janela, clique na opção **New Layout**.
 10. No menu lateral, clique sobre o layout marcado em com um check vermelho e no campo __Template__, verifique qual o nome do template utilizado;
 
-![Layout com check - PT](//images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
+![Layout com check - PT](https://images.ctfassets.net/alneenqid6w5/4GmSglkpk78c4M5hDZEgZX/ab47d3105213471fe370be0b11afcfab/image.png)
 
-![Template](//images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
+![Template](https://images.contentful.com/alneenqid6w5/2OzzBkU2YwsgCGeICsgIcg/61aaf502c787cb4f0468ab8cee821072/Template.png)
 
 11.  Volte ao menu lateral e clique na pasta **HTML Templates**;
 12.  Clique no template encontrado no @Produto@;
diff --git a/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md b/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md
index 3411956b2..ee457dd4f 100644
--- a/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md
+++ b/docs/tutorials/pt/configuring-pwa-in-your-store-framework-store.md
@@ -26,11 +26,11 @@ Para configurar um PWA em sua loja, acesse Configurações da Loja > Storefront
 1. Clique na aba **PWA**.
 2. Defina a **Cor do tema**, **Cor de fundo** e adicione o **Ícone de logotipo Android  (512x512, PNG)** e **Ícone de logotipo iOS (512x512, PNG)**. As cores devem ser especificadas em código hexadecimal (e.g., #F71963) e os ícones devem ter tamanho 512x512  px e extensão `.png`.
 
-  ![pwa-settings-1-pt](//images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/9bea6f91cd42a70bffb185f1037f43eb/pwa-settings-1-pt.png)
+  ![pwa-settings-1-pt](https://images.ctfassets.net/alneenqid6w5/2EscgymgyMjCL6nvKedrjk/9bea6f91cd42a70bffb185f1037f43eb/pwa-settings-1-pt.png)
 
 3. Desça a página e vá para o campo **Outras configurações do PWA**. Clique na seta para mostrar as outras configurações.
 
-  ![pwa-settings-2-pt](//images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/faa642b4f2c82f837d6c60a319e63dd0/pwa-settings-2-pt.png)
+  ![pwa-settings-2-pt](https://images.ctfassets.net/alneenqid6w5/2UJAVrnwSn3NPNxxi42nk8/faa642b4f2c82f837d6c60a319e63dd0/pwa-settings-2-pt.png)
 
 4. Em **Outras configurações de PWA**, preencha os campos conforme orientações abaixo:
 
@@ -60,7 +60,7 @@ Para configurar um PWA em sua loja, acesse Configurações da Loja > Storefront
     - **Adicionar à tela inicial**: quando ativada, permite que o PWA seja instalado pelo usuário.
     - **Exibir prompt “Adicionar à tela inicial”**: define o momento em que a instalação do PWA será sugerida ao usuário. Pode ser atribuído um dos seguintes valores: Na primeira visita, Ao adicionar o primeiro item ao carrinho, ou Ao finalizar a primeira compra. Esta opção é aplicável apenas quando **Adicionar à Tela Inicial** está ativada.
 
-   ![pwa-settings-3-pt](//images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/afb78e3e3a3ead92b334b459227ddb0a/pwa-settings-3-pt.png)
+   ![pwa-settings-3-pt](https://images.ctfassets.net/alneenqid6w5/2wVkAwUIy6E33I6pUoXMVT/afb78e3e3a3ead92b334b459227ddb0a/pwa-settings-3-pt.png)
 
  5. Salve suas alterações clicando em `SALVAR`.
 
diff --git a/docs/tutorials/pt/configuring-redirects.md b/docs/tutorials/pt/configuring-redirects.md
index 365a53943..c89ce0514 100644
--- a/docs/tutorials/pt/configuring-redirects.md
+++ b/docs/tutorials/pt/configuring-redirects.md
@@ -27,7 +27,7 @@ Para configurar um redirecionamento, você precisa seguir os passos a seguir:
 
 Você deve preencher os seguintes campos:
 
-![redirecionamentos-adminv4-PT](//images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
+![redirecionamentos-adminv4-PT](https://images.ctfassets.net/alneenqid6w5/69CWrwXk38Qxwb9fNNzYyc/ff394f626cfa64b037bdf652ec07ca38/Screenshot_2022-04-04_at_15-15-42_Intelligent_Search_-_Redirecionamentos.png)
 
 ### Informações gerais
 
diff --git a/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
index 648f6a3e3..9a5dcc4f4 100644
--- a/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
+++ b/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
@@ -30,15 +30,15 @@ Para atribuir sellers à uma determinada organização compradora, siga os passo
 <li>No Admin VTEX, acesse <b>Aplicativos > Organizações e centros de custo B2B > Organizações</b>, ou digite <b>Organizações</b> na barra de busca no topo da página.</li>
 <li>Na aba <b>Organizações</b>, clique sobre o nome da organização compradora desejada.</li>
 
-![Organizações](//images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/b823f4c4377b5eee578e8d58ec9beb87/ORGANIZACOES.jpg)
+![Organizações](https://images.ctfassets.net/alneenqid6w5/1b6R9emKupGC3gv6BqKPbG/b823f4c4377b5eee578e8d58ec9beb87/ORGANIZACOES.jpg)
 
 <li>Na aba <b>Sellers</b>, em <b>Disponível</b>, selecione os sellers desejados.</li>
 
-![Organizações Detalhes](//images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/002155ca14e5ad656741eff101ec5cbc/ORGANIZACOES-DETALHES.jpg)
+![Organizações Detalhes](https://images.ctfassets.net/alneenqid6w5/185XmP4eH8WdgFT5T7CONb/002155ca14e5ad656741eff101ec5cbc/ORGANIZACOES-DETALHES.jpg)
 
 <li>Clique no botão <b>ADICIONAR À ORG</b>.</li>
 
-![Organizações Detalhes 2](//images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/d6152f123a128db9d6803b1899aff232/ORGANIZACOES-DETALHES2.jpg)
+![Organizações Detalhes 2](https://images.ctfassets.net/alneenqid6w5/2assMBtPIxiA80ldC1yNwu/d6152f123a128db9d6803b1899aff232/ORGANIZACOES-DETALHES2.jpg)
 
 <li>Clique no botão <b>Salvar</b>.</li>
 
diff --git a/docs/tutorials/pt/configuring-seo-in-your-store.md b/docs/tutorials/pt/configuring-seo-in-your-store.md
index fa607886a..787b5b5a3 100644
--- a/docs/tutorials/pt/configuring-seo-in-your-store.md
+++ b/docs/tutorials/pt/configuring-seo-in-your-store.md
@@ -34,7 +34,7 @@ Em todas as lojas VTEX IO é possível configurar esses parâmetros nativamente,
   - **Tag de descrição meta**: forneça uma breve descrição do conteúdo da página. Deve ser informativa e conter palavras-chave relevantes.
   - **Metatag robots**: especifique como os motores de busca devem rastrear e indexar uma página específica. Os valores padrão são `index, follow`. Para saber quais outros valores compatíveis com o Google, consulte a [lista de regras válidas](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag?hl=pt-br#directives). 
 
-  ![seo-pt](//images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/538870f8a15ecac304f2c1093764f02d/seo-pt.png)
+  ![seo-pt](https://images.ctfassets.net/alneenqid6w5/4JajNswh0yiVmfWvsPWbEa/538870f8a15ecac304f2c1093764f02d/seo-pt.png)
 
 ### Favicons
 
@@ -42,7 +42,7 @@ Em todas as lojas VTEX IO é possível configurar esses parâmetros nativamente,
 2. Clique na aba **Geral**.
 3. Clique em **Adicionar**.
 
-  ![favicon-pt](//images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/52dc9e3efc6c9cac57f112a40b13158a/favicons-pt.png)
+  ![favicon-pt](https://images.ctfassets.net/alneenqid6w5/3NtSCr6cKVn7dDqsXn8jBN/52dc9e3efc6c9cac57f112a40b13158a/favicons-pt.png)
 
 4. Abrirá uma nova tela, que deve ser preenchida conforme as orientações a seguir:
     - **Relação do favicon**: defina a relação entre a URL configurada no campo
@@ -53,7 +53,7 @@ Em todas as lojas VTEX IO é possível configurar esses parâmetros nativamente,
 
     Veja o exemplo a seguir:
 
-    ![relacao-favicon-pt](//images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/b0b372b4db26ab50def96346b04d028b/relacao-favicon-pt.png)
+    ![relacao-favicon-pt](https://images.ctfassets.net/alneenqid6w5/4gJkfubRqf9lhtRiryrMMA/b0b372b4db26ab50def96346b04d028b/relacao-favicon-pt.png)
 
 5. Clique em **Aplicar** para que as configurações reflitam em sua loja, o que pode levar alguns minutos.
 
diff --git a/docs/tutorials/pt/configuring-shipping-promotions.md b/docs/tutorials/pt/configuring-shipping-promotions.md
index 9321f3304..f81c02f81 100644
--- a/docs/tutorials/pt/configuring-shipping-promotions.md
+++ b/docs/tutorials/pt/configuring-shipping-promotions.md
@@ -40,40 +40,40 @@ Abaixo explicamos alguns cenários que podem ser configurados na plataforma da V
 Caso você habilite a opção **Aplicar o desconto somente no frete mais barato**, o desconto do frete será aplicado somente no menor valor estimado para o frete. Esta opção já aparece habilitada por padrão, mas você pode desabilitá-la caso prefira configurar a promoção conforme o [Cenário 3](#cenario-3) ou o [Cenário 4](#cenario-4).
 
 #### Configuração
-![Aplicar o desconto somente no frete mais barato - PT](//images.contentful.com/alneenqid6w5/2Y0g5Ta6h4VL6uMRQouzjC/94aab036bb00a8162c934780cdfcb1c9/image.png)
+![Aplicar o desconto somente no frete mais barato - PT](https://images.contentful.com/alneenqid6w5/2Y0g5Ta6h4VL6uMRQouzjC/94aab036bb00a8162c934780cdfcb1c9/image.png)
 
 #### Resultado
-![saggincaso1.2](//images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
+![saggincaso1.2](https://images.ctfassets.net/alneenqid6w5/5YS2Iva3GwayZPPA3pqMmf/1b1f4d05ad16378b993a748e4923e12d/saggincaso1.2.png)
 
 ### Cenário 2
 
 Caso você desabilite a opção Aplicar o desconto somente no frete mais barato, o desconto do frete será aplicado em todos os fretes disponíveis.
 
 #### Configuração
-![Nenhum frete selecionado -PT](//images.ctfassets.net/alneenqid6w5/bdzVVgf0w0vxQttjV5bYm/a3a7f5c6af2d23ac3af5a51ca33fe242/image.png)
+![Nenhum frete selecionado -PT](https://images.ctfassets.net/alneenqid6w5/bdzVVgf0w0vxQttjV5bYm/a3a7f5c6af2d23ac3af5a51ca33fe242/image.png)
 
 #### Resultado
-![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Cenário 3
 
 Caso você habilite somente a opção **Tipo de Frete** e selecione os tipos de frete desejados, o desconto de frete será aplicado a todos os tipos de frete selecionados.
 
 #### Configuração
-![Tipo de Frete - PT](//images.ctfassets.net/alneenqid6w5/4cyEZYLm8kQOhIDnB4lvN2/0ff11ad4ee57639a34f2260c40334eb7/image.png)
+![Tipo de Frete - PT](https://images.ctfassets.net/alneenqid6w5/4cyEZYLm8kQOhIDnB4lvN2/0ff11ad4ee57639a34f2260c40334eb7/image.png)
 
 #### Resultado
-![saggincaso2.2](//images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
+![saggincaso2.2](https://images.ctfassets.net/alneenqid6w5/5bfXAeiAs17vBy1nPPg9jh/ee179b414e3325707e8805ab3ba14dcb/saggincaso2.2.png)
 
 ### Cenário 4
 
 Caso você habilite as opções **Tipo de Frete** e **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente** e selecione os tipos de frete desejados, o desconto de frete será aplicado para todos os tipos de frete selecionados somente quando o cliente escolher o tipo de frete no checkout.
 
 #### Configuração
-![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - PT](//images.ctfassets.net/alneenqid6w5/3lL3TwmFFxL8aOW4UvHFER/931f18d33e7c3147ff12a13620f83b45/image.png)
+![Tipo de Frete e Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente - PT](https://images.ctfassets.net/alneenqid6w5/3lL3TwmFFxL8aOW4UvHFER/931f18d33e7c3147ff12a13620f83b45/image.png)
 
 #### Resultado
-![saggincaso3.2](//images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
+![saggincaso3.2](https://images.ctfassets.net/alneenqid6w5/5U1bTkH8109ZfTsnnZrfXG/c5111f305488d0130be338dc0ad07919/saggincaso3.2.png)
 
 Em resumo, a função do checkbox **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente** é de aplicar o desconto somente quando a Transportadora for selecionada.
 
diff --git a/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
index 19957addb..8c7463f81 100644
--- a/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
+++ b/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
@@ -56,7 +56,7 @@ Uma vez concluído o registro junto à Apple, você precisa habilitar na sua loj
 
     Para entender como obter essas credenciais, confira o guia para desenvolvedores [Registering credentials to set up Apple ID login](https://developers.vtex.com/docs/guides/registering-credentials-to-set-up-apple-id-login).
 
-    ![apple-id-setup-pt](//images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/35e10840c391c7f5abfde67cbc7acfa3/apple-id-setup-es.png)
+    ![apple-id-setup-pt](https://images.ctfassets.net/alneenqid6w5/3llgZRzP1yyUiqgZjagXyT/35e10840c391c7f5abfde67cbc7acfa3/apple-id-setup-es.png)
 
 5. Clique em `Salvar`.
 6. Clique em `Provedores da loja virtual` para retornar para a página anterior.
diff --git a/docs/tutorials/pt/configuring-the-additional-freight.md b/docs/tutorials/pt/configuring-the-additional-freight.md
index 3def2edc2..db7999550 100644
--- a/docs/tutorials/pt/configuring-the-additional-freight.md
+++ b/docs/tutorials/pt/configuring-the-additional-freight.md
@@ -22,7 +22,7 @@ O adicional no frete é calculado sobre o valor final do frete, e não sobre o v
 
 O valor da tabela de frete + os demais adicionais ([por peso ou por valor](https://help.vtex.com/pt/tutorial/como-funciona-o-adicional-de-frete)) * o valor cadastrado no campo.
 
-![adicionalfrete3 PT](//images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
+![adicionalfrete3 PT](https://images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
 
 Nesse caso, o valor inserido no campo __Valor adicional__, é o valor percentual que será somado ao valor final calculado do frete. Por exemplo: se o frete, com todos seus adicionais já calculados, der R$20,00 e o valor cadastrado no campo Adicional nos Fretes for 10, significa que será acrescentando R$2,00 aos R$20,00 do frete, totalizando R$ 22,00 a ser cobrado ao cliente pelo frete. Essa é uma maneira simples de conseguir uma margem sobre os fretes das compras.
 
diff --git a/docs/tutorials/pt/configuring-the-global-checkout.md b/docs/tutorials/pt/configuring-the-global-checkout.md
index 15dcee27f..1102089a5 100644
--- a/docs/tutorials/pt/configuring-the-global-checkout.md
+++ b/docs/tutorials/pt/configuring-the-global-checkout.md
@@ -49,7 +49,7 @@ Dois novos botões devem ser exibidos em seu Checkout:
 - "Não tenho CPF".
 - "Não tenho telefone brasileiro".
 
-![checkoutuniversal1](//images.contentful.com/alneenqid6w5/5M3l0zai5ii4KiayKG4ooI/9a9d27ea50bb97fd248093a6972748e3/checkoutuniversal1.png)
+![checkoutuniversal1](https://images.contentful.com/alneenqid6w5/5M3l0zai5ii4KiayKG4ooI/9a9d27ea50bb97fd248093a6972748e3/checkoutuniversal1.png)
 
 ## Exibindo novos endereços de entrega e fatura
 
diff --git a/docs/tutorials/pt/configuring-the-marketplace-between-vtex-stores.md b/docs/tutorials/pt/configuring-the-marketplace-between-vtex-stores.md
index 34cb5c072..555f31a04 100644
--- a/docs/tutorials/pt/configuring-the-marketplace-between-vtex-stores.md
+++ b/docs/tutorials/pt/configuring-the-marketplace-between-vtex-stores.md
@@ -38,7 +38,7 @@ Depois de realizar as configurações, é necessário fazer a indexação de tod
 1. Com o [usuário titular](https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA?locale=pt), acesse o link `{nomedaloja}.vtexcommercestable.com.br/admin/Site/FullCleanUp.aspx`.
 2. Clique no botão __Reindexar Base__.
 
-[![ReindexarBase](//images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)](//images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png "![ReindexarBase](//images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)")
+[![ReindexarBase](https://images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)](https://images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png "![ReindexarBase](https://images.contentful.com/alneenqid6w5/7Eg8CAclRSSqaSS8cqI66S/44944a80535a465fc449c44b8066b557/ReindexarBase.png)")
 
 Perceba que, na URL, é preciso alterar o termo `{nomedaloja}` para o nome de sua loja.
 
diff --git a/docs/tutorials/pt/configuring-the-past-prices-control.md b/docs/tutorials/pt/configuring-the-past-prices-control.md
index f6f951720..e297041e2 100644
--- a/docs/tutorials/pt/configuring-the-past-prices-control.md
+++ b/docs/tutorials/pt/configuring-the-past-prices-control.md
@@ -33,7 +33,7 @@ Veja [aqui](http://help.vtex.com/tutorial/lista-de-controles-para-templates/ "aq
 
 O modo de exibição padrão dos valores segue o modelo da imagem abaixo. São exibidos em sequência o ano, o mês e o menor valor faturado neste mês.
 
-![HistPrecos](//images.contentful.com/alneenqid6w5/2AX7uKU4zW66sA0AICcEM2/81042cedd7d0ef937b1c56a8878d8d0c/HistPrecos.png)
+![HistPrecos](https://images.contentful.com/alneenqid6w5/2AX7uKU4zW66sA0AICcEM2/81042cedd7d0ef937b1c56a8878d8d0c/HistPrecos.png)
 
 Caso a loja deseje exibir os dados de outra forma, será necessário fazer a customização por meio de uma agência de layout.
 
diff --git a/docs/tutorials/pt/configuring-the-pickup-in-store.md b/docs/tutorials/pt/configuring-the-pickup-in-store.md
index a557dcd2e..984c89211 100644
--- a/docs/tutorials/pt/configuring-the-pickup-in-store.md
+++ b/docs/tutorials/pt/configuring-the-pickup-in-store.md
@@ -28,17 +28,17 @@ A configuração de retirada na loja possibilita ao cliente a escolha de não re
 3. Para essas transportadores, é recomendado que não se cobre valor de frete.
 4. Após criadas todas as  transportadoras, é preciso criar uma transportadora com o nome genérico de _Retirada no local _a qual será usada na programação do front-end da loja (na opçao de seleção de frete).
 
-![](//images.contentful.com/alneenqid6w5/1aPl4HkPD8IagOICkCuigu/185dffc5b9bfd322697b6bf7ae0e7942/1.jpg)
+![](https://images.contentful.com/alneenqid6w5/1aPl4HkPD8IagOICkCuigu/185dffc5b9bfd322697b6bf7ae0e7942/1.jpg)
 
 ## Customização visual (Front-end)
 
 Deverá ser implementado um arquivo _javascript_ no checkout da loja, de acordo com as orientações abaixo.
 
 1. O usuário fará a compra normal dos produtos até a página de checkout.
-2. Após o preenchimento dos dados pessoais, o usuário chega na área de seleção da transportadora. O comportamento da ferramenta normalmente é de apresentar todas as transportadoras disponíveis configuradas. Portanto após configuradas, o _javascript_ deverá “esconder” as opções das lojas disponíveis e apresentar apenas a transportadora genérica que foi criada no ponto 4 acima chamada de **Retirada no local** (ou Retirada en Sucursal &#8211; espanhol).![OpcoesdeEnvio](//images.contentful.com/alneenqid6w5/3YpLqm1q2ckOm4i4g8KWAQ/edc9d9ff1e32352306c1b152c12997e7/OpcoesdeEnvio.png)
-3. Quando o usuário selecionar a opção de retirada no local (retirada en surcursal), o JavaScript abre um lightbox apresentando na tela as opções de lojas para o usuário selecionar. As opções que aparecem aqui são as transportadoras cadastradas no admin nos passos 1 e 2. A imagem abaixo mostra como a loja optou por apresentar visualmente a seleção das lojas para retirada.![](//images.contentful.com/alneenqid6w5/XZ0kevBW6sEK2sGKsYsGm/84c5681cf6c9cf923e90d337d3a727d8/3.jpg)
-4. Quando o usuário escolhe alguma das opções, o _javascript _fecha o _lightbox_ e retorna para a opção de seleção de frete, informando que a seleção foi salva com sucesso.![](//assets.contentful.com/alneenqid6w5/4ekRwP5Hy0yE8ckaWGCAQG/b358a05721f4ce0cc0221fd6eb0ff955/4.bmp)
-5. Após esse retorno da seleção, o _javascript _deve alterar a opção de entrega genérica pela opção real da loja cadastrada, esta que até então, não estava visível no front-end.![](//images.contentful.com/alneenqid6w5/3DlztWQIEUOqoomMeA8yiq/15f3ffa1fe1a10d004ab0c13938ec7fe/5.jpg)
+2. Após o preenchimento dos dados pessoais, o usuário chega na área de seleção da transportadora. O comportamento da ferramenta normalmente é de apresentar todas as transportadoras disponíveis configuradas. Portanto após configuradas, o _javascript_ deverá “esconder” as opções das lojas disponíveis e apresentar apenas a transportadora genérica que foi criada no ponto 4 acima chamada de **Retirada no local** (ou Retirada en Sucursal &#8211; espanhol).![OpcoesdeEnvio](https://images.contentful.com/alneenqid6w5/3YpLqm1q2ckOm4i4g8KWAQ/edc9d9ff1e32352306c1b152c12997e7/OpcoesdeEnvio.png)
+3. Quando o usuário selecionar a opção de retirada no local (retirada en surcursal), o JavaScript abre um lightbox apresentando na tela as opções de lojas para o usuário selecionar. As opções que aparecem aqui são as transportadoras cadastradas no admin nos passos 1 e 2. A imagem abaixo mostra como a loja optou por apresentar visualmente a seleção das lojas para retirada.![](https://images.contentful.com/alneenqid6w5/XZ0kevBW6sEK2sGKsYsGm/84c5681cf6c9cf923e90d337d3a727d8/3.jpg)
+4. Quando o usuário escolhe alguma das opções, o _javascript _fecha o _lightbox_ e retorna para a opção de seleção de frete, informando que a seleção foi salva com sucesso.![](https://assets.contentful.com/alneenqid6w5/4ekRwP5Hy0yE8ckaWGCAQG/b358a05721f4ce0cc0221fd6eb0ff955/4.bmp)
+5. Após esse retorno da seleção, o _javascript _deve alterar a opção de entrega genérica pela opção real da loja cadastrada, esta que até então, não estava visível no front-end.![](https://images.contentful.com/alneenqid6w5/3DlztWQIEUOqoomMeA8yiq/15f3ffa1fe1a10d004ab0c13938ec7fe/5.jpg)
 6. Após essa área de seleção, o cliente segue o fluxo normal de compra.
 
 _Insira uma legenda informando em quantos dias o pedido estará disponível para busca na loja física._
@@ -47,6 +47,6 @@ _Insira uma legenda informando em quantos dias o pedido estará disponível para
 
 No OMS será possível visualizar o pedido do cliente, ao qual irá constar qual loja ele selecionou para retirar o pedido. Essa informação você pode encontrar na área em que os produtos são apresentados.
 
-![](//images.contentful.com/alneenqid6w5/5LIVnwfutq826ciMOOcmUQ/6b1e5180ff186b6199460eb0d7a456c2/6.jpg)
+![](https://images.contentful.com/alneenqid6w5/5LIVnwfutq826ciMOOcmUQ/6b1e5180ff186b6199460eb0d7a456c2/6.jpg)
 
 Lembre-se! O desenvolvimento do javascript necessário para este cenário deve ser desenvolvido pela equipe de desenvolvimento da loja ou por um de nossos [parceiros certificados](http://store.vtex.com "parceiros certificados").
diff --git a/docs/tutorials/pt/configuring-the-scheduled-delivery.md b/docs/tutorials/pt/configuring-the-scheduled-delivery.md
index 9092f3b67..d3abc6f3f 100644
--- a/docs/tutorials/pt/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/pt/configuring-the-scheduled-delivery.md
@@ -31,7 +31,7 @@ Em **Estoque & entrega**, acesse **Painéis** e escolha a **Transportadora** des
 
 Em **Tipo da entrega**, clique  **Entrega agendada**.
 
-![entrega-agendada pt](//images.ctfassets.net/alneenqid6w5/6bbP1sy4xiKUSmYAWGWgMq/c6370ec0630605c537bea7e65e1d15a1/entrega-agendada_pt.png)
+![entrega-agendada pt](https://images.ctfassets.net/alneenqid6w5/6bbP1sy4xiKUSmYAWGWgMq/c6370ec0630605c537bea7e65e1d15a1/entrega-agendada_pt.png)
 Para entender melhor como cadastrar os demais campos da transportadora, veja também nossa documentação sobre [cadastro de transportadora](http://help.vtex.com/pt/tutorial/gerenciar-transportadora).
 
 Nesta estrutura, temos os seguintes dados:
@@ -44,7 +44,7 @@ Nesta estrutura, temos os seguintes dados:
 
 Usando o mesmo cenário da loja citada acima, segue a configuração da transportadora segundo sua demanda:
 
-![](//images.contentful.com/alneenqid6w5/6AEhj0a4SIeyQWCI6IQeCk/28a10fa00baa9723e73847d983e12d66/horariosentregaagendada.jpg)
+![](https://images.contentful.com/alneenqid6w5/6AEhj0a4SIeyQWCI6IQeCk/28a10fa00baa9723e73847d983e12d66/horariosentregaagendada.jpg)
 
 Supondo que o Estoque tem 2 dias de prazo; a Doca tem 1 dia de prazo; a Tabela de Frete tem 5 dias de prazo. O primeiro dia disponibilizado será **8** dias depois da data que o pedido está sendo efetuado. Como o Tempo Máximo de Entrega é de 10 dias, o último dia disponível para a escolha será o **18º** dia após a data que o pedido está sendo efetuado.
 
diff --git a/docs/tutorials/pt/configuring-the-store-domain.md b/docs/tutorials/pt/configuring-the-store-domain.md
index c24fe8d9d..c833b7ff3 100644
--- a/docs/tutorials/pt/configuring-the-store-domain.md
+++ b/docs/tutorials/pt/configuring-the-store-domain.md
@@ -26,7 +26,7 @@ As configurações relacionadas ao domínio são necessárias para que um endere
 
 O endereço da loja é composto pelos elementos ilustrados a seguir:
 
-![url-diagram-pt (3)](//images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/4d3a9763fcd76907f3587f77d8cc9947/url-diagram-pt__3_.png)
+![url-diagram-pt (3)](https://images.ctfassets.net/alneenqid6w5/kg98gTuZiMlewhPiRAyaF/4d3a9763fcd76907f3587f77d8cc9947/url-diagram-pt__3_.png)
 
 | Elemento | Descrição | Exemplo |
 |---|---|---|
diff --git a/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md b/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md
index c520dd44b..78db15b10 100644
--- a/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md
+++ b/docs/tutorials/pt/copying-a-layout-from-one-web-site-to-another.md
@@ -25,10 +25,10 @@ Para isto, no Admin VTEX, acesse **Storefront > Layout > CMS** e clicar no layou
 
 O botão fica no canto superior direito, como mostra a imagem abaixo.
 
-!![copiar layout](//images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
+!![copiar layout](https://images.ctfassets.net/alneenqid6w5/796Zfon1lYOc4Kyg2QeqQg/55aa8b65fb505e09b8088eb7bed884bc/copiar_layout.png)
 
 O sistema vai perguntar para qual web site você quer copiar o layout.
 
 Selecione o web site e clique em __Copiar Layout__.
 
-![copyLayout2](//images.contentful.com/alneenqid6w5/1KPGgtczwMmKEeQKOM44yk/3e74ac50ac9a0fbe89f0de3fbd4a4d7a/copyLayout2.png)
+![copyLayout2](https://images.contentful.com/alneenqid6w5/1KPGgtczwMmKEeQKOM44yk/3e74ac50ac9a0fbe89f0de3fbd4a4d7a/copyLayout2.png)
diff --git a/docs/tutorials/pt/coupons-list-beta.md b/docs/tutorials/pt/coupons-list-beta.md
index 2619a0203..e9afa3892 100644
--- a/docs/tutorials/pt/coupons-list-beta.md
+++ b/docs/tutorials/pt/coupons-list-beta.md
@@ -31,7 +31,7 @@ A partir desta página, você pode:
 
 Para acessá-la no Admin VTEX, clique em **Promoções > Cupons**.
 
-![lista-cupons](//images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/74d61d0b59d9b69728c62b5e1dc5bae7/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-28-18_42_26.png)
+![lista-cupons](https://images.ctfassets.net/alneenqid6w5/3KpOX5OW4oM5dBUNxkc0YP/74d61d0b59d9b69728c62b5e1dc5bae7/screencapture-coupons-pricingqa-myvtex-admin-coupons-2022-04-28-18_42_26.png)
 
 A seguir, confira a descrição dos componentes e ações incluídos na página.
 
@@ -83,7 +83,7 @@ O arquivo gerado contém as informações descritas a seguir.
 
 Veja um exemplo de arquivo CSV exportado a seguir:
 
-![cupons-exportados](//images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
+![cupons-exportados](https://images.ctfassets.net/alneenqid6w5/3BiCzXoNpaMM1ZpkBoa3Nr/921b74b837ae69f974aef332dc8d816a/image3.png)
 
 #### Exportar códigos de um grupo de cupons
 
@@ -100,13 +100,13 @@ Para visualizar ou exportar todos os códigos de um grupo, é necessário seguir
     * <i class="far fa-clone"></i> **Copiar tudo:** permite copiar os códigos gerados para a sua área de transferência. Também é possível copiar cada código clicando sobre ele.
     * **Exportar:** permite exportar os códigos gerados para um arquivo CSV. O arquivo exportado contém uma coluna, com um código por linha.
 
-![exportar-cupons](//images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/27a207fd3f7adc0ebe4493cd5ea15f0f/exportarcupons.PNG)
+![exportar-cupons](https://images.ctfassets.net/alneenqid6w5/P8bIJHkyTTi2jVZ325rko/27a207fd3f7adc0ebe4493cd5ea15f0f/exportarcupons.PNG)
 
 ### Ver uso dos cupons
 
 Para visualizar o total de cupons ativos e a cota de espaço restante para novos cupons, clique em <i class="fas fa-chart-line"></i> `Uso dos cupons`.
 
-![uso-dos-cupons](//images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7c4529a241f54d4e3203ce5c1237bdfc/usodoscupons.PNG)
+![uso-dos-cupons](https://images.ctfassets.net/alneenqid6w5/CaNOtLMQXu26MGYfaAe4o/7c4529a241f54d4e3203ce5c1237bdfc/usodoscupons.PNG)
 
 O número máximo de cupons ativos que você pode ter é 5 mil. Para liberar espaço, você pode arquivar cupons a partir da [Lista de cupons](#lista-de-cupons). Caso precise aumentar o limite de cupons ativos, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
@@ -155,13 +155,13 @@ O modal **Ver detalhes de uso** apresenta os dados de utilização de cada cupom
 
     Esta seção também apresenta a lista de pedidos em que o código foi utilizado e permite buscar pelo número de um pedido. Ao clicar no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-![ver-detalhes-uso](//images.ctfassets.net/alneenqid6w5/4dVuN6fKsu3WRsMSQbZT4e/648e8a2216470558beddea7e9fb0087b/Group_1__4_.png)
+![ver-detalhes-uso](https://images.ctfassets.net/alneenqid6w5/4dVuN6fKsu3WRsMSQbZT4e/648e8a2216470558beddea7e9fb0087b/Group_1__4_.png)
 
 * **Uso geral dos códigos de cupom** (grupos de cupons): exibe a quantidade total de usos dos códigos de um grupo de cupons e a quantidade de usos restantes, caso você tenha limitado a quantidade de usos.
 
     Esta seção também apresenta a lista de códigos do grupo de cupons e permite buscar por um código específico. Ao clicar em um código, você tem acesso à lista de pedidos em que o código foi utilizado e pode buscar pelo número de um pedido. Ao clicar no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-![selecione-o-codigo-grupo-cupons](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png)
+![selecione-o-codigo-grupo-cupons](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/create-a-talk-to-us-form-using-master-data.md b/docs/tutorials/pt/create-a-talk-to-us-form-using-master-data.md
index 75418e92f..dc3cd42f0 100644
--- a/docs/tutorials/pt/create-a-talk-to-us-form-using-master-data.md
+++ b/docs/tutorials/pt/create-a-talk-to-us-form-using-master-data.md
@@ -117,6 +117,6 @@ O plugin foi desenvolvido para facilitar a instalação do formulário no templa
 - jQuery
 - Bootstrap
 
-[Para maiores detalhes, acesse o exemplo em anexo](//assets.ctfassets.net/alneenqid6w5/6vHFk9dnVeUoqICKGiSqqC/70f380832091ceaae3576a82f56a87d5/contactMasterData.zip "Para maiores detalhes, acesse o exemplo em anexo").
+[Para maiores detalhes, acesse o exemplo em anexo](https://assets.ctfassets.net/alneenqid6w5/6vHFk9dnVeUoqICKGiSqqC/70f380832091ceaae3576a82f56a87d5/contactMasterData.zip "Para maiores detalhes, acesse o exemplo em anexo").
 
 **Importante**: esse plugin foi desenvolvido para auxiliar o desenvolvimento do formulário de Fale Conosco utilizando Master Data. A VTEX **NÃO** oferece suporte a essa extensão e seu código é aberto, podendo sofrer alterações e adaptações.
diff --git a/docs/tutorials/pt/creating-a-campaign-audience.md b/docs/tutorials/pt/creating-a-campaign-audience.md
index 140099d23..e7ece28b4 100644
--- a/docs/tutorials/pt/creating-a-campaign-audience.md
+++ b/docs/tutorials/pt/creating-a-campaign-audience.md
@@ -69,7 +69,7 @@ Após clicar em `Criar novo público-alvo`, você precisa seguir as instruções
     * **ou:** a audiência de campanha será composta por clientes que se encaixarem em qualquer um dos públicos-alvo.
     * **e:** a audiência de campanha será composta por clientes que se encaixarem em todos os públicos-alvos, somando seus critérios.
 
-![publico-alvo-e-ou-pt](//images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
+![publico-alvo-e-ou-pt](https://images.ctfassets.net/alneenqid6w5/2NrpuE4MN7q6qaHI6mkoCe/92a1ac37149d16f9b039cd1f024e6dff/image4.gif)
 
 ### Defina seu público-alvo
 
@@ -85,7 +85,7 @@ Após clicar em `Criar novo público-alvo`, você precisa seguir as instruções
 
 Exemplo: participam do público-alvo os itens cuja marca é __Nike__, conforme ilustrado a seguir. A configuração também indica que pelo menos 3 itens precisam se enquadrar nesses critérios. Portanto, um cliente precisa ter no carrinho pelo menos 3 itens que se encaixam nesse cenário para participar do público-alvo.
 
-![exemplo-marca-publico-alvo-pt](//images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/e92e92a79b28abc9bbfe84f886c17c8d/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_12_45_1.png)
+![exemplo-marca-publico-alvo-pt](https://images.ctfassets.net/alneenqid6w5/4Bot3XZUQJ4JkWJknpTxB2/e92e92a79b28abc9bbfe84f886c17c8d/screencapture-lojadobreno-myvtex-admin-rnb-2022-07-21-18_12_45_1.png)
 
 ### Condições para seu público-alvo ser aplicado
 
diff --git a/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md b/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
index 0f9cc7491..4136990d6 100644
--- a/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
+++ b/docs/tutorials/pt/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout.md
@@ -21,7 +21,7 @@ Se seu cliente final compra um produto em qualquer dos seus canais (online ou lo
 
 No entanto, você pode preferir que essa loja funcione como ponto de retirada __mesmo se ela não tiver estoque__. Para isso, sua logística precisa garantir que o produto chegará a essa loja a partir de outro estoque - por exemplo, a partir do estoque do e-commerce. Neste caso, você precisa ter uma política de envio no e-commerce em que esteja configurado o ponto de retirada da loja física.
 
-![Criar ponto de retirada de contingência para garanti-lo como opção no checkout](//images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/53b839763aa9f25178d599d78eb73203/diagrama-como-criar-um-ponto-de_contigencia-pt.jpg)
+![Criar ponto de retirada de contingência para garanti-lo como opção no checkout](https://images.ctfassets.net/alneenqid6w5/38phAuzqPzQoBPy8811K3K/53b839763aa9f25178d599d78eb73203/diagrama-como-criar-um-ponto-de_contigencia-pt.jpg)
 
 ## Como implementar um ponto de retirada de contingência
 
diff --git a/docs/tutorials/pt/creating-a-coupon-beta.md b/docs/tutorials/pt/creating-a-coupon-beta.md
index 554b5777e..25281403f 100644
--- a/docs/tutorials/pt/creating-a-coupon-beta.md
+++ b/docs/tutorials/pt/creating-a-coupon-beta.md
@@ -40,7 +40,7 @@ O formulário para criar ou editar um cupom apresenta as seguintes seções:
 
 O painel superior do formulário de criação e edição de cupom, ilustrado abaixo, apresenta a quantidade de vezes em que o cupom foi utilizado e a quantidade de promoções vinculadas ao cupom.
 
-![usos-do-cupom-promocoes-vinculadas](//images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/7642e6bfa91548c82c851d849fd34a87/criar-cupom-1.png)
+![usos-do-cupom-promocoes-vinculadas](https://images.ctfassets.net/alneenqid6w5/3HAiF63zYFGjrfOnBCl5Hb/7642e6bfa91548c82c851d849fd34a87/criar-cupom-1.png)
 
 Ao clicar em qualquer uma dessas informações no painel, você tem acesso ao modal **Ver detalhes de uso**, que apresenta os dados descritos a seguir:
 
@@ -52,11 +52,11 @@ Ao clicar em qualquer uma dessas informações no painel, você tem acesso ao mo
 
     Caso o cupom seja único, esta seção apresenta a lista de pedidos em que o cupom foi utilizado e permite buscar pelo número de um pedido. Ao clicar no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-  ![ver-detalhes-de-uso](//images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/bcd304169c9f0763693e8d85f54e3e01/ver-detalhes-de-uso.png "Detalhes de uso de um cupom único")
+  ![ver-detalhes-de-uso](https://images.ctfassets.net/alneenqid6w5/1bFOCXCpWwoXzJToacK3BM/bcd304169c9f0763693e8d85f54e3e01/ver-detalhes-de-uso.png "Detalhes de uso de um cupom único")
 
     Caso seja um grupo de cupons, esta seção apresenta a lista de códigos do grupo de cupons e permite buscar por um código específico. Ao clicar em um código, você tem acesso à lista de pedidos em que o código foi utilizado e pode buscar pelo número de um pedido. Clicando no número de um pedido, você será conduzido para a página de detalhes do pedido no **Gerenciamento de pedidos**.
 
-  ![selecione-o-codigo-grupo-cupons](//images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png "Detalhes de uso de um grupo de cupons")
+  ![selecione-o-codigo-grupo-cupons](https://images.ctfassets.net/alneenqid6w5/25yE4tmkHYDm4MISaz9upH/87b9f4e806c8d2c0b4399d64524658b4/Group_2__4_.png "Detalhes de uso de um grupo de cupons")
 
 ### Geral
 
@@ -92,7 +92,7 @@ Após salvar o novo cupom, se você tiver criado um [grupo de cupons](https://he
 * <i class="far fa-clone"></i> **Copiar tudo:** permite copiar os códigos gerados para a sua área de transferência. Posteriormente, se desejar, você pode colá-los em um editor de planilhas como o Excel ou o Google Sheets. Também é possível copiar cada código clicando sobre ele.
 * **Exportar:** permite exportar os códigos gerados para um arquivo CSV. O arquivo exportado contém uma coluna, com um código por linha.
 
-![cupons-gerados-pt](//images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/094bd2aaca673c282bba6a95f688a1b4/cupons-gerados-pt.gif)
+![cupons-gerados-pt](https://images.ctfassets.net/alneenqid6w5/3Ar3vHIyynacQr9vJ5qUf3/094bd2aaca673c282bba6a95f688a1b4/cupons-gerados-pt.gif)
 
 ## Vincular o cupom a uma promoção
 
diff --git a/docs/tutorials/pt/creating-a-form-to-record-information-using-master-data-newsletter.md b/docs/tutorials/pt/creating-a-form-to-record-information-using-master-data-newsletter.md
index 684b8d39f..20b691d78 100644
--- a/docs/tutorials/pt/creating-a-form-to-record-information-using-master-data-newsletter.md
+++ b/docs/tutorials/pt/creating-a-form-to-record-information-using-master-data-newsletter.md
@@ -30,6 +30,6 @@ Depois de concluir as configurações acima, você precisa incluir em nossa CMS
  
 Neste link você vai encontrar um exemplo de um HTML e JS, que serve como um guia para a implementação no CMS.
  
-[Código de exemplo](//assets.contentful.com/alneenqid6w5/xC0HA56uzIO8Ueca2c02g/eb126bee0a1618dff60da75c997a85e2/newsletterMasterData.rar).
+[Código de exemplo](https://assets.contentful.com/alneenqid6w5/xC0HA56uzIO8Ueca2c02g/eb126bee0a1618dff60da75c997a85e2/newsletterMasterData.rar).
  
 IMPORTANTE: Este plugin foi desenvolvido para ajudar a desenvolver uma forma básica usando Master Data (MD). não VTEX não suporta essa extensão e seu código é aberto e pode sofrer modificações e adaptações.
diff --git a/docs/tutorials/pt/creating-a-more-for-less-promotion.md b/docs/tutorials/pt/creating-a-more-for-less-promotion.md
index 2f900769d..adcdea7a7 100644
--- a/docs/tutorials/pt/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/pt/creating-a-more-for-less-promotion.md
@@ -50,7 +50,7 @@ Nesta seção, fornecemos informações detalhadas sobre os dados gerais desta p
 - **Informações adicionais (opcional):** permite  incluir informações adicionais a promoção composto de um nome e valor.
 - **Destaque nos produtos:** insere uma tag com o nome da promoção, utilizada na vitrine e na página do produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template: `<vtex.cmc:discountHightLight/>`. Campo de preenchimento obrigatório.
 
-![Dados gerais 1 - PT](//images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/39c1ba28770bab08c1c8eebcdcf2c5a5/Dados_gerais_1_-_PT.png)
+![Dados gerais 1 - PT](https://images.ctfassets.net/alneenqid6w5/4Ara5CRqjivFlYltPnMGpN/39c1ba28770bab08c1c8eebcdcf2c5a5/Dados_gerais_1_-_PT.png)
 
 ### Restringir esta promoção a produtos dos sellers
 
@@ -64,7 +64,7 @@ Para que a promoção seja válida para todos os sellers, deixe a seleção vazi
   <p>Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
 </div>
 
-![Restringir - PT](//images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/6a43d51af7293cbfee1e0f9a2de2428a/Restringir_-_PT.png)
+![Restringir - PT](https://images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/6a43d51af7293cbfee1e0f9a2de2428a/Restringir_-_PT.png)
 
 ### Política comercial
 
@@ -77,7 +77,7 @@ Esta seção estabelece as políticas comerciais válidas para a promoção. Voc
 
 Para que a promoção seja válida para todas as políticas comerciais, deixe a seleção vazia.
 
-![Politica - PT](//images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/15e5033e2d6b01b848e2d16c81762cb1/Politica_-_PT.png)
+![Politica - PT](https://images.ctfassets.net/alneenqid6w5/5fuMmvGh34BpTbj3t3AgdR/15e5033e2d6b01b848e2d16c81762cb1/Politica_-_PT.png)
 
 ## 2. Leve mais por menos
 
@@ -95,7 +95,7 @@ Esta seção define os produtos, a quantidade e o desconto que serão afetados p
     - **Com desconto de:** o cliente levará a quantidade selecionada de produtos com um desconto percentual definido no campo.
     - **Preço Máximo por Item:** o cliente levará a quantidade selecionada de produtos com um preço máximo por item definido no campo.
 
- ![Leve Mais - PT](//images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/4007f36df438fc5192f131f39f624d02/Leve_Mais_-_PT.png)
+ ![Leve Mais - PT](https://images.ctfassets.net/alneenqid6w5/65GpdBT4FEpUQSNtZ7NXEH/4007f36df438fc5192f131f39f624d02/Leve_Mais_-_PT.png)
 
 ### Configurações avançadas
 
@@ -109,7 +109,7 @@ O desconto deve ser aplicado:
         - **Mais baratos:** o desconto será aplicado aos itens mais baratos da promoção.
         - **Mais caros:** o desconto será aplicado aos itens mais caros da promoção.
 
-![Leve Mais por menos - PT](//images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/8e369e751ba27732e5c324c0cae7c7e1/Leve_Mais_por_menos_-_PT.png)
+![Leve Mais por menos - PT](https://images.ctfassets.net/alneenqid6w5/7lIEbcThX12WgUZvtCgx6E/8e369e751ba27732e5c324c0cae7c7e1/Leve_Mais_por_menos_-_PT.png)
 
 #### Como o desconto deve ser distribuído?
 - **Apenas entre as `quantidade` produtos que recebem desconto:** o desconto será aplicado integralmente à quantidade de produtos selecionada.
@@ -132,7 +132,7 @@ Nesta seção, detalharemos as condições em que você deve aplicar para que um
   <p> Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
  </div>
 
-![Condições de promoção - PT](//images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/d5a51e69868ee890a701dba2dfe8a1f2/Condi__es_de_promo__o_-_PT.png)
+![Condições de promoção - PT](https://images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/d5a51e69868ee890a701dba2dfe8a1f2/Condi__es_de_promo__o_-_PT.png)
 
  ## 4. Restrições e limitações de uso
 
@@ -142,4 +142,4 @@ Nesta seção, detalharemos as condições em que você deve aplicar para que um
  - **Permitir acumular promoções:** permite que mais de uma promoção, independente do tipo de desconto, seja concedida ao mesmo tempo. Saiba mais sobre [como funciona a concorrência de promoções](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270).
 - **Permitir acumular com preços manuais:** permite que a promoção seja aplicada a produtos cujos preços foram manualmente inseridos pelo televendas. Para habilitar a funcionalidade de preços manuais, use o endpoint [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm).
 
-![Restrições e limitações - PT](//images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/ea978a02b2454f97243b951981d0ff1b/Restri__es_e_limita__es_-_PT.png)
+![Restrições e limitações - PT](https://images.ctfassets.net/alneenqid6w5/5jrjtfnEkqiA9ipZEi1jjk/ea978a02b2454f97243b951981d0ff1b/Restri__es_e_limita__es_-_PT.png)
diff --git a/docs/tutorials/pt/creating-a-personalized-master-data-query.md b/docs/tutorials/pt/creating-a-personalized-master-data-query.md
index 88e94a2a5..2af8206fa 100644
--- a/docs/tutorials/pt/creating-a-personalized-master-data-query.md
+++ b/docs/tutorials/pt/creating-a-personalized-master-data-query.md
@@ -21,15 +21,15 @@ Para criar uma consulta, é necessário que [seja realizado um filtro na listage
 
 Após filtrar, _clique no botão **Salvar Consulta** -> dê um nome para a consulta -> clique no botão **Salvar**_.
 
-![image00(3)](//images.contentful.com/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/6698a619ebf6041e828b61ef657ceb89/image003.png)
+![image00(3)](https://images.contentful.com/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/6698a619ebf6041e828b61ef657ceb89/image003.png)
 
 Então, para que a consulta apareça como uma opção de visualização na listagem, basta recarregar a aplicação, na aba **Aplicações**. Clicando no botão **Recarregar aplicações**.
 
-![image02(2)](//images.contentful.com/alneenqid6w5/23qCsgXVSYQYmsS6Ya6eAs/99c65c0009dd7f9e75c1ba4a2cea50cc/image022.png)
+![image02(2)](https://images.contentful.com/alneenqid6w5/23qCsgXVSYQYmsS6Ya6eAs/99c65c0009dd7f9e75c1ba4a2cea50cc/image022.png)
 
 Além disso, é possível ver todas as consultas salvas clicando sobre o botão **Consultas**, na listagem do formulário.
 
-![consulta3](//images.contentful.com/alneenqid6w5/4h0zjZuAc8W8eUaqImo2qg/b1c06c13603d398d1f83bef9f7deb19b/image012.png)
+![consulta3](https://images.contentful.com/alneenqid6w5/4h0zjZuAc8W8eUaqImo2qg/b1c06c13603d398d1f83bef9f7deb19b/image012.png)
 
 Também é interessante configurar um formulário para que ele sempre traga a listagem com o filtro da consulta. Para isso, siga o passo a passo:
 
@@ -40,4 +40,4 @@ Também é interessante configurar um formulário para que ele sempre traga a l
 5. Na opção **Consulta Padrão**, selecione a consulta personalizada que deseja exibir sempre que clicar no formulário.
 6. Clique no botão **Salvar**.
 
-![consulta5](//images.contentful.com/alneenqid6w5/66y0WU112osUwkwuyMquMW/a9143a8ca1aa05bc49cc69d1dd102002/image032.png)
+![consulta5](https://images.contentful.com/alneenqid6w5/66y0WU112osUwkwuyMquMW/a9143a8ca1aa05bc49cc69d1dd102002/image032.png)
diff --git a/docs/tutorials/pt/creating-a-product-collection.md b/docs/tutorials/pt/creating-a-product-collection.md
index c6176f717..b5a91e39f 100644
--- a/docs/tutorials/pt/creating-a-product-collection.md
+++ b/docs/tutorials/pt/creating-a-product-collection.md
@@ -25,7 +25,7 @@ Para criar uma coleção, siga as instruções abaixo:
 2. Clique em **Layout**.
 3. Clique na pasta **Product Clusters (Collections)**.
 4. Clique no botão `new collection`, ilustrado a seguir.
-	![Layout 4](//images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
+	![Layout 4](https://images.ctfassets.net/alneenqid6w5/2qvwI8D3FKuEuyCaEEcu4I/4add6510a4fa136243f35bebabcaf14a/Layout_4.png)
 5. Preencha as informações necessárias:
 	- **Product Cluster Id:** código identificador da coleção. Este campo não deve ser preenchido, pois é gerado automaticamente pelo sistema ao salvar.
 	- **Name:** nome da coleção.
@@ -51,9 +51,9 @@ Para criar um grupo por departamento, categoria ou subcategoria, siga as instru
 
 1. Clique no nome da coleção desejada em **Product Clusters (Collections)**.
 2. Clique no botão `new group`, conforme exemplifica a imagem a seguir.
-	![Layout 5](//images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
+	![Layout 5](https://images.ctfassets.net/alneenqid6w5/5VJuruDOfKeWYG22Kumoy/402839b1a455f205bab5ab01c34c6230/Layout_5.png)
 3. Para acrescentar todos os produtos de um determinado departamento a um grupo, selecione o departamento em questão, como indica a figura a seguir. O mesmo se aplica aos produtos de uma determinada categoria ou subcategoria.
-	![Filtro_por_categoria](//images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
+	![Filtro_por_categoria](https://images.ctfassets.net/alneenqid6w5/ZOZAoB8tWKM4cuYaYw6W2/401a088fe3392fa4b769cc7b667daf77/Filtro_por_categoria.jpg)
 4. Clique em `Salvar Grupo`.
 
 ### Criar grupo por marca
@@ -63,7 +63,7 @@ Para criar um grupo com produtos de uma ou mais marcas, siga as instruções aba
 1. Clique no nome da coleção desejada em **Product Clusters (Collections)**.
 2. Clique no botão `new group`.
 3. Selecione uma ou mais marcas na lista correspondente. As marcas encontram-se dispostas em ordem alfabética. Ao clicar na letra correspondente à inicial da marca, a lista se expande e exibe as marcas existentes.
-  ![FIltro_por_marca](//images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
+  ![FIltro_por_marca](https://images.ctfassets.net/alneenqid6w5/2IsMy84TvOyeKWaKkWAMYS/9af2b71095ed38b958e48976b2415b67/FIltro_por_marca.jpg)
 
 ### Definir grupo por produtos em pré-venda ou em período de lançamento
 
@@ -95,17 +95,17 @@ Quando o número de SKUs na listagem ultrapassar 10 itens, um controle de pagina
 
 Para excluir um SKU da lista, basta clicar no botão vermelho ao lado do SKU correspondente.
 
-  ![Inserir_sku_espec_fico](//images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
+  ![Inserir_sku_espec_fico](https://images.ctfassets.net/alneenqid6w5/u6q7VRW8YSsMs82IICgW6/71728c7bbdd6a12f0bb9c9b5cd84f2f2/inserir-sku-especifico.gif)
 
 ### Importar uma lista de SKUs para o grupo
 
 Apesar dos filtros de grupos serem muito práticos para criar agrupamentos de produtos de forma automática, é possível que eles não atendam as suas necessidades em situações específicas. Para resolver isso, é possível importar uma listagem com os SKUs que farão parte do grupo e consequentemente, da coleção. O módulo de Coleções aceita arquivos nos formatos planilha do Excel (.xls). Todos os IDs dos SKUs devem estar dispostos na primeira coluna, com o cabeçalho, como exemplifica a figura abaixo:
 
-  ![2017-03-08_170117](//images.contentful.com/alneenqid6w5/kZmLZpVL44Uci86aOciEW/a94cb2d1b8cb7e687d1ef625120a1a6b/2017-03-08_170117.jpg)
+  ![2017-03-08_170117](https://images.contentful.com/alneenqid6w5/kZmLZpVL44Uci86aOciEW/a94cb2d1b8cb7e687d1ef625120a1a6b/2017-03-08_170117.jpg)
 
 Depois que a planilha for importada pelo sistema, os SKUs são apresentados da seguinte maneira:
 
-![Importar_lista_de_skus](//images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
+![Importar_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/opkyzS2xKCMecIU0c04Iu/ac8b3e545d02267630712b00b3e532f9/Importar_lista_de_skus.gif)
 
 SKUs que estiverem inativos não terão seus IDs importados mesmo que estejam incluídos na planilha.
 
@@ -117,12 +117,12 @@ SKUs que estiverem inativos não terão seus IDs importados mesmo que estejam in
 
 Para evitar que um administrador tenha que excluir manualmente diversos SKUs, um a um, é possível utilizar o recurso de importação de SKUs da mesma forma que foi exemplificada na seção anterior. Neste caso, depois que o arquivo for carregado, clique na opção `excluir skus`.
 
-![Excluir_lista_de_skus](//images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
+![Excluir_lista_de_skus](https://images.ctfassets.net/alneenqid6w5/7fkP3OAKk0Kq0SYM8aAw6M/37026d5804485392c3dac490adad7b40/Excluir_lista_de_skus.gif)
 
-Obtenha um modelo de arquivo para a importação tanto para inclusão quanto para exclusão de itens na coleção [aqui](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "aqui").
+Obtenha um modelo de arquivo para a importação tanto para inclusão quanto para exclusão de itens na coleção [aqui](https://assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls "aqui").
 
 ### Pesquisar coleções
 
 Quando a quantidade de coleções criadas exceder o limite de exibição, que é de 20 itens, as coleções poderão ser encontradas através do campo de pesquisa. A busca deve ser feita com base no nome da coleção.
 
-![Pesquisar_cole__o](//images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
+![Pesquisar_cole__o](https://images.ctfassets.net/alneenqid6w5/31zMp3YFmUYY0OeyYuIK6I/89e92a9049c0a0af6ce9e7ba6d415e0b/pesquisar_colecao.gif)
diff --git a/docs/tutorials/pt/creating-a-subscription-plan.md b/docs/tutorials/pt/creating-a-subscription-plan.md
index 85cb5fe84..cdc9b7482 100644
--- a/docs/tutorials/pt/creating-a-subscription-plan.md
+++ b/docs/tutorials/pt/creating-a-subscription-plan.md
@@ -92,7 +92,7 @@ Nesta tela, você pode realizar as seguintes ações:
 
 * **Selecionar:** ao clicar no <i class="far fa-square"></i> na linha de cada produto, você pode selecionar produtos ou SKUs individualmente. Outra opção é clicar no primeiro <i class="far fa-square"></i> e selecionar todos os produtos e SKUs exibidos na página para adicioná-los ao plano, conforme ilustrado na imagem abaixo.
 
-![selecionarskus PT](//images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/d5166c26395bfd131c45fe27f51ec5a8/selecionarskus_PT.gif)
+![selecionarskus PT](https://images.ctfassets.net/alneenqid6w5/3nBgV1SCLFqG92L1rOBXOX/d5166c26395bfd131c45fe27f51ec5a8/selecionarskus_PT.gif)
 
 * **Botão** <i class="fas fa-chevron-down"></i>: exibe os SKUs, ou seja, as variações do produto.
 * **Adicionar:** ao clicar neste botão, você adiciona o(s) produto(s) ou SKU(s) ao plano de assinatura.
diff --git a/docs/tutorials/pt/creating-a-subscription-promotion.md b/docs/tutorials/pt/creating-a-subscription-promotion.md
index b58b39bdf..bf6d7359d 100644
--- a/docs/tutorials/pt/creating-a-subscription-promotion.md
+++ b/docs/tutorials/pt/creating-a-subscription-promotion.md
@@ -22,7 +22,7 @@ Neste artigo, você encontrará o passo a passo para criar promoções de assina
 3. Clique no botão `Nova Promoção`.
 4. Selecione o botão `Promoção Regular`.
 5. Selecione o campo **É um pedido de assinatura** na seção **Quais as condições para a promoção ser válida?**. Essa opção define que a promoção será aplicada em pedidos de assinatura. Apenas os produtos com assinatura no carrinho receberão o desconto. Para entender as possibilidades de configuração, veja as condições a seguir:
- ![frequenciapt](//images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/f4eb96b416f69ce48d712463b1d7bd16/image1__2_.png)
+ ![frequenciapt](https://images.ctfassets.net/alneenqid6w5/3H1wS4j8dpkRfI0Le2A2CO/f4eb96b416f69ce48d712463b1d7bd16/image1__2_.png)
 - **Pedido original**: pedidos que geram as assinaturas, mas ainda não fazem parte dos ciclos de assinatura.
 - **Pedidos recorrentes**: pedidos que fazem parte dos ciclos de assinatura.
 - **Filtrar por**: seleção que filtra quais pedidos de assinatura que serão válidos para a promoção.
diff --git a/docs/tutorials/pt/creating-a-type-of-list.md b/docs/tutorials/pt/creating-a-type-of-list.md
index 57d5cf8c1..f2c36a88a 100644
--- a/docs/tutorials/pt/creating-a-type-of-list.md
+++ b/docs/tutorials/pt/creating-a-type-of-list.md
@@ -61,7 +61,7 @@ O lojista decide se a lista terá evento ou não. Uma vez salvo o tipo de lista
 
 Ao selecionar **POSSUI EVENTO**, o formulário disponibiliza outras opções de configuração para o evento, onde será possível configurar todas as datas limites para criação desse tipo de lista, conforme imagem abaixo.
 
-![eventos.pt](//images.ctfassets.net/alneenqid6w5/KhcZ5meUIwnSqBaekhc9C/b8c2b20e083c529a5ae7b4fc63e8a6ab/eventos.pt.png)
+![eventos.pt](https://images.ctfassets.net/alneenqid6w5/KhcZ5meUIwnSqBaekhc9C/b8c2b20e083c529a5ae7b4fc63e8a6ab/eventos.pt.png)
 
 A área de evento é responsável por definir se a lista criada possui ou não um período preestabelecido para a data do evento. Listas de desejo ou listas de compras não necessitam de um período determinado para ocorrência do evento. De forma contrária, listas de casamento ou de chá de bebe, precisam levar em conta a data do evento, para que assim, todos os produtos comprados sejam entregues ao dono em período hábil à data do evento.
 
@@ -79,7 +79,7 @@ As seguintes opções estão disponíveis:
 
 Após a criação do tipo de lista, você será redirecionado para a tela onde aparecem os tipos de listas já cadastrados na loja. Essa tela fornece as seguintes informações e funções:
 
-![listagem.pt](//images.ctfassets.net/alneenqid6w5/5TBHW4MjIqIKMAroEqIKUA/8af47e1d4375b8550a70cb03098adbc0/listagem.pt.png)
+![listagem.pt](https://images.ctfassets.net/alneenqid6w5/5TBHW4MjIqIKMAroEqIKUA/8af47e1d4375b8550a70cb03098adbc0/listagem.pt.png)
 
 - **Exportar para Excel**: Permite exportar os dados de tipos de listas para Excel.
 - **Versão**: Identificação de listas criadas na versão antiga da funcionalidade, com limitações. A versão mais atual é a “v2”.
diff --git a/docs/tutorials/pt/creating-an-oauth2-authentication.md b/docs/tutorials/pt/creating-an-oauth2-authentication.md
index 2bfecaab6..eb9e2adcb 100644
--- a/docs/tutorials/pt/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/pt/creating-an-oauth2-authentication.md
@@ -38,7 +38,7 @@ Você pode consultar o guia oficial do protocolo OAuth2 neste endereço: https:/
 ## Fluxo de integração do OAuth2 com o VTEX ID
 
 Com base na documentação oficial, veja abaixo uma ilustração que explica a integração do OAuth2 com o VTEX ID:
-![oauth2](//images.contentful.com/alneenqid6w5/4Ux3h1bUYMCc6gqaIqo6O6/3e7add68640f1a7f5c6acf74ad4fac36/Fluxo_OAuth2_VTEX_ID.jpg)
+![oauth2](https://images.contentful.com/alneenqid6w5/4Ux3h1bUYMCc6gqaIqo6O6/3e7add68640f1a7f5c6acf74ad4fac36/Fluxo_OAuth2_VTEX_ID.jpg)
 
 A partir dessa ilustração, vamos detalhar os passos a seguir.
 
diff --git a/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
index f293c3058..97d89ab47 100644
--- a/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -22,7 +22,7 @@ Com o fim de aplicar um preço diferenciado a produtos pelo XML, é preciso asso
   2. Clique em `Alterar` no arquivo XML que deseja editar. Caso deseje criar um novo, leia nosso artigo [Configurar XML](https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242).
   3. Aqui, você deve checar se os campos relacionados ao preço do SKU (Menor Preço do Produto, Maior Preço do Produto, Preço Original do SKU, Preço Atual do SKU e Preço Atual do SKU + Taxas) estão preenchidos. Pelo menos um dos campos deve ser preenchido para a operação funcionar corretamente.
   4. Preencha o campo **Tabelas de Preços** com o nome da tabela de preços desejada. Em seguida, clique na caixa de seleção referente à tag na coluna **Exibe Conteúdo**. É necessário que a tabela de preços selecionada tenha preços fixos cadastrados. Caso contrário, a configuração não será realizada.
-![PT-tabela de precos](//images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
+![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
 <div class="alert alert-warning">
   <p>Uma vez que a tabela de preços seja incluída no XML, todos os campos de preço serão sobrescritos.</p>
 </div>
@@ -35,4 +35,4 @@ Após finalizar o cadastro do XML e salvar as alterações, você pode checar as
 
 Exemplo de XML atualizado:
 
-![XML-exemplo](//images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
+![XML-exemplo](https://images.ctfassets.net/alneenqid6w5/6VFUKpMkQdW1mdUTn4XE77/a4d00c7382bb91d26a813eda5946a62d/XML-exemplo.png)
diff --git a/docs/tutorials/pt/creating-collections-beta.md b/docs/tutorials/pt/creating-collections-beta.md
index d2e9259e5..3b2b61ac3 100644
--- a/docs/tutorials/pt/creating-collections-beta.md
+++ b/docs/tutorials/pt/creating-collections-beta.md
@@ -88,23 +88,23 @@ A seleção de produtos pelo Admin VTEX pode ser feita pela lista de produtos, p
 
 Há uma variedade de filtros que podem ser selecionados para reduzir a quantidade de produtos mostrados na lista.
 
-![Coleções-PT](//images.ctfassets.net/alneenqid6w5/1z2kSTLCnZMCyYwaqeopOU/6e80254a130ea6ec1e4ed11663e91219/Screenshot_2020-08-04_Cole____es.png)
+![Coleções-PT](https://images.ctfassets.net/alneenqid6w5/1z2kSTLCnZMCyYwaqeopOU/6e80254a130ea6ec1e4ed11663e91219/Screenshot_2020-08-04_Cole____es.png)
 
 Você pode criar novos filtros a partir de outros critérios que não são abordados nos filtros pré-determinados. As imagens abaixo exemplificam essas opções:
 
-![Novo filtro - PT](//images.ctfassets.net/alneenqid6w5/7s94eqKdl8d3xCPI5wPfOK/d786e39f3886c90831907fc92466f640/Screenshot_14.png)
+![Novo filtro - PT](https://images.ctfassets.net/alneenqid6w5/7s94eqKdl8d3xCPI5wPfOK/d786e39f3886c90831907fc92466f640/Screenshot_14.png)
 
-![Novo filtro detalhes - PT](//images.ctfassets.net/alneenqid6w5/60i6UvQEcghy6zsku1hTia/c158886033e62d698bf043c18d27a659/Screenshot_2020-08-05_Cole____es.png)
+![Novo filtro detalhes - PT](https://images.ctfassets.net/alneenqid6w5/60i6UvQEcghy6zsku1hTia/c158886033e62d698bf043c18d27a659/Screenshot_2020-08-05_Cole____es.png)
 
 Para adicionar um produto à coleção, basta clicar no ícone <i class="fas fa-plus-circle" title = "check em círculo"></i> referente ao produto. Assim, ele será salvo na coleção automaticamente.
 
 Caso deseje mais informações sobre o item, clique no ícone <i class="fas fa-external-link-alt" title = "link externo"></i> para abrir a página de produto ou clique na imagem para ampliá-la.
 
-![PT-colecao-adicionar](//images.ctfassets.net/alneenqid6w5/68r7LGGksNkoM9oqjwStFM/a7ac4e3caea2639e7581bae747f2ee1f/PT-colecao-adicionar.gif)
+![PT-colecao-adicionar](https://images.ctfassets.net/alneenqid6w5/68r7LGGksNkoM9oqjwStFM/a7ac4e3caea2639e7581bae747f2ee1f/PT-colecao-adicionar.gif)
 
 Caso você deseje realizar uma inclusão massiva, aplique pelo menos um dos filtros e clique no botão `Adicionar Todos`. Vale ressaltar que o produto precisa ter pelo menos um SKU cadastrado para ser incluído a uma coleção.
 
-![Coleções Adicionar Todos - PT](//images.ctfassets.net/alneenqid6w5/7Bo9F9fU4sGW4FqBTBquD8/20fa966d9f2bb7339ad12140fc722d2b/Screenshot_22.png)
+![Coleções Adicionar Todos - PT](https://images.ctfassets.net/alneenqid6w5/7Bo9F9fU4sGW4FqBTBquD8/20fa966d9f2bb7339ad12140fc722d2b/Screenshot_22.png)
 
 <div class = "alert alert-danger">
   <p>Não adicione massivamente uma quantidade acima de 100 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.</p>
@@ -120,7 +120,7 @@ Para isso, siga os passos a seguir:
 
   1. No painel da sua coleção, clique no botão `Importar`.  
   2. Clique na opção **Adicionar produtos à coleção** e, em seguida, no botão `Importar`.  
-  3. Clique em **Baixe o modelo** para ter o modelo correto da planilha, como o  exemplo abaixo: ![Coleção planilha - PT](//images.ctfassets.net/alneenqid6w5/2qWba0T6YYLIiwH8vy2JOX/567b23d9479f9e5d8d2929590aa81779/colecao-planilha_-PT.png)
+  3. Clique em **Baixe o modelo** para ter o modelo correto da planilha, como o  exemplo abaixo: ![Coleção planilha - PT](https://images.ctfassets.net/alneenqid6w5/2qWba0T6YYLIiwH8vy2JOX/567b23d9479f9e5d8d2929590aa81779/colecao-planilha_-PT.png)
   4. Preencha a planilha com os IDs ou RefIDs dos Produtos ou dos SKUs. Adicione apenas um ID em cada linha. Independente do ID que você preencher, todos os SKUs do produto selecionado serão adicionados à coleção depois da importação.  
   5. Depois de preencher a planilha, salve as alterações e importe o documento no Admin. Você pode soltar o arquivo na área indicada ou clicar em **Escolha um arquivo**. São aceitos arquivos em formato CSV ou XML. Em caso de um arquivo CSV, use `,` para delimitar os campos.
   6. Para finalizar, clique em `Importar`.
@@ -137,11 +137,11 @@ Os produtos podem ser removidos tanto pela seleção de itens na lista do módul
 
 Para remover um item da coleção, basta clicar no <i class="far fa-check-circle" title="check em círculo"></i> do produto.
 
-![PT-colecao-remover](//images.ctfassets.net/alneenqid6w5/4C7mFX4v4gpVTNV1D9QL2h/e01f7dadd8cedea525b6545eb853a355/PT-colecao-remover.gif)
+![PT-colecao-remover](https://images.ctfassets.net/alneenqid6w5/4C7mFX4v4gpVTNV1D9QL2h/e01f7dadd8cedea525b6545eb853a355/PT-colecao-remover.gif)
 
 Caso você deseje realizar uma remoção massiva, aplique um dos filtros e clique no botão `Remover Todos`.
 
-![Coleções remover filtrados - PT](//images.ctfassets.net/alneenqid6w5/1Ahv25AQ16j2B6zIV7YJrO/0f7aff71f6a25c295315745a69561c1c/Screenshot_23.png)
+![Coleções remover filtrados - PT](https://images.ctfassets.net/alneenqid6w5/1Ahv25AQ16j2B6zIV7YJrO/0f7aff71f6a25c295315745a69561c1c/Screenshot_23.png)
 
 Você também pode clicar no botão <i class="far fa-check-circle" title = "check em círculo"></i> (**Produtos nesta coleção**) na barra superior e depois selecionar `Remover Todos`.
 
@@ -174,7 +174,7 @@ Para alterar a ordem da sua coleção, siga os passos abaixo:
 
   b. Selecione a caixa dos produtos que deseja alterar e clique em `Mover de Posição`. Indique o número da nova posição e, para finalizar, clique em `Mover`. Aqui é possível reordenar massivamente os itens da lista.
 
-![Coleções mover - PT](//images.ctfassets.net/alneenqid6w5/WHrP3DW5rGbyXY40Baixh/4291fbe93c0c64759ca44c07b213146d/Cole____es_mover_-_PT.PNG)
+![Coleções mover - PT](https://images.ctfassets.net/alneenqid6w5/WHrP3DW5rGbyXY40Baixh/4291fbe93c0c64759ca44c07b213146d/Cole____es_mover_-_PT.PNG)
 
 ## Exportar planilha da coleção
 
diff --git a/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md b/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md
index 5fb85c7ff..4e7d61755 100644
--- a/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md
+++ b/docs/tutorials/pt/creating-custom-queries-in-master-data-v1.md
@@ -44,11 +44,11 @@ Siga o passo a passo abaixo para filtrar os registros de um formulário e salvar
 
 Após seguir as instruções acima, a consulta vai aparecer como uma opção de visualização na listagem do formulário.
 
-![consultas-2-pt](//images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/e75d69f663b3042804ad5057c8e66025/consultas-2-pt.png)
+![consultas-2-pt](https://images.ctfassets.net/alneenqid6w5/4x2QAjHSxEZT0RyIUqv5kg/e75d69f663b3042804ad5057c8e66025/consultas-2-pt.png)
 
 Você também pode acessar as consultas salvas clicando no botão Consultas, na listagem do formulário:
 
-![consultas-pt](//images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/85d44e1fe78c43a0e5f5f8d843de9783/consultas-pt.png)
+![consultas-pt](https://images.ctfassets.net/alneenqid6w5/Cj2YVA2pZ64Sscy0O2MA0/85d44e1fe78c43a0e5f5f8d843de9783/consultas-pt.png)
 
 ## Configurar uma consulta padrão
 
diff --git a/docs/tutorials/pt/creating-data-entity.md b/docs/tutorials/pt/creating-data-entity.md
index dcc934377..e14d9e184 100644
--- a/docs/tutorials/pt/creating-data-entity.md
+++ b/docs/tutorials/pt/creating-data-entity.md
@@ -19,7 +19,7 @@ Entidade de dados é uma representação de um conjunto de informações sobre u
 
 Para exemplificar, imagine um sistema de controle de uma biblioteca. Esse sistema controla livros que podem ser alugados por clientes. Então, percebemos que esses 3 conceitos (livro, cliente, aluguel) são entidades que possuem informações sobre cada uma delas. Entidade de dados, portanto, é um grupo de informações sobre determinado conceito.
 
-![exemploBiblioteca](//images.contentful.com/alneenqid6w5/4WFfw93mlykqGCMSyAKcW2/27a0fd02aba4dd22df42a00fd506b75e/new-infographic.png) 
+![exemploBiblioteca](https://images.contentful.com/alneenqid6w5/4WFfw93mlykqGCMSyAKcW2/27a0fd02aba4dd22df42a00fd506b75e/new-infographic.png) 
 
 Com esses conceitos, é possível configurar os mais diversos cenários de controle de dados pelo Master Data. Por padrão, são inseridas as seguintes entidades de dados: Cliente, Endereço, Stores etc. É possível criar quantas mais entidades de dados desejar, possibilitando um ambiente personalizado, voltado às necessidade de cada loja.
 
diff --git a/docs/tutorials/pt/creating-form-in-master-data.md b/docs/tutorials/pt/creating-form-in-master-data.md
index ad73db84b..3ec08d1ec 100644
--- a/docs/tutorials/pt/creating-form-in-master-data.md
+++ b/docs/tutorials/pt/creating-form-in-master-data.md
@@ -40,7 +40,7 @@ Para criar um formulário, siga os passos abaixo:
 
    Se a sigla da entidade __Lista de compras__ for __LC__ e o nome do campo for __Cliente__, deve ser inserido `LC.Cliente` para carregar os atendimentos do cliente que está sendo visualizado no formulário.
 
-   ![registrosRelacionados-pt](//images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/ce0d55331a7bbb03ce1213bb85b7efd0/image_3.png)
+   ![registrosRelacionados-pt](https://images.ctfassets.net/alneenqid6w5/3j6iBpbL7ao6soYaME4e2a/ce0d55331a7bbb03ce1213bb85b7efd0/image_3.png)
 
 Após preencher os campos obrigatórios, aparecerão as abas disponíveis para configuração. Confira abaixo os campos de cada uma delas.
 
diff --git a/docs/tutorials/pt/creating-landing-pages-per-binding.md b/docs/tutorials/pt/creating-landing-pages-per-binding.md
index 438bd5fe2..9200ac398 100644
--- a/docs/tutorials/pt/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/pt/creating-landing-pages-per-binding.md
@@ -23,7 +23,7 @@ No Admin, é possível criar *landing pages* customizadas por [*binding*](https:
 2. Selecione o *binding* no qual deseja criar a nova *landing page* no menu suspenso da página.
 3. Clique no botão `Criar nova`.
 
-  ![pt-landing-page-binding](//images.ctfassets.net/alneenqid6w5/4o8DseduoS1fsMR98iRt1R/8c75f884af19cf8e61e4c4adb1e2a83f/pt-landing-page-binding.png)
+  ![pt-landing-page-binding](https://images.ctfassets.net/alneenqid6w5/4o8DseduoS1fsMR98iRt1R/8c75f884af19cf8e61e4c4adb1e2a83f/pt-landing-page-binding.png)
 
 4. Na seção `Detalhes da página`, preencha os campos e defina os metadados para sua nova *landing page* de acordo com os valores esperados:
 
diff --git a/docs/tutorials/pt/creating-landing-pages.md b/docs/tutorials/pt/creating-landing-pages.md
index a9cc47fe5..d41f5570f 100644
--- a/docs/tutorials/pt/creating-landing-pages.md
+++ b/docs/tutorials/pt/creating-landing-pages.md
@@ -28,7 +28,7 @@ No Admin, você pode criar landing pages personalizadas, como páginas para ofer
 
 2.Clique em **CRIAR PÁGINA**.
 
-![Criando Landing pages](//images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/f9472895136b58039a0f1639a6877652/cms-pages-pt.png)
+![Criando Landing pages](https://images.ctfassets.net/alneenqid6w5/79EZvMxQKLKyE88OxQJudE/f9472895136b58039a0f1639a6877652/cms-pages-pt.png)
 
 3.Na seção Detalhes da página, preencha os campos abaixo para definir os metadados da página:
 
diff --git a/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
index c8376db34..7759c4685 100644
--- a/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
@@ -53,7 +53,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
 
 O Editor visual de regras de merchandising do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
 
-![visual-merch-rules-PT-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
+![visual-merch-rules-PT-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
@@ -89,7 +89,7 @@ O Editor visual de regras de merchandising do VTEX Intelligent Search permite re
 
 O filtro é um atributo selecionável pré-definido que restringe os resultados da busca, por exemplo, possibilitando filtrar por todos os produtos de uma categoria ou marca, entre outras condições. Você pode adicionar uma ou mais condições a um filtro, conforme ilustrado a seguir.
 
-![filtros-merchrules-pt](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
+![filtros-merchrules-pt](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
 
 Para adicionar uma condição no Editor visual, siga o passo a passo abaixo. 
 
diff --git a/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md b/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
index 1b1ed446a..73feaab83 100644
--- a/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
+++ b/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
@@ -49,7 +49,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
 
 O Editor visual de regras de merchandising do VTEX Intelligent Search permite realizar as ações ilustradas na imagem a seguir:
 
-![visual-merch-rules-PT-v2](//images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
+![visual-merch-rules-PT-v2](https://images.ctfassets.net/alneenqid6w5/1wQEvrFFEp5ixHPCVtHsxa/a69e5c51be97c266e1ac0ad5404fde03/visual-merch-rules-PT-v2.png)
 
 <ol class="mv7" type="I">
     <li class="t-body c-on-base mb5 lh-copy">Editar nome da regra de merchandising.</li>
@@ -85,7 +85,7 @@ O Editor visual de regras de merchandising do VTEX Intelligent Search permite re
 
 O filtro é um atributo selecionável pré-definido que restringe os resultados da busca, por exemplo, possibilitando filtrar por todos os produtos de uma categoria ou marca, entre outras condições. Você pode adicionar uma ou mais condições a um filtro, conforme ilustrado a seguir.
 
-![filtros-merchrules-pt](//images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
+![filtros-merchrules-pt](https://images.ctfassets.net/alneenqid6w5/5e2KtHyjaAmvBqRDaJe8EK/f8e0a4b955d517db17268eb1bdff6aa4/image2.gif)
 
 Para adicionar uma condição no Editor visual, siga o passo a passo abaixo. 
 
diff --git a/docs/tutorials/pt/creating-price-tables.md b/docs/tutorials/pt/creating-price-tables.md
index 128c07767..fa7f24a13 100644
--- a/docs/tutorials/pt/creating-price-tables.md
+++ b/docs/tutorials/pt/creating-price-tables.md
@@ -23,7 +23,7 @@ Para criar uma Tabela de Preços siga os seguintes passos:
 4. Escolha o nome da tabela de preços que deseja criar.
 5. Clique no botão **Criar tabela de preços**
 
-![criar-tabela-de-precos](//images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/9e1cb714619aad7cecfac327a7240277/criar-tabela-precos.gif)
+![criar-tabela-de-precos](https://images.ctfassets.net/alneenqid6w5/1aG692obTeP7RMdEQd7jGE/9e1cb714619aad7cecfac327a7240277/criar-tabela-precos.gif)
 
  Para encontrar uma Tabela de Preço:
 
diff --git a/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
index 0041b33d6..b59d3d213 100644
--- a/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
@@ -62,9 +62,9 @@ Na configuração abaixo, por exemplo, apenas registros `funcionario` com o valo
 
 Dessa forma, você poderia configurar também `funcionario=false`, em que apenas registros `funcionario` com valor `false` no campo receberiam a promoção.
 
-![Campo funcionário Master Data PT](//images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/06fd3f196a18b3d331742a01bb4ef2d6/Campo_funcion__rio_Master_Data_PT.png)
+![Campo funcionário Master Data PT](https://images.ctfassets.net/alneenqid6w5/1GQftbj5FuIiQ4mUweacwa/06fd3f196a18b3d331742a01bb4ef2d6/Campo_funcion__rio_Master_Data_PT.png)
 
-![Cluster de clientes PT](//images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/c1d0536a53150d809b8c6c74b5a81b12/Cluster_de_clientes_PT.png)
+![Cluster de clientes PT](https://images.ctfassets.net/alneenqid6w5/1IOHFLD9w840WEuceWMk4Q/c1d0536a53150d809b8c6c74b5a81b12/Cluster_de_clientes_PT.png)
 
 Considerando um campo do tipo **[Varchar](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos)**, poderíamos configurar `funcionario="sim"` para que apenas clientes com valor `"sim"` no campo recebessem a promoção.
 
@@ -82,8 +82,8 @@ A expressão `{nomedapropriedade} contains {valor}` deve ser utilizada quando a
 
 Por exemplo, caso você queira criar um cluster apenas com clientes cujos emails contenham `@teste.com`, a configuração seria igual à representada na imagem abaixo.
 
-![Campo Email Master Data](//images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
+![Campo Email Master Data](https://images.ctfassets.net/alneenqid6w5/5aeXd0Ro72P1GlzVeBiVVZ/4bfb1189f8f967ef9ed77e081291931b/Campo_Email_Master_Data.png)
 
-![cluster email PT](//images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/271cdcec5cdf081311215a57cfa2994c/cluster_email_PT.PNG)
+![cluster email PT](https://images.ctfassets.net/alneenqid6w5/5LKj1wrG3zL54lfh4R2MzQ/271cdcec5cdf081311215a57cfa2994c/cluster_email_PT.PNG)
 
 Nesse caso, `email contains test.com` será verdadeiro, por exemplo, quando o valor for `joao@test.com` e falso quando o valor for `joao@test.org`.
diff --git a/docs/tutorials/pt/creating-promotions.md b/docs/tutorials/pt/creating-promotions.md
index 7d5b819de..b9f116d89 100644
--- a/docs/tutorials/pt/creating-promotions.md
+++ b/docs/tutorials/pt/creating-promotions.md
@@ -85,7 +85,7 @@ Para buscar uma promoção, siga os passos abaixo:
 
 O agendamento de uma promoção ocorre quando esta é criada (ou alterada) com data e hora de validade posteriores ao momento atual . Lembrando que o horário considerado é o do sistema do computador no qual a promoção foi criada, desconsiderando-se ajustes de fuso horário.
 
-Essas promoções podem ser facilmente identificadas na página principal de Promoções, visto que possuem uma tarja laranja no canto superior direito da ficha, com a palavra agendada, como mostra o exemplo a seguir:![agendada](//images.contentful.com/alneenqid6w5/illvXlc6M10IO8p8IfL7J/5006d8b3f6d996abf06bfb0fdc248623/agendada.png)
+Essas promoções podem ser facilmente identificadas na página principal de Promoções, visto que possuem uma tarja laranja no canto superior direito da ficha, com a palavra agendada, como mostra o exemplo a seguir:![agendada](https://images.contentful.com/alneenqid6w5/illvXlc6M10IO8p8IfL7J/5006d8b3f6d996abf06bfb0fdc248623/agendada.png)
 
 Para agendar uma promoção, siga os passos da seção [Agendar promoções](https://help.vtex.com/pt/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI?&utm_source=autocomplete#agendar-promocoes) do artigo [Agendamento para eventos especiais](https://help.vtex.com/pt/tutorial/agendamento-para-eventos-especiais--2nd50tPWdKK4waXRZLg0JI)
 
diff --git a/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
index 302ade034..32a5de438 100644
--- a/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
@@ -48,7 +48,7 @@ Confira o passo a passo a seguir, ilustrado com esse exemplo:
 8. Clique no ícone de engrenagem <i class="fas fa-cog"></i> ao lado do campo de **Relacionamento** para configurá-lo.
 9. Em **Configurações de campo personalizado**, selecione a entidade à qual deseja fazer referência e o campo que será mostrado no relacionamento. Neste exemplo, o relacionamento será feito com a entidade **Cliente** e será exibido o campo **email**.
 
-   ![Relacionamento entidade Lista de Compras](//images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
+   ![Relacionamento entidade Lista de Compras](https://images.ctfassets.net/alneenqid6w5/3YjtdLHluQz9ve11TkmylY/41cb881fc6bfe93744e4a68cca8ea43a/Lista_Compras_Relacionamento.png)
 
 10. Clique no botão `Salvar` para salvar as configurações.
 11. Clique no ícone de publicação <i class="fas fa-save"></i> para publicar a entidade.
@@ -85,7 +85,7 @@ Confira o passo a passo a seguir:
 
 Agora, ao criar um novo documento a partir do formulário, você pode selecionar o valor desejado (neste exemplo, o Cliente preexistente que irá se relacionar com a Lista de Compras):
 
-![Selecionar relacionamento de documento Master Data](//images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
+![Selecionar relacionamento de documento Master Data](https://images.ctfassets.net/alneenqid6w5/6Ss4S4Be4qRqNKLWBz51KF/a913e0402c87456ab9ca07e7431d4eac/Selecionar_relacionamento_de_documento_Master_Data.png)
 
 Além do relacionamento, é possível também visualizar os registros relacionados ao visualizar cada registro de uma entidade, por exemplo, visualizar as ‘Lista de compras’ criadas por um ‘Cliente’ ao consultar o registro do cliente.
 
@@ -95,6 +95,6 @@ Para isso, você precisa adicionar ao formulário da entidade o valor `{acronimo
 
 Os relacionamentos são mantidos através dos IDs dos documentos. Então, ao tentar inserir o valor do campo de relacionamento como filtro no formulário, obteremos apenas os valores dos IDs dos documentos referidos, e não os valores do campo escolhido para cada documento. As duas figuras abaixo mostram esse resultado. Veja mais informações no artigo [Filtrar dados no Master Data](https://help.vtex.com/pt/tutorial/filtrando-dados-no-master-data--tutorials_778).
 
-![Selecionar filtro relacionamento](//images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
+![Selecionar filtro relacionamento](https://images.ctfassets.net/alneenqid6w5/Kh7PNTktepTfJn4s5AQlI/cc64d40a1bcfcd5b508dae36b7ee80cd/Selecionar_filtro_relacionamento.png)
 
-![Filtro relacionamento ID](//images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
+![Filtro relacionamento ID](https://images.ctfassets.net/alneenqid6w5/4O1qpGWOrnnM3Zzmyqzymu/a9e179027658143481e6a6f3444e24cd/Filtro_relacionamento_ID.png)
diff --git a/docs/tutorials/pt/creating-roles.md b/docs/tutorials/pt/creating-roles.md
index 2042365a1..2f93ca917 100644
--- a/docs/tutorials/pt/creating-roles.md
+++ b/docs/tutorials/pt/creating-roles.md
@@ -45,13 +45,13 @@ Para começar a utilizar um perfil de acesso predefinido, siga as instruções a
 
     Por exemplo, o perfil **Call center operator** contém um recurso do produto _Catálogo_ que permite executar operações numa loja em nome de um cliente e um recurso do _OMS_ que permite checar o status de um pedido:
 
-    ![Novo perfil de acesso](//images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/1fe552a5c15c7c3dee8d54c88a60fafc/image_3.png)
+    ![Novo perfil de acesso](https://images.ctfassets.net/alneenqid6w5/5biL3DriciSnHKbgHvV2PE/1fe552a5c15c7c3dee8d54c88a60fafc/image_3.png)
 
     Saiba mais sobre os perfis predefinidos disponíveis e os recursos associados em [Perfis de acesso predefinidos](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy).
 
 4. Adicione usuários administrativos ao perfil de acesso, preenchendo o email do usuário a ser inserido em **Adicionar usuários para este perfil de acesso** e clicando em `Adicionar`.
 
-    ![Usuários do perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/59aaf0ef06ddcb1a4b48c47647d68f2d/usuarios-es.PNG)
+    ![Usuários do perfil](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/59aaf0ef06ddcb1a4b48c47647d68f2d/usuarios-es.PNG)
 
     Se o usuário não existir, será criado um novo usuário usando o email como nome, ou seja, nome e email serão iguais.
 
@@ -71,7 +71,7 @@ Para criar  um perfil de acesso personalizado para atender as necessidades de ac
 
     Você verá a lista de todos os recursos disponíveis para o produto:
 
-    ![Configurando produto](//images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/39bc16eca81b8a13946f081c5a1454d3/image_4.png)
+    ![Configurando produto](https://images.ctfassets.net/alneenqid6w5/1VE4awGJHyrsR2OkYwAzRQ/39bc16eca81b8a13946f081c5a1454d3/image_4.png)
 
 5. Marque os recursos aos quais o perfil deve conceder acesso. Confira a lista completa de [Recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) para mais informações sobre cada um.
 6. Caso deseje adicionar recursos de outro produto, clique no botão **Configurar outro produto**, ao final da lista de produtos e recursos e repita os passos 4 e 5.
@@ -86,7 +86,7 @@ Para criar  um perfil de acesso personalizado para atender as necessidades de ac
 
 8. Adicione usuários administrativos ao perfil de acesso, preenchendo o email do usuário a ser inserido em **Adicionar usuários para este perfil de acesso** e clicando em `Adicionar`.
 
-    ![Usuários do perfil](//images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/59aaf0ef06ddcb1a4b48c47647d68f2d/usuarios-es.PNG)
+    ![Usuários do perfil](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/59aaf0ef06ddcb1a4b48c47647d68f2d/usuarios-es.PNG)
 
     Se o usuário não existir, será criado um novo usuário usando o email como nome, ou seja, nome e email serão iguais.
 
diff --git a/docs/tutorials/pt/creating-service-for-a-sku.md b/docs/tutorials/pt/creating-service-for-a-sku.md
index 4a774310a..f38a45e72 100644
--- a/docs/tutorials/pt/creating-service-for-a-sku.md
+++ b/docs/tutorials/pt/creating-service-for-a-sku.md
@@ -80,7 +80,7 @@ Para vincular um serviço a um SKU, siga os passos abaixo:
   <p>O tamanho do arquivo da planilha não poderá exceder 4Mb (4096KB).</p>
 </div>
 8. Clique na barra ao lado do botão `Select`, destacada abaixo.
-  ![Anexos - PT](//images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/8581377e9a02b411cd383a85be145983/image.png)
+  ![Anexos - PT](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/8581377e9a02b411cd383a85be145983/image.png)
 9. Selecione a planilha CSV atualizada.
 10. Clique em `Vincular Valor(es) de Serviço(s) a SKU(s)` para finalizar.
 
diff --git a/docs/tutorials/pt/creating-surchargestaxes.md b/docs/tutorials/pt/creating-surchargestaxes.md
index deb52d66c..88d5325c5 100644
--- a/docs/tutorials/pt/creating-surchargestaxes.md
+++ b/docs/tutorials/pt/creating-surchargestaxes.md
@@ -59,4 +59,4 @@ A taxa é aplicada conforme o cadastro que é feito no seller. Então se no car
 
 O agendamento de uma taxa ocorre quando é criada ou alterada com data e hora de validade com início posterior ao atual. Visualmente é possível identificar essas taxas na página principal do módulo de Taxas & Promoções, através de uma tarja laranja no canto superior direito do cartão da taxa, com a palavra agendada. Veja abaixo um exemplo de como fica o cartão de uma taxa quando agendada.
 
-![agendamento.pt](//images.ctfassets.net/alneenqid6w5/79wklIdW9FLzJZb8e4rxc0/6214e94e10b4df0cc4b07b7cc81e52f9/agendamento.pt.png)
+![agendamento.pt](https://images.ctfassets.net/alneenqid6w5/79wklIdW9FLzJZb8e4rxc0/6214e94e10b4df0cc4b07b7cc81e52f9/agendamento.pt.png)
diff --git a/docs/tutorials/pt/creating-the-category-tree.md b/docs/tutorials/pt/creating-the-category-tree.md
index f46ebae13..ff0a3108b 100644
--- a/docs/tutorials/pt/creating-the-category-tree.md
+++ b/docs/tutorials/pt/creating-the-category-tree.md
@@ -18,4 +18,4 @@ subcategory: 1E7tziZCkY4w8i4EmUuwec
 A árvore de categorias é a relação de categorias que será utilizada em seu site. Os níveis são: departamento, categoria e subcategoria. Um nível mais específico do que o outro.
 
 [A definição de sua árvore de categorias](/tutorial/cadastrando-categoria/ "A definição de sua árvore de categorias") deve ser realizado no início do projeto e deve ser bem planejada, pensando em seu catálogo de produtos e em seu SEO.
-<video class="wp-video-shortcode" id="video-2565-8" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4?_=8" />[//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4](//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4 "//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4")</video>
+<video class="wp-video-shortcode" id="video-2565-8" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4?_=8" />[//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4](https://assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4 "//assets.contentful.com/alneenqid6w5/5EVmpjIxSECYa4okIyGsae/18e869041abb873483641b0a04fa93df/CriandoArvoreCategorias-1.mp4")</video>
diff --git a/docs/tutorials/pt/creating-trigger-in-master-data.md b/docs/tutorials/pt/creating-trigger-in-master-data.md
index 9741aa5f4..da3df8f68 100644
--- a/docs/tutorials/pt/creating-trigger-in-master-data.md
+++ b/docs/tutorials/pt/creating-trigger-in-master-data.md
@@ -44,7 +44,7 @@ As principais características dos triggers são:
 
 Antes de [criar um trigger](#configurar-um-trigger), é necessário compreender que a configuração de um trigger se dá por quatro partes, explicadas a seguir.
 
-![trigger](//images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/f093dfa7ef956882313f224afe0e4dd0/trigger.png)
+![trigger](https://images.ctfassets.net/alneenqid6w5/5WbC7SD6aPFqaOHuHWgQoq/f093dfa7ef956882313f224afe0e4dd0/trigger.png)
 
 ### Ação que dispara o trigger
 
@@ -121,7 +121,7 @@ Aqui, você deve definir as condições que vão disparar o(s) evento(s) configu
 
    Selecione quais são os campos e quais os valores aceitos ou não para que o trigger seja disparado.
 
-   ![filters-pt](//images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/34cbeea173c7f4944ee87c22eb406c02/filters-pt.png)
+   ![filters-pt](https://images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/34cbeea173c7f4944ee87c22eb406c02/filters-pt.png)
 
 <div class="alert alert-info">
   <p>O Master Data v1 não permite configuração de retentativas de trigger, diferente do Master Data v2.</p>
@@ -143,7 +143,7 @@ Nesta aba, você deve configurar os eventos a serem disparados caso o registro q
 
 Envia um email para destinatários dinâmicos (contidos no registro) ou estáticos. O email a ser enviado é  personalizado, podendo ser um texto, HTML ou até mesmo o conteúdo de uma URL. É possível inserir anexos e o campo **Tags válidas** mostra como inserir valores de campos do registro.
 
-![send-email-pt](//images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/9467386aa32cf4f3338e8d33f9a68fef/send-email-pt.png)
+![send-email-pt](https://images.ctfassets.net/alneenqid6w5/KsQUtktQoECEMiKEY6EU8/9467386aa32cf4f3338e8d33f9a68fef/send-email-pt.png)
 
 #### Enviar um email usando um modelo do VTEX Message Center
 
@@ -159,7 +159,7 @@ Envia uma requisição HTTP com a possibilidade de salvar informações da respo
 
 Preencha a seção **Informações da solicitação** com as informações da requisição a ser enviada. Na seção **Ação de resposta**, você poderá indicar como as informações da resposta deverão ser salvas no Master Data.
 
-![http-request-pt](//images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/7bbe43cc3c3e54a23ba82dca1e21ef19/http-request-pt.png)
+![http-request-pt](https://images.ctfassets.net/alneenqid6w5/5uIXuDHBecTzuJxi0mnjWv/7bbe43cc3c3e54a23ba82dca1e21ef19/http-request-pt.png)
 
 Para configurar a **Ação de resposta**, selecione a entidade de dados desejada e defina, para cada campo a ser salvo, o caminho JSON correspondente na resposta.
 
diff --git a/docs/tutorials/pt/creating-your-promotions.md b/docs/tutorials/pt/creating-your-promotions.md
index 6a101a6e5..38d9094ef 100644
--- a/docs/tutorials/pt/creating-your-promotions.md
+++ b/docs/tutorials/pt/creating-your-promotions.md
@@ -17,4 +17,4 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 
 A [criação de promoções](http://help.vtex.com/tutorial/como-criar-promocoes/ "criação de promoções") não é um passo obrigatório para a subida da loja mas é largamente utilizada pelas lojas e, por isso, está em nosso primeiros passos. Aproveite e configure uma promoção de lançamento. 😋
 
-<video class="wp-video-shortcode" id="video-2576-3" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4?_=3" />[//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4](//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4 "//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4")</video>
+<video class="wp-video-shortcode" id="video-2576-3" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4?_=3" />[//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4](https://assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4 "//assets.contentful.com/alneenqid6w5/6zNzPP4ZuEkUWEK4cIO2UO/61cd3b64aa45b98ace5595dd5a265ae2/CriandoPromocao.mp4")</video>
diff --git a/docs/tutorials/pt/credit-card-basic-payment-flow.md b/docs/tutorials/pt/credit-card-basic-payment-flow.md
index 4b67345f5..a80df1528 100644
--- a/docs/tutorials/pt/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/pt/credit-card-basic-payment-flow.md
@@ -17,7 +17,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 Este artigo tem como objetivo explicar como funciona o fluxo básico de um pagamento por __cartão de crédito__:
 
-![Credit Card Flow](//images.contentful.com/alneenqid6w5/3oIzDRDSwgUQAqUEosW60k/12408bd338f44d41180cd5e71131d341/Credit_Card_Flow.jpg)
+![Credit Card Flow](https://images.contentful.com/alneenqid6w5/3oIzDRDSwgUQAqUEosW60k/12408bd338f44d41180cd5e71131d341/Credit_Card_Flow.jpg)
 
 1. Na tela de Checkout, o cliente escolhe o __Meio de Pagamento__ cartão de crédito para realizar o pagamento de sua compra.
 2. As informações deste pagamento são passadas para o __Gateway de Pagamentos__. O [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) é o player responsável por garantir que este pagamento seja realizado com sucesso.
diff --git a/docs/tutorials/pt/credit-control-overview.md b/docs/tutorials/pt/credit-control-overview.md
index d6148be86..19f80b372 100644
--- a/docs/tutorials/pt/credit-control-overview.md
+++ b/docs/tutorials/pt/credit-control-overview.md
@@ -35,7 +35,7 @@ Por isso criamos o Credit Control – para que o controle de crédito seja feito
 
 ## Como funciona
 
-![Fluxo básico do Credit Control](//images.contentful.com/alneenqid6w5/35jUk6EVksKUQi8EaU6caO/aa5ac9a4af1c972a8bba3cc10ab347b8/credit-control-flow_pt.gif)
+![Fluxo básico do Credit Control](https://images.contentful.com/alneenqid6w5/35jUk6EVksKUQi8EaU6caO/aa5ac9a4af1c972a8bba3cc10ab347b8/credit-control-flow_pt.gif)
 
 *Fluxo básico de como funciona o Credit Control nas lojas VTEX.*
 
diff --git a/docs/tutorials/pt/criar-um-produto-beta.md b/docs/tutorials/pt/criar-um-produto-beta.md
index 36673f385..5e2b512fb 100644
--- a/docs/tutorials/pt/criar-um-produto-beta.md
+++ b/docs/tutorials/pt/criar-um-produto-beta.md
@@ -39,7 +39,7 @@ Feito isso, o produto será ativado e estará disponível na sua loja.
 Nesta aba, você vai realizar o cadastro do produto preenchendo os campos descritos abaixo com as características do item.
 
 ## Informações gerais
-![image9](//images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
+![image9](https://images.ctfassets.net/alneenqid6w5/zuDEylLB51jEYDgupvInT/3cbd44a15e049422865dadb7169d0c38/image9.png)
 
 - **Nome**: informe o título do produto na loja. Use palavras simples e evite outros idiomas ou escrita complexa. Esse campo é importante para SEO e deve respeitar o limite de 150 caracteres. Campo obrigatório. 
 **Exemplo**: Tênis Esportivo Ultralight.
@@ -56,7 +56,7 @@ Nesta etapa, você precisa escrever uma descrição das principais informações
 
 O editor de texto da descrição é do tipo rich text, ou seja, você pode utilizar diversos recursos de formatação utilizando a barra de ferramentas desse campo, ilustrada abaixo.
 
-![image10](//images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
+![image10](https://images.ctfassets.net/alneenqid6w5/15nJVdLeSo0trgDc5czwl3/6796616b891c91907787537076bd12d9/image10.gif)
 Veja quais são os recursos disponíveis a partir da barra de ferramentas:
 
 - **Estilos**: define o estilo do texto selecionado. As opções são: Normal e Título 1 até Título 6.
@@ -75,7 +75,7 @@ Veja quais são os recursos disponíveis a partir da barra de ferramentas:
 - **Abrir em uma nova aba**: selecione esta opção se você deseja que, ao clicar no link, o usuário abra a página em uma nova aba do navegador. Não selecione se o objetivo for que o usuário acesse o link na mesma aba.
 - **Código-fonte**: exibe o código fonte da descrição em HTML. Você pode editar a descrição diretamente pelo código-fonte, se desejar. Para retornar à visão anterior, é necessário clicar novamente no botão referente ao código-fonte.
 ## SEO
-![image11](//images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
+![image11](https://images.ctfassets.net/alneenqid6w5/3JJ2gdAtrSYY4Xo8V83IUf/799e31402321a340e5978c3a2d621f7a/image11.png)
 -  **URL do produto**: insira a URL pela qual será possível acessar o produto na loja. Neste campo, você não pode utilizar espaço nem caracteres especiais. Caso a URL seja composta por mais de uma palavra, você precisa separá-las com um `-`. Campo obrigatório. **Exemplo**: tenis-esportivo-ultralight.
 
 - **Título da página**: escreva o título da página do produto. Para otimizar a classificação do seu produto nos resultados de busca, o ideal é não ultrapassar 60 caracteres. Campo obrigatório. **Exemplo**: Tênis Esportivo Ultralight.
@@ -83,14 +83,14 @@ Veja quais são os recursos disponíveis a partir da barra de ferramentas:
 - **Meta descrição**: escreva o título da página do produto. Para otimizar a classificação do seu produto nos resultados de busca, o ideal é não ultrapassar 60 caracteres. Campo obrigatório. **Exemplo**: Conheça o Tênis Esportivo Ultralight da SportXtreme, perfeito para atletas que buscam leveza e desempenho máximo nas atividades esportivas.
 
 ## Operação e logística
-![image7](//images.ctfassets.net/alneenqid6w5/7u4kwyRsDBKFi1WVu5nV2q/3372b498b4d49932670575ea0b8211ab/image7.png)
+![image7](https://images.ctfassets.net/alneenqid6w5/7u4kwyRsDBKFi1WVu5nV2q/3372b498b4d49932670575ea0b8211ab/image7.png)
 
 - **Políticas comerciais**: selecione uma ou mais políticas comerciais a que o produto se destina, para definir a quais marketplaces o produto será disponibilizado. Caso nenhuma política comercial seja selecionada, o produto vai ser considerado para todas elas. **Exemplo**: B2C.
 - **Fornecedor**: selecione um fornecedor já cadastrado na loja para relacionar ao produto.
 - **Código fiscal**: informe o número de identificação fiscal do produto.
 
 ## Visibilidade
-![image4](//images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)
+![image4](https://images.ctfassets.net/alneenqid6w5/3CygKnTtnLKzlR5Ci2nHdf/f26b3307479a762ad14f858e033a060b/image4.png)
 
 - **Mostrar no site**: ative ou desative a visibilidade do produto na sua loja. Caso o produto seja um brinde que não pode ser comprado, por exemplo, é importante desativar esta opção.
 - **Mostrar quando fora de estoque**: ative ou desative a opção de mostrar o produto na loja mesmo quando não houver quantidade em estoque. Se ativada, o produto esgotado aparece na sua loja no formato de [Avise-me](https://help.vtex.com/pt/tutorial/configurar-a-opcao-avise-me--2VqVifQuf6Co2KG048Yu6e) — campo em que o cliente informa seu email para ser avisado quando o produto estiver novamente disponível. Se essa opção for desativada, o produto não vai aparecer na loja quando estiver esgotado.
@@ -104,7 +104,7 @@ Se você tiver criado algum campo de produto obrigatório, o produto só poderá
 
 Em Atributos, será exibido os [grupos de especificações](https://help.vtex.com/pt/tutorial/criando-grupo-de-especificacoes-em-uma-categoria--tutorials_246) com as especificações cadastradas abaixo. Na imagem a seguir, o grupo de especificação é **Características** e as especificações cadastradas nele são **Vídeo** e **Veja Mais**.
 
-![image3](//images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
+![image3](https://images.ctfassets.net/alneenqid6w5/tp3ppbjPs7mbSo29DAXwI/946499d76c27c99034f37132b0c6d9fa/image3.png)
 
 ## SKUs
 
@@ -117,7 +117,7 @@ Para um produto disponível na sua loja, ele deve ter pelo menos um SKU ativo. 
 Aqui serão exibidas as especificações criadas anteriormente para os SKUs. Se você tiver criado algum campo de SKU obrigatório, o SKU só poderá ser ativado após o preenchimento desta especificação. 
 
 ## Informações básicas
-![image2](//images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
+![image2](https://images.ctfassets.net/alneenqid6w5/48TmuJ985SApT2gwx7IOCW/e08a3e7ece4f6872b7dff3418ad0d297/image2.png)
 - **Nome**: nome do SKU. Este nome será exibido na loja. Campo obrigatório.
 - **Código de referência**: código que será utilizado internamente pela loja para identificar o SKU. Campo obrigatório caso o SKU não tenha EAN/UPC preenchido.
 - **EAN/UPC**: campo que deve conter a informação do código de barras. Campo obrigatório caso o SKU não tenha o Código de referência preenchido.
@@ -131,8 +131,8 @@ Aqui serão exibidas as especificações criadas anteriormente para os SKUs. Se
 
 Para adicionar uma imagem a seu SKU, siga os passos abaixo:
 
-1. Clique no botão `+`.![image8](//images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
-2. Adicione o link da sua imagem no campo 🔗. Você pode adicionar mais de uma imagem ano seu SKU. Para isso, clique em + Adicionar imagem e adicione o novo link.![image6](//images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
+1. Clique no botão `+`.![image8](https://images.ctfassets.net/alneenqid6w5/4cT5SMN8xz8S7dJYaGxVDf/11da22617b306323a5ce39d781edbb14/image8.png)
+2. Adicione o link da sua imagem no campo 🔗. Você pode adicionar mais de uma imagem ano seu SKU. Para isso, clique em + Adicionar imagem e adicione o novo link.![image6](https://images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
 3. Clique em `Salvar`.
 
 <div class="alert alert-info"> A primeira imagem adicionada será a imagem principal do SKU que será exibida na loja e nos resultados de busca. </div>
@@ -143,7 +143,7 @@ Também é possível deletar uma imagem clicando no botão <i class="fas fa-elli
 
 ## Pesos e medidas
 - **Peso e dimensões para frete**:
- ![image1](//images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
+ ![image1](https://images.ctfassets.net/alneenqid6w5/22wJdRKOCeuO8vegdPncfH/755f8b2ea63544951edf6c52c3670a6b/image1.png)
 
 - **Peso do pacote**: peso do pacote vazio em quilos. Campo obrigatório.
 - **Largura do pacote**: largura do pacote em centímetros. Campo obrigatório.
@@ -164,7 +164,7 @@ Também é possível deletar uma imagem clicando no botão <i class="fas fa-elli
 - **Multiplicador de unidade**: unidade numérica que multiplica a quantidade selecionada do produto ao ser inserido no carrinho. Caso o multiplicador seja 5, o produto será adicionado em quantidades múltiplas de 5, ou seja 5, 10, 15, 20, e assim porem diante. 
 
 ## Configurações avançadas
-![image5](//images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
+![image5](https://images.ctfassets.net/alneenqid6w5/3Rk6yBkgQ04TpuyfBOm45H/c0b79e55d74086b471ad54e1e8238e85/image5.png)
 
 - **Ativar kit**: determina se os SKUs que compõem um kit só podem ser vendidos juntos. Você pode fazer com que o SKU faça parte de um kit <i class="fas fa-toggle-on"></i> ou não <i class="fas fa-toggle-off"></i>.
 
diff --git a/docs/tutorials/pt/crm-zen-suiteshare.md b/docs/tutorials/pt/crm-zen-suiteshare.md
index a1868d800..bb2bd0d16 100644
--- a/docs/tutorials/pt/crm-zen-suiteshare.md
+++ b/docs/tutorials/pt/crm-zen-suiteshare.md
@@ -21,17 +21,17 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **CRM Zen**.
 
-   ![CRM Zen_1](//images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
+   ![CRM Zen_1](https://images.ctfassets.net/alneenqid6w5/6E4NMmioOrA8OupyVt9t8R/997fa4ac57496b21bbad96c2476b4b84/CRM_Zen_1.png)
 
 2. Acesse **Configurações > Integrações > Vendas > CRM Zen > Habilitar**.
 
-   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
-   ![CRM Zen_3](//images.ctfassets.net/alneenqid6w5/5r5pR9IWVJ38GAoO7q7YeR/d03a734f6b33423349984d6b762995a7/CRM_Zen_3.png)
+   ![CRM Zen_3](https://images.ctfassets.net/alneenqid6w5/5r5pR9IWVJ38GAoO7q7YeR/d03a734f6b33423349984d6b762995a7/CRM_Zen_3.png)
 
 O próximo passo, é acessar o **CRM Zen** e realizar o login na sua conta.
 
-![CRM Zen_4](//images.ctfassets.net/alneenqid6w5/zyC2JfLz9tZQfbqbkosuy/13fd076b9182d8236f5a314e4ec617dd/CRM_Zen_4.png)
+![CRM Zen_4](https://images.ctfassets.net/alneenqid6w5/zyC2JfLz9tZQfbqbkosuy/13fd076b9182d8236f5a314e4ec617dd/CRM_Zen_4.png)
 
 Agora, dentro da plataforma CRM Zen localize os tokens, clicando no ícone de engrenagem e selecionando **Integração**.
 
@@ -39,7 +39,7 @@ Com as informações do **Token de integração** e/ou o de **notas** (e todos
 
 Após localizar o **CRM Zen** e acessar a opção **Habilitar**, é preciso configurar a integração para cada formulário de captura criado. Para isso, selecione o link de captura em **Selecione**.
 
-![CRM Zen_5](//images.ctfassets.net/alneenqid6w5/4XA4qcTFMx1SzII6oqyTB7/2638f1e3b4e8903dd0fabe6bd0f3e932/CRM_Zen_5.png)
+![CRM Zen_5](https://images.ctfassets.net/alneenqid6w5/4XA4qcTFMx1SzII6oqyTB7/2638f1e3b4e8903dd0fabe6bd0f3e932/CRM_Zen_5.png)
 
 O próximo passo, é configurar o **Tipo de integração**, preencher o **Token de integração** e configurar o **Compartilhamento (opcional)**, conforme a estratégia da sua Empresa.
 
diff --git a/docs/tutorials/pt/customer-credit-overview.md b/docs/tutorials/pt/customer-credit-overview.md
index 3e22fed1d..03c5ded50 100644
--- a/docs/tutorials/pt/customer-credit-overview.md
+++ b/docs/tutorials/pt/customer-credit-overview.md
@@ -40,7 +40,7 @@ Quando instalado, o Customer Credit aparece como uma opção de pagamento no Che
 
 Veja abaixo o fluxo básico de funcionamento do Customer Credit nas lojas VTEX:
 
-![GIF_CC_PT](//images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/4aa3ae0434d69c91f827675128a5ae13/GIF_CC_PT.gif)
+![GIF_CC_PT](https://images.ctfassets.net/alneenqid6w5/6e4DmVcrW4FCvZgrhOYQDe/4aa3ae0434d69c91f827675128a5ae13/GIF_CC_PT.gif)
 
 ## Definições no Customer Credit
 
diff --git a/docs/tutorials/pt/customize-suiteshare.md b/docs/tutorials/pt/customize-suiteshare.md
index 0094e43ee..fd9dfa0ca 100644
--- a/docs/tutorials/pt/customize-suiteshare.md
+++ b/docs/tutorials/pt/customize-suiteshare.md
@@ -17,15 +17,15 @@ subcategory: 4y4ylvqceE6vVqEF8IWZix
 
 Além de definir os textos do seu chat e/ou captura é possível também personalizar a aparência.  Para acessar essas configurações, acesse dentro do seu painel admin do **VTEX Assisted Sales (SuiteShare)** o campo **Configurações > minha conta**.
 
-![Personalizar 1](//images.ctfassets.net/alneenqid6w5/5FaGHXk7TYQh3ksA1d3V2y/13db76bc19548fee364bc5e0446f8a71/Screenshot_2022-08-31_at_15-05-25_Personalizar.png)
+![Personalizar 1](https://images.ctfassets.net/alneenqid6w5/5FaGHXk7TYQh3ksA1d3V2y/13db76bc19548fee364bc5e0446f8a71/Screenshot_2022-08-31_at_15-05-25_Personalizar.png)
 
 Clique em **“Aparência”**.
 
-![Personalizar 2](//images.ctfassets.net/alneenqid6w5/5BXY8UssL3Ad0IGZImI894/0202e3d65872d3d586c2c4a2c4de4add/Screenshot_2022-08-31_at_15-05-32_Personalizar.png)
+![Personalizar 2](https://images.ctfassets.net/alneenqid6w5/5BXY8UssL3Ad0IGZImI894/0202e3d65872d3d586c2c4a2c4de4add/Screenshot_2022-08-31_at_15-05-32_Personalizar.png)
 
 Nesta tela é possível editar o logo, cor e fundo.
 
-![Personalizar 3](//images.ctfassets.net/alneenqid6w5/6AjaiWD8IaEXvtSQuDZ7Eq/6b862f5a8fe54cf15d40a77a49cb8941/Screenshot_2022-08-31_at_15-05-37_Personalizar.png)
+![Personalizar 3](https://images.ctfassets.net/alneenqid6w5/6AjaiWD8IaEXvtSQuDZ7Eq/6b862f5a8fe54cf15d40a77a49cb8941/Screenshot_2022-08-31_at_15-05-37_Personalizar.png)
 
 Recomendamos que o logo seja enviado em PNG e em tamanhos quadrados, como por exemplo 1:1.
 
@@ -33,21 +33,21 @@ Defina a cor que será o seu chat, você pode enviar diretamente o código das c
 
 Escolha a cor do texto.
 
-![Personalizar 4](//images.ctfassets.net/alneenqid6w5/1cpsT10zhmEKWF5WmhIPwh/92d609f5942746ddb489e9777957e48c/Screenshot_2022-08-31_at_15-05-41_Personalizar.png)
+![Personalizar 4](https://images.ctfassets.net/alneenqid6w5/1cpsT10zhmEKWF5WmhIPwh/92d609f5942746ddb489e9777957e48c/Screenshot_2022-08-31_at_15-05-41_Personalizar.png)
 
 Selecione o tema desejado.
 
-![Personalizar 5](//images.ctfassets.net/alneenqid6w5/4sKPJCYclbPfNahy7hWP9g/28815a7fc765486b54efa6f18579780a/Screenshot_2022-08-31_at_15-05-45_Personalizar.png)
+![Personalizar 5](https://images.ctfassets.net/alneenqid6w5/4sKPJCYclbPfNahy7hWP9g/28815a7fc765486b54efa6f18579780a/Screenshot_2022-08-31_at_15-05-45_Personalizar.png)
 
 Pronto!
 
 Essas alterações estarão disponivéis nos [**formulários de captura**](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo).
 
-![Personalizar 6](//images.ctfassets.net/alneenqid6w5/6plXqoT7agynflbxaU5PaS/9d5ea2cb5a58fb03f382a209acd0a239/Screenshot_2022-08-31_at_15-05-49_Personalizar.png)
+![Personalizar 6](https://images.ctfassets.net/alneenqid6w5/6plXqoT7agynflbxaU5PaS/9d5ea2cb5a58fb03f382a209acd0a239/Screenshot_2022-08-31_at_15-05-49_Personalizar.png)
 
 E no [**seletivo**](\"http://help.suiteshare.com/support/solutions/articles/67000214752-seletivo\"). 
 
-![Personalizar 7](//images.ctfassets.net/alneenqid6w5/MA1CvcFrwxcIfbJIY1YTz/d670011df1acae80ce75b174e8f863d2/Screenshot_2022-08-31_at_15-05-54_Personalizar.png)
+![Personalizar 7](https://images.ctfassets.net/alneenqid6w5/MA1CvcFrwxcIfbJIY1YTz/d670011df1acae80ce75b174e8f863d2/Screenshot_2022-08-31_at_15-05-54_Personalizar.png)
 
 Não esqueça de clicar em "_**Salvar"**_.
 
diff --git a/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md b/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md
index 18667f34e..ae4ff9eaa 100644
--- a/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md
+++ b/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md
@@ -15,7 +15,7 @@ legacySlug: customizando-o-checkout-confirmation
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-![Página de confirmação de pedido (Order Placed)](//images.contentful.com/alneenqid6w5/n7VvdVmseGQyGwCEQAIiW/90bd066111747fe05d722e6fad172d14/cconf-hml1.png) 
+![Página de confirmação de pedido (Order Placed)](https://images.contentful.com/alneenqid6w5/n7VvdVmseGQyGwCEQAIiW/90bd066111747fe05d722e6fad172d14/cconf-hml1.png) 
 
 A nova seção de Meus Pedidos vem acompanhada de uma nova página de confirmação de pedido (Order Placed), agora parte do **Checkout Confirmation**, feature responsável pelas páginas de confirmação do Checkout.
 
@@ -25,7 +25,7 @@ Junto ao novo Order Placed, outra novidade é o Order Confirmation, que mostra a
 
 Assim como em versões anteriores, a página de Order Placed (assim como a de Order Changed) aceita **templates de HTML**:
 
-![Página de confirmação de pedido com imports de HTML](//images.contentful.com/alneenqid6w5/2HXuJJE5yMCUIaeCMoOOa8/1e947bf46ec9202214867219ba36677a/cconf-html-2.png)
+![Página de confirmação de pedido com imports de HTML](https://images.contentful.com/alneenqid6w5/2HXuJJE5yMCUIaeCMoOOa8/1e947bf46ec9202214867219ba36677a/cconf-html-2.png)
  
 Para adicionar seu código nesses templates, basta acessar o módulo Portal e, na aba **Code**, editar os seguintes arquivos:
 
@@ -36,7 +36,7 @@ Para adicionar seu código nesses templates, basta acessar o módulo Portal e, n
 
 É importante lembrar que a customização com templates é a mesma para Order Placed e Order Confirmation.
 
-![Página do Portal v2 com arquivos de template corretos destacados](//images.contentful.com/alneenqid6w5/5jGk1WbMqkkggyAog66iAs/c1162190ef431b8c96462fb34355aa98/cconf-html3.png)
+![Página do Portal v2 com arquivos de template corretos destacados](https://images.contentful.com/alneenqid6w5/5jGk1WbMqkkggyAog66iAs/c1162190ef431b8c96462fb34355aa98/cconf-html3.png)
 
 ### Customização de estilos
 
@@ -44,7 +44,7 @@ Para adicionar seu código nesses templates, basta acessar o módulo Portal e, n
 
 Também é possível editar a interface do Checkout Confirmation via classes CSS. Seus estilos devem ser adicionados numa `<style>` tag em um dos templates HTML carregados na página.
 
-![Página de OrderPlaced do Checkout Confirmation com classes de customização marcadas](//images.contentful.com/alneenqid6w5/OgLXDC0eyaOc4iKGmSkgS/a698e4da05726f33659d0ea88d0b1278/cconf-doc-2.png)
+![Página de OrderPlaced do Checkout Confirmation com classes de customização marcadas](https://images.contentful.com/alneenqid6w5/OgLXDC0eyaOc4iKGmSkgS/a698e4da05726f33659d0ea88d0b1278/cconf-doc-2.png)
 
 Para customizar os estilos do Checkout Confirmation, use as seguintes classes:
 
diff --git a/docs/tutorials/pt/customizing-the-my-orders-section.md b/docs/tutorials/pt/customizing-the-my-orders-section.md
index 7169517a8..4f350ff87 100644
--- a/docs/tutorials/pt/customizing-the-my-orders-section.md
+++ b/docs/tutorials/pt/customizing-the-my-orders-section.md
@@ -34,7 +34,7 @@ Caso você já possua um arquivo de customização para a antiga versão do My O
 
 ### Lista de pedidos
 
-![Página de lista de pedidos com classes para customização destacadas sobre ela](//images.contentful.com/alneenqid6w5/1P5JMzt3jGIAKIOmC4ka4e/d7511d7273f4a957acc6f7e1322a81e6/my-orders-doc-1.png) 
+![Página de lista de pedidos com classes para customização destacadas sobre ela](https://images.contentful.com/alneenqid6w5/1P5JMzt3jGIAKIOmC4ka4e/d7511d7273f4a957acc6f7e1322a81e6/my-orders-doc-1.png) 
 
 CSS:
 ```
@@ -49,7 +49,7 @@ CSS:
 
 ### Detalhe do pedido
 
-![Página de detalhe do pedido com classes para customização destacadas sobre ela](//images.contentful.com/alneenqid6w5/5szHUT7x9CAOseYGkcEskS/e8a846072846d20648c65a1cd00059c4/my-orders-doc-2.png)
+![Página de detalhe do pedido com classes para customização destacadas sobre ela](https://images.contentful.com/alneenqid6w5/5szHUT7x9CAOseYGkcEskS/e8a846072846d20648c65a1cd00059c4/my-orders-doc-2.png)
 
 CSS:
 ```
@@ -59,7 +59,7 @@ CSS:
 
 ### Cancelamento de pedido
 
-![Página de cancelamento do pedido com classes para customização destacadas sobre ela](//images.contentful.com/alneenqid6w5/5mUVzR5n7aMScoSs4auem4/05bfeea119bb4fc42afe448c66c9674f/my-orders-doc-3.png)
+![Página de cancelamento do pedido com classes para customização destacadas sobre ela](https://images.contentful.com/alneenqid6w5/5mUVzR5n7aMScoSs4auem4/05bfeea119bb4fc42afe448c66c9674f/my-orders-doc-3.png)
 
 CSS:
 ```
diff --git a/docs/tutorials/pt/customizing-your-stores-typography.md b/docs/tutorials/pt/customizing-your-stores-typography.md
index 6f2c84ca6..c3f650c3f 100644
--- a/docs/tutorials/pt/customizing-your-stores-typography.md
+++ b/docs/tutorials/pt/customizing-your-stores-typography.md
@@ -27,7 +27,7 @@ No Admin, você tem flexibilidade para personalizar a tipografia da sua loja de
 1. No Admin VTEX, acesse **Storefront > Styles (Estilos)**.
 2. Selecione o ícone kebab (três pontos).
 
-![Styles - Mais opções](//images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/e6f569468bccb9c85c309acd4b9fb066/styles-two-pt.png)
+![Styles - Mais opções](https://images.ctfassets.net/alneenqid6w5/7qhmfxaMzZ8Aw0F6mygs2i/e6f569468bccb9c85c309acd4b9fb066/styles-two-pt.png)
 
 3. Clique em **Edit (Editar) > Typography (Tipografia) > Font Family (Família da fonte)**.
 
@@ -51,7 +51,7 @@ Consulte a seção [Tokens de tipo](#type-tokens) para obter mais informações
 2. Selecione o ícone kebab (três pontos).
 3. Clique em **Edit (Editar) > Typography (Tipografia) > Type Tokens (Tokens de tipo)**.
 
-![Styles - Type tokens PT](//images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/13e59fcc04d2034ff8e2c9928c165354/styles-three-pt.gif)
+![Styles - Type tokens PT](https://images.ctfassets.net/alneenqid6w5/6kw7SMB36fZsS0SKX00Kss/13e59fcc04d2034ff8e2c9928c165354/styles-three-pt.gif)
 
 4. Escolha o tipo de ficha que você deseja personalizar como, por exemplo, **Heading 1** (Cabeçalho 1), e clique nele.
 
diff --git a/docs/tutorials/pt/data-entity.md b/docs/tutorials/pt/data-entity.md
index 452960b55..20bdb6136 100644
--- a/docs/tutorials/pt/data-entity.md
+++ b/docs/tutorials/pt/data-entity.md
@@ -19,7 +19,7 @@ Entidade de dados é uma representação de um conjunto de informações sobre u
 
 Para exemplificar, imagine um sistema de controle de uma biblioteca. Esse sistema controla livros que podem ser alugados por clientes. Então, percebemos que esses 3 conceitos (livro, cliente, aluguel) são entidades que possuem informações sobre cada uma delas. Entidade de dados, portanto, é um grupo de informações sobre determinado conceito.
 
-![data-entity-pt](//images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/82f3ea4c99a28baa362e8698f24dc924/data-entity-pt.png)
+![data-entity-pt](https://images.ctfassets.net/alneenqid6w5/4w7gskl1jpuzrFm4gj5K0J/82f3ea4c99a28baa362e8698f24dc924/data-entity-pt.png)
 
 Com esses conceitos, é possível configurar os mais diversos cenários de controle de dados pelo Master Data. Por padrão, são inseridas as seguintes entidades de dados: Cliente, Endereço, Stores etc. É possível criar quantas mais entidades de dados desejar, possibilitando um ambiente personalizado, voltado às necessidade de cada loja.
 
diff --git a/docs/tutorials/pt/data-subject-rights.md b/docs/tutorials/pt/data-subject-rights.md
index 3a9784c31..c2a11e7c1 100644
--- a/docs/tutorials/pt/data-subject-rights.md
+++ b/docs/tutorials/pt/data-subject-rights.md
@@ -50,7 +50,7 @@ Para exportar dados do Master Data v1 pelo painel Admin, siga estes passos:
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
 2. Clique na aba **Aplicações.**
 3. Clique em visualizar (ícone da direita) correspondente à entidade de dados desejada.
-![visualizar button master data](//images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
+![visualizar button master data](https://images.ctfassets.net/alneenqid6w5/2x1xCx4tEeV6eMPy4VRFpE/0e59f11450a93765e037da555f8d6c09/visualizar_button_export_data.png)
 4. Use o [filtro do Master Data v1](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) para filtrar apenas os dados referentes ao usuário desejado. Use o `email` ou `ID do usuário` como campo do filtro.
 5. Clique no botão `Exportar XLS`.
 6. Selecione a opção `Selecionar todos os campos`.
diff --git a/docs/tutorials/pt/deactivating-store-skus-and-products.md b/docs/tutorials/pt/deactivating-store-skus-and-products.md
index 59eea064b..ba961c15a 100644
--- a/docs/tutorials/pt/deactivating-store-skus-and-products.md
+++ b/docs/tutorials/pt/deactivating-store-skus-and-products.md
@@ -25,4 +25,4 @@ Para inativar o SKU de um produto, siga os passos abaixo:
 4. Clique no SKU que você deseja inativar.
 5. Desmarque a opção __Ativar o SKU se possível__.
 
-![inativarSKU](//images.contentful.com/alneenqid6w5/4On7ZXJXPyAUqqy2GaGEuu/04ebceeab81b47272be45f16679c7597/inativarSKU.png)
+![inativarSKU](https://images.contentful.com/alneenqid6w5/4On7ZXJXPyAUqqy2GaGEuu/04ebceeab81b47272be45f16679c7597/inativarSKU.png)
diff --git a/docs/tutorials/pt/declining-order-cancelation.md b/docs/tutorials/pt/declining-order-cancelation.md
index 2117ec66c..2f8cc25ad 100644
--- a/docs/tutorials/pt/declining-order-cancelation.md
+++ b/docs/tutorials/pt/declining-order-cancelation.md
@@ -34,7 +34,7 @@ Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedid
 ## Diagrama de cancelamento de pedido recusado
 A imagem a seguir mostra o fluxo de recusa da solicitação de cancelamento de um pedido após a janela para cancelamento:
 
-![order cancel diagram](//images.ctfassets.net/alneenqid6w5/6cGkrOT0G5sEeA3VaHKm4e/8f44049006390f2ef6a699cac00bd9d0/cancel_api_improvements_help_center_PT.png)
+![order cancel diagram](https://images.ctfassets.net/alneenqid6w5/6cGkrOT0G5sEeA3VaHKm4e/8f44049006390f2ef6a699cac00bd9d0/cancel_api_improvements_help_center_PT.png)
 
 Segue a descrição de cada etapa:
 
@@ -70,11 +70,11 @@ Para recusar uma solicitação de cancelamento do pedido pelo Admin VTEX, siga o
 2. Selecione o pedido desejado para acessar a página [Detalhes do pedido](https://help.vtex.com/en/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl).
 3. Na parte superior da página, clique em Recusar. 
 
-  ![deny cancel request](//images.ctfassets.net/alneenqid6w5/53kKd5oNkEjeziq9XR4yvO/04d25b8c3cf508d489ca53687d2187c7/deny_cancel_request_PT.png)
+  ![deny cancel request](https://images.ctfassets.net/alneenqid6w5/53kKd5oNkEjeziq9XR4yvO/04d25b8c3cf508d489ca53687d2187c7/deny_cancel_request_PT.png)
 
 4. Preencha o pop-up **Solicitação de cancelamento** com o motivo da recusa da solicitação de cancelamento do pedido.
 
-  ![deny_cancel_request_reason_PT_v2](//images.ctfassets.net/alneenqid6w5/2j1DgDKBaWJFMeVfuxfwYL/08eae24f54f83caa4d8449a3dd465d31/deny_cancel_request_reason_PT_v2.png)
+  ![deny_cancel_request_reason_PT_v2](https://images.ctfassets.net/alneenqid6w5/2j1DgDKBaWJFMeVfuxfwYL/08eae24f54f83caa4d8449a3dd465d31/deny_cancel_request_reason_PT_v2.png)
 
   <div class="alert alert-warning">
 Lembre-se de que a mensagem contida nesse campo poderá ser exibida ao cliente pela <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha conta</a> ou enviada pelo marketplace.
diff --git a/docs/tutorials/pt/defining-product-prices.md b/docs/tutorials/pt/defining-product-prices.md
index 75360377b..272d4f7ee 100644
--- a/docs/tutorials/pt/defining-product-prices.md
+++ b/docs/tutorials/pt/defining-product-prices.md
@@ -17,5 +17,5 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Já com os produtos cadastrados, é necessário definir o preço de venda. Eles podem ser limitados por UTMs ou mesmo ter datas de início e fim.
 
-<video class="wp-video-shortcode" id="video-2553-12" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4?_=12" />[//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4](//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4 "//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4")</video>
+<video class="wp-video-shortcode" id="video-2553-12" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4?_=12" />[//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4](https://assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4 "//assets.contentful.com/alneenqid6w5/yM9oycRcD6e0weK4I88w2/9162081490b6579d8e4c59c1d558d16d/cadastrando-precos.mp4")</video>
 
diff --git a/docs/tutorials/pt/defining-window-displays.md b/docs/tutorials/pt/defining-window-displays.md
index 4d3492627..66497e19d 100644
--- a/docs/tutorials/pt/defining-window-displays.md
+++ b/docs/tutorials/pt/defining-window-displays.md
@@ -27,26 +27,26 @@ Realizadas as devidas definições, o vínculo da coleção com a vitrine é fei
 
 No exemplo abaixo, iremos definir a vitrine apresentada na Home, sendo assim, deve-se realizar a alteração no seguinte layout:
 
-![cms_layout_home ](//images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
+![cms_layout_home ](https://images.ctfassets.net/alneenqid6w5/36BJckeyOAIYeEm8sOwQO0/e7a24fbbfe861550445a9f18dee77954/cms_layout_home.png)
 
 No layout selecionado, adicione o controle correspondente à vitrine onde deseja exibir a coleção clicando em **Add object**.
 Após selecionar o tipo de controle desejado, defina seu nome e clique em **Adicionar**.
 
 __Não se esqueça de salvar as configurações feitas para que seja possível posteriormente editar o controle criado.__
 
-![save settings cms](//images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
+![save settings cms](https://images.ctfassets.net/alneenqid6w5/21omKZNVc8QaWSw6K4akEQ/70105f086510d2eec6bfb3862a9979f5/save_settings_cms.png)
 
 ### Edição do controle
 
 Para editar seus controles, clique no **símbolo de lápis**, conforme mostra a imagem exemplo abaixo: 
 
-![banner_edit_cms](//images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
+![banner_edit_cms](https://images.ctfassets.net/alneenqid6w5/5eOuIai1zGGWOKI4OmoMOQ/5ff1b51e63a08d6d265a1e053999a369/banner_edit_cms.png)
 
 Ao editar o controle é necessário adicionar seus conteúdos, que representam cada conjunto de itens que serão exibidos.
 Para isso, clique em **Add content**
 
-![cadastro_conteudo_cms ](//images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
-![cadastro_conteudo_cms 2](//images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
+![cadastro_conteudo_cms ](https://images.ctfassets.net/alneenqid6w5/TWIydQxL2M4WsEiccmI2A/f8ff28eafb9dde3e01926b899262f519/cadastro_de_conteudo_1.png)
+![cadastro_conteudo_cms 2](https://images.ctfassets.net/alneenqid6w5/6Q0ZTbWIBUeu2uSY8w2mMs/5fb5a636e8781881b47237714571ee1c/cadastro_de_conteudo_2.png)
 
 - **"Adicionar arquivo":** para selecionar a coleção que será exibida nesse conteúdo. 
 - **Partner / Campaign / Source:**  define a exibição desse conteúdo caso o visitante possua alguma UTM correspondente em sua URL de origem. 
@@ -62,7 +62,7 @@ Deve-se marcar a opção **Active Content** e clicar em **Add content list**, sa
 
 Se caso depois de salvo o conteúdo for necessário editá-lo, basta clicar no segundo simbolo de lápis conforme mostra a imagem abaixo:
 
-![edit_content_cms](//images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
+![edit_content_cms](https://images.ctfassets.net/alneenqid6w5/3m9TM8vkEU0UmkueoEYIM8/89b2385f1e14978383b9d4fd0ecfd129/edi_content.png)
 
 Deve-se realizar as mudanças desejadas, clicar em **Update Content List** e salvar todas as configurações feitas clicando em **Save Settings** depois. 
 
diff --git a/docs/tutorials/pt/deleting-a-category.md b/docs/tutorials/pt/deleting-a-category.md
index e7f8f994a..8fa3f722f 100644
--- a/docs/tutorials/pt/deleting-a-category.md
+++ b/docs/tutorials/pt/deleting-a-category.md
@@ -26,7 +26,7 @@ Para que uma categoria não apareça para os clientes da loja, você pode torná
 3. Clique na categoria que você deseja inativar.
 4. Clique no botão `Ações`.
 5. Clique em `Alterar`.
-6. Desmarcar o campo __Ativo | Categoria está ativa no site__, conforme a imagem abaixo: ![img inativarcategoria PT](//images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/c13fcfdbd38d3355b8541fff3f215890/img_inativarcategoria_PT.png)
+6. Desmarcar o campo __Ativo | Categoria está ativa no site__, conforme a imagem abaixo: ![img inativarcategoria PT](https://images.ctfassets.net/alneenqid6w5/6SzDebwe2AzOlz9PjlaHNP/c13fcfdbd38d3355b8541fff3f215890/img_inativarcategoria_PT.png)
 7. Clique em `Salvar`.
 
 ## Apagar todas as categorias
diff --git a/docs/tutorials/pt/deleting-a-folder-from-cms.md b/docs/tutorials/pt/deleting-a-folder-from-cms.md
index 4c4e13950..70270b3fa 100644
--- a/docs/tutorials/pt/deleting-a-folder-from-cms.md
+++ b/docs/tutorials/pt/deleting-a-folder-from-cms.md
@@ -25,7 +25,7 @@ Para apagar uma pasta do CMS, siga os passoa abaixo:
 3. Clique no website desejado e depois na pasta raiz (/).
 4. Na linha da pasta que você deseja apagar, clique em __delete__.
 
-![erroDeletarPasta2](//images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
+![erroDeletarPasta2](https://images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
 
 <div class="alert alert-danger">
 Algumas pastas são obrigatórias. Sua loja não funcionará corretamente sem elas. Outras são importantes, portanto não é uma boa ideia apagá-las.<br><br>Entenda melhor este assunto no artigo <a href="http://help.vtex.com/pt/tutorial/estrutura-de-pastas-do-cms">Estrutura de pastas do CMS</a>.
@@ -33,6 +33,6 @@ Algumas pastas são obrigatórias. Sua loja não funcionará corretamente sem el
 
 Se uma pasta contém outras pastas, antes de apagá-la é necessário apagar todas as pastas internas. Caso contrário, o sistema retornará o erro "Object reference not set to an instance of an object", como na imagem abaixo.
 
-![erroDeletarPasta](//images.contentful.com/alneenqid6w5/6g2MBbZJUQUQM2YQQ88MQE/9159df93c82fc1e89199aaf1922a5044/erroDeletarPasta.png)
+![erroDeletarPasta](https://images.contentful.com/alneenqid6w5/6g2MBbZJUQUQM2YQQ88MQE/9159df93c82fc1e89199aaf1922a5044/erroDeletarPasta.png)
 
 Por exemplo, se você deseja deletar a pasta A, e dentro dela ficam as pastas A1 e A2, primeiro apague as pastas A1 e A2, e somente depois apague a pasta A.
diff --git a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
index f1cbac289..2a08ca13f 100644
--- a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
+++ b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
@@ -48,7 +48,7 @@ Para imprimir etiquetas dos pacotes no Admin VTEX, utilize a ferramenta <a href=
 
 No Admin VTEX, em **Envio > Entregas Correios**, a página **Informações dos Pedidos** apresenta uma listagem de todos os pacotes postados. Na lista, é possível acompanhar as seguintes informações:
 
-![order_information_shipping_network_PT](//images.ctfassets.net/alneenqid6w5/2B9Ofd5hFwPkSxl31szyzU/d348694f06824d1e46b995bc712406af/order_information_shipping_network_PT.png)
+![order_information_shipping_network_PT](https://images.ctfassets.net/alneenqid6w5/2B9Ofd5hFwPkSxl31szyzU/d348694f06824d1e46b995bc712406af/order_information_shipping_network_PT.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
     <thead class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
@@ -135,7 +135,7 @@ Ainda na página **Informações dos Pedidos,** você pode:
 
 Para visualizar mais informações sobre os pacotes de um pedido enviado clique no menu <i class="fas fa-ellipsis-v"></i> na última coluna da lista, e então clique em <i class="fas fa-eye"></i> `Detalhes do pedido`.
 
-![entregas_correios_detalhes_pedidos_PT](//images.ctfassets.net/alneenqid6w5/3vtixaxWaubVOeLuueXgMI/ad5ca210783876124a205ee551e41c8f/entregas_correios_detalhes_pedidos_PT.png)
+![entregas_correios_detalhes_pedidos_PT](https://images.ctfassets.net/alneenqid6w5/3vtixaxWaubVOeLuueXgMI/ad5ca210783876124a205ee551e41c8f/entregas_correios_detalhes_pedidos_PT.png)
 
 Na nova página, você pode realizar as seguintes ações: 
 
diff --git a/docs/tutorials/pt/detaching-skus-by-specification.md b/docs/tutorials/pt/detaching-skus-by-specification.md
index 5736c0b62..54bc520af 100644
--- a/docs/tutorials/pt/detaching-skus-by-specification.md
+++ b/docs/tutorials/pt/detaching-skus-by-specification.md
@@ -25,7 +25,7 @@ Essa ferramenta é indicada, principalmente, para lojas de vestuários, pois é
 
 A seguir, confira um exemplo de separação de SKUs por cor. Na imagem abaixo, a sandália em destaque apresenta duas cores diferentes no resultado da pesquisa:
 
-![screencapture-footnotes-sandals-2021-02-11-14 21 21](//images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
+![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
 <div class="alert alert-info"><p>
 Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.</p></div>
diff --git a/docs/tutorials/pt/direct-migration-magazine-luiza.md b/docs/tutorials/pt/direct-migration-magazine-luiza.md
index 2d6202120..ce75edb6c 100644
--- a/docs/tutorials/pt/direct-migration-magazine-luiza.md
+++ b/docs/tutorials/pt/direct-migration-magazine-luiza.md
@@ -19,7 +19,7 @@ A **Migração Direta Magazine Luiza** foi desenvolvida para facilitar o process
 
 Utilizando a **Migração Direta,** a conta do seller no marketplace é reaproveitada e neste caso a relevância de vendas do seller é mantida.  
 
-![Fluxo da migração](//images.ctfassets.net/alneenqid6w5/7GdLQ0HFfZXJ7mxvqGgNeO/26fc293e4cf1592347635841669433b5/Fluxo_de_funcionamento_integra__o.png)
+![Fluxo da migração](https://images.ctfassets.net/alneenqid6w5/7GdLQ0HFfZXJ7mxvqGgNeO/26fc293e4cf1592347635841669433b5/Fluxo_de_funcionamento_integra__o.png)
 
 ## Integrando a loja VTEX com o Magazine Luiza marketplace
 
@@ -47,7 +47,7 @@ O código de referência do SKU na VTEX deve ser igual ao ID do SKU no Magazine
 Na data e horário acordado entre o seller e a VTEX, o processo de migração será iniciado e os pedidos que estão pendentes no Portal do seller Magazine Luiza serão segmentados. Todos os pedidos pendentes anteriores à data definida, ficam sob responsabilidade do seller para atualização manual no Portal do seller e os pedidos posteriores à data definida ficam sob responsabilidade da VTEX.
 </div>
 
-![Data de migração](//images.ctfassets.net/alneenqid6w5/3TcYO5vYXIMqRqpGoY2sWV/3f23ceeb4116f807b2b65e075d42fe85/Fluxo_de_pedidos_na_migra__o.png)
+![Data de migração](https://images.ctfassets.net/alneenqid6w5/3TcYO5vYXIMqRqpGoY2sWV/3f23ceeb4116f807b2b65e075d42fe85/Fluxo_de_pedidos_na_migra__o.png)
 
 Após informar o dia e horário desejado para realizar a integração, o seller deve aguardar o retorno da VTEX confirmando a finalização da migração para seguir aos [testes](#testes).
 
diff --git a/docs/tutorials/pt/disable-cloudflare-proxy.md b/docs/tutorials/pt/disable-cloudflare-proxy.md
index c514bd81a..0e23da548 100644
--- a/docs/tutorials/pt/disable-cloudflare-proxy.md
+++ b/docs/tutorials/pt/disable-cloudflare-proxy.md
@@ -23,7 +23,7 @@ Para desligar o proxy do CloudFlare (e consequentemente, desativar os serviços
 
 Observe que, se o proxy estiver ligado, o ícone estará em laranja com o texto __*Proxied*__. Caso contrário, o ícone estará em cinza com o texto __*DNS Only*__.
 
-![Configuração do proxy da Cloudflare](//images.contentful.com/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/e644144d4c98accd1c24649ac765a7be/DNS_Management.png)
+![Configuração do proxy da Cloudflare](https://images.contentful.com/alneenqid6w5/1pEYEd1KWlH0P97Pgwyb7n/e644144d4c98accd1c24649ac765a7be/DNS_Management.png)
 
 É importante notar que o resultado da desabilitação do proxy da CloudFlare pode demorar um pouco para ser observado, pois é necessário que o cache seja renovado.
 
diff --git a/docs/tutorials/pt/displaying-the-store-in-another-language.md b/docs/tutorials/pt/displaying-the-store-in-another-language.md
index 2236f5405..e738cf3c9 100644
--- a/docs/tutorials/pt/displaying-the-store-in-another-language.md
+++ b/docs/tutorials/pt/displaying-the-store-in-another-language.md
@@ -17,7 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 Para que seu site seja exibido em outra língua, deve-se [criar uma nova política comercial](/pt/tutorial/configurando-a-politica-comercial-para-marketplace/) e atribuir a ela o idioma desejado no campo __Culture Info__.
 
-![exibição-loja-idioma-diferente pt](//images.ctfassets.net/alneenqid6w5/7BeeKmilag6wYaKGMkWwMW/2dab353b989d38047b1c92f342d6c37d/exibi____o-loja-outra-l__ngua_pt.png)
+![exibição-loja-idioma-diferente pt](https://images.ctfassets.net/alneenqid6w5/7BeeKmilag6wYaKGMkWwMW/2dab353b989d38047b1c92f342d6c37d/exibi____o-loja-outra-l__ngua_pt.png)
 
 
 Após a configuração na política comercial, será necessário um ajuste no front-end da loja para que a mudança de idioma ocorra e, com ela, a mudança de políticas comerciais. 
diff --git a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
index 9bfabf668..4c1359a74 100644
--- a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -31,7 +31,7 @@ Por ora, lojas VTEX podem disponibilizar inventário de anúncios apenas em fren
 
 Na tela inicial do aplicativo [VTEX Ad Network para lojas](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#lojas), você pode acompanhar os resultados de anúncios na sua loja.
 
-![vtex_ad_network_admin_PT](//images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/c479a1adcfce1ab838edfa17aeb6aca7/vtex_ad_network_admin.png)
+![vtex_ad_network_admin_PT](https://images.ctfassets.net/alneenqid6w5/7nvJI9GTv53buxMMyvarRa/c479a1adcfce1ab838edfa17aeb6aca7/vtex_ad_network_admin.png)
 
 Na parte superior, estão dados agregados:
 
@@ -62,7 +62,7 @@ Você também pode usar os filtros disponíveis acima da tabela:
 
 Na tabela da tela inicial do app [VTEX Ad Network para lojas](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#lojas), você também pode clicar na linha referente a uma das campanhas para ver dados mais específicos.
 
-![vtex_ad_network_details_PT](//images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/50caa424b0c867189369d8071e5afcf0/vtex_ad_network_details.png)
+![vtex_ad_network_details_PT](https://images.ctfassets.net/alneenqid6w5/11oqzf225OjAxaN4gcGCme/50caa424b0c867189369d8071e5afcf0/vtex_ad_network_details.png)
 
 - **Visualizações / Cliques:** Visualizações de anúncios e cliques em anúncios.
 - **CTR:** taxa de cliques, calculada pela divisão do número de cliques pelo número de visualizações.
diff --git a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
index fd607701f..4614a54a2 100644
--- a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
@@ -41,7 +41,7 @@ A relevância manual é configurada pela distribuição dos pesos realizada na p
 
 1. No Admin VTEX, acesse **Storefront > Intelligent Search >** **Regras de relevância**  ou digite **Regras de relevância** na barra de busca no topo da página.
 2. Selecione a opção **Relevância manual**.
-![relevancia-manual-pt](//images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/1a0116cc71d5df6ffff2d2ac21854736/image.png)
+![relevancia-manual-pt](https://images.ctfassets.net/alneenqid6w5/5BSjswlkB1mMpR1MtCrEWL/1a0116cc71d5df6ffff2d2ac21854736/image.png)
 3. Clique em `Salvar`.
 
 Para configurar a relevância manual, confira o artigo [Relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
@@ -59,7 +59,7 @@ Para ativar a relevância dinâmica, siga os seguintes passos:
 1. No Admin VTEX, acesse **Storefront > Intelligent Search > Regras de relevância**  ou digite **Regras de relevância** na barra de busca no topo da página.
 2. Leia as informações sobre a Relevância Dinâmicas e clique em `Próximo`.
 3. Selecione a opção **Relevância Dinâmica**.
-![relevancia-dinamica-pt](//images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/325dfbf15ee811133ae0a12a89959b43/image.png)
+![relevancia-dinamica-pt](https://images.ctfassets.net/alneenqid6w5/4yzGzHE6WhQp6qFGISgt9q/325dfbf15ee811133ae0a12a89959b43/image.png)
 4. Clique em `Salvar`.
 5. Aguarde a barra de carregamento atingir 100%. Esse processo pode demorar algumas horas. Você receberá um email notificando que o carregamento foi finalizado.
 6. Clique em `Ativar`.
diff --git a/docs/tutorials/pt/editing-my-data-suiteshare.md b/docs/tutorials/pt/editing-my-data-suiteshare.md
index c2aae8e19..43705df6f 100644
--- a/docs/tutorials/pt/editing-my-data-suiteshare.md
+++ b/docs/tutorials/pt/editing-my-data-suiteshare.md
@@ -17,18 +17,18 @@ subcategory: 4y4ylvqceE6vVqEF8IWZix
 
 Para editar os dados de acesso, você deve acessar _**Configurações > Minha conta**_. 
 
-![Editar_dados_Suitshare_1](//images.ctfassets.net/alneenqid6w5/7GjD9aAHEpWeLMULbgIlN7/7373e8bfedf32a7c6c1fa965872b80a5/Editar_dados_1.png)
+![Editar_dados_Suitshare_1](https://images.ctfassets.net/alneenqid6w5/7GjD9aAHEpWeLMULbgIlN7/7373e8bfedf32a7c6c1fa965872b80a5/Editar_dados_1.png)
 
 Em **Profile**, edite informações como **Nome** e **Empresa**. 
 
-![Editar_dados_suitshare_2](//images.ctfassets.net/alneenqid6w5/1IytrpGXxE40bEdQ6eSLtg/4560182def1d9a3ee7b26b66c709f5fe/Editar_dados_suitshare_2.png)
+![Editar_dados_suitshare_2](https://images.ctfassets.net/alneenqid6w5/1IytrpGXxE40bEdQ6eSLtg/4560182def1d9a3ee7b26b66c709f5fe/Editar_dados_suitshare_2.png)
 
 Em **Password**, edite sua senha. 
 
-![Editar_dados_suitshare_3](//images.ctfassets.net/alneenqid6w5/1qcocpgUcO5nj9wqeDUJDW/048ec22ead339bb22b4779a22cad5cfd/Editar_dados_suitshare_3.png)
+![Editar_dados_suitshare_3](https://images.ctfassets.net/alneenqid6w5/1qcocpgUcO5nj9wqeDUJDW/048ec22ead339bb22b4779a22cad5cfd/Editar_dados_suitshare_3.png)
 
 Em **Email**, edite as informações do seu e-mail. 
 
-![Editar_dados_suitshare_4](//images.ctfassets.net/alneenqid6w5/7aNcHeEQPJ8Di0VALzxVXx/341143302118e8a7fad2ef91b26ca817/Editar_dados_suitshare_4.png)
+![Editar_dados_suitshare_4](https://images.ctfassets.net/alneenqid6w5/7aNcHeEQPJ8Di0VALzxVXx/341143302118e8a7fad2ef91b26ca817/Editar_dados_suitshare_4.png)
 
 Para saber mais sobre sua conta, entre em contato conosco.
diff --git a/docs/tutorials/pt/enable-checkout-v6.md b/docs/tutorials/pt/enable-checkout-v6.md
index 4c89689b0..05e633c59 100644
--- a/docs/tutorials/pt/enable-checkout-v6.md
+++ b/docs/tutorials/pt/enable-checkout-v6.md
@@ -28,7 +28,7 @@ Para atualizar o checkout da sua loja para a versão mais recente (Checkout v6),
 5. Clique em __Salvar__. 
 6. [Acesse sua loja em ambiente beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) e realize os ajustes de estilo necessários. O Checkout v6 possui novas classes _CSS_ que devem ser levadas em consideração para customização do estilo.
 
-![Checkoutv6_box](//images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/a1d6c6ab5e38fd7398ebc47b7ae32aa1/CheckoutV6_box_PT.png)
+![Checkoutv6_box](https://images.ctfassets.net/alneenqid6w5/9hAJfi1LLwpFlcB5iWA3k/a1d6c6ab5e38fd7398ebc47b7ae32aa1/CheckoutV6_box_PT.png)
 
 ## Ativar o Checkout v6 em Ambiente de Produção
 
@@ -42,7 +42,7 @@ Após realizar os ajustes necessários em Ambiente de Teste, você pode ativar o
 
 Após este passo, o Checkout v6 estará instalado na sua loja.
 
-![checkoutv6_box_2](//images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/671c0ec19bac97c07c97f3276150c30d/CheckoutV6_box2_PT.png)
+![checkoutv6_box_2](https://images.ctfassets.net/alneenqid6w5/1gXZSHO1C5yRDF6GL6h5IK/671c0ec19bac97c07c97f3276150c30d/CheckoutV6_box2_PT.png)
 
 ## Como checar se o Checkout v6 foi instalado corretamente?
 
diff --git a/docs/tutorials/pt/enabling-2-factor-authentication-login.md b/docs/tutorials/pt/enabling-2-factor-authentication-login.md
index a1eb82966..dec14e58e 100644
--- a/docs/tutorials/pt/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/pt/enabling-2-factor-authentication-login.md
@@ -34,7 +34,7 @@ Há duas opções de autenticação:
 - Por chave gerada por um __aplicativo__ de autenticação.
 - Por chave enviada por mensagem de telefone (__SMS__).
 
-![2FA - Select - PT](//images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
+![2FA - Select - PT](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
 
 <div class="alert alert-danger">
 Recomendamos fortemente que você <strong>escolha a opção de autenticação por aplicativo</strong>, uma vez que na autenticação por SMS você depende de que não haja falhas na operadora de telefonia. Pelo aplicativo, a chave de acesso estará sempre à disposição quando for necessária.
@@ -51,7 +51,7 @@ Para usar uma chave gerada por aplicativo de autenticação:
 1. Baixe o aplicativo __Google Authenticator__ ([App Store](https://itunes.apple.com/br/app/google-authenticator/id388497605?mt=8) / [Google Play](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=pt_BR)).
   ![2FA - App Download - PT](https://images.ctfassets.net/alneenqid6w5/icTTRRH1WH7FiiH0gLnxb/c0bc298cb4c870e271da368bb765e146/2FA_-_App_Download_-_PT.png)
 2. Use o aplicativo para ler o QR Code com a câmera do seu celular.
-![mfa código](//images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/42671df78ec718b7121b8d75379cf951/mfa_qr_code_correction_pt.jpg)
+![mfa código](https://images.ctfassets.net/alneenqid6w5/4wk6Xk8c7T5EURmt94lRJx/42671df78ec718b7121b8d75379cf951/mfa_qr_code_correction_pt.jpg)
 3. Sua conta da VTEX será adicionada ao aplicativo, com um código de 6 dígitos. Insira o código para concluir seu login.
 
   *O código do app é atualizado periodicamente. Não será necessário memorizá-lo, basta consultar o aplicativo sempre que precisar.*
@@ -87,10 +87,10 @@ Para modificar as configurações de verificação em duas etapas:
 
 1. Acesse suas configurações de usuário, clicando no círculo com suas iniciais no canto superior-direito do Admin.
 
-  ![2FA - User Initials - PT](//images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
+  ![2FA - User Initials - PT](https://images.ctfassets.net/alneenqid6w5/3ktWD1KvDLV499l40SxUc2/09b0b09ce0766a877961adaeadb3d273/2FA_-_User_Initials_-_PT.png)
 
 2. Clique em **Verificação em 2 passos** para visualizar suas configurações.
 
-  ![2FA - My User - PT](//images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
+  ![2FA - My User - PT](https://images.ctfassets.net/alneenqid6w5/O4jBeKN2RTMS0bKOWVJVK/f2f91e3154f9392fe1c96207101a627f/2FA_-_My_User_-_PT.png)
 
 3. Você poderá então alterar suas configurações seguindo passos similares aos apresentados nas seções acima para habilitar 2FA por [SMS](#habilitar-o-2fa-por-sms) e [aplicativo](#habilitar-o-2fa-por-aplicativo). 
diff --git a/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
index ace011170..64be5c20e 100644
--- a/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
@@ -35,6 +35,6 @@ Neste tutorial, explicaremos como realizar essa integração por meio do Admin d
 4. Desça a tela e habilite a opção __3DS Enabled__.  
 5. Clique em __Salvar__.
 
-![RedsysV2 PT](//images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/803dff2f8664c2fef47143f6261a4463/Redsys_3DS2_-_PT.png)
+![RedsysV2 PT](https://images.ctfassets.net/alneenqid6w5/9Ee9cJHkCY2NQy6AAwsr5/803dff2f8664c2fef47143f6261a4463/Redsys_3DS2_-_PT.png)
 
 Feito isso, a solução estará habilitada para as transações da Redsýs com cartão de crédito.
diff --git a/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
index e9073a75a..6f2af423f 100644
--- a/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -75,9 +75,9 @@ Para garantir que os vendedores da sua loja física tenham acesso correto ao est
 Para isso, escolha um vendedor cadastrado na loja em que deseja testar a Venda em Mãos e siga os passos descritos abaixo. 
 
 1. Com [o registro do vendedor escolhido](https://help.vtex.com/pt/tutorial/vendedores-instore-beta--4rzit1pzp28km4HSDEdrEC), acesse a aplicação do VTEX Sales App e faça o login.
-![instore-login-pt](//images.ctfassets.net/alneenqid6w5/5vKzjuYAYKGIVZz5aOyuPV/9049d57cf49ca1e753b69896ea5f348f/image.png)
+![instore-login-pt](https://images.ctfassets.net/alneenqid6w5/5vKzjuYAYKGIVZz5aOyuPV/9049d57cf49ca1e753b69896ea5f348f/image.png)
 2. Busque por um item que existe no estoque da conta franquia cadastrado. Este item deverá estar exibindo a quantidade disponível correspondente ao inventário do seller.
-![instore-pdp-pt](//images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/861791e5b4f8f2304ae1a5a7ae577ad8/image.png)
+![instore-pdp-pt](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/861791e5b4f8f2304ae1a5a7ae577ad8/image.png)
 
 <div class="alert alert-info">
 <p>Caso você tenha habilitado estoque infinito, o número exibido será uma quantidade acima de 1 milhão de itens e não será alterado ao realizar uma venda.</p> 
@@ -92,9 +92,9 @@ Você também pode configurar para que a Vendas em Mãos ignore a quantidade do
 2. Clique no botão <i class="fas fa-cog"></i> engrenagem para editar. 
 3. Selecione a aba **Código**.
 4. Selecione na aba lateral o arquivo `checkout-instore-custom-js`.
-![instore-custom-js-pt](//images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/6521818abb09e4178491f4598f33c9a0/image.png)
+![instore-custom-js-pt](https://images.ctfassets.net/alneenqid6w5/5a70caO8nFFF25CrSXPXkx/6521818abb09e4178491f4598f33c9a0/image.png)
 5. Na chave `window.INSTORE_CONFIG`, adicione a flag `sellWithoutStockInHands: true`.
-![sellWithoutStockInHands-pt](//images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/14bef6c0a1cbdc5d216b17a49c438c76/image.png)
+![sellWithoutStockInHands-pt](https://images.ctfassets.net/alneenqid6w5/3yfRFSG0QgIwnXvyxwhsLo/14bef6c0a1cbdc5d216b17a49c438c76/image.png)
 6. Clique em <i class="fas fa-save"></i> `Salvar`. 
 
 ### Habilitar venda de carrinhos mistos (opcional)
diff --git a/docs/tutorials/pt/enabling-pwa-push-notifications-in-your-store.md b/docs/tutorials/pt/enabling-pwa-push-notifications-in-your-store.md
index 06c648d34..69676a0a2 100644
--- a/docs/tutorials/pt/enabling-pwa-push-notifications-in-your-store.md
+++ b/docs/tutorials/pt/enabling-pwa-push-notifications-in-your-store.md
@@ -16,7 +16,7 @@ subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
 Todas as lojas VTEX IO nativamente têm um *Progressive Web App* (PWA) à sua disposição. Um PWA é um tipo de aplicativo da web usado para promover nativamente recursos vantajosos para os usuários, como funcionalidades offline ou um ícone na tela inicial.
-![pwa-noticept](//images.contentful.com/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/8bc20370d21ff3d19a82d3a878cf1483/Screenshot_162.png)
+![pwa-noticept](https://images.contentful.com/alneenqid6w5/24FsMpd5zrenF21J4FG6B5/8bc20370d21ff3d19a82d3a878cf1483/Screenshot_162.png)
 
 O PWA pode ser disponibilizado para instalação do usuário em três momentos distintos de sua experiência de navegação: durante a primeira visita ao site da sua loja, ao adicionar o primeiro item ao carrinho, ou ao finalizar a primeira compra.
 Descubra como configurar o prompt em sua loja seguindo as etapas abaixo.
diff --git a/docs/tutorials/pt/entering-tax-receipts-in-the-order.md b/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
index f3bae8e4c..a97a94461 100644
--- a/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
@@ -19,7 +19,7 @@ Inserir a nota fiscal no pedido é um passo obrigatório para que o status passe
 
 Para fazer manualmente pelo **Gerenciamento de pedidos**, basta clicar no botão `Faturar pacote`, como na imagem abaixo.
 
-![faturar-pedido-ex pt](//images.ctfassets.net/alneenqid6w5/1IOORyWRjC4eEayM8iW6OG/0e49ae3568ea66ed18b5b8ab6f90d414/ex_1_pt.png)
+![faturar-pedido-ex pt](https://images.ctfassets.net/alneenqid6w5/1IOORyWRjC4eEayM8iW6OG/0e49ae3568ea66ed18b5b8ab6f90d414/ex_1_pt.png)
 
 Com a inserção da nota fiscal com o valor completo do pedido, o mesmo passará para o status **Faturado**.
 
diff --git a/docs/tutorials/pt/exact-sales-suiteshare.md b/docs/tutorials/pt/exact-sales-suiteshare.md
index 56e224960..1bfde064e 100644
--- a/docs/tutorials/pt/exact-sales-suiteshare.md
+++ b/docs/tutorials/pt/exact-sales-suiteshare.md
@@ -21,17 +21,17 @@ Para realizar a integração acesse as informações de integrações no seu pai
 
 No dashboard, em **Integrações**, clique em **Ver todas as integrações**. Ou clique em **Configurações > Integrações**.
 
-![Exact Sales_1](//images.ctfassets.net/alneenqid6w5/4BIijO0GTioTrQTMcJ9RHK/43c3fa8faf82688d8b81349ffddb126e/Exact_Sales_1.png)
+![Exact Sales_1](https://images.ctfassets.net/alneenqid6w5/4BIijO0GTioTrQTMcJ9RHK/43c3fa8faf82688d8b81349ffddb126e/Exact_Sales_1.png)
 
 Selecione o **Exact sales** e clique em **Integrar**.
 
 Selecione o [**Formulário de captura**](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseje conectar.
 
-![Exact Sales_2](//images.ctfassets.net/alneenqid6w5/0GPE5ktROtM3W1vK8TXN1/06650c897c805a8fe61433efb6b37621/Exact_Sales_2.png)
+![Exact Sales_2](https://images.ctfassets.net/alneenqid6w5/0GPE5ktROtM3W1vK8TXN1/06650c897c805a8fe61433efb6b37621/Exact_Sales_2.png)
 
 Dentro do Exact Sales, clique em **Configurações** e em [**“Integrações”**](https://app.exactsales.com.br/Configuracao/ConfiguracaoIntegracoes/Index).
 
-![Exact Sales_3](//images.ctfassets.net/alneenqid6w5/36Q38y7U71P7DB6ZlomAi5/6421cdc93d6292958e5fddadf464dadc/Exact_Sales_3.png)
+![Exact Sales_3](https://images.ctfassets.net/alneenqid6w5/36Q38y7U71P7DB6ZlomAi5/6421cdc93d6292958e5fddadf464dadc/Exact_Sales_3.png)
 
 Copie o token fornecido pela Exact Sales e cole dentro da VTEX Assisted Sales (SuiteShare). 
 
diff --git a/docs/tutorials/pt/excluding-a-product-from-the-store.md b/docs/tutorials/pt/excluding-a-product-from-the-store.md
index 062b6b527..a779d4183 100644
--- a/docs/tutorials/pt/excluding-a-product-from-the-store.md
+++ b/docs/tutorials/pt/excluding-a-product-from-the-store.md
@@ -27,6 +27,6 @@ No entanto, uma vez que o produto em questão tenha alguma referência a outra 
 
 Neste caso, a seguinte mensagem de erro aparece ao tentar excluí-lo:
 
-![erroExcluir](//images.contentful.com/alneenqid6w5/19vbt8GlfOK0IMEMEo86Gu/75d44c69a5d553d485daa668d1ab19bc/erroExcluir.png)
+![erroExcluir](https://images.contentful.com/alneenqid6w5/19vbt8GlfOK0IMEMEo86Gu/75d44c69a5d553d485daa668d1ab19bc/erroExcluir.png)
 
 A solução é inativar o produto. Veja como no artigo [Inativar SKUs e produtos da loja](/pt/tutorial/inativar-skus-e-produtos-da-loja).
diff --git a/docs/tutorials/pt/explained-search.md b/docs/tutorials/pt/explained-search.md
index b9cab31c9..50812ac53 100644
--- a/docs/tutorials/pt/explained-search.md
+++ b/docs/tutorials/pt/explained-search.md
@@ -27,5 +27,5 @@ Para utilizá-la, siga o passo a passo abaixo:
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
 2. Em **Intelligent Search**, clique em **Explicação da busca**. 
 
-![Explicação da Busca](//images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
+![Explicação da Busca](https://images.ctfassets.net/alneenqid6w5/5KrbVmzoI4woKzjxhsGJne/7b6559e6b60aacbd221d805318331bf0/explica____o_de_busca_pt.png)
 
diff --git a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
index d9594108b..c4d928fd3 100644
--- a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
@@ -30,14 +30,14 @@ Veja a seguir como exportar a planilha com as especificações de produto ou de
 1. No Admin VTEX, acesse __Catálogo__, ou digite __Catálogo__ na barra de busca no topo da página.
 2. Clique em __Importação e exportação__.
 3. Clique na aba __Especificações de produto__ ou __Especificações de SKU__, dependendo da sua necessidade.
-    ![skuexport.pt](//images.ctfassets.net/alneenqid6w5/2GmGsYDBCUlq01JyLJF6q/63708fe7dece1cf9ec100eeaf0851674/skuexport.pt.png)
+    ![skuexport.pt](https://images.ctfassets.net/alneenqid6w5/2GmGsYDBCUlq01JyLJF6q/63708fe7dece1cf9ec100eeaf0851674/skuexport.pt.png)
 4. Clique com o botão direito na categoria desejada.
     Não é possível exportar especificações de todas as categorias de uma só vez. É preciso escolher apenas uma categoria cujas especificações você deseja exportar.
 5. Clique na opção `Exportar`.
     Um retângulo verde aparecerá na tela.
 6. Clique em `Clique aqui para baixar o arquivo`.
 
-![skuexport2.pt](//images.ctfassets.net/alneenqid6w5/32z4zfvN7GeKcfZsuVQsGA/cac3411fabd0a1d32cb85b4592d0a4dd/skuexport2.pt.png)
+![skuexport2.pt](https://images.ctfassets.net/alneenqid6w5/32z4zfvN7GeKcfZsuVQsGA/cac3411fabd0a1d32cb85b4592d0a4dd/skuexport2.pt.png)
 
 <div class = "alert alert-info">
   <p>A planilha exportada ficará disponível por uma semana no seu email. Caso exceda esse prazo, siga o passo a passo de exportação novamente para gerar uma nova planilha.</p>
@@ -61,7 +61,7 @@ Siga os passos abaixo para importar a planilha:
 2. Clique em __Selecionar__ para escolher o arquivo com a planilha preenchida no seu computador.
 3. Clique em `Importar`.
 
-![skuexport3.pt](//images.ctfassets.net/alneenqid6w5/4KnRQf8W5vHakt5FNyHup0/0a7cbb37721b6110065c14599f0288d7/skuexport3.pt.png)
+![skuexport3.pt](https://images.ctfassets.net/alneenqid6w5/4KnRQf8W5vHakt5FNyHup0/0a7cbb37721b6110065c14599f0288d7/skuexport3.pt.png)
 
 ## Saiba mais
 - [Especificações de produto e de SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP)
diff --git a/docs/tutorials/pt/facebook-faq.md b/docs/tutorials/pt/facebook-faq.md
index 820a3fbd0..d752623d4 100644
--- a/docs/tutorials/pt/facebook-faq.md
+++ b/docs/tutorials/pt/facebook-faq.md
@@ -36,7 +36,7 @@ O primeiro passo a se investigar nesse cenário é se realmente o SKU não possu
 
 Caso o SKU possua um preço, verifique o status desse SKU pois o erro também pode estar relacionado com a situação de ativo/inativo. A melhor forma de fazer isso é realizando uma simulação de checkout:
 
-![face faq01](//images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
+![face faq01](https://images.ctfassets.net/alneenqid6w5/6PFO5g1ZrT0uv7uWLdWNmT/c7b62f12066bdb95f7c45d533b2bb460/face_faq01.JPG)
 
 Nessa simulação é importante analisar os campos:
 
diff --git a/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md b/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md
index 6a0917a85..ca61c914d 100644
--- a/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md
+++ b/docs/tutorials/pt/facebook-liberacao-de-dominio-suiteshare.md
@@ -20,7 +20,7 @@ Como o lançamento do iOS 14 da Apple pode afetar os seus anúncios e relatório
 Se você planeja veicular anúncios otimizados para eventos de conversão que ocorrem no site do VTEX Assisted Sales (SuiteShare), você deve nos informar o seu **número de identificação do Gerenciador de Negócios**, para isso bastar seguir os passos a seguir: 
 
 1. Você pode encontrar o seu Número de identificação do Gerenciador de Negócios, acessando `https://business.facebook.com/settings/info` conforme imagem abaixo:
-![facebook liberação de domínio](//images.ctfassets.net/alneenqid6w5/8upBYK7kQ4JPmnchLkNfz/07b08fedc1d9d8863d0bca7ebc455d02/image.png)
+![facebook liberação de domínio](https://images.ctfassets.net/alneenqid6w5/8upBYK7kQ4JPmnchLkNfz/07b08fedc1d9d8863d0bca7ebc455d02/image.png)
 2. Assim que obter o seu número de identificação, [CLIQUE AQUI](\"https://suit.sh/liberacao-de-dominio\") para realizar a solicitação de liberação. Dentro de um prazo de 48 horas você será notificado por email, informando sobre a finalização do processo de liberação.
 
 Saiba mais:
diff --git a/docs/tutorials/pt/facilitating-b2b-store-operation.md b/docs/tutorials/pt/facilitating-b2b-store-operation.md
index bfebac48d..6ec613233 100644
--- a/docs/tutorials/pt/facilitating-b2b-store-operation.md
+++ b/docs/tutorials/pt/facilitating-b2b-store-operation.md
@@ -91,7 +91,7 @@ Todas as lojas VTEX contam com o [My account](https://help.vtex.com/pt/tutorial/
 
 Essa ferramenta permite que o cliente acompanhe o status do seu pedido no fluxo do pós-venda, bem como faça algumas operações. Uma delas é a de “Pedir novamente”, na qual é possível repetir um pedido feito previamente.  
 
-![Pedir novamente reorder](//images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
+![Pedir novamente reorder](https://images.ctfassets.net/alneenqid6w5/1t7B2SNKQ9aJZ4gFE03ViD/8ba194685df6e2374b7e287fb0ed59bc/image.png)
 
 Para saber mais detalhes sobre o My Account, confira o tutorial sobre [como configurar esta funcionalidade](https://help.vtex.com/pt/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1 "como configurar esta funcionalidade").
 
diff --git a/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 2165748a7..474c1e0f1 100644
--- a/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -17,7 +17,7 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 
 Para entender melhor o significado de cada campo da planilha de cadastro de preço fixo, veja a descrição completa dos itens abaixo.
 
-![tabela.preço.fixo](//images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
+![tabela.preço.fixo](https://images.ctfassets.net/alneenqid6w5/6V1yGMgHF0NP5pzZzcSOCF/cc9369da09f81cafaeac1fc73ac61aa1/tabela.pre__o.fixo.png)
 
 - **SKU ID:** ID do SKU que deseja adicionar o preço fixo.
 - **Trade Policy:** nome ou ID da política comercial em que o preço fixo será aplicado.
diff --git a/docs/tutorials/pt/filtering-all-orders.md b/docs/tutorials/pt/filtering-all-orders.md
index 507294ba7..0f7966021 100644
--- a/docs/tutorials/pt/filtering-all-orders.md
+++ b/docs/tutorials/pt/filtering-all-orders.md
@@ -21,7 +21,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 No módulo **Pedidos**, a página **Todos os pedidos** permite a você acessar os pedidos da sua loja e pesquisar usando a barra de busca e filtros, como na imagem abaixo:
 
-![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Este artigo explica como utilizar estes recursos e se divide em:
 
@@ -63,7 +63,7 @@ Buscar em todos os pedidos retorna a totalidade de pedidos relacionados ao crit
 
 Para buscar em todos os pedidos, digite o termo desejado na caixa de busca. Isso fará com que a opção <i class="fas fa-toggle-on"></i> `Remover limite de datas` se torne visível. Depois basta ativá-la e isso dará início à busca.
 
-![search_bar_without_time_limit_PT](//images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c87949487d1e9ad947ea437c3f368431/search_bar_without_time_limit_PT.png)
+![search_bar_without_time_limit_PT](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c87949487d1e9ad947ea437c3f368431/search_bar_without_time_limit_PT.png)
 
 <div class="alert alert-danger">
 A busca em todos os pedidos não pode ser associada a outros filtros. Ou seja, ao remover o limite de datas da busca, qualquer filtro ativo se torna inativo. Se o termo da busca é removido ou o switch <i class="fas fa-toggle-off"></i> de busca em todos os pedidos é desativado, os filtros anteriormente configurados se tornam ativos novamente.
@@ -81,7 +81,7 @@ Realizar uma busca associada a filtros permite que você combine diferentes filt
 
 Na página **Pedidos > Todos os pedidos**, existe a opção `Filtros`, conforme a imagem abaixo:
 
-![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Ao clicar em `Filtros`, um modal é aberto e apresenta as seguintes opções:
 
@@ -197,7 +197,7 @@ Para utilizar esses filtros, clique em `Filtros` e selecione **Outros**. Você p
 
 Na página **Pedidos > Todos os pedidos**, existe a opção `Filtrar por status` <i class="fas fa-angle-down"></i>, conforme imagem abaixo:
 
-![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Ao clicar em `Filtrar por status` <i class="fas fa-angle-down"></i>, aparecem as opções de [status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196) da sua loja. Por exemplo, se entre todos os seus pedidos não houver pedidos cancelados, esta opção não estará visível.
 
@@ -209,7 +209,7 @@ Para mais opções de filtros de status, veja a seção <a href="https://help.vt
 
 Na página **Pedidos > Todos os pedidos**, existe a opção `Criado: Hoje` <i class="fas fa-angle-down"></i>, conforme imagem abaixo:
 
-![search_bar_PT](//images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
+![search_bar_PT](https://images.ctfassets.net/alneenqid6w5/1aPXtEWSmO3isVQ5k1GF3z/ebb51c0719e6c1db7e9af1ec1b53ab2d/search_bar_PT.png)
 
 Este filtro tem a data **Hoje** ativada de forma padrão, mas ao clicar nele aparecem as seguintes opções:
 
diff --git a/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
index 6533869dc..3e6633d41 100644
--- a/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -21,7 +21,7 @@ Note que o Marketplace Network é uma ferramenta que promove o contato entre pot
 
 ## Encontrar Sellers e Marketplaces
 
-![Marketplace network tour](//images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
+![Marketplace network tour](https://images.ctfassets.net/alneenqid6w5/1dSZvVeBP1yyJ1Ai5xuX12/884c2b263f35ef7e8fbffee7cb23ba84/Marketplace_network_tour.gif)
 
 Para acessar a listagem de marketplaces e sellers cadastrados navegue em *Marketplace > Marketplace Network > Encontrar Sellers / Encontrar Marketplaces*. Em ambas abas, é possível  buscar por palavras-chave e filtrar a lista para obter resultados mais precisos, além de entrar em contato com potenciais parceiros.
 
@@ -44,7 +44,7 @@ O potencial parceiro comercial receberá um e-mail com as informações preenchi
 </div>
 
 ## Perfil da loja
-![Network profile PT](//images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/3566eb996b94604d3449fa0ae773cf27/Marketplace_store_profile_PT.gif)
+![Network profile PT](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/3566eb996b94604d3449fa0ae773cf27/Marketplace_store_profile_PT.gif)
 
 1. Na seção *Marketplace* da sua loja, clique em __Marketplace Network__.  
 2. Clique na aba __Perfil da Loja__.  
diff --git a/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
index 280abdb25..44ae01702 100644
--- a/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
@@ -26,7 +26,7 @@ A partir de 1 de fevereiro de 2023, a nova interface será o padrão de todas as
 
 Você pode visualizar a correspondência de seções e campos entre a versão antiga da página **Detalhes do pedido** e a nova versão na imagem abaixo:
 
-![board_comparativo_interface_pedido_v2_pt](//images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
+![board_comparativo_interface_pedido_v2_pt](https://images.ctfassets.net/alneenqid6w5/30tYehAYOCvQoX0MpSIoNH/70f75ff7e98e67c9c403c32965ab4882/board_comparativo_interface_pedido_v2_pt.png)
 
 ## O que aconteceu com o filtro de busca de seis meses?
 
@@ -38,17 +38,17 @@ A busca em todos os pedidos não pode ser associada a outros filtros, portanto,
 
 Para buscar em todos os pedidos, digite o termo desejado na caixa de busca. Isso fará com que a opção <i class="fas fa-toggle-off"></i> `Remover limite de datas` se torne visível. Depois basta ativá-la e isso dará início à busca.
 
-![busca_sem_limite_data_all_pt](//images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
+![busca_sem_limite_data_all_pt](https://images.ctfassets.net/alneenqid6w5/7mDlDQAgphKCmH12REooCx/b6fee3d3358a18d7fe217d8afc005ca3/busca_sem_limite_data_all_pt.png)
 
 ## Como visualizar o diagrama de fluxo do pedido?
 
 Na nova interface, por padrão, o que é exibido é uma linha tempo com os eventos de **Status do pedido**, como na imagem abaixo:
 
-![timeline_pedido_pt](//images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/c062ec0b49a67aaecd9856a5bbec865b/timeline_pedido_pt.png)
+![timeline_pedido_pt](https://images.ctfassets.net/alneenqid6w5/JID8bYMxBA94nRGXJQ3BI/c062ec0b49a67aaecd9856a5bbec865b/timeline_pedido_pt.png)
 
 Caso você deseje ver o **Diagrama do pedido** como na interface antiga, clique em `Ver diagrama` e um modal como o da imagem abaixo vai aparecer:
 
-![diagrama_pedido_pt](//images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
+![diagrama_pedido_pt](https://images.ctfassets.net/alneenqid6w5/3to0oQYzjgz3Y5i4sDPIG3/20ac041bccaef4e607b082b1e6a346d0/diagrama_pedido_pt.png)
 
 ## Como faturar o pedido?
 
@@ -56,7 +56,7 @@ Na seção **Itens a faturar** da nova interface, todas as ações relacionadas
 
 * **Enviar nota fiscal referenciando itens:** esta opção é exclusiva da nova interface. Por meio dela, é possível emitir a nota fiscal total ou parcial de determinados itens, que são identificados por SKU, estoque e preço. Veja um exemplo na imagem a seguir:
 
-![faturar_referenciar_pedidos_final_pt](//images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/cef5f7a10b488a14945a0f210d464aea/faturar_referenciar_pedidos_final_pt.png)
+![faturar_referenciar_pedidos_final_pt](https://images.ctfassets.net/alneenqid6w5/3h0sV3Gq2dkJk3ZoT85SyG/cef5f7a10b488a14945a0f210d464aea/faturar_referenciar_pedidos_final_pt.png)
 
 * **Enviar nota fiscal avulsa:** a opção corresponde ao antigo _Enviar nota fiscal_ e permite faturar o valor total ou parcial do pedido. A apresentação da página é diferente, mas os campos permanecem os mesmos.
 
@@ -75,6 +75,6 @@ Na nova interface, dentro da seção **Histórico do pedido**, existe uma linha
 
 Para reenviar um email para o cliente, clique no evento de email enviado ou no ícone seta <i class="fas fa-angle-right"></i> para ver os detalhes do evento, que vão aparecer como na imagem a seguir:
 
-![enviar_email_pt](//images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/f59d8a815163c889d8af29cd4e04ccbd/enviar_email_pt.png)
+![enviar_email_pt](https://images.ctfassets.net/alneenqid6w5/5c2ZuqUC1b497RQdImDQ46/f59d8a815163c889d8af29cd4e04ccbd/enviar_email_pt.png)
 
 Clique sobre o botão `Reenviar email` e o email será imediatamente enviado ao cliente, sendo que a seguinte mensagem de confirmação deve aparecer: _Email reenviado ao cliente com sucesso_.
diff --git a/docs/tutorials/pt/fulfillment-logistics-vtex.md b/docs/tutorials/pt/fulfillment-logistics-vtex.md
index 50205d747..98a72a504 100644
--- a/docs/tutorials/pt/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/pt/fulfillment-logistics-vtex.md
@@ -47,7 +47,7 @@ Para saber quais configurações logísticas são necessárias e como são reali
 Note que o processo de envio dependerá das configurações realizadas na plataforma. Aqui apresentamos  os cenários para cada tipo de envio (entrega e retirada), mas há outros fluxos possíveis no processo de envio. Por exemplo, quando o envio é por retirada e o estoque coincide com o ponto de retirada, não é necessário o transporte dos pacotes entre esses locais.
 </div>
 
-![Envio PT](//images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/186ee5138e0d5d412c9eb50890708241/Envio_PT.svg)
+![Envio PT](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/186ee5138e0d5d412c9eb50890708241/Envio_PT.svg)
 
 ## Configuração do processo logístico
 
diff --git a/docs/tutorials/pt/fulfillment-magalu.md b/docs/tutorials/pt/fulfillment-magalu.md
index c9ecf24c1..d5c17a1a8 100644
--- a/docs/tutorials/pt/fulfillment-magalu.md
+++ b/docs/tutorials/pt/fulfillment-magalu.md
@@ -121,6 +121,6 @@ Com as etapas de [Configuração da loja](#configuracao-da-loja) e [Configuraç
 5. Preencha o campo `Estoque do fulfillment` com o Id do estoque cadastrado em Configuração da loja.
 6. Clique em `Salvar`.
 
-![Fulfillment magalu](//images.ctfassets.net/alneenqid6w5/5boAjRcCbzyFflEolDZaFu/fc0e47a429a0ef940f5f20dd1c0db747/Screenshot_2023-12-08_at_13.26.50__1_.png)  
+![Fulfillment magalu](https://images.ctfassets.net/alneenqid6w5/5boAjRcCbzyFflEolDZaFu/fc0e47a429a0ef940f5f20dd1c0db747/Screenshot_2023-12-08_at_13.26.50__1_.png)  
 
 Ao finalizar o processo de configuração do conector, os seus produtos configurados estarão disponíveis no Magalu Marketplace com a opção de envio __Fulfillment Magalu.__
diff --git a/docs/tutorials/pt/general-configurations-on-the-oms.md b/docs/tutorials/pt/general-configurations-on-the-oms.md
index ecc3a3f82..7359e29e9 100644
--- a/docs/tutorials/pt/general-configurations-on-the-oms.md
+++ b/docs/tutorials/pt/general-configurations-on-the-oms.md
@@ -19,7 +19,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 No Admin VTEX, acesse **Configurações da loja > Pedidos > Configurações**, ou digite *Pedidos* na barra de busca no topo da página e e selecione *Configurações da loja / Pedidos*. 
 
-![configuracoes_pedidos_pt](//images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/743fdbe79371cf6f3f7a43ca340102d2/configuracoes_pedidos_pt.png)
+![configuracoes_pedidos_pt](https://images.ctfassets.net/alneenqid6w5/3Pg3IFrgPiGdwsIJowvNBy/743fdbe79371cf6f3f7a43ca340102d2/configuracoes_pedidos_pt.png)
 
 ## Carrinho
 
diff --git a/docs/tutorials/pt/generating-a-har-file.md b/docs/tutorials/pt/generating-a-har-file.md
index eef2e5dc9..8e5e89a2f 100644
--- a/docs/tutorials/pt/generating-a-har-file.md
+++ b/docs/tutorials/pt/generating-a-har-file.md
@@ -33,12 +33,12 @@ O arquivo HAR contém informações sensíveis sobre sua loja. Compartilhe-o som
 Usando o Google Chrome, siga os passos abaixo para gerar o arquivo HAR.
 
 1. Navegue até a URL onde o problema está ocorrendo.
-2. Clique com o botão direito em qualquer lugar da tela e então em __Inspecionar__.![HARfile1](//images.contentful.com/alneenqid6w5/3BZmZ6hkXuueWCMuM4Ykke/e58e1a4fb669de93808ceee862847f56/HARfile1.png)
-3. O Dev Tools será aberto, então clique na aba __Network__.![HARfile2](//images.contentful.com/alneenqid6w5/7vSYRmkjduq6iCaiGgyIo/fd3f3eb23fa57582f8c8f5cd1ac725b5/HARfile2.png)
-4. O botão de gravação deve estar vermelho, o que indica que está ativado. Se não estiver, clique nele.![HARfile3](//images.contentful.com/alneenqid6w5/6YnW3ebd1mq2kQsm8uKG2q/97000a534abfabc66931d27ff9cd28b8/HARfile3.png)
-5. Marque a flag __Preserve log__.![HARfile5](//images.contentful.com/alneenqid6w5/xQAIiEuHIsaoSCUkSsOEE/e6dc32f580a2f50a5789ae39babfb540/HARfile5.png)
+2. Clique com o botão direito em qualquer lugar da tela e então em __Inspecionar__.![HARfile1](https://images.contentful.com/alneenqid6w5/3BZmZ6hkXuueWCMuM4Ykke/e58e1a4fb669de93808ceee862847f56/HARfile1.png)
+3. O Dev Tools será aberto, então clique na aba __Network__.![HARfile2](https://images.contentful.com/alneenqid6w5/7vSYRmkjduq6iCaiGgyIo/fd3f3eb23fa57582f8c8f5cd1ac725b5/HARfile2.png)
+4. O botão de gravação deve estar vermelho, o que indica que está ativado. Se não estiver, clique nele.![HARfile3](https://images.contentful.com/alneenqid6w5/6YnW3ebd1mq2kQsm8uKG2q/97000a534abfabc66931d27ff9cd28b8/HARfile3.png)
+5. Marque a flag __Preserve log__.![HARfile5](https://images.contentful.com/alneenqid6w5/xQAIiEuHIsaoSCUkSsOEE/e6dc32f580a2f50a5789ae39babfb540/HARfile5.png)
 6. Recarregue a página e reproduza a navegação na qual ocorre o problema.
-7. Clique com o botão direito em qualquer lugar dentro da área do Network e depois clique na opção __Save as HAR with content__.![HARfile4](//images.contentful.com/alneenqid6w5/hR0VTzzNFmyQc4A4KS02G/b1f15e2131e21b80f5f2c97023cd0a5b/HARfile4.png)
+7. Clique com o botão direito em qualquer lugar dentro da área do Network e depois clique na opção __Save as HAR with content__.![HARfile4](https://images.contentful.com/alneenqid6w5/hR0VTzzNFmyQc4A4KS02G/b1f15e2131e21b80f5f2c97023cd0a5b/HARfile4.png)
 
 Será gerado um arquivo com extensão HAR, cujo nome é o endereço da página.
 
diff --git a/docs/tutorials/pt/geolocalizado-suiteshare.md b/docs/tutorials/pt/geolocalizado-suiteshare.md
index af1193ea7..e373de4f5 100644
--- a/docs/tutorials/pt/geolocalizado-suiteshare.md
+++ b/docs/tutorials/pt/geolocalizado-suiteshare.md
@@ -27,17 +27,17 @@ Uma empresa que possui lojas em vários cidades (Ex: São Paulo, Rio de Janeiro,
 
 Para começar você deve ter [criado os links](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB)  que serão utilizados no seu atendimento e um link âncora.  Depois de ter criado os links no painel do VTEX Assisted Sales (SuiteShare), acesse a opção _**Organizar > Geolocalização.**_
 
-![Geolocalizado 1](//images.ctfassets.net/alneenqid6w5/4l9dgcmAdSNdgj0PUaKVC8/db334a7cdc6a13954e62d94fbd7ebb0a/Screenshot_2022-08-29_at_17-59-43_Geolocalizado.png)
+![Geolocalizado 1](https://images.ctfassets.net/alneenqid6w5/4l9dgcmAdSNdgj0PUaKVC8/db334a7cdc6a13954e62d94fbd7ebb0a/Screenshot_2022-08-29_at_17-59-43_Geolocalizado.png)
 
 Clique em _**“Novo”**_.
 
-![Geolocalizado 2](//images.ctfassets.net/alneenqid6w5/4Q7Q0Rnkz4UYR85akhHQAh/78deaaef0fc5a328b5bee90eb3a043fb/Screenshot_2022-08-29_at_17-59-47_Geolocalizado.png)
+![Geolocalizado 2](https://images.ctfassets.net/alneenqid6w5/4Q7Q0Rnkz4UYR85akhHQAh/78deaaef0fc5a328b5bee90eb3a043fb/Screenshot_2022-08-29_at_17-59-47_Geolocalizado.png)
 
 Em **Link Âncora**, como o próprio nome já diz, você irá selecionar o link principal da central. Esse é o link que você irá divulgar e que os clientes irão clicar. 
 
 **Nota**: Esse será o link responsável por fazer a ligação com os demais atendentes.
 
-![Geolocalizado 3](//images.ctfassets.net/alneenqid6w5/1VNj6ggD6sFyXtYDojXVKv/aacec6cba54332300bfc899de4c0fed5/Screenshot_2022-08-29_at_17-59-51_Geolocalizado.png)
+![Geolocalizado 3](https://images.ctfassets.net/alneenqid6w5/1VNj6ggD6sFyXtYDojXVKv/aacec6cba54332300bfc899de4c0fed5/Screenshot_2022-08-29_at_17-59-51_Geolocalizado.png)
 
 O link whts.co/geolocalizado  sera o link principal. Nesse link está cadastrado o número de telefone da Matriz da Loja Teste que fica no Rio de Janeiro. 
 
@@ -47,11 +47,11 @@ O link whts.co/geolocalizado  sera o link principal. Nesse link está cadastrad
 
 Clique em _**“Avançar”**_.
 
-![Geolocalizado  4](//images.ctfassets.net/alneenqid6w5/1KIRHBEqDhssJV76yEaszd/15f59999569923cc82a1dd06146190fb/Screenshot_2022-08-29_at_18-00-00_Geolocalizado.png)
+![Geolocalizado  4](https://images.ctfassets.net/alneenqid6w5/1KIRHBEqDhssJV76yEaszd/15f59999569923cc82a1dd06146190fb/Screenshot_2022-08-29_at_18-00-00_Geolocalizado.png)
 
 Em Links Geolocalizados,selecione os vendedores ou números,  que irão participar da central. Clique em **_“Adicionar”_,** selecione o estado e a região e selecione o link para cada participante da central.
 
-![Geolocalizado 5](//images.ctfassets.net/alneenqid6w5/5hq88ccviJz56OJpv9jJdi/1d32fa1d927326fe58fdcfd7cdbb0309/Screenshot_2022-08-29_at_18-00-04_Geolocalizado.png)
+![Geolocalizado 5](https://images.ctfassets.net/alneenqid6w5/5hq88ccviJz56OJpv9jJdi/1d32fa1d927326fe58fdcfd7cdbb0309/Screenshot_2022-08-29_at_18-00-04_Geolocalizado.png)
 
 **IMPORTANTE:** No exemplo definimos por estados e não por cidades, mas você também pode definir somente por cidades.
 
diff --git a/docs/tutorials/pt/geolocation-at-checkout.md b/docs/tutorials/pt/geolocation-at-checkout.md
index b4295183c..7afb57cd8 100644
--- a/docs/tutorials/pt/geolocation-at-checkout.md
+++ b/docs/tutorials/pt/geolocation-at-checkout.md
@@ -42,7 +42,7 @@ Com a API Key em mãos, siga os passos abaixo:
 1. No Admin VTEX, acesse __Configurações da loja > Envio > Envio por geolocalização__, ou digite __Envio por geolocalização__ na barra de busca no topo da página.
 2. Insira a API Key no campo disponível e clique em __Cadastrar chave__.
 
-![Geolocalizacao 1 PT](//images.ctfassets.net/alneenqid6w5/1WnSV74cA82WY8kGscAiy2/68eeec258fd124695047187dc5e15b51/Geolocalizacao_1_PT.png)
+![Geolocalizacao 1 PT](https://images.ctfassets.net/alneenqid6w5/1WnSV74cA82WY8kGscAiy2/68eeec258fd124695047187dc5e15b51/Geolocalizacao_1_PT.png)
 
 <div class="alert alert-info">
 Em alguns países, o Google Maps não realiza um mapping de alta qualidade. Com isso, pode acontecer de certos endereços serem mal escritos ou de o Google indicar um endereço incorreto. Nestes casos, deve-se corrigir o endereço diretamente no mapa.
@@ -63,7 +63,7 @@ Após criar o polígono e inserir seu ID na planilha de frete, você precisará
 3. No menu de opções azul localizado na parte superior da página, clique em __Checkout__.
 4. No campo __Google Maps API Key__, insira a mesma API Key informada na etapa de logística.
 
-![Google map keys](//images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/31ccb9fd38c90109da5d9dfb9a825c71/google_maps_api_key_pt.PNG)
+![Google map keys](https://images.ctfassets.net/alneenqid6w5/5Fly0uJ3DE9SmlK6I1oRNx/31ccb9fd38c90109da5d9dfb9a825c71/google_maps_api_key_pt.PNG)
 
 Assim que a API Key for informada nas configurações do Checkout, a geolocalização já estará visível no checkout da sua loja.
 
diff --git a/docs/tutorials/pt/google-pay-beta.md b/docs/tutorials/pt/google-pay-beta.md
index 48c95eb67..d263d0927 100644
--- a/docs/tutorials/pt/google-pay-beta.md
+++ b/docs/tutorials/pt/google-pay-beta.md
@@ -40,7 +40,7 @@ Para ativar o Google Pay, siga o passo a passo abaixo.
 
 Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como nova forma de pagamento. É possível que demore em torno de 10 minutos para que a configuração apareça no Checkout.
 
-![google pay - PT](//images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/a8bca906bd64bf229ac9521848a7c029/image.png)
+![google pay - PT](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/a8bca906bd64bf229ac9521848a7c029/image.png)
 
 <div class="alert alert-warning">
 <p>Google Pay, neste momento, não vai suportar assinatura.</p>
diff --git a/docs/tutorials/pt/google-search-console-tracking-sitemap.md b/docs/tutorials/pt/google-search-console-tracking-sitemap.md
index ccdb214e4..0ccb64a8d 100644
--- a/docs/tutorials/pt/google-search-console-tracking-sitemap.md
+++ b/docs/tutorials/pt/google-search-console-tracking-sitemap.md
@@ -35,7 +35,7 @@ Para cadastar o Sitemap você deve executar as seguites ações:
 
 **2. Selecione a opção **Sitemaps** na sessão **Rastreamento****
 
-****![](//images.contentful.com/alneenqid6w5/4ZbMabhWNO6cWaqOKQauGA/e0a6c544f7990e7203a89c63761ce7ea/image00.png)****
+****![](https://images.contentful.com/alneenqid6w5/4ZbMabhWNO6cWaqOKQauGA/e0a6c544f7990e7203a89c63761ce7ea/image00.png)****
 
 **3. Clique no botão **Adicionar / Testar Sitemap****
 
@@ -43,13 +43,13 @@ Para cadastar o Sitemap você deve executar as seguites ações:
 
 **5. **Clique em **Enviar Sitemap****
 
-****![](//images.contentful.com/alneenqid6w5/5WlIFTSGm4MGc6Wg6a24qY/8b1ae91bbedfdd5bcae4e255cd649784/image01.png)****
+****![](https://images.contentful.com/alneenqid6w5/5WlIFTSGm4MGc6Wg6a24qY/8b1ae91bbedfdd5bcae4e255cd649784/image01.png)****
 
 **6. O Search Console irá acessar o XML e verificar, clique na opção **Atualize a página** para visualizar o status das urls do sitemap enviado**
 
-**![](//images.contentful.com/alneenqid6w5/4H9Cm60mooYeeeEy0cOOaW/9d714db622a05eeda0dc52042b83aaf8/image02.png)**
+**![](https://images.contentful.com/alneenqid6w5/4H9Cm60mooYeeeEy0cOOaW/9d714db622a05eeda0dc52042b83aaf8/image02.png)**
 
 **7. Após adicionar com sucesso o sitemap no Search Console, a ferramenta disponibilizará o relatório de todas as URLs enviadas versus indexadas, segmentando por **Páginas da Web** e **Imagens**:**
 
-**![](//images.contentful.com/alneenqid6w5/6e0WHJD0YMCaWIkE4Kcgm/db32fa9488506be988d648554c3e3c42/image03.png)**
+**![](https://images.contentful.com/alneenqid6w5/6e0WHJD0YMCaWIkE4Kcgm/db32fa9488506be988d648554c3e3c42/image03.png)**
 
diff --git a/docs/tutorials/pt/headless-cms-overview.md b/docs/tutorials/pt/headless-cms-overview.md
index c61a90f6a..42bf13367 100644
--- a/docs/tutorials/pt/headless-cms-overview.md
+++ b/docs/tutorials/pt/headless-cms-overview.md
@@ -35,7 +35,7 @@ Com o Headless CMS, você pode:
 
 [Projetos](https://help.vtex.com/pt/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM) é uma funcionalidade do Headless CMS que permite criar e gerenciar vários projetos de frontend, como aplicativos móveis, sites e email marketing em um único painel de controle.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
 
 Para mais informações, acesse o artigo [Gerenciando Projetos](https://help.vtex.com/en/tutorial/managing-projects--42IpDFqTVTESH8DCypJMPM).
 
diff --git a/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
index 2a3f25f91..2261d96f3 100644
--- a/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
@@ -26,7 +26,7 @@ A plataforma VTEX é preparada para suportar mudanças de domínios sem impactos
 No License Manager, em Contas, será necessário incluir o novo domínio como HOST da loja. Nesse momento, o DNS do novo domínio ainda não deve estar apontado para a VTEX. 
 
 Esta imagem exemplifica a inclusão de novos HOSTs que deve ser aplicada:
-![Mudar Domínio](//images.ctfassets.net/alneenqid6w5/1AUt1cydWg2W04wc02EKKM/36c9a17ccee114cf38f48c5ba07973e7/626-pt.png)
+![Mudar Domínio](https://images.ctfassets.net/alneenqid6w5/1AUt1cydWg2W04wc02EKKM/36c9a17ccee114cf38f48c5ba07973e7/626-pt.png)
 
 ### 2. Conferir configurações do novo Portal
 Esse passo é fundamental para que o Checkout continue funcionando após a mudança. É necessário conferir se os Sites configurados estão relacionados a algum Accoount Name inexistente no License Manager. [Leia mais sobre configurações do portal aqui](/pt/faq/configurar-template-no-smartcheckout/).
diff --git a/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
index f5f3eb858..8d02dc86d 100644
--- a/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
@@ -45,7 +45,7 @@ Confira o passo a passo:
 
 <div class="alert alert-info">Mais informações sobre <strong>Configurações gerais</strong> e <strong>Configurações de busca e de filtro</strong> podem ser encontradas na sessão <strong>Como configurar</strong> do artigo <a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Criar entidade de dados</a>.</div>
 
-![criar campo master data ds](//images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
+![criar campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
 Desse modo, você retornará para a página de principal da aba Entidade de Dados. Para finalizar, você precisa publicar o campo. Basta localizar a linha da entidade em que o campo foi adicionado e clicar no ícone disquete.
 
@@ -70,6 +70,6 @@ Dito isso, prossiga com as instruções:
 7. Arraste o campo da lista Campos disponíveis para as colunas Campos da coluna 1 ou Campos da coluna 2;
 8. No canto inferior direito da tela, clique no botão azul Salvar.
 
-![criar campo master data CRM](//images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
+![criar campo master data CRM](https://images.ctfassets.net/alneenqid6w5/2ykQ9Vx7FCZLehkQpxMMmp/0b52e7bc11fc024e74c5223b8e534b65/criar_campo_master_data_CRM.gif)
 
 Pronto! Assim, os campos serão exibidos no formulário.
diff --git a/docs/tutorials/pt/how-can-i-create-callcenter-user.md b/docs/tutorials/pt/how-can-i-create-callcenter-user.md
index b96a63b25..ea7e9fcdc 100644
--- a/docs/tutorials/pt/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/pt/how-can-i-create-callcenter-user.md
@@ -41,7 +41,7 @@ Para criar um usuário com perfil de televendas, siga os seguintes passos:
 
 7. Clique no botão **Salvar**.
 
-![GIF animado mostrando como criar usuário televendas](//images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/575304556410712f649e94cda1b3bdce/Adicionar_perfil.gif)
+![GIF animado mostrando como criar usuário televendas](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/575304556410712f649e94cda1b3bdce/Adicionar_perfil.gif)
 
 <div class="alert alert-warning">
   Ao criar um <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evite incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
diff --git a/docs/tutorials/pt/how-can-i-make-master-data-field-editable.md b/docs/tutorials/pt/how-can-i-make-master-data-field-editable.md
index 9017d9312..8fd0dbc58 100644
--- a/docs/tutorials/pt/how-can-i-make-master-data-field-editable.md
+++ b/docs/tutorials/pt/how-can-i-make-master-data-field-editable.md
@@ -19,15 +19,15 @@ Um campo editável é um campo em algum formulário do Master Data em que é pos
 
 Porém, por padrão, nem todos os campos possuem esta configuração no Master Data e para alterá-la basta seguir os passos abaixo.
 
-![campos](//images.contentful.com/alneenqid6w5/3atXWmH28w2eWYYwmuOU4i/d095cda45c25502d516e4ffb7e354f19/campos.png)
+![campos](https://images.contentful.com/alneenqid6w5/3atXWmH28w2eWYYwmuOU4i/d095cda45c25502d516e4ffb7e354f19/campos.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
 2. Na aplicação desejada, clique no símbolo de engrenagem.
 3. Clique no símbolo de editar (lápis) sobre o formulário que deseja alterar.
 4. Clique na aba **Schemas de Layout.**
-5. No campo desejado, clique no símbolo de lápis. ![editar](//images.contentful.com/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/39ee7ee0056fb8404cebac9eede86613/editar.png)
-6. Desmarque a opção **Exibir campo somente para leitura.** ![edicao](//images.contentful.com/alneenqid6w5/pa0JBBIXNAkQaYQm4swwS/58c3520c7393412fa3e4fe8cd6c0ec3d/edicao.png)
+5. No campo desejado, clique no símbolo de lápis. ![editar](https://images.contentful.com/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/39ee7ee0056fb8404cebac9eede86613/editar.png)
+6. Desmarque a opção **Exibir campo somente para leitura.** ![edicao](https://images.contentful.com/alneenqid6w5/pa0JBBIXNAkQaYQm4swwS/58c3520c7393412fa3e4fe8cd6c0ec3d/edicao.png)
 7. Clique no botão **OK.**
 8. Clique no botão **Salvar.**
 
-Pronto! Os campos alterados estarão disponíveis para edição. ![editaveis](//images.contentful.com/alneenqid6w5/3qv3k2OOXSEYOMCQ0Kmogu/0e989baedd9050f3fb7aa9a137d3efdf/editaveis.png)
+Pronto! Os campos alterados estarão disponíveis para edição. ![editaveis](https://images.contentful.com/alneenqid6w5/3qv3k2OOXSEYOMCQ0Kmogu/0e989baedd9050f3fb7aa9a137d3efdf/editaveis.png)
diff --git a/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md b/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md
index a4f64dda2..e9fb33d69 100644
--- a/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md
+++ b/docs/tutorials/pt/how-can-i-track-the-status-of-my-disputes.md
@@ -25,7 +25,7 @@ Eis algumas delas.
 
 Quando o usuário acessa a seção **Disputas**, os processos são exibidos em uma única tela. Contudo, as disputas deixam de ser apresentadas na seção **Disputas** quando se tornam chargeback (7 dias após serem abertas). Ou seja, uma vez que a devolução do dinheiro é feita para o cliente, a disputa é fechada e “some” da exibição.
 
-![disputa-vtex-payment](//images.ctfassets.net/alneenqid6w5/5E3vzxX10nWod99okmR5Ey/5afc15fd3c9b3bfb57d9d55ddd51f4f8/image.png)
+![disputa-vtex-payment](https://images.ctfassets.net/alneenqid6w5/5E3vzxX10nWod99okmR5Ey/5afc15fd3c9b3bfb57d9d55ddd51f4f8/image.png)
 
 ## Consulta de disputa única
 
diff --git a/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md b/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md
index 67b1f8bd9..0308faa48 100644
--- a/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md
+++ b/docs/tutorials/pt/how-can-my-customer-login-to-my-store.md
@@ -28,7 +28,7 @@ O objetivo deste artigo é mostrar como o cliente da sua loja deve fazer login n
 
 Ao clicar em um link para se autenticar, o cliente verá a tela de login.
 
-![vtex-id-pt](//images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/d7e784ef2c14aad7a01faef0e94f5c19/vtex-id-en.png)
+![vtex-id-pt](https://images.ctfassets.net/alneenqid6w5/32ihh602XeY6WyECG6YkwG/d7e784ef2c14aad7a01faef0e94f5c19/vtex-id-en.png)
 
 Existem três formas padrão de se fazer login numa loja VTEX:
 
@@ -43,9 +43,9 @@ Este tipo de login __envia um token de acesso para o e-mail do usuário__ para q
 Para o cliente fazer login por esse método, ele deve seguir os passos abaixo:
 
 1. Na tela de login, o usuário deve clicar em __Receber chave de acesso rápido por email__
-2. Na tela seguinte, o usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-3. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-4. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Entrar__ ![fill-access-token-pt](//images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
+2. Na tela seguinte, o usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+3. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+4. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Entrar__ ![fill-access-token-pt](https://images.ctfassets.net/alneenqid6w5/1a4ACAuZt0koYYW8myAqUQ/0ac63d1ce81e2bd8f57d8e6dc68c0b7c/fill-access-token-pt.png)
 
 ### Entrar com email e senha
 
@@ -56,11 +56,11 @@ Este tipo de login __solicita email e senha__ para que o cliente possa se autent
 - Caso o cliente precise __cadastrar uma senha__, ele deve seguir os passos abaixo:
 
 1. Na tela de login, o usuário deve clicar em __Entrar com email e senha__
-2. Na tela seguinte, o usuário deve clicar em  __Não tem uma senha? Cadastre agora__ ![register-password-pt](//images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
-3. O usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](//images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
-4. Na tela seguinte, o usuário deve escrever sua nova senha nos campos __Nova senha__ e __Confirmar nova senha__ e, então, clicar no botão __Cadastrar nova senha__ ![register-new-password-pt](//images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
-5. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](//images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
-6. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Alterar senha__ ![change-password-pt](//images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)    
+2. Na tela seguinte, o usuário deve clicar em  __Não tem uma senha? Cadastre agora__ ![register-password-pt](https://images.ctfassets.net/alneenqid6w5/2sE6VwOjqAoAQsKGemwCGs/3f61e50940015953828a9248e00b8568/register-password-pt.png)
+3. O usuário deve preencher seu email e clicar no botão __Confirmar__ ![fill-mail-pt](https://images.ctfassets.net/alneenqid6w5/5OXLHK0kY8aqCOuyuuaayQ/4667578a18947906d39ed393c5d8f56f/fill-mail-pt.png)
+4. Na tela seguinte, o usuário deve escrever sua nova senha nos campos __Nova senha__ e __Confirmar nova senha__ e, então, clicar no botão __Cadastrar nova senha__ ![register-new-password-pt](https://images.ctfassets.net/alneenqid6w5/2gqFHdXAxauM0Mkooqyau/ef26bb6203e301e7c2cc8d6aa26e0a2a/register-new-password-pt.png)
+5. __Um token de acesso será enviado para o email informado no passo anterior__. Caso o cliente não tenha recebido o e-mail, peça que ele verifique se digitou o email corretamente. Além disso, é necessário que o cliente verifique o lixo eletrônico para garantir que a chave de acesso não tenha caído no filtro de *spam*. O token possui 6 números. ![code-pt](https://images.ctfassets.net/alneenqid6w5/5eqO3wQ7MImsaMGOeK6Gk8/eff44ac34f23646467b09f389394eb33/code-pt.png)
+6. Retorne à tela de login e __digite a chave de acesso__ recebida no passo anterior e clique em __Alterar senha__ ![change-password-pt](https://images.ctfassets.net/alneenqid6w5/mbczqOea2GsMYaYeaSeSK/365e6278b0e1ed300866a47661af1fca/change-password-pt.png)    
 
 ### Login por rede social
 
diff --git a/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index ed1f0d91f..788ebc7f7 100644
--- a/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -33,16 +33,16 @@ O módulo Layout abrange a home, catálogo (busca, categorias e produtos), landi
 2. Acesse **Sites and channels**.
 3. Acesse o website desejado.
 4. Abra a pasta raiz do website.
-![instrução CMS -pt](//images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
+![instrução CMS -pt](https://images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
 5. A tela que foi aberta apresenta todas as pastas que estão no primeiro nível do site. Para cada pasta pertinente, clique em **Edit** - para a home, considere o botão do topo;
-![CMS edit PT](//images.ctfassets.net/alneenqid6w5/1kHZcohcNawW2AEU6sKAAC/834bb139945132df8e23bd0b8dc9360f/edit_CMS.png)
+![CMS edit PT](https://images.ctfassets.net/alneenqid6w5/1kHZcohcNawW2AEU6sKAAC/834bb139945132df8e23bd0b8dc9360f/edit_CMS.png)
 6. Na caixa de seleção **Protocol**, selecione a opção **HTTPS**;
-![CMS: protocol HTTPS ](//images.ctfassets.net/alneenqid6w5/4d64p6oOPuWgMcAmmeqiKY/062e9c9ec3423f8ed6344436c07f8544/HTTPS.png)
+![CMS: protocol HTTPS ](https://images.ctfassets.net/alneenqid6w5/4d64p6oOPuWgMcAmmeqiKY/062e9c9ec3423f8ed6344436c07f8544/HTTPS.png)
 7. Clique em **Save Folder**.
 
 Atenção às pastas que possuem subpastas, como Departamento, Categoria, Produto e outras pastas, incluindo também as criadas para customização da loja. 
 
 No exemplo a seguir, a pasta dinâmica **@Categoria@**, contida em **Categoria**, que deve ser também editada: 
-![cms: subcategoria edit](//images.ctfassets.net/alneenqid6w5/7GQxgjBhRKomoSSicuMMeE/530405e8da5a8f61ccdfb1ca3285ffdd/subcategoria_edit.png)
+![cms: subcategoria edit](https://images.ctfassets.net/alneenqid6w5/7GQxgjBhRKomoSSicuMMeE/530405e8da5a8f61ccdfb1ca3285ffdd/subcategoria_edit.png)
 
 Após cache de até 10 minutos as alterções irão vigorar.
diff --git a/docs/tutorials/pt/how-do-you-calculate-payments-in-installments-with-compound-interest.md b/docs/tutorials/pt/how-do-you-calculate-payments-in-installments-with-compound-interest.md
index 3f7ef2a9d..aec2481b3 100644
--- a/docs/tutorials/pt/how-do-you-calculate-payments-in-installments-with-compound-interest.md
+++ b/docs/tutorials/pt/how-do-you-calculate-payments-in-installments-with-compound-interest.md
@@ -26,7 +26,7 @@ A cobrança no início do período é calculada da seguinte forma:
 1. i = Taxa de Juros
 2. n = Número de Parcelas
 3. PV = Valor Presente (valor total da compra sem juros)
-4. Parcela = ![juros-inicio-periodo](//images.contentful.com/alneenqid6w5/3JkoK4GMLYAWIwUcAC8W2G/59d18849c4ee9e59ff37cb09ac661c89/juros-inicio-periodo.png)
+4. Parcela = ![juros-inicio-periodo](https://images.contentful.com/alneenqid6w5/3JkoK4GMLYAWIwUcAC8W2G/59d18849c4ee9e59ff37cb09ac661c89/juros-inicio-periodo.png)
 
 ## Fim do período
 
@@ -35,7 +35,7 @@ A cobrança no fim do período é calculada da seguinte forma:
 1. i = Taxa de Juros
 2. n = Número de Parcelas
 3. PV = Valor Presente (valor total da compra sem juros)
-4. Multiplicador Cash Flow =![cash-flow](//images.contentful.com/alneenqid6w5/2xvT7uQ8ccGoCUw8ouOEoK/936546d7e46be7b9ce984c531daf5e8b/cash-flow.png)
+4. Multiplicador Cash Flow =![cash-flow](https://images.contentful.com/alneenqid6w5/2xvT7uQ8ccGoCUw8ouOEoK/936546d7e46be7b9ce984c531daf5e8b/cash-flow.png)
 5. Parcela = `PV x Multiplicador Cash Flow`
 
 ## Exemplos
@@ -45,7 +45,7 @@ A cobrança no fim do período é calculada da seguinte forma:
 1. i = 1%
 2. n = 12
 3. PV = 1000
-![conta0](//images.contentful.com/alneenqid6w5/3AhidhqtTaCqiuGMKK2c64/8c5e8f0067ad5ec80685bdcca8d79c95/conta0.png)
+![conta0](https://images.contentful.com/alneenqid6w5/3AhidhqtTaCqiuGMKK2c64/8c5e8f0067ad5ec80685bdcca8d79c95/conta0.png)
 
 ---
 
@@ -54,4 +54,4 @@ A cobrança no fim do período é calculada da seguinte forma:
 1. i = 1%
 2. n = 12
 3. PV = 1000
-4. ![conta1](//images.contentful.com/alneenqid6w5/4CaAz5DKdaUSY0OwaGEsUu/4afb38b8c7a78977d011f2d6333800d6/conta1.png)![conta2](//images.contentful.com/alneenqid6w5/3hQTOBVJqgMAyMWWia0aAY/5f7fbb82ebeb8b5e912baca35ea39b9b/conta2.png)
+4. ![conta1](https://images.contentful.com/alneenqid6w5/4CaAz5DKdaUSY0OwaGEsUu/4afb38b8c7a78977d011f2d6333800d6/conta1.png)![conta2](https://images.contentful.com/alneenqid6w5/3hQTOBVJqgMAyMWWia0aAY/5f7fbb82ebeb8b5e912baca35ea39b9b/conta2.png)
diff --git a/docs/tutorials/pt/how-does-promotion-proration-work.md b/docs/tutorials/pt/how-does-promotion-proration-work.md
index 2d7d5da54..dab6b0e8f 100644
--- a/docs/tutorials/pt/how-does-promotion-proration-work.md
+++ b/docs/tutorials/pt/how-does-promotion-proration-work.md
@@ -37,7 +37,7 @@ Digamos que temos uma promoção de desconto nominal no valor de R$ 156,00 para
 - Produto D: R$ 150,00.
 
 Considerando a lógica de cálculo acima, ficaria da seguinte forma:
-![](//images.contentful.com/alneenqid6w5/7qc6lyh1oACGmWsIOOiiCC/28e3fe1dffdc8f21040a57ff0e9364ff/Exemplo_de_rateio.JPG)
+![](https://images.contentful.com/alneenqid6w5/7qc6lyh1oACGmWsIOOiiCC/28e3fe1dffdc8f21040a57ff0e9364ff/Exemplo_de_rateio.JPG)
 
 Esse cálculo é aplicado para produtos unitários, como uma blusa ou uma mesa, mas também existem produtos que têm em seu cadastro uma configuração chamada de unidade multiplicadora, como uma caixa de piso com 2,5 m², por exemplo.
 
diff --git a/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index f40475e0f..3d0b16af3 100644
--- a/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -31,7 +31,7 @@ Em vez de usar os IDs de cada item (o que geraria pedidos separados em nosso sis
 
 Você pode encontrar os dois IDs através do relatório enviado a partir do painel de integrações no Admin da VTEX.
 
-![Pedidos Mercado Livre](//images.ctfassets.net/alneenqid6w5/2NFqrrWGlqQMYSOugYo8kQ/deba1c9f1ffb01e0db3f2874fb7ee8a3/Pedidos_Mercado_Livre.png)
+![Pedidos Mercado Livre](https://images.ctfassets.net/alneenqid6w5/2NFqrrWGlqQMYSOugYo8kQ/deba1c9f1ffb01e0db3f2874fb7ee8a3/Pedidos_Mercado_Livre.png)
 
 <div class="alert alert-warning">
 Essa lógica de funcionamento se aplica a todos os tipos de entrega, com exceção daqueles que incluem pickup points. Nesses casos, a plataforma continua a utilizar o ID antigo.
diff --git a/docs/tutorials/pt/how-does-the-delivery-flow-work.md b/docs/tutorials/pt/how-does-the-delivery-flow-work.md
index 61d59be88..87174d647 100644
--- a/docs/tutorials/pt/how-does-the-delivery-flow-work.md
+++ b/docs/tutorials/pt/how-does-the-delivery-flow-work.md
@@ -27,4 +27,4 @@ A plataforma VTEX dá liberdade para que sua loja use essas configurações de d
 
 Mas, por enquanto, vamos nos ater ao cenário mais básico, ilustrado pela figura abaixo:
 
-![Logistics Concept](//images.contentful.com/alneenqid6w5/4fomReyldS6UYoyC6GEYqE/32a9ff98dc0aa61163892bd5ce1aaa06/Logistics_Concept.png)
+![Logistics Concept](https://images.contentful.com/alneenqid6w5/4fomReyldS6UYoyC6GEYqE/32a9ff98dc0aa61163892bd5ce1aaa06/Logistics_Concept.png)
diff --git a/docs/tutorials/pt/how-does-the-score-field-work.md b/docs/tutorials/pt/how-does-the-score-field-work.md
index 7eeb403ca..f9922b745 100644
--- a/docs/tutorials/pt/how-does-the-score-field-work.md
+++ b/docs/tutorials/pt/how-does-the-score-field-work.md
@@ -54,4 +54,4 @@ Para adicionar ou alterar um score relacionado a um produto, siga estes passos:
 2. Clique em `Adicionar Produto` para criar um novo produto ou clique em `Alterar` no produto que deseja editar.
 3. Insira o valor desejado do score no campo **Score (usado para ordenação de busca)**.
 
-![posicao-Score-PT](//images.ctfassets.net/alneenqid6w5/6SGu9GBtxou7sLg5rM59vl/f02f302fc3de0346b7ec9d794c413da3/Screenshot_6.png)
+![posicao-Score-PT](https://images.ctfassets.net/alneenqid6w5/6SGu9GBtxou7sLg5rM59vl/f02f302fc3de0346b7ec9d794c413da3/Screenshot_6.png)
diff --git a/docs/tutorials/pt/how-does-the-search-context-on-website-folders-operate.md b/docs/tutorials/pt/how-does-the-search-context-on-website-folders-operate.md
index 86b320e04..93fc84a38 100644
--- a/docs/tutorials/pt/how-does-the-search-context-on-website-folders-operate.md
+++ b/docs/tutorials/pt/how-does-the-search-context-on-website-folders-operate.md
@@ -39,7 +39,7 @@ Usando o mesmo exemplo anterior, se criarmos uma pasta chamada **minha-landing-p
 
 ### Configuração
 
-![](//images.contentful.com/alneenqid6w5/ZvEGMDPUs0OsuCkoUsqqS/4411604b8b78124edcbacd46cc45ed53/ContextoDeBusca.PNG)
+![](https://images.contentful.com/alneenqid6w5/ZvEGMDPUs0OsuCkoUsqqS/4411604b8b78124edcbacd46cc45ed53/ContextoDeBusca.PNG)
 
 **Importante**:
 
diff --git a/docs/tutorials/pt/how-does-the-type-of-delivery-work.md b/docs/tutorials/pt/how-does-the-type-of-delivery-work.md
index c37123b41..7c93d45e2 100644
--- a/docs/tutorials/pt/how-does-the-type-of-delivery-work.md
+++ b/docs/tutorials/pt/how-does-the-type-of-delivery-work.md
@@ -29,7 +29,7 @@ No carrinho, não são exibidos os nomes das transportadoras e sim os tipos de
 
 Segue uma imagem de como seriam exibidas as opções de frete no fechamento de compra de acordo com o exemplo citado:
 
-![Transportadoras Checkout](//images.ctfassets.net/alneenqid6w5/1c85gOqY9uokEQ2UGI4YAI/87dd9e5eeb8d1a45233e80ce1b7b8de3/Transportadoras_Checkout.png)
+![Transportadoras Checkout](https://images.ctfassets.net/alneenqid6w5/1c85gOqY9uokEQ2UGI4YAI/87dd9e5eeb8d1a45233e80ce1b7b8de3/Transportadoras_Checkout.png)
 
 Note que, mesmo tendo cinco transportadoras cadastradas, só aparecem duas opções de frete: **Agendado** e **Normal**. Isso acontece por dois motivos: 
 
diff --git a/docs/tutorials/pt/how-does-vtex-search-work.md b/docs/tutorials/pt/how-does-vtex-search-work.md
index cc02a2b54..ca117f444 100644
--- a/docs/tutorials/pt/how-does-vtex-search-work.md
+++ b/docs/tutorials/pt/how-does-vtex-search-work.md
@@ -76,7 +76,7 @@ Para entender a busca da VTEX, inicialmente é preciso saber como funciona o i
 
 O indexador do catálogo é uma base de dados escalável de acesso rápido, com algorítimos configuráveis de priorização de resultado. Ele está posicionado entre o banco de dados convencional e o usuário. Veja o esquema abaixo:
 
-![](//images.contentful.com/alneenqid6w5/4PSR97lU5y2iac2QkoUAKg/10b9097341faf0de317fa6984104da95/indexacao.png)
+![](https://images.contentful.com/alneenqid6w5/4PSR97lU5y2iac2QkoUAKg/10b9097341faf0de317fa6984104da95/indexacao.png)
 
 No indexador encontramos todas as informações referentes ao catálogo de produtos (produtos, SKUs, marcas, departamentos, categorias). O buscador utiliza essas informações para localizar os produtos e exibi-los nas vitrines e resultados de busca. Portanto, somente os produtos indexados podem ser encontrados pela busca.
 
diff --git a/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md b/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md
index 401bd64d0..f3f5ac5a4 100644
--- a/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md
+++ b/docs/tutorials/pt/how-is-pro-rata-calculated-in-vtex.md
@@ -21,6 +21,6 @@ A conta do desconto é: `monthly fee dividido pelo número de dias do mês de co
 
 Então, se a sua mensalidade teve um valor de R$ 750 no mês de maio - 31 dias - e você contratou a VTEX no dia 06 de maio, serão descontados R$ 145,16 em sua próxima fatura.
 
-![prorata PT](//images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
+![prorata PT](https://images.ctfassets.net/alneenqid6w5/3FEz6ikQqcaQmkys4Wgq0U/4a992dad8bcb8e6db9cdcfa8ccddbfe5/prorata_PT.png)
 
 A conta feita foi: `R$ 750/31 = R$ 24,19 x 3 (dias) = R$ 145,16`
diff --git a/docs/tutorials/pt/how-is-taxhub-api-rest-structure.md b/docs/tutorials/pt/how-is-taxhub-api-rest-structure.md
index 002c758ca..892165a13 100644
--- a/docs/tutorials/pt/how-is-taxhub-api-rest-structure.md
+++ b/docs/tutorials/pt/how-is-taxhub-api-rest-structure.md
@@ -52,7 +52,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubAPIGetTax](//images.contentful.com/alneenqid6w5/4CaoACwzqEYcUQem6okKQO/0e295bc9101cc0b46e7669a49b6f99e3/TaxHubAPIGetTax.jpg)
+![TaxHubAPIGetTax](https://images.contentful.com/alneenqid6w5/4CaoACwzqEYcUQem6okKQO/0e295bc9101cc0b46e7669a49b6f99e3/TaxHubAPIGetTax.jpg)
 
 __2 Occupation Area__
 
@@ -99,7 +99,7 @@ Response:
 ```
  
 Evidence:
-![TaxHubOccupationArea](//images.contentful.com/alneenqid6w5/2lJDIuKFz6AwgM62eI6aWA/c0bab0f8e5016e3ced947cfb94050d43/TaxHubOccupationArea.jpg)
+![TaxHubOccupationArea](https://images.contentful.com/alneenqid6w5/2lJDIuKFz6AwgM62eI6aWA/c0bab0f8e5016e3ced947cfb94050d43/TaxHubOccupationArea.jpg)
 
 __3 FiscalRegion__
 
@@ -137,7 +137,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubFiscalRegion](//images.contentful.com/alneenqid6w5/3i7TuC4rJYwoIWY62UwgE0/5cfc50a55c0e068a2dea68573a636a1b/TaxHubFiscalRegion.jpg)
+![TaxHubFiscalRegion](https://images.contentful.com/alneenqid6w5/3i7TuC4rJYwoIWY62UwgE0/5cfc50a55c0e068a2dea68573a636a1b/TaxHubFiscalRegion.jpg)
 
 __4	CustomerCode__
 - Host: http://api.beta.vtex.com
@@ -171,7 +171,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubCustomerCode](//images.contentful.com/alneenqid6w5/5ANPppLxvikIK4Kkaoe6qM/3d5033469dc13154c1bae8ddaeb02c06/TaxHubCustomerCode.jpg)
+![TaxHubCustomerCode](https://images.contentful.com/alneenqid6w5/5ANPppLxvikIK4Kkaoe6qM/3d5033469dc13154c1bae8ddaeb02c06/TaxHubCustomerCode.jpg)
 
 __5	ItemCode__
 
@@ -207,7 +207,7 @@ Response:
 
 Evicence:
 
-![TaxHubItemCode](//images.contentful.com/alneenqid6w5/4im391LOekSmYIgWgeqIIK/078dbcbb83861e5b90d9b0b9519778e5/TaxHubItemCode.jpg)
+![TaxHubItemCode](https://images.contentful.com/alneenqid6w5/4im391LOekSmYIgWgeqIIK/078dbcbb83861e5b90d9b0b9519778e5/TaxHubItemCode.jpg)
 
 __6 Aliquot__
 - Host: http://api.beta.vtex.com
@@ -244,7 +244,7 @@ Response:
 ```
 
 Evidence:
-![TaxHubAliquot](//images.contentful.com/alneenqid6w5/6d6Kgove5GaWM2As0EAqmg/6959389c39c4d0c69cccd1982ccf7c6e/TaxHubAliquot.jpg)
+![TaxHubAliquot](https://images.contentful.com/alneenqid6w5/6d6Kgove5GaWM2As0EAqmg/6959389c39c4d0c69cccd1982ccf7c6e/TaxHubAliquot.jpg)
 
 __7 TaxValue__
 
@@ -292,6 +292,6 @@ Response:
 ```
 
 Evidence:
-![TaxHubTaxValue](//images.contentful.com/alneenqid6w5/53rujXNKTYs0kugAMwSca8/53b29d1078e0960a39360bdad84e4b7e/TaxHubTaxValue.jpg)
+![TaxHubTaxValue](https://images.contentful.com/alneenqid6w5/53rujXNKTYs0kugAMwSca8/53b29d1078e0960a39360bdad84e4b7e/TaxHubTaxValue.jpg)
 
 [Continue lendo sobre o TaxHub com o artigo sobre a estructura em JS](http://help.vtex.com/pt/tutorial/como-e-a-estrutura-de-app-em-js-do-taxhub)
diff --git a/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md b/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md
index 96603982c..8c80ecc85 100644
--- a/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md
+++ b/docs/tutorials/pt/how-is-the-order-delivery-deadline-calculated.md
@@ -22,7 +22,7 @@ O prazo de envio de um pedido leva em consideração os seguintes aspectos da lo
 - [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
 - [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
 
-![lead_time_image_total_time_PT](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
+![lead_time_image_total_time_PT](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
 
 Você define um período para essas etapas e o prazo de envio que o seu cliente vê no checkout é uma soma desses períodos. 
 
diff --git a/docs/tutorials/pt/how-is-the-taxhub-app-structure-in-js.md b/docs/tutorials/pt/how-is-the-taxhub-app-structure-in-js.md
index 571fcbb36..4e1b860b8 100644
--- a/docs/tutorials/pt/how-is-the-taxhub-app-structure-in-js.md
+++ b/docs/tutorials/pt/how-is-the-taxhub-app-structure-in-js.md
@@ -34,7 +34,7 @@ Defina o nome do arquivo inicial, com o mesmo país da loja.
 Exemplo: argentina.js ou mexico.js, o arquivo .js da pasta principal e a pasta tem que ter o mesmo nome. A pasta IVA pode ter qualquer nome.
 
 A ordem de chamada que deve seguir também para o desenvolvimento:
-![TaxHubTree](//images.contentful.com/alneenqid6w5/5hPFG8m6pUCMuIg8e2Iymm/957b9c89844099db690e82abe53c2b7a/TxHubTree.jpg)
+![TaxHubTree](https://images.contentful.com/alneenqid6w5/5hPFG8m6pUCMuIg8e2Iymm/957b9c89844099db690e82abe53c2b7a/TxHubTree.jpg)
 
 Depois de fazer as alterações, é necessário fazer upload do arquivo à VTEX no formato .zip sempre com a mesma estrutura de pastas.
 
diff --git a/docs/tutorials/pt/how-my-account-works.md b/docs/tutorials/pt/how-my-account-works.md
index 2a957143d..ec841830f 100644
--- a/docs/tutorials/pt/how-my-account-works.md
+++ b/docs/tutorials/pt/how-my-account-works.md
@@ -34,7 +34,7 @@ Para saber sobre a customização da funcionalidade <b>Minha conta</b>, veja a d
 
 Nesta aba, o cliente pode gerenciar seus dados pessoais cadastrados na loja. É possível [editar as informações do perfil](#editar), [definir uma nova senha](#senha) e [escolher se deseja receber emails com promoções](#newsletter).
 
-![profile PT](//images.contentful.com/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/beab12f450f93773234132305ec3f5b0/profile_PT.png)
+![profile PT](https://images.contentful.com/alneenqid6w5/6LUXeCU09v8EOyMXntPggz/beab12f450f93773234132305ec3f5b0/profile_PT.png)
 
 ### Editar
 
@@ -83,7 +83,7 @@ Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJT
 
 Essa aba traz a listagem completa dos pedidos realizados pelo cliente na sua loja. A lista é ordenada por data de criação e exibe detalhes como data do pedido, valor total da compra, ID do pedido, status e itens adquiridos.
 
-![orders PT](//images.contentful.com/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/6f7d63f0581419353f76bc20429cd339/orders_PT.png)
+![orders PT](https://images.contentful.com/alneenqid6w5/1VTgMxrq3WI02LZt21wuw6/6f7d63f0581419353f76bc20429cd339/orders_PT.png)
 
 A aba **Pedidos** permite que o cliente acompanhe o andamento do pedido e realize solicitações como cancelamento e alteração.Veja abaixo todas as opções disponíveis.
 
@@ -108,7 +108,7 @@ Ao clicar em um pedido da listagem, o cliente poderá visualizar todos os detalh
 
 O cliente também pode [Pedir novamente](#pedir-novamente) a partir desta página. Ao clicar em `Mais opções`, são exibidas as funcionalidades de [Alterar pedido](#alterar-pedido) (caso esteja ativada e o pedido esteja no status `Preparando Entrega`) e [Solicitar cancelamento](#solicitar-cancelamento).
 
-![order details PT](//images.contentful.com/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/a86b441fbf95065f7654fbcbb4e68523/order_details_PT.png)
+![order details PT](https://images.contentful.com/alneenqid6w5/JQbiFPVtCl1Q8F6PaM0A0/a86b441fbf95065f7654fbcbb4e68523/order_details_PT.png)
 
 #### Alterar pedido
 
@@ -135,7 +135,7 @@ Para adicionar novos cartões, siga os passos abaixo:
 6. Resolva o desafio do reCaptcha.
 7. Ocorrerá um processo de validação do cartão automaticamente. Se não houver nenhum problema, você será redirecionado para a lista de cartões e o novo cartão irá aparecer na lista.
 
-![Card ReCaptcha](//images.contentful.com/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/01beb926fb436c05a10b74f7678b954c/Card_ReCaptcha_EN.gif)
+![Card ReCaptcha](https://images.contentful.com/alneenqid6w5/2xGRuG3f5S56POV684Q2Y3/01beb926fb436c05a10b74f7678b954c/Card_ReCaptcha_EN.gif)
 
 Contudo, existem limitações que precisam ser consideradas pelas lojas que utilizam a autenticação [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) (V1 ou V2) em suas adquirentes:
 
@@ -157,7 +157,7 @@ Nesta aba, o cliente pode gerenciar todas as suas assinaturas cadastradas, assim
 
 Esta aba pode ser acessada no painel esquerdo pelo item **Autenticação** nas configurações de perfil do usuário. Na aba são encontradas opções para gerenciamento de senha e gerenciamento de sessões.
 
-![My Authentication app PT](//images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
+![My Authentication app PT](https://images.ctfassets.net/alneenqid6w5/20aIW7imMlRsfDbKYu9IuM/1f8fe73f29fcee82f33e27aa07daa83f/My_Authentication_app_PT.png)
 
 ### Gerenciamento de senha
 
@@ -167,7 +167,7 @@ O componente **Senha** permite que o usuário crie uma senha (caso ainda não po
 2. No campo **Código**, insira o código de verificação recebido por email.
 3. No campo **Nova senha**, insira a nova senha que deseja atribuir à sua conta. Abaixo do campo aparecem os requisitos que a senha deve obedecer para ser válida. Conforme a senha é digitada, os símbolos de cada requisito se alteram de vermelho para verde. A senha será válida somente se todos os símbolos estiverem verdes.
 4. Após ter inserido uma senha válida, clique no botão `SALVAR SENHA` para concluir a criação da senha.  
-![My Authentication create password PT](//images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/3f8b8b62a8722e515edc0eae6322ff6a/My_Authentication_create_password_PT.png)
+![My Authentication create password PT](https://images.ctfassets.net/alneenqid6w5/5EDsOOYVAUmNolMnzs22FD/3f8b8b62a8722e515edc0eae6322ff6a/My_Authentication_create_password_PT.png)
 
 Para mudar a senha atual:
 
@@ -175,7 +175,7 @@ Para mudar a senha atual:
 2. Digite a senha atual no campo correspondente.
 3. Digite a nova senha no campo correspondente, obedecendo todos os requisitos.
 4. Clique no botão `SALVAR SENHA` para concluir a mudança de senha.  
-![My Authentication change password PT](//images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/94f7323e8d97d28a4d5dac042c5c620b/My_Authentication_change_password_PT.png)
+![My Authentication change password PT](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/94f7323e8d97d28a4d5dac042c5c620b/My_Authentication_change_password_PT.png)
 
 <div class="alert alert-info">
 Caso você tenha esquecido a senha, não é possível recuperá-la pelo componente de gerenciamento de senha. Para isso você deve sair da sessão atual, fazer uma tentativa de login usando email e senha, e clicar no link <strong>Esqueci minha senha</strong>.
@@ -189,7 +189,7 @@ Para visualizar as sessões ativas, clique no botão `VER SESSÕES` e você ser
 
 Para revogar o acesso das outras sessões, clique no botão `DESLOGAR` da sessão desejada.
 
-![My Authentication Session Management PT](//images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
+![My Authentication Session Management PT](https://images.ctfassets.net/alneenqid6w5/3qxpIRREWnGmRmv97jhOML/0b818eb59e66b445874945c9e0784e9c/My_Authentication_Session_Management_PT_blur.png)
 
 ## Configurações básicas
 
@@ -200,7 +200,7 @@ No **My Orders**, você pode determinar quais seções estarão visíveis para o
 * Em **ORDERS**, a opção <a class="far fa-check-square"></a> _Visible_ determina se o cliente tem a seção [Pedidos](#pedidos) para acompanhar seus pedidos.
 * Em **ADDRESSES**, a opção <a class="far fa-check-square"></a> _Visible_ define se o cliente vai ter a seção [Endereços](#enderecos) com detalhes do seu endereço.
 
-![vtex-my-account_PT](//images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/12452e82c19c105a9aae17c483531fe2/vtex-my-account_PT.png)
+![vtex-my-account_PT](https://images.ctfassets.net/alneenqid6w5/4x5BM7dpNcnjHagpycIeWt/12452e82c19c105a9aae17c483531fe2/vtex-my-account_PT.png)
 
 Por padrão, as opções **CARDS** e **ORDERS** vem configuradas como visíveis. Para alterá-las ou habilitar outras configurações, realize os passos abaixo: 
 
diff --git a/docs/tutorials/pt/how-order-authorization-works.md b/docs/tutorials/pt/how-order-authorization-works.md
index 47cf21904..6feaa2932 100644
--- a/docs/tutorials/pt/how-order-authorization-works.md
+++ b/docs/tutorials/pt/how-order-authorization-works.md
@@ -17,7 +17,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos**, é possível controlar a aprovação de pedidos com divergência de preços na sua loja.
 
-![print_autorizacao_pedidos_PT](//images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/92157acf2f5d379f30136b846e28a37f/print_autorizacao_pedidos_PT.png)
+![print_autorizacao_pedidos_PT](https://images.ctfassets.net/alneenqid6w5/3OSC6hxQchdd8SoWYwRI6l/92157acf2f5d379f30136b846e28a37f/print_autorizacao_pedidos_PT.png)
 
 A divergência de preços de pedidos podem ser encontradas em dois principais cenários:
 
diff --git a/docs/tutorials/pt/how-order-authorization-workss.md b/docs/tutorials/pt/how-order-authorization-workss.md
index a33a268e1..c56b6df26 100644
--- a/docs/tutorials/pt/how-order-authorization-workss.md
+++ b/docs/tutorials/pt/how-order-authorization-workss.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 No módulo de Gerenciamento de pedidos, a seção __Autorização de pedidos__ permite o controle e a aprovação de pedidos com divergências de preços na sua loja.
 
-![autorização-de-pedidos PT](//images.ctfassets.net/alneenqid6w5/2oP1np8C9Cv004b8NPk1Jn/a7694ae95272db05344bf35d93206e58/autoriza____o-de-pedidos__PT.png)
+![autorização-de-pedidos PT](https://images.ctfassets.net/alneenqid6w5/2oP1np8C9Cv004b8NPk1Jn/a7694ae95272db05344bf35d93206e58/autoriza____o-de-pedidos__PT.png)
 
 As divergências de preços entre pedidos podem ser encontradas em dois principais cenários: 
 
@@ -35,15 +35,15 @@ As regras de autorização são atribuídas a uma faixa percentual à sua escolh
 
 - De 0% a 10% de variação de preço, o pedido será aprovado automaticamente
 
-![regra-1-autorização-de-pedidos PT](//images.ctfassets.net/alneenqid6w5/1wohOoNoG0OrOU69zBxoPM/ff7ca27e0807785aae26bab5190271fc/regra-1-autoriza____o-de-pedidos_PT.png)
+![regra-1-autorização-de-pedidos PT](https://images.ctfassets.net/alneenqid6w5/1wohOoNoG0OrOU69zBxoPM/ff7ca27e0807785aae26bab5190271fc/regra-1-autoriza____o-de-pedidos_PT.png)
 
 - De 10% a 20% de variação de preço, o pedido será enviado para o usuário `usuario@exemplo.com.br` aprovar através de uma tarefa no VTEX DO
 
-![regra2-autorização-de-pedidos PT](//images.ctfassets.net/alneenqid6w5/XkBsErQYCMnQe4TQefwCL/b7cacd0f633c1768de1cb0b703785479/regra2-autoriza____o-de-pedidos_PT.png)
+![regra2-autorização-de-pedidos PT](https://images.ctfassets.net/alneenqid6w5/XkBsErQYCMnQe4TQefwCL/b7cacd0f633c1768de1cb0b703785479/regra2-autoriza____o-de-pedidos_PT.png)
 
 - De 20% a 100% de variação de preço, o pedido será negado automaticamente
 
-![regra3-autorização-de-pedidos pt](//images.ctfassets.net/alneenqid6w5/2t9asV03OYvCiscGKaws7m/2df3c008d6e802f0ecaf8d48b2b3d751/regra3-autoriza____o-de-pedidos_pt.png)
+![regra3-autorização-de-pedidos pt](https://images.ctfassets.net/alneenqid6w5/2t9asV03OYvCiscGKaws7m/2df3c008d6e802f0ecaf8d48b2b3d751/regra3-autoriza____o-de-pedidos_pt.png)
 
 Para a configuração da segunda regra, será necessário o cadastro de usuários com [permissões](https://help.vtex.com/tutorial/como-criar-perfil-de-acesso--tutorials_526) para aprovação de pedidos. 
 
diff --git a/docs/tutorials/pt/how-promotion-competition-works.md b/docs/tutorials/pt/how-promotion-competition-works.md
index 139a7554b..4fe353306 100644
--- a/docs/tutorials/pt/how-promotion-competition-works.md
+++ b/docs/tutorials/pt/how-promotion-competition-works.md
@@ -82,7 +82,7 @@ Todavia, elas incidem no valor já descontado pela promoção que ganhou a conco
 
 Logo, a sequência de aplicação é:
 
-![promocao3 PT](//images.ctfassets.net/alneenqid6w5/1LKDzbLkhua8Gk284SEwsk/997fdac9b6380c68a729bf4d48e20af8/promocao3_PT.png)
+![promocao3 PT](https://images.ctfassets.net/alneenqid6w5/1LKDzbLkhua8Gk284SEwsk/997fdac9b6380c68a729bf4d48e20af8/promocao3_PT.png)
 
 <div class="alert alert-warning">
 Pedidos de origem <a href="https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> e Fulfillment não reconhecem acúmulo de promoção, uma vez que o uso de promoções em Marketplaces VTEX ou externos é restrito a alguns tipos específicos.</div>
diff --git a/docs/tutorials/pt/how-recursive-marketplace-works.md b/docs/tutorials/pt/how-recursive-marketplace-works.md
index 1e62093ba..6b5b6847e 100644
--- a/docs/tutorials/pt/how-recursive-marketplace-works.md
+++ b/docs/tutorials/pt/how-recursive-marketplace-works.md
@@ -33,7 +33,7 @@ Dessa forma:
 
 - __Quando uma loja VTEX for intermediária no fluxo de um pedido__: pedido de cadeia com __Chain Workflow__:
 
-![marketplace-recursivo-chain-order-workflow](//images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
+![marketplace-recursivo-chain-order-workflow](https://images.ctfassets.net/alneenqid6w5/1mYtSFQxV7pnlrp746nnQ4/336550750f99d86b90851742fda8f724/marketplace-recursivo-chain-order-workflow.png)
 
 
 ## Configuração
diff --git a/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md b/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
index e637f9516..eacf95484 100644
--- a/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
+++ b/docs/tutorials/pt/how-shipping-works-when-delivery-is-done-by-the-marketplace.md
@@ -44,7 +44,7 @@ Assim como na interface do OMS, a API traz a informação `vtex:fob_1111` para o
 
 É importante que o ERP esteja adequado à recepção dos dados neste formato.
 
-![](//images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
+![](https://images.ctfassets.net/alneenqid6w5/5jPtBeUPHCUvgMco9FoKuZ/add1ce05e78a216f0aa7074c3ae4d444/slack-imgs.com.png)
 
 ## Etiqueta
 
@@ -52,6 +52,6 @@ O pedido é enviado em um contrato com os Correios do próprio marketplace. Nest
 
 É possível acessar a etiqueta diretamente pelo OMS, abaixo dos itens do pedido. Basta clicar no link e uma nova janela será aberta já com o PDF da etiqueta.
 
-![Etiqueta de entrega pelos Correios (BR) - Marketplace](//images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/e49eff1715dd0b3018bb58a6521f5c0c/Screen_Shot_2020-03-25_at_11.43.27.png)
+![Etiqueta de entrega pelos Correios (BR) - Marketplace](https://images.ctfassets.net/alneenqid6w5/3Xc7eqzjetqNwScoZxkWOK/e49eff1715dd0b3018bb58a6521f5c0c/Screen_Shot_2020-03-25_at_11.43.27.png)
 
 Caso queria aproveitar a etiqueta dentro do ERP, ela também está disponível em [Marketplace Protocol API](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/order-integration/orders), saiba mais em [New Order Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-collect-orders#scenario-12-order-with-tracking-hints).
diff --git a/docs/tutorials/pt/how-the-automatic-compacting-of-images-works.md b/docs/tutorials/pt/how-the-automatic-compacting-of-images-works.md
index 734c70378..8448d7908 100644
--- a/docs/tutorials/pt/how-the-automatic-compacting-of-images-works.md
+++ b/docs/tutorials/pt/how-the-automatic-compacting-of-images-works.md
@@ -17,7 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 As lojas VTEX contam com compatação automática de imagens para __WebP__. Este recurso possibilita uma redução de até 25% no peso do site.
 
-![webplogo](//images.contentful.com/alneenqid6w5/1HsHoCbkyM86KKA4sCWucO/0e6f078eb62b773cc927da79b8ea6f1e/webplogo.png)
+![webplogo](https://images.contentful.com/alneenqid6w5/1HsHoCbkyM86KKA4sCWucO/0e6f078eb62b773cc927da79b8ea6f1e/webplogo.png)
 
 O formato, desenvolvido pelo Google, é mais eficiente que o JPG ou o PNG, sem necessariamente reduzir a qualidade das imagens. Gera facilmente um ganho de 1 ou 2 segundos no tempo de carregamento das páginas (variando conforme o layout).
 
diff --git a/docs/tutorials/pt/how-the-documents-saving-flow-works.md b/docs/tutorials/pt/how-the-documents-saving-flow-works.md
index 6f8a262eb..8ac9f9b10 100644
--- a/docs/tutorials/pt/how-the-documents-saving-flow-works.md
+++ b/docs/tutorials/pt/how-the-documents-saving-flow-works.md
@@ -17,7 +17,7 @@ subcategory: 5gtjaqCG7eIseyCI0aSqc2
 
 A imagem abaixo mostra o fluxo interno de salvamento de documentos no Master Data. Vamos explicar cada passo.
 
-![Save flow](//images.contentful.com/alneenqid6w5/5klqkN1OEwMEq0aEQeMyIY/2ba2b7cc8e29a5ee0baad8be92aeef9a/MDSaveDiagram.png)
+![Save flow](https://images.contentful.com/alneenqid6w5/5klqkN1OEwMEq0aEQeMyIY/2ba2b7cc8e29a5ee0baad8be92aeef9a/MDSaveDiagram.png)
 
 #### Salvar chamada de API
 Ocorre quando o usuário chama a API de salvamento de documentos (POST, PUT ou PATCH).
diff --git a/docs/tutorials/pt/how-the-order-replacement-works.md b/docs/tutorials/pt/how-the-order-replacement-works.md
index 398962e77..dcbe75487 100644
--- a/docs/tutorials/pt/how-the-order-replacement-works.md
+++ b/docs/tutorials/pt/how-the-order-replacement-works.md
@@ -62,13 +62,13 @@ Além disso, não é possível fazer a substituição nos seguintes status de pe
 
 Com essa funcionalidade, os usuários da sua loja ganham uma página de Meus Pedidos redesenhada, com opções de alteração e cancelamento:
 
-![meu pedidos1 PT](//images.contentful.com/alneenqid6w5/3HQW2z7EfmokwYcWWCae8C/f0b0a251aecf8b2e140ad9a1ec2ee3c9/meu_pedidos1_PT.png)
+![meu pedidos1 PT](https://images.contentful.com/alneenqid6w5/3HQW2z7EfmokwYcWWCae8C/f0b0a251aecf8b2e140ad9a1ec2ee3c9/meu_pedidos1_PT.png)
 
-![meus pedidos3 PT](//images.ctfassets.net/alneenqid6w5/Np1Rhp4HIsQ6ocyOcqG4i/291263f717dd3da2ef8a027b5a1534e6/meus_pedidos3_PT.png)
+![meus pedidos3 PT](https://images.ctfassets.net/alneenqid6w5/Np1Rhp4HIsQ6ocyOcqG4i/291263f717dd3da2ef8a027b5a1534e6/meus_pedidos3_PT.png)
 
 Ao selecionar **Alterar pedido**, o cliente é levado para uma tela onde escolhe qual informação gostaria de substituir:
 
-![meus pedidos2 PT](//images.contentful.com/alneenqid6w5/3H4kcxj1Fm0Y0MkmouU2Sq/244d2ca249c117c42ecc7af26b5bfb4d/meus_pedidos2_PT.png)
+![meus pedidos2 PT](https://images.contentful.com/alneenqid6w5/3H4kcxj1Fm0Y0MkmouU2Sq/244d2ca249c117c42ecc7af26b5bfb4d/meus_pedidos2_PT.png)
 
 Para concluir a alteração, ele é levado para o carrinho e o Checkout, onde pode alterar endereço, tipo de frete, forma de pagamento e SKU.
 
diff --git a/docs/tutorials/pt/how-the-seller-portal-catalog-works.md b/docs/tutorials/pt/how-the-seller-portal-catalog-works.md
index eb8bcd484..a6ce64822 100644
--- a/docs/tutorials/pt/how-the-seller-portal-catalog-works.md
+++ b/docs/tutorials/pt/how-the-seller-portal-catalog-works.md
@@ -21,7 +21,7 @@ O Catálogo do Seller Portal é o módulo onde você configura o sortimento de p
 
 A arquitetura do Catálogo do Seller Portal se baseia em alguns conceitos fundamentais distribuídos na seguinte hierarquia:
 
-![ilustra-catalogo](//images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/95ac8458ebfd20bba03c8669a1e27fdf/ilustra-catalogo.png)
+![ilustra-catalogo](https://images.ctfassets.net/alneenqid6w5/3U5oa9w94stDXltSJPqF1V/95ac8458ebfd20bba03c8669a1e27fdf/ilustra-catalogo.png)
 
 - **Categorias:**  formas de organizar os seus produtos. Não é possível adicionar suas próprias Categorias, o marketplace é quem define as categorias disponíveis para enquadrar seus produtos. Cada produto estará obrigatoriamente relacionado a uma categoria já criada pelo marketplace.   
 - **Marcas:**  fazem parte dos atributos que caracterizam os Produtos da sua loja. Desta maneira, seus clientes também podem encontrar o que buscam de forma mais específica. Não é possível adicionar suas próprias marcas, as marcas na aba `Marcas` já foram importadas do marketplace.    
diff --git a/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md b/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md
index 605c78c50..f00d960de 100644
--- a/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md
+++ b/docs/tutorials/pt/how-to-activate-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 O app [Carrinho Compartilhável](https://apps.vtex.com/vtex-social-selling/p) permite que vendedores selecionem produtos para seus clientes e compartilhem o carrinho preenchido por canais como WhatsApp, Facebook Messenger e e-mail.
 
-![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artigo explica como instalar o app e configurar a funcionalidade na sua loja. Ao concluir os passos de ativação, seus vendedores poderão seguir as [instruções de uso](https://help.vtex.com/pt/tutorial/como-usar-o-app-carrinho-compartilhavel--3ePPpkmeZ96GXbeIoGZbTN) para iniciar suas estratégias de Social Selling.
 
@@ -83,7 +83,7 @@ Caso você queira customizar as cores dos botões da interface de compartilhamen
 
 Na imagem a seguir, a opção A apresenta as cores originais e a opção B uma customização possível.
 
-![shareable-cart-ui-customization](//images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
+![shareable-cart-ui-customization](https://images.ctfassets.net/alneenqid6w5/7qzGILGsBqu6sD2n052VQl/ba27c3afc9c744907ac707f10658e8e1/shareable-cart-ui-customization.png)
 
 O código abaixo deve ser adicionado no fim do arquivo `checkout5-custom.css` ou `checkout6-custom.css`, disponível para customização em *Configurações da Loja > Checkout > Código*. A escolha de qual deve ser editado depende da versão do Checkout utilizada pela sua loja.
 
diff --git a/docs/tutorials/pt/how-to-alter-a-banner.md b/docs/tutorials/pt/how-to-alter-a-banner.md
index ba79dab1c..49059dbe4 100644
--- a/docs/tutorials/pt/how-to-alter-a-banner.md
+++ b/docs/tutorials/pt/how-to-alter-a-banner.md
@@ -22,14 +22,14 @@ Usaremos como exemplo um banner da Home no passo-a-passo. Porém, estas instruç
 3. Clique na pasta **Sites and Channels**.
 4. Clique no nome do website desejado.
 5. Clique na pasta **/**.
-![instrução CMS -pt](//images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
+![instrução CMS -pt](https://images.ctfassets.net/alneenqid6w5/1lAXv0QTpq4YOSg2cu86Yi/5e6c2e3cfe424806118b20a9ef5e7b7b/CMS_instru____o.png)
 6. Clique no arquivo **Home**.
 7. Clique na aba **Settings**.
 8. Clique no ícone de lápis para editar.
-![cms-home-settings PT](//images.ctfassets.net/alneenqid6w5/5yEek4apQ4KCoKeSAoCEAY/9d4008ac0a2852da8eaa7fe801d093b1/banner_home_settings_-_pt.png)
+![cms-home-settings PT](https://images.ctfassets.net/alneenqid6w5/5yEek4apQ4KCoKeSAoCEAY/9d4008ac0a2852da8eaa7fe801d093b1/banner_home_settings_-_pt.png)
 9. Será aberta a janela de banners.
 10. Clique no ícone de lápis que aparecerá.
-![cms_home_settings_lapis pt](//images.ctfassets.net/alneenqid6w5/2ab0An97IMUK82aACeS2e4/8ded803db11dfb6e478d4de78749f903/cms_settings_lapis_pt.png)
+![cms_home_settings_lapis pt](https://images.ctfassets.net/alneenqid6w5/2ab0An97IMUK82aACeS2e4/8ded803db11dfb6e478d4de78749f903/cms_settings_lapis_pt.png)
 11. Será aberto o formulário de banner.
 
 **Altere o conteúdo do formulário:**
diff --git a/docs/tutorials/pt/how-to-archive-ratestaxes.md b/docs/tutorials/pt/how-to-archive-ratestaxes.md
index 0602769ea..ea317d49b 100644
--- a/docs/tutorials/pt/how-to-archive-ratestaxes.md
+++ b/docs/tutorials/pt/how-to-archive-ratestaxes.md
@@ -17,7 +17,7 @@ subcategory: 18Gsips3u48UYCu0Ku2sWm
 
 Caso queira que uma taxa criada não fique na lista principal por não ser mais utilizada, por exemplo, pode movê-la para a lista de arquivadas. Ao fazer isso, a taxa terá o status automaticamente alterado para inativo. Para fazer isso siga os passos abaixo:
 
-![exemplo1](//images.ctfassets.net/alneenqid6w5/3jvCIvAkHCyocKewGWa0aG/92224b98c19d15e58b734e1332ff6b0f/exemplo1.png)
+![exemplo1](https://images.ctfassets.net/alneenqid6w5/3jvCIvAkHCyocKewGWa0aG/92224b98c19d15e58b734e1332ff6b0f/exemplo1.png)
 
 1. No Admin VTEX, acesse *Promoções > Taxas*, ou digite *Taxas* na barra de busca no topo da página.
 3. Busque pela taxa que deseja arquivar.
diff --git a/docs/tutorials/pt/how-to-assemble-a-look-kit.md b/docs/tutorials/pt/how-to-assemble-a-look-kit.md
index 5c16b74bf..63cb30c50 100644
--- a/docs/tutorials/pt/how-to-assemble-a-look-kit.md
+++ b/docs/tutorials/pt/how-to-assemble-a-look-kit.md
@@ -35,13 +35,13 @@ Ou seja, o Kit é um novo produto composto por outros que podem, ou não, estar
 
 Esse termo é muito conhecido no segmento de Moda e Mobiliário. Um Kit Look é um modo que você consegue comprar vários produtos, visualizando apenas a tela de um produto.
 
-![](//images.contentful.com/alneenqid6w5/2WA6REAMecCaUiSEk2uoC6/999c983b772d8025d86f6ca2d1ebf3e4/kit-look-donadolook-exemplo.gif)
+![](https://images.contentful.com/alneenqid6w5/2WA6REAMecCaUiSEk2uoC6/999c983b772d8025d86f6ca2d1ebf3e4/kit-look-donadolook-exemplo.gif)
 
 No layout acima, é possível selecionar os itens do kit que o cliente gostaria de comprar e em seguida clicar em “Comprar Produtos Selecionados”.
 
 Ou se preferir comprar o kit completo, basta manter todos os itens selecionados.
 
-![](//images.contentful.com/alneenqid6w5/4ol1nKNyx2WYw26wQscgEE/986c00a0096dd93ac7c3ce206ecf049e/kit-look-jackthebarber-exemplo.gif)
+![](https://images.contentful.com/alneenqid6w5/4ol1nKNyx2WYw26wQscgEE/986c00a0096dd93ac7c3ce206ecf049e/kit-look-jackthebarber-exemplo.gif)
 
 Nesse layout cada item possui um botão de “Comprar Separadamente”.
 
@@ -130,7 +130,7 @@ Entenda a relação entre esses controles em [Lista Completa de Controles](/pt/t
 
 Este template deve ser associado a um novo Layout de Página de Produto, que será aplicado apenas na categoria onde os Kits estão cadastrados. Para criar uma nova página de produto selecione a pasta **_"Produto"_** e clique em **_"novo layout"_**.
 
-![2017-03-09 13_40_22-Index](//images.contentful.com/alneenqid6w5/3O4vfCLtriImIUukkwyIuM/6fabda711e9ca17e42389cfbb0ceeb33/2017-03-09-13_40_22-Index.png)
+![2017-03-09 13_40_22-Index](https://images.contentful.com/alneenqid6w5/3O4vfCLtriImIUukkwyIuM/6fabda711e9ca17e42389cfbb0ceeb33/2017-03-09-13_40_22-Index.png)
 
 Existe um limite de exibição de até 12 componentes para uma página de kit look. Para que não seja necessário criar vários templates diferentes, basta inserir mais vezes o mesmo código acima - alterando o valor de _**productIndex**_.
 
diff --git a/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
index 2fdd1ef35..58130741e 100644
--- a/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
@@ -21,11 +21,11 @@ Para saber qual o IP de um cliente que realizou um pedido na sua loja, basta ana
 
 Ao abrir um pedido, clique em __"Ver detalhes da transação"__ na caixa de pagamento:
 
-![ip pedido1 PT](//images.ctfassets.net/alneenqid6w5/6aXWqGSs9OSiaWaG4SYYcI/21acf3d8aa03a1d1133c776b85b76f09/ip_pedido1_PT.png)
+![ip pedido1 PT](https://images.ctfassets.net/alneenqid6w5/6aXWqGSs9OSiaWaG4SYYcI/21acf3d8aa03a1d1133c776b85b76f09/ip_pedido1_PT.png)
 
 O IP pode ser visualizado na parte superior direita:
 
-![ip pedido2 PT](//images.ctfassets.net/alneenqid6w5/5GWGCRtMWIMM0OwW86MeWG/4e4097ce9a8c5acdc388efac9ef38b9c/ip_pedido2_PT.png)
+![ip pedido2 PT](https://images.ctfassets.net/alneenqid6w5/5GWGCRtMWIMM0OwW86MeWG/4e4097ce9a8c5acdc388efac9ef38b9c/ip_pedido2_PT.png)
 
 Veja mais detalhes em: [Como visualizar detalhe do pedido](/pt/tutorial/como-visualizar-detalhes-do-pedido)
 
diff --git a/docs/tutorials/pt/how-to-change-orders-beta.md b/docs/tutorials/pt/how-to-change-orders-beta.md
index 1a1267b18..fc03dbc0b 100644
--- a/docs/tutorials/pt/how-to-change-orders-beta.md
+++ b/docs/tutorials/pt/how-to-change-orders-beta.md
@@ -93,7 +93,7 @@ Para adicionar um ou mais itens ao pedido, realize os seguintes passos:
 2. Na seção **A faturar**, clique em `Alterar itens`.
 3. Na página **Gerenciar itens do pedido**, clique na seta para cima <i class="fas fa-angle-up"></i> até o número da quantidade desejada, ou digite o número no campo. Feito isso, a página vai apresentar o preço e o número da quantidade anteriores tachados e vai aparecer a seguinte mensagem: _“Item editado”_.
 
-    ![change_order_adding_items_PT](//images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/ac1af94d506fdcd6be258f23cb51bd75/change_order_adding_items_PT.png)
+    ![change_order_adding_items_PT](https://images.ctfassets.net/alneenqid6w5/5dqVuyGULGm5TJH2tliSoO/ac1af94d506fdcd6be258f23cb51bd75/change_order_adding_items_PT.png)
 
 4. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
 5. Clique em `Revisar e aplicar`.
@@ -114,7 +114,7 @@ Para adicionar um ou mais produtos a um pedido, realize os seguintes passos:
   > Se você clicar sobre o nome do produto, você será redirecionado para a página do produto no site da loja.
 6. A seguir, clique em `Adicionar itens selecionados`. A seguinte mensagem vai aparecer: _“Itens adicionados”_.
 
-    ![change_order_adding_product_PT](//images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/1107b86fb89f9e1a76268693807bf4db/change_order_adding_product_PT.png)
+    ![change_order_adding_product_PT](https://images.ctfassets.net/alneenqid6w5/6a1gqq7WZiTO1lXZL26tU0/1107b86fb89f9e1a76268693807bf4db/change_order_adding_product_PT.png)
 
 7. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
 8. Clique em `Revisar e aplicar`.
@@ -131,7 +131,7 @@ Para remover um ou mais itens de um pedido, realize os seguintes passos:
 2. Na seção **A faturar**, clique em `Alterar itens`.
 3. Na página **Gerenciar itens do pedido**, clique na seta para baixo <i class="fas fa-angle-down"></i> até o número da quantidade desejada, ou digite o número no campo. Feito isso, a página apresenta o preço e o número da quantidade anteriores tachados e aparece a mensagem _“Item editado”_.
 
-    ![change_order_removing_items_PT](//images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/1ce6cbceb54dc71fe5da0bd37b2cd848/change_order_removing_items_PT.png)
+    ![change_order_removing_items_PT](https://images.ctfassets.net/alneenqid6w5/1fyXdA3TCu89tVktrQTFOr/1ce6cbceb54dc71fe5da0bd37b2cd848/change_order_removing_items_PT.png)
 
 4. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
 5. A seguir, clique em `Revisar e aplicar`.
@@ -148,7 +148,7 @@ Para excluir um produto de um pedido, realize os seguintes passos:
 2. Na seção **A faturar**, clique em `Alterar itens`.
 3. Na página **Gerenciar itens do pedido**, clique no ícone lixeira <i class="far fa-trash-alt"></i> `Remover item`. A seguinte mensagem de confirmação vai aparecer: _“Item removido”._
 
-    ![change_order_removing_product_PT](//images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/9130a233b2492ba003f4a93415bf16e1/change_order_removing_product_PT.png)
+    ![change_order_removing_product_PT](https://images.ctfassets.net/alneenqid6w5/6aN2IcHBxHHhFYIsy8ihRN/9130a233b2492ba003f4a93415bf16e1/change_order_removing_product_PT.png)
 
 4. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [everter uma alteração](#reverter-acoes).
 5. A seguir, clique em `Revisar e aplicar`.
@@ -183,7 +183,7 @@ Para alterar o peso de um item, realize os seguintes passos:
 3. Na página **Gerenciar itens do pedido**, na linha do produto desejado, digite o novo número do peso no campo. A unidade de medida vai estar especificada de acordo com as configurações no Catálogo. 
 4. Feito isso, a página apresenta o preço e o peso anteriores tachados e a mensagem _“Item editado”_.
 
-    ![change_order_changing_weight_PT](//images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/a34686dc7fa270893387038e3472595e/change_order_changing_weight_PT.png)
+    ![change_order_changing_weight_PT](https://images.ctfassets.net/alneenqid6w5/354LTV0LRZmcCXsB1oJkTw/a34686dc7fa270893387038e3472595e/change_order_changing_weight_PT.png)
 
 5. Revise os [detalhes do valor da alteração](#consultar-detalhes-dos-valores-da-alteracao). É possível [reverter uma alteração](#reverter-acoes).
 6. Clique em `Revisar e aplicar`.
@@ -204,7 +204,7 @@ Na página **Gerenciar itens do pedido**, enquanto você altera o pedido, o valo
 
 Na página **Gerenciar itens do pedido**, se você se arrepender de alguma alteração realizada, é possível desfazê-la. Para isso, clique no ícone seta curva `Desfazer ação`. Feito isso, uma mensagem de confirmação vai aparecer: _“Alteração desfeita”_, e a ação terá sido revertida.
 
-![change_order_undoing_actions_PT](//images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/049029b660f8db15b1846d3098a34ea6/change_order_undoing_actions_PT.png)
+![change_order_undoing_actions_PT](https://images.ctfassets.net/alneenqid6w5/GcSxHKn9jphCgi8eNQarG/049029b660f8db15b1846d3098a34ea6/change_order_undoing_actions_PT.png)
 
 ## Erros de processamento
 
diff --git a/docs/tutorials/pt/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md b/docs/tutorials/pt/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
index 102bea964..38a888661 100644
--- a/docs/tutorials/pt/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
+++ b/docs/tutorials/pt/how-to-check-the-ownership-of-vtex-store-on-google-search-console.md
@@ -17,8 +17,8 @@ subcategory: 1luKrYptdi8WoMYckakUaM
 
 Para habilitar o acesso aos dados do **Search Console**, você precisa verificar a propriedade sobre sua loja. Através de etapas simples você já terá acessos dados da performance da indexação de sua loja no Google.
 
-1. Acesse o Search Console utilizando uma conta Google através da url: [https://www.google.com/webmasters/tools/](https://www.google.com/webmasters/tools/ "https://www.google.com/webmasters/tools/")![Primeiro passo - Verificação de Propriedade Google Search Console](//images.contentful.com/alneenqid6w5/53nfBOKjXOMGacqQIGuYKY/5d9bed2fd41df4956e89a5e52c00acc4/step_1.jpg) 
-2. Selecione a opção **Adicionar propriedade** e insira a URL de sua loja:![](//images.contentful.com/alneenqid6w5/5z5kYNIrzUo2mumc6WU6sC/d5e408a19b2ec6cf3c261ce490b43cab/step_2.jpg)
-3. Método de verificação, o Search Console disponibiliza diversos métodos para verificação de propriedade de sua loja, o método indicado para lojas VTEX é o **Tag HTML** na opção **Métodos alternativos**![](//images.contentful.com/alneenqid6w5/5QvujnxhluSkW8UOkOwUOM/86022ea4ffb6dad43f421af5ea130568/step_3.jpg)
-4. O método **Tag HTML** gera uma meta tag que deverá ser inserido no template da página inicial de sua loja. Copie o tag exibida e insira entre o `<head>` do template de sua loja:![](//images.contentful.com/alneenqid6w5/3uDOqrv56oMGUK6mAewgSO/bd820d0abd57ef29c88cccc5669e314f/step_4.jpg)
-5. Após a inserção da meta tag no template, aguarde em torno de 10 minutos para verificar a propriedade no Search Console, com a verificação concluída você já terá acesso a todos os dados de indexação da loja:![](//images.contentful.com/alneenqid6w5/225MhXRikEygYCyagUY4MQ/11f0f693fa62a9700d6cec050267e98b/step_5.jpg)
+1. Acesse o Search Console utilizando uma conta Google através da url: [https://www.google.com/webmasters/tools/](https://www.google.com/webmasters/tools/ "https://www.google.com/webmasters/tools/")![Primeiro passo - Verificação de Propriedade Google Search Console](https://images.contentful.com/alneenqid6w5/53nfBOKjXOMGacqQIGuYKY/5d9bed2fd41df4956e89a5e52c00acc4/step_1.jpg) 
+2. Selecione a opção **Adicionar propriedade** e insira a URL de sua loja:![](https://images.contentful.com/alneenqid6w5/5z5kYNIrzUo2mumc6WU6sC/d5e408a19b2ec6cf3c261ce490b43cab/step_2.jpg)
+3. Método de verificação, o Search Console disponibiliza diversos métodos para verificação de propriedade de sua loja, o método indicado para lojas VTEX é o **Tag HTML** na opção **Métodos alternativos**![](https://images.contentful.com/alneenqid6w5/5QvujnxhluSkW8UOkOwUOM/86022ea4ffb6dad43f421af5ea130568/step_3.jpg)
+4. O método **Tag HTML** gera uma meta tag que deverá ser inserido no template da página inicial de sua loja. Copie o tag exibida e insira entre o `<head>` do template de sua loja:![](https://images.contentful.com/alneenqid6w5/3uDOqrv56oMGUK6mAewgSO/bd820d0abd57ef29c88cccc5669e314f/step_4.jpg)
+5. Após a inserção da meta tag no template, aguarde em torno de 10 minutos para verificar a propriedade no Search Console, com a verificação concluída você já terá acesso a todos os dados de indexação da loja:![](https://images.contentful.com/alneenqid6w5/225MhXRikEygYCyagUY4MQ/11f0f693fa62a9700d6cec050267e98b/step_5.jpg)
diff --git a/docs/tutorials/pt/how-to-check-your-balance.md b/docs/tutorials/pt/how-to-check-your-balance.md
index 96ef0a6bb..e5847558f 100644
--- a/docs/tutorials/pt/how-to-check-your-balance.md
+++ b/docs/tutorials/pt/how-to-check-your-balance.md
@@ -28,7 +28,7 @@ Para conferir o saldo da sua conta, siga o passo a passo:
 - Clique em __Resumo da Conta__;
 - Do lado esquerdo da tela, encontre o box de __Saldo__.
 
-![saldodisponivelPT](//images.ctfassets.net/alneenqid6w5/wP9JUmFgAaH3svDApS1hi/0da1d892f79292d1c9fce55bfbc9c2f5/image.png)
+![saldodisponivelPT](https://images.ctfassets.net/alneenqid6w5/wP9JUmFgAaH3svDApS1hi/0da1d892f79292d1c9fce55bfbc9c2f5/image.png)
 
 A box apresenta dois valores. O primeiro, __Disponível__, apresenta o saldo em conta livre para movimentações. Já o segundo, __Saldo a receber__, consta o soma dos futuros pagamentos que serão lançados na conta digital corporativa. 
 
diff --git a/docs/tutorials/pt/how-to-configure-extra-fields-in-instore-cart.md b/docs/tutorials/pt/how-to-configure-extra-fields-in-instore-cart.md
index 66a6133b6..8c6d7ec46 100644
--- a/docs/tutorials/pt/how-to-configure-extra-fields-in-instore-cart.md
+++ b/docs/tutorials/pt/how-to-configure-extra-fields-in-instore-cart.md
@@ -22,9 +22,9 @@ Para criar os campos extras, siga os passos abaixo:
 1. Consulte a configuração atual da loja por meio da requisição GET no endpoint [Get orderForm configuration](https://developers.vtex.com/vtex-rest-api/reference/getorderformconfiguration). Salve as informações do JSON retornado da requisição.
 
 Exemplo utilizado para a loja "inStore":
-![2017-08-14 20 12 34-Postman](//images.contentful.com/alneenqid6w5/6I61we4oF2AMkgcIAMgEo/772e7d2b045312f1f5c76b4d8eb9d30f/2017-08-14_20_12_34-Postman.png)
+![2017-08-14 20 12 34-Postman](https://images.contentful.com/alneenqid6w5/6I61we4oF2AMkgcIAMgEo/772e7d2b045312f1f5c76b4d8eb9d30f/2017-08-14_20_12_34-Postman.png)
     2. Faça uma requisição POST utilizando o endpoint [Update orderForm configuration](https://developers.vtex.com/vtex-rest-api/reference/updateorderformconfiguration) com os mesmos dados salvos do JSON, e acrescente os campos extras (`fields`) com as informações dentro da propriedade `apps`.
 
 Exemplo de requisição POST:
 
-![2017-08-14 20 11 18-Postman](//images.contentful.com/alneenqid6w5/6QIwIi5IBiy4qCyu2qseey/538d03ceb7f47ea0e47eb8047b931da6/2017-08-14_20_11_18-Postman.png)
+![2017-08-14 20 11 18-Postman](https://images.contentful.com/alneenqid6w5/6QIwIi5IBiy4qCyu2qseey/538d03ceb7f47ea0e47eb8047b931da6/2017-08-14_20_11_18-Postman.png)
diff --git a/docs/tutorials/pt/how-to-configure-mercado-pago-transparente-in-the-payments-module.md b/docs/tutorials/pt/how-to-configure-mercado-pago-transparente-in-the-payments-module.md
index 48f68cddc..cf3cfbb72 100644
--- a/docs/tutorials/pt/how-to-configure-mercado-pago-transparente-in-the-payments-module.md
+++ b/docs/tutorials/pt/how-to-configure-mercado-pago-transparente-in-the-payments-module.md
@@ -18,13 +18,13 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 O objetivo deste artigo é explicar os passos para adicionar e configurar o conector Mercado Pago Transparente.
 
 Primeiro, você deve acessar o módulo Pagamentos e clicar em **Configurações**, que fica à direita na barra superior.
-![2017-01-26 19_04_37-Transações _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/6Gxdu2Z0NqyggYkEe8A8q0/7fd3e1c15fd89ec76c90473329ff1439/2017-01-26-19_04_37-Transa_C3_A7_C3_B5es-_-VTEX-PCI-Gateway-300x105.png)
+![2017-01-26 19_04_37-Transações _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/6Gxdu2Z0NqyggYkEe8A8q0/7fd3e1c15fd89ec76c90473329ff1439/2017-01-26-19_04_37-Transa_C3_A7_C3_B5es-_-VTEX-PCI-Gateway-300x105.png)
 
 Depois, clique no item **Afiliações de Gateways** e, então, no ícone **+**, que fica à direita. Uma tela com todos os conectores disponíveis vai se abrir e você deve selecionar o card do Mercado Pago Transparente (__MercadoPagoV1__).
-![2017-01-26 19_12_51-Conectores _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/69Wai0Un0A0S4C0EyuCsme/8bcdc06f9863147fb04c403e83125fea/2017-01-26-19_12_51-Conectores-_-VTEX-PCI-Gateway-300x245.png)
+![2017-01-26 19_12_51-Conectores _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/69Wai0Un0A0S4C0EyuCsme/8bcdc06f9863147fb04c403e83125fea/2017-01-26-19_12_51-Conectores-_-VTEX-PCI-Gateway-300x245.png)
 
 Vão surgir os campos de edição relacionados ao conector que você escolheu. Recomendamos que você renomeie o campo **Nome da afiliação**, para facilitar sua localização em **Condições de pagamento**.
-![2017-01-26 20_00_11-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/3oiEcYJ3LGCGiGA0Uq2ucm/2e15790c707b2496e38d2d89fc88687f/2017-01-26-20_00_11-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x208.png)
+![2017-01-26 20_00_11-Mercado Pago Transparente - Nova configuração _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/3oiEcYJ3LGCGiGA0Uq2ucm/2e15790c707b2496e38d2d89fc88687f/2017-01-26-20_00_11-Mercado-Pago-Transparente-Nova-configura_C3_A7_C3_A3o-_-VTEX-PCI-Gateway-300x208.png)
 
 Então, faça a [configuração do anti-fraude](/pt/faq/como-configurar-mercadopago-transparente/) e [preencha as credenciais](/pt/faq/onde-acessar-minhas-credenciais-do-mercado-pago-transparente/). Lembrando que os códigos do **Client Id** e do **Client Secret** não devem começar com **APP_USR**.
 
diff --git a/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index fe34c8015..05455d4fa 100644
--- a/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -30,7 +30,7 @@ Já em operações B2B, há necessidade de se manter relações com os comprador
 2. Na aba __Gerais__, preencha o valor desejado no campo __Valor mínimo total do carrinho__.
 3. Clique em `Salvar`.
 
-![Minimum Order Value - PT](//images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/4b4ff920a4c1a9a98ad3450e00f47d6c/Minimum_Order_Value_-_PT.png)
+![Minimum Order Value - PT](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/4b4ff920a4c1a9a98ad3450e00f47d6c/Minimum_Order_Value_-_PT.png)
 
 <div class="alert alert-warning">
 Ao cliente é permitido montar um carrinho com um valor menor que o especificado na regra de "Valor mínimo total do carrinho". Entretanto, no momento de fechamento da compra, só serão concluídos os pedidos que estiverem com o valor igual ou acima do especificado.
@@ -42,7 +42,7 @@ Ao cliente é permitido montar um carrinho com um valor menor que o especificado
 2. Na aba __Gerais__, preencha o valor desejado no campo __Quantidade máxima de um mesmo SKU no Carrinho__.
 3. Clique em `Salvar`.
 
-![Quantidade Maxima de um mesmo SKU no carrinho](//images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/bb659e068dfde3a2e4d05480422a7113/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_PT.png)
+![Quantidade Maxima de um mesmo SKU no carrinho](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/bb659e068dfde3a2e4d05480422a7113/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_PT.png)
 
 <div class="alert alert-warning">
 Não existem limites para a quantidade máxima de itens do <b>mesmo SKU</b> por carrinho. A única restrição é referente a quantidade máxima de itens de <b>SKUs diferentes</b>, que devem ser no máximo de 300 itens por carrinho. 
diff --git a/docs/tutorials/pt/how-to-configure-payment-conditions.md b/docs/tutorials/pt/how-to-configure-payment-conditions.md
index 2923b2d9c..eeb47ebbc 100644
--- a/docs/tutorials/pt/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/pt/how-to-configure-payment-conditions.md
@@ -38,7 +38,7 @@ Nas etapas abaixo, iremos utilizar o cartão de crédito como exemplo de condiç
 
 ### À vista
 
-![pagamento-a-vista pt](//images.ctfassets.net/alneenqid6w5/16U7FyAeXiC88gWCwkKmSU/b07c00338cbbf59430ec4e5a322e0159/pagamento-a-vista.png)
+![pagamento-a-vista pt](https://images.ctfassets.net/alneenqid6w5/16U7FyAeXiC88gWCwkKmSU/b07c00338cbbf59430ec4e5a322e0159/pagamento-a-vista.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __+__.
@@ -56,7 +56,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 
 ### Parcelado sem juros
 
-![parcelamento-sem-juros pt](//images.ctfassets.net/alneenqid6w5/5UuCXeD07moeaQiqqmuCMe/05b2cdeeac157859c9ffadce866eaebf/parcelamento-sem-juros.png)
+![parcelamento-sem-juros pt](https://images.ctfassets.net/alneenqid6w5/5UuCXeD07moeaQiqqmuCMe/05b2cdeeac157859c9ffadce866eaebf/parcelamento-sem-juros.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __+__.
@@ -73,7 +73,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 
 ### Parcelado com juros
 
-![parcelamento-com-juros pt](//images.ctfassets.net/alneenqid6w5/46wBJ8tCUgCaWmAyOgkycY/cada24446ff801ebffdcf02c5aa4b0e7/parcelamento-com-juros.png)
+![parcelamento-com-juros pt](https://images.ctfassets.net/alneenqid6w5/46wBJ8tCUgCaWmAyOgkycY/cada24446ff801ebffdcf02c5aa4b0e7/parcelamento-com-juros.png)
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __+__.
@@ -91,7 +91,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 14. Para escolher entre juros compostos e juros simples, clique em __Juros compostos aplicados. Alterar__. Uma caixa de seleção vai aparecer oferecendo as duas opções.
 15. Clique em __Salvar__.
 
-![Juros - pt](//images.ctfassets.net/alneenqid6w5/6LByLxJORIELFs7gTY3kmA/ce12cf0d03887377566de5eeadd0ed98/Juros_-_pt.png)
+![Juros - pt](https://images.ctfassets.net/alneenqid6w5/6LByLxJORIELFs7gTY3kmA/ce12cf0d03887377566de5eeadd0ed98/Juros_-_pt.png)
 
 #### Juros Externos
 
@@ -107,5 +107,5 @@ Atenção: a funcionalidade de juros externos é válida apenas para algumas afi
 2. Na aba __Condições de Pagamentos__, clique sobre a condição de pagamento que deseja remover.
 3. Clique sobre o ícone de lixeira.
 
-![Remover condição de pagamento](//images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/9486e6e1036228c2ad8dfa7d0685768e/remover_condi____o_pagamento.png)
+![Remover condição de pagamento](https://images.ctfassets.net/alneenqid6w5/30AGmwCJOclqEqvcNPzuxV/9486e6e1036228c2ad8dfa7d0685768e/remover_condi____o_pagamento.png)
 
diff --git a/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md b/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
index 206661231..0d1920157 100644
--- a/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
@@ -46,10 +46,10 @@ Estes controles, diferentes dos demais, necessitam de uma configuração impresc
 
 No cadastro de Categoria existe a opção de configurar a Avaliação, e normalmente esta configuração é feita na categoria raiz:
 
-![avaliação-categoria PT](//images.ctfassets.net/alneenqid6w5/TtskX9FjmSS0C0UMAeIcM/36a5e64b42da3a23766d7256ade0d8c9/avalia____o_pt.png)
+![avaliação-categoria PT](https://images.ctfassets.net/alneenqid6w5/TtskX9FjmSS0C0UMAeIcM/36a5e64b42da3a23766d7256ade0d8c9/avalia____o_pt.png)
 
 Clique em **Nova Avaliação** e preencha os dados Nome e Texto e depois salve.
 
-![nova-avaliação-categorias PT](//images.ctfassets.net/alneenqid6w5/6ASmMpGULegqwGKYSm8MSW/10966c7137236f5e9b7d74feb266789c/Nova_avalia____o.png)
+![nova-avaliação-categorias PT](https://images.ctfassets.net/alneenqid6w5/6ASmMpGULegqwGKYSm8MSW/10966c7137236f5e9b7d74feb266789c/Nova_avalia____o.png)
 
 Pronto seus controles de Resenha e Avaliação estão prontos para serem utilizados.
diff --git a/docs/tutorials/pt/how-to-configure-taxhub.md b/docs/tutorials/pt/how-to-configure-taxhub.md
index 007c81875..b285431d4 100644
--- a/docs/tutorials/pt/how-to-configure-taxhub.md
+++ b/docs/tutorials/pt/how-to-configure-taxhub.md
@@ -25,4 +25,4 @@ Para configurar o sistema de impostos TaxHub, siga os passos abaixo:
 6.	Em __Token de Autorização__ preencha com o token do serviço do passo anterior. Nota: Em alguns casos pode não ser necessário;
 7.	Clique em __Salvar__.
 
-![TaxHub Configuration](//images.contentful.com/alneenqid6w5/RG3lWrwAOAyQYwk6gwGgq/7f291339357dac4cf07fbee9f5e0a649/TaxHubConfiguration.gif)
+![TaxHub Configuration](https://images.contentful.com/alneenqid6w5/RG3lWrwAOAyQYwk6gwGgq/7f291339357dac4cf07fbee9f5e0a649/TaxHubConfiguration.gif)
diff --git a/docs/tutorials/pt/how-to-configure-the-favicon.md b/docs/tutorials/pt/how-to-configure-the-favicon.md
index e7db69e3c..b91487796 100644
--- a/docs/tutorials/pt/how-to-configure-the-favicon.md
+++ b/docs/tutorials/pt/how-to-configure-the-favicon.md
@@ -19,7 +19,7 @@ O favicon é o ícone exibido na aba do browser, ao lado do título da página.
 
 Exemplo:
 
-![favicon_2](//images.contentful.com/alneenqid6w5/2azvX7m3asGckkU6c8WAcM/2e66d9a107c0394c3f1a63afff7f3149/favicon_2-1024x537.png "Favicon 2")
+![favicon_2](https://images.contentful.com/alneenqid6w5/2azvX7m3asGckkU6c8WAcM/2e66d9a107c0394c3f1a63afff7f3149/favicon_2-1024x537.png "Favicon 2")
 
 Usei o Google como exemplo apenas para reforçar que esse recurso não é exclusivo da VTEX e pode ser utilizado em qualquer conteúdo reproduzido em um browser. Leia mais sobre esse assunto no Google. 🙂
 
@@ -33,5 +33,5 @@ Na VTEX, para garantir que o favicon estará carregado durante toda a navegaç
 
 **Obs. 2:** A variável `{storeName}` deve ser substituída pelo nome da loja, como cadastrado no Gerenciamento da conta.
 
-![fav](//images.contentful.com/alneenqid6w5/6j5eZzVMEE6E2KgqGgsOwU/c2292316f75f3620cd870c96df9e65fc/fav-1024x554.png)
+![fav](https://images.contentful.com/alneenqid6w5/6j5eZzVMEE6E2KgqGgsOwU/c2292316f75f3620cd870c96df9e65fc/fav-1024x554.png)
 
diff --git a/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md b/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md
index d2d685805..7ab252119 100644
--- a/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md
+++ b/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md
@@ -32,7 +32,7 @@ As instruções dessa etapa do artigo são realizadas em um ambiente externo. De
 Para inserir os scripts que a Stelo exige para o device fingerprint, é necessário usar o Google Tag Manager. Para isso, faça login na sua conta em [http://www.google.com/tagmanager](http://www.google.com/tagmanager). Depois, siga os passos abaixo:
 
 1. No menu inicial do Google Tag Manager, clique em **Nova tag**
-2. Selecione **Configuração da tag** e escolha o tipo **HTML personalizado**.![Tela1](//images.contentful.com/alneenqid6w5/2VjcP3lQ9aqceC82kgaAU8/68bffad6d79e91e7286c780ac16fffc7/Tela1.jpg)
+2. Selecione **Configuração da tag** e escolha o tipo **HTML personalizado**.![Tela1](https://images.contentful.com/alneenqid6w5/2VjcP3lQ9aqceC82kgaAU8/68bffad6d79e91e7286c780ac16fffc7/Tela1.jpg)
 
 Então insira o script abaixo:
 
@@ -51,13 +51,13 @@ window.vtex.deviceFingerprint = match[1];
 
 Depois, siga os passos abaixo:
 
-1. Clique em **Acionamento**, Novo acionador (símbolo de **+** no canto superior direito) e em **Configuração do acionador.**![Tela2](//images.contentful.com/alneenqid6w5/6uwEr6KGJyOCcigIMCcUoS/4142ad24f3121bee1fea9d55069d10a6/Tela2.jpg)
+1. Clique em **Acionamento**, Novo acionador (símbolo de **+** no canto superior direito) e em **Configuração do acionador.**![Tela2](https://images.contentful.com/alneenqid6w5/6uwEr6KGJyOCcigIMCcUoS/4142ad24f3121bee1fea9d55069d10a6/Tela2.jpg)
 2. Escolha o tipo **Evento personalizado** e insira o nome **payment**;
 3. Selecione a flag **Alguns eventos personalizados**;
-4. Nas duas primeiras caixas abaixo, selecione: **Event** e **é igual a**. Na terceira, escreva **payment**.![Tela3](//images.contentful.com/alneenqid6w5/5sbXgbm4g0yysWKSwmYWI0/e7d605639093f30aff58bff0efef2ae4/Tela3.jpg)
+4. Nas duas primeiras caixas abaixo, selecione: **Event** e **é igual a**. Na terceira, escreva **payment**.![Tela3](https://images.contentful.com/alneenqid6w5/5sbXgbm4g0yysWKSwmYWI0/e7d605639093f30aff58bff0efef2ae4/Tela3.jpg)
 5. Salve o acionador e a tag;
 6. No menu lateral, clique na opção **Variáveis** e depois em **Nova**;
-7. Clique em **Configuração da variável** e escolha o tipo **JavaScript personalizado**;![Tela4](//images.contentful.com/alneenqid6w5/3I7Eq6Jt2wkYg6EoKAkCqC/91cca1c81534bbbc76e70db8f94be13a/Tela4.jpg)
+7. Clique em **Configuração da variável** e escolha o tipo **JavaScript personalizado**;![Tela4](https://images.contentful.com/alneenqid6w5/3I7Eq6Jt2wkYg6EoKAkCqC/91cca1c81534bbbc76e70db8f94be13a/Tela4.jpg)
 
 Por fim, insira o script abaixo:
 
diff --git a/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md b/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md
index 927af5c65..56011c823 100644
--- a/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md
+++ b/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md
@@ -37,7 +37,7 @@ Você pode configurar o Google Shopping através do Admin VTEX, seguindo os pass
   O link de acesso ao XML será gerado automaticamente.
 9. Grave este XML em um arquivo .txt e envie o arquivo ao Google.
 
-![](//images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
+![](https://images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
 
 <div class = "alert alert-warning">
   <p>Caso a opção <strong>Exibir SKUs indisponíveis</strong> esteja desmarcada, os produtos ou SKUs que estiverem esgotados não aparecerão no XML. Produtos inativos também não aparecem no XML.</p>
diff --git a/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md b/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
index 175d9fe29..d4d6ef75f 100644
--- a/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
+++ b/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
@@ -21,7 +21,7 @@ Seguindo a [Atualização de 2015 da Especificação do feed do Google Shopping
 
 A configuração padrão de nosso formulário de XML já está com as tags atualizada, para criar um novo feed Google Merchant / Shopping basta selecionar a opção “Feed: Atom 1”:
 
-![](//images.contentful.com/alneenqid6w5/2ugQUy4xlaaUEOIYuu6UMe/41fd01c32b6954b14e1ef5818b94ca0c/atom1_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/2ugQUy4xlaaUEOIYuu6UMe/41fd01c32b6954b14e1ef5818b94ca0c/atom1_xml_vtex_google.gif)
 
 Para a correta integração com o Google Merchant / Shopping será necessário atualizar o xml com os novos campos a partir do dia 15 de setembro de 2015.
 
@@ -31,7 +31,7 @@ Conheça os novos campos do formulário de XML:
 
 Opção responsável pela definição da taxonomia dos campos “Categoria” e “Departamento + Categoria”. Comumente utilizado para o preenchimanto da tag [g:product\_type].
 
-![](//images.contentful.com/alneenqid6w5/3dgBcIJZgcKSW2YKCaksmW/653d517228e7d303e7326dfa1dcedbc1/separador_categoria_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/3dgBcIJZgcKSW2YKCaksmW/653d517228e7d303e7326dfa1dcedbc1/separador_categoria_xml_vtex_google.gif)
 
 Padrão (Ex: Categoria Pai - Categoria Filha - Categoria Neta)
 
@@ -47,7 +47,7 @@ Campo responsável pelo relacionamento das categorias de sua loja com as categor
 
 Deverá ser preenchido com a tag [g:google\_product\_category]
 
-![](//images.contentful.com/alneenqid6w5/307z7lsmEMgQMWIOUQWk8K/9d854eb77bb73e1c79d5307c78fb0215/categoria_global_xml_vtex_google.gif)
+![](https://images.contentful.com/alneenqid6w5/307z7lsmEMgQMWIOUQWk8K/9d854eb77bb73e1c79d5307c78fb0215/categoria_global_xml_vtex_google.gif)
 
 Para o correto funcionamento desse campo é necessário verificar se o produto tem o campo **Categorial Global** preenchido no catálogo VTEX.
 
diff --git a/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md b/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md
index 77906b41c..7ca4a83ad 100644
--- a/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md
+++ b/docs/tutorials/pt/how-to-create-a-development-environment-with-a-mobile-version.md
@@ -36,7 +36,7 @@ Para desenvolver uma versão mobile com um novo WebSite, você deve seguir os se
 
   Storefront > Layout > Pasta CMS > Sites and Channels > New Website
 
-![cms-new-website](//images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
+![cms-new-website](https://images.ctfassets.net/alneenqid6w5/62XyLdvzwsQaESok6EmUG8/e8a4597bed1e50d5ce24f350d46be96b/New_website.png)
 
 3. Criar estrutura de pastas do WebSite Mobile: Nesse passo será necessário criar as pastas padrões do sistema que serão utilizadas na versão mobile (busca, departamento, categoria, marca, produto etc.)
 
diff --git a/docs/tutorials/pt/how-to-create-a-financial-access-profile.md b/docs/tutorials/pt/how-to-create-a-financial-access-profile.md
index 4e72120b8..1fa6944e7 100644
--- a/docs/tutorials/pt/how-to-create-a-financial-access-profile.md
+++ b/docs/tutorials/pt/how-to-create-a-financial-access-profile.md
@@ -31,7 +31,7 @@ Para criar um perfil de acesso financeiro:
 6. (Opcional) Antes de salvar, você pode **Adicionar usuários para este perfil de acesso**.
 7. Clique em **Salvar**.
 
-![gif perfil de acesso financeiro](//images.ctfassets.net/alneenqid6w5/6fUKD0hvvh8rYapiH2sDit/205b3a066fe0fc456b6cf778ea2f3f40/gif_perfil_de_acesso_financeiro.gif)
+![gif perfil de acesso financeiro](https://images.ctfassets.net/alneenqid6w5/6fUKD0hvvh8rYapiH2sDit/205b3a066fe0fc456b6cf778ea2f3f40/gif_perfil_de_acesso_financeiro.gif)
 
 Agora o perfil de acesso financeiro está criado e disponível para associação a usuários existentes.
 
@@ -48,6 +48,6 @@ Agora o perfil de acesso financeiro está criado e disponível para associação
 6. Clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/2jZogtT8WT3XVmv5U6yXh/2dc70b446b9aad1b27840e64b2cf15ce/bot__o_adicionar.png" /> ao lado do perfil selecionado para adicionar.
 7. Para finalizar, clique em **Salvar**.
 
-![gif usuário](//images.ctfassets.net/alneenqid6w5/3HH5kuEBHEwYktRfC6aepQ/411e4398d285ac628f5691cb517638f8/gif_usu__rio.gif)
+![gif usuário](https://images.ctfassets.net/alneenqid6w5/3HH5kuEBHEwYktRfC6aepQ/411e4398d285ac628f5691cb517638f8/gif_usu__rio.gif)
 
 Agora o usuário selecionado está associado ao perfil de acesso Financeiro e poderá acessar faturas, informações sobre o contrato, cobranças e outras informações financeiras.
diff --git a/docs/tutorials/pt/how-to-create-a-page-template.md b/docs/tutorials/pt/how-to-create-a-page-template.md
index 5d06d08ee..7d6b7e886 100644
--- a/docs/tutorials/pt/how-to-create-a-page-template.md
+++ b/docs/tutorials/pt/how-to-create-a-page-template.md
@@ -46,7 +46,7 @@ Confira o passo a passo a seguir:
 <li><code>app</code></li>
 </ul></p>
 </div>
-6. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](//images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
+6. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. No canto superior direito, clique no botão __Save Template__.
 
 Para editar um template já existente, o processo é quase idêntico.
diff --git a/docs/tutorials/pt/how-to-create-a-product.md b/docs/tutorials/pt/how-to-create-a-product.md
index 029e69b3e..a6848e12f 100644
--- a/docs/tutorials/pt/how-to-create-a-product.md
+++ b/docs/tutorials/pt/how-to-create-a-product.md
@@ -56,7 +56,7 @@ Nesta seção, você precisa adicionar pelo menos uma política comercial para s
 
 Nesta etapa, você precisa escrever uma descrição das principais informações relacionadas ao produto. O texto deve ser um resumo simples e de fácil entendimento para o cliente. O editor de texto da descrição é rich text, ou seja, você pode utilizar diversos recursos de formatação utilizando a barra de ferramentas desse campo, ilustrada abaixo.
 
-![richtextdescription-PT](//images.contentful.com/alneenqid6w5/5ZsZ8w2bYbaM7yQ685K0QD/703ab1ea4e8618aeac8170938e79b43a/richtextdescription.gif)
+![richtextdescription-PT](https://images.contentful.com/alneenqid6w5/5ZsZ8w2bYbaM7yQ685K0QD/703ab1ea4e8618aeac8170938e79b43a/richtextdescription.gif)
 
 Veja quais são os recursos disponíveis a partir da barra de ferramentas:
 
@@ -89,7 +89,7 @@ Para adicionar imagens ao produto, siga o passo a passo abaixo:
 
 Você pode clicar em uma imagem e arrastá-la para antes ou depois das outras, caso deseje reorganizar as imagens e alterar a ordem de exibição na página do produto, conforme ilustrado abaixo.
 
-![imagens-sku-PT](//images.contentful.com/alneenqid6w5/5m037wmoaACDY2kWW8i590/75fd6f032396efb8d479ad4ae4c075ab/imagens-sku-PT.gif)
+![imagens-sku-PT](https://images.contentful.com/alneenqid6w5/5m037wmoaACDY2kWW8i590/75fd6f032396efb8d479ad4ae4c075ab/imagens-sku-PT.gif)
 
 Você pode alterar informações de cada imagem clicando no botão <i class="fas fa-ellipsis-v"></i> na linha de cada uma, que abre um menu com opções a seguir.
 
@@ -124,7 +124,7 @@ Exemplo: uma loja de cosméticos poderia configurar os grupos de atributos de um
   1. Tempo de fixação: longo
   2. Tipo de aplicação: spray
 
-![atributos-PT](//images.contentful.com/alneenqid6w5/6F9yuSkur10PzPGiBgccSR/1fb207ddf5ff24be4464ff95dad09950/image3.gif)
+![atributos-PT](https://images.contentful.com/alneenqid6w5/6F9yuSkur10PzPGiBgccSR/1fb207ddf5ff24be4464ff95dad09950/image3.gif)
 
 Após realizar as alterações desejadas no painel de atributos, clique em `Aplicar`.
 
@@ -167,7 +167,7 @@ Depois de realizar esse procedimento, as especificações criadas e suas respect
 
 Além disso, a partir da combinação das opções criadas, a lista de SKUs possíveis é gerada automaticamente e exibida na seção **[Variações](#variacoes)**.
 
-![variacoes PT](//images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/4c28a11c44f7df5e108eb595b73a98bb/variations_PT_v2.png)
+![variacoes PT](https://images.ctfassets.net/alneenqid6w5/DkJNVLdFQ6BuBUDPwt2Xj/4c28a11c44f7df5e108eb595b73a98bb/variations_PT_v2.png)
 
 ## Especificações
 
@@ -198,7 +198,7 @@ Ao clicar no botão <i class="fas fa-ellipsis-v"></i>, é possível realizar as
   * **Selecionar imagens:** selecionar as imagens correspondentes à variação. Para selecionar uma imagem, basta clicar nela. Caso queira selecionar todas as imagens de uma vez, você pode utilizar o atalho `Ctrl` + `A` no teclado.
   * **Aplicar a múltiplas variações:** se desejar, você pode aplicar as imagens selecionadas a múltiplas variações. Para isso, clique em `Aplicar a múltiplas variações +` e selecione os valores  das especificações às quais a sua imagem se relaciona. Por exemplo: se a imagem é de um tênis bege, aqui você deve selecionar a opção `bege` da especificação `cor`. Com essa configuração, a imagem será aplicada a todas as variações cuja especificação `cor` tem o valor `bege`, independentemente de outras especificações configuradas, como `tamanho`. A imagem abaixo ilustra esse fluxo de configuração.
 
-![variações-PT](//images.contentful.com/alneenqid6w5/33nhm0Ai4UGwkDicUCk4ew/455b033b84018a2a261735c4afeefc77/image2.gif)
+![variações-PT](https://images.contentful.com/alneenqid6w5/33nhm0Ai4UGwkDicUCk4ew/455b033b84018a2a261735c4afeefc77/image2.gif)
 
   * **Adicionar imagens:** neste painel, também é possível fazer upload de novas imagens, clicando no botão `Adicionar imagens` ou soltando arquivos de imagem no espaço pontilhado.
 * **Desativar:** desativar a variação na sua loja. 
@@ -211,7 +211,7 @@ Ao clicar no botão <i class="fas fa-ellipsis-v"></i>, é possível realizar as
 
 O painel de edição avançada de variações, ilustrado abaixo, possibilita visualizar e editar todas as informações e imagens relacionadas a cada variação do produto. 
 
-![edição avançada - PT](//images.contentful.com/alneenqid6w5/4YLX9IfwOBnFLcZF2vme0x/3b5234624d85e3ad048f797546de6fe2/image11.png)
+![edição avançada - PT](https://images.contentful.com/alneenqid6w5/4YLX9IfwOBnFLcZF2vme0x/3b5234624d85e3ad048f797546de6fe2/image11.png)
 
 Na seção **Variações**, do lado esquerdo do painel, você encontra a lista de variações do seu produto. Para editar uma variação específica, é necessário clicar nela.
 
@@ -222,7 +222,7 @@ Para editar uma grande quantidade de variações de uma única vez, é possível
 
 1. Clique no botão `Edição em massa` para abrir a planilha de edição de variações.
 2. Para editar uma informação da planilha, clique no campo que deseja alterar.
-![edicao-massa-SKU-PT](//images.contentful.com/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/8d5d9d8762ecb143b6d0cd3dbf9b693c/image.png)
+![edicao-massa-SKU-PT](https://images.contentful.com/alneenqid6w5/6WRJU5vCWJKjH0ULhdbCdV/8d5d9d8762ecb143b6d0cd3dbf9b693c/image.png)
 
 Na planilha é possível editar as seguintes informações:
 - **Ativo:** se a variação está ativa ou não.
@@ -238,7 +238,7 @@ Na planilha é possível editar as seguintes informações:
 Para filtrar as colunas exibidas na planilha, clique em `Filtrar colunas` e selecione as colunas que deseja ocultar.
 
 Você pode replicar a informação de uma célula para outras linhas e colunas. Para isso, clique no quadrado azul do canto inferior direito da célula e arraste para as células em que deseja replicar automaticamente o valor, como mostra a imagem abaixo.
-![Formatacao-celula-PT](//images.contentful.com/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/9e45959c7e3a92cf8df1b98777a394c2/Formatacao-celula-PT.gif)
+![Formatacao-celula-PT](https://images.contentful.com/alneenqid6w5/7cFtECFGcmmDTQ6Oy3qGTg/9e45959c7e3a92cf8df1b98777a394c2/Formatacao-celula-PT.gif)
 3. Após realizar a edição, clique em `Aplicar` para salvar as alterações.
 
 ## SEO
@@ -251,7 +251,7 @@ O preenchimento dos campos desta seção influenciam em como o produto será cla
 
 Ao preencher os campos de SEO, é possível conferir, à direita, a pré-visualização do produto nos resultados do Google. Veja um exemplo de preenchimento na imagem abaixo.
 
-![image9](//images.contentful.com/alneenqid6w5/134gy2AQA0Fcazfy3ZnqsW/a22a47a4fd90b56a993b9f54f5ecb24a/image9.png)
+![image9](https://images.contentful.com/alneenqid6w5/134gy2AQA0Fcazfy3ZnqsW/a22a47a4fd90b56a993b9f54f5ecb24a/image9.png)
 
 ## Frente de loja
 
diff --git a/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md
index 1582a1191..1cda72103 100644
--- a/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md
@@ -21,7 +21,7 @@ Para que uma promoção do tipo regular seja aplicada por um número limitado de
 <p>Pedidos com status <code>Iniciando cancelamento</code> ou <code>Cancelado</code> não contam no limite definido.</p>
 </div>
 
-![LimitacaoPromocao](//images.contentful.com/alneenqid6w5/1LsDiScSuE4g0Ww0QiKYEw/2584d871c716ee0abb46471e52b96d0e/LimitacaoPromocao.png)
+![LimitacaoPromocao](https://images.contentful.com/alneenqid6w5/1LsDiScSuE4g0Ww0QiKYEw/2584d871c716ee0abb46471e52b96d0e/LimitacaoPromocao.png)
 
 Também é possível configurar o limite por cliente, ao invés de limite por promoção. Para isso, basta fazer a configuração acima e clicar na opção **Habilitar limite de uso por cliente**.
 
diff --git a/docs/tutorials/pt/how-to-create-a-store-name.md b/docs/tutorials/pt/how-to-create-a-store-name.md
index 00bf6851e..3348aa04a 100644
--- a/docs/tutorials/pt/how-to-create-a-store-name.md
+++ b/docs/tutorials/pt/how-to-create-a-store-name.md
@@ -22,7 +22,7 @@ Para criar ou editar um [nome de loja](https://help.vtex.com/pt/tutorial/o-que-e
 3. Clique em **Conta**.
 4. No painel Loja, você verá os nomes de loja que já existem na sua conta. Você pode editar as informações de cada loja, ou criar um novo nome de loja, clicando no botão **Configurar outra loja**.
 
-![Configuração de nome de loja](//images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/b2bed2ce47001c83e3ea75e6896e7a28/PT.PNG)
+![Configuração de nome de loja](https://images.ctfassets.net/alneenqid6w5/6SMoOHKSbO68nfy6x5mx02/b2bed2ce47001c83e3ea75e6896e7a28/PT.PNG)
 
 Para saber como configurar o domínio de suas lojas, veja o artigo [Mudar o domínio da loja](https://help.vtex.com/pt/tutorial/o-que-preciso-fazer-para-mudar-o-dominio-da-minha-loja--frequentlyAskedQuestions_626).
 
diff --git a/docs/tutorials/pt/how-to-create-a-subscription-attachment.md b/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
index 38331a742..81c22184f 100644
--- a/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
@@ -71,11 +71,11 @@ Siga o passo a passo abaixo para configurar as frequências e datas de ciclo de
 
         * **Semanalmente**: os valores possíveis de preenchimento deste campo são = `0`, `1`, `2`, `3`, `4`, `5`, e `6`, equivalentes aos dias da semana. Considere `0` = domingo , `1` = segunda, `2` = terça, e assim sucessivamente até `6` = sábado. Separe os  valores por `,`, conforme ilustrado abaixo.
 
-        ![PT Assinatura Exemplo Valores week](//images.ctfassets.net/alneenqid6w5/20va8G0uiw3jpHKM2a99Al/7ef796fd84e1328bcc0b6f637bdc30f1/PT_Assinatura_Exemplo_Valores_week.png)
+        ![PT Assinatura Exemplo Valores week](https://images.ctfassets.net/alneenqid6w5/20va8G0uiw3jpHKM2a99Al/7ef796fd84e1328bcc0b6f637bdc30f1/PT_Assinatura_Exemplo_Valores_week.png)
 
         * **Mensalmente**: os valores possíveis de preenchimento deste campo no checkout são = `1`, `2`, `3`, (...) até `28`, que são equivalentes aos dias do mês. Considere `1` = primeiro dia do mês, `2` = segundo dia do mês, e assim sucessivamente até `28` = vigésimo oitavo dia do mês. Separe os  valores por `,`, conforme ilustrado abaixo.
 
-        ![PT Assinatura Exemplo Valores month](//images.ctfassets.net/alneenqid6w5/3ogGjc6DLexe7YeL3qyiuI/748b3dd8e63870c539b58f3404521031/PT_Assinatura_Exemplo_Valores_month.png)
+        ![PT Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/3ogGjc6DLexe7YeL3qyiuI/748b3dd8e63870c539b58f3404521031/PT_Assinatura_Exemplo_Valores_month.png)
 
 <div class="alert alert-info">
   <p>Caso nenhum valor seja inserido no campo <strong>Valores Permitidos</strong>, a data do ciclo de assinatura será o mesmo dia da semana (caso a frequência seja semanal) ou dia do mês (caso a frequência seja mensal) do pedido original.</p>
diff --git a/docs/tutorials/pt/how-to-create-conditional-prices.md b/docs/tutorials/pt/how-to-create-conditional-prices.md
index d1d6f9b77..e44c771c6 100644
--- a/docs/tutorials/pt/how-to-create-conditional-prices.md
+++ b/docs/tutorials/pt/how-to-create-conditional-prices.md
@@ -34,4 +34,4 @@ Segue abaixo um passo a passo de como usar esses Preços Condicionais :
 6. Você pode definir uma pequena mensagem, chamada *Teaser*, pra promover essa condição ao seu cliente. (Para entender melhor, veja [Teasers - Em breve])
 7. Salve.
 
-![conditionalPrice](//images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
+![conditionalPrice](https://images.ctfassets.net/alneenqid6w5/3HJkZntAaQEOoCywOS2Sqo/09869666842b78db00d1dc0ab94ca965/conditionalPrice.gif)
diff --git a/docs/tutorials/pt/how-to-create-the-script-customization-file-for-vtex-instore.md b/docs/tutorials/pt/how-to-create-the-script-customization-file-for-vtex-instore.md
index dd163b376..79042e153 100644
--- a/docs/tutorials/pt/how-to-create-the-script-customization-file-for-vtex-instore.md
+++ b/docs/tutorials/pt/how-to-create-the-script-customization-file-for-vtex-instore.md
@@ -17,20 +17,20 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 
 Para criar o arquivo de personalização basta acessar o Portal pela topbar e criar um novo arquivo com o nome `checkout-instore-custom.js`. Esse arquivo será carregado pelo inStore automaticamente.
 
-![topbar-portal](//images.contentful.com/alneenqid6w5/2Xenr5P0EMKCAyOq2Qmiaw/98fa99c841313072099b11553785660e/topbar-portal.png)
+![topbar-portal](https://images.contentful.com/alneenqid6w5/2Xenr5P0EMKCAyOq2Qmiaw/98fa99c841313072099b11553785660e/topbar-portal.png)
 
 Ao abrir o módulo do Portal deve clicar no botão de editar o site default. No exemplo abaixo a o accountname da loja é __Omniera__.
 
-![portal-default-website](//images.contentful.com/alneenqid6w5/7GHyB8nH6o62e4MWsskgCI/e5066603fe42d311f30b47055cca9cbf/portal-default-website.png)
+![portal-default-website](https://images.contentful.com/alneenqid6w5/7GHyB8nH6o62e4MWsskgCI/e5066603fe42d311f30b47055cca9cbf/portal-default-website.png)
 
 Agora deve clicar na aba `Código` e depois no botão de `Novo` onde deve selecionar a opcao de novo `Arquivo`
 
-![portal-add-file](//images.contentful.com/alneenqid6w5/1qDZc7Yj6wyaAkIaIEMEeI/461efb062c3cc02c11084908bbb01ecc/portal-add-file.png)
+![portal-add-file](https://images.contentful.com/alneenqid6w5/1qDZc7Yj6wyaAkIaIEMEeI/461efb062c3cc02c11084908bbb01ecc/portal-add-file.png)
 
 Preencha o nome do arquivo como `checkout-instore-custom.js` e faça click em `Criar`
 
-![portal-add-file-filename](//images.contentful.com/alneenqid6w5/6vdp46Cv0AgG6caSgQOe2i/3026dfc7f1de5e7b828863b5435a99c1/portal-add-file-filename.png)
+![portal-add-file-filename](https://images.contentful.com/alneenqid6w5/6vdp46Cv0AgG6caSgQOe2i/3026dfc7f1de5e7b828863b5435a99c1/portal-add-file-filename.png)
 
 Pronto, agora você pode adicionar o conteúdo do arquivo e salvar. Automaticamente o inStore vai carregar o arquivo de personalização.
 
-![portal-edit-file](//images.contentful.com/alneenqid6w5/7HxG61bw1aW0yuK6OIycyU/dde5f00b9aeec4bbc05b7b18ebd1b0f3/portal-edit-file.png)
+![portal-edit-file](https://images.contentful.com/alneenqid6w5/7HxG61bw1aW0yuK6OIycyU/dde5f00b9aeec4bbc05b7b18ebd1b0f3/portal-edit-file.png)
diff --git a/docs/tutorials/pt/how-to-customize-a-page-using-placeholders.md b/docs/tutorials/pt/how-to-customize-a-page-using-placeholders.md
index b69fe9586..3ca0f6db5 100644
--- a/docs/tutorials/pt/how-to-customize-a-page-using-placeholders.md
+++ b/docs/tutorials/pt/how-to-customize-a-page-using-placeholders.md
@@ -40,9 +40,9 @@ Lembrando que o `htmlSeo` é o nome do controle criado lá em cima. Este contro
 
 **Exemplos**
 
-![](//images.contentful.com/alneenqid6w5/5LY7pZwZpe8iQiWccqCc26/d4c10dc57a8f6091dd5c23ec3fdad12e/2016-04-05_17_15_29-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5LY7pZwZpe8iQiWccqCc26/d4c10dc57a8f6091dd5c23ec3fdad12e/2016-04-05_17_15_29-Index.png)
 
-![](//images.contentful.com/alneenqid6w5/45kPL4QTfqMkYuAYQEeuC2/aed1934b3268ccb8310226e0e6ce9ff3/2016-04-05_17_15_58-Index.png)
+![](https://images.contentful.com/alneenqid6w5/45kPL4QTfqMkYuAYQEeuC2/aed1934b3268ccb8310226e0e6ce9ff3/2016-04-05_17_15_58-Index.png)
 
 **Obs.:** A aplicação do placeholder pode ser realizada de outras maneiras até que atenda o local, o formato, ou seja, a necessidade do lojista.
 
@@ -52,21 +52,21 @@ Para incluir uma descrição para Categoria, siga os passos abaixo:
 
 1. Entre em Configurações > Portal
 2. Clique em Portal > Web-sites > [nomedaloja] > / > categoria > @categoria@ > categoria
-![](//images.contentful.com/alneenqid6w5/5IrVEkqOlyy644oAwGS0Ou/b82465f649790ab7bbbce5ea4d416265/2016-04-05_16_21_49-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5IrVEkqOlyy644oAwGS0Ou/b82465f649790ab7bbbce5ea4d416265/2016-04-05_16_21_49-Index.png)
 3. Entre na aba **Configurações**
-![](//images.contentful.com/alneenqid6w5/bhebyo6cBaKy2wa8O4moA/fe1f57b2ef00101ba21effb442206043/2016-04-05_16_25_11-Index.png)
+![](https://images.contentful.com/alneenqid6w5/bhebyo6cBaKy2wa8O4moA/fe1f57b2ef00101ba21effb442206043/2016-04-05_16_25_11-Index.png)
 4. Clique em **Adicionar Controle**
 5. Selecione o tipo de controle que deseja, geralmente HTML
-![](//images.contentful.com/alneenqid6w5/42vmuVKKdWSwcc0gsuwimi/91fe4618316504de9ea0fb385e46df6b/2016-04-05_16_34_31-Index.png)
+![](https://images.contentful.com/alneenqid6w5/42vmuVKKdWSwcc0gsuwimi/91fe4618316504de9ea0fb385e46df6b/2016-04-05_16_34_31-Index.png)
 6. Clique em **Adicionar**
 7. Clique em **Salvar Configurações**
 8. Clique em **Editar**
 9. Clique em **Adicionar Conteúdo**
-![](//images.contentful.com/alneenqid6w5/6Ou1gOdTZCWKqIwUA682C6/6f241a6ad96fc83cf6830622ababe08f/2016-04-05_16_34_58-Index.png)
+![](https://images.contentful.com/alneenqid6w5/6Ou1gOdTZCWKqIwUA682C6/6f241a6ad96fc83cf6830622ababe08f/2016-04-05_16_34_58-Index.png)
 10. Crie o HTML que gostaria que aparecesse no site
 11. Na aba **Preview** poderá ter uma pré-visualização do HTML
 12. Nos campos **Condições de Exibição**, configure de acordo com sua necessidade, por exemplo, selecione uma Categoria, onde este conteúdo será disponibilizado.
 13. Clique no checkbox **Conteúdo Ativo**
 14. Clique em **Adicionar na Lista de Conteúdo**
-![](//images.contentful.com/alneenqid6w5/5tqciHrAD6aAgiSIwiKSKE/8ba1d1a683c168257e16dd949133809b/2016-04-05_16_28_19-Index.png)
+![](https://images.contentful.com/alneenqid6w5/5tqciHrAD6aAgiSIwiKSKE/8ba1d1a683c168257e16dd949133809b/2016-04-05_16_28_19-Index.png)
 15. Clique em **Salvar Configurações**
diff --git a/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md b/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md
index 14f749997..7004d9bd3 100644
--- a/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md
+++ b/docs/tutorials/pt/how-to-customize-the-checkout-ui-custom-in-the-admin.md
@@ -63,24 +63,24 @@ Nesta aba é possível realizar as seguintes configurações:
 
 A aba Cores permite personalizar as cores do checkout de sua loja, permitindo alterar cores de fundo, botões, texto entre outros. Essa padronização garante uma harmonia visual consistente.
 
-![Cores ](//images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/73b92d83429b6e2a0d61e2e7c1b4d20e/Cores_-_PT.png)
+![Cores ](https://images.ctfassets.net/alneenqid6w5/4H44wWoSRkxqorAvMIIdtG/73b92d83429b6e2a0d61e2e7c1b4d20e/Cores_-_PT.png)
 
 ## Javascript
 
 A aba JavaScript  adiciona uma camada adicional de personalização à interface permitindo a inclusão de scripts.
 
-![Java - PT](//images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/f71cb1f35775b2a770c12de7be5b9068/Java_-_PT.png)
+![Java - PT](https://images.ctfassets.net/alneenqid6w5/2Uz2vqftUh4RvMsMwuO6OR/f71cb1f35775b2a770c12de7be5b9068/Java_-_PT.png)
 
 ## CSS
 
 A aba CSS permite customizações visuais da loja com a inclusão de código CSS.
 
-![CSS - PT](//images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/ba9c09575f3ba303ad987f9001afb547/CSS_-_PT.png)
+![CSS - PT](https://images.ctfassets.net/alneenqid6w5/70CMxJWujBZ9qK4bCseGeH/ba9c09575f3ba303ad987f9001afb547/CSS_-_PT.png)
 
 ## Histórico
 
 Permite visualizar e restaurar customizações criadas e publicadas anteriormente.
 
-![Histórico - PT](//images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/66f5b12a5417725a619895df98c4fa96/Hist_rico_-_PT.png)
+![Histórico - PT](https://images.ctfassets.net/alneenqid6w5/6C0VthFtBjKP4S3aSS2BaX/66f5b12a5417725a619895df98c4fa96/Hist_rico_-_PT.png)
 
 Para garantir que suas configurações sejam aplicadas com sucesso, basta realizar as configurações necessárias e clicar no botão `Publicar`.
diff --git a/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
index c4853fe53..3753bf6c3 100644
--- a/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
@@ -23,7 +23,7 @@ Você pode alterar o **textLink** de um produto existente a qualquer momento pel
 
 Confira a seção [Regras de preenchimento](#regras-de-preenchimento) para entender as restrições desse campo.
 
-![textlink.pt](//images.ctfassets.net/alneenqid6w5/3K8sFWVJYkESKC7EVWP4zZ/37e4b22a4f177d28c197042ad027c3de/textlink.pt.png)
+![textlink.pt](https://images.ctfassets.net/alneenqid6w5/3K8sFWVJYkESKC7EVWP4zZ/37e4b22a4f177d28c197042ad027c3de/textlink.pt.png)
 
 <div class="alert alert-info">
   <p>Também é possível alterar a URL de um produto utilizando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview">API do Catálogo</a>. Nesse caso, o campo a ser alterado é o <code>LinkId</code>. Confira <a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product">Update Product</a> para mais informações.</p>
diff --git a/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md b/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md
index 86ee0e4d7..300c65107 100644
--- a/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md
+++ b/docs/tutorials/pt/how-to-deprecate-and-undeprecate-your-app.md
@@ -19,4 +19,4 @@ Caso você necessite realizar um rollback da sua app, rode o comando `vtex depre
 
 Se você perceber em seguida que será necessario desfazer a deprecação, poderá realizar o comando `vtex undeprecate`
 
-![image (2)](//images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
+![image (2)](https://images.ctfassets.net/alneenqid6w5/42XNwwb22OQKBkOTO5C2Bl/3bfbb5a89027e41dda9a7532a7591e7f/image__2_.png)
diff --git a/docs/tutorials/pt/how-to-disable-a-transactional-email.md b/docs/tutorials/pt/how-to-disable-a-transactional-email.md
index 031f43950..d3e1af53f 100644
--- a/docs/tutorials/pt/how-to-disable-a-transactional-email.md
+++ b/docs/tutorials/pt/how-to-disable-a-transactional-email.md
@@ -28,7 +28,7 @@ Confira o passo a passo a seguir:
 3. Pesquise por __Payment Pending__ na caixa de busca.
 4. Desmarque a opção __Ativar envio de e-mail__.
 
-  ![Message Center - Desativar - PT](//images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/3ed63d224e34fc3b5a52540cc880ba4a/dlSCQPRLKf46SnYGl7X9a_PT_Payment_Pending.jpg)
+  ![Message Center - Desativar - PT](https://images.ctfassets.net/alneenqid6w5/dlSCQPRLKf46SnYGl7X9a/3ed63d224e34fc3b5a52540cc880ba4a/dlSCQPRLKf46SnYGl7X9a_PT_Payment_Pending.jpg)
 
 5. Clique em __Salvar__.
 
diff --git a/docs/tutorials/pt/how-to-download-the-vtex-invoices.md b/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
index 2772af4bb..070897087 100644
--- a/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
@@ -47,7 +47,7 @@ Para fazer o download da sua fatura, siga os passos abaixo:
 
 Feito isso, sua fatura estará disponível em outra aba.
 
-![baixar faturas pt](//images.ctfassets.net/alneenqid6w5/2v9nnJfdYMrIw9DhYsV6oz/8acb4b8fe2db1b1cf36500cd2bff7b09/baixar_faturas_pt.gif)
+![baixar faturas pt](https://images.ctfassets.net/alneenqid6w5/2v9nnJfdYMrIw9DhYsV6oz/8acb4b8fe2db1b1cf36500cd2bff7b09/baixar_faturas_pt.gif)
 
 ## Brasil
 
@@ -67,7 +67,7 @@ Para fazer o download de seu boleto, siga os passos abaixo:
 
 <div class="alert alert-info"> No Brasil, uma fatura roxa pode indicar que está atrasada mas com um novo boleto gerado para uma data próxima. Nesse caso, a fatura continuará em atraso até a quitação do pagamento. Caso não seja efetuado o pagamento do novo boleto, a fatura voltará a cor vermelha.</div>
 
-![baixar boletos pt](//images.ctfassets.net/alneenqid6w5/3gRniiqHrpZZHNTsQC8Gfm/21d45f702de76ea5c866b61a3c80be8f/baixar_boletos_pt.gif)
+![baixar boletos pt](https://images.ctfassets.net/alneenqid6w5/3gRniiqHrpZZHNTsQC8Gfm/21d45f702de76ea5c866b61a3c80be8f/baixar_boletos_pt.gif)
 
 ### Fazer download da Nota Fiscal
 
@@ -84,6 +84,6 @@ Desse modo, a Nota Fiscal será aberta em outra aba do seu navegador. Clique **I
 1. Em Destino, selecione a opção **Salvar em PDF**.
 2. Para finalizar, clique em **Salvar**.
 
-![baixar notafiscal pt](//images.ctfassets.net/alneenqid6w5/5jKzvOnt2V3JtrvKfxJ9zU/8ce862d5a13587d72464d3a3efea907f/baixar_notafiscal_pt.gif)
+![baixar notafiscal pt](https://images.ctfassets.net/alneenqid6w5/5jKzvOnt2V3JtrvKfxJ9zU/8ce862d5a13587d72464d3a3efea907f/baixar_notafiscal_pt.gif)
 
 Caso você tenha dúvidas sobre o valor cobrado na fatura, leia o artigo [Compreenda o valor da receita aprovada](https://help.vtex.com/pt/tutorial/como-acessar-o-valor-da-receita-aprovada--tutorials_4322) para entender o valor que foi cobrado.
diff --git a/docs/tutorials/pt/how-to-find-an-sku-id.md b/docs/tutorials/pt/how-to-find-an-sku-id.md
index 7b764ae7e..c8759a9a1 100644
--- a/docs/tutorials/pt/how-to-find-an-sku-id.md
+++ b/docs/tutorials/pt/how-to-find-an-sku-id.md
@@ -34,7 +34,7 @@ Para descobrir o ID de um SKU pelo Admin, siga os passos abaixo:
 
 No exemplo abaixo, o ID do SKU é __18__.
 
-![skuId-1](//images.contentful.com/alneenqid6w5/3CEFOn0h8Ac6ciGgi6gmEK/2d64944b8added0ec12d5cdc7ebe9d9c/skuId-1.png)
+![skuId-1](https://images.contentful.com/alneenqid6w5/3CEFOn0h8Ac6ciGgi6gmEK/2d64944b8added0ec12d5cdc7ebe9d9c/skuId-1.png)
 
 ## URL de cadastro do SKU
 
diff --git a/docs/tutorials/pt/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md b/docs/tutorials/pt/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
index 5881e93c4..b94a1db86 100644
--- a/docs/tutorials/pt/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
+++ b/docs/tutorials/pt/how-to-find-google-indexed-urls-that-are-inactive-or-contain-errors.md
@@ -23,17 +23,17 @@ Caso contrário, as páginas indexadas pelo Google com o conteúdo antigo serão
 
 Você precisará acessar sua conta no Web Master Tools do Google. Lá você poderá verificar os números de páginas com erros.
 
-![locateURL1](//images.contentful.com/alneenqid6w5/qEYJuUx2hweIuuMCsQWmE/4667542aeafdfd92daecce10dd7853a6/locateURL1.jpg)
+![locateURL1](https://images.contentful.com/alneenqid6w5/qEYJuUx2hweIuuMCsQWmE/4667542aeafdfd92daecce10dd7853a6/locateURL1.jpg)
 
 Clique em **Rastreamento** e depois em **Erros de Rastreamentos**, como na imagem abaixo:
 
-![locateURL2](//images.contentful.com/alneenqid6w5/2bcdyY8KJqO6EwQOMKys8k/61845c81da0a9718bb46b9df40dff91c/locateURL2.jpg)
+![locateURL2](https://images.contentful.com/alneenqid6w5/2bcdyY8KJqO6EwQOMKys8k/61845c81da0a9718bb46b9df40dff91c/locateURL2.jpg)
 
 Nessa área você poderá visualizar quando ocorreu o erro, com qual URL, e qual é o erro apresentado. Você então poderá exportar uma planilha (\*.csv)
 
-![locateURL3](//images.contentful.com/alneenqid6w5/5pmI5i6RFK4Icku40ua22S/43135af03b16a77ca55bdc3fb53207ea/locateURL3.jpg)
-![locateURL4](//images.contentful.com/alneenqid6w5/6QLDHdNJpCgWgAM6eO8QEi/8f5f07ce59f07c34cefa48b893767ac4/locateURL4.jpg)
+![locateURL3](https://images.contentful.com/alneenqid6w5/5pmI5i6RFK4Icku40ua22S/43135af03b16a77ca55bdc3fb53207ea/locateURL3.jpg)
+![locateURL4](https://images.contentful.com/alneenqid6w5/6QLDHdNJpCgWgAM6eO8QEi/8f5f07ce59f07c34cefa48b893767ac4/locateURL4.jpg)
 
 Você poderá incluir esses links na planilha, fazendo referência à Home, ou coleção, o que for mais adequado à sua loja. Após a correção desses links você precisará voltar ao Web Master Tools, clicar em **Rastreamento** e depois em **Erros de Rastreamentos**.
 
-![locateURL5](//images.contentful.com/alneenqid6w5/54CtZsR9SM2Q8QSEoUaUmy/6a77ef45455da13bb84c8ce005ddaa29/locateURL5.jpg)
+![locateURL5](https://images.contentful.com/alneenqid6w5/54CtZsR9SM2Q8QSEoUaUmy/6a77ef45455da13bb84c8ce005ddaa29/locateURL5.jpg)
diff --git a/docs/tutorials/pt/how-to-identify-a-page-template.md b/docs/tutorials/pt/how-to-identify-a-page-template.md
index 77dcb5b50..fccaae482 100644
--- a/docs/tutorials/pt/how-to-identify-a-page-template.md
+++ b/docs/tutorials/pt/how-to-identify-a-page-template.md
@@ -27,7 +27,7 @@ A VTEX usa o mesmo princípio. O diretório (pasta) é onde deve ser guardada to
 
 Podemos criar inúmeros templates mas devemos especificar no diretório qual template será exibido. Usando a página de __Produto__ como exemplo:
 
-![cms-template-pagina PT](//images.ctfassets.net/alneenqid6w5/5f0VY6nFAAecUce6SQq02m/266795c901433c282669bbb1af7ccb7e/Produto_CMS.png)
+![cms-template-pagina PT](https://images.ctfassets.net/alneenqid6w5/5f0VY6nFAAecUce6SQq02m/266795c901433c282669bbb1af7ccb7e/Produto_CMS.png)
 
 Storefront > Layout > Pasta CMS > Sites and channels > Nome da Loja > Pasta raíz (/) > Produto (por exemplo) > Clicar no link que estiver com a setinha vermelha de "ok"
 
@@ -39,13 +39,13 @@ Para dar flexibilidade é possível ainda incluir subtemplates e inúmeros outro
 
 Agora um exemplo real. Quero identificar qual página é essa que estou navegando:
 
-![Captura-de-Tela-2017-03-01-às-2.49.14-PM-768x445](//images.contentful.com/alneenqid6w5/56TdUPaA48yyoKIUA08uuE/0a1b652077800bd371e41e68c7739f45/Captura-de-Tela-2017-03-01-a__s-2.49.14-PM-768x445.png)
+![Captura-de-Tela-2017-03-01-às-2.49.14-PM-768x445](https://images.contentful.com/alneenqid6w5/56TdUPaA48yyoKIUA08uuE/0a1b652077800bd371e41e68c7739f45/Captura-de-Tela-2017-03-01-a__s-2.49.14-PM-768x445.png)
 
 O próprio domínio muitas vezes já me ajuda a identificar, mas algumas lojas podem customizar isso o que pode dificultar esse trabalho. No caso estou na dúvida se é uma pagina de __Departamento__ ou __Categoria__, talvez possa inclusive ser uma customização de prateleira.
 
 O melhor caminho é conferindo no Código Fonte da página (Ctrl + U). Lojas VTEX vão possuir um indicativo de qual diretório pertence a página.
 
-![Captura-de-Tela-2017-03-01-às-2.51.06-PM-768x89](//images.contentful.com/alneenqid6w5/uIxNOdyuY02GqegWMGGcC/2171322309535c4b93ff9b36132d8be3/Captura-de-Tela-2017-03-01-a__s-2.51.06-PM-768x89.png)
+![Captura-de-Tela-2017-03-01-às-2.51.06-PM-768x89](https://images.contentful.com/alneenqid6w5/uIxNOdyuY02GqegWMGGcC/2171322309535c4b93ff9b36132d8be3/Captura-de-Tela-2017-03-01-a__s-2.51.06-PM-768x89.png)
 
 No exemplo acima: `<!-- CommerceContext.Current.VirtualFolder.Name: @categoria@ -->`
 Agora que sabemos que é uma página de categoria, precisamos identificar qual template está ativo para Categoria. Para isso basta repetir o processo aplicado no exemplo anterior.
diff --git a/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md b/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md
index 2e39500f4..75917f36c 100644
--- a/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md
+++ b/docs/tutorials/pt/how-to-identify-layout-errors-caused-by-javascript-files.md
@@ -26,7 +26,7 @@ Para isso faça os seguintes passos :
 1. Para desabilitar o JS da página basta colocar o `/tools.html` no fim da URL. Ex: {AccountName}.myvtex.com/tools.html
 2. Clique em __Disable__ na aba __Client JavaScript is__.
 
-![javascript-disable ](//images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png) 
+![javascript-disable ](https://images.ctfassets.net/alneenqid6w5/2rDNQsznK8umymyKaOoYkA/1c4306998c4d580505dfaffe20ca66fa/js_enabled.png) 
 
 3. Após isso, retire o `/tools.html` da URL e atualize a página.
 
diff --git a/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
index 271bb5c66..defb71d61 100644
--- a/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
@@ -40,7 +40,7 @@ No carrinho, você pode passar o mouse sobre o ícone de interrogação que fica
 
 Porém, caso mais de uma promoção seja aplicada, o que aparecerá será apenas o somatório dos descontos, dificultando a análise do cenário.
 
-![example-cart](//images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/58e4571f3ce7b0af86ecf17885799258/image6.png)
+![example-cart](https://images.ctfassets.net/alneenqid6w5/4OuONCFldxuXYgevJ8wU81/58e4571f3ce7b0af86ecf17885799258/image6.png)
 
 ## orderForm
 
@@ -56,7 +56,7 @@ Siga o passo a passo para encontrar o orderForm e identificar as promoções apl
 2. Clique em `Network`.
 3. Marque a opção **Preserve log**.
 4. Recarregue a página.
-5. Após o carregamento, pressione `Ctrl+F` para fazer uma busca na janela das **Ferramentas de Desenvolvedor**. Digite `orderForm` na barra de busca.![order-form](//images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
+5. Após o carregamento, pressione `Ctrl+F` para fazer uma busca na janela das **Ferramentas de Desenvolvedor**. Digite `orderForm` na barra de busca.![order-form](https://images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
 6. Clique sobre a linha do `orderForm`. Ao lado abrirá uma nova janela.
 7. Clique em `Preview`.
 8. Procure por `ratesAndBenefitsData` e clique sobre o item.
diff --git a/docs/tutorials/pt/how-to-identify-promotions-attributed-to-an-sku.md b/docs/tutorials/pt/how-to-identify-promotions-attributed-to-an-sku.md
index 2ecc0af1b..6dcab14fe 100644
--- a/docs/tutorials/pt/how-to-identify-promotions-attributed-to-an-sku.md
+++ b/docs/tutorials/pt/how-to-identify-promotions-attributed-to-an-sku.md
@@ -24,12 +24,12 @@ Escrevemos este artigo para responder a uma dúvida recorrente dos usuários da
 Para descobrir quais promoções estão sendo atribuídas a um SKU, devemos analisar suas `priceTags`.
 
 1. Acesse o carrinho com o produto.
-2. No Google Chrome, acesse **Ferramentas de Desenvolvedor** (`Ctrl+Shift+I`).![ferramentas-do-desenvolvedor](//images.contentful.com/alneenqid6w5/3NBGEPjXEkkSqA2WOYs8us/5219ffe6515a120ac0e6d489c78e5820/ferramentas-do-desenvolvedor.png)
-3. Selecione a aba **Network** e pressione `F5` para gravar o carregamento da página.![network-f5](//images.contentful.com/alneenqid6w5/1TZRay17qkEO8As8w0MKOS/f4d88d06f2a3fd656aa41e3809f35d45/network-f5.png)
-4. Após o carregamento, pressione `Ctrl+F` para fazer uma busca na janela das __Ferramentas de Desenvolvedor__ e busque por `orderForm`.![order-form](//images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
-5. Clique em `orderForm` e vá em `items`. Após clicar em `items`, clique nos números (`0`, `1`, `2` etc.) para ver as características do produto desejado. Em nosso exemplo, como temos apenas um item, este é representado pelo número `0` no array.![items-0](//images.contentful.com/alneenqid6w5/DUtSiCdnrwSmoKqqYW8E6/ec7335a0c9308b17b9d8aa2274057220/items-0.png)
-6. Após clicar no número, desça o scroll até `priceTags`. Clique em priceTags e então clique nos números (`0`, `1`, `2` etc.) para ver as características da promoção desejada. Em nosso exemplo, como temos apenas uma promoção, esta é representada pelo número `0` no array. Após isto, busque pelo `identifier` da promoção.![priceTags-0-identifier](//images.contentful.com/alneenqid6w5/5MCOrSJPaMSYQcimY8CKos/ca8960a1a98f680406daf7879d241987/priceTags-0-identifier.png)
-7. Em outra aba, acesse a URL `https://{accountName}.vtexcommercestable.com.br/admin/rnb/#/benefit/{numero-do-identifier}`. Esta é a promoção que está sendo efetivamente aplicada ao produto no carrinho. Verifique as configurações da promoção e veja se as condições se aplicam ao SKU em questão.![promo-debug-help](//images.contentful.com/alneenqid6w5/5G2eJ4AilySK0o8ugaOMq4/b4dba231e9812906a45af5a4432d9783/promo-debug-help.png)
+2. No Google Chrome, acesse **Ferramentas de Desenvolvedor** (`Ctrl+Shift+I`).![ferramentas-do-desenvolvedor](https://images.contentful.com/alneenqid6w5/3NBGEPjXEkkSqA2WOYs8us/5219ffe6515a120ac0e6d489c78e5820/ferramentas-do-desenvolvedor.png)
+3. Selecione a aba **Network** e pressione `F5` para gravar o carregamento da página.![network-f5](https://images.contentful.com/alneenqid6w5/1TZRay17qkEO8As8w0MKOS/f4d88d06f2a3fd656aa41e3809f35d45/network-f5.png)
+4. Após o carregamento, pressione `Ctrl+F` para fazer uma busca na janela das __Ferramentas de Desenvolvedor__ e busque por `orderForm`.![order-form](https://images.contentful.com/alneenqid6w5/jtqrcUjDAAqoMUGiYM4qE/94803953c1577a7954ba09f163738e0e/order-form.png)
+5. Clique em `orderForm` e vá em `items`. Após clicar em `items`, clique nos números (`0`, `1`, `2` etc.) para ver as características do produto desejado. Em nosso exemplo, como temos apenas um item, este é representado pelo número `0` no array.![items-0](https://images.contentful.com/alneenqid6w5/DUtSiCdnrwSmoKqqYW8E6/ec7335a0c9308b17b9d8aa2274057220/items-0.png)
+6. Após clicar no número, desça o scroll até `priceTags`. Clique em priceTags e então clique nos números (`0`, `1`, `2` etc.) para ver as características da promoção desejada. Em nosso exemplo, como temos apenas uma promoção, esta é representada pelo número `0` no array. Após isto, busque pelo `identifier` da promoção.![priceTags-0-identifier](https://images.contentful.com/alneenqid6w5/5MCOrSJPaMSYQcimY8CKos/ca8960a1a98f680406daf7879d241987/priceTags-0-identifier.png)
+7. Em outra aba, acesse a URL `https://{accountName}.vtexcommercestable.com.br/admin/rnb/#/benefit/{numero-do-identifier}`. Esta é a promoção que está sendo efetivamente aplicada ao produto no carrinho. Verifique as configurações da promoção e veja se as condições se aplicam ao SKU em questão.![promo-debug-help](https://images.contentful.com/alneenqid6w5/5G2eJ4AilySK0o8ugaOMq4/b4dba231e9812906a45af5a4432d9783/promo-debug-help.png)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md b/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md
index c46dc1b7f..310f13172 100644
--- a/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md
+++ b/docs/tutorials/pt/how-to-identify-the-store-and-salesperson-in-an-instore-order.md
@@ -29,7 +29,7 @@ Para enviar dados de pedidos para sistemas externos, como dashboards e data lake
 
 Quando um pedido é fechado no inStore, a identificação do usuário logado no aplicativo fica visível na parte superior da tela de detalhes do pedido no Admin. No exemplo abaixo, o nome do usuário é `A123456`.
 
-![PT - ID do vendedor inStore](//images.ctfassets.net/alneenqid6w5/2VlKApkaFLzzxl6wRrcNkw/b46bb2740a82a8fab8988f7dd752f7ce/PT_-_ID_do_vendedor_inStore.png)
+![PT - ID do vendedor inStore](https://images.ctfassets.net/alneenqid6w5/2VlKApkaFLzzxl6wRrcNkw/b46bb2740a82a8fab8988f7dd752f7ce/PT_-_ID_do_vendedor_inStore.png)
 
 Quando os detalhes do pedido são obtidos pela [Orders API](https://developers.vtex.com/vtex-developer-docs/reference/orders), o nome do usuário está disponível no campo `callCenterOperatorData.userName`. Também é possível acessar o e-mail deste usuário em  `callCenterOperatorData.email`.
 
@@ -43,7 +43,7 @@ Quando os detalhes do pedido são obtidos pela [Orders API](https://developers.v
 
 Caso o usuário logado no aplicativo seja compartilhado entre vendedores da mesma loja, é possível ainda incluir a identificação do vendedor no campo de observação do cliente.
 
-![PT - ID do vendedor inStore (alt)](//images.ctfassets.net/alneenqid6w5/2VFGuKA7ZUgcO55TPgpDWU/ce44ee5a33db7284999dc2700d964f75/PT_-_ID_do_vendedor_inStore__alt_.png)
+![PT - ID do vendedor inStore (alt)](https://images.ctfassets.net/alneenqid6w5/2VFGuKA7ZUgcO55TPgpDWU/ce44ee5a33db7284999dc2700d964f75/PT_-_ID_do_vendedor_inStore__alt_.png)
 
 Quando os detalhes do pedido são obtidos pela Orders API, esta informação fica disponível no campo `openTextField.value`.
 
@@ -57,7 +57,7 @@ Quando os detalhes do pedido são obtidos pela Orders API, esta informação fic
 
 Quando um pedido é fechado no inStore, a identificação da loja fica visível na seção de Promoções e Parcerias da tela de detalhes do pedido no Admin. No exemplo abaixo, o identificador da loja é `8b4d5ea1-2055-11ea-82fa-0ad725bc7b4f`.
 
-![PT - ID da loja inStore](//images.ctfassets.net/alneenqid6w5/x0Czqfo4emIb8X6zgQgD2/e6867ef4cf7bd54cd471ee7d07ccd59c/PT_-_ID_da_loja_inStore.png)
+![PT - ID da loja inStore](https://images.ctfassets.net/alneenqid6w5/x0Czqfo4emIb8X6zgQgD2/e6867ef4cf7bd54cd471ee7d07ccd59c/PT_-_ID_da_loja_inStore.png)
 
 Quando os detalhes do pedido são obtidos pela Orders API, esta informação fica disponível no campo `marketingData.utmSource`.
 
@@ -82,7 +82,7 @@ Quando os detalhes do pedido são obtidos pela Orders API, esta informação fic
 
 O identificador do vendedor e da loja podem ser usados para consultar os dados de cadastro em `https://{accountName}.myvtex.com/admin/vtable`. 
 
-![PT - Admin inStore](//images.ctfassets.net/alneenqid6w5/4k1KmCEABh6BJBBCBh5B4F/fe249d924308d3d2f8b7fbfbec739f05/Screen_Shot_2020-11-09_at_15.20.50.png)
+![PT - Admin inStore](https://images.ctfassets.net/alneenqid6w5/4k1KmCEABh6BJBBCBh5B4F/fe249d924308d3d2f8b7fbfbec739f05/Screen_Shot_2020-11-09_at_15.20.50.png)
 
 <div class="alert alert-info" role="alert">As instruções abaixo explicam como fazer essas consultas usando os identificadores que aparecem em um pedido. Se necessário, entretanto, é possível buscar usando qualquer campo do cadastro de lojas e vendedores.</div>
 
@@ -98,7 +98,7 @@ Para fazer essa busca, siga as instruções abaixo:
 
 Ao concluir o passo 4, a expressão do filtro de busca deve ficar no formato `Nome:=:A123456`. Assim será possível encontrar o vendedor na listagem de vendedores, como visto na imagem abaixo.
 
-![PT - Admin dos vendedores](//images.ctfassets.net/alneenqid6w5/601CfGNUMAQyhhWyNcpJg6/67b8789e9b10570025613023fc8e1e30/PT_-_Admin_dos_vendedores.png)
+![PT - Admin dos vendedores](https://images.ctfassets.net/alneenqid6w5/601CfGNUMAQyhhWyNcpJg6/67b8789e9b10570025613023fc8e1e30/PT_-_Admin_dos_vendedores.png)
 
 Caso prefira fazer essa consulta por API, basta usar o endpoint [Search Documents](https://developers.vtex.com/vtex-developer-docs/reference/search#searchdocuments) da [Master Data API - V2](https://developers.vtex.com/reference/master-data-api-v2-overview) para buscar pelo identificador da loja na entidade de dados `vendors`.
 
@@ -114,6 +114,6 @@ Para fazer essa busca, siga as instruções abaixo:
 
 Ao concluir o passo 4, a expressão do filtro de busca deve ficar no formato `Id do Documento:=:8b4d5ea1-2055-11ea-82fa-0ad725bc7b4f`. Assim será possível encontrar a loja na listagem de lojas, como visto na imagem abaixo.
 
-![PT - Admin das lojas](//images.ctfassets.net/alneenqid6w5/ZORye3vSq6dVZ5aE4SRnl/dca845c2c8a16a01b75f9cca1b2b6d2a/PT_-_Admin_das_lojas.png)
+![PT - Admin das lojas](https://images.ctfassets.net/alneenqid6w5/ZORye3vSq6dVZ5aE4SRnl/dca845c2c8a16a01b75f9cca1b2b6d2a/PT_-_Admin_das_lojas.png)
 
 Caso prefira fazer essa consulta por API, basta usar o endpoint [Search Documents](https://developers.vtex.com/vtex-developer-docs/reference/search#searchdocuments) da [Master Data API - V2](https://developers.vtex.com/reference/master-data-api-v2-overview) para buscar pelo identificador da loja na entidade de dados `stores`.
diff --git a/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
index dae42a7d7..943919156 100644
--- a/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
@@ -17,7 +17,7 @@ subcategory: 1c5Btie9ou2Gg2iUo0ggqM
 
 Os pontos de retirada, também conhecidos como pickup points, são parte importante de qualquer estratégia [omnichannel](/pt/announcement/mude-seu-negocio-com-a-experiencia-omnichannel-vtex).
 
-Você pode [configurar pontos de retirada um a um](/pt/tutorial/configurar-pontos-de-retirada-pickup-points) ou fazer isso através da importação de uma planilha XLS [(como a deste exemplo)](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Usando um arquivo XLS, você cadastra todos os pickup points de uma única vez (desde que ele não ultrapasse 10 MB).
+Você pode [configurar pontos de retirada um a um](/pt/tutorial/configurar-pontos-de-retirada-pickup-points) ou fazer isso através da importação de uma planilha XLS [(como a deste exemplo)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Usando um arquivo XLS, você cadastra todos os pickup points de uma única vez (desde que ele não ultrapasse 10 MB).
 
 <div class="alert alert-info">
 Um arquivo XLS de <strong>10 MB</strong> permite o cadastro de, aproximadamente, <strong>50 mil</strong> pontos de retirada. Para importar um número maior, é necessário dividi-los em mais de uma planilha e fazer um upload de cada vez.
@@ -27,8 +27,8 @@ Um arquivo XLS de <strong>10 MB</strong> permite o cadastro de, aproximadamente,
 ## Como fazer o upload da planilha
 1. No menu lateral, clique em __Estoque & entrega__, na seção __Pedidos__.
 2. Nas opções que se abrem, clique em __Pontos de retirada__.
-3. Clique em __Subir um XLS__, localizado no canto superior direito da página. ![Subir XLS](//images.ctfassets.net/alneenqid6w5/405kNpYa3mg6iSaS0UgQmq/4f544dfad6e5e7b95e63c5420c8884fe/Subir_XLS.png)
-4. Um modal vai surgir, permitindo que você envie seu arquivo (com extensão `.xls`) ou baixe a [planilha de exemplo](//assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Lembre-se de que ela vem com valores de exemplo preenchidos, que devem ser deletados e substituídos pelos dados dos seus próprios pontos de retirada. ![modal (PT)](//images.ctfassets.net/alneenqid6w5/20X1H7Xla4WsqoG24UssK2/12a46b5171a72837f5ad6fb46287aae5/modal__PT_.png)
+3. Clique em __Subir um XLS__, localizado no canto superior direito da página. ![Subir XLS](https://images.ctfassets.net/alneenqid6w5/405kNpYa3mg6iSaS0UgQmq/4f544dfad6e5e7b95e63c5420c8884fe/Subir_XLS.png)
+4. Um modal vai surgir, permitindo que você envie seu arquivo (com extensão `.xls`) ou baixe a [planilha de exemplo](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Lembre-se de que ela vem com valores de exemplo preenchidos, que devem ser deletados e substituídos pelos dados dos seus próprios pontos de retirada. ![modal (PT)](https://images.ctfassets.net/alneenqid6w5/20X1H7Xla4WsqoG24UssK2/12a46b5171a72837f5ad6fb46287aae5/modal__PT_.png)
 5. Com tudo certo, os novos pontos de retirada vão estar configurados e disponíveis para seus clientes.
 
 
diff --git a/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
index 6d1061aec..2b6c45ac0 100644
--- a/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -27,31 +27,31 @@ Realizadas as devidas definições, o vínculo da coleção com a vitrine é fei
 
 No exemplo a seguir, iremos definir a vitrine apresentada na Home, para isso, selecione **Settings**, depois **add object**, conforme na imagem a seguir.
 
-![coleção2](//images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
+![coleção2](https://images.ctfassets.net/alneenqid6w5/5JzAgUQ2NU4oIM88Kqm8AW/a4d8c175710d8542dc0099cd16c5168d/cole____o2.png)
 
 Esse comando irá abrir o **Visual Controls**, ou seja, o controle correspondente à vitrine em que se deseja exibir a coleção. Adicione uma _Coleção_, porém não se esqueça de definir um nome para ela.
 
-![coleção3](//images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
+![coleção3](https://images.ctfassets.net/alneenqid6w5/12pUvp3l5u0CcIISmG6g2A/cf86f9d87c6c9ee2e9f1db979d2b2836/cole____o3.png) 
 
-![coleção4](//images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
+![coleção4](https://images.ctfassets.net/alneenqid6w5/6XdqMY2IAoy6ugIK4KcYEk/0491e41c7dda3da46334ab975fe7f2ee/cole____o4.png)
 
 Para editar o controle criado, é necessário salvar as configurações primeiramente em **Save Settings**.
 
-![coleção5](//images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
+![coleção5](https://images.ctfassets.net/alneenqid6w5/3edZaVppl6cuU64yqisaGm/4cb795f99bf6227597d044736a7e0184/cole____o5.png)
 
-![coleção6](//images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
+![coleção6](https://images.ctfassets.net/alneenqid6w5/Zry4UUPxW8Eic6yWmok4C/a997c64b6c59a0f3a3551228a685ff58/cole____o6.png)
 
 Ao editar o controle é necessário adicionar seus conteúdos, que representam cada conjunto de itens que serão exibidos.
 São eles:
 _Layout_: Selecione o template de prateleira utilizado na vitrine.
 _Number of Columns, Number of Items,Show Unavailable, Ramdom ad Paged_: Definem a disposição, quantidade e qual o critério de exibição dos itens.
 
-![coleção7](//images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
+![coleção7](https://images.ctfassets.net/alneenqid6w5/4A4DMctlIkaaa2OGeAMwSq/a8205c9b1715f46dc9b8feac175de132/cole____o7.png)
 
 Lembre-se de salvar as alterações antes de efetuar uma busca ou mudar de página.
 
 O próximo passo é adicionar o conteúdo, selecionando **Add Content**.
-![coleção8](//images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
+![coleção8](https://images.ctfassets.net/alneenqid6w5/ytG3zPwgDY4SQwYWsa6am/27dc5ad87b2f0b25d33b991ab006c7df/cole____o8.png)
 
 É possível definir cada conteúdo utilizando coleções ou resultados de busca, utilizando parâmetros de busca (mais detalhes [aqui](/pt/tutorial/parametros-de-busca "aqui"))
 
@@ -61,7 +61,7 @@ _QueryString_: Os parâmetros preenchidos nesse campo definem o resultado de bus
 
 No campo **Product Cluster (Collection)**, é necessário selecionar a coleção que será exibida, para isso, siga o passo a seguir:
 
-![coleção10](//images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
+![coleção10](https://images.ctfassets.net/alneenqid6w5/RHE3D2CrkG0qSguGsMS40/aa6db36e948f397ca2b1c0abc4a69be1/cole____o10.png)
 
 Os conteúdos a serem preenchidos na parte **Display Condition**:
 _Partner, Campaign_ e _Source_: Definem a exibição deste conteúdo, caso o visitante possua alguma UTM correspondente em sua URL de origem.
@@ -73,7 +73,7 @@ Após as definições, deve-se marcar a opção **Active Content** e adicionar n
 
 No exemplo abaixo temos uma vitrine padrão, sem condições de exibição, e outra exclusiva para as visitas oriundas das audiências de campanhas patrocinadas do Google (utm_source=**google**/utm_medium=**cpc**):
 
-![coleção9](//images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
+![coleção9](https://images.ctfassets.net/alneenqid6w5/5IoPfaWgUwUsGUuCAmYS6q/ded32f70db90ffb4f3fffd740b35381b/cole____o9.png)
 
 No cenário acima, caso o cliente tenha origem na audiência de campanha patrocinada serão exibidos na vitrine **Lançamentos**, localizada na Home, os produtos que correspondem ao resultado de uma busca pela Marca de ID 200000, caso contrário, serão exibidos os produtos da coleção de ID 8.
 
diff --git a/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md b/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md
index 134585aec..06090e085 100644
--- a/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md
+++ b/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md
@@ -37,9 +37,9 @@ Vamos dizer, por exemplo, que voce deseje editar as informações de um cliente
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
 2. No Master Data, clique em **Aplicações**.
-3. Dentro da aplicação **Profile System**, escolha o formulário **Clientes**.![IncluirRegistro1](//images.contentful.com/alneenqid6w5/RnwtCnfBccYk06g8se4OE/94fbce274f877694e8f4cbd09e44e9ba/IncluirRegistro1.png)
+3. Dentro da aplicação **Profile System**, escolha o formulário **Clientes**.![IncluirRegistro1](https://images.contentful.com/alneenqid6w5/RnwtCnfBccYk06g8se4OE/94fbce274f877694e8f4cbd09e44e9ba/IncluirRegistro1.png)
 4. Busque o usuário pelo campo **E-mail** (ou outro campo definido na entidade de dados como buscável).
-5. Clique em **Editar** uma vez dentro do cadastro do usuário.![IncluirRegistro2](//images.contentful.com/alneenqid6w5/2KvY5k3iTSI8CsEaG4mkyq/546835e1a58293c1d3c350733c5e7f7e/IncluirRegistro2.png)
+5. Clique em **Editar** uma vez dentro do cadastro do usuário.![IncluirRegistro2](https://images.contentful.com/alneenqid6w5/2KvY5k3iTSI8CsEaG4mkyq/546835e1a58293c1d3c350733c5e7f7e/IncluirRegistro2.png)
 6. Faça a edição desejada e clique em **Salvar**.
 
 As informações apresentadas neste exemplo vêm da da entidade de dados **CL**, e seus campos podem ser configurados como editáveis ou não diretamente na entidade de dados.
diff --git a/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md b/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
index 40a5c95da..721fdf52c 100644
--- a/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
+++ b/docs/tutorials/pt/how-to-include-metadata-when-exporting-a-prices-spreadsheet.md
@@ -18,10 +18,10 @@ subcategory: 4id9W3RDyw02CasOm2C2iy
 Para incluir metadados ao exportar uma planilha de preços de SKUs siga os passos abaixo:
 
 1. Clique em **Preços**, no menu do lado esquerdo da página
-![refidplanilha1](//images.ctfassets.net/alneenqid6w5/7rc4ppgcGNvFETJ2GxAQlt/32d2770ca9ecaaa693b49031d5bb4705/refidplanilha1.png)
+![refidplanilha1](https://images.ctfassets.net/alneenqid6w5/7rc4ppgcGNvFETJ2GxAQlt/32d2770ca9ecaaa693b49031d5bb4705/refidplanilha1.png)
 2. Clique em **lista de preços**
 3.  Na parte superior da página, lado esquerdo, clique no ícone de **seta para baixo**
 4. Na aba lateral que se abrirá, escolha a opção de tabela que deseja exportar
 5. Clique em **incluir metadados nas tabelas exportadas**
 6. Clique no botão **Exportar tabela**
-![refidplanilha2](//images.ctfassets.net/alneenqid6w5/4NgcVyUUruaf5sfR8cDpWP/93c4f35d46fe8c8ff5fccb372a072379/refidplanilha2.png)
+![refidplanilha2](https://images.ctfassets.net/alneenqid6w5/4NgcVyUUruaf5sfR8cDpWP/93c4f35d46fe8c8ff5fccb372a072379/refidplanilha2.png)
diff --git a/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md b/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md
index f9a345fe5..19ffc72c0 100644
--- a/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md
+++ b/docs/tutorials/pt/how-to-install-and-setup-the-vtex-tracking-app-on-your-vtex-admin.md
@@ -38,7 +38,7 @@ Feito isso, sua plataforma VTEX terá a nova aba VTEX Tracking liberada no menu
 
 A integração entre sua loja no Admin da VTEX, e a app VTEX Tracking depende de algumas configurações. Confira abaixo as configurações necessárias para que seu serviço VTEX Tracking seja ativado, e o passo a passo para acessar o menu de Configurações. 
 
-![VTEX Tracking app install](//images.ctfassets.net/alneenqid6w5/2TreUSwOkfK0VVTLxHLFpi/a6005d9583994252ea385c55bd1a35a6/VTEX_Tracking_app_install.jpg) 
+![VTEX Tracking app install](https://images.ctfassets.net/alneenqid6w5/2TreUSwOkfK0VVTLxHLFpi/a6005d9583994252ea385c55bd1a35a6/VTEX_Tracking_app_install.jpg) 
 
 1. No Admin VTEX, acesse **Aplicativos > Apps instalados > VTEX Tracking**, ou digite **VTEX Tracking** na barra de busca no topo da página.
 2. Digite o **Token da API** na caixa de texto.  
diff --git a/docs/tutorials/pt/how-to-install-the-masterpass-in-the-vtex-app-store.md b/docs/tutorials/pt/how-to-install-the-masterpass-in-the-vtex-app-store.md
index 9c63bbd8e..d3e2e66ae 100644
--- a/docs/tutorials/pt/how-to-install-the-masterpass-in-the-vtex-app-store.md
+++ b/docs/tutorials/pt/how-to-install-the-masterpass-in-the-vtex-app-store.md
@@ -23,7 +23,7 @@ Este artigo tem o objetivo de mostrar o passo-a-passo para instalação da exten
 
 Em primeiro lugar, na tela **Explorar**, clique na extensão **Masterpass**.
 
-![Extension Store 1](//images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
+![Extension Store 1](https://images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
 
 Você terá então acesso à página de detalhes da extensão, onde as seguintes informações são mostradas:
 
@@ -38,17 +38,17 @@ Para instalar o Masterpass, basta clicar no botão verde à direita do ícone da
 
 O botão de instalação leva à tela de permissões, onde é possível visualizar todos os dados e locais a que a extensão deseja ter acesso.
 
-![Masterpass1](//images.contentful.com/alneenqid6w5/qxOKuZ9dZY2Gy8osWg26A/f553a03370fb198e8dd38d95bd20bb35/Masterpass1.gif)
+![Masterpass1](https://images.contentful.com/alneenqid6w5/qxOKuZ9dZY2Gy8osWg26A/f553a03370fb198e8dd38d95bd20bb35/Masterpass1.gif)
 
 Uma vez que você aceite as permissões, a extensão será instalada.
 
-![Masterpass2](//images.contentful.com/alneenqid6w5/4rxdPuNq0oO2QuCiMaISAy/e8cca1acea0db1e87a0573b8c23f2013/Masterpass2.png)
+![Masterpass2](https://images.contentful.com/alneenqid6w5/4rxdPuNq0oO2QuCiMaISAy/e8cca1acea0db1e87a0573b8c23f2013/Masterpass2.png)
 
 ## Configuração
 
 Para funcionar corretamente, você precisa cumprir uma etapa de configuração. Basta preencher alguns campos, como os mostrados na imagem abaixo, e clicar em **Criar conta**.
 
-![Masterpass3](//images.contentful.com/alneenqid6w5/5XbYGeSd2gy4QEaIiMeqQ0/a20d27e9aa18af9a95767fb604e82d7c/Masterpass3.png)
+![Masterpass3](https://images.contentful.com/alneenqid6w5/5XbYGeSd2gy4QEaIiMeqQ0/a20d27e9aa18af9a95767fb604e82d7c/Masterpass3.png)
 
 ## Preview
 
@@ -58,7 +58,7 @@ Além disso, a Extension Store disponibiliza um ambiete de preview do Masterpass
 
 Esse ambiente funciona como um rascunho. Nenhuma alteração feita nele afeta sua loja em produção.
 
-![Masterpass4](//images.contentful.com/alneenqid6w5/7Ki5CoHPvUusGuU4UEE2U4/7d8d02434118b7c3b6c295edc9efbb18/Masterpass4.gif)
+![Masterpass4](https://images.contentful.com/alneenqid6w5/7Ki5CoHPvUusGuU4UEE2U4/7d8d02434118b7c3b6c295edc9efbb18/Masterpass4.gif)
 
 ## Publicação
 
@@ -66,4 +66,4 @@ Para mover o Masterpass para o ambiente em produção (onde seus clientes podem
 
 Para isso, basta clicar no botão **Publicar** da top bar.
 
-![Extension Store 3 - Publishing](//images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
+![Extension Store 3 - Publishing](https://images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
diff --git a/docs/tutorials/pt/how-to-install-the-taxhub.md b/docs/tutorials/pt/how-to-install-the-taxhub.md
index 7d5976857..9d273bd42 100644
--- a/docs/tutorials/pt/how-to-install-the-taxhub.md
+++ b/docs/tutorials/pt/how-to-install-the-taxhub.md
@@ -25,4 +25,4 @@ Para instalar o sistema de impostos TaxHub, siga os passos abaixo:
 6.	Na mesma tela, instale seu App desenvolvido em node.js compactado em formato .zip (o nome do arquivo deve ser jurisdiction.zip);
 7.	O sistema salvará o arquivo automaticamente.
  
-![TaxHub Instalation](//images.contentful.com/alneenqid6w5/7LfwQ6CzIIEYqSwmcoUMCG/7508ba6496d5fedb913c85357a8a632e/Instalacion_TaxHub.gif)
+![TaxHub Instalation](https://images.contentful.com/alneenqid6w5/7LfwQ6CzIIEYqSwmcoUMCG/7508ba6496d5fedb913c85357a8a632e/Instalacion_TaxHub.gif)
diff --git a/docs/tutorials/pt/how-to-integrate-vtex-using-zapier.md b/docs/tutorials/pt/how-to-integrate-vtex-using-zapier.md
index 9e026697c..37e916c29 100644
--- a/docs/tutorials/pt/how-to-integrate-vtex-using-zapier.md
+++ b/docs/tutorials/pt/how-to-integrate-vtex-using-zapier.md
@@ -21,15 +21,15 @@ Até o momento, a integração possível de ser realizada é integrar cliente ou
 
 Para realizar a integração, selecione o app VTEX conforme imagem abaixo.
 
-![VTEX-zapier](//images.contentful.com/alneenqid6w5/51ebExxYL62U60EUsSIGGU/bceb8b8ef1dbe35a31e7d9d2dc9a0ade/Screen_Shot_2017-09-19_at_12.50.00_PM.png)
+![VTEX-zapier](https://images.contentful.com/alneenqid6w5/51ebExxYL62U60EUsSIGGU/bceb8b8ef1dbe35a31e7d9d2dc9a0ade/Screen_Shot_2017-09-19_at_12.50.00_PM.png)
 
 Depois, selecione qual das opções de integrção disponíveis você gostaria, conforme imagem abaixo.
 
-![VTEX-Zapier-integration](//images.contentful.com/alneenqid6w5/47a6W7SdmgEA2YYCACiIoE/e9d75043a99783af1afae5c2662ef209/Screen_Shot_2017-09-19_at_12.51.28_PM.png)
+![VTEX-Zapier-integration](https://images.contentful.com/alneenqid6w5/47a6W7SdmgEA2YYCACiIoE/e9d75043a99783af1afae5c2662ef209/Screen_Shot_2017-09-19_at_12.51.28_PM.png)
 
 Na tela seguinte, você precisará dar acesso ao Zapier para que ele se conecte ao seu ambiente VTEX. Para isso, clique em CONNECT AN ACCOUNT e entre com APP Key, APP Token e o Accountname do seu ambiente.
 
-![VTEX-Zapier-connecting-account](//images.contentful.com/alneenqid6w5/5bsgVVWF5mosKCosC424c0/7b0ad9c5141ca6a05818ea46c021b5f8/Screen_Shot_2017-09-19_at_12.52.46_PM.png)
+![VTEX-Zapier-connecting-account](https://images.contentful.com/alneenqid6w5/5bsgVVWF5mosKCosC424c0/7b0ad9c5141ca6a05818ea46c021b5f8/Screen_Shot_2017-09-19_at_12.52.46_PM.png)
 
 Leia o artigo [ONDE ENCONTRAR A APP KEY TOKEN E APP KEY DA SUA LOJA](http://help.vtex.com/pt/tutorial/onde-encontrar-appkey-e-o-apptoken-de-sua-loja) para mais detalhes.
 
diff --git a/docs/tutorials/pt/how-to-integrate-with-dafiti.md b/docs/tutorials/pt/how-to-integrate-with-dafiti.md
index 132f21db7..6f7cd9c4b 100644
--- a/docs/tutorials/pt/how-to-integrate-with-dafiti.md
+++ b/docs/tutorials/pt/how-to-integrate-with-dafiti.md
@@ -56,11 +56,11 @@ Com essa feature, é possível categorizar corretamente e também criar variaç
 O mapeamento deve ser feito sempre que um produto for enviado pela primeira vez à Dafiti. Isso significa que, já tendo feito o mapeamento uma vez, os produtos que já foram integrados não precisam passar por esse processo novamente. Da mesma forma, produtos novos devem sempre passar pelo mapeamento.
 
 1. De acordo com o __seu país__, faça o download da __Planilha de Mapeamento da Dafiti__ no formato `.xlsx`.
-<br/>&bull; [Brasil](//assets.ctfassets.net/alneenqid6w5/2Vbi7VaYIowaaOYCCucsQq/fa94cd636b38e9810dd6a708c95e26ac/Planilha_de_Mapeamento_da_Dafiti.xlsx)
-<br/>&bull; [Colômbia](//assets.ctfassets.net/alneenqid6w5/4d5y0N09IsKmy4MuAGygqs/0e43349d309fb556179dfac5f2f6c885/Planilha_de_Mapeamento_da_Dafiti_COL.xlsx)
+<br/>&bull; [Brasil](https://assets.ctfassets.net/alneenqid6w5/2Vbi7VaYIowaaOYCCucsQq/fa94cd636b38e9810dd6a708c95e26ac/Planilha_de_Mapeamento_da_Dafiti.xlsx)
+<br/>&bull; [Colômbia](https://assets.ctfassets.net/alneenqid6w5/4d5y0N09IsKmy4MuAGygqs/0e43349d309fb556179dfac5f2f6c885/Planilha_de_Mapeamento_da_Dafiti_COL.xlsx)
 
 2. De acordo com o __seu país__, faça o download da __Planilha de Consulta da Dafiti__ para verificar os valores aceitos de acordo com cada coluna da Planilha de Mapeamento do passo anterior. Essa planilha é __exclusivamente para consulta__.
-<br/>&bull; [Brasil](//assets.ctfassets.net/alneenqid6w5/1gGYn5lo3qSe0iOaoKs0oa/fc1aa02e2761474f0235fcb489f930ff/Planilha_de_Consulta_Dafiti.xlsx)
+<br/>&bull; [Brasil](https://assets.ctfassets.net/alneenqid6w5/1gGYn5lo3qSe0iOaoKs0oa/fc1aa02e2761474f0235fcb489f930ff/Planilha_de_Consulta_Dafiti.xlsx)
 <br/>&bull; [Colômbia](https://s3.amazonaws.com/Marketplace-Integration/SellerCenterIntegration/Colombia.zip)
 
 Siga o passo a passo abaixo, fazendo o de/para na __Planilha de Mapeamento__ entre o que está cadastrado no seu produto na VTEX e os valores especificados na __Planilha de Consulta__ da Dafiti.
diff --git a/docs/tutorials/pt/how-to-manage-subscriptions.md b/docs/tutorials/pt/how-to-manage-subscriptions.md
index 34fab6167..14359a1e8 100644
--- a/docs/tutorials/pt/how-to-manage-subscriptions.md
+++ b/docs/tutorials/pt/how-to-manage-subscriptions.md
@@ -35,7 +35,7 @@ A seção **Assinaturas Únicas** permite:
 - Visualizar um **gráfico dinâmico** com a relação entre assinaturas ativas, canceladas e o total de assinaturas, dentro do período filtrado. Passando o cursor em cima das linhas do gráfico, é possível ver com detalhes a movimentação de assinaturas por dia.
 - **Exportar assinaturas** únicas dentro do período filtrado, pelo botão no canto superior direito da tela.
 
- ![PT Dashboard Assinatura única](//images.ctfassets.net/alneenqid6w5/Dbqw5LPyrXvpT3tElkIXY/89e5fa3647a3e02e5b399e464ce03003/PT_Dashboard_Assinatura___nica.png)
+ ![PT Dashboard Assinatura única](https://images.ctfassets.net/alneenqid6w5/Dbqw5LPyrXvpT3tElkIXY/89e5fa3647a3e02e5b399e464ce03003/PT_Dashboard_Assinatura___nica.png)
 
 ### Pedidos de Assinatura
 
@@ -49,12 +49,12 @@ A seção **Pedidos de Assinatura** permite:
 - Acompanhar o número absoluto e porcentagem correspondente de Pedidos de Assinatura que foram agendados, processados, gerados e completos por período.  
 - Visualizar um gráfico com a porcentagem de pedidos pulados, ciclos com problema e erro de pagamento.  
 
-![PT Dashboard Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/20rYypV5vnYXo42CdCf0ms/3481a1af5bbee24d02b34a39ae03e723/PT_Dashboard_Pedidos_Assinatura.png)
+![PT Dashboard Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/20rYypV5vnYXo42CdCf0ms/3481a1af5bbee24d02b34a39ae03e723/PT_Dashboard_Pedidos_Assinatura.png)
 
 - Ao acessar cada aba do quadro **Pedidos de Assinatura**, é possível visualizar o fluxo e detalhes dos pedidos que foram Pulados, os que apresentaram Ciclos com problema, aqueles que contém um Erro de Pagamento e pedidos Completos.    
 - Além de listar detalhes dos erros que ocorreram durante  o fluxo de pedidos de Assinatura, também é possível realizar a **retentativa manual** dos pedidos com erros. Confira nosso artigo sobre a [Resolução de problemas de pedidos com Assinatura](https://help.vtex.com/pt/tutorial/como-solucionar-pedidos-de-assinatura-com-erros--uLL8AYBGdtAmbbdL5gRCf) para saber mais. 
 
-![PT Log Pedidos Assinatura](//images.ctfassets.net/alneenqid6w5/77DV2slShCKyXY0pKJyTl2/b1e8ed161f7be8bdbf417a68c058a268/PT_Log_Pedidos_Assinatura.png)
+![PT Log Pedidos Assinatura](https://images.ctfassets.net/alneenqid6w5/77DV2slShCKyXY0pKJyTl2/b1e8ed161f7be8bdbf417a68c058a268/PT_Log_Pedidos_Assinatura.png)
 
 ### Assinantes
 
diff --git a/docs/tutorials/pt/how-to-manage-the-kit-stock.md b/docs/tutorials/pt/how-to-manage-the-kit-stock.md
index 918761068..912dc4e2f 100644
--- a/docs/tutorials/pt/how-to-manage-the-kit-stock.md
+++ b/docs/tutorials/pt/how-to-manage-the-kit-stock.md
@@ -27,7 +27,7 @@ O Kit com componentes baseia-se em um produto kit que possui um SKU que é um
 
 Por exemplo, o produto kit de nome Colorido é composto por outros 10 SKUs. Cada um com sua quantidade necessária de 1 item de cada SKU para poder compor o KIT.
 
-![](//images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
+![](https://images.contentful.com/alneenqid6w5/2zwcLWeIX2kwsiQ0GCYm6G/b11fa6ded4ffb56faed9bc0158e980ae/kitcolorido.png)
 
 Se cada componente tiver 1 unidade em estoque, o kit estará em estoque, pois depende do estoque cadastrado em cada um de seus componentes.
 
diff --git a/docs/tutorials/pt/how-to-manually-invoice-an-order.md b/docs/tutorials/pt/how-to-manually-invoice-an-order.md
index bba6ceada..cbb51d914 100644
--- a/docs/tutorials/pt/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/pt/how-to-manually-invoice-an-order.md
@@ -34,7 +34,7 @@ Para enviar a fatura pelo Admin VTEX, realize os seguintes passos:
 2. Busque o pedido pela barra de busca ou [utilizando os filtros](https://help.vtex.com/pt/tutorial/como-filtrar-pedidos--tutorials_192).  
 3. Clique no pedido desejado.     
 4. Na seção **Itens para faturar,** clique no ícone de seta <i class="fas fa-chevron-right"></i> para expandir.
-![Itens faturar](//images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/21fe424a4a5bcb066384dc79f99cf953/Itens_faturar__3_.png)
+![Itens faturar](https://images.ctfassets.net/alneenqid6w5/2wScKr5ZaHShpyntCuN0jy/21fe424a4a5bcb066384dc79f99cf953/Itens_faturar__3_.png)
 5. Clique no botão `Faturar`.   
 6. Clique na opção de faturamento desejada:    
     * **Enviar fatura referenciando itens:** para faturar o pedido referenciando os itens do pacote.    
@@ -64,7 +64,7 @@ Para enviar a fatura pelo Admin VTEX, realize os seguintes passos:
 
 Depois do pedido `Faturado`, confira as notas fiscais inseridas na seção **Fatura**, como apresentado na figura abaixo:
 
-![Fatura](//images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
+![Fatura](https://images.ctfassets.net/alneenqid6w5/24K1rMqn970zgeKxK81f3Z/0dc623d9ea7bff059e5a52f90584b4c4/Fatura__2_.png)
 
 Em casos de envios de [faturas parciais](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe), ao [alterar ou remover itens](https://help.vtex.com/pt/tutorial/how-to-change-order-items--7jekq618QxgbsOxKkXBjE8) de um pedido, o valor total do pedido será atualizado após o faturamento, e corresponde ao que é captado pelo gateway de pagamentos da VTEX.
 
diff --git a/docs/tutorials/pt/how-to-register-a-store-in-vtex-instore.md b/docs/tutorials/pt/how-to-register-a-store-in-vtex-instore.md
index d46ec0c82..669e10075 100644
--- a/docs/tutorials/pt/how-to-register-a-store-in-vtex-instore.md
+++ b/docs/tutorials/pt/how-to-register-a-store-in-vtex-instore.md
@@ -30,7 +30,7 @@ Esse guia auxilia o lojista a configurar sua loja para funcionar melhor com o VT
 
 Assim que o aplicativo é aberto pela primeira vez, ele pergunta qual é o nome da loja que será usada. Conforme a tela abaixo, basta digitar o nome da sua loja para ter as configurações carregadas para o app.
 
-![instore-identificacao-loja](//images.contentful.com/alneenqid6w5/20IMJOo5Kc8Kw4OqicCQyc/8a76ed7d6c16d6b269518d430998ec44/instore-identificacao-loja.png)
+![instore-identificacao-loja](https://images.contentful.com/alneenqid6w5/20IMJOo5Kc8Kw4OqicCQyc/8a76ed7d6c16d6b269518d430998ec44/instore-identificacao-loja.png)
 
 ### Como cadastrar uma loja física
 
@@ -40,14 +40,14 @@ Para gerenciar o seu cadastro de lojas físicas basta acessar o seu Masterdata.
 
 *Se você não encontrar essa aplicação significa que seu ambiente ainda não foi corretamente configurado. Para isso recomendamos o tutorial de configuração de ambiente para uso do inStore.*
 
-![masterdata-home-loja](//images.contentful.com/alneenqid6w5/2uBujqshwgCUkKkeEKWaEU/121417a9d25e998c8bb7a29f85ab1830/masterdata-home-loja.png)
+![masterdata-home-loja](https://images.contentful.com/alneenqid6w5/2uBujqshwgCUkKkeEKWaEU/121417a9d25e998c8bb7a29f85ab1830/masterdata-home-loja.png)
 
 Quando você clicar em *listar*, uma lista de lojas cadastradas irá aparecer como mostra a imagem abaixo. Clique em "Novo" para cadastrar uma nova loja.
 
-![cadastrar-loja](//images.contentful.com/alneenqid6w5/2UxKo2u6CsEagsIYuo8Emy/8c922392c6f0b9373f497575af2cefaf/cadastrar-loja.png)
+![cadastrar-loja](https://images.contentful.com/alneenqid6w5/2UxKo2u6CsEagsIYuo8Emy/8c922392c6f0b9373f497575af2cefaf/cadastrar-loja.png)
 
 Preencha os dados da loja no formulário e depois clique em "salvar".
 
-![cadastrar-loja-formulario](//images.contentful.com/alneenqid6w5/3t3edGHxuo8WoYqkeYmIou/98d23008f916793e6cab618e33905dc2/cadastrar-loja-formulario.png)
+![cadastrar-loja-formulario](https://images.contentful.com/alneenqid6w5/3t3edGHxuo8WoYqkeYmIou/98d23008f916793e6cab618e33905dc2/cadastrar-loja-formulario.png)
 
 Pronto. Sua loja está cadastrada! 😃 Agora você pode continuar cadastrando os vendedores! Veja [aqui](/pt/tutorial/como-cadastrar-vendedores-no-vtex-instore) como fazer.
diff --git a/docs/tutorials/pt/how-to-request-receivables-anticipation.md b/docs/tutorials/pt/how-to-request-receivables-anticipation.md
index 7554f0f51..fd3877a04 100644
--- a/docs/tutorials/pt/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/pt/how-to-request-receivables-anticipation.md
@@ -31,7 +31,7 @@ Agora que você já conferiu o saldo, é importante ter em mente que o valor mí
 
 Por exemplo, caso o seu menor recebível seja de R$10, esse é o valor mínimo que você pode antecipar. Já o valor máximo é informado no próprio Admin - o saldo que você acabou de conferir - na página de “Antecipar recebíveis”. 
 
-![image](//images.ctfassets.net/alneenqid6w5/oWY3RyEekfyjuBEjI27m3/18aba6b309f1acb3f945100927d25ead/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/oWY3RyEekfyjuBEjI27m3/18aba6b309f1acb3f945100927d25ead/image.png)
 
 <div class="alert alert-info">
 <strong>Atenção</strong>: recebíveis em disputa ou previstos para o próximo dia útil não podem ser antecipados.
diff --git a/docs/tutorials/pt/how-to-retrieve-the-access-password.md b/docs/tutorials/pt/how-to-retrieve-the-access-password.md
index 89f040fbd..cfc4f9b69 100644
--- a/docs/tutorials/pt/how-to-retrieve-the-access-password.md
+++ b/docs/tutorials/pt/how-to-retrieve-the-access-password.md
@@ -17,12 +17,12 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 Todas as senhas de acesso são administradas pelo __VTEX ID__. Logo, é preciso acessar a página de login e seguir com o acesso por e-mail e senha para solicitar a criação de uma nova.
 
-1. Em alguma tela de login, clique em **Entrar com e-mail e senha;** ![](//images.contentful.com/alneenqid6w5/5WUhnmS0sE0mGOMKGImII6/b748ec48674b3d18423eb639601343fb/2016-03-10_12_58_32-VTEX_-_lojadosuporte_-_Confirmar_SUA_Identidade_-_forgot_pass.png)
-2. Clique em **Esqueci minha senha;**![](//images.contentful.com/alneenqid6w5/AJukOSefZesKKoiWKmSiQ/0e28a254f9bc3a06931a4fedcf48f5c0/2016-03-10_13_00_20-VTEX_-_lojadosuporte_-_Confirmar_SUA_Identidade_-_forgot_pass_2.png)
-3. Preencha o campo com o seu e-mail;![](//images.contentful.com/alneenqid6w5/2SkvKMVEu426msMWYwsMuo/bbfc1b3ed29e5946a20a81c8435feebe/2016-03-14_14_28_39-Vtex_ID_-_LOGIN_-_esqueci_senha.png)
-4. Preencha o campo com a nova senha e clique em **Cadastrar Nova Senha;**![](//images.contentful.com/alneenqid6w5/3NrJlKPhTag0e40SoMc8KU/16737e86e7900639a6e30a20fb913293/2016-03-14_14_28_56-Vtex_ID_-_LOGIN_-_nova_senha.png)
+1. Em alguma tela de login, clique em **Entrar com e-mail e senha;** ![](https://images.contentful.com/alneenqid6w5/5WUhnmS0sE0mGOMKGImII6/b748ec48674b3d18423eb639601343fb/2016-03-10_12_58_32-VTEX_-_lojadosuporte_-_Confirmar_SUA_Identidade_-_forgot_pass.png)
+2. Clique em **Esqueci minha senha;**![](https://images.contentful.com/alneenqid6w5/AJukOSefZesKKoiWKmSiQ/0e28a254f9bc3a06931a4fedcf48f5c0/2016-03-10_13_00_20-VTEX_-_lojadosuporte_-_Confirmar_SUA_Identidade_-_forgot_pass_2.png)
+3. Preencha o campo com o seu e-mail;![](https://images.contentful.com/alneenqid6w5/2SkvKMVEu426msMWYwsMuo/bbfc1b3ed29e5946a20a81c8435feebe/2016-03-14_14_28_39-Vtex_ID_-_LOGIN_-_esqueci_senha.png)
+4. Preencha o campo com a nova senha e clique em **Cadastrar Nova Senha;**![](https://images.contentful.com/alneenqid6w5/3NrJlKPhTag0e40SoMc8KU/16737e86e7900639a6e30a20fb913293/2016-03-14_14_28_56-Vtex_ID_-_LOGIN_-_nova_senha.png)
 5. Aguarde o código de acesso que será encaminhado por e-mail;
 6. Cole-o no campo solicitado.
-7. Clique em **Alterar Senha**.![](//images.contentful.com/alneenqid6w5/55kQn9GQ5aC44eaIGyOqEw/4607ec0ea43e72b3d6f92048b105b600/2016-03-14_14_31_25-Vtex_ID_-_LOGIN_-_alterando_senha.png)
+7. Clique em **Alterar Senha**.![](https://images.contentful.com/alneenqid6w5/55kQn9GQ5aC44eaIGyOqEw/4607ec0ea43e72b3d6f92048b105b600/2016-03-14_14_31_25-Vtex_ID_-_LOGIN_-_alterando_senha.png)
 
 Pronto! Senha recuperada e acesso liberado.
diff --git a/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md b/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md
index 4ef98772b..14cbaad59 100644
--- a/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md
+++ b/docs/tutorials/pt/how-to-see-orders-closed-with-benefits.md
@@ -20,7 +20,7 @@ Na seção de __Gerenciamento de pedidos__ é possível filtrar os pedidos feito
 Se quiser ver os pedidos que foram fechados tendo uma promoção aplicada, basta seguir os passos abaixo:
 
 1. No menu do admin, clique em __Gerenciamento de pedidos__
-2. Clique no botão de filtro e, dentro da seção __Outros__, clique na opção __Promoções__![promo-filter-pt](//images.ctfassets.net/alneenqid6w5/6LYRvwnDy08eWII6WqUqSC/dcd40f276c57870a2c91c47261d593ea/promo-filter-pt.png)
+2. Clique no botão de filtro e, dentro da seção __Outros__, clique na opção __Promoções__![promo-filter-pt](https://images.ctfassets.net/alneenqid6w5/6LYRvwnDy08eWII6WqUqSC/dcd40f276c57870a2c91c47261d593ea/promo-filter-pt.png)
 3. Selecione a promoção desejada e clique em __Confirme__
 
 Na lista de pedidos, você verá todos os pedidos fechados com essa promoção.
diff --git a/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md b/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
index 865f60095..e6c42053b 100644
--- a/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
+++ b/docs/tutorials/pt/how-to-set-up-a-saleschannel-and-define-a-default-sla-for-recurrent-orders.md
@@ -29,7 +29,7 @@ Basta incluir um atributo com o nome `salesChannel`, conforme ilustrado na rota
 
 A partir de então, os próximos pedidos serão criados com o canal de vendas configurado. Caso não tenha estoque para determinado item neste canal o item será excluido do pedido.   
 
-![posicao.pt](//images.ctfassets.net/alneenqid6w5/7aFEnASwXi9emVUzKJr4pm/8c5f2727be50812817612850e19769cb/posicao.pt.png)
+![posicao.pt](https://images.ctfassets.net/alneenqid6w5/7aFEnASwXi9emVUzKJr4pm/8c5f2727be50812817612850e19769cb/posicao.pt.png)
 
 *Tela onde se encontra o ID do salesChannel*
 
@@ -39,6 +39,6 @@ Basta incluir um atributo com o nome `defaultSLA`, conforme ilustrado na rota d
 
 A partir de então, SLA configurado terá precedência sobre o SLA mais barato para os próximos pedidos que serão criados - sendo que se este possuir uma janela de entrega, será selecionado o primeiro intervalo disponível.
 
-![transportadora.pt](//images.ctfassets.net/alneenqid6w5/1NuCXhjhtIOiYBhtLev1ed/da96b6ce00fdc241f96d81e3184c194f/transportadora.pt.png)
+![transportadora.pt](https://images.ctfassets.net/alneenqid6w5/1NuCXhjhtIOiYBhtLev1ed/da96b6ce00fdc241f96d81e3184c194f/transportadora.pt.png)
 
 *Tela onde se encontra o ID do SLA*
diff --git a/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
index 00e8bbd7a..01c966959 100644
--- a/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
@@ -29,7 +29,7 @@ Neste artigo, explicaremos como associar o recurso Device Fingerprint à afilia
 
 1. Fazer login em http://www.google.com/tagmanager/ para a loja que vamos configurar;
 2. Introduzir o item etiquetas (tags) para configurar o id da sessão do device;
-3. Criar um produto de “HTML Personalizado” como se vê na imagem a seguir:![payU 1](//images.contentful.com/alneenqid6w5/8Kc8zBKQFOmwK6G8ekgMa/2a26fa73a709b116cfdf899d4aee7a23/payU_1.png)
+3. Criar um produto de “HTML Personalizado” como se vê na imagem a seguir:![payU 1](https://images.contentful.com/alneenqid6w5/8Kc8zBKQFOmwK6G8ekgMa/2a26fa73a709b116cfdf899d4aee7a23/payU_1.png)
 4. No campo HTML da configuração, devemos colar o código HTML que chama o código para mandar a informação a PayU:
 
 ```
@@ -75,25 +75,25 @@ Neste artigo, explicaremos como associar o recurso Device Fingerprint à afilia
 <div id="maf"></div>
 ```
 
-![payU 2](//images.contentful.com/alneenqid6w5/4Y60ayHwaQa8ykaUQUmqgq/4a8ad711a25542b1513a75e94725c464/payU_2.png)
+![payU 2](https://images.contentful.com/alneenqid6w5/4Y60ayHwaQa8ykaUQUmqgq/4a8ad711a25542b1513a75e94725c464/payU_2.png)
 
-Depois é preciso realizar a configuração avançada tal como consta na imagem a seguir:![payU 3](//images.contentful.com/alneenqid6w5/2tZRZWcwFWgq6IueAKWQ4o/c64a7a0f2b6dbaad9405e3e55408fb8c/payU_3.png)
+Depois é preciso realizar a configuração avançada tal como consta na imagem a seguir:![payU 3](https://images.contentful.com/alneenqid6w5/2tZRZWcwFWgq6IueAKWQ4o/c64a7a0f2b6dbaad9405e3e55408fb8c/payU_3.png)
 
 Para configurar o evento, siga os passos abaixo:
 
-1. Entre na aba More:![payU 4](//images.contentful.com/alneenqid6w5/1NyDU3X1EseWcCisO04okg/66d6593915e933c22768633a76b4bf92/payU_4.png)
-2. Crie um evento personalizado:![payU 5](//images.contentful.com/alneenqid6w5/Xip98CFhokwoCs22GsUyK/a1c70a419c84d2f4fa2bb0908e0336cd/payU_5.png)
-3. Preencha-o da seguinte maneira:![payU 6](//images.contentful.com/alneenqid6w5/6Rdhtn8quA2IaqKSKeGa0u/0f7a6ed573a438475c477b5c09c331ad/payU_6.png)
-4. Salve o evento e posteriormente salve a etiqueta (tag):![payU 7](//images.contentful.com/alneenqid6w5/2AcLzAcwgMs2SwgkEqEmo2/941c852d50622d570e8fab6534780e33/payU_7.png)
-5. Uma vez salva a etiqueta, é necessário publicá-la:![payU 8](//images.contentful.com/alneenqid6w5/6mpOQSBwzYq844A8uCuWck/125894734e6996cc1521b46c3562a8a7/payU_8.png)
+1. Entre na aba More:![payU 4](https://images.contentful.com/alneenqid6w5/1NyDU3X1EseWcCisO04okg/66d6593915e933c22768633a76b4bf92/payU_4.png)
+2. Crie um evento personalizado:![payU 5](https://images.contentful.com/alneenqid6w5/Xip98CFhokwoCs22GsUyK/a1c70a419c84d2f4fa2bb0908e0336cd/payU_5.png)
+3. Preencha-o da seguinte maneira:![payU 6](https://images.contentful.com/alneenqid6w5/6Rdhtn8quA2IaqKSKeGa0u/0f7a6ed573a438475c477b5c09c331ad/payU_6.png)
+4. Salve o evento e posteriormente salve a etiqueta (tag):![payU 7](https://images.contentful.com/alneenqid6w5/2AcLzAcwgMs2SwgkEqEmo2/941c852d50622d570e8fab6534780e33/payU_7.png)
+5. Uma vez salva a etiqueta, é necessário publicá-la:![payU 8](https://images.contentful.com/alneenqid6w5/6mpOQSBwzYq844A8uCuWck/125894734e6996cc1521b46c3562a8a7/payU_8.png)
 
 Uma vez que já configuramos a etiqueta, temos que salvar o JS chamado a partir do código. Este é salvo dentro do gestor de arquivo da VTEX. Para fazer isso é necessário seguir os seguintes passos:
 
 - Acessando o painel VTEX no menu CMS >> Layout >> Files Manager >> Gerenciamento de arquivo .js >> Add.
 
-![cms js](//images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
+![cms js](https://images.ctfassets.net/alneenqid6w5/175WhPco7ew6OSEUsIG4MU/68772fc79d642781908d19163d787141/cms_js.png)
 
-__Anexo__: [md5.js](//assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
+__Anexo__: [md5.js](https://assets.contentful.com/alneenqid6w5/5PeWM49nPykYYeWI4cOCy4/60c61b5bcf0b4ce92f211f944ab261ad/md5.js)
 
 ### Validação
 
@@ -104,4 +104,4 @@ Para fazer a validação, é necessário entrar na loja, fazer todo o processo d
 3. Faça a busca da palavra MAF
 
 Se o resultado for encontrado, significa que a configuração está correta e o Fingerprint está sendo enviado corretamente, segue um exemplo:
-![payU 9](//images.contentful.com/alneenqid6w5/66H4gkLslyuk0sgOgm8IWC/3d04eca1fdb8ed6a7b4cbf7065a73ec3/payU_9.png)
+![payU 9](https://images.contentful.com/alneenqid6w5/66H4gkLslyuk0sgOgm8IWC/3d04eca1fdb8ed6a7b4cbf7065a73ec3/payU_9.png)
diff --git a/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 469818224..33ef54fc5 100644
--- a/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -77,7 +77,7 @@ Em seguida, é só recolher as informações da Adyen para cadastrar na VTEX. Ai
 
 7. Depois destes passos, seu usuário deverá ter sido criado com sucesso. O número 1 (indicado na imagem em vermelho) é o username. Já o número 2 é a senha (password) que deverá ser inserida no ambiente VTEX.
 
-    ![Adyen - Image 2](//images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
+    ![Adyen - Image 2](https://images.ctfassets.net/alneenqid6w5/7jtKskh7uYiUuMnI6t7UqJ/ea01c037ad5c541a26fdef50b1a0d4fd/image2.png)
 
 8. Envie um e-mail para o suporte da Adyen (suporte@adyen.com) solicitando as habilitações listadas no modelo abaixo:
 
@@ -104,7 +104,7 @@ Se você pretende usar a plataforma da Adyen para fazer análise antifraude com
 
 <ui>5. A configuração deverá parecer conforme abaixo. Não esqueça de clicar em **Save configuration** após concluir as alterações.</ui>
 
-![Adyen - Image 1](//images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
+![Adyen - Image 1](https://images.ctfassets.net/alneenqid6w5/1K5aqITpHU74XYQ5eO7wKc/a29d285086d15dd28a596ab344d72763/image1.png)
 
 ## Configurações na VTEX
 
diff --git a/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
index b9b410d42..1061ba7c6 100644
--- a/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -31,7 +31,7 @@ Para inserir os scripts que a Braspag/CyberSource exige para o device fingerprin
 
 ## Criação de variáveis (macros) e acionador
 
-- Crie a variável de nome `trasactionPaymentId`, tipo **Variável da camada de dados**, lendo a variável `transactionPayment.id` do datalayer.![](//images.contentful.com/alneenqid6w5/2iGloCXR32IMAyWAKe8qWy/cf1108ad17e944adc63f189e67cfa93d/gtm-cybersource-variavel1-1.png)
+- Crie a variável de nome `trasactionPaymentId`, tipo **Variável da camada de dados**, lendo a variável `transactionPayment.id` do datalayer.![](https://images.contentful.com/alneenqid6w5/2iGloCXR32IMAyWAKe8qWy/cf1108ad17e944adc63f189e67cfa93d/gtm-cybersource-variavel1-1.png)
 - Crie a variável de nome `cs_sessionId`, com o tipo **JavaScript personalizado** e o seguinte código:
 
 ```
@@ -41,15 +41,15 @@ function() {
   }
 ```
 
-![](//images.contentful.com/alneenqid6w5/2qhm00B2d2guyeqIU4gCCc/15c42813f5a0ad04937da7aebcc2e5b2/gtm-cybersource-variavel2-javascript-3.png)
+![](https://images.contentful.com/alneenqid6w5/2qhm00B2d2guyeqIU4gCCc/15c42813f5a0ad04937da7aebcc2e5b2/gtm-cybersource-variavel2-javascript-3.png)
 
 - Crie as variáveis `cs_orgId` e `cs_merchantId` com o tipo **Permanente**. O valor dessas duas variáveis deverá ser preenchido com o conteúdo fornecido pela Braspag. Fique atento que esse valor também configura no conector da Braspag como **FingerPrint_MerchantId**.
 
-![gtm-cybersource-variavel3-permanente](//images.contentful.com/alneenqid6w5/5EFSTIM6TCKUE4GEOA66kc/8c2f37cdd8cc94571f6f2ac72ec1d35b/gtm-cybersource-variavel3-permanente.png)
+![gtm-cybersource-variavel3-permanente](https://images.contentful.com/alneenqid6w5/5EFSTIM6TCKUE4GEOA66kc/8c2f37cdd8cc94571f6f2ac72ec1d35b/gtm-cybersource-variavel3-permanente.png)
 
 - Crie ou edite um acionador para a tela de OrderPlaced (tela de compra finalizada com sucesso), para que seja compatível com o evento de tipo **Evento personalizado** e de valor **orderPlaced**.
 
-![gtm-cybersource-acionador-orderplaced](//images.contentful.com/alneenqid6w5/51IPOyaAjmowkEQ24sYyw4/7b11cddfb71c200dd1cd2c85149c7726/gtm-cybersource-acionador-orderplaced.png)
+![gtm-cybersource-acionador-orderplaced](https://images.contentful.com/alneenqid6w5/51IPOyaAjmowkEQ24sYyw4/7b11cddfb71c200dd1cd2c85149c7726/gtm-cybersource-acionador-orderplaced.png)
 
 ## Criação da tag para Braspag
 
@@ -68,6 +68,6 @@ Preencha com o seguinte código HTML:
 <script src="https://h.online-metrix.net/fp/check.js?org_id={{cs_orgId}}&amp;session_id={{cs_merchantId}}{{cs_sessionId}}" type="text/javascript"></script>
 ```
 
-![braspag fingerprint](//images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/c023534e5c43d1f5fd06ebf9e13dcac6/image.png)
+![braspag fingerprint](https://images.ctfassets.net/alneenqid6w5/JTnL01Ko0DMc7Pu8Bp1CQ/c023534e5c43d1f5fd06ebf9e13dcac6/image.png)
 
 Por fim, publique as alterações.
diff --git a/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
index 544e273e0..ccf676ca2 100644
--- a/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -31,7 +31,7 @@ O consumidor realiza o agendamento por meio de um formulário preparado pela Ind
 
 O fluxo de agendamento percorrido pelo cliente se inicia na escolha da loja física onde ele deseja ser atendido. Na imagem abaixo, vemos apenas uma loja cadastrada. Mas você pode cadastrar quantas lojas físicas desejar.
 
-![indeva1](//images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
+![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
 <div class="alert alert-info">
 É possível também fornecer ao cliente um link que conduz diretamente ao formulário de uma loja física específica. Basta adicionar o ID da loja ao final da URL. Dessa forma, o vendedor pode compartilhar o link de sua loja – por exemplo, por meio de um QR Code ou nas mídias sociais.
@@ -48,7 +48,7 @@ Ao clicar na loja desejada, o cliente é levado ao formulário. Ali, ele encontr
 
 Por fim, basta o cliente clicar em Agendar horário. Com isso, essa visita entrará na fila de agendamentos mostrados pelo aplicativo dos vendedores.
 
-![indeva2](//images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
+![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
 <div class=”alert alert-warning”>
 Por enquanto, a confirmação do agendamento deve ser feita manualmente pela loja. O cliente não receberá nenhuma mensagem automática.
@@ -58,13 +58,13 @@ Por enquanto, a confirmação do agendamento deve ser feita manualmente pela loj
 
 A app do Indeva Store organiza a fila de agendamentos realizados para cada loja física. Ele pode ser usado por vendedores ou gerentes para controle tanto dos próximos agendamentos quanto para visualização do histórico de visitas já atendidas.
 
-![indeva3](//images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
+![indeva3](https://images.ctfassets.net/alneenqid6w5/71ZOQFSA8uKJKMdjrfsaX1/ae2b7836ab6e76efe752cfd3cdca0dd4/indeva3.png)
 
 Ao clicar em um agendamento específico, o vendedor tem acesso aos detalhes desse agendamento: data e horário da visita, nome do cliente, mensagem enviada por ele, quantidade de pessoas e o número de telefone do cliente.
 
 Se quiser entrar em contato com o cliente a partir dessa tela, o vendedor pode clicar no botão Abrir Whatsapp. Ele será levado diretamente para uma conversa com aquele cliente específico no aplicativo de mensagens.
 
-![indeva4](//images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
+![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
 <div class=”alert alert-info”>
 O aplicativo pode ser instalado em diversos dispositivos da mesma loja, mas recomendamos que sua equipe use um aplicativo por loja, e não por vendedor.
@@ -115,7 +115,7 @@ O app para os vendedores e gerentes da loja está disponível tanto para Android
 
 Após instalar e abrir o aplicativo, o vendedor deverá informar o token de 10 dígitos da loja para sincronizar o dispositivo e fazer o login.
 
-![indeva5](//images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
+![indeva5](https://images.ctfassets.net/alneenqid6w5/8K9WlmZVH3omGfWus5jke/ce2eb6f9b3b9ba58ba119d285184aca5/indeva5.png)
 
 Para receber o token, entre em contato com o time da Indeva pelos canais de suporte:
 - __Telefone__: (21)3609-2830
diff --git a/docs/tutorials/pt/how-to-set-up-the-zoom.md b/docs/tutorials/pt/how-to-set-up-the-zoom.md
index de3868631..33873e074 100644
--- a/docs/tutorials/pt/how-to-set-up-the-zoom.md
+++ b/docs/tutorials/pt/how-to-set-up-the-zoom.md
@@ -22,7 +22,7 @@ _Se você já possui essa configuração ativa mas está com alguns problemas ve
 
 Abaixo um passo-a-passo de como configurar e implementar esta funcionalidade.
 
-![zoom-configurações](//images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
+![zoom-configurações](https://images.ctfassets.net/alneenqid6w5/2syaIncF2UeOw0YgOcOSIq/02d931bb81ef413ad248f21e518fbd24/zoom.png)
 
 ## Configurando o CSS
 
@@ -36,7 +36,7 @@ Abaixo reproduzimos um trecho de CSS que você pode utilizar como ponto de parti
 
 Em seguida, vamos enviar o arquivo CSS salvo para o servidor. Para isso, acesse no menu **CMS** > Acesse **Layout** > Entre na pasta **CMS** > Entre em **Files Manager** > Entre em **.css** > Na janela que se abrirá à direita, clique no botão **Add**.
 
-![add-cms-.css ](//images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
+![add-cms-.css ](https://images.ctfassets.net/alneenqid6w5/ZXAryRqp4AAosaKM2qmQa/40058a1db81bde2207c60158c682b667/add_.css.png)
 
 Em seguida, localize o arquivo CSS salvo acima e envie-o para o servidor clicando no botão **Localizar** e em seguida no botão **Salvar arquivo**; dessa forma, seu arquivo aparecerá listado como mostra a imagem acima. 
 
@@ -54,4 +54,4 @@ Agora basta inserir `zoom="on"` na tag do produto, conforme abaixo:
 É necessário configurar o tamanho padrão da imagem de zoom. Você pode definir isso em **CMS** > **Configurações** > **Tipos de Arquivos**.
 Por padrão, esse tipo de imagem de zoom vem configurada com 1000×1000 pixels.
 
-![zoom-tiposdearquivo pt](//images.ctfassets.net/alneenqid6w5/3kUqg5mLCUkewseUmA0yK2/cb469406f4cec605ed3e05d9ec487c23/zoom_tipos_de_arquivo.png)
+![zoom-tiposdearquivo pt](https://images.ctfassets.net/alneenqid6w5/3kUqg5mLCUkewseUmA0yK2/cb469406f4cec605ed3e05d9ec487c23/zoom_tipos_de_arquivo.png)
diff --git a/docs/tutorials/pt/how-to-set-up-visa-debit.md b/docs/tutorials/pt/how-to-set-up-visa-debit.md
index 39c51b1f4..540612375 100644
--- a/docs/tutorials/pt/how-to-set-up-visa-debit.md
+++ b/docs/tutorials/pt/how-to-set-up-visa-debit.md
@@ -22,17 +22,17 @@ Para realizar a configuração o pagamento por Visa Débito em sua loja, no Admi
 Em primeiro lugar, devemos criar uma condição de pagamentos para habilitar o Visa Débito no Checkout.
 Para isso, em **Configurações** acesse o menu de opções de **Condições de pagamento**:
 
-![visa debito](//images.ctfassets.net/alneenqid6w5/4oOYYq29TmER7mOldlakl2/ba1eefbd08406217ce0567d3dc18d21f/visa_debito.png)
+![visa debito](https://images.ctfassets.net/alneenqid6w5/4oOYYq29TmER7mOldlakl2/ba1eefbd08406217ce0567d3dc18d21f/visa_debito.png)
 
 Selecione Visa Electron para criar a condição de pagamento:
 
-![Visa Debito 3](//images.contentful.com/alneenqid6w5/7iNwRHWjewEqqYAas0kGw/ae76ec6f4a0361dbb2c8e0b41db85cd2/VD3.png)
+![Visa Debito 3](https://images.contentful.com/alneenqid6w5/7iNwRHWjewEqqYAas0kGw/ae76ec6f4a0361dbb2c8e0b41db85cd2/VD3.png)
 
 ### Configurar condição de pagamento
 
 Deve-se selecionar a afiliação desejada para transacionar os pagamentos, ativar a condição de pagamentos e finalmente salvar as mudanças:
 
-![visa debito.2](//images.ctfassets.net/alneenqid6w5/3IC7m6dgtk2t7jjVKhQTkJ/330c8f3b81c16501f52a619874c84349/visa_debito.2.png)
+![visa debito.2](https://images.ctfassets.net/alneenqid6w5/3IC7m6dgtk2t7jjVKhQTkJ/330c8f3b81c16501f52a619874c84349/visa_debito.2.png)
 
 ### Visualizando os cartões de débito no Checkout
 
diff --git a/docs/tutorials/pt/how-to-use-conditions-builder-app.md b/docs/tutorials/pt/how-to-use-conditions-builder-app.md
index 68f97ef1c..382042549 100644
--- a/docs/tutorials/pt/how-to-use-conditions-builder-app.md
+++ b/docs/tutorials/pt/how-to-use-conditions-builder-app.md
@@ -36,12 +36,12 @@ Depois de instalar, você pode acessá-lo da barra lateral (seção de apps inst
 4. (Opcional) Escreva uma pequena descrição para sua condição. Essa descrição é apenas para controle interno, não será visível aos seus clientes.
 5. Clique em "Começar a construir".
 
-![criarCondicao](//images.ctfassets.net/alneenqid6w5/628KQZeFhY2GsQsgcEMmIm/2610dde91708bfbd304ea52458be6137/criarCondicao.gif)  
+![criarCondicao](https://images.ctfassets.net/alneenqid6w5/628KQZeFhY2GsQsgcEMmIm/2610dde91708bfbd304ea52458be6137/criarCondicao.gif)  
 
 
 Depois de apertar o botão "Começar a construir", você verá um editor e uma lista de blocos no lado esquerda da tela. Agora você só precisa arrastar os blocos para o editor e conectá-los, criando assim sua lógica. 
 
-![criando](//images.ctfassets.net/alneenqid6w5/3wvd23x3WUK4IcSK6MMemU/3cffed6cac4c6398ee2c03fcd95973ba/criando.gif)
+![criando](https://images.ctfassets.net/alneenqid6w5/3wvd23x3WUK4IcSK6MMemU/3cffed6cac4c6398ee2c03fcd95973ba/criando.gif)
 
 ### Editando uma condição
 
@@ -54,4 +54,4 @@ Caso você queira que uma condição não seja mais aplicada, você pode simples
 - Quando o botão ao lado da condição for azul -> está habilitada
 - Quando o botão ao lado da condição for cinza -> está desabilitada
 
-![enableDisable](//images.ctfassets.net/alneenqid6w5/4MqAUcKUfmeakkG2KMyeyc/5874f8d693a49aebebb6b51de37194ae/enableDisable.gif)
+![enableDisable](https://images.ctfassets.net/alneenqid6w5/4MqAUcKUfmeakkG2KMyeyc/5874f8d693a49aebebb6b51de37194ae/enableDisable.gif)
diff --git a/docs/tutorials/pt/how-to-use-the-index-report.md b/docs/tutorials/pt/how-to-use-the-index-report.md
index ba023ab71..28c806eb8 100644
--- a/docs/tutorials/pt/how-to-use-the-index-report.md
+++ b/docs/tutorials/pt/how-to-use-the-index-report.md
@@ -17,7 +17,7 @@ subcategory: 5yDQmr18K4GgQAeGwq8USa
 
 O **Relatório de Indexação** é o relatório que indica o status de indexação de todos os produtos da loja. 
 
-![RelatorioIndexação](//images.contentful.com/alneenqid6w5/6Y212qGxIAU4KWuWw8Uou2/306e536e7b5196abf04513915550a9f6/RelatorioIndexa_C3_A7_C3_A3o.png)
+![RelatorioIndexação](https://images.contentful.com/alneenqid6w5/6Y212qGxIAU4KWuWw8Uou2/306e536e7b5196abf04513915550a9f6/RelatorioIndexa_C3_A7_C3_A3o.png)
 
 <div class="alert alert-info">
 <strong>Nota:</strong> Para mais informações, acesse <a href="http://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao">Entendendo o funcionamento da indexação.</a>
diff --git a/docs/tutorials/pt/how-to-use-the-search-result-control.md b/docs/tutorials/pt/how-to-use-the-search-result-control.md
index aeedad396..dfa97bbd6 100644
--- a/docs/tutorials/pt/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/pt/how-to-use-the-search-result-control.md
@@ -46,14 +46,14 @@ Veja abaixo a lista de todos os atributos do controle Search Result:
 
 O código renderizado pelo controle Search Result tem, por padrão, a seguinte estrutura:
 
-![searchResult1](//images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
+![searchResult1](https://images.ctfassets.net/alneenqid6w5/3BbGHkrGZi8KK4U82IAq6w/123f66c2caa97aca4fc60018cf295aca/searchResult1.jpg) 
 
 E os elementos correspondentes que são renderizados pelo controle em sua versão não customizada seguem o padrão abaixo:
 
-![searchResult2](//images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
+![searchResult2](https://images.ctfassets.net/alneenqid6w5/4R3iwa4QXCW4KUo0sGUuua/4bce4569fadb45665bba25f77d25840d/searchResult2.jpg) 
 
-![searchResult3](//images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
+![searchResult3](https://images.ctfassets.net/alneenqid6w5/1gTj36n2VsOWUuuQ4iWoI0/a873543da266c31f8bc8cc85cf6707ae/searchResult3.jpg) 
 
-![searchResult4](//images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
+![searchResult4](https://images.ctfassets.net/alneenqid6w5/4iv9Pq4zRu62EAei6EOgAC/84b0de1953a6db756aa78a6196478e20/searchResult4.jpg) 
 
-![searchResult5](//images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
+![searchResult5](https://images.ctfassets.net/alneenqid6w5/5uupcekvIIkmmQoCImAEwm/815fedbba0acb340cd895efb9980ab14/searchResult5.jpg)
diff --git a/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md b/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md
index a53dbb065..c66bf67b6 100644
--- a/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md
+++ b/docs/tutorials/pt/how-to-use-the-shareable-cart-app.md
@@ -17,7 +17,7 @@ subcategory:
 
 O app [Carrinho Compartilhável](https://apps.vtex.com/vtex-social-selling/p) permite que vendedores selecionem produtos para seus clientes e compartilhem o carrinho preenchido por canais como WhatsApp, Facebook Messenger e e-mail (Social Selling).
 
-![Shareable Cart Demo](//images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
+![Shareable Cart Demo](https://images.ctfassets.net/alneenqid6w5/sf2zbYOG7janUXWbgkajd/93aa5f4ea002c5877a9620722af67890/Jy98kJ.gif)
 
 Este artigo explica todos os passos para usar esta funcionalidade: ativar app, escolher os produtos, adicionar o código do vendedor, compartilhar e criar um novo carrinho. Antes de começar, é preciso [ativar esta funcionalidade na sua loja](https://help.vtex.com/pt/tutorial/como-ativar-o-app-carrinho-compartilhavel--1lS3fQdXpOoC0BTeVhydfg).
 
@@ -31,25 +31,25 @@ Onde `{Endereço web da sua loja}` deve ser substituído pelo endereço do site
 
 A interface de compartilhamento de carrinho deve aparecer na tela, incluindo alguns dos ícones abaixo. As opções disponíveis dependem da configuração escolhida pela loja.
 
-![Screen Shot 2020-05-03 at 17.37.11](//images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
+![Screen Shot 2020-05-03 at 17.37.11](https://images.ctfassets.net/alneenqid6w5/167aYS1QT597gtpD7Zfxtu/834514c7425ede7f3a1f8c0db2480b63/Screen_Shot_2020-05-03_at_17.37.11.png)
 
 ## Escolher produtos
 
 Uma vez ativado o app, não é necessário fazer login para iniciar a navegação e selecionar os produtos. Basta navegar na loja normalmente, como se estivesse fazendo uma compra online. Depois de escolher todos produtos para o cliente, basta abrir o carrinho e seguir os próximos passos na interface de compartilhamento de carrinho.
 
-![shareable-cart-chooseproducts](//images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
+![shareable-cart-chooseproducts](https://images.ctfassets.net/alneenqid6w5/5KF6iTOUM6fqoAnwUO6JD1/e20cb733489567945c57599681e68185/shareable-cart-chooseproducts.gif)
 
 ## Adicionar código de vendedor
 
 Após selecionar os produtos, clique no botão <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3N22EOkpKDTgr32mkN9ei5/6cb4627d028e3ffe0aa29c607ce6c90b/image10.png" /> para adicionar o seu código de vendedor. Siga as instruções da loja para o preenchimento, já que cada loja pode escolher formas diferentes para identificar vendedores e descontos.
 
-![shareable-cart-addcode](//images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
+![shareable-cart-addcode](https://images.ctfassets.net/alneenqid6w5/1ORhQKfIfTsXZhPR40d3FQ/f751f96f3800e2c7f7ec91bae80257b0/shareable-cart-addcode.gif)
 
 ## Preencher dados pessoais e endereço (opcional)
 
 Conforme a preferência do cliente e as orientações da sua loja, você poderá preencher os dados pessoais e de entrega do pedido. __Já os dados de pagamentos devem ser sempre preenchidos pelo cliente.__
 
-![shareable-cart-customerdetails](//images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
+![shareable-cart-customerdetails](https://images.ctfassets.net/alneenqid6w5/4JY5ktzka93UkWov5cMnb6/8d2cccb0e7189da93ed6bf98c37d7752/shareable-cart-customerdetails.gif)
 
 <div class="alert alert-danger" role="alert"><strong>Nunca peça dados de pagamento ao enviar o carrinho.</strong> Mesmo que o cliente insista, informe que é para a segurança de todos que o pagamento seja informado por ele.</div>
 
@@ -57,7 +57,7 @@ Conforme a preferência do cliente e as orientações da sua loja, você poderá
 
 Depois de adicionar seu código de vendedor, clique no botão correspondente à opção desejada. Detalhamos abaixo os passos para cada tipo de compartilhamento.
 
-![shareable-cart-sharecart](//images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
+![shareable-cart-sharecart](https://images.ctfassets.net/alneenqid6w5/2lFmGUNGO1aECbPwa7w5Fn/d50c6ab066dbfad0b9622f3c2509dcb6/shareable-cart-sharecart.gif)
 
 ### WhatsApp
 
diff --git a/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md b/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md
index 216a927f3..ea5ea4b91 100644
--- a/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md
+++ b/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md
@@ -29,7 +29,7 @@ __Caso um SKU com determinada especificação não esteja disponível em estoque
 
 No exemplo abaixo, os tamanhos P e G do produto não estão disponíveis.
 
-![classeIndisponivel](//images.contentful.com/alneenqid6w5/6dTacclHvqeaMwws8kqU8K/2d0d79d95dc521626eb1ba5c1c056da2/classeIndisponivel.png)
+![classeIndisponivel](https://images.contentful.com/alneenqid6w5/6dTacclHvqeaMwws8kqU8K/2d0d79d95dc521626eb1ba5c1c056da2/classeIndisponivel.png)
 
 ## Incluir a classe de produto indisponível
 
diff --git a/docs/tutorials/pt/how-to-use-vtex-predictor-bot.md b/docs/tutorials/pt/how-to-use-vtex-predictor-bot.md
index 42d438f69..9dd60e3b8 100644
--- a/docs/tutorials/pt/how-to-use-vtex-predictor-bot.md
+++ b/docs/tutorials/pt/how-to-use-vtex-predictor-bot.md
@@ -28,18 +28,18 @@ Ao combinar dados de diferentes fontes, ele é capaz de prever como suas vendas
 ## Como o Predictor Bot funciona
 
 Começamos por uma ideia geral de como está o desempenho da sua loja.
-![sales data](//images.contentful.com/alneenqid6w5/4LVuTVHevYw6eaykMwQY4M/8b9a06a17479a1595c05d879071ad320/sales_data.png)
+![sales data](https://images.contentful.com/alneenqid6w5/4LVuTVHevYw6eaykMwQY4M/8b9a06a17479a1595c05d879071ad320/sales_data.png)
 
 Conforme ilustrado na imagem acima, cada loja típica tem um padrão - mesmo em uma base diária, ou por hora. Devemos identificar esse padrão para iniciar qualquer análise.
 
 Mas nem tudo é flores. Muitas vezes vemos algo mais ou menos assim:
-![crazy sales data](//images.contentful.com/alneenqid6w5/K7vwyviY4S6Q4CwSOSsaW/a644e1f182e82da152d69c661f3f44b7/crazy_sales_data.png)
+![crazy sales data](https://images.contentful.com/alneenqid6w5/K7vwyviY4S6Q4CwSOSsaW/a644e1f182e82da152d69c661f3f44b7/crazy_sales_data.png)
 
 Neste caso, devemos remover discrepâncias e comparar novos conjuntos de dados contra outros períodos. Continuamos iterando assim até que nosso algoritmo saiba que temos um conjunto seguro de dados. Nesse ponto, podemos analisar e __identificar os eventos que fogem ao padrão__.
 
 Ao final, nosso gráfico previsto é algo como a curva abaixo. A linha azul é o resultado do nosso modelo. Esta curva está contida dentro de um intervalo de confiança (área azul).
 
-![unnamed](//images.contentful.com/alneenqid6w5/4dyeHM6ycoSGs0kgMUSQqo/56ff4ea1a3478dfea3fc8c4d9860280c/unnamed.png)
+![unnamed](https://images.contentful.com/alneenqid6w5/4dyeHM6ycoSGs0kgMUSQqo/56ff4ea1a3478dfea3fc8c4d9860280c/unnamed.png)
 
 Sempre que encontramos algo, nós lhe informamos! Se o seu desempenho atual se afastar do nosso modelo mas estiver dentro dos intervalos, enviamos apenas um __ALERTA__. Se for além, você recebe um aviso __CRÍTICO__.
 
@@ -47,7 +47,7 @@ Sempre que encontramos algo, nós lhe informamos! Se o seu desempenho atual se a
 
 Podemos mandar três tipos de e-mails. Aqui está um exemplo:
 
-![Vtex Predictor Bot template](//images.contentful.com/alneenqid6w5/1Ft1I0ibI4g86okS4IYKy0/293929eb488252dabe8cdadee29c86e7/Vtex_Predictor_Bot_template.png)
+![Vtex Predictor Bot template](https://images.contentful.com/alneenqid6w5/1Ft1I0ibI4g86okS4IYKy0/293929eb488252dabe8cdadee29c86e7/Vtex_Predictor_Bot_template.png)
 
 Como você pode ver, este é um exemplo de notificação enviada quando a anomalia não existe mais e as vendas da sua loja voltaram ao normal.
 
diff --git a/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md b/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md
index dbfe0f080..9e7289e38 100644
--- a/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md
+++ b/docs/tutorials/pt/how-to-view-taxes-information-in-taxhub.md
@@ -17,6 +17,6 @@ subcategory:
 
 Quando um produto é incluído no carrinho, serão destacados os valores cobrados dos impostos configurados anteriormente. Para o cálculo de imposto, é necessário o preenchimento dos dados do cliente e dos dados de entrega de compra. Na página de finalização da compra, os impostos estarão sempre destacados. O encarregado da loja também terá a informação destacada no Gerenciamento de Pedidos.
 
-![Screenshot 1](//images.ctfassets.net/alneenqid6w5/h1utOUorGESswSg6QcSGu/1e1084773c4524bcefd6bb357443eb3e/Screenshot_1.png)
+![Screenshot 1](https://images.ctfassets.net/alneenqid6w5/h1utOUorGESswSg6QcSGu/1e1084773c4524bcefd6bb357443eb3e/Screenshot_1.png)
 
 [Continue com o TaxHub lendo sobre sua estrutura de API REST](/pt/tutorial/como-e-a-estrutura-api-rest-do-taxhub)
diff --git a/docs/tutorials/pt/how-to-view-the-orders-details.md b/docs/tutorials/pt/how-to-view-the-orders-details.md
index abe9e3b96..b95500cf0 100644
--- a/docs/tutorials/pt/how-to-view-the-orders-details.md
+++ b/docs/tutorials/pt/how-to-view-the-orders-details.md
@@ -30,7 +30,7 @@ No lado direito há uma caixa que contém o valor total do pedido, os dados do c
 
 O ID é referente à transação no gateway da plataforma VTEX, e é inclusive parte da URL.
 
-![pci](//images.contentful.com/alneenqid6w5/65oy7tCoAoCMgGIi4CYau6/69e8caa34812349a09014157d0d27e33/pci.png)
+![pci](https://images.contentful.com/alneenqid6w5/65oy7tCoAoCMgGIi4CYau6/69e8caa34812349a09014157d0d27e33/pci.png)
 
 Acima dessa caixa, há um link para o pedido no módulo **Pedidos**.
 
@@ -52,19 +52,19 @@ Seguem abaixo exemplos de como visualizar os cenários mais comuns que necessita
 
 ### Evento de aprovação
 
-![](//images.contentful.com/alneenqid6w5/2P90PVqJl6qOWGkc6icoss/fba44bb1bd12c7e42d1658d91d6edd73/2.jpg)
+![](https://images.contentful.com/alneenqid6w5/2P90PVqJl6qOWGkc6icoss/fba44bb1bd12c7e42d1658d91d6edd73/2.jpg)
 
 Nesse exemplo, vemos a aprovação de um pagamento. Ou seja, vemos que a operadora autorizou o fechamento da compra com estes dados de pagamento.
 
 ### Evento de aprovação de antifraude
 
-![](//images.contentful.com/alneenqid6w5/2kCKR8mx3KUGW60cSs0wmo/d4cb6c1271069fd4f85e8ccb0813ef27/3.jpg)
+![](https://images.contentful.com/alneenqid6w5/2kCKR8mx3KUGW60cSs0wmo/d4cb6c1271069fd4f85e8ccb0813ef27/3.jpg)
 
 Neste exemplo, vemos o retorno do antifraude recebendo a transação e posteriormente o retorno com a análise de risco realizada, aprovando a mesma. Em casos de reprovação, o log exibirá a informação `RiskRejected`.
 
 ### Evento de fatura
 
-![](//images.contentful.com/alneenqid6w5/5v6fzCwSCkeqO8g24kSkqS/5e8d39795949ce428153a0e18bcdf558/4.jpg)
+![](https://images.contentful.com/alneenqid6w5/5v6fzCwSCkeqO8g24kSkqS/5e8d39795949ce428153a0e18bcdf558/4.jpg)
 
 Neste exemplo, a operadora retorna o evento de liquidação do valor, ou seja, informa que realizou a fatura do pedido.
 
@@ -72,7 +72,7 @@ Neste exemplo, a operadora retorna o evento de liquidação do valor, ou seja, i
 
 O exemplo abaixo mostra uma transação de cartão de crédito que gerou erro ao ser processada pela adquirente Redecard. Os afiliados costumam retornar um código (`ConnectorCode`) junto a uma mensagem. Para encontrar informações detalhadas do erro, recomendamos consultar a documentação do adquirente. Por meio de uma rápida busca no Google é possível encontrar a lista de códigos e mensagens de cada afiliado.
 
-![2017-01-26 20_23_37-634883 _ VTEX PCI Gateway](//images.contentful.com/alneenqid6w5/4CR2xqOZMkEEKoq0Q4008W/0088088b1a2167314ee31ab1078435b6/2017-01-26-20_23_37-634883-_-VTEX-PCI-Gateway.png)
+![2017-01-26 20_23_37-634883 _ VTEX PCI Gateway](https://images.contentful.com/alneenqid6w5/4CR2xqOZMkEEKoq0Q4008W/0088088b1a2167314ee31ab1078435b6/2017-01-26-20_23_37-634883-_-VTEX-PCI-Gateway.png)
 
 ## Liquidação automática agendada
 
@@ -82,7 +82,7 @@ Caso o pedido seja cancelado, o estorno ocorrerá normalmente.
 
 Veja como visualizar a data do agendamento da liquidação automática:
 
-![](//images.contentful.com/alneenqid6w5/3cUrT8OgtiiiKGiaySoO4Q/5abbea075f47b3c3334954a3fa53f006/5.jpg)
+![](https://images.contentful.com/alneenqid6w5/3cUrT8OgtiiiKGiaySoO4Q/5abbea075f47b3c3334954a3fa53f006/5.jpg)
 
 ## TID de pagamento
 
@@ -92,22 +92,22 @@ Essa informação é importante sempre que for necessário confirmar algo com a
 
 Para encontrar esse código na transação, veja a ilustração abaixo.
 
-![](//images.contentful.com/alneenqid6w5/4UGw2BvqvewicmA4sYq64a/488e64d672529ed30b56e364efd4e89f/6.jpg)
+![](https://images.contentful.com/alneenqid6w5/4UGw2BvqvewicmA4sYq64a/488e64d672529ed30b56e364efd4e89f/6.jpg)
 
 ## IP do cliente
 
 O IP do cliente é coletado no momento da compra e pode ser visto no campo superior da tela da transação, conforme imagem abaixo.
 
-![](//images.contentful.com/alneenqid6w5/3luCOyDKZ2a22y2q26S6E/1b77e158a83d51f43a4e9bb74981a512/7.jpg)
+![](https://images.contentful.com/alneenqid6w5/3luCOyDKZ2a22y2q26S6E/1b77e158a83d51f43a4e9bb74981a512/7.jpg)
 
 ## ID do antifraude
 
 É o ID da transação para o antifraude. Para buscas no antifraude, deve-se consultar esse valor no PCI Gateway.
 
-![IDAntifraude](//images.contentful.com/alneenqid6w5/6KrRXQocKWy6kQosaOgiyU/77e8ae4f52c586280a17a08373675301/IDAntifraude-1.gif)
+![IDAntifraude](https://images.contentful.com/alneenqid6w5/6KrRXQocKWy6kQosaOgiyU/77e8ae4f52c586280a17a08373675301/IDAntifraude-1.gif)
 
 ## Mais informações
 
 Além das informações acima, existem outros dados retirados das interações com a operadora, com o gateway e/ou com o antifraude que são identificados e disponibilizados de forma mais clara no box **+ informações** logo abaixo do topo de informações. Veja na imagem abaixo como visualizá-las:
 
-![](//images.contentful.com/alneenqid6w5/2fHaJACApyyUsIGueGkckU/edade2f60187dc9aed87942e8030d938/8.jpg)
+![](https://images.contentful.com/alneenqid6w5/2fHaJACApyyUsIGueGkckU/edade2f60187dc9aed87942e8030d938/8.jpg)
diff --git a/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md b/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md
index 80774aeb9..b81c1aa75 100644
--- a/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md
+++ b/docs/tutorials/pt/how-to-view-transactions-on-pci-gateway.md
@@ -20,7 +20,7 @@ Todos os pedidos em que o pagamento é transacionado pela VTEX são registrados
 Na sua interface principal teremos as transações listadas em ordem da mais recente para a mais antiga.
 Na listagem já é indicado o status atual, o início (data e hora) da transação, o nome do cliente, o ID do pedido, qual o meio de pagamento utilizado para fechar o pedido e o valor transacionado no mesmo.
 
-![payment_pt](//images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/5818a03e5c91a2497e788f6bf1b6e173/payment_pt.jpg)
+![payment_pt](https://images.ctfassets.net/alneenqid6w5/3g2NhLJ0KNKatzSuVVYoVm/5818a03e5c91a2497e788f6bf1b6e173/payment_pt.jpg)
 
 Cada registro de pedido terá seus dados restritos às condições de pagamento utilizadas para o seu fechamento. Isto é, códigos de autorização, transação, NSU, entre outros, [estão disponibilizados dentro de cada registro](http://help.vtex.com/tutorial/como-visualizar-detalhes-do-pedido/).
 
diff --git a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
index a008d6cf3..7da10893d 100644
--- a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
@@ -37,7 +37,7 @@ Após isso, uma nova seção será disponibilizada e você poderá definir atrav
 
 É possível limitar a disponibilização do template para um período de tempo pré determinado nos campos __From__ e __To__ assim como definir em quais categorias, produtos, marcas e coleções o template será aplicado. 
 
-![template-condicionado-cms](//images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
+![template-condicionado-cms](https://images.ctfassets.net/alneenqid6w5/5oheUsdoc0aKS4ysOwQ6ig/66a11beac0c32d7fde34d43b94fb45bb/template-condicionado-cms.png)
 
 Após preencher todos os campos, não se esqueça de salvar as mudanças feitas clicando em __Save Layout__.
 
diff --git a/docs/tutorials/pt/hubspot-suiteshare.md b/docs/tutorials/pt/hubspot-suiteshare.md
index d3571e773..fb7d28458 100644
--- a/docs/tutorials/pt/hubspot-suiteshare.md
+++ b/docs/tutorials/pt/hubspot-suiteshare.md
@@ -23,11 +23,11 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **HubSpot**.
 
-   ![HubSpot_Suiteshare_1](//images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
+   ![HubSpot_Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
 
 2. Acesse **Configurações > Integrações > HubSpot > Integrar**.
 
-   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
 Selecione a Hubspot e clique em _**“integrar”**_
 
diff --git a/docs/tutorials/pt/i-cant-import-the-price-table.md b/docs/tutorials/pt/i-cant-import-the-price-table.md
index ea64a760c..42de3697b 100644
--- a/docs/tutorials/pt/i-cant-import-the-price-table.md
+++ b/docs/tutorials/pt/i-cant-import-the-price-table.md
@@ -56,7 +56,7 @@ Confira se os campos de sua planilha estão devidamente preenchidos conforme as
 
 Exemplo de planilha com filtros aplicados e campos __Error Code__ e __Error Message__ presentes:
 
-![Planilha de preço](//images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/0109fb3de360f568c44f6e0e6c3a920e/Price_spreadsheet.PNG)
+![Planilha de preço](https://images.ctfassets.net/alneenqid6w5/1r7FGH4sdfT0uzCUX4T07y/0109fb3de360f568c44f6e0e6c3a920e/Price_spreadsheet.PNG)
 
 #### Tamanho do arquivo
 
diff --git a/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md b/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
index c4cde5e4d..adcb246f0 100644
--- a/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
+++ b/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
@@ -95,4 +95,4 @@ Além disso, você também pode verificar se o endereço de email está cadastra
 3. Verifique se o endereço de email não está presente nos campos __Cc:__ ou __Cco:__ do template. Caso esteja, remova a informação e clique em `Salvar`.
 4. Realize este procedimento para cada um dos cards de template da loja e realize um teste de envio de email para o endereço desejado.
 
-![copia_email_pt](//images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/51aaca3868dce4213bc7c9f9b447b6ca/copia_email_pt.png)
+![copia_email_pt](https://images.ctfassets.net/alneenqid6w5/11EjQQnjcUHp2IHF87gNCy/51aaca3868dce4213bc7c9f9b447b6ca/copia_email_pt.png)
diff --git a/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
index 2ac9a0245..c4d643b0e 100644
--- a/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
+++ b/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
@@ -21,9 +21,9 @@ Quando o usuário realiza a pesquisa em uma loja VTEX por meio do [Intelligent S
 
 Cenário de exemplo: ao pesquisar no site da loja por produtos que contenham o termo "Pendleton", o resultado da busca exibe 6 produtos. Entretanto, quando acessamos o Admin VTEX (__Storefront > Intelligent Search > Explicação da busca__) e digitamos o mesmo termo, são apresentados 9 produtos.
 
-![Filter_1](//images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/d91a90067779eab00b0aefe3b40f889a/Filter_1.png)
+![Filter_1](https://images.ctfassets.net/alneenqid6w5/1bMAcWQEyVXBsUBZQp8H0K/d91a90067779eab00b0aefe3b40f889a/Filter_1.png)
 
-![Filter_2](//images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/eb0ef3af6e10a261b1e8176ca18ef04a/Filter_2.png)
+![Filter_2](https://images.ctfassets.net/alneenqid6w5/5TL7uaMv37zf7AGwohmAKu/eb0ef3af6e10a261b1e8176ca18ef04a/Filter_2.png)
 
 Este comportamento pode ocorrer devido aos seguintes cenários:
 
@@ -83,7 +83,7 @@ Para remover a restrição de busca por marca (*brand*) e permitir os produtos s
 
 <blockquote><ui>4. Em <b>Selecione um app</b>, clique sobre a opção do app Rewriter (<b>vtex.rewriter@{app-version-number}</b>).</ui>
 
-![Graphql_ide_pt](//images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/2b1cf341f212c5ac6ea16e7314d3c048/Graphql_ide_pt.png)
+![Graphql_ide_pt](https://images.ctfassets.net/alneenqid6w5/1IBr0HvF5xxf2nfxIwW4YC/2b1cf341f212c5ac6ea16e7314d3c048/Graphql_ide_pt.png)
 
 <blockquote><ui>5. No campo de preenchimento da query (abaixo de <b>GraphiQL</b>), insira os dados da função mutação <i>saveInternal</i>.<ui>
 
diff --git a/docs/tutorials/pt/i-forgot-my-password-suiteshare.md b/docs/tutorials/pt/i-forgot-my-password-suiteshare.md
index c12ba797d..0feb632ac 100644
--- a/docs/tutorials/pt/i-forgot-my-password-suiteshare.md
+++ b/docs/tutorials/pt/i-forgot-my-password-suiteshare.md
@@ -17,14 +17,14 @@ subcategory: 4y4ylvqceE6vVqEF8IWZix
 
 Para recuperar sua senha, acesse o site do [VTEX Assisted Sales (SuiteShare)](https://suiteshare.com) e clique em **Entrar**. 
 
-![Senha_Suitshare_1](//images.ctfassets.net/alneenqid6w5/4tYRuHpLYfRQNao1GV3Tix/dacb5d395c1e04aeaeb9fb438df56b27/Senha_Suitshare_1.png)
+![Senha_Suitshare_1](https://images.ctfassets.net/alneenqid6w5/4tYRuHpLYfRQNao1GV3Tix/dacb5d395c1e04aeaeb9fb438df56b27/Senha_Suitshare_1.png)
 
 Clique em **Esqueci minha senha**.
 
-![Senha_Suitshare_2](//images.ctfassets.net/alneenqid6w5/1F57gl3OYPJz4VxNghFIZM/d3af7ad7764de2b15dd3c305b2263597/Senha_Suitshare_2.png)
+![Senha_Suitshare_2](https://images.ctfassets.net/alneenqid6w5/1F57gl3OYPJz4VxNghFIZM/d3af7ad7764de2b15dd3c305b2263597/Senha_Suitshare_2.png)
 
 Digite o seu email, para receber as informações de redefinição de senha.
 
-![Senha_Suitshare_3](//images.ctfassets.net/alneenqid6w5/6K44Aat6Ad3HVg2wwCKsq2/ba3d2d6801e39cd0650cbed4c0fc30a1/Senha_Suitshare_3.png)
+![Senha_Suitshare_3](https://images.ctfassets.net/alneenqid6w5/6K44Aat6Ad3HVg2wwCKsq2/ba3d2d6801e39cd0650cbed4c0fc30a1/Senha_Suitshare_3.png)
 
 Pronto! Basta adicionar a nova senha e realizar o login normalmente.
diff --git a/docs/tutorials/pt/identifying-whether-marketing-utms-are-being-passed-to-checkout.md b/docs/tutorials/pt/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
index ded7dbd5e..c14b9ef1c 100644
--- a/docs/tutorials/pt/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
+++ b/docs/tutorials/pt/identifying-whether-marketing-utms-are-being-passed-to-checkout.md
@@ -27,13 +27,13 @@ Com isso o checkout poderá montar o orderForm considerando o marketingData usad
 
 Para se certificar de que o conteúdo do parâmetro `utm_source`, por exemplo, está sendo passado ao checkout, você pode seguir as etapas abaixo:
 1. Acesse qualquer página da loja com a utm na querystring (ex: {AccountName}.com.br`?utm_source=facebook`)
-2. Entre nos __developer tools__ (F12 no Chrome, se estiver no Windows, ou Cmd+Opt+I, no Mac), acesse a aba __Application__, abra os cookies do site da loja e procure o cookie __IPS__.![utmSource1](//images.contentful.com/alneenqid6w5/2tGleKs2b2Gge8oEoquSGm/17efaf14e42cd655b037c2bd009eb0d6/utmSource1.png)
+2. Entre nos __developer tools__ (F12 no Chrome, se estiver no Windows, ou Cmd+Opt+I, no Mac), acesse a aba __Application__, abra os cookies do site da loja e procure o cookie __IPS__.![utmSource1](https://images.contentful.com/alneenqid6w5/2tGleKs2b2Gge8oEoquSGm/17efaf14e42cd655b037c2bd009eb0d6/utmSource1.png)
 3. Entre numa página de produto e insira um produto no carrinho.
 4. Entre no carrinho.
 5. Atualize a página e, na aba __Network__ do developer tools, monitore os requests.
 6. Selecione o request __orderForm__.
 7. No preview, abra o nó `marketingData`.
-8. Confira o valor do campo `utmSource`.![utmSource2](//images.contentful.com/alneenqid6w5/3k5685cAUwy4uk4S2I6qGm/6595f50415b17965047c2023ffb46658/utmSource2.png)
+8. Confira o valor do campo `utmSource`.![utmSource2](https://images.contentful.com/alneenqid6w5/3k5685cAUwy4uk4S2I6qGm/6595f50415b17965047c2023ffb46658/utmSource2.png)
 
 No exemplo da imagem acima, note que o valor do parâmetro `utm_source` foi corretamente passado para o checkout, que inseriu esse parâmetro no orderForm, dentro do campo `utmSource`.
 
diff --git a/docs/tutorials/pt/image-compression.md b/docs/tutorials/pt/image-compression.md
index 0de7b81d8..e84c57b08 100644
--- a/docs/tutorials/pt/image-compression.md
+++ b/docs/tutorials/pt/image-compression.md
@@ -44,7 +44,7 @@ Paralelamente, ocorre a otimização de imagens PNG utilizando [pngquant](https:
 
 Por fim, a VTEX entrega o menor arquivo, entre o WebP lossless e o PNG otimizado, conforme ilustrado no diagrama abaixo.
 
-![png-image-compression-pt](//images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/fc5d276c114827f9692cf4b4bf8fd31b/png-image-compression-pt.PNG)
+![png-image-compression-pt](https://images.ctfassets.net/alneenqid6w5/2i6UAp6HkiWl87Q7SDfIMB/fc5d276c114827f9692cf4b4bf8fd31b/png-image-compression-pt.PNG)
 
 ## JPG / JPEG
 
@@ -52,7 +52,7 @@ Para imagens no formato **JPG / JPEG**, indicado para fotos, a conversão para W
 
 A VTEX entrega ao cliente a imagem com menor tamanho de arquivo, dentre a original e a convertida em WebP lossless, conforme ilustrado no diagrama abaixo.
 
-![webp-image-compression-pt](//images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/b22f2eea1c7d528e32932d58a537b36c/webp-image-compression-pt.PNG)
+![webp-image-compression-pt](https://images.ctfassets.net/alneenqid6w5/6fZVHgF3ExpBr4XOpjw2pi/b22f2eea1c7d528e32932d58a537b36c/webp-image-compression-pt.PNG)
 
 ## Artigos relacionados
 
diff --git a/docs/tutorials/pt/importing-amazon-dba-orders.md b/docs/tutorials/pt/importing-amazon-dba-orders.md
index 5012933c1..0a21b032a 100644
--- a/docs/tutorials/pt/importing-amazon-dba-orders.md
+++ b/docs/tutorials/pt/importing-amazon-dba-orders.md
@@ -61,7 +61,7 @@ Após salvar as configurações, o DBA estará ativo na integração com a Amazo
 
 A cada compra finalizada, os pedidos correspondentes ao DBA aparecerão na aba __Pedidos > Todos pedidos__ do Admin VTEX. O sufixo **`_DBA`** aparecerá no ID de cada pedido do programa. Para prosseguir com a entrega, o pedido precisa ser faturado, conforme os passos descritos em [Faturar um pedido > Nota Fiscal](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT#nota-fiscal).  
 
-![pedido DBA](//downloads.ctfassets.net/alneenqid6w5/29NDtLCX5tVW7SzePTvuEG/32ab35230267fe61f772d9c60ea555e8/Pedidos.gif)
+![pedido DBA](https://downloads.ctfassets.net/alneenqid6w5/29NDtLCX5tVW7SzePTvuEG/32ab35230267fe61f772d9c60ea555e8/Pedidos.gif)
 
 ### 3. Download de etiqueta  
 
diff --git a/docs/tutorials/pt/importing-data-into-master-data.md b/docs/tutorials/pt/importing-data-into-master-data.md
index 95153166f..36ba9d5d3 100644
--- a/docs/tutorials/pt/importing-data-into-master-data.md
+++ b/docs/tutorials/pt/importing-data-into-master-data.md
@@ -49,4 +49,4 @@ Mantenha o mesmo formato da planilha (xls) para realizar a importação com suce
 5. Escolha o arquivo.
 6. Clique no botão **Importar** no canto inferior da tela.
 
-![Importando](//images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
+![Importando](https://images.contentful.com/alneenqid6w5/3xkB2DzbqoeIsk2Qice8sM/71d3c7d0379e03a8641180ccbe97dc77/Importando-1.gif)
diff --git a/docs/tutorials/pt/improving-the-performance-of-product-images.md b/docs/tutorials/pt/improving-the-performance-of-product-images.md
index e400845b4..598f8a031 100644
--- a/docs/tutorials/pt/improving-the-performance-of-product-images.md
+++ b/docs/tutorials/pt/improving-the-performance-of-product-images.md
@@ -64,7 +64,7 @@ No nosso exemplo anterior, basta escrever da seguinte maneira a URL da imagem no
 
 Desta forma, o VTEX Img entregará a imagem com um tamanho de 50x50. Isto tornará seu carregamento muito mais rápido.
 
-![tamanhosImg](//images.contentful.com/alneenqid6w5/p4aDcgaE4SmyYkCwaW0CI/189307d29c86dae17beabde67780d907/tamanhosImg.png)
+![tamanhosImg](https://images.contentful.com/alneenqid6w5/p4aDcgaE4SmyYkCwaW0CI/189307d29c86dae17beabde67780d907/tamanhosImg.png)
 _Entregar imagens em um tamanho maior que o de exibição prejudica a performance da sua loja._
 
 ## Imagens retangulares
diff --git a/docs/tutorials/pt/improving-the-seo-of-product-listing-pages.md b/docs/tutorials/pt/improving-the-seo-of-product-listing-pages.md
index fb772a410..7a12b848d 100644
--- a/docs/tutorials/pt/improving-the-seo-of-product-listing-pages.md
+++ b/docs/tutorials/pt/improving-the-seo-of-product-listing-pages.md
@@ -21,7 +21,7 @@ As PLPs são correlacionadas, pois cada produto tem um link de volta para uma p
 
 Para melhorar o desempenho de SEO das PLPs, você deve permitir que os rastreadores da web, como Google, percebam essa conexão entre as PLPs. Desse modo, esses rastreadores serão capazes de navegar em diferentes páginas e acessar os diferentes produtos que elas mostram.
 
-![Botão mostrar mais](//images.contentful.com/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/407d073404b0f7eaa7934dc7bc4a64f9/bt-mostrar-mais.png)
+![Botão mostrar mais](https://images.contentful.com/alneenqid6w5/63jE8FYBJW8ssJOXwoADTZ/407d073404b0f7eaa7934dc7bc4a64f9/bt-mostrar-mais.png)
 
 Veja na seção abaixo como melhorar o desempenho de SEO das PLPs [usando o Site Editor](#usando-site-editor).
 
@@ -40,7 +40,7 @@ Para melhorar o desempenho de SEO das PLPs via Site Editor, você deve configura
 4. Clique em __Mostrar mais.__
 5. Em __Comportamento do botão,__ selecione a opção __Link para a página - Melhora o SEO, pode mudar a aparência do botão.__
 
-![bt-config-pt](//images.contentful.com/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/3f3cbb455fd6739c886beae22017e2b6/bt-config-pt.gif)
+![bt-config-pt](https://images.contentful.com/alneenqid6w5/6LQJMtP8loMFop3pp5NgFt/3f3cbb455fd6739c886beae22017e2b6/bt-config-pt.gif)
 
 6. Clique em `SALVAR`.
 7. Para configurar o item __Mostrar anteriores,__ expanda o bloco __Resultado de busca flexível.__
diff --git a/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md b/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md
index 169e61fd1..533d09012 100644
--- a/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md
+++ b/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md
@@ -36,7 +36,7 @@ Digamos que você queira inserir o nome da transportadora no e-mail de pedido en
 
 Para fazer isso, entre no template de pedido enviado e, no campo __JSON Data__, busque a propriedade `courier`.
 
-![courier](//images.contentful.com/alneenqid6w5/2AKyoHdoQ8c40SsQa2uSKS/b4c2b0c460d0f31bec40148f5bba6006/courier.png)
+![courier](https://images.contentful.com/alneenqid6w5/2AKyoHdoQ8c40SsQa2uSKS/b4c2b0c460d0f31bec40148f5bba6006/courier.png)
 
 O valor preenchido para essa propriedade é apenas um exemplo, mas você pode usá-la no campo __HTML__ para que, quando o e-mail for enviado, o cliente veja a transportadora de fato responsável pela entrega do pedido.
 
@@ -44,7 +44,7 @@ Note que a propriedade `courier` está dentro do objeto `package`. Portanto, voc
 
 `{{package.courier}}`
 
-![courier3](//images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
+![courier3](https://images.contentful.com/alneenqid6w5/2yzopAVuU46I2UICEQ0y2S/69e4a43fa202c90cb9996f4a3eea19aa/courier3.png)
 
 Veja que o valor de exemplo ("Transportadora Teste Courier S.A.") foi inserido na tela de preview, abaixo dos campos __HTML__ e __JSON Data__.
 
diff --git a/docs/tutorials/pt/indexes-in-master-data.md b/docs/tutorials/pt/indexes-in-master-data.md
index c0f8f5d05..d1ed2835c 100644
--- a/docs/tutorials/pt/indexes-in-master-data.md
+++ b/docs/tutorials/pt/indexes-in-master-data.md
@@ -55,11 +55,11 @@ Se houver somente um campo configurado como índice, a chave alternativa não va
 
 Por exemplo, a tabela **Cliente** possui duas colunas: **ID** e **Nome**. Para facilitar a busca, o campo **Nome** (`firstName`) pode ser configurado como índice e marcado como **Valores únicos**, conforme ilustrado a seguir:
 
-![indices-1-pt](//images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/cde79764d3fe7472eca9db660139a068/indices-1-pt.png)
+![indices-1-pt](https://images.ctfassets.net/alneenqid6w5/3OsXbib7NQTwtjSzBlvR0a/cde79764d3fe7472eca9db660139a068/indices-1-pt.png)
 
 Com isso, não será possível inserir um nome que já tenha sido cadastrado em __Cliente__:
 
-![indices-2-pt](//images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/c7e27a54409119fa21c5ff4a137c7879/indices-2-pt.png)
+![indices-2-pt](https://images.ctfassets.net/alneenqid6w5/4hHQqk8reoDAAzuMiNBncY/c7e27a54409119fa21c5ff4a137c7879/indices-2-pt.png)
 
 No exemplo acima, como já existe um registro com o **Nome** igual a **Maria**, não é possível cadastrar outro com o mesmo valor.
 
@@ -73,11 +73,11 @@ Se houver mais de um campo no índice, a chave alternativa vai impedir que um co
 
 Por exemplo, imagine que a entidade **Cliente **possui três campos: **ID**, **Nome** e **Documento**. Na configuração do índice, em **Campos**, foram inseridos Nome (`firstName`) e Documento (`document`), conforme ilustrado abaixo:
 
-![indices-3-pt](//images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/b4a19b8d53d100227895aeda8951718f/indices-3-pt.png)
+![indices-3-pt](https://images.ctfassets.net/alneenqid6w5/66m8jlFgaiE07dSpSFiWhg/b4a19b8d53d100227895aeda8951718f/indices-3-pt.png)
 
 Nesse caso, o valor do **Nome** pode se repetir ou o valor do **Documento** pode se repetir. Porém, a combinação dos dois valores não pode se repetir, ou seja, não pode existir nenhum registro que repita o mesmo par (**Nome** e **Documento **iguais).
 
-![indices-4-pt](//images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/1d6132aa5f7eaadd2425530e5e536f9b/indices-4-pt.png)
+![indices-4-pt](https://images.ctfassets.net/alneenqid6w5/7sLqZNCOgjbF794zd6Jcz7/1d6132aa5f7eaadd2425530e5e536f9b/indices-4-pt.png)
 
 No exemplo acima, já existe um registro com o **Nome** igual a **Maria**. É possível incluir outro registro com o mesmo **Nome**, desde que o valor do **Documento** seja diferente.
 
diff --git a/docs/tutorials/pt/indexing-history-beta.md b/docs/tutorials/pt/indexing-history-beta.md
index 2f34231c7..e9198fe32 100644
--- a/docs/tutorials/pt/indexing-history-beta.md
+++ b/docs/tutorials/pt/indexing-history-beta.md
@@ -21,12 +21,12 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 
 **Histórico da Indexação** é a página que monitora a situação de sincronização de todos os produtos do Catálogo enviados para o Intelligent Search. Ele permite visualizar de forma ampla o progresso da indexação da sua loja.
 
-![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 1 - PT](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
 
 A seção **Status da indexação** exibe as seguintes informações:
 
 * **Tempo médio de indexação:** tempo médio para a indexação dos produtos, a partir do momento em que o sistema recebeu a notificação de uma mudança até a atualização na loja. O desempenho do tempo de indexação é medido por um ponto verde (saudável) ou vermelho (ruim). 
-![Historico Indexação 2 - PT](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
+![Historico Indexação 2 - PT](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
 * **Produtos na loja:** quantidade de produtos com informações atualizadas exibidos atualmente na loja.
 * **Divisão dos status:** porcentagem de produtos em cada etapa de indexação. O desempenho da divisão dos status é medido por um ponto verde (saudável) ou vermelho (ruim). As etapas exibidas são:
     * **Atualizado:** a atualização mais recente do produto foi inserida na loja.
@@ -37,15 +37,15 @@ Você pode filtrar a lista de produtos indexados para uma visualização customi
 
 Para filtrar a lista de produtos indexados clique em `Filtro` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Status` você pode selecionar por qual status deseja filtrar, podendo ser `Atualizado`, `Atualizando`, `Erro`.
 
- ![Historico indexação 4 - PT](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+ ![Historico indexação 4 - PT](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Tempo de indexação` você pode selecionar se o intervelo de tempo `É maior que`, `É igual ou maior que`, `É menor que` ou `É igual ou menor que` um horário definido.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
 
 Depois de definir o filtro, clique em `Aplicar` para ativá-lo. 
 
@@ -55,18 +55,18 @@ Você também pode filtrar os produtos exibidos na listagem por **ID**, **Últim
 
 Caso deseje obter mais informações sobre a indexação de um produto específico, você pode clicar na linha do produto na lista para acessar a janela com mais detalhes, ilustrada abaixo.
 
-![Historico indexação 6 - PT](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 6 - PT](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Além dos dados exibidos na lista de produtos, também é possível visualizar:
 
 * **Tempo de Indexação:** registro de quanto tempo durou a última atualização do produto, no formato `hh:mm:ss`.
 * **Linha do tempo da indexação:** registro de cada mudança de status com data e horário. Você pode vizualizar mais detalhes de cada etapa clicando no ícone <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - PT](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 7 - PT](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 É possível reindexar um produto manualmente sem a necessidade de realizar alguma atualização no seu cadastro. Para reidexar um produto, clique em <i class="fa-solid fa-arrows-rotate"></i> `Reindexar`. Apenas produtos no status **Atualizado** podem ser reindexados.
 
 Você pode acessar o **Histórico de indexação** do produto, uma lista com data e horário de cada atualização realizada. Dessa forma, é possível ter registro de toda alteração que foi realizada no produto. Para acessá-lo, clique em <i class="fa-solid fa-arrow-rotate-left"></i> `Histórico`. 
 
-![Histórico da Indexação 8 - PT](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 8 - PT](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
 
diff --git a/docs/tutorials/pt/indexing-history.md b/docs/tutorials/pt/indexing-history.md
index dcaca3fa6..317d041f4 100644
--- a/docs/tutorials/pt/indexing-history.md
+++ b/docs/tutorials/pt/indexing-history.md
@@ -17,12 +17,12 @@ subcategory: l3DubpOCHBfKyF2ueg2Vs
 
 **Histórico da Indexação** é a página que monitora a situação de sincronização de todos os produtos do Catálogo enviados para o Intelligent Search. Ele permite visualizar de forma ampla o progresso da indexação da sua loja.
 
-![Histórico da Indexação 1 - PT](//images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 1 - PT](https://images.ctfassets.net/alneenqid6w5/5xzFLcLomZTSXgdqyK2rH/eafd584f145b495cab5aee630f44fb8a/Screenshot_2022-09-01_at_12-47-19_Hist__rico_da_Indexa____o.png)
 
 A seção **Status da indexação** exibe as seguintes informações:
 
 * **Tempo médio de indexação:** tempo médio para a indexação dos produtos, a partir do momento em que o sistema recebeu a notificação de uma mudança até a atualização na loja. O desempenho do tempo de indexação é medido por um ponto verde (saudável) ou vermelho (ruim). 
-![Historico Indexação 2 - PT](//images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
+![Historico Indexação 2 - PT](https://images.ctfassets.net/alneenqid6w5/3xjj1vez5Z6tImLPrJyaGD/4edc414b3c0a6c77f66577006b4b1094/Captura_de_Tela_2022-09-01_a__s_12.55.40.png)
 * **Produtos na loja:** quantidade de produtos com informações atualizadas exibidos atualmente na loja.
 * **Divisão dos status:** porcentagem de produtos em cada etapa de indexação. O desempenho da divisão dos status é medido por um ponto verde (saudável) ou vermelho (ruim). As etapas exibidas são:
     * **Atualizado:** a atualização mais recente do produto foi inserida na loja.
@@ -33,15 +33,15 @@ Você pode filtrar a lista de produtos indexados para uma visualização customi
 
 Para filtrar a lista de produtos indexados clique em `Filtro` <img src="//images.ctfassets.net/alneenqid6w5/7fFqJC2W7BQXSHlocRAqOM/dc6cf099d6add3b55d0353024dcc3ca8/Screenshot_2022-09-01_at_13-46-21_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png" alt="filtros" width="25"/>. Selecione `Status` ou `Tempo de indexação` para definir o critério de filtragem. 
 
-![Historico indexação 3 - PT](//images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 3 - PT](https://images.ctfassets.net/alneenqid6w5/4lDygmJ2FzZsQF60nVb4fj/62e70bc865853961ce4d57456e7d3830/Screenshot_2022-09-01_at_13-08-05_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Status` você pode selecionar por qual status deseja filtrar, podendo ser `Atualizado`, `Atualizando`, `Erro`.
 
- ![Historico indexação 4 - PT](//images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+ ![Historico indexação 4 - PT](https://images.ctfassets.net/alneenqid6w5/1ryNxIRRLeuZtRfhV4BmuQ/98c1a8334a4059c288a5e2df8c517426/Screenshot_2022-09-01_at_13-08-11_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Caso filtre por `Tempo de indexação` você pode selecionar se o intervelo de tempo `É maior que`, `É igual ou maior que`, `É menor que` ou `É igual ou menor que` um horário definido.
 
-![Historico indexação 5 - PT](//images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
+![Historico indexação 5 - PT](https://images.ctfassets.net/alneenqid6w5/5OzQHzuBsYz0jHpBP3f71k/0fd37c74d7c095d3d3b23495898ec045/Captura_de_Tela_2022-09-01_a__s_15.39.29.png)
 
 Depois de definir o filtro, clique em `Aplicar` para ativá-lo. 
 
@@ -51,18 +51,18 @@ Você também pode filtrar os produtos exibidos na listagem por **ID**, **Últim
 
 Caso deseje obter mais informações sobre a indexação de um produto específico, você pode clicar na linha do produto na lista para acessar a janela com mais detalhes, ilustrada abaixo.
 
-![Historico indexação 6 - PT](//images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 6 - PT](https://images.ctfassets.net/alneenqid6w5/1sDrEMUBa3D7JbzF8EOXmX/21792b7c3840b60739a8b8f1ad7e725b/Screenshot_2022-09-01_at_13-18-23_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 Além dos dados exibidos na lista de produtos, também é possível visualizar:
 
 * **Tempo de Indexação:** registro de quanto tempo durou a última atualização do produto, no formato `hh:mm:ss`.
 * **Linha do tempo da indexação:** registro de cada mudança de status com data e horário. Você pode vizualizar mais detalhes de cada etapa clicando no ícone <i class="fa-solid fa-chevron-down"></i>.
 
-![Historico indexação 7 - PT](//images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
+![Historico indexação 7 - PT](https://images.ctfassets.net/alneenqid6w5/7cKIak0WrkdJocLWtyxzvo/af57b47341ca28144aad637c55704af8/Screenshot_2022-09-01_at_13-22-34_EDU-7374_-_Documenta____o_nova_tela_de_indexa____o.png)
 
 É possível reindexar um produto manualmente sem a necessidade de realizar alguma atualização no seu cadastro. Para reidexar um produto, clique em <i class="fa-solid fa-arrows-rotate"></i> `Reindexar`. Apenas produtos no status **Atualizado** podem ser reindexados.
 
 Você pode acessar o **Histórico de indexação** do produto, uma lista com data e horário de cada atualização realizada. Dessa forma, é possível ter registro de toda alteração que foi realizada no produto. Para acessá-lo, clique em <i class="fa-solid fa-arrow-rotate-left"></i> `Histórico`. 
 
-![Histórico da Indexação 8 - PT](//images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
+![Histórico da Indexação 8 - PT](https://images.ctfassets.net/alneenqid6w5/6SYLHXtHBZRF6OvvNMuwNv/8a1542cd6bb290282a686fb3bb889b27/Screenshot_2022-09-01_at_13-43-12_Hist__rico_da_Indexa____o.png)
 
diff --git a/docs/tutorials/pt/install-visa-checkout-in-the-extension-store.md b/docs/tutorials/pt/install-visa-checkout-in-the-extension-store.md
index 9d35392b8..70fc7c0cf 100644
--- a/docs/tutorials/pt/install-visa-checkout-in-the-extension-store.md
+++ b/docs/tutorials/pt/install-visa-checkout-in-the-extension-store.md
@@ -21,7 +21,7 @@ Este artigo tem o objetivo de mostrar o passo-a-passo para instalação da exten
 
 Primeiro, na tela **Explorar**, clique na extensão **Visa Checkout**.
 
-![Extension Store 1](//images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
+![Extension Store 1](https://images.contentful.com/alneenqid6w5/6E480Kd4t2EqimaiKW8cii/ef5ba713601e5bdc4f97ff20133aa354/Extension_Store_1.png)
 
 Você terá então acesso à página de detalhes da extensão, onde as seguintes informações são mostradas:
 
@@ -76,4 +76,4 @@ Para mover o Visa Checkout para o ambiente em produção (onde seus clientes pod
 
 Para isso, basta clicar no botão **Publicar** da top bar.
 
-![Extension Store 3 - Publishing](//images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
+![Extension Store 3 - Publishing](https://images.contentful.com/alneenqid6w5/39BcR4BFkk8kGEKiaEWICU/f195532be2243b35168ac69e72226d20/Extension_Store_3_-_Publishing.png)
diff --git a/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md b/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md
index 6df6b456a..7849011c1 100644
--- a/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md
+++ b/docs/tutorials/pt/installing-my-orders-through-the-extension-store.md
@@ -19,7 +19,7 @@ Acompanhando a evolução da plataforma VTEX, a viewpart de __Meus Pedidos__ ago
 
 Para fazer sua instalação, é preciso que você acesse a [VTEX App Store.](https://extensions.vtex.com/)
 
-![app store1 PT](//images.ctfassets.net/alneenqid6w5/2aqC9IvvUM6o6Ko4WusYYQ/87950d670a9ff9eaa858bd3d24186814/app_store1_PT.png)
+![app store1 PT](https://images.ctfassets.net/alneenqid6w5/2aqC9IvvUM6o6Ko4WusYYQ/87950d670a9ff9eaa858bd3d24186814/app_store1_PT.png)
 
 __Ao instalar a app, você já conta com as seguintes atualizações:__
 
@@ -29,7 +29,7 @@ __Ao instalar a app, você já conta com as seguintes atualizações:__
 - Informações de rastreio para vários itens.
 - Correção de bugs menores.
 
-![app store2 PT](//images.ctfassets.net/alneenqid6w5/6NFSN0UxEcQgSWK6UaU8OW/5db671b107a7f6bd248aa4940dc5a108/app_store2_PT.png)
+![app store2 PT](https://images.ctfassets.net/alneenqid6w5/6NFSN0UxEcQgSWK6UaU8OW/5db671b107a7f6bd248aa4940dc5a108/app_store2_PT.png)
 
 Além disso, com o novo app você consegue, realizar testes de versões e atualizá-lo sempre que uma nova versão estiver disponível, recebendo melhorias contínuas e atualizações de novas features.
 
@@ -42,4 +42,4 @@ Para fazer os testes de customização na sua página, você pode trabalhar em u
 5. Pronto! Agora você vê, antes de subir sua página, como ela irá se comportar.
 6. Para mover o My Orders para o ambiente em produção (onde seus clientes podem de fato usá-lo), você precisa publicar a modificação. Para isso, basta clicar no botão __Publicar__.
 
-![app store3 PT](//images.ctfassets.net/alneenqid6w5/6jIsBdBtfiiKgiW6saCcMS/c81ca0455ac08dacf4a4d1db44782a15/app_store3_PT.png)
+![app store3 PT](https://images.ctfassets.net/alneenqid6w5/6jIsBdBtfiiKgiW6saCcMS/c81ca0455ac08dacf4a4d1db44782a15/app_store3_PT.png)
diff --git a/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md b/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md
index 8d2f937a6..62469511f 100644
--- a/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md
+++ b/docs/tutorials/pt/installing-the-widget-with-gtm-suiteshare.md
@@ -23,44 +23,44 @@ Para instalar o nosso widget no seu site, siga os passos abaixo:
 
 1. Em nosso CMS, acesse o menu **Widget** e depois em **Instalação**.
 
-   ![Widget_1](//images.ctfassets.net/alneenqid6w5/PvBIqUXXoy0HKgG9kHYQF/861a7781882e3459c3e4446c53bf3f7c/Widget_1.png)
+   ![Widget_1](https://images.ctfassets.net/alneenqid6w5/PvBIqUXXoy0HKgG9kHYQF/861a7781882e3459c3e4446c53bf3f7c/Widget_1.png)
 
 2. Clique no botão **COPIAR CÓDIGO** e salve esse código em um bloco de notas.
 
-   ![Widget_2](//images.ctfassets.net/alneenqid6w5/5x9QKNU0tIYtoAzYv3JMGK/ee316a807d88dc202bb002217b780469/Widget_2.png)
+   ![Widget_2](https://images.ctfassets.net/alneenqid6w5/5x9QKNU0tIYtoAzYv3JMGK/ee316a807d88dc202bb002217b780469/Widget_2.png)
 
 3. No GTM, clique no menu **Tags** e, após nisso, no botão **New**.
 
-   ![Widget_3](//images.ctfassets.net/alneenqid6w5/5JEWuW29vUzuXxU1ZIE3T3/a0bba65a23153557b65776b870bd2ba3/Widget_3.png)
+   ![Widget_3](https://images.ctfassets.net/alneenqid6w5/5JEWuW29vUzuXxU1ZIE3T3/a0bba65a23153557b65776b870bd2ba3/Widget_3.png)
 
 4. Na tela abaixo, defina um nome para a tag (ex: VTEX Assisted Sales (SuiteShare) - Widget) e clique em **Choose a tag type to begin setup** para configurar a tag.
 
-   ![Widget_4](//images.ctfassets.net/alneenqid6w5/7LcqsWNdLni472pl8Xn85n/378cccd15c9139214cafb9491fd84c40/Widget_4.png)
+   ![Widget_4](https://images.ctfassets.net/alneenqid6w5/7LcqsWNdLni472pl8Xn85n/378cccd15c9139214cafb9491fd84c40/Widget_4.png)
 
 5. Após clicar na opção acima, irá surgir um menu a direita. Nesse menu, selecione a opção **Custom HTML**.
 
-   ![Widget_5](//images.ctfassets.net/alneenqid6w5/19ve1JVLWfVTHhz8lQg64t/14b851233c3bbbaced668fad02bfd8ca/Widget_5.png)
+   ![Widget_5](https://images.ctfassets.net/alneenqid6w5/19ve1JVLWfVTHhz8lQg64t/14b851233c3bbbaced668fad02bfd8ca/Widget_5.png)
 
 6. No campo exibido, cole o código copiado no **item 1** desse artigo.
 
-   ![Widget_6](//images.ctfassets.net/alneenqid6w5/5n3YOrNAiZt0bEdGgQrF7w/f26751fb2bc334254f173a16dac0fd32/Widget_6.png)
+   ![Widget_6](https://images.ctfassets.net/alneenqid6w5/5n3YOrNAiZt0bEdGgQrF7w/f26751fb2bc334254f173a16dac0fd32/Widget_6.png)
 
 7. Ainda na tela acima, após colar o nosso código, clique em **Choose a trigger to make this tag fire...**. Será exibido um novo menu a direita, onde você deve selecionar a opção **All Pages**.
 
-   ![Widget_7](//images.ctfassets.net/alneenqid6w5/7DW6UcnlaTC5fgWRnG1BsR/48063165c62c1550fb505f067b922966/Widget_7.png)
+   ![Widget_7](https://images.ctfassets.net/alneenqid6w5/7DW6UcnlaTC5fgWRnG1BsR/48063165c62c1550fb505f067b922966/Widget_7.png)
 
 8. Após isso, o resultado será uma tela semelhante a abaixo.
 
-   ![Widget_8](//images.ctfassets.net/alneenqid6w5/753LeeyLcq2EUuMMG4riJY/8663150797f41fe362867ab30d3c3178/Widget_8.png)
+   ![Widget_8](https://images.ctfassets.net/alneenqid6w5/753LeeyLcq2EUuMMG4riJY/8663150797f41fe362867ab30d3c3178/Widget_8.png)
 
 9. Clique no botão **Save** a direita, para salvar sua tag de instalação do widget VTEX Assisted Sales (SuiteShare).
 
 10. Por fim, publique essa alteração do GTM: clique no menu **Submit** a direita.
 
-   ![Widget_9](//images.ctfassets.net/alneenqid6w5/6QLTRqElrB59rchytvzNzI/b8eb90559fa7b9537b08d41b17a1bee2/Widget_9.png)
+   ![Widget_9](https://images.ctfassets.net/alneenqid6w5/6QLTRqElrB59rchytvzNzI/b8eb90559fa7b9537b08d41b17a1bee2/Widget_9.png)
 
 11. Informe um título e descrição da versão do deploy e clique em **Publish**.
 
-   ![Widget_10](//images.ctfassets.net/alneenqid6w5/gec4OU8KY7V5KCYCS1OUS/8758cda8e7ced08ee85a0948a80a419e/Widget_10.png)
+   ![Widget_10](https://images.ctfassets.net/alneenqid6w5/gec4OU8KY7V5KCYCS1OUS/8758cda8e7ced08ee85a0948a80a419e/Widget_10.png)
 
 Pronto, a integração foi finalizada.
diff --git a/docs/tutorials/pt/integrating-with-farmacias-app.md b/docs/tutorials/pt/integrating-with-farmacias-app.md
index 4e92108fe..fa50e53fc 100644
--- a/docs/tutorials/pt/integrating-with-farmacias-app.md
+++ b/docs/tutorials/pt/integrating-with-farmacias-app.md
@@ -49,7 +49,7 @@ Depois, será necessário:
 Por fim, deve ser realizado o cadastro do afiliado, que serve como identificação única do marketplace em sua loja. Para fazer isso, siga os passos abaixo:
 
 1. Acesse o menu **Configurações da loja > Pedidos**;
-2. Clique no botão **Conigurações**;![Farmacias2](//images.contentful.com/alneenqid6w5/7Mekt0KzpmaS4M4uoEu2kC/d0b13138a044072b6ba2c7c89808eacc/Farmacias2.png)
+2. Clique no botão **Conigurações**;![Farmacias2](https://images.contentful.com/alneenqid6w5/7Mekt0KzpmaS4M4uoEu2kC/d0b13138a044072b6ba2c7c89808eacc/Farmacias2.png)
 3. Clique na aba **Afiliados**;
 4. Clique no botão **Novo afiliado**;
 5. Preencha os campos da seguinte forma:
@@ -60,7 +60,7 @@ Por fim, deve ser realizado o cadastro do afiliado, que serve como identificaç
 **E-mail de follow up**: _e-mail da pessoa responsável pela integração_;
 **Endpoint de Search**: https://integrador.farmaciasapp.com.br/Vtex/api/notification
 
-![Farmacias3](//images.contentful.com/alneenqid6w5/6pnQjxLuhO8cUogU6oYoig/953a840b59416974f9a3baeff39d47cd/Farmacias3.png)
+![Farmacias3](https://images.contentful.com/alneenqid6w5/6pnQjxLuhO8cUogU6oYoig/953a840b59416974f9a3baeff39d47cd/Farmacias3.png)
 
 _Quando os pagamentos forem processados por meio do Farmácias App, a opção **Usar meu meio de pagamento** deve estar desmarcada. Marque essa opção apenas para pagamentos processados em ambientes diferentes, como pagamentos processados na plataforma VTEX._
 
diff --git a/docs/tutorials/pt/integration-guide-for-erps-orders.md b/docs/tutorials/pt/integration-guide-for-erps-orders.md
index 0ddb8a87f..c39e4d89d 100644
--- a/docs/tutorials/pt/integration-guide-for-erps-orders.md
+++ b/docs/tutorials/pt/integration-guide-for-erps-orders.md
@@ -25,7 +25,7 @@ Neste artigo, você encontrará o principal método para entrada dos pedidos rec
 
 A integração de um pedido compreende quatro momentos distintos, cada um deles sendo um pequeno processo por si só.
 
-![ERP Orders 1](//images.contentful.com/alneenqid6w5/7MtCGP7jpKOO2gKa8muGwO/481c6346e0d216f1cbe0588dc79eb617/ERP_Orders_1.png) 
+![ERP Orders 1](https://images.contentful.com/alneenqid6w5/7MtCGP7jpKOO2gKa8muGwO/481c6346e0d216f1cbe0588dc79eb617/ERP_Orders_1.png) 
 
 ## Download de pedido
 
@@ -35,7 +35,7 @@ Após decidir que é hora de levar um pedido para sua plataforma de fulfillment,
 
 No fim, para os pedidos processados, você envia ao OMS uma mensagem de "Start Handling".
 
-![ERP Orders 2](//images.contentful.com/alneenqid6w5/3SUWupt48gSG2iqM2q8qEA/28a578fa22944fac74f7f9d9121506ca/orders-integration-download.png) 
+![ERP Orders 2](https://images.contentful.com/alneenqid6w5/3SUWupt48gSG2iqM2q8qEA/28a578fa22944fac74f7f9d9121506ca/orders-integration-download.png) 
 
 ### Chamadas de API
 
@@ -102,7 +102,7 @@ Agora o pedido está sendo processado por sua plataforma de fulfillment. Durante
 
 Quando você estiver pronto para a entrega do pedido, é hora de informar isso à VTEX. Assim, a autorização de pagamento poderá ser capturada e o consumidor será notificado sobre o progresso.
 
-![ERP Orders 3](//images.contentful.com/alneenqid6w5/5UGtFvC0UwoEoEcqQk8kGa/249a691293a7f195257f5c161565cf5c/ERP_Orders_3.png)
+![ERP Orders 3](https://images.contentful.com/alneenqid6w5/5UGtFvC0UwoEoEcqQk8kGa/249a691293a7f195257f5c161565cf5c/ERP_Orders_3.png)
 
 ### Chamadas de API
 
@@ -176,7 +176,7 @@ Não há limite para o número de mensagens de rastreamento que podem ser adicio
 
 É importante ressaltar que essa informação é, na verdade, um conjunto de atributos de uma fatura. Portanto, pode ser enviada junto à fatura, no momento de envio à loja, caso você tenha essa informação nessa etapa.
 
-![ERP Orders 4](//images.contentful.com/alneenqid6w5/1v0Mk0y5a0uAmgcGmgAks4/6d416ec4b79faa89330d683a32c6905c/ERP_Orders_4.png) 
+![ERP Orders 4](https://images.contentful.com/alneenqid6w5/1v0Mk0y5a0uAmgcGmgAks4/6d416ec4b79faa89330d683a32c6905c/ERP_Orders_4.png) 
 
 ### Chamadas de API
 
diff --git a/docs/tutorials/pt/integration-interfaces.md b/docs/tutorials/pt/integration-interfaces.md
index 2a2743a45..8d8c15d4d 100644
--- a/docs/tutorials/pt/integration-interfaces.md
+++ b/docs/tutorials/pt/integration-interfaces.md
@@ -19,7 +19,7 @@ As interfaces de integração permitem realizar o controle de estoque com relaç
 
 No sistema da VTEX, você conseguirá realizar as integrações através de diferentes Interfaces: __API REST__ (linguagem em JSON) e __Web Service__ (linguagem em SOAP - XML) - que está em desuso.
 
-![](//images.contentful.com/alneenqid6w5/KWUcU5mICWqCSgk8moqIa/dab6ed22c22231405712fc87f768450b/V_integra__oERP_docs.png)
+![](https://images.contentful.com/alneenqid6w5/KWUcU5mICWqCSgk8moqIa/dab6ed22c22231405712fc87f768450b/V_integra__oERP_docs.png)
 
 Para que a integração aconteça, é necessário que exista um sistema para fazer a comunicação entre o ERP (ou outros sistemas) e a VTEX. Esse sistema específico é chamado de __Integrador__ ou __Middleware__. Geralmente, o próprio fornecedor do sistema desenvolve seu integrador, mas também pode ser desenvolvido pela própria loja ou por uma agência contratada pela loja.
 
diff --git a/docs/tutorials/pt/integration-with-google-tag-manager.md b/docs/tutorials/pt/integration-with-google-tag-manager.md
index fa2576d0c..9114ab7d2 100644
--- a/docs/tutorials/pt/integration-with-google-tag-manager.md
+++ b/docs/tutorials/pt/integration-with-google-tag-manager.md
@@ -49,7 +49,7 @@ Depois, você deve configurar o código de identificação da loja no Tag Manage
 4. No campo __Google Tag Manager__, insira o código de identificação da loja, no formato `GTM-XXXX`, ilustrado na imagem abaixo.
 5. Clique em `Salvar`. 
 
-![Google Tag Manager](//images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/193fa3039dd13eba99544247affae5a6/Google_Tag_Manager_-_PT.PNG)
+![Google Tag Manager](https://images.ctfassets.net/alneenqid6w5/2AVIJtSgxsTDl4mVRORj41/193fa3039dd13eba99544247affae5a6/Google_Tag_Manager_-_PT.PNG)
 
 Para verificar eventos (acionadores) e variáveis disponíveis nas páginas, que serão usados nas tags, você pode utilizar o modo de visualização do Google Tag Manager. Consulte a [documentação do Google Tag Manager](https://support.google.com/tagmanager/answer/6107056?hl=pt-BR) para mais detalhes.
 
diff --git a/docs/tutorials/pt/integration-with-vtex-tracking.md b/docs/tutorials/pt/integration-with-vtex-tracking.md
index 308d96cee..c1c9673af 100644
--- a/docs/tutorials/pt/integration-with-vtex-tracking.md
+++ b/docs/tutorials/pt/integration-with-vtex-tracking.md
@@ -32,7 +32,7 @@ Há dois cenários de integração:
 * **Integração nativa:** para os pedidos que já estão cadastrados no Gerenciamento de Pedidos do Admin VTEX.  Sua integração ocorre automaticamente após a [instalação do App](#instalacao-do-aplicativo). 
 * **Integração não nativa:** para os pedidos que não estão no Gerenciamento de Pedidos do Admin VTEX. Além da [instalação do App](#instalacao-do-aplicativo) é necessário o cadastro via API ou cadastro pela interface do VTEX Admin (utilizando da função televendas).
 
-![integracao tracking](//images.contentful.com/alneenqid6w5/L4u1MHbVvqNeKovdUv2ve/a9dfb661c1a2ac48b6f9400f75d0eaa8/integracao_tracking.jpg)
+![integracao tracking](https://images.contentful.com/alneenqid6w5/L4u1MHbVvqNeKovdUv2ve/a9dfb661c1a2ac48b6f9400f75d0eaa8/integracao_tracking.jpg)
 
 ## Instalação do aplicativo 
 
diff --git a/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
index 0d9de45b6..7afe5afd8 100644
--- a/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
@@ -32,7 +32,7 @@ As sugestões são exibidas em duas categorias na listagem de sinônimos, confor
 * **Novas sugestões:** sugestões geradas pela plataforma que ainda não foram visualizadas.
 * **Sugestões salvas:** sugestões salvas para depois, como descrito no passo 5 da seção [Revisar sugestões](#revisar-sugestoes).
 
-![synonym-suggestion-list-pt](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
+![synonym-suggestion-list-pt](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
 
 Você pode revisar as sugestões geradas e optar por salvar para depois, recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
 
@@ -48,7 +48,7 @@ Siga as instruções para visualizar as sugestões de sinônimos e definir se el
 
 4. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
 
-   ![synonym-suggestion-pt](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
+   ![synonym-suggestion-pt](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
 
 5. Para revisar cada sugestão, escolha uma das ações a seguir:
 
diff --git a/docs/tutorials/pt/intelligent-synonyms.md b/docs/tutorials/pt/intelligent-synonyms.md
index e410ea991..9ce546f30 100644
--- a/docs/tutorials/pt/intelligent-synonyms.md
+++ b/docs/tutorials/pt/intelligent-synonyms.md
@@ -32,7 +32,7 @@ As sugestões são exibidas em duas categorias na listagem de sinônimos, confor
 * **Novas sugestões:** sugestões geradas pela plataforma que ainda não foram visualizadas.
 * **Sugestões salvas:** sugestões salvas para depois, como descrito no passo 5 da seção [Revisar sugestões](#revisar-sugestoes).
 
-![synonym-suggestion-list-pt](//images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
+![synonym-suggestion-list-pt](https://images.ctfassets.net/alneenqid6w5/YxS5i9kNqByGvZkPXyioK/188a778320a17c36d1af8a39ab15d4f4/synonym-suggestion-list-pt.png)
 
 Você pode revisar as sugestões geradas e optar por salvar para depois, recusar, editar ou aprovar. Confira o passo a passo na seção a seguir.
 
@@ -48,7 +48,7 @@ Siga as instruções para visualizar as sugestões de sinônimos e definir se el
 
 4. Você verá um modal com a primeira sugestão de sinônimo. Cada sugestão indica o termo buscado e o termo que será adicionado como sinônimo, bem como a quantidade de vezes em que clientes da sua loja reescreveram o termo original para o segundo termo nos últimos 30 dias.
 
-   ![synonym-suggestion-pt](//images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
+   ![synonym-suggestion-pt](https://images.ctfassets.net/alneenqid6w5/187mlOYBTMHniFVEJGgUP3/f1e5f45d51ed3d98bd1b85e7ddcbed9e/synonym-suggestion-pt.png)
 
 5. Para revisar cada sugestão, escolha uma das ações a seguir:
 
diff --git a/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md b/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md
index dc515ddb3..a7085388f 100644
--- a/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md
+++ b/docs/tutorials/pt/interacting-with-masterdata-through-graphql.md
@@ -25,7 +25,7 @@ Comece certificando-se de ter a versão mais recente do VTEX CLI e clonando o ap
 
 Execute o comando `vtex init` e selecione `graphql getting-started`.
 
-![Screen Shot 2019-01-16 at 15.00.29](//images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
+![Screen Shot 2019-01-16 at 15.00.29](https://images.ctfassets.net/alneenqid6w5/6Ms4swzkPZ7zdyZyTllB78/f4fde23e90b0f4bc9845cbf86fd83431/Screen_Shot_2019-01-16_at_15.00.29.png)
 
 Vamos usar sua estrutura básica para adaptá-la às nossas necessidades.
 
@@ -155,15 +155,15 @@ Abra o Postman e digite a seguinte pesquisa:
 
 Escolha um ID e copie-o. Vamos colá-lo em nossa consulta.
 
-![Screen Shot 2019-01-16 at 16.14.31](//images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
+![Screen Shot 2019-01-16 at 16.14.31](https://images.ctfassets.net/alneenqid6w5/2eDkOdvUmisBlGWOIDMU5S/b77a875756854e0977c838494a287c14/Screen_Shot_2019-01-16_at_16.14.31.png)
 
-![Screen Shot 2019-01-16 at 17.34.04](//images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
+![Screen Shot 2019-01-16 at 17.34.04](https://images.ctfassets.net/alneenqid6w5/3C82QeSWvvPNjAKTd8TKhC/c89275da1bb55836c3bf10f87d72ae37/Screen_Shot_2019-01-16_at_17.34.04.png)
 
 Agora você deve ver a luz de output à direita.
 Parabéns! Você realizou sua primeira consulta simples em tempo recorde.
 
 Voltando ao terminal, você pode olhar sob o capô e perceber o GraphQL resolvendo as consultas, como normalmente você teria feito.
-![Screen Shot 2019-01-16 at 16.29.03](//images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
+![Screen Shot 2019-01-16 at 16.29.03](https://images.ctfassets.net/alneenqid6w5/38KV7YYgHz8xTcsY18ySPf/e6a33fd274c4f40610e47793ff2ca0d3/Screen_Shot_2019-01-16_at_16.29.03.png)
 
 **Mas e se quisermos pesquisar usando todos os filtros possíveis?**
 Vamos seguir em frente para definir uma nova estrutura de consulta e criar um novo resolver para lidar com os novos parâmetros.
@@ -279,6 +279,6 @@ query{
 
 ```
 
-![Screen Shot 2019-01-16 at 17.23.00](//images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
+![Screen Shot 2019-01-16 at 17.23.00](https://images.ctfassets.net/alneenqid6w5/6Q06UiMGSQVeJjQKpLuant/92de5aeaf26a41b1cffa22603391a834/Screen_Shot_2019-01-16_at_17.23.00.png)
 
 E é isso :)  Happy coding!
diff --git a/docs/tutorials/pt/interaction-details.md b/docs/tutorials/pt/interaction-details.md
index 12237072d..69c09e523 100644
--- a/docs/tutorials/pt/interaction-details.md
+++ b/docs/tutorials/pt/interaction-details.md
@@ -40,7 +40,7 @@ O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="
 </div>
 
 ## Cabeçalho
-![Interaction details PT cabeçalho](//images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/13e23260eaabde52ec1c38246a05be68/Interaction_details_PT_cabe__alho.jpg)
+![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/13e23260eaabde52ec1c38246a05be68/Interaction_details_PT_cabe__alho.jpg)
 O *cabeçalho* traz informações principais do anúncio para rápida visualização, como nome do SKU, logo do canal para onde foi enviado, seu ID na VTEX e ID no canal.
 
 ## Resultado da Interação
@@ -50,26 +50,26 @@ As interações, ou atualizações de  um [anúncio](https://help.vtex.com/pt/tu
 O bloco de *Resultado da Interação* informa o efeito que a interação teve sobre o anúncio, calculado a partir da combinação de registros que formam a interação. O resultado de uma interação faz com o que o sistema determine o status daquele anúncio, indicando se foi possível enviá-lo e sincronizá-lo ao canal, ou não. Resultados das interações incluem: 
 
 ### Resultado: Sucesso
-![Interaction details PT resultado sucesso](//images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/4c0f6f4dacc479647a334304f46156ba/Interaction_details_PT_resultado_sucesso.jpg)
+![Interaction details PT resultado sucesso](https://images.ctfassets.net/alneenqid6w5/72PZOesROTjIZbmFOTQ8jk/4c0f6f4dacc479647a334304f46156ba/Interaction_details_PT_resultado_sucesso.jpg)
 O status de uma interação é *Sucesso* quando interações cumprem com o seu efeito esperado. Isso significa que foi possível enviar o anúncio ao canal corretamente, ou que de fato geraram atualizações em um anúncio em termos de preço, estoque ou catálogo. 
 
 ### Resultado: Falha
-![Interaction details PT resultado falha](//images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/3818ba5ecd25b3aed73ad7c8d27950b3/Interaction_details_PT_resultado_falha.jpg)
+![Interaction details PT resultado falha](https://images.ctfassets.net/alneenqid6w5/1ZR16rSnDEVY0812xY4XFZ/3818ba5ecd25b3aed73ad7c8d27950b3/Interaction_details_PT_resultado_falha.jpg)
 O status de uma interação é *Falha* quando interações não são realizadas por causa de um erro identificado pelo sistema. Resultados desse tipo acabam gerando o status *Erro* em um anúncio, impedindo-o de ser enviado ou atualizado corretamente no canal. 
 
 Caso o resultado da interação seja *Falha*, o bloco aponta uma lista com as falhas detectadas, onde cada uma pode ser expandida para que o seller acesse mais informações sobre o que ocorreu.
 
 ### Resultado: Aviso
-![Interaction details PT resultado aviso](//images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/6eb5baa530de97d609c827f07344eb38/Interaction_details_PT_resultado_aviso.jpg)
+![Interaction details PT resultado aviso](https://images.ctfassets.net/alneenqid6w5/7kwwswW5m4kVL3fXWzxKSV/6eb5baa530de97d609c827f07344eb38/Interaction_details_PT_resultado_aviso.jpg)
 O status de uma interação é *Aviso* quando existem interações que trazem mais visibilidade para as etapas ocorridas no processo de envio e atualização de um anúncio, mas não geraram atualizações de fato.
 
 ### Resultado: Processando
-![Interaction details PT resultado processing](//images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/754b810e1c0feaeed6f79203fab2bea1/Interaction_details_PT_resultado_processing.jpg)
+![Interaction details PT resultado processing](https://images.ctfassets.net/alneenqid6w5/1gilFQQUmLVzTznTQDNv7G/754b810e1c0feaeed6f79203fab2bea1/Interaction_details_PT_resultado_processing.jpg)
 O status de uma interação é *Processando* quando uma interação não foi concluída e ainda deve receber mais ações. Esse é um estado transitório, considerando que quando um evento é fechado, só pode terminar em `sucesso`, `falha`, ou `aviso` como seu resultado. 
 
 ## Linha do tempo
 
-![Interaction details PT linha do tempo](//images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/13786eef8d2ec669080b995324c507d8/Interaction_details_PT_linha_do_tempo.jpg)
+![Interaction details PT linha do tempo](https://images.ctfassets.net/alneenqid6w5/6rLi24P5ltS8XFIEBIn6hb/13786eef8d2ec669080b995324c507d8/Interaction_details_PT_linha_do_tempo.jpg)
 Uma interação é aberta pelo sistema para dar início a uma atualização e contém uma série de registros para realizar as ações necessárias para que isso aconteça. 
 
 A linha do tempo na **Detalhes da interação** organiza cronologicamente os registros que ocorreram dentro de cada interação, sendo que as informações ficam disponíveis para consulta por dez dias. A interação é fechada pelo sistema quando seu objetivo é concluído e não existem mais registros a serem feitos. A linha do tempo da apresenta os seguintes dados:
diff --git a/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
index d226502a3..9bff065ff 100644
--- a/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
@@ -26,7 +26,7 @@ O seguinte conjunto de dados é apresentado na tela de __Todos os pedidos__ na s
 
 Ao lado de cada um desses valores, pode-se ver uma porcentagem que representa a variação relativa aos pedidos feitos no dia de hoje.
 
-![order-metric-pt](//images.ctfassets.net/alneenqid6w5/4H6gLOi9RSYkUG2eIM6Oc2/d6de6b0c59982229df6b5ccc152dd83a/order-metric-pt.png)
+![order-metric-pt](https://images.ctfassets.net/alneenqid6w5/4H6gLOi9RSYkUG2eIM6Oc2/d6de6b0c59982229df6b5ccc152dd83a/order-metric-pt.png)
 
 No screenshot das métricas acima, podemos ver as seguintes informações:
 
diff --git a/docs/tutorials/pt/introduction-to-vtex-apis.md b/docs/tutorials/pt/introduction-to-vtex-apis.md
index 9b6e40f54..1c36f0139 100644
--- a/docs/tutorials/pt/introduction-to-vtex-apis.md
+++ b/docs/tutorials/pt/introduction-to-vtex-apis.md
@@ -62,7 +62,7 @@ Nela devem ser incluídos:
  
 No Postman, a URL deve ser inserida no campo destacado abaixo:
 
-![APIs1](//images.contentful.com/alneenqid6w5/f53Sv9BCZqK4EI0sYmW8A/63e512b825d47daa2f685ae5bb9df553/APIs1.png)
+![APIs1](https://images.contentful.com/alneenqid6w5/f53Sv9BCZqK4EI0sYmW8A/63e512b825d47daa2f685ae5bb9df553/APIs1.png)
 
 ****
 
@@ -80,7 +80,7 @@ Mas você não precisa deduzir isso sozinho. Ao disponibilizar uma API, a VTEX i
  
 No Postman, o método é selecionado à esquerda do campo de URL.
 
-![APIs2](//images.contentful.com/alneenqid6w5/wDClzNRJDiCE6OKecOAs4/8545dbce3bc2ee546b8cf497750360b5/APIs2.png)
+![APIs2](https://images.contentful.com/alneenqid6w5/wDClzNRJDiCE6OKecOAs4/8545dbce3bc2ee546b8cf497750360b5/APIs2.png)
 
 ****
 
@@ -92,7 +92,7 @@ Quando um novo usuário é criado para a sua loja, atribui-se a ele determinado
  
 No postman, a AppKey e o AppToken devem ser inseridos na aba **Headers**. No primeiro header, insira `X-VTEX-API-AppKey` e então sua AppKey. Na segunda linha, insira `X-VTEX-API-AppToken` e então seu AppToken. Para saber como gerar sua AppKey e seu ApToken, leia o artigo [Criar appKey e appToken para autenticar integrações](/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes).
 
-![APIs3](//images.contentful.com/alneenqid6w5/4z9W9DYJEcYa2WGIoSceEE/166d8adc70a8176af1a7fb04e5cdbb65/APIs3.png)
+![APIs3](https://images.contentful.com/alneenqid6w5/4z9W9DYJEcYa2WGIoSceEE/166d8adc70a8176af1a7fb04e5cdbb65/APIs3.png)
 
 ****
 
@@ -110,11 +110,11 @@ As APIs da VTEX estão disponíveis em nosso Help Center, na seção [Developer
  
 Elas ficam divididas por módulo ou funcionalidade. Entrando em um destes, você encontra as APIs correspondentes, cada uma delas acompanhada da indicação do método correto, URL e Headers. Algumas APIs têm também o código que deve ser passado no Body.
  
-![APIs4](//images.contentful.com/alneenqid6w5/1JZCBHsm6UGS2EwuGqoGm4/a61e000b81acd2f06a1021f70c12e31b/APIs4.png)
+![APIs4](https://images.contentful.com/alneenqid6w5/1JZCBHsm6UGS2EwuGqoGm4/a61e000b81acd2f06a1021f70c12e31b/APIs4.png)
  
 À direita dessas indicações, o Postman exibe, para cada API, um Sample Request. De acordo com a linguagem escolhida na caixa de seleção acima dele, o Sample Request mostra como seria a aplicação da requisição no código.
 
-![sample request](//images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
+![sample request](https://images.ctfassets.net/alneenqid6w5/3wK9xsMZmwca8IeygiYOyO/fc875afab27a1abb9c812ec62e511ec9/sample_request.png)
  
 Para algumas APIs, há também uma Sample Response, que é um exemplo de resposta àquele request.
 
diff --git a/docs/tutorials/pt/kit-registration.md b/docs/tutorials/pt/kit-registration.md
index 3c19adcc7..0969fb1da 100644
--- a/docs/tutorials/pt/kit-registration.md
+++ b/docs/tutorials/pt/kit-registration.md
@@ -26,7 +26,7 @@ Um kit pode permitir ou não que seus componentes sejam vendidos separadamente,
 
 Para a configuração do kit é necessário que os produtos que irão fazer parte dele &#8211; seus componentes &#8211; já estejam criados. Confira o exemplo abaixo:
 
-![Componentes](//images.ctfassets.net/alneenqid6w5/6k1lQeZ7AQ4qSQ80sWy0wg/24b2af0e0aa753077e69a3a0a8de7359/Screenshot_2018-10-24_11.05.54.png)
+![Componentes](https://images.ctfassets.net/alneenqid6w5/6k1lQeZ7AQ4qSQ80sWy0wg/24b2af0e0aa753077e69a3a0a8de7359/Screenshot_2018-10-24_11.05.54.png)
 
 Após a criação dos produtos componentes, podemos seguir para a configuração do kit.
 
@@ -37,7 +37,7 @@ Após a criação dos produtos componentes, podemos seguir para a configuração
 5. Caso queira um kit look, clique na opção __Kit com itens vendidos separadamente__.
 6. Clique em `Salvar`.
 
-![kit](//images.ctfassets.net/alneenqid6w5/2ELMh0gTCcSiag28qAsAmg/68fb75589fef19ed4001aec9b3cedfa1/02-kit_PT.png)
+![kit](https://images.ctfassets.net/alneenqid6w5/2ELMh0gTCcSiag28qAsAmg/68fb75589fef19ed4001aec9b3cedfa1/02-kit_PT.png)
 
 ## Associar componentes
 
@@ -52,9 +52,9 @@ Depois de criar o produto que será o kit, você precisa associar os componentes
 7. Preencha o preço unitário do SKU dentro do KIT.
 6. Clique em `Salvar`.
 
-![Adicionar componente ao kit](//images.ctfassets.net/alneenqid6w5/3Cza8qJSEoIK6I00wa2aAU/07caa35d542518e389b66eca48bdffbb/03-add_component_to_kit_PT.gif)
+![Adicionar componente ao kit](https://images.ctfassets.net/alneenqid6w5/3Cza8qJSEoIK6I00wa2aAU/07caa35d542518e389b66eca48bdffbb/03-add_component_to_kit_PT.gif)
 
-![Kit no carrinho](//images.ctfassets.net/alneenqid6w5/239UK8f3gEQi4IKc6YeyEI/0878bffc1325d9c3f79365f7aa479ef8/04-kit_in_cart_ALL.png)
+![Kit no carrinho](https://images.ctfassets.net/alneenqid6w5/239UK8f3gEQi4IKc6YeyEI/0878bffc1325d9c3f79365f7aa479ef8/04-kit_in_cart_ALL.png)
 
 ## Peso do kit
 
@@ -84,7 +84,7 @@ Mas note que alterar qualquer componente irá gerar um novo preço final, atuali
 
 Alterar somente o preço final não atualiza o preço dos componentes.
 
-![Lista de preços](//images.ctfassets.net/alneenqid6w5/6eI3atVTvq0SgOw6c2uAqa/27af79495fd4de8860c36d214196246e/06-price_list_PT.png)
+![Lista de preços](https://images.ctfassets.net/alneenqid6w5/6eI3atVTvq0SgOw6c2uAqa/27af79495fd4de8860c36d214196246e/06-price_list_PT.png)
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
index 183a47239..a369c086a 100644
--- a/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
+++ b/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
@@ -35,7 +35,7 @@ Para configurar o lead time por API, acesse <a href="https://developers.vtex.com
 
 Quando configurado, o lead time é um tempo adicional que compõe o prazo de envio do pedido apresentado ao cliente no checkout. A imagem abaixo apresenta como esse prazo total é composto:
 
-![lead_time_image_total_time_PT](//images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
+![lead_time_image_total_time_PT](https://images.ctfassets.net/alneenqid6w5/WDlW2CzaAKl3KtzzsgGwc/7aae98aad97be4947233c9ef489f266a/lead_time_image_total_time_PT.png)
 
 * **Lead time:** quantidade de tempo configurável para o SKU de um estoque. Este período pode corresponder ao tempo de manipulação ou fabricação do item, por exemplo. Essa configuração é opcional e, por padrão, está definida como zero dias.
 * [Tempo de estoque:](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137) tempo que o SKU leva para sair de um estoque para uma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Essa configuração é obrigatória, mas você pode definir o tempo igual a zero.
@@ -80,7 +80,7 @@ Para configurar o lead time de um SKU, siga os passos abaixo:
 1. No Admin VTEX, acesse **Catálogo > Estoque > Gerenciamento de inventário**, ou digite **Gerenciamento de inventário** na barra de busca no topo da página.
 2. Selecione o SKU do estoque que você deseja configurar. Você pode usar a barra de pesquisa e os filtros de pesquisa.
 3. Na linha do SKU e na coluna **Lead time (dias)**, digite o número de dias desejado.
-  ![lead_time_inventory_management_PT](//images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
+  ![lead_time_inventory_management_PT](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
 4. No canto inferior da página, clique em `Salvar`.
 
 <div class = "alert alert-info">
diff --git a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
index 3b3d316b1..38baf0407 100644
--- a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
+++ b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -48,7 +48,7 @@ Após a criação do cluster, é preciso criar a regra na política comercial pa
 3. No campo **Regra condicional**, preencha com o valor **{NomeDoCluster}=”true”**. O valor **{NomeDoCluster}** deve ser alterado pelo nome do campo na entidade de dados.
 4. Clique no botão **Salvar**.
 
-![Catálogo PT](//images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/739b47fa293440f94bb635d0d90cfbc0/pol__ticas_comerciais_pt.png)
+![Catálogo PT](https://images.ctfassets.net/alneenqid6w5/7r2ANIP2U6JDt1B0dxGmF6/739b47fa293440f94bb635d0d90cfbc0/pol__ticas_comerciais_pt.png)
 
 Na configuração acima, apenas o clientes com o valor true (utilizado um campo boolean – em que os valores são verdadeiro ou falso) acessarão o site.
 
diff --git a/docs/tutorials/pt/linking-an-account-name-to-a-website-binding.md b/docs/tutorials/pt/linking-an-account-name-to-a-website-binding.md
index 3bf530f19..87427c179 100644
--- a/docs/tutorials/pt/linking-an-account-name-to-a-website-binding.md
+++ b/docs/tutorials/pt/linking-an-account-name-to-a-website-binding.md
@@ -20,9 +20,9 @@ Uma das primeiras ações que você precisa realizar em seu web site é vinculá
 1. No Admin VTEX, acesse **Storefront > Layout**.
 2. Clique na pasta __CMS__.
 3. Clique na pasta __Sites and channels__.
-4. Clique no website desejado.![websites](//images.contentful.com/alneenqid6w5/56BRjkYWyIwKogAI0oMmSM/0910a749d03b6fd8d596ce6361a21045/websites.png)
+4. Clique no website desejado.![websites](https://images.contentful.com/alneenqid6w5/56BRjkYWyIwKogAI0oMmSM/0910a749d03b6fd8d596ce6361a21045/websites.png)
 5. Clique em __Save Website__.
-6. Clique em __Add__.![addBinding](//images.contentful.com/alneenqid6w5/r0P8ZE9LNesKoeGewcWOu/527511bc3ae48875fe1a6421a1db5f42/addBinding.png)
-7. Selecione o nome da loja.![chooseBinding](//images.contentful.com/alneenqid6w5/3nFPaDlnaEG2EqIMM8gCe0/188754ebaa172cef01a9212eea168e46/chooseBinding.png)
-8. Marque a política comercial ou as políticas comerciais que ficarão atreladas a essa loja.![bindingSalesPolicy](//images.contentful.com/alneenqid6w5/5FFxnelVTyCu04a6EkiEkS/30905c7f368a1393100f118fd70fcb02/bindingSalesPolicy.png)
+6. Clique em __Add__.![addBinding](https://images.contentful.com/alneenqid6w5/r0P8ZE9LNesKoeGewcWOu/527511bc3ae48875fe1a6421a1db5f42/addBinding.png)
+7. Selecione o nome da loja.![chooseBinding](https://images.contentful.com/alneenqid6w5/3nFPaDlnaEG2EqIMM8gCe0/188754ebaa172cef01a9212eea168e46/chooseBinding.png)
+8. Marque a política comercial ou as políticas comerciais que ficarão atreladas a essa loja.![bindingSalesPolicy](https://images.contentful.com/alneenqid6w5/5FFxnelVTyCu04a6EkiEkS/30905c7f368a1393100f118fd70fcb02/bindingSalesPolicy.png)
 9. Clique em __Save Binding__.
diff --git a/docs/tutorials/pt/linking-urls-to-banners-using-the-site-editor.md b/docs/tutorials/pt/linking-urls-to-banners-using-the-site-editor.md
index 7f7124e74..aa15c852f 100644
--- a/docs/tutorials/pt/linking-urls-to-banners-using-the-site-editor.md
+++ b/docs/tutorials/pt/linking-urls-to-banners-using-the-site-editor.md
@@ -19,7 +19,7 @@ Você pode configurar um dos banners de sua loja para um redirecionamento de pá
 
 ## URLs internas
 
-![url-interna](//images.contentful.com/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/51fc0d948a1b0105ef9d36cb20205e43/Site_Editor_old_PT.png)
+![url-interna](https://images.contentful.com/alneenqid6w5/76tw5q9jP5kqkEhkFMIAOE/51fc0d948a1b0105ef9d36cb20205e43/Site_Editor_old_PT.png)
 
 1. No admin VTEX, acesse **Storefront > Site Editor**.
 2. Selecione o bloco __Carrossel__ desejado e escolha o banner que terá seu conteúdo editado.
@@ -33,7 +33,7 @@ Os campos de <i>Página alvo do banner</i> e  <i>Parâmetros</i> foram descontin
 
 ## URLs externas
 
-![url-externa](//images.contentful.com/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/85299ed51633d217ab446fd73c95d6b4/image4.png)
+![url-externa](https://images.contentful.com/alneenqid6w5/7ESwBk45QYY2eHme82hy1Y/85299ed51633d217ab446fd73c95d6b4/image4.png)
 
 1. No admin VTEX, acesse **Storefront > Site Editor**.
 2. Selecione o bloco __Carrossel__ desejado e escolha o banner que terá seu conteúdo editado.
diff --git a/docs/tutorials/pt/links-suiteshare.md b/docs/tutorials/pt/links-suiteshare.md
index c6fcee9e6..918f53a11 100644
--- a/docs/tutorials/pt/links-suiteshare.md
+++ b/docs/tutorials/pt/links-suiteshare.md
@@ -23,37 +23,37 @@ Pensando nisso e também em aumentar as suas vendas, o VTEX Assisted Sales (Suit
 
 Para criar seu link é muito fácil, acesse seu painel do VTEX Assisted Sales (SuiteShare) e clique em **Atrair** e depois em **Links**.
 
-![Links 1](//images.ctfassets.net/alneenqid6w5/33OwHBb0Nhs6sIGzWSsni5/a2b02a88970460ae4f9864408623e93e/Screenshot_2022-08-26_at_12-51-46_Links.png)
+![Links 1](https://images.ctfassets.net/alneenqid6w5/33OwHBb0Nhs6sIGzWSsni5/a2b02a88970460ae4f9864408623e93e/Screenshot_2022-08-26_at_12-51-46_Links.png)
 
 Clique no botão **Novo**.
 
-![Links 2](//images.ctfassets.net/alneenqid6w5/4tfO1ztHOuGKRLfX3IRPrP/1d794be4a6f244c3a2a937a38a699624/Screenshot_2022-08-26_at_12-51-50_Links.png)
+![Links 2](https://images.ctfassets.net/alneenqid6w5/4tfO1ztHOuGKRLfX3IRPrP/1d794be4a6f244c3a2a937a38a699624/Screenshot_2022-08-26_at_12-51-50_Links.png)
 
 Escolha o País e o DDD do número e insira o número do WhatsApp da sua empresa.
 
-![Links 3](//images.ctfassets.net/alneenqid6w5/4yepQ824DfJ05kAV5na0Ry/1d2b8f92c7ace3f8dd2010243137d56c/Screenshot_2022-08-26_at_12-51-54_Links.png)
+![Links 3](https://images.ctfassets.net/alneenqid6w5/4yepQ824DfJ05kAV5na0Ry/1d2b8f92c7ace3f8dd2010243137d56c/Screenshot_2022-08-26_at_12-51-54_Links.png)
 
 Escolha o endereço do link (URL), você poderá personalizar o domínio do seu link com o nome da sua empresa. Por exemplo: `whts.co/suaempresa`.
 
-![Links 4](//images.ctfassets.net/alneenqid6w5/6YMrf9qg0TFRVWzXWSuSLR/1a88f4096f80889c2636e9e611b595d1/Screenshot_2022-08-26_at_12-52-00_Links.png)
+![Links 4](https://images.ctfassets.net/alneenqid6w5/6YMrf9qg0TFRVWzXWSuSLR/1a88f4096f80889c2636e9e611b595d1/Screenshot_2022-08-26_at_12-52-00_Links.png)
 
 Em seguida, defina a mensagem que irá aparecer pré-digitado para o usuário ao clicar no seu link. Exemplo: _Olá, vi o seu anúncio no Facebook e gostaria de saber mais, meu nome é_.
 
-![Links 5](//images.ctfassets.net/alneenqid6w5/6LwJhOFUAuu6A6UaEGhPN6/bb3682511657bcdf0d23d19d72ab3667/Screenshot_2022-08-26_at_12-52-04_Links.png)
+![Links 5](https://images.ctfassets.net/alneenqid6w5/6LwJhOFUAuu6A6UaEGhPN6/bb3682511657bcdf0d23d19d72ab3667/Screenshot_2022-08-26_at_12-52-04_Links.png)
 
 Opção avançado de mensagem (Não disponível para o plano Free).
 
 Clique em avançado no campo **Mensagem**.
 
-![Links 6](//images.ctfassets.net/alneenqid6w5/J7lvRR5r1pzM0DoV0bkSm/62f679adde4b862f35e84296e3933108/Screenshot_2022-08-26_at_12-54-58_Links.png)
+![Links 6](https://images.ctfassets.net/alneenqid6w5/J7lvRR5r1pzM0DoV0bkSm/62f679adde4b862f35e84296e3933108/Screenshot_2022-08-26_at_12-54-58_Links.png)
 
 Irá abrir as instruções para as configurações avançadas. Tenha mais de uma mensagem no mesmo link. 
 
-![Links 7](//images.ctfassets.net/alneenqid6w5/1jaJc5jFTtiBFL1oWSDkmT/7ca67b4e57b1737ca752ba7a6cd55691/Screenshot_2022-08-26_at_12-55-04_Links.png)
+![Links 7](https://images.ctfassets.net/alneenqid6w5/1jaJc5jFTtiBFL1oWSDkmT/7ca67b4e57b1737ca752ba7a6cd55691/Screenshot_2022-08-26_at_12-55-04_Links.png)
 
 Defina um **Identificador** para localizar o link de forma prática e rápida:
 
-![Links 8](//images.ctfassets.net/alneenqid6w5/1r5L9HK5R3yjE3PrUwlJVi/6b91ff9f4b3522d216bf95304887e767/Screenshot_2022-08-26_at_12-55-08_Links.png)
+![Links 8](https://images.ctfassets.net/alneenqid6w5/1r5L9HK5R3yjE3PrUwlJVi/6b91ff9f4b3522d216bf95304887e767/Screenshot_2022-08-26_at_12-55-08_Links.png)
 
 Esse Identificador é apenas para fins de organização dentro do painel do VTEX Assisted Sales (SuiteShare). 
 
@@ -61,6 +61,6 @@ Feito todas as configurações, clique no botão `Finalizar`. 
 
 Seus links irão para a lista de links. 
 
-![Links 9](//images.ctfassets.net/alneenqid6w5/309KnK9t3XlZihSsDcXOWA/ad95b291308ffa4f007b944c8e9b4685/Screenshot_2022-08-26_at_16-29-16_Links.png)
+![Links 9](https://images.ctfassets.net/alneenqid6w5/309KnK9t3XlZihSsDcXOWA/ad95b291308ffa4f007b944c8e9b4685/Screenshot_2022-08-26_at_16-29-16_Links.png)
 
 [Quer saber onde utilizar os links criados? Criamos um artigo que vai te explicar tudo.](https://help.vtex.com/pt/faq/onde-utilizar-o-link-de-whatsapp--6VbyH573udBQJ3j7kfsWeJ)
diff --git a/docs/tutorials/pt/list-the-account-workspaces.md b/docs/tutorials/pt/list-the-account-workspaces.md
index 3d11a05d8..186af4e79 100644
--- a/docs/tutorials/pt/list-the-account-workspaces.md
+++ b/docs/tutorials/pt/list-the-account-workspaces.md
@@ -21,7 +21,7 @@ Toda conta pode ter vários workspaces. Para ver os workspaces que existem atual
 
 Veja um exemplo abaixo:
 
-![workspace list](//images.contentful.com/alneenqid6w5/2au4D7r6YkmskO0Ko8esC6/aa635baf0e6f543c0e08ee2613e20127/workspace_list.png)
+![workspace list](https://images.contentful.com/alneenqid6w5/2au4D7r6YkmskO0Ko8esC6/aa635baf0e6f543c0e08ee2613e20127/workspace_list.png)
 
 As colunas que aparecem são as seguintes:
 
diff --git a/docs/tutorials/pt/lista-da-vez.md b/docs/tutorials/pt/lista-da-vez.md
index 9d8a60731..d358a427f 100644
--- a/docs/tutorials/pt/lista-da-vez.md
+++ b/docs/tutorials/pt/lista-da-vez.md
@@ -30,7 +30,7 @@ O aplicativo **Lista da Vez** permite organizar a fila de atendimento dos vended
 
 A aba Lista da Vez gerencia a ordem de atendimento dos vendedores da loja. Além de ordenar a fila de atendimento, também é possível identificar a situação de cada vendedor: [Esperando a vez](#esperando-a-vez), [Em atendimento](#em-atendimento) e [Fora da loja](#fora-da-loja).
 
-![lista-da-vez-PT](//images.ctfassets.net/alneenqid6w5/0hiWrn69rcSgwI8yHktBG/c13ca4d30a1c3aa36d7dbe117890dfcd/Screenshot_20220211-131959_DuckDuckGo.jpg)
+![lista-da-vez-PT](https://images.ctfassets.net/alneenqid6w5/0hiWrn69rcSgwI8yHktBG/c13ca4d30a1c3aa36d7dbe117890dfcd/Screenshot_20220211-131959_DuckDuckGo.jpg)
 
 ### Esperando a vez
 Nesta seção, os vendedores da loja estarão listados em ordem de atendimento. Para adicionar um vendedor na fila, arraste o vendedor para a coluna **Esperando a vez**.
@@ -81,12 +81,12 @@ Clique em `Concluir` para finalizar.
 ## Campanhas
 Nesta aba você pode visualizar as campanhas configuradas na plataforma da Indeva. Uma campanha é um desafio de metas para os vendedores da loja. Nela será exibida a condição da campanha, a premiação para quem completá-la e a posição dos vendedores em relação à condição.
 
-![campanha-PT](//images.ctfassets.net/alneenqid6w5/WDPAVhqCaRb5mzkNdH9Je/8dd97addafdff96674c48d74765b4f76/Screenshot_20220215-112922_Ecosia.jpg)
+![campanha-PT](https://images.ctfassets.net/alneenqid6w5/WDPAVhqCaRb5mzkNdH9Je/8dd97addafdff96674c48d74765b4f76/Screenshot_20220215-112922_Ecosia.jpg)
 
 ## Rankings
 Nesta aba serão exibidos os rankings dos vendedores da loja configurados na plataforma  da Indeva. Um ranking é uma classificação a partir de uma condição definida pela loja, com regras para os vendedores participarem e uma premiação para o primeiro colocado. 
 
-![rankings-PT](//images.ctfassets.net/alneenqid6w5/7sieBaz6E1RJHQLmr0TOIp/47259a247043f1806a98c465efd73f78/Screenshot_20220215-112727_Ecosia.jpg)
+![rankings-PT](https://images.ctfassets.net/alneenqid6w5/7sieBaz6E1RJHQLmr0TOIp/47259a247043f1806a98c465efd73f78/Screenshot_20220215-112727_Ecosia.jpg)
 
 ## Metas
 A página de Metas exibe as metas e o desempenho de um vendedor, cadastradas na plataforma da Indeva. Para acessar uma meta individual, siga os passos abaixo.
@@ -96,7 +96,7 @@ A página de Metas exibe as metas e o desempenho de um vendedor, cadastradas na
 3. Insira a senha de acesso do vendedor.
 4. Clique em `Entrar`.
 
-![metas-PT](//images.ctfassets.net/alneenqid6w5/eSRDRLRc6bkfoAylfMQLY/f8bdb99f379d377be82c8bd39464a08d/Screenshot_20220216-124454_Ecosia.jpg)
+![metas-PT](https://images.ctfassets.net/alneenqid6w5/eSRDRLRc6bkfoAylfMQLY/f8bdb99f379d377be82c8bd39464a08d/Screenshot_20220216-124454_Ecosia.jpg)
 
 Nesta página você pode visualizar as seguintes informações:
 
diff --git a/docs/tutorials/pt/listing-apps-installed-in-the-store.md b/docs/tutorials/pt/listing-apps-installed-in-the-store.md
index 7c6b5cef6..0f6c5f6d0 100644
--- a/docs/tutorials/pt/listing-apps-installed-in-the-store.md
+++ b/docs/tutorials/pt/listing-apps-installed-in-the-store.md
@@ -26,6 +26,6 @@ Você verá uma tabela com as seguintes colunas:
 - __Version__: versão da app.
 - __Linked__: mostra se a app está ou não linkada.
 
-![appList](//images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
+![appList](https://images.contentful.com/alneenqid6w5/23dywoz95GmeAOkuwe8WWq/d1097f363859c30abd67e699fa0d23ed/appList.png)
 
 Não há limite de apps que podem ser criadas para uma conta.
diff --git a/docs/tutorials/pt/loading-dock.md b/docs/tutorials/pt/loading-dock.md
index 6f9fbd229..954eee468 100644
--- a/docs/tutorials/pt/loading-dock.md
+++ b/docs/tutorials/pt/loading-dock.md
@@ -19,7 +19,7 @@ A doca é parte do sistema logístico e geralmente funciona como ponto intermedi
 
 Na VTEX, a doca é um intermediador entre o armazenamento de itens e a entrega dos pedidos do seu negócio. É pela doca que ocorre a integração das partes necessárias para a logística da sua loja: [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb),  [Política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) e [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 
-![Doca PT](//images.contentful.com/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/b26625a316028e55b1f15c0c7e3433ee/Doca_PT.svg)
+![Doca PT](https://images.contentful.com/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/b26625a316028e55b1f15c0c7e3433ee/Doca_PT.svg)
 
 <div class = "alert alert-info">
 O Estoque é o espaço físico de armazenamento das mercadorias vendidas pela loja; a Política comercial é a configuração das estratégias de venda da loja; e a Política de envio é um conjunto de regras que definem as opções e condições de frete.
diff --git a/docs/tutorials/pt/locations-details-page-beta.md b/docs/tutorials/pt/locations-details-page-beta.md
index 1310aadfa..4c5744f39 100644
--- a/docs/tutorials/pt/locations-details-page-beta.md
+++ b/docs/tutorials/pt/locations-details-page-beta.md
@@ -21,7 +21,7 @@ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando
 
 No [módulo Localidades](https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy) do seu Admin VTEX, em **Envio > Localidades**, ao clicar sobre uma localidade você é direcionado para sua página de detalhes, como a imagem a seguir:
 
-![pagina_detalhes_image_1_PT](//images.ctfassets.net/alneenqid6w5/6fehx8bwcHLXGXZFALiGSR/4fe303ef087c40b1eb7147ac39a949de/pagina_detalhes_image_1_PT.png)
+![pagina_detalhes_image_1_PT](https://images.ctfassets.net/alneenqid6w5/6fehx8bwcHLXGXZFALiGSR/4fe303ef087c40b1eb7147ac39a949de/pagina_detalhes_image_1_PT.png)
 
 No topo da página, existe o diagrama **Status da capacidade operacional**, que apresenta em tempo real a porcentagem da capacidade da localidade que já foi consumida. O diagrama apresenta os seguintes períodos:
 
@@ -47,11 +47,11 @@ Para ver todas as ações que você pode realizar com localidades, veja o artigo
 
 Nos detalhes da localidade, é possível acompanhar o registro de todas as ações executadas pelo sistema ou por um usuário. Para isso, no topo da página, clique em `Ver histórico`:
 
-![pagina_detalhes_image_2_PT](//images.ctfassets.net/alneenqid6w5/31OXQKO48e7bRiNn5HptZF/610023d778dd4ae1442321f20365379c/pagina_detalhes_image_2_PT.png)
+![pagina_detalhes_image_2_PT](https://images.ctfassets.net/alneenqid6w5/31OXQKO48e7bRiNn5HptZF/610023d778dd4ae1442321f20365379c/pagina_detalhes_image_2_PT.png)
 
 Você será redirecionado para o **Histórico da capacidade operacional** da localidade, conforme a imagem abaixo:
 
-![pagina_detalhes_image_3_PT](//images.ctfassets.net/alneenqid6w5/6r91diwK9rP2LVMz1qOweq/007aa6776d06df12dd56a37269e53389/pagina_detalhes_image_3_PT.png)
+![pagina_detalhes_image_3_PT](https://images.ctfassets.net/alneenqid6w5/6r91diwK9rP2LVMz1qOweq/007aa6776d06df12dd56a37269e53389/pagina_detalhes_image_3_PT.png)
 
 Nesta tela, você pode:
 
@@ -63,11 +63,11 @@ Nesta tela, você pode:
 
 Quando uma localidade atinge <i class="fas fa-exclamation-triangle"></i> 100% da sua capacidade, a página de detalhes oferece uma outra opção de como aumentar essa capacidade, clicando em `Aumentar capacidade`, conforme imagem abaixo:
 
-![pagina_detalhes_image_4_PT](//images.ctfassets.net/alneenqid6w5/3AhCW3Psea1eTlcGMZ51im/eee4c4f097cd862b465cdf5fcf9b2e00/pagina_detalhes_image_4_PT.png)
+![pagina_detalhes_image_4_PT](https://images.ctfassets.net/alneenqid6w5/3AhCW3Psea1eTlcGMZ51im/eee4c4f097cd862b465cdf5fcf9b2e00/pagina_detalhes_image_4_PT.png)
 
 Feito isso, será apresentado o modal **Aumentar capacidade**, como a imagem a seguir:
 
-![pagina_detalhes_image_5_PT](//images.ctfassets.net/alneenqid6w5/625fjXiFlU5wtL9ySZnVT4/c397d8c8e496642061cbf880d7d1736f/pagina_detalhes_image_5_PT.png)
+![pagina_detalhes_image_5_PT](https://images.ctfassets.net/alneenqid6w5/625fjXiFlU5wtL9ySZnVT4/c397d8c8e496642061cbf880d7d1736f/pagina_detalhes_image_5_PT.png)
 
 Você pode configurar qual será o valor da nova capacidade e definir o período para o qual deseja aplicar a mudança. As opções são as seguintes:
 
diff --git a/docs/tutorials/pt/log-in-to-the-account.md b/docs/tutorials/pt/log-in-to-the-account.md
index 1a8cc69ee..b48daa9e9 100644
--- a/docs/tutorials/pt/log-in-to-the-account.md
+++ b/docs/tutorials/pt/log-in-to-the-account.md
@@ -21,6 +21,6 @@ Para fazer login na conta da loja, entre no terminal e digite:
 
 O terminal vai solicitar o Account, ou seja, o nome da conta da loja.
 
-![vtex login](//images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
+![vtex login](https://images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
 
 Após inserir o Account, digite a senha, se necessário, e pronto. Você fez login na sua conta!
diff --git a/docs/tutorials/pt/logging-in-to-the-account-with-vtex-io.md b/docs/tutorials/pt/logging-in-to-the-account-with-vtex-io.md
index 793c956fd..7d97541ea 100644
--- a/docs/tutorials/pt/logging-in-to-the-account-with-vtex-io.md
+++ b/docs/tutorials/pt/logging-in-to-the-account-with-vtex-io.md
@@ -19,7 +19,7 @@ Para fazer login na conta da loja, entre no terminal e digite `vtex login`.
 
 O terminal vai solicitar o Account, ou seja, o nome da conta da loja desejada.
 
-![vtex login](//images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
+![vtex login](https://images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
 
 Após inserir o Account, basta informar a senha, se necessário, e pronto. Você fez login na sua conta!
 
diff --git a/docs/tutorials/pt/logistics-in-the-grocery-segment-supermarkets.md b/docs/tutorials/pt/logistics-in-the-grocery-segment-supermarkets.md
index e005133fe..f65e8a1e5 100644
--- a/docs/tutorials/pt/logistics-in-the-grocery-segment-supermarkets.md
+++ b/docs/tutorials/pt/logistics-in-the-grocery-segment-supermarkets.md
@@ -27,7 +27,7 @@ O fulfillment nada mais é do que o processo da análise dos pedidos, separaçã
 
 Na maioria das operações convencionais de e-commerce, temos um armazém que representa o estoque. Já na maioria das operações de grocery, esse armazém não é praticado devido à perecibilidade, rápido detrimento das mercadorias (validade) e a grande variedade do mix de produtos.
 
-![](//images.contentful.com/alneenqid6w5/5VsYaqLOz6iq2Q6KEGiOIw/ccca0432aef12d539de3d6d9301383df/mapaARMAZEM1.jpg)
+![](https://images.contentful.com/alneenqid6w5/5VsYaqLOz6iq2Q6KEGiOIw/ccca0432aef12d539de3d6d9301383df/mapaARMAZEM1.jpg)
 
 Neste contexto, para a existência de um armazém que represente o estoque é praticamente necessário o dobro do espaço físico e um grande fluxo de pedidos para escoamento antes do detrimento dos produtos.
 Para evitar esta custosa e complexa operação, os grocerys de modo geral, utilizam os próprios pdvs como fonte de estoque, ou seja, os produtos que estão nas gôndolas são os produtos que alimentam o estoque da loja virtual. 
@@ -58,7 +58,7 @@ A partir de volumes medianos (acima de 30 pedidos diários) o método de picking
 
 Pode-se realizar essas ondas por transportadora, rotas, docas ou lote.
 
-![](//images.contentful.com/alneenqid6w5/5rrGJF8WL60uOmgeEia08o/5b66179fe04f4fd6c1cddcd9c12f774f/pickingonda2.jpg)
+![](https://images.contentful.com/alneenqid6w5/5rrGJF8WL60uOmgeEia08o/5b66179fe04f4fd6c1cddcd9c12f774f/pickingonda2.jpg)
 
 ## Picking _por onda lote_ favorece o Packing
 
@@ -72,7 +72,7 @@ Devido aos diferentes tipos de mercadorias vendáveis no grocery, podemos atribu
 6. Frágeis
 7. Congelados
 
-![](//images.contentful.com/alneenqid6w5/tepJVna9uoiKUqeUeOQM4/e9b1e3bca826f9a4bb8f662d34108339/mapa.jpg)
+![](https://images.contentful.com/alneenqid6w5/tepJVna9uoiKUqeUeOQM4/e9b1e3bca826f9a4bb8f662d34108339/mapa.jpg)
 
 Além de ser imprescindível para a separação, o lote é muito importante no packing, uma vez que os tipos de lotes tem necessidades características e particulares:
 
@@ -91,7 +91,7 @@ Exemplos: Ovos, Frutas, bomboniere, batatas etc.
 **7. (Congelados):** Devem ser transportados em caixas térmicas, em até 6 horas são conservados com o auxílio de blocos de gelos, estes gelos devem estar preferencialmente em recipientes plásticos fechados para evitar o envolvimento com água e reaproveitamento do insumo.
 Exemplos: Sorvetes, sobremesas, empanados, pratos prontos, hambúrgueres, petiscos e etc.
 
-![](//images.contentful.com/alneenqid6w5/ptgKUEgHBu4syuiuS46mS/ae31c4cbd90a04a8d0dc19a3e2a6b669/packing.jpg)
+![](https://images.contentful.com/alneenqid6w5/ptgKUEgHBu4syuiuS46mS/ae31c4cbd90a04a8d0dc19a3e2a6b669/packing.jpg)
 
 ## Despacho, transporte e entrega
 
diff --git a/docs/tutorials/pt/logistics-module-overview.md b/docs/tutorials/pt/logistics-module-overview.md
index 5e3b5bb51..b323337f8 100644
--- a/docs/tutorials/pt/logistics-module-overview.md
+++ b/docs/tutorials/pt/logistics-module-overview.md
@@ -27,7 +27,7 @@ Onde é possível cadastrar a relação de **[Estoque](https://help.vtex.com/pt
 
 Onde é cadastrada a definição de valores de preço e tempo de entrega para uma determinada faixa de CEP em relação ao peso cúbico do produto, dimensões, entre outros fatores.
 
-![tarifas-envioPT](//images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/7a4f1f361c762cc7efa4f283f5e496e7/tarifas_envio.png)
+![tarifas-envioPT](https://images.ctfassets.net/alneenqid6w5/6BuxCyz2bujSpqx9Mq0CcZ/7a4f1f361c762cc7efa4f283f5e496e7/tarifas_envio.png)
 - [Tarifas de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM)
 
 ## Simulador de envio
@@ -36,35 +36,35 @@ Aqui será possível realizar uma simulação de frete e reproduzir diversos ce
 
 Este retornará os valores e as transportadoras que atendem à entrega, as dimensões e pesos dos produtos, o preço da entrega e o tempo estimado para ser realizada. Além dos detalhes adicionais sobre os valores da faixa do CEP, percentuais que variam de acordo com a faixa de peso do produto, volume, valores adicionais por grama excedente, custo para a doca, fator cúbico e peso cubado.
 
-![simulador envio](//images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/d3a55f4de664d821c427933224346b54/simulador_envio.png)
+![simulador envio](https://images.ctfassets.net/alneenqid6w5/5Chp5OU2vGVkHDXtQEayoL/d3a55f4de664d821c427933224346b54/simulador_envio.png)
 - [Simulação de Frete](http://help.vtex.com/pt/tutorial/simulacao-de-frete)
 
 ## Inventário
 
 Local para gerenciar e acompanhar a movimentação de estoque realizada nos produtos da loja. Tanto quanto as reservas que o produto possui naquele momento e se já foram confirmadas ou não.
 
-![gerenciar inventario](//images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/c455c47a1c937d068901baee81e7cfd3/gerenciar_inventario.png)
+![gerenciar inventario](https://images.ctfassets.net/alneenqid6w5/7DXfGBySZsZmejB31WQBRK/c455c47a1c937d068901baee81e7cfd3/gerenciar_inventario.png)
 - [Gerenciar Inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139)
 
 ## Envio por geolocalização
 
 Geolocalização é o cadastro das localizações de entrega a partir da latitude e longitude dos endereços. Aqui é permitido criar “polígonos” para um atendimento logístico específico, normalmente utilizado em zonas rurais e industriais, onde se há a divisão por lotes, por exemplo, ou em áreas de risco, onde se faz necessário excluir determinados locais dentro de uma mesma região. 
 
-![geolocalizaçao](//images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/f3596617d3f5ba0bc5219ddd7515074f/geolocaliza__ao.png)
+![geolocalizaçao](https://images.ctfassets.net/alneenqid6w5/4UrlnVmhHGhR2XEWU8bOwx/f3596617d3f5ba0bc5219ddd7515074f/geolocaliza__ao.png)
 - [Geolocalização](http://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao)
 
 ## Pontos de retirada
 
 Em Pontos de retirada é possível excluir, editar e cadastrar um *Pickup Point*. Junto ao tradicinal "delivery" (entrega em domicílio), a feature de Pontos de Retirada agrega maior flexibilidade e melhor experiência de compra para o cliente ao permitir a ele a retirada do pedido em um ponto físico. 
 
-![pontos retirada](//images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/4437f547b06d579f64ec05cabdb32356/pontos_retirada.png)
+![pontos retirada](https://images.ctfassets.net/alneenqid6w5/t58ChaH55346tKGLDD1wu/4437f547b06d579f64ec05cabdb32356/pontos_retirada.png)
 
 - [Configurar Pontos de Retirada](http://help.vtex.com/pt/tutorial/configurar-pontos-de-retirada-pickup-points) 
 ## Feriados
 
 Aqui é possivel cadastrar os dias que **não** serão considerados como úteis para a sua loja. O módulo irá considerar os feriado cadastrados no cálculo de entrega dos pedido e esses dias não serâo contabilizados no prazo de entrega. 
 
-![feriado](//images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/89ac9ae473a1696eef05c80e214b3f66/feriado.png)
+![feriado](https://images.ctfassets.net/alneenqid6w5/naLgWqy2UVusNnzG9FdUc/89ac9ae473a1696eef05c80e214b3f66/feriado.png)
 - [Cadastrar Feriado](http://help.vtex.com/pt/tutorial/cadastrar-feriados)
 
 ## Configurações
diff --git a/docs/tutorials/pt/magento-suiteshare.md b/docs/tutorials/pt/magento-suiteshare.md
index 7f11985f0..7a58e919b 100644
--- a/docs/tutorials/pt/magento-suiteshare.md
+++ b/docs/tutorials/pt/magento-suiteshare.md
@@ -21,7 +21,7 @@ No Painel de Controle do **Magento**, acesse o menu **Sistema** e clique em 
 
 Na página seguinte, selecione **Visual** (Design) e então clique em **Cabeçalho HTML**:
 
-![Magento_Suiteshare](//images.ctfassets.net/alneenqid6w5/7DnzVtmv6u7rjlUD8iyVXJ/92ff4b0de0ffee721d9307ccdd991a3d/Magento_Suiteshare.png)
+![Magento_Suiteshare](https://images.ctfassets.net/alneenqid6w5/7DnzVtmv6u7rjlUD8iyVXJ/92ff4b0de0ffee721d9307ccdd991a3d/Magento_Suiteshare.png)
 
 Desça na página até encontrar o campo **Outros Scripts** e cole o código do VTEX Assisted Sales (SuiteShare) dentro dele. Não se esqueça de salvar as mudanças clicando no botão **Salvar Configurações**.
 
diff --git a/docs/tutorials/pt/making-a-master-data-field-editable.md b/docs/tutorials/pt/making-a-master-data-field-editable.md
index ccc5385cc..af01f48fb 100644
--- a/docs/tutorials/pt/making-a-master-data-field-editable.md
+++ b/docs/tutorials/pt/making-a-master-data-field-editable.md
@@ -23,7 +23,7 @@ Por padrão, nem todos os campos são editáveis no Master Data. Para alterar es
 2. Na aplicação desejada, clique no símbolo de engrenagem <i class="fas fa-cog"></i>.
 3. Clique no ícone de edição  <i class="fas fa-edit"></i>  no formulário que deseja alterar.
 4. Clique na aba **Esquemas de layout**.
-5. No campo desejado, clique no ícone de edição <i class="fas fa-edit"></i>. ![master-data-editar-campo-layout](//images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/27db047819bc08ee9d597da18aed6c7f/Group_3.png)
+5. No campo desejado, clique no ícone de edição <i class="fas fa-edit"></i>. ![master-data-editar-campo-layout](https://images.ctfassets.net/alneenqid6w5/3zHKQ7fVCwqi4CIWqumYC/27db047819bc08ee9d597da18aed6c7f/Group_3.png)
 6. Desmarque a opção **Exibir campos de somente leitura**.
 7. Clique no botão `OK`.
 8. Clique no botão `Salvar`.
diff --git a/docs/tutorials/pt/manage-the-sales-comissions-report.md b/docs/tutorials/pt/manage-the-sales-comissions-report.md
index c2963f688..c2a5c0d81 100644
--- a/docs/tutorials/pt/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/pt/manage-the-sales-comissions-report.md
@@ -63,7 +63,7 @@ A criação do relatório pode demorar caso o volume de dados analisados seja ex
 Sair da página não afetará a operação.
 </div>
 
-![comissionamento PT](//images.ctfassets.net/alneenqid6w5/7bWvI8TAgRPvtF4kr00TbC/6a3805d30656ad30c9afae6cb3079fce/comissionamento_PT.png)
+![comissionamento PT](https://images.ctfassets.net/alneenqid6w5/7bWvI8TAgRPvtF4kr00TbC/6a3805d30656ad30c9afae6cb3079fce/comissionamento_PT.png)
 
 Posteriormente, você também pode baixar o relatório recém-gerado em um link para download disponibilizado na listagem de relatórios.  
 
diff --git a/docs/tutorials/pt/managing-b2b-organizations.md b/docs/tutorials/pt/managing-b2b-organizations.md
index b04302e6a..baa5b5a8e 100644
--- a/docs/tutorials/pt/managing-b2b-organizations.md
+++ b/docs/tutorials/pt/managing-b2b-organizations.md
@@ -47,7 +47,7 @@ Cada organização pode ter um dos seguintes status:
 
 - **Inativo:** a organização foi desativada pelos administradores da loja, portanto, seus usuários não poderão fazer login.
 
-![Status- PT](//images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/4e8ec550596a86988e076707f570dc6e/Status-_PT.gif)
+![Status- PT](https://images.ctfassets.net/alneenqid6w5/2UywOtrYrvizJEY5LjQgau/4e8ec550596a86988e076707f570dc6e/Status-_PT.gif)
 
 ## Adicionar uma nova organização
 
@@ -73,7 +73,7 @@ Para adicionar uma nova organização, siga os passos abaixo:
     - **Destinatário:** nome da pessoa que receberá os pedidos no endereço informado.
 4. Clique em `Adicionar`.
 
-![Adiconar organização- PT](//images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/c0e63411db1ab4a2fd44b4592d4aeffd/Adiconar_organiza__o-_PT.gif)
+![Adiconar organização- PT](https://images.ctfassets.net/alneenqid6w5/7vp9NX3NLvSWErVBlYzbNI/c0e63411db1ab4a2fd44b4592d4aeffd/Adiconar_organiza__o-_PT.gif)
 
 ## Notificações por emails
 
diff --git a/docs/tutorials/pt/managing-credit-with-customer-credit.md b/docs/tutorials/pt/managing-credit-with-customer-credit.md
index 99891702d..069998c52 100644
--- a/docs/tutorials/pt/managing-credit-with-customer-credit.md
+++ b/docs/tutorials/pt/managing-credit-with-customer-credit.md
@@ -69,11 +69,11 @@ Para um número reduzido de cadastros, o cliente pode criar as contas uma a uma
 - E-mail
 - Limite de crédito
 
-![CustomerCredit1](//images.ctfassets.net/alneenqid6w5/4qFEtQ96Ylr6isBrULX16Z/30921e212931852bc69c66e6d2cef62c/CustomerCredit1.png)
+![CustomerCredit1](https://images.ctfassets.net/alneenqid6w5/4qFEtQ96Ylr6isBrULX16Z/30921e212931852bc69c66e6d2cef62c/CustomerCredit1.png)
 
 Se, por outro lado, a base tem um número grande de contas, o mais indicado é importar uma planilha em formato CSV. Você pode baixar um modelo desse documento na seção Contas e preenchê-lo com as informações necessárias. Para isso, clique no botão __Importar__.
 
-![CustomerCredit2](//images.ctfassets.net/alneenqid6w5/3Gjxyu2UOkyg7T31tpEKcW/3387e9b15b3fe91842ea4db1a714c17a/CustomerCredit2.png)
+![CustomerCredit2](https://images.ctfassets.net/alneenqid6w5/3Gjxyu2UOkyg7T31tpEKcW/3387e9b15b3fe91842ea4db1a714c17a/CustomerCredit2.png)
 
 ### Grandes bases
 
diff --git a/docs/tutorials/pt/managing-page-and-template-content.md b/docs/tutorials/pt/managing-page-and-template-content.md
index 297423d46..2f787743f 100644
--- a/docs/tutorials/pt/managing-page-and-template-content.md
+++ b/docs/tutorials/pt/managing-page-and-template-content.md
@@ -30,7 +30,7 @@ Exercite sua autonomia sobre o código e construa o cenário de loja desejado de
 
 1. Selecione o bloco para o qual deseja criar um novo conteúdo. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface-pt](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
+![seta-interface-pt](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
 
 2. Clique em `Versões` no canto superior direito.
 
@@ -58,7 +58,7 @@ O Site Editor aplica configurações de conteúdo de acordo com a hierarquia de
 
 1. Selecione o bloco desejado cujo conteúdo será sobrescrito. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface-pt](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
+![seta-interface-pt](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
 
 2. O conteúdo disponível é o ativo vigente. Edite os campos com os novos valores ou clique em `Versões` para editar as configurações de outros conteúdos.
 3. Salve suas alterações.
@@ -71,7 +71,7 @@ Os conteúdos derivados do Store Theme não podem ter sua visibilidade atualizad
 
 1. Selecione o bloco desejado cujo conteúdo será excluído ou redefinido. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface-pt](//images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
+![seta-interface-pt](https://images.ctfassets.net/alneenqid6w5/5Jy42Ht1E66ETZf4Beiv85/533c69a0cd05f2a0c88e6df83ce13615/img-two.png)
 
 2. Clique em `Versões` no canto superior direito.
 3. Clique no menu kebab do conteúdo desejado (três pontos).
diff --git a/docs/tutorials/pt/managing-pages.md b/docs/tutorials/pt/managing-pages.md
index 1d5b407b2..29f36f95a 100644
--- a/docs/tutorials/pt/managing-pages.md
+++ b/docs/tutorials/pt/managing-pages.md
@@ -19,7 +19,7 @@ No **Headless CMS**, você pode gerenciar todas as rotas de URL e modelos de pá
 
 ## Visão geral
 
-![Novas páginas ](//images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/5e6068b5ae50645a857916be2d6e7caa/novas_pgs._pt.png)
+![Novas páginas ](https://images.ctfassets.net/alneenqid6w5/7cftK7sS2epeqGjY6m0Cmj/5e6068b5ae50645a857916be2d6e7caa/novas_pgs._pt.png)
 
 | Opção               | Descrição                                              |
 | ------------------- | ------------------------------------------------------ |
@@ -42,7 +42,7 @@ Para criar e gerenciar uma página, siga estas etapas:
 3. Em `Untitled`, nomeie a página.
 
 4. Clique em **Seções** e selecione a seção desejada.
-![Gif - páginas disponíveis](//images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/3934fab358660137fdd190830e77dc80/Portugu__s_gif_das_paginas.gif)
+![Gif - páginas disponíveis](https://images.ctfassets.net/alneenqid6w5/1JOLEO3RErUiJ8AYroKwTe/3934fab358660137fdd190830e77dc80/Portugu__s_gif_das_paginas.gif)
 5. Adicione mais seções, se necessário, e preencha-as.
 
 6. Clique em `Publicar`.
diff --git a/docs/tutorials/pt/managing-placeholders.md b/docs/tutorials/pt/managing-placeholders.md
index 1354c3c87..c94fc3a40 100644
--- a/docs/tutorials/pt/managing-placeholders.md
+++ b/docs/tutorials/pt/managing-placeholders.md
@@ -35,7 +35,7 @@ O que ele faz é criar um elemento configurável no local do código onde for in
 
 É importante inserir um valor de `id`. Este será o identificador desse placeholder no sistema.
 
-![6 1](//images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
+![6 1](https://images.ctfassets.net/alneenqid6w5/5TcE6FWxp9xwmSl2fQCYMa/bb0a3544af3d95d1d59e9f484ba61984/6_1.png)
 
 ### Configurando o placeholder
 
@@ -43,7 +43,7 @@ Agora que o controle de placeholder foi inserido no template, vamos configurá-l
 
 Isso é feito nas configurações do layout que usa esse template.
 
-1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](//images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
+1. Abra o layout e depois clique na aba **Settings**. O novo placeholder deve aparecer aí, com o nome igual ao valor do id definido no controle. Por enquanto, esse placeholder está vazio, ou seja, não há nenhum objeto dentro dele.![6 2](https://images.ctfassets.net/alneenqid6w5/3sr9POkZJdqXMiUC45nIeZ/440a22c2e88050d9b1e82cfe155938e9/6_2.png)
 2. Para inserir um objeto, clique em **add object**. 
 3. Em seguida, escolha o tipo de objeto e clique em **Adicionar**.
 4. Por fim, clique no botão **Save Settings**, no alto da página.
@@ -52,7 +52,7 @@ Agora você já pode editar o objeto inserido no placeholder.
 
 Para isso, clique no lápis dentro do objeto e, em seguida, clique em **add content**.
 
-![6 3](//images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
+![6 3](https://images.ctfassets.net/alneenqid6w5/4Mgr9vmPRKmzTGu7ntH6u6/201c7b83ce8cef556a4a802b5a457359/6_3.png)
 
 Agora você pode definir o nome desse objeto, subir imagens para ele e configurar as condições em que ele vai ser renderizado, tais como o período. 
 
diff --git a/docs/tutorials/pt/managing-projects.md b/docs/tutorials/pt/managing-projects.md
index 2d7425f62..6a3a7652d 100644
--- a/docs/tutorials/pt/managing-projects.md
+++ b/docs/tutorials/pt/managing-projects.md
@@ -17,7 +17,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 
 Projetos é uma funcionalidade do VTEX Headless CMS que simplifica o gerenciamento de vários projetos de frontend, como aplicativos móveis, sites e email marketing em uma única tela.
 
-![Projects pages](//images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
+![Projects pages](https://images.ctfassets.net/alneenqid6w5/5sXlS9M78whzUVdSxJiKpX/b5bd29ece472c96fceb0aefb71a5365a/projects-one-pt-certo.gif)
 
 Cada projeto tem suas configurações, conteúdo e marca personalizados de acordo com públicos ou objetivos específicos.
 
@@ -33,7 +33,7 @@ Certifique-se de que os [recursos](https://help.vtex.com/pt/tutorial/license-man
 ## Visão geral
 Para acessar a página de **Projetos**, entre no VTEX Admin e clique em **Storefront > Headless CMS**.
 
-![Projects overview](//images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c5a1f1ba3077c11504d9f78c1712c59e/projects-two-pt.png)
+![Projects overview](https://images.ctfassets.net/alneenqid6w5/3RgVmOuLr7SJmEfots0KMZ/c5a1f1ba3077c11504d9f78c1712c59e/projects-two-pt.png)
 
 | Opção               | Descrição                                              |
 | ------------------- | ------------------------------------------------------ |
@@ -116,7 +116,7 @@ Para arquivar um projeto, siga os passos abaixo:
 2. Escolha o projeto que deseja arquivar e clique em **Configurações** (⚙️). Isso abrirá um modal.
 
 3. No modal, clique em `Arquivar projeto` na página `Geral`. Uma mensagem pop-up aparecerá confirmando se você deseja arquivar o projeto.
-![Arquivar projeto](//images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/c7410dbcff84549da3a15720a0ce68ed/projects-three-pt.png)
+![Arquivar projeto](https://images.ctfassets.net/alneenqid6w5/3FkQ3UCU68HH8QkP4LH91I/c7410dbcff84549da3a15720a0ce68ed/projects-three-pt.png)
 4. Clique em `Arquivar`. Em seguida, será exibida uma mensagem informando que o projeto foi arquivado com sucesso.
 
 Para restaurar um projeto arquivado, siga os passos em [Restaurar projeto](#restaurar-projeto).
diff --git a/docs/tutorials/pt/managing-redirects-per-binding.md b/docs/tutorials/pt/managing-redirects-per-binding.md
index a5bf9cbb9..5e5692be4 100644
--- a/docs/tutorials/pt/managing-redirects-per-binding.md
+++ b/docs/tutorials/pt/managing-redirects-per-binding.md
@@ -30,7 +30,7 @@ No Admin VTEX:
 1. Acesse **Storefront > Pages**.
 2. Clique na aba **Redirecionamentos**.
 
-![pt-redirecttab](//images.ctfassets.net/alneenqid6w5/5L8GV385HAeTQqBjQ3uAS4/e3a177caafdb271ce78b94c86f9add4f/pt-redirecttab.png)
+![pt-redirecttab](https://images.ctfassets.net/alneenqid6w5/5L8GV385HAeTQqBjQ3uAS4/e3a177caafdb271ce78b94c86f9add4f/pt-redirecttab.png)
 
 ## Criando redirecionamentos manualmente
 
@@ -40,7 +40,7 @@ No Admin VTEX:
 4. Defina se o seu redirecionamento será permanente ou temporário - caso o seu redirecionamento seja temporário, você pode selecionar o botão `Este redirecionamento tem uma data de término` para definir uma data de término para ele.
 5. Salve as suas alterações.
 
-![pt-newredirect](//images.ctfassets.net/alneenqid6w5/1qnEjsKieoskStnq0Bvl2P/0d02ab19801b3c6fea8e8b2a78ae4ef9/pt-newredirect.png)
+![pt-newredirect](https://images.ctfassets.net/alneenqid6w5/1qnEjsKieoskStnq0Bvl2P/0d02ab19801b3c6fea8e8b2a78ae4ef9/pt-newredirect.png)
 
 ## Excluindo redirecionamentos manualmente
 
@@ -48,7 +48,7 @@ No Admin VTEX:
 2. Clique no botão `Excluir`.
 3. Confirme sua ação.
 
-![pt-redirectdelete](//images.ctfassets.net/alneenqid6w5/3dRsZxKTYJTaOPrm6rBU84/3e5a9c1f27986e34fa7fd7b32f1a636e/pt-redirectdelete.png)
+![pt-redirectdelete](https://images.ctfassets.net/alneenqid6w5/3dRsZxKTYJTaOPrm6rBU84/3e5a9c1f27986e34fa7fd7b32f1a636e/pt-redirectdelete.png)
 
 <div class="alert alert-warning">
 Um <i>bug</i> pode ser encontrado ao tentar clicar em redirecionamentos com parâmetros de consulta na URL (<i>query strings</i>). O time de produto da VTEX já está ciente do comportamento inesperado e trabalhando na correção. Caso você não consiga clicar no redirecionamento desejado para excluí-lo, prefira fazê-lo por meio da importação da planilha enquanto o problema não é resolvido.
@@ -77,7 +77,7 @@ Os redirecionamentos listados na planilha serão obrigatoriamente criados ou exc
 4. Clique no botão `Importar`.
 5. Marque o botão `Salvar` ou` Excluir` de acordo com o seu cenário.
 
-![pt-planilharedirect](//images.ctfassets.net/alneenqid6w5/1Vjku4KoOrCbO7mcdehcCt/e7979dca1ef4b2f159bb3c09a42d9716/pt-planilharedirect.png)
+![pt-planilharedirect](https://images.ctfassets.net/alneenqid6w5/1Vjku4KoOrCbO7mcdehcCt/e7979dca1ef4b2f159bb3c09a42d9716/pt-planilharedirect.png)
 
 <div class="alert alert-warning">
 Ao clicar no botão <code>Salvar</code>, você criará todos os redirecionamentos listados em sua planilha, ao passo que clicar no botão <code>Excluir</couirde> removerá todos eles do banco de dados de redirecionamentos da sua loja.
diff --git a/docs/tutorials/pt/managing-shipping-policies.md b/docs/tutorials/pt/managing-shipping-policies.md
index 2cacc19f4..9c5a7a45a 100644
--- a/docs/tutorials/pt/managing-shipping-policies.md
+++ b/docs/tutorials/pt/managing-shipping-policies.md
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) é um conjunto de regras e configurações que definem quais opções de envio serão apresentadas aos clientes no checkout. A relação entre política de envio, [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) é o que compõe a sua [estratégia de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) na VTEX, conforme a imagem abaixo:
 
-![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
+![shipping_strategy_PT](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
 
 Este artigo apresenta como acompanhar e gerenciar suas políticas de envio. No Admin VTEX, em **Envio > Estratégia de envio**, a aba **Políticas de envio** é onde você realiza as seguintes ações:
 
@@ -37,7 +37,7 @@ Também é possível criar políticas de envio, confira o passo a passo no artig
 
 No Admin VTEX, ao acessar **Envio > Estratégia de envio**, na aba **Políticas de envio** você encontra uma lista como na imagem abaixo:
 
-![shipping_policy_PT](//images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/8f71ffc10c5e9e530c7f7d122de84005/shipping_policy_PT.png)
+![shipping_policy_PT](https://images.ctfassets.net/alneenqid6w5/uiwwWTGlS60kPjMDLNfzY/8f71ffc10c5e9e530c7f7d122de84005/shipping_policy_PT.png)
 
 As informações apresentadas nessa página estão descritas na tabela a seguir: 
 
diff --git a/docs/tutorials/pt/managing-singleton-content-types.md b/docs/tutorials/pt/managing-singleton-content-types.md
index e30cfea8e..67ca53215 100644
--- a/docs/tutorials/pt/managing-singleton-content-types.md
+++ b/docs/tutorials/pt/managing-singleton-content-types.md
@@ -18,7 +18,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 Content types do tipo Singleton permitem a criação e o gerenciamento de uma única página, garantindo que apenas uma página desse content type exista no Headless CMS.
 
 Esse content type evita conflitos e inconsistências que podem ocorrer quando várias páginas do mesmo content type são criadas. Por exemplo, você poder usar o Singleton para a Página Inicial (Home) da sua loja, garantindo que exista apenas uma Página Inicial e todas as atualizações e solicitações feitas a essa página sempre retornem o mesmo resultado.
-![singleton-br](//images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
+![singleton-br](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
 
 <div class="alert alert-warning">
 Para criar um content type Singleton, verifique com o seu time de desenvolvimento se a propriedade <i>isSingleton</i> já está implementada ou peça para que o time siga as intruções em <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> para adicioná-la ao content type desejado.
diff --git a/docs/tutorials/pt/managing-url-redirects.md b/docs/tutorials/pt/managing-url-redirects.md
index f9854b64d..6025b5f78 100644
--- a/docs/tutorials/pt/managing-url-redirects.md
+++ b/docs/tutorials/pt/managing-url-redirects.md
@@ -31,7 +31,7 @@ Para criar, editar ou apagar redirecionamentos, o usuário do Admin precisa ter
 4. Na caixa de seleção, indique se esse redirecionamento é temporário ou permanente. Caso seja temporário, é preciso definir a data final.
 5. Clique em `Salvar` para finalizar.
 
-![gerenciando redirecionamentos pt 1](//images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/1492276d15ccad0d3fb36ea59f712912/image4.png)
+![gerenciando redirecionamentos pt 1](https://images.ctfassets.net/alneenqid6w5/6WZzZNgQPLtfwP1Z8fK7S9/1492276d15ccad0d3fb36ea59f712912/image4.png)
 ## Importar redirecionamento
 
 Para importar um redirecionamento, siga os passos abaixo.
diff --git a/docs/tutorials/pt/managing-users.md b/docs/tutorials/pt/managing-users.md
index fad35c6a7..3c7c6f67b 100644
--- a/docs/tutorials/pt/managing-users.md
+++ b/docs/tutorials/pt/managing-users.md
@@ -19,7 +19,7 @@ A gestão dos usuários com acesso ao ambiente administrativo da sua loja VTEX 
 
 Esta página mostra a lista de usuários com os respectivos __Nome__, __Email__ e configuração de __MFA__. Também estão presentes opções de busca de usuários, exportar usuários e criar novos usuários. Outras opções disponíveis por esta interface são de editar ou excluir cada usuário.
 
-![Lista Usuários User Management PT](//images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
+![Lista Usuários User Management PT](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
 
 <div class="alert alert-warning">
 Qualquer usuário que deseje gerenciar usuários ou chaves de aplicação deve ter um perfil que contenha o <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recurso</a> <b>Save User</b>. Você pode usar, por exemplo, o perfil predefinido <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>.
@@ -30,10 +30,10 @@ Qualquer usuário que deseje gerenciar usuários ou chaves de aplicação deve t
 1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
 2. Clique no botão `+ Novo`.  
 3. Preencha o **Email**.
-  ![Cadastro Novo usuário User Management PT](//images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/24b86a1bfa609e3a7df29a9d871bf92c/Cadastro_Novo_usu__rio_User_Management_PT.png)
+  ![Cadastro Novo usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/6EWyev5Qu1nYYxbL1K8YMw/24b86a1bfa609e3a7df29a9d871bf92c/Cadastro_Novo_usu__rio_User_Management_PT.png)
 4. Clique em `+ Adicionar perfis`.
 5. Selecione os [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) desejados, conforme ilustrado pela imagem:
-  ![Selecionar perfis User Management PT](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png)
+  ![Selecionar perfis User Management PT](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png)
 6. Clique em `Adicionar perfis` para confirmar a seleção.
 7. Clique em `Salvar`.  
 
@@ -45,10 +45,10 @@ A senha deverá ter pelo menos oito caracteres e um número, uma letra maiúscul
 
 1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
 2. Para editar um usuário já cadastrado, clique em seu nome a partir da listagem de usuários. Outra possibilidade é clicar no botão de menu <i class="fas fa-ellipsis-v"></i> na linha do usuário desejado e então em **Editar**.
-  ![Botão Editar Usuário User Management PT](//images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/4795fe5b550804de645180f2ce973cb0/Bot__o_Editar_Usu__rio_User_Management_PT.png)
+  ![Botão Editar Usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/5XzJuCftOAty7JHkxHO5Th/4795fe5b550804de645180f2ce973cb0/Bot__o_Editar_Usu__rio_User_Management_PT.png)
   <div class="alert alert-warning" role="alert">Não é possível alterar o email de um usuário cadastrado. Neste caso, é necessário excluir o cadastro anterior e fazer um novo cadastro.</div>
 3. Na tela de edição, é possível adicionar e remover [Perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) do usuário, conforme ilustrado a seguir.
-  ![Selecionar perfis User Management PT](//images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png) 
+  ![Selecionar perfis User Management PT](https://images.ctfassets.net/alneenqid6w5/4wSp2QkYZH114DFFEOo3ly/f04120c62872db0a334a94cd6eaa27d0/Selecionar_perfis_User_Management__PT.png) 
 4. Clique em `Adicionar perfis` para confirmar a seleção.
 5. Clique em `Salvar`.
 
@@ -61,10 +61,10 @@ A senha deverá ter pelo menos oito caracteres e um número, uma letra maiúscul
 1. Na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > __Usuários__.
 2. Para remover o acesso de um usuário, na listagem de usuários, clique no botão de menu <i class="fas fa-ellipsis-v"></i> na linha do usuário que deseja remover.
 3. Clique no item **Excluir**.  
-  ![Botão Excluir Usuário User Management PT](//images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/211543a868c70430b56872901e1a834d/Bot__o_Excluir_Usu__rio_User_Management_PT.png)
+  ![Botão Excluir Usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/40v9IfXb47lKyi79vZgWpJ/211543a868c70430b56872901e1a834d/Bot__o_Excluir_Usu__rio_User_Management_PT.png)
   Aparecerá uma mensagem para confirmar a exclusão do usuário.
 4. Para confirmar, clique no botão `SIM, REMOVER O ACESSO`.  
-  ![Confirmar Remover Acesso User Management PT](//images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/682ccb51fcb859c7f0f50f7914049718/Confirmar_Remover_Acesso_User_Management_PT.png)
+  ![Confirmar Remover Acesso User Management PT](https://images.ctfassets.net/alneenqid6w5/2lnDFzfX0ZPsZM8uX59Nq7/682ccb51fcb859c7f0f50f7914049718/Confirmar_Remover_Acesso_User_Management_PT.png)
 
 ## Exportar dados de usuários
 
diff --git a/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md b/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md
index 1967adb0e..fb43b7572 100644
--- a/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md
+++ b/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md
@@ -17,7 +17,7 @@ subcategory: 1vwB9FtTSQmcSewQw02QoW
 
 O manual das classes e métodos usados no Web Service é um material complementar ao [guia de integração para ERPs](https://help.vtex.com/tutorial/guia-de-integracao-de-erps--3VuOwNLmb624ImooEIIkmO). Antes de usá-lo, atente-se a esse guia.
 
-[Download do manual de classes e métodos](//assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
+[Download do manual de classes e métodos](https://assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
 
 
 <div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
diff --git a/docs/tutorials/pt/marketplace-invited-sellers.md b/docs/tutorials/pt/marketplace-invited-sellers.md
index 3c8bdb70a..15fce3d25 100644
--- a/docs/tutorials/pt/marketplace-invited-sellers.md
+++ b/docs/tutorials/pt/marketplace-invited-sellers.md
@@ -28,7 +28,7 @@ Além de enviar convites, a página também conta com a lista de sellers, para q
 
 Para que novos sellers se integrem ao seu marketplace, algumas ações precisam ser feitas no seu ambiente VTEX: [Convidar](#convidar-seller) e [Conectar](#conectar-seller)
 
-![sellers convidados](//images.ctfassets.net/alneenqid6w5/2y4yFpA7vo6BNjMdVyvZSU/bf18d2e0010e23be921ecb520a060725/sellers_convidados.JPG)
+![sellers convidados](https://images.ctfassets.net/alneenqid6w5/2y4yFpA7vo6BNjMdVyvZSU/bf18d2e0010e23be921ecb520a060725/sellers_convidados.JPG)
 
 ## Convidar seller
 
diff --git a/docs/tutorials/pt/marketplace-strategies-at-vtex.md b/docs/tutorials/pt/marketplace-strategies-at-vtex.md
index 228fd6920..ba6386423 100644
--- a/docs/tutorials/pt/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/pt/marketplace-strategies-at-vtex.md
@@ -17,7 +17,7 @@ subcategory: 4uqMnZjwBO04uWgCom8QiA
 
 Um marketplace é uma plataforma virtual por meio da qual diferentes vendedores anunciam seus produtos. Esses vendedores são chamados de sellers, que além de serem os donos dos produtos, muitas vezes são também os responsáveis pelo [processo de fulfillment do produto](https://help.vtex.com/pt/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP).  
 
-![Estratégias de marketplace](//images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/a528c80c87b9e97b323f71f7608da296/Ecommerce_web_page-pana.png)
+![Estratégias de marketplace](https://images.ctfassets.net/alneenqid6w5/1XaGifpW4ztfRM3XIkiACS/a528c80c87b9e97b323f71f7608da296/Ecommerce_web_page-pana.png)
 
 [A VTEX promove a colaboração digital](https://vtex.com/br-pt/marketplace/) em diferentes cenários. Você pode não apenas vender seus produtos em outros marketplaces, mas também vender produtos de outros sellers no seu ambiente, tornando-se um marketplace.
 
@@ -72,7 +72,7 @@ A configuração da para [se tornar um marketplace VTEX](https://help.vtex.com/p
 
 Veja abaixo os principais marketplaces VTEX:  
 
-![mkt br](//images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
+![mkt br](https://images.ctfassets.net/alneenqid6w5/6DB08TtDzQ0tuesrK1I1XU/d42c1c45fff7301eea1e2fe7160274b5/mkt_br.png)
 
 Além disso, a página __Marketplaces e integrações__ promove e facilita o contato entre marketplaces VTEX e certificados com sellers VTEX interessados em colaborações.
 
diff --git a/docs/tutorials/pt/marketplaces-and-integrations.md b/docs/tutorials/pt/marketplaces-and-integrations.md
index 058638f0d..4230cd6f9 100644
--- a/docs/tutorials/pt/marketplaces-and-integrations.md
+++ b/docs/tutorials/pt/marketplaces-and-integrations.md
@@ -32,7 +32,7 @@ Note que a <b>Marketplaces e Integrações</b> é uma ferramenta que promove o c
 
 Para acessar a página, no Admin VTEX clique em __Marketplace > Conexões > Marketplaces e Integrações__. Na página será possível visualizar os marketplaces sugeridos para conexão e a lista completa de todos os marketplaces disponíveis ou já conectados.  
 
-![Marketplace e integrações](//images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png) 
+![Marketplace e integrações](https://images.ctfassets.net/alneenqid6w5/6O436Pjv91m3GWuWFsmeAD/563d08e7d74c4621111ae6a677725235/Marketplaces_e_Integra____es.png) 
 
 A tabela que lista os marketplaces possui as seguintes colunas:  
 
diff --git a/docs/tutorials/pt/master-data-v2.md b/docs/tutorials/pt/master-data-v2.md
index 86abda303..f6c07e731 100644
--- a/docs/tutorials/pt/master-data-v2.md
+++ b/docs/tutorials/pt/master-data-v2.md
@@ -26,11 +26,11 @@ Não é necessário criar um JSON Schema para salvar documentos. Você pode salv
 
 O JSON Schema indica como validar e indexar. Uma entidade de dados pode ou não ter múltiplos JSON Schemas.
 
-![master-data-data-entity-schemas](//images.contentful.com/alneenqid6w5/5Ms8eS24xOsGWcEGY0WKwu/724d0585090ee2d3bf6fc47dad7a3859/master-data-data-entity-schemas.jpg)
+![master-data-data-entity-schemas](https://images.contentful.com/alneenqid6w5/5Ms8eS24xOsGWcEGY0WKwu/724d0585090ee2d3bf6fc47dad7a3859/master-data-data-entity-schemas.jpg)
 
 Um documento pode ser compatível com múltiplos JSON Schemas, mas também com nenhum.
 
-![master-data-documents-compliant](//images.contentful.com/alneenqid6w5/7m7NMV5Hc4Wq8aKeGeWiAY/29301b6873e1549c244d56e15cf4caf7/master-data-documents-compliant.jpg)
+![master-data-documents-compliant](https://images.contentful.com/alneenqid6w5/7m7NMV5Hc4Wq8aKeGeWiAY/29301b6873e1549c244d56e15cf4caf7/master-data-documents-compliant.jpg)
 
 Isso significa que o JSON Schema é um formato de documentos em entidades de dados.
 
diff --git a/docs/tutorials/pt/master-data.md b/docs/tutorials/pt/master-data.md
index 0eb9189c5..d61e49745 100644
--- a/docs/tutorials/pt/master-data.md
+++ b/docs/tutorials/pt/master-data.md
@@ -282,7 +282,7 @@ Com a v2 do Master Data, você pode definir formatos de dados com JSON schemas.
 
 Você pode salvar um documento em qualquer entidade de dados se o conteúdo for um JSON válido. Uma entidade de dados pode ou não ter múltiplos JSON schemas associados.
 
-![Master Data schemas](//images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/908c8b04ea9e32271a494eeb0f2f7a56/schemas_pt.jpg)
+![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/908c8b04ea9e32271a494eeb0f2f7a56/schemas_pt.jpg)
 
 <div class = "alert alert-info">
 Um documento pode ser compatível com múltiplos JSON Schemas, mas também com nenhum.
diff --git a/docs/tutorials/pt/match-offers-mercado-livre.md b/docs/tutorials/pt/match-offers-mercado-livre.md
index a5a809813..2221052d5 100644
--- a/docs/tutorials/pt/match-offers-mercado-livre.md
+++ b/docs/tutorials/pt/match-offers-mercado-livre.md
@@ -34,7 +34,7 @@ Nesse artigo você pode explorar os seguintes tópicos:
 [Tipos de oportunidades](#tipos-de-oportunidades)  
 [Analisar oportunidade](#analisar-oportunidade)  
 
-![overview-match-anuncios-meli-pt](//images.ctfassets.net/alneenqid6w5/3ve5RacaoRg0KNNEDzegGi/4bdce35a31296b74251777db678e7843/overview-match-anuncios-meli-pt.png)
+![overview-match-anuncios-meli-pt](https://images.ctfassets.net/alneenqid6w5/3ve5RacaoRg0KNNEDzegGi/4bdce35a31296b74251777db678e7843/overview-match-anuncios-meli-pt.png)
 
 ## Estrutura da página
 A página **Match de anúncios Mercado Livre** é composta por duas abas, [Oportunidades](#aba-oportunidades) e [catálogos ativos](#aba-anuncios-vinculados). Veja a seguir quais as informações e dados disponíveis em cada uma.
@@ -63,7 +63,7 @@ Na lista dos catálogos ativos, cada linha representa um anúncio e cada linha 
 
 No topo da tela é possível acompanhar quantos dos catálogos ativos estão em cada status de relevância.
 
-![relevancia-anuncio-pt](//images.ctfassets.net/alneenqid6w5/2Yye8ZNkakmcMBTPZP7QKH/c70be3ea5ca177806104ef47dec0c29b/Captura_de_tela_2024-04-30_181530.png)
+![relevancia-anuncio-pt](https://images.ctfassets.net/alneenqid6w5/2Yye8ZNkakmcMBTPZP7QKH/c70be3ea5ca177806104ef47dec0c29b/Captura_de_tela_2024-04-30_181530.png)
 
 <div class=”alert alert-info>
  Os anúncios ganham relevância quando ele merece o melhor preço e as melhores condições logísticas. 
@@ -80,15 +80,15 @@ A relevância de um anúncio mostra se a oferta do seller aparece como a primeir
 Três tipos de oportunidades podem ser disponibilizadas para os anúncios de um seller, **Aviso prévio, Obrigatório** e **Opcional.** Em todas as oportunidades listadas pelo Mercado Livre o seller tem a opção de vincular o produto a um anúncio e caso não tenha correspondência do anúncio do seller com uma oferta de catálogo, é necessário abrir um chamado no suporte do Mercado Livre.
 
 - **Aviso prévio:**  as oportunidades desse tipo são de caráter obrigatório e têm um prazo para serem vinculadas, ou seja, o seller precisa vincular o produto a uma oferta do catálogo Mercado Livre. Caso a vinculação não seja realizada no prazo determinado pelo Mercado Livre, o anúncio do seller será moderado pelo marketplace.  
-![oportunidade-avisoprevio-pt](//images.ctfassets.net/alneenqid6w5/wSTOwKrQ7AFCEtCNI2l5P/a0b2d2e0331096c95b082e72fc0ba9a0/Captura_de_tela_2024-04-30_184708.png)
+![oportunidade-avisoprevio-pt](https://images.ctfassets.net/alneenqid6w5/wSTOwKrQ7AFCEtCNI2l5P/a0b2d2e0331096c95b082e72fc0ba9a0/Captura_de_tela_2024-04-30_184708.png)
 
 - **Obrigatória:** as oportunidades desse tipo são de caráter obrigatório, mas não têm um prazo para serem vinculadas, mas caso o anúncio não seja vinculado, o Mercado Livre poderá moderar o anúncio do seller no marketplace.  
 
-![oportunidade-obrigatoria-pt](//images.ctfassets.net/alneenqid6w5/3z59cnsyTgy1QGQdZ3OGyH/e00a9c162c596956e5eb1663b9802a67/Captura_de_tela_2024-04-30_185306.png)
+![oportunidade-obrigatoria-pt](https://images.ctfassets.net/alneenqid6w5/3z59cnsyTgy1QGQdZ3OGyH/e00a9c162c596956e5eb1663b9802a67/Captura_de_tela_2024-04-30_185306.png)
 
 - **Opcional:** as oportunidades desse tipo não são de caráter obrigatório. Caso a vinculação não seja realizada, o anúncio do seller não perde relevância e nem é bloqueado pelo marketplace.  
 
-![oportunidade-opcional-pt](//images.ctfassets.net/alneenqid6w5/2vXdrBmj4ba5iXobKSv8B2/402b94780b58a9817413ab543cb6f544/Captura_de_tela_2024-04-30_185642.png)  
+![oportunidade-opcional-pt](https://images.ctfassets.net/alneenqid6w5/2vXdrBmj4ba5iXobKSv8B2/402b94780b58a9817413ab543cb6f544/Captura_de_tela_2024-04-30_185642.png)  
 
 ## Analisar oportunidade
 
@@ -99,7 +99,7 @@ Para analisar uma oportunidade, o seller utiliza a página **Match de anúncios*
 A tela **Analisar oportunidade,** aparecerá quando o seller clicar no botão **`Analisar oportunidade`** em um dos anúncios disponíveis na aba **Oportunidades.**  
 Nessa tela o seller visualizará do lado esquerdo o seu produto cadastrado no catálogo VTEX e do lado direito o produto do catálogo Mercado Livre que foi sugerido para vinculação.
 
-![analisar-oportunidade-pt](//images.ctfassets.net/alneenqid6w5/79EgKpmRxwlWvMUzaERmk4/840d4be11a3b133042499ee3786b7227/Captura_de_tela_2024-04-30_193248.png)  
+![analisar-oportunidade-pt](https://images.ctfassets.net/alneenqid6w5/79EgKpmRxwlWvMUzaERmk4/840d4be11a3b133042499ee3786b7227/Captura_de_tela_2024-04-30_193248.png)  
 
 ### Vinculação individual
 
@@ -110,7 +110,7 @@ Para vincular as oportunidades individualmente, após acessar a página **Match
 3. Clique no botão **`Aceitar sugestão`.**   
 4. Clique no botão **`Confirmar`**.  
 
-![aceitar-sugestão-pt](//images.ctfassets.net/alneenqid6w5/7dH1vRXEHyXBMSOr3IaehY/254d43b67aa8f40b47247f15c909ed9e/Captura_de_tela_2024-04-30_192650.png)  
+![aceitar-sugestão-pt](https://images.ctfassets.net/alneenqid6w5/7dH1vRXEHyXBMSOr3IaehY/254d43b67aa8f40b47247f15c909ed9e/Captura_de_tela_2024-04-30_192650.png)  
 
 Após vincular, o anúncio é publicado no catálogo Mercado Livre e enviado para a **Aba catálogos ativos** sob o status de **Processando relevância.**
 
@@ -118,7 +118,7 @@ Caso os produtos não sejam correspondentes, o seller deve buscar um anúncio no
 
 Para procurar outros anúncios no catálogo Mercado Livre,  o seller deve digitar o nome de seu produto na barra de busca que está abaixo da foto principal do produto na página **`Analisar oportunidade`.** Veja na imagem abaixo:
 
-![buscar-anuncio-pt](//images.ctfassets.net/alneenqid6w5/5xdQ2BlXl6KgQq2Y6fvD2N/18b9333ef684e6cc478e1c08c17f237d/Captura_de_tela_2024-04-30_194057.png)  
+![buscar-anuncio-pt](https://images.ctfassets.net/alneenqid6w5/5xdQ2BlXl6KgQq2Y6fvD2N/18b9333ef684e6cc478e1c08c17f237d/Captura_de_tela_2024-04-30_194057.png)  
 
 ### Vinculação em massa
 
@@ -128,7 +128,7 @@ Para vincular as oportunidades massivamente, após acessar a página **Match de
 2. Clique no botão **`Aceitar sugestões`.**
 3. Clique no botão **`Confirmar`.**
 
-![aceitar-sugestão-bulk-pt](//images.ctfassets.net/alneenqid6w5/5Eq1eBQB2BgqO6xbtLByQr/0e4bdfc9f7b37ba8684dcb72ad7d6ae6/Captura_de_tela_2024-04-30_192556.png)  
+![aceitar-sugestão-bulk-pt](https://images.ctfassets.net/alneenqid6w5/5Eq1eBQB2BgqO6xbtLByQr/0e4bdfc9f7b37ba8684dcb72ad7d6ae6/Captura_de_tela_2024-04-30_192556.png)  
 
 Após vincular, o anúncio é publicado no catálogo Mercado Livre e enviado para a **Aba catálogos ativos** sob o status de **Processando relevância.**
 
diff --git a/docs/tutorials/pt/media-overview.md b/docs/tutorials/pt/media-overview.md
index 17dc95ce9..45ea3f4f8 100644
--- a/docs/tutorials/pt/media-overview.md
+++ b/docs/tutorials/pt/media-overview.md
@@ -21,7 +21,7 @@ O Mídia é uma funcionalidade responsável por gerenciar os arquivos de mídia
   Para upload, os arquivos devem ter uma extensão em minúsculo, por exemplo, <code>store.png</code>, e tamanho de até <b>5 MB</b>.
 </div>
 
-![Mídia Visão Geral](//images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/1daf233a39aa1f3e4bd5b42b1f4b8805/pt-m__dia-overview.png)
+![Mídia Visão Geral](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/1daf233a39aa1f3e4bd5b42b1f4b8805/pt-m__dia-overview.png)
 
 Além disso, o Mídia está integrado ao **Site Editor** e ao **Headless CMS**, o que permite que ele seja acessado e gerenciado diretamente através de soluções de CMS da VTEX. 
 
@@ -45,7 +45,7 @@ A seção disponível deve utilizar o <a href="https://developers.vtex.com/docs/
 
 Na imagem a seguir, confira a visão geral da interface do Mídia e as ações disponíveis para gerenciar seus arquivos de mídia:
 
-![Mídia Features](//images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/4ffd0d22e2c3ce0173f5643177728be4/pt-m__dia-features.png)
+![Mídia Features](https://images.ctfassets.net/alneenqid6w5/2teyzkUy2zP5vjMLPxlXgD/4ffd0d22e2c3ce0173f5643177728be4/pt-m__dia-features.png)
 
 | Campo | Descrição |
 | ---------- | ------------- |
diff --git a/docs/tutorials/pt/mercado-libre-promotions.md b/docs/tutorials/pt/mercado-libre-promotions.md
index b34c213e3..5fed2d8c9 100644
--- a/docs/tutorials/pt/mercado-libre-promotions.md
+++ b/docs/tutorials/pt/mercado-libre-promotions.md
@@ -21,7 +21,7 @@ Para proporcionar maior agilidade à operação do seller, na barra de busca glo
 
 Para acessar a página de promoções disponíveis no Admin VTEX, você deve seguir o caminho __Marketplace > Mercado Livre > Promoções.__  
 
-![Promoções do mercado livre](//images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
+![Promoções do mercado livre](https://images.ctfassets.net/alneenqid6w5/6LigPeBx1YMf6NQPJaqURK/cae6ebf8e19c5bc2fd8b8d4839ad029e/buscapromocoes.gif)
 
 ## Tipos de promoções  
 
diff --git a/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md b/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
index be92cae86..623b0afe3 100644
--- a/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
+++ b/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
@@ -29,7 +29,7 @@ Nos anúncios enviados ao Mercado Livre é possível identificar quais apresenta
 Os anúncios que apresentarem erro, não serão enviados ao Mercado Livre até que seja corrigido.
 </div>  
 
-![Mercado Livre: Compatibilidade Automobilística](//images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/71bc2c07df8a14d172a0f58afb4e99f8/compatibilidade_automobilistica_1.png)  
+![Mercado Livre: Compatibilidade Automobilística](https://images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/71bc2c07df8a14d172a0f58afb4e99f8/compatibilidade_automobilistica_1.png)  
 
 Para acessar o módulo de Gerenciamento de anúncios, no Admin VTEX vá em Marketplace > Integrações > Gerenciamento de anúncios. Nesta página você pode filtrar os anúncios por, canal, marca, categoria ou status.
 
@@ -39,7 +39,7 @@ Para corrigir os erros de `Compatibilidade com Meli`, siga o passo a passo abaix
 2. Clique em __Error de associação de autopeças.__  
 3. Clique em __Gerenciar compatibilidade.__  
 4. Preencha os campos, __marca, modelo, ano__ e __versão,__ conforme a compatibilidade do acessório.  
-![Mercado Livre: Compatibilidade Automobilística 2](//images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/581cda2b20d2cccec1fc818a2a4153b7/comopatibilidade_automobilistica_2.png)  
+![Mercado Livre: Compatibilidade Automobilística 2](https://images.ctfassets.net/alneenqid6w5/GWG92iEbWI9FBRGswnGWk/581cda2b20d2cccec1fc818a2a4153b7/comopatibilidade_automobilistica_2.png)  
 5. Adicione todos os modelos de veículos compatíveis clicando em +.
 6. Clique no botão __Adicionar exceção__ e aguarde a mensagem “exceção enviada com sucesso”.
 7. Clique em __Confirmar__ e a mensagem “compatibilidade associada com sucesso” aparecerá na tela.  
diff --git a/docs/tutorials/pt/mercado-livre-faq.md b/docs/tutorials/pt/mercado-livre-faq.md
index cf0ec0adf..d695c2f58 100644
--- a/docs/tutorials/pt/mercado-livre-faq.md
+++ b/docs/tutorials/pt/mercado-livre-faq.md
@@ -125,7 +125,7 @@ Ao cadastrar um produto, é necessário estabelecer uma quantidade mínima para
 
 A categoria em questão exige o mapeamento de marca e modelo. Essas informações devem estar presentes na planilha de mapeamento. Formato de exemplo:
 
-![mercadolivre faq erro](//images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
+![mercadolivre faq erro](https://images.ctfassets.net/alneenqid6w5/0ohB2SiPHNmQMufVCfyou/21f9472e17fb15af9b910756ab6d0c89/mercadolivre_faq_erro.JPG)
 
 ### Por que meu anúncio está desativado no Mercado Livre?
 
@@ -165,13 +165,13 @@ No entanto, esses atributos são bastante claros (Cor principal, Cor secundária
 
 Se algum desses atributos for preenchido incorretamente (por exemplo, se você atribuiu um código referente a Tamanho de cinto para um calçado), o Integrações vai retornar um erro com o seguinte formato:
 
-![mercadolivre faq erro2](//images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
+![mercadolivre faq erro2](https://images.ctfassets.net/alneenqid6w5/2vUouOJPTK2ual9FZMfOFS/5e3d929a0cd2523663b9370745dce783/mercadolivre_faq_erro2.JPG)
 
 Neste caso, temos dois exemplos de erros na mesma mensagem.
 
 O primeiro deles indica que o atributo cujo código se inicia com o número `113000` é necessário para a categoria escolhida e não foi inserido na planilha de mapeamento. Veja a planilha abaixo:
 
-![mercadolivre faq erro3](//images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
+![mercadolivre faq erro3](https://images.ctfassets.net/alneenqid6w5/2YAWKiw4kIJc41xfNm1sdw/6345af3383c6acdaea4813c42274248b/mercadolivre_faq_erro3.JPG)
 
 O segundo erro indica que o atributo cujo código se inicia com o número `63000`, inserido na última coluna da planilha acima, é inválido para a categoria escolhida.
 
@@ -216,7 +216,7 @@ Existe o elemento principal do anúncio e ele contém as variações (que são o
 
 Acontece que cada categoria tem sua especificação de quantidade de imagens que podem ser adicionadas, para o caso da categoria MLA3697 são somente 12 imagens permitidas para esse elemento principal. Veja [aqui](https://api.mercadolibre.com/categories/MLA3697) as condições dessa categoria. 
 
-![mercadolivre faq erro4](//images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
+![mercadolivre faq erro4](https://images.ctfassets.net/alneenqid6w5/5fz7U4ytVKkijIWqof3XGu/b7748b6c1c14bbf87b1f6bb009d58c5d/mercadolivre_faq_erro4.JPG)
 
 `Sku não integrado pois o mesmo não possui descrição`
 
diff --git a/docs/tutorials/pt/merchandising-rules-list.md b/docs/tutorials/pt/merchandising-rules-list.md
index d8bff694a..3252f710c 100644
--- a/docs/tutorials/pt/merchandising-rules-list.md
+++ b/docs/tutorials/pt/merchandising-rules-list.md
@@ -22,7 +22,7 @@ No Admin VTEX, a página **Storefront** > **Intelligent Search** > **Regras de m
 * [Editar regra de merchandising](#editar-regras-de-merchandising)
 * [Excluir regra de merchandising](#excluir-regras-de-merchandising)
 
-![regras-merch-pt](//images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/725d7d991d98ca633d7efd56ec14a254/regras-merch-pt.PNG)
+![regras-merch-pt](https://images.ctfassets.net/alneenqid6w5/3EB5tru4DiZzTMQ7oe8xHV/725d7d991d98ca633d7efd56ec14a254/regras-merch-pt.PNG)
 
 | Coluna | Descrição |
 | - | - |
diff --git a/docs/tutorials/pt/meta-tags-suiteshare.md b/docs/tutorials/pt/meta-tags-suiteshare.md
index 95dadf254..487a39ef5 100644
--- a/docs/tutorials/pt/meta-tags-suiteshare.md
+++ b/docs/tutorials/pt/meta-tags-suiteshare.md
@@ -19,11 +19,11 @@ Meta Tags são informações que são carregadas juntamente com o seu link, assi
 
 Meta tag no WhatsApp:
 
-![Meta Tags_Suitshare_1](//images.ctfassets.net/alneenqid6w5/1vDto0Syulmk1FrMOc2i89/74ea4883a2c35c4149b76681f91f407d/Meta_Tags_Suitshare_1.png)
+![Meta Tags_Suitshare_1](https://images.ctfassets.net/alneenqid6w5/1vDto0Syulmk1FrMOc2i89/74ea4883a2c35c4149b76681f91f407d/Meta_Tags_Suitshare_1.png)
 
 Meta tag no Facebook:
 
-![Meta Tags_Suitshare_2](//images.ctfassets.net/alneenqid6w5/2q2emAMuyTEdQkG2vGoimB/6716bfd664b525f0557a99c676359bde/Meta_Tags_Suitshare_2.png)
+![Meta Tags_Suitshare_2](https://images.ctfassets.net/alneenqid6w5/2q2emAMuyTEdQkG2vGoimB/6716bfd664b525f0557a99c676359bde/Meta_Tags_Suitshare_2.png)
 
 As Meta Tags servem como uma prévia do que o usuário irá encontrar quando clicar no seu link.
 
@@ -33,15 +33,15 @@ As Meta Tags servem como uma prévia do que o usuário irá encontrar quando cli
 
 No painel da VTEX Assisted Sales (SuiteShare), acesse a opção _**Atrair > Links**_.
 
-![Meta Tags_Suitshare_3](//images.ctfassets.net/alneenqid6w5/1JG2XCOA4pYyJeQiWB2Hkv/fa3c65fd6506c7594b93f55e7b05fe8a/Meta_Tags_Suitshare_3.png)
+![Meta Tags_Suitshare_3](https://images.ctfassets.net/alneenqid6w5/1JG2XCOA4pYyJeQiWB2Hkv/fa3c65fd6506c7594b93f55e7b05fe8a/Meta_Tags_Suitshare_3.png)
 
 Clique na seta para baixo, localizada no lado direito do link que você deseja editar as Meta Tags. Clique na opção **Meta tags**.
 
-![Meta Tags_Suitshare_4](//images.ctfassets.net/alneenqid6w5/2mtMGJL5l7nE5w8GrPmfNm/6773c197d01eed56453f7d23b419211f/Meta_Tags_Suitshare_4.png)
+![Meta Tags_Suitshare_4](https://images.ctfassets.net/alneenqid6w5/2mtMGJL5l7nE5w8GrPmfNm/6773c197d01eed56453f7d23b419211f/Meta_Tags_Suitshare_4.png)
 
 Em **Título**, você irá digitar o título do link. Nesse caso, utilizaremos um nome. Já na Descrição, você pode escrever um breve resumo do que você faz, de quem você é, o que a sua empresa vende, ou até mesmo, uma chamada para ação, como no exemplo. E por fim adicione uma imagem ao seu link. 
 
-![Meta Tags_Suitshare_5](//images.ctfassets.net/alneenqid6w5/3voZYLGdaJE8BqWuHP40ix/7e55c30cfaf23bf4db1f84c63737d060/Meta_Tags_Suitshare_5.png)
+![Meta Tags_Suitshare_5](https://images.ctfassets.net/alneenqid6w5/3voZYLGdaJE8BqWuHP40ix/7e55c30cfaf23bf4db1f84c63737d060/Meta_Tags_Suitshare_5.png)
 
 Clique no botão **Finalizar**.
 
diff --git a/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md b/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md
index 7892d3e26..2f670c1ae 100644
--- a/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md
+++ b/docs/tutorials/pt/metrics-are-not-displayed-in-the-order-dashboard.md
@@ -23,7 +23,7 @@ Ao acessar o painel Admin, pode ser que sua loja não carregue métricas na **Vi
 - **Período de comparação inadequado:** o período selecionado no canto superior direito do dashboard pode não conter dados de pedidos suficientes para a comparação.
 - **Permissões de acesso insuficientes:** você pode não ter o perfil de acesso necessário para visualizar determinadas informações no dashboard.
 
-![Visão geral - PT](//images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/466e5f7f843a9023750b32bb3397adbb/Vis_o_geral_-_PT.png)
+![Visão geral - PT](https://images.ctfassets.net/alneenqid6w5/29XRCPWPEnqdR79xKebzv/466e5f7f843a9023750b32bb3397adbb/Vis_o_geral_-_PT.png)
 
 ## Solução
 Para resolver inconsistências no dashboard inicial do painel administrativo, você pode testar as ações descritas abaixo:
@@ -34,7 +34,7 @@ Ajustar o período de comparação pode resolver o problema ao exibir métricas
 1. No Admin VTEX, acesse **Dashboard > Visão geral**.
 2. No canto superior direito, selecione o período de comparação.
 
-![Dashboard- PT](//images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/77b35596da94175d044944a1f01de1b4/Dashboard-_PT.png)
+![Dashboard- PT](https://images.ctfassets.net/alneenqid6w5/6JTwTAXr2d4M16xQK6fE8x/77b35596da94175d044944a1f01de1b4/Dashboard-_PT.png)
 
 ### Aguarde a atualização das informações
 Considere o tempo de espera de 10 a 80 minutos para a atualização das informações no painel. Este período é necessário para que os dados sejam processados e exibidos corretamente. Para mais informações sobre o tempo de espera, acesse  [Comparação de períodos](https://help.vtex.com/pt/tutorial/visao-geral-da-loja--P8ahguoRs0U3PzmXg2wuQ?&utm_source=autocomplete#comparacao-de-periodos).
diff --git a/docs/tutorials/pt/migrating-ads-in-mercado-livre.md b/docs/tutorials/pt/migrating-ads-in-mercado-livre.md
index 1a078a0af..08a83d890 100644
--- a/docs/tutorials/pt/migrating-ads-in-mercado-livre.md
+++ b/docs/tutorials/pt/migrating-ads-in-mercado-livre.md
@@ -41,7 +41,7 @@ Caso utilize o ID de uma política comercial existente, a integração criará n
 
 Nessa etapa você precisará fazer a equivalência entre seus anúncios no Mercado Livre e os SKUs da sua loja. O envio dessas informações é feito por meio da planilha de migração.
 
-Primeiro, faça download da [Planilha de migração](//assets.ctfassets.net/alneenqid6w5/4tgBiQQeiAQGyys4OAuIGc/1bf6f64f485de43d2329db270c1303de/Planilha_de_Migrac__a__o_de_Anu__ncios_-_Mercado_Livre_BR.xlsx) e utilize o arquivo como modelo para preenchimento. Esta é a planilha que será preenchida e enviada para o Mercado Livre.
+Primeiro, faça download da [Planilha de migração](https://assets.ctfassets.net/alneenqid6w5/4tgBiQQeiAQGyys4OAuIGc/1bf6f64f485de43d2329db270c1303de/Planilha_de_Migrac__a__o_de_Anu__ncios_-_Mercado_Livre_BR.xlsx) e utilize o arquivo como modelo para preenchimento. Esta é a planilha que será preenchida e enviada para o Mercado Livre.
 
 O produto cadastrado na VTEX só poderá ser mapeado com um anúncio no Mercado Livre. No caso de [anúncios dos tipos Clássico e Premium](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/2MR2USqcvDGaoAkGNdCfGi), por serem configurações separadas, o mesmo produto pode estar anunciado em ambos tipos de anúncios.
 
diff --git a/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md b/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md
index 95b268952..58f169e8f 100644
--- a/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md
+++ b/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md
@@ -25,7 +25,7 @@ Note que, apesar de estar em um iframe, ainda é possível aplicar CSS normalmen
 
 Em exemplo prático, para ocultar a opção "Pagar usando dois cartões", deve ser usado apenas `.ChangeNumberOfPayments {display: none}`.
 
-![2017-06-22 162341](//images.contentful.com/alneenqid6w5/5Un86ot46Qg0kwKoUkSioG/fb3cc25e273d68ab27a3ccd2b254eea6/2017-06-22_162341.jpg)
+![2017-06-22 162341](https://images.contentful.com/alneenqid6w5/5Un86ot46Qg0kwKoUkSioG/fb3cc25e273d68ab27a3ccd2b254eea6/2017-06-22_162341.jpg)
 
 ### Nova opção de cálculo de frete por geocoordenada
 
diff --git a/docs/tutorials/pt/moskit-suiteshare.md b/docs/tutorials/pt/moskit-suiteshare.md
index 3d2f40f91..1e42db610 100644
--- a/docs/tutorials/pt/moskit-suiteshare.md
+++ b/docs/tutorials/pt/moskit-suiteshare.md
@@ -23,29 +23,29 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Moskit**.
 
-   ![HubSpot_Suiteshare_1](//images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
+   ![HubSpot_Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/6ohwamJ0xsLQsxtuTZrrxA/affa4804ec1386284ac220a82ec6622a/HubSpot_Suiteshare_1.png)
 
 2. Acesse **Configurações > Integrações > Moskit > Integrar**.
 
-   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
 Selecione o [Formulário de captura](http://help.suiteshare.com/support/solutions/articles/67000192044-formul%C3%A1rio-de-captura) que irá integrar ao Moskit. 
 
-![Moskit_Suiteshare_1](//images.ctfassets.net/alneenqid6w5/7JgLdaJfPQDOVHvNe767sW/a4362f1e43b1cda42d00490f364deee5/Moskit_Suiteshare_1.png)
+![Moskit_Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/7JgLdaJfPQDOVHvNe767sW/a4362f1e43b1cda42d00490f364deee5/Moskit_Suiteshare_1.png)
 
 Para descobrir o seu ID, acesse dentro do Moskit: **Configurações > Usuários do sistema > Selecione o usuário desejado** e copie o número informado na URL.
 
-![Moskit_Suiteshare_2](//images.ctfassets.net/alneenqid6w5/7H9cd7rbPyMUvFeQp0tQjq/8b863a0d3c950739c115b841040b8272/Moskit_Suiteshare_2.png)
+![Moskit_Suiteshare_2](https://images.ctfassets.net/alneenqid6w5/7H9cd7rbPyMUvFeQp0tQjq/8b863a0d3c950739c115b841040b8272/Moskit_Suiteshare_2.png)
 
 Agora precisamos do token fornecido pela Moskit, no painel da Moskit clique em **Marketplace** e selecione a opção **API pública do Moskit CRM**, clique em **Ver mais**. 
 
 Clique em **Gerar nova key**.
 
-![Moskit_Suiteshare_3](//images.ctfassets.net/alneenqid6w5/1S7dteXair1ffMZayzfbCE/96e40883c818c03ae778439390767696/Moskit_Suiteshare_3.png)
+![Moskit_Suiteshare_3](https://images.ctfassets.net/alneenqid6w5/1S7dteXair1ffMZayzfbCE/96e40883c818c03ae778439390767696/Moskit_Suiteshare_3.png)
 
 Copie a Hash informada. 
 
-![Moskit_Suiteshare_4](//images.ctfassets.net/alneenqid6w5/a07HZoQQxhOUULnleYwUN/3e1530d84adb5de0869324eb7c3790cb/Moskit_Suiteshare_4.png)
+![Moskit_Suiteshare_4](https://images.ctfassets.net/alneenqid6w5/a07HZoQQxhOUULnleYwUN/3e1530d84adb5de0869324eb7c3790cb/Moskit_Suiteshare_4.png)
 
 Cole a informação dentro do painel do VTEX Assisted Sales (SuiteShare) no segundo campo. 
 
diff --git a/docs/tutorials/pt/multilevel-omnichannel-inventory.md b/docs/tutorials/pt/multilevel-omnichannel-inventory.md
index 3235432b7..a1ed8a7c4 100644
--- a/docs/tutorials/pt/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/pt/multilevel-omnichannel-inventory.md
@@ -38,7 +38,7 @@ Também é possível que esse seller principal venda seus produtos em um marketp
 
 Quando isso ocorre, temos uma arquitetura de três níveis entre marketplace, seller principal,  e seus sellers white label, como ilustra a imagem abaixo.
 
-![Arquitetura Multilevel omichannel inventory](//images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/b70689c18e55ad472f71176a283b9c17/Screen_Shot_2022-09-30_at_18.57.26.png)
+![Arquitetura Multilevel omichannel inventory](https://images.ctfassets.net/alneenqid6w5/7k6hYv3kWxBVZrPFkUbsCK/b70689c18e55ad472f71176a283b9c17/Screen_Shot_2022-09-30_at_18.57.26.png)
 
 Por padrão, os produtos das lojas físicas, ou sellers white label (nível 3, na imagem), não ficam disponíveis para serem vendidos pelo marketplace do nível 1. Mas é possível torná-los disponíveis com a funcionalidade **Multilevel Omnichannel Inventory.**
 
diff --git a/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md b/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md
index 3d8bac096..7d89bbd61 100644
--- a/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md
+++ b/docs/tutorials/pt/my-ad-is-not-displayed-on-mercado-livre.md
@@ -36,7 +36,7 @@ Para validar se a política comercial está configurada corretamente no cadastro
 3. Na página de cadastro do produto, valide se a política comercial que atende o Mercado Livre está selecionada.
 4. Caso não esteja, marque a flag da política comercial.
 
-  ![politicas-comerciais-pt](//images.ctfassets.net/alneenqid6w5/dRDUjjHbk3Ui0ZQEX7SYd/973f3dd4441c0b4646d0139380d13666/politicas-comerciais-pt.png)
+  ![politicas-comerciais-pt](https://images.ctfassets.net/alneenqid6w5/dRDUjjHbk3Ui0ZQEX7SYd/973f3dd4441c0b4646d0139380d13666/politicas-comerciais-pt.png)
 
  5. Clique no botão `Salvar`.
 
@@ -52,7 +52,7 @@ Para validar a configuração do estoque limite, acesse Marketplace > Conexões
 2. Na linha do card de integração desejado, clique em `Editar`.
 3. Em `Configurações`, verifique se há algum valor atribuído ao campo Estoque limite para pausa de anúncio.
 
-  ![estoque-limite-pt](//images.ctfassets.net/alneenqid6w5/wy7Bz5Dcm2pt24HNVHYdZ/4cf81a0315f7dbb465e1dd9a737d6ec9/estoque-limite-pt.png)
+  ![estoque-limite-pt](https://images.ctfassets.net/alneenqid6w5/wy7Bz5Dcm2pt24HNVHYdZ/4cf81a0315f7dbb465e1dd9a737d6ec9/estoque-limite-pt.png)
 
  4. Certifique-se de que a configuração deste campo está correta, de acordo com o artigo [Controle de estoque mínimo para integrações](https://help.vtex.com/pt/tutorial/controle-de-estoque-minimo-para-integracoes--5hvUNIiSeJ5QCaZQYpYf1D). 
 
diff --git a/docs/tutorials/pt/names-of-vtex-branches-worldwide.md b/docs/tutorials/pt/names-of-vtex-branches-worldwide.md
index 3ac18758f..2dcf4c94b 100644
--- a/docs/tutorials/pt/names-of-vtex-branches-worldwide.md
+++ b/docs/tutorials/pt/names-of-vtex-branches-worldwide.md
@@ -29,4 +29,4 @@ A VTEX se orgulha de possuir escritórios em países diferentes e vários client
 
 Para saber em qual país você é faturado, você pode consultar seu contrato ou [fazer download da sua fatura](https://help.vtex.com/pt/tutorial/como-fazer-download-faturas-da-VTEX--tutorials_653). Ao abrir a fatura, você encontrará no canto esquerdo da sua fatura, abaixo do logo da VTEX, o nome e endereço da companhia na qual sua loja está sendo faturada.
 
-![reconhecimento fatura](//images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
+![reconhecimento fatura](https://images.ctfassets.net/alneenqid6w5/2YSH0hyY910biHl0uEO1Sw/fedfac90ba460d15c2bac63d80cd1866/reconhecimento_fatura.JPG)
diff --git a/docs/tutorials/pt/new-integration-with-erede-erederest.md b/docs/tutorials/pt/new-integration-with-erede-erederest.md
index 971da63f4..2dde59cd7 100644
--- a/docs/tutorials/pt/new-integration-with-erede-erederest.md
+++ b/docs/tutorials/pt/new-integration-with-erede-erederest.md
@@ -25,11 +25,11 @@ Para configurar a nova versão, você precisa primeiro solicitar à Rede a ativa
 
 Uma vez notificado, acesse o menu __e.Rede > Configurações > Geração de token__.
 
-![GerarToken](//images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
+![GerarToken](https://images.ctfassets.net/alneenqid6w5/2W5UP5c9EIwe4Ayaa8kk0k/835f7771328d57ae7ed764fbcbf340aa/GerarToken.png)
 
 Depois, basta clicar no botão __Gerar Token__.
 
-![GerarToken Click](//images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
+![GerarToken Click](https://images.ctfassets.net/alneenqid6w5/36eVS4dU3CMa0qqiuaaICg/5e2e2f8e9bba46837ad973914c40d222/GerarToken_Click.png)
 
 Com isso, você vai poder visualizar o token que deverá ser informado no formulário de configuração da afiliação de gateway ERedeRest. Além do token, você também vai precisar informar o PV, que nada mais é do que o número de identificação do estabelecimento no site da Rede.
 
@@ -39,10 +39,10 @@ Para fazer essa configuração na VTEX, siga os passos abaixo:
 2. Em __Configurações__, acesse __Afiliações de Gateways__; 
 3. Clique no botão verde __+__ _Quero receber pagamento pelo conector..._ e procure o conector __ERedeRest.__
 
-![erederestPT](//images.ctfassets.net/alneenqid6w5/3RvR1eS0FWKyS8ImoQOk4I/13563c566f5f599885fc2f7759c6d826/erederestPT.jpg)
+![erederestPT](https://images.ctfassets.net/alneenqid6w5/3RvR1eS0FWKyS8ImoQOk4I/13563c566f5f599885fc2f7759c6d826/erederestPT.jpg)
 
-![erederestPT-config](//images.ctfassets.net/alneenqid6w5/6ZD1t6RKfe468MASAycWEg/b38d8ecd1c455d09f82bceeb0317cfeb/erederestPT-config.jpg)
+![erederestPT-config](https://images.ctfassets.net/alneenqid6w5/6ZD1t6RKfe468MASAycWEg/b38d8ecd1c455d09f82bceeb0317cfeb/erederestPT-config.jpg)
 
-![PegarPV](//images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
+![PegarPV](https://images.ctfassets.net/alneenqid6w5/5YuBm2nzkQ8oeqmGKGwUOy/fbadf9ac541985fce57139e764a4d0ed/PegarPV.png)
 
 Este novo conector oferece uma série de opções de configuração, entre elas o suporte ao ApplePay.
diff --git a/docs/tutorials/pt/new-my-orders-area.md b/docs/tutorials/pt/new-my-orders-area.md
index 4cd01d126..e0b07c019 100644
--- a/docs/tutorials/pt/new-my-orders-area.md
+++ b/docs/tutorials/pt/new-my-orders-area.md
@@ -24,28 +24,28 @@ Como a nova estrutura de páginas é completamente diferente, será necessário
 
 A VTEX busca usar uma stack moderna para criar produtos que atendam cada vez melhor ao mercado de e-commerce. Por essa razão, começamos a usar a library React JS em nossas features mais recentes: a nova página de **Meus Pedidos** é um exemplo. Ela vem com novas features e novo design, e foi criada do zero usando React. 
 
-![Tela de listagem do novo Meus Pedidos](//images.contentful.com/alneenqid6w5/5iEOW4etrGO208I4gMiqmq/3db31b5565b297daff34247be23dc7f0/my-orders-blog-1.png)
+![Tela de listagem do novo Meus Pedidos](https://images.contentful.com/alneenqid6w5/5iEOW4etrGO208I4gMiqmq/3db31b5565b297daff34247be23dc7f0/my-orders-blog-1.png)
 
 ### Nova experiência de navegação
 
 O React não foi escolhido apenas para ficar alinhado com a nova plataforma da VTEX — por ser uma single-page application carregada dentro da loja, a nova área de pedidos possui uma navegação suave, com uma experiência muito melhor para o usuário.
 
-![Navegação Meus Pedidos](//images.contentful.com/alneenqid6w5/6LN7wTA0k8maaaGGwicqkG/cb11a2c95c14d9c707e5c2a50de3ffd5/MOg.gif)
+![Navegação Meus Pedidos](https://images.contentful.com/alneenqid6w5/6LN7wTA0k8maaaGGwicqkG/cb11a2c95c14d9c707e5c2a50de3ffd5/MOg.gif)
 
 ### Features
 
 Este update no Meus Pedidos vai servir de ponto de partida para novas features nesta seção, mas já traz melhorias nesta primeira versão, como layout mobile-ready e timeline do pedido — que muitas agências implementavam como customização.
 
-![Meus Pedidos mobile & desktop](//images.contentful.com/alneenqid6w5/5PiNAlG8LekCssuiq2kuQ2/28b4d60785682b7b4a53a1583b11c9bf/my-orders-blog-2.png) 
+![Meus Pedidos mobile & desktop](https://images.contentful.com/alneenqid6w5/5PiNAlG8LekCssuiq2kuQ2/28b4d60785682b7b4a53a1583b11c9bf/my-orders-blog-2.png) 
 
-![Detalhes do Pedido](//images.contentful.com/alneenqid6w5/1p3u7cATQAIgyEMAQCsyKa/151bd1aa2063456420a6716b4f6c57ad/my-orders-blog-3.png) 
+![Detalhes do Pedido](https://images.contentful.com/alneenqid6w5/1p3u7cATQAIgyEMAQCsyKa/151bd1aa2063456420a6716b4f6c57ad/my-orders-blog-3.png) 
 
 
 Outra nova feature são as razões pré-definidas de cancelamento, que o cliente pode escolher caso não queria escrever uma razão. Estas opções podem ser facilmente customizadas e traduzidas nas configurações do Portal v2:
 
-![Cancelamento do pedido](//images.contentful.com/alneenqid6w5/4KBPK3bXf2e8aO2MYkikAY/ce0f45e9fc81f778cfbf6c5904b9f39e/my-orders-blog-4.png) 
+![Cancelamento do pedido](https://images.contentful.com/alneenqid6w5/4KBPK3bXf2e8aO2MYkikAY/ce0f45e9fc81f778cfbf6c5904b9f39e/my-orders-blog-4.png) 
 
-![Customizando razões de cancelamento](//images.contentful.com/alneenqid6w5/3Na3wIvSRG6ygy4YgkgICC/24e1ad1513b367326c46a481c0d79bcc/my-orders-blog-5.png)
+![Customizando razões de cancelamento](https://images.contentful.com/alneenqid6w5/3Na3wIvSRG6ygy4YgkgICC/24e1ad1513b367326c46a481c0d79bcc/my-orders-blog-5.png)
 
 Pela primeira vez, estamos suportando também tradução nativa do My Orders para francês!
 
@@ -53,7 +53,7 @@ Pela primeira vez, estamos suportando também tradução nativa do My Orders par
 
 Para não causar problemas de compatibilidade e quebrar customizações, a nova seção de Meus Pedidos vem com um opt-in, que permite que as lojas inicialmente migrem na velocidade em que desejarem. Este opt-in fica no Portal v2, na mesma seção que a customização de razões de cancelamento:
 
-![Opt-in para ativar a nova versão](//images.contentful.com/alneenqid6w5/Nf4NJcrnMWQEay0YmW0IU/af155d35e2db7ab7a8fa8f8e0ec8462e/MO6.png)
+![Opt-in para ativar a nova versão](https://images.contentful.com/alneenqid6w5/Nf4NJcrnMWQEay0YmW0IU/af155d35e2db7ab7a8fa8f8e0ec8462e/MO6.png)
 
 Antes de ativar a nova versão, é possível vê-lá acessando a sua loja pelo ambiente beta (accountname.vtexcommercestable.com.br/account/orders).
 
diff --git a/docs/tutorials/pt/new-route.md b/docs/tutorials/pt/new-route.md
index a23d46452..7f46b1b73 100644
--- a/docs/tutorials/pt/new-route.md
+++ b/docs/tutorials/pt/new-route.md
@@ -95,5 +95,5 @@ Remover entregas clicando  no __X__ à direta da entrega.
 Só é possível editar uma rota se ela ainda estiver no status Ativo. Não é indicado alterar uma rota se ela já foi iniciada - isso pode causar inconsistências na plataforma do VTEX Tracking e no aplicativo do portador.
 </div>
 
-![Cadastro de nova rota](//images.ctfassets.net/alneenqid6w5/3m2JhopNd3vcscWEOYSnvn/f739888039df88f13fc7bcab16325253/Nova_Rota.gif)
+![Cadastro de nova rota](https://images.ctfassets.net/alneenqid6w5/3m2JhopNd3vcscWEOYSnvn/f739888039df88f13fc7bcab16325253/Nova_Rota.gif)
 
diff --git a/docs/tutorials/pt/offer-details.md b/docs/tutorials/pt/offer-details.md
index 13789df2e..e8d3c41d0 100644
--- a/docs/tutorials/pt/offer-details.md
+++ b/docs/tutorials/pt/offer-details.md
@@ -42,7 +42,7 @@ O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="
 
 ## Cabeçalho
 
-![Offer details PT cabecalho](//images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/1d3d99d4aa6204871518904c7abbef2b/Offer_details_PT_cabecalho.jpg)
+![Offer details PT cabecalho](https://images.ctfassets.net/alneenqid6w5/6XRh7RmJr7rfGUfVHER580/1d3d99d4aa6204871518904c7abbef2b/Offer_details_PT_cabecalho.jpg)
 
 O cabeçalho traz algumas informações principais do anúncio para rápida visualização, como imagem, canal nome, status, ID na VTEX e ID no canal. Permite também realizar as seguintes interações por meio do botão `Editar`:
 
@@ -58,13 +58,13 @@ O bloco de _Status do anúncio_ traz mais detalhes sobre o status do anúncio, q
 
 ### Status: Sincronizado
 
-![Offer details PT status sucesso](//images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/ee786de0eeee54fd2f5ee39fbc4e9d2e/Offer_details_PT_status_sucesso.jpg)
+![Offer details PT status sucesso](https://images.ctfassets.net/alneenqid6w5/6s1o33PAsB6H7X3Z0UJxaY/ee786de0eeee54fd2f5ee39fbc4e9d2e/Offer_details_PT_status_sucesso.jpg)
 
 O status *Sincronizado* significa que o anúncio foi recebido com sucesso em um canal e está sendo atualizado tanto pelo marketplace quanto pelo seller, em tempo real.   
 
 ### Status: Erro
 
-![Offer details PT status erro](//images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/99e44f5378b0fcec010e122d48c2ad12/Offer_details_PT_status_erro.jpg)
+![Offer details PT status erro](https://images.ctfassets.net/alneenqid6w5/5M2tBMrTbrBloZ1093Jdjw/99e44f5378b0fcec010e122d48c2ad12/Offer_details_PT_status_erro.jpg)
 
 O status *Erro* significa que o sistema encontrou um problema que previne um anúncio de ser enviado ou atualizado em um canal, portanto é necessário que o seller o corrija. Erros podem originar do lado do seller VTEX, como descrições de produtos que excedem o limite de caracteres, e do lado do marketplace, como chamadas de API que falharam.   
 
@@ -82,19 +82,19 @@ Se ainda existirem erros para serem corrigidos, ou se todos forem corrigidos mas
 
 ### Status: Indisponível
 
-![Offer details PT status indisponivel](//images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/89c9d4be9f3ce73bc9d39c462895588e/Offer_details_PT_status_indisponivel.jpg)
+![Offer details PT status indisponivel](https://images.ctfassets.net/alneenqid6w5/5ASZDWJU36WcdTJPL4HyWh/89c9d4be9f3ce73bc9d39c462895588e/Offer_details_PT_status_indisponivel.jpg)
 
 O status *Indisponível* ocorre quando o anúncio é descartado, por estar inativo ou não incluído na [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) determinada para o canal.
 
 ### Status: Enviando
 
-![Offer details PT status enviando](//images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/e0d021f8201b4188eb386d6de06bf4e5/Offer_details_PT_status_enviando.jpg)
+![Offer details PT status enviando](https://images.ctfassets.net/alneenqid6w5/4sIUmJ2FxZ02SlOCPNYEi6/e0d021f8201b4188eb386d6de06bf4e5/Offer_details_PT_status_enviando.jpg)
 
 O status *Enviando* é um estado intermediário, quando anúncios ainda estão no processo de envio para o canal. Esse status envolve anúncios que estão sendo enviados pela primeira vez ao marketplace, estão migrando para um novo canal, ou foram reenviados após serem descartados em um canal.   
 
 ## Lista de Interações
 
-![Offer details PT lista interacoes](//images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/323c0c9d2a17e850dca69cc70a4a00fb/Offer_details_PT_lista_interacoes.jpg)
+![Offer details PT lista interacoes](https://images.ctfassets.net/alneenqid6w5/78sdw5zgXZJL8aM9wMKqVE/323c0c9d2a17e850dca69cc70a4a00fb/Offer_details_PT_lista_interacoes.jpg)
 
 A lista de *Interações* reúne todas as atualizações de `estoque`, `preço` ou `catálogo` que aquele SKU sofreu. É possível filtrar por origem e por status, além de ajustar quantos itens são mostrados por página. Cada linha corresponde a uma interação ocorrida àquele anúncio, e inclui os seguintes dados:
 
diff --git a/docs/tutorials/pt/offer-management.md b/docs/tutorials/pt/offer-management.md
index aa817520b..ea4a8cdd6 100644
--- a/docs/tutorials/pt/offer-management.md
+++ b/docs/tutorials/pt/offer-management.md
@@ -24,17 +24,17 @@ Para os conectores com interesse em iniciar a integração, solicitamos que agua
 
 O módulo **Gerenciamento de anúncios** permite aos sellers acompanhar o envio e a sincronização de anúncios de integrações com canais de venda. Na VTEX, anúncio é um SKU de um seller que teve seu preço e estoque configurados e foi enviado para um canal de venda.
 
-![Offer Management gif](//images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
+![Offer Management gif](https://images.ctfassets.net/alneenqid6w5/39zPddPF6cBtI1QZn7GSDz/d270dd62f2b92f6100de71836279b195/Offer_Management_gif.gif)
 
 O **Gerenciamento de anúncios** permite acompanhar anúncios com o [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic e Premium), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e marketplaces VTEX. Para conectores que desejam integrar via API, existe o [Guia de integração do Gerenciamento de anúncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 Para acessar o módulo, no Admin VTEX, acesse **Marketplace > Conexões > Gerenciamento de anúncios**. Feito isso, a seguinte interface vai aparecer: 
 
-![gerenciamentodeanúncios front](//images.ctfassets.net/alneenqid6w5/u8R35ILY4A5G79HWKj7cg/cf4fe5a5145955d4f8955faf3ae47dee/gerenciamentodean__ncios_front.JPG)
+![gerenciamentodeanúncios front](https://images.ctfassets.net/alneenqid6w5/u8R35ILY4A5G79HWKj7cg/cf4fe5a5145955d4f8955faf3ae47dee/gerenciamentodean__ncios_front.JPG)
 
 A interface da **Gerenciamento de anúncios** apresenta uma listagem dos seus anúncios, sendo possível clicar sobre o anúncio para acessar [detalhes do anúncio](https://help.vtex.com/pt/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) e conferir [detalhes da interação](https://help.vtex.com/pt/tutorial/detalhes-da-interacao--5qC6XPkyUsYPd0dqKHQNlf). As interações são os registros do anúncio ao longo do processo de sincronização e envio para o canal de venda, e ficam disponíveis para consulta por dez dias.
 
-![diagrama ju meyer sent offers pt](//images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/c87303d8811c779c9ae72e9ee97df409/diagrama_ju_meyer_sent_offers_pt.png)
+![diagrama ju meyer sent offers pt](https://images.ctfassets.net/alneenqid6w5/1v1nQSOtb5hekGMB4sQCiW/c87303d8811c779c9ae72e9ee97df409/diagrama_ju_meyer_sent_offers_pt.png)
 
 Na página **Gerenciamento de anúncios**, é possível realizar as seguintes ações:
 
diff --git a/docs/tutorials/pt/offer-quality-filters.md b/docs/tutorials/pt/offer-quality-filters.md
index 05cb4488d..bd5f73fd2 100644
--- a/docs/tutorials/pt/offer-quality-filters.md
+++ b/docs/tutorials/pt/offer-quality-filters.md
@@ -21,7 +21,7 @@ Marketplaces precisam revisar e aprovar anúncios enviados por sellers para que
 
 **Filtros de qualidade dos anúncios** é a página onde marketplaces cadastram e gerenciam os grupos de requisitos aplicados ao processo de catalogação de SKUs recebidos. Para acessá-la, em seu Admin VTEX, vá para **Marketplace > Qualidade dos Anúncios** ou digite __“Qualidade dos anúncios”__ na barra de busca.
 
-![PT offer quality](//images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/d51603a30cf92b54035d2229ae23792a/PT_offer_quality.png)
+![PT offer quality](https://images.ctfassets.net/alneenqid6w5/7GL1AaqkfQqjLCj262wg04/d51603a30cf92b54035d2229ae23792a/PT_offer_quality.png)
 
 Nesse artigo, saiba como:
 
@@ -47,7 +47,7 @@ A funcionalidade permite ao operador de marketplace realizar uma série de açõ
 
 ## Visualizar "Default requirements"
 
-![PT Default requirements](//images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/7b191f93fedb9f951939925e481c473b/PT_Default_requirements.png)
+![PT Default requirements](https://images.ctfassets.net/alneenqid6w5/6OxPTO8QO6o9zZ8kTt5tVG/7b191f93fedb9f951939925e481c473b/PT_Default_requirements.png)
 
 A página já vem por padrão com alguns requisitos pré-cadastrados que serão aplicados a todas as categorias, sellers e marcas, chamados de "Default requirements", ou Regras padrão. Alguns desses critérios são configurados nativamente no [VTEX Matcher](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), a ferramenta aplicada aos marketplaces VTEX para auxiliar no processo de catalogação de anúncios recebidos. 
 
diff --git a/docs/tutorials/pt/offer-status.md b/docs/tutorials/pt/offer-status.md
index 91fab67dd..69209301d 100644
--- a/docs/tutorials/pt/offer-status.md
+++ b/docs/tutorials/pt/offer-status.md
@@ -19,11 +19,11 @@ subcategory: 2zVauFUkYn8vgS0y0MfWeK
 
 O **Status de anúncios** permite acompanhar anúncios enviados somente a marketplaces VTEX. Para encontrar o módulo no Admin VTEX, acesse **Marketplace > Conexões > Status de anúncios,** ou digite **Status de anúncios** na barra de busca. Feito isso, a seguinte página aparecerá:  
 
-![Tela Offer Status](//downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/e007c56b38b37f10eb1765dcef3d4945/-PT-_Offer_Status_-_GIF.gif)
+![Tela Offer Status](https://downloads.ctfassets.net/alneenqid6w5/5elFaSW31IgANpXseTApPo/e007c56b38b37f10eb1765dcef3d4945/-PT-_Offer_Status_-_GIF.gif)
 
 A página **Status de anúncios** é composta por três abas, a [**aba Publicados**](#aba-publicados), a [**aba Problemas**](#aba-problemas) e a [**aba Aguardando conclusão**](#aba-aguardando-conclusao), todas apresentam uma listagem de seus anúncios conforme o status que ele se encontra. Em cada anúncio é possível acessar e conferir seus detalhes, que mostram o status, o estoque, preço, data de atualização e motivos de rejeição no marketplace.  
 
-![Fluxo offer status](//images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/bfc7e29ba2f46edfb6c795f5329ce349/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.002.png)  
+![Fluxo offer status](https://images.ctfassets.net/alneenqid6w5/mC78m1ROUDWruOE5V5XEk/bfc7e29ba2f46edfb6c795f5329ce349/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.002.png)  
 
 ## Aba Publicados
 
@@ -50,7 +50,7 @@ Para filtrar os anúncios por **Marketplace**, clique na seta para baixo ao lado
 
 Para filtrar os anúncios por **Estoque**, clique na seta para baixo ao lado do filtro, depois digite o número de estoque mínimo, estoque máximo, ou ambos, e clique em **APLICAR**.  
 
-![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/483a898afda9f9ec5121f7ff566de49e/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.003.png)
+![Filtro estoque offer status](https://images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/483a898afda9f9ec5121f7ff566de49e/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.003.png)
 
 Para filtrar os anúncios por **Atualização**, clique na seta para baixo ao lado do filtro, selecione uma das opções e clique em **APLICAR.**  
 
@@ -59,7 +59,7 @@ Veja abaixo as opções disponíveis para esse filtro:
 - **Atualizado**: são anúncios que tiveram seu preço e/ou estoque atualizados pelo seller e obtiveram sucesso no processamento.  
 - **Erro ao atualizar:** são anúncios processados após atualização e, tendo sido encontrada alguma inconsistência, ele apresenta erro para atualizar.  
 
-![Filtro atualizado offer status](//images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/715b713a9e23057cd281e869f5d33959/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.004.png)
+![Filtro atualizado offer status](https://images.ctfassets.net/alneenqid6w5/VBAg96YrCwBHB358eJS7r/715b713a9e23057cd281e869f5d33959/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.004.png)
 
 Você pode utilizar um único filtro ou combiná-los em uma mesma busca. Por padrão, os filtros não estarão selecionados, de forma que a página inicial apresenta a quantidade total de anúncios existentes.  
 
@@ -102,7 +102,7 @@ Para atualizar qualquer informação de um anúncio já publicado, o seller deve
 
 Você será redirecionado à página correspondente para realizar as alterações necessárias.  
 
-![Ações offer status](//images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/7dc3f62846ca6a28768fe9bc6faddc9d/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.006.jpeg)
+![Ações offer status](https://images.ctfassets.net/alneenqid6w5/3SzA8sqcAKJx2L4GrdLcQ2/7dc3f62846ca6a28768fe9bc6faddc9d/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.006.jpeg)
 
 ### Exportar lista de anúncios publicados
 
@@ -139,7 +139,7 @@ Para filtrar os anúncios por **Envio**, clique na seta para baixo ao lado do fi
 
 Para filtrar os anúncios por **Estoque**, clique na seta para baixo ao lado do filtro, depois digite o número de estoque mínimo ou estoque máximo, ou, ambos e clique em **APLICAR**.  
 
-![Filtro estoque offer status](//images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/483a898afda9f9ec5121f7ff566de49e/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.003.png)
+![Filtro estoque offer status](https://images.ctfassets.net/alneenqid6w5/p6cXcm4zP1pYWyTGbQcoE/483a898afda9f9ec5121f7ff566de49e/Aspose.Words.978c189a-0715-46de-a85d-4a215e29140f.003.png)
 
 Você pode utilizar um único filtro ou combiná-los em uma mesma busca. Por padrão, os filtros não estarão selecionados, de forma que a página inicial apresenta a quantidade total de anúncios existentes.  
 
diff --git a/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md b/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
index 7b108f79f..8dfc6575c 100644
--- a/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
+++ b/docs/tutorials/pt/offers-sent-from-the-same-vtex-sellers-and-marketplaces.md
@@ -23,7 +23,7 @@ Por padrão, é necessário que o produto que será enviado do seller também po
 
 A imagem a seguir representa um exemplo, no qual o Seller A envia um produto para o Marketplace A. Caso o Marketplace A possua em seu próprio estoque o mesmo produto que o Seller A enviou, então ele poderá enviar esse item ao marketplace B.
 
-![erro-envio-skus-sellers-marketplaces-docnovo](//images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
+![erro-envio-skus-sellers-marketplaces-docnovo](https://images.ctfassets.net/alneenqid6w5/3T528zwESuAVeiJXJWpFME/bb694301be01d46ac0d33ced3016da01/erro-envio-skus-sellers-marketplaces-docnovo.JPG)
 
 Marketplaces com esse modelo de negócios são beneficiados porque poderão expandir seu sortimento em canais de vendas terceiros gerando mais oportunidades de vendas.
 
diff --git a/docs/tutorials/pt/oms-page-structure.md b/docs/tutorials/pt/oms-page-structure.md
index 49b5ebfa9..7bb29494d 100644
--- a/docs/tutorials/pt/oms-page-structure.md
+++ b/docs/tutorials/pt/oms-page-structure.md
@@ -37,7 +37,7 @@ Para todos os dados de variações de pedidos, e também para os números de evo
 Importante: se a comparação de pedidos é feita com base em 0 pedidos no passado, a variação é de 0%.
 </div>
 
-![barra-de-status-oms pt](//images.ctfassets.net/alneenqid6w5/4LWth3g02ACyIe4kAAgaW4/375d254b73d0fe7a0b2ae42da0a35b12/barra_de_status_pt.png)
+![barra-de-status-oms pt](https://images.ctfassets.net/alneenqid6w5/4LWth3g02ACyIe4kAAgaW4/375d254b73d0fe7a0b2ae42da0a35b12/barra_de_status_pt.png)
 
 ### Filtros
 
@@ -45,7 +45,7 @@ Permitem aplicar diversos filtros para ver somente a listagem de pedidos desejad
 
 - [Como filtrar pedidos](/pt/tutorial/como-filtrar-pedidos/)
 
-![botao-filtro-oms pt ](//images.ctfassets.net/alneenqid6w5/5BeUtetKIoIOqqCeQqkwOe/7fcc082340475f487e58de9c5d162c27/filtro_pt.png)
+![botao-filtro-oms pt ](https://images.ctfassets.net/alneenqid6w5/5BeUtetKIoIOqqCeQqkwOe/7fcc082340475f487e58de9c5d162c27/filtro_pt.png)
 
 ### Barra de busca
 
@@ -53,7 +53,7 @@ Utilizada para fazer buscas sobres os termos encontrados no pedido, como número
 
 - [Como buscar pedidos](/pt/tutorial/como-buscar-o-pedido/)
 
-![barra-de-busca-oms pt](//images.ctfassets.net/alneenqid6w5/5n7vRoP7ws8ScEuukOG86G/0860905754f93c79af9d01ff1d8af114/barra_de_busca_pt.png)
+![barra-de-busca-oms pt](https://images.ctfassets.net/alneenqid6w5/5n7vRoP7ws8ScEuukOG86G/0860905754f93c79af9d01ff1d8af114/barra_de_busca_pt.png)
 
 ### Barra de informações
 
@@ -63,7 +63,7 @@ Traz também o ranking de vendas da loja em relação a todas as outras lojas da
 
 - [Interpretando os dados da barra de pedidos na tela de Todos os Pedidos.](http://help.vtex.com/pt/tutorial/interpretando-os-dados-da-barra-de-pedidos-do-oms) 
 
-![barra-de-info-oms pt](//images.ctfassets.net/alneenqid6w5/5yArBUQd9emIc0iA8e8Meq/74cc0ed8d9b7d6ab7b4dc48c44a79e96/barra_de_info_pt.png)
+![barra-de-info-oms pt](https://images.ctfassets.net/alneenqid6w5/5yArBUQd9emIc0iA8e8Meq/74cc0ed8d9b7d6ab7b4dc48c44a79e96/barra_de_info_pt.png)
 
 ### Botão de exportação
 
@@ -71,7 +71,7 @@ Utilizado para exportar os pedidos retornados na busca, sempre considerando os f
 
 - [Exportar pedidos em Gerenciamento de pedidos](http://help.vtex.com/pt/tutorial/exportando-pedidos-no-oms-2) 
 
-![botao-exportação-oms pt ](//images.ctfassets.net/alneenqid6w5/2GJezm4WzmIOig8mkmekAy/525184bd7f438e74e609feea092ec98e/botao_exporta____o_pt.png)
+![botao-exportação-oms pt ](https://images.ctfassets.net/alneenqid6w5/2GJezm4WzmIOig8mkmekAy/525184bd7f438e74e609feea092ec98e/botao_exporta____o_pt.png)
 
 ### Lista de pedidos
 
@@ -79,7 +79,7 @@ Principal área de Gerenciamento de pedidos. Traz os últimos pedidos realizados
 
 - [Lista de pedidos](/pt/tutorial/lista-de-pedidos/)
 
-![todos-pedidos-oms pt](//images.ctfassets.net/alneenqid6w5/VIquxEKz8kK4uEqOkWIUK/7fa197e58df4996da0f9e9b957bf0dcd/todos_os_pedidos_pt.png)
+![todos-pedidos-oms pt](https://images.ctfassets.net/alneenqid6w5/VIquxEKz8kK4uEqOkWIUK/7fa197e58df4996da0f9e9b957bf0dcd/todos_os_pedidos_pt.png)
 
 ### VTEX DO
 
@@ -87,7 +87,7 @@ Reúne tarefas pendentes pela loja e são geradas pelos diferentes módulos da V
 
 - [Como funciona a lista de tarefas do VTEX DO](http://help.vtex.com/pt/tutorial/vtex-do)
 
-![vtex-do-oms pt](//images.ctfassets.net/alneenqid6w5/JkifTR1dyCUC8SIASwmws/35a6dcac6626553ea08a4492c526f965/vtex_do_pt.png)
+![vtex-do-oms pt](https://images.ctfassets.net/alneenqid6w5/JkifTR1dyCUC8SIASwmws/35a6dcac6626553ea08a4492c526f965/vtex_do_pt.png)
 
 ## Assinaturas
 
@@ -105,5 +105,5 @@ A segunda aba, **Afiliados**, é destinada para configurações de afiliados em
 
 - [Configurar Afiliado](http://help.vtex.com/pt/tutorial/como-configurar-afiliado/)
 
-![oms-configurações-gerais pt](//images.ctfassets.net/alneenqid6w5/T2R9jSftMAa66ukO864Wy/235af9b18deb16fc1e187b1da5752318/oms_configura____es_pt.png)
+![oms-configurações-gerais pt](https://images.ctfassets.net/alneenqid6w5/T2R9jSftMAa66ukO864Wy/235af9b18deb16fc1e187b1da5752318/oms_configura____es_pt.png)
 
diff --git a/docs/tutorials/pt/opening-hours-suiteshare.md b/docs/tutorials/pt/opening-hours-suiteshare.md
index 32bfd0a95..6c6c0aac0 100644
--- a/docs/tutorials/pt/opening-hours-suiteshare.md
+++ b/docs/tutorials/pt/opening-hours-suiteshare.md
@@ -24,7 +24,7 @@ Além de organizar e distribuir os atendimentos, você pode definir horários de
 - [**Sequencial**](https://help.vtex.com/pt/tutorial/sequencial--212r1PKHPGdpbbRlpf2gY3): o atendente não receberá clientes durante o período.  
 - [**Geolocalizado**](https://help.vtex.com/pt/tutorial/geolocalizado--6XIfgaqXaPe5exQa9oVp6D): o atendente ou loja não receberão clientes durante o período. 
 
-![horario_suitshare_1](//images.ctfassets.net/alneenqid6w5/5SYhzGHjrNpxQbrJ93Op0b/388d8adf88bb0d50c43cccaa34bde610/horario_suitshare_1.png)
+![horario_suitshare_1](https://images.ctfassets.net/alneenqid6w5/5SYhzGHjrNpxQbrJ93Op0b/388d8adf88bb0d50c43cccaa34bde610/horario_suitshare_1.png)
 
 <div class="alert alert-warning">
   <p><b>Nota</b>: Para configurar o horário de atendimento você deve ter organizado seu atendimento de forma seletiva, sequencial ou geolocalizado.</p>
@@ -32,13 +32,13 @@ Além de organizar e distribuir os atendimentos, você pode definir horários de
 
 Acesse o **link âncora** que irá distribuir os atendimentos. 
 
-![horario_suitshare_2](//images.ctfassets.net/alneenqid6w5/1X3ZPHRxpt7z4KfnY9f7nn/e3e184e88340561d6df75955983ea705/horario_suitshare_2.png)
+![horario_suitshare_2](https://images.ctfassets.net/alneenqid6w5/1X3ZPHRxpt7z4KfnY9f7nn/e3e184e88340561d6df75955983ea705/horario_suitshare_2.png)
 
 Defina o horário de atendimento clicando no **botão de relógio** localizado a frente do nome de cada um dos atendentes. 
 
-![horario_suitshare_3](//images.ctfassets.net/alneenqid6w5/7376i6E6WK77Ic2yFQAB2L/39bb1a2795ff771b32c26e6dc7c7d4f3/horario_suitshare_3.png)
+![horario_suitshare_3](https://images.ctfassets.net/alneenqid6w5/7376i6E6WK77Ic2yFQAB2L/39bb1a2795ff771b32c26e6dc7c7d4f3/horario_suitshare_3.png)
 
-![horario_suitshare_4](//images.ctfassets.net/alneenqid6w5/4Wf7YIwXrwTE4InVBvoy4n/3a3961c1508758b73776cb7a071ab70a/horario_suitshare_4.png)
+![horario_suitshare_4](https://images.ctfassets.net/alneenqid6w5/4Wf7YIwXrwTE4InVBvoy4n/3a3961c1508758b73776cb7a071ab70a/horario_suitshare_4.png)
 
 <div class="alert alert-danger">
   <p>A disponibilidade padrão de todos os atendentes está configurada para 24 horas. Dessa forma, qualquer modificação deve ser feita de forma individual.</p>
@@ -46,7 +46,7 @@ Defina o horário de atendimento clicando no **botão de relógio** localizado a
 
 Defina os dias disponíveis e horários de cada atendente. 
 
-![horario_suitshare_1](//images.ctfassets.net/alneenqid6w5/7JZAm3Es0UcANnxWLFGX64/a6d41e127452b6b1f0cbb2e68810368c/horario_suitshare_gif.gif)
+![horario_suitshare_1](https://images.ctfassets.net/alneenqid6w5/7JZAm3Es0UcANnxWLFGX64/a6d41e127452b6b1f0cbb2e68810368c/horario_suitshare_gif.gif)
 
 Clique no botão **Finalizar**. 
 
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
index aabe9fd76..755945565 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
@@ -35,7 +35,7 @@ Depois de se autenticar pelo método escolhido, você entra no painel de suporte
 
 Para abrir um chamado, basta clicar no botão __Enviar uma solicitação__.
 
-![chamado financeiro1 PT](//images.ctfassets.net/alneenqid6w5/51uuDEcQzKOkoOUEImoGqO/c8df51e5c79445754b132ca7cef1c12c/chamado_financeiro1_PT.png)
+![chamado financeiro1 PT](https://images.ctfassets.net/alneenqid6w5/51uuDEcQzKOkoOUEImoGqO/c8df51e5c79445754b132ca7cef1c12c/chamado_financeiro1_PT.png)
 
 Você será levado para o formulário de abertura de chamado, onde deve preencher:
 - Seu nome.
@@ -45,7 +45,7 @@ Você será levado para o formulário de abertura de chamado, onde deve preenche
 - O assunto.
 - A descrição da pergunta ou do problema.
 
-![chamado financeiro2 PT](//images.ctfassets.net/alneenqid6w5/7sG4rinPpeuMyMcYsQke0G/10dc27da30681e980219bab1bba1dc0a/chamado_financeiro2_PT.png)
+![chamado financeiro2 PT](https://images.ctfassets.net/alneenqid6w5/7sG4rinPpeuMyMcYsQke0G/10dc27da30681e980219bab1bba1dc0a/chamado_financeiro2_PT.png)
 
 Você pode também incluir anexos, como capturas de telas ou gifs animados que ajudem a descrever o contexto da sua solicitação.
 
@@ -85,7 +85,7 @@ Clicando em __Minhas solicitações__, você vê o histórico de chamados aberto
 
 Se clicar em __Todas as solicitações__, você pode ver o histórico de chamados abertos por quaisquer funcionários da sua loja.
 
-![chamado financeiro3 PT](//images.ctfassets.net/alneenqid6w5/5rFH6THjZSeC2282OGcO0/575bdab938687e35d787bb41e618fee3/chamado_financeiro3_PT.png)
+![chamado financeiro3 PT](https://images.ctfassets.net/alneenqid6w5/5rFH6THjZSeC2282OGcO0/575bdab938687e35d787bb41e618fee3/chamado_financeiro3_PT.png)
 
 ## Os status dos chamados
 
@@ -100,4 +100,4 @@ Depois disso, ele passa pelos status `Aguardando resposta`, `Resolvido` e `Fecha
 
 No seu painel de suporte, você pode filtrar a busca de chamados por status. Para isso, basta usar a caixa de seleção abaixo do botão de envio de solicitação.
 
-![chamado financeiro4 PT](//images.ctfassets.net/alneenqid6w5/66WicNamPYmIWuKGo2ICSC/f45496c0f278e4382098908fcc1ae872/chamado_financeiro4_PT.png)
+![chamado financeiro4 PT](https://images.ctfassets.net/alneenqid6w5/66WicNamPYmIWuKGo2ICSC/f45496c0f278e4382098908fcc1ae872/chamado_financeiro4_PT.png)
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support.md b/docs/tutorials/pt/opening-tickets-to-vtex-support.md
index e931554a9..4621a4a8d 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support.md
@@ -67,7 +67,7 @@ Ao selecionar essa opção de suporte, você precisa preencher as informações
    * *Tenho uma dúvida e gostaria de fazer uma pergunta*
    * *Gostaria de solicitar uma configuração*
 2. No campo **Assunto da solicitação**, preencha com informações relacionadas ao tipo de problema que você precisa de ajuda. Baseada na descrição do seu problema, iremos indicar alguns artigos do [Help Center](https://help.vtex.com/pt/) que podem ajudar a solucionar seu problema. Caso você entenda que nenhum artigo pode ajudar a resolver o problema, siga para o próximo passo.
-![https help.vtex.com pt support](//images.ctfassets.net/alneenqid6w5/1R5JgnPNiJWbG8IDU0MQmm/ae29e8a323aae90c3e6cb11b36baed8d/https___help.vtex.com_pt_support.gif)
+![https help.vtex.com pt support](https://images.ctfassets.net/alneenqid6w5/1R5JgnPNiJWbG8IDU0MQmm/ae29e8a323aae90c3e6cb11b36baed8d/https___help.vtex.com_pt_support.gif)
 3. Clique no botão `Continuar`.
 Você será direcionado para outra página.
 4. No campo **Impacto do problema**, selecione a opção que melhor corresponde ao impacto do problema:
diff --git a/docs/tutorials/pt/operational-capacity-beta.md b/docs/tutorials/pt/operational-capacity-beta.md
index fb9ecd28b..11220fc89 100644
--- a/docs/tutorials/pt/operational-capacity-beta.md
+++ b/docs/tutorials/pt/operational-capacity-beta.md
@@ -29,7 +29,7 @@ O bom gerenciamento da capacidade operacional dos sellers traz os seguintes bene
 
 Ao acessar no Admin VTEX **Envio > Capacidade operacional**, você encontra uma página como a imagem abaixo:
 
-![operational_capacity_image1_PT](//images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/750c0ac19cbb24293a58ccadeb4604b8/operational_capacity_image1_PT.png)
+![operational_capacity_image1_PT](https://images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/750c0ac19cbb24293a58ccadeb4604b8/operational_capacity_image1_PT.png)
 
 <div class="alert alert-warning">
 Os sellers que aparecem na interface são os sellers da sua operação, e eles são previamente configurados pela nossa equipe. Para acrescentar um novo seller, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
@@ -127,7 +127,7 @@ A plataforma tem algumas restrições com relação a <a href="https://help.vtex
 
 O gráfico **Status da capacidade operacional** apresenta, em tempo real, a porcentagem da capacidade do seller que já foi consumida, como na imagem a seguir: 
 
-![operational_capacity_image2_PT](//images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/5a10fcf3a7fc20c4796a0bac0f14eeca/operational_capacity_image2_PT.png)
+![operational_capacity_image2_PT](https://images.ctfassets.net/alneenqid6w5/510RtT3ugOksM3YD5tYSGc/5a10fcf3a7fc20c4796a0bac0f14eeca/operational_capacity_image2_PT.png)
 
 O gráfico apresenta os seguintes períodos:
 
@@ -149,7 +149,7 @@ Para editar o endereço ou o nome de identificação do seller na **Capacidade o
 
 Na seção **Capacidade operacional**, você visualiza as configurações atuais da capacidade operacional do seller para cada dia da semana, como na imagem abaixo:
 
-![operational_capacity_image3_PT](//images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/f8faca5d71b3729e9c5df67b5609753d/operational_capacity_image3_PT.png)
+![operational_capacity_image3_PT](https://images.ctfassets.net/alneenqid6w5/70kbPFFifh8ykCHvIj6vEZ/f8faca5d71b3729e9c5df67b5609753d/operational_capacity_image3_PT.png)
 
 Para alterar essas configurações, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
index 96c5dadaa..f21734143 100644
--- a/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
@@ -53,7 +53,7 @@ Para desabilitar a função __Opções de entrega otimizadas__, siga os passos a
 3. No menu de opções azul localizado na parte superior da página, clique em __Checkout__.
 4. Em __Opções de entrega otimizadas__, clique no botão <i class="fas fa-toggle-off"></i> para desabilitar a opção __Otimizar exibição das opções de entrega__.
 
-![Opções de entrega otimizadas](//images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/1101fc69a729d79465192bca2b331bfe/Op____es_de_entrega_otimizadas.PNG)
+![Opções de entrega otimizadas](https://images.ctfassets.net/alneenqid6w5/4NfLhi5ao5JyVs4mNTwaRu/1101fc69a729d79465192bca2b331bfe/Op____es_de_entrega_otimizadas.PNG)
 
 <ul>
   5. Clique em <b>Salvar</b>.
diff --git a/docs/tutorials/pt/order-flow-and-status.md b/docs/tutorials/pt/order-flow-and-status.md
index b6c63f1df..56e37258e 100644
--- a/docs/tutorials/pt/order-flow-and-status.md
+++ b/docs/tutorials/pt/order-flow-and-status.md
@@ -40,7 +40,7 @@ Para os casos de pedidos incompletos, confira o artigo <a href="https://help.vte
 
 ### Fluxo do marketplace
 
-![pedido_marketplace_pt](//images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/7916b546cd4e92b0bdddf0e9f4a2ec11/pedido_marketplace_pt.png)
+![pedido_marketplace_pt](https://images.ctfassets.net/alneenqid6w5/5XrrV8mQNzqESn0XKJHJW7/7916b546cd4e92b0bdddf0e9f4a2ec11/pedido_marketplace_pt.png)
 
 O fluxo do marketplace está integrado ao fluxo do seller. Quando um pedido que será entregue por um seller externo (não sendo o seller principal) é finalizado, o fluxo visto pelo marketplace é:
 
@@ -57,7 +57,7 @@ Para saber como identificar pedidos que são provenientes de marketplace, consul
 
 ### Fluxo do seller
 
-![pedido_fluxo_seller_pt](//images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/23f611308f135cf4b591991934afac70/pedido_fluxo_seller_pt.png)
+![pedido_fluxo_seller_pt](https://images.ctfassets.net/alneenqid6w5/wAez6nwupt5Fw7OosaTUH/23f611308f135cf4b591991934afac70/pedido_fluxo_seller_pt.png)
 
 Esse é o fluxo do pedido visto pela loja responsável pelo envio dos produtos que compõem o pedido. O pedido foi realizado através de outra loja (o marketplace), e o fluxo do seller é iniciado depois da confirmação do pedido.
 
@@ -95,7 +95,7 @@ Note que:
 
 ### Fluxo completo
 
-![pedido_fluxo_completo_pt](//images.ctfassets.net/alneenqid6w5/5b57cGGmPatcg8TtS1UZvW/8ceb29cc95740b3c4d70574f8bf79ab3/pedido_fluxo_completo_pt.png)
+![pedido_fluxo_completo_pt](https://images.ctfassets.net/alneenqid6w5/5b57cGGmPatcg8TtS1UZvW/8ceb29cc95740b3c4d70574f8bf79ab3/pedido_fluxo_completo_pt.png)
 
 O fluxo completo do pedido é visto pela loja que realiza a venda e entrega do pedido. Ele é composto pelo fluxo de marketplace e o fluxo do seller de forma sequencial.
 
@@ -139,7 +139,7 @@ Para saber mais sobre cancelamento de pedidos, confira o artigo [Por que meu ped
 
 ### Fluxo chain
 
-![pedido_fluxo_chain_pt](//images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/a6129ed22ec48b2506f108951ef6409d/pedido_fluxo_chain_pt.png)
+![pedido_fluxo_chain_pt](https://images.ctfassets.net/alneenqid6w5/1H891HnUzdCfoEVuO3Ry3Q/a6129ed22ec48b2506f108951ef6409d/pedido_fluxo_chain_pt.png)
 
 O fluxo de pedidos visto pela loja da camada intermediária de uma venda em[ Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) é semelhante ao fluxo de pedidos do marketplace, exceto pelo recebimento do pagamento de pedidos. No estágio de `Pagamento pendente`, ao invés do chain receber o pagamento diretamente do Gateway, o que ocorre é que o marketplace informa ao chain que recebeu a confirmação do pagamento. 
 
diff --git a/docs/tutorials/pt/order-in-the-name-of-a-customer-using-the-callcenter.md b/docs/tutorials/pt/order-in-the-name-of-a-customer-using-the-callcenter.md
index 21243893b..637c8674f 100644
--- a/docs/tutorials/pt/order-in-the-name-of-a-customer-using-the-callcenter.md
+++ b/docs/tutorials/pt/order-in-the-name-of-a-customer-using-the-callcenter.md
@@ -21,10 +21,10 @@ A toolbar de televendas aparece uma vez que o operador cadastrado faça o login
 
 Para comprar em nome do cliente pelo televendas, o operador precisa clicar em **Entrar como**, no canto direito da toolbar.
 
-![Operador de televendas personificando cliente com a toolbar](//images.contentful.com/alneenqid6w5/3rWoDmY4paceYWKEW2cg2S/c7edba682c7fd97b25d0fdc01faf1f9b/toolbar-1-1.png)
+![Operador de televendas personificando cliente com a toolbar](https://images.contentful.com/alneenqid6w5/3rWoDmY4paceYWKEW2cg2S/c7edba682c7fd97b25d0fdc01faf1f9b/toolbar-1-1.png)
 
 Feito isso, o e-mail do cliente passa a ser exibido nesta mesma área.
 
 Para logar como outro usuário, basta clicar no botão **Trocar de cliente**.
 
-![Cliente personificado na toolbar](//images.contentful.com/alneenqid6w5/2n3J0YmqxCQq8mW64iQmMG/3e75e00fbeb5fdd0b23dcfc31135e69d/toolbar-2-1.png)
+![Cliente personificado na toolbar](https://images.contentful.com/alneenqid6w5/2n3J0YmqxCQq8mW64iQmMG/3e75e00fbeb5fdd0b23dcfc31135e69d/toolbar-2-1.png)
diff --git a/docs/tutorials/pt/order-to-delivery.md b/docs/tutorials/pt/order-to-delivery.md
index ec9d0e9cc..76a4ae268 100644
--- a/docs/tutorials/pt/order-to-delivery.md
+++ b/docs/tutorials/pt/order-to-delivery.md
@@ -29,7 +29,7 @@ subcategory: 5SE2asHiQtHKfbnFru8RWH
 
 Você pode buscar por um pedido clicando no ícone da lupa 🔍. Você pode clicar em <i class="fas fa-ellipsis-v" alt="elipses"></i> para receber pedidos de outra origem ou gerar um relatório de pedidos.
 
-![Pedidos para entrega - PT](//images.ctfassets.net/alneenqid6w5/6yMDBApwvfHclrY5DS3fVk/d1bad3ebb121029d42034109b5d9154e/Screenshot_2022-06-01_at_17-09-12_Figma.png)
+![Pedidos para entrega - PT](https://images.ctfassets.net/alneenqid6w5/6yMDBApwvfHclrY5DS3fVk/d1bad3ebb121029d42034109b5d9154e/Screenshot_2022-06-01_at_17-09-12_Figma.png)
 
 As categorias de etapas do pedido são as seguintes: 
 
@@ -57,7 +57,7 @@ Cada pedido apresenta as seguintes informações:
 - Tipo de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 - Modalidade de entrega do pedido, como **Expressa** ou **Normal**.
 
-![Preparação - PT](//images.ctfassets.net/alneenqid6w5/4gdmIBJfITnEIkYf68xDjk/c0fc7e138a6bf423b073ee78649b06d7/Screenshot_2022-06-01_at_17-24-04_Figma.png)
+![Preparação - PT](https://images.ctfassets.net/alneenqid6w5/4gdmIBJfITnEIkYf68xDjk/c0fc7e138a6bf423b073ee78649b06d7/Screenshot_2022-06-01_at_17-24-04_Figma.png)
 
 ## Entrega em casa
 A etapa **Entrega em casa** exibe os pedidos que estão em fase de envio para a casa do cliente. Os pedidos são ordenados por prioridade de prazo, ou seja, o pedido com previsão de entrega mais próximo ou atrasado há mais tempo é o primeiro da lista.
@@ -71,7 +71,7 @@ Na aba **Pedidos** são exibidos os pedidos na etapa. Cada pedido apresenta as s
 - ID do pedido.
 - Status atual do pedido, podendo ser **Aguardando criação do envio**, **Aguardando transportadora** ou **Coletado pela transportadora**.
 
-![Entrega em casa - PT](//images.ctfassets.net/alneenqid6w5/4C9M1TGP6cExmF6RICxOR6/090775ac0eacddb8ce7101db419a672e/Screenshot_2022-06-02_at_16-24-36_Figma.png)
+![Entrega em casa - PT](https://images.ctfassets.net/alneenqid6w5/4C9M1TGP6cExmF6RICxOR6/090775ac0eacddb8ce7101db419a672e/Screenshot_2022-06-02_at_16-24-36_Figma.png)
 
 Na aba **Lotes de envio** são exibidas informações de cada envio feito pela loja. São apresentadas as seguintes informações:
 
@@ -79,13 +79,13 @@ Na aba **Lotes de envio** são exibidas informações de cada envio feito pela l
 - Número do lote de envio e nome da transportadora.
 - Status atual do envio, podendo ser **Aguardando transportadora**, **Coletado pela transportadora** ou **Concluído**.
 
-![Entrega em casa - lotes de envio -PT](//images.ctfassets.net/alneenqid6w5/2o1qrINumd4BhrsKCX1YVy/8bd3d3ebb16e344e11a942be97b811b3/Entrega_em_casa_-_lotes_de_envio.png)
+![Entrega em casa - lotes de envio -PT](https://images.ctfassets.net/alneenqid6w5/2o1qrINumd4BhrsKCX1YVy/8bd3d3ebb16e344e11a942be97b811b3/Entrega_em_casa_-_lotes_de_envio.png)
 
 Para criar um novo lote, clique em <i class="fas fa-plus"></i> `Criar lote de envio`.
 
 Ao selecionar um lote de envio será exibido uma tela com os detalhes de cada pedido relacionado a ele. Caso a transportadora responsável pelo envio não esteja integrada com a loja, será exibido um alerta, como na imagem abaixo.
 
-![Lote de envio - PT](//images.ctfassets.net/alneenqid6w5/3dw9uaaJMdMPZQb6q5xqLN/d44731538f9e485360a5af9176812dc0/Screenshot_2022-06-02_at_16-31-42_Figma.png)
+![Lote de envio - PT](https://images.ctfassets.net/alneenqid6w5/3dw9uaaJMdMPZQb6q5xqLN/d44731538f9e485360a5af9176812dc0/Screenshot_2022-06-02_at_16-31-42_Figma.png)
 
 Para confirmar o envio dos pedidos, siga os passos a seguir:
 
@@ -103,7 +103,7 @@ Ao clicar no ícone <i class="fas fa-ellipsis-v"></i> de um pedido, é possível
 
 Clicando em `Informações do envio`, será exibida uma tela com **Status**, **Transportadora**, **Pedidos neste envio** e **Data de criação**.
 
-![Informações do envio - PT](//images.ctfassets.net/alneenqid6w5/132AGJoZVmHLM04lLEkB8B/383a20e3500a3147597af869f47576b9/Screenshot_2022-06-02_at_16-33-50_Figma.png)
+![Informações do envio - PT](https://images.ctfassets.net/alneenqid6w5/132AGJoZVmHLM04lLEkB8B/383a20e3500a3147597af869f47576b9/Screenshot_2022-06-02_at_16-33-50_Figma.png)
 
 Caso a loja não apresente integração com transportadora, será preciso marcar manualmente os pedidos como Entregue quando eles forem entregues ao cliente. Caso exista a integração com a transportadora, os pedidos são marcados como entregues automaticamente.
 
@@ -118,7 +118,7 @@ Cada pedido apresenta as seguintes informações:
 - Em casos de atraso, é indicado quanto tempo a retirada do cliente está atrasada.
 - ID do pedido.
 
-![Retirada na loja - PT](//images.ctfassets.net/alneenqid6w5/5dWy0rBy4GfEb2jVmS0MIE/256dedcced031fcf6717a6404a045a37/Screenshot_2022-06-02_at_16-36-07_Figma.png)
+![Retirada na loja - PT](https://images.ctfassets.net/alneenqid6w5/5dWy0rBy4GfEb2jVmS0MIE/256dedcced031fcf6717a6404a045a37/Screenshot_2022-06-02_at_16-36-07_Figma.png)
 
 ## Recusados
 A etapa **Recusados** exibe os pedidos que foram cancelados pela loja por falta do item no estoque, produto com defeito, entre outros motivos. Os pedidos são ordenados por prioridade de prazo, ou seja, o pedido com previsão de entrega mais próximo ou atrasado há mais tempo é o primeiro da lista.
@@ -133,7 +133,7 @@ Cada pedido apresenta as seguintes informações:
 - Status atual do pedido, podendo ser **Cancelado** ou **Aguardando análise**.
 - Modalidade de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 
-![Recusados - PT](//images.ctfassets.net/alneenqid6w5/6JOEUXqZsrD4Fl4PflbIeU/3295b747e4b5c12bf33d7efa8a5a72c1/Screenshot_2022-06-02_at_16-40-10_Figma.png)
+![Recusados - PT](https://images.ctfassets.net/alneenqid6w5/6JOEUXqZsrD4Fl4PflbIeU/3295b747e4b5c12bf33d7efa8a5a72c1/Screenshot_2022-06-02_at_16-40-10_Figma.png)
 
 ## Devoluções
 A etapa **Devoluções** exibe os pedidos que foram devolvidos pelo cliente. Você pode buscar por um pedido clicando no ícone da lupa 🔍. Cada pedido apresenta as seguintes informações:
@@ -142,7 +142,7 @@ A etapa **Devoluções** exibe os pedidos que foram devolvidos pelo cliente. Voc
 - Data e horário de quando o pedido foi devolvido.
 - Modalidade de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 
-![Devoluções - PT](//images.ctfassets.net/alneenqid6w5/sI6uA75Ms3LQHAkaCF1ts/0a0e7b5140d72fb78053f9a894fff0ff/Screenshot_2022-06-02_at_17-09-08_Figma.png)
+![Devoluções - PT](https://images.ctfassets.net/alneenqid6w5/sI6uA75Ms3LQHAkaCF1ts/0a0e7b5140d72fb78053f9a894fff0ff/Screenshot_2022-06-02_at_17-09-08_Figma.png)
 
 ## Entregues
 A etapa Entregues exibe os pedidos que foram finalizados e entregues ao cliente. Você pode buscar por um pedido clicando no ícone da lupa 🔍. Cada pedido apresenta as seguintes informações:
@@ -151,4 +151,4 @@ A etapa Entregues exibe os pedidos que foram finalizados e entregues ao cliente.
 - Tipo de entrega, podendo ser **Retirada na loja** ou **Entrega em casa**.
 - Modalidade de entrega do pedido, como **Expressa** ou **Normal**.
 
-![Entregues - PT](//images.ctfassets.net/alneenqid6w5/5GJhMUquRRYWAo9zRtZtst/62aaef737462a4f77cd37c025cdbbed5/Screenshot_2022-06-02_at_17-22-45_Figma.png)
+![Entregues - PT](https://images.ctfassets.net/alneenqid6w5/5GJhMUquRRYWAo9zRtZtst/62aaef737462a4f77cd37c025cdbbed5/Screenshot_2022-06-02_at_17-22-45_Figma.png)
diff --git a/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md b/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
index 348e203eb..261fa7acd 100644
--- a/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
+++ b/docs/tutorials/pt/ordering-images-on-the-shop-window-display-and-on-the-product-page.md
@@ -29,6 +29,6 @@ Entre as imagens do SKU, a principal será aquela definida no cadastro de imagen
 
 Veja, em nosso exemplo, que mesmo não sendo a primeira imagem cadastrada, a imagem definida como principal é aquela assumida na página de produto quando o cliente seleciona o SKU.
 
-![sku_imagem_principal pt ](//images.ctfassets.net/alneenqid6w5/4ouTS09QkgCMoqSAomMa2O/b56de01d796e9c75736bf51a865ada18/Ex_1_pt.png)
+![sku_imagem_principal pt ](https://images.ctfassets.net/alneenqid6w5/4ouTS09QkgCMoqSAomMa2O/b56de01d796e9c75736bf51a865ada18/Ex_1_pt.png)
 
 - Em caso de upload da planilha de imagens, a plataforma considera linha por linha. Logo, a primeira linha de um SKU será considerada a principal, e assim por diante.
diff --git a/docs/tutorials/pt/orders-list.md b/docs/tutorials/pt/orders-list.md
index e5febd9e0..dd848a442 100644
--- a/docs/tutorials/pt/orders-list.md
+++ b/docs/tutorials/pt/orders-list.md
@@ -17,7 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 É através da lista de pedidos do Gerenciamento de Pedidos que o lojista pode acompanhar as compras concretizadas em sua loja. A listagem está disponível na primeira tela do módulo Gerenciamento de Pedidos.
 
-![todosospedidos.pt](//images.ctfassets.net/alneenqid6w5/RIjd55ovorcC4L2gZ4aFQ/c1f8a9043d1da0e979348951bbbba1e7/todosospedidos.pt.png)
+![todosospedidos.pt](https://images.ctfassets.net/alneenqid6w5/RIjd55ovorcC4L2gZ4aFQ/c1f8a9043d1da0e979348951bbbba1e7/todosospedidos.pt.png)
 
 Na visualização padrão são listados todos os pedidos da loja a partir do mais recente. É possível alterar a ordenação clicando no nome das colunas, assim como buscar ou filtrar os pedidos por dados específicos, e também exportar estes dados.
 
@@ -30,7 +30,7 @@ Ao clicar em qualquer pedido, o usuário é direcionado para a página de detalh
 
 Sempre que o Gerenciamento de Pedidos estiver aberto e novos pedidos forem realizados, uma indicação será exibida, permitindo que se clique para atualizar a lista de pedidos.
 
-![oms novospedidos](//images.contentful.com/alneenqid6w5/764uQcLH1YiGiusQEec8Uc/80cbd9c180ad0c65143ae753b833f8a8/oms-novospedidos.png)
+![oms novospedidos](https://images.contentful.com/alneenqid6w5/764uQcLH1YiGiusQEec8Uc/80cbd9c180ad0c65143ae753b833f8a8/oms-novospedidos.png)
 
 Veja a seguir mais detalhes sobre as colunas da lista:
 
@@ -38,7 +38,7 @@ Veja a seguir mais detalhes sobre as colunas da lista:
 
 Nada mais é do que o número do pedido (exibido ao cliente), o sufixo e o código sequencial da transação (para uso interno).
 
-![oms formato do pedido](//images.contentful.com/alneenqid6w5/60zd69MLTyOk8SW080Mo8o/ebef05cf26d82b3b15aaed852567fe5c/oms-formato-do-pedido.png)
+![oms formato do pedido](https://images.contentful.com/alneenqid6w5/60zd69MLTyOk8SW080Mo8o/ebef05cf26d82b3b15aaed852567fe5c/oms-formato-do-pedido.png)
 
 ### Número do pedido
 
@@ -77,7 +77,7 @@ Traz sempre o nome e o sobrenome do cliente que efetuou a compra, mesmo que o pe
 
 Expõe quantos produtos diferentes existem no pedido (sem considerar a quantidade comprada de cada item). Ao passar o mouse é possível ver quais foram os produtos comprados.
 
-![oms produtos do pedido](//images.contentful.com/alneenqid6w5/4fTIEf2ywwc2U2IuwSkg8U/82b81b00387db8959cf18ae392e5e1f0/oms-produtos-do-pedido.png)
+![oms produtos do pedido](https://images.contentful.com/alneenqid6w5/4fTIEf2ywwc2U2IuwSkg8U/82b81b00387db8959cf18ae392e5e1f0/oms-produtos-do-pedido.png)
 
 ## Valor
 
diff --git a/docs/tutorials/pt/overview-pricing-module.md b/docs/tutorials/pt/overview-pricing-module.md
index 63265a92a..adb5dd28b 100644
--- a/docs/tutorials/pt/overview-pricing-module.md
+++ b/docs/tutorials/pt/overview-pricing-module.md
@@ -21,7 +21,7 @@ Existem quatro departamentos dentro do módulo que são responsáveis pela confi
 
 ## Audiência de campanhas 
 
-![campanha-pt](//images.ctfassets.net/alneenqid6w5/2vEodWRzSkHWdujqLvOxmb/dcd29bb90a3ed684c38d276c07afe80e/campanha-pt.png)
+![campanha-pt](https://images.ctfassets.net/alneenqid6w5/2vEodWRzSkHWdujqLvOxmb/dcd29bb90a3ed684c38d276c07afe80e/campanha-pt.png)
 
 Audiência de campanha é uma forma de definir o público alvo ao qual uma promoção poderá ser aplicada. Ou seja criar segmentos de clientes com base na definição de alguns critérios que serão elegíveis a uma determinada audiência de campanha e consequentemente a uma ou mais promoções. Uma audiências de campanhas pode ser associada a uma ou mais promoções de audiência de campanha.
 
@@ -29,7 +29,7 @@ Audiência de campanha é uma forma de definir o público alvo ao qual uma promo
 
 ## Promoções
 
-![promoções.pt](//images.ctfassets.net/alneenqid6w5/6rXDxtSGLLmGlpBlooTQHk/8094b01bc8fab75b014a0da8cd0db0cf/promo____es.pt.png)
+![promoções.pt](https://images.ctfassets.net/alneenqid6w5/6rXDxtSGLLmGlpBlooTQHk/8094b01bc8fab75b014a0da8cd0db0cf/promo____es.pt.png)
 
 É aqui que os descontos que a sua loja vai oferecer são criados. É possível ainda visualizar, filtrar, buscar e arquivar todas as promoções. De acordo com a configuração de cada loja, existe um limite de promoções que podem estar ativas ao mesmo tempo. 
 
@@ -44,13 +44,13 @@ Para verificar essa quantidade, observe a mensagem que aparece no canto superior
 
 ## Cupons
 
-![cupons.pt](//images.ctfassets.net/alneenqid6w5/7AsIdJZzvmLwI08igAZDj3/233c803c436c8cf6909561aeae2da292/cupons.pt.png)
+![cupons.pt](https://images.ctfassets.net/alneenqid6w5/7AsIdJZzvmLwI08igAZDj3/233c803c436c8cf6909561aeae2da292/cupons.pt.png)
 
 É nesta seção que são criados os cupons. Você também pode buscá-los e arquivá-los. [Aprenda como criar cupons](/pt/tutorial/como-criar-cupom/).
 
 ## Taxas
 
-![taxas.pt](//images.ctfassets.net/alneenqid6w5/6M97ug98KchFim5RsY9nXY/e2a626bc42050616032de314949f0b48/taxas.pt.png)
+![taxas.pt](https://images.ctfassets.net/alneenqid6w5/6M97ug98KchFim5RsY9nXY/e2a626bc42050616032de314949f0b48/taxas.pt.png)
 
 Nesta área serão criados os impostos que incidirão sobre os seus produtos. É permitido também filtrar, buscar e arquivar as taxas. [Entenda melhor as particularidades dessa configuração no artigo sobre taxas](/pt/tutorial/como-criar-taxaimposto/).
 
diff --git a/docs/tutorials/pt/partner-program-intranet-and-vtex-store-manual.md b/docs/tutorials/pt/partner-program-intranet-and-vtex-store-manual.md
index d73def7c7..5f6761ae6 100644
--- a/docs/tutorials/pt/partner-program-intranet-and-vtex-store-manual.md
+++ b/docs/tutorials/pt/partner-program-intranet-and-vtex-store-manual.md
@@ -21,40 +21,40 @@ URL de Acesso: http://extrato.vtex.com
 
 ## Dados cadastrais
 Este é o primeiro passo, nele você deve preencher os dados cadastrais da sua agência. Estes dados serão replicados na VTEX STORE.
-![partner intranet 1](//images.contentful.com/alneenqid6w5/6n5cqrsG3uEuqE0w88882M/87f7eb33ae50e6d0783dc1ea5a121aca/partner_intranet_1.png)
+![partner intranet 1](https://images.contentful.com/alneenqid6w5/6n5cqrsG3uEuqE0w88882M/87f7eb33ae50e6d0783dc1ea5a121aca/partner_intranet_1.png)
 
 ### Cor do Header
 No primeiro passo temos alguns campos que merecem atenção, o primeiro é a cor do header. Onde se aplica? Na VTEX STORE dentro da pagina da sua agencia como é demonstrado ao lado.
-![partner intranet 2](//images.contentful.com/alneenqid6w5/13tICp7cXoiOseM2AOYYEc/aaf98faa4e33f47e517f2204fec9dcd2/partner_intranet_2.png)
+![partner intranet 2](https://images.contentful.com/alneenqid6w5/13tICp7cXoiOseM2AOYYEc/aaf98faa4e33f47e517f2204fec9dcd2/partner_intranet_2.png)
 
 ### Escritórios
 O segundo ponto que merece atenção é a inscrição dos escritórios, ex: São Paulo, Salvador, ou fora do País. Para cada escritório cadastrado terá que ser feito o cadastro dos serviços prestados.
-![partner intranet 3](//images.contentful.com/alneenqid6w5/6JZIkI0N5SKgySUW46W2Yc/64069026123057856b3430bf4e4e5344/partner_intranet_3.png)
+![partner intranet 3](https://images.contentful.com/alneenqid6w5/6JZIkI0N5SKgySUW46W2Yc/64069026123057856b3430bf4e4e5344/partner_intranet_3.png)
 
 ## Minha equipe
 Neste passo você vai cadastrar todas as pessoas da sua agência que devem ter acesso ao nosso ambiente de treinamento e certificação VTEX Partner. (VTEX Academy)
-![partner intranet 4](//images.contentful.com/alneenqid6w5/4AmT9EOi6AC6CUIa6gK8uq/c79b462dad40ededc388903d6de2535c/partner_intranet_4.png)
+![partner intranet 4](https://images.contentful.com/alneenqid6w5/4AmT9EOi6AC6CUIa6gK8uq/c79b462dad40ededc388903d6de2535c/partner_intranet_4.png)
 
 ## Certificações
 Depois que o seu time se certificar, é necessário informar nessa página quais as certificações que você parceiro tem. É importante ressaltar que a VTEX verifica se realmente o parceiro tem a certificação marcada. Caso sim, é exibido o selo conforme a lupa ao lado.
-![partner intranet 5](//images.contentful.com/alneenqid6w5/1Iq4VXwlUQimW0kQmqsIe8/9038bd2510ba516cbc72596a41d7a25f/partner_intranet_5.png)
+![partner intranet 5](https://images.contentful.com/alneenqid6w5/1Iq4VXwlUQimW0kQmqsIe8/9038bd2510ba516cbc72596a41d7a25f/partner_intranet_5.png)
 
 ## Serviços
 Neste passo você deve cadastrar os serviços prestados pela sua agência, os quais temos como padrão: Criação e Implantação de Layout, Gestão de Projeto e Suporte pós-lançamento. Estes serviços irão aparecer na STORE para os clientes VTEX.
-![partner intranet 6](//images.contentful.com/alneenqid6w5/1x3zqdaxMgGU4CKsKi4i8c/8484f7197c8643388a716e0e595f9763/partner_intranet_6.png)
+![partner intranet 6](https://images.contentful.com/alneenqid6w5/1x3zqdaxMgGU4CKsKi4i8c/8484f7197c8643388a716e0e595f9763/partner_intranet_6.png)
 
 ### VTEX Store
 Ao lado conseguimos visualizar a prateleira dos serviços/soluções de acordo com o que escolheu.
-![partner intranet 7](//images.contentful.com/alneenqid6w5/3jJA8IyIkgcEmSYy8W6wam/34407ce97bfcc75431fdc9960d91fd2b/partner_intranet_7.png)
+![partner intranet 7](https://images.contentful.com/alneenqid6w5/3jJA8IyIkgcEmSYy8W6wam/34407ce97bfcc75431fdc9960d91fd2b/partner_intranet_7.png)
 
 ## Extrato
 É no extrato que o responsável pelo financeiro da agência deve acompanhar os valores de comissões de revenda da plataforma VTEX, que são liberadas apenas para agências certificadas Reseller.
-![partner intranet 8](//images.contentful.com/alneenqid6w5/2TB5pCAgr6qKqQmsuY0kgU/47bcbdbf15c7101612dddbc8901a8f99/partner_intranet_8.png)
+![partner intranet 8](https://images.contentful.com/alneenqid6w5/2TB5pCAgr6qKqQmsuY0kgU/47bcbdbf15c7101612dddbc8901a8f99/partner_intranet_8.png)
 
 ## Acesso a Usuários
 Aqui você vai cadastrar todos os usuários que terão acesso a essa ferramenta. Sugerimos que seja uma pessoa do financeiro e uma ou duas pessoas como administradores.
-![partner intranet 9](//images.contentful.com/alneenqid6w5/2aFx9YxuAMOEAEIOOos6Gg/82e8c287becc9b2ccbd9590ce4a6fb6e/partner_intranet_9.png)
+![partner intranet 9](https://images.contentful.com/alneenqid6w5/2aFx9YxuAMOEAEIOOos6Gg/82e8c287becc9b2ccbd9590ce4a6fb6e/partner_intranet_9.png)
 
 ## Canais VTEX
 No menu superior é possível visualizar TODOS nossos canais de comunicação com você, parceiro.
-![partner intranet 10](//images.contentful.com/alneenqid6w5/5Pa8OjOuyWwigKwmqCSK66/96fb124b8400feb3abd78317be03037c/partner_intranet_10.png)
+![partner intranet 10](https://images.contentful.com/alneenqid6w5/5Pa8OjOuyWwigKwmqCSK66/96fb124b8400feb3abd78317be03037c/partner_intranet_10.png)
diff --git a/docs/tutorials/pt/payment-provider-protocol.md b/docs/tutorials/pt/payment-provider-protocol.md
index 3e98ddd9d..f79ac6a6c 100644
--- a/docs/tutorials/pt/payment-provider-protocol.md
+++ b/docs/tutorials/pt/payment-provider-protocol.md
@@ -91,7 +91,7 @@ Há casos em que conectores podem ser construídos para atender alguma solução
 ### 3. Homologação do Payment Provider
 Depois de receber os dados de acesso e implementar o back-end, o provedor deve instalar a app Payment Provider Test Suite para acessar a ferramenta de testes. A instalação é feita por meio de [VTEX App Store](https://apps.vtex.com/vtex-payment-provider-test-suite/p "VTEX App Store"). 
 
-![ppp-vtex-store-pt](//images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d4ba38eb2aed1c4a4072cddbc2b4decf/image.png)
+![ppp-vtex-store-pt](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d4ba38eb2aed1c4a4072cddbc2b4decf/image.png)
 
 <div class="alert alert-warning">
 Para passar no processo de homologação, é necessário implementar uma lógica específica para lidar com os requisitos do teste. Nas requisições enviadas ao Test Suite, utilize o header extra <code>X-VTEX-API-Is-TestSuite = true</code> para identificá-las e mascarar qualquer cenário exigido.<br>Toda comunicação com servidores, seja durante o processo de homologação ou em produção, deve ocorrer via HTTPS, que por padrão utiliza a porta 443. É importante lembrar que toda comunicação HTTPS deve ser exclusivamente sobre TLS 1.2.
@@ -120,7 +120,7 @@ Após preeencher o campo Service URL, o Test Suite irá validar o [endpoint Mani
 
 Nessa seção, você deve selecionar os casos que deseja testar. Se você está testando um método de cartão de crédito, a sua integração deve passar nos casos Approved, Denied, Cancellation, Async Approved e Async Denied. Para um método de pagamento com [redirecionamento](https://developers.vtex.com/docs/guides/payments-integration-purchase-flows#redirect), apenas o Redirect flow é necessário.
 
-![ppp-config-pt](//images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/e41bf6da622195968fe1f91bad8f3b75/image.png)
+![ppp-config-pt](https://images.ctfassets.net/alneenqid6w5/5s70iVRPAnrikX88iv8fn1/e41bf6da622195968fe1f91bad8f3b75/image.png)
 
 ### 4. Testes
 
@@ -150,18 +150,18 @@ Para identificar como responder corretamente a cada um dos testes com cartão de
 ### 5. Resultados
 Após executar os testes, o sistema irá mostrar o Test Report, onde você pode ver os resultados detalhados de cada caso de teste. Desse modo, você tem mais visibilidade sobre o que deve ser ajustado caso ocorra algum erro.
 
-![Payment Provider Test Suite 2](//images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/9ecdf0551940ee02ed6bd21b3b86420e/image.png)
+![Payment Provider Test Suite 2](https://images.ctfassets.net/alneenqid6w5/6o9b9Wz3tSKiU6mwEssEgs/9ecdf0551940ee02ed6bd21b3b86420e/image.png)
 
 Para ver as mensagens transmitidas entre o Test Suite e a implementação do seu provedor de pagamento, clique no botão Inspect Log do caso de teste desejado. Um modal irá se abrir para mostrar a lista de mensagem transmitidas e o payload de cada requisição e resposta. O botão no canto superior direito da seção de código facilita a cópia do código para a área de transferência.
 
-![Payment Provider Test Suite Logs](//images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/369d86cffea42dfbe842d037bfdd065e/image.png)
+![Payment Provider Test Suite Logs](https://images.ctfassets.net/alneenqid6w5/3FCFc1FA7L6ILyXB8NSmA3/369d86cffea42dfbe842d037bfdd065e/image.png)
 
 ## Fluxo do protocolo de pagamento
 Aqui vamos explicar o fluxo de pagamento integrado em detalhes. A imagem abaixo ilustra todo o fluxo, mostrando o fluxo de um pagamento e as responsabilidades do seu fornecedor.
 
 Tudo começa com a solicitação de um novo pagamento, após a criação de um novo pedido. A VTEX cria uma nova representação do pagamento e avança para o processamento dos pagamentos.
 
-![fluxo-atualizado-ppp](//images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
+![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
 
 <div class="alert alert-info">
   O período padrão de 7 dias para novas tentativas de pagamento assíncronas só é aplicado quando o usuário não especifica um valor no campo <code>delayToCancel</code> do endpoint <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> ou ao enviar o callbackURL.</div>
@@ -178,7 +178,7 @@ Seja qual for o caso, uma vez que o processamento termine e o provedor tenha um
 
 O fluxo completo com status undefined e uso de notificação pode ser visto abaixo:
 
-![Payment authorization callback notification flow](//images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/90500ae3bc824ff831193cf7cdf59c64/image1.png)
+![Payment authorization callback notification flow](https://images.ctfassets.net/alneenqid6w5/2jMjUV7EZuzqN5L1OCQgIJ/90500ae3bc824ff831193cf7cdf59c64/image1.png)
 
 1. A autorização do pagamento é iniciada quando o Gateway chama o endpoint Create Payment (__/payment__) para o Provider. No body do request, é enviado no campo `callbackUrl` a URL para fazer a notificação.
 2. O pagamento ocorre de forma assíncrona (não gera o status definitivo no momento em que a transação é iniciada). Então o Gateway recebe a resposta com status __undefined__ e fica esperando a conclusão do processamento do pagamento e, por fim, atualizar com o status definitivo (__approved__ ou __denied__).
@@ -187,7 +187,7 @@ O fluxo completo com status undefined e uso de notificação pode ser visto abai
 
 O fluxo completo com status __undefined__ e uso do __retry__ pode ser visto abaixo:
 
-![Payment authorization callback retry flow](//images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/66f6fe3be218a9fe6e2584e75bb18640/image2.png)
+![Payment authorization callback retry flow](https://images.ctfassets.net/alneenqid6w5/5kGkX4QGLUPNfclwMdibax/66f6fe3be218a9fe6e2584e75bb18640/image2.png)
 
 1. A autorização do pagamento é iniciada quando o Gateway chama o endpoint Create Payment (__/payment__) para o Provider. No body do request, é enviado no campo `callbackUrl` a URL do endpoint __retry__.
 2. O pagamento ocorre de forma assíncrona (não gera o status definitivo no momento em que a transação é iniciada). Então o Gateway recebe a resposta com status __undefined__ e fica esperando a conclusão do processamento do pagamento e, por fim, atualizar com o status definitivo (__approved__ ou __denied__).
diff --git a/docs/tutorials/pt/payu-romania-refund-details.md b/docs/tutorials/pt/payu-romania-refund-details.md
index 1bbe3b8f5..70dcfeb16 100644
--- a/docs/tutorials/pt/payu-romania-refund-details.md
+++ b/docs/tutorials/pt/payu-romania-refund-details.md
@@ -38,7 +38,7 @@ Se o botão Excluir não estiver ativo e o tempo limite não tiver expirado, voc
 
 Se o pedido de reembolso ou de reembolso já tiver sido enviado pelo sistema ao banco emissor, não poderemos mais excluir / interromper o pedido de forma alguma.
 
-![PayU Romania](//images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
+![PayU Romania](https://images.ctfassets.net/alneenqid6w5/eR53ZeK0Le8UMeQQs2osq/03a5bad4e5f9269dc12159b28fd27dd8/PayU_Romania.png)
 
 Depois que a PayU enviar o pedido de reembolso ou de reembolso ao banco emissor, o status do pedido será atualizado no PayP cPanel como "REVERSE" (para vazios) ou "REEMBOLSO". E a VTEX receberá um webhook do PaymentsOS, portanto, o status do pedido também pode ser atualizado na plataforma (no Pagamentos e, consequentemente, refletido no OMS).
 
diff --git a/docs/tutorials/pt/pci-gateway-overview.md b/docs/tutorials/pt/pci-gateway-overview.md
index 32cb65bc4..f34d8c11c 100644
--- a/docs/tutorials/pt/pci-gateway-overview.md
+++ b/docs/tutorials/pt/pci-gateway-overview.md
@@ -19,7 +19,7 @@ subcategory: 2Xay1NOZKE2CSqKMwckOm8
 
 # Começando a usar
 
-![new-admin-pagamentos ](//images.ctfassets.net/alneenqid6w5/1QtaQtxOB2gYys8yqiaEkE/a10f07d80939b53ae95255b41e5ee6f7/NEW_ADMIN_PAGAMENTOS_PT.png)
+![new-admin-pagamentos ](https://images.ctfassets.net/alneenqid6w5/1QtaQtxOB2gYys8yqiaEkE/a10f07d80939b53ae95255b41e5ee6f7/NEW_ADMIN_PAGAMENTOS_PT.png)
 
 Criado para oferecer a flexibilidade máxima em relação às configurações de pagamento, o módulo de **Pagamentos** processa as transações com base em alguns conceitos de negócio. Entenda cada um deles:
 
diff --git a/docs/tutorials/pt/permissions-management-in-b2b-suite.md b/docs/tutorials/pt/permissions-management-in-b2b-suite.md
index 3ba902279..93f43bcbe 100644
--- a/docs/tutorials/pt/permissions-management-in-b2b-suite.md
+++ b/docs/tutorials/pt/permissions-management-in-b2b-suite.md
@@ -61,7 +61,7 @@ Para gerenciar perfis de acesso e permissões de aplicativos, configure as permi
 
 5. Clique em `Salvar`.
 
-![Gerenciamento de permissões - PT](//images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/8c88c345288f6092061820e2193e104f/Gerenciamento_de_permiss_es_-_PT.gif)
+![Gerenciamento de permissões - PT](https://images.ctfassets.net/alneenqid6w5/287qksSZ46sMPwg4CuXQ8F/8c88c345288f6092061820e2193e104f/Gerenciamento_de_permiss_es_-_PT.gif)
 
 Depois de associar os perfis com as permissões desejadas, você pode atribuir funções aos usuários. Para saber mais, acesse [Organizações B2B](https://developers.vtex.com/docs/guides/vtex-b2b-organizations#users).
 
diff --git a/docs/tutorials/pt/physical-store-instore-beta.md b/docs/tutorials/pt/physical-store-instore-beta.md
index 9d0b08af7..4affcb3bd 100644
--- a/docs/tutorials/pt/physical-store-instore-beta.md
+++ b/docs/tutorials/pt/physical-store-instore-beta.md
@@ -28,7 +28,7 @@ Esta página permite que você realize as seguintes ações:
 * [Editar](#editar-loja-fisica)
 * [Excluir](#excluir-loja-fisica)
 
-![loja-fisica-PT](//images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
+![loja-fisica-PT](https://images.ctfassets.net/alneenqid6w5/6C1IhZgOyHi06ZogDIfTcF/0c7eafb7209254cfca3224ccb820012e/image.png)
 
 A página apresenta as seguintes informações: 
 
@@ -54,7 +54,7 @@ Você pode cadastrar uma loja física seguindo os passos a seguir:
 
 ### Campos de cadastro da loja física
 
-![loja-fisica2-pt](//images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
+![loja-fisica2-pt](https://images.ctfassets.net/alneenqid6w5/60OAU1QatgSvdghvRebAOW/92f54533a7b36d602d4108760ba3c7e0/image.png)
 
 #### Identificação
 
diff --git a/docs/tutorials/pt/pickup-points-for-subscription-orders.md b/docs/tutorials/pt/pickup-points-for-subscription-orders.md
index 6419fc095..f8561f52e 100644
--- a/docs/tutorials/pt/pickup-points-for-subscription-orders.md
+++ b/docs/tutorials/pt/pickup-points-for-subscription-orders.md
@@ -41,7 +41,7 @@ Para disponibilizar pontos de retirada para pedidos de assinatura, é necessári
 
 O cliente final pode escolher pontos de retirada para itens de um pedido de assinatura no momento do checkout, conforme ilustrado na imagem abaixo.
 
-![subscriptionspickup PT](//images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
+![subscriptionspickup PT](https://images.ctfassets.net/alneenqid6w5/6qqc7DV4Wk6yRWvsdiWNCP/d7b20c88e0bcc04178d9bd0a5234d702/subscriptionspickup_PT.gif)
 
 Você também pode atribuir pontos de retirada ao [criar novas assinaturas](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#post_api-rns-pub-subscriptions) por meio da [API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1). No caso de assinaturas já existentes, você pode alterar o endereço de entrega com a [rota de atualização de assinatura da API de Subscriptions](https://developers.vtex.com/vtex-rest-api/reference/subscriptions-1#patch_api-rns-pub-subscriptions-id) para começar a utilizar um ponto de retirada.
 
diff --git a/docs/tutorials/pt/pickup-points.md b/docs/tutorials/pt/pickup-points.md
index d2512dc98..ccba58514 100644
--- a/docs/tutorials/pt/pickup-points.md
+++ b/docs/tutorials/pt/pickup-points.md
@@ -71,7 +71,7 @@ A VTEX considera que o ponto de retirada é uma forma de envio e, por isso, as c
     - b. Na aba **Política de envio**, selecione a política de envio criada para o ponto de retirada.
     - c. Na coluna **Ações**, clique no ícone <i class="fas fa-pen"></i> para edição.
     - d. Ative o <i class="fas fa-toggle-on"></i> do campo **Relacionar pontos de retirada**.
-    - e. Selecione o ponto de retirada pelos campos disponíveis.![relacionarpontosretiradaPT](//images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/666ecbf11f8f19e5b8b1ca8b381abbf8/relacionarpontosretiradaPT.png)<div class = "alert alert-info">Para lojas que possuem mais de 50 pontos de retirada, recomendamos utilizar o campo Tags dos pontos de retirada ao criar um ponto de retirada. Utilizar tags facilita a busca dos pontos de <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio">retirada na hora de relacioná-los com a política de envio</a>.Lembre-se também que a política de envio que está associada a um ponto de retirada não fica disponível para outro tipo de envio. Recomendamos criar uma política de envio exclusiva do ponto de retirada.</div>
+    - e. Selecione o ponto de retirada pelos campos disponíveis.![relacionarpontosretiradaPT](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/666ecbf11f8f19e5b8b1ca8b381abbf8/relacionarpontosretiradaPT.png)<div class = "alert alert-info">Para lojas que possuem mais de 50 pontos de retirada, recomendamos utilizar o campo Tags dos pontos de retirada ao criar um ponto de retirada. Utilizar tags facilita a busca dos pontos de <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio">retirada na hora de relacioná-los com a política de envio</a>.Lembre-se também que a política de envio que está associada a um ponto de retirada não fica disponível para outro tipo de envio. Recomendamos criar uma política de envio exclusiva do ponto de retirada.</div>
 
 4. [Cadastrar a geolocalização](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): para maior precisão da localização dos pontos de retirada no checkout.<div class = "alert alert-info">A visualização dos pontos de retirada com mapa e horário no checkout está disponível apenas para o Checkout V6.</div>
 
@@ -79,7 +79,7 @@ A VTEX considera que o ponto de retirada é uma forma de envio e, por isso, as c
     - a. No Admin VTEX, acesse **Configurações da loja > Storefront > Checkout**, ou digite *Checkout* na barra de busca no topo da página. 
     - b. Seleciona a configuração utilizada na loja e clique no ícone <i class="fas fa-cog"></i>.
     - c. Clique na aba **Checkout** na barra superior.
-    - d. Selecione o <i class="fas fa-toggle-on"></i> do campo **Endereço na nota fiscal para retirada em loja**.![NFpontoretiradaPT](//images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/491e27746972c957683057e5c944bb84/NFpontoretiradaPT.png)<div class="alert alert-warning">A opção de <b>Endereço na nota fiscal para retirada em loja</b> deve estar habilitada em todas as lojas do Brasil, pois é num requisito que a Nota Fiscal emitida contenha a informação do endereço do cliente, mesmo que a opção de entrega do pedido seja no ponto de retirada. O endereço preenchido pelo cliente será registrado no campo `invoiceData`do <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - d. Selecione o <i class="fas fa-toggle-on"></i> do campo **Endereço na nota fiscal para retirada em loja**.![NFpontoretiradaPT](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/491e27746972c957683057e5c944bb84/NFpontoretiradaPT.png)<div class="alert alert-warning">A opção de <b>Endereço na nota fiscal para retirada em loja</b> deve estar habilitada em todas as lojas do Brasil, pois é num requisito que a Nota Fiscal emitida contenha a informação do endereço do cliente, mesmo que a opção de entrega do pedido seja no ponto de retirada. O endereço preenchido pelo cliente será registrado no campo `invoiceData`do <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
 
 6. Configurar a quantidade de pontos de retirada que são exibidos no checkout:
     - a. No Admin VTEX, acesse **Configurações da loja > Envio > Configurações**, ou digite *Envio* na barra de busca no topo da página e selecione *Configurações da loja / Envio*. 
diff --git a/docs/tutorials/pt/pipedrive-suiteshare.md b/docs/tutorials/pt/pipedrive-suiteshare.md
index e3d12036f..7a8cdcbd4 100644
--- a/docs/tutorials/pt/pipedrive-suiteshare.md
+++ b/docs/tutorials/pt/pipedrive-suiteshare.md
@@ -21,37 +21,37 @@ Para realizar a integração acesse no seu painel do **VTEX Assisted Sales (Sui
 
 Na dashboard em _**“Integrações”**_.
 
-![Pipedrive 1](//images.ctfassets.net/alneenqid6w5/2VCqCuAJgX4c5kqnBx3YnN/e9142c549e1f18a21005b50f10cf71b5/Screenshot_2022-08-30_at_11-33-50_Pipedrive.png)
+![Pipedrive 1](https://images.ctfassets.net/alneenqid6w5/2VCqCuAJgX4c5kqnBx3YnN/e9142c549e1f18a21005b50f10cf71b5/Screenshot_2022-08-30_at_11-33-50_Pipedrive.png)
 
  Ou clique em "_**configurações > Integrações"**_.
 
-![Pipedrive 2](//images.ctfassets.net/alneenqid6w5/Nhn2eGDJpBtVFFthvQZ7U/d51faa28f026a4255e20f25265770e43/Screenshot_2022-08-30_at_11-36-20_Pipedrive.png)
+![Pipedrive 2](https://images.ctfassets.net/alneenqid6w5/Nhn2eGDJpBtVFFthvQZ7U/d51faa28f026a4255e20f25265770e43/Screenshot_2022-08-30_at_11-36-20_Pipedrive.png)
 
 Selecione o Pipedrive e clique em _**“integrar”**_.
 
 Clique em _**“Conectar”**_.
 
-![Pipedrive 3](//images.ctfassets.net/alneenqid6w5/1g0sbuLweixaeJlazFhYFU/1168f8512f4aeb0cbde1b193caffe409/Screenshot_2022-08-30_at_11-36-25_Pipedrive.png)
+![Pipedrive 3](https://images.ctfassets.net/alneenqid6w5/1g0sbuLweixaeJlazFhYFU/1168f8512f4aeb0cbde1b193caffe409/Screenshot_2022-08-30_at_11-36-25_Pipedrive.png)
 
 Faça o login na sua conta no Pipedrive
 
-![Pipedrive 4](//images.ctfassets.net/alneenqid6w5/3TD2H7RDO8b0dqMvkqSJ4N/d4a63437da3d6cce788843c33ac9c173/Screenshot_2022-08-30_at_11-36-30_Pipedrive.png)
+![Pipedrive 4](https://images.ctfassets.net/alneenqid6w5/3TD2H7RDO8b0dqMvkqSJ4N/d4a63437da3d6cce788843c33ac9c173/Screenshot_2022-08-30_at_11-36-30_Pipedrive.png)
 
 Autorize a conexão.
 
-![Pipedrive 5](//images.ctfassets.net/alneenqid6w5/2kQRACyZzHp6Dw0VrHGXrc/5ae1be25734616fc3d4488621b13c272/Screenshot_2022-08-30_at_11-36-35_Pipedrive.png)
+![Pipedrive 5](https://images.ctfassets.net/alneenqid6w5/2kQRACyZzHp6Dw0VrHGXrc/5ae1be25734616fc3d4488621b13c272/Screenshot_2022-08-30_at_11-36-35_Pipedrive.png)
 
 Selecione qual será o **Formulário de captura**  a ser conectado e qual será o usuário responsável. 
 
-![Pipedrive 6](//images.ctfassets.net/alneenqid6w5/3CCTVLOTW1c1dMXTmwFNQG/9fbfe42bf7a3caf548b9ccfb7770f330/Screenshot_2022-08-30_at_11-36-39_Pipedrive.png)
+![Pipedrive 6](https://images.ctfassets.net/alneenqid6w5/3CCTVLOTW1c1dMXTmwFNQG/9fbfe42bf7a3caf548b9ccfb7770f330/Screenshot_2022-08-30_at_11-36-39_Pipedrive.png)
 
 Defina qual será o pipeline que será enviado o Lead.
 
-![Pipedrive 7](//images.ctfassets.net/alneenqid6w5/6E6RhqVHWwvGFmgCpMjga8/2e5add02161795cc1bc8abe9a676030e/Screenshot_2022-08-30_at_11-36-43_Pipedrive.png)
+![Pipedrive 7](https://images.ctfassets.net/alneenqid6w5/6E6RhqVHWwvGFmgCpMjga8/2e5add02161795cc1bc8abe9a676030e/Screenshot_2022-08-30_at_11-36-43_Pipedrive.png)
 
 Defina o estágio.
 
-![Pipedrive 8](//images.ctfassets.net/alneenqid6w5/6ReBh9zp1bL3Eqe5ibku1E/81b25ef6129bb6f68d38a949ebf7e991/Screenshot_2022-08-30_at_11-36-50_Pipedrive.png)
+![Pipedrive 8](https://images.ctfassets.net/alneenqid6w5/6ReBh9zp1bL3Eqe5ibku1E/81b25ef6129bb6f68d38a949ebf7e991/Screenshot_2022-08-30_at_11-36-50_Pipedrive.png)
 
 Clique no botão _**“Salvar”**_. 
 
diff --git a/docs/tutorials/pt/piperun-suiteshare.md b/docs/tutorials/pt/piperun-suiteshare.md
index 300dc29b0..725cdefc8 100644
--- a/docs/tutorials/pt/piperun-suiteshare.md
+++ b/docs/tutorials/pt/piperun-suiteshare.md
@@ -21,11 +21,11 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Piperun**.
 
-   ![Piperun - Suiteshare_1](//images.ctfassets.net/alneenqid6w5/6FkPhokvfKkWwpjUMNF2MF/a2a8aa6ef4cfaa3cf39337769f94232c/Piperun_-_Suiteshare_1.png)
+   ![Piperun - Suiteshare_1](https://images.ctfassets.net/alneenqid6w5/6FkPhokvfKkWwpjUMNF2MF/a2a8aa6ef4cfaa3cf39337769f94232c/Piperun_-_Suiteshare_1.png)
 
 2. Acesse **Configurações > Integrações > Piperun > Integrar**.
 
-   ![CRM Zen_2](//images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
+   ![CRM Zen_2](https://images.ctfassets.net/alneenqid6w5/5Q1v1x7pR9DaaavNtDLIkh/017737adacef1737787ce533f3898f20/CRM_Zen_2.png)
 
 Com a Piperun podemos ter duas integrações diferentes: **Integração estática** e **Integração dinâmica**. 
 
@@ -35,23 +35,23 @@ Com a Piperun podemos ter duas integrações diferentes: **Integração estáti
   <p>Na integração dinâmica, você envia os leads para um pipeline e estágio específico do seu funil e atribui a um usuário da sua conta PipeRun.</p>
 </div>
 
-![Piperun - Suiteshare_2](//images.ctfassets.net/alneenqid6w5/5K6w6Kf2Y47ISe5j8umeIv/9a6b1f91d8d69ec27f1f85d799754af0/Piperun_-_Suiteshare_2.png)
+![Piperun - Suiteshare_2](https://images.ctfassets.net/alneenqid6w5/5K6w6Kf2Y47ISe5j8umeIv/9a6b1f91d8d69ec27f1f85d799754af0/Piperun_-_Suiteshare_2.png)
 
 Selecione o [link de captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que deseje integrar. 
 
-![Piperun - Suiteshare_3](//images.ctfassets.net/alneenqid6w5/GnzcGDKFpgtNECgfKS2nV/268f05e4d5f3a92b32e10402c004d084/Piperun_-_Suiteshare_3.png)
+![Piperun - Suiteshare_3](https://images.ctfassets.net/alneenqid6w5/GnzcGDKFpgtNECgfKS2nV/268f05e4d5f3a92b32e10402c004d084/Piperun_-_Suiteshare_3.png)
 
 Agora, selecione qual o usuário que receberá o Lead.
 
-![Piperun - Suiteshare_4](//images.ctfassets.net/alneenqid6w5/630ZqvavvlcCWKTAd9hcg6/3acb35f033142492ffb8fbb674631fb1/Piperun_-_Suiteshare_4.png)
+![Piperun - Suiteshare_4](https://images.ctfassets.net/alneenqid6w5/630ZqvavvlcCWKTAd9hcg6/3acb35f033142492ffb8fbb674631fb1/Piperun_-_Suiteshare_4.png)
 
 Agora, defina para qual pipeline ele será direcionado.
 
-![Piperun - Suiteshare_5](//images.ctfassets.net/alneenqid6w5/6DK6dpBefSKHOrJqkSiRRh/07cf8e08698b0d60a0aaf98fa0351ce5/Piperun_-_Suiteshare_5.png)
+![Piperun - Suiteshare_5](https://images.ctfassets.net/alneenqid6w5/6DK6dpBefSKHOrJqkSiRRh/07cf8e08698b0d60a0aaf98fa0351ce5/Piperun_-_Suiteshare_5.png)
 
 Você ainda pode definir opcionais para esse lead, por exemplo: de onde ele veio, ou tags para sua identificação. 
 
-![Piperun - Suiteshare_6](//images.ctfassets.net/alneenqid6w5/DiZTq34gfIsbs37JuhPka/3d689978d9fd79ebf28f5946eca086c8/Piperun_-_Suiteshare_6.png)
+![Piperun - Suiteshare_6](https://images.ctfassets.net/alneenqid6w5/DiZTq34gfIsbs37JuhPka/3d689978d9fd79ebf28f5946eca086c8/Piperun_-_Suiteshare_6.png)
 
 Clique no botão **Salvar**.
 
@@ -61,31 +61,31 @@ Clique no botão **Salvar**.
   <p>Na integração estática, você envia os leads para um estágio específico do seu funil sem atribuir a nenhum usuário automaticamente.</p>
 </div>
 
-![Piperun - Suiteshare_7](//images.ctfassets.net/alneenqid6w5/3adHKF0lGdefcI8eYzs3me/06cf495e6609100c1f06b944d80febff/Piperun_-_Suiteshare_7.png)
+![Piperun - Suiteshare_7](https://images.ctfassets.net/alneenqid6w5/3adHKF0lGdefcI8eYzs3me/06cf495e6609100c1f06b944d80febff/Piperun_-_Suiteshare_7.png)
 
 Selecione o [Formulário de captura](http://help.suiteshare.com/support/solutions/articles/67000192044-formul%C3%A1rio-de-captura) que deseje integrar. 
 
-![Piperun - Suiteshare_8](//images.ctfassets.net/alneenqid6w5/3EJtWkPa5Ks9r3uKgR5Jr/7592ef0a3e2a24f6bab3236f25c022c5/Piperun_-_Suiteshare_8.png)
+![Piperun - Suiteshare_8](https://images.ctfassets.net/alneenqid6w5/3EJtWkPa5Ks9r3uKgR5Jr/7592ef0a3e2a24f6bab3236f25c022c5/Piperun_-_Suiteshare_8.png)
 
 Agora você precisa da HasH ID fornecida pela Piperun.
 
-![Piperun - Suiteshare_9](//images.ctfassets.net/alneenqid6w5/1OyXRL50jrbBNqfwYbHqDe/8bbeaddb6a8498639c99e68921e6503f/Piperun_-_Suiteshare_9.png)
+![Piperun - Suiteshare_9](https://images.ctfassets.net/alneenqid6w5/1OyXRL50jrbBNqfwYbHqDe/8bbeaddb6a8498639c99e68921e6503f/Piperun_-_Suiteshare_9.png)
 
 Acesse o painel da [Piperun](https://app.pipe.run/pipeline), clique no seu usuário e acesse [Ajustes](https://app.pipe.run/configuracao). 
 
-![Piperun - Suiteshare_10](//images.ctfassets.net/alneenqid6w5/gXXMJ1MOmZpyQx2ZcFaEL/b4bc987bdfcfdf1ac448b2ec9e1bd4e1/Piperun_-_Suiteshare_10.png)
+![Piperun - Suiteshare_10](https://images.ctfassets.net/alneenqid6w5/gXXMJ1MOmZpyQx2ZcFaEL/b4bc987bdfcfdf1ac448b2ec9e1bd4e1/Piperun_-_Suiteshare_10.png)
 
 Em **Oportunidades**, selecione a opção **Funis e etapas de funis**.
 
-![Piperun - Suiteshare_11](//images.ctfassets.net/alneenqid6w5/7FdRYz6JrDMDJ9UorXeAdd/68b01e5931f8e1427289a6d184bc98d7/Piperun_-_Suiteshare_11.png)
+![Piperun - Suiteshare_11](https://images.ctfassets.net/alneenqid6w5/7FdRYz6JrDMDJ9UorXeAdd/68b01e5931f8e1427289a6d184bc98d7/Piperun_-_Suiteshare_11.png)
 
 Selecione o funil e a etapa que deseja enviar esse cliente.
 
-![Piperun - Suiteshare_12](//images.ctfassets.net/alneenqid6w5/7bPYfrubfoVFcLTWySDGpr/c0c49d2f10a9506e5d31844db8db89f6/Piperun_-_Suiteshare_12.png)
+![Piperun - Suiteshare_12](https://images.ctfassets.net/alneenqid6w5/7bPYfrubfoVFcLTWySDGpr/c0c49d2f10a9506e5d31844db8db89f6/Piperun_-_Suiteshare_12.png)
 
 Copie a Hash fornecida pela Piperun. 
 
-![Piperun - Suiteshare_13](//images.ctfassets.net/alneenqid6w5/4ZKN2T0Y2GHgzM3fw4ltEN/a251d7d53b4c8a4a8f57a06ec2835008/Piperun_-_Suiteshare_13.png)
+![Piperun - Suiteshare_13](https://images.ctfassets.net/alneenqid6w5/4ZKN2T0Y2GHgzM3fw4ltEN/a251d7d53b4c8a4a8f57a06ec2835008/Piperun_-_Suiteshare_13.png)
 
 <div class="alert alert-danger">
   <p>Para copiar a Hash, é necessário clicar com o botão direito do mouse e selecione a opção copiar.</p>
@@ -93,7 +93,7 @@ Copie a Hash fornecida pela Piperun. 
 
 Você ainda pode definir opcionais para esse lead, por exemplo: de onde ele veio, ou tags para sua identificação. 
 
-![Piperun - Suiteshare_14](//images.ctfassets.net/alneenqid6w5/7DvPeJlG1GyPD2oKQrJMxB/f44496bb6c7f7046c809ec994eb30413/Piperun_-_Suiteshare_14.png)
+![Piperun - Suiteshare_14](https://images.ctfassets.net/alneenqid6w5/7DvPeJlG1GyPD2oKQrJMxB/f44496bb6c7f7046c809ec994eb30413/Piperun_-_Suiteshare_14.png)
 
 Clique no botão **Salvar**.
 
diff --git a/docs/tutorials/pt/pix-faq.md b/docs/tutorials/pt/pix-faq.md
index 5619d4d95..86c27d648 100644
--- a/docs/tutorials/pt/pix-faq.md
+++ b/docs/tutorials/pt/pix-faq.md
@@ -64,9 +64,9 @@ A opção de pagar via Pix aparecerá na lista, junto com as outras opções de
 
 Quando o usuário clicar no Pix, um QR Code que comporta as informações da compra será gerado. A partir daí, o usuário tem dez minutos para efetuar a transação com a sua instituição financeira de preferência.
 
-![Checkout_Pix](//images.ctfassets.net/alneenqid6w5/8wd0gOpf8bsODhLIgZWSS/c57d465dca70e9362f3a3f9a485ae9ac/Checkout_Pix.png)
+![Checkout_Pix](https://images.ctfassets.net/alneenqid6w5/8wd0gOpf8bsODhLIgZWSS/c57d465dca70e9362f3a3f9a485ae9ac/Checkout_Pix.png)
 
-![QRCode_Pix](//images.ctfassets.net/alneenqid6w5/5aHNT7dd5nIXellY6L7Y74/97796620983d212cc6f063860df6734f/QRCode_Pix.png)
+![QRCode_Pix](https://images.ctfassets.net/alneenqid6w5/5aHNT7dd5nIXellY6L7Y74/97796620983d212cc6f063860df6734f/QRCode_Pix.png)
 
 ### É possível dividir um pagamento entre Pix e outra forma de pagamento?
 
diff --git a/docs/tutorials/pt/planner-calendar-page-beta.md b/docs/tutorials/pt/planner-calendar-page-beta.md
index 2c51c91b8..9dccb8df1 100644
--- a/docs/tutorials/pt/planner-calendar-page-beta.md
+++ b/docs/tutorials/pt/planner-calendar-page-beta.md
@@ -39,7 +39,7 @@ O **Calendário** apresenta somente [lançamentos agendados](https://help.vtex.c
 
 A imagem a seguir apresenta a visualização por mês e identifica o que você pode realizar pela interface:
 
-![releases-calendar-monthly-view-pt](//images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6f066a16c87c6bccc2ac229dd83cca4b/releases-calendar-monthly-view-pt.png)
+![releases-calendar-monthly-view-pt](https://images.ctfassets.net/alneenqid6w5/BQCF0b8kNzGTOv06wCOde/6f066a16c87c6bccc2ac229dd83cca4b/releases-calendar-monthly-view-pt.png)
 
 Nesta tela, é possível:
 
@@ -57,7 +57,7 @@ Nesta tela, é possível:
 
 A imagem a seguir apresenta a visualização por semana e identifica o que você pode realizar na interface:
 
-![releases-calendar-weekly-view-pt](//images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/936efd12d08cbcc539bccfad7dc9da55/releases-calendar-weekly-view-pt.png)
+![releases-calendar-weekly-view-pt](https://images.ctfassets.net/alneenqid6w5/QHZDKB0IX07GLoEO84NJv/936efd12d08cbcc539bccfad7dc9da55/releases-calendar-weekly-view-pt.png)
 
 Nesta tela, é possível:
 
@@ -75,7 +75,7 @@ Nesta tela, é possível:
 
 A imagem a seguir apresenta a visualização por dia e identifica o que você pode realizar na interface:
 
-![daily view v2 pt](//images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/6b5ee0b8d3f0ede45eb8bc70b0c3f885/daily_view_v2_pt.png)
+![daily view v2 pt](https://images.ctfassets.net/alneenqid6w5/5dwgo1qqTYNFMKV4sBNW0Q/6b5ee0b8d3f0ede45eb8bc70b0c3f885/daily_view_v2_pt.png)
 
 Além de visualizar informações sobre o lançamento, nesta tela, é possível:
 
diff --git a/docs/tutorials/pt/planner-releases-page-beta.md b/docs/tutorials/pt/planner-releases-page-beta.md
index 936d8613b..6416ee370 100644
--- a/docs/tutorials/pt/planner-releases-page-beta.md
+++ b/docs/tutorials/pt/planner-releases-page-beta.md
@@ -35,7 +35,7 @@ A ordenação dos lançamentos agendados é feita com base na data de publicaç
 
 Para acessar a página **Lançamentos** no Admin VTEX, vá no menu de navegação **Lançamentos**. A imagem a seguir apresenta a interface e identifica o que você pode realizar por meio dela:
 
-![Releases list view v2 - PT](//images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/4dfbad1e1ee3bbf47ffd965472430291/Releases_list_view_v2_-_PT.png)
+![Releases list view v2 - PT](https://images.ctfassets.net/alneenqid6w5/Fe7SCh8LI8Nv4x6ZM6EGc/4dfbad1e1ee3bbf47ffd965472430291/Releases_list_view_v2_-_PT.png)
 
 | **Campo** | **Descrição** |
 |---|---|
diff --git a/docs/tutorials/pt/price-divergence-rule.md b/docs/tutorials/pt/price-divergence-rule.md
index d607c80b2..639ee6bb9 100644
--- a/docs/tutorials/pt/price-divergence-rule.md
+++ b/docs/tutorials/pt/price-divergence-rule.md
@@ -29,7 +29,7 @@ A regra de Divergência de valores é composta de uma ou mais regras de autoriza
 - **Negar automaticamente:** pedidos com diferença de preço até a porcentagem definida são automaticamente recusados e não são integrados.
 - **Criar uma tarefa no VTEX DO para aprovação:** para diferenças de preço dentro do intervalo configurado, o pedido é integrado, mas fica pendente de [autorização manual](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe#autorizar-pedidos-manualmente) por parte de um usuário habilitado.
 
-![price_divergence_rules_PT](//images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/f3858b3abbc1be86fd281ba357198e3f/price_divergence_rules_PT.png)
+![price_divergence_rules_PT](https://images.ctfassets.net/alneenqid6w5/3eUHS2dcIUY5KiDshLpurc/f3858b3abbc1be86fd281ba357198e3f/price_divergence_rules_PT.png)
 
 Quando a [configuração de uma regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) não foi feita, pedidos com erro de divergência de preço são aprovados automaticamente. Isso vale para marketplaces VTEX, marketplaces externos e conectores certificados (parceiros), mas não para [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex).
 
diff --git a/docs/tutorials/pt/price-divergence-rules-beta.md b/docs/tutorials/pt/price-divergence-rules-beta.md
index 1f70a6ca7..ab4b19ed0 100644
--- a/docs/tutorials/pt/price-divergence-rules-beta.md
+++ b/docs/tutorials/pt/price-divergence-rules-beta.md
@@ -25,7 +25,7 @@ Os pedidos que apresentam erros por divergência de preço maior que os valores
 
 Os pedidos apresentam um status de erro no módulo de *INTEGRAÇÕES* e ficam aguardando serem reprocessados manualmente.
 
-![Início (6)](//images.contentful.com/alneenqid6w5/3ew5jbEQLOWq35gB0H0rLx/1fa45e6308ecc1906fcff908df9ba0c2/In__cio__6_.gif)
+![Início (6)](https://images.contentful.com/alneenqid6w5/3ew5jbEQLOWq35gB0H0rLx/1fa45e6308ecc1906fcff908df9ba0c2/In__cio__6_.gif)
 
 Para que os pedidos com divergência de preço subam para o OMS, foi criada a regra de divergência de valores (Beta). Nessa regra, todos os pedidos com divergência de preço são enviados ao OMS e devem ser aprovados manualmente pelo responsável da loja, com e-mail cadastrado em *Gerenciamento de contas > Contas*. É possível ter mais de um e-mail cadastrado.
 
@@ -47,7 +47,7 @@ Na configuração da regra de divergência de valores, temos duas possibilidades
 
 ### Criar regras
 
-![barra regradivergencia](//images.contentful.com/alneenqid6w5/6JNnSQFFrel5aIEWZPPQGs/98dd2567f3a1c178dc0ea1c150895ee0/barra_regradivergencia.JPG)
+![barra regradivergencia](https://images.contentful.com/alneenqid6w5/6JNnSQFFrel5aIEWZPPQGs/98dd2567f3a1c178dc0ea1c150895ee0/barra_regradivergencia.JPG)
 
 Para criar as regras, siga os passos abaixo:
 
@@ -80,7 +80,7 @@ Para editar as regras já existentes, siga os passos abaixo:
 5. Edite a regra que deseja alterando a barra de porcentagem.
 6. Clique em `Salvar Regras`.
 
-![Início (7)](//images.contentful.com/alneenqid6w5/78PxO7B0deTXnm48YPRlew/0b46e4637bfe89bfb373a679b4afadac/In__cio__7_.gif)
+![Início (7)](https://images.contentful.com/alneenqid6w5/78PxO7B0deTXnm48YPRlew/0b46e4637bfe89bfb373a679b4afadac/In__cio__7_.gif)
 
 ## Autorização de pedidos
 
@@ -103,7 +103,7 @@ Para autorizar manualmente os pedidos, siga os passos a seguir:
 4. Selecione o pedido com status `Aguardando autorização manual` que deseja autorizar. 
 5. Clique em `Confirmar pedido`.
 
-![Início (8)](//images.contentful.com/alneenqid6w5/4cDra6L7aNwPbmTxZJVNPJ/8f232c924f02fa9377bccb8f1e42d698/In__cio__8_.gif)
+![Início (8)](https://images.contentful.com/alneenqid6w5/4cDra6L7aNwPbmTxZJVNPJ/8f232c924f02fa9377bccb8f1e42d698/In__cio__8_.gif)
 
 ### Autorização pelo VTEX DO
 
@@ -117,4 +117,4 @@ O [VTEX DO](https://help.vtex.com/pt/tutorial/vtex-do--tutorials_203?&utm_source
 6. Clique em `Fechar`.
 7. Clique em `Autorizar`.
 
-![Início (9)](//images.contentful.com/alneenqid6w5/6WCfZf454PzSeJ2ZZASERn/f1fd489741a19979544bcc80f8686598/In__cio__9_.gif)
+![Início (9)](https://images.contentful.com/alneenqid6w5/6WCfZf454PzSeJ2ZZASERn/f1fd489741a19979544bcc80f8686598/In__cio__9_.gif)
diff --git a/docs/tutorials/pt/price-waterfall.md b/docs/tutorials/pt/price-waterfall.md
index 9e65102f7..65432c9c0 100644
--- a/docs/tutorials/pt/price-waterfall.md
+++ b/docs/tutorials/pt/price-waterfall.md
@@ -21,7 +21,7 @@ Com essa nova feature, temos agora uma nova entidade de preço chamada *Preços
 
 O gráfico abaixo explica como funciona a cascata de preços:
 
-![Cascata de Preço](//images.ctfassets.net/alneenqid6w5/4Dh0ulBDFCEs8WuuigSsoY/3cfeccdf7b8d690a026533fbcbc699b0/cascataPreco.png)
+![Cascata de Preço](https://images.ctfassets.net/alneenqid6w5/4Dh0ulBDFCEs8WuuigSsoY/3cfeccdf7b8d690a026533fbcbc699b0/cascataPreco.png)
 
 Quando um preço para um SKU é solicitado ao módulo de *Pricing*:
 1. Um *Preço Fixo* é selecionado em seus critérios como **agendamento** e **quantidade mínima**
diff --git a/docs/tutorials/pt/pricing-rules-v2.md b/docs/tutorials/pt/pricing-rules-v2.md
index d8b6499a9..f7e995b50 100644
--- a/docs/tutorials/pt/pricing-rules-v2.md
+++ b/docs/tutorials/pt/pricing-rules-v2.md
@@ -20,7 +20,7 @@ As funcionalidades descritas neste artigo ainda não estão disponíveis para to
 
 Uma regra de preço é um modificador do preço-base cadastrado na tela Lista de preços.
 
-![new-dashboard-pricing-pt](//images.contentful.com/alneenqid6w5/1iEFJLw3xuKGiQS0W02cgm/5bcf2a65612a2fed4754352a7093dee8/new-dashboard-pricing-pt.gif)
+![new-dashboard-pricing-pt](https://images.contentful.com/alneenqid6w5/1iEFJLw3xuKGiQS0W02cgm/5bcf2a65612a2fed4754352a7093dee8/new-dashboard-pricing-pt.gif)
 
 ## Como funciona
 
@@ -34,7 +34,7 @@ Além disso, é importante ressaltar que as regras de preço são aplicadas ao p
 
 Será aplicada **apenas a primeira** regra de preço que seja válida para as condições do SKU (categoria; marca; e faixa de markup). Mesmo que existam outras regras de preço válidas, apenas a primeira na ordenação será utilizada para o cálculo de preço do SKU.
 
-![new-dashboard-pricing-rule-reordering-pt](//images.contentful.com/alneenqid6w5/6DTrNN6UMgoWkCU68Q2CWC/7b6168a2cb9a5e93b9b5db8ba98eaa09/new-dashboard-pricing-rule-reordering-pt.gif)
+![new-dashboard-pricing-rule-reordering-pt](https://images.contentful.com/alneenqid6w5/6DTrNN6UMgoWkCU68Q2CWC/7b6168a2cb9a5e93b9b5db8ba98eaa09/new-dashboard-pricing-rule-reordering-pt.gif)
 
 _Recomendamos que a ordenação parta das regras mais específicas para as regras mais abrangentes._
 
@@ -42,7 +42,7 @@ _Recomendamos que a ordenação parta das regras mais específicas para as regra
 
 O passo-a-passo para cadastro é bem simples, e está ilustrado a seguir:
 
-![new-dashboard-pricing-add-rule-pt](//images.contentful.com/alneenqid6w5/30MxuI9hD2qwc0AWm2MWmA/883e44a5845ba77d05e413aac3baf3f2/new-dashboard-pricing-add-rule-pt.gif)
+![new-dashboard-pricing-add-rule-pt](https://images.contentful.com/alneenqid6w5/30MxuI9hD2qwc0AWm2MWmA/883e44a5845ba77d05e413aac3baf3f2/new-dashboard-pricing-add-rule-pt.gif)
 
 1. Na tela de **Regras de preços** será exibida uma lista com todas as políticas comerciais. Dentro de cada uma dessa políticas, estarão as regras. Clique no botão **Nova regra**, acima da lista, para criar uma regra.
 2. Escolha em qual política comercial essa regra será inserida.
@@ -53,8 +53,8 @@ O passo-a-passo para cadastro é bem simples, e está ilustrado a seguir:
 
 Abaixo é possível visualizar exemplos dos fluxos de edição e exclusão de regras de preço. 
 
-![new-dashboard-pricing-edit-rule-pt](//images.contentful.com/alneenqid6w5/6k5P1L2ypGWsGA2UAsMq6I/df54e4098d1e1534c5d9953a7a50dd67/new-dashboard-pricing-edit-rule-pt.gif)
+![new-dashboard-pricing-edit-rule-pt](https://images.contentful.com/alneenqid6w5/6k5P1L2ypGWsGA2UAsMq6I/df54e4098d1e1534c5d9953a7a50dd67/new-dashboard-pricing-edit-rule-pt.gif)
 *Fluxo de alteração de uma regra*
 
-![new-dashboard-pricing-remove-rule-pt](//images.contentful.com/alneenqid6w5/64ESXpmeLmGokKA004aoqE/9d08afb457f280450eed449d9509ce3a/new-dashboard-pricing-remove-rule-pt.gif)
+![new-dashboard-pricing-remove-rule-pt](https://images.contentful.com/alneenqid6w5/64ESXpmeLmGokKA004aoqE/9d08afb457f280450eed449d9509ce3a/new-dashboard-pricing-remove-rule-pt.gif)
 *Fluxo de exclusão de uma regra*
diff --git a/docs/tutorials/pt/product-list.md b/docs/tutorials/pt/product-list.md
index d28c201da..5ce47dec5 100644
--- a/docs/tutorials/pt/product-list.md
+++ b/docs/tutorials/pt/product-list.md
@@ -17,7 +17,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 
 A página **Produtos** permite visualizar e gerenciar a lista completa de produtos cadastrados na sua loja, simplificando a gestão do catálogo no Seller Portal. Você pode acessar a página através do menu **Catálogo** no Admin VTEX.
 
-![product-list-pt](//images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/7d149b1193674dad3407a94652dcd669/product-list-pt.png)
+![product-list-pt](https://images.ctfassets.net/alneenqid6w5/25zE8wHvqhOGvaXweX7acK/7d149b1193674dad3407a94652dcd669/product-list-pt.png)
 
 A partir da lista de produtos, você pode realizar uma variedade de ações:
 
diff --git a/docs/tutorials/pt/products-and-skus-beta.md b/docs/tutorials/pt/products-and-skus-beta.md
index 3f604c98d..e05be4416 100644
--- a/docs/tutorials/pt/products-and-skus-beta.md
+++ b/docs/tutorials/pt/products-and-skus-beta.md
@@ -21,7 +21,7 @@ subcategory: 6XPsLadoT3moZ7eTduCg3c
 
 A página **Produtos e SKUs** possibilita visualizar e gerenciar a lista completa de produtos cadastrados na sua loja, incluindo informações sobre SKUs, data da última atualização e status. Para acessá-la, entre no menu **Catálogo > Produtos e SKUs**.
 
-![products-skus-pt](//images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/42eb4310fbe66a016176c54adb447ad9/products-skus-pt.png)
+![products-skus-pt](https://images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/42eb4310fbe66a016176c54adb447ad9/products-skus-pt.png)
 
 <div class="alert alert-info">
   <p>Esta página está disponível somente para lojas que estão operando com o <a href="https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">Novo Admin VTEX</a>. Para acessar esta página e fazer parte de uma nova experiência, participe do <a href="https://content.vtex.com/participe-do-programa-beta-pt/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> do Novo Admin VTEX.</p>
@@ -63,7 +63,7 @@ Para localizar um produto específico, você pode digitar um dos seguintes dados
 
 Em seguida, clique no critério que você deseja utilizar para a busca, conforme ilustrado na imagem a seguir:
 
-![products-skus-search-pt](//images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/7a04a740e895558318b88b2b00dd6949/search-pt.gif)
+![products-skus-search-pt](https://images.ctfassets.net/alneenqid6w5/3XkJPsJihm6flcVxPksPPO/7a04a740e895558318b88b2b00dd6949/search-pt.gif)
 
 A lista de produtos exibida será atualizada de acordo com sua busca. 
 
@@ -103,7 +103,7 @@ Para visualizar o status dos SKUs de um produto, leia a seção [Visualizar list
 
 Ao clicar na seta <i class="fas fa-chevron-right"></i> na linha de um produto da lista, a plataforma exibe uma lista com todos os SKUs cadastrados para aquele produto.
 
-![sku-actions-pt](//images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/dfbd3240bd021d0c91ca42f80a36ddd4/sku-actions-pt.gif)
+![sku-actions-pt](https://images.ctfassets.net/alneenqid6w5/wv1FevJRrT0GwvKvvNb2W/dfbd3240bd021d0c91ca42f80a36ddd4/sku-actions-pt.gif)
 
 Na lista de SKUs, é possível identificar as informações a seguir:
 
@@ -148,7 +148,7 @@ Ao clicar no menu <i class="fas fa-ellipsis-v"></i> na linha de um produto e opt
 
 Esta aba do modal exibe a lista de SKUs associados ao produto e suas respectivas informações indexadas.
 
-![catalog-price-inventory-pt](//images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/6ae475a3c76de0310e1fc08b8d087312/preco-inventario-pt.PNG)
+![catalog-price-inventory-pt](https://images.ctfassets.net/alneenqid6w5/4JWODR51ILI7KhEnzVC2t2/6ae475a3c76de0310e1fc08b8d087312/preco-inventario-pt.PNG)
 
 Ao clicar na seta `>` na linha de cada SKU, você pode visualizar uma tabela com as as seguintes informações:
 
@@ -163,7 +163,7 @@ Ao clicar na seta `>` na linha de cada SKU, você pode visualizar uma tabela com
 
 Esta aba do modal apresenta o log, ou seja, o registro técnico detalhado da indexação referente ao produto e aos SKUs relacionados.
 
-![indexed-log-pt](//images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/1d3d2899be6f6fb3b6b3aa8b993d71a4/log-indexacao-pt.PNG)
+![indexed-log-pt](https://images.ctfassets.net/alneenqid6w5/4pPJmvun6SB9jTFqSR7XSX/1d3d2899be6f6fb3b6b3aa8b993d71a4/log-indexacao-pt.PNG)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/promotion-alerts-beta.md b/docs/tutorials/pt/promotion-alerts-beta.md
index daf2cd423..0e8d70641 100644
--- a/docs/tutorials/pt/promotion-alerts-beta.md
+++ b/docs/tutorials/pt/promotion-alerts-beta.md
@@ -29,7 +29,7 @@ Se você configurar apenas a ação de alerta por email, outros pedidos com o de
 
 Para acessar a página no Admin VTEX, acesse *Promoções > Alerta de promoções*. A seguinte interface vai aparecer:
 
-![simuladordepromocoes gerenciar](//images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
+![simuladordepromocoes gerenciar](https://images.ctfassets.net/alneenqid6w5/4E0oZf13zNjKgj5MNRYiuf/94c9af89ae0bad5601b316dfc73a6caf/simuladordepromocoes_gerenciar.gif)
 
 A tabela a seguir apresenta a descrição das colunas da listagem de promoções:
 
diff --git a/docs/tutorials/pt/promotion-list-beta.md b/docs/tutorials/pt/promotion-list-beta.md
index 1875344d9..7e3f54b75 100644
--- a/docs/tutorials/pt/promotion-list-beta.md
+++ b/docs/tutorials/pt/promotion-list-beta.md
@@ -30,7 +30,7 @@ A página apresenta a lista com as promoções cadastradas na sua loja e suas in
 | `Até` | Data de término da promoção. |
 | `Status` | Status da promoção, que pode estar: <p> __Ativa:__ quando a promoção está ativada.</p> <p>__Programada:__ quando a promoção foi programada.</p> <p>__Pausada:__ quando a promoção estiver pausada. <p>__Finalizada:__ quando a promoção foi encerrada.</p> |
 
-![listadepromocoes pt](//images.ctfassets.net/alneenqid6w5/3vT0P63t0Kvm2heipqfpsT/5f4e74dae8d76243d8214588c2db247a/listadepromocoes_pt.gif)
+![listadepromocoes pt](https://images.ctfassets.net/alneenqid6w5/3vT0P63t0Kvm2heipqfpsT/5f4e74dae8d76243d8214588c2db247a/listadepromocoes_pt.gif)
 
 Você pode ordenar a exibição das promoções a partir do nome, das datas ou do status da promoção. Para isso, clique no título da coluna com a informação que você deseja utilizar como critério de ordenação.
 
@@ -82,7 +82,7 @@ O arquivo contém as seguintes informações sobre cada promoção:
 
 ## Uso das promoções
 
-![usodaspromoções pt](//images.ctfassets.net/alneenqid6w5/6kpAz3b5vxOjIb8o9Aouxe/2c9b92564afeadbeb777b04813fbe0fa/usodaspromo____es_pt.JPG)
+![usodaspromoções pt](https://images.ctfassets.net/alneenqid6w5/6kpAz3b5vxOjIb8o9Aouxe/2c9b92564afeadbeb777b04813fbe0fa/usodaspromo____es_pt.JPG)
 
 Para visualizar o total de promoções ativas na sua loja e a cota de espaço restante para novas promoções, clique em `Uso das promoções`.
 
@@ -90,7 +90,7 @@ O número máximo padrão de promoções ativas é 100. Caso precise aumentar es
 
 ## Filtrar promoções
 
-![filtrodepromocoes pt](//images.ctfassets.net/alneenqid6w5/3flpyzIkBlYDiuhYLea8nu/6e57eb53961b821b54233964711fe4d4/filtrodepromocoes_pt.gif)
+![filtrodepromocoes pt](https://images.ctfassets.net/alneenqid6w5/3flpyzIkBlYDiuhYLea8nu/6e57eb53961b821b54233964711fe4d4/filtrodepromocoes_pt.gif)
 
 A lista de promoções pode ser filtrada conforme a sua necessidade. A filtragem da lista pode ser feita pelos filtros a seguir: 
 
diff --git a/docs/tutorials/pt/promotion-summary.md b/docs/tutorials/pt/promotion-summary.md
index d2b315db6..62115cf15 100644
--- a/docs/tutorials/pt/promotion-summary.md
+++ b/docs/tutorials/pt/promotion-summary.md
@@ -63,16 +63,16 @@ O resumo da promoção pode exibir três tipos diferentes de alertas. Veja as de
 Alertas de alto risco indicam configurações ou falhas de preenchimento críticas que precisam ser revistas, pois podem comprometer negativamente a atuação da promoção e, consequentemente, a margem de operação da loja.
 
 Exemplo:
-![alert-alto-risco-PT](//images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/3f4a74d3d0222b13056831b2e941e8dd/image.png)
+![alert-alto-risco-PT](https://images.ctfassets.net/alneenqid6w5/5RRucT5TJJKfoe39NsQvPx/3f4a74d3d0222b13056831b2e941e8dd/image.png)
 
 ### Médio risco
 Alertas de médio risco apresentam avisos de configurações que podem causar efeitos indesejados na promoção.
 
 Exemplo:
-![alert-medio-risco-PT](//images.contentful.com/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/f13a84dd765566d3ca5939deee6e1d23/image.png)
+![alert-medio-risco-PT](https://images.contentful.com/alneenqid6w5/1vYDqk4ZK3X2jjfGBY0voq/f13a84dd765566d3ca5939deee6e1d23/image.png)
 
 ### Baixo risco 
 Alertas de baixo risco apresentam informações relevantes sobre a configuração da promoção, que podem contribuir para uma melhor performance.
 
 Exemplo:
-![alert-baixo-risco-PT](//images.contentful.com/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/4db7719d69da3936610f5c8ab32e0819/image.png)
+![alert-baixo-risco-PT](https://images.contentful.com/alneenqid6w5/tvjluVBbsK78ozr29Fgfb/4db7719d69da3936610f5c8ab32e0819/image.png)
diff --git a/docs/tutorials/pt/promotions-beta.md b/docs/tutorials/pt/promotions-beta.md
index 2036ac5b2..bc6ceb792 100644
--- a/docs/tutorials/pt/promotions-beta.md
+++ b/docs/tutorials/pt/promotions-beta.md
@@ -33,20 +33,20 @@ A página inicial apresenta a lista de promoções em uma grade que permite visu
 - Duplicar ou arquivar promoções através do botão <i class="fas fa-ellipsis-v"></i>
 - Gerenciar as condições da promoção clicando em qualquer parte da linha do grid (veja [Nova promoção](#nova-promocao) para detalhamento das condições da promoção).
 
-![promobeta1 acoes lista promocoes PT](//images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/75ce08a03318ebe1cf47d3a01b5b7c62/promobeta1_acoes_lista_promocoes_PT.gif)
+![promobeta1 acoes lista promocoes PT](https://images.ctfassets.net/alneenqid6w5/1iLvxFtAqM5pFOz6enx8KU/75ce08a03318ebe1cf47d3a01b5b7c62/promobeta1_acoes_lista_promocoes_PT.gif)
 
 A lista de promoções pode ser filtrada e ordenada conforme a sua necessidade. A filtragem da lista pode ser feita por *Efeito*, *Estado*, *Data início*, *Data fim* ou *Política comercial*.
 
-![promobeta2 filtros lista promocoes PT](//images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/8bbb1eefeee7a0f8b4c6c8746249481f/promobeta2_filtros_lista_promocoes_PT.gif)
+![promobeta2 filtros lista promocoes PT](https://images.ctfassets.net/alneenqid6w5/4UBGUJC4RTEA9alSeHmJlh/8bbb1eefeee7a0f8b4c6c8746249481f/promobeta2_filtros_lista_promocoes_PT.gif)
 
 A ordenação pode ser crescente ou decrescente a partir das informações básicas da promoção, bastando clicar sobre o título.
 
-![promobeta3 ordenacao lista promocoes PT](//images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/1c13ddd465a09fe39561b685a1dbe35f/promobeta3_ordenacao_lista_promocoes_PT.gif)
+![promobeta3 ordenacao lista promocoes PT](https://images.ctfassets.net/alneenqid6w5/60Z7afuYC3PqwTEPCVLVYd/1c13ddd465a09fe39561b685a1dbe35f/promobeta3_ordenacao_lista_promocoes_PT.gif)
 
 ## Nova promoção
 Na tela inicial, clique no botão **NOVA PROMOÇÃO** para acessar a página de criação de promoções, na qual você vai preencher uma variedade de campos para configurar as condições desejadas para a sua promoção.
 
-![promobeta4 botao novapromocao PT](//images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/e336ee376b77685d357999e5bd6430d2/promobeta4_botao_novapromocao_PT.png)
+![promobeta4 botao novapromocao PT](https://images.ctfassets.net/alneenqid6w5/4Zp0NocPVWeIW44Ky8pWqo/e336ee376b77685d357999e5bd6430d2/promobeta4_botao_novapromocao_PT.png)
 
 As condições da nova promoção, bem como os campos da tela, estão separados por grupos, sendo eles:
 
diff --git a/docs/tutorials/pt/promotions-simulator-beta.md b/docs/tutorials/pt/promotions-simulator-beta.md
index d89a7e6f6..e196c9b2a 100644
--- a/docs/tutorials/pt/promotions-simulator-beta.md
+++ b/docs/tutorials/pt/promotions-simulator-beta.md
@@ -35,7 +35,7 @@ O **Simulador de promoções** está disponível para todas as lojas VTEX pelo [
 
     Na nova janela, você verá uma listagem dos produtos presentes no seu carrinho. Será possível visualizar todas as promoções aplicadas e aplicáveis em cada um dos itens.
 
-![Simulator-promo-pt-gif-1](//images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/be250ed52b2c5abfcbf1a0debf120c98/simulador-promo-pt-230706.gif)
+![Simulator-promo-pt-gif-1](https://images.ctfassets.net/alneenqid6w5/66PaJF2TBi2T1VBEFPlLuz/be250ed52b2c5abfcbf1a0debf120c98/simulador-promo-pt-230706.gif)
 
 A interface do **Simulador de promoções** apresenta as seguintes informações:
 
@@ -79,7 +79,7 @@ Para editar uma promoção, siga os passos abaixo:
 
 O **Simulador de promoções** possibilita testar a aplicação de uma outra promoção ou simular o que aconteceria ao desativar promoções aplicadas. Para isso, clique no botão `Selecionar promoções`, no topo direito da página, conforme ilustrado na imagem abaixo.
 
-![ui-Simulator-promo-pt-gif-2](//images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/6bc4e0a9ee37002a0d265d57a156bff6/ui-simulador-promo-pt-230706.gif)
+![ui-Simulator-promo-pt-gif-2](https://images.ctfassets.net/alneenqid6w5/4CkGZCw0142IDUwH8VVf7A/6bc4e0a9ee37002a0d265d57a156bff6/ui-simulador-promo-pt-230706.gif)
 
 Para fazer uma simulação, siga as instruções abaixo:
 
diff --git a/docs/tutorials/pt/promotions-simulator.md b/docs/tutorials/pt/promotions-simulator.md
index ee09ae043..eb7a6b0d1 100644
--- a/docs/tutorials/pt/promotions-simulator.md
+++ b/docs/tutorials/pt/promotions-simulator.md
@@ -27,9 +27,9 @@ Para usar essa funcionalidade, primeiro você precisa [configurar o Cartman](htt
 2. No carrinho de compras, clique no botão <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/> para abrir o Cartman.
 3. Clique na opção `Ver detalhes da promoção`.
 4. Esta janela exibe as promoções aplicadas no carrinho. Para mais detalhes, clique em <i class="fas fa-search"></i>`Ver detalhes`.
-![cartman-analisador-promoção-PT](//images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/3978d26dac1793e9ced1f1d0e72c88d2/image.png)
+![cartman-analisador-promoção-PT](https://images.ctfassets.net/alneenqid6w5/43LSTCKfLxf0Buvbc3mNpQ/3978d26dac1793e9ced1f1d0e72c88d2/image.png)
 5. Em seguida, a janela **Simulador de Promoções** será exibida.
-![analisador-promoção-PT](//images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/8617bf80e3997673bcc274f1ef97da74/Screenshot_15.png)
+![analisador-promoção-PT](https://images.ctfassets.net/alneenqid6w5/6xNgt4sv7HTXcHfoJnX9B7/8617bf80e3997673bcc274f1ef97da74/Screenshot_15.png)
 
 Nesta janela, é possível consultar as seguintes informações:
 
diff --git a/docs/tutorials/pt/protection-against-transaction-attacks.md b/docs/tutorials/pt/protection-against-transaction-attacks.md
index 8734cda75..1bd91a0d8 100644
--- a/docs/tutorials/pt/protection-against-transaction-attacks.md
+++ b/docs/tutorials/pt/protection-against-transaction-attacks.md
@@ -36,9 +36,9 @@ Para habilitar a proteção, confira o passo a passo:
 4. No canto superior direito, clilque no ícone de configurações.
 5. Em __Proteção contra ataques__, clique no botão para habilitar (cor verde indica "habilitado").
 
-![proteção-botao-configurações](//images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
+![proteção-botao-configurações](https://images.ctfassets.net/alneenqid6w5/1jhGP8FOgMtkEp0O8AqOnX/c36c317b8cd30966cd76901c897219f3/prote____o-botao-configura____es.png)
 
-![proteção-opção-habilitar1](//images.ctfassets.net/alneenqid6w5/kk96NiBFAUzzuv23FbQeu/7f4c2e67f22c7aaa2886f9850a3fcc03/prote____o-op____o-habilitar1.png)
+![proteção-opção-habilitar1](https://images.ctfassets.net/alneenqid6w5/kk96NiBFAUzzuv23FbQeu/7f4c2e67f22c7aaa2886f9850a3fcc03/prote____o-op____o-habilitar1.png)
 
 ### Como desabilitar a proteção contra ataques em transações?
 
@@ -68,13 +68,13 @@ Para acessar estas informações, confira o passo a passo:
 6. Para selecionar __Ameaças detectadas__ ou __Ameaças neutralizadas__, clique em uma das setas à direita.
 7. Verifique os detalhes dos eventos na janela popup apresentada.
 
-![proteção-opção-historico1](//images.ctfassets.net/alneenqid6w5/19hGY1Jjv5DOBXABIxCnxd/43d9eb3c6c754576e2879fbc9c5f62bc/prote____o-op____o-historico1.png)
+![proteção-opção-historico1](https://images.ctfassets.net/alneenqid6w5/19hGY1Jjv5DOBXABIxCnxd/43d9eb3c6c754576e2879fbc9c5f62bc/prote____o-op____o-historico1.png)
 
-![proteção-tela-historico1](//images.ctfassets.net/alneenqid6w5/6p6N8EV2PnhzbnxFUkOWda/bec651a71aa79f2374426afefe8cdf23/prote____o-tela-historico1.png)
+![proteção-tela-historico1](https://images.ctfassets.net/alneenqid6w5/6p6N8EV2PnhzbnxFUkOWda/bec651a71aa79f2374426afefe8cdf23/prote____o-tela-historico1.png)
 
-![tela-ameaça-potencial1](//images.ctfassets.net/alneenqid6w5/4l9WCe1f7yYN9Gx0sczBXK/40dddb9cb38a2b415a57c262fc61faa0/tela-amea__a-potencial1.png)
+![tela-ameaça-potencial1](https://images.ctfassets.net/alneenqid6w5/4l9WCe1f7yYN9Gx0sczBXK/40dddb9cb38a2b415a57c262fc61faa0/tela-amea__a-potencial1.png)
 
-![tela-ameaça-neutralizada1](//images.ctfassets.net/alneenqid6w5/68JvVENRbcGGOcBFXno54/fe85365340965f6d7927f2d6525d27a2/tela-amea__a-neutralizada1.png)
+![tela-ameaça-neutralizada1](https://images.ctfassets.net/alneenqid6w5/68JvVENRbcGGOcBFXno54/fe85365340965f6d7927f2d6525d27a2/tela-amea__a-neutralizada1.png)
 
 ### Artigos relacionados
 
diff --git a/docs/tutorials/pt/qr-code-suiteshare.md b/docs/tutorials/pt/qr-code-suiteshare.md
index 93de33324..8fa24372a 100644
--- a/docs/tutorials/pt/qr-code-suiteshare.md
+++ b/docs/tutorials/pt/qr-code-suiteshare.md
@@ -19,7 +19,7 @@ Código QR é um código de barras bidimensional que pode ser facilmente escanea
 
 No VTEX Assisted Sales (SuiteShare) você conseguirá unir a tecnologia dos QRCODES com o Link de WhatsApp e fazer com que os clientes abram uma conversa com você no WhatsApp com apenas um escaneamento.
 
-![QR Code_1](//images.ctfassets.net/alneenqid6w5/2I4HDB3mTmDa7I0OPcmLH1/a9a86497f4a5a9e385a65d8ce422c3f1/QR_Code_1.png)
+![QR Code_1](https://images.ctfassets.net/alneenqid6w5/2I4HDB3mTmDa7I0OPcmLH1/a9a86497f4a5a9e385a65d8ce422c3f1/QR_Code_1.png)
 
 Se na sua empresa, você utiliza materiais impressos, esses códigos são a melhor opção para levar os clientes do offline para o online.
 
@@ -29,19 +29,19 @@ Se na sua empresa, você utiliza materiais impressos, esses códigos são a melh
 
 No painel do VTEX Assisted Sales (SuiteShare), acesse a opção _**Atrair > Links**_.
 
-![QR Code_2](//images.ctfassets.net/alneenqid6w5/3Gwg5q0rWo21D4oopPiVKS/29699a9f60e197f2fc0e2ca20dc79644/QR_Code_2.png)
+![QR Code_2](https://images.ctfassets.net/alneenqid6w5/3Gwg5q0rWo21D4oopPiVKS/29699a9f60e197f2fc0e2ca20dc79644/QR_Code_2.png)
 
 Clique no ícone do QRCODE, localizado no lado direito do link que você deseja criar um código.
 
-![QR Code_3](//images.ctfassets.net/alneenqid6w5/6pOgNXtgNW5QMs1fMwJyW9/0b1884f5e61b195c13fc8591f71f9491/QR_Code_3.png)
+![QR Code_3](https://images.ctfassets.net/alneenqid6w5/6pOgNXtgNW5QMs1fMwJyW9/0b1884f5e61b195c13fc8591f71f9491/QR_Code_3.png)
 
 Escolha um logotipo (Opcional):
 
-![QR Code_4](//images.ctfassets.net/alneenqid6w5/2eVNZiKJ6wUsq1f5NqqsPa/f793938eabeae194250c53668a5b84cd/QR_Code_4.png)
+![QR Code_4](https://images.ctfassets.net/alneenqid6w5/2eVNZiKJ6wUsq1f5NqqsPa/f793938eabeae194250c53668a5b84cd/QR_Code_4.png)
 
 Pronto! Agora você precisa escolher o formato do arquivo que deseja fazer o download (PNG, SVG, EPS) e adiciona-lo a sua arte do seu material no Corel Drawn, Ilustrator, Potoshop.
 
-![QR Code_5](//images.ctfassets.net/alneenqid6w5/1ExIlz752tONoKQOz5Eqml/5e63e2fc5c226a332e1ca091c1a98104/QR_Code_5.png)
+![QR Code_5](https://images.ctfassets.net/alneenqid6w5/1ExIlz752tONoKQOz5Eqml/5e63e2fc5c226a332e1ca091c1a98104/QR_Code_5.png)
 
 ## Saiba onde utilizar o QR code: 
 
diff --git a/docs/tutorials/pt/rdstation-crm-suiteshare.md b/docs/tutorials/pt/rdstation-crm-suiteshare.md
index 989ced14c..3445af419 100644
--- a/docs/tutorials/pt/rdstation-crm-suiteshare.md
+++ b/docs/tutorials/pt/rdstation-crm-suiteshare.md
@@ -19,22 +19,22 @@ Com essa integração é possível criar oportunidades via VTEX Assisted Sales (
 
 Para realizar está integração, clique na engrenagem que se encontra no canto superior direito e em seguida clique em **"Integrações"**.
 
-![RdStation CRM 1](//images.ctfassets.net/alneenqid6w5/4Wts5lWqc9NmkPrwjXSd5S/4da0068d32a5509dee6fb4ac230d74fc/Screenshot_2022-08-30_at_16-25-23_RdStation_CRM.png)  
+![RdStation CRM 1](https://images.ctfassets.net/alneenqid6w5/4Wts5lWqc9NmkPrwjXSd5S/4da0068d32a5509dee6fb4ac230d74fc/Screenshot_2022-08-30_at_16-25-23_RdStation_CRM.png)  
 
 Após clicar em integrações, localize o RD Station CRM e Clique em Habilitar.
 
-![RdStation CRM 2](//images.ctfassets.net/alneenqid6w5/73woJ2dZwHCMFCTDc7Jkce/bdb887e8700e217948d223008010494a/Screenshot_2022-08-30_at_16-25-27_RdStation_CRM.png)
+![RdStation CRM 2](https://images.ctfassets.net/alneenqid6w5/73woJ2dZwHCMFCTDc7Jkce/bdb887e8700e217948d223008010494a/Screenshot_2022-08-30_at_16-25-27_RdStation_CRM.png)
 
 Após clicar em Habilitar, selecione o link de [Captura](https://help.vtex.com/pt/tutorial/formulario-de-captura--6NJ6JyS3x5P2iWEZGadHAo) que irá integrar os dados para dentro do RD Station CRM.
 
-![RdStation CRM 3](//images.ctfassets.net/alneenqid6w5/14c77bx8MEprrVkfJwjFZ6/dfb058533fe2bbf8b3822010d8a4989a/Screenshot_2022-08-30_at_16-25-30_RdStation_CRM.png)
+![RdStation CRM 3](https://images.ctfassets.net/alneenqid6w5/14c77bx8MEprrVkfJwjFZ6/dfb058533fe2bbf8b3822010d8a4989a/Screenshot_2022-08-30_at_16-25-30_RdStation_CRM.png)
 
 Em seguida, insira o seu Token. Caso esteja com dificuldades para encontrar o seu token, [Clique Aqui](\"https://crmsupport.rdstation.com.br/hc/pt-br/articles/360018468312-O-que-%C3%A9-Token-Como-ativ%C3%A1-lo-\").
 
-![RdStation CRM 4](//images.ctfassets.net/alneenqid6w5/3NQT2ZZl3zbnJJIheFArXn/375deec9df31676a9998370777042d1b/Screenshot_2022-08-30_at_16-25-35_RdStation_CRM.png)
+![RdStation CRM 4](https://images.ctfassets.net/alneenqid6w5/3NQT2ZZl3zbnJJIheFArXn/375deec9df31676a9998370777042d1b/Screenshot_2022-08-30_at_16-25-35_RdStation_CRM.png)
 
 Após inserir o seu token, Preencha o campo usuário de acordo com qual usuário deve receber os leads dentro do CRM.
 
-![RdStation CRM 5](//images.ctfassets.net/alneenqid6w5/3P9Gen2qj3ccv4JhvaBsMk/91bf86407a3d551ff0bc8c6e70957f10/Screenshot_2022-08-30_at_16-25-39_RdStation_CRM.png)
+![RdStation CRM 5](https://images.ctfassets.net/alneenqid6w5/3P9Gen2qj3ccv4JhvaBsMk/91bf86407a3d551ff0bc8c6e70957f10/Screenshot_2022-08-30_at_16-25-39_RdStation_CRM.png)
 
 Pronto, seus leads Capturados serão integrados para o RD CRM.
diff --git a/docs/tutorials/pt/rdstation-suiteshare.md b/docs/tutorials/pt/rdstation-suiteshare.md
index 8fc4c2fe9..51c6e6399 100644
--- a/docs/tutorials/pt/rdstation-suiteshare.md
+++ b/docs/tutorials/pt/rdstation-suiteshare.md
@@ -21,28 +21,28 @@ Com essa integração via **VTEX Assisted Sales (SuiteShare)** (através do for
 
 Na dashboard em _**“Integrações”**_.
 
-![RdStation 1](//images.ctfassets.net/alneenqid6w5/2eZU6639ayDOZ8QCPfhvIm/b58704b43e43079e466f0c51e2902866/image.png)
+![RdStation 1](https://images.ctfassets.net/alneenqid6w5/2eZU6639ayDOZ8QCPfhvIm/b58704b43e43079e466f0c51e2902866/image.png)
 
 Ou clique em "_**configurações > Integrações"**_.
 
-![RdStation 2](//images.ctfassets.net/alneenqid6w5/69OR69XXK5ksuOkHyhA6ku/c1aaf7c386916941d553316b5b92a3fe/image.png)
+![RdStation 2](https://images.ctfassets.net/alneenqid6w5/69OR69XXK5ksuOkHyhA6ku/c1aaf7c386916941d553316b5b92a3fe/image.png)
 
 Selecione a RD Station e clique em _**“integrar”**_.
 
 Clique em _**“conectar”**_.
 
-![RdStation 3](//images.ctfassets.net/alneenqid6w5/4qA2jyDT6GchuNX1EQay0d/f474ba834120299d199781e04d57859d/image.png)
+![RdStation 3](https://images.ctfassets.net/alneenqid6w5/4qA2jyDT6GchuNX1EQay0d/f474ba834120299d199781e04d57859d/image.png)
 
 Faça login na sua conta no RD Station.
 
-![RdStation 4](//images.ctfassets.net/alneenqid6w5/54xB2yNgi98NQ4aas2MX21/b24bff869eb915b241ad26107e16e701/image.png)
+![RdStation 4](https://images.ctfassets.net/alneenqid6w5/54xB2yNgi98NQ4aas2MX21/b24bff869eb915b241ad26107e16e701/image.png)
 
 Escolha qual conta deseja conectar e clique em _**continuar**_.
 
-![RdStation 5](//images.ctfassets.net/alneenqid6w5/SJmHEE51Md5KjkSMXHtPi/cac3ffe38046d35a4d25f05044c04015/image.png)
+![RdStation 5](https://images.ctfassets.net/alneenqid6w5/SJmHEE51Md5KjkSMXHtPi/cac3ffe38046d35a4d25f05044c04015/image.png)
 
 Clique em _**“Conectar”**_.
 
-![RdStation 6](//images.ctfassets.net/alneenqid6w5/cEx8hWwX1dPWLgbxe5HbM/8e83613e252b12f7154eeb342af8e514/image.png)
+![RdStation 6](https://images.ctfassets.net/alneenqid6w5/cEx8hWwX1dPWLgbxe5HbM/8e83613e252b12f7154eeb342af8e514/image.png)
 
 Pronto! Você acabou de integrar a **VTEX Assisted Sales (SuiteShare)** com o seu CRM.
diff --git a/docs/tutorials/pt/ready-to-dispatch.md b/docs/tutorials/pt/ready-to-dispatch.md
index 8d6cdeec8..81eb6d8c3 100644
--- a/docs/tutorials/pt/ready-to-dispatch.md
+++ b/docs/tutorials/pt/ready-to-dispatch.md
@@ -92,7 +92,7 @@ Para imprimir etiquetas específicas e notificar as transportadoras encarregadas
 
 As transportadoras são notificadas quando é feito o download das etiquetas. 
 
-![etiquetas](//images.contentful.com/alneenqid6w5/1L1fExGcJgTPi3WD5nmWBL/7714df72cacfafda1d915aa86cc1203e/etiquetas.png)
+![etiquetas](https://images.contentful.com/alneenqid6w5/1L1fExGcJgTPi3WD5nmWBL/7714df72cacfafda1d915aa86cc1203e/etiquetas.png)
 
 <div class="alert alert-danger">
 Em caso de erros ou dúvidas, entre em contato diretamente com o suporte do <b>VTEX Shipping Network</b> através do email vtexlog@vtex.com.br.
diff --git a/docs/tutorials/pt/received-skus-beta.md b/docs/tutorials/pt/received-skus-beta.md
index f694bee29..269757e34 100644
--- a/docs/tutorials/pt/received-skus-beta.md
+++ b/docs/tutorials/pt/received-skus-beta.md
@@ -19,7 +19,7 @@ A página **SKUs recebidos** permite que o [marketplace](https://help.vtex.com/p
 
 A catalogação pode ser feita manualmente ou automaticamente, [por meio de um ou mais matchers](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher?locale=pt), e também pelo [autoApprove](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions/#put-/suggestions/configuration/autoapproval/toggle). Além disso, também existe a possibilidade de usar ferramentas externas para realizar essa operação.
 
-![Apresentação Anúncios Recebidos-PT](//downloads.ctfassets.net/alneenqid6w5/1qyRLboXsLXCwaoT3xfSwI/9882db31e2a68ebe127532f24cf4bcae/GIF_PT.gif)
+![Apresentação Anúncios Recebidos-PT](https://downloads.ctfassets.net/alneenqid6w5/1qyRLboXsLXCwaoT3xfSwI/9882db31e2a68ebe127532f24cf4bcae/GIF_PT.gif)
 
 Neste artigo você encontrará uma visão geral sobre a [Estrutura da página](#estrutura-da-pagina), [Priorizando a catalogação](#priorizando-a-catalogacao) e [Catalogação de itens](#catalogacao-de-itens).
 
@@ -49,7 +49,7 @@ Cada linha da lista representa um produto com as seguintes informações:
 
 Para verificar todas as especificações de um produto, clique sobre o nome do produto desejado e uma nova janela abrirá com todas as informações daquele produto.
 
-![pendentes-info-produto-PT](//images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/ea57f537bcad436fad6a45286adc7840/pendentes-info-produto-PT.png)
+![pendentes-info-produto-PT](https://images.ctfassets.net/alneenqid6w5/3QSXyYXqhdAB3R4J3lL749/ea57f537bcad436fad6a45286adc7840/pendentes-info-produto-PT.png)
 
 ### Problemas
 
@@ -61,7 +61,7 @@ A ação pedir correção não está disponível na seção <b>Problemas.</b>
 
 Para identificar qual o problema de um anúncio, basta clicar no nome do produto desejado. Uma nova janela será exibida com as informações referentes ao produto, a mensagem de erro e o revisor do anúncio.
 
-![problemas do produto-PT](//images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/f0a31393e47198a3ff81d0016c2491e9/problemas_do_produto-PT.png)
+![problemas do produto-PT](https://images.ctfassets.net/alneenqid6w5/4yZtOcq16r6SXvai0lWzau/f0a31393e47198a3ff81d0016c2491e9/problemas_do_produto-PT.png)
 
 ### Aprovados
 
@@ -120,7 +120,7 @@ Por padrão, os itens com envios mais recentes são os primeiros a serem listado
 
 Nesse caso, os itens serão ordenados de forma crescente ou decrescente ao clicar em **"Preço"** ou **"Estoque"** no cabeçalho.
 
-![ordenacao-PT](//images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/1f5cbbbae8c8b969fcabcfd531e57d95/ordenacao-PT.png)
+![ordenacao-PT](https://images.ctfassets.net/alneenqid6w5/3Eur3cPCdSTtZjoGIqeq6o/1f5cbbbae8c8b969fcabcfd531e57d95/ordenacao-PT.png)
 
 ## Catalogação de itens
 
@@ -147,7 +147,7 @@ As ações disponíveis para catalogação são:
   3. Preencha os campos **Categoria** e **Marca** para cada produto. Caso o mapeamento tenha sido realizado previamente, esses campos já estarão preenchidos.  
   4. Clique em `Aprovar`.  
 
-![criar-novos-produtos-PT](//images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/07a3e80b2b4143779da1ebfdd29729a7/criar-novos-produtos-PT.png)
+![criar-novos-produtos-PT](https://images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/07a3e80b2b4143779da1ebfdd29729a7/criar-novos-produtos-PT.png)
 
 <div class="alert alert-info">
 Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
@@ -160,7 +160,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
   3. Preencha o ID do produto ao qual será associado.
   4. Clique em `Aprovar`.  
 
-![associar-a-produto-PT](//images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/d2130d8af5d5de678c36a6821316c09a/associar-a-produto-PT.png)
+![associar-a-produto-PT](https://images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/d2130d8af5d5de678c36a6821316c09a/associar-a-produto-PT.png)
 
 **Caso de uso**
 
@@ -178,7 +178,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
   3. Preencha o ID do SKU a associar para cada SKU que está sendo aprovado.  
   4. Clique em `Aprovar`.  
 
-![associar-a-sku-PT](//images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/9a4c3fdb8049f6825fe752baae239b52/associar-a-sku-PT.png)
+![associar-a-sku-PT](https://images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/9a4c3fdb8049f6825fe752baae239b52/associar-a-sku-PT.png)
 
 **Caso de uso**
 
@@ -197,7 +197,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
   3. Preencha o campo **Motivo de bloqueio.** O preenchimento é opcional.  
   4. Clique em `Recusar`.  
 
-![recusar-e-bloquear-PT](//images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/35b8c59c3b4284047fba1882372c8e88/recusar-e-bloquear-PT.png)
+![recusar-e-bloquear-PT](https://images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/35b8c59c3b4284047fba1882372c8e88/recusar-e-bloquear-PT.png)
 
 Quando um SKU é bloqueado pelo marketplace, significa que na próxima vez que o seller enviar seus produtos, aqueles que foram bloqueados não estarão mais em meio aos enviados. É possível desbloquear um SKU por API REST, se o marketplace deseja voltar a recebê-lo como sugestão do seller.  
 Para saber mais sobre aprovação de SKUs, acesse nossa documentação [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).
@@ -213,7 +213,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
   3. Preencha o campo **correções** com a informação a ser corrigida pelo seller.  
   4. Clique em `Recusar`.  
 
-![recusar-e-corrigir-PT](//images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/e53cdbf195194a408fb05f790f812083/recusar-e-corrigir-PT.png)
+![recusar-e-corrigir-PT](https://images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/e53cdbf195194a408fb05f790f812083/recusar-e-corrigir-PT.png)
 
 <div class="alert alert-info">
 Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b>. Os anúncios para correção serão exibidos na seção <b>Problemas</b>.
diff --git a/docs/tutorials/pt/registered-ticket-flow.md b/docs/tutorials/pt/registered-ticket-flow.md
index f052505de..af6263ef5 100644
--- a/docs/tutorials/pt/registered-ticket-flow.md
+++ b/docs/tutorials/pt/registered-ticket-flow.md
@@ -23,7 +23,7 @@ A seguir, veremos como funciona o fluxo básico de um pagamento com boleto regis
  
 ## Emissão do Boleto
 
-![Frame 2](//images.contentful.com/alneenqid6w5/2CqwPgtFuIkgkkus2y8gg0/69c19ff0cf7116579b3e3b91342189b3/Frame_2.png)
+![Frame 2](https://images.contentful.com/alneenqid6w5/2CqwPgtFuIkgkkus2y8gg0/69c19ff0cf7116579b3e3b91342189b3/Frame_2.png)
 
 1. Seu __e-commerce__ informa ao __Gateway__ que um pedido será pago através de boleto bancário.
 2. O gateway entra em contato com o __Banco__ para realizar o registro do boleto.
@@ -35,7 +35,7 @@ Neste momento, o boleto ainda não foi pago pelo cliente.
 
 ## Pagamento do Boleto e Conciliação Bancária
 
-![Frame 2.1](//images.contentful.com/alneenqid6w5/8xi6DVozxSiWi2sWegG4c/b23a178d5c8ddcc3b8c6196df22119af/Frame_2.1.png)
+![Frame 2.1](https://images.contentful.com/alneenqid6w5/8xi6DVozxSiWi2sWegG4c/b23a178d5c8ddcc3b8c6196df22119af/Frame_2.1.png)
 
 1. O __Cliente__ paga o boleto diretamente ao __Banco__.
 2. O banco envia para o __Gateway__ os arquivos de [conciliação bancária](/pt/tutorial/conciliacoes-bancarias) com as informações sobre o status de pagamento dos boletos.
diff --git a/docs/tutorials/pt/registering-brands.md b/docs/tutorials/pt/registering-brands.md
index 45828225e..0115de444 100644
--- a/docs/tutorials/pt/registering-brands.md
+++ b/docs/tutorials/pt/registering-brands.md
@@ -23,4 +23,4 @@ Para cadastrar uma marca, siga os passos abaixo:
 4. Preencha os [campos de cadastro de marca](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-marca--37Ky7lTbEkiWIAYA80EMyI).
 5. Clique no botão `Salvar`.
 
-![cadastrarmarcas3](//images.ctfassets.net/alneenqid6w5/4PK9aPVzNJrp478wRsSUM0/6aabac3201d04805ea18c3d03c11593c/cadastrarmarcas3.PNG)
+![cadastrarmarcas3](https://images.ctfassets.net/alneenqid6w5/4PK9aPVzNJrp478wRsSUM0/6aabac3201d04805ea18c3d03c11593c/cadastrarmarcas3.PNG)
diff --git a/docs/tutorials/pt/registering-gateway-affiliations.md b/docs/tutorials/pt/registering-gateway-affiliations.md
index d6a9ecdf4..e90f10e98 100644
--- a/docs/tutorials/pt/registering-gateway-affiliations.md
+++ b/docs/tutorials/pt/registering-gateway-affiliations.md
@@ -23,7 +23,7 @@ Por meio da tela de gerenciamento de provedores você pode:
 - [Visualizar provedores cadastrados](#visualizar-provedores-cadastrados)
 - [Editar configurações de provedores](#editar-configuracoes-de-provedores)
 
-![interface_provedor_PT_1](//images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/d997ea6d0bf7807c1219d307933467e6/interface_provedor_PT_1.JPG)
+![interface_provedor_PT_1](https://images.ctfassets.net/alneenqid6w5/6721j5gbs4JkxAFJ9QPQve/d997ea6d0bf7807c1219d307933467e6/interface_provedor_PT_1.JPG)
 
 ## Cadastrar provedor
 
@@ -48,7 +48,7 @@ Para configurar os métodos de pagamento a serem processados pelo provedor de pa
 
 Para definir condições especiais sobre os métodos de pagamento, acesse [Configurar condições especiais de Pagamento](https://help.vtex.com/pt/tutorial/condiciones-especiales--tutorials_456?&utm_source=autocomplete).
 
-![interface_provedor_PT_2](//images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/03ec92c0a18fd9cc8b368fd27a4eeee2/artigo_interface_provedor_PT_2.JPG)
+![interface_provedor_PT_2](https://images.ctfassets.net/alneenqid6w5/2uzCrSICV4zlbieq13Vky0/03ec92c0a18fd9cc8b368fd27a4eeee2/artigo_interface_provedor_PT_2.JPG)
 
 ## Visualizar provedores cadastrados
 
@@ -58,7 +58,7 @@ A tela principal de gerenciamento de provedores, disponível no Admin VTEX em __
 
 Para localizar provedores pelo nome, acesse a página de gerenciamento de provedores e digite o nome do provedor desejado.
 
-![interface_provedor_PT_3](//images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/b7489e1bd5b8f23cf1c41190266c7178/interface_provedor_PT_3.JPG)
+![interface_provedor_PT_3](https://images.ctfassets.net/alneenqid6w5/1AVxMc8gzpBLTaoOM3DqJt/b7489e1bd5b8f23cf1c41190266c7178/interface_provedor_PT_3.JPG)
 
 ### Filtrar provedores
 
@@ -66,15 +66,15 @@ Para selecionar a exibição de provedores por meio de filtros, acesse a página
 
 - __Nome__: selecione a exibição de provedores de pagamento por meio do nome, ativando a caixa de texto ou digitando na barra de busca do menu.
 
-![interface_provedor_PT_4](//images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/b994729bad2abcc7fff53dbae2c45788/interface_provedor_PT_4.JPG)
+![interface_provedor_PT_4](https://images.ctfassets.net/alneenqid6w5/3HWuAtg2Ei867PMhqqXTpZ/b994729bad2abcc7fff53dbae2c45788/interface_provedor_PT_4.JPG)
 
 - __Tipo__: selecione a exibição de provedores de pagamento, antifraude ou ambos.
 
-![interface_provedor_PT_5](//images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/52542c9cbf58ab10d6527e5b5c8efd17/interface_provedor_PT_5.JPG)
+![interface_provedor_PT_5](https://images.ctfassets.net/alneenqid6w5/34wou6AALCHGCAMSufWpxZ/52542c9cbf58ab10d6527e5b5c8efd17/interface_provedor_PT_5.JPG)
 
 - __Ambiente__: selecione a exibição de provedores pelo tipo de ambiente de operação cadastrado (produção ou teste).
 
-![interface_provedor_PT_6](//images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/fe3d094d3ce7e5463841694309b28a52/interface_provedor_PT_6.JPG)
+![interface_provedor_PT_6](https://images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/fe3d094d3ce7e5463841694309b28a52/interface_provedor_PT_6.JPG)
 
 <div class = "alert alert-danger">
 Para remover os filtros aplicados e voltar a visualizar todos os provedores cadastrados na loja, clique no botão <code>Limpar todos</code>.</div>
@@ -88,7 +88,7 @@ Para editar configurações de provedores de pagamento ou antifraude já cadastr
 3. Na tela de configuração do provedor, clique em `Editar`.
 4. Realize as modificações necessárias e clique em `Salvar`.
 
-![interface_provedor_PT_7](//images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/1852b341c59e2ac6419504214fcfdee0/artigo_interface_provedor_PT_7.JPG)
+![interface_provedor_PT_7](https://images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/1852b341c59e2ac6419504214fcfdee0/artigo_interface_provedor_PT_7.JPG)
 
 <div class = "alert alert-danger">
 Antes de realizar qualquer alteração na configuração de um provedor, como por exemplo: dados de autorização, modo de processamento ou tipo de reembolso, certifique-se de que as novas informações a serem inseridas não irão prejudicar o seu desempenho operacional na loja.</div>
diff --git a/docs/tutorials/pt/registering-sku-price.md b/docs/tutorials/pt/registering-sku-price.md
index 30c0962f1..d614a911c 100644
--- a/docs/tutorials/pt/registering-sku-price.md
+++ b/docs/tutorials/pt/registering-sku-price.md
@@ -21,7 +21,7 @@ O processo manual é mais indicado para quando o lojista deseja alterar o preço
 
 ## Cadastro ou alteração manual
 
-![](//images.contentful.com/alneenqid6w5/62eMKlDZ04As4ey46yiOeK/2d689eb25d9945a532d4447ba770649f/Tabela_de_Valores.gif)
+![](https://images.contentful.com/alneenqid6w5/62eMKlDZ04As4ey46yiOeK/2d689eb25d9945a532d4447ba770649f/Tabela_de_Valores.gif)
 
 ### Cadastrar para um valor novo
 
@@ -59,7 +59,7 @@ _Se clicar no botão “Novo Valor de Tabela” após filtrar um SKU, esse será
 
 ## Cadastro ou alteração via importação de planilha do Excel
 
-![](//images.contentful.com/alneenqid6w5/5Pbm0WFO12QmEwW88OM2iU/453748487c805f0ef7bd20887e454670/Altera__o_de_pre_o_Importa__o.gif)
+![](https://images.contentful.com/alneenqid6w5/5Pbm0WFO12QmEwW88OM2iU/453748487c805f0ef7bd20887e454670/Altera__o_de_pre_o_Importa__o.gif)
 
 ### Para cadastrar novos preços
 
@@ -87,7 +87,7 @@ _Se clicar no botão “Novo Valor de Tabela” após filtrar um SKU, esse será
 
 ### Campos da planilha do Excel para importação
 
-![](//images.contentful.com/alneenqid6w5/1wTiiJMsUcUGMoI6GGWsOw/b31f627d1a8d642532d475fd72e23ff6/Como_cadastrar_preco_SKU_2.jpg)
+![](https://images.contentful.com/alneenqid6w5/1wTiiJMsUcUGMoI6GGWsOw/b31f627d1a8d642532d475fd72e23ff6/Como_cadastrar_preco_SKU_2.jpg)
 
 - **StockKeepingUnitId: **Id do SKU que deseja cadastrar ou alterar o preço;
 - **Source: **valor de utm_source;
diff --git a/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
index 135883e1e..a3dbaa3be 100644
--- a/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -19,7 +19,7 @@ Ao criar uma [promoção regular](https://help.vtex.com/pt/tutorial/promocao-reg
 
 Selecionando esse tipo de desconto, você precisa criar uma fórmula para definir qual será o cálculo do desconto aplicado. Neste artigo, explicamos como construir uma fórmula para atender aos objetivos da sua promoção.
 
-![tipo-desconto-formula](//images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/fa412a32b6d8d56b3652332ade308dd0/image1.png)
+![tipo-desconto-formula](https://images.ctfassets.net/alneenqid6w5/5NTM35GkPQtUzA6CKDco9q/fa412a32b6d8d56b3652332ade308dd0/image1.png)
 
 De modo geral, a fórmula para calcular o desconto nominal da promoção segue a mesma lógica das [fórmulas do Microsoft Excel](https://support.microsoft.com/pt-br/office/f%C3%B3rmulas-e-fun%C3%A7%C3%B5es-294d9486-b332-48ed-b489-abe7d0f9eda9), ou seja, você pode utilizar [variáveis](#variaveis) (`total`, `freight` e `quantity`), realizar [operações](#operacoes) (soma, subtração, multiplicação e divisão), e aplicar [funções](#funcoes) (`min` e `max`).
 
@@ -78,19 +78,19 @@ Assim, a promoção vai aplicar o menor valor de desconto em cada caso, comparan
 
 Um cliente adicionou ao carrinho um item cujo preço é R$45. Ao calcular 20% do total do preço, o resultado é 9, já que `total * 0.2 = 9`. Como 9 está abaixo do valor limite de desconto, o desconto aplicado será R$9.
 
-![cenario-1](//images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/f02144b4ab13eedb33d12f478c273f3d/image3.png)
+![cenario-1](https://images.ctfassets.net/alneenqid6w5/22tobaXfukykfntCXBpISS/f02144b4ab13eedb33d12f478c273f3d/image3.png)
 
 #### Cenário 2
 
 Outro cliente adicionou ao carrinho um item cujo preço é R$ 2600. Calculando 20% desse valor, o resultado é 520, já que `total * 0.2 = 520`. Como esse valor está acima do limite (R$10), o desconto aplicado será de R$10.
 
-![cenario-2](//images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/8da8d4eb9f5facad8c1023e115a9cdae/image7.png)
+![cenario-2](https://images.ctfassets.net/alneenqid6w5/6M3rMa2VKBXNtDV44J3x5w/8da8d4eb9f5facad8c1023e115a9cdae/image7.png)
 
 #### Cenário 3
 
 Um terceiro cliente adicionou dois itens ao carrinho: um cujo preço é R$100 e outro cujo preço é R$2600. A soma desses valores é R$2700, visto que `total = 2700`. Ao calcular 20% do valor total, obtemos o resultado de 540, já que `total * 0.2 = 540`. Como esse valor está acima do limite (R$10), o desconto total aplicado será de R$10.
 
-![cenario-3](//images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/2d57ca1c8a1f0093721d6fc14fc96095/image2.png)
+![cenario-3](https://images.ctfassets.net/alneenqid6w5/2lYHI6Iw0pZ8sOyN282TDr/2d57ca1c8a1f0093721d6fc14fc96095/image2.png)
 
 O desconto total de R$10 é distribuído proporcionalmente entre os itens, considerando o preço e a quantidade de cada um. Essa distribuição é feita automaticamente pela plataforma, seguindo a lógica explicada a seguir.
 
diff --git a/docs/tutorials/pt/regular-promotion-with-reward-value.md b/docs/tutorials/pt/regular-promotion-with-reward-value.md
index 61dddab23..3e3ec45ff 100644
--- a/docs/tutorials/pt/regular-promotion-with-reward-value.md
+++ b/docs/tutorials/pt/regular-promotion-with-reward-value.md
@@ -39,7 +39,7 @@ O **Valor fidelidade nominal** adiciona um valor fixo de crédito na conta do us
 
 No exemplo ilustrado a seguir, os clientes ganharão um crédito de R$10,00 na loja quando o status do pedido mudar para **Faturado**.
 
-![vf-nominal-pt](//images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/f2498f3f46cbafe7e1d8dd747422cce8/vf-nominal-pt.png)
+![vf-nominal-pt](https://images.ctfassets.net/alneenqid6w5/5i67rFawcAHCOpI84bBP2U/f2498f3f46cbafe7e1d8dd747422cce8/vf-nominal-pt.png)
 
 ### Valor fidelidade percentual
 
@@ -50,7 +50,7 @@ O **Valor fidelidade percentual** adiciona um valor percentual de crédito basea
 
 No exemplo ilustrado a seguir, os clientes ganharão um crédito de 20% do valor da compra quando o status do pedido mudar para **Pagamento aprovado**.
 
-![vf-percentual-pt](//images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4373e3263836d3388356a06dc025f73a/vf-percentual-pt.png)
+![vf-percentual-pt](https://images.ctfassets.net/alneenqid6w5/4EIq0OwX5GI1FgdWk0JHje/4373e3263836d3388356a06dc025f73a/vf-percentual-pt.png)
 
 ## Como configurar restrições
 
@@ -92,11 +92,11 @@ Na seção **Promoções e parcerias**, aparece o nome da promoção aplicada ao
 
 Na seção __Fluxo do pedido__, é possível verificar o valor fidelidade concedido:
 
-![fluxo-oms-pt](//images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/57cc8d05f5a909b360634d35bb5eb54e/fluxo-oms-pt__1_.png)
+![fluxo-oms-pt](https://images.ctfassets.net/alneenqid6w5/62q5OKyu3BqHmbd23HVyOc/57cc8d05f5a909b360634d35bb5eb54e/fluxo-oms-pt__1_.png)
 
 Se você utiliza a nova interface de [Detalhes do pedido (Beta)](https://help.vtex.com/pt/tutorial/order-details-page-beta--2Y75n54Cc9VizrlG1N6ZNl), acesse `Ver interações` para verificar o valor concedido:
 
-![interacoes-neworders-pt (1)](//images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/0b7c14a0db14110258c907a78377ec7a/interacoes-neworders-pt__1_.png)
+![interacoes-neworders-pt (1)](https://images.ctfassets.net/alneenqid6w5/7jjz0zNzeoZbOZ4PapQ836/0b7c14a0db14110258c907a78377ec7a/interacoes-neworders-pt__1_.png)
 
 Considere que a promoção aplicada no pedido ilustrado oferece **Valor fidelidade percentual** de **50%**. Por isso, a cliente ganhou um crédito de `R$ 54,28` para as próximas compras na loja, que equivale a **50%** de `R$ 108,55`, o valor total do pedido.
 
@@ -104,13 +104,13 @@ Considere que a promoção aplicada no pedido ilustrado oferece **Valor fidelida
 
 O valor fidelidade disponível para uso é apresentado para os clientes da sua loja na etapa de **Pagamento** durante o checkout, conforme ilustrado a seguir.
 
-![checkout-pt (1)](//images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
+![checkout-pt (1)](https://images.ctfassets.net/alneenqid6w5/6TNM6G9j4f3vnD7JERO6TE/60bf6f957d722190baf2c3c3e9b8a302/checkout-pt__1_.png)
 
 O valor concedido pode ser utilizado para compor o pagamento. Para isso, o cliente deve clicar em `utilizar crédito` e, em seguida, digitar o valor que deseja utilizar.
 
 Observe que o valor será descontado da outra forma de pagamento selecionada. No exemplo a seguir, o boleto passou a ter o valor de `R$ 113,50`, que corresponde a `R$ 167,80` menos o valor fidelidade utilizado (`R$ 54,30`).
 
-![checkout-2-pt (1)](//images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
+![checkout-2-pt (1)](https://images.ctfassets.net/alneenqid6w5/6pM4KJyCPRijRDFqLHNehz/26f4604ae74e66ebfc41040164d8c1e9/checkout-2-pt__1_.png)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/regular-promotion.md b/docs/tutorials/pt/regular-promotion.md
index c60d28a60..e1d15ffcd 100644
--- a/docs/tutorials/pt/regular-promotion.md
+++ b/docs/tutorials/pt/regular-promotion.md
@@ -90,7 +90,7 @@ Para que a promoção seja válida para todas as políticas comerciais, deixe a
 
 Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
 
-![promocoes-restricao-pt](//images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
+![promocoes-restricao-pt](https://images.ctfassets.net/alneenqid6w5/55xxIduLJDJrwQMuk4OgRu/359155bac11f7ac88a4d12a041cf8b96/image.png)
 
 Caso deseje aplicar a promoção a todo o seu catálogo, selecione a opção **Aplicar a todos os produtos**.
 
@@ -100,7 +100,7 @@ Você pode incluir ou excluir **Categorias**, **Marcas**, **Coleções**, **Prod
 
 Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção todos os produtos da categoria **Vestido** cuja marca é **Farm**, com a exceção do produto **Vestido Rosas**.
 
-![exemplo-pt](//images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/6c40e996aece6e87b82b0bc71a50f3e5/image.png)
+![exemplo-pt](https://images.ctfassets.net/alneenqid6w5/69J3NHBR8yLbbn04SSc5er/6c40e996aece6e87b82b0bc71a50f3e5/image.png)
 
 Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
 
diff --git a/docs/tutorials/pt/releases-module-beta.md b/docs/tutorials/pt/releases-module-beta.md
index ff467b48f..2ea1b2b1d 100644
--- a/docs/tutorials/pt/releases-module-beta.md
+++ b/docs/tutorials/pt/releases-module-beta.md
@@ -73,7 +73,7 @@ Nesta etapa, não é obrigatório preencher os campos <b>Dia da publicação</b>
 
 8. Clique em `Criar`.
 
-![print_cms_paginas_pt](//images.ctfassets.net/alneenqid6w5/qAAAv5fblHtY8C930fegs/10a16411a1e4d6ac49fcdf0e5729c88b/print_cms_paginas.png)
+![print_cms_paginas_pt](https://images.ctfassets.net/alneenqid6w5/qAAAv5fblHtY8C930fegs/10a16411a1e4d6ac49fcdf0e5729c88b/print_cms_paginas.png)
 
 ### Criar usando o módulo Lançamentos
 
@@ -94,7 +94,7 @@ Nesta etapa, não é obrigatório preencher os campos <b>Dia da publicação</b>
 
 Todos os lançamentos criados aparecem listados no Admin VTEX, em **Configurações da loja > Lançamentos**. A página apresenta duas abas, a `AGENDADOS` e a `NÃO AGENDADOS`, dependendo se o lançamento foi criado com uma data de publicação ou não. 
 
-![print_lancamentos_pt](//images.ctfassets.net/alneenqid6w5/5i9KXnDxE2lc3xqcdA3Ts7/a7466170347535b2062f66a533cfc2f6/print_lancamentos.png)
+![print_lancamentos_pt](https://images.ctfassets.net/alneenqid6w5/5i9KXnDxE2lc3xqcdA3Ts7/a7466170347535b2062f66a533cfc2f6/print_lancamentos.png)
 
 Na aba `AGENDADOS`, a descrição de cada coluna é a seguinte:
 
diff --git a/docs/tutorials/pt/releasing-the-store-for-production.md b/docs/tutorials/pt/releasing-the-store-for-production.md
index 23670fa4d..a2725bbf4 100644
--- a/docs/tutorials/pt/releasing-the-store-for-production.md
+++ b/docs/tutorials/pt/releasing-the-store-for-production.md
@@ -30,7 +30,7 @@ Depois, é preciso colocar a loja com status de produção no License Manager d
 4. Na opção **Está em produção**, clique no botão **Não**, ficando **Sim**;
 5. Clique no botão **Salvar**.
 
-![contas.pt](//images.ctfassets.net/alneenqid6w5/7bNDNf7soYiH98n5m8GFI6/695149200124cd522b0e2b6962014cf9/contas.pt.png)
+![contas.pt](https://images.ctfassets.net/alneenqid6w5/7bNDNf7soYiH98n5m8GFI6/695149200124cd522b0e2b6962014cf9/contas.pt.png)
 
 Após esta configuração, ao acessar a url final da loja, ela já será redirecionada para seu e-commerce!
 
diff --git a/docs/tutorials/pt/relevance-rules.md b/docs/tutorials/pt/relevance-rules.md
index 36bf23e61..3068fd888 100644
--- a/docs/tutorials/pt/relevance-rules.md
+++ b/docs/tutorials/pt/relevance-rules.md
@@ -24,7 +24,7 @@ Existem dois cenários possíveis de configurações de relevância:
 - **Critérios prioritários:** é a forma de forçar que um ou mais critérios terão prioridade maior entre os demais. Nessa situação não existem pesos, pois todos os produtos que possuírem essa característica serão apresentados primeiro no resultado de busca.
 - **Composição de critérios:** é a forma de distribuir pesos para cada opção, variando de 0 a 10. Aqui, não existe uma ordem entre os critérios, serão os pesos que vão definir a relevância.
 
-![criterios-pt](//images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/faefb674583084511a114faf0c39cdbd/criterios-pt.png)
+![criterios-pt](https://images.ctfassets.net/alneenqid6w5/2okH4XcNScAzf6PJIlOKqs/faefb674583084511a114faf0c39cdbd/criterios-pt.png)
 
 As informações aplicadas para compor a relevância são:
 
@@ -110,5 +110,5 @@ Para alterar a configuração de relevância, siga os passos abaixo.
 
    Caso você queira mudar a posição de um critério de **Composição de critérios** para **Critérios prioritários**, arraste-o pelo ícone <i class="fas fa-grip-vertical"></i> para a área superior, conforme ilustrado na imagem abaixo. Note que quando o critério se torna prioritário, não é mais possível alterar seu peso. 
 
-    ![criterios-prioritarios-pt](//images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/43155e1e110f6ec8eaff5debf9d8a2df/criterios-prioritarios-pt.gif)
+    ![criterios-prioritarios-pt](https://images.ctfassets.net/alneenqid6w5/c6CNsiZOSl7WnmP7k8Ffa/43155e1e110f6ec8eaff5debf9d8a2df/criterios-prioritarios-pt.gif)
 5. Para finalizar, clique em `Salvar`.
diff --git a/docs/tutorials/pt/remarketing.md b/docs/tutorials/pt/remarketing.md
index 198d894b7..c5cfb02ff 100644
--- a/docs/tutorials/pt/remarketing.md
+++ b/docs/tutorials/pt/remarketing.md
@@ -23,19 +23,19 @@ Estudos comprovam que o remarketing é 7x mais barato do que impulsionar um anú
 
 Para começar acesse o painel da Suiteshare, escolha a opção \\"_**Atrair > Remarketing\\".**_
 
-![Remarketing 1](//images.ctfassets.net/alneenqid6w5/66Ky5eCdV4c52T5Dt9dLos/e73774f335c569358e12c9d3c0e86fee/Screenshot_2022-08-30_at_11-24-18_Remarketing.png)
+![Remarketing 1](https://images.ctfassets.net/alneenqid6w5/66Ky5eCdV4c52T5Dt9dLos/e73774f335c569358e12c9d3c0e86fee/Screenshot_2022-08-30_at_11-24-18_Remarketing.png)
 
 Na nova página, clique no botão _**“Novo”**_
 
-![Remarketing 2](//images.ctfassets.net/alneenqid6w5/2ajyBDBc5UaqXlbcjJ4uv5/432c832d0c7a4db385aaa561aca2a6a2/Screenshot_2022-08-30_at_11-24-23_Remarketing.png)
+![Remarketing 2](https://images.ctfassets.net/alneenqid6w5/2ajyBDBc5UaqXlbcjJ4uv5/432c832d0c7a4db385aaa561aca2a6a2/Screenshot_2022-08-30_at_11-24-23_Remarketing.png)
 
 Na opção Plataforma, escolha qual é a rede social que você irá utilizar para fazer o remarketing. Depois, clique em \\"_**avançar\\".**_
 
-![Remarketing 3](//images.ctfassets.net/alneenqid6w5/7irDLNWoiNDJXCETGRhrtv/6a6b5f717c6493d1cd857375927a6b2b/Screenshot_2022-08-30_at_11-24-27_Remarketing.png)
+![Remarketing 3](https://images.ctfassets.net/alneenqid6w5/7irDLNWoiNDJXCETGRhrtv/6a6b5f717c6493d1cd857375927a6b2b/Screenshot_2022-08-30_at_11-24-27_Remarketing.png)
 
 Defina as configurações de dados do Pixel.
 
-![Remarketing 4](//images.ctfassets.net/alneenqid6w5/4MCC8CYfYtyxcImTAngxiX/78549c164908fb3c706cf745d845f99b/Screenshot_2022-08-30_at_11-24-32_Remarketing.png)
+![Remarketing 4](https://images.ctfassets.net/alneenqid6w5/4MCC8CYfYtyxcImTAngxiX/78549c164908fb3c706cf745d845f99b/Screenshot_2022-08-30_at_11-24-32_Remarketing.png)
 
 Em **Identificador**, dê um nome ao seu pixel para reconhecê-lo facilmente dentro da plataforma da **Suiteshare**.
 
@@ -49,7 +49,7 @@ Clique no botão _**“avançar”**_.
 
 Informe como o Remarketing irá rastrear os seus clientes. Em Conexão, você deve selecionar o link que os clientes irão clicar para iniciar uma conversa com o seu time de atendimento. O link selecionado será trackeado e, se desejar, poderá selecionar mais de um.
 
-![Remarketing 5](//images.ctfassets.net/alneenqid6w5/23NHac0nN3Nz8yzktILGn2/52e1a5e94731325df8624c8b44263b90/Screenshot_2022-08-30_at_11-24-37_Remarketing.png)
+![Remarketing 5](https://images.ctfassets.net/alneenqid6w5/23NHac0nN3Nz8yzktILGn2/52e1a5e94731325df8624c8b44263b90/Screenshot_2022-08-30_at_11-24-37_Remarketing.png)
 
 Clique em _**“Finalizar”.**_
 
diff --git a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
index 1bbd7befa..7a11bcfda 100644
--- a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -21,7 +21,7 @@ A mensagem "__Request headers must contain only ASCII characters__" pode ser exi
 
 Este cenário ocorre se a página ou funcionalidade solicitada contém um cookie com caracteres especiais (não-ASCII).
 
-![ascii_1](//images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/1001eedf70586fcfeaf7847eb641ee5a/ascii_1.png)
+![ascii_1](https://images.ctfassets.net/alneenqid6w5/geQO7G0cIDk7FmSjC9ZmQ/1001eedf70586fcfeaf7847eb641ee5a/ascii_1.png)
 
 Segundo as normas do [IETF](https://www.ietf.org/) (Internet Engineering Task Force), instituição responsável por documentar os padrões utilizados na internet, cookies não devem conter caracteres especiais (não-ASCII). Para mais informações sobre os caracteres aceitos em cookies e headers, acesse [IETF - Request for Comments 7230 - Section 3.2.6 - Field Value Components](https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6). 
 
@@ -41,19 +41,19 @@ Na página em que a mensagem "__Request headers must contain only ASCII characte
 
 <blockquote><ui>2. Na barra superior da tela, acesse a aba <b>Rede</b> e ordene as requisições clicando em <b>Status</b>. A informação <b>400</b> no status indica que uma requisição não foi processada corretamente e, dentre os erros possíveis, pode haver cookies incorretos.</ui>  
 
-![ascii 2](//images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/151a66fb0ce501c47e77869a8b4b6de3/ascii_2.png)    
+![ascii 2](https://images.ctfassets.net/alneenqid6w5/KAwQG2JiXozFU5Pjgjv3Z/151a66fb0ce501c47e77869a8b4b6de3/ascii_2.png)    
 
 <blockquote><ui>3. Clique sobre uma requisição e depois na aba <b>Visualização</b> para identificar se o erro encontrado é referente à mensagem "<b>Request headers must contain only ASCII characters</b>".</ui>
 
-![ascii 3](//images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/05f662484ece5d1e5876684319b32c62/ascii_3.png)
+![ascii 3](https://images.ctfassets.net/alneenqid6w5/16XPfE6SIwVO8SkTxl9yuR/05f662484ece5d1e5876684319b32c62/ascii_3.png)
 
 <blockquote><ui>4. Clique na aba <b>Cabeçalhos</b> e copie os dados do cookie.</ui>  
 
-![ascii 4](//images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/eab317339dfe8c29f82d9987e3f28980/ascii_4.png)    
+![ascii 4](https://images.ctfassets.net/alneenqid6w5/1CwUNkSO895RfPCTTaO29l/eab317339dfe8c29f82d9987e3f28980/ascii_4.png)    
 
 <blockquote><ui>5. Acesse um <a href="https://pages.cs.wisc.edu/~markm/ascii.html">validador online de caracteres ASCII</a> e insira a informação do cookie. Se um ou mais caracteres especiais forem identificados, os tipos e posições serão exibidas na parte inferior do validador de caracteres.</ui>     
 
-![ascii 5](//images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/917872a195c9cce233a183a4f44b4677/ascii_5.png)  
+![ascii 5](https://images.ctfassets.net/alneenqid6w5/2xwztAmvtrxpJQeusgwlpH/917872a195c9cce233a183a4f44b4677/ascii_5.png)  
 
 <blockquote><ui>6. Repita os passos 3 a 5 com todas as requisições com erro para identificar quais delas contêm cookies com caracteres especiais.</ui>      
 
diff --git a/docs/tutorials/pt/reports.md b/docs/tutorials/pt/reports.md
index 9052197f6..56b04004c 100644
--- a/docs/tutorials/pt/reports.md
+++ b/docs/tutorials/pt/reports.md
@@ -31,4 +31,4 @@ Os relatórios disponíveis, são:
 *   [Relatório de SMS e Email](https://help.vtex.com/pt/tutorial/relatorio-de-sms-e-email--7AZmTlojzg1hDmwhDOxCNO)
 *   [Relatório de Serviços](https://help.vtex.com/pt/tutorial/relatorio-de-servicos--7djPWfxtf9qb6hFTOgKDE8)
 
-![relatorio](//images.ctfassets.net/alneenqid6w5/7y2pg2YdeX5Y4vEjz2TYMl/44110199a50b25b75041edbf9deb79ec/relatorio.png)
+![relatorio](https://images.ctfassets.net/alneenqid6w5/7y2pg2YdeX5Y4vEjz2TYMl/44110199a50b25b75041edbf9deb79ec/relatorio.png)
diff --git a/docs/tutorials/pt/requering-authentication-on-store-pages.md b/docs/tutorials/pt/requering-authentication-on-store-pages.md
index 32a6cc160..d36cb2e74 100644
--- a/docs/tutorials/pt/requering-authentication-on-store-pages.md
+++ b/docs/tutorials/pt/requering-authentication-on-store-pages.md
@@ -19,15 +19,15 @@ Você pode exigir que, para determinadas páginas da loja, os usuários precisem
 
 Algumas páginas vêm com essa configuração por padrão. Por exemplo, as páginas `/Account` e `/Account/Orders`.
 
-![authenticationRequired](//images.contentful.com/alneenqid6w5/60cIIkiKDSEs2ocmqescgM/3f5a0c46d61c1002c22bc7b5469db7eb/authenticationRequired.png)
+![authenticationRequired](https://images.contentful.com/alneenqid6w5/60cIIkiKDSEs2ocmqescgM/3f5a0c46d61c1002c22bc7b5469db7eb/authenticationRequired.png)
 
 Mas você pode tanto retirar a exigência de autenticação para estas páginas como inseri-la em outras páginas.
 
 Para isso, siga os passos abaixo:
 1. Acesse o módulo __CMS__.
 2. Clique na pasta referente à página desejada.
-3. Clique no botão __Edit__.![editFolder](//images.contentful.com/alneenqid6w5/2DSRmQFQxeAYcoiWCAaU62/bc08bd32b394545d8af716338d55a0be/editFolder.png)
-4. Marque ou desmarque a flag __Authentication Required__.![authenticationRequiredFlag](//images.contentful.com/alneenqid6w5/3iK3iGguAUg84KuAsC4MYW/1dcdae221b886b4a4d1cdc4eb87af9a4/authenticationRequiredFlag.png)
+3. Clique no botão __Edit__.![editFolder](https://images.contentful.com/alneenqid6w5/2DSRmQFQxeAYcoiWCAaU62/bc08bd32b394545d8af716338d55a0be/editFolder.png)
+4. Marque ou desmarque a flag __Authentication Required__.![authenticationRequiredFlag](https://images.contentful.com/alneenqid6w5/3iK3iGguAUg84KuAsC4MYW/1dcdae221b886b4a4d1cdc4eb87af9a4/authenticationRequiredFlag.png)
 5. Clique em __Save Folder__.
 
 Note que sempre que a flag __Authentication Required__ estiver marcada para uma pasta, a URL desta página será montada com a rota `_secure`. Ex: `http://{AccountName}.vtexcommercestable.com.br/_secure/account/`
diff --git a/docs/tutorials/pt/requesting-the-ssl-certificate.md b/docs/tutorials/pt/requesting-the-ssl-certificate.md
index 06ebb6212..4b4daf702 100644
--- a/docs/tutorials/pt/requesting-the-ssl-certificate.md
+++ b/docs/tutorials/pt/requesting-the-ssl-certificate.md
@@ -17,6 +17,6 @@ subcategory: 2Za4fjGfxYOo6oqykukgyy
 
 O certificado SSL vai proteger a transferência de dados importantes de seus clientes em sua loja e é oferecido gratuitamente pela VTEX. O selo deverá ser inserido no rodapé da loja e a instalação do certificado garante que, em HTTPS, a navegação ocorra em segurança.
 
-<video class="wp-video-shortcode" id="video-2558-10" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4?_=10" />[//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4](//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4 "//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4")</video>
+<video class="wp-video-shortcode" id="video-2558-10" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4?_=10" />[//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4](https://assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4 "//assets.contentful.com/alneenqid6w5/17AAe0VyN426qiYmWMI6SG/1806e294d31bd22b55f778948b6086e7/SolicitandoSSL-1.mp4")</video>
 
 [Veja em mais detalhes como contratar o certificado de segurança (SSL)](/pt/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar/).
diff --git a/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
index 042aba573..95ce972fa 100644
--- a/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
+++ b/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
@@ -30,7 +30,7 @@ Durante a configuração inicial da VTEX, caso a sua loja utilize [integrações
 
 Uma vez configurada a integração inicial de produtos, preços e inventário, e desenvolvido o middleware, o fluxo de informações será conforme o diagrama a seguir.
 
-![back-office-pt](//images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/6bc291243b2b38f8a570d404d88e055e/back-office-pt.PNG)
+![back-office-pt](https://images.ctfassets.net/alneenqid6w5/6M5KnqChk7RT99b034UY3L/6bc291243b2b38f8a570d404d88e055e/back-office-pt.PNG)
 
 Durante a rotina da operação, as responsabilidades são divididas da seguinte forma:
 
@@ -214,6 +214,6 @@ Para entender qual suporte deve ser acionado caso haja algum problema na atualiz
 2. Clique no pedido desejado para acessar a [página de detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl).
 3. Na seção **Histórico do pedido**, clique em `Ver interações` (botão ilustrado a seguir), e verifique se há alguma mensagem de erro. 
 
-![ver-interacoes-pt](//images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/6d50ebab0fb9de03850bc219ea7fbce8/ver-interacoes-pt.png)
+![ver-interacoes-pt](https://images.ctfassets.net/alneenqid6w5/2A2368gEpzx8T1VnDXsQ2C/6d50ebab0fb9de03850bc219ea7fbce8/ver-interacoes-pt.png)
 
 Caso a mensagem de erro não seja autossuficiente, o lojista pode acionar nossos canais de comunicação, conforme a [Política de atendimento do suporte da VTEX](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9). Recomendamos incluir a evidência da tela de interações e o ID do pedido, para que o time de especialistas ajude a identificar a origem do problema.
diff --git a/docs/tutorials/pt/responsive-vs-mobile-version.md b/docs/tutorials/pt/responsive-vs-mobile-version.md
index 14b91bd03..5e9cfa5e9 100644
--- a/docs/tutorials/pt/responsive-vs-mobile-version.md
+++ b/docs/tutorials/pt/responsive-vs-mobile-version.md
@@ -23,7 +23,7 @@ Seja do computador, smartphone, tablet ou notebook, o design é o mesmo. O que a
 
 O design da versão mobile e toda a sua programação é feito pensando apenas no mobile, sendo uma segunda aplicação, ou seja, uma para navegadores comuns e outra para navegadores mobile. Ao acessar a loja, identifica-se o dispositivo e redireciona a programação específica.
 
-![Principais resoluões mobile utilizadas atualmente](//images.contentful.com/alneenqid6w5/4tOHOVzZO8w6a0mUAuqSk6/770a9f0ff450163bd3e30f32e8e56cd6/RESOLUTION.jpg)
+![Principais resoluões mobile utilizadas atualmente](https://images.contentful.com/alneenqid6w5/4tOHOVzZO8w6a0mUAuqSk6/770a9f0ff450163bd3e30f32e8e56cd6/RESOLUTION.jpg)
 
 Principais resoluções de tela utilizadas atualmente (pode-se haver variações conforme o dispositivo
 
@@ -56,7 +56,7 @@ Principais resoluções de tela utilizadas atualmente (pode-se haver variações
 
 #### Principais elementos visuais reconhecidos nos dispositivos móveis:
 
-![Principais elementos visuais reconhecidos nos dispositivos móveis](//images.contentful.com/alneenqid6w5/5837hcHdBussm8oMI42iWQ/c6f399a1ff3f438c3618d3678ec918ee/icon.jpg)
+![Principais elementos visuais reconhecidos nos dispositivos móveis](https://images.contentful.com/alneenqid6w5/5837hcHdBussm8oMI42iWQ/c6f399a1ff3f438c3618d3678ec918ee/icon.jpg)
 
 #### A qualidade é indiferente ao tamanho!
 
diff --git a/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md b/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md
index 6c20d9003..e0213e40e 100644
--- a/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md
+++ b/docs/tutorials/pt/restrict-public-access-to-master-data-fields.md
@@ -27,25 +27,25 @@ Dependendo dos dados armazenados, o acesso público sem autenticação pode repr
 2. No Master Data, clique em **Aplicações**.
 3. Clique na engrenagem <i class="fas fa-cog"></i> ao lado de **Profile System**:
 
-   ![1-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/8ef8b96790388f461fa7c987039c2d25/1-master-data-confidential-data-pt.png)
+   ![1-master-data-confidential-data-pt](https://images.ctfassets.net/alneenqid6w5/2Ulq3zVfRfAkmXYzC1fCCq/8ef8b96790388f461fa7c987039c2d25/1-master-data-confidential-data-pt.png)
 
 4. Em **Configurações**, clique em **Estrutura de dados**.
 
-   ![2-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/524173ebe8a58a71711ac518b571218b/2-master-data-confidential-data-pt.png)
+   ![2-master-data-confidential-data-pt](https://images.ctfassets.net/alneenqid6w5/3F2667ZvZymEE03zyoHSsh/524173ebe8a58a71711ac518b571218b/2-master-data-confidential-data-pt.png)
 5. Clique na aba **Entidades de dados**.
 6. Na linha da entidade de dados, clique no botão de edição <i class="fas fa-edit"></i>.
 
-   ![3-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/8a5d88237d95243515b0528ff1b7a4b0/3-master-data-confidential-data-pt.png)
+   ![3-master-data-confidential-data-pt](https://images.ctfassets.net/alneenqid6w5/4yZP09vrLVx5FtLUAW8Q1b/8a5d88237d95243515b0528ff1b7a4b0/3-master-data-confidential-data-pt.png)
 7. Na linha do campo que contém um dado confidencial, clique na engrenagem <i class="fas fa-cog"></i>.
 
-   ![4-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/7c1f6afa0c6d7cda830b03b1532d22ed/4-master-data-confidential-data-pt.png)
+   ![4-master-data-confidential-data-pt](https://images.ctfassets.net/alneenqid6w5/5FZRbvfibWYENZIeoGGvXk/7c1f6afa0c6d7cda830b03b1532d22ed/4-master-data-confidential-data-pt.png)
 8. Desmarque as opções a seguir:
 
    * **Permitir a leitura sem credencial**
    * **Permitir editar sem credencial**
    * **Permitir filtrar sem credencial**
 
-   ![5-master-data-confidential-data-pt](//images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/caf25f3c588303febe067d9a219dd9f2/5-master-data-confidential-data-pt.png)
+   ![5-master-data-confidential-data-pt](https://images.ctfassets.net/alneenqid6w5/1FTKHYceHs2H5HkDV6lwCv/caf25f3c588303febe067d9a219dd9f2/5-master-data-confidential-data-pt.png)
 
 9. Clique em `Salvar`.
 10. Na linha da entidade de dados alterada, clique no botão de publicação <i class="fas fa-save"></i> para que as configurações salvas sejam publicadas.
diff --git a/docs/tutorials/pt/roles.md b/docs/tutorials/pt/roles.md
index ecdaddd9a..23290533a 100644
--- a/docs/tutorials/pt/roles.md
+++ b/docs/tutorials/pt/roles.md
@@ -24,7 +24,7 @@ A partir da página de perfis de acesso, você pode realizar as seguintes açõe
 * [Editar um perfil de acesso](#editar-um-perfil-de-acesso)
 * [Excluir um perfil de acesso](#excluir-um-perfil-de-acesso)
 
-![roles-pt](//images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/943f5df380f3fb685bb369014b435454/roles-pt.png)
+![roles-pt](https://images.ctfassets.net/alneenqid6w5/hn5I8XMFI38UCoMxIIjjM/943f5df380f3fb685bb369014b435454/roles-pt.png)
 
 A página apresenta uma lista com todos os perfis de acesso cadastrados na conta e suas respectivas informações em uma tabela: 
 
diff --git a/docs/tutorials/pt/rounding-rules.md b/docs/tutorials/pt/rounding-rules.md
index bea8229fd..324f8a20d 100644
--- a/docs/tutorials/pt/rounding-rules.md
+++ b/docs/tutorials/pt/rounding-rules.md
@@ -60,16 +60,16 @@ Abaixo é possível ver exemplos dos fluxos de inclusão, edição e exclusão d
 
 *Fluxo de criação de uma regra*
 
-![config-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/6HPUHcVmPcDz90eXLbKrlV/16bd4ce06174eee79c58e998424f36dd/config-arrendodamento-PT.gif)
+![config-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/6HPUHcVmPcDz90eXLbKrlV/16bd4ce06174eee79c58e998424f36dd/config-arrendodamento-PT.gif)
 
 *Fluxo de alteração de uma regra*
 
-![editar-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/2DYnjck4KL2nGvoSIywViM/f5a35515cfbeb14b10f57fa0989c147f/editar-arrendodamento-PT.gif)
+![editar-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/2DYnjck4KL2nGvoSIywViM/f5a35515cfbeb14b10f57fa0989c147f/editar-arrendodamento-PT.gif)
 
 *Fluxo de exclusão de uma regra*
 
-![deletar-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/5T0Ti47Sv4Nndmg1IitZC5/742cccd2aefde6de5843a6b15d27b16c/deletar-arrendodamento-PT.gif)
+![deletar-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/5T0Ti47Sv4Nndmg1IitZC5/742cccd2aefde6de5843a6b15d27b16c/deletar-arrendodamento-PT.gif)
 
 *Simulação de preço para uma regra*
 
-![teste-arrendodamento-PT](//images.ctfassets.net/alneenqid6w5/21ONAWrW6xYEjI5C31yski/9f059b32409995f6be45f22856a62885/teste-arrendodamento-PT.gif)
+![teste-arrendodamento-PT](https://images.ctfassets.net/alneenqid6w5/21ONAWrW6xYEjI5C31yski/9f059b32409995f6be45f22856a62885/teste-arrendodamento-PT.gif)
diff --git a/docs/tutorials/pt/routing-monitoring.md b/docs/tutorials/pt/routing-monitoring.md
index 189f32cca..fa3eb9c08 100644
--- a/docs/tutorials/pt/routing-monitoring.md
+++ b/docs/tutorials/pt/routing-monitoring.md
@@ -79,4 +79,4 @@ Caso precise mudar o status, ao final da página [Detalhes da rota](#detalhes-da
 Para que esteja disponível uma Justificativa ela deve ser cadastrada previamente na aba de Configurações de Conta. Para saber mais confira <a href="https://help.vtex.com/pt/tutorial/justificativa-de-status-vtex-tracking--4shboc7h5XPUpA8TQzXPRG">Justificativa de status</a>.
 </div>
 
-![Monitoramento de Rota](//images.ctfassets.net/alneenqid6w5/3cHz27dvHjO7ObLDxJTIuc/01103e99a288ab15935a7b453487fd7c/Monitoramento_Rota.gif)
+![Monitoramento de Rota](https://images.ctfassets.net/alneenqid6w5/3cHz27dvHjO7ObLDxJTIuc/01103e99a288ab15935a7b453487fd7c/Monitoramento_Rota.gif)
diff --git a/docs/tutorials/pt/sales-app-sales-performance.md b/docs/tutorials/pt/sales-app-sales-performance.md
index 87f452191..c874b2a98 100644
--- a/docs/tutorials/pt/sales-app-sales-performance.md
+++ b/docs/tutorials/pt/sales-app-sales-performance.md
@@ -22,7 +22,7 @@ subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 1. No aplicativo do Sales App, acesse a página principal do aplicativo. 
 2. Clique no botão <i class="fas fa-bars"></i>.
 3. Clique em **Performance de vendas**. 
-![Métricas da Loja](//images.ctfassets.net/alneenqid6w5/4DLSNWjwX0G26UoKr4K9wg/03d35f5197f748a3f9f3ca2138039c3f/vendas_totais.png)
+![Métricas da Loja](https://images.ctfassets.net/alneenqid6w5/4DLSNWjwX0G26UoKr4K9wg/03d35f5197f748a3f9f3ca2138039c3f/vendas_totais.png)
 Nessa página, você terá acesso às seguintes métricas:
 
 - **Valor total das vendas:** exibirá o valor total das vendas da loja referentes aos períodos selecionados no campo **Exibir** (azul) e do campo **Comparado a** (cinza), indicando a porcentagem de aumento ou decréscimo de venda nesta comparação.
@@ -39,7 +39,7 @@ Para acessar métricas específicas de um vendedor, siga os passos abaixo:
 2. Selecione o perfil do vendedor e insira a senha de acesso.
 3. Clique em `Confirmar`.
 
-![Vendas de Bruna - VTEX Sales App](//images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/bbe1ec3e5cf0e840f01acd279301e81c/Vendas_de_bruna_-.png)
+![Vendas de Bruna - VTEX Sales App](https://images.ctfassets.net/alneenqid6w5/78nJXcuThGbc7cGrOb7CqV/bbe1ec3e5cf0e840f01acd279301e81c/Vendas_de_bruna_-.png)
 
 Nessa página, você terá acesso às seguintes métricas referentes àquele vendedor:
 
diff --git a/docs/tutorials/pt/sales-associate-code-field-at-checkout.md b/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
index ce14d9613..cd89bf90e 100644
--- a/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
+++ b/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
@@ -61,7 +61,7 @@ Após a criação da entidade *codigovendedor*, é necessário associá-la a uma
 
 <blockquote><ui>3. Em <b>Quais as condições para a promoção ser válida?</b>, clique na opção <b>utm_campaign</b> e digite no campo <i>codigovendedor</i>.</ui>
 
-![utm campaign codigovendedor](//images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/1896457a0ea45bc20292377e8c963077/UTM_Campaign_codigovendedor.PNG)
+![utm campaign codigovendedor](https://images.ctfassets.net/alneenqid6w5/6jroNJYCvzunmfosErnmZF/1896457a0ea45bc20292377e8c963077/UTM_Campaign_codigovendedor.PNG)
 
 <blockquote><ui>4. Em <b>Restrições e limitações de uso</b>, adicione as demais restrições disponíveis, caso desejar. Selecione a opção <b>Permitir acumular promoções</b>.</ui>
 
@@ -93,4 +93,4 @@ Adicionalmente, os seguintes passos devem ser realizados:
 
 Após executar todas as etapas acima descritas, o campo **Código do Vendedor** estará disponível na tela do Checkout.
 
-![Código do vendedor](//images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/c44bb28d5954f7f015da9feb751dc8f4/Checkout_UI_-_PT_2.png)
+![Código do vendedor](https://images.ctfassets.net/alneenqid6w5/kWi3gE5Q9gyHP2pa8XFpv/c44bb28d5954f7f015da9feb751dc8f4/Checkout_UI_-_PT_2.png)
diff --git a/docs/tutorials/pt/sales-associates-instore-beta.md b/docs/tutorials/pt/sales-associates-instore-beta.md
index d02d40ea2..bd3bcd2f8 100644
--- a/docs/tutorials/pt/sales-associates-instore-beta.md
+++ b/docs/tutorials/pt/sales-associates-instore-beta.md
@@ -29,7 +29,7 @@ Esta página permite que você gerencia seus vendedores a partir das seguintes a
 * [Editar](#editar-vendedor)
 * [Excluir](#excluir-vendedor)
 
-![vendedores-pt](//images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/247cb80ead8132c0b82a5787328279dc/image.png)
+![vendedores-pt](https://images.ctfassets.net/alneenqid6w5/1PDeYBlqDILaEOFGOE7H8x/247cb80ead8132c0b82a5787328279dc/image.png)
 
 A página apresenta as seguintes informações: 
 
@@ -52,7 +52,7 @@ Você pode cadastrar um vendedor seguindo os passos abaixo:
 
 Após o cadastro, o vendedor irá receber um email confirmando o cadastro e redirecionando para a opção de login do vendedor ao aplicativo inStore.
 
-![email-vendedor-pt](//images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
+![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
 <div class ="alert alert-warning">
 <p>Os vendedores cadastrados no inStore não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin seu cadastro será excluído.</p> 
diff --git a/docs/tutorials/pt/sales-funnel-suiteshare.md b/docs/tutorials/pt/sales-funnel-suiteshare.md
index 56ecc5ffe..79453bf80 100644
--- a/docs/tutorials/pt/sales-funnel-suiteshare.md
+++ b/docs/tutorials/pt/sales-funnel-suiteshare.md
@@ -25,22 +25,22 @@ Nessa etapa, será possível localizar todas as informações necessárias para
 
 Nessa página você irá encontrar todas as informações necessárias para realizar a integração.
 
-![Funil de vendas_1](//images.ctfassets.net/alneenqid6w5/Fk4RseF2XChIrFyoLy4k4/872ac7d142b8f47309be32cd84ea14ff/Funil_de_vendas_1.png)
+![Funil de vendas_1](https://images.ctfassets.net/alneenqid6w5/Fk4RseF2XChIrFyoLy4k4/872ac7d142b8f47309be32cd84ea14ff/Funil_de_vendas_1.png)
 
 Para realizar a integração com a Suiteshare, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **Funil de Vendas**.
 
-   ![Funil de vendas_2](//images.ctfassets.net/alneenqid6w5/7kizQsL75XA6W5a0Lz06YR/c2c6238812f816f1b3cd649fdf6288ae/Funil_de_vendas_2.png)
+   ![Funil de vendas_2](https://images.ctfassets.net/alneenqid6w5/7kizQsL75XA6W5a0Lz06YR/c2c6238812f816f1b3cd649fdf6288ae/Funil_de_vendas_2.png)
 
 2. Acesse **Configurações > Integrações > Funil de Vendas > Integrar**.
 
-   ![Funil de vendas_3](//images.ctfassets.net/alneenqid6w5/6pq85VMCe5UDq6XucdVi7h/4e69b243a4d8e5316a9ba95a2e67eb75/Funil_de_vendas_3.png)
+   ![Funil de vendas_3](https://images.ctfassets.net/alneenqid6w5/6pq85VMCe5UDq6XucdVi7h/4e69b243a4d8e5316a9ba95a2e67eb75/Funil_de_vendas_3.png)
 
 Clique em **Conectar**.
 
 Pronto! Esse deve ser o resultado da integração dentro do Funil de Vendas CRM:
 
-![Funil de vendas_4](//images.ctfassets.net/alneenqid6w5/46bMGyUdRbzTwK6OcUss57/42741b5b2196679f2adac2e5131a61e3/Funil_de_vendas_4.png)
+![Funil de vendas_4](https://images.ctfassets.net/alneenqid6w5/46bMGyUdRbzTwK6OcUss57/42741b5b2196679f2adac2e5131a61e3/Funil_de_vendas_4.png)
 
 Agora é só aproveitar a integração!
diff --git a/docs/tutorials/pt/sales-performance.md b/docs/tutorials/pt/sales-performance.md
index 9243f63ff..28f5e15ec 100644
--- a/docs/tutorials/pt/sales-performance.md
+++ b/docs/tutorials/pt/sales-performance.md
@@ -26,7 +26,7 @@ Para acessar a página, em seu Admin VTEX vá para __Dashboards > Performance de
 
 É possível customizar a visualização dos dados do gráfico e da lista filtrando por período, dimensões e métricas.
 
-![Sales Perf Dash PT](//images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
+![Sales Perf Dash PT](https://images.ctfassets.net/alneenqid6w5/1nTkH8KfhrLPOBuxFhcZvC/97ef8b2e3525cc9a565f1d55783730b3/Sales_Perf_Dash_PT.gif)
 
 ## Dados 
 Os dados da página são provenientes do [sistema de Gerenciamento de Pedidos](https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa) da VTEX. A Performance de Vendas é uma solução analítica, que usa heurísticas e fórmulas criadas a partir de nossa experiência levando nossos clientes de ecommerce para o próximo nível para calcular suas métricas. A página não deve ser utilizada como substituto para os dados do OMS, mas como ferramenta de análise e insights de negócio.
@@ -154,7 +154,7 @@ Além de aplicar filtros, também é possível realizar as ações abaixo:
 
 ## Menu Exibições
 
-![Sales perf update PT](//images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
+![Sales perf update PT](https://images.ctfassets.net/alneenqid6w5/5mHOltfUnUpV1DtHXrT8xD/3abd7dcbd11988d998dd95659c1088de/Sales_perf_update_PT.gif)
 
 A Performance de Vendas permite customizar o dashboard aplicando diferentes filtros e selecionando as métricas que aparecerão no gráfico e na lista. Para facilitar sua exploração de dados no dia a dia, criamos as Exibições, que gravam os filtros e métricas aplicados na página para sua visualização direta. É possível salvar, editar e compartilhar visualizações distintas do dashboard. A página já vem com as seguintes Exibições configuradas por default:
 
diff --git a/docs/tutorials/pt/scheduling-features-for-special-events.md b/docs/tutorials/pt/scheduling-features-for-special-events.md
index 30612d420..a92fdc752 100644
--- a/docs/tutorials/pt/scheduling-features-for-special-events.md
+++ b/docs/tutorials/pt/scheduling-features-for-special-events.md
@@ -70,7 +70,7 @@ Para agendar um conteúdo da sua loja, siga os passos abaixo:
 3. Use o campo URL no canto superior para navegar até a página que exibe o bloco cujo conteúdo será sobrescrito.
 4. Selecione o bloco para o qual deseja criar um novo conteúdo. Você pode selecioná-lo usando a lista no canto direito ou através da interface:
 
-![seta-interface](//images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
+![seta-interface](https://images.ctfassets.net/alneenqid6w5/6IhPT84ZmkV83ooydYNLLc/89b848f0f5678a4ce69c9f095e3abcbc/seta-interface.png)
 
 5. Clique em `Configurações` no canto superior direito.
 6. Clique no botão `Novo conteúdo`.
diff --git a/docs/tutorials/pt/scheduling-prices.md b/docs/tutorials/pt/scheduling-prices.md
index 2a8a6d125..b71305793 100644
--- a/docs/tutorials/pt/scheduling-prices.md
+++ b/docs/tutorials/pt/scheduling-prices.md
@@ -58,7 +58,7 @@ Você também pode realizar o agendamento de preços por importação de planilh
 
 1. No Admin VTEX, acesse *Preços > Lista de preços*, ou digite *Lista de preços* na barra de busca no topo da página.
 2. Clique no ícone 📥 para exportar a planilha que será preenchida.
-![Agendar preço fixo - PT](//images.contentful.com/alneenqid6w5/49YjTAWw59Mglg2DMUT65w/08b89d10517f3bbddc78569650ebc09d/Screenshot_2021-08-05_at_17-11-39_-EDU-4229-_Agendar_pre__o_fixo.png)
+![Agendar preço fixo - PT](https://images.contentful.com/alneenqid6w5/49YjTAWw59Mglg2DMUT65w/08b89d10517f3bbddc78569650ebc09d/Screenshot_2021-08-05_at_17-11-39_-EDU-4229-_Agendar_pre__o_fixo.png)
 3. Selecione apenas a opção **Tabela de preços fixos**.
 4. Clique em `Exportar 1 tabela` para finalizar.
 
@@ -72,7 +72,7 @@ A planilha será enviada para seu email e pode ser baixada por lá. Após baixar
 - **Date From:** data e hora de início, no formato [RFC3339](https://www.ietf.org/rfc/rfc3339.txt), do agendamento do preço fixo. Será a partir dessa data e hora que o preço fixo será válido.
 - **Date To:** data e hora de fim, no formato [RFC3339](https://www.ietf.org/rfc/rfc3339.txt), do agendamento do preço fixo. Será a partir dessa data e hora que o preço fixo não será mais válido.
 
-![Agendar preço fixo planilha PT](//images.contentful.com/alneenqid6w5/7g3wkpsDPcdjYHT2xSqGhS/1895766def1ed02971f47f003d115491/Screenshot_2021-08-05_at_17-17-11_-EDU-4229-_Agendar_pre__o_fixo.png)
+![Agendar preço fixo planilha PT](https://images.contentful.com/alneenqid6w5/7g3wkpsDPcdjYHT2xSqGhS/1895766def1ed02971f47f003d115491/Screenshot_2021-08-05_at_17-17-11_-EDU-4229-_Agendar_pre__o_fixo.png)
 
 Depois de finalizar o preenchimento da planilha é necessário importá-la para a loja. Siga os passos abaixo.
 
diff --git a/docs/tutorials/pt/search-configuration.md b/docs/tutorials/pt/search-configuration.md
index 046915015..beee85ff9 100644
--- a/docs/tutorials/pt/search-configuration.md
+++ b/docs/tutorials/pt/search-configuration.md
@@ -37,7 +37,7 @@ As configurações gerais apresentam as opções a seguir, relacionadas a [espec
 
 As configurações de filtros apresentam ajustes relacionados aos filtros exibidos para os clientes da sua loja durante a busca:
 
-![Configurações de filtros](//images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
+![Configurações de filtros](https://images.ctfassets.net/alneenqid6w5/mSm3lqR5H5pTn1AVrhYk8/d30c6a13e65de39d0273a014abf55781/configuracoes_de_filtro_pt.png)
 
 * **Ordenação dos filtros:** ordem em que os filtros serão exibidos na loja. Caso não tenha nenhum filtro selecionado na área, a ordem padrão é alfabética.
 
diff --git a/docs/tutorials/pt/search-control-fulltextsearchbox.md b/docs/tutorials/pt/search-control-fulltextsearchbox.md
index 5451799c5..630f1bacd 100644
--- a/docs/tutorials/pt/search-control-fulltextsearchbox.md
+++ b/docs/tutorials/pt/search-control-fulltextsearchbox.md
@@ -21,7 +21,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 O controle `<vtex.cmc:fullTextSearchBox />` é responsável por gerar a caixa de busca. Além do campo de pesquisa o controle renderiza um combo para restringir uma busca em um departamento. Abaixo temos um exemplo do controle sem nenhuma aplicação de css:
 
-![Controle busca cru](//images.contentful.com/alneenqid6w5/4tvtNt1u0Mw8sgmwyAaOuW/2375499b868cfe4c24b3425fa0f33a8c/controle-busca-cru.png)
+![Controle busca cru](https://images.contentful.com/alneenqid6w5/4tvtNt1u0Mw8sgmwyAaOuW/2375499b868cfe4c24b3425fa0f33a8c/controle-busca-cru.png)
 
 A busca é uma funcionalidade que deve estar disponível em todas as páginas de uma loja e por isso é sugerido que o controle seja inserido dentro de um [subtemplate](http://help.vtex.com/pt/tutorial/subtemplates). Normalmente o controle de busca é usado dentro do subtemplate do header da loja.
 
@@ -75,9 +75,9 @@ A funcionalidade de autocomplete já está prevista neste controle e é necessá
 
 Alguns exemplos de como pode ser customizado o controle:
 
-![](//images.contentful.com/alneenqid6w5/BMzmz8NA0o4SQqUO8ow4Y/5c6d179a8fca8a3efaf981c05203c061/controle-busca-autocomplete-560x318.png)
+![](https://images.contentful.com/alneenqid6w5/BMzmz8NA0o4SQqUO8ow4Y/5c6d179a8fca8a3efaf981c05203c061/controle-busca-autocomplete-560x318.png)
 
-![](//images.contentful.com/alneenqid6w5/5TiDgTywScWuAcC24wmeIu/58acad8f8151f8803251679453627968/controle-busca-exemplo-560x43.png)
+![](https://images.contentful.com/alneenqid6w5/5TiDgTywScWuAcC24wmeIu/58acad8f8151f8803251679453627968/controle-busca-exemplo-560x43.png)
 
-![](//images.contentful.com/alneenqid6w5/2X2lkCGHdSIaok08yYKCYO/6bef8f3e0c0b11313479226c0174e093/controle-busca-exemplo1.png)
+![](https://images.contentful.com/alneenqid6w5/2X2lkCGHdSIaok08yYKCYO/6bef8f3e0c0b11313479226c0174e093/controle-busca-exemplo1.png)
 
diff --git a/docs/tutorials/pt/search-navigator-control.md b/docs/tutorials/pt/search-navigator-control.md
index f2067e984..c7370d984 100644
--- a/docs/tutorials/pt/search-navigator-control.md
+++ b/docs/tutorials/pt/search-navigator-control.md
@@ -44,7 +44,7 @@ Para que uma coleção seja exibida no menu pelo controle Search Navigator, ela
 
 Essa flag fica nas configurações da própria coleção, dentro do CMS.
 
-![searchNavigator2](//images.contentful.com/alneenqid6w5/30xKS65fWMuoiQO4ac2EKM/921be3bc19a8cdff48dade515c354908/searchNavigator2.jpg)
+![searchNavigator2](https://images.contentful.com/alneenqid6w5/30xKS65fWMuoiQO4ac2EKM/921be3bc19a8cdff48dade515c354908/searchNavigator2.jpg)
 
 ## Categorias
 
@@ -52,7 +52,7 @@ Para uma categoria ser exibida por ação desse controle, ela deve estar com a f
 
 Essa flag fica na tela de cadastro da categoria.
 
-![searchNavigator1](//images.contentful.com/alneenqid6w5/Q04sSdSPeK4U6Cu48MKkK/198759d6dcdb5d740f0e7b380d8f38cc/searchNavigator1.jpg)
+![searchNavigator1](https://images.contentful.com/alneenqid6w5/Q04sSdSPeK4U6Cu48MKkK/198759d6dcdb5d740f0e7b380d8f38cc/searchNavigator1.jpg)
 
 <div class="alert alert-info">
   <strong>Importante</strong>: O controle <code>&lt;vtex.cmc:searchNavigator/&gt;</code> exibe, por padrão, apenas a categoria raiz (primeiro nível) e a subcategoria mais específica (último nível) dentro do contexto atual. Desdobramentos intermediários da árvore de categorias são omitidos.
@@ -85,7 +85,7 @@ Para que um campo de produto ou um campo de SKU seja exibido no menu pelo contro
 
 Ambas se encontram na tela de cadastro do campo.
 
-![searchNavigator3](//images.contentful.com/alneenqid6w5/5ZG3cioleoCUqSgiuGiG4m/cb943696e7952da38d36746f20941569/searchNavigator3.jpg)
+![searchNavigator3](https://images.contentful.com/alneenqid6w5/5ZG3cioleoCUqSgiuGiG4m/cb943696e7952da38d36746f20941569/searchNavigator3.jpg)
 
 ## Faixas de preço
 
diff --git a/docs/tutorials/pt/search-parameters.md b/docs/tutorials/pt/search-parameters.md
index 8010b707d..0ebd0ef5b 100644
--- a/docs/tutorials/pt/search-parameters.md
+++ b/docs/tutorials/pt/search-parameters.md
@@ -21,7 +21,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Ao realizar buscas na VTEX, existem algumas possibilidades de URLs. Temos as URLs de Departamentos e Categorias, que são formadas da seguinte maneira:
 
-![](//images.contentful.com/alneenqid6w5/1MhPmB1yxKS426UCsASUsY/eeaf45262ccde7b0a50ee6ef6b787afb/arvore_categoria.png)
+![](https://images.contentful.com/alneenqid6w5/1MhPmB1yxKS426UCsASUsY/eeaf45262ccde7b0a50ee6ef6b787afb/arvore_categoria.png)
 
 Na árvore de categorias acima, os links ficariam da seguintes forma:
 
@@ -33,7 +33,7 @@ Na árvore de categorias acima, os links ficariam da seguintes forma:
 
 Ao utilizar o campo de busca, a url sempre será formada pelo termo buscado:
 
-![](//images.contentful.com/alneenqid6w5/tJYda31CZUUOCii0EcwmE/89481a9321a61fb50fd5463217d6760d/campo_busca.png)
+![](https://images.contentful.com/alneenqid6w5/tJYda31CZUUOCii0EcwmE/89481a9321a61fb50fd5463217d6760d/campo_busca.png)
 
 - www.loja.com.br/cama
 
@@ -49,7 +49,7 @@ Onde:
 
 **C:\[IdDepartamento/IdCategoria/IdSubcategoria\]**: Retorna produtos de uma determinada subcategoria, de acordo com os IDs informados do departamento, categoria e subcategoria. Este código é apresentado ao lado dos nomes das categorias em **Cadastro de Produtos -> Categoria**:
 
-![](//images.contentful.com/alneenqid6w5/44i8Rue6hiMmMs64wiks86/8f31981e162596d825190865cefd121e/id_categoria1.png)
+![](https://images.contentful.com/alneenqid6w5/44i8Rue6hiMmMs64wiks86/8f31981e162596d825190865cefd121e/id_categoria1.png)
 
 >Observação: 
 
@@ -57,7 +57,7 @@ OBS: O ID da categoria também pode ser encontrado em sua página de edição, a
 
 **B:\[IdMarca\]:** Retorna produtos de uma determinada marca, de acordo com o ID informado. Este código é apresentado ao final da URL, na página de alteração de uma marca, em **Cadastro de Produtos -> Marca**:
 
-![](//images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
+![](https://images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
 
 <div class = "alert alert-warning">
   <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
@@ -65,11 +65,11 @@ OBS: O ID da categoria também pode ser encontrado em sua página de edição, a
 
 **H:\[IdColeção\]**: Retorna produtos de uma determinada coleção, de acordo com o ID informado. Este código é informado na edição da coleção, em **Configurações &gt; Portal &gt; Pasta Portal &gt; Subpasta Coleções:**
 
-![](//images.contentful.com/alneenqid6w5/2vqAbADq0cUQO224YoOQAQ/7eef524621cbf80d9c37b37c9cc4099e/id_colecao.png)
+![](https://images.contentful.com/alneenqid6w5/2vqAbADq0cUQO224YoOQAQ/7eef524621cbf80d9c37b37c9cc4099e/id_colecao.png)
 
 **spec\_fct\_\[IdCampoProduto/Sku\]:\[ValorBuscado\]:** Retorna produtos cujo valor do campo produto/sku com o ID indicado seja igual ao valor informado. Este código pode ser obtido na página de alteração de um campo produto/sku, ao final da url:
 
-![](//images.contentful.com/alneenqid6w5/7noRXDnenuSU4ugc8mmoSg/7a85e4ab97b87c00d4306c57c2462ecc/id_campo-560x386.png)
+![](https://images.contentful.com/alneenqid6w5/7noRXDnenuSU4ugc8mmoSg/7a85e4ab97b87c00d4306c57c2462ecc/id_campo-560x386.png)
 
 Um exemplo de utilização deste campo seria:
 
diff --git a/docs/tutorials/pt/searching-for-old-orders.md b/docs/tutorials/pt/searching-for-old-orders.md
index 2e986340c..952c1b381 100644
--- a/docs/tutorials/pt/searching-for-old-orders.md
+++ b/docs/tutorials/pt/searching-for-old-orders.md
@@ -19,7 +19,7 @@ Para buscar seus pedidos antigos, siga os passos abaixo:
 
 1. No menu lateral do admin, clique em __Gerenciamento de Pedidos__
 2. Clique em __Todos os pedidos__
-3. Clique no botão de filtro ![filter](//images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
+3. Clique no botão de filtro ![filter](https://images.ctfassets.net/alneenqid6w5/1TVmDkKRDOe88o8oqqYMqu/e20881562b722c81f062efe4f2015101/filter.png)
 4. Escolha um filtro *por período*: __Data de faturamento__, __Data do pedido__, __Data de autorização__ ou **Data de entrega**
 5. No filtro escolhido, clique no __ícone de calendário__, ao lado do texto __Todas as datas__
 6. Escolha uma data/hora inicial e uma data/hora final
diff --git a/docs/tutorials/pt/searching-for-transactions-on-payments.md b/docs/tutorials/pt/searching-for-transactions-on-payments.md
index 07a0a42dc..6a6589a04 100644
--- a/docs/tutorials/pt/searching-for-transactions-on-payments.md
+++ b/docs/tutorials/pt/searching-for-transactions-on-payments.md
@@ -35,13 +35,13 @@ Para voltar à listagem original das transações, basta apagar o valor anterior
 
 Ao clicar em um pedido no Gerenciamento de Pedidos, você vai para a página que traz um resumo sobre ele. As principais informações estão lá, mas você pode ver ainda mais detalhes se clicar no link _Detalhes da transação_:
 
-![Link transação OMS (PT)](//images.ctfassets.net/alneenqid6w5/4HbLRjdyNyusgoSYAUmIee/c26af370c7be5288ab100d87a30d34ee/Link_transa____o_OMS__PT_.png)
+![Link transação OMS (PT)](https://images.ctfassets.net/alneenqid6w5/4HbLRjdyNyusgoSYAUmIee/c26af370c7be5288ab100d87a30d34ee/Link_transa____o_OMS__PT_.png)
 
 ## TID do Pagamento e ID do Pagamento
 
 A busca utilizando esses códigos necessariamente precisa conter todos os dígitos, ou sua busca retornará vazia. Veja abaixo como encontrá-lo:
 
-![Códigos PT](//images.ctfassets.net/alneenqid6w5/6cKptwp1XqOYs6umGEeW4m/44436d8afbf8055d10aeddd53f83f3ca/C__digos_PT.png)
+![Códigos PT](https://images.ctfassets.net/alneenqid6w5/6cKptwp1XqOYs6umGEeW4m/44436d8afbf8055d10aeddd53f83f3ca/C__digos_PT.png)
 
 Estes valores, dentro do detalhe da transação representarão a comunicação junto ao respectivo conector. Nos [eventos da transação](/pt/tutorial/como-visualizar-detalhes-do-pedido) será possível validar cada contato feito.
 
diff --git a/docs/tutorials/pt/security-monitor.md b/docs/tutorials/pt/security-monitor.md
index 53bc0c8a6..9a25fde79 100644
--- a/docs/tutorials/pt/security-monitor.md
+++ b/docs/tutorials/pt/security-monitor.md
@@ -26,7 +26,7 @@ Para acessar o dashboard, siga os passos abaixo:
 1. No Admin VTEX, acesse **Dashboards**, ou digite **Dashboards** na barra de busca.
 2. Em **Security Monitor**, clique em **Security Monitor Dashboard**.
 
-![1-security-monitor-pt](//images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/b0355765dafddea697f6cd29739be2fa/1-security-monitor-pt.png)
+![1-security-monitor-pt](https://images.ctfassets.net/alneenqid6w5/k2BpYU2kF3p3grDdfy4aB/b0355765dafddea697f6cd29739be2fa/1-security-monitor-pt.png)
 
 O Security Monitor apresenta as descobertas em três abas, divididas por status:
 
@@ -48,7 +48,7 @@ A aba **Abertas** apresenta as ameaças identificadas pelo Security Monitor que
 
 A barra superior indica o total de descobertas e a quantidade de ameaças por nível de severidade (alta, média ou baixa).
 
-![2-findings-pt](//images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/1d9ec105165551da7e470f3be5aa30ec/2-findings-pt.png)
+![2-findings-pt](https://images.ctfassets.net/alneenqid6w5/4wpzGuNHIyqAaRGuv5Dt8E/1d9ec105165551da7e470f3be5aa30ec/2-findings-pt.png)
 
 A aba apresenta a listagem completa de descobertas abertas em uma tabela, da mais recente para a mais antiga: 
 
@@ -79,7 +79,7 @@ Para mover uma descoberta para a aba **Silenciadas**, ou seja, removê-la tempor
 3. Escolha o período de tempo em dias para manter essa descoberta na aba **Silenciadas**. As opções disponíveis são: **7**, **90** ou **120** dias.
 4. Clique em `Silenciar`.
 
-![3-snooze-finding-pt](//images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/8a2ba4dbd793fcfde04b219947bba6f4/3-snooze-finding-pt.png)
+![3-snooze-finding-pt](https://images.ctfassets.net/alneenqid6w5/1neaA5XmCxK4EB3HAVxcud/8a2ba4dbd793fcfde04b219947bba6f4/3-snooze-finding-pt.png)
 
 ## Silenciadas
 
@@ -108,7 +108,7 @@ Na barra de busca, digite o email de usuário ou o nome da chave de aplicação
 
 Ao clicar em <i class="fas fa-chevron-down"></i> `Tipo`, você pode escolher um dos tipos de descoberta para filtrar os resultados exibidos na listagem. Clique em `Aplicar` para confirmar o filtro escolhido e a listagem será atualizada.
 
-![4-filter-findings-pt](//images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/afdf81607e3076ac05f71515b02e742a/4-filter-findings-pt.png)
+![4-filter-findings-pt](https://images.ctfassets.net/alneenqid6w5/1qJnJBy5YHJzQKynw783W7/afdf81607e3076ac05f71515b02e742a/4-filter-findings-pt.png)
 
 ## Editar configurações de notificações
 
@@ -121,7 +121,7 @@ Para editar os usuários administrativos que vão receber notificações em caso
 
 3. Clique em `Salvar`.
 
-![5-edit-notifications-pt](//images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/db1c1b11d46b98b05ab9b9091db65fa5/5-edit-notifications-pt__1_.png)
+![5-edit-notifications-pt](https://images.ctfassets.net/alneenqid6w5/1CmMhWokQgzxRAqk1Jvqn4/db1c1b11d46b98b05ab9b9091db65fa5/5-edit-notifications-pt__1_.png)
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md b/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md
index addfd792b..44dedbce4 100644
--- a/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md
+++ b/docs/tutorials/pt/selecting-stock-for-orders-mercado-envios-full.md
@@ -32,4 +32,4 @@ Com o estoque já cadastrado, siga os passos a seguir:
 7. Insira o ID do estoque selecionado no campo **Armazém Mercado Full**.
 8. Clique em **Salvar Configuração**.
 
-![Início (3)](//images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
+![Início (3)](https://images.ctfassets.net/alneenqid6w5/4iKrvuMuXZBzVzrZU7hWev/3f1bcba69b69cce6b56ff2afac670c6d/In__cio__3_.gif)
diff --git a/docs/tutorials/pt/seletivo.md b/docs/tutorials/pt/seletivo.md
index 69b9b98be..da798088f 100644
--- a/docs/tutorials/pt/seletivo.md
+++ b/docs/tutorials/pt/seletivo.md
@@ -19,41 +19,41 @@ No modo Seletivo, cada cliente que clicar no link será direcionado para uma tel
 
 Para criar um atendimento seletivo, acesse: _**Organizar > Seletivo**_ 
 
-![Seletivo 1](//images.ctfassets.net/alneenqid6w5/5aqMlFa9eCrKjp4Rc6VEZF/fbb0948a7381804f786f3dd2dc501af4/Screenshot_2022-08-29_at_14-27-26_Seletivo.png)
+![Seletivo 1](https://images.ctfassets.net/alneenqid6w5/5aqMlFa9eCrKjp4Rc6VEZF/fbb0948a7381804f786f3dd2dc501af4/Screenshot_2022-08-29_at_14-27-26_Seletivo.png)
 
 **IMPORTANTE**:  Antes de começar, você já deverá ter criado um link para cada número de WhatsApp que deseja adicionar na central. Se ainda não fez isso, é só [acessar esse link.](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB)
 
 Clique em _**“Novo”.**_
 
-![Seletivo 2](//images.ctfassets.net/alneenqid6w5/5gwGt7VFr7HoZRu4z4P3Fm/1db890b971e8dca053e7933f5f2670ba/Screenshot_2022-08-29_at_14-27-30_Seletivo.png)
+![Seletivo 2](https://images.ctfassets.net/alneenqid6w5/5gwGt7VFr7HoZRu4z4P3Fm/1db890b971e8dca053e7933f5f2670ba/Screenshot_2022-08-29_at_14-27-30_Seletivo.png)
 
 Defina o link principal. 
 
 Em **Link Âncora**, como o próprio nome já diz, você irá selecionar o link principal da central. Esse é o link que você irá divulgar, será o link responsável por fazer a ligação com os demais atendentes.
 
-![Seletivo 3](//images.ctfassets.net/alneenqid6w5/66tVW8yRNV93ovPLUdmDx/de491f10c1bf46f88283a7a88413d245/Screenshot_2022-08-29_at_14-27-34_Seletivo.png)
+![Seletivo 3](https://images.ctfassets.net/alneenqid6w5/66tVW8yRNV93ovPLUdmDx/de491f10c1bf46f88283a7a88413d245/Screenshot_2022-08-29_at_14-27-34_Seletivo.png)
 
 Clique em **“Avançar**”.
 
 Em Links de **Seleção**,escolha quem serão os vendedores ou setores que irão participar da central. Clique em Adicionar , personalize as informações dos atendentes (título, descrição e foto) e selecione o link para cada participante da central.
 
-![Seletivo 4](//images.ctfassets.net/alneenqid6w5/6CGgMpW1raNaPRl25knaQW/b191e79a7485244b7c045a3fd9828e05/Screenshot_2022-08-29_at_14-27-39_Seletivo.png)
+![Seletivo 4](https://images.ctfassets.net/alneenqid6w5/6CGgMpW1raNaPRl25knaQW/b191e79a7485244b7c045a3fd9828e05/Screenshot_2022-08-29_at_14-27-39_Seletivo.png)
 
 Defina se os links ficarão em _**“Ordenação randômica”**_ ou seja, a sequência de links sempre irá mudar para cada acesso.
 
-![Seletivo 5](//images.ctfassets.net/alneenqid6w5/1Az1uDyBgUIletuPjq7Zum/8065b8091e778b7affe31edda074b789/Screenshot_2022-08-29_at_14-27-43_Seletivo.png)
+![Seletivo 5](https://images.ctfassets.net/alneenqid6w5/1Az1uDyBgUIletuPjq7Zum/8065b8091e778b7affe31edda074b789/Screenshot_2022-08-29_at_14-27-43_Seletivo.png)
 
 Clique em "_**Avançar"**_. 
 
 Defina o texto que irá aparecer na sua tela de seleção.
 
-![Seletivo 6](//images.ctfassets.net/alneenqid6w5/3nQN1TbH980LDrPEIHjpVq/30f6e9e19c82f6d3f8eb2701ee4fcc64/Screenshot_2022-08-29_at_14-27-47_Seletivo.png)
+![Seletivo 6](https://images.ctfassets.net/alneenqid6w5/3nQN1TbH980LDrPEIHjpVq/30f6e9e19c82f6d3f8eb2701ee4fcc64/Screenshot_2022-08-29_at_14-27-47_Seletivo.png)
 
 Clique no botão “_**Finalizar**_” para salvar seu atendimento seletivo. 
 
 Configure a aparência, você pode clicar no botão “_**Clique aqui**_” ou acessar  **Configurações > Minha conta > Aparência**
 
-![Seletivo 7](//images.ctfassets.net/alneenqid6w5/575cQ08f4RMKj8YymWqGhY/1cf33469f22a684d3116d039f881ba4d/Screenshot_2022-08-29_at_14-28-01_Seletivo.png)
+![Seletivo 7](https://images.ctfassets.net/alneenqid6w5/575cQ08f4RMKj8YymWqGhY/1cf33469f22a684d3116d039f881ba4d/Screenshot_2022-08-29_at_14-28-01_Seletivo.png)
 
 **Atenção:** Se você ir para a aparência e não salvar seu seletivo, você terá que refazer as opções. 
 
diff --git a/docs/tutorials/pt/seller-management.md b/docs/tutorials/pt/seller-management.md
index b07d3f6a9..b64f34448 100644
--- a/docs/tutorials/pt/seller-management.md
+++ b/docs/tutorials/pt/seller-management.md
@@ -17,7 +17,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 __Gerenciamento de Sellers__ é a página onde operadores de marketplace [adicionam sellers](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392), registram suas informações e administram seus status. A página inclui métricas de andamento da operação de marketplace. Também é possível aplicar filtros nos resultados da lista de sellers e agrupar sellers por meio da opção Grupos que permite filtrar resultados mais facilmente.  
 
-![Seller management gif 2022 launch](//images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
+![Seller management gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/6nedzBeTr3y9d47ArKh40r/d280e61590f95fcd669cf45b137790f8/Seller_Management.gif)
 
 ## Métricas
 A página apresenta métricas gerais dos sellers:
@@ -46,7 +46,7 @@ Com essa funcionalidade, lojistas otimizam cenários de acompanhamento da opera
 
 Grupos são criados manualmente ao Adicionar seller ou clicando em Gerenciar grupos e após criados é possível editar e excluir cada um deles.  
 
-![Gerenciamento de sellers](//images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/cb37f601d4b9a096b0c1e94c03b90c11/gerenciamento_de_seller.png)  
+![Gerenciamento de sellers](https://images.ctfassets.net/alneenqid6w5/1dkekloSl228CxABGgylD7/cb37f601d4b9a096b0c1e94c03b90c11/gerenciamento_de_seller.png)  
 
 ## Gerenciar grupos  
 
diff --git a/docs/tutorials/pt/seller-monitoring.md b/docs/tutorials/pt/seller-monitoring.md
index a6586853d..f15f4753a 100644
--- a/docs/tutorials/pt/seller-monitoring.md
+++ b/docs/tutorials/pt/seller-monitoring.md
@@ -24,7 +24,7 @@ O **Monitoramento de seller** é uma ferramenta do módulo [Gerenciamento de sel
 
 - **Oque está acontecendo**: Aqui você acompanhará os detalhes do resultado da métrica com a visão detalhada da infração que levou o seller ao status de ⚠ **Aceitável** ou ❌ **Insatisfatório**. Épossível filtrar por seller,clicando no botão (colocar o símbolo do botão) e selecionar somente os sellers desejados.
 
-![Monitoramento de seller](//images.ctfassets.net/alneenqid6w5/1a6BgbLPMxQzuSPLFGb7DM/5fa662c273968852081a0ef98f50c95d/monitoramento_de_seller.png)
+![Monitoramento de seller](https://images.ctfassets.net/alneenqid6w5/1a6BgbLPMxQzuSPLFGb7DM/5fa662c273968852081a0ef98f50c95d/monitoramento_de_seller.png)
 
 Ao clicar no botão **Ver pedidos,** abrirá um pop-up com o **ID do pedido**, **Valor** e o botão **Ver.**
 
diff --git a/docs/tutorials/pt/seller-portal-creating-a-promotion.md b/docs/tutorials/pt/seller-portal-creating-a-promotion.md
index cd46503bf..16b4f8ba2 100644
--- a/docs/tutorials/pt/seller-portal-creating-a-promotion.md
+++ b/docs/tutorials/pt/seller-portal-creating-a-promotion.md
@@ -22,7 +22,7 @@ Para criar uma nova promoção como seller no Seller Portal, siga o passo a pass
 3. Preencha as informações descritas em [Campos de cadastro da promoção](#campos-de-cadastro-da-promocao).
 4. Clique em `Salvar.`
 5. Revise as configurações da sua promoção antes de publicá-la.
-![seller-portal-promo-revisao-pt](//images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/b4bd761ce6c36f7165a88ca5ac46eae3/image.png)
+![seller-portal-promo-revisao-pt](https://images.ctfassets.net/alneenqid6w5/76ttKMrp8E1XlK2QZ6OAJQ/b4bd761ce6c36f7165a88ca5ac46eae3/image.png)
 6. Depois de revisar as informações, clique em `Confirmar`.
 
 Feito isso, a promoção será ativada e aplicada na sua loja.
@@ -37,7 +37,7 @@ As promoções que afetam os mesmos itens inseridos no carrinho são comparadas
 
 Nesta seção, você deve configurar as informações gerais da sua promoção.
 
-![seller-portal-promo-geral-pt](//images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/88a1a7946d0794d9168b3d3816adbb33/image.png)
+![seller-portal-promo-geral-pt](https://images.ctfassets.net/alneenqid6w5/33rywokDbzTvVS1VscDxvp/88a1a7946d0794d9168b3d3816adbb33/image.png)
 
 * **Nome:** nome da promoção.
 * **Status: **opção que define se a promoção está ativa <i class="fas-toggle-on"></i> ou inativa <i class="fas-toggle-off"></i>.
@@ -51,7 +51,7 @@ Nesta seção, você deve configurar as informações gerais da sua promoção.
 
 Seção que define o tipo e valor do desconto que será aplicado na promoção. Veja as opções de desconto a seguir:
 
-![seller-portal-promo-tipo-desconto-pt](//images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/9acedc88d86af0f0a2fa860d941ccfa7/image.png)
+![seller-portal-promo-tipo-desconto-pt](https://images.ctfassets.net/alneenqid6w5/cvG0Q9A8BHoazDipvbnol/9acedc88d86af0f0a2fa860d941ccfa7/image.png)
 
 #### Preço
 
@@ -68,7 +68,7 @@ Seção que define o tipo e valor do desconto que será aplicado na promoção.
 
 Nesta seção, você precisa escolher se a promoção será aplicada a todos os produtos cadastrados na sua loja ou apenas a produtos específicos, conforme ilustrado abaixo.
 
-![seller-portal-promo-produtos-elegiveis-pt](//images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/737ac93c123828fe3c335dcf067bf7e7/image.png)
+![seller-portal-promo-produtos-elegiveis-pt](https://images.ctfassets.net/alneenqid6w5/77OBxN704Khh9t2MqXq49k/737ac93c123828fe3c335dcf067bf7e7/image.png)
 
 * **Todos os produtos:** aplica a promoção a todo o seu catálogo.
 * **Produtos que atendam a todas as seguintes regras:** limita a sua promoção a produtos específicos a partir das regras de seleção a seguir:
@@ -86,7 +86,7 @@ Para deletar uma regra, clique em <i class="fas-trash-can"></i> `Remover regra`.
 
 O pedido do cliente deve atender a todas as condições cadastradas nesta seção para ser válido na promoção.
 
-![seller-portal-promo-condicoes-pt](//images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/89137c0a33eea10f6c9ca9cd4e0bae1c/image.png)
+![seller-portal-promo-condicoes-pt](https://images.ctfassets.net/alneenqid6w5/52hsesSaNHcwM7Ti6jKQL7/89137c0a33eea10f6c9ca9cd4e0bae1c/image.png)
 
 * **Preço do item:** o desconto será concedido apenas aos itens que estão dentro do intervalo de preço preenchidos. 
 * **Tipo de envio:** o desconto será concedido caso o tipo de frete escolhido pelo cliente seja o mesmo que o cadastrado na promoção. 
@@ -97,6 +97,6 @@ O pedido do cliente deve atender a todas as condições cadastradas nesta seçã
 
 A atuação da promoção será limitada pelo seguinte critério:
 
-![seller-portal-promo-restricoes-pt](//images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/4f4b06e2fe29eb7ef71c28e4f39d26c8/image.png)
+![seller-portal-promo-restricoes-pt](https://images.ctfassets.net/alneenqid6w5/1FG1nW6lJCXmHJtSdlERkc/4f4b06e2fe29eb7ef71c28e4f39d26c8/image.png)
 
 * **Limitar a quantidade de itens elegíveis por carrinho:** define o número máximo de itens do carrinho serão afetados pela promoção. Caso o carrinho apresente uma quantidade de itens maior que o limite, o desconto será aplicado a apenas a quantidade configurada neste campo.
diff --git a/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
index c9b5519a4..2ff0b34fa 100644
--- a/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
@@ -27,7 +27,7 @@ Por meio do Seller Portal, marketplaces conseguem:
 - Diminuir o tempo de conversão das vendas, com o onboarding self-service de novos sellers, agora mais rápido e sem fricção.  
 - Compartilhar o sortimento de produtos com o seller de forma simples e gerenciar com agilidade anúncios de produtos compartilhados.  
 
-![Seller Portal gif 2022 launch](//images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
+![Seller Portal gif 2022 launch](https://images.ctfassets.net/alneenqid6w5/48uQe9Gi0K9ZU8qyXXO8US/ff02b9c926398dcfa69683bcfbf5b02f/Seller_Portal.gif)
 
 ## Interação entre seller e marketplace no Seller Portal
 
diff --git a/docs/tutorials/pt/seller-portal-product-details.md b/docs/tutorials/pt/seller-portal-product-details.md
index 11a26f6de..0a027e599 100644
--- a/docs/tutorials/pt/seller-portal-product-details.md
+++ b/docs/tutorials/pt/seller-portal-product-details.md
@@ -15,7 +15,7 @@ legacySlug: seller-portal-detalhes-do-produto
 subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
-![Shared products product details PT](//images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/6e0ade39ea38708c2081d48b346d96ed/Shared_products_product_details_PT.jpg)
+![Shared products product details PT](https://images.ctfassets.net/alneenqid6w5/6H2NihfYF5QWfj60VjFueu/6e0ade39ea38708c2081d48b346d96ed/Shared_products_product_details_PT.jpg)
 
 A página Detalhes do Produto na funcionalidade [Produtos Compartilhados](https://help.vtex.com/pt/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) é onde todas as informações sobre um produto  específico são visualizadas. É a partir dela que o seller:  
 
diff --git a/docs/tutorials/pt/seller-portal-promotions.md b/docs/tutorials/pt/seller-portal-promotions.md
index 13afa97af..a118129ed 100644
--- a/docs/tutorials/pt/seller-portal-promotions.md
+++ b/docs/tutorials/pt/seller-portal-promotions.md
@@ -27,7 +27,7 @@ A partir da lista de promoções no Seller Portal, você pode realizar uma varie
 * [Acessar menu de ações da promoção](#acessar-menu-de-acoes-da-promocao)
 * [Acessar promoções arquivadas](#acessar-promocoes-arquivadas)
 
-![seller-portal-promo-pt](//images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/124f6651a5de6411ec93f545748cd75c/image.png)
+![seller-portal-promo-pt](https://images.ctfassets.net/alneenqid6w5/266zLPS2IkGekYdMOz27Pz/124f6651a5de6411ec93f545748cd75c/image.png)
 
 A página **Promoções** apresenta as seguintes informações em uma tabela: 
 
@@ -71,7 +71,7 @@ O arquivo contém as seguintes informações sobre cada promoção:
 
 ## Verificar dados de uso das promoções
 
-![seller-portal-promo-ativas-pt](//images.ctfassets.net/alneenqid6w5/3tnyz6u3HxC6Qjezn9PvLr/b8e5dbee51610f19330da09d655ee8ca/image.png)
+![seller-portal-promo-ativas-pt](https://images.ctfassets.net/alneenqid6w5/3tnyz6u3HxC6Qjezn9PvLr/b8e5dbee51610f19330da09d655ee8ca/image.png)
 
 Para visualizar o total de promoções ativas na sua loja e a cota de espaço restante para novas promoções, clique em `Uso das promoções`.
 
diff --git a/docs/tutorials/pt/seller-portal-shared-products.md b/docs/tutorials/pt/seller-portal-shared-products.md
index 540fb0127..5348cfe44 100644
--- a/docs/tutorials/pt/seller-portal-shared-products.md
+++ b/docs/tutorials/pt/seller-portal-shared-products.md
@@ -29,7 +29,7 @@ Para acessar a funcionalidade Produtos Compartilhados, clique em *Preços > Cat
 
 ## Importados
 
-![Shared products Importados PT](//images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/e7b820dcb3cbbcc3031f58ec3e6dde20/Shared_products_Importados_PT.jpg)
+![Shared products Importados PT](https://images.ctfassets.net/alneenqid6w5/2mmTwK1Kn3g8TPOICMMMk8/e7b820dcb3cbbcc3031f58ec3e6dde20/Shared_products_Importados_PT.jpg)
 
 A aba *Importados* reúne produtos do catálogo do marketplace que já foram importados pelo seller, ou seja, que já podem virar anúncios. A lista contém uma barra de busca, para pesquisar produtos por nome ou SKU. É por meio dessa aba, que produtos são ativados.  
 
@@ -39,7 +39,7 @@ Ao clicar em um produto da listagem, você acessa a página de [Detalhes do prod
 
 ## Disponíveis 
 
-![Shared products Disponíveis PT](//images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/ad06a23c6ec0486964a8465290e215b3/Shared_products_Dispon__veis_PT.jpg)
+![Shared products Disponíveis PT](https://images.ctfassets.net/alneenqid6w5/1MIr5t82Ncx9ssV5oT2eyw/ad06a23c6ec0486964a8465290e215b3/Shared_products_Dispon__veis_PT.jpg)
 
 A aba *Disponíveis* reúne produtos do catálogo do marketplace que foram disponibilizados para que o seller os venda, e que não foram incorporados ainda no catálogo do seller. É possível filtrar os produtos disponíveis por marca ou categoria para agilizar o processo de importação dos produtos selecionados. 
 
diff --git a/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md b/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md
index 45daf8399..75095fcea 100644
--- a/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md
+++ b/docs/tutorials/pt/send-item-price-with-tax-shown-separately.md
@@ -22,10 +22,10 @@ Para isso, você pode utilizar a configuração de impostos em [__Pricing__](/pt
 Neste artigo, mostraremos como funciona o sistema para estes casos.
 **Cenário 1**: Meu ERP envia o preço já com o IVA para a VTEX, portanto, não preciso fazer o cálculo.
 
-1. Página de Categoria![CATEGORIASINIVA](//images.contentful.com/alneenqid6w5/OAT1GSzx4YUs4iuMKOsiE/61f68ef8a8f6ca0e52db228c53f0ede1/CATEGORIASINIVA.png)
-2. Página de Produto![PRODUTOSINIVA](//images.contentful.com/alneenqid6w5/2RW5XMDChOo2SaWWqcGGis/658b27601bff63231565921b5ccf9d48/PRODUCTOSINIVA.png)
-3. Carrinho![CARRINHOSINIVA](//images.contentful.com/alneenqid6w5/6aq95ChS2ke6yeqW8MKYWs/c6c3e4e8368a99a3ab65d0e4f8723fe3/CARRITOSINIVA.png)
-4. Checkout![CHECKOUTSINIVA](//images.contentful.com/alneenqid6w5/KD05AMNlKeEE2kMY2KsKw/e7d845e01d7e758da7395d3183e96461/CHECKOUTSINIVA.png)
+1. Página de Categoria![CATEGORIASINIVA](https://images.contentful.com/alneenqid6w5/OAT1GSzx4YUs4iuMKOsiE/61f68ef8a8f6ca0e52db228c53f0ede1/CATEGORIASINIVA.png)
+2. Página de Produto![PRODUTOSINIVA](https://images.contentful.com/alneenqid6w5/2RW5XMDChOo2SaWWqcGGis/658b27601bff63231565921b5ccf9d48/PRODUCTOSINIVA.png)
+3. Carrinho![CARRINHOSINIVA](https://images.contentful.com/alneenqid6w5/6aq95ChS2ke6yeqW8MKYWs/c6c3e4e8368a99a3ab65d0e4f8723fe3/CARRITOSINIVA.png)
+4. Checkout![CHECKOUTSINIVA](https://images.contentful.com/alneenqid6w5/KD05AMNlKeEE2kMY2KsKw/e7d845e01d7e758da7395d3183e96461/CHECKOUTSINIVA.png)
 
 **Cenário 2**: Meu ERP envia o preço *sem* IVA para a VTEX.
 
@@ -37,7 +37,7 @@ Ou, então, para criar um JS e somar o valor do imposto nas vitrines, também é
 
 __Atenção__: Na página de produto é necessário colocar um JavaScript para fazer a soma do valor.
 
-1. Página de Categoria![CATEGORIASINIVA](//images.contentful.com/alneenqid6w5/OAT1GSzx4YUs4iuMKOsiE/61f68ef8a8f6ca0e52db228c53f0ede1/CATEGORIASINIVA.png)
-2. Página de Produto![PRODUTOCONIVA](//images.contentful.com/alneenqid6w5/1PFWNiW4lK8ogIMKMu06Gy/d3ec875da04e52f971cac61f4b10d9b2/PRODUCTOCONIVA.png)
-3. Carrinho![CARRINHOCONIVA](//images.contentful.com/alneenqid6w5/52xSrXT1Pigoo4aAuwYq6A/7bdf52cfa0deb873fca1909592607fa9/CARRITOCONIVA.png)
-4. Checkout![CHECKOUTCONIVA](//images.contentful.com/alneenqid6w5/6Hbi6RI704AYM0GEUUO88A/4042846eac28ac9aafa6568a9f4adcf1/CHECKOUTCONIVA.png)
+1. Página de Categoria![CATEGORIASINIVA](https://images.contentful.com/alneenqid6w5/OAT1GSzx4YUs4iuMKOsiE/61f68ef8a8f6ca0e52db228c53f0ede1/CATEGORIASINIVA.png)
+2. Página de Produto![PRODUTOCONIVA](https://images.contentful.com/alneenqid6w5/1PFWNiW4lK8ogIMKMu06Gy/d3ec875da04e52f971cac61f4b10d9b2/PRODUCTOCONIVA.png)
+3. Carrinho![CARRINHOCONIVA](https://images.contentful.com/alneenqid6w5/52xSrXT1Pigoo4aAuwYq6A/7bdf52cfa0deb873fca1909592607fa9/CARRITOCONIVA.png)
+4. Checkout![CHECKOUTCONIVA](https://images.contentful.com/alneenqid6w5/6Hbi6RI704AYM0GEUUO88A/4042846eac28ac9aafa6568a9f4adcf1/CHECKOUTCONIVA.png)
diff --git a/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md b/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
index 03a48c233..df473b3f4 100644
--- a/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
+++ b/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
@@ -31,10 +31,10 @@ Os valores aceitos pelo Mercado Livre podem ser encontrados nos links a seguir.
 
 __Links com os valores aceitos pelo Mercado Livre__:
 
-- [Brasil](//assets.contentful.com/alneenqid6w5/6BHWQLL9bGuMq2ycMye0uc/76e64b67cb7352d95d6bb977b33394d4/Brasil-2.zip)
-- [Argentina](//assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
-- [Colômbia](//assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
-- [México](//assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+- [Brasil](https://assets.contentful.com/alneenqid6w5/6BHWQLL9bGuMq2ycMye0uc/76e64b67cb7352d95d6bb977b33394d4/Brasil-2.zip)
+- [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar)
+- [Colômbia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar)
+- [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
 
 Quando sua planilha estiver preenchida com os valores corretos, basta fazer o __upload no Bridge__ da VTEX. Para isso, siga estes passos:
 
@@ -49,7 +49,7 @@ __Pronto!__ Agora os atributos dos seus produtos do tipo __Roupa__, __Calçados_
 
 Um calçado *amarelo* com *detalhes azuis* de *tamanho 39* deve ser enviado para o Mercado Livre com o __ID do SKU__ correspondente e os códigos __33000_Amarelo_52007__, __43000_Azul_52092__ e __23000_39_22039__, relativos a *cor principal*, *cor secundária* e *tamanho*. Veja mais exemplos na imagem abaixo:
 
-![Planilha modelo ML](//images.contentful.com/alneenqid6w5/1Z4UPfR5beG6SoMucASAm0/132e8316128421a2c98da7ee8fdb81b4/Planilha-modelo-ML.png)
+![Planilha modelo ML](https://images.contentful.com/alneenqid6w5/1Z4UPfR5beG6SoMucASAm0/132e8316128421a2c98da7ee8fdb81b4/Planilha-modelo-ML.png)
 
 ## Para saber mais
 
diff --git a/docs/tutorials/pt/sending-products-to-the-marketplace.md b/docs/tutorials/pt/sending-products-to-the-marketplace.md
index 814e49708..7ebe0ea0a 100644
--- a/docs/tutorials/pt/sending-products-to-the-marketplace.md
+++ b/docs/tutorials/pt/sending-products-to-the-marketplace.md
@@ -21,7 +21,7 @@ Ao se integrar com um marketplace, é preciso definir quais produtos serão envi
 
 Uma possibilidade é trabalhar todo o catálogo de produtos junto ao marketplace. Para isso, basta associar o ID da política comercial da loja principal, que será sempre a de **ID 1**, [quando solicitado nas configurações](/pt/tutorial/integrando-com-marketplace/).
 
-![ExemploPoliticaComercial](//images.contentful.com/alneenqid6w5/37CzxbrZ9KciYm4G2gK0MK/54a58d8fa3a53dcf310caa2769e53174/ExemploPoliticaComercial.png)
+![ExemploPoliticaComercial](https://images.contentful.com/alneenqid6w5/37CzxbrZ9KciYm4G2gK0MK/54a58d8fa3a53dcf310caa2769e53174/ExemploPoliticaComercial.png)
 
 Esta política comercial não demanda uma coleção de produtos configurada, pois o sistema já entende que ela se refere a todos os produtos.
 
@@ -34,7 +34,7 @@ Outra possibilidade é trabalhar com um sortimento específico por alguma polí
 5. Marque o checkbox das políticas comerciais a qual este produto deverá pertencer.
 6. Clique em **Salvar**.
 
-![](//images.contentful.com/alneenqid6w5/2Fp2Y3qFF6SCwQaQI2iEiC/fae0654d1685f1f625794180044ae6a6/loja-cadastro-produto.gif)
+![](https://images.contentful.com/alneenqid6w5/2Fp2Y3qFF6SCwQaQI2iEiC/fae0654d1685f1f625794180044ae6a6/loja-cadastro-produto.gif)
 _Caso existam produtos que não têm nenhum valor marcado no campo **loja** no cadastro de produtos ou no cadastro de preços, esses produtos serão enviados para todas as políticas comerciais configuradas sem coleção._
 
 ## Indexação do Produto
diff --git a/docs/tutorials/pt/sending-sku-attributes-to-amazon.md b/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
index 8a5e78f3e..f8985dcdb 100644
--- a/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
@@ -19,7 +19,7 @@ Feitas as configurações iniciais para a [integração com a Amazon](/pt/tutori
 
 O mapeamento só será feito uma vez para cada categoria. Desta forma, mesmo já tendo feito um mapeamento, quando novos produtos forem criados, eles serão integrados diretamente. Será feito um __de/para__ dos atributos cadastrados na VTEX com os atributos aceitos pela Amazon.
 
-1. Crie uma __planilha de upload__ no formato `.xlsx` e preencha o título das colunas conforme a imagem abaixo.![Modelo Atributos Amazon](//images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
+1. Crie uma __planilha de upload__ no formato `.xlsx` e preencha o título das colunas conforme a imagem abaixo.![Modelo Atributos Amazon](https://images.ctfassets.net/alneenqid6w5/1oqAPItLPaMc8gYICU6oWa/7d54955d0c179a2fbcb036e62ede9dc3/Modelo_Atributos_Amazon.png)
 
 2. Preencha os campos da planilha de mapeamento de acordo com as indicações abaixo:
 
@@ -49,7 +49,7 @@ Atenção: caso as colunas não forem nomeadas <strong>tal qual</strong> a forma
 
 Planilha de exemplo usando a categoria Clothing & Accessories:
 
-![Amazon Mapeamento ](//images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
+![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
 <div class="alert alert-danger">
 Lembre-se que estes valores devem estar de acordo com os valores aceitos pela Amazon. Consulte os termos aceitos e faça o De/Para entre o que está cadastrado no seu campo de SKU na VTEX e os valores permitidos na Amazon.
diff --git a/docs/tutorials/pt/sent-offers-beta.md b/docs/tutorials/pt/sent-offers-beta.md
index 668b896e8..1529128e9 100644
--- a/docs/tutorials/pt/sent-offers-beta.md
+++ b/docs/tutorials/pt/sent-offers-beta.md
@@ -22,7 +22,7 @@ O módulo Anúncios Enviados permite que sellers supervisionem o envio e a sincr
 - [Anúncios](https://help.vtex.com/pt/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#anuncios)            
 - [Canais](https://help.vtex.com/pt/tutorial/anuncios-enviados-beta--6yg2CBv5Z5AnD0qS0cw2sa#canais)          
 
-![Anuncios enviados Home PT](//images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/7b571504f49ac69f0788861144905d4e/Anuncios_enviados_Home_PT.jpg)
+![Anuncios enviados Home PT](https://images.ctfassets.net/alneenqid6w5/4eTCYZQ0RRa2n9JN81RhRG/7b571504f49ac69f0788861144905d4e/Anuncios_enviados_Home_PT.jpg)
 
 ## Anúncios
 
diff --git a/docs/tutorials/pt/sent-offers-buybox-opportunities.md b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
index 013a044ac..4cba68222 100644
--- a/docs/tutorials/pt/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
@@ -40,19 +40,19 @@ Na página [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/offers
 
 ## Detalhes do Anúncio
 
-![PT Oportunidades Offer details](//images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/c50404811bbb7be69e463f97cdc4408e/PT_Oportunidades_Offer_details.jpg)
+![PT Oportunidades Offer details](https://images.ctfassets.net/alneenqid6w5/05EP70mvjspXAYAqYUBlm/c50404811bbb7be69e463f97cdc4408e/PT_Oportunidades_Offer_details.jpg)
 
 A página de [Detalhes do anúncio](https://help.vtex.com/pt/tutorial/detalhes-do-anuncio--4FF9QYAewqAn610mDHwb0P) apresenta um card de `Oportunidade` no topo. Ao clicar em `Ver Oportunidade`, você será redirecionado para a página a seguir.
 
 ## Oportunidades do Anúncio
 
-![PT Oportunidades oportunidades do anúncio](//images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/753c2b80a4bf68ca6f82aa6f23cca363/PT_Oportunidades_oportunidades_do_an__ncio.jpg)
+![PT Oportunidades oportunidades do anúncio](https://images.ctfassets.net/alneenqid6w5/6Atuthxay11bdJrmSQxEM9/753c2b80a4bf68ca6f82aa6f23cca363/PT_Oportunidades_oportunidades_do_an__ncio.jpg)
 
 A página **Oportunidades do anúncio** apresenta o anúncio elegível para o Catálogo MeLi ao lado do anúncio já presente no marketplace. A página permite comparar os dados dos dois anúncios, incluindo informações das marcas, especificações e dimensões.
 
 Além da oportunidade de adicionar anúncios, há o __Auto Optin (criação automática de anúncios Catálogo MeLi)__, nesta opção o Mercado Livre irá avaliar as publicações dos sellers, caso cumpra com todos os requisitos para se tornar um anúncio de Catálogo MeLi, ele será feito automaticamente e o seller visualizará a mensagem da imagem abaixo.
 
-![Auto Optin MELI](//images.ctfassets.net/alneenqid6w5/2Hiw11uUW5n5QHvwIlpo0C/95e691c69a8a8afccdf50abd0f0d09c4/Captura_de_tela_2023-06-27_175316.png)
+![Auto Optin MELI](https://images.ctfassets.net/alneenqid6w5/2Hiw11uUW5n5QHvwIlpo0C/95e691c69a8a8afccdf50abd0f0d09c4/Captura_de_tela_2023-06-27_175316.png)
 
 ## Adicionar anúncios ao Catálogo MeLi
 
@@ -90,4 +90,4 @@ A seção de *Oportunidades Ativas* da página [Detalhes do anúncio](https://he
 - **Status da oportunidade:** incluindo `Ganhando` ou `Perdendo`.  
 - **Lista de configurações:** ações necessárias para que seu anúncio esteja ganhando na Catálogo MeLi. As instruções listadas incluem alterar preço, promover frete grátis, entrega rápida ou oferecer pagamento com parcelamento sem juros, por exemplo. Cada item da lista apresenta uma sugestão de configuração  que tornará o anúncio mais atrativo, posicionando-o em primeiro lugar no Catálogo MeLi. 
 
-![PT Oportunidades oportunidades ativas](//images.ctfassets.net/alneenqid6w5/1e5ozasXAVsjNrH7RBjq71/6e7672dc863d4150b4e8b8efe600187a/PT_Oportunidades_oportunidades_ativas.jpg)
+![PT Oportunidades oportunidades ativas](https://images.ctfassets.net/alneenqid6w5/1e5ozasXAVsjNrH7RBjq71/6e7672dc863d4150b4e8b8efe600187a/PT_Oportunidades_oportunidades_ativas.jpg)
diff --git a/docs/tutorials/pt/sequencial-suiteshare.md b/docs/tutorials/pt/sequencial-suiteshare.md
index db049a682..9c7ad4e4f 100644
--- a/docs/tutorials/pt/sequencial-suiteshare.md
+++ b/docs/tutorials/pt/sequencial-suiteshare.md
@@ -21,25 +21,25 @@ O Sequencial garante que a sua empresa terá um atendimento no WhatsApp mais org
 
  Para criar um atendimento seletivo, acesse: _**Organizar > Sequencial**_. 
 
-![Sequencial  1](//images.ctfassets.net/alneenqid6w5/5d6rENDv7iZliW45U3wSdX/863a4066aeb31f4130f509441aed7560/Screenshot_2022-08-29_at_17-29-16_Sequencial.png)
+![Sequencial  1](https://images.ctfassets.net/alneenqid6w5/5d6rENDv7iZliW45U3wSdX/863a4066aeb31f4130f509441aed7560/Screenshot_2022-08-29_at_17-29-16_Sequencial.png)
 
 IMPORTANTE: Antes de começar, você já deverá ter criado um link para cada número de WhatsApp que deseja adicionar na central. Se ainda não fez isso, é só [acessar esse link](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB).
 
 Clique em “_**Novo**_”.
 
-![Sequencial 2](//images.ctfassets.net/alneenqid6w5/6yE3a7cKM7tjSmg2YUCnsi/372a64bb021c5ed195aa0d49fc3a0508/Screenshot_2022-08-29_at_17-29-21_Sequencial.png)
+![Sequencial 2](https://images.ctfassets.net/alneenqid6w5/6yE3a7cKM7tjSmg2YUCnsi/372a64bb021c5ed195aa0d49fc3a0508/Screenshot_2022-08-29_at_17-29-21_Sequencial.png)
 
 Defina o **link principal**. 
 
 Em **Link Âncora**, como o próprio nome já diz, você irá selecionar o link principal da central. Esse é o link que você irá divulgar, será o link responsável por fazer a ligação com os demais atendentes.
 
-![Sequencial 3](//images.ctfassets.net/alneenqid6w5/1ey00JvWyDeOWkCG7kzhgl/1985a9808e85374f15d3fb21feabb4b5/Screenshot_2022-08-29_at_17-29-25_Sequencial.png)
+![Sequencial 3](https://images.ctfassets.net/alneenqid6w5/1ey00JvWyDeOWkCG7kzhgl/1985a9808e85374f15d3fb21feabb4b5/Screenshot_2022-08-29_at_17-29-25_Sequencial.png)
 
 Clique em _**“Avançar”**_.
 
 Em Links de Sequência, você irá escolher quem serão os vendedores ou números que irão participar da central. Clique em Adicionar e selecione o link para cada participante da central.
 
-![Sequencial 4](//images.ctfassets.net/alneenqid6w5/7wYRRK5a5E8Myh7LUkSNKN/facae61bda1dafdc6421eca7cbd19687/Screenshot_2022-08-29_at_17-29-30_Sequencial.png)
+![Sequencial 4](https://images.ctfassets.net/alneenqid6w5/7wYRRK5a5E8Myh7LUkSNKN/facae61bda1dafdc6421eca7cbd19687/Screenshot_2022-08-29_at_17-29-30_Sequencial.png)
 
 **NOTA**: Em atendimento fixo (opcional), você irá escolher se um cliente que já falou com algum atendente, ao clicar novamente no link principal (/minhacentral), cairá sempre para o mesmo atendente.
 
diff --git a/docs/tutorials/pt/services-import.md b/docs/tutorials/pt/services-import.md
index 26639db7e..cbb5b62d9 100644
--- a/docs/tutorials/pt/services-import.md
+++ b/docs/tutorials/pt/services-import.md
@@ -86,5 +86,5 @@ Cuidados com o preenchimento da planilha:
   </body>
 </div>
 
-![menu importação de serviços](//images.ctfassets.net/alneenqid6w5/6VXBtxVKQvnNvqEwCI09dZ/15a4abddec959d9efdd9ae97f4116b97/importacao_servi__os.png)
+![menu importação de serviços](https://images.ctfassets.net/alneenqid6w5/6VXBtxVKQvnNvqEwCI09dZ/15a4abddec959d9efdd9ae97f4116b97/importacao_servi__os.png)
 
diff --git a/docs/tutorials/pt/services-scheduling.md b/docs/tutorials/pt/services-scheduling.md
index f986ed053..210a6c8ae 100644
--- a/docs/tutorials/pt/services-scheduling.md
+++ b/docs/tutorials/pt/services-scheduling.md
@@ -48,7 +48,7 @@ Na planilha os campos a serem preenchidos são:
 
 Para escolher o turno da entrega, marque um X na célula em apenas um dos turnos (Manhã, Tarde ou Noite).
 
-![exemplo de planilha de agendamento](//images.ctfassets.net/alneenqid6w5/5crlOibYcmzfWkusdc2iSP/2cefb30f0df8fc7ab61104a09f8f9414/exemplo_planilha_agendamento.png)
+![exemplo de planilha de agendamento](https://images.ctfassets.net/alneenqid6w5/5crlOibYcmzfWkusdc2iSP/2cefb30f0df8fc7ab61104a09f8f9414/exemplo_planilha_agendamento.png)
 
 <div class="alert alert-danger"> 
 O modelo da planilha não deve ser alterado. Nenhuma coluna deve ser modificada ou trocada de posição. 
@@ -76,4 +76,4 @@ Depois de preencher a planilha, você precisa subir o arquivo na plataforma VTEX
 Os agendamentos só podem ser alterados se as entregas ainda estiverem no status Ativo. 
 </div>
 
-![Agendamento de serviços](//images.ctfassets.net/alneenqid6w5/OhKdJX8S3Ef4EjoUOaGL3/5f463a280ae7cfa51a856d047b39be82/Agendamento.gif)
+![Agendamento de serviços](https://images.ctfassets.net/alneenqid6w5/OhKdJX8S3Ef4EjoUOaGL3/5f463a280ae7cfa51a856d047b39be82/Agendamento.gif)
diff --git a/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md b/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md
index 1c65b37fc..0ad42d386 100644
--- a/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md
+++ b/docs/tutorials/pt/set-up-user-authentication-for-recurring-payments.md
@@ -27,7 +27,7 @@ Para configurar essa autenticação, siga os passos abaixo:
 2. Entre em __Configurações__ 
 3. Na seção de **Carrinho**, ative a flag __Exigir autenticação do usuário para pagamentos autorizados automaticamente__
 
-![autenticação-usuario-pagamento-recorrencia pt](//images.ctfassets.net/alneenqid6w5/16uRqeq2F4k4UIouOooeoo/40ff615b3f2cbe6b079462960f0a5e8f/autentica____o-usuario-pagamento-recorrencia_pt.png)
+![autenticação-usuario-pagamento-recorrencia pt](https://images.ctfassets.net/alneenqid6w5/16uRqeq2F4k4UIouOooeoo/40ff615b3f2cbe6b079462960f0a5e8f/autentica____o-usuario-pagamento-recorrencia_pt.png)
 
 
 4. Clique no botão __Salvar__.
diff --git a/docs/tutorials/pt/setting-up-a-personal-gift-message.md b/docs/tutorials/pt/setting-up-a-personal-gift-message.md
index 2b8fb74ea..8ebbedc66 100644
--- a/docs/tutorials/pt/setting-up-a-personal-gift-message.md
+++ b/docs/tutorials/pt/setting-up-a-personal-gift-message.md
@@ -45,11 +45,11 @@ No site da sua loja, é possível validar se a configuração foi efetuada corre
 3. Neste momento o tipo de serviço deve ser disponibilizado para seleção. A mensagem precisa ser escrita em até 150 caracteres.
 4. Selecione o serviço no carrinho clique no link para adicionar mensagem.
 
-![](//images.contentful.com/alneenqid6w5/3txxLHOWtqguWu4qmAqumA/e68ef2cf4881d3b9a01199244567c790/mensagem-carrinho.png)
+![](https://images.contentful.com/alneenqid6w5/3txxLHOWtqguWu4qmAqumA/e68ef2cf4881d3b9a01199244567c790/mensagem-carrinho.png)
 
 Você pode visualizar a mensagem escrita em __Minha Conta > Meus Pedidos__:
 
-![](//images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
+![](https://images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
 
 <div class="alert alert-info">
   <p>Após a configuração do serviço no SKU, aguarde a indexação para o cadastro ter efeito no site. Após isto já será possível testar a compra com este serviço ativo.</p>
diff --git a/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md b/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md
index f63dbe80d..81244d7d1 100644
--- a/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md
+++ b/docs/tutorials/pt/setting-up-a-similar-product-suggestions-accessories-and-generics.md
@@ -35,7 +35,7 @@ Para te auxiliar na utilização da técnicas acima podemos utilizar os campos n
 4. Preencha os campos corretamente conforme indicação abaixo.
 5. Clique no botão `Salvar`.
 
-![produto-similar-sugestão-acessório-exemplo pt](//images.ctfassets.net/alneenqid6w5/2Eg0eAnNjCkWu6acGQYq4Q/02418b5ba84fbbca1c8269ebcbc51d96/produto-simular-sugest__o-acess__rio-exemplo_pt.png)
+![produto-similar-sugestão-acessório-exemplo pt](https://images.ctfassets.net/alneenqid6w5/2Eg0eAnNjCkWu6acGQYq4Q/02418b5ba84fbbca1c8269ebcbc51d96/produto-simular-sugest__o-acess__rio-exemplo_pt.png)
 
 **Acessórios:** nesse campo cadastramos os produtos que devem ser vendidos como complemento de um outro produto. Nesta opção os produto cadastrados como acessórios são mostrados como opção de compra com o checkbox de seleção habilitado (função feita no layout).
 
diff --git a/docs/tutorials/pt/setting-up-abandoned-carts.md b/docs/tutorials/pt/setting-up-abandoned-carts.md
index c420a17bb..45ae60f99 100644
--- a/docs/tutorials/pt/setting-up-abandoned-carts.md
+++ b/docs/tutorials/pt/setting-up-abandoned-carts.md
@@ -40,7 +40,7 @@ Você pode criar o seu próprio template de email customizado ou utilizar a opç
 4. Preencha o campo __Template XHTML__ com os códigos do template.
 5. Clique em `Save Template`.
 
-![template xhtml](//images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
+![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
 
 <div class="alert alert-warning">
 Recomendamos que a customização de template seja realizada por profissionais com experiência no módulo CMS, e preferencialmente, que já tenham realizado configurações de outros templates de página e prateleira.
@@ -52,7 +52,7 @@ Para utilizar uma opção padrão de template, siga os seguintes passos:
 2. Em __CMS > HTML Templates__, clique em `CEM-Abandoned-Cart`.
 3. Verifique as informações dos códigos de template presentes no campo __Template XHTML__.
 
-![CEM-Abandoned-Cart](//images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
+![CEM-Abandoned-Cart](https://images.ctfassets.net/alneenqid6w5/5ZBXBk2KNJVjekmT7P7RqQ/0dd187775baec69f3deee305c05950cb/CEM-Abandoned-Cart.PNG)
 
 ### Configurar modelo de email na Central de Mensagens
 
@@ -71,7 +71,7 @@ Uma vez criado o novo template de email ou utilizado os dados do template padrã
 O campo JSON Data não deve ser preenchido ou seus dados utilizados no template do email. Ele contém apenas informações para permitir uma pré-visualização do formato em que os dados que serão visualizados no email.
 </div>
 
-![New template - message center](//images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
+![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
 
 ### Liberar SPF
 
@@ -79,7 +79,7 @@ A liberação do SPF é fundamental para evitar problemas de entregabilidade do
 
 Como boa prática de configuração de DNS de um domínio genérico (não obrigatório), segue o exemplo abaixo:
 
-![Hostnames - SPF](//images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
+![Hostnames - SPF](https://images.ctfassets.net/alneenqid6w5/4txj9x3nVeN7Z3WEZmSpev/45230f3dbeda2d8ee040ec8a6ee39d31/Hostnames_-_SPF.PNG)
 
 Saiba mais em [Configurar o apontamento de DNS para a VTEX](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280?&utm_source=autocomplete).
 
diff --git a/docs/tutorials/pt/setting-up-an-index-on-master-data.md b/docs/tutorials/pt/setting-up-an-index-on-master-data.md
index a3f15c5b0..43a0ba5c6 100644
--- a/docs/tutorials/pt/setting-up-an-index-on-master-data.md
+++ b/docs/tutorials/pt/setting-up-an-index-on-master-data.md
@@ -44,9 +44,9 @@ A tabela cliente possui 2 colunas: ID e nome.
 ID é um número que não se repete, pois é o número que identifica o cliente. Nome é o nome do cliente.
 Porém, para facilitar a busca, a coluna nome foi criada como índice e colocada como **Valores Únicos**. 
 
-[![indice1](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png "![indice1](//images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)")Com isso, caso se queira inserir um nome que já tenha sido cadastrado em Cliente, não será possível. 
+[![indice1](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png "![indice1](https://images.contentful.com/alneenqid6w5/2Z02pI4DxeaaWOmYw42Suu/60bb0d893f5bd07f94928288390a5526/image011.png)")Com isso, caso se queira inserir um nome que já tenha sido cadastrado em Cliente, não será possível. 
 
-[![indice2](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png "![indice2](//images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)")
+[![indice2](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png "![indice2](https://images.contentful.com/alneenqid6w5/FwEjcrqaQwKE8U4AEMOY4/ca741feb38fb89e6c3e0bd3ec442ba37/image002.png)")
 Esse exemplo mostra que a opção **Valores Únicos** deve ser utilizada com cuidado, pois, caso um valor possa se repetir, ele será impedido de ser cadastrado com a configuração realizada.
 
 ### Vários campos no Índice
@@ -57,9 +57,9 @@ Neste caso, a chave alternativa vai impedir que a combinação dos campos seleci
 
 Seguindo o mesmo exemplo, imagine que a entidade cliente tenha mais uma coluna: CPF. Então, na configuração do índice, em **Composição de campos**, foram inseridas as colunas nome e CPF.
 
-[![indice3](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png "![indice3](//images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)")
+[![indice3](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png "![indice3](https://images.contentful.com/alneenqid6w5/41Y8vUIFjWGuqoqwA6UYaK/0a33bc147f17f95ea5038124bbd5132a/image021.png)")
 Então, agora é possível incluir o Marcos do exemplo anterior, basta que ele não tenha o mesmo CPF que o Marcos já inserido. Ou seja, apenas a combinação de campos não pode se repetir. Podem ter CPFs repetidos entre si e podem ter nomes repetidos entre si, porém, não pode ser CPF e nome repetido para o mesmo registro.
 
-[![indice4](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png "![indice4](//images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)")
+[![indice4](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png "![indice4](https://images.contentful.com/alneenqid6w5/36308RenwQq2aYcSkAYq6K/5a18bd8e7eca83e3f7ac40d3e6ca41ad/image031.png)")
 
 __Lembre-se!__ Neste caso também é necessário atenção pois a mesma combinação de valores não poderão e repetir e o registro será impossibilitado de ser gravado. Recomendamos que o atributo **Valores Únicos** no Índice seja utilizado apenas quando os valores não têm possibilidade de se repetir.
diff --git a/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
index f06796908..88660b170 100644
--- a/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
@@ -17,7 +17,7 @@ subcategory:
 
 Este artigo tem como objetivo explicar como a app do inStore configura o AppLinking para as ações de `payment` e `payment-reversal` com as apps dos adquirentes.
 
-![Payment app](//images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
+![Payment app](https://images.ctfassets.net/alneenqid6w5/SZ7d3IeuCAagwCqSW4eCO/27d469e37d9d1d8fb3ce22850012e685/Payment_app.png)
 
 ## Campos de configuração
 
diff --git a/docs/tutorials/pt/setting-up-b2b-on-vtex.md b/docs/tutorials/pt/setting-up-b2b-on-vtex.md
index e8ef70f12..1199c091e 100644
--- a/docs/tutorials/pt/setting-up-b2b-on-vtex.md
+++ b/docs/tutorials/pt/setting-up-b2b-on-vtex.md
@@ -35,7 +35,7 @@ Esse é o passo mais importante para ativar o B2B. Ao configurar a Política Com
 
 Normalmente, nos B2Bs convencionais, esse campo é preenchido com o valor `approved="true"` (`approved` é o nome de um campo na entidade Cliente, no Master Data). Com essa regra, o sistema permite que apenas usuários autenticados e aprovados naveguem no site.
 
-![](//images.contentful.com/alneenqid6w5/34rM0gmlgQOoqwwEG2c0ck/a506984d2e7c23381e05a6ad16306d9f/1.png)
+![](https://images.contentful.com/alneenqid6w5/34rM0gmlgQOoqwwEG2c0ck/a506984d2e7c23381e05a6ad16306d9f/1.png)
 
 ## 2. Customizar layout de diretórios B2B
 
@@ -49,15 +49,15 @@ Veja as características básicas de cada tipo de usuário:
 
 Dessa forma, para ter um ambiente B2B, será necessário customizar as pastas **401** e **403**, filhas da pasta **sistema**.
 
-![](//images.contentful.com/alneenqid6w5/4eOGUWH7nWqyQGCmIou6WO/1910b62f54515007e85aa3a82d04fb9e/2.png)
+![](https://images.contentful.com/alneenqid6w5/4eOGUWH7nWqyQGCmIou6WO/1910b62f54515007e85aa3a82d04fb9e/2.png)
 
 Navegação por um usuário Anônimo (ao tentar acessar qualquer página, será redirecionado para 401):
 
-![](//images.contentful.com/alneenqid6w5/1bxTbhKatws2mgGiOGSUYW/8bf8e626bf53a8e785ffdcc5f2ffc813/3.png)
+![](https://images.contentful.com/alneenqid6w5/1bxTbhKatws2mgGiOGSUYW/8bf8e626bf53a8e785ffdcc5f2ffc813/3.png)
 
 Navegação por um usuário não aprovado (ao tentar acessar qualquer página, será redirecionado para 403):
 
-![](//images.contentful.com/alneenqid6w5/1Ep24Fgl1SIG6Uw8Wmkq42/2a995f8d9c2be0e92629447c1e6d3948/4.png)
+![](https://images.contentful.com/alneenqid6w5/1Ep24Fgl1SIG6Uw8Wmkq42/2a995f8d9c2be0e92629447c1e6d3948/4.png)
 
 ## 3. Definir campos de pré-cadastro
 
@@ -73,7 +73,7 @@ Dessa forma, é necessário definir os campos desse pré-cadastro. Normalmente,
 
 Após definidos os campos, você deverá criar o formulário de pré-cadastro na pasta **/sistema/401**, pois é a única pasta para onde o usuário anônimo sempre será redirecionado.
 
-As informações submetidas no formulário deverão ser enviadas para o CRM através das APIs do Master Data ([veja documentação](https://developers.vtex.com/reference/master-data-api-v2-overview), ou seja, será necessário desenvolver um JavaScript para aplicar essa função. Confira aqui um [exemplo de template HTML e JavaScript](//assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar "Exemplo de template HTML e JS") com esse propósito.
+As informações submetidas no formulário deverão ser enviadas para o CRM através das APIs do Master Data ([veja documentação](https://developers.vtex.com/reference/master-data-api-v2-overview), ou seja, será necessário desenvolver um JavaScript para aplicar essa função. Confira aqui um [exemplo de template HTML e JavaScript](https://assets.contentful.com/alneenqid6w5/5PJaFVGdOwomgCYG66g2M4/ac29ba69fdd11cb8c87b88a0a6a62795/ExemploTemplateB2B.rar "Exemplo de template HTML e JS") com esse propósito.
 
 ## 5. Operação
 
diff --git a/docs/tutorials/pt/setting-up-cache-for-queries-to-master-data.md b/docs/tutorials/pt/setting-up-cache-for-queries-to-master-data.md
index b969a521a..ae07436d4 100644
--- a/docs/tutorials/pt/setting-up-cache-for-queries-to-master-data.md
+++ b/docs/tutorials/pt/setting-up-cache-for-queries-to-master-data.md
@@ -26,7 +26,7 @@ Para configurar essa camada de cache, siga os passos abaixo:
 2. Clique em __Novo__ para criar uma nova entidade ou no ícone de lápis de uma entidade existente caso queira editá-la.
 3. Clique na caixa de seleção __Tempo de cache para consultas paginadas__ e escolha o tempo de cache para a entidade.
 
-![cacheMD](//images.contentful.com/alneenqid6w5/7EJ8s7Z3uE0coc4QUkQcQC/0efbe18c6bd8018165e18f6d87da765f/cacheMD.jpg)
+![cacheMD](https://images.contentful.com/alneenqid6w5/7EJ8s7Z3uE0coc4QUkQcQC/0efbe18c6bd8018165e18f6d87da765f/cacheMD.jpg)
 
 As opções de tempo de cache são:
 - 5 horas
diff --git a/docs/tutorials/pt/setting-up-cybersource-gateway.md b/docs/tutorials/pt/setting-up-cybersource-gateway.md
index 33d22ecf7..272306cbc 100644
--- a/docs/tutorials/pt/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/pt/setting-up-cybersource-gateway.md
@@ -64,7 +64,7 @@ Siga os passos abaixo:
 
 Com as chaves de autenticação disponíveis, é o momento de realizar a configuração do app Cybersource IO no Admin. 
 
-![Cybersource Admin settings PT](//images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/635fe1762fa5be2e9c6c118f5245cb39/Cybersource_Admin_settings_PT.JPG)
+![Cybersource Admin settings PT](https://images.ctfassets.net/alneenqid6w5/53S98k6G5yOwOJrAO4ueiF/635fe1762fa5be2e9c6c118f5245cb39/Cybersource_Admin_settings_PT.JPG)
 
 Siga os passos abaixo para configurar o app Cybersource IO:
 
@@ -190,7 +190,7 @@ document.body.appendChild(noScript);
 
 Adicionalmente, você pode definir campos customizados que serão incluídos em pedidos encaminhados da VTEX para a Cybersource. 
 
-![Cybersource Admin merchant define fields PT](//images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/107a5ce54fb0f218e8bed5918499d9b4/Cybersource_Admin_merchant_define_fields_PT.JPG)
+![Cybersource Admin merchant define fields PT](https://images.ctfassets.net/alneenqid6w5/5KPPO5k4to3sH9amCFyp7B/107a5ce54fb0f218e8bed5918499d9b4/Cybersource_Admin_merchant_define_fields_PT.JPG)
 
 Veja abaixo como criar estes campos:
 
diff --git a/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md b/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md
index 6cea1dd0b..35e0e6222 100644
--- a/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md
+++ b/docs/tutorials/pt/setting-up-intelligent-search-integration-with-the-catalog.md
@@ -25,6 +25,6 @@ Siga as instruções para iniciar o processo de integração:
 
 O processo de indexação será iniciado. Uma vez concluído, a tela ilustrada a seguir será exibida.
 
-![integracoes-is](//images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/43b9e3474b8f3046405278e34266e0fc/integracoes-is.PNG)
+![integracoes-is](https://images.ctfassets.net/alneenqid6w5/3biSEYFprYPdnhQpgfpGhV/43b9e3474b8f3046405278e34266e0fc/integracoes-is.PNG)
 
 Não é necessário repetir esse processo. Depois de iniciar a integração, é possível acompanhar o status da indexação na página [Histórico da indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH).
diff --git a/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
index 2c4b71f09..ea7951823 100644
--- a/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
@@ -35,18 +35,18 @@ Dito isso, confira o passo a passo:
 
 1. Acesse sua __conta de desenvolvedor__ Apple em `https://developer.apple.com/account/#/overview`;
 2. Selecione a opção __Certificates, IDs & Profiles__;
-![AP1](//images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
+![AP1](https://images.ctfassets.net/alneenqid6w5/6LeAGbVL1w66i4QeoUikfC/912141350c1d591a9bb057d791e2f8d5/AP1.PNG)
 3. Clique em __Identifiers__;
- ![AP2](//images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
+ ![AP2](https://images.ctfassets.net/alneenqid6w5/23SE1jYWfCN6ZXTgQFYc1o/19fbe5f704aee658dd5a77f8e2f3b161/AP2.PNG)
 4. Ao lado de Identifiers, clique no __botão azul +__;
-![AP3](//images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
+![AP3](https://images.ctfassets.net/alneenqid6w5/4JGlrzDtI0BL3MDChr5gfn/2fb71b0a4dfc498baff3acb0546e5476/AP3.PNG)
 5. Selecione a opção __Merchant IDs__; 
 6. Clique no botão azul __Continue__;
-![AP4](//images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
+![AP4](https://images.ctfassets.net/alneenqid6w5/6OyfJq6Eeped4gNItoqD93/19edd37b12bb72d24d55058f5aa265bf/AP4.PNG)
 7. Preencha o campo __Description__;
 8. Preencha o campo __Identifier__; 
 9. Clique no botão __Continue__;
-![AP5](//images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
+![AP5](https://images.ctfassets.net/alneenqid6w5/7cPYdu8tLJsQWH7FFemIxb/8d710da870e18a5db33e46f29d484882/AP5.PNG) 
 
 Desse modo, o __Merchant ID__ será criado. 
 
@@ -61,14 +61,14 @@ Em seguida, o lojista pode submetê-lo ao sistema do Apple Pay.
 Para iniciar essa etapa, prossiga com as instruções: 
 
 1. No menu do lado esquerdo, selecione __Certificates__;
-![AP6](//images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
+![AP6](https://images.ctfassets.net/alneenqid6w5/6F1QMQhaeedUplo0gYGaHd/bbc1c07ad0f8541f33a797b09224543a/AP6.PNG)
 2. Digite seu __Merchant ID__ recém-criado na barra de busca;
 3. Selecione o __Merchant ID__ desejado;
-![AP7](//images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
+![AP7](https://images.ctfassets.net/alneenqid6w5/6McxWOZA6ZGUtsoxsRoVKb/d0f133d66267606fa998be562b57570b/AP7.PNG)
 4. No item __Apple Pay Payment Processing Certificate__, clique no botão __Create Certificate__;
-![AP8](//images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
+![AP8](https://images.ctfassets.net/alneenqid6w5/3Rp2Dt49HkCwzFHjScLjV/a83399b2270e638f3d480e4f885cc8d6/AP8.PNG)
 5. Certifique-se que a pergunta *"Will payments associated with this Merchant ID be processed exclusively in China?"* está marcada com __a opção default (No)__.
-![AP9](//images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
+![AP9](https://images.ctfassets.net/alneenqid6w5/Sp9juhAMuWRA1vHgk6pZ9/8eda99f583b842bb94a52d729fd4066a/AP9.PNG)
 
 Em seguida, você será direcionado para uma tela com instruções sobre a criação do CSR (Certificate Signing Request). 
 
@@ -81,9 +81,9 @@ Com o {{merchantID}}.csr. que você recebeu, finalize:
 1. Clique em __Choose File__; 
 2. Selecione o __arquivo CSR__ desejado;
 3. Clique no botão __Continue__;
-![AP10](//images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
+![AP10](https://images.ctfassets.net/alneenqid6w5/3hECpP7iFDlIO6PatZCOEY/d38bfb6be71f867c1f3182616a6fcb4b/AP10.PNG)
 4. Clique em __Download__; 
-![AP11](//images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
+![AP11](https://images.ctfassets.net/alneenqid6w5/5LZH1cD0JOe4dHN1noRbUE/2de89d38d2fde3f870c4274d32092c83/AP11.PNG)
 5. Clique em __Done__.
 
 ## Registrando domínios no Merchant ID
@@ -100,17 +100,17 @@ Por fim, é preciso importar esse arquivo para o sistema da VTEX por meio do Pos
 Confira as instruções:
 
 1. Digite pelo __Merchant ID__ recém-criado na barra de busca;
-![AP12](//images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
+![AP12](https://images.ctfassets.net/alneenqid6w5/4RnNU5b0rsfCpEKkj9dFnj/3ddb803ff21d56c9f54d214d9b8bf56f/AP12.PNG)
 2. Clique no __Merchant ID__ desejado;
 3. No módulo __Merchant Domains__, clique no botão __Add Domain__;
-![AP13](//images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
+![AP13](https://images.ctfassets.net/alneenqid6w5/7pPoN1yAltfTpHQVQRzvb9/61da4650bae649475637cf185a228c4f/AP13.PNG)
 4. Adicione o domínio no campo __Enter the domain you wish to register__; 
 5. Clique em __Save__.
 
 Agora, para fazer o upload do arquivo `.txt` por meio da API, prossiga com as instruções:
 
 1. Clique em __Download__ e não faça nenhuma alteração no arquivo; 
-![AP14](//images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
+![AP14](https://images.ctfassets.net/alneenqid6w5/20a92ocy0wEVTY6zXqfa5w/56b96dc4d0fe44c322065a10af594980/AP14.PNG)
 2. Abra o arquivo `.txt` e __copie__ todo o conteúdo.
 
 Em seguida, inicie uma sessão no Postman. Você realizará uma chamada via POST para a CDN da VTEX:
@@ -122,7 +122,7 @@ Em seguida, inicie uma sessão no Postman. Você realizará uma chamada via POST
 Ao fazer a chamada *POST*, a resposta deve informar que o certificado estará salvo por 60 minutos. Durante esse período, você deve concluir a validação do domínio. 
 
 Agora, volte ao site da Apple. Na mesma tela em que você fez o download do arquivo `.txt`, clique em __Verify__.
-![AP15](//images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
+![AP15](https://images.ctfassets.net/alneenqid6w5/2rG0fF8Bvo5TqsDqAHqL4j/92c7bc8601572cd80caf4bea8b101208/AP15.PNG)
 
 Assim, caso o passo a passo seja feito corretamente, o domínio estará registrado com o status __Verified__. Se quiser, você pode repetir todo o processo para registrar mais domínios usando o botão __Add Domain__ na seção __Merchant Domains__.
 
@@ -138,12 +138,12 @@ Atenção: recomendamos que a senha seja fácil de lembrar, já que ela será in
 
 1. Acesse o módulo __Certificates, Identifiers & Profilers__;
 2. No menu do lado esquerdo, clique em __Identifiers__;
-3. No canto superior direito, filtre por __Merchant IDs__;    ![AP16](//images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
+3. No canto superior direito, filtre por __Merchant IDs__;    ![AP16](https://images.ctfassets.net/alneenqid6w5/5XBSpBP20NFq5HRQKpxQjS/e8f662462087cd43d0c8a5b7f7bdd4c3/AP16.PNG)
 4. Selecione o __Merchant Identifier__ desejado;
-5. Clique em __Create Certificate__;    ![AP17](//images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
+5. Clique em __Create Certificate__;    ![AP17](https://images.ctfassets.net/alneenqid6w5/33Mm1jF8PBhIjj7X7LjAxc/181c7490381f754c0580d847da2c120d/AP17.PNG)
 6. Siga as __instruções__ expostas na tela para criar um certificado;
-7. Clique no botão __Continue__;    ![AP18](//images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
-8. Clique em __Download__.    ![AP19](//images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
+7. Clique no botão __Continue__;    ![AP18](https://images.ctfassets.net/alneenqid6w5/zY9tykCxck32wV3c9w1V8/bcacdf765e787fb104b8f7f70677c2df/AP18.PNG)
+8. Clique em __Download__.    ![AP19](https://images.ctfassets.net/alneenqid6w5/3VMp9diaN7L7M8dsopkWQo/6fa0b54d0a7310bfb7dd0cd183c2a56e/AP19.PNG)
 
 Agora, quando o arquivo for baixado, clique duas vezes para instalá-lo no Keychain Access.
 
@@ -151,7 +151,7 @@ Em seguida, continue com o passo a passo:
 
 1. Abra o __Keychain Access__; 
 2. Localize o __certificado__ criado no passo quatro acima;
-3. Com o botão direito do mouse, clique no ícone __Chave__; ![AP20](//images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
+3. Com o botão direito do mouse, clique no ícone __Chave__; ![AP20](https://images.ctfassets.net/alneenqid6w5/1PqNUvHOaSVXkc4FfeMIEQ/cc421cbd0e0cfaff6f7763c861d84baf/AP20.PNG) 
 4. Clique em __Export__;
 5. Nomeie o __certificado__; 
 6. Selecione o formato de exportação __.p12__; 
diff --git a/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md b/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md
index d6f002adb..d73a37f3a 100644
--- a/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md
+++ b/docs/tutorials/pt/setting-up-payments-with-easypay-marketplace.md
@@ -47,7 +47,7 @@ As informações de configuração estão divididas em quatro seções:
 - [Personalização do Checkout easypay (opcional)](#personalizacao-do-checkout-easypay)
 - [Modo sandbox](#modo-sandbox)
 
-![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+![easypay_pt_1](https://images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
 
 <div class="alert alert-warning" role="alert">Você deve realizar as configurações abaixo no <a href="https://backoffice.easypay.pt/">ambiente easypay</a>. O controle destas configurações é de responsabilidade da easypay, e portanto, a VTEX não garante que os passos abaixo estejam atualizados permanentemente. Utilize este documento como uma referência e consulte sua conta no <a href="https://backoffice.easypay.pt/">ambiente easypay</a> para informações atualizadas.</div>
 
@@ -59,34 +59,34 @@ __Key ID e Key Value__: valor e ID da chave easypay.
 
    <ui>1. No [ambiente easypay](https://backoffice.easypay.pt/), clique no logotipo da easypay localizado no canto superior esquerdo da tela, e na seta da conta <b>Marketplace</b>.</ui>
 
-![easypay_pt_10](//images.ctfassets.net/alneenqid6w5/4EEjKGvGS9CtKtpKoIxM6P/e872f7e1484e7498288ac9c214572261/easypay_pt_10.PNG)
+![easypay_pt_10](https://images.ctfassets.net/alneenqid6w5/4EEjKGvGS9CtKtpKoIxM6P/e872f7e1484e7498288ac9c214572261/easypay_pt_10.PNG)
 
    <ui>2. Acesse <b>Web Services > Configuração API 2.0</b>.</ui>
 
    <ui>3. No menu <b>Alias</b>, opção <b>Criar Dados de Pagamentos</b>, clique em <b>Chaves</b>.</ui>
 
-![easypay_pt_11](//images.ctfassets.net/alneenqid6w5/76UJMX2vIty0CSYqHSyvRM/25620b17b9a968615a66e71505e81c65/easypay_pt_11.png)
+![easypay_pt_11](https://images.ctfassets.net/alneenqid6w5/76UJMX2vIty0CSYqHSyvRM/25620b17b9a968615a66e71505e81c65/easypay_pt_11.png)
 
    <ui>4. Copie e salve as informações <b>ID</b> e <b>Chave</b>. Caso deseje criar uma nova chave, clique em <b>+ Nova</b>.</ui>
 
-![easypay_pt_12](//images.ctfassets.net/alneenqid6w5/61bArIKoWC0mVXu8WmRlq7/ca541fe6220d0e6b1f74bf7816fe18a7/easypay_pt_12.PNG)
+![easypay_pt_12](https://images.ctfassets.net/alneenqid6w5/61bArIKoWC0mVXu8WmRlq7/ca541fe6220d0e6b1f74bf7816fe18a7/easypay_pt_12.PNG)
 
 __Merchant account UID__: identificação da conta do comerciante onde serão depositados os valores das compras dos produtos efetuados na loja. Caso não haja uma conta comerciante separada, é possível utilizar o “Account UID” da conta de pagamentos.
 
    <ui>1. No [ambiente easypay](https://backoffice.easypay.pt/), clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois na conta “COMERCIANTE 1”, clique na seta.</ui>
 
-![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+![easypay_pt_5](https://images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
 
    <ui>2. Copie e salve as informações do __Account UID__.</ui>
 
-![easypay_pt_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/084650f9a54f09ac4466c7c0c52e6ba8/easypay_pt_6.PNG)
+![easypay_pt_6](https://images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/084650f9a54f09ac4466c7c0c52e6ba8/easypay_pt_6.PNG)
 
 __Margin account UID__: identificação da conta de margens. 
 
 1. No menu lateral do [ambiente easypay](https://backoffice.easypay.pt/), clique em __Beneficiário__.
 2. Copie as informações e salve as informações do __Account UID__ disponíveis em __Conta de Margens__.
 
-![easypay_pt_13](//images.ctfassets.net/alneenqid6w5/6SjwHG131w2wUNlXLFcCD3/2853c1435b96a9be0f442236d36039c0/easypay_pt_13.PNG)
+![easypay_pt_13](https://images.ctfassets.net/alneenqid6w5/6SjwHG131w2wUNlXLFcCD3/2853c1435b96a9be0f442236d36039c0/easypay_pt_13.PNG)
 
 __Refund account ID e Refund account key__: easypay refund keys ID e value.
 
@@ -94,21 +94,21 @@ __Refund account ID e Refund account key__: easypay refund keys ID e value.
 
    <ui>2. No menu <b>Alias</b>, opção <b>Conta de margens</b>, clique em <b>Chaves</b>.</b>.</ui>
 
-![easypay_pt_14](//images.ctfassets.net/alneenqid6w5/3Llo906P3snImorgYKdsEn/5df8f470383b6e45032959a3707fa399/easypay_pt_14.PNG)
+![easypay_pt_14](https://images.ctfassets.net/alneenqid6w5/3Llo906P3snImorgYKdsEn/5df8f470383b6e45032959a3707fa399/easypay_pt_14.PNG)
 
    <ui>3. Clique em <b>+ Nova</b>.</ui>
 
-![easypay_pt_15](//images.ctfassets.net/alneenqid6w5/3CQJbQd6HywrS4FVMNzrIp/6cfaca92ba1aa114173cc97862d325ac/easypay_pt_15.PNG)
+![easypay_pt_15](https://images.ctfassets.net/alneenqid6w5/3CQJbQd6HywrS4FVMNzrIp/6cfaca92ba1aa114173cc97862d325ac/easypay_pt_15.PNG)
 
    <ui>4. Preencha o campo <b>Nome</b> com <b>Refund Account</b>.</ui>
 
-![easypay_pt_16](//images.ctfassets.net/alneenqid6w5/28yf4dj3pbum7HuzvO7FHH/49c04507ba1eb16fa85c6964786d50f5/easypay_pt_16.png)
+![easypay_pt_16](https://images.ctfassets.net/alneenqid6w5/28yf4dj3pbum7HuzvO7FHH/49c04507ba1eb16fa85c6964786d50f5/easypay_pt_16.png)
 
    <ui>5. Clique em <b>Salvar</b>.</ui>
 
    <ui>6. Copie e salve as informações <b>ID</b> e <b>Chave</b>.</ui>
 
-![easypay_pt_17](//images.ctfassets.net/alneenqid6w5/4Syc7o7Twuasd3uFyw9F0W/b22ae772f368d8e25db2723ff88b5276/easypay_pt_17.png)
+![easypay_pt_17](https://images.ctfassets.net/alneenqid6w5/4Syc7o7Twuasd3uFyw9F0W/b22ae772f368d8e25db2723ff88b5276/easypay_pt_17.png)
 
 <div class="alert alert-warning" role="alert">Os reembolsos são debitados diretamente de uma conta pertencente ao marketplace. Posteriormente, o marketplace deve solicitar ao seller o valor reembolsado.</div>
 
@@ -116,7 +116,7 @@ __Refund account ID e Refund account key__: easypay refund keys ID e value.
 
 Nesta seção, você deve indicar se a sua loja utilizará pagamentos assíncronos, síncronos ou ambos. Acesse a documentação easypay para verificar os [métodos de pagamentos](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) disponíveis e suas respectivas [siglas](https://docs.quality-utility.aws.easypay.pt/checkout/reference) de identificação.
 
-![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+![easypay_pt_7](https://images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
 
 __Tipos de pagamento assíncronos aceites__: métodos de pagamento assíncronos disponíveis para o cliente. Preencha apenas com as siglas dos tipos de Assíncronos, separados por vírgula, sem pontos e sem espaços.
 
@@ -148,7 +148,7 @@ Exemplo:
 
 A easypay possui um layout de Checkout nativo configurado no app. Veja abaixo:
 
-![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+![easypay_pt_8](https://images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
 
 Caso deseje realizar algum tipo de personalização no Checkout nativo da easypay, preencha um ou mais dos campos nesta seção:
 
@@ -198,7 +198,7 @@ Para configurar o webhook da easypay, sig os passos abaixo:
 
    <ui>1. No [ambiente easypay](https://backoffice.easypay.pt/), clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois clique na seta da conta marketplace.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
    <ui>2. Acesse __Web Services > Configuração URL__.</ui>
 
@@ -206,7 +206,7 @@ Para configurar o webhook da easypay, sig os passos abaixo:
 
 `https://{nome-da-sua-conta}.myvtex.com/_v/labsitpartnerpt.payment-provider-easypay/webhook`
 
-![easypay_pt_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/5724ef2676c10b5f1eff6594eafb5412/easypay_pt_9.PNG)
+![easypay_pt_9](https://images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/5724ef2676c10b5f1eff6594eafb5412/easypay_pt_9.PNG)
 
 <div class="alert alert-warning" role="alert">Caso haja mais de uma conta de pagamento em seu marketplace, adicione um link para cada uma das contas existentes.</div>
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md b/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md
index db45677d2..d2e94ba28 100644
--- a/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md
+++ b/docs/tutorials/pt/setting-up-payments-with-easypay-seller.md
@@ -45,7 +45,7 @@ Após realizar a instalação do app Easypay Seller Account, você deve configur
 
 <blockquote><ui>- <b>Easypay Account UID</b>: identificação de sua conta seller onde serão depositados os valores das compras dos produtos efetuados na loja. Para obter esta informação, acesse o <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da Easypay localizado no canto superior da tela, e depois na conta desejada. Copie e salve a informação <b>Account UID</b>.</ui> 
 
-![easypay_pt_18](//images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/e9218fcccf92ed76e45024aa1c4c2285/easypay_pt_18.PNG)
+![easypay_pt_18](https://images.ctfassets.net/alneenqid6w5/72jPh8mwBcEqbtiCBU09Bm/e9218fcccf92ed76e45024aa1c4c2285/easypay_pt_18.PNG)
 
 <blockquote><ui>4. Clique em <b>Salvar</b>.</ui>
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-easypay.md b/docs/tutorials/pt/setting-up-payments-with-easypay.md
index bc4ee41b8..2d388d762 100644
--- a/docs/tutorials/pt/setting-up-payments-with-easypay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-easypay.md
@@ -48,7 +48,7 @@ As informações de configuração estão divididas em quatro seções:
 - [Personalização do Checkout easypay (opcional)](#personalizacao-do-checkout-easypay)
 - [Modo sandbox](#modo-sandbox)
 
-![easypay_pt_1](//images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
+![easypay_pt_1](https://images.ctfassets.net/alneenqid6w5/5SQRO4e7bYL1o8CG383UBE/03f939e9444e2655b4b9b540a4e521cc/easypay_pt_1.png)
 
 <div class="alert alert-warning" role="alert">Você deve realizar as configurações abaixo no <a href="https://backoffice.easypay.pt/">ambiente easypay</a>. O controle destas configurações é de responsabilidade da easypay, e portanto, a VTEX não garante que os passos abaixo estejam atualizados permanentemente. Utilize este documento como uma referência e consulte sua conta no <a href="https://backoffice.easypay.pt/">ambiente easypay</a> para informações atualizadas.</div>
 
@@ -60,25 +60,25 @@ __Key ID e Key Value__: valor e ID da chave easypay.
 
 <blockquote><ui>1. No <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da easypay localizado no canto superior esquerdo da tela, e na seta da conta desejada.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
 <blockquote><ui>2. Acesse <b>Web Services > Configuração API 2.0 > Chaves</b>.</ui>
 
-![easypay_pt_3](//images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/912dd97df028290e81d6f90057093878/easypay_pt_3.PNG)
+![easypay_pt_3](https://images.ctfassets.net/alneenqid6w5/3Qrv6zVnD0aUq4bqHXgrlk/912dd97df028290e81d6f90057093878/easypay_pt_3.PNG)
 
 <blockquote><ui>3. Copie e salve as informações <b>ID</b> e <b>Chave</b>.</ui>
 
-![easypay_pt_4](//images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/849733bfcb8535a272d38c08c39138d2/easypay_pt_4.PNG)
+![easypay_pt_4](https://images.ctfassets.net/alneenqid6w5/32OyO0qBLXPTJ0aZpXsQIv/849733bfcb8535a272d38c08c39138d2/easypay_pt_4.PNG)
 
 __Merchant account UID__: identificação da conta do comerciante onde serão depositados os valores das compras dos produtos efetuados na loja. Caso não haja uma conta comerciante separada, é possível utilizar o “Account UID” da conta de pagamentos.
 
 <blockquote><ui>1. No <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois na conta “COMERCIANTE 1”, clique na seta.</ui>
 
-![easypay_pt_5](//images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
+![easypay_pt_5](https://images.ctfassets.net/alneenqid6w5/gQE8fL64YRCCggxVZB7qX/8e130d01b3cc65871f540233b1693df5/easypay_pt_5.PNG)
 
 <blockquote><ui>2. Copie e salve as informações do <b>Account UID</b>.</ui>
 
-![easypay_pt_6](//images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/084650f9a54f09ac4466c7c0c52e6ba8/easypay_pt_6.PNG)
+![easypay_pt_6](https://images.ctfassets.net/alneenqid6w5/3S2dkHv1WmJSyAVVn3salh/084650f9a54f09ac4466c7c0c52e6ba8/easypay_pt_6.PNG)
 
 __Margin account UID__: identificação da conta de margens. 
 
@@ -90,7 +90,7 @@ __Refund account ID e Refund account key__: caso não exista conta específica d
 
 Nesta seção, você deve indicar se a sua loja utilizará pagamentos assíncronos, síncronos ou ambos. Acesse a documentação easypay para verificar os [métodos de pagamentos](https://docs.quality-utility.aws.easypay.pt/concepts/payment-methods) disponíveis e suas respectivas [siglas](https://docs.quality-utility.aws.easypay.pt/checkout/reference) de identificação.
 
-![easypay_pt_7](//images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
+![easypay_pt_7](https://images.ctfassets.net/alneenqid6w5/2Im2zLusDEAguft1GN8uf3/216d2af1607b93c016263a0e59110736/easypay_pt_7.PNG)
 
 __Tipos de pagamento assíncronos aceites__: métodos de pagamento assíncronos disponíveis para o cliente. Preencha apenas com as siglas dos tipos de Assíncronos, separados por vírgula, sem pontos e sem espaços.
 
@@ -122,7 +122,7 @@ Exemplo:
 
 A easypay possui um layout de Checkout nativo configurado no app. Veja abaixo:
 
-![easypay_pt_8](//images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
+![easypay_pt_8](https://images.ctfassets.net/alneenqid6w5/1xcsW6xpPx79OOnA2dB1zw/cfa4f96a4bfb561424245c9a119f4ed2/easypay_pt_8.PNG)
 
 Caso deseje realizar algum tipo de personalização no Checkout nativo da easypay, preencha um ou mais dos campos nesta seção:
 
@@ -174,7 +174,7 @@ Para configurar o webhook da easypay, sig os passos abaixo:
 
 <blockquote><ui>1. No <a href="https://backoffice.easypay.pt/">ambiente easypay</a>, clique no logotipo da easypay localizado no canto superior esquerdo da tela, e depois clique na seta da conta desejada.</ui>
 
-![easypay_pt_2](//images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
+![easypay_pt_2](https://images.ctfassets.net/alneenqid6w5/53o4nqsgB92I5zBOt2gpwv/0f8e3401fc6b08160fede1cc08cc49ec/easypay_pt_2.PNG)
 
 <blockquote><ui>2. Acesse <b>Web Services > Configuração URL</b>.</ui>
 
@@ -182,7 +182,7 @@ Para configurar o webhook da easypay, sig os passos abaixo:
 
 `https://{nome-da-sua-conta}.myvtex.com/_v/easypaypartnerpt.payment-provider-easypay/webhook`
 
-![easypay_pt_9](//images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/5724ef2676c10b5f1eff6594eafb5412/easypay_pt_9.PNG)
+![easypay_pt_9](https://images.ctfassets.net/alneenqid6w5/2f7UMqQzrIqNbtslGCFxyC/5724ef2676c10b5f1eff6594eafb5412/easypay_pt_9.PNG)
 
 <blockquote><ui>4. Clique em <b>Submeter</b>.</ui>
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-itau-rede.md b/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
index 72e0cc24b..cd7732fea 100644
--- a/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
+++ b/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
@@ -35,27 +35,27 @@ Para obter as credenciais __Chave de aplicação__ e __Token de aplicação__ ne
 
 <blockquote><ui>2. Selecione a conta na qual deseja transacionar pagamentos na VTEX e clique em <b>Aplicar</b>. Guarde o número da conta, pois ele deve ser utilizado no campo <b>Chave de aplicação</b> na seção <a href="#configurar-itau-rede-na-vtex">Configurar Itaú Rede na VTEX</a>.</ui> 
 
-![Itaú Rede_1](//images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
+![Itaú Rede_1](https://images.ctfassets.net/alneenqid6w5/gooU2CGrEsArx16vHLBAw/af69b2edd0c9361563fa4b624941f2d0/Itau_Rede_1.PNG)
 
 <blockquote><ui>3. Após a tela atualizar para a conta desejada, no menu <b>para vender</b>, selecione a opção <b>e-commerce</b>.</ui>
 
-![Itaú Rede_2](//images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
+![Itaú Rede_2](https://images.ctfassets.net/alneenqid6w5/3VB0bwzReQKt2zjXnLHltx/11bfb6b935d77828b0a243dc90ea55fd/Itau_Rede_2.PNG)
 
 <blockquote><ui>4. Na página <b>e-commerce</b>, clique no card <b>chave de integração</b>.</ui>
 
-![Itaú Rede_3](//images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
+![Itaú Rede_3](https://images.ctfassets.net/alneenqid6w5/AxbQNB9snirJxN4zOV7qT/b8441d7cc910a99448ea9f4c9724612e/Itau_Rede_3.png)
 
 <blockquote><ui>5. Após ler as informações da chave de integração, clique em <b>li, estou ciente</b>.</ui>
 
-![Itaú Rede_4](//images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
+![Itaú Rede_4](https://images.ctfassets.net/alneenqid6w5/BU5ydvg5BxaY9KRPHevzv/73a8d3ed6e2bf9e9625b69430f8ae2d6/Itau_Rede_4.png)
 
 <blockquote><ui>6. Clique no botão <b>gerar nova chave</b>.</ui>
 
-![Itaú Rede_5](//images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
+![Itaú Rede_5](https://images.ctfassets.net/alneenqid6w5/kZGFItLuWLgm6lc9Twrhb/266384a3037afaeed2b8b04a5efb9a87/Itau_Rede_5.png)
 
 <blockquote><ui>7. Verifique as informações descritas na janela <b>gerar nova chave de integração</b> e clique em <b>gerar nova chave</b>.</ui>
 
-![Itaú Rede_6](//images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
+![Itaú Rede_6](https://images.ctfassets.net/alneenqid6w5/diZYL8GRAhwcL5sX7IQtn/24789d56142d14bc756ecd8c02616135/Itau_Rede_6.png)
 
 <blockquote><ui>8. Após a criação da nova chave, clique em <b>copiar</b> e preserve a informação em um local seguro. Esta chave deverá ser utilizada no campo <b>Token de aplicação</b> na seção <a href="#configurar-itau-rede-na-vtex">Configurar Itaú Rede na VTEX</a>.</ui>
 
diff --git a/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md b/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md
index 38b296041..dc8b32b9e 100644
--- a/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md
+++ b/docs/tutorials/pt/setting-up-personal-data-on-the-users-screen.md
@@ -21,18 +21,18 @@ Para acessá-la, siga os passos abaixo:
 
 1. Na topbar do Admin, no canto direito, clique no botão com a letra inicial do seu nome;
 2. Clique na opção __Configurações de usuário__.  
-![Opção Configurações de usuário User Management PT](//images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/44c8a24a6ac48c1aeedc6c8adba9f908/Op____o_Configura____es_de_usu__rio_User_Management_PT.png)
+![Opção Configurações de usuário User Management PT](https://images.ctfassets.net/alneenqid6w5/t0xviJchq6iWQbtJc1OAX/44c8a24a6ac48c1aeedc6c8adba9f908/Op____o_Configura____es_de_usu__rio_User_Management_PT.png)
 
 Há duas opções no menu:
 
 - Em __Pessoal__ você pode ver seu nome, seu e-mail cadastrado no Admin e o número do seu telefone.  
-![Configuração Pessoal User Management PT](//images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/0dec6b4bc84d23a354515d5e3b0af587/Configura____o_Pessoal_User_Management_PT.png)
+![Configuração Pessoal User Management PT](https://images.ctfassets.net/alneenqid6w5/2iCA8XwoUatxRcW1WWQuwo/0dec6b4bc84d23a354515d5e3b0af587/Configura____o_Pessoal_User_Management_PT.png)
   - Ao clicar em __Nome__, você terá a opção de editar seu nome e sobrenome.  
-  ![Configuração Nome User Management PT](//images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/5f20a76c8125496df3ae088cc96a26d5/Configura____o_Nome_User_Management_PT.png)
+  ![Configuração Nome User Management PT](https://images.ctfassets.net/alneenqid6w5/3rW547lV2D4sMVEiESj9uZ/5f20a76c8125496df3ae088cc96a26d5/Configura____o_Nome_User_Management_PT.png)
   - Ao clicar em __Número de celular__, você terá a opção de editar seu número de celular com o código do país.  
-  ![Configuração Celular User Management PT](//images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/be07018ea8cb2d69ababafa7bf136c35/Configura____o_Celular_User_Management_PT.png)
+  ![Configuração Celular User Management PT](https://images.ctfassets.net/alneenqid6w5/7i4UTwnhDRataNtaPzEpUw/be07018ea8cb2d69ababafa7bf136c35/Configura____o_Celular_User_Management_PT.png)
 - Em __Autenticação__, você encontra as opções de modificação de senha, gerenciamento da verificação em 2 passos (2FA) para seu login no Admin VTEX e gerenciamento de sessões. Veja abaixo quais são essas opções.  
-![Configuração Autenticação User Management PT](//images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/809706ede591d828432722b73feb06ad/Configura____o_Autentica____o_User_Management_PT.png)
+![Configuração Autenticação User Management PT](https://images.ctfassets.net/alneenqid6w5/hqW76p2oJaFT3EDHDzzbA/809706ede591d828432722b73feb06ad/Configura____o_Autentica____o_User_Management_PT.png)
 
 ## Verificação em 2 passos
 
@@ -50,4 +50,4 @@ Aqui você deve configurar o aplicativo que fornecerá a chave de autenticação
 
 Veja em detalhes como configurar o aplicativo no artigo [Habilitar login por autenticação de 2 fatores](https://help.vtex.com/pt/tutorial/habilitar-login-por-autenticacao-de-2-fatores#habilitar-o-2fa-por-aplicativo).
 
-![Configuração Verificação em 2 passos User Management PT](//images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2f8ad9e2ee454b407adb333d0af7dfd7/Configura____o_Verifica____o_em_2_passos_User_Management_PT.png)
+![Configuração Verificação em 2 passos User Management PT](https://images.ctfassets.net/alneenqid6w5/6sAdQOMRYWiXa9gmHo4lsv/2f8ad9e2ee454b407adb333d0af7dfd7/Configura____o_Verifica____o_em_2_passos_User_Management_PT.png)
diff --git a/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md b/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
index f2bb65564..bda4b0976 100644
--- a/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
@@ -78,11 +78,11 @@ No menu principal do Admin, acesse __Preços__ e escolha a opção __Lista de pr
 
 No filtro da busca, insira os nomes das tabelas criadas no __Master Data__.
 
-![Filters](//images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
+![Filters](https://images.ctfassets.net/alneenqid6w5/4l7cEOha360ceaegCA4Ws6/17ea17f13d6dd9e399f07c4cefe1888a/Filters.png)
 
 As tabelas de preço são mostradas como colunas da lista de preços, assim como as políticas comerciais.
 
-![Prices](//images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
+![Prices](https://images.ctfassets.net/alneenqid6w5/31kElv6oD6KksC8wyUoCgU/815d607e3cdcd2d7c15239d202a81ad0/Prices.png)
 
 Para atualizar o preço fixo em uma tabela específica, clique na coluna dessa tabela e depois em __Definir preços fixos__. 
 
@@ -99,7 +99,7 @@ Quando um usuário da sua loja não está logado, os preços mostrados a ele sã
 Mas se o usuário estiver logado, ele verá os preços correspondentes à tabela de preços à qual o email dele estiver associado.
 
 Por exemplo, estes dois clientes estão atrelados a tabelas de preços diferentes:
-![Clients](//images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
+![Clients](https://images.ctfassets.net/alneenqid6w5/4YanVck2GswcKKEEamO6gs/d1a2bc5603716c485dd000239a49fb41/Clients.png)
 
 Quando o cliente Daniel, que está na tabela Silver, estiver logado na loja, ele verá os preços definidos nessa tabela. A mochila do exemplo acima aparecerá com o valor de R$ 50,00.
 Já o cliente Breno, que está na tabela Gold, verá os preços definidos nessa outra tabela. Para ele a mochila custará R$ 60,50.
diff --git a/docs/tutorials/pt/setting-up-shipment.md b/docs/tutorials/pt/setting-up-shipment.md
index 984e2b71a..ec8295e56 100644
--- a/docs/tutorials/pt/setting-up-shipment.md
+++ b/docs/tutorials/pt/setting-up-shipment.md
@@ -27,7 +27,7 @@ A primeira caixinha com tempo total de __2 dias__ irá esperar o item represent
 
 O período considera T = 0 como a data do pedido.
 
-![Configuração em estoque e entrega ](//images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/3dd5e11e0c89ad2285777f6a0a8eadc5/Configura____o_em_estoque_e_entrega_PT.png)
+![Configuração em estoque e entrega ](https://images.ctfassets.net/alneenqid6w5/2lvFxIIkeZtgpqm66yRiyf/3dd5e11e0c89ad2285777f6a0a8eadc5/Configura____o_em_estoque_e_entrega_PT.png)
 
 ## Como configurar a remessa
 1. No Admin VTEX, acesse **Configurações da loja > Envio > Configurações**, ou digite *Envio* na barra de busca no topo da página e selecione *Configurações da loja / Envio*.  
diff --git a/docs/tutorials/pt/setting-up-sms-password-recovery.md b/docs/tutorials/pt/setting-up-sms-password-recovery.md
index f8ab6b821..983c69e9a 100644
--- a/docs/tutorials/pt/setting-up-sms-password-recovery.md
+++ b/docs/tutorials/pt/setting-up-sms-password-recovery.md
@@ -26,13 +26,13 @@ Dito isso, confira o passo a passo de como configurar essa modalidade:
 1. Acesse __Central de Mensagens__.
 2. Clique em __Templates__.
 
-  ![5NrtBpFRTxInFl4aY2FrVz-pt](//images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/554312ca709ec61b03aee1fed2f16e24/5NrtBpFRTxInFl4aY2FrVz-pt.png)
+  ![5NrtBpFRTxInFl4aY2FrVz-pt](https://images.ctfassets.net/alneenqid6w5/1l0OsDNW7teR6iaGoNgei0/554312ca709ec61b03aee1fed2f16e24/5NrtBpFRTxInFl4aY2FrVz-pt.png)
 
 3. Clique no template __Password Recovery__.
 4. Clique na aba __SMS__.
 5. Selecione a opção __“Ativar envio de SMS?”__
 
-  ![password-recovery-sms-tab-pt](//images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/9199293f8290a94fbc4cf47c9cc2dd4a/password-recovery-sms-tab-pt.gif)
+  ![password-recovery-sms-tab-pt](https://images.ctfassets.net/alneenqid6w5/6bGbc4Wo9IJcKld5wBXYoi/9199293f8290a94fbc4cf47c9cc2dd4a/password-recovery-sms-tab-pt.gif)
 
   *No momento em que o usuário clica em “Ativar envio de SMS”, a plataforma apresenta as demais configurações de envio.*
 
@@ -40,7 +40,7 @@ Dito isso, confira o passo a passo de como configurar essa modalidade:
 7. Preencha o campo __Destination__ com a variável `{{_accountInfo.Telephone}}`.
 8. Preencha o campo __Message Text__ com o conteúdo da mensagem. As informações `Nome:{{name}}`, `Login:{{login}}` e `Senha: {{senha}}` são essenciais.
 
-  ![password-recovery-sms-fields-pt](//images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ec001c43cf655f023b30db5a0bba2b29/password-recovery-sms-fields-pt.png)
+  ![password-recovery-sms-fields-pt](https://images.ctfassets.net/alneenqid6w5/7D17OjBCwC4FWnpMJ5hlys/ec001c43cf655f023b30db5a0bba2b29/password-recovery-sms-fields-pt.png)
 
 9. Revise o conteúdo do SMS em __Preview__.
 10. Clique em __Salvar __.
diff --git a/docs/tutorials/pt/setting-up-the-critical-stock-alert.md b/docs/tutorials/pt/setting-up-the-critical-stock-alert.md
index 5aaa013fb..5af720806 100644
--- a/docs/tutorials/pt/setting-up-the-critical-stock-alert.md
+++ b/docs/tutorials/pt/setting-up-the-critical-stock-alert.md
@@ -23,7 +23,7 @@ O alerta de estoque crítico é uma funcionalidade de logística que tem o objet
 2. Preencha o campo de **Alerta de estoque crítico** com a quantidade de itens ou porcentagem de estoque desejada.
 3. Clique em **Salvar**.
 
-![alerta-estoque-critico pt](//images.ctfassets.net/alneenqid6w5/4NNqAy9PJ6wUQsywOyE0UK/b033e0752c942adfbe5bab4e616acb63/alerta-estoque-critico_pt.png)
+![alerta-estoque-critico pt](https://images.ctfassets.net/alneenqid6w5/4NNqAy9PJ6wUQsywOyE0UK/b033e0752c942adfbe5bab4e616acb63/alerta-estoque-critico_pt.png)
 
 ## Como funciona o Alerta
 
diff --git a/docs/tutorials/pt/setting-up-the-css-for-the-product-zoom.md b/docs/tutorials/pt/setting-up-the-css-for-the-product-zoom.md
index af68de1d7..f6ccebfb4 100644
--- a/docs/tutorials/pt/setting-up-the-css-for-the-product-zoom.md
+++ b/docs/tutorials/pt/setting-up-the-css-for-the-product-zoom.md
@@ -25,7 +25,7 @@ Abaixo reproduzimos um trecho de CSS que você pode utilizar como ponto de parti
 
 Em seguida, vamos enviar o arquivo CSS salvo para o servidor. Para isso, clique no menu _Configurações&gt; Portal_ dentro do Admin.
 
-![](//images.contentful.com/alneenqid6w5/3uLeF6wpvq4m4Wis48eeE8/4f79bf7753fb25309b670e9ea702a3ad/configuracao_zoom.gif)
+![](https://images.contentful.com/alneenqid6w5/3uLeF6wpvq4m4Wis48eeE8/4f79bf7753fb25309b670e9ea702a3ad/configuracao_zoom.gif)
 
 Na janela que se abrirá à direita, clique no botão **Adicionar**.
 
@@ -33,4 +33,4 @@ Em seguida, localize o arquivo CSS salvo acima e envie-o para o servidor clicand
 
 Então, o seu arquivo será lista na janela, conforme a imagem abaixo:
 
-![](//images.contentful.com/alneenqid6w5/2pWBIqL3So2wm04oU8CyQ8/ab9f623fd28f15e2708cc3fcbecafe03/gerenciador_arq_css-560x373.jpg)
+![](https://images.contentful.com/alneenqid6w5/2pWBIqL3So2wm04oU8CyQ8/ab9f623fd28f15e2708cc3fcbecafe03/gerenciador_arq_css-560x373.jpg)
diff --git a/docs/tutorials/pt/setting-up-the-notify-me-option.md b/docs/tutorials/pt/setting-up-the-notify-me-option.md
index 3480c1e5b..57e6e943e 100644
--- a/docs/tutorials/pt/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/pt/setting-up-the-notify-me-option.md
@@ -23,7 +23,7 @@ Quando um produto está fora de [estoque](https://help.vtex.com/pt/tutorial/gere
 
 Veja abaixo um exemplo de como a opção **Avise-me** é exibida em uma loja. Para receber uma notificação quando o item estiver disponível para venda, o cliente deve digitar o nome e o email nos campos destacados e, em seguida, clicar no botão `Enviar`.
 
-![aviseme-pt](//images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/c97a66089cc55b3570f518fd901a139f/image1.png)
+![aviseme-pt](https://images.ctfassets.net/alneenqid6w5/AuBR53LGxrJC0abAyzsIp/c97a66089cc55b3570f518fd901a139f/image1.png)
 
 Assim que o item é reposto no estoque da loja, o sistema envia um email para o cliente automaticamente, informando que o produto já está disponível para compra. 
 
diff --git a/docs/tutorials/pt/setting-up-the-price-range-filter.md b/docs/tutorials/pt/setting-up-the-price-range-filter.md
index 7349af9cf..34ec36778 100644
--- a/docs/tutorials/pt/setting-up-the-price-range-filter.md
+++ b/docs/tutorials/pt/setting-up-the-price-range-filter.md
@@ -20,7 +20,7 @@ Importantíssimas para navegação e procura dos produtos desejados na loja.
 
 O cadastro é simples e pode-se determinar diferentes faixas de preços para categorias, conforme imagem abaixo:
 
-![faixa-de-preço pt](//images.ctfassets.net/alneenqid6w5/2H77Lil1K88GcO4W6CYoy8/5af2211860af12fdcd846fbebabb9c2e/faixa-de-pre__o_pt.png)
+![faixa-de-preço pt](https://images.ctfassets.net/alneenqid6w5/2H77Lil1K88GcO4W6CYoy8/5af2211860af12fdcd846fbebabb9c2e/faixa-de-pre__o_pt.png)
 
 Dentro de Faixas de Preço, clique em “Nova Faixa de Preço” e preencha os campos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
index e0b84398a..a8bd1c120 100644
--- a/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
@@ -25,23 +25,23 @@ Para facilitar, toda a configuração apresentada neste artigo pode ser <a href=
 
 Para configuração manual ou edição de uma meta já existente, o primeiro passo é acessar o Analytics e clicar no botão __Administrador__ no canto inferior esquerdo. Em seguida, ir na opção __Metas__, da coluna "Vista".
 
-![image](//images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/1br6W1yFRuMWoO2wW8Iu04/de2c4c8938a856821b25fde18b2632a7/image.png)
 
 Na tela de administração de metas, opte por criar uma nova ou editar uma já existente.
 
 __No passo 1__ você pode seguir com uma meta de tipo personalizado:
 
-![image](//images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/7GPxGfEoaA2GUqOGA48U2a/3b731dfd468a389813d0da16802df98f/image.png)
 
 __No passo 2__ você pode definir o nome que preferir para a sua meta e um código de posição (de uso interno do Google Analytics). Em tipo, vamos usar "Destino":
 
-![image](//images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/6Sdi6PJ4e4SKiuUSeEgMii/d0f1e7fb597333867e4d56453922847a/image.png)
 
 __No passo 3__ temos as configurações mais sensíveis. Nele configuramos a página que determina a conclusão da meta e o caminho que os clientes vão percorrer para atingi-la.
 
 No campo "Destino" selecione a opção expressão regular e insira a URL da página de pedido concluído: `^/checkout/orderPlaced`
 
-![image](//images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/6lxVMRQt7GWcqqSiCGe40g/177d2cf23b65d5f2134fc389a5646b9b/image.png)
 
 Depois configure o caminho que o cliente vai percorrer até finalizar um pedido. Neste caso, estamos levando em conta que o processo de compra inicia na tela do produto; então meu funil vai servir para medir a quantidade de clientes que acessam essa tela, quantos pedidos foram finalizados e em qual passo os clientes estão desistindo da compra.
 
@@ -54,7 +54,7 @@ Ainda __no passo 3__, então, ative a opção __Funil__ com as etapas a seguir:
 5. __Entrega__: `^/checkout/(\?.*)?#/shipping$`
 6. __Pagamento__: `^/checkout/(\?.*)?#/payment$`
 
-![image](//images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
+![image](https://images.ctfassets.net/alneenqid6w5/4gzupPXI4w0gYWISUaCUQS/efb5f7cd239cae3cfd992b2b649e58b9/image.png)
 
 Uma forma de verificar se a meta está configurada corretamente é usar o link "Verifique essa meta". O Google vai gerar uma simulação da conversão da meta nos últimos 7 dias.
 
diff --git a/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md b/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
index 5888cf310..174b7dcdd 100644
--- a/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
@@ -25,7 +25,7 @@ O ID da forma de pagamento, que será configurada com Juros Simples, é obtido d
 - Acesse a Condição de Pagamento que deseja configurar para usar Juros Simples
 - Copie o último parâmetro da URL, que indica o ID dessa Forma de Pagamento (ver imagem)
 
-![imagem para valer do artigo em português de financial](//images.ctfassets.net/alneenqid6w5/2Q1rgCboSZE7N9hQ5k7qlD/f179a4a58dc9c75a1154b48141d3c003/imagem_para_valer_do_artigo_em_portugu__s_de_financial.png)
+![imagem para valer do artigo em português de financial](https://images.ctfassets.net/alneenqid6w5/2Q1rgCboSZE7N9hQ5k7qlD/f179a4a58dc9c75a1154b48141d3c003/imagem_para_valer_do_artigo_em_portugu__s_de_financial.png)
 
 ## Configurar o tipo de juros usando API
 
diff --git a/docs/tutorials/pt/setting-up-the-voucher-list.md b/docs/tutorials/pt/setting-up-the-voucher-list.md
index 3fba6c038..109e24fa8 100644
--- a/docs/tutorials/pt/setting-up-the-voucher-list.md
+++ b/docs/tutorials/pt/setting-up-the-voucher-list.md
@@ -27,14 +27,14 @@ A configuração depende de dois pontos, listados abaixo.
 
 - O SKU precisa ser configurado para gerar crédito em vale.
 
-![sku-opção-credito-vale pt](//images.ctfassets.net/alneenqid6w5/JLjFssu5Q2awo2UyiuOEQ/2719360144a349ef7fcf68fc96a7dee6/sku-op____o-credito-vale_pt.png)
+![sku-opção-credito-vale pt](https://images.ctfassets.net/alneenqid6w5/JLjFssu5Q2awo2UyiuOEQ/2719360144a349ef7fcf68fc96a7dee6/sku-op____o-credito-vale_pt.png)
 
 
 ## Configurações no Tipo de Lista
 
 A criação desse tipo de lista pede que, nas configurações, a entrega seja marcada como "Valor dos produtos comprados será convertido em Vale Compras". Veja a imagem de exemplo.
 
-![entrega-tipos-lista pt](//images.ctfassets.net/alneenqid6w5/7cX5Qz5CG4gSQuwOUKSy0Y/21687cba7440124b65e6b4be17007191/entrega-tipos-lista_pt.png)
+![entrega-tipos-lista pt](https://images.ctfassets.net/alneenqid6w5/7cX5Qz5CG4gSQuwOUKSy0Y/21687cba7440124b65e6b4be17007191/entrega-tipos-lista_pt.png)
 
 Salve a sua lista após realizadas as demais configurações desejadas.
 
diff --git a/docs/tutorials/pt/setting-up-vtex-instore-logistics.md b/docs/tutorials/pt/setting-up-vtex-instore-logistics.md
index 392c8d8fe..432c4f065 100644
--- a/docs/tutorials/pt/setting-up-vtex-instore-logistics.md
+++ b/docs/tutorials/pt/setting-up-vtex-instore-logistics.md
@@ -21,6 +21,6 @@ A rota de check-in do Checkout chama no seu fluxo o Logistics. O que isso quer d
 
 Após o cadastro de sua(s) lojas(s) no MasterData ([veja aqui como fazer](/pt/tutorial/como-cadastrar-lojas-no-vtex-instore)), você poderá escolher a loja que gostaria de associar a essa doca pelo dropdown conforme a imagem abaixo:
 
-![2017-06-16 16 43 14-VTEX - Logística](//images.contentful.com/alneenqid6w5/2NIbvde6HSK6OUCWUcwigq/879c7de324037ebb2ffbc64d768d7404/2017-06-16_16_43_14-VTEX_-_Log__stica.png)
+![2017-06-16 16 43 14-VTEX - Logística](https://images.contentful.com/alneenqid6w5/2NIbvde6HSK6OUCWUcwigq/879c7de324037ebb2ffbc64d768d7404/2017-06-16_16_43_14-VTEX_-_Log__stica.png)
 
 Para cada loja cadastrada deverá existir uma doca correspondente.
diff --git a/docs/tutorials/pt/sharing-your-store-access-to-google-webmaster-tools.md b/docs/tutorials/pt/sharing-your-store-access-to-google-webmaster-tools.md
index 752c1d1ba..713a0dcb7 100644
--- a/docs/tutorials/pt/sharing-your-store-access-to-google-webmaster-tools.md
+++ b/docs/tutorials/pt/sharing-your-store-access-to-google-webmaster-tools.md
@@ -19,18 +19,18 @@ Para possibilitar um trabalho mais eficiente de nosso time de consultoria e oper
 
 Após acessar sua conta, você será direcionado à lista de seus sites, assim basta selecionar o site cujo acesso deseja compartilhar, clicando sobre o link do site.
 
-![web1](//images.contentful.com/alneenqid6w5/3sjO5gPjcA2uCms8KskmU4/484df9e2d251c709169c88a626e2b575/web1.png)
+![web1](https://images.contentful.com/alneenqid6w5/3sjO5gPjcA2uCms8KskmU4/484df9e2d251c709169c88a626e2b575/web1.png)
 
 Assim, agora acessamos o painel administrativo da nossa página. Diversas opções são possíveis no menu lateral esquerdo, porém para compartilhar o acesso, devemos selecionar a engrenagem no menu superior e clicar em **Usuários e proprietários de site**.
 
-![web2](//images.contentful.com/alneenqid6w5/kk9u4aygFyAG4EkKsYIw0/67bd8a6966fafea49f6c50f81d36c49d/web2.png)
+![web2](https://images.contentful.com/alneenqid6w5/kk9u4aygFyAG4EkKsYIw0/67bd8a6966fafea49f6c50f81d36c49d/web2.png)
 
 Será exibida agora a lista dos usuário já autorizados à este site, portanto para adicionarmos um novo usuário basta clicar, na parte superior da tela, sobre o botão **Adicionar Novo Usuário**.
 
-![web3](//images.contentful.com/alneenqid6w5/1MLOKUoQliKsMc88EQUcmK/3e7dc118b07c2f23282ba48e63c1aee0/web3.png)
+![web3](https://images.contentful.com/alneenqid6w5/1MLOKUoQliKsMc88EQUcmK/3e7dc118b07c2f23282ba48e63c1aee0/web3.png)
 
 Após o clique, abre-se um pop-up solicitando como informações o e-mail do usuário a ser adicionado, e o tipo de permissão, Total ou restrita, que este usuário irá receber.
 
-![web4](//images.contentful.com/alneenqid6w5/hINzOyisNy0GyaMSOMEMq/b629abc8ff70a3820ab37f8a57f974e2/web4.png)
+![web4](https://images.contentful.com/alneenqid6w5/hINzOyisNy0GyaMSOMEMq/b629abc8ff70a3820ab37f8a57f974e2/web4.png)
 
 Não se esqueça de clicar em **Adicionar** para salvar.
diff --git a/docs/tutorials/pt/sharpspring-suiteshare.md b/docs/tutorials/pt/sharpspring-suiteshare.md
index cadda81fd..3b7377779 100644
--- a/docs/tutorials/pt/sharpspring-suiteshare.md
+++ b/docs/tutorials/pt/sharpspring-suiteshare.md
@@ -21,29 +21,29 @@ Para realizar a integração, utilize uma das duas formas abaixo:
 
 1. No dashboard, clique em **Ver todas integrações** e em **SharpSrpring**.
 
-   ![SharpSpring_1](//images.ctfassets.net/alneenqid6w5/3GAphuPmnfRLWSwUj6kf2t/9b3a07ed03a91a5c7b56cbf813fd31b8/SharpSpring_1.png)
+   ![SharpSpring_1](https://images.ctfassets.net/alneenqid6w5/3GAphuPmnfRLWSwUj6kf2t/9b3a07ed03a91a5c7b56cbf813fd31b8/SharpSpring_1.png)
 
 2. Acesse **Configurações > Integrações > Marketing > Habilitar**.
 
-   ![SharpSpring_2](//images.ctfassets.net/alneenqid6w5/2mVIrVMqw46gouJObzggSb/e84e232c373a1388f66bd21e99d4e163/SharpSpring_2.png)
+   ![SharpSpring_2](https://images.ctfassets.net/alneenqid6w5/2mVIrVMqw46gouJObzggSb/e84e232c373a1388f66bd21e99d4e163/SharpSpring_2.png)
 
-   ![SharpSpring_3](//images.ctfassets.net/alneenqid6w5/2iyTWPWFwA8knyZVVTvMNz/f8841da59167b18c48f6a81d8a7c0190/SharpSpring_3.png)
+   ![SharpSpring_3](https://images.ctfassets.net/alneenqid6w5/2iyTWPWFwA8knyZVVTvMNz/f8841da59167b18c48f6a81d8a7c0190/SharpSpring_3.png)
 
 O próximo passo é acessar sua conta da **SharpSpring** e fazer login.
 
-![SharpSpring_4](//images.ctfassets.net/alneenqid6w5/2WlxccYGdMlXuhmqndYnZE/f4774b9e268ffb3e1f5439c15413127e/SharpSpring_4.png)
+![SharpSpring_4](https://images.ctfassets.net/alneenqid6w5/2WlxccYGdMlXuhmqndYnZE/f4774b9e268ffb3e1f5439c15413127e/SharpSpring_4.png)
 
 Agora, acesse o menu **Configurações** no canto superior direito.
 
-![SharpSpring_5](//images.ctfassets.net/alneenqid6w5/5Ywk5ubVZNDQi0IpYt2u0Y/7c728729f51983336ce07e02b5c8a856/SharpSpring_5.png)
+![SharpSpring_5](https://images.ctfassets.net/alneenqid6w5/5Ywk5ubVZNDQi0IpYt2u0Y/7c728729f51983336ce07e02b5c8a856/SharpSpring_5.png)
 
 Em **Configurações**, clique em **Configurações API**.
 
-![SharpSpring_6](//images.ctfassets.net/alneenqid6w5/2gzKOi3F2hCvrhHH7LRFOk/29f24870c6c09d3cd9e509550b9c5b37/SharpSpring_6.png)
+![SharpSpring_6](https://images.ctfassets.net/alneenqid6w5/2gzKOi3F2hCvrhHH7LRFOk/29f24870c6c09d3cd9e509550b9c5b37/SharpSpring_6.png)
 
 Agora que você tem acesso às chaves da API, basta selecionar o link que deseja integrar com o CRM (captura) e inserior os códigos dentro da VTEX Assisted Sales (SuiteShare).
 
-![SharpSpring_7](//images.ctfassets.net/alneenqid6w5/5EuuoLIO47LBgF0cKElMdo/6321b7c9b4ce5137efbcc669f80a7a47/SharpSpring_7.png)
+![SharpSpring_7](https://images.ctfassets.net/alneenqid6w5/5EuuoLIO47LBgF0cKElMdo/6321b7c9b4ce5137efbcc669f80a7a47/SharpSpring_7.png)
 
 Pronto! Você acabou de integrar a VTEX Assisted Sales (SuiteShare) com o seu CRM. 
 
diff --git a/docs/tutorials/pt/shipping-options-beta.md b/docs/tutorials/pt/shipping-options-beta.md
index 08cf7e222..5f309b152 100644
--- a/docs/tutorials/pt/shipping-options-beta.md
+++ b/docs/tutorials/pt/shipping-options-beta.md
@@ -93,7 +93,7 @@ Para criar uma opção de envio, siga os passos abaixo:
     - **Frete grátis:** sem custos para o consumidor, não requer configurações adicionais.
 8. Clique no botão `Salvar`.
 
-![opcoes_envio_criacao_pt](//images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/a99720c733f07f383aa9cfcdd9a18e76/opcoes_envio_criacao_pt.png)
+![opcoes_envio_criacao_pt](https://images.ctfassets.net/alneenqid6w5/6TOlNWWBTED41BXemhsvQE/a99720c733f07f383aa9cfcdd9a18e76/opcoes_envio_criacao_pt.png)
 
 ### Editar opção de envio
 
@@ -117,7 +117,7 @@ Além de editar uma opção de envio, no ícone menu <i class="fas fa-ellipsis-v
 
 Uma vez que você tenha opções de envio configuradas, elas vão aparecer em uma listagem em **Configurações da loja > Envio > Opções de envio**, conforme a imagem a seguir:
 
-![opcoes_envio_listagem_pt](//images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/713a7a5fa03c809e2bd0ad8b8abe60f5/opcoes_envio_listagem_pt.png)
+![opcoes_envio_listagem_pt](https://images.ctfassets.net/alneenqid6w5/2MAxFwYr86Y2ErCyo7GRIN/713a7a5fa03c809e2bd0ad8b8abe60f5/opcoes_envio_listagem_pt.png)
 
 A tabela abaixo contém a descrição das colunas apresentadas:
 
diff --git a/docs/tutorials/pt/shipping-policy.md b/docs/tutorials/pt/shipping-policy.md
index b346d2a61..17c0d54b0 100644
--- a/docs/tutorials/pt/shipping-policy.md
+++ b/docs/tutorials/pt/shipping-policy.md
@@ -23,7 +23,7 @@ O conjunto de configurações [logísticas](https://help.vtex.com/pt/tutorial/fu
 
 A imagem abaixo mostra como esses conceitos se relacionam entre si:
 
-![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
+![shipping_strategy_PT](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
 
 **Política de envio** é um conjunto de regras e configurações que definem quais opções de envio serão apresentadas aos clientes no checkout. Quando a plataforma VTEX [calcula o tempo de envio](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) do pedido, as configurações das políticas de envio são consideradas, e algumas das principais são:
 
diff --git a/docs/tutorials/pt/shipping-rate-template.md b/docs/tutorials/pt/shipping-rate-template.md
index b763bc50d..ecb4ef9bf 100644
--- a/docs/tutorials/pt/shipping-rate-template.md
+++ b/docs/tutorials/pt/shipping-rate-template.md
@@ -181,7 +181,7 @@ Para fins de usabilidade de termos, utilizamos em nossa documentação o termo "
 
 Veja abaixo um exemplo de preenchimento dos campos, considerando o formato aceito em cada coluna. 
 
-![modelo_planilhanumerica](//images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
+![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
 
 ## Enviar o arquivo pelo Admin VTEX
 
diff --git a/docs/tutorials/pt/shipping-rates.md b/docs/tutorials/pt/shipping-rates.md
index cdffc8a3c..49b136f27 100644
--- a/docs/tutorials/pt/shipping-rates.md
+++ b/docs/tutorials/pt/shipping-rates.md
@@ -21,7 +21,7 @@ As tarifas de envio são os custos de frete que sua loja oferece aos clientes, e
 O <a href="https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV">custo final do envio</a> para o cliente inclui tarifa de envio, <a href="https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">adicionais de frete</a> e custo de doca com estoque.
 </div>
 
-![Tarifa envio PT](//images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
+![Tarifa envio PT](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
 
 Pelo Admin VTEX, há duas maneiras de cadastrar as tarifas de envio:
 
diff --git a/docs/tutorials/pt/shipping-strategy.md b/docs/tutorials/pt/shipping-strategy.md
index 5be66fc10..b97079ae0 100644
--- a/docs/tutorials/pt/shipping-strategy.md
+++ b/docs/tutorials/pt/shipping-strategy.md
@@ -17,7 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Estratégia de envio é a relação entre estoque, doca e política de envio. A forma que   estoque, doca e política de envio se comunicam definirá a combinação de estrutura para entrega dos pedidos da loja.
 
-![shipping_strategy_PT](//images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
+![shipping_strategy_PT](https://images.ctfassets.net/alneenqid6w5/1LdEuL3gjF12uwFj4ya6OL/c60984b010b96980383798cffad3527f/shipping_strategy_PT.png)
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;">
    <tr class="bb b--muted-3">
diff --git a/docs/tutorials/pt/shopee-integration.md b/docs/tutorials/pt/shopee-integration.md
index 93f7b5332..6fc549324 100644
--- a/docs/tutorials/pt/shopee-integration.md
+++ b/docs/tutorials/pt/shopee-integration.md
@@ -148,7 +148,7 @@ Os Serviços ERP disponibilizam um endpoint para obter o arquivo da etiqueta de
 5. Com a chave de acesso em maõs, faça uma requisição GET no seu provedor com o endpoint do campo `Endpoint`, substituindo `{vtex_order_id}` pelo ID do pedido na VTEX e utilizando no Header a chave de acesso obtida.
 6. Na resposta dessa requisição, no campo `base64Encoded` a etiqueta será disponibilizada no formato base64.
 
-  ![postman etiquetas shopee](//images.ctfassets.net/alneenqid6w5/fXwvkIp7rguIH22t04rAy/de4a888cd831e0f60917c30f23fb5602/postman_etiquetas_shopee.png)
+  ![postman etiquetas shopee](https://images.ctfassets.net/alneenqid6w5/fXwvkIp7rguIH22t04rAy/de4a888cd831e0f60917c30f23fb5602/postman_etiquetas_shopee.png)
 
 7. Selecione o arquivo no campo `base64Encoded`, copie e use um decodificador de arquivos formato base64 para fazer a conversão no formato do arquivo selecionado no campo `Tipo de etiqueta de envio`.
 8. No final da conversão, a etiqueta estará pronta para ser utilizada.
diff --git a/docs/tutorials/pt/shopify-suiteshare.md b/docs/tutorials/pt/shopify-suiteshare.md
index 83fe74320..6741e3fd3 100644
--- a/docs/tutorials/pt/shopify-suiteshare.md
+++ b/docs/tutorials/pt/shopify-suiteshare.md
@@ -21,7 +21,7 @@ Para localizar o script da Suiteshare, acesse **Configurações** no canto supe
 
 Com o script da Suiteshare em mãos, acesse em sua conta Shopify o menu localizado no canto inferior esquerdo **My Store**, depois em **Themes**, clique em **Edit HTML/CSS** conforme a imagem abaixo:
 
-![Shopify - Suiteshare](//images.ctfassets.net/alneenqid6w5/45EPnxpruUgUqIUl9cDR3t/894418df9be3fab2755c2f895fc9145e/Shopify_-_Suiteshare.png)
+![Shopify - Suiteshare](https://images.ctfassets.net/alneenqid6w5/45EPnxpruUgUqIUl9cDR3t/894418df9be3fab2755c2f895fc9145e/Shopify_-_Suiteshare.png)
 
 O próximo passo é acessar no canto esquerdo **Layout**, a opção **Theme Liquid**.
 
diff --git a/docs/tutorials/pt/site-editor-overview.md b/docs/tutorials/pt/site-editor-overview.md
index 44c7b556e..277151a4d 100644
--- a/docs/tutorials/pt/site-editor-overview.md
+++ b/docs/tutorials/pt/site-editor-overview.md
@@ -23,7 +23,7 @@ Site Editor é uma interface gráfica de gerenciamento de conteúdo da sua frent
 
 No Admin VTEX, acesse **Storefront > Site Editor** e confira as principais ferramentas disponíveis na interface gráfica.
 
-![Site Editor - PT](//images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/e526abc990cdf0bfa1d451580e7a8ec2/site-editor-ui-pt.png)
+![Site Editor - PT](https://images.ctfassets.net/alneenqid6w5/5K3z9KH8VLYFh0iYA4UFDX/e526abc990cdf0bfa1d451580e7a8ec2/site-editor-ui-pt.png)
 
 | **Ferramenta**    | **Descrição** |
 | ----------        | ----------    |
diff --git a/docs/tutorials/pt/sku-bindings.md b/docs/tutorials/pt/sku-bindings.md
index ae5e5fad0..bc73dd9dc 100644
--- a/docs/tutorials/pt/sku-bindings.md
+++ b/docs/tutorials/pt/sku-bindings.md
@@ -27,7 +27,7 @@ Por padrão, para <a href="https://help.vtex.com/pt/tutorial/seller-white-label-
 
 A página **Vínculos de SKU** permite ao marketplace acompanhar e gerenciar a relação de vínculo entre os SKUs do seller e do marketplace. Para acessar a página, no Admin VTEX vá em **Marketplace > Sellers > Vínculos de SKU**. A seguinte interface vai aparecer:
 
-![sku-bindings-pt](//images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/f226cc707a595197ffa86fcb68db212b/sku-bindings-pt.png)
+![sku-bindings-pt](https://images.ctfassets.net/alneenqid6w5/3TrV8m2JLKuPjhKTtkY2Yl/f226cc707a595197ffa86fcb68db212b/sku-bindings-pt.png)
 
 A tabela a seguir apresenta a descrição das colunas da listagem de vínculos de SKUs:
 
diff --git a/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md b/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
index 675904b39..b10dcee11 100644
--- a/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
+++ b/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
@@ -25,7 +25,7 @@ Note que, apesar de estar em um iframe, ainda é possível aplicar CSS normalmen
 
 Em exemplo prático, para ocultar a opção "Pagar usando dois cartões", deve ser usado apenas `.ChangeNumberOfPayments {display: none}`.
 
-![2017-06-22 162341](//images.contentful.com/alneenqid6w5/5Un86ot46Qg0kwKoUkSioG/fb3cc25e273d68ab27a3ccd2b254eea6/2017-06-22_162341.jpg)
+![2017-06-22 162341](https://images.contentful.com/alneenqid6w5/5Un86ot46Qg0kwKoUkSioG/fb3cc25e273d68ab27a3ccd2b254eea6/2017-06-22_162341.jpg)
 
 ### Nova opção de cálculo de frete por geocoordenada
 
diff --git a/docs/tutorials/pt/special-conditions.md b/docs/tutorials/pt/special-conditions.md
index c3a20c2c3..a23d8360b 100644
--- a/docs/tutorials/pt/special-conditions.md
+++ b/docs/tutorials/pt/special-conditions.md
@@ -19,7 +19,7 @@ As condições especiais fazem parte da configuração das condições de pagame
 
 Para identificar as condições especiais aplicáveis a cada forma de pagamento, no Admin VTEX, acesse __Pagamentos > Configurações > Condições de Pagamento__, selecione a forma de pagamento desejada e verifique as opções conforme ilustração abaixo.
 
-![condições especiais de pago](//images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/7d7e10782385dcd7f76019a6ac8390e0/Condi____o_especial_de_pagamento.png)
+![condições especiais de pago](https://images.ctfassets.net/alneenqid6w5/1DllASa2BBHO7VjL1krOqD/7d7e10782385dcd7f76019a6ac8390e0/Condi____o_especial_de_pagamento.png)
 
 ## Condição Comercial
 
@@ -29,7 +29,7 @@ Para saber como cadastrar uma nova condição comercial e associá-la a um SKU,
 
 ## Como configurar a condição comercial na condição de pagamento
 
-![condicao-comercial pt](//images.ctfassets.net/alneenqid6w5/3VXKTcFtIkca4iwioWw648/6d574cddd91fd57ad6610631b11129c7/condicao-comercial.png)
+![condicao-comercial pt](https://images.ctfassets.net/alneenqid6w5/3VXKTcFtIkca4iwioWw648/6d574cddd91fd57ad6610631b11129c7/condicao-comercial.png)
 
 1. Dentro da condição de pagamento, clique em `Adicionar condição especial`.
 2. Em seguida, clique em `Condição Comercial`.
@@ -89,7 +89,7 @@ Permite disponibilizar uma condição de pagamento para uma política comercial
 
 Como configurar a política comercial na condição de pagamento
 
-![politica-comercial pt](//images.ctfassets.net/alneenqid6w5/25wX7GscdqwUmiWQC4Oi4U/291c228f5deee2036890f4e6bbb812d0/politica-comercial.png)
+![politica-comercial pt](https://images.ctfassets.net/alneenqid6w5/25wX7GscdqwUmiWQC4Oi4U/291c228f5deee2036890f4e6bbb812d0/politica-comercial.png)
 
 1. Dentro da condição de pagamento, clique em `Adicionar condição especial`.
 3. Em seguida em `Política Comercial (Canal de Vendas)`.
@@ -114,7 +114,7 @@ Como configurar o banco emissor na condição de pagamento:
 6. Caso deseje segmentar por co-brand, selecione a opção desejada em __Co-brand__ (essa caixa de seleção só vai aparecer se sua loja houver informado à VTEX a lista de cartões com co-brand).
 7. Salve as alterações.
 
-![banco-emissor pt](//images.ctfassets.net/alneenqid6w5/6e5Hf9tpLyuSkoGk08oOcw/38c528cd80c158b750a06ce3b99beea0/banco-emissor.png)
+![banco-emissor pt](https://images.ctfassets.net/alneenqid6w5/6e5Hf9tpLyuSkoGk08oOcw/38c528cd80c158b750a06ce3b99beea0/banco-emissor.png)
 
 ### Exemplos
 
@@ -146,7 +146,7 @@ Permite configurar uma validade na condição de pagamento, para que deixe de se
 
 Veja a seguir como configurar o período na condição de pagamento:
 
-![periodo pt](//images.ctfassets.net/alneenqid6w5/4zOoeve2Q8mgqkCQGQIWoq/5a37b26881341ce133c582693816bf18/periodo.png)
+![periodo pt](https://images.ctfassets.net/alneenqid6w5/4zOoeve2Q8mgqkCQGQIWoq/5a37b26881341ce133c582693816bf18/periodo.png)
 
 1. Dentro da condição de pagamento, clique em `Adicionar condição especial`.
 3. Em seguida, clique em `Período`.
diff --git a/docs/tutorials/pt/split-payment.md b/docs/tutorials/pt/split-payment.md
index 25c4fcf10..69a801255 100644
--- a/docs/tutorials/pt/split-payment.md
+++ b/docs/tutorials/pt/split-payment.md
@@ -57,11 +57,11 @@ Por exemplo, um cliente adiciona dois produtos ao mesmo carrinho de compras. Um
 
 O pagamento é distribuído da seguinte forma:
 
-![Split de recebíveis](//images.ctfassets.net/alneenqid6w5/4XGw7jeLfayteKzZ9eMaUU/60f806b9ee7dc128b7b6b55e8cc114c7/Split_de_receb__veis.png)
+![Split de recebíveis](https://images.ctfassets.net/alneenqid6w5/4XGw7jeLfayteKzZ9eMaUU/60f806b9ee7dc128b7b6b55e8cc114c7/Split_de_receb__veis.png)
 
 Nosso gateway calcula e distribui os pagamentos para cada beneficiário quando o pedido é faturado e envia essas informações ao provedor de pagamento. A distribuição é feita considerando o valor destinado a cada parte envolvida no pedido e as comissões cobradas pelo marketplace.
 
-![Relatório de comissão](//images.ctfassets.net/alneenqid6w5/2C8DFezzCKaSzgq2f77pxB/ca3cbcf0fa22a2bca6ab0d219b45e684/Split_de_receb__veis_2.png)
+![Relatório de comissão](https://images.ctfassets.net/alneenqid6w5/2C8DFezzCKaSzgq2f77pxB/ca3cbcf0fa22a2bca6ab0d219b45e684/Split_de_receb__veis_2.png)
 
 É importante considerar que a nossa solução de split de recebíveis tem algumas limitações:
 
@@ -88,11 +88,11 @@ Isso significa que o marketplace tem menos controle sobre o fluxo de pagamento.
 
 Por exemplo, um cliente adiciona dois produtos ao mesmo carrinho de compras. Um deles será entregue pelo próprio marketplace e o outro por um seller chamado Seller A.
 
-![Split de transação](//images.ctfassets.net/alneenqid6w5/3ZOMQYkxlRzMgUMck9o7o8/d36e97acd5addabaee0d1ef6c21fd712/Split_de_transa____o.png)
+![Split de transação](https://images.ctfassets.net/alneenqid6w5/3ZOMQYkxlRzMgUMck9o7o8/d36e97acd5addabaee0d1ef6c21fd712/Split_de_transa____o.png)
 
 No split de transação, o marketplace não precisa fazer nenhuma configuração. O seller é quem precisa configurar seu próprio meio de pagamento na afiliação com o marketplace em questão. Para mais detalhes, confira nossa documentação [Envie os meios de pagamento do seller white label ao marketplace.](https://help.vtex.com/pt/tutorial/enviar-os-meios-de-pagamento-do-seller-white-label-para-o-marketplace--bfvtPzZyikacSqgkgeGW)
 
-![Afiliação](//images.ctfassets.net/alneenqid6w5/yX3yPgPbkjlDDoYYdsnYD/9b03a7e73c7747db5b6cf22518730c50/Afiliados.png)
+![Afiliação](https://images.ctfassets.net/alneenqid6w5/yX3yPgPbkjlDDoYYdsnYD/9b03a7e73c7747db5b6cf22518730c50/Afiliados.png)
 
 O split de transação tem algumas limitações que devem ser levadas em consideração.
 
diff --git a/docs/tutorials/pt/store-access-permission.md b/docs/tutorials/pt/store-access-permission.md
index b13877427..fe3c19cae 100644
--- a/docs/tutorials/pt/store-access-permission.md
+++ b/docs/tutorials/pt/store-access-permission.md
@@ -25,4 +25,4 @@ Para realizar essa configuração, no painel administrativo (Admin) da conta des
 4. Selecione a opção __VTEX Store__.
 5. Marque a caixa de seleção __“Enables B2B behaviour”__ e salve as alterações.
 
-![Habilitar cenário B2B](//images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
+![Habilitar cenário B2B](https://images.ctfassets.net/alneenqid6w5/Kxh1UuEyCT52qprSkBkeH/49fd977f929e7422641030804973cf2f/Habilitar_B2B.gif)
diff --git a/docs/tutorials/pt/store-overview-beta.md b/docs/tutorials/pt/store-overview-beta.md
index 6ac109a70..7ffb33ec5 100644
--- a/docs/tutorials/pt/store-overview-beta.md
+++ b/docs/tutorials/pt/store-overview-beta.md
@@ -23,7 +23,7 @@ A página Visão Geral (Beta) em seu Admin VTEX fornece um acompanhamento em tem
 
 Essa ferramenta está disponível no Admin VTEX, na página de início. Para acessá-la, clique em **Dashboards > Visão Geral** no menu de navegação, ou digite _Visão Geral_ na barra de busca no topo da página.
 
-![PT Visão geral Beta](//images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/62aceefab415f246a39fcd604a89f080/PT_Visa__o_geral_Beta.png)
+![PT Visão geral Beta](https://images.ctfassets.net/alneenqid6w5/5C2Na8YDkwgIsMHqp28oGv/62aceefab415f246a39fcd604a89f080/PT_Visa__o_geral_Beta.png)
 
 Neste artigo, apresentamos as principais seções e ações presentes na página. Saiba mais sobre:
 
@@ -78,7 +78,7 @@ Caso deseje analisar os resultados gerados por campanhas, promoções ou lançam
 3. Selecione a [visualização](#visualizacao) `Acumulada`.
 4. Acompanhe a performance hora a hora das métricas.
 
-![PT visão geral acumulado](//images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/93f86ef067d3c7630ba6b545a8811a8b/PT_visa__o_geral_acumulado.png)
+![PT visão geral acumulado](https://images.ctfassets.net/alneenqid6w5/44wg1PRlF5WHD5I6R5Cu8o/93f86ef067d3c7630ba6b545a8811a8b/PT_visa__o_geral_acumulado.png)
 
 ### Acompanhar impactos de mudanças na loja
 
@@ -91,7 +91,7 @@ Caso deseje ver o impacto de mudanças feitas na loja, para identificar um poss
 3. Avalie o pulso nas métricas, ou pontos de inflexão no gráfico, ocorridos nas últimas duas horas. 
 4. Compare os horários dos pontos de inflexão, com as mudanças geradas para identificar sua causa e impacto. 
 
-![PT visão geral últimas duas horas](//images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/a069a0657d521f68a7be3a4221b70036/PT_visa__o_geral_u__ltimas_duas_horas.png)
+![PT visão geral últimas duas horas](https://images.ctfassets.net/alneenqid6w5/6JA6a85eBz6dMN5Cg1EAQi/a069a0657d521f68a7be3a4221b70036/PT_visa__o_geral_u__ltimas_duas_horas.png)
 
 ## Comparar períodos
 
@@ -134,7 +134,7 @@ A tabela abaixo descreve os gráficos incluídos na seção _Monitoramento_ da p
 
 ## Métricas
 
-![PT métricas](//images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/5757d545cae0367ad8a8e784532252f8/PT_me__tricas.png)
+![PT métricas](https://images.ctfassets.net/alneenqid6w5/6kxOvmmLfGYnhFiBvOtrOV/5757d545cae0367ad8a8e784532252f8/PT_me__tricas.png)
 
 A tabela abaixo descreve as métricas disponíveis no painel da página inicial. Todas as métricas se referem aos fluxos de compra realizados em lojas VTEX no período selecionado.
 
diff --git a/docs/tutorials/pt/store-overview.md b/docs/tutorials/pt/store-overview.md
index c4e99928e..92efe42b7 100644
--- a/docs/tutorials/pt/store-overview.md
+++ b/docs/tutorials/pt/store-overview.md
@@ -17,7 +17,7 @@ subcategory: 1TIJqw8kV2Yok4iQe4SAkq
 
 Na página Visão Geral, os proprietários de lojas VTEX têm acesso às principais métricas que impactam a receita de suas lojas. Nesse painel, você pode acompanhar a evolução das suas vendas através dos recursos de análise de tendências de pedidos, taxa de conversão e gráficos de funil de vendas. Essa ferramenta está disponível no Admin VTEX. Para acessá-la, clique em __Dashboards > Visão Geral__ no menu de navegação, ou digite *Visão Geral* na barra de busca no topo da página.
 
-![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 A página de Visão Geral traz um resumo do seu negócio com a VTEX. Para consultar análises mais profundas das métricas da sua loja, acesse [Performance de Vendas](https://help.vtex.com/pt/v4/docs/performance-de-vendas--6gx46RGRzWO8qgaVck7PRp).
 
@@ -54,7 +54,7 @@ Para comparar dados de diferentes períodos, no topo da página, selecione a dat
 | Últimos 28 dias | 00:00 do 29° dia anterior ao dia atual        | 23:59 do dia anterior ao dia de hoje                                                                                                                                    |
 
 ## Métricas
-![Store overview Métricas PT](//images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/efa916ff3c1f70906439c3f2f4adbf06/Me__tricas_PT.png)
+![Store overview Métricas PT](https://images.ctfassets.net/alneenqid6w5/75FnGMAHaNQxfcHmKM7Jjf/efa916ff3c1f70906439c3f2f4adbf06/Me__tricas_PT.png)
 
 A tabela abaixo descreve as principais métricas disponíveis no painel da página inicial. Todas as métricas se referem aos fluxos de compra realizados em lojas VTEX em um determinado período de tempo.
 
@@ -71,7 +71,7 @@ Pedidos cancelados                               | Número total de pedidos canc
 | Pedidos na última hora                | Pedidos feitos na sua loja na última hora. Ao clicar nessa métrica, você será redirecionado para a página [Todos os pedidos](https://help.vtex.com/pt/v4/docs/todos-os-pedidos--6JHeydzIft46VY7JTEpbJT).                                                                                                                                                                   |
 
 ## Produtos com maior receita / Produtos com mais unidades vendidas
-![Store overview Growing products PT](//images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/186c31b9b5632b5a106d3439dac945ec/Store_overview_Growing_products_PT.jpg)
+![Store overview Growing products PT](https://images.ctfassets.net/alneenqid6w5/5J5U85LjLuTt6MRFSaisZG/186c31b9b5632b5a106d3439dac945ec/Store_overview_Growing_products_PT.jpg)
 
 Esse componente lista seus produtos com maior receita e os produtos com mais unidades vendidas no período selecionado. Você pode alternar entre as duas opções clicando no título, ou no ícone <i class="fas fa-chevron-down"></i>.
 
@@ -80,16 +80,16 @@ Saiba mais sobre as listas:
 - **Produtos com mais unidades vendidas:** produtos que venderam mais unidades no período selecionado. Indica a quantidade de itens vendidos e uma porcentagem indicando aumento ou diminuição de itens vendidos, comparando entre os períodos selecionados. 
 
 ## Pedidos realizados
-![Store overview Pedidos realizados PT](//images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/7f8f3d3bab538d4c680dcd09511f0984/Pedidos_realizados_PT.png)
+![Store overview Pedidos realizados PT](https://images.ctfassets.net/alneenqid6w5/54DyQfUdOlf3VZdwIUdQjT/7f8f3d3bab538d4c680dcd09511f0984/Pedidos_realizados_PT.png)
 
 Esse gráfico mostra o número de pedidos recebidos pela sua loja no período selecionado. A linha azul mais grossa indica os pedidos feitos no período mais recente. A linha cinza mais fina indica os pedidos feitos no período que está sendo comparado.   Ao passar o cursor, o gráfico mostra o número de pedidos captados para cada data. 
 
 ## Pedidos cancelados
-![Store overview Pedidos cancelados PT](//images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/3bb0e1ec615af3d38c6b10cdcf3a3370/Pedidos_cancelados_PT.png)
+![Store overview Pedidos cancelados PT](https://images.ctfassets.net/alneenqid6w5/2RUKzEeb2SvpktBvQJoUQk/3bb0e1ec615af3d38c6b10cdcf3a3370/Pedidos_cancelados_PT.png)
 Esse gráfico mostra o número de pedidos cancelados na sua loja no período selecionado. A linha azul mais grossa indica os pedidos cancelados no período mais recente. A linha cinza mais fina indica os pedidos cancelados no período que está sendo comparado. Ao passar o cursor, o gráfico mostra o número de pedidos cancelados em cada data. 
 
 ## Análise de tendências de pedidos
-![Store overview Order trend PT](//images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/9807c6b956c1b2a34d558046766d1120/Store_overview_Order_trend_PT.jpg)
+![Store overview Order trend PT](https://images.ctfassets.net/alneenqid6w5/5c3eFasw5spgqeynh4Q9c5/9807c6b956c1b2a34d558046766d1120/Store_overview_Order_trend_PT.jpg)
 
 Esse gráfico mostra o comportamento dos pedidos da sua loja, indicando o número de pedidos feitos pelos compradores no período selecionado.
 
@@ -98,14 +98,14 @@ A linha indica a curva de pedidos para o período selecionado. Ao passar o curso
 A etiqueta acima do gráfico indica se o número de pedidos está `normal`, `baixo` ou `alto` em comparação com o desempenho habitual da sua loja no período selecionado.
 
 ## Taxa de conversão
-![Store overview Conversion rate PT](//images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/c974a11d3e708c5d40d0757ebfa95faf/Store_overview_Conversion_rate_PT.jpg)  
+![Store overview Conversion rate PT](https://images.ctfassets.net/alneenqid6w5/1S5WA2yR00R1GuBU0NoKaZ/c974a11d3e708c5d40d0757ebfa95faf/Store_overview_Conversion_rate_PT.jpg)  
 
 Esse gráfico mostra a taxa de conversão da sua loja nos períodos que você deseja comparar. 
 
 A taxa de conversão é calculada dividindo o número total de pedidos pelo número total de sessões na sua loja. A linha azul mais grossa indica a taxa de conversão para o período mais recente. A linha cinza mais fina indica a taxa para o período que está sendo comparado.  Ao passar o cursor, o gráfico mostra a taxa de conversão para cada período comparado. 
 
 ## Funil de vendas
-![Store overview sales funnel PT](//images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/c00dbe392b24f5157350d6c037759837/Store_overview_sales_funnel_PT.jpg)
+![Store overview sales funnel PT](https://images.ctfassets.net/alneenqid6w5/3jSzBfJ4nQa8iI2f1opyds/c00dbe392b24f5157350d6c037759837/Store_overview_sales_funnel_PT.jpg)
 
 Esse gráfico acompanha e rastreia o volume de sessões nas etapas intermediárias do fluxo de compras e identifica oportunidades para otimizar a taxa de conversão da loja. A tabela abaixo descreve as etapas intermediárias do fluxo de compras.
 
@@ -121,7 +121,7 @@ Esse gráfico acompanha e rastreia o volume de sessões nas etapas intermediári
 Cada barra azul no gráfico representa o volume de sessões que atingiram um determinado estágio do fluxo de compras. Esse volume é representado como um valor absoluto (acima), e como uma porcentagem do número de sessões (abaixo), juntamente com os pontos percentuais (p.p) de aumento ou diminuição no funil de vendas. Ao passar o cursor sobre a porcentagem, você pode ver mais detalhes sobre essa etapa intermediária.
 
 ## Categorias com maior receita
-![Categorias PT](//images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/18f8e56b4d93e7a89ca021153a73eb8e/Categorias_PT.png)
+![Categorias PT](https://images.ctfassets.net/alneenqid6w5/1jkVQ63kTKC7EWYNpZ2M5i/18f8e56b4d93e7a89ca021153a73eb8e/Categorias_PT.png)
 
 Este gráfico indica as dez categorias da sua loja que geraram mais receita no período selecionado. A barra azul indica a receita gerada na data mais recente, e a barra cinza indica a receita gerada no período comparado. Ao passar o cursor, o gráfico mostra a taxa de conversão para cada período comparado. Ao clicar no título do gráfico é possível mudar a visualização para __Categorias mais vendidas por pedido__.
 
diff --git a/docs/tutorials/pt/structured-data-through-google-search-console-data-markers.md b/docs/tutorials/pt/structured-data-through-google-search-console-data-markers.md
index 2b41b9b68..a4084df24 100644
--- a/docs/tutorials/pt/structured-data-through-google-search-console-data-markers.md
+++ b/docs/tutorials/pt/structured-data-through-google-search-console-data-markers.md
@@ -65,13 +65,13 @@ Com esse tipo de informação o usuário indicará ao Google informações sobre
 - <em style="color: gray">Data da resenha:_
 
 **Passo 1**
-![](//images.contentful.com/alneenqid6w5/2auEIkvBGMO8gqWqgA4u8q/0c53485d350f622ae184852c88688f0c/marcadordedados_step1.gif)****
+![](https://images.contentful.com/alneenqid6w5/2auEIkvBGMO8gqWqgA4u8q/0c53485d350f622ae184852c88688f0c/marcadordedados_step1.gif)****
 
 **Passo 2**
-![](//images.contentful.com/alneenqid6w5/62T28aRiUM0cOwOmiOQ2UA/8584923dd2b3c1f9f9bc7a782caee223/marcadordedados_step2_url_type.gif)
+![](https://images.contentful.com/alneenqid6w5/62T28aRiUM0cOwOmiOQ2UA/8584923dd2b3c1f9f9bc7a782caee223/marcadordedados_step2_url_type.gif)
 
 **Passo 3**
-![](//images.contentful.com/alneenqid6w5/5YhbETD9mMMgsAeKGE2SMG/622bccd0df4e05462f7db9ae7bb05cf9/marcadordedados_step3_markup_business.gif)
+![](https://images.contentful.com/alneenqid6w5/5YhbETD9mMMgsAeKGE2SMG/622bccd0df4e05462f7db9ae7bb05cf9/marcadordedados_step3_markup_business.gif)
 
 ### Produtos
 
@@ -90,10 +90,10 @@ Com esse tipo de informação o usuário indicará ao Google informações sobre
 - <em style="color: gray">Data da resenha:_
 
 **Passo 1**
-![](//images.contentful.com/alneenqid6w5/5ARq4O3nna8gqGM8KasC4K/57999e6c592e985550758aaab1c15c06/marcadordedados_step2_url_type_product.gif)
+![](https://images.contentful.com/alneenqid6w5/5ARq4O3nna8gqGM8KasC4K/57999e6c592e985550758aaab1c15c06/marcadordedados_step2_url_type_product.gif)
 
 **Passo 2**
-![](//images.contentful.com/alneenqid6w5/1TNyUZzqLSOOO48gmCOQ26/d78f4f460a7d6caf864498db7f1ce2b2/marcadordedados_step3_markup_product.gif)
+![](https://images.contentful.com/alneenqid6w5/1TNyUZzqLSOOO48gmCOQ26/d78f4f460a7d6caf864498db7f1ce2b2/marcadordedados_step3_markup_product.gif)
 
 **Passo 3**
 Lembrando que o **Marcador de Dados** apenas identifica os dados para o Google, para as demais ferramentas de busca será necessário estruturar os dados através de tags inseridas no código fonte.
diff --git a/docs/tutorials/pt/styles-overview.md b/docs/tutorials/pt/styles-overview.md
index b4a761895..a16dd89f8 100644
--- a/docs/tutorials/pt/styles-overview.md
+++ b/docs/tutorials/pt/styles-overview.md
@@ -19,7 +19,7 @@ A página **Estilos** permite que você defina a tipografia e a paleta de cores
 
 Para acessar a seção Estilos, entre no Admin VTEX, acesse **Storefront > Estilos** e descubra as principais ferramentas disponíveis na interface.
 
-![Estilos - Visão geral](//images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/e4118ab1f6d82ffdb0c093068c93759b/PT.png)
+![Estilos - Visão geral](https://images.ctfassets.net/alneenqid6w5/3pu48Ht8rMcJ8oRXpXJf1h/e4118ab1f6d82ffdb0c093068c93759b/PT.png)
 
 <div style="background-color:#FFF3CD; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px">
   Para aplicar e prever mudanças nos estilos da sua loja, certifique-se de utilizar um workspace que suporte o tráfego de produção, como um <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">workspace de produção</a>. 
diff --git a/docs/tutorials/pt/subscription-plans.md b/docs/tutorials/pt/subscription-plans.md
index f1d3050f2..94e6c4d09 100644
--- a/docs/tutorials/pt/subscription-plans.md
+++ b/docs/tutorials/pt/subscription-plans.md
@@ -21,7 +21,7 @@ Para disponibilizar planos de assinatura, você precisa antes instalar o aplicat
 
 A partir da página **Planos**, você pode visualizar e gerenciar os planos de assinaturas disponibilizados para os clientes da sua loja, conforme ilustrado abaixo.
 
-![planslist PT](//images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/a727c14ea5611ca6da8bb6207ef3b09a/planslist_PT.png)
+![planslist PT](https://images.ctfassets.net/alneenqid6w5/5PAOM3BmvgeIjU1ruAmEYG/a727c14ea5611ca6da8bb6207ef3b09a/planslist_PT.png)
 
 As principais funcionalidades desta página são:
 
diff --git a/docs/tutorials/pt/synonym-list.md b/docs/tutorials/pt/synonym-list.md
index 269294d76..6a39c652e 100644
--- a/docs/tutorials/pt/synonym-list.md
+++ b/docs/tutorials/pt/synonym-list.md
@@ -17,7 +17,7 @@ subcategory: BBzMtJan1UTxC9QZODnlN
 
 A página de **Sinônimos** possibilita visualizar e gerenciar todos os [sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do Intelligent Search cadastrados na sua loja. Para acessá-la no Admin VTEX, clique em **Storefront > Intelligent Search > Sinônimos**.
 
-![lista-sinonimos-pt](//images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/df0221f5313f7218c943a6f5f58b1088/lista-sinonimos-pt.PNG)
+![lista-sinonimos-pt](https://images.ctfassets.net/alneenqid6w5/4pBgCLPNUXZ2XZFgBS4tC7/df0221f5313f7218c943a6f5f58b1088/lista-sinonimos-pt.PNG)
 
 A página apresenta as seguintes informações em uma tabela: 
 
diff --git a/docs/tutorials/pt/telesales-toolbar.md b/docs/tutorials/pt/telesales-toolbar.md
index 1b732d1c3..89018e6f5 100644
--- a/docs/tutorials/pt/telesales-toolbar.md
+++ b/docs/tutorials/pt/telesales-toolbar.md
@@ -19,7 +19,7 @@ A toolbar de televendas é uma barra superior exibida no site da loja para usuá
 
 A toolbar aparece uma vez que o operador cadastrado faz o login no ambiente da loja e é exibida em todas as áreas do site.
 
-![toolbartelevendas PT](//images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/14d47a02678e01865dfcfc304647f1f2/toolbartelevendas_PT.png)
+![toolbartelevendas PT](https://images.ctfassets.net/alneenqid6w5/5ed5A8G266JqwpCaYAyDdI/14d47a02678e01865dfcfc304647f1f2/toolbartelevendas_PT.png)
 
 Veja abaixo os principais recursos da toolbar:
 *   [Entrar como cliente](#entrar-como-cliente)
diff --git a/docs/tutorials/pt/teste.md b/docs/tutorials/pt/teste.md
index 6776de554..372fb1a5b 100644
--- a/docs/tutorials/pt/teste.md
+++ b/docs/tutorials/pt/teste.md
@@ -21,7 +21,7 @@ Este é apenas um teste do markdown-renderer.
 16. Em __Chave Secreta do Aplicativo__, clique no botão __Mostrar__.
     - Copie o campo __ID do Aplicativo__ e cole no campo `Client Id` no admin do VTEX ID.
     - Copie o campo __Chave Secreta do Aplicativo__ do Aplicativo do Facebook e cole no campo `Client Secret` no admin do VTEX ID.
-    ![ID Chave Facebook PT](//images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/ae15499ad9a86bc2adc92ec7907d30f6/ID_Chave_Facebook_PT.png)
+    ![ID Chave Facebook PT](https://images.ctfassets.net/alneenqid6w5/1kQRsAhb9kEaXHgIzIm4ba/ae15499ad9a86bc2adc92ec7907d30f6/ID_Chave_Facebook_PT.png)
 
 1. LoremIpsum
 16. Em __Chave Secreta do Aplicativo__, clique no botão __Mostrar__.
diff --git a/docs/tutorials/pt/testing-webservice-using-soapui.md b/docs/tutorials/pt/testing-webservice-using-soapui.md
index 7adcb0082..9110fd2c3 100644
--- a/docs/tutorials/pt/testing-webservice-using-soapui.md
+++ b/docs/tutorials/pt/testing-webservice-using-soapui.md
@@ -33,7 +33,7 @@ O passo a passo de utilização é o seguinte:
 
 Substitua o valor {NOMEDALOJA} pelo nome de sua loja.
 
-![](//images.contentful.com/alneenqid6w5/WMZnCJCLg2WGSIesMOMKu/efed51a5c0e151d1ac1f7902600e522a/1.png)
+![](https://images.contentful.com/alneenqid6w5/WMZnCJCLg2WGSIesMOMKu/efed51a5c0e151d1ac1f7902600e522a/1.png)
 
 Efetue o login com os dados do Web Service desejado. Após efetuar o login, você visualizará todos os métodos existentes no [manual do Web Service](/pt/tutorial/manual-das-classes-e-metodos-usados-no-webservice/).
 
@@ -42,7 +42,7 @@ Efetue o login com os dados do Web Service desejado. Após efetuar o login, voc
 3. Localize o botão **Auth** e repita a autenticação antes de executar o método;
 4. Execute o método.
 
-![](//images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
+![](https://images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
 
 <div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
 <p><strong>Todos os outros métodos estão descontinuados.</strong></p>
diff --git a/docs/tutorials/pt/total-shipping-cost.md b/docs/tutorials/pt/total-shipping-cost.md
index e59b15a89..2df25d377 100644
--- a/docs/tutorials/pt/total-shipping-cost.md
+++ b/docs/tutorials/pt/total-shipping-cost.md
@@ -30,7 +30,7 @@ O custo final do envio é o preço total que será cobrado do cliente final para
 
 Sendo assim, de modo geral, o custo final de envio pode ser calculado desta forma:
 
-![Custo-final-envio-PT](//images.contentful.com/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/dc18eacbd9078557282f53cecb2ae4cf/Custo-final-envio-PT.svg)
+![Custo-final-envio-PT](https://images.contentful.com/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/dc18eacbd9078557282f53cecb2ae4cf/Custo-final-envio-PT.svg)
 
 <div class="alert alert-danger">
 Se o <b>adicional por preço</b> for menor que o <b>adicional de seguro</b>, a tarifa que é considerada é a do adicional de seguro e o adicional por preço é desconsiderado no cálculo da tarifa final.<p>
diff --git a/docs/tutorials/pt/transaction-flow-in-payments.md b/docs/tutorials/pt/transaction-flow-in-payments.md
index 0b22dcfe9..6bfe4d896 100644
--- a/docs/tutorials/pt/transaction-flow-in-payments.md
+++ b/docs/tutorials/pt/transaction-flow-in-payments.md
@@ -19,7 +19,7 @@ As transações realizadas pelo Pagamentos da VTEX passam por diversos status, d
 
 Veja abaixo um exemplo de linha do tempo com os status da transação.
 
-![Transaction Flow](//images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
+![Transaction Flow](https://images.contentful.com/alneenqid6w5/4AvpkJnEN2ImKkIgQQoIKK/e031cc030d5e1da745fac51137c4d4b2/Transaction_Flow.jpg)
 
 1. __Authorizing__: Este é o primeiro status de uma transação no Pagamentos. Neste estágio, o Pagamentos indica que teve início o processo de envio de informações para um adquirente ou para um outro gateway.
 2. __Authorized__: Após o início do processo de autorização, o adquirente ou o outro gateway envia as informações da transação para o banco emissor. O banco responde se a transação deve ser ou não autorizada. Caso negue a transação, o pagamento é __cancelado__. Caso autorize, o status da transação passa para __Authorized__.
diff --git a/docs/tutorials/pt/transactional-emails-for-subscription-orders.md b/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
index 88c9f086b..da55baf25 100644
--- a/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
@@ -43,7 +43,7 @@ Não é preciso ativar o envio de e-mails manualmente, pois são enviados de for
 5. Desmarque a caixa `Ativar envio de e-mail?`, que por default, vem marcada como ativa.
 6. Clique em **Salvar**.
 
-![PT Subscription Message Center](//images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
+![PT Subscription Message Center](https://images.ctfassets.net/alneenqid6w5/3g9hWtw1XUcYlUlwGCzagX/8161e2468d88999ec8505a46274b55f1/PT_Subscription_Message_Center.png)
 
 ## Templates default da Central de Mensagens
 
diff --git a/docs/tutorials/pt/transactions-events.md b/docs/tutorials/pt/transactions-events.md
index c7ec73972..5034e9c42 100644
--- a/docs/tutorials/pt/transactions-events.md
+++ b/docs/tutorials/pt/transactions-events.md
@@ -32,14 +32,14 @@ Abaixo são compartilhados exemplos de onde encontrar as informações mais comu
 
 Neste evento, vemos que VTEX começou o processo de autorização com o gateway de pagamentos e respondeu que a operação pode começar:
 
-![transação-autorizando](//images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
+![transação-autorizando](https://images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
 
 
 ## Transação autorizada e aprovada
 
 Através de uma solicitação de autorização, o gateway de pagamentos irá autorizar/pré-autorizar a transação, em caso de sucesso no fluxo. Com a autorização, a transação terá status de _aprovada_ para continuar com o fluxo do pedido
 
-![transação-autorizada-aprovada](//images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
+![transação-autorizada-aprovada](https://images.contentful.com/alneenqid6w5/2czvz4AZkECkCoC2CCmOME/92b9272bc3cf7302b3f51a69010591bf/transaccion-autorizada-aprobada.png)
 
 Caso a autorização não aconteça por algum problema fora do fluxo, o log dele será detalhado na timeline de acordo com as informações retornadas pelo gateway de pagamentos.
 
@@ -47,7 +47,7 @@ Caso a autorização não aconteça por algum problema fora do fluxo, o log dele
 
 No fluxo de pedidos, existe a possibilidade de enviar o pagamento para um antifraude (diretamente integrado na VTEX) para aplicar uma análise de risco. Depois de ter solicitado uma análise, o pedido terá um status indicando o início da análise e o retorno do antifraude, juntamente com o resultado:
 
-![transação -antifraude](//images.contentful.com/alneenqid6w5/3MjNaFOEJyiumaUyO2owSa/84130c11335612c4d982c016cc160616/transaccion-antifraude.png)
+![transação -antifraude](https://images.contentful.com/alneenqid6w5/3MjNaFOEJyiumaUyO2owSa/84130c11335612c4d982c016cc160616/transaccion-antifraude.png)
 
 Caso não aconteça a análise por causa de algum problema fora do fluxo, o log dele será detalhado na timeline, de acordo com as informações retornadas pelo gateway de pagamentos.
 
@@ -57,11 +57,11 @@ Quando a modalidade de pré-autorização de transações é utilizada, depois d
 
 Quando o processo de captura for iniciado, o evento Settlement será visualizado, o que indica que a captura foi solicitada ao gateway de pagamentos:
 
-![transação-captura-solicitação](//images.contentful.com/alneenqid6w5/4ZnegfgNcA4MQsgMuQaAsE/478d66d4b763730762637cc75a1aaea4/transaccion-captura-solicitud.png)
+![transação-captura-solicitação](https://images.contentful.com/alneenqid6w5/4ZnegfgNcA4MQsgMuQaAsE/478d66d4b763730762637cc75a1aaea4/transaccion-captura-solicitud.png)
 
 Enquanto a captura tenha sido iniciada com sucesso, o evento Settling será visualizado. E no final da captura, o evento Settled será mostrado:
 
-![transação-captura-iniciada-capturada](//images.contentful.com/alneenqid6w5/2Z2fPSYG5WK0YqSCuWGAQi/42f03171a702ada307bd85b21614757f/transaccion-captura-iniciada-capturada.png)
+![transação-captura-iniciada-capturada](https://images.contentful.com/alneenqid6w5/2Z2fPSYG5WK0YqSCuWGAQi/42f03171a702ada307bd85b21614757f/transaccion-captura-iniciada-capturada.png)
 
 Caso não aconteça a captura por causa de algum problema fora do fluxo, o log dele será detalhado na timeline, de acordo com as informações retornadas pelo operador de pagamentos.
 
@@ -69,7 +69,7 @@ Caso não aconteça a captura por causa de algum problema fora do fluxo, o log d
 
 Após a conclusão da transação, a VTEX indicará conforme mostra a imagem abaixo:
 
-![transação-concluida](//images.contentful.com/alneenqid6w5/68PjN2ChyMWqYQ4Owm8Yk6/0a440ea3cf6e5190b7b03e72d6a7e7e8/transaccion-finalizada.png)
+![transação-concluida](https://images.contentful.com/alneenqid6w5/68PjN2ChyMWqYQ4Owm8Yk6/0a440ea3cf6e5190b7b03e72d6a7e7e8/transaccion-finalizada.png)
 
 ## Transação agendada para captura automática
 
@@ -77,5 +77,5 @@ Geralmente as afiliações permitem que você configure uma data agendada de cap
 
 Aqui você consegue ver a data do agendamento da captura automática:
 
-![captura-auto-agendada pt](//images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
+![captura-auto-agendada pt](https://images.ctfassets.net/alneenqid6w5/6rg3IZhX9eGegqeUUQCEgQ/cc229f8dc0916dced5e7288ea279abec/transa____o_programada_cap_auto_pt.png)
 
diff --git a/docs/tutorials/pt/transferring-store-ownership.md b/docs/tutorials/pt/transferring-store-ownership.md
index 84c52f598..d7a7d6d14 100644
--- a/docs/tutorials/pt/transferring-store-ownership.md
+++ b/docs/tutorials/pt/transferring-store-ownership.md
@@ -25,7 +25,7 @@ A página de Gerenciamento de Titular permite identificar o usuário Titular atu
 
 Você deverá ver uma tela semelhante à imagem abaixo, com informações de contato do usuário Titular atual, um aviso indicando os riscos associados à transferência de propriedade da loja e um botão para confirmar que você reconhece os riscos e deseja transferir a propriedade mesmo assim.
 
-![Painel de gerenciamento de titular](//images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/5bfcb540546580d2f584550ce67a04a4/Sponsor_Management_pt.png)
+![Painel de gerenciamento de titular](https://images.ctfassets.net/alneenqid6w5/7AiPMmn3NnMjg89WgEfBXP/5bfcb540546580d2f584550ce67a04a4/Sponsor_Management_pt.png)
 
 ## Etapas do fluxo de transferência de propriedade
 
@@ -51,7 +51,7 @@ Com isso, a transferência de propriedade será concluída, e não será mais po
 
 O usuário Titular é responsável por ações importantes de manutenção e autorização, e erros cometidos por este perfil de acesso podem ter consequências drásticas. Portanto, é essencial acompanhar as mudanças relacionadas a este perfil de acesso. Para monitorar e auditar as transferências de propriedade da conta, você pode acessar o histórico de atividades clicando no botão **Histórico de Atividades** na página Gerenciamento de Titular.
 
-![Histórico de Atividades](//images.contentful.com/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/5b10117478c78e73f605cebebeeba43d/Activity_Log_pt.gif)
+![Histórico de Atividades](https://images.contentful.com/alneenqid6w5/6iXw7ib1Wsq4BiyR4Dgp8C/5b10117478c78e73f605cebebeeba43d/Activity_Log_pt.gif)
 
 Todos os eventos relacionados à transferência de propriedade da conta são registrados no histórico de atividades com a data em que ocorreram e o usuário associado ao evento.
 
diff --git a/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
index 7fed93247..d6e886c33 100644
--- a/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
@@ -32,7 +32,7 @@ Problemas em ciclos de assinaturas acontecem quando há um problema que impede a
 
 A aba **Ciclos com problema**, ilustrada na imagem abaixo, reúne os pedidos de assinaturas que apresentam problemas desse tipo.
 
-![cicloscomproblema PT](//images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/ee04171d3d9c785e049382f1e927b715/cicloscomproblema_PT.png)
+![cicloscomproblema PT](https://images.ctfassets.net/alneenqid6w5/5ijnWeUeqRzKWa2agsxK7O/ee04171d3d9c785e049382f1e927b715/cicloscomproblema_PT.png)
 
 A partir dessa aba, é possível gerenciar os pedidos que apresentam ciclos com problema e fazer novas tentativas manuais de criação de pedidos. Por exemplo, quando um produto está indisponível, você pode ajustar o estoque e, em seguida, fazer a nova tentativa.
 
@@ -189,7 +189,7 @@ Erros de pagamento são os que acontecem durante o fluxo de aprovação do pagam
 
 Pedidos com esse tipo de erro podem ser visualizados na aba **Erro de Pagamento**, ilustrada na imagem abaixo.
 
-![errosdepagamento PT](//images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/305350275dedd4e7c7888814db9fab07/errosdepagamento_PT.png)
+![errosdepagamento PT](https://images.ctfassets.net/alneenqid6w5/1RIw7xmqhpU4eWq0zHEnKG/305350275dedd4e7c7888814db9fab07/errosdepagamento_PT.png)
 
 Para analisar erros de pagamento, confira o passo a passo a seguir.
 
@@ -197,7 +197,7 @@ Para analisar erros de pagamento, confira o passo a passo a seguir.
 2. Clique na aba **Dashboards**.
 3. Na seção **Pedidos de Assinatura**, clique na aba **Erro de Pagamento**.
 4. Identifique o pedido desejado e clique na ID do pedido, conforme ilustrado na imagem abaixo. Você será redirecionado à página de detalhes do pedido, no módulo de **Todos os pedidos**.
-  ![PT Log Erro de pagamento](//images.ctfassets.net/alneenqid6w5/7697GbtjQbOutzL1sgrpjV/afdaba25349564a26d46149b437aab2a/PT_Log_Erro_de_pagamento.png)
+  ![PT Log Erro de pagamento](https://images.ctfassets.net/alneenqid6w5/7697GbtjQbOutzL1sgrpjV/afdaba25349564a26d46149b437aab2a/PT_Log_Erro_de_pagamento.png)
 5. Uma vez na página de detalhes do pedido, clique em `Ver detalhes da transação`, no card de **Pagamento**. Você será redirecionado à página de **Transações**, no módulo de **Pagamentos**.
 6. Na página de **Transações**, você poderá visualizar e analisar os eventos de transação do pedido. Leia o artigo [Visualizar detalhes da transação no Pagamentos](https://help.vtex.com/pt/tutorial/como-visualizar-detalhes-do-pedido) para mais informações.
 
diff --git a/docs/tutorials/pt/understand-your-balance.md b/docs/tutorials/pt/understand-your-balance.md
index eafd1be0f..ad8de0387 100644
--- a/docs/tutorials/pt/understand-your-balance.md
+++ b/docs/tutorials/pt/understand-your-balance.md
@@ -32,7 +32,7 @@ A box apresenta dois valores. O primeiro, __Disponível__, apresenta o saldo em
  
 Porém, isso não significa que você já pode movimentar o saldo completo. Os valores só podem ser movimentados depois que o recebível for liquidado na conta, que ocorre na data predeterminada de cada recebível.  
 
-![saldo_VTEXPAYMENT](//images.ctfassets.net/alneenqid6w5/3gxHd6hbhoTaKTJAe5IFBJ/08939976b6a113437a5852310ea3b467/image.png)
+![saldo_VTEXPAYMENT](https://images.ctfassets.net/alneenqid6w5/3gxHd6hbhoTaKTJAe5IFBJ/08939976b6a113437a5852310ea3b467/image.png)
 
 ### Como calcular o saldo a receber?
 
diff --git a/docs/tutorials/pt/understanding-b2b-orders.md b/docs/tutorials/pt/understanding-b2b-orders.md
index 8dc1b708a..71f32105a 100644
--- a/docs/tutorials/pt/understanding-b2b-orders.md
+++ b/docs/tutorials/pt/understanding-b2b-orders.md
@@ -19,7 +19,7 @@ Na operação de um e-commerce B2B, frequentemente é necessário informar o sta
 
 O app **Pedidos B2B** simplifica este processo, permitindo que qualquer funcionário possa consultar os pedidos feitos pela sua empresa pela própria loja virtual.
 
-![orders VTEX B2B](//images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
+![orders VTEX B2B](https://images.ctfassets.net/alneenqid6w5/VNG3045dKhkQBgG1ZTxOl/d239fe8c9794fb3aa7fb29a4c0623635/Screenshot_2020-10-20_VTEX_B2B.png)
 
 Essa experiência de autosserviço é possível graças a uma integração via API com o ERP. Com isso, o funcionário pode buscar pedidos por:
 
diff --git a/docs/tutorials/pt/understanding-how-indexation-works.md b/docs/tutorials/pt/understanding-how-indexation-works.md
index a8f94958f..a17b7873d 100644
--- a/docs/tutorials/pt/understanding-how-indexation-works.md
+++ b/docs/tutorials/pt/understanding-how-indexation-works.md
@@ -32,7 +32,7 @@ Toda vez que há alguma alteração como as listadas abaixo em um produto, a rei
 
 Uma vez que o produto esteja marcado para reindexar, ele fica com o status _indexação pendente_ na listagem de produtos do Admin VTEX. O indexador coloca esses produtos em uma fila, com um tempo de espera de 2 minutos, para que sejam processados. Após os 2 minutos, o produto fica disponível para o consumo da indexação. Nesse processo, todos os módulos da VTEX são consultados, atualizando preço e disponibilidade para cada política comercial. O tempo médio até a finalização desse processo é de 4 minutos.
 
-![](//images.contentful.com/alneenqid6w5/YdTfy83vaMCSCoUwUGsay/b5636eeb2cbf51ed0a5211c28f921ad5/Diagrama_sem_t_tulo__1_.png)
+![](https://images.contentful.com/alneenqid6w5/YdTfy83vaMCSCoUwUGsay/b5636eeb2cbf51ed0a5211c28f921ad5/Diagrama_sem_t_tulo__1_.png)
 
 ## Relatório de Indexação
 
@@ -47,7 +47,7 @@ Nele, são divididos os produtos em cada passo do processo de indexação e em p
 - **Total Indexado**, **Ainda não enfileirado** e **Total na Fila**: dizem respeito aos estágios do produto dentro do processo &#8211; Ainda não enfileirado são os produtos que foram alterados em menos de 2 minutos e Total na fila são aqueles que já entraram no processo de indexação, após esses 2 minutos.
 - **Na fila recentemente**, **Na fila entre 1 e 4 horas**, **Na fila de 4 a 8 horas** e **Na fila há mais de 8 horas**: são os períodos em que os produtos estão no processo de indexação.
 
-![RelatorioIndexação](//images.contentful.com/alneenqid6w5/6Y212qGxIAU4KWuWw8Uou2/306e536e7b5196abf04513915550a9f6/RelatorioIndexa_C3_A7_C3_A3o.png)
+![RelatorioIndexação](https://images.contentful.com/alneenqid6w5/6Y212qGxIAU4KWuWw8Uou2/306e536e7b5196abf04513915550a9f6/RelatorioIndexa_C3_A7_C3_A3o.png)
 
 O relatório de indexação exibe o tempo que o último item levou para ser reindexado no lado superior direito do relatório, conforme imagem acima. 
 
diff --git a/docs/tutorials/pt/understanding-how-the-cache-works.md b/docs/tutorials/pt/understanding-how-the-cache-works.md
index 31b308223..2b080979b 100644
--- a/docs/tutorials/pt/understanding-how-the-cache-works.md
+++ b/docs/tutorials/pt/understanding-how-the-cache-works.md
@@ -25,11 +25,11 @@ A solicitação do browser é conhecida como **request**, e a resposta do servid
 
 Veja o esquema abaixo:
 
-![Como o cache funciona - comunicação entre servidor e browser](//images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/51e191e174947c589ad4de6d4d56e474/1_PT.png)
+![Como o cache funciona - comunicação entre servidor e browser](https://images.ctfassets.net/alneenqid6w5/6ONSKQqdEoIsHxcvfp5GoS/51e191e174947c589ad4de6d4d56e474/1_PT.png)
 
 O cache é representado através de uma camada entre o browser e o servidor. Assim, quando um **request** acontece, em vez de o sistema ir buscar as informações diretamente no servidor, primeiramente ele vai até essa camada, o que torna a resposta muito mais ágil. Veja o esquema abaixo:
 
-![Como o cache funciona - comunicação com cache (sem expirar)](//images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/bb35e006ee78f624c403a0d81aefb65a/2_PT.png)
+![Como o cache funciona - comunicação com cache (sem expirar)](https://images.ctfassets.net/alneenqid6w5/15ss3biutJhXX2WkG9k8xG/bb35e006ee78f624c403a0d81aefb65a/2_PT.png)
 
 No entanto, como o dado atualizado está no servidor, de tempos em tempos o cache precisa ser atualizado. Esse tempo varia de acordo com o tipo de **request**, ou seja, se o **request** for uma página, o tempo é um, se for um arquivo javascript ou CSS é outro e, ainda, se for uma imagem, outro.
 
@@ -60,7 +60,7 @@ Quando o cache de um **request** (página ou arquivo) expira, ao realizar uma no
 
 Depois de atualizada, a versão cacheada volta a ser retornada para novas solicitações da URL. Veja o esquema ilustrando esse caso:
 
-![Como o cache funciona - comunicação com cache (expirado)](//images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/369d7e767ed2f09583955cea2d432a36/3_PT.png)
+![Como o cache funciona - comunicação com cache (expirado)](https://images.ctfassets.net/alneenqid6w5/e5oS6cve6yw1tS81PYkBK/369d7e767ed2f09583955cea2d432a36/3_PT.png)
 
 Nesse aspecto, podemos separar as respostas em dois grupos: Cacheadas e não cacheadas.
 
@@ -73,7 +73,7 @@ Ao clicar no request, o primeiro ao recarregar a página, localize, entre os hea
 
 Se o valor for `MISS`, significa que o conteúdo exibido não é um conteúdo cacheado e foi retornado diretamente do servidor. Mais uma informação relevante que pode ser identificada nos headers dos **requests** é a data em que o cache foi criado. Essa informação está disponível na propriedade `X-vtex-processed-at`.
 
-[]![](//images.contentful.com/alneenqid6w5/5GPSsb4UWA28QS4soyguSI/8772946997cc979ddf9c2297f2ca8bb6/cache.png)
+[]![](https://images.contentful.com/alneenqid6w5/5GPSsb4UWA28QS4soyguSI/8772946997cc979ddf9c2297f2ca8bb6/cache.png)
 
 Apesar de arquivos JavaScript e CSS também terem a duração de cache estabelecida, como esses tipos de arquivo são utilizados na formatação dos layouts e, por isso, em alguns casos, precisam ter sua atualização mais ágil, o portal possui uma inteligência que identifica alterações em seus conteúdos, rompendo com a camada de cache. 
 
diff --git a/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md b/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md
index 6982af4f1..6ae75794a 100644
--- a/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md
+++ b/docs/tutorials/pt/understanding-storebuilder-and-stylesbuilder.md
@@ -15,7 +15,7 @@ legacySlug: conhecendo-o-storebuilder-e-o-stylesbuilder
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-![UI Blocks Voando.mp4](//images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
+![UI Blocks Voando.mp4](https://images.ctfassets.net/alneenqid6w5/4VRam6UukpPhsCBMtrhBbv/60bb012cd676ebcc8b8805de021529db/UI_Blocks_Voando.mp4.gif) 
 
 Esta documentação foi estruturada para explicar os conceitos por tras do StoreBuilder e StyleBuilder da Store 2.xx. Durante toda a documentação, usaremos a DreamStore (um loja template que utiliza a `Store 2.xx`) para entender os principais conceitos que lhe permitirão estruturar e estilizar sua loja.
 
@@ -35,7 +35,7 @@ Esta documentação foi estruturada para explicar os conceitos por tras do Store
 
 Vamos olhar dentro do `/manifest.json` da DreamStore para ver o que nosso aplicativo precisa para funcionar corretamente:
 
-![Screen Shot 2019-01-25 at 16.40.06](//images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
+![Screen Shot 2019-01-25 at 16.40.06](https://images.ctfassets.net/alneenqid6w5/xQg8Ok5B1SbpKnACXsT7E/0d796fc2af346e1e9caf71eca3f6ec43/Screen_Shot_2019-01-25_at_16.40.06.png)
 
 Observe como temos dois builders especificados:
 
@@ -54,7 +54,7 @@ Como toda theme app (uma loja) faz uso do aplicativo `Store` (através da depend
 
 Execute "vtex link" e envie o app DreamStore para um workspace para que possamos estudá-lo
 
-![Screen Shot 2019-01-27 at 22.24.47](//images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
+![Screen Shot 2019-01-27 at 22.24.47](https://images.ctfassets.net/alneenqid6w5/6yCpuWYPBSqCIBkuv9oW14/47963f20fa8e85d76e57713a241eb583/Screen_Shot_2019-01-27_at_22.24.47.png)
 
 Se você é familiarizado com  React ou outros frameworks modernos de Javascript , você estará familiarizado com o conceito de componentes em uma página da Web. Como podemos observar, nossa página da Web tem um "cabeçalho", "carrossel" e uma "prateleira". Como esses componentes foram inseridos?
 
@@ -92,7 +92,7 @@ _Por favor, tenha em mente que você não estará desenvolvendo no aplicativo St
 
 Vamos olhar dentro do arquivo `/manifest.json` do Store2.xx para ver o que o aplicativo importa.
 
-![Screen Shot 2019-01-25 at 17.18.56](//images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
+![Screen Shot 2019-01-25 at 17.18.56](https://images.ctfassets.net/alneenqid6w5/1E61SoeL536WyC8OIIi5YR/31e433f5cd9ed495e4cde33aa09d5faa/Screen_Shot_2019-01-25_at_17.18.56.png)
 
 Podemos ver que é uma estrutura semelhante à do `manifest.json` da `Dreamstore`.
 
@@ -137,7 +137,7 @@ __Como cada página é definida por blocos e organizada por interfaces__, é hor
 Abra a pasta `store` e abra o arquivo `interfaces.json`.
 
 ### Interfaces
-![Screen Shot 2019-01-25 at 17.35.10](//images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
+![Screen Shot 2019-01-25 at 17.35.10](https://images.ctfassets.net/alneenqid6w5/7oDltXNQMdYZ2uPTsk5b4G/97ff30d86ab194a331d9f2c2ef8d5c95/Screen_Shot_2019-01-25_at_17.35.10.png)
 
 Uma interface é um conjunto de `blocks` e existe exclusivamente dentro do `Store2.xx`. Ele serve como um contrato entre os blocos e determina como vão trabalhar juntos.
 
@@ -194,7 +194,7 @@ Vamos continuar analisando o `store.home`. Eu estarei comentando inline.
 ```
 
 Se descermos podemos ver os mesmos objetos JSON definindo e configurando a organização da pagina. Outro exemplo é a página de resultados da pesquisa:
-![Screen Shot 2019-01-25 at 18.22.12](//images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
+![Screen Shot 2019-01-25 at 18.22.12](https://images.ctfassets.net/alneenqid6w5/1xXBCG7xjBUz1CEmHVoOhc/cf0bf48f2653f8688c97fd20f0d16287/Screen_Shot_2019-01-25_at_18.22.12.png)
 
 A informação descreve as seguintes informações de interface
   
@@ -216,7 +216,7 @@ Até agora, entendemos que:
 
 ### Estruturando e configurando nossa loja com o `StoreBuilder`
 
-![Codigo voando blocks.mp4](//images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
+![Codigo voando blocks.mp4](https://images.ctfassets.net/alneenqid6w5/7FiPuNIljcVgvS8zIwKD5f/7f5b67d4f7314afc404680a96e5f3680/Codigo_voando_blocks.mp4.gif)
 
 Abra `/ blocks.json` e encontre o nosso conhecido `store.home`. Vamos começar analisando o primeiro bloco dentro de `store.home : carrossel#home`.
 
@@ -240,12 +240,12 @@ Role para baixo até encontrarmos `carrossel#home`. Através de `props` podemos
   
   
 ### Estilizando nossa loja com o `StylesBuilder`
-![StyleBuilder.mp4](//images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
+![StyleBuilder.mp4](https://images.ctfassets.net/alneenqid6w5/5a9gZSPvWcVRIzdEbVo3k2/7ae4968655fa1a1919da1612fc490761/StyleBuilder.mp4.gif)
 
 
 O StylesBuilder é simples de entender pois pega seu arquivo styles.json durente o build e usa o gerador de [Tachyons](https://tachyons.io/) para produzir o CSS da sua loja.
 
 Nós projetamos o StylesBuilder para ser extremamente intuitivo e autoexplicativo. É tão simples quanto ajustar os códigos hexadecimais adequadamente e ver os resultados permearem por toda a loja.
 
-![Screen Shot 2019-01-28 at 00.40.17](//images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
+![Screen Shot 2019-01-28 at 00.40.17](https://images.ctfassets.net/alneenqid6w5/3JswKIv8jfYAyZCgmhfZhB/8208650f2907bb300e1ae83199490892/Screen_Shot_2019-01-28_at_00.40.17.png)
 
diff --git a/docs/tutorials/pt/understanding-the-additional-shipping-cost.md b/docs/tutorials/pt/understanding-the-additional-shipping-cost.md
index 38baad68c..00a8eac01 100644
--- a/docs/tutorials/pt/understanding-the-additional-shipping-cost.md
+++ b/docs/tutorials/pt/understanding-the-additional-shipping-cost.md
@@ -29,7 +29,7 @@ Existem três formas de se adicionar um valor extra sobre o frete: adicional por
 
 O adicional por valor é calculado a partir do preço do produto. É definida uma porcentagem que se aplicará ao preço do produto, e esse valor resultante é adicionado ao valor inicialmente calculado pelo frete. 
 
-![adicionalfrete1 PT](//images.ctfassets.net/alneenqid6w5/JRCo7yI9iwkS0uYW822eY/32044c9a1d1636d10d9eec1202625fc6/adicionalfrete1_PT.png)
+![adicionalfrete1 PT](https://images.ctfassets.net/alneenqid6w5/JRCo7yI9iwkS0uYW822eY/32044c9a1d1636d10d9eec1202625fc6/adicionalfrete1_PT.png)
 
 No caso acima, o valor dos produtos totaliza R$ 80,00 e o valor cadastrado como __Valor adicional__ é 10%. Com isso, o valor calculado para ser adicionado ao valor do frete é de R$ 8,00. A soma do valor final de frete e o valor adicional, é de R$18,00.
 
@@ -46,7 +46,7 @@ O adicional por peso é calculado com base no peso do produto. O cálculo desse
 
 A conta é a seguinte:
 
-![adicionalfrete2 PT](//images.ctfassets.net/alneenqid6w5/19t4etUFuYCK0sM2SCK4g2/99a0bc4b935a1db688f94795ea3614b3/adicionalfrete2_PT.png)
+![adicionalfrete2 PT](https://images.ctfassets.net/alneenqid6w5/19t4etUFuYCK0sM2SCK4g2/99a0bc4b935a1db688f94795ea3614b3/adicionalfrete2_PT.png)
 
 Ou seja, no exemplo, o limite mínimo da faixa de peso que o produto se encontra é de 100 gramas. O valor cadastrado no campo __Valor adicional por peso__ é de 0,1. Logo, o valor a ser adicionado ao cálculo de 14,00, o valor final ficou em R$ 24,00.
 
@@ -62,7 +62,7 @@ O adicional no frete é calculado sobre o valor final do frete, e não sobre o v
 
 O valor cadastrado na tabela de frete + o adicional por peso + o adicional por valor * o valor cadastrado no campo adicional no frete.
 
-![adicionalfrete3 PT](//images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
+![adicionalfrete3 PT](https://images.ctfassets.net/alneenqid6w5/Q9pu2UYMAEM0gs200yAmw/0442d1b40cba53fb7237b27df323fe08/adicionalfrete3_PT.png)
 
 Nesse caso, o valor inserido no campo __Valor adicional__, será o valor percentual a ser somado ao valor final calculado do frete. Por exemplo: se o frete, com todos seus adicionais já calculados, der R$20,00 e o valor cadastrado no campo Adicional nos Fretes for 10, significa que será acrescentando R$2,00 aos R$20,00 do frete, totalizando R$ 22,00 a ser cobrado ao cliente pelo frete. Essa é uma maneira simples de conseguir uma margem sobre os fretes das compras.
 
diff --git a/docs/tutorials/pt/understanding-the-cubic-weight-factor.md b/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
index c906758f7..1ab553f4e 100644
--- a/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
@@ -40,7 +40,7 @@ Ao realizar o cálculo do peso cúbico, a plataforma VTEX não utiliza unidades
 
 Observe o exemplo a seguir:
 
-![](//images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
+![](https://images.contentful.com/alneenqid6w5/3KZDUQlPBYEY8mSwqQgW6k/15cef41598f4fc1359f482cddbcca756/pesocubado.jpg)
 
 - __Dimensões do pacote:__ `50cm x 60cm x 15cm`
 - __Peso mínimo do pacote:__ `9kg`
@@ -55,7 +55,7 @@ Ou seja, caso o valor oferecido pela sua transportadora `6.000`, é necessário
 
 Ao realizar o cadastro da sua transportadora, esse é o valor que você deve preencher no campo **Fator de peso cúbico** na sua [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 
-![cubic_weight_PT](//images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/dffa4cf86d504ec7325bb80b7b26704d/cubic_weight_PT.png)
+![cubic_weight_PT](https://images.ctfassets.net/alneenqid6w5/44WaAckgByWYgyYGXtEoOj/dffa4cf86d504ec7325bb80b7b26704d/cubic_weight_PT.png)
 
 Portanto, o cálculo final seria:
 - __Dimensões do pacote:__ `50cm x 60cm x 15cm`
diff --git a/docs/tutorials/pt/understanding-the-message-center.md b/docs/tutorials/pt/understanding-the-message-center.md
index 7caec06b5..15ccf2075 100644
--- a/docs/tutorials/pt/understanding-the-message-center.md
+++ b/docs/tutorials/pt/understanding-the-message-center.md
@@ -23,7 +23,7 @@ Os templates são as mensagens em si. As mensagens estão categorizadas conforme
 
 Entenda as informações que cada _card_ do template traz:
 
-![message center - card templates](//images.contentful.com/alneenqid6w5/4Npky1GjAs2OsoQ6oG6a8/c001d59b1eeca31d0342e52d79c58a3f/message-center-card-templates.png)
+![message center - card templates](https://images.contentful.com/alneenqid6w5/4Npky1GjAs2OsoQ6oG6a8/c001d59b1eeca31d0342e52d79c58a3f/message-center-card-templates.png)
 
 - Nome do template, para identificação interna (não se trata do assunto do e-mail enviado).
 - Aplicação/módulo ao qual ele pertence (em verde).
@@ -33,7 +33,7 @@ Entenda as informações que cada _card_ do template traz:
 
 Para facilitar a navegação a interface disponibiliza, além do campo de busca por texto livre, filtros por aplicações (módulos) e tipo (mensagem padrão ou personalizada/alterada).
 
-![busca-templates-central-mensagens pt](//images.ctfassets.net/alneenqid6w5/QbPAmXYUeIwUqsugGkw40/c489a00144a36b78df59ba4eb4cc539c/busca-templates-central-mensagens_pt.png)
+![busca-templates-central-mensagens pt](https://images.ctfassets.net/alneenqid6w5/QbPAmXYUeIwUqsugGkw40/c489a00144a36b78df59ba4eb4cc539c/busca-templates-central-mensagens_pt.png)
 
 Depois de entender o básico sobre os templates, você já pode ver como editá-los. Esse passo não é obrigatório, pois a VTEX fornece um layout básico e responsivo para todas as mensagens, com os dados necessários para uma boa comunicação com seu cliente, mas é natural que as lojas os adequem ao padrão de comunicação já usado para a marca.
 
@@ -41,7 +41,7 @@ Depois de entender o básico sobre os templates, você já pode ver como editá-
 
 O remetente é quem envia a mensagem, mas neste caso trazendo também o cadastro do nome e e-mail que será exibido ao cliente, e configurações do servidor de envio (SMTP).
 
-![message center - card remetentes](//images.contentful.com/alneenqid6w5/4Vx2zuCo3YmowCmMe6IAuQ/9d9442495a9218586ed7cc85c76f6189/message-center-card-remetentes.png)
+![message center - card remetentes](https://images.contentful.com/alneenqid6w5/4Vx2zuCo3YmowCmMe6IAuQ/9d9442495a9218586ed7cc85c76f6189/message-center-card-remetentes.png)
 
 - Nome do remetente, para identificação interna.
 - Tipo de servidor SMTP, que pode ser da VTEX ou da própria loja.
diff --git a/docs/tutorials/pt/understanding-the-price-change-rule.md b/docs/tutorials/pt/understanding-the-price-change-rule.md
index 7c0d870c7..52c950c94 100644
--- a/docs/tutorials/pt/understanding-the-price-change-rule.md
+++ b/docs/tutorials/pt/understanding-the-price-change-rule.md
@@ -26,6 +26,6 @@ Esse bloqueio também é realizado para todas as demais formas de atualização
 
 O percentual da __trava de preço__ pode ser removido ou alterado nas __Configurações__ do módulo de __Preços__.
 
-![trava-variação-preço pt](//images.ctfassets.net/alneenqid6w5/5anjARjLAk0sCKgEEoWCK8/c148b88625482f6fb9ca35373ab69fe7/trava-varia____o-pre__o_pt.png)
+![trava-variação-preço pt](https://images.ctfassets.net/alneenqid6w5/5anjARjLAk0sCKgEEoWCK8/c148b88625482f6fb9ca35373ab69fe7/trava-varia____o-pre__o_pt.png)
 
 Alguns marketplaces também possuem esta trava de variação de preços. Caso você deseje alterar os preços para além dos ranges da trava, basta entrar em contato com o marketplace solicitando a alteração. 
diff --git a/docs/tutorials/pt/understanding-the-security-report.md b/docs/tutorials/pt/understanding-the-security-report.md
index 24246f138..785a268d4 100644
--- a/docs/tutorials/pt/understanding-the-security-report.md
+++ b/docs/tutorials/pt/understanding-the-security-report.md
@@ -31,7 +31,7 @@ Siga o passo a passo para acessar o relatório:
 
 O exemplo abaixo ilustra o filtro para uma alteração (seja criação ou atualização) de preço de um SKU. Para isso, é necessário utilizar os campos __Dados__ com o Id do SKU, __Tela__ com o local da plataforma onde ocorre essa alteração e um período de tempo específico. De acordo com o relatório que se deseja, pode ser necessário usar outros campos em conjunto ou em substituição a esses.
 
-![relatoriosegurançaPT](//images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/beca72120562bfd90fa0b81965fcf2be/relatorio-seguranca-pt.gif)
+![relatoriosegurançaPT](https://images.ctfassets.net/alneenqid6w5/9t5KxHdSwTGYy84KmJIq7/beca72120562bfd90fa0b81965fcf2be/relatorio-seguranca-pt.gif)
 
 Confira a seção a seguir para entender todos os campos disponíveis para filtrar o relatório.
 
diff --git a/docs/tutorials/pt/understanding-the-suspicious-purchase-notice-on-vtex-do.md b/docs/tutorials/pt/understanding-the-suspicious-purchase-notice-on-vtex-do.md
index 055f0cb1b..3b634634f 100644
--- a/docs/tutorials/pt/understanding-the-suspicious-purchase-notice-on-vtex-do.md
+++ b/docs/tutorials/pt/understanding-the-suspicious-purchase-notice-on-vtex-do.md
@@ -27,7 +27,7 @@ Quando o SherlockBOT identifica um pedido fechado de maneira que pode indicar at
 
 Veja um exemplo desse alerta no screenshot abaixo:
 
-![sherlock (1)](//images.contentful.com/alneenqid6w5/6CsvYu9nfG0E4QowAEu86/c69b772065781ddc98bc85eeee37ef01/sherlock-1.png)
+![sherlock (1)](https://images.contentful.com/alneenqid6w5/6CsvYu9nfG0E4QowAEu86/c69b772065781ddc98bc85eeee37ef01/sherlock-1.png)
 
 O lojista pode ainda ser incluído nas barreiras de segurança do Gateway, ou seja, a VTEX pode aplicar à sua loja regras de proteção contra testes de cartão de crédito. 
 
diff --git a/docs/tutorials/pt/understanding-the-task-list-vtex-do.md b/docs/tutorials/pt/understanding-the-task-list-vtex-do.md
index 25c5d6a96..e8588ee82 100644
--- a/docs/tutorials/pt/understanding-the-task-list-vtex-do.md
+++ b/docs/tutorials/pt/understanding-the-task-list-vtex-do.md
@@ -19,13 +19,13 @@ O VTEX DO é um gerenciador de tarefas geradas pelos módulos da plataforma para
 
 Para visualizar a lista de tarefas, basta clicar no canto inferior direto da tela do Gerenciamento de Pedidos.  Alguns exemplos dessas tarefas são: __revisar pagamento para cancelar; estornar pagamento; autorizar pedido com alçada; cancelamento requisitado e muitas outras__, pois cada módulo existente na VTEX tem a autonomia e permissão para postar qualquer informação.
 
-![](//images.contentful.com/alneenqid6w5/6CypzWJhLye2OOW6QqEKu0/fce59ed1fedbb5f8889b1cb5f3ec4bf2/VtexDO_GifAbrir.gif)
+![](https://images.contentful.com/alneenqid6w5/6CypzWJhLye2OOW6QqEKu0/fce59ed1fedbb5f8889b1cb5f3ec4bf2/VtexDO_GifAbrir.gif)
 
 Essa funcionalidade permite ao usuário as seguintes ações: atribuir as tarefas a alguém (até para si próprio), marcá-las como resolvidas, adicionar um comentário e ver mais detalhes, que é o redirecionamento para onde a tarefa precisa ser feita. Existem os botões adiar e ignorar, mas são futuras ações que ainda estão sendo desenvolvidas.
 
 ## Atribuir e desatribuir uma tarefa a si próprio
 
-![](//images.contentful.com/alneenqid6w5/hSiaD565VuWwKUmWuwucO/a7f7a04e378a43e14cc0ed8469deb573/VtexDO_GifAtribuirTarefaProprio.gif)
+![](https://images.contentful.com/alneenqid6w5/hSiaD565VuWwKUmWuwucO/a7f7a04e378a43e14cc0ed8469deb573/VtexDO_GifAtribuirTarefaProprio.gif)
 
 ### Atribuir uma tarefa:
 - Abra o **VTEX DO**;
@@ -38,7 +38,7 @@ Essa funcionalidade permite ao usuário as seguintes ações: atribuir as tarefa
 
 ## Atribuir e desatribuir uma tarefa a outro usuário
 
-![](//images.contentful.com/alneenqid6w5/xTb2Dtb79ueKEiESCWi2y/05af0e238ac055a992b612381d3acd42/VtexDO_GifAtribuirTarefaTerceiros.gif)
+![](https://images.contentful.com/alneenqid6w5/xTb2Dtb79ueKEiESCWi2y/05af0e238ac055a992b612381d3acd42/VtexDO_GifAtribuirTarefaTerceiros.gif)
 
 ### Atribuir uma tarefa:
 - Abra o **VTEX DO**;
@@ -55,7 +55,7 @@ _As tarefas que são atribuídas a você, aparecem na aba chamada “MINHAS”.
 
 ## Filtrar uma tarefa
 
-![](//images.contentful.com/alneenqid6w5/1o6DK8SFHiuWwcESKScaqE/a616812c5d48431cf5383dbd204c511f/VtexDO_GifFiltro.gif)
+![](https://images.contentful.com/alneenqid6w5/1o6DK8SFHiuWwcESKScaqE/a616812c5d48431cf5383dbd204c511f/VtexDO_GifFiltro.gif)
 
 É possível filtrar através da barra de busca utilizando: o nome da tarefa, nome do usuário que está atribuído às mesmas ou comentário inserido. Permite ainda filtrar de acordo com o módulo que postou a tarefa.
 
@@ -73,7 +73,7 @@ _As tarefas que são atribuídas a você, aparecem na aba chamada “MINHAS”.
 
 Como o objetivo da funcionalidade é realizar as tarefas, uma facilidade que é proporcionada pela mesma é, o redirecionamento para o módulo que postou a tarefa dentro do pedido, transação ou qualquer outro endereço específico do respectivo módulo que criou a tarefa.
 
-![](//images.contentful.com/alneenqid6w5/5nxobC9IVUGUe8CQoaI02I/84ac62df3673e85a379d3c9f409ef999/VtexDO_GifFazerTarefa.gif)
+![](https://images.contentful.com/alneenqid6w5/5nxobC9IVUGUe8CQoaI02I/84ac62df3673e85a379d3c9f409ef999/VtexDO_GifFazerTarefa.gif)
 
 1. Abra o VTEX Do;
 2. Clique sobre a tarefa que deseja realizar;
@@ -85,7 +85,7 @@ Como o objetivo da funcionalidade é realizar as tarefas, uma facilidade que é
 
 A título de manter o VTEX Do de forma organizada, o ideal é finalizar a tarefa após a realização desta, a fim de evitar retrabalho ou perda de tempo futuramente quando visualizar a lista de tarefas novamente. Uma outra possibilidade seria finalizar uma tarefa mesmo sem acatá-la, por exemplo, se for solicitado o cancelamento de um pedido, mas você conseguiu reverter a situação. Caso necessite reabrir uma tarefa que foi indevidamente finalizada, não se preocupe, pois é possível reabrí-la a qualquer momento. Basta procurá-la na lista e seguir os passos do gif a seguir.
 
-![](//images.contentful.com/alneenqid6w5/5Uc9dUfGusGcoAW6iw4EOa/52d9aa14d083b08e66fd4f9453cf1813/VtexDO_GifFinalizarTarefa.gif)
+![](https://images.contentful.com/alneenqid6w5/5Uc9dUfGusGcoAW6iw4EOa/52d9aa14d083b08e66fd4f9453cf1813/VtexDO_GifFinalizarTarefa.gif)
 
 ### Para finalizar uma tarefa:
 - Abra o **VTEX DO**;
@@ -101,7 +101,7 @@ A título de manter o VTEX Do de forma organizada, o ideal é finalizar a taref
 
 Ainda com o intuito de organizar essas tarefas e formalizar a comunicação através delas, existe a função de inserir um comentário de acordo com a necessidade de cada caso.
 
-![](//images.contentful.com/alneenqid6w5/5SrDSFwNIkokms4ayga2oo/86862b1896fabd96b34344318fd553fb/VtexDO_GifInserirComentario.gif)
+![](https://images.contentful.com/alneenqid6w5/5SrDSFwNIkokms4ayga2oo/86862b1896fabd96b34344318fd553fb/VtexDO_GifInserirComentario.gif)
 
 1. Abra o **VTEX DO**;
 2. Clique sobre a tarefa que deseja realizar um comentário;
@@ -110,4 +110,4 @@ Ainda com o intuito de organizar essas tarefas e formalizar a comunicação atra
 
 Como há a possibilidade de executar as ações do VTEX Do com ele aberto, para fechá-lo se faz necessário clicar na seta para baixo, conforme no gif abaixo:
 
-![](//images.contentful.com/alneenqid6w5/6N34IAYvdKyYAa6KCIM2AO/670277853327aa793c851d8a0ce99b2a/VtexDO_GifFechar.gif)
+![](https://images.contentful.com/alneenqid6w5/6N34IAYvdKyYAa6KCIM2AO/670277853327aa793c851d8a0ce99b2a/VtexDO_GifFechar.gif)
diff --git a/docs/tutorials/pt/understanding-the-topbar.md b/docs/tutorials/pt/understanding-the-topbar.md
index 66d681c75..0d43f5412 100644
--- a/docs/tutorials/pt/understanding-the-topbar.md
+++ b/docs/tutorials/pt/understanding-the-topbar.md
@@ -19,16 +19,16 @@ A sidebar é o ponto de partida para todas as áreas do admin VTEX. Abaixo, voc
 
 **Navegue entre os módulos**: Para isso, basta clicar sobre o simbolo da VTEX à sua esquerda. Na barra lateral que se abrirá, basta clicar sobre o nome do módulo desejado para acessá-lo.
 
-![paginainicial.pt](//images.ctfassets.net/alneenqid6w5/9od439KuVjDIGM1iFrBRc/75561521e641b3f19488b4e5e5897a9b/ppaginainicial.pt.png)
+![paginainicial.pt](https://images.ctfassets.net/alneenqid6w5/9od439KuVjDIGM1iFrBRc/75561521e641b3f19488b4e5e5897a9b/ppaginainicial.pt.png)
 
 **Navegue entre os subdomínios**: Para navegar entre os subdomínios de sua loja, basta clicar sobre o domínio atual. Você visualizará todas as opções. Para ir para o admin de um dos subdomínios, basta clicar sobre ele no menu.
 
-![subdominios.pt](//images.ctfassets.net/alneenqid6w5/4U9sb38voR0peYq5FQS5cI/ff7c5aef5d05a5cb98d53087f0552a45/subdominios.pt.png)
+![subdominios.pt](https://images.ctfassets.net/alneenqid6w5/4U9sb38voR0peYq5FQS5cI/ff7c5aef5d05a5cb98d53087f0552a45/subdominios.pt.png)
 
 **Selecione o idioma do admin**: Para selecionar o idioma, basta clicar sobre o ícone de idioma e selecionar o desejado.
-![idioma.pt](//images.ctfassets.net/alneenqid6w5/1scR4VdnKvmExP9kRGeDGy/c880564e43448077d0fee2fd8336ea49/idioma.pt.png)
+![idioma.pt](https://images.ctfassets.net/alneenqid6w5/1scR4VdnKvmExP9kRGeDGy/c880564e43448077d0fee2fd8336ea49/idioma.pt.png)
 
 **Acesse nossas bases de conhecimento**: Para acessar uma de nossas bases, clique sobre seu perfil de suporte e selecione o local que deseja acessar, clicando sobre ele.
-![support.pt](//images.ctfassets.net/alneenqid6w5/7h9sRBe9lVGqqS1NpX9c5J/9bd14d91177a930317fd1137f34a8188/support.pt.png)
+![support.pt](https://images.ctfassets.net/alneenqid6w5/7h9sRBe9lVGqqS1NpX9c5J/9bd14d91177a930317fd1137f34a8188/support.pt.png)
 
 **Faça o logoff**: Para realizar o logoff, basta clicar sobre seu nome e clicar sobre o link **Sair**.
diff --git a/docs/tutorials/pt/understanding-the-updating-of-the-xml.md b/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
index 10f65a2a6..8341eef55 100644
--- a/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
@@ -21,6 +21,6 @@ Essa consulta significa que o XML foi chamado em menos de 48 horas. Aqueles XML
 
 É possível visualizar a última data de atualização do XML. Essa informação fica em horário UTC no final do documento, conforme imagem abaixo.
 
-[![xml](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](//images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
+[![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
 
 <div class="alert alert-info">Caso a opção "Exibir os SKUs sem saldo disponível (esgotados) em Estoque entre os resultados" esteja desmarcada, os produtos/SKUs que estiverem esgotados não aparecerão no XML. <br>Produtos inativos também <strong>não</strong> aparecem no XML.</div>
diff --git a/docs/tutorials/pt/understanding-vtexs-email-capture-system.md b/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
index 164062ad0..a30446a1c 100644
--- a/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
@@ -51,4 +51,4 @@ Para que a função do <a href="https://help.vtex.com/pt/tutorial/acesse-o-carri
 Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
 </div>
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
diff --git a/docs/tutorials/pt/untitled-entry-2017-07-10-at-10-14-00.md b/docs/tutorials/pt/untitled-entry-2017-07-10-at-10-14-00.md
index f07e3daaf..3be8b4560 100644
--- a/docs/tutorials/pt/untitled-entry-2017-07-10-at-10-14-00.md
+++ b/docs/tutorials/pt/untitled-entry-2017-07-10-at-10-14-00.md
@@ -19,7 +19,7 @@ Existem algumas ferramentas que podem te ajudar na analise do cenario de possive
 
 Analisar um caso de nao exibiçao de algum elemento no front da loja pode levar algum tempo ,porem uma forma facil de analisar estes casos é desativando o css e o JS do frontend ,porem para desativa-los voce nao precisa de muito , basta utilizar chrome e instalar a extensao web developer , esta extensao posibilita desabilitar alguns elementos da pagina dentre eles JS y CSS , com isso sua analisa ficara mais facil.
 
-![IMAGEMFB1](//images.contentful.com/alneenqid6w5/39TAI2iVFmSsoeMYeqC6wy/9d863f829ee04987e7c3f08395c1cdb3/IMAGEMFB1.png)
+![IMAGEMFB1](https://images.contentful.com/alneenqid6w5/39TAI2iVFmSsoeMYeqC6wy/9d863f829ee04987e7c3f08395c1cdb3/IMAGEMFB1.png)
 
 Caso voce nao o tenha uma outra opção será realizar esta desativação na pagina de tools.html que mostramos neste outro artigo LINK OUTRO ARTIGO
 
diff --git a/docs/tutorials/pt/untitled-entry-2017-07-19-at-06-54-03.md b/docs/tutorials/pt/untitled-entry-2017-07-19-at-06-54-03.md
index 90a277623..d590612b3 100644
--- a/docs/tutorials/pt/untitled-entry-2017-07-19-at-06-54-03.md
+++ b/docs/tutorials/pt/untitled-entry-2017-07-19-at-06-54-03.md
@@ -29,4 +29,4 @@ Esse ambiente pode ser considerado um Seller e possui tais módulos:
 
 É uma solução, principalmente, para lojas com franquias, pois permite que cada franquia possue seu Portal Admin, preços e definição de estoques. Além das formas de pagamento independentes da loja principal (loja pai).
 
-![whitelabel-modules](//images.contentful.com/alneenqid6w5/3Jbu7lk4NGeWuSuUUI8mQa/40af512f57f507f3bae8a50b3856cb88/2017-07-19_16_17_51-Orders___VTEX_OMS.png)
+![whitelabel-modules](https://images.contentful.com/alneenqid6w5/3Jbu7lk4NGeWuSuUUI8mQa/40af512f57f507f3bae8a50b3856cb88/2017-07-19_16_17_51-Orders___VTEX_OMS.png)
diff --git a/docs/tutorials/pt/untitled-entry-2017-09-12-at-06-50-03.md b/docs/tutorials/pt/untitled-entry-2017-09-12-at-06-50-03.md
index 7cc99f16f..e02aa0120 100644
--- a/docs/tutorials/pt/untitled-entry-2017-09-12-at-06-50-03.md
+++ b/docs/tutorials/pt/untitled-entry-2017-09-12-at-06-50-03.md
@@ -142,7 +142,7 @@ Para fazer login na conta da loja, entre no terminal e digite:
 
 O terminal vai solicitar o Account, ou seja, o nome da conta da loja.
 
-![vtex login](//images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
+![vtex login](https://images.contentful.com/alneenqid6w5/rs5YFeBAtiYG4KuwcOe8Y/91406e5bfbcbad8ce3efbb56b5a31848/vtex__login.png)
 
 Após inserir o Account, digite a senha, se necessário, e pronto. Você fez login na sua conta!
 
@@ -172,7 +172,7 @@ Para voltar ao workspace master, o procedimento é o mesmo:
 
 `vtex use master`
 
-![use master](//images.contentful.com/alneenqid6w5/4SK7JvVupO0sOoGE2As4Yc/e578222b656c74a3b082a6b498a3f04e/use_master.png)
+![use master](https://images.contentful.com/alneenqid6w5/4SK7JvVupO0sOoGE2As4Yc/e578222b656c74a3b082a6b498a3f04e/use_master.png)
 
 ---
 
@@ -213,7 +213,7 @@ Para confirmar que deu tudo certo, entre no browser e acesse a seguinte URL:
 
 Se a tela abaixo está sendo exibida, sua app está linkada.
 
-![Indexjs](//images.contentful.com/alneenqid6w5/6x1Vx9RVKgUCsKscmEqSky/df5c3183c374710d2017b87d63fefff6/Indexjs.png)
+![Indexjs](https://images.contentful.com/alneenqid6w5/6x1Vx9RVKgUCsKscmEqSky/df5c3183c374710d2017b87d63fefff6/Indexjs.png)
 
 Entre no arquivo `Index.js` e altere alguma coisa. Salve e veja a mudança no browser!
 
diff --git a/docs/tutorials/pt/updating-quantity-of-skus-in-inventory.md b/docs/tutorials/pt/updating-quantity-of-skus-in-inventory.md
index 9ec38caef..39d6f0a1c 100644
--- a/docs/tutorials/pt/updating-quantity-of-skus-in-inventory.md
+++ b/docs/tutorials/pt/updating-quantity-of-skus-in-inventory.md
@@ -56,7 +56,7 @@ Lembrando que um pedido pode ter reserva ativa do produto. Caso o produto não t
 
 Os pedidos com itens reservados, continuarão listados como reservados e impossibilitados de serem vendidos. No exemplo abaixo temos o caso em que 10 unidades de Gatorade estão reservadas e os pedidos ainda não faturados. A medida que atualizamos a contagem em estoque, o sistema já simula qual será o resultado. No exemplo, até 10 itens temos estoque negativo, pois os pedidos com reserva ativa continuam listados. [Entenda melhor como funcionam as reservas.](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona/)
 
-![Atualizar Estoque GIF](//images.contentful.com/alneenqid6w5/1lorbuip9ewo8gY8qg8wU0/07e97e612b4711f0f21c205b50e74867/InventoryUpdate.gif)
+![Atualizar Estoque GIF](https://images.contentful.com/alneenqid6w5/1lorbuip9ewo8gY8qg8wU0/07e97e612b4711f0f21c205b50e74867/InventoryUpdate.gif)
 
 
 
diff --git a/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md b/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md
index b75014f35..c027e04c8 100644
--- a/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md
+++ b/docs/tutorials/pt/updating-the-quantity-of-items-in-inventory.md
@@ -45,7 +45,7 @@ _Unidades disponíveis = unidades da última atualização - unidades reservadas
 
 O estoque negativo normalmente ocorre quando há atualização na quantidade de itens de um SKU de um pedido em que os produtos já estavam reservados no inventário. Para evitar essa situação, é importante que a atualização da quantidade de SKUs ocorra com pedidos com status posterior a `Preparando entrega`. Dessa forma, a [reserva já terá sido reconhecida](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona/#reserva-reconhecida) e não haverá conflito entre os itens do inventário com os itens que de fato estão disponíveis para venda.
 
-![gerenciar inventario](//images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/9ce03695fdd2173d9fa079ab2887eb68/gerenciar_inventario.gif)
+![gerenciar inventario](https://images.ctfassets.net/alneenqid6w5/384hm6LEhpNrvqGITDwzZ1/9ce03695fdd2173d9fa079ab2887eb68/gerenciar_inventario.gif)
 
 ## Artigos relacionados
 
diff --git a/docs/tutorials/pt/uploading-a-product-xml.md b/docs/tutorials/pt/uploading-a-product-xml.md
index c6fa77142..deeb13c34 100644
--- a/docs/tutorials/pt/uploading-a-product-xml.md
+++ b/docs/tutorials/pt/uploading-a-product-xml.md
@@ -17,5 +17,5 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 [XML é uma das maneiras de envio de produtos para parceiros](/pt/tutorial/configurando-xml/), como buscadores, por exemplo. Por padrão, a VTEX já vem configurada com diversos modelos de XMLs, bastando que se associe uma coleção para começar a usar!
 
-<video class="wp-video-shortcode" id="video-2573-4" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4?_=4" />[//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4](//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4 "//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4")</video>
+<video class="wp-video-shortcode" id="video-2573-4" width="840" height="473" preload="metadata" controls="controls"><source type="video/mp4" src="//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4?_=4" />[//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4](https://assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4 "//assets.contentful.com/alneenqid6w5/68HY73E6dyKiSWIWGmsgg6/29029a33ec933f5a9da073b01a9082e5/CriandoXML.mp4")</video>
 
diff --git a/docs/tutorials/pt/url-mapping-301-redirect.md b/docs/tutorials/pt/url-mapping-301-redirect.md
index 51958b74a..99a2986b3 100644
--- a/docs/tutorials/pt/url-mapping-301-redirect.md
+++ b/docs/tutorials/pt/url-mapping-301-redirect.md
@@ -58,7 +58,7 @@ Existem duas formas de adicionar e alterar um Mapeamento de URL:
 4. Clique no botão `Import` para realizar a importação da planilha.
 
 5. Baixe a planilha modelo ilustrada abaixo utilizando o botão `Clique aqui`.
-![exemplo-planilha](//images.contentful.com/alneenqid6w5/2Z63gJkADcR2gveT3lncQb/9bbd790becd99acb7b647537eb71c6a9/Screenshot_5.png)
+![exemplo-planilha](https://images.contentful.com/alneenqid6w5/2Z63gJkADcR2gveT3lncQb/9bbd790becd99acb7b647537eb71c6a9/Screenshot_5.png)
 6. Preencha os [campos da planilha](#campos-da-planilha).
 7. Depois de preencher a planilha, clique no botão `Localizar` na tela de importação.
 8. Selecione o arquivo que será importado de seu computador. O arquivo deve ter extensão `.xls` formato `Excel 97-2003 Workbook`.
diff --git a/docs/tutorials/pt/using-orders-managment-filters-in-api.md b/docs/tutorials/pt/using-orders-managment-filters-in-api.md
index f90bf83e9..d6d7ea300 100644
--- a/docs/tutorials/pt/using-orders-managment-filters-in-api.md
+++ b/docs/tutorials/pt/using-orders-managment-filters-in-api.md
@@ -28,19 +28,19 @@ O exemplo utilizado é a API de consulta aos pedidos: http://{NOMEDALOJA}.vtex
 
 Usaremos o filtro pela data de criação do pedido em um intervalo que traga todos os pedidos realizados **há um mês** e que estejam no status **pronto ****para manuseio.**
 
-![](//images.contentful.com/alneenqid6w5/53zjSDeDBe20MkAQa2iqk0/ba1b8b24ddb63e121dd060a79aa1a534/OMS_Filtro5.png)
+![](https://images.contentful.com/alneenqid6w5/53zjSDeDBe20MkAQa2iqk0/ba1b8b24ddb63e121dd060a79aa1a534/OMS_Filtro5.png)
 
-![](//images.contentful.com/alneenqid6w5/3AS1rSk36MAwSIMGkaqsSm/1c496620f9c9669b7c9ccd6078681f8e/OMS_Filtro.png)
+![](https://images.contentful.com/alneenqid6w5/3AS1rSk36MAwSIMGkaqsSm/1c496620f9c9669b7c9ccd6078681f8e/OMS_Filtro.png)
 
-![](//images.contentful.com/alneenqid6w5/jj5tYpFP8WkYicAAIymCa/5157cf41ab647f31e20db895669eabea/OMS_Filtro2.png)
+![](https://images.contentful.com/alneenqid6w5/jj5tYpFP8WkYicAAIymCa/5157cf41ab647f31e20db895669eabea/OMS_Filtro2.png)
 
 Quando feitos os filtros, será gerada uma URL no próprio navegador com os parâmetros selecionados:
-![](//images.contentful.com/alneenqid6w5/WYPqJKIjwkuCO86SMU6sy/d5ad173798f8103c19990eed35709ecf/OMS_Filtro3.png)
+![](https://images.contentful.com/alneenqid6w5/WYPqJKIjwkuCO86SMU6sy/d5ad173798f8103c19990eed35709ecf/OMS_Filtro3.png)
 
 Então, é preciso decodificar a URL para ser interpretada pela interface de REST.
 Uma ferramenta ágil para ajustar isso manualmente é a [URL dencoder](http://meyerweb.com/eric/tools/dencoder/ "URL dencoder").
 
-![](//images.contentful.com/alneenqid6w5/4j6WPSCXq084cMaIcQ8QsE/8dcab3bc07fd714af788cea586293f57/OMS_Filtro4.png)
+![](https://images.contentful.com/alneenqid6w5/4j6WPSCXq084cMaIcQ8QsE/8dcab3bc07fd714af788cea586293f57/OMS_Filtro4.png)
 
 Feito isso, basta copiar a extensão da URL a partir do “?” e colar na estrutura de origem para a URL de request. 
 Ex.: `http://nomedaloja.vtexcommercestable.com.br/api/oms/pvt/orders/?orderBy=creationDate,desc&amp;f_creationDate=creationDate:[2014-09-03T03:00:00.000Z TO 2014-10-04T02:59:59.999Z]&amp;f_statusDescription=Pronto para o manuseio`
diff --git a/docs/tutorials/pt/using-recaptcha-at-checkout.md b/docs/tutorials/pt/using-recaptcha-at-checkout.md
index 246ba99ce..bab574131 100644
--- a/docs/tutorials/pt/using-recaptcha-at-checkout.md
+++ b/docs/tutorials/pt/using-recaptcha-at-checkout.md
@@ -54,15 +54,15 @@ Você pode utilizar reCAPTCHA checkbox (v2). Ou seja, quando aplicável, o usuá
 
 Levando em consideração os fatores mencionados acima, a experiência de compra com cartão de débito ou crédito tende a seguir o fluxo abaixo. Isso minimiza a incidência de alguns tipos de fraudes e ataques com o mínimo de fricção para o usuário.
 
-![reCAPTCHA scenariosPT](//images.contentful.com/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/383565089037ce6be7d7b0a05df2c8fe/reCAPTCHA_scenarios.jpg)
+![reCAPTCHA scenariosPT](https://images.contentful.com/alneenqid6w5/3gA55NZPuxpKOxCZxvbhgj/383565089037ce6be7d7b0a05df2c8fe/reCAPTCHA_scenarios.jpg)
 Como mostrado na imagem acima, existem diferentes possibilidades de resultado neste fluxo:
 
 1. Se o algoritmo do VTEX Criteria não considerar a sessão suspeita, a plataforma prossegue normalmente com a compra.
 
 2. Caso contrário, a interface deverá exibir o reCAPTCHA Checkbox, a qual deverá ser marcada pelo cliente. Se o reCAPTCHA não considerar o comportamento suspeito ao marcar a Checkbox, a compra prossegue normalmente.
-![newCaptchaAnchor](//images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/f4d75c1fab0fc5789b22fb1b259e7560/newCaptchaAnchor.gif)
+![newCaptchaAnchor](https://images.ctfassets.net/alneenqid6w5/2lv7PfOmkakDcSkNbAITtK/f4d75c1fab0fc5789b22fb1b259e7560/newCaptchaAnchor.gif)
 3. Se o reCAPTCHA ainda considera o comportamento suspeito, a interface exibirá o desafio.
-![desafio recaptcha](//images.contentful.com/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/8276208bf8d6db1f086f33df1e8a3641/desafio_recaptcha.png)
+![desafio recaptcha](https://images.contentful.com/alneenqid6w5/3wg7F9nmxJwZ8jxUJKb8OT/8276208bf8d6db1f086f33df1e8a3641/desafio_recaptcha.png)
 4. Se o desafio for resolvido com sucesso, a plataforma prossegue com a compra. Caso contrário, o comportamento é considerado compatível com o de um bot e a plataforma não finaliza a compra.
 
 ## reCAPTCHA v3
diff --git a/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 4913ea208..61c68a105 100644
--- a/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -41,7 +41,7 @@ Apps que têm uma dependência de sessão monitoram mudanças nas suas entradas
 
 Transforms frequentemente disparam outras transforms, repetindo até que nenhuma atualização de parâmetro adicional seja enviada por apps. Esta operação é, naturalmente, cautelosamente monitorada para evitar condições de loop. O diagrama abaixo ilustra um exemplo de ciclo de transform:
 
-![EN - Session Manager](//images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
+![EN - Session Manager](https://images.ctfassets.net/alneenqid6w5/1QWb3hs5wfr3Zj38TnpwHY/162fb09edaf6fca3b5cdf3ce7d5a20b2/Session_Manager.jpg)
 
 1. Uma mudança foi feita no parâmetro de sessão X
 2. A App A monitorava o parâmetro de sessão X, o que disparou a Transform 1
diff --git a/docs/tutorials/pt/using-the-homepage-of-the-admin-panel.md b/docs/tutorials/pt/using-the-homepage-of-the-admin-panel.md
index 059578464..b46f23755 100644
--- a/docs/tutorials/pt/using-the-homepage-of-the-admin-panel.md
+++ b/docs/tutorials/pt/using-the-homepage-of-the-admin-panel.md
@@ -28,7 +28,7 @@ A seção de métricas está organizada em três grandes grupos:
 - Dados de Pagamento;
 - Dados do Catálogo.
 
-![Action Dashboard](//images.contentful.com/alneenqid6w5/5ir6pwnlyMeQEeSOmOyisw/dcad530fb9c0004d32a89a3a6d5492ef/Action_Dashboard.png)
+![Action Dashboard](https://images.contentful.com/alneenqid6w5/5ir6pwnlyMeQEeSOmOyisw/dcad530fb9c0004d32a89a3a6d5492ef/Action_Dashboard.png)
 
 ### Bridge
 
@@ -64,4 +64,4 @@ São exibidos os artigos novos do Help VTEX ou aqueles que foram atualizados rec
 
 Logo abaixo dos artigos, fica a seção **Info e Eventos**, onde exibimos novidades sobre a plataforma, dicas sobre e-commerce, informações sobre eventos de comércio eletrônico e tudo mais que for divulgado pela VTEX.
 
-![APIDocs](//images.contentful.com/alneenqid6w5/1GzmJz7qIwgm0kMq4smSk4/fb98a1d430346f559ada7800ad6cc321/APIDocs.png)
+![APIDocs](https://images.contentful.com/alneenqid6w5/1GzmJz7qIwgm0kMq4smSk4/fb98a1d430346f559ada7800ad6cc321/APIDocs.png)
diff --git a/docs/tutorials/pt/using-tools-html.md b/docs/tutorials/pt/using-tools-html.md
index 9f0b3c158..04766dd26 100644
--- a/docs/tutorials/pt/using-tools-html.md
+++ b/docs/tutorials/pt/using-tools-html.md
@@ -20,13 +20,13 @@ Em alguns momentos o sistema pode ficar inacessível ocasionando assim algumas t
 
 Caso já tenha verificado o status e seja algo somente nesta loja voce pode seguir os passos abaixo para identificar melhor o erro e ter detalhes mais claros para acrescentar em usa comunicaáo com a VTEX .
 Por vezes poderá apresentada uma tela de erro como a mostrada abaixo:
-![IMAGEN1](//images.contentful.com/alneenqid6w5/69e3CvUZi08eyIYCcMKySu/de3d8e24d7e9da57ec26f92e7172e68d/IMAGEN1.png)
+![IMAGEN1](https://images.contentful.com/alneenqid6w5/69e3CvUZi08eyIYCcMKySu/de3d8e24d7e9da57ec26f92e7172e68d/IMAGEN1.png)
 
 Este é uma mensagem amigável  que é exibida quando o sistema não consegue responder a solicitação feita , com esta tela é quase que impossível identificar o erro logo de cara , porem temos como mostrar o que realmente esta ocorrendo por trás desta  mensagem.
 Entre na URL da loja e acrescente no final a terminação /tools.html 
 EX: nomedaloja.vtexcommercestable.com.br/tools.html
 Após isso  será exibido uma tela de controle  como no exemplo abaixo:
-![IMAGEM2](//images.contentful.com/alneenqid6w5/PASltgiJwWAaWc8cCisaQ/469fba8aa9c5686ef25918fc677043a6/IMAGEM2.png)
+![IMAGEM2](https://images.contentful.com/alneenqid6w5/PASltgiJwWAaWc8cCisaQ/469fba8aa9c5686ef25918fc677043a6/IMAGEM2.png)
 
 Após entrar nesta tela você deve desabilitar a exibição de erro amigável  assim você pode printar a verdadeira causa do erro e enviar no chamado para que nossos analistas consigam responder o chamado com maior assertividade como no exemplo abaixo:
 
diff --git a/docs/tutorials/pt/validating-a-layout-before-moving-it-to-production.md b/docs/tutorials/pt/validating-a-layout-before-moving-it-to-production.md
index 38541a7ab..62a59716e 100644
--- a/docs/tutorials/pt/validating-a-layout-before-moving-it-to-production.md
+++ b/docs/tutorials/pt/validating-a-layout-before-moving-it-to-production.md
@@ -34,7 +34,7 @@ Com isso, você pode:
 
 Para encontrar o `LID`, basta acessar o layout pelo Admin, no módulo CMS. Ele fica na seção __Properties__, como indica a imagem abaixo:
 
-![lid](//images.contentful.com/alneenqid6w5/4FISyY6wwg2asGE4Mog2sK/991b8c634b474c336de1754acdb414de/lid.png)
+![lid](https://images.contentful.com/alneenqid6w5/4FISyY6wwg2asGE4Mog2sK/991b8c634b474c336de1754acdb414de/lid.png)
 
 Para acessar a página da loja com o novo layout, você deve inserir um ponto de interrogação ao final da URL e depois o parâmetro `LID`.
 
@@ -53,7 +53,7 @@ Outra alternativa que lhe permite testar mudanças no layout antes de ir para pr
 
 Para encontrar o `WID`, acesse o web site. Ele fica no primeiro campo da tela do web site: __Id do WebSite__.
 
-![wid](//images.contentful.com/alneenqid6w5/ghvd0wl9HqGu2KCWW2Yu2/5e27a13e79134f7ba89863ccd54031a6/wid.png)
+![wid](https://images.contentful.com/alneenqid6w5/ghvd0wl9HqGu2KCWW2Yu2/5e27a13e79134f7ba89863ccd54031a6/wid.png)
 
 Lembre-se que, apesar de com a duplicação do web site você poder alterar os layouts do novo web site de maneira intependente, estes vão consumir os mesmos templates do web site original. 
 
diff --git a/docs/tutorials/pt/view-reindex-log.md b/docs/tutorials/pt/view-reindex-log.md
index 9f1637f60..2d0ba6172 100644
--- a/docs/tutorials/pt/view-reindex-log.md
+++ b/docs/tutorials/pt/view-reindex-log.md
@@ -21,7 +21,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Na verdade, qualquer ação tomada no Full Clean Up fica registrada nessa página.
 
-![fullcleanupLog](//images.contentful.com/alneenqid6w5/4imYxqJjWwog0UYwCIcWY4/a036d799b6de9d34a2e2f810f3780929/fullcleanupLog.png)
+![fullcleanupLog](https://images.contentful.com/alneenqid6w5/4imYxqJjWwog0UYwCIcWY4/a036d799b6de9d34a2e2f810f3780929/fullcleanupLog.png)
 
 O log apresenta as seguintes informações para cada ação:
 - __Data__: data e horário da ação.
diff --git a/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md b/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md
index 1992845ec..e9e51e3bd 100644
--- a/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md
+++ b/docs/tutorials/pt/visao-geral-configuracoes-de-usuario.md
@@ -17,7 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 *Configurações de usuário* são o conjunto de configurações aplicadas ao seu perfil pessoal no Admin, e não relacionadas à sua loja ou conta do seu negócio na VTEX. Para acessar essa página, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e clique no botão **Configurações do usuário**. 
 
-![Admin v4 User settings menu PT](//images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/4128b79a8b245fb113072ca97c5988ae/Admin_v4_User_settings_menu_PT.jpg)
+![Admin v4 User settings menu PT](https://images.ctfassets.net/alneenqid6w5/5WVJereXlPhkKKyXbg7jog/4128b79a8b245fb113072ca97c5988ae/Admin_v4_User_settings_menu_PT.jpg)
 
 Nessa página, que em breve estará no design do Admin v4, é possível realizar as seguintes ações:
 
diff --git a/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md b/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md
index 6fe343ec9..ee848b38f 100644
--- a/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md
+++ b/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md
@@ -21,7 +21,7 @@ No Catálogo, os produtos são organizados por categorias, e as categorias organ
 
 Um exemplo de estrutura de catálogo seria o seguinte:
 
-![img como funciona o catalogo](//images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
+![img como funciona o catalogo](https://images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
 
 <div class="alert alert-warning">
 Não é necessário que a sua árvore de categorias possua três níveis. A hierarquia exibida acima é apenas um exemplo. A quantidade de níveis de categoria a ser criada depende muito do setor de atuação de cada loja.
diff --git a/docs/tutorials/pt/vtex-ad-network-beta.md b/docs/tutorials/pt/vtex-ad-network-beta.md
index e86ec086e..2e9b26a25 100644
--- a/docs/tutorials/pt/vtex-ad-network-beta.md
+++ b/docs/tutorials/pt/vtex-ad-network-beta.md
@@ -45,7 +45,7 @@ Atualmente, a VTEX disponibiliza um único formato de anúncio: produtos patroci
 
 Veja abaixo um exemplo da exibição deste formato:
 
-![vtex_ad_network_sponsored_PT](//images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
+![vtex_ad_network_sponsored_PT](https://images.ctfassets.net/alneenqid6w5/1PlUii3Hd3Tma9trnhqnLS/12e38a4f482a08d13f823b17a88fbf5b/vtex_ad_network_sponsored.png)
 
 Lojas participantes do **VTEX Ad Network** poderão [configurar a quantidade de espaços de anúncio](https://help.vtex.com/pt/tutorial/advertising-with-vtex-ad-network-beta--5WoXcJzHc7EQElpPjziqse#criando-uma-campanha) que disponibilizarão em cada um destes contextos na loja.
 
diff --git a/docs/tutorials/pt/vtex-admin-start-here.md b/docs/tutorials/pt/vtex-admin-start-here.md
index bfac7ffec..d4a29f667 100644
--- a/docs/tutorials/pt/vtex-admin-start-here.md
+++ b/docs/tutorials/pt/vtex-admin-start-here.md
@@ -19,7 +19,7 @@ O Admin permite que os comerciantes gerenciem toda sua experiência de comércio
 
 ## Página inicial
 
-![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 A página inicial oferece uma visão geral de alto nível da sua loja, como uma cabine de comando para as suas operações de comércio digital. Por isso, ela se chama [Visão Geral](https://help.vtex.com/pt/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -28,7 +28,7 @@ Assim que você fizer login no Admin, verá métricas e gráficos úteis para mo
 ## Menu de navegação 
 Nossos menus de navegação lateral e barra superior agrupam categorias similares para reduzir as distrações e ajudar a sua equipe a encontrar o que precisa mais rapidamente. 
 
-![menu de navegação admin SEP2023](//images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/40fe4023fbe2c890f512761ae1ff77ed/admin-navigation.png)
+![menu de navegação admin SEP2023](https://images.ctfassets.net/alneenqid6w5/2uRMUQWZoiRiuEL70siDJ1/40fe4023fbe2c890f512761ae1ff77ed/admin-navigation.png)
 
 Na topbar, você pode usar a barra de busca global para pesquisar páginas do Admin VTEX ou pedidos da sua loja. Por padrão, a busca está configurada para `Páginas`. Para buscar um pedido, clique sobre a barra, selecione a opção `Pedidos` e utilize algum dos seguintes critérios:
 
@@ -58,7 +58,7 @@ Também é possível utilizar a barra de busca na parte superior do Admin VTEX p
 
 ### Central de Informações
 
-![central de informações admin SEP2023](//images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/d344e0470f3980a3a7323216e46a95c8/Information_center.gif)
+![central de informações admin SEP2023](https://images.ctfassets.net/alneenqid6w5/7a9d2QspPcT4w9BbdpQiR6/d344e0470f3980a3a7323216e46a95c8/Information_center.gif)
 
 É aqui que reunimos todos os links úteis do nosso ecossistema VTEX, para ajudá-lo(a) a aproveitar a nossa plataforma ao máximo. C Clicando no botão <i class='fa fa-question-circle-o'></i> na barra superior, você pode acessar nosso [Help Center](https://help.vtex.com), [Developer Portal](https://developers.vtex.com/), [Status da Plataforma](https://status.vtex.com/), [blog](https://vtex.com/pt/blog/) e central de suporte.
 
@@ -70,7 +70,7 @@ O botão Enviar feedback permite que um usuário possa enviar comentários a res
 
 Neste momento um formulário do Google será exibido para que você possa enviar seu feedback. Após o envio, você receberá um email.
 
-![Botão feedback - PT -](//images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/b9b9ecdd1ade0fce9e3a29cd6df1432c/Bot_o_feedback_-_PT_-.gif)
+![Botão feedback - PT -](https://images.ctfassets.net/alneenqid6w5/6OUJxw2vU5UhLX16TOMAts/b9b9ecdd1ade0fce9e3a29cd6df1432c/Bot_o_feedback_-_PT_-.gif)
 
 #### Formulário do feedback
 O objetivo principal das perguntas no formulário de feedback é coletar informações detalhadas sobre as experiências e percepções em relação ao produto no Admin VTEX.
@@ -98,7 +98,7 @@ Este processo de envio de feedback não deve ser utilizado para criar um ticket
 
 ### Configurações da conta e do usuário
 
-![configurações de avatar admin SEP2023](//images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/34b6240c3917892dc8c34f2c5efa4afd/Avatar_settings2.gif)
+![configurações de avatar admin SEP2023](https://images.ctfassets.net/alneenqid6w5/52uxBkDXceU5apwZe4ZkaQ/34b6240c3917892dc8c34f2c5efa4afd/Avatar_settings2.gif)
 
 Seu avatar de perfil, reúne todas as configurações relacionadas ao seu usuário e à sua conta. Através do avatar, você pode acessar as [Configurações do usuário](https://help.vtex.com/pt/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Configurações da conta](https://help.vtex.com/pt/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), e [Faturas](https://help.vtex.com/pt/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC), alterar o idioma do seu Admin e encerrar a sessão. 
 
diff --git a/docs/tutorials/pt/vtex-admin-start-here1.md b/docs/tutorials/pt/vtex-admin-start-here1.md
index 0b765bce8..d5ff64594 100644
--- a/docs/tutorials/pt/vtex-admin-start-here1.md
+++ b/docs/tutorials/pt/vtex-admin-start-here1.md
@@ -19,7 +19,7 @@ O Admin permite que os comerciantes gerenciem toda sua experiência de comércio
 
 ## Página inicial
 
-![Store overview gif PT](//images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
+![Store overview gif PT](https://images.ctfassets.net/alneenqid6w5/4vKmiLmTVUtaxn5vzpX5xq/b9a4a299f80286eadf1727cd5057a64c/Store_overview_gif_PT.gif)
 
 A página inicial do nosso Admin foi redesenhada para oferecer uma visão geral de alto nível da sua loja, como uma cabine de comando para as suas operações de comércio digital. Por isso, ela se chama [Visão Geral](https://help.vtex.com/pt/v4/docs/visao-geral-da-loja--6mcM4LPUqQxSiXY6uFtXZy).
 
@@ -29,23 +29,23 @@ Assim que você fizer login no Admin, verá métricas e gráficos úteis para mo
 
 Tudo que você precisa para administrar sua loja VTEX continua disponível no Admin, mas agora com uma organização mais simples. Nossos menus de navegação lateral e barra superior foram reformulados do zero, agrupando categorias similares de forma mais clara para reduzir as distrações e ajudar a sua equipe a encontrar o que precisa mais rapidamente. Também é possível utilizar a barra de busca para encontrar seções específicas no menu lateral.
 
-![New Admin Shell](//images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
+![New Admin Shell](https://images.ctfassets.net/alneenqid6w5/4Q4sQVxNy82zlFT2rmqaCo/f5e423ed52f3d468227155b73d74f163/New_Admin_Shell__1_.png)
 
 ### Central de Informações
 
 É aqui que reunimos todos os links úteis do nosso ecossistema VTEX, para ajudá-lo(a) a aproveitar a nossa plataforma ao máximo. Clicando no botão `?` na barra superior, você pode acessar nosso Help Center, Developer Portal, Status da Plataforma, blog e páginas de suporte.
 
-![Information center](//images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
+![Information center](https://images.ctfassets.net/alneenqid6w5/6lVqieCabdmgG53teixwyg/06dbecc541f55c4644134af302bdfd0c/Information_center.gif)
 
 ### Configurações da Loja
 
 Para esta experiência, reunimos todas as configurações de todas as seções do seu Admin em uma guia específica: [Configurações da Loja](https://help.vtex.com/pt/v4/docs/visao-geral-configuracoes-da-loja--5e1Mj7oBDq2NEYJ7cpDdR4). Através dessa melhoria, você pode acessar facilmente todas as configurações que afetam cada serviço da sua conta.
 
-![Store settings](//images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
+![Store settings](https://images.ctfassets.net/alneenqid6w5/3Mypjey9ors57oaq2wKQc3/9fc79445cb6a43dc62ccc99751d5981a/Store_settings.gif)
 
 ### Configurações da conta e do usuário
 
-![Avatar settings](//images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
+![Avatar settings](https://images.ctfassets.net/alneenqid6w5/mAIHwG3IM1E0BfcDg7orj/5542e02ec58e87d97f7e14960f5de69c/Avatar_settings.gif)
 
 Seu avatar de perfil, no canto superior direito, agora reúne todas as configurações relacionadas ao seu usuário e à sua conta. Através do avatar, você pode acessar as [Configurações do usuário](https://help.vtex.com/pt/v4/docs/user-settings-overview--1qYAvOTZBVYMosJ7tQm3Ry), [Configurações da conta](https://help.vtex.com/pt/v4/docs/account-settings-overview--159BmXTQhaP44wLxtPff6r), e [Faturas](https://help.vtex.com/pt/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC), alterar o idioma do seu Admin e encerrar a sessão. 
 
diff --git a/docs/tutorials/pt/vtex-agreement.md b/docs/tutorials/pt/vtex-agreement.md
index a3511dc13..31a75008f 100644
--- a/docs/tutorials/pt/vtex-agreement.md
+++ b/docs/tutorials/pt/vtex-agreement.md
@@ -17,7 +17,7 @@ subcategory: 22TaEgFhwE6a6CG2KASYkC
 
 O contrato VTEX, ou acordo comercial, é composto por duas partes: o [MSA (Master Service Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/) e o **Anexo 1 Order Form** para prestação de serviços às empresas ou o [MPA (Master Partner Agreement)](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) e os **Termos e condições específicos da parceria.**
 
-![Contrato VTEX](//images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/cb616e04ff8e452d9f286210d9ad4c57/PT.png)
+![Contrato VTEX](https://images.ctfassets.net/alneenqid6w5/3PQyLQGwJQ4iS28cP5C4Bf/cb616e04ff8e452d9f286210d9ad4c57/PT.png)
 
 O [Master Service Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/) e o [Master Partner Agreement](https://vtex.com/us-en/privacy-and-agreements/agreements/#:~:text=Master%20Services%20Agreement,Partner%20Agreement) são os acordos mestre de serviço e parceria, respectivamente, que regulam o relacionamento entre VTEX e cliente ou VTEX e parceiro. Ambos variam de acordo com a região em que a empresa ou o parceiro estão localizados. 
 
diff --git a/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
index 4cd5d780c..b60343c27 100644
--- a/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
+++ b/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
@@ -34,7 +34,7 @@ Veja abaixo algumas dicas para aproveitar ao máximo essa funcionalidade:
 
 Inicie ajustando o fuso horário e selecionando a loja que deseja monitorar na Visão geral em tempo real.
 
-![fuso-pt](//images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/27380d6a540c52fb03aaf6a19ccdafb4/fuso-pt.png)
+![fuso-pt](https://images.ctfassets.net/alneenqid6w5/7sfMnNC4GYLOU0tiiunxvR/27380d6a540c52fb03aaf6a19ccdafb4/fuso-pt.png)
 
 ### Filtro de referência
 
@@ -51,26 +51,26 @@ Para configurar a referência, siga os passos a seguir:
 Uma comparação útil durante a Black Week é com a mesma data do ano anterior. No ajuste de referência, defina preferencialmente uma data entre 21/11/2022 e 27/11/2022, idealmente, os mesmos dias da semana. <br>Esta opção está disponível para clientes que utilizavam a plataforma VTEX nesse período no ano passado.</br>
 </div>
 
-![referencia-pt](//images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/c92d901550424a6ce3e095a28fd1f8db/referencia-pt.png)
+![referencia-pt](https://images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/c92d901550424a6ce3e095a28fd1f8db/referencia-pt.png)
 
 ### Filtro de visualização
 
 - **Acompanhe a performance do dia com a visão acumulada:** a **visão acumulada** mostra o monitoramento da performance de vendas do seu ecommerce minuto a minuto, trazendo insights para ajustes rápidos na operação.  
 Para selecionar o modo **visão acumulada** no dashboard, clique em **Visualização<i class="fas fa-angle-down"></i> > Acumulado.**   
 
-![acumulada-pt](//images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/90c6937f448f6b02da0721181b8ae552/acumulada-pt.png)
+![acumulada-pt](https://images.ctfassets.net/alneenqid6w5/12S4L4jhi6FwkoW3TsNnAP/90c6937f448f6b02da0721181b8ae552/acumulada-pt.png)
 
 - **Acompanhe a performance das últimas horas:** a **visão das últimas 2 horas** apresenta as métricas isoladas minuto a minuto, o que é importante para assegurar a estabilidade operacional da sua loja durante o evento.  
 Para selecionar o modo **Últimas 2 horas** no dashboard, clique em **Visualização <i class="fas fa-angle-down"></i> > Últimas 2 horas.**
 
-![horas-pt](//images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/76b3ea0dbacfa045ebd05cd6ae939796/horas-pt.png)
+![horas-pt](https://images.ctfassets.net/alneenqid6w5/7lFOUhQFyRgGFjooVOuvDy/76b3ea0dbacfa045ebd05cd6ae939796/horas-pt.png)
 
 ### Métricas  
 
 Com a **Visão geral em tempo real,** obtenha insights importantes sobre sua estratégia de vendas. Por exemplo, use os "produtos mais vendidos" como referência para impulsionar campanhas e alavancar ainda mais seus resultados.  
 Para visualizar os produtos mais vendidos, no quadro de **Métricas,** clique no botão <i class="fas fa-ellipsis-v"></i> e selecione **Produtos mais vendidos.**
 
-![mais-vendidos-pt](//images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/9c99acbbf617a57ef431bfec05873aa9/mais-vendidos-pt.png)
+![mais-vendidos-pt](https://images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/9c99acbbf617a57ef431bfec05873aa9/mais-vendidos-pt.png)
 
 <div class="alert alert-info">
 Para análises ou acompanhamentos de períodos maiores, recomendamos o uso do nosso dashboard de performance de vendas, que será detalhado na próxima pergunta.
@@ -84,7 +84,7 @@ Para um acompanhamento diário da operação do seu ecommerce, o [dashboard de P
 - **Data**  
 Ao acessar o dashboard, o primeiro passo é definir o **Período principal** e **Comparar com**. Se estiver analisando após a Black Week, selecione `Última semana` para comparar com a Black Week do ano passado (opção disponível se você já era cliente VTEX). Durante a Black Week, prefira `Personalizar` e escolha os dias específicos para análise.
 
-![vendas-data-pt](//images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/e55170c03fa62f9df615a8be66d0dcd6/vendas-data-pt.png)
+![vendas-data-pt](https://images.ctfassets.net/alneenqid6w5/1ohgIwKBI0qsKrScdHUdE4/e55170c03fa62f9df615a8be66d0dcd6/vendas-data-pt.png)
 
 - **Filtros combinados**  
 Os dados apresentados no dashboard de vendas podem ser segmentados através dos filtros combinados, um exemplo é o filtro de categoria. Para adicionar um novo filtro, siga os seguintes passos:  
@@ -95,7 +95,7 @@ Os dados apresentados no dashboard de vendas podem ser segmentados através dos
 
 É possível explorar outros filtros conforme a necessidade e os aspectos do seu ecommerce.  
 
-![adicionar-filtro-pt](//images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/f6e9ab2ea49d191a99cabda460179bc7/adicionar-filtro-pt.png)
+![adicionar-filtro-pt](https://images.ctfassets.net/alneenqid6w5/71V1UF9tUvs1BtIFw9BRgZ/f6e9ab2ea49d191a99cabda460179bc7/adicionar-filtro-pt.png)
 
 ### Métricas  
 
@@ -109,22 +109,22 @@ Durante a Black Week, esse dashboard pode ser utilizado para analisar as seguint
 - Ticket médio (aprovado)
 - Pedidos (cancelados)
 
-![mudar-metrica-pt](//images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/0c821bba0f892f370cb964c3066ca260/mudar-metrica-pt.png)
+![mudar-metrica-pt](https://images.ctfassets.net/alneenqid6w5/VI0G6Wp0QYu85mUQN9hA9/0c821bba0f892f370cb964c3066ca260/mudar-metrica-pt.png)
 
 - **Performance da semana**  
 Após os ajustes, compare o desempenho da semana atual com a Black Week do ano passado para identificar tendências e oportunidades.  
 
-![performance-semana-pt](//images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/b6f43694faee09f289227978a311a797/performance-semana-pt.png)
+![performance-semana-pt](https://images.ctfassets.net/alneenqid6w5/5UOlx5RSYyY9LQbryuMlYw/b6f43694faee09f289227978a311a797/performance-semana-pt.png)
 
 - **Análise da tabela**   
 Analise a tabela detalhada para obter insights mais profundos. Por exemplo, a análise por SKU pode revelar quais produtos devem ser destacados em futuras campanhas.
 
-![analise-tabela-pt](//images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/05e608c70c457650ee826c85cb7a18b5/analise-tabela-pt.png)
+![analise-tabela-pt](https://images.ctfassets.net/alneenqid6w5/5bcuf4WK9hCMAyrKjfvUUV/05e608c70c457650ee826c85cb7a18b5/analise-tabela-pt.png)
 
 - **Salve sua visualização**   
 Para consultas futuras, salve a configuração do seu dashboard. Clique em **Gestão de vendas > <i class="fas fa-plus"></i>  > Adicione um nome > `Criar`** para guardar sua visualização personalizada.  
 
-![criar-exibição-pt](//images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/f3f76fdffa9837442e414b42aae75ac3/criar-exibi__o-pt.png)
+![criar-exibição-pt](https://images.ctfassets.net/alneenqid6w5/4JFfJdUqSKhh3vqO2Jdq2Q/f3f76fdffa9837442e414b42aae75ac3/criar-exibi__o-pt.png)
 
 ## Por que minhas métricas estão diferentes da tela de Pedidos do Admin?  
 
@@ -135,7 +135,7 @@ Há alguns motivos que podem levar a diferenças entre as métricas da Visão ge
 - **Tempo de atualização diferente:** a tela Visão geral em tempo real tem um tempo de atualização de cerca de 1 a 3 minutos. Portanto, é comum haver uma pequena discrepância (de 1 a 3% do total) entre as duas telas.  
 - **Fórmula de cálculo de receita:** as métricas na Visão geral em tempo real não consideram descontos, frete, taxas e promoções no cálculo da receita, enquanto a tela de Pedidos considera esses fatores.  
 
-![selecao-loja-pt](//images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/89439bd5b253d4c38eacbdb441df0d5a/selecao-loja-pt.png)
+![selecao-loja-pt](https://images.ctfassets.net/alneenqid6w5/1REIeF2xgDkIW8JuxjIWwx/89439bd5b253d4c38eacbdb441df0d5a/selecao-loja-pt.png)
 
 Para ver as métricas combinadas de todas as lojas,acesse o dashboard **Performance de vendas,** que apresenta dados agregados com uma taxa de atualização de aproximadamente 90 minutos. 
 
@@ -143,11 +143,11 @@ Para ver as métricas combinadas de todas as lojas,acesse o dashboard **Performa
   No <b>dashboard Visão geral em tempo real,</b> ecommercess que operam com mais de uma moeda têm seus pedidos somados somente na moeda mais utilizada em suas vendas.<br>Para comparar com a tela de <b>Pedidos,</b> você deve somar o total de pedidos de todas as suas moedas.</br>
 </div>  
 
-![todos-os-pedidos-pt](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)
+![todos-os-pedidos-pt](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)
 
 - **Fuso horário:** este filtro está disponível na **Visão geral.** Se usar um fuso horário diferente do padrão da tela de Pedidos (que é seu fuso horário atual), as métricas não serão iguais. Ajuste o fuso horário conforme necessário.  
 
-![vendas-fuso-pt](//images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/cb0e95d1cb6606230099bc85855254c6/vendas-fuso-pt.png)
+![vendas-fuso-pt](https://images.ctfassets.net/alneenqid6w5/3PQegjpVrlr4JlBs7fR2Cv/cb0e95d1cb6606230099bc85855254c6/vendas-fuso-pt.png)
 
 ## Por que não tenho dados de sessões ou taxa de conversão?  
 
@@ -157,7 +157,7 @@ No entanto, é importante saber que nosso script não captura dados de sessões
 
 Se você notar a ausência desses dados, é possível que isso se deva a uma dessas limitações. Recomendamos verificar as configurações do script e possíveis personalizações no frontend que possam estar afetando a captura de dados.
 
-![vendas-visao-geral-pt](//images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/c20776ac629c196881678e0a720f5e86/vendas-visao-geral-pt.png)  
+![vendas-visao-geral-pt](https://images.ctfassets.net/alneenqid6w5/2Lywp5C24kGVVhUHriyug8/c20776ac629c196881678e0a720f5e86/vendas-visao-geral-pt.png)  
 
 ## Por que as minhas métricas de taxa de conversão, novas sessões ou funil de vendas não batem com os números das minhas ferramentas internas?  
 
@@ -175,8 +175,8 @@ Para definir qual moeda será exibida, avaliamos qual é a moeda mais utilizada
 
 Como resultado, se você opera com mais de uma moeda, é importante somar o total de pedidos da tela de Pedidos do Admin de todas as suas moedas para corresponder ao dado de pedidos apresentado na Visão geral em tempo real.  
 
-![todos-os-pedidos-pt](//images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)  
-![monitoramento-pt](//images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/cd0ac69320e37428e59c1a7770895632/monitoramento-pt.png)  
+![todos-os-pedidos-pt](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)  
+![monitoramento-pt](https://images.ctfassets.net/alneenqid6w5/3Kmi0wL5ie28LIIFZlLIzN/cd0ac69320e37428e59c1a7770895632/monitoramento-pt.png)  
 
 ## Por que o número de pedidos da análise de funil de vendas não bate com o da parte de Monitoramento?
 
@@ -186,8 +186,8 @@ Por outro lado, os dados do funil de vendas são coletados da base de navegaçã
 
 Como resultado, é comum que o número de pedidos no funil de vendas seja menor do que na parte de monitoramento, que apresenta uma visão mais ampla das vendas da loja, incluindo canais externos à plataforma VTEX.  
 
-![taxa-conversão-pt](//images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/837f35d360d6b1c7fad1089e39fb4119/taxa-convers_o-pt.png)  
-![novas-sessoes-pt](//images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/7f9a00ffd9e4bf2cf5c6718403e0c0ab/novas-sessoes-pt.png)  
+![taxa-conversão-pt](https://images.ctfassets.net/alneenqid6w5/3PTACRp0lgoWd35Mavp9Fj/837f35d360d6b1c7fad1089e39fb4119/taxa-convers_o-pt.png)  
+![novas-sessoes-pt](https://images.ctfassets.net/alneenqid6w5/2mMweozEf0zpcmSTxLiU94/7f9a00ffd9e4bf2cf5c6718403e0c0ab/novas-sessoes-pt.png)  
 
 ## Por que a nova Visão geral está em uma URL separada?
 
diff --git a/docs/tutorials/pt/vtex-do-interface.md b/docs/tutorials/pt/vtex-do-interface.md
index 3951bf161..a3f777957 100644
--- a/docs/tutorials/pt/vtex-do-interface.md
+++ b/docs/tutorials/pt/vtex-do-interface.md
@@ -17,7 +17,7 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 O VTEX DO é um gerenciador de tarefas criadas automaticamente pelo Admin VTEX, para que a equipe de ecommerce da sua loja as realize manualmente. Para acessá-lo, em seu Admin VTEX, vá em **Pedidos > [Todos os pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos--2QTduKHAJMFIZ3BAsi6Pi)** e clique no ícone de caixa de entrada, localizado no canto inferior direito da página. Ao clicar no ícone, um modal se abrirá com a lista de tarefas relacionadas aos pedidos da loja. 
 
-![VTEX Do overview PT](//images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
+![VTEX Do overview PT](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
 
 <div class = "alert alert-info">
 Somente usuários com o perfil de acesso <a href = "https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> podem realizar tarefas pelo VTEX DO. 
@@ -116,7 +116,7 @@ As tarefas gerenciadas por meio do VTEX DO podem incluir mensagens de todos os s
 
 ## Detalhes da tarefa
 
-![VTEX Do details PT](//images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/08c283d0b9bcebf7da71bd78c0d7eeec/VTEX_Do_details_PT.jpg)
+![VTEX Do details PT](https://images.ctfassets.net/alneenqid6w5/mPby3BuhZYAwGyFuII8mr/08c283d0b9bcebf7da71bd78c0d7eeec/VTEX_Do_details_PT.jpg)
 
 Ao clicar no nome de uma tarefa da lista, você é redirecionado para o modal de detalhes da tarefa, que apresenta mais informações sobre a tarefa e ações para resolvê-la. São apresentados os seguintes campos:
 
diff --git a/docs/tutorials/pt/vtex-insurance.md b/docs/tutorials/pt/vtex-insurance.md
index 5014990b6..5020e5086 100644
--- a/docs/tutorials/pt/vtex-insurance.md
+++ b/docs/tutorials/pt/vtex-insurance.md
@@ -55,7 +55,7 @@ Após a instalação do VTEX Insurance, é necessário realizar a preparação d
 5. Após a criação do campo **Garantia do Fabricante**, defina o período desejado de garantia. No campo **Valor Padrão**, é recomendado o valor 12, representando um período de 12 meses.
 6. [Crie uma categoria](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3UYjVS03JbleGPh0Ckpic1?&utm_source=autocomplete) específica para o produto de seguro.
 7. [Crie o produto](https://help.vtex.com/pt/tutorial/produtos-e-skus-beta--2ig7TmROlirWirZjFWZ3By?&utm_source=autocomplete#criar-produto) de seguro.
-8. [Crie SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) de seguro. É recomendada a criação de mais de três SKUs para cada seguro.![Insurance - SKUs](//images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/763ed10aa72e1f453bca4e858b4347e1/image1.png)
+8. [Crie SKUs](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY) de seguro. É recomendada a criação de mais de três SKUs para cada seguro.![Insurance - SKUs](https://images.ctfassets.net/alneenqid6w5/7z6EX1cFT3l5wmnlX5LQk1/763ed10aa72e1f453bca4e858b4347e1/image1.png)
 9. [Vincule os SKUs criados](https://help.vtex.com/pt/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX?&utm_source=autocomplete) com o seller da Assurant.
 10.  [Vincule o seguro com o produto](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106#preencher-especificacoes-de-produto) desejado.
 
@@ -69,7 +69,7 @@ Após a preparação do catálogo, sua loja já tem o vínculo do seguro com os
 Siga os passos abaixo para configurar seu app VTEX Insurance.
 
 ### Company Information
-1. ![Insurance Configuration](//images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/343aefaafe713ae74ab488f87caf4b55/image5.png)
+1. ![Insurance Configuration](https://images.ctfassets.net/alneenqid6w5/27tKnogbpFLSaeGPW4OnkZ/343aefaafe713ae74ab488f87caf4b55/image5.png)
 1. Preencha a seção com as seguintes informações:
 
 - **Email**: email da loja.
@@ -85,7 +85,7 @@ Siga os passos abaixo para configurar seu app VTEX Insurance.
 2. Clique em `Submit`.
 
 ### Items bound to insurance items
-![Items Bound to Source Items](//images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/e55e7f2af44167b5885af398cfda7637/image6.png)
+![Items Bound to Source Items](https://images.ctfassets.net/alneenqid6w5/6E68A1BaKeUzAgZuzD7KIY/e55e7f2af44167b5885af398cfda7637/image6.png)
 
 1. Selecione os códigos que representam os tipos de seguro desejados para a coleção criada. 
 2. Vincule os SKUs criados com os planos de seguro: você deverá incluir o plano de seguro seguido pelo SKU ID.
@@ -94,13 +94,13 @@ Se desejar vincular mais de um plano de seguro, como o de **Roubo e Furto Qualif
 3. Clique em `Submit`.      
 
 ### Warranty field name
-![Warranty Field Name](//images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/441c24ddc67aa0182fbaad41b6ca4f86/image2.png)
+![Warranty Field Name](https://images.ctfassets.net/alneenqid6w5/215SqlxeJ3yFSZjfGnuJRl/441c24ddc67aa0182fbaad41b6ca4f86/image2.png)
 
 1. Especifique o campo de garantia do fabricante, indicando o nome da garantia utilizada no catálogo.
 2. Clique em `Submit`.
 
 ### Insurance attachment setup
-![Attachement Setup](//images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/976dc38542cfe701e45e8ce0eec936b1/image7.png)
+![Attachement Setup](https://images.ctfassets.net/alneenqid6w5/7wpyDOdmdsK2VqOOUbqrfr/976dc38542cfe701e45e8ce0eec936b1/image7.png)
 
 1. [Crie um anexo](https://help.vtex.com/pt/tutorial/cadastrar-um-anexo) para a Assurant com as informações recebidas pelo suporte na contratação do serviço.
 2. Em **Seguro > Configuração**, clique em `Add attachment` na seção **Insurance** **attachment setup**.
@@ -109,7 +109,7 @@ Se desejar vincular mais de um plano de seguro, como o de **Roubo e Furto Qualif
 5. Clique em `Salvar`.
 
 ### Manual pricing setup
-![Manual Pricing](//images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/59f5683a077151a789969ff64b7b5aac/image4.png)
+![Manual Pricing](https://images.ctfassets.net/alneenqid6w5/a1wDUYo5UhkR09keQU6WG/59f5683a077151a789969ff64b7b5aac/image4.png)
 
 1. Ative o manual pricing na sua loja.
 2. Clique em `Done, next`.
diff --git a/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
index 97c5878e1..082705b33 100644
--- a/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -43,7 +43,7 @@ O VTEX Intelligent Search Multi-idioma permite que você personalize a experiên
 ### Regras de merchandising
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Regras de merchandising — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Regras de merchandising__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas a Regra de Merchandising será aplicada através da seleção dos idiomas desejados, conforme mostrado na figura abaixo.
 
-![img regrasmerch intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/000fe10fd8752c5996afdea9a4bc8e9a/01-merchrules-pt.png)
+![img regrasmerch intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/3Pv8xpcvB43bLALrijD1UO/000fe10fd8752c5996afdea9a4bc8e9a/01-merchrules-pt.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Regras de merchandising no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/2FpbarYzsnbg7aZZn3TGF8).
 
@@ -57,7 +57,7 @@ Existem duas formas de configurar Sinônimos em uma loja multi-idioma no Admin:
 #### Criar Sinônimos via formulário
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Sinônimos — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Sinônimos__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Sinônimos cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
 
-![img sinonimos intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/d513d8a4b124aa077b447ce9a1d4adb8/02-sinonimos-pt.png)
+![img sinonimos intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/12CjlIh67TyloFOBPkE72x/d513d8a4b124aa077b447ce9a1d4adb8/02-sinonimos-pt.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Sinônimos no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
@@ -81,7 +81,7 @@ Para saber mais sobre a importação de planilha de Sinônimos, leia nosso artig
 
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Redirecionamentos — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Redirecionamentos__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Redirecionamentos cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
 
-![img redirecionamentos intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/38bda1599742284c81ed067b2330514d/03-redirecionamentos-pt.png)
+![img redirecionamentos intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/2f245NNeb0APEgeQGj6bTg/38bda1599742284c81ed067b2330514d/03-redirecionamentos-pt.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Redirecionamentos no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4Gd2wLQFbCwTsh8RUDwSoL).
 
@@ -89,6 +89,6 @@ Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Redire
 
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Banners — encontrada no Admin VTEX em __Storefront__ > __Banners__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Banners cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
 
-![img banner intelligentsearchmultilanguage PT](//images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/9c5e675df49840e3fa4db7437f866524/image_8.png)
+![img banner intelligentsearchmultilanguage PT](https://images.ctfassets.net/alneenqid6w5/2TeFZzq8LxaVApotGBfemL/9c5e675df49840e3fa4db7437f866524/image_8.png)
 
 Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Banners no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4ViKEivLJtJsvpaW0aqIQ5).
diff --git a/docs/tutorials/pt/vtex-invoice-notifier.md b/docs/tutorials/pt/vtex-invoice-notifier.md
index c7dc446a7..06ebe2573 100644
--- a/docs/tutorials/pt/vtex-invoice-notifier.md
+++ b/docs/tutorials/pt/vtex-invoice-notifier.md
@@ -15,7 +15,7 @@ legacySlug: vtex-invoice-notifier
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-![invoice-flow](//images.ctfassets.net/alneenqid6w5/1J8NLy4mw7miEPixtV20G8/80c960a20017f2058209c58681fae862/invoice-flow.svg)
+![invoice-flow](https://images.ctfassets.net/alneenqid6w5/1J8NLy4mw7miEPixtV20G8/80c960a20017f2058209c58681fae862/invoice-flow.svg)
 
 ## Instalação da app - VTEX Invoice Notifier
 
@@ -25,7 +25,7 @@ Usuário deve fazer instalação da APP através da VTEX App Store - apps.vtex.c
 
 Ao realizar a instalação, uma página de configuração será exibida, nela o usuário insere o endpoint de comunicação com o sistema responsável pela emissão das notas.
 
-![install-app](//images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
+![install-app](https://images.ctfassets.net/alneenqid6w5/1QCqfd7Yc3lBF2BWUjPQ2g/888f9a2e18a90fa92f7b8ad32048d17d/install-app.png)
 
 ## OMS notificar faturador
 
@@ -33,9 +33,9 @@ Com o endpoint cadastrado na APP o OMS passa a reconhecer que está habilitado p
 
 O operador deve, no pedido, selecionar o pacote ou os itens que deseja faturar e gerar uma nova notificação:
 
-![notify-invoicer1](//images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
+![notify-invoicer1](https://images.ctfassets.net/alneenqid6w5/1pTJ8sEgLo7cpyYcVFQKxR/7a0b066fc646d1941f3ac704023ea5f7/notify-invoicer1.png)
 
-![notify-invoicer2](//images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
+![notify-invoicer2](https://images.ctfassets.net/alneenqid6w5/59qqed77NuvF0rrlpdABe9/1108b18f8eba54bf25c6766803578b42/notify-invoicer2.png)
 
 quando o usuário do OMS apertar o botão __Request Invoice__, a app irá realizar um request POST no endpoint cadastrado na APP com o seguinte BODY exemplo:
 
@@ -59,7 +59,7 @@ Essa propriedade deve ser utilizada para saber qual endereço enviar o Invoice.
 
 Uma vez notificado com sucesso, a APP grava no Banco de Dados (VBASE) essa notificação.
 
-![callBackProperty](//images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
+![callBackProperty](https://images.ctfassets.net/alneenqid6w5/POhuHliun9MO0hYgTmPvr/1df598855b888b113ef035df3502134d/callBackProperty.png)
 
 ## Faturador pegar detalhes da nota
 
@@ -170,7 +170,7 @@ Pedidos de Pickup podem conter a identificação do cliente ou não. Um pedido f
 
 A forma base de identificar se um pedido é Delivery ou Pickup é através do objeto __shippingData.logisticsInfo[0].deliveryChannel__
 
-![shipping-type](//images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
+![shipping-type](https://images.ctfassets.net/alneenqid6w5/6p9yfYsHRbz4xCX9sjrGx9/cfeb4ae8afe0d47f53e49a556c51ccc6/shipping-type.png)
 
 ## Inserir nota fiscal no pedido
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-insights.md b/docs/tutorials/pt/vtex-pick-and-pack-insights.md
index 33640f914..fb6a1bd3c 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-insights.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-insights.md
@@ -21,7 +21,7 @@ Essa funcionalidade está na fase Beta fechado, o que significa que somente clie
 
 **Insights** é uma página do Admin VTEX que exibe informações sobre o desempenho da sua loja em relação ao VTEX Pick and Pack.
 
-![pick-pack-insights-pt](//images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/2764b70414073ede61f4481cd159ae6e/image.png)
+![pick-pack-insights-pt](https://images.ctfassets.net/alneenqid6w5/3C3eQIIJczIaJjRLRpFTFK/2764b70414073ede61f4481cd159ae6e/image.png)
 
 A página apresenta as seguintes seções:
 
@@ -40,7 +40,7 @@ Nesta seção você terá acesso ao total de pedidos ou ordens de serviço de um
 * Últimos três meses
 * Últimos seis meses
 
-![pick-pack-insights-2-pt](//images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/8c4e56474ee580fa0b975912637ee596/image.png)
+![pick-pack-insights-2-pt](https://images.ctfassets.net/alneenqid6w5/3RQxDHaIIizzeWuzR0V6BB/8c4e56474ee580fa0b975912637ee596/image.png)
 
 ## Tempo das etapas
 
@@ -50,16 +50,16 @@ Nesta seção, você terá acesso às informações relativas a duração de cad
 * Tempo de embalagem
 * Tempo de envio
 
-![pick-pack-insights-3-pt](//images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/3123713047ffc0a8a3e74a3ac745468f/image.png)
+![pick-pack-insights-3-pt](https://images.ctfassets.net/alneenqid6w5/1m58WOMMnQ7WOdaj4i3SFf/3123713047ffc0a8a3e74a3ac745468f/image.png)
 
 ## Pedidos - Orders Perfomance
 
 Nesta seção você terá acesso às informações sobre o desempenho geral dos pedidos e o tempo médio de atendimento de cada pedido.
 
-![pick-pack-insights-4-pt](//images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/4260d9e311ad31e53f535d59e9b6f463/image.png)
+![pick-pack-insights-4-pt](https://images.ctfassets.net/alneenqid6w5/7wqqORtnKrckhBf8FN5ff7/4260d9e311ad31e53f535d59e9b6f463/image.png)
 
 ## Itens
 
 Nesta seção você terá acesso às informações sobre os itens dos pedidos gerenciados no VTEX Pick and Pack, o tempo médio de separação por item, quantidade de itens selecionados por separador e taxa de preenchimento dos pedidos.
 
-![pick-pack-insights-5-pt](//images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/40317d13fe72e856459cd97d7d66fb88/image.png)
+![pick-pack-insights-5-pt](https://images.ctfassets.net/alneenqid6w5/eKZL0i3FM5wsulVBPzLJv/40317d13fe72e856459cd97d7d66fb88/image.png)
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
index ac2f375fc..cecb0c325 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
@@ -21,7 +21,7 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 
 O aplicativo móvel do [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) auxilia o separador - profissional responsável por selecionar e empacotar itens na instalação - no manuseio de pedidos, abrangendo desde a separação dos itens até o envio. Assim, o fluxo de separação e entrega dos pedidos da loja torna-se mais organizado e fluido.
 
-![pickpack-mobile-pt](//images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/825577c3ee5232ac15408d243a20d04e/image.png)
+![pickpack-mobile-pt](https://images.ctfassets.net/alneenqid6w5/4VZJd6qfgBB45lcqptQ5L9/825577c3ee5232ac15408d243a20d04e/image.png)
 
 O manuseio do pedido é dividido em quatro etapas, seguindo o caminho normal de pedidos na loja:
 
@@ -56,7 +56,7 @@ Ordens de serviço se aplicam apenas às fases de separação e empacotamento de
 
 A aba __Sem alocação__ lista os pedidos que devem ser selecionados para [ordens de serviço](#ordem-de-servico).
 
-![pickpack-ordemservico-pt](//images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/ed6060bd509ee50e397b06e62a335547/image.png)
+![pickpack-ordemservico-pt](https://images.ctfassets.net/alneenqid6w5/2zTfjSklG6b57gEHryo2BI/ed6060bd509ee50e397b06e62a335547/image.png)
 
 Para criar uma ordem de serviço, siga os passos abaixo:
 
@@ -72,7 +72,7 @@ A etapa de separação consiste em selecionar fisicamente os itens correspondent
 
 A aba __Pendentes__ exibe a lista de ordens de serviço que ainda não tiveram sua separação finalizada.
 
-![pickpack-pendente-pt](//images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/617071b6d8e6f098f74aa466bd5321fc/image.png)
+![pickpack-pendente-pt](https://images.ctfassets.net/alneenqid6w5/43VayjqahaHNiFLoT2gjbm/617071b6d8e6f098f74aa466bd5321fc/image.png)
 
 Nesta aba, é possível selecionar pelo ID de uma ordem de serviço, caso queira visualizar apenas os itens separados daquele pedido.
 
@@ -87,7 +87,7 @@ Ao clicar em uma ordem de serviço, as seguintes informações são exibidas:
 - __Informações:__ informações gerais da ordem de serviço e do pedido.
 - __Resumo:__ produtos que já foram separados pelo separador.
 
-![pickpack-em-separacao-pt](//images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/5f0e48be4c066bf3aa3757f0ddc3db07/image.png)
+![pickpack-em-separacao-pt](https://images.ctfassets.net/alneenqid6w5/5zrrsEx43mNC0shZkDiBQ0/5f0e48be4c066bf3aa3757f0ddc3db07/image.png)
 
 Ao clicar no menu <i class="fas fa-ellipsis-v"></i>, serão exibidas as seguintes ações:
 
@@ -103,7 +103,7 @@ Para separar um produto, siga estes passos:
 1. Na tela de __Separação__, acesse a aba __Item(ns)__.
 2. Clique no produto que deseja separar ou deslize o produto para a direita. Caso o produto tenha mais de uma unidade, é necessário clicar a quantidade de unidades do produto. Para produtos que contém peso ou volume é preciso confirmar a medida e depois confirmar a seleção, como o exemplo abaixo.
 
-![pickpack-item-pt](//images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/f46444bb6af306fc698e2084473a421d/image.png)
+![pickpack-item-pt](https://images.ctfassets.net/alneenqid6w5/6DXcDvIWNba93QEDb1wjo3/f46444bb6af306fc698e2084473a421d/image.png)
 
 Para separar todos os produtos da ordem de serviço de uma única vez, siga estes passos:
 
@@ -126,7 +126,7 @@ Para recusar um produto da ordem de serviço, siga os passos abaixo:
 1. Acesse a aba __Item(ns)__.
 2. Clique e deslize para a esquerda o produto que deseja recusar.
 3. Selecione a razão da recusa da lista **Motivos de recusa**.
-  ![pickpack-item-recusa-pt](//images.ctfassets.net/alneenqid6w5/2rFwEeBHOf6PLRpgpcdDTL/08fac545bfe628e5211c0c818a22c3df/image.png)
+  ![pickpack-item-recusa-pt](https://images.ctfassets.net/alneenqid6w5/2rFwEeBHOf6PLRpgpcdDTL/08fac545bfe628e5211c0c818a22c3df/image.png)
 4. Selecione a quantidade de itens que deseja recusar ou clique em `Confirmar e descartar todas as unidades`.
 5. Clique em `Descartar unidades`.
 
@@ -154,7 +154,7 @@ Para substituir itens da ordem de serviço, siga os passos abaixo:
 2. Pressione o produto que deseja substituir.
 3. Clique na opção **Substituir item**.
 4. Busque ou selecione o item que substituirá o produto do pedido e clique na caixa de seleção <i class="fas fa-check-square"></i>.
-  ![pickpack-item-substituir-pt](//images.ctfassets.net/alneenqid6w5/3rdotgG0FkRbv3AprESrYA/6558b779984c5b763bfbc5e3a87c838d/image.png)
+  ![pickpack-item-substituir-pt](https://images.ctfassets.net/alneenqid6w5/3rdotgG0FkRbv3AprESrYA/6558b779984c5b763bfbc5e3a87c838d/image.png)
 5. Selecione o número de unidades que deverão ser substituídas.
 6. Selecione o motivo da substituição dentre as opções da lista.
 7. Preencha o campo **Descrição** com mais informações sobre a substituição.
@@ -168,14 +168,14 @@ Uma vez que todos os itens da ordem de serviço foram separados, recusados ou su
 
 Na etapa de empacotamento, o separador seleciona os itens de cada pedido nas respectivas embalagens de envio. O aplicativo móvel do Pick and Pack permite organizar todos os pacotes necessários para diversos pedidos de forma simples e fácil.
 
-![pickpack-empacotamento-pt](//images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/346447464d242ff16d085322378503fe/image.png)
+![pickpack-empacotamento-pt](https://images.ctfassets.net/alneenqid6w5/7vJJMaVu3OgpDTtpXAPOCU/346447464d242ff16d085322378503fe/image.png)
 
 É possível acessar a página de Empacotamento ao [concluir a separação](#concluir-separacao) de uma ordem de serviço ou seguindo estes passos:
 
 1. Na tela inicial do aplicativo, clique em **Para empacotar**. Será exibida uma lista com as [ordens de serviço](#ordens-de-servico) designadas ao separador que estão na etapa de empacotamento.
 2. Clique na ordem de serviço cujos produtos deseja separar. 
 
-![pickpack-item-pendente-pt](//images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/abcca3f55094eea7f71c73660bd1b5f0/image.png)
+![pickpack-item-pendente-pt](https://images.ctfassets.net/alneenqid6w5/6ZdONyhqHoSVFf0snDQ6SO/abcca3f55094eea7f71c73660bd1b5f0/image.png)
 
 Siga os passos abaixo para empacotar itens:
 
@@ -194,10 +194,10 @@ Caso opte por empacotar todos os itens do pedido, os produtos que ainda não for
 Os itens que já foram empacotados estão disponíveis na aba **Itens empacotados**. É possível alternar a visualização dos itens entre uma lista de itens ou de pedidos e pacotes, clicando em <i class="fas fa-toggle-on"></i>.
 
 __Lista de itens__
-![pickpack-item-empacotado-pt](//images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/5bb135ce0588205f44ff5511681ff816/image.png)
+![pickpack-item-empacotado-pt](https://images.ctfassets.net/alneenqid6w5/2fKkok0mKMpcwLtaaY48gd/5bb135ce0588205f44ff5511681ff816/image.png)
 
 __Pedidos e pacotes__
-![pickpack-item-empacotado-2-pt](//images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/fbaaedf590f158d3dbc9d24941d9f15a/image.png)
+![pickpack-item-empacotado-2-pt](https://images.ctfassets.net/alneenqid6w5/6BIoHcM0CwTg8boKYiiL4T/fbaaedf590f158d3dbc9d24941d9f15a/image.png)
 
 ### Envio
 
@@ -215,11 +215,11 @@ Para enviar pacotes no aplicativo Pick and Pack, siga os passos abaixo:
 4. Preencha as informações de envio:
     - **Data prevista para coleta**
     - **Data prevista para entrega**
-    ![pickpack-envio-pt](//images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/913d43663fb129edf3750b852bad2706/image.png)
+    ![pickpack-envio-pt](https://images.ctfassets.net/alneenqid6w5/241KZLvmluqVG6uR63dBze/913d43663fb129edf3750b852bad2706/image.png)
 5. Selecione uma transportadora disponível.
 6. Clique em `Selecionar e continuar`.
 7. Confirme as informações do envio. Se nenhuma correção for necessária, clique no botão `Criar serviço`. Caso contrário, clique em `Voltar` e volte ao passo 5. 
 
 Finalizado o cadastro, as informações do envio serão exibidas na tela seguinte no aplicativo. Os pedidos enviados estão disponíveis pelo menu <i class="fas fa-ellipsis-v"></i> __> Concluído__. 
 
-![pickpack-finalizacao-pt](//images.ctfassets.net/alneenqid6w5/40mZiPyjG5VEHmcDazxUrI/2007a8d429ddb218f53add49575c0e76/image.png)
+![pickpack-finalizacao-pt](https://images.ctfassets.net/alneenqid6w5/40mZiPyjG5VEHmcDazxUrI/2007a8d429ddb218f53add49575c0e76/image.png)
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-orders.md b/docs/tutorials/pt/vtex-pick-and-pack-orders.md
index 2da7d1d83..d65726123 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-orders.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-orders.md
@@ -28,7 +28,7 @@ Esta página permite que você realize as seguintes ações:
 * [Filtrar pedidos](#filtrar-pedido)
 * [Exportar pedidos](#exportar-pedidos)
 
-![pick-and-pack-pedidos-PT](//images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/83a5b409f6cbeff9c7efbdfe55b22fbe/image.png)
+![pick-and-pack-pedidos-PT](https://images.ctfassets.net/alneenqid6w5/7oIngXdaDwQP0CQSHlQaPO/83a5b409f6cbeff9c7efbdfe55b22fbe/image.png)
 
 A página apresenta as seguintes informações em uma tabela: 
 
@@ -56,7 +56,7 @@ Você pode otimizar a consulta de pedidos a partir das seguintes abas:
 
 Você também pode acessar informações mais detalhadas sobre cada pedido clicando no respectivo pedido na tabela.
 
-![pick-and-pack-pedidos-2-PT](//images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/20b4531d5c5f49f9f70ea4c839fcaacb/image.png)
+![pick-and-pack-pedidos-2-PT](https://images.ctfassets.net/alneenqid6w5/2X9tIEvxpMKtTTCMC7NF9N/20b4531d5c5f49f9f70ea4c839fcaacb/image.png)
 
 Ao selecionar o pedido desejado, você terá acesso às seguintes informações:
 
@@ -91,5 +91,5 @@ Você pode exportar os pedidos seguindo os passos abaixo:
 1. Clique em `Exportar`.
 2. Selecione os dados que deseja exportar: `Relatório de pacotes` ou `Orders Reports`.
     * No caso de `Relatório de pacotes`, você deve selecionar o período que deseja exportar, o tipo e o método de envio.
-  ![pick-and-pack-pedidos-3-PT](//images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/b0f36539e9039aa4e127fc49e47f8a6b/image.png)
+  ![pick-and-pack-pedidos-3-PT](https://images.ctfassets.net/alneenqid6w5/4e3Zjkh9zuwmcPNe0CKJQU/b0f36539e9039aa4e127fc49e47f8a6b/image.png)
 3. Clique em `Exportar`.
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-settings.md b/docs/tutorials/pt/vtex-pick-and-pack-settings.md
index be50022b7..efd539978 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-settings.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-settings.md
@@ -34,7 +34,7 @@ Essa funcionalidade está na fase Beta fechado, o que significa que somente clie
 
 Nesta aba, você encontrará as configurações relacionadas à etapa de separação de itens do pedido. Nela você consegue definir ações que o separador pode realizar durante o processo de separação, incluindo informar que um item do pedido não estava disponível e sugerir uma substituição.
 
-![pick-and-pack-separacao-pt](//images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/a57a373de5dc0b3875f2e4286ab039b4/image.png)
+![pick-and-pack-separacao-pt](https://images.ctfassets.net/alneenqid6w5/31IMWfSufilPJHlkU7bLyh/a57a373de5dc0b3875f2e4286ab039b4/image.png)
 
 ### Estratégia de separação
 
@@ -93,7 +93,7 @@ Clique em `Salvar` para registrar as alterações feitas na aba.
 
 Nesta aba, você pode configurar a ordem das categorias em que os pedidos serão separados. Dessa forma, o separador consegue organizar o fluxo de coleta dos produtos para a montagem dos pedidos com eficiência.
 
-![pick-pack-categorias-pt](//images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/700e3120ee48d2b4e557e12325f7fe6f/image.png)
+![pick-pack-categorias-pt](https://images.ctfassets.net/alneenqid6w5/3BSGR29QrAWbHBRjadYcBE/700e3120ee48d2b4e557e12325f7fe6f/image.png)
 
 * **Configuração rápida:** habilita as configurações em todas as instalações. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
 * **Instalação**: determina qual a instalação terá as configurações de categorias aplicadas.
@@ -106,7 +106,7 @@ Você pode importar um arquivo CSV ou exportar a lista que já está configurada
 
 Nesta aba, você encontrará as configurações relacionadas à etapa de empacotamento de itens do pedido. 
 
-![pick-pack-empacotamento-pt](//images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/dfef3cd4f98481adef1f31c9b5be8da7/image.png)
+![pick-pack-empacotamento-pt](https://images.ctfassets.net/alneenqid6w5/2SbFdooYvZpNL3KDq2gdgK/dfef3cd4f98481adef1f31c9b5be8da7/image.png)
 
 * **Permitir relatório de pacotes:** habilita a exibição de relatório de pacotes. O relatório será exibido  na tela de **Pedidos**. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
 * **Permitir empacotamento automático:** habilita o empacotamento automático. Você pode ativar <i class="fas fa-toggle-on"></i> ou desativar <i class="fas fa-toggle-off"></i> a opção.
@@ -174,7 +174,7 @@ Clique em `Salvar` para registrar as alterações feitas na aba.
 
 Nesta aba, você encontrará configurações relacionadas aos pedidos processados pelo VTEX Pick and Pack.
 
-![pick-pack-config-pedidos-pt](//images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/70c1a50002db6ec6f984b0382391483a/image.png)
+![pick-pack-config-pedidos-pt](https://images.ctfassets.net/alneenqid6w5/4WY1T4pWaSbvdzA6FqOeGY/70c1a50002db6ec6f984b0382391483a/image.png)
 
 * **Baixar pedidos do OMS:** permite exportar pedidos do OMS.
 * **Meios de pagamento:** meios de pagamento utilizados nos pedidos que serão exportados.
@@ -188,7 +188,7 @@ Clique em `Salvar` para registrar as alterações feitas na aba.
 
 Nesta aba, você encontrará as configurações de automação de processos do VTEX Pick and Pack.
 
-![pick-pack-automacao-pt](//images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/2d72b5f563970d8deb9041e2b5d301e8/image.png)
+![pick-pack-automacao-pt](https://images.ctfassets.net/alneenqid6w5/4ymzTYa77AIPdheE0KkgSy/2d72b5f563970d8deb9041e2b5d301e8/image.png)
 
 Para criar uma nova automação, siga os passos abaixo:
 
@@ -200,7 +200,7 @@ Para criar uma nova automação, siga os passos abaixo:
 
 Nesta aba, você fará o gerenciamento dos usuários, admins e separadores, da sua operação VTEX Pick and Pack. Usuários com permissão **Admin** terão acesso ao Admin VTEX e poderão realizar alterações na ferramenta. Usuários com permissão **Separador** terão acesso apenas ao aplicativo do VTEX PIck and Pack. 
 
-![pick-pack-usuarios-pt](//images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/b2d142e6e32bef9d35a6afa9feedaca9/image.png)
+![pick-pack-usuarios-pt](https://images.ctfassets.net/alneenqid6w5/1VzckMNHfoiub8sRtreP3p/b2d142e6e32bef9d35a6afa9feedaca9/image.png)
 
 Para criar um novo usuário, siga os seguintes passos:
 
@@ -210,7 +210,7 @@ Para criar um novo usuário, siga os seguintes passos:
      * Permissão **Admin**
         1. Selecione o usuário listado que deseja cadastrar como **Admin**.
         2. Clique em `Criar`.
-![pick-pack-usuarios-2-pt](//images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/a0b7366fe48d624a3470933629474032/image.png)
+![pick-pack-usuarios-2-pt](https://images.ctfassets.net/alneenqid6w5/1cdVquaWE1X8XIgD7M6tlS/a0b7366fe48d624a3470933629474032/image.png)
      * Permissão **Separador**
         1.  Preencha o formulário com as seguintes informações:
            * Nome de usuário
@@ -221,13 +221,13 @@ Para criar um novo usuário, siga os seguintes passos:
            * Permitir o envio de pacotes
            * Categorias
         2. Clique em `Criar`.
-        ![pick-pack-usuarios-3-pt](//images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/e06dcefd1c9f172c90debd7c2108c049/image.png)
+        ![pick-pack-usuarios-3-pt](https://images.ctfassets.net/alneenqid6w5/4PrkthovWlPTX7vzJ1IdAN/e06dcefd1c9f172c90debd7c2108c049/image.png)
 
 ## Catálogo
 
 Nesta aba, você terá acesso às informações dos itens dos pedidos que estão na etapa de entrega para o cliente.
 
-![pick-pack-catalogo-pt](//images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/b517d26ac0b52f72ac4e97e65b232979/image.png)
+![pick-pack-catalogo-pt](https://images.ctfassets.net/alneenqid6w5/7bEUt2nvw2xGUKO8WjmkSl/b517d26ac0b52f72ac4e97e65b232979/image.png)
 
 A página apresenta as seguintes informações em uma tabela: 
 
@@ -260,7 +260,7 @@ A indexação do catálogo irá apagar e recriar todo o conteúdo dele, o que si
 
 Nesta aba, você terá acesso ao cadastro e consulta das instalações da sua loja.
 
-![pick-pack-instalacoes-pt](//images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/14186600ad10fec8354aa80e7c1a077e/image.png)
+![pick-pack-instalacoes-pt](https://images.ctfassets.net/alneenqid6w5/4VKy2KHlm4Vdz8oa8lv8VB/14186600ad10fec8354aa80e7c1a077e/image.png)
 
 Para criar uma nova instalação, siga os seguintes passos:
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md b/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
index fe5074fcc..28f33e8f0 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
@@ -27,11 +27,11 @@ Esta página permite que você realize as seguintes ações:
 * [Buscar ordem de serviço](#buscar-ordem-de-servico)
 * [Filtrar ordens de serviço](#filtrar-ordem-de-servico)
 
-![pick-pack-ordem-servico-pt](//images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/0d7875431b5940b7d94bcc7d156c4d7c/image.png)
+![pick-pack-ordem-servico-pt](https://images.ctfassets.net/alneenqid6w5/6mHohZLRFdkoTlltboN2pm/0d7875431b5940b7d94bcc7d156c4d7c/image.png)
 
 As ordens de pedido são apresentadas em cartões contendo as seguintes informações: 
 
-![pick-pack-ordem-servico-2-pt](//images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/c8143a8bf5b02f69cf6906531e46b755/image.png)
+![pick-pack-ordem-servico-2-pt](https://images.ctfassets.net/alneenqid6w5/2LZZpv41eVop7ajXNrkfC4/c8143a8bf5b02f69cf6906531e46b755/image.png)
 
 * ID da ordem de serviço.
 * Quantidade de pedidos contidos na ordem de serviço.
@@ -49,7 +49,7 @@ Você pode criar uma nova ordem de serviço seguindo os passos descritos abaixo:
 3. Clique na aba **Manual** para criar manualmente a ordem de serviço.
 4. Clique em `+` para criar uma ordem de serviço. Você pode criar mais de uma ordem de serviço.
 5. Arraste os pedidos que deseja para a ordem de serviço.
-  ![pick-pack-ordem-servico-3-pt](//images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/9fff8b6632fe20c3b5e8b6b568b5adc1/image.png)
+  ![pick-pack-ordem-servico-3-pt](https://images.ctfassets.net/alneenqid6w5/1xxnRTbuVnfvto7Q8czn8i/9fff8b6632fe20c3b5e8b6b568b5adc1/image.png)
 6. Clique em `Criar` para finalizar.
 
 ## Consultar ordem de serviço
@@ -64,7 +64,7 @@ Você pode otimizar a consulta por ordens de serviço a partir das seguintes aba
 
 Você também pode acessar mais informações de cada ordem de serviço clicando no botão <i class="fas fa-chevron-down"></i> no bloco.
 
-![pick-pack-ordem-servico-4-pt](//images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/bb8e751deeb457a5f2d73a941ef05689/image.png)
+![pick-pack-ordem-servico-4-pt](https://images.ctfassets.net/alneenqid6w5/1sQ1kwEN7xnPeL7Kb9rPIq/bb8e751deeb457a5f2d73a941ef05689/image.png)
 
 ## Buscar ordem de serviço
 
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
index 6acd13a19..04c9f8643 100644
--- a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
@@ -25,7 +25,7 @@ Este artigo é sobre como ativar o **VTEX Shipping Network Correios**. Esta ativ
 
 O vídeo abaixo apresenta todas as etapas da ativação, e na seção seguinte você encontra o passo a passo:
 
-![vsncorreios_ativacao_PT](//images.ctfassets.net/alneenqid6w5/3jkyhn9NypaHZBeXAib7iz/410d76ca2ba8b25cbfce2c0adcb27813/vsncorreios_ativacao.gif)
+![vsncorreios_ativacao_PT](https://images.ctfassets.net/alneenqid6w5/3jkyhn9NypaHZBeXAib7iz/410d76ca2ba8b25cbfce2c0adcb27813/vsncorreios_ativacao.gif)
 
 <div class = "alert alert-info">
 Se você deseja integrar a sua operação com outras transportadoras além dos Correios, temos o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>, com sugestões de parceiros selecionados pela nossa equipe com foco no seu modelo de negócio.
@@ -36,7 +36,7 @@ Se você deseja integrar a sua operação com outras transportadoras além dos C
 Para realizar a ativação, siga o passo a passo abaixo:
 
 1. No Admin VTEX, acesse **Envio > Estratégia de envio**, ou digite **Estratégia de envio** na barra de busca no topo da página. Em seguida, clique no banner em `Veja a sua oferta`.
-  ![vsncorreios_banner_PT](//images.ctfassets.net/alneenqid6w5/SHhb94U7uQeYTggJBFYxJ/487402ecdbfa87d8777c8071ae49c297/vsncorreios_banner.png)
+  ![vsncorreios_banner_PT](https://images.ctfassets.net/alneenqid6w5/SHhb94U7uQeYTggJBFYxJ/487402ecdbfa87d8777c8071ae49c297/vsncorreios_banner.png)
   > Se o banner não aparecer na página, acesse a URL `https://{nome-da-loja}.myvtex.com/admin/shipping-strategy/beta/shipping-network-offer/form`, substituindo `{nome-da-loja}` pelo seu [account name](https://help.vtex.com/pt/tutorial/o-que-e-account-name--i0mIGLcg3QyEy8OCicEoC).
 2. Na etapa **Sua Operação**, realize os passos abaixo:
 
@@ -50,17 +50,17 @@ Caso você já possua um contrato com os Correios, antes de ativar o <b>VTEX Shi
 
   c. Clique em **Conhecer Oferta**.
 
-  ![vsncorreios_conhecer_oferta_PT](//images.ctfassets.net/alneenqid6w5/oIBsNdSOSJoNQtzT14RGc/1e836be59f73d8171a0e0551ede0be25/vsncorreios_conhecer_oferta.png)
+  ![vsncorreios_conhecer_oferta_PT](https://images.ctfassets.net/alneenqid6w5/oIBsNdSOSJoNQtzT14RGc/1e836be59f73d8171a0e0551ede0be25/vsncorreios_conhecer_oferta.png)
 
 3. Na etapa **Nossa Oferta**, consulte os benefícios da tabela que foi considerada a mais adequada à sua operação.
   > A imagem abaixo é um exemplo da _Tabela Ouro_:
 
-  ![vsncorreios_nossa_oferta_PT](//images.ctfassets.net/alneenqid6w5/3dW4e20L9fdXo5lVdp1MLy/34dee25d430596a57261894e759b1b27/vsncorreios_nossa_oferta.png)
+  ![vsncorreios_nossa_oferta_PT](https://images.ctfassets.net/alneenqid6w5/3dW4e20L9fdXo5lVdp1MLy/34dee25d430596a57261894e759b1b27/vsncorreios_nossa_oferta.png)
 
 4. Em seguida, clique em `Tenho interesse` e um modal será aberto contendo os termos e condições da ativação.
   > Você pode adquirir uma cópia do arquivo em formato PDF clicando em **Download dos termos**.
 
-  ![vsncorreios_termos_condicoes_PT](//images.ctfassets.net/alneenqid6w5/1X6rp478ZIsZlGZCOCPjEq/b518371d3989a37595ce48a9175b05b6/vsncorreios_termos_condicoes.png)
+  ![vsncorreios_termos_condicoes_PT](https://images.ctfassets.net/alneenqid6w5/1X6rp478ZIsZlGZCOCPjEq/b518371d3989a37595ce48a9175b05b6/vsncorreios_termos_condicoes.png)
 
 5. Clique em `Aceitar` para concordar com as condições apresentadas e ativar o VTEX Shipping Network Correios.
 6. Na etapa **Um Resumo**, confira as informações finais e garanta que a sua operação tenha uma [agência dos Correios parceira](https://www.correios.com.br/coronavirus/rede-de-atendimento).
@@ -69,7 +69,7 @@ Caso você já possua um contrato com os Correios, antes de ativar o <b>VTEX Shi
     * `Ativar políticas de envio`: as novas políticas de envio são criadas ativas e, em poucos instantes após a confirmação, serão válidas para envio de pedidos.
     > Você pode a qualquer momento ativar ou desativar as políticas de envio associadas aos Correios, e não existe cobrança quando o serviço não é utilizado. 
 
-    ![vsncorreios_contratou_tabela_PT](//images.ctfassets.net/alneenqid6w5/5qYbCqvYVzttbB3RnsAkCX/cdc81c301c9409f5e9a518f9212c9d15/vsncorreios_contratou_tabela.png)
+    ![vsncorreios_contratou_tabela_PT](https://images.ctfassets.net/alneenqid6w5/5qYbCqvYVzttbB3RnsAkCX/cdc81c301c9409f5e9a518f9212c9d15/vsncorreios_contratou_tabela.png)
 
 Feito isso, a ativação do **VTEX Shipping Network Correios** terá sido concluída.
 
diff --git a/docs/tutorials/pt/vtex-shipping-network-dashboard.md b/docs/tutorials/pt/vtex-shipping-network-dashboard.md
index 4beee0b5a..439a0fe9d 100644
--- a/docs/tutorials/pt/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/pt/vtex-shipping-network-dashboard.md
@@ -66,7 +66,7 @@ No cálculo da performance, são considerados todos os pacotes que fazem parte d
 
 A performance é o resultado em percentual do cálculo entre a relação dos pacotes entregues dentro do  prazo pelo total de pacotes entregues. Assim, o cálculo da performance só leva em consideração os pacotes que foram entregues. Veja:
 
-![equation PT performance](//images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/5f190d7ed6439920a22dfbb5d86fe127/CodeCogsEqn.gif)
+![equation PT performance](https://images.ctfassets.net/alneenqid6w5/24t2KA8ivoNmb4y3oaDDxf/5f190d7ed6439920a22dfbb5d86fe127/CodeCogsEqn.gif)
 
  A ferramenta de Performance do **VTEX Shipping Network** permite:
 
diff --git a/docs/tutorials/pt/vtex-status-page.md b/docs/tutorials/pt/vtex-status-page.md
index d5a58bd46..95ccd89be 100644
--- a/docs/tutorials/pt/vtex-status-page.md
+++ b/docs/tutorials/pt/vtex-status-page.md
@@ -19,7 +19,7 @@ Na página [Status VTEX](https://status.vtex.com/), você pode acompanhar a esta
 
 Os eventos são reportados pela nossa equipe sempre que nosso sistema automático de monitoramento identifica uma instabilidade nos módulos da plataforma. As manutenções programadas também são comunicadas em detalhes.
 
-![statuspage-1](//images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/8fc52cd3637d63edbd9963962460e6dc/statuspage-1.png)
+![statuspage-1](https://images.ctfassets.net/alneenqid6w5/qECQAjnWxwGH47wzXDv6c/8fc52cd3637d63edbd9963962460e6dc/statuspage-1.png)
 
 Abaixo, você encontra detalhes sobre os elementos da página de status da plataforma VTEX, desenvolvida com a ferramenta [incident.io](https://incident.io/):
 
@@ -41,7 +41,7 @@ A página de status apresenta o botão `Subscribe to updates `no canto superior
 
 Ao escolher a inscrição por email, você pode optar por receber notificações apenas para impactos em componentes específicos. Para isso, marque a opção **Subscribe to specific components** e, em seguida, marque os componentes a acompanhar.
 
-![statuspage-2](//images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/a5d988626d923d454ef74bb60d7104c4/statuspage-2.png)
+![statuspage-2](https://images.ctfassets.net/alneenqid6w5/765OraMzYp5UPazSPX8JoP/a5d988626d923d454ef74bb60d7104c4/statuspage-2.png)
 
 ## Status geral
 
@@ -49,23 +49,23 @@ Nesta seção, você pode visualizar o status geral da plataforma, que pode ser
 
 Quando problemas ou manutenção estão afetando algum sistema, o componente impactado é apresentado, assim como uma explicação da ocorrência. Veja exemplos a seguir.
 
-![statuspage-3](//images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/f464e8250a0b198b4b0d5fd6daafd514/statuspage-3.png)
+![statuspage-3](https://images.ctfassets.net/alneenqid6w5/16vditkk4vdDH5NGhGp7zJ/f464e8250a0b198b4b0d5fd6daafd514/statuspage-3.png)
 
-![statuspage-4](//images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/723008187b05b2c81eba0af564b7514d/statuspage-4.png)
+![statuspage-4](https://images.ctfassets.net/alneenqid6w5/6EpVdfEsrlzNk2qQNWDN2b/723008187b05b2c81eba0af564b7514d/statuspage-4.png)
 
-![statuspage-5](//images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/5d64281bddf023076fa17e84671a6cc9/statuspage-5.png)
+![statuspage-5](https://images.ctfassets.net/alneenqid6w5/46ql2YGxhdGrZwrbhj9oe4/5d64281bddf023076fa17e84671a6cc9/statuspage-5.png)
 
 ## Status dos sistemas
 
 Nesta seção, é possível verificar, em tempo real, o status de cada sistema da plataforma e de seus componentes.
 
-![statuspage-6](//images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/decc90536636cd0a50086535cb9f3450/statuspage-6.png)
+![statuspage-6](https://images.ctfassets.net/alneenqid6w5/23cxCKAgrYgrHwsGeTWEFM/decc90536636cd0a50086535cb9f3450/statuspage-6.png)
 
 Ao clicar na seta <i class="fas fa-chevron-down"></i> ao lado do número de componentes, você pode visualizar o status de componentes específicos de cada sistema.
 
 Se houver uma manutenção agendada para uma data futura, você verá também o botão `Upcoming maintenance scheduled`, ilustrado a seguir. Ao passar o mouse sobre ele, aparece o evento de manutenção agendada, no qual é possível clicar para visualizar o registro dessa ocorrência.
 
-![statuspage-7](//images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/9e861753a2f77e368d0f32f262d98f26/statuspage-7.png)
+![statuspage-7](https://images.ctfassets.net/alneenqid6w5/01rsFj3g2ZIyQfGvVj1U3F/9e861753a2f77e368d0f32f262d98f26/statuspage-7.png)
 
 Os estados possíveis para cada componente são:
 
@@ -123,7 +123,7 @@ Para navegar para meses anteriores, clique na seta `&lt;`.
 
 Para visualizar as ocorrências de um dia específico, passe o mouse sobre a data. Para acessar a página com o registro completo da ocorrência, clique no incidente ou na manutenção listada.
 
-![statuspage-8](//images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/36a4d394c1fb447958eec18ceaa849d3/statuspage-8.png)
+![statuspage-8](https://images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/36a4d394c1fb447958eec18ceaa849d3/statuspage-8.png)
 
 <div class="alert alert-warning">
   <p>Se a manutenção agendada durar um período maior que um dia, somente a data de início estará marcada no calendário. É necessário abrir o <a href="#registro-de-manutencao-agendada">registro da manutenção</a> para ver a data de início e a data de fim.</p>
@@ -135,7 +135,7 @@ A seguir, detalhamos as informações disponíveis no [registro de incidente](#r
 
 A página de detalhes do incidente contém as seguintes informações:
 
-![statuspage-9](//images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/af16c15476205d3a3529d4a434bfdd8d/statuspage-9.png)
+![statuspage-9](https://images.ctfassets.net/alneenqid6w5/2jNJB6z7HrvDzQMLi1W4KW/af16c15476205d3a3529d4a434bfdd8d/statuspage-9.png)
 
 * **Título:** título que descreve o incidente.
 * **Status:** cada incidente possui um ciclo definido, em que nossa equipe trabalha para identificar e solucionar os problemas. Conheça um pouco mais sobre cada etapa desse ciclo:
@@ -164,6 +164,6 @@ O registro de manutenção agendada apresenta as mesmas informações dos regist
 
 Veja a seguir exemplos do status e da linha do tempo de uma manutenção agendada.
 
-![statuspage-10](//images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/a2d673b455bd2ecc8f76745515609e5c/statuspage-10.png)
+![statuspage-10](https://images.ctfassets.net/alneenqid6w5/1pf3IU5k6R0pHhC7xLeKu0/a2d673b455bd2ecc8f76745515609e5c/statuspage-10.png)
 
-![statuspage-11](//images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/d54ae87af5467cc94d9978cf5bca6e93/statuspage-11.png)
+![statuspage-11](https://images.ctfassets.net/alneenqid6w5/4GtphAcpvUEwKmhl7FuPiU/d54ae87af5467cc94d9978cf5bca6e93/statuspage-11.png)
diff --git a/docs/tutorials/pt/vtex-suiteshare.md b/docs/tutorials/pt/vtex-suiteshare.md
index 729ab1278..1c8b67d89 100644
--- a/docs/tutorials/pt/vtex-suiteshare.md
+++ b/docs/tutorials/pt/vtex-suiteshare.md
@@ -19,28 +19,28 @@ Para instalar o script do **VTEX Assisted Sales (SuiteShare)** no seu site, bas
 
 Primeiro, acesse o painel administrativo da VTEX e, no menu à esquerda, siga para: **_CMS -> Layout -> CMS -> Custom Elements._**
 
-![VTEX 1](//images.ctfassets.net/alneenqid6w5/c6LgDxrCW3RPrrYoLcjlH/6e006379d1252dd7b128c914ae4660c8/Screenshot_2022-08-31_at_12-22-28_VTEX.png)
+![VTEX 1](https://images.ctfassets.net/alneenqid6w5/c6LgDxrCW3RPrrYoLcjlH/6e006379d1252dd7b128c914ae4660c8/Screenshot_2022-08-31_at_12-22-28_VTEX.png)
 
 Desça até encontrar a opção “Menu Footer - Primeiro”, ou somente “Menu Footer” caso não exista a divisão, clique em cima da linha para selecioná-la e depois clique em “Update”.
 
-![VTEX 2](//images.ctfassets.net/alneenqid6w5/f4sFPkaytHRI850pKkrQY/de55c692384c29a1b1a2bf1522b40b48/Screenshot_2022-08-31_at_12-22-35_VTEX.png)
+![VTEX 2](https://images.ctfassets.net/alneenqid6w5/f4sFPkaytHRI850pKkrQY/de55c692384c29a1b1a2bf1522b40b48/Screenshot_2022-08-31_at_12-22-35_VTEX.png)
 
 Na tela a seguir, clique no ícone de lápis como mostrado abaixo para editar o rodapé do site.
 
-![VTEX 3](//images.ctfassets.net/alneenqid6w5/4kLaAycDHWE8o8qVg4C3Xd/7a9dd8b0233fdab27a1f0b72e6193ad4/Screenshot_2022-08-31_at_12-22-41_VTEX.png)
+![VTEX 3](https://images.ctfassets.net/alneenqid6w5/4kLaAycDHWE8o8qVg4C3Xd/7a9dd8b0233fdab27a1f0b72e6193ad4/Screenshot_2022-08-31_at_12-22-41_VTEX.png)
 
 Role até o final do código que verá na tela, dê um Enter para pular uma linha e cole o código de instalação do **VTEX Assisted Sales (SuiteShare)**.
 
 O código de instalação do **VTEX Assisted Sales (SuiteShare)** está disponível em diversos locais, um deles é no menu _configurações> perfil>rastreamento_, ou caso você já tenha configurado o chat, em _atrair> chat> instruções de instalação_.
 
-![VTEX 4](//images.ctfassets.net/alneenqid6w5/1AgyPu8q1IZpCpdF4EkSRU/5f91387bdf97e016da3c1699a0a729ea/Screenshot_2022-08-31_at_12-22-47_VTEX.png)
+![VTEX 4](https://images.ctfassets.net/alneenqid6w5/1AgyPu8q1IZpCpdF4EkSRU/5f91387bdf97e016da3c1699a0a729ea/Screenshot_2022-08-31_at_12-22-47_VTEX.png)
 
 Após colar o código, clique em “Update content list”.
 
-![VTEX 5](//images.ctfassets.net/alneenqid6w5/6lifcFGPbg4Jvc1Tpx2Vii/2d86aadbb2bf066b8c1b16a9d1c6dc6e/Screenshot_2022-08-31_at_12-22-53_VTEX.png)
+![VTEX 5](https://images.ctfassets.net/alneenqid6w5/6lifcFGPbg4Jvc1Tpx2Vii/2d86aadbb2bf066b8c1b16a9d1c6dc6e/Screenshot_2022-08-31_at_12-22-53_VTEX.png)
 
 Depois, clique em “Save Content” para finalizar a instalação.
 
-![VTEX 6](//images.ctfassets.net/alneenqid6w5/7CN7v2TnOQwqflotqdK53o/673ccbe75774f9f54b4948ade030fc04/Screenshot_2022-08-31_at_12-23-01_VTEX.png)
+![VTEX 6](https://images.ctfassets.net/alneenqid6w5/7CN7v2TnOQwqflotqdK53o/673ccbe75774f9f54b4948ade030fc04/Screenshot_2022-08-31_at_12-23-01_VTEX.png)
 
 Pronto, o Chat/Widget ou CTA está instalado no seu site. Agora é aproveitar as funcionalidades!
diff --git a/docs/tutorials/pt/vtex-tracking-agencies.md b/docs/tutorials/pt/vtex-tracking-agencies.md
index 1406f0f66..4fe8f425b 100644
--- a/docs/tutorials/pt/vtex-tracking-agencies.md
+++ b/docs/tutorials/pt/vtex-tracking-agencies.md
@@ -76,13 +76,13 @@ Para cada status de entrega, é enviado um e-mail e um SMS para o consumidor com
 *O corpo do email deve ser preenchido em HTML, CSS e Javascript. Já a mensagem SMS pode ser preenchida em texto normal, substituindo os valores variáveis pelas `{{tags}}`, que explicaremos a seguir.*   
  7. Clique em **Salvar**.  
 
-![PT Tracking Agencia Configurar email](//images.ctfassets.net/alneenqid6w5/3piB2Vv9Lwkk7dIg0pvZnx/577774614e73f3d37f420ed92a681f89/PT_Tracking_Agencia_Configurar_email.png)
+![PT Tracking Agencia Configurar email](https://images.ctfassets.net/alneenqid6w5/3piB2Vv9Lwkk7dIg0pvZnx/577774614e73f3d37f420ed92a681f89/PT_Tracking_Agencia_Configurar_email.png)
 
 #### Status 
 
 A imagem abaixo representa o fluxo de disparo de emails e SMS para destinatários presentes em uma rota. 
 
-![PT Tracking Agencia status disparo](//images.ctfassets.net/alneenqid6w5/7qxjQpPt56Xs6HgsMP9vs9/c4ea6b54e215dcfc881b6c989c88ebc8/PT_Tracking_Agencia_status_disparo.png)
+![PT Tracking Agencia status disparo](https://images.ctfassets.net/alneenqid6w5/7qxjQpPt56Xs6HgsMP9vs9/c4ea6b54e215dcfc881b6c989c88ebc8/PT_Tracking_Agencia_status_disparo.png)
 
 - **Rota itinerante:** rota itinerante é aquela que demora mais de um dia para ser concluída. A comunicação é enviada quando o portador inicia a primeira entrega da rota. No email ou SMS a mensagem avisa que o serviço está em rota, e determina que a entrega será feita até o dia cadastrado como a data de fim da rota. 
 - **Rota Iniciada:** enviado quando o portador inicia a primeira entrega da rota. Todos os pedidos dentro daquela rota recebem uma previsão estimada, que será atualizada quando a comunicação de Entrega Iniciada for enviado.    
diff --git a/docs/tutorials/pt/warehouse.md b/docs/tutorials/pt/warehouse.md
index b1577003c..9c687982a 100644
--- a/docs/tutorials/pt/warehouse.md
+++ b/docs/tutorials/pt/warehouse.md
@@ -19,7 +19,7 @@ Para a plataforma VTEX o estoque é a identificação do espaço físico de arma
 
 É importante atentar-se à etapa logística do estoque e como as configurações na plataforma VTEX influenciam na entrega de pedidos. A partir do estoque os pedidos saem para as docas, e nas docas são retirados pelas transportadoras. 
 
-![EstrategiaEnvio](//images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/02cad4cbd4829e774e2b51474e4675cf/Frame_2__1_.svg)
+![EstrategiaEnvio](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/02cad4cbd4829e774e2b51474e4675cf/Frame_2__1_.svg)
 
 <div class="alert alert-info">
 A transportadora que realizará a entrega de um certo pedido é definida pela <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">política de envio</a>. Para que uma transportadora seja escolhida para a realização da entrega do pedido, é preciso que a política de envio dessa transportadora satisfaça as condições necessárias para a entrega do pedido. A política de envio é vinculada ao estoque pela Doca.
diff --git a/docs/tutorials/pt/web-application-firewall-waf.md b/docs/tutorials/pt/web-application-firewall-waf.md
index 9476ba33e..3aac9e02c 100644
--- a/docs/tutorials/pt/web-application-firewall-waf.md
+++ b/docs/tutorials/pt/web-application-firewall-waf.md
@@ -23,7 +23,7 @@ O Web Application Firewall (WAF) é uma camada de segurança projetada para prot
 
 O WAF é direcionado especificamente para comunicações que ocorrem pelos protocolos HTTP (Hypertext Transfer Protocol) e HTTPS (HTTP Secure), examinando os dados de entrada e saída para detectar e bloquear possíveis ameaças.
 
-![waf-pt](//images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/9eb9944bfed9b23421e053f2c6102825/waf-pt.png)
+![waf-pt](https://images.ctfassets.net/alneenqid6w5/6yRQRFGEYBnfbynGxcNJrU/9eb9944bfed9b23421e053f2c6102825/waf-pt.png)
 
 A operação do WAF começa com a definição de [regras de segurança](#regras-de-seguranca), que são definidas pelo time de Segurança da VTEX a partir da análise de padrões de circulação de informações. A partir dessas regras, o WAF monitora continuamente o tráfego da web. Quando detecta uma atividade potencialmente prejudicial, ele pode bloquear o tráfego, evitando assim a exploração de vulnerabilidades no aplicativo web.
 
diff --git a/docs/tutorials/pt/web-page-performance.md b/docs/tutorials/pt/web-page-performance.md
index 995b68e26..584f968d2 100644
--- a/docs/tutorials/pt/web-page-performance.md
+++ b/docs/tutorials/pt/web-page-performance.md
@@ -25,7 +25,7 @@ A tela “Performance das páginas web” disponibiliza a ferramenta [PageSpeed
 
 Embora o dashboard “Performance das páginas web” ofereça as mesmas funcionalidades da ferramenta PageSpeed Insights do Google, somente no Admin VTEX os comerciantes conseguem adicionar várias URLs e monitorá-las continuamente. 
 
-![Web page performance Dash PT](//images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
+![Web page performance Dash PT](https://images.ctfassets.net/alneenqid6w5/4EHCyrE0JQxGgxhk1YVdMY/69b6c76024c031cda5ec2a557620d067/Screen_Shot_2022-06-29_at_15.37.19.png)
 
 ## Por que você deve ficar de olho no desempenho de uma página web?
 
@@ -109,7 +109,7 @@ Observação: não é possível excluir as 10 páginas mais acessadas do seu eco
 
 ## Principais métricas da web
 
-![Core web vitals PT](//images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/a7221d5dc9e5197b55069697fbd3f758/Screen_Shot_2022-06-29_at_15.48.06.png)
+![Core web vitals PT](https://images.ctfassets.net/alneenqid6w5/2dqXPGBXhoqAOlu98GvSjg/a7221d5dc9e5197b55069697fbd3f758/Screen_Shot_2022-06-29_at_15.48.06.png)
 
 Para cada URL, o dashboard Performance das páginas web exibe as [Principais métricas da web do Google](https://web.dev/vitals/#core-web-vitals) referentes à página em questão. 
 
diff --git a/docs/tutorials/pt/welcome-message-control.md b/docs/tutorials/pt/welcome-message-control.md
index 8b4a967e4..bf8534b84 100644
--- a/docs/tutorials/pt/welcome-message-control.md
+++ b/docs/tutorials/pt/welcome-message-control.md
@@ -19,7 +19,7 @@ O controle `<vtex.cmc:welcomeMessage/>` renderiza uma mensagem de boas vindas, q
 
 Veja um exemplo na imagem abaixo.
 
-![welcome1](//images.contentful.com/alneenqid6w5/2z4iyUDAm0muKc4OCOUOa2/9e6f37d39596161bfe1721effdceb692/welcome1.png)
+![welcome1](https://images.contentful.com/alneenqid6w5/2z4iyUDAm0muKc4OCOUOa2/9e6f37d39596161bfe1721effdceb692/welcome1.png)
 
 ## Código HTML renderizado
 
diff --git a/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md b/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
index 58b4736e4..7d97a3754 100644
--- a/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
+++ b/docs/tutorials/pt/what-are-orders-with-marketplace-source-and-orders-with-fulfillment-source.md
@@ -19,7 +19,7 @@ Ao acessar a seção __Todos os pedidos__, em __Gerenciamento de pedidos__, é p
 
 A coluna __Origem__ indica de onde partiu o pedido, diferenciando o mesmo em duas possíveis origens: __Marketplace__ e __Fulfillment__.
 
-![orders-list-origin-pt](//images.ctfassets.net/alneenqid6w5/38XgFUqPIlB8T8FDRLsSXc/8db60848bd28cee74c5177d425130d1c/oders-list-origin-pt.png)
+![orders-list-origin-pt](https://images.ctfassets.net/alneenqid6w5/38XgFUqPIlB8T8FDRLsSXc/8db60848bd28cee74c5177d425130d1c/oders-list-origin-pt.png)
 
 ## Marketplace
 
diff --git a/docs/tutorials/pt/what-are-shelves.md b/docs/tutorials/pt/what-are-shelves.md
index bd0977de7..c377b9d24 100644
--- a/docs/tutorials/pt/what-are-shelves.md
+++ b/docs/tutorials/pt/what-are-shelves.md
@@ -23,7 +23,7 @@ Prateleiras são elementos configuráveis que exibem um agrupamento de produtos
 
 As prateleiras são estruturadas a partir de código HTML, organizados em [templates](/pt/tutorial/o-que-sao-templates)(arquivos que estruturam código) específicos, chamados de __Shelves Templates__. Eles estão localizados na pasta de **CMS**, no módulo [Layout](/pt/faq/o-que-e-o-cms). É nessa pasta que você vai poder criar novos templates e editar os que já existem.
 
-![Shelves Templates](//images.contentful.com/alneenqid6w5/4pIuR3BWKQisWuos4gcCWS/ade52c1df88c9e371169df99776b0779/Shelves_Template-min.png)
+![Shelves Templates](https://images.contentful.com/alneenqid6w5/4pIuR3BWKQisWuos4gcCWS/ade52c1df88c9e371169df99776b0779/Shelves_Template-min.png)
 
 Por ser um elemento que pode ser utilizado em mais de uma página, esse tipo especial de template (Shelf Template) fica armazenado em pastas diferentes dos outros tipos (HTML Templates e Sub Templates). Assim, é possível manter a organização dos arquivos e, consequentemente, do código do seu web site.
 
diff --git a/docs/tutorials/pt/what-are-templates.md b/docs/tutorials/pt/what-are-templates.md
index 1917ea50f..d56bee40c 100644
--- a/docs/tutorials/pt/what-are-templates.md
+++ b/docs/tutorials/pt/what-are-templates.md
@@ -32,7 +32,7 @@ Além desses dois tipos básicos, há ainda uma subdivisão dos __templates de p
 
 E falando em organização, você encontra todos os templates no módulo **Storefront > Layout > CMS**, reunidos em pastas de acordo com seu tipo (HTML ou Shelves). Os __Sub Templates__ estão na pasta de mesmo nome, que fica dentro do diretório __HTML Templates__. Nesses locais, você vai poder criar novos templates e editar os que já existem.
 
-![cms](//images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
+![cms](https://images.ctfassets.net/alneenqid6w5/JJxxdcGFq04SKmaqas6Oy/5c7a29f8676d68cc0d4dc7bfcf639ded/cms.png)
 
 ### Artigos relacionados
 - [O que é o CMS?](/pt/tutorial/o-que-e-o-cms)
diff --git a/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md b/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
index 557aac590..302387155 100644
--- a/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
+++ b/docs/tutorials/pt/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion.md
@@ -24,4 +24,4 @@ Ao configurar uma promoção **Compre e Ganhe**, é possível **Ativar multiplic
 Para ambos cenários, é necessário preencher a quantidade máxima de selecionável. Com o multiplicador de brindes **ativado**, determine a **quantidade máxima** de brindes para a condição. Para o multiplicador de brindes **desativado**, a quantidade é **sempre 1**. 
 
 
-![ativar-multiplicador-brinde pt ](//images.ctfassets.net/alneenqid6w5/X9IFg93pUiQQSeMocSqwS/b60bfe34e64450bcd25d97294dd2d66c/gift_multi_pt.png)
+![ativar-multiplicador-brinde pt ](https://images.ctfassets.net/alneenqid6w5/X9IFg93pUiQQSeMocSqwS/b60bfe34e64450bcd25d97294dd2d66c/gift_multi_pt.png)
diff --git a/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md b/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
index 75ca3ff3b..626df3202 100644
--- a/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
+++ b/docs/tutorials/pt/what-does-vtex-consider-as-revenue-in-the-billing-calculation.md
@@ -31,7 +31,7 @@ Para descobrir como acessar os pedidos que foram considerados na apuração da r
 
 Buscando facilitar sua visualização, todos os pedidos financeiramente aprovados terão essa marcação, que poderá ser vista no módulo gerenciamento de pedidos. 
 
-![image (3)](//images.ctfassets.net/alneenqid6w5/2hl6jNViPdxOaOqF9ZCrt7/ac5af18b2a91c8d3da149eff421991ea/image__3_.png)
+![image (3)](https://images.ctfassets.net/alneenqid6w5/2hl6jNViPdxOaOqF9ZCrt7/ac5af18b2a91c8d3da149eff421991ea/image__3_.png)
 
 Para acessar o módulo, siga os procedimentos abaixo:
 
diff --git a/docs/tutorials/pt/what-is-a-franchise-account.md b/docs/tutorials/pt/what-is-a-franchise-account.md
index 6382ac0fd..72dbd3e1a 100644
--- a/docs/tutorials/pt/what-is-a-franchise-account.md
+++ b/docs/tutorials/pt/what-is-a-franchise-account.md
@@ -19,7 +19,7 @@ Na plataforma VTEX, você tem a opção de cadastrar lojas físicas, franqueados
 
 A conta franquia é associada a uma conta principal. No caso de uma marca que possui múltiplas lojas físicas, franqueados ou representantes, cada um deles pode ter uma conta franquia vinculada à conta principal da marca. Isso permite que eles entreguem produtos vendidos pelo ecommerce da marca.
 
-![diagrama contas v2](//images.contentful.com/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/6a4d22cb3f55e2e97a1766bad65a7101/diagrama_contas_v2.png)
+![diagrama contas v2](https://images.contentful.com/alneenqid6w5/6KC4yvWh08WZ3DMcGRJS4I/6a4d22cb3f55e2e97a1766bad65a7101/diagrama_contas_v2.png)
 
 Neste artigo, você verá:
 
@@ -38,7 +38,7 @@ Além disso, utilizando a conta franquia, você pode gerenciar preços, meios de
 
 Uma conta franquia não possui um site próprio: os consumidores navegam diretamente no site da conta principal, que atua como marketplace nessa situação. Os dados dos clientes são armazenados no Master Data da conta principal.
 
-![diagrama admin contas](//images.contentful.com/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/87f8422ad8559f0681a5ab9eec71be51/diagrama_admin_contas.png)
+![diagrama admin contas](https://images.contentful.com/alneenqid6w5/226ePm8TzkWPFnTvJj2Sej/87f8422ad8559f0681a5ab9eec71be51/diagrama_admin_contas.png)
 
 ## Relação entre conta franquia e Seller White Label
 
diff --git a/docs/tutorials/pt/what-is-binding.md b/docs/tutorials/pt/what-is-binding.md
index 0070b73a1..f9e3473af 100644
--- a/docs/tutorials/pt/what-is-binding.md
+++ b/docs/tutorials/pt/what-is-binding.md
@@ -19,7 +19,7 @@ O Website binding é o que faz a ponte entre o CMS (Portal) e as informações d
 
 Ou seja, é ele que define que um __account name__ (configurado no License Manager) está atrelado à estrutura de pastas e arquivos de determinado __Website__ (construída no CMS). 
 
-![Binding](//images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
+![Binding](https://images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
 
 Esta é a configuração realizada quando uma conta deseja ter mais de uma loja. Para cada uma dessas lojas (que chamamos de [multilojas](/pt/tutorial/como-criar-multiloja-multidominio)), é feito um binding.
 
diff --git a/docs/tutorials/pt/what-is-cms-layout.md b/docs/tutorials/pt/what-is-cms-layout.md
index a36ccd795..47157d5e1 100644
--- a/docs/tutorials/pt/what-is-cms-layout.md
+++ b/docs/tutorials/pt/what-is-cms-layout.md
@@ -37,7 +37,7 @@ Antes de começar a organizar o conteúdo do seu Web Site, ele precisa estar vin
 
 Esse é um processo fundamental para o perfeito funcionamento da sua loja, mas também é muito simples. Basta seguir os passos [deste artigo](/pt/tutorial/vincular-um-account-name-a-um-website-binding).
 
-![Binding](//images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
+![Binding](https://images.contentful.com/alneenqid6w5/2selXSrkaoWaqUug24Mewm/bfea4f2413f1433c6cc2b80d8c7c9a93/Binding-min.png)
 
 ## Layouts e templates
 
diff --git a/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md b/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md
index 73879bb65..5a668e11d 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-inventory-and-warehouse-dock.md
@@ -25,7 +25,7 @@ __As três etapas da logística são representadas pela seguinte estrutura:__
 
 __E podem ser ilustradas pelo fluxo abaixo:__
 
-![PT Conceitos Logistics](//images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/bfa6fd2b0feed227b8f7338ee5a9db24/PT_Conceitos_Logistics.png)
+![PT Conceitos Logistics](https://images.ctfassets.net/alneenqid6w5/3xi4LHhJAElMNsp88xJ3A4/bfa6fd2b0feed227b8f7338ee5a9db24/PT_Conceitos_Logistics.png)
 
 ## Estoque 
 É o espaço físico utilizado para a armazenagem das mercadorias de um e-commerce, funcionando como o repositório de disponibilidade dos itens da sua loja.
diff --git a/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
index 45a336cf5..d71663818 100644
--- a/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
@@ -35,7 +35,7 @@ Os tipos são:
 
 Para criar uma tag personalizada de controle customizado, basta clicar em __Add__ e cadastrar um nome e uma tag, e então selecionar o tipo.
 
-![cms-custom-elements PT](//images.ctfassets.net/alneenqid6w5/oYjlNFuR8WKUkCag2yiQM/8da98e4f84d6e31639552d8d28931089/custom_elements_pt.png)
+![cms-custom-elements PT](https://images.ctfassets.net/alneenqid6w5/oYjlNFuR8WKUkCag2yiQM/8da98e4f84d6e31639552d8d28931089/custom_elements_pt.png)
 
 <div class="alert alert-warning">
   <p><b>Atenção:</b> não crie um controle do tipo HTML com um elemento <code>title</code>. Isso pode interferir no funcionamento correto da sua loja.</p>
diff --git a/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md b/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md
index dbfe9be7b..14376f432 100644
--- a/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md
+++ b/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md
@@ -33,7 +33,7 @@ Para se abrir uma disputa, o lojista deve enviar um email com o assunto Defesa D
 
 Os documentos devem ser enviados compilados em um único arquivo PDF, com no máximo 10 páginas e 7MB, com largura máxima de 21,59 cm e altura máxima de 27,59 cm. O nome do arquivo deve ser obrigatoriamente o ID da **Autorização da Transação (authld)**, como está no Admin da VTEX. A foto abaixo ilustra onde esse campo pode ser encontrado.
 
-![Transação disputa VTEX Payment PT](//images.contentful.com/alneenqid6w5/6Ll2HqxD17m89Vq3mZcazq/36fbb81cff88c9e83ae399902ebada74/image1.png)
+![Transação disputa VTEX Payment PT](https://images.contentful.com/alneenqid6w5/6Ll2HqxD17m89Vq3mZcazq/36fbb81cff88c9e83ae399902ebada74/image1.png)
 
 Caso haja algum problema no formato dos arquivos ou nos dados enviados, o lojista receberá um email automático, indicando que o email está fora dos padrões, possibilitando que o ele reenvie a documentação de maneira correta. Se os documentos estiverem corretos, serão enviados imediatamente para a adquirente. Caso a documentação já esteja correta, o envio é automático e não há retorno para o lojista de que o envio para a adquirente foi realizado.
 
diff --git a/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md b/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md
index 1e8975abd..b817ff0b8 100644
--- a/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md
+++ b/docs/tutorials/pt/what-to-do-when-my-report-does-not-reach-my-inbox.md
@@ -24,7 +24,7 @@ Ainda assim, existe uma maneira de extrair manualmente esse relatório acessando
 A seguir, entenda o passo a passo:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
-2. Clique em __Exportações__. ![exportacoes-md](//images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/043eef8efcf827b16d0546110bcec786/exportacoes.png)
+2. Clique em __Exportações__. ![exportacoes-md](https://images.ctfassets.net/alneenqid6w5/70bXGj3PhkEfcixEF0ik6I/043eef8efcf827b16d0546110bcec786/exportacoes.png)
 3. Certifique-se que aba aberta é a de __Aplicações__.
 4. Em __Status das exportações__, identifique a linha do relatório que deseja baixar.
 5. Se o __Status__ for __Finalizado - Baixar__, clique em **Baixar** para fazer download do arquivo.
diff --git a/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md b/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md
index 7fb3783ec..b868303e0 100644
--- a/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md
+++ b/docs/tutorials/pt/whatsapp-ai-campaigns-management-and-details.md
@@ -80,7 +80,7 @@ Para pausar o envio de mensagens de uma campanha:
 
 Você pode encontrar informações relativas às suas campanhas em andamento no Admin VTEX.
 
-![Visão geral-PT](//images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/5b970054cd95f9bd75086f1df4fca02d/Vis_o_geral-PT.png)
+![Visão geral-PT](https://images.ctfassets.net/alneenqid6w5/3QiT4K7FuFoTyhmlWYWKFl/5b970054cd95f9bd75086f1df4fca02d/Vis_o_geral-PT.png)
 
 Abaixo estão os detalhes das métricas disponíveis:
 
diff --git a/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md b/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md
index a4b10db7d..edf90f17a 100644
--- a/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md
+++ b/docs/tutorials/pt/where-do-i-see-clients-that-use-recurrence.md
@@ -22,6 +22,6 @@ Mas lembre-se: uma recorrência só aparece na listagem depois que seu pagamento
 1. Acesse o módulo __Gerenciamento de Pedidos__.
 2. Clique na aba __Assinaturas__.
 
-![subscriptions PT](//images.ctfassets.net/alneenqid6w5/yF4h1Bs3Ys2gU4kYGCkyK/feb155bc4414f904db25aea5dc0f12e8/subscriptions_PT.png)
+![subscriptions PT](https://images.ctfassets.net/alneenqid6w5/yF4h1Bs3Ys2gU4kYGCkyK/feb155bc4414f904db25aea5dc0f12e8/subscriptions_PT.png)
 
 
diff --git a/docs/tutorials/pt/where-do-i-see-the-payment-capture-date.md b/docs/tutorials/pt/where-do-i-see-the-payment-capture-date.md
index 9cb0de66d..d58748201 100644
--- a/docs/tutorials/pt/where-do-i-see-the-payment-capture-date.md
+++ b/docs/tutorials/pt/where-do-i-see-the-payment-capture-date.md
@@ -23,4 +23,4 @@ Basta seguir os passos abaixo:
 2. Busque a transação desejada e clique nela.
 3. Nos __Eventos da Transação__, busque o evento de captura:
 
-![captura](//images.contentful.com/alneenqid6w5/Xb2INQA3Qqa2K06IK6YWs/e70dcb1fbec79e0fb180e27b204dc0e4/captura.png)
+![captura](https://images.contentful.com/alneenqid6w5/Xb2INQA3Qqa2K06IK6YWs/e70dcb1fbec79e0fb180e27b204dc0e4/captura.png)
diff --git a/docs/tutorials/pt/white-label-sellers-selection.md b/docs/tutorials/pt/white-label-sellers-selection.md
index b1bc504c8..b37a28a6a 100644
--- a/docs/tutorials/pt/white-label-sellers-selection.md
+++ b/docs/tutorials/pt/white-label-sellers-selection.md
@@ -112,13 +112,13 @@ Se existir um empate entre sellers nos critérios de melhor custo ou prazo, o cr
 
 Um cliente adicionou ao carrinho cinco SKUs. Dentre os sellers que entregam na sua região, os sellers A, B, C e D, cada um possui no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) apenas parte dos itens, conforme a imagem a seguir:
 
-![print_selecao_seller_white_label_1](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
+![print_selecao_seller_white_label_1](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/4fdb2ed25e8d3d52eef96e5c0e2fd908/print_selecao_seller_white_label_1.png)
 
 A plataforma VTEX seleciona o seller que tem disponível no estoque a quantidade máxima de SKUs do carrinho. Neste caso, trata-se do Seller B, o único que entrega três SKUs. 
 
 Depois que o Seller B é selecionado, existem ainda dois SKUs não entregues. Se um único seller enviasse ambos, esse seria o fator decisivo da seleção, pois o objetivo é reunir o menor número de sellers para atender o carrinho. No entanto, são necessários os sellers A e C para entregar os SKUs 1 e 4, conforme imagem a seguir:
 
-![print_selecao_seller_white_label_2](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
+![print_selecao_seller_white_label_2](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/3f7b71abf734ae7c55d8b40d3a76f3c0/print_selecao_seller_white_label_2.png)
 
 Na primeira imagem, o Seller C era capaz de entregar os SKUs 3 e 4, e o Seller D entregava o SKU 5. No entanto, o Seller B foi selecionado para entregar esses itens, de forma que os SKUs são desconsiderados nas outras etapas de seleção. Isso foi representado com a remoção da seta do Seller C para o SKU 3 e do Seller D para o SKU 5.
 
@@ -128,7 +128,7 @@ O resultado da seleção para entrega é uma combinação dos sellers A, B e C.
 
 Um cliente adicionou cinco SKUs ao carrinho e existem quatro sellers que entregam na sua região, os sellers A, B, C e D. Nenhum deles tem no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) todos os itens, conforme imagem a seguir:
 
-![print_selecao_seller_white_label_3](//images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
+![print_selecao_seller_white_label_3](https://images.ctfassets.net/alneenqid6w5/23CWM1CDejDvKqF31O2DH9/26cd86b37e5e47ada6f15cc08acfbfbc/print_selecao_seller_white_label_3.png)
 
 A plataforma VTEX seleciona o seller que tem disponível no estoque o maior número de SKUs do carrinho. Tanto o Seller B quanto o D são capazes de entregar três itens, e como ambos entregam o SKU 3, existe uma concorrência.
 
@@ -141,11 +141,11 @@ Digamos que o Seller B tenha a entrega mais barata e que o Seller D tenha a mais
 
 - **Entrega mais rápida:** quando o Seller D é selecionado, restam como não entregues os SKUs 3 e 4. O Seller C consegue entregar ambos, sendo o escolhido, e o resultado da seleção é a combinação dos seller D e C.
 
-![print_selecao_seller_white_label_4](//images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
+![print_selecao_seller_white_label_4](https://images.ctfassets.net/alneenqid6w5/5OVQXuRwsEWGUxy3hocfOF/4751f13e35a8187655c04b11c67f6079/print_selecao_seller_white_label_4.png)
 
 - **Entrega mais barata:** quando o Seller B é selecionado, restam como não entregues os SKUs 1 e 4. Como somente o Seller A entrega o SKU 1, e somente o Seller C entrega o SKU 4, o resultado da seleção é uma combinação dos sellers A, B e C. 
 
-![print_selecao_seller_white_label_5](//images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
+![print_selecao_seller_white_label_5](https://images.ctfassets.net/alneenqid6w5/2zLEDj7yHw54HufNUeC8OT/d69cee9bb79c876adb571e98ccd0060c/print_selecao_seller_white_label_5.png)
 
 Nas imagens para entrega mais barata e mais rápida, foram retiradas as setas repetidas de sellers que entregavam SKUs já cobertos pelos sellers B e D. O motivo é que, nas sucessivas etapas de seleção, SKUs cobertos são desconsiderados.
 
diff --git a/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index eb129098d..a4ac69a5e 100644
--- a/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -37,7 +37,7 @@ Siga os passos abaixo para validar as informações:
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data**.
 2. Na caixa __Profile System__, clique em __Clientes__.
-3. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](//images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
+3. Selecione a opção __E-mail__ e busque pelo e-mail do cliente.![e-mail - Master Data](https://images.ctfassets.net/alneenqid6w5/cjpYKSZ1i8USYqs8Yga4E/df2c4793391483458ffcf8209a222f69/e-mail_-_Master_Data.png)
 4. Clique no registro do cliente para acessar os detalhes do perfil.
 
 Na seção __Contato__, você verá que a opção `É Empresa?` está preenchida com o valor `Não`. Ao mesmo tempo, na seção __Dados da empresa__, você verá que o campo `Tipo documento` está preenchido com o valor `cnpj`. 
diff --git a/docs/tutorials/pt/widget.md b/docs/tutorials/pt/widget.md
index cde6bcc91..501c4e93a 100644
--- a/docs/tutorials/pt/widget.md
+++ b/docs/tutorials/pt/widget.md
@@ -27,21 +27,21 @@ Para começar a configuração, você deve ter criado anteriormente os links da
 
 Para configurar o Widget, acesse o menu **Atrair > Widget**:
 
-![Widget 1](//images.ctfassets.net/alneenqid6w5/plu5lwBYTbLY02fyz1orV/42c0462dfe1cf8bbb2990a684992cbb9/Screenshot_2022-08-26_at_16-48-30_Widget.png)
+![Widget 1](https://images.ctfassets.net/alneenqid6w5/plu5lwBYTbLY02fyz1orV/42c0462dfe1cf8bbb2990a684992cbb9/Screenshot_2022-08-26_at_16-48-30_Widget.png)
 
 Clique em **Novo**.
 
-![Widget 2](//images.ctfassets.net/alneenqid6w5/5gdzo6cmPcnahgjsNBggVm/625f4267163a0acd29e77357a29591de/Screenshot_2022-08-26_at_16-48-35_Widget.png)
+![Widget 2](https://images.ctfassets.net/alneenqid6w5/5gdzo6cmPcnahgjsNBggVm/625f4267163a0acd29e77357a29591de/Screenshot_2022-08-26_at_16-48-35_Widget.png)
 
 Selecione qual será o **link** do seu Widget:
 
-![Widget 3](//images.ctfassets.net/alneenqid6w5/3KLP64x03ZXU08YUj91rWO/7f4164e710339ea907d081da684e5a20/Screenshot_2022-08-26_at_16-52-25_Widget.png)
+![Widget 3](https://images.ctfassets.net/alneenqid6w5/3KLP64x03ZXU08YUj91rWO/7f4164e710339ea907d081da684e5a20/Screenshot_2022-08-26_at_16-52-25_Widget.png)
 
 Lembrando: Seu widget ficará disponível para visualização durante a configuração para que você acompanhe as alterações simultaneamente, no canto inferior direito.
 
 Defina agora as **configurações:**
 
-![Widget 4](//images.ctfassets.net/alneenqid6w5/4jdAfiLbtqcX6PjueiA6nk/46ad924295bd825ca9629270d2041d42/Screenshot_2022-08-26_at_16-52-32_Widget.png)
+![Widget 4](https://images.ctfassets.net/alneenqid6w5/4jdAfiLbtqcX6PjueiA6nk/46ad924295bd825ca9629270d2041d42/Screenshot_2022-08-26_at_16-52-32_Widget.png)
 
 Entre as opções, é possível definir o **tamanho** do Widget, se ficará **posicionado** no canto inferior esquerdo ou direito e também, se terá **ícone ou título, balão com mensagem** ou não.
 
@@ -49,24 +49,24 @@ Dica: explore todas as opções para escolher qual se adequa ao seu objetivo.
 
 Você também pode configurar **Gatilhos** para o seu Widget, ou seja, definir quando ele ficará visivel ou não para o seu cliente. 
 
-![Widget 5](//images.ctfassets.net/alneenqid6w5/3Adkuu3v93Bi7t0boSDTrN/e1e66f29e390c15bde4d2e1cf6b7d3d4/Screenshot_2022-08-26_at_16-52-38_Widget.png)
+![Widget 5](https://images.ctfassets.net/alneenqid6w5/3Adkuu3v93Bi7t0boSDTrN/e1e66f29e390c15bde4d2e1cf6b7d3d4/Screenshot_2022-08-26_at_16-52-38_Widget.png)
 
 Defina em quais **páginas** do seu site o Widget aparecerá:
 
-![Widget 6](//images.ctfassets.net/alneenqid6w5/3tfk4LFq53xFe71wCzaKl7/82271947ed49cd1ce205d2860dc19ec7/Screenshot_2022-08-26_at_16-52-41_Widget.png)
+![Widget 6](https://images.ctfassets.net/alneenqid6w5/3tfk4LFq53xFe71wCzaKl7/82271947ed49cd1ce205d2860dc19ec7/Screenshot_2022-08-26_at_16-52-41_Widget.png)
 
 É possível definir também se o clique no Widget direcionará seu cliente para uma nova aba, ou se o link destino será aberto na mesma aba.
 
-![Widget 7](//images.ctfassets.net/alneenqid6w5/01vdpRCpknmKAuCn4Vepve/8272a56f4daf91e749bd35c8b2a461b9/Screenshot_2022-08-26_at_16-52-46_Widget.png)
+![Widget 7](https://images.ctfassets.net/alneenqid6w5/01vdpRCpknmKAuCn4Vepve/8272a56f4daf91e749bd35c8b2a461b9/Screenshot_2022-08-26_at_16-52-46_Widget.png)
 
 Após definir as configurações, gatilhos e ação do clique, acesse _**“Salvar”**_
 
 Para instalar o Widget no seu site, acesse o menu _**\\"Widget\\"**_ e depois em _**\\"Instalação\\"**_:
 
-![Widget 8](//images.ctfassets.net/alneenqid6w5/14g7BJkYhfCrn5l2W4GQB5/c1929880319410d55d389976bd1ba456/Screenshot_2022-08-26_at_16-52-51_Widget.png)
+![Widget 8](https://images.ctfassets.net/alneenqid6w5/14g7BJkYhfCrn5l2W4GQB5/c1929880319410d55d389976bd1ba456/Screenshot_2022-08-26_at_16-52-51_Widget.png)
 
 Basta clicar em _**\\"copiar código\\"**_ e colar o código fornecido no _“Body”_ do painel administrativo do seu site:
 
-![Widget 9](//images.ctfassets.net/alneenqid6w5/6S6gSymknb9qibSStoAINz/d76815718ce166b4b922519224a9316c/Screenshot_2022-08-26_at_16-52-56_Widget.png)
+![Widget 9](https://images.ctfassets.net/alneenqid6w5/6S6gSymknb9qibSStoAINz/d76815718ce166b4b922519224a9316c/Screenshot_2022-08-26_at_16-52-56_Widget.png)
 
 E pronto, qualquer ajuste dentro do painel do VTEX Assisted Sales (SuiteShare), seá atualizado automaticamente no seu site, sem que seja necessária qualquer alteração no script.
diff --git a/docs/tutorials/pt/wix-suiteshare.md b/docs/tutorials/pt/wix-suiteshare.md
index aa556f003..008c6819d 100644
--- a/docs/tutorials/pt/wix-suiteshare.md
+++ b/docs/tutorials/pt/wix-suiteshare.md
@@ -19,11 +19,11 @@ Para instalar o script do VTEX Assisted Sales (SuiteShare) no seu site do Wix, 
 
 Para isso, você deve acessar seu painel do Wix e clicar em **_Configurações > Acompanhamento e Análises_**.
 
-![Wix_1](//images.ctfassets.net/alneenqid6w5/7H7h9u61B7hV52gAJlzOtv/bf8fb87c8ee103a11575009809a83510/Wix_1.png)
+![Wix_1](https://images.ctfassets.net/alneenqid6w5/7H7h9u61B7hV52gAJlzOtv/bf8fb87c8ee103a11575009809a83510/Wix_1.png)
 
 Na janela que será aberta, o próximo passo é clicar em **_Nova Ferramenta > Personalizado_**.
 
-![Wix_2](//images.ctfassets.net/alneenqid6w5/26eIVGEMNUEfq9FmPzE2T1/46e34a3251d12d5471d45d37d2cffa81/Wix_2.png)
+![Wix_2](https://images.ctfassets.net/alneenqid6w5/26eIVGEMNUEfq9FmPzE2T1/46e34a3251d12d5471d45d37d2cffa81/Wix_2.png)
 
 Preencha então os seguintes campos:
 - **Cole o trecho do código aqui**: insira seu código de instalação (script) do VTEX Assisted Sales (SuiteShare).
@@ -33,7 +33,7 @@ Preencha então os seguintes campos:
 
 Salve a nova configuração.
 
-![Wix_3](//images.ctfassets.net/alneenqid6w5/1HQbRhPZamrTy4qwMtR1iM/0b9835329e68004479cf4d8cf49212a9/Wix_3.png)
+![Wix_3](https://images.ctfassets.net/alneenqid6w5/1HQbRhPZamrTy4qwMtR1iM/0b9835329e68004479cf4d8cf49212a9/Wix_3.png)
 
 Pronto! Agora o chat do VTEX Assisted Sales (SuiteShare) estará disponível no seu site do Wix.
 
diff --git a/docs/tutorials/pt/wordpress-suiteshare.md b/docs/tutorials/pt/wordpress-suiteshare.md
index eb76d4478..cec286bd8 100644
--- a/docs/tutorials/pt/wordpress-suiteshare.md
+++ b/docs/tutorials/pt/wordpress-suiteshare.md
@@ -21,14 +21,14 @@ Após realizar o download, você deve acessar seu wordpress clicar em: **Plugin
 
 Selecione o arquivo que você acabou de fazer download e instale.
 
-![Wordpress 1](//images.ctfassets.net/alneenqid6w5/1QRLLMPv7aDIYIxyJ8wIoC/93e8387838b2f916cd5dc1b9097def28/Screenshot_2022-08-30_at_12-00-57_Wordpress.png)
+![Wordpress 1](https://images.ctfassets.net/alneenqid6w5/1QRLLMPv7aDIYIxyJ8wIoC/93e8387838b2f916cd5dc1b9097def28/Screenshot_2022-08-30_at_12-00-57_Wordpress.png)
 
 O próximo passo é clicar em **Plugins** no menu do seu Wordpress e ativar o plugin do VTEX Assisted Sales (SuiteShare).
 
-![Wordpress 2](//images.ctfassets.net/alneenqid6w5/1BUOMxdFlKQYcUmNqNxZ7j/8c1e91fdb619bfe0033cccf3d2e6e638/Screenshot_2022-08-30_at_12-01-02_Wordpress.png)
+![Wordpress 2](https://images.ctfassets.net/alneenqid6w5/1BUOMxdFlKQYcUmNqNxZ7j/8c1e91fdb619bfe0033cccf3d2e6e638/Screenshot_2022-08-30_at_12-01-02_Wordpress.png)
 
 Por fim, após o plugin devidamente instalado e ativado só precisamos acessar **Configurações** -> **VTEX Assisted Sales (SuiteShare)**, aqui você deve marcar a opção **Ativar Plugin** e também preencher o campo token com o seu token: 
 
-![Wordpress 3](//images.ctfassets.net/alneenqid6w5/63DIufRLNRJQws24szLTS1/839c6cfd2e7b5523baaebca1c7831cb0/Screenshot_2022-08-30_at_12-01-08_Wordpress.png)
+![Wordpress 3](https://images.ctfassets.net/alneenqid6w5/63DIufRLNRJQws24szLTS1/839c6cfd2e7b5523baaebca1c7831cb0/Screenshot_2022-08-30_at_12-01-08_Wordpress.png)
 
 Agora se você já configurou um Chat, CTA ou Widget aqui na Suiteshare, ele irá começar a ser exibido no seu Wordpress.
diff --git a/docs/tutorials/pt/wow-to-integrate-with-multiplus.md b/docs/tutorials/pt/wow-to-integrate-with-multiplus.md
index bee26faca..50c8de7a0 100644
--- a/docs/tutorials/pt/wow-to-integrate-with-multiplus.md
+++ b/docs/tutorials/pt/wow-to-integrate-with-multiplus.md
@@ -28,7 +28,7 @@ Uma alternativa para os passos acima é acessar o painel de configuração de ma
 
 Substitua STORENAME pelo accountName da sua loja.
 
-![Multiplus1](//images.contentful.com/alneenqid6w5/2NxVrnsnZCOuQOqEOIusOq/d5cd381241a842c29e81763ea6f8f506/Multiplus1.png)
+![Multiplus1](https://images.contentful.com/alneenqid6w5/2NxVrnsnZCOuQOqEOIusOq/d5cd381241a842c29e81763ea6f8f506/Multiplus1.png)
 
 Após clicar em **Integrar**, será aberto um formulário com alguns campos a serem preenchidos. Atente-se aos campos obrigatórios: são aqueles em que aparece um “\*” ao lado da caixa de texto.
 
@@ -41,7 +41,7 @@ Após clicar em **Integrar**, será aberto um formulário com alguns campos a se
 - **Código Parceiro que será utilizado na Multiplus**: Este código deve conter de 1 a 30 dígitos, de sua escolha. Para habilitar suas vendas você deverá informar esse código à Multiplus após realizar a configuração no Bridge. Caso você altere esse código, o novo também deverá ser informado à Multiplus, que modo que seja feita a atualização. Caso isso não ocorra, a loja ficará impedida de realizar vendas;
 - **E-mails para a criação do Afiliado**: Depois que a configuração for salva, a integração criará o Afiliado na VTEX e inserirá essa informação no cadastro.
 
-![Multiplus2](//images.contentful.com/alneenqid6w5/4lTWbmFiGcOoIkUK8KSIAm/501d2f8e79300fc814d08ac600d7b0be/Multiplus2.png)
+![Multiplus2](https://images.contentful.com/alneenqid6w5/4lTWbmFiGcOoIkUK8KSIAm/501d2f8e79300fc814d08ac600d7b0be/Multiplus2.png)
 
 
 Após as informações estarem preenchidas, clique em **Salvar** e espere a mensagem de sucesso aparecer.
diff --git a/docs/tutorials/pt/zapier-suiteshare.md b/docs/tutorials/pt/zapier-suiteshare.md
index f8578ce53..57e2a7c8f 100644
--- a/docs/tutorials/pt/zapier-suiteshare.md
+++ b/docs/tutorials/pt/zapier-suiteshare.md
@@ -19,32 +19,32 @@ Para realizar a integração, acesse a plataforma **Zapier** clicando [aqui](htt
 
 Fazendo **login** ou criando uma **conta**.
 
-![Zapier_1](//images.ctfassets.net/alneenqid6w5/EQrfjNlvuFJMEv38vvptl/dec4fdb4b6c09c6b0ce30f5097226727/Zapier_1.png)
+![Zapier_1](https://images.ctfassets.net/alneenqid6w5/EQrfjNlvuFJMEv38vvptl/dec4fdb4b6c09c6b0ce30f5097226727/Zapier_1.png)
 
 Após a criação, personalize sua conta com suas **informações**.
 
-![Zapier_2](//images.ctfassets.net/alneenqid6w5/4vjr8JP1W1XG9Xzc2HhITd/7c42c60a14c836eeff91041de5f99d15/Zapier_2.png)
+![Zapier_2](https://images.ctfassets.net/alneenqid6w5/4vjr8JP1W1XG9Xzc2HhITd/7c42c60a14c836eeff91041de5f99d15/Zapier_2.png)
 
 Depois de configurado, pesquise o **VTEX Assisted Sales (SuiteShare)** nos aplicativos do **Zapier**.
 
 E conclua a configuração no **botão inferior**.
 
-![Zapier_3](//images.ctfassets.net/alneenqid6w5/1sF6axf20MhMIxzklT9mbi/7a148a23418c84341f97240ab1576c83/Zapier_3.png)
+![Zapier_3](https://images.ctfassets.net/alneenqid6w5/1sF6axf20MhMIxzklT9mbi/7a148a23418c84341f97240ab1576c83/Zapier_3.png)
 
 Crie seu fluxo de integração adicionando o **VTEX Assisted Sales (SuiteShare)** e a outra plataforma que desejar, e configure a ação que a integração fará.
 
-![Zapier_4](//images.ctfassets.net/alneenqid6w5/zfjtW84RbUzLM93CbmX2M/57c15b87bcb4e050986f07a00ba06c1b/Zapier_4.png)
+![Zapier_4](https://images.ctfassets.net/alneenqid6w5/zfjtW84RbUzLM93CbmX2M/57c15b87bcb4e050986f07a00ba06c1b/Zapier_4.png)
 
 Clique em **iniciar**.
 
-![Zapier_5](//images.ctfassets.net/alneenqid6w5/5jfRBJCFsW9XGErRInbWMh/fb77fd84708e430ca51969f2e2d85b0a/Zapier_5.png)
+![Zapier_5](https://images.ctfassets.net/alneenqid6w5/5jfRBJCFsW9XGErRInbWMh/fb77fd84708e430ca51969f2e2d85b0a/Zapier_5.png)
 
 Clique em **conectar** para acessar sua conta **VTEX Assisted Sales (SuiteShare)**.
 
-![Zapier_6](//images.ctfassets.net/alneenqid6w5/3Pl48zsf6uJhKhL73E5GYN/d5b4de316a721a92a8306920f2af46a9/Zapier_6.png)
+![Zapier_6](https://images.ctfassets.net/alneenqid6w5/3Pl48zsf6uJhKhL73E5GYN/d5b4de316a721a92a8306920f2af46a9/Zapier_6.png)
 
 Forneça seu email **VTEX Assisted Sales (SuiteShare)** e sua senha para realizar a **conexão**.
 
-![Zapier_7](//images.ctfassets.net/alneenqid6w5/7vbkoNnBLR8SYBG6mQireN/45eef9978e5715ff671c3dc06f0743e9/Zapier_7.png)
+![Zapier_7](https://images.ctfassets.net/alneenqid6w5/7vbkoNnBLR8SYBG6mQireN/45eef9978e5715ff671c3dc06f0743e9/Zapier_7.png)
 
 Pronto! Após o login, sua integração está pronta para ser utilizada!

From 39b7db652e0b84f0903d13a661110851d36fce7c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 11:59:36 -0300
Subject: [PATCH 03/13] fix quotation marks

---
 .../admin-global-search-doesnt-recognize-profile-menu-items.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
index da9f9980a..cdb09523a 100644
--- a/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
+++ b/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -1,5 +1,5 @@
 ---
-title: "[Admin] Global Search doesn't recognize "Profile Menu items""
+title: '[Admin] Global Search doesn't recognize "Profile Menu items"'
 id: 4AZiu9NXouL6b8z5EHJIWK
 status: PUBLISHED
 createdAt: 2024-01-22T17:09:55.423Z

From 8aaaef81c063e00f09c6a06d5b8c536eb8691d10 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 12:35:43 -0300
Subject: [PATCH 04/13] fix quotation marks

---
 .../admin-global-search-doesnt-recognize-profile-menu-items.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
index cdb09523a..8b3d0599a 100644
--- a/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
+++ b/docs/known-issues/en/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -1,5 +1,5 @@
 ---
-title: '[Admin] Global Search doesn't recognize "Profile Menu items"'
+title: "[Admin] Global Search doesn't recognize 'Profile Menu items'"
 id: 4AZiu9NXouL6b8z5EHJIWK
 status: PUBLISHED
 createdAt: 2024-01-22T17:09:55.423Z

From 47e2ed3ad8c3d5482a52028ce691d0d44b0b1418 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 15:32:59 -0300
Subject: [PATCH 05/13] Create replace-quotes.js

---
 docs-utils/replace-quotes.js | 82 ++++++++++++++++++++++++++++++++++++
 1 file changed, 82 insertions(+)
 create mode 100644 docs-utils/replace-quotes.js

diff --git a/docs-utils/replace-quotes.js b/docs-utils/replace-quotes.js
new file mode 100644
index 000000000..4e375a07b
--- /dev/null
+++ b/docs-utils/replace-quotes.js
@@ -0,0 +1,82 @@
+const fs = require('fs');
+const path = require('path');
+
+// Path to the 'docs' directory
+const docsDir = path.resolve(__dirname, '../docs');
+
+// Function to process each Markdown file
+const processFile = (filePath) => {
+  const data = fs.readFileSync(filePath, 'utf8');
+  const lines = data.split('\n');
+
+  if (lines[1] && lines[1].startsWith('title:')) {
+    let titleLine = lines[1].trim();
+    const titleContentMatch = titleLine.match(/^title:\s*(['"])(.*)\1$/);
+
+    if (titleContentMatch) {
+      const currentOuterQuote = titleContentMatch[1];
+      const originalTitleContent = titleContentMatch[2];
+      let updatedTitleContent;
+      let updatedTitleLine;
+
+      if (currentOuterQuote === `'`) {
+        // Outer quotes are single
+        if (originalTitleContent.includes('"')) {
+          // Inner double quotes present
+          updatedTitleContent = originalTitleContent.replace(/"/g, "'");
+          updatedTitleLine = `title: "${updatedTitleContent}"`;
+        } else {
+          // No inner double quotes
+          updatedTitleLine = titleLine;
+        }
+      } else if (currentOuterQuote === `"`) {
+        // Outer quotes are double
+        if (originalTitleContent.includes('"')) {
+          // Inner double quotes present
+          updatedTitleContent = originalTitleContent.replace(/"(?![^"]*")/g, "'");
+          updatedTitleLine = `title: "${updatedTitleContent}"`;
+        } else {
+          // No inner double quotes
+          updatedTitleLine = titleLine;
+        }
+      }
+
+      // Only update if necessary
+      if (updatedTitleLine && updatedTitleLine !== titleLine) {
+        lines[1] = updatedTitleLine;
+        const newData = lines.join('\n');
+        fs.writeFileSync(filePath, newData, 'utf8');
+        console.log(`Updated file: ${filePath}`);
+      }
+    }
+  }
+};
+
+// Function to recursively process files in directories
+const processDirectory = (dirPath) => {
+  fs.readdir(dirPath, (err, files) => {
+    if (err) {
+      console.error('Unable to scan directory:', err);
+      return;
+    }
+
+    files.forEach((file) => {
+      const filePath = path.join(dirPath, file);
+      fs.stat(filePath, (err, stats) => {
+        if (err) {
+          console.error('Unable to stat file:', err);
+          return;
+        }
+
+        if (stats.isDirectory()) {
+          processDirectory(filePath);
+        } else if (path.extname(file) === '.md') {
+          processFile(filePath);
+        }
+      });
+    });
+  });
+};
+
+// Start processing from the docs directory
+processDirectory(docsDir);

From 85125d3012807e46458c144b039cc512d91a048c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 15:49:52 -0300
Subject: [PATCH 06/13] massively fix quotation marks

---
 .../en/New-returned-object-in-API-Get-Order-itemMetadata.md     | 2 +-
 ...power-your-customers-with-the-new-reviews-and-ratings-app.md | 2 +-
 ...ipping-learn-what-has-changed-in-the-inventory-management.md | 2 +-
 ...ry-and-shipping-see-what-has-changed-in-the-dashboard-tab.md | 2 +-
 .../en/maximum-price-per-item-promotion-will-be-disabled.md     | 2 +-
 .../en/new-object-returned-to-api-get-order-cancelreason.md     | 2 +-
 .../en/new-returned-object-in-api-get-order-cancelreason.md     | 2 +-
 ...odule-will-be-discontinued-migrate-your-data-until-august.md | 2 +-
 .../the-items-field-will-be-removed-from-the-list-orders-api.md | 2 +-
 ...ofile-has-been-replaced-by-the-term-role-in-your-admin-ui.md | 2 +-
 .../es/New-returned-object-in-API-Get-Order-itemMetadata.md     | 2 +-
 ...power-your-customers-with-the-new-reviews-and-ratings-app.md | 2 +-
 ...ipping-learn-what-has-changed-in-the-inventory-management.md | 2 +-
 ...ry-and-shipping-see-what-has-changed-in-the-dashboard-tab.md | 2 +-
 .../es/maximum-price-per-item-promotion-will-be-disabled.md     | 2 +-
 .../es/new-object-returned-to-api-get-order-cancelreason.md     | 2 +-
 .../es/new-returned-object-in-api-get-order-cancelreason.md     | 2 +-
 .../the-items-field-will-be-removed-from-the-list-orders-api.md | 2 +-
 .../pt/New-returned-object-in-API-Get-Order-itemMetadata.md     | 2 +-
 ...power-your-customers-with-the-new-reviews-and-ratings-app.md | 2 +-
 ...ipping-learn-what-has-changed-in-the-inventory-management.md | 2 +-
 ...ry-and-shipping-see-what-has-changed-in-the-dashboard-tab.md | 2 +-
 .../pt/new-object-returned-to-api-get-order-cancelreason.md     | 2 +-
 .../pt/new-returned-object-in-api-get-order-cancelreason.md     | 2 +-
 ...odule-will-be-discontinued-migrate-your-data-until-august.md | 2 +-
 .../the-items-field-will-be-removed-from-the-list-orders-api.md | 2 +-
 docs/faq/en/checkout-with-store-not-found-error.md              | 2 +-
 ...lid-header-signature-ao-tentar-importar-planilha-de-frete.md | 2 +-
 ...t-reference-not-set-to-an-instance-of-an-object-ao-tentar.md | 2 +-
 ...imit-of-activated-calculators-has-been-reached-what-to-do.md | 2 +-
 .../en/order-is-locked-in-ready-for-handling-what-do-i-do.md    | 2 +-
 .../order-is-locked-in-ready-for-handling-what-should-i-do.md   | 2 +-
 ...d-in-the-erp-but-remains-in-the-preparing-delivery-status.md | 2 +-
 .../en/what-to-do-when-the-notify-me-option-is-not-displayed.md | 2 +-
 ...-managment-returns-authorize-fulfillment-error-what-to-do.md | 2 +-
 ...-does-the-message-the-timespan-could-not-be-parsed-appear.md | 2 +-
 docs/faq/en/why-is-the-thumb-image-of-poor-quality.md           | 2 +-
 docs/faq/es/checkout-with-store-not-found-error.md              | 2 +-
 ...lid-header-signature-ao-tentar-importar-planilha-de-frete.md | 2 +-
 ...t-reference-not-set-to-an-instance-of-an-object-ao-tentar.md | 2 +-
 ...imit-of-activated-calculators-has-been-reached-what-to-do.md | 2 +-
 .../es/order-is-locked-in-ready-for-handling-what-do-i-do.md    | 2 +-
 .../order-is-locked-in-ready-for-handling-what-should-i-do.md   | 2 +-
 ...d-in-the-erp-but-remains-in-the-preparing-delivery-status.md | 2 +-
 ...-managment-returns-authorize-fulfillment-error-what-to-do.md | 2 +-
 ...-does-the-message-the-timespan-could-not-be-parsed-appear.md | 2 +-
 ...doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md | 2 +-
 docs/faq/es/why-has-my-order-stopped-on-ready-for-handling.md   | 2 +-
 docs/faq/es/why-is-let-me-know-not-showing.md                   | 2 +-
 docs/faq/es/why-is-the-thumb-image-of-poor-quality.md           | 2 +-
 docs/faq/pt/checkout-with-store-not-found-error.md              | 2 +-
 ...lid-header-signature-ao-tentar-importar-planilha-de-frete.md | 2 +-
 ...t-reference-not-set-to-an-instance-of-an-object-ao-tentar.md | 2 +-
 ...imit-of-activated-calculators-has-been-reached-what-to-do.md | 2 +-
 .../pt/order-is-locked-in-ready-for-handling-what-do-i-do.md    | 2 +-
 .../order-is-locked-in-ready-for-handling-what-should-i-do.md   | 2 +-
 ...tacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md | 2 +-
 ...d-in-the-erp-but-remains-in-the-preparing-delivery-status.md | 2 +-
 docs/faq/pt/untitled-entry-2017-05-24-at-20-19-07.md            | 2 +-
 .../pt/what-to-do-when-the-notify-me-option-is-not-displayed.md | 2 +-
 ...-does-the-message-the-timespan-could-not-be-parsed-appear.md | 2 +-
 ...doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md | 2 +-
 docs/faq/pt/why-has-my-order-stopped-on-ready-for-handling.md   | 2 +-
 docs/faq/pt/why-is-let-me-know-not-showing.md                   | 2 +-
 docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md           | 2 +-
 ...e-active-and-have-the-activate-if-possible-flag-unchecked.md | 2 +-
 ...ounts-with-on-the-name-dont-have-metrics-on-search-report.md | 2 +-
 .../en/add-option-not-available-when-creating-dictionary.md     | 2 +-
 ...address-field-comes-with-null-vaule-in-payments-api-query.md | 2 +-
 ...orm-with-excessive-size-for-multiples-cities-separated-by.md | 2 +-
 ...n-the-checkout-when-buyer-has-can-add-shipping-permission.md | 2 +-
 ...dressid-mismatch-causes-invalid-address-for-an-item-error.md | 2 +-
 ...age-has-an-error-in-how-to-improve-section-of-the-catalog.md | 2 +-
 .../alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md | 2 +-
 ...azon-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 .../an-error-has-occurred-when-adding-tracking-information.md   | 2 +-
 ...tachents-api-doesnt-allow-null-domainvalues-and-it-should.md | 2 +-
 .../en/audit-pricing-logs-showing-unknow-information.md         | 2 +-
 ...lete-suggestion-api-removes-the-dot-from-the-product-name.md | 2 +-
 ...ly-when-set-to-calculate-during-the-first-hour-of-the-day.md | 2 +-
 ...-in-fulfillment-simulation-for-no-stock-or-price-products.md | 2 +-
 docs/known-issues/en/aviseme-report-does-not-open.md            | 2 +-
 .../en/b2w-b2w-direct-order-fob-integrating-with-carrier.md     | 2 +-
 .../en/b2w-order-with-parameter-count-mismatch-error.md         | 2 +-
 .../en/back-button-is-not-rendered-in-my-organization.md        | 2 +-
 ...akes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md | 2 +-
 .../bad-request-when-searching-terms-with-directly-via-url.md   | 2 +-
 ...ad-request-when-searching-terms-with-through-autocomplete.md | 2 +-
 ...-cancel-inside-the-mycards-page-not-translated-to-spanish.md | 2 +-
 ...-ui-changing-different-from-to-equal-to-with-a-collection.md | 2 +-
 ...rs-email-is-not-being-placed-as-expected-in-the-orderform.md | 2 +-
 ...displays-empty-cart-message-while-screen-is-still-loading.md | 2 +-
 ...-export-does-not-show-sales-channels-when-none-are-tagged.md | 2 +-
 .../catalog-indexing-report-total-section-calculation-error.md  | 2 +-
 .../centauro-orders-with-pedido-sem-o-campo-packages-error.md   | 2 +-
 docs/known-issues/en/centauro-to-implement-centauro-envios.md   | 2 +-
 ...e-my-account-page-do-not-appear-immediately-in-the-domain.md | 2 +-
 ...ckbox-requires-authentication-doesnt-work-on-pages-module.md | 2 +-
 ...lit-may-generate-incorrect-information-in-the-paymentdata.md | 2 +-
 ...ns-value-0-in-slastax-field-for-shipping-percentage-taxes.md | 2 +-
 ...g-lean-shipping-for-items-with-no-common-shipping-methods.md | 2 +-
 ...selects-the-schedule-all-toggle-after-refreshing-the-page.md | 2 +-
 ...lways-appearing-as-equal-to-on-the-campaign-audience-form.md | 2 +-
 ...ilablepersaleschannel-in-searches-portal-and-search-again.md | 2 +-
 ...stom-fields-for-custom-data-converts-the-ids-to-lowercase.md | 2 +-
 ...edit-total-due-value-updating-according-to-the-pagination.md | 2 +-
 ...ng-lost-when-it-has-some-order-with-profileerroronloading.md | 2 +-
 ...o-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md | 2 +-
 ...ction-got-reprocessed-after-some-retries-to-authorization.md | 2 +-
 ...rocessing-the-shipping-policy-locked-in-processing-status.md | 2 +-
 ...mtocheckfirstinstallment-configuration-and-splitted-items.md | 2 +-
 ...cation-choose-a-more-specific-global-category-persistente.md | 2 +-
 ...did-when-creating-a-promotion-excluding-more-than-1-brand.md | 2 +-
 ...rder-the-same-item-cannot-have-more-than-one-sla-selected.md | 2 +-
 ...lit-value-in-recipients-is-different-than-operation-value.md | 2 +-
 ...error-in-refund-value-cannot-be-null-parameter-name-value.md | 2 +-
 .../en/error-integrating-sku-field-may-not-be-null-magalu.md    | 2 +-
 ...pting-to-perform-a-search-using-the-all-field-in-vtex-crm.md | 2 +-
 ...wrong-please-try-again-when-adding-images-via-site-editor.md | 2 +-
 ...with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md | 2 +-
 .../en/ey-send-kit-is-not-recording-a-change-in-the-card.md     | 2 +-
 ...address-step-causes-the-go-to-payment-button-to-disappear.md | 2 +-
 ...eturns-is-not-updating-on-seller-management-ui-after-save.md | 2 +-
 docs/known-issues/en/field-reference-always-set-as-null.md      | 2 +-
 ...-by-productclusternames-while-applying-additional-filters.md | 2 +-
 ...n-the-catalog-admin-can-show-the-wrong-ammount-of-results.md | 2 +-
 ...t-search-in-a-store-is-not-considered-on-ui-last-searches.md | 2 +-
 ...t-to-the-cheapest-shipping-option-not-working-as-expected.md | 2 +-
 ...-external-marketplace-integrate-an-order-erro-code-fmt010.md | 2 +-
 ...tions-api-doesnt-keep-same-sku-order-when-changing-limits.md | 2 +-
 .../en/get-product-by-refid-returning-null-when-not-found.md    | 2 +-
 ...d-hub-is-adding-an-extra-backslash-when-calling-providers.md | 2 +-
 ...ields-caption-and-relationname-when-we-make-a-get-request.md | 2 +-
 ...iftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md | 2 +-
 ...split-when-switching-between-delivery-and-pick-up-options.md | 2 +-
 ...your-store-saving-incorrectly-on-promotion-form-interface.md | 2 +-
 ...ion-page-is-redirecting-to-the-wedding-list-creation-page.md | 2 +-
 ...ts-the-order-of-products-if-import-is-made-based-on-skuid.md | 2 +-
 ...ncorrect-address-format-on-the-my-cards-billing-addresses.md | 2 +-
 ...lit-value-in-recipients-is-different-than-operation-value.md | 2 +-
 ...-doesnt-accept-urls-from-servers-that-require-user-agents.md | 2 +-
 ...ropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md | 2 +-
 ...-address-is-in-available-addresses-with-different-country.md | 2 +-
 ...sible-to-save-some-addresses-from-argentina-in-my-account.md | 2 +-
 ...-possible-to-save-some-addresses-from-chile-in-my-account.md | 2 +-
 ...nd-indexed-text-not-being-changed-by-specification-import.md | 2 +-
 ...-causes-something-went-wrong-after-changing-pickup-points.md | 2 +-
 .../en/legacy-catalog-ui-delete-button-not-functional.md        | 2 +-
 ...he-product-is-not-available-for-the-websites-trade-policy.md | 2 +-
 ...ategory-on-category-setup-only-works-opening-in-a-new-tab.md | 2 +-
 ...eport-does-not-apply-filter-correctly-in-orders-managment.md | 2 +-
 ...inventory-full-access-permission-did-not-work-as-expected.md | 2 +-
 ...rror-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 ...ine-luiza-integrated-fob-order-with-conventional-delivery.md | 2 +-
 ...rror-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 ...ng-selected-as-merchantname-in-the-subaccount-environment.md | 2 +-
 ...tch-multiple-received-skus-api-returning-invalid-sellerid.md | 2 +-
 ...-less-applies-incorrect-discount-when-using-the-same-item.md | 2 +-
 ...o-update-a-document-passing-a-symbol-or-special-character.md | 2 +-
 ...-sku-integration-input-string-was-not-in-a-correct-format.md | 2 +-
 ...ation-is-receiving-errors-from-meli-429-too-many-requests.md | 2 +-
 .../en/meli-integration-zipcodes-11111-meli-limaperu.md         | 2 +-
 ...bject-reference-not-set-to-an-instance-of-an-object-error.md | 2 +-
 ...ndising-rules-not-working-for-the-facet-productclusterids.md | 2 +-
 .../message-freight-value-has-changed-is-shown-incorrectly.md   | 2 +-
 ...koutgraphql-while-sending-options-for-already-added-items.md | 2 +-
 .../en/my-account-page-does-not-work-on-domain-myvtex-com.md    | 2 +-
 ...vos-does-not-automatically-translate-on-the-product-admin.md | 2 +-
 ...epontos-function-does-not-work-inside-the-automatic-field.md | 2 +-
 ...ly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md | 2 +-
 docs/known-issues/en/orders-with-error-sistema-de-perfis.md     | 2 +-
 .../en/portal-dont-respect-the-tag-principal-of-skus-image.md   | 2 +-
 ...cy-depends-on-the-page-it-is-shown-on-the-admin-interface.md | 2 +-
 ...ter-applied-on-top-of-spot-price-instead-of-regular-price.md | 2 +-
 .../prices-restricted-to-int32-max-value-on-change-price-api.md | 2 +-
 .../en/prices-restricted-to-int32-max-value-on-checkout-apis.md | 2 +-
 ...oritization-by-products-keyword-not-considering-stopwords.md | 2 +-
 ...lems-opening-manage-inventory-by-admin-page-with-error-ui.md | 2 +-
 .../problems-with-price-from-in-the-buttonbuymodal-control.md   | 2 +-
 .../product-insertupdate-api-allows-n-in-the-textlink-field.md  | 2 +-
 ...-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md | 2 +-
 ...ion-filter-on-collection-module-assuming-incorrect-values.md | 2 +-
 ...lier-wrongly-flagged-as-with-promotion-for-search-filters.md | 2 +-
 ...cant-be-finished-and-is-stuck-on-freight-type-has-changed.md | 2 +-
 ...shed-and-returns-the-error-receiver-name-field-is-invalid.md | 2 +-
 .../en/received-skus-review-tab-missing-products.md             | 2 +-
 ...seller-1-correctly-while-requesting-nonwhitelabel-sellers.md | 2 +-
 ...ers-not-following-the-operator-and-for-trigger-conditions.md | 2 +-
 .../en/secondlevel-folders-dont-consider-the-search-context.md  | 2 +-
 .../en/settings-ui-doesnt-update-expiration-period-of-quotes.md | 2 +-
 ...ng-component-locked-in-waiting-for-more-information-state.md | 2 +-
 ...n-dismissed-as-a-matter-of-priority-even-with-better-cost.md | 2 +-
 ...-insert-file-api-is-not-responding-with-the-text-property.md | 2 +-
 ...ng-when-adding-an-incomplete-address-and-tried-to-edit-it.md | 2 +-
 .../special-character-not-mapped-to-be-ignored-in-textlink.md   | 2 +-
 .../en/status-erro-de-processamento-shipping-policy.md          | 2 +-
 .../en/stockkeepingunitbyean-returns-404-for-eans-with-.md      | 2 +-
 docs/known-issues/en/store-texts-search-doesnt-work.md          | 2 +-
 .../en/storefront-permissions-app-sets-documenttype-as-cpf.md   | 2 +-
 ...mporting-after-uploading-the-skus-association-spreadsheet.md | 2 +-
 ...esales-search-doesnt-accept-special-characters-aside-from.md | 2 +-
 ...nk-created-with-on-marketplace-upon-approvals-reoccurence.md | 2 +-
 ...atus-even-in-scenarios-when-the-authentication-has-failed.md | 2 +-
 ...-in-my-orders-when-the-order-has-the-same-shipping-method.md | 2 +-
 ...d-does-not-change-when-the-updating-is-done-by-webservice.md | 2 +-
 ...n-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md | 2 +-
 ...he-wrong-language-when-using-checkout-in-catalan-language.md | 2 +-
 ...d-option-does-not-work-for-asynchronous-payment-providers.md | 2 +-
 ...e-new-card-option-does-not-work-when-using-3-d-secure-3ds.md | 2 +-
 ...toriodeimportacaodeestoque-does-not-support-multilanguage.md | 2 +-
 ...timeout-timeout-no-request-para-o-sistema-de-parcelamento.md | 2 +-
 ...nsaction-cancellation-error-with-unreachable-code-message.md | 2 +-
 ...i-shows-gifts-picked-when-using-order-replacement-feature.md | 2 +-
 ...ay-when-transaction-cart-object-in-transaction-is-unknown.md | 2 +-
 .../en/unable-to-create-produtos-relacionados-custom-element.md | 2 +-
 ...nhandled-exception-error-when-changing-edition-of-account.md | 2 +-
 .../url-logo-field-in-the-update-seller-request-not-updating.md | 2 +-
 ...er-administrator-restricted-is-not-able-to-list-the-users.md | 2 +-
 .../version-author-note-not-found-on-vtex-id-on-the-profile.md  | 2 +-
 .../en/visited-product-feature-does-not-work-properly.md        | 2 +-
 .../en/vtexcontentplaceholder-idacessorios-is-not-working.md    | 2 +-
 ...name-is-not-displayed-in-the-order-and-email-notification.md | 2 +-
 ...aping-page-on-admin-the-initial-message-is-not-translated.md | 2 +-
 ...de-as-refundmanually-our-gateway-performs-a-double-refund.md | 2 +-
 docs/known-issues/en/xml-currency-symbol-in-the-installment.md  | 2 +-
 .../en/xmls-product-name-flag-not-working-properly.md           | 2 +-
 ...e-active-and-have-the-activate-if-possible-flag-unchecked.md | 2 +-
 ...ounts-with-on-the-name-dont-have-metrics-on-search-report.md | 2 +-
 .../es/add-option-not-available-when-creating-dictionary.md     | 2 +-
 ...address-field-comes-with-null-vaule-in-payments-api-query.md | 2 +-
 ...orm-with-excessive-size-for-multiples-cities-separated-by.md | 2 +-
 ...n-the-checkout-when-buyer-has-can-add-shipping-permission.md | 2 +-
 ...dressid-mismatch-causes-invalid-address-for-an-item-error.md | 2 +-
 .../admin-global-search-doesnt-recognize-profile-menu-items.md  | 2 +-
 ...age-has-an-error-in-how-to-improve-section-of-the-catalog.md | 2 +-
 .../alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md | 2 +-
 ...azon-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 .../an-error-has-occurred-when-adding-tracking-information.md   | 2 +-
 ...ght-who-bought-also-bought-not-always-working-as-expected.md | 2 +-
 ...tachents-api-doesnt-allow-null-domainvalues-and-it-should.md | 2 +-
 .../es/audit-pricing-logs-showing-unknow-information.md         | 2 +-
 ...lete-suggestion-api-removes-the-dot-from-the-product-name.md | 2 +-
 ...-in-fulfillment-simulation-for-no-stock-or-price-products.md | 2 +-
 docs/known-issues/es/aviseme-report-does-not-open.md            | 2 +-
 .../es/b2w-b2w-direct-order-fob-integrating-with-carrier.md     | 2 +-
 .../es/b2w-order-with-parameter-count-mismatch-error.md         | 2 +-
 .../es/back-button-is-not-rendered-in-my-organization.md        | 2 +-
 ...akes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md | 2 +-
 .../bad-request-when-searching-terms-with-directly-via-url.md   | 2 +-
 ...ad-request-when-searching-terms-with-through-autocomplete.md | 2 +-
 .../es/bug-in-cart-with-promotion-when-splitting-item.md        | 2 +-
 ...-cancel-inside-the-mycards-page-not-translated-to-spanish.md | 2 +-
 ...-ui-changing-different-from-to-equal-to-with-a-collection.md | 2 +-
 ...rs-email-is-not-being-placed-as-expected-in-the-orderform.md | 2 +-
 ...displays-empty-cart-message-while-screen-is-still-loading.md | 2 +-
 ...-export-does-not-show-sales-channels-when-none-are-tagged.md | 2 +-
 .../catalog-indexing-report-total-section-calculation-error.md  | 2 +-
 .../centauro-orders-with-pedido-sem-o-campo-packages-error.md   | 2 +-
 docs/known-issues/es/centauro-to-implement-centauro-envios.md   | 2 +-
 ...e-my-account-page-do-not-appear-immediately-in-the-domain.md | 2 +-
 ...ckbox-requires-authentication-doesnt-work-on-pages-module.md | 2 +-
 ...lit-may-generate-incorrect-information-in-the-paymentdata.md | 2 +-
 ...ns-value-0-in-slastax-field-for-shipping-percentage-taxes.md | 2 +-
 ...g-lean-shipping-for-items-with-no-common-shipping-methods.md | 2 +-
 ...selects-the-schedule-all-toggle-after-refreshing-the-page.md | 2 +-
 ...lways-appearing-as-equal-to-on-the-campaign-audience-form.md | 2 +-
 ...vailable-in-catalog-sellers-cms-and-gift-card-modules-for.md | 2 +-
 ...ilablepersaleschannel-in-searches-portal-and-search-again.md | 2 +-
 ...stom-fields-for-custom-data-converts-the-ids-to-lowercase.md | 2 +-
 ...edit-total-due-value-updating-according-to-the-pagination.md | 2 +-
 ...ng-lost-when-it-has-some-order-with-profileerroronloading.md | 2 +-
 ...o-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md | 2 +-
 ...ction-got-reprocessed-after-some-retries-to-authorization.md | 2 +-
 ...rocessing-the-shipping-policy-locked-in-processing-status.md | 2 +-
 ...mtocheckfirstinstallment-configuration-and-splitted-items.md | 2 +-
 ...cation-choose-a-more-specific-global-category-persistente.md | 2 +-
 ...did-when-creating-a-promotion-excluding-more-than-1-brand.md | 2 +-
 ...rder-the-same-item-cannot-have-more-than-one-sla-selected.md | 2 +-
 ...lit-value-in-recipients-is-different-than-operation-value.md | 2 +-
 ...error-in-refund-value-cannot-be-null-parameter-name-value.md | 2 +-
 .../es/error-integrating-sku-field-may-not-be-null-magalu.md    | 2 +-
 ...pting-to-perform-a-search-using-the-all-field-in-vtex-crm.md | 2 +-
 ...wrong-please-try-again-when-adding-images-via-site-editor.md | 2 +-
 ...with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md | 2 +-
 .../es/ey-send-kit-is-not-recording-a-change-in-the-card.md     | 2 +-
 ...address-step-causes-the-go-to-payment-button-to-disappear.md | 2 +-
 ...eturns-is-not-updating-on-seller-management-ui-after-save.md | 2 +-
 docs/known-issues/es/field-reference-always-set-as-null.md      | 2 +-
 ...-by-productclusternames-while-applying-additional-filters.md | 2 +-
 ...n-the-catalog-admin-can-show-the-wrong-ammount-of-results.md | 2 +-
 ...t-search-in-a-store-is-not-considered-on-ui-last-searches.md | 2 +-
 ...t-to-the-cheapest-shipping-option-not-working-as-expected.md | 2 +-
 ...-external-marketplace-integrate-an-order-erro-code-fmt010.md | 2 +-
 ...tions-api-doesnt-keep-same-sku-order-when-changing-limits.md | 2 +-
 .../es/get-product-by-refid-returning-null-when-not-found.md    | 2 +-
 ...d-hub-is-adding-an-extra-backslash-when-calling-providers.md | 2 +-
 ...ields-caption-and-relationname-when-we-make-a-get-request.md | 2 +-
 ...iftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md | 2 +-
 ...split-when-switching-between-delivery-and-pick-up-options.md | 2 +-
 ...your-store-saving-incorrectly-on-promotion-form-interface.md | 2 +-
 ...ion-page-is-redirecting-to-the-wedding-list-creation-page.md | 2 +-
 ...ts-the-order-of-products-if-import-is-made-based-on-skuid.md | 2 +-
 ...ncorrect-address-format-on-the-my-cards-billing-addresses.md | 2 +-
 ...lit-value-in-recipients-is-different-than-operation-value.md | 2 +-
 ...-doesnt-accept-urls-from-servers-that-require-user-agents.md | 2 +-
 ...ropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md | 2 +-
 ...-address-is-in-available-addresses-with-different-country.md | 2 +-
 ...-characters-in-category-names-cause-page-not-found-errors.md | 2 +-
 ...sible-to-save-some-addresses-from-argentina-in-my-account.md | 2 +-
 ...-possible-to-save-some-addresses-from-chile-in-my-account.md | 2 +-
 ...nd-indexed-text-not-being-changed-by-specification-import.md | 2 +-
 ...-causes-something-went-wrong-after-changing-pickup-points.md | 2 +-
 .../es/legacy-catalog-ui-delete-button-not-functional.md        | 2 +-
 ...ategory-on-category-setup-only-works-opening-in-a-new-tab.md | 2 +-
 ...eport-does-not-apply-filter-correctly-in-orders-managment.md | 2 +-
 ...inventory-full-access-permission-did-not-work-as-expected.md | 2 +-
 ...rror-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 ...ine-luiza-integrated-fob-order-with-conventional-delivery.md | 2 +-
 ...rror-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 ...ng-selected-as-merchantname-in-the-subaccount-environment.md | 2 +-
 ...tch-multiple-received-skus-api-returning-invalid-sellerid.md | 2 +-
 ...-less-applies-incorrect-discount-when-using-the-same-item.md | 2 +-
 ...o-update-a-document-passing-a-symbol-or-special-character.md | 2 +-
 ...-sku-integration-input-string-was-not-in-a-correct-format.md | 2 +-
 ...ation-is-receiving-errors-from-meli-429-too-many-requests.md | 2 +-
 .../es/meli-integration-zipcodes-11111-meli-limaperu.md         | 2 +-
 ...bject-reference-not-set-to-an-instance-of-an-object-error.md | 2 +-
 ...ndising-rules-not-working-for-the-facet-productclusterids.md | 2 +-
 .../message-freight-value-has-changed-is-shown-incorrectly.md   | 2 +-
 ...koutgraphql-while-sending-options-for-already-added-items.md | 2 +-
 .../es/my-account-page-does-not-work-on-domain-myvtex-com.md    | 2 +-
 ...vos-does-not-automatically-translate-on-the-product-admin.md | 2 +-
 ...epontos-function-does-not-work-inside-the-automatic-field.md | 2 +-
 ...ly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md | 2 +-
 docs/known-issues/es/orders-with-error-sistema-de-perfis.md     | 2 +-
 .../es/portal-dont-respect-the-tag-principal-of-skus-image.md   | 2 +-
 ...cy-depends-on-the-page-it-is-shown-on-the-admin-interface.md | 2 +-
 ...ter-applied-on-top-of-spot-price-instead-of-regular-price.md | 2 +-
 .../prices-restricted-to-int32-max-value-on-change-price-api.md | 2 +-
 .../es/prices-restricted-to-int32-max-value-on-checkout-apis.md | 2 +-
 ...oritization-by-products-keyword-not-considering-stopwords.md | 2 +-
 ...lems-opening-manage-inventory-by-admin-page-with-error-ui.md | 2 +-
 .../problems-with-price-from-in-the-buttonbuymodal-control.md   | 2 +-
 .../product-insertupdate-api-allows-n-in-the-textlink-field.md  | 2 +-
 ...-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md | 2 +-
 ...ion-filter-on-collection-module-assuming-incorrect-values.md | 2 +-
 ...t-with-type-text-does-not-trigger-the-products-indexation.md | 2 +-
 ...n-itemattachment-duplicate-when-the-quantity-is-increased.md | 2 +-
 ...lier-wrongly-flagged-as-with-promotion-for-search-filters.md | 2 +-
 ...cant-be-finished-and-is-stuck-on-freight-type-has-changed.md | 2 +-
 ...shed-and-returns-the-error-receiver-name-field-is-invalid.md | 2 +-
 ...isplayed-according-to-the-searched-zip-codes-availability.md | 2 +-
 .../es/received-skus-review-tab-missing-products.md             | 2 +-
 ...seller-1-correctly-while-requesting-nonwhitelabel-sellers.md | 2 +-
 ...ers-not-following-the-operator-and-for-trigger-conditions.md | 2 +-
 .../es/secondlevel-folders-dont-consider-the-search-context.md  | 2 +-
 .../es/settings-ui-doesnt-update-expiration-period-of-quotes.md | 2 +-
 ...ng-component-locked-in-waiting-for-more-information-state.md | 2 +-
 ...n-dismissed-as-a-matter-of-priority-even-with-better-cost.md | 2 +-
 ...lue-viewpart-incorrectly-displays-delivery-times-in-hours.md | 2 +-
 ...-insert-file-api-is-not-responding-with-the-text-property.md | 2 +-
 ...ng-message-when-accessing-a-and-p-routes-in-portal-stores.md | 2 +-
 ...ng-when-adding-an-incomplete-address-and-tried-to-edit-it.md | 2 +-
 .../special-character-not-mapped-to-be-ignored-in-textlink.md   | 2 +-
 .../es/status-erro-de-processamento-shipping-policy.md          | 2 +-
 .../es/stockkeepingunitbyean-returns-404-for-eans-with-.md      | 2 +-
 docs/known-issues/es/store-texts-search-doesnt-work.md          | 2 +-
 .../es/storefront-permissions-app-sets-documenttype-as-cpf.md   | 2 +-
 ...mporting-after-uploading-the-skus-association-spreadsheet.md | 2 +-
 ...esales-search-doesnt-accept-special-characters-aside-from.md | 2 +-
 ...nk-created-with-on-marketplace-upon-approvals-reoccurence.md | 2 +-
 ...atus-even-in-scenarios-when-the-authentication-has-failed.md | 2 +-
 ...-in-my-orders-when-the-order-has-the-same-shipping-method.md | 2 +-
 ...n-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md | 2 +-
 ...he-wrong-language-when-using-checkout-in-catalan-language.md | 2 +-
 ...d-option-does-not-work-for-asynchronous-payment-providers.md | 2 +-
 ...toriodeimportacaodeestoque-does-not-support-multilanguage.md | 2 +-
 ...timeout-timeout-no-request-para-o-sistema-de-parcelamento.md | 2 +-
 ...nsaction-cancellation-error-with-unreachable-code-message.md | 2 +-
 ...i-shows-gifts-picked-when-using-order-replacement-feature.md | 2 +-
 ...ay-when-transaction-cart-object-in-transaction-is-unknown.md | 2 +-
 .../es/unable-to-create-produtos-relacionados-custom-element.md | 2 +-
 ...nhandled-exception-error-when-changing-edition-of-account.md | 2 +-
 .../url-logo-field-in-the-update-seller-request-not-updating.md | 2 +-
 ...er-administrator-restricted-is-not-able-to-list-the-users.md | 2 +-
 .../version-author-note-not-found-on-vtex-id-on-the-profile.md  | 2 +-
 .../es/visited-product-feature-does-not-work-properly.md        | 2 +-
 .../es/vtexcontentplaceholder-idacessorios-is-not-working.md    | 2 +-
 ...name-is-not-displayed-in-the-order-and-email-notification.md | 2 +-
 ...aping-page-on-admin-the-initial-message-is-not-translated.md | 2 +-
 ...de-as-refundmanually-our-gateway-performs-a-double-refund.md | 2 +-
 docs/known-issues/es/xml-currency-symbol-in-the-installment.md  | 2 +-
 .../es/xmls-product-name-flag-not-working-properly.md           | 2 +-
 ...e-active-and-have-the-activate-if-possible-flag-unchecked.md | 2 +-
 ...ounts-with-on-the-name-dont-have-metrics-on-search-report.md | 2 +-
 .../pt/add-option-not-available-when-creating-dictionary.md     | 2 +-
 ...address-field-comes-with-null-vaule-in-payments-api-query.md | 2 +-
 ...orm-with-excessive-size-for-multiples-cities-separated-by.md | 2 +-
 ...n-the-checkout-when-buyer-has-can-add-shipping-permission.md | 2 +-
 ...dressid-mismatch-causes-invalid-address-for-an-item-error.md | 2 +-
 ...th-attachments-and-assembly-options-components-attachment.md | 2 +-
 .../admin-global-search-doesnt-recognize-profile-menu-items.md  | 2 +-
 .../alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md | 2 +-
 ...azon-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 .../an-error-has-occurred-when-adding-tracking-information.md   | 2 +-
 ...tachents-api-doesnt-allow-null-domainvalues-and-it-should.md | 2 +-
 .../pt/audit-pricing-logs-showing-unknow-information.md         | 2 +-
 ...lete-suggestion-api-removes-the-dot-from-the-product-name.md | 2 +-
 ...-in-fulfillment-simulation-for-no-stock-or-price-products.md | 2 +-
 docs/known-issues/pt/aviseme-report-does-not-open.md            | 2 +-
 .../pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md     | 2 +-
 .../pt/b2w-order-with-parameter-count-mismatch-error.md         | 2 +-
 .../pt/back-button-is-not-rendered-in-my-organization.md        | 2 +-
 ...akes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md | 2 +-
 .../bad-request-when-searching-terms-with-directly-via-url.md   | 2 +-
 ...ad-request-when-searching-terms-with-through-autocomplete.md | 2 +-
 .../pt/bug-in-cart-with-promotion-when-splitting-item.md        | 2 +-
 ...-cancel-inside-the-mycards-page-not-translated-to-spanish.md | 2 +-
 ...-ui-changing-different-from-to-equal-to-with-a-collection.md | 2 +-
 ...rs-email-is-not-being-placed-as-expected-in-the-orderform.md | 2 +-
 ...displays-empty-cart-message-while-screen-is-still-loading.md | 2 +-
 ...-export-does-not-show-sales-channels-when-none-are-tagged.md | 2 +-
 .../catalog-indexing-report-total-section-calculation-error.md  | 2 +-
 .../centauro-orders-with-pedido-sem-o-campo-packages-error.md   | 2 +-
 docs/known-issues/pt/centauro-to-implement-centauro-envios.md   | 2 +-
 ...e-my-account-page-do-not-appear-immediately-in-the-domain.md | 2 +-
 ...ckbox-requires-authentication-doesnt-work-on-pages-module.md | 2 +-
 ...lit-may-generate-incorrect-information-in-the-paymentdata.md | 2 +-
 ...ns-value-0-in-slastax-field-for-shipping-percentage-taxes.md | 2 +-
 ...g-lean-shipping-for-items-with-no-common-shipping-methods.md | 2 +-
 ...selects-the-schedule-all-toggle-after-refreshing-the-page.md | 2 +-
 ...lways-appearing-as-equal-to-on-the-campaign-audience-form.md | 2 +-
 ...vailable-in-catalog-sellers-cms-and-gift-card-modules-for.md | 2 +-
 ...ilablepersaleschannel-in-searches-portal-and-search-again.md | 2 +-
 ...stom-fields-for-custom-data-converts-the-ids-to-lowercase.md | 2 +-
 ...edit-total-due-value-updating-according-to-the-pagination.md | 2 +-
 ...ng-lost-when-it-has-some-order-with-profileerroronloading.md | 2 +-
 ...o-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md | 2 +-
 ...ction-got-reprocessed-after-some-retries-to-authorization.md | 2 +-
 ...rocessing-the-shipping-policy-locked-in-processing-status.md | 2 +-
 ...mtocheckfirstinstallment-configuration-and-splitted-items.md | 2 +-
 ...cation-choose-a-more-specific-global-category-persistente.md | 2 +-
 ...did-when-creating-a-promotion-excluding-more-than-1-brand.md | 2 +-
 ...rder-the-same-item-cannot-have-more-than-one-sla-selected.md | 2 +-
 ...lit-value-in-recipients-is-different-than-operation-value.md | 2 +-
 ...error-in-refund-value-cannot-be-null-parameter-name-value.md | 2 +-
 .../pt/error-integrating-sku-field-may-not-be-null-magalu.md    | 2 +-
 ...pting-to-perform-a-search-using-the-all-field-in-vtex-crm.md | 2 +-
 ...wrong-please-try-again-when-adding-images-via-site-editor.md | 2 +-
 ...with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md | 2 +-
 .../pt/ey-send-kit-is-not-recording-a-change-in-the-card.md     | 2 +-
 ...address-step-causes-the-go-to-payment-button-to-disappear.md | 2 +-
 ...eturns-is-not-updating-on-seller-management-ui-after-save.md | 2 +-
 docs/known-issues/pt/field-reference-always-set-as-null.md      | 2 +-
 ...-by-productclusternames-while-applying-additional-filters.md | 2 +-
 ...n-the-catalog-admin-can-show-the-wrong-ammount-of-results.md | 2 +-
 ...t-search-in-a-store-is-not-considered-on-ui-last-searches.md | 2 +-
 ...t-to-the-cheapest-shipping-option-not-working-as-expected.md | 2 +-
 ...-external-marketplace-integrate-an-order-erro-code-fmt010.md | 2 +-
 ...tions-api-doesnt-keep-same-sku-order-when-changing-limits.md | 2 +-
 .../pt/get-product-by-refid-returning-null-when-not-found.md    | 2 +-
 ...d-hub-is-adding-an-extra-backslash-when-calling-providers.md | 2 +-
 ...ields-caption-and-relationname-when-we-make-a-get-request.md | 2 +-
 ...iftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md | 2 +-
 ...split-when-switching-between-delivery-and-pick-up-options.md | 2 +-
 ...your-store-saving-incorrectly-on-promotion-form-interface.md | 2 +-
 ...ion-page-is-redirecting-to-the-wedding-list-creation-page.md | 2 +-
 ...ts-the-order-of-products-if-import-is-made-based-on-skuid.md | 2 +-
 ...ncorrect-address-format-on-the-my-cards-billing-addresses.md | 2 +-
 ...lit-value-in-recipients-is-different-than-operation-value.md | 2 +-
 ...-doesnt-accept-urls-from-servers-that-require-user-agents.md | 2 +-
 ...ropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md | 2 +-
 ...-address-is-in-available-addresses-with-different-country.md | 2 +-
 ...-characters-in-category-names-cause-page-not-found-errors.md | 2 +-
 ...sible-to-save-some-addresses-from-argentina-in-my-account.md | 2 +-
 ...-possible-to-save-some-addresses-from-chile-in-my-account.md | 2 +-
 ...nd-indexed-text-not-being-changed-by-specification-import.md | 2 +-
 ...-causes-something-went-wrong-after-changing-pickup-points.md | 2 +-
 .../pt/legacy-catalog-ui-delete-button-not-functional.md        | 2 +-
 ...he-product-is-not-available-for-the-websites-trade-policy.md | 2 +-
 ...ategory-on-category-setup-only-works-opening-in-a-new-tab.md | 2 +-
 ...eport-does-not-apply-filter-correctly-in-orders-managment.md | 2 +-
 ...inventory-full-access-permission-did-not-work-as-expected.md | 2 +-
 ...rror-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 ...ine-luiza-integrated-fob-order-with-conventional-delivery.md | 2 +-
 ...rror-object-reference-not-set-to-an-instance-of-an-object.md | 2 +-
 ...ng-selected-as-merchantname-in-the-subaccount-environment.md | 2 +-
 ...tch-multiple-received-skus-api-returning-invalid-sellerid.md | 2 +-
 ...-less-applies-incorrect-discount-when-using-the-same-item.md | 2 +-
 ...o-update-a-document-passing-a-symbol-or-special-character.md | 2 +-
 ...-sku-integration-input-string-was-not-in-a-correct-format.md | 2 +-
 ...ation-is-receiving-errors-from-meli-429-too-many-requests.md | 2 +-
 .../pt/meli-integration-zipcodes-11111-meli-limaperu.md         | 2 +-
 ...bject-reference-not-set-to-an-instance-of-an-object-error.md | 2 +-
 ...ndising-rules-not-working-for-the-facet-productclusterids.md | 2 +-
 .../message-freight-value-has-changed-is-shown-incorrectly.md   | 2 +-
 .../metatagdescription-field-cannot-be-deleted-through-admin.md | 2 +-
 ...koutgraphql-while-sending-options-for-already-added-items.md | 2 +-
 .../pt/my-account-page-does-not-work-on-domain-myvtex-com.md    | 2 +-
 ...vos-does-not-automatically-translate-on-the-product-admin.md | 2 +-
 ...ly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md | 2 +-
 docs/known-issues/pt/orders-with-error-sistema-de-perfis.md     | 2 +-
 .../pt/portal-dont-respect-the-tag-principal-of-skus-image.md   | 2 +-
 ...cy-depends-on-the-page-it-is-shown-on-the-admin-interface.md | 2 +-
 ...ter-applied-on-top-of-spot-price-instead-of-regular-price.md | 2 +-
 .../prices-restricted-to-int32-max-value-on-change-price-api.md | 2 +-
 .../pt/prices-restricted-to-int32-max-value-on-checkout-apis.md | 2 +-
 ...oritization-by-products-keyword-not-considering-stopwords.md | 2 +-
 ...lems-opening-manage-inventory-by-admin-page-with-error-ui.md | 2 +-
 .../problems-with-price-from-in-the-buttonbuymodal-control.md   | 2 +-
 .../product-insertupdate-api-allows-n-in-the-textlink-field.md  | 2 +-
 ...-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md | 2 +-
 ...ion-filter-on-collection-module-assuming-incorrect-values.md | 2 +-
 ...t-with-type-text-does-not-trigger-the-products-indexation.md | 2 +-
 ...n-itemattachment-duplicate-when-the-quantity-is-increased.md | 2 +-
 ...lier-wrongly-flagged-as-with-promotion-for-search-filters.md | 2 +-
 ...cant-be-finished-and-is-stuck-on-freight-type-has-changed.md | 2 +-
 ...shed-and-returns-the-error-receiver-name-field-is-invalid.md | 2 +-
 ...isplayed-according-to-the-searched-zip-codes-availability.md | 2 +-
 .../pt/received-skus-review-tab-missing-products.md             | 2 +-
 ...seller-1-correctly-while-requesting-nonwhitelabel-sellers.md | 2 +-
 ...ers-not-following-the-operator-and-for-trigger-conditions.md | 2 +-
 .../pt/secondlevel-folders-dont-consider-the-search-context.md  | 2 +-
 .../pt/settings-ui-doesnt-update-expiration-period-of-quotes.md | 2 +-
 ...ng-component-locked-in-waiting-for-more-information-state.md | 2 +-
 ...n-dismissed-as-a-matter-of-priority-even-with-better-cost.md | 2 +-
 ...-insert-file-api-is-not-responding-with-the-text-property.md | 2 +-
 ...ng-when-adding-an-incomplete-address-and-tried-to-edit-it.md | 2 +-
 .../special-character-not-mapped-to-be-ignored-in-textlink.md   | 2 +-
 .../pt/status-erro-de-processamento-shipping-policy.md          | 2 +-
 .../pt/stockkeepingunitbyean-returns-404-for-eans-with-.md      | 2 +-
 docs/known-issues/pt/store-texts-search-doesnt-work.md          | 2 +-
 .../pt/storefront-permissions-app-sets-documenttype-as-cpf.md   | 2 +-
 ...mporting-after-uploading-the-skus-association-spreadsheet.md | 2 +-
 ...esales-search-doesnt-accept-special-characters-aside-from.md | 2 +-
 ...nk-created-with-on-marketplace-upon-approvals-reoccurence.md | 2 +-
 ...atus-even-in-scenarios-when-the-authentication-has-failed.md | 2 +-
 ...-in-my-orders-when-the-order-has-the-same-shipping-method.md | 2 +-
 ...d-does-not-change-when-the-updating-is-done-by-webservice.md | 2 +-
 ...n-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md | 2 +-
 ...he-wrong-language-when-using-checkout-in-catalan-language.md | 2 +-
 ...d-option-does-not-work-for-asynchronous-payment-providers.md | 2 +-
 ...toriodeimportacaodeestoque-does-not-support-multilanguage.md | 2 +-
 ...timeout-timeout-no-request-para-o-sistema-de-parcelamento.md | 2 +-
 ...nsaction-cancellation-error-with-unreachable-code-message.md | 2 +-
 ...i-shows-gifts-picked-when-using-order-replacement-feature.md | 2 +-
 ...ay-when-transaction-cart-object-in-transaction-is-unknown.md | 2 +-
 .../pt/unable-to-create-produtos-relacionados-custom-element.md | 2 +-
 ...nhandled-exception-error-when-changing-edition-of-account.md | 2 +-
 .../url-logo-field-in-the-update-seller-request-not-updating.md | 2 +-
 ...er-administrator-restricted-is-not-able-to-list-the-users.md | 2 +-
 .../version-author-note-not-found-on-vtex-id-on-the-profile.md  | 2 +-
 .../pt/visited-product-feature-does-not-work-properly.md        | 2 +-
 .../pt/vtexcontentplaceholder-idacessorios-is-not-working.md    | 2 +-
 ...name-is-not-displayed-in-the-order-and-email-notification.md | 2 +-
 ...aping-page-on-admin-the-initial-message-is-not-translated.md | 2 +-
 ...de-as-refundmanually-our-gateway-performs-a-double-refund.md | 2 +-
 docs/known-issues/pt/xml-currency-symbol-in-the-installment.md  | 2 +-
 .../pt/xmls-product-name-flag-not-working-properly.md           | 2 +-
 docs/tutorials/en/configuring-a-registered-boleto.md            | 2 +-
 docs/tutorials/en/configuring-a-santander-registered-boleto.md  | 2 +-
 docs/tutorials/en/how-do-i-request-a-duplicate-of-my-boleto.md  | 2 +-
 ...ong-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md | 2 +-
 ...-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md | 2 +-
 docs/tutorials/en/inserting-images-into-let-me-know-email.md    | 2 +-
 ...ing-error-message-request-headers-must-only-contain-ascii.md | 2 +-
 ...ing-up-lendico-boleto-in-installments-as-a-payment-method.md | 2 +-
 .../en/why-is-the-order-in-the-verifying-invoice-status.md      | 2 +-
 ...-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md | 2 +-
 docs/tutorials/es/inserting-images-into-let-me-know-email.md    | 2 +-
 ...ing-error-message-request-headers-must-only-contain-ascii.md | 2 +-
 .../es/why-is-the-order-in-the-verifying-invoice-status.md      | 2 +-
 ...-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md | 2 +-
 docs/tutorials/pt/inserting-images-into-let-me-know-email.md    | 2 +-
 ...ing-error-message-request-headers-must-only-contain-ascii.md | 2 +-
 .../pt/why-is-the-order-in-the-verifying-invoice-status.md      | 2 +-
 576 files changed, 576 insertions(+), 576 deletions(-)

diff --git a/docs/announcements/en/New-returned-object-in-API-Get-Order-itemMetadata.md b/docs/announcements/en/New-returned-object-in-API-Get-Order-itemMetadata.md
index 0aab8a58b..ee76309a3 100644
--- a/docs/announcements/en/New-returned-object-in-API-Get-Order-itemMetadata.md
+++ b/docs/announcements/en/New-returned-object-in-API-Get-Order-itemMetadata.md
@@ -1,5 +1,5 @@
 ---
-title: 'New returned object in API Get Order  "itemMetadata"'
+title: "New returned object in API Get Order  'itemMetadata'"
 id: 473vn32oLLH2qyep29rpi
 status: PUBLISHED
 createdAt: 2019-04-08T16:33:34.076Z
diff --git a/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 9689ce484..7c9f4edd6 100644
--- a/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/en/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -1,5 +1,5 @@
 ---
-title: 'Empower your customers with the new "Reviews and Ratings" app'
+title: "Empower your customers with the new 'Reviews and Ratings' app"
 id: 3hIYH0F9hNa1058hGWtb6b
 status: PUBLISHED
 createdAt: 2020-12-07T18:49:04.152Z
diff --git a/docs/announcements/en/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md b/docs/announcements/en/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
index 66656f216..82ec218bd 100644
--- a/docs/announcements/en/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
+++ b/docs/announcements/en/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
@@ -1,5 +1,5 @@
 ---
-title: 'Inventory & Shipping: learn what has changed in the "Inventory management" tab '
+title: "Inventory & Shipping: learn what has changed in the 'Inventory management' tab "
 id: 6AKTFKEdVMyjRdDBv3vGkv
 status: PUBLISHED
 createdAt: 2020-10-29T15:15:14.224Z
diff --git a/docs/announcements/en/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md b/docs/announcements/en/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
index d80ede3ee..96161594c 100644
--- a/docs/announcements/en/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
+++ b/docs/announcements/en/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
@@ -1,5 +1,5 @@
 ---
-title: 'Inventory & shipping: see what has changed in the "Dashboard" tab'
+title: "Inventory & shipping: see what has changed in the 'Dashboard' tab"
 id: 1YNfaeNG206XKI2UbGBRSl
 status: CHANGED
 createdAt: 2020-05-05T18:56:51.879Z
diff --git a/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
index f3d79f5b3..3f966fdb4 100644
--- a/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
@@ -1,5 +1,5 @@
 ---
-title: '"Maximum Price per Item" implementation has changed'
+title: "'Maximum Price per Item' implementation has changed"
 id: 2snrUcdlt2C8QIq2yqaUww
 status: DRAFT
 createdAt: 2017-10-30T19:12:11.257Z
diff --git a/docs/announcements/en/new-object-returned-to-api-get-order-cancelreason.md b/docs/announcements/en/new-object-returned-to-api-get-order-cancelreason.md
index 201627117..baacd98d4 100644
--- a/docs/announcements/en/new-object-returned-to-api-get-order-cancelreason.md
+++ b/docs/announcements/en/new-object-returned-to-api-get-order-cancelreason.md
@@ -1,5 +1,5 @@
 ---
-title: 'New object returned to API Get Order "cancelReason"'
+title: "New object returned to API Get Order 'cancelReason'"
 id: 1NeR0RsaoUPZYW4dsrgS9S
 status: PUBLISHED
 createdAt: 2019-04-10T14:15:51.553Z
diff --git a/docs/announcements/en/new-returned-object-in-api-get-order-cancelreason.md b/docs/announcements/en/new-returned-object-in-api-get-order-cancelreason.md
index 8728d3dac..a8d64ed13 100644
--- a/docs/announcements/en/new-returned-object-in-api-get-order-cancelreason.md
+++ b/docs/announcements/en/new-returned-object-in-api-get-order-cancelreason.md
@@ -1,5 +1,5 @@
 ---
-title: 'New returned object in API Get Order  "cancelReason"'
+title: "New returned object in API Get Order  'cancelReason'"
 id: vqcWN9lw7XuUW64uzaVDU
 status: DRAFT
 createdAt: 2019-04-08T17:11:33.773Z
diff --git a/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md b/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
index 81b57f0f7..57896d52f 100644
--- a/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
+++ b/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
@@ -1,5 +1,5 @@
 ---
-title: '"Recurrences" module will be discontinued: migrate your data until August'
+title: "'Recurrences' module will be discontinued: migrate your data until August"
 id: 6FMxXxKZknbKKULVFII4vQ
 status: PUBLISHED
 createdAt: 2020-06-05T16:09:52.370Z
diff --git a/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md b/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md
index e1dbba9be..e706e466b 100644
--- a/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md
+++ b/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'The "items" field will be removed from the List Orders API'
+title: "The 'items' field will be removed from the List Orders API"
 id: 40UDVKiocUCSi8Uo8eUKui
 status: PUBLISHED
 createdAt: 2018-10-04T20:56:17.252Z
diff --git a/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md b/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
index 2c25c5918..4d1b59571 100644
--- a/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
+++ b/docs/announcements/en/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'The term "Access Profile" has been replaced by the term "Role" in your Admin UI'
+title: "The term 'Access Profile' has been replaced by the term 'Role' in your Admin UI"
 id: jSmEYL6oN5QFLA20a8Aj9
 status: PUBLISHED
 createdAt: 2021-03-23T14:02:18.054Z
diff --git a/docs/announcements/es/New-returned-object-in-API-Get-Order-itemMetadata.md b/docs/announcements/es/New-returned-object-in-API-Get-Order-itemMetadata.md
index 2e4ae5ab9..45c3adcab 100644
--- a/docs/announcements/es/New-returned-object-in-API-Get-Order-itemMetadata.md
+++ b/docs/announcements/es/New-returned-object-in-API-Get-Order-itemMetadata.md
@@ -1,5 +1,5 @@
 ---
-title: 'Nuevo objeto devuelto en API Get Order  "itemMetadata"'
+title: "Nuevo objeto devuelto en API Get Order  'itemMetadata'"
 id: 473vn32oLLH2qyep29rpi
 status: PUBLISHED
 createdAt: 2019-04-08T16:33:34.076Z
diff --git a/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index c232b4bb4..8204856cb 100644
--- a/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/es/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -1,5 +1,5 @@
 ---
-title: 'Empodere a sus consumidores con la nueva app "Reviews and Ratings"'
+title: "Empodere a sus consumidores con la nueva app 'Reviews and Ratings'"
 id: 3hIYH0F9hNa1058hGWtb6b
 status: PUBLISHED
 createdAt: 2020-12-07T18:49:04.152Z
diff --git a/docs/announcements/es/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md b/docs/announcements/es/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
index e363bbe4a..86d190290 100644
--- a/docs/announcements/es/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
+++ b/docs/announcements/es/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
@@ -1,5 +1,5 @@
 ---
-title: 'Inventario y envío: entienda lo que cambió en la pestaña "Gestión del inventario" '
+title: "Inventario y envío: entienda lo que cambió en la pestaña 'Gestión del inventario' "
 id: 6AKTFKEdVMyjRdDBv3vGkv
 status: PUBLISHED
 createdAt: 2020-10-29T15:15:14.224Z
diff --git a/docs/announcements/es/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md b/docs/announcements/es/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
index b3e574232..a3423c5bd 100644
--- a/docs/announcements/es/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
+++ b/docs/announcements/es/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
@@ -1,5 +1,5 @@
 ---
-title: 'Inventario y envío: comprenda lo que cambió en la pestaña "Paneles".'
+title: "Inventario y envío: comprenda lo que cambió en la pestaña 'Paneles'."
 id: 1YNfaeNG206XKI2UbGBRSl
 status: CHANGED
 createdAt: 2020-05-05T18:56:51.879Z
diff --git a/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
index e623e7347..872aed2aa 100644
--- a/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cambiamos la implementación del "Precio Máximo por Artículo"'
+title: "Cambiamos la implementación del 'Precio Máximo por Artículo'"
 id: 2snrUcdlt2C8QIq2yqaUww
 status: DRAFT
 createdAt: 2017-10-30T19:12:11.257Z
diff --git a/docs/announcements/es/new-object-returned-to-api-get-order-cancelreason.md b/docs/announcements/es/new-object-returned-to-api-get-order-cancelreason.md
index 5fb033f26..c6a45d1e2 100644
--- a/docs/announcements/es/new-object-returned-to-api-get-order-cancelreason.md
+++ b/docs/announcements/es/new-object-returned-to-api-get-order-cancelreason.md
@@ -1,5 +1,5 @@
 ---
-title: 'Nuevo objeto devuelto a API Get Order "cancelReason"'
+title: "Nuevo objeto devuelto a API Get Order 'cancelReason'"
 id: 1NeR0RsaoUPZYW4dsrgS9S
 status: PUBLISHED
 createdAt: 2019-04-10T14:15:51.553Z
diff --git a/docs/announcements/es/new-returned-object-in-api-get-order-cancelreason.md b/docs/announcements/es/new-returned-object-in-api-get-order-cancelreason.md
index e7a63d9b4..14dabd144 100644
--- a/docs/announcements/es/new-returned-object-in-api-get-order-cancelreason.md
+++ b/docs/announcements/es/new-returned-object-in-api-get-order-cancelreason.md
@@ -1,5 +1,5 @@
 ---
-title: 'Nuevo objeto devuelto en API Get Order "cancelReason"'
+title: "Nuevo objeto devuelto en API Get Order 'cancelReason'"
 id: vqcWN9lw7XuUW64uzaVDU
 status: DRAFT
 createdAt: 2019-04-08T17:11:33.773Z
diff --git a/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md b/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md
index 16499f649..330bc8eed 100644
--- a/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md
+++ b/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campo "items" se quitará de la API de List Orders'
+title: "Campo 'items' se quitará de la API de List Orders"
 id: 40UDVKiocUCSi8Uo8eUKui
 status: PUBLISHED
 createdAt: 2018-10-04T20:56:17.252Z
diff --git a/docs/announcements/pt/New-returned-object-in-API-Get-Order-itemMetadata.md b/docs/announcements/pt/New-returned-object-in-API-Get-Order-itemMetadata.md
index dbe2162b2..1a11363e4 100644
--- a/docs/announcements/pt/New-returned-object-in-API-Get-Order-itemMetadata.md
+++ b/docs/announcements/pt/New-returned-object-in-API-Get-Order-itemMetadata.md
@@ -1,5 +1,5 @@
 ---
-title: 'Novo objeto retornado na API Get Order  "itemMetadata"'
+title: "Novo objeto retornado na API Get Order  'itemMetadata'"
 id: 473vn32oLLH2qyep29rpi
 status: PUBLISHED
 createdAt: 2019-04-08T16:33:34.076Z
diff --git a/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md b/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
index 01cbafc1f..f0bc35413 100644
--- a/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
+++ b/docs/announcements/pt/empower-your-customers-with-the-new-reviews-and-ratings-app.md
@@ -1,5 +1,5 @@
 ---
-title: 'Empodere seus consumidores com o novo app "Reviews and Ratings"'
+title: "Empodere seus consumidores com o novo app 'Reviews and Ratings'"
 id: 3hIYH0F9hNa1058hGWtb6b
 status: PUBLISHED
 createdAt: 2020-12-07T18:49:04.152Z
diff --git a/docs/announcements/pt/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md b/docs/announcements/pt/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
index 7c396ebdf..470b8e624 100644
--- a/docs/announcements/pt/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
+++ b/docs/announcements/pt/inventory-and-shipping-learn-what-has-changed-in-the-inventory-management.md
@@ -1,5 +1,5 @@
 ---
-title: 'Estoque & entrega: entenda o que mudou na aba "Gerenciar Inventário" '
+title: "Estoque & entrega: entenda o que mudou na aba 'Gerenciar Inventário' "
 id: 6AKTFKEdVMyjRdDBv3vGkv
 status: PUBLISHED
 createdAt: 2020-10-29T15:15:14.224Z
diff --git a/docs/announcements/pt/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md b/docs/announcements/pt/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
index 0eeeff24a..464df0e70 100644
--- a/docs/announcements/pt/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
+++ b/docs/announcements/pt/inventory-and-shipping-see-what-has-changed-in-the-dashboard-tab.md
@@ -1,5 +1,5 @@
 ---
-title: 'Estoque & entrega: entenda o que mudou na aba "Painéis"'
+title: "Estoque & entrega: entenda o que mudou na aba 'Painéis'"
 id: 1YNfaeNG206XKI2UbGBRSl
 status: CHANGED
 createdAt: 2020-05-05T18:56:51.879Z
diff --git a/docs/announcements/pt/new-object-returned-to-api-get-order-cancelreason.md b/docs/announcements/pt/new-object-returned-to-api-get-order-cancelreason.md
index 00fc350ba..79cff80bb 100644
--- a/docs/announcements/pt/new-object-returned-to-api-get-order-cancelreason.md
+++ b/docs/announcements/pt/new-object-returned-to-api-get-order-cancelreason.md
@@ -1,5 +1,5 @@
 ---
-title: 'Novo objeto retornado na API Get Order "cancelReason"'
+title: "Novo objeto retornado na API Get Order 'cancelReason'"
 id: 1NeR0RsaoUPZYW4dsrgS9S
 status: PUBLISHED
 createdAt: 2019-04-10T14:15:51.553Z
diff --git a/docs/announcements/pt/new-returned-object-in-api-get-order-cancelreason.md b/docs/announcements/pt/new-returned-object-in-api-get-order-cancelreason.md
index 3f35bb7c6..9851d780f 100644
--- a/docs/announcements/pt/new-returned-object-in-api-get-order-cancelreason.md
+++ b/docs/announcements/pt/new-returned-object-in-api-get-order-cancelreason.md
@@ -1,5 +1,5 @@
 ---
-title: 'Novo objeto retornado na API Get Order "cancelReason"'
+title: "Novo objeto retornado na API Get Order 'cancelReason'"
 id: vqcWN9lw7XuUW64uzaVDU
 status: DRAFT
 createdAt: 2019-04-08T17:11:33.773Z
diff --git a/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md b/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
index 18fa93556..c35e3a9ae 100644
--- a/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
+++ b/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
@@ -1,5 +1,5 @@
 ---
-title: 'Módulo "Recorrência" será descontinuado: migre seus dados até agosto'
+title: "Módulo 'Recorrência' será descontinuado: migre seus dados até agosto"
 id: 6FMxXxKZknbKKULVFII4vQ
 status: PUBLISHED
 createdAt: 2020-06-05T16:09:52.370Z
diff --git a/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md b/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md
index 5c35894fa..5a39d41c8 100644
--- a/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md
+++ b/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campo "items" será removido da API de List Orders'
+title: "Campo 'items' será removido da API de List Orders"
 id: 40UDVKiocUCSi8Uo8eUKui
 status: PUBLISHED
 createdAt: 2018-10-04T20:56:17.252Z
diff --git a/docs/faq/en/checkout-with-store-not-found-error.md b/docs/faq/en/checkout-with-store-not-found-error.md
index f26429cc7..ec282f687 100644
--- a/docs/faq/en/checkout-with-store-not-found-error.md
+++ b/docs/faq/en/checkout-with-store-not-found-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout with "store not found" error. What to do?'
+title: "Checkout with 'store not found' error. What to do?"
 id: 23ZZv5zvfuAsSWCwOMIoQE
 status: PUBLISHED
 createdAt: 2017-11-29T14:00:08.262Z
diff --git a/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md b/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
index 84884d61b..a640886f3 100644
--- a/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
@@ -1,5 +1,5 @@
 ---
-title: '"Invalid header signature" error when trying to import freight spreadsheet'
+title: "'Invalid header signature' error when trying to import freight spreadsheet"
 id: qruKcwf7zwwOcGWA6mkgK
 status: PUBLISHED
 createdAt: 2018-10-02T16:01:21.654Z
diff --git a/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md b/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
index fa87a54f4..64bb90ed8 100644
--- a/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
+++ b/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "object reference not set to an instance of an object" when uploading a freight spreadsheet'
+title: "Error 'object reference not set to an instance of an object' when uploading a freight spreadsheet"
 id: 51E8sNlQu40w0QWWg6mqGE
 status: PUBLISHED
 createdAt: 2018-10-01T16:23:51.945Z
diff --git a/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md b/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
index 9f285cb38..966fed50f 100644
--- a/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
+++ b/docs/faq/en/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'I received the message error "the limit of activated calculators has been reached". What to do?'
+title: "I received the message error 'the limit of activated calculators has been reached'. What to do?"
 id: frequentlyAskedQuestions_349
 status: PUBLISHED
 createdAt: 2017-04-27T22:37:28.949Z
diff --git a/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
index c4f16f1d8..dc360a4be 100644
--- a/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Order is locked in "Ready for Handling". What do I do?'
+title: "Order is locked in 'Ready for Handling'. What do I do?"
 id: frequentlyAskedQuestions_771
 status: PUBLISHED
 createdAt: 2017-04-27T22:27:37.057Z
diff --git a/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
index defdddbda..0ae2997f3 100644
--- a/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
+++ b/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Order is locked in "Ready for Handling", what should I do?'
+title: "Order is locked in 'Ready for Handling', what should I do?"
 id: frequentlyAskedQuestions_771
 status: PUBLISHED
 createdAt: 2017-04-27T22:27:37.057Z
diff --git a/docs/faq/en/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md b/docs/faq/en/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
index e70589d4d..28c2229ce 100644
--- a/docs/faq/en/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
+++ b/docs/faq/en/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'The order was billed in the ERP but remains in the "Preparing Delivery" status. What to do?'
+title: "The order was billed in the ERP but remains in the 'Preparing Delivery' status. What to do?"
 id: 4szpXviNMAkwOe2cCiMiMe
 status: PUBLISHED
 createdAt: 2017-12-19T13:00:23.800Z
diff --git a/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
index 78694cc04..399c1c6a7 100644
--- a/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/en/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -1,5 +1,5 @@
 ---
-title: 'What to do when the "Notify me" option is not displayed'
+title: "What to do when the 'Notify me' option is not displayed"
 id: oNb6JK1LPMOQwYsecKKCs
 status: PUBLISHED
 createdAt: 2019-01-24T20:30:45.175Z
diff --git a/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md b/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
index 025b18db2..d95078431 100644
--- a/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
+++ b/docs/faq/en/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'When trying to approve payment, Orders Managment returns "authorize-fulfillment" error. What to do?'
+title: "When trying to approve payment, Orders Managment returns 'authorize-fulfillment' error. What to do?"
 id: 1cbaJI69pSMWkugoUkmQ8O
 status: PUBLISHED
 createdAt: 2017-12-21T14:02:07.873Z
diff --git a/docs/faq/en/why-does-the-message-the-timespan-could-not-be-parsed-appear.md b/docs/faq/en/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
index 47aff11c3..26c586f86 100644
--- a/docs/faq/en/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
+++ b/docs/faq/en/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
@@ -1,5 +1,5 @@
 ---
-title: 'Why does the message "The TimeSpan could not be parsed... " appear when importing the shipping worksheet?'
+title: "Why does the message 'The TimeSpan could not be parsed... ' appear when importing the shipping worksheet?"
 id: frequentlyAskedQuestions_6691
 status: PUBLISHED
 createdAt: 2017-04-27T22:22:14.460Z
diff --git a/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
index 7010bfc30..a84adf179 100644
--- a/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/en/why-is-the-thumb-image-of-poor-quality.md
@@ -1,5 +1,5 @@
 ---
-title: 'Why is the "thumb" image of poor quality?'
+title: "Why is the 'thumb' image of poor quality?"
 id: 4T5kL7MK5a8Y4AC8SO0yKG
 status: PUBLISHED
 createdAt: 2017-05-09T14:00:47.862Z
diff --git a/docs/faq/es/checkout-with-store-not-found-error.md b/docs/faq/es/checkout-with-store-not-found-error.md
index 753a98365..0d960c853 100644
--- a/docs/faq/es/checkout-with-store-not-found-error.md
+++ b/docs/faq/es/checkout-with-store-not-found-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout con error "tienda no encontrada". ¿Que hacer?'
+title: "Checkout con error 'tienda no encontrada'. ¿Que hacer?"
 id: 23ZZv5zvfuAsSWCwOMIoQE
 status: PUBLISHED
 createdAt: 2017-11-29T14:00:08.262Z
diff --git a/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md b/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
index 786863b9d..68b358468 100644
--- a/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "invalid header signature" al intentar importar la plantilla de flete'
+title: "Error 'invalid header signature' al intentar importar la plantilla de flete"
 id: qruKcwf7zwwOcGWA6mkgK
 status: PUBLISHED
 createdAt: 2018-10-02T16:01:21.654Z
diff --git a/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md b/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
index a0d975e07..ed7720c21 100644
--- a/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
+++ b/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "object reference not set to an instance of an object" al intentar hacer el upload de una plantilla de flete'
+title: "Error 'object reference not set to an instance of an object' al intentar hacer el upload de una plantilla de flete"
 id: 51E8sNlQu40w0QWWg6mqGE
 status: PUBLISHED
 createdAt: 2018-10-01T16:23:51.945Z
diff --git a/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md b/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
index e2e849f29..5093e0e66 100644
--- a/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
+++ b/docs/faq/es/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'He recibido el mensaje de error "the limit of activated calculators has been reached". Que hacer?'
+title: "He recibido el mensaje de error 'the limit of activated calculators has been reached'. Que hacer?"
 id: frequentlyAskedQuestions_349
 status: PUBLISHED
 createdAt: 2017-04-27T22:37:28.949Z
diff --git a/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
index d0126a99e..e78a28e22 100644
--- a/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedido está trabado en "Listo para manuseo". ¿Qué se hace?'
+title: "Pedido está trabado en 'Listo para manuseo'. ¿Qué se hace?"
 id: frequentlyAskedQuestions_771
 status: PUBLISHED
 createdAt: 2017-04-27T22:27:37.057Z
diff --git a/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
index a8bdbe222..8409c3dc7 100644
--- a/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
+++ b/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedido está trabado en "Listo para preparación", ¿qué se hace?'
+title: "Pedido está trabado en 'Listo para preparación', ¿qué se hace?"
 id: frequentlyAskedQuestions_771
 status: PUBLISHED
 createdAt: 2017-04-27T22:27:37.057Z
diff --git a/docs/faq/es/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md b/docs/faq/es/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
index 703e35f19..aff8d6713 100644
--- a/docs/faq/es/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
+++ b/docs/faq/es/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'El pedido fue facturado en el ERP pero continúa en el status "Preparando Entrega". ¿Que hacer?'
+title: "El pedido fue facturado en el ERP pero continúa en el status 'Preparando Entrega'. ¿Que hacer?"
 id: 4szpXviNMAkwOe2cCiMiMe
 status: PUBLISHED
 createdAt: 2017-12-19T13:00:23.800Z
diff --git a/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md b/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
index d5754b2af..129fc4ad0 100644
--- a/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
+++ b/docs/faq/es/when-trying-to-approve-payment-orders-managment-returns-authorize-fulfillment-error-what-to-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Al intentar aprobar el pago, Gestión de Pedidos devuelve el error de "authorize-fulfillment". ¿Que hacer?'
+title: "Al intentar aprobar el pago, Gestión de Pedidos devuelve el error de 'authorize-fulfillment'. ¿Que hacer?"
 id: 1cbaJI69pSMWkugoUkmQ8O
 status: PUBLISHED
 createdAt: 2017-12-21T14:02:07.873Z
diff --git a/docs/faq/es/why-does-the-message-the-timespan-could-not-be-parsed-appear.md b/docs/faq/es/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
index 99caa0eb3..aa42b25cf 100644
--- a/docs/faq/es/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
+++ b/docs/faq/es/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
@@ -1,5 +1,5 @@
 ---
-title: '¿Por qué aparece el mensaje "The TimeSpan could not be parsed..." al importar planilla de flete?'
+title: "¿Por qué aparece el mensaje 'The TimeSpan could not be parsed...' al importar planilla de flete?"
 id: frequentlyAskedQuestions_6691
 status: PUBLISHED
 createdAt: 2017-04-27T22:22:14.460Z
diff --git a/docs/faq/es/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md b/docs/faq/es/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md
index d84b47ffb..f49622a89 100644
--- a/docs/faq/es/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md
+++ b/docs/faq/es/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md
@@ -1,5 +1,5 @@
 ---
-title: '¿Por qué el pedido no cambia para el estado "Enviado" en el marketplace?'
+title: "¿Por qué el pedido no cambia para el estado 'Enviado' en el marketplace?"
 id: frequentlyAskedQuestions_719
 status: PUBLISHED
 createdAt: 2017-04-27T22:28:07.933Z
diff --git a/docs/faq/es/why-has-my-order-stopped-on-ready-for-handling.md b/docs/faq/es/why-has-my-order-stopped-on-ready-for-handling.md
index 79b50ebe2..c2a36dc76 100644
--- a/docs/faq/es/why-has-my-order-stopped-on-ready-for-handling.md
+++ b/docs/faq/es/why-has-my-order-stopped-on-ready-for-handling.md
@@ -1,5 +1,5 @@
 ---
-title: '¿Por qué está mi pedido parado en  "Listo para preparar"?'
+title: "¿Por qué está mi pedido parado en  'Listo para preparar'?"
 id: frequentlyAskedQuestions_301
 status: PUBLISHED
 createdAt: 2017-04-27T22:38:27.319Z
diff --git a/docs/faq/es/why-is-let-me-know-not-showing.md b/docs/faq/es/why-is-let-me-know-not-showing.md
index c217f112e..4f0f9a540 100644
--- a/docs/faq/es/why-is-let-me-know-not-showing.md
+++ b/docs/faq/es/why-is-let-me-know-not-showing.md
@@ -1,5 +1,5 @@
 ---
-title: '¿Por qué no aparece el "Avíseme"?'
+title: "¿Por qué no aparece el 'Avíseme'?"
 id: frequentlyAskedQuestions_628
 status: PUBLISHED
 createdAt: 2017-04-27T22:31:23.053Z
diff --git a/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
index 2617eca32..ac1ebbf0c 100644
--- a/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/es/why-is-the-thumb-image-of-poor-quality.md
@@ -1,5 +1,5 @@
 ---
-title: '¿Por qué la imagen "thumb" está en baja calidad?'
+title: "¿Por qué la imagen 'thumb' está en baja calidad?"
 id: 4T5kL7MK5a8Y4AC8SO0yKG
 status: PUBLISHED
 createdAt: 2017-05-09T14:00:47.862Z
diff --git a/docs/faq/pt/checkout-with-store-not-found-error.md b/docs/faq/pt/checkout-with-store-not-found-error.md
index f5cd0d614..6b62de50a 100644
--- a/docs/faq/pt/checkout-with-store-not-found-error.md
+++ b/docs/faq/pt/checkout-with-store-not-found-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout com erro "loja não encontrada". O que fazer?'
+title: "Checkout com erro 'loja não encontrada'. O que fazer?"
 id: 23ZZv5zvfuAsSWCwOMIoQE
 status: PUBLISHED
 createdAt: 2017-11-29T14:00:08.262Z
diff --git a/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md b/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
index 56dfd3b07..42e3593ce 100644
--- a/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "invalid header signature" ao tentar importar planilha de frete'
+title: "Erro 'invalid header signature' ao tentar importar planilha de frete"
 id: qruKcwf7zwwOcGWA6mkgK
 status: PUBLISHED
 createdAt: 2018-10-02T16:01:21.654Z
diff --git a/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md b/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
index a757145b6..6c2f9d34e 100644
--- a/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
+++ b/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "object reference not set to an instance of an object" ao tentar importar planilha de frete'
+title: "Erro 'object reference not set to an instance of an object' ao tentar importar planilha de frete"
 id: 51E8sNlQu40w0QWWg6mqGE
 status: PUBLISHED
 createdAt: 2018-10-01T16:23:51.945Z
diff --git a/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md b/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
index 99e77f915..52308f3a8 100644
--- a/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
+++ b/docs/faq/pt/i-received-the-message-error-the-limit-of-activated-calculators-has-been-reached-what-to-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Recebi a mensagem de erro "the limit of activated calculators has been reached". O que fazer?'
+title: "Recebi a mensagem de erro 'the limit of activated calculators has been reached'. O que fazer?"
 id: frequentlyAskedQuestions_349
 status: PUBLISHED
 createdAt: 2017-04-27T22:37:28.949Z
diff --git a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
index b24075ebc..06d566d44 100644
--- a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedido está travado em "Pronto para manuseio". O que fazer?'
+title: "Pedido está travado em 'Pronto para manuseio'. O que fazer?"
 id: frequentlyAskedQuestions_771
 status: PUBLISHED
 createdAt: 2017-04-27T22:27:37.057Z
diff --git a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
index 24b1f392e..5c4991c8a 100644
--- a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
+++ b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedido está travado em "Pronto para manuseio", o que fazer?'
+title: "Pedido está travado em 'Pronto para manuseio', o que fazer?"
 id: frequentlyAskedQuestions_771
 status: PUBLISHED
 createdAt: 2017-04-27T22:27:37.057Z
diff --git a/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md b/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md
index 64b8d3c9b..d9fd0ec58 100644
--- a/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md
+++ b/docs/faq/pt/porque-a-exportacao-de-pedidos-no-oms-fica-com-quebra-de-linha-no-excel.md
@@ -1,5 +1,5 @@
 ---
-title: 'Porque a exportação de pedidos no OMS, fica com "quebra de linha" no excel?'
+title: "Porque a exportação de pedidos no OMS, fica com 'quebra de linha' no excel?"
 id: 2TW35qM4RGAmyMeYsK2GiW
 status: DRAFT
 createdAt: 2017-07-03T21:52:22.770Z
diff --git a/docs/faq/pt/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md b/docs/faq/pt/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
index 6a4f73b5d..3c0742e91 100644
--- a/docs/faq/pt/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
+++ b/docs/faq/pt/the-order-was-billed-in-the-erp-but-remains-in-the-preparing-delivery-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'O pedido foi faturado no ERP mas continua no status "Preparando Entrega". O que fazer?'
+title: "O pedido foi faturado no ERP mas continua no status 'Preparando Entrega'. O que fazer?"
 id: 4szpXviNMAkwOe2cCiMiMe
 status: PUBLISHED
 createdAt: 2017-12-19T13:00:23.800Z
diff --git a/docs/faq/pt/untitled-entry-2017-05-24-at-20-19-07.md b/docs/faq/pt/untitled-entry-2017-05-24-at-20-19-07.md
index cf2b9d899..393520596 100644
--- a/docs/faq/pt/untitled-entry-2017-05-24-at-20-19-07.md
+++ b/docs/faq/pt/untitled-entry-2017-05-24-at-20-19-07.md
@@ -1,5 +1,5 @@
 ---
-title: 'O status "Aguardando autorização para despachar" significa o que?'
+title: "O status 'Aguardando autorização para despachar' significa o que?"
 id: 5kM2u7aOGWsOoAIgSqE6qm
 status: DRAFT
 createdAt: 2017-05-24T20:19:07.147Z
diff --git a/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md b/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
index 622936471..a0a33405b 100644
--- a/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
+++ b/docs/faq/pt/what-to-do-when-the-notify-me-option-is-not-displayed.md
@@ -1,5 +1,5 @@
 ---
-title: 'O que fazer quando o "Avise-me" não está sendo exibido'
+title: "O que fazer quando o 'Avise-me' não está sendo exibido"
 id: oNb6JK1LPMOQwYsecKKCs
 status: PUBLISHED
 createdAt: 2019-01-24T20:30:45.175Z
diff --git a/docs/faq/pt/why-does-the-message-the-timespan-could-not-be-parsed-appear.md b/docs/faq/pt/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
index d15a16f60..8201fe832 100644
--- a/docs/faq/pt/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
+++ b/docs/faq/pt/why-does-the-message-the-timespan-could-not-be-parsed-appear.md
@@ -1,5 +1,5 @@
 ---
-title: 'Por que aparece a mensagem "The TimeSpan could not be parsed... " ao importar planilha de frete?'
+title: "Por que aparece a mensagem 'The TimeSpan could not be parsed... ' ao importar planilha de frete?"
 id: frequentlyAskedQuestions_6691
 status: PUBLISHED
 createdAt: 2017-04-27T22:22:14.460Z
diff --git a/docs/faq/pt/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md b/docs/faq/pt/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md
index a6bdccea0..1eab31cda 100644
--- a/docs/faq/pt/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md
+++ b/docs/faq/pt/why-doesnt-the-order-go-to-the-sent-status-on-the-marketplace.md
@@ -1,5 +1,5 @@
 ---
-title: 'Por que o pedido não vai para o status "Enviado" no marketplace?'
+title: "Por que o pedido não vai para o status 'Enviado' no marketplace?"
 id: frequentlyAskedQuestions_719
 status: PUBLISHED
 createdAt: 2017-04-27T22:28:07.933Z
diff --git a/docs/faq/pt/why-has-my-order-stopped-on-ready-for-handling.md b/docs/faq/pt/why-has-my-order-stopped-on-ready-for-handling.md
index 12116226e..b224f03e3 100644
--- a/docs/faq/pt/why-has-my-order-stopped-on-ready-for-handling.md
+++ b/docs/faq/pt/why-has-my-order-stopped-on-ready-for-handling.md
@@ -1,5 +1,5 @@
 ---
-title: 'Por que meu pedido está parado em "Preparando entrega"?'
+title: "Por que meu pedido está parado em 'Preparando entrega'?"
 id: frequentlyAskedQuestions_301
 status: PUBLISHED
 createdAt: 2017-04-27T22:38:27.319Z
diff --git a/docs/faq/pt/why-is-let-me-know-not-showing.md b/docs/faq/pt/why-is-let-me-know-not-showing.md
index 94941a6fe..a8afd4658 100644
--- a/docs/faq/pt/why-is-let-me-know-not-showing.md
+++ b/docs/faq/pt/why-is-let-me-know-not-showing.md
@@ -1,5 +1,5 @@
 ---
-title: 'Por que não aparece o "Avise-me"?'
+title: "Por que não aparece o 'Avise-me'?"
 id: frequentlyAskedQuestions_628
 status: PUBLISHED
 createdAt: 2017-04-27T22:31:23.053Z
diff --git a/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md b/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
index 19868a985..ea0f999c5 100644
--- a/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
+++ b/docs/faq/pt/why-is-the-thumb-image-of-poor-quality.md
@@ -1,5 +1,5 @@
 ---
-title: 'Por que a imagem "thumb" está em baixa qualidade?'
+title: "Por que a imagem 'thumb' está em baixa qualidade?"
 id: 4T5kL7MK5a8Y4AC8SO0yKG
 status: PUBLISHED
 createdAt: 2017-05-09T14:00:47.862Z
diff --git a/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
index 79fd27b81..8e05c1032 100644
--- a/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
+++ b/docs/known-issues/en/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -1,5 +1,5 @@
 ---
-title: 'A SKU can be active and have the "activate if possible" flag unchecked'
+title: "A SKU can be active and have the 'activate if possible' flag unchecked"
 id: 5uXQ65flkoEbYeLkNSw4ig
 status: PUBLISHED
 createdAt: 2023-11-07T11:01:20.612Z
diff --git a/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md b/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
index b8e07ded3..ba51272e7 100644
--- a/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
+++ b/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
@@ -1,5 +1,5 @@
 ---
-title: "Accounts with "-" on the name don't have metrics on search report"
+title: "Accounts with "-' on the name don't have metrics on search report"
 id: 71rVz43g0rgIN7Joe4GEj6
 status: PUBLISHED
 createdAt: 2023-04-19T17:35:28.560Z
diff --git a/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
index 6f37ddca1..5ecb52553 100644
--- a/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/en/add-option-not-available-when-creating-dictionary.md
@@ -1,5 +1,5 @@
 ---
-title: '"Add" option not available when creating dictionary'
+title: "'Add' option not available when creating dictionary"
 id: 6kSvXDetqLw954q5hYIRQN
 status: PUBLISHED
 createdAt: 2019-12-26T14:48:14.548Z
diff --git a/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md b/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md
index 8c461f476..13facb65c 100644
--- a/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md
+++ b/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md
@@ -1,5 +1,5 @@
 ---
-title: ""Address" field comes with "null" vaule in Payment's API query"
+title: ""Address" field comes with "null' vaule in Payment's API query"
 id: 7oEEc24umACsOoy4Ceso2W
 status: PUBLISHED
 createdAt: 2018-01-11T16:33:01.231Z
diff --git a/docs/known-issues/en/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md b/docs/known-issues/en/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
index f9092c1c1..99af3ea54 100644
--- a/docs/known-issues/en/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
+++ b/docs/known-issues/en/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
@@ -1,5 +1,5 @@
 ---
-title: 'Address in orderForm with excessive size for multiples cities separated by "::"'
+title: "Address in orderForm with excessive size for multiples cities separated by '::'"
 id: 7E6x4O56SxcSeU2qv09GBt
 status: PUBLISHED
 createdAt: 2023-01-06T11:52:36.229Z
diff --git a/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
index a054ba53a..50c6f6b28 100644
--- a/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
+++ b/docs/known-issues/en/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -1,5 +1,5 @@
 ---
-title: 'Addresses are shown in the Checkout when buyer has "Can add shipping" permission'
+title: "Addresses are shown in the Checkout when buyer has 'Can add shipping' permission"
 id: 2ssiTryGJ6kGoZWxWkGnFF
 status: PUBLISHED
 createdAt: 2024-05-21T22:03:55.172Z
diff --git a/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md
index 72af9f4e1..6b2c059b7 100644
--- a/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md
+++ b/docs/known-issues/en/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'AddressId mismatch causes "invalid address for an item" error'
+title: "AddressId mismatch causes 'invalid address for an item' error"
 id: 5bSac85eHb9NmrOhcTjHNw
 status: PUBLISHED
 createdAt: 2024-03-01T19:28:52.074Z
diff --git a/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index a2cb2e61c..4ed70d4d0 100644
--- a/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/en/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -1,5 +1,5 @@
 ---
-title: 'Admin homepage has an error in "How to improve" section of the Catalog'
+title: "Admin homepage has an error in 'How to improve' section of the Catalog"
 id: 4f8oPMiiCvBMtjFUoOVIGv
 status: CHANGED
 createdAt: 2021-09-29T14:02:37.809Z
diff --git a/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index a1567c30a..4463197bb 100644
--- a/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/en/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -1,5 +1,5 @@
 ---
-title: 'ALT attribute not showing in <vtex.cmc:ProductImage zoom="on" />'
+title: "ALT attribute not showing in <vtex.cmc:ProductImage zoom='on' />"
 id: 4P1Eys9Q2WFddrMLQVDvM9
 status: DRAFT
 createdAt: 2022-02-17T13:08:53.295Z
diff --git a/docs/known-issues/en/amazon-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/en/amazon-object-reference-not-set-to-an-instance-of-an-object.md
index 3f79d5633..2ea7c8c4d 100644
--- a/docs/known-issues/en/amazon-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/en/amazon-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: '[AMAZON] "Object reference not set to an instance of an object"'
+title: "[AMAZON] 'Object reference not set to an instance of an object'"
 id: 7xWXzfztp7b9I8KeBSzgST
 status: PUBLISHED
 createdAt: 2022-03-10T18:00:38.681Z
diff --git a/docs/known-issues/en/an-error-has-occurred-when-adding-tracking-information.md b/docs/known-issues/en/an-error-has-occurred-when-adding-tracking-information.md
index 9c9ffc478..2f2eba71c 100644
--- a/docs/known-issues/en/an-error-has-occurred-when-adding-tracking-information.md
+++ b/docs/known-issues/en/an-error-has-occurred-when-adding-tracking-information.md
@@ -1,5 +1,5 @@
 ---
-title: '"An error has occurred" when adding tracking information'
+title: "'An error has occurred' when adding tracking information"
 id: 1gmlrPh9P1KbNI5NNXuImO
 status: PUBLISHED
 createdAt: 2023-02-08T18:38:55.699Z
diff --git a/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
index 966bd6706..493c49c32 100644
--- a/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
+++ b/docs/known-issues/en/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -1,5 +1,5 @@
 ---
-title: "Attachents API doesn't allow null "domainValues" (and it should)"
+title: "Attachents API doesn't allow null 'domainValues' (and it should)"
 id: 7KMb6nh0ulcWdEfz7USbPg
 status: PUBLISHED
 createdAt: 2023-09-11T19:02:51.514Z
diff --git a/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md
index 83cd33bc3..52e6475fe 100644
--- a/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md
+++ b/docs/known-issues/en/audit-pricing-logs-showing-unknow-information.md
@@ -1,5 +1,5 @@
 ---
-title: 'Audit pricing logs showing "unknow" information'
+title: "Audit pricing logs showing 'unknow' information"
 id: 7b8UDsiBo7VOHCN3pgcfd0
 status: PUBLISHED
 createdAt: 2023-07-05T18:51:22.120Z
diff --git a/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
index 99a7640d1..2a7c375fb 100644
--- a/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
+++ b/docs/known-issues/en/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -1,5 +1,5 @@
 ---
-title: 'Autocomplete Suggestion API removes the dot "." from the product name'
+title: "Autocomplete Suggestion API removes the dot '.' from the product name"
 id: 55185IvERIwGQ3kH6H510O
 status: PUBLISHED
 createdAt: 2024-04-10T13:58:51.138Z
diff --git a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index d8a71f481..5a080e11e 100644
--- a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -1,5 +1,5 @@
 ---
-title: "Automatic field doesn't calculate the field correctly when set to "Calculate during the first hour of the day""
+title: "Automatic field doesn't calculate the field correctly when set to "Calculate during the first hour of the day'"
 id: 6DieNCI6paEUeg06cKsCYI
 status: PUBLISHED
 createdAt: 2018-12-17T18:37:45.246Z
diff --git a/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
index ec830756b..3beb814ec 100644
--- a/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
+++ b/docs/known-issues/en/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -1,5 +1,5 @@
 ---
-title: '"availability" field is incorrect in Fulfillment Simulation for no stock or price products'
+title: "'availability' field is incorrect in Fulfillment Simulation for no stock or price products"
 id: 1k2zcLEN5vG6mnksLwEXxp
 status: PUBLISHED
 createdAt: 2023-10-04T14:22:53.519Z
diff --git a/docs/known-issues/en/aviseme-report-does-not-open.md b/docs/known-issues/en/aviseme-report-does-not-open.md
index e4f9bd62d..db18b5b6a 100644
--- a/docs/known-issues/en/aviseme-report-does-not-open.md
+++ b/docs/known-issues/en/aviseme-report-does-not-open.md
@@ -1,5 +1,5 @@
 ---
-title: '"Avise-me" report does not open'
+title: "'Avise-me' report does not open"
 id: 5jRrYk5Nm0uGSmoyeogIs2
 status: PUBLISHED
 createdAt: 2017-06-13T15:07:33.222Z
diff --git a/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 1f0b70450..e36f07435 100644
--- a/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/en/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -1,5 +1,5 @@
 ---
-title: '[B2W] "B2W direct" order (FOB) integrating with carrier'
+title: "[B2W] 'B2W direct' order (FOB) integrating with carrier"
 id: 20nA7vm1RFMhv7yhaJ43GG
 status: PUBLISHED
 createdAt: 2022-12-12T18:14:19.975Z
diff --git a/docs/known-issues/en/b2w-order-with-parameter-count-mismatch-error.md b/docs/known-issues/en/b2w-order-with-parameter-count-mismatch-error.md
index 4dd60a12f..7d497dfbe 100644
--- a/docs/known-issues/en/b2w-order-with-parameter-count-mismatch-error.md
+++ b/docs/known-issues/en/b2w-order-with-parameter-count-mismatch-error.md
@@ -1,5 +1,5 @@
 ---
-title: '[B2W] Order with "Parameter count mismatch" error'
+title: "[B2W] Order with 'Parameter count mismatch' error"
 id: 6XhzSJrrHaEt85QseRdC3k
 status: PUBLISHED
 createdAt: 2023-03-22T19:32:10.011Z
diff --git a/docs/known-issues/en/back-button-is-not-rendered-in-my-organization.md b/docs/known-issues/en/back-button-is-not-rendered-in-my-organization.md
index 2ca0fcc72..14a540629 100644
--- a/docs/known-issues/en/back-button-is-not-rendered-in-my-organization.md
+++ b/docs/known-issues/en/back-button-is-not-rendered-in-my-organization.md
@@ -1,5 +1,5 @@
 ---
-title: '"Back" button is not rendered in My Organization'
+title: "'Back' button is not rendered in My Organization"
 id: xzd2JVKP6jcTN0dGWwISB
 status: PUBLISHED
 createdAt: 2023-04-25T21:26:35.401Z
diff --git a/docs/known-issues/en/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md b/docs/known-issues/en/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
index 3684b46ca..073a985b9 100644
--- a/docs/known-issues/en/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
+++ b/docs/known-issues/en/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
@@ -1,5 +1,5 @@
 ---
-title: '"Back to site" button takes to gatewayCallback//Success instead of placeOrder page'
+title: "'Back to site' button takes to gatewayCallback//Success instead of placeOrder page"
 id: 7Hp6yYCblhbhrN3jHHigUC
 status: PUBLISHED
 createdAt: 2023-04-10T15:18:58.986Z
diff --git a/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md
index d56d8c179..cb8d5b25b 100644
--- a/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/en/bad-request-when-searching-terms-with-directly-via-url.md
@@ -1,5 +1,5 @@
 ---
-title: 'Bad Request when searching terms with "%" directly via URL'
+title: "Bad Request when searching terms with '%' directly via URL"
 id: 3gdZ8egQRa4zcNRe2f5CbT
 status: PUBLISHED
 createdAt: 2023-03-21T22:51:46.273Z
diff --git a/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md
index 18400ec50..e5cce8bb6 100644
--- a/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md
+++ b/docs/known-issues/en/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -1,5 +1,5 @@
 ---
-title: 'Bad Request when searching terms with "#" through autocomplete'
+title: "Bad Request when searching terms with '#' through autocomplete"
 id: 18pMsxubB9eSPGlULAN35p
 status: PUBLISHED
 createdAt: 2024-02-06T20:07:52.739Z
diff --git a/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index 5fa2c85c9..d6426af87 100644
--- a/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/en/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -1,5 +1,5 @@
 ---
-title: 'Button "Cancel" inside the MyCards page not translated to Spanish'
+title: "Button 'Cancel' inside the MyCards page not translated to Spanish"
 id: 5wIEEoF7gTLYlWnANxDZ7h
 status: PUBLISHED
 createdAt: 2022-02-24T13:18:00.062Z
diff --git a/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
index 61e439361..8fe69e1a7 100644
--- a/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
+++ b/docs/known-issues/en/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campaign audience UI changing "Different from" to "Equal to" with a collection'
+title: "Campaign audience UI changing 'Different from' to 'Equal to' with a collection"
 id: 6IkWioZ9WRgg1DFEMdnthB
 status: PUBLISHED
 createdAt: 2023-08-15T15:12:54.580Z
diff --git a/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
index 54823ba3e..377a14c50 100644
--- a/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
+++ b/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -1,5 +1,5 @@
 ---
-title: "Cart created from an "order again" option in My Orders, the customer's email is not being placed as expected in the orderForm"
+title: "Cart created from an "order again' option in My Orders, the customer's email is not being placed as expected in the orderForm"
 id: 6dDhkaIhquOqaDuNkVZuln
 status: PUBLISHED
 createdAt: 2023-12-04T22:41:21.385Z
diff --git a/docs/known-issues/en/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md b/docs/known-issues/en/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
index 9a058e31e..52b08a1c1 100644
--- a/docs/known-issues/en/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
+++ b/docs/known-issues/en/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cart with items displays "empty cart" message while screen is still loading'
+title: "Cart with items displays 'empty cart' message while screen is still loading"
 id: 4oAiVz7fJL9vPkpPFEGyBT
 status: PUBLISHED
 createdAt: 2023-03-09T22:42:06.855Z
diff --git a/docs/known-issues/en/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md b/docs/known-issues/en/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
index 3cad0b55f..b21b86290 100644
--- a/docs/known-issues/en/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
+++ b/docs/known-issues/en/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
@@ -1,5 +1,5 @@
 ---
-title: 'Catalog Export does not show Sales Channels when "none" are tagged'
+title: "Catalog Export does not show Sales Channels when 'none' are tagged"
 id: 10Bozz8ai3fAvu1m9Ex2Gk
 status: PUBLISHED
 createdAt: 2022-12-23T13:38:32.114Z
diff --git a/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md
index 9088420ed..fe8189531 100644
--- a/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/en/catalog-indexing-report-total-section-calculation-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Catalog Indexing Report "Total" Section Calculation Error'
+title: "Catalog Indexing Report 'Total' Section Calculation Error"
 id: 6TJXux104P2c0mruo5vlEn
 status: PUBLISHED
 createdAt: 2022-02-25T11:39:42.098Z
diff --git a/docs/known-issues/en/centauro-orders-with-pedido-sem-o-campo-packages-error.md b/docs/known-issues/en/centauro-orders-with-pedido-sem-o-campo-packages-error.md
index 6b57c4f57..b10d942bd 100644
--- a/docs/known-issues/en/centauro-orders-with-pedido-sem-o-campo-packages-error.md
+++ b/docs/known-issues/en/centauro-orders-with-pedido-sem-o-campo-packages-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Centauro Orders with "Pedido sem o campo: "packages" error'
+title: "Centauro Orders with 'Pedido sem o campo: 'packages' error"
 id: 1HMhinuVlggWwQZPuNchiX
 status: PUBLISHED
 createdAt: 2022-06-24T13:10:45.752Z
diff --git a/docs/known-issues/en/centauro-to-implement-centauro-envios.md b/docs/known-issues/en/centauro-to-implement-centauro-envios.md
index 8cd7c280c..c70fdde0a 100644
--- a/docs/known-issues/en/centauro-to-implement-centauro-envios.md
+++ b/docs/known-issues/en/centauro-to-implement-centauro-envios.md
@@ -1,5 +1,5 @@
 ---
-title: '[Centauro] To implement "Centauro Envios"'
+title: "[Centauro] To implement 'Centauro Envios'"
 id: 1xkjyfVfT8Fs2as9mbNjj3
 status: PUBLISHED
 createdAt: 2022-11-25T21:23:23.849Z
diff --git a/docs/known-issues/en/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md b/docs/known-issues/en/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
index 55d3b9de4..c4c290bfd 100644
--- a/docs/known-issues/en/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
+++ b/docs/known-issues/en/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
@@ -1,5 +1,5 @@
 ---
-title: 'Changes to the "my account" page do not appear immediately in the domain "vtexcommercestable.com.br"'
+title: "Changes to the 'my account' page do not appear immediately in the domain 'vtexcommercestable.com.br'"
 id: iUmuXOYVj97sTpqQnJqAU
 status: PUBLISHED
 createdAt: 2019-03-19T13:23:11.941Z
diff --git a/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md b/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md
index 3eb20ee03..f1245a12e 100644
--- a/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md
+++ b/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md
@@ -1,5 +1,5 @@
 ---
-title: "Checkbox "Requires authentication" doesn't work on Pages module"
+title: "Checkbox "Requires authentication' doesn't work on Pages module"
 id: 6nKuqSmk7JZgdaAysNYls3
 status: PUBLISHED
 createdAt: 2022-05-11T21:25:07.700Z
diff --git a/docs/known-issues/en/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md b/docs/known-issues/en/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
index c65c6bd40..211d55a7f 100644
--- a/docs/known-issues/en/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
+++ b/docs/known-issues/en/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout payment split may generate incorrect information in the "paymentData" of orders (NO-PAYMENT)'
+title: "Checkout payment split may generate incorrect information in the 'paymentData' of orders (NO-PAYMENT)"
 id: 1bZ5H0T0isc0DUtkIb38sQ
 status: PUBLISHED
 createdAt: 2022-01-24T20:37:23.861Z
diff --git a/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
index b277f0e5e..d0a359c8f 100644
--- a/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
+++ b/docs/known-issues/en/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout Simulation returns value 0 in "slas.tax" field for Shipping Percentage taxes'
+title: "Checkout Simulation returns value 0 in 'slas.tax' field for Shipping Percentage taxes"
 id: 54Mtsj8EKuo0SaQCoWyYzj
 status: PUBLISHED
 createdAt: 2024-04-05T18:55:32.183Z
diff --git a/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
index 06a54b9d8..02ca06892 100644
--- a/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
+++ b/docs/known-issues/en/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout UI is not automatically using "lean shipping" for items with no common shipping methods'
+title: "Checkout UI is not automatically using 'lean shipping' for items with no common shipping methods"
 id: 2LXp8VCAay7Ic9MBfbtirT
 status: PUBLISHED
 createdAt: 2024-04-02T15:27:23.003Z
diff --git a/docs/known-issues/en/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md b/docs/known-issues/en/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
index 3f116e593..4e1f2509c 100644
--- a/docs/known-issues/en/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
+++ b/docs/known-issues/en/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout UI unselects the "Schedule all" toggle after refreshing the page'
+title: "Checkout UI unselects the 'Schedule all' toggle after refreshing the page"
 id: 28TIselp0EzU3iSD4kLJgX
 status: PUBLISHED
 createdAt: 2023-04-04T21:08:55.937Z
diff --git a/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index 62ad4114a..8b32e3ec3 100644
--- a/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/en/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -1,5 +1,5 @@
 ---
-title: 'Collections Field always appearing as "Equal To" on the Campaign Audience Form'
+title: "Collections Field always appearing as 'Equal To' on the Campaign Audience Form"
 id: 2NPEh7LZkrpO0gf802I7HZ
 status: PUBLISHED
 createdAt: 2022-11-11T21:18:53.386Z
diff --git a/docs/known-issues/en/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md b/docs/known-issues/en/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
index bbbf903f7..f81ece985 100644
--- a/docs/known-issues/en/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
+++ b/docs/known-issues/en/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
@@ -1,5 +1,5 @@
 ---
-title: 'Conflicts with price filters and "isAvailablePerSalesChannel" in searches (Portal and Search) (Again)'
+title: "Conflicts with price filters and 'isAvailablePerSalesChannel' in searches (Portal and Search) (Again)"
 id: 6dLv8lP69Em68ooydjaPzY
 status: PUBLISHED
 createdAt: 2022-02-24T13:24:42.299Z
diff --git a/docs/known-issues/en/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md b/docs/known-issues/en/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
index 9c6e856c2..d81073f1d 100644
--- a/docs/known-issues/en/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
+++ b/docs/known-issues/en/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
@@ -1,5 +1,5 @@
 ---
-title: 'Creating "custom fields" for "custom data" converts the IDs to lowercase letters'
+title: "Creating 'custom fields' for 'custom data' converts the IDs to lowercase letters"
 id: 6oCXPldEYkC9HG1fw3G3RL
 status: PUBLISHED
 createdAt: 2019-02-19T18:52:45.049Z
diff --git a/docs/known-issues/en/customer-credit-total-due-value-updating-according-to-the-pagination.md b/docs/known-issues/en/customer-credit-total-due-value-updating-according-to-the-pagination.md
index 69d68ca20..fec46683c 100644
--- a/docs/known-issues/en/customer-credit-total-due-value-updating-according-to-the-pagination.md
+++ b/docs/known-issues/en/customer-credit-total-due-value-updating-according-to-the-pagination.md
@@ -1,5 +1,5 @@
 ---
-title: 'Customer Credit "Total Due" value updating according to the pagination'
+title: "Customer Credit 'Total Due' value updating according to the pagination"
 id: 6faMqwY8yHsIdYjkwTgCCQ
 status: PUBLISHED
 createdAt: 2022-03-27T20:52:29.371Z
diff --git a/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
index ceda43ea0..e253ff59f 100644
--- a/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
+++ b/docs/known-issues/en/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -1,5 +1,5 @@
 ---
-title: 'Customer information being lost when it has some order with "profileErrorOnLoading"'
+title: "Customer information being lost when it has some order with 'profileErrorOnLoading'"
 id: 7B0eutLBOCKOun4iwALVpq
 status: PUBLISHED
 createdAt: 2023-06-27T12:51:33.790Z
diff --git a/docs/known-issues/en/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md b/docs/known-issues/en/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
index 8dd0152ff..24a7d600a 100644
--- a/docs/known-issues/en/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
+++ b/docs/known-issues/en/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
@@ -1,5 +1,5 @@
 ---
-title: '[Dafiti] Orders that are in "Awaiting Authorization to Dispatch" at VTEX, but are still "payment_pending" at Dafiti.'
+title: "[Dafiti] Orders that are in 'Awaiting Authorization to Dispatch' at VTEX, but are still 'payment_pending' at Dafiti."
 id: 6XbDr2QRAtk0bVAeywagjq
 status: PUBLISHED
 createdAt: 2022-12-20T13:14:31.368Z
diff --git a/docs/known-issues/en/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md b/docs/known-issues/en/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
index 2be6153db..d424fffb3 100644
--- a/docs/known-issues/en/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
+++ b/docs/known-issues/en/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
@@ -1,5 +1,5 @@
 ---
-title: 'DecidirV1 transaction got "reprocessed" after some retries to authorization'
+title: "DecidirV1 transaction got 'reprocessed' after some retries to authorization"
 id: 2fxfg1IlnFUxAjo9E47HPq
 status: PUBLISHED
 createdAt: 2022-03-03T21:19:22.471Z
diff --git a/docs/known-issues/en/delay-in-processing-the-shipping-policy-locked-in-processing-status.md b/docs/known-issues/en/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
index 0f53779de..ee7e062b1 100644
--- a/docs/known-issues/en/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
+++ b/docs/known-issues/en/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'Delay in processing the shipping policy (locked in "processing" status)'
+title: "Delay in processing the shipping policy (locked in 'processing' status)"
 id: 5wl2TdIbyQeCF8eoo5oYKl
 status: PUBLISHED
 createdAt: 2022-05-17T17:26:58.778Z
diff --git a/docs/known-issues/en/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md b/docs/known-issues/en/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
index 505a2ffdc..421a472da 100644
--- a/docs/known-issues/en/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
+++ b/docs/known-issues/en/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
@@ -1,5 +1,5 @@
 ---
-title: 'Divergent value while mixing "paymentSystemToCheckFirstInstallment" configuration and splitted items'
+title: "Divergent value while mixing 'paymentSystemToCheckFirstInstallment' configuration and splitted items"
 id: 3h2o69kTBqFdQlzhED2kMN
 status: PUBLISHED
 createdAt: 2023-03-07T18:35:31.215Z
diff --git a/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index c29a2c2da..a86f11590 100644
--- a/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -1,5 +1,5 @@
 ---
-title: "Erro "Category XXX not found in browse node mapping for SKU's department specification, choose a more specific global category" persistente"
+title: "Erro "Category XXX not found in browse node mapping for SKU's department specification, choose a more specific global category' persistente"
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
diff --git a/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index af19a06f6..aa5b58eb0 100644
--- a/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -1,5 +1,5 @@
 ---
-title: "Error "can't create search criteria! error: filter already exists:"brandId"" when creating a promotion excluding more than 1 brand."
+title: "Error "can't create search criteria! error: filter already exists:"brandId"' when creating a promotion excluding more than 1 brand."
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
diff --git a/docs/known-issues/en/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md b/docs/known-issues/en/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
index 6e0c7442b..241db3383 100644
--- a/docs/known-issues/en/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
+++ b/docs/known-issues/en/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error generating subscription order ""The same item cannot have more than one SLA selected"'
+title: "Error generating subscription order ''The same item cannot have more than one SLA selected'"
 id: 2aBMa8ncalkqSm2s868i1q
 status: PUBLISHED
 createdAt: 2022-09-29T13:31:57.984Z
diff --git a/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
index 674396588..7d3cdaf3e 100644
--- a/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/en/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error in refund and capture operations with Payout Split - "Value in recipients * is different than operation value *."'
+title: "Error in refund and capture operations with Payout Split - 'Value in recipients * is different than operation value *.'"
 id: 3Wo9ltN7Ju0ZqVLAQZcd7m
 status: PUBLISHED
 createdAt: 2023-08-23T13:57:20.424Z
diff --git a/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md
index 1339aa6da..061fdae0a 100644
--- a/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md
+++ b/docs/known-issues/en/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error in refund - "Value cannot be null. Parameter name: value"'
+title: "Error in refund - 'Value cannot be null. Parameter name: value'"
 id: 6TZFYB9zb02oMoN5IJMxR3
 status: PUBLISHED
 createdAt: 2024-06-13T18:49:16.797Z
diff --git a/docs/known-issues/en/error-integrating-sku-field-may-not-be-null-magalu.md b/docs/known-issues/en/error-integrating-sku-field-may-not-be-null-magalu.md
index 998cd0910..da1d260c7 100644
--- a/docs/known-issues/en/error-integrating-sku-field-may-not-be-null-magalu.md
+++ b/docs/known-issues/en/error-integrating-sku-field-may-not-be-null-magalu.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error integrating sku "Field may not be null" - Magalu'
+title: "Error integrating sku 'Field may not be null' - Magalu"
 id: 3SYlRr6XVrl7T3Uw646MkE
 status: PUBLISHED
 createdAt: 2022-08-19T21:01:40.357Z
diff --git a/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
index 6c7a1cd6c..e7605e674 100644
--- a/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
+++ b/docs/known-issues/en/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error occurs when attempting to perform a search using the "All" field in VTEX CRM'
+title: "Error occurs when attempting to perform a search using the 'All' field in VTEX CRM"
 id: 1OKMTJuUZx6mnDmYW3MBjP
 status: PUBLISHED
 createdAt: 2023-10-25T18:46:48.120Z
diff --git a/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
index 305b1c166..2b2b5924a 100644
--- a/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
+++ b/docs/known-issues/en/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "Something went wrong. Please try again." when adding images via Site Editor'
+title: "Error 'Something went wrong. Please try again.' when adding images via Site Editor"
 id: r3QVP1kp8HApP83bOi6t9
 status: PUBLISHED
 createdAt: 2023-11-07T22:33:02.296Z
diff --git a/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index cc2cc1ff1..a4ffd900c 100644
--- a/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -1,5 +1,5 @@
 ---
-title: "Exporting SKU images for accounts starting with 'h','t' or 'p' get this character cut in the "Image URL" rows."
+title: "Exporting SKU images for accounts starting with 'h','t' or 'p' get this character cut in the "Image URL' rows."
 id: 1IZdnE8IGwkBlbcFhjLrzn
 status: PUBLISHED
 createdAt: 2023-10-13T15:20:49.703Z
diff --git a/docs/known-issues/en/ey-send-kit-is-not-recording-a-change-in-the-card.md b/docs/known-issues/en/ey-send-kit-is-not-recording-a-change-in-the-card.md
index 797956254..dad0dab33 100644
--- a/docs/known-issues/en/ey-send-kit-is-not-recording-a-change-in-the-card.md
+++ b/docs/known-issues/en/ey-send-kit-is-not-recording-a-change-in-the-card.md
@@ -1,5 +1,5 @@
 ---
-title: 'ey "Send Kit:" is not recording a change in the Card'
+title: "ey 'Send Kit:' is not recording a change in the Card"
 id: 4J1SynfbrQqXpSIcveAMxJ
 status: PUBLISHED
 createdAt: 2022-06-14T11:56:12.170Z
diff --git a/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
index f49c46968..2f41a8632 100644
--- a/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
+++ b/docs/known-issues/en/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -1,5 +1,5 @@
 ---
-title: 'Failure to add data in the "deliver to another address" step causes the "go to payment" button to disappear'
+title: "Failure to add data in the 'deliver to another address' step causes the 'go to payment' button to disappear"
 id: cdZO8gGXDB1JZSj42AnVh
 status: PUBLISHED
 createdAt: 2022-01-24T21:42:52.750Z
diff --git a/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index f344e694a..d7a1bf0f4 100644
--- a/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/en/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -1,5 +1,5 @@
 ---
-title: 'Field "Exchanges and returns" is not updating on seller management UI after save'
+title: "Field 'Exchanges and returns' is not updating on seller management UI after save"
 id: 1z8LrsbGk5B2ejZ1PV9vaB
 status: PUBLISHED
 createdAt: 2022-11-01T17:47:30.359Z
diff --git a/docs/known-issues/en/field-reference-always-set-as-null.md b/docs/known-issues/en/field-reference-always-set-as-null.md
index fd6021f5c..74e0f9d9d 100644
--- a/docs/known-issues/en/field-reference-always-set-as-null.md
+++ b/docs/known-issues/en/field-reference-always-set-as-null.md
@@ -1,5 +1,5 @@
 ---
-title: 'Field "reference" always set as null'
+title: "Field 'reference' always set as null"
 id: 6Tq4zip0lfUm7vVJdwfZWx
 status: PUBLISHED
 createdAt: 2023-04-26T22:31:38.892Z
diff --git a/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
index 63b83138b..e7620dde0 100644
--- a/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
+++ b/docs/known-issues/en/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -1,5 +1,5 @@
 ---
-title: 'Filter "productClusterIds" is overwritten by "productClusterNames" while applying additional filters'
+title: "Filter 'productClusterIds' is overwritten by 'productClusterNames' while applying additional filters"
 id: 3d4BIZQBZgeK3eKwT8B1PZ
 status: PUBLISHED
 createdAt: 2023-09-13T22:42:57.138Z
diff --git a/docs/known-issues/en/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md b/docs/known-issues/en/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
index 38346107f..87d66da46 100644
--- a/docs/known-issues/en/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
+++ b/docs/known-issues/en/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
@@ -1,5 +1,5 @@
 ---
-title: 'Filter products by "Store" on the Catalog Admin can show the wrong ammount of results'
+title: "Filter products by 'Store' on the Catalog Admin can show the wrong ammount of results"
 id: E38Y6a81l7QNtrmh2I2id
 status: PUBLISHED
 createdAt: 2023-02-17T16:01:30.420Z
diff --git a/docs/known-issues/en/first-search-in-a-store-is-not-considered-on-ui-last-searches.md b/docs/known-issues/en/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
index 6eab2d5fb..a6e99dd2b 100644
--- a/docs/known-issues/en/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
+++ b/docs/known-issues/en/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
@@ -1,5 +1,5 @@
 ---
-title: 'First search in a store is not considered on UI "last searches"'
+title: "First search in a store is not considered on UI 'last searches'"
 id: 7mc9vRE92VGauQmRaK6NnU
 status: PUBLISHED
 createdAt: 2022-05-04T17:08:25.235Z
diff --git a/docs/known-issues/en/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md b/docs/known-issues/en/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
index 56316b814..02b1f1248 100644
--- a/docs/known-issues/en/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
+++ b/docs/known-issues/en/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: 'Flag "Only apply discount to the cheapest shipping option" not working as expected'
+title: "Flag 'Only apply discount to the cheapest shipping option' not working as expected"
 id: 15irjH6rNkHhkBeRNn9RUI
 status: PUBLISHED
 createdAt: 2022-10-05T18:01:57.821Z
diff --git a/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index ee9c5f37c..dffc4abbd 100644
--- a/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/en/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -1,5 +1,5 @@
 ---
-title: 'FOB External Marketplace integrate an order (Erro code: "FMT010")'
+title: "FOB External Marketplace integrate an order (Erro code: 'FMT010')"
 id: 3qzV4zJRkPIwQnAZuK5dWu
 status: PUBLISHED
 createdAt: 2022-02-25T16:33:49.641Z
diff --git a/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index e93f7ec17..9abed7fcf 100644
--- a/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -1,5 +1,5 @@
 ---
-title: ""Get all SKU suggestions" API doesn't keep same sku order when changing limits"
+title: ""Get all SKU suggestions' API doesn't keep same sku order when changing limits"
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
diff --git a/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md
index 85760ba7f..03e74c937 100644
--- a/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/en/get-product-by-refid-returning-null-when-not-found.md
@@ -1,5 +1,5 @@
 ---
-title: 'GET Product by Refid Returning "Null" when not Found'
+title: "GET Product by Refid Returning 'Null' when not Found"
 id: 6yiM9gJT5DB77pZSBNfGZ3
 status: PUBLISHED
 createdAt: 2023-05-16T19:35:46.743Z
diff --git a/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index 49e444760..4f9571d1d 100644
--- a/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/en/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -1,5 +1,5 @@
 ---
-title: 'Gift Card hub is adding an extra backslash ("/") when calling providers.'
+title: "Gift Card hub is adding an extra backslash ('/') when calling providers."
 id: 2ZstMKKGUbrdXGuhS2Rr1f
 status: PUBLISHED
 createdAt: 2022-09-30T21:07:47.856Z
diff --git a/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
index c66fa629f..78bbb0533 100644
--- a/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
+++ b/docs/known-issues/en/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -1,5 +1,5 @@
 ---
-title: 'Gift card - It does not return Fields "caption" and "relationName" when we make a get request.'
+title: "Gift card - It does not return Fields 'caption' and 'relationName' when we make a get request."
 id: 2nh2Cc3Hc2Zm0b1INtwDep
 status: PUBLISHED
 createdAt: 2023-06-23T19:33:35.774Z
diff --git a/docs/known-issues/en/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md b/docs/known-issues/en/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
index 1714a3dbc..933c7573c 100644
--- a/docs/known-issues/en/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
+++ b/docs/known-issues/en/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'Giftcard HUB setting "R$" as the automatic currency on the UI'
+title: "Giftcard HUB setting 'R$' as the automatic currency on the UI"
 id: 2ODtc4t1GSo3iUjT9Gk0uk
 status: PUBLISHED
 createdAt: 2022-11-03T12:57:31.895Z
diff --git a/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md b/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
index 6f1a782cd..25c5e0726 100644
--- a/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
+++ b/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
@@ -1,5 +1,5 @@
 ---
-title: ""Go to payment" button doesn't work in delivery split when switching between Delivery and Pick up options"
+title: ""Go to payment' button doesn't work in delivery split when switching between Delivery and Pick up options"
 id: 4VDxpsWl6N0SjriaqUtXG9
 status: PUBLISHED
 createdAt: 2023-02-17T18:03:49.526Z
diff --git a/docs/known-issues/en/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md b/docs/known-issues/en/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
index bb0e2fb5c..0563aa431 100644
--- a/docs/known-issues/en/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
+++ b/docs/known-issues/en/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
@@ -1,5 +1,5 @@
 ---
-title: '"How many times will your benefit be applied in your store" Saving Incorrectly on Promotion Form Interface'
+title: "'How many times will your benefit be applied in your store' Saving Incorrectly on Promotion Form Interface"
 id: 6vT0rYIry3cGx1nG5BPkmx
 status: PUBLISHED
 createdAt: 2022-06-28T19:23:30.074Z
diff --git a/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md b/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
index c4a20586f..56abdf282 100644
--- a/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
+++ b/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
@@ -1,5 +1,5 @@
 ---
-title: ""I don't know my ZIP code" link in the wedding list creation page is redirecting to the wedding list creation page"
+title: ""I don't know my ZIP code' link in the wedding list creation page is redirecting to the wedding list creation page"
 id: 59Go6zy62I2iwACQqW8qmA
 status: PUBLISHED
 createdAt: 2018-02-20T22:07:31.331Z
diff --git a/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
index 93cd1d1c5..abf03902c 100644
--- a/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
+++ b/docs/known-issues/en/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -1,5 +1,5 @@
 ---
-title: 'Import collection only accepts the order of products if import is made based on "skuId"'
+title: "Import collection only accepts the order of products if import is made based on 'skuId'"
 id: 7vXi2bDVyGHSMLluQi2ZWZ
 status: PUBLISHED
 createdAt: 2023-12-15T16:35:11.545Z
diff --git a/docs/known-issues/en/incorrect-address-format-on-the-my-cards-billing-addresses.md b/docs/known-issues/en/incorrect-address-format-on-the-my-cards-billing-addresses.md
index 5d74ab1c7..19f1179dd 100644
--- a/docs/known-issues/en/incorrect-address-format-on-the-my-cards-billing-addresses.md
+++ b/docs/known-issues/en/incorrect-address-format-on-the-my-cards-billing-addresses.md
@@ -1,5 +1,5 @@
 ---
-title: 'Incorrect address format on the "My Cards" billing addresses'
+title: "Incorrect address format on the 'My Cards' billing addresses"
 id: 25QxVtMOazrxugHZqFrhSG
 status: PUBLISHED
 createdAt: 2023-04-17T17:40:24.795Z
diff --git a/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
index 2f5d3157f..1c09c9500 100644
--- a/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/en/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Incorrect refund calculation in Payout Split - "Value in recipients * is different than operation value *."'
+title: "Incorrect refund calculation in Payout Split - 'Value in recipients * is different than operation value *.'"
 id: 7Fxtwnntpmi0DrUD5a603W
 status: PUBLISHED
 createdAt: 2024-07-29T15:07:07.716Z
diff --git a/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
index b1b63a22c..171cefc2c 100644
--- a/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
+++ b/docs/known-issues/en/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -1,5 +1,5 @@
 ---
-title: 'Insert SKU File API doesnt accept URLs from servers that require "User Agents"'
+title: "Insert SKU File API doesnt accept URLs from servers that require 'User Agents'"
 id: 5Z1PmRXyW78mohsKTMQfzj
 status: PUBLISHED
 createdAt: 2024-07-22T19:49:14.140Z
diff --git a/docs/known-issues/en/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md b/docs/known-issues/en/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
index f2b38a533..0c11f01c2 100644
--- a/docs/known-issues/en/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
+++ b/docs/known-issues/en/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
@@ -1,5 +1,5 @@
 ---
-title: 'Installments dropdown on checkout UI is "loose" when scrolling the screen'
+title: "Installments dropdown on checkout UI is 'loose' when scrolling the screen"
 id: 0bbx1aDD7qw3DmaeMOebp
 status: PUBLISHED
 createdAt: 2022-03-10T20:07:05.251Z
diff --git a/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
index 70b572c14..6fc374efb 100644
--- a/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
+++ b/docs/known-issues/en/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -1,5 +1,5 @@
 ---
-title: '"Invalid postal code" message in Checkout UI when address is in available addresses with different country'
+title: "'Invalid postal code' message in Checkout UI when address is in available addresses with different country"
 id: 4VggIx4xWPNW6OBIrQ0js4
 status: PUBLISHED
 createdAt: 2024-06-21T17:08:59.860Z
diff --git a/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md b/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
index d18f5e893..765726e8f 100644
--- a/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
+++ b/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'It is not possible to save some addresses from Argentina in "My Account"'
+title: "It is not possible to save some addresses from Argentina in 'My Account'"
 id: 6kWZsPNLSDYgmJPDsQOO2w
 status: PUBLISHED
 createdAt: 2022-05-05T14:57:01.624Z
diff --git a/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md b/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
index cdf128dbb..422f80e29 100644
--- a/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
+++ b/docs/known-issues/en/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'It is not possible to save some addresses from Chile in "My Account"'
+title: "It is not possible to save some addresses from Chile in 'My Account'"
 id: 6DLPSH4eJY0Hbgtc5iGh21
 status: PUBLISHED
 createdAt: 2022-02-24T14:51:08.104Z
diff --git a/docs/known-issues/en/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md b/docs/known-issues/en/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
index d64137a2a..a1b29b64f 100644
--- a/docs/known-issues/en/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
+++ b/docs/known-issues/en/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
@@ -1,5 +1,5 @@
 ---
-title: '"Large Indexed Text" and "Indexed Text" not being changed by Specification Import'
+title: "'Large Indexed Text' and 'Indexed Text' not being changed by Specification Import"
 id: 5ty5q8AfOROtCc8GegzZbd
 status: PUBLISHED
 createdAt: 2022-04-22T17:12:36.962Z
diff --git a/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
index e530908aa..f148d7246 100644
--- a/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
+++ b/docs/known-issues/en/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -1,5 +1,5 @@
 ---
-title: 'Lean shipping causes "Something went wrong" after changing pick-up points'
+title: "Lean shipping causes 'Something went wrong' after changing pick-up points"
 id: 45jQODtjZ4vLXniNJIlQZc
 status: PUBLISHED
 createdAt: 2024-06-20T21:11:53.067Z
diff --git a/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md
index 38a01ccb8..c8b3b92a4 100644
--- a/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md
+++ b/docs/known-issues/en/legacy-catalog-ui-delete-button-not-functional.md
@@ -1,5 +1,5 @@
 ---
-title: 'Legacy Catalog UI "delete" button not functional'
+title: "Legacy Catalog UI 'delete' button not functional"
 id: 2soNSJfiQMZcxlpW6jT2FR
 status: PUBLISHED
 createdAt: 2022-01-23T02:51:17.884Z
diff --git a/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md b/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
index 1a1999a17..0017f3ea4 100644
--- a/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
+++ b/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
@@ -1,5 +1,5 @@
 ---
-title: ""Let me know" email is sent even when the product is not available for the website's trade policy"
+title: ""Let me know' email is sent even when the product is not available for the website's trade policy"
 id: 577r3i32P5Yv9QIfVR5AYP
 status: PUBLISHED
 createdAt: 2021-02-22T20:44:52.444Z
diff --git a/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index f202bba67..4713ccd3b 100644
--- a/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/en/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -1,5 +1,5 @@
 ---
-title: 'Link "Why fill VTEX Global Category?" on category setup only works opening in a new tab'
+title: "Link 'Why fill VTEX Global Category?' on category setup only works opening in a new tab"
 id: 3u7aq2otUovQbO98lzjbus
 status: PUBLISHED
 createdAt: 2022-03-16T17:59:14.355Z
diff --git a/docs/known-issues/en/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md b/docs/known-issues/en/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
index 51b2afc66..cb5398b37 100644
--- a/docs/known-issues/en/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
+++ b/docs/known-issues/en/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
@@ -1,5 +1,5 @@
 ---
-title: '"List Purchases" link in the gift list report does not apply filter correctly in Orders Managment'
+title: "'List Purchases' link in the gift list report does not apply filter correctly in Orders Managment"
 id: 5p7nqrzUqIK88cYkkOqMMG
 status: PUBLISHED
 createdAt: 2017-04-03T19:36:10.117Z
diff --git a/docs/known-issues/en/logistics-inventory-full-access-permission-did-not-work-as-expected.md b/docs/known-issues/en/logistics-inventory-full-access-permission-did-not-work-as-expected.md
index df640dac9..b70bf8d9c 100644
--- a/docs/known-issues/en/logistics-inventory-full-access-permission-did-not-work-as-expected.md
+++ b/docs/known-issues/en/logistics-inventory-full-access-permission-did-not-work-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: '"Logistics inventory full access" permission did not work as expected'
+title: "'Logistics inventory full access' permission did not work as expected"
 id: 6F11U5C6cULOeJ3Jo5AgAc
 status: PUBLISHED
 createdAt: 2022-04-27T14:16:03.358Z
diff --git a/docs/known-issues/en/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/en/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 289743f18..4c13f3de9 100644
--- a/docs/known-issues/en/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/en/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: ' [Magalu] Order with error "Object reference not set to an instance of an object"'
+title: " [Magalu] Order with error 'Object reference not set to an instance of an object'"
 id: 6758qSnWuXR6TWQ1mlKOxs
 status: PUBLISHED
 createdAt: 2022-11-29T17:45:30.636Z
diff --git a/docs/known-issues/en/magazine-luiza-integrated-fob-order-with-conventional-delivery.md b/docs/known-issues/en/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
index 764971c09..91081d458 100644
--- a/docs/known-issues/en/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
+++ b/docs/known-issues/en/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
@@ -1,5 +1,5 @@
 ---
-title: '[Magazine Luiza] Integrated FOB order with "Conventional" delivery'
+title: "[Magazine Luiza] Integrated FOB order with 'Conventional' delivery"
 id: 74uM19UXEopXguM6m0JbOL
 status: PUBLISHED
 createdAt: 2022-12-23T12:40:05.775Z
diff --git a/docs/known-issues/en/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/en/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 46000d99c..42162f594 100644
--- a/docs/known-issues/en/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/en/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: '[Magazine Luiza] Order with error "Object reference not set to an instance of an object"'
+title: "[Magazine Luiza] Order with error 'Object reference not set to an instance of an object'"
 id: 72w2GWNOlosoOHhs1ip4dl
 status: PUBLISHED
 createdAt: 2023-03-23T20:11:55.897Z
diff --git a/docs/known-issues/en/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md b/docs/known-issues/en/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
index 25f857817..401bfa34b 100644
--- a/docs/known-issues/en/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
+++ b/docs/known-issues/en/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
@@ -1,5 +1,5 @@
 ---
-title: 'Main account is being selected as "Merchant.Name" in the sub-account environment'
+title: "Main account is being selected as 'Merchant.Name' in the sub-account environment"
 id: 51coXFBM2wtrJukH3oRESy
 status: PUBLISHED
 createdAt: 2023-03-29T20:54:19.877Z
diff --git a/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md
index bea3c6bcf..9fdacd7df 100644
--- a/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md
+++ b/docs/known-issues/en/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -1,5 +1,5 @@
 ---
-title: 'Match Multiple Received SKUs API returning "Invalid sellerId"'
+title: "Match Multiple Received SKUs API returning 'Invalid sellerId'"
 id: 60aL2Chds0Jo3m6XMkxmnG
 status: PUBLISHED
 createdAt: 2023-10-17T16:26:27.980Z
diff --git a/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
index 309344198..f611c8d04 100644
--- a/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
+++ b/docs/known-issues/en/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -1,5 +1,5 @@
 ---
-title: '"maximum number of eligible items for each cart" + more for less applies incorrect discount when using the same item.'
+title: "'maximum number of eligible items for each cart' + more for less applies incorrect discount when using the same item."
 id: gWIMhi9RCv9BE1RvV6GiM
 status: PUBLISHED
 createdAt: 2024-07-30T17:14:36.972Z
diff --git a/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
index 7eb1dc839..a1e0928a0 100644
--- a/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
+++ b/docs/known-issues/en/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -1,5 +1,5 @@
 ---
-title: 'MDv2 returns error "504 Gateway Timeout" when we try to update a document passing a symbol or special character.'
+title: "MDv2 returns error '504 Gateway Timeout' when we try to update a document passing a symbol or special character."
 id: 6GP5QBWyIAir2oKe08giT2
 status: PUBLISHED
 createdAt: 2023-08-09T13:04:34.819Z
diff --git a/docs/known-issues/en/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md b/docs/known-issues/en/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
index 918daa82f..40338ad3d 100644
--- a/docs/known-issues/en/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
+++ b/docs/known-issues/en/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
@@ -1,5 +1,5 @@
 ---
-title: '[Meli] Error sku integration "Input string was not in a correct format"'
+title: "[Meli] Error sku integration 'Input string was not in a correct format'"
 id: 2NCm4vLyb1juIuIGMaB048
 status: PUBLISHED
 createdAt: 2022-09-27T21:05:39.320Z
diff --git a/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
index 249703cb2..d7fb22077 100644
--- a/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
+++ b/docs/known-issues/en/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -1,5 +1,5 @@
 ---
-title: 'MELI integration is receiving errors from MELI "429 too many requests"'
+title: "MELI integration is receiving errors from MELI '429 too many requests'"
 id: 1e4g9nzZFyanywmLbSHq4D
 status: PUBLISHED
 createdAt: 2023-08-03T10:47:41.602Z
diff --git a/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md
index a9150b021..9b97b53a0 100644
--- a/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/en/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -1,5 +1,5 @@
 ---
-title: 'MELI integration ZIPCodes "11111" Meli - Lima/Perú'
+title: "MELI integration ZIPCodes '11111' Meli - Lima/Perú"
 id: 7ICcek0NOUczgtA65CaZk5
 status: PUBLISHED
 createdAt: 2023-05-16T17:50:38.417Z
diff --git a/docs/known-issues/en/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md b/docs/known-issues/en/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
index 9283ad8e5..74bfb2b67 100644
--- a/docs/known-issues/en/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
+++ b/docs/known-issues/en/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
@@ -1,5 +1,5 @@
 ---
-title: '[Meli] SKU integration with "Object reference not set to an instance of an object" error.'
+title: "[Meli] SKU integration with 'Object reference not set to an instance of an object' error."
 id: 3GNnAidwvASTP223ncqsiV
 status: PUBLISHED
 createdAt: 2022-12-07T11:59:25.793Z
diff --git a/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md
index 6201a1727..fac2fef43 100644
--- a/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md
+++ b/docs/known-issues/en/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -1,5 +1,5 @@
 ---
-title: 'Merchandising rules not working for the facet "productClusterIds"'
+title: "Merchandising rules not working for the facet 'productClusterIds'"
 id: 6sLODMgjuoyJD52uc0DBW1
 status: PUBLISHED
 createdAt: 2024-07-09T00:02:40.930Z
diff --git a/docs/known-issues/en/message-freight-value-has-changed-is-shown-incorrectly.md b/docs/known-issues/en/message-freight-value-has-changed-is-shown-incorrectly.md
index f389d4f89..f6936782e 100644
--- a/docs/known-issues/en/message-freight-value-has-changed-is-shown-incorrectly.md
+++ b/docs/known-issues/en/message-freight-value-has-changed-is-shown-incorrectly.md
@@ -1,5 +1,5 @@
 ---
-title: 'Message "Freight value has changed" is shown incorrectly'
+title: "Message 'Freight value has changed' is shown incorrectly"
 id: 6ct93Q2391vEd0JAt0n5RU
 status: PUBLISHED
 createdAt: 2023-03-21T22:28:23.673Z
diff --git a/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index 165dd8ce0..51d5b6d9a 100644
--- a/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/en/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -1,5 +1,5 @@
 ---
-title: 'Misbehaviors for addToCart mutation from checkout-graphql while sending "options" for already added items'
+title: "Misbehaviors for addToCart mutation from checkout-graphql while sending 'options' for already added items"
 id: 1lMWbgmBsOis9gAKcMm8ob
 status: PUBLISHED
 createdAt: 2022-05-03T20:42:18.655Z
diff --git a/docs/known-issues/en/my-account-page-does-not-work-on-domain-myvtex-com.md b/docs/known-issues/en/my-account-page-does-not-work-on-domain-myvtex-com.md
index 05dbd68c6..fa094e698 100644
--- a/docs/known-issues/en/my-account-page-does-not-work-on-domain-myvtex-com.md
+++ b/docs/known-issues/en/my-account-page-does-not-work-on-domain-myvtex-com.md
@@ -1,5 +1,5 @@
 ---
-title: '"My Account" page does not work on domain "myvtex.com"'
+title: "'My Account' page does not work on domain 'myvtex.com'"
 id: 1EW2Fuwbt3vO9uF8b9zRz4
 status: PUBLISHED
 createdAt: 2019-03-19T13:18:13.540Z
diff --git a/docs/known-issues/en/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md b/docs/known-issues/en/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
index 0a404863a..ef10bc698 100644
--- a/docs/known-issues/en/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
+++ b/docs/known-issues/en/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
@@ -1,5 +1,5 @@
 ---
-title: '"Não é possível inativar este produto porque ele possui um ou mais skus ativos." does not automatically translate on the Product admin'
+title: "'Não é possível inativar este produto porque ele possui um ou mais skus ativos.' does not automatically translate on the Product admin"
 id: 2wYoZ01LtolL1Tfhc4ldV8
 status: PUBLISHED
 createdAt: 2023-04-03T19:17:17.147Z
diff --git a/docs/known-issues/en/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md b/docs/known-issues/en/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md
index a576850e1..bbe84ec97 100644
--- a/docs/known-issues/en/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md
+++ b/docs/known-issues/en/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md
@@ -1,5 +1,5 @@
 ---
-title: '"ObterTotalDePontos" function does not work inside the Automatic Field'
+title: "'ObterTotalDePontos' function does not work inside the Automatic Field"
 id: 1iHy0tOPoUEIyGsYoq2Sqm
 status: PUBLISHED
 createdAt: 2018-12-10T18:08:19.476Z
diff --git a/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
index 404f7d44b..7238ac0f5 100644
--- a/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
+++ b/docs/known-issues/en/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -1,5 +1,5 @@
 ---
-title: "Order Filter doesn't work properly due to double quotes (") in the Promotion name or SKU name"
+title: "Order Filter doesn't work properly due to double quotes (') in the Promotion name or SKU name"
 id: 4Qm0akQTQXR8sSbkTDiBL7
 status: PUBLISHED
 createdAt: 2024-06-06T15:42:19.747Z
diff --git a/docs/known-issues/en/orders-with-error-sistema-de-perfis.md b/docs/known-issues/en/orders-with-error-sistema-de-perfis.md
index 53585eb7e..1b6ff7407 100644
--- a/docs/known-issues/en/orders-with-error-sistema-de-perfis.md
+++ b/docs/known-issues/en/orders-with-error-sistema-de-perfis.md
@@ -1,5 +1,5 @@
 ---
-title: 'Orders with error "Ocorreu um erro de comunicação com o Sistema de Perfis"'
+title: "Orders with error 'Ocorreu um erro de comunicação com o Sistema de Perfis'"
 id: 2vj48Gmty8i4oQuoSOS46y
 status: PUBLISHED
 createdAt: 2017-05-08T20:51:46.084Z
diff --git a/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md
index 85d7e7726..2084937ff 100644
--- a/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -1,5 +1,5 @@
 ---
-title: "Portal don't respect the tag "Principal" of SKU's Image"
+title: "Portal don't respect the tag "Principal' of SKU's Image"
 id: 2ej5V3eIGgkUoo0Omgacc6
 status: CHANGED
 createdAt: 2017-04-17T18:35:42.842Z
diff --git a/docs/known-issues/en/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md b/docs/known-issues/en/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
index f31707514..ff8329340 100644
--- a/docs/known-issues/en/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
+++ b/docs/known-issues/en/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
@@ -1,5 +1,5 @@
 ---
-title: ' "Position" of the trade policy depends on the page it is shown on the admin interface'
+title: " 'Position' of the trade policy depends on the page it is shown on the admin interface"
 id: 3kcSD7J5uuHYGdhBcg1lMa
 status: PUBLISHED
 createdAt: 2022-10-31T20:28:08.565Z
diff --git a/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
index f8aeb5f6a..4ee389cb7 100644
--- a/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
+++ b/docs/known-issues/en/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -1,5 +1,5 @@
 ---
-title: 'Price filter applied on top of "spot price" instead of regular price'
+title: "Price filter applied on top of 'spot price' instead of regular price"
 id: 2EEgRV1NxYuns4eF7F0ZqD
 status: PUBLISHED
 createdAt: 2024-02-15T19:39:53.576Z
diff --git a/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md
index 53fca52ef..6b4f42ea5 100644
--- a/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md
+++ b/docs/known-issues/en/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'Prices restricted to "Int32" max value on Change Price API'
+title: "Prices restricted to 'Int32' max value on Change Price API"
 id: 5mzOjCUYs7vXUkttbsK0za
 status: PUBLISHED
 createdAt: 2022-04-25T17:28:05.159Z
diff --git a/docs/known-issues/en/prices-restricted-to-int32-max-value-on-checkout-apis.md b/docs/known-issues/en/prices-restricted-to-int32-max-value-on-checkout-apis.md
index 474c74bff..a94d02dee 100644
--- a/docs/known-issues/en/prices-restricted-to-int32-max-value-on-checkout-apis.md
+++ b/docs/known-issues/en/prices-restricted-to-int32-max-value-on-checkout-apis.md
@@ -1,5 +1,5 @@
 ---
-title: 'Prices restricted to "Int32" max value on checkout APIs'
+title: "Prices restricted to 'Int32' max value on checkout APIs"
 id: 5mzOjCUYs7vXUkttbsK0za
 status: PUBLISHED
 createdAt: 2022-04-25T17:28:05.159Z
diff --git a/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
index 803cbd9ba..91a78764a 100644
--- a/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
+++ b/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -1,5 +1,5 @@
 ---
-title: "Prioritization by product's "keyword" not considering stopwords"
+title: "Prioritization by product's "keyword' not considering stopwords"
 id: 55S7nFg61dAyCeGQCIw6aK
 status: PUBLISHED
 createdAt: 2024-05-30T22:05:25.328Z
diff --git a/docs/known-issues/en/problems-opening-manage-inventory-by-admin-page-with-error-ui.md b/docs/known-issues/en/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
index f4810e51f..eee5febcb 100644
--- a/docs/known-issues/en/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
+++ b/docs/known-issues/en/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'Problems opening "Manage Inventory" by Admin page with error (UI).'
+title: "Problems opening 'Manage Inventory' by Admin page with error (UI)."
 id: 7owutd1w2Fa2JjgDnn3j5q
 status: PUBLISHED
 createdAt: 2022-03-15T20:14:57.926Z
diff --git a/docs/known-issues/en/problems-with-price-from-in-the-buttonbuymodal-control.md b/docs/known-issues/en/problems-with-price-from-in-the-buttonbuymodal-control.md
index 43a18e217..147b782d8 100644
--- a/docs/known-issues/en/problems-with-price-from-in-the-buttonbuymodal-control.md
+++ b/docs/known-issues/en/problems-with-price-from-in-the-buttonbuymodal-control.md
@@ -1,5 +1,5 @@
 ---
-title: 'Problems with "price from" in the "ButtonBuyModal" control'
+title: "Problems with 'price from' in the 'ButtonBuyModal' control"
 id: 2DdTK2AQNysEqM8AyMwSMQ
 status: PUBLISHED
 createdAt: 2018-10-05T17:06:27.321Z
diff --git a/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 972a6c506..2df045ab3 100644
--- a/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/en/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -1,5 +1,5 @@
 ---
-title: 'Product Insert/Update API allows "\n" in the textLink field.'
+title: "Product Insert/Update API allows '\n' in the textLink field."
 id: 5TfUw5tTxBEu9HkL3ypBKw
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.325Z
diff --git a/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
index e1e5c754f..ece515333 100644
--- a/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
+++ b/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -1,5 +1,5 @@
 ---
-title: ""Product name contains" search with more than one term doesn't work on catalog's redesigned UI"
+title: ""Product name contains' search with more than one term doesn't work on catalog's redesigned UI"
 id: 2kI6ab0kdpLG6m63ETGGqf
 status: PUBLISHED
 createdAt: 2024-06-05T13:38:38.836Z
diff --git a/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md
index 9f5cf1481..22b8dffc8 100644
--- a/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md
+++ b/docs/known-issues/en/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -1,5 +1,5 @@
 ---
-title: '"Product Specification" filter on Collection Module assuming incorrect values'
+title: "'Product Specification' filter on Collection Module assuming incorrect values"
 id: 2vg3t5kp7j4Ttla53pVjck
 status: PUBLISHED
 createdAt: 2023-10-26T22:22:44.895Z
diff --git a/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
index 4be51a718..0c1f92b72 100644
--- a/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
+++ b/docs/known-issues/en/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -1,5 +1,5 @@
 ---
-title: 'Products with "unitMultiplier" wrongly flagged as "with promotion" for search filters'
+title: "Products with 'unitMultiplier' wrongly flagged as 'with promotion' for search filters"
 id: 2rCi8K01DHsNuYsefE7oR2
 status: PUBLISHED
 createdAt: 2024-02-15T22:52:17.434Z
diff --git a/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
index 577ac9f00..dd00861c3 100644
--- a/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
+++ b/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -1,5 +1,5 @@
 ---
-title: "Purchase can't be finished and is stuck on "freight type has changed""
+title: "Purchase can't be finished and is stuck on "freight type has changed'"
 id: mgewQ8QmZ3V3dkc7vdJkV
 status: PUBLISHED
 createdAt: 2023-09-25T13:28:28.121Z
diff --git a/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md b/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
index a21ec47a3..d00ecb2b9 100644
--- a/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
+++ b/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
@@ -1,5 +1,5 @@
 ---
-title: "Purchase can't be finished and returns the error "receiver name field is invalid""
+title: "Purchase can't be finished and returns the error "receiver name field is invalid'"
 id: 6ALBFvGzD0SiSuttfXPiQo
 status: PUBLISHED
 createdAt: 2022-05-12T14:53:10.287Z
diff --git a/docs/known-issues/en/received-skus-review-tab-missing-products.md b/docs/known-issues/en/received-skus-review-tab-missing-products.md
index bb4a1acea..0a209cf3f 100644
--- a/docs/known-issues/en/received-skus-review-tab-missing-products.md
+++ b/docs/known-issues/en/received-skus-review-tab-missing-products.md
@@ -1,5 +1,5 @@
 ---
-title: 'Received Skus "Review" tab missing products'
+title: "Received Skus 'Review' tab missing products"
 id: 2UM0JQUZVq5o7NHCjmrg8N
 status: PUBLISHED
 createdAt: 2023-11-23T16:30:51.874Z
diff --git a/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 08393b335..125ce2d8f 100644
--- a/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,5 +1,5 @@
 ---
-title: "Regions API doesn't calculate the "seller 1" correctly while requesting non-whitelabel sellers"
+title: "Regions API doesn't calculate the "seller 1' correctly while requesting non-whitelabel sellers"
 id: 20sT9AMMi7Ob5IZc7FeiCB
 status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
diff --git a/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md
index ce86b1486..223551f5e 100644
--- a/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md
+++ b/docs/known-issues/en/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -1,5 +1,5 @@
 ---
-title: 'Search banners not following the operator "AND" for trigger conditions'
+title: "Search banners not following the operator 'AND' for trigger conditions"
 id: 4nQLt5q3Mz2DxvBIyZknXj
 status: PUBLISHED
 createdAt: 2024-06-20T21:17:46.485Z
diff --git a/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
index a06935177..d4e0defdd 100644
--- a/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
@@ -1,5 +1,5 @@
 ---
-title: "Second-level folders don't consider the "search context""
+title: "Second-level folders don't consider the "search context'"
 id: 6WvlorgpBEeIuKk2mprMXm
 status: PUBLISHED
 createdAt: 2019-02-17T19:55:07.529Z
diff --git a/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
index 738696d7d..ade184f72 100644
--- a/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
+++ b/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -1,5 +1,5 @@
 ---
-title: "Settings UI doesn't update "expiration period" of quotes"
+title: "Settings UI doesn't update "expiration period' of quotes"
 id: 4CmuAYwDn7tcCiR9DQHSFb
 status: PUBLISHED
 createdAt: 2023-08-07T19:42:22.810Z
diff --git a/docs/known-issues/en/shipping-component-locked-in-waiting-for-more-information-state.md b/docs/known-issues/en/shipping-component-locked-in-waiting-for-more-information-state.md
index cf347df53..ffd7b7921 100644
--- a/docs/known-issues/en/shipping-component-locked-in-waiting-for-more-information-state.md
+++ b/docs/known-issues/en/shipping-component-locked-in-waiting-for-more-information-state.md
@@ -1,5 +1,5 @@
 ---
-title: 'Shipping component locked in "Waiting for more information" state'
+title: "Shipping component locked in 'Waiting for more information' state"
 id: 7HHlJdZvZ31NgsB7lTShAz
 status: PUBLISHED
 createdAt: 2023-03-29T19:26:05.971Z
diff --git a/docs/known-issues/en/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md b/docs/known-issues/en/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
index a330c0677..bb7509d27 100644
--- a/docs/known-issues/en/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
+++ b/docs/known-issues/en/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
@@ -1,5 +1,5 @@
 ---
-title: 'Shipping policy not prioritized due "Reason: Dismissed as a matter of priority" even with better cost'
+title: "Shipping policy not prioritized due 'Reason: Dismissed as a matter of priority' even with better cost"
 id: p1oTHG7CuYITViV4uFZEQ
 status: PUBLISHED
 createdAt: 2022-05-10T18:05:57.097Z
diff --git a/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md
index e5a979869..891b026f8 100644
--- a/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md
+++ b/docs/known-issues/en/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -1,5 +1,5 @@
 ---
-title: 'SKU Insert File API is not responding with the "Text" property.'
+title: "SKU Insert File API is not responding with the 'Text' property."
 id: 2rPsyAkpGNCVIM4yGlcMBw
 status: PUBLISHED
 createdAt: 2024-04-10T14:59:14.341Z
diff --git a/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
index c13e67a62..8f93d8bf0 100644
--- a/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
+++ b/docs/known-issues/en/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -1,5 +1,5 @@
 ---
-title: '"Something went wrong" when adding an incomplete address and tried to edit it'
+title: "'Something went wrong' when adding an incomplete address and tried to edit it"
 id: 3rWGAr4K86JAetSBJ75q3h
 status: PUBLISHED
 createdAt: 2024-01-02T21:11:17.425Z
diff --git a/docs/known-issues/en/special-character-not-mapped-to-be-ignored-in-textlink.md b/docs/known-issues/en/special-character-not-mapped-to-be-ignored-in-textlink.md
index 33569a472..43662b604 100644
--- a/docs/known-issues/en/special-character-not-mapped-to-be-ignored-in-textlink.md
+++ b/docs/known-issues/en/special-character-not-mapped-to-be-ignored-in-textlink.md
@@ -1,5 +1,5 @@
 ---
-title: 'Special character "|" not mapped to be ignored in TextLink'
+title: "Special character '|' not mapped to be ignored in TextLink"
 id: 5ALFG0CX168qaYUYWecW2q
 status: PUBLISHED
 createdAt: 2017-09-06T20:33:05.265Z
diff --git a/docs/known-issues/en/status-erro-de-processamento-shipping-policy.md b/docs/known-issues/en/status-erro-de-processamento-shipping-policy.md
index 17eec7391..c0021665f 100644
--- a/docs/known-issues/en/status-erro-de-processamento-shipping-policy.md
+++ b/docs/known-issues/en/status-erro-de-processamento-shipping-policy.md
@@ -1,5 +1,5 @@
 ---
-title: 'Status "ERRO DE PROCESSAMENTO" Shipping Policy'
+title: "Status 'ERRO DE PROCESSAMENTO' Shipping Policy"
 id: 4g3SWNwDVJG5OeJVP05TOd
 status: PUBLISHED
 createdAt: 2022-05-18T15:12:15.503Z
diff --git a/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 57b0bc687..f34b6269b 100644
--- a/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/en/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -1,5 +1,5 @@
 ---
-title: 'StockKeepingUnitByEAN returns 404 for EANs with "/"'
+title: "StockKeepingUnitByEAN returns 404 for EANs with '/'"
 id: Pp3lE5Gu54gOw6liInte4
 status: DRAFT
 createdAt: 2022-02-25T12:23:55.903Z
diff --git a/docs/known-issues/en/store-texts-search-doesnt-work.md b/docs/known-issues/en/store-texts-search-doesnt-work.md
index e6188d0ba..a560efc73 100644
--- a/docs/known-issues/en/store-texts-search-doesnt-work.md
+++ b/docs/known-issues/en/store-texts-search-doesnt-work.md
@@ -1,5 +1,5 @@
 ---
-title: ""Store texts" search doesn't work"
+title: ""Store texts' search doesn't work"
 id: 6C6JUkssKcOoQqsaikucwy
 status: PUBLISHED
 createdAt: 2017-08-24T15:16:31.392Z
diff --git a/docs/known-issues/en/storefront-permissions-app-sets-documenttype-as-cpf.md b/docs/known-issues/en/storefront-permissions-app-sets-documenttype-as-cpf.md
index 8ffd58e77..d7ee3e721 100644
--- a/docs/known-issues/en/storefront-permissions-app-sets-documenttype-as-cpf.md
+++ b/docs/known-issues/en/storefront-permissions-app-sets-documenttype-as-cpf.md
@@ -1,5 +1,5 @@
 ---
-title: 'Storefront permissions app sets "documentType" as "cpf"'
+title: "Storefront permissions app sets 'documentType' as 'cpf'"
 id: 1vd0gFWrP50UZacQ0QBKP8
 status: PUBLISHED
 createdAt: 2023-04-27T15:19:53.064Z
diff --git a/docs/known-issues/en/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md b/docs/known-issues/en/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
index 356bd2a68..ebe8b5ad5 100644
--- a/docs/known-issues/en/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
+++ b/docs/known-issues/en/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
@@ -1,5 +1,5 @@
 ---
-title: 'Subscription plan is "stuck" in "importing" after uploading the SKUs association spreadsheet'
+title: "Subscription plan is 'stuck' in 'importing' after uploading the SKUs association spreadsheet"
 id: 4BVj2X44OZMttG57vUryHb
 status: PUBLISHED
 createdAt: 2022-05-03T00:28:48.118Z
diff --git a/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
index 668017aa5..fddfa60ee 100644
--- a/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
+++ b/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -1,5 +1,5 @@
 ---
-title: "Telesales search doesn't accept special characters aside from "@"."
+title: "Telesales search doesn't accept special characters aside from "@'."
 id: 5eTb6KlR07dOP06BGhovoL
 status: PUBLISHED
 createdAt: 2024-07-29T17:21:34.828Z
diff --git a/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index dacdb49fd..579787b85 100644
--- a/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/en/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -1,5 +1,5 @@
 ---
-title: 'Textlink created with " " on Marketplace upon approvals - Reoccurence'
+title: "Textlink created with ' ' on Marketplace upon approvals - Reoccurence"
 id: 2afynQ9MwaHPMPWyhx80Tp
 status: PUBLISHED
 createdAt: 2023-04-24T19:36:10.185Z
diff --git a/docs/known-issues/en/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md b/docs/known-issues/en/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
index 35b3e3ddb..023023c3e 100644
--- a/docs/known-issues/en/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
+++ b/docs/known-issues/en/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
@@ -1,5 +1,5 @@
 ---
-title: 'The Cielo 3DS2 app is returning an "approved" status even in scenarios when the authentication has failed.'
+title: "The Cielo 3DS2 app is returning an 'approved' status even in scenarios when the authentication has failed."
 id: 58hSiWFhn6sHQofJAUoHqv
 status: PUBLISHED
 createdAt: 2023-05-05T14:48:56.148Z
diff --git a/docs/known-issues/en/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md b/docs/known-issues/en/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
index b050a52af..245a498e3 100644
--- a/docs/known-issues/en/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
+++ b/docs/known-issues/en/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
@@ -1,5 +1,5 @@
 ---
-title: 'The Delivery Split will not be displayed in the UI or in My Orders, when the order has the same "Shipping Method".'
+title: "The Delivery Split will not be displayed in the UI or in My Orders, when the order has the same 'Shipping Method'."
 id: 2VnPyguau8KjpWx09C2vOW
 status: PUBLISHED
 createdAt: 2022-03-15T20:24:32.693Z
diff --git a/docs/known-issues/en/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md b/docs/known-issues/en/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md
index f2bbd79eb..25cd14021 100644
--- a/docs/known-issues/en/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md
+++ b/docs/known-issues/en/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md
@@ -1,5 +1,5 @@
 ---
-title: 'The field "Administrator who approved the product (id)" does not change when the updating is done by webservice'
+title: "The field 'Administrator who approved the product (id)' does not change when the updating is done by webservice"
 id: 5R6Jj0aglq0gUu2OakqgUw
 status: PUBLISHED
 createdAt: 2017-04-11T22:17:03.345Z
diff --git a/docs/known-issues/en/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md b/docs/known-issues/en/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
index bbbb2a560..e36caa52e 100644
--- a/docs/known-issues/en/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
+++ b/docs/known-issues/en/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
@@ -1,5 +1,5 @@
 ---
-title: 'The Issuing Bank Special Condition is causing for some BINs the error on checkout page "Issuer bank for this bank is not accepted"'
+title: "The Issuing Bank Special Condition is causing for some BINs the error on checkout page 'Issuer bank for this bank is not accepted'"
 id: 7HgNpwcvqQDwSfJfv9KpY8
 status: PUBLISHED
 createdAt: 2022-03-25T19:04:12.310Z
diff --git a/docs/known-issues/en/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md b/docs/known-issues/en/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
index 3fcf6b22b..4979d3142 100644
--- a/docs/known-issues/en/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
+++ b/docs/known-issues/en/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
@@ -1,5 +1,5 @@
 ---
-title: 'The message "My billing address is ..." on the credit card iFrame is in the wrong language when using checkout in Catalan language'
+title: "The message 'My billing address is ...' on the credit card iFrame is in the wrong language when using checkout in Catalan language"
 id: 3AqPihwDDIM2qixa1jvJmz
 status: PUBLISHED
 createdAt: 2022-03-28T01:11:35.679Z
diff --git a/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index eea9c4c60..fff0c667c 100644
--- a/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/en/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -1,5 +1,5 @@
 ---
-title: 'The "Save new card" option does not work for asynchronous Payment Providers'
+title: "The 'Save new card' option does not work for asynchronous Payment Providers"
 id: 3B4gVSNrSeCc8EBXwk5sAu
 status: PUBLISHED
 createdAt: 2022-03-11T17:54:35.664Z
diff --git a/docs/known-issues/en/the-save-new-card-option-does-not-work-when-using-3-d-secure-3ds.md b/docs/known-issues/en/the-save-new-card-option-does-not-work-when-using-3-d-secure-3ds.md
index 1f0d58d54..468a2780f 100644
--- a/docs/known-issues/en/the-save-new-card-option-does-not-work-when-using-3-d-secure-3ds.md
+++ b/docs/known-issues/en/the-save-new-card-option-does-not-work-when-using-3-d-secure-3ds.md
@@ -1,5 +1,5 @@
 ---
-title: 'The "Save new card" option does not work when using 3-D Secure (3DS)'
+title: "The 'Save new card' option does not work when using 3-D Secure (3DS)"
 id: 20INELA5LVhY1XqFWG7047
 status: PUBLISHED
 createdAt: 2021-06-15T17:10:05.803Z
diff --git a/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index a3f436e5f..6871647a6 100644
--- a/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/en/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -1,5 +1,5 @@
 ---
-title: 'The template "relatorio-de-importacao-de-estoque" does not support multi-language'
+title: "The template 'relatorio-de-importacao-de-estoque' does not support multi-language"
 id: 5R8b0jnibOQdXupo0hIyts
 status: PUBLISHED
 createdAt: 2022-05-25T18:25:43.394Z
diff --git a/docs/known-issues/en/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md b/docs/known-issues/en/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
index c4c909360..17a26840b 100644
--- a/docs/known-issues/en/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
+++ b/docs/known-issues/en/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
@@ -1,5 +1,5 @@
 ---
-title: 'Transaction canceled by timeout: "Timeout no request para o Sistema de Parcelamento"'
+title: "Transaction canceled by timeout: 'Timeout no request para o Sistema de Parcelamento'"
 id: 68L2ka1QJ3yEHTsId1arF7
 status: PUBLISHED
 createdAt: 2022-03-02T12:15:17.495Z
diff --git a/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md
index 446bbefb5..39aaccd8c 100644
--- a/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md
+++ b/docs/known-issues/en/transaction-cancellation-error-with-unreachable-code-message.md
@@ -1,5 +1,5 @@
 ---
-title: 'Transaction cancellation error with "Unreachable code" message'
+title: "Transaction cancellation error with 'Unreachable code' message"
 id: 2Y4joZlyDhbNWU9ycw32U3
 status: PUBLISHED
 createdAt: 2024-03-12T16:34:10.113Z
diff --git a/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md
index 79cd50a30..72ec62476 100644
--- a/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md
+++ b/docs/known-issues/en/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -1,5 +1,5 @@
 ---
-title: 'UI shows "Gifts picked!" when using Order replacement feature'
+title: "UI shows 'Gifts picked!' when using Order replacement feature"
 id: 4efm7L6hQhad98uYkjzrXO
 status: PUBLISHED
 createdAt: 2023-09-27T20:57:46.944Z
diff --git a/docs/known-issues/en/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md b/docs/known-issues/en/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
index 1642bb3c1..494ada04f 100644
--- a/docs/known-issues/en/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
+++ b/docs/known-issues/en/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
@@ -1,5 +1,5 @@
 ---
-title: 'Unable to change status on gateway when transaction Cart object in /transaction is "unknown".'
+title: "Unable to change status on gateway when transaction Cart object in /transaction is 'unknown'."
 id: 3gWqk1T2xP3eRYZtXZLX3b
 status: PUBLISHED
 createdAt: 2023-03-23T14:27:16.116Z
diff --git a/docs/known-issues/en/unable-to-create-produtos-relacionados-custom-element.md b/docs/known-issues/en/unable-to-create-produtos-relacionados-custom-element.md
index 80a5befdf..59471c212 100644
--- a/docs/known-issues/en/unable-to-create-produtos-relacionados-custom-element.md
+++ b/docs/known-issues/en/unable-to-create-produtos-relacionados-custom-element.md
@@ -1,5 +1,5 @@
 ---
-title: 'Unable to create "Produtos Relacionados" Custom Element'
+title: "Unable to create 'Produtos Relacionados' Custom Element"
 id: 4Ca3b0mfpe20K7wSaImSQj
 status: PUBLISHED
 createdAt: 2022-01-21T14:44:26.429Z
diff --git a/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md
index 5c836f4c2..e956b2173 100644
--- a/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md
+++ b/docs/known-issues/en/unhandled-exception-error-when-changing-edition-of-account.md
@@ -1,5 +1,5 @@
 ---
-title: '"Unhandled exception" error when changing edition of account'
+title: "'Unhandled exception' error when changing edition of account"
 id: 1NVjCrlRkadscl8fW9rOdA
 status: PUBLISHED
 createdAt: 2023-09-26T12:45:44.999Z
diff --git a/docs/known-issues/en/url-logo-field-in-the-update-seller-request-not-updating.md b/docs/known-issues/en/url-logo-field-in-the-update-seller-request-not-updating.md
index f6a86f65b..0a004fac3 100644
--- a/docs/known-issues/en/url-logo-field-in-the-update-seller-request-not-updating.md
+++ b/docs/known-issues/en/url-logo-field-in-the-update-seller-request-not-updating.md
@@ -1,5 +1,5 @@
 ---
-title: '"Url Logo" Field in the Update Seller Request not Updating'
+title: "'Url Logo' Field in the Update Seller Request not Updating"
 id: 1WmNl3RgesWAUL8rjitJV1
 status: PUBLISHED
 createdAt: 2022-01-21T15:18:15.945Z
diff --git a/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
index cc6ee8db8..86a63bd65 100644
--- a/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
+++ b/docs/known-issues/en/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -1,5 +1,5 @@
 ---
-title: 'User only with the role "User Administrator - RESTRICTED" is not able to list the users'
+title: "User only with the role 'User Administrator - RESTRICTED' is not able to list the users"
 id: ifXUAzgJ1xr8ezhqKpRUI
 status: PUBLISHED
 createdAt: 2023-11-08T18:07:14.508Z
diff --git a/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md
index 4aa94de7c..dd4cda7dd 100644
--- a/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md
+++ b/docs/known-issues/en/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -1,5 +1,5 @@
 ---
-title: 'Version author "Note: Not found on VTEX ID." on the profile'
+title: "Version author 'Note: Not found on VTEX ID.' on the profile"
 id: 0X6Aj6YdCXXfNweAkDS46
 status: PUBLISHED
 createdAt: 2023-10-04T21:48:14.699Z
diff --git a/docs/known-issues/en/visited-product-feature-does-not-work-properly.md b/docs/known-issues/en/visited-product-feature-does-not-work-properly.md
index cb82a8d9e..fab18618d 100644
--- a/docs/known-issues/en/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/en/visited-product-feature-does-not-work-properly.md
@@ -1,5 +1,5 @@
 ---
-title: ' "Visited product" feature does not work properly'
+title: " 'Visited product' feature does not work properly"
 id: 5AiCVwLkGToEgtLkZVPe5i
 status: PUBLISHED
 createdAt: 2022-11-25T18:45:15.389Z
diff --git a/docs/known-issues/en/vtexcontentplaceholder-idacessorios-is-not-working.md b/docs/known-issues/en/vtexcontentplaceholder-idacessorios-is-not-working.md
index 8d1d3eaf9..644706995 100644
--- a/docs/known-issues/en/vtexcontentplaceholder-idacessorios-is-not-working.md
+++ b/docs/known-issues/en/vtexcontentplaceholder-idacessorios-is-not-working.md
@@ -1,5 +1,5 @@
 ---
-title: '<vtex:contentPlaceHolder id="Acessorios"/> is not working'
+title: "<vtex:contentPlaceHolder id='Acessorios'/> is not working"
 id: 7x8f0vGaunX1P3EFJGCYaz
 status: PUBLISHED
 createdAt: 2022-01-23T02:24:12.606Z
diff --git a/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 6a8bb04c0..8391a1495 100644
--- a/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/en/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -1,5 +1,5 @@
 ---
-title: 'When adding a SKU through our "Change Order" functionality, the product name is not displayed in the order and e-mail notification'
+title: "When adding a SKU through our 'Change Order' functionality, the product name is not displayed in the order and e-mail notification"
 id: 35Q3KoOSsUr9n9XEDIk7nk
 status: PUBLISHED
 createdAt: 2022-04-07T14:53:35.829Z
diff --git a/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index f97880e29..0fd35ea59 100644
--- a/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/en/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -1,5 +1,5 @@
 ---
-title: 'When loading the "Catalog Maping" page on admin the initial message is not translated'
+title: "When loading the 'Catalog Maping' page on admin the initial message is not translated"
 id: 4WszmRZ5jpeSDNTEuFIdwF
 status: PUBLISHED
 createdAt: 2022-12-15T12:32:17.741Z
diff --git a/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 8f691bdeb..1e9d714cf 100644
--- a/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/en/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -1,5 +1,5 @@
 ---
-title: 'When settleId is sent as null and code as "refund-manually" our gateway performs a double refund.'
+title: "When settleId is sent as null and code as 'refund-manually' our gateway performs a double refund."
 id: 2PdRRjHDODY2Tk0VItO4Fo
 status: PUBLISHED
 createdAt: 2022-07-11T17:37:43.961Z
diff --git a/docs/known-issues/en/xml-currency-symbol-in-the-installment.md b/docs/known-issues/en/xml-currency-symbol-in-the-installment.md
index 9d0e0baf0..2b66fa829 100644
--- a/docs/known-issues/en/xml-currency-symbol-in-the-installment.md
+++ b/docs/known-issues/en/xml-currency-symbol-in-the-installment.md
@@ -1,5 +1,5 @@
 ---
-title: 'XML - Currency symbol in the "Installment"'
+title: "XML - Currency symbol in the 'Installment'"
 id: 4s7hBA1MAUgeEC2Q4K8gKM
 status: DRAFT
 createdAt: 2017-06-26T15:22:31.980Z
diff --git a/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
index 2273b0695..bd0d16c52 100644
--- a/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
+++ b/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
@@ -1,5 +1,5 @@
 ---
-title: "XML's "Product Name" flag not working properly"
+title: "XML's "Product Name' flag not working properly"
 id: 6YDbpRns3LCN02bVKM8aaf
 status: PUBLISHED
 createdAt: 2023-10-26T11:35:14.500Z
diff --git a/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
index ad6335718..55c776f4a 100644
--- a/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
+++ b/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -1,5 +1,5 @@
 ---
-title: 'Una SKU puede estar activa y tener el indicador "activar si es posible" desmarcado'
+title: "Una SKU puede estar activa y tener el indicador 'activar si es posible' desmarcado"
 id: 5uXQ65flkoEbYeLkNSw4ig
 status: PUBLISHED
 createdAt: 2023-11-07T11:01:20.612Z
diff --git a/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md b/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
index c1311c058..7f5a54d12 100644
--- a/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
+++ b/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
@@ -1,5 +1,5 @@
 ---
-title: 'Las cuentas con "-" en el nombre no tienen métricas en el informe de búsqueda'
+title: "Las cuentas con '-' en el nombre no tienen métricas en el informe de búsqueda"
 id: 71rVz43g0rgIN7Joe4GEj6
 status: PUBLISHED
 createdAt: 2023-04-19T17:35:28.560Z
diff --git a/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
index 5134c8199..3255ccce8 100644
--- a/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/es/add-option-not-available-when-creating-dictionary.md
@@ -1,5 +1,5 @@
 ---
-title: 'Crear diccionario no proporciona la opción de "Add"'
+title: "Crear diccionario no proporciona la opción de 'Add'"
 id: 6kSvXDetqLw954q5hYIRQN
 status: PUBLISHED
 createdAt: 2019-12-26T14:48:14.548Z
diff --git a/docs/known-issues/es/address-field-comes-with-null-vaule-in-payments-api-query.md b/docs/known-issues/es/address-field-comes-with-null-vaule-in-payments-api-query.md
index 0fb801ff3..7d72b2541 100644
--- a/docs/known-issues/es/address-field-comes-with-null-vaule-in-payments-api-query.md
+++ b/docs/known-issues/es/address-field-comes-with-null-vaule-in-payments-api-query.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campo "address" trae valor "null" en la consulta de la API del Pagos'
+title: "Campo 'address' trae valor 'null' en la consulta de la API del Pagos"
 id: 7oEEc24umACsOoy4Ceso2W
 status: PUBLISHED
 createdAt: 2018-01-11T16:33:01.231Z
diff --git a/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md b/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
index 6b7d3e1dc..7416e2e45 100644
--- a/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
+++ b/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
@@ -1,5 +1,5 @@
 ---
-title: 'Dirección en orderForm con tamaño excesivo para múltiples ciudades separadas por "::"'
+title: "Dirección en orderForm con tamaño excesivo para múltiples ciudades separadas por '::'"
 id: 7E6x4O56SxcSeU2qv09GBt
 status: PUBLISHED
 createdAt: 2023-01-06T11:52:36.229Z
diff --git a/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
index 1ad069193..5f1940868 100644
--- a/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
+++ b/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -1,5 +1,5 @@
 ---
-title: 'Las direcciones se muestran en la caja cuando el comprador tiene permiso para "Añadir envío".'
+title: "Las direcciones se muestran en la caja cuando el comprador tiene permiso para 'Añadir envío'."
 id: 2ssiTryGJ6kGoZWxWkGnFF
 status: PUBLISHED
 createdAt: 2024-05-21T22:03:55.172Z
diff --git a/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
index 1cf7e27d8..cbf7d5ab5 100644
--- a/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
+++ b/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'La falta de coincidencia de AddressId provoca el error "dirección no válida para un artículo".'
+title: "La falta de coincidencia de AddressId provoca el error 'dirección no válida para un artículo'."
 id: 5bSac85eHb9NmrOhcTjHNw
 status: PUBLISHED
 createdAt: 2024-03-01T19:28:52.074Z
diff --git a/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
index ab462b3ce..1e011d417 100644
--- a/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
+++ b/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -1,5 +1,5 @@
 ---
-title: '[Admin] La búsqueda global no reconoce los "Elementos del menú de perfil".'
+title: "[Admin] La búsqueda global no reconoce los 'Elementos del menú de perfil'."
 id: 4AZiu9NXouL6b8z5EHJIWK
 status: PUBLISHED
 createdAt: 2024-01-22T17:09:55.423Z
diff --git a/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md b/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
index 2cfb32c8c..10c122a1d 100644
--- a/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
+++ b/docs/known-issues/es/admin-homepage-has-an-error-in-how-to-improve-section-of-the-catalog.md
@@ -1,5 +1,5 @@
 ---
-title: 'La página de inicio del Admin presenta un error en la sección "Cómo mejorar" del Catálogo'
+title: "La página de inicio del Admin presenta un error en la sección 'Cómo mejorar' del Catálogo"
 id: 4f8oPMiiCvBMtjFUoOVIGv
 status: CHANGED
 createdAt: 2021-09-29T14:02:37.809Z
diff --git a/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index 6d959d983..1a5443391 100644
--- a/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -1,5 +1,5 @@
 ---
-title: 'ALT attribute not showing in <vtex.cmc:ProductImage zoom="on" />'
+title: "ALT attribute not showing in <vtex.cmc:ProductImage zoom='on' />"
 id: 4P1Eys9Q2WFddrMLQVDvM9
 status: DRAFT
 createdAt: 2022-02-17T13:08:53.295Z
diff --git a/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md
index 70f6ae23c..6d0c5ba44 100644
--- a/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: '[AMAZON] "La referencia a un objeto no es una instancia de un objeto"'
+title: "[AMAZON] 'La referencia a un objeto no es una instancia de un objeto'"
 id: 7xWXzfztp7b9I8KeBSzgST
 status: PUBLISHED
 createdAt: 2022-03-10T18:00:38.681Z
diff --git a/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md b/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md
index 5bd5ea551..e0d7afe1b 100644
--- a/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md
+++ b/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md
@@ -1,5 +1,5 @@
 ---
-title: '"Se ha producido un error al añadir información de seguimiento'
+title: "'Se ha producido un error al añadir información de seguimiento"
 id: 1gmlrPh9P1KbNI5NNXuImO
 status: PUBLISHED
 createdAt: 2023-02-08T18:38:55.699Z
diff --git a/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md b/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
index 981b5e1a3..c6639ec86 100644
--- a/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
+++ b/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: 'Las API "Quién vio también vio", "Quién vio también compró" y "Quién compró también compró" no siempre funcionan como se esperaba.'
+title: "Las API 'Quién vio también vio', 'Quién vio también compró' y 'Quién compró también compró' no siempre funcionan como se esperaba."
 id: KawgHAWqUlCvCGCAaHxDj
 status: PUBLISHED
 createdAt: 2022-12-07T12:32:13.613Z
diff --git a/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
index 3e3333649..e4cb3f993 100644
--- a/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
+++ b/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API de Attachents no permite "domainValues" nulos (y debería)'
+title: "La API de Attachents no permite 'domainValues' nulos (y debería)"
 id: 7KMb6nh0ulcWdEfz7USbPg
 status: PUBLISHED
 createdAt: 2023-09-11T19:02:51.514Z
diff --git a/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
index 577999bee..a1a4e56ce 100644
--- a/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
+++ b/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
@@ -1,5 +1,5 @@
 ---
-title: 'Registros de precios de auditoría que muestran información "desconocida".'
+title: "Registros de precios de auditoría que muestran información 'desconocida'."
 id: 7b8UDsiBo7VOHCN3pgcfd0
 status: PUBLISHED
 createdAt: 2023-07-05T18:51:22.120Z
diff --git a/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
index 6ca0c1abd..51db1f306 100644
--- a/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
+++ b/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API de sugerencia de autocompletar elimina el punto "." del nombre del producto'
+title: "La API de sugerencia de autocompletar elimina el punto '.' del nombre del producto"
 id: 55185IvERIwGQ3kH6H510O
 status: PUBLISHED
 createdAt: 2024-04-10T13:58:51.138Z
diff --git a/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
index 9af4be58c..3928b1a50 100644
--- a/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
+++ b/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -1,5 +1,5 @@
 ---
-title: 'El campo "disponibilidad" es incorrecto en la Simulación de Cumplimiento para productos sin stock o precio'
+title: "El campo 'disponibilidad' es incorrecto en la Simulación de Cumplimiento para productos sin stock o precio"
 id: 1k2zcLEN5vG6mnksLwEXxp
 status: PUBLISHED
 createdAt: 2023-10-04T14:22:53.519Z
diff --git a/docs/known-issues/es/aviseme-report-does-not-open.md b/docs/known-issues/es/aviseme-report-does-not-open.md
index 47c24b051..bddb9ff33 100644
--- a/docs/known-issues/es/aviseme-report-does-not-open.md
+++ b/docs/known-issues/es/aviseme-report-does-not-open.md
@@ -1,5 +1,5 @@
 ---
-title: 'Informe de "Avise-me" no se abre'
+title: "Informe de 'Avise-me' no se abre"
 id: 5jRrYk5Nm0uGSmoyeogIs2
 status: PUBLISHED
 createdAt: 2017-06-13T15:07:33.222Z
diff --git a/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index a96869244..91c692a06 100644
--- a/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -1,5 +1,5 @@
 ---
-title: '[B2W] Pedido "B2W directo" (FOB) integrando con transportista'
+title: "[B2W] Pedido 'B2W directo' (FOB) integrando con transportista"
 id: 20nA7vm1RFMhv7yhaJ43GG
 status: PUBLISHED
 createdAt: 2022-12-12T18:14:19.975Z
diff --git a/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md b/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md
index 43c4a0888..d1568290e 100644
--- a/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md
+++ b/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md
@@ -1,5 +1,5 @@
 ---
-title: '[B2W] Pedido con error "Parameter count mismatch'
+title: "[B2W] Pedido con error 'Parameter count mismatch"
 id: 6XhzSJrrHaEt85QseRdC3k
 status: PUBLISHED
 createdAt: 2023-03-22T19:32:10.011Z
diff --git a/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md b/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md
index 4306a0639..78efc86c6 100644
--- a/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md
+++ b/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md
@@ -1,5 +1,5 @@
 ---
-title: 'El botón "Atrás" no aparece en Mi Organización'
+title: "El botón 'Atrás' no aparece en Mi Organización"
 id: xzd2JVKP6jcTN0dGWwISB
 status: PUBLISHED
 createdAt: 2023-04-25T21:26:35.401Z
diff --git a/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md b/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
index c4ceb080b..b323f9555 100644
--- a/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
+++ b/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'El botón "Volver al sitio" lleva a gatewayCallback//Success en lugar de a la página placeOrder'
+title: "El botón 'Volver al sitio' lleva a gatewayCallback//Success en lugar de a la página placeOrder"
 id: 7Hp6yYCblhbhrN3jHHigUC
 status: PUBLISHED
 createdAt: 2023-04-10T15:18:58.986Z
diff --git a/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
index 006f8b930..b695afc57 100644
--- a/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
@@ -1,5 +1,5 @@
 ---
-title: 'Solicitud incorrecta al buscar términos con "%" directamente a través de la URL'
+title: "Solicitud incorrecta al buscar términos con '%' directamente a través de la URL"
 id: 3gdZ8egQRa4zcNRe2f5CbT
 status: PUBLISHED
 createdAt: 2023-03-21T22:51:46.273Z
diff --git a/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
index 6a5025db3..7e31240db 100644
--- a/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
+++ b/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -1,5 +1,5 @@
 ---
-title: 'Solicitud incorrecta al buscar términos con "#" mediante autocompletar'
+title: "Solicitud incorrecta al buscar términos con '#' mediante autocompletar"
 id: 18pMsxubB9eSPGlULAN35p
 status: PUBLISHED
 createdAt: 2024-02-06T20:07:52.739Z
diff --git a/docs/known-issues/es/bug-in-cart-with-promotion-when-splitting-item.md b/docs/known-issues/es/bug-in-cart-with-promotion-when-splitting-item.md
index 03429713c..4fc0d23ae 100644
--- a/docs/known-issues/es/bug-in-cart-with-promotion-when-splitting-item.md
+++ b/docs/known-issues/es/bug-in-cart-with-promotion-when-splitting-item.md
@@ -1,5 +1,5 @@
 ---
-title: 'Bug en el carrito con promoción al "splitar" item'
+title: "Bug en el carrito con promoción al 'splitar' item"
 id: 26EY5QcY4wcGm88okke8SY
 status: PUBLISHED
 createdAt: 2017-05-24T20:20:57.562Z
diff --git a/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index c275db7fe..dd81256fe 100644
--- a/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -1,5 +1,5 @@
 ---
-title: 'Botón "Cancelar" dentro de la página de MyCards no traducido al español'
+title: "Botón 'Cancelar' dentro de la página de MyCards no traducido al español"
 id: 5wIEEoF7gTLYlWnANxDZ7h
 status: PUBLISHED
 createdAt: 2022-02-24T13:18:00.062Z
diff --git a/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
index 09ee63f01..d8911a9a4 100644
--- a/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
+++ b/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -1,5 +1,5 @@
 ---
-title: 'Interfaz de usuario de la audiencia de la campaña cambiando "Diferente de" a "Igual a" con una colección'
+title: "Interfaz de usuario de la audiencia de la campaña cambiando 'Diferente de' a 'Igual a' con una colección"
 id: 6IkWioZ9WRgg1DFEMdnthB
 status: PUBLISHED
 createdAt: 2023-08-15T15:12:54.580Z
diff --git a/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
index cc59f134e..55c65bde1 100644
--- a/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
+++ b/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -1,5 +1,5 @@
 ---
-title: 'Carro creado a partir de una opción "pedir de nuevo" en Mis pedidos, el correo electrónico del cliente no se está colocando como se esperaba en el orderForm'
+title: "Carro creado a partir de una opción 'pedir de nuevo' en Mis pedidos, el correo electrónico del cliente no se está colocando como se esperaba en el orderForm"
 id: 6dDhkaIhquOqaDuNkVZuln
 status: PUBLISHED
 createdAt: 2023-12-04T22:41:21.385Z
diff --git a/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md b/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
index 04b1cb66e..fbbe47039 100644
--- a/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
+++ b/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
@@ -1,5 +1,5 @@
 ---
-title: 'La cesta con artículos muestra el mensaje "cesta vacía" mientras la pantalla aún se está cargando.'
+title: "La cesta con artículos muestra el mensaje 'cesta vacía' mientras la pantalla aún se está cargando."
 id: 4oAiVz7fJL9vPkpPFEGyBT
 status: PUBLISHED
 createdAt: 2023-03-09T22:42:06.855Z
diff --git a/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md b/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
index 250e1614e..3657f0822 100644
--- a/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
+++ b/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
@@ -1,5 +1,5 @@
 ---
-title: 'La exportación de catálogos no muestra los canales de venta cuando se marca "ninguno".'
+title: "La exportación de catálogos no muestra los canales de venta cuando se marca 'ninguno'."
 id: 10Bozz8ai3fAvu1m9Ex2Gk
 status: PUBLISHED
 createdAt: 2022-12-23T13:38:32.114Z
diff --git a/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
index 502e36f05..fa834d4ca 100644
--- a/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error de cálculo de la sección "total" del informe de indexación del catálogo'
+title: "Error de cálculo de la sección 'total' del informe de indexación del catálogo"
 id: 6TJXux104P2c0mruo5vlEn
 status: PUBLISHED
 createdAt: 2022-02-25T11:39:42.098Z
diff --git a/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md b/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md
index 651b611af..c769a5392 100644
--- a/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md
+++ b/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedidos de Centauro con error "Pedido sin el campo: "paquetes'
+title: "Pedidos de Centauro con error 'Pedido sin el campo: 'paquetes"
 id: 1HMhinuVlggWwQZPuNchiX
 status: PUBLISHED
 createdAt: 2022-06-24T13:10:45.752Z
diff --git a/docs/known-issues/es/centauro-to-implement-centauro-envios.md b/docs/known-issues/es/centauro-to-implement-centauro-envios.md
index 3edc8fbe6..a9d98292d 100644
--- a/docs/known-issues/es/centauro-to-implement-centauro-envios.md
+++ b/docs/known-issues/es/centauro-to-implement-centauro-envios.md
@@ -1,5 +1,5 @@
 ---
-title: '[Centauro] Implementar "Centauro Envios"'
+title: "[Centauro] Implementar 'Centauro Envios'"
 id: 1xkjyfVfT8Fs2as9mbNjj3
 status: PUBLISHED
 createdAt: 2022-11-25T21:23:23.849Z
diff --git a/docs/known-issues/es/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md b/docs/known-issues/es/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
index c0f7fcfe7..fa7bd6f42 100644
--- a/docs/known-issues/es/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
+++ b/docs/known-issues/es/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cambios en la página de "mi cuenta" no aparecen inmediatamente en el dominio "vtexcommercestable.com.br"'
+title: "Cambios en la página de 'mi cuenta' no aparecen inmediatamente en el dominio 'vtexcommercestable.com.br'"
 id: iUmuXOYVj97sTpqQnJqAU
 status: PUBLISHED
 createdAt: 2019-03-19T13:23:11.941Z
diff --git a/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md b/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md
index aead25ad0..9c674f0cb 100644
--- a/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md
+++ b/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md
@@ -1,5 +1,5 @@
 ---
-title: 'La casilla "Requiere autenticación" no funciona en el módulo de páginas'
+title: "La casilla 'Requiere autenticación' no funciona en el módulo de páginas"
 id: 6nKuqSmk7JZgdaAysNYls3
 status: PUBLISHED
 createdAt: 2022-05-11T21:25:07.700Z
diff --git a/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md b/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
index a040eb2d0..ff2c52060 100644
--- a/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
+++ b/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout payment split may generate incorrect information in the "paymentData" of orders (NO-PAYMENT)'
+title: "Checkout payment split may generate incorrect information in the 'paymentData' of orders (NO-PAYMENT)"
 id: 1bZ5H0T0isc0DUtkIb38sQ
 status: PUBLISHED
 createdAt: 2022-01-24T20:37:23.861Z
diff --git a/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
index ed5be0f20..9ddb666f2 100644
--- a/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
+++ b/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -1,5 +1,5 @@
 ---
-title: 'La simulación de pago devuelve el valor 0 en el campo "slas.tax" para los impuestos del porcentaje de envío.'
+title: "La simulación de pago devuelve el valor 0 en el campo 'slas.tax' para los impuestos del porcentaje de envío."
 id: 54Mtsj8EKuo0SaQCoWyYzj
 status: PUBLISHED
 createdAt: 2024-04-05T18:55:32.183Z
diff --git a/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
index 937abbf58..51f9d4794 100644
--- a/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
+++ b/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -1,5 +1,5 @@
 ---
-title: 'La interfaz de usuario de la caja no utiliza automáticamente el "envío reducido" para los artículos sin métodos de envío comunes.'
+title: "La interfaz de usuario de la caja no utiliza automáticamente el 'envío reducido' para los artículos sin métodos de envío comunes."
 id: 2LXp8VCAay7Ic9MBfbtirT
 status: PUBLISHED
 createdAt: 2024-04-02T15:27:23.003Z
diff --git a/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md b/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
index a69459ae8..a85e9fd69 100644
--- a/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
+++ b/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'La interfaz de pago deselecciona la opción "Programar todo" después de actualizar la página.'
+title: "La interfaz de pago deselecciona la opción 'Programar todo' después de actualizar la página."
 id: 28TIselp0EzU3iSD4kLJgX
 status: PUBLISHED
 createdAt: 2023-04-04T21:08:55.937Z
diff --git a/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index 11c46ec8d..3ba91f134 100644
--- a/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -1,5 +1,5 @@
 ---
-title: 'El campo de las colecciones siempre aparece como "Igual a" en el formulario de audiencia de la campaña'
+title: "El campo de las colecciones siempre aparece como 'Igual a' en el formulario de audiencia de la campaña"
 id: 2NPEh7LZkrpO0gf802I7HZ
 status: PUBLISHED
 createdAt: 2022-11-11T21:18:53.386Z
diff --git a/docs/known-issues/es/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md b/docs/known-issues/es/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md
index 7f3d49420..45f5f4c3f 100644
--- a/docs/known-issues/es/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md
+++ b/docs/known-issues/es/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md
@@ -1,5 +1,5 @@
 ---
-title: '"Confirmar acción" está indisponible en Catálogo, Sellers, CMS y Tarjeta de regalo por Google Chrome'
+title: "'Confirmar acción' está indisponible en Catálogo, Sellers, CMS y Tarjeta de regalo por Google Chrome"
 id: 5UzVaWa63dPwPlbK3n2AH5
 status: PUBLISHED
 createdAt: 2021-07-27T22:29:39.402Z
diff --git a/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md b/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
index fa7d1053f..aace7bd6d 100644
--- a/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
+++ b/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
@@ -1,5 +1,5 @@
 ---
-title: 'Conflictos con los filtros de precios y "isAvailablePerSalesChannel" en las búsquedas (Portal y Búsqueda) (de nuevo)'
+title: "Conflictos con los filtros de precios y 'isAvailablePerSalesChannel' en las búsquedas (Portal y Búsqueda) (de nuevo)"
 id: 6dLv8lP69Em68ooydjaPzY
 status: PUBLISHED
 createdAt: 2022-02-24T13:24:42.299Z
diff --git a/docs/known-issues/es/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md b/docs/known-issues/es/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
index 8c13715d7..060fa3efe 100644
--- a/docs/known-issues/es/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
+++ b/docs/known-issues/es/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
@@ -1,5 +1,5 @@
 ---
-title: 'La creación de "custom fields" para "custom data" convierte los IDs a letras minúsculas'
+title: "La creación de 'custom fields' para 'custom data' convierte los IDs a letras minúsculas"
 id: 6oCXPldEYkC9HG1fw3G3RL
 status: PUBLISHED
 createdAt: 2019-02-19T18:52:45.049Z
diff --git a/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md b/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md
index 899829d0a..779195df6 100644
--- a/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md
+++ b/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md
@@ -1,5 +1,5 @@
 ---
-title: 'Actualización del valor del crédito del cliente "Total debido" según la paginación'
+title: "Actualización del valor del crédito del cliente 'Total debido' según la paginación"
 id: 6faMqwY8yHsIdYjkwTgCCQ
 status: PUBLISHED
 createdAt: 2022-03-27T20:52:29.371Z
diff --git a/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
index 71e44b14f..6074946e3 100644
--- a/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
+++ b/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -1,5 +1,5 @@
 ---
-title: 'Se pierde la información del cliente cuando tiene algún pedido con "profileErrorOnLoading"'
+title: "Se pierde la información del cliente cuando tiene algún pedido con 'profileErrorOnLoading'"
 id: 7B0eutLBOCKOun4iwALVpq
 status: PUBLISHED
 createdAt: 2023-06-27T12:51:33.790Z
diff --git a/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md b/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
index bd2bd0393..c755fbc9f 100644
--- a/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
+++ b/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
@@ -1,5 +1,5 @@
 ---
-title: '[Dafiti] Pedidos que se encuentran en "A la espera de autorización de envío" en VTEX, pero que siguen en "pago_pendiente" en Dafiti.'
+title: "[Dafiti] Pedidos que se encuentran en 'A la espera de autorización de envío' en VTEX, pero que siguen en 'pago_pendiente' en Dafiti."
 id: 6XbDr2QRAtk0bVAeywagjq
 status: PUBLISHED
 createdAt: 2022-12-20T13:14:31.368Z
diff --git a/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md b/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
index abb9e9a98..61c434b99 100644
--- a/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
+++ b/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
@@ -1,5 +1,5 @@
 ---
-title: 'La transacción DecidirV1 fue "reprocesada" después de algunos reintentos de autorización'
+title: "La transacción DecidirV1 fue 'reprocesada' después de algunos reintentos de autorización"
 id: 2fxfg1IlnFUxAjo9E47HPq
 status: PUBLISHED
 createdAt: 2022-03-03T21:19:22.471Z
diff --git a/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md b/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
index 32ec58f5e..ce42ea4fa 100644
--- a/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
+++ b/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'Retraso en la tramitación de la póliza de envío (bloqueada en estado de "tramitación")'
+title: "Retraso en la tramitación de la póliza de envío (bloqueada en estado de 'tramitación')"
 id: 5wl2TdIbyQeCF8eoo5oYKl
 status: PUBLISHED
 createdAt: 2022-05-17T17:26:58.778Z
diff --git a/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md b/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
index e88109112..8cf8cc395 100644
--- a/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
+++ b/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
@@ -1,5 +1,5 @@
 ---
-title: 'Valor divergente al mezclar la configuración "paymentSystemToCheckFirstInstallment" y partidas divididas'
+title: "Valor divergente al mezclar la configuración 'paymentSystemToCheckFirstInstallment' y partidas divididas"
 id: 3h2o69kTBqFdQlzhED2kMN
 status: PUBLISHED
 createdAt: 2023-03-07T18:35:31.215Z
diff --git a/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index 9b47ce16c..40122dd45 100644
--- a/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "Categoría XXX no encontrada en el mapeo del nodo de navegación para la especificación del departamento de SKU, elija una categoría global más específica" persistente'
+title: "Erro 'Categoría XXX no encontrada en el mapeo del nodo de navegación para la especificación del departamento de SKU, elija una categoría global más específica' persistente"
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
diff --git a/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index f476af950..d7eefc4e3 100644
--- a/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "¡no se pueden crear criterios de búsqueda! error: el filtro ya existe: "brandId"" al crear una promoción que excluye más de 1 marca.'
+title: "Error '¡no se pueden crear criterios de búsqueda! error: el filtro ya existe: 'brandId'' al crear una promoción que excluye más de 1 marca."
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
diff --git a/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md b/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
index 644b77144..29ea40716 100644
--- a/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
+++ b/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error al generar la orden de suscripción ""El mismo artículo no puede tener más de un ANS seleccionado"'
+title: "Error al generar la orden de suscripción ''El mismo artículo no puede tener más de un ANS seleccionado'"
 id: 2aBMa8ncalkqSm2s868i1q
 status: PUBLISHED
 createdAt: 2022-09-29T13:31:57.984Z
diff --git a/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
index e4783987d..fce2ca31e 100644
--- a/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error en operaciones de reembolso y captura con Payout Split - "Valor en destinatarios * es diferente al valor de la operación *."'
+title: "Error en operaciones de reembolso y captura con Payout Split - 'Valor en destinatarios * es diferente al valor de la operación *.'"
 id: 3Wo9ltN7Ju0ZqVLAQZcd7m
 status: PUBLISHED
 createdAt: 2023-08-23T13:57:20.424Z
diff --git a/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
index 040b96997..1927d63ec 100644
--- a/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
+++ b/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error en el reembolso - "El valor no puede ser nulo. Nombre del parámetro: valor"'
+title: "Error en el reembolso - 'El valor no puede ser nulo. Nombre del parámetro: valor'"
 id: 6TZFYB9zb02oMoN5IJMxR3
 status: PUBLISHED
 createdAt: 2024-06-13T18:49:16.797Z
diff --git a/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md b/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md
index 6bf234373..77c5c2019 100644
--- a/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md
+++ b/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error al integrar sku "El campo no puede ser nulo" - Magalu'
+title: "Error al integrar sku 'El campo no puede ser nulo' - Magalu"
 id: 3SYlRr6XVrl7T3Uw646MkE
 status: PUBLISHED
 createdAt: 2022-08-19T21:01:40.357Z
diff --git a/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
index ccfcbf2a9..d3639c5c8 100644
--- a/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
+++ b/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -1,5 +1,5 @@
 ---
-title: 'Se produce un error al intentar realizar una búsqueda utilizando el campo "Todos" en VTEX CRM'
+title: "Se produce un error al intentar realizar una búsqueda utilizando el campo 'Todos' en VTEX CRM"
 id: 1OKMTJuUZx6mnDmYW3MBjP
 status: PUBLISHED
 createdAt: 2023-10-25T18:46:48.120Z
diff --git a/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
index a0e2f3cce..2f06bb6d9 100644
--- a/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
+++ b/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "Algo ha ido mal. Por favor, inténtelo de nuevo" al añadir imágenes a través del Editor de Sitios.'
+title: "Error 'Algo ha ido mal. Por favor, inténtelo de nuevo' al añadir imágenes a través del Editor de Sitios."
 id: r3QVP1kp8HApP83bOi6t9
 status: PUBLISHED
 createdAt: 2023-11-07T22:33:02.296Z
diff --git a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index 021774453..9f85ee192 100644
--- a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -1,5 +1,5 @@
 ---
-title: "Al exportar imágenes SKU para cuentas que empiezan por 'h','t' o 'p' se corta este carácter en las filas "URL de la imagen"."
+title: "Al exportar imágenes SKU para cuentas que empiezan por 'h','t' o 'p' se corta este carácter en las filas "URL de la imagen'."
 id: 1IZdnE8IGwkBlbcFhjLrzn
 status: PUBLISHED
 createdAt: 2023-10-13T15:20:49.703Z
diff --git a/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md b/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md
index 0fa97a6a7..4edc07ab1 100644
--- a/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md
+++ b/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md
@@ -1,5 +1,5 @@
 ---
-title: 'ey "Enviar Kit:" no está registrando un cambio en la Tarjeta'
+title: "ey 'Enviar Kit:' no está registrando un cambio en la Tarjeta"
 id: 4J1SynfbrQqXpSIcveAMxJ
 status: PUBLISHED
 createdAt: 2022-06-14T11:56:12.170Z
diff --git a/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
index 3edece709..128c01daa 100644
--- a/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
+++ b/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -1,5 +1,5 @@
 ---
-title: 'Si no se añaden los datos en el paso "entregar en otra dirección", desaparece el botón "ir al pago".'
+title: "Si no se añaden los datos en el paso 'entregar en otra dirección', desaparece el botón 'ir al pago'."
 id: cdZO8gGXDB1JZSj42AnVh
 status: PUBLISHED
 createdAt: 2022-01-24T21:42:52.750Z
diff --git a/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index 9e397f9ce..1c4e7f40e 100644
--- a/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -1,5 +1,5 @@
 ---
-title: 'El campo "Cambios y devoluciones" no se actualiza en la interfaz de usuario de gestión de vendedores después de guardar.'
+title: "El campo 'Cambios y devoluciones' no se actualiza en la interfaz de usuario de gestión de vendedores después de guardar."
 id: 1z8LrsbGk5B2ejZ1PV9vaB
 status: PUBLISHED
 createdAt: 2022-11-01T17:47:30.359Z
diff --git a/docs/known-issues/es/field-reference-always-set-as-null.md b/docs/known-issues/es/field-reference-always-set-as-null.md
index 99b4f0ca7..0fff7a2fb 100644
--- a/docs/known-issues/es/field-reference-always-set-as-null.md
+++ b/docs/known-issues/es/field-reference-always-set-as-null.md
@@ -1,5 +1,5 @@
 ---
-title: 'El campo "referencia" siempre se establece como null'
+title: "El campo 'referencia' siempre se establece como null"
 id: 6Tq4zip0lfUm7vVJdwfZWx
 status: PUBLISHED
 createdAt: 2023-04-26T22:31:38.892Z
diff --git a/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
index fe472dd0d..f59d3f974 100644
--- a/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
+++ b/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -1,5 +1,5 @@
 ---
-title: 'El filtro "productClusterIds" es sobrescrito por "productClusterNames" al aplicar filtros adicionales'
+title: "El filtro 'productClusterIds' es sobrescrito por 'productClusterNames' al aplicar filtros adicionales"
 id: 3d4BIZQBZgeK3eKwT8B1PZ
 status: PUBLISHED
 createdAt: 2023-09-13T22:42:57.138Z
diff --git a/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md b/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
index 6b4b5452a..de51c46f2 100644
--- a/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
+++ b/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
@@ -1,5 +1,5 @@
 ---
-title: 'Filtrar productos por "Tienda" en la administración del catálogo puede mostrar una cantidad incorrecta de resultados.'
+title: "Filtrar productos por 'Tienda' en la administración del catálogo puede mostrar una cantidad incorrecta de resultados."
 id: E38Y6a81l7QNtrmh2I2id
 status: PUBLISHED
 createdAt: 2023-02-17T16:01:30.420Z
diff --git a/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md b/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
index f57cce2dc..42b3ef5a9 100644
--- a/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
+++ b/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
@@ -1,5 +1,5 @@
 ---
-title: 'La primera búsqueda en una tienda no se considera en la IU "últimas búsquedas"'
+title: "La primera búsqueda en una tienda no se considera en la IU 'últimas búsquedas'"
 id: 7mc9vRE92VGauQmRaK6NnU
 status: PUBLISHED
 createdAt: 2022-05-04T17:08:25.235Z
diff --git a/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md b/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
index d147b3de1..04b0ddfe1 100644
--- a/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
+++ b/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: 'La bandera "Aplicar el descuento sólo a la opción de envío más barata" no funciona como se esperaba'
+title: "La bandera 'Aplicar el descuento sólo a la opción de envío más barata' no funciona como se esperaba"
 id: 15irjH6rNkHhkBeRNn9RUI
 status: PUBLISHED
 createdAt: 2022-10-05T18:01:57.821Z
diff --git a/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index 9e4e89b9e..53655f69b 100644
--- a/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -1,5 +1,5 @@
 ---
-title: 'El mercado externo FOB integra un pedido (código Erro: "FMT010")'
+title: "El mercado externo FOB integra un pedido (código Erro: 'FMT010')"
 id: 3qzV4zJRkPIwQnAZuK5dWu
 status: PUBLISHED
 createdAt: 2022-02-25T16:33:49.641Z
diff --git a/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 7d7944773..633370649 100644
--- a/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API "Obtener todas las sugerencias de SKU" no mantiene el mismo orden de SKU al cambiar los límites.'
+title: "La API 'Obtener todas las sugerencias de SKU' no mantiene el mismo orden de SKU al cambiar los límites."
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
diff --git a/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
index 2671bb99b..552b2c0aa 100644
--- a/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
@@ -1,5 +1,5 @@
 ---
-title: 'GET Product by Refid Devuelve "Null" cuando no se encuentra'
+title: "GET Product by Refid Devuelve 'Null' cuando no se encuentra"
 id: 6yiM9gJT5DB77pZSBNfGZ3
 status: PUBLISHED
 createdAt: 2023-05-16T19:35:46.743Z
diff --git a/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index ec14102eb..441dd07db 100644
--- a/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -1,5 +1,5 @@
 ---
-title: 'Gift Card hub está añadiendo una barra invertida extra ("/") al llamar a los proveedores.'
+title: "Gift Card hub está añadiendo una barra invertida extra ('/') al llamar a los proveedores."
 id: 2ZstMKKGUbrdXGuhS2Rr1f
 status: PUBLISHED
 createdAt: 2022-09-30T21:07:47.856Z
diff --git a/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
index 3052fe59e..cfb609c89 100644
--- a/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
+++ b/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -1,5 +1,5 @@
 ---
-title: 'Tarjeta regalo - No devuelve los campos "caption" y "relationName" cuando hacemos una petición get.'
+title: "Tarjeta regalo - No devuelve los campos 'caption' y 'relationName' cuando hacemos una petición get."
 id: 2nh2Cc3Hc2Zm0b1INtwDep
 status: PUBLISHED
 createdAt: 2023-06-23T19:33:35.774Z
diff --git a/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md b/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
index da9f34756..a55cdd575 100644
--- a/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
+++ b/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'El HUB de tarjetas de regalo establece "R$" como moneda automática en la interfaz de usuario'
+title: "El HUB de tarjetas de regalo establece 'R$' como moneda automática en la interfaz de usuario"
 id: 2ODtc4t1GSo3iUjT9Gk0uk
 status: PUBLISHED
 createdAt: 2022-11-03T12:57:31.895Z
diff --git a/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md b/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
index 429fdbfdf..664f2dba2 100644
--- a/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
+++ b/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
@@ -1,5 +1,5 @@
 ---
-title: 'El botón "Ir al pago" no funciona en la división de entrega cuando se cambia entre las opciones de Entrega y Recogida.'
+title: "El botón 'Ir al pago' no funciona en la división de entrega cuando se cambia entre las opciones de Entrega y Recogida."
 id: 4VDxpsWl6N0SjriaqUtXG9
 status: PUBLISHED
 createdAt: 2023-02-17T18:03:49.526Z
diff --git a/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md b/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
index ae68eef63..60f02fea8 100644
--- a/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
+++ b/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
@@ -1,5 +1,5 @@
 ---
-title: '"¿Cuántas veces se aplicará su beneficio en su tienda?" Guardar incorrectamente en la interfaz del formulario de promoción'
+title: "'¿Cuántas veces se aplicará su beneficio en su tienda?' Guardar incorrectamente en la interfaz del formulario de promoción"
 id: 6vT0rYIry3cGx1nG5BPkmx
 status: PUBLISHED
 createdAt: 2022-06-28T19:23:30.074Z
diff --git a/docs/known-issues/es/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md b/docs/known-issues/es/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
index 2b7768487..5daf0b221 100644
--- a/docs/known-issues/es/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
+++ b/docs/known-issues/es/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'El enlace "No sé mi código postal" en la página de creación de listas de bodas redirecciona el usuario a la propia página de creación de listas de bodas'
+title: "El enlace 'No sé mi código postal' en la página de creación de listas de bodas redirecciona el usuario a la propia página de creación de listas de bodas"
 id: 59Go6zy62I2iwACQqW8qmA
 status: PUBLISHED
 createdAt: 2018-02-20T22:07:31.331Z
diff --git a/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
index 50ffc468f..2969dd2da 100644
--- a/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
+++ b/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -1,5 +1,5 @@
 ---
-title: 'La colección de importación sólo acepta el orden de los productos si la importación se realiza basándose en "skuId"'
+title: "La colección de importación sólo acepta el orden de los productos si la importación se realiza basándose en 'skuId'"
 id: 7vXi2bDVyGHSMLluQi2ZWZ
 status: PUBLISHED
 createdAt: 2023-12-15T16:35:11.545Z
diff --git a/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md b/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md
index 9c6a9913e..8de1965c7 100644
--- a/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md
+++ b/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md
@@ -1,5 +1,5 @@
 ---
-title: 'Formato de dirección incorrecto en las direcciones de facturación de "Mis tarjetas".'
+title: "Formato de dirección incorrecto en las direcciones de facturación de 'Mis tarjetas'."
 id: 25QxVtMOazrxugHZqFrhSG
 status: PUBLISHED
 createdAt: 2023-04-17T17:40:24.795Z
diff --git a/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
index 937142821..4190676fb 100644
--- a/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cálculo de reembolso incorrecto en Payout Split - "Valor en destinatarios * es diferente al valor de operación *".'
+title: "Cálculo de reembolso incorrecto en Payout Split - 'Valor en destinatarios * es diferente al valor de operación *'."
 id: 7Fxtwnntpmi0DrUD5a603W
 status: PUBLISHED
 createdAt: 2024-07-29T15:07:07.716Z
diff --git a/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
index 7950ea2e9..f4644de90 100644
--- a/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
+++ b/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API Insertar Archivo SKU no acepta URLs de servidores que requieren "Agentes de Usuario".'
+title: "La API Insertar Archivo SKU no acepta URLs de servidores que requieren 'Agentes de Usuario'."
 id: 5Z1PmRXyW78mohsKTMQfzj
 status: PUBLISHED
 createdAt: 2024-07-22T19:49:14.140Z
diff --git a/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md b/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
index b33808a4b..3683fecc6 100644
--- a/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
+++ b/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
@@ -1,5 +1,5 @@
 ---
-title: 'El menú desplegable de las cuotas en la interfaz de compra está "suelto" cuando se desplaza la pantalla.'
+title: "El menú desplegable de las cuotas en la interfaz de compra está 'suelto' cuando se desplaza la pantalla."
 id: 0bbx1aDD7qw3DmaeMOebp
 status: PUBLISHED
 createdAt: 2022-03-10T20:07:05.251Z
diff --git a/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
index 7ad921710..4f147ee39 100644
--- a/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
+++ b/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -1,5 +1,5 @@
 ---
-title: 'Mensaje "Código postal no válido" en la interfaz de usuario de la caja cuando la dirección está en las direcciones disponibles con un país diferente.'
+title: "Mensaje 'Código postal no válido' en la interfaz de usuario de la caja cuando la dirección está en las direcciones disponibles con un país diferente."
 id: 4VggIx4xWPNW6OBIrQ0js4
 status: PUBLISHED
 createdAt: 2024-06-21T17:08:59.860Z
diff --git a/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
index f0f03c11d..a7abf1cae 100644
--- a/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
+++ b/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -1,5 +1,5 @@
 ---
-title: 'Los caracteres invisibles en los nombres de categoría provocan errores de "página no encontrada".'
+title: "Los caracteres invisibles en los nombres de categoría provocan errores de 'página no encontrada'."
 id: 4np2BZUF1EmlLmV0KTpnrf
 status: PUBLISHED
 createdAt: 2024-07-05T13:11:13.031Z
diff --git a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
index 9721b4d0d..4e6dc6108 100644
--- a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
+++ b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'No es posible guardar algunas direcciones de Argentina en "Mi cuenta"'
+title: "No es posible guardar algunas direcciones de Argentina en 'Mi cuenta'"
 id: 6kWZsPNLSDYgmJPDsQOO2w
 status: PUBLISHED
 createdAt: 2022-05-05T14:57:01.624Z
diff --git a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
index f95c36cd7..614290742 100644
--- a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
+++ b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'No es posible guardar algunas direcciones de Chile en "Mi cuenta"'
+title: "No es posible guardar algunas direcciones de Chile en 'Mi cuenta'"
 id: 6DLPSH4eJY0Hbgtc5iGh21
 status: PUBLISHED
 createdAt: 2022-02-24T14:51:08.104Z
diff --git a/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md b/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
index eb013e829..33a28fd59 100644
--- a/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
+++ b/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
@@ -1,5 +1,5 @@
 ---
-title: '"Texto grande indexado" y "Texto indexado" no se modifican con la importación de la especificación'
+title: "'Texto grande indexado' y 'Texto indexado' no se modifican con la importación de la especificación"
 id: 5ty5q8AfOROtCc8GegzZbd
 status: PUBLISHED
 createdAt: 2022-04-22T17:12:36.962Z
diff --git a/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
index 4d4a5f9ff..031adcb9d 100644
--- a/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
+++ b/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -1,5 +1,5 @@
 ---
-title: 'Lean shipping provoca "Algo salió mal" tras cambiar los puntos de recogida'
+title: "Lean shipping provoca 'Algo salió mal' tras cambiar los puntos de recogida"
 id: 45jQODtjZ4vLXniNJIlQZc
 status: PUBLISHED
 createdAt: 2024-06-20T21:11:53.067Z
diff --git a/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
index d05743498..5eed0a613 100644
--- a/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
+++ b/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
@@ -1,5 +1,5 @@
 ---
-title: 'El botón "eliminar" de la interfaz de usuario del catálogo heredado no funciona'
+title: "El botón 'eliminar' de la interfaz de usuario del catálogo heredado no funciona"
 id: 2soNSJfiQMZcxlpW6jT2FR
 status: PUBLISHED
 createdAt: 2022-01-23T02:51:17.884Z
diff --git a/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index eb7923699..e757008ef 100644
--- a/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -1,5 +1,5 @@
 ---
-title: 'El enlace "¿Por qué rellenar la Categoría Global VTEX?" en la configuración de la categoría sólo funciona abriéndose en una nueva pestaña'
+title: "El enlace '¿Por qué rellenar la Categoría Global VTEX?' en la configuración de la categoría sólo funciona abriéndose en una nueva pestaña"
 id: 3u7aq2otUovQbO98lzjbus
 status: PUBLISHED
 createdAt: 2022-03-16T17:59:14.355Z
diff --git a/docs/known-issues/es/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md b/docs/known-issues/es/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
index 942f34a11..cf86629b7 100644
--- a/docs/known-issues/es/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
+++ b/docs/known-issues/es/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
@@ -1,5 +1,5 @@
 ---
-title: '"Lista de compras" en el informe de lista de regalos no aplica el filtro correctamente en el Gestión de Pedidos'
+title: "'Lista de compras' en el informe de lista de regalos no aplica el filtro correctamente en el Gestión de Pedidos"
 id: 5p7nqrzUqIK88cYkkOqMMG
 status: PUBLISHED
 createdAt: 2017-04-03T19:36:10.117Z
diff --git a/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md b/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md
index f00e2610c..93a80d833 100644
--- a/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md
+++ b/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: 'El permiso de "acceso total al inventario de logística" no funcionó como se esperaba'
+title: "El permiso de 'acceso total al inventario de logística' no funcionó como se esperaba"
 id: 6F11U5C6cULOeJ3Jo5AgAc
 status: PUBLISHED
 createdAt: 2022-04-27T14:16:03.358Z
diff --git a/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 022edfad8..a1e9b149a 100644
--- a/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: ' [Magalu] Pedido con error "Referencia de objeto no establecida a una instancia de un objeto"'
+title: " [Magalu] Pedido con error 'Referencia de objeto no establecida a una instancia de un objeto'"
 id: 6758qSnWuXR6TWQ1mlKOxs
 status: PUBLISHED
 createdAt: 2022-11-29T17:45:30.636Z
diff --git a/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md b/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
index f01c16594..bad604b94 100644
--- a/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
+++ b/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
@@ -1,5 +1,5 @@
 ---
-title: '[Magazine Luiza] Pedido FOB integrado con entrega "Convencional'
+title: "[Magazine Luiza] Pedido FOB integrado con entrega 'Convencional"
 id: 74uM19UXEopXguM6m0JbOL
 status: PUBLISHED
 createdAt: 2022-12-23T12:40:05.775Z
diff --git a/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index aa81ecf7a..270196332 100644
--- a/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: '[Revista Luiza] Pedido con error "Referencia de objeto no establecida a una instancia de un objeto"'
+title: "[Revista Luiza] Pedido con error 'Referencia de objeto no establecida a una instancia de un objeto'"
 id: 72w2GWNOlosoOHhs1ip4dl
 status: PUBLISHED
 createdAt: 2023-03-23T20:11:55.897Z
diff --git a/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md b/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
index 66d4fd427..f9c6b584e 100644
--- a/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
+++ b/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
@@ -1,5 +1,5 @@
 ---
-title: 'La cuenta principal está siendo seleccionada como "Merchant.Name" en el entorno de la subcuenta.'
+title: "La cuenta principal está siendo seleccionada como 'Merchant.Name' en el entorno de la subcuenta."
 id: 51coXFBM2wtrJukH3oRESy
 status: PUBLISHED
 createdAt: 2023-03-29T20:54:19.877Z
diff --git a/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
index 8f08ca096..d5b03dd96 100644
--- a/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
+++ b/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API recibe varios SKU y devuelve "Invalid sellerId".'
+title: "La API recibe varios SKU y devuelve 'Invalid sellerId'."
 id: 60aL2Chds0Jo3m6XMkxmnG
 status: PUBLISHED
 createdAt: 2023-10-17T16:26:27.980Z
diff --git a/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
index 23bf232e3..7eebfd98c 100644
--- a/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
+++ b/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -1,5 +1,5 @@
 ---
-title: '"número máximo de artículos elegibles para cada cesta" + más por menos aplica un descuento incorrecto al utilizar el mismo artículo.'
+title: "'número máximo de artículos elegibles para cada cesta' + más por menos aplica un descuento incorrecto al utilizar el mismo artículo."
 id: gWIMhi9RCv9BE1RvV6GiM
 status: PUBLISHED
 createdAt: 2024-07-30T17:14:36.972Z
diff --git a/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
index f8db2cf34..04fba0158 100644
--- a/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
+++ b/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -1,5 +1,5 @@
 ---
-title: 'MDv2 devuelve el error "504 Gateway Timeout" cuando intentamos actualizar un documento pasando un símbolo o carácter especial.'
+title: "MDv2 devuelve el error '504 Gateway Timeout' cuando intentamos actualizar un documento pasando un símbolo o carácter especial."
 id: 6GP5QBWyIAir2oKe08giT2
 status: PUBLISHED
 createdAt: 2023-08-09T13:04:34.819Z
diff --git a/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md b/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
index 17b5e2cd4..a196f6ee9 100644
--- a/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
+++ b/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
@@ -1,5 +1,5 @@
 ---
-title: '[Meli] Error de integración de sku "La cadena de entrada no estaba en un formato correcto"'
+title: "[Meli] Error de integración de sku 'La cadena de entrada no estaba en un formato correcto'"
 id: 2NCm4vLyb1juIuIGMaB048
 status: PUBLISHED
 createdAt: 2022-09-27T21:05:39.320Z
diff --git a/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
index 4362376ba..13eeda84b 100644
--- a/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
+++ b/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -1,5 +1,5 @@
 ---
-title: 'La integración MELI está recibiendo errores de MELI "429 demasiadas peticiones"'
+title: "La integración MELI está recibiendo errores de MELI '429 demasiadas peticiones'"
 id: 1e4g9nzZFyanywmLbSHq4D
 status: PUBLISHED
 createdAt: 2023-08-03T10:47:41.602Z
diff --git a/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
index 5106b85bc..b6a30624e 100644
--- a/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -1,5 +1,5 @@
 ---
-title: 'Integración MELI Códigos postales "11111" Meli - Lima/Perú'
+title: "Integración MELI Códigos postales '11111' Meli - Lima/Perú"
 id: 7ICcek0NOUczgtA65CaZk5
 status: PUBLISHED
 createdAt: 2023-05-16T17:50:38.417Z
diff --git a/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md b/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
index 31a20ba0c..daa25e89a 100644
--- a/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
+++ b/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
@@ -1,5 +1,5 @@
 ---
-title: '[Meli] Integración SKU con error "Object reference not set to an instance of an object".'
+title: "[Meli] Integración SKU con error 'Object reference not set to an instance of an object'."
 id: 3GNnAidwvASTP223ncqsiV
 status: PUBLISHED
 createdAt: 2022-12-07T11:59:25.793Z
diff --git a/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
index f5941d2fc..29f44a94f 100644
--- a/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
+++ b/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -1,5 +1,5 @@
 ---
-title: 'Las reglas de comercialización no funcionan para la faceta "productClusterIds".'
+title: "Las reglas de comercialización no funcionan para la faceta 'productClusterIds'."
 id: 6sLODMgjuoyJD52uc0DBW1
 status: PUBLISHED
 createdAt: 2024-07-09T00:02:40.930Z
diff --git a/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md b/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md
index 9552c1765..83b49107e 100644
--- a/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md
+++ b/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md
@@ -1,5 +1,5 @@
 ---
-title: 'El mensaje "El valor de la carga ha cambiado" se muestra incorrectamente'
+title: "El mensaje 'El valor de la carga ha cambiado' se muestra incorrectamente"
 id: 6ct93Q2391vEd0JAt0n5RU
 status: PUBLISHED
 createdAt: 2023-03-21T22:28:23.673Z
diff --git a/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index 7fd74de95..bdd149176 100644
--- a/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -1,5 +1,5 @@
 ---
-title: 'Comportamiento erróneo de la mutación addToCart de checkout-graphql al enviar las "opciones" de los artículos ya añadidos'
+title: "Comportamiento erróneo de la mutación addToCart de checkout-graphql al enviar las 'opciones' de los artículos ya añadidos"
 id: 1lMWbgmBsOis9gAKcMm8ob
 status: PUBLISHED
 createdAt: 2022-05-03T20:42:18.655Z
diff --git a/docs/known-issues/es/my-account-page-does-not-work-on-domain-myvtex-com.md b/docs/known-issues/es/my-account-page-does-not-work-on-domain-myvtex-com.md
index b6f5e36ca..f3b036312 100644
--- a/docs/known-issues/es/my-account-page-does-not-work-on-domain-myvtex-com.md
+++ b/docs/known-issues/es/my-account-page-does-not-work-on-domain-myvtex-com.md
@@ -1,5 +1,5 @@
 ---
-title: 'Página "Mi Cuenta" no funciona en el dominio "myvtex.com"'
+title: "Página 'Mi Cuenta' no funciona en el dominio 'myvtex.com'"
 id: 1EW2Fuwbt3vO9uF8b9zRz4
 status: PUBLISHED
 createdAt: 2019-03-19T13:18:13.540Z
diff --git a/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md b/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
index 0ec45f321..f7c02ef8f 100644
--- a/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
+++ b/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
@@ -1,5 +1,5 @@
 ---
-title: '"No puede desactivar este producto porque tiene uno o más skus activos" no se traduce automáticamente en el Product admin'
+title: "'No puede desactivar este producto porque tiene uno o más skus activos' no se traduce automáticamente en el Product admin"
 id: 2wYoZ01LtolL1Tfhc4ldV8
 status: PUBLISHED
 createdAt: 2023-04-03T19:17:17.147Z
diff --git a/docs/known-issues/es/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md b/docs/known-issues/es/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md
index d5d1640fd..1dc762357 100644
--- a/docs/known-issues/es/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md
+++ b/docs/known-issues/es/obtertotaldepontos-function-does-not-work-inside-the-automatic-field.md
@@ -1,5 +1,5 @@
 ---
-title: 'La función "ObterTotalDePontos" no funciona dentro del Campo Automático'
+title: "La función 'ObterTotalDePontos' no funciona dentro del Campo Automático"
 id: 1iHy0tOPoUEIyGsYoq2Sqm
 status: PUBLISHED
 createdAt: 2018-12-10T18:08:19.476Z
diff --git a/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
index 5eba8fb2f..ef93d4fcd 100644
--- a/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
+++ b/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -1,5 +1,5 @@
 ---
-title: 'El filtro de pedidos no funciona correctamente debido a la presencia de comillas dobles (") en el nombre de la promoción o del SKU.'
+title: "El filtro de pedidos no funciona correctamente debido a la presencia de comillas dobles (') en el nombre de la promoción o del SKU."
 id: 4Qm0akQTQXR8sSbkTDiBL7
 status: PUBLISHED
 createdAt: 2024-06-06T15:42:19.747Z
diff --git a/docs/known-issues/es/orders-with-error-sistema-de-perfis.md b/docs/known-issues/es/orders-with-error-sistema-de-perfis.md
index dcf504959..40c13393c 100644
--- a/docs/known-issues/es/orders-with-error-sistema-de-perfis.md
+++ b/docs/known-issues/es/orders-with-error-sistema-de-perfis.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedidos con error "Ocorreu um erro de comunicação com o Sistema de Perfis"'
+title: "Pedidos con error 'Ocorreu um erro de comunicação com o Sistema de Perfis'"
 id: 2vj48Gmty8i4oQuoSOS46y
 status: PUBLISHED
 createdAt: 2017-05-08T20:51:46.084Z
diff --git a/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
index 4b0c649ef..109ac1b3c 100644
--- a/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -1,5 +1,5 @@
 ---
-title: "Portal no respeta la etiqueta "Principal" de SKU's Imagen"
+title: "Portal no respeta la etiqueta "Principal' de SKU's Imagen"
 id: 2ej5V3eIGgkUoo0Omgacc6
 status: CHANGED
 createdAt: 2017-04-17T18:35:42.842Z
diff --git a/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md b/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
index 208845fab..459e591fe 100644
--- a/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
+++ b/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
@@ -1,5 +1,5 @@
 ---
-title: ' La "posición" de la política comercial depende de la página en la que se muestra en la interfaz de administración'
+title: " La 'posición' de la política comercial depende de la página en la que se muestra en la interfaz de administración"
 id: 3kcSD7J5uuHYGdhBcg1lMa
 status: PUBLISHED
 createdAt: 2022-10-31T20:28:08.565Z
diff --git a/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
index 7e5c099cf..fdf5f345f 100644
--- a/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
+++ b/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -1,5 +1,5 @@
 ---
-title: 'El filtro de precios se aplica sobre el "precio al contado" en lugar del precio normal'
+title: "El filtro de precios se aplica sobre el 'precio al contado' en lugar del precio normal"
 id: 2EEgRV1NxYuns4eF7F0ZqD
 status: PUBLISHED
 createdAt: 2024-02-15T19:39:53.576Z
diff --git a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
index fc6e25de8..5092112c7 100644
--- a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
+++ b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'Precios restringidos al valor máximo "Int32" en la API de cambio de precio'
+title: "Precios restringidos al valor máximo 'Int32' en la API de cambio de precio"
 id: 5mzOjCUYs7vXUkttbsK0za
 status: PUBLISHED
 createdAt: 2022-04-25T17:28:05.159Z
diff --git a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md
index ad839fdf1..38b73df12 100644
--- a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md
+++ b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md
@@ -1,5 +1,5 @@
 ---
-title: 'Precios restringidos a un valor máximo de "Int32" en las APIs de pago'
+title: "Precios restringidos a un valor máximo de 'Int32' en las APIs de pago"
 id: 5mzOjCUYs7vXUkttbsK0za
 status: PUBLISHED
 createdAt: 2022-04-25T17:28:05.159Z
diff --git a/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
index 1c3caa913..78b077cfe 100644
--- a/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
+++ b/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -1,5 +1,5 @@
 ---
-title: 'Priorización por "palabra clave" del producto sin tener en cuenta las "stopwords'
+title: "Priorización por 'palabra clave' del producto sin tener en cuenta las 'stopwords"
 id: 55S7nFg61dAyCeGQCIw6aK
 status: PUBLISHED
 createdAt: 2024-05-30T22:05:25.328Z
diff --git a/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md b/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
index a15fce7e2..d978a40c7 100644
--- a/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
+++ b/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'Problemas al abrir la página "Gestionar el inventario" por parte del administrador con error (UI).'
+title: "Problemas al abrir la página 'Gestionar el inventario' por parte del administrador con error (UI)."
 id: 7owutd1w2Fa2JjgDnn3j5q
 status: PUBLISHED
 createdAt: 2022-03-15T20:14:57.926Z
diff --git a/docs/known-issues/es/problems-with-price-from-in-the-buttonbuymodal-control.md b/docs/known-issues/es/problems-with-price-from-in-the-buttonbuymodal-control.md
index 3be4840ad..8283d94ec 100644
--- a/docs/known-issues/es/problems-with-price-from-in-the-buttonbuymodal-control.md
+++ b/docs/known-issues/es/problems-with-price-from-in-the-buttonbuymodal-control.md
@@ -1,5 +1,5 @@
 ---
-title: 'Problemas con "precio de" en el control "ButtonBuyModal"'
+title: "Problemas con 'precio de' en el control 'ButtonBuyModal'"
 id: 2DdTK2AQNysEqM8AyMwSMQ
 status: PUBLISHED
 createdAt: 2018-10-05T17:06:27.321Z
diff --git a/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 7b4756cbe..0b9d3b082 100644
--- a/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API de inserción/actualización de productos permite "\n" en el campo textLink.'
+title: "La API de inserción/actualización de productos permite '\n' en el campo textLink."
 id: 5TfUw5tTxBEu9HkL3ypBKw
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.325Z
diff --git a/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
index 1d434be0f..b001e1db1 100644
--- a/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
+++ b/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'La búsqueda "El nombre del producto contiene" con más de un término no funciona en la interfaz de usuario rediseñada del catálogo.'
+title: "La búsqueda 'El nombre del producto contiene' con más de un término no funciona en la interfaz de usuario rediseñada del catálogo."
 id: 2kI6ab0kdpLG6m63ETGGqf
 status: PUBLISHED
 createdAt: 2024-06-05T13:38:38.836Z
diff --git a/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
index f7104f269..2b75f46c3 100644
--- a/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
+++ b/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -1,5 +1,5 @@
 ---
-title: 'El filtro "Especificación del producto" del módulo de recogida asume valores incorrectos.'
+title: "El filtro 'Especificación del producto' del módulo de recogida asume valores incorrectos."
 id: 2vg3t5kp7j4Ttla53pVjck
 status: PUBLISHED
 createdAt: 2023-10-26T22:22:44.895Z
diff --git a/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
index dfdc57600..912a6bd8c 100644
--- a/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
+++ b/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -1,5 +1,5 @@
 ---
-title: 'La importación de especificaciones de producto con el tipo "texto" no activa la indexación del producto.'
+title: "La importación de especificaciones de producto con el tipo 'texto' no activa la indexación del producto."
 id: 5eQB7LCCyDbVNQBQvWti33
 status: PUBLISHED
 createdAt: 2024-03-12T19:36:58.647Z
diff --git a/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md b/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
index 36a3c6dc6..b5b425f22 100644
--- a/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
+++ b/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
@@ -1,5 +1,5 @@
 ---
-title: 'Los productos de la "lista de productos" que tienen un "itemAttachment" se duplican cuando se aumenta la cantidad'
+title: "Los productos de la 'lista de productos' que tienen un 'itemAttachment' se duplican cuando se aumenta la cantidad"
 id: 4QybxJRoj7wLNvN7NG2FLA
 status: PUBLISHED
 createdAt: 2022-01-24T21:19:51.135Z
diff --git a/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
index 92ebef841..600acf3d9 100644
--- a/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
+++ b/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -1,5 +1,5 @@
 ---
-title: 'Productos con "unitMultiplier" marcados erróneamente como "con promoción" para los filtros de búsqueda'
+title: "Productos con 'unitMultiplier' marcados erróneamente como 'con promoción' para los filtros de búsqueda"
 id: 2rCi8K01DHsNuYsefE7oR2
 status: PUBLISHED
 createdAt: 2024-02-15T22:52:17.434Z
diff --git a/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
index 03aed88ee..ce46174b2 100644
--- a/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
+++ b/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -1,5 +1,5 @@
 ---
-title: 'La compra no se puede finalizar y se queda atascada en "el tipo de carga ha cambiado"'
+title: "La compra no se puede finalizar y se queda atascada en 'el tipo de carga ha cambiado'"
 id: mgewQ8QmZ3V3dkc7vdJkV
 status: PUBLISHED
 createdAt: 2023-09-25T13:28:28.121Z
diff --git a/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md b/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
index 7a1aa9000..9f88c7690 100644
--- a/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
+++ b/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
@@ -1,5 +1,5 @@
 ---
-title: 'La compra no se puede finalizar y devuelve el error "el campo del nombre del receptor no es válido"'
+title: "La compra no se puede finalizar y devuelve el error 'el campo del nombre del receptor no es válido'"
 id: 6ALBFvGzD0SiSuttfXPiQo
 status: PUBLISHED
 createdAt: 2022-05-12T14:53:10.287Z
diff --git a/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index adec58422..5cd819036 100644
--- a/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/es/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pestañas "Recibir | Retirar" se muestran solo según la disponibilidad en el código postal buscado'
+title: "Pestañas 'Recibir | Retirar' se muestran solo según la disponibilidad en el código postal buscado"
 id: 5PVGReAvyE0AOcoIq2SeKS
 status: PUBLISHED
 createdAt: 2018-11-21T16:19:00.507Z
diff --git a/docs/known-issues/es/received-skus-review-tab-missing-products.md b/docs/known-issues/es/received-skus-review-tab-missing-products.md
index 54e774d69..22bb8d00b 100644
--- a/docs/known-issues/es/received-skus-review-tab-missing-products.md
+++ b/docs/known-issues/es/received-skus-review-tab-missing-products.md
@@ -1,5 +1,5 @@
 ---
-title: 'Recibidos Skus "Revisión" ficha productos que faltan'
+title: "Recibidos Skus 'Revisión' ficha productos que faltan"
 id: 2UM0JQUZVq5o7NHCjmrg8N
 status: PUBLISHED
 createdAt: 2023-11-23T16:30:51.874Z
diff --git a/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 390ae0e81..70adc74bb 100644
--- a/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API de Regions no calcula correctamente el "seller 1" al solicitar sellers que no son white label'
+title: "La API de Regions no calcula correctamente el 'seller 1' al solicitar sellers que no son white label"
 id: 20sT9AMMi7Ob5IZc7FeiCB
 status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
diff --git a/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
index 2456a174f..e08875318 100644
--- a/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
+++ b/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -1,5 +1,5 @@
 ---
-title: 'Los banners de búsqueda no siguen el operador "AND" para las condiciones de activación'
+title: "Los banners de búsqueda no siguen el operador 'AND' para las condiciones de activación"
 id: 4nQLt5q3Mz2DxvBIyZknXj
 status: PUBLISHED
 createdAt: 2024-06-20T21:17:46.485Z
diff --git a/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md
index 66344e5e5..643591c86 100644
--- a/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md
@@ -1,5 +1,5 @@
 ---
-title: 'Las carpetas de segundo nivel no consideran el "contexto de búsqueda"'
+title: "Las carpetas de segundo nivel no consideran el 'contexto de búsqueda'"
 id: 6WvlorgpBEeIuKk2mprMXm
 status: PUBLISHED
 createdAt: 2019-02-17T19:55:07.529Z
diff --git a/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
index 792e074da..8fbb31e91 100644
--- a/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
+++ b/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -1,5 +1,5 @@
 ---
-title: 'La interfaz de usuario de la configuración no actualiza el "periodo de caducidad" de las cotizaciones'
+title: "La interfaz de usuario de la configuración no actualiza el 'periodo de caducidad' de las cotizaciones"
 id: 4CmuAYwDn7tcCiR9DQHSFb
 status: PUBLISHED
 createdAt: 2023-08-07T19:42:22.810Z
diff --git a/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md b/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md
index 7cf79da1f..9f9437dac 100644
--- a/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md
+++ b/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md
@@ -1,5 +1,5 @@
 ---
-title: 'Componente de expedición bloqueado en estado "Esperando más información".'
+title: "Componente de expedición bloqueado en estado 'Esperando más información'."
 id: 7HHlJdZvZ31NgsB7lTShAz
 status: PUBLISHED
 createdAt: 2023-03-29T19:26:05.971Z
diff --git a/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md b/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
index f6eaae566..f4d84b3e9 100644
--- a/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
+++ b/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
@@ -1,5 +1,5 @@
 ---
-title: 'Política de envío no priorizada por "Motivo: Descartado con carácter prioritario" incluso con mejor coste'
+title: "Política de envío no priorizada por 'Motivo: Descartado con carácter prioritario' incluso con mejor coste"
 id: p1oTHG7CuYITViV4uFZEQ
 status: PUBLISHED
 createdAt: 2022-05-10T18:05:57.097Z
diff --git a/docs/known-issues/es/shippingvalue-viewpart-incorrectly-displays-delivery-times-in-hours.md b/docs/known-issues/es/shippingvalue-viewpart-incorrectly-displays-delivery-times-in-hours.md
index 759cfa25a..ea92969b5 100644
--- a/docs/known-issues/es/shippingvalue-viewpart-incorrectly-displays-delivery-times-in-hours.md
+++ b/docs/known-issues/es/shippingvalue-viewpart-incorrectly-displays-delivery-times-in-hours.md
@@ -1,5 +1,5 @@
 ---
-title: 'ViewPart "shippingValue" no muestra los plazos en horas correctamente'
+title: "ViewPart 'shippingValue' no muestra los plazos en horas correctamente"
 id: 5hvl9eGxPLZAuNcFAFc9Vb
 status: PUBLISHED
 createdAt: 2019-09-09T20:07:14.796Z
diff --git a/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
index b2c865d00..8897b01e0 100644
--- a/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
+++ b/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -1,5 +1,5 @@
 ---
-title: 'La API de inserción de archivos de SKU no responde con la propiedad "Texto".'
+title: "La API de inserción de archivos de SKU no responde con la propiedad 'Texto'."
 id: 2rPsyAkpGNCVIM4yGlcMBw
 status: PUBLISHED
 createdAt: 2024-04-10T14:59:14.341Z
diff --git a/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md b/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
index 2c6f6a2b2..8cdb8c460 100644
--- a/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
+++ b/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
@@ -1,5 +1,5 @@
 ---
-title: 'Mensaje "Algo ha ido mal" al acceder a las rutas /a y /p en los almacenes de Portal'
+title: "Mensaje 'Algo ha ido mal' al acceder a las rutas /a y /p en los almacenes de Portal"
 id: 2XGAGH8xpNqjJpAir6DKzz
 status: PUBLISHED
 createdAt: 2023-11-30T16:31:45.428Z
diff --git a/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
index 1f15ea2e2..a8a6c0c85 100644
--- a/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
+++ b/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -1,5 +1,5 @@
 ---
-title: '"Algo salió mal" al añadir una dirección incompleta e intentar editarla'
+title: "'Algo salió mal' al añadir una dirección incompleta e intentar editarla"
 id: 3rWGAr4K86JAetSBJ75q3h
 status: PUBLISHED
 createdAt: 2024-01-02T21:11:17.425Z
diff --git a/docs/known-issues/es/special-character-not-mapped-to-be-ignored-in-textlink.md b/docs/known-issues/es/special-character-not-mapped-to-be-ignored-in-textlink.md
index aebb7738c..866f01d07 100644
--- a/docs/known-issues/es/special-character-not-mapped-to-be-ignored-in-textlink.md
+++ b/docs/known-issues/es/special-character-not-mapped-to-be-ignored-in-textlink.md
@@ -1,5 +1,5 @@
 ---
-title: 'Carácter especial "|" no mapeado para ser ignorado en TextLink'
+title: "Carácter especial '|' no mapeado para ser ignorado en TextLink"
 id: 5ALFG0CX168qaYUYWecW2q
 status: PUBLISHED
 createdAt: 2017-09-06T20:33:05.265Z
diff --git a/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md b/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md
index 36eabba02..ed87a89ab 100644
--- a/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md
+++ b/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md
@@ -1,5 +1,5 @@
 ---
-title: 'Estado "ERRO DE PROCESSAMENTO" Política de envíos'
+title: "Estado 'ERRO DE PROCESSAMENTO' Política de envíos"
 id: 4g3SWNwDVJG5OeJVP05TOd
 status: PUBLISHED
 createdAt: 2022-05-18T15:12:15.503Z
diff --git a/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 8c89cc253..90efc5cd0 100644
--- a/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -1,5 +1,5 @@
 ---
-title: 'StockKeepingUnitByEAN returns 404 for EANs with "/"'
+title: "StockKeepingUnitByEAN returns 404 for EANs with '/'"
 id: Pp3lE5Gu54gOw6liInte4
 status: DRAFT
 createdAt: 2022-02-25T12:23:55.903Z
diff --git a/docs/known-issues/es/store-texts-search-doesnt-work.md b/docs/known-issues/es/store-texts-search-doesnt-work.md
index af672a6ab..b0d454203 100644
--- a/docs/known-issues/es/store-texts-search-doesnt-work.md
+++ b/docs/known-issues/es/store-texts-search-doesnt-work.md
@@ -1,5 +1,5 @@
 ---
-title: 'Búsqueda de "Textos de la tienda" no funciona'
+title: "Búsqueda de 'Textos de la tienda' no funciona"
 id: 6C6JUkssKcOoQqsaikucwy
 status: PUBLISHED
 createdAt: 2017-08-24T15:16:31.392Z
diff --git a/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md b/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md
index d5957425d..fc52bd9e3 100644
--- a/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md
+++ b/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md
@@ -1,5 +1,5 @@
 ---
-title: 'La aplicación Storefront permissions establece "documentType" como "cpf"'
+title: "La aplicación Storefront permissions establece 'documentType' como 'cpf'"
 id: 1vd0gFWrP50UZacQ0QBKP8
 status: PUBLISHED
 createdAt: 2023-04-27T15:19:53.064Z
diff --git a/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md b/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
index 975555760..fbdd24fcb 100644
--- a/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
+++ b/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
@@ -1,5 +1,5 @@
 ---
-title: 'El plan de suscripción está "atascado" en la "importación" después de cargar la hoja de cálculo de la asociación de SKUs'
+title: "El plan de suscripción está 'atascado' en la 'importación' después de cargar la hoja de cálculo de la asociación de SKUs"
 id: 4BVj2X44OZMttG57vUryHb
 status: PUBLISHED
 createdAt: 2022-05-03T00:28:48.118Z
diff --git a/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
index 30fab17bc..68ceff8f1 100644
--- a/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
+++ b/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -1,5 +1,5 @@
 ---
-title: 'La búsqueda de televentas no acepta caracteres especiales aparte de "@".'
+title: "La búsqueda de televentas no acepta caracteres especiales aparte de '@'."
 id: 5eTb6KlR07dOP06BGhovoL
 status: PUBLISHED
 createdAt: 2024-07-29T17:21:34.828Z
diff --git a/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index f83486067..4faa791d4 100644
--- a/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -1,5 +1,5 @@
 ---
-title: 'Enlace de texto creado con " " en Marketplace tras las aprobaciones - Reoccurrence'
+title: "Enlace de texto creado con ' ' en Marketplace tras las aprobaciones - Reoccurrence"
 id: 2afynQ9MwaHPMPWyhx80Tp
 status: PUBLISHED
 createdAt: 2023-04-24T19:36:10.185Z
diff --git a/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md b/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
index ac1b851a5..ce0078704 100644
--- a/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
+++ b/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
@@ -1,5 +1,5 @@
 ---
-title: 'La aplicación Cielo 3DS2 devuelve un estado "aprobado" incluso en situaciones en las que la autenticación ha fallado.'
+title: "La aplicación Cielo 3DS2 devuelve un estado 'aprobado' incluso en situaciones en las que la autenticación ha fallado."
 id: 58hSiWFhn6sHQofJAUoHqv
 status: PUBLISHED
 createdAt: 2023-05-05T14:48:56.148Z
diff --git a/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md b/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
index 2a9727b66..49e15cf02 100644
--- a/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
+++ b/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
@@ -1,5 +1,5 @@
 ---
-title: 'La división de la entrega no se mostrará en la interfaz de usuario ni en Mis pedidos cuando el pedido tenga el mismo "Método de envío".'
+title: "La división de la entrega no se mostrará en la interfaz de usuario ni en Mis pedidos cuando el pedido tenga el mismo 'Método de envío'."
 id: 2VnPyguau8KjpWx09C2vOW
 status: PUBLISHED
 createdAt: 2022-03-15T20:24:32.693Z
diff --git a/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md b/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
index 815378570..b36473b73 100644
--- a/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
+++ b/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
@@ -1,5 +1,5 @@
 ---
-title: 'La condición especial del banco emisor está causando para algunos BINs el error en la página de pago "El banco emisor para este banco no es aceptado"'
+title: "La condición especial del banco emisor está causando para algunos BINs el error en la página de pago 'El banco emisor para este banco no es aceptado'"
 id: 7HgNpwcvqQDwSfJfv9KpY8
 status: PUBLISHED
 createdAt: 2022-03-25T19:04:12.310Z
diff --git a/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md b/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
index 45e48e30d..82db528ab 100644
--- a/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
+++ b/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
@@ -1,5 +1,5 @@
 ---
-title: 'El mensaje "Mi dirección de facturación es ..." en el iFrame de la tarjeta de crédito está en un idioma incorrecto cuando se utiliza el checkout en catalán.'
+title: "El mensaje 'Mi dirección de facturación es ...' en el iFrame de la tarjeta de crédito está en un idioma incorrecto cuando se utiliza el checkout en catalán."
 id: 3AqPihwDDIM2qixa1jvJmz
 status: PUBLISHED
 createdAt: 2022-03-28T01:11:35.679Z
diff --git a/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index 1089145ab..14ae7540d 100644
--- a/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -1,5 +1,5 @@
 ---
-title: 'La opción "Guardar nueva tarjeta" no funciona para los proveedores de pago asíncronos.'
+title: "La opción 'Guardar nueva tarjeta' no funciona para los proveedores de pago asíncronos."
 id: 3B4gVSNrSeCc8EBXwk5sAu
 status: PUBLISHED
 createdAt: 2022-03-11T17:54:35.664Z
diff --git a/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index d17e9619c..fef0d3589 100644
--- a/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -1,5 +1,5 @@
 ---
-title: 'La plantilla "relatorio-de-importacao-de-estoque" no admite el multilingüismo'
+title: "La plantilla 'relatorio-de-importacao-de-estoque' no admite el multilingüismo"
 id: 5R8b0jnibOQdXupo0hIyts
 status: PUBLISHED
 createdAt: 2022-05-25T18:25:43.394Z
diff --git a/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md b/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
index 10a2efdf5..0be407bbb 100644
--- a/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
+++ b/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
@@ -1,5 +1,5 @@
 ---
-title: 'Transacción cancelada por tiempo de espera: "Timeout no request para o Sistema de Parcelamento"'
+title: "Transacción cancelada por tiempo de espera: 'Timeout no request para o Sistema de Parcelamento'"
 id: 68L2ka1QJ3yEHTsId1arF7
 status: PUBLISHED
 createdAt: 2022-03-02T12:15:17.495Z
diff --git a/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
index 799ec8761..20833ccfd 100644
--- a/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
+++ b/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error de cancelación de transacción con el mensaje "Código no localizable".'
+title: "Error de cancelación de transacción con el mensaje 'Código no localizable'."
 id: 2Y4joZlyDhbNWU9ycw32U3
 status: PUBLISHED
 createdAt: 2024-03-12T16:34:10.113Z
diff --git a/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
index 1441e839a..8b88813b8 100644
--- a/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
+++ b/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -1,5 +1,5 @@
 ---
-title: 'La interfaz de usuario muestra "¡Regalos elegidos!" cuando se utiliza la función de sustitución de pedidos.'
+title: "La interfaz de usuario muestra '¡Regalos elegidos!' cuando se utiliza la función de sustitución de pedidos."
 id: 4efm7L6hQhad98uYkjzrXO
 status: PUBLISHED
 createdAt: 2023-09-27T20:57:46.944Z
diff --git a/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md b/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
index 72e5f4611..e0edf0fa9 100644
--- a/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
+++ b/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
@@ -1,5 +1,5 @@
 ---
-title: 'No se puede cambiar el estado en la pasarela cuando el objeto de carro de la transacción en /transacción es "desconocido".'
+title: "No se puede cambiar el estado en la pasarela cuando el objeto de carro de la transacción en /transacción es 'desconocido'."
 id: 3gWqk1T2xP3eRYZtXZLX3b
 status: PUBLISHED
 createdAt: 2023-03-23T14:27:16.116Z
diff --git a/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md b/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md
index 76d797086..1a2a46688 100644
--- a/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md
+++ b/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md
@@ -1,5 +1,5 @@
 ---
-title: 'No se puede crear el elemento personalizado "Productos relacionados".'
+title: "No se puede crear el elemento personalizado 'Productos relacionados'."
 id: 4Ca3b0mfpe20K7wSaImSQj
 status: PUBLISHED
 createdAt: 2022-01-21T14:44:26.429Z
diff --git a/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
index bce363441..b96eb524a 100644
--- a/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
+++ b/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'Error "Unhandled exception" al cambiar la edición de la cuenta'
+title: "Error 'Unhandled exception' al cambiar la edición de la cuenta"
 id: 1NVjCrlRkadscl8fW9rOdA
 status: PUBLISHED
 createdAt: 2023-09-26T12:45:44.999Z
diff --git a/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md b/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md
index f1454f824..ca0640217 100644
--- a/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md
+++ b/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md
@@ -1,5 +1,5 @@
 ---
-title: 'El campo "Url Logo" en la solicitud de actualización del vendedor no se actualiza'
+title: "El campo 'Url Logo' en la solicitud de actualización del vendedor no se actualiza"
 id: 1WmNl3RgesWAUL8rjitJV1
 status: PUBLISHED
 createdAt: 2022-01-21T15:18:15.945Z
diff --git a/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
index e895b5353..a429de0b2 100644
--- a/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
+++ b/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -1,5 +1,5 @@
 ---
-title: 'El usuario sólo con el rol "Administrador de usuarios - RESTRINGIDO" no puede listar los usuarios'
+title: "El usuario sólo con el rol 'Administrador de usuarios - RESTRINGIDO' no puede listar los usuarios"
 id: ifXUAzgJ1xr8ezhqKpRUI
 status: PUBLISHED
 createdAt: 2023-11-08T18:07:14.508Z
diff --git a/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
index e65315138..15f59d1a7 100644
--- a/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
+++ b/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -1,5 +1,5 @@
 ---
-title: 'Autor de la versión "Nota: No encontrado en VTEX ID." en el perfil'
+title: "Autor de la versión 'Nota: No encontrado en VTEX ID.' en el perfil"
 id: 0X6Aj6YdCXXfNweAkDS46
 status: PUBLISHED
 createdAt: 2023-10-04T21:48:14.699Z
diff --git a/docs/known-issues/es/visited-product-feature-does-not-work-properly.md b/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
index 4270ddd83..1668e9d07 100644
--- a/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
@@ -1,5 +1,5 @@
 ---
-title: ' La función "Producto visitado" no funciona correctamente'
+title: " La función 'Producto visitado' no funciona correctamente"
 id: 5AiCVwLkGToEgtLkZVPe5i
 status: PUBLISHED
 createdAt: 2022-11-25T18:45:15.389Z
diff --git a/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md b/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md
index 6b8986a4b..1b13b78dc 100644
--- a/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md
+++ b/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md
@@ -1,5 +1,5 @@
 ---
-title: '<vtex:contentPlaceHolder id="Acessorios"/> no funciona'
+title: "<vtex:contentPlaceHolder id='Acessorios'/> no funciona"
 id: 7x8f0vGaunX1P3EFJGCYaz
 status: PUBLISHED
 createdAt: 2022-01-23T02:24:12.606Z
diff --git a/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 6cb16b78f..7d111d3a1 100644
--- a/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -1,5 +1,5 @@
 ---
-title: 'Al añadir una SKU a través de nuestra funcionalidad "Cambiar pedido", el nombre del producto no se muestra en el pedido ni en la notificación por correo electrónico'
+title: "Al añadir una SKU a través de nuestra funcionalidad 'Cambiar pedido', el nombre del producto no se muestra en el pedido ni en la notificación por correo electrónico"
 id: 35Q3KoOSsUr9n9XEDIk7nk
 status: PUBLISHED
 createdAt: 2022-04-07T14:53:35.829Z
diff --git a/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index bbea01c51..2efbe4ad8 100644
--- a/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -1,5 +1,5 @@
 ---
-title: 'Al cargar la página "Catalog Maping" en admin no se traduce el mensaje inicial'
+title: "Al cargar la página 'Catalog Maping' en admin no se traduce el mensaje inicial"
 id: 4WszmRZ5jpeSDNTEuFIdwF
 status: PUBLISHED
 createdAt: 2022-12-15T12:32:17.741Z
diff --git a/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 3674fd1e2..497a34519 100644
--- a/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cuando settleId se envía como null y el código como "refund-manually" nuestra pasarela realiza un doble reembolso.'
+title: "Cuando settleId se envía como null y el código como 'refund-manually' nuestra pasarela realiza un doble reembolso."
 id: 2PdRRjHDODY2Tk0VItO4Fo
 status: PUBLISHED
 createdAt: 2022-07-11T17:37:43.961Z
diff --git a/docs/known-issues/es/xml-currency-symbol-in-the-installment.md b/docs/known-issues/es/xml-currency-symbol-in-the-installment.md
index 02fea633e..ab92d548c 100644
--- a/docs/known-issues/es/xml-currency-symbol-in-the-installment.md
+++ b/docs/known-issues/es/xml-currency-symbol-in-the-installment.md
@@ -1,5 +1,5 @@
 ---
-title: 'XML - Simbolo de moneda en campo "Parcelamento"'
+title: "XML - Simbolo de moneda en campo 'Parcelamento'"
 id: 4s7hBA1MAUgeEC2Q4K8gKM
 status: DRAFT
 createdAt: 2017-06-26T15:22:31.980Z
diff --git a/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
index 7c8f4971a..cabb0ee22 100644
--- a/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
+++ b/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
@@ -1,5 +1,5 @@
 ---
-title: 'El indicador "Nombre del producto" de XML no funciona correctamente'
+title: "El indicador 'Nombre del producto' de XML no funciona correctamente"
 id: 6YDbpRns3LCN02bVKM8aaf
 status: PUBLISHED
 createdAt: 2023-10-26T11:35:14.500Z
diff --git a/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
index 6b71a7142..112226125 100644
--- a/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
+++ b/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -1,5 +1,5 @@
 ---
-title: 'Uma SKU pode estar ativa e ter o sinalizador "ativar se possível" desmarcado'
+title: "Uma SKU pode estar ativa e ter o sinalizador 'ativar se possível' desmarcado"
 id: 5uXQ65flkoEbYeLkNSw4ig
 status: PUBLISHED
 createdAt: 2023-11-07T11:01:20.612Z
diff --git a/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md b/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
index 33ba888c8..10ea3ebae 100644
--- a/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
+++ b/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
@@ -1,5 +1,5 @@
 ---
-title: 'Contas com "-" no nome não têm métricas no relatório de busca'
+title: "Contas com '-' no nome não têm métricas no relatório de busca"
 id: 71rVz43g0rgIN7Joe4GEj6
 status: PUBLISHED
 createdAt: 2023-04-19T17:35:28.560Z
diff --git a/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md b/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
index c33f22ff1..e85957dda 100644
--- a/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
+++ b/docs/known-issues/pt/add-option-not-available-when-creating-dictionary.md
@@ -1,5 +1,5 @@
 ---
-title: 'Criar dicionário não disponibiliza opção de "Add"'
+title: "Criar dicionário não disponibiliza opção de 'Add'"
 id: 6kSvXDetqLw954q5hYIRQN
 status: PUBLISHED
 createdAt: 2019-12-26T14:48:14.548Z
diff --git a/docs/known-issues/pt/address-field-comes-with-null-vaule-in-payments-api-query.md b/docs/known-issues/pt/address-field-comes-with-null-vaule-in-payments-api-query.md
index 596a85fde..491f401a3 100644
--- a/docs/known-issues/pt/address-field-comes-with-null-vaule-in-payments-api-query.md
+++ b/docs/known-issues/pt/address-field-comes-with-null-vaule-in-payments-api-query.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campo "address" vem com valor "null" na consulta da API do Pagamentos'
+title: "Campo 'address' vem com valor 'null' na consulta da API do Pagamentos"
 id: 7oEEc24umACsOoy4Ceso2W
 status: PUBLISHED
 createdAt: 2018-01-11T16:33:01.231Z
diff --git a/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md b/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
index d59c310e2..7963a1f57 100644
--- a/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
+++ b/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
@@ -1,5 +1,5 @@
 ---
-title: 'Endereço em ordemForma com tamanho excessivo para múltiplas cidades separadas por "::".'
+title: "Endereço em ordemForma com tamanho excessivo para múltiplas cidades separadas por '::'."
 id: 7E6x4O56SxcSeU2qv09GBt
 status: PUBLISHED
 createdAt: 2023-01-06T11:52:36.229Z
diff --git a/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
index 7faf8d91e..21a67282f 100644
--- a/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
+++ b/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -1,5 +1,5 @@
 ---
-title: 'Os endereços são exibidos no Checkout quando o comprador tem a permissão "Can add shipping" (Pode adicionar frete)'
+title: "Os endereços são exibidos no Checkout quando o comprador tem a permissão 'Can add shipping' (Pode adicionar frete)"
 id: 2ssiTryGJ6kGoZWxWkGnFF
 status: PUBLISHED
 createdAt: 2024-05-21T22:03:55.172Z
diff --git a/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
index c79005de7..39f802401 100644
--- a/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
+++ b/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'A incompatibilidade de AddressId causa o erro "endereço inválido para um item"'
+title: "A incompatibilidade de AddressId causa o erro 'endereço inválido para um item'"
 id: 5bSac85eHb9NmrOhcTjHNw
 status: PUBLISHED
 createdAt: 2024-03-01T19:28:52.074Z
diff --git a/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md b/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
index 1af0021c4..134fe3c70 100644
--- a/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
+++ b/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
@@ -1,5 +1,5 @@
 ---
-title: 'A função addToCart não funciona corretamente com anexos e com o anexo do componente "opções de montagem".'
+title: "A função addToCart não funciona corretamente com anexos e com o anexo do componente 'opções de montagem'."
 id: 6I8vn2K7PWLRwIj2YTY7nZ
 status: PUBLISHED
 createdAt: 2023-05-23T15:40:36.343Z
diff --git a/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
index 757d663cd..2858606f3 100644
--- a/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
+++ b/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -1,5 +1,5 @@
 ---
-title: '[Admin] A Pesquisa global não reconhece os "Itens do menu de perfil"'
+title: "[Admin] A Pesquisa global não reconhece os 'Itens do menu de perfil'"
 id: 4AZiu9NXouL6b8z5EHJIWK
 status: PUBLISHED
 createdAt: 2024-01-22T17:09:55.423Z
diff --git a/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index a3088d15a..bc9fe3270 100644
--- a/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -1,5 +1,5 @@
 ---
-title: 'ALT attribute not showing in <vtex.cmc:ProductImage zoom="on" />'
+title: "ALT attribute not showing in <vtex.cmc:ProductImage zoom='on' />"
 id: 4P1Eys9Q2WFddrMLQVDvM9
 status: DRAFT
 createdAt: 2022-02-17T13:08:53.295Z
diff --git a/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md
index e278326e9..80c6242e4 100644
--- a/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: '[AMAZON] Referência de objeto não definida para uma instância de um objeto"'
+title: "[AMAZON] Referência de objeto não definida para uma instância de um objeto'"
 id: 7xWXzfztp7b9I8KeBSzgST
 status: PUBLISHED
 createdAt: 2022-03-10T18:00:38.681Z
diff --git a/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md b/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md
index 37ff1768e..c7d225c10 100644
--- a/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md
+++ b/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md
@@ -1,5 +1,5 @@
 ---
-title: '"Ocorreu um erro" ao adicionar informações de rastreamento'
+title: "'Ocorreu um erro' ao adicionar informações de rastreamento"
 id: 1gmlrPh9P1KbNI5NNXuImO
 status: PUBLISHED
 createdAt: 2023-02-08T18:38:55.699Z
diff --git a/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
index 8174330a5..9071c4fe1 100644
--- a/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
+++ b/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -1,5 +1,5 @@
 ---
-title: 'A API da Attachents não permite "domainValues" nulos (e deveria)'
+title: "A API da Attachents não permite 'domainValues' nulos (e deveria)"
 id: 7KMb6nh0ulcWdEfz7USbPg
 status: PUBLISHED
 createdAt: 2023-09-11T19:02:51.514Z
diff --git a/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
index e1f6d719f..13dbd6308 100644
--- a/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
+++ b/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
@@ -1,5 +1,5 @@
 ---
-title: 'Registros de preços de auditoria mostrando informações "desconhecidas"'
+title: "Registros de preços de auditoria mostrando informações 'desconhecidas'"
 id: 7b8UDsiBo7VOHCN3pgcfd0
 status: PUBLISHED
 createdAt: 2023-07-05T18:51:22.120Z
diff --git a/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
index f4343482c..bd84a1822 100644
--- a/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
+++ b/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -1,5 +1,5 @@
 ---
-title: 'A API de sugestão de preenchimento automático remove o ponto "." do nome do produto'
+title: "A API de sugestão de preenchimento automático remove o ponto '.' do nome do produto"
 id: 55185IvERIwGQ3kH6H510O
 status: PUBLISHED
 createdAt: 2024-04-10T13:58:51.138Z
diff --git a/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
index ddaed9b98..3fdfce2e1 100644
--- a/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
+++ b/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -1,5 +1,5 @@
 ---
-title: 'O campo "disponibilidade" está incorreto na Simulação de Cumprimento para produtos sem estoque ou preço'
+title: "O campo 'disponibilidade' está incorreto na Simulação de Cumprimento para produtos sem estoque ou preço"
 id: 1k2zcLEN5vG6mnksLwEXxp
 status: PUBLISHED
 createdAt: 2023-10-04T14:22:53.519Z
diff --git a/docs/known-issues/pt/aviseme-report-does-not-open.md b/docs/known-issues/pt/aviseme-report-does-not-open.md
index 5a8189392..6dde8fb79 100644
--- a/docs/known-issues/pt/aviseme-report-does-not-open.md
+++ b/docs/known-issues/pt/aviseme-report-does-not-open.md
@@ -1,5 +1,5 @@
 ---
-title: 'Relatório de "Avise-me" não abre'
+title: "Relatório de 'Avise-me' não abre"
 id: 5jRrYk5Nm0uGSmoyeogIs2
 status: PUBLISHED
 createdAt: 2017-06-13T15:07:33.222Z
diff --git a/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 1fa2ef38c..46d957a4d 100644
--- a/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -1,5 +1,5 @@
 ---
-title: '[Ordem "B2W direta" (FOB) integrando-se com a transportadora'
+title: "[Ordem 'B2W direta' (FOB) integrando-se com a transportadora"
 id: 20nA7vm1RFMhv7yhaJ43GG
 status: PUBLISHED
 createdAt: 2022-12-12T18:14:19.975Z
diff --git a/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md b/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md
index 5d5940bda..de4c5e989 100644
--- a/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md
+++ b/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md
@@ -1,5 +1,5 @@
 ---
-title: '[Ordem com erro de "Parâmetro de desajuste de contagem".'
+title: "[Ordem com erro de 'Parâmetro de desajuste de contagem'."
 id: 6XhzSJrrHaEt85QseRdC3k
 status: PUBLISHED
 createdAt: 2023-03-22T19:32:10.011Z
diff --git a/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md b/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md
index ed9806bb5..63404b0ff 100644
--- a/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md
+++ b/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md
@@ -1,5 +1,5 @@
 ---
-title: 'O botão "Voltar" não é renderizado em Minha organização'
+title: "O botão 'Voltar' não é renderizado em Minha organização"
 id: xzd2JVKP6jcTN0dGWwISB
 status: PUBLISHED
 createdAt: 2023-04-25T21:26:35.401Z
diff --git a/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md b/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
index 5cd07f2c5..54ec41d6f 100644
--- a/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
+++ b/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'O botão "Back to site" leva ao gatewayCallback//Success ao invés de placeOrder page'
+title: "O botão 'Back to site' leva ao gatewayCallback//Success ao invés de placeOrder page"
 id: 7Hp6yYCblhbhrN3jHHigUC
 status: PUBLISHED
 createdAt: 2023-04-10T15:18:58.986Z
diff --git a/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
index 37adf5bd6..31c7277d3 100644
--- a/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
@@ -1,5 +1,5 @@
 ---
-title: 'Solicitação incorreta ao pesquisar termos com "%" diretamente via URL'
+title: "Solicitação incorreta ao pesquisar termos com '%' diretamente via URL"
 id: 3gdZ8egQRa4zcNRe2f5CbT
 status: PUBLISHED
 createdAt: 2023-03-21T22:51:46.273Z
diff --git a/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
index 32119cdb4..dee5b61b2 100644
--- a/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
+++ b/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -1,5 +1,5 @@
 ---
-title: 'Solicitação incorreta ao pesquisar termos com "#" por meio do preenchimento automático'
+title: "Solicitação incorreta ao pesquisar termos com '#' por meio do preenchimento automático"
 id: 18pMsxubB9eSPGlULAN35p
 status: PUBLISHED
 createdAt: 2024-02-06T20:07:52.739Z
diff --git a/docs/known-issues/pt/bug-in-cart-with-promotion-when-splitting-item.md b/docs/known-issues/pt/bug-in-cart-with-promotion-when-splitting-item.md
index 6fc6338ee..3a98029f0 100644
--- a/docs/known-issues/pt/bug-in-cart-with-promotion-when-splitting-item.md
+++ b/docs/known-issues/pt/bug-in-cart-with-promotion-when-splitting-item.md
@@ -1,5 +1,5 @@
 ---
-title: 'Bug no Carrinho com promoção ao "splitar" item'
+title: "Bug no Carrinho com promoção ao 'splitar' item"
 id: 26EY5QcY4wcGm88okke8SY
 status: PUBLISHED
 createdAt: 2017-05-24T20:20:57.562Z
diff --git a/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index 6572c7dca..606f4e42b 100644
--- a/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -1,5 +1,5 @@
 ---
-title: 'Botão "Cancelar" dentro da página MyCards não traduzido para o espanhol'
+title: "Botão 'Cancelar' dentro da página MyCards não traduzido para o espanhol"
 id: 5wIEEoF7gTLYlWnANxDZ7h
 status: PUBLISHED
 createdAt: 2022-02-24T13:18:00.062Z
diff --git a/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
index 4107cc932..b9d9e63f7 100644
--- a/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
+++ b/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -1,5 +1,5 @@
 ---
-title: 'IU do público-alvo da campanha alterando "Diferente de" para "Igual a" com uma coleção'
+title: "IU do público-alvo da campanha alterando 'Diferente de' para 'Igual a' com uma coleção"
 id: 6IkWioZ9WRgg1DFEMdnthB
 status: PUBLISHED
 createdAt: 2023-08-15T15:12:54.580Z
diff --git a/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
index 17876d77b..3b68dfbf9 100644
--- a/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
+++ b/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -1,5 +1,5 @@
 ---
-title: 'Carrinho criado a partir de uma opção "pedir novamente" em Meus pedidos, o e-mail do cliente não está sendo colocado como esperado no formulário de pedido'
+title: "Carrinho criado a partir de uma opção 'pedir novamente' em Meus pedidos, o e-mail do cliente não está sendo colocado como esperado no formulário de pedido"
 id: 6dDhkaIhquOqaDuNkVZuln
 status: PUBLISHED
 createdAt: 2023-12-04T22:41:21.385Z
diff --git a/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md b/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
index 13b024cb1..839a71d63 100644
--- a/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
+++ b/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
@@ -1,5 +1,5 @@
 ---
-title: 'Carrinho com itens exibe a mensagem "carrinho vazio" enquanto a tela ainda está carregando'
+title: "Carrinho com itens exibe a mensagem 'carrinho vazio' enquanto a tela ainda está carregando"
 id: 4oAiVz7fJL9vPkpPFEGyBT
 status: PUBLISHED
 createdAt: 2023-03-09T22:42:06.855Z
diff --git a/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md b/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
index 7e3376772..6c3a837f3 100644
--- a/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
+++ b/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
@@ -1,5 +1,5 @@
 ---
-title: 'Exportação de Catálogo não mostra os Canais de Venda quando "nenhum" está marcado'
+title: "Exportação de Catálogo não mostra os Canais de Venda quando 'nenhum' está marcado"
 id: 10Bozz8ai3fAvu1m9Ex2Gk
 status: PUBLISHED
 createdAt: 2022-12-23T13:38:32.114Z
diff --git a/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
index ace8e0823..2709ad53a 100644
--- a/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro de Cálculo da Seção "Total" do Relatório de Indexação do Catálogo '
+title: "Erro de Cálculo da Seção 'Total' do Relatório de Indexação do Catálogo "
 id: 6TJXux104P2c0mruo5vlEn
 status: PUBLISHED
 createdAt: 2022-02-25T11:39:42.098Z
diff --git a/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md b/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md
index de1831b8e..fde07d4f9 100644
--- a/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md
+++ b/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md
@@ -1,5 +1,5 @@
 ---
-title: 'Centauro Orders with "Pedido sem o campo: "packages" error'
+title: "Centauro Orders with 'Pedido sem o campo: 'packages' error"
 id: 1HMhinuVlggWwQZPuNchiX
 status: PUBLISHED
 createdAt: 2022-06-24T13:10:45.752Z
diff --git a/docs/known-issues/pt/centauro-to-implement-centauro-envios.md b/docs/known-issues/pt/centauro-to-implement-centauro-envios.md
index 6d5cbfd35..f6381a7e5 100644
--- a/docs/known-issues/pt/centauro-to-implement-centauro-envios.md
+++ b/docs/known-issues/pt/centauro-to-implement-centauro-envios.md
@@ -1,5 +1,5 @@
 ---
-title: '[Para implementar o "Centauro Envios'
+title: "[Para implementar o 'Centauro Envios"
 id: 1xkjyfVfT8Fs2as9mbNjj3
 status: PUBLISHED
 createdAt: 2022-11-25T21:23:23.849Z
diff --git a/docs/known-issues/pt/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md b/docs/known-issues/pt/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
index f18ff545e..774060e6e 100644
--- a/docs/known-issues/pt/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
+++ b/docs/known-issues/pt/changes-to-the-my-account-page-do-not-appear-immediately-in-the-domain.md
@@ -1,5 +1,5 @@
 ---
-title: 'Alterações na página de "minha conta" não aparecem imediatamente no domínio "vtexcommercestable.com.br"'
+title: "Alterações na página de 'minha conta' não aparecem imediatamente no domínio 'vtexcommercestable.com.br'"
 id: iUmuXOYVj97sTpqQnJqAU
 status: PUBLISHED
 createdAt: 2019-03-19T13:23:11.941Z
diff --git a/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md b/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md
index 5b28b659b..c51ab3d6f 100644
--- a/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md
+++ b/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md
@@ -1,5 +1,5 @@
 ---
-title: 'A caixa de seleção "Requer autenticação" não funciona no módulo Páginas'
+title: "A caixa de seleção 'Requer autenticação' não funciona no módulo Páginas"
 id: 6nKuqSmk7JZgdaAysNYls3
 status: PUBLISHED
 createdAt: 2022-05-11T21:25:07.700Z
diff --git a/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md b/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
index 7ce867022..1bf54c8c9 100644
--- a/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
+++ b/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout payment split may generate incorrect information in the "paymentData" of orders (NO-PAYMENT)'
+title: "Checkout payment split may generate incorrect information in the 'paymentData' of orders (NO-PAYMENT)"
 id: 1bZ5H0T0isc0DUtkIb38sQ
 status: PUBLISHED
 createdAt: 2022-01-24T20:37:23.861Z
diff --git a/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
index 679cfdbcf..3f8d7d981 100644
--- a/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
+++ b/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -1,5 +1,5 @@
 ---
-title: 'A simulação de checkout retorna o valor 0 no campo "slas.tax" para impostos de porcentagem de frete'
+title: "A simulação de checkout retorna o valor 0 no campo 'slas.tax' para impostos de porcentagem de frete"
 id: 54Mtsj8EKuo0SaQCoWyYzj
 status: PUBLISHED
 createdAt: 2024-04-05T18:55:32.183Z
diff --git a/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
index d337a1cf7..6f6ddceac 100644
--- a/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
+++ b/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -1,5 +1,5 @@
 ---
-title: 'A interface de usuário do checkout não está usando automaticamente o "envio enxuto" para itens sem métodos de envio comuns'
+title: "A interface de usuário do checkout não está usando automaticamente o 'envio enxuto' para itens sem métodos de envio comuns"
 id: 2LXp8VCAay7Ic9MBfbtirT
 status: PUBLISHED
 createdAt: 2024-04-02T15:27:23.003Z
diff --git a/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md b/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
index a15d0ecad..f96aa758d 100644
--- a/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
+++ b/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'Checkout UI desmarca a opção "Schedule all" após refrescar a página'
+title: "Checkout UI desmarca a opção 'Schedule all' após refrescar a página"
 id: 28TIselp0EzU3iSD4kLJgX
 status: PUBLISHED
 createdAt: 2023-04-04T21:08:55.937Z
diff --git a/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index 965d9a39b..23a973c19 100644
--- a/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -1,5 +1,5 @@
 ---
-title: 'O campo de coleções sempre aparece como "Igual a" no formulário da campanha para o público'
+title: "O campo de coleções sempre aparece como 'Igual a' no formulário da campanha para o público"
 id: 2NPEh7LZkrpO0gf802I7HZ
 status: PUBLISHED
 createdAt: 2022-11-11T21:18:53.386Z
diff --git a/docs/known-issues/pt/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md b/docs/known-issues/pt/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md
index ba8b9cac3..9d8b3fe5a 100644
--- a/docs/known-issues/pt/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md
+++ b/docs/known-issues/pt/confirm-action-unavailable-in-catalog-sellers-cms-and-gift-card-modules-for.md
@@ -1,5 +1,5 @@
 ---
-title: '"Confirmar Ação" está indisponível no Catálogo, Sellers, CMS, Vale-compra pelo Google Chrome'
+title: "'Confirmar Ação' está indisponível no Catálogo, Sellers, CMS, Vale-compra pelo Google Chrome"
 id: 5UzVaWa63dPwPlbK3n2AH5
 status: PUBLISHED
 createdAt: 2021-07-27T22:29:39.402Z
diff --git a/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md b/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
index a8e6814d5..34726445d 100644
--- a/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
+++ b/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
@@ -1,5 +1,5 @@
 ---
-title: 'Conflitos com filtros de preço e "isAvailablePerSalesChannel" em buscas (Portal e Busca) (Novamente)'
+title: "Conflitos com filtros de preço e 'isAvailablePerSalesChannel' em buscas (Portal e Busca) (Novamente)"
 id: 6dLv8lP69Em68ooydjaPzY
 status: PUBLISHED
 createdAt: 2022-02-24T13:24:42.299Z
diff --git a/docs/known-issues/pt/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md b/docs/known-issues/pt/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
index 01c5171db..b7f895eba 100644
--- a/docs/known-issues/pt/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
+++ b/docs/known-issues/pt/creating-custom-fields-for-custom-data-converts-the-ids-to-lowercase.md
@@ -1,5 +1,5 @@
 ---
-title: 'A criação de "custom fields" para "custom data" converte os IDs para letras minúsculas'
+title: "A criação de 'custom fields' para 'custom data' converte os IDs para letras minúsculas"
 id: 6oCXPldEYkC9HG1fw3G3RL
 status: PUBLISHED
 createdAt: 2019-02-19T18:52:45.049Z
diff --git a/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md b/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md
index ed49f6da7..49e07349d 100644
--- a/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md
+++ b/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md
@@ -1,5 +1,5 @@
 ---
-title: 'Crédito ao cliente "Total devido" atualização do valor de acordo com a paginação'
+title: "Crédito ao cliente 'Total devido' atualização do valor de acordo com a paginação"
 id: 6faMqwY8yHsIdYjkwTgCCQ
 status: PUBLISHED
 createdAt: 2022-03-27T20:52:29.371Z
diff --git a/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
index 4b0f6ea44..3e94b035e 100644
--- a/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
+++ b/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -1,5 +1,5 @@
 ---
-title: 'As informações do cliente estão sendo perdidas quando há algum pedido com "profileErrorOnLoading"'
+title: "As informações do cliente estão sendo perdidas quando há algum pedido com 'profileErrorOnLoading'"
 id: 7B0eutLBOCKOun4iwALVpq
 status: PUBLISHED
 createdAt: 2023-06-27T12:51:33.790Z
diff --git a/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md b/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
index 52cebea4a..704b43cd2 100644
--- a/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
+++ b/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
@@ -1,5 +1,5 @@
 ---
-title: '[Ordens que estão em "Aguardando Autorização para Despacho" na VTEX, mas que ainda estão "gastando_de-pagamento" na Dafiti.'
+title: "[Ordens que estão em 'Aguardando Autorização para Despacho' na VTEX, mas que ainda estão 'gastando_de-pagamento' na Dafiti."
 id: 6XbDr2QRAtk0bVAeywagjq
 status: PUBLISHED
 createdAt: 2022-12-20T13:14:31.368Z
diff --git a/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md b/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
index 73819fa71..7966b9c6a 100644
--- a/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
+++ b/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
@@ -1,5 +1,5 @@
 ---
-title: 'A transação DecidirV1 foi "reprocessada" após algumas tentativas de autorização'
+title: "A transação DecidirV1 foi 'reprocessada' após algumas tentativas de autorização"
 id: 2fxfg1IlnFUxAjo9E47HPq
 status: PUBLISHED
 createdAt: 2022-03-03T21:19:22.471Z
diff --git a/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md b/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
index 84f6ec0b4..6ae452d43 100644
--- a/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
+++ b/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'Atraso no processamento da política de expedição (bloqueado no status "processamento")'
+title: "Atraso no processamento da política de expedição (bloqueado no status 'processamento')"
 id: 5wl2TdIbyQeCF8eoo5oYKl
 status: PUBLISHED
 createdAt: 2022-05-17T17:26:58.778Z
diff --git a/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md b/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
index 2c127788a..2fefa9579 100644
--- a/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
+++ b/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
@@ -1,5 +1,5 @@
 ---
-title: 'Valor divergente ao misturar a configuração "paymentSystemToCheckFirstInstallment" e itens divididos'
+title: "Valor divergente ao misturar a configuração 'paymentSystemToCheckFirstInstallment' e itens divididos"
 id: 3h2o69kTBqFdQlzhED2kMN
 status: PUBLISHED
 createdAt: 2023-03-07T18:35:31.215Z
diff --git a/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index 6fcb74e39..65c21949b 100644
--- a/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "Categoria XXX não encontrada no mapeamento de nós de navegação para a especificação do departamento da SKU, escolha uma categoria global mais específica" persistente'
+title: "Erro 'Categoria XXX não encontrada no mapeamento de nós de navegação para a especificação do departamento da SKU, escolha uma categoria global mais específica' persistente"
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
diff --git a/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index 9c50978e8..fd86e892a 100644
--- a/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "não pode criar critérios de busca! erro: o filtro já existe: "brandId" ao criar uma promoção excluindo mais de 1 marca.'
+title: "Erro 'não pode criar critérios de busca! erro: o filtro já existe: 'brandId' ao criar uma promoção excluindo mais de 1 marca."
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
diff --git a/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md b/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
index af306381f..8afcc860a 100644
--- a/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
+++ b/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
@@ -1,5 +1,5 @@
 ---
-title: 'Ordem de assinatura geradora de erro ""O mesmo item não pode ter mais de um SLA selecionado"".'
+title: "Ordem de assinatura geradora de erro ''O mesmo item não pode ter mais de um SLA selecionado''."
 id: 2aBMa8ncalkqSm2s868i1q
 status: PUBLISHED
 createdAt: 2022-09-29T13:31:57.984Z
diff --git a/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
index 245a75039..5b8303523 100644
--- a/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro nas operações de reembolso e captura com divisão de pagamento - "O valor nos destinatários * é diferente do valor da operação *".'
+title: "Erro nas operações de reembolso e captura com divisão de pagamento - 'O valor nos destinatários * é diferente do valor da operação *'."
 id: 3Wo9ltN7Ju0ZqVLAQZcd7m
 status: PUBLISHED
 createdAt: 2023-08-23T13:57:20.424Z
diff --git a/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
index b66f05b6a..7df765803 100644
--- a/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
+++ b/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro no reembolso - "Value cannot be null. Nome do parâmetro: value"'
+title: "Erro no reembolso - 'Value cannot be null. Nome do parâmetro: value'"
 id: 6TZFYB9zb02oMoN5IJMxR3
 status: PUBLISHED
 createdAt: 2024-06-13T18:49:16.797Z
diff --git a/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md b/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md
index 4ab41ce58..1343e88bb 100644
--- a/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md
+++ b/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro integrando sku "O campo não pode ser nulo" - Magalu'
+title: "Erro integrando sku 'O campo não pode ser nulo' - Magalu"
 id: 3SYlRr6XVrl7T3Uw646MkE
 status: PUBLISHED
 createdAt: 2022-08-19T21:01:40.357Z
diff --git a/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
index 3dbf9c6f4..633579032 100644
--- a/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
+++ b/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -1,5 +1,5 @@
 ---
-title: 'Ocorre um erro ao tentar realizar uma pesquisa usando o campo "Todos" no VTEX CRM'
+title: "Ocorre um erro ao tentar realizar uma pesquisa usando o campo 'Todos' no VTEX CRM"
 id: 1OKMTJuUZx6mnDmYW3MBjP
 status: PUBLISHED
 createdAt: 2023-10-25T18:46:48.120Z
diff --git a/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
index 4f2ff0bc0..ea81e7f2d 100644
--- a/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
+++ b/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "Algo deu errado. Tente novamente." ao adicionar imagens pelo Site Editor'
+title: "Erro 'Algo deu errado. Tente novamente.' ao adicionar imagens pelo Site Editor"
 id: r3QVP1kp8HApP83bOi6t9
 status: PUBLISHED
 createdAt: 2023-11-07T22:33:02.296Z
diff --git a/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index 5d90b229a..342a80466 100644
--- a/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -1,5 +1,5 @@
 ---
-title: 'A exportação de imagens de SKU para contas que começam com "h", "t" ou "p" recebe esse corte de caracteres nas linhas de "URL da imagem".'
+title: "A exportação de imagens de SKU para contas que começam com 'h', 't' ou 'p' recebe esse corte de caracteres nas linhas de 'URL da imagem'."
 id: 1IZdnE8IGwkBlbcFhjLrzn
 status: PUBLISHED
 createdAt: 2023-10-13T15:20:49.703Z
diff --git a/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md b/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md
index cd89b876a..9269eaebc 100644
--- a/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md
+++ b/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md
@@ -1,5 +1,5 @@
 ---
-title: 'ey "Enviar Kit:" não está registrando uma mudança no Cartão'
+title: "ey 'Enviar Kit:' não está registrando uma mudança no Cartão"
 id: 4J1SynfbrQqXpSIcveAMxJ
 status: PUBLISHED
 createdAt: 2022-06-14T11:56:12.170Z
diff --git a/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
index 3ff43ed9a..ecf7916d2 100644
--- a/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
+++ b/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -1,5 +1,5 @@
 ---
-title: 'A não adição de dados na etapa "entregar em outro endereço" faz com que o botão "ir para o pagamento" desapareça'
+title: "A não adição de dados na etapa 'entregar em outro endereço' faz com que o botão 'ir para o pagamento' desapareça"
 id: cdZO8gGXDB1JZSj42AnVh
 status: PUBLISHED
 createdAt: 2022-01-24T21:42:52.750Z
diff --git a/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index 553da380d..103305f4e 100644
--- a/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -1,5 +1,5 @@
 ---
-title: 'O campo "Exchanges and returns" (Trocas e devoluções) não está sendo atualizado na IU de gerenciamento do vendedor após o salvamento'
+title: "O campo 'Exchanges and returns' (Trocas e devoluções) não está sendo atualizado na IU de gerenciamento do vendedor após o salvamento"
 id: 1z8LrsbGk5B2ejZ1PV9vaB
 status: PUBLISHED
 createdAt: 2022-11-01T17:47:30.359Z
diff --git a/docs/known-issues/pt/field-reference-always-set-as-null.md b/docs/known-issues/pt/field-reference-always-set-as-null.md
index 9af9c465f..fb3d47fe3 100644
--- a/docs/known-issues/pt/field-reference-always-set-as-null.md
+++ b/docs/known-issues/pt/field-reference-always-set-as-null.md
@@ -1,5 +1,5 @@
 ---
-title: 'O campo "reference" sempre é definido como nulo'
+title: "O campo 'reference' sempre é definido como nulo"
 id: 6Tq4zip0lfUm7vVJdwfZWx
 status: PUBLISHED
 createdAt: 2023-04-26T22:31:38.892Z
diff --git a/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
index ee65018f7..99d9d3753 100644
--- a/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
+++ b/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -1,5 +1,5 @@
 ---
-title: 'O filtro "productClusterIds" é substituído por "productClusterNames" ao aplicar filtros adicionais'
+title: "O filtro 'productClusterIds' é substituído por 'productClusterNames' ao aplicar filtros adicionais"
 id: 3d4BIZQBZgeK3eKwT8B1PZ
 status: PUBLISHED
 createdAt: 2023-09-13T22:42:57.138Z
diff --git a/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md b/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
index 1ec2c5b8f..70f0305ff 100644
--- a/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
+++ b/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
@@ -1,5 +1,5 @@
 ---
-title: 'Filtrar produtos por "Loja" no Catálogo Admin pode mostrar a quantidade errada de resultados'
+title: "Filtrar produtos por 'Loja' no Catálogo Admin pode mostrar a quantidade errada de resultados"
 id: E38Y6a81l7QNtrmh2I2id
 status: PUBLISHED
 createdAt: 2023-02-17T16:01:30.420Z
diff --git a/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md b/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
index 564df17ec..cb0065c8f 100644
--- a/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
+++ b/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
@@ -1,5 +1,5 @@
 ---
-title: 'A primeira busca em uma loja não é considerada na UI "últimas buscas".'
+title: "A primeira busca em uma loja não é considerada na UI 'últimas buscas'."
 id: 7mc9vRE92VGauQmRaK6NnU
 status: PUBLISHED
 createdAt: 2022-05-04T17:08:25.235Z
diff --git a/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md b/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
index 85a9160b5..dcf0ddb6b 100644
--- a/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
+++ b/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: 'Bandeira "Aplicar desconto apenas à opção de remessa mais barata" não funcionando como esperado'
+title: "Bandeira 'Aplicar desconto apenas à opção de remessa mais barata' não funcionando como esperado"
 id: 15irjH6rNkHhkBeRNn9RUI
 status: PUBLISHED
 createdAt: 2022-10-05T18:01:57.821Z
diff --git a/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index 1da7bcecc..b6301b7ad 100644
--- a/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -1,5 +1,5 @@
 ---
-title: 'FOB External Marketplace integra uma ordem (código Erro: "FMT010")'
+title: "FOB External Marketplace integra uma ordem (código Erro: 'FMT010')"
 id: 3qzV4zJRkPIwQnAZuK5dWu
 status: PUBLISHED
 createdAt: 2022-02-25T16:33:49.641Z
diff --git a/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 545f095d4..5700a788f 100644
--- a/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -1,5 +1,5 @@
 ---
-title: 'A API "Obter todas as sugestões de SKU" não mantém a mesma ordem de SKU ao alterar os limites'
+title: "A API 'Obter todas as sugestões de SKU' não mantém a mesma ordem de SKU ao alterar os limites"
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
diff --git a/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
index 53163076d..c278631c7 100644
--- a/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
@@ -1,5 +1,5 @@
 ---
-title: 'GET Product by Refid retorna "Null" quando não é encontrado'
+title: "GET Product by Refid retorna 'Null' quando não é encontrado"
 id: 6yiM9gJT5DB77pZSBNfGZ3
 status: PUBLISHED
 createdAt: 2023-05-16T19:35:46.743Z
diff --git a/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index 5cd43aa74..e843bc359 100644
--- a/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -1,5 +1,5 @@
 ---
-title: 'O hub do Gift Card está adicionando uma contrabarra extra ("/") ao ligar para os fornecedores.'
+title: "O hub do Gift Card está adicionando uma contrabarra extra ('/') ao ligar para os fornecedores."
 id: 2ZstMKKGUbrdXGuhS2Rr1f
 status: PUBLISHED
 createdAt: 2022-09-30T21:07:47.856Z
diff --git a/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
index 195b4f2d8..9a6f57654 100644
--- a/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
+++ b/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cartão-presente - Ele não retorna os campos "caption" e "relationName" quando fazemos uma solicitação get.'
+title: "Cartão-presente - Ele não retorna os campos 'caption' e 'relationName' quando fazemos uma solicitação get."
 id: 2nh2Cc3Hc2Zm0b1INtwDep
 status: PUBLISHED
 createdAt: 2023-06-23T19:33:35.774Z
diff --git a/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md b/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
index 402dce3d0..b5732e792 100644
--- a/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
+++ b/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'HUB Giftcard definindo "R$" como a moeda automática na IU'
+title: "HUB Giftcard definindo 'R$' como a moeda automática na IU"
 id: 2ODtc4t1GSo3iUjT9Gk0uk
 status: PUBLISHED
 createdAt: 2022-11-03T12:57:31.895Z
diff --git a/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md b/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
index e04ec5aab..c962e4f11 100644
--- a/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
+++ b/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
@@ -1,5 +1,5 @@
 ---
-title: 'O botão "Ir para pagamento" não funciona na divisão da entrega ao alternar entre as opções de Entrega e Coleta'
+title: "O botão 'Ir para pagamento' não funciona na divisão da entrega ao alternar entre as opções de Entrega e Coleta"
 id: 4VDxpsWl6N0SjriaqUtXG9
 status: PUBLISHED
 createdAt: 2023-02-17T18:03:49.526Z
diff --git a/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md b/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
index c6a87507e..82bab3624 100644
--- a/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
+++ b/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
@@ -1,5 +1,5 @@
 ---
-title: '"Quantas vezes seu benefício será aplicado em sua loja" Salvando Incorretamente na Interface do Formulário de Promoção'
+title: "'Quantas vezes seu benefício será aplicado em sua loja' Salvando Incorretamente na Interface do Formulário de Promoção"
 id: 6vT0rYIry3cGx1nG5BPkmx
 status: PUBLISHED
 createdAt: 2022-06-28T19:23:30.074Z
diff --git a/docs/known-issues/pt/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md b/docs/known-issues/pt/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
index 7975faf3c..5e0059f45 100644
--- a/docs/known-issues/pt/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
+++ b/docs/known-issues/pt/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
@@ -1,5 +1,5 @@
 ---
-title: 'Link "Não sei meu CEP" na criação de listas de casamento redireciona para a própria página de criação de listas de casamento'
+title: "Link 'Não sei meu CEP' na criação de listas de casamento redireciona para a própria página de criação de listas de casamento"
 id: 59Go6zy62I2iwACQqW8qmA
 status: PUBLISHED
 createdAt: 2018-02-20T22:07:31.331Z
diff --git a/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
index dea1156ac..467da6ae4 100644
--- a/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
+++ b/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -1,5 +1,5 @@
 ---
-title: 'A coleção de importação só aceita a ordem dos produtos se a importação for feita com base no "skuId"'
+title: "A coleção de importação só aceita a ordem dos produtos se a importação for feita com base no 'skuId'"
 id: 7vXi2bDVyGHSMLluQi2ZWZ
 status: PUBLISHED
 createdAt: 2023-12-15T16:35:11.545Z
diff --git a/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md b/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md
index 2e6c2c239..559a58da0 100644
--- a/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md
+++ b/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md
@@ -1,5 +1,5 @@
 ---
-title: 'Formato incorreto do endereço nos endereços de cobrança "Meus Cartões'
+title: "Formato incorreto do endereço nos endereços de cobrança 'Meus Cartões"
 id: 25QxVtMOazrxugHZqFrhSG
 status: PUBLISHED
 createdAt: 2023-04-17T17:40:24.795Z
diff --git a/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
index 19d7890d2..fd3cdb134 100644
--- a/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cálculo incorreto de reembolso na divisão de pagamentos - "O valor nos destinatários * é diferente do valor da operação *."'
+title: "Cálculo incorreto de reembolso na divisão de pagamentos - 'O valor nos destinatários * é diferente do valor da operação *.'"
 id: 7Fxtwnntpmi0DrUD5a603W
 status: PUBLISHED
 createdAt: 2024-07-29T15:07:07.716Z
diff --git a/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
index a7f666c33..e998dea03 100644
--- a/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
+++ b/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -1,5 +1,5 @@
 ---
-title: 'A API Insert SKU File não aceita URLs de servidores que exigem "User Agents"'
+title: "A API Insert SKU File não aceita URLs de servidores que exigem 'User Agents'"
 id: 5Z1PmRXyW78mohsKTMQfzj
 status: PUBLISHED
 createdAt: 2024-07-22T19:49:14.140Z
diff --git a/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md b/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
index 720d4f5fa..4ee51fa95 100644
--- a/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
+++ b/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
@@ -1,5 +1,5 @@
 ---
-title: 'As prestações caem no checkout UI está "solta" quando se rola a tela'
+title: "As prestações caem no checkout UI está 'solta' quando se rola a tela"
 id: 0bbx1aDD7qw3DmaeMOebp
 status: PUBLISHED
 createdAt: 2022-03-10T20:07:05.251Z
diff --git a/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
index a1bc94ed7..ffbf0e4be 100644
--- a/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
+++ b/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -1,5 +1,5 @@
 ---
-title: 'Mensagem "Código postal inválido" na interface do usuário do checkout quando o endereço está em endereços disponíveis com país diferente'
+title: "Mensagem 'Código postal inválido' na interface do usuário do checkout quando o endereço está em endereços disponíveis com país diferente"
 id: 4VggIx4xWPNW6OBIrQ0js4
 status: PUBLISHED
 createdAt: 2024-06-21T17:08:59.860Z
diff --git a/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
index 4fcb39130..f62e526b3 100644
--- a/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
+++ b/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -1,5 +1,5 @@
 ---
-title: 'Caracteres invisíveis em nomes de categorias causam erros de "página não encontrada'
+title: "Caracteres invisíveis em nomes de categorias causam erros de 'página não encontrada"
 id: 4np2BZUF1EmlLmV0KTpnrf
 status: PUBLISHED
 createdAt: 2024-07-05T13:11:13.031Z
diff --git a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
index bda9a9d5b..0a67f64f6 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'Não é possível salvar alguns endereços da Argentina em "Minha Conta".'
+title: "Não é possível salvar alguns endereços da Argentina em 'Minha Conta'."
 id: 6kWZsPNLSDYgmJPDsQOO2w
 status: PUBLISHED
 createdAt: 2022-05-05T14:57:01.624Z
diff --git a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
index 37f2a76b4..bc15ecec1 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'Não é possível salvar alguns endereços do Chile em "Minha Conta".'
+title: "Não é possível salvar alguns endereços do Chile em 'Minha Conta'."
 id: 6DLPSH4eJY0Hbgtc5iGh21
 status: PUBLISHED
 createdAt: 2022-02-24T14:51:08.104Z
diff --git a/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md b/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
index 7d93246ec..732a39f06 100644
--- a/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
+++ b/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
@@ -1,5 +1,5 @@
 ---
-title: '"Texto Grande Indexado" e "Texto Indexado" não sendo alterados pela Importação de Especificação'
+title: "'Texto Grande Indexado' e 'Texto Indexado' não sendo alterados pela Importação de Especificação"
 id: 5ty5q8AfOROtCc8GegzZbd
 status: PUBLISHED
 createdAt: 2022-04-22T17:12:36.962Z
diff --git a/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
index 3366f853c..bb1830009 100644
--- a/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
+++ b/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -1,5 +1,5 @@
 ---
-title: 'O transporte enxuto causa "Algo deu errado" depois de mudar os pontos de coleta'
+title: "O transporte enxuto causa 'Algo deu errado' depois de mudar os pontos de coleta"
 id: 45jQODtjZ4vLXniNJIlQZc
 status: PUBLISHED
 createdAt: 2024-06-20T21:11:53.067Z
diff --git a/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
index 277053d8a..6431d71a8 100644
--- a/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
+++ b/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
@@ -1,5 +1,5 @@
 ---
-title: 'O botão "excluir" da interface do usuário do catálogo legado não funciona'
+title: "O botão 'excluir' da interface do usuário do catálogo legado não funciona"
 id: 2soNSJfiQMZcxlpW6jT2FR
 status: PUBLISHED
 createdAt: 2022-01-23T02:51:17.884Z
diff --git a/docs/known-issues/pt/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md b/docs/known-issues/pt/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
index c7ba983e3..ef4494d9d 100644
--- a/docs/known-issues/pt/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
+++ b/docs/known-issues/pt/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
@@ -1,5 +1,5 @@
 ---
-title: 'Email de "Avise-me" é enviado mesmo quando o produto não está disponível para a política comercial do site'
+title: "Email de 'Avise-me' é enviado mesmo quando o produto não está disponível para a política comercial do site"
 id: 577r3i32P5Yv9QIfVR5AYP
 status: PUBLISHED
 createdAt: 2021-02-22T20:44:52.444Z
diff --git a/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index 993b339c9..e86c5e232 100644
--- a/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -1,5 +1,5 @@
 ---
-title: 'Link "Por que preencher a categoria VTEX Global?" na configuração da categoria só funciona abrindo em uma nova aba'
+title: "Link 'Por que preencher a categoria VTEX Global?' na configuração da categoria só funciona abrindo em uma nova aba"
 id: 3u7aq2otUovQbO98lzjbus
 status: PUBLISHED
 createdAt: 2022-03-16T17:59:14.355Z
diff --git a/docs/known-issues/pt/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md b/docs/known-issues/pt/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
index 7ff43056e..20f5cd183 100644
--- a/docs/known-issues/pt/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
+++ b/docs/known-issues/pt/list-purchases-link-in-the-gift-list-report-does-not-apply-filter-correctly-in-orders-managment.md
@@ -1,5 +1,5 @@
 ---
-title: 'Link "Listar Compras" no relatório de lista de presentes não aplica o filtro corretamente no Gerenciamento de Pedidos'
+title: "Link 'Listar Compras' no relatório de lista de presentes não aplica o filtro corretamente no Gerenciamento de Pedidos"
 id: 5p7nqrzUqIK88cYkkOqMMG
 status: PUBLISHED
 createdAt: 2017-04-03T19:36:10.117Z
diff --git a/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md b/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md
index 69f2407a5..807f3bc6a 100644
--- a/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md
+++ b/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md
@@ -1,5 +1,5 @@
 ---
-title: 'A permissão de "acesso total ao inventário logístico" não funcionou como esperado'
+title: "A permissão de 'acesso total ao inventário logístico' não funcionou como esperado"
 id: 6F11U5C6cULOeJ3Jo5AgAc
 status: PUBLISHED
 createdAt: 2022-04-27T14:16:03.358Z
diff --git a/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 96d6eb2ac..057365b25 100644
--- a/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: ' [Ordem com erro "Referência do objeto não definida para uma instância de um objeto".'
+title: " [Ordem com erro 'Referência do objeto não definida para uma instância de um objeto'."
 id: 6758qSnWuXR6TWQ1mlKOxs
 status: PUBLISHED
 createdAt: 2022-11-29T17:45:30.636Z
diff --git a/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md b/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
index a5df3dda5..52c2fd9d0 100644
--- a/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
+++ b/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
@@ -1,5 +1,5 @@
 ---
-title: '[Pedido FOB integrado com entrega "Convencional".'
+title: "[Pedido FOB integrado com entrega 'Convencional'."
 id: 74uM19UXEopXguM6m0JbOL
 status: PUBLISHED
 createdAt: 2022-12-23T12:40:05.775Z
diff --git a/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 40a3f4dac..16290ea57 100644
--- a/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -1,5 +1,5 @@
 ---
-title: '[Ordem com erro "Referência do objeto não definida para uma instância de um objeto".'
+title: "[Ordem com erro 'Referência do objeto não definida para uma instância de um objeto'."
 id: 72w2GWNOlosoOHhs1ip4dl
 status: PUBLISHED
 createdAt: 2023-03-23T20:11:55.897Z
diff --git a/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md b/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
index 6c66b4c65..2fd28ed5d 100644
--- a/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
+++ b/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
@@ -1,5 +1,5 @@
 ---
-title: 'A conta principal está sendo selecionada como "Merchant.Name" no ambiente da sub-conta'
+title: "A conta principal está sendo selecionada como 'Merchant.Name' no ambiente da sub-conta"
 id: 51coXFBM2wtrJukH3oRESy
 status: PUBLISHED
 createdAt: 2023-03-29T20:54:19.877Z
diff --git a/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
index c9e80cd7c..b49334ed7 100644
--- a/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
+++ b/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -1,5 +1,5 @@
 ---
-title: 'API Match Multiple Received SKUs retornando "Invalid sellerId"'
+title: "API Match Multiple Received SKUs retornando 'Invalid sellerId'"
 id: 60aL2Chds0Jo3m6XMkxmnG
 status: PUBLISHED
 createdAt: 2023-10-17T16:26:27.980Z
diff --git a/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
index 6a632dfbc..c5193f416 100644
--- a/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
+++ b/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -1,5 +1,5 @@
 ---
-title: '"número máximo de itens qualificados para cada carrinho" + more for less aplica desconto incorreto ao usar o mesmo item.'
+title: "'número máximo de itens qualificados para cada carrinho' + more for less aplica desconto incorreto ao usar o mesmo item."
 id: gWIMhi9RCv9BE1RvV6GiM
 status: PUBLISHED
 createdAt: 2024-07-30T17:14:36.972Z
diff --git a/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
index 7d579c917..6fd2d163d 100644
--- a/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
+++ b/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -1,5 +1,5 @@
 ---
-title: 'O MDv2 retorna o erro "504 Gateway Timeout" quando tentamos atualizar um documento passando um símbolo ou caractere especial.'
+title: "O MDv2 retorna o erro '504 Gateway Timeout' quando tentamos atualizar um documento passando um símbolo ou caractere especial."
 id: 6GP5QBWyIAir2oKe08giT2
 status: PUBLISHED
 createdAt: 2023-08-09T13:04:34.819Z
diff --git a/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md b/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
index c5561289a..107169367 100644
--- a/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
+++ b/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
@@ -1,5 +1,5 @@
 ---
-title: '[Meli] Erro de integração do SKU "A cadeia de entrada não estava em um formato correto".'
+title: "[Meli] Erro de integração do SKU 'A cadeia de entrada não estava em um formato correto'."
 id: 2NCm4vLyb1juIuIGMaB048
 status: PUBLISHED
 createdAt: 2022-09-27T21:05:39.320Z
diff --git a/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
index 790c53692..cfe7d22f6 100644
--- a/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
+++ b/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -1,5 +1,5 @@
 ---
-title: 'A integração do MELI está recebendo erros do MELI "429 solicitações demais"'
+title: "A integração do MELI está recebendo erros do MELI '429 solicitações demais'"
 id: 1e4g9nzZFyanywmLbSHq4D
 status: PUBLISHED
 createdAt: 2023-08-03T10:47:41.602Z
diff --git a/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
index 10026ea05..8cf29e181 100644
--- a/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -1,5 +1,5 @@
 ---
-title: 'Códigos postais de integração MELI "11111" Meli - Lima/Perú'
+title: "Códigos postais de integração MELI '11111' Meli - Lima/Perú"
 id: 7ICcek0NOUczgtA65CaZk5
 status: PUBLISHED
 createdAt: 2023-05-16T17:50:38.417Z
diff --git a/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md b/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
index 6c387156f..d87d6f959 100644
--- a/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
+++ b/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
@@ -1,5 +1,5 @@
 ---
-title: '[Integração do SKU com o erro "Referência de objeto não definida para uma instância de um objeto".'
+title: "[Integração do SKU com o erro 'Referência de objeto não definida para uma instância de um objeto'."
 id: 3GNnAidwvASTP223ncqsiV
 status: PUBLISHED
 createdAt: 2022-12-07T11:59:25.793Z
diff --git a/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
index 8a96a389a..5b90b83fa 100644
--- a/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
+++ b/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -1,5 +1,5 @@
 ---
-title: 'As regras de merchandising não estão funcionando para a faceta "productClusterIds"'
+title: "As regras de merchandising não estão funcionando para a faceta 'productClusterIds'"
 id: 6sLODMgjuoyJD52uc0DBW1
 status: PUBLISHED
 createdAt: 2024-07-09T00:02:40.930Z
diff --git a/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md b/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md
index c19452ce6..3e5fffd52 100644
--- a/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md
+++ b/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md
@@ -1,5 +1,5 @@
 ---
-title: 'A mensagem "O valor do frete mudou" é mostrada incorretamente'
+title: "A mensagem 'O valor do frete mudou' é mostrada incorretamente"
 id: 6ct93Q2391vEd0JAt0n5RU
 status: PUBLISHED
 createdAt: 2023-03-21T22:28:23.673Z
diff --git a/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md b/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
index c27214bea..f7aa68e09 100644
--- a/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
+++ b/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
@@ -1,5 +1,5 @@
 ---
-title: 'O campo "MetaTagDescription" não pode ser excluído por meio do Admin'
+title: "O campo 'MetaTagDescription' não pode ser excluído por meio do Admin"
 id: 7h0HlpuQnE8nWylgSWJ1lR
 status: PUBLISHED
 createdAt: 2024-02-08T20:21:00.735Z
diff --git a/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index 01e5dd75d..7c542ea90 100644
--- a/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -1,5 +1,5 @@
 ---
-title: 'Comportamentos incorretos para a mutação addToCart a partir do checkout-graphql enquanto envia "opções" para itens já adicionados'
+title: "Comportamentos incorretos para a mutação addToCart a partir do checkout-graphql enquanto envia 'opções' para itens já adicionados"
 id: 1lMWbgmBsOis9gAKcMm8ob
 status: PUBLISHED
 createdAt: 2022-05-03T20:42:18.655Z
diff --git a/docs/known-issues/pt/my-account-page-does-not-work-on-domain-myvtex-com.md b/docs/known-issues/pt/my-account-page-does-not-work-on-domain-myvtex-com.md
index bf2ef0646..929faca0b 100644
--- a/docs/known-issues/pt/my-account-page-does-not-work-on-domain-myvtex-com.md
+++ b/docs/known-issues/pt/my-account-page-does-not-work-on-domain-myvtex-com.md
@@ -1,5 +1,5 @@
 ---
-title: 'Página de "minha conta" não funciona no domínio "myvtex.com"'
+title: "Página de 'minha conta' não funciona no domínio 'myvtex.com'"
 id: 1EW2Fuwbt3vO9uF8b9zRz4
 status: PUBLISHED
 createdAt: 2019-03-19T13:18:13.540Z
diff --git a/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md b/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
index 98bfd4623..9dcc3cb2e 100644
--- a/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
+++ b/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
@@ -1,5 +1,5 @@
 ---
-title: '"Não é possível inativar este produto porque ele possui um ou mais skus ativos." does not automatically translate on the Product admin'
+title: "'Não é possível inativar este produto porque ele possui um ou mais skus ativos.' does not automatically translate on the Product admin"
 id: 2wYoZ01LtolL1Tfhc4ldV8
 status: PUBLISHED
 createdAt: 2023-04-03T19:17:17.147Z
diff --git a/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
index 2cdd9a57d..8e2a19c36 100644
--- a/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
+++ b/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -1,5 +1,5 @@
 ---
-title: 'O filtro de pedidos não funciona corretamente devido a aspas duplas (") no nome da promoção ou no nome da SKU'
+title: "O filtro de pedidos não funciona corretamente devido a aspas duplas (') no nome da promoção ou no nome da SKU"
 id: 4Qm0akQTQXR8sSbkTDiBL7
 status: PUBLISHED
 createdAt: 2024-06-06T15:42:19.747Z
diff --git a/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md b/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md
index 8a06df005..e708d788a 100644
--- a/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md
+++ b/docs/known-issues/pt/orders-with-error-sistema-de-perfis.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pedidos com erro "Ocorreu um erro de comunicação com o Sistema de Perfis"'
+title: "Pedidos com erro 'Ocorreu um erro de comunicação com o Sistema de Perfis'"
 id: 2vj48Gmty8i4oQuoSOS46y
 status: PUBLISHED
 createdAt: 2017-05-08T20:51:46.084Z
diff --git a/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md
index 15fdee9f9..fdcb3d6d6 100644
--- a/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -1,5 +1,5 @@
 ---
-title: 'O portal não respeita a etiqueta "Principal" da imagem da SKU'
+title: "O portal não respeita a etiqueta 'Principal' da imagem da SKU"
 id: 2ej5V3eIGgkUoo0Omgacc6
 status: CHANGED
 createdAt: 2017-04-17T18:35:42.842Z
diff --git a/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md b/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
index 5ced9da86..b4311721f 100644
--- a/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
+++ b/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
@@ -1,5 +1,5 @@
 ---
-title: ' A "posição" da política comercial depende da página que é mostrada na interface administrativa'
+title: " A 'posição' da política comercial depende da página que é mostrada na interface administrativa"
 id: 3kcSD7J5uuHYGdhBcg1lMa
 status: PUBLISHED
 createdAt: 2022-10-31T20:28:08.565Z
diff --git a/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
index ee599b182..2cf6bf0be 100644
--- a/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
+++ b/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -1,5 +1,5 @@
 ---
-title: 'Filtro de preço aplicado sobre o "preço à vista" em vez do preço normal'
+title: "Filtro de preço aplicado sobre o 'preço à vista' em vez do preço normal"
 id: 2EEgRV1NxYuns4eF7F0ZqD
 status: PUBLISHED
 createdAt: 2024-02-15T19:39:53.576Z
diff --git a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
index ea87aa091..83a1339f7 100644
--- a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
+++ b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -1,5 +1,5 @@
 ---
-title: 'Preços restritos ao valor máximo "Int32" na API Change Price'
+title: "Preços restritos ao valor máximo 'Int32' na API Change Price"
 id: 5mzOjCUYs7vXUkttbsK0za
 status: PUBLISHED
 createdAt: 2022-04-25T17:28:05.159Z
diff --git a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md
index 7a9beed81..59ed71efb 100644
--- a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md
+++ b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md
@@ -1,5 +1,5 @@
 ---
-title: 'Preços restritos a "Int32" valor máximo no checkout APIs'
+title: "Preços restritos a 'Int32' valor máximo no checkout APIs"
 id: 5mzOjCUYs7vXUkttbsK0za
 status: PUBLISHED
 createdAt: 2022-04-25T17:28:05.159Z
diff --git a/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
index 2eab29a6a..7b893005b 100644
--- a/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
+++ b/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -1,5 +1,5 @@
 ---
-title: 'Priorização por "palavra-chave" do produto, sem considerar stopwords'
+title: "Priorização por 'palavra-chave' do produto, sem considerar stopwords"
 id: 55S7nFg61dAyCeGQCIw6aK
 status: PUBLISHED
 createdAt: 2024-05-30T22:05:25.328Z
diff --git a/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md b/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
index 6cff99bc7..93f4c2112 100644
--- a/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
+++ b/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'Problemas ao abrir a página "Gerenciar Inventário" por Admin com erro (UI).'
+title: "Problemas ao abrir a página 'Gerenciar Inventário' por Admin com erro (UI)."
 id: 7owutd1w2Fa2JjgDnn3j5q
 status: PUBLISHED
 createdAt: 2022-03-15T20:14:57.926Z
diff --git a/docs/known-issues/pt/problems-with-price-from-in-the-buttonbuymodal-control.md b/docs/known-issues/pt/problems-with-price-from-in-the-buttonbuymodal-control.md
index 1719cb6e5..35f965255 100644
--- a/docs/known-issues/pt/problems-with-price-from-in-the-buttonbuymodal-control.md
+++ b/docs/known-issues/pt/problems-with-price-from-in-the-buttonbuymodal-control.md
@@ -1,5 +1,5 @@
 ---
-title: 'Problemas com "preço de" no controle "ButtonBuyModal"'
+title: "Problemas com 'preço de' no controle 'ButtonBuyModal'"
 id: 2DdTK2AQNysEqM8AyMwSMQ
 status: PUBLISHED
 createdAt: 2018-10-05T17:06:27.321Z
diff --git a/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 0c4d0fac6..1fe516354 100644
--- a/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -1,5 +1,5 @@
 ---
-title: 'A API de Inserção/Atualização de Produto permite "\n" no campo de textoLink.'
+title: "A API de Inserção/Atualização de Produto permite '\n' no campo de textoLink."
 id: 5TfUw5tTxBEu9HkL3ypBKw
 status: PUBLISHED
 createdAt: 2022-06-28T16:55:53.325Z
diff --git a/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
index 80f2f07d7..67d047176 100644
--- a/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
+++ b/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -1,5 +1,5 @@
 ---
-title: 'A pesquisa "Product name contains" (O nome do produto contém) com mais de um termo não funciona na IU reformulada do catálogo'
+title: "A pesquisa 'Product name contains' (O nome do produto contém) com mais de um termo não funciona na IU reformulada do catálogo"
 id: 2kI6ab0kdpLG6m63ETGGqf
 status: PUBLISHED
 createdAt: 2024-06-05T13:38:38.836Z
diff --git a/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
index b8dae0cf4..8a1400dbb 100644
--- a/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
+++ b/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -1,5 +1,5 @@
 ---
-title: 'Filtro "Product Specification" no Collection Module assumindo valores incorretos'
+title: "Filtro 'Product Specification' no Collection Module assumindo valores incorretos"
 id: 2vg3t5kp7j4Ttla53pVjck
 status: PUBLISHED
 createdAt: 2023-10-26T22:22:44.895Z
diff --git a/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
index 347c1ce08..87e1fc93f 100644
--- a/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
+++ b/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -1,5 +1,5 @@
 ---
-title: 'A importação da especificação do produto com o tipo "texto" não aciona a indexação do produto'
+title: "A importação da especificação do produto com o tipo 'texto' não aciona a indexação do produto"
 id: 5eQB7LCCyDbVNQBQvWti33
 status: PUBLISHED
 createdAt: 2024-03-12T19:36:58.647Z
diff --git a/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md b/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
index 20f309598..281336c13 100644
--- a/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
+++ b/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
@@ -1,5 +1,5 @@
 ---
-title: 'Produtos da "lista de produtos" que têm um duplicado de "itemAcmercadoria" quando a quantidade é aumentada'
+title: "Produtos da 'lista de produtos' que têm um duplicado de 'itemAcmercadoria' quando a quantidade é aumentada"
 id: 4QybxJRoj7wLNvN7NG2FLA
 status: PUBLISHED
 createdAt: 2022-01-24T21:19:51.135Z
diff --git a/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
index bfd9ce2c3..15f22ee55 100644
--- a/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
+++ b/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -1,5 +1,5 @@
 ---
-title: 'Produtos com "unitMultiplier" sinalizados erroneamente como "com promoção" para filtros de pesquisa'
+title: "Produtos com 'unitMultiplier' sinalizados erroneamente como 'com promoção' para filtros de pesquisa"
 id: 2rCi8K01DHsNuYsefE7oR2
 status: PUBLISHED
 createdAt: 2024-02-15T22:52:17.434Z
diff --git a/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
index c2febef23..4dfe6c472 100644
--- a/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
+++ b/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -1,5 +1,5 @@
 ---
-title: 'A compra não pode ser concluída e está travada em "o tipo de frete foi alterado"'
+title: "A compra não pode ser concluída e está travada em 'o tipo de frete foi alterado'"
 id: mgewQ8QmZ3V3dkc7vdJkV
 status: PUBLISHED
 createdAt: 2023-09-25T13:28:28.121Z
diff --git a/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md b/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
index 94806b2c7..96ef4b4b1 100644
--- a/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
+++ b/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
@@ -1,5 +1,5 @@
 ---
-title: 'A compra não pode ser concluída e retorna o erro "o campo do nome do receptor é inválido".'
+title: "A compra não pode ser concluída e retorna o erro 'o campo do nome do receptor é inválido'."
 id: 6ALBFvGzD0SiSuttfXPiQo
 status: PUBLISHED
 createdAt: 2022-05-12T14:53:10.287Z
diff --git a/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md b/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
index be7ca6043..6ebf6dbc9 100644
--- a/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
+++ b/docs/known-issues/pt/receive-and-pickup-tabs-are-displayed-according-to-the-searched-zip-codes-availability.md
@@ -1,5 +1,5 @@
 ---
-title: 'Abas de "Receber | Retirar" são exibidas apenas de acordo com a disponibilidade no CEP buscado'
+title: "Abas de 'Receber | Retirar' são exibidas apenas de acordo com a disponibilidade no CEP buscado"
 id: 5PVGReAvyE0AOcoIq2SeKS
 status: PUBLISHED
 createdAt: 2018-11-21T16:19:00.507Z
diff --git a/docs/known-issues/pt/received-skus-review-tab-missing-products.md b/docs/known-issues/pt/received-skus-review-tab-missing-products.md
index 173e088ae..f7c97130a 100644
--- a/docs/known-issues/pt/received-skus-review-tab-missing-products.md
+++ b/docs/known-issues/pt/received-skus-review-tab-missing-products.md
@@ -1,5 +1,5 @@
 ---
-title: 'Produtos ausentes na guia "Revisão" da Skus recebida'
+title: "Produtos ausentes na guia 'Revisão' da Skus recebida"
 id: 2UM0JQUZVq5o7NHCjmrg8N
 status: PUBLISHED
 createdAt: 2023-11-23T16:30:51.874Z
diff --git a/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index de0f7d42d..4ab302d59 100644
--- a/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,5 +1,5 @@
 ---
-title: 'Regions API não calcula corretamente o "seller 1" ao solicitar sellers que não são white label'
+title: "Regions API não calcula corretamente o 'seller 1' ao solicitar sellers que não são white label"
 id: 20sT9AMMi7Ob5IZc7FeiCB
 status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
diff --git a/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
index 162341f02..0b9a03473 100644
--- a/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
+++ b/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -1,5 +1,5 @@
 ---
-title: 'Os banners de pesquisa não seguem o operador "AND" para condições de acionamento'
+title: "Os banners de pesquisa não seguem o operador 'AND' para condições de acionamento"
 id: 4nQLt5q3Mz2DxvBIyZknXj
 status: PUBLISHED
 createdAt: 2024-06-20T21:17:46.485Z
diff --git a/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md
index 208adb59d..1ef7e71f7 100644
--- a/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md
@@ -1,5 +1,5 @@
 ---
-title: 'Pastas de segundo nível não consideram o "contexto de busca"'
+title: "Pastas de segundo nível não consideram o 'contexto de busca'"
 id: 6WvlorgpBEeIuKk2mprMXm
 status: PUBLISHED
 createdAt: 2019-02-17T19:55:07.529Z
diff --git a/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
index 8b28c7071..cdc8eba97 100644
--- a/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
+++ b/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -1,5 +1,5 @@
 ---
-title: 'A interface do usuário de configurações não atualiza o "período de expiração" das cotações'
+title: "A interface do usuário de configurações não atualiza o 'período de expiração' das cotações"
 id: 4CmuAYwDn7tcCiR9DQHSFb
 status: PUBLISHED
 createdAt: 2023-08-07T19:42:22.810Z
diff --git a/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md b/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md
index b67b9b181..ef34fa090 100644
--- a/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md
+++ b/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md
@@ -1,5 +1,5 @@
 ---
-title: 'Componente de envio trancado no estado "À espera de mais informações".'
+title: "Componente de envio trancado no estado 'À espera de mais informações'."
 id: 7HHlJdZvZ31NgsB7lTShAz
 status: PUBLISHED
 createdAt: 2023-03-29T19:26:05.971Z
diff --git a/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md b/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
index 34d8efb37..a3dd6d00d 100644
--- a/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
+++ b/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
@@ -1,5 +1,5 @@
 ---
-title: 'Política de embarque não priorizada devido ao "Motivo": Dispensada como prioridade" mesmo com melhor custo'
+title: "Política de embarque não priorizada devido ao 'Motivo': Dispensada como prioridade' mesmo com melhor custo"
 id: p1oTHG7CuYITViV4uFZEQ
 status: PUBLISHED
 createdAt: 2022-05-10T18:05:57.097Z
diff --git a/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
index 1dc35a300..3e6337bc9 100644
--- a/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
+++ b/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -1,5 +1,5 @@
 ---
-title: 'A API SKU Insert File não está respondendo com a propriedade "Text".'
+title: "A API SKU Insert File não está respondendo com a propriedade 'Text'."
 id: 2rPsyAkpGNCVIM4yGlcMBw
 status: PUBLISHED
 createdAt: 2024-04-10T14:59:14.341Z
diff --git a/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
index 2b25a7d12..c491780b4 100644
--- a/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
+++ b/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -1,5 +1,5 @@
 ---
-title: '"Algo deu errado" ao adicionar um endereço incompleto e tentar editá-lo'
+title: "'Algo deu errado' ao adicionar um endereço incompleto e tentar editá-lo"
 id: 3rWGAr4K86JAetSBJ75q3h
 status: PUBLISHED
 createdAt: 2024-01-02T21:11:17.425Z
diff --git a/docs/known-issues/pt/special-character-not-mapped-to-be-ignored-in-textlink.md b/docs/known-issues/pt/special-character-not-mapped-to-be-ignored-in-textlink.md
index 7ca7c9aa3..82ded9c57 100644
--- a/docs/known-issues/pt/special-character-not-mapped-to-be-ignored-in-textlink.md
+++ b/docs/known-issues/pt/special-character-not-mapped-to-be-ignored-in-textlink.md
@@ -1,5 +1,5 @@
 ---
-title: 'Caractere especial "|" não mapeado para ser ignorado no TextLink'
+title: "Caractere especial '|' não mapeado para ser ignorado no TextLink"
 id: 5ALFG0CX168qaYUYWecW2q
 status: PUBLISHED
 createdAt: 2017-09-06T20:33:05.265Z
diff --git a/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md b/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md
index e44cf378e..871388301 100644
--- a/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md
+++ b/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md
@@ -1,5 +1,5 @@
 ---
-title: 'Status "ERRO DE PROCESSAMENTO" Política de embarque'
+title: "Status 'ERRO DE PROCESSAMENTO' Política de embarque"
 id: 4g3SWNwDVJG5OeJVP05TOd
 status: PUBLISHED
 createdAt: 2022-05-18T15:12:15.503Z
diff --git a/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 7effbeb13..317445303 100644
--- a/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -1,5 +1,5 @@
 ---
-title: 'StockKeepingUnitByEAN returns 404 for EANs with "/"'
+title: "StockKeepingUnitByEAN returns 404 for EANs with '/'"
 id: Pp3lE5Gu54gOw6liInte4
 status: DRAFT
 createdAt: 2022-02-25T12:23:55.903Z
diff --git a/docs/known-issues/pt/store-texts-search-doesnt-work.md b/docs/known-issues/pt/store-texts-search-doesnt-work.md
index 1811f00ce..2cf95f2d7 100644
--- a/docs/known-issues/pt/store-texts-search-doesnt-work.md
+++ b/docs/known-issues/pt/store-texts-search-doesnt-work.md
@@ -1,5 +1,5 @@
 ---
-title: 'Busca de "Textos da loja" não funciona'
+title: "Busca de 'Textos da loja' não funciona"
 id: 6C6JUkssKcOoQqsaikucwy
 status: PUBLISHED
 createdAt: 2017-08-24T15:16:31.392Z
diff --git a/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md b/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md
index 5a9d0da8f..5457fdc74 100644
--- a/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md
+++ b/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md
@@ -1,5 +1,5 @@
 ---
-title: 'O aplicativo de permissões do Storefront define "documentType" como "cpf"'
+title: "O aplicativo de permissões do Storefront define 'documentType' como 'cpf'"
 id: 1vd0gFWrP50UZacQ0QBKP8
 status: PUBLISHED
 createdAt: 2023-04-27T15:19:53.064Z
diff --git a/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md b/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
index 4ed4070be..88ab92d0a 100644
--- a/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
+++ b/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
@@ -1,5 +1,5 @@
 ---
-title: 'O plano de assinatura está "preso" na "importação" após o carregamento da planilha da associação SKUs'
+title: "O plano de assinatura está 'preso' na 'importação' após o carregamento da planilha da associação SKUs"
 id: 4BVj2X44OZMttG57vUryHb
 status: PUBLISHED
 createdAt: 2022-05-03T00:28:48.118Z
diff --git a/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
index d0ac08436..f589a6c34 100644
--- a/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
+++ b/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -1,5 +1,5 @@
 ---
-title: 'A pesquisa de televendas não aceita caracteres especiais além de "@".'
+title: "A pesquisa de televendas não aceita caracteres especiais além de '@'."
 id: 5eTb6KlR07dOP06BGhovoL
 status: PUBLISHED
 createdAt: 2024-07-29T17:21:34.828Z
diff --git a/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index 44b9ee226..e54910959 100644
--- a/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -1,5 +1,5 @@
 ---
-title: 'Link de texto criado com " " no Marketplace após as aprovações - Reocorrência'
+title: "Link de texto criado com ' ' no Marketplace após as aprovações - Reocorrência"
 id: 2afynQ9MwaHPMPWyhx80Tp
 status: PUBLISHED
 createdAt: 2023-04-24T19:36:10.185Z
diff --git a/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md b/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
index 2f97ede07..4ab743156 100644
--- a/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
+++ b/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
@@ -1,5 +1,5 @@
 ---
-title: 'O aplicativo Cielo 3DS2 está retornando o status "aprovado" mesmo em cenários em que a autenticação falhou.'
+title: "O aplicativo Cielo 3DS2 está retornando o status 'aprovado' mesmo em cenários em que a autenticação falhou."
 id: 58hSiWFhn6sHQofJAUoHqv
 status: PUBLISHED
 createdAt: 2023-05-05T14:48:56.148Z
diff --git a/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md b/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
index 98dd9ecc2..06f0bbbfc 100644
--- a/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
+++ b/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
@@ -1,5 +1,5 @@
 ---
-title: 'O Split de Entrega não será exibido na IU ou em Meus Pedidos, quando o pedido tiver o mesmo "Método de Envio".'
+title: "O Split de Entrega não será exibido na IU ou em Meus Pedidos, quando o pedido tiver o mesmo 'Método de Envio'."
 id: 2VnPyguau8KjpWx09C2vOW
 status: PUBLISHED
 createdAt: 2022-03-15T20:24:32.693Z
diff --git a/docs/known-issues/pt/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md b/docs/known-issues/pt/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md
index 9f4cfae21..fd33f523c 100644
--- a/docs/known-issues/pt/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md
+++ b/docs/known-issues/pt/the-field-administrator-who-approved-the-product-id-does-not-change-when-the-updating-is-done-by-webservice.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campo "Administrador que aprovou o produto (id)" não muda quando a atualização é feita por webservice'
+title: "Campo 'Administrador que aprovou o produto (id)' não muda quando a atualização é feita por webservice"
 id: 5R6Jj0aglq0gUu2OakqgUw
 status: PUBLISHED
 createdAt: 2017-04-11T22:17:03.345Z
diff --git a/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md b/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
index 962ac4f51..f40d9c019 100644
--- a/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
+++ b/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
@@ -1,5 +1,5 @@
 ---
-title: 'A Condição Especial do Banco Emissor está causando para alguns BINs o erro na página de checkout "Banco Emissor para este banco não é aceito".'
+title: "A Condição Especial do Banco Emissor está causando para alguns BINs o erro na página de checkout 'Banco Emissor para este banco não é aceito'."
 id: 7HgNpwcvqQDwSfJfv9KpY8
 status: PUBLISHED
 createdAt: 2022-03-25T19:04:12.310Z
diff --git a/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md b/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
index 221d39642..7788727c2 100644
--- a/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
+++ b/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
@@ -1,5 +1,5 @@
 ---
-title: 'A mensagem "My billing address is ..." (Meu endereço de cobrança é ...) no iFrame do cartão de crédito está no idioma errado ao usar o checkout no idioma catalão'
+title: "A mensagem 'My billing address is ...' (Meu endereço de cobrança é ...) no iFrame do cartão de crédito está no idioma errado ao usar o checkout no idioma catalão"
 id: 3AqPihwDDIM2qixa1jvJmz
 status: PUBLISHED
 createdAt: 2022-03-28T01:11:35.679Z
diff --git a/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index b699fea8e..04c977d23 100644
--- a/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -1,5 +1,5 @@
 ---
-title: 'A opção "Salvar novo cartão" não funciona para provedores de pagamento assíncronos'
+title: "A opção 'Salvar novo cartão' não funciona para provedores de pagamento assíncronos"
 id: 3B4gVSNrSeCc8EBXwk5sAu
 status: PUBLISHED
 createdAt: 2022-03-11T17:54:35.664Z
diff --git a/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index cc86d5dd7..5f77ee787 100644
--- a/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -1,5 +1,5 @@
 ---
-title: 'O modelo "relatorio-de-importacao-de-estoque" não suporta multi-linguagem'
+title: "O modelo 'relatorio-de-importacao-de-estoque' não suporta multi-linguagem"
 id: 5R8b0jnibOQdXupo0hIyts
 status: PUBLISHED
 createdAt: 2022-05-25T18:25:43.394Z
diff --git a/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md b/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
index cbaa7d2ac..cac9b7f42 100644
--- a/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
+++ b/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
@@ -1,5 +1,5 @@
 ---
-title: 'Transação cancelada por tempo limite: "Timeout sem pedido para o Sistema de Parcelamento".'
+title: "Transação cancelada por tempo limite: 'Timeout sem pedido para o Sistema de Parcelamento'."
 id: 68L2ka1QJ3yEHTsId1arF7
 status: PUBLISHED
 createdAt: 2022-03-02T12:15:17.495Z
diff --git a/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
index f1d9a27a4..61a97d290 100644
--- a/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
+++ b/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro de cancelamento de transação com a mensagem "Unreachable code" (código inacessível)'
+title: "Erro de cancelamento de transação com a mensagem 'Unreachable code' (código inacessível)"
 id: 2Y4joZlyDhbNWU9ycw32U3
 status: PUBLISHED
 createdAt: 2024-03-12T16:34:10.113Z
diff --git a/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
index fcb225f88..1ee55fc53 100644
--- a/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
+++ b/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -1,5 +1,5 @@
 ---
-title: 'A interface do usuário mostra "Presentes escolhidos!" ao usar o recurso de substituição de pedidos'
+title: "A interface do usuário mostra 'Presentes escolhidos!' ao usar o recurso de substituição de pedidos"
 id: 4efm7L6hQhad98uYkjzrXO
 status: PUBLISHED
 createdAt: 2023-09-27T20:57:46.944Z
diff --git a/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md b/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
index 5302db58a..aef2c13a3 100644
--- a/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
+++ b/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
@@ -1,5 +1,5 @@
 ---
-title: 'Incapaz de mudar o status no gateway quando a transação Cart objeto em /transação é "desconhecido".'
+title: "Incapaz de mudar o status no gateway quando a transação Cart objeto em /transação é 'desconhecido'."
 id: 3gWqk1T2xP3eRYZtXZLX3b
 status: PUBLISHED
 createdAt: 2023-03-23T14:27:16.116Z
diff --git a/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md b/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md
index b3c413f6d..604a047e1 100644
--- a/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md
+++ b/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md
@@ -1,5 +1,5 @@
 ---
-title: 'Unable to create "Produtos Relacionados" Custom Element'
+title: "Unable to create 'Produtos Relacionados' Custom Element"
 id: 4Ca3b0mfpe20K7wSaImSQj
 status: PUBLISHED
 createdAt: 2022-01-21T14:44:26.429Z
diff --git a/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
index 7f82376a2..627f6f306 100644
--- a/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
+++ b/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
@@ -1,5 +1,5 @@
 ---
-title: 'Erro "Unhandled exception" ao alterar a edição da conta'
+title: "Erro 'Unhandled exception' ao alterar a edição da conta"
 id: 1NVjCrlRkadscl8fW9rOdA
 status: PUBLISHED
 createdAt: 2023-09-26T12:45:44.999Z
diff --git a/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md b/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md
index 70eb5098f..4b12f69c0 100644
--- a/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md
+++ b/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md
@@ -1,5 +1,5 @@
 ---
-title: 'Campo "Url Logo" no campo "Update Seller Request not Updating".'
+title: "Campo 'Url Logo' no campo 'Update Seller Request not Updating'."
 id: 1WmNl3RgesWAUL8rjitJV1
 status: PUBLISHED
 createdAt: 2022-01-21T15:18:15.945Z
diff --git a/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
index 39143a1e5..465d6d519 100644
--- a/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
+++ b/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -1,5 +1,5 @@
 ---
-title: 'O usuário apenas com a função "User Administrator - RESTRICTED" não consegue listar os usuários'
+title: "O usuário apenas com a função 'User Administrator - RESTRICTED' não consegue listar os usuários"
 id: ifXUAzgJ1xr8ezhqKpRUI
 status: PUBLISHED
 createdAt: 2023-11-08T18:07:14.508Z
diff --git a/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
index 04dcb642e..dfe8ea04d 100644
--- a/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
+++ b/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -1,5 +1,5 @@
 ---
-title: 'Autor da versão "Note: Not found on VTEX ID." no perfil'
+title: "Autor da versão 'Note: Not found on VTEX ID.' no perfil"
 id: 0X6Aj6YdCXXfNweAkDS46
 status: PUBLISHED
 createdAt: 2023-10-04T21:48:14.699Z
diff --git a/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md b/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
index ba5d16c21..632e6b434 100644
--- a/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
@@ -1,5 +1,5 @@
 ---
-title: ' O recurso "Produto visitado" não funciona corretamente'
+title: " O recurso 'Produto visitado' não funciona corretamente"
 id: 5AiCVwLkGToEgtLkZVPe5i
 status: PUBLISHED
 createdAt: 2022-11-25T18:45:15.389Z
diff --git a/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md b/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md
index cd07df9ec..7ddbadd38 100644
--- a/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md
+++ b/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md
@@ -1,5 +1,5 @@
 ---
-title: '<vtex:contentPlaceHolder id="Acessorios"/> não está funcionando'
+title: "<vtex:contentPlaceHolder id='Acessorios'/> não está funcionando"
 id: 7x8f0vGaunX1P3EFJGCYaz
 status: PUBLISHED
 createdAt: 2022-01-23T02:24:12.606Z
diff --git a/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 3ae5a632f..4f193e236 100644
--- a/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -1,5 +1,5 @@
 ---
-title: 'Ao adicionar um SKU através de nossa funcionalidade "Change Order", o nome do produto não é exibido no pedido e na notificação por e-mail'
+title: "Ao adicionar um SKU através de nossa funcionalidade 'Change Order', o nome do produto não é exibido no pedido e na notificação por e-mail"
 id: 35Q3KoOSsUr9n9XEDIk7nk
 status: PUBLISHED
 createdAt: 2022-04-07T14:53:35.829Z
diff --git a/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index 046ed61d8..9c874336d 100644
--- a/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -1,5 +1,5 @@
 ---
-title: 'Ao carregar a página "Mapeamento do Catálogo" em admin a mensagem inicial não é traduzida'
+title: "Ao carregar a página 'Mapeamento do Catálogo' em admin a mensagem inicial não é traduzida"
 id: 4WszmRZ5jpeSDNTEuFIdwF
 status: PUBLISHED
 createdAt: 2022-12-15T12:32:17.741Z
diff --git a/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 624998deb..271a7df09 100644
--- a/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -1,5 +1,5 @@
 ---
-title: 'Quando o acordo é enviado tão nulo e codificado como "reembolso-manual", nosso gateway realiza um duplo reembolso.'
+title: "Quando o acordo é enviado tão nulo e codificado como 'reembolso-manual', nosso gateway realiza um duplo reembolso."
 id: 2PdRRjHDODY2Tk0VItO4Fo
 status: PUBLISHED
 createdAt: 2022-07-11T17:37:43.961Z
diff --git a/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md b/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md
index 14aa21db0..114c8e107 100644
--- a/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md
+++ b/docs/known-issues/pt/xml-currency-symbol-in-the-installment.md
@@ -1,5 +1,5 @@
 ---
-title: ' XML - Símbolo de moeda em campo "Parcelamento"'
+title: " XML - Símbolo de moeda em campo 'Parcelamento'"
 id: 4s7hBA1MAUgeEC2Q4K8gKM
 status: DRAFT
 createdAt: 2017-06-26T15:22:31.980Z
diff --git a/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
index a35eada4b..d91d5d9e0 100644
--- a/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
+++ b/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
@@ -1,5 +1,5 @@
 ---
-title: 'O sinalizador "Nome do produto" do XML não está funcionando corretamente'
+title: "O sinalizador 'Nome do produto' do XML não está funcionando corretamente"
 id: 6YDbpRns3LCN02bVKM8aaf
 status: PUBLISHED
 createdAt: 2023-10-26T11:35:14.500Z
diff --git a/docs/tutorials/en/configuring-a-registered-boleto.md b/docs/tutorials/en/configuring-a-registered-boleto.md
index 586688ece..cc5ed3e25 100644
--- a/docs/tutorials/en/configuring-a-registered-boleto.md
+++ b/docs/tutorials/en/configuring-a-registered-boleto.md
@@ -1,5 +1,5 @@
 ---
-title: 'Configuring a registered "boleto" (Brazilian off-line payment method)'
+title: "Configuring a registered 'boleto' (Brazilian off-line payment method)"
 id: frequentlyAskedQuestions_2867
 status: DRAFT
 createdAt: 2019-01-24T20:46:00.197Z
diff --git a/docs/tutorials/en/configuring-a-santander-registered-boleto.md b/docs/tutorials/en/configuring-a-santander-registered-boleto.md
index bfc7d0d20..0fdbe1cb6 100644
--- a/docs/tutorials/en/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/en/configuring-a-santander-registered-boleto.md
@@ -1,5 +1,5 @@
 ---
-title: 'Configuring a Santander registered "boleto"'
+title: "Configuring a Santander registered 'boleto'"
 id: 67siNqkC7mcgy2GWUYimaa
 status: DRAFT
 createdAt: 2017-12-04T19:04:02.215Z
diff --git a/docs/tutorials/en/how-do-i-request-a-duplicate-of-my-boleto.md b/docs/tutorials/en/how-do-i-request-a-duplicate-of-my-boleto.md
index 2330da255..d12a07d2b 100644
--- a/docs/tutorials/en/how-do-i-request-a-duplicate-of-my-boleto.md
+++ b/docs/tutorials/en/how-do-i-request-a-duplicate-of-my-boleto.md
@@ -1,5 +1,5 @@
 ---
-title: 'How do I request a duplicate of my "boleto"?'
+title: "How do I request a duplicate of my 'boleto'?"
 id: 5uIetorejSECKuyS2068mG
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:47.207Z
diff --git a/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md b/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
index 39a1bebb2..fab1e1453 100644
--- a/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
+++ b/docs/tutorials/en/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
@@ -1,5 +1,5 @@
 ---
-title: 'How long does it take to cancel an order with an unpaid "boleto"?'
+title: "How long does it take to cancel an order with an unpaid 'boleto'?"
 id: frequentlyAskedQuestions_300
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:51.983Z
diff --git a/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index 9794b53d3..c3cd57359 100644
--- a/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -1,5 +1,5 @@
 ---
-title: 'How to set up the "Responsible for pick up" field in SmartCheckout™ V6'
+title: "How to set up the 'Responsible for pick up' field in SmartCheckout™ V6"
 id: 2GsFnXUJxSOYEE6U2c4Syw
 status: PUBLISHED
 createdAt: 2018-11-09T12:18:14.596Z
diff --git a/docs/tutorials/en/inserting-images-into-let-me-know-email.md b/docs/tutorials/en/inserting-images-into-let-me-know-email.md
index 378015b7c..634e9734e 100644
--- a/docs/tutorials/en/inserting-images-into-let-me-know-email.md
+++ b/docs/tutorials/en/inserting-images-into-let-me-know-email.md
@@ -1,5 +1,5 @@
 ---
-title: 'Inserting images into "Let Me Know" email'
+title: "Inserting images into 'Let Me Know' email"
 id: 3soCXGcE3XBPsnPhxJh2DY
 status: PUBLISHED
 createdAt: 2019-02-21T19:52:16.679Z
diff --git a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
index 2835aae6f..35518e8d3 100644
--- a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -1,5 +1,5 @@
 ---
-title: 'How to remove the error message "Request headers must only contain ASCII characters"'
+title: "How to remove the error message 'Request headers must only contain ASCII characters'"
 id: 19psKZvLXrBqqK1bPaTIHG
 status: PUBLISHED
 createdAt: 2024-07-25T16:54:41.663Z
diff --git a/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md b/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
index dcb89c290..3f1836f65 100644
--- a/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
+++ b/docs/tutorials/en/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
@@ -1,5 +1,5 @@
 ---
-title: 'Setting up Provu (Lendico) "boleto" in installments as a payment method (Brazilian off-line payment method)'
+title: "Setting up Provu (Lendico) 'boleto' in installments as a payment method (Brazilian off-line payment method)"
 id: 1pRpPlkppLDEc1TVXTgrcu
 status: DRAFT
 createdAt: 2020-12-02T10:58:09.076Z
diff --git a/docs/tutorials/en/why-is-the-order-in-the-verifying-invoice-status.md b/docs/tutorials/en/why-is-the-order-in-the-verifying-invoice-status.md
index 3c6c095bc..1ecca2dea 100644
--- a/docs/tutorials/en/why-is-the-order-in-the-verifying-invoice-status.md
+++ b/docs/tutorials/en/why-is-the-order-in-the-verifying-invoice-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'Why is the order in the "Verifying Invoice" status?'
+title: "Why is the order in the 'Verifying Invoice' status?"
 id: 5VJjxRjeH6SimiG0Wkk2gm
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:44.680Z
diff --git a/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index a6fb2b281..f310387f1 100644
--- a/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cómo configurar el campo "Responsable de la recogida" en SmartCheckout™ V6'
+title: "Cómo configurar el campo 'Responsable de la recogida' en SmartCheckout™ V6"
 id: 2GsFnXUJxSOYEE6U2c4Syw
 status: PUBLISHED
 createdAt: 2018-11-09T12:18:14.596Z
diff --git a/docs/tutorials/es/inserting-images-into-let-me-know-email.md b/docs/tutorials/es/inserting-images-into-let-me-know-email.md
index 135f95116..ffdc152c4 100644
--- a/docs/tutorials/es/inserting-images-into-let-me-know-email.md
+++ b/docs/tutorials/es/inserting-images-into-let-me-know-email.md
@@ -1,5 +1,5 @@
 ---
-title: 'Insertar imágenes en el email de "Avisame"'
+title: "Insertar imágenes en el email de 'Avisame'"
 id: 3soCXGcE3XBPsnPhxJh2DY
 status: PUBLISHED
 createdAt: 2019-02-21T19:52:16.679Z
diff --git a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
index 8f12920e8..70567901f 100644
--- a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -1,5 +1,5 @@
 ---
-title: 'Cómo remover el mensaje de error "Request headers must contain only ASCII characters"'
+title: "Cómo remover el mensaje de error 'Request headers must contain only ASCII characters'"
 id: 19psKZvLXrBqqK1bPaTIHG
 status: PUBLISHED
 createdAt: 2024-07-25T16:54:41.663Z
diff --git a/docs/tutorials/es/why-is-the-order-in-the-verifying-invoice-status.md b/docs/tutorials/es/why-is-the-order-in-the-verifying-invoice-status.md
index 55b98556c..613eb2da0 100644
--- a/docs/tutorials/es/why-is-the-order-in-the-verifying-invoice-status.md
+++ b/docs/tutorials/es/why-is-the-order-in-the-verifying-invoice-status.md
@@ -1,5 +1,5 @@
 ---
-title: '¿Por qué el pedido se encuentra en el status "Verificando fatura"?'
+title: "¿Por qué el pedido se encuentra en el status 'Verificando fatura'?"
 id: 5VJjxRjeH6SimiG0Wkk2gm
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:44.680Z
diff --git a/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index b9dbfad7d..091692c60 100644
--- a/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -1,5 +1,5 @@
 ---
-title: 'Como configurar o campo "Responsável pela retirada" no SmartCheckout™ V6'
+title: "Como configurar o campo 'Responsável pela retirada' no SmartCheckout™ V6"
 id: 2GsFnXUJxSOYEE6U2c4Syw
 status: PUBLISHED
 createdAt: 2018-11-09T12:18:14.596Z
diff --git a/docs/tutorials/pt/inserting-images-into-let-me-know-email.md b/docs/tutorials/pt/inserting-images-into-let-me-know-email.md
index e1b72dda7..609c97313 100644
--- a/docs/tutorials/pt/inserting-images-into-let-me-know-email.md
+++ b/docs/tutorials/pt/inserting-images-into-let-me-know-email.md
@@ -1,5 +1,5 @@
 ---
-title: 'Inserir imagens no email de "Avise-me"'
+title: "Inserir imagens no email de 'Avise-me'"
 id: 3soCXGcE3XBPsnPhxJh2DY
 status: PUBLISHED
 createdAt: 2019-02-21T19:52:16.679Z
diff --git a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
index 7a11bcfda..de152f8bb 100644
--- a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -1,5 +1,5 @@
 ---
-title: 'Como remover a mensagem de erro "Request headers must contain only ASCII characters"'
+title: "Como remover a mensagem de erro 'Request headers must contain only ASCII characters'"
 id: 19psKZvLXrBqqK1bPaTIHG
 status: PUBLISHED
 createdAt: 2024-07-25T16:54:41.663Z
diff --git a/docs/tutorials/pt/why-is-the-order-in-the-verifying-invoice-status.md b/docs/tutorials/pt/why-is-the-order-in-the-verifying-invoice-status.md
index 928a93167..f29737560 100644
--- a/docs/tutorials/pt/why-is-the-order-in-the-verifying-invoice-status.md
+++ b/docs/tutorials/pt/why-is-the-order-in-the-verifying-invoice-status.md
@@ -1,5 +1,5 @@
 ---
-title: 'Por que o pedido está no status "Verificando fatura"?'
+title: "Por que o pedido está no status 'Verificando fatura'?"
 id: 5VJjxRjeH6SimiG0Wkk2gm
 status: PUBLISHED
 createdAt: 2019-01-24T20:45:44.680Z

From a8f22f20d24cc51384e4741427120d5ebcfbce71 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 16:14:57 -0300
Subject: [PATCH 07/13] fix quotation marks

---
 ...ounts-with-on-the-name-dont-have-metrics-on-search-report.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md b/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
index ba51272e7..a2702c26e 100644
--- a/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
+++ b/docs/known-issues/en/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
@@ -1,5 +1,5 @@
 ---
-title: "Accounts with "-' on the name don't have metrics on search report"
+title: "Accounts with '-' on the name don't have metrics on search report"
 id: 71rVz43g0rgIN7Joe4GEj6
 status: PUBLISHED
 createdAt: 2023-04-19T17:35:28.560Z

From 4b8a6d9cd1ee28bb42660842f16d52a69933dc20 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 16:30:06 -0300
Subject: [PATCH 08/13] fix quotation marks

---
 ...address-field-comes-with-null-vaule-in-payments-api-query.md | 2 +-
 ...tions-api-doesnt-keep-same-sku-order-when-changing-limits.md | 2 +-
 ...split-when-switching-between-delivery-and-pick-up-options.md | 2 +-
 ...ion-page-is-redirecting-to-the-wedding-list-creation-page.md | 2 +-
 ...he-product-is-not-available-for-the-websites-trade-policy.md | 2 +-
 ...-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md | 2 +-
 docs/known-issues/en/store-texts-search-doesnt-work.md          | 2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md b/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md
index 13facb65c..3f365b5bb 100644
--- a/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md
+++ b/docs/known-issues/en/address-field-comes-with-null-vaule-in-payments-api-query.md
@@ -1,5 +1,5 @@
 ---
-title: ""Address" field comes with "null' vaule in Payment's API query"
+title: "'Address' field comes with 'null' vaule in Payment's API query"
 id: 7oEEc24umACsOoy4Ceso2W
 status: PUBLISHED
 createdAt: 2018-01-11T16:33:01.231Z
diff --git a/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 9abed7fcf..8b16f0301 100644
--- a/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/en/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -1,5 +1,5 @@
 ---
-title: ""Get all SKU suggestions' API doesn't keep same sku order when changing limits"
+title: "'Get all SKU suggestions' API doesn't keep same sku order when changing limits"
 id: 4wQbZm9rFc8iD2xYwEiAlQ
 status: PUBLISHED
 createdAt: 2022-12-05T14:49:46.856Z
diff --git a/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md b/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
index 25c5e0726..75b14f245 100644
--- a/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
+++ b/docs/known-issues/en/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
@@ -1,5 +1,5 @@
 ---
-title: ""Go to payment' button doesn't work in delivery split when switching between Delivery and Pick up options"
+title: "'Go to payment' button doesn't work in delivery split when switching between Delivery and Pick up options"
 id: 4VDxpsWl6N0SjriaqUtXG9
 status: PUBLISHED
 createdAt: 2023-02-17T18:03:49.526Z
diff --git a/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md b/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
index 56abdf282..7b08789e0 100644
--- a/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
+++ b/docs/known-issues/en/i-dont-know-my-zip-code-link-in-the-wedding-list-creation-page-is-redirecting-to-the-wedding-list-creation-page.md
@@ -1,5 +1,5 @@
 ---
-title: ""I don't know my ZIP code' link in the wedding list creation page is redirecting to the wedding list creation page"
+title: "'I don't know my ZIP code' link in the wedding list creation page is redirecting to the wedding list creation page"
 id: 59Go6zy62I2iwACQqW8qmA
 status: PUBLISHED
 createdAt: 2018-02-20T22:07:31.331Z
diff --git a/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md b/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
index 0017f3ea4..37e1febc0 100644
--- a/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
+++ b/docs/known-issues/en/let-me-know-email-is-sent-even-when-the-product-is-not-available-for-the-websites-trade-policy.md
@@ -1,5 +1,5 @@
 ---
-title: ""Let me know' email is sent even when the product is not available for the website's trade policy"
+title: "'Let me know' email is sent even when the product is not available for the website's trade policy"
 id: 577r3i32P5Yv9QIfVR5AYP
 status: PUBLISHED
 createdAt: 2021-02-22T20:44:52.444Z
diff --git a/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
index ece515333..1832851e3 100644
--- a/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
+++ b/docs/known-issues/en/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -1,5 +1,5 @@
 ---
-title: ""Product name contains' search with more than one term doesn't work on catalog's redesigned UI"
+title: "'Product name contains' search with more than one term doesn't work on catalog's redesigned UI"
 id: 2kI6ab0kdpLG6m63ETGGqf
 status: PUBLISHED
 createdAt: 2024-06-05T13:38:38.836Z
diff --git a/docs/known-issues/en/store-texts-search-doesnt-work.md b/docs/known-issues/en/store-texts-search-doesnt-work.md
index a560efc73..a72f33fdf 100644
--- a/docs/known-issues/en/store-texts-search-doesnt-work.md
+++ b/docs/known-issues/en/store-texts-search-doesnt-work.md
@@ -1,5 +1,5 @@
 ---
-title: ""Store texts' search doesn't work"
+title: "'Store texts' search doesn't work"
 id: 6C6JUkssKcOoQqsaikucwy
 status: PUBLISHED
 createdAt: 2017-08-24T15:16:31.392Z

From 80947dfc66797625be3fcb256c9e34983c9b0de9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Mon, 5 Aug 2024 18:11:53 -0300
Subject: [PATCH 09/13] fix quotation marks

---
 .../en/my-orders-is-now-available-on-extension-store.md     | 2 +-
 ...hen-set-to-calculate-during-the-first-hour-of-the-day.md | 2 +-
 ...mail-is-not-being-placed-as-expected-in-the-orderform.md | 2 +-
 ...x-requires-authentication-doesnt-work-on-pages-module.md | 2 +-
 ...on-choose-a-more-specific-global-category-persistente.md | 2 +-
 ...when-creating-a-promotion-excluding-more-than-1-brand.md | 2 +-
 ...-ht-or-p-get-this-character-cut-in-the-image-url-rows.md | 2 +-
 .../portal-dont-respect-the-tag-principal-of-skus-image.md  | 2 +-
 ...ization-by-products-keyword-not-considering-stopwords.md | 2 +-
 ...-be-finished-and-is-stuck-on-freight-type-has-changed.md | 2 +-
 ...-and-returns-the-error-receiver-name-field-is-invalid.md | 2 +-
 ...er-1-correctly-while-requesting-nonwhitelabel-sellers.md | 2 +-
 .../secondlevel-folders-dont-consider-the-search-context.md | 2 +-
 ...settings-ui-doesnt-update-expiration-period-of-quotes.md | 2 +-
 ...es-search-doesnt-accept-special-characters-aside-from.md | 2 +-
 .../en/xmls-product-name-flag-not-working-properly.md       | 2 +-
 ...-ht-or-p-get-this-character-cut-in-the-image-url-rows.md | 6 +++---
 .../portal-dont-respect-the-tag-principal-of-skus-image.md  | 6 +++---
 18 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/docs/announcements/en/my-orders-is-now-available-on-extension-store.md b/docs/announcements/en/my-orders-is-now-available-on-extension-store.md
index 5eb2f109b..e7505b4c0 100644
--- a/docs/announcements/en/my-orders-is-now-available-on-extension-store.md
+++ b/docs/announcements/en/my-orders-is-now-available-on-extension-store.md
@@ -12,7 +12,7 @@ slug: my-orders-is-now-available-on-extension-store
 locale: en
 legacySlug: my-orders-is-now-available-on-extension-store
 announcementImageID: ''
-announcementSynopsisEN: "Starting June 5, the use of the "My Orders" page's extension will be required for all stores."
+announcementSynopsisEN: "Starting June 5, the use of the 'My Orders' page's extension will be required for all stores."
 ---
 
 <div class="alert alert-info">
diff --git a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
index 5a080e11e..ca704bae9 100644
--- a/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
+++ b/docs/known-issues/en/automatic-field-doesnt-calculate-the-field-correctly-when-set-to-calculate-during-the-first-hour-of-the-day.md
@@ -1,5 +1,5 @@
 ---
-title: "Automatic field doesn't calculate the field correctly when set to "Calculate during the first hour of the day'"
+title: "Automatic field doesn't calculate the field correctly when set to 'Calculate during the first hour of the day'"
 id: 6DieNCI6paEUeg06cKsCYI
 status: PUBLISHED
 createdAt: 2018-12-17T18:37:45.246Z
diff --git a/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
index 377a14c50..b4c5efe76 100644
--- a/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
+++ b/docs/known-issues/en/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -1,5 +1,5 @@
 ---
-title: "Cart created from an "order again' option in My Orders, the customer's email is not being placed as expected in the orderForm"
+title: "Cart created from an 'order again' option in My Orders, the customer's email is not being placed as expected in the orderForm"
 id: 6dDhkaIhquOqaDuNkVZuln
 status: PUBLISHED
 createdAt: 2023-12-04T22:41:21.385Z
diff --git a/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md b/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md
index f1245a12e..dc9aabd67 100644
--- a/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md
+++ b/docs/known-issues/en/checkbox-requires-authentication-doesnt-work-on-pages-module.md
@@ -1,5 +1,5 @@
 ---
-title: "Checkbox "Requires authentication' doesn't work on Pages module"
+title: "Checkbox 'Requires authentication' doesn't work on Pages module"
 id: 6nKuqSmk7JZgdaAysNYls3
 status: PUBLISHED
 createdAt: 2022-05-11T21:25:07.700Z
diff --git a/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index a86f11590..7137210c8 100644
--- a/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/en/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -1,5 +1,5 @@
 ---
-title: "Erro "Category XXX not found in browse node mapping for SKU's department specification, choose a more specific global category' persistente"
+title: "Erro 'Category XXX not found in browse node mapping for SKU's department specification, choose a more specific global category' persistente"
 id: 4DCJmkRvgh3qUYP9HYgtg2
 status: PUBLISHED
 createdAt: 2022-03-10T17:58:42.674Z
diff --git a/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index aa5b58eb0..9a9428484 100644
--- a/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/en/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -1,5 +1,5 @@
 ---
-title: "Error "can't create search criteria! error: filter already exists:"brandId"' when creating a promotion excluding more than 1 brand."
+title: "Error 'can't create search criteria! error: filter already exists: 'brandId' when creating a promotion excluding more than 1 brand"
 id: 6s6cvYpImIBEH0SLqE3J2U
 status: PUBLISHED
 createdAt: 2022-09-22T15:53:15.001Z
diff --git a/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index a4ffd900c..b821d888d 100644
--- a/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/en/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -1,5 +1,5 @@
 ---
-title: "Exporting SKU images for accounts starting with 'h','t' or 'p' get this character cut in the "Image URL' rows."
+title: "Exporting SKU images for accounts starting with 'h','t' or 'p' get this character cut in the 'Image URL' rows."
 id: 1IZdnE8IGwkBlbcFhjLrzn
 status: PUBLISHED
 createdAt: 2023-10-13T15:20:49.703Z
diff --git a/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md
index 2084937ff..f263aa38f 100644
--- a/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/en/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -1,5 +1,5 @@
 ---
-title: "Portal don't respect the tag "Principal' of SKU's Image"
+title: "Portal don't respect the tag 'Principal' of SKU's Image"
 id: 2ej5V3eIGgkUoo0Omgacc6
 status: CHANGED
 createdAt: 2017-04-17T18:35:42.842Z
diff --git a/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
index 91a78764a..90263ee1a 100644
--- a/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
+++ b/docs/known-issues/en/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -1,5 +1,5 @@
 ---
-title: "Prioritization by product's "keyword' not considering stopwords"
+title: "Prioritization by product's 'keyword' not considering stopwords"
 id: 55S7nFg61dAyCeGQCIw6aK
 status: PUBLISHED
 createdAt: 2024-05-30T22:05:25.328Z
diff --git a/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
index dd00861c3..8e3577459 100644
--- a/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
+++ b/docs/known-issues/en/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -1,5 +1,5 @@
 ---
-title: "Purchase can't be finished and is stuck on "freight type has changed'"
+title: "Purchase can't be finished and is stuck on 'freight type has changed'"
 id: mgewQ8QmZ3V3dkc7vdJkV
 status: PUBLISHED
 createdAt: 2023-09-25T13:28:28.121Z
diff --git a/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md b/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
index d00ecb2b9..9b9e40061 100644
--- a/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
+++ b/docs/known-issues/en/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
@@ -1,5 +1,5 @@
 ---
-title: "Purchase can't be finished and returns the error "receiver name field is invalid'"
+title: "Purchase can't be finished and returns the error 'receiver name field is invalid'"
 id: 6ALBFvGzD0SiSuttfXPiQo
 status: PUBLISHED
 createdAt: 2022-05-12T14:53:10.287Z
diff --git a/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 125ce2d8f..feca39c52 100644
--- a/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/en/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -1,5 +1,5 @@
 ---
-title: "Regions API doesn't calculate the "seller 1' correctly while requesting non-whitelabel sellers"
+title: "Regions API doesn't calculate the 'seller 1' correctly while requesting non-whitelabel sellers"
 id: 20sT9AMMi7Ob5IZc7FeiCB
 status: DRAFT
 createdAt: 2022-03-28T20:45:27.687Z
diff --git a/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
index d4e0defdd..366ae687e 100644
--- a/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
@@ -1,5 +1,5 @@
 ---
-title: "Second-level folders don't consider the "search context'"
+title: "Second-level folders don't consider the 'search context'"
 id: 6WvlorgpBEeIuKk2mprMXm
 status: PUBLISHED
 createdAt: 2019-02-17T19:55:07.529Z
diff --git a/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
index ade184f72..fcfd0e51b 100644
--- a/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
+++ b/docs/known-issues/en/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -1,5 +1,5 @@
 ---
-title: "Settings UI doesn't update "expiration period' of quotes"
+title: "Settings UI doesn't update 'expiration period' of quotes"
 id: 4CmuAYwDn7tcCiR9DQHSFb
 status: PUBLISHED
 createdAt: 2023-08-07T19:42:22.810Z
diff --git a/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
index fddfa60ee..a7e8b2f8e 100644
--- a/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
+++ b/docs/known-issues/en/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -1,5 +1,5 @@
 ---
-title: "Telesales search doesn't accept special characters aside from "@'."
+title: "Telesales search doesn't accept special characters aside from '@'."
 id: 5eTb6KlR07dOP06BGhovoL
 status: PUBLISHED
 createdAt: 2024-07-29T17:21:34.828Z
diff --git a/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
index bd0d16c52..18184a5ce 100644
--- a/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
+++ b/docs/known-issues/en/xmls-product-name-flag-not-working-properly.md
@@ -1,5 +1,5 @@
 ---
-title: "XML's "Product Name' flag not working properly"
+title: "XML's 'Product Name' flag not working properly"
 id: 6YDbpRns3LCN02bVKM8aaf
 status: PUBLISHED
 createdAt: 2023-10-26T11:35:14.500Z
diff --git a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index 9f85ee192..f29241616 100644
--- a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -1,5 +1,5 @@
 ---
-title: "Al exportar imágenes SKU para cuentas que empiezan por 'h','t' o 'p' se corta este carácter en las filas "URL de la imagen'."
+title: "Al exportar imágenes SKU para cuentas que empiezan por 'h','t' o 'p' se corta este carácter en las filas 'URL de la imagen'."
 id: 1IZdnE8IGwkBlbcFhjLrzn
 status: PUBLISHED
 createdAt: 2023-10-13T15:20:49.703Z
@@ -18,8 +18,8 @@ internalReference: 919199
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
 
diff --git a/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
index 109ac1b3c..a8d558211 100644
--- a/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -1,5 +1,5 @@
 ---
-title: "Portal no respeta la etiqueta "Principal' de SKU's Imagen"
+title: "Portal no respeta la etiqueta 'Principal' de SKU's Imagen"
 id: 2ej5V3eIGgkUoo0Omgacc6
 status: CHANGED
 createdAt: 2017-04-17T18:35:42.842Z
@@ -18,8 +18,8 @@ internalReference: 712443
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
+<div class="alert alert-info">
+  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
 </div>
 
 

From 325a4315a4dfc6bbc7732495a5a0835d6051f5e8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Wed, 21 Aug 2024 09:18:55 -0300
Subject: [PATCH 10/13] massively fix callouts

running fix-callouts.js manually
---
 ...ers-new-variables-in-order-calculations.md |   4 +-
 ...res-front-end-requisites-to-master-data.md |   2 +-
 ...ion-will-now-be-restricted-by-user-role.md |   4 +-
 ...ntil-april-20th-to-activate-the-new-cdn.md |  12 +-
 ...ply-manual-prices-in-subscription-items.md |   4 +-
 ...ome-an-expert-in-vtex-with-training-day.md |   4 +-
 ...-payment-system-for-more-than-one-trade.md |   4 +-
 .../en/boost-your-marketplace-sales.md        |   4 +-
 ...lment-operation-with-vtex-pick-and-pack.md |   4 +-
 ...more-precision-to-google-analytics-data.md |   4 +-
 ...the-types-of-conversation-tracker-masks.md |   4 +-
 .../changes-in-vtex-support-service-policy.md |   2 +-
 .../en/check-your-stores-caa-record.md        |   8 +-
 .../en/checkout-api-improvements-part-1.md    |   4 +-
 ...close-bigger-deals-with-the-shared-cart.md |   4 +-
 ...ll-access-rules-to-allow-the-new-domain.md |   4 +-
 docs/announcements/en/delivery-capacity.md    |   4 +-
 ...d-order-create-error-and-order-creation.md |   4 +-
 .../en/discontinuation-of-vtex-payment.md     |   4 +-
 ...seller-confirmation-and-order-completed.md |   4 +-
 ...trol-on-your-order-authorization-screen.md |   4 +-
 .../erp-integration-guides-have-a-new-home.md |   2 +-
 ...-longer-be-available-for-the-vtex-admin.md |   4 +-
 ...t-your-conversion-with-the-new-checkout.md |   4 +-
 ...custom-storefront-components-in-vtex-io.md |  12 +-
 ...you-can-create-promotional-price-tables.md |  14 +-
 ...-you-can-export-up-to-3-thousand-orders.md |   4 +-
 .../en/google-catalog-migration.md            |   4 +-
 .../headless-cms-events-available-in-audit.md |   4 +-
 ...-seller-white-label-selection-algorithm.md |   4 +-
 ...the-catalog-through-web-service-will-be.md |   4 +-
 ...vtex-apis-now-need-token-authentication.md |   2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |   4 +-
 .../en/introducing-vtex-ad-network-beta.md    |   4 +-
 ...ce-to-buy-tickets-for-vtex-training-day.md |   4 +-
 ...-configuring-shipping-time-at-sku-level.md |   4 +-
 ...connectors-will-be-discontinued-in-2024.md |   8 +-
 ...-for-credit-and-debit-cards-at-checkout.md |   4 +-
 ...ice-per-item-promotion-will-be-disabled.md |   4 +-
 .../en/multi-currency-gift-card.md            |   4 +-
 ...my-authentication-section-in-my-account.md |   8 +-
 ...ers-is-now-available-on-extension-store.md |  12 +-
 ...dline-activate-the-new-cdn-until-may-31.md |   4 +-
 ...book-business-extension-integration-app.md |   4 +-
 .../en/new-limits-for-causes-of-benefit.md    |   7 +-
 ...uthorization-flow-for-native-connectors.md |   4 +-
 .../en/new-ready-to-dispatch-functionality.md |   4 +-
 .../new-rules-for-activating-vtex-support.md  |   2 +-
 .../en/new-subscriptions-module.md            |   8 +-
 ...-vtex-shipping-network-performance-page.md |   4 +-
 ...urs-setup-is-now-available-for-carriers.md |   8 +-
 ...e-products-from-your-physical-stores-in.md |  20 +--
 ...f-the-vtex-id-script-will-be-deprecated.md |   8 +-
 ...-png-to-webp-conversion-is-now-lossless.md |   4 +-
 ...ing-guide-your-complete-journey-at-vtex.md |   4 +-
 ...t-module-feed-v1-and-v2-discontinuation.md |   4 +-
 .../en/practical-guides-for-b2b-commerce.md   |   2 +-
 ...vice-experience-with-the-new-my-account.md |   4 +-
 ...rderform-configuration-for-all-requests.md |   8 +-
 ...ontinued-migrate-your-data-until-august.md |   4 +-
 ...agination-will-change-in-the-search-api.md |  18 +-
 ...arch-resolve-hides-number-product-stock.md |   4 +-
 ...curity-improvements-to-checkout-cookies.md |   4 +-
 ...-files-can-now-operate-at-full-capacity.md |   8 +-
 ...and-media-new-authorization-requirement.md |   4 +-
 ...ersion-already-available-for-all-stores.md |   4 +-
 ...ill-be-removed-from-the-list-orders-api.md |  12 +-
 ...is-already-being-deployed-to-all-stores.md |   4 +-
 ...-allows-you-to-export-up-to-5000-orders.md |   4 +-
 ...-management-module-will-be-discontinued.md |   4 +-
 ...o-longer-has-permission-to-create-users.md |   4 +-
 ...i-helps-marketplaces-avoid-losing-sales.md |   8 +-
 ...os-para-manter-sua-operacao-funcionando.md |   4 +-
 ...a-migration-will-be-completed-on-may-23.md |  20 +--
 ...x-announces-its-integration-with-amazon.md |   4 +-
 .../en/vtex-login-now-features-recaptcha.md   |   5 +-
 ...login-now-needs-2-factor-authentication.md |   4 +-
 ...uiza-is-already-available-to-all-stores.md |   4 +-
 .../web-service-methods-will-be-deprecated.md |   4 +-
 ...-powerful-marketing-tool-for-your-store.md |   4 +-
 ...ss-to-the-settings-screen-on-the-orders.md |   4 +-
 ...ers-new-variables-in-order-calculations.md |   4 +-
 ...res-front-end-requisites-to-master-data.md |   2 +-
 ...ion-will-now-be-restricted-by-user-role.md |   4 +-
 ...ntil-april-20th-to-activate-the-new-cdn.md |  12 +-
 ...ply-manual-prices-in-subscription-items.md |   4 +-
 ...ome-an-expert-in-vtex-with-training-day.md |   4 +-
 ...-payment-system-for-more-than-one-trade.md |   4 +-
 .../es/boost-your-marketplace-sales.md        |   4 +-
 ...lment-operation-with-vtex-pick-and-pack.md |   4 +-
 ...more-precision-to-google-analytics-data.md |   4 +-
 .../changes-in-vtex-support-service-policy.md |   2 +-
 .../es/check-your-stores-caa-record.md        |   8 +-
 .../es/checkout-api-improvements-part-1.md    |   4 +-
 .../checkout-api-now-supports-recaptcha-v3.md |   4 +-
 ...close-bigger-deals-with-the-shared-cart.md |   4 +-
 ...ll-access-rules-to-allow-the-new-domain.md |   4 +-
 docs/announcements/es/delivery-capacity.md    |   4 +-
 ...d-order-create-error-and-order-creation.md |   4 +-
 .../es/discontinuation-of-vtex-payment.md     |   4 +-
 ...seller-confirmation-and-order-completed.md |   4 +-
 ...trol-on-your-order-authorization-screen.md |   4 +-
 .../erp-integration-guides-have-a-new-home.md |   2 +-
 ...-longer-be-available-for-the-vtex-admin.md |   4 +-
 ...t-your-conversion-with-the-new-checkout.md |   4 +-
 ...custom-storefront-components-in-vtex-io.md |  12 +-
 ...you-can-create-promotional-price-tables.md |  14 +-
 ...-you-can-export-up-to-3-thousand-orders.md |   4 +-
 .../es/google-catalog-migration.md            |   4 +-
 .../headless-cms-events-available-in-audit.md |   4 +-
 ...-seller-white-label-selection-algorithm.md |   4 +-
 ...vtex-apis-now-need-token-authentication.md |   2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |   4 +-
 .../es/introducing-vtex-ad-network-beta.md    |   4 +-
 ...ce-to-buy-tickets-for-vtex-training-day.md |   6 +-
 ...-configuring-shipping-time-at-sku-level.md |   4 +-
 ...connectors-will-be-discontinued-in-2024.md |   8 +-
 ...-for-credit-and-debit-cards-at-checkout.md |   4 +-
 ...ice-per-item-promotion-will-be-disabled.md |   4 +-
 .../es/multi-currency-gift-card.md            |   4 +-
 ...my-authentication-section-in-my-account.md |   8 +-
 ...ers-is-now-available-on-extension-store.md |  12 +-
 ...dline-activate-the-new-cdn-until-may-31.md |   4 +-
 ...book-business-extension-integration-app.md |   4 +-
 .../es/new-limits-for-causes-of-benefit.md    |   7 +-
 ...API-increases-configuration-flexibility.md |   2 +-
 ...uthorization-flow-for-native-connectors.md |   4 +-
 .../es/new-ready-to-dispatch-functionality.md |   4 +-
 .../new-rules-for-activating-vtex-support.md  |   2 +-
 .../es/new-subscriptions-module.md            |   8 +-
 ...-vtex-shipping-network-performance-page.md |   5 +-
 ...urs-setup-is-now-available-for-carriers.md |   8 +-
 ...e-products-from-your-physical-stores-in.md |  18 +-
 ...f-the-vtex-id-script-will-be-deprecated.md |   8 +-
 ...-png-to-webp-conversion-is-now-lossless.md |   4 +-
 ...ing-guide-your-complete-journey-at-vtex.md |   4 +-
 ...t-module-feed-v1-and-v2-discontinuation.md |   4 +-
 ...vice-experience-with-the-new-my-account.md |   4 +-
 ...rderform-configuration-for-all-requests.md |   8 +-
 ...agination-will-change-in-the-search-api.md |  14 +-
 ...arch-resolve-hides-number-product-stock.md |   4 +-
 ...curity-improvements-to-checkout-cookies.md |   4 +-
 ...-files-can-now-operate-at-full-capacity.md |   8 +-
 ...and-media-new-authorization-requirement.md |   4 +-
 ...ersion-already-available-for-all-stores.md |   4 +-
 ...ill-be-removed-from-the-list-orders-api.md |  12 +-
 ...is-already-being-deployed-to-all-stores.md |   8 +-
 ...-allows-you-to-export-up-to-5000-orders.md |   4 +-
 ...-management-module-will-be-discontinued.md |   4 +-
 ...o-longer-has-permission-to-create-users.md |   4 +-
 ...laced-by-the-term-role-in-your-admin-ui.md |   4 +-
 ...i-helps-marketplaces-avoid-losing-sales.md |   8 +-
 ...os-para-manter-sua-operacao-funcionando.md |   4 +-
 ...a-migration-will-be-completed-on-may-23.md |  18 +-
 ...x-announces-its-integration-with-amazon.md |   4 +-
 .../es/vtex-login-now-features-recaptcha.md   |   4 +-
 ...uiza-is-already-available-to-all-stores.md |   4 +-
 .../web-service-methods-will-be-deprecated.md |   4 +-
 ...-powerful-marketing-tool-for-your-store.md |   4 +-
 ...ss-to-the-settings-screen-on-the-orders.md |   4 +-
 ...ers-new-variables-in-order-calculations.md |   4 +-
 ...res-front-end-requisites-to-master-data.md |   3 +-
 ...ion-will-now-be-restricted-by-user-role.md |   4 +-
 ...ntil-april-20th-to-activate-the-new-cdn.md |  12 +-
 ...ply-manual-prices-in-subscription-items.md |   4 +-
 ...ome-an-expert-in-vtex-with-training-day.md |   4 +-
 ...-payment-system-for-more-than-one-trade.md |   4 +-
 .../pt/boost-your-marketplace-sales.md        |   4 +-
 ...lment-operation-with-vtex-pick-and-pack.md |   4 +-
 ...more-precision-to-google-analytics-data.md |   4 +-
 .../changes-in-vtex-support-service-policy.md |   4 +-
 .../pt/check-your-stores-caa-record.md        |   8 +-
 .../pt/checkout-api-improvements-part-1.md    |   4 +-
 .../checkout-api-now-supports-recaptcha-v3.md |   4 +-
 ...close-bigger-deals-with-the-shared-cart.md |   4 +-
 ...ll-access-rules-to-allow-the-new-domain.md |   4 +-
 docs/announcements/pt/delivery-capacity.md    |   4 +-
 ...d-order-create-error-and-order-creation.md |   4 +-
 ...seller-confirmation-and-order-completed.md |   4 +-
 ...trol-on-your-order-authorization-screen.md |   4 +-
 .../erp-integration-guides-have-a-new-home.md |   2 +-
 ...-longer-be-available-for-the-vtex-admin.md |   4 +-
 ...t-your-conversion-with-the-new-checkout.md |   4 +-
 ...custom-storefront-components-in-vtex-io.md |  12 +-
 ...you-can-create-promotional-price-tables.md |  14 +-
 ...-you-can-export-up-to-3-thousand-orders.md |   4 +-
 .../pt/google-catalog-migration.md            |   4 +-
 .../headless-cms-events-available-in-audit.md |   4 +-
 ...-seller-white-label-selection-algorithm.md |   4 +-
 ...the-catalog-through-web-service-will-be.md |   4 +-
 ...vtex-apis-now-need-token-authentication.md |   2 +-
 ...ng-the-new-shipping-strategy-interfaces.md |   4 +-
 .../pt/introducing-vtex-ad-network-beta.md    |   4 +-
 ...ce-to-buy-tickets-for-vtex-training-day.md |   6 +-
 ...-configuring-shipping-time-at-sku-level.md |   4 +-
 ...connectors-will-be-discontinued-in-2024.md |   8 +-
 ...-for-credit-and-debit-cards-at-checkout.md |   4 +-
 ...ice-per-item-promotion-will-be-disabled.md |   4 +-
 .../pt/multi-currency-gift-card.md            |   4 +-
 ...my-authentication-section-in-my-account.md |   8 +-
 ...ers-is-now-available-on-extension-store.md |  12 +-
 .../new-cdn-gives-more-security-and-speed.md  |   8 +-
 ...dline-activate-the-new-cdn-until-may-31.md |   4 +-
 ...book-business-extension-integration-app.md |   4 +-
 .../pt/new-limits-for-causes-of-benefit.md    |   7 +-
 ...uthorization-flow-for-native-connectors.md |   4 +-
 .../new-rules-for-activating-vtex-support.md  |   2 +-
 .../pt/new-subscriptions-module.md            |   8 +-
 ...-vtex-shipping-network-performance-page.md |   5 +-
 ...urs-setup-is-now-available-for-carriers.md |   8 +-
 ...e-products-from-your-physical-stores-in.md |  18 +-
 ...f-the-vtex-id-script-will-be-deprecated.md |   8 +-
 ...-png-to-webp-conversion-is-now-lossless.md |   4 +-
 ...ing-guide-your-complete-journey-at-vtex.md |   4 +-
 ...t-module-feed-v1-and-v2-discontinuation.md |   4 +-
 .../pt/practical-guides-for-b2b-commerce.md   |   2 +-
 ...vice-experience-with-the-new-my-account.md |   4 +-
 ...rderform-configuration-for-all-requests.md |   8 +-
 ...ontinued-migrate-your-data-until-august.md |   4 +-
 ...agination-will-change-in-the-search-api.md |  18 +-
 ...arch-resolve-hides-number-product-stock.md |   4 +-
 ...curity-improvements-to-checkout-cookies.md |   4 +-
 ...-files-can-now-operate-at-full-capacity.md |   8 +-
 ...and-media-new-authorization-requirement.md |   4 +-
 ...ersion-already-available-for-all-stores.md |   4 +-
 ...ill-be-removed-from-the-list-orders-api.md |  12 +-
 ...is-already-being-deployed-to-all-stores.md |   4 +-
 ...-allows-you-to-export-up-to-5000-orders.md |   4 +-
 ...eckout-will-now-be-unchecked-by-default.md |   8 +-
 ...-management-module-will-be-discontinued.md |   4 +-
 ...o-longer-has-permission-to-create-users.md |   4 +-
 ...laced-by-the-term-role-in-your-admin-ui.md |   4 +-
 ...i-helps-marketplaces-avoid-losing-sales.md |   8 +-
 ...os-para-manter-sua-operacao-funcionando.md |   4 +-
 ...a-migration-will-be-completed-on-may-23.md |  20 +--
 ...x-announces-its-integration-with-amazon.md |   4 +-
 .../pt/vtex-login-now-features-recaptcha.md   |   5 +-
 ...login-now-needs-2-factor-authentication.md |   4 +-
 ...uiza-is-already-available-to-all-stores.md |   4 +-
 .../web-service-methods-will-be-deprecated.md |   4 +-
 ...elcome-to-the-redesigned-vtex-admin-new.md |   4 +-
 ...-powerful-marketing-tool-for-your-store.md |   4 +-
 ...ss-to-the-settings-screen-on-the-orders.md |   4 +-
 ...ations-to-troubleshoot-front-end-issues.md |   4 +-
 ...h-the-best-selling-products-in-my-store.md |   4 +-
 .../en/can-i-order-my-products-as-i-want.md   |   4 +-
 ...iliations-that-support-native-split-faq.md |   8 +-
 ...la-ao-tentar-importar-planilha-de-frete.md |   4 +-
 ...re-ao-tentar-importar-planilha-de-frete.md |   4 +-
 ...t-to-an-instance-of-an-object-ao-tentar.md |   4 +-
 .../faq/en/fix-redirect-error-in-pagseguro.md |   2 +-
 ...w-to-add-more-agents-in-a-whatsapp-link.md |   4 +-
 .../en/how-to-configure-a-new-trade-policy.md |   4 +-
 ...e-in-the-integration-with-mercado-livre.md |   2 +-
 docs/faq/en/how-to-edit-a-whatsapp-link.md    |   4 +-
 docs/faq/en/how-to-find-facebook-pixel.md     |   4 +-
 .../en/how-to-find-google-analytics-pixel.md  |   4 +-
 .../how-to-find-google-tag-manager-pixel.md   |   4 +-
 docs/faq/en/how-to-find-linkedin-pixel.md     |   4 +-
 ...improvements-in-the-checkout-api-part-1.md |   8 +-
 ...le-to-change-data-in-a-master-workspace.md |   4 +-
 docs/faq/en/locate-the-google-ads-pixel.md    |   4 +-
 docs/faq/en/my-trial-is-over-now-what.md      |   4 +-
 ...cked-in-ready-for-handling-what-do-i-do.md |   4 +-
 ...-in-ready-for-handling-what-should-i-do.md |   4 +-
 ...understanding-vtex-email-capture-system.md |   8 +-
 docs/faq/en/utms.md                           |   4 +-
 ...ders-do-not-appear-in-my-orders-section.md |   4 +-
 docs/faq/en/vtex-support-emea.md              |   6 +-
 docs/faq/en/vtex-support-united-states.md     |   2 +-
 docs/faq/en/what-is-the-whatsapp-link.md      |   4 +-
 docs/faq/en/where-to-use-whatsapp-link.md     |   4 +-
 .../why-cant-i-see-my-carrier-on-checkout.md  |   8 +-
 ...ntication-with-appkey-and-apptoken-work.md |   8 +-
 ...en-wrongly-categorized-on-mercado-livre.md |   3 +-
 ...do-not-receive-my-abandoned-cart-emails.md |   4 +-
 docs/faq/en/why-is-my-stock-negative.md       |   4 +-
 ...-the-product-not-visible-on-the-website.md |  29 ++--
 ...-status-was-shown-as-preparando-entrega.md |   4 +-
 ...heckout-when-the-purchase-was-concluded.md |   4 +-
 ...ations-to-troubleshoot-front-end-issues.md |   4 +-
 .../es/can-i-order-my-products-as-i-want.md   |   4 +-
 ...iliations-that-support-native-split-faq.md |  12 +-
 ...gencia-entre-o-valor-total-do-pedido-da.md |   4 +-
 ...la-ao-tentar-importar-planilha-de-frete.md |   4 +-
 ...re-ao-tentar-importar-planilha-de-frete.md |   5 +-
 ...t-to-an-instance-of-an-object-ao-tentar.md |   6 +-
 .../faq/es/fix-redirect-error-in-pagseguro.md |   2 +-
 ...w-to-add-more-agents-in-a-whatsapp-link.md |   4 +-
 .../es/how-to-configure-a-new-trade-policy.md |   4 +-
 docs/faq/es/how-to-edit-a-whatsapp-link.md    |   4 +-
 docs/faq/es/how-to-find-facebook-pixel.md     |   4 +-
 .../es/how-to-find-google-analytics-pixel.md  |   4 +-
 .../how-to-find-google-tag-manager-pixel.md   |   4 +-
 docs/faq/es/how-to-find-linkedin-pixel.md     |   4 +-
 ...improvements-in-the-checkout-api-part-1.md |   8 +-
 docs/faq/es/locate-the-google-ads-pixel.md    |   4 +-
 docs/faq/es/my-trial-is-over-now-what.md      |   4 +-
 ...cked-in-ready-for-handling-what-do-i-do.md |   4 +-
 ...-in-ready-for-handling-what-should-i-do.md |   4 +-
 ...understanding-vtex-email-capture-system.md |   8 +-
 .../untitled-entry-2017-09-19-at-09-42-49.md  |   2 +-
 docs/faq/es/utms.md                           |   4 +-
 ...ders-do-not-appear-in-my-orders-section.md |   4 +-
 docs/faq/es/what-is-the-whatsapp-link.md      |   4 +-
 docs/faq/es/where-to-use-whatsapp-link.md     |   4 +-
 .../why-cant-i-see-my-carrier-on-checkout.md  |   8 +-
 ...ntication-with-appkey-and-apptoken-work.md |   8 +-
 ...en-wrongly-categorized-on-mercado-livre.md |   4 +-
 ...do-not-receive-my-abandoned-cart-emails.md |   4 +-
 docs/faq/es/why-is-my-stock-negative.md       |   4 +-
 ...-the-product-not-visible-on-the-website.md |  29 ++--
 ...-status-was-shown-as-preparando-entrega.md |   4 +-
 ...heckout-when-the-purchase-was-concluded.md |   4 +-
 ...ations-to-troubleshoot-front-end-issues.md |   4 +-
 ...h-the-best-selling-products-in-my-store.md |   4 +-
 .../pt/can-i-order-my-products-as-i-want.md   |   4 +-
 ...iliations-that-support-native-split-faq.md |  12 +-
 ...gencia-entre-o-valor-total-do-pedido-da.md |   4 +-
 ...la-ao-tentar-importar-planilha-de-frete.md |   4 +-
 ...re-ao-tentar-importar-planilha-de-frete.md |   4 +-
 ...t-to-an-instance-of-an-object-ao-tentar.md |   4 +-
 .../faq/pt/fix-redirect-error-in-pagseguro.md |   2 +-
 docs/faq/pt/how-does-vtex-support-work.md     |   2 +-
 .../pt/how-to-configure-a-new-trade-policy.md |   4 +-
 .../how-to-find-google-tag-manager-pixel.md   |   4 +-
 ...le-to-change-data-in-a-master-workspace.md |   4 +-
 ...cked-in-ready-for-handling-what-do-i-do.md |   4 +-
 ...-in-ready-for-handling-what-should-i-do.md |   4 +-
 ...understanding-vtex-email-capture-system.md |   8 +-
 .../untitled-entry-2018-03-06-at-02-03-12.md  |  12 +-
 ...ders-do-not-appear-in-my-orders-section.md |   4 +-
 docs/faq/pt/vtex-support-brazil.md            |   4 +-
 .../why-cant-i-see-my-carrier-on-checkout.md  |   8 +-
 ...ntication-with-appkey-and-apptoken-work.md |   8 +-
 ...en-wrongly-categorized-on-mercado-livre.md |   4 +-
 ...do-not-receive-my-abandoned-cart-emails.md |   4 +-
 docs/faq/pt/why-is-my-stock-negative.md       |   4 +-
 ...-the-product-not-visible-on-the-website.md |  29 ++--
 ...-status-was-shown-as-preparando-entrega.md |   4 +-
 ...was-not-an-order-sent-to-the-anti-fraud.md |   4 +-
 ...heckout-when-the-purchase-was-concluded.md |   4 +-
 ...en-running-vtex-link-for-the-first-time.md |   4 +-
 ...-of-collections-doesnt-work-as-expected.md |   3 +-
 ...-message-centre-module-returns-an-error.md |   4 +-
 ...checkout-and-causing-stuck-transactions.md |   4 +-
 ...3-error-for-all-urls-containing-develop.md |   4 +-
 ...the-activate-if-possible-flag-unchecked.md |   4 +-
 ...when-having-it-as-a-single-payment-rule.md |   4 +-
 ...-be-returned-blank-in-the-catalog-admin.md |   4 +-
 ...information-for-sessions-and-conversion.md |   4 +-
 ...name-dont-have-metrics-on-search-report.md |   4 +-
 ...skuvincularvalorservicoaspx-not-working.md |   4 +-
 ...nvoice-address-returns-null-api-results.md |   4 +-
 ...cation-mode-even-for-complete-addresses.md |   4 +-
 ...he-shopper-opts-to-insert-a-new-address.md |   4 +-
 ...-size-for-multiples-cities-separated-by.md |   4 +-
 ...-removing-essential-address-information.md |   4 +-
 ...n-buyer-has-can-add-shipping-permission.md |   4 +-
 ...n-impersonated-using-vtex-telemarketing.md |   4 +-
 ...auses-invalid-address-for-an-item-error.md |   4 +-
 ...-assembly-options-components-attachment.md |   4 +-
 ...for-integration-with-wl-seller-facebook.md |   4 +-
 .../es/adjust-processing-tab-export.md        |   4 +-
 ...rder-has-more-than-one-product-centauro.md |   4 +-
 .../es/admin-collection-brand-list-timeout.md |   4 +-
 ...rch-doesnt-recognize-profile-menu-items.md |   4 +-
 ...nsion-as-jpg-even-when-the-image-is-png.md |   4 +-
 ...-engine-redirects-them-to-the-wrong-url.md |   4 +-
 .../es/admin-review-global-search.md          |   4 +-
 docs/known-issues/es/admin-timeout.md         |   4 +-
 ...ut-country-disrupting-orderform-changes.md |   4 +-
 ...egistered-globally-insted-of-by-binding.md |   4 +-
 ...-generates-payment-authorization-denial.md |   4 +-
 ...-some-operations-and-thus-causing-error.md |   4 +-
 ...ethodtype-for-amex-when-using-apple-pay.md |   4 +-
 ...ring-pspreference-to-cancel-transaction.md |   4 +-
 ...ed-delivery-selection-appears-only-once.md |   4 +-
 ...-return-values-without-relating-an-item.md |   4 +-
 ...-showing-in-vtexcmcproductimage-zoomon-.md |  12 +-
 .../es/amazon-category-implementation.md      |   4 +-
 ...e-sending-product-to-amazon-marketplace.md |   4 +-
 ...sku-is-not-being-logged-into-the-bridge.md |   4 +-
 .../es/amazon-global-category-not-working.md  |   4 +-
 ...n-integration-attribute-number-of-itens.md |   4 +-
 ...ration-is-not-cancelling-orders-in-vtex.md |   4 +-
 ...integration-stock-reservations-for-kits.md |   4 +-
 ...nce-not-set-to-an-instance-of-an-object.md |   4 +-
 .../es/amazon-order-integration-error.md      |   4 +-
 .../amazoncasacaso-erros-de-rastreamento.md   |   4 +-
 ...curred-when-adding-tracking-information.md |   4 +-
 .../es/analytics-duplicated-events.md         |   4 +-
 ...ing-data-in-sales-performance-dashboard.md |   4 +-
 ...expected-behavior-with-the-enter-button.md |   4 +-
 ...mate-returns-wrong-info-when-sc-is-null.md |   4 +-
 ...ts-does-not-return-additionalinfo-field.md |   4 +-
 ...o-bought-not-always-working-as-expected.md |   4 +-
 ...-are-not-erased-when-you-delete-the-app.md |   4 +-
 ...most-expensive-items-ui-not-saving-data.md |   4 +-
 ...oved-skus-spreadsheet-not-showing-price.md |   4 +-
 ...when-selected-on-pdp-and-adding-to-cart.md |   4 +-
 ...t-allow-null-domainvalues-and-it-should.md |   4 +-
 ...ation-on-field-domainvalues-not-working.md |   4 +-
 ...g-an-item-from-a-seller-with-attachment.md |   4 +-
 ...are-not-updated-when-its-added-to-items.md |   4 +-
 ...e-not-being-updated-in-meli-integration.md |   4 +-
 ...pricing-logs-showing-unknow-information.md |   4 +-
 ...payments-when-the-first-one-is-canceled.md |   4 +-
 .../es/auto-approve-api-accepts-any-values.md |   4 +-
 ...ng-suggestion-products-shown-with-delay.md |   4 +-
 ...arch-suggestion-is-not-working-properly.md |  12 +-
 ...tocomplete-not-answering-to-cold-starts.md |   4 +-
 ...ys-updating-when-changed-multiple-times.md |   4 +-
 ...ocomplete-search-not-working-with-space.md |   4 +-
 ...i-removes-the-dot-from-the-product-name.md |   4 +-
 ...ic-payment-settlement-incorrectly-setup.md |   4 +-
 ...not-occurring-due-to-special-characters.md |   4 +-
 ...mulation-for-no-stock-or-price-products.md |   4 +-
 ...-missing-data-for-newly-created-address.md |   4 +-
 ...r-of-routes-created-to-deliver-the-item.md |   4 +-
 ...d-data-is-not-removed-after-logging-out.md |   4 +-
 ...story-doesnt-work-in-the-website-domain.md |   4 +-
 ...ng-geolocation-when-registering-address.md |   4 +-
 ...-detail-ui-only-shows-100-first-sellers.md |   4 +-
 ...e-doesnt-register-information-in-orders.md |   4 +-
 ...count-at-checkout-in-the-website-domain.md |   4 +-
 ...e-geocoordinates-to-calculate-region-id.md |   4 +-
 ...rect-order-fob-integrating-with-carrier.md |   4 +-
 .../es/b2w-freight-value-in-oms-vtex.md       |   4 +-
 ...der-with-parameter-count-mismatch-error.md |   4 +-
 ...w-tracking-status-not-updated-on-skyhub.md |   4 +-
 ...tton-is-not-rendered-in-my-organization.md |   4 +-
 ...lbacksuccess-instead-of-placeorder-page.md |   4 +-
 ...n-searching-terms-with-directly-via-url.md |   4 +-
 ...arching-terms-with-through-autocomplete.md |   4 +-
 ...-with-a-huge-quantity-of-reserved-items.md |   4 +-
 ...ific-scenarios-with-merchandising-rules.md |   4 +-
 ...ity-of-the-search-level-in-search-pages.md |   4 +-
 ...duling-is-deactivated-after-expiry-date.md |  12 +-
 ...en-the-promotion-is-a-buy-together-type.md |   4 +-
 ...does-not-match-an-associated-card-brand.md |   4 +-
 ...or-not-working-at-site-editor-home-page.md |   4 +-
 .../es/bmail-problems-with-filaumbro.md       |   4 +-
 ...form-application-does-not-work-properly.md |   4 +-
 ...rties-not-being-validated-on-legacy-cms.md |   4 +-
 ...port-selecting-fewer-skus-than-expected.md |   4 +-
 ...s-are-not-searchable-on-the-brand-admin.md |   4 +-
 ...nceling-due-to-an-error-with-code-bp901.md |   4 +-
 ...-being-read-by-crawlers-due-ssr-timeout.md |   4 +-
 ...hanges-to-the-intelligent-search-module.md |   4 +-
 ...cep-not-working-in-create-giftlist-form.md |   4 +-
 ...-mycards-page-not-translated-to-spanish.md |   4 +-
 ...-points-not-being-presented-in-the-list.md |   4 +-
 ...k-on-the-first-try-in-fullcleanup-admin.md |   4 +-
 ...oducts-not-to-load-on-the-front-timeout.md |   4 +-
 ...e-restriction-impact-in-gift-promotions.md |   4 +-
 ...figuration-in-organizationscost-centers.md |   4 +-
 docs/known-issues/es/cabals-regex-update.md   |   4 +-
 ...reating-or-deleting-merchandising-rules.md |   4 +-
 ...rice-table-export-not-bringing-all-skus.md |   4 +-
 .../calculation-issue-in-comissionamount.md   |   4 +-
 ...lendar-in-english-for-stores-in-spanish.md |   4 +-
 ...s-to-cart-from-store-framework-frontend.md |   4 +-
 ...to-retry-payment-which-may-also-deny-it.md |   4 +-
 ...nnector-owner-account-has-been-disabled.md |   4 +-
 ...-a-customers-credit-card-via-my-account.md |  12 +-
 ...audience-doesnt-save-coupon-information.md |   4 +-
 ...rent-from-to-equal-to-with-a-collection.md |   4 +-
 ...ormaspx-save-button-requires-two-clicks.md |   4 +-
 ...re-not-applied-after-3rd-category-level.md |   4 +-
 ...-a-seller-under-the-multilevel-behavior.md |   4 +-
 ...nt-edit-the-name-of-the-styles-template.md |   4 +-
 ...rd-brands-incorrectly-processed-as-visa.md |   4 +-
 ...card-facebook-doesnt-save-some-settings.md |   4 +-
 ...holderdocument-is-not-sent-to-antifraud.md |   4 +-
 ...order-doesnt-bring-the-assembly-options.md |   4 +-
 ...-old-order-doesnt-bring-the-attachments.md |   4 +-
 ...ing-placed-as-expected-in-the-orderform.md |   4 +-
 ...sing-sent-by-checkout-in-additionaldata.md |   4 +-
 ...re-kept-in-orders-with-total-value-zero.md |   4 +-
 ...t-message-while-screen-is-still-loading.md |   4 +-
 ...if-store-cant-ship-to-all-the-countries.md |   4 +-
 ...ent-do-not-receive-promotions-correctly.md |   4 +-
 ...-not-consider-items-removed-from-orders.md |   4 +-
 ...le-gives-access-to-the-gift-card-module.md |   4 +-
 ...i-create-sku-file-only-work-with-an-url.md |   4 +-
 ...properly-to-space-at-the-end-of-strings.md |   4 +-
 ...on-if-sending-request-with-wrong-values.md |   4 +-
 ...ters-skus-with-duplicate-specifications.md |   4 +-
 ...export-cannot-handle-t-and-s-characters.md |   4 +-
 ...how-sales-channels-when-none-are-tagged.md |   4 +-
 ...xport-for-attachment-cuts-50-characters.md |   4 +-
 ...ilter-for-seller-1-brings-empty-results.md |   4 +-
 .../es/catalog-filters-timeout.md             |   4 +-
 ...ger-a-new-intelligent-search-indexation.md |   4 +-
 ...ql-categoryinputtranslation-not-working.md |   4 +-
 ...enerating-invalid-translation-documents.md |   4 +-
 ...-report-total-section-calculation-error.md |   4 +-
 ...ion-xml-fiscal-code-field-not-rendering.md |   4 +-
 ...mapping-ui-taking-too-much-time-to-load.md |   4 +-
 ...ame-html-select-breaking-for-chrome-108.md |   4 +-
 ...alog-search-api-limited-to-2500-results.md |   4 +-
 ...rn-information-for-products-unavailable.md |   4 +-
 ...f-the-selected-category-is-a-department.md |   4 +-
 ...slations-not-reflecting-on-the-frontend.md |   4 +-
 .../es/catalogv2-user-roles-not-applying.md   |   4 +-
 ...update-with-values-from-review-skus-tab.md |   4 +-
 .../categoriesaspx-specification-timeout.md   |   4 +-
 ...on-the-seller-config-generates-time-out.md |   4 +-
 ...r-when-translating-with-catalog-graphql.md |   4 +-
 ...s-do-not-open-in-admin-on-first-attempt.md |   4 +-
 ...gory-substitute-words-not-being-indexed.md |   4 +-
 ...ds-being-overwritten-on-catalog-graphql.md |   4 +-
 ...entage-on-seller-api-allowing-any-value.md |   4 +-
 ...-with-pedido-sem-o-campo-packages-error.md |   4 +-
 ...-to-myaccount-instead-of-the-order-page.md |   4 +-
 ...-calculation-of-promotions-take-3-pay-2.md |   4 +-
 ...er-using-api-without-email-orderchanged.md |   4 +-
 ...umber-of-characters-in-the-braspag-slip.md |   4 +-
 ...-are-saved-but-dont-reflect-on-the-page.md |   4 +-
 ...tyles-admin-page-are-not-saved-properly.md |   4 +-
 ...ccessories-is-not-triggering-indexation.md |   4 +-
 ...-could-make-the-page-not-work-correctly.md |   4 +-
 ...hentication-doesnt-work-on-pages-module.md |   4 +-
 ...without-shipping-address-on-the-ui-only.md |   4 +-
 ...-add-2-different-addresses-for-delivery.md |   4 +-
 ...pty-shippingdata-when-using-geolocation.md |   4 +-
 ...es-when-two-or-more-sellers-can-fulfill.md |   4 +-
 ...-unavailable-after-pickuppoint-selected.md |   4 +-
 ...as-free-shipping-and-scheduled-delivery.md |   4 +-
 ...at-first-instant-for-specific-condition.md |   4 +-
 ...does-not-show-option-to-change-zip-code.md |   4 +-
 ...support-encoding-assembly-options-names.md |   4 +-
 ...-pageview-events-multiplied-per-tracker.md |   4 +-
 ...pickup-point-option-was-defined-via-api.md |   4 +-
 ...e-identified-and-the-logged-in-customer.md |   4 +-
 ...tly-sending-item-details-to-transaction.md |   4 +-
 ...hanging-email-but-flow-is-not-supported.md |   4 +-
 ...ut-orderplaced-boleto-bank-invoice-moip.md |   4 +-
 ...writes-receiver-name-with-customer-name.md |   4 +-
 ...ncorrect-information-in-the-paymentdata.md |  12 +-
 ...f-apple-pay-is-the-first-payment-method.md |  12 +-
 ...ct-seller-when-merging-cart-information.md |   4 +-
 ...tax-field-for-shipping-percentage-taxes.md |   4 +-
 ...e-same-sku-receives-a-logistics-timeout.md |   4 +-
 ...ress-for-shoppers-with-complete-profile.md |   4 +-
 ...r-items-with-no-common-shipping-methods.md |   4 +-
 ...orrect-sla-values-from-logistics-system.md |  12 +-
 ...hen-name-is-different-from-profile-data.md |   4 +-
 ...-hyphen-in-the-postal-code-to-orderform.md |   4 +-
 ...-the-user-switches-the-delivery-options.md |   4 +-
 ...le-all-toggle-after-refreshing-the-page.md |   4 +-
 ...-there-is-only-pickup-address-available.md |   4 +-
 ...oesnt-handle-multiple-filters-correctly.md |   4 +-
 ...licks-on-the-numericstepper-not-working.md |   4 +-
 ...ly-sometimes-in-global-checkout-setting.md |   4 +-
 ...t-add-client-profile-is-performed-twice.md |   4 +-
 ...with-the-same-names-as-the-default-ones.md |   4 +-
 .../es/cms-legacy-collections-timeout.md      |   4 +-
 .../cms-loyalty-value-settings-not-working.md |   4 +-
 ...oving-value-from-the-unit-of-mass-field.md |   4 +-
 ...s-settings-role-not-working-as-expected.md |   4 +-
 ...r-doesnt-work-in-development-workspaces.md |   4 +-
 ...saved-card-with-wrong-payment-system-id.md |   4 +-
 ...courier-retries-not-working-as-expected.md |   4 +-
 ...ble-menu-issues-rendering-all-the-items.md |   4 +-
 ...n-functionality-doesnt-work-on-giftcard.md |  12 +-
 ...ection-ordering-not-working-as-expected.md |   4 +-
 ...accessed-through-mapproductclusternames.md |   4 +-
 ...ot-allow-more-than-1000-skus-per-upload.md |   4 +-
 ...ustom-search-results-pages-in-b2b-suite.md |   4 +-
 .../collections-dont-open-on-subaccounts.md   |   4 +-
 ...-only-shows-1st-sku-of-inactive-product.md |   4 +-
 ...-equal-to-on-the-campaign-audience-form.md |   4 +-
 ...h-special-characters-cannot-be-exported.md |   4 +-
 ...ation-details-shows-only-20-collections.md |   4 +-
 ...llections-schedule-end-date-not-working.md |   4 +-
 ...ections-schedule-start-date-not-working.md |   4 +-
 ...ng-as-expected-on-progressive-discounts.md |   4 +-
 ...ch-for-products-with-special-characters.md |   4 +-
 ...texcrm-field-is-not-showing-its-content.md |   4 +-
 ...eation-due-to-failure-in-gatewaycallbak.md |   4 +-
 ...n-implemented-in-productsummary-for-ios.md |   4 +-
 ...nconsistency-in-deliveryshipping-prices.md |   4 +-
 ...components-in-a-kit-with-the-same-price.md |   4 +-
 ...o-pode-ser-alterada-por-contas-franquia.md |   4 +-
 .../confirmed-order-email-not-being-sent.md   |   4 +-
 ...the-same-name-at-the-intelligent-search.md |   4 +-
 ...nel-in-searches-portal-and-search-again.md |   4 +-
 ...violates-the-following-content-security.md |   4 +-
 .../es/cookie-broken-the-apisessions.md       |   4 +-
 ...-only-25-options-in-b2b-admin-customers.md |   4 +-
 ...g-logic-diverges-on-computed-prices-api.md |   4 +-
 .../country-field-as-null-in-invoicedata.md   |   4 +-
 ...ys-restricted-to-the-delivery-countries.md |   4 +-
 ...sage-not-restored-for-incomplete-orders.md |   4 +-
 ...oupons-created-as-archived-temporarrily.md |   4 +-
 ...oesnt-send-nulls-as-release-date-values.md |   4 +-
 ...ional-information-is-returning-an-error.md |   4 +-
 ...-does-not-update-the-items-stockbalance.md |   4 +-
 ...-of-redirects-breaks-the-redirects-page.md |   4 +-
 ...-of-the-csv-through-the-cli-doesnt-work.md |   4 +-
 ...not-returned-on-the-explained-search-ui.md |   4 +-
 ...-allow-values-longer-than-10-characters.md |   4 +-
 ...y-symbol-does-not-follow-admin-language.md |   4 +-
 .../custom-attribute-mapper-mercado-livre.md  |   4 +-
 ...cms-not-working-with-more-than-one-html.md |   4 +-
 ...mage-is-not-displayed-on-mobile-version.md |   4 +-
 ...edit-doesnt-show-installments-correctly.md |   4 +-
 ...tatus-at-mycredits-page-are-not-correct.md |   4 +-
 ...ue-updating-according-to-the-pagination.md |   4 +-
 ...credits-invoice-list-cannot-be-exported.md |   4 +-
 ...s-some-order-with-profileerroronloading.md |   4 +-
 ...rom-profile-system-without-clear-reason.md |   4 +-
 ...tion-is-not-saved-in-the-profile-system.md |   4 +-
 ...-products-catalog-page-after-logging-in.md |  12 +-
 ...ipping-promotion-default-saleschannel-1.md |   4 +-
 ...v-without-validation-of-characters-type.md |   4 +-
 ...-but-are-still-paymentpending-at-dafiti.md |   4 +-
 .../es/dafiti-quality-dafiti-images.md        |   4 +-
 ...n-search-report-showing-duplicated-date.md |   4 +-
 ...ed-payment-system-rendering-at-checkout.md |   4 +-
 ...eadlocked-error-when-using-catalog-apis.md |   4 +-
 ...-an-error-in-the-transactionstate-field.md |   4 +-
 ...dtotalamount-and-csittotalamount-fields.md |   4 +-
 ...sed-after-some-retries-to-authorization.md |   4 +-
 ...ng-when-creating-products-through-admin.md |   4 +-
 ...ping-policy-locked-in-processing-status.md |   4 +-
 ...register-cancelreason-in-the-order-json.md |   4 +-
 ...utomatic-capture-even-without-antifraud.md |   4 +-
 ...-checkout-if-not-deactivated-previously.md |   4 +-
 ...ew-admin-is-not-reindexing-the-products.md |   4 +-
 ...s-allowing-schedule-carrier-at-checkout.md |   4 +-
 ...e-is-space-in-the-id-of-shipping-policy.md |   4 +-
 ...-due-to-an-error-in-filling-the-invoice.md |   4 +-
 ...w-when-there-is-only-scheduled-delivery.md |   4 +-
 ...ector-does-not-appear-in-some-scenarios.md |   4 +-
 ...getting-empty-when-item-is-a-gift-added.md |   4 +-
 ...with-lean-shipping-offering-invalid-sla.md |   4 +-
 .../es/deliverycontracttype-problem-b2w.md    |   4 +-
 ...ing-on-seller-management-commissions-ui.md |   4 +-
 .../diacritics-are-removed-on-catalogapi.md   |   4 +-
 ...rices-between-pdp-plp-and-checkout-cart.md |   4 +-
 ...-specification-value-on-apis-and-portal.md |   4 +-
 ...f-sellers-for-the-same-seller-in-a-cart.md |   4 +-
 ...ds-being-unselected-during-sku-creation.md |   4 +-
 ...perly-when-prop-animated-is-set-as-true.md |   4 +-
 ...oupon-usage-count-on-oms-and-coupons-ui.md |   4 +-
 ...and-the-subtotal-of-items-or-totalizers.md |   4 +-
 .../es/divergence-delivery-time-netshoes.md   |   4 +-
 ...lculations-involving-decimals-in-weight.md |   4 +-
 ...-settings-on-new-accounts-or-workspaces.md |   4 +-
 .../known-issues/es/divergence-rule-dafiti.md |   4 +-
 .../es/divergencia-shipping-estimate-b2w.md   |   4 +-
 ...ues-per-item-between-chk-and-ffm-orders.md |   4 +-
 ...ile-using-price-override-and-promotions.md |   4 +-
 ...transaction-list-and-on-the-transaction.md |   4 +-
 ...llment-configuration-and-splitted-items.md |   4 +-
 ...domly-getting-last-digit-deleted-on-ios.md |   4 +-
 .../es/drag-and-drop-issue-on-site-editor.md  |   4 +-
 ...sspecification-values-on-the-same-level.md |   4 +-
 ...n-modal-to-switch-between-organizations.md |   4 +-
 ...-ignored-when-approved-on-received-skus.md |   4 +-
 ...th-automatic-capture-on-authorizedotnet.md |   4 +-
 ...derest-are-not-respecting-early-capture.md |   4 +-
 ...filling-for-new-buyers-after-logging-in.md |   4 +-
 ...autofilling-for-new-users-on-checkoutui.md |   4 +-
 ...ate-using-the-b2b-organizations-feature.md |   4 +-
 ...ters-leads-to-unexpected-product-search.md |   4 +-
 ...cancelation-when-the-status-code-is-359.md |   4 +-
 ...re-specific-global-category-persistente.md |   4 +-
 .../es/erro-sqlerrm-no-tracking-brinox-b2w.md |   4 +-
 ...e-rejected-or-reviewed-by-offer-quality.md |   4 +-
 ...ror-cancelling-customer-credit-invoices.md |   4 +-
 ...a-promotion-excluding-more-than-1-brand.md |   4 +-
 .../error-closing-customer-credit-account.md  |   4 +-
 ...xporting-entity-with-too-many-documents.md |   4 +-
 ...ror-exporting-large-amount-of-giftcards.md |   4 +-
 .../error-exporting-prices-with-metadata.md   |   4 +-
 ...-cannot-have-more-than-one-sla-selected.md |   4 +-
 .../es/error-in-checkout-error-message.md     |   4 +-
 .../es/error-in-custom-payments-creation.md   |   4 +-
 ...ients-is-different-than-operation-value.md |   4 +-
 ...lue-cannot-be-null-parameter-name-value.md |   4 +-
 ...-cancelation-when-the-returncode-is-359.md |   4 +-
 ...ntity-field-of-the-same-sku-in-the-cart.md |   4 +-
 ...ui-after-requesting-the-invoice-via-app.md |   4 +-
 ...rating-sku-field-may-not-be-null-magalu.md |   4 +-
 ...trying-to-access-catalog-pages-on-admin.md |   4 +-
 ...-sku-is-binded-on-vtexvtex-integrations.md |   4 +-
 ...-search-using-the-all-field-in-vtex-crm.md |   4 +-
 .../es/error-on-duplicate-payment-method.md   |   4 +-
 .../error-saving-netshoes-integration-card.md |   4 +-
 ...gain-when-adding-images-via-site-editor.md |   4 +-
 .../es/error-sww-on-product-pdp.md            |   4 +-
 ...al-connector-for-pending-payment-status.md |   4 +-
 ...-viewing-shippingestimatedate-in-new-ui.md |   4 +-
 ...ng-an-index-if-the-fields-are-identical.md |   4 +-
 ...delivery-type-when-seller-has-recursion.md |   4 +-
 ...ncluding-many-filters-in-the-order-list.md |   4 +-
 .../error-when-install-customer-credit-app.md |   4 +-
 ...-publishing-dynamic-storage-data-entity.md |   4 +-
 ...a-entity-list-more-than-10000-documents.md |   4 +-
 ...en-running-vtex-link-for-the-first-time.md |   4 +-
 ...-transaction-with-2-cards-mercadopagov1.md |   4 +-
 .../es/error-when-trying-to-open-my-cards.md  |   4 +-
 ...r-when-trying-to-publish-or-link-an-app.md |   4 +-
 .../es/eternal-loading-in-checkout-ui-v5.md   |   4 +-
 docs/known-issues/es/event-inconsistency.md   |   4 +-
 ...be-returned-once-the-order-has-a-change.md |   4 +-
 ...de-products-from-collection-not-working.md |   4 +-
 ...ate-of-special-condition-is-not-deleted.md |   4 +-
 ...eupdatable-due-to-price-variation-limit.md |   4 +-
 ...edirects-not-pointing-back-to-old-route.md |   4 +-
 ...e-also-configured-in-intelligent-search.md |   4 +-
 ...xts-between-different-areas-or-products.md |   4 +-
 ...ist-in-column-creation-date-is-at-utc-0.md |   4 +-
 ...sometimes-the-request-can-not-completed.md |   4 +-
 ...xport-redirects-not-working-as-intended.md |   4 +-
 ...-for-spanish-language-operating-systems.md |   4 +-
 ...the-csv-in-the-sales-performance-module.md |   4 +-
 ...ed-by-brand-does-not-bring-all-the-skus.md |   4 +-
 ...his-character-cut-in-the-image-url-rows.md |   4 +-
 ...working-on-received-skus-processing-tab.md |   4 +-
 ...ot-consider-change-margin-for-upselling.md |   4 +-
 ...t-is-not-recording-a-change-in-the-card.md |   4 +-
 ...ew-skus-load-route-behavior-on-facebook.md |   4 +-
 ...pdate-the-price-in-the-facebook-catalog.md |   4 +-
 ...rumbs-page-title-and-additional-filters.md |   4 +-
 ...heckout-ui-transaction-without-payments.md |   4 +-
 ...ancellation-ppp-when-cancellationidnull.md |   4 +-
 ...s-the-go-to-payment-button-to-disappear.md |   4 +-
 ...ststore-cart-merges-assembly-line-items.md |   4 +-
 ...ng-not-removing-facets-set-to-ne-hidden.md |   4 +-
 ...pi-considering-fuzzy-as-auto-as-default.md |   4 +-
 ...return-seo-information-on-graphql-query.md |   4 +-
 ...rking-correctly-in-firefox-private-mode.md |   4 +-
 ...e-skipping-events-in-fromorders-filters.md |   4 +-
 ...repeated-values-between-the-to-and-from.md |   4 +-
 ...page-status-and-crashing-the-pagination.md |   4 +-
 ...n-trade-policy-not-reflecting-on-pdpplp.md |   4 +-
 ...ting-on-seller-management-ui-after-save.md |   4 +-
 .../es/field-reference-always-set-as-null.md  |   4 +-
 ...any-change-in-order-management-settings.md |   4 +-
 ...not-update-all-the-files-only-the-first.md |   4 +-
 ...-performance-is-not-accepting-uppercase.md |   4 +-
 ...omotion-with-space-blank-is-not-working.md |   4 +-
 ...names-while-applying-additional-filters.md |   4 +-
 ...n-can-show-the-wrong-ammount-of-results.md |   4 +-
 ...t-considering-regionalized-availability.md |   4 +-
 ...den-from-intelligent-search-admin-pages.md |   4 +-
 ...-hide-scenarios-internals-and-usability.md |   4 +-
 ...to-old-component-version-on-site-editor.md |   4 +-
 ...ll-the-profileshipping-data-at-checkout.md |   4 +-
 ...orporatedocument-if-starts-with-letters.md |   4 +-
 ...e-is-not-considered-on-ui-last-searches.md |   4 +-
 .../es/first-subscription-cycle-is-skipped.md |   4 +-
 ...rade-policy-1-when-saving-bundle-prices.md |   4 +-
 ...shipping-option-not-working-as-expected.md |   4 +-
 ...ace-integrate-an-order-erro-code-fmt010.md |   4 +-
 ...t-respecting-the-status-of-the-response.md |   4 +-
 ...ions-that-have-not-1-installment-option.md |   4 +-
 ...it-orders-outside-promotion-restriction.md |   4 +-
 ...ng-time-to-reflect-on-simulation-module.md |   4 +-
 ...-has-seller-groups-on-seller-management.md |   4 +-
 ...egory-tree-on-itemcategory-in-datalayer.md |   4 +-
 ...a-cant-be-informed-for-some-cultureinfo.md |   4 +-
 ...eep-same-sku-order-when-changing-limits.md |   4 +-
 ...t-category-tree-api-with-internal-cache.md |   4 +-
 ...ist-multiple-orders-for-the-same-coupon.md |   4 +-
 ...ed-offers-list-api-not-working-properly.md |   4 +-
 ...-by-refid-returning-null-when-not-found.md |   4 +-
 ...ller-list-responding-with-empty-urllogo.md |   4 +-
 ...sku-by-ean-api-returns-only-active-skus.md |   4 +-
 ...from-component-sku-and-not-from-kit-sku.md |   4 +-
 .../es/gift-card-creation-error-via-admin.md  |   4 +-
 ...ith-the-date-chosen-when-it-was-created.md |   4 +-
 ...ty-id-in-response-to-create-transaction.md |   4 +-
 ...-extra-backslash-when-calling-providers.md |   4 +-
 ...relationname-when-we-make-a-get-request.md |   4 +-
 ...h-permission-from-accessing-it-properly.md |  12 +-
 ...-a-generic-exception-if-it-has-no-price.md |   4 +-
 .../es/gift-list-error-incomplete-address.md  |   4 +-
 ...n-acting-alongside-other-gift-promotion.md |   4 +-
 ...g-r-as-the-automatic-currency-on-the-ui.md |   4 +-
 ...g-refund-after-transaction-cancellation.md |   4 +-
 ...add-credit-to-the-gift-card-through-api.md |   4 +-
 ...ction-api-always-returns-empty-response.md |   4 +-
 ...a-na-ui-nao-e-a-mesma-que-reflete-no-bd.md |   4 +-
 ...-in-catalog-outdated-compared-to-google.md |   4 +-
 ...ng-between-delivery-and-pick-up-options.md |   4 +-
 .../google-bot-terms-appearing-in-results.md  |   4 +-
 ...onent-iframe-has-inconsistent-rendering.md |   4 +-
 ...-the-selected-country-in-some-scenarios.md |   4 +-
 ...les-performance-not-working-as-expected.md |   4 +-
 ...matically-updated-on-intelligent-search.md |   4 +-
 ...s-cms-ignores-array-validation-settings.md |   4 +-
 ...incorrectly-on-promotion-form-interface.md |   4 +-
 ...label-generation-does-not-work-properly.md |   4 +-
 ...ng-do-not-work-on-seller-portal-catalog.md |   4 +-
 ...ng-error-message-fail-to-process-record.md |   4 +-
 ...rted-when-the-account-has-too-many-skus.md |   4 +-
 ...ed-authentication-cookie-for-some-calls.md |   4 +-
 ...ignored-after-one-purchase-is-completed.md |   4 +-
 ...idget-not-shown-if-showmodal-is-enabled.md |   4 +-
 ...er-only-works-for-last-level-categories.md |   4 +-
 ...oducts-if-import-is-made-based-on-skuid.md |   4 +-
 ...-with-adyen-due-to-lack-of-pspreference.md |   4 +-
 ...no-longer-allows-a-cancellation-request.md |   4 +-
 ...se-button-may-not-work-on-the-first-try.md |   4 +-
 ...with-customer-credit-for-1x-installment.md |   4 +-
 ...-items-to-invoice-field-in-the-order-ui.md |   4 +-
 ...e-tax-values-in-the-ui-appear-the-total.md |   4 +-
 ...partial-cancellation-with-mercadopagov1.md |   4 +-
 ...paypal-credentials-for-the-same-account.md |   4 +-
 ...duct-still-appearing-on-pdp-or-checkout.md |   4 +-
 ...tions-appearing-with-brazilian-currency.md |   4 +-
 ...in-billingaddress-field-sent-to-gateway.md |   4 +-
 ...ween-unique-clicks-and-productids-on-is.md |   4 +-
 ...method-boleto-bancario-expiration-dates.md |   4 +-
 ...e-deadlines-of-customer-credit-invoices.md |   4 +-
 ...nsistency-on-the-report-admin-page-data.md |   4 +-
 ...-organization-and-b2b-checkout-settings.md |   4 +-
 ...results-with-large-specification-values.md |   4 +-
 ...ku-has-unit-multiplier-different-than-1.md |   4 +-
 ...ormat-on-the-my-cards-billing-addresses.md |   4 +-
 .../es/incorrect-currency-on-payment-form.md  |   4 +-
 ...in-pickupstoreinfo-after-order-creation.md |   4 +-
 ...display-of-package-quantity-at-checkout.md |   4 +-
 ...he-expiration-date-fields-of-promotions.md |   4 +-
 ...message-error-when-creatingediting-skus.md |   4 +-
 ...-on-order-change-due-to-unit-multiplier.md |   4 +-
 ...hen-unit-multiplier-is-different-from-1.md |   4 +-
 ...iscount-to-all-the-same-items-in-a-cart.md |   4 +-
 ...ients-is-different-than-operation-value.md |   4 +-
 ...-3-payment-methods-one-of-them-being-gc.md |   4 +-
 ...eview-when-items-are-scheduled-delivery.md |   4 +-
 ...rect-shippingestimatedate-for-order-fob.md |   4 +-
 ...-usd-currency-displayed-in-some-locales.md |   4 +-
 ...-value-on-package-due-discount-division.md |   4 +-
 ...e-registered-on-the-fulfillmentendpoint.md |   4 +-
 .../es/incorrectly-updated-inventory.md       |   4 +-
 ...the-highest-instead-of-the-lowest-price.md |   4 +-
 ...s-do-not-work-on-seller-portal-accounts.md |   4 +-
 ...are-same-skuid-in-different-array-items.md |   4 +-
 .../es/infocard-mobile-images-wont-apply.md   |   4 +-
 ...s-from-servers-that-require-user-agents.md |   4 +-
 ...ns-not-updating-automatically-on-pdpplp.md |   4 +-
 ...account-specific-installment-promotions.md |   4 +-
 ...t-ui-is-loose-when-scrolling-the-screen.md |   4 +-
 ...ml-registred-in-the-product-information.md |   4 +-
 ...dido-amazon-quantidade-de-item-invalida.md |   4 +-
 ...e-via-image-url-does-not-work-correctly.md |   4 +-
 ...s-not-in-sync-with-store-configurations.md |   4 +-
 ...-2-variations-of-the-same-languageidiom.md |   4 +-
 ...ot-capturing-sales-events-for-faststore.md |   4 +-
 ...-search-not-returning-correct-sku-order.md |   4 +-
 ...t-settings-search-bar-is-case-sensitive.md |   4 +-
 ...-normalizing-gender-in-portuguese-words.md |   4 +-
 ...f-field-values-is-limited-to-9999-items.md |   4 +-
 ...tate-changes-the-address-insertion-mode.md |   4 +-
 ...ng-state-sends-the-wrong-payment-option.md |   4 +-
 .../intermitent-site-editor-content-loss.md   |   4 +-
 .../internalsearcherror-timeouts-on-portal.md |   4 +-
 ...ering-custom-currency-in-formatcurrency.md |   4 +-
 ...codelength-0-securitycodeisnumeric-true.md |   4 +-
 ...ilable-addresses-with-different-country.md |   4 +-
 ...ue-to-warehouse-id-being-case-sensitive.md |   4 +-
 ...tics-handle-zero-on-left-as-another-sku.md |   4 +-
 ...king-properly-on-seller-portal-accounts.md |   4 +-
 ...ory-notifications-to-indexer-are-cached.md |   4 +-
 .../es/inventory-reserved-items-error.md      |   4 +-
 ...grations-to-notify-external-marketplace.md |   4 +-
 ...egory-names-cause-page-not-found-errors.md |   4 +-
 ...-not-work-as-expected-on-the-search-api.md |   4 +-
 ...d-search-for-searches-with-accent-marks.md |   4 +-
 ...ting-products-that-were-already-updated.md |   4 +-
 ...e-on-translating-titles-for-some-facets.md |   4 +-
 ...operties-beginning-with-the-same-prefix.md |   4 +-
 ...values-in-loyalty-gift-card-at-checkout.md |   4 +-
 ...ss-leading-to-transaction-cancellations.md |   4 +-
 .../es/issues-with-my-account-links.md        |   4 +-
 ...or-transaction-with-minimumvalue-of-001.md |   4 +-
 ...his-item-without-attachment-in-the-cart.md |   4 +-
 ...e-to-cancel-a-transaction-with-maxipago.md |  12 +-
 ...create-a-path-using-content-type-via-ui.md |   4 +-
 ...ith-end-date-from-the-year-2100-onwards.md |   4 +-
 ...-addresses-from-argentina-in-my-account.md |   4 +-
 ...some-addresses-from-chile-in-my-account.md |   4 +-
 ...on-with-the-boleto-method-using-braspag.md |   4 +-
 ...er-is-in-another-package-after-invoiced.md |   4 +-
 ...shown-in-seller-whitelabel-change-order.md |   4 +-
 ...r-location-is-not-defined-with-no-stock.md |   4 +-
 ...f-add-to-cart-event-in-google-analytics.md |   4 +-
 ...-promotions-with-collections-associated.md |   4 +-
 ...ing-in-subscription-plans-configuration.md |   4 +-
 ...action-but-the-inverse-flow-doesnt-work.md |   4 +-
 ...api-is-not-calculating-component-prices.md |   4 +-
 ...ight-can-be-overritten-by-apiwebservice.md |   4 +-
 ...a-request-when-the-accountid-is-missing.md |   4 +-
 ...lecting-gift-items-that-arent-available.md |   4 +-
 ...pis-allowing-invalid-data-in-the-orders.md |   4 +-
 ...lidation-in-the-billingaddress-zip-code.md |   4 +-
 ...eadsheet-error-on-new-collections-admin.md |   4 +-
 ...t-being-changed-by-specification-import.md |   4 +-
 ...same-slas-but-in-a-different-ordination.md |   4 +-
 ...went-wrong-after-changing-pickup-points.md |   4 +-
 ...ed-delivery-is-the-cheapest-and-fastest.md |   4 +-
 ...activate-after-removing-items-from-cart.md |   4 +-
 ...st-option-in-different-sessionsbrowsers.md |   4 +-
 ...catalog-ui-delete-button-not-functional.md |   4 +-
 ...with-less-than-3-characters-in-the-name.md |   4 +-
 ...-cmss-banner-custom-element-not-working.md |   4 +-
 .../es/legacy-collection-import-timeout.md    |   4 +-
 ...n-schedule-does-not-respect-sc-timezone.md |   4 +-
 ...ting-products-wrongly-to-the-collection.md |   4 +-
 ...alidation-diverges-from-new-collections.md |   4 +-
 ...ntrols-do-not-consider-unit-multipliers.md |   4 +-
 ...ntroller-texts-are-not-being-translated.md |   4 +-
 ...sales-channel-management-is-not-working.md |   4 +-
 ...eadsheet-only-returning-active-services.md |   4 +-
 ...y-setup-only-works-opening-in-a-new-tab.md |   4 +-
 ...r-when-translating-with-catalog-graphql.md |   4 +-
 ...e-is-being-modified-by-a-unitmultiplier.md |   4 +-
 ...tcher-doesnt-work-in-myvtex-environment.md |   4 +-
 ...with-password-cannot-be-undone-in-admin.md |   4 +-
 ...ess-permission-did-not-work-as-expected.md |   4 +-
 ...es-not-work-when-productprice-as-0-zero.md |   4 +-
 ...ault-currency-instead-of-local-currency.md |   4 +-
 ...er-the-reversal-does-not-actually-occur.md |   4 +-
 ...yment-condition-requires-authentication.md |   4 +-
 ...o-shipping-methods-one-for-the-same-day.md |  12 +-
 ...ated-via-site-editor-from-cms-migration.md |   4 +-
 ...reated-in-oms-and-without-log-in-bridge.md |   4 +-
 ...nce-not-set-to-an-instance-of-an-object.md |   4 +-
 ...specifications-from-another-marketplace.md |   4 +-
 ...just-plaintextdescription-specification.md |   4 +-
 ...ed-fob-order-with-conventional-delivery.md |   4 +-
 ...led-on-marketplace-didnt-cancel-on-vtex.md |   4 +-
 ...marketplace-didnt-update-status-on-vtex.md |   4 +-
 ...nce-not-set-to-an-instance-of-an-object.md |   4 +-
 ...ketplace-are-not-being-approved-on-vtex.md |   4 +-
 ...status-for-delivered-on-the-marketplace.md |   4 +-
 ...ine-luiza-some-skus-do-not-update-price.md |   4 +-
 ...-deve-ser-igual-ou-menor-a-data-de-hoje.md |   4 +-
 ...chantname-in-the-subaccount-environment.md |   4 +-
 .../mandatory-service-working-as-optional.md  |   4 +-
 ...ied-when-creating-a-product-through-api.md |   4 +-
 ...d-to-work-with-2digit-decimal-precision.md |   4 +-
 ...-of-collections-doesnt-work-as-expected.md |   4 +-
 ...using-multiple-coupons-feature-and-utms.md |   4 +-
 ...value-when-campaign-audience-is-matched.md |   4 +-
 ...lues-due-to-certain-purchase-conditions.md |   4 +-
 ...snt-consider-manual-price-for-discounts.md |   4 +-
 ...est-doesnt-consider-some-discount-types.md |   4 +-
 ...ransactions-are-being-processed-as-visa.md |   4 +-
 ...erdata-export-download-link-unavailable.md |   4 +-
 ...ved-skus-api-returning-invalid-sellerid.md |   4 +-
 ...ng-height-width-weight-and-length-to-01.md |   4 +-
 ...uctsku-name-contains-special-characters.md |   4 +-
 ...hipping-discount-not-updating-pricetags.md |   4 +-
 ...rrect-discount-when-using-the-same-item.md |   4 +-
 ...cannot-be-changed-by-franchise-accounts.md |   4 +-
 ...t-passing-a-symbol-or-special-character.md |   4 +-
 ...o-meli-without-being-mapped-from-seller.md |   4 +-
 ...ntegration-with-a-non-expected-behavior.md |   4 +-
 ...tomatic-messages-mercado-livre-messages.md |   4 +-
 ...enu-not-showing-the-orderid-information.md |   4 +-
 ...aused-when-the-marketplace-ad-is-paused.md |   4 +-
 ...ads-not-being-linked-to-bridge-products.md |   4 +-
 .../es/meli-customdata-paymentfield.md        |   4 +-
 .../es/meli-error-importing-some-orders.md    |   4 +-
 ...nput-string-was-not-in-a-correct-format.md |   4 +-
 ...-error-while-sending-the-order-tracking.md |   4 +-
 ...quotation-for-multiple-officialstoreids.md |   4 +-
 ...ull-orders-not-creating-invoice-in-vtex.md |   4 +-
 .../known-issues/es/meli-images-limitation.md |   4 +-
 ...ct-value-when-client-has-coupon-on-meli.md |   4 +-
 ...-errors-from-meli-429-too-many-requests.md |   4 +-
 ...-for-peru-venezuela-equador-and-uruguai.md |   4 +-
 ...meli-integration-missing-billingaddress.md |   4 +-
 ...ntegration-zipcodes-11111-meli-limaperu.md |   4 +-
 .../es/meli-kit-stock-integration.md          |   4 +-
 ...ding-product-specification-as-variation.md |   4 +-
 .../es/meli-oms-label-printing.md             |   4 +-
 ...tex-oms-for-multiples-accounts-scenario.md |   4 +-
 ...li-plaintextdescriptionmeli-not-working.md |   4 +-
 ...on-center-not-linking-skus-to-promotion.md |   4 +-
 docs/known-issues/es/meli-promotion-center.md |   4 +-
 .../es/meli-promotions-ui-error.md            |   4 +-
 ...bre-is-paused-when-a-sku-is-inactivated.md |   4 +-
 ...hart-not-working-for-sizes-with-letters.md |   4 +-
 ...eli-sizechart-issue-attribute-not-valid.md |   4 +-
 ...t-set-to-an-instance-of-an-object-error.md |   4 +-
 .../es/meli-update-stockprice-issue.md        |   4 +-
 ...-allowed-unique-attributes-combinations.md |   4 +-
 ...ybox-doesnt-update-shippingmode-for-me2.md |   4 +-
 ...mercado-livre-attribute-size-is-missing.md |   4 +-
 ...bridge-isnt-logging-some-error-messages.md |   4 +-
 ...-not-showing-the-shippingid-information.md |   4 +-
 .../es/mercado-livre-mapper-attribute-size.md |   4 +-
 ...ve-underreview-validation-in-update-sku.md |   4 +-
 ...bridge-isnt-logging-some-error-messages.md |   4 +-
 ...t-comes-with-phone-user-data-value-as-0.md |   4 +-
 ...working-for-the-facet-productclusterids.md |   4 +-
 ...for-some-clients-in-customer-credit-api.md |   4 +-
 ...re-not-receiving-the-fixed-price-report.md |   4 +-
 ...-value-has-changed-is-shown-incorrectly.md |   4 +-
 ...ing-too-long-to-return-the-informations.md |   4 +-
 ...n-field-cannot-be-deleted-through-admin.md |   4 +-
 ...messages-only-appear-after-a-second-try.md |   4 +-
 ...does-not-show-sku-specs-in-b2b-scenario.md |   4 +-
 .../minicart-error-when-updating-promotion.md |   4 +-
 ...sending-options-for-already-added-items.md |   4 +-
 ...configuration-set-to-a-different-option.md |   4 +-
 ...causes-antifraud-to-cancel-transactions.md |   4 +-
 ...price-facetfilter-at-intelligent-search.md |   4 +-
 ...en-this-type-of-modal-are-configured-ok.md |   4 +-
 ...rent-texts-between-api-and-logistics-ui.md |   4 +-
 ...cated-divergences-setup-shipping-policy.md |   4 +-
 ...pdate-the-department-id-on-the-products.md |   4 +-
 ...pected-behaviors-in-the-categories-tree.md |   4 +-
 .../multiple-sku-promotion-api-not-working.md |   4 +-
 ...eiver-name-field-doesnt-recognize-input.md |   4 +-
 ...shivering-when-trying-to-add-a-new-card.md |   4 +-
 ...-not-working-for-some-legacy-connectors.md |   4 +-
 ...field-filled-in-the-address-information.md |   4 +-
 ...ntlink-invoice-even-if-the-field-is-set.md |   4 +-
 ...ra-resolvelo-tente-novamente-mais-tarde.md |  12 +-
 ...tion-is-associated-with-a-pick-up-point.md |   4 +-
 ...-the-address-line-2-this-appear-as-null.md |   4 +-
 ...-spinner-button-is-not-working-properly.md |   4 +-
 ...hen-accessing-from-an-dependent-account.md |   4 +-
 ...atically-translate-on-the-product-admin.md |   4 +-
 ...s-adding-credit-although-it-returns-500.md |   4 +-
 ...ders-placed-at-magalu-were-as-incomplet.md |   4 +-
 .../negative-amounts-in-split-recipients.md   |   4 +-
 ...ot-handle-non-existent-productid-import.md |   4 +-
 ...eased-filter-is-not-working-for-exports.md |  12 +-
 .../es/new-collections-page-not-loading.md    |   4 +-
 ...s-the-correct-delivery-window-estimated.md |   4 +-
 ...in-orders-with-partial-or-total-invoice.md |   4 +-
 ...e-customers-id-document-for-example-cpf.md |   4 +-
 ...the-invoiced-value-on-return-items-page.md |   4 +-
 ...e-and-lastdeliveryday-for-high-timecost.md |   4 +-
 ...k-to-the-user-when-something-goes-wrong.md |  12 +-
 ...as-expected-with-subtraction-operations.md |   4 +-
 ...distributed-among-all-items-in-the-cart.md |   4 +-
 ...plit-for-second-item-incorrect-discount.md |   4 +-
 ...proper-detached-sku-on-pdp-in-a-new-tab.md |   4 +-
 ...he-productsku-specification-spreadsheet.md |   4 +-
 ...when-entity-has-more-than-10k-documents.md |   4 +-
 ...on-order-detail-ui-when-exceeding-limit.md |   4 +-
 ...upted-file-when-there-are-no-skus-found.md |   4 +-
 ...esponse-with-more-than-65536-characters.md |   4 +-
 ...r-does-not-correspond-to-correct-number.md |   4 +-
 ...s-not-reliable-in-vtexvtex-integrations.md |   4 +-
 ...t-first-informs-an-address-for-delivery.md |   4 +-
 ...-filter-selected-has-special-characters.md |   4 +-
 ...pears-even-after-filled-until-save-data.md |   4 +-
 ...er-only-captures-the-information-of-the.md |   4 +-
 ...rbypriceasc-could-bring-the-wrong-order.md |   4 +-
 ...bypricedesc-could-bring-the-wrong-order.md |   4 +-
 ...dal-hook-affects-all-modals-on-the-page.md |   4 +-
 ...orrectly-due-to-null-documenttype-field.md |   4 +-
 ...rd-reset-not-logging-out-other-sessions.md |   4 +-
 ...ain-from-b2b-orders-history-doesnt-work.md |   4 +-
 ...arketplace-but-not-integrated-into-vtex.md |   4 +-
 ...ization-lessthan-100-goes-with-the-flow.md |   4 +-
 ...hen-seller-has-a-different-country-code.md |   4 +-
 ...t-be-created-due-to-invalid-credit-card.md |   4 +-
 ...r-card-info-causing-confusing-on-status.md |   4 +-
 ...o-price-divergence-on-fulfillment-layer.md |   4 +-
 .../es/order-doesnt-update-status-in-oms.md   |   4 +-
 ...some-order-with-big-payload-on-the-list.md |   4 +-
 ...erly-due-double-space-on-promotion-name.md |   4 +-
 ...uotes-in-the-promotion-name-or-sku-name.md |   4 +-
 ...carrier-leaves-label-barcode-incomplete.md |   4 +-
 ...-triggered-the-transaction-total-refund.md |   4 +-
 ...nal-amount-is-refunded-using-new-ui-oms.md |   4 +-
 ...-and-original-order-have-the-same-value.md |   4 +-
 ...nses-field-from-get-payment-details-api.md |   4 +-
 ...ler-status-cancellationrequestdeniedffm.md |   4 +-
 ...o-missing-payment-approved-notification.md |   4 +-
 ...annot-be-invoiced-referencing-the-items.md |   4 +-
 ...-the-items-and-refund-the-total-payment.md |   4 +-
 ...-conectors-like-payment-app-or-redirect.md |   4 +-
 ...eled-but-the-payment-remains-authorized.md |   4 +-
 ...ing-invoice-does-not-update-to-invoiced.md |   4 +-
 .../es/order-xxx-with-invalid-status.md       |   4 +-
 ...r-the-same-item-under-different-sellers.md |   4 +-
 ...difying-item-attachments-in-the-catalog.md |   4 +-
 ...id-scheduled-delivery-that-cant-be-used.md |   4 +-
 ...changes-in-itemattachment-and-offerings.md |   4 +-
 ...rs-data-even-for-authorized-credentials.md |   4 +-
 ...form-not-updating-after-order-is-placed.md |   4 +-
 ...rd-that-were-removed-via-myaccount-page.md |   4 +-
 ...of-product-fields-and-skus-is-not-saved.md |   4 +-
 ...f-product-fields-and-skus-is-not-saved1.md |   4 +-
 ...ps-from-the-root-category-does-not-work.md |   4 +-
 ...-is-refused-for-the-regular-items-order.md |   4 +-
 ...hat-dont-update-the-invoice-at-netshoes.md |   4 +-
 ...oice-value-in-output-invoice-validation.md |   4 +-
 ...e-fromorders-for-state-payment-approved.md |   4 +-
 ...th-asterisks-in-the-address-and-profile.md |   4 +-
 ...especting-the-cancellation-grace-period.md |   4 +-
 ...aceitems-is-not-opening-on-new-ui-admin.md |   4 +-
 ...splayed-where-it-should-show-the-sku-id.md |   4 +-
 ...nvoiceaddress-created-through-native-ui.md |   4 +-
 ...some-details-in-the-shipping-sla-object.md |   4 +-
 ...hen-uploading-a-new-version-not-working.md |   4 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   4 +-
 ...n-performing-2-product-changes-in-a-row.md |   4 +-
 ...as-billing-address-on-the-checkout-page.md |   4 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   4 +-
 .../outdated-url-on-the-update-binding-ui.md  |   4 +-
 ...e-when-printing-ctrlp-is-used-in-chrome.md |   4 +-
 ...iggered-twice-when-accessing-my-account.md |   4 +-
 ...being-duplicated-in-custom-search-pages.md |   4 +-
 ...h-results-not-working-on-giftlist-pages.md |   4 +-
 ...esnt-reset-when-changing-search-context.md |   4 +-
 ...he-same-sla-affecting-the-purchase-flow.md |   4 +-
 ...-cart-sometimes-returns-null-api-result.md |   4 +-
 ...cessing-transactions-as-prepaid-in-full.md |   4 +-
 ...-with-swl-when-using-identical-typesids.md |   4 +-
 ...t-differ-from-active-payment-conditions.md |   4 +-
 ...ssociated-payment-condition-is-disabled.md |   4 +-
 ...ot-applied-in-the-b2b-checkout-settings.md |   4 +-
 ...-assigned-after-approving-organizations.md |   4 +-
 ...rmation-in-the-payload-to-the-connector.md |   4 +-
 ...rice-comes-exclusively-from-manualprice.md |   4 +-
 ...er-for-multilevel-omnichannel-inventory.md |   4 +-
 ...-respect-the-minimum-installment-amount.md |   4 +-
 ...ecial-characters-are-passed-on-the-link.md |   4 +-
 .../es/phone-field-order-netshoes.md          |   4 +-
 ...f-switching-between-delivery-and-pickup.md |   4 +-
 ...in-marketplaces-with-multilevel-sellers.md |   4 +-
 ...eocoordinates-without-a-google-maps-key.md |   4 +-
 ...-shows-even-inactive-or-invalid-options.md |   4 +-
 ...earch-will-not-working-with-enterreturn.md |   4 +-
 ...d-in-the-shipping-policy-after-deletion.md |   4 +-
 ...d-after-searching-addresses-in-map-mode.md |   4 +-
 ...ickup-points-not-indexed-in-master-data.md |   4 +-
 ...-same-id-pattern-show-product-available.md |   4 +-
 ...the-same-cart-are-not-working-correctly.md |   4 +-
 ...ndependent-pickups-on-the-purchase-flow.md |   4 +-
 ...in-the-cms-does-not-display-all-content.md |   4 +-
 ...ers-showing-instead-of-the-correct-data.md |   4 +-
 ...etween-items-that-appear-more-than-once.md |   4 +-
 ...address-options-for-recurring-customers.md |   4 +-
 ...-cookies-when-client-logout-at-checkout.md |   4 +-
 ...respect-the-tag-principal-of-skus-image.md |   4 +-
 ...tag-not-updating-when-changing-metadata.md |   4 +-
 ...ging-out-when-using-callcenter-operator.md |   4 +-
 ...ct-with-parameters-in-url-does-not-work.md |   4 +-
 ...ssing-the-url-with-pagination-parameter.md |   4 +-
 ...page-it-is-shown-on-the-admin-interface.md |   4 +-
 ...-pdp-doesnt-reset-when-changing-product.md |   4 +-
 ...ss-and-receiver-name-in-the-checkout-ui.md |   4 +-
 ...th-blank-postal-code-in-the-checkout-ui.md |   4 +-
 ...-notification-in-the-ui-api-and-gateway.md |   4 +-
 ...-loop-in-the-shipping-preview-component.md |   4 +-
 ...he-legacy-cms-collection-is-not-working.md |   4 +-
 ...-incomplete-when-using-category-filters.md |   4 +-
 ...t-is-not-accepted-by-the-import-process.md |   4 +-
 ...-of-spot-price-instead-of-regular-price.md |   4 +-
 ...doesnt-correspond-to-the-search-results.md |   4 +-
 ...-minimum-value-after-selecting-a-filter.md |   4 +-
 ...-twice-and-one-is-from-assembly-options.md |   4 +-
 ...-updates-with-cache-on-end-applications.md |   4 +-
 ...ion-limit-only-works-in-the-main-policy.md |   4 +-
 ...-to-int32-max-value-on-change-price-api.md |   4 +-
 ...ted-to-int32-max-value-on-checkout-apis.md |   4 +-
 .../es/pricing-api-allows-negative-values.md  |   4 +-
 ...bility-post-prices-route-is-losing-data.md |   4 +-
 ...ducts-keyword-not-considering-stopwords.md |   4 +-
 ...-using-period-of-time-special-condition.md |   4 +-
 ...m-to-pay-with-giftcard-two-cards-option.md |   4 +-
 ...-value-field-when-buying-with-two-cards.md |   4 +-
 ...with-phone-validation-on-mobile-devices.md |   4 +-
 ...ems-to-cart-in-io-that-have-attachments.md |   4 +-
 ...e-inventory-by-admin-page-with-error-ui.md |   4 +-
 ...problems-with-payment-condition-storage.md |   4 +-
 ...ayed-when-using-multiple-sales-channels.md |   4 +-
 ...ed-in-the-pickups-in-cart-display-modal.md |   4 +-
 ...ion-from-datalayer-with-a-wrong-sorting.md |   4 +-
 ...product-comissioning-inconsistent-cache.md |   4 +-
 .../es/product-created-with-id-0.md           |   4 +-
 ...hlights-doesnt-work-into-a-product-list.md |   4 +-
 ...on-admin-changes-with-more-than-70-skus.md |   4 +-
 ...orting-doesnt-respect-the-catalog-order.md |   4 +-
 ...date-api-allows-n-in-the-textlink-field.md |   4 +-
 ...m-doesnt-work-on-catalogs-redesigned-ui.md |   4 +-
 ...ku-name-when-the-product-has-only-1-sku.md |   4 +-
 .../es/product-page-sessions-not-working.md   |   4 +-
 ...e-not-considering-default-seller-in-pdp.md |   4 +-
 ...ector-error-for-high-resolution-screens.md |   4 +-
 ...r-not-working-on-seller-portal-accounts.md |   4 +-
 ...at-for-offers-with-more-than-one-seller.md |   4 +-
 ...specification-export-index-out-of-range.md |   4 +-
 ...ection-module-assuming-incorrect-values.md |   4 +-
 ...tion-module-does-not-list-root-category.md |   4 +-
 ...oes-not-trigger-the-products-indexation.md |   4 +-
 ...chresolver-is-incorrect-due-to-rounding.md |   4 +-
 ...-unavailable-even-with-franchised-stock.md |   4 +-
 ...ck-event-considers-the-incorrect-sku-id.md |   4 +-
 ...click-event-not-triggering-in-searchbar.md |   4 +-
 ...-checkboxes-if-you-keep-the-drawer-open.md |   4 +-
 ...cts-when-the-sku-is-individually-showed.md |   4 +-
 ...uplicate-when-the-quantity-is-increased.md |   4 +-
 ...d-when-the-productname-contains-numbers.md |   4 +-
 ...flag-and-discount-after-promotion-ended.md |   4 +-
 ...wn-as-unavailable-at-intelligent-search.md |   4 +-
 ...ted-with-duplicated-skus-on-the-catalog.md |   4 +-
 ...ed-as-with-promotion-for-search-filters.md |   4 +-
 ...-the-admin-when-searching-by-product-id.md |   4 +-
 ...sellers-are-appearing-in-the-end-of-plp.md |   4 +-
 ...form-allows-utf16-format-uploaddownload.md |   4 +-
 ...productsskus-import-does-not-support-lb.md |   4 +-
 ...complete-profile-with-ignoreprofiledata.md |   4 +-
 ...ed-after-adding-client-preferences-data.md |   4 +-
 ...show-splitted-after-adding-profile-data.md |   4 +-
 ...not-working-alongside-regular-promotion.md |   4 +-
 ...equency-not-working-on-recurring-cycles.md |   4 +-
 ...t-performance-or-lead-to-timeout-errors.md |   4 +-
 ...hod-doesnt-works-for-whitelabel-sellers.md |   4 +-
 ...thods-do-not-appear-on-the-product-page.md |   4 +-
 .../es/promotions-microrounding-divergence.md |   4 +-
 ...-sorting-filtering-by-price-or-discount.md |   4 +-
 ...s-ui-loading-wrong-currency-information.md |   4 +-
 ...ty-blockclass-from-infocard-not-working.md |   4 +-
 ...t-split-items-and-free-shipping-applied.md |   4 +-
 ...er-chooses-to-pay-with-giftcard-and-pse.md |  12 +-
 ...-is-shown-in-the-license-manager-module.md |   4 +-
 ...tes-in-mercado-livre-are-not-integrated.md |   4 +-
 ...ly-when-2-categories-have-the-same-name.md |   4 +-
 ...-in-stores-without-geopositioning-setup.md |   4 +-
 ...nd-is-stuck-on-freight-type-has-changed.md |   4 +-
 ...he-error-receiver-name-field-is-invalid.md |   4 +-
 .../put-price-overwrites-kit-price-logic.md   |   4 +-
 ...-item-with-product-list-component-io-sf.md |   4 +-
 ...he-limit-value-when-user-quickly-clicks.md |   4 +-
 ...-wont-let-me-change-the-value-by-typing.md |   4 +-
 ...h-after-reaching-max-available-qunatity.md |   4 +-
 ...g-longer-than-expected-to-update-status.md |   4 +-
 ...n-the-sku-is-sold-by-more-than-1-seller.md |   4 +-
 ...admins-in-other-languages-only-pt-en-es.md |   4 +-
 ...ter-do-not-work-with-special-characters.md |   4 +-
 ...ceived-skus-review-tab-missing-products.md |   4 +-
 ...parameters-in-cms-builder-does-not-work.md |   4 +-
 ...irects-are-being-counted-multiple-times.md |   4 +-
 ...inks-when-using-in-the-final-of-the-url.md |   4 +-
 ...rresponding-mutation-in-the-graphql-app.md |   4 +-
 ...avior-not-consistent-between-api-and-ui.md |   4 +-
 ...es-us-to-misidentify-mastercard-as-visa.md |   4 +-
 ...auses-us-to-misidentify-the-cards-brand.md |   4 +-
 ...on-api-returns-seller-list-due-to-cache.md |   4 +-
 ...ies-arent-considered-while-filtering-or.md |   4 +-
 ...-while-requesting-nonwhitelabel-sellers.md |   4 +-
 ...delivery-to-pickup-on-the-checkout-page.md |   4 +-
 ...onflicts-with-value-filters-on-the-cart.md |   4 +-
 ...is-not-inactivating-skus-without-refids.md |   4 +-
 .../render-component-issues-on-site-editor.md |   4 +-
 ...ollection-failing-for-large-collections.md |   4 +-
 ...mmary-for-carts-with-more-than-20-items.md |   4 +-
 ...ing-orders-with-different-sales-channel.md |   4 +-
 .../es/replicated-pending-payment-emails.md   |   4 +-
 ...ing-new-events-when-using-legacy-stores.md |   4 +-
 ...g-is-inconsistent-when-running-ab-tests.md |   4 +-
 ...ecurity-policy-could-break-the-checkout.md |   4 +-
 ...users-orders-api-does-not-return-paging.md |   4 +-
 ...queid-arrays-it-is-not-visible-properly.md |   4 +-
 ...ivering-to-final-customer-on-my-account.md |   4 +-
 .../review-flow-for-updatestock-netshoes.md   |   4 +-
 ...ve-a-different-value-added-to-gift-card.md |   4 +-
 .../rewriter-is-not-receiving-url-updates.md  |   4 +-
 .../rounding-of-totalvalue-in-listorders.md   |   4 +-
 ...-items-with-unitmultiplier-other-than-1.md |   4 +-
 ...terms-of-quantity-of-packages-and-items.md |   4 +-
 ...-assigned-after-approving-organizations.md |   4 +-
 ...annel-info-divergent-between-ui-and-api.md |   4 +-
 ...a-problem-with-some-european-time-zones.md |   4 +-
 ...when-modifying-imported-search-synonyms.md |   4 +-
 .../scheduled-banners-doesnt-work-properly.md |   4 +-
 ...witching-between-delivery-and-scheduled.md |   4 +-
 ...ailing-for-custom-types-in-headless-cms.md |   4 +-
 ...e-when-zooming-after-search-page-render.md |   4 +-
 ...en-theres-a-slider-layout-on-background.md |   4 +-
 .../es/search-analytics-duplicated-events.md  |   4 +-
 ...een-versions-withwithout-funnel-metrics.md |   4 +-
 ...-api-does-not-accept-special-characters.md |   4 +-
 ...-skus-for-fqspecificationfilter-queries.md |   4 +-
 ...login-in-using-the-call-center-operator.md |   4 +-
 ...wer-case-and-uppercase-for-first-letter.md |   4 +-
 ...rl-after-navigating-through-suggestions.md |   4 +-
 ...the-operator-and-for-trigger-conditions.md |   4 +-
 ...rch-by-ean-not-working-on-received-skus.md |   4 +-
 ...search-filters-disappear-intermittently.md |   4 +-
 ...account-management-when-using-b2b-suite.md |   4 +-
 ...-price-range-yielding-incorrect-results.md |   4 +-
 ...ng-properly-on-store-framework-jamstack.md |   4 +-
 ...lations-over-already-translated-content.md |   4 +-
 ...-does-not-work-on-legacy-cms-collection.md |   4 +-
 ...nto-fuzzy-when-using-special-characters.md |   4 +-
 ...s-with-at-the-end-not-working-correctly.md |   4 +-
 ...t-when-the-value-contains-a-plus-symbol.md |   4 +-
 ...-updated-only-after-refreshing-the-page.md |   4 +-
 ...mmercial-policy-is-not-working-properly.md |   4 +-
 ...sion-updates-does-not-index-binded-skus.md |   4 +-
 ...-creation-does-not-add-selected-sellers.md |   4 +-
 .../seller-logo-not-being-saved-as-an-url.md  |   4 +-
 ...al-account-not-able-to-export-baseprice.md |   4 +-
 ...product-doesnt-load-when-without-images.md |   4 +-
 ...price-condition-not-working-as-expected.md |   4 +-
 ...-specifications-dropdown-malfunctioning.md |   4 +-
 ...s-to-reindex-when-inactivating-a-seller.md |   4 +-
 ...y-of-the-item-to-choose-the-best-option.md |   4 +-
 ...ced-with-problem-in-the-payment-capture.md |   4 +-
 ...ype-name-field-wrongly-returned-via-api.md |   4 +-
 ...ces-are-not-updated-when-added-to-items.md |   4 +-
 ...hen-they-are-not-in-the-same-path-level.md |   4 +-
 ...esnt-update-expiration-period-of-quotes.md |   4 +-
 .../es/shared-products-import-error.md        |   4 +-
 ...d-in-waiting-for-more-information-state.md |   4 +-
 ...ed-delivery-and-lean-shipping-activated.md |   4 +-
 ...-frozen-when-trying-to-select-an-option.md |   4 +-
 ...atter-of-priority-even-with-better-cost.md |   4 +-
 ...layed-as-active-in-the-new-logistics-ui.md |   4 +-
 ...deliver-on-weekends-is-being-considered.md |   4 +-
 ...es-not-show-message-error-on-simulation.md |   4 +-
 ...e-in-case-of-multiple-packagesdeadlines.md |   4 +-
 ...does-not-use-sla-name-for-display-in-ui.md |   4 +-
 ...s-package-split-for-pickup-and-shipping.md |   4 +-
 ...ng-the-date-when-its-scheduled-delivery.md |   4 +-
 ...g-the-price-when-its-scheduled-delivery.md |   4 +-
 ...view-wrongly-reporting-pickup-selection.md |   4 +-
 ...owing-unavailability-message-for-pickup.md |   4 +-
 ...s-postal-code-input-field-is-not-hidden.md |   4 +-
 ...tion-does-not-generate-highlights-flags.md |   4 +-
 ...rent-slas-causing-divergence-in-tax-hub.md |   4 +-
 ...e-shipping-options-are-being-calculated.md |   4 +-
 ...for-some-countries-united-arab-emirates.md |   4 +-
 .../es/shopee-could-not-create-product.md     |   4 +-
 ...pee-failed-to-create-product-variations.md |   4 +-
 ...place-shopeeskuhelper-sku-update-failed.md |   4 +-
 ...oducts-ui-brokes-with-too-many-products.md |   4 +-
 ...-catalog-v2-on-shipping-simulation-page.md |   4 +-
 ...ormation-generates-data-loss-in-the-api.md |  12 +-
 ...t-condition-does-not-appear-at-checkout.md |   4 +-
 ...nt-condition-does-not-appear-at-chekout.md |   4 +-
 ...ku-with-multiple-ean-in-merchant-center.md |   4 +-
 ...y-is-not-accessed-using-its-direct-link.md |   4 +-
 ...low-changes-on-the-conditional-template.md |   4 +-
 ...ks-when-accessing-the-landing-route-url.md |   4 +-
 ...ittent-rendering-issues-in-small-screen.md |   4 +-
 ...rsion-when-accessing-via-ipad-on-safari.md |   4 +-
 ...-from-other-subaccounts-and-mainaccount.md |   4 +-
 .../es/sitemap-isnt-being-generated.md        |   4 +-
 .../es/sitemap-isnt-being-generatedupdated.md |   4 +-
 ...-cause-problems-in-site-editor-features.md |   4 +-
 ...eference-code-longer-than-50-characters.md |   4 +-
 ...after-throttling-on-marketplace-catalog.md |   4 +-
 ...e-update-does-not-update-v-version-tags.md |   4 +-
 ...ut-doesnt-log-correct-message-on-bridge.md |   4 +-
 ...s-not-responding-with-the-text-property.md |   4 +-
 ...pping-simulation-and-registration-admin.md |  12 +-
 ...ot-follow-the-sku-position-of-the-admin.md |   4 +-
 ...c-is-not-being-disable-in-amazon-portal.md |   4 +-
 ...splay-mode-select-not-working-in-shelfs.md |   4 +-
 ...ving-similar-variations-with-substrings.md |   4 +-
 .../es/sku-selector-with-multilpe-contexts.md |   4 +-
 ...s-only-available-in-a-whitelabel-seller.md |   4 +-
 ...sku-variations-doesnt-return-in-the-plp.md |   4 +-
 .../es/skus-expiring-in-merchant-center.md    |   4 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   4 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   4 +-
 ...rs-are-created-with-images-out-of-order.md |   4 +-
 ...-value-tables-at-first-for-a-value-type.md |   4 +-
 ...o-cache-in-estimated-date-of-30-seconds.md |   4 +-
 ...using-prop-infinite-as-always-on-mobile.md |   4 +-
 ...talog-facets-api-have-different-formats.md |   4 +-
 ...-message-centre-module-returns-an-error.md |   4 +-
 ...ail-template-redirects-user-to-404-page.md |   4 +-
 ...-are-not-able-to-be-saved-on-my-account.md |   4 +-
 ...cted-when-viewed-through-safari-browser.md |   4 +-
 ...king-properly-on-seller-portal-accounts.md |   4 +-
 ...ons-cant-be-displayed-in-search-context.md |   4 +-
 ...-being-uploaded-to-the-facebook-catalog.md |   4 +-
 .../es/some-skus-dont-integrate-dafiti.md     |   4 +-
 ...ipped-from-product-searches-or-indexing.md |   4 +-
 ...played-in-admin-but-are-visible-via-api.md |   4 +-
 .../some-unexpected-behavior-in-masterdata.md |   4 +-
 ...error-is-displayed-in-the-catalog-admin.md |   4 +-
 ...cessing-a-and-p-routes-in-portal-stores.md |   4 +-
 ...incomplete-address-and-tried-to-edit-it.md |   4 +-
 ...rent-on-stores-integrated-before-a-date.md |   4 +-
 ...fects-address-field-display-at-checkout.md |   4 +-
 ...ses-internal-logistics-requests-to-fail.md |   4 +-
 ...special-character-in-seller-name-report.md |   4 +-
 ...t-be-used-for-cnpj-search-on-masterdata.md |   4 +-
 ...enumber-cause-postpurchase-flow-to-fail.md |   4 +-
 ...or-radio-box-category-type-of-selection.md |   4 +-
 ...tion-field-delete-button-not-functional.md |   4 +-
 ...ecification-value-ordering-is-not-saved.md |   4 +-
 .../specifications-multiplied-on-catalog.md   |   4 +-
 ...der-with-value-as-0-zero-on-the-invoice.md |  12 +-
 ...package-suggestion-not-working-properly.md |   4 +-
 ...rect-for-products-with-multiple-sellers.md |   4 +-
 ...fter-approving-the-organization-request.md |   4 +-
 ...s-erro-de-processamento-shipping-policy.md |   4 +-
 ...different-from-the-current-order-status.md |   4 +-
 ...sactions-list-doesnt-match-actual-state.md |   4 +-
 ...ompleted-even-after-receiving-error-500.md |   4 +-
 ...ows-invalid-commercial-condition-values.md |   4 +-
 ...ingunitbyean-returns-404-for-eans-with-.md |  12 +-
 ...-method-allows-to-insert-existent-refid.md |   4 +-
 ...ermissions-app-sets-documenttype-as-cpf.md |   4 +-
 ...ssions-considers-inactive-organizations.md |   4 +-
 ...quested-in-the-address-step-at-checkout.md |   4 +-
 .../stucked-not-found-routes-on-platform.md   |   4 +-
 ...not-show-active-subscriptions-correctly.md |   4 +-
 ...subscription-event-history-out-of-order.md |   4 +-
 ...s-dont-work-properly-for-some-languages.md |   4 +-
 ...oading-the-skus-association-spreadsheet.md |   4 +-
 ...-dashboard-with-conflicting-information.md |   4 +-
 ...ing-failure-or-masterdata-query-failure.md |   4 +-
 ...he-sku-has-linked-to-a-gift-unavailable.md |   4 +-
 ...ckuppointid-contains-special-characters.md |   4 +-
 ...point-and-does-not-have-one-of-the-skus.md |   4 +-
 ...th-less-than-3-characters-does-not-work.md |   4 +-
 ...forming-unitmultiplier-less-than-1-to-0.md |   4 +-
 ...via-update-selected-address-information.md |   4 +-
 ...-revert-the-zoom-causing-display-issues.md |   4 +-
 ...he-pages-with-collections-or-categories.md |   4 +-
 ...senting-success-even-for-failed-actions.md |   4 +-
 ...-not-reflecting-on-the-explained-search.md |   4 +-
 ...onyms-not-shown-in-the-explained-search.md |   4 +-
 ...idering-seller-1-for-rule-sellers-limit.md |   4 +-
 ...ometimes-appear-on-list-format-plp-view.md |   4 +-
 .../es/tax-apportionment-divergence.md        |   4 +-
 ...s-not-displayng-marketing-tags-dropdown.md |   4 +-
 ...-discounts-when-manual-price-is-applied.md |   4 +-
 ...re-than-once-when-using-assembly-option.md |   4 +-
 ...otions-with-promotion-that-splits-items.md |   4 +-
 ...-nominal-promotions-when-placing-orders.md |   4 +-
 ...en-when-a-cart-has-two-selected-address.md |   4 +-
 ...document-data-instead-of-customer-email.md |   4 +-
 ...ith-requiresauthenticationtoloadprofile.md |   4 +-
 ...nt-accept-special-characters-aside-from.md |   4 +-
 .../term-makes-search-api-have-no-return.md   |   4 +-
 ...-not-being-translated-using-site-editor.md |   4 +-
 ...-not-being-translated-using-site-editor.md |   4 +-
 ...-not-being-translated-using-site-editor.md |   4 +-
 ...-marketplace-upon-approvals-reoccurence.md |   4 +-
 ...textlink-created-with-special-character.md |   4 +-
 ...t-has-never-added-a-new-provider-before.md |   4 +-
 ...rk-on-the-site-editor-with-custom-pages.md |   4 +-
 ...d-returns-to-the-payment-with-two-cards.md |   4 +-
 ...-payments-are-not-reflected-in-checkout.md |   4 +-
 ...rios-when-the-authentication-has-failed.md |   4 +-
 ...e-two-or-more-items-share-the-same-name.md |   4 +-
 ...-causing-sync-problems-of-payment-rules.md |   4 +-
 ...documents-even-with-the-success-message.md |   4 +-
 ...ng-credits-even-if-the-card-is-inactive.md |   4 +-
 ...-the-order-has-the-same-shipping-method.md |   4 +-
 ...n-address-editing-on-romania-my-account.md |   4 +-
 ...-list-after-using-the-api-to-create-put.md |   4 +-
 ...lace-is-always-done-with-saleschannel-1.md |   4 +-
 ...suer-bank-for-this-bank-is-not-accepted.md |   4 +-
 ...-asynchronously-denying-payment-capture.md |   4 +-
 ...s-not-work-with-save-card-functionality.md |   4 +-
 ...s-not-work-with-save-card-functionality.md |   4 +-
 ...when-using-checkout-in-catalan-language.md |   4 +-
 ...ria-that-have-double-spaces-in-the-name.md |   4 +-
 ...data-containing-more-than-40-characters.md |   4 +-
 ...ages-based-on-sku-specifications-change.md |   4 +-
 ...redit-of-payment-method-customer-credit.md |   4 +-
 ...equest-as-query-string-in-the-crm-login.md |   4 +-
 ...work-for-asynchronous-payment-providers.md |   4 +-
 ...-documents-typically-exceeding-millions.md |   4 +-
 ...en-the-restrange-header-is-less-than-10.md |   4 +-
 ...low-multiple-cancellation-with-giftcard.md |   4 +-
 ...ent-affiliation-for-debit-online-method.md |   4 +-
 ...n-one-extension-payment-affiliation-for.md |  12 +-
 ...eestoque-does-not-support-multilanguage.md |   4 +-
 ...tions-if-the-payload-exceeds-5000-lines.md |   4 +-
 ...-directly-from-the-mysubscriptions-area.md |   4 +-
 ...romissory-doesnt-cancel-the-transaction.md |   4 +-
 docs/known-issues/es/this-is-a-test.md        |   4 +-
 .../es/time-out-at-relatorioindexacaoaspx.md  |   4 +-
 .../es/time-out-import-and-export-admin.md    |   4 +-
 ...gory-keywords-change-with-many-products.md |   4 +-
 ...eout-api-get-accounts-approval-settings.md |   4 +-
 ...ut-generating-internal-application-keys.md |   4 +-
 ...s-preventing-to-check-the-inventory-log.md |   4 +-
 ...terms-presented-in-the-analytics-report.md |   4 +-
 ...tem-with-negative-value-in-inventory-ui.md |   4 +-
 docs/known-issues/es/tracking-error.md        |   4 +-
 ...-api-do-not-generate-reindexing-request.md |   4 +-
 ...-request-para-o-sistema-de-parcelamento.md |   4 +-
 ...ion-error-with-unreachable-code-message.md |   4 +-
 ...us-prior-to-the-state-that-it-should-be.md |   4 +-
 ...ing-risk-due-to-null-documenttype-field.md |   4 +-
 ...anceling-when-one-of-the-card-is-denied.md |  12 +-
 ...n-status-approved-with-payment-canceled.md |   4 +-
 ...o-pspresponsecod-in-settlement-response.md |   4 +-
 ...nsactions-entered-into-wrong-conditions.md |   4 +-
 ...yu-do-not-change-from-cancelling-status.md |   4 +-
 ...g-longer-than-expected-to-update-status.md |   4 +-
 ...enied-by-error-card-not-enrolled-in-3ds.md |   4 +-
 ...count-to-implement-multilanguage-stores.md |   4 +-
 ...ng-saved-in-vbase-and-not-into-rewriter.md |   4 +-
 ...roduct-name-and-description-on-centauro.md |   4 +-
 ...der-resulting-in-status-detailstatenull.md |   4 +-
 ...p-and-item-is-not-in-the-first-position.md |   4 +-
 ...ly-the-available-items-to-calculate-sla.md |   4 +-
 ...eflect-invoice-address-selection-markup.md |   4 +-
 ...does-not-update-best-sla-choice-in-cart.md |   4 +-
 ...en-items-for-pickup-from-another-seller.md |   4 +-
 ...en-selecting-to-add-a-new-address-first.md |   4 +-
 ...-delivery-when-it-has-delivery-division.md |   4 +-
 ...tween-delivery-and-collection-correctly.md |   4 +-
 ...urs-in-the-place-order-internal-process.md |   4 +-
 ...dress-that-had-previously-available-sla.md |   4 +-
 ...-with-subscriptions-but-it-wasnt-in-api.md |   4 +-
 ...-email-template-sender-has-its-own-smtp.md |   4 +-
 ...or-delivery-is-between-items-for-pickup.md |   4 +-
 ...ed-when-using-order-replacement-feature.md |   4 +-
 ...ests-for-each-keyfield-of-an-attachment.md |   4 +-
 ...ers-is-selected-for-delivery-and-pickup.md |   4 +-
 ...ckages-are-split-for-scheduled-delivery.md |   4 +-
 .../unable-to-access-vtex-payment-account.md  |   4 +-
 ...ons-that-had-payout-split-config-change.md |   4 +-
 ...n-cart-object-in-transaction-is-unknown.md |   4 +-
 ...te-produtos-relacionados-custom-element.md |   4 +-
 ...unable-to-delete-template-on-legacy-cms.md |   4 +-
 ...le-to-download-prices-importing-results.md |   4 +-
 ...rt-more-than-65536-lines-in-cms-builder.md |   4 +-
 ...to-log-in-through-the-google-app-on-ios.md |   4 +-
 .../known-issues/es/unable-to-pause-seller.md |   4 +-
 ...sing-protocol-encryption-protocol-ssl13.md |   4 +-
 ...scenario-while-using-whitelabel-sellers.md |   4 +-
 ...e-products-pdp-are-still-being-returned.md |   4 +-
 ...ritization-by-diacritics-for-portuguese.md |   4 +-
 ...-requests-and-components-being-reloaded.md |   4 +-
 ...-props-infinitetrue-and-navigationstep1.md |   4 +-
 ...em-is-available-through-the-same-option.md |   4 +-
 ...ning-when-registeringupdating-a-product.md |   4 +-
 ...-error-when-changing-edition-of-account.md |   4 +-
 ...mber-to-fetch-a-transaction-in-admin-ui.md |   4 +-
 ...exportacaoimportacaoespecificacaov2aspx.md |   4 +-
 ...t-search-api-return-wrong-or-empty-data.md |   4 +-
 ...default-value-after-changing-it-via-api.md |   4 +-
 ...s-does-not-trigger-automatic-indexation.md |   4 +-
 .../update-users-name-in-the-login-section.md |   4 +-
 ...ue-to-lacking-property-on-get-resp-json.md |   4 +-
 ...-working-on-adminportalsitesdefaultcode.md |   4 +-
 ...-the-update-seller-request-not-updating.md |   4 +-
 ...cial-characters-non-ascii-return-errors.md |   4 +-
 .../es/urls-redirecionando-para-buscavazia.md |   4 +-
 ...res-even-without-the-correct-permission.md |   4 +-
 ...rder-and-does-not-allow-ui-reprocessing.md |   4 +-
 ...estricted-is-not-able-to-list-the-users.md |   4 +-
 ...age-on-first-registration-in-my-account.md |   4 +-
 ...i-on-the-admin-due-to-a-forbidden-error.md |   4 +-
 ...ant-access-gift-card-admin-looping-page.md |   4 +-
 ...ey-try-to-log-in-by-saml-authentication.md |   4 +-
 ...n-not-see-the-orders-on-my-account-page.md |   4 +-
 ...-when-adding-the-first-item-to-the-cart.md |   4 +-
 ...-list-affects-the-results-in-the-report.md |   4 +-
 ...nstep-to-1-causes-last-dots-to-be-empty.md |   4 +-
 ...c-not-being-kept-on-the-url-after-login.md |   4 +-
 ...cartmutation-failing-when-large-payload.md |   4 +-
 ...fields-at-checkout-not-working-properly.md |  12 +-
 .../vbase-responds-404-to-vtexpagesgraphql.md |   4 +-
 ...-mycards-are-not-automatically-canceled.md |   4 +-
 ...ote-not-found-on-vtex-id-on-the-profile.md |   4 +-
 ...ion-not-sending-the-description-in-card.md |   4 +-
 ...t-being-sent-from-seller-to-marketplace.md |   4 +-
 ...ent-doesnt-work-properly-on-ios-devices.md |   4 +-
 ...eived-on-the-datalayer-every-other-time.md |   4 +-
 ...-we-change-product-quantity-in-minicart.md |   4 +-
 ...-product-feature-does-not-work-properly.md |   4 +-
 ...when-multiple-search-terms-are-provided.md |   4 +-
 ...-does-not-work-before-acessing-checkout.md |   4 +-
 ...placeholder-idacessorios-is-not-working.md |   4 +-
 ...-pageurl-parameter-using-http-not-https.md |   4 +-
 ...-pickup-point-deleted-instore-warehouse.md |   4 +-
 ...clientid-field-of-the-giftcard-on-admin.md |   4 +-
 ...shows-success-even-when-it-isnt-working.md |   4 +-
 ...-not-fully-integrated-with-headless-cms.md |   4 +-
 ...ctname-without-the-sku-name-information.md |   4 +-
 ...yed-in-the-order-and-email-notification.md |   4 +-
 ...ent-the-transaction-cannot-be-completed.md |   4 +-
 ...er-its-not-possible-to-use-a-custom-one.md |   4 +-
 ...n-the-initial-message-is-not-translated.md |   4 +-
 ...-cart-ui-makes-incorrect-request-to-api.md |   4 +-
 ...ly-our-gateway-performs-a-double-refund.md |   4 +-
 ...ryslainminutes-calculation-returns-null.md |   4 +-
 ...ected-to-the-braspag-affiliation-screen.md |   4 +-
 ...-filters-options-doesnt-colapse-anymore.md |   4 +-
 ...utton-calltoaction-name-in-profile-step.md |   4 +-
 ...api-when-the-payload-request-is-invalid.md |   4 +-
 ...rror-when-using-a-nonexisting-gift-card.md |   4 +-
 ...eater-than-1-in-intelligent-search-apis.md |   4 +-
 ...nt-fields-under-the-same-original-value.md |   4 +-
 ...hain-order-for-a-multilevel-marketplace.md |   4 +-
 ...saction-split-with-partial-cancellation.md |   4 +-
 .../xml-file-does-not-get-price-from-swl.md   |   4 +-
 ...mation-defined-on-category-global-level.md |   4 +-
 ...xml-installment-currency-does-not-apply.md |   4 +-
 ...not-load-contents-for-unavailable-items.md |   4 +-
 ...xml-url-on-the-admin-showing-wrong-link.md |   4 +-
 docs/known-issues/es/xmlaspx-timeout.md       |   4 +-
 ...-product-name-flag-not-working-properly.md |   4 +-
 .../es/xmls-returning-500-error.md            |   4 +-
 ...checkout-and-causing-stuck-transactions.md |   4 +-
 ...3-error-for-all-urls-containing-develop.md |   4 +-
 ...the-activate-if-possible-flag-unchecked.md |   4 +-
 ...when-having-it-as-a-single-payment-rule.md |   4 +-
 ...-be-returned-blank-in-the-catalog-admin.md |   4 +-
 ...information-for-sessions-and-conversion.md |   4 +-
 ...name-dont-have-metrics-on-search-report.md |   4 +-
 ...skuvincularvalorservicoaspx-not-working.md |   4 +-
 ...nvoice-address-returns-null-api-results.md |   4 +-
 ...cation-mode-even-for-complete-addresses.md |   4 +-
 ...he-shopper-opts-to-insert-a-new-address.md |   4 +-
 ...-size-for-multiples-cities-separated-by.md |   4 +-
 ...-removing-essential-address-information.md |   4 +-
 ...n-buyer-has-can-add-shipping-permission.md |   4 +-
 ...n-impersonated-using-vtex-telemarketing.md |   4 +-
 ...auses-invalid-address-for-an-item-error.md |   4 +-
 ...-assembly-options-components-attachment.md |   4 +-
 ...for-integration-with-wl-seller-facebook.md |   4 +-
 .../pt/adjust-processing-tab-export.md        |   4 +-
 ...rder-has-more-than-one-product-centauro.md |   4 +-
 .../pt/admin-collection-brand-list-timeout.md |   4 +-
 ...rch-doesnt-recognize-profile-menu-items.md |   4 +-
 ...nsion-as-jpg-even-when-the-image-is-png.md |   4 +-
 ...-engine-redirects-them-to-the-wrong-url.md |   4 +-
 .../pt/admin-review-global-search.md          |   4 +-
 docs/known-issues/pt/admin-timeout.md         |   4 +-
 ...ut-country-disrupting-orderform-changes.md |   4 +-
 ...egistered-globally-insted-of-by-binding.md |   4 +-
 ...-generates-payment-authorization-denial.md |   4 +-
 ...-some-operations-and-thus-causing-error.md |   4 +-
 ...ethodtype-for-amex-when-using-apple-pay.md |   4 +-
 ...ring-pspreference-to-cancel-transaction.md |   4 +-
 ...ed-delivery-selection-appears-only-once.md |   4 +-
 ...-return-values-without-relating-an-item.md |   4 +-
 ...-showing-in-vtexcmcproductimage-zoomon-.md |  12 +-
 .../pt/amazon-category-implementation.md      |   4 +-
 ...e-sending-product-to-amazon-marketplace.md |   4 +-
 ...sku-is-not-being-logged-into-the-bridge.md |   4 +-
 .../pt/amazon-global-category-not-working.md  |   4 +-
 ...n-integration-attribute-number-of-itens.md |   4 +-
 ...ration-is-not-cancelling-orders-in-vtex.md |   4 +-
 ...integration-stock-reservations-for-kits.md |   4 +-
 ...nce-not-set-to-an-instance-of-an-object.md |   4 +-
 .../pt/amazon-order-integration-error.md      |   4 +-
 .../amazoncasacaso-erros-de-rastreamento.md   |   4 +-
 ...curred-when-adding-tracking-information.md |   4 +-
 .../pt/analytics-duplicated-events.md         |   4 +-
 ...ing-data-in-sales-performance-dashboard.md |   4 +-
 ...expected-behavior-with-the-enter-button.md |   4 +-
 ...mate-returns-wrong-info-when-sc-is-null.md |   4 +-
 ...ts-does-not-return-additionalinfo-field.md |   4 +-
 ...o-bought-not-always-working-as-expected.md |   4 +-
 ...-are-not-erased-when-you-delete-the-app.md |   4 +-
 ...most-expensive-items-ui-not-saving-data.md |   4 +-
 ...oved-skus-spreadsheet-not-showing-price.md |   4 +-
 ...when-selected-on-pdp-and-adding-to-cart.md |   4 +-
 ...t-allow-null-domainvalues-and-it-should.md |   4 +-
 ...ation-on-field-domainvalues-not-working.md |   4 +-
 ...g-an-item-from-a-seller-with-attachment.md |   4 +-
 ...are-not-updated-when-its-added-to-items.md |   4 +-
 ...e-not-being-updated-in-meli-integration.md |   4 +-
 ...pricing-logs-showing-unknow-information.md |   4 +-
 ...payments-when-the-first-one-is-canceled.md |   4 +-
 .../pt/auto-approve-api-accepts-any-values.md |   4 +-
 ...ng-suggestion-products-shown-with-delay.md |   4 +-
 ...arch-suggestion-is-not-working-properly.md |  12 +-
 ...tocomplete-not-answering-to-cold-starts.md |   4 +-
 ...ys-updating-when-changed-multiple-times.md |   4 +-
 ...ocomplete-search-not-working-with-space.md |   4 +-
 ...i-removes-the-dot-from-the-product-name.md |   4 +-
 ...ic-payment-settlement-incorrectly-setup.md |   4 +-
 ...not-occurring-due-to-special-characters.md |   4 +-
 ...mulation-for-no-stock-or-price-products.md |   4 +-
 ...-missing-data-for-newly-created-address.md |   4 +-
 ...r-of-routes-created-to-deliver-the-item.md |   4 +-
 ...d-data-is-not-removed-after-logging-out.md |   4 +-
 ...story-doesnt-work-in-the-website-domain.md |   4 +-
 ...ng-geolocation-when-registering-address.md |   4 +-
 ...-detail-ui-only-shows-100-first-sellers.md |   4 +-
 ...e-doesnt-register-information-in-orders.md |   4 +-
 ...count-at-checkout-in-the-website-domain.md |   4 +-
 ...e-geocoordinates-to-calculate-region-id.md |   4 +-
 ...rect-order-fob-integrating-with-carrier.md |   4 +-
 .../pt/b2w-freight-value-in-oms-vtex.md       |   4 +-
 ...der-with-parameter-count-mismatch-error.md |   4 +-
 ...w-tracking-status-not-updated-on-skyhub.md |   4 +-
 ...tton-is-not-rendered-in-my-organization.md |   4 +-
 ...lbacksuccess-instead-of-placeorder-page.md |   4 +-
 ...n-searching-terms-with-directly-via-url.md |   4 +-
 ...arching-terms-with-through-autocomplete.md |   4 +-
 ...-with-a-huge-quantity-of-reserved-items.md |   4 +-
 ...ific-scenarios-with-merchandising-rules.md |   4 +-
 ...ity-of-the-search-level-in-search-pages.md |   4 +-
 ...duling-is-deactivated-after-expiry-date.md |  12 +-
 ...en-the-promotion-is-a-buy-together-type.md |   4 +-
 ...does-not-match-an-associated-card-brand.md |   4 +-
 ...or-not-working-at-site-editor-home-page.md |   4 +-
 .../pt/bmail-problems-with-filaumbro.md       |   4 +-
 ...form-application-does-not-work-properly.md |   4 +-
 ...rties-not-being-validated-on-legacy-cms.md |   4 +-
 ...port-selecting-fewer-skus-than-expected.md |   4 +-
 ...s-are-not-searchable-on-the-brand-admin.md |   4 +-
 ...nceling-due-to-an-error-with-code-bp901.md |   4 +-
 ...-being-read-by-crawlers-due-ssr-timeout.md |   4 +-
 ...hanges-to-the-intelligent-search-module.md |   4 +-
 ...cep-not-working-in-create-giftlist-form.md |   4 +-
 ...-mycards-page-not-translated-to-spanish.md |   4 +-
 ...-points-not-being-presented-in-the-list.md |   4 +-
 ...k-on-the-first-try-in-fullcleanup-admin.md |   4 +-
 ...oducts-not-to-load-on-the-front-timeout.md |   4 +-
 ...e-restriction-impact-in-gift-promotions.md |   4 +-
 ...figuration-in-organizationscost-centers.md |   4 +-
 docs/known-issues/pt/cabals-regex-update.md   |   4 +-
 ...reating-or-deleting-merchandising-rules.md |   4 +-
 ...rice-table-export-not-bringing-all-skus.md |   4 +-
 .../calculation-issue-in-comissionamount.md   |   4 +-
 ...lendar-in-english-for-stores-in-spanish.md |   4 +-
 ...s-to-cart-from-store-framework-frontend.md |   4 +-
 ...to-retry-payment-which-may-also-deny-it.md |   4 +-
 ...nnector-owner-account-has-been-disabled.md |   4 +-
 ...-a-customers-credit-card-via-my-account.md |  12 +-
 ...audience-doesnt-save-coupon-information.md |   4 +-
 ...rent-from-to-equal-to-with-a-collection.md |   4 +-
 ...ormaspx-save-button-requires-two-clicks.md |   4 +-
 ...re-not-applied-after-3rd-category-level.md |   4 +-
 ...-a-seller-under-the-multilevel-behavior.md |   4 +-
 ...nt-edit-the-name-of-the-styles-template.md |   4 +-
 ...rd-brands-incorrectly-processed-as-visa.md |   4 +-
 ...card-facebook-doesnt-save-some-settings.md |   4 +-
 ...holderdocument-is-not-sent-to-antifraud.md |   4 +-
 ...order-doesnt-bring-the-assembly-options.md |   4 +-
 ...-old-order-doesnt-bring-the-attachments.md |   4 +-
 ...ing-placed-as-expected-in-the-orderform.md |   4 +-
 ...sing-sent-by-checkout-in-additionaldata.md |   4 +-
 ...re-kept-in-orders-with-total-value-zero.md |   4 +-
 ...t-message-while-screen-is-still-loading.md |   4 +-
 ...if-store-cant-ship-to-all-the-countries.md |   4 +-
 ...ent-do-not-receive-promotions-correctly.md |   4 +-
 ...-not-consider-items-removed-from-orders.md |   4 +-
 ...le-gives-access-to-the-gift-card-module.md |   4 +-
 ...i-create-sku-file-only-work-with-an-url.md |   4 +-
 ...properly-to-space-at-the-end-of-strings.md |   4 +-
 ...on-if-sending-request-with-wrong-values.md |   4 +-
 ...ters-skus-with-duplicate-specifications.md |   4 +-
 ...export-cannot-handle-t-and-s-characters.md |   4 +-
 ...how-sales-channels-when-none-are-tagged.md |   4 +-
 ...xport-for-attachment-cuts-50-characters.md |   4 +-
 ...ilter-for-seller-1-brings-empty-results.md |   4 +-
 .../pt/catalog-filters-timeout.md             |   4 +-
 ...ger-a-new-intelligent-search-indexation.md |   4 +-
 ...ql-categoryinputtranslation-not-working.md |   4 +-
 ...enerating-invalid-translation-documents.md |   4 +-
 ...-report-total-section-calculation-error.md |   4 +-
 ...ion-xml-fiscal-code-field-not-rendering.md |   4 +-
 ...mapping-ui-taking-too-much-time-to-load.md |   4 +-
 ...ame-html-select-breaking-for-chrome-108.md |   4 +-
 ...alog-search-api-limited-to-2500-results.md |   4 +-
 ...rn-information-for-products-unavailable.md |   4 +-
 ...f-the-selected-category-is-a-department.md |   4 +-
 ...slations-not-reflecting-on-the-frontend.md |   4 +-
 .../pt/catalogv2-user-roles-not-applying.md   |   4 +-
 ...update-with-values-from-review-skus-tab.md |   4 +-
 .../categoriesaspx-specification-timeout.md   |   4 +-
 ...on-the-seller-config-generates-time-out.md |   4 +-
 ...r-when-translating-with-catalog-graphql.md |   4 +-
 ...s-do-not-open-in-admin-on-first-attempt.md |   4 +-
 ...gory-substitute-words-not-being-indexed.md |   4 +-
 ...ds-being-overwritten-on-catalog-graphql.md |   4 +-
 ...entage-on-seller-api-allowing-any-value.md |   4 +-
 ...-with-pedido-sem-o-campo-packages-error.md |   4 +-
 ...-to-myaccount-instead-of-the-order-page.md |   4 +-
 ...-calculation-of-promotions-take-3-pay-2.md |   4 +-
 ...er-using-api-without-email-orderchanged.md |   4 +-
 ...umber-of-characters-in-the-braspag-slip.md |   4 +-
 ...-are-saved-but-dont-reflect-on-the-page.md |   4 +-
 ...tyles-admin-page-are-not-saved-properly.md |   4 +-
 ...ccessories-is-not-triggering-indexation.md |   4 +-
 ...-could-make-the-page-not-work-correctly.md |   4 +-
 ...hentication-doesnt-work-on-pages-module.md |   4 +-
 ...without-shipping-address-on-the-ui-only.md |   4 +-
 ...-add-2-different-addresses-for-delivery.md |   4 +-
 ...pty-shippingdata-when-using-geolocation.md |   4 +-
 ...es-when-two-or-more-sellers-can-fulfill.md |   4 +-
 ...-unavailable-after-pickuppoint-selected.md |   4 +-
 ...as-free-shipping-and-scheduled-delivery.md |   4 +-
 ...at-first-instant-for-specific-condition.md |   4 +-
 ...does-not-show-option-to-change-zip-code.md |   4 +-
 ...support-encoding-assembly-options-names.md |   4 +-
 ...-pageview-events-multiplied-per-tracker.md |   4 +-
 ...pickup-point-option-was-defined-via-api.md |   4 +-
 ...e-identified-and-the-logged-in-customer.md |   4 +-
 ...tly-sending-item-details-to-transaction.md |   4 +-
 ...hanging-email-but-flow-is-not-supported.md |   4 +-
 ...ut-orderplaced-boleto-bank-invoice-moip.md |   4 +-
 ...writes-receiver-name-with-customer-name.md |   4 +-
 ...ncorrect-information-in-the-paymentdata.md |  12 +-
 ...f-apple-pay-is-the-first-payment-method.md |  12 +-
 ...ct-seller-when-merging-cart-information.md |   4 +-
 ...tax-field-for-shipping-percentage-taxes.md |   4 +-
 ...e-same-sku-receives-a-logistics-timeout.md |   4 +-
 ...ress-for-shoppers-with-complete-profile.md |   4 +-
 ...r-items-with-no-common-shipping-methods.md |   4 +-
 ...orrect-sla-values-from-logistics-system.md |  12 +-
 ...hen-name-is-different-from-profile-data.md |   4 +-
 ...-hyphen-in-the-postal-code-to-orderform.md |   4 +-
 ...-the-user-switches-the-delivery-options.md |   4 +-
 ...le-all-toggle-after-refreshing-the-page.md |   4 +-
 ...-there-is-only-pickup-address-available.md |   4 +-
 ...oesnt-handle-multiple-filters-correctly.md |   4 +-
 ...licks-on-the-numericstepper-not-working.md |   4 +-
 ...ly-sometimes-in-global-checkout-setting.md |   4 +-
 ...t-add-client-profile-is-performed-twice.md |   4 +-
 ...with-the-same-names-as-the-default-ones.md |   4 +-
 .../pt/cms-legacy-collections-timeout.md      |   4 +-
 .../cms-loyalty-value-settings-not-working.md |   4 +-
 ...oving-value-from-the-unit-of-mass-field.md |   4 +-
 ...s-settings-role-not-working-as-expected.md |   4 +-
 ...r-doesnt-work-in-development-workspaces.md |   4 +-
 ...saved-card-with-wrong-payment-system-id.md |   4 +-
 ...courier-retries-not-working-as-expected.md |   4 +-
 ...ble-menu-issues-rendering-all-the-items.md |   4 +-
 ...n-functionality-doesnt-work-on-giftcard.md |  12 +-
 ...ection-ordering-not-working-as-expected.md |   4 +-
 ...accessed-through-mapproductclusternames.md |   4 +-
 ...ot-allow-more-than-1000-skus-per-upload.md |   4 +-
 ...ustom-search-results-pages-in-b2b-suite.md |   4 +-
 .../collections-dont-open-on-subaccounts.md   |   4 +-
 ...-only-shows-1st-sku-of-inactive-product.md |   4 +-
 ...-equal-to-on-the-campaign-audience-form.md |   4 +-
 ...h-special-characters-cannot-be-exported.md |   4 +-
 ...ation-details-shows-only-20-collections.md |   4 +-
 ...llections-schedule-end-date-not-working.md |   4 +-
 ...ections-schedule-start-date-not-working.md |   4 +-
 ...ng-as-expected-on-progressive-discounts.md |   4 +-
 ...ch-for-products-with-special-characters.md |   4 +-
 ...texcrm-field-is-not-showing-its-content.md |   4 +-
 ...eation-due-to-failure-in-gatewaycallbak.md |   4 +-
 ...n-implemented-in-productsummary-for-ios.md |   4 +-
 ...nconsistency-in-deliveryshipping-prices.md |   4 +-
 ...components-in-a-kit-with-the-same-price.md |   4 +-
 ...o-pode-ser-alterada-por-contas-franquia.md |   4 +-
 .../confirmed-order-email-not-being-sent.md   |   4 +-
 ...the-same-name-at-the-intelligent-search.md |   4 +-
 ...nel-in-searches-portal-and-search-again.md |   4 +-
 ...violates-the-following-content-security.md |   4 +-
 .../pt/cookie-broken-the-apisessions.md       |   4 +-
 ...-only-25-options-in-b2b-admin-customers.md |   4 +-
 ...g-logic-diverges-on-computed-prices-api.md |   4 +-
 .../country-field-as-null-in-invoicedata.md   |   4 +-
 ...ys-restricted-to-the-delivery-countries.md |   4 +-
 ...sage-not-restored-for-incomplete-orders.md |   4 +-
 ...oupons-created-as-archived-temporarrily.md |   4 +-
 ...oesnt-send-nulls-as-release-date-values.md |   4 +-
 ...ional-information-is-returning-an-error.md |   4 +-
 ...-does-not-update-the-items-stockbalance.md |   4 +-
 ...-of-redirects-breaks-the-redirects-page.md |   4 +-
 ...-of-the-csv-through-the-cli-doesnt-work.md |   4 +-
 ...not-returned-on-the-explained-search-ui.md |   4 +-
 ...-allow-values-longer-than-10-characters.md |   4 +-
 ...y-symbol-does-not-follow-admin-language.md |   4 +-
 .../custom-attribute-mapper-mercado-livre.md  |   4 +-
 ...cms-not-working-with-more-than-one-html.md |   4 +-
 ...mage-is-not-displayed-on-mobile-version.md |   4 +-
 ...edit-doesnt-show-installments-correctly.md |   4 +-
 ...tatus-at-mycredits-page-are-not-correct.md |   4 +-
 ...ue-updating-according-to-the-pagination.md |   4 +-
 ...credits-invoice-list-cannot-be-exported.md |   4 +-
 ...s-some-order-with-profileerroronloading.md |   4 +-
 ...rom-profile-system-without-clear-reason.md |   4 +-
 ...tion-is-not-saved-in-the-profile-system.md |   4 +-
 ...-products-catalog-page-after-logging-in.md |  12 +-
 ...ipping-promotion-default-saleschannel-1.md |   4 +-
 ...v-without-validation-of-characters-type.md |   4 +-
 ...-but-are-still-paymentpending-at-dafiti.md |   4 +-
 .../pt/dafiti-quality-dafiti-images.md        |   4 +-
 ...n-search-report-showing-duplicated-date.md |   4 +-
 ...ed-payment-system-rendering-at-checkout.md |   4 +-
 ...eadlocked-error-when-using-catalog-apis.md |   4 +-
 ...-an-error-in-the-transactionstate-field.md |   4 +-
 ...dtotalamount-and-csittotalamount-fields.md |   4 +-
 ...sed-after-some-retries-to-authorization.md |   4 +-
 ...ng-when-creating-products-through-admin.md |   4 +-
 ...ping-policy-locked-in-processing-status.md |   4 +-
 ...register-cancelreason-in-the-order-json.md |   4 +-
 ...utomatic-capture-even-without-antifraud.md |   4 +-
 ...-checkout-if-not-deactivated-previously.md |   4 +-
 ...ew-admin-is-not-reindexing-the-products.md |   4 +-
 ...s-allowing-schedule-carrier-at-checkout.md |   4 +-
 ...e-is-space-in-the-id-of-shipping-policy.md |   4 +-
 ...-due-to-an-error-in-filling-the-invoice.md |   4 +-
 ...w-when-there-is-only-scheduled-delivery.md |   4 +-
 ...ector-does-not-appear-in-some-scenarios.md |   4 +-
 ...getting-empty-when-item-is-a-gift-added.md |   4 +-
 ...with-lean-shipping-offering-invalid-sla.md |   4 +-
 .../pt/deliverycontracttype-problem-b2w.md    |   4 +-
 ...ing-on-seller-management-commissions-ui.md |   4 +-
 .../diacritics-are-removed-on-catalogapi.md   |   4 +-
 ...rices-between-pdp-plp-and-checkout-cart.md |   4 +-
 ...-specification-value-on-apis-and-portal.md |   4 +-
 ...f-sellers-for-the-same-seller-in-a-cart.md |   4 +-
 ...ds-being-unselected-during-sku-creation.md |   4 +-
 ...perly-when-prop-animated-is-set-as-true.md |   4 +-
 ...oupon-usage-count-on-oms-and-coupons-ui.md |   4 +-
 ...and-the-subtotal-of-items-or-totalizers.md |   4 +-
 .../pt/divergence-delivery-time-netshoes.md   |   4 +-
 ...lculations-involving-decimals-in-weight.md |   4 +-
 ...-settings-on-new-accounts-or-workspaces.md |   4 +-
 .../known-issues/pt/divergence-rule-dafiti.md |   4 +-
 .../pt/divergencia-shipping-estimate-b2w.md   |   4 +-
 ...ues-per-item-between-chk-and-ffm-orders.md |   4 +-
 ...ile-using-price-override-and-promotions.md |   4 +-
 ...transaction-list-and-on-the-transaction.md |   4 +-
 ...llment-configuration-and-splitted-items.md |   4 +-
 ...domly-getting-last-digit-deleted-on-ios.md |   4 +-
 .../pt/drag-and-drop-issue-on-site-editor.md  |   4 +-
 ...sspecification-values-on-the-same-level.md |   4 +-
 ...n-modal-to-switch-between-organizations.md |   4 +-
 ...-ignored-when-approved-on-received-skus.md |   4 +-
 ...th-automatic-capture-on-authorizedotnet.md |   4 +-
 ...derest-are-not-respecting-early-capture.md |   4 +-
 ...filling-for-new-buyers-after-logging-in.md |   4 +-
 ...autofilling-for-new-users-on-checkoutui.md |   4 +-
 ...ate-using-the-b2b-organizations-feature.md |   4 +-
 ...ters-leads-to-unexpected-product-search.md |   4 +-
 ...cancelation-when-the-status-code-is-359.md |   4 +-
 ...re-specific-global-category-persistente.md |   4 +-
 .../pt/erro-sqlerrm-no-tracking-brinox-b2w.md |   4 +-
 ...e-rejected-or-reviewed-by-offer-quality.md |   4 +-
 ...ror-cancelling-customer-credit-invoices.md |   4 +-
 ...a-promotion-excluding-more-than-1-brand.md |   4 +-
 .../error-closing-customer-credit-account.md  |   4 +-
 ...xporting-entity-with-too-many-documents.md |   4 +-
 ...ror-exporting-large-amount-of-giftcards.md |   4 +-
 .../error-exporting-prices-with-metadata.md   |   4 +-
 ...-cannot-have-more-than-one-sla-selected.md |   4 +-
 .../pt/error-in-checkout-error-message.md     |   4 +-
 .../pt/error-in-custom-payments-creation.md   |   4 +-
 ...ients-is-different-than-operation-value.md |   4 +-
 ...lue-cannot-be-null-parameter-name-value.md |   4 +-
 ...-cancelation-when-the-returncode-is-359.md |   4 +-
 ...ntity-field-of-the-same-sku-in-the-cart.md |   4 +-
 ...ui-after-requesting-the-invoice-via-app.md |   4 +-
 ...rating-sku-field-may-not-be-null-magalu.md |   4 +-
 ...trying-to-access-catalog-pages-on-admin.md |   4 +-
 ...-sku-is-binded-on-vtexvtex-integrations.md |   4 +-
 ...-search-using-the-all-field-in-vtex-crm.md |   4 +-
 .../pt/error-on-duplicate-payment-method.md   |   4 +-
 .../error-saving-netshoes-integration-card.md |   4 +-
 ...gain-when-adding-images-via-site-editor.md |   4 +-
 .../pt/error-sww-on-product-pdp.md            |   4 +-
 ...al-connector-for-pending-payment-status.md |   4 +-
 ...-viewing-shippingestimatedate-in-new-ui.md |   4 +-
 ...ng-an-index-if-the-fields-are-identical.md |   4 +-
 ...delivery-type-when-seller-has-recursion.md |   4 +-
 ...ncluding-many-filters-in-the-order-list.md |   4 +-
 .../error-when-install-customer-credit-app.md |   4 +-
 ...-publishing-dynamic-storage-data-entity.md |   4 +-
 ...a-entity-list-more-than-10000-documents.md |   4 +-
 ...en-running-vtex-link-for-the-first-time.md |   4 +-
 ...-transaction-with-2-cards-mercadopagov1.md |   4 +-
 .../pt/error-when-trying-to-open-my-cards.md  |   4 +-
 ...r-when-trying-to-publish-or-link-an-app.md |   4 +-
 .../pt/eternal-loading-in-checkout-ui-v5.md   |   4 +-
 docs/known-issues/pt/event-inconsistency.md   |   4 +-
 ...be-returned-once-the-order-has-a-change.md |   4 +-
 ...de-products-from-collection-not-working.md |   4 +-
 ...ate-of-special-condition-is-not-deleted.md |   4 +-
 ...eupdatable-due-to-price-variation-limit.md |   4 +-
 ...edirects-not-pointing-back-to-old-route.md |   4 +-
 ...e-also-configured-in-intelligent-search.md |   4 +-
 ...xts-between-different-areas-or-products.md |   4 +-
 ...ist-in-column-creation-date-is-at-utc-0.md |   4 +-
 ...sometimes-the-request-can-not-completed.md |   4 +-
 ...xport-redirects-not-working-as-intended.md |   4 +-
 ...-for-spanish-language-operating-systems.md |   4 +-
 ...the-csv-in-the-sales-performance-module.md |   4 +-
 ...ed-by-brand-does-not-bring-all-the-skus.md |   4 +-
 ...his-character-cut-in-the-image-url-rows.md |   4 +-
 ...working-on-received-skus-processing-tab.md |   4 +-
 ...ot-consider-change-margin-for-upselling.md |   4 +-
 ...t-is-not-recording-a-change-in-the-card.md |   4 +-
 ...ew-skus-load-route-behavior-on-facebook.md |   4 +-
 ...pdate-the-price-in-the-facebook-catalog.md |   4 +-
 ...rumbs-page-title-and-additional-filters.md |   4 +-
 ...heckout-ui-transaction-without-payments.md |   4 +-
 ...ancellation-ppp-when-cancellationidnull.md |   4 +-
 ...s-the-go-to-payment-button-to-disappear.md |   4 +-
 ...ststore-cart-merges-assembly-line-items.md |   4 +-
 ...ng-not-removing-facets-set-to-ne-hidden.md |   4 +-
 ...pi-considering-fuzzy-as-auto-as-default.md |   4 +-
 ...return-seo-information-on-graphql-query.md |   4 +-
 ...rking-correctly-in-firefox-private-mode.md |   4 +-
 ...e-skipping-events-in-fromorders-filters.md |   4 +-
 ...repeated-values-between-the-to-and-from.md |   4 +-
 ...page-status-and-crashing-the-pagination.md |   4 +-
 ...n-trade-policy-not-reflecting-on-pdpplp.md |   4 +-
 ...ting-on-seller-management-ui-after-save.md |   4 +-
 .../pt/field-reference-always-set-as-null.md  |   4 +-
 ...any-change-in-order-management-settings.md |   4 +-
 ...not-update-all-the-files-only-the-first.md |   4 +-
 ...-performance-is-not-accepting-uppercase.md |   4 +-
 ...omotion-with-space-blank-is-not-working.md |   4 +-
 ...names-while-applying-additional-filters.md |   4 +-
 ...n-can-show-the-wrong-ammount-of-results.md |   4 +-
 ...t-considering-regionalized-availability.md |   4 +-
 ...den-from-intelligent-search-admin-pages.md |   4 +-
 ...-hide-scenarios-internals-and-usability.md |   4 +-
 ...to-old-component-version-on-site-editor.md |   4 +-
 ...ll-the-profileshipping-data-at-checkout.md |   4 +-
 ...orporatedocument-if-starts-with-letters.md |   4 +-
 ...e-is-not-considered-on-ui-last-searches.md |   4 +-
 .../pt/first-subscription-cycle-is-skipped.md |   4 +-
 ...rade-policy-1-when-saving-bundle-prices.md |   4 +-
 ...shipping-option-not-working-as-expected.md |   4 +-
 ...ace-integrate-an-order-erro-code-fmt010.md |   4 +-
 ...t-respecting-the-status-of-the-response.md |   4 +-
 ...ions-that-have-not-1-installment-option.md |   4 +-
 ...it-orders-outside-promotion-restriction.md |   4 +-
 ...ng-time-to-reflect-on-simulation-module.md |   4 +-
 ...-has-seller-groups-on-seller-management.md |   4 +-
 ...egory-tree-on-itemcategory-in-datalayer.md |   4 +-
 ...a-cant-be-informed-for-some-cultureinfo.md |   4 +-
 ...eep-same-sku-order-when-changing-limits.md |   4 +-
 ...t-category-tree-api-with-internal-cache.md |   4 +-
 ...ist-multiple-orders-for-the-same-coupon.md |   4 +-
 ...ed-offers-list-api-not-working-properly.md |   4 +-
 ...-by-refid-returning-null-when-not-found.md |   4 +-
 ...ller-list-responding-with-empty-urllogo.md |   4 +-
 ...sku-by-ean-api-returns-only-active-skus.md |   4 +-
 ...from-component-sku-and-not-from-kit-sku.md |   4 +-
 .../pt/gift-card-creation-error-via-admin.md  |   4 +-
 ...ith-the-date-chosen-when-it-was-created.md |   4 +-
 ...ty-id-in-response-to-create-transaction.md |   4 +-
 ...-extra-backslash-when-calling-providers.md |   4 +-
 ...relationname-when-we-make-a-get-request.md |   4 +-
 ...h-permission-from-accessing-it-properly.md |  12 +-
 ...-a-generic-exception-if-it-has-no-price.md |   4 +-
 .../pt/gift-list-error-incomplete-address.md  |   4 +-
 ...n-acting-alongside-other-gift-promotion.md |   4 +-
 ...g-r-as-the-automatic-currency-on-the-ui.md |   4 +-
 ...g-refund-after-transaction-cancellation.md |   4 +-
 ...add-credit-to-the-gift-card-through-api.md |   4 +-
 ...ction-api-always-returns-empty-response.md |   4 +-
 ...a-na-ui-nao-e-a-mesma-que-reflete-no-bd.md |   4 +-
 ...-in-catalog-outdated-compared-to-google.md |   4 +-
 ...ng-between-delivery-and-pick-up-options.md |   4 +-
 .../google-bot-terms-appearing-in-results.md  |   4 +-
 ...onent-iframe-has-inconsistent-rendering.md |   4 +-
 ...-the-selected-country-in-some-scenarios.md |   4 +-
 ...les-performance-not-working-as-expected.md |   4 +-
 ...matically-updated-on-intelligent-search.md |   4 +-
 ...s-cms-ignores-array-validation-settings.md |   4 +-
 ...incorrectly-on-promotion-form-interface.md |   4 +-
 ...label-generation-does-not-work-properly.md |   4 +-
 ...ng-do-not-work-on-seller-portal-catalog.md |   4 +-
 ...ng-error-message-fail-to-process-record.md |   4 +-
 ...rted-when-the-account-has-too-many-skus.md |   4 +-
 ...ed-authentication-cookie-for-some-calls.md |   4 +-
 ...ignored-after-one-purchase-is-completed.md |   4 +-
 ...idget-not-shown-if-showmodal-is-enabled.md |   4 +-
 ...er-only-works-for-last-level-categories.md |   4 +-
 ...oducts-if-import-is-made-based-on-skuid.md |   4 +-
 ...-with-adyen-due-to-lack-of-pspreference.md |   4 +-
 ...no-longer-allows-a-cancellation-request.md |   4 +-
 ...se-button-may-not-work-on-the-first-try.md |   4 +-
 ...with-customer-credit-for-1x-installment.md |   4 +-
 ...-items-to-invoice-field-in-the-order-ui.md |   4 +-
 ...e-tax-values-in-the-ui-appear-the-total.md |   4 +-
 ...partial-cancellation-with-mercadopagov1.md |   4 +-
 ...paypal-credentials-for-the-same-account.md |   4 +-
 ...duct-still-appearing-on-pdp-or-checkout.md |   4 +-
 ...tions-appearing-with-brazilian-currency.md |   4 +-
 ...in-billingaddress-field-sent-to-gateway.md |   4 +-
 ...ween-unique-clicks-and-productids-on-is.md |   4 +-
 ...method-boleto-bancario-expiration-dates.md |   4 +-
 ...e-deadlines-of-customer-credit-invoices.md |   4 +-
 ...nsistency-on-the-report-admin-page-data.md |   4 +-
 ...-organization-and-b2b-checkout-settings.md |   4 +-
 ...results-with-large-specification-values.md |   4 +-
 ...ku-has-unit-multiplier-different-than-1.md |   4 +-
 ...ormat-on-the-my-cards-billing-addresses.md |   4 +-
 .../pt/incorrect-currency-on-payment-form.md  |   4 +-
 ...in-pickupstoreinfo-after-order-creation.md |   4 +-
 ...display-of-package-quantity-at-checkout.md |   4 +-
 ...he-expiration-date-fields-of-promotions.md |   4 +-
 ...message-error-when-creatingediting-skus.md |   4 +-
 ...-on-order-change-due-to-unit-multiplier.md |   4 +-
 ...hen-unit-multiplier-is-different-from-1.md |   4 +-
 ...iscount-to-all-the-same-items-in-a-cart.md |   4 +-
 ...ients-is-different-than-operation-value.md |   4 +-
 ...-3-payment-methods-one-of-them-being-gc.md |   4 +-
 ...eview-when-items-are-scheduled-delivery.md |   4 +-
 ...rect-shippingestimatedate-for-order-fob.md |   4 +-
 ...-usd-currency-displayed-in-some-locales.md |   4 +-
 ...-value-on-package-due-discount-division.md |   4 +-
 ...e-registered-on-the-fulfillmentendpoint.md |   4 +-
 .../pt/incorrectly-updated-inventory.md       |   4 +-
 ...the-highest-instead-of-the-lowest-price.md |   4 +-
 ...s-do-not-work-on-seller-portal-accounts.md |   4 +-
 ...are-same-skuid-in-different-array-items.md |   4 +-
 .../pt/infocard-mobile-images-wont-apply.md   |   4 +-
 ...s-from-servers-that-require-user-agents.md |   4 +-
 ...ns-not-updating-automatically-on-pdpplp.md |   4 +-
 ...account-specific-installment-promotions.md |   4 +-
 ...t-ui-is-loose-when-scrolling-the-screen.md |   4 +-
 ...ml-registred-in-the-product-information.md |   4 +-
 ...dido-amazon-quantidade-de-item-invalida.md |   4 +-
 ...e-via-image-url-does-not-work-correctly.md |   4 +-
 ...s-not-in-sync-with-store-configurations.md |   4 +-
 ...-2-variations-of-the-same-languageidiom.md |   4 +-
 ...ot-capturing-sales-events-for-faststore.md |   4 +-
 ...-search-not-returning-correct-sku-order.md |   4 +-
 ...t-settings-search-bar-is-case-sensitive.md |   4 +-
 ...-normalizing-gender-in-portuguese-words.md |   4 +-
 ...f-field-values-is-limited-to-9999-items.md |   4 +-
 ...tate-changes-the-address-insertion-mode.md |   4 +-
 ...ng-state-sends-the-wrong-payment-option.md |   4 +-
 .../intermitent-site-editor-content-loss.md   |   4 +-
 .../internalsearcherror-timeouts-on-portal.md |   4 +-
 ...ering-custom-currency-in-formatcurrency.md |   4 +-
 ...codelength-0-securitycodeisnumeric-true.md |   4 +-
 ...ilable-addresses-with-different-country.md |   4 +-
 ...ue-to-warehouse-id-being-case-sensitive.md |   4 +-
 ...tics-handle-zero-on-left-as-another-sku.md |   4 +-
 ...king-properly-on-seller-portal-accounts.md |   4 +-
 ...ory-notifications-to-indexer-are-cached.md |   4 +-
 .../pt/inventory-reserved-items-error.md      |   4 +-
 ...grations-to-notify-external-marketplace.md |   4 +-
 ...egory-names-cause-page-not-found-errors.md |   4 +-
 ...-not-work-as-expected-on-the-search-api.md |   4 +-
 ...d-search-for-searches-with-accent-marks.md |   4 +-
 ...ting-products-that-were-already-updated.md |   4 +-
 ...e-on-translating-titles-for-some-facets.md |   4 +-
 ...operties-beginning-with-the-same-prefix.md |   4 +-
 ...values-in-loyalty-gift-card-at-checkout.md |   4 +-
 ...ss-leading-to-transaction-cancellations.md |   4 +-
 .../pt/issues-with-my-account-links.md        |   4 +-
 ...or-transaction-with-minimumvalue-of-001.md |   4 +-
 ...his-item-without-attachment-in-the-cart.md |   4 +-
 ...e-to-cancel-a-transaction-with-maxipago.md |  12 +-
 ...create-a-path-using-content-type-via-ui.md |   4 +-
 ...ith-end-date-from-the-year-2100-onwards.md |   4 +-
 ...-addresses-from-argentina-in-my-account.md |   4 +-
 ...some-addresses-from-chile-in-my-account.md |   4 +-
 ...on-with-the-boleto-method-using-braspag.md |   4 +-
 ...er-is-in-another-package-after-invoiced.md |   4 +-
 ...shown-in-seller-whitelabel-change-order.md |   4 +-
 ...r-location-is-not-defined-with-no-stock.md |   4 +-
 ...f-add-to-cart-event-in-google-analytics.md |   4 +-
 ...-promotions-with-collections-associated.md |   4 +-
 ...ing-in-subscription-plans-configuration.md |   4 +-
 ...action-but-the-inverse-flow-doesnt-work.md |   4 +-
 ...api-is-not-calculating-component-prices.md |   4 +-
 ...ight-can-be-overritten-by-apiwebservice.md |   4 +-
 ...a-request-when-the-accountid-is-missing.md |   4 +-
 ...lecting-gift-items-that-arent-available.md |   4 +-
 ...pis-allowing-invalid-data-in-the-orders.md |   4 +-
 ...lidation-in-the-billingaddress-zip-code.md |   4 +-
 ...eadsheet-error-on-new-collections-admin.md |   4 +-
 ...t-being-changed-by-specification-import.md |   4 +-
 ...same-slas-but-in-a-different-ordination.md |   4 +-
 ...went-wrong-after-changing-pickup-points.md |   4 +-
 ...ed-delivery-is-the-cheapest-and-fastest.md |   4 +-
 ...activate-after-removing-items-from-cart.md |   4 +-
 ...st-option-in-different-sessionsbrowsers.md |   4 +-
 ...catalog-ui-delete-button-not-functional.md |   4 +-
 ...with-less-than-3-characters-in-the-name.md |   4 +-
 ...-cmss-banner-custom-element-not-working.md |   4 +-
 .../pt/legacy-collection-import-timeout.md    |   4 +-
 ...n-schedule-does-not-respect-sc-timezone.md |   4 +-
 ...ting-products-wrongly-to-the-collection.md |   4 +-
 ...alidation-diverges-from-new-collections.md |   4 +-
 ...ntrols-do-not-consider-unit-multipliers.md |   4 +-
 ...ntroller-texts-are-not-being-translated.md |   4 +-
 ...sales-channel-management-is-not-working.md |   4 +-
 ...eadsheet-only-returning-active-services.md |   4 +-
 ...y-setup-only-works-opening-in-a-new-tab.md |   4 +-
 ...r-when-translating-with-catalog-graphql.md |   4 +-
 ...e-is-being-modified-by-a-unitmultiplier.md |   4 +-
 ...tcher-doesnt-work-in-myvtex-environment.md |   4 +-
 ...with-password-cannot-be-undone-in-admin.md |   4 +-
 ...ess-permission-did-not-work-as-expected.md |   4 +-
 ...es-not-work-when-productprice-as-0-zero.md |   4 +-
 ...ault-currency-instead-of-local-currency.md |   4 +-
 ...er-the-reversal-does-not-actually-occur.md |   4 +-
 ...yment-condition-requires-authentication.md |   4 +-
 ...o-shipping-methods-one-for-the-same-day.md |  12 +-
 ...ated-via-site-editor-from-cms-migration.md |   4 +-
 ...reated-in-oms-and-without-log-in-bridge.md |   4 +-
 ...nce-not-set-to-an-instance-of-an-object.md |   4 +-
 ...specifications-from-another-marketplace.md |   4 +-
 ...just-plaintextdescription-specification.md |   4 +-
 ...ed-fob-order-with-conventional-delivery.md |   4 +-
 ...led-on-marketplace-didnt-cancel-on-vtex.md |   4 +-
 ...marketplace-didnt-update-status-on-vtex.md |   4 +-
 ...nce-not-set-to-an-instance-of-an-object.md |   4 +-
 ...ketplace-are-not-being-approved-on-vtex.md |   4 +-
 ...status-for-delivered-on-the-marketplace.md |   4 +-
 ...ine-luiza-some-skus-do-not-update-price.md |   4 +-
 ...-deve-ser-igual-ou-menor-a-data-de-hoje.md |   4 +-
 ...chantname-in-the-subaccount-environment.md |   4 +-
 .../mandatory-service-working-as-optional.md  |   4 +-
 ...ied-when-creating-a-product-through-api.md |   4 +-
 ...d-to-work-with-2digit-decimal-precision.md |   4 +-
 ...-of-collections-doesnt-work-as-expected.md |   4 +-
 ...using-multiple-coupons-feature-and-utms.md |   4 +-
 ...value-when-campaign-audience-is-matched.md |   4 +-
 ...lues-due-to-certain-purchase-conditions.md |   4 +-
 ...snt-consider-manual-price-for-discounts.md |   4 +-
 ...est-doesnt-consider-some-discount-types.md |   4 +-
 ...ransactions-are-being-processed-as-visa.md |   4 +-
 ...erdata-export-download-link-unavailable.md |   4 +-
 ...ved-skus-api-returning-invalid-sellerid.md |   4 +-
 ...ng-height-width-weight-and-length-to-01.md |   4 +-
 ...uctsku-name-contains-special-characters.md |   4 +-
 ...hipping-discount-not-updating-pricetags.md |   4 +-
 ...rrect-discount-when-using-the-same-item.md |   4 +-
 ...cannot-be-changed-by-franchise-accounts.md |   4 +-
 ...t-passing-a-symbol-or-special-character.md |   4 +-
 ...o-meli-without-being-mapped-from-seller.md |   4 +-
 ...ntegration-with-a-non-expected-behavior.md |   4 +-
 ...tomatic-messages-mercado-livre-messages.md |   4 +-
 ...enu-not-showing-the-orderid-information.md |   4 +-
 ...aused-when-the-marketplace-ad-is-paused.md |   4 +-
 ...ads-not-being-linked-to-bridge-products.md |   4 +-
 .../pt/meli-customdata-paymentfield.md        |   4 +-
 .../pt/meli-error-importing-some-orders.md    |   4 +-
 ...nput-string-was-not-in-a-correct-format.md |   4 +-
 ...-error-while-sending-the-order-tracking.md |   4 +-
 ...quotation-for-multiple-officialstoreids.md |   4 +-
 ...ull-orders-not-creating-invoice-in-vtex.md |   4 +-
 .../known-issues/pt/meli-images-limitation.md |   4 +-
 ...ct-value-when-client-has-coupon-on-meli.md |   4 +-
 ...-errors-from-meli-429-too-many-requests.md |   4 +-
 ...-for-peru-venezuela-equador-and-uruguai.md |   4 +-
 ...meli-integration-missing-billingaddress.md |   4 +-
 ...ntegration-zipcodes-11111-meli-limaperu.md |   4 +-
 .../pt/meli-kit-stock-integration.md          |   4 +-
 ...ding-product-specification-as-variation.md |   4 +-
 .../pt/meli-oms-label-printing.md             |   4 +-
 ...tex-oms-for-multiples-accounts-scenario.md |   4 +-
 ...li-plaintextdescriptionmeli-not-working.md |   4 +-
 ...on-center-not-linking-skus-to-promotion.md |   4 +-
 docs/known-issues/pt/meli-promotion-center.md |   4 +-
 .../pt/meli-promotions-ui-error.md            |   4 +-
 ...bre-is-paused-when-a-sku-is-inactivated.md |   4 +-
 ...hart-not-working-for-sizes-with-letters.md |   4 +-
 ...eli-sizechart-issue-attribute-not-valid.md |   4 +-
 ...t-set-to-an-instance-of-an-object-error.md |   4 +-
 .../pt/meli-update-stockprice-issue.md        |   4 +-
 ...-allowed-unique-attributes-combinations.md |   4 +-
 ...ybox-doesnt-update-shippingmode-for-me2.md |   4 +-
 ...mercado-livre-attribute-size-is-missing.md |   4 +-
 ...bridge-isnt-logging-some-error-messages.md |   4 +-
 ...-not-showing-the-shippingid-information.md |   4 +-
 .../pt/mercado-livre-mapper-attribute-size.md |   4 +-
 ...ve-underreview-validation-in-update-sku.md |   4 +-
 ...bridge-isnt-logging-some-error-messages.md |   4 +-
 ...t-comes-with-phone-user-data-value-as-0.md |   4 +-
 ...working-for-the-facet-productclusterids.md |   4 +-
 ...for-some-clients-in-customer-credit-api.md |   4 +-
 ...re-not-receiving-the-fixed-price-report.md |   4 +-
 ...-value-has-changed-is-shown-incorrectly.md |   4 +-
 ...ing-too-long-to-return-the-informations.md |   4 +-
 ...n-field-cannot-be-deleted-through-admin.md |   4 +-
 ...messages-only-appear-after-a-second-try.md |   4 +-
 ...does-not-show-sku-specs-in-b2b-scenario.md |   4 +-
 .../minicart-error-when-updating-promotion.md |   4 +-
 ...sending-options-for-already-added-items.md |   4 +-
 ...configuration-set-to-a-different-option.md |   4 +-
 ...causes-antifraud-to-cancel-transactions.md |   4 +-
 ...price-facetfilter-at-intelligent-search.md |   4 +-
 ...en-this-type-of-modal-are-configured-ok.md |   4 +-
 ...rent-texts-between-api-and-logistics-ui.md |   4 +-
 ...cated-divergences-setup-shipping-policy.md |   4 +-
 ...pdate-the-department-id-on-the-products.md |   4 +-
 ...pected-behaviors-in-the-categories-tree.md |   4 +-
 .../multiple-sku-promotion-api-not-working.md |   4 +-
 ...eiver-name-field-doesnt-recognize-input.md |   4 +-
 ...shivering-when-trying-to-add-a-new-card.md |   4 +-
 ...-not-working-for-some-legacy-connectors.md |   4 +-
 ...field-filled-in-the-address-information.md |   4 +-
 ...ntlink-invoice-even-if-the-field-is-set.md |   4 +-
 ...ra-resolvelo-tente-novamente-mais-tarde.md |  12 +-
 ...tion-is-associated-with-a-pick-up-point.md |   4 +-
 ...-the-address-line-2-this-appear-as-null.md |   4 +-
 ...-spinner-button-is-not-working-properly.md |   4 +-
 ...hen-accessing-from-an-dependent-account.md |   4 +-
 ...atically-translate-on-the-product-admin.md |   4 +-
 ...s-adding-credit-although-it-returns-500.md |   4 +-
 ...ders-placed-at-magalu-were-as-incomplet.md |   4 +-
 .../negative-amounts-in-split-recipients.md   |   4 +-
 ...ot-handle-non-existent-productid-import.md |   4 +-
 ...eased-filter-is-not-working-for-exports.md |  12 +-
 .../pt/new-collections-page-not-loading.md    |   4 +-
 ...s-the-correct-delivery-window-estimated.md |   4 +-
 ...in-orders-with-partial-or-total-invoice.md |   4 +-
 ...e-customers-id-document-for-example-cpf.md |   4 +-
 ...the-invoiced-value-on-return-items-page.md |   4 +-
 ...e-and-lastdeliveryday-for-high-timecost.md |   4 +-
 ...k-to-the-user-when-something-goes-wrong.md |  12 +-
 ...as-expected-with-subtraction-operations.md |   4 +-
 ...distributed-among-all-items-in-the-cart.md |   4 +-
 ...plit-for-second-item-incorrect-discount.md |   4 +-
 ...proper-detached-sku-on-pdp-in-a-new-tab.md |   4 +-
 ...he-productsku-specification-spreadsheet.md |   4 +-
 ...when-entity-has-more-than-10k-documents.md |   4 +-
 ...on-order-detail-ui-when-exceeding-limit.md |   4 +-
 ...upted-file-when-there-are-no-skus-found.md |   4 +-
 ...esponse-with-more-than-65536-characters.md |   4 +-
 ...r-does-not-correspond-to-correct-number.md |   4 +-
 ...s-not-reliable-in-vtexvtex-integrations.md |   4 +-
 ...t-first-informs-an-address-for-delivery.md |   4 +-
 ...-filter-selected-has-special-characters.md |   4 +-
 ...pears-even-after-filled-until-save-data.md |   4 +-
 ...er-only-captures-the-information-of-the.md |   4 +-
 ...rbypriceasc-could-bring-the-wrong-order.md |   4 +-
 ...bypricedesc-could-bring-the-wrong-order.md |   4 +-
 ...dal-hook-affects-all-modals-on-the-page.md |   4 +-
 ...orrectly-due-to-null-documenttype-field.md |   4 +-
 ...rd-reset-not-logging-out-other-sessions.md |   4 +-
 ...ain-from-b2b-orders-history-doesnt-work.md |   4 +-
 ...arketplace-but-not-integrated-into-vtex.md |   4 +-
 ...ization-lessthan-100-goes-with-the-flow.md |   4 +-
 ...hen-seller-has-a-different-country-code.md |   4 +-
 ...t-be-created-due-to-invalid-credit-card.md |   4 +-
 ...r-card-info-causing-confusing-on-status.md |   4 +-
 ...o-price-divergence-on-fulfillment-layer.md |   4 +-
 .../pt/order-doesnt-update-status-in-oms.md   |   4 +-
 ...some-order-with-big-payload-on-the-list.md |   4 +-
 ...erly-due-double-space-on-promotion-name.md |   4 +-
 ...uotes-in-the-promotion-name-or-sku-name.md |   4 +-
 ...carrier-leaves-label-barcode-incomplete.md |   4 +-
 ...-triggered-the-transaction-total-refund.md |   4 +-
 ...nal-amount-is-refunded-using-new-ui-oms.md |   4 +-
 ...-and-original-order-have-the-same-value.md |   4 +-
 ...nses-field-from-get-payment-details-api.md |   4 +-
 ...ler-status-cancellationrequestdeniedffm.md |   4 +-
 ...o-missing-payment-approved-notification.md |   4 +-
 ...annot-be-invoiced-referencing-the-items.md |   4 +-
 ...-the-items-and-refund-the-total-payment.md |   4 +-
 ...-conectors-like-payment-app-or-redirect.md |   4 +-
 ...eled-but-the-payment-remains-authorized.md |   4 +-
 ...ing-invoice-does-not-update-to-invoiced.md |   4 +-
 .../pt/order-xxx-with-invalid-status.md       |   4 +-
 ...r-the-same-item-under-different-sellers.md |   4 +-
 ...difying-item-attachments-in-the-catalog.md |   4 +-
 ...id-scheduled-delivery-that-cant-be-used.md |   4 +-
 ...changes-in-itemattachment-and-offerings.md |   4 +-
 ...rs-data-even-for-authorized-credentials.md |   4 +-
 ...form-not-updating-after-order-is-placed.md |   4 +-
 ...rd-that-were-removed-via-myaccount-page.md |   4 +-
 ...of-product-fields-and-skus-is-not-saved.md |   4 +-
 ...f-product-fields-and-skus-is-not-saved1.md |   4 +-
 ...ps-from-the-root-category-does-not-work.md |   4 +-
 ...-is-refused-for-the-regular-items-order.md |   4 +-
 ...hat-dont-update-the-invoice-at-netshoes.md |   4 +-
 ...oice-value-in-output-invoice-validation.md |   4 +-
 ...e-fromorders-for-state-payment-approved.md |   4 +-
 ...th-asterisks-in-the-address-and-profile.md |   4 +-
 ...especting-the-cancellation-grace-period.md |   4 +-
 ...aceitems-is-not-opening-on-new-ui-admin.md |   4 +-
 ...splayed-where-it-should-show-the-sku-id.md |   4 +-
 ...nvoiceaddress-created-through-native-ui.md |   4 +-
 ...some-details-in-the-shipping-sla-object.md |   4 +-
 ...hen-uploading-a-new-version-not-working.md |   4 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   4 +-
 ...n-performing-2-product-changes-in-a-row.md |   4 +-
 ...as-billing-address-on-the-checkout-page.md |   4 +-
 ...-is-causing-us-to-misidentify-some-bins.md |   4 +-
 .../outdated-url-on-the-update-binding-ui.md  |   4 +-
 ...e-when-printing-ctrlp-is-used-in-chrome.md |   4 +-
 ...iggered-twice-when-accessing-my-account.md |   4 +-
 ...being-duplicated-in-custom-search-pages.md |   4 +-
 ...h-results-not-working-on-giftlist-pages.md |   4 +-
 ...esnt-reset-when-changing-search-context.md |   4 +-
 ...he-same-sla-affecting-the-purchase-flow.md |   4 +-
 ...-cart-sometimes-returns-null-api-result.md |   4 +-
 ...cessing-transactions-as-prepaid-in-full.md |   4 +-
 ...-with-swl-when-using-identical-typesids.md |   4 +-
 ...t-differ-from-active-payment-conditions.md |   4 +-
 ...ssociated-payment-condition-is-disabled.md |   4 +-
 ...ot-applied-in-the-b2b-checkout-settings.md |   4 +-
 ...-assigned-after-approving-organizations.md |   4 +-
 ...rmation-in-the-payload-to-the-connector.md |   4 +-
 ...rice-comes-exclusively-from-manualprice.md |   4 +-
 ...er-for-multilevel-omnichannel-inventory.md |   4 +-
 ...-respect-the-minimum-installment-amount.md |   4 +-
 ...ecial-characters-are-passed-on-the-link.md |   4 +-
 .../pt/phone-field-order-netshoes.md          |   4 +-
 ...f-switching-between-delivery-and-pickup.md |   4 +-
 ...in-marketplaces-with-multilevel-sellers.md |   4 +-
 ...eocoordinates-without-a-google-maps-key.md |   4 +-
 ...-shows-even-inactive-or-invalid-options.md |   4 +-
 ...earch-will-not-working-with-enterreturn.md |   4 +-
 ...d-in-the-shipping-policy-after-deletion.md |   4 +-
 ...d-after-searching-addresses-in-map-mode.md |   4 +-
 ...ickup-points-not-indexed-in-master-data.md |   4 +-
 ...-same-id-pattern-show-product-available.md |   4 +-
 ...the-same-cart-are-not-working-correctly.md |   4 +-
 ...ndependent-pickups-on-the-purchase-flow.md |   4 +-
 ...in-the-cms-does-not-display-all-content.md |   4 +-
 ...ers-showing-instead-of-the-correct-data.md |   4 +-
 ...etween-items-that-appear-more-than-once.md |   4 +-
 ...address-options-for-recurring-customers.md |   4 +-
 ...-cookies-when-client-logout-at-checkout.md |   4 +-
 ...respect-the-tag-principal-of-skus-image.md |   4 +-
 ...tag-not-updating-when-changing-metadata.md |   4 +-
 ...ging-out-when-using-callcenter-operator.md |   4 +-
 ...ct-with-parameters-in-url-does-not-work.md |   4 +-
 ...ssing-the-url-with-pagination-parameter.md |   4 +-
 ...page-it-is-shown-on-the-admin-interface.md |   4 +-
 ...-pdp-doesnt-reset-when-changing-product.md |   4 +-
 ...ss-and-receiver-name-in-the-checkout-ui.md |   4 +-
 ...th-blank-postal-code-in-the-checkout-ui.md |   4 +-
 ...-notification-in-the-ui-api-and-gateway.md |   4 +-
 ...-loop-in-the-shipping-preview-component.md |   4 +-
 ...he-legacy-cms-collection-is-not-working.md |   4 +-
 ...-incomplete-when-using-category-filters.md |   4 +-
 ...t-is-not-accepted-by-the-import-process.md |   4 +-
 ...-of-spot-price-instead-of-regular-price.md |   4 +-
 ...doesnt-correspond-to-the-search-results.md |   4 +-
 ...-minimum-value-after-selecting-a-filter.md |   4 +-
 ...-twice-and-one-is-from-assembly-options.md |   4 +-
 ...-updates-with-cache-on-end-applications.md |   4 +-
 ...ion-limit-only-works-in-the-main-policy.md |   4 +-
 ...-to-int32-max-value-on-change-price-api.md |   4 +-
 ...ted-to-int32-max-value-on-checkout-apis.md |   4 +-
 .../pt/pricing-api-allows-negative-values.md  |   4 +-
 ...bility-post-prices-route-is-losing-data.md |   4 +-
 ...ducts-keyword-not-considering-stopwords.md |   4 +-
 ...-using-period-of-time-special-condition.md |   4 +-
 ...m-to-pay-with-giftcard-two-cards-option.md |   4 +-
 ...-value-field-when-buying-with-two-cards.md |   4 +-
 ...with-phone-validation-on-mobile-devices.md |   4 +-
 ...ems-to-cart-in-io-that-have-attachments.md |   4 +-
 ...e-inventory-by-admin-page-with-error-ui.md |   4 +-
 ...problems-with-payment-condition-storage.md |   4 +-
 ...ayed-when-using-multiple-sales-channels.md |   4 +-
 ...ed-in-the-pickups-in-cart-display-modal.md |   4 +-
 ...ion-from-datalayer-with-a-wrong-sorting.md |   4 +-
 ...product-comissioning-inconsistent-cache.md |   4 +-
 .../pt/product-created-with-id-0.md           |   4 +-
 ...hlights-doesnt-work-into-a-product-list.md |   4 +-
 ...on-admin-changes-with-more-than-70-skus.md |   4 +-
 ...orting-doesnt-respect-the-catalog-order.md |   4 +-
 ...date-api-allows-n-in-the-textlink-field.md |   4 +-
 ...m-doesnt-work-on-catalogs-redesigned-ui.md |   4 +-
 ...ku-name-when-the-product-has-only-1-sku.md |   4 +-
 .../pt/product-page-sessions-not-working.md   |   4 +-
 ...e-not-considering-default-seller-in-pdp.md |   4 +-
 ...ector-error-for-high-resolution-screens.md |   4 +-
 ...r-not-working-on-seller-portal-accounts.md |   4 +-
 ...at-for-offers-with-more-than-one-seller.md |   4 +-
 ...specification-export-index-out-of-range.md |   4 +-
 ...ection-module-assuming-incorrect-values.md |   4 +-
 ...tion-module-does-not-list-root-category.md |   4 +-
 ...oes-not-trigger-the-products-indexation.md |   4 +-
 ...chresolver-is-incorrect-due-to-rounding.md |   4 +-
 ...-unavailable-even-with-franchised-stock.md |   4 +-
 ...ck-event-considers-the-incorrect-sku-id.md |   4 +-
 ...click-event-not-triggering-in-searchbar.md |   4 +-
 ...-checkboxes-if-you-keep-the-drawer-open.md |   4 +-
 ...cts-when-the-sku-is-individually-showed.md |   4 +-
 ...uplicate-when-the-quantity-is-increased.md |   4 +-
 ...d-when-the-productname-contains-numbers.md |   4 +-
 ...flag-and-discount-after-promotion-ended.md |   4 +-
 ...wn-as-unavailable-at-intelligent-search.md |   4 +-
 ...ted-with-duplicated-skus-on-the-catalog.md |   4 +-
 ...ed-as-with-promotion-for-search-filters.md |   4 +-
 ...-the-admin-when-searching-by-product-id.md |   4 +-
 ...sellers-are-appearing-in-the-end-of-plp.md |   4 +-
 ...form-allows-utf16-format-uploaddownload.md |   4 +-
 ...productsskus-import-does-not-support-lb.md |   4 +-
 ...complete-profile-with-ignoreprofiledata.md |   4 +-
 ...ed-after-adding-client-preferences-data.md |   4 +-
 ...show-splitted-after-adding-profile-data.md |   4 +-
 ...not-working-alongside-regular-promotion.md |   4 +-
 ...equency-not-working-on-recurring-cycles.md |   4 +-
 ...t-performance-or-lead-to-timeout-errors.md |   4 +-
 ...hod-doesnt-works-for-whitelabel-sellers.md |   4 +-
 ...thods-do-not-appear-on-the-product-page.md |   4 +-
 .../pt/promotions-microrounding-divergence.md |   4 +-
 ...-sorting-filtering-by-price-or-discount.md |   4 +-
 ...s-ui-loading-wrong-currency-information.md |   4 +-
 ...ty-blockclass-from-infocard-not-working.md |   4 +-
 ...t-split-items-and-free-shipping-applied.md |   4 +-
 ...er-chooses-to-pay-with-giftcard-and-pse.md |  12 +-
 ...-is-shown-in-the-license-manager-module.md |   4 +-
 ...tes-in-mercado-livre-are-not-integrated.md |   4 +-
 ...ly-when-2-categories-have-the-same-name.md |   4 +-
 ...-in-stores-without-geopositioning-setup.md |   4 +-
 ...nd-is-stuck-on-freight-type-has-changed.md |   4 +-
 ...he-error-receiver-name-field-is-invalid.md |   4 +-
 .../put-price-overwrites-kit-price-logic.md   |   4 +-
 ...-item-with-product-list-component-io-sf.md |   4 +-
 ...he-limit-value-when-user-quickly-clicks.md |   4 +-
 ...-wont-let-me-change-the-value-by-typing.md |   4 +-
 ...h-after-reaching-max-available-qunatity.md |   4 +-
 ...g-longer-than-expected-to-update-status.md |   4 +-
 ...n-the-sku-is-sold-by-more-than-1-seller.md |   4 +-
 ...admins-in-other-languages-only-pt-en-es.md |   4 +-
 ...ter-do-not-work-with-special-characters.md |   4 +-
 ...ceived-skus-review-tab-missing-products.md |   4 +-
 ...parameters-in-cms-builder-does-not-work.md |   4 +-
 ...irects-are-being-counted-multiple-times.md |   4 +-
 ...inks-when-using-in-the-final-of-the-url.md |   4 +-
 ...rresponding-mutation-in-the-graphql-app.md |   4 +-
 ...avior-not-consistent-between-api-and-ui.md |   4 +-
 ...es-us-to-misidentify-mastercard-as-visa.md |   4 +-
 ...auses-us-to-misidentify-the-cards-brand.md |   4 +-
 ...on-api-returns-seller-list-due-to-cache.md |   4 +-
 ...ies-arent-considered-while-filtering-or.md |   4 +-
 ...-while-requesting-nonwhitelabel-sellers.md |   4 +-
 ...delivery-to-pickup-on-the-checkout-page.md |   4 +-
 ...onflicts-with-value-filters-on-the-cart.md |   4 +-
 ...is-not-inactivating-skus-without-refids.md |   4 +-
 .../render-component-issues-on-site-editor.md |   4 +-
 ...ollection-failing-for-large-collections.md |   4 +-
 ...mmary-for-carts-with-more-than-20-items.md |   4 +-
 ...ing-orders-with-different-sales-channel.md |   4 +-
 .../pt/replicated-pending-payment-emails.md   |   4 +-
 ...ing-new-events-when-using-legacy-stores.md |   4 +-
 ...g-is-inconsistent-when-running-ab-tests.md |   4 +-
 ...ecurity-policy-could-break-the-checkout.md |   4 +-
 ...users-orders-api-does-not-return-paging.md |   4 +-
 ...queid-arrays-it-is-not-visible-properly.md |   4 +-
 ...ivering-to-final-customer-on-my-account.md |   4 +-
 .../review-flow-for-updatestock-netshoes.md   |   4 +-
 ...ve-a-different-value-added-to-gift-card.md |   4 +-
 .../rewriter-is-not-receiving-url-updates.md  |   4 +-
 .../rounding-of-totalvalue-in-listorders.md   |   4 +-
 ...-items-with-unitmultiplier-other-than-1.md |   4 +-
 ...terms-of-quantity-of-packages-and-items.md |   4 +-
 ...-assigned-after-approving-organizations.md |   4 +-
 ...annel-info-divergent-between-ui-and-api.md |   4 +-
 ...a-problem-with-some-european-time-zones.md |   4 +-
 ...when-modifying-imported-search-synonyms.md |   4 +-
 .../scheduled-banners-doesnt-work-properly.md |   4 +-
 ...witching-between-delivery-and-scheduled.md |   4 +-
 ...ailing-for-custom-types-in-headless-cms.md |   4 +-
 ...e-when-zooming-after-search-page-render.md |   4 +-
 ...en-theres-a-slider-layout-on-background.md |   4 +-
 .../pt/search-analytics-duplicated-events.md  |   4 +-
 ...een-versions-withwithout-funnel-metrics.md |   4 +-
 ...-api-does-not-accept-special-characters.md |   4 +-
 ...-skus-for-fqspecificationfilter-queries.md |   4 +-
 ...login-in-using-the-call-center-operator.md |   4 +-
 ...wer-case-and-uppercase-for-first-letter.md |   4 +-
 ...rl-after-navigating-through-suggestions.md |   4 +-
 ...the-operator-and-for-trigger-conditions.md |   4 +-
 ...rch-by-ean-not-working-on-received-skus.md |   4 +-
 ...search-filters-disappear-intermittently.md |   4 +-
 ...account-management-when-using-b2b-suite.md |   4 +-
 ...-price-range-yielding-incorrect-results.md |   4 +-
 ...ng-properly-on-store-framework-jamstack.md |   4 +-
 ...lations-over-already-translated-content.md |   4 +-
 ...-does-not-work-on-legacy-cms-collection.md |   4 +-
 ...nto-fuzzy-when-using-special-characters.md |   4 +-
 ...s-with-at-the-end-not-working-correctly.md |   4 +-
 ...t-when-the-value-contains-a-plus-symbol.md |   4 +-
 ...-updated-only-after-refreshing-the-page.md |   4 +-
 ...mmercial-policy-is-not-working-properly.md |   4 +-
 ...sion-updates-does-not-index-binded-skus.md |   4 +-
 ...-creation-does-not-add-selected-sellers.md |   4 +-
 .../seller-logo-not-being-saved-as-an-url.md  |   4 +-
 ...al-account-not-able-to-export-baseprice.md |   4 +-
 ...product-doesnt-load-when-without-images.md |   4 +-
 ...price-condition-not-working-as-expected.md |   4 +-
 ...-specifications-dropdown-malfunctioning.md |   4 +-
 ...s-to-reindex-when-inactivating-a-seller.md |   4 +-
 ...y-of-the-item-to-choose-the-best-option.md |   4 +-
 ...ced-with-problem-in-the-payment-capture.md |   4 +-
 ...ype-name-field-wrongly-returned-via-api.md |   4 +-
 ...ces-are-not-updated-when-added-to-items.md |   4 +-
 ...hen-they-are-not-in-the-same-path-level.md |   4 +-
 ...esnt-update-expiration-period-of-quotes.md |   4 +-
 .../pt/shared-products-import-error.md        |   4 +-
 ...d-in-waiting-for-more-information-state.md |   4 +-
 ...ed-delivery-and-lean-shipping-activated.md |   4 +-
 ...-frozen-when-trying-to-select-an-option.md |   4 +-
 ...atter-of-priority-even-with-better-cost.md |   4 +-
 ...layed-as-active-in-the-new-logistics-ui.md |   4 +-
 ...deliver-on-weekends-is-being-considered.md |   4 +-
 ...es-not-show-message-error-on-simulation.md |   4 +-
 ...e-in-case-of-multiple-packagesdeadlines.md |   4 +-
 ...does-not-use-sla-name-for-display-in-ui.md |   4 +-
 ...s-package-split-for-pickup-and-shipping.md |   4 +-
 ...ng-the-date-when-its-scheduled-delivery.md |   4 +-
 ...g-the-price-when-its-scheduled-delivery.md |   4 +-
 ...view-wrongly-reporting-pickup-selection.md |   4 +-
 ...owing-unavailability-message-for-pickup.md |   4 +-
 ...s-postal-code-input-field-is-not-hidden.md |   4 +-
 ...tion-does-not-generate-highlights-flags.md |   4 +-
 ...rent-slas-causing-divergence-in-tax-hub.md |   4 +-
 ...e-shipping-options-are-being-calculated.md |   4 +-
 ...for-some-countries-united-arab-emirates.md |   4 +-
 .../pt/shopee-could-not-create-product.md     |   4 +-
 ...pee-failed-to-create-product-variations.md |   4 +-
 ...place-shopeeskuhelper-sku-update-failed.md |   4 +-
 ...oducts-ui-brokes-with-too-many-products.md |   4 +-
 ...-catalog-v2-on-shipping-simulation-page.md |   4 +-
 ...ormation-generates-data-loss-in-the-api.md |  12 +-
 ...t-condition-does-not-appear-at-checkout.md |   4 +-
 ...nt-condition-does-not-appear-at-chekout.md |   4 +-
 ...ku-with-multiple-ean-in-merchant-center.md |   4 +-
 ...y-is-not-accessed-using-its-direct-link.md |   4 +-
 ...low-changes-on-the-conditional-template.md |   4 +-
 ...ks-when-accessing-the-landing-route-url.md |   4 +-
 ...ittent-rendering-issues-in-small-screen.md |   4 +-
 ...rsion-when-accessing-via-ipad-on-safari.md |   4 +-
 ...-from-other-subaccounts-and-mainaccount.md |   4 +-
 .../pt/sitemap-isnt-being-generated.md        |   4 +-
 .../pt/sitemap-isnt-being-generatedupdated.md |   4 +-
 ...-cause-problems-in-site-editor-features.md |   4 +-
 ...eference-code-longer-than-50-characters.md |   4 +-
 ...after-throttling-on-marketplace-catalog.md |   4 +-
 ...e-update-does-not-update-v-version-tags.md |   4 +-
 ...ut-doesnt-log-correct-message-on-bridge.md |   4 +-
 ...s-not-responding-with-the-text-property.md |   4 +-
 ...pping-simulation-and-registration-admin.md |  12 +-
 ...ot-follow-the-sku-position-of-the-admin.md |   4 +-
 ...c-is-not-being-disable-in-amazon-portal.md |   4 +-
 ...splay-mode-select-not-working-in-shelfs.md |   4 +-
 ...ving-similar-variations-with-substrings.md |   4 +-
 .../pt/sku-selector-with-multilpe-contexts.md |   4 +-
 ...s-only-available-in-a-whitelabel-seller.md |   4 +-
 ...sku-variations-doesnt-return-in-the-plp.md |   4 +-
 .../pt/skus-expiring-in-merchant-center.md    |   4 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   4 +-
 ...-accounts-with-autoapprove-flag-enabled.md |   4 +-
 ...rs-are-created-with-images-out-of-order.md |   4 +-
 ...-value-tables-at-first-for-a-value-type.md |   4 +-
 ...o-cache-in-estimated-date-of-30-seconds.md |   4 +-
 ...using-prop-infinite-as-always-on-mobile.md |   4 +-
 ...talog-facets-api-have-different-formats.md |   4 +-
 ...-message-centre-module-returns-an-error.md |   4 +-
 ...ail-template-redirects-user-to-404-page.md |   4 +-
 ...-are-not-able-to-be-saved-on-my-account.md |   4 +-
 ...cted-when-viewed-through-safari-browser.md |   4 +-
 ...king-properly-on-seller-portal-accounts.md |   4 +-
 ...ons-cant-be-displayed-in-search-context.md |   4 +-
 ...-being-uploaded-to-the-facebook-catalog.md |   4 +-
 .../pt/some-skus-dont-integrate-dafiti.md     |   4 +-
 ...ipped-from-product-searches-or-indexing.md |   4 +-
 ...played-in-admin-but-are-visible-via-api.md |   4 +-
 .../some-unexpected-behavior-in-masterdata.md |   4 +-
 ...error-is-displayed-in-the-catalog-admin.md |   4 +-
 ...cessing-a-and-p-routes-in-portal-stores.md |   4 +-
 ...incomplete-address-and-tried-to-edit-it.md |   4 +-
 ...rent-on-stores-integrated-before-a-date.md |   4 +-
 ...fects-address-field-display-at-checkout.md |   4 +-
 ...ses-internal-logistics-requests-to-fail.md |   4 +-
 ...special-character-in-seller-name-report.md |   4 +-
 ...t-be-used-for-cnpj-search-on-masterdata.md |   4 +-
 ...enumber-cause-postpurchase-flow-to-fail.md |   4 +-
 ...or-radio-box-category-type-of-selection.md |   4 +-
 ...tion-field-delete-button-not-functional.md |   4 +-
 ...ecification-value-ordering-is-not-saved.md |   4 +-
 .../specifications-multiplied-on-catalog.md   |   4 +-
 ...der-with-value-as-0-zero-on-the-invoice.md |  12 +-
 ...package-suggestion-not-working-properly.md |   4 +-
 ...rect-for-products-with-multiple-sellers.md |   4 +-
 ...fter-approving-the-organization-request.md |   4 +-
 ...s-erro-de-processamento-shipping-policy.md |   4 +-
 ...different-from-the-current-order-status.md |   4 +-
 ...sactions-list-doesnt-match-actual-state.md |   4 +-
 ...ompleted-even-after-receiving-error-500.md |   4 +-
 ...ows-invalid-commercial-condition-values.md |   4 +-
 ...ingunitbyean-returns-404-for-eans-with-.md |  12 +-
 ...-method-allows-to-insert-existent-refid.md |   4 +-
 ...ermissions-app-sets-documenttype-as-cpf.md |   4 +-
 ...ssions-considers-inactive-organizations.md |   4 +-
 ...quested-in-the-address-step-at-checkout.md |   4 +-
 .../stucked-not-found-routes-on-platform.md   |   4 +-
 ...not-show-active-subscriptions-correctly.md |   4 +-
 ...subscription-event-history-out-of-order.md |   4 +-
 ...s-dont-work-properly-for-some-languages.md |   4 +-
 ...oading-the-skus-association-spreadsheet.md |   4 +-
 ...-dashboard-with-conflicting-information.md |   4 +-
 ...ing-failure-or-masterdata-query-failure.md |   4 +-
 ...he-sku-has-linked-to-a-gift-unavailable.md |   4 +-
 ...ckuppointid-contains-special-characters.md |   4 +-
 ...point-and-does-not-have-one-of-the-skus.md |   4 +-
 ...th-less-than-3-characters-does-not-work.md |   4 +-
 ...forming-unitmultiplier-less-than-1-to-0.md |   4 +-
 ...via-update-selected-address-information.md |   4 +-
 ...-revert-the-zoom-causing-display-issues.md |   4 +-
 ...he-pages-with-collections-or-categories.md |   4 +-
 ...senting-success-even-for-failed-actions.md |   4 +-
 ...-not-reflecting-on-the-explained-search.md |   4 +-
 ...onyms-not-shown-in-the-explained-search.md |   4 +-
 ...idering-seller-1-for-rule-sellers-limit.md |   4 +-
 ...ometimes-appear-on-list-format-plp-view.md |   4 +-
 .../pt/tax-apportionment-divergence.md        |   4 +-
 ...s-not-displayng-marketing-tags-dropdown.md |   4 +-
 ...-discounts-when-manual-price-is-applied.md |   4 +-
 ...re-than-once-when-using-assembly-option.md |   4 +-
 ...otions-with-promotion-that-splits-items.md |   4 +-
 ...-nominal-promotions-when-placing-orders.md |   4 +-
 ...en-when-a-cart-has-two-selected-address.md |   4 +-
 ...document-data-instead-of-customer-email.md |   4 +-
 ...ith-requiresauthenticationtoloadprofile.md |   4 +-
 ...nt-accept-special-characters-aside-from.md |   4 +-
 .../term-makes-search-api-have-no-return.md   |   4 +-
 ...-not-being-translated-using-site-editor.md |   4 +-
 ...-not-being-translated-using-site-editor.md |   4 +-
 ...-not-being-translated-using-site-editor.md |   4 +-
 ...-marketplace-upon-approvals-reoccurence.md |   4 +-
 ...textlink-created-with-special-character.md |   4 +-
 ...t-has-never-added-a-new-provider-before.md |   4 +-
 ...rk-on-the-site-editor-with-custom-pages.md |   4 +-
 ...d-returns-to-the-payment-with-two-cards.md |   4 +-
 ...-payments-are-not-reflected-in-checkout.md |   4 +-
 ...rios-when-the-authentication-has-failed.md |   4 +-
 ...e-two-or-more-items-share-the-same-name.md |   4 +-
 ...-causing-sync-problems-of-payment-rules.md |   4 +-
 ...documents-even-with-the-success-message.md |   4 +-
 ...ng-credits-even-if-the-card-is-inactive.md |   4 +-
 ...-the-order-has-the-same-shipping-method.md |   4 +-
 ...n-address-editing-on-romania-my-account.md |   4 +-
 ...-list-after-using-the-api-to-create-put.md |   4 +-
 ...lace-is-always-done-with-saleschannel-1.md |   4 +-
 ...suer-bank-for-this-bank-is-not-accepted.md |   4 +-
 ...-asynchronously-denying-payment-capture.md |   4 +-
 ...s-not-work-with-save-card-functionality.md |   4 +-
 ...s-not-work-with-save-card-functionality.md |   4 +-
 ...when-using-checkout-in-catalan-language.md |   4 +-
 ...ria-that-have-double-spaces-in-the-name.md |   4 +-
 ...data-containing-more-than-40-characters.md |   4 +-
 ...ages-based-on-sku-specifications-change.md |   4 +-
 ...redit-of-payment-method-customer-credit.md |   4 +-
 ...equest-as-query-string-in-the-crm-login.md |   4 +-
 ...work-for-asynchronous-payment-providers.md |   4 +-
 ...-documents-typically-exceeding-millions.md |   4 +-
 ...en-the-restrange-header-is-less-than-10.md |   4 +-
 ...low-multiple-cancellation-with-giftcard.md |   4 +-
 ...ent-affiliation-for-debit-online-method.md |   4 +-
 ...n-one-extension-payment-affiliation-for.md |  12 +-
 ...eestoque-does-not-support-multilanguage.md |   4 +-
 ...tions-if-the-payload-exceeds-5000-lines.md |   4 +-
 ...-directly-from-the-mysubscriptions-area.md |   4 +-
 ...romissory-doesnt-cancel-the-transaction.md |   4 +-
 docs/known-issues/pt/this-is-a-test.md        |   4 +-
 .../pt/time-out-at-relatorioindexacaoaspx.md  |   4 +-
 .../pt/time-out-import-and-export-admin.md    |   4 +-
 ...gory-keywords-change-with-many-products.md |   4 +-
 ...eout-api-get-accounts-approval-settings.md |   4 +-
 ...ut-generating-internal-application-keys.md |   4 +-
 ...s-preventing-to-check-the-inventory-log.md |   4 +-
 ...terms-presented-in-the-analytics-report.md |   4 +-
 ...tem-with-negative-value-in-inventory-ui.md |   4 +-
 docs/known-issues/pt/tracking-error.md        |   4 +-
 ...-api-do-not-generate-reindexing-request.md |   4 +-
 ...-request-para-o-sistema-de-parcelamento.md |   4 +-
 ...ion-error-with-unreachable-code-message.md |   4 +-
 ...us-prior-to-the-state-that-it-should-be.md |   4 +-
 ...ing-risk-due-to-null-documenttype-field.md |   4 +-
 ...anceling-when-one-of-the-card-is-denied.md |  12 +-
 ...n-status-approved-with-payment-canceled.md |   4 +-
 ...o-pspresponsecod-in-settlement-response.md |   4 +-
 ...nsactions-entered-into-wrong-conditions.md |   4 +-
 ...yu-do-not-change-from-cancelling-status.md |   4 +-
 ...g-longer-than-expected-to-update-status.md |   4 +-
 ...enied-by-error-card-not-enrolled-in-3ds.md |   4 +-
 ...count-to-implement-multilanguage-stores.md |   4 +-
 ...ng-saved-in-vbase-and-not-into-rewriter.md |   4 +-
 ...roduct-name-and-description-on-centauro.md |   4 +-
 ...der-resulting-in-status-detailstatenull.md |   4 +-
 ...p-and-item-is-not-in-the-first-position.md |   4 +-
 ...ly-the-available-items-to-calculate-sla.md |   4 +-
 ...eflect-invoice-address-selection-markup.md |   4 +-
 ...does-not-update-best-sla-choice-in-cart.md |   4 +-
 ...en-items-for-pickup-from-another-seller.md |   4 +-
 ...en-selecting-to-add-a-new-address-first.md |   4 +-
 ...-delivery-when-it-has-delivery-division.md |   4 +-
 ...tween-delivery-and-collection-correctly.md |   4 +-
 ...urs-in-the-place-order-internal-process.md |   4 +-
 ...dress-that-had-previously-available-sla.md |   4 +-
 ...-with-subscriptions-but-it-wasnt-in-api.md |   4 +-
 ...-email-template-sender-has-its-own-smtp.md |   4 +-
 ...or-delivery-is-between-items-for-pickup.md |   4 +-
 ...ed-when-using-order-replacement-feature.md |   4 +-
 ...ests-for-each-keyfield-of-an-attachment.md |   4 +-
 ...ers-is-selected-for-delivery-and-pickup.md |   4 +-
 ...ckages-are-split-for-scheduled-delivery.md |   4 +-
 .../unable-to-access-vtex-payment-account.md  |   4 +-
 ...ons-that-had-payout-split-config-change.md |   4 +-
 ...n-cart-object-in-transaction-is-unknown.md |   4 +-
 ...te-produtos-relacionados-custom-element.md |   4 +-
 ...unable-to-delete-template-on-legacy-cms.md |   4 +-
 ...le-to-download-prices-importing-results.md |   4 +-
 ...rt-more-than-65536-lines-in-cms-builder.md |   4 +-
 ...to-log-in-through-the-google-app-on-ios.md |   4 +-
 .../known-issues/pt/unable-to-pause-seller.md |   4 +-
 ...sing-protocol-encryption-protocol-ssl13.md |   4 +-
 ...scenario-while-using-whitelabel-sellers.md |   4 +-
 ...e-products-pdp-are-still-being-returned.md |   4 +-
 ...ritization-by-diacritics-for-portuguese.md |   4 +-
 ...-requests-and-components-being-reloaded.md |   4 +-
 ...-props-infinitetrue-and-navigationstep1.md |   4 +-
 ...em-is-available-through-the-same-option.md |   4 +-
 ...ning-when-registeringupdating-a-product.md |   4 +-
 ...-error-when-changing-edition-of-account.md |   4 +-
 ...mber-to-fetch-a-transaction-in-admin-ui.md |   4 +-
 ...exportacaoimportacaoespecificacaov2aspx.md |   4 +-
 ...t-search-api-return-wrong-or-empty-data.md |   4 +-
 ...default-value-after-changing-it-via-api.md |   4 +-
 ...s-does-not-trigger-automatic-indexation.md |   4 +-
 .../update-users-name-in-the-login-section.md |   4 +-
 ...ue-to-lacking-property-on-get-resp-json.md |   4 +-
 ...-working-on-adminportalsitesdefaultcode.md |   4 +-
 ...-the-update-seller-request-not-updating.md |   4 +-
 ...cial-characters-non-ascii-return-errors.md |   4 +-
 .../pt/urls-redirecionando-para-buscavazia.md |   4 +-
 ...res-even-without-the-correct-permission.md |   4 +-
 ...rder-and-does-not-allow-ui-reprocessing.md |   4 +-
 ...estricted-is-not-able-to-list-the-users.md |   4 +-
 ...age-on-first-registration-in-my-account.md |   4 +-
 ...i-on-the-admin-due-to-a-forbidden-error.md |   4 +-
 ...ant-access-gift-card-admin-looping-page.md |   4 +-
 ...ey-try-to-log-in-by-saml-authentication.md |   4 +-
 ...n-not-see-the-orders-on-my-account-page.md |   4 +-
 ...-when-adding-the-first-item-to-the-cart.md |   4 +-
 ...-list-affects-the-results-in-the-report.md |   4 +-
 ...nstep-to-1-causes-last-dots-to-be-empty.md |   4 +-
 ...c-not-being-kept-on-the-url-after-login.md |   4 +-
 ...cartmutation-failing-when-large-payload.md |   4 +-
 ...fields-at-checkout-not-working-properly.md |  12 +-
 .../vbase-responds-404-to-vtexpagesgraphql.md |   4 +-
 ...-mycards-are-not-automatically-canceled.md |   4 +-
 ...ote-not-found-on-vtex-id-on-the-profile.md |   4 +-
 ...ion-not-sending-the-description-in-card.md |   4 +-
 ...t-being-sent-from-seller-to-marketplace.md |   4 +-
 ...ent-doesnt-work-properly-on-ios-devices.md |   4 +-
 ...eived-on-the-datalayer-every-other-time.md |   4 +-
 ...-we-change-product-quantity-in-minicart.md |   4 +-
 ...-product-feature-does-not-work-properly.md |   4 +-
 ...when-multiple-search-terms-are-provided.md |   4 +-
 ...-does-not-work-before-acessing-checkout.md |   4 +-
 ...placeholder-idacessorios-is-not-working.md |   4 +-
 ...-pageurl-parameter-using-http-not-https.md |   4 +-
 ...-pickup-point-deleted-instore-warehouse.md |   4 +-
 ...clientid-field-of-the-giftcard-on-admin.md |   4 +-
 ...shows-success-even-when-it-isnt-working.md |   4 +-
 ...-not-fully-integrated-with-headless-cms.md |   4 +-
 ...ctname-without-the-sku-name-information.md |   4 +-
 ...yed-in-the-order-and-email-notification.md |   4 +-
 ...ent-the-transaction-cannot-be-completed.md |   4 +-
 ...er-its-not-possible-to-use-a-custom-one.md |   4 +-
 ...n-the-initial-message-is-not-translated.md |   4 +-
 ...-cart-ui-makes-incorrect-request-to-api.md |   4 +-
 ...ly-our-gateway-performs-a-double-refund.md |   4 +-
 ...ryslainminutes-calculation-returns-null.md |   4 +-
 ...ected-to-the-braspag-affiliation-screen.md |   4 +-
 ...-filters-options-doesnt-colapse-anymore.md |   4 +-
 ...utton-calltoaction-name-in-profile-step.md |   4 +-
 ...api-when-the-payload-request-is-invalid.md |   4 +-
 ...rror-when-using-a-nonexisting-gift-card.md |   4 +-
 ...eater-than-1-in-intelligent-search-apis.md |   4 +-
 ...nt-fields-under-the-same-original-value.md |   4 +-
 ...hain-order-for-a-multilevel-marketplace.md |   4 +-
 ...saction-split-with-partial-cancellation.md |   4 +-
 .../xml-file-does-not-get-price-from-swl.md   |   4 +-
 ...mation-defined-on-category-global-level.md |   4 +-
 ...xml-installment-currency-does-not-apply.md |   4 +-
 ...not-load-contents-for-unavailable-items.md |   4 +-
 ...xml-url-on-the-admin-showing-wrong-link.md |   4 +-
 docs/known-issues/pt/xmlaspx-timeout.md       |   4 +-
 ...-product-name-flag-not-working-properly.md |   4 +-
 .../pt/xmls-returning-500-error.md            |   4 +-
 docs/tracks/en/accounts-and-architecture.md   |  21 ++-
 docs/tracks/en/add-an-image-to-the-sku.md     |   4 +-
 docs/tracks/en/add-on-products.md             |   8 +-
 docs/tracks/en/add-pickup-points.md           |   4 +-
 docs/tracks/en/add-sku-specifications.md      |   4 +-
 docs/tracks/en/adding-a-loading-dock.md       |   8 +-
 docs/tracks/en/adding-a-price-rule.md         |   4 +-
 docs/tracks/en/adding-a-sender.md             |   4 +-
 docs/tracks/en/adding-collections-track.md    |   4 +-
 .../adding-extra-text-to-the-order-print.md   |   8 +-
 docs/tracks/en/adding-holidays.md             |   8 +-
 .../en/adding-product-specifications.md       |   4 +-
 docs/tracks/en/adding-products.md             |   4 +-
 docs/tracks/en/adding-skus.md                 |   4 +-
 .../adding-the-magazine-luiza-integration.md  |   3 +-
 docs/tracks/en/adding-vendors.md              |   4 +-
 docs/tracks/en/adding-warehouses.md           |   4 +-
 docs/tracks/en/amazon-account-settings.md     |   4 +-
 docs/tracks/en/apple-pay.md                   |   8 +-
 ...enticating-your-google-shopping-account.md |   4 +-
 docs/tracks/en/backend-integrations.md        |  12 +-
 .../en/basic-vtex-io-developer-setup.md       |   8 +-
 docs/tracks/en/cadastrar-preco-base.md        |   4 +-
 docs/tracks/en/cadastrar-tabelas-de-preco.md  |   4 +-
 docs/tracks/en/cadastrar-trava-de-preco.md    |   4 +-
 docs/tracks/en/canceling-an-order.md          |   4 +-
 ...tes-de-iniciar-uma-conversa-no-whatsapp.md |   4 +-
 .../en/categories-concept-definition.md       |   8 +-
 .../en/changing-the-instore-language.md       |   4 +-
 docs/tracks/en/cms-folder-structure.md        |   8 +-
 ...ento-no-whatsapp-para-mais-de-um-numero.md |   4 +-
 .../en/como-funciona-o-adaptador-vtex.md      |   4 +-
 ...uracao-da-estrutura-para-suporte-humano.md |   4 +-
 docs/tracks/en/configurar-adaptador.md        |   4 +-
 docs/tracks/en/configurar-erps.md             |   4 +-
 .../en/configure-clustered-conditions.md      |  12 +-
 docs/tracks/en/configure-integration.md       |   2 +-
 docs/tracks/en/configuring-banners.md         |   4 +-
 .../en/configuring-merchandising-rules.md     |  16 +-
 .../en/configuring-payment-connectors.md      |   4 +-
 ...onfiguring-price-divergence-rule-amazon.md |   4 +-
 .../configuring-price-divergence-rule-via.md  |   4 +-
 docs/tracks/en/configuring-ship-from-store.md |   4 +-
 docs/tracks/en/configuring-synonyms.md        |   8 +-
 .../en/configuring-the-amazon-integration.md  |   4 +-
 ...iguring-the-google-shopping-integration.md |   4 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |   4 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  12 +-
 docs/tracks/en/create-a-product.md            |  12 +-
 docs/tracks/en/create-an-account.md           |   4 +-
 docs/tracks/en/create-an-sku.md               |   4 +-
 docs/tracks/en/create-the-category-tree.md    |  12 +-
 docs/tracks/en/creating-accounts.md           |  12 +-
 docs/tracks/en/creating-and-editing-users.md  |   4 +-
 docs/tracks/en/creating-discount-coupons.md   |   8 +-
 docs/tracks/en/creating-franchise-accounts.md |   4 +-
 ...ating-merchandising-rules-visual-editor.md |   4 +-
 .../en/creating-or-editing-a-page-template.md |  19 ++-
 docs/tracks/en/creating-regular-promotions.md |   4 +-
 docs/tracks/en/credit-card-payment-flow.md    |   4 +-
 ...tor-and-dimensional-weight-calculations.md |   4 +-
 docs/tracks/en/customer-identification.md     |   4 +-
 docs/tracks/en/customizing-instore.md         |   4 +-
 docs/tracks/en/customizing-instores-layout.md |   4 +-
 docs/tracks/en/data-protection-roles.md       |   4 +-
 ...ne-payment-methods-displayed-on-instore.md |   4 +-
 ...fining-the-google-shopping-trade-policy.md |   8 +-
 .../en/detaching-skus-by-specification.md     |   3 +-
 .../en/enable-clustered-payment-conditions.md |  10 +-
 .../enabling-2-factor-authentication-login.md |  16 +-
 docs/tracks/en/enabling-a-sales-rep-code.md   |  16 +-
 .../enabling-cart-transfer-between-devices.md |   4 +-
 .../enabling-order-filter-by-salesperson.md   |   8 +-
 .../en/enabling-product-recommendations.md    |   8 +-
 ...g-the-remarks-field-in-the-order-screen.md |   8 +-
 ...o-os-clientes-chegam-ate-o-seu-whatsapp.md |   4 +-
 docs/tracks/en/exporting-an-order.md          |   4 +-
 docs/tracks/en/extensions-hub-partners.md     |   4 +-
 docs/tracks/en/facebook-business-extension.md |   4 +-
 docs/tracks/en/filters.md                     |  12 +-
 docs/tracks/en/forcing-stock-availability.md  |   8 +-
 docs/tracks/en/frontend-implementation.md     |   4 +-
 ...website-and-social-networks-to-whatsapp.md |   4 +-
 .../en/getting-started-with-logistics.md      |  20 +--
 docs/tracks/en/go-live-process.md             |   4 +-
 docs/tracks/en/go-live.md                     |   4 +-
 docs/tracks/en/google-pay.md                  |  12 +-
 docs/tracks/en/google-shopping-ads-install.md |   4 +-
 docs/tracks/en/google-shopping-ads-set-up.md  |   8 +-
 docs/tracks/en/google-shopping-marketplace.md |   4 +-
 .../how-a-split-payment-transaction-works.md  |   4 +-
 .../en/how-clustered-conditions-work.md       |   4 +-
 .../how-does-vtex-intelligent-search-work.md  |   8 +-
 .../en/how-the-payments-module-works.md       |   4 +-
 ...nfigure-a-device-for-printout-the-order.md |   8 +-
 ...-and-edit-transactional-email-templates.md |   4 +-
 .../how-to-customize-the-observation-field.md |   4 +-
 docs/tracks/en/how-to-get-started.md          |   4 +-
 ...uding-order-variables-in-email-template.md |   4 +-
 docs/tracks/en/initial-setup.md               |  19 +--
 .../en/initializing-your-store-theme.md       |   8 +-
 docs/tracks/en/instore-basic-settings.md      |  12 +-
 docs/tracks/en/instore-customizations.md      |   8 +-
 docs/tracks/en/instore.md                     |   4 +-
 ...ating-instore-to-a-new-payment-acquirer.md |   8 +-
 docs/tracks/en/integration-configurations.md  |  82 +++++----
 docs/tracks/en/integration-overview.md        |   8 +-
 docs/tracks/en/intelligent-synonyms.md        |   4 +-
 docs/tracks/en/introduction-to-vtex.md        |   8 +-
 .../inventory-and-shipping-module-overview.md |   4 +-
 docs/tracks/en/legacy-cms-portal.md           |   8 +-
 ...var-os-contatos-do-whatsapp-para-um-crm.md |   4 +-
 docs/tracks/en/live-support.md                |   4 +-
 docs/tracks/en/login-e-senha.md               |   4 +-
 docs/tracks/en/manage-skus-in-inventory.md    |   4 +-
 docs/tracks/en/managing-accounts.md           |   8 +-
 .../en/managing-customer-credit-invoices.md   |   8 +-
 docs/tracks/en/managing-shipping-rates.md     |   4 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  13 +-
 .../en/merchandising-rule-conditions.md       |   4 +-
 docs/tracks/en/monitor-da-integracao.md       |   4 +-
 docs/tracks/en/next-steps.md                  |   4 +-
 docs/tracks/en/order-flow.md                  |  25 ++-
 .../en/pickup-points-concept-definition.md    |   4 +-
 docs/tracks/en/pickup-store.md                |   4 +-
 docs/tracks/en/planning-the-go-live.md        |  28 +---
 docs/tracks/en/pre-go-live.md                 |   4 +-
 .../en/preco-fixo-definicao-de-conceito.md    |   4 +-
 docs/tracks/en/printing-an-order-summary.md   |   4 +-
 .../en/promotions-for-specific-scenarios.md   |   8 +-
 docs/tracks/en/redirect.md                    |   4 +-
 ...ter-the-barcode-of-the-skus-for-instore.md |   8 +-
 .../regra-de-preco-definicao-de-conceito.md   |   4 +-
 docs/tracks/en/relevance.md                   |   4 +-
 .../en/reports-vtex-intelligent-search.md     |   4 +-
 ...eduled-deliveries-and-delivery-capacity.md |   6 +-
 docs/tracks/en/seeing-order-details.md        |   4 +-
 .../en/sending-product-data-to-dafiti.md      |   2 +-
 docs/tracks/en/sending-products-to-amazon.md  |  23 +--
 .../tracks/en/sending-products-to-facebook.md |  12 +-
 .../en/sending-products-to-google-shopping.md |  12 +-
 docs/tracks/en/set-a-price-for-the-sku.md     |   4 +-
 ...setting-up-a-marketplace-trade-policy-2.md |   3 +-
 .../setting-up-a-marketplace-trade-policy.md  |   3 +-
 docs/tracks/en/setting-up-a-smart-campaign.md |   8 +-
 ...app-linking-for-payments-app-in-instore.md |   8 +-
 docs/tracks/en/setting-up-instore-as-a-pos.md |   4 +-
 docs/tracks/en/setting-up-pix.md              |   4 +-
 ...s-template-description-in-mercado-livre.md |   8 +-
 docs/tracks/en/setting-up-the-app.md          |  12 +-
 ...ting-up-the-cappta-acquirer-for-instore.md |   4 +-
 ...g-up-the-cielo-lio-acquirer-for-instore.md |   8 +-
 .../setting-up-the-order-summary-printing.md  |  20 +--
 ...ng-up-the-pagar-me-acquirer-for-instore.md |   8 +-
 ...tting-up-the-sitef-acquirer-for-instore.md |  12 +-
 ...tting-up-the-stone-acquirer-for-instore.md |   8 +-
 docs/tracks/en/settings.md                    |  12 +-
 ...pping-cart-using-instore-social-selling.md |   4 +-
 docs/tracks/en/shipping-strategies.md         |   8 +-
 .../en/specifications-concept-definition.md   |   8 +-
 docs/tracks/en/subscription-orders.md         |   4 +-
 docs/tracks/en/teste-1.md                     |   4 +-
 docs/tracks/en/the-reservation.md             |   8 +-
 docs/tracks/en/tiktok-for-business.md         |   4 +-
 docs/tracks/en/unified-commerce.md            |   4 +-
 docs/tracks/en/vtex-modules-i.md              |  24 +--
 docs/tracks/en/vtex-modules-ii.md             |  12 +-
 docs/tracks/en/vtex-platform-settings.md      |   8 +-
 .../what-are-clustered-payment-conditions.md  |   4 +-
 ...hat-are-permissions-and-access-profiles.md |   4 +-
 .../what-is-conversational-commerce-vtex.md   |   4 +-
 docs/tracks/en/what-is-lengow.md              |   4 +-
 docs/tracks/en/what-is-suiteshare.md          |   4 +-
 docs/tracks/en/what-is-the-payment-split.md   |  12 +-
 ...figure-in-wish-prior-to-the-integration.md |   2 +-
 ...th-vtex-before-starting-the-integration.md |  18 +-
 docs/tracks/es/accounts-and-architecture.md   |  17 +-
 docs/tracks/es/add-an-image-to-the-sku.md     |   4 +-
 docs/tracks/es/add-on-products.md             |   8 +-
 docs/tracks/es/add-pickup-points.md           |   4 +-
 docs/tracks/es/add-sku-specifications.md      |   4 +-
 docs/tracks/es/adding-a-loading-dock.md       |  10 +-
 docs/tracks/es/adding-a-price-rule.md         |   4 +-
 docs/tracks/es/adding-a-sender.md             |   4 +-
 .../adding-extra-text-to-the-order-print.md   |   8 +-
 docs/tracks/es/adding-holidays.md             |   8 +-
 .../es/adding-product-specifications.md       |   4 +-
 docs/tracks/es/adding-products.md             |   4 +-
 .../adding-the-magazine-luiza-integration.md  |   3 +-
 docs/tracks/es/adding-warehouses.md           |   4 +-
 docs/tracks/es/amazon-account-settings.md     |   4 +-
 docs/tracks/es/apple-pay.md                   |   4 +-
 ...enticating-your-google-shopping-account.md |   4 +-
 docs/tracks/es/backend-integrations.md        |  12 +-
 .../es/basic-vtex-io-developer-setup.md       |   8 +-
 docs/tracks/es/cadastrar-preco-base.md        |   4 +-
 docs/tracks/es/cadastrar-tabelas-de-preco.md  |   4 +-
 docs/tracks/es/cadastrar-trava-de-preco.md    |   4 +-
 docs/tracks/es/canceling-an-order.md          |   4 +-
 ...tes-de-iniciar-uma-conversa-no-whatsapp.md |   4 +-
 .../es/categories-concept-definition.md       |   8 +-
 .../es/changing-the-instore-language.md       |   4 +-
 ...ento-no-whatsapp-para-mais-de-um-numero.md |   4 +-
 .../es/como-funciona-o-adaptador-vtex.md      |   4 +-
 ...uracao-da-estrutura-para-suporte-humano.md |   4 +-
 docs/tracks/es/configurar-adaptador.md        |   4 +-
 docs/tracks/es/configurar-erps.md             |   4 +-
 .../es/configure-clustered-conditions.md      |  12 +-
 ...configure-integration-of-pick-up-points.md |   4 +-
 docs/tracks/es/configure-integration.md       |   4 +-
 docs/tracks/es/configuring-banners.md         |   4 +-
 .../tracks/es/configuring-dafiti-connector.md |   4 +-
 .../es/configuring-merchandising-rules.md     |  16 +-
 ...onfiguring-price-divergence-rule-amazon.md |   4 +-
 ...onfiguring-price-divergence-rule-dafiti.md |   4 +-
 ...ing-price-divergence-rule-mercado-libre.md |   4 +-
 .../configuring-price-divergence-rule-via.md  |   4 +-
 docs/tracks/es/configuring-ship-from-store.md |   4 +-
 docs/tracks/es/configuring-synonyms.md        |   8 +-
 .../es/configuring-the-amazon-integration.md  |   4 +-
 ...iguring-the-google-shopping-integration.md |   4 +-
 .../es/configuring-the-integration-dafiti.md  |   4 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |   4 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  12 +-
 docs/tracks/es/create-a-product.md            |  12 +-
 docs/tracks/es/create-an-account.md           |   4 +-
 docs/tracks/es/create-an-sku.md               |   4 +-
 docs/tracks/es/create-the-category-tree.md    |   4 +-
 docs/tracks/es/creating-accounts.md           |  12 +-
 docs/tracks/es/creating-and-editing-users.md  |   4 +-
 docs/tracks/es/creating-discount-coupons.md   |   8 +-
 docs/tracks/es/creating-franchise-accounts.md |   4 +-
 ...ating-merchandising-rules-visual-editor.md |   4 +-
 .../es/creating-or-editing-a-page-template.md |  19 ++-
 docs/tracks/es/creating-regular-promotions.md |   4 +-
 docs/tracks/es/credit-card-payment-flow.md    |   4 +-
 ...tor-and-dimensional-weight-calculations.md |   4 +-
 docs/tracks/es/customer-identification.md     |   4 +-
 docs/tracks/es/customizing-instore.md         |   4 +-
 docs/tracks/es/customizing-instores-layout.md |   4 +-
 docs/tracks/es/data-protection-roles.md       |   4 +-
 ...ne-payment-methods-displayed-on-instore.md |   4 +-
 ...fining-the-google-shopping-trade-policy.md |   8 +-
 .../es/detaching-skus-by-specification.md     |   3 +-
 .../es/enable-clustered-payment-conditions.md |   8 +-
 .../enabling-2-factor-authentication-login.md |  17 +-
 docs/tracks/es/enabling-a-sales-rep-code.md   |  16 +-
 .../enabling-cart-transfer-between-devices.md |   4 +-
 .../enabling-order-filter-by-salesperson.md   |   8 +-
 .../es/enabling-product-recommendations.md    |   4 +-
 ...g-the-remarks-field-in-the-order-screen.md |   8 +-
 ...o-os-clientes-chegam-ate-o-seu-whatsapp.md |   4 +-
 docs/tracks/es/exporting-an-order.md          |   4 +-
 docs/tracks/es/extensions-hub-partners.md     |   4 +-
 docs/tracks/es/facebook-business-extension.md |   4 +-
 docs/tracks/es/filters.md                     |  12 +-
 docs/tracks/es/forcing-stock-availability.md  |   8 +-
 docs/tracks/es/frontend-implementation.md     |   4 +-
 ...website-and-social-networks-to-whatsapp.md |   4 +-
 .../es/getting-started-with-logistics.md      |  20 +--
 docs/tracks/es/go-live-process.md             |   4 +-
 docs/tracks/es/go-live.md                     |   8 +-
 docs/tracks/es/google-pay.md                  |  12 +-
 docs/tracks/es/google-shopping-ads-install.md |   4 +-
 docs/tracks/es/google-shopping-ads-set-up.md  |  12 +-
 docs/tracks/es/google-shopping-marketplace.md |   4 +-
 .../es/how-clustered-conditions-work.md       |   4 +-
 .../how-does-vtex-intelligent-search-work.md  |   8 +-
 .../es/how-the-payments-module-works.md       |   4 +-
 ...nfigure-a-device-for-printout-the-order.md |   8 +-
 ...-and-edit-transactional-email-templates.md |   4 +-
 .../how-to-customize-the-observation-field.md |   6 +-
 docs/tracks/es/how-to-get-started.md          |   4 +-
 ...uding-order-variables-in-email-template.md |   4 +-
 docs/tracks/es/initial-setup.md               |  19 +--
 docs/tracks/es/instore-basic-settings.md      |  12 +-
 docs/tracks/es/instore-customizations.md      |   8 +-
 docs/tracks/es/instore.md                     |   4 +-
 ...ating-instore-to-a-new-payment-acquirer.md |  14 +-
 docs/tracks/es/integration-overview.md        |   8 +-
 docs/tracks/es/intelligent-synonyms.md        |   4 +-
 docs/tracks/es/introduction-to-vtex.md        |   8 +-
 .../inventory-and-shipping-module-overview.md |   4 +-
 ...var-os-contatos-do-whatsapp-para-um-crm.md |   4 +-
 docs/tracks/es/live-support.md                |   4 +-
 docs/tracks/es/login-e-senha.md               |   4 +-
 docs/tracks/es/manage-skus-in-inventory.md    |   4 +-
 docs/tracks/es/managing-accounts.md           |   8 +-
 .../es/managing-customer-credit-invoices.md   |   8 +-
 docs/tracks/es/managing-shipping-rates.md     |   4 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  13 +-
 .../es/merchandising-rule-conditions.md       |   4 +-
 docs/tracks/es/monitor-da-integracao.md       |   4 +-
 docs/tracks/es/next-steps.md                  |   4 +-
 docs/tracks/es/order-flow.md                  |  25 ++-
 .../es/pickup-points-concept-definition.md    |   4 +-
 docs/tracks/es/pickup-store.md                |   4 +-
 docs/tracks/es/planning-the-go-live.md        |  28 +---
 docs/tracks/es/pre-go-live.md                 |   4 +-
 .../es/preco-fixo-definicao-de-conceito.md    |   4 +-
 docs/tracks/es/printing-an-order-summary.md   |   4 +-
 .../es/promotions-for-specific-scenarios.md   |   8 +-
 docs/tracks/es/redirect.md                    |   4 +-
 .../es/register-mercado-livre-integration.md  |   4 +-
 ...ter-the-barcode-of-the-skus-for-instore.md |   8 +-
 .../regra-de-preco-definicao-de-conceito.md   |   4 +-
 docs/tracks/es/relevance.md                   |   4 +-
 .../es/reports-vtex-intelligent-search.md     |   4 +-
 ...eduled-deliveries-and-delivery-capacity.md |   6 +-
 docs/tracks/es/seeing-order-details.md        |   4 +-
 .../es/sending-product-data-to-dafiti.md      |  12 +-
 docs/tracks/es/sending-products-to-amazon.md  |  24 +--
 .../tracks/es/sending-products-to-facebook.md |  12 +-
 .../es/sending-products-to-google-shopping.md |  12 +-
 .../setting-up-a-marketplace-trade-policy.md  |   4 +-
 docs/tracks/es/setting-up-a-smart-campaign.md |   8 +-
 ...app-linking-for-payments-app-in-instore.md |  14 +-
 docs/tracks/es/setting-up-instore-as-a-pos.md |   4 +-
 docs/tracks/es/setting-up-pix.md              |   4 +-
 ...s-template-description-in-mercado-livre.md |   8 +-
 docs/tracks/es/setting-up-the-app.md          |  12 +-
 ...ting-up-the-cappta-acquirer-for-instore.md |  23 +--
 ...g-up-the-cielo-lio-acquirer-for-instore.md |   8 +-
 ...ting-up-the-logistics-for-mercado-livre.md |  20 +--
 .../setting-up-the-order-summary-printing.md  |  20 +--
 ...ng-up-the-pagar-me-acquirer-for-instore.md |   8 +-
 ...tting-up-the-sitef-acquirer-for-instore.md |  32 ++--
 ...tting-up-the-stone-acquirer-for-instore.md |   8 +-
 docs/tracks/es/settings.md                    |  12 +-
 ...pping-cart-using-instore-social-selling.md |   4 +-
 docs/tracks/es/shipping-strategies.md         |   8 +-
 .../es/specifications-concept-definition.md   |   8 +-
 docs/tracks/es/subscription-orders.md         |   4 +-
 docs/tracks/es/teste-1.md                     |   4 +-
 docs/tracks/es/the-reservation.md             |   8 +-
 docs/tracks/es/tiktok-for-business.md         |   4 +-
 docs/tracks/es/unified-commerce.md            |   4 +-
 docs/tracks/es/vtex-modules-i.md              |  24 +--
 docs/tracks/es/vtex-modules-ii.md             |  16 +-
 docs/tracks/es/vtex-platform-settings.md      |   8 +-
 .../what-are-clustered-payment-conditions.md  |   4 +-
 ...hat-are-permissions-and-access-profiles.md |   4 +-
 .../what-is-conversational-commerce-vtex.md   |   4 +-
 docs/tracks/es/what-is-suiteshare.md          |   4 +-
 docs/tracks/es/what-is-the-payment-split.md   |  16 +-
 ...figure-in-wish-prior-to-the-integration.md |   2 +-
 ...th-vtex-before-starting-the-integration.md |  18 +-
 docs/tracks/pt/about-b2w-integration.md       |   4 +-
 docs/tracks/pt/accounts-and-architecture.md   |  15 +-
 docs/tracks/pt/add-an-image-to-the-sku.md     |   4 +-
 docs/tracks/pt/add-on-products.md             |   8 +-
 docs/tracks/pt/add-pickup-points.md           |   4 +-
 docs/tracks/pt/add-sku-specifications.md      |   4 +-
 docs/tracks/pt/adding-a-loading-dock.md       |   8 +-
 docs/tracks/pt/adding-a-price-rule.md         |   4 +-
 docs/tracks/pt/adding-a-sender.md             |   4 +-
 docs/tracks/pt/adding-collections-track.md    |   4 +-
 .../adding-extra-text-to-the-order-print.md   |   8 +-
 docs/tracks/pt/adding-holidays.md             |   8 +-
 .../pt/adding-product-specifications.md       |   4 +-
 docs/tracks/pt/adding-products.md             |   4 +-
 .../adding-the-magazine-luiza-integration.md  |   4 +-
 docs/tracks/pt/adding-vendors.md              |   8 +-
 docs/tracks/pt/adding-warehouses.md           |   4 +-
 docs/tracks/pt/amazon-account-settings.md     |   4 +-
 docs/tracks/pt/apple-pay.md                   |   8 +-
 ...enticating-your-google-shopping-account.md |   4 +-
 docs/tracks/pt/backend-integrations.md        |  12 +-
 .../pt/basic-vtex-io-developer-setup.md       |   8 +-
 docs/tracks/pt/cadastrar-preco-base.md        |   4 +-
 docs/tracks/pt/cadastrar-tabelas-de-preco.md  |   4 +-
 docs/tracks/pt/cadastrar-trava-de-preco.md    |   4 +-
 docs/tracks/pt/canceling-an-order.md          |   4 +-
 .../pt/categories-concept-definition.md       |   8 +-
 .../pt/changing-the-instore-language.md       |   4 +-
 .../pt/como-funciona-o-adaptador-vtex.md      |   8 +-
 ...uracao-da-estrutura-para-suporte-humano.md |   4 +-
 docs/tracks/pt/configurar-adaptador.md        |  12 +-
 docs/tracks/pt/configurar-erps.md             |   4 +-
 .../pt/configure-clustered-conditions.md      |  12 +-
 ...configure-integration-of-pick-up-points.md |   4 +-
 docs/tracks/pt/configure-integration.md       |   6 +-
 ...nfiguring-cash-payments-through-instore.md |   4 +-
 .../tracks/pt/configuring-dafiti-connector.md |  10 +-
 ...onfiguring-livelo-price-divergence-rule.md |  10 +-
 .../pt/configuring-merchandising-rules.md     |  16 +-
 ...onfiguring-price-divergence-rule-amazon.md |   4 +-
 ...iguring-price-divergence-rule-carrefour.md |   4 +-
 ...figuring-price-divergence-rule-centauro.md |   4 +-
 ...onfiguring-price-divergence-rule-dafiti.md |   6 +-
 ...ng-price-divergence-rule-magazine-luiza.md |   4 +-
 ...ing-price-divergence-rule-mercado-libre.md |   4 +-
 ...figuring-price-divergence-rule-netshoes.md |   4 +-
 .../configuring-price-divergence-rule-via.md  |   4 +-
 .../pt/configuring-price-divergence-rule.md   |   4 +-
 ...configuring-rappi-price-divergence-rule.md |   6 +-
 docs/tracks/pt/configuring-ship-from-store.md |   4 +-
 docs/tracks/pt/configuring-synonyms.md        |   4 +-
 .../pt/configuring-the-amazon-integration.md  |   4 +-
 .../pt/configuring-the-connector-b2w.md       |   6 +-
 ...iguring-the-google-shopping-integration.md |   4 +-
 .../pt/configuring-the-integration-dafiti.md  |   4 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |   4 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |   8 +-
 docs/tracks/pt/configuring-the-integration.md |   4 +-
 docs/tracks/pt/create-a-product.md            |  12 +-
 docs/tracks/pt/create-an-account.md           |   4 +-
 docs/tracks/pt/create-an-sku.md               |   4 +-
 docs/tracks/pt/create-the-category-tree.md    |  12 +-
 docs/tracks/pt/creating-accounts.md           |  12 +-
 docs/tracks/pt/creating-and-editing-users.md  |   4 +-
 docs/tracks/pt/creating-discount-coupons.md   |   8 +-
 docs/tracks/pt/creating-franchise-accounts.md |   4 +-
 ...ating-merchandising-rules-visual-editor.md |   4 +-
 .../pt/creating-or-editing-a-page-template.md |  19 ++-
 docs/tracks/pt/creating-regular-promotions.md |   4 +-
 docs/tracks/pt/credit-card-payment-flow.md    |   4 +-
 ...tor-and-dimensional-weight-calculations.md |   4 +-
 docs/tracks/pt/customer-identification.md     |   4 +-
 docs/tracks/pt/customizing-instore.md         |   4 +-
 docs/tracks/pt/customizing-instores-layout.md |   4 +-
 docs/tracks/pt/data-protection-roles.md       |   4 +-
 ...ne-payment-methods-displayed-on-instore.md |   4 +-
 ...fining-the-google-shopping-trade-policy.md |  12 +-
 .../pt/detaching-skus-by-specification.md     |   3 +-
 .../pt/enable-clustered-payment-conditions.md |  10 +-
 .../enabling-2-factor-authentication-login.md |  16 +-
 docs/tracks/pt/enabling-a-sales-rep-code.md   |  16 +-
 .../enabling-cart-transfer-between-devices.md |   4 +-
 .../enabling-order-filter-by-salesperson.md   |   8 +-
 .../pt/enabling-product-recommendations.md    |   4 +-
 ...g-the-remarks-field-in-the-order-screen.md |   8 +-
 docs/tracks/pt/exporting-an-order.md          |   4 +-
 docs/tracks/pt/extensions-hub-app-store.md    |   4 +-
 docs/tracks/pt/extensions-hub-partners.md     |   4 +-
 docs/tracks/pt/facebook-business-extension.md |   4 +-
 docs/tracks/pt/filters.md                     |  12 +-
 docs/tracks/pt/forcing-stock-availability.md  |   8 +-
 docs/tracks/pt/frontend-implementation.md     |   4 +-
 .../pt/getting-started-with-logistics.md      |  21 ++-
 docs/tracks/pt/go-live-process.md             |   4 +-
 docs/tracks/pt/go-live.md                     |   8 +-
 docs/tracks/pt/google-pay.md                  |  28 +---
 docs/tracks/pt/google-shopping-ads-install.md |   4 +-
 docs/tracks/pt/google-shopping-ads-set-up.md  |   8 +-
 docs/tracks/pt/google-shopping-marketplace.md |   4 +-
 .../how-a-split-payment-transaction-works.md  |   4 +-
 .../pt/how-clustered-conditions-work.md       |   4 +-
 .../pt/how-the-payments-module-works.md       |   4 +-
 ...nfigure-a-device-for-printout-the-order.md |   8 +-
 ...-and-edit-transactional-email-templates.md |   4 +-
 .../how-to-customize-the-observation-field.md |   4 +-
 docs/tracks/pt/how-vtex-support-works.md      |   4 +-
 ...uding-order-variables-in-email-template.md |   4 +-
 docs/tracks/pt/initial-setup.md               |  19 +--
 docs/tracks/pt/instore-basic-settings.md      |  12 +-
 docs/tracks/pt/instore-customizations.md      |   8 +-
 docs/tracks/pt/instore.md                     |   4 +-
 ...ating-instore-to-a-new-payment-acquirer.md |  12 +-
 .../pt/integrating-with-magazine-luiza.md     |   4 +-
 docs/tracks/pt/integration-overview.md        |   8 +-
 docs/tracks/pt/intelligent-synonyms.md        |   4 +-
 docs/tracks/pt/introduction-to-vtex.md        |   8 +-
 docs/tracks/pt/live-support.md                |   4 +-
 docs/tracks/pt/livelo-integration-overview.md |   3 +-
 .../pt/livelo-integration-registration.md     |   6 +-
 docs/tracks/pt/manage-skus-in-inventory.md    |   4 +-
 docs/tracks/pt/managing-accounts.md           |   8 +-
 .../pt/managing-customer-credit-invoices.md   |   8 +-
 docs/tracks/pt/managing-shipping-rates.md     |   4 +-
 ...-with-tiktok-for-business-in-vtex-admin.md |  13 +-
 ...s-variations-and-attributes-in-netshoes.md |  16 +-
 ...ro-categories-variations-and-attributes.md |   4 +-
 ...pping-product-categories-and-attributes.md |   4 +-
 ...rappi-product-categories-and-attributes.md |   4 +-
 .../pt/merchandising-rule-conditions.md       |   4 +-
 docs/tracks/pt/next-steps.md                  |   4 +-
 docs/tracks/pt/order-flow.md                  |  25 ++-
 ...oducts-and-freight-settings-in-netshoes.md |   6 +-
 .../pt/pickup-points-concept-definition.md    |   4 +-
 docs/tracks/pt/pickup-store.md                |   6 +-
 docs/tracks/pt/planning-the-go-live.md        |  28 +---
 docs/tracks/pt/pre-go-live.md                 |   4 +-
 .../pt/preco-fixo-definicao-de-conceito.md    |   4 +-
 docs/tracks/pt/printing-an-order-summary.md   |   4 +-
 .../product-group-registration-in-netshoes.md |   2 +-
 .../pt/promotions-for-specific-scenarios.md   |   8 +-
 docs/tracks/pt/rappi-integration-overview.md  |   8 +-
 .../pt/rappi-integration-registration.md      |   4 +-
 docs/tracks/pt/receivables-management.md      |   4 +-
 docs/tracks/pt/redirect.md                    |   4 +-
 .../pt/register-mercado-livre-integration.md  |   4 +-
 ...ter-the-barcode-of-the-skus-for-instore.md |   8 +-
 .../registering-the-carrefour-integration.md  |   9 +-
 .../registering-the-centauro-integration.md   |   6 +-
 docs/tracks/pt/registering-the-integration.md |  11 +-
 .../registering-the-netshoes-integration.md   |  18 +-
 .../regra-de-preco-definicao-de-conceito.md   |   4 +-
 docs/tracks/pt/relevance.md                   |   4 +-
 .../pt/reports-vtex-intelligent-search.md     |   4 +-
 ...eduled-deliveries-and-delivery-capacity.md |   6 +-
 .../pt/sending-product-data-to-dafiti.md      |  12 +-
 docs/tracks/pt/sending-products-to-amazon.md  |  22 +--
 .../tracks/pt/sending-products-to-facebook.md |  12 +-
 .../pt/sending-products-to-google-shopping.md |  12 +-
 docs/tracks/pt/set-a-price-for-the-sku.md     |   4 +-
 ...setting-up-a-marketplace-trade-policy-2.md |   3 +-
 .../setting-up-a-marketplace-trade-policy.md  |   3 +-
 docs/tracks/pt/setting-up-a-smart-campaign.md |   8 +-
 ...app-linking-for-payments-app-in-instore.md |  12 +-
 .../pt/setting-up-credit-direct-sale.md       |   4 +-
 .../tracks/pt/setting-up-debit-direct-sale.md |   4 +-
 docs/tracks/pt/setting-up-instore-as-a-pos.md |   4 +-
 .../pt/setting-up-payments-for-instore.md     |   7 +-
 docs/tracks/pt/setting-up-pick-up-points.md   |   4 +-
 docs/tracks/pt/setting-up-pix.md              |   4 +-
 ...s-template-description-in-mercado-livre.md |   8 +-
 docs/tracks/pt/setting-up-the-app.md          |  12 +-
 ...ting-up-the-cappta-acquirer-for-instore.md |  23 +--
 ...g-up-the-cielo-lio-acquirer-for-instore.md |   8 +-
 ...ting-up-the-logistics-for-mercado-livre.md |  22 +--
 .../setting-up-the-order-summary-printing.md  |  20 +--
 ...ng-up-the-pagar-me-acquirer-for-instore.md |   8 +-
 ...tting-up-the-sitef-acquirer-for-instore.md |  32 ++--
 ...tting-up-the-stone-acquirer-for-instore.md |   8 +-
 docs/tracks/pt/settings-on-via-marketplace.md |   4 +-
 docs/tracks/pt/settings.md                    |  12 +-
 ...pping-cart-using-instore-social-selling.md |   4 +-
 docs/tracks/pt/shipping-strategies.md         |   8 +-
 .../pt/specifications-concept-definition.md   |   8 +-
 docs/tracks/pt/subscription-orders.md         |   4 +-
 docs/tracks/pt/teste-1.md                     |   4 +-
 docs/tracks/pt/the-reservation.md             |   8 +-
 docs/tracks/pt/tiktok-for-business.md         |   4 +-
 docs/tracks/pt/unified-commerce.md            |   4 +-
 .../untitled-entry-2018-03-20-at-04-04-56.md  |   8 +-
 docs/tracks/pt/vtex-modules-i.md              |  24 +--
 docs/tracks/pt/vtex-modules-ii.md             |  12 +-
 docs/tracks/pt/vtex-platform-settings.md      |   8 +-
 .../what-are-clustered-payment-conditions.md  |   4 +-
 ...hat-are-permissions-and-access-profiles.md |   4 +-
 .../what-is-conversational-commerce-vtex.md   |   4 +-
 docs/tracks/pt/what-is-the-payment-split.md   |  16 +-
 docs/tracks/pt/what-is-vtex-payment.md        |   8 +-
 ...figure-in-wish-prior-to-the-integration.md |   2 +-
 ...th-vtex-before-starting-the-integration.md |  16 +-
 docs/tutorials/en/account-management.md       |  22 +--
 .../actions-for-vtex-marketplace-operation.md |   8 +-
 docs/tutorials/en/activating-new-vtex-cdn.md  |  12 +-
 docs/tutorials/en/activating-skus-in-bulk.md  |   7 +-
 .../en/active-campaign-suiteshare.md          |   4 +-
 ...s-support-to-the-integration-with-adyen.md |   4 +-
 .../adding-a-record-on-a-master-data-form.md  |  25 ++-
 docs/tutorials/en/adding-a-seller-beta.md     |   8 +-
 docs/tutorials/en/adding-a-seller.md          |   8 +-
 docs/tutorials/en/adding-an-attachment.md     |   8 +-
 docs/tutorials/en/adding-collections-cms.md   |  28 +---
 .../tutorials/en/additional-shipping-costs.md |  14 +-
 .../advertising-with-vtex-ad-network-beta.md  |   4 +-
 docs/tutorials/en/affiliates-program-app.md   |   8 +-
 ...mazon-multi-channel-fulfillment-mcf-app.md |  22 +--
 docs/tutorials/en/analytics.md                |   4 +-
 docs/tutorials/en/analyze-suiteshare.md       |   4 +-
 docs/tutorials/en/anapro-suiteshare.md        |   4 +-
 docs/tutorials/en/antifraud-provider.md       |   4 +-
 docs/tutorials/en/application-keys.md         |  20 +--
 ...roving-payment-of-the-bank-payment-slip.md |   8 +-
 docs/tutorials/en/apps-overview.md            |   4 +-
 docs/tutorials/en/assembly-options-app.md     |  12 +-
 docs/tutorials/en/assembly-options.md         |   8 +-
 docs/tutorials/en/audit.md                    |   4 +-
 docs/tutorials/en/authentication-page.md      |   4 +-
 ...user-and-password-on-the-rest-interface.md |   4 +-
 docs/tutorials/en/authentication.md           |   8 +-
 docs/tutorials/en/bank-reconciliations.md     |   4 +-
 .../become-a-certified-connector-partner.md   |   3 +-
 .../best-practices-against-virtual-attacks.md |   4 +-
 ...ces-for-accessing-the-store-without-www.md |   4 +-
 docs/tutorials/en/billing-module-overview.md  |   4 +-
 docs/tutorials/en/bitrix24.md                 |   4 +-
 docs/tutorials/en/black-friday-checklist.md   |   2 +-
 docs/tutorials/en/black-week.md               |   4 +-
 .../tutorials/en/brand-registration-fields.md |  19 ++-
 .../tutorials/en/call-to-action-suiteshare.md |   4 +-
 docs/tutorials/en/campaign-audiences-list.md  |   4 +-
 docs/tutorials/en/campaign-promotion.md       |   8 +-
 docs/tutorials/en/capture-form-suiteshare.md  |   4 +-
 docs/tutorials/en/carrier-working-hours.md    |   4 +-
 .../en/category-registration-fields.md        |  19 ++-
 ...egory-variations-and-attributes-mapping.md |  13 +-
 ...-seller-of-an-vtex-sales-app-order-beta.md |   4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |   6 +-
 ...ult-system-texts-displayed-in-the-store.md |   4 +-
 .../changing-items-from-a-complete-order.md   |   4 +-
 .../changing-the-total-cost-of-the-order.md   |   4 +-
 docs/tutorials/en/chat.md                     |   4 +-
 ...for-errors-or-problems-in-a-transaction.md |   4 +-
 docs/tutorials/en/checkout-vtex-overview.md   |   8 +-
 ...chitecture-or-an-additional-environment.md |   4 +-
 ...ount-franchise-account-or-seller-portal.md |   2 +-
 docs/tutorials/en/cms-folder-structure.md     |   8 +-
 .../en/collection-highlight-control.md        |   4 +-
 .../en/como-criar-usuario-webservice.md       |   8 +-
 .../como-funciona-a-integracao-da-netshoes.md | 156 +++++++++++-------
 ...-sistema-esta-sendo-renderizada-no-site.md |   4 +-
 .../en/conditions-builder-usage-examples.md   |   5 +-
 ...-accounts-with-multiple-official-stores.md |   4 +-
 docs/tutorials/en/configure-cartman.md        |   8 +-
 ...yee-benefits-using-master-data-clusters.md |  25 ++-
 .../en/configure-seller-regionalization.md    |   4 +-
 ...figure-template-in-smartcheckout-update.md |   8 +-
 .../tutorials/en/configuring-a-data-entity.md |   2 +-
 .../configuring-a-marketplace-trade-policy.md |   4 +-
 ...uring-a-pricing-rule-for-a-sales-policy.md |   4 +-
 ...nfiguring-a-santander-registered-boleto.md |   2 +-
 .../en/configuring-access-profiles-old.md     |   4 +-
 .../en/configuring-access-without-www.md      |   4 +-
 docs/tutorials/en/configuring-affiliates.md   |   4 +-
 docs/tutorials/en/configuring-affirm.md       |   4 +-
 docs/tutorials/en/configuring-banners.md      |   4 +-
 .../en/configuring-carriers-cut-off-time.md   |   4 +-
 .../en/configuring-cielo-acquirer.md          |   4 +-
 ...ng-clearsale-global-anti-fraud-solution.md |   4 +-
 .../en/configuring-clearsale-v3-antifraud.md  |  13 +-
 .../en/configuring-dns-pointing-to-vtex.md    |  20 +--
 ...nfiguring-domains-in-account-management.md |  14 +-
 docs/tutorials/en/configuring-greenlist.md    |   4 +-
 ...eal-payment-method-in-adyen-integration.md |   6 +-
 ...automatic-payment-settlement-time-frame.md |   8 +-
 ...guring-mercado-pagos-device-fingerprint.md |   4 +-
 .../en/configuring-openpay-payment-gateway.md |   4 +-
 ...-payment-with-adyenv3-in-vtex-sales-app.md |  12 +-
 .../en/configuring-payment-with-adyenv3.md    |  20 +--
 .../en/configuring-price-divergence-rule.md   |   8 +-
 ...guring-seller-allocation-for-buying-xky.md |   3 +-
 .../configuring-sign-in-with-apple-id-beta.md |   8 +-
 .../en/configuring-spin-pay-gateway.md        |   8 +-
 .../configuring-stripe-gateway-affiliation.md |  21 +--
 .../en/configuring-telesales-features.md      |   4 +-
 .../en/configuring-the-global-checkout.md     |   4 +-
 .../en/configuring-the-pickup-in-store.md     |   4 +-
 .../en/configuring-the-rede-acquirer.md       |   4 +-
 .../en/configuring-the-scheduled-delivery.md  |   4 +-
 .../en/configuring-the-store-domain.md        |   8 +-
 .../configuring-tuna-gateway-affiliation.md   |   4 +-
 .../en/configuring-vtex-marketplace.md        |   4 +-
 docs/tutorials/en/configuring-xml.md          |   4 +-
 docs/tutorials/en/coupons-beta.md             |   4 +-
 .../en/creating-a-campaign-audience.md        |  19 +--
 docs/tutorials/en/creating-a-coupon-beta.md   |   8 +-
 docs/tutorials/en/creating-a-coupon.md        |  24 +--
 ...nformation-using-master-data-newsletter.md |   2 +-
 .../en/creating-a-product-collection.md       |   4 +-
 .../en/creating-a-product-for-presale.md      |   8 +-
 .../en/creating-a-shipping-policy.md          |   4 +-
 .../en/creating-a-subscription-plan.md        |  12 +-
 docs/tutorials/en/creating-a-trade-policy.md  |   8 +-
 docs/tutorials/en/creating-a-type-of-list.md  |   4 +-
 .../en/creating-an-oauth2-authentication.md   |   4 +-
 ...h-promotional-price-using-a-price-table.md |   4 +-
 ...-apptokens-to-authenticate-integrations.md |   6 +-
 ...ustomer-and-address-forms-in-new-stores.md |  25 ++-
 docs/tutorials/en/creating-data-entity.md     |  25 ++-
 docs/tutorials/en/creating-landing-pages.md   |  10 +-
 ...ating-merchandising-rules-manual-editor.md |  16 +-
 ...-merchandising-rules-visual-editor-beta.md |   8 +-
 ...ating-merchandising-rules-visual-editor.md |   4 +-
 docs/tutorials/en/creating-pickup-points.md   |  12 +-
 ...eating-promotion-for-a-customer-cluster.md |   8 +-
 docs/tutorials/en/creating-roles.md           |   8 +-
 .../en/creating-service-for-a-sku.md          |   4 +-
 docs/tutorials/en/creating-synonyms.md        |   8 +-
 ...-files-structure-for-your-app-vtex-init.md |   4 +-
 .../en/creating-trigger-in-master-data.md     |   8 +-
 .../en/credit-card-basic-payment-flow.md      |   4 +-
 docs/tutorials/en/credit-control-overview.md  |   6 +-
 docs/tutorials/en/criar-um-produto-beta.md    |  12 +-
 docs/tutorials/en/crm-zen-suiteshare.md       |   4 +-
 docs/tutorials/en/custom-product-fields.md    |   4 +-
 docs/tutorials/en/customer-credit-overview.md |  16 +-
 .../en/customizar-a-toolbar-de-televendas.md  |   2 +-
 docs/tutorials/en/customize-suiteshare.md     |   4 +-
 ...omizing-the-checkout-confirmation-pages.md |   2 +-
 .../en/customizing-the-my-orders-section.md   |  20 +--
 .../en/customizing-your-stores-typography.md  |   8 +-
 docs/tutorials/en/data-entity.md              |  17 +-
 docs/tutorials/en/data-subject-rights.md      |   4 +-
 .../en/database-maintenance-full-cleanup.md   |  17 +-
 ...eactivating-and-reorganizing-categories.md |   4 +-
 .../en/declining-order-cancelation.md         |  21 +--
 docs/tutorials/en/deleting-a-category.md      |   2 +-
 docs/tutorials/en/deleting-customer-data.md   |   8 +-
 .../en/detaching-skus-by-specification.md     |   3 +-
 ...-end-for-the-list-feature-in-your-store.md |   8 +-
 .../en/direct-migration-magazine-luiza.md     |   4 +-
 docs/tutorials/en/disable-cloudflare-proxy.md |   4 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |   4 +-
 ...ic-relevance-in-intelligent-search-beta.md |   7 +-
 ...-field-on-profile-system-of-master-data.md |  25 ++-
 .../en/editing-my-data-suiteshare.md          |   4 +-
 .../en/enable-https-throughout-the-site.md    |   9 +-
 .../enabling-2-factor-authentication-login.md |  24 +--
 ...enabling-3ds2-for-redsys-v2-integration.md |   6 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |  12 +-
 .../en/enabling-payments-with-bitcoin.md      |   4 +-
 ...cking-number-on-orders-already-invoiced.md |   4 +-
 .../en/entering-tax-receipts-in-the-order.md  |   8 +-
 docs/tutorials/en/erasing-customer-data.md    |   8 +-
 .../tutorials/en/events-available-in-audit.md |   4 +-
 docs/tutorials/en/exact-sales-suiteshare.md   |   4 +-
 ...mporting-product-and-sku-specifications.md |   4 +-
 ...the-availability-notification-notify-me.md |   4 +-
 docs/tutorials/en/exporting-data.md           |   4 +-
 .../en/exporting-orders-in-orders-module.md   |   4 +-
 ...acebook-liberacao-de-dominio-suiteshare.md |   4 +-
 .../en/faq-security-restricted-content.md     |   4 +-
 .../en/fill-out-the-stock-spreadsheet.md      |   4 +-
 ...ing-in-fields-in-the-import-spreadsheet.md |  19 ++-
 ...-import-spreadsheets-fixed-price-fields.md |   2 +-
 docs/tutorials/en/filtering-all-orders.md     |   4 +-
 docs/tutorials/en/filters.md                  |  12 +-
 ...tplaces-and-sellers-in-the-vtex-network.md |   4 +-
 docs/tutorials/en/find-sellers.md             |  10 +-
 .../fromto-of-payment-means-on-webservice.md  |   8 +-
 docs/tutorials/en/geolocalizado-suiteshare.md |   4 +-
 docs/tutorials/en/geolocation-at-checkout.md  |   4 +-
 docs/tutorials/en/gift-card.md                |  23 +--
 ...od-practices-for-the-golive-of-my-store.md |  24 +--
 .../en/google-integration-warnings.md         |   4 +-
 docs/tutorials/en/google-pay-beta.md          |   4 +-
 .../en/hiring-the-security-certificate-sll.md |   4 +-
 ...how-can-i-change-the-domain-of-my-store.md |   4 +-
 ...how-can-i-create-a-field-in-master-data.md |   2 +-
 .../en/how-can-i-create-callcenter-user.md    |   4 +-
 .../how-can-i-create-cluster-of-customers.md  |  25 ++-
 ...e-newsletter-database-using-master-data.md |   4 +-
 .../en/how-change-order-works-beta.md         |   4 +-
 .../how-cnova-via-varejo-integration-works.md | 147 ++++++++++-------
 ...-inclusion-of-newsletter-in-master-data.md |   4 +-
 ...e-the-https-protocol-on-my-stores-pages.md |   9 +-
 .../tutorials/en/how-does-reservation-work.md |  12 +-
 ...th-multiple-items-work-in-mercado-livre.md |   4 +-
 .../tutorials/en/how-does-vtex-search-work.md |   6 +-
 ...-item-with-shipping-benefit-on-the-cart.md |   4 +-
 ...-the-platforms-operation-sla-determined.md |   4 +-
 ...he-platform-take-to-identify-my-payment.md |   4 +-
 docs/tutorials/en/how-my-account-works.md     |   4 +-
 .../en/how-order-authorization-workss.md      |   4 +-
 .../en/how-product-name-control-works.md      |   4 +-
 .../en/how-promotion-competition-works.md     |   6 +-
 ...portional-shipping-costs-are-calculated.md |   4 +-
 .../en/how-shipping-calculation-works.md      |  15 +-
 .../en/how-the-carrefour-integration-works.md |  32 ++--
 .../how-the-integration-with-buscape-works.md |  30 ++--
 ...en-websites-and-business-policies-works.md |   4 +-
 ...ess-to-the-order-for-invoicing-purposes.md |   4 +-
 ...ormation-to-the-order-and-manipulate-it.md |   4 +-
 .../en/how-to-capture-the-ip-of-an-order.md   |   8 +-
 .../tutorials/en/how-to-change-order-items.md |   4 +-
 .../tutorials/en/how-to-change-orders-beta.md |   8 +-
 ...he-order-of-payment-methods-at-checkout.md |   4 +-
 ...e-sorting-of-delivery-types-in-the-cart.md |   4 +-
 .../en/how-to-configure-a-custom-payment.md   |   4 +-
 ...re-mercado-pago-pro-as-a-payment-method.md |   4 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |   8 +-
 .../en/how-to-configure-payment-conditions.md |  12 +-
 .../en/how-to-configure-subscriptions.md      |  12 +-
 ...figure-the-fingerprint-device-for-stelo.md |   8 +-
 ...ng-feed-and-the-google-product-taxonomy.md |   2 +-
 .../en/how-to-create-a-page-template.md       |  22 +--
 docs/tutorials/en/how-to-create-a-product.md  |  20 +--
 ...eate-a-promotion-with-limitation-of-use.md |   4 +-
 .../en/how-to-create-a-shelf-template.md      |  19 ++-
 ...how-to-create-a-subscription-attachment.md |  12 +-
 .../en/how-to-create-conditional-prices.md    |   5 +-
 ...ow-to-define-the-url-for-a-product-page.md |   8 +-
 .../en/how-to-download-the-vtex-invoices.md   |   2 +-
 .../en/how-to-export-a-product-spreadsheet.md |   4 +-
 docs/tutorials/en/how-to-find-an-sku-id.md    |   4 +-
 ...import-pickup-points-using-spreadsheets.md |   4 +-
 ...de-a-registration-on-a-master-data-form.md |  25 ++-
 ...reverse-proxy-in-front-of-vtex-services.md |  22 ++-
 .../en/how-to-integrate-vtex-using-zapier.md  |   2 +-
 .../en/how-to-integrate-with-dafiti.md        |  21 +--
 .../en/how-to-integrate-with-facebook.md      |   8 +-
 docs/tutorials/en/how-to-make-transfers.md    |   4 +-
 .../en/how-to-migrate-a-store-to-pricing.md   |   4 +-
 ...o-modify-details-of-customers-addresses.md |  25 ++-
 ...optimize-searches-with-substitute-words.md |   8 +-
 ...o-place-a-regular-order-using-vtex-apis.md |   3 +-
 .../en/how-to-rank-the-best-selling-items.md  |   4 +-
 ...ister-your-salespersons-on-vtex-instore.md |   4 +-
 ...how-to-request-receivables-anticipation.md |   4 +-
 ...to-schedule-prices-for-a-range-of-hours.md |  12 +-
 .../en/how-to-set-up-fingerprint-for-payu.md  |   6 +-
 ...r-to-accept-payments-with-adyen-at-vtex.md |   4 +-
 ...t-up-the-device-fingerprint-for-braspag.md |   6 +-
 ...set-up-the-indeva-scheduled-appointment.md |   4 +-
 ...e-for-pick-up-field-in-smartcheckout-v6.md |   8 +-
 ...w-to-set-up-your-store-on-seller-portal.md |   6 +-
 ...s-4-in-vtex-stores-in-legacy-cms-portal.md |   4 +-
 ...to-setup-google-analytics-in-vtex-store.md |   4 +-
 ...how-to-turn-my-store-website-into-a-pwa.md |   4 +-
 .../en/how-to-use-messages-on-your-io-apps.md |   8 +-
 .../en/how-to-use-the-index-report.md         |   4 +-
 .../en/how-to-use-the-meta-tags-control.md    |   4 +-
 .../how-to-use-the-search-result-control.md   |   4 +-
 ...ow-to-use-the-unavailable-product-class.md |   4 +-
 .../en/how-to-view-the-orders-details.md      |   4 +-
 ...ith-different-layouts-for-the-same-page.md |   4 +-
 docs/tutorials/en/how-trade-policies-work.md  |   4 +-
 docs/tutorials/en/hubspot-suiteshare.md       |   4 +-
 .../en/i-forgot-my-password-suiteshare.md     |   4 +-
 docs/tutorials/en/image-compression.md        |   4 +-
 docs/tutorials/en/image-widget.md             |  12 +-
 .../en/import-customer-data-brazil.md         |   7 +-
 .../en/importing-amazon-classic-fba-orders.md |   4 +-
 .../en/importing-data-into-master-data.md     |   8 +-
 .../en/importing-images-from-a-spreadsheet.md |  37 ++---
 .../en/importing-the-shipping-spreadsheet.md  |  16 +-
 ...les-in-the-transactional-email-template.md |   4 +-
 docs/tutorials/en/indexes-in-master-data.md   |   9 +-
 ...stalling-the-widget-with-gtm-suiteshare.md |   4 +-
 docs/tutorials/en/integrate-with-carrefour.md |   4 +-
 docs/tutorials/en/integrating-with-amazon.md  |  16 +-
 .../en/integrating-with-buscape-bp.md         |   4 +-
 .../en/integrating-with-mercado-livre.md      |  20 +--
 .../tutorials/en/integrating-with-netshoes.md |  21 +--
 .../en/integrating-with-viavarejo-cnova.md    |   4 +-
 docs/tutorials/en/integrating-with-walmart.md |   8 +-
 ...etplace-and-vtex-seller-catalog-updates.md |  26 ++-
 ...en-non-vtex-marketplace-and-vtex-seller.md |  18 +-
 ...ormation-for-use-in-an-external-service.md |   8 +-
 ...egration-guide-for-erps-express-catalog.md |   2 +-
 ...integration-guide-for-erps-full-catalog.md |   2 +-
 ...laces-marketplace-non-vtex-with-payment.md |   4 +-
 ...e-for-marketplaces-marketplace-non-vtex.md |   4 +-
 ...rketplaces-seller-non-vtex-with-payment.md |   4 +-
 ...-guide-for-marketplaces-seller-non-vtex.md |   4 +-
 .../en/integration-guide-for-marketplaces.md  |   6 +-
 docs/tutorials/en/integration-interfaces.md   |   4 +-
 .../en/integration-with-google-tag-manager.md |   8 +-
 ...lligent-search-synonym-suggestions-beta.md |   4 +-
 docs/tutorials/en/intelligent-synonyms.md     |   4 +-
 docs/tutorials/en/interaction-details.md      |   8 +-
 ...erpreting-the-data-of-the-oms-order-bar.md |   4 +-
 .../tutorials/en/introduction-to-vtex-apis.md |   4 +-
 docs/tutorials/en/inventory-update-history.md |   4 +-
 docs/tutorials/en/kit-registration.md         |   4 +-
 .../tutorials/en/license-manager-resources.md |   6 +-
 ...t-method-through-checkout-customization.md |   2 +-
 ...-the-store-by-means-of-the-sales-policy.md |  25 ++-
 ...-the-store-by-means-of-the-trade-policy.md |  25 ++-
 docs/tutorials/en/links-suiteshare.md         |   4 +-
 docs/tutorials/en/lista-da-vez.md             |   4 +-
 docs/tutorials/en/magento-suiteshare.md       |   4 +-
 .../en/manage-the-sales-comissions-report.md  |  20 +--
 .../en/managing-content-per-binding.md        |   4 +-
 .../tutorials/en/managing-content-versions.md |  14 +-
 .../en/managing-delivery-capacity-beta.md     |  12 +-
 .../en/managing-delivery-capacity.md          |   6 +-
 docs/tutorials/en/managing-http-headers.md    |   4 +-
 docs/tutorials/en/managing-loading-docks.md   |  27 ++-
 .../en/managing-page-and-template-content.md  |  28 +---
 docs/tutorials/en/managing-pages.md           |   4 +-
 docs/tutorials/en/managing-projects.md        |   4 +-
 .../en/managing-redirects-per-binding.md      |  12 +-
 .../en/managing-shipping-policies.md          |   4 +-
 docs/tutorials/en/managing-shipping-rates.md  |   4 +-
 .../en/managing-singleton-content-types.md    |  16 +-
 docs/tutorials/en/managing-stock-items.md     |  12 +-
 docs/tutorials/en/managing-users.md           |   4 +-
 docs/tutorials/en/managing-warehouses.md      |  31 ++--
 ...-classes-and-methods-used-on-webservice.md |   8 +-
 ...tegories-and-brands-for-the-marketplace.md |  10 +-
 .../en/marketplace-invited-sellers.md         |   6 +-
 .../en/marketplace-strategies-at-vtex.md      |  22 +--
 .../en/marketplaces-and-integrations.md       |   6 +-
 docs/tutorials/en/master-data-v2.md           |   3 +-
 docs/tutorials/en/master-data.md              |   8 +-
 .../en/match-offers-mercado-livre.md          |   4 +-
 docs/tutorials/en/maximum-price-per-item.md   |   8 +-
 docs/tutorials/en/media-overview.md           |  20 +--
 docs/tutorials/en/mercado-libre-size-chart.md |   4 +-
 .../en/merchandising-rule-conditions.md       |   4 +-
 docs/tutorials/en/meta-tags-suiteshare.md     |   4 +-
 ...ng-to-the-new-version-of-smart-checkout.md |   4 +-
 docs/tutorials/en/mode-off-faq.md             |   7 +-
 docs/tutorials/en/moskit-suiteshare.md        |   4 +-
 ...moving-order-to-start-handling-shipping.md |   4 +-
 .../en/multilevel-omnichannel-inventory.md    |  16 +-
 .../my-orders-in-mercado-libre-have-errors.md |   4 +-
 .../en/my-store-order-was-not-created.md      |   4 +-
 docs/tutorials/en/navigation.md               |  10 +-
 .../en/new-google-shopping-api-integration.md |   4 +-
 docs/tutorials/en/new-my-orders-area.md       |  14 +-
 docs/tutorials/en/offer-details.md            |   8 +-
 docs/tutorials/en/offer-management.md         |   8 +-
 docs/tutorials/en/offer-quality-filters.md    |   8 +-
 docs/tutorials/en/offer-status.md             |  12 +-
 docs/tutorials/en/opening-hours-suiteshare.md |   4 +-
 .../tutorials/en/operational-capacity-beta.md |  12 +-
 ...ization-of-shipping-options-at-checkout.md |   8 +-
 .../en/order-allocation-algorithm-beta.md     |   4 +-
 ...-cancellation-requested-by-the-customer.md |   8 +-
 docs/tutorials/en/order-flow-and-status.md    |  37 ++---
 docs/tutorials/en/order-replacement.md        |  14 +-
 .../en/order-split-and-delivery-split.md      |   4 +-
 docs/tutorials/en/order-to-delivery.md        |   4 +-
 .../en/order-transactional-email-templates.md |   4 +-
 .../en/orders-management-feed-v3-setup.md     |  28 +---
 ...rrors-in-marketplace-integration-orders.md |   4 +-
 .../tutorials/en/payment-provider-protocol.md |  41 ++---
 .../en/payments-in-vtex-marketplaces.md       |   8 +-
 .../en/payu-romania-refund-details.md         |   4 +-
 ...ration-testing-and-vulnerability-notice.md |  28 +---
 ...kup-points-for-subscription-orders-beta.md |   8 +-
 .../pickup-points-for-subscription-orders.md  |   4 +-
 docs/tutorials/en/pickup-points.md            |   2 +-
 docs/tutorials/en/pipedrive-suiteshare.md     |   4 +-
 docs/tutorials/en/piperun-suiteshare.md       |   4 +-
 .../en/planner-actions-on-releases-beta.md    |  12 +-
 .../en/planner-calendar-page-beta.md          |   8 +-
 .../en/planner-release-concept-beta.md        |   8 +-
 .../en/planner-releases-page-beta.md          |   8 +-
 docs/tutorials/en/predefined-roles.md         |  12 +-
 docs/tutorials/en/price-divergence-rule.md    |   8 +-
 .../en/price-divergence-rules-beta.md         |   8 +-
 docs/tutorials/en/product-list.md             |   2 +-
 .../en/product-registration-fields.md         |  23 ++-
 docs/tutorials/en/products-and-skus-beta.md   |   8 +-
 docs/tutorials/en/promotions-beta.md          |  20 +--
 .../tutorials/en/promotions-simulator-beta.md |  12 +-
 docs/tutorials/en/promotions-simulator.md     |   4 +-
 docs/tutorials/en/qr-code-suiteshare.md       |   4 +-
 .../en/querying-data-on-master-data.md        |   2 +-
 docs/tutorials/en/rdstation-crm-suiteshare.md |   4 +-
 docs/tutorials/en/rdstation-suiteshare.md     |   4 +-
 docs/tutorials/en/received-skus-beta.md       |  36 +---
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |   8 +-
 .../en/redirect-from-other-addresses.md       |   4 +-
 .../en/redirection-from-other-addresses.md    |   4 +-
 docs/tutorials/en/redirects.md                |   4 +-
 docs/tutorials/en/regionalization-beta.md     |   8 +-
 .../en/registering-a-products-base-price.md   |   8 +-
 docs/tutorials/en/registering-geolocation.md  |   7 +-
 docs/tutorials/en/registering-holidays.md     |   8 +-
 ...-with-nominal-discount-based-on-formula.md |   8 +-
 docs/tutorials/en/releases-module-beta.md     |   4 +-
 docs/tutorials/en/releases-overview.md        |   8 +-
 docs/tutorials/en/relevance-rules.md          |   4 +-
 docs/tutorials/en/remarketing.md              |   4 +-
 ...request-headers-must-only-contain-ascii.md |   4 +-
 ...l-data-under-international-data-privacy.md |   8 +-
 .../responsibilities-in-the-vtex-ecosystem.md |   4 +-
 docs/tutorials/en/returning-order-items.md    |  19 ++-
 docs/tutorials/en/risk-assessment.md          |   4 +-
 docs/tutorials/en/roles.md                    |   8 +-
 .../sales-associate-code-field-at-checkout.md |  16 +-
 docs/tutorials/en/sales-funnel-suiteshare.md  |   4 +-
 docs/tutorials/en/sales-performance.md        |   4 +-
 docs/tutorials/en/scheduled-delivery.md       |  15 +-
 .../scheduling-features-for-special-events.md |   4 +-
 docs/tutorials/en/scheduling-prices.md        |   4 +-
 docs/tutorials/en/schemas-on-master-data.md   |   2 +-
 docs/tutorials/en/search-behavior.md          |   8 +-
 .../tutorials/en/search-by-geo-coordinates.md |   3 +-
 docs/tutorials/en/search-navigator-control.md |  26 +--
 docs/tutorials/en/search-parameters.md        |   4 +-
 .../en/searching-for-events-on-audit.md       |  12 +-
 docs/tutorials/en/searching-for-old-orders.md |   4 +-
 .../en/searching-for-orders-in-oms.md         |   4 +-
 docs/tutorials/en/security-certificate-ssl.md |   4 +-
 docs/tutorials/en/security-monitor.md         |   4 +-
 docs/tutorials/en/seletivo.md                 |   4 +-
 ...reating-an-account-in-the-seller-portal.md |   4 +-
 docs/tutorials/en/seller-management.md        |   4 +-
 docs/tutorials/en/seller-portal-promotions.md |   4 +-
 .../en/seller-portal-shared-products.md       |   2 +-
 ...abel-payment-methods-to-the-marketplace.md |   4 +-
 ...es-and-bags-attributes-to-mercado-livre.md |   8 +-
 .../en/sending-sku-attributes-to-amazon.md    |   4 +-
 docs/tutorials/en/sent-offers-beta.md         |   4 +-
 .../en/sent-offers-buybox-opportunities.md    |  12 +-
 docs/tutorials/en/sequencial-suiteshare.md    |   4 +-
 ...et-up-alelo-payment-method-for-cielo-v3.md |   8 +-
 .../setting-up-3ds-2-authentication-flow.md   |   8 +-
 .../en/setting-up-a-personal-gift-message.md  |   4 +-
 .../en/setting-up-abandoned-carts.md          |  14 +-
 .../en/setting-up-alternative-accounts.md     |   4 +-
 .../tutorials/en/setting-up-amazonpay-beta.md |   4 +-
 ...app-linking-for-payments-app-in-instore.md |   8 +-
 docs/tutorials/en/setting-up-b2b-on-vtex.md   |   8 +-
 .../en/setting-up-conductor-gateway.md        |   2 +-
 ...ayments-using-mercadopago-latin-america.md |   4 +-
 .../en/setting-up-cybersource-antifraud.md    |   8 +-
 .../en/setting-up-cybersource-gateway.md      |  15 +-
 .../en/setting-up-decidir-gateway.md          |   4 +-
 ...etting-up-device-fingerprint-for-niubiz.md |  12 +-
 .../en/setting-up-firstdata-acquirer.md       |   2 +-
 .../en/setting-up-future-inventory.md         |  15 +-
 ...-itau-registered-ticket-itau-registrado.md |   2 +-
 ...ow-y-klarna-pay-later-as-payment-method.md |   8 +-
 ...o-offline-and-wallet-as-payment-methods.md |   4 +-
 .../setting-up-mercadopagov1-sub-acquirer.md  |   6 +-
 .../en/setting-up-merchant-id-in-apple-pay.md |  12 +-
 ...g-up-mundipagg-fraud-prevention-gateway.md |   2 +-
 .../en/setting-up-mundipagg-gateway.md        |   2 +-
 docs/tutorials/en/setting-up-my-account.md    |   4 +-
 .../en/setting-up-nethone-antifraud.md        |   8 +-
 .../en/setting-up-nexxpago-gateway.md         |   2 +-
 docs/tutorials/en/setting-up-nps-gateway.md   |   2 +-
 ...ne-payment-conditions-using-mercadopago.md |   4 +-
 .../en/setting-up-pagarmev2-gateway.md        |   4 +-
 .../en/setting-up-pagbrasil-gateway.md        |   2 +-
 .../en/setting-up-paghiper-gateway.md         |   2 +-
 .../en/setting-up-payment-with-paypal.md      |   2 +-
 .../en/setting-up-paymentez-gateway.md        |   2 +-
 .../en/setting-up-payments-with-alignet.md    |   2 +-
 .../en/setting-up-payments-with-apple-pay.md  |   8 +-
 ...setting-up-payments-with-cieloecommerce.md |   4 +-
 .../setting-up-payments-with-credimarcas.md   |   4 +-
 .../en/setting-up-payments-with-itau-rede.md  |   8 +-
 .../en/setting-up-payments-with-iugu.md       |  12 +-
 .../en/setting-up-payments-with-koin.md       |   2 +-
 .../setting-up-payments-with-mercado-pago.md  |   4 +-
 .../setting-up-payments-with-notes-payable.md |   4 +-
 .../en/setting-up-payments-with-nuvei.md      |   8 +-
 .../en/setting-up-payments-with-pagosweb.md   |   2 +-
 .../en/setting-up-payments-with-payclub.md    |   2 +-
 .../en/setting-up-payments-with-promissory.md |   4 +-
 .../en/setting-up-payments-with-pse.md        |   3 +-
 .../en/setting-up-payments-with-stelo.md      |   2 +-
 ...g-up-payments-with-store-card-cobranded.md |   8 +-
 docs/tutorials/en/setting-up-paypal-plus.md   |   2 +-
 docs/tutorials/en/setting-up-payu-gateway.md  |   2 +-
 .../en/setting-up-payu-global-gateway.md      |   3 +-
 .../tutorials/en/setting-up-payzen-gateway.md |   2 +-
 .../en/setting-up-place2pay-gateway.md        |   2 +-
 ...rice-and-availability-of-skus-by-region.md |  11 +-
 ...ting-up-price-tables-for-specific-users.md |  17 +-
 ...setting-up-rede-acquirer-with-erederest.md |   6 +-
 ...up-seller-white-label-as-a-pickup-point.md |   8 +-
 docs/tutorials/en/setting-up-shipment.md      |   4 +-
 .../setting-up-sitef-gateway-with-pre-auth.md |   2 +-
 docs/tutorials/en/setting-up-sitef-gateway.md |   2 +-
 .../en/setting-up-sub-acquirer-stelo.md       |   2 +-
 .../en/setting-up-the-global-category.md      |  16 +-
 .../setting-up-the-logistics-for-instore.md   |   4 +-
 .../en/setting-up-the-moip-sub-acquirer.md    |   8 +-
 .../en/setting-up-the-notify-me-option.md     |   4 +-
 ...up-the-sales-funnel-on-google-analytics.md |  63 +++----
 .../en/setting-up-the-tnspay-gateway.md       |   2 +-
 .../setting-up-the-type-of-interest-rate.md   |   4 +-
 docs/tutorials/en/setting-up-triggers.md      |   4 +-
 docs/tutorials/en/setup-safetypay.md          |   2 +-
 docs/tutorials/en/sharpspring-suiteshare.md   |   4 +-
 docs/tutorials/en/shipping-options-beta.md    |   4 +-
 docs/tutorials/en/shipping-rate-template.md   |  16 +-
 docs/tutorials/en/shipping-rates.md           |  12 +-
 docs/tutorials/en/shipping-simulation.md      |  14 +-
 docs/tutorials/en/shopify-suiteshare.md       |   4 +-
 docs/tutorials/en/sku-bindings.md             |   4 +-
 docs/tutorials/en/sku-registration-fields.md  |   8 +-
 ...rrors-in-marketplace-integration-orders.md |   4 +-
 ...-customer-information-automatic-fill-in.md |   4 +-
 ...martcheckout-v5-general-characteristics.md |   4 +-
 docs/tutorials/en/special-conditions.md       |   4 +-
 docs/tutorials/en/split-payment.md            |   8 +-
 docs/tutorials/en/store-overview-beta.md      |   7 +-
 docs/tutorials/en/subscription-plans.md       |   8 +-
 docs/tutorials/en/table-of-base-prices.md     |   4 +-
 docs/tutorials/en/telesales-toolbar.md        |   5 +-
 .../en/testing-webservice-using-soapui.md     |  18 +-
 ...-into-packages-with-separate-deliveries.md |   4 +-
 .../en/the-risk-assessment-process.md         |   4 +-
 docs/tutorials/en/total-shipping-cost.md      |   6 +-
 .../en/tracking-your-sales-analytics.md       |   2 +-
 ...understanding-competition-of-promotions.md |   6 +-
 .../en/understanding-how-indexation-works.md  |   9 +-
 .../en/understanding-incomplete-orders.md     |   4 +-
 .../understanding-the-conversation-tracker.md |   4 +-
 .../understanding-the-cubic-weight-factor.md  |   4 +-
 .../understanding-the-updating-of-the-xml.md  |   2 +-
 .../en/understanding-vtex-matcher-scoring.md  |   4 +-
 ...nderstanding-vtexs-email-capture-system.md |   8 +-
 .../en/updating-prices-in-marketplaces.md     |   4 +-
 docs/tutorials/en/url-mapping-301-redirect.md |   8 +-
 ...rol-of-component-layout-and-positioning.md |   4 +-
 ...-track-browsing-sessions-in-vtex-stores.md |   4 +-
 docs/tutorials/en/using-tools-html.md         |   2 +-
 docs/tutorials/en/vtex-ad-network-beta.md     |   7 +-
 docs/tutorials/en/vtex-admin-start-here.md    |   4 +-
 docs/tutorials/en/vtex-agreement.md           |   4 +-
 ...vtex-dashboard-guide-for-black-week-faq.md |  16 +-
 ...gent-search-multilanguage-settings-beta.md |  16 +-
 .../en/vtex-pick-and-pack-fulfillment.md      |  25 +--
 .../en/vtex-pick-and-pack-last-mile.md        |  20 +--
 .../tutorials/en/vtex-pick-and-pack-mobile.md |  22 +--
 docs/tutorials/en/vtex-shield.md              |   8 +-
 .../en/vtex-shipping-network-dashboard.md     |   4 +-
 docs/tutorials/en/vtex-status-page.md         |   4 +-
 docs/tutorials/en/vtex-suiteshare.md          |   4 +-
 docs/tutorials/en/vtex-support-apac.md        |   4 +-
 docs/tutorials/en/vtex-tracking-holidays.md   |   4 +-
 docs/tutorials/en/warehouse.md                |  31 ++--
 .../en/web-application-firewall-waf.md        |   4 +-
 ...ements-to-start-developing-with-vtex-io.md |   4 +-
 ...-utm-source-utm-campaign-and-utm-medium.md |   8 +-
 .../en/what-is-a-franchise-account.md         |  19 +--
 docs/tutorials/en/what-is-a-marketplace.md    |   4 +-
 docs/tutorials/en/what-is-an-affiliate.md     |   4 +-
 ...rand-gateway-and-sub-acquirer-in-brazil.md |   4 +-
 ...d-considered-for-calculating-my-billing.md |   4 +-
 ...s-the-purpose-of-the-customized-control.md |   4 +-
 docs/tutorials/en/what-is-the-shared-cart.md  |  12 +-
 docs/tutorials/en/what-is-the-sponsor-user.md |   4 +-
 docs/tutorials/en/what-is-vtex-io.md          |   4 +-
 ...d-i-group-products-in-the-same-shipment.md |   4 +-
 .../en/white-label-sellers-selection.md       |   4 +-
 ...stered-bank-slip-require-authentication.md |   4 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  25 ++-
 docs/tutorials/en/widget.md                   |   4 +-
 docs/tutorials/en/wix-suiteshare.md           |   4 +-
 docs/tutorials/en/wordpress-suiteshare.md     |   4 +-
 .../en/working-with-master-data-rest-api.md   |   2 +-
 ...ing-an-effective-ticket-to-vtex-support.md |   6 +-
 docs/tutorials/en/zapier-suiteshare.md        |   4 +-
 docs/tutorials/es/account-management.md       |  22 +--
 .../actions-for-vtex-marketplace-operation.md |   8 +-
 docs/tutorials/es/activating-new-vtex-cdn.md  |   8 +-
 docs/tutorials/es/activating-skus-in-bulk.md  |   7 +-
 .../es/active-campaign-suiteshare.md          |   4 +-
 ...s-support-to-the-integration-with-adyen.md |   4 +-
 .../adding-a-record-on-a-master-data-form.md  |  25 ++-
 docs/tutorials/es/adding-a-seller-beta.md     |   8 +-
 docs/tutorials/es/adding-a-seller.md          |   8 +-
 docs/tutorials/es/adding-an-attachment.md     |   8 +-
 docs/tutorials/es/adding-collections-cms.md   |  16 +-
 .../tutorials/es/additional-shipping-costs.md |  14 +-
 .../advertising-with-vtex-ad-network-beta.md  |   4 +-
 docs/tutorials/es/affiliates-program-app.md   |   8 +-
 ...mazon-multi-channel-fulfillment-mcf-app.md |  20 +--
 docs/tutorials/es/analytics.md                |   4 +-
 docs/tutorials/es/analyze-suiteshare.md       |   4 +-
 docs/tutorials/es/anapro-suiteshare.md        |   4 +-
 docs/tutorials/es/antifraud-provider.md       |   4 +-
 docs/tutorials/es/application-keys.md         |  20 +--
 ...roving-payment-of-the-bank-payment-slip.md |   8 +-
 docs/tutorials/es/apps-overview.md            |   4 +-
 docs/tutorials/es/assembly-options-app.md     |  12 +-
 docs/tutorials/es/assembly-options.md         |   8 +-
 docs/tutorials/es/audit.md                    |   4 +-
 docs/tutorials/es/authentication-page.md      |   4 +-
 ...user-and-password-on-the-rest-interface.md |   4 +-
 docs/tutorials/es/authentication.md           |   8 +-
 docs/tutorials/es/bank-reconciliations.md     |   4 +-
 .../become-a-certified-connector-partner.md   |   4 +-
 .../best-practices-against-virtual-attacks.md |   4 +-
 ...ces-for-accessing-the-store-without-www.md |   4 +-
 docs/tutorials/es/billing-module-overview.md  |   4 +-
 docs/tutorials/es/bitrix24.md                 |   4 +-
 docs/tutorials/es/black-friday-checklist.md   |   2 +-
 docs/tutorials/es/black-week.md               |   4 +-
 .../tutorials/es/brand-registration-fields.md |  19 ++-
 .../tutorials/es/call-to-action-suiteshare.md |   4 +-
 docs/tutorials/es/campaign-audiences-list.md  |   4 +-
 docs/tutorials/es/campaign-promotion.md       |   8 +-
 docs/tutorials/es/capture-form-suiteshare.md  |   4 +-
 docs/tutorials/es/carrier-working-hours.md    |   4 +-
 .../es/category-registration-fields.md        |  19 ++-
 ...egory-variations-and-attributes-mapping.md |   9 +-
 ...-seller-of-an-vtex-sales-app-order-beta.md |   4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |   4 +-
 ...ult-system-texts-displayed-in-the-store.md |   5 +-
 .../changing-items-from-a-complete-order.md   |   4 +-
 .../changing-the-total-cost-of-the-order.md   |   4 +-
 docs/tutorials/es/chat.md                     |   4 +-
 ...for-errors-or-problems-in-a-transaction.md |   4 +-
 docs/tutorials/es/checkout-vtex-overview.md   |   8 +-
 ...chitecture-or-an-additional-environment.md |   4 +-
 ...ount-franchise-account-or-seller-portal.md |   2 +-
 docs/tutorials/es/cms-folder-structure.md     |   9 +-
 .../es/collection-highlight-control.md        |   4 +-
 .../es/como-criar-usuario-webservice.md       |   8 +-
 .../como-funciona-a-integracao-da-netshoes.md | 156 +++++++++++-------
 ...-sistema-esta-sendo-renderizada-no-site.md |   4 +-
 .../es/conditions-builder-usage-examples.md   |   5 +-
 ...-accounts-with-multiple-official-stores.md |   4 +-
 docs/tutorials/es/configure-cartman.md        |   8 +-
 ...yee-benefits-using-master-data-clusters.md |  25 ++-
 .../es/configure-seller-regionalization.md    |   4 +-
 ...figure-template-in-smartcheckout-update.md |   8 +-
 .../tutorials/es/configuring-a-data-entity.md |   2 +-
 .../configuring-a-marketplace-trade-policy.md |   4 +-
 ...uring-a-pricing-rule-for-a-sales-policy.md |   4 +-
 ...nfiguring-a-santander-registered-boleto.md |   2 +-
 .../es/configuring-access-profiles-old.md     |   4 +-
 .../es/configuring-access-without-www.md      |   4 +-
 docs/tutorials/es/configuring-affiliates.md   |   4 +-
 docs/tutorials/es/configuring-affirm.md       |   4 +-
 docs/tutorials/es/configuring-banners.md      |   4 +-
 ...port-for-organizations-and-cost-centers.md |   4 +-
 .../es/configuring-carriers-cut-off-time.md   |   6 +-
 .../es/configuring-cielo-acquirer.md          |   4 +-
 ...ng-clearsale-global-anti-fraud-solution.md |   4 +-
 .../es/configuring-clearsale-v3-antifraud.md  |  11 +-
 .../es/configuring-dns-pointing-to-vtex.md    |  24 +--
 ...nfiguring-domains-in-account-management.md |  14 +-
 ...eal-payment-method-in-adyen-integration.md |   6 +-
 ...automatic-payment-settlement-time-frame.md |   8 +-
 ...guring-mercado-pagos-device-fingerprint.md |   4 +-
 .../es/configuring-openpay-payment-gateway.md |   4 +-
 ...-payment-with-adyenv3-in-vtex-sales-app.md |  12 +-
 .../es/configuring-payment-with-adyenv3.md    |  20 +--
 .../es/configuring-price-divergence-rule.md   |   8 +-
 ...guring-seller-allocation-for-buying-xky.md |   4 +-
 .../configuring-sign-in-with-apple-id-beta.md |   8 +-
 .../es/configuring-spin-pay-gateway.md        |   8 +-
 .../configuring-stripe-gateway-affiliation.md |  21 +--
 .../es/configuring-telesales-features.md      |   4 +-
 .../es/configuring-the-global-checkout.md     |   4 +-
 .../es/configuring-the-pickup-in-store.md     |   4 +-
 .../es/configuring-the-rede-acquirer.md       |   4 +-
 .../es/configuring-the-scheduled-delivery.md  |   4 +-
 .../es/configuring-the-store-domain.md        |   8 +-
 .../configuring-tuna-gateway-affiliation.md   |   4 +-
 .../es/configuring-vtex-marketplace.md        |   4 +-
 docs/tutorials/es/configuring-xml.md          |   4 +-
 docs/tutorials/es/coupons-beta.md             |   4 +-
 .../es/creating-a-campaign-audience.md        |  19 +--
 docs/tutorials/es/creating-a-coupon-beta.md   |   8 +-
 docs/tutorials/es/creating-a-coupon.md        |  24 +--
 .../es/creating-a-product-collection.md       |   4 +-
 .../es/creating-a-product-for-presale.md      |   8 +-
 .../es/creating-a-shipping-policy.md          |   4 +-
 .../es/creating-a-subscription-plan.md        |  12 +-
 docs/tutorials/es/creating-a-trade-policy.md  |   8 +-
 docs/tutorials/es/creating-a-type-of-list.md  |   4 +-
 .../es/creating-an-oauth2-authentication.md   |   4 +-
 ...h-promotional-price-using-a-price-table.md |   4 +-
 ...ustomer-and-address-forms-in-new-stores.md |  25 ++-
 docs/tutorials/es/creating-data-entity.md     |  25 ++-
 docs/tutorials/es/creating-landing-pages.md   |   9 +-
 ...ating-merchandising-rules-manual-editor.md |  16 +-
 ...-merchandising-rules-visual-editor-beta.md |   8 +-
 ...ating-merchandising-rules-visual-editor.md |   4 +-
 docs/tutorials/es/creating-pickup-points.md   |  11 +-
 ...eating-promotion-for-a-customer-cluster.md |  18 +-
 docs/tutorials/es/creating-roles.md           |   8 +-
 .../es/creating-service-for-a-sku.md          |   4 +-
 docs/tutorials/es/creating-synonyms.md        |   8 +-
 ...-files-structure-for-your-app-vtex-init.md |   4 +-
 .../es/creating-trigger-in-master-data.md     |   8 +-
 .../es/credit-card-basic-payment-flow.md      |   4 +-
 docs/tutorials/es/credit-control-overview.md  |   6 +-
 docs/tutorials/es/criar-um-produto-beta.md    |   8 +-
 docs/tutorials/es/crm-zen-suiteshare.md       |   4 +-
 docs/tutorials/es/custom-product-fields.md    |   4 +-
 docs/tutorials/es/customer-credit-overview.md |  16 +-
 .../es/customizar-a-toolbar-de-televendas.md  |   2 +-
 docs/tutorials/es/customize-suiteshare.md     |   4 +-
 ...omizing-the-checkout-confirmation-pages.md |   2 +-
 .../es/customizing-the-my-orders-section.md   |  20 +--
 .../es/customizing-your-stores-typography.md  |   8 +-
 ...data-dictionary-vtex-data-pipeline-beta.md |   4 +-
 docs/tutorials/es/data-entity.md              |  17 +-
 docs/tutorials/es/data-subject-rights.md      |   4 +-
 .../es/database-maintenance-full-cleanup.md   |  15 +-
 ...eactivating-and-reorganizing-categories.md |   4 +-
 .../es/declining-order-cancelation.md         |  21 +--
 docs/tutorials/es/deleting-a-category.md      |   2 +-
 docs/tutorials/es/deleting-customer-data.md   |   8 +-
 .../es/detaching-skus-by-specification.md     |   3 +-
 ...-end-for-the-list-feature-in-your-store.md |   8 +-
 .../es/direct-migration-magazine-luiza.md     |   4 +-
 docs/tutorials/es/disable-cloudflare-proxy.md |   4 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |   4 +-
 ...ic-relevance-in-intelligent-search-beta.md |   7 +-
 ...-field-on-profile-system-of-master-data.md |  25 ++-
 .../es/editing-my-data-suiteshare.md          |   4 +-
 .../es/enable-https-throughout-the-site.md    |   9 +-
 .../enabling-2-factor-authentication-login.md |  28 ++--
 ...enabling-3ds2-for-redsys-v2-integration.md |   6 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |  12 +-
 .../es/enabling-payments-with-bitcoin.md      |   4 +-
 ...cking-number-on-orders-already-invoiced.md |   4 +-
 .../es/entering-tax-receipts-in-the-order.md  |   8 +-
 docs/tutorials/es/erasing-customer-data.md    |   8 +-
 .../tutorials/es/events-available-in-audit.md |   4 +-
 docs/tutorials/es/exact-sales-suiteshare.md   |   4 +-
 ...mporting-product-and-sku-specifications.md |   4 +-
 ...the-availability-notification-notify-me.md |   4 +-
 docs/tutorials/es/exporting-data.md           |   4 +-
 .../es/exporting-orders-in-orders-module.md   |   4 +-
 ...acebook-liberacao-de-dominio-suiteshare.md |   4 +-
 .../es/faq-security-restricted-content.md     |   4 +-
 .../es/fill-out-the-stock-spreadsheet.md      |   4 +-
 ...ing-in-fields-in-the-import-spreadsheet.md |  19 ++-
 ...-import-spreadsheets-fixed-price-fields.md |   2 +-
 docs/tutorials/es/filtering-all-orders.md     |   4 +-
 docs/tutorials/es/filters.md                  |  12 +-
 ...tplaces-and-sellers-in-the-vtex-network.md |   4 +-
 docs/tutorials/es/find-sellers.md             |  10 +-
 .../fromto-of-payment-means-on-webservice.md  |   8 +-
 docs/tutorials/es/generating-a-har-file.md    |   7 +-
 docs/tutorials/es/geolocalizado-suiteshare.md |   4 +-
 docs/tutorials/es/geolocation-at-checkout.md  |   4 +-
 docs/tutorials/es/gift-card.md                |  24 +--
 ...od-practices-for-the-golive-of-my-store.md |  24 +--
 .../es/google-integration-warnings.md         |   4 +-
 docs/tutorials/es/google-pay-beta.md          |   4 +-
 .../es/hiring-the-security-certificate-sll.md |   4 +-
 ...how-can-i-change-the-domain-of-my-store.md |   4 +-
 ...how-can-i-create-a-field-in-master-data.md |   2 +-
 .../es/how-can-i-create-callcenter-user.md    |   3 +-
 .../how-can-i-create-cluster-of-customers.md  |  25 ++-
 ...e-newsletter-database-using-master-data.md |   4 +-
 .../es/how-change-order-works-beta.md         |   4 +-
 .../how-cnova-via-varejo-integration-works.md | 144 ++++++++++------
 ...-inclusion-of-newsletter-in-master-data.md |   4 +-
 ...e-the-https-protocol-on-my-stores-pages.md |   9 +-
 .../tutorials/es/how-does-reservation-work.md |  12 +-
 ...th-multiple-items-work-in-mercado-livre.md |   4 +-
 .../tutorials/es/how-does-vtex-search-work.md |   5 +-
 ...-item-with-shipping-benefit-on-the-cart.md |   4 +-
 ...-the-platforms-operation-sla-determined.md |   4 +-
 ...he-platform-take-to-identify-my-payment.md |   4 +-
 docs/tutorials/es/how-my-account-works.md     |   4 +-
 .../es/how-order-authorization-workss.md      |   4 +-
 .../es/how-product-name-control-works.md      |   4 +-
 .../es/how-promotion-competition-works.md     |   6 +-
 ...portional-shipping-costs-are-calculated.md |   4 +-
 .../es/how-shipping-calculation-works.md      |  15 +-
 .../es/how-the-carrefour-integration-works.md |  30 +---
 .../how-the-integration-with-buscape-works.md |  30 ++--
 .../es/how-the-order-replacement-works.md     |   2 +-
 ...en-websites-and-business-policies-works.md |   4 +-
 ...ess-to-the-order-for-invoicing-purposes.md |   4 +-
 ...ormation-to-the-order-and-manipulate-it.md |   4 +-
 .../es/how-to-capture-the-ip-of-an-order.md   |   8 +-
 .../tutorials/es/how-to-change-order-items.md |   4 +-
 .../tutorials/es/how-to-change-orders-beta.md |   8 +-
 ...he-order-of-payment-methods-at-checkout.md |   4 +-
 ...e-sorting-of-delivery-types-in-the-cart.md |   4 +-
 .../es/how-to-configure-a-custom-payment.md   |   4 +-
 ...re-mercado-pago-pro-as-a-payment-method.md |   4 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |   8 +-
 .../es/how-to-configure-payment-conditions.md |  12 +-
 .../es/how-to-configure-subscriptions.md      |  12 +-
 ...figure-the-fingerprint-device-for-stelo.md |   8 +-
 ...ng-feed-and-the-google-product-taxonomy.md |   2 +-
 .../es/how-to-create-a-page-template.md       |  22 +--
 docs/tutorials/es/how-to-create-a-product.md  |  20 +--
 ...eate-a-promotion-with-limitation-of-use.md |   4 +-
 .../es/how-to-create-a-shelf-template.md      |  19 ++-
 ...how-to-create-a-subscription-attachment.md |  12 +-
 .../es/how-to-create-conditional-prices.md    |   5 +-
 ...ow-to-define-the-url-for-a-product-page.md |   8 +-
 .../es/how-to-download-the-vtex-invoices.md   |   2 +-
 .../es/how-to-export-a-product-spreadsheet.md |   4 +-
 docs/tutorials/es/how-to-find-an-sku-id.md    |   4 +-
 ...import-pickup-points-using-spreadsheets.md |   4 +-
 ...de-a-registration-on-a-master-data-form.md |  25 ++-
 ...reverse-proxy-in-front-of-vtex-services.md |  22 ++-
 .../es/how-to-integrate-vtex-using-zapier.md  |   2 +-
 .../es/how-to-integrate-with-dafiti.md        |  20 +--
 .../es/how-to-integrate-with-facebook.md      |   6 +-
 docs/tutorials/es/how-to-make-transfers.md    |   4 +-
 .../es/how-to-migrate-a-store-to-pricing.md   |   4 +-
 ...o-modify-details-of-customers-addresses.md |  25 ++-
 ...optimize-searches-with-substitute-words.md |   8 +-
 ...o-place-a-regular-order-using-vtex-apis.md |   4 +-
 .../es/how-to-rank-the-best-selling-items.md  |   4 +-
 ...ister-your-salespersons-on-vtex-instore.md |   4 +-
 ...how-to-request-receivables-anticipation.md |   4 +-
 ...to-schedule-prices-for-a-range-of-hours.md |  12 +-
 .../es/how-to-set-up-fingerprint-for-payu.md  |   6 +-
 ...r-to-accept-payments-with-adyen-at-vtex.md |   5 +-
 ...t-up-the-device-fingerprint-for-braspag.md |   6 +-
 ...set-up-the-indeva-scheduled-appointment.md |  24 +--
 ...e-for-pick-up-field-in-smartcheckout-v6.md |   8 +-
 ...w-to-set-up-your-store-on-seller-portal.md |   6 +-
 ...s-4-in-vtex-stores-in-legacy-cms-portal.md |   4 +-
 ...to-setup-google-analytics-in-vtex-store.md |   4 +-
 ...how-to-turn-my-store-website-into-a-pwa.md |   4 +-
 .../es/how-to-use-messages-on-your-io-apps.md |   8 +-
 .../es/how-to-use-the-index-report.md         |   4 +-
 .../es/how-to-use-the-meta-tags-control.md    |   4 +-
 .../how-to-use-the-search-result-control.md   |   4 +-
 ...ow-to-use-the-unavailable-product-class.md |   5 +-
 .../es/how-to-view-the-orders-details.md      |   4 +-
 ...ith-different-layouts-for-the-same-page.md |   4 +-
 docs/tutorials/es/how-trade-policies-work.md  |   4 +-
 docs/tutorials/es/hubspot-suiteshare.md       |   4 +-
 .../es/i-forgot-my-password-suiteshare.md     |   4 +-
 docs/tutorials/es/image-compression.md        |   4 +-
 docs/tutorials/es/image-widget.md             |  12 +-
 .../es/import-customer-data-brazil.md         |   7 +-
 .../es/importing-data-into-master-data.md     |   8 +-
 .../es/importing-images-from-a-spreadsheet.md |  11 +-
 .../es/importing-the-shipping-spreadsheet.md  |  16 +-
 ...les-in-the-transactional-email-template.md |   4 +-
 docs/tutorials/es/indexes-in-master-data.md   |   8 +-
 ...stalling-the-widget-with-gtm-suiteshare.md |   4 +-
 docs/tutorials/es/integrate-with-carrefour.md |   4 +-
 docs/tutorials/es/integrating-with-amazon.md  |  12 +-
 .../es/integrating-with-buscape-bp.md         |   4 +-
 .../es/integrating-with-mercado-livre.md      |  59 +++----
 .../tutorials/es/integrating-with-netshoes.md |  23 +--
 .../es/integrating-with-viavarejo-cnova.md    |   4 +-
 docs/tutorials/es/integrating-with-walmart.md |   8 +-
 ...etplace-and-vtex-seller-catalog-updates.md |  26 ++-
 ...en-non-vtex-marketplace-and-vtex-seller.md |  17 +-
 ...ormation-for-use-in-an-external-service.md |   8 +-
 ...egration-guide-for-erps-express-catalog.md |   2 +-
 ...integration-guide-for-erps-full-catalog.md |   2 +-
 ...r-marketplaces-marketplace-non-vtex-old.md |   4 +-
 ...laces-marketplace-non-vtex-with-payment.md |   4 +-
 ...e-for-marketplaces-marketplace-non-vtex.md |   4 +-
 ...rketplaces-seller-non-vtex-with-payment.md |   4 +-
 ...-guide-for-marketplaces-seller-non-vtex.md |   4 +-
 .../es/integration-guide-for-marketplaces.md  |   4 +-
 docs/tutorials/es/integration-interfaces.md   |   4 +-
 .../es/integration-with-google-tag-manager.md |   8 +-
 ...lligent-search-synonym-suggestions-beta.md |   4 +-
 docs/tutorials/es/intelligent-synonyms.md     |   4 +-
 docs/tutorials/es/interaction-details.md      |  10 +-
 ...erpreting-the-data-of-the-oms-order-bar.md |   4 +-
 .../tutorials/es/introduction-to-vtex-apis.md |   4 +-
 docs/tutorials/es/inventory-update-history.md |   4 +-
 docs/tutorials/es/kit-registration.md         |   4 +-
 .../tutorials/es/license-manager-resources.md |   6 +-
 ...t-method-through-checkout-customization.md |   2 +-
 ...-the-store-by-means-of-the-sales-policy.md |  25 ++-
 ...-the-store-by-means-of-the-trade-policy.md |  25 ++-
 docs/tutorials/es/links-suiteshare.md         |   4 +-
 docs/tutorials/es/lista-da-vez.md             |   4 +-
 docs/tutorials/es/magento-suiteshare.md       |   4 +-
 .../es/manage-the-sales-comissions-report.md  |  28 +---
 .../es/managing-content-per-binding.md        |   4 +-
 .../tutorials/es/managing-content-versions.md |  14 +-
 .../es/managing-delivery-capacity-beta.md     |  12 +-
 .../es/managing-delivery-capacity.md          |   6 +-
 docs/tutorials/es/managing-http-headers.md    |   4 +-
 docs/tutorials/es/managing-loading-docks.md   |  28 ++--
 .../es/managing-page-and-template-content.md  |  32 +---
 docs/tutorials/es/managing-pages.md           |   4 +-
 docs/tutorials/es/managing-projects.md        |   4 +-
 .../es/managing-redirects-per-binding.md      |  12 +-
 .../es/managing-shipping-policies.md          |   4 +-
 docs/tutorials/es/managing-shipping-rates.md  |   4 +-
 .../es/managing-singleton-content-types.md    |  16 +-
 docs/tutorials/es/managing-stock-items.md     |  12 +-
 docs/tutorials/es/managing-url-redirects.md   |   4 +-
 docs/tutorials/es/managing-users.md           |   4 +-
 docs/tutorials/es/managing-warehouses.md      |  33 ++--
 ...-classes-and-methods-used-on-webservice.md |   8 +-
 ...tegories-and-brands-for-the-marketplace.md |  12 +-
 ...re-categories-variations-and-attributes.md |  13 +-
 .../es/marketplace-invited-sellers.md         |   5 +-
 .../es/marketplace-strategies-at-vtex.md      |  22 +--
 .../es/marketplaces-and-integrations.md       |  10 +-
 docs/tutorials/es/master-data-v2.md           |   3 +-
 docs/tutorials/es/master-data.md              |   8 +-
 .../es/match-offers-mercado-livre.md          |   4 +-
 docs/tutorials/es/maximum-price-per-item.md   |   8 +-
 docs/tutorials/es/media-overview.md           |  20 +--
 docs/tutorials/es/mercado-libre-size-chart.md |   8 +-
 docs/tutorials/es/mercado-livre-faq.md        |   2 +-
 .../es/merchandising-rule-conditions.md       |   4 +-
 docs/tutorials/es/meta-tags-suiteshare.md     |   4 +-
 .../es/migrating-ads-in-mercado-livre.md      |   8 +-
 ...ng-to-the-new-version-of-smart-checkout.md |   4 +-
 docs/tutorials/es/mode-off-faq.md             |   4 +-
 docs/tutorials/es/moskit-suiteshare.md        |   4 +-
 ...moving-order-to-start-handling-shipping.md |   4 +-
 .../es/multilevel-omnichannel-inventory.md    |  16 +-
 .../my-orders-in-mercado-libre-have-errors.md |  18 +-
 .../es/my-store-order-was-not-created.md      |   4 +-
 docs/tutorials/es/navigation.md               |  10 +-
 .../es/new-google-shopping-api-integration.md |   4 +-
 docs/tutorials/es/new-my-orders-area.md       |  14 +-
 ...n-vtex-cmc-newsletteroptin-greater-than.md |   2 +-
 docs/tutorials/es/offer-details.md            |  10 +-
 docs/tutorials/es/offer-management.md         |  10 +-
 docs/tutorials/es/offer-quality-filters.md    |   8 +-
 docs/tutorials/es/offer-status.md             |  12 +-
 docs/tutorials/es/oms-page-structure.md       |   4 +-
 docs/tutorials/es/opening-hours-suiteshare.md |   4 +-
 .../tutorials/es/operational-capacity-beta.md |  12 +-
 ...ization-of-shipping-options-at-checkout.md |   8 +-
 .../es/order-allocation-algorithm-beta.md     |   4 +-
 ...-cancellation-requested-by-the-customer.md |   8 +-
 docs/tutorials/es/order-flow-and-status.md    |  37 ++---
 docs/tutorials/es/order-replacement.md        |  13 +-
 .../es/order-split-and-delivery-split.md      |   4 +-
 docs/tutorials/es/order-to-delivery.md        |   4 +-
 .../es/order-transactional-email-templates.md |   4 +-
 .../es/orders-management-feed-v3-setup.md     |  28 +---
 ...rrors-in-marketplace-integration-orders.md |   4 +-
 .../tutorials/es/payment-provider-protocol.md |  43 ++---
 .../es/payments-in-vtex-marketplaces.md       |   8 +-
 ...ration-testing-and-vulnerability-notice.md |  28 +---
 ...kup-points-for-subscription-orders-beta.md |   8 +-
 .../pickup-points-for-subscription-orders.md  |   4 +-
 docs/tutorials/es/pickup-points.md            |   2 +-
 docs/tutorials/es/pipedrive-suiteshare.md     |   4 +-
 docs/tutorials/es/piperun-suiteshare.md       |   4 +-
 .../es/planner-actions-on-releases-beta.md    |  12 +-
 .../es/planner-calendar-page-beta.md          |   8 +-
 .../es/planner-release-concept-beta.md        |   8 +-
 .../es/planner-releases-page-beta.md          |   8 +-
 docs/tutorials/es/predefined-roles.md         |  11 +-
 docs/tutorials/es/price-divergence-rule.md    |   8 +-
 .../es/price-divergence-rules-beta.md         |  14 +-
 docs/tutorials/es/product-list.md             |   2 +-
 .../es/product-registration-fields.md         |  23 ++-
 docs/tutorials/es/products-and-skus-beta.md   |  12 +-
 docs/tutorials/es/promotions-beta.md          |  20 +--
 .../tutorials/es/promotions-simulator-beta.md |  12 +-
 docs/tutorials/es/promotions-simulator.md     |   4 +-
 docs/tutorials/es/qr-code-suiteshare.md       |   4 +-
 .../es/querying-data-on-master-data.md        |   2 +-
 docs/tutorials/es/rdstation-crm-suiteshare.md |   4 +-
 docs/tutorials/es/rdstation-suiteshare.md     |   4 +-
 docs/tutorials/es/received-skus-beta.md       |  32 +---
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |   8 +-
 .../es/redirect-from-other-addresses.md       |   4 +-
 .../es/redirection-from-other-addresses.md    |   4 +-
 docs/tutorials/es/redirects.md                |   4 +-
 docs/tutorials/es/regionalization-beta.md     |   8 +-
 .../es/registering-a-products-base-price.md   |   8 +-
 docs/tutorials/es/registering-geolocation.md  |   4 +-
 docs/tutorials/es/registering-holidays.md     |   8 +-
 ...-with-nominal-discount-based-on-formula.md |   8 +-
 docs/tutorials/es/releases-module-beta.md     |   4 +-
 docs/tutorials/es/releases-overview.md        |   8 +-
 docs/tutorials/es/relevance-rules.md          |   4 +-
 docs/tutorials/es/remarketing.md              |   4 +-
 ...request-headers-must-only-contain-ascii.md |   4 +-
 ...l-data-under-international-data-privacy.md |   8 +-
 .../responsibilities-in-the-vtex-ecosystem.md |   4 +-
 docs/tutorials/es/returning-order-items.md    |  19 ++-
 docs/tutorials/es/risk-assessment.md          |   2 +-
 docs/tutorials/es/roles.md                    |   8 +-
 .../sales-associate-code-field-at-checkout.md |  16 +-
 docs/tutorials/es/sales-funnel-suiteshare.md  |   4 +-
 docs/tutorials/es/sales-performance.md        |   4 +-
 docs/tutorials/es/scheduled-delivery.md       |  14 +-
 .../scheduling-features-for-special-events.md |   4 +-
 docs/tutorials/es/scheduling-prices.md        |   4 +-
 docs/tutorials/es/schemas-on-master-data.md   |   2 +-
 docs/tutorials/es/search-behavior.md          |   8 +-
 .../tutorials/es/search-by-geo-coordinates.md |   3 +-
 docs/tutorials/es/search-navigator-control.md |  24 +--
 docs/tutorials/es/search-parameters.md        |   4 +-
 .../es/searching-for-events-on-audit.md       |  12 +-
 docs/tutorials/es/searching-for-old-orders.md |   5 +-
 .../es/searching-for-orders-in-oms.md         |   4 +-
 docs/tutorials/es/security-certificate-ssl.md |   4 +-
 docs/tutorials/es/security-monitor.md         |   4 +-
 docs/tutorials/es/seletivo.md                 |   4 +-
 ...reating-an-account-in-the-seller-portal.md |   4 +-
 docs/tutorials/es/seller-management.md        |   4 +-
 docs/tutorials/es/seller-portal-promotions.md |   4 +-
 .../es/seller-portal-shared-products.md       |   2 +-
 ...abel-payment-methods-to-the-marketplace.md |   4 +-
 ...es-and-bags-attributes-to-mercado-livre.md |   8 +-
 .../es/sending-sku-attributes-to-amazon.md    |   8 +-
 docs/tutorials/es/sent-offers-beta.md         |   4 +-
 .../es/sent-offers-buybox-opportunities.md    |  14 +-
 docs/tutorials/es/sequencial-suiteshare.md    |   4 +-
 ...et-up-alelo-payment-method-for-cielo-v3.md |   8 +-
 .../setting-up-3ds-2-authentication-flow.md   |   8 +-
 .../es/setting-up-a-personal-gift-message.md  |   4 +-
 .../es/setting-up-abandoned-carts.md          |  20 +--
 .../es/setting-up-alternative-accounts.md     |   4 +-
 ...app-linking-for-payments-app-in-instore.md |  14 +-
 docs/tutorials/es/setting-up-b2b-on-vtex.md   |   8 +-
 .../es/setting-up-conductor-gateway.md        |   2 +-
 .../es/setting-up-cybersource-antifraud.md    |   8 +-
 .../es/setting-up-cybersource-gateway.md      |  15 +-
 ...etting-up-device-fingerprint-for-niubiz.md |  12 +-
 .../es/setting-up-firstdata-acquirer.md       |   2 +-
 .../es/setting-up-future-inventory.md         |  15 +-
 ...-itau-registered-ticket-itau-registrado.md |   2 +-
 ...ow-y-klarna-pay-later-as-payment-method.md |   8 +-
 ...o-offline-and-wallet-as-payment-methods.md |   4 +-
 .../setting-up-mercadopagov1-sub-acquirer.md  |   6 +-
 .../es/setting-up-merchant-id-in-apple-pay.md |   8 +-
 ...g-up-mundipagg-fraud-prevention-gateway.md |   6 +-
 .../es/setting-up-mundipagg-gateway.md        |   6 +-
 docs/tutorials/es/setting-up-my-account.md    |   4 +-
 .../es/setting-up-nethone-antifraud.md        |   8 +-
 .../es/setting-up-nexxpago-gateway.md         |   2 +-
 docs/tutorials/es/setting-up-nps-gateway.md   |   2 +-
 ...ne-payment-conditions-using-mercadopago.md |   4 +-
 .../es/setting-up-pagarmev2-gateway.md        |   4 +-
 .../es/setting-up-pagbrasil-gateway.md        |   2 +-
 .../es/setting-up-paghiper-gateway.md         |   2 +-
 .../es/setting-up-payment-with-paypal.md      |   2 +-
 .../es/setting-up-paymentez-gateway.md        |   2 +-
 .../es/setting-up-payments-with-alignet.md    |   2 +-
 .../es/setting-up-payments-with-apple-pay.md  |   4 +-
 ...setting-up-payments-with-cieloecommerce.md |   4 +-
 .../setting-up-payments-with-credimarcas.md   |   4 +-
 .../es/setting-up-payments-with-itau-rede.md  |   8 +-
 .../es/setting-up-payments-with-iugu.md       |  12 +-
 .../es/setting-up-payments-with-koin.md       |   2 +-
 .../setting-up-payments-with-mercado-pago.md  |   4 +-
 .../setting-up-payments-with-notes-payable.md |   4 +-
 .../es/setting-up-payments-with-nuvei.md      |  10 +-
 .../setting-up-payments-with-pagoefectivo.md  |   2 +-
 .../es/setting-up-payments-with-pagosweb.md   |   2 +-
 .../es/setting-up-payments-with-payclub.md    |   2 +-
 .../es/setting-up-payments-with-promissory.md |   4 +-
 .../es/setting-up-payments-with-pse.md        |   3 +-
 .../es/setting-up-payments-with-stelo.md      |   2 +-
 ...g-up-payments-with-store-card-cobranded.md |   8 +-
 docs/tutorials/es/setting-up-paypal-plus.md   |   2 +-
 docs/tutorials/es/setting-up-payu-gateway.md  |   2 +-
 .../es/setting-up-payu-global-gateway.md      |   3 +-
 .../tutorials/es/setting-up-payzen-gateway.md |   2 +-
 .../es/setting-up-place2pay-gateway.md        |   2 +-
 ...rice-and-availability-of-skus-by-region.md |  12 +-
 ...ting-up-price-tables-for-specific-users.md |  16 +-
 ...setting-up-rede-acquirer-with-erederest.md |   6 +-
 ...up-seller-white-label-as-a-pickup-point.md |   8 +-
 docs/tutorials/es/setting-up-shipment.md      |   4 +-
 .../setting-up-sitef-gateway-with-pre-auth.md |   2 +-
 docs/tutorials/es/setting-up-sitef-gateway.md |   2 +-
 .../es/setting-up-sub-acquirer-stelo.md       |   2 +-
 .../es/setting-up-the-global-category.md      |  12 +-
 .../setting-up-the-logistics-for-instore.md   |   4 +-
 .../es/setting-up-the-moip-sub-acquirer.md    |   8 +-
 .../es/setting-up-the-notify-me-option.md     |   4 +-
 ...up-the-sales-funnel-on-google-analytics.md |  63 +++----
 .../es/setting-up-the-tnspay-gateway.md       |   2 +-
 .../setting-up-the-type-of-interest-rate.md   |   4 +-
 docs/tutorials/es/setting-up-triggers.md      |   4 +-
 .../es/setting-up-webpay2p-gateway.md         |   2 +-
 docs/tutorials/es/setup-safetypay.md          |   2 +-
 docs/tutorials/es/sharpspring-suiteshare.md   |   4 +-
 docs/tutorials/es/shipping-options-beta.md    |   4 +-
 docs/tutorials/es/shipping-policy-beta.md     |   6 +-
 docs/tutorials/es/shipping-rate-template.md   |  16 +-
 docs/tutorials/es/shipping-rates.md           |  12 +-
 docs/tutorials/es/shipping-simulation.md      |  16 +-
 docs/tutorials/es/shopify-suiteshare.md       |   4 +-
 docs/tutorials/es/sku-bindings.md             |   4 +-
 docs/tutorials/es/sku-registration-fields.md  |  12 +-
 ...rrors-in-marketplace-integration-orders.md |   4 +-
 ...-customer-information-automatic-fill-in.md |   4 +-
 ...martcheckout-v5-general-characteristics.md |   4 +-
 docs/tutorials/es/special-conditions.md       |   8 +-
 docs/tutorials/es/split-payment.md            |   4 +-
 docs/tutorials/es/store-overview-beta.md      |   8 +-
 docs/tutorials/es/subscription-plans.md       |   8 +-
 docs/tutorials/es/table-of-base-prices.md     |   4 +-
 docs/tutorials/es/telesales-toolbar.md        |   4 +-
 .../es/testing-webservice-using-soapui.md     |  18 +-
 ...-into-packages-with-separate-deliveries.md |   4 +-
 .../es/the-risk-assessment-process.md         |   4 +-
 docs/tutorials/es/total-shipping-cost.md      |   6 +-
 .../es/tracking-your-sales-analytics.md       |   2 +-
 ...understanding-competition-of-promotions.md |   6 +-
 .../es/understanding-how-indexation-works.md  |   7 +-
 .../es/understanding-incomplete-orders.md     |   4 +-
 .../understanding-the-conversation-tracker.md |   4 +-
 .../understanding-the-cubic-weight-factor.md  |   4 +-
 .../understanding-the-updating-of-the-xml.md  |   2 +-
 .../es/understanding-vtex-matcher-scoring.md  |   4 +-
 ...nderstanding-vtexs-email-capture-system.md |   8 +-
 .../es/updating-prices-in-marketplaces.md     |   4 +-
 docs/tutorials/es/url-mapping-301-redirect.md |   8 +-
 ...-track-browsing-sessions-in-vtex-stores.md |   5 +-
 docs/tutorials/es/using-tools-html.md         |   2 +-
 docs/tutorials/es/vtex-ad-network-beta.md     |   8 +-
 docs/tutorials/es/vtex-admin-start-here.md    |   4 +-
 docs/tutorials/es/vtex-agreement.md           |   4 +-
 ...vtex-dashboard-guide-for-black-week-faq.md |  16 +-
 ...gent-search-multilanguage-settings-beta.md |  16 +-
 .../es/vtex-pick-and-pack-fulfillment.md      |   8 +-
 .../tutorials/es/vtex-pick-and-pack-mobile.md |  24 +--
 docs/tutorials/es/vtex-shield.md              |   8 +-
 .../es/vtex-shipping-network-dashboard.md     |   4 +-
 docs/tutorials/es/vtex-status-page.md         |   4 +-
 docs/tutorials/es/vtex-suiteshare.md          |   4 +-
 docs/tutorials/es/vtex-tracking-holidays.md   |   4 +-
 docs/tutorials/es/warehouse.md                |  53 +++---
 .../es/web-application-firewall-waf.md        |   4 +-
 ...ements-to-start-developing-with-vtex-io.md |   4 +-
 ...-utm-source-utm-campaign-and-utm-medium.md |   8 +-
 .../es/what-is-a-franchise-account.md         |  19 +--
 docs/tutorials/es/what-is-a-marketplace.md    |   4 +-
 docs/tutorials/es/what-is-an-affiliate.md     |   4 +-
 ...rand-gateway-and-sub-acquirer-in-brazil.md |   4 +-
 ...tween-sales-policy-affiliate-and-seller.md |   4 +-
 ...d-considered-for-calculating-my-billing.md |   4 +-
 ...s-the-purpose-of-the-customized-control.md |   4 +-
 docs/tutorials/es/what-is-the-shared-cart.md  |  12 +-
 docs/tutorials/es/what-is-the-sponsor-user.md |   4 +-
 docs/tutorials/es/what-is-vtex-io.md          |   4 +-
 ...d-i-group-products-in-the-same-shipment.md |   4 +-
 .../es/white-label-sellers-selection.md       |   4 +-
 ...stered-bank-slip-require-authentication.md |   4 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  25 ++-
 docs/tutorials/es/widget.md                   |   4 +-
 docs/tutorials/es/wix-suiteshare.md           |   4 +-
 docs/tutorials/es/wordpress-suiteshare.md     |   4 +-
 .../es/working-with-master-data-rest-api.md   |   2 +-
 ...ing-an-effective-ticket-to-vtex-support.md |   6 +-
 docs/tutorials/es/zapier-suiteshare.md        |   4 +-
 docs/tutorials/pt/account-management.md       |  22 +--
 docs/tutorials/pt/accounts-payable-brazil.md  |   4 +-
 .../actions-for-vtex-marketplace-operation.md |   8 +-
 docs/tutorials/pt/activating-new-vtex-cdn.md  |  12 +-
 docs/tutorials/pt/activating-skus-in-bulk.md  |   7 +-
 ...s-support-to-the-integration-with-adyen.md |   4 +-
 .../adding-a-record-on-a-master-data-form.md  |  13 +-
 docs/tutorials/pt/adding-a-seller-beta.md     |   8 +-
 docs/tutorials/pt/adding-a-seller.md          |   8 +-
 docs/tutorials/pt/adding-an-attachment.md     |   8 +-
 docs/tutorials/pt/adding-collections-cms.md   |  28 +---
 .../tutorials/pt/additional-shipping-costs.md |  14 +-
 .../advertising-with-vtex-ad-network-beta.md  |   4 +-
 docs/tutorials/pt/affiliates-program-app.md   |   8 +-
 docs/tutorials/pt/amaro-integration.md        |   8 +-
 ...mazon-multi-channel-fulfillment-mcf-app.md |  22 +--
 docs/tutorials/pt/analytics.md                |   4 +-
 docs/tutorials/pt/antifraud-provider.md       |   4 +-
 docs/tutorials/pt/application-keys.md         |  20 +--
 ...roving-payment-of-the-bank-payment-slip.md |   8 +-
 docs/tutorials/pt/apps-overview.md            |   4 +-
 docs/tutorials/pt/assembly-options-app.md     |  12 +-
 docs/tutorials/pt/assembly-options.md         |   8 +-
 docs/tutorials/pt/audit.md                    |   4 +-
 docs/tutorials/pt/authentication-page.md      |   4 +-
 ...user-and-password-on-the-rest-interface.md |   4 +-
 docs/tutorials/pt/authentication.md           |   8 +-
 docs/tutorials/pt/bank-reconciliations.md     |   4 +-
 .../become-a-certified-connector-partner.md   |   3 +-
 .../best-practices-against-virtual-attacks.md |   4 +-
 ...ces-for-accessing-the-store-without-www.md |   4 +-
 docs/tutorials/pt/billing-module-overview.md  |   4 +-
 docs/tutorials/pt/black-week.md               |   8 +-
 .../tutorials/pt/brand-registration-fields.md |  19 ++-
 docs/tutorials/pt/campaign-audiences-list.md  |   4 +-
 docs/tutorials/pt/campaign-promotion.md       |   8 +-
 docs/tutorials/pt/carrier-working-hours.md    |   4 +-
 .../pt/category-registration-fields.md        |  19 ++-
 ...egory-variations-and-attributes-mapping.md |  13 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |   4 +-
 ...ult-system-texts-displayed-in-the-store.md |   4 +-
 .../changing-items-from-a-complete-order.md   |   6 +-
 .../changing-the-total-cost-of-the-order.md   |   4 +-
 ...for-errors-or-problems-in-a-transaction.md |   4 +-
 docs/tutorials/pt/checkout-vtex-overview.md   |   8 +-
 ...chitecture-or-an-additional-environment.md |   4 +-
 ...ount-franchise-account-or-seller-portal.md |   2 +-
 docs/tutorials/pt/cms-folder-structure.md     |   8 +-
 .../pt/collection-highlight-control.md        |   4 +-
 .../pt/como-criar-usuario-webservice.md       |   8 +-
 ...funciona-a-integracao-da-magazine-luiza.md |  42 +++--
 .../como-funciona-a-integracao-da-netshoes.md | 156 +++++++++++-------
 ...-sistema-esta-sendo-renderizada-no-site.md |   4 +-
 .../pt/conditions-builder-usage-examples.md   |   5 +-
 docs/tutorials/pt/conecta-la-integration.md   |  12 +-
 ...-accounts-with-multiple-official-stores.md |   4 +-
 docs/tutorials/pt/configure-cartman.md        |   8 +-
 ...yee-benefits-using-master-data-clusters.md |  25 ++-
 .../pt/configure-seller-regionalization.md    |   4 +-
 ...figure-template-in-smartcheckout-update.md |   8 +-
 .../configuring-a-marketplace-trade-policy.md |   4 +-
 ...uring-a-pricing-rule-for-a-sales-policy.md |   4 +-
 ...nfiguring-a-santander-registered-boleto.md |  25 ++-
 .../pt/configuring-access-profiles-old.md     |   2 +-
 .../pt/configuring-access-without-www.md      |   4 +-
 docs/tutorials/pt/configuring-affiliates.md   |   4 +-
 docs/tutorials/pt/configuring-affirm.md       |   4 +-
 ...port-for-organizations-and-cost-centers.md |   4 +-
 .../pt/configuring-carriers-cut-off-time.md   |   6 +-
 .../pt/configuring-cielo-acquirer.md          |   4 +-
 ...ng-clearsale-global-anti-fraud-solution.md |   4 +-
 .../pt/configuring-clearsale-v3-antifraud.md  |  11 +-
 .../pt/configuring-dns-pointing-to-vtex.md    |  28 +---
 ...nfiguring-domains-in-account-management.md |  14 +-
 docs/tutorials/pt/configuring-greenlist.md    |   4 +-
 ...eal-payment-method-in-adyen-integration.md |   6 +-
 ...automatic-payment-settlement-time-frame.md |   8 +-
 ...guring-mercado-pagos-device-fingerprint.md |   4 +-
 .../pt/configuring-openpay-payment-gateway.md |   4 +-
 .../pt/configuring-order-recurrence.md        |   4 +-
 ...-payment-with-adyenv3-in-vtex-sales-app.md |  12 +-
 .../pt/configuring-payment-with-adyenv3.md    |  20 +--
 .../pt/configuring-price-divergence-rule.md   |   8 +-
 ...guring-seller-allocation-for-buying-xky.md |   3 +-
 .../configuring-sign-in-with-apple-id-beta.md |   8 +-
 .../pt/configuring-spin-pay-gateway.md        |   8 +-
 .../configuring-stripe-gateway-affiliation.md |  21 +--
 .../pt/configuring-telesales-features.md      |   4 +-
 .../pt/configuring-the-global-checkout.md     |   4 +-
 .../pt/configuring-the-pickup-in-store.md     |   4 +-
 .../pt/configuring-the-rede-acquirer.md       |   4 +-
 .../pt/configuring-the-scheduled-delivery.md  |   6 +-
 .../pt/configuring-the-store-domain.md        |   8 +-
 .../configuring-tuna-gateway-affiliation.md   |   4 +-
 .../pt/configuring-vtex-marketplace.md        |   8 +-
 docs/tutorials/pt/configuring-xml.md          |   4 +-
 docs/tutorials/pt/coupons-beta.md             |   4 +-
 .../pt/creating-a-campaign-audience.md        |  19 +--
 docs/tutorials/pt/creating-a-coupon-beta.md   |   8 +-
 docs/tutorials/pt/creating-a-coupon.md        |  24 +--
 .../pt/creating-a-product-collection.md       |   8 +-
 .../pt/creating-a-product-for-presale.md      |   8 +-
 .../pt/creating-a-shipping-policy.md          |   4 +-
 .../pt/creating-a-subscription-plan.md        |  12 +-
 docs/tutorials/pt/creating-a-trade-policy.md  |   8 +-
 docs/tutorials/pt/creating-a-type-of-list.md  |   4 +-
 .../pt/creating-an-oauth2-authentication.md   |   4 +-
 ...h-promotional-price-using-a-price-table.md |   4 +-
 ...-apptokens-to-authenticate-integrations.md |   6 +-
 ...ustomer-and-address-forms-in-new-stores.md |  25 ++-
 docs/tutorials/pt/creating-data-entity.md     |  25 ++-
 docs/tutorials/pt/creating-landing-pages.md   |  10 +-
 ...ating-merchandising-rules-manual-editor.md |  16 +-
 ...-merchandising-rules-visual-editor-beta.md |   8 +-
 ...ating-merchandising-rules-visual-editor.md |   4 +-
 docs/tutorials/pt/creating-pickup-points.md   |  12 +-
 docs/tutorials/pt/creating-price-tables.md    |  12 +-
 ...eating-promotion-for-a-customer-cluster.md |  18 +-
 ...etween-master-data-entities-using-admin.md |   4 +-
 docs/tutorials/pt/creating-roles.md           |   8 +-
 .../pt/creating-service-for-a-sku.md          |   4 +-
 docs/tutorials/pt/creating-synonyms.md        |   4 +-
 ...-files-structure-for-your-app-vtex-init.md |   4 +-
 .../pt/creating-trigger-in-master-data.md     |   8 +-
 .../pt/credit-card-basic-payment-flow.md      |   4 +-
 docs/tutorials/pt/credit-control-overview.md  |   6 +-
 docs/tutorials/pt/criar-um-produto-beta.md    |   8 +-
 docs/tutorials/pt/custom-product-fields.md    |   4 +-
 docs/tutorials/pt/customer-credit-overview.md |  16 +-
 .../pt/customizar-a-toolbar-de-televendas.md  |   2 +-
 ...omizing-the-checkout-confirmation-pages.md |   2 +-
 .../pt/customizing-the-my-orders-section.md   |  18 +-
 .../pt/customizing-your-stores-typography.md  |   8 +-
 ...data-dictionary-vtex-data-pipeline-beta.md |   4 +-
 docs/tutorials/pt/data-entity.md              |  17 +-
 docs/tutorials/pt/data-subject-rights.md      |   4 +-
 .../pt/database-maintenance-full-cleanup.md   |  14 +-
 ...eactivating-and-reorganizing-categories.md |   4 +-
 docs/tutorials/pt/deadline-indicators.md      |   4 +-
 .../pt/declining-order-cancelation.md         |  21 +--
 docs/tutorials/pt/deleting-a-category.md      |   2 +-
 .../pt/deleting-a-folder-from-cms.md          |   8 +-
 docs/tutorials/pt/deleting-customer-data.md   |   4 +-
 ...liveries-progress-vtex-shipping-network.md |  12 +-
 .../pt/detaching-skus-by-specification.md     |   3 +-
 ...-end-for-the-list-feature-in-your-store.md |   8 +-
 docs/tutorials/pt/disable-cloudflare-proxy.md |   4 +-
 ...-vtex-ad-network-ads-in-your-store-beta.md |   4 +-
 ...ic-relevance-in-intelligent-search-beta.md |   7 +-
 ...-field-on-profile-system-of-master-data.md |  25 ++-
 .../pt/enable-https-throughout-the-site.md    |   9 +-
 .../enabling-2-factor-authentication-login.md |  28 ++--
 ...enabling-3ds2-for-redsys-v2-integration.md |   6 +-
 ...ling-local-stock-sale-in-vtex-sales-app.md |  12 +-
 .../pt/enabling-payments-with-bitcoin.md      |   4 +-
 ...cking-number-on-orders-already-invoiced.md |   4 +-
 .../pt/entering-tax-receipts-in-the-order.md  |   8 +-
 docs/tutorials/pt/erasing-customer-data.md    |   4 +-
 .../tutorials/pt/events-available-in-audit.md |   4 +-
 ...mporting-product-and-sku-specifications.md |   4 +-
 ...the-availability-notification-notify-me.md |   4 +-
 docs/tutorials/pt/exporting-data.md           |   4 +-
 .../pt/exporting-orders-in-orders-module.md   |   4 +-
 .../pt/faq-security-restricted-content.md     |   4 +-
 .../pt/fill-out-the-stock-spreadsheet.md      |   4 +-
 ...ing-in-fields-in-the-import-spreadsheet.md |  19 ++-
 ...-import-spreadsheets-fixed-price-fields.md |   6 +-
 docs/tutorials/pt/filtering-all-orders.md     |   4 +-
 docs/tutorials/pt/filters.md                  |  12 +-
 ...tplaces-and-sellers-in-the-vtex-network.md |   8 +-
 docs/tutorials/pt/find-sellers.md             |   4 +-
 .../fromto-of-payment-means-on-webservice.md  |   8 +-
 docs/tutorials/pt/fulfillment-magalu.md       |   8 +-
 docs/tutorials/pt/generating-a-har-file.md    |   7 +-
 docs/tutorials/pt/geolocation-at-checkout.md  |   4 +-
 docs/tutorials/pt/gift-card.md                |  24 +--
 ...od-practices-for-the-golive-of-my-store.md |  24 +--
 .../pt/google-integration-warnings.md         |   8 +-
 docs/tutorials/pt/google-pay-beta.md          |  20 +--
 .../pt/hiring-the-security-certificate-sll.md |   4 +-
 ...how-can-i-change-the-domain-of-my-store.md |   2 +-
 ...how-can-i-create-a-field-in-master-data.md |   2 +-
 .../pt/how-can-i-create-callcenter-user.md    |   4 +-
 .../how-can-i-create-cluster-of-customers.md  |  25 ++-
 ...e-newsletter-database-using-master-data.md |   4 +-
 .../pt/how-change-order-works-beta.md         |   4 +-
 .../how-cnova-via-varejo-integration-works.md | 144 ++++++++++------
 ...-inclusion-of-newsletter-in-master-data.md |   4 +-
 ...e-the-https-protocol-on-my-stores-pages.md |  10 +-
 .../tutorials/pt/how-does-reservation-work.md |  12 +-
 ...th-multiple-items-work-in-mercado-livre.md |   4 +-
 .../tutorials/pt/how-does-vtex-search-work.md |   4 +-
 ...-item-with-shipping-benefit-on-the-cart.md |  10 +-
 ...-the-platforms-operation-sla-determined.md |   4 +-
 ...o-cancel-an-order-with-an-unpaid-boleto.md |   4 +-
 ...he-platform-take-to-identify-my-payment.md |   4 +-
 docs/tutorials/pt/how-my-account-works.md     |   4 +-
 .../pt/how-order-authorization-workss.md      |   4 +-
 .../pt/how-product-name-control-works.md      |   4 +-
 .../pt/how-promotion-competition-works.md     |   6 +-
 ...portional-shipping-costs-are-calculated.md |   4 +-
 .../pt/how-shipping-calculation-works.md      |  15 +-
 .../pt/how-the-carrefour-integration-works.md |  32 ++--
 .../how-the-integration-with-buscape-works.md |  64 +++----
 .../pt/how-the-order-replacement-works.md     |   2 +-
 ...en-websites-and-business-policies-works.md |   4 +-
 ...ess-to-the-order-for-invoicing-purposes.md |   4 +-
 ...ormation-to-the-order-and-manipulate-it.md |   4 +-
 .../pt/how-to-capture-the-ip-of-an-order.md   |   8 +-
 .../tutorials/pt/how-to-change-order-items.md |   6 +-
 .../tutorials/pt/how-to-change-orders-beta.md |   8 +-
 ...he-order-of-payment-methods-at-checkout.md |   4 +-
 ...e-sorting-of-delivery-types-in-the-cart.md |   4 +-
 .../pt/how-to-configure-a-custom-payment.md   |   4 +-
 ...re-mercado-pago-pro-as-a-payment-method.md |   8 +-
 ...e-and-maximum-quantity-of-items-per-sku.md |   8 +-
 .../pt/how-to-configure-payment-conditions.md |  12 +-
 ...to-configure-rating-and-review-controls.md |   4 +-
 .../pt/how-to-configure-subscriptions.md      |  12 +-
 ...figure-the-fingerprint-device-for-stelo.md |   8 +-
 ...ng-feed-and-the-google-product-taxonomy.md |   2 +-
 .../pt/how-to-create-a-page-template.md       |  22 +--
 docs/tutorials/pt/how-to-create-a-product.md  |  20 +--
 ...eate-a-promotion-with-limitation-of-use.md |   4 +-
 .../pt/how-to-create-a-shelf-template.md      |  19 ++-
 ...how-to-create-a-subscription-attachment.md |  12 +-
 .../pt/how-to-create-conditional-prices.md    |   5 +-
 ...ow-to-define-the-url-for-a-product-page.md |   8 +-
 .../pt/how-to-download-the-vtex-invoices.md   |   2 +-
 .../pt/how-to-export-a-product-spreadsheet.md |   4 +-
 docs/tutorials/pt/how-to-find-an-sku-id.md    |   4 +-
 ...import-pickup-points-using-spreadsheets.md |   4 +-
 ...de-a-registration-on-a-master-data-form.md |  25 ++-
 ...reverse-proxy-in-front-of-vtex-services.md |  22 ++-
 .../pt/how-to-integrate-with-dafiti.md        |  21 +--
 .../pt/how-to-integrate-with-facebook.md      |  12 +-
 docs/tutorials/pt/how-to-make-transfers.md    |   4 +-
 .../pt/how-to-migrate-a-store-to-pricing.md   |   4 +-
 ...o-modify-details-of-customers-addresses.md |  25 ++-
 ...optimize-searches-with-substitute-words.md |   4 +-
 ...o-place-a-regular-order-using-vtex-apis.md |   4 +-
 .../pt/how-to-rank-the-best-selling-items.md  |   4 +-
 ...ister-your-salespersons-on-vtex-instore.md |   4 +-
 ...how-to-request-receivables-anticipation.md |   4 +-
 ...to-schedule-prices-for-a-range-of-hours.md |   4 +-
 .../pt/how-to-set-up-fingerprint-for-payu.md  |   6 +-
 ...r-to-accept-payments-with-adyen-at-vtex.md |   4 +-
 ...t-up-the-device-fingerprint-for-braspag.md |   6 +-
 ...set-up-the-indeva-scheduled-appointment.md |   4 +-
 ...e-for-pick-up-field-in-smartcheckout-v6.md |   8 +-
 ...w-to-set-up-your-store-on-seller-portal.md |   6 +-
 ...s-4-in-vtex-stores-in-legacy-cms-portal.md |   8 +-
 ...to-setup-google-analytics-in-vtex-store.md |   4 +-
 ...how-to-turn-my-store-website-into-a-pwa.md |   3 +-
 .../pt/how-to-update-the-image-of-an-sku.md   |   8 +-
 .../pt/how-to-use-messages-on-your-io-apps.md |   8 +-
 .../pt/how-to-use-the-index-report.md         |   4 +-
 .../pt/how-to-use-the-meta-tags-control.md    |   4 +-
 .../how-to-use-the-search-result-control.md   |   4 +-
 ...ow-to-use-the-unavailable-product-class.md |   4 +-
 .../pt/how-to-view-the-orders-details.md      |   4 +-
 ...ith-different-layouts-for-the-same-page.md |   4 +-
 docs/tutorials/pt/image-compression.md        |   4 +-
 docs/tutorials/pt/image-widget.md             |  12 +-
 .../pt/import-customer-data-brazil.md         |   7 +-
 .../pt/importing-data-into-master-data.md     |   8 +-
 .../pt/importing-images-from-a-spreadsheet.md |  37 ++---
 .../pt/importing-the-shipping-spreadsheet.md  |  18 +-
 ...les-in-the-transactional-email-template.md |   4 +-
 docs/tutorials/pt/indexes-in-master-data.md   |   8 +-
 docs/tutorials/pt/integrate-with-carrefour.md |   4 +-
 docs/tutorials/pt/integrating-with-amazon.md  |  16 +-
 .../pt/integrating-with-buscape-bp.md         |   4 +-
 docs/tutorials/pt/integrating-with-enjoei.md  |  12 +-
 docs/tutorials/pt/integrating-with-loopi.md   |  20 +--
 .../pt/integrating-with-madeiramadeira.md     |  12 +-
 .../pt/integrating-with-magazine-luiza.md     |   3 +-
 .../pt/integrating-with-mercado-livre.md      |  60 +++----
 .../tutorials/pt/integrating-with-netshoes.md |  21 +--
 .../integrating-with-renner-and-camicado.md   |  12 +-
 .../pt/integrating-with-riachuelo.md          |  24 +--
 .../pt/integrating-with-viavarejo-cnova.md    |   4 +-
 docs/tutorials/pt/integrating-with-walmart.md |   8 +-
 docs/tutorials/pt/integrating-with-zoom.md    |  12 +-
 ...etplace-and-vtex-seller-catalog-updates.md |  26 ++-
 ...en-non-vtex-marketplace-and-vtex-seller.md |  18 +-
 ...ormation-for-use-in-an-external-service.md |   8 +-
 ...egration-guide-for-erps-express-catalog.md |   2 +-
 ...integration-guide-for-erps-full-catalog.md |   2 +-
 ...laces-marketplace-non-vtex-with-payment.md |   6 +-
 ...e-for-marketplaces-marketplace-non-vtex.md |   4 +-
 ...rketplaces-seller-non-vtex-with-payment.md |   4 +-
 ...-guide-for-marketplaces-seller-non-vtex.md |   4 +-
 .../pt/integration-guide-for-marketplaces.md  |   6 +-
 docs/tutorials/pt/integration-interfaces.md   |   4 +-
 .../pt/integration-with-google-tag-manager.md |   8 +-
 .../pt/integration-with-vtex-tracking.md      |  16 +-
 ...lligent-search-synonym-suggestions-beta.md |   4 +-
 docs/tutorials/pt/intelligent-synonyms.md     |   4 +-
 docs/tutorials/pt/interaction-details.md      |  10 +-
 ...erpreting-the-data-of-the-oms-order-bar.md |   4 +-
 .../tutorials/pt/introduction-to-vtex-apis.md |   4 +-
 docs/tutorials/pt/inventory-update-history.md |   4 +-
 docs/tutorials/pt/kabum-integration.md        |   4 +-
 docs/tutorials/pt/kit-registration.md         |   4 +-
 .../tutorials/pt/license-manager-resources.md |   6 +-
 ...t-method-through-checkout-customization.md |   2 +-
 ...-the-store-by-means-of-the-sales-policy.md |  25 ++-
 ...-the-store-by-means-of-the-trade-policy.md |  25 ++-
 docs/tutorials/pt/lista-da-vez.md             |   8 +-
 .../pt/locations-details-page-beta.md         |   4 +-
 docs/tutorials/pt/locations-module-beta.md    |  12 +-
 docs/tutorials/pt/magento-suiteshare.md       |   4 +-
 .../pt/manage-the-sales-comissions-report.md  |  28 +---
 .../pt/managing-content-per-binding.md        |   4 +-
 .../tutorials/pt/managing-content-versions.md |  14 +-
 .../pt/managing-delivery-capacity-beta.md     |  12 +-
 .../pt/managing-delivery-capacity.md          |   6 +-
 docs/tutorials/pt/managing-http-headers.md    |   4 +-
 docs/tutorials/pt/managing-loading-docks.md   |  27 ++-
 .../pt/managing-page-and-template-content.md  |   4 +-
 docs/tutorials/pt/managing-pages.md           |   4 +-
 docs/tutorials/pt/managing-projects.md        |   4 +-
 .../pt/managing-redirects-per-binding.md      |  12 +-
 .../pt/managing-shipping-policies.md          |   4 +-
 docs/tutorials/pt/managing-shipping-rates.md  |   4 +-
 .../pt/managing-singleton-content-types.md    |  16 +-
 docs/tutorials/pt/managing-stock-items.md     |  12 +-
 docs/tutorials/pt/managing-url-redirects.md   |   4 +-
 docs/tutorials/pt/managing-users.md           |   4 +-
 docs/tutorials/pt/managing-warehouses.md      |  31 ++--
 ...-classes-and-methods-used-on-webservice.md |   8 +-
 ...ies-and-brands-for-the-marketplace-beta.md |   4 +-
 ...tegories-and-brands-for-the-marketplace.md |  12 +-
 ...re-categories-variations-and-attributes.md |   8 +-
 .../pt/marketplace-invited-sellers.md         |   6 +-
 .../pt/marketplace-strategies-at-vtex.md      |  16 +-
 docs/tutorials/pt/master-data-v2.md           |   3 +-
 docs/tutorials/pt/master-data.md              |   4 +-
 .../pt/match-offers-mercado-livre.md          |   4 +-
 docs/tutorials/pt/maximum-price-per-item.md   |   8 +-
 docs/tutorials/pt/media-overview.md           |  20 +--
 docs/tutorials/pt/mercado-libre-size-chart.md |   8 +-
 docs/tutorials/pt/mercado-livre-faq.md        |   2 +-
 .../pt/merchandising-rule-conditions.md       |   4 +-
 docs/tutorials/pt/meta-tags-suiteshare.md     |   4 +-
 .../pt/migrating-ads-in-mercado-livre.md      |   8 +-
 ...ng-to-the-new-version-of-smart-checkout.md |   4 +-
 docs/tutorials/pt/mode-off-faq.md             |   7 +-
 ...moving-order-to-start-handling-shipping.md |   4 +-
 .../pt/multilevel-omnichannel-inventory.md    |  20 +--
 .../my-orders-in-mercado-libre-have-errors.md |  20 ++-
 .../pt/my-store-order-was-not-created.md      |   4 +-
 docs/tutorials/pt/navigation.md               |  11 +-
 .../pt/new-google-shopping-api-integration.md |   4 +-
 docs/tutorials/pt/new-my-orders-area.md       |  14 +-
 docs/tutorials/pt/new-route.md                |  12 +-
 docs/tutorials/pt/o-que-e-uma-disputa.md      |   4 +-
 docs/tutorials/pt/offer-details.md            |  10 +-
 docs/tutorials/pt/offer-management.md         |  10 +-
 docs/tutorials/pt/offer-quality-filters.md    |   8 +-
 docs/tutorials/pt/offer-status.md             |  12 +-
 docs/tutorials/pt/oms-page-structure.md       |   4 +-
 docs/tutorials/pt/opening-hours-suiteshare.md |  20 +--
 ...pening-tickets-to-vtex-support-finacial.md |   8 +-
 .../pt/opening-tickets-to-vtex-support.md     |   2 +-
 .../tutorials/pt/operational-capacity-beta.md |  12 +-
 ...ization-of-shipping-options-at-checkout.md |   8 +-
 .../pt/order-allocation-algorithm-beta.md     |   4 +-
 ...-cancellation-requested-by-the-customer.md |   8 +-
 docs/tutorials/pt/order-flow-and-status.md    |  36 ++--
 docs/tutorials/pt/order-replacement.md        |  14 +-
 .../pt/order-split-and-delivery-split.md      |   4 +-
 docs/tutorials/pt/order-status-table-oms.md   |   4 +-
 docs/tutorials/pt/order-to-delivery.md        |   8 +-
 .../pt/order-transactional-email-templates.md |   4 +-
 .../pt/orders-management-feed-v3-setup.md     |  28 +---
 ...rrors-in-marketplace-integration-orders.md |   4 +-
 docs/tutorials/pt/payment-methods.md          |   4 +-
 .../tutorials/pt/payment-provider-protocol.md |  37 ++---
 .../pt/payments-in-vtex-marketplaces.md       |   8 +-
 ...ration-testing-and-vulnerability-notice.md |  28 +---
 ...kup-points-for-subscription-orders-beta.md |   8 +-
 .../pickup-points-for-subscription-orders.md  |   4 +-
 docs/tutorials/pt/pickup-points.md            |   2 +-
 docs/tutorials/pt/piperun-suiteshare.md       |  12 +-
 .../pt/planner-actions-on-releases-beta.md    |  12 +-
 .../pt/planner-calendar-page-beta.md          |   8 +-
 .../pt/planner-release-concept-beta.md        |   8 +-
 .../pt/planner-releases-page-beta.md          |   8 +-
 docs/tutorials/pt/portadores-vtex-tracking.md |   8 +-
 docs/tutorials/pt/predefined-roles.md         |   8 +-
 docs/tutorials/pt/price-divergence-rule.md    |   8 +-
 .../pt/price-divergence-rules-beta.md         |  14 +-
 docs/tutorials/pt/product-list.md             |   2 +-
 .../pt/product-registration-fields.md         |  23 ++-
 docs/tutorials/pt/products-and-skus-beta.md   |   8 +-
 docs/tutorials/pt/promotions-beta.md          |  20 +--
 .../tutorials/pt/promotions-simulator-beta.md |  12 +-
 docs/tutorials/pt/promotions-simulator.md     |   4 +-
 docs/tutorials/pt/qr-code-suiteshare.md       |   4 +-
 docs/tutorials/pt/ready-to-dispatch.md        |  20 +--
 docs/tutorials/pt/received-skus-beta.md       |  36 +---
 .../reconciliation-of-accounts-receivable.md  |   4 +-
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |   8 +-
 .../pt/redirect-from-other-addresses.md       |   4 +-
 .../pt/redirection-from-other-addresses.md    |   4 +-
 docs/tutorials/pt/redirects.md                |   4 +-
 docs/tutorials/pt/regionalization-beta.md     |   8 +-
 docs/tutorials/pt/registering-a-category.md   |   4 +-
 .../pt/registering-a-products-base-price.md   |   8 +-
 docs/tutorials/pt/registering-geolocation.md  |  11 +-
 docs/tutorials/pt/registering-holidays.md     |   8 +-
 ...-with-nominal-discount-based-on-formula.md |   8 +-
 docs/tutorials/pt/releases-module-beta.md     |   8 +-
 docs/tutorials/pt/releases-overview.md        |   8 +-
 docs/tutorials/pt/relevance-rules.md          |   4 +-
 ...request-headers-must-only-contain-ascii.md |   4 +-
 .../responsibilities-in-the-vtex-ecosystem.md |   4 +-
 docs/tutorials/pt/returning-order-items.md    |  19 ++-
 docs/tutorials/pt/risk-assessment.md          |   4 +-
 docs/tutorials/pt/roles.md                    |   8 +-
 docs/tutorials/pt/routing-monitoring.md       |   8 +-
 .../sales-associate-code-field-at-checkout.md |  16 +-
 docs/tutorials/pt/sales-performance.md        |   4 +-
 docs/tutorials/pt/scheduled-delivery.md       |  14 +-
 .../scheduling-features-for-special-events.md |   4 +-
 docs/tutorials/pt/scheduling-prices.md        |   4 +-
 docs/tutorials/pt/scheduling-report.md        |   4 +-
 .../tutorials/pt/search-by-geo-coordinates.md |   3 +-
 docs/tutorials/pt/search-navigator-control.md |  26 +--
 docs/tutorials/pt/search-parameters.md        |   4 +-
 .../pt/searching-for-events-on-audit.md       |  12 +-
 docs/tutorials/pt/searching-for-old-orders.md |   4 +-
 .../pt/searching-for-orders-in-oms.md         |   4 +-
 docs/tutorials/pt/security-certificate-ssl.md |   4 +-
 docs/tutorials/pt/security-monitor.md         |   4 +-
 ...reating-an-account-in-the-seller-portal.md |   4 +-
 docs/tutorials/pt/seller-management.md        |   4 +-
 docs/tutorials/pt/seller-portal-promotions.md |   4 +-
 .../pt/seller-portal-shared-products.md       |   2 +-
 ...abel-payment-methods-to-the-marketplace.md |   4 +-
 ...es-and-bags-attributes-to-mercado-livre.md |   8 +-
 .../pt/sending-sku-attributes-to-amazon.md    |  12 +-
 docs/tutorials/pt/sent-offers-beta.md         |   4 +-
 .../pt/sent-offers-buybox-opportunities.md    |  14 +-
 docs/tutorials/pt/service-indicators.md       |   4 +-
 docs/tutorials/pt/service-management.md       |   8 +-
 docs/tutorials/pt/services-import.md          |  20 +--
 docs/tutorials/pt/services-scheduling.md      |  14 +-
 ...et-up-alelo-payment-method-for-cielo-v3.md |   8 +-
 .../setting-up-3ds-2-authentication-flow.md   |   8 +-
 .../pt/setting-up-a-personal-gift-message.md  |   4 +-
 .../pt/setting-up-abandoned-carts.md          |   8 +-
 .../pt/setting-up-alternative-accounts.md     |   4 +-
 ...app-linking-for-payments-app-in-instore.md |  12 +-
 docs/tutorials/pt/setting-up-b2b-on-vtex.md   |  13 +-
 .../setting-up-bradesco-registered-ticket.md  |   6 +-
 .../pt/setting-up-conductor-gateway.md        |   2 +-
 ...ayments-using-mercadopago-latin-america.md |   4 +-
 .../pt/setting-up-cybersource-antifraud.md    |   8 +-
 .../pt/setting-up-cybersource-gateway.md      |  16 +-
 .../pt/setting-up-decidir-gateway.md          |   4 +-
 ...etting-up-device-fingerprint-for-niubiz.md |  12 +-
 .../pt/setting-up-firstdata-acquirer.md       |   2 +-
 .../pt/setting-up-future-inventory.md         |  15 +-
 ...-itau-registered-ticket-itau-registrado.md |   2 +-
 .../pt/setting-up-itau-registered-ticket.md   |   2 +-
 ...ow-y-klarna-pay-later-as-payment-method.md |   8 +-
 ...eto-in-installments-as-a-payment-method.md |   8 +-
 ...o-offline-and-wallet-as-payment-methods.md |   4 +-
 .../setting-up-mercadopagov1-sub-acquirer.md  |   6 +-
 .../pt/setting-up-merchant-id-in-apple-pay.md |  12 +-
 ...g-up-mundipagg-fraud-prevention-gateway.md |   6 +-
 .../pt/setting-up-mundipagg-gateway.md        |   6 +-
 docs/tutorials/pt/setting-up-my-account.md    |   4 +-
 .../pt/setting-up-nethone-antifraud.md        |   8 +-
 .../pt/setting-up-nexxpago-gateway.md         |   2 +-
 docs/tutorials/pt/setting-up-nps-gateway.md   |   2 +-
 ...ne-payment-conditions-using-mercadopago.md |   4 +-
 .../pt/setting-up-pagarmev2-gateway.md        |   4 +-
 .../pt/setting-up-pagbrasil-gateway.md        |   2 +-
 .../pt/setting-up-paghiper-gateway.md         |   2 +-
 .../pt/setting-up-payment-with-paypal.md      |   2 +-
 .../pt/setting-up-paymentez-gateway.md        |   2 +-
 .../pt/setting-up-payments-with-alignet.md    |   2 +-
 .../pt/setting-up-payments-with-apple-pay.md  |   8 +-
 ...setting-up-payments-with-cieloecommerce.md |   4 +-
 .../setting-up-payments-with-credimarcas.md   |   4 +-
 .../pt/setting-up-payments-with-itau-rede.md  |   8 +-
 .../pt/setting-up-payments-with-iugu.md       |  12 +-
 .../pt/setting-up-payments-with-koin.md       |   2 +-
 .../setting-up-payments-with-mercado-pago.md  |   4 +-
 .../setting-up-payments-with-notes-payable.md |   4 +-
 .../pt/setting-up-payments-with-nuvei.md      |   8 +-
 .../pt/setting-up-payments-with-pagosweb.md   |   2 +-
 .../pt/setting-up-payments-with-payclub.md    |   2 +-
 .../pt/setting-up-payments-with-promissory.md |   4 +-
 .../pt/setting-up-payments-with-pse.md        |   3 +-
 .../pt/setting-up-payments-with-stelo.md      |   2 +-
 ...g-up-payments-with-store-card-cobranded.md |   8 +-
 docs/tutorials/pt/setting-up-paypal-plus.md   |   2 +-
 docs/tutorials/pt/setting-up-payu-gateway.md  |   2 +-
 .../pt/setting-up-payu-global-gateway.md      |   3 +-
 .../tutorials/pt/setting-up-payzen-gateway.md |   2 +-
 .../pt/setting-up-pix-as-a-payment-method.md  |   8 +-
 .../pt/setting-up-place2pay-gateway.md        |   2 +-
 ...rice-and-availability-of-skus-by-region.md |  12 +-
 ...ting-up-price-tables-for-specific-users.md |  18 +-
 ...setting-up-rede-acquirer-with-erederest.md |   6 +-
 ...up-seller-white-label-as-a-pickup-point.md |   8 +-
 docs/tutorials/pt/setting-up-shipment.md      |   4 +-
 .../setting-up-sitef-gateway-with-pre-auth.md |   2 +-
 docs/tutorials/pt/setting-up-sitef-gateway.md |   2 +-
 .../pt/setting-up-sub-acquirer-stelo.md       |   2 +-
 .../pt/setting-up-the-global-category.md      |  16 +-
 .../setting-up-the-logistics-for-instore.md   |   6 +-
 .../pt/setting-up-the-moip-sub-acquirer.md    |   8 +-
 .../pt/setting-up-the-notify-me-option.md     |   4 +-
 ...up-the-sales-funnel-on-google-analytics.md |  63 +++----
 .../pt/setting-up-the-tnspay-gateway.md       |   2 +-
 .../setting-up-the-type-of-interest-rate.md   |   4 +-
 docs/tutorials/pt/setting-up-triggers.md      |   4 +-
 docs/tutorials/pt/setup-safetypay.md          |   2 +-
 docs/tutorials/pt/shipping-options-beta.md    |   4 +-
 docs/tutorials/pt/shipping-policy-beta.md     |   6 +-
 docs/tutorials/pt/shipping-rate-template.md   |  16 +-
 docs/tutorials/pt/shipping-rates.md           |  14 +-
 docs/tutorials/pt/shipping-simulation.md      |  17 +-
 docs/tutorials/pt/shopee-integration.md       |  16 +-
 docs/tutorials/pt/sku-bindings.md             |   4 +-
 docs/tutorials/pt/sku-registration-fields.md  |  12 +-
 ...rrors-in-marketplace-integration-orders.md |   4 +-
 ...-customer-information-automatic-fill-in.md |   4 +-
 ...martcheckout-v5-general-characteristics.md |   4 +-
 docs/tutorials/pt/sms-and-email-report.md     |   4 +-
 docs/tutorials/pt/special-conditions.md       |   4 +-
 docs/tutorials/pt/split-payment.md            |   8 +-
 docs/tutorials/pt/store-overview-beta.md      |   8 +-
 docs/tutorials/pt/subscription-plans.md       |   8 +-
 docs/tutorials/pt/support-indicators.md       |   4 +-
 docs/tutorials/pt/table-of-base-prices.md     |   4 +-
 docs/tutorials/pt/telesales-toolbar.md        |   4 +-
 .../pt/testing-webservice-using-soapui.md     |  18 +-
 ...-into-packages-with-separate-deliveries.md |   4 +-
 .../pt/the-risk-assessment-process.md         |   4 +-
 docs/tutorials/pt/total-shipping-cost.md      |   6 +-
 .../pt/tracking-your-sales-analytics.md       |   2 +-
 .../pt/tutorial-vtex-tracking-mobile-app.md   |  76 ++++-----
 .../pt/understand-vtex-payment-fees.md        |   4 +-
 ...understanding-competition-of-promotions.md |   6 +-
 .../pt/understanding-how-indexation-works.md  |   7 +-
 .../pt/understanding-incomplete-orders.md     |   4 +-
 .../understanding-the-conversation-tracker.md |   4 +-
 .../understanding-the-cubic-weight-factor.md  |   4 +-
 .../understanding-the-updating-of-the-xml.md  |   4 +-
 .../pt/understanding-vtex-matcher-scoring.md  |   4 +-
 ...nderstanding-vtexs-email-capture-system.md |   8 +-
 .../pt/updating-prices-in-marketplaces.md     |   4 +-
 docs/tutorials/pt/url-mapping-301-redirect.md |   8 +-
 ...-track-browsing-sessions-in-vtex-stores.md |   4 +-
 docs/tutorials/pt/usuarios-vtex-tracking.md   |   3 +-
 .../visao-geral-da-estrutura-do-catalogo.md   |   4 +-
 docs/tutorials/pt/vtex-ad-network-beta.md     |   8 +-
 docs/tutorials/pt/vtex-admin-start-here.md    |   4 +-
 docs/tutorials/pt/vtex-agreement.md           |   4 +-
 ...vtex-dashboard-guide-for-black-week-faq.md |  16 +-
 ...gent-search-multilanguage-settings-beta.md |  16 +-
 .../pt/vtex-pick-and-pack-fulfillment.md      |  25 +--
 .../tutorials/pt/vtex-pick-and-pack-mobile.md |  24 +--
 docs/tutorials/pt/vtex-shield.md              |   8 +-
 ...ex-shipping-network-correios-activation.md |  12 +-
 .../pt/vtex-shipping-network-correios-faq.md  |   8 +-
 .../pt/vtex-shipping-network-dashboard.md     |  16 +-
 docs/tutorials/pt/vtex-status-page.md         |   4 +-
 docs/tutorials/pt/vtex-tracking-holidays.md   |   4 +-
 docs/tutorials/pt/warehouse.md                |  31 ++--
 .../pt/web-application-firewall-waf.md        |   4 +-
 docs/tutorials/pt/what-are-layouts.md         |   8 +-
 ...-utm-source-utm-campaign-and-utm-medium.md |   8 +-
 docs/tutorials/pt/what-is-a-dispute.md        |   4 +-
 .../pt/what-is-a-franchise-account.md         |  19 +--
 docs/tutorials/pt/what-is-a-marketplace.md    |   4 +-
 docs/tutorials/pt/what-is-a-service.md        |   4 +-
 docs/tutorials/pt/what-is-an-affiliate.md     |   4 +-
 ...rand-gateway-and-sub-acquirer-in-brazil.md |   4 +-
 ...tween-sales-policy-affiliate-and-seller.md |   4 +-
 ...d-considered-for-calculating-my-billing.md |   4 +-
 ...s-the-purpose-of-the-customized-control.md |   4 +-
 docs/tutorials/pt/what-is-the-shared-cart.md  |  12 +-
 docs/tutorials/pt/what-is-the-sponsor-user.md |   4 +-
 ...hat-to-do-when-a-customer-opens-dispute.md |   4 +-
 ...d-i-group-products-in-the-same-shipment.md |   4 +-
 ...ney-from-sale-be-credited-to-my-account.md |   4 +-
 .../pt/white-label-sellers-selection.md       |   4 +-
 ...stered-bank-slip-require-authentication.md |   4 +-
 ...-able-to-register-a-cpf-in-a-cnpj-field.md |  25 ++-
 ...ing-an-effective-ticket-to-vtex-support.md |   6 +-
 5199 files changed, 9504 insertions(+), 22070 deletions(-)

diff --git a/docs/announcements/en/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md b/docs/announcements/en/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md
index a9ed0e84a..814ed6828 100644
--- a/docs/announcements/en/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md	
+++ b/docs/announcements/en/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md	
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Now available detailed information about the calculation of shipping of the order'
 ---
 
-<div class="alert alert-warning">
-Due to technical reasons, the launch of this feature was postponed until further notice.
-</div>
+>⚠️ Due to technical reasons, the launch of this feature was postponed until further notice.
 
 Starting  April 1, 2019, the request JSON will return a new object called `alternativeTotals`. It will appear in the totalizers that are inside the array of `totals`, for queries made by the APIs Get Order.
 
diff --git a/docs/announcements/en/adapting-your-stores-front-end-requisites-to-master-data.md b/docs/announcements/en/adapting-your-stores-front-end-requisites-to-master-data.md
index 211febba3..c039f5c36 100644
--- a/docs/announcements/en/adapting-your-stores-front-end-requisites-to-master-data.md
+++ b/docs/announcements/en/adapting-your-stores-front-end-requisites-to-master-data.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: 'VTEX will discontinue Master Data CORS support starting
 
 With its main objective of providing clients with an increasingly efficient experience, VTEX will discontinue Master Data CORS support starting. In order for your store to avoid any operational and browsing failure, follow this article’s instructions.
 
-<div class="alert alert-warning"> Aligning this with the partnership we have with our clients and ensuring the least amount of friction possible to your operations, we have extended this resource's discontinuation date to October 7th, 2019. </div>
+>⚠️ Aligning this with the partnership we have with our clients and ensuring the least amount of friction possible to your operations, we have extended this resource's discontinuation date to October 7th, 2019.
 
 
 ### What is CORS?
diff --git a/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
index e148719d3..570eb387e 100644
--- a/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/en/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -17,9 +17,7 @@ announcementSynopsisEN: 'Users will only see the sidebar menu items they’re al
 
 [Roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) allow stores to grant users access only to a selection of resources on our platform. While this was enough to protect your account's data integrity and security, users could still see the sidebar menu items for restricted sections of the admin. These sections are no longer visible, so that users will only be able to see the items they are allowed to access. 
 
-<div class="alert alert-info">
-This action has a low impact on store’s operations, since it involves a reorganization of the left navigation, and not changes in individual user roles.  Also, no predefined settings will be lost: if your users already had pre-defined roles and permissions, they will remain the same.
-</div>
+>ℹ️ This action has a low impact on store’s operations, since it involves a reorganization of the left navigation, and not changes in individual user roles.  Also, no predefined settings will be lost: if your users already had pre-defined roles and permissions, they will remain the same.
 
 ## What has changed?
 
diff --git a/docs/announcements/en/all-stores-have-until-april-20th-to-activate-the-new-cdn.md b/docs/announcements/en/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
index a6ea2cadd..f15f30e48 100644
--- a/docs/announcements/en/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
+++ b/docs/announcements/en/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
@@ -22,10 +22,12 @@ Available for everyone since October 2017 the new CDN will be mandatory __starti
 __Important:__ The main requirement to use the new CDN is __enabling HTTPS in your whole website__. You must pay special attention to HTTP requests, that should turn into the HTTPS protocol in order to work under the new CDN. See how to [enable HTTPS throughout your website](/en/tutorial/enable-https-throughout-the-site) and pay attention to the requirements for this migration.
 
 So, remember:
-<div class="alert alert-warning">
-You have until <b>april 20th</b> to:<br>
-- Enable HTTPS in your whole website.<br>
-- Activate VTEX's new CDN.
-</div>
+>⚠️ You have until **april 20th** to:
+>
+> 
+> - Enable HTTPS in your whole website.
+>
+> 
+> - Activate VTEX's new CDN.
 
 After this, __crashes may occur__ in the stores that haven't completed the process, from broken layouts to your store going completely *offline* . We recommend you to enable HTTPS and activate the new CDN in this period, so your customers will enjoy the best e-commerce experience.
diff --git a/docs/announcements/en/apply-manual-prices-in-subscription-items.md b/docs/announcements/en/apply-manual-prices-in-subscription-items.md
index 312f07c2a..23a23f4ed 100644
--- a/docs/announcements/en/apply-manual-prices-in-subscription-items.md
+++ b/docs/announcements/en/apply-manual-prices-in-subscription-items.md
@@ -34,6 +34,4 @@ This change is motivated by merchants’ demands to set manual prices for each i
 
 To enable the Manual Price feature for Subscriptions, make sure you follow the steps described in the developer guide [Enabling Manual Price for Subscriptions v3](https://developers.vtex.com/vtex-rest-api/docs/enabling-manual-prices-for-subscriptions-v3).
 
-<div class="alert alert-warning">
-<p>Manual Price is only available for Subscriptions v3. If you are using a previous version of the Subscriptions system, check out the <a href="https://developers.vtex.com/vtex-rest-api/docs/subscriptions-v3-migration-guide">Subscriptions v3 migration guide</a>.</p>
-</div>
+>⚠️ Manual Price is only available for Subscriptions v3. If you are using a previous version of the Subscriptions system, check out the [Subscriptions v3 migration guide](https://developers.vtex.com/vtex-rest-api/docs/subscriptions-v3-migration-guide).
diff --git a/docs/announcements/en/become-an-expert-in-vtex-with-training-day.md b/docs/announcements/en/become-an-expert-in-vtex-with-training-day.md
index 94dcc2db8..d4bce8e0d 100644
--- a/docs/announcements/en/become-an-expert-in-vtex-with-training-day.md
+++ b/docs/announcements/en/become-an-expert-in-vtex-with-training-day.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: "Take part in an intensive VTEX training day with the world's leading experts."
 ---
 
-<div class="alert alert-info">
-A full day of training in VTEX given by leading experts.
-</div>
+>ℹ️ A full day of training in VTEX given by leading experts.
 
 For a long time, customers and partners have been asking for in-depth platform training. Now, finally, we have been able to fulfill that request.
 
diff --git a/docs/announcements/en/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md b/docs/announcements/en/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
index b84b0ed98..fcb8b8fd0 100644
--- a/docs/announcements/en/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
+++ b/docs/announcements/en/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
@@ -25,6 +25,4 @@ Previously, benefits with payment system conditions were only applied to the mai
 
 In the current scenario, benefits now consider the payment system condition by trade policy. That means that a benefit with payment system filter can be applied to more than one trade policy. With this improvement, the retailer has more flexibility to configure his benefits.
 
-<div class="alert alert-danger">
-It is important to note that this feature <strong>is not valid</strong> for third party trade policies.
-</div>
+>❗ It is important to note that this feature **is not valid** for third party trade policies.
diff --git a/docs/announcements/en/boost-your-marketplace-sales.md b/docs/announcements/en/boost-your-marketplace-sales.md
index aa798e3c2..b3a39b454 100644
--- a/docs/announcements/en/boost-your-marketplace-sales.md
+++ b/docs/announcements/en/boost-your-marketplace-sales.md
@@ -34,6 +34,4 @@ If your store has __an external marketplace integration__ (and you want to use t
 
 If your store is integrated with __VTEX's certified marketplaces__ (using the Bridge module), the flag will be activated automatically. You'll only need to fulfill the instructions described on items `2` and `3`.
 
-<div class="alert alert-info">
-Remember that order integrations need to be done using the <a href="https://developers.vtex.com/reference/orders#getorder">Get Order</a> and <a href="https://developers.vtex.com/reference/feed-v2-deprecated#getfeedorderstatus">Get Feed Order Status</a> APIs.
-</div>
+>ℹ️ Remember that order integrations need to be done using the [Get Order](https://developers.vtex.com/reference/orders#getorder) and [Get Feed Order Status](https://developers.vtex.com/reference/feed-v2-deprecated#getfeedorderstatus) APIs.
diff --git a/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 3c39e4e17..bebe17c3a 100644
--- a/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/en/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -41,9 +41,7 @@ The solution is a combination of:
 - **Last Mile:** Store operators can manage and instruct delivery drivers about collecting and delivering orders. It includes route optimization and proof of collecting/delivering. Besides, your store can easily integrate with external carriers or a TMS. It also includes a URL where shoppers can track their orders' status in real time.   
 - **Mobile apps:** Apps for mobile devices meant exclusively for pickers and drivers, so that they accomplish their tasks with no access to the store’s Admin. Currently, the apps are available only for Android devices.
 
-<div class="alert alert-danger">
-<b>VTEX Pick and Pack</b> is not an invoicing system and orders should be invoiced orders through VTEX's OMS, learn more in <a href="https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT">Invoicing an order</a>.
- </div>
+>❗ **VTEX Pick and Pack** is not an invoicing system and orders should be invoiced orders through VTEX's OMS, learn more in [Invoicing an order](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT).
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md b/docs/announcements/en/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
index 203737eda..8982f80e5 100644
--- a/docs/announcements/en/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
+++ b/docs/announcements/en/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
@@ -60,6 +60,4 @@ The updates are mainly intended for those scenarios where a single order has pro
 This update __doesn't require__ any actions. If your store already uses the __version 4 of the orderPlaced__, which is fully compatible with the [Omnichannel](/en/announcement/shift-your-business-with-vtexs-omnichannel-experience) features, the new logic is already on.
 
 
-<div class="alert alert-warning">
-It's an update on the <strong>version 4 of orderPlaced only</strong>, and it doesn't affect the behavior of previous versions.
-</div>
+>⚠️ It's an update on the **version 4 of orderPlaced only**, and it doesn't affect the behavior of previous versions.
diff --git a/docs/announcements/en/changes-in-the-types-of-conversation-tracker-masks.md b/docs/announcements/en/changes-in-the-types-of-conversation-tracker-masks.md
index 3df4f2153..634b05b79 100644
--- a/docs/announcements/en/changes-in-the-types-of-conversation-tracker-masks.md
+++ b/docs/announcements/en/changes-in-the-types-of-conversation-tracker-masks.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisEN: 'This announcement refers to terms used only in Portuguese and Spanish. Read it in those languages to find out more.'
 ---
 
-<div class="alert alert-info">
-<p>This change refers to terms used only in Portuguese and Spanish. Read this announcement in Portuguese or Spanish to find out more.</p>
-</div>
+>ℹ️ This change refers to terms used only in Portuguese and Spanish. Read this announcement in Portuguese or Spanish to find out more.
diff --git a/docs/announcements/en/changes-in-vtex-support-service-policy.md b/docs/announcements/en/changes-in-vtex-support-service-policy.md
index c20713eed..3b752ac3f 100644
--- a/docs/announcements/en/changes-in-vtex-support-service-policy.md
+++ b/docs/announcements/en/changes-in-vtex-support-service-policy.md
@@ -15,4 +15,4 @@ announcementImageID: ''
 announcementSynopsisEN: 'Now, the main channel to open a ticket is the VTEX Community.'
 ---
 
-<div class="alert alert-info">This content is being translated.</div>
+>ℹ️ This content is being translated.
diff --git a/docs/announcements/en/check-your-stores-caa-record.md b/docs/announcements/en/check-your-stores-caa-record.md
index b4b570fee..80a262061 100644
--- a/docs/announcements/en/check-your-stores-caa-record.md
+++ b/docs/announcements/en/check-your-stores-caa-record.md
@@ -17,9 +17,7 @@ announcementSynopsisEN: 'We recommend you to update your CAA record on your DNS
 
 With __Black Friday__ just around the corner, we recommend you to update the CAA records of your DNS management system until __November 9__. This is an action required to generate and update the SSL certificates, necessary to use VTEX's CDN.
 
-<div class="alert alert-warning">
-<strong>Attention:</strong> Depending on your DNS management system, this kind of entry may not be available. However, sometimes those services offer the possibility of managing the CAA records through their support channel.
-</div>
+>⚠️ **Attention:** Depending on your DNS management system, this kind of entry may not be available. However, sometimes those services offer the possibility of managing the CAA records through their support channel.
 
 ## What you need to do
 Check on your DNS management setup (or ask someone responsible for managing your store's domains) if the following records are set up like the examples below:
@@ -33,9 +31,7 @@ Check on your DNS management setup (or ask someone responsible for managing your
 ## What's the impact?
 Setting up the new CAA records will only allow the __Digicert__, __Comodo__, __Globalsign__, and __Let's encrypt__ entities to generate and renew certificates for your domain. __These certificates are actually requirements for your store to use VTEX's CDN and achieve superior performance.__ If you don't update the CAA records, your store will experience performance issues and will have a slower loading speed.
 
-<div class="alert alert-info">
-Stores that don't have CAA records set up <strong>don't need to do anything</strong> and <strong>won't have impacts</strong>.
-</div>
+>ℹ️ Stores that don't have CAA records set up **don't need to do anything** and **won't have impacts**.
 
 
 ## Useful resources
diff --git a/docs/announcements/en/checkout-api-improvements-part-1.md b/docs/announcements/en/checkout-api-improvements-part-1.md
index f65a96f1e..5089b55f2 100644
--- a/docs/announcements/en/checkout-api-improvements-part-1.md
+++ b/docs/announcements/en/checkout-api-improvements-part-1.md
@@ -19,9 +19,7 @@ Our development team is constantly striving towards improving API performance, b
 
 By updating you on the latest developments, we suggest that you already start the process of updating your store's integrations and customizations, with an eye on the latest solutions offered by our system. 
 
-<div class="alert alert-warning">
-The layout of the current Checkout API continues to function normally, however, it is imperative to start implementing the improvements described below. Even though no official launch date for the new Checkout API has been set yet, we can confirm that the features described below will be discontinued.
-</div>
+>⚠️ The layout of the current Checkout API continues to function normally, however, it is imperative to start implementing the improvements described below. Even though no official launch date for the new Checkout API has been set yet, we can confirm that the features described below will be discontinued.
 
 ## Cart and order address
 
diff --git a/docs/announcements/en/close-bigger-deals-with-the-shared-cart.md b/docs/announcements/en/close-bigger-deals-with-the-shared-cart.md
index dbb52e1ef..9864464e9 100644
--- a/docs/announcements/en/close-bigger-deals-with-the-shared-cart.md
+++ b/docs/announcements/en/close-bigger-deals-with-the-shared-cart.md
@@ -41,8 +41,6 @@ The shared cart is only possible because of a new parameter on the checkout's UR
 - Use [VTEX's APIs](https://github.com/vtex/vtex.js/tree/master/docs/checkout#getorderformexpectedorderformsections) to obtain the shopping cart's ID.
 - Customize the cart's page to let the link display the ID.
 
-<div class="alert alert-warning">
-Remember that the shared cart is an optional feature. Therefore, the changes pointed out in this article must be performed <strong>only by stores that intend to use it</strong>.
-</div>
+>⚠️ Remember that the shared cart is an optional feature. Therefore, the changes pointed out in this article must be performed **only by stores that intend to use it**.
 
 Read the [article about the shared cart](/en/tutorial/what-is-the-shared-cart) and learn more about this new feature.
diff --git a/docs/announcements/en/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md b/docs/announcements/en/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
index 365d985f1..702e7432c 100644
--- a/docs/announcements/en/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
+++ b/docs/announcements/en/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
@@ -31,9 +31,7 @@ Contact the operation's IT team which is responsible for the network firewall se
 
 This team will need to __revise the firewall rules and tweak them to ensure the vtexassets.com domain's access__.
 
-<div class="alert alert-info">
-Note: You will not need to make any adjustments in the front end as the domain <code>vteximg.com.br</code> will continue to work for customizations.
-</div>
+>ℹ️ Note: You will not need to make any adjustments in the front end as the domain `vteximg.com.br` will continue to work for customizations.
 
 ## What impact may befall your operation if the adjustment does not occur?
 
diff --git a/docs/announcements/en/delivery-capacity.md b/docs/announcements/en/delivery-capacity.md
index f81e7e05f..ed75ab887 100644
--- a/docs/announcements/en/delivery-capacity.md
+++ b/docs/announcements/en/delivery-capacity.md
@@ -40,7 +40,5 @@ To use the delivery capacity feature, you need to set up a shipping policy to en
 
 To learn how to configure it for your scheduled deliveries, read the article [Delivery Capacity](https://help.vtex.com/en/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
-<div class="alert alert-info">
-This functionality is in Beta and is currently available only in v3 Admin environments.
-</div>
+>ℹ️ This functionality is in Beta and is currently available only in v3 Admin environments.
 
diff --git a/docs/announcements/en/discontinuation-of-order-completed-order-create-error-and-order-creation.md b/docs/announcements/en/discontinuation-of-order-completed-order-create-error-and-order-creation.md
index 9217b140f..be82a1152 100644
--- a/docs/announcements/en/discontinuation-of-order-completed-order-create-error-and-order-creation.md
+++ b/docs/announcements/en/discontinuation-of-order-completed-order-create-error-and-order-creation.md
@@ -19,9 +19,7 @@ Starting June 24<sup>th</sup> 2019, the following Fulfillment order statuses wil
 
 Fulfillment originated orders are those related to the delivery or pick-up stages of an order. We can associate orders who have this origin to the process that a seller undergoes to have an order delivered or picked-up.
 
-<div class="alert alert-warning">
-Status of orders originating in a Marketplace will not be affected.
-</div>
+>⚠️ Status of orders originating in a Marketplace will not be affected.
 
 ## Why is VTEX taking this action
 
diff --git a/docs/announcements/en/discontinuation-of-vtex-payment.md b/docs/announcements/en/discontinuation-of-vtex-payment.md
index 3015d15d4..6db8e23d8 100644
--- a/docs/announcements/en/discontinuation-of-vtex-payment.md
+++ b/docs/announcements/en/discontinuation-of-vtex-payment.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisEN: 'Discontinuation of VTEX Payment'
 ---
 
-<div class="alert alert-warning">
-This content is not available for this language because VTEX Payment is only available for Brazilian stores.
-</div>
+>⚠️ This content is not available for this language because VTEX Payment is only available for Brazilian stores.
diff --git a/docs/announcements/en/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md b/docs/announcements/en/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
index b4d1acc80..dfe444239 100644
--- a/docs/announcements/en/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
+++ b/docs/announcements/en/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
@@ -31,6 +31,4 @@ Generally speaking, the discontinuation of these statuses should not affect any
 
 In any case, we recommend you revise your integration in order to confirm that these statuses are in fact not in use.
 
-<div class="alert alert-info">
-The workflow removal from the purchase closing critical path for Fulfillment orders has already been done. Read the following article for more on <a href="https://help.vtex.com/en/announcements/discontinuation-of-order-completed-order-create-error-and-order-creation--4AJyu9fJNSKNpL4g4dfgcp">fulfillment orders workflow removal.</a>
-</div>
+>ℹ️ The workflow removal from the purchase closing critical path for Fulfillment orders has already been done. Read the following article for more on [fulfillment orders workflow removal.](https://help.vtex.com/en/announcements/discontinuation-of-order-completed-order-create-error-and-order-creation--4AJyu9fJNSKNpL4g4dfgcp)
diff --git a/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 3ced52386..b89fb5a9b 100644
--- a/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/en/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Possibility to limit user access to order authorizations'
 ---
 
-<div class="alert alert-warning">
-From June 25<sup>th</sup>, 2019, users without access to <code>Order Authorization</code> will not be allowed to neither view nor edit the Order Authorization screen. 
-</div>
+>⚠️ From June 25<sup>th</sup>, 2019, users without access to `Order Authorization` will not be allowed to neither view nor edit the Order Authorization screen.
 
 Seeking to ensure greater safety, we created the possibility to limit user access to order authorizations, allowing information to be edited or viewed by selected users. For more on Order Authorization, have a look at our [feature launch announcement](https://help.vtex.com/announcements/increase-your-sales-with-the-new-order-authentication-screen--7EXIgaESHfI46lkaZw9jrQ) or read [this tutorial explaining how it works](https://help.vtex.com/tutorial/how-order-authorisation-works--3MBK6CmKHAuUjMBieDU0pn).
 
diff --git a/docs/announcements/en/erp-integration-guides-have-a-new-home.md b/docs/announcements/en/erp-integration-guides-have-a-new-home.md
index f6c24a461..a6371cf42 100644
--- a/docs/announcements/en/erp-integration-guides-have-a-new-home.md
+++ b/docs/announcements/en/erp-integration-guides-have-a-new-home.md
@@ -27,5 +27,5 @@ As part of our ongoing effort of developer documentation migration to our Develo
 
 This brand new documentation uses the new [Catalog REST API](https://developers.vtex.com/docs/guides/catalog-api-overview) and replaces our prior guide that used the Webservice SOAP API, which is no longer available in our Help Center.
 
-<div class="alert alert-warning">We have not yet deprecated the Webservice SOAP API, but it is no longer recommended for new integrations.</div>
+>⚠️ We have not yet deprecated the Webservice SOAP API, but it is no longer recommended for new integrations.
 
diff --git a/docs/announcements/en/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md b/docs/announcements/en/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
index 0d365ce97..91362a146 100644
--- a/docs/announcements/en/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
+++ b/docs/announcements/en/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
@@ -24,9 +24,7 @@ Therefore, after an objective and thorough analysis, we have decided to remove t
 
 The Facebook login feature will be removed from all versions of the VTEX admin panel.
 
-<div class="alert alert-info">
-The Facebook login feature will still be available for customers to log in to your VTEX store.
-</div>
+>ℹ️ The Facebook login feature will still be available for customers to log in to your VTEX store.
 
 ## Why are we making this change?
 
diff --git a/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
index 4cbb62525..e107e210c 100644
--- a/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
+++ b/docs/announcements/en/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -48,9 +48,7 @@ FastCheckout allows you to create a customizable checkout experience, adapting t
 
 We allow you to add fully custom elements, without having to be familiar with JavaScript or CSS.
 
-<div class="alert alert-warning">
-  <p>The first version released of FastCheckout allows limited customization. Soon, you will be able to fully customize the content using the FastStore Platform extensions.</p>
-</div>
+>⚠️ The first version released of FastCheckout allows limited customization. Soon, you will be able to fully customize the content using the FastStore Platform extensions.
 
 ### New purchase flow
 
diff --git a/docs/announcements/en/freely-develop-custom-storefront-components-in-vtex-io.md b/docs/announcements/en/freely-develop-custom-storefront-components-in-vtex-io.md
index c13876a67..47b6d8ff0 100644
--- a/docs/announcements/en/freely-develop-custom-storefront-components-in-vtex-io.md
+++ b/docs/announcements/en/freely-develop-custom-storefront-components-in-vtex-io.md
@@ -24,9 +24,7 @@ If your store is built using the [VTEX Store Framework](https://developers.vtex.
 
 From now on, **develop custom storefront components in [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io) using the VTEX Store Framework and [React](https://reactjs.org/) technologies** according to your business needs, without asking VTEX for permission. 
 
-<div class="alert alert-info">
-Store Framework is the VTEX solution to build storefront in lightning speed. VTEX customers can leverage all its benefits by using the VTEX IO development platform. If you are not familiar with the VTEX IO yet, get in touch with your Customer Success, Account Manager or SI Partner Agency to know how to start! 
-</div>
+>ℹ️ Store Framework is the VTEX solution to build storefront in lightning speed. VTEX customers can leverage all its benefits by using the VTEX IO development platform. If you are not familiar with the VTEX IO yet, get in touch with your Customer Success, Account Manager or SI Partner Agency to know how to start!
 
 ## What changed?
 
@@ -34,9 +32,7 @@ Before,  developers interested in creating custom components using the VTEX Stor
 
 This is no longer required as **we officially move our React builder to open beta status**. You can take advantage of this autonomy to further customize and improve your storefront experience using React technology. 
 
-<div class="alert alert-warning">
-<bold>This change applies only to the React builder.</bold> We continue to require that you fill in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">Application form for development</a> and wait for our approval if your project depends on builders that are still in closed beta. This includes, for example, back-end integrations using Node.js and GraphQL.  
-</div>
+>⚠️ <bold>This change applies only to the React builder.</bold> We continue to require that you fill in the [Application form for development](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io) and wait for our approval if your project depends on builders that are still in closed beta. This includes, for example, back-end integrations using Node.js and GraphQL.
 
 ## Why did we make this change?
 
@@ -46,7 +42,5 @@ We understand that VTEX IO has now reached enough maturity and stability as a de
 
 No actions are needed from your side. Keep in mind, however, that **VTEX does not provide support to custom components developed by third-parties**. Their maintenance, performance, and quality is under the responsibility of the app's vendor.
 
-<div class="alert alert-info">
-Check out our documentation on <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-developing-custom-storefront-components">best practices for storefront component development</a>!
-</div>
+>ℹ️ Check out our documentation on [best practices for storefront component development](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-developing-custom-storefront-components)!
 
diff --git a/docs/announcements/en/from-now-on-you-can-create-promotional-price-tables.md b/docs/announcements/en/from-now-on-you-can-create-promotional-price-tables.md
index dee56d9c5..6f73ebf41 100644
--- a/docs/announcements/en/from-now-on-you-can-create-promotional-price-tables.md
+++ b/docs/announcements/en/from-now-on-you-can-create-promotional-price-tables.md
@@ -35,12 +35,8 @@ In case you still don't have a price table (or wish to create a new one), the [S
 
 After going through all the steps above, your promotional price table will be active and ready to use. Remember that it usually takes __10 minutes__ before a given benefit becomes available on your store.
 
-<div class="alert alert-info">
-The benefits that use price tables have a few characteristics that you must take into consideration while using them:</br>
-<strong>1-</strong> The price on the price table will only be applied if it is lower than the one defined on your store sales policy. <em>For example:</em> Imagine an item sold at $ 199,00. The price table will only alter this value if it was filled with a lower price.</br>
-<strong>2-</strong> Benefits which use price tables concur with each other and with all other benefits which interfere directly on prices. In other words, if there is more than one price table set on your store and, at least, one other active promotion (of the percentage, nominal, or formula types), the lowest value among them will be the one applied.
-</div>
-
-<div class="alert alert-warning">
-You can only set a <strong>single price table per benefit</strong>. Also, today we have a limit of <strong>5 simultaneous price tables</strong> for each store.
-</div>
+>ℹ️ The benefits that use price tables have a few characteristics that you must take into consideration while using them:</br>
+> **1-** The price on the price table will only be applied if it is lower than the one defined on your store sales policy. *For example:* Imagine an item sold at $ 199,00. The price table will only alter this value if it was filled with a lower price.</br>
+> **2-** Benefits which use price tables concur with each other and with all other benefits which interfere directly on prices. In other words, if there is more than one price table set on your store and, at least, one other active promotion (of the percentage, nominal, or formula types), the lowest value among them will be the one applied.
+
+>⚠️ You can only set a **single price table per benefit**. Also, today we have a limit of **5 simultaneous price tables** for each store.
diff --git a/docs/announcements/en/from-now-on-you-can-export-up-to-3-thousand-orders.md b/docs/announcements/en/from-now-on-you-can-export-up-to-3-thousand-orders.md
index fa4e6c634..390f334ab 100644
--- a/docs/announcements/en/from-now-on-you-can-export-up-to-3-thousand-orders.md
+++ b/docs/announcements/en/from-now-on-you-can-export-up-to-3-thousand-orders.md
@@ -23,6 +23,4 @@ To ensure the best experience possible, we've been recommending the 3.000 orders
 ## How to export more than 3.000 orders
 You can still export more than 3.000 orders. To do so, you must use our orders management (formerly known as OMS) APIs: [Get Order](https://developers.vtex.com/reference/orders#getorder) and [Get Feed Order Status](https://developers.vtex.com/reference/feed-v3#getfeedorderstatus1).
 
-<div class="alert alert-warning">
-<strong>But remember:</strong> For it to work, it's necessary to <strong>create a date/hour range that includes up to 3.000 orders</strong>. After defining a range that respects this limit, you'll be able to make as many requests to the API as you want.
-</div>
+>⚠️ **But remember:** For it to work, it's necessary to **create a date/hour range that includes up to 3.000 orders**. After defining a range that respects this limit, you'll be able to make as many requests to the API as you want.
diff --git a/docs/announcements/en/google-catalog-migration.md b/docs/announcements/en/google-catalog-migration.md
index d962b2d29..f697df894 100644
--- a/docs/announcements/en/google-catalog-migration.md
+++ b/docs/announcements/en/google-catalog-migration.md
@@ -23,9 +23,7 @@ This feature is designed for sellers who previously integrated their store's pro
 
 This feature enables sellers to maintain the relevance of their Google Shopping ads. By migrating your integration to the VTEX connector, you preserve the relevance history of your ads.
 
-<div class="alert alert-info">
-Catalog migration maps and matches products in the VTEX catalog with the existing ads in the Google Merchant Center.
-</div>
+>ℹ️ Catalog migration maps and matches products in the VTEX catalog with the existing ads in the Google Merchant Center.
 
 Catalog migration maps and matches products in the VTEX catalog with the existing ads in the Google Merchant Center.
 
diff --git a/docs/announcements/en/headless-cms-events-available-in-audit.md b/docs/announcements/en/headless-cms-events-available-in-audit.md
index 25a98f823..7c215093e 100644
--- a/docs/announcements/en/headless-cms-events-available-in-audit.md
+++ b/docs/announcements/en/headless-cms-events-available-in-audit.md
@@ -38,9 +38,7 @@ In the **Action** column, all Headless CMS events also display the following inf
 * **VARIANT_ID:** unique identifier of the content version.
 * **WORKSPACE**: workspace where the action occurred.
 
-<div class="alert alert-info">
-  <p>Check the complete <a href="https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">list of events available in Audit</a>.</p>
-</div>
+>ℹ️ Check the complete [list of events available in Audit](https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## What needs to be done?
 No action is required. The change in Audit is already active for all accounts, recording the [list of events](#what-has-changed) mentioned above.
diff --git a/docs/announcements/en/improvement-of-the-seller-white-label-selection-algorithm.md b/docs/announcements/en/improvement-of-the-seller-white-label-selection-algorithm.md
index 963933dea..9ec2f3972 100644
--- a/docs/announcements/en/improvement-of-the-seller-white-label-selection-algorithm.md
+++ b/docs/announcements/en/improvement-of-the-seller-white-label-selection-algorithm.md
@@ -27,9 +27,7 @@ The seller selection algorithm was updated to ensure the maximum possible covera
 
 Also, for selecting sellers that offer a pickup option, the algorithm will always prioritize distance to the reference location over price and pickup time criteria.
 
-<div class="alert alert-warning">
-Note: The algorithm update applies to White Label Seller, and it includes <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">Franchise Accounts</a>. The seller selection algorithm is applied when the client checks the delivery options. That means that it is applied in the delivery preview in the cart or in the delivery and pickup stage at checkout.
-</div>
+>⚠️ Note: The algorithm update applies to White Label Seller, and it includes [Franchise Accounts](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa). The seller selection algorithm is applied when the client checks the delivery options. That means that it is applied in the delivery preview in the cart or in the delivery and pickup stage at checkout.
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/integration-methods-with-the-catalog-through-web-service-will-be.md b/docs/announcements/en/integration-methods-with-the-catalog-through-web-service-will-be.md
index d5a0bb335..1c5a4e021 100644
--- a/docs/announcements/en/integration-methods-with-the-catalog-through-web-service-will-be.md
+++ b/docs/announcements/en/integration-methods-with-the-catalog-through-web-service-will-be.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'On 10/29, we will discontinue some Web Service methods for integration with the catalog.'
 ---
 
-<div class="alert alert-info">
-The change described here only impacts your operation if your store uses <b>Web Service integration</b> and this integration uses some of the methods listed below. Otherwise, you do <b>not</b> need to take any action.
-</div>
+>ℹ️ The change described here only impacts your operation if your store uses **Web Service integration** and this integration uses some of the methods listed below. Otherwise, you do **not** need to take any action.
 
 As of __October 29__, VTEX will discontinue the following methods of integration by Web Service, with the aim of improving the platform performance.
 
diff --git a/docs/announcements/en/integrations-with-vtex-apis-now-need-token-authentication.md b/docs/announcements/en/integrations-with-vtex-apis-now-need-token-authentication.md
index 9b7bccc57..f5e2533e4 100644
--- a/docs/announcements/en/integrations-with-vtex-apis-now-need-token-authentication.md
+++ b/docs/announcements/en/integrations-with-vtex-apis-now-need-token-authentication.md
@@ -37,4 +37,4 @@ Using the email and password for authentication compromises the security of your
 - Check if your store uses email and password in any integration with VTEX APIs.
 - If it does, create a pair of appKey and appToken for that integration. See how to do that in the article [Creating appKeys and appTokens to authenticate integrations](http://help.vtex.com/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations).
 
-<div class="alert alert-warning"><strong>Attention</strong>: any pair of appKey and appToken, when created, is born without being linked to a role. So, after creating it, you need to link the appKey and appToken to the correspondent role.</div>
+>⚠️ **Attention**: any pair of appKey and appToken, when created, is born without being linked to a role. So, after creating it, you need to link the appKey and appToken to the correspondent role.
diff --git a/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
index 3f9e39a9b..c9ffb4e98 100644
--- a/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/en/introducing-the-new-shipping-strategy-interfaces.md
@@ -38,7 +38,5 @@ Starting from May 31st, the beta version of **Shipping Strategy** is available f
 
 After testing it, if you wish to go back to the previous version, click the menu <i class="fas fa-ellipsis-v"></i> at the top of the page, select `Switch to Previous Version` and give us some feedback. The return to the previous experience will be automatic.
 
-<div class="alert alert-warning">
-Starting from July 26th, the new <b>Shipping Strategy</b> interfaces will be the standard for all VTEX stores.
-</div>
+>⚠️ Starting from July 26th, the new **Shipping Strategy** interfaces will be the standard for all VTEX stores.
 
diff --git a/docs/announcements/en/introducing-vtex-ad-network-beta.md b/docs/announcements/en/introducing-vtex-ad-network-beta.md
index dfb9dc3df..53eef9693 100644
--- a/docs/announcements/en/introducing-vtex-ad-network-beta.md
+++ b/docs/announcements/en/introducing-vtex-ad-network-beta.md
@@ -39,9 +39,7 @@ See below how you can join **VTEX Ad Network** as a merchant or an advertiser.
 
 To make ad space available in your store, install the [VTEX Ad Network for stores]() app in your VTEX account. Learn more in the [Displaying VTEX Ad Network ads in your store (Beta)](https://help.vtex.com/en/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA) article.
 
-<div class="alert alert-danger">
-Currently, only stores developed with <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> can offer ad space.
-</div>
+>❗ Currently, only stores developed with [Store Framework](https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) can offer ad space.
 
 ### Advertisers
 
diff --git a/docs/announcements/en/last-chance-to-buy-tickets-for-vtex-training-day.md b/docs/announcements/en/last-chance-to-buy-tickets-for-vtex-training-day.md
index c54cb4e6b..542e58aa0 100644
--- a/docs/announcements/en/last-chance-to-buy-tickets-for-vtex-training-day.md
+++ b/docs/announcements/en/last-chance-to-buy-tickets-for-vtex-training-day.md
@@ -38,9 +38,7 @@ The stage for VTEX IO, VTEX's development platform. Our engineers will explain a
 <br />
 <br />
 
-<div class="alert alert-info">
-<strong>Get 30% off</strong> buying 10 or more tickets! But hurry up, because this condition will only be available until the end of November.
-</div>
+>ℹ️ **Get 30% off** buying 10 or more tickets! But hurry up, because this condition will only be available until the end of November.
 
 
 __When:__ 06/12/2018 _(all day long)_ 
diff --git a/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
index 5d9661957..9e4451e99 100644
--- a/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
+++ b/docs/announcements/en/lead-time-configuring-shipping-time-at-sku-level.md
@@ -33,9 +33,7 @@ Now, you can also configure the shipping time at SKU level with the new lead tim
 
 ![lead_time_inventory_management_EN](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png) 
 
-<div class="alert alert-warning">
-In the VTEX Admin, the lead time is configured in days, with a 365-day limit. By default, the days are calculated in business days, but you can configure your shipping policy to <a href="https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configuring-lead-time-calculation-in-calendar-days-optional">calculate them in calendar days</a>. You need to use the <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a> endpoint to configure periods in hours, minutes, and seconds.
-</div>
+>⚠️ In the VTEX Admin, the lead time is configured in days, with a 365-day limit. By default, the days are calculated in business days, but you can configure your shipping policy to [calculate them in calendar days](https://help.vtex.com/en/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configuring-lead-time-calculation-in-calendar-days-optional). You need to use the [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-) endpoint to configure periods in hours, minutes, and seconds.
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md b/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md
index df291872b..a0a7ed551 100644
--- a/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md
+++ b/docs/announcements/en/legacy-payment-connectors-will-be-discontinued-in-2024.md
@@ -19,9 +19,7 @@ To integrate payment methods to the VTEX platform, payment providers can create
 
 ## What has changed?
 
-<div class="alert alert-danger">
-These changes will not affect Black Friday 2023. They will only be implemented in the first quarter of 2024.
-</div>
+>❗ These changes will not affect Black Friday 2023. They will only be implemented in the first quarter of 2024.
 
 VTEX is initiating the discontinuation of these legacy connectors, which will happen gradually:
 
@@ -109,9 +107,7 @@ If you are a payment provider managing one or more [connectors being discontinue
 
 In this case, we recommend that you submit your new connector for approval by February 10, 2024, so that stores have time to reconfigure their payment connections before discontinuation. Learn more about the [approval process for new payment connectors](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
 
-<div class="alert alert-danger">
-VTEX cannot guarantee that your new payment connector will be available to VTEX merchants before the official discontinuation if you submit it for approval after this date.
-</div>
+>❗ VTEX cannot guarantee that your new payment connector will be available to VTEX merchants before the official discontinuation if you submit it for approval after this date.
 
 If you have any questions about this process or would like to align joint communication with merchants, please contact your VTEX Partner Manager.
 
diff --git a/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
index a7e8ba235..4b875f40c 100644
--- a/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
+++ b/docs/announcements/en/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -35,6 +35,4 @@ Having a payment transaction declined due to an invalid card number could lead c
 
 No action is required. The Luhn algorithm is already active in all VTEX stores.
 
-<div class="alert alert-warning">
-The Luhn algorithm does not prevent fraud through card testing attacks. Its purpose is to detect typing errors in card numbers.
-</div>
+>⚠️ The Luhn algorithm does not prevent fraud through card testing attacks. Its purpose is to detect typing errors in card numbers.
diff --git a/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
index 3f966fdb4..202a6784d 100644
--- a/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/en/maximum-price-per-item-promotion-will-be-disabled.md
@@ -21,9 +21,9 @@ Actually, we are making this change precisely because, with the development of t
 
 By eliminating the Maximum Price per Item promotion, we are improving the performance of the promotions module as well as the store management.
 
-<div class="alert alert-warning">Until November 20, the Maximum Price per Item promotion continues to exist. However, the maximum number of items allowed becomes <b>100</b>. Previously the maximum allowed was 500.</div>
+>⚠️ Until November 20, the Maximum Price per Item promotion continues to exist. However, the maximum number of items allowed becomes **100**. Previously the maximum allowed was 500.
 
-<div class="alert alert-danger">If you use any Maximum Price per Item promotion, read this announcement through the end and adapt the method in your store. Otherwise, the SKUs concerned will no longer be impacted by this business strategy.</div>
+>❗ If you use any Maximum Price per Item promotion, read this announcement through the end and adapt the method in your store. Otherwise, the SKUs concerned will no longer be impacted by this business strategy.
 
 ## Alternatives
 
diff --git a/docs/announcements/en/multi-currency-gift-card.md b/docs/announcements/en/multi-currency-gift-card.md
index 37193d8b3..371022bed 100644
--- a/docs/announcements/en/multi-currency-gift-card.md
+++ b/docs/announcements/en/multi-currency-gift-card.md
@@ -43,6 +43,4 @@ To create a gift card using a specific currency, follow the steps below:
 
 The currencies available will be the same as those in the [trade policies](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) of each store.
 
-<div class="alert alert-warning">
-You must choose the currency when creating each gift card or a batch of gift cards since you cannot change the gift card currency after it has been created.
-</div>
+>⚠️ You must choose the currency when creating each gift card or a batch of gift cards since you cannot change the gift card currency after it has been created.
diff --git a/docs/announcements/en/my-authentication-section-in-my-account.md b/docs/announcements/en/my-authentication-section-in-my-account.md
index a4018efc3..4295cab56 100644
--- a/docs/announcements/en/my-authentication-section-in-my-account.md
+++ b/docs/announcements/en/my-authentication-section-in-my-account.md
@@ -17,9 +17,7 @@ announcementSynopsisEN: 'My authentication is a section in My account that allow
 
 The My Authentication section is available on all VTEX accounts, and you can find it on the My account dashboard in your store.
 
-<div class="alert alert-danger">
-This change will affect all VTEX stores. Because this change interferes with some components in the store UI, you are required to make some changes in your store’s settings until September 29, 2021.
-</div>
+>❗ This change will affect all VTEX stores. Because this change interferes with some components in the store UI, you are required to make some changes in your store’s settings until September 29, 2021.
 
 ## What has changed?
 
@@ -55,9 +53,7 @@ Enabling a new section means a new element will be added to your store’s UI, w
 - If your store uses VTEX IO, access the URL `https://{account}.myvtex.com/account#/authentication`, replacing `{account}` with the name of your account.
 - If your store does not use VTEX IO, access the URL `https://{account}.vtexcommercestable.com.br/_secure/account#/authentication`, replacing `{account}` with the name of your account.
 
-<div class="alert alert-warning">
-Before accessing the URL, you need to log in to your store with a user account.
-</div>
+>⚠️ Before accessing the URL, you need to log in to your store with a user account.
 
 To customize the section appearance, ask the developer responsible to follow the instructions in the article [My Authentication Customization Guide using CMS](https://developers.vtex.com/vtex-rest-api/docs/ui-customization-my-authentication), if your store does not use VTEX IO. For stores using VTEX IO, check out the article [My Authentication Customization Guide on VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-my-authentication) in our developer portal.
 
diff --git a/docs/announcements/en/my-orders-is-now-available-on-extension-store.md b/docs/announcements/en/my-orders-is-now-available-on-extension-store.md
index e7505b4c0..452832f7b 100644
--- a/docs/announcements/en/my-orders-is-now-available-on-extension-store.md
+++ b/docs/announcements/en/my-orders-is-now-available-on-extension-store.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: "Starting June 5, the use of the 'My Orders' page's extension will be required for all stores."
 ---
 
-<div class="alert alert-info">
-As announced here, <strong>My Orders extension</strong> is already mandatory to all stores. Since <strong>June 6</strong>, it is available by default and is not accessible through VTEX's App Store anymore.
-</div>
+>ℹ️ As announced here, **My Orders extension** is already mandatory to all stores. Since **June 6**, it is available by default and is not accessible through VTEX's App Store anymore.
 
 The __My Orders__ extension is already available on VTEX's __App Store__, bringing lots of improvements to the "My Orders" page. Because of all the benefits it delivers (including easier customization and better performance), it's use will be mandatory as of __June 5__.
 
@@ -25,7 +23,7 @@ Among the new features are: visualization support for attachments and bundle ite
 
 Another important thing is that the extension gets order's data from the OMS's API. This gives more precision to the order's status.
 
-<div class="alert alert-warning">
-<strong>Atention</strong><br>
-We recommend you to install the <strong>My Orders</strong> extension in your store as soon as possible, specially if it's "My Orders" page has any customizations. In doing so, you'll be able to test all the new features and prevent crashes when the migration is completed.
-</div>
+>⚠️ **Atention**
+>
+> 
+> We recommend you to install the **My Orders** extension in your store as soon as possible, specially if it's "My Orders" page has any customizations. In doing so, you'll be able to test all the new features and prevent crashes when the migration is completed.
diff --git a/docs/announcements/en/new-deadline-activate-the-new-cdn-until-may-31.md b/docs/announcements/en/new-deadline-activate-the-new-cdn-until-may-31.md
index e9b6d13f6..3e8d9ee15 100644
--- a/docs/announcements/en/new-deadline-activate-the-new-cdn-until-may-31.md
+++ b/docs/announcements/en/new-deadline-activate-the-new-cdn-until-may-31.md
@@ -45,9 +45,7 @@ After enabling HTTPS, you must:
 
 If your store's domain points to anything that contains `vtexcommerce.com.br` or `hodor.vtex.com`, you're still using the old CNAME. The update is necessary because all content will be hosted in `{hostname}.cdn.vtex.com`.
 
-<div class="alert alert-warning">
-After <strong>May 31st</strong>, the old CNAMEs will stop working. <strong>All stores using them will crash</strong>.
-</div>
+>⚠️ After **May 31st**, the old CNAMEs will stop working. **All stores using them will crash**.
 
 After HTTPS is enabled and your store is updated with VTEX's new CNAME, you'll need to request the activation of the new CDN. If you don't do this until __May 31st__, the activation will be done automatically. That's why it's so important to follow the instructions already given and reinforced in this announcement: it's the only way to avoid future problems with your store. 
 
diff --git a/docs/announcements/en/new-facebook-business-extension-integration-app.md b/docs/announcements/en/new-facebook-business-extension-integration-app.md
index 1a784d63b..3eb84823f 100644
--- a/docs/announcements/en/new-facebook-business-extension-integration-app.md
+++ b/docs/announcements/en/new-facebook-business-extension-integration-app.md
@@ -62,8 +62,6 @@ The features installed automatically with the app integration also offer several
 
 To integrate your VTEX store with FBE, just follow the steps in the [Facebook Business Extension integration guide](https://help.vtex.com/en/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D).
 
-<div class="alert alert-warning">
-Even if you have already configured the <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Facebook Integration</a>, we recommend you to integrate your store with the <i>Facebook Business Extension and Conversions API</i> app. This will give you access to improved services and new features.
-</div>
+>⚠️ Even if you have already configured the <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Facebook Integration</a>, we recommend you to integrate your store with the <i>Facebook Business Extension and Conversions API</i> app. This will give you access to improved services and new features.
 
 It is worth noting that the two integrations do not interfere with each other. Once the integration with the _Facebook Business Extension and Conversions API_ app is complete, your store will have access to all the services provided by Facebook Business Extension.
diff --git a/docs/announcements/en/new-limits-for-causes-of-benefit.md b/docs/announcements/en/new-limits-for-causes-of-benefit.md
index 08af35081..58a59d9ad 100644
--- a/docs/announcements/en/new-limits-for-causes-of-benefit.md
+++ b/docs/announcements/en/new-limits-for-causes-of-benefit.md
@@ -21,10 +21,9 @@ A cause of benefit is any condition that generates a benefit.
 
 For example: the retailer can set up a benefit to be applied if the customer chooses a particular payment method. In this case, the payment method is the cause of the benefit.
 
-<div class="alert alert-danger">You can't save a benefit that violates any limits. So if your store currently has benefits that exceed any of these limits, be careful.
-
-Any changes to any of these benefits will cause the new limits to apply. Therefore, you will not be able to save the benefit using the previous settings.
-</div>
+>❗ You can't save a benefit that violates any limits. So if your store currently has benefits that exceed any of these limits, be careful.
+>
+> Any changes to any of these benefits will cause the new limits to apply. Therefore, you will not be able to save the benefit using the previous settings.
 
 Here are the new limits for each cause of benefit:
 
diff --git a/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md b/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md
index 3c1406b9b..b88a01887 100644
--- a/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md
+++ b/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md
@@ -77,8 +77,6 @@ Once you have configured the Price Divergence rule, it will apply to all marketp
 
 For VTEX marketplaces, external marketplaces and certified connectors (partners), as long as the Price Divergence rule has not been created, orders with price divergence error are automatically approved.
 
-<div class="alert alert-warning">
-For <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a>, while the seller does not <a href= "https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configure the Price Divergence rule</a>, orders with price divergence are retained. You can track them in your VTEX Admin by clicking on MARKETPLACE > Integrations > Orders.
-</div>
+>⚠️ For <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a>, while the seller does not <a href= "https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configure the Price Divergence rule</a>, orders with price divergence are retained. You can track them in your VTEX Admin by clicking on MARKETPLACE > Integrations > Orders.
 
 If you don't want native connectors to obey the Price Divergence Rule, you can keep the previous flow. In this case, [contact the VTEX support team](https://support.vtex.com/hc/en-us/requests).
diff --git a/docs/announcements/en/new-ready-to-dispatch-functionality.md b/docs/announcements/en/new-ready-to-dispatch-functionality.md
index 6b1c436a0..53fd80852 100644
--- a/docs/announcements/en/new-ready-to-dispatch-functionality.md
+++ b/docs/announcements/en/new-ready-to-dispatch-functionality.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisEN: ' New VTEX Log functionality for label printing and carrier notification.'
 ---
 
-<div class="alert alert-warning">
-This content is not available for this language because the new feature is only available for Brazilian stores that use the VTEX Shipping Network solution. 
-</div> 
+>⚠️ This content is not available for this language because the new feature is only available for Brazilian stores that use the VTEX Shipping Network solution. 
diff --git a/docs/announcements/en/new-rules-for-activating-vtex-support.md b/docs/announcements/en/new-rules-for-activating-vtex-support.md
index 36e10d2b9..498f7b17e 100644
--- a/docs/announcements/en/new-rules-for-activating-vtex-support.md
+++ b/docs/announcements/en/new-rules-for-activating-vtex-support.md
@@ -17,7 +17,7 @@ announcementSynopsisEN: "For accounts in Brazil, it's now required the Open Supp
 
 Now, for Brazil accounts to contact VTEX Support, the  **Open Support Ticket** resource of the **VTEX - Support** product must be enabled in their role. A user with the *User Administrator - Restricted* role must configure this permission in [License Manager](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
 
-<div class="alert alert-info">Admin users with the <strong> Owner (Admin Super) </strong> role are automatically associated with the <em> Open Support Ticket</em> resource.</div> 
+>ℹ️ Admin users with the ** Owner (Admin Super) ** role are automatically associated with the * Open Support Ticket* resource. 
 
 ## What has changed?
 
diff --git a/docs/announcements/en/new-subscriptions-module.md b/docs/announcements/en/new-subscriptions-module.md
index 66a0491a4..711e1840d 100644
--- a/docs/announcements/en/new-subscriptions-module.md
+++ b/docs/announcements/en/new-subscriptions-module.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'The Subscriptions module is the VTEX solution for recurring orders in your store, and it is continuously evolving.'
 ---
 
-<div class="alert alert-info">
-  <p>This update only applies to stores that have the Subscriptions module. For stores that do not use this feature, nothing will change.</p>
-</div>
+>ℹ️ This update only applies to stores that have the Subscriptions module. For stores that do not use this feature, nothing will change.
 
 The Subscriptions module is the VTEX solution for recurring orders in your store, and it is continuously evolving. The module was enhanced to streamline the system performance and deliver new features that improve the customer experience in your store. This article describes all the changes made in the Subscriptions module and how to adapt your store accordingly. 
 
@@ -79,6 +77,4 @@ We also changed the way of calculating the subscription order cycle date. Users
 Remember that if your store does not use our APIs in their integrations, no adaptation is needed on your side. The implementation will be automatic. 
 If you are a retailer or partner that used our subscriptions API, please note that every subscription API route previously defined will be replaced by new ones. You will be assisted by the VTEX team during the entire migration process, ensuring a seamless transition to the new module. Check out our [Integration with the New Subscription Module Guide](https://developers.vtex.com/vtex-developer-docs/docs/subscriptions-v3-migration-guide). 
 
-<div class="alert alert-info">
-You can request the new Subscriptions UI by contacting our customer <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">support</a>. Your store needs to enable and install <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a> in order to use the new UI.  
-</div>
+>ℹ️ You can request the new Subscriptions UI by contacting our customer [support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM). Your store needs to enable and install [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) in order to use the new UI.
diff --git a/docs/announcements/en/new-vtex-shipping-network-performance-page.md b/docs/announcements/en/new-vtex-shipping-network-performance-page.md
index 0fe83ce78..f0f9b6fa5 100644
--- a/docs/announcements/en/new-vtex-shipping-network-performance-page.md
+++ b/docs/announcements/en/new-vtex-shipping-network-performance-page.md
@@ -41,6 +41,4 @@ This update process will be implemented natively. No action is required on your
 
 To better understand how VTEX Shipping Network performance works, check out the article[ Tracking shipping carriers' performance](https://help.vtex.com/en/tutorial/painel-vtex-log--51e8tx1IehiN4ZtURRWU92?&utm_source=autocomplete).
 
-<div class="alert alert-info">
-VTEX Shipping Network is currently available only for Brazil. Learn more about VTEX Shipping Network in the article  <a href="https://vtex.com/br-pt/log/">Discover VTEX Shipping Network, VTEX's delivery solution</a>.
-</div>
+>ℹ️ VTEX Shipping Network is currently available only for Brazil. Learn more about VTEX Shipping Network in the article  [Discover VTEX Shipping Network, VTEX's delivery solution](https://vtex.com/br-pt/log/).
diff --git a/docs/announcements/en/new-working-hours-setup-is-now-available-for-carriers.md b/docs/announcements/en/new-working-hours-setup-is-now-available-for-carriers.md
index e8b120790..4062501ee 100644
--- a/docs/announcements/en/new-working-hours-setup-is-now-available-for-carriers.md
+++ b/docs/announcements/en/new-working-hours-setup-is-now-available-for-carriers.md
@@ -33,10 +33,6 @@ To set up the carrier working hours, follow the steps below:
 ## Next steps
 Soon, we'll enable the definition of more time ranges per day. That way, stores that close during lunch hours, for example, will be able to register those periods too. See the article [Setting up carrier's business hour](https://help.vtex.com/en/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS).
 
-<div class="alert alert-info">
-The default setup comes with all days selected, and working hours from 00:00 to 23:59 (local time).
-</div>
+>ℹ️ The default setup comes with all days selected, and working hours from 00:00 to 23:59 (local time).
 
-<div class="alert alert-warning">
-While using the Carrier business hours option, you won't be able to use cut-off times. That means that you need to choose the option that best suits your store's needs.
-</div>
+>⚠️ While using the Carrier business hours option, you won't be able to use cut-off times. That means that you need to choose the option that best suits your store's needs.
diff --git a/docs/announcements/en/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md b/docs/announcements/en/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
index a7af238e9..e0781f94c 100644
--- a/docs/announcements/en/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
+++ b/docs/announcements/en/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
@@ -27,9 +27,7 @@ You can now easily sell products from your entire network of physical stores in
 
 The only necessary setting is the integration of the main account with the external marketplace. Once this is done, the inventories of all franchise accounts linked to the main one will also be sent to the marketplace. This is a new franchise account feature, which is active and ready to make your life easier whenever you need to integrate your operation with marketplaces.
 
-<div class="alert alert-warning">
-<strong> For now, automatic integration of the franchise accounts inventory is only available when the marketplace is not a VTEX one</strong>. 
-</div>
+>⚠️ ** For now, automatic integration of the franchise accounts inventory is only available when the marketplace is not a VTEX one**.
 
 ## What has changed
 
@@ -41,12 +39,10 @@ The Multilevel Omnichannel Inventory brought a new ally for omnichannel operatio
 
 To learn more about Multilevel Omnichannel Inventory and changes to the Checkout APIs, visit [this Help article](https://help.vtex.com/en/business-guides/offer-the-products-from-your-physical-stores-in-external-marketplaces--6s64bV8Dqb5QN6sqIfPzcA).
 
-<div class="alert alert-danger">
-<body>
-  <li>The Recursive Marketplace is now called <b>Multilevel Omnichannel Inventory.</b></li>
-<li>
-The feature does not allow you to <a href="https://help.vtex.com/en/tutorial/how-to-use-the-change-seller-feature--5TBAwO2kOAMw44uyaaQMQO">change seller.</a></li>
-<li>This solution is aimed at integrating with external marketplaces, not those that are <a href="https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402">natively integrated with VTEX.</a>.</li> 
-<li>Learn more about usage restrictions in the article <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> e confira as restrições de uso detalhadamente.</li>
-   </body>
-</div>
+>❗ <body>
+>   <li>The Recursive Marketplace is now called **Multilevel Omnichannel Inventory.**</li>
+> <li>
+> The feature does not allow you to [change seller.](https://help.vtex.com/en/tutorial/how-to-use-the-change-seller-feature--5TBAwO2kOAMw44uyaaQMQO)</li>
+> <li>This solution is aimed at integrating with external marketplaces, not those that are [natively integrated with VTEX.](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402).</li> 
+> <li>Learn more about usage restrictions in the article [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) e confira as restrições de uso detalhadamente.</li>
+>    </body>
diff --git a/docs/announcements/en/old-versions-of-the-vtex-id-script-will-be-deprecated.md b/docs/announcements/en/old-versions-of-the-vtex-id-script-will-be-deprecated.md
index 4691703c6..47cb38511 100644
--- a/docs/announcements/en/old-versions-of-the-vtex-id-script-will-be-deprecated.md
+++ b/docs/announcements/en/old-versions-of-the-vtex-id-script-will-be-deprecated.md
@@ -27,9 +27,9 @@ To make this change possible, the VTEX ID script must be requested using this li
 
 This new method brings lots of advantages: even faster script updates, guarantees that your store is always using the latest version, and the end of the need to review the endpoint everytime a new version is released. 
 
-<div class="alert alert-warning">
-<strong>Warning:</strong><br>
-We don't recommend you to use the link in a hard-coded version. We'll soon deprecate the support for this import method.
-</div>
+>⚠️ **Warning:**
+>
+> 
+> We don't recommend you to use the link in a hard-coded version. We'll soon deprecate the support for this import method.
 
 Because all these changes have a direct impact in the client's access to your store, we strongly recommend you to not wait for the deadline and adopt this new VTEX ID script request method as soon as possible.
diff --git a/docs/announcements/en/on-vtex-png-to-webp-conversion-is-now-lossless.md b/docs/announcements/en/on-vtex-png-to-webp-conversion-is-now-lossless.md
index f1d204de2..a2dc407a1 100644
--- a/docs/announcements/en/on-vtex-png-to-webp-conversion-is-now-lossless.md
+++ b/docs/announcements/en/on-vtex-png-to-webp-conversion-is-now-lossless.md
@@ -19,8 +19,6 @@ VTEX stores already have automatic image compiling to __WebP__ format, as report
 
 The conversion of the image files only happens when your store is accessed by someone using a compatible browser (e.g. Gooogle Chrome). If they use a browser that doesn't read the format, the images won't be converted and will be displayed in their original formats. Notice that this automatic image compiling doesn't affect the file you uploaded in the CMS, only the way it's rendered on screen. 
 
-<div class="alert alert-warning">
-<strong>Lossless</strong> compression is only available for <strong>PNG</strong> files. <strong>JPG</strong> files continue to be compressed through the <strong>lossy</strong> process (wich reduces the image size in order to increase loading speed). 
-</div>
+>⚠️ **Lossless** compression is only available for **PNG** files. **JPG** files continue to be compressed through the **lossy** process (wich reduces the image size in order to increase loading speed).
 
 This change was developed to meet the needs of users who really have to display high quality images on their stores, even after the conversion to the WebP format. In all other situations, using _.jpg_ files still is the best solution to keep your website's performance.
diff --git a/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md b/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md
index 1ac95286d..95e52e67f 100644
--- a/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md
+++ b/docs/announcements/en/onboarding-guide-your-complete-journey-at-vtex.md
@@ -33,9 +33,7 @@ The **Onboarding guide** has three tracks:
 - [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS)
 - [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-<div class="alert alert-info">
-The tracks include content that complement one another, but they are intended to be standalone. This means you can explore the content freely, without following any specific order.
-</div>
+>ℹ️ The tracks include content that complement one another, but they are intended to be standalone. This means you can explore the content freely, without following any specific order.
 
 Our aim is to allow clients, partners, and the VTEX ecosystem to take advantage of the **Onboarding guide**. We took into account a comprehensive journey to make sure the content stayed relevant for different businesses.
 
diff --git a/docs/announcements/en/order-management-module-feed-v1-and-v2-discontinuation.md b/docs/announcements/en/order-management-module-feed-v1-and-v2-discontinuation.md
index e6e0b4e3c..778a56a57 100644
--- a/docs/announcements/en/order-management-module-feed-v1-and-v2-discontinuation.md
+++ b/docs/announcements/en/order-management-module-feed-v1-and-v2-discontinuation.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Order Management Module Feed v1 and v2 will be discontinued'
 ---
 
-<div class="alert alert-warning">
-From July 25<sup>th</sup>, 2019, the Order Management Module Feed v1 and v2 will be discontinued, meaning that after this date, only Feed v3 will be available for use.
-</div>
+>⚠️ From July 25<sup>th</sup>, 2019, the Order Management Module Feed v1 and v2 will be discontinued, meaning that after this date, only Feed v3 will be available for use.
 
 ## Why is VTEX removing the older versions?
 
diff --git a/docs/announcements/en/practical-guides-for-b2b-commerce.md b/docs/announcements/en/practical-guides-for-b2b-commerce.md
index ad6d85fd9..9b69f66ed 100644
--- a/docs/announcements/en/practical-guides-for-b2b-commerce.md
+++ b/docs/announcements/en/practical-guides-for-b2b-commerce.md
@@ -23,4 +23,4 @@ To help you provide tailor-made ecommerce experiences for your business and reth
 
 This documentation presents the main resources available on the platform for different B2B ecommerce scenarios.
 
-<div class="alert alert-info">This is just the beginning! In the coming months, we will gather all B2B documentation in a <a href="https://help.vtex.com/en/category/b2b--3BQkex089ohYNodLZKKrhi">specific section</a> in the VTEX Help Center.</div>
+>ℹ️ This is just the beginning! In the coming months, we will gather all B2B documentation in a [specific section](https://help.vtex.com/en/category/b2b--3BQkex089ohYNodLZKKrhi) in the VTEX Help Center.
diff --git a/docs/announcements/en/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md b/docs/announcements/en/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
index f4740019f..ebe88dab7 100644
--- a/docs/announcements/en/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
+++ b/docs/announcements/en/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
@@ -38,9 +38,7 @@ All VTEX stores already have the new app installed in a test environment, meanin
 
 By adding new visual elements, __the new My Account warrants a page revision together with the agency responsible for the your customization__. 
 
-<div class="alert alert-danger">
-<strong>VTEX will massively migrate the new My Account on the 3rd of July 2019.</strong> It is therefore imperative to begin reviewing page customizations now.
-</div>
+>❗ **VTEX will massively migrate the new My Account on the 3rd of July 2019.** It is therefore imperative to begin reviewing page customizations now.
 
 For more on new My Account __[settings](https://help.vtex.com/en/tutorial/setting-up-my-account--23Ayv5D6b86UBnYfoXqZL1)__ and __[functionality](https://help.vtex.com/en/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh)__, access the documentation available on our Help page.
 
diff --git a/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
index 752fca65a..064e06f67 100644
--- a/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
+++ b/docs/announcements/en/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -64,17 +64,13 @@ They should be able to follow the diagram below to assess whether an integration
 
 If your development team identified that your integration requires attention, they must follow the instructions provided in the developer guide [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations).
 
-<div class="alert alert-warning">
-If you are implementing reCAPTCHA on a native mobile app, use reCAPTCHA v3. Otherwise, reCAPTCHA use v2.
-</div>
+>⚠️ If you are implementing reCAPTCHA on a native mobile app, use reCAPTCHA v3. Otherwise, reCAPTCHA use v2.
 
 Using the reCAPTCHA key returned by the Checkout, the reCAPTCHA widget should be rendered in the user interface of your mobile app/headless storefront (or similar) as described in the [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) or [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3) documentation provided by Google.
 
 After the shopper has completed the reCAPTCHA challenge, their response (`recaptchaToken`) should be sent to the Checkout API to complete the purchase, as described in the *Final validation* section of [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#final-validation). Checkout API will then [verify the user's response](https://developers.google.com/recaptcha/docs/verify) using the provided token.
 
-<div class="alert alert-danger">
-All integrations using Checkout API to place orders must be reviewed and adjusted before September 1, 2023. Applications that fail to render the reCAPTCHA widget and verify the user's response will not be able to place orders after this date.
-</div>
+>❗ All integrations using Checkout API to place orders must be reviewed and adjusted before September 1, 2023. Applications that fail to render the reCAPTCHA widget and verify the user's response will not be able to place orders after this date.
 
 ## Learn more
 
diff --git a/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md b/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
index 57896d52f..0f4faad82 100644
--- a/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
+++ b/docs/announcements/en/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'All stores still using the Recurrence module should migrate to Subscriptions module until August 3, 2020'
 ---
 
-<div class="alert alert-info">
-The discontinuation will only affect stores that still have the Recurrences module. For stores that are already using the Subscriptions module or that don’t have this functionality, nothing will change.
-</div>
+>ℹ️ The discontinuation will only affect stores that still have the Recurrences module. For stores that are already using the Subscriptions module or that don’t have this functionality, nothing will change.
 
 The *Recurrences* module is an earlier version of our current *Subscriptions* module. This version will be discontinued, and all stores that still use it must migrate to the *Subscriptions* module by **August 3rd, 2020**.
 
diff --git a/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
index a1e87e3e1..2f3ff10dd 100644
--- a/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
@@ -25,11 +25,17 @@ Starting __march 31st__, the  request header `resources` for pagination will be
 
 This change has already been implemented in the API, but until the due date, both ways to make the request will be permitted. On the other hand, we won't make any changes in the response header `resources` (so it will keep working normally).
 
-<div class="alert alert-warning">
-<b>Important:</b><br> 
-- The parameters <b>_from</b> and <b>_to</b> must not have a difference bigger than <b>50</b>. This will limit the number of results shown to 50 at a time.<br>
-<br>
-- There's also a limit of 2500 items for any given search. Because of that, it's not possible to have a value over 2500 at the <b>_to</b> parameter.<br>
-</div>
+>⚠️ **Important:**
+>
+>  
+> - The parameters **_from** and **_to** must not have a difference bigger than **50**. This will limit the number of results shown to 50 at a time.
+>
+> 
+>
+>
+> 
+> - There's also a limit of 2500 items for any given search. Because of that, it's not possible to have a value over 2500 at the **_to** parameter.
+>
+> 
 
 To know more about how pagination requests work in the search API, take a look at this [document](https://developers.vtex.com/docs/api-reference/search-api).
diff --git a/docs/announcements/en/search-resolve-hides-number-product-stock.md b/docs/announcements/en/search-resolve-hides-number-product-stock.md
index b3dca95cc..b779a3f07 100644
--- a/docs/announcements/en/search-resolve-hides-number-product-stock.md
+++ b/docs/announcements/en/search-resolve-hides-number-product-stock.md
@@ -35,8 +35,6 @@ No action is needed. The change will be automatically implemented.
 
 If you use this data in your store (to indicate that a product is running out of stock, for example) you need to contact [our Support](https://support.vtex.com/hc/en-us/requests) to keep displaying this information.
 
-<div class="alert alert-warning">
-<p>Please note that if the store decides to display the number of products in stock, this information will be public and can be accessed using <a href="https://github.com/vtex-apps/search-graphql">VTEX Search GraphQL</a>.</p>
-</div>
+>⚠️ Please note that if the store decides to display the number of products in stock, this information will be public and can be accessed using [VTEX Search GraphQL](https://github.com/vtex-apps/search-graphql).
 </div>
 
diff --git a/docs/announcements/en/security-improvements-to-checkout-cookies.md b/docs/announcements/en/security-improvements-to-checkout-cookies.md
index 5425fd39e..c483ed200 100644
--- a/docs/announcements/en/security-improvements-to-checkout-cookies.md
+++ b/docs/announcements/en/security-improvements-to-checkout-cookies.md
@@ -57,6 +57,4 @@ If you find any errors while performing operational tests in the Beta environmen
 
 After verifying the store settings, run the test in Beta environment again.
 
-<div class="alert alert-warning">
-After February 13, 2023, stores that do not have the appropriate settings could be unable to operate the Checkout correctly.
-</div>
+>⚠️ After February 13, 2023, stores that do not have the appropriate settings could be unable to operate the Checkout correctly.
diff --git a/docs/announcements/en/service-worker-files-can-now-operate-at-full-capacity.md b/docs/announcements/en/service-worker-files-can-now-operate-at-full-capacity.md
index 9ad00b85a..fb1cea402 100644
--- a/docs/announcements/en/service-worker-files-can-now-operate-at-full-capacity.md
+++ b/docs/announcements/en/service-worker-files-can-now-operate-at-full-capacity.md
@@ -19,9 +19,9 @@ __Service Worker__ files now can intercept requests from all parts of your store
 
 The upgrade in the __Service Worker__ permissions broadens the possibilities for your store, like turning it into a PWA (Progressive Web App). This solution allows users to access a certain website like they would do in a smartphone app, but without the inconvenience of having to download it. The only requirement is saving the website in the home screen. And you don't even have to be connected to the internet to browse through it's content.
 
-<div class="alert alert-warning">
-<strong>Warning:</strong><br>
-VTEX's platform <strong>doesn't have</strong> a feature to turn your store into a PWA. It only offers the conditions to enable the implementation.
-</div>
+>⚠️ **Warning:**
+>
+> 
+> VTEX's platform **doesn't have** a feature to turn your store into a PWA. It only offers the conditions to enable the implementation.
 
 Read this [VTEX Help article](/en/tutorial/how-to-install-a-service-worker) to learn how to install a __Service Worker__ file in your store.
diff --git a/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md b/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md
index 089b225ba..0a65b21dd 100644
--- a/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md
+++ b/docs/announcements/en/site-editor-and-media-new-authorization-requirement.md
@@ -29,7 +29,5 @@ This change aims to enhance security and simplify user access to the Site Editor
 ## What needs to be done?
 Ensure that users are associated with the `CMS GraphQL API` resource within their user roles by either [creating a new role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) or editing an existing one.
 
-<div class="alert alert-warning">
-  <p>To manage users and their roles, you need the <code>Save access profile</code> resource from the <bold>License Manager</bold> product associated with your user role. For example, the <a href=”https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted”> User Administrator - RESTRICTED</a> is a predefined role that has the <code>Save access profile</code> resource associated with it.</p>
-</div>
+>⚠️ To manage users and their roles, you need the `Save access profile` resource from the <bold>License Manager</bold> product associated with your user role. For example, the <a href=”https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted”> User Administrator - RESTRICTED</a> is a predefined role that has the `Save access profile` resource associated with it.
 
diff --git a/docs/announcements/en/smartcheckout-tm-new-version-already-available-for-all-stores.md b/docs/announcements/en/smartcheckout-tm-new-version-already-available-for-all-stores.md
index 45aca5862..ece400bfb 100644
--- a/docs/announcements/en/smartcheckout-tm-new-version-already-available-for-all-stores.md
+++ b/docs/announcements/en/smartcheckout-tm-new-version-already-available-for-all-stores.md
@@ -28,8 +28,6 @@ Other important changes:
 - New data layer information to be used along with Google Enhanced Ecommerce.
 - Customizations are now avaiable for the `checkout5-custom.js` and `orderplaced2-custom.js` files, wich edits the checkout and the finished order screen, repectively.
 
-<div class="alert alert-warning">
-Remember: VTEX <strong>doesn't recommend</strong> the customization of JavaScript files, because this can damage your checkout. We don't take responsibility for any problems originated from the editing of this code.
-</div>
+>⚠️ Remember: VTEX **doesn't recommend** the customization of JavaScript files, because this can damage your checkout. We don't take responsibility for any problems originated from the editing of this code.
 
 To know everything about the SmartCheckout™'s new version, take a look at [this VTEX Help article](/en/tutorial/migrating-to-the-new-version-of-smart-checkout).
diff --git a/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md b/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md
index e706e466b..e71978681 100644
--- a/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md
+++ b/docs/announcements/en/the-items-field-will-be-removed-from-the-list-orders-api.md
@@ -23,9 +23,7 @@ List Orders API request: <code>http://{{accountName}}.{{environment}}.com.br/api
 
 If your store uses the List Orders API and your integration mapping is expected to receive the `items` field, your development team needs to __remove it from the integration mapping__.
 
-<div class="alert alert-warning">
-The <code>items</code> field of the List Orders API has already been <strong>stale</strong> for quite some time. It does not have any use today, and so your store should not consider it in your integrations. To get order items, you should be using the <a href="http://help.vtex.com/en/tutorial/how-the-oms-feed-works">Feed API</a> .
-</div>
+>⚠️ The `items` field of the List Orders API has already been **stale** for quite some time. It does not have any use today, and so your store should not consider it in your integrations. To get order items, you should be using the [Feed API](http://help.vtex.com/en/tutorial/how-the-oms-feed-works) .
 
 It is important to remember that __the List Orders API remains working normally__. Only the `items` field will be deleted.
 
@@ -35,13 +33,9 @@ Removing this field will greatly increase the stability and performance of the o
 
 That is why it's crucial to remove it from integration.
 
-<div class="alert alert-info">
-<strong>Attention:</strong> This change only impacts integrations that depend on the delivery of the `items` field through the List Orders API.
-</div>
+>ℹ️ **Attention:** This change only impacts integrations that depend on the delivery of the `items` field through the List Orders API.
 
-<div class="alert alert-info">
-This change does <strong>not</strong> affect the Get Orders API. In it, the <code>items</code> field continues to exist and keeps being normally updated.
-</div>
+>ℹ️ This change does **not** affect the Get Orders API. In it, the `items` field continues to exist and keeps being normally updated.
 
 <div class="alert">
 Get Order API request: <code>http://{{accountName}}.{{environment}}.com.br/api/oms/pvt/orders/{{orderId}}</code>
diff --git a/docs/announcements/en/the-new-admin-is-already-being-deployed-to-all-stores.md b/docs/announcements/en/the-new-admin-is-already-being-deployed-to-all-stores.md
index 469b0f50c..38b54d37c 100644
--- a/docs/announcements/en/the-new-admin-is-already-being-deployed-to-all-stores.md
+++ b/docs/announcements/en/the-new-admin-is-already-being-deployed-to-all-stores.md
@@ -25,6 +25,4 @@ And don't worry: this transition will not interfere on your daily routine, becau
 
 If you can't wait to try the __new Admin__, type `https://{AccountName}.myvtex.com/admin` in your browser, replacing _{AccountName}_ with your store's account name.
 
-<div class="alert alert-warning">
-The legacy modules (Catalog, Master Data, and CMS) will keep redirecting to their external environments.
-</div>
+>⚠️ The legacy modules (Catalog, Master Data, and CMS) will keep redirecting to their external environments.
diff --git a/docs/announcements/en/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md b/docs/announcements/en/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
index bdafc962f..946f38cf8 100644
--- a/docs/announcements/en/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
+++ b/docs/announcements/en/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
@@ -31,6 +31,4 @@ The module's behavior remains the same since the last update: If the applied fil
 ## How to export more than 5.000 orders
 You can export more than 5.000 orders using the Orders Management (formerly known as OMS) APIs: [Get Order](https://developers.vtex.com/reference/orders#getorder) and [Get Feed Order Status](https://developers.vtex.com/reference/note).
 
-<div class="alert alert-warning">
-<strong>But remember:</strong> For it to work, it's necessary to <strong>create a date/hour range that includes up to 5.000 orders</strong>. After defining a range that respects this limit, you'll be able to make as many requests to the API as you want.
-</div>
+>⚠️ **But remember:** For it to work, it's necessary to **create a date/hour range that includes up to 5.000 orders**. After defining a range that respects this limit, you'll be able to make as many requests to the API as you want.
diff --git a/docs/announcements/en/the-offer-management-module-will-be-discontinued.md b/docs/announcements/en/the-offer-management-module-will-be-discontinued.md
index 635b3bfc2..f5ebaad5d 100644
--- a/docs/announcements/en/the-offer-management-module-will-be-discontinued.md
+++ b/docs/announcements/en/the-offer-management-module-will-be-discontinued.md
@@ -28,8 +28,6 @@ The [Moderation](https://help.vtex.com/pt/tutorial/gerenciamento-de-anuncios-mod
 
 This update is automatic, so no action is required from you. As of the date indicated above, the module will be completely discontinued from the VTEX Admin.  
 
-<div class="alert alert-info">
-We will soon have a replacement module for Offer Management. Follow the updates through the <a href="https://developers.vtex.com/updates/release-notes">Release Notes page on the Developer Portal</a> and the <a href="https://help.vtex.com/en/announcements">News page in the VTEX Help Center</a>.
-</div>
+>ℹ️ We will soon have a replacement module for Offer Management. Follow the updates through the [Release Notes page on the Developer Portal](https://developers.vtex.com/updates/release-notes) and the [News page in the VTEX Help Center](https://help.vtex.com/en/announcements).
 
 
diff --git a/docs/announcements/en/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md b/docs/announcements/en/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
index 78e0694f3..2c7bf68a1 100644
--- a/docs/announcements/en/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
+++ b/docs/announcements/en/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
@@ -58,9 +58,7 @@ If you want any user in your store to be able to perform the actions associated
 ### Application Keys
 Application keys with the **Owner (Admin Super)** role will not automatically be granted the **User Administrator - RESTRICTED** role.  Therefore, if you want any application key to be able to perform the actions associated with the above **Save user** feature, make sure that this key has the **User Administrator - RESTRICTED** role or create a [custom role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#tipos-de-perfis) that includes the **Save user** resource.
 
-<div class="alert alert-warning">
-Note that with the changes described above, application keys no longer have the <b>Save user</b> resource, so a user with access to this feature must grant it, if needed.
-</div>
+>⚠️ Note that with the changes described above, application keys no longer have the **Save user** resource, so a user with access to this feature must grant it, if needed.
 
 ## How to protect your store app keys?
 
diff --git a/docs/announcements/en/this-new-api-helps-marketplaces-avoid-losing-sales.md b/docs/announcements/en/this-new-api-helps-marketplaces-avoid-losing-sales.md
index 49662d0d6..7803f4efd 100644
--- a/docs/announcements/en/this-new-api-helps-marketplaces-avoid-losing-sales.md
+++ b/docs/announcements/en/this-new-api-helps-marketplaces-avoid-losing-sales.md
@@ -19,10 +19,10 @@ A new API, which gives more autonomy to marketplaces using VTEX, is already in s
 
 With this new status, marketplaces can recover sales that would be otherwise lost should a seller canceled an order. Now, they will still have time to find another seller with the requirements to accept the order and ensure conversion.
 
-<div class="alert alert-warning">
-<strong>Warning:</strong><br> 
-The "Window to change Seller" status is only available when both <strong>Marketplace</strong> and <strong>Seller</strong> are VTEX users. If there's no VTEX seller with the necessary inventory, the order will not proceed to the new status and will be canceled automatically. 
-</div>
+>⚠️ **Warning:**
+>
+>  
+> The "Window to change Seller" status is only available when both **Marketplace** and **Seller** are VTEX users. If there's no VTEX seller with the necessary inventory, the order will not proceed to the new status and will be canceled automatically.
 
 This new feature allows marketplaces to have a more efficient quality control on the overall buying experience because they can also choose a different seller when the order status is "__Pending payment__" or "__Awaiting authorization__". Another possibility is for those stores that have white label sellers: now they're able to change the seller responsible for an order.
 
diff --git a/docs/announcements/en/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md b/docs/announcements/en/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
index 683eb17cd..f841ff316 100644
--- a/docs/announcements/en/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
+++ b/docs/announcements/en/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
@@ -19,9 +19,7 @@ On 13/06/19, [Feed V1 and V2 API discontinuation was announced](/announcements/o
 
 __The migration due date has been changed and stores that have not yet adapted to the new version have until August 12th to implement the integration__. After this date, it will no longer be possible to consume orders data using previous versions of this API, thus impacting your order delivery process.
 
-<div class="alert alert-info">
-No action is required from stores already using Feed API V3.
-</div>
+>ℹ️ No action is required from stores already using Feed API V3.
 
 The discontinuation of this API's V1 and V2 will interrupt orders integration from services that use these versions. It is therefore necessary for your integration to be running V3 of this API for your orders delivery operation to continue functioning properly.
 
diff --git a/docs/announcements/en/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md b/docs/announcements/en/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
index 8fd12ce4b..3f062aa35 100644
--- a/docs/announcements/en/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
+++ b/docs/announcements/en/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
@@ -15,21 +15,19 @@ announcementImageID: ''
 announcementSynopsisEN: 'The V2 brings a lot of improvements in comparison with the previous version and removes some outdated routes and fields.'
 ---
 
-<div class="alert alert-danger">
-The migration to V2 of Checkout and Fulfillment API was already completed on <strong>05/23/2018</strong>
-</div>
+>❗ The migration to V2 of Checkout and Fulfillment API was already completed on **05/23/2018**
 
-<div class="alert alert-warning">
-The deadline changed from <strong>05/21</strong> to <strong>05/23</strong> (a two-day postponement) due to the need for additional tests.
-</div>
+>⚠️ The deadline changed from **05/21** to **05/23** (a two-day postponement) due to the need for additional tests.
 
 The second version of the Checkout and Fulfillment API is already available in beta. Starting __May 23__, all stores will be running it. This V2 brings a lot of improvements in comparison with the previous version and removes some outdated routes and fields.
 
-<div class="alert alert-warning">
-<strong>Atention</strong><br>
-We strongly recommend you to run tests to evaluate all impacts and adapt you web site's integrations and customizations before the deadline.<br> 
-So, when we complete the update to the API's new version, the process will run smoothly for your store.
-</div>
+>⚠️ **Atention**
+>
+> 
+> We strongly recommend you to run tests to evaluate all impacts and adapt you web site's integrations and customizations before the deadline.
+>
+>  
+> So, when we complete the update to the API's new version, the process will run smoothly for your store.
 
 Take a look at everything wich changes with the Checkout and Fulfillment new API (and what's in beta or in stable):
 
diff --git a/docs/announcements/en/vtex-announces-its-integration-with-amazon.md b/docs/announcements/en/vtex-announces-its-integration-with-amazon.md
index 2d3d09d59..3435b78d5 100644
--- a/docs/announcements/en/vtex-announces-its-integration-with-amazon.md
+++ b/docs/announcements/en/vtex-announces-its-integration-with-amazon.md
@@ -19,7 +19,5 @@ VTEX announces its new integration with Amazon. Now our customers can now connec
 
 At first, integration will be available for the Electronic, Books and Games categories. For more details about the integration, see our [tutorial](https://help.vtex.com/en/tracks/amazon-integration-setup--6sgd4Pagy3wNsWKBvmIFrP "tutorial").
 
-<div class="alert alert-warning">
-This integration is available for Brazil and the United States.
-</div>
+>⚠️ This integration is available for Brazil and the United States.
 
diff --git a/docs/announcements/en/vtex-login-now-features-recaptcha.md b/docs/announcements/en/vtex-login-now-features-recaptcha.md
index 73a9634cc..d27b0893e 100644
--- a/docs/announcements/en/vtex-login-now-features-recaptcha.md
+++ b/docs/announcements/en/vtex-login-now-features-recaptcha.md
@@ -25,7 +25,6 @@ This means that the confirmation request may or may not appear, depending on sev
 
 With this change, VTEX no longer prevents user access after 3 incorrect attempts, since security is guaranteed by reCAPTCHA.
 
-<div class="alert alert-info">Currently, we only use reCAPTCHA in the admin login flow.</div>
+>ℹ️ Currently, we only use reCAPTCHA in the admin login flow.
 
-<div class="alert alert-warning">
-Due to this change, <a href="https://help.vtex.com/en/announcements/integrations-with-vtex-apis-now-need-token-authentication--7AdnXDH7AkYmuEUmmis8Es">it is no longer possible to use email and password for integrations</a>.</div>
+>⚠️ Due to this change, [it is no longer possible to use email and password for integrations](https://help.vtex.com/en/announcements/integrations-with-vtex-apis-now-need-token-authentication--7AdnXDH7AkYmuEUmmis8Es).
diff --git a/docs/announcements/en/vtex-login-now-needs-2-factor-authentication.md b/docs/announcements/en/vtex-login-now-needs-2-factor-authentication.md
index 53d150b58..993e9c125 100644
--- a/docs/announcements/en/vtex-login-now-needs-2-factor-authentication.md
+++ b/docs/announcements/en/vtex-login-now-needs-2-factor-authentication.md
@@ -17,9 +17,7 @@ announcementSynopsisEN: 'As of November 16, 2-factor authentication (2FA) become
 
 As of __November 16__, at 2:00 p.m. (Brazil time), 2-factor authentication (2FA) becomes mandatory for all emails in VTEX Admin.
 
-<div class="alert alert-info">
-Check the article on <a href="http://help.vtex.com/en/tutorial/enabling-2-factor-authentication-login">how to enable 2FA</a>.
-</div>
+>ℹ️ Check the article on [how to enable 2FA](http://help.vtex.com/en/tutorial/enabling-2-factor-authentication-login).
 
 2FA is an authentication method that greatly increases the security of your store. That's because, at the moment of login, in addition to requesting email and password, the system requires an access key generated by application or SMS.
 
diff --git a/docs/announcements/en/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md b/docs/announcements/en/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
index 0f48b9ec1..93ae138a4 100644
--- a/docs/announcements/en/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
+++ b/docs/announcements/en/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
@@ -21,9 +21,7 @@ Now you don't have to depend on external integrations to sell on Magazine Luiza.
 ## How was the process
 Our integration with Magazine Luiza became available in October 2018, but only for stores that weren't connected to the marketplace yet. In early December,  we started the migration process of stores that were operating with external integrations.  It all went down smoothly, with no action required on client side.
 
-<div class="alert alert-info">
-Magazine Luiza's integration occurs through  Integra Commerce's system, which intermediates the information sent by VTEX and repasses them to the marketplace.
-</div>
+>ℹ️ Magazine Luiza's integration occurs through  Integra Commerce's system, which intermediates the information sent by VTEX and repasses them to the marketplace.
 
 
 ## Complete, stable, and with our team's full support
diff --git a/docs/announcements/en/web-service-methods-will-be-deprecated.md b/docs/announcements/en/web-service-methods-will-be-deprecated.md
index ef425610f..579418f04 100644
--- a/docs/announcements/en/web-service-methods-will-be-deprecated.md
+++ b/docs/announcements/en/web-service-methods-will-be-deprecated.md
@@ -17,9 +17,7 @@ announcementSynopsisEN: 'As of February 28, the use of Web Service will be disco
 
 As of __February 28__, we will discontinue the use of Web Service for integrations with VTEX, __except for the Catalog methods__.
 
-<div class="alert alert-warning">
-Web Service will continue to work for the Catalog, while we work on the development of this service's REST APIs. We will let you know as soon as a migration schedule is defined.
-</div>
+>⚠️ Web Service will continue to work for the Catalog, while we work on the development of this service's REST APIs. We will let you know as soon as a migration schedule is defined.
 
 If your store still uses any of these methods, replace them with API integrations. Otherwise, as of February 28, these integrations will no longer work.
 
diff --git a/docs/announcements/en/wordpress-a-powerful-marketing-tool-for-your-store.md b/docs/announcements/en/wordpress-a-powerful-marketing-tool-for-your-store.md
index 3c249dfcd..00caf4bd0 100644
--- a/docs/announcements/en/wordpress-a-powerful-marketing-tool-for-your-store.md
+++ b/docs/announcements/en/wordpress-a-powerful-marketing-tool-for-your-store.md
@@ -31,6 +31,4 @@ Integrating your blog/website into the store is equal to using a powerful conten
 
 Install the app from the [VTEX App Store](https://apps.vtex.com/vtex-wordpress-integration/p) and follow the instructions in [this documentation](https://developers.vtex.com/vtex-developer-docs/docs/vtex-wordpress-integration) to configure the integration.
 
-<div class="alert alert-info">
-To use this application you need to have a website/blog developed on WordPress.
-</div>
+>ℹ️ To use this application you need to have a website/blog developed on WordPress.
diff --git a/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 354383732..136990543 100644
--- a/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/en/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Possibility to limit user access to the Settings screen'
 ---
 
-<div class="alert alert-warning">
-From June 25 <sup>th</sup>, 2019, users without access to <code>Checkout</code> will not be allowed to edit the Settings tab on the Orders Management module. 
-</div>
+>⚠️ From June 25 <sup>th</sup>, 2019, users without access to `Checkout` will not be allowed to edit the Settings tab on the Orders Management module.
 
 Seeking to ensure greater safety, we created the possibility to limit user access to the **Settings** screen on the Orders Management module, allowing information to be edited by selected users only. 
 
diff --git a/docs/announcements/es/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md b/docs/announcements/es/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md
index 68d0cafbe..6444e7440 100644
--- a/docs/announcements/es/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md	
+++ b/docs/announcements/es/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md	
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Ahora disponible informaciónes detalladas sobre el cálculo del envio de lo pedido'
 ---
 
-<div class="alert alert-warning">
-Por motivos técnicos, el lanzamiento de esta funcionalidad fue aplazado por tiempo indeterminado.
-</div>
+>⚠️ Por motivos técnicos, el lanzamiento de esta funcionalidad fue aplazado por tiempo indeterminado.
 
 A partir del 1 de abril de 2019, el JSON de pedidos devolverá un nuevo objeto llamado `alternativeTotals`. Se mostrará en los totalizadores que quedan dentro del array de `totals`, para las consultas realizadas por la API de Get Order.
 
diff --git a/docs/announcements/es/adapting-your-stores-front-end-requisites-to-master-data.md b/docs/announcements/es/adapting-your-stores-front-end-requisites-to-master-data.md
index e51c96655..209c358a0 100644
--- a/docs/announcements/es/adapting-your-stores-front-end-requisites-to-master-data.md
+++ b/docs/announcements/es/adapting-your-stores-front-end-requisites-to-master-data.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'VTEX descontinuará el soporte para CORS del Master Dat
 
 Con el objetivo principal de proporcionar una experiencia cada vez más eficiente para usted y sus clientes, VTEX descontinuará el soporte para CORS del Master Data. Siga las instrucciones de este artículo y evite cualquier falla en la operación y la navegación de su tienda.
 
-<div class="alert alert-warning"> En alineamiento con la colaboración que tenemos con nuestros clientes, asegurando una fricción mínima en sus operaciones, ampliamos la fecha de descontinuación de este recurso hasta el día 7 de octubre de 2019. </div>
+>⚠️ En alineamiento con la colaboración que tenemos con nuestros clientes, asegurando una fricción mínima en sus operaciones, ampliamos la fecha de descontinuación de este recurso hasta el día 7 de octubre de 2019.
   
 ### ¿Qué es CORS?
 
diff --git a/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
index f38564df5..21f879977 100644
--- a/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/es/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -17,9 +17,7 @@ announcementSynopsisES: 'Usuarios solo verán los ítems del menú de la barra l
 
 Los [perfiles de acceso](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) permiten a las tiendas conceder y limitar el acceso de los usuarios a un subconjunto determinado de recursos en la plataforma. Aunque esto era suficiente para proteger la integridad y seguridad de su cuenta, los usuarios sí podían ver los ítems del menú de las secciones restringidas del Admin. Ahora las secciones no son visibles de manera que los usuarios solo ven los ítems a los que tienen acceso. 
 
-<div class="alert alert-info">
-Esta acción tiene bajo impacto en las operaciones de la tienda, dado que es una reorganización de la barra de navegación de la izquierda y no supone cambios a los perfiles de usuarios individuales.  Además, no se perderá ninguna configuración predefinida: si sus usuarios ya tenían perfiles y permisos predefinidos, no sufrirán ningún cambio.
-</div>
+>ℹ️ Esta acción tiene bajo impacto en las operaciones de la tienda, dado que es una reorganización de la barra de navegación de la izquierda y no supone cambios a los perfiles de usuarios individuales.  Además, no se perderá ninguna configuración predefinida: si sus usuarios ya tenían perfiles y permisos predefinidos, no sufrirán ningún cambio.
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/all-stores-have-until-april-20th-to-activate-the-new-cdn.md b/docs/announcements/es/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
index 9fd09aaa5..e98580037 100644
--- a/docs/announcements/es/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
+++ b/docs/announcements/es/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
@@ -22,10 +22,12 @@ Esta solución está disponible para todas las tiendas desde octubre de 2017 y,
 __Importante:__ el principal requisito para cambiar a el nuevo CDN es que su sitio sea __totalmente disponible en HTTPS__. Usted debe estar atento principalmente a las llamadas HTTP de su sitio, que deben pasar a ser HTTPS para funcionar en el nuevo CDN. Vea como [activar HTTPS en todo el sitio](/es/tutorial/activar-https-en-todo-el-sitio) y esté atento  los requisitos necesarios para esta migración.
 
 Por lo tanto, mucha atención:
-<div class="alert alert-warning">
-Usted tiene hasta el día <b>20 de abril</b> para asegurarse de que su tienda:<br>
-- Esté totalmente disponible en HTTPS.<br>
-- Ha completado la migración a el nuevo CDN de VTEX.
-</div>
+>⚠️ Usted tiene hasta el día **20 de abril** para asegurarse de que su tienda:
+>
+> 
+> - Esté totalmente disponible en HTTPS.
+>
+> 
+> - Ha completado la migración a el nuevo CDN de VTEX.
 
 Después de esa fecha, las tiendas que no hicieron los cambios necesarios __pueden sufrir indisponibilidad__, como layout roto hasta sua tienda *offline*. Por lo tanto, le recomendamos que active el HTTPS y migre a el nuevo CDN hasta esa fecha. Esto garantizará a sus clientes la mejor experiencia.
diff --git a/docs/announcements/es/apply-manual-prices-in-subscription-items.md b/docs/announcements/es/apply-manual-prices-in-subscription-items.md
index 736bfe044..0e5ec88d8 100644
--- a/docs/announcements/es/apply-manual-prices-in-subscription-items.md
+++ b/docs/announcements/es/apply-manual-prices-in-subscription-items.md
@@ -34,7 +34,5 @@ Este cambio está motivado por la demanda de los comerciantes de configurar manu
 
 Para activar la funcionalidad Precio Manual para Suscripciones, asegúrate de seguir los pasos descritos en la guía [Enabling manual prices for Subscriptions v3](https://developers.vtex.com/vtex-rest-api/docs/enabling-manual-prices-for-subscriptions-v3).
 
-<div class="alert alert-warning">
-<p>La funcionalidad Precio Manual solo está disponible para Suscripciones v3. Si estás utilizando una versión anterior del sistema de Suscripciones, consulta la guía <a href="https://developers.vtex.com/vtex-rest-api/docs/subscriptions-v3-migration-guide">Subscriptions v3 migration guide</a>.</p>
-</div>
+>⚠️ La funcionalidad Precio Manual solo está disponible para Suscripciones v3. Si estás utilizando una versión anterior del sistema de Suscripciones, consulta la guía [Subscriptions v3 migration guide](https://developers.vtex.com/vtex-rest-api/docs/subscriptions-v3-migration-guide).
 
diff --git a/docs/announcements/es/become-an-expert-in-vtex-with-training-day.md b/docs/announcements/es/become-an-expert-in-vtex-with-training-day.md
index 26141e44a..6c5031fe3 100644
--- a/docs/announcements/es/become-an-expert-in-vtex-with-training-day.md
+++ b/docs/announcements/es/become-an-expert-in-vtex-with-training-day.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Participe en un día de entrenamiento intensivo en VTEX con los mayores especialistas en el tema.'
 ---
 
-<div class="alert alert-info">
-Un día completo de entrenamiento en VTEX con los mayores especialistas en el tema.
-</div>
+>ℹ️ Un día completo de entrenamiento en VTEX con los mayores especialistas en el tema.
 
 Hace mucho tiempo, nuestros clientes y socios piden un entrenamiento de la plataforma en profundidad. Ahora, finalmente, hemos logrado atender a esa solicitación.
 
diff --git a/docs/announcements/es/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md b/docs/announcements/es/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
index 706b8e800..cd36be214 100644
--- a/docs/announcements/es/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
+++ b/docs/announcements/es/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
@@ -25,6 +25,4 @@ Anteriormente, las promociones con condiciones de medio de pago sólo se aplicab
 
 En el escenario actual, las promociones pasan a considerar la condición de medio de pago por política comercial. Esto significa que una promoción con filtro de medio de pago puede aplicarse a más de una política comercial. Con esta mejora, el minorista tiene mayor flexibilidad para configurar sus promociones.
 
-<div class="alert alert-danger">
-Es importante resaltar que esta feature <strong>no es válida</strong> para las políticas comerciales de terceros.
-</div>
+>❗ Es importante resaltar que esta feature **no es válida** para las políticas comerciales de terceros.
diff --git a/docs/announcements/es/boost-your-marketplace-sales.md b/docs/announcements/es/boost-your-marketplace-sales.md
index ee70d8b2a..58598b647 100644
--- a/docs/announcements/es/boost-your-marketplace-sales.md
+++ b/docs/announcements/es/boost-your-marketplace-sales.md
@@ -34,7 +34,5 @@ Si su tienda tiene __integración externa con marketplaces__ (y desea utilizar l
 
 Si su tienda tiene __integración con marketplaces certificados__ (usando el bridge), la flag se activará automáticamente. Sólo necesitará cumplir los pasos descritos en los ítems `2` y `3`.
 
-<div class="alert alert-info">
-Recuerde que las integraciones de pedido se deben realizar utilizando las siguientes API <a href="https://developers.vtex.com/reference/orders#getorder">Get Order</a> y <a href="https://developers.vtex.com/reference/feed-v2-deprecated#getfeedorderstatus">Get Feed Order Status</a>.
-</div>
+>ℹ️ Recuerde que las integraciones de pedido se deben realizar utilizando las siguientes API [Get Order](https://developers.vtex.com/reference/orders#getorder) y [Get Feed Order Status](https://developers.vtex.com/reference/feed-v2-deprecated#getfeedorderstatus).
 
diff --git a/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 33bacada6..a65326f15 100644
--- a/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/es/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -41,9 +41,7 @@ La solución combina:
 -	**Last Mile**: los operadores de la tienda pueden gestionar y dar instrucciones a los repartidores sobre la recolección y entrega de pedidos. Esto incluye optimización de rutas y prueba de recolección/entrega. Además, tu tienda puede integrarse fácilmente con transportadoras externas o un sistema TMS.  
 - **Aplicaciones móviles:** aplicaciones para dispositivos móviles diseñadas exclusivamente para que los alistadores y repartidores puedan realizar sus tareas sin necesidad de acceder al Admin de la tienda. Actualmente, las aplicaciones solo están disponibles para dispositivos Android.  
 
-<div class="alert alert-danger">
-<b>VTEX Pick and Pack</b> no es un sistema de facturación. Los pedidos deben facturarse a través del OMS de VTEX. Puedes ver más información en <a href="https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT">Facturar un pedido</a>.
-</div>
+>❗ **VTEX Pick and Pack** no es un sistema de facturación. Los pedidos deben facturarse a través del OMS de VTEX. Puedes ver más información en [Facturar un pedido](https://help.vtex.com/es/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT).
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md b/docs/announcements/es/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
index 259d6fefe..8addcef7c 100644
--- a/docs/announcements/es/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
+++ b/docs/announcements/es/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
@@ -61,6 +61,4 @@ Las mejoras atienden principalmente a escenarios en los que uno mismo pedido tie
 Este cambio __no requiere__ ningún tipo de acción. Si su tienda ya usa la __versión 4 del orderPlaced__, que es compatible con todas las funcionalidades de [Omnichannel](/es/announcement/cambie-su-negocio-con-la-experiencia-omnichannel-vtex), el nuevo comportamiento ya se está aplicando.
 
 
-<div class="alert alert-warning">
-Este cambio se llevó a cabo <strong>sólo en la versión 4 del orderPlaced</strong> y no afecta el comportamiento de las versiones anteriores.
-</div>
+>⚠️ Este cambio se llevó a cabo **sólo en la versión 4 del orderPlaced** y no afecta el comportamiento de las versiones anteriores.
diff --git a/docs/announcements/es/changes-in-vtex-support-service-policy.md b/docs/announcements/es/changes-in-vtex-support-service-policy.md
index 3b851bba7..7344e859e 100644
--- a/docs/announcements/es/changes-in-vtex-support-service-policy.md
+++ b/docs/announcements/es/changes-in-vtex-support-service-policy.md
@@ -15,4 +15,4 @@ announcementImageID: ''
 announcementSynopsisES: 'Ahora, el canal principal para abrir un ticket es la Comunidad VTEX.'
 ---
 
-<div class="alert alert-info">Este contenido está siendo traducido.</div>
+>ℹ️ Este contenido está siendo traducido.
diff --git a/docs/announcements/es/check-your-stores-caa-record.md b/docs/announcements/es/check-your-stores-caa-record.md
index 52bf5c43d..b391e0bf0 100644
--- a/docs/announcements/es/check-your-stores-caa-record.md
+++ b/docs/announcements/es/check-your-stores-caa-record.md
@@ -17,9 +17,7 @@ announcementSynopsisES: 'Recomendamos que actualice las entradas CAA de sus admi
 
 Con el acercamiento a __Black Friday__, le recomendamos que actualice las entradas CAA en sus Gestores de DNS hasta el __9 de noviembre__. Esta acción es necesaria para que se genere y se renueve el certificado SSL. Sólo así es posible utilizar el CDN de VTEX.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> estos tipos de entrada pueden no estar disponibles en la interfaz de su administrador de DNS, pero a menudo se pueden gestionar a través de llamados en el soporte de la herramienta.
-</div>
+>⚠️ **Atención:** estos tipos de entrada pueden no estar disponibles en la interfaz de su administrador de DNS, pero a menudo se pueden gestionar a través de llamados en el soporte de la herramienta.
 
 ## ¿Qué necesitas hacer?
 En las configuraciones del __Gestor de DNS__, consulte (o pida al responsable de la gestión del dominio de su tienda) si las entradas siguientes están configuradas de la siguiente manera:
@@ -33,9 +31,7 @@ En las configuraciones del __Gestor de DNS__, consulte (o pida al responsable de
 ## ¿Cuál es el impacto?
 Registrar las nuevas entradas sólo permite que las entidades __Digicert__, __Comodo__, __Globalsign__ y __Let's encrypt__ puedan generar y renovar certificados para su dominio. __Estos certificados son fundamentales para que su tienda pueda utilizar el CDN de VTEX y tener un rendimiento superior.__ Si la actualización no se realiza, su tienda puede tener problemas de rendimiento y tardar más en cargarse.
 
-<div class="alert alert-info">
-Las tiendas que no tienen ninguna entrada CAA configurada <strong>no tienen que hacer la configuración</strong> y <strong>no se verán afectada</strong>.
-</div>
+>ℹ️ Las tiendas que no tienen ninguna entrada CAA configurada **no tienen que hacer la configuración** y **no se verán afectada**.
 
 
 ## Contenidos útiles
diff --git a/docs/announcements/es/checkout-api-improvements-part-1.md b/docs/announcements/es/checkout-api-improvements-part-1.md
index d4d71bab5..81dfa8c53 100644
--- a/docs/announcements/es/checkout-api-improvements-part-1.md
+++ b/docs/announcements/es/checkout-api-improvements-part-1.md
@@ -19,9 +19,7 @@ Nuestro equipo de desarrollo está constantemente mejorando la performance de nu
 
 Con la comunicación de estas mejoras, queremos permitir que usted ya empiece el proceso de actualización de las integraciones y personalizaciones de su tienda, pensando en las nuevas soluciones ofrecidas por nuestro sistema.
 
-<div class="alert alert-warning">
-El layout actual de la API del Checkout sigue funcionando con normalidad. Sin embargo, es muy importante que la implementación de las mejoras descritas a continuación sea hecha desde ahora. Todavía no hay previsión para el lanzamiento de la nueva mayor de la API del Checkout. Sin embargo, en esta próxima versión, los puntos descontinuados que se describen a continuación ya no funcionarán.
-</div>
+>⚠️ El layout actual de la API del Checkout sigue funcionando con normalidad. Sin embargo, es muy importante que la implementación de las mejoras descritas a continuación sea hecha desde ahora. Todavía no hay previsión para el lanzamiento de la nueva mayor de la API del Checkout. Sin embargo, en esta próxima versión, los puntos descontinuados que se describen a continuación ya no funcionarán.
 
 ## Dirección en el carrito y en el pedido
 
diff --git a/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md b/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md
index 1e7c08848..a444b4d0b 100644
--- a/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md
+++ b/docs/announcements/es/checkout-api-now-supports-recaptcha-v3.md
@@ -23,9 +23,7 @@ Además de la funcionalidad disponible para los storefronts nativos de la plataf
 
 La API de Checkout ahora también admite validación reCAPTCHA basada en puntuación (equivalente a v3), adecuado para aplicaciones móviles nativas.
 
-<div class="alert alert-info">
-VTEX está integrado con reCAPTCHA enterprise, que ofrece dos enfoques de validación: checkbox (equivalente a reCAPTCHA v2) y basada en puntuación (equivalente a reCAPTCHA v3). Consulta este artículo sobre <a href="https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#versiones-de-recaptcha">reCAPTCHA en el Checkout de VTEX</a> para aprender qué versión debes usar según las características de tu tienda. También puedes obtener más información sobre cada método: <a href="https://developers.google.com/recaptcha/docs/display">reCAPTCHA v2</a> o <a href="https://developers.google.com/recaptcha/docs/v3">reCAPTCHA v3</a> con la documentación proporcionada por Google.
-</div>
+>ℹ️ VTEX está integrado con reCAPTCHA enterprise, que ofrece dos enfoques de validación: checkbox (equivalente a reCAPTCHA v2) y basada en puntuación (equivalente a reCAPTCHA v3). Consulta este artículo sobre [reCAPTCHA en el Checkout de VTEX](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#versiones-de-recaptcha) para aprender qué versión debes usar según las características de tu tienda. También puedes obtener más información sobre cada método: [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) o [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3) con la documentación proporcionada por Google.
 
 Sin embargo, la opción de integración con validación de reCAPTCHA checkbox (equivalente a v2) sigue disponible y es la opción recomendada si deseas implementar una [integración de reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) que no sea en una aplicación móvil nativa.
 
diff --git a/docs/announcements/es/close-bigger-deals-with-the-shared-cart.md b/docs/announcements/es/close-bigger-deals-with-the-shared-cart.md
index 26b37e71a..73b9a7c42 100644
--- a/docs/announcements/es/close-bigger-deals-with-the-shared-cart.md
+++ b/docs/announcements/es/close-bigger-deals-with-the-shared-cart.md
@@ -41,8 +41,6 @@ El carro compartido sólo es posible debido a la inclusión de un nuevo parámet
 - Utilice las [API de VTEX](https://github.com/vtex/vtex.js/tree/master/docs/checkout#getorderformexpectedorderformsections) para obtener el identificador del carritto.
 - Personalice la página del carrito para que el enlace pase a contar con el ID.
 
-<div class="alert alert-warning">
-Recordamos que el carrito compartido es opcional y los cambios citados aquí deben hacerse <strong>sólo por las tiendas que desean usar la funcionalidad</strong>.
-</div>
+>⚠️ Recordamos que el carrito compartido es opcional y los cambios citados aquí deben hacerse **sólo por las tiendas que desean usar la funcionalidad**.
 
 Lea el [artículo sobre el carrito compartido](/es/tutorial/que-es-el-carrito-compartido) y conozca mejor la nueva funcionalidad.
diff --git a/docs/announcements/es/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md b/docs/announcements/es/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
index 48bcf6ab9..6d2f916ce 100644
--- a/docs/announcements/es/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
+++ b/docs/announcements/es/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
@@ -31,9 +31,7 @@ Póngase en contacto con el equipo de TI de su operación, responsable de las co
 
 Este equipo deberá __revisar las reglas de firewall y ajustarlas, garantizando la liberación del dominio vtexassets.com__.
 
-<div class="alert alert-info">
-Nota: No necesitará hacer ningún ajuste en el front end ya que el dominio <code>vteximg.com.br</code> continuará trabajando para las personalizaciones.
-</div>
+>ℹ️ Nota: No necesitará hacer ningún ajuste en el front end ya que el dominio `vteximg.com.br` continuará trabajando para las personalizaciones.
 
 ## ¿Qué impactos puede sufrir su operación si el ajuste no ocurre?
 
diff --git a/docs/announcements/es/delivery-capacity.md b/docs/announcements/es/delivery-capacity.md
index 81a280bd3..0d7c752f2 100644
--- a/docs/announcements/es/delivery-capacity.md
+++ b/docs/announcements/es/delivery-capacity.md
@@ -40,7 +40,5 @@ Para utilizar la capacidad de entrega, es necesario configurar una política de
 
 Para saber cómo configurar la capacidad de entrega para sus entregas programadas, lea [Capacidad de Entrega](https://help.vtex.com/es/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
-<div class="alert alert-info">
-Esta funcionalidad está en fase Beta y solo está disponible para los ambientes Admin v3.
-</div>
+>ℹ️ Esta funcionalidad está en fase Beta y solo está disponible para los ambientes Admin v3.
 
diff --git a/docs/announcements/es/discontinuation-of-order-completed-order-create-error-and-order-creation.md b/docs/announcements/es/discontinuation-of-order-completed-order-create-error-and-order-creation.md
index fb28dde6f..6790b1ea2 100644
--- a/docs/announcements/es/discontinuation-of-order-completed-order-create-error-and-order-creation.md
+++ b/docs/announcements/es/discontinuation-of-order-completed-order-create-error-and-order-creation.md
@@ -19,9 +19,7 @@ A partir del 24 de junio de 2019, los status de los pedidos de Fulfillment `orde
 
 Los pedidos de origen Fulfillment son aquellos relacionados con las etapas de entrega o recogida de un pedido. Podemos asociar los pedidos que tienen este origen al proceso que realiza un seller para efectuar la entrega o recogida de un pedido.
 
-<div class="alert alert-warning">
-El status de los pedidos de origen Marketplace no se alterará.
-</div>
+>⚠️ El status de los pedidos de origen Marketplace no se alterará.
 
 ## ¿Por qué VTEX está tomando esta acción?
 
diff --git a/docs/announcements/es/discontinuation-of-vtex-payment.md b/docs/announcements/es/discontinuation-of-vtex-payment.md
index 47f89915e..3601c4c75 100644
--- a/docs/announcements/es/discontinuation-of-vtex-payment.md
+++ b/docs/announcements/es/discontinuation-of-vtex-payment.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisES: 'Suspensión de VTEX Payment'
 ---
 
-<div class="alert alert-warning">
-Este contenido no está disponible en este idioma, ya que VTEX Payment solo está disponible para las tiendas de Brasil.
-</div>
+>⚠️ Este contenido no está disponible en este idioma, ya que VTEX Payment solo está disponible para las tiendas de Brasil.
diff --git a/docs/announcements/es/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md b/docs/announcements/es/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
index 35c4ffb57..9a1f5be5a 100644
--- a/docs/announcements/es/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
+++ b/docs/announcements/es/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
@@ -31,6 +31,4 @@ En general, la descontinuación de estos status no debería impactar a ninguna i
 
 Sin embargo, recomendamos que revise su integración para confirmar que estos status no se están utilizando realmente.
 
-<div class="alert alert-info">
-La acción de sacar el workflow del camino crítico del cierre de compra para pedidos de origen Fulfillment ya se realizó. Acceda a nuestro artículo para saber más sobre esta <a href="https://help.vtex.com/es/announcements/descontinuacao-dos-status-dos-pedidos-de-fulfillment-order-completed-order--4AJyu9fJNSKNpL4g4dfgcp"> retirada del workflow en los pedidos de origen Fulfillment.</a>
-</div>
+>ℹ️ La acción de sacar el workflow del camino crítico del cierre de compra para pedidos de origen Fulfillment ya se realizó. Acceda a nuestro artículo para saber más sobre esta [ retirada del workflow en los pedidos de origen Fulfillment.](https://help.vtex.com/es/announcements/descontinuacao-dos-status-dos-pedidos-de-fulfillment-order-completed-order--4AJyu9fJNSKNpL4g4dfgcp)
diff --git a/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 1673e18a9..dd225fb8f 100644
--- a/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/es/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Posibilidad de limitar perfiles de acceso a la pantalla de Autorización de Pedidos'
 ---
 
-<div class="alert alert-warning">
-A partir del 25 de junio de 2019, el usuario que no tenga acceso vinculado al perfil con el producto <code>Order Authorization</code> no tendrá permiso para visualizar o editar la pantalla Autorización de Pedidos.
-</div>
+>⚠️ A partir del 25 de junio de 2019, el usuario que no tenga acceso vinculado al perfil con el producto `Order Authorization` no tendrá permiso para visualizar o editar la pantalla Autorización de Pedidos.
 
 Con el fin de garantizar una mayor seguridad, creamos la posibilidad de limitar perfiles de acceso a la pantalla de Autorización de Pedidos, permitiendo que solo algunos usuarios puedan visualizar o editar las informaciones. Para saber más sobre la Autorización de Pedidos, acceda a  nuestro [comunicado sobre el lanzamiento de la feature](https://help.vtex.com/es/announcements/aumente-sus-ventas-con-la-nueva-pantalla-autorizacion-de-pedidos--7EXIgaESHfI46lkaZw9jrQ) o el [tutorial que explica su funcionamiento](https://help.vtex.com/es/tutorial/como-funciona-la-autorizacion-de-pedidos--3MBK6CmKHAuUjMBieDU0pn).
   
diff --git a/docs/announcements/es/erp-integration-guides-have-a-new-home.md b/docs/announcements/es/erp-integration-guides-have-a-new-home.md
index 140067adb..ee59c670c 100644
--- a/docs/announcements/es/erp-integration-guides-have-a-new-home.md
+++ b/docs/announcements/es/erp-integration-guides-have-a-new-home.md
@@ -27,4 +27,4 @@ Como parte del esfuerzo por migrar la documentación para desarrolladores a nues
 
 Esta documentación utiliza la nueva [API REST del Catálogo](https://developers.vtex.com/docs/guides/catalog-api-overview) y reemplaza nuestra guía anterior basada en la API SOAP del Webservice, que ya no está disponible en nuestro Help Center.
 
-<div class="alert alert-warning">Todavía no hemos desactivado la API SOAP del Webservice, pero ya no se recomienda para nuevas integraciones.</div>
+>⚠️ Todavía no hemos desactivado la API SOAP del Webservice, pero ya no se recomienda para nuevas integraciones.
diff --git a/docs/announcements/es/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md b/docs/announcements/es/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
index fbb18e0be..592783d68 100644
--- a/docs/announcements/es/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
+++ b/docs/announcements/es/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
@@ -23,9 +23,7 @@ Por lo tanto, después de un análisis objetivo y cuidadoso, hemos decidido elim
 
 El soporte al inicio de sesión con Facebook se eliminará de todas las versiones del panel administrativo de VTEX.
 
-<div class="alert alert-info">
-La funcionalidad de inicio de sesión con Facebook seguirá estando disponible para el inicio de sesión de los compradores en tu tienda VTEX.
-</div>
+>ℹ️ La funcionalidad de inicio de sesión con Facebook seguirá estando disponible para el inicio de sesión de los compradores en tu tienda VTEX.
 
 ## ¿Por qué hacemos este cambio?
 
diff --git a/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
index 5cab46f1a..7b2fe8e26 100644
--- a/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
+++ b/docs/announcements/es/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -48,9 +48,7 @@ FastCheckout permite personalizar la experiencia de checkout para adaptarse al c
 
 También es posible incluir elementos completamente personalizados sin necesidad de conocimientos previos de JavaScript o CSS.
 
-<div class="alert alert-warning">
-  <p>La versión inicial de FastCheckout permite personalizaciones limitadas. Pronto será posible personalizar todo el contenido utilizando los puntos de extensión de la plataforma FastStore.</p>
-</div>
+>⚠️ La versión inicial de FastCheckout permite personalizaciones limitadas. Pronto será posible personalizar todo el contenido utilizando los puntos de extensión de la plataforma FastStore.
 
 ### Nuevo flujo de compra
 
diff --git a/docs/announcements/es/freely-develop-custom-storefront-components-in-vtex-io.md b/docs/announcements/es/freely-develop-custom-storefront-components-in-vtex-io.md
index b006a2d36..88e7d8188 100644
--- a/docs/announcements/es/freely-develop-custom-storefront-components-in-vtex-io.md
+++ b/docs/announcements/es/freely-develop-custom-storefront-components-in-vtex-io.md
@@ -27,9 +27,7 @@ Si su tienda está construida con [VTEX Store Framework](https://developers.vtex
 
 A partir de ahora, **desarrolle componentes personalizados de *storefront* en [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io) utilizando las tecnologías VTEX Store Framework y [React](https://reactjs.org/)** de acuerdo con sus necesidades de negocio, sin pedir permiso a VTEX.
 
-<div class="alert alert-info">
-Store Framework es la solución de VTEX para construir <i>storefronts</i> a altísima velocidad. Los clientes VTEX pueden aprovechar todos sus beneficios utilizando la plataforma de desarrollo de VTEX IO. Si no está familiarizado con VTEX IO, póngase en contacto con su Customer Success, Account Manager o Agencia Partner SI (integradora de sistemas) para saber cómo empezar.
-</div>
+>ℹ️ Store Framework es la solución de VTEX para construir <i>storefronts</i> a altísima velocidad. Los clientes VTEX pueden aprovechar todos sus beneficios utilizando la plataforma de desarrollo de VTEX IO. Si no está familiarizado con VTEX IO, póngase en contacto con su Customer Success, Account Manager o Agencia Partner SI (integradora de sistemas) para saber cómo empezar.
 
 ## ¿Qué cambió?
 
@@ -37,9 +35,7 @@ Antes, se requería que los desarrolladores interesados en crear componentes per
 
 Esto ya no es necesario, ya que **hemos pasado nuestro *builder* React oficialmente al status de beta abierta**. Puede disfrutar de esta autonomía para personalizar y mejorar su experiencia de storefront utilizando la tecnología [React](https://reactjs.org/).
 
-<div class="alert alert-warning">
-<bold>Este cambio se aplica únicamente al <i>builder</i> React.</bold> Aún se requiere que complete el <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">Formulario de solicitud para desarrollo</a> y espere nuestra aprobación si su proyecto depende de <i>builders</i> que todavía están en beta cerrada. Esto incluye, por ejemplo, integraciones de <i>back-end</i> utilizando Node.js y GraphQL.  
-</div>
+>⚠️ <bold>Este cambio se aplica únicamente al <i>builder</i> React.</bold> Aún se requiere que complete el [Formulario de solicitud para desarrollo](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io) y espere nuestra aprobación si su proyecto depende de <i>builders</i> que todavía están en beta cerrada. Esto incluye, por ejemplo, integraciones de <i>back-end</i> utilizando Node.js y GraphQL.
 
 ## ¿Por qué realizamos este cambio?
 
@@ -49,7 +45,5 @@ Entendemos que VTEX IO ha alcanzado suficiente madurez y estabilidad como plataf
 
 No se requiere ninguna acción por su parte. No obstante, tenga en cuenta que **VTEX no ofrece soporte para componentes personalizados desarrollados por terceros**. Su mantenimiento, desempeño y calidad están bajo la responsabilidad del proveedor de la aplicación.
 
-<div class="alert alert-info">
-Consulte nuestra documentación sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-developing-custom-storefront-components">las mejores prácticas para el desarrollo de componentes personalizados de <i>storefront</i></a>!
-</div>
+>ℹ️ Consulte nuestra documentación sobre [las mejores prácticas para el desarrollo de componentes personalizados de <i>storefront</i>](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-developing-custom-storefront-components)!
 
diff --git a/docs/announcements/es/from-now-on-you-can-create-promotional-price-tables.md b/docs/announcements/es/from-now-on-you-can-create-promotional-price-tables.md
index 7238cd837..80aaf2ffd 100644
--- a/docs/announcements/es/from-now-on-you-can-create-promotional-price-tables.md
+++ b/docs/announcements/es/from-now-on-you-can-create-promotional-price-tables.md
@@ -37,12 +37,8 @@ Si aún no tiene una tabla de precios o si desea crear una nueva, el artículo [
 
 Completando los pasos arriba, su tabla de precios promocionales va a estar activa y lista para ser aplicada. Pero recuerde que la promoción tarda __10 minutos__ hasta que sea visible y empieza a reflejarse en los pedidos en la tienda.
 
-<div class="alert alert-info">
-Hay algunas características específicas de esta promoción que deben tenerse en cuenta en el momento de la creación y utilización:</br>
-<strong>1-</strong> El precio configurado en la tabla de precios se aplicará sólo si el valor es menor que el configurado en la política comercial utilizada por el sitio. <em>Ejemplo:</em> el ítem que posee un precio de $ 199,00 sólo tendrá el valor de la tabla aplicado si este último es menor que $ 199,00.</br>
-<strong>2-</strong> Las promociones de tablas de precios compiten entre sí y con las demás promociones configuradas que manipulan precios. Es decir, si hay más de una promoción de tabla de precios configurada y al menos una promoción de descuento porcentual, nominal, o fórmula (activas y elegibles al carrito en cuestión), el precio más bajo entre ellas es el que se aplicará.
-</div>
-
-<div class="alert alert-warning">
-Sólo se puede configurar <strong>una tabla de precios por promoción</strong>. Y, hoy, <strong>hay un límite de hasta 5 promociones de tablas de precios simultáneas</strong> para cada tienda.
-</div>
+>ℹ️ Hay algunas características específicas de esta promoción que deben tenerse en cuenta en el momento de la creación y utilización:</br>
+> **1-** El precio configurado en la tabla de precios se aplicará sólo si el valor es menor que el configurado en la política comercial utilizada por el sitio. *Ejemplo:* el ítem que posee un precio de $ 199,00 sólo tendrá el valor de la tabla aplicado si este último es menor que $ 199,00.</br>
+> **2-** Las promociones de tablas de precios compiten entre sí y con las demás promociones configuradas que manipulan precios. Es decir, si hay más de una promoción de tabla de precios configurada y al menos una promoción de descuento porcentual, nominal, o fórmula (activas y elegibles al carrito en cuestión), el precio más bajo entre ellas es el que se aplicará.
+
+>⚠️ Sólo se puede configurar **una tabla de precios por promoción**. Y, hoy, **hay un límite de hasta 5 promociones de tablas de precios simultáneas** para cada tienda.
diff --git a/docs/announcements/es/from-now-on-you-can-export-up-to-3-thousand-orders.md b/docs/announcements/es/from-now-on-you-can-export-up-to-3-thousand-orders.md
index d034d44ea..c54dd398d 100644
--- a/docs/announcements/es/from-now-on-you-can-export-up-to-3-thousand-orders.md
+++ b/docs/announcements/es/from-now-on-you-can-export-up-to-3-thousand-orders.md
@@ -23,6 +23,4 @@ Para que el proceso fuera lo más ágil posible, ya veníamos recomendando el l
 ## Cómo exportar más de 3.000 pedidos
 Usted todavía puede exportar más de 3.000 pedidos. Para ello, utilice las APIs de gestión de pedidos (anteriormente conocido como OMS): [Get Order](https://developers.vtex.com/reference/orders#getorder) y [Get Feed Order Status](https://developers.vtex.com/reference/feed-v3#getfeedorderstatus1).
 
-<div class="alert alert-warning">
-<strong>Pero recuerde:</strong> para funcionar, es necesario que usted <strong>cree un range de fecha/hora que incluya un máximo de 3.000 pedidos</strong>. Con el range definido y el límite respetado, usted podrá llamar al API tantas veces como sea necesario.
-</div>
+>⚠️ **Pero recuerde:** para funcionar, es necesario que usted **cree un range de fecha/hora que incluya un máximo de 3.000 pedidos**. Con el range definido y el límite respetado, usted podrá llamar al API tantas veces como sea necesario.
diff --git a/docs/announcements/es/google-catalog-migration.md b/docs/announcements/es/google-catalog-migration.md
index 6f5546ea3..09053f1d0 100644
--- a/docs/announcements/es/google-catalog-migration.md
+++ b/docs/announcements/es/google-catalog-migration.md
@@ -23,9 +23,7 @@ La funcionalidad está dirigida a sellers que anteriormente integraban los produ
 
 El objetivo de esta funcionalidad es permitir al seller la migración de la relevancia de sus anuncios en Google Shopping. Al llevar a cabo la migración con el conector de VTEX, el seller no pierde el historial de relevancia de sus anuncios.
 
-<div class="alert alert-info">
-La migración del catálogo solo mapea y realiza match entre productos del catálogo VTEX con anuncios existentes en Merchant Center de Google Shopping.
-</div>
+>ℹ️ La migración del catálogo solo mapea y realiza match entre productos del catálogo VTEX con anuncios existentes en Merchant Center de Google Shopping.
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/headless-cms-events-available-in-audit.md b/docs/announcements/es/headless-cms-events-available-in-audit.md
index 0d700c31f..9ab1cc029 100644
--- a/docs/announcements/es/headless-cms-events-available-in-audit.md
+++ b/docs/announcements/es/headless-cms-events-available-in-audit.md
@@ -38,9 +38,7 @@ En la columna **Acción**, todos los eventos de Headless CMS también muestran l
 * **VARIANT_ID:** código identificador único de la versión del contenido.
 * **WORKSPACE**: workspace en el que se realizó el cambio.
 
-<div class="alert alert-info">
-  <p>Consulta la<a href="https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ"> lista completa de eventos disponibles en Audit</a>.</p>
-</div>
+>ℹ️ Consulta la[ lista completa de eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/improvement-of-the-seller-white-label-selection-algorithm.md b/docs/announcements/es/improvement-of-the-seller-white-label-selection-algorithm.md
index ad390fb93..4220e3f5e 100644
--- a/docs/announcements/es/improvement-of-the-seller-white-label-selection-algorithm.md
+++ b/docs/announcements/es/improvement-of-the-seller-white-label-selection-algorithm.md
@@ -27,9 +27,7 @@ Actualizamos el algoritmo de selección de sellers para asegurar la mayor cobert
 
 Además, para elegir los sellers que ofrecen la opción de recogida, el algoritmo siempre priorizará la distancia de la ubicación de referencia sobre los criterios de precio y plazo para la recogida.
 
-<div class="alert alert-warning">
-Atención: La actualización del algoritmo se aplica a Sellers White Label, e incluye a <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">Cuentas Franquicia</a>. El algoritmo de selección de seller es aplicado cuando el cliente consulta las opciones de entrega. Esto significa que se aplica a la previsión de entrega en el carrito o en la etapa de entrega y recogida del checkout.
-</div>
+>⚠️ Atención: La actualización del algoritmo se aplica a Sellers White Label, e incluye a [Cuentas Franquicia](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa). El algoritmo de selección de seller es aplicado cuando el cliente consulta las opciones de entrega. Esto significa que se aplica a la previsión de entrega en el carrito o en la etapa de entrega y recogida del checkout.
 
 ## ¿Por qué realizamos este cambio?
 El objetivo de esta mejora es ayudar a reducir la tasa de abandono de carritos por los compradores en las tiendas de los clientes VTEX. Esto impacta directamente en la tasa de conversión.
diff --git a/docs/announcements/es/integrations-with-vtex-apis-now-need-token-authentication.md b/docs/announcements/es/integrations-with-vtex-apis-now-need-token-authentication.md
index 576c98392..6b62e0c17 100644
--- a/docs/announcements/es/integrations-with-vtex-apis-now-need-token-authentication.md
+++ b/docs/announcements/es/integrations-with-vtex-apis-now-need-token-authentication.md
@@ -37,4 +37,4 @@ Utilizar email y contraseña para la autenticación compromete la seguridad de s
 - Compruebe si su tienda utiliza email y contraseña en alguna integración con las API de VTEX.
 - Si lo usa, cree un par de appKey y appToken para esa integración. Vea como en el artículo [Crear appKey y appToken para autenticar integraciones](http://help.vtex.com/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations).
 
-<div class="alert alert-warning"><strong>Atención</strong>: todo par de appKey y appToken, cuando se crea, nace sin estar vinculado a un perfil de acceso. Entonces, después de crearlo, es necesario vincular la appKey y el appToken al perfil de acceso deseado.</div>
+>⚠️ **Atención**: todo par de appKey y appToken, cuando se crea, nace sin estar vinculado a un perfil de acceso. Entonces, después de crearlo, es necesario vincular la appKey y el appToken al perfil de acceso deseado.
diff --git a/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
index 465183b69..e499fb9dc 100644
--- a/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/es/introducing-the-new-shipping-strategy-interfaces.md
@@ -38,7 +38,5 @@ A partir del 31 de mayo, la versión beta de la **Estrategia de envío** está d
 
 Si después de probar el beta deseas volver a la versión anterior, en el menú <i class="fas fa-ellipsis-v"></i> en la parte superior de **Estrategia de envío**, haga clic en `Cambiar a la versión anterior` y comenta el motivo. El regreso será automático.
 
-<div class="alert alert-warning">
-A partir del 26 de julio, las nuevas interfaces de la <b>Estrategia de envío</b> sean el estándar para todas las tiendas VTEX.
-</div>
+>⚠️ A partir del 26 de julio, las nuevas interfaces de la **Estrategia de envío** sean el estándar para todas las tiendas VTEX.
 
diff --git a/docs/announcements/es/introducing-vtex-ad-network-beta.md b/docs/announcements/es/introducing-vtex-ad-network-beta.md
index a0238d6c1..888d724d3 100644
--- a/docs/announcements/es/introducing-vtex-ad-network-beta.md
+++ b/docs/announcements/es/introducing-vtex-ad-network-beta.md
@@ -39,9 +39,7 @@ Consulta a continuación cómo puedes formar parte de **VTEX Ad Network**, como
 
 Para disponibilizar espacios para anuncios en tu tienda, instala la aplicación [VTEX Ad Network para retailers]() en tu cuenta VTEX. Para saber más, consulta el artículo [Mostrar anuncios con VTEX Ad Network en tu tienda (Beta)](https://help.vtex.com/es/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA).
 
-<div class="alert alert-danger">
-Por el momento, solamente tiendas desarrolladas con <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> pueden ofrecer espacios para anuncios.
-</div>
+>❗ Por el momento, solamente tiendas desarrolladas con [Store Framework](https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) pueden ofrecer espacios para anuncios.
 
 ### Anunciantes
 
diff --git a/docs/announcements/es/last-chance-to-buy-tickets-for-vtex-training-day.md b/docs/announcements/es/last-chance-to-buy-tickets-for-vtex-training-day.md
index 8abccf3c9..87e01d868 100644
--- a/docs/announcements/es/last-chance-to-buy-tickets-for-vtex-training-day.md
+++ b/docs/announcements/es/last-chance-to-buy-tickets-for-vtex-training-day.md
@@ -38,9 +38,9 @@ El escenario del VTEX IO, la plataforma de desarrollo de VTEX. Nuestros ingenier
 <br />
 <br />
 
-<div class="alert alert-info">
-¡<strong>Garantiza un 30% de descuento</strong> en la compra de 10 o más ingresos! <br />Pero corre, que la promoción es válida sólo hasta finales de noviembre.
-</div>
+>ℹ️ ¡**Garantiza un 30% de descuento** en la compra de 10 o más ingresos! 
+>
+> Pero corre, que la promoción es válida sólo hasta finales de noviembre.
 
 
 __¿Cuando?__ 06/12/2018 _(o evento dura o dia todo)_ 
diff --git a/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
index 072d8dcc1..c637a56ad 100644
--- a/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
+++ b/docs/announcements/es/lead-time-configuring-shipping-time-at-sku-level.md
@@ -33,9 +33,7 @@ Ahora, también existe la opción de configurar el tiempo de envío a nivel de S
 
 ![lead_time_inventory_management_ES](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
 
-<div class="alert alert-warning">
-En el Admin VTEX, el lead time se configura en días, hasta un límite de 365. De manera predeterminada, el contaje se realiza en días laborables, pero puedes configurar tu política de envío para se <a href="https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional">realice en días naturales</a>. Para configurar periodos en horas, minutos y segundos debes utilizar el endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>⚠️ En el Admin VTEX, el lead time se configura en días, hasta un límite de 365. De manera predeterminada, el contaje se realiza en días laborables, pero puedes configurar tu política de envío para se [realice en días naturales](https://help.vtex.com/es/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional). Para configurar periodos en horas, minutos y segundos debes utilizar el endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md b/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md
index 90a944294..7c3811e1e 100644
--- a/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md
+++ b/docs/announcements/es/legacy-payment-connectors-will-be-discontinued-in-2024.md
@@ -19,9 +19,7 @@ Para integrar los medios de pago en la plataforma VTEX, los proveedores de pago
 
 ## ¿Qué va a cambiar?
 
-<div class="alert alert-danger">
-Los cambios descritos en este documento no tendrán ninguna repercusión en el Black Friday 2023,  ya que no se aplicarán hasta el primer trimestre de 2024.
-</div>
+>❗ Los cambios descritos en este documento no tendrán ninguna repercusión en el Black Friday 2023,  ya que no se aplicarán hasta el primer trimestre de 2024.
 
 VTEX está iniciando la descontinuación de estos conectores legados, lo que ocurrirá por etapas:
 
@@ -109,9 +107,7 @@ Si actúas como proveedor de pago responsable de uno o más [conectores que ser
 
 En este caso, te recomendamos que presentes un nuevo conector para homologación antes del 10 de febrero de 2024 para que las tiendas tengan tiempo de reconfigurar sus conexiones de pago antes de la descontinuación. Aquí puedes consultar más información sobre el [proceso de homologación de nuevos conectores de pago](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
 
-<div class="alert alert-danger">
-VTEX no puede garantizar que tu nuevo conector de pago esté disponible para administradores de tiendas VTEX antes de la descontinuación oficial si lo presentas para homologación después de esta fecha.
-</div>
+>❗ VTEX no puede garantizar que tu nuevo conector de pago esté disponible para administradores de tiendas VTEX antes de la descontinuación oficial si lo presentas para homologación después de esta fecha.
 
 Si tienes alguna pregunta sobre este proceso o deseas alinear la información con los administradores de tiendas, ponte en contacto con tu Partner Manager VTEX.
 
diff --git a/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
index 3bee9311e..e64c93e16 100644
--- a/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
+++ b/docs/announcements/es/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -35,6 +35,4 @@ El rechazo de una transacción de pago debido a un número de tarjeta inválido
 
 No se requiere ninguna acción. El algoritmo de Luhn ya está activo en todas las tiendas VTEX.
 
-<div class="alert alert-warning">
-El algoritmo de Luhn no restringe el fraude por ataques con tarjeta. El objetivo específico es comprobar si hay errores tipográficos o del valor ingresado en los números de las tarjetas.
-</div>
+>⚠️ El algoritmo de Luhn no restringe el fraude por ataques con tarjeta. El objetivo específico es comprobar si hay errores tipográficos o del valor ingresado en los números de las tarjetas.
diff --git a/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
index 872aed2aa..e4e79ff08 100644
--- a/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/es/maximum-price-per-item-promotion-will-be-disabled.md
@@ -21,9 +21,9 @@ De hecho, estamos haciendo este cambio justamente porque, con la evolución de l
 
 Eliminando la promoción Precio Máximo por Artículo, mejoramos el rendimiento del módulo de promociones y la gestión de las tiendas.
 
-<div class="alert alert-warning">Hasta el día 20 de noviembre, la promoción Precio máximo por Artículo sigue existiendo. Sin embargo, el número máximo de elementos permitidos pasa a ser <b>100</b>. Anteriormente el máximo permitido era 500.</div>
+>⚠️ Hasta el día 20 de noviembre, la promoción Precio máximo por Artículo sigue existiendo. Sin embargo, el número máximo de elementos permitidos pasa a ser **100**. Anteriormente el máximo permitido era 500.
 
-<div class="alert alert-danger">Si usted utiliza alguna promoción Precio Máximo por Artículo, lea este texto hasta el final y adapte el método en su tienda. En caso contrario, los SKUs en cuestión dejarán de ser impactados por esta estrategia de negocio.</div>
+>❗ Si usted utiliza alguna promoción Precio Máximo por Artículo, lea este texto hasta el final y adapte el método en su tienda. En caso contrario, los SKUs en cuestión dejarán de ser impactados por esta estrategia de negocio.
 
 ## Alternativas
 
diff --git a/docs/announcements/es/multi-currency-gift-card.md b/docs/announcements/es/multi-currency-gift-card.md
index 5ca5019d5..aa6288901 100644
--- a/docs/announcements/es/multi-currency-gift-card.md
+++ b/docs/announcements/es/multi-currency-gift-card.md
@@ -43,6 +43,4 @@ Para crear una tarjeta de regalo en una moneda concreta, sigue los pasos que se
 
 Las monedas disponibles serán las mismas que las registradas en las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) de cada tienda.
 
-<div class="alert alert-warning">
-La elección de la moneda debe hacerse durante la creación de cada tarjeta de regalo o de un lote de tarjetas de regalo. No es posible cambiar la moneda asignada a una tarjeta de regalo una vez creada.
-</div>
+>⚠️ La elección de la moneda debe hacerse durante la creación de cada tarjeta de regalo o de un lote de tarjetas de regalo. No es posible cambiar la moneda asignada a una tarjeta de regalo una vez creada.
diff --git a/docs/announcements/es/my-authentication-section-in-my-account.md b/docs/announcements/es/my-authentication-section-in-my-account.md
index 14b0aa73c..63b834303 100644
--- a/docs/announcements/es/my-authentication-section-in-my-account.md
+++ b/docs/announcements/es/my-authentication-section-in-my-account.md
@@ -17,9 +17,7 @@ announcementSynopsisES: 'My Authentication es una pestaña de My Account que per
 
 My Authentication es una pestaña que aparece en el panel de My Account dentro de la tienda y está disponible en todas las cuentas VTEX.
 
-<div class="alert alert-danger">
-Este cambio afectará a todas las tiendas VTEX. Debido a que el cambio interfiere en algunos componentes de la interfaz de usuario de la tienda, es necesario realizar cambios manuales en la configuración de la tienda antes de la fecha límite del 29 de septiembre.
-</div>
+>❗ Este cambio afectará a todas las tiendas VTEX. Debido a que el cambio interfiere en algunos componentes de la interfaz de usuario de la tienda, es necesario realizar cambios manuales en la configuración de la tienda antes de la fecha límite del 29 de septiembre.
 
 ## ¿Qué cambia?
 
@@ -55,9 +53,7 @@ Debido a que la habilitación de la pestaña inserta un elemento en la interfaz
 - Si su tienda es VTEX IO, utilice la dirección `https://{account}.myvtex.com/account#/authentication`, sustituyendo `{account}` por el nombre de la cuenta.
 - Si su tienda no usa VTEX IO, utilice la dirección `https://{account}.vtexcommercestable.com.br/_secure/account#/authentication`, sustituyendo `{account}` por el nombre de la cuenta.
 
-<div class="alert alert-warning">
-Antes de acceder a la pestaña de autentificación a través de la URL es necesario acceder a la tienda con una cuenta de usuario.
-</div>
+>⚠️ Antes de acceder a la pestaña de autentificación a través de la URL es necesario acceder a la tienda con una cuenta de usuario.
 
 Para realizar la personalización de la apariencia de la pestaña, pida al desarrollador que consulte el artículo [My Authentication Customization Guide using CMS](https://developers.vtex.com/vtex-rest-api/docs/ui-customization-my-authentication), para las tiendas que no usan VTEX IO, o el artículo [My Authentication Customization Guide on VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-my-authentication), para las tiendas de VTEX IO, en nuestro portal del desarrollador.
 
diff --git a/docs/announcements/es/my-orders-is-now-available-on-extension-store.md b/docs/announcements/es/my-orders-is-now-available-on-extension-store.md
index 2c9e176ec..6be4bee60 100644
--- a/docs/announcements/es/my-orders-is-now-available-on-extension-store.md
+++ b/docs/announcements/es/my-orders-is-now-available-on-extension-store.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'A partir del 5 de junio, el uso de la extensión a la página "Mis pedidos" será obligatorio para todas las tiendas.'
 ---
 
-<div class="alert alert-info">
-Como se anunció aquí, <strong>My Orders</strong> ya es obligatorio para todas las tiendas. Desde el <strong>6 de junio</strong> está disponible de forma predeterminada y ya no es necesario instalarla a través de la App Store de VTEX.
-</div>
+>ℹ️ Como se anunció aquí, **My Orders** ya es obligatorio para todas las tiendas. Desde el **6 de junio** está disponible de forma predeterminada y ya no es necesario instalarla a través de la App Store de VTEX.
 
 Ya está disponible en la __App Store__ de VTEX el __My Orders__, una extensión que trae una serie de mejoras a la página "Mis Pedidos". Por todas las ventajas que ofrece (incluyendo facilidad de personalización y aumentos de rendimiento de la página), su uso pasará a ser obligatorio a partir del __5 de junio__.
 
@@ -25,7 +23,7 @@ Entre las novedades de la nueva extensión están el soporte para visualización
 
 Otra característica importante es que ahora los datos de los pedidos vienen de la API del OMS. Un cambio que deja el status del pedido mucho más preciso.
 
-<div class="alert alert-warning">
-<strong>Atención</strong><br>
-Recomendamos que instale el <strong>My Orders</strong> en su tienda cuanto antes, sobre todo si ya tiene alguna personalización en la página "Mis Pedidos". Dessa forma, você vai poder testar todas as possibilidades da nova extensão e evitar quebras quando ela se tornar obrigatória. De esta manera, usted podrá probar todas las posibilidades de la nueva extensión y evitar errores cuando se convierta en obligatoria.
-</div>
+>⚠️ **Atención**
+>
+> 
+> Recomendamos que instale el **My Orders** en su tienda cuanto antes, sobre todo si ya tiene alguna personalización en la página "Mis Pedidos". Dessa forma, você vai poder testar todas as possibilidades da nova extensão e evitar quebras quando ela se tornar obrigatória. De esta manera, usted podrá probar todas las posibilidades de la nueva extensión y evitar errores cuando se convierta en obligatoria.
diff --git a/docs/announcements/es/new-deadline-activate-the-new-cdn-until-may-31.md b/docs/announcements/es/new-deadline-activate-the-new-cdn-until-may-31.md
index ffb2a6ae6..f2ad25206 100644
--- a/docs/announcements/es/new-deadline-activate-the-new-cdn-until-may-31.md
+++ b/docs/announcements/es/new-deadline-activate-the-new-cdn-until-may-31.md
@@ -45,9 +45,7 @@ Después de activar HTTPS, debe:
 
 Si el dominio de su tienda apunta a algo que contenga `vtexcommerce.com.br` o `hodor.vtex.com`, eso significa que todavía usa el CNAME antiguo. La actualización es necesaria porque sólo será posible tener contenido en el dominio `{hostname}.cdn.vtex.com`.
 
-<div class="alert alert-warning">
-Después de <strong>31 de mayo</strong>, todos los CNAME antiguos dejarán de entregar las tiendas. Si usted está usando un CNAME antiguo, <strong>su tienda ya no funcionará</strong>.
-</div>
+>⚠️ Después de **31 de mayo**, todos los CNAME antiguos dejarán de entregar las tiendas. Si usted está usando un CNAME antiguo, **su tienda ya no funcionará**.
 
 Después de activar HTTPS y actualizar al nuevo CNAME de VTEX, necesitará solicitar la activación del nuevo CDN. Si esto no se realiza hasta __31 de mayo__, la activación se realizará de manera automática. Por eso, es fundamental que usted realice todas las acciones ya comunicadas anteriormente y reforzadas en este anuncio. Así, usted evita problemas en la tienda que podrían ser evitados.
 
diff --git a/docs/announcements/es/new-facebook-business-extension-integration-app.md b/docs/announcements/es/new-facebook-business-extension-integration-app.md
index 45c58255b..cefc2390d 100644
--- a/docs/announcements/es/new-facebook-business-extension-integration-app.md
+++ b/docs/announcements/es/new-facebook-business-extension-integration-app.md
@@ -62,8 +62,6 @@ Las funcionalidades que se instalan automáticamente con la integración de la a
 
 Para integrar tu tienda VTEX con FBE, sigue los pasos de la [guía de Integración con Facebook Business Extension](https://help.vtex.com/es/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D).
 
-<div class="alert alert-warning">
-Incluso si ya has configurado la <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">integración con Facebook</a>, se recomienda que realices la integración con la aplicación <i>Facebook Business Extension y Conversions API</i>. Esto te permitirá disponer de servicios mejorados y nuevas funcionalidades. 
-</div>
+>⚠️ Incluso si ya has configurado la <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">integración con Facebook</a>, se recomienda que realices la integración con la aplicación <i>Facebook Business Extension y Conversions API</i>. Esto te permitirá disponer de servicios mejorados y nuevas funcionalidades.
 
 Cabe resaltar que no hay ninguna interferencia entre las dos integraciones. Una vez completada la integración con la aplicación _Facebook Business Extension y Conversions API_, tu tienda podrá acceder a todos los servicios que ofrece Facebook Business Extension.
diff --git a/docs/announcements/es/new-limits-for-causes-of-benefit.md b/docs/announcements/es/new-limits-for-causes-of-benefit.md
index 2a8317437..76b836ee8 100644
--- a/docs/announcements/es/new-limits-for-causes-of-benefit.md
+++ b/docs/announcements/es/new-limits-for-causes-of-benefit.md
@@ -21,10 +21,9 @@ Una causa de promoción es cualquier condición que genera una promoción.
 
 Por ejemplo: el minorista puede configurar una promoción para que se aplique si el cliente elige un medio de pago. En este caso, el medio de pago es la causa de la promoción.
 
-<div class="alert alert-danger">No se puede guardar una promoción que no respete alguno de los límites. Por lo tanto, si actualmente su tienda tiene promociones que superen alguno de esos límites, esté atento.
-
-Cualquier cambio en alguna de estas promociones hará que los nuevos límites sean aplicados. Por lo tanto, usted no podrá guardar la promoción con la configuración anterior.
-</div>
+>❗ No se puede guardar una promoción que no respete alguno de los límites. Por lo tanto, si actualmente su tienda tiene promociones que superen alguno de esos límites, esté atento.
+>
+> Cualquier cambio en alguna de estas promociones hará que los nuevos límites sean aplicados. Por lo tanto, usted no podrá guardar la promoción con la configuración anterior.
 
 Los siguientes son los nuevos límites para cada causa de promoción:
 
diff --git a/docs/announcements/es/new-master-data-API-increases-configuration-flexibility.md b/docs/announcements/es/new-master-data-API-increases-configuration-flexibility.md
index f5a3220d5..8577d7891 100644
--- a/docs/announcements/es/new-master-data-API-increases-configuration-flexibility.md
+++ b/docs/announcements/es/new-master-data-API-increases-configuration-flexibility.md
@@ -15,4 +15,4 @@ announcementImageID: ''
 announcementSynopsisES: 'Nueva versión trae features que permiten más flexibilidad de configuración de las estructuras almacenadas en Master Data'
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md b/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md
index 8cb2b5c02..ae7096a56 100644
--- a/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md
+++ b/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md
@@ -77,8 +77,6 @@ Una vez que haya configurado la regla de divergencia de precios, se aplicará a
 
 Para los VTEX marketplaces, los marketplaces externos y los conectores certificados (partners), siempre que no se haya creado la regla de Divergencia de precios, los pedidos con error de divergencia de valores se aprueban automáticamente.
 
-<div class="alert alert-warning">
-Para los <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a>, aunque el seller no <a href= "https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configura la regla de Divergencia de precios</a>, se retienen los pedidos con divergencia de valores. Puede consultarlos en su VTEX Admin, en <b>MARKETPLACE > Integraciones > Pedidos</b>.
-</div>
+>⚠️ Para los <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a>, aunque el seller no <a href= "https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configura la regla de Divergencia de precios</a>, se retienen los pedidos con divergencia de valores. Puede consultarlos en su VTEX Admin, en **MARKETPLACE > Integraciones > Pedidos**.
 
 Si no desea que los conectores nativos obedezcan la regla de Divergencia de precios, puede mantener el flujo antiguo. En este caso, póngase en [contacto con el equipo de soporte de VTEX.](https://support.vtex.com/hc/es-es/requests)
diff --git a/docs/announcements/es/new-ready-to-dispatch-functionality.md b/docs/announcements/es/new-ready-to-dispatch-functionality.md
index 297af5a7a..2ef583dcb 100644
--- a/docs/announcements/es/new-ready-to-dispatch-functionality.md
+++ b/docs/announcements/es/new-ready-to-dispatch-functionality.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisES: ' Nueva funcionalidad VTEX Log para la impresión de etiquetas y la notificación al transportista.'
 ---
 
-<div class="alert alert-warning">
-Este contenido no está disponible en este idioma, ya que la nueva funcionalidad solo está disponible para las tiendas de Brasil que utilizan la solución VTEX Shipping Network.
-</div>
+>⚠️ Este contenido no está disponible en este idioma, ya que la nueva funcionalidad solo está disponible para las tiendas de Brasil que utilizan la solución VTEX Shipping Network.
diff --git a/docs/announcements/es/new-rules-for-activating-vtex-support.md b/docs/announcements/es/new-rules-for-activating-vtex-support.md
index 1b601aabc..066b66096 100644
--- a/docs/announcements/es/new-rules-for-activating-vtex-support.md
+++ b/docs/announcements/es/new-rules-for-activating-vtex-support.md
@@ -17,7 +17,7 @@ announcementSynopsisES: 'Para cuentas en Brasil, ahora es esencial tener Open Su
 
 Las cuentas de Brasil ahora requieren que los roles de los usuarios tengan asignado el recurso **Open Support Ticket** del producto **VTEX - Support** para poder solicitar asistencia del equipo de soporte VTEX. Un usuario con el rol *User Administrator - Restricted* debe asignar el permiso en [License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete).
 
-<div class="alert alert-info"> Los usuarios administrativos asociados al rol <strong> Owner (Admin Super)</strong> tienen el recurso <em> Open Support Ticket </em> asignado automáticamente.</div> 
+>ℹ️ Los usuarios administrativos asociados al rol ** Owner (Admin Super)** tienen el recurso * Open Support Ticket * asignado automáticamente. 
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/new-subscriptions-module.md b/docs/announcements/es/new-subscriptions-module.md
index 3d81c3458..33ff6a85f 100644
--- a/docs/announcements/es/new-subscriptions-module.md
+++ b/docs/announcements/es/new-subscriptions-module.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'El módulo Suscripciones es una solución de VTEX para pedidos recurrentes en su tienda, y está en constante evolución'
 ---
 
-<div class="alert alert-info">
-  <p>La actualización solo afectará a las tiendas que poseen el módulo Suscripciones. Para las tiendas que no tienen esta funcionalidad, nada cambiará.</p>
-</div>
+>ℹ️ La actualización solo afectará a las tiendas que poseen el módulo Suscripciones. Para las tiendas que no tienen esta funcionalidad, nada cambiará.
 
 El módulo Suscripciones es una solución de VTEX para pedidos recurrentes en su tienda, y está en constante evolución. Mejoramos el módulo para agilizar el desempeño del sistema y entregar nuevas funcionalidades que mejoran la experiencia del consumidor de su tienda. Este artículo detalla todos los cambios del módulo y lo que se necesita realizar en su tienda. 
 
@@ -77,6 +75,4 @@ El cálculo de la próxima fecha del pedido por suscripción cambió. Esta alter
 Recordamos que, si su tienda no utiliza nuestras APIs en integraciones, no se necesita realizar ninguna adaptación, la evolución será implementada de forma automática por el sistema de VTEX. 
 Para los administradores de tiendas o partners que utilizan nuestra API de Suscripciones, cabe señalar que todas las anteriores rutas de la API de Suscripciones se sustituirán por nuevas, para reflejar la evolución del módulo. Todo el proceso de migración será apoyado por el equipo de VTEX, garantizando una transición sin problemas al nuevo módulo. Vea nuestra [guía de integración con el nuevo módulo de Suscripciones](https://developers.vtex.com/vtex-developer-docs/docs/subscriptions-v3-migration-guide).
 
-<div class="alert alert-info">
-  Solicita la nueva interfaz de Suscripciones a nuestro <a href="https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM">soporte</a>. La tienda debe contar con la instalación de Search of Biggy (<a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>) para activar la nueva interfaz.
-  </div>
+>ℹ️ Solicita la nueva interfaz de Suscripciones a nuestro [soporte](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM). La tienda debe contar con la instalación de Search of Biggy ([Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)) para activar la nueva interfaz.
diff --git a/docs/announcements/es/new-vtex-shipping-network-performance-page.md b/docs/announcements/es/new-vtex-shipping-network-performance-page.md
index 40ba7082d..29cf62e3f 100644
--- a/docs/announcements/es/new-vtex-shipping-network-performance-page.md
+++ b/docs/announcements/es/new-vtex-shipping-network-performance-page.md
@@ -41,7 +41,4 @@ Este proceso de actualización se realizará de forma nativa. No se requiere nin
 
 Para comprender mejor cómo funciona el desempeño de VTEX Shipping Network, lea el artículo[ Seguimiento de desempeño de transportadora](https://help.vtex.com/es/tutorial/painel-vtex-log--51e8tx1IehiN4ZtURRWU92?&utm_source=autocomplete).
 
-<div class="alert alert-info">
-
-Por el momento, VTEX Shipping Network solo está disponible para Brasil. Para obtener más información sobre VTEX Shipping Network, lea el artículo  <a href="https://vtex.com/br-pt/log/">Conozca VTEX Shipping Network, la solución para entregas de VTEX</a>.
-</div>
+>ℹ️ Por el momento, VTEX Shipping Network solo está disponible para Brasil. Para obtener más información sobre VTEX Shipping Network, lea el artículo  [Conozca VTEX Shipping Network, la solución para entregas de VTEX](https://vtex.com/br-pt/log/).
diff --git a/docs/announcements/es/new-working-hours-setup-is-now-available-for-carriers.md b/docs/announcements/es/new-working-hours-setup-is-now-available-for-carriers.md
index e2bad27c7..1b131462f 100644
--- a/docs/announcements/es/new-working-hours-setup-is-now-available-for-carriers.md
+++ b/docs/announcements/es/new-working-hours-setup-is-now-available-for-carriers.md
@@ -33,11 +33,7 @@ Para configurar las horas de funcionamiento para las compañías de transporte,
 ## Próximos pasos
 En breve, también se permitirá la creación de más de un horario al día. Así, tiendas que cierran para la siesta, por ejemplo, van a poder registrar sus horarios de pausa. Consulte el artículo [Configurar horario de funcionamiento de la transportadora](https://help.vtex.com/es/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS).
 
-<div class="alert alert-info">
-La configuración viene, por default, con todos los días marcados y con los horarios de 00:00 a 23:59 (siempre en horario local).
-</div>
+>ℹ️ La configuración viene, por default, con todos los días marcados y con los horarios de 00:00 a 23:59 (siempre en horario local).
 
-<div class="alert alert-warning">
-Al utilizar la opción de horario de funcionamiento, no es posible utilizar el tiempo de corte. Esto quiere decir que usted tendrá que elegir cuál de las configuraciones tiene más sentido para su tienda.
-</div>
+>⚠️ Al utilizar la opción de horario de funcionamiento, no es posible utilizar el tiempo de corte. Esto quiere decir que usted tendrá que elegir cuál de las configuraciones tiene más sentido para su tienda.
 
diff --git a/docs/announcements/es/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md b/docs/announcements/es/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
index af5c1bbf4..1a73f22b3 100644
--- a/docs/announcements/es/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
+++ b/docs/announcements/es/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
@@ -27,9 +27,7 @@ Usted ya puede ofrecer los productos de toda su red de tiendas físicas en __mar
 
 Ninguna acción es necesaria. La única configuración necesaria es la integración de la cuenta principal con el marketplace externo. En el momento en que esto se hace, los inventarios de todas las cuentas franquicia vinculadas a la principal también serán enviadas al marketplace. Esta es una nueva feature de las cuentas franquicia, que ya está activa para facilitar su vida a la hora de integrar su operación con marketplaces.
 
-<div class="alert alert-warning">
-<strong>La integración automática del inventario de las cuentas franquicia sólo está disponible por el momento cuando el marketplace no es VTEX</strong>.
-</div>
+>⚠️ **La integración automática del inventario de las cuentas franquicia sólo está disponible por el momento cuando el marketplace no es VTEX**.
 
 ## Que ha cambiado
 
@@ -41,11 +39,9 @@ El Multilevel Omnichannel Inventory fue lanzado trayendo un nuevo aliado para op
 
 Para obtener más información acerca del Multilevel Omnichannel Inventory y los cambios en las APIs del Checkout, acceda a [este artículo del Help](https://help.vtex.com/es/business-guides/ofrezca-los-productos-de-sus-tiendas-fisicas-en-marketplaces-externos--6s64bV8Dqb5QN6sqIfPzcA).
 
-<div class="alert alert-danger">
-<body>
-  <li>El término Marketplace Recursivo fue sustituido por <b>Multilevel Omnichannel Inventory.</b></li>
-<li>Esta funcionalidad no permite <a href="https://help.vtex.com/es/tutorial/vea-como-utilizar-change-seller--5TBAwO2kOAMw44uyaaQMQO">cambiar de seller.</a></li>
-<li>Esta solución se destina a la integración con marketplaces externos, no con marketplaces que ya tienen una <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-en-vtex--tutorials_402">integración nativa VTEX</a>.</li> 
-<li>Lee el artículo <a href="https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> para conocer en detalle las restricciones de uso.</li>
-   </body>
-</div>
+>❗ <body>
+>   <li>El término Marketplace Recursivo fue sustituido por **Multilevel Omnichannel Inventory.**</li>
+> <li>Esta funcionalidad no permite [cambiar de seller.](https://help.vtex.com/es/tutorial/vea-como-utilizar-change-seller--5TBAwO2kOAMw44uyaaQMQO)</li>
+> <li>Esta solución se destina a la integración con marketplaces externos, no con marketplaces que ya tienen una [integración nativa VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-en-vtex--tutorials_402).</li> 
+> <li>Lee el artículo [Multilevel Omnichannel Inventory](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) para conocer en detalle las restricciones de uso.</li>
+>    </body>
diff --git a/docs/announcements/es/old-versions-of-the-vtex-id-script-will-be-deprecated.md b/docs/announcements/es/old-versions-of-the-vtex-id-script-will-be-deprecated.md
index 822fedf0a..0e0fa66d5 100644
--- a/docs/announcements/es/old-versions-of-the-vtex-id-script-will-be-deprecated.md
+++ b/docs/announcements/es/old-versions-of-the-vtex-id-script-will-be-deprecated.md
@@ -27,9 +27,9 @@ Para que este cambio ocurra, el script de VTEX ID debe llamarse desde el siguien
 
 Este nuevo método trae una serie de ventajas: aún más agilidad en las mejoras del script, garantía de que su tienda está usando la última versión y el fin de la necesidad de cambiar el endpoint después de una actualización.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong><br>
-No recomendamos el uso del link con la versión hard-coded, porque pronto vamos a suspender el soporte a ese modo de importación del script.
-</div>
+>⚠️ **Atención:**
+>
+> 
+> No recomendamos el uso del link con la versión hard-coded, porque pronto vamos a suspender el soporte a ese modo de importación del script.
 
 Como estos cambios afectan directamente el acceso del cliente a su tienda, le recomendamos que no espere el plazo final: cuanto antes empezar a utilizar el nuevo método de llamada del script de VTEX ID, mejor.
diff --git a/docs/announcements/es/on-vtex-png-to-webp-conversion-is-now-lossless.md b/docs/announcements/es/on-vtex-png-to-webp-conversion-is-now-lossless.md
index 8a1c2a024..404dbc80f 100644
--- a/docs/announcements/es/on-vtex-png-to-webp-conversion-is-now-lossless.md
+++ b/docs/announcements/es/on-vtex-png-to-webp-conversion-is-now-lossless.md
@@ -19,8 +19,6 @@ Las tiendas VTEX ya contaban con compresión automática de imágenes para el fo
 
 Esta conversión sólo ocurre cuando su tienda es accedida por un navegador compatible con el formato (por ejemplo, Google Chrome). En navegadores que no reconocen el WebP, las imágenes siguen siendo renderizadas en sus formatos originales. Recordamos también que la compresión automática no cambia el archivo que subió en el CMS, pero sólo la forma en que se representa este archivo en la pantalla de su usuario.
 
-<div class="alert alert-warning">
-La compresión <strong>sin pérdidas</strong> es aplicable sólo a los archivos <strong>PNG</strong>. Los archivos <strong>JPG</strong> continúan siendo comprimidos por el proceso <strong>lossy</strong> (que disminuye el tamaño de la imagen para aumentar la velocidad de carga de la página). 
-</div>
+>⚠️ La compresión **sin pérdidas** es aplicable sólo a los archivos **PNG**. Los archivos **JPG** continúan siendo comprimidos por el proceso **lossy** (que disminuye el tamaño de la imagen para aumentar la velocidad de carga de la página).
 
 Este cambio se ha desarrollado para satisfacer a los usuarios que realmente necesitan mantener una calidad de imagen más alta, incluso después de la conversión al formato WebP. Para condiciones normales de uso, los archivos _.jpg_ siguen siendo la solución más indicada.
diff --git a/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md b/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md
index 71166d43f..02dddad39 100644
--- a/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md
+++ b/docs/announcements/es/onboarding-guide-your-complete-journey-at-vtex.md
@@ -33,9 +33,7 @@ La **Guía de onboarding** se compone de 3 series:
 * [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS)
 * [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-<div class="alert alert-info"> 
-Las series presentan contenidos complementarios, pero son independientes entre sí, lo que significa que se puede explorar el contenido libremente y sin necesidad de seguir una secuencia.
-</div>
+>ℹ️ Las series presentan contenidos complementarios, pero son independientes entre sí, lo que significa que se puede explorar el contenido libremente y sin necesidad de seguir una secuencia.
 
 Nuestra meta es asegurarnos de que tanto clientes como partners, así como todo el ecosistema de VTEX, puedan sacarle el máximo partido a la **Guía de onboarding**. Con este objetivo de garantizar la pertinencia del material para una amplia gama de negocios, hemos cubierto una jornada completa y abarcadora. 
 
diff --git a/docs/announcements/es/order-management-module-feed-v1-and-v2-discontinuation.md b/docs/announcements/es/order-management-module-feed-v1-and-v2-discontinuation.md
index a8c2b902f..2d560c0ba 100644
--- a/docs/announcements/es/order-management-module-feed-v1-and-v2-discontinuation.md
+++ b/docs/announcements/es/order-management-module-feed-v1-and-v2-discontinuation.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'El Feed v1 y v2 del módulo de Gestión de Pedidos'
 ---
 
-<div class="alert alert-warning">
-A partir del 25 de julio de 2019, se descontinuará el Feed v1 y v2 del módulo de Gestión de Pedidos. Esto significa que, después de esta fecha, solo será posible utilizar el Feed v3.
-</div>
+>⚠️ A partir del 25 de julio de 2019, se descontinuará el Feed v1 y v2 del módulo de Gestión de Pedidos. Esto significa que, después de esta fecha, solo será posible utilizar el Feed v3.
 
 ## ¿Por qué VTEX está eliminando las versiones antiguas?
 
diff --git a/docs/announcements/es/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md b/docs/announcements/es/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
index 224636d17..eee00c996 100644
--- a/docs/announcements/es/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
+++ b/docs/announcements/es/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
@@ -38,9 +38,7 @@ Actualmente, todas las tiendas VTEX ya tienen el nuevo aplicativo instalado en u
 
 Por añadir nuevos elementos visuales,  __el nuevo My Account demanda la revisión de la página junto a la agencia responsable por su personalización__.
 
-<div class="alert alert-danger">
-<strong>VTEX migrará masivamente el nuevo My Account en el día 3 de julio de 2019.</strong> Por lo tanto, es importante revisar las personalizaciones de la página desde ahora.
-</div>
+>❗ **VTEX migrará masivamente el nuevo My Account en el día 3 de julio de 2019.** Por lo tanto, es importante revisar las personalizaciones de la página desde ahora.
 
 Para saber más sobre el nuevo My Account, acceda a nuestros artículos sobre su __[configuración](https://help.vtex.com/es/tutorial/configuración-de-my-account--23Ayv5D6b86UBnYfoXqZL1)__ y __[funcionamiento](https://help.vtex.com/es/tutorial/como-funciona-el-my-account--2BQ3GiqhqGJTXsWVuio3Xh)__.
 
diff --git a/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
index fe21df5cf..9be07bd26 100644
--- a/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
+++ b/docs/announcements/es/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -65,17 +65,13 @@ Tu tienda utiliza reCAPTCHA en el Checkout y está preparada para exhibirlo corr
 
 Si tu equipo de desarrolladores identifica que tu integración requiere algún tipo de atención, deben seguir las instrucciones proporcionadas en el artículo [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations).
 
-<div class="alert alert-warning">
-Si está implementando reCAPTCHA en una aplicación móvil nativa, use reCAPTCHA v3. De lo contrario, use reCAPTCHA v2.
-</div>
+>⚠️ Si está implementando reCAPTCHA en una aplicación móvil nativa, use reCAPTCHA v3. De lo contrario, use reCAPTCHA v2.
 
 Al utilizar el `recaptchaKey` que devolvió el Checkout, el widget reCAPTCHA debe ser renderizado en la interfaz de usuario de tu aplicación móvil/entorno de tienda headless (o similar) como se describe en el artículo de [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display?hl=es-419) o [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3?hl=es-419) proporcionado por Google.
 
 Después de que el comprador resuelva el reCAPTCHA, su respuesta (`recaptchaToken`) se debe enviar a la API de Checkout para completar la compra, tal y como se describe en la sección *Final validation* del artículo [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#final-validation). En este momento, la API de Checkout [verificará la respuesta del usuario](https://developers.google.com/recaptcha/docs/verify?hl=es-419) utilizando el token proporcionado.
 
-<div class="alert alert-danger">
-Todas las integraciones que utilicen la API de Checkout para realizar pedidos deben revisarse y ajustarse antes del 1 de septiembre de 2023. Las aplicaciones que no tengan la capacidad de mostrar el widget reCAPTCHA y verificar la respuesta del usuario no podrán realizar pedidos a partir de esta fecha.
-</div>
+>❗ Todas las integraciones que utilicen la API de Checkout para realizar pedidos deben revisarse y ajustarse antes del 1 de septiembre de 2023. Las aplicaciones que no tengan la capacidad de mostrar el widget reCAPTCHA y verificar la respuesta del usuario no podrán realizar pedidos a partir de esta fecha.
 
 ## Más información
 
diff --git a/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
index 40037d7fd..e93b0321f 100644
--- a/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
@@ -25,10 +25,14 @@ A partir de __31 de marzo__, los requests con paginación en la API de búsqueda
 
 Este cambio ya se ha implementado en la API, pero hasta la fecha límite, todavía será posible realizar el request de las dos formas. El header `resources` del response no se verá afectado y seguirá funcionando.
 
-<div class="alert alert-warning">
-<b>Importante:</b><br>
-- Para funcionar, los parámetros <b>_from</b> y <b>_to</b> no deben tener una diferencia mayor que <b>50</b>. Esto hará que se muestren como máximo 50 resultados de búsqueda a la vez.<br><br>
-- También hay un límite de 2500 elementos para una búsqueda. Por lo tanto, usted no puede utilizar un valor mayor que 2500 al parámetro <b>_to</b>.
-</div>
+>⚠️ **Importante:**
+>
+> 
+> - Para funcionar, los parámetros **_from** y **_to** no deben tener una diferencia mayor que **50**. Esto hará que se muestren como máximo 50 resultados de búsqueda a la vez.
+>
+> 
+>
+> 
+> - También hay un límite de 2500 elementos para una búsqueda. Por lo tanto, usted no puede utilizar un valor mayor que 2500 al parámetro **_to**.
 
 Para saber todos los detalles del funcionamiento de los requests de paginación en la API de búsqueda, acceda a este [documento](https://developers.vtex.com/docs/api-reference/search-api).
diff --git a/docs/announcements/es/search-resolve-hides-number-product-stock.md b/docs/announcements/es/search-resolve-hides-number-product-stock.md
index a28e9e777..6efe86557 100644
--- a/docs/announcements/es/search-resolve-hides-number-product-stock.md
+++ b/docs/announcements/es/search-resolve-hides-number-product-stock.md
@@ -35,7 +35,5 @@ Esta actualización es automática, no se requiere ninguna acción.
 
 Si utilizas estos datos en tu tienda (para indicar que un producto tiene pocas unidades en _stock_, por ejemplo) debes contactar con [nuestro equipo de soporte](https://support.vtex.com/hc/es-419/requests) para seguir mostrando esta información.
 
-<div class="alert alert-warning">
-  <p>Es importante señalar que, si la tienda decide mostrar la cantidad de productos en stock, esta información será pública y se podrá acceder a ella mediante <a href="https://github.com/vtex-apps/search-graphql">VTEX Search GraphQL</a>.</p>
-</div>
+>⚠️ Es importante señalar que, si la tienda decide mostrar la cantidad de productos en stock, esta información será pública y se podrá acceder a ella mediante [VTEX Search GraphQL](https://github.com/vtex-apps/search-graphql).
 
diff --git a/docs/announcements/es/security-improvements-to-checkout-cookies.md b/docs/announcements/es/security-improvements-to-checkout-cookies.md
index 2b0fc6f69..3774eba89 100644
--- a/docs/announcements/es/security-improvements-to-checkout-cookies.md
+++ b/docs/announcements/es/security-improvements-to-checkout-cookies.md
@@ -57,6 +57,4 @@ Si encuentra algún error al realizar pruebas operativas en un ambiente Beta, ve
 
 Después de verificar la configuración de la tienda, vuelva a ejecutar la prueba en ambiente Beta.
 
-<div class="alert alert-warning">
-A partir del 13 de Febrero de 2023, es posible que las tiendas que no estén configuradas correctamente no puedan operar Checkout correctamente.
-</div>
+>⚠️ A partir del 13 de Febrero de 2023, es posible que las tiendas que no estén configuradas correctamente no puedan operar Checkout correctamente.
diff --git a/docs/announcements/es/service-worker-files-can-now-operate-at-full-capacity.md b/docs/announcements/es/service-worker-files-can-now-operate-at-full-capacity.md
index d173d9560..6540ce74b 100644
--- a/docs/announcements/es/service-worker-files-can-now-operate-at-full-capacity.md
+++ b/docs/announcements/es/service-worker-files-can-now-operate-at-full-capacity.md
@@ -19,9 +19,9 @@ El __Service Worker__ ahora puede interceptar todas los requests de su tienda VT
 
 Esta actualización de permisos del __Service Worker__ amplía las posibilidades de su tienda, siendo la mayor de ellas poder operar como PWA (Progressive Web App). Esta solución permite al usuario acceder a un website como lo hace con una aplicación, pero sin tener que descargar nada. Sólo necesita guardar el sitio en la pantalla de inicio del smartphone para navegar, sin tener que estar conectado a Internet para ver el contenido.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong><br>
-La plataforma VTEX <strong>no</strong> posee features nativas para transformar su tienda en PWA. Sólo ofrece las condiciones para que esta implementación se haga.
-</div>
+>⚠️ **Atención:**
+>
+> 
+> La plataforma VTEX **no** posee features nativas para transformar su tienda en PWA. Sólo ofrece las condiciones para que esta implementación se haga.
 
 Para saber cómo instalar __Service Worker__ en su tienda, lea [este artículo del Help](/es/tutorial/como-instalar-un-service-worker).
diff --git a/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md b/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md
index 6b323a14f..ed796fae0 100644
--- a/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md
+++ b/docs/announcements/es/site-editor-and-media-new-authorization-requirement.md
@@ -29,7 +29,5 @@ Este cambio tiene como objetivo mejorar la seguridad y simplificar el acceso del
 ## ¿Qué se necesita hacer?
 Asegúrate de que los usuarios de Site Editor y Multimedia tienen sus roles asociados al recurso `CMS GraphQL API`, ya sea [creando un nuevo rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) o editando uno existente.
 
-<div class="alert alert-warning">
-  <p>Para gestionar usuarios y roles, tu rol de usuario debe estar asociado al recurso <code>Save access profile</code> del producto <bold>License Manager</bold>. Por ejemplo, <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> es un rol predefinido que tiene asociado el recurso <code>Save access profile</code>.</p>
-</div>
+>⚠️ Para gestionar usuarios y roles, tu rol de usuario debe estar asociado al recurso `Save access profile` del producto <bold>License Manager</bold>. Por ejemplo, [User Administrator - RESTRICTED](https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted) es un rol predefinido que tiene asociado el recurso `Save access profile`.
 
diff --git a/docs/announcements/es/smartcheckout-tm-new-version-already-available-for-all-stores.md b/docs/announcements/es/smartcheckout-tm-new-version-already-available-for-all-stores.md
index ce57fbe0b..5992a2931 100644
--- a/docs/announcements/es/smartcheckout-tm-new-version-already-available-for-all-stores.md
+++ b/docs/announcements/es/smartcheckout-tm-new-version-already-available-for-all-stores.md
@@ -28,9 +28,7 @@ Vea más cambios importantes:
 - Data Layer actualizado con información para utilizar en Google Enhanced Ecommerce.
 - Posibilidad de edición de los archivos `checkout5-custom.js` y` orderplaced2-custom.js` para personalizar JavaScript del checkout y de la pantalla de pedido finalizado, respectivamente.
 
-<div class="alert alert-warning">
-Pero recuerde: VTEX <strong>no recomienda</strong> el cambio de los archivos de JavaScript, porque esto puede causar daños en la seguridad a su checkout. Por eso, no nos responsabilizamos por cualquier problema generado en la edición de ese código.
-</div>
+>⚠️ Pero recuerde: VTEX **no recomienda** el cambio de los archivos de JavaScript, porque esto puede causar daños en la seguridad a su checkout. Por eso, no nos responsabilizamos por cualquier problema generado en la edición de ese código.
 
 Para conocer todos los detalles de la nueva versión de SmartCheckout™, vea el [artículo de VTEX Help](/es/tutorial/cambio-la-nueva-version-de-smart-checkout)
 
diff --git a/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md b/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md
index 330bc8eed..054f64fbf 100644
--- a/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md
+++ b/docs/announcements/es/the-items-field-will-be-removed-from-the-list-orders-api.md
@@ -23,9 +23,7 @@ Request de la API de List Orders: <code>http://{{accountName}}.{{environment}}.c
 
 Si su tienda utiliza la API de List Orders y en el mapeo de su integración se espera recibir el campo `items`, su equipo de desarrollo necesita retirarlo del mapeo de la integración.
 
-<div class="alert alert-warning">
-El campo <code>items</code> de la API de List Orders ya está <strong>obsoleto</strong> desde hace bastante tiempo. Él no tiene ninguna utilidad actualmente, y por eso su tienda no debería considerarlo en sus integraciones. Para recoger artículos de pedidos, usted debe usar la <a href="http://help.vtex.com/es/tutorial/como-funciona-el-feed-del-oms">API del Feed</a>.
-</div>
+>⚠️ El campo `items` de la API de List Orders ya está **obsoleto** desde hace bastante tiempo. Él no tiene ninguna utilidad actualmente, y por eso su tienda no debería considerarlo en sus integraciones. Para recoger artículos de pedidos, usted debe usar la [API del Feed](http://help.vtex.com/es/tutorial/como-funciona-el-feed-del-oms).
 
 Es importante recordar que la API de List Orders sigue funcionando normalmente. Sólo se eliminará el campo `items`.
 
@@ -35,13 +33,9 @@ La retirada de este campo aumentará considerablemente la estabilidad y el rendi
 
 Por eso, es crucial retirarlo de la integración.
 
-<div class="alert alert-info">
-<strong>Atención:</strong> este cambio sólo impacta las integraciones que dependen de la entrega del campo `items` por la API de List Orders.
-</div>
+>ℹ️ **Atención:** este cambio sólo impacta las integraciones que dependen de la entrega del campo `items` por la API de List Orders.
 
-<div class="alert alert-info">
-Este cambio <strong>no</strong> afecta a la API de Get Orders. En ella, el campo <code>items</code> sigue existiendo y se actualiza normalmente.
-</div>
+>ℹ️ Este cambio **no** afecta a la API de Get Orders. En ella, el campo `items` sigue existiendo y se actualiza normalmente.
 
 <div class="alert">
 Request de la API de Get Order: <code>http://{{accountName}}.{{environment}}.com.br/api/oms/pvt/orders/{{orderId}}</code>
diff --git a/docs/announcements/es/the-new-admin-is-already-being-deployed-to-all-stores.md b/docs/announcements/es/the-new-admin-is-already-being-deployed-to-all-stores.md
index 1d9944c3d..d2c71000e 100644
--- a/docs/announcements/es/the-new-admin-is-already-being-deployed-to-all-stores.md
+++ b/docs/announcements/es/the-new-admin-is-already-being-deployed-to-all-stores.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Hasta 7 de mayo, todas las tiendas VTEX van a operar con el nuevo Admin.'
 ---
 
-<div class="alert alert-warning">
-La nueva fecha de liberación del nuevo admin será en el 7 de mayo de 2018 (lunes).
-</div>
+>⚠️ La nueva fecha de liberación del nuevo admin será en el 7 de mayo de 2018 (lunes).
 
 El nuevo ambiente administrativo de VTEX está listo para ser utilizado por todas las tiendas. Después de pasar un tiempo en beta, pudiendo ser probado por una parte de nuestros clientes, el __nuevo Admin__ se ha mejorado y va a empezar a ser liberado poco a poco, en un proceso que comienza esta semana y va hasta 7 de mayo.
 
@@ -29,6 +27,4 @@ Pero quédese tranquilo: esa migración no va a impactar su rutina diaria, ya qu
 
 Usted puede acceder al __nuevo Admin__ usando la url `https://{AccountName}.myvtex.com/admin`, reemplazando _{AccountName}_ por el account name de su tienda.
 
-<div class="alert alert-warning">
-Los módulos de legado (Catálogo, Master Data y CMS) continúan dirigiéndole a ambientes externos.
-</div>
+>⚠️ Los módulos de legado (Catálogo, Master Data y CMS) continúan dirigiéndole a ambientes externos.
diff --git a/docs/announcements/es/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md b/docs/announcements/es/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
index 4bbd3bd34..e5eadf433 100644
--- a/docs/announcements/es/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
+++ b/docs/announcements/es/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
@@ -31,6 +31,4 @@ El comportamiento del modulo permanece igual desde el ultimo cambio: sí el filt
 ## Cómo exportar más de 5.000 pedidos
 Usted puede continuar exportando mas de 5000 pedidos usando las APIs de gerenciamiento de pedidos (antiguo OMS): [Get Order](https://developers.vtex.com/reference/orders#getorder) y [Get Feed Order Status](https://developers.vtex.com/reference/note).
 
-<div class="alert alert-warning">
-<strong>Por favor recuerde:</strong> para que funcione, es necesario que usted <strong>cree un range de fecha/hora que incluya no mas de 5000 pedidos</strong>. Con el range definido y el limite respetado, usted va a poder usar la API cuantas veces considere necesario.
-</div>
+>⚠️ **Por favor recuerde:** para que funcione, es necesario que usted **cree un range de fecha/hora que incluya no mas de 5000 pedidos**. Con el range definido y el limite respetado, usted va a poder usar la API cuantas veces considere necesario.
diff --git a/docs/announcements/es/the-offer-management-module-will-be-discontinued.md b/docs/announcements/es/the-offer-management-module-will-be-discontinued.md
index 3af612e5a..4a4d71583 100644
--- a/docs/announcements/es/the-offer-management-module-will-be-discontinued.md
+++ b/docs/announcements/es/the-offer-management-module-will-be-discontinued.md
@@ -28,7 +28,5 @@ Las funcionalidades de [Moderación](https://help.vtex.com/es/tutorial/gerenciam
 
 Esta actualización es automática y no se requiere ninguna acción por tu parte. El módulo dejará de estar disponible para todos los Admin VTEX a partir de la fecha anteriormente indicada.
 
-<div class="alert alert-info">
-Pronto pondremos a disposición un reemplazo del módulo Gestión de anuncios; accede a las novedades en la página <a href="https://developers.vtex.com/updates/release-notes">Release notes, dentro del Developer portal</a> y <a href="https://help.vtex.com/es/announcements">en la pestaña Noticias de nuestro Help Center</a>.
-</div>
+>ℹ️ Pronto pondremos a disposición un reemplazo del módulo Gestión de anuncios; accede a las novedades en la página [Release notes, dentro del Developer portal](https://developers.vtex.com/updates/release-notes) y [en la pestaña Noticias de nuestro Help Center](https://help.vtex.com/es/announcements).
 
diff --git a/docs/announcements/es/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md b/docs/announcements/es/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
index 7d57673b4..7eb7c234a 100644
--- a/docs/announcements/es/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
+++ b/docs/announcements/es/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
@@ -59,9 +59,7 @@ Si deseas que algún usuario de tu tienda pueda realizar las acciones asociadas
 
 Las claves de aplicación con el rol de usuario **Owner (Admin Super)** no recibirán el rol **User Administrator - RESTRICTED** automáticamente. Por lo tanto, si deseas que alguna clave de aplicación pueda realizar las acciones asociadas al recurso **Save user** antes mencionadas, debes asegurarte de que la clave tenga el rol **User Administrator - RESTRICTED** o crear un [rol de usuario personalizado](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#tipos-de-roles) que incluya el recurso **Save user**.
 
-<div class="alert alert-warning">
-Ten en cuenta que con los cambios descritos anteriormente, las claves de aplicación dejarán de tener el recurso <b>Save user</b> y será necesario que un usuario con este recurso se lo asigne, de ser necesario.
-</div>
+>⚠️ Ten en cuenta que con los cambios descritos anteriormente, las claves de aplicación dejarán de tener el recurso **Save user** y será necesario que un usuario con este recurso se lo asigne, de ser necesario.
 
 ## ¿Cómo proteger las llaves de tu tienda?
 
diff --git a/docs/announcements/es/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md b/docs/announcements/es/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
index b44212ab9..0296bcd5d 100644
--- a/docs/announcements/es/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
+++ b/docs/announcements/es/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisES: 'El término ‘Access Profile’ ha sido sustituido por el término ‘Role’ para reflejar mejor el concepto al que se refiere.'
 ---
 
-<div class="alert alert-warning">
-Este cambio se refiere a un término utilizado únicamente en la lengua inglesa. Consulte este anuncio en inglés para obtener más información.
-</div>
+>⚠️ Este cambio se refiere a un término utilizado únicamente en la lengua inglesa. Consulte este anuncio en inglés para obtener más información.
diff --git a/docs/announcements/es/this-new-api-helps-marketplaces-avoid-losing-sales.md b/docs/announcements/es/this-new-api-helps-marketplaces-avoid-losing-sales.md
index 6022e0fb0..64ec7d4e1 100644
--- a/docs/announcements/es/this-new-api-helps-marketplaces-avoid-losing-sales.md
+++ b/docs/announcements/es/this-new-api-helps-marketplaces-avoid-losing-sales.md
@@ -19,10 +19,10 @@ Ya está disponible en stable una API que va a traer aún más autonomía para l
 
 Con este nuevo status, los marketplaces pueden recuperar ventas que se perderían en caso de que un seller cancele el pedido de un cliente. Ahora, tendrán tiempo para encontrar otro seller con el inventario necesario para satisfacer el pedido y así asegurar la conversión.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong><br> 
-El nuevo status sólo estará disponible cuando <strong>Marketplace</strong> y <strong>Seller</strong> son VTEX. Y, si no hay seller VTEX con inventario disponible, la compra del cliente no pasa por el nuevo status y se cancela automáticamente. 
-</div>
+>⚠️ **Atención:**
+>
+>  
+> El nuevo status sólo estará disponible cuando **Marketplace** y **Seller** son VTEX. Y, si no hay seller VTEX con inventario disponible, la compra del cliente no pasa por el nuevo status y se cancela automáticamente.
 
 El Change Seller también permite que el marketplace tenga más control sobre la calidad de la entrega de los productos, ya que también será posible cambiar de seller cuando el pedido esté con el status "__Pagamento pendiente" y "__Aguardando autorización__". Otro caso de uso es para tiendas que poseen franquiciados (sellers white label): ahora, ellas también van a poder cambiar el franquiciado responsable de un pedido.
 
diff --git a/docs/announcements/es/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md b/docs/announcements/es/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
index 2d2bd6bdb..99f59c6ad 100644
--- a/docs/announcements/es/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
+++ b/docs/announcements/es/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
@@ -19,9 +19,7 @@ El día 13/06/19, [anunciamos la descontinuación de las APIs de Feed V1 y V2](/
 
 __Cambiamos la fecha final de migración y las tiendas que aún no se adaptaron a la nueva versión tienen hasta el día 12/08 para adecuar su integración__. Después de esta fecha, no será más posible consumir datos de pedidos utilizando las versiones anteriores de esta API, impactando su proceso de entrega de pedidos.
 
-<div class="alert alert-info">
-Las tiendas que ya estén usando la V3 de la API de Feed no necesitan realizar ninguna acción.
-</div>
+>ℹ️ Las tiendas que ya estén usando la V3 de la API de Feed no necesitan realizar ninguna acción.
 
 Es muy importante que esta migración se realice lo antes posible para que su operación no esté en riesgo. Siga las instrucciones a continuación y solicite al responsable por su integración que ejecute los cambios necesarios.
 
diff --git a/docs/announcements/es/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md b/docs/announcements/es/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
index fee699f0c..2c826d240 100644
--- a/docs/announcements/es/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
+++ b/docs/announcements/es/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
@@ -15,21 +15,17 @@ announcementImageID: ''
 announcementSynopsisES: 'La V2 trae una serie de mejoras y quita algunos campos y rutas que ya estaban obsoletas.'
 ---
 
-<div class="alert alert-danger">
-La migración para la v2 de la API de Checkout y Fulfillment ya fue finalizada en <strong>23/05/2018</strong>
-</div>
+>❗ La migración para la v2 de la API de Checkout y Fulfillment ya fue finalizada en **23/05/2018**
 
-<div class="alert alert-warning">
-El plazo anterior se modifica de <strong>21/05</strong> a <strong>23/05</strong> (2 días) debido a la necesidad de pruebas adicionales.
-</div>
+>⚠️ El plazo anterior se modifica de **21/05** a **23/05** (2 días) debido a la necesidad de pruebas adicionales.
 
 Ya está en beta la versión 2 de la API de Checkout y Fulfillment. Y, a partir de __23 de mayo__, se aplicará a todas las tiendas. La V2 trae una serie de mejoras con respecto a la versión anterior y quita algunos campos y rutas que ya estaban obsoletas.
 
-<div class="alert alert-warning">
-<Strong>Atención</strong><br>
-Recomendamos que usted haga todas las pruebas para evaluar los impactos y adaptar sus integraciones y personalizaciones antes del plazo final.
-Así, cuando realizamos la migración a la nueva versión de la API, su tienda tendrá una transición tranquila.
-</div>
+>⚠️ <Strong>Atención</strong>
+>
+> 
+> Recomendamos que usted haga todas las pruebas para evaluar los impactos y adaptar sus integraciones y personalizaciones antes del plazo final.
+> Así, cuando realizamos la migración a la nueva versión de la API, su tienda tendrá una transición tranquila.
 
 Compruebe abajo todo lo que cambia con la nueva versión de la API de Checkout y Fulfillment (y lo que está en beta o en stable):
 
diff --git a/docs/announcements/es/vtex-announces-its-integration-with-amazon.md b/docs/announcements/es/vtex-announces-its-integration-with-amazon.md
index 123e37329..15a384547 100644
--- a/docs/announcements/es/vtex-announces-its-integration-with-amazon.md
+++ b/docs/announcements/es/vtex-announces-its-integration-with-amazon.md
@@ -19,6 +19,4 @@ VTEX anuncia su nueva integración con Amazon. Ahora nuestros clientes ya pueden
 
 En un primer momento, la integración estará disponible para las categorías Electrónicos, Libros y Games. Para saber más detalles sobre la integración, vea nuestro [tutorial](https://help.vtex.com/es/tracks/configurar-la-integracion-de-amazon--6sgd4Pagy3wNsWKBvmIFrP "tutorial").
 
-<div class="alert alert-warning">
-Esta integración está disponible para Brasil y los Estados Unidos
-</div>
+>⚠️ Esta integración está disponible para Brasil y los Estados Unidos
diff --git a/docs/announcements/es/vtex-login-now-features-recaptcha.md b/docs/announcements/es/vtex-login-now-features-recaptcha.md
index 00f8d14d3..1618b5ff5 100644
--- a/docs/announcements/es/vtex-login-now-features-recaptcha.md
+++ b/docs/announcements/es/vtex-login-now-features-recaptcha.md
@@ -25,6 +25,6 @@ Esto significa que la solicitud de confirmación puede o no aparecer, dependiend
 
 Con este cambio, VTEX deja de impedir el acceso de un usuario después de 3 intentos incorrectos, ya que la seguridad queda garantizada por el reCAPTCHA.
 
-<div class="alert alert-info">Actualmente, usamos reCAPTCHA solo en el flujo de login del admin.</div>
+>ℹ️ Actualmente, usamos reCAPTCHA solo en el flujo de login del admin.
 
-<div class="alert alert-warning">Debido a este cambio, <a href="https://help.vtex.com/es/announcements/integrations-with-vtex-apis-now-need-token-authentication--7AdnXDH7AkYmuEUmmis8Es">ya no se permite el uso de e-mail y contraseña para las integraciones</a>.</div>
+>⚠️ Debido a este cambio, [ya no se permite el uso de e-mail y contraseña para las integraciones](https://help.vtex.com/es/announcements/integrations-with-vtex-apis-now-need-token-authentication--7AdnXDH7AkYmuEUmmis8Es).
diff --git a/docs/announcements/es/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md b/docs/announcements/es/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
index 85ade008c..e926fcc6a 100644
--- a/docs/announcements/es/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
+++ b/docs/announcements/es/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
@@ -21,9 +21,7 @@ Su tienda VTEX no depende más de las integraciones externas para vender en la M
 ## Cómo fue el cambio
 Funcionando desde octubre de 2018, nuestra integración con la Magazine Luiza estaba disponible sólo para tiendas que todavía no vendían en el marketplace. En diciembre, iniciamos la migración de las tiendas que trabajaban con integraciones externas y el proceso se concluyó con éxito.
 
-<div class="alert alert-info">
-La integración con la Magazine Luiza ocurre a través del sistema de Integra Commerce, que intermedia las informaciones enviadas por VTEX y repasa al marketplace.
-</div>
+>ℹ️ La integración con la Magazine Luiza ocurre a través del sistema de Integra Commerce, que intermedia las informaciones enviadas por VTEX y repasa al marketplace.
 
 
 ## Integración completa, estable y con todo el soporte VTEX
diff --git a/docs/announcements/es/web-service-methods-will-be-deprecated.md b/docs/announcements/es/web-service-methods-will-be-deprecated.md
index ef500a0f3..e468eed45 100644
--- a/docs/announcements/es/web-service-methods-will-be-deprecated.md
+++ b/docs/announcements/es/web-service-methods-will-be-deprecated.md
@@ -17,9 +17,7 @@ announcementSynopsisES: 'A partir del 28/02/18, el uso de Web Service se descont
 
 A partir del día __28 de febrero__, vamos a descontinuar el uso de Web Service para integraciones con VTEX, __a excepción de los métodos del Catálogo__.
 
-<div class="alert alert-warning">
-El Web Service continuará funcionando para el Catálogo, mientras trabajamos en el desarrollo de las API REST de este servicio. Se le informará una vez que se haya establecido un calendario de migración.
-</div>
+>⚠️ El Web Service continuará funcionando para el Catálogo, mientras trabajamos en el desarrollo de las API REST de este servicio. Se le informará una vez que se haya establecido un calendario de migración.
 
 Si su tienda todavía usa alguno de estos métodos, sustitúyalos por integraciones a través de API. En caso contrario, a partir del 28 de febrero estas integraciones dejarán de funcionar.
 
diff --git a/docs/announcements/es/wordpress-a-powerful-marketing-tool-for-your-store.md b/docs/announcements/es/wordpress-a-powerful-marketing-tool-for-your-store.md
index 2bc04c5a3..10377ba80 100644
--- a/docs/announcements/es/wordpress-a-powerful-marketing-tool-for-your-store.md
+++ b/docs/announcements/es/wordpress-a-powerful-marketing-tool-for-your-store.md
@@ -31,6 +31,4 @@ Integrar su _blog_/sitio web en la tienda equivale a utilizar una poderosa herra
 
 Instale la aplicación desde la [App Store de VTEX](https://apps.vtex.com/vtex-wordpress-integration/p) y siga las instrucciones de esta [documentación](https://developers.vtex.com/vtex-developer-docs/docs/vtex-wordpress-integration) para configurar la integración.
 
-<div class="alert alert-info">
-Para utilizar esta aplicación es necesario tener un sitio web/blog desarrollado en WordPress.
-</div>
+>ℹ️ Para utilizar esta aplicación es necesario tener un sitio web/blog desarrollado en WordPress.
diff --git a/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 55303f276..271ed6020 100644
--- a/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/es/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Posibilidad de limitar perfiles de acceso a la pantalla Confiuración'
 ---
 
-<div class="alert alert-warning">
-A partir del 25 de junio de 2019, el usuario que no tenga acceso vinculado al perfil con el producto <code>Checkout</code> no tendrá permiso para editar la pantalla **Configuración** del modulo Gestión de pedidos.
-</div>
+>⚠️ A partir del 25 de junio de 2019, el usuario que no tenga acceso vinculado al perfil con el producto `Checkout` no tendrá permiso para editar la pantalla **Configuración** del modulo Gestión de pedidos.
 
 Con el fin de garantizar una mayor seguridad, creamos la posibilidad de limitar perfiles de acceso en la pantalla **Configuración**, permitiendo que solo algunos usuarios editen las informaciones.
 
diff --git a/docs/announcements/pt/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md b/docs/announcements/pt/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md
index 4947dc2d5..04f5a93b6 100644
--- a/docs/announcements/pt/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md	
+++ b/docs/announcements/pt/ Get-Order-Json-now-delivers-new-variables-in-order-calculations.md	
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Tenha em mãos informações detalhadas sobre o cálculo do frete do pedido'
 ---
 
-<div class="alert alert-warning">
-Por motivos técnicos, o lançamento dessa funcionalidade foi postergado por tempo inderteminado.
-</div>
+>⚠️ Por motivos técnicos, o lançamento dessa funcionalidade foi postergado por tempo inderteminado.
 
 
 A partir de 01 de Abril de 2019, o JSON de pedidos retornará um novo objeto chamado `alternativeTotals`.  Ele aparecerá nos totalizers que ficam dentro do array de `totals`, para as consultas feitas pela API de Get Order.
diff --git a/docs/announcements/pt/adapting-your-stores-front-end-requisites-to-master-data.md b/docs/announcements/pt/adapting-your-stores-front-end-requisites-to-master-data.md
index acfe04fd4..d737f0a42 100644
--- a/docs/announcements/pt/adapting-your-stores-front-end-requisites-to-master-data.md
+++ b/docs/announcements/pt/adapting-your-stores-front-end-requisites-to-master-data.md
@@ -17,8 +17,7 @@ announcementSynopsisPT: ' A VTEX descontinuará o suporte ao CORS do Master Data
 
 Com o principal objetivo de fornecer uma experiência cada vez mais eficiente para você e seus clientes, **a VTEX descontinuará o suporte ao CORS do Master Data.** Siga as instruções deste artigo e evite qualquer falha na operação e na navegação da sua loja.
 
-<div class="alert alert-warning"> A descontinuação estava agendada para setembro de 2019, anteriormente. Porém, em alinhamento com a parceria que temos com nossos clientes e garantindo o mínimo de atrito em suas operações, prorrogamos a data da descontinuação deste recurso para o dia 07 de outubro de 2019. 
-</div>
+>⚠️ A descontinuação estava agendada para setembro de 2019, anteriormente. Porém, em alinhamento com a parceria que temos com nossos clientes e garantindo o mínimo de atrito em suas operações, prorrogamos a data da descontinuação deste recurso para o dia 07 de outubro de 2019.
 
 
 ### O que é CORS?
diff --git a/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md b/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
index b6ba0b616..619b1337c 100644
--- a/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
+++ b/docs/announcements/pt/admin-navigation-will-now-be-restricted-by-user-role.md
@@ -17,9 +17,7 @@ announcementSynopsisPT: 'Usuários verão apenas os itens do menu lateral que t
 
 Os [perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) permitem que as lojas concedam aos usuários acesso apenas a uma seleção de recursos em nossa plataforma. Embora esse recurso fosse suficiente para proteger a integridade e a segurança dos dados da sua conta, qualquer usuário podia ver os itens do menu lateral para seções restritas do Admin. Essas seções não estão mais visíveis. Agora, os usuários conseguem ver apenas os itens liberados para seu perfil de acesso.
 
-<div class="alert alert-info">
-Essa modificação tem baixo impacto nas operações da loja, uma vez que se trata de uma reorganização do menu de navegação à esquerda, e não de alterações nos perfis de acesso individuais.  Além disso, nenhuma configuração anterior será perdida; se seus usuários já tiverem perfis de acesso e permissões predefinidas, estes serão mantidos.
-</div>
+>ℹ️ Essa modificação tem baixo impacto nas operações da loja, uma vez que se trata de uma reorganização do menu de navegação à esquerda, e não de alterações nos perfis de acesso individuais.  Além disso, nenhuma configuração anterior será perdida; se seus usuários já tiverem perfis de acesso e permissões predefinidas, estes serão mantidos.
 
 ## O que mudou?
 Antes, os usuários podiam ver todos os itens do menu lateral do Admin, incluindo seções que eles não tinham permissão para acessar. Por exemplo, um usuário com o [perfil de acesso de operador de call center](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator) não tem acesso ao Master Data, mas essa opção estaria visível em seu menu lateral.
diff --git a/docs/announcements/pt/all-stores-have-until-april-20th-to-activate-the-new-cdn.md b/docs/announcements/pt/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
index f65fcaaa0..6aa5c39cf 100644
--- a/docs/announcements/pt/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
+++ b/docs/announcements/pt/all-stores-have-until-april-20th-to-activate-the-new-cdn.md
@@ -22,11 +22,13 @@ Disponível para todas as lojas desde outubro de 2017, a nova CDN vai passar a s
 __Importante:__ o principal requisito para mudar para a nova CDN é que seu site seja __totalmente disponibilizado em HTTPS__. Você deve ficar atento principalmente às chamadas HTTP do seu site, que devem passar a ser HTTPS para funcionarem na nova CDN. Veja como [ativar HTTPS em todo o site](/pt/tutorial/ativar-https-em-todo-o-site) e atente-se aos requisitos necessários para essa migração.
 
 Portanto, muita atenção:
-<div class="alert alert-warning">
-Você tem até o dia <b>20 de abril</b> para garantir que sua loja:<br>
-- Esteja totalmente disponibilizada em HTTPS.<br>
-- Tenha completado a migração para a nova CDN da VTEX.
-</div>
+>⚠️ Você tem até o dia **20 de abril** para garantir que sua loja:
+>
+> 
+> - Esteja totalmente disponibilizada em HTTPS.
+>
+> 
+> - Tenha completado a migração para a nova CDN da VTEX.
 
 Depois dessa data, as lojas que não tenham feito as mudanças necessárias __podem sofrer indisponibilidades__, como layout quebrado até sua loja ficar *offline*. Por isso, recomendamos que você ative o HTTPS e migre para a nova CDN neste prazo. Isso vai garantir aos seus clientes a melhor experiência.
 
diff --git a/docs/announcements/pt/apply-manual-prices-in-subscription-items.md b/docs/announcements/pt/apply-manual-prices-in-subscription-items.md
index 3ac0df746..0bd15f1ac 100644
--- a/docs/announcements/pt/apply-manual-prices-in-subscription-items.md
+++ b/docs/announcements/pt/apply-manual-prices-in-subscription-items.md
@@ -34,6 +34,4 @@ Esta alteração foi motivada pela demanda dos lojistas de estabelecer preços m
 
 Para habilitar a funcionalidade de Preço Manual para Assinaturas, siga os passos descritos no guia para desenvolvedores [Enabling Manual Prices for Subscriptions v3](https://developers.vtex.com/vtex-rest-api/docs/enabling-manual-prices-for-subscriptions-v3) (Habilitar Preços Manuais para Assinaturas v3).
 
-<div class="alert alert-warning">
-<p>A funcionalidade de Preço Manual está disponível apenas para Assinaturas v3. Se você estiver utilizando uma versão anterior do sistema de Assinaturas, consulte o <a href="https://developers.vtex.com/vtex-rest-api/docs/subscriptions-v3-migration-guide">Subscriptions v3 migration guide</a> (Guia de migração para Assinaturas v3).</p>
-</div>
+>⚠️ A funcionalidade de Preço Manual está disponível apenas para Assinaturas v3. Se você estiver utilizando uma versão anterior do sistema de Assinaturas, consulte o [Subscriptions v3 migration guide](https://developers.vtex.com/vtex-rest-api/docs/subscriptions-v3-migration-guide) (Guia de migração para Assinaturas v3).
diff --git a/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md b/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
index 3b7a3baec..7ad76f6f7 100644
--- a/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
+++ b/docs/announcements/pt/become-an-expert-in-vtex-with-training-day.md
@@ -17,9 +17,7 @@ announcementSynopsisPT: 'Participe de um dia de treinamento intensivo em VTEX co
 
 ![cover fb 01](https://images.ctfassets.net/alneenqid6w5/fj8PzFYRP2yaeAaIiKCW2/e06c967d7129640c493c545ecfc48db8/cover_fb_01.png)
 
-<div class="alert alert-info">
-Um dia inteiro de treinamento em VTEX com os maiores especialistas no assunto.
-</div>
+>ℹ️ Um dia inteiro de treinamento em VTEX com os maiores especialistas no assunto.
 
 Há muito tempo, clientes e parceiros vêm pedindo por um treinamento aprofundado da plataforma. Agora, finalmente, conseguimos atender a esse pedido.
 
diff --git a/docs/announcements/pt/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md b/docs/announcements/pt/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
index eff39b2ec..f103eab86 100644
--- a/docs/announcements/pt/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
+++ b/docs/announcements/pt/benefits-now-consider-condition-of-payment-system-for-more-than-one-trade.md
@@ -25,6 +25,4 @@ Anteriormente, as promoções com condições de meio de pagamento eram aplicada
 
 No cenário atual, os promoções passam a considerar a condição de meio de pagamento por política comercial. Isso significa que uma promoção com filtro de meio de pagamento pode ser aplicada a mais de uma política comercial. Com esta melhoria, o lojista tem maior flexibilidade para configurar suas promoções.
 
-<div class="alert alert-danger">
-É importante ressaltar que esta feature <strong>não é válida</strong> para políticas comerciais de terceiros.
-</div>
+>❗ É importante ressaltar que esta feature **não é válida** para políticas comerciais de terceiros.
diff --git a/docs/announcements/pt/boost-your-marketplace-sales.md b/docs/announcements/pt/boost-your-marketplace-sales.md
index 16e5b0424..59a418c07 100644
--- a/docs/announcements/pt/boost-your-marketplace-sales.md
+++ b/docs/announcements/pt/boost-your-marketplace-sales.md
@@ -35,6 +35,4 @@ Se sua loja possui __integração externa com marketplaces__ (e você deseja usa
 
 Se a sua loja possui __integração com marketplaces certificados__ (usando o Bridge), a flag será acionada automaticamente. Você só vai precisar cumprir as etapas descritas nos passos `2`e `3`.
 
-<div class="alert alert-info">
-Lembre-se de que as integrações de pedido devem ser feitas usando as seguintes APIs <a href="https://developers.vtex.com/reference/orders#getorder">Get Order</a> e <a href="https://developers.vtex.com/reference/feed-v2-deprecated#getfeedorderstatus">Get Feed Order Status</a>.
-</div>
+>ℹ️ Lembre-se de que as integrações de pedido devem ser feitas usando as seguintes APIs [Get Order](https://developers.vtex.com/reference/orders#getorder) e [Get Feed Order Status](https://developers.vtex.com/reference/feed-v2-deprecated#getfeedorderstatus).
diff --git a/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md b/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
index 92df48457..5f6a6209c 100644
--- a/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
+++ b/docs/announcements/pt/build-and-scale-your-fulfillment-operation-with-vtex-pick-and-pack.md
@@ -41,9 +41,7 @@ A solução é composta por:
 - **Last Mile:** os operadores da loja podem gerenciar e instruir os entregadores sobre a coleta e entrega dos pedidos. Isso inclui a otimização de rotas e comprovação de coleta e entrega. Além disso, sua loja pode se integrar facilmente a transportadoras externas ou a um sistema TMS. E ainda, é possível acompanhar o status de seus pedidos em tempo real via URL. 
 - **Aplicativos móveis:** aplicativos para dispositivos móveis desenvolvidos exclusivamente para que os separadores e entregadores possam realizar suas tarefas sem precisar acessar o Admin da loja. Atualmente, os aplicativos estão disponíveis apenas para Android.  
 
-<div class="alert alert-danger"> 
-O <b>VTEX Pick and Pack</b> não é um sistema de faturamento e, por isso, os pedidos devem ser faturados através do OMS da VTEX. Saiba mais em <a href="https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT">Faturar um pedido</a>.
-</div>
+>❗ O **VTEX Pick and Pack** não é um sistema de faturamento e, por isso, os pedidos devem ser faturados através do OMS da VTEX. Saiba mais em [Faturar um pedido](https://help.vtex.com/pt/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT).
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md b/docs/announcements/pt/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
index 845bb6d44..05b2c7773 100644
--- a/docs/announcements/pt/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
+++ b/docs/announcements/pt/changes-in-the-orderplaced-provide-more-precision-to-google-analytics-data.md
@@ -60,7 +60,5 @@ As melhorias atendem principalmente a cenários em que um mesmo pedido possui pr
 Essa mudança __não requer__ nenhum tipo de ação. Se a sua loja já usa a __versão 4 do orderPlaced__, que é compatível com todas as funcionalidades de [Omnichannel](/pt/announcement/mude-seu-negocio-com-a-experiencia-omnichannel-vtex), o novo comportamento já está sendo aplicado.
 
 
-<div class="alert alert-warning">
-Essa mudança foi realizada <strong>apenas na versão 4 do orderPlaced</strong> e não afeta o comportamento das versões anteriores.
-</div>
+>⚠️ Essa mudança foi realizada **apenas na versão 4 do orderPlaced** e não afeta o comportamento das versões anteriores.
 
diff --git a/docs/announcements/pt/changes-in-vtex-support-service-policy.md b/docs/announcements/pt/changes-in-vtex-support-service-policy.md
index 090d71065..1fc660cec 100644
--- a/docs/announcements/pt/changes-in-vtex-support-service-policy.md
+++ b/docs/announcements/pt/changes-in-vtex-support-service-policy.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Agora, o canal principal para abrir um chamado é a VTE
 
 A dinâmica do Suporte VTEX passou por transformações com a transição do canal de atendimento. Agora, a [VTEX Community](https://community.vtex.com/) passa a ser o canal principal de suporte na maioria dos casos.
 
-<div class="alert alert-info">Esta mudança é válida apenas para contas no Brasil.</div>
+>ℹ️ Esta mudança é válida apenas para contas no Brasil.
 
 # O que mudou?
 Anteriormente, para obter auxílio do time do suporte VTEX, era necessário abrir um chamado no Suporte. A partir de hoje, a [VTEX Community](https://community.vtex.com/) se torna o canal primário de Suporte.
@@ -35,5 +35,5 @@ A maioria dos casos será tratada através da VTEX Community, porém, ainda exis
 
 Sugerimos também que, antes de publicar uma pergunta, os usuários realizem uma pesquisa na comunidade para verificar se a resposta já está disponível. Caso não encontrem a solução desejada, podem criar um novo tópico para receber ajuda da comunidade.
 
-<div class="alert alert-warning"> VTEX Community é um fórum público e, portanto, não devem ser compartilhadas informações sensíveis, como chaves de aplicação, senhas ou quaisquer outros dados confidenciais. </div>
+>⚠️ VTEX Community é um fórum público e, portanto, não devem ser compartilhadas informações sensíveis, como chaves de aplicação, senhas ou quaisquer outros dados confidenciais.
 
diff --git a/docs/announcements/pt/check-your-stores-caa-record.md b/docs/announcements/pt/check-your-stores-caa-record.md
index 3813c2ac7..2a252909d 100644
--- a/docs/announcements/pt/check-your-stores-caa-record.md
+++ b/docs/announcements/pt/check-your-stores-caa-record.md
@@ -17,9 +17,7 @@ announcementSynopsisPT: 'Recomendamos que você atualize as entradas CAA dos seu
 
 Com a aproximação da __Black Friday__, recomendamos que você atualize as entradas CAA dos seus gerenciadores de DNS até __9 de novembro__. Essa ação é necessária para que o certificado SSL seja gerado e/ou renovado. Só assim é possível usar a CDN da VTEX.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> esses tipos de entrada podem não estar disponíveis na interface do seu gerenciador de DNS, mas muitas vezes é possível gerenciá-los através de chamados no suporte da ferramenta específica.
-</div>
+>⚠️ **Atenção:** esses tipos de entrada podem não estar disponíveis na interface do seu gerenciador de DNS, mas muitas vezes é possível gerenciá-los através de chamados no suporte da ferramenta específica.
 
 
 ## O que você precisa fazer?
@@ -34,9 +32,7 @@ Nas configurações do __Gerenciador de DNS__, confira (ou peça para o respons
 ## Qual o impacto?
 Cadastrar as novas entradas apenas permite que as entidades __Digicert__, __Comodo__, __Globalsign__ e __Let's encrypt__ possam gerar e renovar certificados para seu domínio. __Esses certificados são fundamentais para que sua loja possa usar a CDN da VTEX e ter uma performance superior.__ Se a atualização não for feita, sua loja pode ter problemas de performance e demorar mais para ser carregada.
 
-<div class="alert alert-info">
-Lojas que não têm nenhuma entrada CAA configurada <strong>não precisam fazer a configuração</strong> e <strong>não serão afetadas</strong>.
-</div>
+>ℹ️ Lojas que não têm nenhuma entrada CAA configurada **não precisam fazer a configuração** e **não serão afetadas**.
 
 
 ## Conteúdos úteis
diff --git a/docs/announcements/pt/checkout-api-improvements-part-1.md b/docs/announcements/pt/checkout-api-improvements-part-1.md
index d637e9014..afc301396 100644
--- a/docs/announcements/pt/checkout-api-improvements-part-1.md
+++ b/docs/announcements/pt/checkout-api-improvements-part-1.md
@@ -19,9 +19,7 @@ Nosso time de desenvolvimento está constantemente melhorando a performance das
 
 Com a comunicação destas melhorias, queremos permitir que você já comece o processo de atualização das integrações e customizações da sua loja, pensando nas novas soluções oferecidas pelo nosso sistema.
 
-<div class="alert alert-warning">
-  O layout atual da API do Checkout continua funcionando normalmente. Ainda assim, é muito importante que a implementação das melhorias descritas abaixo seja feita desde já. Ainda não há previsão para o lançamento da nova major da API do Checkout. No entanto, nesta próxima versão, os pontos descontinuados que estão descritos abaixo não irão mais funcionar.
-</div>
+>⚠️ O layout atual da API do Checkout continua funcionando normalmente. Ainda assim, é muito importante que a implementação das melhorias descritas abaixo seja feita desde já. Ainda não há previsão para o lançamento da nova major da API do Checkout. No entanto, nesta próxima versão, os pontos descontinuados que estão descritos abaixo não irão mais funcionar.
 
 ## Endereço no carrinho e no pedido
 
diff --git a/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md b/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md
index 0080f819c..60def0885 100644
--- a/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md
+++ b/docs/announcements/pt/checkout-api-now-supports-recaptcha-v3.md
@@ -23,9 +23,7 @@ Além da funcionalidade nas frentes de loja nativas da plataforma VTEX, lojas im
 
 Agora, a API do Checkout suporta também reCATPCHA com validação baseada em pontuação (equivalente à v3), adequada para apps mobile nativos.
 
-<div class="alert alert-info">
-A VTEX está integrada com o reCAPTCHA enterprise, que oferece duas abordagens de validação: checkbox (equivalente ao reCAPTCHA v2) e baseada em pontuação (equivalente ao reCAPTCHA v3). Confira este artigo sobre o <a href="https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#versoes-do-recaptcha">reCAPTCHA no Checkout da VTEX</a> para aprender qual versão você deve usar dependendo das características da sua loja. Você também pode aprender mais sobre cada método: <a href="https://developers.google.com/recaptcha/docs/display">reCAPTCHA v2</a> ou <a href="https://developers.google.com/recaptcha/docs/v3">reCAPTCHA v3</a> com a documentação fornecida pelo Google.
-</div>
+>ℹ️ A VTEX está integrada com o reCAPTCHA enterprise, que oferece duas abordagens de validação: checkbox (equivalente ao reCAPTCHA v2) e baseada em pontuação (equivalente ao reCAPTCHA v3). Confira este artigo sobre o [reCAPTCHA no Checkout da VTEX](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#versoes-do-recaptcha) para aprender qual versão você deve usar dependendo das características da sua loja. Você também pode aprender mais sobre cada método: [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) ou [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3) com a documentação fornecida pelo Google.
 
 Entretanto, a opção de integração com reCAPTCHA checkbox (equivalente à v2) continua disponível, sendo a opção recomendada caso deseje implementar uma [integração de reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha) que não seja em um app mobile nativo.
 
diff --git a/docs/announcements/pt/close-bigger-deals-with-the-shared-cart.md b/docs/announcements/pt/close-bigger-deals-with-the-shared-cart.md
index 41cba1d82..6845a71c0 100644
--- a/docs/announcements/pt/close-bigger-deals-with-the-shared-cart.md
+++ b/docs/announcements/pt/close-bigger-deals-with-the-shared-cart.md
@@ -41,8 +41,6 @@ O carrinho compartilhado só é possível por causa da inclusão de um novo par
 - Use as [APIs da VTEX](https://github.com/vtex/vtex.js/tree/master/docs/checkout#getorderformexpectedorderformsections) para obter o ID do carrinho.
 - Customize a página do carrinho para que o link passe a contar com o ID.
 
-<div class="alert alert-warning">
-Lembramos que o carrinho compartilhado é opcional e as mudanças citadas aqui devem se feitas <strong>apenas pelas lojas que desejam usar a feature</strong>.
-</div>
+>⚠️ Lembramos que o carrinho compartilhado é opcional e as mudanças citadas aqui devem se feitas **apenas pelas lojas que desejam usar a feature**.
 
 Leia o [artigo sobre o carrinho compartilhado](/pt/tutorial/o-que-e-o-carrinho-compartilhado) e conheça melhor a nova funcionalidade. 
diff --git a/docs/announcements/pt/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md b/docs/announcements/pt/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
index 9d8d79421..ade650849 100644
--- a/docs/announcements/pt/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
+++ b/docs/announcements/pt/configuring-your-networks-firewall-access-rules-to-allow-the-new-domain.md
@@ -33,9 +33,7 @@ Entre em contato com a equipe de TI da sua operação, responsável pelas config
 
 Esta equipe precisará __revisar e ajustar as regras de firewall, garantindo a liberação para o domínio vtexassets.com__.
 
-<div class="alert alert-info">
-OBS: Não será necessário realizar qualquer ajuste no front-end, uma vez que o domínio <code>vteximg.com.br</code> continuará funcionando para customizações.
-</div>
+>ℹ️ OBS: Não será necessário realizar qualquer ajuste no front-end, uma vez que o domínio `vteximg.com.br` continuará funcionando para customizações.
 
 ## Quais impactos sua operação poderá sofrer caso não ocorra a adequação?
 
diff --git a/docs/announcements/pt/delivery-capacity.md b/docs/announcements/pt/delivery-capacity.md
index 8de5f1341..93b248106 100644
--- a/docs/announcements/pt/delivery-capacity.md
+++ b/docs/announcements/pt/delivery-capacity.md
@@ -40,6 +40,4 @@ Para utilizar da capacidade de entrega é necessário configurar uma  política
 
 Para saber como configurar a capacidade de entrega das suas entregas agendadas leia  [Capacidade de Entrega](https://help.vtex.com/pt/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
-<div class="alert alert-info">
-Essa funcionalidade está em estágio Beta e disponível apenas para ambientes Admin v3. 
-</div>
+>ℹ️ Essa funcionalidade está em estágio Beta e disponível apenas para ambientes Admin v3.
diff --git a/docs/announcements/pt/discontinuation-of-order-completed-order-create-error-and-order-creation.md b/docs/announcements/pt/discontinuation-of-order-completed-order-create-error-and-order-creation.md
index 2d954f42d..0ec8fdf62 100644
--- a/docs/announcements/pt/discontinuation-of-order-completed-order-create-error-and-order-creation.md
+++ b/docs/announcements/pt/discontinuation-of-order-completed-order-create-error-and-order-creation.md
@@ -19,9 +19,7 @@ A partir de 24 de junho de 2019, os status dos pedidos de Fulfillment `order-com
 
 Os pedidos de origem Fulfillment são aqueles relacionados às etapas de entrega ou retirada de um pedido. Podemos associar os pedidos que têm esta origem ao processo que um seller realiza para efetuar a entrega ou a retirada de um pedido.
 
-<div class="alert alert-warning">
-O status dos pedidos de origem Marketplace não serão alterados.
-</div>
+>⚠️ O status dos pedidos de origem Marketplace não serão alterados.
 
 ## Por que a VTEX está tomando esta ação
 
diff --git a/docs/announcements/pt/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md b/docs/announcements/pt/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
index 0a9c0c5d0..4c9c06368 100644
--- a/docs/announcements/pt/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
+++ b/docs/announcements/pt/discontinuation-of-waiting-for-seller-confirmation-and-order-completed.md
@@ -31,6 +31,4 @@ De uma maneira geral, a descontinuação destes status não deve impactar nenhum
 
 De qualquer forma, recomendamos que você revise sua integração para confirmar que esses status não estão sendo usados realmente.
 
-<div class="alert alert-info">
-A ação de tirar o workflow do caminho crítico do fechamento de compra para pedidos de origem Fulfillment já foi realizado. Acesse nosso artigo para saber mais sobre esta <a href="https://help.vtex.com/pt/announcements/descontinuacao-dos-status-dos-pedidos-de-fulfillment-order-completed-order--4AJyu9fJNSKNpL4g4dfgcp">retirada do workflow nos pedidos de origem Fulfillment.</a>
-</div>
+>ℹ️ A ação de tirar o workflow do caminho crítico do fechamento de compra para pedidos de origem Fulfillment já foi realizado. Acesse nosso artigo para saber mais sobre esta [retirada do workflow nos pedidos de origem Fulfillment.](https://help.vtex.com/pt/announcements/descontinuacao-dos-status-dos-pedidos-de-fulfillment-order-completed-order--4AJyu9fJNSKNpL4g4dfgcp)
diff --git a/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md b/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
index 41397822a..139cb87e0 100644
--- a/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
+++ b/docs/announcements/pt/ensure-more-safety-and-control-on-your-order-authorization-screen.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Possibilidade de limitar perfis de acesso à tela de Autorização de pedidos'
 ---
 
-<div class="alert alert-warning">
-A partir do dia 25 de junho de 2019, o usuário que não tiver acesso vinculado ao perfil com o produto <code>Order Authorization</code>  não terá permissão para visualizar ou editar a tela de Autorização de Pedidos.
-</div>
+>⚠️ A partir do dia 25 de junho de 2019, o usuário que não tiver acesso vinculado ao perfil com o produto `Order Authorization`  não terá permissão para visualizar ou editar a tela de Autorização de Pedidos.
 
 Buscando garantir maior segurança, criamos a possibilidade de limitar perfis de acesso à tela de Autorização de pedidos, permitindo que somente alguns usuários visualizem ou editem as informações. Para saber mais sobre a Autorização de pedidos, acesse nosso [comunicado sobre o lançamento da feature](https://help.vtex.com/pt/announcements/aumente-suas-vendas-com-a-nova-tela-autorizacao-de-pedidos--7EXIgaESHfI46lkaZw9jrQ) ou o [tutorial que explica o seu funcionamento](https://help.vtex.com/pt/tutorial/como-funciona-a-autorizacao-de-pedidos--3MBK6CmKHAuUjMBieDU0pn)
   
diff --git a/docs/announcements/pt/erp-integration-guides-have-a-new-home.md b/docs/announcements/pt/erp-integration-guides-have-a-new-home.md
index 46b2d57e0..ca9260bf3 100644
--- a/docs/announcements/pt/erp-integration-guides-have-a-new-home.md
+++ b/docs/announcements/pt/erp-integration-guides-have-a-new-home.md
@@ -27,4 +27,4 @@ Como parte do esforço de migração da documentação para desenvolvedores para
 
 Esta documentação usa a nova [API REST do catálogo](https://developers.vtex.com/docs/guides/catalog-api-overview) e substitui nosso guia anterior baseado na API SOAP do Webservice, que não está mais disponível no nosso Help Center.
 
-<div class="alert alert-warning">Ainda não deprecamos a API SOAP do Webservice, porém ela não é mais recomendada para novas integrações.</div>
+>⚠️ Ainda não deprecamos a API SOAP do Webservice, porém ela não é mais recomendada para novas integrações.
diff --git a/docs/announcements/pt/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md b/docs/announcements/pt/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
index 796b92d38..f4a7cfcc7 100644
--- a/docs/announcements/pt/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
+++ b/docs/announcements/pt/facebook-login-will-no-longer-be-available-for-the-vtex-admin.md
@@ -23,9 +23,7 @@ Por isso, após uma análise objetiva e criteriosa, decidimos remover a funciona
 
 O suporte ao login por Facebook será removido de todas versões do painel administrativo da VTEX.
 
-<div class="alert alert-info">
-A funcionalidade de login por Facebook ainda vai estar disponível para o login de compradores na sua loja VTEX.
-</div>
+>ℹ️ A funcionalidade de login por Facebook ainda vai estar disponível para o login de compradores na sua loja VTEX.
 
 ## Por que estamos realizando esta mudança?
 
diff --git a/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md b/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
index bd58a9afb..a7c922007 100644
--- a/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
+++ b/docs/announcements/pt/fastcheckout-boost-your-conversion-with-the-new-checkout.md
@@ -49,9 +49,7 @@ O FastCheckout permite uma experiência de checkout customizável, adaptando-se
 
 Proporcionamos a liberdade de incluir elementos completamente customizados, sem a necessidade de conhecimento em JavaScript ou CSS.
 
-<div class="alert alert-warning">
-  <p>A primeira versão lançada do FastCheckout permite customizações limitadas. Em breve, será possível personalizar completamente o conteúdo utilizando os pontos de extensão da FastStore Platform.</p>
-</div>
+>⚠️ A primeira versão lançada do FastCheckout permite customizações limitadas. Em breve, será possível personalizar completamente o conteúdo utilizando os pontos de extensão da FastStore Platform.
 
 ### Novo fluxo de compra
 
diff --git a/docs/announcements/pt/freely-develop-custom-storefront-components-in-vtex-io.md b/docs/announcements/pt/freely-develop-custom-storefront-components-in-vtex-io.md
index f4fa3cd6c..e4a507009 100644
--- a/docs/announcements/pt/freely-develop-custom-storefront-components-in-vtex-io.md
+++ b/docs/announcements/pt/freely-develop-custom-storefront-components-in-vtex-io.md
@@ -27,9 +27,7 @@ Se a sua loja é construída usando o [VTEX Store Framework](https://developers.
 
 De agora em diante, **desenvolva componentes customizados de *front* de loja no [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io) usando as tecnologias do VTEX Store Framework e [React](https://reactjs.org/)** de acordo com as necessidades do seu negócio, sem pedir permissão à VTEX.
 
-<div class="alert alert-info">
-  O VTEX Store Framework é a solução da VTEX para construir <i>front</i> de lojas na velocidade da luz. Clientes VTEX podem aproveitar todos os benefícios da solução usando a plataforma de desenvolvimento VTEX IO. Se você ainda não está familiarizado com o VTEX IO, entre em contato com o time de Customer Success da VTEX, com a sua agência parceira ou com o seu gerente de conta para saber por onde começar. 
-</div>
+>ℹ️ O VTEX Store Framework é a solução da VTEX para construir <i>front</i> de lojas na velocidade da luz. Clientes VTEX podem aproveitar todos os benefícios da solução usando a plataforma de desenvolvimento VTEX IO. Se você ainda não está familiarizado com o VTEX IO, entre em contato com o time de Customer Success da VTEX, com a sua agência parceira ou com o seu gerente de conta para saber por onde começar.
 
 ## O que mudou?
 
@@ -37,9 +35,7 @@ Antes, desenvolvedores interessados em criar componentes customizados usando o V
 
 Esse processo se tornou dispensável, uma vez que **o *builder* de React está oficialmente em *open beta***. Você agora pode se beneficiar da autonomia  para customizar e melhorar a experiência do *front* da sua loja usando a tecnologia VTEX Store Framework e React.
 
-<div class="alert alert-warning">
-<bold>Essa mudança se aplica somente ao <i>builder</i> de React.</bold> A VTEX ainda exige que você preencha o <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">formulário de candidatura para desenvolvimento</a> e espere pela nossa aprovação caso o seu projeto dependa de outros <i>builders</i> ainda em <i>closed beta</i>. Isso inclui, por exemplo, integrações de <i>back-end</i> usando Node.js e GraphQL.  
-</div>
+>⚠️ <bold>Essa mudança se aplica somente ao <i>builder</i> de React.</bold> A VTEX ainda exige que você preencha o [formulário de candidatura para desenvolvimento](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io) e espere pela nossa aprovação caso o seu projeto dependa de outros <i>builders</i> ainda em <i>closed beta</i>. Isso inclui, por exemplo, integrações de <i>back-end</i> usando Node.js e GraphQL.
 
 ## Por que realizamos esta mudança?
 
@@ -49,7 +45,5 @@ Entendemos que a plataforma de desenvolvimento VTEX IO alcançou maturidade e es
 
 Nenhuma ação é necessária. Entretanto, tenha em mente que **a VTEX não fornece suporte para componentes customizados desenvolvidos por terceiros**. A manutenção, performance e qualidade deles está sob a responsabilidade do fornecedor da app. 
 
-<div class="alert alert-info">
-Confira a nossa documentação sobre as <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-developing-custom-storefront-components">melhores práticas para o desenvolvimento de componentes customizados de <i>storefront</i></a>!
-</div>
+>ℹ️ Confira a nossa documentação sobre as [melhores práticas para o desenvolvimento de componentes customizados de <i>storefront</i>](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-developing-custom-storefront-components)!
 
diff --git a/docs/announcements/pt/from-now-on-you-can-create-promotional-price-tables.md b/docs/announcements/pt/from-now-on-you-can-create-promotional-price-tables.md
index 946a062a0..fa16eb618 100644
--- a/docs/announcements/pt/from-now-on-you-can-create-promotional-price-tables.md
+++ b/docs/announcements/pt/from-now-on-you-can-create-promotional-price-tables.md
@@ -39,12 +39,8 @@ Caso você ainda não tenha uma tabela de preços ou se quiser criar uma nova, o
 
 Completando os passos acima, sua tabela de preços promocionais vai estar ativa e pronta para ser aplicada. Mas lembre-se de que a promoção leva __10 minutos__ até ficar visível e começar a ser refletida nos pedidos na loja.
 
-<div class="alert alert-info">
-Há algumas características específicas dessa promoção que devem ser levadas em conta no momento da criação e utilização:</br>
-<strong>1-</strong> O preço configurado na tabela de preço vai ser aplicado apenas se o valor for menor que o configurado na política comercial usada pelo site. <em>Exemplo:</em> o item que possui um preço de R$ 199,00 só terá o valor da tabela aplicado se este último for menor do que R$ 199,00.</br>
-<strong>2-</strong> Promoções de tabelas de preços concorrem entre si e com as demais promoções configuradas que manipulam preços. Ou seja, caso exista mais de uma promoção de tabela de preço configurada e ao menos uma promoção de desconto percentual, nominal ou fórmula (ativas e elegíveis ao carrinho em questão), o menor preço entre elas é o que será aplicado.
-</div>
-
-<div class="alert alert-warning">
-Só é possível configurar <strong>uma tabela de preço por promoção</strong>. E, hoje, há um limite de <strong>até 5 promoções de tabelas de preços simultâneas</strong> para cada loja.
-</div>
+>ℹ️ Há algumas características específicas dessa promoção que devem ser levadas em conta no momento da criação e utilização:</br>
+> **1-** O preço configurado na tabela de preço vai ser aplicado apenas se o valor for menor que o configurado na política comercial usada pelo site. *Exemplo:* o item que possui um preço de R$ 199,00 só terá o valor da tabela aplicado se este último for menor do que R$ 199,00.</br>
+> **2-** Promoções de tabelas de preços concorrem entre si e com as demais promoções configuradas que manipulam preços. Ou seja, caso exista mais de uma promoção de tabela de preço configurada e ao menos uma promoção de desconto percentual, nominal ou fórmula (ativas e elegíveis ao carrinho em questão), o menor preço entre elas é o que será aplicado.
+
+>⚠️ Só é possível configurar **uma tabela de preço por promoção**. E, hoje, há um limite de **até 5 promoções de tabelas de preços simultâneas** para cada loja.
diff --git a/docs/announcements/pt/from-now-on-you-can-export-up-to-3-thousand-orders.md b/docs/announcements/pt/from-now-on-you-can-export-up-to-3-thousand-orders.md
index 0cb155e5a..d2583af0b 100644
--- a/docs/announcements/pt/from-now-on-you-can-export-up-to-3-thousand-orders.md
+++ b/docs/announcements/pt/from-now-on-you-can-export-up-to-3-thousand-orders.md
@@ -23,6 +23,4 @@ Para que o processo fosse o mais ágil possível, já vínhamos recomendando o l
 ## Como exportar mais de 3 mil pedidos
 Você ainda pode exportar mais do que 3 mil pedidos. Para isso, use as APIs de gerenciamento de pedidos (antigo OMS): [Get Order](https://developers.vtex.com/reference/orders#getorder) e [Get Feed Order Status](https://developers.vtex.com/reference/feed-v3#getfeedorderstatus1).
 
-<div class="alert alert-warning">
-<strong>Mas lembre-se:</strong> para funcionar, é necessário que você <strong>crie um range de data/hora que inclua, no máximo, 3 mil pedidos</strong>. Com o range definido e o limite respeitado, você vai poder chamar a API quantas vezes for necessário.
-</div>
+>⚠️ **Mas lembre-se:** para funcionar, é necessário que você **crie um range de data/hora que inclua, no máximo, 3 mil pedidos**. Com o range definido e o limite respeitado, você vai poder chamar a API quantas vezes for necessário.
diff --git a/docs/announcements/pt/google-catalog-migration.md b/docs/announcements/pt/google-catalog-migration.md
index 4f98b50db..8a1468aaa 100644
--- a/docs/announcements/pt/google-catalog-migration.md
+++ b/docs/announcements/pt/google-catalog-migration.md
@@ -23,9 +23,7 @@ A funcionalidade é destinada a sellers que antes integravam os produtos de sua
 
 O objetivo dessa funcionalidade é possibilitar ao seller a migração da relevância de seus anúncios no Google Shopping. Ao migrar sua integração para o conector da VTEX, você não perde o histórico de relevância dos seus anúncios. 
 
-<div class="alert alert-info">
-A migração de catálogo apenas mapeia e realiza match entre produtos do catálogo VTEX com anúncios já existentes no Merchant Center do Google Shopping.
-</div>
+>ℹ️ A migração de catálogo apenas mapeia e realiza match entre produtos do catálogo VTEX com anúncios já existentes no Merchant Center do Google Shopping.
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/headless-cms-events-available-in-audit.md b/docs/announcements/pt/headless-cms-events-available-in-audit.md
index cb0ce0a16..5d95928dc 100644
--- a/docs/announcements/pt/headless-cms-events-available-in-audit.md
+++ b/docs/announcements/pt/headless-cms-events-available-in-audit.md
@@ -38,9 +38,7 @@ Na coluna **Ação**, todos os eventos do Headless CMS também apresentam as seg
 * **VARIANT_ID:** código identificador único da versão do conteúdo.
 * **WORKSPACE:** workspace em que a alteração foi realizada.
 
-<div class="alert alert-info">
-  <p>Confira a <a href="https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista completa de eventos disponíveis no Audit</a>.</p>
-</div>
+>ℹ️ Confira a [lista completa de eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/improvement-of-the-seller-white-label-selection-algorithm.md b/docs/announcements/pt/improvement-of-the-seller-white-label-selection-algorithm.md
index 22502b705..5484c5374 100644
--- a/docs/announcements/pt/improvement-of-the-seller-white-label-selection-algorithm.md
+++ b/docs/announcements/pt/improvement-of-the-seller-white-label-selection-algorithm.md
@@ -27,9 +27,7 @@ O algoritmo de seleção de sellers foi atualizado para assegurar a maior cobert
 
 Além disso, para escolha de sellers que oferecem a opção de retirada, o algoritmo priorizará sempre a distância da localização de referência sobre critérios de preço e prazo para retirada.
 
-<div class="alert alert-warning">
-Atenção: A atualização do algoritmo se aplica para Seller White Label, e inclui <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">Contas Franquia</a>. O algoritmo de seleção de sellers é aplicado quando o cliente consulta as opções de entrega. Isso significa que ele é aplicado na previsão de entrega no carrinho ou na etapa de entrega e retirada do checkout.
-</div>
+>⚠️ Atenção: A atualização do algoritmo se aplica para Seller White Label, e inclui [Contas Franquia](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa). O algoritmo de seleção de sellers é aplicado quando o cliente consulta as opções de entrega. Isso significa que ele é aplicado na previsão de entrega no carrinho ou na etapa de entrega e retirada do checkout.
 
 ##  Por que realizamos esta mudança?
 
diff --git a/docs/announcements/pt/integration-methods-with-the-catalog-through-web-service-will-be.md b/docs/announcements/pt/integration-methods-with-the-catalog-through-web-service-will-be.md
index c08259126..c95954495 100644
--- a/docs/announcements/pt/integration-methods-with-the-catalog-through-web-service-will-be.md
+++ b/docs/announcements/pt/integration-methods-with-the-catalog-through-web-service-will-be.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Em 29/10, vamos descontinuar alguns métodos de Web Service para integração com o catálogo.'
 ---
 
-<div class="alert alert-info">
-A mudança descrita aqui só tem impacto na sua operação se sua loja usa <b>integração por Web Service</b> e essa integração usa algum dos métodos listados abaixo. Caso contrário, você <b>não</b> precisa tomar nenhuma ação.
-</div>
+>ℹ️ A mudança descrita aqui só tem impacto na sua operação se sua loja usa **integração por Web Service** e essa integração usa algum dos métodos listados abaixo. Caso contrário, você **não** precisa tomar nenhuma ação.
 
 A partir do dia __29 de outubro__, a VTEX vai descontinuar os seguintes métodos de integração por Web Service, com o objetivo de melhorar a performance da plataforma.
 
diff --git a/docs/announcements/pt/integrations-with-vtex-apis-now-need-token-authentication.md b/docs/announcements/pt/integrations-with-vtex-apis-now-need-token-authentication.md
index a8c111529..f43aa1f74 100644
--- a/docs/announcements/pt/integrations-with-vtex-apis-now-need-token-authentication.md
+++ b/docs/announcements/pt/integrations-with-vtex-apis-now-need-token-authentication.md
@@ -37,4 +37,4 @@ Usar e-mail e senha para autenticação compromete a segurança de suas integra
 - Verifique se sua loja usa e-mail e senha em alguma integração com as APIs VTEX.
 - Caso use, crie um par de appKey e appToken para essa integração. Veja como no artigo [Criar appKey e appToken para autenticar integrações](http://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes).
 
-<div class="alert alert-warning"><strong>Atenção</strong>: todo par de appKey e appToken, quando criado, nasce sem estar vinculado a um perfil de acessso. Então, depois de criá-lo, é necessário vincular a appKey e o appToken ao perfil de acesso desejado.</div>
+>⚠️ **Atenção**: todo par de appKey e appToken, quando criado, nasce sem estar vinculado a um perfil de acessso. Então, depois de criá-lo, é necessário vincular a appKey e o appToken ao perfil de acesso desejado.
diff --git a/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md b/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
index 11133d20b..d346eefe7 100644
--- a/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
+++ b/docs/announcements/pt/introducing-the-new-shipping-strategy-interfaces.md
@@ -38,7 +38,5 @@ A partir de 31 de maio, a versão beta da **Estratégia de envio** está dispon
 
 Se após o teste você desejar voltar à versão antiga, no menu <i class="fas fa-ellipsis-v"></i> do canto superior da página, clique em `Voltar à versão anterior` e comente sobre o motivo. O retorno à experiência antiga será automático.
 
-<div class="alert alert-warning">
-A partir de 26 de julho, as novas interfaces de <b>Estratégia de envio</b> serão o padrão para todas as lojas VTEX.
-</div>
+>⚠️ A partir de 26 de julho, as novas interfaces de **Estratégia de envio** serão o padrão para todas as lojas VTEX.
 
diff --git a/docs/announcements/pt/introducing-vtex-ad-network-beta.md b/docs/announcements/pt/introducing-vtex-ad-network-beta.md
index 1f050ab75..4eed7914a 100644
--- a/docs/announcements/pt/introducing-vtex-ad-network-beta.md
+++ b/docs/announcements/pt/introducing-vtex-ad-network-beta.md
@@ -41,9 +41,7 @@ Veja abaixo como você pode fazer parte da **VTEX Ad Network**, seja como loja o
 
 Para disponibilizar espaço publicitário na sua loja, basta instalar o app [VTEX Ad Network para lojas]() na sua conta VTEX. Saiba mais com o artigo [Exibindo anúncios do VTEX Ad Network na sua loja (Beta)](https://help.vtex.com/pt/tutorial/exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta--6gWgZrMLcS5FDFFdl5LETA).
 
-<div class="alert alert-danger">
-Por hora, podem disponibilizar espaço de anúncios apenas lojas desenvolvidas com <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
-</div>
+>❗ Por hora, podem disponibilizar espaço de anúncios apenas lojas desenvolvidas com [Store Framework](https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework).
 
 ### Anunciantes
 
diff --git a/docs/announcements/pt/last-chance-to-buy-tickets-for-vtex-training-day.md b/docs/announcements/pt/last-chance-to-buy-tickets-for-vtex-training-day.md
index 84a9e17f3..83d939de0 100644
--- a/docs/announcements/pt/last-chance-to-buy-tickets-for-vtex-training-day.md
+++ b/docs/announcements/pt/last-chance-to-buy-tickets-for-vtex-training-day.md
@@ -38,9 +38,9 @@ O palco do VTEX IO, a plataforma de desenvolvimento da VTEX. Nossos engenheiros
 <br />
 <br />
 
-<div class="alert alert-info">
-<strong>Garanta 30% de desconto</strong> na compra de 10 ou mais ingressos! <br />Mas corra, que a promoção é válida só até o fim de novembro.
-</div>
+>ℹ️ **Garanta 30% de desconto** na compra de 10 ou mais ingressos! 
+>
+> Mas corra, que a promoção é válida só até o fim de novembro.
 
 
 __Quando:__ 06/12/2018 _(o evento dura o dia todo)_ 
diff --git a/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md b/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
index 269072861..00a454887 100644
--- a/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
+++ b/docs/announcements/pt/lead-time-configuring-shipping-time-at-sku-level.md
@@ -33,9 +33,7 @@ Agora, existe também a opção de configurar o tempo de envio a nível de SKU,
 
 ![lead_time_inventory_management_PT](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
 
-<div class="alert alert-warning">
-Pelo Admin VTEX, o lead time é configurado em dias, até o limite de 365 dias. Por padrão, os dias são contados em dias úteis, mas você pode configurar sua política de envio para que a <a href="https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional">contagem seja feita em dias corridos</a>. Para configurar períodos em horas, minutos e segundos, é necessário utilizar o endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>⚠️ Pelo Admin VTEX, o lead time é configurado em dias, até o limite de 365 dias. Por padrão, os dias são contados em dias úteis, mas você pode configurar sua política de envio para que a [contagem seja feita em dias corridos](https://help.vtex.com/pt/tutorial/lead-time-tempo-de-envio-a-nivel-de-sku--16yv5Mkj6bTyWR1hCN2f4B#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional). Para configurar períodos em horas, minutos e segundos, é necessário utilizar o endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md b/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md
index 697814ba7..1c3d83918 100644
--- a/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md
+++ b/docs/announcements/pt/legacy-payment-connectors-will-be-discontinued-in-2024.md
@@ -19,9 +19,7 @@ Para integrar meios de pagamentos à plataforma VTEX, provedores de pagamentos p
 
 ## O que está mudando?
 
-<div class="alert alert-danger">
-As mudanças descritas neste documento não terão impacto na Black Friday 2023. Serão realizadas apenas no primeiro trimestre de 2024.
-</div>
+>❗ As mudanças descritas neste documento não terão impacto na Black Friday 2023. Serão realizadas apenas no primeiro trimestre de 2024.
 
 A VTEX está iniciando a descontinuação destes conectores legados, que acontecerá em etapas:
 
@@ -109,9 +107,7 @@ Se você é um provedor de pagamentos responsável por um ou mais [conectores qu
 
 Neste caso, recomendamos que submeta seu novo conector para homologação até 10 de fevereiro de 2024, para que as lojas tenham tempo hábil para reconfigurar suas conexões de pagamentos antes da descontinuação. Saiba mais sobre o [processo de homologação de novos conectores de pagamento](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-homologation).
 
-<div class="alert alert-danger">
-A VTEX não pode garantir que seu novo conector de pagamentos estará disponível para lojistas VTEX antes da descontinuação oficial caso você o submeta para homologação após esta data.
-</div>
+>❗ A VTEX não pode garantir que seu novo conector de pagamentos estará disponível para lojistas VTEX antes da descontinuação oficial caso você o submeta para homologação após esta data.
 
 Caso tenha dúvidas sobre este processo ou queira alinhar a comunicação conjunta com lojistas, entre em contato com seu Partner Manager VTEX.
 
diff --git a/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md b/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
index 1fb9ab0de..751b527df 100644
--- a/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
+++ b/docs/announcements/pt/luhn-algorithm-for-credit-and-debit-cards-at-checkout.md
@@ -35,6 +35,4 @@ A rejeição de uma transação de pagamento por motivo de número de cartão in
 
 Nenhuma ação é necessária. O algoritmo de Luhn já está ativo em todas as lojas VTEX.
 
-<div class="alert alert-warning">
-O algoritmo de Luhn não tem a função restringir fraudes por ataques de cartões. Seu objetivo específico é a verificação de erros de digitação ou preenchimento dos números dos cartões.
-</div>
+>⚠️ O algoritmo de Luhn não tem a função restringir fraudes por ataques de cartões. Seu objetivo específico é a verificação de erros de digitação ou preenchimento dos números dos cartões.
diff --git a/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md b/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md
index 42f6ed366..d753204d9 100644
--- a/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md
+++ b/docs/announcements/pt/maximum-price-per-item-promotion-will-be-disabled.md
@@ -21,9 +21,9 @@ De fato, estamos fazendo essa mudança justamente porque, com a evolução da pl
 
 Eliminando a promoção Preço Máximo por Item, melhoramos a performance do módulo de promoções e o gerenciamento das lojas.
 
-<div class="alert alert-warning">Até o dia 20 de novembro, a promoção Preço Máximo por Item continua existindo. Porém, o número máximo de itens permitido passa a ser <b>100</b>. Anteriormente o máximo permitido era 500.</div>
+>⚠️ Até o dia 20 de novembro, a promoção Preço Máximo por Item continua existindo. Porém, o número máximo de itens permitido passa a ser **100**. Anteriormente o máximo permitido era 500.
 
-<div class="alert alert-danger">Se você usa alguma promoção Preço Máximo por Item, leia este texto até o final e adapte o método em sua loja. Caso contrário, os SKUs em questão deixarão de ser impactados por essa estratégia de negócio.</div>
+>❗ Se você usa alguma promoção Preço Máximo por Item, leia este texto até o final e adapte o método em sua loja. Caso contrário, os SKUs em questão deixarão de ser impactados por essa estratégia de negócio.
 
 ## Alternativas
 
diff --git a/docs/announcements/pt/multi-currency-gift-card.md b/docs/announcements/pt/multi-currency-gift-card.md
index d58af7cad..bd9c1df47 100644
--- a/docs/announcements/pt/multi-currency-gift-card.md
+++ b/docs/announcements/pt/multi-currency-gift-card.md
@@ -43,7 +43,5 @@ Para criar um vale-presente em uma moeda específica, siga os passos abaixo:
 
 As moedas disponíveis serão as mesmas cadastradas nas [políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) de cada loja.
 
-<div class="alert alert-warning">
-A escolha da moeda deve ser realizada durante a criação de cada vale-presente ou de um lote de vales-presente. Não é possível modificar a moeda atribuída a um vale-presente após a sua criação. 
-</div>
+>⚠️ A escolha da moeda deve ser realizada durante a criação de cada vale-presente ou de um lote de vales-presente. Não é possível modificar a moeda atribuída a um vale-presente após a sua criação.
 
diff --git a/docs/announcements/pt/my-authentication-section-in-my-account.md b/docs/announcements/pt/my-authentication-section-in-my-account.md
index ed316e547..8e478dfab 100644
--- a/docs/announcements/pt/my-authentication-section-in-my-account.md
+++ b/docs/announcements/pt/my-authentication-section-in-my-account.md
@@ -17,9 +17,7 @@ announcementSynopsisPT: 'My Authentication é uma aba do My Account que permite
 
 My Authentication é uma aba que aparece no painel do My Account dentro da loja e está disponível em todas as contas da VTEX.
 
-<div class="alert alert-danger">
-Esta mudança afetará todas as lojas da VTEX. Como a mudança interfere em alguns componentes na UI da loja, é necessário que você faça alterações manuais nas configurações da sua loja até a data limite de 29/09.
-</div>
+>❗ Esta mudança afetará todas as lojas da VTEX. Como a mudança interfere em alguns componentes na UI da loja, é necessário que você faça alterações manuais nas configurações da sua loja até a data limite de 29/09.
 
 ## O que muda?
 
@@ -55,9 +53,7 @@ Como a habilitação da aba insere um elemento na UI da loja, ela pode precisar
 - Caso a sua loja seja VTEX IO, utilize o endereço `https://{account}.myvtex.com/account#/authentication`, substituindo `{account}` pelo nome da conta.
 - Caso a sua loja não use o VTEX IO, utilize o endereço `https://{account}.vtexcommercestable.com.br/_secure/account#/authentication`, substituindo `{account}` pelo nome da conta.
 
-<div class="alert alert-warning">
-Antes de acessar a aba de autenticação pela URL é preciso fazer login na loja com uma conta de usuário.
-</div>
+>⚠️ Antes de acessar a aba de autenticação pela URL é preciso fazer login na loja com uma conta de usuário.
 
 Para realizar a customização de aparência da aba, peça para o desenvolvedor seguir o artigo [My Authentication Customization Guide using CMS](https://developers.vtex.com/vtex-rest-api/docs/ui-customization-my-authentication), para lojas que não utilizam o VTEX IO, ou o artigo [My Authentication Customization Guide on VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-my-authentication), para lojas do VTEX IO, no nosso portal para desenvolvedores.
 
diff --git a/docs/announcements/pt/my-orders-is-now-available-on-extension-store.md b/docs/announcements/pt/my-orders-is-now-available-on-extension-store.md
index 989394914..a56abee21 100644
--- a/docs/announcements/pt/my-orders-is-now-available-on-extension-store.md
+++ b/docs/announcements/pt/my-orders-is-now-available-on-extension-store.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'A partir de 5 de junho,  o uso da extensão para a página "Meus pedidos" será obrigatório para todas as lojas.'
 ---
 
-<div class="alert alert-info">
-Conforme anunciado aqui, o <strong>My Orders</strong> já é obrigatório para todas as lojas. Desde <strong>6 de junho</strong>, ele já vem instalado por default e não está mais visível na App Store.
-</div>
+>ℹ️ Conforme anunciado aqui, o **My Orders** já é obrigatório para todas as lojas. Desde **6 de junho**, ele já vem instalado por default e não está mais visível na App Store.
 
 Já está disponível na __App Store__ da VTEX o __My Orders__, uma extensão que traz uma série de melhorias para a página "Meus Pedidos". Por todas as vantagens que oferece (incluindo facilidade de customização e ganhos de performance da página), seu uso vai passar a ser obrigatório a partir de __5 de junho__.
 
@@ -25,7 +23,7 @@ Entre as novidades da nova extensão estão o suporte para visualização de ane
 
 Outra característica importante é que agora os dados dos pedidos vêm da API do OMS. Uma mudança que deixa o status do pedido muito mais preciso.
 
-<div class="alert alert-warning">
-<strong>Atenção</strong><br>
-Recomendamos que você instale o <strong>My Orders</strong> na sua loja o quanto antes, principalmente se você já tiver alguma customização na página "Meus Pedidos". Dessa forma, você vai poder testar todas as possibilidades da nova extensão e evitar quebras quando ela se tornar obrigatória.
-</div>
+>⚠️ **Atenção**
+>
+> 
+> Recomendamos que você instale o **My Orders** na sua loja o quanto antes, principalmente se você já tiver alguma customização na página "Meus Pedidos". Dessa forma, você vai poder testar todas as possibilidades da nova extensão e evitar quebras quando ela se tornar obrigatória.
diff --git a/docs/announcements/pt/new-cdn-gives-more-security-and-speed.md b/docs/announcements/pt/new-cdn-gives-more-security-and-speed.md
index 3343d113e..0adb65f9f 100644
--- a/docs/announcements/pt/new-cdn-gives-more-security-and-speed.md
+++ b/docs/announcements/pt/new-cdn-gives-more-security-and-speed.md
@@ -26,9 +26,11 @@ Algumas das vantagens de usar uma CDN são:
 
 E com o suporte a HTTP/2 você tem acesso a uma série de outras melhorias. Para entender quais são elas, veja este artigo do Tecnoblog: [Como funciona o HTTP/2 e o que ele muda na sua vida](https://tecnoblog.net/173920/http-2-como-funciona/).
 
-<div class="alert alert-warning">
-<strong>Todas as lojas VTEX devem migrar</strong> para a nova CDN.<br><br>Veja <a href="http://help.vtex.com/pt/tutorial/ativar-nova-cdn-da-vtex">neste artigo</a> como fazer essa migração.
-</div>
+>⚠️ **Todas as lojas VTEX devem migrar** para a nova CDN.
+>
+> 
+>
+> Veja [neste artigo](http://help.vtex.com/pt/tutorial/ativar-nova-cdn-da-vtex) como fazer essa migração.
 
 Não há riscos ou contraindicações para aderir ao novo modelo.
 
diff --git a/docs/announcements/pt/new-deadline-activate-the-new-cdn-until-may-31.md b/docs/announcements/pt/new-deadline-activate-the-new-cdn-until-may-31.md
index e0cf527d7..1c9555fbf 100644
--- a/docs/announcements/pt/new-deadline-activate-the-new-cdn-until-may-31.md
+++ b/docs/announcements/pt/new-deadline-activate-the-new-cdn-until-may-31.md
@@ -45,9 +45,7 @@ Depois de ativar o HTTPS, você deverá:
 
 Se o domínio da sua loja aponta para algo que contenha `vtexcommerce.com.br` ou `hodor.vtex.com`, isso significa que ela ainda usa o CNAME antigo. A atualização é necessária porque só vai ser possível ter conteúdo no domínio `{hostname}.cdn.vtex.com`.
 
-<div class="alert alert-warning">
-Após <strong>31 de maio</strong>, todos os CNAMEs antigos deixarão de entregar as lojas. Se a sua estiver usando um CNAME antigo, <strong>ela vai ficar fora do ar</strong>.
-</div>
+>⚠️ Após **31 de maio**, todos os CNAMEs antigos deixarão de entregar as lojas. Se a sua estiver usando um CNAME antigo, **ela vai ficar fora do ar**.
 
 Depois de ativar o HTTPS e atualizar para o novo CNAME da VTEX, você precisará solicitar a ativação da nova CDN. Se isso não for feito até __31 de maio__, a ativação será feita de maneira automática. Por isso, é fundamental que você realize todas as ações já comunicadas anteriormente e reforçadas neste anúncio. Assim, você evita quebras na loja que poderiam ser evitadas.
 
diff --git a/docs/announcements/pt/new-facebook-business-extension-integration-app.md b/docs/announcements/pt/new-facebook-business-extension-integration-app.md
index f2090e6ba..3208a7407 100644
--- a/docs/announcements/pt/new-facebook-business-extension-integration-app.md
+++ b/docs/announcements/pt/new-facebook-business-extension-integration-app.md
@@ -62,8 +62,6 @@ As funcionalidades instaladas automaticamente com a integração com a app tamb
 
 Para integrar sua loja VTEX ao FBE, basta seguir os passos do [guia de Integração com o Facebook Business Extension](https://help.vtex.com/pt/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D).
 
-<div class="alert alert-warning">
-Mesmo que você já tenha configurado a <a href="https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Integração com o Facebook</a>, a recomendação é que você realize a Integração com a app <i>Facebook Business Extension e Conversions API</i>. Isso vai permitir que você disponha de serviços aprimorados e novas funcionalidades. 
-</div>
+>⚠️ Mesmo que você já tenha configurado a [Integração com o Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc), a recomendação é que você realize a Integração com a app <i>Facebook Business Extension e Conversions API</i>. Isso vai permitir que você disponha de serviços aprimorados e novas funcionalidades.
 
 Vale ressaltar que não há interferência entre as duas integrações. Uma vez concluída a integração com a app _Facebook Business Extension e Conversions API_, sua loja passará a acessar todos os serviços disponibilizados pelo Facebook Business Extension.
diff --git a/docs/announcements/pt/new-limits-for-causes-of-benefit.md b/docs/announcements/pt/new-limits-for-causes-of-benefit.md
index 475e06b24..435b2eb43 100644
--- a/docs/announcements/pt/new-limits-for-causes-of-benefit.md
+++ b/docs/announcements/pt/new-limits-for-causes-of-benefit.md
@@ -21,10 +21,9 @@ Uma causa de promoção é qualquer condição que gera uma promoção.
 
 Por exemplo: o lojista pode configurar uma promoção para ser aplicada caso o cliente escolha determinado meio de pagamento. Neste caso, o meio de pagamento é a causa da promoção.
 
-<div class="alert alert-danger">Não é possível salvar uma promoção que desrespeite algum dos limites. Portanto, se atualmente sua loja tem promoções que ultrapassem algum desses limites, fique atento. 
-
-Qualquer alteração em alguma dessas promoções fará com que os novos limites sejam aplicados. Assim, você não conseguirá salvar a promoção usando as configurações anteriores.
-</div>
+>❗ Não é possível salvar uma promoção que desrespeite algum dos limites. Portanto, se atualmente sua loja tem promoções que ultrapassem algum desses limites, fique atento. 
+>
+> Qualquer alteração em alguma dessas promoções fará com que os novos limites sejam aplicados. Assim, você não conseguirá salvar a promoção usando as configurações anteriores.
 
 Seguem abaixo os novos limites para cada causa de promoção:
 
diff --git a/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md b/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md
index 320190f67..d97215d89 100644
--- a/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md
+++ b/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md
@@ -79,8 +79,6 @@ Uma vez que você configure a regra de Divergência de valores, ela passa a vale
 
 Para marketplaces VTEX, marketplaces externos e conectores certificados (parceiros), enquanto a regra de Divergência de valores não for criada, pedidos com erro de divergência de preço são aprovados automaticamente.
 
-<div class="alert alert-warning">
-Para <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a>, enquanto o seller não <a href= "https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configura a regra de Divergência de valores</a>, pedidos com divergência de preço ficam retidos. É possível acompanhá-los no Admin VTEX, em <b>MARKETPLACE > Integrações > Pedidos</b>.
-</div>
+>⚠️ Para <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a>, enquanto o seller não <a href= "https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configura a regra de Divergência de valores</a>, pedidos com divergência de preço ficam retidos. É possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
 
 Se você não quiser que conectores nativos obedeçam à Regra de Divergência de valores, é possível manter o fluxo anterior. Neste caso, [entre em contato com o time de suporte da VTEX](https://support.vtex.com/hc/pt-br/requests).
diff --git a/docs/announcements/pt/new-rules-for-activating-vtex-support.md b/docs/announcements/pt/new-rules-for-activating-vtex-support.md
index 14c1d5b9b..4d379b127 100644
--- a/docs/announcements/pt/new-rules-for-activating-vtex-support.md
+++ b/docs/announcements/pt/new-rules-for-activating-vtex-support.md
@@ -17,7 +17,7 @@ announcementSynopsisPT: 'Para contas no Brasil, agora é essencial ter o recurso
 
 Para contas no Brasil, agora é obrigatório ter o recurso **Open Support Ticket** do produto **VTEX - Support** autorizado em seu perfil de acesso para acionar o suporte VTEX. Um usuário com perfil de acesso *User Administrator - Restricted* precisará configurar essa autorização no [License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete).
 
-<div class="alert alert-info"> Usuários administrativos vinculados ao perfil de acesso <strong>Owner (Admin Super)</strong>  possuem o recurso <em>Open Support Ticket</em>  vinculado automaticamente.</div>
+>ℹ️ Usuários administrativos vinculados ao perfil de acesso **Owner (Admin Super)**  possuem o recurso *Open Support Ticket*  vinculado automaticamente.
 
 ## O que mudou?
 A configuração é válida somente para contas no Brasil e restringe a abertura de tickets de suporte a usuários autorizados. Para realizar a abertura de solicitação ao time de suporte, o usuário precisará ter o recurso *Open Support Ticket* do produto **VTEX - Support** autorizado em seu [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc). 
diff --git a/docs/announcements/pt/new-subscriptions-module.md b/docs/announcements/pt/new-subscriptions-module.md
index 7da275344..b007bc56d 100644
--- a/docs/announcements/pt/new-subscriptions-module.md
+++ b/docs/announcements/pt/new-subscriptions-module.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'O módulo de Assinaturas é a solução da VTEX para pedidos recorrentes na sua loja, e está em constante evolução.'
 ---
 
-<div class="alert alert-info">
-  <p>A atualização só afetará lojas que possuem o módulo Assinaturas. Para lojas que não possuíam essa funcionalidade, nada mudará.</p>
-</div>
+>ℹ️ A atualização só afetará lojas que possuem o módulo Assinaturas. Para lojas que não possuíam essa funcionalidade, nada mudará.
 
 O módulo de Assinaturas é a solução da VTEX para pedidos recorrentes na sua loja, e está em constante evolução. Aprimoramos o módulo para agilizar o desempenho do sistema e entregar funcionalidades novas que melhoram a experiência do consumidor da sua loja. Este artigo detalha todas as mudanças do módulo e o que precisa ser feito na sua loja.
 
@@ -77,6 +75,4 @@ O cálculo da próxima data do ciclo de assinatura mudou. Essa alteração permi
 Lembramos que se sua loja não utiliza as nossas APIs em integrações, não é preciso fazer nenhuma adaptação, a evolução será implementada automaticamente pelo próprio sistema da VTEX. 
 Para lojistas ou parceiros que consumiam a nossa API de Assinaturas, vale destacar que todas as rotas anteriores da API de Assinaturas serão substituídas pelas novas, para refletir a evolução do módulo. Todo o processo de migração será assistido pelo time VTEX, garantindo uma transição suave ao novo módulo. Confira nosso [guia de integração com o novo módulo de Assinaturas](https://developers.vtex.com/vtex-developer-docs/docs/subscriptions-v3-migration-guide). 
 
-<div class="alert alert-info">
-  Solicite a nova interface de Assinaturas pelo <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">suporte</a>. É preciso que a loja esteja de acordo com a instalação do Search of Biggy (<a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>) para a ativação da nova interface.
-  </div>
+>ℹ️ Solicite a nova interface de Assinaturas pelo [suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). É preciso que a loja esteja de acordo com a instalação do Search of Biggy ([Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG)) para a ativação da nova interface.
diff --git a/docs/announcements/pt/new-vtex-shipping-network-performance-page.md b/docs/announcements/pt/new-vtex-shipping-network-performance-page.md
index 34658d2e3..9b35f7cdb 100644
--- a/docs/announcements/pt/new-vtex-shipping-network-performance-page.md
+++ b/docs/announcements/pt/new-vtex-shipping-network-performance-page.md
@@ -41,7 +41,4 @@ Esse processo de atualização será realizado nativamente e nenhuma modificaç
 
 Para entender melhor o funcionamento da performance do VTEX Shipping Network, acesse o artigo [Acompanhamento do desempenho da transportadora](https://help.vtex.com/pt/tutorial/painel-vtex-log--51e8tx1IehiN4ZtURRWU92?&utm_source=autocomplete). 
 
-<div class="alert alert-info">
-VTEX Shipping Network está atualmente disponível somente para o Brasil. Para saber mais sobre a VTEX Shipping Network leia o artigo <a href="https://vtex.com/br-pt/log/">Conheça a VTEX Shipping Network, a solução para entregas da VTEX</a>.
-
-</div>
+>ℹ️ VTEX Shipping Network está atualmente disponível somente para o Brasil. Para saber mais sobre a VTEX Shipping Network leia o artigo [Conheça a VTEX Shipping Network, a solução para entregas da VTEX](https://vtex.com/br-pt/log/).
diff --git a/docs/announcements/pt/new-working-hours-setup-is-now-available-for-carriers.md b/docs/announcements/pt/new-working-hours-setup-is-now-available-for-carriers.md
index c322938f0..5c19fdd97 100644
--- a/docs/announcements/pt/new-working-hours-setup-is-now-available-for-carriers.md
+++ b/docs/announcements/pt/new-working-hours-setup-is-now-available-for-carriers.md
@@ -33,10 +33,6 @@ Para configurar horários de funcionamento para transportadoras, siga os passos
 ## Próximos passos
 Em breve, também será permitida a criação de mais de um horário por dia. Assim, lojas que fecham na hora do almoço, por exemplo, vão poder cadastrar seus horários de pausa. Confira o artigo de configuração do [Horário de Funcionamento das Transportadoras](https://help.vtex.com/pt/tutorial/configurar-horario-de-funcionamento-para-transportadoras--2oGpbInIgdxSWUi3TZjdCS).
 
-<div class="alert alert-info">
-A configuração vem, por default, com todos os dias marcados e com os horários de 00:00 a 23:59 (sempre em horário local).
-</div>
+>ℹ️ A configuração vem, por default, com todos os dias marcados e com os horários de 00:00 a 23:59 (sempre em horário local).
 
-<div class="alert alert-warning">
-Ao usar a opção de horário de funcionamento, não é possível a utilização do horário de corte. Isso quer dizer que você vai precisar escolher qual das configurações faz mais sentido para sua loja.
-</div>
+>⚠️ Ao usar a opção de horário de funcionamento, não é possível a utilização do horário de corte. Isso quer dizer que você vai precisar escolher qual das configurações faz mais sentido para sua loja.
diff --git a/docs/announcements/pt/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md b/docs/announcements/pt/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
index 8a49155ad..50cf34f2c 100644
--- a/docs/announcements/pt/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
+++ b/docs/announcements/pt/now-its-easier-to-sell-the-products-from-your-physical-stores-in.md
@@ -27,9 +27,7 @@ Você já pode oferecer os produtos de toda sua rede de lojas físicas em __mark
 
 A única configuração necessária é a integração da conta principal com o marketplace externo. No momento em que isso for feito, os estoques de todas as contas-franquia vinculadas à principal também serão enviados para o marketplace. Essa é uma nova característica das contas-franquia, que já está ativa para facilitar sua vida na hora integrar sua operação com marketplaces.
 
-<div class="alert alert-warning">
-<strong>A integração automática do estoque das contas-franquia só está disponível por enquanto para marketplaces externos</strong>.
-</div>
+>⚠️ **A integração automática do estoque das contas-franquia só está disponível por enquanto para marketplaces externos**.
 
 ## O que mudou
 
@@ -41,11 +39,9 @@ O Multilevel Omnichannel Inventory foi lançado trazendo um novo aliado para ope
 
 Para saber mais sobre Multilevel Omnichannel Inventory e as mudanças nas APIs do Checkout, acesse [este artigo do Help](https://help.vtex.com/pt/business-guides/ofereca-os-produtos-da-sua-rede-de-lojas-fisicas-em-marketplaces-externos--6s64bV8Dqb5QN6sqIfPzcA). 
 
-<div class="alert alert-danger">
-<body>
-  <li>O termo Marketplace Recursivo foi substituído por<b>Multilevel Omnichannel Inventory.</b></li>
-<li>A funcionalidade não permite <a href="https://help.vtex.com/pt/tutorial/veja-como-utilizar-o-change-seller--5TBAwO2kOAMw44uyaaQMQO?">change seller</a>.
-<li>Essa solução é destinada à integração com Marketplaces externos, e não marketplaces que já possuem uma <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">integração nativa VTEX</a>.</li> 
-<li>Leia o artigo <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> e confira as restrições de uso detalhadamente.</li>
-   </body>
-</div>
+>❗ <body>
+>   <li>O termo Marketplace Recursivo foi substituído por**Multilevel Omnichannel Inventory.**</li>
+> <li>A funcionalidade não permite [change seller](https://help.vtex.com/pt/tutorial/veja-como-utilizar-o-change-seller--5TBAwO2kOAMw44uyaaQMQO?).
+> <li>Essa solução é destinada à integração com Marketplaces externos, e não marketplaces que já possuem uma [integração nativa VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex).</li> 
+> <li>Leia o artigo [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) e confira as restrições de uso detalhadamente.</li>
+>    </body>
diff --git a/docs/announcements/pt/old-versions-of-the-vtex-id-script-will-be-deprecated.md b/docs/announcements/pt/old-versions-of-the-vtex-id-script-will-be-deprecated.md
index dbadc2d59..ded55c9cf 100644
--- a/docs/announcements/pt/old-versions-of-the-vtex-id-script-will-be-deprecated.md
+++ b/docs/announcements/pt/old-versions-of-the-vtex-id-script-will-be-deprecated.md
@@ -27,9 +27,9 @@ Para essa mudança acontecer, o script do VTEX ID deverá ser chamado a partir d
 
 Esse novo método traz uma série de vantagens: ainda mais agilidade nas melhorias do script, garantia de que sua loja está usando a versão mais recente e o fim da necessidade de alterar a rota de chamada depois de uma atualização.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong><br>
-Não recomendamos o uso do link com a versão hard-coded, porque em breve vamos suspender o suporte a esse modo de importação do script.
-</div>
+>⚠️ **Atenção:**
+>
+> 
+> Não recomendamos o uso do link com a versão hard-coded, porque em breve vamos suspender o suporte a esse modo de importação do script.
 
 Como essas mudanças impactam diretamente no acesso do cliente à sua loja, recomendamos que você não espere o prazo final e passe a utilizar o novo método de chamada do script do VTEX ID o quanto antes.
diff --git a/docs/announcements/pt/on-vtex-png-to-webp-conversion-is-now-lossless.md b/docs/announcements/pt/on-vtex-png-to-webp-conversion-is-now-lossless.md
index 7893e95f4..fc6cbb77f 100644
--- a/docs/announcements/pt/on-vtex-png-to-webp-conversion-is-now-lossless.md
+++ b/docs/announcements/pt/on-vtex-png-to-webp-conversion-is-now-lossless.md
@@ -19,8 +19,6 @@ As lojas VTEX já contavam com compressão automática de imagens para o formato
 
 Essa conversão só acontece quando sua loja é acessada por um navegador compatível com o formato (por exemplo, o Google Chrome). Em navegadores que não reconhecem o WebP, as imagens continuam a ser renderizadas em seus formatos originais. Lembramos também que a compressão automática não altera o arquivo que você subiu no CMS, mas apenas a forma como esse arquivo é renderizado na tela do seu usuário.
 
-<div class="alert alert-warning">
-A compressão <strong>lossless</strong> é aplicável apenas para arquivos <strong>PNG</strong>. Os arquivos <strong>JPG</strong> continuam a ser comprimidos pelo processo <strong>lossy</strong> (que diminui o tamanho da imagem para aumentar velocidade de carregamento da página). 
-</div>
+>⚠️ A compressão **lossless** é aplicável apenas para arquivos **PNG**. Os arquivos **JPG** continuam a ser comprimidos pelo processo **lossy** (que diminui o tamanho da imagem para aumentar velocidade de carregamento da página).
 
 Essa mudança foi desenvolvida para atender aos usuários que realmente precisam manter uma qualidade mais alta de imagem, mesmo após a conversão para o formato WebP. Para condições normais de uso, os arquivos _.jpg_ continuam a ser a solução mais indicada.
diff --git a/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md b/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md
index 50072af2f..d37d5184d 100644
--- a/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md
+++ b/docs/announcements/pt/onboarding-guide-your-complete-journey-at-vtex.md
@@ -33,9 +33,7 @@ O **Guia de onboarding** é composto por três trilhas, são elas:
 - [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS)
 - [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-<div class="alert alert-info">
-As trilhas tem conteúdos complementares, mas são independentes entre si. Isso significa que você pode explorar o conteúdo com liberdade, sem precisar seguir uma sequência.
-</div>
+>ℹ️ As trilhas tem conteúdos complementares, mas são independentes entre si. Isso significa que você pode explorar o conteúdo com liberdade, sem precisar seguir uma sequência.
 
 Nosso objetivo é que clientes, parceiros e todo o ecossistema VTEX se beneficiem do **Guia de onboarding**. E para manter a relevância do material para diferentes negócios, consideramos uma jornada bastante abrangente. 
 Veja a seguir uma [introdução](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) do que você encontrará no guia.
diff --git a/docs/announcements/pt/order-management-module-feed-v1-and-v2-discontinuation.md b/docs/announcements/pt/order-management-module-feed-v1-and-v2-discontinuation.md
index 383418d95..cce23aa67 100644
--- a/docs/announcements/pt/order-management-module-feed-v1-and-v2-discontinuation.md
+++ b/docs/announcements/pt/order-management-module-feed-v1-and-v2-discontinuation.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: ' O Feed v1 e v2 do módulo de Gerenciamento de pedidos será descontinuado'
 ---
 
-<div class="alert alert-warning">
-A partir do dia 25 de julho de 2019, o Feed v1 e v2 do módulo de Gerenciamento de pedidos será descontinuado. Isso significa que, após esta data, somente será possível usar o Feed v3.
-</div>
+>⚠️ A partir do dia 25 de julho de 2019, o Feed v1 e v2 do módulo de Gerenciamento de pedidos será descontinuado. Isso significa que, após esta data, somente será possível usar o Feed v3.
 
 ## Por que a VTEX está removendo as antigas versões? 
 
diff --git a/docs/announcements/pt/practical-guides-for-b2b-commerce.md b/docs/announcements/pt/practical-guides-for-b2b-commerce.md
index dfc1f7266..b42696204 100644
--- a/docs/announcements/pt/practical-guides-for-b2b-commerce.md
+++ b/docs/announcements/pt/practical-guides-for-b2b-commerce.md
@@ -23,4 +23,4 @@ Para permitir que nossos clientes ofereçam experiências de comércio feitas so
 
 Esta documentação destaca os principais recursos disponíveis na plataforma para os diferentes cenários de ecommerce B2B.
 
-<div class="alert alert-info">Este é apenas o começo! Nos próximos meses, reuniremos todas as documentações relacionadas em uma <a href="https://help.vtex.com/pt/category/b2b--3BQkex089ohYNodLZKKrhi">seção específica para B2B</a> no Help Center da VTEX.</div>
+>ℹ️ Este é apenas o começo! Nos próximos meses, reuniremos todas as documentações relacionadas em uma [seção específica para B2B](https://help.vtex.com/pt/category/b2b--3BQkex089ohYNodLZKKrhi) no Help Center da VTEX.
diff --git a/docs/announcements/pt/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md b/docs/announcements/pt/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
index 6796da1f6..64a07a24b 100644
--- a/docs/announcements/pt/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
+++ b/docs/announcements/pt/provide-your-customers-with-a-better-self-service-experience-with-the-new-my-account.md
@@ -38,9 +38,7 @@ Atualmente, todas as lojas VTEX já têm o novo aplicativo instalado em um ambie
 
 Por acrescentar novos elementos visuais, __o novo My Account demanda a revisão da página junto à agência responsável pela sua customização__. 
 
-<div class="alert alert-danger">
-<strong>A VTEX irá migrar massivamente o novo My Account no dia 03 de julho de 2019.</strong> Portanto, é importante revisar as customizações da página desde já.
-</div>
+>❗ **A VTEX irá migrar massivamente o novo My Account no dia 03 de julho de 2019.** Portanto, é importante revisar as customizações da página desde já.
 
 Para saber mais sobre o novo My Account, acesse os nossos artigos sobre sua __[configuração](https://help.vtex.com/pt/tutorial/configurar-o-my-account--23Ayv5D6b86UBnYfoXqZL1)__ e __[funcionamento](https://help.vtex.com/pt/tutorial/como-funciona-o-my-account--2BQ3GiqhqGJTXsWVuio3Xh)__. 
 
diff --git a/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md b/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
index 5d3bac41c..80ad0cb9b 100644
--- a/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
+++ b/docs/announcements/pt/recaptcha-validation-will-now-follow-orderform-configuration-for-all-requests.md
@@ -64,17 +64,13 @@ Ela poderá seguir o diagrama abaixo para avaliar se uma integração precisa se
 
 Se sua equipe de desenvolvimento identificou que sua integração requer atenção, ela deve seguir as instruções fornecidas no guia para desenvolvedores [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations) (em inglês).
 
-<div class="alert alert-warning">
-Para implementar o reCAPTCHA em um aplicativo mobile nativo, use reCAPTCHA v3. Para outros casos de integração, use reCAPTCHA v2.
-</div>
+>⚠️ Para implementar o reCAPTCHA em um aplicativo mobile nativo, use reCAPTCHA v3. Para outros casos de integração, use reCAPTCHA v2.
 
 Ao usar a chave do reCAPTCHA (`recaptchaKey`) retornada pelo Checkout, o widget reCAPTCHA deve ser renderizado na interface do usuário do seu aplicativo móvel/storefront headless (ou similar), conforme descrito na documentação do [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display?hl=pt-br) ou [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3?hl=pt-br) fornecida pelo Google.
 
 Depois que o comprador tiver concluído o desafio do reCAPTCHA, sua resposta (`recaptchaToken`) deverá ser enviada para a API de Checkout para finalizar a compra, conforme descrito na seção *Final validation* do guia [Implementing reCAPTCHA in integrations](https://developers.vtex.com/docs/guides/implementing-recaptcha-in-integrations#final-validation) (em inglês). Em seguida, a API de Checkout [verificará a resposta do usuário](https://developers.google.com/recaptcha/docs/verify?hl=pt-br) usando o token fornecido.
 
-<div class="alert alert-danger">
-Todas as integrações que usam a API de Checkout para fazer pedidos devem ser revisadas e ajustadas antes de 1 de setembro de 2023. Os aplicativos que não conseguirem renderizar o widget reCAPTCHA e verificar a resposta do usuário não poderão fazer pedidos após essa data.
-</div>
+>❗ Todas as integrações que usam a API de Checkout para fazer pedidos devem ser revisadas e ajustadas antes de 1 de setembro de 2023. Os aplicativos que não conseguirem renderizar o widget reCAPTCHA e verificar a resposta do usuário não poderão fazer pedidos após essa data.
 
 ## Saiba mais
 
diff --git a/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md b/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
index c35e3a9ae..89f6d820e 100644
--- a/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
+++ b/docs/announcements/pt/recurrences-module-will-be-discontinued-migrate-your-data-until-august.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Todas as lojas que ainda a utilizam o módulo Recorrência devem migrar para o módulo Assinaturas até 03 de agosto de 2020'
 ---
 
-<div class="alert alert-info">
-A descontinuação só afetará lojas que ainda possuem o módulo Recorrência. Para lojas que já estão utilizando o módulo Assinaturas, ou que não possuíam essa funcionalidade, nada mudará. 
-</div>
+>ℹ️ A descontinuação só afetará lojas que ainda possuem o módulo Recorrência. Para lojas que já estão utilizando o módulo Assinaturas, ou que não possuíam essa funcionalidade, nada mudará.
 
 O módulo *Recorrência* é uma versão anterior do atual módulo *Assinaturas*. Essa versão será descontinuada, e todas as lojas que ainda a utilizam devem migrar para o módulo *Assinaturas até **03 de agosto de 2020**. 
 
diff --git a/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
index 0bca9e35b..24dca2343 100644
--- a/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
@@ -25,12 +25,18 @@ A partir de __31 de março__, as requisições com paginação na API de busca n
 
 Essa mudança já foi implementada na API, mas até a data limite, ainda será possível realizar a request das duas formas. Já o `resources` no header do response vai continuar funcionando normalmente.
 
-<div class="alert alert-warning">
-<b>Importante:</b><br> 
-- Para funcionar, os parâmetros <b>_from</b> e <b>_to</b> não devem ter uma diferença maior do que <b>50</b>. Isso vai fazer com que sejam exibidos, no máximo, 50 resultados de busca por vez.<br>
-<br>
-- Também há um limite de 2500 itens para uma busca. Por isso, não é possível adicionar um valor maior que 2500 ao parâmetro <b>_to</b>.<br>
-</div>
+>⚠️ **Importante:**
+>
+>  
+> - Para funcionar, os parâmetros **_from** e **_to** não devem ter uma diferença maior do que **50**. Isso vai fazer com que sejam exibidos, no máximo, 50 resultados de busca por vez.
+>
+> 
+>
+>
+> 
+> - Também há um limite de 2500 itens para uma busca. Por isso, não é possível adicionar um valor maior que 2500 ao parâmetro **_to**.
+>
+> 
 
 Para saber todos os detalhes do funcionamento das requisições de paginação na API de busca, acesse este [documento](https://developers.vtex.com/docs/api-reference/search-api).
 
diff --git a/docs/announcements/pt/search-resolve-hides-number-product-stock.md b/docs/announcements/pt/search-resolve-hides-number-product-stock.md
index 0812fe0bf..62f8ef310 100644
--- a/docs/announcements/pt/search-resolve-hides-number-product-stock.md
+++ b/docs/announcements/pt/search-resolve-hides-number-product-stock.md
@@ -35,6 +35,4 @@ Essa atualização é automática, não é preciso realizar nenhuma ação.
 
 Caso você utilize esse dado na sua loja – para indicar as últimas unidades disponíveis de um produto, por exemplo – você precisa entrar em contato com o [nosso Suporte](https://support.vtex.com/hc/pt-br/requests) para continuar a exibir essa informação.
 
-<div class="alert alert-warning">
-  <p>É importante ressaltar que, caso a loja decida exibir a quantidade de produtos em estoque, essa informação será pública e poderá ser acessada pelo <a href="https://github.com/vtex-apps/search-graphql">VTEX Search GraphQL</a>.</p>
-</div>
+>⚠️ É importante ressaltar que, caso a loja decida exibir a quantidade de produtos em estoque, essa informação será pública e poderá ser acessada pelo [VTEX Search GraphQL](https://github.com/vtex-apps/search-graphql).
diff --git a/docs/announcements/pt/security-improvements-to-checkout-cookies.md b/docs/announcements/pt/security-improvements-to-checkout-cookies.md
index b8fc145f6..7862e90ea 100644
--- a/docs/announcements/pt/security-improvements-to-checkout-cookies.md
+++ b/docs/announcements/pt/security-improvements-to-checkout-cookies.md
@@ -57,7 +57,5 @@ Caso encontre algum erro durante a realização dos testes operacionais no ambie
 
 Após verificar as configurações da loja, execute novamente o teste em ambiente Beta.
 
-<div class="alert alert-warning">
-A partir de 13 de Fevereiro de 2023, as lojas que não estiverem devidamente configuradas poderão não conseguir operar o Checkout corretamente.
-</div>
+>⚠️ A partir de 13 de Fevereiro de 2023, as lojas que não estiverem devidamente configuradas poderão não conseguir operar o Checkout corretamente.
 
diff --git a/docs/announcements/pt/service-worker-files-can-now-operate-at-full-capacity.md b/docs/announcements/pt/service-worker-files-can-now-operate-at-full-capacity.md
index ad7967980..6c1c89501 100644
--- a/docs/announcements/pt/service-worker-files-can-now-operate-at-full-capacity.md
+++ b/docs/announcements/pt/service-worker-files-can-now-operate-at-full-capacity.md
@@ -19,9 +19,9 @@ O __Service Worker__ agora pode interceptar todos os requests da sua loja VTEX.
 
 Na prática, a atualização das permissões do __Service Worker__ amplia as possibilidades da sua loja, sendo a maior delas poder operar como PWA (Progressive Web App). Essa solução permite que o usuário acesse um site como faz com um aplicativo, mas sem precisar baixar nada. Ele só precisa salvar o site na tela de início do smartphone para navegar, sem nem precisar estar conectado à internet para ver o conteúdo.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong><br>
-A plataforma VTEX <strong>não</strong> possui features nativas para transformar sua loja em PWA. Ela apenas oferece as condições para que essa implementação seja feita.
-</div>
+>⚠️ **Atenção:**
+>
+> 
+> A plataforma VTEX **não** possui features nativas para transformar sua loja em PWA. Ela apenas oferece as condições para que essa implementação seja feita.
 
 Para saber como instalar o __Service Worker__ na sua loja, leia [este artigo do Help](/pt/tutorial/como-instalar-um-service-worker).
diff --git a/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md b/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md
index c99879cb1..9897bd960 100644
--- a/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md
+++ b/docs/announcements/pt/site-editor-and-media-new-authorization-requirement.md
@@ -28,7 +28,5 @@ Essa alteração visa aumentar a segurança e simplificar o acesso do usuário a
 ## O que precisa ser feito?
 Certifique-se de que os usuários do Site Editor e do Mídia estejam associados ao recurso `CMS GraphQL API` em seus perfis de acesso, seja [criando um novo perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete#creating-a-role) ou editando um existente.
 
-<div class="alert alert-warning">
-  <p> Para gerenciar usuários e perfis de acesso, é necessário ter o recurso <code>Save access profile</code> do produto <bold>License Manager</bold> associado ao perfil de acesso do usuário. Por exemplo, o <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a> é um perfil de acesso predefinido que tem o recurso <code>Save access profile</code> associado a ele.</p>
-</div>
+>⚠️ Para gerenciar usuários e perfis de acesso, é necessário ter o recurso `Save access profile` do produto <bold>License Manager</bold> associado ao perfil de acesso do usuário. Por exemplo, o [User Administrator - RESTRICTED](https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted) é um perfil de acesso predefinido que tem o recurso `Save access profile` associado a ele.
 
diff --git a/docs/announcements/pt/smartcheckout-tm-new-version-already-available-for-all-stores.md b/docs/announcements/pt/smartcheckout-tm-new-version-already-available-for-all-stores.md
index 39230b381..f53c6354f 100644
--- a/docs/announcements/pt/smartcheckout-tm-new-version-already-available-for-all-stores.md
+++ b/docs/announcements/pt/smartcheckout-tm-new-version-already-available-for-all-stores.md
@@ -28,8 +28,6 @@ Veja mais mudanças importantes:
 - Data layer atualizado com informações para serem usadas no Google Enhanced Ecommerce.
 - Possibilidade de edição dos arquivos `checkout5-custom.js` e `orderplaced2-custom.js` para customizar o JavaScript do checkout e da tela de pedido finalizado, repectivamente.
 
-<div class="alert alert-warning">
-Mas lembre-se: a VTEX <strong>não recomenda</strong> a alteração dos arquivos de JavaScript, porque isso pode causar danos de segurança ao seu checkout. Por isso, não nos responsabilizamos por qualquer problema gerado na edição desse código.
-</div>
+>⚠️ Mas lembre-se: a VTEX **não recomenda** a alteração dos arquivos de JavaScript, porque isso pode causar danos de segurança ao seu checkout. Por isso, não nos responsabilizamos por qualquer problema gerado na edição desse código.
 
 Para saber todos os detalhes sobre a nova versão do SmartCheckout™, veja o [artigo do VTEX Help](/pt/tutorial/mudando-para-nova-versao-do-smart-checkout).
diff --git a/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md b/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md
index 5a39d41c8..3b194a531 100644
--- a/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md
+++ b/docs/announcements/pt/the-items-field-will-be-removed-from-the-list-orders-api.md
@@ -23,9 +23,7 @@ Request da API de List Orders: <code>http://{{accountName}}.{{environment}}.com.
 
 Se sua loja usa a API de List Orders e no mapeamento da sua integração é esperado receber o campo `items`, seu time de desenvolvimento precisa __retirá-lo do mapeamento da integração__.
 
-<div class="alert alert-warning">
-O campo <code>items</code> da API de List Orders já está <strong>obsoleto</strong> há bastante tempo. Ele não tem serventia alguma atualmente, e por isso sua loja não deveria considerá-lo em suas integrações. Para pegar itens de pedidos, sua loja deve usar a <a href="http://help.vtex.com/pt/tutorial/como-funciona-o-feed-do-oms">API do Feed</a>.
-</div>
+>⚠️ O campo `items` da API de List Orders já está **obsoleto** há bastante tempo. Ele não tem serventia alguma atualmente, e por isso sua loja não deveria considerá-lo em suas integrações. Para pegar itens de pedidos, sua loja deve usar a [API do Feed](http://help.vtex.com/pt/tutorial/como-funciona-o-feed-do-oms).
 
 É importante lembrar que __a API de List Orders continua funcionando normalmente__. Apenas o campo `items` será excluído.
 
@@ -35,13 +33,9 @@ A retirada desse campo vai aumentar consideravelmente a estabilidade e a perform
 
 Por isso, é crucial retirá-lo da integração.
 
-<div class="alert alert-info">
-<strong>Atenção:</strong> esta mudança somente impacta as integrações que dependem da entrega do campo `items` pela API do List Orders.
-</div>
+>ℹ️ **Atenção:** esta mudança somente impacta as integrações que dependem da entrega do campo `items` pela API do List Orders.
 
-<div class="alert alert-info">
-Esta mudança <strong>não</strong> afeta a API de Get Order. Nela, o campo <code>items</code> continua existindo e sendo atualizado normalmente.
-</div>
+>ℹ️ Esta mudança **não** afeta a API de Get Order. Nela, o campo `items` continua existindo e sendo atualizado normalmente.
 
 <div class="alert">
 Request da API de Get Order: <code>http://{{accountName}}.{{environment}}.com.br/api/oms/pvt/orders/{{orderId}}</code>
diff --git a/docs/announcements/pt/the-new-admin-is-already-being-deployed-to-all-stores.md b/docs/announcements/pt/the-new-admin-is-already-being-deployed-to-all-stores.md
index 783719e35..92f3c3722 100644
--- a/docs/announcements/pt/the-new-admin-is-already-being-deployed-to-all-stores.md
+++ b/docs/announcements/pt/the-new-admin-is-already-being-deployed-to-all-stores.md
@@ -25,6 +25,4 @@ Mas fique tranquilo: essa migração não vai impactar sua rotina diária, já q
 
 Você pode sair na frente e acessar o __novo Admin__ usando a url `https://{AccountName}.myvtex.com/admin`, substituindo _{AccountName}_ pelo account name da sua loja.
 
-<div class="alert alert-warning">
-Os módulos de legado (Catálogo, Master Data e CMS) continuam sendo direcionados para seus ambientes externos.
-</div>
+>⚠️ Os módulos de legado (Catálogo, Master Data e CMS) continuam sendo direcionados para seus ambientes externos.
diff --git a/docs/announcements/pt/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md b/docs/announcements/pt/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
index ec8dce8cb..7c701bd5e 100644
--- a/docs/announcements/pt/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
+++ b/docs/announcements/pt/the-new-oms-report-allows-you-to-export-up-to-5000-orders.md
@@ -31,6 +31,4 @@ O comportamento do módulo permanece o mesmo desde a última mudança: se o filt
 ## Como exportar mais de 5 mil pedidos
 Você pode continuar exportando mais do que 5 mil pedidos usando as APIs de gerenciamento de pedidos (antigo OMS): [Get Order](https://developers.vtex.com/reference/orders#getorder) e [Get Feed Order Status](https://developers.vtex.com/reference/note).
 
-<div class="alert alert-warning">
-<strong>Mas lembre-se:</strong> para funcionar, é necessário que você <strong>crie um range de data/hora que inclua, no máximo, 5 mil pedidos</strong>. Com o range definido e o limite respeitado, você vai poder chamar a API quantas vezes for necessário.
-</div>
+>⚠️ **Mas lembre-se:** para funcionar, é necessário que você **crie um range de data/hora que inclua, no máximo, 5 mil pedidos**. Com o range definido e o limite respeitado, você vai poder chamar a API quantas vezes for necessário.
diff --git a/docs/announcements/pt/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md b/docs/announcements/pt/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
index cd4ce72b5..d45e04d05 100644
--- a/docs/announcements/pt/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
+++ b/docs/announcements/pt/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
@@ -19,9 +19,11 @@ A partir do dia __27 de abril de 2020__, a UI do Checkout da VTEX receberá uma
 
 Essa mudança tem por objetivo atender às leis de proteção de dados, mantendo sua loja em acordo com as recentes alterações na legislação sobre o tema.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> se atualmente sua loja realiza alguma customização do Checkout VTEX que altera o comportamento da flag de newsletter (por exemplo, desmarcando a flag via script), a alteração que estamos anunciando pode afetar o comportamento esperado. Nos casos em que atualmente a customização via script desmarca a flag, por exemplo, pode ser que agora ela passe a fazer justamente o contrário, marcando a flag.<br><br>Portanto, caso sua loja tenha implementado alguma customização que altere o comportamento padrão da flag de newsletter, é importante garantir que sua equipe de desenvolvimento fique ciente da mudança e realize ajustes, caso necessário.
-</div>
+>⚠️ **Atenção:** se atualmente sua loja realiza alguma customização do Checkout VTEX que altera o comportamento da flag de newsletter (por exemplo, desmarcando a flag via script), a alteração que estamos anunciando pode afetar o comportamento esperado. Nos casos em que atualmente a customização via script desmarca a flag, por exemplo, pode ser que agora ela passe a fazer justamente o contrário, marcando a flag.
+>
+> 
+>
+> Portanto, caso sua loja tenha implementado alguma customização que altere o comportamento padrão da flag de newsletter, é importante garantir que sua equipe de desenvolvimento fique ciente da mudança e realize ajustes, caso necessário.
 
 - __Data e horário da mudança__: 27 de abril de 2020, às 11h (Brazil Time).
 - __O que você precisa fazer__: se sua loja customiza a flag de newsletter do Checkout (e apenas neste caso), seu time de desenvolvimento deve checar se a mudança impactará o comportamento da flag.
diff --git a/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md b/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md
index 843e49eb1..ce55351b2 100644
--- a/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md
+++ b/docs/announcements/pt/the-offer-management-module-will-be-discontinued.md
@@ -28,7 +28,5 @@ Permanece disponível as funcionalidades de [Moderação](https://help.vtex.com/
 
 Essa atualização é automática, não é necessário realizar nenhuma ação. A partir da data indicada acima o módulo será completamente descontinuado de todos os Admin VTEX.
 
-<div class="alert alert-info">
-Em breve teremos um módulo substituto para o Gerenciador de anúncios, acompanhe as novidades no <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
-</div>
+>ℹ️ Em breve teremos um módulo substituto para o Gerenciador de anúncios, acompanhe as novidades no [Developer portal na página de release notes](https://developers.vtex.com/updates/release-notes) e [VTEX Help Center na página de novidades](https://help.vtex.com/pt/en/announcements).
 
diff --git a/docs/announcements/pt/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md b/docs/announcements/pt/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
index 82130e4be..cc70d1654 100644
--- a/docs/announcements/pt/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
+++ b/docs/announcements/pt/the-owner-admin-super-user-role-no-longer-has-permission-to-create-users.md
@@ -59,9 +59,7 @@ Caso deseje que algum usuário da sua loja possa realizar as ações associadas
 
 Chaves de aplicação com o perfil de acesso **Owner (Admin Super)** não receberão o perfil **User Administrator - RESTRICTED** automaticamente. Portanto, caso deseje que alguma chave de aplicação possa realizar as ações associadas ao recurso **Save user** citadas acima, você deverá garantir que esta chave tenha o perfil de acesso **User Administrator - RESTRICTED** ou criar um [perfil de acesso customizado](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#tipos-de-perfis) que inclua o recurso **Save user**.
 
-<div class="alert alert-warning">
-Note que, com as mudanças descritas acima, chaves de aplicação não têm mais o recurso <b>Save user</b>, então um usuário com este recurso deverá concedê-lo, caso seja necessário.
-</div>
+>⚠️ Note que, com as mudanças descritas acima, chaves de aplicação não têm mais o recurso **Save user**, então um usuário com este recurso deverá concedê-lo, caso seja necessário.
 
 ## Como proteger as chaves da sua loja?
 
diff --git a/docs/announcements/pt/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md b/docs/announcements/pt/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
index f10687c3d..d7cf55eb7 100644
--- a/docs/announcements/pt/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
+++ b/docs/announcements/pt/the-term-access-profile-has-been-replaced-by-the-term-role-in-your-admin-ui.md
@@ -15,6 +15,4 @@ announcementImageID: ''
 announcementSynopsisPT: 'O termo “Access Profile” foi substituído pelo termo “Role” para melhor refletir o conceito a que se refere.'
 ---
 
-<div class="alert alert-warning">
-Esta mudança se refere a um termo usado apenas na língua inglesa. Verifique este anúncio em inglês para mais informações.
-</div>
+>⚠️ Esta mudança se refere a um termo usado apenas na língua inglesa. Verifique este anúncio em inglês para mais informações.
diff --git a/docs/announcements/pt/this-new-api-helps-marketplaces-avoid-losing-sales.md b/docs/announcements/pt/this-new-api-helps-marketplaces-avoid-losing-sales.md
index fce9909fb..a0df2f13e 100644
--- a/docs/announcements/pt/this-new-api-helps-marketplaces-avoid-losing-sales.md
+++ b/docs/announcements/pt/this-new-api-helps-marketplaces-avoid-losing-sales.md
@@ -19,10 +19,10 @@ Já está disponível em stable uma API que vai trazer ainda mais autonomia para
 
 Com esse novo status, os marketplaces podem recuperar vendas que seriam perdidas no caso de um seller cancelar o pedido de um cliente. Agora, eles terão tempo para encontrar um outro seller com o estoque necessário para atender o pedido e, assim, garantir a conversão.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong><br> 
-O novo status só estará disponível quando <strong>Marketplace</strong> e <strong>Seller</strong> forem VTEX. E, se não houver seller VTEX com estoque disponível, a compra do cliente não passa pelo novo status e é cancelada automaticamente.
-</div>
+>⚠️ **Atenção:**
+>
+>  
+> O novo status só estará disponível quando **Marketplace** e **Seller** forem VTEX. E, se não houver seller VTEX com estoque disponível, a compra do cliente não passa pelo novo status e é cancelada automaticamente.
 
 A nova funcionalidade também permite que o marketplace tenha mais controle sobre a qualidade da entrega dos produtos, uma vez que também será possível trocar de seller quando o pedido estiver com os status "__Pagamento pendente__" e "__Aguardando autorização__". Outro caso de uso é para lojas que possuem franqueados (sellers white label): agora, elas também vão poder alterar o franqueado responsável por um pedido. 
 
diff --git a/docs/announcements/pt/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md b/docs/announcements/pt/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
index f54c467c6..335d09e5a 100644
--- a/docs/announcements/pt/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
+++ b/docs/announcements/pt/urgente-migracao-do-sistema-de-pedidos-para-manter-sua-operacao-funcionando.md
@@ -19,9 +19,7 @@ No dia 13/06/19, [anunciamos a descontinuação das APIs de Feed V1 e V2](/annou
 
 __Mudamos a data final de migração e as lojas que ainda não se adaptaram à nova versão têm até o dia 12/08 para adequar sua integração__. Após esta data, não será mais possível consumir dados de pedidos utilizando as versões anteriores desta API, impactando seu processo de entrega de pedidos.
 
-<div class="alert alert-info">
-As lojas que já estiverem usando a V3 da API de Feed não precisam realizar nehuma ação.
-</div>
+>ℹ️ As lojas que já estiverem usando a V3 da API de Feed não precisam realizar nehuma ação.
 
 É muito importante que essa migração seja feita o quanto antes para que sua operação não fique em risco. Siga as instruções a seguir e solicite ao responsável pela sua integração que execute as mudanças necessárias.
 
diff --git a/docs/announcements/pt/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md b/docs/announcements/pt/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
index bb7439037..6b7a5d7e6 100644
--- a/docs/announcements/pt/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
+++ b/docs/announcements/pt/v2-of-checkout-and-fulfillment-api-is-already-in-beta-migration-will-be-completed-on-may-23.md
@@ -15,21 +15,19 @@ announcementImageID: ''
 announcementSynopsisPT: 'A V2 traz uma série de melhorias em relação à versão anterior e remove alguns campos e rotas que já estavam obsoletos.'
 ---
 
-<div class="alert alert-danger">
-A migração para a v2 da API de Checkout e Fulfillment já foi finalizada em <strong>23/05/2018</strong>
-</div>
+>❗ A migração para a v2 da API de Checkout e Fulfillment já foi finalizada em **23/05/2018**
 
-<div class="alert alert-warning">
-O prazo foi alterado de <strong>21/05</strong> para <strong>23/05</strong> (2 dias) devido à necessidade de testes complementares.
-</div>
+>⚠️ O prazo foi alterado de **21/05** para **23/05** (2 dias) devido à necessidade de testes complementares.
 
 Já está em beta a Versão 2 da API de Checkout e Fulfillment. E, a partir de __23 de maio__, ela será aplicada para todas as lojas. A V2 traz uma série de melhorias em relação à versão anterior e remove alguns campos e rotas que já estavam obsoletos. 
 
-<div class="alert alert-warning">
-<strong>Atenção</strong><br>
-Recomendamos que você faça todos os testes para avaliar os impactos e adaptar suas integrações e customizações antes do prazo final.<br> 
-Assim, quando realizarmos a migração para a nova versão da API, sua loja vai ter uma transição tranquila.
-</div>
+>⚠️ **Atenção**
+>
+> 
+> Recomendamos que você faça todos os testes para avaliar os impactos e adaptar suas integrações e customizações antes do prazo final.
+>
+>  
+> Assim, quando realizarmos a migração para a nova versão da API, sua loja vai ter uma transição tranquila.
 
 Confira abaixo tudo o que muda com a nova versão da API de Checkout e Fulfillment (e o que está em beta ou em stable):
 
diff --git a/docs/announcements/pt/vtex-announces-its-integration-with-amazon.md b/docs/announcements/pt/vtex-announces-its-integration-with-amazon.md
index 4226197af..4d3757cd3 100644
--- a/docs/announcements/pt/vtex-announces-its-integration-with-amazon.md
+++ b/docs/announcements/pt/vtex-announces-its-integration-with-amazon.md
@@ -19,7 +19,5 @@ A VTEX anuncia sua nova integração com a Amazon. Agora nossos clientes já pod
 
 Num primeiro momento, a integração estará disponível para as categorias Eletrônicos, Livros e Games. Para saber mais detalhes sobre a integração, veja nosso [tutorial](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP "tutorial").
 
-<div class="alert alert-warning">
-Esta integração está disponível para Brasil e Estados Unidos.
-</div>
+>⚠️ Esta integração está disponível para Brasil e Estados Unidos.
 
diff --git a/docs/announcements/pt/vtex-login-now-features-recaptcha.md b/docs/announcements/pt/vtex-login-now-features-recaptcha.md
index e86ca26c0..28ee3e979 100644
--- a/docs/announcements/pt/vtex-login-now-features-recaptcha.md
+++ b/docs/announcements/pt/vtex-login-now-features-recaptcha.md
@@ -25,7 +25,6 @@ Isto significa que o pedido de confirmação pode ou não aparecer, dependendo d
 
 Com essa mudança, a VTEX deixa de impedir o acesso de um usuário após 3 tentativas incorretas, uma vez que a segurança fica garantida pelo reCAPTCHA.
 
-<div class="alert alert-info">Atualmente, usamos reCAPTCHA apenas no fluxo de login do admin.</div>
+>ℹ️ Atualmente, usamos reCAPTCHA apenas no fluxo de login do admin.
 
-<div class="alert alert-warning">
-Devido a esta mudança, <a href="https://help.vtex.com/pt/announcements/integracoes-com-apis-vtex-agora-precisam-de-autenticacao-por-token--7AdnXDH7AkYmuEUmmis8Es">não é mais permitido o uso de e-mail e senha para integrações</a>.</div>
+>⚠️ Devido a esta mudança, [não é mais permitido o uso de e-mail e senha para integrações](https://help.vtex.com/pt/announcements/integracoes-com-apis-vtex-agora-precisam-de-autenticacao-por-token--7AdnXDH7AkYmuEUmmis8Es).
diff --git a/docs/announcements/pt/vtex-login-now-needs-2-factor-authentication.md b/docs/announcements/pt/vtex-login-now-needs-2-factor-authentication.md
index 7b044f147..67f58c01b 100644
--- a/docs/announcements/pt/vtex-login-now-needs-2-factor-authentication.md
+++ b/docs/announcements/pt/vtex-login-now-needs-2-factor-authentication.md
@@ -17,9 +17,7 @@ announcementSynopsisPT: 'A partir de 16/11, a autenticação de 2 fatores torna-
 
 A partir de 16 de novembro, às 14h (horário do Brasil), a autenticação de 2 fatores (2FA) torna-se __obrigatória para todos os e-mails__ no Admin da VTEX. Se você usa e-mail e senha para logar, habilite o 2FA antes dessa data.
 
-<div class="alert alert-info">
-Veja o artigo sobre <a href="http://help.vtex.com/pt/tutorial/habilitar-login-por-autenticacao-de-2-fatores">como habilitar o 2FA</a>.
-</div>
+>ℹ️ Veja o artigo sobre [como habilitar o 2FA](http://help.vtex.com/pt/tutorial/habilitar-login-por-autenticacao-de-2-fatores).
 
 O 2FA é um método de autenticação que aumenta muito a segurança da sua loja. Porque, no momento do login, além de pedir e-mail e senha, o sistema exige uma chave de acesso gerada por aplicativo ou SMS.
 
diff --git a/docs/announcements/pt/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md b/docs/announcements/pt/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
index f39e42bf3..a4f9ce7e6 100644
--- a/docs/announcements/pt/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
+++ b/docs/announcements/pt/vtexs-integration-with-magazine-luiza-is-already-available-to-all-stores.md
@@ -22,9 +22,7 @@ A partir da parceria com o marketplace, desenvolvemos uma solução que substitu
 ## Como foi a mudança
 No ar desde outubro de 2018, nossa integração com a Magazine Luiza estava disponível apenas para lojistas que ainda não vendiam no marketplace. Em dezembro, iniciamos a migração das lojas que trabalhavam com integrações externas e o processo foi concluído com sucesso.
 
-<div class="alert alert-info">
-A integração com a Magazine Luiza acontece através do sistema da Integra Commerce, que intermedia as informações enviadas pela VTEX e repassa ao marketplace.
-</div>
+>ℹ️ A integração com a Magazine Luiza acontece através do sistema da Integra Commerce, que intermedia as informações enviadas pela VTEX e repassa ao marketplace.
 
 
 ## Integração completa, estável e com todo o suporte VTEX
diff --git a/docs/announcements/pt/web-service-methods-will-be-deprecated.md b/docs/announcements/pt/web-service-methods-will-be-deprecated.md
index 3c11108f8..68a1fe003 100644
--- a/docs/announcements/pt/web-service-methods-will-be-deprecated.md
+++ b/docs/announcements/pt/web-service-methods-will-be-deprecated.md
@@ -17,9 +17,7 @@ announcementSynopsisPT: 'A partir de 28/02/18, o uso de Web Service será descon
 
 A partir do dia __28 de fevereiro__, vamos descontinuar o uso de Web Service para integrações com a VTEX, __à exceção dos métodos do Catálogo__.
 
-<div class="alert alert-warning">
-Vamos manter o funcionamento do Web Service para o Catálogo, enquanto trabalhamos no desenvolvimento das APIs REST desse serviço. Você será informado assim que um cronograma de migração for definido.
-</div>
+>⚠️ Vamos manter o funcionamento do Web Service para o Catálogo, enquanto trabalhamos no desenvolvimento das APIs REST desse serviço. Você será informado assim que um cronograma de migração for definido.
 
 Se sua loja ainda usa algum desses métodos, substitua-os por integrações via API. Caso contrário, a partir de 28 de fevereiro essas integrações deixarão de funcionar.
 
diff --git a/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md b/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
index ec7e449d5..53223f65d 100644
--- a/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
+++ b/docs/announcements/pt/welcome-to-the-redesigned-vtex-admin-new.md
@@ -36,9 +36,7 @@ Embora tenhamos redesenhado o Admin VTEX, as configurações e os dados da sua l
 
 Nenhuma página foi removida do Admin VTEX, mas organizamos o menu de navegação para estar alinhado às páginas mais acessadas e refletir as prioridades da sua operação. Saiba mais sobre a nossa [navegação aprimorada](https://help.vtex.com/pt/tutorial/admin-vtex-comece-aqui--5bBA7QgKuU2wL2Aq11pqAA).
 
-<div class="alert alert-info">
-É possível usar a barra de pesquisa na parte superior do seu Admin VTEX para pesquisar páginas específicas. As páginas que não fazem parte da nossa edição default do Admin VTEX podem ser encontradas em Aplicativos > Apps instalados.  
-</div>
+>ℹ️ É possível usar a barra de pesquisa na parte superior do seu Admin VTEX para pesquisar páginas específicas. As páginas que não fazem parte da nossa edição default do Admin VTEX podem ser encontradas em Aplicativos > Apps instalados.
 
 Além de modificar a organização das páginas, também melhoramos alguns nomes de itens do menu de navegação para ficarem mais consistentes e alinhados com as funcionalidades oferecidas pela VTEX. A tabela abaixo lista as alterações nos nomes das seções.
 
diff --git a/docs/announcements/pt/wordpress-a-powerful-marketing-tool-for-your-store.md b/docs/announcements/pt/wordpress-a-powerful-marketing-tool-for-your-store.md
index 67727b67d..4c495ed8c 100644
--- a/docs/announcements/pt/wordpress-a-powerful-marketing-tool-for-your-store.md
+++ b/docs/announcements/pt/wordpress-a-powerful-marketing-tool-for-your-store.md
@@ -31,7 +31,5 @@ Integrar seu blog/website na loja é fazer uso de uma poderosa ferramenta de mar
 
 Instale o app a partir da [VTEX App Store](https://apps.vtex.com/vtex-wordpress-integration/p) e siga as instruções [desta documentação](https://developers.vtex.com/vtex-developer-docs/docs/vtex-wordpress-integration) para configurar a integração.
 
-<div class="alert alert-info">
-Para utilizar este aplicativo você precisa ter website/blog desenvolvido no WordPress.
-</div>
+>ℹ️ Para utilizar este aplicativo você precisa ter website/blog desenvolvido no WordPress.
 
diff --git a/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md b/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
index 60df2c039..1b170fa6b 100644
--- a/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
+++ b/docs/announcements/pt/you-can-now-restrict-user-access-to-the-settings-screen-on-the-orders.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'Possibilidade de limitar perfis de acesso a tela Configuração'
 ---
 
-<div class="alert alert-warning">
-A partir do dia 25 de junho de 2019, o usuário que não tiver acesso vinculado ao perfil com o produto <code>Checkout</code>  não terá permissão para editar a tela de Configurações do módulo Gerenciamento de Pedidos. 
-</div>
+>⚠️ A partir do dia 25 de junho de 2019, o usuário que não tiver acesso vinculado ao perfil com o produto `Checkout`  não terá permissão para editar a tela de Configurações do módulo Gerenciamento de Pedidos.
 
 Buscando garantir maior segurança, criamos a possibilidade de limitar perfis de acesso a tela de **Configurações** do módulo Gerenciamento de Pedidos, permitindo que somente alguns usuários editem as informações.
 
diff --git a/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
index e3ba3e98a..8607093f2 100644
--- a/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/en/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -14,9 +14,7 @@ locale: en
 legacySlug: como-bloquear-customizacoes-para-investigar-problemas-no-front-end-da-loja
 ---
 
-<div class="alert alert-warning">
-  Tutorial valid only for Legacy CMS Stores.
-</div>
+>⚠️ Tutorial valid only for Legacy CMS Stores.
 
 In this article, you will learn how to find the origin of the problem. The first step is to block front-end customizations. Depending on the website’s response, you will be able to identify whether the problem is in the information that VTEX delivers natively or in your page customization.
 
diff --git a/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md b/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
index dcc9eb361..c90852490 100644
--- a/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
+++ b/docs/faq/en/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
@@ -30,6 +30,4 @@ Your request will enter a queue, which can be followed through the OMS. When you
 
 To get the information about your best selling products, after downloading the spreadsheet, you must make the account between the columns __AH (Quantity_SKU) __, which says the amount of SKU that was sold, and the column __AI (ID_SKU) __, which refers to the SKU in question.
 
-<div class="alert alert-danger">
-Exports can be made within a 31-day time frame.
-</div>
+>❗ Exports can be made within a 31-day time frame.
diff --git a/docs/faq/en/can-i-order-my-products-as-i-want.md b/docs/faq/en/can-i-order-my-products-as-i-want.md
index 47e462ef8..043840952 100644
--- a/docs/faq/en/can-i-order-my-products-as-i-want.md
+++ b/docs/faq/en/can-i-order-my-products-as-i-want.md
@@ -36,6 +36,4 @@ The parameters are as follows:
 
 For example: `http://www.{AccountName}.com/{departament}/{category}?O=OrderByPriceASC`
 
-<div class="alert alert-warning">
-<strong>You can only use one product order parameter at a time.</strong> Therefore, you have to choose the one that best suits your store's needs (remember that parameters can be changed at will).
-</div>
+>⚠️ **You can only use one product order parameter at a time.** Therefore, you have to choose the one that best suits your store's needs (remember that parameters can be changed at will).
diff --git a/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
index 5c1249dd1..406f09000 100644
--- a/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/en/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -49,9 +49,7 @@ When the payment is settled, the system will send information about recipients a
 
 No. Split payments support the change seller feature only when made with one or two credit cards. This is because most of the payment providers settle the value immediately for payment methods such as “boleto” (popular Brazilian off-line payment method) or debit card. Therefore, we cannot offer a time window to change sellers in this case. 
 
-<div class="alert alert-warning">
-  If you make an attempt to change sellers with payment methods other than credit card, you will receive the following API call error message: "Error when updating additional data for transaction = 722726D8B04C4AAFB1EC945076FD2913. Payout split was already done".
-  </div>
+>⚠️ If you make an attempt to change sellers with payment methods other than credit card, you will receive the following API call error message: "Error when updating additional data for transaction = 722726D8B04C4AAFB1EC945076FD2913. Payout split was already done".
 
 ### Is it possible to partially or fully refund an order?
 
@@ -78,9 +76,7 @@ However, it was necessary to change the seller. After the change, the order was
 
 On the Partner02 dashboard, you can see a discount of BRL 0.28 identified as "Coinshop Discount". Although the price advertised by the seller Partner02 was BRL 0.30, it will receive only BRL 0.02.
 
-<div class="alert alert-info">
-  It is worth mentioning that in this case, it was possible to change sellers because the total cost difference was no more than BRL 0.30. If the difference was higher than BRL 0.31, it would not be possible to change sellers.
-  </div>
+>ℹ️ It is worth mentioning that in this case, it was possible to change sellers because the total cost difference was no more than BRL 0.30. If the difference was higher than BRL 0.31, it would not be possible to change sellers.
 
 After the order invoicing, the system settled BRL 5.02 and performed the split payment.
 
diff --git a/docs/faq/en/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md b/docs/faq/en/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
index 6e7a0b8d6..8351d61be 100644
--- a/docs/faq/en/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/en/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
@@ -20,9 +20,7 @@ This error occurs when the imported freight spreadsheet __has a tab outside the
 
 Generally, the tab outside default format does not contain any important information. To solve the problem, __delete the tabs outside default format__, check if the tabs within default format have the correct information and try the upload again.
 
-<div class="alert alert-warning">
-In case the spreadsheet is over 10 MB, you’ll need to compact it in .zip format. The .zip archive should have less than 10 MB. Otherwise, the upload won’t work.
-</div>
+>⚠️ In case the spreadsheet is over 10 MB, you’ll need to compact it in .zip format. The .zip archive should have less than 10 MB. Otherwise, the upload won’t work.
 
 ## Obtain spreadsheet with default format
 
diff --git a/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md b/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
index a640886f3..bb16c63e4 100644
--- a/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/en/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
@@ -20,7 +20,5 @@ This error occurs when the freight spreadsheet is imported with the __.xlsx__ ex
 
 To solve the problem, it is necessary to adjust the freight spreadsheet to the __.xls__ extension and [import the freight spreadsheet](http://help.vtex.com/en/tutorial/importing-the-shipping-spreadsheet) again.
 
-<div class="alert alert-warning">
-In case the spreadsheet is over 10 MB, you’ll need to compact it in .zip format. The .zip archive should have less than 10 MB. Otherwise, the upload won’t work.
-</div>
+>⚠️ In case the spreadsheet is over 10 MB, you’ll need to compact it in .zip format. The .zip archive should have less than 10 MB. Otherwise, the upload won’t work.
 
diff --git a/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md b/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
index 64bb90ed8..741fdbc31 100644
--- a/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
+++ b/docs/faq/en/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
@@ -20,9 +20,7 @@ This error occurs when a __column title of the freight spreadsheet__ is written
 
 To solve the problem, it is necessary to adjust the title of the column to the correct name and upload the spreadsheet again.
 
-<div class="alert alert-warning">
-In case the spreadsheet is over 10 MB, you’ll need to compact it in .zip format. The .zip archive should have less than 10 MB. Otherwise, the upload won’t work.
-</div>
+>⚠️ In case the spreadsheet is over 10 MB, you’ll need to compact it in .zip format. The .zip archive should have less than 10 MB. Otherwise, the upload won’t work.
 
 ## Obtain the correct names of the column titles
 
diff --git a/docs/faq/en/fix-redirect-error-in-pagseguro.md b/docs/faq/en/fix-redirect-error-in-pagseguro.md
index 2df023ffd..009202d9e 100644
--- a/docs/faq/en/fix-redirect-error-in-pagseguro.md
+++ b/docs/faq/en/fix-redirect-error-in-pagseguro.md
@@ -14,7 +14,7 @@ locale: en
 legacySlug: fix-redirect-error-in-pagseguro
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 If you are having "redirect problems" using PagSeguro, it's likely that PagSeguro's *redirect* is configured incorrectly.
 
diff --git a/docs/faq/en/how-to-add-more-agents-in-a-whatsapp-link.md b/docs/faq/en/how-to-add-more-agents-in-a-whatsapp-link.md
index 771633535..ff7a2f788 100644
--- a/docs/faq/en/how-to-add-more-agents-in-a-whatsapp-link.md
+++ b/docs/faq/en/how-to-add-more-agents-in-a-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: how-to-add-more-agents-in-a-whatsapp-link
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/how-to-configure-a-new-trade-policy.md b/docs/faq/en/how-to-configure-a-new-trade-policy.md
index 12c142e74..4b9cb499d 100644
--- a/docs/faq/en/how-to-configure-a-new-trade-policy.md
+++ b/docs/faq/en/how-to-configure-a-new-trade-policy.md
@@ -24,6 +24,4 @@ Let's say, for example, that you have a substore specific for B2B sales and you
 
 To add more trade policies, you have to get in touch with the Sales Operations area at: __sales-operations@vtex.com__.
 
-<div class="alert alert-warning">
-Adding trade policies that are linked to certified marketplaces or other VTEX stores is free of monthly fees.
-</div>
+>⚠️ Adding trade policies that are linked to certified marketplaces or other VTEX stores is free of monthly fees.
diff --git a/docs/faq/en/how-to-configure-a-top-level-store-in-the-integration-with-mercado-livre.md b/docs/faq/en/how-to-configure-a-top-level-store-in-the-integration-with-mercado-livre.md
index 4b709356c..9b282df37 100644
--- a/docs/faq/en/how-to-configure-a-top-level-store-in-the-integration-with-mercado-livre.md
+++ b/docs/faq/en/how-to-configure-a-top-level-store-in-the-integration-with-mercado-livre.md
@@ -14,4 +14,4 @@ locale: en
 legacySlug: how-to-configure-a-top-level-store-in-the-integration-with-mercado-livre
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/faq/en/how-to-edit-a-whatsapp-link.md b/docs/faq/en/how-to-edit-a-whatsapp-link.md
index 82b862c27..7de2027ab 100644
--- a/docs/faq/en/how-to-edit-a-whatsapp-link.md
+++ b/docs/faq/en/how-to-edit-a-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: how-to-edit-a-whatsapp-link
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/how-to-find-facebook-pixel.md b/docs/faq/en/how-to-find-facebook-pixel.md
index 40bf0d688..45bf13522 100644
--- a/docs/faq/en/how-to-find-facebook-pixel.md
+++ b/docs/faq/en/how-to-find-facebook-pixel.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: how-to-find-facebook-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/how-to-find-google-analytics-pixel.md b/docs/faq/en/how-to-find-google-analytics-pixel.md
index d93abc3dc..4700149e5 100644
--- a/docs/faq/en/how-to-find-google-analytics-pixel.md
+++ b/docs/faq/en/how-to-find-google-analytics-pixel.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: how-to-find-google-analytics-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/how-to-find-google-tag-manager-pixel.md b/docs/faq/en/how-to-find-google-tag-manager-pixel.md
index d9fcd7849..fcb7385e0 100644
--- a/docs/faq/en/how-to-find-google-tag-manager-pixel.md
+++ b/docs/faq/en/how-to-find-google-tag-manager-pixel.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: how-to-find-google-tag-manager-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/how-to-find-linkedin-pixel.md b/docs/faq/en/how-to-find-linkedin-pixel.md
index 553b64ade..81b71d90b 100644
--- a/docs/faq/en/how-to-find-linkedin-pixel.md
+++ b/docs/faq/en/how-to-find-linkedin-pixel.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: how-to-find-linkedin-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/improvements-in-the-checkout-api-part-1.md b/docs/faq/en/improvements-in-the-checkout-api-part-1.md
index 3491d88bf..8b2608940 100644
--- a/docs/faq/en/improvements-in-the-checkout-api-part-1.md
+++ b/docs/faq/en/improvements-in-the-checkout-api-part-1.md
@@ -18,13 +18,9 @@ Our development team is constantly improving the performance of our APIs. This m
 
 In this article, we'll list all parts of the Checkout V2 API that are not likely to be part of the next release.
 
-<div class="alert alert-warning">
-This article will be in permanent update until the release of the Checkout API V3. However, you should be aware of changes not described here that may be implemented in V3.
-</div>
+>⚠️ This article will be in permanent update until the release of the Checkout API V3. However, you should be aware of changes not described here that may be implemented in V3.
 
-<div class="alert alert-warning">
-The purpose of this article is to allow you to begin the process of updating your store integrations and customizations, considering the new solutions offered by the system. Therefore, we recommend that you stay tuned and do not leave changes to the last minute.
-</div>
+>⚠️ The purpose of this article is to allow you to begin the process of updating your store integrations and customizations, considering the new solutions offered by the system. Therefore, we recommend that you stay tuned and do not leave changes to the last minute.
 
 
 ## Address in the cart and in the order
diff --git a/docs/faq/en/is-it-possible-to-change-data-in-a-master-workspace.md b/docs/faq/en/is-it-possible-to-change-data-in-a-master-workspace.md
index e7f2498be..561523c0a 100644
--- a/docs/faq/en/is-it-possible-to-change-data-in-a-master-workspace.md
+++ b/docs/faq/en/is-it-possible-to-change-data-in-a-master-workspace.md
@@ -22,6 +22,4 @@ You can not make changes to this workspace.
 
 Instead, work the new code on another workspace, then change the status of that workspace to `production true` and then promote it.
 
-<div class="alert alert-warning">
-You can not make changes to a master workspace.
-</div>
+>⚠️ You can not make changes to a master workspace.
diff --git a/docs/faq/en/locate-the-google-ads-pixel.md b/docs/faq/en/locate-the-google-ads-pixel.md
index 12447ee1e..c5c1f66f8 100644
--- a/docs/faq/en/locate-the-google-ads-pixel.md
+++ b/docs/faq/en/locate-the-google-ads-pixel.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: locate-the-google-ads-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/my-trial-is-over-now-what.md b/docs/faq/en/my-trial-is-over-now-what.md
index ded6c35fc..073fdb2f7 100644
--- a/docs/faq/en/my-trial-is-over-now-what.md
+++ b/docs/faq/en/my-trial-is-over-now-what.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: my-trial-is-over-now-what
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
index dc360a4be..be3941007 100644
--- a/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/en/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -29,6 +29,4 @@ When the ERP queries and enters this order in your base, it has to inform VTEX t
 
 > You must have a [OMS - Full access role](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") in order to perform this action.
 
-<div class="alert alert-warning">
-<p>If the order is moved manually from the <b>Start handling</b> status, it will not be possible to move the order down to the ERP afterwards.</p>
-</div>
+>⚠️ If the order is moved manually from the **Start handling** status, it will not be possible to move the order down to the ERP afterwards.
diff --git a/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
index 0ae2997f3..00894ef89 100644
--- a/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
+++ b/docs/faq/en/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -25,6 +25,4 @@ When the ERP queries and enters this order in your base, it has to inform VTEX t
 
 > You must have a [OMS - Full access role](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") to be able to perform this action.
 
-<div class="alert alert-warning">
-<p>If the order is moved manually from the <b>Start handling</b> status, it will not be possible to move the order down to the ERP afterwards.</p>
-</div>
+>⚠️ If the order is moved manually from the **Start handling** status, it will not be possible to move the order down to the ERP afterwards.
diff --git a/docs/faq/en/understanding-vtex-email-capture-system.md b/docs/faq/en/understanding-vtex-email-capture-system.md
index 17f72c5ed..aad4892d3 100644
--- a/docs/faq/en/understanding-vtex-email-capture-system.md
+++ b/docs/faq/en/understanding-vtex-email-capture-system.md
@@ -38,17 +38,13 @@ For better understanding, we will present a scenario (divided into 3 steps), whe
 |------------------|------------------|
 | Click on `Go to delivery`. | Checkout prompts RC.JS to transfer email address and cart information to Master Data (via Profile System). |
 
-<div class="alert alert-warning">
-So that the <a href="https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#">abandoned cart</a> function can be used , the user must have filled in the following information: e-mail, name, surname and CPF. The lack of one of these data, makes it impossible to use the abandoned cart.
-</div>
+>⚠️ So that the [abandoned cart](https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#) function can be used , the user must have filled in the following information: e-mail, name, surname and CPF. The lack of one of these data, makes it impossible to use the abandoned cart.
 
 | __User__ | __VTEX Platform__ |
 |------------------|------------------|
 | Fill in the shipping and payment information. | The Checkout orderForm becomes an order and is transmitted to the VTEX OMS. The user's complete information (first name, last name, email, cart and all additional information) is transmitted to Master Data. Email capture can take up to 46 minutes to properly reflect in CRM. |
 
-<div class="alert alert-info">
-Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
-</div>
+>ℹ️ Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
 
 ![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/faq/en/utms.md b/docs/faq/en/utms.md
index c268af9f3..5c3417c02 100644
--- a/docs/faq/en/utms.md
+++ b/docs/faq/en/utms.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: utms
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/visa-checkout-orders-do-not-appear-in-my-orders-section.md b/docs/faq/en/visa-checkout-orders-do-not-appear-in-my-orders-section.md
index ca59c3c97..5e288b8b2 100644
--- a/docs/faq/en/visa-checkout-orders-do-not-appear-in-my-orders-section.md
+++ b/docs/faq/en/visa-checkout-orders-do-not-appear-in-my-orders-section.md
@@ -20,6 +20,4 @@ As a result, customers who make a first purchase at the store do not have their
 
 For customers already registered at the store, you can access __My Orders__ section and view all orders placed, including those closed through Visa Checkout.
 
-<div class="alert alert-info">
-The customer email saved in VTEX must be the same as the one used for signing in to Visa Checkout so that orders can be viewed in <strong>My Orders</strong>.
-</div>
+>ℹ️ The customer email saved in VTEX must be the same as the one used for signing in to Visa Checkout so that orders can be viewed in **My Orders**.
diff --git a/docs/faq/en/vtex-support-emea.md b/docs/faq/en/vtex-support-emea.md
index 140086d00..8926e4243 100644
--- a/docs/faq/en/vtex-support-emea.md
+++ b/docs/faq/en/vtex-support-emea.md
@@ -16,7 +16,7 @@ legacySlug: vtex-support-emea
 
 This article presents the availability, SLA, and additional support resources available to customers served by our offices in **Europe, the Middle East, and Africa (EMEA).** For a broader perspective of our global support resources, see: [How does VTEX support work?](https://help.vtex.com/en/faq/how-does-vtex-support-work--3kACEfni4m8Yxa1vnf2ebe)
 
-<div class="alert alert-info">If the Support team identifies that a ticket was opened incorrectly, they will recommend the most appropriate resource to use, and this assessment can be made at any time during the resolution process.</div>
+>ℹ️ If the Support team identifies that a ticket was opened incorrectly, they will recommend the most appropriate resource to use, and this assessment can be made at any time during the resolution process.
 
 ## Availability
 
@@ -75,9 +75,7 @@ viable alternative to overcome the problem.</p>
 
 Keep in mind that our first response time calculation is based on working hours. The criteria for ticket urgency are defined in the section below.  
 
-<div class="alert alert-warning">
-Emergency support will be available <b>exclusively</b> for Urgent requests and provided via <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Zendesk tickets</a>. Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in <a href="#ticket-urgency">Ticket Urgency</a>.
-</div>
+>⚠️ Emergency support will be available **exclusively** for Urgent requests and provided via [Zendesk tickets](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM). Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in [Ticket Urgency](#ticket-urgency).
 
 ## Ticket urgency
 
diff --git a/docs/faq/en/vtex-support-united-states.md b/docs/faq/en/vtex-support-united-states.md
index 1f8a0acbe..f64470dfb 100644
--- a/docs/faq/en/vtex-support-united-states.md
+++ b/docs/faq/en/vtex-support-united-states.md
@@ -27,7 +27,7 @@ Our regular support hours are Monday through Friday, from 8am EST to 7pm EST. Su
 
 Keep in mind that our first response time calculation is based on working hours. The criteria for ticket urgency are defined in the section below.
 
-<div class="alert alert-warning">Emergency support will be available <strong>exclusively</strong> for Urgent requests and provided via <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Zendesk tickets</a>. Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in <a href="#ticket-urgency">Ticket Urgency</a>.</div>
+>⚠️ Emergency support will be available **exclusively** for Urgent requests and provided via [Zendesk tickets](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM). Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in [Ticket Urgency](#ticket-urgency).
 
 ## Ticket urgency
 
diff --git a/docs/faq/en/what-is-the-whatsapp-link.md b/docs/faq/en/what-is-the-whatsapp-link.md
index c4dd6bfe3..74f02bee4 100644
--- a/docs/faq/en/what-is-the-whatsapp-link.md
+++ b/docs/faq/en/what-is-the-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: what-is-the-whatsapp-link
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/where-to-use-whatsapp-link.md b/docs/faq/en/where-to-use-whatsapp-link.md
index 821fcc8ec..be15479aa 100644
--- a/docs/faq/en/where-to-use-whatsapp-link.md
+++ b/docs/faq/en/where-to-use-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: en
 legacySlug: where-to-use-whatsapp-link
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md b/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md
index d1c1084bf..36ecbd991 100644
--- a/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md
+++ b/docs/faq/en/why-cant-i-see-my-carrier-on-checkout.md
@@ -26,9 +26,7 @@ Carriers should be grouped into categories upon registration, including the [typ
 
 Checkout will always highlight the cheapest/fastest carrier from the options of the same type of delivery. Thus, a carrier will not appear at checkout when another of the same type has a better cost/delivery option registered. 
 
-<div class="alert alert-warning">
-When there is a tie between carriers, the tiebreaker criterion is to have the lowest shipping cost.
-</div>
+>⚠️ When there is a tie between carriers, the tiebreaker criterion is to have the lowest shipping cost.
 
 ### Solution
 
@@ -80,6 +78,4 @@ To improve the customer's shopping experience, the**Optimization of shipping opt
 
 Disable the function [Optimization of delivery options at Checkout](https://help.vtex.com/en/tutorial/optimization-of-shipping-options-at-checkout--6DeGO9eBSFWe4XkoS0SxAB) in your store.
 
-<div class="alert alert-warning">
-By disabling this function in Admin VTEX, all available shipping options will be displayed in the Checkout process. However, if the <a href="https://help.vtex.com/en/tutorial/order-split-and-delivery-split--jQvzA6QgSd51e2p6bthoV#">Multiple Deliveries</a> functionality is enabled in the store and there are different delivery options between the selected items in the cart, the <b>Optimized Delivery Options</b> will continue to be displayed. That is, delivery optimization will be needed to handle multiple packages (items with different delivery options).
-</div>
+>⚠️ By disabling this function in Admin VTEX, all available shipping options will be displayed in the Checkout process. However, if the [Multiple Deliveries](https://help.vtex.com/en/tutorial/order-split-and-delivery-split--jQvzA6QgSd51e2p6bthoV#) functionality is enabled in the store and there are different delivery options between the selected items in the cart, the **Optimized Delivery Options** will continue to be displayed. That is, delivery optimization will be needed to handle multiple packages (items with different delivery options).
diff --git a/docs/faq/en/why-doesnt-authentication-with-appkey-and-apptoken-work.md b/docs/faq/en/why-doesnt-authentication-with-appkey-and-apptoken-work.md
index 5f50b4bbb..94d9f0b3d 100644
--- a/docs/faq/en/why-doesnt-authentication-with-appkey-and-apptoken-work.md
+++ b/docs/faq/en/why-doesnt-authentication-with-appkey-and-apptoken-work.md
@@ -24,9 +24,7 @@ When created, no pair of appKey and appToken is linked to a role. It's necessary
 
 One of the reasons for integration errors can be a lack of association of the created keys with the role. Another possible error is the link of the appKey and appToken to a profile that, although being registered, does not have enough access to perform that specific task on the platform.
 
-<div class="alert alert-info">
-Only the <a href="https://help.vtex.com/tutorial/what-is-the-master-user--3oPr7YuIkEYqUGmEqIMSEy">Sponsor user</a> has the necessary permission to edit the keys, meaning to create the appKey and appToken used in integrations with a store.
-</div>
+>ℹ️ Only the [Sponsor user](https://help.vtex.com/tutorial/what-is-the-master-user--3oPr7YuIkEYqUGmEqIMSEy) has the necessary permission to edit the keys, meaning to create the appKey and appToken used in integrations with a store.
 
 ## Mistyping
 
@@ -34,7 +32,5 @@ Both keys should be filled out in their respective fields, without spacing and b
 
 Check for possible errors by accessing __Account Management__ and __[Users](https://help.vtex.com/en/tutorial/managing-users--tutorials_512)__.
 
-<div class="alert alert-info">
-The appToken cannot be recovered, once it has been created and displayed to the user.
-</div>
+>ℹ️ The appToken cannot be recovered, once it has been created and displayed to the user.
 
diff --git a/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md b/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
index 71e940a80..4a98fcb82 100644
--- a/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
+++ b/docs/faq/en/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
@@ -22,8 +22,7 @@ But in some cases this automatic definition does not place the product in the ri
 
 ## Defining the product category
 
-<div class="alert alert-danger"> This procedure does not cause the integration to update the category in Mercado Livre. The ideal is to do it before integrating the product. If the product is already integrated, the solution is to delete the existing advertisement and integrate it again, with the category registered previously.
-</div>
+>❗ This procedure does not cause the integration to update the category in Mercado Livre. The ideal is to do it before integrating the product. If the product is already integrated, the solution is to delete the existing advertisement and integrate it again, with the category registered previously.
 
 Mercado Livre has a tool which automatically defines the category of each product shipped. This tool uses information such as the name of the product, and if it makes the wrong inference it may categorize the product wrongly. Thus the announcement can appear in the incorrect category.
 
diff --git a/docs/faq/en/why-i-do-not-receive-my-abandoned-cart-emails.md b/docs/faq/en/why-i-do-not-receive-my-abandoned-cart-emails.md
index 1d9daa703..a21ccbade 100644
--- a/docs/faq/en/why-i-do-not-receive-my-abandoned-cart-emails.md
+++ b/docs/faq/en/why-i-do-not-receive-my-abandoned-cart-emails.md
@@ -46,6 +46,4 @@ When dealing with the Abandoned Cart, it's important to configure two filters: "
 
 After checking, it's crucial to save all the information created. Afterwards, the emails will be sent out as usual.
 
-<div class="alert alert-warning">
-In addition, it is also important to state that a session lasts <strong>30 minutes</strong>. Only after this time has expired would the system consider setting off the Abandoned Cart Trigger, which means that the time taken into account is that of the session's duration in addition to that of the Trigger scheduling.
-</div>
+>⚠️ In addition, it is also important to state that a session lasts **30 minutes**. Only after this time has expired would the system consider setting off the Abandoned Cart Trigger, which means that the time taken into account is that of the session's duration in addition to that of the Trigger scheduling.
diff --git a/docs/faq/en/why-is-my-stock-negative.md b/docs/faq/en/why-is-my-stock-negative.md
index 33cf9e7c9..148b915aa 100644
--- a/docs/faq/en/why-is-my-stock-negative.md
+++ b/docs/faq/en/why-is-my-stock-negative.md
@@ -36,6 +36,4 @@ To adjust it, the item stock must be updated with the quantity of physical items
 4. In the __Update Count__ column, fill in the value indicated in the description above.
 5. Click __Save__.
 
-<div class="alert alert-warning">
-When two or more warehouses use the same <a href="https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV">trade policy</a>, and there is a negative number of items in stock for a given SKU in one of these warehouses, the SKU becomes unavailable for sale, even though the  <a href="https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139">inventory</a> quantity is positive in another warehouse.
-</div>
+>⚠️ When two or more warehouses use the same [trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV), and there is a negative number of items in stock for a given SKU in one of these warehouses, the SKU becomes unavailable for sale, even though the  [inventory](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) quantity is positive in another warehouse.
diff --git a/docs/faq/en/why-is-the-product-not-visible-on-the-website.md b/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
index 6898a5409..bd6f79531 100644
--- a/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/en/why-is-the-product-not-visible-on-the-website.md
@@ -30,10 +30,9 @@ This article explains the main means of investigating, in the VTEX Admin, what a
 * [Logistics](#logistics)
 * [CMS](#cms)
 
-<div class="alert alert-info">
-<p>After adjusting any of the product and SKU details or after changing the Logistics settings, you must wait for the product to be indexed. You can check the indexing status in the <a href="https://help.vtex.com/en/tutorial/understanding-how-indexation-works--tutorials_256">indexing queue</a> in <strong>Catalog > Reports > Product indexing</strong>.</p>
-<p>When the indexing is finished, try accessing the product page from an anonymous tab to view the updated page version avoiding cache issues.</p>
-</div>
+>ℹ️ After adjusting any of the product and SKU details or after changing the Logistics settings, you must wait for the product to be indexed. You can check the indexing status in the [indexing queue](https://help.vtex.com/en/tutorial/understanding-how-indexation-works--tutorials_256) in **Catalog > Reports > Product indexing**.
+>
+> When the indexing is finished, try accessing the product page from an anonymous tab to view the updated page version avoiding cache issues.
 
 ## Catalog
 
@@ -58,10 +57,9 @@ To check the product settings, you must follow the steps below.
     * **Brand:** Check the brand associated with the product and make sure it is active.
     * **Category:** Check the category associated with the product and make sure it is active.
 
-   <div class="alert alert-warning">
-      <p>When adding a new product, you must associate it with a brand and a category that are active before it can be activated for the first time. However, once a product has been added and is active, deactivating the category and brand will not deactivate it completely.</p>
-      <p>Products with inactive categories and brands become invisible in the store, which means they are not displayed in the search results and do not have their own pages. To make them unavailable, you must reset their quantity in stock to zero.</p>
-   </div>
+   >⚠️ When adding a new product, you must associate it with a brand and a category that are active before it can be activated for the first time. However, once a product has been added and is active, deactivating the category and brand will not deactivate it completely.
+>
+> Products with inactive categories and brands become invisible in the store, which means they are not displayed in the search results and do not have their own pages. To make them unavailable, you must reset their quantity in stock to zero.
 
     * **Trade policies:** Check if the product is associated with a [trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV). If it's not, use the selection box to choose the trade policy with which you want to associate it.
     * **Market launch date:** Check if the date for the product launch on market is correct. If the date is set in the future, the product will only be displayed on the website at the mentioned date.
@@ -131,10 +129,9 @@ An active SKU without errors will appear in the index, similar to the one illust
 
 ![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/9e9c99cc4c9408c6dfbaddd4feaaaa84/11-indexed-info-code-active.png)
 
-<div class="alert alert-info">
-<p>If no reason is given for the product’s unavailability and if you do not find any issues in the product/SKUs, reindexing the product may solve the problem.</p>
-<p>To do this, you can edit one of the fields within the product or SKUs information page and save the changes. This will force a reindexing.</p>
-</div>
+>ℹ️ If no reason is given for the product’s unavailability and if you do not find any issues in the product/SKUs, reindexing the product may solve the problem.
+>
+> To do this, you can edit one of the fields within the product or SKUs information page and save the changes. This will force a reindexing.
 
 ## Prices
 
@@ -177,9 +174,7 @@ The **Shipping simulator** allows you to check if the item exists in the invento
 
 ![13-simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/0fbc4b15077d4ea265c82c0a70f5f064/13-simular-frete-en.PNG)
 
-<div class="alert alert-info">
-<p>To investigate a specific item, you must perform the simulation using a <strong>zip code</strong> included in all the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140">trade policies</a>. If you find out the item is not available for that zip code, it means it will not be available for any other one.</p>
-</div>
+>ℹ️ To investigate a specific item, you must perform the simulation using a **zip code** included in all the [trade policies](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140). If you find out the item is not available for that zip code, it means it will not be available for any other one.
 
 The simulation result shows whether the product is available for delivery at the provided address and which are the best shipping options. For example, if there are not enough available items in stock, the simulator will display the following message:
 
@@ -212,9 +207,7 @@ For more information, please read the [Inventory management](https://help.vtex.c
 
 If your product is still not visible on the website even after checking all the **Catalog**, **Prices** and **Logistics** settings, you must check your store [CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC). See below to learn how to investigate if your store's [binding](https://help.vtex.com/en/tutorial/what-is-binding--4NcN3NJd0IeYccgWCI8O2W) is correct and check the specific settings for [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) and [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
 
-<div class="alert alert-warning">
-<p>To perform the CMS investigation described below, you must ask your store's developer team for support.</p>
-</div>
+>⚠️ To perform the CMS investigation described below, you must ask your store's developer team for support.
 
 ## Binding
 
diff --git a/docs/faq/en/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md b/docs/faq/en/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
index b67149e86..61d67d61d 100644
--- a/docs/faq/en/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
+++ b/docs/faq/en/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
@@ -22,7 +22,5 @@ When cancellation happens, the user is notified through [VTEX DO](https://help.v
 
 2) If you want to go ahead with fulfillment, follow with the invoicing, informing the customer that the order cannot be canceled.
 
-<div class="alert alert-danger">
-Under <code>Cancellation Window</code> status, only the customer’s cancellation request is unilateral, and the store does not confirm. In all other statuses, the store will be informed of the request through VTEX DO.
-</div>
+>❗ Under `Cancellation Window` status, only the customer’s cancellation request is unilateral, and the store does not confirm. In all other statuses, the store will be informed of the request through VTEX DO.
 
diff --git a/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 1f5abc26e..d92f1e0f3 100644
--- a/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/en/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -22,9 +22,7 @@ Since with SmartCheckout purchases can be closed just with the email and with th
 
 In other words, if the customer concludes the purchase using only the email and the CVV of the credit card, and if the operator’s approval does not occur after 3 consecutive attempts, a user ID screen is displayed so that the customer can continue trying to purchase. This countdown starts again when the customer logs in and successfully completes their purchase.
 
-<div class="alert alert-warning">
-Requiring a new authentication is only related to the established limit of 3 unsuccessful purchase attempts with the same card. This means that, <strong> regardless of the time interval between each attempt, authentication will be requested when the customer tries for the third time to end a purchase without success.</strong>
-</div>
+>⚠️ Requiring a new authentication is only related to the established limit of 3 unsuccessful purchase attempts with the same card. This means that, ** regardless of the time interval between each attempt, authentication will be requested when the customer tries for the third time to end a purchase without success.**
 
 This measure is aimed at the security of customer data against counter-attacks and attempts at fraud.
 
diff --git a/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
index 19e4d623f..59c5e16da 100644
--- a/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/es/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: como-bloquear-customizacoes-para-investigar-problemas-no-front-end-da-loja, como-bloquear-personalizaciones-para-investigar-problemas-en-el-front-end-de-la-tienda
 ---
 
-<div class="alert alert-warning">
-Tutorial válido solo para tiendas CMS Portal Legado.
-</div>
+>⚠️ Tutorial válido solo para tiendas CMS Portal Legado.
 
 En este artículo, aprenderá a bloquear las personalizaciones de front-end para detectar si el problema es la información que VTEX entrega de forma nativa o si es la personalización de la página.
 
diff --git a/docs/faq/es/can-i-order-my-products-as-i-want.md b/docs/faq/es/can-i-order-my-products-as-i-want.md
index 1cf4f492c..d164de584 100644
--- a/docs/faq/es/can-i-order-my-products-as-i-want.md
+++ b/docs/faq/es/can-i-order-my-products-as-i-want.md
@@ -36,6 +36,4 @@ Estes son los parámetros:
 
 Ejemplo: `http://www.{AccountName}.com.br/{departamento}/{categoria}?O=OrderByPriceASC`
 
-<div class="alert alert-warning">
-<strong>Sólo puede utilizar un parámetro de ordenación de productos a la vez.</strong> Por eso, elija el que mejor se adapte a sus necesidades (si lo necesita, puede reemplazar los parámetros utilizados).
-</div>
+>⚠️ **Sólo puede utilizar un parámetro de ordenación de productos a la vez.** Por eso, elija el que mejor se adapte a sus necesidades (si lo necesita, puede reemplazar los parámetros utilizados).
diff --git a/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
index bec68f16b..8bd737da1 100644
--- a/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/es/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -53,9 +53,7 @@ No. Los pagos con split soportan el cambio de seller solamente cuando se realiza
 
 Por tanto, no podemos ofrecer una ventana de tiempo para la realización del cambio de seller. 
 
-<div class="alert alert-warning">
-  Si intenta cambiar de seller con medios de pago que no sean tarjeta de crédito, recibirá el siguiente mensaje de error en la llamada de la API: «Error when updating additional data for transaction = 722726D8B04C4AAFB1EC945076FD2913. Payout split was already done»
-  </div>
+>⚠️ Si intenta cambiar de seller con medios de pago que no sean tarjeta de crédito, recibirá el siguiente mensaje de error en la llamada de la API: «Error when updating additional data for transaction = 722726D8B04C4AAFB1EC945076FD2913. Payout split was already done»
 
 ### ¿Se podrá realizar reembolsos parciales o totales de los pedidos?
 
@@ -83,9 +81,7 @@ Sin embargo, fue necesario cambiar de *seller* y, después del cambio, el pedido
 
 En la pantalla del *seller* Partner02, podemos observar una reducción de BRL 0,28 en el precio del producto, que se identifica como «Descuento de Coinshop» (a pesar de que el precio para el *seller* Partner02 es BRL 0,30, el valor que se le paga es BRL 0,02). 
 
-<div class="alert alert-info">
-  Cabe destacar que, en este caso, cambiar de seller fue posible porque la diferencia era menor a BRL 0,30; sin embargo, si fuera BRL 0,31 o más, no se podría cambiar de seller.
-  </div>
+>ℹ️ Cabe destacar que, en este caso, cambiar de seller fue posible porque la diferencia era menor a BRL 0,30; sin embargo, si fuera BRL 0,31 o más, no se podría cambiar de seller.
 
 Después de facturar el pedido, se liquidó el valor BRL 5,02 y se aprobó la división del pago.
 
@@ -113,9 +109,7 @@ Con relación a la repartición de esas cuentas por cobrar con el seller, la div
 | Marketplace Coinshop      | Comisión sobre valor de producto = 10% (de BRL 0,60)       | 0,06 (solo ilustrativo)      |
 | Japacoin    | Valor total del pedido - comisión = BRL 0,60-0,06       | 0,64 (solo ilustrativo)     |
 
-<div class="alert alert-info">
-  Es importante recordar que, si el precio que tiene el nuevo seller es más bajo que el precio del seller original, no habrá un bloqueo de seguridad de BRL 0,30.
-  </div>
+>ℹ️ Es importante recordar que, si el precio que tiene el nuevo seller es más bajo que el precio del seller original, no habrá un bloqueo de seguridad de BRL 0,30.
 
 Por tanto, aunque el precio para el seller Japacoin es BRL 0,04, el valor dividido es BRL 0,60. 
 
diff --git a/docs/faq/es/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md b/docs/faq/es/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md
index e55b442a3..edffd24fe 100644
--- a/docs/faq/es/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md
+++ b/docs/faq/es/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md
@@ -30,9 +30,7 @@ Vea el paso a paso a continuación:
 4. Haga clic en el ícono de __Engranaje__ 
 5. Busque por __Porcentaje de Tolerancia__ y agregue un valor
 
-<div class="alert alert-info">
-Generalmente, en el caso de Magazine Luiza, el valor mínimo cobrado por el Porcentaje de Tolerancia es de 15%. Sin embargo, todo depende del valor que el marketplace registrará para un producto. Siempre vale la pena verificar el porcentaje antes de llenar el campo en la configuración.
-</div>
+>ℹ️ Generalmente, en el caso de Magazine Luiza, el valor mínimo cobrado por el Porcentaje de Tolerancia es de 15%. Sin embargo, todo depende del valor que el marketplace registrará para un producto. Siempre vale la pena verificar el porcentaje antes de llenar el campo en la configuración.
 
 Después de completar esta primera etapa, es posible que los pedidos no se procesen inmediatamente. Aún así, existe una forma de agilizar el proceso que es ignorando [a divergência do valor do pedido](https://help.vtex.com/es/tracks/configurar-integracao-com-a-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y/4QWLcDhsh2GSSamouyu6M0 "a divergência do valor do pedido").
 
diff --git a/docs/faq/es/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md b/docs/faq/es/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
index 6e5f12801..717d901d2 100644
--- a/docs/faq/es/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/es/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
@@ -20,9 +20,7 @@ Este error ocurre cuando la plantilla de flete importada __posee una pestaña fu
 
 Generalmente, la pestaña fuera del estándar no contiene ninguna información importante. Para resolver el problema, __elimine las pestañas fuera del estándar__, verifique si las pestañas dentro del estándar están con las informaciones correctas y realice el upload nuevamente.
 
-<div class="alert alert-warning">
-Si la plantilla tiene más de 10 MB, será necesario comprimirla en el formato .zip. Este archivo .zip deberá tener menos de 10 MB. De lo contrario, el upload no funcionará.
-</div>
+>⚠️ Si la plantilla tiene más de 10 MB, será necesario comprimirla en el formato .zip. Este archivo .zip deberá tener menos de 10 MB. De lo contrario, el upload no funcionará.
 
 ## Obtener plantilla con formato estándar
 
diff --git a/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md b/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
index 68b358468..79ad06faa 100644
--- a/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/es/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
@@ -20,8 +20,5 @@ Este error ocurre cuando la plantilla de flete es importada con la extensión __
 
 Para resolver el problema, es necesario ajustar la plantilla de flete para la extensión __.xls__ e [importar la plantilla de flete](http://help.vtex.com/es/tutorial/importar-planilla-de-envio) nuevamente.
 
-<div class="alert alert-warning">
-
-Si la plantilla tiene más de 10 MB, será necesario comprimirla en el formato .zip. Este archivo .zip deberá tener menos de 10 MB. De lo contrario, o upload no funcionará.
-</div>
+>⚠️ Si la plantilla tiene más de 10 MB, será necesario comprimirla en el formato .zip. Este archivo .zip deberá tener menos de 10 MB. De lo contrario, o upload no funcionará.
 
diff --git a/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md b/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
index ed7720c21..da53e7f3e 100644
--- a/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
+++ b/docs/faq/es/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
@@ -20,10 +20,8 @@ Este error ocurre cuando algún __título de las columnas de las plantillas de f
 
 Para resolver el problema, es necesario ajustar el título de la columna con el nombre correcto y hacer nuevamente el upload de la plantilla. 
 
-<div class="alert alert-warning">
-Si la plantilla tiene más de 10 MB, será necesario comprimirla en el formato .zip. Este archivo .zip deberá tener menos de 10 MB.
-De lo contrario, el upload no funcionará. 
-</div>
+>⚠️ Si la plantilla tiene más de 10 MB, será necesario comprimirla en el formato .zip. Este archivo .zip deberá tener menos de 10 MB.
+> De lo contrario, el upload no funcionará.
 
 ## Obtener el nombre correcto de los títulos de las columnas 
 
diff --git a/docs/faq/es/fix-redirect-error-in-pagseguro.md b/docs/faq/es/fix-redirect-error-in-pagseguro.md
index 779b2645e..4aeaa2ef2 100644
--- a/docs/faq/es/fix-redirect-error-in-pagseguro.md
+++ b/docs/faq/es/fix-redirect-error-in-pagseguro.md
@@ -14,7 +14,7 @@ locale: es
 legacySlug: corregir-error-de-redirecionamento-en-pagseguro
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Si usted está encontrando __problemas de redireccionamiento__ utilizando Pagseguro, es probable que el *redirect* de PagSeguro esté configurado de forma incorrecta.
 
diff --git a/docs/faq/es/how-to-add-more-agents-in-a-whatsapp-link.md b/docs/faq/es/how-to-add-more-agents-in-a-whatsapp-link.md
index e7975e313..84c57f515 100644
--- a/docs/faq/es/how-to-add-more-agents-in-a-whatsapp-link.md
+++ b/docs/faq/es/how-to-add-more-agents-in-a-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: como-agregar-mas-agentes-en-un-link-de-whatsapp
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/how-to-configure-a-new-trade-policy.md b/docs/faq/es/how-to-configure-a-new-trade-policy.md
index a646a9ba3..e18fb31c3 100644
--- a/docs/faq/es/how-to-configure-a-new-trade-policy.md
+++ b/docs/faq/es/how-to-configure-a-new-trade-policy.md
@@ -24,6 +24,4 @@ Digamos, por ejemplo, que usted tiene una subtienda específica para el B2B, y q
 
 Para contractar políticas comerciales adicionales es necesario contactar nuestra area de Sales Operations por el email: __sales-operations@vtex.com__.
 
-<div class="alert alert-warning">
-La contratación de políticas comerciales para integración con marketplaces certificados u otras tiendas VTEX és libre de tasas mensuales.
-</div>
+>⚠️ La contratación de políticas comerciales para integración con marketplaces certificados u otras tiendas VTEX és libre de tasas mensuales.
diff --git a/docs/faq/es/how-to-edit-a-whatsapp-link.md b/docs/faq/es/how-to-edit-a-whatsapp-link.md
index 3f683ce62..7ba4a0b65 100644
--- a/docs/faq/es/how-to-edit-a-whatsapp-link.md
+++ b/docs/faq/es/how-to-edit-a-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: como-editar-un-link-de-whatsapp
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/how-to-find-facebook-pixel.md b/docs/faq/es/how-to-find-facebook-pixel.md
index 05e921de3..f9eba1ce3 100644
--- a/docs/faq/es/how-to-find-facebook-pixel.md
+++ b/docs/faq/es/how-to-find-facebook-pixel.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: como-encontrar-el-pixel-de-facebook
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/how-to-find-google-analytics-pixel.md b/docs/faq/es/how-to-find-google-analytics-pixel.md
index 245fbbff5..75761cf0b 100644
--- a/docs/faq/es/how-to-find-google-analytics-pixel.md
+++ b/docs/faq/es/how-to-find-google-analytics-pixel.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: como-encontrar-el-pixel-de-google-analytics
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/how-to-find-google-tag-manager-pixel.md b/docs/faq/es/how-to-find-google-tag-manager-pixel.md
index b9444f5b9..b5536d3ad 100644
--- a/docs/faq/es/how-to-find-google-tag-manager-pixel.md
+++ b/docs/faq/es/how-to-find-google-tag-manager-pixel.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: como-encontrar-google-tag-manager-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/how-to-find-linkedin-pixel.md b/docs/faq/es/how-to-find-linkedin-pixel.md
index 114b96bcb..29816d1d5 100644
--- a/docs/faq/es/how-to-find-linkedin-pixel.md
+++ b/docs/faq/es/how-to-find-linkedin-pixel.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: como-encontrar-linkedin-pixel
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/improvements-in-the-checkout-api-part-1.md b/docs/faq/es/improvements-in-the-checkout-api-part-1.md
index bb29a69a2..b89f623c0 100644
--- a/docs/faq/es/improvements-in-the-checkout-api-part-1.md
+++ b/docs/faq/es/improvements-in-the-checkout-api-part-1.md
@@ -18,13 +18,9 @@ Nuestro equipo de desarrollo está constantemente mejorando el rendimiento de nu
 
 En este artículo se enumeran todas las partes de la API V2 de Checkout que probablemente no van a estar en el próximo release.
 
-<div class="alert alert-warning">
-Este artículo va a estar en permanente actualización hasta el lanzamiento de la API V3 del Checkout. Sin embargo, usted necesita estar atento a los cambios no descritos aquí y que se pueden implementar en la V3.
-</div>
+>⚠️ Este artículo va a estar en permanente actualización hasta el lanzamiento de la API V3 del Checkout. Sin embargo, usted necesita estar atento a los cambios no descritos aquí y que se pueden implementar en la V3.
 
-<div class="alert alert-warning">
-El objetivo de este artículo es permitir que usted ya empiece el proceso de actualización de las integraciones y personalizaciones de su tienda, pensando en las nuevas soluciones ofrecidas por el sistema. Por eso, le recomendamos que esté atento y no deje para realizar los cambios de última hora.
-</div>
+>⚠️ El objetivo de este artículo es permitir que usted ya empiece el proceso de actualización de las integraciones y personalizaciones de su tienda, pensando en las nuevas soluciones ofrecidas por el sistema. Por eso, le recomendamos que esté atento y no deje para realizar los cambios de última hora.
 
 
 ## Dirección en el carrito y en el pedido
diff --git a/docs/faq/es/locate-the-google-ads-pixel.md b/docs/faq/es/locate-the-google-ads-pixel.md
index 7d9a62c5d..7ff163f68 100644
--- a/docs/faq/es/locate-the-google-ads-pixel.md
+++ b/docs/faq/es/locate-the-google-ads-pixel.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: localiza-el-pixel-de-google-ads
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/my-trial-is-over-now-what.md b/docs/faq/es/my-trial-is-over-now-what.md
index e14fda073..0ce72aeb2 100644
--- a/docs/faq/es/my-trial-is-over-now-what.md
+++ b/docs/faq/es/my-trial-is-over-now-what.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: mi-prueba-ha-terminado-ahora-que
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
index e78a28e22..0e185cd21 100644
--- a/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/es/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -29,6 +29,4 @@ Cuando el ERP consulta e inserta este pedido en su base, es necesario que él le
 
 > Es necesario tener un [perfil de acceso con permiso OMS - Full access](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para llevar a cabo esta acción.
 
-<div class="alert alert-warning">
-  <p>Si el pedido pasa del status <b>Iniciar manoseo</b> manualmente, no será posible bajar el pedido para el ERP posteriormente.</p>
-</div>
+>⚠️ Si el pedido pasa del status **Iniciar manoseo** manualmente, no será posible bajar el pedido para el ERP posteriormente.
diff --git a/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
index 8409c3dc7..4867d4d04 100644
--- a/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
+++ b/docs/faq/es/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -25,6 +25,4 @@ Cuando el ERP consulta e inserta este pedido en su base, es necesario que él le
 
 > Es necesario tener un [perfil de acceso con permiso OMS - Full access](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para llevar a cabo esta acción.
 
-<div class="alert alert-warning">
-<p>Si el pedido pasa del status <b>Iniciar preparación</b> manualmente, no será posible bajar el pedido para el ERP posteriormente.</p>
-</div>
+>⚠️ Si el pedido pasa del status **Iniciar preparación** manualmente, no será posible bajar el pedido para el ERP posteriormente.
diff --git a/docs/faq/es/understanding-vtex-email-capture-system.md b/docs/faq/es/understanding-vtex-email-capture-system.md
index c365d2000..b055346ee 100644
--- a/docs/faq/es/understanding-vtex-email-capture-system.md
+++ b/docs/faq/es/understanding-vtex-email-capture-system.md
@@ -38,17 +38,13 @@ Para una mejor comprensión, presentaremos un escenario (dividido en 3 pasos), d
 |------------------|------------------|
 | Haga clic en `Ir para la Entrega`. | Checkout solicita a RC.JS que transfiera la dirección de correo electrónico y la información del carrito a Master Data (a través del Profile System). |
 
-<div class="alert alert-warning">
-Para que se pueda utilizar la función <a href="https://help.vtex.com/es/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#">carrito abandonado</a>, es necesario que el usuario haya rellenado los siguientes datos: e-mail, nombre, apellidos y CPF. La falta de alguno de estos datos, imposibilita la utilización del carrito abandonado.
-</div>
+>⚠️ Para que se pueda utilizar la función [carrito abandonado](https://help.vtex.com/es/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#), es necesario que el usuario haya rellenado los siguientes datos: e-mail, nombre, apellidos y CPF. La falta de alguno de estos datos, imposibilita la utilización del carrito abandonado.
 
 | __Usuario__ | __Plataforma VTEX__ |
 |------------------|------------------|
 | Rellena los datos de envío y pago. | The Checkout orderForm becomes an order and is transmitted to the VTEX OMS. El orderForm de Checkout se convierte en un pedido y se transmite al VTEX OMS. La información completa del usuario (nombre, apellido, correo electrónico, carrito y toda la información adicional) se transmite a Master Data. La captura de correo electrónico puede tardar hasta 46 minutos en reflejarse correctamente en CRM. |
 
-<div class="alert alert-info">
-Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
-</div>
+>ℹ️ Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
 
 ![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md b/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md
index d0be6edc6..59c4691f5 100644
--- a/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md
+++ b/docs/faq/es/untitled-entry-2017-09-19-at-09-42-49.md
@@ -38,4 +38,4 @@ https://documenter.getpostman.com/view/322855/pci/Hs3y#56ae3651-0086-7cbc-faec-5
 El response que devolvió la llamada "GET Rule by ID" anterior, será el request de la siguiente llamada "POST Rule by ID", para grabar la nueva configuración, en donde se deberá modificar únicamente el valor "interestRateMethod": 1:
 https://documenter.getpostman.com/view/322855/pci/Hs3y#80db2e68-0913-668b-36ea-b484a839d9ab
 
-<div class="alert alert-danger">IMPORTANTE: Actualmente, solo se logra modificar la forma de pago mediante API. En caso de necesitar modificar la forma de pago desde la interfáz de usuario, se deberá repetir el proceso de configuración por API, ya que al Guardar los cambios, se irá a tomar valor vacío por defecto.</div>
+>❗ IMPORTANTE: Actualmente, solo se logra modificar la forma de pago mediante API. En caso de necesitar modificar la forma de pago desde la interfáz de usuario, se deberá repetir el proceso de configuración por API, ya que al Guardar los cambios, se irá a tomar valor vacío por defecto.
diff --git a/docs/faq/es/utms.md b/docs/faq/es/utms.md
index 7fd18b298..1fec2f7a4 100644
--- a/docs/faq/es/utms.md
+++ b/docs/faq/es/utms.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: utms
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/visa-checkout-orders-do-not-appear-in-my-orders-section.md b/docs/faq/es/visa-checkout-orders-do-not-appear-in-my-orders-section.md
index 70a6a57f1..2ad729acd 100644
--- a/docs/faq/es/visa-checkout-orders-do-not-appear-in-my-orders-section.md
+++ b/docs/faq/es/visa-checkout-orders-do-not-appear-in-my-orders-section.md
@@ -20,6 +20,4 @@ Con eso, los clientes que realizan una primera compra en la tienda no tienen su
 
 Para clientes ya registrados en la tienda, es posible acceder a la sección de __Mis Pedidos__ y ver todos los pedidos realizados, incluso los cerrados por Visa Checkout.
 
-<div class="alert alert-info">
-El e-mail del cliente guardado en VTEX debe ser el mismo que el que se utiliza para iniciar sesión en Visa Checkout para que sea posible ver los pedidos en la sección de <strong>Mis Pedidos</strong>.
-</div>
+>ℹ️ El e-mail del cliente guardado en VTEX debe ser el mismo que el que se utiliza para iniciar sesión en Visa Checkout para que sea posible ver los pedidos en la sección de **Mis Pedidos**.
diff --git a/docs/faq/es/what-is-the-whatsapp-link.md b/docs/faq/es/what-is-the-whatsapp-link.md
index 4d976de7f..1c3dbd84e 100644
--- a/docs/faq/es/what-is-the-whatsapp-link.md
+++ b/docs/faq/es/what-is-the-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: cual-es-el-link-de-whatsapp
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/where-to-use-whatsapp-link.md b/docs/faq/es/where-to-use-whatsapp-link.md
index b4a82efe5..233ca6d8c 100644
--- a/docs/faq/es/where-to-use-whatsapp-link.md
+++ b/docs/faq/es/where-to-use-whatsapp-link.md
@@ -14,6 +14,4 @@ locale: es
 legacySlug: donde-usar-el-link-de-whatsapp
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md b/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md
index eb49b8a8f..e38aa46af 100644
--- a/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md
+++ b/docs/faq/es/why-cant-i-see-my-carrier-on-checkout.md
@@ -26,9 +26,7 @@ Al momento de registrar una transportadora, es necesario incluir el [tipo de ent
 
 El checkout exhibe siempre la transportadora más rápida/barata entre las opciones de un mismo tipo de entrega. Así, una transportadora no aparece en el checkout cuando otra del mismo tipo tiene menor plazo/costo registrado.  
 
-<div class="alert alert-warning">
-Cuando hay empate entre dos transportadoras, el criterio de desempate es tener el menor costo de envío.
-</div>
+>⚠️ Cuando hay empate entre dos transportadoras, el criterio de desempate es tener el menor costo de envío.
 
 ### Solución
 
@@ -79,6 +77,4 @@ Para mejorar la experiencia de compra del cliente, la funcionalidad **Optimizaci
 
 Desactive la función [Optimización de opciones de entrega en Checkout](https://help.vtex.com/es/tutorial/optimizacion-de-opciones-de-entrega-en-checkout--6DeGO9eBSFWe4XkoS0SxAB) en su tienda.
 
-<div class="alert alert-warning">
-Al deshabilitar esta función en Admin VTEX, todas las opciones de entrega disponibles se mostrarán en el proceso de Checkout. Sin embargo, si la funcionalidad de <a href="https://help.vtex.com/es/tutorial/division-de-pedidos-y-division-de-entregas--jQvzA6QgSd51e2p6bthoV#">Entregas Múltiples</a> está habilitada en la tienda y hay diferentes opciones de entrega entre los artículos seleccionados en el carrito, las <b>Opciones de entrega optimizadas</b> seguirán mostrándose. Es decir, se necesitará optimizar la entrega para manejar múltiples paquetes (artículos con diferentes opciones de entrega).
-</div>
+>⚠️ Al deshabilitar esta función en Admin VTEX, todas las opciones de entrega disponibles se mostrarán en el proceso de Checkout. Sin embargo, si la funcionalidad de [Entregas Múltiples](https://help.vtex.com/es/tutorial/division-de-pedidos-y-division-de-entregas--jQvzA6QgSd51e2p6bthoV#) está habilitada en la tienda y hay diferentes opciones de entrega entre los artículos seleccionados en el carrito, las **Opciones de entrega optimizadas** seguirán mostrándose. Es decir, se necesitará optimizar la entrega para manejar múltiples paquetes (artículos con diferentes opciones de entrega).
diff --git a/docs/faq/es/why-doesnt-authentication-with-appkey-and-apptoken-work.md b/docs/faq/es/why-doesnt-authentication-with-appkey-and-apptoken-work.md
index cf7c1798d..a2134ccd5 100644
--- a/docs/faq/es/why-doesnt-authentication-with-appkey-and-apptoken-work.md
+++ b/docs/faq/es/why-doesnt-authentication-with-appkey-and-apptoken-work.md
@@ -24,9 +24,7 @@ Cada par de appKey y appToken, cuando se crea, no está vinculado a un perfil de
 
 Uno de los motivos de error en la autenticación puede ser la falta de asociación de las claves creadas a un perfil de acceso. Otro posible error es la vinculación del appKey y appToken a un perfil que, aunque esté registrado, no tiene acceso para ejercer determinada acción en la plataforma.
 
-<div class="alert alert-info">
-Apenas el <a href="https://help.vtex.com/es/tutorial/que-es-el-usuario-master--3oPr7YuIkEYqUGmEqIMSEy">usuario Titular</a> tiene permiso para manipular las claves; es decir, crear la appKey y el appToken usados en integraciones con la tienda.
-</div>
+>ℹ️ Apenas el [usuario Titular](https://help.vtex.com/es/tutorial/que-es-el-usuario-master--3oPr7YuIkEYqUGmEqIMSEy) tiene permiso para manipular las claves; es decir, crear la appKey y el appToken usados en integraciones con la tienda.
 
 ## Error de digitación
 
@@ -34,7 +32,5 @@ Ambas claves deben ser rellenadas en sus respectivos campos, sin espacio y mante
 
 Puede verificar posibles errores de digitación en los campos en el módulo __Gestión de cuenta__, en __[Usuarios__](https://help.vtex.com/es/tutorial/administrar-usuarios--tutorials_512)__. 
 
-<div class="alert alert-warning">
-El appToken se muestra al usuario apenas en el momento de su creación, no pudiendo recuperarse posteriormente.
-</div>
+>⚠️ El appToken se muestra al usuario apenas en el momento de su creación, no pudiendo recuperarse posteriormente.
 
diff --git a/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md b/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
index 401a64e73..ab71075f8 100644
--- a/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
+++ b/docs/faq/es/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
@@ -39,6 +39,4 @@ Al finalizar la planilla, envía al asesor de tu cuenta __en Mercado Libre__ par
 
 En caso de que usted __no__ tenga un asesor de cuenta en Mercado Libre, sólo será posible cambiar las categorías de los anuncios a través del MyML (frente del MELI) y sólo en casos de productos que __no__ tengan ninguna venta.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> vale resaltar que este proceso no tiene ninguna relación con la VTEX y debe ser intermediado directamente en el Mercado Libre.
-</div>
+>⚠️ **OBS:** vale resaltar que este proceso no tiene ninguna relación con la VTEX y debe ser intermediado directamente en el Mercado Libre.
diff --git a/docs/faq/es/why-i-do-not-receive-my-abandoned-cart-emails.md b/docs/faq/es/why-i-do-not-receive-my-abandoned-cart-emails.md
index c190c147a..19e372678 100644
--- a/docs/faq/es/why-i-do-not-receive-my-abandoned-cart-emails.md
+++ b/docs/faq/es/why-i-do-not-receive-my-abandoned-cart-emails.md
@@ -46,7 +46,5 @@ En el caso de Carrito Abandonado, es importante configurar dos filtros: "Checkou
 
 Después de la verificación, es imprescindible guardar todas las informaciones hechas. Posteriormente, los correos electrónicos serán enviados como de costumbre.
 
-<div class="alert alert-warning">
-Además, es importante resaltar que el tiempo de una sesión dura <strong>30 minutos</strong>. Solo después de ese tiempo el sistema considerará la programación del Trigger de Carrito Abandonado. Es decir, el tiempo considerado es el del período de la sesión sumado a la programación del Trigger.
-</div>
+>⚠️ Además, es importante resaltar que el tiempo de una sesión dura **30 minutos**. Solo después de ese tiempo el sistema considerará la programación del Trigger de Carrito Abandonado. Es decir, el tiempo considerado es el del período de la sesión sumado a la programación del Trigger.
 
diff --git a/docs/faq/es/why-is-my-stock-negative.md b/docs/faq/es/why-is-my-stock-negative.md
index b236579ed..12cbd0027 100644
--- a/docs/faq/es/why-is-my-stock-negative.md
+++ b/docs/faq/es/why-is-my-stock-negative.md
@@ -38,6 +38,4 @@ Para ajustar este escenario, el stock del elemento se debe actualizar con la can
 4. En la columna __Actualizar recuento__, rellene el valor indicado en la descripción anterior.
 5. Haga clic en __Guardar__.
 
-<div class="alert alert-warning">
-Cuando dos o más stocks utilizan la misma <a href="https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV">política comercial</a> y uno de estos stocks tiene una cantidad negativa de unidades, el SKU pasa a no estar disponible para la venta, aunque haya una cantidad disponible en uno de los stocks.  
-</div>
+>⚠️ Cuando dos o más stocks utilizan la misma [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) y uno de estos stocks tiene una cantidad negativa de unidades, el SKU pasa a no estar disponible para la venta, aunque haya una cantidad disponible en uno de los stocks.
diff --git a/docs/faq/es/why-is-the-product-not-visible-on-the-website.md b/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
index f45c0b2c4..8513be255 100644
--- a/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/es/why-is-the-product-not-visible-on-the-website.md
@@ -30,10 +30,9 @@ Este artículo explica los principales puntos a revisar en el Admin VTEX para ve
 * [Logística](#logistica)
 * [CMS](#cms)
 
-<div class="alert alert-info">
-<p>Luego de ajustar cualquier información de los productos y SKU o de modificar la configuración de la logística, espera a que se indexe el producto. Puedes verificar el status de la indexación desde la <a href="https://help.vtex.com/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion--tutorials_256">fila de indexación</a> en <strong>Catálogo > Informes > Productos indexados</strong>.</p>
-<p>Cuando la indexación haya terminado, intenta acceder a la página del producto desde una pestaña anónima en tu navegador para así visualizar la página en su versión más reciente y evitar problemas con el caché.</p>
-</div>
+>ℹ️ Luego de ajustar cualquier información de los productos y SKU o de modificar la configuración de la logística, espera a que se indexe el producto. Puedes verificar el status de la indexación desde la [fila de indexación](https://help.vtex.com/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion--tutorials_256) en **Catálogo > Informes > Productos indexados**.
+>
+> Cuando la indexación haya terminado, intenta acceder a la página del producto desde una pestaña anónima en tu navegador para así visualizar la página en su versión más reciente y evitar problemas con el caché.
 
 ## Catálogo
 
@@ -58,10 +57,9 @@ Para verificar la configuración del producto, es importante que sigas los pasos
     * **Marca:** comprueba el nombre de la marca asociada al producto y asegúrate de que está activa.
     * **Categoría:** comprueba el nombre de la categoría asociada al producto y asegúrate de que está activa.
 
-   <div class="alert alert-warning">
-      <p>Al crear un nuevo producto, debes asociarlo a una marca y a una categoría que estén activas para que se active por primera vez. Sin embargo, una vez que un producto ya existe y está activo, la desactivación de la categoría y la marca no lo desactivará por completo.</p>
-      <p>Los productos con categorías y marcas inactivas se vuelven invisibles en la tienda, es decir, no aparecen en la búsqueda y no tienen su propia página. Para que no estén disponibles, debes restablecer su cantidad en stock a cero.</p>
-   </div>
+   >⚠️ Al crear un nuevo producto, debes asociarlo a una marca y a una categoría que estén activas para que se active por primera vez. Sin embargo, una vez que un producto ya existe y está activo, la desactivación de la categoría y la marca no lo desactivará por completo.
+>
+> Los productos con categorías y marcas inactivas se vuelven invisibles en la tienda, es decir, no aparecen en la búsqueda y no tienen su propia página. Para que no estén disponibles, debes restablecer su cantidad en stock a cero.
 
     * **Políticas comerciales:** revisa que el producto esté asociado a una [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Si no lo está, usa el recuadro de selección para marcar la política comercial en la que deseas incluirlo.
     * **Fecha de lanzamiento en el mercado:** verifica que la fecha de lanzamiento al mercado sea correcta. Si es una fecha futura, el producto recién se mostrará en el sitio web en la fecha indicada.
@@ -131,10 +129,9 @@ Un SKU activo y sin errores tendrá el registro en el indexador parecido al que
 
 ![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/059ed660c68d5e05fbe5f2ac0c571326/11-indexed-info-code-active.png)
 
-<div class="alert alert-info">
-<p>Si la información de la indexación no muestra ningún motivo para la falta de disponibilidad de los productos, y si no encontraste ningún error en el registro de los productos y SKU, probablemente lo que resuelva el problema sea volver a indexar el producto.</p>
-<p>Para hacerlo, modifica algún campo dentro del registro del producto o alguno de sus SKU, y guarda los cambios. Esto forzará la indexación.</p>
-</div>
+>ℹ️ Si la información de la indexación no muestra ningún motivo para la falta de disponibilidad de los productos, y si no encontraste ningún error en el registro de los productos y SKU, probablemente lo que resuelva el problema sea volver a indexar el producto.
+>
+> Para hacerlo, modifica algún campo dentro del registro del producto o alguno de sus SKU, y guarda los cambios. Esto forzará la indexación.
 
 ## Precios
 
@@ -177,9 +174,7 @@ El **Simulador de envío** sirve para verificar si el ítem está en stock y si
 
 ![13-simular-frete-es](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/9d99f84da1c2fa38d8457f1668eb4a5f/13-simular-frete-es.PNG)
 
-<div class="alert alert-info">
-<p>Para revisar un ítem específico, debes realizar la simulación con un <strong>código postal</strong> que cubra todas las <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">políticas de envío</a> registradas. Así sabrás que si un ítem no está disponible para ese CP, tampoco lo estará para algún otro.</p>
-</div>
+>ℹ️ Para revisar un ítem específico, debes realizar la simulación con un **código postal** que cubra todas las [políticas de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) registradas. Así sabrás que si un ítem no está disponible para ese CP, tampoco lo estará para algún otro.
 
 El resultado obtenido indica si el producto está disponible o no para ser entregado en la dirección informada y cuáles son las mejores opciones de envío. Ejemplo: si no hay ítems suficientes disponibles en stock, el simulador mostrará el siguiente mensaje:
 
@@ -212,9 +207,7 @@ Para más información, consulta el tutorial [Gestión del stock](https://help.v
 
 Si tu producto no aparece en el sitio web incluso después de verificar todas las configuraciones en **Catálogo**, **Precios **y **Logística**, es importante revisar el [CMS](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC) de tu tienda. Luego, revisa si el _[binding](https://help.vtex.com/es/tutorial/que-es-binding--4NcN3NJd0IeYccgWCI8O2W)_ de tu tienda es el correcto y también revisa la configuración específica de [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) y [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
 
-<div class="alert alert-warning">
-<p>Para realizar la revisión que se describe a continuación en el CMS, debes pedirle ayuda al equipo de desarrolladores encargado de tu tienda.</p>
-</div>
+>⚠️ Para realizar la revisión que se describe a continuación en el CMS, debes pedirle ayuda al equipo de desarrolladores encargado de tu tienda.
 
 ### Binding
 
diff --git a/docs/faq/es/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md b/docs/faq/es/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
index 409dd04e0..1353c5316 100644
--- a/docs/faq/es/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
+++ b/docs/faq/es/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
@@ -22,7 +22,5 @@ Cuando sucede la cancelación, el comerciante es notificado a través de [VTEX D
 
 2) En el caso de que desee proseguir con la entrega, basta seguir el procedimiento de facturación, informándole al cliente sobre la imposibilidad de cancelar el pedido.
 
-<div class="alert alert-danger">
-Solamente en el status <code>Carencia para cancelación</code> la solicitud de cancelación del cliente es unilateral, no le cabiendo al comerciante ninguna confirmación. En los demás status, el comerciante será informado sobre lo solicitud a través de VTEX DO.
-</div>
+>❗ Solamente en el status `Carencia para cancelación` la solicitud de cancelación del cliente es unilateral, no le cabiendo al comerciante ninguna confirmación. En los demás status, el comerciante será informado sobre lo solicitud a través de VTEX DO.
 
diff --git a/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 8da2b358c..8a336012f 100644
--- a/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/es/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -22,9 +22,7 @@ Como el SmartCheckout permite cerrar una compra sólo con el email y con el CVV
 
 O sea, en el caso de que el cliente finalice la compra tan sólo con el email y el CVV de la tarjeta de crédito y la autorización de la operadora no ocurra en hasta 3 veces seguidas, es mostrada la pantalla de login para que el cliente siga intentando comprar. Ese conteo vuelve al inicio cuando el cliente inicia sesión y completa con éxito su compra.
 
-<div class="alert alert-warning">
-La solicitud de una nueva autenticación al cliente sólo está relacionada con el límite establecido de 3 intentos de compra sin éxito con la misma tarjeta. Esto quiere decir que, <strong>independientemente del intervalo de tiempo entre cada intento, se solicitará la autenticación cuando el cliente intenta por tercera vez finalizar una compra sin éxito.</strong>
-</div>
+>⚠️ La solicitud de una nueva autenticación al cliente sólo está relacionada con el límite establecido de 3 intentos de compra sin éxito con la misma tarjeta. Esto quiere decir que, **independientemente del intervalo de tiempo entre cada intento, se solicitará la autenticación cuando el cliente intenta por tercera vez finalizar una compra sin éxito.**
 
 Esa medida tiene por objeto la seguridad de los datos de los clientes contra ataques e intentos de fraude.
 
diff --git a/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md b/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
index 56fa2bdbd..4d5ecabc6 100644
--- a/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
+++ b/docs/faq/pt/blocking-customizations-to-troubleshoot-front-end-issues.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: como-bloquear-customizacoes-para-investigar-problemas-no-front-end-da-loja
 ---
 
-<div class="alert alert-warning">
- Tutorial válido apenas para lojas CMS Portal Legado.
-</div>
+>⚠️ Tutorial válido apenas para lojas CMS Portal Legado.
 
 Neste artigo, você vai aprender como verificar a origem de um problema front-end. O primeiro passo é bloquear as customizações de front-end. A partir da resposta do site, será possível entender se o problema está na informação que a VTEX entrega de forma nativa ou na customização da sua página.
 
diff --git a/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md b/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
index 628144d65..df5eb8e04 100644
--- a/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
+++ b/docs/faq/pt/can-i-generate-a-report-with-the-best-selling-products-in-my-store.md
@@ -30,6 +30,4 @@ Sua solicitação irá para uma fila, que pode ser acompanhada pelo OMS. Quando
 
 Para obter a informação dos seus produtos mais vendidos, após baixar a planilha, você deve fazer a conta entre as colunas __AH (Quantity_SKU)__, que diz a quantidade do SKU que foi vendida, e a coluna __AI (ID_SKU)__, que se refere o SKU em questão. 
 
-<div class="alert alert-danger">
-As exportações podem ser feitas dentro de uma faixa de tempo de 31 dias.
-</div>
+>❗ As exportações podem ser feitas dentro de uma faixa de tempo de 31 dias.
diff --git a/docs/faq/pt/can-i-order-my-products-as-i-want.md b/docs/faq/pt/can-i-order-my-products-as-i-want.md
index fa84f760f..18b6ff9ef 100644
--- a/docs/faq/pt/can-i-order-my-products-as-i-want.md
+++ b/docs/faq/pt/can-i-order-my-products-as-i-want.md
@@ -36,6 +36,4 @@ Veja abaixo esses parâmetros:
 
 Exemplo: `http://www.{AccountName}.com.br/{departamento}/{categoria}?O=OrderByPriceASC`
 
-<div class="alert alert-warning">
-<strong>Você só pode usar um parâmetro de ordenação de produtos por vez.</strong> Por isso, escolha aquele que melhor se adequa às suas necessidades (se precisar, você pode substituir os parâmetros utilizados)
-</div>
+>⚠️ **Você só pode usar um parâmetro de ordenação de produtos por vez.** Por isso, escolha aquele que melhor se adequa às suas necessidades (se precisar, você pode substituir os parâmetros utilizados)
diff --git a/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md b/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
index 60d0ee256..b468da5fa 100644
--- a/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
+++ b/docs/faq/pt/change-seller-for-affiliations-that-support-native-split-faq.md
@@ -51,9 +51,7 @@ Quando o pagamento é liquidado, as informações sobre recebedores e valores s
 
 Não. Pagamentos com split suportam change seller apenas quando foram realizados com um ou dois cartões de crédito. Isso acontece porque, na maior parte dos provedores de pagamento, meios como o boleto ou cartão de débito têm o valor capturado imediatamente. Sendo assim, não conseguimos oferecer uma janela de tempo para a realização do change seller.
 
-<div class="alert alert-warning">
-  Em casos de tentativa de change seller com meios de pagamento que não seja cartão de crédito, você receberá a seguinte mensagem de erro na chamada da API: "Error when updating additional data for transaction = 722726D8B04C4AAFB1EC945076FD2913. Payout split was already done"
-  </div>
+>⚠️ Em casos de tentativa de change seller com meios de pagamento que não seja cartão de crédito, você receberá a seguinte mensagem de erro na chamada da API: "Error when updating additional data for transaction = 722726D8B04C4AAFB1EC945076FD2913. Payout split was already done"
 
 ### Será possível realizar reembolsos parciais ou totais dos pedidos?
 
@@ -81,9 +79,7 @@ Foi necessário realizar o change seller e, após a mudança, o pedido foi desig
 
 Na tela do seller __Parceiro02__ podemos notar um decréscimo de R$0,28 com a identificação "Desconto de Coinshop" (apesar do preço para o seller Parceiro02 ser de R$ 0,30, o valor pago a ele foi de apenas R$ 0,02)
 
-<div class="alert alert-info">
-  Vale ressaltar que nesse caso o change seller foi possível pois a diferença era inferior a R$0,30, caso fosse de R$0,31 ou mais o change seller não aconteceria.
-  </div>
+>ℹ️ Vale ressaltar que nesse caso o change seller foi possível pois a diferença era inferior a R$0,30, caso fosse de R$0,31 ou mais o change seller não aconteceria.
 
 Após o faturamento do pedido, o valor de R$5,02 foi liquidado e a divisão do pagamento, efetivado.
 
@@ -111,9 +107,7 @@ Com relação à distribuição desses recebíveis com o seller, a divisão seri
 | Marketplace Coinshop     | Comissão x Valor do produto = 10%(0,60)       | 0,06 (apenas ilustrativo)       |
 | Seller Japacoin     | Total do pedido - Comissão = 0,60-0,06      | 0,54 (apenas ilustrativo)       |
 
-<div class="alert alert-info">
-Vale relembrar que em casos onde o preço do novo seller é inferior ao preço do seller original, não existirá uma trava de segurança de R$0,30
-  </div>
+>ℹ️ Vale relembrar que em casos onde o preço do novo seller é inferior ao preço do seller original, não existirá uma trava de segurança de R$0,30
 
 Sendo assim, apesar do preço para o seller Japacoin ser de R$ 0,04, o valor dividido foi de R$ 0,60.
 
diff --git a/docs/faq/pt/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md b/docs/faq/pt/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md
index 17d7f3bf2..7cd3284ac 100644
--- a/docs/faq/pt/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md
+++ b/docs/faq/pt/como-corrigir-pedido-com-divergencia-entre-o-valor-total-do-pedido-da.md
@@ -30,9 +30,7 @@ Confira o passo a passo a seguir:
 4. Clique no ícone de __Engrenagem__ 
 5. Procure por __Percentual de Tolerância__ e adicione um valor
 
-<div class="alert alert-info">
-Geralmente, no caso da Magazine Luiza,  o valor mínimo cobrado pelo Percentual de Tolerância é de 15%. Porém, tudo depende do valor pelo qual o marketplace irá cadastrar para um produto. Sempre vale conferir a porcentagem antes de preencher o campo na configuração.
-</div>
+>ℹ️ Geralmente, no caso da Magazine Luiza,  o valor mínimo cobrado pelo Percentual de Tolerância é de 15%. Porém, tudo depende do valor pelo qual o marketplace irá cadastrar para um produto. Sempre vale conferir a porcentagem antes de preencher o campo na configuração.
 
 Depois de concluir essa primeira etapa, é possível que os pedidos não sejam processados imediatamente. Ainda assim, existe uma forma de agilizar o processo que é ignorando [a divergência do valor do pedido](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-magazine-luiza--5Yx5IrNa7Y48c6aSC8wu2Y/4QWLcDhsh2GSSamouyu6M0 "a divergência do valor do pedido"). 
 
diff --git a/docs/faq/pt/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md b/docs/faq/pt/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
index a9aafd3e9..9ae9fc453 100644
--- a/docs/faq/pt/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/pt/erro-de-coluna-nula-ao-tentar-importar-planilha-de-frete.md
@@ -20,9 +20,7 @@ Este erro ocorre quando a planilha de frete importada __possui uma aba fora do f
 
 Geralmente, a aba fora do padrão não contém nenhuma informação importante. Para resolver o problema, __delete as abas fora do padrão__, verifique se as abas dentro do padrão estão com as informações corretas e realizar o upload novamente.
 
-<div class="alert alert-warning">
-Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato .zip. Este arquivo .zip deverá ter menos de 10 MB. Caso contrário, o upload não irá funcionar.
-</div>
+>⚠️ Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato .zip. Este arquivo .zip deverá ter menos de 10 MB. Caso contrário, o upload não irá funcionar.
 
 ## Obter planilha com formato padrão
 
diff --git a/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md b/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
index 42e3593ce..5073bb5c7 100644
--- a/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
+++ b/docs/faq/pt/erro-invalid-header-signature-ao-tentar-importar-planilha-de-frete.md
@@ -20,6 +20,4 @@ Este erro ocorre quando a planilha de frete é importada com a extensão __.xlsx
 
 Para resolver o problema, é necessário ajustar a planilha de frete para a extensão __.xls__ e [importar a planilha de frete](http://help.vtex.com/pt/tutorial/importar-planilha-de-frete) novamente.
 
-<div class="alert alert-warning">
-Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato .zip. Este arquivo .zip deverá ter menos de 10 MB. Caso contrário, o upload não irá funcionar.
-</div>
+>⚠️ Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato .zip. Este arquivo .zip deverá ter menos de 10 MB. Caso contrário, o upload não irá funcionar.
diff --git a/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md b/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
index 6c2f9d34e..0e1a52f62 100644
--- a/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
+++ b/docs/faq/pt/erro-object-reference-not-set-to-an-instance-of-an-object-ao-tentar.md
@@ -20,9 +20,7 @@ Este erro ocorre quando algum __título das colunas da planilha de frete__ não
 
 Para resolver o problema, é necessário ajustar o título da coluna para o nome correto e fazer novamente o upload da planilha.
 
-<div class="alert alert-warning">
-Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato .zip. Este arquivo .zip deverá ter menos de 10 MB. Caso contrário, o upload não irá funcionar.
-</div>
+>⚠️ Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato .zip. Este arquivo .zip deverá ter menos de 10 MB. Caso contrário, o upload não irá funcionar.
 
 ## Obter o nome correto dos títulos das colunas
 
diff --git a/docs/faq/pt/fix-redirect-error-in-pagseguro.md b/docs/faq/pt/fix-redirect-error-in-pagseguro.md
index 580f53633..55ccf2939 100644
--- a/docs/faq/pt/fix-redirect-error-in-pagseguro.md
+++ b/docs/faq/pt/fix-redirect-error-in-pagseguro.md
@@ -14,7 +14,7 @@ locale: pt
 legacySlug: corrigir-erro-de-redirecionamento-no-pagseguro
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Caso você esteja encontrando __problemas de redirecionamento__ utilizando o Pagseguro, é provável que o *redirect* do PagSeguro esteja configurado de forma errada.
 
diff --git a/docs/faq/pt/how-does-vtex-support-work.md b/docs/faq/pt/how-does-vtex-support-work.md
index 9e5037a3e..2369a0438 100644
--- a/docs/faq/pt/how-does-vtex-support-work.md
+++ b/docs/faq/pt/how-does-vtex-support-work.md
@@ -16,7 +16,7 @@ legacySlug: planos-de-suporte
 
 Na VTEX, compartilhamos a responsabilidade pelo sucesso dos nossos clientes. Nossos planos de suporte permitem que você receba o nível adequado de atenção e expertise para fazer o melhor uso da plataforma e desenvolver o seu negócio. Com isso, você pode mitigar os riscos da sua operação digital e manter seus custos operacionais sob controle. 
 
-<div class="alert alert-info">É necessário <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">habilitar a autorização de suporte</a> no <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">License Manager</a> para que o usuário tenha acesso ao Suporte da VTEX. Esta configuração é válida apenas para contas no Brasil.</div>
+>ℹ️ É necessário [habilitar a autorização de suporte](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) no [License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) para que o usuário tenha acesso ao Suporte da VTEX. Esta configuração é válida apenas para contas no Brasil.
 
 ## Suporte	
 
diff --git a/docs/faq/pt/how-to-configure-a-new-trade-policy.md b/docs/faq/pt/how-to-configure-a-new-trade-policy.md
index 6af51e2b6..a0d5acd99 100644
--- a/docs/faq/pt/how-to-configure-a-new-trade-policy.md
+++ b/docs/faq/pt/how-to-configure-a-new-trade-policy.md
@@ -24,8 +24,6 @@ Digamos, por exemplo, que você tenha uma subloja específica para B2B, e que ne
 
 Para contratar políticas comerciais adicionais, é preciso entrar em contato com a área de Sales Operations, pelo e-mail: __sales-ops-br@vtex.com__
 
-<div class="alert alert-warning">
-A contratação de políticas comerciais para integração com marketplace certificado ou outras lojas VTEX é isenta da taxa mensal.
-</div>
+>⚠️ A contratação de políticas comerciais para integração com marketplace certificado ou outras lojas VTEX é isenta da taxa mensal.
 
 
diff --git a/docs/faq/pt/how-to-find-google-tag-manager-pixel.md b/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
index 7efa61583..7a10e4320 100644
--- a/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
+++ b/docs/faq/pt/how-to-find-google-tag-manager-pixel.md
@@ -20,9 +20,7 @@ Faça login no Gerenciador de [tags do Google](https://www.google.com/intl/pt-B
 
 Na opção **Contâiner ID**, você encontrará o código. Copie-o.
 
-<div class="alert alert-warning">
-  <p><b>Atenção</b>: Seu ID deve conter o prefixo do GTM.</p>
-</div>
+>⚠️ **Atenção**: Seu ID deve conter o prefixo do GTM.
 
 ![Gerenciador de tags Goggle 2](https://images.ctfassets.net/alneenqid6w5/4UqVluoy3i3PraHgP3upQ3/5f45d8f38635a803a00b417667102433/Gerenciador_de_Tags_Google_2.png)
 
diff --git a/docs/faq/pt/is-it-possible-to-change-data-in-a-master-workspace.md b/docs/faq/pt/is-it-possible-to-change-data-in-a-master-workspace.md
index 4c81ebd6a..e6bbbcf7e 100644
--- a/docs/faq/pt/is-it-possible-to-change-data-in-a-master-workspace.md
+++ b/docs/faq/pt/is-it-possible-to-change-data-in-a-master-workspace.md
@@ -22,6 +22,4 @@ Não é possível fazer alterações nesse workspace.
 
 Em vez disso, trabalhe o novo código em outro workspace, depois mude o status desse workspace para `production true` e, por fim, promova-o.
 
-<div class="alert alert-warning">
-Não é possível fazer alterações em master.
-</div>
+>⚠️ Não é possível fazer alterações em master.
diff --git a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
index 06d566d44..4aa10182c 100644
--- a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
+++ b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-do-i-do.md
@@ -29,6 +29,4 @@ Quando o ERP consulta e insere este pedido em sua base, é preciso que ele infor
 
 > É necessário ter um [perfil de acesso com permissão OMS - Full access](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para realizar esta ação.
 
-<div class="alert alert-warning">
-<p>Se o pedido passar do status <b>Iniciar manuseio</b> manualmente, não será possível enviar o pedido para o ERP posteriormente.</p>
-</div>
+>⚠️ Se o pedido passar do status **Iniciar manuseio** manualmente, não será possível enviar o pedido para o ERP posteriormente.
diff --git a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
index 5c4991c8a..bc943d299 100644
--- a/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
+++ b/docs/faq/pt/order-is-locked-in-ready-for-handling-what-should-i-do.md
@@ -25,6 +25,4 @@ Quando o ERP consulta e insere este pedido em sua base, é preciso que ele infor
 
 > É necessário ter um [perfil de acesso com permissão OMS - Full access](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access "Perfis de acesso - OMS Full access") para realizar esta ação.
 
-<div class="alert alert-warning">
-<p>Se o pedido passar do status <b>Iniciar manuseio</b> manualmente, não será possível enviar o pedido para o ERP posteriormente.</p>
-</div>
+>⚠️ Se o pedido passar do status **Iniciar manuseio** manualmente, não será possível enviar o pedido para o ERP posteriormente.
diff --git a/docs/faq/pt/understanding-vtex-email-capture-system.md b/docs/faq/pt/understanding-vtex-email-capture-system.md
index b70f6d7d9..56e78d98a 100644
--- a/docs/faq/pt/understanding-vtex-email-capture-system.md
+++ b/docs/faq/pt/understanding-vtex-email-capture-system.md
@@ -38,16 +38,12 @@ Para melhor compreensão, iremos apresentar um cenário (dividido em 3 etapas),
 |------------------|------------------|
 | Clica em `Ir para entrega`. | Checkout solicita que o RC.JS transfira o endereço de e-mail e as informações do carrinho para o Master Data (por meio do Profile System). |
 
-<div class="alert alert-warning">
-Para que a função do <a href="https://help.vtex.com/pt/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#">carrinho abandonado</a> possa ser utilizada, é necessário que o usuário tenha preenchido as seguintes informações: e-mail, nome, sobrenome e CPF. A falta de um destes dados, impossibilita a utilização do carrinho abandonado.
-</div>
+>⚠️ Para que a função do [carrinho abandonado](https://help.vtex.com/pt/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#) possa ser utilizada, é necessário que o usuário tenha preenchido as seguintes informações: e-mail, nome, sobrenome e CPF. A falta de um destes dados, impossibilita a utilização do carrinho abandonado.
 
 | __Usuário__ | __Plataforma VTEX__ |
 |------------------|------------------|
 | Preenche as informações de frete e pagamento. | O orderForm do Checkout torna-se um pedido e é transmitido para o OMS da VTEX. As informações completas do usuário (nome, sobrenome, e-mail, carrinho e todas as informações adicionais) são transmitidas para o Master Data. A captura de e-mail pode levar até 46 minutos para ser corretamente refletida no CRM. |
 
-<div class="alert alert-info">
-Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
-</div>
+>ℹ️ Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
 
 ![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
diff --git a/docs/faq/pt/untitled-entry-2018-03-06-at-02-03-12.md b/docs/faq/pt/untitled-entry-2018-03-06-at-02-03-12.md
index 5464c09e8..b6c3d3ab0 100644
--- a/docs/faq/pt/untitled-entry-2018-03-06-at-02-03-12.md
+++ b/docs/faq/pt/untitled-entry-2018-03-06-at-02-03-12.md
@@ -65,19 +65,13 @@ A estrutura básica do orderForm é esta:
 
 Essa estrutura é constituída de várias __seções__.
 
-<div class="alert alert-info">
-A maioria das chamadas à API do Checkout pede o parâmetro <code>expectedOrderFormSection</code>, que indica exatamente quais seções devem ser retornadas pela API.
-</div>
+>ℹ️ A maioria das chamadas à API do Checkout pede o parâmetro `expectedOrderFormSection`, que indica exatamente quais seções devem ser retornadas pela API.
 
 No menu abaixo você encontra os links para cada uma dessas seções.
 
-<div class="alert alert-info">
-Propriedades que representam valores monetários têm seus valores expressos em <b>centavos</b>. Por exemplo, <code>10390</code> significa <b>R$103,90</b> em lojas brasileiras.
-</div>
+>ℹ️ Propriedades que representam valores monetários têm seus valores expressos em **centavos**. Por exemplo, `10390` significa **R$103,90** em lojas brasileiras.
 
-<div class="alert alert-info">
-Seções que não foram solicitadas à API do Checkout são retornadas com valor <code>null</code>.
-</div>
+>ℹ️ Seções que não foram solicitadas à API do Checkout são retornadas com valor `null`.
 
 ## Seções do OrderForm
 
diff --git a/docs/faq/pt/visa-checkout-orders-do-not-appear-in-my-orders-section.md b/docs/faq/pt/visa-checkout-orders-do-not-appear-in-my-orders-section.md
index c7a580150..6ec9046fd 100644
--- a/docs/faq/pt/visa-checkout-orders-do-not-appear-in-my-orders-section.md
+++ b/docs/faq/pt/visa-checkout-orders-do-not-appear-in-my-orders-section.md
@@ -20,6 +20,4 @@ Com isso, os clientes que realizam uma primeira compra na loja não têm o seu p
 
 Para clientes já cadastrados na loja, é possível acessar a seção de __Meus Pedidos__ e ver todos os pedidos realizados, inclusive os fechados pelo Visa Checkout. 
 
-<div class="alert alert-info">
-O e-mail do cliente salvo na VTEX deve ser o mesmo que o utilizado para login no Visa Checkout para que ele possa visualizar estes pedidos na seção de <strong>Meus Pedidos</strong>.
-</div>
+>ℹ️ O e-mail do cliente salvo na VTEX deve ser o mesmo que o utilizado para login no Visa Checkout para que ele possa visualizar estes pedidos na seção de **Meus Pedidos**.
diff --git a/docs/faq/pt/vtex-support-brazil.md b/docs/faq/pt/vtex-support-brazil.md
index bee1adc1d..c13996d38 100644
--- a/docs/faq/pt/vtex-support-brazil.md
+++ b/docs/faq/pt/vtex-support-brazil.md
@@ -16,7 +16,7 @@ legacySlug: suporte-vtex-brasil
 
 Este artigo apresenta a disponibilidade, SLA e recursos de suporte adicionais disponíveis para clientes atendidos por nossos escritórios no **Brasil**. Para uma perspectiva mais ampla de nossos recursos de suporte global, consulte: [Como funciona o suporte VTEX?](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe)
 
-<div class="alert alert-info">Se a equipe de Suporte identificar que um chamado foi aberto incorretamente, será recomendado o recurso mais apropriado a ser utilizado, e essa avaliação poderá ser feita em qualquer momento durante o processo de resolução.</div>
+>ℹ️ Se a equipe de Suporte identificar que um chamado foi aberto incorretamente, será recomendado o recurso mais apropriado a ser utilizado, e essa avaliação poderá ser feita em qualquer momento durante o processo de resolução.
 
 ## Disponibilidade e SLA de atendimento
 
@@ -72,7 +72,7 @@ Nosso acordo de nível de serviço (SLA de atendimento) para o tempo de primeira
 
 Note que nosso cálculo do tempo de primeira resposta é baseado em horas úteis. Os critérios de prioridade de chamados são definidos na seção a seguir.
 
-<div class="alert alert-warning">A <a href="#prioridade-de-chamados">prioridade de um chamado</a> poderá ser alterada a qualquer momento, caso nosso time avalie que um chamado foi aberto com prioridade incompatível com as descrições da tabela acima.</div>
+>⚠️ A [prioridade de um chamado](#prioridade-de-chamados) poderá ser alterada a qualquer momento, caso nosso time avalie que um chamado foi aberto com prioridade incompatível com as descrições da tabela acima.
 
 ## Prioridade de chamados
 
diff --git a/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md b/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md
index f0f17662b..3fc9c92aa 100644
--- a/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md
+++ b/docs/faq/pt/why-cant-i-see-my-carrier-on-checkout.md
@@ -26,9 +26,7 @@ No momento de cadastro de uma transportadora, é preciso incluir o [método de e
 
 O checkout exibe sempre a transportadora mais rápida/barata entre as opções de um mesmo métodos de envio. Assim, uma transportadora não aparece no checkout quando outra do mesmo tipo tem menor prazo/custo cadastrado.
 
-<div class="alert alert-warning">
-O critério de desempate na concorrência entre transportadoras é a priorização do menor custo de envio.
-</div>
+>⚠️ O critério de desempate na concorrência entre transportadoras é a priorização do menor custo de envio.
 
 ### Solução
 
@@ -78,7 +76,5 @@ Para melhorar a experiência de compra do cliente, a funcionalidade **Otimizaç
 
 Desabilitar a função [Otimização das opções de entrega no Checkout](https://help.vtex.com/pt/tutorial/otimizacao-das-opcoes-de-entrega-no-checkout--6DeGO9eBSFWe4XkoS0SxAB) em sua loja. 
 
-<div class="alert alert-warning">
-Ao desabilitar esta função no Admin VTEX, todas as opções disponíveis de entrega serão exibidas no processo do Checkout. Entretanto, caso a funcionalidade de <a href="https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#">múltiplas entregas</a> esteja habilitada na loja e existam opções de entrega diferentes entre os itens selecionados no carrinho, as <b>Opções de entrega otimizadas</b> continuarão a ser exibidas. Ou seja, a otimização de entrega será necessária para lidar com os múltiplos pacotes (itens com diferentes opções de entrega).
-</div>
+>⚠️ Ao desabilitar esta função no Admin VTEX, todas as opções disponíveis de entrega serão exibidas no processo do Checkout. Entretanto, caso a funcionalidade de [múltiplas entregas](https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#) esteja habilitada na loja e existam opções de entrega diferentes entre os itens selecionados no carrinho, as **Opções de entrega otimizadas** continuarão a ser exibidas. Ou seja, a otimização de entrega será necessária para lidar com os múltiplos pacotes (itens com diferentes opções de entrega).
 
diff --git a/docs/faq/pt/why-doesnt-authentication-with-appkey-and-apptoken-work.md b/docs/faq/pt/why-doesnt-authentication-with-appkey-and-apptoken-work.md
index 63becc97c..d596d8ef3 100644
--- a/docs/faq/pt/why-doesnt-authentication-with-appkey-and-apptoken-work.md
+++ b/docs/faq/pt/why-doesnt-authentication-with-appkey-and-apptoken-work.md
@@ -24,9 +24,7 @@ Todo par de appKey e appToken quando criado não é vinculado a um perfil de ace
 
 Um dos motivos de erro na autenticação pode ser a falta de vínculo das chaves criadas a um perfil de acesso. Outro possível erro é a vinculação do appKey e appToken um perfil que, embora cadastrado, não tenha acesso para exercer determinada ação na plataforma.
 
-<div class="alert alert-info">
-Apenas o <a href="https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy">usuário Titular</a> tem permissão para manipular as chaves, isso é, criar a appKey e o appToken usados em integrações com a loja.
-</div>
+>ℹ️ Apenas o [usuário Titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy) tem permissão para manipular as chaves, isso é, criar a appKey e o appToken usados em integrações com a loja.
 
 ## Erro de digitação
 
@@ -34,7 +32,5 @@ Ambas chaves devem ser preenchidas nos seus respectivos campos, sem espaçamento
 
 Você pode verificar possíveis erros de digitação nos campos no módulo __Gerenciamento de conta__, em [Usuários](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512). 
 
-<div class="alert alert-warning">
-O appToken é exibido para o usuário apenas no momento da sua criação, não podendo ser recuperado posteriormente.
-</div>
+>⚠️ O appToken é exibido para o usuário apenas no momento da sua criação, não podendo ser recuperado posteriormente.
 
diff --git a/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md b/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
index d18055455..893b4d375 100644
--- a/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
+++ b/docs/faq/pt/why-has-my-product-been-wrongly-categorized-on-mercado-livre.md
@@ -36,7 +36,5 @@ Ao finalizar a planilha, você deve enviá-la ao assessor da sua conta __no Merc
 
 Caso você __não__ possua um assessor de conta no Mercado Livre, só vai ser possível alterar as categorias dos anúncios através do MyML (front do MELI) e somente em casos de produtos que __não__ tenham nenhuma venda.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> vale ressaltar que esse processo não tem nenhuma relação com a VTEX e deve ser intermediado diretamente com o Mercado Livre.
-</div>
+>⚠️ **OBS:** vale ressaltar que esse processo não tem nenhuma relação com a VTEX e deve ser intermediado diretamente com o Mercado Livre.
 
diff --git a/docs/faq/pt/why-i-do-not-receive-my-abandoned-cart-emails.md b/docs/faq/pt/why-i-do-not-receive-my-abandoned-cart-emails.md
index 8028260e3..4b4efa75f 100644
--- a/docs/faq/pt/why-i-do-not-receive-my-abandoned-cart-emails.md
+++ b/docs/faq/pt/why-i-do-not-receive-my-abandoned-cart-emails.md
@@ -46,6 +46,4 @@ No caso de Carrinho Abandonado, é importante configurar dois filtros: “Checko
 
 Depois da verificação, é imprescindível salvar todas as informações feitas. Posteriormente, os emails serão enviados como o de costume. 
 
-<div class="alert alert-warning">
-Além disso, é importante ressaltar que o tempo de uma sessão dura <strong>30 minutos</strong>. Somente após esse tempo o sistema considerará o agendamento da Trigger de Carrinho Abandonado. Ou seja, o tempo considerado é o do período da sessão somado ao agendamento da Trigger.
-</div>
+>⚠️ Além disso, é importante ressaltar que o tempo de uma sessão dura **30 minutos**. Somente após esse tempo o sistema considerará o agendamento da Trigger de Carrinho Abandonado. Ou seja, o tempo considerado é o do período da sessão somado ao agendamento da Trigger.
diff --git a/docs/faq/pt/why-is-my-stock-negative.md b/docs/faq/pt/why-is-my-stock-negative.md
index 4ead41073..20a4fa980 100644
--- a/docs/faq/pt/why-is-my-stock-negative.md
+++ b/docs/faq/pt/why-is-my-stock-negative.md
@@ -36,7 +36,5 @@ Para ajustar este cenário, o estoque do item deve ser atualizado com a quantida
 4. Na coluna __Atualizar contagem__, preencha com o valor indicado na descrição acima.
 5. Clique em __Salvar__.
 
-<div class="alert alert-warning">
-  Quando dois ou mais estoques utilizam a mesma <a href="https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">política comercial</a> e há uma quantidade negativa de unidades em um desses estoques, o SKU fica indisponível para venda, mesmo que exista uma quantidade disponível em um dos estoques no <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">inventário</a>.
-</div>
+>⚠️ Quando dois ou mais estoques utilizam a mesma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) e há uma quantidade negativa de unidades em um desses estoques, o SKU fica indisponível para venda, mesmo que exista uma quantidade disponível em um dos estoques no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
diff --git a/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md b/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
index 7510b5e9d..62e633d5e 100644
--- a/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
+++ b/docs/faq/pt/why-is-the-product-not-visible-on-the-website.md
@@ -30,10 +30,9 @@ Este artigo explica os principais meios de investigar no Admin VTEX o que deve s
 - [Logística](#logistica)
 - [CMS](#cms)
 
-<div class="alert alert-info">
-<p>Após ajustar qualquer informação de produtos e SKUs ou alterar configurações de Logística, aguarde a indexação do produto. Você pode verificar o status da indexação a partir da <a href="https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao">fila de indexação</a> em <strong>Catálogo > Relatórios > Indexação de produtos</strong>.</p>
-<p>Quando a indexação for concluída, tente acessar a página do produto por uma aba anônima no seu navegador, para visualizar a página na sua versão mais atualizada, evitando problemas com cache.</p>
-</div>
+>ℹ️ Após ajustar qualquer informação de produtos e SKUs ou alterar configurações de Logística, aguarde a indexação do produto. Você pode verificar o status da indexação a partir da [fila de indexação](https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao) em **Catálogo > Relatórios > Indexação de produtos**.
+>
+> Quando a indexação for concluída, tente acessar a página do produto por uma aba anônima no seu navegador, para visualizar a página na sua versão mais atualizada, evitando problemas com cache.
 
 ## Catálogo
 
@@ -59,10 +58,9 @@ Para verificar as configurações do produto, é importante seguir os passos aba
    * **Marca:** confira o nome da marca associada ao produto e observe se ela está ativa.
    * **Categoria:** confira o nome da categoria associada ao produto e observe se ela está ativa.
 
-   <div class="alert alert-warning">
-      <p>Ao criar um novo produto, é preciso associá-lo a uma marca e uma categoria que estejam ativas para que ele seja ativado pela primeira vez. Porém, uma vez que um produto já existe e já está ativo, desativar a categoria e a marca não vai desativá-lo por completo.</p>
-<p>O produto com categoria e marca inativas se torna invisível na loja, ou seja, não aparece na busca e não tem página própria. Para torná-lo indisponível para compra, também é necessário zerar a sua quantidade em estoque.</p>
-   </div>
+   >⚠️ Ao criar um novo produto, é preciso associá-lo a uma marca e uma categoria que estejam ativas para que ele seja ativado pela primeira vez. Porém, uma vez que um produto já existe e já está ativo, desativar a categoria e a marca não vai desativá-lo por completo.
+>
+> O produto com categoria e marca inativas se torna invisível na loja, ou seja, não aparece na busca e não tem página própria. Para torná-lo indisponível para compra, também é necessário zerar a sua quantidade em estoque.
    * **Políticas Comerciais:** veja se o produto está associado a uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Caso não esteja, use a caixa de seleção para marcar a política comercial em que deseja incluí-lo.
    * **Data de lançamento no mercado:** confira se a data de lançamento no mercado está correta. Se for uma data futura, o produto só será exibido no site na data indicada.
    * **Exibir no site:** verifique se a opção **Sim** está marcada. Caso contrário, o produto não será exibido.
@@ -131,10 +129,9 @@ Um SKU ativo e sem erros terá o registro no indexador similar ao ilustrado a se
 
 ![11-indexed-info-code-active](https://images.ctfassets.net/alneenqid6w5/3Sd3Ta5gzKo0LY9dMHmCqp/a5c498ba9733244ba7d9c85cd02d801c/11-indexed-info-code-active.png)
 
-<div class="alert alert-info">
-<p>Se as informações de indexação não apontarem nenhum motivo para a indisponibilidade dos produtos e se você não tiver encontrado nenhum erro no cadastro dos produtos e dos SKUs, é possível que reindexar o produto resolva o problema.</p>
-<p>Para isso, altere algum campo dentro do cadastro do produto ou de um dos seus SKUs e salve suas alterações. Isso forçará a reindexação.</p>
-</div>
+>ℹ️ Se as informações de indexação não apontarem nenhum motivo para a indisponibilidade dos produtos e se você não tiver encontrado nenhum erro no cadastro dos produtos e dos SKUs, é possível que reindexar o produto resolva o problema.
+>
+> Para isso, altere algum campo dentro do cadastro do produto ou de um dos seus SKUs e salve suas alterações. Isso forçará a reindexação.
 
 ## Preços
 
@@ -177,9 +174,7 @@ O **Simulador de envio** serve para verificar se o item existe em estoque e se s
 
 ![13-simular-frete-pt](https://images.ctfassets.net/alneenqid6w5/rJE0n5ZijrAerIWzzf2Gy/4acf4052c5e41e259ef8374afae39472/13-simular-frete-pt.png)
 
-<div class="alert alert-info">
-<p>Para investigar um item específico, você deve realizar essa simulação com um <strong>Código postal</strong> atendido por todas as <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Políticas de envio</a> cadastradas, pois saberá que, se o item não estiver disponível para esse CEP, não estará disponível para nenhum outro.</p>
-</div>
+>ℹ️ Para investigar um item específico, você deve realizar essa simulação com um **Código postal** atendido por todas as [Políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) cadastradas, pois saberá que, se o item não estiver disponível para esse CEP, não estará disponível para nenhum outro.
 
 O resultado obtido indica se o produto está disponível ou não para entrega no endereço informado e quais são as melhores opções de frete. Exemplo: caso não existam itens suficientes disponíveis em estoque, o simulador apresenta a seguinte mensagem:
 
@@ -212,9 +207,7 @@ Para mais informações, leia o tutorial [Gerenciar inventário](https://help.vt
 
 Se o seu produto não aparecer no site mesmo após verificar todas as configurações de **Catálogo**, **Preços **e **Logística**, é importante conferir o [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC) da sua loja. A seguir, veja como investigar se o [binding](https://help.vtex.com/pt/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W) da sua loja está correto e verifique as configurações específicas para [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) e [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2).
 
-<div class="alert alert-warning">
-<p>Para realizar a investigação no CMS descrita a seguir, é necessário solicitar apoio da equipe de desenvolvedores responsável pela sua loja.</p>
-</div>
+>⚠️ Para realizar a investigação no CMS descrita a seguir, é necessário solicitar apoio da equipe de desenvolvedores responsável pela sua loja.
 
 ### Binding
 
diff --git a/docs/faq/pt/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md b/docs/faq/pt/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
index 66968d80a..b27eb0b66 100644
--- a/docs/faq/pt/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
+++ b/docs/faq/pt/why-was-an-order-cancelled-when-its-status-was-shown-as-preparando-entrega.md
@@ -22,7 +22,5 @@ Quando o cancelamento acontece, o lojista é notificado por meio do [VTEX DO](ht
 
 2) Caso deseje prosseguir com a entrega, siga o procedimento normal de faturamento, informando ao cliente sobre a impossibilidade de cancelar o pedido.
 
-<div class="alert alert-danger">
-Apenas no status <code>Carência para cancelamento</code> a solicitação de cancelamento do cliente é unilateral, não cabendo ao lojista qualquer confirmação. Nos outros status, o lojista será informado sobre a solicitação através do VTEX DO.
-</div>
+>❗ Apenas no status `Carência para cancelamento` a solicitação de cancelamento do cliente é unilateral, não cabendo ao lojista qualquer confirmação. Nos outros status, o lojista será informado sobre a solicitação através do VTEX DO.
 
diff --git a/docs/faq/pt/why-was-not-an-order-sent-to-the-anti-fraud.md b/docs/faq/pt/why-was-not-an-order-sent-to-the-anti-fraud.md
index 83ff21094..38bdd7b8b 100644
--- a/docs/faq/pt/why-was-not-an-order-sent-to-the-anti-fraud.md
+++ b/docs/faq/pt/why-was-not-an-order-sent-to-the-anti-fraud.md
@@ -18,8 +18,6 @@ Sempre que um pagamento é realizado, o conector do gateway de pagamento realiza
 
 Após diversas tentativas, caso não obtenha as respostas esperadas, o pagamento e o pedido são cancelados. Os pedidos nesta situação não são enviados para o antifraude.
 
-<div class="alert alert-warning">
-Não é possível reenviar um pedido cancelado para o antifraude.
-</div>
+>⚠️ Não é possível reenviar um pedido cancelado para o antifraude.
 
 
diff --git a/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md b/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
index 261a1e246..079055e8f 100644
--- a/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
+++ b/docs/faq/pt/why-was-the-user-id-requested-at-checkout-when-the-purchase-was-concluded.md
@@ -22,9 +22,7 @@ Como o SmartCheckout permite fechar uma compra apenas com o e-mail e com o CVV d
 
 Ou seja, caso o cliente finalize a compra apenas com o e-mail e o CVV do cartão de crédito e a autorização da operadora não ocorra em até 3 vezes seguidas, é mostrada a tela de login para que o cliente continue tentando comprar. Essa contagem volta ao início quando o cliente fizer o login e finalizar sua compra com sucesso.
 
-<div class="alert alert-warning">
-A solicitação de uma nova autenticação ao cliente está únicamente relacionada ao limite estabelecido de 3 tentativas de compra sem sucesso com o mesmo cartão. Isso quer dizer que, <strong>independentemente do intervalo de tempo entre cada tentativa, a autenticação será solicitada quando o cliente tentar pela terceira vez finalizar uma compra sem sucesso.</strong>
-</div>
+>⚠️ A solicitação de uma nova autenticação ao cliente está únicamente relacionada ao limite estabelecido de 3 tentativas de compra sem sucesso com o mesmo cartão. Isso quer dizer que, **independentemente do intervalo de tempo entre cada tentativa, a autenticação será solicitada quando o cliente tentar pela terceira vez finalizar uma compra sem sucesso.**
 
 Essa medida visa à segurança dos dados dos clientes contra ataques e tentativas de fraudes.
 
diff --git a/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
index 565eabfaa..f52611098 100644
--- a/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/en/error-when-running-vtex-link-for-the-first-time.md
@@ -36,7 +36,5 @@ The error authorization message can change from `node`to `react` according to th
 1. Fill out this [form](https://suportevtex1.typeform.com/to/SxXknn) 
 2. Access your Account Management module and make sure that your profile has VTEX IO Admin permissions.
 
-<div class="alert alert-info">
-Filling out the form does not guarantee Node + GraphQL and Extensibility Whitelist access.
-</div>
+>ℹ️ Filling out the form does not guarantee Node + GraphQL and Extensibility Whitelist access.
 
diff --git a/docs/known-issues/en/manual-sorting-of-collections-doesnt-work-as-expected.md b/docs/known-issues/en/manual-sorting-of-collections-doesnt-work-as-expected.md
index e4fcdcae0..b124f60d0 100644
--- a/docs/known-issues/en/manual-sorting-of-collections-doesnt-work-as-expected.md
+++ b/docs/known-issues/en/manual-sorting-of-collections-doesnt-work-as-expected.md
@@ -26,8 +26,7 @@ Manual sorting of collections doesn't work as expected. There are two ways to so
 
 In both cases, the system supports sorting up to **30** SKUs of the collection. When the collection has more than 30 SKUs, all spare SKUs will be listed BEFORE those positioned between 1 and 30.
 
-<div class="alert alert-info">
-  <p>This behavior is observed in all VTEX stores, including those developed using VTEX IO. Additionally, the sorting order provided by collections is not used by VTEX Intelligent Search.</p></div>
+>ℹ️ This behavior is observed in all VTEX stores, including those developed using VTEX IO. Additionally, the sorting order provided by collections is not used by VTEX Intelligent Search.
 
 
 ## Simulation
diff --git a/docs/known-issues/en/sms-configuration-in-message-centre-module-returns-an-error.md b/docs/known-issues/en/sms-configuration-in-message-centre-module-returns-an-error.md
index 83bfb02b7..5da43328d 100644
--- a/docs/known-issues/en/sms-configuration-in-message-centre-module-returns-an-error.md
+++ b/docs/known-issues/en/sms-configuration-in-message-centre-module-returns-an-error.md
@@ -22,9 +22,7 @@ When configuring SMS sending in the message centre module, the UI returns an err
 
 ## Simulation
 
-<div class="alert alert-info">
-You need to have the movile APP installed in order to simulate the error.
-</div>
+>ℹ️ You need to have the movile APP installed in order to simulate the error.
 
 1. Access the message centre module
 2. Select the MOVILE SMS option
diff --git a/docs/known-issues/es/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md b/docs/known-issues/es/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md
index 4582e6638..cc0c3fb39 100644
--- a/docs/known-issues/es/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md
+++ b/docs/known-issues/es/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md
@@ -18,9 +18,7 @@ internalReference: 452392
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un cliente introduce un cardNumber de 12 dígitos, a pesar de que este número de dígitos no es válido, lo enviamos varias veces a la entidad adquirente aún sabiendo que no lo aprobará ya que el cardNumber no está en el patrón: [0-9]{13,19}. El resultado es un pedido atascado durante varios días hasta ser cancelado.
diff --git a/docs/known-issues/es/403-error-for-all-urls-containing-develop.md b/docs/known-issues/es/403-error-for-all-urls-containing-develop.md
index 5f0cd53b3..92d5f8228 100644
--- a/docs/known-issues/es/403-error-for-all-urls-containing-develop.md
+++ b/docs/known-issues/es/403-error-for-all-urls-containing-develop.md
@@ -18,9 +18,7 @@ internalReference: 975182
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera que una URL pueda contener cualquier palabra sin generar un error, pero la palabra "**desarrollar "** seguida del carácter "**-**" genera un error 403 automático.
diff --git a/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
index 55c776f4a..93ad94a16 100644
--- a/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
+++ b/docs/known-issues/es/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -18,9 +18,7 @@ internalReference: 931324
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera que una SKU activa tenga marcada la opción "activar si es posible", sin embargo, no siempre es así.
diff --git a/docs/known-issues/es/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md b/docs/known-issues/es/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md
index 5c2891d1d..efc25af4a 100644
--- a/docs/known-issues/es/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md
+++ b/docs/known-issues/es/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md
@@ -18,9 +18,7 @@ internalReference: 712575
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Todo el almacenamiento en caché combinado con la función de fecha de caducidad puede causar un comportamiento muy extraño para nuestros compradores durante el pago. Los mayores problemas provienen de la forma en que la pasarela indexa los métodos de pago:
diff --git a/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md b/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
index d22f83c38..7c875d18d 100644
--- a/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
+++ b/docs/known-issues/es/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
@@ -18,9 +18,7 @@ internalReference: 966499
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera que el administrador de especificaciones de producto siempre muestre los valores correctos para las especificaciones de un producto. Sin embargo, puede que no siempre sea así.
diff --git a/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md b/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
index eb0ae658d..f401dd89e 100644
--- a/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
+++ b/docs/known-issues/es/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
@@ -18,9 +18,7 @@ internalReference: 865727
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La aplicación AB Tester muestra información mal calculada para las sesiones y la conversión al ejecutar las pruebas, lo que provoca una interpretación no deseada de los resultados. La funcionalidad de división del espacio de trabajo sigue funcionando como se esperaba.
diff --git a/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md b/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
index 7f5a54d12..248506a9f 100644
--- a/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
+++ b/docs/known-issues/es/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
@@ -18,9 +18,7 @@ internalReference: 793570
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si el nombre de la cuenta es algo como `mi-cuenta` el informe de búsqueda no recibe datos. Incluso con los eventos correctamente configurados.
diff --git a/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md b/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
index b48048103..439298559 100644
--- a/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
+++ b/docs/known-issues/es/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
@@ -18,9 +18,7 @@ internalReference: 339894
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, en la usabilidad de importación de SkuVincularValorServico.aspx, cuando se intenta cambiar los servicios previamente salidos de inactivos a activos, los valores no se cambian. La interfaz de usuario indica que se han cambiado los valores, pero en realidad no ocurre nada.
diff --git a/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md b/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md
index dfc3e92ef..4283b83fd 100644
--- a/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md
+++ b/docs/known-issues/es/adding-a-new-address-on-invoice-address-returns-null-api-results.md
@@ -18,9 +18,7 @@ internalReference: 748668
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay más de una dirección registrada en el Sistema de Perfiles, se produce una petición "nula" al servicio de código postal si se añade una nueva dirección en "Dirección de Facturación".
diff --git a/docs/known-issues/es/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md b/docs/known-issues/es/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md
index 27abb0ddd..7dd6be355 100644
--- a/docs/known-issues/es/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md
+++ b/docs/known-issues/es/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md
@@ -18,9 +18,7 @@ internalReference: 618724
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El botón "calcular envío", utilizado para la validación de la dirección en el modo de geolocalización (dirección insertada a través de Google Maps), se está mostrando incluso para direcciones completas. Debería mostrarse solo para las direcciones editadas -por cambio de información o por direcciones que estaban incompletas en un primer momento- para asegurar que son válidas, pero no para las direcciones completas.
diff --git a/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md b/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
index 92c0983be..07cff81b5 100644
--- a/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
+++ b/docs/known-issues/es/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
@@ -18,9 +18,7 @@ internalReference: 1061637
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, cuando un comprador identificado intenta añadir una nueva dirección en el paso de envío de la caja, se solicita un mensaje que requiere autenticación, pero el formulario de dirección no se muestra y no se puede rellenar.
diff --git a/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md b/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
index 7416e2e45..073ac524c 100644
--- a/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
+++ b/docs/known-issues/es/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
@@ -18,9 +18,7 @@ internalReference: 287854
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 En algunos casos, la API de Checkout utiliza "::" como separador cuando hay varias posibilidades de ciudades desde el servicio de código postal, provocando un error por tamaño excesivo en el campo dirección, afectando a la realización del pedido. Este comportamiento ocurre porque la API tiene un autocompletado para la dirección
 
diff --git a/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md b/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md
index d25dc173f..e8acf2819 100644
--- a/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md
+++ b/docs/known-issues/es/address-review-flow-is-removing-essential-address-information.md
@@ -18,9 +18,7 @@ internalReference: 618756
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La validación de la dirección en el modo de geolocalización (dirección insertada a través de Google Maps) está eliminando información esencial, como la calle y el número, de las direcciones válidas, afectando al flujo de compra.
diff --git a/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
index 5f1940868..98054c439 100644
--- a/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
+++ b/docs/known-issues/es/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -18,9 +18,7 @@ internalReference: 1037067
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un rol tiene el permiso "Puede añadir envío" en la Configuración de Pago B2B y un comprador tiene direcciones registradas en el Sistema de Perfiles, al hacer clic en "Entregar en otra dirección" en el paso de envío y hacer clic en "Volver a la lista de direcciones" se muestran las direcciones del Sistema de Perfiles.
diff --git a/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md b/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
index 3ecaa8a32..a1c7b6949 100644
--- a/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
+++ b/docs/known-issues/es/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
@@ -18,9 +18,7 @@ internalReference: 860375
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el comprador tiene direcciones registradas en el Sistema de Perfiles, y es suplantado utilizando VTEX Telemarketing, se muestran las direcciones del Sistema de Perfiles y Organizaciones
diff --git a/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
index cbf7d5ab5..e7eeb851b 100644
--- a/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
+++ b/docs/known-issues/es/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -18,9 +18,7 @@ internalReference: 992503
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El adjunto del carrito `shippingData` soporta el campo `addressId` dentro de algunos objetos diferentes: `logisticsInfo`, `address`, y `selectedAddresses`.
diff --git a/docs/known-issues/es/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md b/docs/known-issues/es/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
index 691f1cb1c..da2221407 100644
--- a/docs/known-issues/es/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
+++ b/docs/known-issues/es/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
@@ -18,9 +18,7 @@ internalReference: 830495
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función addToCart no funciona correctamente cuando un producto tiene configuradas opciones de montaje y anexos y uno de los componentes de las opciones de montaje también tiene anexos. Sólo se añadirá al carrito el adjunto del componente.
diff --git a/docs/known-issues/es/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md b/docs/known-issues/es/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md
index baa7b618a..cf72a8764 100644
--- a/docs/known-issues/es/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md
+++ b/docs/known-issues/es/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md
@@ -18,9 +18,7 @@ internalReference: 600208
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Ajustar el mensaje en el puente para la integración con el vendedor WL
diff --git a/docs/known-issues/es/adjust-processing-tab-export.md b/docs/known-issues/es/adjust-processing-tab-export.md
index af5970fdb..2dfecb927 100644
--- a/docs/known-issues/es/adjust-processing-tab-export.md
+++ b/docs/known-issues/es/adjust-processing-tab-export.md
@@ -18,9 +18,7 @@ internalReference: 649311
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La exportación en la pestaña de procesamiento de skus está fallando:
diff --git a/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md b/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
index 9cb40d278..ffbf81a59 100644
--- a/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
+++ b/docs/known-issues/es/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
@@ -18,9 +18,7 @@ internalReference: 599380
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Ajustar la consulta de envío cuando el pedido tiene más de un producto
diff --git a/docs/known-issues/es/admin-collection-brand-list-timeout.md b/docs/known-issues/es/admin-collection-brand-list-timeout.md
index 8ad7a5884..b61d716b2 100644
--- a/docs/known-issues/es/admin-collection-brand-list-timeout.md
+++ b/docs/known-issues/es/admin-collection-brand-list-timeout.md
@@ -18,9 +18,7 @@ internalReference: 639905
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, para las tiendas que tienen más de 4000 marcas en su catálogo, el siguiente listado de marcas no carga ninguna marca cuando se intenta crear una nueva colección:
diff --git a/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
index 1e011d417..2ca94e85c 100644
--- a/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
+++ b/docs/known-issues/es/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -18,9 +18,7 @@ internalReference: 969645
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Búsqueda Global no reconoce los "Elementos del Menú de Perfil"
diff --git a/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md b/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
index 31c58ba0d..720483945 100644
--- a/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
+++ b/docs/known-issues/es/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
@@ -18,9 +18,7 @@ internalReference: 516269
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la página de exportación de imágenes o en el informe de imágenes exportadas, la URL de las imágenes aparece con la extensión .jpg incluso cuando la imagen es PNG. Sin embargo, la información incorrecta en el Admin no afecta al formato real de la imagen, y accediendo a la URL de la imagen desde el frente se puede ver que la imagen sigue siendo PNG.
diff --git a/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md b/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
index 8f714bc0d..7b9edae19 100644
--- a/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
+++ b/docs/known-issues/es/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
@@ -18,9 +18,7 @@ internalReference: 889045
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El módulo de Datos Maestros, el motor de búsqueda admin los redirige a la URL equivocada.
diff --git a/docs/known-issues/es/admin-review-global-search.md b/docs/known-issues/es/admin-review-global-search.md
index 5f2712586..39dc5e8cc 100644
--- a/docs/known-issues/es/admin-review-global-search.md
+++ b/docs/known-issues/es/admin-review-global-search.md
@@ -18,9 +18,7 @@ internalReference: 889993
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 la búsqueda global no encuentra información sobre "usuarios"
diff --git a/docs/known-issues/es/admin-timeout.md b/docs/known-issues/es/admin-timeout.md
index e7d22d78c..e34d82afe 100644
--- a/docs/known-issues/es/admin-timeout.md
+++ b/docs/known-issues/es/admin-timeout.md
@@ -18,9 +18,7 @@ internalReference: 1051070
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La aplicación de mensajes está recibiendo un error de tiempo de espera al azar y algunas páginas de administración pueden necesitar una actualización para funcionar correctamente.
diff --git a/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md b/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md
index 925902ead..b8822e179 100644
--- a/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md
+++ b/docs/known-issues/es/adress-without-country-disrupting-orderform-changes.md
@@ -18,9 +18,7 @@ internalReference: 579814
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si se inserta una dirección incompleta sin la información del "país" en un orderForm, no se pueden añadir artículos al mismo.
diff --git a/docs/known-issues/es/advanced-store-settings-being-registered-globally-insted-of-by-binding.md b/docs/known-issues/es/advanced-store-settings-being-registered-globally-insted-of-by-binding.md
index c99d14508..a54acd03a 100644
--- a/docs/known-issues/es/advanced-store-settings-being-registered-globally-insted-of-by-binding.md
+++ b/docs/known-issues/es/advanced-store-settings-being-registered-globally-insted-of-by-binding.md
@@ -18,9 +18,7 @@ internalReference: 783835
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md b/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md
index 040a135bb..14c830254 100644
--- a/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md
+++ b/docs/known-issues/es/adyen-3ds2-double-request-generates-payment-authorization-denial.md
@@ -18,9 +18,7 @@ internalReference: 884154
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la solicitud 3DS2 de Adyen se envía dos veces, obtiene un error en la respuesta y el pago se deniega automáticamente.
diff --git a/docs/known-issues/es/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md b/docs/known-issues/es/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md
index 222849787..fa83be6a6 100644
--- a/docs/known-issues/es/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md
+++ b/docs/known-issues/es/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md
@@ -18,9 +18,7 @@ internalReference: 758411
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md b/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
index 00f96dd1b..c52857018 100644
--- a/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
+++ b/docs/known-issues/es/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
@@ -18,9 +18,7 @@ internalReference: 920563
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Aunque Apple Pay permite al usuario realizar un pedido utilizando una tarjeta Amex, nuestro conector heredado AdyenV1 no es compatible con esta marca.
diff --git a/docs/known-issues/es/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md b/docs/known-issues/es/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md
index ecf0e8662..e8144a4da 100644
--- a/docs/known-issues/es/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md
+++ b/docs/known-issues/es/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md
@@ -18,9 +18,7 @@ internalReference: 486752
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la transacción es reconocida por el proveedor y el estado nunca cambia de indefinido, AdyenV2 está requiriendo una pspReference para cancelar la transacción. Este no es un comportamiento esperado porque este campo no existe en la APP, por lo que el cliente se queda atascado en el modal PIX en la interfaz de pago.
diff --git a/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md b/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
index fb6c31457..defe15fe6 100644
--- a/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
+++ b/docs/known-issues/es/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
@@ -18,9 +18,7 @@ internalReference: 565982
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md b/docs/known-issues/es/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md
index 93077055a..ad06f865a 100644
--- a/docs/known-issues/es/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md
+++ b/docs/known-issues/es/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md
@@ -18,9 +18,7 @@ internalReference: 519576
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para los flujos de devolución dentro de un pedido, es posible indicar qué productos serán devueltos y/o los valores asociados, como los gastos de envío o simplemente una parte del valor del pedido.
diff --git a/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index 1a5443391..6fde1c6f0 100644
--- a/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/es/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -18,19 +18,13 @@ internalReference: 526563
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/amazon-category-implementation.md b/docs/known-issues/es/amazon-category-implementation.md
index 9cb1931ee..d06109f3f 100644
--- a/docs/known-issues/es/amazon-category-implementation.md
+++ b/docs/known-issues/es/amazon-category-implementation.md
@@ -18,9 +18,7 @@ internalReference: 549924
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md b/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
index 6a0893ec8..bd237f358 100644
--- a/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
+++ b/docs/known-issues/es/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 926656
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md b/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
index 39ee89d2e..343e6e742 100644
--- a/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
+++ b/docs/known-issues/es/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
@@ -18,9 +18,7 @@ internalReference: 990197
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Error en el flujo de actualización sku no se está registrando en el puente
diff --git a/docs/known-issues/es/amazon-global-category-not-working.md b/docs/known-issues/es/amazon-global-category-not-working.md
index 8d2702651..f99da6302 100644
--- a/docs/known-issues/es/amazon-global-category-not-working.md
+++ b/docs/known-issues/es/amazon-global-category-not-working.md
@@ -18,9 +18,7 @@ internalReference: 634199
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md b/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md
index bef1e9079..fe3cf0ed1 100644
--- a/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md
+++ b/docs/known-issues/es/amazon-integration-attribute-number-of-itens.md
@@ -18,9 +18,7 @@ internalReference: 557788
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-integration-is-not-cancelling-orders-in-vtex.md b/docs/known-issues/es/amazon-integration-is-not-cancelling-orders-in-vtex.md
index 0ddeac8ac..572309767 100644
--- a/docs/known-issues/es/amazon-integration-is-not-cancelling-orders-in-vtex.md
+++ b/docs/known-issues/es/amazon-integration-is-not-cancelling-orders-in-vtex.md
@@ -18,9 +18,7 @@ internalReference: 588456
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md b/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md
index 560e74009..9927a3d3a 100644
--- a/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md
+++ b/docs/known-issues/es/amazon-integration-stock-reservations-for-kits.md
@@ -18,9 +18,7 @@ internalReference: 829583
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md
index 6d0c5ba44..65dfa8db0 100644
--- a/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/es/amazon-object-reference-not-set-to-an-instance-of-an-object.md
@@ -18,9 +18,7 @@ internalReference: 482173
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazon-order-integration-error.md b/docs/known-issues/es/amazon-order-integration-error.md
index 54ae53248..d7380e0e9 100644
--- a/docs/known-issues/es/amazon-order-integration-error.md
+++ b/docs/known-issues/es/amazon-order-integration-error.md
@@ -18,9 +18,7 @@ internalReference: 557223
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md b/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md
index 9c7cc1c47..01de163e1 100644
--- a/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md
+++ b/docs/known-issues/es/amazoncasacaso-erros-de-rastreamento.md
@@ -18,9 +18,7 @@ internalReference: 360564
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Estamos teniendo problemas en algunos casos en los que el flujo de trabajo de seguimiento para Amazon no está funcionando.
diff --git a/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md b/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md
index e0d7afe1b..d00ed505f 100644
--- a/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md
+++ b/docs/known-issues/es/an-error-has-occurred-when-adding-tracking-information.md
@@ -18,9 +18,7 @@ internalReference: 409225
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Al introducir la información de seguimiento cuando el número de factura contiene espacios, se produce el siguiente error (ya sea a través de la interfaz de usuario o de la API) "`An error has occurred`".
 
diff --git a/docs/known-issues/es/analytics-duplicated-events.md b/docs/known-issues/es/analytics-duplicated-events.md
index 4892739a2..1965f9d62 100644
--- a/docs/known-issues/es/analytics-duplicated-events.md
+++ b/docs/known-issues/es/analytics-duplicated-events.md
@@ -18,9 +18,7 @@ internalReference: 771986
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/analytics-error-loading-data-in-sales-performance-dashboard.md b/docs/known-issues/es/analytics-error-loading-data-in-sales-performance-dashboard.md
index b75e0f1c8..8ec59e904 100644
--- a/docs/known-issues/es/analytics-error-loading-data-in-sales-performance-dashboard.md
+++ b/docs/known-issues/es/analytics-error-loading-data-in-sales-performance-dashboard.md
@@ -18,9 +18,7 @@ internalReference: 799899
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Error al cargar los datos en el cuadro de mandos `rendimiento de ventas
diff --git a/docs/known-issues/es/android-button-with-unexpected-behavior-with-the-enter-button.md b/docs/known-issues/es/android-button-with-unexpected-behavior-with-the-enter-button.md
index 675abef01..501431552 100644
--- a/docs/known-issues/es/android-button-with-unexpected-behavior-with-the-enter-button.md
+++ b/docs/known-issues/es/android-button-with-unexpected-behavior-with-the-enter-button.md
@@ -18,9 +18,7 @@ internalReference: 606718
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md b/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
index 6db522e89..81a579394 100644
--- a/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
+++ b/docs/known-issues/es/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
@@ -18,9 +18,7 @@ internalReference: 554948
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md b/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
index f07720a3c..0adc2f2bf 100644
--- a/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
+++ b/docs/known-issues/es/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
@@ -18,9 +18,7 @@ internalReference: 650714
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Nuestra API para listar los puntos de recogida por ubicación siempre devuelve `null` en el campo `additionalInfo`. Sin embargo, como estos datos normalmente provienen de la API de logística, estos datos están presentes en el orderForm cuando se realiza un pedido en la caja.
diff --git a/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md b/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
index c6639ec86..cf6036be8 100644
--- a/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
+++ b/docs/known-issues/es/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 712015
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md b/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md
index 300ed6585..8fa68b050 100644
--- a/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md
+++ b/docs/known-issues/es/app-settings-are-not-erased-when-you-delete-the-app.md
@@ -18,9 +18,7 @@ internalReference: 1065954
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md b/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
index 26eb093a4..a18672b40 100644
--- a/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
+++ b/docs/known-issues/es/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
@@ -18,9 +18,7 @@ internalReference: 1011071
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar la interfaz de usuario de promociones, al intentar guardar manualmente la opción "Aplicar a los artículos más caros" no funcionará y el selector permanecerá en la opción de tipo más barato.
diff --git a/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md b/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md
index 50ee62f17..de9c20111 100644
--- a/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md
+++ b/docs/known-issues/es/approved-skus-spreadsheet-not-showing-price.md
@@ -18,9 +18,7 @@ internalReference: 552155
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 cuando se utiliza la opción de exportación en la pestaña de SKUs Recibidos Aprobados, el archivo excel no tiene datos en los campos Precio de Venta, Moneda y Símbolo de Moneda.
diff --git a/docs/known-issues/es/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md b/docs/known-issues/es/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md
index 8e67ea43f..2bac8b9f2 100644
--- a/docs/known-issues/es/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md
+++ b/docs/known-issues/es/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md
@@ -18,9 +18,7 @@ internalReference: 743529
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un PDP de opciones de montaje, cuando el usuario selecciona diferentes cantidades para un mismo artículo y va al carro de la Caja la selección es ignorada y las cantidades se reinician a la cantidad inicial. Pero si el usuario aumenta, para **todos** los artículos, en 1 cantidad al menos se persiste la selección.
diff --git a/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
index e4cb3f993..670e0093a 100644
--- a/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
+++ b/docs/known-issues/es/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -18,9 +18,7 @@ internalReference: 897480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las solicitudes de actualización para la API /api/catalog/pvt/attachment/ no están permitiendo actualizaciones para el campo Valor del dominio como valor nulo.
diff --git a/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md b/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
index 662bf6686..124a0ea11 100644
--- a/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
+++ b/docs/known-issues/es/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
@@ -18,9 +18,7 @@ internalReference: 751091
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A través de la interfaz de usuario (directamente en VTEX admin) es posible crear un archivo adjunto sin el campo **Valores permitidos** lleno:
diff --git a/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md b/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
index 0a48a927a..8747c9ca6 100644
--- a/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
+++ b/docs/known-issues/es/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
@@ -18,9 +18,7 @@ internalReference: 957343
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Añadir un artículo de un vendedor con un archivo adjunto en la misma solicitud de API, la validación de archivos adjuntos se produce sólo en el mercado.
diff --git a/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md b/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
index fa86a36cf..1eae9bb12 100644
--- a/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
+++ b/docs/known-issues/es/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
@@ -18,9 +18,7 @@ internalReference: 920970
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los valores permitidos del adjunto no se actualizan si se añadió a un artículo antes de cambiar sus valores en el admin. Esto provocará un error en el carrito con el mensaje "Imposible comunicarse con el vendedor".
diff --git a/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md b/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md
index 80cd5f1b9..d208bf653 100644
--- a/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md
+++ b/docs/known-issues/es/attribute-melishippingmode-not-being-updated-in-meli-integration.md
@@ -18,9 +18,7 @@ internalReference: 873993
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
index a1a4e56ce..df4e08d26 100644
--- a/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
+++ b/docs/known-issues/es/audit-pricing-logs-showing-unknow-information.md
@@ -18,9 +18,7 @@ internalReference: 856420
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas acciones de usuario relativas a modificaciones de precios se están registrando en el módulo de auditoría como "desconocidas".
diff --git a/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md b/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
index 96db2e179..1e1aaa927 100644
--- a/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
+++ b/docs/known-issues/es/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
@@ -18,9 +18,7 @@ internalReference: 929517
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una transacción tiene múltiples pagos y se vuelve asíncrona debido al modo Sherlock o Defensa, y si el primer intento de autorización de pago falla, puede resultar en que los otros pagos se queden atascados en un estado "Autorizado". Esto se debe a que se cancela toda la transacción, pero nuestro trabajador no lo reconoce y procede con un intento de autorización para el segundo pago. En consecuencia, el segundo pago no puede ser cancelado, ya que la transacción ya ha sido cancelada, y no permite una solicitud de cancelación.
diff --git a/docs/known-issues/es/auto-approve-api-accepts-any-values.md b/docs/known-issues/es/auto-approve-api-accepts-any-values.md
index e7327f67c..4be7dd4ea 100644
--- a/docs/known-issues/es/auto-approve-api-accepts-any-values.md
+++ b/docs/known-issues/es/auto-approve-api-accepts-any-values.md
@@ -18,9 +18,7 @@ internalReference: 713704
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la API de autoaprobación no comprueba si el vendedor existe, lo que puede dar lugar a configuraciones incorrectas.
diff --git a/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md b/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md
index e65da5c0a..f0d0678ec 100644
--- a/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md
+++ b/docs/known-issues/es/autocomplete-bringing-suggestion-products-shown-with-delay.md
@@ -18,9 +18,7 @@ internalReference: 615616
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/autocomplete-hover-on-search-suggestion-is-not-working-properly.md b/docs/known-issues/es/autocomplete-hover-on-search-suggestion-is-not-working-properly.md
index ea811ecbb..17c9d50d8 100644
--- a/docs/known-issues/es/autocomplete-hover-on-search-suggestion-is-not-working-properly.md
+++ b/docs/known-issues/es/autocomplete-hover-on-search-suggestion-is-not-working-properly.md
@@ -18,19 +18,13 @@ internalReference: 697406
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md b/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md
index fb1eaf7bc..e90fc4074 100644
--- a/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md
+++ b/docs/known-issues/es/autocomplete-not-answering-to-cold-starts.md
@@ -18,9 +18,7 @@ internalReference: 418573
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función de búsqueda inteligente conocida como **autocompletar** no funciona en algunas tiendas nuevas incluso después de ejecutar un proceso interno llamado _cold start_.
diff --git a/docs/known-issues/es/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md b/docs/known-issues/es/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md
index c0a9e7fec..803b1c5d2 100644
--- a/docs/known-issues/es/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md
+++ b/docs/known-issues/es/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md
@@ -18,9 +18,7 @@ internalReference: 793275
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al buscar cualquier término sin pulsar enter, el autocompletado trae resultados de productos que contienen ese término.
diff --git a/docs/known-issues/es/autocomplete-search-not-working-with-space.md b/docs/known-issues/es/autocomplete-search-not-working-with-space.md
index e69b27c3e..5db9599f0 100644
--- a/docs/known-issues/es/autocomplete-search-not-working-with-space.md
+++ b/docs/known-issues/es/autocomplete-search-not-working-with-space.md
@@ -18,9 +18,7 @@ internalReference: 568821
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
index 51db1f306..3ed45f359 100644
--- a/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
+++ b/docs/known-issues/es/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -18,9 +18,7 @@ internalReference: 1014701
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Este problema se produce cuando se busca un término y la sugerencia de autocompletar devuelve el nombre del producto sin el carácter de punto ".", aunque exista en el nombre del producto, lo que da lugar a resultados de búsqueda incorrectos.
diff --git a/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md b/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md
index f6b8d3bb8..8afb7acfd 100644
--- a/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md
+++ b/docs/known-issues/es/automatic-payment-settlement-incorrectly-setup.md
@@ -18,9 +18,7 @@ internalReference: 1053010
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El problema es que la pasarela ignoraba el valor `delayToAutoSettleAfterAntifraud`.
diff --git a/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md b/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
index f350c1194..806f24caf 100644
--- a/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
+++ b/docs/known-issues/es/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 1062858
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
index 3928b1a50..5b943289a 100644
--- a/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
+++ b/docs/known-issues/es/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -18,9 +18,7 @@ internalReference: 773537
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un producto está agotado o no tiene precio, la simulación de cumplimiento informa incorrectamente del campo "disponibilidad" como "disponible".
diff --git a/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md b/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
index 262ccb7ee..a7b968f46 100644
--- a/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
+++ b/docs/known-issues/es/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
@@ -18,9 +18,7 @@ internalReference: 1061630
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario añade una nueva dirección durante el paso de envío de la caja, avanza al paso de pago y, a continuación, vuelve a la lista de direcciones disponibles del paso de envío, es posible que esta dirección recién creada no aparezca en la lista o que muestre información incompleta en la interfaz de usuario.
diff --git a/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md b/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
index 7fc22aa12..11777b094 100644
--- a/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
+++ b/docs/known-issues/es/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
@@ -18,9 +18,7 @@ internalReference: 1034211
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Durante el pipeline de indexación de un artículo, se realiza una simulación sin uso de código postal para validar la disponibilidad, esta simulación, cuando llega al sistema logístico, realiza una validación combinando todos los muelles, almacenes y políticas de envío disponibles para un canal de venta, la respuesta a este cálculo determina la disponibilidad del artículo, sin embargo esta respuesta tiene un límite de lectura de 10.000 rutas, por lo que cuando un cálculo da como resultado más de 10.000, el resto de rutas no se tienen en cuenta, lo que puede provocar que el sistema devuelva una respuesta inconsistente.
diff --git a/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md b/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md
index 8e298580a..15ffb72c6 100644
--- a/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md
+++ b/docs/known-issues/es/b2b-impersonated-data-is-not-removed-after-logging-out.md
@@ -18,9 +18,7 @@ internalReference: 1067969
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El cierre de sesión después de hacerse pasar por un usuario en B2B Suite no elimina los permisos de la tienda de la sesión.
diff --git a/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md b/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md
index 7c8ce38a0..51fe20994 100644
--- a/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md
+++ b/docs/known-issues/es/b2b-orders-history-doesnt-work-in-the-website-domain.md
@@ -18,9 +18,7 @@ internalReference: 849394
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El Historial de Pedidos B2B no funciona en el dominio web, mostrando el mensaje "No tiene permiso para acceder a esto".
diff --git a/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md b/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
index 155153f37..c998a3d44 100644
--- a/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
+++ b/docs/known-issues/es/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
@@ -18,9 +18,7 @@ internalReference: 904907
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Organización B2B no tiene nada para configurar una dirección cuando las cuentas usan geolocalización, causando que los artículos no estén disponibles.
diff --git a/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md b/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
index c851dfd60..ac88a6fd8 100644
--- a/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
+++ b/docs/known-issues/es/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
@@ -18,9 +18,7 @@ internalReference: 966450
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 B2B Organizations Detail UI sólo muestra 100 primeros vendedores; la UI no tiene paginación, lo que hace imposible seleccionar un vendedor si no está en la primera página.
diff --git a/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md b/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
index e64774aa6..2ad33c767 100644
--- a/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
+++ b/docs/known-issues/es/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
@@ -18,9 +18,7 @@ internalReference: 1056736
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md b/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
index 2702a1cd8..2f03a1342 100644
--- a/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
+++ b/docs/known-issues/es/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
@@ -18,9 +18,7 @@ internalReference: 849080
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una cotización tiene un descuento aplicado por un vendedor, las Cotizaciones B2B no aplicarán el descuento al momento de pagar en el dominio del sitio web.
diff --git a/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md b/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
index a2f9de87c..7f9f2dd12 100644
--- a/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
+++ b/docs/known-issues/es/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
@@ -18,9 +18,7 @@ internalReference: 1055033
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Es posible utilizar tarifas de envío utilizando códigos postales o geocoordenadas, pero las Organizaciones B2B utilizan sólo códigos postales para calcular los ID de región. Si una cuenta tiene geolocalización (polígonos) registrada en sus tarifas de envío, los productos se mostrarán como no disponibles en el escaparate.
diff --git a/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 91c692a06..b1b943cc9 100644
--- a/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/es/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -18,9 +18,7 @@ internalReference: 714879
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos de "b2wentregadirect" que deberían entrar como (FOB), pero se están integrando con el flete calculado aquí en nuestro lado.
diff --git a/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md b/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md
index d847d8eef..bb79f0459 100644
--- a/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md
+++ b/docs/known-issues/es/b2w-freight-value-in-oms-vtex.md
@@ -18,9 +18,7 @@ internalReference: 671748
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos algunos casos en los que el valor del flete no aparece en los detalles de las transacciones de pago - OMS
diff --git a/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md b/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md
index d1568290e..60a1ed249 100644
--- a/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md
+++ b/docs/known-issues/es/b2w-order-with-parameter-count-mismatch-error.md
@@ -18,9 +18,7 @@ internalReference: 776361
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas órdenes de Skyhub no se están integrando en la plataforma, debido al error `"Parameter count mismatch"`, cuando la orden no se crea en OMS (VTEX)
diff --git a/docs/known-issues/es/b2w-tracking-status-not-updated-on-skyhub.md b/docs/known-issues/es/b2w-tracking-status-not-updated-on-skyhub.md
index 6e0edcd19..e4b1bcab3 100644
--- a/docs/known-issues/es/b2w-tracking-status-not-updated-on-skyhub.md
+++ b/docs/known-issues/es/b2w-tracking-status-not-updated-on-skyhub.md
@@ -18,9 +18,7 @@ internalReference: 673597
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md b/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md
index 78efc86c6..e0cf0f596 100644
--- a/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md
+++ b/docs/known-issues/es/back-button-is-not-rendered-in-my-organization.md
@@ -18,9 +18,7 @@ internalReference: 797003
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El botón "Atrás" no se muestra en Mi Organización en los móviles, lo que impide al comprador acceder a otras opciones desde Mi Cuenta.
diff --git a/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md b/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
index b323f9555..685d3e80e 100644
--- a/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
+++ b/docs/known-issues/es/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
@@ -18,9 +18,7 @@ internalReference: 786685
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el cliente cierra una compra utilizando una tarjeta regalo y la app de pago MercadoPago, el botón "volver al sitio" no le lleva a la página de realizar pedido, sino a `/gatewayCallback//Success`.
diff --git a/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
index b695afc57..12bbb047f 100644
--- a/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/es/bad-request-when-searching-terms-with-directly-via-url.md
@@ -18,9 +18,7 @@ internalReference: 775524
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al buscar un término con "%" directamente vía URL, la página devuelve un 400 Bad Request.
diff --git a/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
index 7e31240db..c7d9488e1 100644
--- a/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
+++ b/docs/known-issues/es/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -18,9 +18,7 @@ internalReference: 978136
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al buscar un término con "#" directamente mediante autocompletar, la página nunca se carga
diff --git a/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md b/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
index 841e65975..22b5d0f8f 100644
--- a/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
+++ b/docs/known-issues/es/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
@@ -18,9 +18,7 @@ internalReference: 296066
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md b/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
index a359a1ac0..ee6fb8d5e 100644
--- a/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
+++ b/docs/known-issues/es/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
@@ -18,9 +18,7 @@ internalReference: 999476
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas páginas de resultados de búsqueda ocultan los filtros aplicados - puesto que ya forman parte de la propia página, por lo que se establecen como "initialAttributes" - para centrarse en los filtros adicionales que se pueden aplicar. En estos escenarios, los valores para el título de la página y las migas de pan están básicamente definidos por el primer producto de la página.
diff --git a/docs/known-issues/es/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md b/docs/known-issues/es/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md
index 04b2c8c5b..f14420688 100644
--- a/docs/known-issues/es/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md
+++ b/docs/known-issues/es/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md
@@ -18,9 +18,7 @@ internalReference: 566809
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/banner-scheduling-is-deactivated-after-expiry-date.md b/docs/known-issues/es/banner-scheduling-is-deactivated-after-expiry-date.md
index 75b4a767f..7f5413639 100644
--- a/docs/known-issues/es/banner-scheduling-is-deactivated-after-expiry-date.md
+++ b/docs/known-issues/es/banner-scheduling-is-deactivated-after-expiry-date.md
@@ -18,19 +18,13 @@ internalReference: 301023
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md b/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
index b4dd331e2..8ab095559 100644
--- a/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
+++ b/docs/known-issues/es/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
@@ -18,9 +18,7 @@ internalReference: 915213
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al mirar el array de beneficios dentro del ProductContextProvider en el PDP de un producto podemos ver que no se devuelven todos los productos y se barajan los que se devuelven. Ambas listas de productos dentro de la promoción están juntas en el mismo array. Esto sólo ocurre cuando la promoción es del tipo Buy Together.
diff --git a/docs/known-issues/es/bin-sent-does-not-match-an-associated-card-brand.md b/docs/known-issues/es/bin-sent-does-not-match-an-associated-card-brand.md
index 6d1099cef..74bc5a8c3 100644
--- a/docs/known-issues/es/bin-sent-does-not-match-an-associated-card-brand.md
+++ b/docs/known-issues/es/bin-sent-does-not-match-an-associated-card-brand.md
@@ -18,9 +18,7 @@ internalReference: 308896
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La plataforma permite enviar un BIN con la bandera de otra marca de tarjeta. Por ejemplo: Se puede informar de un BIN de VISA, pero se puede marcar la bandera de la marca de tarjeta Mastercard.
diff --git a/docs/known-issues/es/block-selector-not-working-at-site-editor-home-page.md b/docs/known-issues/es/block-selector-not-working-at-site-editor-home-page.md
index b0a30bf21..02534fb0b 100644
--- a/docs/known-issues/es/block-selector-not-working-at-site-editor-home-page.md
+++ b/docs/known-issues/es/block-selector-not-working-at-site-editor-home-page.md
@@ -18,9 +18,7 @@ internalReference: 431941
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al acceder al Editor de Sitios, el selector de bloques no funciona inmediatamente.
diff --git a/docs/known-issues/es/bmail-problems-with-filaumbro.md b/docs/known-issues/es/bmail-problems-with-filaumbro.md
index e324c1fd5..76cec00d2 100644
--- a/docs/known-issues/es/bmail-problems-with-filaumbro.md
+++ b/docs/known-issues/es/bmail-problems-with-filaumbro.md
@@ -18,9 +18,7 @@ internalReference: 392798
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md b/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md
index 5f2a8e573..ab94a8677 100644
--- a/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md
+++ b/docs/known-issues/es/boolean-filter-on-form-application-does-not-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 918537
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se selecciona un filtro booleano, se devuelve el siguiente mensaje:
diff --git a/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md b/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
index 1a17f5783..785761a2e 100644
--- a/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
+++ b/docs/known-issues/es/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
@@ -18,9 +18,7 @@ internalReference: 491898
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/brand-filter-export-selecting-fewer-skus-than-expected.md b/docs/known-issues/es/brand-filter-export-selecting-fewer-skus-than-expected.md
index 553adcf18..0043fcc00 100644
--- a/docs/known-issues/es/brand-filter-export-selecting-fewer-skus-than-expected.md
+++ b/docs/known-issues/es/brand-filter-export-selecting-fewer-skus-than-expected.md
@@ -18,9 +18,7 @@ internalReference: 597038
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md b/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
index 14a806969..c2fc5c79a 100644
--- a/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
+++ b/docs/known-issues/es/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
@@ -18,9 +18,7 @@ internalReference: 503496
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La interfaz de usuario de marcas, `.myvtex.com/admin/Site/Marca.aspx`, no permite a los usuarios buscar marcas con algunos caracteres especiales en el nombre, como los apóstrofes `'`. Además, tampoco se pueden buscar letras de alfabetos no latinos, por ejemplo del alfabeto polaco como `Ż`.
diff --git a/docs/known-issues/es/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md b/docs/known-issues/es/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md
index 4a7d5671c..2b6b5bf51 100644
--- a/docs/known-issues/es/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md
+++ b/docs/known-issues/es/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md
@@ -18,9 +18,7 @@ internalReference: 490428
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas transacciones devuelven una falla de comunicación o integración entre Braspag y la adquirida, o sea, un error de timeout. El código de error para este comportamiento es BP901.
diff --git a/docs/known-issues/es/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md b/docs/known-issues/es/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md
index af25fefcf..bace7b557 100644
--- a/docs/known-issues/es/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md
+++ b/docs/known-issues/es/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md
@@ -18,9 +18,7 @@ internalReference: 460999
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se cargan por primera vez las migas de pan, los datos de la lista de categorías son más rápidos que los del árbol de categorías enviados por la consulta de facetas, esto está causando un comportamiento inesperado en el tiempo de carga de la miga de pan, porque la lista de categorías trae también categorías similares de productos similares y no tiene toda la información necesaria para json+ld.
diff --git a/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md b/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
index e91e6dc2e..168471424 100644
--- a/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
+++ b/docs/known-issues/es/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
@@ -18,9 +18,7 @@ internalReference: 683345
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md b/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md
index 2b74b5597..1dbf5c282 100644
--- a/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md
+++ b/docs/known-issues/es/buscacep-not-working-in-create-giftlist-form.md
@@ -18,9 +18,7 @@ internalReference: 342418
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index dd81256fe..1970ce1d3 100644
--- a/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/es/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -18,9 +18,7 @@ internalReference: 431200
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para las cuentas españolas podemos ver el botón "cancelar" en la página de MyCards pero debería tener escrito "cancelar", ya que el sitio web está en español. Los demás botones y el mensaje ya están en español.
diff --git a/docs/known-issues/es/button-to-see-more-pickup-points-not-being-presented-in-the-list.md b/docs/known-issues/es/button-to-see-more-pickup-points-not-being-presented-in-the-list.md
index 37c1fca64..593643f98 100644
--- a/docs/known-issues/es/button-to-see-more-pickup-points-not-being-presented-in-the-list.md
+++ b/docs/known-issues/es/button-to-see-more-pickup-points-not-being-presented-in-the-list.md
@@ -18,9 +18,7 @@ internalReference: 685650
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El botón "ver más" en la lista de puntos de recogida puede no aparecer, ocultando algunas opciones que se presentan en el mapa.
diff --git a/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md b/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
index e1e1e9858..49c5df16f 100644
--- a/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
+++ b/docs/known-issues/es/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
@@ -18,9 +18,7 @@ internalReference: 790828
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el administrador de Fullcleanup, se espera que los botones actúen al primer intento. Sin embargo, para realizar la acción, puede ser necesario hacer clic en el botón varias veces.
diff --git a/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md b/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
index 16f765830..23082227c 100644
--- a/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
+++ b/docs/known-issues/es/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
@@ -18,9 +18,7 @@ internalReference: 301463
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La promoción Buy Together con muchas SKU puede hacer que los productos elegibles no se carguen en la portada debido al tiempo de espera. Las páginas de producto utilizan el control de producto `<vtex.cmc:BuyTogether/>`. Este control es responsable de llevar la información de todos los SKUs elegibles establecidos en la promoción a la página del producto.
diff --git a/docs/known-issues/es/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md b/docs/known-issues/es/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md
index 72773e83d..9f13c43a8 100644
--- a/docs/known-issues/es/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md
+++ b/docs/known-issues/es/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md
@@ -18,9 +18,7 @@ internalReference: 676382
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md b/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
index 3552677d9..374ad076f 100644
--- a/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
+++ b/docs/known-issues/es/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
@@ -18,9 +18,7 @@ internalReference: 945609
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario tiene la primera organización asignada es inválida con el id de centro de coste incorrecto el login falla sin ningún mensaje.
diff --git a/docs/known-issues/es/cabals-regex-update.md b/docs/known-issues/es/cabals-regex-update.md
index 6761cd64c..b8a55f6b2 100644
--- a/docs/known-issues/es/cabals-regex-update.md
+++ b/docs/known-issues/es/cabals-regex-update.md
@@ -18,9 +18,7 @@ internalReference: 374652
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md b/docs/known-issues/es/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md
index 4c0f1ddfc..55fb14b93 100644
--- a/docs/known-issues/es/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md
+++ b/docs/known-issues/es/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md
@@ -18,9 +18,7 @@ internalReference: 841197
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear reglas de merchandising visual o eliminar cualquier regla de merchandising, hay una caché de 5 minutos para estar visualmente disponible en admin.
diff --git a/docs/known-issues/es/calculated-price-table-export-not-bringing-all-skus.md b/docs/known-issues/es/calculated-price-table-export-not-bringing-all-skus.md
index 88e6226e0..1afb5788f 100644
--- a/docs/known-issues/es/calculated-price-table-export-not-bringing-all-skus.md
+++ b/docs/known-issues/es/calculated-price-table-export-not-bringing-all-skus.md
@@ -18,9 +18,7 @@ internalReference: 722005
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/calculation-issue-in-comissionamount.md b/docs/known-issues/es/calculation-issue-in-comissionamount.md
index 97d970ffc..b6696c4cd 100644
--- a/docs/known-issues/es/calculation-issue-in-comissionamount.md
+++ b/docs/known-issues/es/calculation-issue-in-comissionamount.md
@@ -18,9 +18,7 @@ internalReference: 1001005
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Esto ocurre en un escenario específico de división de pagos con múltiples pagos y vendedores (donde ambos son responsables de los gastos de procesamiento de pagos y devoluciones). La suma de `comissionAmount` de los vendedores no es igual a `amount` del mercado (problema de redondeo), esta diferencia puede causar una denegación de liquidación por parte de la entidad adquirente.
diff --git a/docs/known-issues/es/calendar-in-english-for-stores-in-spanish.md b/docs/known-issues/es/calendar-in-english-for-stores-in-spanish.md
index 41f8d06de..56e9a2523 100644
--- a/docs/known-issues/es/calendar-in-english-for-stores-in-spanish.md
+++ b/docs/known-issues/es/calendar-in-english-for-stores-in-spanish.md
@@ -18,9 +18,7 @@ internalReference: 412426
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md b/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
index 4d0af64f8..764c7ecfa 100644
--- a/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
+++ b/docs/known-issues/es/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
@@ -18,9 +18,7 @@ internalReference: 1066571
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utilizan componentes de Store Framework para añadir artículos a un carrito mientras se ha iniciado sesión como operador de un centro de llamadas y no se suplanta la identidad de ningún cliente, el correo electrónico del operador se rellena en el archivo adjunto clientProfileData del orderForm.
diff --git a/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md b/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
index e38cfd189..750750f20 100644
--- a/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
+++ b/docs/known-issues/es/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
@@ -18,9 +18,7 @@ internalReference: 740499
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el proveedor envía una devolución de llamada justo después de la autorización, puede desencadenar un nuevo intento de autorización. Por lo tanto, en algunos casos cuando la transacción tiene más de 1 pago y uno de ellos es una tarjeta regalo, un nuevo reintento de autorización puede cancelar la transacción cuando no tiene fondos.
diff --git a/docs/known-issues/es/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md b/docs/known-issues/es/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md
index d16547e7e..d5c26d9c7 100644
--- a/docs/known-issues/es/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md
+++ b/docs/known-issues/es/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md
@@ -18,9 +18,7 @@ internalReference: 775235
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md b/docs/known-issues/es/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md
index e17e30c9c..ac21d7458 100644
--- a/docs/known-issues/es/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md
+++ b/docs/known-issues/es/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md
@@ -18,19 +18,13 @@ internalReference: 294001
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/campaign-audience-doesnt-save-coupon-information.md b/docs/known-issues/es/campaign-audience-doesnt-save-coupon-information.md
index da94947e5..19b6d35e5 100644
--- a/docs/known-issues/es/campaign-audience-doesnt-save-coupon-information.md
+++ b/docs/known-issues/es/campaign-audience-doesnt-save-coupon-information.md
@@ -18,9 +18,7 @@ internalReference: 521601
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Campaign Audience no guarda la información de los cupones
diff --git a/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
index d8911a9a4..0baa3868e 100644
--- a/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
+++ b/docs/known-issues/es/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -18,9 +18,7 @@ internalReference: 881131
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md b/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md
index 1391abf98..3dafc5dbb 100644
--- a/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md
+++ b/docs/known-issues/es/campovalorformaspx-save-button-requires-two-clicks.md
@@ -18,9 +18,7 @@ internalReference: 525616
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md b/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md
index 1275fae6f..3326e0664 100644
--- a/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md
+++ b/docs/known-issues/es/canonical-tags-are-not-applied-after-3rd-category-level.md
@@ -18,9 +18,7 @@ internalReference: 932349
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las etiquetas canónicas no se aplican después del 3er nivel de categoría cuando se tiene un árbol de categorías con más de 3 niveles (departamento, categoría y subcategoría), los otros niveles por encima no se muestran en canónica
diff --git a/docs/known-issues/es/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md b/docs/known-issues/es/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md
index 23ab5672c..c989a75a8 100644
--- a/docs/known-issues/es/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md
+++ b/docs/known-issues/es/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md
@@ -18,9 +18,7 @@ internalReference: 446938
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No es posible finalizar las compras cuando el marketplace está aplicando promociones a los artículos de los vendedores que están bajo comportamiento multinivel. El cliente verá un mensaje de error genérico.
diff --git a/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md b/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md
index f7813fd58..fcdc0d5af 100644
--- a/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md
+++ b/docs/known-issues/es/cant-edit-the-name-of-the-styles-template.md
@@ -18,9 +18,7 @@ internalReference: 882147
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Una vez creado un nuevo estilo en el módulo Estilos no es posible editar su nombre.
diff --git a/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md b/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md
index 99a1def01..24c1b32b8 100644
--- a/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md
+++ b/docs/known-issues/es/card-brands-incorrectly-processed-as-visa.md
@@ -18,9 +18,7 @@ internalReference: 1024823
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas tarjetas de crédito pueden ser procesadas como Visa cuando en realidad son de otra marca.
diff --git a/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md b/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md
index 0acf26d15..67a9485e3 100644
--- a/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md
+++ b/docs/known-issues/es/card-facebook-doesnt-save-some-settings.md
@@ -18,9 +18,7 @@ internalReference: 548763
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El facebook de la tarjeta no guarda algunos ajustes.
diff --git a/docs/known-issues/es/cardholderdocument-is-not-sent-to-antifraud.md b/docs/known-issues/es/cardholderdocument-is-not-sent-to-antifraud.md
index cdcda585c..97ac527a9 100644
--- a/docs/known-issues/es/cardholderdocument-is-not-sent-to-antifraud.md
+++ b/docs/known-issues/es/cardholderdocument-is-not-sent-to-antifraud.md
@@ -18,9 +18,7 @@ internalReference: 829864
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
index d2131a97a..b73c0a82b 100644
--- a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
+++ b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
@@ -18,9 +18,7 @@ internalReference: 1020278
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
index b5d3047ad..c07687487 100644
--- a/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
+++ b/docs/known-issues/es/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
@@ -18,9 +18,7 @@ internalReference: 802464
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
index 55c65bde1..a8837c4c5 100644
--- a/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
+++ b/docs/known-issues/es/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -18,9 +18,7 @@ internalReference: 947563
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md b/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
index 70efe4d2f..8a14cddfd 100644
--- a/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
+++ b/docs/known-issues/es/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
@@ -18,9 +18,7 @@ internalReference: 1002115
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay una cantidad dividida en el `priceDefinition` debido al redondeo para el multiplicador de unidades, la pasarela no puede recibir ningún valor para `deliveryType` en el objeto del carrito. Por lo tanto, esto podría causar que el proveedor de pago denegar el pago si utilizan este campo..
diff --git a/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md b/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md
index e6e5c0d94..c669b59ef 100644
--- a/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md
+++ b/docs/known-issues/es/cart-itens-are-kept-in-orders-with-total-value-zero.md
@@ -18,9 +18,7 @@ internalReference: 1054999
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md b/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
index fbbe47039..f7efe7862 100644
--- a/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
+++ b/docs/known-issues/es/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
@@ -18,9 +18,7 @@ internalReference: 303673
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Mientras se carga la pantalla del carrito, eventualmente, aparece un mensaje de "carrito vacío" delante de los artículos. Este escenario puede ocurrir rápidamente, con algo menos de milisegundos, y volverse imperceptible, o posiblemente más lentamente, durando hasta un segundo o incluso más y generando consultas por parte de las tiendas.
diff --git a/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md b/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
index 4c9b554b8..f4d0f07ff 100644
--- a/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
+++ b/docs/known-issues/es/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
@@ -18,9 +18,7 @@ internalReference: 1068197
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si un comprador tiene varias direcciones de distintos países en su perfil y la tienda no realiza entregas en ninguna de esas direcciones, al seleccionar la recogida en una dirección válida y pasar al paso de pago, la interfaz de usuario de la caja redirige al comprador de nuevo al paso de envío.
diff --git a/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md b/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
index c09cfddb4..54f464d67 100644
--- a/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
+++ b/docs/known-issues/es/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
@@ -18,9 +18,7 @@ internalReference: 473424
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md b/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md
index b35f8159e..b0707d0d0 100644
--- a/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md
+++ b/docs/known-issues/es/cashback-promotions-do-not-consider-items-removed-from-orders.md
@@ -18,9 +18,7 @@ internalReference: 1019864
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/catalog-access-profile-gives-access-to-the-gift-card-module.md b/docs/known-issues/es/catalog-access-profile-gives-access-to-the-gift-card-module.md
index 8dae93a7e..febff3bd1 100644
--- a/docs/known-issues/es/catalog-access-profile-gives-access-to-the-gift-card-module.md
+++ b/docs/known-issues/es/catalog-access-profile-gives-access-to-the-gift-card-module.md
@@ -18,9 +18,7 @@ internalReference: 362165
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El acceso al módulo de catálogos también da acceso al módulo de tarjetas de regalo a través de la interfaz de usuario.
diff --git a/docs/known-issues/es/catalog-api-create-sku-file-only-work-with-an-url.md b/docs/known-issues/es/catalog-api-create-sku-file-only-work-with-an-url.md
index ea5aaacda..0ab52e848 100644
--- a/docs/known-issues/es/catalog-api-create-sku-file-only-work-with-an-url.md
+++ b/docs/known-issues/es/catalog-api-create-sku-file-only-work-with-an-url.md
@@ -18,9 +18,7 @@ internalReference: 503153
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API del catálogo Crear archivo SKU sólo funciona con la opción 1 ( enviar una imagen a través de la URL)
diff --git a/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md b/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
index eaaba4b9e..79a7b16c7 100644
--- a/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
+++ b/docs/known-issues/es/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
@@ -18,9 +18,7 @@ internalReference: 977033
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza la colección de la API de catálogo, si se envía un campo JSON de cadena que termina con espacios (por ejemplo productName: "myProductName ") las API de catálogo responderán con una respuesta 400 incorrecta y un cuerpo de respuesta vacío, dejando al usuario sin saber qué se envió incorrectamente.
diff --git a/docs/known-issues/es/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md b/docs/known-issues/es/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md
index ea0b856ce..6a7e82bbf 100644
--- a/docs/known-issues/es/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md
+++ b/docs/known-issues/es/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md
@@ -18,9 +18,7 @@ internalReference: 269109
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un montón de rutas que soportan algún tipo de valor, pero si el cliente utiliza otro tipo de valor (por ejemplo, insertar null en lugar de boolean) puede romper la interfaz de producto / SKU / categoría / marca. Negando al cliente actualizar la información a través de admin.
diff --git a/docs/known-issues/es/catalog-database-registers-skus-with-duplicate-specifications.md b/docs/known-issues/es/catalog-database-registers-skus-with-duplicate-specifications.md
index 1a5091108..e130b6a62 100644
--- a/docs/known-issues/es/catalog-database-registers-skus-with-duplicate-specifications.md
+++ b/docs/known-issues/es/catalog-database-registers-skus-with-duplicate-specifications.md
@@ -18,9 +18,7 @@ internalReference: 536133
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunas situaciones aleatorias, la base de datos del catálogo permite duplicar los valores de una especificación en la misma SKU.
diff --git a/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md b/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md
index 8e21ae2ad..2c87b1a12 100644
--- a/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md
+++ b/docs/known-issues/es/catalog-export-cannot-handle-t-and-s-characters.md
@@ -18,9 +18,7 @@ internalReference: 950933
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la importación/exportación de catálogos corta nuestros caracteres especiales ț y ș al exportar datos.
diff --git a/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md b/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
index 3657f0822..c30ca17fd 100644
--- a/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
+++ b/docs/known-issues/es/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
@@ -18,9 +18,7 @@ internalReference: 722001
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, los canales de venta que se comprueban en la interfaz de usuario del producto tienen una lógica de "si no se marca ninguno, todos están disponibles".
diff --git a/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md b/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md
index e015f83fe..b40d2b0ae 100644
--- a/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md
+++ b/docs/known-issues/es/catalog-export-for-attachment-cuts-50-characters.md
@@ -18,9 +18,7 @@ internalReference: 953161
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al importar datos de adjuntos en el módulo catálogo, si dicho adjunto tiene más de 50 caracteres, se corta la cadena, lo que provoca que no se actualicen estos datos.
diff --git a/docs/known-issues/es/catalog-filter-for-seller-1-brings-empty-results.md b/docs/known-issues/es/catalog-filter-for-seller-1-brings-empty-results.md
index 0cd1277ee..d2cd3a55d 100644
--- a/docs/known-issues/es/catalog-filter-for-seller-1-brings-empty-results.md
+++ b/docs/known-issues/es/catalog-filter-for-seller-1-brings-empty-results.md
@@ -18,9 +18,7 @@ internalReference: 801538
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, al filtrar exclusivamente por el vendedor principal en los menús del Catálogo, no se muestra ningún resultado. Esto sucede porque este filtro está buscando incorrectamente un vendedor específico cuando, en cambio, el vendedor = 1 (el vendedor principal de la cuenta) es el propio mercado.
diff --git a/docs/known-issues/es/catalog-filters-timeout.md b/docs/known-issues/es/catalog-filters-timeout.md
index 58de30041..54b52ab03 100644
--- a/docs/known-issues/es/catalog-filters-timeout.md
+++ b/docs/known-issues/es/catalog-filters-timeout.md
@@ -18,9 +18,7 @@ internalReference: 922350
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para las tiendas con una gran cantidad de skus (1 millón o más), a menudo, al filtrar utilizando los filtros de la interfaz de usuario del catálogo, ya sea para el menú principal o para la sección de informes, si la consulta de filtro devuelve un resultado muy grande, la interfaz de usuario se agota (504 tiempo de espera de la puerta de enlace).
diff --git a/docs/known-issues/es/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md b/docs/known-issues/es/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md
index c1d4969cc..206c3e18e 100644
--- a/docs/known-issues/es/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md
+++ b/docs/known-issues/es/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md
@@ -18,9 +18,7 @@ internalReference: 449763
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al ejecutar una limpieza completa (https://{AccountName}.myvtex.com/admin/Site/fullcleanup.aspx) en el catálogo, la emisora no envía la notificación de actualización al indexador de búsqueda inteligente, y los datos de los productos pueden quedar obsoletos, lo que provoca discrepancias entre el contenido de PDP y PLP.
diff --git a/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md b/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md
index c00288702..de4f991d0 100644
--- a/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md
+++ b/docs/known-issues/es/catalog-graphql-categoryinputtranslation-not-working.md
@@ -18,9 +18,7 @@ internalReference: 1024172
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el método CategoryInputTranslation, para el catálogo graphQL no está generando una actualización en los datos traducidos para las cuentas.
diff --git a/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md b/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md
index cda73dc07..b0bb200f2 100644
--- a/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md
+++ b/docs/known-issues/es/catalog-indexer-generating-invalid-translation-documents.md
@@ -18,9 +18,7 @@ internalReference: 991494
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al indexar un producto con información traducida se solicitan los mensajes de la aplicación. Se supone que estas solicitudes son menos de 3s y cuando toman más de que la indexación falla y genera un documento de traducción no válida.
diff --git a/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
index fa834d4ca..e0a16b27c 100644
--- a/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/es/catalog-indexing-report-total-section-calculation-error.md
@@ -18,9 +18,7 @@ internalReference: 499450
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, en el informe de indexación del catálogo (RelatorioIndexacao.aspx), la sección "Total indexado" está considerando todos los productos del catálogo al llegar al 100% de la métrica, no restando los productos no indexados si es necesario.
diff --git a/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md b/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md
index ffaf689d4..58dccb2f5 100644
--- a/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md
+++ b/docs/known-issues/es/catalog-integration-xml-fiscal-code-field-not-rendering.md
@@ -18,9 +18,7 @@ internalReference: 1031109
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/catalog-mapping-ui-taking-too-much-time-to-load.md b/docs/known-issues/es/catalog-mapping-ui-taking-too-much-time-to-load.md
index b3d1d6e18..0004a694d 100644
--- a/docs/known-issues/es/catalog-mapping-ui-taking-too-much-time-to-load.md
+++ b/docs/known-issues/es/catalog-mapping-ui-taking-too-much-time-to-load.md
@@ -18,9 +18,7 @@ internalReference: 823218
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el marketplace tiene muchos vendedores y utiliza las hojas de cálculo de mapeo para la mayoría de ellos, la UI de mapeo de catálogos puede ser demasiado pesada y cada vez que el vendedor intenta acceder a ella, tarda mucho en cargarse.
diff --git a/docs/known-issues/es/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md b/docs/known-issues/es/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md
index 63b4d9780..408268ffc 100644
--- a/docs/known-issues/es/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md
+++ b/docs/known-issues/es/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md
@@ -18,9 +18,7 @@ internalReference: 711637
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md b/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md
index 703cd582b..7c8a0e7e4 100644
--- a/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md
+++ b/docs/known-issues/es/catalog-search-api-limited-to-2500-results.md
@@ -18,9 +18,7 @@ internalReference: 891184
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar la API de Búsqueda por Catálogo el máximo de resultados obtenidos es de 2500, aunque haya más productos.
diff --git a/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md b/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
index 0e12896de..653b2390e 100644
--- a/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
+++ b/docs/known-issues/es/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
@@ -18,9 +18,7 @@ internalReference: 583623
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las Facetas de Búsqueda del Catálogo API / Filtros del Resultado de la Búsqueda del Portal no devuelven la información de los productos no disponibles y configurados para ser mostrados sin stock. El producto aparecerá en el Resultado de la Búsqueda, pero sus filtros no aparecerán.
diff --git a/docs/known-issues/es/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md b/docs/known-issues/es/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md
index b9e9ee9cb..fa7f40591 100644
--- a/docs/known-issues/es/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md
+++ b/docs/known-issues/es/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md
@@ -18,9 +18,7 @@ internalReference: 465445
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Exportación de Especificación SKU del Catálogo, no siempre exportará todos los datos si se selecciona el departamento y no la subcategoría más interna.
diff --git a/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md b/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md
index a019c0bc0..2150f1515 100644
--- a/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md
+++ b/docs/known-issues/es/catalog-translations-not-reflecting-on-the-frontend.md
@@ -18,9 +18,7 @@ internalReference: 861892
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el comerciante realiza una acción en la aplicación Mensajes para que se traduzcan algunos datos del producto en el frontend, esta acción no se está reflejando realmente.
diff --git a/docs/known-issues/es/catalogv2-user-roles-not-applying.md b/docs/known-issues/es/catalogv2-user-roles-not-applying.md
index 38308357f..e81241c98 100644
--- a/docs/known-issues/es/catalogv2-user-roles-not-applying.md
+++ b/docs/known-issues/es/catalogv2-user-roles-not-applying.md
@@ -18,9 +18,7 @@ internalReference: 489297
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Actualmente, la interfaz de usuario de la aplicación CatalogV2 no aplica correctamente los permisos de control de acceso cuando un usuario utiliza la interfaz para crear, leer o actualizar productos.
 
diff --git a/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md b/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
index 0b5ab1428..61ae70492 100644
--- a/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
+++ b/docs/known-issues/es/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
@@ -18,9 +18,7 @@ internalReference: 1026699
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un vendedor envía al marketplace una sku con una categoría o marca que aún no está mapeada en la hoja de cálculo, ésta se actualiza con este nuevo valor en la 3ª columna para poder ser mapeada.
diff --git a/docs/known-issues/es/categoriesaspx-specification-timeout.md b/docs/known-issues/es/categoriesaspx-specification-timeout.md
index ae233e3aa..58e0e0fe2 100644
--- a/docs/known-issues/es/categoriesaspx-specification-timeout.md
+++ b/docs/known-issues/es/categoriesaspx-specification-timeout.md
@@ -18,9 +18,7 @@ internalReference: 433664
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No hay límite en el registro de los campos de especificación, lo que puede generar tiempos de espera en el administrador del catálogo.
diff --git a/docs/known-issues/es/category-commissioning-on-the-seller-config-generates-time-out.md b/docs/known-issues/es/category-commissioning-on-the-seller-config-generates-time-out.md
index 883478807..388f9aff2 100644
--- a/docs/known-issues/es/category-commissioning-on-the-seller-config-generates-time-out.md
+++ b/docs/known-issues/es/category-commissioning-on-the-seller-config-generates-time-out.md
@@ -18,9 +18,7 @@ internalReference: 310527
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si una cuenta tiene muchas categorías, en la pantalla de configuración del vendedor puede que no se cargue la puesta en marcha de la categoría debido a un tiempo de espera.
diff --git a/docs/known-issues/es/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/es/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
index 50ecf88a2..90dfea14a 100644
--- a/docs/known-issues/es/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
+++ b/docs/known-issues/es/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -18,9 +18,7 @@ internalReference: 654951
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza el catálogo graphql y se traduce la URL utilizando el linkId el reescribidor debería almacenar el linkId, pero, no está sucediendo: https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization#category
diff --git a/docs/known-issues/es/category-specs-do-not-open-in-admin-on-first-attempt.md b/docs/known-issues/es/category-specs-do-not-open-in-admin-on-first-attempt.md
index c4fb7eb36..b6475d299 100644
--- a/docs/known-issues/es/category-specs-do-not-open-in-admin-on-first-attempt.md
+++ b/docs/known-issues/es/category-specs-do-not-open-in-admin-on-first-attempt.md
@@ -18,9 +18,7 @@ internalReference: 664419
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, al intentar abrir una especificación de producto o sku en el administrador de categorías, la página no se carga correctamente y se actualiza de nuevo a la página inicial del árbol de categorías.
diff --git a/docs/known-issues/es/category-substitute-words-not-being-indexed.md b/docs/known-issues/es/category-substitute-words-not-being-indexed.md
index d6c90859e..7343fb893 100644
--- a/docs/known-issues/es/category-substitute-words-not-being-indexed.md
+++ b/docs/known-issues/es/category-substitute-words-not-being-indexed.md
@@ -18,9 +18,7 @@ internalReference: 374204
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/category-translation-fields-being-overwritten-on-catalog-graphql.md b/docs/known-issues/es/category-translation-fields-being-overwritten-on-catalog-graphql.md
index 631fe1ac7..187ce8aec 100644
--- a/docs/known-issues/es/category-translation-fields-being-overwritten-on-catalog-graphql.md
+++ b/docs/known-issues/es/category-translation-fields-being-overwritten-on-catalog-graphql.md
@@ -18,9 +18,7 @@ internalReference: 654896
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al traducir contenido utilizando la aplicación catalog-graphql o la traducción de catálogos, los campos como nombre, título o descripción se sobrescriben. Este comportamiento sólo ocurre si uno de estos campos (nombre, título, descripción) es igual en el registro del catálogo.
diff --git a/docs/known-issues/es/categorycommissionpercentage-on-seller-api-allowing-any-value.md b/docs/known-issues/es/categorycommissionpercentage-on-seller-api-allowing-any-value.md
index f2532f3a6..775492171 100644
--- a/docs/known-issues/es/categorycommissionpercentage-on-seller-api-allowing-any-value.md
+++ b/docs/known-issues/es/categorycommissionpercentage-on-seller-api-allowing-any-value.md
@@ -18,9 +18,7 @@ internalReference: 382680
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la API de vendedor PUT, la propiedad CategoryCommissionPercentage acepta cualquier tipo de entrada, por ejemplo, entradas de texto. Esto puede incluso romper el proceso de indexación de los productos que tienen SKUs en los que se incluye este vendedor.
diff --git a/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md b/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md
index c769a5392..19258af8c 100644
--- a/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md
+++ b/docs/known-issues/es/centauro-orders-with-pedido-sem-o-campo-packages-error.md
@@ -18,9 +18,7 @@ internalReference: 604422
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md b/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
index 2fc7ed9fc..86ab01e32 100644
--- a/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
+++ b/docs/known-issues/es/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
@@ -18,9 +18,7 @@ internalReference: 844893
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la cuenta ha configurado la posibilidad de que el comprador cambie el pedido por sí mismo, el enlace de cambio de pedido aparecerá en la plantilla de pago/pedido realizado.
diff --git a/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md b/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
index 4c8cb1a55..5a4c5ff41 100644
--- a/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
+++ b/docs/known-issues/es/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
@@ -18,9 +18,7 @@ internalReference: 472882
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En los pedidos con la promoción "Más por menos", es posible modificar el pedido y eliminar uno o varios artículos en la interfaz de usuario, pero el descuento sigue aplicándose.
diff --git a/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md b/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md
index ecbacd69b..83a99508c 100644
--- a/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md
+++ b/docs/known-issues/es/change-order-using-api-without-email-orderchanged.md
@@ -18,9 +18,7 @@ internalReference: 380509
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el administrador de una cuenta cambia el pedido aplicando descuentos sobre el valor y no sobre los artículos utilizando la API, el correo electrónico de la orden de cambio no se envía al cliente final.
diff --git a/docs/known-issues/es/change-the-number-of-characters-in-the-braspag-slip.md b/docs/known-issues/es/change-the-number-of-characters-in-the-braspag-slip.md
index 4189862eb..3940d79c4 100644
--- a/docs/known-issues/es/change-the-number-of-characters-in-the-braspag-slip.md
+++ b/docs/known-issues/es/change-the-number-of-characters-in-the-braspag-slip.md
@@ -18,9 +18,7 @@ internalReference: 771045
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se genera un pedido vía boleto con Braspag y en los datos de dirección, si tiene más de 40 caracteres, se están cortando los datos de dirección. Deberá realizar una mejora cambiando el límite de caracteres del campo de dirección de 40 caracteres a 60.
diff --git a/docs/known-issues/es/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md b/docs/known-issues/es/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md
index ce06eea9a..691d069d7 100644
--- a/docs/known-issues/es/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md
+++ b/docs/known-issues/es/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md
@@ -18,9 +18,7 @@ internalReference: 786145
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando creas una nueva página en Pages y luego cambias su ruta a algo diferente, el routeId no cambia. Así que cuando cree otra página con la misma ruta que la primera, el routeId seguirá siendo el mismo. Y entonces el editor del sitio tendrá problemas para guardar el contenido de estas dos páginas debido al conflicto en sus rutas.
diff --git a/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md b/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
index 36f148a2d..1e913d934 100644
--- a/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
+++ b/docs/known-issues/es/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
@@ -18,9 +18,7 @@ internalReference: 971948
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los cambios que se realizan utilizando la página de estilos de la interfaz de usuario de administración no se están guardando correctamente y no siempre se aplicarán a la página web.
diff --git a/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md b/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md
index 541c9adce..c47443616 100644
--- a/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md
+++ b/docs/known-issues/es/changing-accessories-is-not-triggering-indexation.md
@@ -18,9 +18,7 @@ internalReference: 1037800
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el comerciante realiza cambios o añade nuevos accesorios a la sku, el indexador no se activa automáticamente.
diff --git a/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md b/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
index 602995561..fb981e01a 100644
--- a/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
+++ b/docs/known-issues/es/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
@@ -18,9 +18,7 @@ internalReference: 460329
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cambiar el orden de una especificación de SKU en el Admin podría hacer que la página no funcione correctamente.
diff --git a/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md b/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md
index 9c674f0cb..12f9054a2 100644
--- a/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md
+++ b/docs/known-issues/es/checkbox-requires-authentication-doesnt-work-on-pages-module.md
@@ -18,9 +18,7 @@ internalReference: 577306
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función de autenticación, que se gestiona mediante la selección de una casilla de verificación en el módulo Páginas, no funciona correctamente. El usuario no es redirigido a una página de solicitud de autenticación cuando la casilla está marcada.
diff --git a/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md b/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
index 0c9634abc..6404cb813 100644
--- a/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
+++ b/docs/known-issues/es/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
@@ -18,9 +18,7 @@ internalReference: 699317
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un carro con SLA sólo para la entrega y el usuario introduce un código postal correcto, el checkout permite al usuario continuar, sin embargo, si el usuario vuelve a la página del carro de nuevo y cambia a la opción de recogida y luego hace clic para continuar a la parte de pago, luego vuelve al carro de nuevo, cambia de nuevo a la opción de entrega y continúa de nuevo, esta vez, el usuario va al formulario de pago. Además, hay un mensaje en la parte de la dirección de envío que dice que el componente está "esperando a que se rellenen los datos".
diff --git a/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md b/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md
index 55f448537..dd75e66b5 100644
--- a/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md
+++ b/docs/known-issues/es/checkout-allows-to-add-2-different-addresses-for-delivery.md
@@ -18,9 +18,7 @@ internalReference: 931225
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Checkout permite añadir dos direcciones diferentes para la entrega en el orderForm, por ejemplo, una "comercial" y una "residencial" (definidas por el campo 'addressType'), cuando una de ellas es desechable.
diff --git a/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md b/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
index 77855c236..ec7782e40 100644
--- a/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
+++ b/docs/known-issues/es/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
@@ -18,9 +18,7 @@ internalReference: 343056
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md b/docs/known-issues/es/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md
index 741ab94bc..03381857c 100644
--- a/docs/known-issues/es/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md
+++ b/docs/known-issues/es/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md
@@ -18,9 +18,7 @@ internalReference: 802156
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando dos o más vendedores pueden completar un carro con más de un artículo, es posible que la API de pago no agrupe los paquetes seleccionando vendedores diferentes para cada producto. Esto aumenta el valor del envío para el comprador.
diff --git a/docs/known-issues/es/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md b/docs/known-issues/es/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md
index c01253dbf..3a597e2a2 100644
--- a/docs/known-issues/es/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md
+++ b/docs/known-issues/es/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md
@@ -18,9 +18,7 @@ internalReference: 363885
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza un artículo en un carrito con un beneficio de promoción de regalo, el artículo que contiene no se puede eliminar si no está disponible después de la selección del punto de recogida.
diff --git a/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md b/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
index dd096adc2..e3e5f7913 100644
--- a/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
+++ b/docs/known-issues/es/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 529043
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el carrito está compuesto por dos artículos, y el tipo de envío es programado, al añadir el primer artículo al carrito con envío gratuito, y se trata del mismo SLA, la caja acaba cobrando el valor de este envío, ya que no sabe cómo tratar el cálculo de la distribución de los valores de los portes entre los artículos, ya que se trata de un envío programado y el precio de la ventana es para un paquete en su conjunto.
diff --git a/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md b/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
index dc457b74f..36f6d3d1d 100644
--- a/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
+++ b/docs/known-issues/es/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
@@ -18,9 +18,7 @@ internalReference: 280144
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El checkout (backend) tiene un comportamiento de pre-seleccionar el mejor método de entrega para el usuario tan pronto como un código postal es informado.
diff --git a/docs/known-issues/es/checkout-does-not-show-option-to-change-zip-code.md b/docs/known-issues/es/checkout-does-not-show-option-to-change-zip-code.md
index 59decbad5..1841f3f3b 100644
--- a/docs/known-issues/es/checkout-does-not-show-option-to-change-zip-code.md
+++ b/docs/known-issues/es/checkout-does-not-show-option-to-change-zip-code.md
@@ -18,9 +18,7 @@ internalReference: 321598
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para los artículos que están restringidos a la recogida en la tienda a determinadas direcciones, la opción de cambiar el código postal está desapareciendo mientras el usuario está en la pestaña de entrega, en el carrito .
diff --git a/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md b/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md
index e40ad9903..169e17cc6 100644
--- a/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md
+++ b/docs/known-issues/es/checkout-does-not-support-encoding-assembly-options-names.md
@@ -18,9 +18,7 @@ internalReference: 378842
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los nombres de las opciones de ensamblaje se utilizan en la ruta API. Por ello, es necesario soportar la codificación de estos nombres para no crear problemas en la URL con caracteres especiales, como "/". Al añadir una opción de montaje con "/" en el carrito, simplemente no se añade y tampoco se notifica al usuario.
diff --git a/docs/known-issues/es/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md b/docs/known-issues/es/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md
index 23ba82bf1..272a38555 100644
--- a/docs/known-issues/es/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md
+++ b/docs/known-issues/es/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md
@@ -18,9 +18,7 @@ internalReference: 350780
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La implementación de Google Analytics de Checkout dispara el evento pageview una vez por rastreador, incluso si el rastreador no está destinado a rastrear la información de pageview.
diff --git a/docs/known-issues/es/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md b/docs/known-issues/es/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md
index efbd509ef..d6d42fbdb 100644
--- a/docs/known-issues/es/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md
+++ b/docs/known-issues/es/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md
@@ -18,9 +18,7 @@ internalReference: 287444
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md b/docs/known-issues/es/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md
index eef64769f..8b63c31c3 100644
--- a/docs/known-issues/es/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md
+++ b/docs/known-issues/es/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md
@@ -18,9 +18,7 @@ internalReference: 442267
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Durante el proceso de compra, es necesario iniciar sesión para ver/cambiar la información personal y, en algunos casos, incluso finalizar la compra. El proceso de inicio de sesión está desconectado del orderForm, por lo que puede iniciar sesión como cualquier correo electrónico y ser identificado con algún otro correo electrónico en el flujo de compra.
diff --git a/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md b/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md
index b610f3ac3..1f968cfc0 100644
--- a/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md
+++ b/docs/known-issues/es/checkout-incorrectly-sending-item-details-to-transaction.md
@@ -18,9 +18,7 @@ internalReference: 535859
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md b/docs/known-issues/es/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md
index a378b2978..cc68157b5 100644
--- a/docs/known-issues/es/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md
+++ b/docs/known-issues/es/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md
@@ -18,9 +18,7 @@ internalReference: 258447
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando en el checkout con un email informado y datos enmascarados, será necesario iniciar sesión si el comprador quiere cambiar alguna información. En el cuadro de inicio de sesión que se abrirá, el correo electrónico ya se rellenará con el contexto del carrito, pero la interfaz permite modificar el correo electrónico "sugerido".
diff --git a/docs/known-issues/es/checkout-orderplaced-boleto-bank-invoice-moip.md b/docs/known-issues/es/checkout-orderplaced-boleto-bank-invoice-moip.md
index 952b0b003..cfdcdafde 100644
--- a/docs/known-issues/es/checkout-orderplaced-boleto-bank-invoice-moip.md
+++ b/docs/known-issues/es/checkout-orderplaced-boleto-bank-invoice-moip.md
@@ -18,9 +18,7 @@ internalReference: 376951
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El orderPlaced tiene una función automática que inyecta el PDF del "Boleto - Factura Bancaria" en un iframe dentro de la página de pedido terminado.
diff --git a/docs/known-issues/es/checkout-overwrites-receiver-name-with-customer-name.md b/docs/known-issues/es/checkout-overwrites-receiver-name-with-customer-name.md
index 1656107fb..a28e6acb4 100644
--- a/docs/known-issues/es/checkout-overwrites-receiver-name-with-customer-name.md
+++ b/docs/known-issues/es/checkout-overwrites-receiver-name-with-customer-name.md
@@ -18,9 +18,7 @@ internalReference: 324792
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El nombre del receptor se reescribe con el nombre del cliente después de recargar la página de pago.
diff --git a/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md b/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
index ff2c52060..2aee9ae6f 100644
--- a/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
+++ b/docs/known-issues/es/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
@@ -18,19 +18,13 @@ internalReference: 330802
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md b/docs/known-issues/es/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md
index 80513f271..6cb165a43 100644
--- a/docs/known-issues/es/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md
+++ b/docs/known-issues/es/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md
@@ -18,19 +18,13 @@ internalReference: 704699
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md b/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
index 75ac70a0c..b36b89cfe 100644
--- a/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
+++ b/docs/known-issues/es/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
@@ -18,9 +18,7 @@ internalReference: 759842
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay 2 vendedores en el método "SellerElection", uno de ellos es seleccionado como el que tiene el precio más barato para la entrega, y el otro el precio más barato para la recogida en el punto, la fusión de la información del carrito no actualiza los impuestos al seleccionar la recogida en el punto, causando un error al finalizar la compra.
diff --git a/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
index 9ddb666f2..271167362 100644
--- a/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
+++ b/docs/known-issues/es/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -18,9 +18,7 @@ internalReference: 1012724
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los impuestos del porcentaje de envío no se devuelven en el campo `logisticsInfo.slas.tax` al realizar una simulación de pago aunque la información de los impuestos individuales esté disponible en el campo `items.priceTags`.
diff --git a/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md b/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
index 3c5a1953d..f637d358c 100644
--- a/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
+++ b/docs/known-issues/es/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
@@ -18,9 +18,7 @@ internalReference: 330775
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos un error en el servicio de Logística cuando intentamos simular una compra con miles de unidades del mismo SKU. Ese error se produce porque la solicitud para dividir el paquete tarda demasiado.
diff --git a/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md b/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
index 454378e9f..bbba75d03 100644
--- a/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
+++ b/docs/known-issues/es/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
@@ -18,9 +18,7 @@ internalReference: 937615
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un comprador tiene un perfil completo y la tienda está configurada para utilizar una dirección de factura para la recogida, la interfaz de usuario pasará a Pago con una dirección de factura incompleta.
diff --git a/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
index 51f9d4794..78b685b41 100644
--- a/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
+++ b/docs/known-issues/es/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -18,9 +18,7 @@ internalReference: 329846
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La configuración de Checkout UI permite desactivar el lean shipping (optimizaciones del modo de entrega), pero esto sólo es posible si todos los artículos del carrito tienen en común los mismos métodos de entrega. De lo contrario, el lean shipping debe aparecer forzosamente en el carrito incluso con la opción desactivada.
diff --git a/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md b/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
index b515fdcd5..59f0af922 100644
--- a/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
+++ b/docs/known-issues/es/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
@@ -18,19 +18,13 @@ internalReference: 485016
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md b/docs/known-issues/es/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md
index 3af310a19..779dabc53 100644
--- a/docs/known-issues/es/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md
+++ b/docs/known-issues/es/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md
@@ -18,9 +18,7 @@ internalReference: 822670
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si un comprador tiene un perfil completo en el que el nombre y los apellidos difieren del destinatario del envío, cuando su perfil se rellena automáticamente al realizar el pago, la interfaz de usuario sobrescribe el Destinatario del envío con el valor del nombre y los apellidos combinados.
diff --git a/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md b/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
index 5f5a9e6bf..845961ce6 100644
--- a/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
+++ b/docs/known-issues/es/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
@@ -18,9 +18,7 @@ internalReference: 937692
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Checkout UI envía un guión para el código postal a orderForm, causando problemas al calcular los ANS cuando un país tiene 7 dígitos + el guión. Esto sucede porque el módulo de Logística considera el guión como un dígito y dependiendo de cómo se registraron las tarifas de envío en la política de envío.
diff --git a/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md b/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
index 1b110db6e..c7a83b29c 100644
--- a/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
+++ b/docs/known-issues/es/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
@@ -18,9 +18,7 @@ internalReference: 897109
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La interfaz de usuario de la caja muestra la entrega gratuita cuando el usuario cambia el método de entrega de envío normal a entrega programada. El problema solo se produce en el cuadro de entrega y cuando la cuenta tiene configurada la función LeanShipping. aunque la IU muestra el envío gratuito, los valores totales de la compra se muestran y cobran correctamente.
diff --git a/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md b/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
index a85e9fd69..6e62032e1 100644
--- a/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
+++ b/docs/known-issues/es/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
@@ -18,9 +18,7 @@ internalReference: 784693
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La interfaz de usuario del proceso de pago anula la selección del conmutador "Programar todo" en el paso de envío después de actualizar la página, aunque la API siga seleccionada. Este comportamiento no tiene ningún impacto; el pedido tendrá seleccionada la entrega programada.
diff --git a/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md b/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
index c0fd44533..41978f179 100644
--- a/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
+++ b/docs/known-issues/es/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
@@ -18,9 +18,7 @@ internalReference: 836025
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los campos "ciudad" y "estado" no se envían a PayPalPlus cuando el comprador sólo añade una dirección de recogida al carro, lo que hace que no se cargue la forma de pago.
diff --git a/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md b/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
index 7796ef717..a1b6d603b 100644
--- a/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
+++ b/docs/known-issues/es/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
@@ -18,9 +18,7 @@ internalReference: 960905
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos casos, como en páginas de destino y páginas de colección, los filtros adicionales no se borran correctamente después de hacer clic en el botón "Borrar filtro". La URL puede ir a filtros no válidos o erróneos y el listado de productos puede quedar vacío o con productos inesperados.
diff --git a/docs/known-issues/es/clicks-on-the-numericstepper-not-working.md b/docs/known-issues/es/clicks-on-the-numericstepper-not-working.md
index 60e5827da..381e94f0d 100644
--- a/docs/known-issues/es/clicks-on-the-numericstepper-not-working.md
+++ b/docs/known-issues/es/clicks-on-the-numericstepper-not-working.md
@@ -18,9 +18,7 @@ internalReference: 537245
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los clics del Stepper Numérico no están funcionando como se esperaba - todavía se puede editar el cuadro de texto pero los botones no aumentan o disminuyen el número del cuadro de texto. Las llamadas de red parecen enviarse de la misma manera. El cliente reportó este problema al usar Windows 11 con Chrome. Algunas consideraciones:
diff --git a/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md b/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
index 9f057f62c..15d393e2d 100644
--- a/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
+++ b/docs/known-issues/es/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
@@ -18,9 +18,7 @@ internalReference: 863726
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza Global Checkout, y el cambio de utilizar el documento por defecto y un documento auto-identificado y el valor informado para el campo de número de documento no "tomarlo" correctamente.
diff --git a/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md b/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
index 42ed8cc05..71d5efa0f 100644
--- a/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
+++ b/docs/known-issues/es/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
@@ -18,9 +18,7 @@ internalReference: 911203
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se envía la petición Añadir perfil de cliente dos veces y el email tiene un perfil completo, "clientProfileData" se queda vacío, mostrando sólo el email.
diff --git a/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md b/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
index bc9905e15..8cdab2c9d 100644
--- a/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
+++ b/docs/known-issues/es/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
@@ -18,9 +18,7 @@ internalReference: 566791
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el CMS permite la creación de carpetas con los mismos nombres que las carpetas por defecto, pero posteriormente no permite editar/borrar estas nuevas carpetas
diff --git a/docs/known-issues/es/cms-legacy-collections-timeout.md b/docs/known-issues/es/cms-legacy-collections-timeout.md
index 0aa6162b3..d6efcf906 100644
--- a/docs/known-issues/es/cms-legacy-collections-timeout.md
+++ b/docs/known-issues/es/cms-legacy-collections-timeout.md
@@ -18,9 +18,7 @@ internalReference: 434026
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 A menudo, al intentar guardar los datos de un grupo de colecciones utilizando la aplicación de colecciones heredada, en la ruta /admin/a e intentando Guardar grupo, el usuario, en casos de catálogos grandes (gran cantidad de categorías, marcas, productos), se encontrará con un mensaje de error de tiempo de espera y no podrá guardar sus cambios.
 
diff --git a/docs/known-issues/es/cms-loyalty-value-settings-not-working.md b/docs/known-issues/es/cms-loyalty-value-settings-not-working.md
index 2c4e9767c..79160a905 100644
--- a/docs/known-issues/es/cms-loyalty-value-settings-not-working.md
+++ b/docs/known-issues/es/cms-loyalty-value-settings-not-working.md
@@ -18,9 +18,7 @@ internalReference: 726849
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md b/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
index 6e41e47d6..b3f7f9478 100644
--- a/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
+++ b/docs/known-issues/es/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
@@ -18,9 +18,7 @@ internalReference: 540756
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se introduce un valor en el campo Unidad de masa en los ajustes del CMS, el sistema no permite eliminar el valor por UI
diff --git a/docs/known-issues/es/cms-settings-role-not-working-as-expected.md b/docs/known-issues/es/cms-settings-role-not-working-as-expected.md
index 3452c7fa0..f9c9f74c4 100644
--- a/docs/known-issues/es/cms-settings-role-not-working-as-expected.md
+++ b/docs/known-issues/es/cms-settings-role-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 538706
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 CMS Settings Role no funciona como se esperaba. A veces el usuario no puede acceder al CMS incluso después de ser añadido al rol.
diff --git a/docs/known-issues/es/cms-styles-selector-doesnt-work-in-development-workspaces.md b/docs/known-issues/es/cms-styles-selector-doesnt-work-in-development-workspaces.md
index 722ee6c39..8005321a1 100644
--- a/docs/known-issues/es/cms-styles-selector-doesnt-work-in-development-workspaces.md
+++ b/docs/known-issues/es/cms-styles-selector-doesnt-work-in-development-workspaces.md
@@ -18,9 +18,7 @@ internalReference: 388544
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/cobranded-saved-card-with-wrong-payment-system-id.md b/docs/known-issues/es/cobranded-saved-card-with-wrong-payment-system-id.md
index c1bd2b384..f3778deab 100644
--- a/docs/known-issues/es/cobranded-saved-card-with-wrong-payment-system-id.md
+++ b/docs/known-issues/es/cobranded-saved-card-with-wrong-payment-system-id.md
@@ -18,9 +18,7 @@ internalReference: 833400
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, cuando se paga un pedido con una tarjeta de marca compartida, la tarjeta guardada tiene el identificador del sistema de pago incorrecto. Cuando se produce este problema, la información de la tarjeta guardada se muestra en el método de pago incorrecto en la interfaz de usuario de la tarjeta.
diff --git a/docs/known-issues/es/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md b/docs/known-issues/es/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md
index 8fbc716a9..114dd2e63 100644
--- a/docs/known-issues/es/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md
+++ b/docs/known-issues/es/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 789499
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una app no recibe peticiones durante un tiempo, entra en cold start. Courier entonces hace varios intentos de enviar eventos hasta que la app "despierta". Cuando la app no "despierta" las peticiones a la misma pueden fallar debido a un timeout. Como resultado, resulta que algunos eventos parecen no enviarse nunca. Se trata de un comportamiento intermitente.
diff --git a/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md b/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md
index 2215a0b04..ad1752ef2 100644
--- a/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md
+++ b/docs/known-issues/es/collapsible-menu-issues-rendering-all-the-items.md
@@ -18,9 +18,7 @@ internalReference: 542091
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, cuando se utiliza un submenú plegable que tiene muchos elementos, el tamaño del menú puede fallar y con ello no mostrar todos los elementos dentro. Esto sucede debido a un valor calculado que define la altura del menú.
diff --git a/docs/known-issues/es/collection-functionality-doesnt-work-on-giftcard.md b/docs/known-issues/es/collection-functionality-doesnt-work-on-giftcard.md
index 81daf2645..0cf4e4787 100644
--- a/docs/known-issues/es/collection-functionality-doesnt-work-on-giftcard.md
+++ b/docs/known-issues/es/collection-functionality-doesnt-work-on-giftcard.md
@@ -18,19 +18,13 @@ internalReference: 319349
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/collection-ordering-not-working-as-expected.md b/docs/known-issues/es/collection-ordering-not-working-as-expected.md
index 9747ca1fc..87ee4fdbf 100644
--- a/docs/known-issues/es/collection-ordering-not-working-as-expected.md
+++ b/docs/known-issues/es/collection-ordering-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 502409
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En Colecciones (Beta), deberíamos poder cambiar el orden de los productos dentro de una colección utilizando la función "Mover a posición":
diff --git a/docs/known-issues/es/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md b/docs/known-issues/es/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md
index 38f9517ab..3a437c71d 100644
--- a/docs/known-issues/es/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md
+++ b/docs/known-issues/es/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md
@@ -18,9 +18,7 @@ internalReference: 439856
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las páginas de colecciones a las que se accede a través de map=productClusterNames muestran el nombre de la colección sin acentos en el componente search-title.
diff --git a/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md b/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md
index 8e58a01bb..e8c99a291 100644
--- a/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md
+++ b/docs/known-issues/es/collections-does-not-allow-more-than-1000-skus-per-upload.md
@@ -18,9 +18,7 @@ internalReference: 793274
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, no es posible subir artículos al nuevo módulo de colecciones con una lista que tenga más de 1000 SKUs, ya que el proceso se agotará.
diff --git a/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md b/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
index 66019514b..781eba7ba 100644
--- a/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
+++ b/docs/known-issues/es/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
@@ -18,9 +18,7 @@ internalReference: 1043470
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las páginas de resultados de búsqueda personalizadas configuradas con el id de colección no funcionan cuando se asignan diferentes colecciones de productos a una organización.
diff --git a/docs/known-issues/es/collections-dont-open-on-subaccounts.md b/docs/known-issues/es/collections-dont-open-on-subaccounts.md
index 26d036e23..4fb4ff43c 100644
--- a/docs/known-issues/es/collections-dont-open-on-subaccounts.md
+++ b/docs/known-issues/es/collections-dont-open-on-subaccounts.md
@@ -18,9 +18,7 @@ internalReference: 649948
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar abrir una colección en el módulo de nuevas colecciones de una subcuenta se devuelve un error "Lo sentimos, se ha producido un error desconocido".
diff --git a/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md b/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md
index f1d103140..35366cedb 100644
--- a/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md
+++ b/docs/known-issues/es/collections-export-only-shows-1st-sku-of-inactive-product.md
@@ -18,9 +18,7 @@ internalReference: 1040753
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza el módulo de colecciones y se intenta exportar registros, si el producto listado en una colección dada tiene todos sus skus configurados como inactivos, la hoja exportada sólo listará 1 de los skus del producto, en lugar de todos.
diff --git a/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index 3ba91f134..3170a84e9 100644
--- a/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/es/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -18,9 +18,7 @@ internalReference: 697168
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md b/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md
index 844c964b3..ad8912c0e 100644
--- a/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md
+++ b/docs/known-issues/es/collections-named-with-special-characters-cannot-be-exported.md
@@ -18,9 +18,7 @@ internalReference: 683343
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera que una colección pueda ser exportada en el admin. Sin embargo, las colecciones con nombres que contienen símbolos como `$` , `+` o `,` no se pueden exportar.
diff --git a/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md b/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md
index d6ac05511..c5eb7a65d 100644
--- a/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md
+++ b/docs/known-issues/es/collections-page-in-organization-details-shows-only-20-collections.md
@@ -18,9 +18,7 @@ internalReference: 891511
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La página Colecciones en Detalles de la Organización muestra sólo 20 colecciones incluso después de cambiar la cantidad de filas en la parte inferior de la página.
diff --git a/docs/known-issues/es/collections-schedule-end-date-not-working.md b/docs/known-issues/es/collections-schedule-end-date-not-working.md
index 0a76be9fd..87e5e35c1 100644
--- a/docs/known-issues/es/collections-schedule-end-date-not-working.md
+++ b/docs/known-issues/es/collections-schedule-end-date-not-working.md
@@ -18,9 +18,7 @@ internalReference: 497880
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se alcanza la fecha de finalización de una colección programada, no se desencadena el proceso de reindexación de los productos que contiene, lo que hace que la programación de la fecha de finalización no sea funcional en su conjunto.
diff --git a/docs/known-issues/es/collections-schedule-start-date-not-working.md b/docs/known-issues/es/collections-schedule-start-date-not-working.md
index fa969ad72..807d49793 100644
--- a/docs/known-issues/es/collections-schedule-start-date-not-working.md
+++ b/docs/known-issues/es/collections-schedule-start-date-not-working.md
@@ -18,9 +18,7 @@ internalReference: 667328
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se alcanza la fecha de inicio de una colección programada, el proceso de reindexación de los productos en ella no se activa, es decir, la programación de la fecha de inicio no funciona en su totalidad. En consecuencia, los productos no se indexan en la colección en la fecha configurada.
diff --git a/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md b/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md
index 26cd13b92..046c48421 100644
--- a/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md
+++ b/docs/known-issues/es/collections-trigger-not-working-as-expected-on-progressive-discounts.md
@@ -18,9 +18,7 @@ internalReference: 930849
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear una promoción de descuento progresivo el cliente puede establecer el activador por colección, por una lista de SKU o por ambas.
diff --git a/docs/known-issues/es/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md b/docs/known-issues/es/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md
index c8ff023ba..6249df8ea 100644
--- a/docs/known-issues/es/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md
+++ b/docs/known-issues/es/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 344451
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La nueva interfaz de colecciones, `.myvtex.com/admin/collections`, no permite a los usuarios buscar productos con caracteres especiales.
diff --git a/docs/known-issues/es/comment-vtexcrm-field-is-not-showing-its-content.md b/docs/known-issues/es/comment-vtexcrm-field-is-not-showing-its-content.md
index c5f3d6c87..6a9be8331 100644
--- a/docs/known-issues/es/comment-vtexcrm-field-is-not-showing-its-content.md
+++ b/docs/known-issues/es/comment-vtexcrm-field-is-not-showing-its-content.md
@@ -18,9 +18,7 @@ internalReference: 565919
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md b/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
index 97268741b..05ff92e8d 100644
--- a/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
+++ b/docs/known-issues/es/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
@@ -18,9 +18,7 @@ internalReference: 416936
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hemos recibido algunas consultas sobre pedidos que estaban atascados en el estado de pago aprobado pero que ya lo estaban, lo que no debería ocurrir en el flujo normal de pedidos.
diff --git a/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md b/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
index 0511d5bfc..e1924fed3 100644
--- a/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
+++ b/docs/known-issues/es/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
@@ -18,9 +18,7 @@ internalReference: 833338
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el componente "drawer" se implementa en "product-summary", hace que la página se recargue después de la página 3 en iOS, y puede que se muestre un mensaje de error.
diff --git a/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md b/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
index d6ba76598..1db6f5599 100644
--- a/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
+++ b/docs/known-issues/es/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
@@ -18,9 +18,7 @@ internalReference: 658452
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El componente Selector de Vendedor presenta incoherencias en los precios de entrega/envío en función del importe del pedido.
diff --git a/docs/known-issues/es/components-in-a-kit-with-the-same-price.md b/docs/known-issues/es/components-in-a-kit-with-the-same-price.md
index 2e5e0caba..f40abe7f3 100644
--- a/docs/known-issues/es/components-in-a-kit-with-the-same-price.md
+++ b/docs/known-issues/es/components-in-a-kit-with-the-same-price.md
@@ -18,9 +18,7 @@ internalReference: 989371
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los componentes de un kit tienen el mismo precio cuando se configura una promoción de regalo y la realiza un vendedor habitual.
diff --git a/docs/known-issues/es/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md b/docs/known-issues/es/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md
index 3ebb6b3b4..f43a3b001 100644
--- a/docs/known-issues/es/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md
+++ b/docs/known-issues/es/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md
@@ -18,9 +18,7 @@ internalReference: 325273
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La configuración de la cantidad máxima de un mismo artículo en el carrito no puede ser modificada por las cuentas de franquicia (vendedor de marca blanca), ya que tiene lugar en una pantalla de catálogo heredada (/admin/Site/ConfigForm.aspx) - módulo que se elimina de las cuentas de franquicia, ya que heredan los productos de la cuenta padre.
diff --git a/docs/known-issues/es/confirmed-order-email-not-being-sent.md b/docs/known-issues/es/confirmed-order-email-not-being-sent.md
index cd30f7b00..7429ab324 100644
--- a/docs/known-issues/es/confirmed-order-email-not-being-sent.md
+++ b/docs/known-issues/es/confirmed-order-email-not-being-sent.md
@@ -18,9 +18,7 @@ internalReference: 423628
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Checkout no mapea todos los flujos donde el "GatewayCallback" debe disparar el evento "Raised OrderPlaced", por lo que los flujos no mapeados son aptos para no disparar este evento como se espera, afectando directamente al email de confirmación de pedido a enviar.
diff --git a/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md b/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
index adcd872a4..7a0f041a8 100644
--- a/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
+++ b/docs/known-issues/es/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 933958
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Múltiples especificaciones con el mismo nombre son agrupadas en la misma _"faceta"_ por la Búsqueda Inteligente, lo que puede ser un problema si tienen diferentes configuraciones.
diff --git a/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md b/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
index aace7bd6d..7ac752fe5 100644
--- a/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
+++ b/docs/known-issues/es/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
@@ -18,9 +18,7 @@ internalReference: 531277
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 ## **Resumen**
 
diff --git a/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md b/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
index 1bdc587f3..491991af5 100644
--- a/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
+++ b/docs/known-issues/es/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
@@ -18,9 +18,7 @@ internalReference: 1017370
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos algunos logs en la consola informando de bloqueos de script debido a restricciones a través de la cabecera CSP.
diff --git a/docs/known-issues/es/cookie-broken-the-apisessions.md b/docs/known-issues/es/cookie-broken-the-apisessions.md
index 404795569..4e9da09af 100644
--- a/docs/known-issues/es/cookie-broken-the-apisessions.md
+++ b/docs/known-issues/es/cookie-broken-the-apisessions.md
@@ -18,9 +18,7 @@ internalReference: 779014
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay un script que genera una cookie para rastrear a los usuarios y su cookie rompe la llamada a /api/sessions, por ejemplo porque tiene una carta especial en el valor cookie. Entonces necesitamos descartar esa cookie malformada de nuestro lado y mantener todas las demás, para que no afecte el comportamiento.
diff --git a/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md b/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
index 3dbed70cb..0ea8983b5 100644
--- a/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
+++ b/docs/known-issues/es/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
@@ -18,9 +18,7 @@ internalReference: 921115
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al dar de alta un nuevo cliente mediante el Admin Clientes B2B, el desplegable del centro de coste sólo muestra 25 opciones.
diff --git a/docs/known-issues/es/cost-price-rounding-logic-diverges-on-computed-prices-api.md b/docs/known-issues/es/cost-price-rounding-logic-diverges-on-computed-prices-api.md
index 913fe252d..16f085f95 100644
--- a/docs/known-issues/es/cost-price-rounding-logic-diverges-on-computed-prices-api.md
+++ b/docs/known-issues/es/cost-price-rounding-logic-diverges-on-computed-prices-api.md
@@ -18,9 +18,7 @@ internalReference: 842336
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la API de precios calculados tiene una propiedad llamada 'precio de coste' que en escenarios específicos podría mostrar una diferencia de 1 céntimo entre su valor en la interfaz de usuario y la API de precios calculados https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-
diff --git a/docs/known-issues/es/country-field-as-null-in-invoicedata.md b/docs/known-issues/es/country-field-as-null-in-invoicedata.md
index 12a6b5e13..ef26faee5 100644
--- a/docs/known-issues/es/country-field-as-null-in-invoicedata.md
+++ b/docs/known-issues/es/country-field-as-null-in-invoicedata.md
@@ -18,9 +18,7 @@ internalReference: 382175
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El campo País en invoiceData puede ser nulo si se envía vía API o hay una dirección de factura en el Sistema de Perfiles con el país como nulo, por lo que se crearán pedidos con datos incompletos en invoiceData.
diff --git a/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md b/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
index f367f1c01..0594cd60e 100644
--- a/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
+++ b/docs/known-issues/es/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
@@ -18,9 +18,7 @@ internalReference: 335581
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/coupon-usage-not-restored-for-incomplete-orders.md b/docs/known-issues/es/coupon-usage-not-restored-for-incomplete-orders.md
index 40269c2f4..450943193 100644
--- a/docs/known-issues/es/coupon-usage-not-restored-for-incomplete-orders.md
+++ b/docs/known-issues/es/coupon-usage-not-restored-for-incomplete-orders.md
@@ -18,9 +18,7 @@ internalReference: 639418
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/coupons-created-as-archived-temporarrily.md b/docs/known-issues/es/coupons-created-as-archived-temporarrily.md
index 9909da47d..ccbf9f6b7 100644
--- a/docs/known-issues/es/coupons-created-as-archived-temporarrily.md
+++ b/docs/known-issues/es/coupons-created-as-archived-temporarrily.md
@@ -18,9 +18,7 @@ internalReference: 892041
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se crea un cupón, la UI/API muestra que está archivado durante unos minutos (~2) cuando en realidad (en la base de datos de precios), el cupón está activo.
diff --git a/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md b/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md
index 3cc064166..a65ed020d 100644
--- a/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md
+++ b/docs/known-issues/es/create-product-api-doesnt-send-nulls-as-release-date-values.md
@@ -18,9 +18,7 @@ internalReference: 1024207
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar las API de creación o actualización de productos en la aplicación de catálogo: https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product y enviar el campo releaseDate como null, en su valor, se crea con la fecha actual en su lugar.
diff --git a/docs/known-issues/es/create-seller-with-additional-information-is-returning-an-error.md b/docs/known-issues/es/create-seller-with-additional-information-is-returning-an-error.md
index 73628d728..c4c1c154a 100644
--- a/docs/known-issues/es/create-seller-with-additional-information-is-returning-an-error.md
+++ b/docs/known-issues/es/create-seller-with-additional-information-is-returning-an-error.md
@@ -18,9 +18,7 @@ internalReference: 741110
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md b/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
index 1c71a4b93..057ed0535 100644
--- a/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
+++ b/docs/known-issues/es/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
@@ -18,9 +18,7 @@ internalReference: 1005112
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para las cuentas regionalizadas el sistema de índices filtra por los canales de venta regionalizados el stockbalance que debe aparecer, para no mostrar vinculaciones de ventas que no están regionalizadas.
diff --git a/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md b/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
index 93a135cbe..d802fe287 100644
--- a/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
+++ b/docs/known-issues/es/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
@@ -18,9 +18,7 @@ internalReference: 1010392
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tratar con una cantidad masiva de redirecciones puede romper la página de la interfaz de usuario. Si tiene muchas redirecciones o necesita borrar una gran cantidad de redirecciones esto puede llevar a un error en el que la página de la interfaz de usuario se carga para siempre y nunca devuelve la información de las redirecciones. Creemos que esto puede ocurrir porque cuando borramos una gran cantidad de redirecciones las primeras páginas de la consulta `listRedirects` están en blanco y la interfaz de usuario buscará estas primeras páginas para cargar las primeras redirecciones y nunca las encontrará.
diff --git a/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md b/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
index 95b00d8b3..e6c947975 100644
--- a/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
+++ b/docs/known-issues/es/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference: 971936
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de crear redirecciones erróneas que contienen caracteres que no deben ser subidos: ie.: #, consultas, o redirecciones que deberían ser creadas a nivel de servidor, la carga/descarga masiva del csv a través del CLI ya no funciona.
diff --git a/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md b/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md
index ff50f2203..058d92904 100644
--- a/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md
+++ b/docs/known-issues/es/criteria-composition-is-not-returned-on-the-explained-search-ui.md
@@ -18,9 +18,7 @@ internalReference: 852898
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se busca un término en el que la respuesta es un solo producto, ese producto no tendrá la composición de criterios que aparece en la pantalla de la búsqueda explicada.
diff --git a/docs/known-issues/es/cultureinfo-does-not-allow-values-longer-than-10-characters.md b/docs/known-issues/es/cultureinfo-does-not-allow-values-longer-than-10-characters.md
index 6541c173c..47a0b0cd3 100644
--- a/docs/known-issues/es/cultureinfo-does-not-allow-values-longer-than-10-characters.md
+++ b/docs/known-issues/es/cultureinfo-does-not-allow-values-longer-than-10-characters.md
@@ -18,9 +18,7 @@ internalReference: 667652
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el campo CultureInfo en el registro de la política comercial tiene una limitación a valores de 10 caracteres, esto hace que valores mayores a este generen un error SWW al guardar la política.
diff --git a/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md b/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md
index f0c99f4b0..889fda270 100644
--- a/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md
+++ b/docs/known-issues/es/currency-symbol-does-not-follow-admin-language.md
@@ -18,9 +18,7 @@ internalReference: 1000915
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario accede a la pantalla de configuración del carrito en la zona de pedidos (`https://{accountname}}.myvtex.com/admin/checkout/#/configurations )` el símbolo de la moneda sigue las convenciones de la configuración regional indicada por el admin, el intercambio de este símbolo se realiza siempre que el admin indica una configuración regional diferente, sin embargo según nuestro análisis este intercambio está fallando en determinados momentos, provocando que el símbolo de la moneda indicado sea el predeterminado de la página que en este caso es R$.
diff --git a/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md b/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md
index 9fe8de218..15ba2c987 100644
--- a/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md
+++ b/docs/known-issues/es/custom-attribute-mapper-mercado-livre.md
@@ -18,9 +18,7 @@ internalReference: 521197
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md b/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
index 406730dc4..a2c0ee52b 100644
--- a/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
+++ b/docs/known-issues/es/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
@@ -18,9 +18,7 @@ internalReference: 871480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se crea un elemento personalizado con más de un elemento HTML, sólo se carga el primero en la plantilla.
diff --git a/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md b/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
index 24937ca5b..2522d88b5 100644
--- a/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
+++ b/docs/known-issues/es/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
@@ -18,9 +18,7 @@ internalReference: 412632
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al subir una imagen en miniatura a un bloque de vídeo sólo se actualiza para la versión de escritorio, la miniatura móvil se mantiene vacía.
diff --git a/docs/known-issues/es/customer-credit-doesnt-show-installments-correctly.md b/docs/known-issues/es/customer-credit-doesnt-show-installments-correctly.md
index ab810503f..5f265c841 100644
--- a/docs/known-issues/es/customer-credit-doesnt-show-installments-correctly.md
+++ b/docs/known-issues/es/customer-credit-doesnt-show-installments-correctly.md
@@ -18,9 +18,7 @@ internalReference: 501730
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 El crédito del cliente no muestra los diferentes valores entre reglas con el mismo número de cuotas y diferentes periodos. Para entender mejor este problema, debemos observar el comportamiento de la pasarela y del Crédito Cliente:
 
diff --git a/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md b/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
index 14a22d5f9..08e247111 100644
--- a/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
+++ b/docs/known-issues/es/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
@@ -18,9 +18,7 @@ internalReference: 369457
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El estado de las facturas en la interfaz de MyCredits de las tiendas españolas no se muestra como debería, se muestran los nombres de los componentes en lugar de "cancelado", "vencido", "pagado" o "abierto".
diff --git a/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md b/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md
index 779195df6..f1ea6ee40 100644
--- a/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md
+++ b/docs/known-issues/es/customer-credit-total-due-value-updating-according-to-the-pagination.md
@@ -18,9 +18,7 @@ internalReference: 432587
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El valor del "Total a pagar" en una cuenta de crédito de cliente no está mostrando el valor total, sino el valor total en la paginación actual de la UI
diff --git a/docs/known-issues/es/customer-credits-invoice-list-cannot-be-exported.md b/docs/known-issues/es/customer-credits-invoice-list-cannot-be-exported.md
index d2638d931..27ac36841 100644
--- a/docs/known-issues/es/customer-credits-invoice-list-cannot-be-exported.md
+++ b/docs/known-issues/es/customer-credits-invoice-list-cannot-be-exported.md
@@ -18,9 +18,7 @@ internalReference: 327219
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Existe una limitación con el módulo de Crédito a Clientes que no permite al usuario exportar más de 150k facturas a la vez.
diff --git a/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
index 6074946e3..d3d55b165 100644
--- a/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
+++ b/docs/known-issues/es/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -18,9 +18,7 @@ internalReference: 340036
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el pedido tiene "profileErrorOnLoading=true", el comportamiento esperado es que el perfil del cliente, la dirección y la tarjeta de crédito no se guarden/actualicen en el Sistema de Perfiles.
diff --git a/docs/known-issues/es/customer-information-being-removed-from-profile-system-without-clear-reason.md b/docs/known-issues/es/customer-information-being-removed-from-profile-system-without-clear-reason.md
index 81afaf5bd..d17138db3 100644
--- a/docs/known-issues/es/customer-information-being-removed-from-profile-system-without-clear-reason.md
+++ b/docs/known-issues/es/customer-information-being-removed-from-profile-system-without-clear-reason.md
@@ -18,9 +18,7 @@ internalReference: 469823
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces recibimos informes en los que la información del cliente se ha eliminado de las entidades CL y AD de Master Data, lo que puede gestionarse de muchas maneras: uso directo de Master Data por parte de la propia tienda (UI, API, importación/exportación de datos) y otras integraciones internas de la plataforma, como el servicio CHK a través de Profile System.
diff --git a/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md b/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md
index f509427ed..7dc3ee149 100644
--- a/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md
+++ b/docs/known-issues/es/customer-information-is-not-saved-in-the-profile-system.md
@@ -18,9 +18,7 @@ internalReference: 784763
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, la información de un nuevo cliente no se guarda en el Sistema de Perfiles.
diff --git a/docs/known-issues/es/customers-cant-see-products-catalog-page-after-logging-in.md b/docs/known-issues/es/customers-cant-see-products-catalog-page-after-logging-in.md
index 5d65f02d3..daf70f565 100644
--- a/docs/known-issues/es/customers-cant-see-products-catalog-page-after-logging-in.md
+++ b/docs/known-issues/es/customers-cant-see-products-catalog-page-after-logging-in.md
@@ -18,19 +18,13 @@ internalReference: 550112
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md b/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
index 63a9a1379..ea93343d4 100644
--- a/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
+++ b/docs/known-issues/es/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
@@ -18,9 +18,7 @@ internalReference: 334027
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente las expresiones de cluster personalizadas no funcionan en las promociones de tipo envío gratuito.
diff --git a/docs/known-issues/es/cvv-without-validation-of-characters-type.md b/docs/known-issues/es/cvv-without-validation-of-characters-type.md
index f9ef20401..480fa5dda 100644
--- a/docs/known-issues/es/cvv-without-validation-of-characters-type.md
+++ b/docs/known-issues/es/cvv-without-validation-of-characters-type.md
@@ -18,9 +18,7 @@ internalReference: 425204
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el momento de la compra, pedimos la información de la tarjeta de crédito y sólo permitimos que el cliente escriba números en el campo Número de tarjeta, y sólo letras en el campo Nombre del propietario de la tarjeta. Sin embargo, no hacemos una validación similar para el campo CVV, permitiendo que el cliente escriba letras en este campo
diff --git a/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md b/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
index c755fbc9f..0fc92064c 100644
--- a/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
+++ b/docs/known-issues/es/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
@@ -18,9 +18,7 @@ internalReference: 719606
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Pedidos que están en `"Esperando Autorización para Despachar" `en VTEX, pero aún están en `"pago_pendiente"` en Dafiti.
diff --git a/docs/known-issues/es/dafiti-quality-dafiti-images.md b/docs/known-issues/es/dafiti-quality-dafiti-images.md
index 92173a6ac..8ad24ad5b 100644
--- a/docs/known-issues/es/dafiti-quality-dafiti-images.md
+++ b/docs/known-issues/es/dafiti-quality-dafiti-images.md
@@ -18,9 +18,7 @@ internalReference: 675317
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La imagen pierde calidad cuando llega a Dafiti.
diff --git a/docs/known-issues/es/daily-metrics-on-search-report-showing-duplicated-date.md b/docs/known-issues/es/daily-metrics-on-search-report-showing-duplicated-date.md
index f2cf47113..37753f60a 100644
--- a/docs/known-issues/es/daily-metrics-on-search-report-showing-duplicated-date.md
+++ b/docs/known-issues/es/daily-metrics-on-search-report-showing-duplicated-date.md
@@ -18,9 +18,7 @@ internalReference: 508883
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se descarga un informe de búsqueda, la tabla que contiene métricas como búsquedas, clics y clics únicos al final del informe contiene una columna de fecha que muestra entradas duplicadas sin una razón aparente como se puede ver en la imagen:
diff --git a/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md b/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md
index 715f24bdd..80a25c5eb 100644
--- a/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md
+++ b/docs/known-issues/es/deactivated-payment-system-rendering-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 1049543
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El problema parece ocurrir sólo en las subcuentas, incluso desactivado (también eliminado) el método de pago rinde en la caja
diff --git a/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md b/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md
index 38468865a..d483f8a9d 100644
--- a/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md
+++ b/docs/known-issues/es/deadlocked-error-when-using-catalog-apis.md
@@ -18,9 +18,7 @@ internalReference: 862626
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md b/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
index 5979d4656..f72b01618 100644
--- a/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
+++ b/docs/known-issues/es/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
@@ -18,9 +18,7 @@ internalReference: 461095
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar el conector Firstdata para procesar pagos de débito, nuestro código está diseñado para esperar que el campo TransactionState se establezca como "CAPTURED". Sin embargo, hemos encontrado un problema en el que el proveedor está enviando ambos valores "CAPTURED" y "SETTLED", lo que está causando un error:
diff --git a/docs/known-issues/es/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md b/docs/known-issues/es/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md
index d301b5998..b00f42f9a 100644
--- a/docs/known-issues/es/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md
+++ b/docs/known-issues/es/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md
@@ -18,9 +18,7 @@ internalReference: 787367
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El conector heredado DecidirV1 utiliza un método interno para calcular los campos `CSPTGRANDTOTALAMOUNT` y `CSITTOTALAMOUNT`, que es el producto entre el valor del producto y la cantidad. Este método da como resultado una cadena con dos decimales. En consecuencia, cuando el precio del producto contiene más de dos decimales, el valor del campo `CSPTGRANDTOTALAMOUNT` diverge, ya que es el propio valor del pago.
diff --git a/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md b/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
index 61c434b99..734dbac73 100644
--- a/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
+++ b/docs/known-issues/es/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
@@ -18,9 +18,7 @@ internalReference: 384009
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Esto sucede cuando una transacción obtiene el estado 480 que significa "REVISIÓN", y comienza a reintentar hasta que recibe una carga útil nula. Entonces, después de eso, "reprocesamos" la transacción lo que provoca un fallo y la cancelación.
diff --git a/docs/known-issues/es/default-value-on-specification-only-working-when-creating-products-through-admin.md b/docs/known-issues/es/default-value-on-specification-only-working-when-creating-products-through-admin.md
index 8c4963be4..59e0b77b4 100644
--- a/docs/known-issues/es/default-value-on-specification-only-working-when-creating-products-through-admin.md
+++ b/docs/known-issues/es/default-value-on-specification-only-working-when-creating-products-through-admin.md
@@ -18,9 +18,7 @@ internalReference: 550097
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se crea una especificación en una categoría VTEX se puede configurar un valor por defecto que se rellenará cuando se cree el sku/producto sin esta información.
diff --git a/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md b/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
index ce42ea4fa..5db43cee4 100644
--- a/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
+++ b/docs/known-issues/es/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
@@ -18,9 +18,7 @@ internalReference: 396914
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al cargar una hoja de cálculo y luego hacer clic en "guardar cambios" en las configuraciones de la política de envío, la hoja de cálculo debe ser procesada por nuestro módulo de logística. El tiempo de procesamiento puede variar en función del tamaño del archivo, pero suele tardar unos minutos. En algunos casos, el tiempo de procesamiento puede durar hasta un par de horas o incluso días, y el estado permanece bloqueado en "procesamiento".
diff --git a/docs/known-issues/es/delay-to-register-cancelreason-in-the-order-json.md b/docs/known-issues/es/delay-to-register-cancelreason-in-the-order-json.md
index 834faa222..a9d5ed055 100644
--- a/docs/known-issues/es/delay-to-register-cancelreason-in-the-order-json.md
+++ b/docs/known-issues/es/delay-to-register-cancelreason-in-the-order-json.md
@@ -18,9 +18,7 @@ internalReference: 792650
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a la forma en que se ejecuta el flujo de actualización de la orden desde cualquier estado hasta cancelada, es posible que el sistema de órdenes tarde un tiempo en registrar el CancelReason en el json de la orden, provocando un breve escenario de inconsistencia si se consulta o utiliza el Json unos segundos después de la acción de cancelación;
diff --git a/docs/known-issues/es/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md b/docs/known-issues/es/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md
index 8a4e4aa4c..f48b97005 100644
--- a/docs/known-issues/es/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md
+++ b/docs/known-issues/es/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md
@@ -18,9 +18,7 @@ internalReference: 369633
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la transacción **NO** tiene antifraude, se toma el valor más corto entre `delayToAutoSettle` y `delayToAutoSettleAfterAntifraud`. En este caso, el responsable de la captura es el `EarlySettlementWorker`, que es el trabajador de captura anticipada. Técnicamente, es el trabajador que se llama después de que el antifraude se realice, pero cuando no hay uno, comienza su cuenta atrás después de la autorización del pago.
diff --git a/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md b/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
index 3a80108d9..85100b2fc 100644
--- a/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
+++ b/docs/known-issues/es/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
@@ -18,9 +18,7 @@ internalReference: 994066
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md b/docs/known-issues/es/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md
index b35fc8bef..193c884eb 100644
--- a/docs/known-issues/es/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md
+++ b/docs/known-issues/es/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md
@@ -18,9 +18,7 @@ internalReference: 490740
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, si tiene una colección creada por completo en la administración de Colecciones nuevas/antiguas (CMS), al eliminarla a través de la interfaz de usuario no se reindexan los productos que contiene, por lo que no se eliminan efectivamente de la colección.
diff --git a/docs/known-issues/es/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md b/docs/known-issues/es/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md
index d8e6eeb68..69f2b1fac 100644
--- a/docs/known-issues/es/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md
+++ b/docs/known-issues/es/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 471612
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md b/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
index cfdaa825e..f2e8e9462 100644
--- a/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
+++ b/docs/known-issues/es/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
@@ -18,9 +18,7 @@ internalReference: 862830
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si la función de programación de entregas está en uso y la capacidad de entrega está habilitada, hay dos escenarios conocidos que pueden hacer que la ventana esté disponible incluso después de haber alcanzado su límite máximo de capacidad configurada.
diff --git a/docs/known-issues/es/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md b/docs/known-issues/es/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md
index 826da331c..84a8f7907 100644
--- a/docs/known-issues/es/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md
+++ b/docs/known-issues/es/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md
@@ -18,9 +18,7 @@ internalReference: 547053
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md b/docs/known-issues/es/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md
index 2a03092c9..aa108ec78 100644
--- a/docs/known-issues/es/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md
+++ b/docs/known-issues/es/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 296786
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El selector de fecha/hora para la entrega programada desaparece cuando el usuario cambia de "recoger" a "recibir", este comportamiento ocurre independientemente del uso de la función Lean Shipping.
diff --git a/docs/known-issues/es/delivery-method-selector-does-not-appear-in-some-scenarios.md b/docs/known-issues/es/delivery-method-selector-does-not-appear-in-some-scenarios.md
index 4a0ba3bb6..3bac90d40 100644
--- a/docs/known-issues/es/delivery-method-selector-does-not-appear-in-some-scenarios.md
+++ b/docs/known-issues/es/delivery-method-selector-does-not-appear-in-some-scenarios.md
@@ -18,9 +18,7 @@ internalReference: 293784
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las tiendas que tienen opciones de entrega programada pueden tener un mal funcionamiento con respecto a la selección del método de entrega. Esto puede ocurrir con o sin el uso de Lean Shipping.
diff --git a/docs/known-issues/es/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md b/docs/known-issues/es/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md
index 667359858..37ade8c6a 100644
--- a/docs/known-issues/es/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md
+++ b/docs/known-issues/es/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md
@@ -18,9 +18,7 @@ internalReference: 586143
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md b/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md
index 40d0ad195..f8db592db 100644
--- a/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md
+++ b/docs/known-issues/es/delivery-split-with-lean-shipping-offering-invalid-sla.md
@@ -18,9 +18,7 @@ internalReference: 990155
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un carro de la compra incluye productos de diferentes vendedores, con diferentes canales de entrega e ID de SLA entre ellos, la interfaz de usuario de Checkout activa Lean Shipping, resumiendo los SLA disponibles para mostrar sólo las opciones "más rápida" y "más barata" para cada artículo.
diff --git a/docs/known-issues/es/deliverycontracttype-problem-b2w.md b/docs/known-issues/es/deliverycontracttype-problem-b2w.md
index 37f61d744..9eac46f03 100644
--- a/docs/known-issues/es/deliverycontracttype-problem-b2w.md
+++ b/docs/known-issues/es/deliverycontracttype-problem-b2w.md
@@ -18,9 +18,7 @@ internalReference: 605908
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md b/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md
index 45e85982b..abfd7d9a8 100644
--- a/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md
+++ b/docs/known-issues/es/departments-name-not-loading-on-seller-management-commissions-ui.md
@@ -18,9 +18,7 @@ internalReference: 1005799
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al seleccionar un departamento para establecer una comisión específica en la gestión de vendedores la tabla no está cargando el nombre del departamento. Este comportamiento no ocurre con las categorías inferiores.
diff --git a/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md b/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md
index 077eb8e68..e6c330fbc 100644
--- a/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md
+++ b/docs/known-issues/es/diacritics-are-removed-on-catalogapi.md
@@ -18,9 +18,7 @@ internalReference: 623345
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md b/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md
index 5aa58afd5..138f5d5b5 100644
--- a/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md
+++ b/docs/known-issues/es/difference-in-prices-between-pdp-plp-and-checkout-cart.md
@@ -18,9 +18,7 @@ internalReference: 853175
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md b/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md
index 454159698..4e43a8854 100644
--- a/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md
+++ b/docs/known-issues/es/differences-between-specification-value-on-apis-and-portal.md
@@ -18,9 +18,7 @@ internalReference: 853184
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md b/docs/known-issues/es/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md
index 3ee23e467..18ca0b38f 100644
--- a/docs/known-issues/es/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md
+++ b/docs/known-issues/es/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md
@@ -18,9 +18,7 @@ internalReference: 821741
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En los casos en los que un vendedor actúe como vendedor de marca blanca y como vendedor habitual para distintos artículos del mismo carrito, el importe del pago será con el valor del envío duplicado.
diff --git a/docs/known-issues/es/dimension-text-fields-being-unselected-during-sku-creation.md b/docs/known-issues/es/dimension-text-fields-being-unselected-during-sku-creation.md
index 802822f5c..bc02890dd 100644
--- a/docs/known-issues/es/dimension-text-fields-being-unselected-during-sku-creation.md
+++ b/docs/known-issues/es/dimension-text-fields-being-unselected-during-sku-creation.md
@@ -18,9 +18,7 @@ internalReference: 786048
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se crea un SKU desde Admin, es necesario registrar las dimensiones para el envío y las dimensiones reales. Sin embargo, al rellenar uno de los campos de texto y hacer clic (o utilizar el tabulador) para rellenar otro, este campo se deselecciona y es necesario volver a hacer clic en el campo de texto para poder insertar/editar el valor.
diff --git a/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md b/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
index 0eab98da8..2743d08a6 100644
--- a/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
+++ b/docs/known-issues/es/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
@@ -18,9 +18,7 @@ internalReference: 417947
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un problema en el diseño de divulgación que sólo activa el bloque para mostrar, pero no se cierra. Esto es causado por la animación de la prop, que no está funcionando correctamente cuando se establece en el diseño de divulgación y no permite ocultar el elemento después de la apertura.
diff --git a/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md b/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
index 6406993d4..8232a0180 100644
--- a/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
+++ b/docs/known-issues/es/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
@@ -18,9 +18,7 @@ internalReference: 954959
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos no están siendo recuperados en el uso de los cupones, hemos identificado que algunos pedidos no estaban siendo contados por el administrador de cupones.
diff --git a/docs/known-issues/es/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md b/docs/known-issues/es/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md
index 14f89c81e..4e5522243 100644
--- a/docs/known-issues/es/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md
+++ b/docs/known-issues/es/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md
@@ -18,9 +18,7 @@ internalReference: 331188
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 En algunos casos, el valor total del pedido difiere de la suma del valor total de los productos (añadiendo también los gastos de envío y los posibles descuentos, si los hay). Esto ocurre porque el valor mostrado de los artículos forma parte del "sellingPrice", una información del orderForm que pierde precisión por motivos de redondeo.
 
diff --git a/docs/known-issues/es/divergence-delivery-time-netshoes.md b/docs/known-issues/es/divergence-delivery-time-netshoes.md
index bc4c5b447..cf453e028 100644
--- a/docs/known-issues/es/divergence-delivery-time-netshoes.md
+++ b/docs/known-issues/es/divergence-delivery-time-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 635509
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md b/docs/known-issues/es/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md
index 94c0fbadd..780900eaa 100644
--- a/docs/known-issues/es/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md
+++ b/docs/known-issues/es/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md
@@ -18,9 +18,7 @@ internalReference: 657186
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En ciertos casos de kits, la política de envío puede no estar disponible, esto puede suceder debido a la lógica utilizada para los cálculos que involucran el peso.
diff --git a/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md b/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
index 7443ca715..530e3c6c0 100644
--- a/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
+++ b/docs/known-issues/es/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
@@ -18,9 +18,7 @@ internalReference: 1064235
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En nuevos espacios de trabajo o cuentas que nunca cambiaron las configuraciones avanzadas de la Configuración de la Tienda se puede verificar una inconsistencia entre la información en la UI y la bandera aplicada a la cuenta.
diff --git a/docs/known-issues/es/divergence-rule-dafiti.md b/docs/known-issues/es/divergence-rule-dafiti.md
index e5a6ec272..8cff0990b 100644
--- a/docs/known-issues/es/divergence-rule-dafiti.md
+++ b/docs/known-issues/es/divergence-rule-dafiti.md
@@ -18,9 +18,7 @@ internalReference: 594648
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/divergencia-shipping-estimate-b2w.md b/docs/known-issues/es/divergencia-shipping-estimate-b2w.md
index e0a4a9b46..37404844c 100644
--- a/docs/known-issues/es/divergencia-shipping-estimate-b2w.md
+++ b/docs/known-issues/es/divergencia-shipping-estimate-b2w.md
@@ -18,9 +18,7 @@ internalReference: 642448
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md b/docs/known-issues/es/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md
index da9d0c8aa..11a5faf5e 100644
--- a/docs/known-issues/es/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md
+++ b/docs/known-issues/es/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md
@@ -18,9 +18,7 @@ internalReference: 321111
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos casos, los valores de envío prorrateados por artículo entre los pedidos del mercado (lado de la caja) y del vendedor (lado de la ejecución) pueden ser divergentes.
diff --git a/docs/known-issues/es/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md b/docs/known-issues/es/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md
index 2b0d8a22e..33d3d6c60 100644
--- a/docs/known-issues/es/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md
+++ b/docs/known-issues/es/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md
@@ -18,9 +18,7 @@ internalReference: 756629
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el precio del artículo del vendedor _menos_ los descuentos del marketplace tiene un valor negativo, no se puede aplicar al artículo (no pueden tener un precio negativo), por lo que se considerará como cero y se estropeará con otros cálculos. Esto ocurre cuando el mercado está utilizando la función de anulación de precio del vendedor, generando valores más altos que la propia cuenta del vendedor, y luego combinando con una promoción.
diff --git a/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md b/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md
index 4c5546a9e..b473afa11 100644
--- a/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md
+++ b/docs/known-issues/es/divergent-status-on-the-transaction-list-and-on-the-transaction.md
@@ -18,9 +18,7 @@ internalReference: 308919
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El estado de las transacciones es diferente una vez que las abre en comparación con lo que se muestra en la lista de transacciones.
diff --git a/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md b/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
index 8cf8cc395..52db49fa4 100644
--- a/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
+++ b/docs/known-issues/es/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
@@ -18,9 +18,7 @@ internalReference: 766454
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la cuenta tiene configurado "paymentSystemToCheckFirstInstallment" en orderForm Configuration, el cálculo de pago enviará dos peticiones al módulo de promociones. Si hay artículos divididos en el carrito (por ejemplo, promoción Más por Menos), la primera petición enviará los artículos correctamente, pero la segunda enviará los artículos divididos en función de la aplicación de la promoción.
diff --git a/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md b/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
index dd01dbe8c..2f6afc2c4 100644
--- a/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
+++ b/docs/known-issues/es/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
@@ -18,9 +18,7 @@ internalReference: 921944
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Sólo en Safari/iOS, al rellenar el número de documento y desplazarse por los campos de datos del cliente, el campo número de documento (RUT) tendrá el último dígito borrado.
diff --git a/docs/known-issues/es/drag-and-drop-issue-on-site-editor.md b/docs/known-issues/es/drag-and-drop-issue-on-site-editor.md
index 8c895f8e7..fb90252b7 100644
--- a/docs/known-issues/es/drag-and-drop-issue-on-site-editor.md
+++ b/docs/known-issues/es/drag-and-drop-issue-on-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 685103
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los clientes no pueden utilizar la función de arrastrar y soltar en el editor del sitio para subir imágenes, esto probablemente ocurre duo nuestra nueva implementación de nuestro nuevo CMS Media Management.
diff --git a/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md b/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
index ef79ef648..1ea2be809 100644
--- a/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
+++ b/docs/known-issues/es/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
@@ -18,9 +18,7 @@ internalReference: 562588
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md b/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md
index c0b1b44ae..b453e9040 100644
--- a/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md
+++ b/docs/known-issues/es/duplicated-organizations-in-modal-to-switch-between-organizations.md
@@ -18,9 +18,7 @@ internalReference: 986868
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario tiene muchas organizaciones registradas y utiliza el modal para cambiar entre organizaciones, algunas organizaciones se mostrarán duplicadas en la lista.
diff --git a/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md b/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
index b94ce3185..d05d7f032 100644
--- a/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
+++ b/docs/known-issues/es/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
@@ -18,9 +18,7 @@ internalReference: 897301
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vendedor envía el sku con todos los campos declarados en este artículo (https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-) para que el marketplace lo apruebe en el módulo Skus Recibidos.
diff --git a/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md b/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
index f3b663e4b..81220ebf6 100644
--- a/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
+++ b/docs/known-issues/es/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
@@ -18,9 +18,7 @@ internalReference: 866068
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para que podamos entender este comportamiento, primero tenemos que comprender la diferencia entre captura automática y captura anticipada:
diff --git a/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md b/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
index 408bffe15..d71e7a57c 100644
--- a/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
+++ b/docs/known-issues/es/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
@@ -18,9 +18,7 @@ internalReference: 350814
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En las transacciones con la marca de tarjeta Elo, no se está respetando la configuración de captura anticipada, y la transacción se está capturando inmediatamente después de la aprobación.
diff --git a/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md b/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md
index 4c9617ede..4d9ae4eec 100644
--- a/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md
+++ b/docs/known-issues/es/email-not-autofilling-for-new-buyers-after-logging-in.md
@@ -18,9 +18,7 @@ internalReference: 920634
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un nuevo comprador inicia sesión y procede al pago, el correo electrónico no se rellena automáticamente, lo que requiere que el cliente vuelva a introducir su correo electrónico. Esto también ocurre utilizando APIs y enviando cabeceras con las cookies del comprador.
diff --git a/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md b/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md
index 08f0909c2..94e9dba7d 100644
--- a/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md
+++ b/docs/known-issues/es/email-not-autofilling-for-new-users-on-checkoutui.md
@@ -18,9 +18,7 @@ internalReference: 887949
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un nuevo usuario introduce un nuevo correo electrónico en el paso de correo electrónico y pasa a la página siguiente, en el componente de datos del cliente, el correo electrónico no se rellena automáticamente.
diff --git a/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md b/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
index 583756ff3..a28b9a251 100644
--- a/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
+++ b/docs/known-issues/es/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
@@ -18,9 +18,7 @@ internalReference: 910328
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si los correos electrónicos tienen algún rol de ventas asociado, no se les permite suplantar utilizando la función Organizaciones B2B.
diff --git a/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md b/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
index aca00eb58..a57fde604 100644
--- a/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
+++ b/docs/known-issues/es/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
@@ -18,9 +18,7 @@ internalReference: 1022550
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/erederest-only-allows-cancelation-when-the-status-code-is-359.md b/docs/known-issues/es/erederest-only-allows-cancelation-when-the-status-code-is-359.md
index 075b6caa3..b7679282e 100644
--- a/docs/known-issues/es/erederest-only-allows-cancelation-when-the-status-code-is-359.md
+++ b/docs/known-issues/es/erederest-only-allows-cancelation-when-the-status-code-is-359.md
@@ -18,9 +18,7 @@ internalReference: 740084
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Nuestro conector heredado ERedeRest realiza una cancelación a través de una petición al proveedor y espera un statusCode=359 que significa que la cancelación se ha realizado correctamente. Cualquier otro código significa para nuestra pasarela que el estado es indefinido aunque, en algunos casos, significa que la solicitud de reembolso/cancelación también fue exitosa, por lo tanto, nos lleva a reintentar la cancelación sin embargo nos quedamos atascados en este paso ya que la cancelación ya se ha completado en el lado del proveedor.
diff --git a/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index 40122dd45..4dcf25f66 100644
--- a/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/es/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -18,9 +18,7 @@ internalReference: 417639
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 ## **Resumen**
 
diff --git a/docs/known-issues/es/erro-sqlerrm-no-tracking-brinox-b2w.md b/docs/known-issues/es/erro-sqlerrm-no-tracking-brinox-b2w.md
index 3c26a9f1a..036ec9287 100644
--- a/docs/known-issues/es/erro-sqlerrm-no-tracking-brinox-b2w.md
+++ b/docs/known-issues/es/erro-sqlerrm-no-tracking-brinox-b2w.md
@@ -18,9 +18,7 @@ internalReference: 643287
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md b/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
index eab9bd5c7..3f22c597c 100644
--- a/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
+++ b/docs/known-issues/es/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
@@ -18,9 +18,7 @@ internalReference: 940998
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un sku falla las reglas de Calidad de Oferta creadas por el Marketplace, va directamente a la "Pestaña de Revisión" o "Pestaña de Rechazados" de Skus Recibidos.
diff --git a/docs/known-issues/es/error-cancelling-customer-credit-invoices.md b/docs/known-issues/es/error-cancelling-customer-credit-invoices.md
index caf84c018..cac0e4c7c 100644
--- a/docs/known-issues/es/error-cancelling-customer-credit-invoices.md
+++ b/docs/known-issues/es/error-cancelling-customer-credit-invoices.md
@@ -18,9 +18,7 @@ internalReference: 926563
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos casos las facturas no se pueden cancelar, al ejecutar la API DELETE obtenemos un error 500 con la siguiente respuesta:
diff --git a/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index d7eefc4e3..1b1e5483c 100644
--- a/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/es/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -18,9 +18,7 @@ internalReference: 663698
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear una promoción, el cliente puede decidir a qué artículos se aplicará la promoción.
diff --git a/docs/known-issues/es/error-closing-customer-credit-account.md b/docs/known-issues/es/error-closing-customer-credit-account.md
index decdcb31a..006250f7a 100644
--- a/docs/known-issues/es/error-closing-customer-credit-account.md
+++ b/docs/known-issues/es/error-closing-customer-credit-account.md
@@ -18,9 +18,7 @@ internalReference: 904432
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando las cuentas principales y secundarias tienen instalada la aplicación de Crédito a Clientes, la creación de una creditAccount se produce en todas ellas. En este escenario hay casos en los que cerrar la creditAccount no funciona, aparece el siguiente error:
diff --git a/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md b/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md
index a0f5efc20..6515427d4 100644
--- a/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md
+++ b/docs/known-issues/es/error-exporting-entity-with-too-many-documents.md
@@ -18,9 +18,7 @@ internalReference: 857894
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La exportación de un gran número de documentos de una entidad provoca un procesamiento excesivo, causando errores en la cola de proceso e impidiendo la exportación de la lista de documentos.
diff --git a/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md b/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md
index c91ffa526..864153402 100644
--- a/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md
+++ b/docs/known-issues/es/error-exporting-large-amount-of-giftcards.md
@@ -18,9 +18,7 @@ internalReference: 550658
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Error de tiempo de espera al intentar exportar una gran cantidad de tarjetas regalo, aunque el periodo de consulta sea corto.
diff --git a/docs/known-issues/es/error-exporting-prices-with-metadata.md b/docs/known-issues/es/error-exporting-prices-with-metadata.md
index 1d585669b..26ff45f52 100644
--- a/docs/known-issues/es/error-exporting-prices-with-metadata.md
+++ b/docs/known-issues/es/error-exporting-prices-with-metadata.md
@@ -18,9 +18,7 @@ internalReference: 860290
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En ocasiones, al intentar exportar los precios con la opción de metadatos activada y sin utilizar filtros, puede producirse un error. Comprobando el mensaje en devTools aparecerá algo similar a "Polly broken circuit on service...".
diff --git a/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md b/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
index 29ea40716..9ea8d5b0f 100644
--- a/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
+++ b/docs/known-issues/es/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
@@ -18,9 +18,7 @@ internalReference: 658185
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En los escenarios de pedidos de suscripción en los que un mismo artículo de compra acaba dividido en diferentes entradas, como la compra de 10 unidades del mismo artículo que se presenta como 7 unidades (A) y 3 unidades (B), el flujo de ejecución del ciclo de suscripción puede acabar eligiendo diferentes métodos de entrega entre el artículo A y el B, aunque sean la misma SKU.
diff --git a/docs/known-issues/es/error-in-checkout-error-message.md b/docs/known-issues/es/error-in-checkout-error-message.md
index 61060dabc..450070bea 100644
--- a/docs/known-issues/es/error-in-checkout-error-message.md
+++ b/docs/known-issues/es/error-in-checkout-error-message.md
@@ -18,9 +18,7 @@ internalReference: 409895
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se produce un error en el flujo de pago de afiliación de MercadoPagov2 en la página de pago, los detalles del mensaje se muestran sin formato para acentos y caracteres especiales.
diff --git a/docs/known-issues/es/error-in-custom-payments-creation.md b/docs/known-issues/es/error-in-custom-payments-creation.md
index a6be1e11c..507d4c416 100644
--- a/docs/known-issues/es/error-in-custom-payments-creation.md
+++ b/docs/known-issues/es/error-in-custom-payments-creation.md
@@ -18,9 +18,7 @@ internalReference: 995110
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los comerciantes pueden experimentar un error al crear un pago personalizado, después de rellenar todo y pulsar guardar aparece el mensaje "Pago personalizado se ha configurado correctamente", pero en realidad la creación falló (no aparece en la interfaz de usuario).
diff --git a/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
index fce2ca31e..5123ede37 100644
--- a/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/es/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -18,9 +18,7 @@ internalReference: 698005
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a problemas de redondeo al recalcular los destinatarios de una transacción con Payout Split, ya sea en la captura o en el reembolso, recibimos la siguiente excepción de la pasarela, ya que la suma del valor del destinatario difiere del valor de la transacción.
diff --git a/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
index 1927d63ec..138558ffa 100644
--- a/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
+++ b/docs/known-issues/es/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -18,9 +18,7 @@ internalReference: 1049494
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar reembolsar una transacción puede producirse un error 500 con el mensaje:
diff --git a/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md b/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
index 858f37279..bd8895f56 100644
--- a/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
+++ b/docs/known-issues/es/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
@@ -18,9 +18,7 @@ internalReference: 740084
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los conectores heredados, ERedeRest y E-Rede V2, inician las cancelaciones enviando una petición al proveedor y esperan un "returnCode": "359" indicando una cancelación exitosa. Cualquier otro código es interpretado por nuestra pasarela como un estado indefinido, provocando que la transacción se quede atascada en un estado de cancelación. Aunque en algunos casos, la solicitud de reembolso/cancelación se realiza correctamente. Esto provocaba repetidos intentos de cancelación, incluso cuando la cancelación ya había sido procesada por el proveedor.
diff --git a/docs/known-issues/es/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md b/docs/known-issues/es/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md
index c749285e2..320c99e71 100644
--- a/docs/known-issues/es/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md
+++ b/docs/known-issues/es/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 587394
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la tienda configura el campo "cantidad máxima de una misma SKU en el carrito" y se trata de un pedido procedente de un marketplace, si la cantidad de artículos del pedido es mayor que la configurada en el admin, está permitiendo que los pedidos se integren, no respetando la cantidad máxima de skus configurados.
diff --git a/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md b/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
index 759bdcd59..30ed110aa 100644
--- a/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
+++ b/docs/known-issues/es/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
@@ -18,9 +18,7 @@ internalReference: 1070299
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando ejecutamos un `change V2` eliminando o añadiendo un ítem a un pedido, creamos un cambio en la lista de ítems del pedido, que puede aumentar o disminuir el número de índices de la lista de ítems en el json. Este cambio, a su vez, puede no ser consumido por todas las apps o bases de datos implicadas en la gestión del pedido, como la app notificadora de facturas;
diff --git a/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md b/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md
index 77c5c2019..cdb773c50 100644
--- a/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md
+++ b/docs/known-issues/es/error-integrating-sku-field-may-not-be-null-magalu.md
@@ -18,9 +18,7 @@ internalReference: 639272
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md b/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
index 43f7f1e7b..ebe833743 100644
--- a/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
+++ b/docs/known-issues/es/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
@@ -18,9 +18,7 @@ internalReference: 1055578
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos usuarios incluso con el rol correcto reciben un error "El usuario xx no tiene acceso a la página solicitada (LeituraDeDadosDoAdministrador)" al acceder a las páginas del catálogo en admin.
diff --git a/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md b/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
index 956df124a..129660050 100644
--- a/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
+++ b/docs/known-issues/es/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
@@ -18,9 +18,7 @@ internalReference: 712956
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
index d3639c5c8..306f955b0 100644
--- a/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
+++ b/docs/known-issues/es/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -18,9 +18,7 @@ internalReference: 925679
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Este caso ocurre con entidades que contienen un gran número de campos y millones de registros en una entidad. El problema surge debido a que el buscador utiliza el campo "Todos", que envía peticiones individuales para cada campo consultable de la entidad y multiplica la carga de peticiones para cada documento.
diff --git a/docs/known-issues/es/error-on-duplicate-payment-method.md b/docs/known-issues/es/error-on-duplicate-payment-method.md
index 89640f2c1..449e62518 100644
--- a/docs/known-issues/es/error-on-duplicate-payment-method.md
+++ b/docs/known-issues/es/error-on-duplicate-payment-method.md
@@ -18,9 +18,7 @@ internalReference: 929428
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al duplicar una forma de pago que no tiene fraccionamiento, el operador recibe en pantalla el siguiente mensaje: "El sistema de pago actual no permite opciones de fraccionamiento". Esto sucede porque al crear el cuerpo de la solicitud de creación de la nueva regla, se insertan por defecto algunos campos, entre ellos installmentOptions, pero este campo no existe para pagos en efectivo como débito y boleto(Brasil).
diff --git a/docs/known-issues/es/error-saving-netshoes-integration-card.md b/docs/known-issues/es/error-saving-netshoes-integration-card.md
index 7454960d1..b85356361 100644
--- a/docs/known-issues/es/error-saving-netshoes-integration-card.md
+++ b/docs/known-issues/es/error-saving-netshoes-integration-card.md
@@ -18,9 +18,7 @@ internalReference: 591921
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
index 2f06bb6d9..be7f1b3e2 100644
--- a/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
+++ b/docs/known-issues/es/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 932126
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al añadir imágenes a través del Editor de Sitios, el mensaje "`Algo salió mal. Por favor inténtelo de nuevo.`" puede ocurrir ocasionalmente.
diff --git a/docs/known-issues/es/error-sww-on-product-pdp.md b/docs/known-issues/es/error-sww-on-product-pdp.md
index b88b8e779..0eabc4444 100644
--- a/docs/known-issues/es/error-sww-on-product-pdp.md
+++ b/docs/known-issues/es/error-sww-on-product-pdp.md
@@ -18,9 +18,7 @@ internalReference: 738108
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunas ocasiones, al abrir la PDP del producto a través de la página de administración (o del dominio final) aparece en pantalla un error Algo ha ido mal.
diff --git a/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md b/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
index 717fa3c5e..8439e0854 100644
--- a/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
+++ b/docs/known-issues/es/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
@@ -18,9 +18,7 @@ internalReference: 308214
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En nuestro conector heredado de PayPal, nos hemos enfrentado a un problema relacionado con la sobrescritura del campo `TOKEN` para `PAYMENTINFO_0_TRANSACTIONID`. El problema surge cuando el proveedor envía un estado de pago como pendiente. En consecuencia, nuestra implementación del conector sobrescribe el TOKEN, lo que provoca un error que PayPal desencadena durante las solicitudes posteriores. Como resultado, la transacción se bloquea con un mensaje de "código inválido".
diff --git a/docs/known-issues/es/error-viewing-shippingestimatedate-in-new-ui.md b/docs/known-issues/es/error-viewing-shippingestimatedate-in-new-ui.md
index ac0db9810..ec2ed459d 100644
--- a/docs/known-issues/es/error-viewing-shippingestimatedate-in-new-ui.md
+++ b/docs/known-issues/es/error-viewing-shippingestimatedate-in-new-ui.md
@@ -18,9 +18,7 @@ internalReference: 661040
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md b/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md
index 97d2ff5ba..d7bad9785 100644
--- a/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md
+++ b/docs/known-issues/es/error-when-changing-an-index-if-the-fields-are-identical.md
@@ -18,9 +18,7 @@ internalReference: 854634
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La actualización de un índice de esquema puede dar lugar a un error 500 Internal Server cuando no hay cambios que realizar, esto significa que los valores de los campos son idénticos a los actuales.
diff --git a/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md b/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md
index 3dac76480..d78513141 100644
--- a/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md
+++ b/docs/known-issues/es/error-when-changing-delivery-type-when-seller-has-recursion.md
@@ -18,9 +18,7 @@ internalReference: 597915
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el escenario en el que el vendedor tiene recursividad, al llegar a la etapa de pago y cambiar el tipo de entrega de entrega a recogida, el usuario recibe el error "No se puede comunicar con el vendedor ...." pero en realidad el error es "La dirección no se puede utilizar para el canal de entrega dado". Esto se debe a la recursión en la que la API no sabe cómo tratar este tipo de escenario y la UI no selecciona un deliveryChannel.
diff --git a/docs/known-issues/es/error-when-including-many-filters-in-the-order-list.md b/docs/known-issues/es/error-when-including-many-filters-in-the-order-list.md
index be3d79b24..f1ccef69b 100644
--- a/docs/known-issues/es/error-when-including-many-filters-in-the-order-list.md
+++ b/docs/known-issues/es/error-when-including-many-filters-in-the-order-list.md
@@ -18,9 +18,7 @@ internalReference: 347932
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunas tiendas, la lista de Vendedores, promociones u otros filtros puede ser bastante alta, y en algunos momentos pueden querer hacer una selección bastante amplia.
diff --git a/docs/known-issues/es/error-when-install-customer-credit-app.md b/docs/known-issues/es/error-when-install-customer-credit-app.md
index 506f1562a..3b1a01ed9 100644
--- a/docs/known-issues/es/error-when-install-customer-credit-app.md
+++ b/docs/known-issues/es/error-when-install-customer-credit-app.md
@@ -18,9 +18,7 @@ internalReference: 336533
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al descargar la aplicación de Crédito Cliente e insertar el nombre de la cuenta en el campo de la derecha, se devuelve el mensaje: _no se ha podido encontrar la tienda indicada_. este es un problema intermitente un No se ha podido identificar el escenario específico que hace que aparezca este error.
diff --git a/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md b/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md
index e921aa8b2..88d8e8b47 100644
--- a/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md
+++ b/docs/known-issues/es/error-when-publishing-dynamic-storage-data-entity.md
@@ -18,9 +18,7 @@ internalReference: 666357
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la tienda crea o actualiza una Entidad de Datos y luego intenta publicarla, puede ocurrir el siguiente error:
diff --git a/docs/known-issues/es/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md b/docs/known-issues/es/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md
index 030018cca..e4d780b30 100644
--- a/docs/known-issues/es/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md
+++ b/docs/known-issues/es/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md
@@ -18,9 +18,7 @@ internalReference: 334407
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la tienda tiene más de 10.000 documentos, es decir, más de 333 páginas, al intentar acceder a las últimas páginas en CRM, aparece un mensaje de error:
diff --git a/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
index f34973483..b009bddef 100644
--- a/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/es/error-when-running-vtex-link-for-the-first-time.md
@@ -36,7 +36,5 @@ El mensaje de autorización de error puede cambiar de `node` a `react` de acuerd
 1. Rellene el [formulario](https://suportevtex1.typeform.com/to/SxXknn)
 2. Acceda al módulo de Gestión de la cuenta y asegúrese de que su perfil tiene los permisos de "VTEX IO Admin"
 
-<div class="alert alert-info">
-Rellenar el formulario no garantiza el acceso a la Whitelist de Node + GraphQL y Extensibilty.
-</div>
+>ℹ️ Rellenar el formulario no garantiza el acceso a la Whitelist de Node + GraphQL y Extensibilty.
 
diff --git a/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md b/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md
index 57e336f9a..8143622ec 100644
--- a/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md
+++ b/docs/known-issues/es/error-when-settling-transaction-with-2-cards-mercadopagov1.md
@@ -18,9 +18,7 @@ internalReference: 395943
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 ## **Resumen**
 
diff --git a/docs/known-issues/es/error-when-trying-to-open-my-cards.md b/docs/known-issues/es/error-when-trying-to-open-my-cards.md
index 57cb60354..4d91e8799 100644
--- a/docs/known-issues/es/error-when-trying-to-open-my-cards.md
+++ b/docs/known-issues/es/error-when-trying-to-open-my-cards.md
@@ -18,9 +18,7 @@ internalReference: 370706
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos usuarios específicos están recibiendo el siguiente mensaje de error al iniciar sesión en Mis tarjetas:
diff --git a/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md b/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md
index 81a53eeb0..9f85d43e9 100644
--- a/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md
+++ b/docs/known-issues/es/error-when-trying-to-publish-or-link-an-app.md
@@ -18,9 +18,7 @@ internalReference: 1056882
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Nuestro equipo investigó que esto está normalmente asociado con el desarrollo de una aplicación de gran tamaño. Esto ocurre porque el builder hub explota su memoria debido a la gran cantidad de archivos en la app. Los retrasos en la vinculación de la aplicación también pueden estar asociados con este problema.
diff --git a/docs/known-issues/es/eternal-loading-in-checkout-ui-v5.md b/docs/known-issues/es/eternal-loading-in-checkout-ui-v5.md
index cd450bdca..ccb66eb13 100644
--- a/docs/known-issues/es/eternal-loading-in-checkout-ui-v5.md
+++ b/docs/known-issues/es/eternal-loading-in-checkout-ui-v5.md
@@ -18,9 +18,7 @@ internalReference: 332740
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En Checkout v5, en un escenario específico, la página se atasca en una carga infinita, y en la consola, podemos ver el error: "Uncaught SyntaxError: Unexpected token u in JSON at position 0 at JSON.parse (<anonymous>)".
diff --git a/docs/known-issues/es/event-inconsistency.md b/docs/known-issues/es/event-inconsistency.md
index 1424a110e..a01e49b67 100644
--- a/docs/known-issues/es/event-inconsistency.md
+++ b/docs/known-issues/es/event-inconsistency.md
@@ -18,9 +18,7 @@ internalReference: 267299
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md b/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
index b940e9319..98fcd30a5 100644
--- a/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
+++ b/docs/known-issues/es/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
@@ -18,9 +18,7 @@ internalReference: 735854
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La nueva UI no sugiere el artículo correcto a devolver.
diff --git a/docs/known-issues/es/exclude-products-from-collection-not-working.md b/docs/known-issues/es/exclude-products-from-collection-not-working.md
index 2a93b3f06..071a8bb29 100644
--- a/docs/known-issues/es/exclude-products-from-collection-not-working.md
+++ b/docs/known-issues/es/exclude-products-from-collection-not-working.md
@@ -18,9 +18,7 @@ internalReference: 923016
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La cuenta puede crear colecciones utilizando la versión anterior y añadir colecciones y marcas completas.
diff --git a/docs/known-issues/es/expiration-date-of-special-condition-is-not-deleted.md b/docs/known-issues/es/expiration-date-of-special-condition-is-not-deleted.md
index a48fbfae0..7b4e7b287 100644
--- a/docs/known-issues/es/expiration-date-of-special-condition-is-not-deleted.md
+++ b/docs/known-issues/es/expiration-date-of-special-condition-is-not-deleted.md
@@ -18,9 +18,7 @@ internalReference: 547046
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el cliente configura una Condición Especial para un periodo de tiempo y quiere eliminar esta configuración, sólo se elimina el periodo, la recurrencia de esta configuración no se elimina. Esto significa que aunque se elimine la configuración de programación de la Condición de Pago, el campo `dateIntervals` sigue indexando y deja de indexar la Regla de Pago.
diff --git a/docs/known-issues/es/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md b/docs/known-issues/es/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md
index 329827646..25d85acf6 100644
--- a/docs/known-issues/es/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md
+++ b/docs/known-issues/es/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md
@@ -18,9 +18,7 @@ internalReference: 325695
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md b/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md
index 5b29fc538..54096ccdb 100644
--- a/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md
+++ b/docs/known-issues/es/expired-temporary-redirects-not-pointing-back-to-old-route.md
@@ -18,9 +18,7 @@ internalReference: 898062
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md b/docs/known-issues/es/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md
index c16b4c45c..81c7036ef 100644
--- a/docs/known-issues/es/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md
+++ b/docs/known-issues/es/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 830490
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se configura más de un idioma en la Búsqueda Inteligente, la Búsqueda Explicada no devolverá ningún resultado si coincide con una configuración regional de admin que también está en la Búsqueda Inteligente, pero no es la coincidencia exacta. Por ejemplo:
diff --git a/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md b/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
index 53eaba11f..9c2c168a3 100644
--- a/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
+++ b/docs/known-issues/es/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
@@ -18,9 +18,7 @@ internalReference: 904482
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La página de administración de búsqueda explicada tiene problemas con las reglas de comercialización y las áreas de campo de búsqueda cuando una búsqueda o un producto tiene demasiada información allí, textos superpuestos entre diferentes secciones/productos.
diff --git a/docs/known-issues/es/export-from-order-list-in-column-creation-date-is-at-utc-0.md b/docs/known-issues/es/export-from-order-list-in-column-creation-date-is-at-utc-0.md
index 8208c4f4d..f4c49d2fc 100644
--- a/docs/known-issues/es/export-from-order-list-in-column-creation-date-is-at-utc-0.md
+++ b/docs/known-issues/es/export-from-order-list-in-column-creation-date-is-at-utc-0.md
@@ -18,9 +18,7 @@ internalReference: 619890
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md b/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
index 1e647f811..f4206d614 100644
--- a/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
+++ b/docs/known-issues/es/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
@@ -18,9 +18,7 @@ internalReference: 284386
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Exportar muchos productos/SKUs lleva mucho tiempo y a veces no se puede completar la solicitud. Este problema también afecta a otras exportaciones de catálogos.
diff --git a/docs/known-issues/es/export-redirects-not-working-as-intended.md b/docs/known-issues/es/export-redirects-not-working-as-intended.md
index 2cdc3564b..075a0dadb 100644
--- a/docs/known-issues/es/export-redirects-not-working-as-intended.md
+++ b/docs/known-issues/es/export-redirects-not-working-as-intended.md
@@ -18,9 +18,7 @@ internalReference: 537962
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md b/docs/known-issues/es/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md
index de5d0cfc9..acf5f18e7 100644
--- a/docs/known-issues/es/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md
+++ b/docs/known-issues/es/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md
@@ -18,9 +18,7 @@ internalReference: 566393
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el idioma del sistema operativo es el español (Perú), la exportación de los valores del anexo SKU genera una hoja de cálculo con las columnas "Valor" y "Custo" incorrectamente rellenadas
diff --git a/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md b/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md
index 40825268c..8b9e3f70d 100644
--- a/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md
+++ b/docs/known-issues/es/export-the-csv-in-the-sales-performance-module.md
@@ -18,9 +18,7 @@ internalReference: 823878
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Estamos teniendo problemas al intentar exportar el CSV en el módulo de rendimiento de ventas.
diff --git a/docs/known-issues/es/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md b/docs/known-issues/es/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md
index 3ca4cad2f..96bbbdb4b 100644
--- a/docs/known-issues/es/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md
+++ b/docs/known-issues/es/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md
@@ -18,9 +18,7 @@ internalReference: 594075
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al exportar la tabla de precios filtrada por Marca para obtener un resultado más específico, la hoja de cálculo llega incompleta al cliente.
diff --git a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index f29241616..e7c518ade 100644
--- a/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/es/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -18,9 +18,7 @@ internalReference: 919199
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El informe de imágenes SKU, /admin/Site/ProdutoImagemExportacao.aspx, para nombres de cuenta que empiezan por "h", "t" o "p", como "testaccount", mostrará un carácter que falta en la hoja de exportación para la fila imageURL.
diff --git a/docs/known-issues/es/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md b/docs/known-issues/es/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md
index 3375100d6..311b9ae17 100644
--- a/docs/known-issues/es/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md
+++ b/docs/known-issues/es/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md
@@ -18,9 +18,7 @@ internalReference: 792511
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar exportar la lista de skus que se encuentran en la pestaña de procesamiento del módulo de Skus Recibidos, aparece un error en pantalla:
diff --git a/docs/known-issues/es/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md b/docs/known-issues/es/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md
index 90470a81e..f4e16348d 100644
--- a/docs/known-issues/es/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md
+++ b/docs/known-issues/es/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md
@@ -18,9 +18,7 @@ internalReference: 525987
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El valor máximo para la venta adicional sólo se calcula para los pagarés por defecto, cuando se añaden otros adicionales, nuestra pasarela no considera el campo de rango de margen cambiante en el cálculo
diff --git a/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md b/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md
index 4edc07ab1..7b3f84190 100644
--- a/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md
+++ b/docs/known-issues/es/ey-send-kit-is-not-recording-a-change-in-the-card.md
@@ -18,9 +18,7 @@ internalReference: 442215
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/facebook-review-skus-load-route-behavior-on-facebook.md b/docs/known-issues/es/facebook-review-skus-load-route-behavior-on-facebook.md
index 6f0cefc6b..e2ce83993 100644
--- a/docs/known-issues/es/facebook-review-skus-load-route-behavior-on-facebook.md
+++ b/docs/known-issues/es/facebook-review-skus-load-route-behavior-on-facebook.md
@@ -18,9 +18,7 @@ internalReference: 660874
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Revisar el comportamiento de la ruta de carga de skus en facebook
diff --git a/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md b/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
index a8a9e77ac..47b6212b2 100644
--- a/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
+++ b/docs/known-issues/es/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
@@ -18,9 +18,7 @@ internalReference: 924411
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hoy Facebook mira sellingPrice y listPrice para actualizar el precio en el catálogo de Facebook.
diff --git a/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md b/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
index c35d18ea3..51c305869 100644
--- a/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
+++ b/docs/known-issues/es/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
@@ -18,9 +18,7 @@ internalReference: 1057254
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La propiedad "facets" almacenada en el Segmento/Sesión para un contexto de navegación funciona para limitar los resultados de búsqueda a filtros predefinidos. Por ejemplo, es utilizada por "Organizaciones B2B" para restringir lo que un usuario puede ver en la tienda.
diff --git a/docs/known-issues/es/failed-payments-created-by-checkout-ui-transaction-without-payments.md b/docs/known-issues/es/failed-payments-created-by-checkout-ui-transaction-without-payments.md
index e685aaf59..409e85ad2 100644
--- a/docs/known-issues/es/failed-payments-created-by-checkout-ui-transaction-without-payments.md
+++ b/docs/known-issues/es/failed-payments-created-by-checkout-ui-transaction-without-payments.md
@@ -18,9 +18,7 @@ internalReference: 339243
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Casos de pedidos incompletos donde sus transacciones no tienen pagos.
diff --git a/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md b/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md
index c50e48c46..b08ac0692 100644
--- a/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md
+++ b/docs/known-issues/es/failure-on-the-cancellation-ppp-when-cancellationidnull.md
@@ -18,9 +18,7 @@ internalReference: 333897
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
index 128c01daa..d88aa54e8 100644
--- a/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
+++ b/docs/known-issues/es/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -18,9 +18,7 @@ internalReference: 467419
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Durante la etapa de pago, en el paso de rellenar los datos de envío, pulsando sobre la opción "Entregar en otra dirección", si no se añade ninguna dirección y el comprador vuelve a la lista de direcciones (utilizando el botón "volver a la libreta de direcciones") el botón "Ir al pago" desaparece.
diff --git a/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md b/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md
index cc61c75cd..398d42a3c 100644
--- a/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md
+++ b/docs/known-issues/es/faststore-cart-merges-assembly-line-items.md
@@ -18,9 +18,7 @@ internalReference: 1050068
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si la misma opción de montaje se añade a diferentes productos FastStore los fusionará en una única partida.
diff --git a/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md b/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
index 7a4b6ecb1..c52aa0a56 100644
--- a/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
+++ b/docs/known-issues/es/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
@@ -18,9 +18,7 @@ internalReference: 1029837
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md b/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md
index 47a2d383b..57b0e048c 100644
--- a/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md
+++ b/docs/known-issues/es/faststore-search-api-considering-fuzzy-as-auto-as-default.md
@@ -18,9 +18,7 @@ internalReference: 889321
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el paquete @fatstore/api, para el Intelligent Search resolver, estamos considerando fuzzy como auto por defecto cuando deberia ser 0, esto esta causando que el comportamiento de fuzzy se aplique causando un "fake missmatch" en los resultados de busqueda cuando realmente tenemos una coincidencia exacta con el termino buscado, pero, mostramos mas resultados a pesar de que
diff --git a/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md b/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md
index eafd9c54c..8c6aa8f21 100644
--- a/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md
+++ b/docs/known-issues/es/faststore-v1-dont-return-seo-information-on-graphql-query.md
@@ -18,9 +18,7 @@ internalReference: 929029
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al acceder al playground de Graphql para ejecutar consultas en Faststore V1 tenemos una consulta de producto. La documentación indica que el campo SEO de esa consulta debería devolver la información SEO, pero esto no está ocurriendo.
diff --git a/docs/known-issues/es/faststores-not-working-correctly-in-firefox-private-mode.md b/docs/known-issues/es/faststores-not-working-correctly-in-firefox-private-mode.md
index 58717ca57..a35c4817b 100644
--- a/docs/known-issues/es/faststores-not-working-correctly-in-firefox-private-mode.md
+++ b/docs/known-issues/es/faststores-not-working-correctly-in-firefox-private-mode.md
@@ -18,9 +18,7 @@ internalReference: 828685
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md b/docs/known-issues/es/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md
index e359d673b..f168bb1db 100644
--- a/docs/known-issues/es/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md
+++ b/docs/known-issues/es/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md
@@ -18,9 +18,7 @@ internalReference: 832400
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al configurar el filtro Feed/Hook, se define qué actualizaciones de pedidos deben mostrarse en el feed. Se pueden utilizar dos tipos de filtros en el feed: FromWorkflow y FromOrders.
diff --git a/docs/known-issues/es/fetchmore-bringing-repeated-values-between-the-to-and-from.md b/docs/known-issues/es/fetchmore-bringing-repeated-values-between-the-to-and-from.md
index cc11cecc2..27daa1de6 100644
--- a/docs/known-issues/es/fetchmore-bringing-repeated-values-between-the-to-and-from.md
+++ b/docs/known-issues/es/fetchmore-bringing-repeated-values-between-the-to-and-from.md
@@ -18,9 +18,7 @@ internalReference: 835396
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función fetchMore está trayendo entre la primera y la segunda página algunos valores duplicados y esto hace que la página muestre repetidamente algunos de los productos.
diff --git a/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md b/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
index eadd9a388..3086fb2e0 100644
--- a/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
+++ b/docs/known-issues/es/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
@@ -18,9 +18,7 @@ internalReference: 560014
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si se accede a una tienda y se hace clic en mostrar más, se navega por algunas páginas, y luego se hace clic de nuevo en el enlace "categoría" para reiniciar la navegación, el fetch more traerá el estado(página) de la última navegación, no volviendo al principio.
diff --git a/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md b/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
index 5c962c5f4..0c327ac58 100644
--- a/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
+++ b/docs/known-issues/es/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
@@ -18,9 +18,7 @@ internalReference: 695044
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index 1c4e7f40e..baa99f65f 100644
--- a/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/es/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -18,9 +18,7 @@ internalReference: 689886
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de guardar el campo "Cambios y devoluciones" en la UI la información se actualiza por primera vez pero si intentamos salir del área de gestión o refrescar la página la información se pierde.
diff --git a/docs/known-issues/es/field-reference-always-set-as-null.md b/docs/known-issues/es/field-reference-always-set-as-null.md
index 0fff7a2fb..0ec159649 100644
--- a/docs/known-issues/es/field-reference-always-set-as-null.md
+++ b/docs/known-issues/es/field-reference-always-set-as-null.md
@@ -18,9 +18,7 @@ internalReference: 797989
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El campo `reference` de la dirección del punto de recogida siempre se establece como nulo aunque esté registrado en la API del punto de recogida.
diff --git a/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md b/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
index f9b3ae078..2dd15cccb 100644
--- a/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
+++ b/docs/known-issues/es/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
@@ -18,9 +18,7 @@ internalReference: 748404
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al actualizar cualquier información en la configuración de la gestión de pedidos (en el administrador), los campos `paymentSystemToCheckFirstInstallment` y `defaultPaymentSystemToApplyOnUserOrderForm` se establecen como `null` en la configuración de orderForm
diff --git a/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md b/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
index 71aa9402a..f524ece8e 100644
--- a/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
+++ b/docs/known-issues/es/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
@@ -18,9 +18,7 @@ internalReference: 418253
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La carga de archivos con dos o más archivos existentes no actualiza todos los archivos, sólo el primero.
diff --git a/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md b/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
index f8d1efc3b..34004336a 100644
--- a/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
+++ b/docs/known-issues/es/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
@@ -18,9 +18,7 @@ internalReference: 639219
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el tablero de rendimiento de ventas el filtro por un término no está aceptando letras mayúsculas en el SkuName.
diff --git a/docs/known-issues/es/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md b/docs/known-issues/es/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md
index 8328e96b0..b10c4f436 100644
--- a/docs/known-issues/es/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md
+++ b/docs/known-issues/es/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 523984
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el orden de la lista un filtro por promoción, cuando hay un espacio extra en blanco en el nombre de la promoción en el json no está coincidiendo.
diff --git a/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
index f59d3f974..ecb6621cf 100644
--- a/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
+++ b/docs/known-issues/es/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -18,9 +18,7 @@ internalReference: 899508
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se inicia una búsqueda desde el filtro "productClusterIds", al aplicar cualquier filtro adicional se convertirá en "productClusterNames", perdiendo la característica de presentar los ítems con la ordenación definida manualmente en la colección de productos.
diff --git a/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md b/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
index de51c46f2..03d430f51 100644
--- a/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
+++ b/docs/known-issues/es/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
@@ -18,9 +18,7 @@ internalReference: 756461
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Filtrar productos por "Tienda" en el Catalogo Admin puede mostrar una cantidad incorrecta de resultados
diff --git a/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md b/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md
index db4449183..48d8c988a 100644
--- a/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md
+++ b/docs/known-issues/es/filters-by-sku-specifications-not-considering-regionalized-availability.md
@@ -18,9 +18,7 @@ internalReference: 1045111
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al filtrar la búsqueda por una especificación de SKU también se aplicará un filtro por disponibilidad de SKU, eliminando los productos en los que la variación seleccionada esté agotada, pero no se aplica a las tiendas regionalizadas.
diff --git a/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md b/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
index d7631e653..74b2418c8 100644
--- a/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
+++ b/docs/known-issues/es/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
@@ -18,9 +18,7 @@ internalReference: 416638
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas especificaciones tienen un uso interno o escenarios que necesitan ser ocultados, pero la tienda necesita esa especificación para propósitos de la búsqueda, como usarlo para Reglas de Mercadeo.
diff --git a/docs/known-issues/es/filters-hide-scenarios-internals-and-usability.md b/docs/known-issues/es/filters-hide-scenarios-internals-and-usability.md
index 682b1835c..0d6464ab0 100644
--- a/docs/known-issues/es/filters-hide-scenarios-internals-and-usability.md
+++ b/docs/known-issues/es/filters-hide-scenarios-internals-and-usability.md
@@ -18,9 +18,7 @@ internalReference: 416638
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas especificaciones tienen un uso interno y también ocultan escenarios, pero la tienda necesita esa especificación para un propósito en la búsqueda, como usarlo para reglas de comercio o propósitos de visualización.
diff --git a/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md b/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
index e2a7a5cf0..ae2e41841 100644
--- a/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
+++ b/docs/known-issues/es/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 948071
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces puedes hacer cambios en el Editor de Sitios y esos cambios se reflejan en el entorno myvtex, pero cuando intentas actualizar el dominio final, esos cambios no se reflejan. Esto ocurre normalmente cuando el componente que intentas cambiar tiene más de una versión. El front sigue utilizando la versión inactiva del componente mientras que el myvtex está utilizando la versión activa. La única forma de solucionar esto es borrando la versión inactiva del componente.
diff --git a/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md b/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
index cf0b7e7ea..5ca93c761 100644
--- a/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
+++ b/docs/known-issues/es/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 366975
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario tiene más de una dirección en su perfil y la primera dirección de la lista de direcciones está incompleta, independientemente de que las demás sean válidas, la caja no rellena automáticamente sus datos de perfil/envío después de añadir su correo electrónico.
diff --git a/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md b/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
index a3431633d..f99365339 100644
--- a/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
+++ b/docs/known-issues/es/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
@@ -18,9 +18,7 @@ internalReference: 920703
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el documento corporativo de una organización comienza con letras, el primer dígito se elimina después de acceder a la comprobación.
diff --git a/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md b/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
index 42b3ef5a9..b62a78b9f 100644
--- a/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
+++ b/docs/known-issues/es/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
@@ -18,9 +18,7 @@ internalReference: 570971
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando busques en una tienda por primera vez, tu primera búsqueda no aparecerá en "últimas búsquedas", pero todas las demás se tendrán en cuenta.
diff --git a/docs/known-issues/es/first-subscription-cycle-is-skipped.md b/docs/known-issues/es/first-subscription-cycle-is-skipped.md
index 314895ba3..39e0056ae 100644
--- a/docs/known-issues/es/first-subscription-cycle-is-skipped.md
+++ b/docs/known-issues/es/first-subscription-cycle-is-skipped.md
@@ -18,9 +18,7 @@ internalReference: 528556
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El sistema de suscripción utiliza información como la frecuencia de compra y la fecha del ciclo de suscripción para generar un pedido de suscripción. Sin embargo, en función de la zona horaria del consumidor y de la hora a la que se realiza el pedido, se omite el primer ciclo y sólo se genera el segundo mes.
diff --git a/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md b/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
index 8441252d4..bc16c8452 100644
--- a/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
+++ b/docs/known-issues/es/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
@@ -18,9 +18,7 @@ internalReference: 705869
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md b/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
index 04b0ddfe1..2c051f800 100644
--- a/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
+++ b/docs/known-issues/es/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 672567
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index 53655f69b..3a49b5c55 100644
--- a/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/es/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -18,9 +18,7 @@ internalReference: 532377
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El mercado externo (socio) al tratar de integrar los pedidos FOB están recibiendo el error:
diff --git a/docs/known-issues/es/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md b/docs/known-issues/es/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md
index 2c50fda87..165ec8187 100644
--- a/docs/known-issues/es/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md
+++ b/docs/known-issues/es/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md
@@ -18,9 +18,7 @@ internalReference: 367284
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 ## **Resumen**
 
diff --git a/docs/known-issues/es/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md b/docs/known-issues/es/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md
index 1fa0e0a6d..6e98d8279 100644
--- a/docs/known-issues/es/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md
+++ b/docs/known-issues/es/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md
@@ -18,9 +18,7 @@ internalReference: 292781
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para el pago en efectivo (1 plazo) se está ignorando para la regla de condición de pago, aunque la condición de pago no tiene configuración para 1 plazo.
diff --git a/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md b/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
index a12e8cedc..14598b52e 100644
--- a/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
+++ b/docs/known-issues/es/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
@@ -18,9 +18,7 @@ internalReference: 732302
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md b/docs/known-issues/es/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md
index 434bcee44..7e08b56f6 100644
--- a/docs/known-issues/es/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md
+++ b/docs/known-issues/es/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md
@@ -18,9 +18,7 @@ internalReference: 621230
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las actualizaciones del valor del flete están tardando más de 1 día en reflejarse en la simulación de envío cuando la actualización se solicitó mediante el método POST de la API. Este problema es intermitente, normalmente la actualización tarda sólo unos minutos.
diff --git a/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md b/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
index 2630ea38b..3bdf03aa4 100644
--- a/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
+++ b/docs/known-issues/es/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
@@ -18,9 +18,7 @@ internalReference: 922541
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el área de Gestión de Vendedores el marketplace puede agrupar a sus vendedores como desee y gestionarlos en la pestaña de gestión de grupos.
diff --git a/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md b/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
index 128a2fc97..64c18c0f4 100644
--- a/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
+++ b/docs/known-issues/es/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
@@ -18,9 +18,7 @@ internalReference: 860655
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El evento de compra GA4 no tiene el árbol de categorías en item_category en dataLayer, por lo que la única categoría disponible es la categoría de último nivel del producto.
diff --git a/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md b/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
index 90e229f12..0a53ece77 100644
--- a/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
+++ b/docs/known-issues/es/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
@@ -18,9 +18,7 @@ internalReference: 582065
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 633370649..2cc1a10be 100644
--- a/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/es/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -18,9 +18,7 @@ internalReference: 367187
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/get-category-tree-api-with-internal-cache.md b/docs/known-issues/es/get-category-tree-api-with-internal-cache.md
index 502706f45..f8705d92d 100644
--- a/docs/known-issues/es/get-category-tree-api-with-internal-cache.md
+++ b/docs/known-issues/es/get-category-tree-api-with-internal-cache.md
@@ -18,9 +18,7 @@ internalReference: 480892
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API GET Árbol de Categorías tiene una caché interna. Cuando se realiza una petición utilizando el dominio interno de VTEX y luego, se realiza la misma petición utilizando el dominio del cliente, la primera petición se almacenará en la caché y en la respuesta de la segunda petición, realizada utilizando el dominio del cliente, devolveremos las URL de las categorías con el dominio interno de VTEX.
diff --git a/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md b/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
index f318c6064..7e4e1efce 100644
--- a/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
+++ b/docs/known-issues/es/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
@@ -18,9 +18,7 @@ internalReference: 326662
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md b/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md
index 60ae513c0..eb5dd5066 100644
--- a/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md
+++ b/docs/known-issues/es/get-matched-offers-list-api-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 553456
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API Get Matched Offers List , documentada aquí: https://developers.vtex.com/vtex-rest-api/reference/getofferslist, no funciona correctamente cuando el usuario intenta insertar los parámetros de consulta sugeridos.
diff --git a/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
index 552b2c0aa..ba8c6d791 100644
--- a/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/es/get-product-by-refid-returning-null-when-not-found.md
@@ -18,9 +18,7 @@ internalReference: 826702
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La ruta get product by refid (/catalog_system/pvt/products/productgetbyrefid) devuelve un null en lugar de una simple respuesta 404 cuando no se encuentra un id válido en el catálogo de una tienda determinada.
diff --git a/docs/known-issues/es/get-seller-list-responding-with-empty-urllogo.md b/docs/known-issues/es/get-seller-list-responding-with-empty-urllogo.md
index 7bb60b19f..a09d6141e 100644
--- a/docs/known-issues/es/get-seller-list-responding-with-empty-urllogo.md
+++ b/docs/known-issues/es/get-seller-list-responding-with-empty-urllogo.md
@@ -18,9 +18,7 @@ internalReference: 387508
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la ruta `/api/catalog_system/pvt/seller/list` responde con una propiedad UrlLogo vacía para todos los vendedores, independientemente de que tengan un archivo de logotipo válido o no.
diff --git a/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md b/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md
index 95a695792..a93d1b9ac 100644
--- a/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md
+++ b/docs/known-issues/es/get-sku-by-ean-api-returns-only-active-skus.md
@@ -18,9 +18,7 @@ internalReference: 699007
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md b/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
index 7949912b3..572f4ce21 100644
--- a/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
+++ b/docs/known-issues/es/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
@@ -18,9 +18,7 @@ internalReference: 324416
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función `getCurrentProductWithVariations` de VTEX.js trae los datos del SKU del componente en lugar del SKU del KIT.
diff --git a/docs/known-issues/es/gift-card-creation-error-via-admin.md b/docs/known-issues/es/gift-card-creation-error-via-admin.md
index e4ac565e9..98bb0f429 100644
--- a/docs/known-issues/es/gift-card-creation-error-via-admin.md
+++ b/docs/known-issues/es/gift-card-creation-error-via-admin.md
@@ -18,9 +18,7 @@ internalReference: 986327
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas cuentas no podrán crear una Tarjeta Regalo por primera vez vía admin, el mensaje de abajo aparecerá en la pantalla:
diff --git a/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md b/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
index cd6ab6fa5..8bc5a0279 100644
--- a/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
+++ b/docs/known-issues/es/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
@@ -18,9 +18,7 @@ internalReference: 378436
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los clientes están recibiendo un error al intentar pagar con tarjetas regalo cuando la fecha de la compra coincide con la fecha de caducidad.
diff --git a/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md b/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
index 11f48ed47..dced0757a 100644
--- a/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
+++ b/docs/known-issues/es/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
@@ -18,9 +18,7 @@ internalReference: 855864
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La documentación de nuestro protocolo para proveedores de tarjetas regalo especifica que la API de creación de transacciones debe incluir un ID válido en la respuesta. Sin embargo, la implementación actual del protocolo permite a los proveedores responder a esta solicitud con un ID vacío o no válido. Como resultado, al intentar liquidar el pago, la transacción se bloquea porque falta el ID requerido. Esto provoca que se lance un error y que la transacción se quede atascada en el proceso.
diff --git a/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index 441dd07db..e198e89a0 100644
--- a/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/es/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -18,9 +18,7 @@ internalReference: 669575
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Nuestra API del hub de tarjetas de regalo está añadiendo una barra invertida extra a la solicitud cuando se llama a los proveedores. Esto se debe a la forma en que convertimos la serviceUrl y la concatenamos con la URL proporcionada por el conector.
diff --git a/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
index cfb609c89..b66ad51a5 100644
--- a/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
+++ b/docs/known-issues/es/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -18,9 +18,7 @@ internalReference: 428725
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se ejecuta el método GET para una tarjeta regalo existente, no devuelve el campo "caption" ni el campo "relationName" aunque estos parámetros tengan valor.
diff --git a/docs/known-issues/es/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md b/docs/known-issues/es/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md
index 864e5a9a8..ba2c1ed7c 100644
--- a/docs/known-issues/es/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md
+++ b/docs/known-issues/es/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md
@@ -18,19 +18,13 @@ internalReference: 325007
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md b/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md
index 0a602b918..1114d93c2 100644
--- a/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md
+++ b/docs/known-issues/es/gift-items-throws-a-generic-exception-if-it-has-no-price.md
@@ -18,9 +18,7 @@ internalReference: 510490
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La selección de un artículo de regalo en el carrito lanzará una excepción genérica si no tiene precio, especialmente si la tienda utiliza un servicio de impuestos externo. El cliente no puede seguir seleccionándolo.
diff --git a/docs/known-issues/es/gift-list-error-incomplete-address.md b/docs/known-issues/es/gift-list-error-incomplete-address.md
index 469023996..be80ce101 100644
--- a/docs/known-issues/es/gift-list-error-incomplete-address.md
+++ b/docs/known-issues/es/gift-list-error-incomplete-address.md
@@ -18,9 +18,7 @@ internalReference: 313576
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas listas de regalos se muestran en rojo con el mensaje "dirección incompleta". Al hacer clic en la URL de la lista de regalos la redirigen al siguiente mensaje de error: `.myvtex.com/giftlist?GiftListAddressFail_ID`
diff --git a/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md b/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
index 1364b3598..38da59f5f 100644
--- a/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
+++ b/docs/known-issues/es/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
@@ -18,9 +18,7 @@ internalReference: 729980
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md b/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
index a55cdd575..dcff781f4 100644
--- a/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
+++ b/docs/known-issues/es/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
@@ -18,9 +18,7 @@ internalReference: 690794
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/giftcard-not-getting-refund-after-transaction-cancellation.md b/docs/known-issues/es/giftcard-not-getting-refund-after-transaction-cancellation.md
index 0216fcbb4..e57584fee 100644
--- a/docs/known-issues/es/giftcard-not-getting-refund-after-transaction-cancellation.md
+++ b/docs/known-issues/es/giftcard-not-getting-refund-after-transaction-cancellation.md
@@ -18,9 +18,7 @@ internalReference: 491195
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el pago es una tarjeta regalo y se produce un error durante el proceso de realización del pedido y éste queda incompleto, no se reembolsa la CG una vez cancelada la transacción.
diff --git a/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md b/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
index f7969e4c4..5072bbb8f 100644
--- a/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
+++ b/docs/known-issues/es/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
@@ -18,9 +18,7 @@ internalReference: 583669
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear una tarjeta regalo, configuramos si es recargable o no. Sin embargo, el impedimento de añadir crédito a una tarjeta regalo no recargable ocurre sólo a través de la UI, a través de la API es posible añadir crédito aunque la tarjeta regalo no sea recargable.
diff --git a/docs/known-issues/es/giftcard-transaction-api-always-returns-empty-response.md b/docs/known-issues/es/giftcard-transaction-api-always-returns-empty-response.md
index dcda9d6db..56119b7ac 100644
--- a/docs/known-issues/es/giftcard-transaction-api-always-returns-empty-response.md
+++ b/docs/known-issues/es/giftcard-transaction-api-always-returns-empty-response.md
@@ -18,9 +18,7 @@ internalReference: 384430
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los puntos finales de API Get Giftcard Transaction y Get GiftCard from GiftCard Provider siempre devuelven una respuesta vacía
diff --git a/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md b/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
index 32741e738..ad422c962 100644
--- a/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
+++ b/docs/known-issues/es/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
@@ -18,9 +18,7 @@ internalReference: 402134
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al guardar el evento de la lista de regalos con fecha 31/12/2021, se registra en la interfaz de usuario 30/12/2021, pero es 31/12/2021 en la exportación (la fecha correcta)
diff --git a/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md b/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md
index b05f242a4..c61eaa72a 100644
--- a/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md
+++ b/docs/known-issues/es/global-categories-in-catalog-outdated-compared-to-google.md
@@ -18,9 +18,7 @@ internalReference: 754062
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Google ha actualizado recientemente las categorías de su taxonomía, denominada categoría global en VTEX. Sin embargo, comparando las categorías descritas en el archivo de Google y dentro del catálogo VTEX, se puede ver que nuestra referencia está desactualizada.
diff --git a/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md b/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
index 664f2dba2..091740a1e 100644
--- a/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
+++ b/docs/known-issues/es/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
@@ -18,9 +18,7 @@ internalReference: 756587
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un carrito con al menos 2 productos en el que hay una división de entrega en la que uno de los artículos está disponible para recogida y el otro sólo para entrega programada, la interfaz de usuario no permitirá ir al paso de pago cuando cambie entre las opciones de recogida y entrega si el primer artículo del carrito es el que tiene entrega programada.
diff --git a/docs/known-issues/es/google-bot-terms-appearing-in-results.md b/docs/known-issues/es/google-bot-terms-appearing-in-results.md
index 5515f5520..dc0cd93c5 100644
--- a/docs/known-issues/es/google-bot-terms-appearing-in-results.md
+++ b/docs/known-issues/es/google-bot-terms-appearing-in-results.md
@@ -18,9 +18,7 @@ internalReference: 627537
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los informes de búsqueda inteligente muestran los términos consultados por Google Bot. Se espera que esto sea filtrado.
diff --git a/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md b/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
index b6360748a..e93d3fe04 100644
--- a/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
+++ b/docs/known-issues/es/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
@@ -18,9 +18,7 @@ internalReference: 578443
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El iframe, responsable de la insignia de Opiniones de clientes de Google, tiene una representación incoherente dentro del elemento div del componente Opiniones de clientes de Google.
diff --git a/docs/known-issues/es/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md b/docs/known-issues/es/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md
index 0ca4b0687..9c120360b 100644
--- a/docs/known-issues/es/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md
+++ b/docs/known-issues/es/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md
@@ -18,9 +18,7 @@ internalReference: 727408
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las búsquedas de direcciones de Google Maps para países sin reglas internas específicas no se filtran para devolver sólo este país seleccionado.
diff --git a/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md b/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
index ef92fbd8b..5c160b142 100644
--- a/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
+++ b/docs/known-issues/es/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 639294
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se intenta agrupar por el método de entrega en el tablero de rendimiento de ventas, aparece un error:
diff --git a/docs/known-issues/es/group-name-is-not-automatically-updated-on-intelligent-search.md b/docs/known-issues/es/group-name-is-not-automatically-updated-on-intelligent-search.md
index e47f691a8..7dfd6db4b 100644
--- a/docs/known-issues/es/group-name-is-not-automatically-updated-on-intelligent-search.md
+++ b/docs/known-issues/es/group-name-is-not-automatically-updated-on-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 821481
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, existen 2 módulos de recogida distintos:
diff --git a/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md b/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md
index df225fcea..b671fc999 100644
--- a/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md
+++ b/docs/known-issues/es/headless-cms-ignores-array-validation-settings.md
@@ -18,9 +18,7 @@ internalReference: 1046372
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se intentan configurar reglas de validación de arrays en Headless CMS, como elementos de arrays mínimos y máximos, los errores de validación no se muestran al usuario y es posible guardar el esquema sin pasar la validación.
diff --git a/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md b/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
index 60f02fea8..dd7297dd6 100644
--- a/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
+++ b/docs/known-issues/es/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
@@ -18,9 +18,7 @@ internalReference: 268304
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md b/docs/known-issues/es/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md
index f376d9a60..272d9fbee 100644
--- a/docs/known-issues/es/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md
+++ b/docs/known-issues/es/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 517449
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La falta de agrupación en las tablas de Correios dificulta el uso del filtro Listo para despachar así como puede llevar a algún error, y seleccionar la tabla equivocada.
diff --git a/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md b/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
index dfb1c301e..622ad8351 100644
--- a/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
+++ b/docs/known-issues/es/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
@@ -18,9 +18,7 @@ internalReference: 1020505
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar crear un producto con un formato de imagen establecido como JPG o PNG, el producto se crea con una imagen rota. Este comportamiento no ocurre si el formato se establece como jpg o png (sin capslock).
diff --git a/docs/known-issues/es/image-spreadsheet-not-importing-error-message-fail-to-process-record.md b/docs/known-issues/es/image-spreadsheet-not-importing-error-message-fail-to-process-record.md
index ac59aa8af..65c4370c6 100644
--- a/docs/known-issues/es/image-spreadsheet-not-importing-error-message-fail-to-process-record.md
+++ b/docs/known-issues/es/image-spreadsheet-not-importing-error-message-fail-to-process-record.md
@@ -18,9 +18,7 @@ internalReference: 691803
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md b/docs/known-issues/es/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md
index 482e88e75..0a992a82a 100644
--- a/docs/known-issues/es/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md
+++ b/docs/known-issues/es/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md
@@ -18,9 +18,7 @@ internalReference: 623183
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A pesar del mensaje de éxito en el Admin de que la hoja de cálculo de imágenes se está procesando y que pronto se enviará al correo electrónico, el informe nunca llega realmente.
diff --git a/docs/known-issues/es/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md b/docs/known-issues/es/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md
index ea0fd92e7..c58cbda82 100644
--- a/docs/known-issues/es/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md
+++ b/docs/known-issues/es/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md
@@ -18,9 +18,7 @@ internalReference: 790185
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md b/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md
index f43f8c797..344d86db2 100644
--- a/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md
+++ b/docs/known-issues/es/impersonation-is-ignored-after-one-purchase-is-completed.md
@@ -18,9 +18,7 @@ internalReference: 1003545
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un operador del centro de llamadas se hace pasar por un comprador, completa una compra y es enviado a la página orderPlaced, se generará un nuevo orderForm.
diff --git a/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md b/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
index d67a05fea..e037a93fb 100644
--- a/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
+++ b/docs/known-issues/es/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
@@ -18,9 +18,7 @@ internalReference: 1043039
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de suplantar otro email, se espera que se muestre un botón "Detener suplantación", pero cuando el `showModal` está habilitado, no se muestra.
diff --git a/docs/known-issues/es/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md b/docs/known-issues/es/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md
index 5a1a8657c..5923c79c9 100644
--- a/docs/known-issues/es/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md
+++ b/docs/known-issues/es/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md
@@ -18,9 +18,7 @@ internalReference: 550313
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para reducir la cantidad de skus exportados en la hoja de cálculo Producto/Skus el cliente puede utilizar los filtros.
diff --git a/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
index 2969dd2da..e164cbd01 100644
--- a/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
+++ b/docs/known-issues/es/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -18,9 +18,7 @@ internalReference: 953862
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al importar una hoja de cálculo de productos a una colección, el usuario puede elegir seleccionar los productos por "skuId", "productId", "skuRefId" o "productRefId".
diff --git a/docs/known-issues/es/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md b/docs/known-issues/es/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md
index dfd101f33..07c1c5710 100644
--- a/docs/known-issues/es/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md
+++ b/docs/known-issues/es/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md
@@ -18,9 +18,7 @@ internalReference: 506914
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md b/docs/known-issues/es/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md
index 0bafdc3f3..b979f7e54 100644
--- a/docs/known-issues/es/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md
+++ b/docs/known-issues/es/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md
@@ -18,9 +18,7 @@ internalReference: 742046
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para un escenario de split, cuando el usuario realiza una orden de cambio o incluso una simple cancelación después de que el pago ya ha sido capturado, la pasarela ya no permite recibir un nuevo UpdateAdditionalData.
diff --git a/docs/known-issues/es/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md b/docs/known-issues/es/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md
index 9f026ead9..0bc7dc69e 100644
--- a/docs/known-issues/es/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md
+++ b/docs/known-issues/es/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md
@@ -18,9 +18,7 @@ internalReference: 790828
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el admin de Fullcleanup, hay un botón para reindexar los productos de la cuenta. Se espera que este botón realice la acción en el primer intento, sin embargo, para que la acción se realice puede ser necesario hacer clic en el botón varias veces.
diff --git a/docs/known-issues/es/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md b/docs/known-issues/es/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md
index f2ed1be56..7455338b9 100644
--- a/docs/known-issues/es/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md
+++ b/docs/known-issues/es/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md
@@ -18,9 +18,7 @@ internalReference: 748320
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para un escenario donde el Crédito de Cliente es usado para pagar una cantidad menor que el valor total del carrito; muestra, para 1x cuota en el desplegable, la cantidad total ignorando débitos considerados como pagar con otro método de pago como una tarjeta de regalo.
diff --git a/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md b/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
index bb477a539..de3442c5d 100644
--- a/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
+++ b/docs/known-issues/es/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
@@ -18,9 +18,7 @@ internalReference: 1028210
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se ha detectado que en algunos pedidos en los que existe un descuento asociado a uno o varios artículos, podemos tener una discrepancia en el valor total del campo "artículos a facturar" en la interfaz de usuario del pedido, ya que el cálculo de este campo tiene en cuenta el parámetro "precioVenta", en lugar del parámetro "precioDefiniciones". Por lo tanto, es posible notar diferencias de 0,01 o un poco más del valor total del pedido.
diff --git a/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md b/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
index 3a10753c9..ff59eae4d 100644
--- a/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
+++ b/docs/known-issues/es/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
@@ -18,9 +18,7 @@ internalReference: 559458
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un pedido en el que tenemos dos artículos idénticos, y uno de los artículos es devuelto, las tarifas de ambos artículos se muestran en la interfaz de usuario, en lugar de mostrar sólo las tarifas del artículo que fue devuelto en la interfaz de usuario. Esta información sobre las tarifas es meramente informativa, ya que lo que realmente se devuelve es lo que se rellena en la nota de devolución.
diff --git a/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md b/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md
index 77985d083..922de2c58 100644
--- a/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md
+++ b/docs/known-issues/es/inability-to-make-partial-cancellation-with-mercadopagov1.md
@@ -18,9 +18,7 @@ internalReference: 286738
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la cancelación parcial se realiza en un pago de débito, la pasarela no realizó una solicitud a Mercado Pago y en consecuencia no se realiza la solicitud de captura porque el estado nos hizo entender que el pago ya fue capturado, lo que significa que no se devuelve el dinero del cliente
diff --git a/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md b/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
index 99b1de843..495c882d1 100644
--- a/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
+++ b/docs/known-issues/es/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
@@ -18,9 +18,7 @@ internalReference: 459704
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el usuario registra dos afiliaciones diferentes en la misma cuenta utilizando PayPalPlus, la plataforma no actualiza la caché para cuando se produce un cambio en una regla de pago, es decir, sólo es posible utilizar una credencial por cuenta.
diff --git a/docs/known-issues/es/inactive-product-still-appearing-on-pdp-or-checkout.md b/docs/known-issues/es/inactive-product-still-appearing-on-pdp-or-checkout.md
index 26ccb4580..b56d29142 100644
--- a/docs/known-issues/es/inactive-product-still-appearing-on-pdp-or-checkout.md
+++ b/docs/known-issues/es/inactive-product-still-appearing-on-pdp-or-checkout.md
@@ -18,9 +18,7 @@ internalReference: 542264
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Desactivar sólo el producto por API hace que el producto permanezca activo para el PDP y la caja
diff --git a/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md b/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md
index bdc84fb0f..3e9ca0671 100644
--- a/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md
+++ b/docs/known-issues/es/incomplete-transactions-appearing-with-brazilian-currency.md
@@ -18,9 +18,7 @@ internalReference: 1007953
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Transacciones incompletas (cliente "Sin nombre") pueden aparecer en la sección de Transacciones con moneda R$, estos son resultado de un error de creación (los datos de pago no fueron enviados) pero las órdenes son creadas correctamente en moneda local.
diff --git a/docs/known-issues/es/inconsistencies-in-billingaddress-field-sent-to-gateway.md b/docs/known-issues/es/inconsistencies-in-billingaddress-field-sent-to-gateway.md
index 2749bbc77..449056e10 100644
--- a/docs/known-issues/es/inconsistencies-in-billingaddress-field-sent-to-gateway.md
+++ b/docs/known-issues/es/inconsistencies-in-billingaddress-field-sent-to-gateway.md
@@ -18,9 +18,7 @@ internalReference: 291688
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La pasarela utiliza la dirección incorrecta en los escenarios de compras recurrentes cuando ya hay una tarjeta guardada en el perfil del usuario.
diff --git a/docs/known-issues/es/inconsistency-between-unique-clicks-and-productids-on-is.md b/docs/known-issues/es/inconsistency-between-unique-clicks-and-productids-on-is.md
index 21a1d8a00..a291ccaac 100644
--- a/docs/known-issues/es/inconsistency-between-unique-clicks-and-productids-on-is.md
+++ b/docs/known-issues/es/inconsistency-between-unique-clicks-and-productids-on-is.md
@@ -18,9 +18,7 @@ internalReference: 501802
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente tenemos un problema cuando miramos el archivo CSV, cuenta los clics únicos y también muestra los productIds en orden descendente desde el más alto al más bajo mostrando sólo los primeros 30 debido a una configuración.
diff --git a/docs/known-issues/es/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md b/docs/known-issues/es/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md
index 29960b61c..d09a38c72 100644
--- a/docs/known-issues/es/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md
+++ b/docs/known-issues/es/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md
@@ -18,9 +18,7 @@ internalReference: 489460
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos Boletos Bancarios generados desde el conector ItauShopLine pueden tener una fecha de caducidad diferente a la configurada en la afiliación
diff --git a/docs/known-issues/es/inconsistency-on-the-deadlines-of-customer-credit-invoices.md b/docs/known-issues/es/inconsistency-on-the-deadlines-of-customer-credit-invoices.md
index a24498db0..50be13586 100644
--- a/docs/known-issues/es/inconsistency-on-the-deadlines-of-customer-credit-invoices.md
+++ b/docs/known-issues/es/inconsistency-on-the-deadlines-of-customer-credit-invoices.md
@@ -18,9 +18,7 @@ internalReference: 331279
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los pedidos realizados con Crédito Cliente como forma de pago generan facturas de una sola cuota a 60 días. Si se comprueba la cuenta en el módulo de Crédito Cliente se dice que la factura se ha generado sin problemas. Sin embargo, mirando a través de la API es posible notar que dentro del campo customData los plazos (fechas de vencimiento) se envían con valores diferentes. Esto impacta en la integración con otros sistemas que organizan los cumplimientos.
diff --git a/docs/known-issues/es/inconsistency-on-the-report-admin-page-data.md b/docs/known-issues/es/inconsistency-on-the-report-admin-page-data.md
index b3f0030a0..05e658fd9 100644
--- a/docs/known-issues/es/inconsistency-on-the-report-admin-page-data.md
+++ b/docs/known-issues/es/inconsistency-on-the-report-admin-page-data.md
@@ -18,9 +18,7 @@ internalReference: 501829
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al hacer clic en la página de administración para grandes almacenes devuelve un error del servidor, esto está sucediendo a la agregación realizada que es demasiado pesada.
diff --git a/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md b/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
index b94ebbc89..dfbc2caff 100644
--- a/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
+++ b/docs/known-issues/es/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
@@ -18,9 +18,7 @@ internalReference: 847340
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Información inconsistente entre los Detalles del Centro de Coste en Mi Organización y los Ajustes de Pago B2B donde Mi Organización muestra un término de pago desactivado, pero el término de pago se sigue mostrando al acceder al pago.
diff --git a/docs/known-issues/es/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md b/docs/known-issues/es/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md
index 858e10672..a9da819bb 100644
--- a/docs/known-issues/es/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md
+++ b/docs/known-issues/es/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md
@@ -18,9 +18,7 @@ internalReference: 824198
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de facetas tiene un campo specificationFilters y este campo puede romper el retorno de la API cuando los valores registrados en cualquier especificación de esa categoría son demasiado grandes
diff --git a/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md b/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
index ccc91a89b..d4ca60890 100644
--- a/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
+++ b/docs/known-issues/es/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
@@ -18,9 +18,7 @@ internalReference: 651102
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando algún SKU contiene un multiplicador de unidades diferente de 1 (puede ser int como 10 o 100, o float como 0.8, por ejemplo), en algunas situaciones, el precio devuelto en store-graphql puede tener inconsistencias basadas en la división del precio devuelto desde la API de simulación:
diff --git a/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md b/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md
index 8de1965c7..c32a45556 100644
--- a/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md
+++ b/docs/known-issues/es/incorrect-address-format-on-the-my-cards-billing-addresses.md
@@ -18,9 +18,7 @@ internalReference: 791779
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al añadir una nueva dirección de facturación en vtex.my-cards, se muestra un formato de dirección incorrecto. Esto ocurre cuando el usuario está intentando añadir una nueva tarjeta de crédito, y ocurre sólo cuando la nueva dirección que el usuario está intentando escribir es de un país diferente. Lo que ocurre, por ejemplo, es que el usuario elige una nueva dirección de EE.UU., mientras que las demás son de Canadá, todas las direcciones de Canadá se formatearán como una dirección de EE.UU..
diff --git a/docs/known-issues/es/incorrect-currency-on-payment-form.md b/docs/known-issues/es/incorrect-currency-on-payment-form.md
index eafcdfc8f..8fa9dd3a7 100644
--- a/docs/known-issues/es/incorrect-currency-on-payment-form.md
+++ b/docs/known-issues/es/incorrect-currency-on-payment-form.md
@@ -18,9 +18,7 @@ internalReference: 449286
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/incorrect-data-in-pickupstoreinfo-after-order-creation.md b/docs/known-issues/es/incorrect-data-in-pickupstoreinfo-after-order-creation.md
index 3df18b274..0b66bd78d 100644
--- a/docs/known-issues/es/incorrect-data-in-pickupstoreinfo-after-order-creation.md
+++ b/docs/known-issues/es/incorrect-data-in-pickupstoreinfo-after-order-creation.md
@@ -18,9 +18,7 @@ internalReference: 347155
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunas ocasiones, donde tenemos 1 artículo con opción de entrega y el otro artículo con opción de recogida. Los datos `pickupStoreInfo` se rellenan incorrectamente después de finalizar el pedido.
diff --git a/docs/known-issues/es/incorrect-display-of-package-quantity-at-checkout.md b/docs/known-issues/es/incorrect-display-of-package-quantity-at-checkout.md
index 5ecef082f..f464447e4 100644
--- a/docs/known-issues/es/incorrect-display-of-package-quantity-at-checkout.md
+++ b/docs/known-issues/es/incorrect-display-of-package-quantity-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 520369
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/incorrect-information-in-the-expiration-date-fields-of-promotions.md b/docs/known-issues/es/incorrect-information-in-the-expiration-date-fields-of-promotions.md
index bd1050ea3..c457e3033 100644
--- a/docs/known-issues/es/incorrect-information-in-the-expiration-date-fields-of-promotions.md
+++ b/docs/known-issues/es/incorrect-information-in-the-expiration-date-fields-of-promotions.md
@@ -18,9 +18,7 @@ internalReference: 611284
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 De forma intermitente, cuando abrimos una promoción, los campos Fecha de inicio y Fecha de finalización muestran la fecha actual, y los campos Hora de inicio y Hora de finalización muestran las 12:00 AM. A pesar de la información incorrecta en la UI, las fechas establecidas en la promoción no se ven afectadas.
diff --git a/docs/known-issues/es/incorrect-message-error-when-creatingediting-skus.md b/docs/known-issues/es/incorrect-message-error-when-creatingediting-skus.md
index 3c0a650a8..0f9037108 100644
--- a/docs/known-issues/es/incorrect-message-error-when-creatingediting-skus.md
+++ b/docs/known-issues/es/incorrect-message-error-when-creatingediting-skus.md
@@ -18,9 +18,7 @@ internalReference: 774518
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para crear o editar una SKU es necesario rellenar los campos obligatorios, como peso del envío, altura, anchura y longitud. Sin embargo, cuando dejamos uno de estos campos sin un valor válido y guardamos la SKU, Admin devuelve un mensaje de error sobre las especificaciones, incluso cuando no hay especificaciones requeridas que rellenar.
diff --git a/docs/known-issues/es/incorrect-price-on-order-change-due-to-unit-multiplier.md b/docs/known-issues/es/incorrect-price-on-order-change-due-to-unit-multiplier.md
index 07908c701..ded49d994 100644
--- a/docs/known-issues/es/incorrect-price-on-order-change-due-to-unit-multiplier.md
+++ b/docs/known-issues/es/incorrect-price-on-order-change-due-to-unit-multiplier.md
@@ -18,9 +18,7 @@ internalReference: 371066
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si añade o elimina una SKU de un pedido existente (proceso de modificación de pedido) y la SKU tiene una unidad multiplicadora diferente de 1, la unidad multiplicadora no se tiene en cuenta para calcular el valor del nuevo pedido.
diff --git a/docs/known-issues/es/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md b/docs/known-issues/es/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md
index afaf0f2b3..1688a2061 100644
--- a/docs/known-issues/es/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md
+++ b/docs/known-issues/es/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md
@@ -18,9 +18,7 @@ internalReference: 426275
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El precio mostrado por el bloque vtex.product-price diverge debido a los redondeos de la multiplicación de unidades.
diff --git a/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md b/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
index 0c763d94f..1d3443c4b 100644
--- a/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
+++ b/docs/known-issues/es/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
@@ -18,9 +18,7 @@ internalReference: 1025539
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una promoción aplica un descuento a un solo artículo de la misma SKU (por ejemplo, una promoción Más por Menos), si hay una segunda promoción para esa misma SKU, el cálculo del descuento se aplicará a la cantidad ya descontada por la primera promoción - resultando en un descuento menor que el que se aplicaría si la segunda promoción se aplicara al precio inicial de la SKU.
diff --git a/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
index 4190676fb..417af62d0 100644
--- a/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/es/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -18,9 +18,7 @@ internalReference: 1072285
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al llamar a un reembolso (en transacciones con división de pago) puede ocurrir el error de abajo con importes divergentes:
diff --git a/docs/known-issues/es/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md b/docs/known-issues/es/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md
index 42c9cfa40..306804313 100644
--- a/docs/known-issues/es/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md
+++ b/docs/known-issues/es/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md
@@ -18,9 +18,7 @@ internalReference: 464837
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las transacciones con 3 métodos de pago que son una de sus tarjetas de regalo tienen importes de reembolso incorrectos. En algunos casos tenemos un reembolso negativo que hace que se cancele el pago.
diff --git a/docs/known-issues/es/incorrect-shipping-preview-when-items-are-scheduled-delivery.md b/docs/known-issues/es/incorrect-shipping-preview-when-items-are-scheduled-delivery.md
index 7e9ad61a8..677ff862a 100644
--- a/docs/known-issues/es/incorrect-shipping-preview-when-items-are-scheduled-delivery.md
+++ b/docs/known-issues/es/incorrect-shipping-preview-when-items-are-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 545697
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La visualización de los valores de entrega en shipping-preview (carrito) es incorrecta cuando los artículos tienen una entrega programada y todos estos artículos salen del mismo SLA. Aunque la API devuelva el valor correcto, la interfaz de usuario no refleja esta información y muestra el valor incorrecto.
diff --git a/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md b/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md
index 3ea7ae513..91ba71ff8 100644
--- a/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md
+++ b/docs/known-issues/es/incorrect-shippingestimatedate-for-order-fob.md
@@ -18,9 +18,7 @@ internalReference: 269104
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/incorrect-usd-currency-displayed-in-some-locales.md b/docs/known-issues/es/incorrect-usd-currency-displayed-in-some-locales.md
index 9a4d7653c..7abe0b598 100644
--- a/docs/known-issues/es/incorrect-usd-currency-displayed-in-some-locales.md
+++ b/docs/known-issues/es/incorrect-usd-currency-displayed-in-some-locales.md
@@ -18,9 +18,7 @@ internalReference: 414901
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/incorrect-value-on-package-due-discount-division.md b/docs/known-issues/es/incorrect-value-on-package-due-discount-division.md
index 9d5416f0b..0a5e467f9 100644
--- a/docs/known-issues/es/incorrect-value-on-package-due-discount-division.md
+++ b/docs/known-issues/es/incorrect-value-on-package-due-discount-division.md
@@ -18,9 +18,7 @@ internalReference: 605517
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El paquete tiene un valor diferente del total del pedido sin el valor del envío. Esto sucede debido a que los descuentos no tienen una división adecuada con la cantidad de itens de la orden.
diff --git a/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md b/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
index d1d67cd39..f989ba3e5 100644
--- a/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
+++ b/docs/known-issues/es/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
@@ -18,9 +18,7 @@ internalReference: 1050023
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, una cuenta de franquicia puede tener su registro fulFillmentEndpoint diferente de su nombre de cuenta "oficial", lo cual es una práctica común para arquitecturas específicas de vendedor<>marketplace que necesitan múltiples precios y/o stock para distintos canales de venta utilizando la característica de franquicia con múltiples vendedores para la misma franquicia.
diff --git a/docs/known-issues/es/incorrectly-updated-inventory.md b/docs/known-issues/es/incorrectly-updated-inventory.md
index 3b8dd9f21..aad035fa8 100644
--- a/docs/known-issues/es/incorrectly-updated-inventory.md
+++ b/docs/known-issues/es/incorrectly-updated-inventory.md
@@ -18,9 +18,7 @@ internalReference: 556514
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La emisora fue notificada para el cambio de existencias en el mismo día en 2 minutos, pero sólo llegó una notificación en la integración.
diff --git a/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md b/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
index 35dc65f2e..804fbe886 100644
--- a/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
+++ b/docs/known-issues/es/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
@@ -18,9 +18,7 @@ internalReference: 822120
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El precio indexado, que es un valor único para todo el producto (junto con sus SKUs), y se utiliza para ordenar y filtrar los productos en la Búsqueda Inteligente, está considerando el precio más alto entre los SKUs, mientras que lo esperado es considerar el SKU con el precio más bajo - junto con reglas adicionales sobre la política comercial y los vendedores de los SKUs.
diff --git a/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md b/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
index 6f6f3e295..971e9167e 100644
--- a/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
+++ b/docs/known-issues/es/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 684464
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md b/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
index 677cb789e..3b97fbd15 100644
--- a/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
+++ b/docs/known-issues/es/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
@@ -18,9 +18,7 @@ internalReference: 1008459
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos tienen el mismo SKUid en un conjunto separado de artículos, esto ocurre en el momento de la compra en la caja por diferentes razones como el descuento a aplicar, por ejemplo.
diff --git a/docs/known-issues/es/infocard-mobile-images-wont-apply.md b/docs/known-issues/es/infocard-mobile-images-wont-apply.md
index 81a02a42e..6aea8b15a 100644
--- a/docs/known-issues/es/infocard-mobile-images-wont-apply.md
+++ b/docs/known-issues/es/infocard-mobile-images-wont-apply.md
@@ -18,9 +18,7 @@ internalReference: 909647
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando cambias la imagen de una infocard para que se muestre en la versión móvil, no se muestra. En su lugar, se sigue mostrando la imagen principal.
diff --git a/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
index f4644de90..a568a8400 100644
--- a/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
+++ b/docs/known-issues/es/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -18,9 +18,7 @@ internalReference: 1069222
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un **user-agent** es una cadena de texto que un navegador web u otro cliente envía a un servidor web en una cabecera de petición HTTP para identificarse. Esta cadena contiene información sobre el tipo de navegador, sistema operativo, y a veces detalles adicionales como la versión del navegador y el motor de renderizado utilizado.
diff --git a/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md b/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md
index 627f70ad8..391fda4f1 100644
--- a/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md
+++ b/docs/known-issues/es/installment-options-not-updating-automatically-on-pdpplp.md
@@ -18,9 +18,7 @@ internalReference: 987467
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una cuenta cambia las opciones de pago a plazos de un producto, a pesar de que el producto está correctamente indexado, las opciones de pago a plazos no se actualizan en el PLP o en el PDP (a veces en ambos).
diff --git a/docs/known-issues/es/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md b/docs/known-issues/es/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md
index c4d73d4de..072f27e29 100644
--- a/docs/known-issues/es/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md
+++ b/docs/known-issues/es/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md
@@ -18,9 +18,7 @@ internalReference: 644563
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una promoción está restringida a una cantidad específica de cuotas de la tarjeta de crédito (por ejemplo, "10% en efectivo"), el importe descontado se aplica incluso a las cuotas fuera del rango limitado, donde el objeto "installmentOptions" de la API de orderForm devolverá valores erróneos.
diff --git a/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md b/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
index 3683fecc6..36871b530 100644
--- a/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
+++ b/docs/known-issues/es/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
@@ -18,9 +18,7 @@ internalReference: 540257
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al abrir el desplegable de cuotas en la página de pago y desplazamiento de otra página de pago, se puede ver que la casilla de cuotas se desprende y queda suelta en la pantalla de pago
diff --git a/docs/known-issues/es/instore-does-not-read-properly-the-html-registred-in-the-product-information.md b/docs/known-issues/es/instore-does-not-read-properly-the-html-registred-in-the-product-information.md
index 2001f88f9..7ef6fbb3f 100644
--- a/docs/known-issues/es/instore-does-not-read-properly-the-html-registred-in-the-product-information.md
+++ b/docs/known-issues/es/instore-does-not-read-properly-the-html-registred-in-the-product-information.md
@@ -18,9 +18,7 @@ internalReference: 718136
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la página del producto, alguna información sobre el producto tiene etiquetas HTML(<b>[...]</b>, <font>[...]</font>, <li>[...]</li> etc).
diff --git a/docs/known-issues/es/integracao-de-pedido-amazon-quantidade-de-item-invalida.md b/docs/known-issues/es/integracao-de-pedido-amazon-quantidade-de-item-invalida.md
index 384ddccd7..8b06de849 100644
--- a/docs/known-issues/es/integracao-de-pedido-amazon-quantidade-de-item-invalida.md
+++ b/docs/known-issues/es/integracao-de-pedido-amazon-quantidade-de-item-invalida.md
@@ -18,9 +18,7 @@ internalReference: 385656
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md b/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
index a4f5bbd7a..16137f542 100644
--- a/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
+++ b/docs/known-issues/es/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
@@ -18,9 +18,7 @@ internalReference: 734833
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En Admin V4, en el módulo Banners, el usuario tiene la posibilidad de crear o actualizar banners ya creados. Al seleccionar un banner para actualizar, puede elegir entre utilizar un campo HTML o insertar un enlace de imagen directo con una URL externa. Al seleccionar insertar el banner mediante un enlace de imagen directo, se lanza la consulta GraphQL, que actualmente no funciona correctamente, devolviendo `syntaxError`, en consecuencia, error 500.
diff --git a/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md b/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
index 6b7478a4f..3c2dfa51d 100644
--- a/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
+++ b/docs/known-issues/es/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
@@ -18,9 +18,7 @@ internalReference: 990343
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El idioma principal de la Búsqueda Inteligente no se actualiza automáticamente según la política comercial y la configuración de vinculación, lo que hace que no esté sincronizado.
diff --git a/docs/known-issues/es/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md b/docs/known-issues/es/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md
index 0648df488..9c8b66ac6 100644
--- a/docs/known-issues/es/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md
+++ b/docs/known-issues/es/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md
@@ -18,9 +18,7 @@ internalReference: 841704
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si utilizamos más de una configuración regional en la cuenta, la traducción se realizará en función del idioma al que se refiera la configuración regional y si utilizamos más de una configuración regional en la cuenta, la traducción se realizará en función del idioma al que se refiera la configuración regional.
diff --git a/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md b/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md
index 80e6b3304..9874d942b 100644
--- a/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md
+++ b/docs/known-issues/es/intelligent-search-not-capturing-sales-events-for-faststore.md
@@ -18,9 +18,7 @@ internalReference: 1045163
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Búsqueda Inteligente no está capturando los eventos de pedidos finalizados para las tiendas que utilizan FastStore. Estos eventos componen los criterios de relevancia y la clasificación de productos por ventas.
diff --git a/docs/known-issues/es/intelligent-search-not-returning-correct-sku-order.md b/docs/known-issues/es/intelligent-search-not-returning-correct-sku-order.md
index b9277196b..68e395142 100644
--- a/docs/known-issues/es/intelligent-search-not-returning-correct-sku-order.md
+++ b/docs/known-issues/es/intelligent-search-not-returning-correct-sku-order.md
@@ -18,9 +18,7 @@ internalReference: 677937
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de búsqueda inteligente no devuelve el orden esperado de las variaciones de SKU para un producto en la búsqueda y las estanterías
diff --git a/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md b/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
index 68ba08511..73301a2f0 100644
--- a/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
+++ b/docs/known-issues/es/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
@@ -18,9 +18,7 @@ internalReference: 361894
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La página de configuración de Redirección de Búsqueda Inteligente tiene una barra de búsqueda para ayudar a encontrar configuraciones de redirección específicas, pero distingue entre mayúsculas y minúsculas y sólo encontrará términos si coinciden exactamente.
diff --git a/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md b/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
index 3cd22c398..14fe0b467 100644
--- a/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
+++ b/docs/known-issues/es/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
@@ -18,9 +18,7 @@ internalReference: 1072003
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera que los términos buscados se normalicen entre sus diferentes formas (plural/singular, género y otras posibilidades), un proceso formalmente llamado stemming. El analizador es diferente para cada idioma para ajustarse a sus necesidades.
diff --git a/docs/known-issues/es/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md b/docs/known-issues/es/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md
index e0956d2e3..057b8c8a4 100644
--- a/docs/known-issues/es/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md
+++ b/docs/known-issues/es/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md
@@ -18,9 +18,7 @@ internalReference: 428486
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Búsqueda Inteligente tiene un problema con la paginación de los valores. Esto hace que algunos valores no se muestren al seleccionarlos en un filtro de condición, como las condiciones de Reglas de comercialización, por ejemplo. Si el campo seleccionado contiene más de 9.999 valores, sólo se mostrarán los primeros 9.999 en el desplegable de vista previa.
diff --git a/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md b/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
index ccf082de8..604665808 100644
--- a/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
+++ b/docs/known-issues/es/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
@@ -18,9 +18,7 @@ internalReference: 423811
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el usuario elige cambiar su dirección mientras algunos datos respectivos todavía se están cargando en la página, el componente de dirección cambia de geolocalización al componente con un desplegable. Los datos pueden ser, por ejemplo, la selección de una tienda para recoger. Mientras los datos se cargan en la interfaz, el usuario hace clic en "cambiar dirección", con eso, la dirección de vuelta está en otro componente, no en el componente de geolocalización.
diff --git a/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md b/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
index 0cc64c0e2..3cabc8c4a 100644
--- a/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
+++ b/docs/known-issues/es/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
@@ -18,9 +18,7 @@ internalReference: 952086
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el comprador cambia el método de pago mientras el componente de pago todavía se está cargando en la página, si el método de pago tiene opciones, el pago enviado al orderForm es incorrecto. Cuando se produce este comportamiento, el pedido no se crea y se muestra un mensaje para revisar la información de pago.
diff --git a/docs/known-issues/es/intermitent-site-editor-content-loss.md b/docs/known-issues/es/intermitent-site-editor-content-loss.md
index 1e8af4429..4ea22e16b 100644
--- a/docs/known-issues/es/intermitent-site-editor-content-loss.md
+++ b/docs/known-issues/es/intermitent-site-editor-content-loss.md
@@ -18,9 +18,7 @@ internalReference: 610533
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cada cambio de contenido en el Editor de Sitios inserta cambios en el archivo content.json, que se almacena en un bucket en AWS S3. Algunos clientes han informado de la pérdida de contenido del Editor de Sitios tras algunos procedimientos habituales de actualización de temas.
diff --git a/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md b/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md
index 7f015de44..2aa5b85c0 100644
--- a/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md
+++ b/docs/known-issues/es/internalsearcherror-timeouts-on-portal.md
@@ -18,9 +18,7 @@ internalReference: 1043003
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la actualidad, las tiendas que utilizan la búsqueda heredada del Portal pueden enfrentarse, al utilizar varios filtros en su tienda, como filtros de colección en plantillas, a tiempos de espera aleatorios e intermitentes que a menudo se muestran como un error "Algo ha ido mal" para los clientes.
diff --git a/docs/known-issues/es/intl-not-considering-custom-currency-in-formatcurrency.md b/docs/known-issues/es/intl-not-considering-custom-currency-in-formatcurrency.md
index a633c6ae1..90c01fee2 100644
--- a/docs/known-issues/es/intl-not-considering-custom-currency-in-formatcurrency.md
+++ b/docs/known-issues/es/intl-not-considering-custom-currency-in-formatcurrency.md
@@ -18,9 +18,7 @@ internalReference: 736695
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md b/docs/known-issues/es/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md
index be36605de..827b656dd 100644
--- a/docs/known-issues/es/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md
+++ b/docs/known-issues/es/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md
@@ -18,9 +18,7 @@ internalReference: 442772
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El error ocurre en un escenario específico en el que se rellena la información de la tarjeta, luego se cambia el método de pago a otro (MercadoPago por ejemplo) y luego se vuelve de nuevo al método de pago con tarjeta de crédito y luego se confirma el pago.
diff --git a/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
index 4f147ee39..39cd2d828 100644
--- a/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
+++ b/docs/known-issues/es/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -18,9 +18,7 @@ internalReference: 1053959
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Checkout UI utiliza el país registrado en su estado para validar la entrada del código postal.
diff --git a/docs/known-issues/es/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md b/docs/known-issues/es/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md
index 2eca6cce4..664e9acbd 100644
--- a/docs/known-issues/es/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md
+++ b/docs/known-issues/es/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md
@@ -18,9 +18,7 @@ internalReference: 346163
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Como en realidad la misma API crea y actualiza el almacén (Create/update warehouse: `POST https://{accountName}.{environment}.com.br/api/logistics/pvt/configuration/warehouses`), Logística identifica por el id qué acción debe realizarse, y como el id es sensible a mayúsculas y minúsculas, si la intención sería actualizar de id "TEST" pero se introduce el id "test", se crea un nuevo almacén, pero el inventario se replica para ambos porque el inventario es insensible a mayúsculas y minúsculas.
 
diff --git a/docs/known-issues/es/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md b/docs/known-issues/es/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md
index 13627d808..b460d47da 100644
--- a/docs/known-issues/es/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md
+++ b/docs/known-issues/es/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md
@@ -18,9 +18,7 @@ internalReference: 427610
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/inventory-management-search-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/es/inventory-management-search-not-working-properly-on-seller-portal-accounts.md
index 7b877250b..95dc6a2a8 100644
--- a/docs/known-issues/es/inventory-management-search-not-working-properly-on-seller-portal-accounts.md
+++ b/docs/known-issues/es/inventory-management-search-not-working-properly-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 694254
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La búsqueda de gestión de inventario no se comporta como se espera en las cuentas del portal del vendedor. Esto ocurre porque este tipo de cuentas utilizan una versión diferente del catálogo.
diff --git a/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md b/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md
index 264473225..7667c90c4 100644
--- a/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md
+++ b/docs/known-issues/es/inventory-notifications-to-indexer-are-cached.md
@@ -18,9 +18,7 @@ internalReference: 914545
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una cuenta de franquicia o vendedor notifica a la cuenta principal (o marketplace) sobre cambios en el inventario, la cuenta envía el producto al indexador para tener la información más actualizada.
diff --git a/docs/known-issues/es/inventory-reserved-items-error.md b/docs/known-issues/es/inventory-reserved-items-error.md
index 24776d768..3a9532708 100644
--- a/docs/known-issues/es/inventory-reserved-items-error.md
+++ b/docs/known-issues/es/inventory-reserved-items-error.md
@@ -18,9 +18,7 @@ internalReference: 347924
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md b/docs/known-issues/es/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md
index ff4541bdb..a484a912a 100644
--- a/docs/known-issues/es/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md
+++ b/docs/known-issues/es/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 549645
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
index a7abf1cae..0f3745c00 100644
--- a/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
+++ b/docs/known-issues/es/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -18,9 +18,7 @@ internalReference: 1061149
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear categorías a través de la API o del panel de administración, el nombre de la categoría no se valida correctamente, lo que permite incluir caracteres invisibles. Dado que el nombre de la categoría se utiliza para generar la URL de la categoría, estos caracteres invisibles también se incluyen en la URL. Esto provoca que la página de la categoría no funcione correctamente y devuelva un error de "Página no encontrada".
diff --git a/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md b/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
index c50dfcd9c..2074b814a 100644
--- a/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
+++ b/docs/known-issues/es/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
@@ -18,9 +18,7 @@ internalReference: 656284
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar utilizar el parámetro isAvailablePerSalesChannel para mostrar los productos disponibles (fq=isAvailablePerSalesChannel_{id}:1) o no disponibles (fq=isAvailablePerSalesChannel_{id}:0) el resultado no es coherente.
diff --git a/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md b/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md
index 59c7c9bff..616eeb7fc 100644
--- a/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md
+++ b/docs/known-issues/es/issue-on-the-explained-search-for-searches-with-accent-marks.md
@@ -18,9 +18,7 @@ internalReference: 434752
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza la Búsqueda Explicada en el admin para depurar y buscar un producto con acento en el nombre como por ejemplo "Pão Francês", tenemos un sinónimo que funciona como se espera pero esta información no se refleja en la pantalla para que el equipo pueda depurar y comprobar si está funcionando.
diff --git a/docs/known-issues/es/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md b/docs/known-issues/es/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md
index dcc8f9cb8..bc109639a 100644
--- a/docs/known-issues/es/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md
+++ b/docs/known-issues/es/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md
@@ -18,9 +18,7 @@ internalReference: 680241
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md b/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md
index ba09ed1f4..44f75e1c8 100644
--- a/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md
+++ b/docs/known-issues/es/issue-on-translating-titles-for-some-facets.md
@@ -18,9 +18,7 @@ internalReference: 776353
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay algunos casos en los que el título de la página es incorrecto para las tiendas multilingües en páginas como categoría, subcategoría y marcas, donde la ruta tiene un valor en él y al mirar el título de la página tiene un nombre diferente que no coincide con el esperado.
diff --git a/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md b/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
index 725d1700f..14b71dd25 100644
--- a/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
+++ b/docs/known-issues/es/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
@@ -18,9 +18,7 @@ internalReference: 885011
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de sesión está generando algunas inconsistencias. El equipo de ingeniería ha identificado el fallo, el fallo está relacionado con propiedades que empiezan por la misma palabra.
diff --git a/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md b/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
index 3868b8798..09908f18a 100644
--- a/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
+++ b/docs/known-issues/es/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 943629
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar la tarjeta regalo de fidelización, los usuarios pueden tener una mala experiencia al seleccionar la opción "Utilizar sólo parte del valor", ya que no hay ningún botón "Añadir" después de rellenar "Valor a utilizar" (la entrada se acepta automáticamente), por lo que si un valor no se rellena lo suficientemente rápido, se actualizará sólo con los primeros dígitos, obligando al usuario a repetir el procedimiento. Esta experiencia es peor a través del sitio web para móviles.
diff --git a/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md b/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md
index eda50deff..2a2850228 100644
--- a/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md
+++ b/docs/known-issues/es/issues-with-billingaddress-leading-to-transaction-cancellations.md
@@ -18,9 +18,7 @@ internalReference: 1027901
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/issues-with-my-account-links.md b/docs/known-issues/es/issues-with-my-account-links.md
index 49e050d67..cbd8a5eb9 100644
--- a/docs/known-issues/es/issues-with-my-account-links.md
+++ b/docs/known-issues/es/issues-with-my-account-links.md
@@ -18,9 +18,7 @@ internalReference: 522514
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los enlaces en Mi Cuenta (menú de cabecera) no funcionan si el usuario ya está en la sección Mi Cuenta
diff --git a/docs/known-issues/es/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md b/docs/known-issues/es/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md
index d9270724e..16202cfba 100644
--- a/docs/known-issues/es/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md
+++ b/docs/known-issues/es/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md
@@ -18,9 +18,7 @@ internalReference: 825122
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Sólo hay dos formas de cambiar el campo `isValueChangeable` de una transacción: cuando se produce una división, y cuando el `maximumValue` es igual al `minimumValue`. Además, hay que tener en cuenta que todas las transacciones se crean con un "valor mínimo" de 0,01. Por lo tanto, cuando una transacción se divide, el campo "isValueChangeable" no se modifica. En consecuencia, cuando se crea una transacción con un valor de 0,01, el campo "isValueChangeable" se establece automáticamente en "false".
diff --git a/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md b/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
index 168bd1d4b..2a1817bc2 100644
--- a/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
+++ b/docs/known-issues/es/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 412041
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Durante el proceso de compra, si el cliente añade un artículo que ya ha sido incluido en el carrito anteriormente y la nueva inclusión tiene opciones de montaje, el segundo artículo no se añade al carrito.
diff --git a/docs/known-issues/es/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md b/docs/known-issues/es/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md
index f05a71809..f51b025cf 100644
--- a/docs/known-issues/es/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md
+++ b/docs/known-issues/es/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md
@@ -18,19 +18,13 @@ internalReference: 507480
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md b/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
index f1485b0ac..a8eba1409 100644
--- a/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
+++ b/docs/known-issues/es/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
@@ -18,9 +18,7 @@ internalReference: 923619
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si intentamos crear una ruta usando tipos de contenido a través de la UI la página no funcionará. Sólo funciona si la creamos a través del tema.
diff --git a/docs/known-issues/es/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md b/docs/known-issues/es/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md
index f287c6a6e..299c96774 100644
--- a/docs/known-issues/es/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md
+++ b/docs/known-issues/es/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md
@@ -18,9 +18,7 @@ internalReference: 833957
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
index 4e6dc6108..ec905e2d4 100644
--- a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
+++ b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
@@ -18,9 +18,7 @@ internalReference: 385410
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
index 614290742..6673a467f 100644
--- a/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
+++ b/docs/known-issues/es/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
@@ -18,9 +18,7 @@ internalReference: 386030
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un caso de algunas direcciones que no se pueden guardar en la página de la sección Mi Cuenta en las cuentas de Chile.
diff --git a/docs/known-issues/es/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md b/docs/known-issues/es/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md
index de72b0f54..a5f3ee9cd 100644
--- a/docs/known-issues/es/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md
+++ b/docs/known-issues/es/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md
@@ -18,9 +18,7 @@ internalReference: 558065
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la transacción con Boleto Bancário utilizando el conector BrasPag está atascada en aprobado, pago en autorizado y se llama a la API Liquidar la transacción, se produce un error en la captura debido a que el estado está como liquidando, lo que no permite que la transacción sea efectivamente capturada.
diff --git a/docs/known-issues/es/item-added-to-change-order-is-in-another-package-after-invoiced.md b/docs/known-issues/es/item-added-to-change-order-is-in-another-package-after-invoiced.md
index 89de17af8..beb7e9264 100644
--- a/docs/known-issues/es/item-added-to-change-order-is-in-another-package-after-invoiced.md
+++ b/docs/known-issues/es/item-added-to-change-order-is-in-another-package-after-invoiced.md
@@ -18,9 +18,7 @@ internalReference: 412526
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los elementos eliminados o añadidos por el flujo de órdenes de cambio no forman parte del paquete, por lo que no aparecerán en el correo electrónico de la factura, y en caso de que todos los elementos de una orden se eliminen y se añadan más tarde, el correo electrónico de la factura no se envía, porque los elementos añadidos no se añaden al paquete original de la orden;
diff --git a/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md b/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
index d1208f2cb..2c4caf71d 100644
--- a/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
+++ b/docs/known-issues/es/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
@@ -18,9 +18,7 @@ internalReference: 348841
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al modificar un artículo (orden de modificación) desde una cuenta de vendedor de Marca Blanca, el autocompletado no muestra el artículo como se esperaba.
diff --git a/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md b/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md
index ba30d5f27..378120679 100644
--- a/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md
+++ b/docs/known-issues/es/item-available-when-customer-location-is-not-defined-with-no-stock.md
@@ -18,9 +18,7 @@ internalReference: 1073363
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la ubicación del cliente no está definida, los artículos aparecen disponibles incluso cuando no hay existencias disponibles y la marca blanca del vendedor no es completa. Esto solo ocurre si la SKU tiene existencias en el vendedor de marca blanca en un almacén asociado a un canal de ventas distinto al registrado en el punto final de cumplimiento del vendedor.
diff --git a/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md b/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
index 378e1e5fc..906160770 100644
--- a/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
+++ b/docs/known-issues/es/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
@@ -18,9 +18,7 @@ internalReference: 878629
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el SKU tiene el mismo nombre que el producto, el item_name de la compra es diferente del item_name del evento add-to-cart.
diff --git a/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md b/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
index c26fe60a0..dcb7f80c1 100644
--- a/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
+++ b/docs/known-issues/es/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
@@ -18,9 +18,7 @@ internalReference: 985850
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md b/docs/known-issues/es/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md
index ef17735b9..b42a7da72 100644
--- a/docs/known-issues/es/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md
+++ b/docs/known-issues/es/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md
@@ -18,9 +18,7 @@ internalReference: 648117
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md b/docs/known-issues/es/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md
index b0d17672d..eef4abb86 100644
--- a/docs/known-issues/es/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md
+++ b/docs/known-issues/es/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference: 393483
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La `secuencia`, número que puede verse junto al número de pedido y también en la transacción, es la responsable de vincular la transacción al pedido y también la inversa.
diff --git a/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md b/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md
index 90575704a..cbcfb6cb1 100644
--- a/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md
+++ b/docs/known-issues/es/kit-creation-api-is-not-calculating-component-prices.md
@@ -18,9 +18,7 @@ internalReference: 739693
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la carga útil de la API de insertar KIT tiene un formato que solicita los componentes de los que consta este kit y sus cantidades y precios correspondientes.
diff --git a/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md b/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md
index 4558701f2..34e77b6fe 100644
--- a/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md
+++ b/docs/known-issues/es/kit-weight-can-be-overritten-by-apiwebservice.md
@@ -19,9 +19,7 @@ internalReference: 429993
 ## Sumario
 
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés
 
 Actualmente, las reglas de negocio de nuestro catálogo establecen que el peso de la carga de un KIT SKU debe ser definido por la suma de sus componentes - https://help.vtex.com/en/tutorial/cadastrando-kit--tutorials_215
 
diff --git a/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md b/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
index 9282aa658..5563374e0 100644
--- a/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
+++ b/docs/known-issues/es/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
@@ -18,9 +18,7 @@ internalReference: 496298
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Existe un problema para aprobar algunas transacciones que está relacionado con el sistema antifraude Konduto. Este problema surge cuando el sistema no puede realizar la petición necesaria debido a la ausencia del accountId, que es necesario para recuperar la información del pago de la base de datos de cuentas. Puede comprobarlo examinando la ruta "/payment", donde encontrará el nodo "usedAccountId" con valor "False" en estos casos.
diff --git a/docs/known-issues/es/lack-of-feedback-while-selecting-gift-items-that-arent-available.md b/docs/known-issues/es/lack-of-feedback-while-selecting-gift-items-that-arent-available.md
index d9dc18bb0..47b2dff99 100644
--- a/docs/known-issues/es/lack-of-feedback-while-selecting-gift-items-that-arent-available.md
+++ b/docs/known-issues/es/lack-of-feedback-while-selecting-gift-items-that-arent-available.md
@@ -18,9 +18,7 @@ internalReference: 648767
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La selección de un artículo de regalo en el carrito que no tiene existencias no proporcionará ninguna respuesta. Después de seleccionar el regalo, se realizará la solicitud de la API, pero cuando responda, la selección del regalo se eliminará sin más.
diff --git a/docs/known-issues/es/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md b/docs/known-issues/es/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md
index f97517d59..7559c9c6f 100644
--- a/docs/known-issues/es/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md
+++ b/docs/known-issues/es/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md
@@ -18,9 +18,7 @@ internalReference: 680500
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La validación de un número de teléfono está restringida al formulario donde se inserta o edita a través de la interfaz en el paso de perfil de compra. Los valores insertados directamente a través de las APIs REST a un orderForm o a un pedido, o que provengan del perfil del cliente (que, a su manera, pueden ser insertados por diferentes vías) no son validados por la plataforma.
diff --git a/docs/known-issues/es/lack-of-validation-in-the-billingaddress-zip-code.md b/docs/known-issues/es/lack-of-validation-in-the-billingaddress-zip-code.md
index 8c7f2085d..8a5e255a6 100644
--- a/docs/known-issues/es/lack-of-validation-in-the-billingaddress-zip-code.md
+++ b/docs/known-issues/es/lack-of-validation-in-the-billingaddress-zip-code.md
@@ -18,9 +18,7 @@ internalReference: 375481
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Es posible rellenar y completar la compra rellenando el código postal `billingAddress` con caracteres no numéricos
diff --git a/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md b/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md
index e90398b26..24848afa3 100644
--- a/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md
+++ b/docs/known-issues/es/large-importexport-spreadsheet-error-on-new-collections-admin.md
@@ -18,9 +18,7 @@ internalReference: 362017
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, subir artículos al nuevo módulo de colecciones con una lista de más de 1000 SKUs es imposible, ya que el proceso se agota. Devuelve una respuesta de error inespecífica
diff --git a/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md b/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
index 33a28fd59..ced0555cf 100644
--- a/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
+++ b/docs/known-issues/es/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
@@ -18,9 +18,7 @@ internalReference: 322657
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md b/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
index c5813c6be..138259a4e 100644
--- a/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
+++ b/docs/known-issues/es/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
@@ -18,9 +18,7 @@ internalReference: 455218
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos escenarios es posible que aunque la función LeanShipping esté desactivada en la configuración, el sistema aún considere necesario agrupar las opciones de envío, y con ello no desactivará leanShipping, esto se debe a que la regla utilizada por el sistema para definir el uso o no de leanShipping distinta a la configuración está activada o desactivada y existen los mismos o diferentes ANS disponibles para los artículos del carrito;
diff --git a/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
index 031adcb9d..9c6acaabe 100644
--- a/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
+++ b/docs/known-issues/es/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -18,9 +18,7 @@ internalReference: 1053609
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un comprador puede buscar diferentes puntos de recogida en diferentes códigos postales. Al utilizar lean shipping, después de añadir un código postal con puntos de recogida disponibles y cambiar a un código postal sin puntos de recogida, el paso de envío se bloquea con el mensaje "Algo ha ido mal".
diff --git a/docs/known-issues/es/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md b/docs/known-issues/es/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md
index c93a95943..7a0f09d33 100644
--- a/docs/known-issues/es/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md
+++ b/docs/known-issues/es/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md
@@ -18,9 +18,7 @@ internalReference: 842018
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En carros donde hay una entrega programada y una entrega regular, y Lean Shipping está activado; si la opción más barata y rápida es la entrega programada, la UI mostrará el toggle normalmente, pero al deseleccionar, no pasará nada, y la entrega programada seguirá seleccionada.
diff --git a/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md b/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
index 9b032414e..384678508 100644
--- a/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
+++ b/docs/known-issues/es/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
@@ -18,9 +18,7 @@ internalReference: 916461
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Lean Shipping no se desactiva automáticamente después de eliminar artículos del carrito, manteniendo sólo uno donde debería mostrar todas las opciones.
diff --git a/docs/known-issues/es/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md b/docs/known-issues/es/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md
index 5fdd8fdab..38d729961 100644
--- a/docs/known-issues/es/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md
+++ b/docs/known-issues/es/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md
@@ -18,9 +18,7 @@ internalReference: 607411
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
index 5eed0a613..0ee8b0179 100644
--- a/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
+++ b/docs/known-issues/es/legacy-catalog-ui-delete-button-not-functional.md
@@ -18,9 +18,7 @@ internalReference: 326408
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El botón para eliminar productos en el catálogo no funciona, simplemente no reconoce ningún clic del usuario
diff --git a/docs/known-issues/es/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md b/docs/known-issues/es/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md
index 5bda759a8..f92204db1 100644
--- a/docs/known-issues/es/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md
+++ b/docs/known-issues/es/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md
@@ -18,9 +18,7 @@ internalReference: 825530
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Legacy CMS no crea carpetas con menos de 3 caracteres en el nombre
diff --git a/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md b/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md
index c685fd21d..9a61ba1d9 100644
--- a/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md
+++ b/docs/known-issues/es/legacy-cmss-banner-custom-element-not-working.md
@@ -18,9 +18,7 @@ internalReference: 978466
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la pestaña "elementos personalizados" de las configuraciones del CMS heredado no funciona correctamente.
diff --git a/docs/known-issues/es/legacy-collection-import-timeout.md b/docs/known-issues/es/legacy-collection-import-timeout.md
index f957d8587..c6ce2f69e 100644
--- a/docs/known-issues/es/legacy-collection-import-timeout.md
+++ b/docs/known-issues/es/legacy-collection-import-timeout.md
@@ -18,9 +18,7 @@ internalReference: 483785
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando un usuario intenta importar datos a través del botón de inserción masiva de skus, si la hoja que se está utilizando es demasiado extensa, el proceso puede fallar.
diff --git a/docs/known-issues/es/legacy-collection-schedule-does-not-respect-sc-timezone.md b/docs/known-issues/es/legacy-collection-schedule-does-not-respect-sc-timezone.md
index 87d34e79f..001f20d81 100644
--- a/docs/known-issues/es/legacy-collection-schedule-does-not-respect-sc-timezone.md
+++ b/docs/known-issues/es/legacy-collection-schedule-does-not-respect-sc-timezone.md
@@ -18,9 +18,7 @@ internalReference: 316054
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El horario de recogida del legado no respeta la zona horaria de SC.
diff --git a/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md b/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
index 0a2bf4c3e..624b64bcb 100644
--- a/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
+++ b/docs/known-issues/es/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
@@ -18,9 +18,7 @@ internalReference: 590934
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Eventualmente, dependiendo del número de productos que tengamos dentro de una categoría, si seleccionamos los filtros de categorías en la UI de la colección heredada, puede que nos devuelva productos que no pertenezcan a estas categorías.
diff --git a/docs/known-issues/es/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md b/docs/known-issues/es/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md
index 0198e8cae..97c3e8cb7 100644
--- a/docs/known-issues/es/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md
+++ b/docs/known-issues/es/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md
@@ -18,9 +18,7 @@ internalReference: 450569
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md b/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
index 4111eb932..dbfa73909 100644
--- a/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
+++ b/docs/known-issues/es/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
@@ -18,9 +18,7 @@ internalReference: 979205
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, para la tienda que utiliza el CMS heredado, la plantilla heredada y los controles de estantería no se ajustan si el SKU tiene un multiplicador de unidades.
diff --git a/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md b/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md
index 1c160fe3d..ebd65f05e 100644
--- a/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md
+++ b/docs/known-issues/es/let-me-know-controller-texts-are-not-being-translated.md
@@ -18,9 +18,7 @@ internalReference: 517165
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar cambiar el texto del "nombre" y del "correo electrónico" del controlador de Let Me Know a través de Store Text a otros idiomas que no sean EN-BR, el texto no se traduce y permanece en portugués
diff --git a/docs/known-issues/es/license-manager-access-for-sales-channel-management-is-not-working.md b/docs/known-issues/es/license-manager-access-for-sales-channel-management-is-not-working.md
index 8fecba9db..733482752 100644
--- a/docs/known-issues/es/license-manager-access-for-sales-channel-management-is-not-working.md
+++ b/docs/known-issues/es/license-manager-access-for-sales-channel-management-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 380904
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la configuración del Gestor de Licencias, podemos seleccionar a qué recurso puede acceder el usuario. La gestión de los Canales de Venta no está dando acceso a la página de configuración de los Canales de Venta: `account.myvtex.com/admin/Site/Store.aspx`.
diff --git a/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md b/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
index ff26a8300..d2e1b7ff9 100644
--- a/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
+++ b/docs/known-issues/es/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
@@ -18,9 +18,7 @@ internalReference: 886486
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al exportar valores de servicios de una categoría específica en el admin el resultado solo trae los servicios activos. No permitiendo al comerciante activar servicios previamente inactivos por hoja de cálculo.
diff --git a/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index e757008ef..08a43cd30 100644
--- a/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/es/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -18,9 +18,7 @@ internalReference: 544034
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Enlace "¿Por qué llenar VTEX Categoría Global?" en la configuración de la categoría sólo funciona la apertura en una nueva pestaña. tratando de abrir con sólo hacer clic en el enlace se redirige a una página de error.
diff --git a/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
index c22542260..c62a34213 100644
--- a/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
+++ b/docs/known-issues/es/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -18,9 +18,7 @@ internalReference: 654951
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza el catálogo graphQL y se traduce la URL utilizando el linkId el rewriter debería almacenar el linkId, pero no está sucediendo: https://developers.vtex.com/docs/guides/catalog-internationalization
diff --git a/docs/known-issues/es/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md b/docs/known-issues/es/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md
index 8e50f9bd2..33c26f581 100644
--- a/docs/known-issues/es/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md
+++ b/docs/known-issues/es/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md
@@ -18,9 +18,7 @@ internalReference: 578649
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El ListPrice de un carrito interactúa con el precio expuesto para mostrar un precio antiguo frente al actual, en una cuestión de resaltar los descuentos.
diff --git a/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md b/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md
index de72abfed..a6f304e43 100644
--- a/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md
+++ b/docs/known-issues/es/locale-switcher-doesnt-work-in-myvtex-environment.md
@@ -18,9 +18,7 @@ internalReference: 778306
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Locale Switcher no funciona en el entorno myvtex sin configurar explícitamente el espacio de trabajo/entorno, pero no hay impacto en el sitio web. Este comportamiento afecta a la navegación sólo en myvtex y gestión de contenidos para diferentes idiomas.
diff --git a/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md b/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md
index 1e2dc072e..4050d86f9 100644
--- a/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md
+++ b/docs/known-issues/es/login-preference-with-password-cannot-be-undone-in-admin.md
@@ -18,9 +18,7 @@ internalReference: 1020548
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario se conecta a la plataforma VTEX por primera vez (Admin), se le pide que elija su preferencia de inicio de sesión para la próxima vez que se conecte. A continuación, puede elegir entre introducir su dirección de correo electrónico y contraseña, o introducir un código que se le enviará a su dirección de correo electrónico;
diff --git a/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md b/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md
index 93a80d833..78e9c1031 100644
--- a/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md
+++ b/docs/known-issues/es/logistics-inventory-full-access-permission-did-not-work-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 482353
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md b/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
index de7271699..310667bf8 100644
--- a/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
+++ b/docs/known-issues/es/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
@@ -18,9 +18,7 @@ internalReference: 553080
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md b/docs/known-issues/es/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md
index a358eb1b4..0924f0b5f 100644
--- a/docs/known-issues/es/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md
+++ b/docs/known-issues/es/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md
@@ -18,9 +18,7 @@ internalReference: 514551
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md b/docs/known-issues/es/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md
index a7b703d07..b7389ea28 100644
--- a/docs/known-issues/es/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md
+++ b/docs/known-issues/es/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md
@@ -18,9 +18,7 @@ internalReference: 545331
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Incluso con los registros de transacciones que informan de que se ha realizado el contracargo, se ha producido un error en la entidad adquirente.
diff --git a/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md b/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
index afc967f4e..faac60544 100644
--- a/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
+++ b/docs/known-issues/es/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
@@ -18,9 +18,7 @@ internalReference: 844192
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La ventana emergente de autenticación entra en bucle cuando la primera condición de pago tiene `requiresAuthentication: true`. Continuar la compra sólo será posible si se recarga la página.
diff --git a/docs/known-issues/es/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md b/docs/known-issues/es/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md
index b078fbf2f..d593707f6 100644
--- a/docs/known-issues/es/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md
+++ b/docs/known-issues/es/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md
@@ -18,19 +18,13 @@ internalReference: 373868
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/loss-of-content-created-via-site-editor-from-cms-migration.md b/docs/known-issues/es/loss-of-content-created-via-site-editor-from-cms-migration.md
index 84e6e3c65..f18840b31 100644
--- a/docs/known-issues/es/loss-of-content-created-via-site-editor-from-cms-migration.md
+++ b/docs/known-issues/es/loss-of-content-created-via-site-editor-from-cms-migration.md
@@ -18,9 +18,7 @@ internalReference: 610533
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/magalu-order-not-created-in-oms-and-without-log-in-bridge.md b/docs/known-issues/es/magalu-order-not-created-in-oms-and-without-log-in-bridge.md
index ee9b3780c..7142cf7dd 100644
--- a/docs/known-issues/es/magalu-order-not-created-in-oms-and-without-log-in-bridge.md
+++ b/docs/known-issues/es/magalu-order-not-created-in-oms-and-without-log-in-bridge.md
@@ -18,9 +18,7 @@ internalReference: 667547
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index a1e9b149a..25beddca1 100644
--- a/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/es/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -18,9 +18,7 @@ internalReference: 707113
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los pedidos no se han creado en OMS+Bridge y en el registro aparece el error: `"Object reference not set to an instance of an object"`.
diff --git a/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md b/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
index b0dbc2c3a..b2f80bbce 100644
--- a/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
+++ b/docs/known-issues/es/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 689151
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos skus se están integrando con especificaciones de otro Marketplace.
diff --git a/docs/known-issues/es/magazine-luiza-adjust-plaintextdescription-specification.md b/docs/known-issues/es/magazine-luiza-adjust-plaintextdescription-specification.md
index 1fbde9287..a9abb36eb 100644
--- a/docs/known-issues/es/magazine-luiza-adjust-plaintextdescription-specification.md
+++ b/docs/known-issues/es/magazine-luiza-adjust-plaintextdescription-specification.md
@@ -18,9 +18,7 @@ internalReference: 754022
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md b/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
index bad604b94..a7189461e 100644
--- a/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
+++ b/docs/known-issues/es/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
@@ -18,9 +18,7 @@ internalReference: 721951
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Necesitamos revisar el flujo y entender por qué órdenes como `"Magalu Entregas/FOB"` están siendo integradas con` selectedSla = "Convencional"` por ejemplo.
diff --git a/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md b/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md
index 7a1226669..2982cc047 100644
--- a/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md
+++ b/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md
@@ -18,9 +18,7 @@ internalReference: 792618
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El pedido se canceló en el mercado, pero en OMS se canceló y sigue en el estado "Esperando autorización para envío"
diff --git a/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md b/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
index b92ae7796..d1fd70296 100644
--- a/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
+++ b/docs/known-issues/es/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
@@ -18,9 +18,7 @@ internalReference: 865926
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Orden cancelada en marketplace no actualiza estado en VTEX
diff --git a/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 270196332..cb4af163a 100644
--- a/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/es/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -18,9 +18,7 @@ internalReference: 777298
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos no se han creado en OMS+Bridge y en el log aparece el error: `"Object reference not set to an instance of an object"`.
diff --git a/docs/known-issues/es/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md b/docs/known-issues/es/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md
index 14e251715..f4841cc65 100644
--- a/docs/known-issues/es/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md
+++ b/docs/known-issues/es/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md
@@ -18,9 +18,7 @@ internalReference: 823443
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos con estado APROBADO en el mercado no están siendo aprobados en VTEX
diff --git a/docs/known-issues/es/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md b/docs/known-issues/es/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md
index f2c986665..374b27a48 100644
--- a/docs/known-issues/es/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md
+++ b/docs/known-issues/es/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 827440
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos no están actualizando el estado a `DELIVERED` en el mercado
diff --git a/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md b/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md
index 3abf82aeb..0534918ab 100644
--- a/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md
+++ b/docs/known-issues/es/magazine-luiza-some-skus-do-not-update-price.md
@@ -18,9 +18,7 @@ internalReference: 882919
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Necesitamos entender por qué algunos skus no actualizan el precio en el marketplace.
diff --git a/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md b/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
index cf1042f68..70bdf43bb 100644
--- a/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
+++ b/docs/known-issues/es/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
@@ -18,9 +18,7 @@ internalReference: 856984
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el paso de seguimiento algunos pedidos están devolviendo el siguiente error `"Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"`
diff --git a/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md b/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
index f9c6b584e..a5042e791 100644
--- a/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
+++ b/docs/known-issues/es/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
@@ -18,9 +18,7 @@ internalReference: 780767
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una subcuenta está procesando transacciones, el cuerpo de la solicitud está enviando la propiedad "merchantName" con el nombre de la cuenta principal. En algunos casos, debido a este comportamiento, el conector no puede autorizar las transacciones por su parte, provocando la pérdida de pedidos.
diff --git a/docs/known-issues/es/mandatory-service-working-as-optional.md b/docs/known-issues/es/mandatory-service-working-as-optional.md
index b59c55aa9..55ed3502b 100644
--- a/docs/known-issues/es/mandatory-service-working-as-optional.md
+++ b/docs/known-issues/es/mandatory-service-working-as-optional.md
@@ -18,9 +18,7 @@ internalReference: 872411
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear un servicio el comerciante puede elegir si va a ser un campo obligatorio en el pago o no.
diff --git a/docs/known-issues/es/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md b/docs/known-issues/es/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md
index d45872f0d..16b5388a1 100644
--- a/docs/known-issues/es/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md
+++ b/docs/known-issues/es/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md
@@ -18,9 +18,7 @@ internalReference: 522293
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se supone que los productos con especificaciones obligatorias no están activos si al menos una de estas especificaciones no está cumplida o comprobada.
diff --git a/docs/known-issues/es/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md b/docs/known-issues/es/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md
index 80546fc28..feb6b9198 100644
--- a/docs/known-issues/es/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md
+++ b/docs/known-issues/es/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md
@@ -18,9 +18,7 @@ internalReference: 627719
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La entrada "manualPrice" en el carrito está restringida a trabajar con la precisión decimal de 2 dígitos. Si la tienda utiliza sólo uno o ningún decimal, el campo de entrada no funcionará correctamente.
diff --git a/docs/known-issues/es/manual-sorting-of-collections-doesnt-work-as-expected.md b/docs/known-issues/es/manual-sorting-of-collections-doesnt-work-as-expected.md
index a45090b8d..d2b79922a 100644
--- a/docs/known-issues/es/manual-sorting-of-collections-doesnt-work-as-expected.md
+++ b/docs/known-issues/es/manual-sorting-of-collections-doesnt-work-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 295245
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La ordenación manual de las colecciones no funciona como se esperaba. Hay dos maneras de ordenar las SKUs utilizando una colección:
diff --git a/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md b/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
index 9b2d7f0f6..11d2d8f86 100644
--- a/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
+++ b/docs/known-issues/es/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
@@ -18,9 +18,7 @@ internalReference: 936458
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza la función de cupones múltiples y hay cupones y utms, o 'marketingTags', en el 'orderForm', no se guarda ningún 'marketingData' en el pedido.
diff --git a/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md b/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md
index f12be8177..154a5e262 100644
--- a/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md
+++ b/docs/known-issues/es/marketingtags-with-null-value-when-campaign-audience-is-matched.md
@@ -18,9 +18,7 @@ internalReference: 1052895
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una cuenta tiene un público de campaña y se hace coincidir con un usuario logueado, el checkout utiliza la información registrada en la sesión, que sólo tiene el id de la campaña. En `marketingTags`, debería tener el nombre de la campaña, pero es `null` ya que no hay información disponible en la sesión.
diff --git a/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md b/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
index b3a4b17ae..49ffccf1a 100644
--- a/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
+++ b/docs/known-issues/es/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
@@ -18,9 +18,7 @@ internalReference: 1032473
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las capas de Marketplace y Fulfillment pueden esperar valores diferentes para el pedido, impidiendo la finalización de la compra.
diff --git a/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
index 116085e9b..d31752e47 100644
--- a/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
+++ b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
@@ -18,9 +18,7 @@ internalReference: 932657
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la cuenta tiene configurado isMarketplaceResponsibleForTaxes, la solicitud del centro de impuestos no tiene en cuenta los precios manuales para los descuentos de artículos.
diff --git a/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
index 7280d4fa6..8a178eaa0 100644
--- a/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
+++ b/docs/known-issues/es/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
@@ -18,9 +18,7 @@ internalReference: 945580
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la cuenta tiene configurado isMarketplaceResponsibleForTaxes, la solicitud del hub de impuestos no considera algunos tipos de descuento: Nominal, Porcentaje y Precio máximo por artículo. Esto afecta al cálculo de impuestos, y el precio final es más alto de lo esperado.
diff --git a/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md b/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md
index 1079a0b20..bb987f0e3 100644
--- a/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md
+++ b/docs/known-issues/es/mastercard-credit-card-transactions-are-being-processed-as-visa.md
@@ -18,9 +18,7 @@ internalReference: 1026263
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas transacciones se están registrando erróneamente bajo la marca Visa, cuando en realidad las tarjetas son Mastercard. Este problema se produce específicamente con tarjetas nuevas, aunque podemos verificar que el BIN de la tarjeta coincide correctamente con el regex del validador para la marca correcta.
diff --git a/docs/known-issues/es/masterdata-export-download-link-unavailable.md b/docs/known-issues/es/masterdata-export-download-link-unavailable.md
index 99dbb45f5..946ad72c8 100644
--- a/docs/known-issues/es/masterdata-export-download-link-unavailable.md
+++ b/docs/known-issues/es/masterdata-export-download-link-unavailable.md
@@ -18,9 +18,7 @@ internalReference: 613864
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, para las entidades de datos con varios campos, cuando se intenta exportar una hoja y descargarla, tanto por correo electrónico como directamente a través de la interfaz de usuario, el enlace de descarga no guarda el archivo en el navegador.
diff --git a/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
index d5b03dd96..73f67fabe 100644
--- a/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
+++ b/docs/known-issues/es/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -18,9 +18,7 @@ internalReference: 506660
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API Match Multiple Received SKUs (doc: https://developers.vtex.com/vtex-rest-api/reference/match-received-skus#matchmultiple) está devolviendo el mensaje de error "Invalid sellerId" para cualquier intento de aprobación de nuevos productos, incluso si el vendedor está correctamente activo en el marketplace.
diff --git a/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md b/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md
index 662845a7e..46db63365 100644
--- a/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md
+++ b/docs/known-issues/es/matcher-converting-height-width-weight-and-length-to-01.md
@@ -18,9 +18,7 @@ internalReference: 886168
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el Matcher procesa los skus en el módulo de sugerencias del marketplace las infos de Altura, Anchura, Peso y Longitud se están poniendo a 0.1 en lugar de respetar los valores enviados por el vendedor.
diff --git a/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md b/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
index 9585a5717..76a6edae6 100644
--- a/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
+++ b/docs/known-issues/es/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 736164
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al integrar productos que tienen caracteres especiales en el nombre, como `. - + # /` , Matcher da una puntuación del 50% y hace que los productos se queden en Pendiente. Con esto, los productos dependen de la aprobación manual o vía API.
diff --git a/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md b/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md
index 976545fc2..66b6283d4 100644
--- a/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md
+++ b/docs/known-issues/es/max-shipping-discount-not-updating-pricetags.md
@@ -18,9 +18,7 @@ internalReference: 904190
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
index 7eebfd98c..14904614d 100644
--- a/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
+++ b/docs/known-issues/es/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -18,9 +18,7 @@ internalReference: 1073080
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar un descuento de más por menos junto con otra promoción que utiliza el "máximo de artículos por carrito" para el mismo artículo, acumulándose ambos, se produce un descuento incorrecto, superando la configuración inicialmente configurada.
diff --git a/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md b/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
index 65a1e8fbd..60e3e9030 100644
--- a/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
+++ b/docs/known-issues/es/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
@@ -18,9 +18,7 @@ internalReference: 325273
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La configuración de la cantidad máxima de un mismo artículo en el carrito no puede ser modificada por las cuentas franquiciadas (vendedor whitelabel), ya que tiene lugar en una pantalla heredada del catálogo (/admin/Site/ConfigForm.aspx) - módulo que se elimina de las cuentas franquiciadas, ya que heredan los productos de la cuenta padre.
diff --git a/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
index 04fba0158..b617d0420 100644
--- a/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
+++ b/docs/known-issues/es/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -18,9 +18,7 @@ internalReference: 852966
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md b/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
index f135c33d8..c3c1b6969 100644
--- a/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
+++ b/docs/known-issues/es/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
@@ -18,9 +18,7 @@ internalReference: 791380
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md b/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
index 08856a5d9..bbd3a7d99 100644
--- a/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
+++ b/docs/known-issues/es/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
@@ -18,9 +18,7 @@ internalReference: 660703
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md b/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md
index 4adbcd7fb..50bd8746a 100644
--- a/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md
+++ b/docs/known-issues/es/meli-automatic-messages-mercado-livre-messages.md
@@ -18,9 +18,7 @@ internalReference: 615164
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md b/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md
index b81604d00..7b10ab594 100644
--- a/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md
+++ b/docs/known-issues/es/meli-bridge-orders-menu-not-showing-the-orderid-information.md
@@ -18,9 +18,7 @@ internalReference: 881733
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md b/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
index db4f8bc68..387ebc433 100644
--- a/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
+++ b/docs/known-issues/es/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
@@ -18,9 +18,7 @@ internalReference: 910371
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-buybox-ads-not-being-linked-to-bridge-products.md b/docs/known-issues/es/meli-buybox-ads-not-being-linked-to-bridge-products.md
index 6ceab9e72..00d52e95c 100644
--- a/docs/known-issues/es/meli-buybox-ads-not-being-linked-to-bridge-products.md
+++ b/docs/known-issues/es/meli-buybox-ads-not-being-linked-to-bridge-products.md
@@ -18,9 +18,7 @@ internalReference: 780961
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-customdata-paymentfield.md b/docs/known-issues/es/meli-customdata-paymentfield.md
index 93b41a468..34f78e1d3 100644
--- a/docs/known-issues/es/meli-customdata-paymentfield.md
+++ b/docs/known-issues/es/meli-customdata-paymentfield.md
@@ -18,9 +18,7 @@ internalReference: 542992
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-error-importing-some-orders.md b/docs/known-issues/es/meli-error-importing-some-orders.md
index a039e19e3..5f91014ef 100644
--- a/docs/known-issues/es/meli-error-importing-some-orders.md
+++ b/docs/known-issues/es/meli-error-importing-some-orders.md
@@ -18,9 +18,7 @@ internalReference: 664351
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 identificamos que estamos haciendo la división por tipo de listado, así que cuando tratamos de dividir, y es Cumplimiento, no lo deja.
diff --git a/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md b/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
index a196f6ee9..a6985046c 100644
--- a/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
+++ b/docs/known-issues/es/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
@@ -18,9 +18,7 @@ internalReference: 664010
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos skus tienen un error en la integración` "La cadena de entrada no estaba en un formato correcto"`.
diff --git a/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md b/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md
index d640b558b..1966a6abb 100644
--- a/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md
+++ b/docs/known-issues/es/meli-error-while-sending-the-order-tracking.md
@@ -18,9 +18,7 @@ internalReference: 764885
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md b/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md
index 6581e05d8..2286624b0 100644
--- a/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md
+++ b/docs/known-issues/es/meli-freight-quotation-for-multiple-officialstoreids.md
@@ -18,9 +18,7 @@ internalReference: 978358
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente tenemos un problema con la integración de MELI con respecto a la API de cotización de flete de MELI, esto se aplica sólo para los vendedores que utilizan múltiples officialStoreIDs en MELI, pero utilizando sólo una cuenta en VTEX utilizando el mismo sellerID en MELI
diff --git a/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md b/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md
index 22596b670..5ab48db5f 100644
--- a/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md
+++ b/docs/known-issues/es/meli-full-orders-not-creating-invoice-in-vtex.md
@@ -18,9 +18,7 @@ internalReference: 976614
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-images-limitation.md b/docs/known-issues/es/meli-images-limitation.md
index 33b5c2643..2e1d1afe1 100644
--- a/docs/known-issues/es/meli-images-limitation.md
+++ b/docs/known-issues/es/meli-images-limitation.md
@@ -18,9 +18,7 @@ internalReference: 571539
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md b/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md
index 10b1cd455..c6a234f84 100644
--- a/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md
+++ b/docs/known-issues/es/meli-incorrect-value-when-client-has-coupon-on-meli.md
@@ -18,9 +18,7 @@ internalReference: 969297
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
index 13eeda84b..b3cf71fee 100644
--- a/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
+++ b/docs/known-issues/es/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -18,9 +18,7 @@ internalReference: 873998
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md b/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
index c02fb0fb8..bc75bd028 100644
--- a/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
+++ b/docs/known-issues/es/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
@@ -18,9 +18,7 @@ internalReference: 925139
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-integration-missing-billingaddress.md b/docs/known-issues/es/meli-integration-missing-billingaddress.md
index 573b059fa..340517227 100644
--- a/docs/known-issues/es/meli-integration-missing-billingaddress.md
+++ b/docs/known-issues/es/meli-integration-missing-billingaddress.md
@@ -18,9 +18,7 @@ internalReference: 771418
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
index b6a30624e..1b9031993 100644
--- a/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/es/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -18,9 +18,7 @@ internalReference: 826566
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-kit-stock-integration.md b/docs/known-issues/es/meli-kit-stock-integration.md
index 6193ddf08..ba1cf5004 100644
--- a/docs/known-issues/es/meli-kit-stock-integration.md
+++ b/docs/known-issues/es/meli-kit-stock-integration.md
@@ -18,9 +18,7 @@ internalReference: 489220
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Necesitamos investigar y solucionar el problema al enviar el balance de stock a MELI cuando el artículo es un KIT. Envíe el saldo de existencias del KIT en lugar de las existencias de la SKU.
diff --git a/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md b/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md
index ec0be5dbd..65d6504c0 100644
--- a/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md
+++ b/docs/known-issues/es/meli-mapper-incorrectly-sending-product-specification-as-variation.md
@@ -18,9 +18,7 @@ internalReference: 851021
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-oms-label-printing.md b/docs/known-issues/es/meli-oms-label-printing.md
index ccf8906aa..d653be52b 100644
--- a/docs/known-issues/es/meli-oms-label-printing.md
+++ b/docs/known-issues/es/meli-oms-label-printing.md
@@ -18,9 +18,7 @@ internalReference: 546542
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Estamos teniendo algunos problemas al hacer clic directamente dentro del botón "etiqueta de entrega", para los pedidos de Mercado Livre dentro de OMS.
diff --git a/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md b/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
index d05cf16d9..6d4b31ff6 100644
--- a/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
+++ b/docs/known-issues/es/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
@@ -18,9 +18,7 @@ internalReference: 977453
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-plaintextdescriptionmeli-not-working.md b/docs/known-issues/es/meli-plaintextdescriptionmeli-not-working.md
index 4b65d6a57..b26d1b7d6 100644
--- a/docs/known-issues/es/meli-plaintextdescriptionmeli-not-working.md
+++ b/docs/known-issues/es/meli-plaintextdescriptionmeli-not-working.md
@@ -18,9 +18,7 @@ internalReference: 555122
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-promotion-center-not-linking-skus-to-promotion.md b/docs/known-issues/es/meli-promotion-center-not-linking-skus-to-promotion.md
index f0c6684ca..bddefda26 100644
--- a/docs/known-issues/es/meli-promotion-center-not-linking-skus-to-promotion.md
+++ b/docs/known-issues/es/meli-promotion-center-not-linking-skus-to-promotion.md
@@ -18,9 +18,7 @@ internalReference: 801348
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-promotion-center.md b/docs/known-issues/es/meli-promotion-center.md
index 50033cce2..8f99f52c0 100644
--- a/docs/known-issues/es/meli-promotion-center.md
+++ b/docs/known-issues/es/meli-promotion-center.md
@@ -18,9 +18,7 @@ internalReference: 600922
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-promotions-ui-error.md b/docs/known-issues/es/meli-promotions-ui-error.md
index 1213f7f0c..c4b0790a4 100644
--- a/docs/known-issues/es/meli-promotions-ui-error.md
+++ b/docs/known-issues/es/meli-promotions-ui-error.md
@@ -18,9 +18,7 @@ internalReference: 797143
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md b/docs/known-issues/es/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md
index 4fc07b33f..e767c97b6 100644
--- a/docs/known-issues/es/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md
+++ b/docs/known-issues/es/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md
@@ -18,9 +18,7 @@ internalReference: 557293
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md b/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md
index 87b95b7f7..d46bc9ad7 100644
--- a/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md
+++ b/docs/known-issues/es/meli-size-chart-not-working-for-sizes-with-letters.md
@@ -18,9 +18,7 @@ internalReference: 867262
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md b/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md
index 54182f444..06ad2bb0f 100644
--- a/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md
+++ b/docs/known-issues/es/meli-sizechart-issue-attribute-not-valid.md
@@ -18,9 +18,7 @@ internalReference: 996639
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md b/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
index daa25e89a..a9ab5409b 100644
--- a/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
+++ b/docs/known-issues/es/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
@@ -18,9 +18,7 @@ internalReference: 657515
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos skus en el Mercado Livre están registrando error: "Referencia de objeto no establecida a una instancia de un objeto".
diff --git a/docs/known-issues/es/meli-update-stockprice-issue.md b/docs/known-issues/es/meli-update-stockprice-issue.md
index 757a24329..26073f81d 100644
--- a/docs/known-issues/es/meli-update-stockprice-issue.md
+++ b/docs/known-issues/es/meli-update-stockprice-issue.md
@@ -18,9 +18,7 @@ internalReference: 939329
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md b/docs/known-issues/es/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md
index 923e420ac..4bc2f1b7c 100644
--- a/docs/known-issues/es/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md
+++ b/docs/known-issues/es/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md
@@ -18,9 +18,7 @@ internalReference: 758331
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md b/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
index fff66d6ba..e6fcbbc8e 100644
--- a/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
+++ b/docs/known-issues/es/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
@@ -18,9 +18,7 @@ internalReference: 1042779
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 AD BuyBox no actualiza shipping_mode para ME2
diff --git a/docs/known-issues/es/mercado-livre-attribute-size-is-missing.md b/docs/known-issues/es/mercado-livre-attribute-size-is-missing.md
index 6b794e377..ffc51d6d0 100644
--- a/docs/known-issues/es/mercado-livre-attribute-size-is-missing.md
+++ b/docs/known-issues/es/mercado-livre-attribute-size-is-missing.md
@@ -18,9 +18,7 @@ internalReference: 658473
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
index 67342d0a4..0791790e7 100644
--- a/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
+++ b/docs/known-issues/es/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
@@ -18,9 +18,7 @@ internalReference: 1053742
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Error en el flujo de actualización sku no se está registrando en el puente
diff --git a/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md b/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
index 4ecc7e18f..d2fb1ed4d 100644
--- a/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
+++ b/docs/known-issues/es/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
@@ -18,9 +18,7 @@ internalReference: 1001903
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente tenemos un problema que solo afecta a la visibilidad de algunos Pedidos MELI, lo que ocurre es que actualmente estamos registrando el ShipmentID en el menu del puente de pedidos, pero en algunos mensajes de error falta el OrderID, y es necesario para algunos casos ya que el orderID es la informacion que los vendedores tienen en el Portal MELI
diff --git a/docs/known-issues/es/mercado-livre-mapper-attribute-size.md b/docs/known-issues/es/mercado-livre-mapper-attribute-size.md
index e0618f551..5cbcbfa4c 100644
--- a/docs/known-issues/es/mercado-livre-mapper-attribute-size.md
+++ b/docs/known-issues/es/mercado-livre-mapper-attribute-size.md
@@ -18,9 +18,7 @@ internalReference: 592577
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md b/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md
index a6bca9d9b..8c5f9855b 100644
--- a/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md
+++ b/docs/known-issues/es/mercado-livre-remove-underreview-validation-in-update-sku.md
@@ -18,9 +18,7 @@ internalReference: 890658
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
index c3b68a55b..32ad656c8 100644
--- a/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
+++ b/docs/known-issues/es/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
@@ -18,9 +18,7 @@ internalReference: 1069692
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Contexto correcto: En algunos casos, el vendedor no puede integrar el SKU, ya que el mensaje de error con el motivo por el que se moderó el artículo no aparece correctamente en Bridge.
diff --git a/docs/known-issues/es/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md b/docs/known-issues/es/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md
index c8f57c5a6..2ff1c0907 100644
--- a/docs/known-issues/es/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md
+++ b/docs/known-issues/es/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md
@@ -18,9 +18,7 @@ internalReference: 778611
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si el proceso de pago del cliente envía datos de usuario sin la validación adecuada, como un número de teléfono con menos de tres dígitos, estos datos se pasan a la pasarela tal cual, lo que puede provocar errores inesperados durante el procesamiento. Por ejemplo, nuestro analizador puede lanzar una excepción y cancelar la transacción.
diff --git a/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
index 29f44a94f..2794cfcf8 100644
--- a/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
+++ b/docs/known-issues/es/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -18,9 +18,7 @@ internalReference: 1062457
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las reglas de merchandising no se aplican a la faceta "productClusterIds". Esto ocurre porque esta faceta tiene el comportamiento especial de ordenar los productos por el orden de colección en lugar de por relevancia y reglas de merchandising.
diff --git a/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md b/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
index 563a61aa5..bf0dba3db 100644
--- a/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
+++ b/docs/known-issues/es/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
@@ -18,9 +18,7 @@ internalReference: 906509
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Por alguna razón, al intentar abrir una nueva cuenta para clientes específicos a través de la API, devuelve el siguiente error:
diff --git a/docs/known-issues/es/merchants-are-not-receiving-the-fixed-price-report.md b/docs/known-issues/es/merchants-are-not-receiving-the-fixed-price-report.md
index 59112053b..c350496a9 100644
--- a/docs/known-issues/es/merchants-are-not-receiving-the-fixed-price-report.md
+++ b/docs/known-issues/es/merchants-are-not-receiving-the-fixed-price-report.md
@@ -18,9 +18,7 @@ internalReference: 674353
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md b/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md
index 83b49107e..b4f8fd9e4 100644
--- a/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md
+++ b/docs/known-issues/es/message-freight-value-has-changed-is-shown-incorrectly.md
@@ -18,9 +18,7 @@ internalReference: 775515
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al eliminar un artículo del carrito, se muestra el mensaje "El valor del flete ha cambiado" aunque el Total de envío sea el mismo después del cambio.
diff --git a/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md b/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md
index f92dff269..e528bbecd 100644
--- a/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md
+++ b/docs/known-issues/es/messages-app-taking-too-long-to-return-the-informations.md
@@ -18,9 +18,7 @@ internalReference: 567305
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el proceso de indexación, llamamos a la aplicación de mensajes para guardar la información traducida de los productos, el principal problema es que las peticiones están tardando demasiado en volver y con eso, algunas tiendas que tienen muchos idiomas no indexan completamente o tienen sus indexaciones atascadas.
diff --git a/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md b/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md
index fb468a5b4..a1ad6468f 100644
--- a/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md
+++ b/docs/known-issues/es/metatagdescription-field-cannot-be-deleted-through-admin.md
@@ -18,9 +18,7 @@ internalReference: 979691
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md b/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md
index 5952713f8..820fc74a8 100644
--- a/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md
+++ b/docs/known-issues/es/minicart-coupon-error-messages-only-appear-after-a-second-try.md
@@ -18,9 +18,7 @@ internalReference: 938379
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los mensajes de error de cupón en Minicart no aparecerán la primera vez que intente un cupón, incluso si no existe.
diff --git a/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md b/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md
index 05d6b733d..ad7baf554 100644
--- a/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md
+++ b/docs/known-issues/es/minicart-does-not-show-sku-specs-in-b2b-scenario.md
@@ -18,9 +18,7 @@ internalReference: 687308
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se añade un artículo al minicart en una tienda B2B, no se presenta la información relacionada con sus especificaciones, registradas en el Catálogo.
diff --git a/docs/known-issues/es/minicart-error-when-updating-promotion.md b/docs/known-issues/es/minicart-error-when-updating-promotion.md
index e8a091a8f..935124440 100644
--- a/docs/known-issues/es/minicart-error-when-updating-promotion.md
+++ b/docs/known-issues/es/minicart-error-when-updating-promotion.md
@@ -18,9 +18,7 @@ internalReference: 552633
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index bdd149176..858924382 100644
--- a/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/es/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -18,9 +18,7 @@ internalReference: 452053
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Al utilizar la mutación "_addToCart"_ del "_checkout-graphql"_ en un carrito en el que ya se ha añadido un determinado artículo sin "_options_", al intentar incluirlo de nuevo, esta vez con "_options_", no funcionará correctamente. La mutación no registrará las "_opciones_" enviadas y además devolverá un error si están relacionadas con la información de "_suscripción_".
 
diff --git a/docs/known-issues/es/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md b/docs/known-issues/es/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md
index 67da3462b..72c948d22 100644
--- a/docs/known-issues/es/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md
+++ b/docs/known-issues/es/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md
@@ -18,9 +18,7 @@ internalReference: 709971
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay más de una condición de pago configurada para un sistema de pago, y una condición de pago distinta de la que tiene la opción de pago a plazos 1x está configurada como predeterminada, la opción de pago a plazos 1x no aparece en la página de pago. En estos casos, sólo se elimina de la página de pago la opción del plazo 1x.
diff --git a/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md b/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
index 90991c755..aec9441a1 100644
--- a/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
+++ b/docs/known-issues/es/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
@@ -18,9 +18,7 @@ internalReference: 514335
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Ha habido casos en los que ciertas transacciones han sido rechazadas durante el análisis antifraude debido al valor nulo en el campo `minicart.buyer.id`. Por lo tanto, se espera que el campo `minicart.buyer.id` se envíe desde la caja a la pasarela a través de `sendAdditionalData`. Sin embargo, de acuerdo con la arquitectura actual de la caja, no hay ningún requisito específico para proporcionar este campo en `sendAdditionalData`, y su definición puede o no estar disponible en una etapa posterior.
diff --git a/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md b/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
index 3301482be..f6b15e5b0 100644
--- a/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
+++ b/docs/known-issues/es/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 974840
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Búsqueda Inteligente no aplica la traducción al nombre del filtro/facet "precio" para idiomas adicionales cuando se consulta a través de REST API.
diff --git a/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md b/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
index 583a3f60f..b615ab90e 100644
--- a/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
+++ b/docs/known-issues/es/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
@@ -18,9 +18,7 @@ internalReference: 488339
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un escenario en el que hay modales configurados OK en SKU y Shipping Police también y la simulación está mostrando un problema en la configuración modal.
diff --git a/docs/known-issues/es/modal-values-with-different-texts-between-api-and-logistics-ui.md b/docs/known-issues/es/modal-values-with-different-texts-between-api-and-logistics-ui.md
index 1591286df..182a76bf9 100644
--- a/docs/known-issues/es/modal-values-with-different-texts-between-api-and-logistics-ui.md
+++ b/docs/known-issues/es/modal-values-with-different-texts-between-api-and-logistics-ui.md
@@ -18,9 +18,7 @@ internalReference: 775800
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la pantalla de Ajustes Generales del módulo de logística, al configurar los modos disponibles para usar en el catálogo, el usuario verá una lista de valores disponibles, estos valores al ser seleccionados habilitan una opción de selección en la pantalla de Ajustes Avanzados del SKU, pero estos valores no son traducidos a la API y por lo tanto los valores de la UI del catálogo pueden no tener cadenas iguales al valor de la UI de logística, ya que el valor mostrado en la UI del catálogo es exactamente el valor de la API.
diff --git a/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md b/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md
index dd5d7e535..ede43d43e 100644
--- a/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md
+++ b/docs/known-issues/es/modals-deprecated-divergences-setup-shipping-policy.md
@@ -18,9 +18,7 @@ internalReference: 445866
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un escenario con respecto a los modales usados y obsoletos que no coinciden.
diff --git a/docs/known-issues/es/moving-categories-does-not-update-the-department-id-on-the-products.md b/docs/known-issues/es/moving-categories-does-not-update-the-department-id-on-the-products.md
index b4ec818f9..c1926fad9 100644
--- a/docs/known-issues/es/moving-categories-does-not-update-the-department-id-on-the-products.md
+++ b/docs/known-issues/es/moving-categories-does-not-update-the-department-id-on-the-products.md
@@ -18,9 +18,7 @@ internalReference: 316694
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Mover categorías en el árbol de categorías, por ejemplo mover un departamento a otra categoría no actualiza el ID del departamento en los Productos.
diff --git a/docs/known-issues/es/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md b/docs/known-issues/es/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md
index 1f7a1e23d..688ee823b 100644
--- a/docs/known-issues/es/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md
+++ b/docs/known-issues/es/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md
@@ -18,9 +18,7 @@ internalReference: 367136
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, esta funcionalidad puede provocar incoherencias en el banco de datos de su árbol de categorías, según el tipo de movimiento. Por lo tanto, no se recomienda esta funcionalidad hasta que se pueda remediar.
diff --git a/docs/known-issues/es/multiple-sku-promotion-api-not-working.md b/docs/known-issues/es/multiple-sku-promotion-api-not-working.md
index 8dd440cbc..fe89a3cd3 100644
--- a/docs/known-issues/es/multiple-sku-promotion-api-not-working.md
+++ b/docs/known-issues/es/multiple-sku-promotion-api-not-working.md
@@ -18,9 +18,7 @@ internalReference: 729990
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A pesar de la información de retorno de éxito en la API y el correo electrónico, la promoción no se crea en el administrador.
diff --git a/docs/known-issues/es/my-account-receiver-name-field-doesnt-recognize-input.md b/docs/known-issues/es/my-account-receiver-name-field-doesnt-recognize-input.md
index 9586df86a..08e4bdfb5 100644
--- a/docs/known-issues/es/my-account-receiver-name-field-doesnt-recognize-input.md
+++ b/docs/known-issues/es/my-account-receiver-name-field-doesnt-recognize-input.md
@@ -18,9 +18,7 @@ internalReference: 568527
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar registrar la primera dirección en esta cuenta, a través de "Mi Cuenta > direcciones", se muestra la información de que es "obligatorio" introducir los "Datos del Tercero Autorizado", pero incluso después de introducir esta información y hacer clic en "Anadir Dirección" la dirección no se registra y se muestra de nuevo el mensaje de que es "obligatorio", sólo después del segundo intento se guarda la dirección con éxito.
diff --git a/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md b/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
index df7f00a19..f9f4b3b46 100644
--- a/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
+++ b/docs/known-issues/es/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
@@ -18,9 +18,7 @@ internalReference: 1012542
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El pie de página de "Mis tarjetas" tiembla en la pantalla al intentar añadir una nueva tarjeta.
diff --git a/docs/known-issues/es/my-cards-is-not-working-for-some-legacy-connectors.md b/docs/known-issues/es/my-cards-is-not-working-for-some-legacy-connectors.md
index 264f2516b..bfa3b5172 100644
--- a/docs/known-issues/es/my-cards-is-not-working-for-some-legacy-connectors.md
+++ b/docs/known-issues/es/my-cards-is-not-working-for-some-legacy-connectors.md
@@ -18,9 +18,7 @@ internalReference: 373636
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar guardar una tarjeta de crédito en Mis Tarjetas dentro de la sesión de Mi Cuenta **sin haber realizado ninguna compra con esa tarjeta anteriormente** se produce un error al intentar guardar la tarjeta con un conector interno heredado.
diff --git a/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md b/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
index e63cc4dff..6811e98e9 100644
--- a/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
+++ b/docs/known-issues/es/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
@@ -18,9 +18,7 @@ internalReference: 521542
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario quiere guardar una tarjeta en MyAccount, la dirección es obligatoria y sin los datos rellenados, el botón no realiza la acción de intentar guardar la tarjeta. Pero esta regla no se aplica al campo número del formulario de dirección, que es obligatorio, sino que se puede dejar vacío y el usuario puede guardar la tarjeta sin esta validación.
diff --git a/docs/known-issues/es/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md b/docs/known-issues/es/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md
index 3633868b5..40e0c4fa4 100644
--- a/docs/known-issues/es/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md
+++ b/docs/known-issues/es/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md
@@ -18,9 +18,7 @@ internalReference: 546267
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El enlace del campo paymentLink no se está mostrando en la página de Mis Créditos, dentro de MiCuenta, a pesar de que ha sido configurado y está disponible en la página de Facturas de Crédito de Cliente, dentro de la Administración.
diff --git a/docs/known-issues/es/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md b/docs/known-issues/es/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md
index 72005d171..5b3326e65 100644
--- a/docs/known-issues/es/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md
+++ b/docs/known-issues/es/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md
@@ -18,19 +18,13 @@ internalReference: 356936
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md b/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
index 6d6a3e76a..bbdd640d3 100644
--- a/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
+++ b/docs/known-issues/es/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
@@ -18,9 +18,7 @@ internalReference: 692523
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md b/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
index a5b944aad..0725f6ac1 100644
--- a/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
+++ b/docs/known-issues/es/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
@@ -18,9 +18,7 @@ internalReference: 588046
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md b/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md
index 7def9a992..824a77eb7 100644
--- a/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md
+++ b/docs/known-issues/es/mycards-spinner-button-is-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 780667
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de hacer clic en el botón "Guardar nueva tarjeta", los usuarios esperan ver alguna respuesta indicando que algo se está procesando. Desafortunadamente, la experiencia actual es deficiente, ya que el botón no muestra la esperada animación "spinner". Esto puede ser frustrante para los usuarios y perjudica la experiencia general del usuario.
diff --git a/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md b/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
index f0a303aa8..c09c743bc 100644
--- a/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
+++ b/docs/known-issues/es/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
@@ -18,9 +18,7 @@ internalReference: 367276
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Existe la posibilidad de crear un dependiente adicional, cuando se crea una cuenta en Crédito Cliente y al hacerlo, la cuenta dependiente está mostrando un error cuando se accede a MisCréditos (dentro de Mi Cuenta)
diff --git a/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md b/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
index f7c02ef8f..d7180e997 100644
--- a/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
+++ b/docs/known-issues/es/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
@@ -18,9 +18,7 @@ internalReference: 768603
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/native-gift-card-is-adding-credit-although-it-returns-500.md b/docs/known-issues/es/native-gift-card-is-adding-credit-although-it-returns-500.md
index c51367642..43f5240a0 100644
--- a/docs/known-issues/es/native-gift-card-is-adding-credit-although-it-returns-500.md
+++ b/docs/known-issues/es/native-gift-card-is-adding-credit-although-it-returns-500.md
@@ -18,9 +18,7 @@ internalReference: 760896
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tras realizar algunas pruebas empíricas, hemos observado que la ruta /transaction de la API nativa de tarjetas regalo, devuelve en ocasiones un código de error 500 al añadir el crédito solicitado, lo cual es un comportamiento inesperado. Además, hemos observado que la solicitud está tardando más de lo esperado en recibir una respuesta, lo que indica un comportamiento de tiempo de espera. Como resultado, no existe un bloqueo efectivo que garantice que el saldo de la tarjeta no se abonará en este caso.
diff --git a/docs/known-issues/es/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md b/docs/known-issues/es/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md
index f220dc52b..f83322c63 100644
--- a/docs/known-issues/es/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md
+++ b/docs/known-issues/es/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md
@@ -18,9 +18,7 @@ internalReference: 597771
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/negative-amounts-in-split-recipients.md b/docs/known-issues/es/negative-amounts-in-split-recipients.md
index 3fa607bd4..2ca86a3c4 100644
--- a/docs/known-issues/es/negative-amounts-in-split-recipients.md
+++ b/docs/known-issues/es/negative-amounts-in-split-recipients.md
@@ -18,9 +18,7 @@ internalReference: 388580
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un escenario de Mercado con división de pagos cuando el mercado no tiene comisión en la transacción, redondear cualquiera de los valores de referencia (buyTotal o totalSellers) puede resultar en una cantidad negativa para el mercado.
diff --git a/docs/known-issues/es/new-collections-import-does-not-handle-non-existent-productid-import.md b/docs/known-issues/es/new-collections-import-does-not-handle-non-existent-productid-import.md
index 902070052..444ef4229 100644
--- a/docs/known-issues/es/new-collections-import-does-not-handle-non-existent-productid-import.md
+++ b/docs/known-issues/es/new-collections-import-does-not-handle-non-existent-productid-import.md
@@ -18,9 +18,7 @@ internalReference: 398602
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md b/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md
index 3c6c92e19..8275df8a2 100644
--- a/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md
+++ b/docs/known-issues/es/new-collections-newly-released-filter-is-not-working-for-exports.md
@@ -18,19 +18,13 @@ internalReference:
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/new-collections-page-not-loading.md b/docs/known-issues/es/new-collections-page-not-loading.md
index b903f7483..77cb677e0 100644
--- a/docs/known-issues/es/new-collections-page-not-loading.md
+++ b/docs/known-issues/es/new-collections-page-not-loading.md
@@ -18,9 +18,7 @@ internalReference: 419729
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La cuenta no ha podido cargar la página de la aplicación de colecciones, la petición `api/catalog_system/pvt/collection/search/?an=&page=1&pageSize=10&orderByAsc=false` ha devuelto 500, debido al tiempo de espera:
diff --git a/docs/known-issues/es/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md b/docs/known-issues/es/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md
index 5c4af0a65..025a1204d 100644
--- a/docs/known-issues/es/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md
+++ b/docs/known-issues/es/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md
@@ -18,9 +18,7 @@ internalReference: 620668
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 En la nueva interfaz de usuario, algunos pedidos no muestran correctamente el desglose de la entrega estimada.
 
diff --git a/docs/known-issues/es/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md b/docs/known-issues/es/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md
index 6c3eff01c..787abf1d8 100644
--- a/docs/known-issues/es/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md
+++ b/docs/known-issues/es/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md
@@ -18,9 +18,7 @@ internalReference: 646253
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md b/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
index 44731df09..eaf83091e 100644
--- a/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
+++ b/docs/known-issues/es/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
@@ -18,9 +18,7 @@ internalReference: 713480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Nueva UI no muestra el documento de identificación del cliente en los pedidos. Por ejemplo como CPF, ocurre porque la política comercial de cuentas tiene configurado otro país.
diff --git a/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md b/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
index d4b4c35a6..1610d3ed6 100644
--- a/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
+++ b/docs/known-issues/es/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
@@ -18,9 +18,7 @@ internalReference: 664838
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La nueva interfaz de usuario no muestra en la página de artículos devueltos el valor total ya facturado.
diff --git a/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md b/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
index 1d7608482..a85985920 100644
--- a/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
+++ b/docs/known-issues/es/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
@@ -18,9 +18,7 @@ internalReference: 995491
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/no-feedback-to-the-user-when-something-goes-wrong.md b/docs/known-issues/es/no-feedback-to-the-user-when-something-goes-wrong.md
index 8612a7301..d8073a9ac 100644
--- a/docs/known-issues/es/no-feedback-to-the-user-when-something-goes-wrong.md
+++ b/docs/known-issues/es/no-feedback-to-the-user-when-something-goes-wrong.md
@@ -18,19 +18,13 @@ internalReference: 339072
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md b/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
index 9b1a5dd0b..906b5cdfd 100644
--- a/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
+++ b/docs/known-issues/es/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
@@ -18,9 +18,7 @@ internalReference: 886980
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear una promoción utilizando Descuento nominal basado en fórmula, el comerciante puede utilizar las siguientes operaciones de acuerdo con esta documentación: https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV
diff --git a/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md b/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
index f705f564a..79d000e07 100644
--- a/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
+++ b/docs/known-issues/es/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 334130
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md b/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
index c2e7fee98..d082b8cd4 100644
--- a/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
+++ b/docs/known-issues/es/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
@@ -18,9 +18,7 @@ internalReference: 1071119
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al configurar una promoción de descuento nominal que se acumula con la promoción más por menos, cuando hay un descuento en la promoción más por menos sólo para 1 de 2 artículos, se produce un descuento incorrecto en el artículo del segundo pedido debido a la división de la caja.
diff --git a/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md b/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
index cf3e34a46..c1f087304 100644
--- a/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
+++ b/docs/known-issues/es/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
@@ -18,9 +18,7 @@ internalReference: 871848
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza la función detach para dividir productos por alguna especificación SKU y se intenta abrir una nueva pestaña de PLP a PDP, no reconoce el parámetro de propiedad que se pasa a la URL para seleccionar el SKU correcto, sólo muestra el SKU adecuado al abrir en la misma pestaña.
diff --git a/docs/known-issues/es/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md b/docs/known-issues/es/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md
index 9a90ff209..f2fd89d1a 100644
--- a/docs/known-issues/es/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md
+++ b/docs/known-issues/es/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md
@@ -18,9 +18,7 @@ internalReference: 649316
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Este comportamiento ocurre cuando una categoría tiene muchas especificaciones y muchos skus. De esta manera, al exportar la hoja de cálculo eventualmente se va a alcanzar el límite de Excel (alrededor de 65k).
diff --git a/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md b/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
index a39e5711d..b15c87f54 100644
--- a/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
+++ b/docs/known-issues/es/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
@@ -18,9 +18,7 @@ internalReference: 795940
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md b/docs/known-issues/es/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md
index 8da73d8a9..50a52d220 100644
--- a/docs/known-issues/es/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md
+++ b/docs/known-issues/es/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md
@@ -18,9 +18,7 @@ internalReference: 514992
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md b/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
index 741ba9eeb..8680c70a8 100644
--- a/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
+++ b/docs/known-issues/es/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
@@ -18,9 +18,7 @@ internalReference: 956264
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el informe 'Notifícame' no tiene SKUs, al intentar exportarlo se generará un archivo corrupto a Excel
diff --git a/docs/known-issues/es/nps-we-arent-accepting-response-with-more-than-65536-characters.md b/docs/known-issues/es/nps-we-arent-accepting-response-with-more-than-65536-characters.md
index ae7895ea4..a3609d3cb 100644
--- a/docs/known-issues/es/nps-we-arent-accepting-response-with-more-than-65536-characters.md
+++ b/docs/known-issues/es/nps-we-arent-accepting-response-with-more-than-65536-characters.md
@@ -18,9 +18,7 @@ internalReference: 317389
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No aceptamos respuestas de NPS con más de 65536 caracteres
diff --git a/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md b/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
index bcfcf5bef..21c8b2cf5 100644
--- a/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
+++ b/docs/known-issues/es/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
@@ -18,9 +18,7 @@ internalReference: 371405
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la interfaz de usuario de precios, podemos filtrar por marca o categoría. Después de hacer un filtro, la UI devuelve sólo los productos en el filtro, pero el total de artículos devueltos en el menú es en realidad el total sin ningún filtro, y los datos mostrados están filtrados como se esperaba.
diff --git a/docs/known-issues/es/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md b/docs/known-issues/es/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md
index fc5bfe224..ee88640cb 100644
--- a/docs/known-issues/es/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md
+++ b/docs/known-issues/es/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md
@@ -18,9 +18,7 @@ internalReference: 745738
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Actualmente el sistema de gestión de ofertas muestra el estado de los skus enviados desde un vendedor a un marketplace y sus interacciones y logs de acciones como actualizaciones de precio y stock.
 
diff --git a/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md b/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
index ae1310c46..b92d585fe 100644
--- a/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
+++ b/docs/known-issues/es/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
@@ -18,9 +18,7 @@ internalReference: 945896
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md b/docs/known-issues/es/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md
index 602e8d5f3..05214d17a 100644
--- a/docs/known-issues/es/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md
+++ b/docs/known-issues/es/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 662821
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La nueva interfaz de usuario tiene una limitación para exportar algunos pedidos una vez que el filtro seleccionado tiene en el nombre un carácter especial, por ejemplo ("&" y "á" o "ú") esto ocurre porque incluso la nueva interfaz de usuario puede filtrar los pedidos, pero llama a la antigua ruta de OMS para exportar los pedidos.
diff --git a/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md b/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
index fe4fd1baa..6d757f2fb 100644
--- a/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
+++ b/docs/known-issues/es/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
@@ -18,9 +18,7 @@ internalReference: 870891
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la página de edición de Mi dirección de Mi cuenta, aunque se rellene la dirección aparece la información roja de "Campo obligatorio" hasta que se guardan los datos.
diff --git a/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md b/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
index 5194e658c..461908d51 100644
--- a/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
+++ b/docs/known-issues/es/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
@@ -18,9 +18,7 @@ internalReference: 727339
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Al finalizar la compra, el cliente va a la página conocida como **Order Placed**, en esta página tenemos un evento **Request Capture** *(`RequestType: "orderPlaced"`) de nuestra plataforma que captura algunos detalles del pedido y sirve para alimentar de información el **DataLayer**.
 
diff --git a/docs/known-issues/es/oorderbypriceasc-could-bring-the-wrong-order.md b/docs/known-issues/es/oorderbypriceasc-could-bring-the-wrong-order.md
index d3a83f537..35e8c90f5 100644
--- a/docs/known-issues/es/oorderbypriceasc-could-bring-the-wrong-order.md
+++ b/docs/known-issues/es/oorderbypriceasc-could-bring-the-wrong-order.md
@@ -18,9 +18,7 @@ internalReference: 582861
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 O=OrderByPriceASC puede utilizar una política errónea para ordenar los precios
diff --git a/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md b/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
index 88b83571a..bdecf7829 100644
--- a/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
+++ b/docs/known-issues/es/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
@@ -18,9 +18,7 @@ internalReference: 582861
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 **O=OrderByPriceASC** (o **OrderByPriceDESC**) puede utilizar una política incorrecta para ordenar los precios. Además, como el precio indexado sólo tiene un decimal, no se tendrá en cuenta el segundo decimal del precio.
diff --git a/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md b/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md
index 8aacd1191..5da86eeb7 100644
--- a/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md
+++ b/docs/known-issues/es/openclose-modal-hook-affects-all-modals-on-the-page.md
@@ -18,9 +18,7 @@ internalReference: 1042165
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al abrir/cerrar un modal la acción afecta a todos los modales de la página
diff --git a/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md b/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
index 9314224a6..ff33ed69d 100644
--- a/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
+++ b/docs/known-issues/es/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
@@ -18,9 +18,7 @@ internalReference: 697107
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/ord-reset-not-logging-out-other-sessions.md b/docs/known-issues/es/ord-reset-not-logging-out-other-sessions.md
index f41c38f54..9506fa9ba 100644
--- a/docs/known-issues/es/ord-reset-not-logging-out-other-sessions.md
+++ b/docs/known-issues/es/ord-reset-not-logging-out-other-sessions.md
@@ -18,9 +18,7 @@ internalReference: 530461
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md b/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md
index 93160023e..cc6017925 100644
--- a/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md
+++ b/docs/known-issues/es/order-again-from-b2b-orders-history-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference: 819920
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza la aplicación Historial de Pedidos B2B, la funcionalidad Volver a Pedir no funciona.
diff --git a/docs/known-issues/es/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md b/docs/known-issues/es/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md
index 0cc55d9fb..a4b40add5 100644
--- a/docs/known-issues/es/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md
+++ b/docs/known-issues/es/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md
@@ -18,9 +18,7 @@ internalReference: 547809
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md b/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md
index 80bbb4437..4282f57d6 100644
--- a/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md
+++ b/docs/known-issues/es/order-authorization-lessthan-100-goes-with-the-flow.md
@@ -18,9 +18,7 @@ internalReference: 983031
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Identificamos que cuando el sistema de Autorización de ordenes (OrderAuth) se configura con el valor "lessThan: 100", en el "Rules-list.CreateDoEffect" , no puede entender que es menor o igual al 100%, solo que es menor al 100% y cuando la orden tiene un descuento del 100%, el sistema autoriza la orden para que siga el flujo normal.
diff --git a/docs/known-issues/es/order-cannot-be-created-when-seller-has-a-different-country-code.md b/docs/known-issues/es/order-cannot-be-created-when-seller-has-a-different-country-code.md
index c2b72afc5..9552ac1eb 100644
--- a/docs/known-issues/es/order-cannot-be-created-when-seller-has-a-different-country-code.md
+++ b/docs/known-issues/es/order-cannot-be-created-when-seller-has-a-different-country-code.md
@@ -18,9 +18,7 @@ internalReference: 763955
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un marketplace, cuando hay un vendedor configurado con un Código de País diferente, el servicio de cumplimiento tendrá en cuenta el Código de País del vendedor al realizar el pedido. Puede generar un error si el Código de país del vendedor define campos obligatorios diferentes a los del marketplace.
diff --git a/docs/known-issues/es/order-cant-be-created-due-to-invalid-credit-card.md b/docs/known-issues/es/order-cant-be-created-due-to-invalid-credit-card.md
index 49d10d64c..0bbcce7b1 100644
--- a/docs/known-issues/es/order-cant-be-created-due-to-invalid-credit-card.md
+++ b/docs/known-issues/es/order-cant-be-created-due-to-invalid-credit-card.md
@@ -18,9 +18,7 @@ internalReference: 607742
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La creación de un pedido puede fallar con la excepción genérica "_Se ha producido un error de comunicación con la pasarela y los datos de pago de la transacción {id} no se han recibido correctamente_", que tienen diferentes causas de origen. Una de ellas estará relacionada con la excepción interna "_La información de la cuenta solicitada no existe_", que puede verse en el historial de transacciones/pagos relacionado con el pedido incompleto.
diff --git a/docs/known-issues/es/order-card-info-causing-confusing-on-status.md b/docs/known-issues/es/order-card-info-causing-confusing-on-status.md
index b0bb58cb1..7cc03156e 100644
--- a/docs/known-issues/es/order-card-info-causing-confusing-on-status.md
+++ b/docs/known-issues/es/order-card-info-causing-confusing-on-status.md
@@ -18,9 +18,7 @@ internalReference: 619778
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Pedidos en estado Manipulación en la nueva vista de la UI, tiene una información de tarjeta que dice (Pedido facturado), y es confuso para el cliente.
diff --git a/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md b/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
index 37f10a8b1..4aaefc812 100644
--- a/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
+++ b/docs/known-issues/es/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
@@ -18,9 +18,7 @@ internalReference: 512393
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-doesnt-update-status-in-oms.md b/docs/known-issues/es/order-doesnt-update-status-in-oms.md
index b6a3d3f6f..1492f8a65 100644
--- a/docs/known-issues/es/order-doesnt-update-status-in-oms.md
+++ b/docs/known-issues/es/order-doesnt-update-status-in-oms.md
@@ -18,9 +18,7 @@ internalReference: 421529
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md b/docs/known-issues/es/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md
index 86c3afe62..90b6df3cc 100644
--- a/docs/known-issues/es/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md
+++ b/docs/known-issues/es/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md
@@ -18,9 +18,7 @@ internalReference: 832429
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La exportación de pedidos no funciona correctamente porque la tarea de exportar se cancela cuando hay un pedido en la lista con una gran carga útil, por ejemplo en el caso de un pedido con más de 500 elementos en json.
diff --git a/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md b/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
index 360af0124..d6fe1262f 100644
--- a/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
+++ b/docs/known-issues/es/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
@@ -18,9 +18,7 @@ internalReference: 786216
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El sistema de reporte de pedidos actualmente no puede construir un archivo a partir de filtros de promoción que contengan doble espacio en sus nombres, al intentar construir el reporte el sistema genera un error y no se realiza la exportación, dando como resultado el mensaje "_Exportación completada. Se enviaron 0 pedidos a su correo electrónico"_.
diff --git a/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
index ef93d4fcd..365c34606 100644
--- a/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
+++ b/docs/known-issues/es/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -18,9 +18,7 @@ internalReference: 1045623
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El sistema de filtrado de pedidos actualmente no devuelve los pedidos con promociones que contienen comillas dobles `"` en sus nombres, esto también se aplica al nombre SKU.
diff --git a/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md b/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md
index fd6b67749..5637dd01a 100644
--- a/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md
+++ b/docs/known-issues/es/order-not-notified-carrier-leaves-label-barcode-incomplete.md
@@ -18,9 +18,7 @@ internalReference: 872530
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los clientes que utilizan transportistas asociados a la Red de Envíos, al solicitar la emisión de etiquetas en Listo para enviar, pueden obtener el archivo con el código de barras incompleto, lo que puede impedir que se envíe el paquete.
diff --git a/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md b/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md
index a5b8fd95c..3ea1ab1f5 100644
--- a/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md
+++ b/docs/known-issues/es/order-partial-return-triggered-the-transaction-total-refund.md
@@ -18,9 +18,7 @@ internalReference: 377044
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md b/docs/known-issues/es/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md
index c06051640..fcda8aef5 100644
--- a/docs/known-issues/es/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md
+++ b/docs/known-issues/es/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md
@@ -18,9 +18,7 @@ internalReference: 563300
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un pedido es devuelto por Marketplace a través de la "nueva UI" y se inserta un valor "adicional" en la "nueva UI", se genera una giftcard erróneamente y con ello, Checkout devuelve un error diciendo "que no hay valor a revertir y el email transaccional "vtexcommerce-order-refunded" no es enviado al cliente final.
diff --git a/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md b/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
index 4bacdbf04..c566a7be1 100644
--- a/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
+++ b/docs/known-issues/es/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
@@ -18,9 +18,7 @@ internalReference: 866622
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La característica de reemplazo de pedidos no funciona cuando el carrito reemplazado tiene el mismo valor que el pedido original, y el sistema de pago es "Reutilizar Pago".
diff --git a/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md b/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
index 58d6d9891..71a3f463f 100644
--- a/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
+++ b/docs/known-issues/es/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
@@ -18,9 +18,7 @@ internalReference: 895664
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los conectores de esa lista necesitan guardar más campos para el conector que trabaja con "Venda direta" - Sales app. En concreto, para los conectores de la siguiente lista, y sólo para ellos, todo el contenido de la carga útil debe dirigirse al campo "`connectorResponses`". Esto resulta en una duplicación del campo "`tid`", que ya existe en el "`connectorResponses`". Aunque esta duplicación no plantea ningún problema en cuanto al ciclo de vida de la transacción, sí crea una incoherencia a la hora de generar informes desde la página de pedido.
diff --git a/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md b/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
index 679bb6b59..811009480 100644
--- a/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
+++ b/docs/known-issues/es/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
@@ -18,9 +18,7 @@ internalReference: 1004978
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hemos identificado que algunos vendedores, en la estructura de vendedores y marketplace de VTEX, cuando solicitan la cancelación, luego deniegan esta cancelación a través de la UI, o llaman a la API "cancellation-request-denied-ffm", esto es como si denegaran la propia solicitud de cancelación, por alguna razón, la solicitud de denegar la cancelación se solapa con la solicitud de cancelar.
diff --git a/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md b/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
index ada93e1d4..995733547 100644
--- a/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
+++ b/docs/known-issues/es/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
@@ -18,9 +18,7 @@ internalReference: 1031035
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md b/docs/known-issues/es/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md
index a4255b8fd..28a2a6dc4 100644
--- a/docs/known-issues/es/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md
+++ b/docs/known-issues/es/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md
@@ -18,9 +18,7 @@ internalReference: 784171
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md b/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
index 7f2c78270..6fc454e38 100644
--- a/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
+++ b/docs/known-issues/es/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
@@ -18,9 +18,7 @@ internalReference: 376077
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La plataforma impide la devolución de importes superiores al total del pedido. Esto se convierte en un problema para la devolución de pedidos en los que la forma de pago conlleva intereses.
diff --git a/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md b/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
index 22ed0021e..d3e4039c4 100644
--- a/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
+++ b/docs/known-issues/es/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
@@ -18,9 +18,7 @@ internalReference: 529143
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para los pedidos con método de pago que utilizan conectores como la aplicación de pago o la redirección no hay ningún GatewayCallback para Checkout que sea responsable de crear la suscripción y enviar un correo electrónico de nuevo pedido.
diff --git a/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md b/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md
index 91bf1ac44..079854cfd 100644
--- a/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md
+++ b/docs/known-issues/es/order-with-status-of-canceled-but-the-payment-remains-authorized.md
@@ -18,9 +18,7 @@ internalReference: 420019
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos casos en los que el pedido queda incompleto o anulado al producirse algún fallo de comunicación con la Pasarela, el pago queda autorizado y/o aprobado, no entrando en el flujo de anulación y no devolviéndose automáticamente el importe pagado. Además, se pueden enviar accidentalmente correos electrónicos transaccionales, que también permiten el pago de recibos bancarios, ya que la URL irá con él.
diff --git a/docs/known-issues/es/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md b/docs/known-issues/es/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md
index a047cb676..33b76c7c2 100644
--- a/docs/known-issues/es/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md
+++ b/docs/known-issues/es/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md
@@ -18,9 +18,7 @@ internalReference: 500245
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a una incoherencia, existe una diferencia entre lo que realmente se capturó y lo que se solicitó capturar. Haciendo imposible la facturación del pedido.
diff --git a/docs/known-issues/es/order-xxx-with-invalid-status.md b/docs/known-issues/es/order-xxx-with-invalid-status.md
index ea0b5bbce..45deace6e 100644
--- a/docs/known-issues/es/order-xxx-with-invalid-status.md
+++ b/docs/known-issues/es/order-xxx-with-invalid-status.md
@@ -18,9 +18,7 @@ internalReference: 514613
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md b/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
index 624bc84e7..d71ce5ae9 100644
--- a/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
+++ b/docs/known-issues/es/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
@@ -18,9 +18,7 @@ internalReference: 742139
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Aunque un orderForm soporta que el mismo SKU sea añadido múltiples veces a través de diferentes vendedores, no permite que el método de envío (SLA) sea seleccionado individualmente - donde la logística para un vendedor es completamente independiente de los demás.
diff --git a/docs/known-issues/es/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md b/docs/known-issues/es/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md
index 0e0a70e65..e916f233d 100644
--- a/docs/known-issues/es/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md
+++ b/docs/known-issues/es/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md
@@ -18,9 +18,7 @@ internalReference: 320044
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de cambiar (actualizar o eliminar) algunos anexos de artículos en el catálogo de productos, si ya tiene algún carro/formulario de pedido que hace referencia a artículos con el anexo específico, el formulario de pedido ya no se puede cargar.
diff --git a/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md b/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
index 38f00029e..9ec2ef98d 100644
--- a/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
+++ b/docs/known-issues/es/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
@@ -18,9 +18,7 @@ internalReference: 298665
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un carrito/pedido tiene varios artículos con entrega programada del mismo vendedor, las opciones programadas con el mismo ID (consideradas el mismo método de envío) necesitan tener las mismas ventanas de entrega entre ellas. Si no hay intersección, el método de envío será descartado para algunos artículos.
diff --git a/docs/known-issues/es/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md b/docs/known-issues/es/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md
index 7072e5cdd..effd7d3a6 100644
--- a/docs/known-issues/es/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md
+++ b/docs/known-issues/es/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md
@@ -18,9 +18,7 @@ internalReference: 334191
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El orderForm es sensible a la modificación o eliminación de un itemAttachment del catálogo de productos. Si un itemAttachment deja de existir o comienza a tener otro patrón de validación, un orderForm que ya tiene datos antiguos se volverá inaccesible, y no será posible proceder con el flujo de compra.
diff --git a/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md b/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md
index 8cea78482..e6be76266 100644
--- a/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md
+++ b/docs/known-issues/es/orderform-not-returning-customers-data-even-for-authorized-credentials.md
@@ -18,9 +18,7 @@ internalReference: 582070
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al interactuar con un orderForm en la situación específica en la que los datos del cliente se importaron automáticamente después de iniciar sesión, se eliminarán sus datos del orderForm incluso para los "superusuarios", identificados por sus appKeys.
diff --git a/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md b/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md
index 9cc9eccf7..6e5f09827 100644
--- a/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md
+++ b/docs/known-issues/es/orderform-not-updating-after-order-is-placed.md
@@ -18,9 +18,7 @@ internalReference: 1056870
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de realizar un pedido, el orderFormId no se actualiza, lo que provoca que los artículos permanezcan visibles en el carrito. Este problema afecta a las cuentas FastStore
diff --git a/docs/known-issues/es/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md b/docs/known-issues/es/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md
index a8e8876ee..216653e77 100644
--- a/docs/known-issues/es/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md
+++ b/docs/known-issues/es/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md
@@ -18,9 +18,7 @@ internalReference: 276823
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La eliminación de una tarjeta de crédito a través de la página de mi cuenta no actualiza el orderForm, que mantendría una tarjeta de crédito que ya no existe.
diff --git a/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved.md b/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved.md
index 10d87bb5a..530843753 100644
--- a/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved.md
+++ b/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved.md
@@ -18,9 +18,7 @@ internalReference: 525127
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Cuando se cambia la ordenación de los campos de productos o SKUs en una categoría que no es la principal, después de hacer clic en el botón de ordenación los cambios no se guardan y los campos modificados no aparecen después de recargar la página.
 
diff --git a/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved1.md b/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved1.md
index 26cd81997..353519846 100644
--- a/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved1.md
+++ b/docs/known-issues/es/ordering-of-product-fields-and-skus-is-not-saved1.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se cambia la ordenación de los campos de productos o SKUs en una categoría que no es la principal, después de hacer clic en el botón de ordenación los cambios no se guardan y los campos modificados no aparecen después de recargar la página.
diff --git a/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md b/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md
index 4d8e8ac4b..f0d11e245 100644
--- a/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md
+++ b/docs/known-issues/es/ordering-of-specification-groups-from-the-root-category-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 634129
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se crean grupos de especificaciones en la categoría raíz, no es posible reordenarlos por parte del administrador o de la API
diff --git a/docs/known-issues/es/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md b/docs/known-issues/es/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md
index 4179c08cc..a1375cbef 100644
--- a/docs/known-issues/es/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md
+++ b/docs/known-issues/es/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md
@@ -18,9 +18,7 @@ internalReference: 679598
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los pedidos son independientes cuando no comparten la misma transacción de pago. Los pedidos creados para cumplir sólo con el artículo de regalo a través de un vendedor diferente a los demás artículos de una compra no tienen ninguna transacción de pago porque son gratuitos.
diff --git a/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md b/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
index 7edff1441..f0b753792 100644
--- a/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
+++ b/docs/known-issues/es/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 577219
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Pedidos facturados en VTEX pero que no actualizan la factura en Netshoes
diff --git a/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md b/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
index e3a1c1faf..f0a879f21 100644
--- a/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
+++ b/docs/known-issues/es/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
@@ -18,9 +18,7 @@ internalReference: 930491
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Durante el proceso de envío de facturas, es posible que el usuario envíe facturas de salida y de entrada, pero si en un pedido se realizan dos facturas parciales, una de salida y otra de entrada, el sistema suma estos valores para validar si el pedido puede recibir una nueva factura, imposibilitando que los pedidos cuyo artículo fue facturado y luego devuelto no tengan facturado su valor total.
diff --git a/docs/known-issues/es/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md b/docs/known-issues/es/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md
index 8c835e88b..eb1ae1255 100644
--- a/docs/known-issues/es/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md
+++ b/docs/known-issues/es/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md
@@ -18,9 +18,7 @@ internalReference: 640925
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vendedor de pedidos 1, donde el MKT y el FFMT están en la misma cuenta, no tiene notificaciones en el tipo de gancho FromOrders para el estado "Payment-Approved".
diff --git a/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md b/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md
index 2ef15524c..641705a64 100644
--- a/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md
+++ b/docs/known-issues/es/orders-with-asterisks-in-the-address-and-profile.md
@@ -18,9 +18,7 @@ internalReference: 360783
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay pedidos en los que la `invoiceAddress`, `shippingAddress` o `clientProfileData` se están enviando como `masked` en lugar de la dirección real. Este comportamiento se produce cuando un usuario completa la compra con un formulario de pedido que contiene datos enmascarados que están "encadenados". Como se trata de campos de cadena, los datos del pedido se rellenan con la máscara "***".
diff --git a/docs/known-issues/es/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md b/docs/known-issues/es/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md
index 75675a466..5c9e7b819 100644
--- a/docs/known-issues/es/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md
+++ b/docs/known-issues/es/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md
@@ -18,9 +18,7 @@ internalReference: 656815
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los pedidos con cambio de vendedor, tienen el respectivo pedido en el primer vendedor cancelado y se creará un nuevo pedido en el segundo vendedor. Si incluso el nuevo pedido está fuera del período de gracia de cancelación, el usuario todavía puede cancelar el pedido.
diff --git a/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md b/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
index bcbdbe01c..d9061a386 100644
--- a/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
+++ b/docs/known-issues/es/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
@@ -18,9 +18,7 @@ internalReference: 656821
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md b/docs/known-issues/es/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md
index dff8762e2..839d0a043 100644
--- a/docs/known-issues/es/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md
+++ b/docs/known-issues/es/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md
@@ -18,9 +18,7 @@ internalReference: 618388
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Pedidos con KIT, en NEW_UI se está mostrando el ID del KIT, donde debería mostrar el ID de la SKU.
diff --git a/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md b/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md
index 996b9d711..8bced32c6 100644
--- a/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md
+++ b/docs/known-issues/es/orders-without-invoiceaddress-created-through-native-ui.md
@@ -18,9 +18,7 @@ internalReference: 306140
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/orders-without-some-details-in-the-shipping-sla-object.md b/docs/known-issues/es/orders-without-some-details-in-the-shipping-sla-object.md
index 66535490e..25db0b523 100644
--- a/docs/known-issues/es/orders-without-some-details-in-the-shipping-sla-object.md
+++ b/docs/known-issues/es/orders-without-some-details-in-the-shipping-sla-object.md
@@ -18,9 +18,7 @@ internalReference: 575219
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos pedidos de vendedores nativos (incluyendo el "vendedor 1") han sido reportados como que no devuelven algunos detalles en el objeto SLA de envío, como el `"transitTime"` o incluso `"deliveryIds"`. Pero la información está disponible en la orden de cumplimiento (en el lado del vendedor).
diff --git a/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md b/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md
index 7059d4eb0..83dd18542 100644
--- a/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md
+++ b/docs/known-issues/es/ordination-of-images-when-uploading-a-new-version-not-working.md
@@ -18,9 +18,7 @@ internalReference: 739814
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El filtro de orden en el editor CMS/Site al subir una nueva imagen no funciona correctamente
diff --git a/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
index 72359e985..361c10486 100644
--- a/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/es/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
@@ -18,9 +18,7 @@ internalReference: 1015043
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos BIN no se identifican correctamente en la caja. La marca de la tarjeta se determina mediante una regex que podría quedar obsoleta, dando lugar a marcas de tarjeta no identificadas o mal identificadas.
diff --git a/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md b/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
index 62d1ef073..cad925086 100644
--- a/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
+++ b/docs/known-issues/es/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
@@ -18,9 +18,7 @@ internalReference: 907428
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para las tiendas que utilizan el motor de búsqueda heredado, si se realizan dos cambios en los datos de un producto en una sucesión rápida (es decir, has desactivado un producto y lo has reactivado justo después), y el último cambio devuelve la información del producto a lo que era justo antes, el estado de dicho artículo puede quedarse atascado en el primer cambio, ya que este último no se reconoce correctamente.
diff --git a/docs/known-issues/es/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md b/docs/known-issues/es/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md
index 10f0bfa6f..553ae171a 100644
--- a/docs/known-issues/es/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md
+++ b/docs/known-issues/es/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md
@@ -18,9 +18,7 @@ internalReference: 373603
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los clientes guatemaltecos informaron que el formulario de dirección de facturación está desactualizado. La causa principal son algunos cambios de localización de zona. La actualización ya fue implementada en la dirección de envío y necesita ser hecha en la dirección de facturación también
diff --git a/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
index b37832673..03c9bcebd 100644
--- a/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/es/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
@@ -18,9 +18,7 @@ internalReference: 642136
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos códigos BIN no se identifican correctamente en la caja. La marca de la tarjeta se determina mediante una regex que puede quedar obsoleta, provocando que la marca de la tarjeta no se identifique o se identifique erróneamente.
diff --git a/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md b/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md
index 928a7dcad..a681ffbd5 100644
--- a/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md
+++ b/docs/known-issues/es/outdated-url-on-the-update-binding-ui.md
@@ -18,9 +18,7 @@ internalReference: 890791
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el comerciante es la actualización de una licitación de la interfaz de usuario es como sigue:
diff --git a/docs/known-issues/es/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md b/docs/known-issues/es/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md
index fc914eccd..40e9a09d7 100644
--- a/docs/known-issues/es/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md
+++ b/docs/known-issues/es/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md
@@ -18,9 +18,7 @@ internalReference: 454680
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 El diseño de la página cambia a la versión móvil cuando se activa la impresión (CTRL+P) dos veces en Google Chrome Desktop.
 
diff --git a/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md b/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md
index 214b8db12..76e4a7af4 100644
--- a/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md
+++ b/docs/known-issues/es/pageview-is-triggered-twice-when-accessing-my-account.md
@@ -18,9 +18,7 @@ internalReference: 854480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al acceder a Mi Cuenta, el evento pageView se dispara dos veces, duplicando los datos en Analytics.
diff --git a/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md b/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
index a286b3b87..703f538f6 100644
--- a/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
+++ b/docs/known-issues/es/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
@@ -18,9 +18,7 @@ internalReference: 888042
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El evento pageView se muestra duplicado en dataLayer cuando en las páginas de búsqueda personalizada
diff --git a/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md b/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md
index c50328f49..a325d9ab6 100644
--- a/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md
+++ b/docs/known-issues/es/pagination-links-on-search-results-not-working-on-giftlist-pages.md
@@ -18,9 +18,7 @@ internalReference: 481330
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los enlaces de paginación en `SearchResult` no funcionan en `Giftlist`.
diff --git a/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md b/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
index 950ea64fc..5aa0860e3 100644
--- a/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
+++ b/docs/known-issues/es/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
@@ -18,9 +18,7 @@ internalReference: 857392
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Mientras navegamos por una determinada página de un PLP, realizamos una búsqueda para mostrar más resultados, y cambiamos el contexto para navegar por un departamento diferente, el parámetro de paginación se mantendrá y el resultado de la búsqueda comenzará en la nueva categoría en la misma página en la que estábamos anteriormente.
diff --git a/docs/known-issues/es/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md b/docs/known-issues/es/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md
index 8b9a462e8..f31f4b2e8 100644
--- a/docs/known-issues/es/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md
+++ b/docs/known-issues/es/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md
@@ -18,9 +18,7 @@ internalReference: 627261
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El cambio de dirección puede modificar las opciones de envío de un artículo y, naturalmente, puede eliminar la selección de la ventana de entrega para las entregas programadas si las opciones son diferentes.
diff --git a/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md b/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
index 8b9307940..3ee513331 100644
--- a/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
+++ b/docs/known-issues/es/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
@@ -18,9 +18,7 @@ internalReference: 481878
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md b/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
index 76cba7845..437a1f6d7 100644
--- a/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
+++ b/docs/known-issues/es/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
@@ -18,9 +18,7 @@ internalReference: 1030652
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las condiciones de pago configuradas para procesar transacciones en un número de plazos distinto de 1x están pudiendo procesar pagos en 1x. El problema solo se produce en los pagos en los que el usuario ha optado por el prepago total.
diff --git a/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md b/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
index 3285f1ab3..f24c4258d 100644
--- a/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
+++ b/docs/known-issues/es/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
@@ -18,9 +18,7 @@ internalReference: 402140
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la configuración del método de pago, en el producto de las promociones, no está previsto que se transmita a través de la solicitud/respuesta de cumplimiento.
diff --git a/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md b/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
index bd85b45d9..ffacb4e4a 100644
--- a/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
+++ b/docs/known-issues/es/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
@@ -18,9 +18,7 @@ internalReference: 666469
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Este KI se manifiesta de dos maneras en la caja:
diff --git a/docs/known-issues/es/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md b/docs/known-issues/es/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md
index e55c58540..19e8f726d 100644
--- a/docs/known-issues/es/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md
+++ b/docs/known-issues/es/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md
@@ -18,9 +18,7 @@ internalReference: 649237
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos métodos de pago permanecen en la página de pago incluso cuando la condición de pago asociada está desactivada durante más de 10 minutos. Este es un problema intermitente y no hay pruebas sobre cómo reproducir este comportamiento
diff --git a/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md b/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
index da6953427..35b9a3974 100644
--- a/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
+++ b/docs/known-issues/es/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
@@ -18,9 +18,7 @@ internalReference: 1019548
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La actualización de las condiciones de pago en la interfaz de usuario de detalles de la organización para una organización no se aplica a la configuración de pago B2B.
diff --git a/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
index 93ac8ea6e..56ccb8b41 100644
--- a/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
+++ b/docs/known-issues/es/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -18,9 +18,7 @@ internalReference: 989507
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las condiciones de pago configuradas en los Ajustes de Organizaciones B2B no se guardan en los Detalles de la Organización.
diff --git a/docs/known-issues/es/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md b/docs/known-issues/es/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md
index 3de06eace..f6637b788 100644
--- a/docs/known-issues/es/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md
+++ b/docs/known-issues/es/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md
@@ -18,9 +18,7 @@ internalReference: 801012
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El problema radica en la formulación de las URLs que se envían al proveedor de pagos. Por lo tanto, lo que ocurre es que en escenarios donde estas URLs son diferentes, como en el caso de una cuenta franquiciada que procesa el pago y almacena en una tienda rápida, la diferencia entre las URLs generadas en el pago y la URL esperada por el checkout provoca que la app no renderice.
diff --git a/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md b/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
index ef8cdd7b6..1bbca9c2d 100644
--- a/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
+++ b/docs/known-issues/es/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
@@ -18,9 +18,7 @@ internalReference: 1025321
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el valor total de un carrito proviene exclusivamente de un precio manual, el `precio` de los artículos y el `precio` de la entrega son `0`, no se ofrecen otros sistemas de pago que la Tarjeta Regalo (si está activa).
diff --git a/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md b/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
index c63f0bb20..597efa142 100644
--- a/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
+++ b/docs/known-issues/es/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
@@ -18,9 +18,7 @@ internalReference: 777201
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un marketplace con vendedores con relación multinivel (MOI), cuando se monta un carrito con al menos un vendedor que utiliza división de transacciones y otros que utilizan división de pagos, las transacciones con división de pagos se duplicarán repitiendo los artículos de distintos vendedores. Este escenario no permitirá realizar el pedido, y aparecerá el mensaje "Lo sentimos. No se han podido procesar los pagos solicitados".
diff --git a/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md b/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md
index 7c8632f0f..cfd14f72b 100644
--- a/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md
+++ b/docs/known-issues/es/paypalplus-does-not-respect-the-minimum-installment-amount.md
@@ -18,9 +18,7 @@ internalReference: 370271
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Incluso con el importe mínimo de la cuota configurado en el término de pago de PayPalPlus, mostramos cuotas en el pago que no respetan esta configuración
diff --git a/docs/known-issues/es/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md b/docs/known-issues/es/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md
index aafa2eac3..e1d99ecfe 100644
--- a/docs/known-issues/es/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md
+++ b/docs/known-issues/es/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md
@@ -18,9 +18,7 @@ internalReference: 770893
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay algunos casos especiales en los que la tienda tiene un enlace a una página en la que se pasa un carácter especial como '#' para pasar una propiedad, por ejemplo, el color del artículo, que hace que el PDP no cargue a la primera, sino que sigue intentando cargar, pero cuando se refresca la página sí carga correctamente.
diff --git a/docs/known-issues/es/phone-field-order-netshoes.md b/docs/known-issues/es/phone-field-order-netshoes.md
index ddfb55e48..6d89f8026 100644
--- a/docs/known-issues/es/phone-field-order-netshoes.md
+++ b/docs/known-issues/es/phone-field-order-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 599271
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md b/docs/known-issues/es/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md
index 6bb46d3f4..e118b4c6f 100644
--- a/docs/known-issues/es/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md
+++ b/docs/known-issues/es/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md
@@ -18,9 +18,7 @@ internalReference: 588394
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el comprador selecciona una tienda para la recogida, cambia a la entrega y añade una nueva dirección no disponible para la entrega cuando vuelve para la recogida, vuelve a aparecer seleccionada otra tienda. Si alternamos entre entrega y recogida, a veces la tienda seleccionada aparece inicialmente intercalada con otra tienda.
diff --git a/docs/known-issues/es/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md b/docs/known-issues/es/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md
index 9462b95b7..fa7866211 100644
--- a/docs/known-issues/es/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md
+++ b/docs/known-issues/es/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 524073
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un mercado con una relación multinivel (MOI), cuando se selecciona un punto de recogida, el mercado devuelve un error de comunicación con el vendedor, impidiendo el uso de puntos de recogida en el mercado junto con esos vendedores.
diff --git a/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md b/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
index 98427ff10..28eadf855 100644
--- a/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
+++ b/docs/known-issues/es/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
@@ -18,9 +18,7 @@ internalReference: 1041462
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al insertar un código postal en el modal del selector de punto de recogida, se activa una solicitud para obtener los ANS disponibles para esa ubicación. Si la cuenta no tiene una clave de API de Google Maps definida en su configuración de Pago, esta solicitud no incluirá información de geoCoordenadas. Esto puede provocar que no se muestren los puntos de recogida dentro de un rango válido, como aquellos cuyas tablas de carga se basan en polígonos.
diff --git a/docs/known-issues/es/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md b/docs/known-issues/es/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md
index 75067f3ab..698167929 100644
--- a/docs/known-issues/es/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md
+++ b/docs/known-issues/es/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md
@@ -18,9 +18,7 @@ internalReference: 328464
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El modal de puntos de recogida, desde el checkout, muestra en azul las opciones válidas como SLA calculadas para el carrito y en gris otras opciones que no estaban calculadas previamente como SLA, para que el comprador pueda conocer estas opciones e incluso comprobar su disponibilidad bajo demanda. Estas opciones provienen de la API `/api/checkout/pub/pickup-points` (que no es más que un proxy al servicio de Logística), que listará todos los puntos de recogida de la tienda.
diff --git a/docs/known-issues/es/pickup-point-selector-search-will-not-working-with-enterreturn.md b/docs/known-issues/es/pickup-point-selector-search-will-not-working-with-enterreturn.md
index 4ed27c5b0..eacb8d180 100644
--- a/docs/known-issues/es/pickup-point-selector-search-will-not-working-with-enterreturn.md
+++ b/docs/known-issues/es/pickup-point-selector-search-will-not-working-with-enterreturn.md
@@ -18,9 +18,7 @@ internalReference: 829955
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el selector de puntos de recogida, si se escribe una dirección y se pulsa Intro/Retorno, no aparecerán las tiendas más cercanas. El comprador siempre tiene que escribir la dirección y seleccionar una opción de la lista.
diff --git a/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md b/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
index d1553f982..1901edc6d 100644
--- a/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
+++ b/docs/known-issues/es/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
@@ -18,9 +18,7 @@ internalReference: 1015158
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las etiquetas registradas en el punto de recogida están disponibles en un desplegable en las políticas de envío para enlazar el PUP con la Política de Envío, sin embargo cuando alguna de estas etiquetas es eliminada en el PUP, permanecen disponibles en el desplegable dentro de la política de envío.
diff --git a/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md b/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
index cb7422252..aa5917e69 100644
--- a/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
+++ b/docs/known-issues/es/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
@@ -18,9 +18,7 @@ internalReference: 624646
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al buscar un punto de recogida en el carrito o en la caja mientras se encuentra en un diseño responsivo estrecho/de retrato (ancho inferior a 1024px) utilizando la vista de mapa, los resultados se presentarán en el modo de lista en lugar del propio mapa, y esta lista no funcionará (el usuario no podrá desplazarse hacia abajo).
diff --git a/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md b/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md
index 7cde89048..55f374f92 100644
--- a/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md
+++ b/docs/known-issues/es/pickup-points-not-indexed-in-master-data.md
@@ -18,9 +18,7 @@ internalReference: 530824
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el sistema logístico utiliza MasterData para almacenar la información de los Puntos de Recogida. Como resultado, podemos tener problemas para indexar esta entidad interna cuando se utiliza la ruta de búsqueda. Esto puede dar lugar a información obsoleta, como por ejemplo:
diff --git a/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md b/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
index eece6e37a..0e859ad01 100644
--- a/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
+++ b/docs/known-issues/es/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
@@ -18,9 +18,7 @@ internalReference: 964036
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando los dos puntos de recogida con IDs comienzan con el mismo patrón, la UI de caja los valida como la misma tienda, mostrando un producto disponible.
diff --git a/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md b/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
index e70cd577b..c5cf10c65 100644
--- a/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
+++ b/docs/known-issues/es/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
@@ -18,9 +18,7 @@ internalReference: 482256
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La interfaz de usuario no funciona correctamente en un carrito con más de un artículo con una división de entrega en la que uno de los artículos está disponible para recogida y los otros sólo para entrega programada.
diff --git a/docs/known-issues/es/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md b/docs/known-issues/es/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md
index 7b6190634..3b5bc0e68 100644
--- a/docs/known-issues/es/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md
+++ b/docs/known-issues/es/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md
@@ -18,9 +18,7 @@ internalReference: 438630
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay una característica en el módulo de Logística para heredar los puntos de recogida entre las cuentas de franquicia, y así entre los vendedores de marca blanca. Mientras estén registrados en un vendedor X, aparecerán como opciones de recogida para un vendedor Y según lo configurado en la estrategia de envío. Aunque sean los mismos, su ID será diferente entre cada vendedor, por lo que se verán como opciones de recogida diferentes e independientes.
diff --git a/docs/known-issues/es/placeholder-settings-in-the-cms-does-not-display-all-content.md b/docs/known-issues/es/placeholder-settings-in-the-cms-does-not-display-all-content.md
index 9422223b5..193001155 100644
--- a/docs/known-issues/es/placeholder-settings-in-the-cms-does-not-display-all-content.md
+++ b/docs/known-issues/es/placeholder-settings-in-the-cms-does-not-display-all-content.md
@@ -18,9 +18,7 @@ internalReference: 547555
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se añade demasiado contenido dentro de un marcador de posición en un diseño de CMS, Admin no permite el desplazamiento de la página, lo que detiene la edición
diff --git a/docs/known-issues/es/placeholders-showing-instead-of-the-correct-data.md b/docs/known-issues/es/placeholders-showing-instead-of-the-correct-data.md
index ff9f4fab2..5a39d4c3b 100644
--- a/docs/known-issues/es/placeholders-showing-instead-of-the-correct-data.md
+++ b/docs/known-issues/es/placeholders-showing-instead-of-the-correct-data.md
@@ -18,9 +18,7 @@ internalReference: 371183
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md b/docs/known-issues/es/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md
index ee108893d..9bd4fb65b 100644
--- a/docs/known-issues/es/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md
+++ b/docs/known-issues/es/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md
@@ -18,9 +18,7 @@ internalReference: 732529
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la solicitud de creación de pedido declara el mismo artículo más de una vez, requerido para declarar diferentes precios o valores de descuento entre las múltiples unidades del artículo, el servicio de checkout sumará todas las cantidades en un único artículo y aplicará sólo las condiciones del primer artículo en todos ellos. Generará un precio/descuento total erróneo e incluso el envío.
diff --git a/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md b/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
index 9f51fa893..baa9b7846 100644
--- a/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
+++ b/docs/known-issues/es/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
@@ -18,9 +18,7 @@ internalReference: 956338
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos algunos problemas a la hora de colocar los códigos postales en el módulo **Previsualización de envíos** del carrito, algunos de ellos se describen en estos KIs:
diff --git a/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md b/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
index 01f763d59..72656d257 100644
--- a/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
+++ b/docs/known-issues/es/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 417322
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la caja de una tienda, tenemos una opción para cerrar la sesión.
diff --git a/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
index a8d558211..375d26149 100644
--- a/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/es/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -18,9 +18,7 @@ internalReference: 712443
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Una tienda necesita configurar la imagen **Principal** independientemente del orden en el que se haya cargado en el sistema. Actualmente el sistema no respeta la etiqueta **Principal** y acaba tomando como principal la primera imagen registrada.
diff --git a/docs/known-issues/es/portal-etag-not-updating-when-changing-metadata.md b/docs/known-issues/es/portal-etag-not-updating-when-changing-metadata.md
index e349da8a1..8776c83b0 100644
--- a/docs/known-issues/es/portal-etag-not-updating-when-changing-metadata.md
+++ b/docs/known-issues/es/portal-etag-not-updating-when-changing-metadata.md
@@ -18,9 +18,7 @@ internalReference: 411434
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md b/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
index 596df85f6..79b40f399 100644
--- a/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
+++ b/docs/known-issues/es/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
@@ -18,9 +18,7 @@ internalReference: 534838
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El portal mantiene las UTM's después de cerrar la sesión cuando se utiliza Callcenter Operator.
diff --git a/docs/known-issues/es/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md b/docs/known-issues/es/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md
index b69cb22aa..81e0cabc8 100644
--- a/docs/known-issues/es/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md
+++ b/docs/known-issues/es/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 444496
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El Portal Legacy CMS Redirect no funcionará si la URL From tiene parámetros. Si el parámetro es un utm_source, funcionará. Si el parámetro es de cualquier otro tipo, no funcionará.
diff --git a/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md b/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
index 7517350bf..aa113deed 100644
--- a/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
+++ b/docs/known-issues/es/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
@@ -18,9 +18,7 @@ internalReference: 342378
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El portal recarga todos los resultados de la búsqueda cuando se accede a la URL con un parámetro de paginación.
diff --git a/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md b/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
index 459e591fe..9d8c1b983 100644
--- a/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
+++ b/docs/known-issues/es/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
@@ -18,9 +18,7 @@ internalReference: 286470
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un cliente con más de 20 políticas comerciales acaba teniendo más de una política comercial por posición. Esto es crítico porque las configuraciones vinculantes se basan en el número de posición, por lo que sólo debería haber una política comercial por posición.
diff --git a/docs/known-issues/es/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md b/docs/known-issues/es/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md
index 10b523511..92c7b8967 100644
--- a/docs/known-issues/es/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md
+++ b/docs/known-issues/es/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md
@@ -18,9 +18,7 @@ internalReference: 595434
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al seleccionar cualquier imagen en la PDP de un producto, si se pasa de esta PDP directamente a otra PDP, la posición de la imagen no se borrará - si estaba viendo la tercera imagen, verá directamente la tercera imagen en la nueva PDP.
diff --git a/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md b/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md
index bc61852a8..b7bcf55be 100644
--- a/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md
+++ b/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md
@@ -18,9 +18,7 @@ internalReference: 554052
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al llegar al paso de dirección de la UI de compra, el usuario puede completar el número de dirección y el nombre del destinatario con un espacio en blanco y recibir la confirmación de validación, incluso poder pasar al siguiente paso de pago. Incluso sabiendo que no puede terminar la compra con éxito, es una mala usabilidad.
diff --git a/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md b/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md
index 6b39e686b..bd299288f 100644
--- a/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md
+++ b/docs/known-issues/es/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md
@@ -18,9 +18,7 @@ internalReference: 334310
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando eres un usuario que tiene un login y va al checkout, donde los datos están enmascarados, y en el formulario de envío, eliges la opción de entregar en otras direcciones, existe la posibilidad de ir al pago sin necesidad de rellenar el código postal. Llegando así al proceso de pago con los datos de entrega vacíos en la UI.
diff --git a/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md b/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
index a00362de2..d1eb5e46a 100644
--- a/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
+++ b/docs/known-issues/es/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
@@ -18,9 +18,7 @@ internalReference: 955489
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se identificaron algunos problemas en la arquitectura Change Orders V1, donde algunos casos no eran notificados en la interacción de la orden en la UI, no eran notificados en la API Get Orders, sin embargo, había un descuento o incremento en el valor. También hemos visto escenarios donde la notificación ocurre en la UI y API, sin embargo, el descuento o incremento no se realiza en el gateway.
diff --git a/docs/known-issues/es/postal-code-request-in-loop-in-the-shipping-preview-component.md b/docs/known-issues/es/postal-code-request-in-loop-in-the-shipping-preview-component.md
index 4d225221a..e598ae7e1 100644
--- a/docs/known-issues/es/postal-code-request-in-loop-in-the-shipping-preview-component.md
+++ b/docs/known-issues/es/postal-code-request-in-loop-in-the-shipping-preview-component.md
@@ -18,9 +18,7 @@ internalReference: 352659
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de alternar el código postal unas cuantas veces en el componente de vista previa de envío del carrito, el componente entra en un eterno bucle de peticiones de `/api/checkout/pub/postal-code//`
diff --git a/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md b/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md
index 3e58282a2..98c7b8ca3 100644
--- a/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md
+++ b/docs/known-issues/es/presales-of-the-legacy-cms-collection-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 885693
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se esperaba que, al seleccionar la casilla de verificación de pre-pedido, la colección se poblaría con productos cuya fecha de lanzamiento se hubiera rellenado para una fecha futura.
diff --git a/docs/known-issues/es/price-export-incomplete-when-using-category-filters.md b/docs/known-issues/es/price-export-incomplete-when-using-category-filters.md
index f997342c3..e1dcaea29 100644
--- a/docs/known-issues/es/price-export-incomplete-when-using-category-filters.md
+++ b/docs/known-issues/es/price-export-incomplete-when-using-category-filters.md
@@ -18,9 +18,7 @@ internalReference: 753466
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar exportar una hoja de cálculo de precios fijos utilizando los filtros de categorías, algunos skus no aparecen en la hoja de cálculo a pesar de tener precios fijos. La cantidad habitual de skus que se devuelven es de 250.
diff --git a/docs/known-issues/es/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md b/docs/known-issues/es/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md
index a13ebe9da..f19848d90 100644
--- a/docs/known-issues/es/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md
+++ b/docs/known-issues/es/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md
@@ -18,9 +18,7 @@ internalReference: 584975
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces (hay un 50% de posibilidades) los precios se exportan utilizando un nuevo formato que no es aceptado por la importación de precios.
diff --git a/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
index fdf5f345f..5a3b3b53d 100644
--- a/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
+++ b/docs/known-issues/es/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -18,9 +18,7 @@ internalReference: 982664
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los filtros de precio se aplican sobre el valor "spotPrice", que es el precio para condiciones especiales de pago, en lugar del precio normal del artículo.
diff --git a/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md b/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
index 09f150032..f1278020a 100644
--- a/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
+++ b/docs/known-issues/es/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
@@ -18,9 +18,7 @@ internalReference: 997121
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los rangos de precios de la API de facetas ("Obtener lista de las facetas posibles para una consulta dada") pueden variar entre devolver cubos de valores "desde" y "hasta" con precios redondeados y los precios mínimos y máximos entre los resultados de la búsqueda.
diff --git a/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md b/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
index d51bf5b29..2d18fc24d 100644
--- a/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
+++ b/docs/known-issues/es/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
@@ -18,9 +18,7 @@ internalReference: 843442
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Este es un rango de precios, es un deslizador y tiene dos selectores (marcadores), uno para el mínimo y otro para el máximo para saber dónde posicionarse en el deslizador.
diff --git a/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md b/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
index 6951687d6..dc1722476 100644
--- a/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
+++ b/docs/known-issues/es/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
@@ -18,9 +18,7 @@ internalReference: 1070336
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si un artículo se añade al carrito como opción (también conocido como hijo) desde Opciones de montaje, y el mismo artículo se añade al carrito como artículo normal; los precios se mezclan, y cada uno se aplica al incorrecto.
diff --git a/docs/known-issues/es/price-updates-with-cache-on-end-applications.md b/docs/known-issues/es/price-updates-with-cache-on-end-applications.md
index 3bc98098e..46e12dc77 100644
--- a/docs/known-issues/es/price-updates-with-cache-on-end-applications.md
+++ b/docs/known-issues/es/price-updates-with-cache-on-end-applications.md
@@ -18,9 +18,7 @@ internalReference: 896520
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/price-variation-limit-only-works-in-the-main-policy.md b/docs/known-issues/es/price-variation-limit-only-works-in-the-main-policy.md
index c77818c9a..212b2dac5 100644
--- a/docs/known-issues/es/price-variation-limit-only-works-in-the-main-policy.md
+++ b/docs/known-issues/es/price-variation-limit-only-works-in-the-main-policy.md
@@ -18,9 +18,7 @@ internalReference: 509540
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
index 5092112c7..6d0cc2961 100644
--- a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
+++ b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -18,9 +18,7 @@ internalReference: 566142
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API REST de Checkout Cambiar precio no admite precios superiores a un valor "Int32". Por lo tanto, aplicar un "precio manual" estará restringido hasta el número "2.147.483.647" (número en decimales).
diff --git a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md
index 38b73df12..50c857ef6 100644
--- a/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md
+++ b/docs/known-issues/es/prices-restricted-to-int32-max-value-on-checkout-apis.md
@@ -18,9 +18,7 @@ internalReference: 566142
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las API REST de Checkout no admiten precios superiores a un valor "Int32". Por lo tanto, la aplicación de un "precio manual" se limitará al número "2.147.483.647" (número en decimales).
diff --git a/docs/known-issues/es/pricing-api-allows-negative-values.md b/docs/known-issues/es/pricing-api-allows-negative-values.md
index be60541fc..6783431fa 100644
--- a/docs/known-issues/es/pricing-api-allows-negative-values.md
+++ b/docs/known-issues/es/pricing-api-allows-negative-values.md
@@ -18,9 +18,7 @@ internalReference: 774548
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la API de precio PUT permite la entrada de valores negativos a través de la carga útil de la API PUT, si establece el margen y el precio base en valores negativos, establecerá el producto como no disponible.
diff --git a/docs/known-issues/es/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md b/docs/known-issues/es/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md
index 6febfb753..4864ea519 100644
--- a/docs/known-issues/es/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md
+++ b/docs/known-issues/es/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md
@@ -18,9 +18,7 @@ internalReference: 487698
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hemos identificado un problema en la ruta de los precios de los puestos de compatibilidad cuando se envían demasiadas solicitudes en una ventana pequeña no estamos utilizando el precio más actualizado
diff --git a/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
index 78b077cfe..d55ab0335 100644
--- a/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
+++ b/docs/known-issues/es/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -18,9 +18,7 @@ internalReference: 1041743
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los productos pueden ser priorizados en los resultados de búsqueda por su "palabra clave", una palabra del nombre del producto establecida como relevante por un algoritmo. Las palabras clave son términos de búsqueda filtrados de los términos originales porque no son significativos para la búsqueda.
diff --git a/docs/known-issues/es/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md b/docs/known-issues/es/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md
index 40f802961..27f462a12 100644
--- a/docs/known-issues/es/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md
+++ b/docs/known-issues/es/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md
@@ -18,9 +18,7 @@ internalReference: 402857
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos un problema para indexar los métodos de pago en el checkout. Ocurre con las condiciones de pago que están configuradas con un periodo de tiempo especial.
diff --git a/docs/known-issues/es/problem-to-pay-with-giftcard-two-cards-option.md b/docs/known-issues/es/problem-to-pay-with-giftcard-two-cards-option.md
index f4af1ab6b..ada740c9e 100644
--- a/docs/known-issues/es/problem-to-pay-with-giftcard-two-cards-option.md
+++ b/docs/known-issues/es/problem-to-pay-with-giftcard-two-cards-option.md
@@ -18,9 +18,7 @@ internalReference: 393958
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando los usuarios aplican una tarjeta de regalo y luego van a utilizar "Pagar con dos tarjetas" para pagar la diferencia, la pantalla salta y simplemente escoge un valor diferente al elegido.
diff --git a/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md b/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md
index 4f04be86a..c57959745 100644
--- a/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md
+++ b/docs/known-issues/es/problem-while-validating-value-field-when-buying-with-two-cards.md
@@ -18,9 +18,7 @@ internalReference: 460683
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un comprador decide pagar con dos tarjetas de crédito y además quiere cambiar el importe pagado por cada tarjeta, resulta que al escribir caracteres no numéricos en el campo de valor, nuestra validación tiene un comportamiento diferente dependiendo de dónde inserte el usuario este carácter.
diff --git a/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md b/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md
index 413ac1e1b..7fbe974ad 100644
--- a/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md
+++ b/docs/known-issues/es/problem-with-phone-validation-on-mobile-devices.md
@@ -18,9 +18,7 @@ internalReference: 964802
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La validación del campo del teléfono en dispositivos móviles no se comporta como es debido. Cuando se alcanza el número esperado de caracteres, la validación marca correctamente el campo con un check. Sin embargo, cuando se añaden caracteres adicionales y luego se eliminan uno a uno, la validación no reconoce que el recuento de caracteres sigue siendo superior al esperado, marcando incorrectamente la entrada como válida. La validación también marca como válidas las entradas con menos caracteres de los esperados.
diff --git a/docs/known-issues/es/problems-adding-items-to-cart-in-io-that-have-attachments.md b/docs/known-issues/es/problems-adding-items-to-cart-in-io-that-have-attachments.md
index 6c2695cbc..be934fbb9 100644
--- a/docs/known-issues/es/problems-adding-items-to-cart-in-io-that-have-attachments.md
+++ b/docs/known-issues/es/problems-adding-items-to-cart-in-io-that-have-attachments.md
@@ -18,9 +18,7 @@ internalReference: 429724
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md b/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
index d978a40c7..4c65c421d 100644
--- a/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
+++ b/docs/known-issues/es/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
@@ -18,9 +18,7 @@ internalReference: 466491
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Problemas al abrir la página "Gestionar el inventario" por parte del administrador con un mensaje de error:
diff --git a/docs/known-issues/es/problems-with-payment-condition-storage.md b/docs/known-issues/es/problems-with-payment-condition-storage.md
index 84303c8d4..752a0f066 100644
--- a/docs/known-issues/es/problems-with-payment-condition-storage.md
+++ b/docs/known-issues/es/problems-with-payment-condition-storage.md
@@ -18,9 +18,7 @@ internalReference: 377684
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay una cuenta y una subcuenta con el mismo sufijo estamos teniendo problemas para almacenar las Condiciones de Pago cada vez que hay cambios en ellas.
diff --git a/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md b/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md
index a2d60c919..70ea4ddb2 100644
--- a/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md
+++ b/docs/known-issues/es/product-availability-display-delayed-when-using-multiple-sales-channels.md
@@ -18,9 +18,7 @@ internalReference: 949411
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La visualización, para tiendas de portales heredados, de productos en PLPs se basa en el canal de venta de la tienda y sus datos básicos de disponibilidad.
diff --git a/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md b/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
index 8c3c09557..caeda7869 100644
--- a/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
+++ b/docs/known-issues/es/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
@@ -18,9 +18,7 @@ internalReference: 552875
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/product-category-information-from-datalayer-with-a-wrong-sorting.md b/docs/known-issues/es/product-category-information-from-datalayer-with-a-wrong-sorting.md
index 35239da7a..ff5c59e62 100644
--- a/docs/known-issues/es/product-category-information-from-datalayer-with-a-wrong-sorting.md
+++ b/docs/known-issues/es/product-category-information-from-datalayer-with-a-wrong-sorting.md
@@ -18,9 +18,7 @@ internalReference: 328415
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La información de la categoría del producto en el dataLayer en las páginas de pago se muestra en el orden incorrecto. Esto está representado por la propiedad "categoryTree".
diff --git a/docs/known-issues/es/product-comissioning-inconsistent-cache.md b/docs/known-issues/es/product-comissioning-inconsistent-cache.md
index 2e10c8ce3..1ca360915 100644
--- a/docs/known-issues/es/product-comissioning-inconsistent-cache.md
+++ b/docs/known-issues/es/product-comissioning-inconsistent-cache.md
@@ -18,9 +18,7 @@ internalReference: 872364
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Hay, a partir de 2023, dos conjuntos de API distintos para actualizar la información de un vendedor en un mercado, son:
 https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
diff --git a/docs/known-issues/es/product-created-with-id-0.md b/docs/known-issues/es/product-created-with-id-0.md
index ab5c969cf..3d14f1c39 100644
--- a/docs/known-issues/es/product-created-with-id-0.md
+++ b/docs/known-issues/es/product-created-with-id-0.md
@@ -18,9 +18,7 @@ internalReference: 335840
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Es posible crear productos con ID = 0 si utilizan nuestra API o WebService.
diff --git a/docs/known-issues/es/product-highlights-doesnt-work-into-a-product-list.md b/docs/known-issues/es/product-highlights-doesnt-work-into-a-product-list.md
index bdcfd2197..b10569efe 100644
--- a/docs/known-issues/es/product-highlights-doesnt-work-into-a-product-list.md
+++ b/docs/known-issues/es/product-highlights-doesnt-work-into-a-product-list.md
@@ -18,9 +18,7 @@ internalReference: 546844
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay una promoción con el resaltado activado y el producto, que está incluido en esta promoción, está dentro de una lista, como una estantería, no se muestra la insignia que informa de la promoción.
diff --git a/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md b/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md
index f0dbfadd8..323eec466 100644
--- a/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md
+++ b/docs/known-issues/es/product-image-on-admin-changes-with-more-than-70-skus.md
@@ -18,9 +18,7 @@ internalReference: 1003966
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un producto tiene más de 70 variaciones de skus su imagen en admin (y sólo en admin) cambia a una imagen de información:
diff --git a/docs/known-issues/es/product-image-sorting-doesnt-respect-the-catalog-order.md b/docs/known-issues/es/product-image-sorting-doesnt-respect-the-catalog-order.md
index 93ad968bc..dbeee6ebf 100644
--- a/docs/known-issues/es/product-image-sorting-doesnt-respect-the-catalog-order.md
+++ b/docs/known-issues/es/product-image-sorting-doesnt-respect-the-catalog-order.md
@@ -18,9 +18,7 @@ internalReference: 682177
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza el prop para mostrar una imagen diferente al pasar el ratón sobre un componente de resumen de producto actualmente se llama a la API de búsqueda inteligente para devolver las imágenes y con estos datos se mostrará una imagen diferente al pasar el ratón, lo que ocurre actualmente es que el orden en el Catálogo no es necesariamente el mismo orden que devolverá la búsqueda causando divergencias dentro de los resultados esperados.
diff --git a/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 0b9d3b082..c5ebe848e 100644
--- a/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/es/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -18,9 +18,7 @@ internalReference: 486459
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, las APIs para la inserción o actualización de productos del catálogo permiten el carácter "\n" en el textLink
diff --git a/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
index b001e1db1..f372c75c7 100644
--- a/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
+++ b/docs/known-issues/es/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -18,9 +18,7 @@ internalReference: 1044571
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la lista de productos rediseñada del catálogo, uno de los campos de búsqueda es "El nombre del producto contiene". Actualmente, al buscar un nombre de producto con más de un término, pueden darse dos situaciones:
diff --git a/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md b/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
index d37575868..d2cb61961 100644
--- a/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
+++ b/docs/known-issues/es/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
@@ -18,9 +18,7 @@ internalReference: 661089
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/product-page-sessions-not-working.md b/docs/known-issues/es/product-page-sessions-not-working.md
index 65dd4138f..df5d63b79 100644
--- a/docs/known-issues/es/product-page-sessions-not-working.md
+++ b/docs/known-issues/es/product-page-sessions-not-working.md
@@ -18,9 +18,7 @@ internalReference: 961591
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El resumen del administrador tiene alguna información analítica. La información sobre las sesiones de la página de productos debería devolver los valores de este evento, pero a veces devuelve cero.
diff --git a/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md b/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md
index 768cca16f..779d480f6 100644
--- a/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md
+++ b/docs/known-issues/es/product-price-not-considering-default-seller-in-pdp.md
@@ -18,9 +18,7 @@ internalReference: 429888
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al mostrar el precio en PDP, el componente ignora el Vendedor por defecto, considerando el primer vendedor que se registró.
diff --git a/docs/known-issues/es/product-quantity-selector-error-for-high-resolution-screens.md b/docs/known-issues/es/product-quantity-selector-error-for-high-resolution-screens.md
index f45b34121..76690b76c 100644
--- a/docs/known-issues/es/product-quantity-selector-error-for-high-resolution-screens.md
+++ b/docs/known-issues/es/product-quantity-selector-error-for-high-resolution-screens.md
@@ -18,9 +18,7 @@ internalReference: 561921
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al renderizar resoluciones altas, el selector de cantidad no funciona.
diff --git a/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md b/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
index 84d83708f..b37f690e0 100644
--- a/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
+++ b/docs/known-issues/es/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 753484
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No está siendo posible cambiar el sku de un pedido porque el OMS utiliza la API de búsqueda (que está relacionada con el catálogo V1) y las cuentas del portal del vendedor utilizan una nueva versión del catálogo. No se ha implementado ningún proxy en esta área.
diff --git a/docs/known-issues/es/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md b/docs/known-issues/es/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md
index 786f515f4..de0e47e53 100644
--- a/docs/known-issues/es/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md
+++ b/docs/known-issues/es/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md
@@ -18,9 +18,7 @@ internalReference: 753505
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un mismo producto está asociado a múltiples ofertas (por ejemplo, el mismo par de zapatos es ofrecido por diferentes comerciantes), entonces AggregateOffer puede ser usado para enviar esta información a Google de forma que su rastreador no rechace la oferta por precios erróneos.
diff --git a/docs/known-issues/es/product-specification-export-index-out-of-range.md b/docs/known-issues/es/product-specification-export-index-out-of-range.md
index 10c27f670..8cf910212 100644
--- a/docs/known-issues/es/product-specification-export-index-out-of-range.md
+++ b/docs/known-issues/es/product-specification-export-index-out-of-range.md
@@ -18,9 +18,7 @@ internalReference: 481095
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar exportar Especificaciones de Producto desde la UI "Importar y Exportar", si existe algún valor nulo o relación nula en la categoría a exportar, el proceso fallará con un mensaje de "Índice fuera de Rango". En otras palabras, la categoría debe tener registrado directamente a su nivel un campo de producto, productos y productos con valores asociados.
diff --git a/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
index 2b75f46c3..a5e5cddbc 100644
--- a/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
+++ b/docs/known-issues/es/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -18,9 +18,7 @@ internalReference: 926593
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el módulo Recogida, el filtro Especificaciones del producto no funciona correctamente cuando la especificación tiene el tipo "Texto" y "Texto grande". Cuando se selecciona este tipo de especificación, se abre un cuadro de texto para insertar los posibles valores separados por una coma, tabulador o enter. Sin embargo, cuando se teclea un solo carácter, el sistema lo asume como valor incluso sin separar los términos.
diff --git a/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md b/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
index 5b69b6890..26e793e48 100644
--- a/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
+++ b/docs/known-issues/es/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
@@ -18,9 +18,7 @@ internalReference: 918687
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el módulo de recogida, al utilizar los filtros para añadir productos, el filtro Especificación de producto no lista los campos registrados en la categoría raíz
diff --git a/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
index 912a6bd8c..016d94c6f 100644
--- a/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
+++ b/docs/known-issues/es/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -18,9 +18,7 @@ internalReference: 998658
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al importar especificaciones de producto, los tipos con valores pre-registrados (como Checkbox o Radio) activan la indexación del producto, pero cuando el tipo es "Texto" no ocurre lo mismo.
diff --git a/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md b/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
index 78e5c47ba..248aac4f3 100644
--- a/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
+++ b/docs/known-issues/es/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
@@ -18,9 +18,7 @@ internalReference: 470143
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vtex.search-resolver@1.x guarda la información de un producto en cuanto a su porcentaje de impuestos, pero el valor registrado puede ser ligeramente incorrecto debido al redondeo de los números.
diff --git a/docs/known-issues/es/product-unavailable-even-with-franchised-stock.md b/docs/known-issues/es/product-unavailable-even-with-franchised-stock.md
index f844ce46e..10f4d6367 100644
--- a/docs/known-issues/es/product-unavailable-even-with-franchised-stock.md
+++ b/docs/known-issues/es/product-unavailable-even-with-franchised-stock.md
@@ -18,9 +18,7 @@ internalReference: 404499
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si el producto está agotado en el mercado, en cualquier otro vendedor habitual y la bandera **mostrar agotado** está desmarcada, el producto se mostrará agotado en el portal aunque tenga stock en las cuentas de las franquicias. Es posible añadir el producto a la cesta.
diff --git a/docs/known-issues/es/productclick-event-considers-the-incorrect-sku-id.md b/docs/known-issues/es/productclick-event-considers-the-incorrect-sku-id.md
index 411f796a7..175e1fb53 100644
--- a/docs/known-issues/es/productclick-event-considers-the-incorrect-sku-id.md
+++ b/docs/known-issues/es/productclick-event-considers-the-incorrect-sku-id.md
@@ -18,9 +18,7 @@ internalReference: 788145
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El evento productClick considera el Id SKU incorrecto cuando se utiliza el bloque Selector SKU de Resumen de Producto. Siempre utilizará el primer SKU de la lista de productos.
diff --git a/docs/known-issues/es/productclick-event-not-triggering-in-searchbar.md b/docs/known-issues/es/productclick-event-not-triggering-in-searchbar.md
index 76fab0d57..8eb7ff711 100644
--- a/docs/known-issues/es/productclick-event-not-triggering-in-searchbar.md
+++ b/docs/known-issues/es/productclick-event-not-triggering-in-searchbar.md
@@ -18,9 +18,7 @@ internalReference: 742754
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md b/docs/known-issues/es/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md
index 1940b59ca..06ad65729 100644
--- a/docs/known-issues/es/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md
+++ b/docs/known-issues/es/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md
@@ -18,9 +18,7 @@ internalReference: 568409
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md b/docs/known-issues/es/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md
index 036a4bfd1..6ad54cc1e 100644
--- a/docs/known-issues/es/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md
+++ b/docs/known-issues/es/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md
@@ -18,9 +18,7 @@ internalReference: 717617
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la tienda "separa" el SKU de un producto para mostrarlo individualmente en el escaparate, el ProductImpression del GTM sólo ve los productos por su productID, no por cada SKUId. Así que si el producto tiene 3 SKUs diferentes en la página de búsqueda, el ProductImpression sólo lo mostrará como un producto.
diff --git a/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md b/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
index b5b425f22..f889fbd26 100644
--- a/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
+++ b/docs/known-issues/es/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
@@ -18,9 +18,7 @@ internalReference: 337069
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si una tienda utiliza el componente de lista de productos de Store Framework, utilizado en el minicart, los artículos del carrito pueden duplicarse al aumentar la cantidad de un artículo que tiene un adjunto (itemAttachment).
diff --git a/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md b/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
index b8fd1b88c..db10e334c 100644
--- a/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
+++ b/docs/known-issues/es/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
@@ -18,9 +18,7 @@ internalReference: 762525
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el vendedor envía un sku al marketplace, el sistema Matcher se encarga de consultar el catálogo del marketplace y verificar si ya existe un producto similar al skus del vendedor.
diff --git a/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md b/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md
index c0ea9906a..cedb976bd 100644
--- a/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md
+++ b/docs/known-issues/es/products-showing-flag-and-discount-after-promotion-ended.md
@@ -18,9 +18,7 @@ internalReference: 383911
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces las banderas de promoción y los descuentos se muestran en PLP y PLP después de la fecha de caducidad de la promoción. Esto ocurre porque la promoción no activa la indexación del producto, resultando en la exposición errónea del descuento.
diff --git a/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md b/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
index 60d08408d..1211db8c6 100644
--- a/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
+++ b/docs/known-issues/es/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 1045184
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los productos con precio cero son mostrados como no disponibles por la Búsqueda Inteligente. A diferencia de un producto sin precio registrado, el precio fijado como cero define un producto libre.
diff --git a/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md b/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
index fbb0bf813..3daa3911a 100644
--- a/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
+++ b/docs/known-issues/es/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
@@ -18,9 +18,7 @@ internalReference: 889676
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vendedor puede enviar un producto con múltiples variaciones de sku.
diff --git a/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
index 600acf3d9..7ab69461f 100644
--- a/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
+++ b/docs/known-issues/es/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -18,9 +18,7 @@ internalReference: 982830
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un producto cuyo precio de venta sea inferior a su precio de lista será marcado como parte de una promoción a efectos de filtrado de búsqueda. Los productos con algún multiplicador de unidades pueden dar lugar a un cálculo erróneo que puede afectar a esta comparación, dando lugar a que reciban erróneamente esta bandera.
diff --git a/docs/known-issues/es/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md b/docs/known-issues/es/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md
index d1faed836..d24a8e231 100644
--- a/docs/known-issues/es/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md
+++ b/docs/known-issues/es/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md
@@ -18,9 +18,7 @@ internalReference: 740431
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los productos sin SKU no se devuelven en la administración cuando se busca por ID de producto
diff --git a/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md b/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
index 3ae184535..93e4c0c63 100644
--- a/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
+++ b/docs/known-issues/es/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
@@ -18,9 +18,7 @@ internalReference: 495741
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los productos que no tienen stock en los vendedores de WL aparecen al final del PLP.
diff --git a/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md b/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md
index 58a8833a0..35acb30cb 100644
--- a/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md
+++ b/docs/known-issues/es/productsku-upload-form-allows-utf16-format-uploaddownload.md
@@ -18,9 +18,7 @@ internalReference: 493402
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, si un usuario intenta cargar una lista de SKU en el formulario de promoción habitual utilizando un archivo .txt, si el archivo cargado está en el formato de codificación UTF-16, también lo estará el archivo descargado después.
diff --git a/docs/known-issues/es/productsskus-import-does-not-support-lb.md b/docs/known-issues/es/productsskus-import-does-not-support-lb.md
index 791faebfe..dd52d99a6 100644
--- a/docs/known-issues/es/productsskus-import-does-not-support-lb.md
+++ b/docs/known-issues/es/productsskus-import-does-not-support-lb.md
@@ -18,9 +18,7 @@ internalReference: 337860
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la hoja de catálogo de Productos y SKUs no soporta la unidad de medida 'lb'. `/admin/Site/Relatorio_Skus.aspx`
diff --git a/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md b/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
index 913345533..2ff40818c 100644
--- a/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
+++ b/docs/known-issues/es/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
@@ -18,9 +18,7 @@ internalReference: 1016582
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al configurar 'ignoreProfileData' a través de la API Ignorar datos de perfil en el pago, si el comprador tiene un perfil completo pero no ha iniciado sesión, los datos se cargarán vacíos en la interfaz de usuario.
diff --git a/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md b/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
index c34999c25..121cf434c 100644
--- a/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
+++ b/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
@@ -18,9 +18,7 @@ internalReference: 842575
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-profile-data.md b/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-profile-data.md
index 83182c681..fd3845e52 100644
--- a/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-profile-data.md
+++ b/docs/known-issues/es/promotion-item-will-not-show-splitted-after-adding-profile-data.md
@@ -18,9 +18,7 @@ internalReference: 842575
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El comportamiento esperado al aplicar una promoción Más por Menos es tener el artículo promocional separado de los artículos normales, pero los artículos se agruparán después de añadir un correo electrónico a la caja.
diff --git a/docs/known-issues/es/promotion-more-for-less-not-working-alongside-regular-promotion.md b/docs/known-issues/es/promotion-more-for-less-not-working-alongside-regular-promotion.md
index 73cbae459..73122e337 100644
--- a/docs/known-issues/es/promotion-more-for-less-not-working-alongside-regular-promotion.md
+++ b/docs/known-issues/es/promotion-more-for-less-not-working-alongside-regular-promotion.md
@@ -18,9 +18,7 @@ internalReference: 637586
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El descuento final en el carrito de la compra no es correcto cuando se está aplicando una promoción Más por Menos junto con una promoción normal. El descuento es mayor de lo esperado.
diff --git a/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md b/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
index 679f00618..79070b58b 100644
--- a/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
+++ b/docs/known-issues/es/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
@@ -18,9 +18,7 @@ internalReference: 965484
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se establece una promoción de suscripción en el módulo de suscripción, el comerciante tiene la posibilidad de elegir la frecuencia con la que se aplicará esta promoción en la suscripción.
diff --git a/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md b/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
index 92974374b..789a9dd70 100644
--- a/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
+++ b/docs/known-issues/es/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
@@ -18,9 +18,7 @@ internalReference: 949389
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md b/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
index f4b586ecd..b7649ac18 100644
--- a/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
+++ b/docs/known-issues/es/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 315485
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las promociones e impuestos restringidos por métodos de envío no funcionan para los Vendedores de Marca Blanca. No se aplicarán en la solicitud de simulación (utilizada para el carrito y el pago) porque la solicitud de marketplace no especifica la `selectedSla`, por lo que sus valores no se presentarán al usuario.
diff --git a/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md b/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
index b41049750..7eb8deb0f 100644
--- a/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
+++ b/docs/known-issues/es/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
@@ -18,9 +18,7 @@ internalReference: 781523
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La página del producto sólo muestra el precio SKU con algunas promociones, que no incluyen las condiciones específicas de los métodos de pago ni el número de plazos. Estos sólo se aplican durante el pago, después de que el usuario haya optado explícitamente por utilizar una determinada condición de pago.
diff --git a/docs/known-issues/es/promotions-microrounding-divergence.md b/docs/known-issues/es/promotions-microrounding-divergence.md
index fa2fe08ea..d12971454 100644
--- a/docs/known-issues/es/promotions-microrounding-divergence.md
+++ b/docs/known-issues/es/promotions-microrounding-divergence.md
@@ -18,9 +18,7 @@ internalReference: 957369
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El módulo de promociones redondea los descuentos hasta en 3 dígitos significativos, lo que puede, en escenarios muy concretos, suponer ligeras divergencias en el precio final de un carrito.
diff --git a/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md b/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
index d5f937a23..4c624bdb6 100644
--- a/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
+++ b/docs/known-issues/es/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
@@ -18,9 +18,7 @@ internalReference: 888304
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Las listas de productos y los resultados de búsqueda pueden estar mal ordenados/filtrados al utilizar la ordenación o el filtrado por precio o descuento si hay precios de artículos obsoletos a nivel de índice, incluso si el escaparate muestra el precio correcto.
 
diff --git a/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md b/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md
index 4884144e8..2becb6e70 100644
--- a/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md
+++ b/docs/known-issues/es/promotions-ui-loading-wrong-currency-information.md
@@ -18,9 +18,7 @@ internalReference: 718908
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al abrir el módulo de Promociones muy rápidamente y muchas veces seguidas aparece un comportamiento erróneo en la UI.
diff --git a/docs/known-issues/es/property-blockclass-from-infocard-not-working.md b/docs/known-issues/es/property-blockclass-from-infocard-not-working.md
index d9c21eb5c..39a935d5d 100644
--- a/docs/known-issues/es/property-blockclass-from-infocard-not-working.md
+++ b/docs/known-issues/es/property-blockclass-from-infocard-not-working.md
@@ -18,9 +18,7 @@ internalReference: 743730
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md b/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
index 3034be878..320a65610 100644
--- a/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
+++ b/docs/known-issues/es/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
@@ -18,9 +18,7 @@ internalReference: 909925
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md b/docs/known-issues/es/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md
index b7949fc99..3d29271f6 100644
--- a/docs/known-issues/es/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md
+++ b/docs/known-issues/es/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md
@@ -18,19 +18,13 @@ internalReference: 580333
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md b/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md
index fe70ba900..e4913394c 100644
--- a/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md
+++ b/docs/known-issues/es/pt-message-is-shown-in-the-license-manager-module.md
@@ -18,9 +18,7 @@ internalReference: 620782
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/publication-attributes-in-mercado-livre-are-not-integrated.md b/docs/known-issues/es/publication-attributes-in-mercado-livre-are-not-integrated.md
index e8e3c70f5..03a771909 100644
--- a/docs/known-issues/es/publication-attributes-in-mercado-livre-are-not-integrated.md
+++ b/docs/known-issues/es/publication-attributes-in-mercado-livre-are-not-integrated.md
@@ -32,7 +32,5 @@ Se consigue realizar esta integración por fuera de VTEX Bridge, utilizando las
 
 Se consigue también cargar los atributos manualmente en MercadoLibre.
 
-<div class="alert alert-info">
-Este problema ya ha sido resuelto por nuestro equipo. <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA">Sepa más.</a>
-</div>
+>ℹ️ Este problema ya ha sido resuelto por nuestro equipo. [Sepa más.](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA)
 
diff --git a/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md b/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
index a99c97965..afa3bfc4d 100644
--- a/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
+++ b/docs/known-issues/es/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
@@ -18,9 +18,7 @@ internalReference: 314551
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md b/docs/known-issues/es/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md
index 9960b58fd..39aab149c 100644
--- a/docs/known-issues/es/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md
+++ b/docs/known-issues/es/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md
@@ -18,9 +18,7 @@ internalReference: 648604
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
index ce46174b2..6ef0b3933 100644
--- a/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
+++ b/docs/known-issues/es/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -18,9 +18,7 @@ internalReference: 449341
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar cualquier promoción que provoque la división de un artículo y se seleccionen dos vendedores diferentes, al hacer clic en "Comprar ahora" aparecerá el mensaje "El tipo de carga ha cambiado", lo que impedirá que se complete la compra.
diff --git a/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md b/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
index 9f88c7690..6e2c032b6 100644
--- a/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
+++ b/docs/known-issues/es/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
@@ -18,9 +18,7 @@ internalReference: 313945
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un alto volumen de errores en el proceso de creación de un pedido con el mensaje "_El campo del nombre del destinatario en el archivo adjunto de envío no es válido_". Parece ser algo relacionado con nuestra interfaz de usuario de pago. No tenemos recursos para entender hasta qué punto está afectando o bloqueando las ventas.
diff --git a/docs/known-issues/es/put-price-overwrites-kit-price-logic.md b/docs/known-issues/es/put-price-overwrites-kit-price-logic.md
index 648104aac..3f7322aca 100644
--- a/docs/known-issues/es/put-price-overwrites-kit-price-logic.md
+++ b/docs/known-issues/es/put-price-overwrites-kit-price-logic.md
@@ -18,9 +18,7 @@ internalReference: 404486
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La composición del precio del KIT debe basarse en el cálculo de sus componentes y sus cantidades.
diff --git a/docs/known-issues/es/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md b/docs/known-issues/es/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md
index 22874ba8a..7201cc91a 100644
--- a/docs/known-issues/es/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md
+++ b/docs/known-issues/es/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md
@@ -18,9 +18,7 @@ internalReference: 402976
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 En el componente ["vtex.product-list"](https://github.com/vtex-apps/product-list), utilizado en IO/SF Minicart ([vtex.minicart](https://github.com/vtex-apps/minicart) v2) o en "Cart v0" ([vtex.checkout-cart](https://github.com/vtex-apps/checkout-cart)), cuando un carrito tiene el mismo artículo troceado en más de una ocurrencia (por ejemplo cuando se necesita para el prorrateo de descuentos o quizás cuando tiene itemAttachments), para cambiar la cantidad para su segunda ocurrencia se llamará a la API para su primera ocurrencia, por lo que la cantidad sumada para el artículo será incorrecta.
 
diff --git a/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md b/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
index 541487239..a48150a60 100644
--- a/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
+++ b/docs/known-issues/es/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
@@ -18,9 +18,7 @@ internalReference: 659909
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Básicamente, hay una función que recibe el estado actualizado del valor que está siendo controlado en la pantalla por el usuario (es un useState). Esta función se utiliza en todo el componente para manejar las actualizaciones del estado de la cantidad. Para que este estado se actualice automáticamente cuando el usuario supere la cantidad devuelta en el contexto, relacionada con la disponibilidad del artículo, se pasa dentro de un useEffect.
diff --git a/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md b/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md
index d26e321c1..c05ddce38 100644
--- a/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md
+++ b/docs/known-issues/es/quantity-selector-wont-let-me-change-the-value-by-typing.md
@@ -18,9 +18,7 @@ internalReference: 1057544
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El componente selector de cantidades en Faststore está presentando un bug. Si el valor mínimo de un producto es 10 y quiero teclear 15, el selector no me deja borrar el 0 porque nos dejará con 1, y sería un valor inferior a la cantidad mínima. Si quiero escribir 15 tengo que escribir 150 y entonces puedo borrar el 0.
diff --git a/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md b/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
index 7633a8c79..92e937792 100644
--- a/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
+++ b/docs/known-issues/es/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
@@ -18,9 +18,7 @@ internalReference: 704458
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si alcanzas la cantidad disponible del producto haciendo clic más de una vez, el componente tarda demasiado en avisarte y ni siquiera actualiza el selector de cantidad con la cantidad máxima disponible.
diff --git a/docs/known-issues/es/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/es/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
index a74ba65ab..672b18578 100644
--- a/docs/known-issues/es/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
+++ b/docs/known-issues/es/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -18,9 +18,7 @@ internalReference: 541149
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md b/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
index d4f0c4432..cedba6ff0 100644
--- a/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
+++ b/docs/known-issues/es/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
@@ -18,9 +18,7 @@ internalReference: 562472
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un producto vendido por otro vendedor en el catálogo del mercado está disponible para ser vendido en el canal de ventas de este vendedor.
diff --git a/docs/known-issues/es/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md b/docs/known-issues/es/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md
index 33650fdee..883dd0183 100644
--- a/docs/known-issues/es/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md
+++ b/docs/known-issues/es/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md
@@ -18,9 +18,7 @@ internalReference: 668122
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función de exportación para recuperar una hoja de cálculo con los skus pendientes, aprobados o rechazados por vendedor no funciona cuando el admin está configurado en cualquier otro idioma que no sea PT, EN, ES.
diff --git a/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md b/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md
index 2353f6b07..8520602c4 100644
--- a/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md
+++ b/docs/known-issues/es/received-skus-filter-do-not-work-with-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 944533
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar filtrar los skus en el módulo de Skus Recibidos, el marketplace puede elegir filtrar por vendedor, categoría y/o marca.
diff --git a/docs/known-issues/es/received-skus-review-tab-missing-products.md b/docs/known-issues/es/received-skus-review-tab-missing-products.md
index 22bb8d00b..bbd4f6293 100644
--- a/docs/known-issues/es/received-skus-review-tab-missing-products.md
+++ b/docs/known-issues/es/received-skus-review-tab-missing-products.md
@@ -18,9 +18,7 @@ internalReference: 939877
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las ofertas enviadas por los vendedores pueden eventualmente ir a la pestaña de Revisión de los Skus Recibidos del Marketplace dependiendo si pasaron o no las reglas de Calidad de la Oferta.
diff --git a/docs/known-issues/es/redirection-with-parameters-in-cms-builder-does-not-work.md b/docs/known-issues/es/redirection-with-parameters-in-cms-builder-does-not-work.md
index 90d18955f..02b37a2f9 100644
--- a/docs/known-issues/es/redirection-with-parameters-in-cms-builder-does-not-work.md
+++ b/docs/known-issues/es/redirection-with-parameters-in-cms-builder-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 593906
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la redirección mediante parámetros genera un error a pesar de que el administrador de URL Bilder dice que es posible utilizar parámetros.
diff --git a/docs/known-issues/es/redirects-are-being-counted-multiple-times.md b/docs/known-issues/es/redirects-are-being-counted-multiple-times.md
index a2fd35390..3b7b16aec 100644
--- a/docs/known-issues/es/redirects-are-being-counted-multiple-times.md
+++ b/docs/known-issues/es/redirects-are-being-counted-multiple-times.md
@@ -18,9 +18,7 @@ internalReference: 1066548
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar cargar un archivo con más de 200 redirecciones, el frente entra en un bucle y lee esas redirecciones tres veces. Esto puede llevar a más redirecciones en el mensaje de error en pantalla o en el modal de carga. Las redirecciones no se están duplicando, pero las estamos leyendo más de una vez.
diff --git a/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md b/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
index 8dc6e1b89..58b7173c6 100644
--- a/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
+++ b/docs/known-issues/es/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
@@ -18,9 +18,7 @@ internalReference: 927041
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En Faststore, si accede a un enlace de previsualización con el / al final de la URL el enlace será redirigido a una página como esta https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
diff --git a/docs/known-issues/es/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md b/docs/known-issues/es/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md
index 6854e6223..cdb0e4e06 100644
--- a/docs/known-issues/es/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md
+++ b/docs/known-issues/es/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md
@@ -18,9 +18,7 @@ internalReference: 577825
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El usuario no puede iniciar sesión después de cambiar la contraseña temporal y es dirigido a la pantalla para solicitar el acceso
diff --git a/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md b/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md
index 797c41328..30ffbaada 100644
--- a/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md
+++ b/docs/known-issues/es/refid-behavior-not-consistent-between-api-and-ui.md
@@ -18,9 +18,7 @@ internalReference: 910050
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md b/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
index af099feeb..e9b26b97d 100644
--- a/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
+++ b/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
@@ -18,9 +18,7 @@ internalReference: 893588
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un conflicto de Regex hace que identifiquemos erróneamente la marca de las tarjetas en la caja.
diff --git a/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-the-cards-brand.md b/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-the-cards-brand.md
index 8d1d26199..40ae7bb51 100644
--- a/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-the-cards-brand.md
+++ b/docs/known-issues/es/regex-conflict-causes-us-to-misidentify-the-cards-brand.md
@@ -18,9 +18,7 @@ internalReference: 316213
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md b/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md
index 88145c2c0..7f9a1e4d2 100644
--- a/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md
+++ b/docs/known-issues/es/region-api-returns-seller-list-due-to-cache.md
@@ -18,9 +18,7 @@ internalReference: 969692
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza una estructura de subcuenta con región, si la API Obtener vendedores por región o dirección se utiliza en ambas cuentas para el mismo canal de ventas, y una de ellas no está disponible para ese canal de ventas, devolverá una lista de vendedores debido a la caché.
diff --git a/docs/known-issues/es/regionalization-or-trade-policies-arent-considered-while-filtering-or.md b/docs/known-issues/es/regionalization-or-trade-policies-arent-considered-while-filtering-or.md
index bd22e3fc6..b638e0b46 100644
--- a/docs/known-issues/es/regionalization-or-trade-policies-arent-considered-while-filtering-or.md
+++ b/docs/known-issues/es/regionalization-or-trade-policies-arent-considered-while-filtering-or.md
@@ -18,9 +18,7 @@ internalReference: 571101
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Cuando se utiliza la búsqueda inteligente (a través de PLP o incluso de su API) junto con la regionalización (regionId) o la variación de la política comercial, la clasificación y el filtrado de artículos por precio no funcionan correctamente.
 
diff --git a/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 70adc74bb..139f26875 100644
--- a/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/es/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 551402
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md b/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
index 8b17c1004..bb8b07178 100644
--- a/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
+++ b/docs/known-issues/es/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
@@ -18,9 +18,7 @@ internalReference: 870845
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario registrado (no logueado) inicia el checkout con Entrega como opción de envío, y posteriormente cambia a recolección, al intentar finalizar el checkout aparece el mensaje de error "El campo Número en el adjunto de envío no es válido" y no permite realizar el pedido.
diff --git a/docs/known-issues/es/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md b/docs/known-issues/es/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md
index 3ea301381..81389383d 100644
--- a/docs/known-issues/es/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md
+++ b/docs/known-issues/es/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 445569
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md b/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
index 40353c513..0795a109b 100644
--- a/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
+++ b/docs/known-issues/es/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
@@ -18,9 +18,7 @@ internalReference: 626031
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/render-component-issues-on-site-editor.md b/docs/known-issues/es/render-component-issues-on-site-editor.md
index 73581451d..d41a7be49 100644
--- a/docs/known-issues/es/render-component-issues-on-site-editor.md
+++ b/docs/known-issues/es/render-component-issues-on-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 415674
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a la cantidad de información en la página, el editor del sitio puede tener problemas al renderizar bloques. Este comportamiento ocurre de forma intermitente, a veces los componentes no se renderizan y otras veces se renderizan dos veces. Puede ocurrir que no aparezca ningún bloque en el editor del sitio:
diff --git a/docs/known-issues/es/reorder-collection-failing-for-large-collections.md b/docs/known-issues/es/reorder-collection-failing-for-large-collections.md
index 8d9fce860..8f62211f5 100644
--- a/docs/known-issues/es/reorder-collection-failing-for-large-collections.md
+++ b/docs/known-issues/es/reorder-collection-failing-for-large-collections.md
@@ -18,9 +18,7 @@ internalReference: 408140
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la nueva interfaz de administración de colecciones, cuando un usuario intenta reordenar la visualización de pedidos de productos, la mutación GraphQL del catálogo que realiza esta acción suele fallar
diff --git a/docs/known-issues/es/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md b/docs/known-issues/es/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md
index e3af4f76f..387e9f387 100644
--- a/docs/known-issues/es/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md
+++ b/docs/known-issues/es/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md
@@ -18,9 +18,7 @@ internalReference: 367339
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al llegar a la caja con más de 20 artículos, los artículos mostrados en el resumen de la compra (lista de artículos superior derecha) pueden estar duplicados. Los totalizadores e incluso la API son correctos. El escenario no ocurre en la lista principal de artículos (paso del carrito).
diff --git a/docs/known-issues/es/replacing-orders-with-different-sales-channel.md b/docs/known-issues/es/replacing-orders-with-different-sales-channel.md
index f7b3078d7..824d51824 100644
--- a/docs/known-issues/es/replacing-orders-with-different-sales-channel.md
+++ b/docs/known-issues/es/replacing-orders-with-different-sales-channel.md
@@ -18,9 +18,7 @@ internalReference: 982965
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hemos identificado que no es posible reemplazar un SKU en el pedido si el Canal de Ventas (SC), igual a 1, no está disponible para la cuenta.
diff --git a/docs/known-issues/es/replicated-pending-payment-emails.md b/docs/known-issues/es/replicated-pending-payment-emails.md
index 7c0f497d2..c5faa89b6 100644
--- a/docs/known-issues/es/replicated-pending-payment-emails.md
+++ b/docs/known-issues/es/replicated-pending-payment-emails.md
@@ -18,9 +18,7 @@ internalReference: 348932
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay algunos pedidos que tienen una réplica de correos electrónicos de pago pendiente en pocos minutos. Hasta incluso diez correos electrónicos.
diff --git a/docs/known-issues/es/request-capture-not-registering-new-events-when-using-legacy-stores.md b/docs/known-issues/es/request-capture-not-registering-new-events-when-using-legacy-stores.md
index e748f5583..5d157c50b 100644
--- a/docs/known-issues/es/request-capture-not-registering-new-events-when-using-legacy-stores.md
+++ b/docs/known-issues/es/request-capture-not-registering-new-events-when-using-legacy-stores.md
@@ -18,9 +18,7 @@ internalReference: 604254
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se utilizan los almacenes VTEX del portal (almacenes IO no VTEX) la aplicación de captura de solicitudes no está registrando eventos específicamente para las visitas a la página del producto.
diff --git a/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md b/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md
index ec15c43af..b88d52b88 100644
--- a/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md
+++ b/docs/known-issues/es/request-routing-is-inconsistent-when-running-ab-tests.md
@@ -18,9 +18,7 @@ internalReference: 931246
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Las peticiones HTTP de navegación de tienda no respetan la cookie de selección de espacio de trabajo durante la sesión. De hecho, durante una única sesión, un usuario puede recibir respuestas de todos los espacios de trabajo que se estén probando.
 
diff --git a/docs/known-issues/es/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md b/docs/known-issues/es/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md
index 9ef36f83b..3102ae3d5 100644
--- a/docs/known-issues/es/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md
+++ b/docs/known-issues/es/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md
@@ -18,9 +18,7 @@ internalReference: 763359
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Restringir la cabecera de la Política de Seguridad de Contenidos puede provocar que no se carguen los archivos de checkout. Por ejemplo, la configuración `default-src 'self'` puede provocar que no se carguen los archivos procedentes de vtex.com
diff --git a/docs/known-issues/es/retrieve-users-orders-api-does-not-return-paging.md b/docs/known-issues/es/retrieve-users-orders-api-does-not-return-paging.md
index c441eccb5..2cb31fb8f 100644
--- a/docs/known-issues/es/retrieve-users-orders-api-does-not-return-paging.md
+++ b/docs/known-issues/es/retrieve-users-orders-api-does-not-return-paging.md
@@ -18,9 +18,7 @@ internalReference: 516699
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md b/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
index dcf8e815f..8be8cf767 100644
--- a/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
+++ b/docs/known-issues/es/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
@@ -18,9 +18,7 @@ internalReference: 1050294
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Nuestros sistemas integrados (OMS/SNO/UI) no fueron diseñados para utilizar la misma información para la correlación para mostrar la información correcta cuando un iten con el mismo SKU fue creado en diferente matriz uniqueid. Esto sucede porque algunos sistemas utilizan skuid y otros itemindex.
diff --git a/docs/known-issues/es/returned-package-as-delivering-to-final-customer-on-my-account.md b/docs/known-issues/es/returned-package-as-delivering-to-final-customer-on-my-account.md
index cb7f2aa0b..51053444b 100644
--- a/docs/known-issues/es/returned-package-as-delivering-to-final-customer-on-my-account.md
+++ b/docs/known-issues/es/returned-package-as-delivering-to-final-customer-on-my-account.md
@@ -18,9 +18,7 @@ internalReference: 415482
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un escenario en el que el paquete devuelto se muestra como entregado en la página **Mi Cuenta > Mis Pedidos**. Parece que se va a entregar más de un paquete al cliente en lugar de mostrar que el paquete ya fue entregado al cliente y que se generó un nuevo paquete que simboliza la devolución.
diff --git a/docs/known-issues/es/review-flow-for-updatestock-netshoes.md b/docs/known-issues/es/review-flow-for-updatestock-netshoes.md
index ee421b548..b07631dd1 100644
--- a/docs/known-issues/es/review-flow-for-updatestock-netshoes.md
+++ b/docs/known-issues/es/review-flow-for-updatestock-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 646869
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Flujo de revisión de UpdateStock
diff --git a/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md b/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
index a79b27780..033ae409a 100644
--- a/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
+++ b/docs/known-issues/es/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
@@ -18,9 +18,7 @@ internalReference: 844079
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El valor de la recompensa puede no ser o tener un valor diferente añadido a la tarjeta regalo del comprador cuando la promoción está configurada para aplicar el importe de la recompensa cuando el estado del pedido cambia a pago aprobado.
diff --git a/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md b/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md
index ed54697d0..f28e9df6e 100644
--- a/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md
+++ b/docs/known-issues/es/rewriter-is-not-receiving-url-updates.md
@@ -18,9 +18,7 @@ internalReference: 1066527
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se cambia/elimina una URL en el catálogo, la reescritura no recibe este cambio. Dado que la reescritura no recibe ninguna notificación al respecto, la URL sigue apuntando al tipo incorrecto, lo que también puede provocar problemas en el SI.
diff --git a/docs/known-issues/es/rounding-of-totalvalue-in-listorders.md b/docs/known-issues/es/rounding-of-totalvalue-in-listorders.md
index 2c8dba7bc..9f45c7bc0 100644
--- a/docs/known-issues/es/rounding-of-totalvalue-in-listorders.md
+++ b/docs/known-issues/es/rounding-of-totalvalue-in-listorders.md
@@ -18,9 +18,7 @@ internalReference: 756314
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando consultamos el valor del pedido a través de la UI, nos muestra un valor y cuando lo consultamos a través de la API Get Orders, vemos un valor 0.01 superior. Este comportamiento se produce debido al redondeo realizado en la base de datos. Sin embargo, este comportamiento no afecta al valor total del pedido, es sólo una visualización en el ListOrders, el valor total del pedido sigue siendo correcto.
diff --git a/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md b/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
index aa1f2e4b3..ecf63ea21 100644
--- a/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
+++ b/docs/known-issues/es/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
@@ -18,9 +18,7 @@ internalReference: 968349
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md b/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
index 4f8bd30f0..902f294db 100644
--- a/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
+++ b/docs/known-issues/es/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
@@ -18,9 +18,7 @@ internalReference: 927747
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En Logística, el primer criterio de desempate cuando el sistema está eligiendo la ruta (almacén + muelle + política de envío), está relacionado con el número de paquetes necesarios para esta ruta específica, menos paquetes significa que la ruta debería ser mejor.
diff --git a/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
index a83989da9..63dbcef83 100644
--- a/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
+++ b/docs/known-issues/es/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -18,9 +18,7 @@ internalReference: 866933
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El canal de ventas configurado en los Ajustes de Organizaciones B2B no se guarda en los Detalles de la Organización.
diff --git a/docs/known-issues/es/sales-channel-info-divergent-between-ui-and-api.md b/docs/known-issues/es/sales-channel-info-divergent-between-ui-and-api.md
index 4a5f99338..b2d3584cc 100644
--- a/docs/known-issues/es/sales-channel-info-divergent-between-ui-and-api.md
+++ b/docs/known-issues/es/sales-channel-info-divergent-between-ui-and-api.md
@@ -18,9 +18,7 @@ internalReference: 802560
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces la información sobre el canal de ventas puede ser diferente dependiendo de dónde esté consultando el cliente.
diff --git a/docs/known-issues/es/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md b/docs/known-issues/es/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md
index f77d60591..5b5d867cc 100644
--- a/docs/known-issues/es/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md
+++ b/docs/known-issues/es/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md
@@ -18,9 +18,7 @@ internalReference: 718470
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/save-button-disabled-when-modifying-imported-search-synonyms.md b/docs/known-issues/es/save-button-disabled-when-modifying-imported-search-synonyms.md
index 5d38563c2..b6bb74d13 100644
--- a/docs/known-issues/es/save-button-disabled-when-modifying-imported-search-synonyms.md
+++ b/docs/known-issues/es/save-button-disabled-when-modifying-imported-search-synonyms.md
@@ -18,9 +18,7 @@ internalReference: 508893
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar hacer cualquier cambio en una configuración de sinónimos que fue importada previamente por un archivo csv, el botón de guardar siempre se desactiva, sin importar el cambio:
diff --git a/docs/known-issues/es/scheduled-banners-doesnt-work-properly.md b/docs/known-issues/es/scheduled-banners-doesnt-work-properly.md
index d119550c6..ddd5a1eff 100644
--- a/docs/known-issues/es/scheduled-banners-doesnt-work-properly.md
+++ b/docs/known-issues/es/scheduled-banners-doesnt-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 400194
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al programar un banner en el CMS no funciona como se pretende y muchas veces el banner se bloquea o no muestra toda la información que contiene.
diff --git a/docs/known-issues/es/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md b/docs/known-issues/es/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md
index 785d4edce..249472ebd 100644
--- a/docs/known-issues/es/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md
+++ b/docs/known-issues/es/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md
@@ -18,9 +18,7 @@ internalReference: 770250
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se configura una promoción de valor máximo de envío, si empieza a cambiar entre entrega estándar y entrega programada varias veces, puede haber un precio de entrega programada diferente en la interfaz de usuario.
diff --git a/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md b/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md
index f849da5a6..7eb23caa3 100644
--- a/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md
+++ b/docs/known-issues/es/schema-validation-failing-for-custom-types-in-headless-cms.md
@@ -18,9 +18,7 @@ internalReference: 903687
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md b/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md
index 491b2b175..52fcb16aa 100644
--- a/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md
+++ b/docs/known-issues/es/scroll-issue-when-zooming-after-search-page-render.md
@@ -18,9 +18,7 @@ internalReference: 979464
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md b/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
index e07b347a4..d6435ee05 100644
--- a/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
+++ b/docs/known-issues/es/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
@@ -18,9 +18,7 @@ internalReference: 985097
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al deslizar la imagen de un producto en la vista rápida en el móvil cuando hay un diseño deslizante en el fondo, ambos deslizadores se van a mover a la siguiente en lugar de sólo la imagen en la vista rápida
diff --git a/docs/known-issues/es/search-analytics-duplicated-events.md b/docs/known-issues/es/search-analytics-duplicated-events.md
index 915344753..2f4023bcd 100644
--- a/docs/known-issues/es/search-analytics-duplicated-events.md
+++ b/docs/known-issues/es/search-analytics-duplicated-events.md
@@ -18,9 +18,7 @@ internalReference: 771986
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos eventos de los informes de búsqueda inteligente están duplicados, lo que puede afectar a la vista de análisis del módulo de administración de búsqueda.
diff --git a/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md b/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
index 703b2268c..e2e83b431 100644
--- a/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
+++ b/docs/known-issues/es/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
@@ -18,9 +18,7 @@ internalReference: 980297
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El informe de análisis de búsqueda exportado como CSV puede divergir entre su versión con métricas de embudo y su versión sin ellas.
diff --git a/docs/known-issues/es/search-api-does-not-accept-special-characters.md b/docs/known-issues/es/search-api-does-not-accept-special-characters.md
index 1fff4114b..28f358eac 100644
--- a/docs/known-issues/es/search-api-does-not-accept-special-characters.md
+++ b/docs/known-issues/es/search-api-does-not-accept-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 754363
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de búsqueda en catálogos, documentada aquí: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/products/search/-search- , no acepta términos con caracteres especiales como el apóstrofo ' o las comillas ".
diff --git a/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md b/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
index 5f5e4fd4e..93d92893d 100644
--- a/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
+++ b/docs/known-issues/es/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
@@ -18,9 +18,7 @@ internalReference: 336896
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md b/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
index 71490a603..22473596e 100644
--- a/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
+++ b/docs/known-issues/es/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
@@ -18,9 +18,7 @@ internalReference: 304586
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de búsqueda no funciona correctamente después de iniciar sesión con el operador del centro de llamadas.
diff --git a/docs/known-issues/es/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md b/docs/known-issues/es/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md
index c842f3447..1147d23c7 100644
--- a/docs/known-issues/es/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md
+++ b/docs/known-issues/es/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md
@@ -18,9 +18,7 @@ internalReference: 305247
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de búsqueda utilizando O=OrderByNameASC o O=OrderByNameDESC devuelve los resultados teniendo en cuenta la diferencia entre minúsculas y mayúsculas de la primera letra
diff --git a/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md b/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
index 868536c87..9bad13d7a 100644
--- a/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
+++ b/docs/known-issues/es/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
@@ -18,9 +18,7 @@ internalReference: 968604
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el componente "search-bar" con "autocomplete-result-list.v2", al pasar el ratón por las sugerencias de búsqueda también cambiarán los productos sugeridos, así como el texto de "ver todos {n} los productos" para mencionar la búsqueda seleccionada, pero el hipervínculo de "ver todos" sigue el término de búsqueda original en lugar del seleccionado.
diff --git a/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
index e08875318..7aceddee8 100644
--- a/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
+++ b/docs/known-issues/es/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -18,9 +18,7 @@ internalReference: 1053614
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las condiciones para los banners de búsqueda (gestionados a través de "/admin/search/v4/banners/") no soportan el operador "AND" tal y como se presenta en sus reglas de activación. La interfaz de usuario es incorrecta, y el operador se comporta como "OR" de forma fija.
diff --git a/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md b/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md
index 48fe67085..d17b8e154 100644
--- a/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md
+++ b/docs/known-issues/es/search-by-ean-not-working-on-received-skus.md
@@ -18,9 +18,7 @@ internalReference: 510907
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La función de búsqueda de Skus Recibidos permite al marketplace buscar un producto o sku por los siguientes criterios:
diff --git a/docs/known-issues/es/search-filters-disappear-intermittently.md b/docs/known-issues/es/search-filters-disappear-intermittently.md
index b55e645a7..63aec9fe2 100644
--- a/docs/known-issues/es/search-filters-disappear-intermittently.md
+++ b/docs/known-issues/es/search-filters-disappear-intermittently.md
@@ -18,9 +18,7 @@ internalReference: 734221
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos escenarios, cuando el usuario hace clic en el botón para borrar los filtros seleccionados en la página de búsqueda, los mismos filtros dejan de renderizarse y mostrarse en pantalla.
diff --git a/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md b/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
index 894a77223..c8f85c776 100644
--- a/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
+++ b/docs/known-issues/es/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
@@ -18,9 +18,7 @@ internalReference: 946391
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las organizaciones B2B utilizan los nombres de los vendedores desde la Gestión de Vendedores. Si una organización tiene asignado el vendedor 1, el nombre guardado será de la Gestión de vendedores, pero es posible que no se muestren productos en la búsqueda si difiere del nombre comercial en la Gestión de cuentas.
diff --git a/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md b/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md
index 4cf7d8e32..f55aec3ed 100644
--- a/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md
+++ b/docs/known-issues/es/search-navigator-filter-price-range-yielding-incorrect-results.md
@@ -18,9 +18,7 @@ internalReference: 504992
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando se utiliza el filtro de marca del Navegador de búsqueda junto con un rango de precios en un VTEX Business Edition, se pueden mostrar productos fuera de la marca filtrada.
diff --git a/docs/known-issues/es/search-not-working-properly-on-store-framework-jamstack.md b/docs/known-issues/es/search-not-working-properly-on-store-framework-jamstack.md
index ab6caae14..547a9a549 100644
--- a/docs/known-issues/es/search-not-working-properly-on-store-framework-jamstack.md
+++ b/docs/known-issues/es/search-not-working-properly-on-store-framework-jamstack.md
@@ -18,9 +18,7 @@ internalReference: 383231
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las sugerencias de búsqueda no funcionan correctamente en SFJ debido a la falta de implementación de eventos.
diff --git a/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md b/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md
index 05b4222a4..f92c712e0 100644
--- a/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md
+++ b/docs/known-issues/es/search-resolver-applying-messages-translations-over-already-translated-content.md
@@ -18,9 +18,7 @@ internalReference: 865918
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El Search Resolver (capa GraphQL para la Búsqueda Inteligente) solicita traducciones al servicio de Mensajes incluso para tiendas de un solo idioma o contenido ya traducido en una tienda multi-idioma.
diff --git a/docs/known-issues/es/searchable-flag-does-not-work-on-legacy-cms-collection.md b/docs/known-issues/es/searchable-flag-does-not-work-on-legacy-cms-collection.md
index 2b629bb4c..e181de508 100644
--- a/docs/known-issues/es/searchable-flag-does-not-work-on-legacy-cms-collection.md
+++ b/docs/known-issues/es/searchable-flag-does-not-work-on-legacy-cms-collection.md
@@ -18,9 +18,7 @@ internalReference: 322552
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La bandera de búsqueda no funciona en la Colección CMS heredada. Nuestro documento explica que cuando usamos esta bandera, si buscamos el nombre de la colección, debería devolver los itens asociados a esta colección.
diff --git a/docs/known-issues/es/searches-falls-into-fuzzy-when-using-special-characters.md b/docs/known-issues/es/searches-falls-into-fuzzy-when-using-special-characters.md
index c1e2b425c..2da798e57 100644
--- a/docs/known-issues/es/searches-falls-into-fuzzy-when-using-special-characters.md
+++ b/docs/known-issues/es/searches-falls-into-fuzzy-when-using-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 382382
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se buscan términos con caracteres especiales, como comas (`,`), apóstrofes (`'`), hashtags (`#`) y dos puntos (`:`), se desencadena un retroceso y se difumina, haciendo que los resultados de la búsqueda tengan un aspecto extraño.
diff --git a/docs/known-issues/es/searches-with-at-the-end-not-working-correctly.md b/docs/known-issues/es/searches-with-at-the-end-not-working-correctly.md
index 321ec81eb..b68626adc 100644
--- a/docs/known-issues/es/searches-with-at-the-end-not-working-correctly.md
+++ b/docs/known-issues/es/searches-with-at-the-end-not-working-correctly.md
@@ -18,9 +18,7 @@ internalReference: 509101
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se busca con un % al final de la búsqueda no funciona como se espera debido a problemas de decodificación.
diff --git a/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md b/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
index 1a3edf7af..1cbd988ab 100644
--- a/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
+++ b/docs/known-issues/es/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
@@ -18,9 +18,7 @@ internalReference: 828170
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se busca un documento utilizando un valor de campo que incluye el símbolo "+", la búsqueda no devuelve el documento. Esto ocurre porque el símbolo "+" se interpreta incorrectamente, lo que provoca que el valor de búsqueda no coincida con el valor existente.
diff --git a/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md b/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md
index 0887c365f..9e5716c66 100644
--- a/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md
+++ b/docs/known-issues/es/segment-cookie-updated-only-after-refreshing-the-page.md
@@ -18,9 +18,7 @@ internalReference: 647116
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas funciones y componentes de VTEX pueden utilizar datos solicitados a la cookie de segmento para presentar información (como precio, datos de promoción, disponibilidad de SKU, etc.) en el escaparate. Esta cookie se almacena en el navegador del usuario cuando se crea la sesión. A veces, sobre todo en escenarios dinámicos donde se necesita hacer cambios en el frente donde se desencadena una actualización del Segmento Cookie, la cookie en sí pierde algunos datos que es de un comportamiento en render-runtime que no desencadena el cambio de segmento al contexto.
diff --git a/docs/known-issues/es/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md b/docs/known-issues/es/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md
index 22961d44f..edf2d83cb 100644
--- a/docs/known-issues/es/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md
+++ b/docs/known-issues/es/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 515480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El cambio de disponibilidad de un vendedor en una póliza comercial no está siendo reconocido correctamente en el catálogo. Esto puede causar dos escenarios: un producto de un vendedor no seleccionado pasa a estar disponible o un producto de un vendedor seleccionado pasa a no estar disponible
diff --git a/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md b/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md
index 4e8e9958a..d3fc1a992 100644
--- a/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md
+++ b/docs/known-issues/es/seller-commission-updates-does-not-index-binded-skus.md
@@ -18,9 +18,7 @@ internalReference: 891162
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el vendedor actualiza la comisión del vendedor en la interfaz de usuario de gestión de vendedores, los skus vinculados relacionados con este vendedor no se indexan automáticamente.
diff --git a/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md b/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md
index 663ffeb82..1c67d4c92 100644
--- a/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md
+++ b/docs/known-issues/es/seller-group-creation-does-not-add-selected-sellers.md
@@ -18,9 +18,7 @@ internalReference: 926969
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El mercado puede crear grupos con algunos vendedores en la interfaz de usuario de gestión de vendedores.
diff --git a/docs/known-issues/es/seller-logo-not-being-saved-as-an-url.md b/docs/known-issues/es/seller-logo-not-being-saved-as-an-url.md
index 899b8e190..429300080 100644
--- a/docs/known-issues/es/seller-logo-not-being-saved-as-an-url.md
+++ b/docs/known-issues/es/seller-logo-not-being-saved-as-an-url.md
@@ -18,9 +18,7 @@ internalReference: 736716
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/seller-portal-account-not-able-to-export-baseprice.md b/docs/known-issues/es/seller-portal-account-not-able-to-export-baseprice.md
index f973d6ae5..c6dcd7369 100644
--- a/docs/known-issues/es/seller-portal-account-not-able-to-export-baseprice.md
+++ b/docs/known-issues/es/seller-portal-account-not-able-to-export-baseprice.md
@@ -18,9 +18,7 @@ internalReference: 408868
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas cuentas del Portal del Vendedor no pueden exportar el "precio base".
diff --git a/docs/known-issues/es/seller-portal-product-doesnt-load-when-without-images.md b/docs/known-issues/es/seller-portal-product-doesnt-load-when-without-images.md
index afc9996eb..c06b5bdfc 100644
--- a/docs/known-issues/es/seller-portal-product-doesnt-load-when-without-images.md
+++ b/docs/known-issues/es/seller-portal-product-doesnt-load-when-without-images.md
@@ -18,9 +18,7 @@ internalReference: 800480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para las cuentas del portal del vendedor, si tiene un producto sin imágenes para cada sku, la interfaz de usuario del producto no se cargará correctamente.
diff --git a/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md b/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
index fe0e87683..690fef419 100644
--- a/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
+++ b/docs/known-issues/es/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 928558
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md b/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md
index c402c1027..b776dd73c 100644
--- a/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md
+++ b/docs/known-issues/es/seller-portal-select-specifications-dropdown-malfunctioning.md
@@ -18,9 +18,7 @@ internalReference: 711303
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el cuadro de selección de especificación de producto de la página accountname.myvtex.com/admin/products/new/ tiene un comportamiento defectuoso cuando se intenta seleccionar un valor para una especificación de producto.
diff --git a/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md b/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
index f0f740af3..4ecb354f3 100644
--- a/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
+++ b/docs/known-issues/es/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
@@ -18,9 +18,7 @@ internalReference: 915970
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar la nueva interfaz de usuario de experiencia del vendedor, /admin/sellers, la acción de desactivar un vendedor debería reindexar sus productos relacionados para que puedan eliminarse de los mercados asociados, lo que no ocurre actualmente.
diff --git a/docs/known-issues/es/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md b/docs/known-issues/es/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md
index c21224db9..0ed20376f 100644
--- a/docs/known-issues/es/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md
+++ b/docs/known-issues/es/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md
@@ -18,9 +18,7 @@ internalReference: 360097
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El algoritmo de selección de vendedores tiene en cuenta el stock de los artículos para seleccionar el mejor vendedor de marca blanca para un contexto determinado.
diff --git a/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md b/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md
index 8d200210c..cfbb1594f 100644
--- a/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md
+++ b/docs/known-issues/es/sellers-order-invoiced-with-problem-in-the-payment-capture.md
@@ -18,9 +18,7 @@ internalReference: 376646
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Ahora mismo, tal y como está construida nuestra arquitectura, tanto el Vendedor como el Marketplace son dos entidades totalmente diferentes. Marketplace se encarga de recibir el dinero del cliente y el vendedor es responsable de toda la logística hasta el momento en que entrega los productos al cliente.
diff --git a/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md b/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md
index 789bd7434..617fe30a9 100644
--- a/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md
+++ b/docs/known-issues/es/service-type-name-field-wrongly-returned-via-api.md
@@ -18,9 +18,7 @@ internalReference: 961278
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente las APIs del Catálogo SKU no están devolviendo correctamente el nombre de un tipo de servicio. En su lugar se está devolviendo el nombre del valor del servicio.
diff --git a/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md b/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md
index 36b10c0c0..caabf592d 100644
--- a/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md
+++ b/docs/known-issues/es/services-prices-are-not-updated-when-added-to-items.md
@@ -18,9 +18,7 @@ internalReference: 822107
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los precios de los servicios no se actualizan si se añadió a un artículo antes de cambiar su precio de servicio en el admin. Esto provocará que el pedido se cree con un precio desactualizado.
diff --git a/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md b/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
index bc0a80e1d..f22c67f96 100644
--- a/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
+++ b/docs/known-issues/es/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
@@ -18,9 +18,7 @@ internalReference: 925071
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las cookies para la información de sesión son exclusivas de la vinculación de cuenta específica, pero las vinculaciones que no están en el mismo nivel de ruta pueden recibir cookies de niveles inferiores, lo que provoca problemas.
diff --git a/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
index 8fbb31e91..11bce1207 100644
--- a/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
+++ b/docs/known-issues/es/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -18,9 +18,7 @@ internalReference: 876576
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 B2B Quote settings UI no actualiza el valor del periodo de expiración; siempre es 30.
diff --git a/docs/known-issues/es/shared-products-import-error.md b/docs/known-issues/es/shared-products-import-error.md
index 30e63290d..364fdf019 100644
--- a/docs/known-issues/es/shared-products-import-error.md
+++ b/docs/known-issues/es/shared-products-import-error.md
@@ -18,9 +18,7 @@ internalReference: 647962
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente tenemos un error en algunos casos donde la ruta de la categoría contiene "/" los productos no se pueden importar a productos compartidos
diff --git a/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md b/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md
index 9f9437dac..e780003fa 100644
--- a/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md
+++ b/docs/known-issues/es/shipping-component-locked-in-waiting-for-more-information-state.md
@@ -18,9 +18,7 @@ internalReference: 780673
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Checkout UI no renderiza el componente de envío cuando se accede a la página de checkout directamente a través de un paso específico en la URL (excepto para /cart y /shipping), el "shippingData" está incompleto, y hay un incremento de latencia en las peticiones a la API orderForm. Verá el mensaje "Esperando más información" y no podrá continuar con la compra.
diff --git a/docs/known-issues/es/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md b/docs/known-issues/es/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md
index 18e8c5429..51b3a99c7 100644
--- a/docs/known-issues/es/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md
+++ b/docs/known-issues/es/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md
@@ -18,9 +18,7 @@ internalReference: 362685
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el carrito, cuando se selecciona la dirección, las tiendas con Lean Shipping activado y ofrecen entrega/recogida programada, no se muestran todas las opciones disponibles en la vista previa del envío; sólo se muestra y selecciona la entrega regular.
diff --git a/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md b/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md
index cff1af4bf..f7438a0f1 100644
--- a/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md
+++ b/docs/known-issues/es/shipping-options-gets-frozen-when-trying-to-select-an-option.md
@@ -18,9 +18,7 @@ internalReference: 898888
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza la configuración de pago B2B y se va y viene entre los pasos de envío y pago, el envío se congela al intentar seleccionar una opción.
diff --git a/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md b/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
index f4d84b3e9..fb8b044ab 100644
--- a/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
+++ b/docs/known-issues/es/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
@@ -18,9 +18,7 @@ internalReference: 379685
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el cliente establece un coste desde el almacén hasta el muelle en la tarifa de envío, puede afectar a la selección de la política de envío. Esto puede ocurrir porque el coste del muelle no se incluye en la priorización de las pólizas de envío. Por lo tanto, se puede priorizar una política de envío que sea más cara para el consumidor, ya que el cálculo del valor del flete no tuvo en cuenta el coste del muelle.
diff --git a/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md b/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
index 4499cf996..ca79177ab 100644
--- a/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
+++ b/docs/known-issues/es/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
@@ -18,9 +18,7 @@ internalReference: 925914
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En ocasiones la póliza de transporte puede quedarse atascada en el estado de tramitación, pero en la nueva UI de logística no se ve porque informa de que el estado está activo.
diff --git a/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md b/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
index d2c87a422..8df304152 100644
--- a/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
+++ b/docs/known-issues/es/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
@@ -18,9 +18,7 @@ internalReference: 594828
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Antes, la funcionalidad "**Fines de semana y festivos**" y "**horario comercial**" funcionaban conjuntamente, es decir, una información dependía de la otra.
diff --git a/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md b/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
index ac06e01a6..f7d124caf 100644
--- a/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
+++ b/docs/known-issues/es/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
@@ -18,9 +18,7 @@ internalReference: 380471
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la política de envío tiene el MaxVolume en la hoja de cálculo no hay ningún mensaje de error con respecto a esto en la simulación.
diff --git a/docs/known-issues/es/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md b/docs/known-issues/es/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md
index 37f6bb12f..5bf23e21f 100644
--- a/docs/known-issues/es/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md
+++ b/docs/known-issues/es/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md
@@ -18,9 +18,7 @@ internalReference: 264441
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si el carrito tiene varios paquetes con diferentes plazos de entrega, el selector de entrega de la Vista Previa de Envío muestra sólo uno de los plazos, dando información incorrecta.
diff --git a/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md b/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
index 7c6be0ed3..3b6263e69 100644
--- a/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
+++ b/docs/known-issues/es/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
@@ -18,9 +18,7 @@ internalReference: 574651
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md b/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
index 48471fc1c..0325e826f 100644
--- a/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
+++ b/docs/known-issues/es/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
@@ -18,9 +18,7 @@ internalReference: 938124
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la vista previa del envío, cuando se selecciona recoger en tienda, pero no todos los artículos están disponibles para esa recogida, la dirección mostrada para el envío es la de la recogida elegida, y no es posible cambiarla. Sin embargo, en el formulario de pedido, la dirección seleccionada para el envío es correcta.
diff --git a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
index 2a2ab06c5..4aaa0b6e6 100644
--- a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
+++ b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 743774
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Checkout UI convierte la hora utilizando la zona horaria del ordenador mostrando la fecha de entrega incorrectamente en shipping-preview (carrito) cuando los artículos son de entrega programada.
diff --git a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
index e25b4d0b5..263c7fd3a 100644
--- a/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
+++ b/docs/known-issues/es/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 532487
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El precio de entrega mostrado en shipping-preview (carrito) es incorrecto cuando los artículos son de entrega programada y todos estos artículos salen en el mismo SLA. Aunque la API devuelva el valor correcto, la interfaz de usuario no refleja esta información y muestra el valor incorrecto.
diff --git a/docs/known-issues/es/shipping-preview-wrongly-reporting-pickup-selection.md b/docs/known-issues/es/shipping-preview-wrongly-reporting-pickup-selection.md
index 840968bf2..524948b70 100644
--- a/docs/known-issues/es/shipping-preview-wrongly-reporting-pickup-selection.md
+++ b/docs/known-issues/es/shipping-preview-wrongly-reporting-pickup-selection.md
@@ -18,9 +18,7 @@ internalReference: 552912
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el carrito, al informar de su ubicación, la vista previa del envío informa erróneamente de qué recogida se ha seleccionado para esta recogida. Cuando en realidad deberían aparecer dos opciones de recogida (en este ejemplo hubo una rotura de paquete). Y al llegar a la caja, la información se proporciona correctamente, con las retiradas en las respectivas recogidas correctas.
diff --git a/docs/known-issues/es/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md b/docs/known-issues/es/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md
index 0d3ff764f..45fda3996 100644
--- a/docs/known-issues/es/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md
+++ b/docs/known-issues/es/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md
@@ -18,9 +18,7 @@ internalReference: 764457
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se añade "selectedSla" (debe ser una recogida) y "selectedAddresses" vía API en un carrito con promoción de regalo, la tienda está configurada para geolocalización y utiliza polígonos, la vista previa del envío mostrará un mensaje de no disponibilidad para la recogida, que fue seleccionada vía API. Este comportamiento impactará en el flujo de compra ya que no permitirá avanzar después del envío.
diff --git a/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md b/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md
index fc43b3917..41a8e35ca 100644
--- a/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md
+++ b/docs/known-issues/es/shipping-previews-postal-code-input-field-is-not-hidden.md
@@ -18,9 +18,7 @@ internalReference: 821984
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para algunos países, el campo de entrada del código postal de la vista previa de envío no se oculta después de incluir un código postal válido por segunda vez.
diff --git a/docs/known-issues/es/shipping-promotion-does-not-generate-highlights-flags.md b/docs/known-issues/es/shipping-promotion-does-not-generate-highlights-flags.md
index 49a00d453..6678ccc08 100644
--- a/docs/known-issues/es/shipping-promotion-does-not-generate-highlights-flags.md
+++ b/docs/known-issues/es/shipping-promotion-does-not-generate-highlights-flags.md
@@ -18,9 +18,7 @@ internalReference: 527111
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los porcentajes de envío, el envío máximo, el envío gratuito y las promociones de regalo no están generando puntos destacados / banderas en los PDP y PLP.
diff --git a/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md b/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
index 08db353fd..579740269 100644
--- a/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
+++ b/docs/known-issues/es/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
@@ -18,9 +18,7 @@ internalReference: 916423
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando las promociones de envío aplican para diferentes SLAs, siendo uno de ellos el envío gratuito, causa divergencia en la solicitud enviada por el Tax Hub, impidiendo que el pedido sea realizado.
diff --git a/docs/known-issues/es/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md b/docs/known-issues/es/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md
index cf5a4145f..4432dde43 100644
--- a/docs/known-issues/es/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md
+++ b/docs/known-issues/es/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md
@@ -18,9 +18,7 @@ internalReference: 650038
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Un usuario que tiene guardada la dirección en su perfil, al llegar al paso de dirección donde se muestra la selección de envío, al seleccionar otra opción se muestra erróneamente un aviso de "La entrega no está disponible para esta dirección", puede aparecer rápidamente debido a la carga de información, puede ocurrir según la demora en esta búsqueda dependiendo de la complejidad de la tienda.
diff --git a/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md b/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
index e44ac24e8..d56299c3f 100644
--- a/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
+++ b/docs/known-issues/es/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
@@ -18,9 +18,7 @@ internalReference: 312132
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 ## **Resumen**
 
diff --git a/docs/known-issues/es/shopee-could-not-create-product.md b/docs/known-issues/es/shopee-could-not-create-product.md
index 814ed47f7..b2b09cf0b 100644
--- a/docs/known-issues/es/shopee-could-not-create-product.md
+++ b/docs/known-issues/es/shopee-could-not-create-product.md
@@ -18,9 +18,7 @@ internalReference: 685149
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/shopee-failed-to-create-product-variations.md b/docs/known-issues/es/shopee-failed-to-create-product-variations.md
index ee61dd9c4..ef218dcc2 100644
--- a/docs/known-issues/es/shopee-failed-to-create-product-variations.md
+++ b/docs/known-issues/es/shopee-failed-to-create-product-variations.md
@@ -18,9 +18,7 @@ internalReference: 685160
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md b/docs/known-issues/es/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md
index 7020db962..f8acde30a 100644
--- a/docs/known-issues/es/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md
+++ b/docs/known-issues/es/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md
@@ -18,9 +18,7 @@ internalReference: 685137
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md b/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md
index a21a1c033..f9ffb4460 100644
--- a/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md
+++ b/docs/known-issues/es/similar-products-ui-brokes-with-too-many-products.md
@@ -18,9 +18,7 @@ internalReference: 868425
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md b/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
index f5478e694..76cc1b3f0 100644
--- a/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
+++ b/docs/known-issues/es/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
@@ -18,9 +18,7 @@ internalReference: 488362
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un problema al utilizar el autocompletado para encontrar productos en el módulo de simulación de productos del catálogo V2.
diff --git a/docs/known-issues/es/simultaneous-sending-of-information-generates-data-loss-in-the-api.md b/docs/known-issues/es/simultaneous-sending-of-information-generates-data-loss-in-the-api.md
index ff85808b0..18f026737 100644
--- a/docs/known-issues/es/simultaneous-sending-of-information-generates-data-loss-in-the-api.md
+++ b/docs/known-issues/es/simultaneous-sending-of-information-generates-data-loss-in-the-api.md
@@ -18,19 +18,13 @@ internalReference: 280390
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-checkout.md b/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-checkout.md
index 541a2b4e9..7460d3978 100644
--- a/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-checkout.md
+++ b/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 605568
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se registra una condición de pago en la que sólo hay un plazo, esta información no aparece en la caja.
diff --git a/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md b/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md
index dea28de1d..696b680b1 100644
--- a/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md
+++ b/docs/known-issues/es/single-installment-payment-condition-does-not-appear-at-chekout.md
@@ -18,9 +18,7 @@ internalReference: 605568
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se configura una única condición de pago con una única opción de pago a plazos o múltiples condiciones de pago en las que sólo hay disponible una opción de pago a plazos para un carro específico, esta opción de pago a plazos no se muestra en el proceso de pago. Aunque aparece correctamente en `paymentData`, no es visible para el usuario. En su lugar, sólo se muestra la opción de pagar el valor total. Sin embargo, cuando se completa la transacción, el pago se procesa con la opción de pago a plazos correcta.
diff --git a/docs/known-issues/es/single-sku-with-multiple-ean-in-merchant-center.md b/docs/known-issues/es/single-sku-with-multiple-ean-in-merchant-center.md
index eea3e76ef..a61d400c5 100644
--- a/docs/known-issues/es/single-sku-with-multiple-ean-in-merchant-center.md
+++ b/docs/known-issues/es/single-sku-with-multiple-ean-in-merchant-center.md
@@ -18,9 +18,7 @@ internalReference: 520345
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Confirmar cómo estamos enviando la propiedad EAN cuando el producto tiene varios skus del mismo producto en el catálogo VTEX.
diff --git a/docs/known-issues/es/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md b/docs/known-issues/es/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md
index bff36adcf..37e7970a3 100644
--- a/docs/known-issues/es/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md
+++ b/docs/known-issues/es/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md
@@ -18,9 +18,7 @@ internalReference: 371994
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md b/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md
index 956e349da..ae40f4153 100644
--- a/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md
+++ b/docs/known-issues/es/site-editor-doesnt-allow-changes-on-the-conditional-template.md
@@ -18,9 +18,7 @@ internalReference: 861920
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando una plantilla se establece como la condicional no es capaz de realizar cambios en él a través del editor del sitio.
diff --git a/docs/known-issues/es/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md b/docs/known-issues/es/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md
index ae5a6e1aa..fc0427f07 100644
--- a/docs/known-issues/es/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md
+++ b/docs/known-issues/es/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md
@@ -18,9 +18,7 @@ internalReference: 755993
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si intentas acceder a una página en el editor del sitio usando la página de aterrizaje no carga los bloques, se queda en carga infinita. Por ejemplo `https://.myvtex.com/admin/cms/site-editor/.`
diff --git a/docs/known-issues/es/site-editor-has-intermittent-rendering-issues-in-small-screen.md b/docs/known-issues/es/site-editor-has-intermittent-rendering-issues-in-small-screen.md
index 778f233a7..c0aee9c4f 100644
--- a/docs/known-issues/es/site-editor-has-intermittent-rendering-issues-in-small-screen.md
+++ b/docs/known-issues/es/site-editor-has-intermittent-rendering-issues-in-small-screen.md
@@ -18,9 +18,7 @@ internalReference: 399339
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El Editor del Sitio tiene problemas intermitentes de representación en pantallas menores de 1366px de ancho.
diff --git a/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md b/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
index 48dd0bb16..81f86c0fc 100644
--- a/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
+++ b/docs/known-issues/es/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
@@ -18,9 +18,7 @@ internalReference: 735208
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md b/docs/known-issues/es/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md
index b6b999d06..87dd36a01 100644
--- a/docs/known-issues/es/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md
+++ b/docs/known-issues/es/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md
@@ -18,9 +18,7 @@ internalReference: 617974
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El mapa del sitio generado está mostrando todos los productos de las subcuentas y cuentas, sin tener en cuenta el canal de venta de los productos y si la subcuenta tiene un sitio web propio.
diff --git a/docs/known-issues/es/sitemap-isnt-being-generated.md b/docs/known-issues/es/sitemap-isnt-being-generated.md
index 1a201789f..07c901e41 100644
--- a/docs/known-issues/es/sitemap-isnt-being-generated.md
+++ b/docs/known-issues/es/sitemap-isnt-being-generated.md
@@ -18,9 +18,7 @@ internalReference: 827104
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay dos escenarios en los que no se está generando el mapa del sitio:
diff --git a/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md b/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md
index 6e1e33c1e..601f72308 100644
--- a/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md
+++ b/docs/known-issues/es/sitemap-isnt-being-generatedupdated.md
@@ -18,9 +18,7 @@ internalReference: 827104
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/size-of-content-files-can-cause-problems-in-site-editor-features.md b/docs/known-issues/es/size-of-content-files-can-cause-problems-in-site-editor-features.md
index cbe5edd73..53c7073b7 100644
--- a/docs/known-issues/es/size-of-content-files-can-cause-problems-in-site-editor-features.md
+++ b/docs/known-issues/es/size-of-content-files-can-cause-problems-in-site-editor-features.md
@@ -18,9 +18,7 @@ internalReference: 715480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md b/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
index 08b15e734..faabdb44c 100644
--- a/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
+++ b/docs/known-issues/es/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
@@ -18,9 +18,7 @@ internalReference: 884789
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera que el usuario pueda cambiar el código de referencia de la SKU utilizando el admin. Sin embargo, cuando se introduce un valor de más de 50 caracteres, el administrador se bloquea y muestra un mensaje de error.
diff --git a/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md b/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
index cb0fbc5c7..178ce7757 100644
--- a/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
+++ b/docs/known-issues/es/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
@@ -18,9 +18,7 @@ internalReference: 970208
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al aprobar un nuevo producto en Skus Recibidos (automática o manualmente) el módulo de sugerencias se comunica con el catálogo del Marketplace para realizar la acción.
diff --git a/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md b/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md
index a9983935d..f1fb8305b 100644
--- a/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md
+++ b/docs/known-issues/es/sku-file-update-does-not-update-v-version-tags.md
@@ -18,9 +18,7 @@ internalReference: 852869
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, cuando un archivo de imagen SKU se actualiza a través de la API para estar en la misma posición que uno anterior, su etiqueta de versión (?v=) en la página del producto no se actualiza correctamente.
diff --git a/docs/known-issues/es/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md b/docs/known-issues/es/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md
index db3657730..a4551e888 100644
--- a/docs/known-issues/es/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md
+++ b/docs/known-issues/es/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md
@@ -18,9 +18,7 @@ internalReference: 603761
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Sku inactivo, se actualiza en B2W pero no registra el mensaje correcto en el puente
diff --git a/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
index 8897b01e0..3897ff139 100644
--- a/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
+++ b/docs/known-issues/es/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -18,9 +18,7 @@ internalReference: 1014787
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la API para crear un archivo sku https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file no responde con la propiedad "Texto" correctamente.
diff --git a/docs/known-issues/es/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md b/docs/known-issues/es/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md
index 439930f1d..05c59edcc 100644
--- a/docs/known-issues/es/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md
+++ b/docs/known-issues/es/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md
@@ -18,19 +18,13 @@ internalReference: 389784
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md b/docs/known-issues/es/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md
index ebccfbf3b..307bfa942 100644
--- a/docs/known-issues/es/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md
+++ b/docs/known-issues/es/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md
@@ -18,9 +18,7 @@ internalReference: 515042
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la respuesta de la API de búsqueda no respeta el posicionamiento de las SKU dentro del producto en Admin. En la respuesta, las SKU se ordenan en orden ascendente de SkuId.
diff --git a/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md b/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
index 86b3bb766..26a9a85af 100644
--- a/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
+++ b/docs/known-issues/es/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
@@ -18,9 +18,7 @@ internalReference: 827760
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md b/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md
index d7f288320..561fd5e8d 100644
--- a/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md
+++ b/docs/known-issues/es/sku-selector-display-mode-select-not-working-in-shelfs.md
@@ -18,9 +18,7 @@ internalReference: 682152
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando eliges una opción diferente de sku en el modo de visualización SELECT en lugar de la predeterminada, sólo muestra "elegir y opción" en lugar de marcar la que eliges. Este comportamiento solo ocurre en estanterias en Firefox.
diff --git a/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md b/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
index e11e861fa..b95a50f95 100644
--- a/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
+++ b/docs/known-issues/es/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
@@ -18,9 +18,7 @@ internalReference: 1047992
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al tener una subcadena de la variación en la SKU elegida en otra variación disponible, podríamos no seleccionar la SKU elegida
diff --git a/docs/known-issues/es/sku-selector-with-multilpe-contexts.md b/docs/known-issues/es/sku-selector-with-multilpe-contexts.md
index 89c328752..5fc28a4b9 100644
--- a/docs/known-issues/es/sku-selector-with-multilpe-contexts.md
+++ b/docs/known-issues/es/sku-selector-with-multilpe-contexts.md
@@ -18,9 +18,7 @@ internalReference: 341322
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md b/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
index f4362508b..9d9dab6bd 100644
--- a/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
+++ b/docs/known-issues/es/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
@@ -18,9 +18,7 @@ internalReference: 431888
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Desde una reciente actualización en el comportamiento de la Búsqueda, los filtros de especificación de SKUs no disponibles no se muestran en las páginas de resultados de la búsqueda.
diff --git a/docs/known-issues/es/sku-variations-doesnt-return-in-the-plp.md b/docs/known-issues/es/sku-variations-doesnt-return-in-the-plp.md
index d6b4c4215..69dcfd76d 100644
--- a/docs/known-issues/es/sku-variations-doesnt-return-in-the-plp.md
+++ b/docs/known-issues/es/sku-variations-doesnt-return-in-the-plp.md
@@ -18,9 +18,7 @@ internalReference: 569563
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La presentación de las variaciones de SKU en el PLP se limita a las variaciones disponibles independientemente de la configuración de la prop skusFilter. Según nuestro análisis, search-graphql no está entregando todas las variaciones según el retorno de la API, por lo que el ProductContextProvider no recibe todas las variaciones.
diff --git a/docs/known-issues/es/skus-expiring-in-merchant-center.md b/docs/known-issues/es/skus-expiring-in-merchant-center.md
index bb9da323b..054cca718 100644
--- a/docs/known-issues/es/skus-expiring-in-merchant-center.md
+++ b/docs/known-issues/es/skus-expiring-in-merchant-center.md
@@ -18,9 +18,7 @@ internalReference: 548044
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
index 333a748a5..69cfd2278 100644
--- a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
@@ -18,9 +18,7 @@ internalReference: 467112
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vendedor envía un lote con skus del mismo producto (todas las variaciones posibles del producto).
diff --git a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
index c77bc0243..101c0ed98 100644
--- a/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/es/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
@@ -18,9 +18,7 @@ internalReference: 962986
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vendedor envía un lote con skus del mismo producto (todas las variaciones posibles del producto).
diff --git a/docs/known-issues/es/skus-sent-by-sellers-are-created-with-images-out-of-order.md b/docs/known-issues/es/skus-sent-by-sellers-are-created-with-images-out-of-order.md
index effa7c3ef..a061c27fd 100644
--- a/docs/known-issues/es/skus-sent-by-sellers-are-created-with-images-out-of-order.md
+++ b/docs/known-issues/es/skus-sent-by-sellers-are-created-with-images-out-of-order.md
@@ -18,9 +18,7 @@ internalReference: 648349
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el sku es enviado por un vendedor y aprobado en el módulo de Skus Recibidos, las imágenes del nuevo sku en el catálogo del marketplace están fuera del pedido enviado por el vendedor.
diff --git a/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md b/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
index 7a6ff2fa4..06cd351bd 100644
--- a/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
+++ b/docs/known-issues/es/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
@@ -18,9 +18,7 @@ internalReference: 335819
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 Al asociar un servicio para una SKU en nuestro catálogo, para una tienda que tiene múltiples tipos de servicio y valores de servicio (campo Tipo de valor), al principio, cuando un usuario entra en la UI, la lista de opciones para un determinado "Tipo de servicio" actualmente sólo lista las opciones asociadas en la tabla Valor del primer tipo de servicio seleccionado.
 
diff --git a/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md b/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
index 57b345582..2e114cece 100644
--- a/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
+++ b/docs/known-issues/es/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
@@ -18,9 +18,7 @@ internalReference: 1036916
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La simulación logística puede oscilar entre ofrecer SLAs si el cliente tiene políticas de envío con el mismo precio, tiempo de entrega, SlaType, coste de muelle y configuración de almacén, pero diferente prioridad de muelle.
diff --git a/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md b/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
index e5ff478b6..be5d5baed 100644
--- a/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
+++ b/docs/known-issues/es/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
@@ -18,9 +18,7 @@ internalReference: 920725
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el slider-layout está configurado como `infinite: "always"` en el móvil el componente presenta un bug intermitente. Después de un rato desplazando la estantería los productos dejarán de aparecer y en su lugar aparecerá un espacio en blanco.
diff --git a/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md b/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
index aa3088f94..f6ecaf4af 100644
--- a/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
+++ b/docs/known-issues/es/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
@@ -18,9 +18,7 @@ internalReference: 998397
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 API de Facetas de Catálogo descrita aquí: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/facets/search/-term-
diff --git a/docs/known-issues/es/sms-configuration-in-message-centre-module-returns-an-error.md b/docs/known-issues/es/sms-configuration-in-message-centre-module-returns-an-error.md
index aa8f72e06..50631b97a 100644
--- a/docs/known-issues/es/sms-configuration-in-message-centre-module-returns-an-error.md
+++ b/docs/known-issues/es/sms-configuration-in-message-centre-module-returns-an-error.md
@@ -22,9 +22,7 @@ Al configurar el envío de SMS por el módulo Centro de Mensajes, la UI devuelve
 
 ## Simulación
 
-<div class="alert alert-info">
-Es necesario tener el APP de movile instalado para simular el error.
-</div>
+>ℹ️ Es necesario tener el APP de movile instalado para simular el error.
 
  1. Entrar en el módulo Centro de Mensajes;
  2. Seleccione la opción MOVILE SMS;
diff --git a/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md b/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
index 010481730..032cf933c 100644
--- a/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
+++ b/docs/known-issues/es/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
@@ -18,9 +18,7 @@ internalReference: 1054007
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la pantalla de configuración de plantillas del sistema de centro de mensajes, hay un enlace que debería llevar al usuario a la configuración de la app de envío de SMS, pero esta app ya no está disponible y el enlace ahora devuelve 404, mostrando una pantalla con el mensaje "`store/not-found-box-title`".
diff --git a/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md b/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
index 4a352fb45..8224260cd 100644
--- a/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
+++ b/docs/known-issues/es/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
@@ -18,9 +18,7 @@ internalReference: 415388
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas direcciones devueltas desde el campo de búsqueda de Google no se están guardando cuando se añaden a través del flujo Mi cuenta, y la interfaz de usuario no devuelve ninguna respuesta al usuario.
diff --git a/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md b/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
index 714628cb2..25872c3cb 100644
--- a/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
+++ b/docs/known-issues/es/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
@@ -18,9 +18,7 @@ internalReference: 868535
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas funciones del componente de diseño pegajoso no funcionan como se espera cuando se ve a través del navegador Safari
diff --git a/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
index bcdddef67..6f8efdda0 100644
--- a/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
+++ b/docs/known-issues/es/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 1001665
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las funciones de gestión de inventario (como los enlaces a los productos) no se comportan como se espera en las cuentas del portal del vendedor. Esto ocurre porque este tipo de cuentas utilizan una versión diferente del catálogo.
diff --git a/docs/known-issues/es/some-promotions-cant-be-displayed-in-search-context.md b/docs/known-issues/es/some-promotions-cant-be-displayed-in-search-context.md
index c5fa11976..34d8a8990 100644
--- a/docs/known-issues/es/some-promotions-cant-be-displayed-in-search-context.md
+++ b/docs/known-issues/es/some-promotions-cant-be-displayed-in-search-context.md
@@ -18,9 +18,7 @@ internalReference: 475289
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos tipos de promociones no se recuperan en el contexto de ProductSummaryProvider, y por lo tanto sus insignias no son renderizadas por el componente vtex.product-highlights.
diff --git a/docs/known-issues/es/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md b/docs/known-issues/es/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md
index c45192d72..c7fc15b2c 100644
--- a/docs/known-issues/es/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md
+++ b/docs/known-issues/es/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md
@@ -18,9 +18,7 @@ internalReference: 558926
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/some-skus-dont-integrate-dafiti.md b/docs/known-issues/es/some-skus-dont-integrate-dafiti.md
index 805aced05..14ff73c44 100644
--- a/docs/known-issues/es/some-skus-dont-integrate-dafiti.md
+++ b/docs/known-issues/es/some-skus-dont-integrate-dafiti.md
@@ -18,9 +18,7 @@ internalReference: 655574
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md b/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
index 539a710fc..3213450a8 100644
--- a/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
+++ b/docs/known-issues/es/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
@@ -18,9 +18,7 @@ internalReference: 382382
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos caracteres especiales no se eliminan completamente de las palabras clave buscadas o de la indexación de productos, lo que puede afectar a las búsquedas en algunos escenarios específicos.
diff --git a/docs/known-issues/es/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md b/docs/known-issues/es/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md
index 486b114ee..e157beb75 100644
--- a/docs/known-issues/es/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md
+++ b/docs/known-issues/es/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md
@@ -18,9 +18,7 @@ internalReference: 418348
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas especificaciones no se muestran en Admin, pero son visibles a través de la API.
diff --git a/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md b/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md
index 5b88da2e7..399651749 100644
--- a/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md
+++ b/docs/known-issues/es/some-unexpected-behavior-in-masterdata.md
@@ -18,9 +18,7 @@ internalReference: 669048
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Incluso con datos disponibles (documentos), la información no se devuelve como se esperaba.
diff --git a/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md b/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
index 68b8d81a6..7e8c9aa9d 100644
--- a/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
+++ b/docs/known-issues/es/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
@@ -18,9 +18,7 @@ internalReference: 907567
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera utilizar el admin sin restricciones. Sin embargo, a veces se muestra un error **Something Went Wrong** en el admin del catálogo.
diff --git a/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md b/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
index 8cdb8c460..b88b85d10 100644
--- a/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
+++ b/docs/known-issues/es/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
@@ -18,9 +18,7 @@ internalReference: 945226
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se espera poder buscar cualquier término en los almacenes del Portal; sin embargo, las letras "A" y "P" no se pueden buscar directamente a través de la URL.
diff --git a/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
index a8a6c0c85..ef31ee107 100644
--- a/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
+++ b/docs/known-issues/es/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -18,9 +18,7 @@ internalReference: 960064
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Durante la etapa de pago utilizando un comprador con un perfil completo, en el paso de rellenar los datos de envío, pulsando en la opción "Entregar en otra dirección", si sólo se añade el código postal y el comprador vuelve a la lista de direcciones (utilizando el botón "volver a la libreta de direcciones") y pulsa en "Actualizar la información de la dirección seleccionada" se produce un error con el mensaje "Algo ha ido mal".
diff --git a/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md b/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md
index b69dc1554..d9bc51379 100644
--- a/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md
+++ b/docs/known-issues/es/sort-by-name-working-different-on-stores-integrated-before-a-date.md
@@ -18,9 +18,7 @@ internalReference: 600468
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se ordena por nombre en el PLP desde un almacén puede tener comportamientos diferentes con palabras con letras mayúsculas y minúsculas y esto ocurre debido a un normalizador que se realiza en los almacenes para trabajar las letras todas como minúsculas y la ordenación no considera las palabras cameladas o mayúsculas.
diff --git a/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md b/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
index a6dde768f..9e3e46210 100644
--- a/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
+++ b/docs/known-issues/es/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 872935
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al activar el uso de la API de código postal en el formulario de dirección para países que no están en el modelo BR (country, state, city, neighborhood, street), estos países que no tienen todos estos campos rellenados en la API y necesitan poder introducir el resto de datos de dirección en el formulario de dirección en el checkout, el campo street del bloque de dirección no estará disponible si la propiedad street del JSON está con espacio, ya que se entenderá como rellenado y válido, lo que no permite proceder con el pedido.
diff --git a/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md b/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
index 6894a3291..da95b0ef2 100644
--- a/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
+++ b/docs/known-issues/es/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
@@ -18,9 +18,7 @@ internalReference: 654370
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La UI de logística permite a un usuario crear un Almacén registrando un ID con espacio y esto afecta directamente a las peticiones realizadas a este almacén pudiendo provocar fallos en la actualización del inventario.
diff --git a/docs/known-issues/es/special-character-in-seller-name-report.md b/docs/known-issues/es/special-character-in-seller-name-report.md
index e174a5f6c..2e75a676b 100644
--- a/docs/known-issues/es/special-character-in-seller-name-report.md
+++ b/docs/known-issues/es/special-character-in-seller-name-report.md
@@ -18,9 +18,7 @@ internalReference: 756243
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Específicamente para el caracter especial ":", cuando tenemos un vendedor con este caracter especial en el nombre, y tratamos de filtrarlo para reportarlo, tenemos lo siguiente cuando lo vemos en "devtools":
diff --git a/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md b/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
index 1282869e6..f0bd993c9 100644
--- a/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
+++ b/docs/known-issues/es/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
@@ -18,9 +18,7 @@ internalReference: 602054
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los tipos de campo CNPJ y CPF se utilizan entre varias partes de VTEX y son campos esenciales presentes también en la entidad MasterData CL.
diff --git a/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md b/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
index e1b927bfb..8857d1550 100644
--- a/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
+++ b/docs/known-issues/es/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
@@ -18,9 +18,7 @@ internalReference: 953285
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, SNO (Shipping Notification Order) acepta que se envíe un número de factura (invoiceNumber) a través de API y UI con un "carácter especial" al final o al principio de los datos, por ejemplo: "#123456".
diff --git a/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md b/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
index cb793d0f2..4c1f555e2 100644
--- a/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
+++ b/docs/known-issues/es/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
@@ -18,9 +18,7 @@ internalReference: 337933
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los caracteres especiales en el nombre de la SKU rompen la selección de la SKU en las páginas PDP del Portal Web Store para la selección del tipo de categoría de la caja de radio, por ejemplo, caracteres como `%`.
diff --git a/docs/known-issues/es/specification-field-delete-button-not-functional.md b/docs/known-issues/es/specification-field-delete-button-not-functional.md
index 7357b168e..203159ec7 100644
--- a/docs/known-issues/es/specification-field-delete-button-not-functional.md
+++ b/docs/known-issues/es/specification-field-delete-button-not-functional.md
@@ -18,9 +18,7 @@ internalReference: 328943
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la página de campos de especificación, nuestro administrador heredado tiene un botón de "eliminar" que no funciona, esta acción no está disponible para la tienda.
diff --git a/docs/known-issues/es/specification-value-ordering-is-not-saved.md b/docs/known-issues/es/specification-value-ordering-is-not-saved.md
index 56d70e87d..0baae42b9 100644
--- a/docs/known-issues/es/specification-value-ordering-is-not-saved.md
+++ b/docs/known-issues/es/specification-value-ordering-is-not-saved.md
@@ -18,9 +18,7 @@ internalReference: 584182
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No es posible cambiar el orden de los valores de las especificaciones para las cuentas con un gran volumen de valores. Cuando se cambia el orden de algún valor, la página se recarga y el cambio no se guarda
diff --git a/docs/known-issues/es/specifications-multiplied-on-catalog.md b/docs/known-issues/es/specifications-multiplied-on-catalog.md
index 8701b084f..7c78778a6 100644
--- a/docs/known-issues/es/specifications-multiplied-on-catalog.md
+++ b/docs/known-issues/es/specifications-multiplied-on-catalog.md
@@ -18,9 +18,7 @@ internalReference: 919761
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El mercado puede aprobar los productos enviados por los vendedores en el módulo de Skus Recibidos.
diff --git a/docs/known-issues/es/split-items-order-with-value-as-0-zero-on-the-invoice.md b/docs/known-issues/es/split-items-order-with-value-as-0-zero-on-the-invoice.md
index 2261c45e6..1cd74e121 100644
--- a/docs/known-issues/es/split-items-order-with-value-as-0-zero-on-the-invoice.md
+++ b/docs/known-issues/es/split-items-order-with-value-as-0-zero-on-the-invoice.md
@@ -18,19 +18,13 @@ internalReference: 387933
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/split-package-suggestion-not-working-properly.md b/docs/known-issues/es/split-package-suggestion-not-working-properly.md
index 61ee1cad4..f22df03ac 100644
--- a/docs/known-issues/es/split-package-suggestion-not-working-properly.md
+++ b/docs/known-issues/es/split-package-suggestion-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 656810
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La sugerencia de paquetes divididos no está funcionando correctamente, cuando se termina la compra la UI sugiere los paquetes divididos en casos de diferentes muelles o diferentes tamaños y diferentes estrategias de envío.
diff --git a/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md b/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
index 4c32a502e..51562bff0 100644
--- a/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
+++ b/docs/known-issues/es/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
@@ -18,9 +18,7 @@ internalReference: 264791
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Valor del "spotPrice" (precio al contado) en el "skuJson" del Portal incorrecto en productos con múltiples vendedores.
diff --git a/docs/known-issues/es/state-registration-is-not-filled-after-approving-the-organization-request.md b/docs/known-issues/es/state-registration-is-not-filled-after-approving-the-organization-request.md
index 720ee4fb5..dfa329267 100644
--- a/docs/known-issues/es/state-registration-is-not-filled-after-approving-the-organization-request.md
+++ b/docs/known-issues/es/state-registration-is-not-filled-after-approving-the-organization-request.md
@@ -18,9 +18,7 @@ internalReference: 825127
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El campo Registro de Estado no se rellena después de aprobar la Solicitud de Organización en el admin.
diff --git a/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md b/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md
index ed87a89ab..78a875078 100644
--- a/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md
+++ b/docs/known-issues/es/status-erro-de-processamento-shipping-policy.md
@@ -18,9 +18,7 @@ internalReference: 445793
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hay un escenario con respecto al estado de la Política de Envío después de crear/actualizar los valores de carga de la API. El estado sigue pendiente como "Error al procesar" en caso de creación sin hoja de cálculo.
diff --git a/docs/known-issues/es/status-in-the-order-list-is-different-from-the-current-order-status.md b/docs/known-issues/es/status-in-the-order-list-is-different-from-the-current-order-status.md
index 840c6636f..dbf0adb70 100644
--- a/docs/known-issues/es/status-in-the-order-list-is-different-from-the-current-order-status.md
+++ b/docs/known-issues/es/status-in-the-order-list-is-different-from-the-current-order-status.md
@@ -18,9 +18,7 @@ internalReference: 577103
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos casos, la lista de pedidos muestra un estado diferente del estado actual del pedido (tarjeta).
diff --git a/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md b/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md
index 5549a5286..1c629243a 100644
--- a/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md
+++ b/docs/known-issues/es/status-on-transactions-list-doesnt-match-actual-state.md
@@ -18,9 +18,7 @@ internalReference: 1004883
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas transacciones pueden no coincidir con el estado real al abrirlas (problema de indexación).
diff --git a/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md b/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md
index 4206cfe14..03853ffb4 100644
--- a/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md
+++ b/docs/known-issues/es/stock-change-is-completed-even-after-receiving-error-500.md
@@ -18,9 +18,7 @@ internalReference: 388176
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El cliente está tratando de actualizar la cantidad de sku en el inventario y la solicitud recibió el error 500. A pesar del error, la cantidad en el inventario se cambia.
diff --git a/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md b/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
index 099096a37..d1483f2eb 100644
--- a/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
+++ b/docs/known-issues/es/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
@@ -18,9 +18,7 @@ internalReference: 769053
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la API de mantenimiento de existencias https://catalog.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit/{skuid} no realiza ninguna comprobación para el campo "CommercialConditionId".
diff --git a/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 90efc5cd0..e03fb7354 100644
--- a/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/es/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -18,19 +18,13 @@ internalReference: 479244
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md b/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
index 8913d5461..b8ed84537 100644
--- a/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
+++ b/docs/known-issues/es/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
@@ -18,9 +18,7 @@ internalReference: 419460
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hoy en día no podemos insertar/actualizar un RefId ya registrado para otro SKU utilizando la API REST, la carga de hojas de cálculo o el Catalog Admin, pero utilizando el WebService podemos insertar un RefId existente.
diff --git a/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md b/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md
index fc52bd9e3..b2e5c311e 100644
--- a/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md
+++ b/docs/known-issues/es/storefront-permissions-app-sets-documenttype-as-cpf.md
@@ -18,9 +18,7 @@ internalReference: 798330
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La aplicación de permisos de la tienda siempre establece el campo "clientProfileData.documentType" como "cpf" en el orderForm. Esto puede causar que la transacción sea denegada por el proveedor.
diff --git a/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md b/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md
index eadcf6990..412e5a9f1 100644
--- a/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md
+++ b/docs/known-issues/es/storefront-permissions-considers-inactive-organizations.md
@@ -18,9 +18,7 @@ internalReference: 927174
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un usuario tiene asignada más de una organización, y la primera registrada está inactiva, no se reconoce como asignada ninguna organización tras el login.
diff --git a/docs/known-issues/es/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md b/docs/known-issues/es/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md
index 438071345..ed75d3247 100644
--- a/docs/known-issues/es/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md
+++ b/docs/known-issues/es/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 563507
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la dirección se introduce a través de la API de código postal y estos datos se actualizan en el shippingData antes de llegar a la caja. Si nuestra API postal no devuelve todos los datos completos, por ejemplo, calle, barrio, etc. faltarán en shippingData. El problema es que cuando el cliente utiliza el componente de geolocalización en su checkout, no realiza la validación de estos campos que faltan, dejando que el usuario vaya al paso de pago sin rellenar los datos que no están completos.
diff --git a/docs/known-issues/es/stucked-not-found-routes-on-platform.md b/docs/known-issues/es/stucked-not-found-routes-on-platform.md
index c214da439..9329c7826 100644
--- a/docs/known-issues/es/stucked-not-found-routes-on-platform.md
+++ b/docs/known-issues/es/stucked-not-found-routes-on-platform.md
@@ -18,9 +18,7 @@ internalReference: 793457
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a la falta de notificaciones y problemas de caché, algunas rutas son cacheadas en no encontradas en vbase y en rewriter por store-indexer impactando en la experiencia cuando estas rutas vuelven a estar disponibles, siendo necesario enviar una nueva indexación y nuevas notificaciones o esperar a que el tiempo de store-indexer vuelva a activar la nueva indexación.
diff --git a/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md b/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md
index 67676fa2c..c75430a64 100644
--- a/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md
+++ b/docs/known-issues/es/subscribers-report-does-not-show-active-subscriptions-correctly.md
@@ -18,9 +18,7 @@ internalReference: 587556
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando exportamos el informe de suscriptores, la información de las columnas `TotalSubscriptions` y `TotalSubscriptionsActives` son divergentes en comparación con la información mostrada en el tablero.
diff --git a/docs/known-issues/es/subscription-event-history-out-of-order.md b/docs/known-issues/es/subscription-event-history-out-of-order.md
index b7b620af0..fcea8ae5f 100644
--- a/docs/known-issues/es/subscription-event-history-out-of-order.md
+++ b/docs/known-issues/es/subscription-event-history-out-of-order.md
@@ -18,9 +18,7 @@ internalReference: 872697
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el Historial de suscripciones en el área Mi suscripción , no muestra los eventos en un orden predefinido, por lo que puede mostrar los eventos en orden no cronológico;
diff --git a/docs/known-issues/es/subscription-options-translations-dont-work-properly-for-some-languages.md b/docs/known-issues/es/subscription-options-translations-dont-work-properly-for-some-languages.md
index 3cbb1b632..322d84cd9 100644
--- a/docs/known-issues/es/subscription-options-translations-dont-work-properly-for-some-languages.md
+++ b/docs/known-issues/es/subscription-options-translations-dont-work-properly-for-some-languages.md
@@ -18,9 +18,7 @@ internalReference: 561186
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el carrito, los periodos de suscripción están mal en UI. Pero, si nos fijamos en el orderForm, el período se muestra correctamente.
diff --git a/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md b/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
index fbdd24fcb..9722a134d 100644
--- a/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
+++ b/docs/known-issues/es/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
@@ -18,9 +18,7 @@ internalReference: 571080
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md b/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md
index ad8ec044b..f02e78cf5 100644
--- a/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md
+++ b/docs/known-issues/es/subscriptions-dashboard-with-conflicting-information.md
@@ -18,9 +18,7 @@ internalReference: 587579
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md b/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
index 56b3764e2..1071dc10c 100644
--- a/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
+++ b/docs/known-issues/es/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
@@ -18,9 +18,7 @@ internalReference: 961526
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La creación de solicitudes de suscripción depende del retorno de una consulta realizada a la base de datos de suscripciones, esta consulta se realiza periódicamente para identificar qué suscripciones deben ejecutarse en ese periodo, si esta consulta falla o no devuelve una suscripción en particular, su ciclo no se ejecuta, y no se registra ningún error, resultando así una suscripción con la próximaFechaDeCompra en el pasado.
diff --git a/docs/known-issues/es/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md b/docs/known-issues/es/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md
index add898a4f..9360df5bf 100644
--- a/docs/known-issues/es/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md
+++ b/docs/known-issues/es/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md
@@ -18,9 +18,7 @@ internalReference: 395965
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Existe la condición de que los Pedidos desde Suscripción no se pueden crear porque están vinculados a un **regalo no disponible**, aunque los artículos de una suscripción estén disponibles.
diff --git a/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md b/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
index ae60ef5f8..53a775aef 100644
--- a/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
+++ b/docs/known-issues/es/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 903332
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para realizar un pedido de suscripción o actualizar una suscripción, el sistema de suscripción realiza una simulación, y en esta simulación utiliza los datos de entrega devueltos por el sistema logístico, y si dentro de estos datos hay un punto de recogida cuyo ID está subrayado, el sistema de suscripción no podrá elegir correctamente el ANS, generando así el error "AddressProvider inválido:...." en la simulación y en consecuencia no generará el pedido.
diff --git a/docs/known-issues/es/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md b/docs/known-issues/es/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md
index a3f21735e..ab9577b19 100644
--- a/docs/known-issues/es/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md
+++ b/docs/known-issues/es/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md
@@ -18,9 +18,7 @@ internalReference: 666701
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md b/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md
index 94c66ae3a..8041a0524 100644
--- a/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md
+++ b/docs/known-issues/es/substitute-words-with-less-than-3-characters-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 282500
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Sustituir palabras con menos de 3 caracteres no funciona
diff --git a/docs/known-issues/es/suggestions-transforming-unitmultiplier-less-than-1-to-0.md b/docs/known-issues/es/suggestions-transforming-unitmultiplier-less-than-1-to-0.md
index 098b41c4d..0041835ab 100644
--- a/docs/known-issues/es/suggestions-transforming-unitmultiplier-less-than-1-to-0.md
+++ b/docs/known-issues/es/suggestions-transforming-unitmultiplier-less-than-1-to-0.md
@@ -18,9 +18,7 @@ internalReference: 702056
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md b/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
index a9aa10833..f0146c43d 100644
--- a/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
+++ b/docs/known-issues/es/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
@@ -18,9 +18,7 @@ internalReference: 978571
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En las cuentas españolas, el inicio de sesión en la caja a través de "Actualizar la información de la dirección seleccionada" después de identificarse con un perfil completo hace que algunos textos del resumen se traduzcan al inglés.
diff --git a/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md b/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
index dc3a575e4..6b846a166 100644
--- a/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
+++ b/docs/known-issues/es/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
@@ -18,9 +18,7 @@ internalReference: 491180
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza el vtex.store-components product-image, al deslizar una imagen hacia un lado después de hacer clic en ella para el zoom, la primera imagen se mantendrá ampliada, causando problemas de renderización cuando el usuario desliza de nuevo a ella.
diff --git a/docs/known-issues/es/sww-on-the-pages-with-collections-or-categories.md b/docs/known-issues/es/sww-on-the-pages-with-collections-or-categories.md
index 9ec4cc421..a5f2b274e 100644
--- a/docs/known-issues/es/sww-on-the-pages-with-collections-or-categories.md
+++ b/docs/known-issues/es/sww-on-the-pages-with-collections-or-categories.md
@@ -18,9 +18,7 @@ internalReference: 785324
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, cuando cargamos una categoría o colección, ya sea por view-part o desde la propia página de la colección/categoría, se muestra un error SWW en toda la página.
diff --git a/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md b/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md
index fa4501df8..16dde5fbc 100644
--- a/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md
+++ b/docs/known-issues/es/synonyms-import-presenting-success-even-for-failed-actions.md
@@ -18,9 +18,7 @@ internalReference: 984557
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La importación de sinónimos para archivos CSV devolverá un mensaje de éxito incluso para las acciones que fallaron.
diff --git a/docs/known-issues/es/synonyms-not-reflecting-on-the-explained-search.md b/docs/known-issues/es/synonyms-not-reflecting-on-the-explained-search.md
index 6ebcfdab9..4b4f239e4 100644
--- a/docs/known-issues/es/synonyms-not-reflecting-on-the-explained-search.md
+++ b/docs/known-issues/es/synonyms-not-reflecting-on-the-explained-search.md
@@ -18,9 +18,7 @@ internalReference: 774307
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Teníamos un escenario en el que un producto, incluso con un sinónimo aplicado a él, no aparecía en la pantalla de Búsqueda Explicada. Esto suele ocurrir con sinónimos unidireccionales.
diff --git a/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md b/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md
index 9c14a6360..e58c1f02d 100644
--- a/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md
+++ b/docs/known-issues/es/synonyms-not-shown-in-the-explained-search.md
@@ -18,9 +18,7 @@ internalReference: 774307
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Es posible que algunos productos no presenten sus sinónimos en la página de administración de búsqueda explicada. Esto suele ocurrir con los sinónimos unidireccionales.
diff --git a/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md b/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md
index 53ad2f577..8fd75dd85 100644
--- a/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md
+++ b/docs/known-issues/es/system-considering-seller-1-for-rule-sellers-limit.md
@@ -18,9 +18,7 @@ internalReference: 564614
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hoy en día, en un escenario en el que tenemos una cuenta que utiliza una arquitectura en el modelo MOI (marketplace/vendedor multinivel), el sistema considera al vendedor 1 como parte del cálculo para limitar el número de vendedores en el carro que se puede configurar utilizando la clave maxNumberOfWhiteLabelSellers
diff --git a/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md b/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md
index e4e534d3a..3bb41f3bd 100644
--- a/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md
+++ b/docs/known-issues/es/tags-wont-sometimes-appear-on-list-format-plp-view.md
@@ -18,9 +18,7 @@ internalReference: 982200
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al visualizar el PLP en vista de lista, las etiquetas de los elementos.
diff --git a/docs/known-issues/es/tax-apportionment-divergence.md b/docs/known-issues/es/tax-apportionment-divergence.md
index 4bcb4b8a1..4ac2125d4 100644
--- a/docs/known-issues/es/tax-apportionment-divergence.md
+++ b/docs/known-issues/es/tax-apportionment-divergence.md
@@ -18,9 +18,7 @@ internalReference: 561466
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El prorrateo de un valor fiscal realizado por el módulo de Promociones considera los decimales, resultando en un valor fiscal total diferente al establecido.
diff --git a/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md b/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
index 91559e07b..86c88573b 100644
--- a/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
+++ b/docs/known-issues/es/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
@@ -18,9 +18,7 @@ internalReference: 1058148
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al guardar impuestos en el módulo de promociones, el valor desplegable para "al menos uno de los siguientes" o "todos los siguientes" no se muestra después de guardar el impuesto. En consecuencia, el usuario no puede averiguar cuál de ellos se está utilizando.
diff --git a/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md b/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
index 38e2b5357..262ef3a05 100644
--- a/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
+++ b/docs/known-issues/es/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
@@ -18,9 +18,7 @@ internalReference: 932667
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se aplica un precio manual a un artículo para disminuir el precio, la solicitud del centro de impuestos no lo suma y muestra los totales de descuento siempre como 0.
diff --git a/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md b/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
index f19d7c678..e75151b0a 100644
--- a/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
+++ b/docs/known-issues/es/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
@@ -18,9 +18,7 @@ internalReference: 906518
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utilizan Opciones de Montaje, si el artículo se añade de nuevo al carrito, aparecerá dos veces y el Servicio de Impuestos considerará sólo el precio para ese artículo que está primero en el carrito, causando valores de divergencia de impuestos al realizar un pedido.
diff --git a/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md b/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
index eb6d1bd4e..c48a4b500 100644
--- a/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
+++ b/docs/known-issues/es/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
@@ -18,9 +18,7 @@ internalReference: 995527
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar el servicio de impuestos, si hay una promoción que divide artículos, por ejemplo, una promoción Más por menos y una promoción de envío gratuito, el envío gratuito no se aplica correctamente para todos los artículos en la solicitud del servicio de impuestos, lo que provoca un cálculo erróneo y evita que el pedido se cree con el mensaje "No se ha podido crear el pedido solicitado. Por favor, inténtelo de nuevo".
diff --git a/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md b/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
index 5dea8ac3d..2e39bd088 100644
--- a/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
+++ b/docs/known-issues/es/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
@@ -18,9 +18,7 @@ internalReference: 900120
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar el servicio de impuestos, si hay una promoción nominal aplicada en el carrito y se produce una división de artículos, la solicitud de pago no tiene la promoción nominal aplicada, no permitiendo finalizar la compra, y se mostrará el mensaje "No se ha podido crear el pedido solicitado. Por favor, inténtelo de nuevo".
diff --git a/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md b/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
index f6f8cdf56..3aa702b7a 100644
--- a/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
+++ b/docs/known-issues/es/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
@@ -18,9 +18,7 @@ internalReference: 1074168
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un carrito con artículos para recogida y entrega, la simulación de checkout sólo considera la información del objeto shippingData.address para la solicitud del servicio de impuestos. Por ejemplo, considerando que esas direcciones son de diferentes estados, y el proveedor de impuestos considera diferentes impuestos para cada estado, a uno de los artículos se le aplicará el impuesto incorrecto.
diff --git a/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md b/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md
index f0556f128..ba171f72e 100644
--- a/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md
+++ b/docs/known-issues/es/tax-service-uses-document-data-instead-of-customer-email.md
@@ -18,9 +18,7 @@ internalReference: 548671
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md b/docs/known-issues/es/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md
index fb9e1a951..26e2447d1 100644
--- a/docs/known-issues/es/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md
+++ b/docs/known-issues/es/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md
@@ -18,9 +18,7 @@ internalReference: 797651
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se utiliza el flag RequiresAuthenticationToLoadProfile de las APIs de checkout con una app de televenta para suplantar usuarios, no se está lanzando ningún tipo de feedback al usuario si la suplantación se ha realizado con éxito y provoca algunas inconsistencias en el flujo
diff --git a/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
index 68ceff8f1..1e63fe864 100644
--- a/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
+++ b/docs/known-issues/es/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -18,9 +18,7 @@ internalReference: 1072418
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, al utilizar el buscador de televentas, un usuario puede suplantar la identidad de compradores para ayudar en las compras y, para ello, es necesario introducir, en el buscador nativo, el email de quien se va a suplantar.
diff --git a/docs/known-issues/es/term-makes-search-api-have-no-return.md b/docs/known-issues/es/term-makes-search-api-have-no-return.md
index 31ae3534b..aa7d4e90d 100644
--- a/docs/known-issues/es/term-makes-search-api-have-no-return.md
+++ b/docs/known-issues/es/term-makes-search-api-have-no-return.md
@@ -18,9 +18,7 @@ internalReference: 570542
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas palabras son ignoradas por la búsqueda, en el caso de "é", el término debe ser convertido en "e" y luego ignorado por la búsqueda. Pero una búsqueda con ese término devolverá una búsqueda vacía.
diff --git a/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md b/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
index 4484b06ca..d364c5a34 100644
--- a/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
+++ b/docs/known-issues/es/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 1026103
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar traducir un texto utilizando el editor del sitio para el botón Añadir al carro, los cambios no se aplicarán en el frente de la tienda.
diff --git a/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md b/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md
index 5f187adc0..d456ef2be 100644
--- a/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md
+++ b/docs/known-issues/es/text-in-infocard-is-not-being-translated-using-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 1049491
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar traducir un texto utilizando el editor del sitio para el componente de la tarjeta de información, los cambios no se aplicarán en el frente de la tienda.
diff --git a/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md b/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md
index 5aec72f7b..3590317d0 100644
--- a/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md
+++ b/docs/known-issues/es/text-in-store-login-are-not-being-translated-using-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 911757
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al tratar de traducir un texto utilizando el editor de sitio para el inicio de sesión de la tienda, los cambios no se aplicarán en el frente de la tienda.
diff --git a/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index 4faa791d4..367f0c00b 100644
--- a/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/es/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -18,9 +18,7 @@ internalReference: 795900
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En algunos escenarios, al aprobar un producto en un Marketplace, en la aplicación de SKUs Recibidos, la petición falla al introducir los datos en el catálogo y al reintentar, los campos textlink rellenan los caracteres "-" con " ", cambiando el comportamiento deseado.
diff --git a/docs/known-issues/es/textlink-created-with-special-character.md b/docs/known-issues/es/textlink-created-with-special-character.md
index e0d164faf..e9c925aaa 100644
--- a/docs/known-issues/es/textlink-created-with-special-character.md
+++ b/docs/known-issues/es/textlink-created-with-special-character.md
@@ -18,9 +18,7 @@ internalReference: 537159
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un producto tiene caracteres especiales específicos en el nombre, como por ejemplo ®, el `textlink` se crea con ese carácter en la URL.
diff --git a/docs/known-issues/es/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md b/docs/known-issues/es/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md
index 6d135c329..93469cd74 100644
--- a/docs/known-issues/es/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md
+++ b/docs/known-issues/es/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md
@@ -18,9 +18,7 @@ internalReference: 768954
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar añadir un nuevo identificador de proveedor por primera vez en una cuenta, en lugar de añadir un nuevo proveedor, se actualiza el proveedor nativo actual (VtexGiftCard).
diff --git a/docs/known-issues/es/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md b/docs/known-issues/es/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md
index 7215e6709..b6ec19f09 100644
--- a/docs/known-issues/es/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md
+++ b/docs/known-issues/es/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md
@@ -18,9 +18,7 @@ internalReference: 580543
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md b/docs/known-issues/es/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md
index a3b66e9f6..7e533b7bf 100644
--- a/docs/known-issues/es/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md
+++ b/docs/known-issues/es/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md
@@ -18,9 +18,7 @@ internalReference: 670424
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el usuario elige pagar con dos tarjetas, luego cambia el método de pago y vuelve a pagar con dos tarjetas, aparecerá el mensaje "_Error inesperado"_ en la caja de opciones de pago.
diff --git a/docs/known-issues/es/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md b/docs/known-issues/es/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md
index 2ad246c7b..0b197fc32 100644
--- a/docs/known-issues/es/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md
+++ b/docs/known-issues/es/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md
@@ -18,9 +18,7 @@ internalReference: 276250
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el cliente intenta modificar la configuración realizada para los pagos personalizados que ya tienen una regla de pago asociada, los cambios no se reflejan en el pago.
diff --git a/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md b/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
index ce0078704..90533b088 100644
--- a/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
+++ b/docs/known-issues/es/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
@@ -18,9 +18,7 @@ internalReference: 820060
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Hoy en día, nuestro cielo-authentication-app v1.2.1 está devolviendo un estado "aprobado" en el paso final del flujo cuando se llama al paso de autorización que evalúa si la autenticación ha fallado o no. Sin embargo, la aplicación sólo activa el paso de fallo cuando se produce un error en este paso. Como resultado, incluso si el estado es "fallido" en el paso anterior, pero no se produce ningún error en el paso /authorize actual, el estado se sigue considerando "aprobado", lo que nos permite realizar una solicitud a la entidad adquirente. Este no es el comportamiento esperado, ya que en este caso deberíamos denegar la autorización de pago y cambiar la transacción a "autorización denegada".
diff --git a/docs/known-issues/es/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md b/docs/known-issues/es/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md
index c09417328..3c20f43f2 100644
--- a/docs/known-issues/es/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md
+++ b/docs/known-issues/es/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md
@@ -18,9 +18,7 @@ internalReference: 799396
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El conector antifraude ClearSale utiliza el nombre del artículo como condición cuando realiza un bucle a través del minicarrito enviado por la caja. En los casos en que dos o más artículos comparten el mismo nombre, aunque tengan SKU diferentes, sólo uno de esos artículos se envía al sistema antifraude. El importe de la transacción de los artículos restantes se envía como carga.
diff --git a/docs/known-issues/es/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md b/docs/known-issues/es/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md
index 320827d47..459d084e4 100644
--- a/docs/known-issues/es/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md
+++ b/docs/known-issues/es/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md
@@ -18,9 +18,7 @@ internalReference: 391569
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La aplicación de condiciones de pago agrupadas está causando problemas de sincronización de las reglas de pago y hace que el método de pago desaparezca de la caja. la función está en Beta cerrada y no se ha instalado en las cuentas nuevas. Más detalles en la página **Habilitar condiciones de pago agrupadas en su tienda**.
diff --git a/docs/known-issues/es/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md b/docs/known-issues/es/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md
index 43c08e0c6..0ab0e4644 100644
--- a/docs/known-issues/es/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md
+++ b/docs/known-issues/es/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md
@@ -18,9 +18,7 @@ internalReference: 699374
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La interfaz de usuario de CRM no elimina los documentos, aunque se muestra el mensaje de éxito.
diff --git a/docs/known-issues/es/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md b/docs/known-issues/es/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md
index f8a4587cf..bd938730a 100644
--- a/docs/known-issues/es/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md
+++ b/docs/known-issues/es/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md
@@ -18,9 +18,7 @@ internalReference: 795997
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, nuestro sistema de tarjetas regalo no incluye una comprobación para verificar si una tarjeta regalo está activa antes de añadir o eliminar créditos. Aunque esta ruta solo afecta a la realización de transacciones con tarjetas regalo, es la única forma de hacerlo, por lo que se espera que se realice alguna validación.
diff --git a/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md b/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
index 49e15cf02..4352956c9 100644
--- a/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
+++ b/docs/known-issues/es/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
@@ -18,9 +18,7 @@ internalReference: 495352
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La sugerencia de dividir paquetes no está funcionando correctamente, cuando se finaliza la compra la interfaz de usuario sugiere la división de paquetes en casos de diferentes muelles o diferentes tamaños y diferentes estrategias de envío.
diff --git a/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md b/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
index 44b69a36c..ada5d04c3 100644
--- a/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
+++ b/docs/known-issues/es/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
@@ -18,9 +18,7 @@ internalReference: 394658
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para las tiendas de Rumania en la página _**Mi Cuenta**_ hay un campo llamado "Judet", condado en inglés, que no se muestra como guardado al editar la dirección.
diff --git a/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md b/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
index a168c57e6..e6becd605 100644
--- a/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
+++ b/docs/known-issues/es/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
@@ -18,9 +18,7 @@ internalReference: 571040
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md b/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
index c30e5d650..fc5fb95aa 100644
--- a/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
+++ b/docs/known-issues/es/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
@@ -18,9 +18,7 @@ internalReference: 391197
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las solicitudes para obtener cuotas externas en la pasarela a un vendedor distinto del mercado se realizan siempre con salesChannel = 1.
diff --git a/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md b/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
index b36473b73..68c2c3e0c 100644
--- a/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
+++ b/docs/known-issues/es/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
@@ -18,9 +18,7 @@ internalReference: 391549
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El uso de las condiciones especiales en el método de pago para filtrar el emisor está causando que la caja muestre un error "El banco emisor no es aceptado". El problema es intermitente y se notó por primera vez al utilizar la tarjeta de marca compartida de pago personalizado, pero también ocurrió en el método de pago con tarjeta de crédito.
diff --git a/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md b/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
index ba7240442..bcde13464 100644
--- a/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
+++ b/docs/known-issues/es/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
@@ -18,9 +18,7 @@ internalReference: 976005
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
index 7dbe4b2fc..6e3b6f4fd 100644
--- a/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
+++ b/docs/known-issues/es/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
@@ -18,9 +18,7 @@ internalReference: 283727
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La integración de MercadoPagoV1 y MercadoPagoV2 no funciona correctamente con la funcionalidad de guardar tarjeta en la sección "Mi Cuenta" para países que no permiten transacciones con decimales.
diff --git a/docs/known-issues/es/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/es/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md
index 80b7c5afb..9c12709f2 100644
--- a/docs/known-issues/es/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md
+++ b/docs/known-issues/es/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md
@@ -18,9 +18,7 @@ internalReference: 283727
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La integración de MercadoPagoV1 no funciona con la funcionalidad de guardar la tarjeta en la sección Mi cuenta.
diff --git a/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md b/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
index 82db528ab..531812948 100644
--- a/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
+++ b/docs/known-issues/es/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
@@ -18,9 +18,7 @@ internalReference: 481181
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El mensaje "Mi dirección de facturación es ..." en el iFrame de la tarjeta de crédito está en un idioma incorrecto cuando se utiliza el checkout en catalán.
diff --git a/docs/known-issues/es/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md b/docs/known-issues/es/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md
index d4e0ba3ed..bd40fe85f 100644
--- a/docs/known-issues/es/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md
+++ b/docs/known-issues/es/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md
@@ -18,9 +18,7 @@ internalReference: 353656
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md b/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
index 8fd6d5019..0a7bcf780 100644
--- a/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
+++ b/docs/known-issues/es/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
@@ -18,9 +18,7 @@ internalReference: 902539
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El conector de PayU no maneja los datos de dirección recibidos de la caja y los envía al proveedor tal cual, sin ninguna modificación. Sin embargo, en la documentación del proveedor se indica que dichos datos no deben superar los 40 caracteres.
diff --git a/docs/known-issues/es/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md b/docs/known-issues/es/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md
index e8260becf..747f98eda 100644
--- a/docs/known-issues/es/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md
+++ b/docs/known-issues/es/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md
@@ -18,9 +18,7 @@ internalReference: 669619
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md b/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
index 4e04c0430..1c82143d7 100644
--- a/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
+++ b/docs/known-issues/es/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
@@ -18,9 +18,7 @@ internalReference: 309820
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El botón de compra se mantiene activo incluso con un crédito insuficiente en el crédito del cliente.
diff --git a/docs/known-issues/es/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md b/docs/known-issues/es/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md
index 7689b492d..64a358d87 100644
--- a/docs/known-issues/es/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md
+++ b/docs/known-issues/es/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md
@@ -18,9 +18,7 @@ internalReference: 789146
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunos proveedores SAML necesitan recibir parámetros como query string, pero nuestra solución SAML no permite enviar estos parámetros (como parámetros SAMLRequest y SAMLResponse) como query string en el login CRM porque el sistema CRM utiliza una versión del sistema de login, que no soporta esta característica.
diff --git a/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index 14ae7540d..399ed8db5 100644
--- a/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/es/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -18,9 +18,7 @@ internalReference: 308892
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el cliente intenta añadir una nueva tarjeta en la sección Mi cuenta de las tiendas cuyas afiliaciones no devuelven una respuesta sincrónica, el sistema devolverá _ocurrió un error al intentar registrar la tarjeta_ y se podrá generar un cargo indebido de R$1,50.
diff --git a/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md b/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
index 22be6fe3d..a83ad626d 100644
--- a/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
+++ b/docs/known-issues/es/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
@@ -18,9 +18,7 @@ internalReference: 1035873
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de desplazamiento está diseñada para manejar grandes conjuntos de datos permitiendo la recuperación de documentos de forma desplazable. Sin embargo, cuando se consultan entidades con un número significativo de documentos, normalmente millones, los usuarios pueden encontrarse con errores 429 (Demasiadas solicitudes) y/o 408 (Tiempo de espera de la solicitud). Estos errores surgen debido al elevado volumen de datos que se procesan, que puede saturar la API y provocar la limitación de la tasa de solicitudes o tiempos de espera.
diff --git a/docs/known-issues/es/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md b/docs/known-issues/es/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md
index 959a6ca47..3a22b2b8d 100644
--- a/docs/known-issues/es/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md
+++ b/docs/known-issues/es/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md
@@ -18,9 +18,7 @@ internalReference: 770337
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un escenario donde el cliente tiene vales de fidelidad y llega a la caja, se espera que la ruta /_search devuelva todos los vales vinculados a ese usuario. Sin embargo, la caja pasa la cabecera con REST-range = 0-9. En algunas cuentas, este rango no es suficiente y la API devuelve una matriz vacía. Cuando simulamos la llamada directamente a la API con un rango superior a 10, podemos recuperar al menos un vale.
diff --git a/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md b/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
index 18d57c459..2536b1a1b 100644
--- a/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
+++ b/docs/known-issues/es/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
@@ -18,9 +18,7 @@ internalReference: 309117
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El sistema no está enviando la cancelación parcial de una transacción de Giftcard.
diff --git a/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md b/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
index 98fd99d7e..64a459f68 100644
--- a/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
+++ b/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
@@ -18,9 +18,7 @@ internalReference: 319750
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El sistema no funciona con más de una afiliación de pago de prórroga
diff --git a/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md b/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md
index 75397b29e..104192530 100644
--- a/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md
+++ b/docs/known-issues/es/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md
@@ -18,19 +18,13 @@ internalReference: 319750
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index fef0d3589..99ffa9e71 100644
--- a/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/es/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -18,9 +18,7 @@ internalReference: 585906
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el mensaje de retorno del informe de importación de inventario está en _pt-BR_. Por lo tanto, cuando la importación está terminada, el correo electrónico lanzado a través de la plantilla "`relatorio-de-importacao-de-estoque`" tiene la información en _pt-BR_, sin considerar la configuración regional de la tienda.
diff --git a/docs/known-issues/es/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md b/docs/known-issues/es/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md
index b6f90387a..29d7a4305 100644
--- a/docs/known-issues/es/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md
+++ b/docs/known-issues/es/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md
@@ -18,9 +18,7 @@ internalReference: 778408
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, la API /interactions sólo puede recuperar un máximo de 5000 líneas del archivo S3 donde se almacenan todos los datos. Esto puede crear un problema cuando una transacción genera registros que superan este límite.
diff --git a/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md b/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
index d6b0da88f..ad251c160 100644
--- a/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
+++ b/docs/known-issues/es/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
@@ -18,9 +18,7 @@ internalReference: 430650
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El usuario que ha iniciado la sesión no puede realizar una suscripción diaria directamente desde la pestaña Suscripción de Mi Cuenta. El botón parece no responder y no aparece ningún mensaje de error. Parece que otras frecuencias, como las suscripciones mensuales o anuales, funcionan normalmente.
diff --git a/docs/known-issues/es/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md b/docs/known-issues/es/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md
index 0c03402ef..cb965c96d 100644
--- a/docs/known-issues/es/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md
+++ b/docs/known-issues/es/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md
@@ -18,9 +18,7 @@ internalReference: 325491
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si un cliente realiza un pedido con el método de pago de pagarés y el pago no se realiza, la transacción no es cancelada por la pasarela después de la fecha de vencimiento del pago. En consecuencia, como la OMS no puede identificar el evento de cancelación, el pedido no se cancela
diff --git a/docs/known-issues/es/this-is-a-test.md b/docs/known-issues/es/this-is-a-test.md
index 429454a52..1e576d3b3 100644
--- a/docs/known-issues/es/this-is-a-test.md
+++ b/docs/known-issues/es/this-is-a-test.md
@@ -18,9 +18,7 @@ internalReference: 741722
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Describa el fallo de forma concisa.
diff --git a/docs/known-issues/es/time-out-at-relatorioindexacaoaspx.md b/docs/known-issues/es/time-out-at-relatorioindexacaoaspx.md
index f855defcb..eba49c010 100644
--- a/docs/known-issues/es/time-out-at-relatorioindexacaoaspx.md
+++ b/docs/known-issues/es/time-out-at-relatorioindexacaoaspx.md
@@ -18,9 +18,7 @@ internalReference: 547844
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las cuentas con muchos productos pueden perder el tiempo en la pantalla del informe del índice
diff --git a/docs/known-issues/es/time-out-import-and-export-admin.md b/docs/known-issues/es/time-out-import-and-export-admin.md
index da09eedbc..68d64a16b 100644
--- a/docs/known-issues/es/time-out-import-and-export-admin.md
+++ b/docs/known-issues/es/time-out-import-and-export-admin.md
@@ -18,9 +18,7 @@ internalReference: 424902
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para algunas cuentas con muchos productos, el administrador de importación y exportación no se carga, generando un tiempo de espera
diff --git a/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md b/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md
index 69c155523..fb29c2fa6 100644
--- a/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md
+++ b/docs/known-issues/es/time-out-on-category-keywords-change-with-many-products.md
@@ -18,9 +18,7 @@ internalReference: 497335
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 No se puede cambiar las palabras clave de una categoría con muchos productos, ya que se devuelve un timeout en el proceso, ya sea por el administrador o por la API
 
diff --git a/docs/known-issues/es/timeout-api-get-accounts-approval-settings.md b/docs/known-issues/es/timeout-api-get-accounts-approval-settings.md
index 4f56c4418..ea4bdf7a8 100644
--- a/docs/known-issues/es/timeout-api-get-accounts-approval-settings.md
+++ b/docs/known-issues/es/timeout-api-get-accounts-approval-settings.md
@@ -18,9 +18,7 @@ internalReference: 772840
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/timeout-generating-internal-application-keys.md b/docs/known-issues/es/timeout-generating-internal-application-keys.md
index 7cf21660e..fa11ccf0b 100644
--- a/docs/known-issues/es/timeout-generating-internal-application-keys.md
+++ b/docs/known-issues/es/timeout-generating-internal-application-keys.md
@@ -18,9 +18,7 @@ internalReference: 1029425
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md b/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
index ef3b108f8..b6a76f00a 100644
--- a/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
+++ b/docs/known-issues/es/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
@@ -18,9 +18,7 @@ internalReference: 984482
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El registro de actualización en la interfaz de usuario de inventario a veces devuelve el error: Request failed with status code 500 for some specific SKUs, due to a timeout in the query to Analytics (where the data is stored), and no log for the SKU will be shown in the UI.
diff --git a/docs/known-issues/es/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md b/docs/known-issues/es/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md
index aa6154f5b..03d5d6bb4 100644
--- a/docs/known-issues/es/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md
+++ b/docs/known-issues/es/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md
@@ -18,9 +18,7 @@ internalReference: 741999
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los datos presentados en los informes de Analítica de Búsqueda Inteligente, relacionados con los términos resultantes del autocompletado, no coinciden con los términos Top searches presentados en autocompletado que se están mostrando al usuario cuando utiliza la barra de búsqueda en la parte frontal de la tienda. De acuerdo con el propósito del módulo, los últimos 10 términos presentados en el autocompletado deberían ser los mismos que los términos presentados en el informe Analytics, al seleccionar la opción Autocompletar.
diff --git a/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md b/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md
index 72b30890b..eba44eda6 100644
--- a/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md
+++ b/docs/known-issues/es/total-reservation-item-with-negative-value-in-inventory-ui.md
@@ -18,9 +18,7 @@ internalReference: 991735
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/tracking-error.md b/docs/known-issues/es/tracking-error.md
index c6c4e402c..cc170c76b 100644
--- a/docs/known-issues/es/tracking-error.md
+++ b/docs/known-issues/es/tracking-error.md
@@ -18,9 +18,7 @@ internalReference: 514557
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El vendedor facturó algunos pedidos pero la información de seguimiento no fue enviada a B2W.
diff --git a/docs/known-issues/es/trade-policy-api-do-not-generate-reindexing-request.md b/docs/known-issues/es/trade-policy-api-do-not-generate-reindexing-request.md
index 8ecc9d810..44576a2b5 100644
--- a/docs/known-issues/es/trade-policy-api-do-not-generate-reindexing-request.md
+++ b/docs/known-issues/es/trade-policy-api-do-not-generate-reindexing-request.md
@@ -18,9 +18,7 @@ internalReference: 276511
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Usando la API https://developers.vtex.com/vtex-rest-api/reference/catalog-api-trade-policy para insertar/borrar una Política Comercial a un producto o la API no generan una petición de reindexación.
diff --git a/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md b/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
index 0be407bbb..868eafab3 100644
--- a/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
+++ b/docs/known-issues/es/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
@@ -18,9 +18,7 @@ internalReference: 533844
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
index 20833ccfd..dd0ae2891 100644
--- a/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
+++ b/docs/known-issues/es/transaction-cancellation-error-with-unreachable-code-message.md
@@ -18,9 +18,7 @@ internalReference: 998435
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md b/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
index 773840e27..52f5b77db 100644
--- a/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
+++ b/docs/known-issues/es/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
@@ -18,9 +18,7 @@ internalReference: 1037765
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El caso más común es la transacción atascada en autorizada cuando debería estar aprobada, en este escenario el pedido no puede ser facturado.
diff --git a/docs/known-issues/es/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md b/docs/known-issues/es/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md
index c70f01889..96075a73e 100644
--- a/docs/known-issues/es/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md
+++ b/docs/known-issues/es/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md
@@ -18,9 +18,7 @@ internalReference: 697107
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las transacciones se están atascando en la etapa de "Análisis de Riesgo" porque el campo `documentType` es nulo.
diff --git a/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md b/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
index 33445415a..4fdca66cd 100644
--- a/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
+++ b/docs/known-issues/es/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
@@ -18,19 +18,13 @@ internalReference: 429082
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md b/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md
index 484e5825c..0cfe571f4 100644
--- a/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md
+++ b/docs/known-issues/es/transaction-stuck-in-status-approved-with-payment-canceled.md
@@ -18,9 +18,7 @@ internalReference: 1046365
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La transacción estaba atascada en estado aprobado, a pesar de que el pago fue cancelado.
diff --git a/docs/known-issues/es/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md b/docs/known-issues/es/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md
index 45d647545..47f8fd008 100644
--- a/docs/known-issues/es/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md
+++ b/docs/known-issues/es/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md
@@ -18,9 +18,7 @@ internalReference: 557051
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Después de enviar la Solicitud de Captura al conector NPS, recibimos su respuesta. Sin embargo, actualmente no disponemos de ninguna acción para cuando el campo `psp_ResponseCod` devuelve un valor distinto de 2. Esto provoca que la operación de captura falle, impidiendo que el pago se capture correctamente.
diff --git a/docs/known-issues/es/transactions-entered-into-wrong-conditions.md b/docs/known-issues/es/transactions-entered-into-wrong-conditions.md
index 6df2e953b..9a10e08ca 100644
--- a/docs/known-issues/es/transactions-entered-into-wrong-conditions.md
+++ b/docs/known-issues/es/transactions-entered-into-wrong-conditions.md
@@ -18,9 +18,7 @@ internalReference: 392666
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Transacciones introducidas en condiciones erróneas, más amplias de lo previsto(configurado)
diff --git a/docs/known-issues/es/transactions-made-with-payu-do-not-change-from-cancelling-status.md b/docs/known-issues/es/transactions-made-with-payu-do-not-change-from-cancelling-status.md
index 5d9d6eb9b..4eecc313b 100644
--- a/docs/known-issues/es/transactions-made-with-payu-do-not-change-from-cancelling-status.md
+++ b/docs/known-issues/es/transactions-made-with-payu-do-not-change-from-cancelling-status.md
@@ -18,9 +18,7 @@ internalReference: 338124
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la transacción entra en un estado de **cancelación** no es posible reconocerla por lo que no cambia a **cancelada**.
diff --git a/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
index a6a2b7282..38edbf580 100644
--- a/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
+++ b/docs/known-issues/es/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -18,9 +18,7 @@ internalReference: 541149
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md b/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
index fd9b15458..2a51199eb 100644
--- a/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
+++ b/docs/known-issues/es/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
@@ -18,9 +18,7 @@ internalReference: 541687
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Por defecto se cancelan y enviamos dos Solicitudes de Autorización 3Ds, y todavía no ha recibido la respuesta de Solicitud de Autorización.
diff --git a/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md b/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
index 408c37f6f..2a733276d 100644
--- a/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
+++ b/docs/known-issues/es/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
@@ -18,9 +18,7 @@ internalReference: 848524
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La indexación unificada de catálogos sólo tiene en cuenta las traducciones de los mensajes de la cuenta principal, incluso cuando se utiliza una arquitectura de subcuentas para implementar almacenes transfronterizos.
diff --git a/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md b/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
index 580408ebb..182362b81 100644
--- a/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
+++ b/docs/known-issues/es/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
@@ -18,9 +18,7 @@ internalReference: 738334
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md b/docs/known-issues/es/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md
index 183fe4fa9..fc41cdb6e 100644
--- a/docs/known-issues/es/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md
+++ b/docs/known-issues/es/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md
@@ -18,9 +18,7 @@ internalReference: 544084
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md b/docs/known-issues/es/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md
index 69883da34..180b97892 100644
--- a/docs/known-issues/es/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md
+++ b/docs/known-issues/es/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md
@@ -18,9 +18,7 @@ internalReference: 680919
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a un fallo en el paso de creación del flujo de trabajo, algunos pedidos cuyo flujo de creación se completó correctamente, pueden presentar el siguiente valor en el campo de estado: `detail.state.null` y en el listado de pedidos no muestran ningún valor de estado;
diff --git a/docs/known-issues/es/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md b/docs/known-issues/es/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md
index 9e4103353..e4380fc3f 100644
--- a/docs/known-issues/es/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md
+++ b/docs/known-issues/es/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md
@@ -18,9 +18,7 @@ internalReference: 843602
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un carrito donde hay al menos dos productos cumplidos por vendedores diferentes, si ambos vendedores han programado la recogida y el 2º artículo tiene varias opciones de ANS, la UI se pierde y selecciona automáticamente un ANS diferente y muestra el mensaje "No hay franjas horarias disponibles para esta fecha", no permitiendo ir al paso de pago.
diff --git a/docs/known-issues/es/ui-considers-only-the-available-items-to-calculate-sla.md b/docs/known-issues/es/ui-considers-only-the-available-items-to-calculate-sla.md
index f9255f0e8..5dbd36a42 100644
--- a/docs/known-issues/es/ui-considers-only-the-available-items-to-calculate-sla.md
+++ b/docs/known-issues/es/ui-considers-only-the-available-items-to-calculate-sla.md
@@ -18,9 +18,7 @@ internalReference: 797028
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se pueden seleccionar diferentes marcas blancas de vendedor para cumplir con los productos cuando se utilizan diferentes direcciones para la entrega y la recogida. Cuando se selecciona la opción de recogida y al cambiar a entrega, la interfaz de usuario sólo tiene en cuenta los artículos disponibles para calcular el nuevo ANS de entrega, aunque los productos estén disponibles. El precio de entrega sólo tendrá en cuenta los artículos seleccionados disponibles para la recogida.
diff --git a/docs/known-issues/es/ui-does-not-reflect-invoice-address-selection-markup.md b/docs/known-issues/es/ui-does-not-reflect-invoice-address-selection-markup.md
index ecb39b82c..c84b42c4c 100644
--- a/docs/known-issues/es/ui-does-not-reflect-invoice-address-selection-markup.md
+++ b/docs/known-issues/es/ui-does-not-reflect-invoice-address-selection-markup.md
@@ -18,9 +18,7 @@ internalReference: 522946
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md b/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md
index 61263bbae..6dd72c027 100644
--- a/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md
+++ b/docs/known-issues/es/ui-does-not-update-best-sla-choice-in-cart.md
@@ -18,9 +18,7 @@ internalReference: 550201
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando tenemos dos SKUs en el carrito cuyo SLAID de los artículos tiene una intersección, este es el SLA que se ofrecerá en el carrito con leanShipping activo;
diff --git a/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md b/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
index 1d4baa51a..5b48daf6a 100644
--- a/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
+++ b/docs/known-issues/es/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
@@ -18,9 +18,7 @@ internalReference: 954108
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un carro con al menos tres productos, donde los pedidos de artículos son: El 1º es para recogida programada 1, el 2º para recogida programada 2 (vendedor diferente), y el 3º es para recogida programada 1, la UI no mostrará las ventanas de entrega para seleccionar la fecha/hora de la 2ª recogida. Esto sucede porque la API agrupará el 1er artículo y el 3er artículo ya que es el mismo SLA.
diff --git a/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md b/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
index 9962130ca..459badb2a 100644
--- a/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
+++ b/docs/known-issues/es/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
@@ -18,9 +18,7 @@ internalReference: 747772
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La interfaz de usuario no muestra el formulario correcto para editar la dirección seleccionada en el paso Envío cuando se selecciona añadir primero una nueva dirección.
diff --git a/docs/known-issues/es/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md b/docs/known-issues/es/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md
index f79d8d884..c28fb3892 100644
--- a/docs/known-issues/es/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md
+++ b/docs/known-issues/es/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md
@@ -18,9 +18,7 @@ internalReference: 569132
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/ui-fails-to-change-state-between-delivery-and-collection-correctly.md b/docs/known-issues/es/ui-fails-to-change-state-between-delivery-and-collection-correctly.md
index dc4e4fd80..7c21fed53 100644
--- a/docs/known-issues/es/ui-fails-to-change-state-between-delivery-and-collection-correctly.md
+++ b/docs/known-issues/es/ui-fails-to-change-state-between-delivery-and-collection-correctly.md
@@ -18,9 +18,7 @@ internalReference: 526736
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces, cuando el usuario cambia el tipo de entrega entre entrega y recogida en el Checkout (importante que sea en el checkout y no en el carrito, aunque probablemente también ocurra en el carrito), el orderForm guarda el estado de entrega en `logisticsInfo` cuando se selecciona la recogida.
diff --git a/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md b/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
index fb054897a..6aac16144 100644
--- a/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
+++ b/docs/known-issues/es/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
@@ -18,9 +18,7 @@ internalReference: 943771
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se produce un error durante el proceso interno de realizar un pedido, la interfaz de usuario se congela en la carga sin ningún mensaje de error/advertencia.
diff --git a/docs/known-issues/es/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md b/docs/known-issues/es/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md
index 84499d700..0430fba6d 100644
--- a/docs/known-issues/es/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md
+++ b/docs/known-issues/es/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md
@@ -18,9 +18,7 @@ internalReference: 585249
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el usuario conectado llega a la fase de envío, con la dirección ya preseleccionada y con el ANS disponible para esa ubicación, al editar su dirección con exactamente la misma información rellenada anteriormente, la UI informa que no hay entrega disponible. Incluso la respuesta de la API es que sí hay SLA disponible (ya que es la misma dirección).
diff --git a/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md b/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
index ccbb0b632..361862d86 100644
--- a/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
+++ b/docs/known-issues/es/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
@@ -18,9 +18,7 @@ internalReference: 996976
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las opciones de recogida se ofrecen a los compradores en un carro con un artículo con una suscripción. Cuando se selecciona una de las opciones de recogida, el proceso de pago cambia automáticamente a entrega, pero la interfaz de usuario sigue mostrando que se ha seleccionado la opción de recogida.
diff --git a/docs/known-issues/es/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md b/docs/known-issues/es/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md
index fe2b8790f..1863441e2 100644
--- a/docs/known-issues/es/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md
+++ b/docs/known-issues/es/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md
@@ -18,9 +18,7 @@ internalReference: 771942
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md b/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
index 2f009440c..c89a0e548 100644
--- a/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
+++ b/docs/known-issues/es/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
@@ -18,9 +18,7 @@ internalReference: 906549
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un carro con al menos tres productos, donde los pedidos de artículos son: 1º es para recogida, 2º es para entrega y 3º es para recogida, la IU mostrará el punto de recogida duplicado. Esto sucede porque la API agrupará el 1er artículo y el 3er artículo ya que es el mismo SLA.
diff --git a/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
index 8b88813b8..b1652849d 100644
--- a/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
+++ b/docs/known-issues/es/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -18,9 +18,7 @@ internalReference: 909137
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al utilizar la función de sustitución de pedidos, la interfaz de usuario de la caja muestra "¡Regalos seleccionados!" aunque no haya ninguna promoción de regalos configurada.
diff --git a/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md b/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
index 86e96f54a..ac4957ab4 100644
--- a/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
+++ b/docs/known-issues/es/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
@@ -18,9 +18,7 @@ internalReference: 336371
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se establece el valor de un campo de adjunto de artículo a través de la interfaz de usuario, esto desencadena una solicitud para actualizar el orderForm, incluso si todavía hay más campos restantes.
diff --git a/docs/known-issues/es/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md b/docs/known-issues/es/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md
index 3e317d958..b902e0cb4 100644
--- a/docs/known-issues/es/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md
+++ b/docs/known-issues/es/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md
@@ -18,9 +18,7 @@ internalReference: 797023
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se pueden seleccionar diferentes marcas blancas de vendedor para entregar los productos cuando se utilizan diferentes direcciones para la entrega y la recogida. La interfaz de usuario tiene en cuenta el ANS incorrecto al cambiar entre entrega y recogida.
diff --git a/docs/known-issues/es/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md b/docs/known-issues/es/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md
index f4cfe2675..ee6a5c6d1 100644
--- a/docs/known-issues/es/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md
+++ b/docs/known-issues/es/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 774155
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando hay una división de paquetes para una entrega programada, el precio de uno de los paquetes puede ser incorrecto en la interfaz de usuario, pero los precios serán correctos en la API.
diff --git a/docs/known-issues/es/unable-to-access-vtex-payment-account.md b/docs/known-issues/es/unable-to-access-vtex-payment-account.md
index ad2162c6f..04cf25f36 100644
--- a/docs/known-issues/es/unable-to-access-vtex-payment-account.md
+++ b/docs/known-issues/es/unable-to-access-vtex-payment-account.md
@@ -18,9 +18,7 @@ internalReference: 550244
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Aparece un mensaje de error al intentar acceder al módulo de pago de VTEX
diff --git a/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md b/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md
index 4f4c4a8b0..2e48a2235 100644
--- a/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md
+++ b/docs/known-issues/es/unable-to-cancel-transactions-that-had-payout-split-config-change.md
@@ -18,9 +18,7 @@ internalReference: 364382
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se produce un cambio en la configuración, añadiendo la división del pago, y esto hace que las nuevas transacciones tengan información que no estaba disponible antes y que ahora se utilizará en la operación de cancelación, lo que hace que las transacciones creadas antes de esta configuración no se estén cancelando.
diff --git a/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md b/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
index e0edf0fa9..3c353e41b 100644
--- a/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
+++ b/docs/known-issues/es/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
@@ -18,9 +18,7 @@ internalReference: 776837
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Para cancelar o modificar un pedido en escenarios divididos, nuestra pasarela requiere un objeto de carrito. Sin embargo, si el proceso de pago a través de OMS envía un objeto de carrito nulo/desconocido, nuestra pasarela no puede procesar estas operaciones, lo que provoca un error de análisis de la biblioteca Newtonsoft utilizada en la pasarela.
diff --git a/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md b/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md
index 1a2a46688..5820a8579 100644
--- a/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md
+++ b/docs/known-issues/es/unable-to-create-produtos-relacionados-custom-element.md
@@ -18,9 +18,7 @@ internalReference: 326899
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No se puede crear el elemento personalizado "Produtos Relacionados" en el CMS
diff --git a/docs/known-issues/es/unable-to-delete-template-on-legacy-cms.md b/docs/known-issues/es/unable-to-delete-template-on-legacy-cms.md
index 1de9968df..28a14d823 100644
--- a/docs/known-issues/es/unable-to-delete-template-on-legacy-cms.md
+++ b/docs/known-issues/es/unable-to-delete-template-on-legacy-cms.md
@@ -18,9 +18,7 @@ internalReference: 332033
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los clientes no pueden eliminar las plantillas en el CMS heredado.
diff --git a/docs/known-issues/es/unable-to-download-prices-importing-results.md b/docs/known-issues/es/unable-to-download-prices-importing-results.md
index 01dd3e85f..277d9d0be 100644
--- a/docs/known-issues/es/unable-to-download-prices-importing-results.md
+++ b/docs/known-issues/es/unable-to-download-prices-importing-results.md
@@ -18,9 +18,7 @@ internalReference: 579906
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/unable-to-export-more-than-65536-lines-in-cms-builder.md b/docs/known-issues/es/unable-to-export-more-than-65536-lines-in-cms-builder.md
index a38c356d9..039e4cbdc 100644
--- a/docs/known-issues/es/unable-to-export-more-than-65536-lines-in-cms-builder.md
+++ b/docs/known-issues/es/unable-to-export-more-than-65536-lines-in-cms-builder.md
@@ -18,9 +18,7 @@ internalReference: 492861
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 No se puede exportar más de 65.536 líneas en CMS Builder (límite de líneas en .xls)
diff --git a/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md b/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md
index 7847565f2..9f6d8b5fc 100644
--- a/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md
+++ b/docs/known-issues/es/unable-to-log-in-through-the-google-app-on-ios.md
@@ -18,9 +18,7 @@ internalReference: 926239
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/unable-to-pause-seller.md b/docs/known-issues/es/unable-to-pause-seller.md
index 56c99e899..76cf2a3e8 100644
--- a/docs/known-issues/es/unable-to-pause-seller.md
+++ b/docs/known-issues/es/unable-to-pause-seller.md
@@ -18,9 +18,7 @@ internalReference: 682151
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces el mercado no puede pausar al vendedor a través del administrador o a través de la API.
diff --git a/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md b/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
index 70b3f540a..8e808d673 100644
--- a/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
+++ b/docs/known-issues/es/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
@@ -18,9 +18,7 @@ internalReference: 851911
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el host de imágenes de la hoja de cálculo utiliza un protocolo de encriptación SSL1.3, aparece un error al intentar subir la hoja de cálculo:
diff --git a/docs/known-issues/es/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md b/docs/known-issues/es/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md
index d22dcfb46..31891a7c5 100644
--- a/docs/known-issues/es/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md
+++ b/docs/known-issues/es/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 745047
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md b/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md
index 565679d7d..b19c590e8 100644
--- a/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md
+++ b/docs/known-issues/es/unavailable-products-pdp-are-still-being-returned.md
@@ -18,9 +18,7 @@ internalReference: 1041920
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un producto no está disponible, todavía se puede devolver su PDP.
diff --git a/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md b/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
index 569994231..6fa5a8910 100644
--- a/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
+++ b/docs/known-issues/es/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
@@ -18,9 +18,7 @@ internalReference: 1028763
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Búsqueda Inteligente prioriza los resultados que tienen una coincidencia exacta, teniendo en cuenta los diacríticos del término buscado y los productos.
diff --git a/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md b/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md
index 146a4af64..18964e3e9 100644
--- a/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md
+++ b/docs/known-issues/es/unecessary-simulation-requests-and-components-being-reloaded.md
@@ -18,9 +18,7 @@ internalReference: 648298
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se pueden hacer múltiples solicitudes de simulación después de los cambios en el orderForm. Esto está relacionado con el cálculo de _lean shipping_ para calcular los paquetes de envío.
diff --git a/docs/known-issues/es/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md b/docs/known-issues/es/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md
index 840c041da..b6a1a805f 100644
--- a/docs/known-issues/es/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md
+++ b/docs/known-issues/es/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md
@@ -18,9 +18,7 @@ internalReference: 462895
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Se produce un comportamiento inesperado cuando se utiliza vtex.slider-layout, si estos dos props se establecen juntos:
diff --git a/docs/known-issues/es/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md b/docs/known-issues/es/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md
index 3ebad3e42..1b1bfb73f 100644
--- a/docs/known-issues/es/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md
+++ b/docs/known-issues/es/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md
@@ -18,9 +18,7 @@ internalReference: 467702
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md b/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md
index 2b6136e2e..c8fd71b21 100644
--- a/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md
+++ b/docs/known-issues/es/unexpected-reload-happening-when-registeringupdating-a-product.md
@@ -18,9 +18,7 @@ internalReference: 863542
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
index b96eb524a..15d8642f2 100644
--- a/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
+++ b/docs/known-issues/es/unhandled-exception-error-when-changing-edition-of-account.md
@@ -18,9 +18,7 @@ internalReference: 907294
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces cuando cambiamos la edición de una cuenta o espacio de trabajo nos podemos encontrar con el siguiente error:
diff --git a/docs/known-issues/es/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md b/docs/known-issues/es/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md
index b5210657b..2b06e81e3 100644
--- a/docs/known-issues/es/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md
+++ b/docs/known-issues/es/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md
@@ -18,9 +18,7 @@ internalReference: 503446
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el usuario busca una transacción en el admin por el número de secuencia, en algunos casos, el retorno es la transacción deseada y la transacción no relacionada con el estado de devolución de cargos.
diff --git a/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md b/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
index 1cfca1f7f..9ceae4430 100644
--- a/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
+++ b/docs/known-issues/es/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
@@ -18,9 +18,7 @@ internalReference: 314227
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el mensaje de error de la interfaz ProdutoExportacaoImportacaoEspecificacaoV2.aspx en el catálogo de importación/exportación, cuando un usuario intenta exportar una ficha de producto y no hay productos en una categoría determinada (pero sí hay especificaciones registradas) no señala el origen del problema.
diff --git a/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md b/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
index 928aa4b18..f66a69e01 100644
--- a/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
+++ b/docs/known-issues/es/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
@@ -18,9 +18,7 @@ internalReference: 1032531
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La API de búsqueda inteligente se basa principalmente en la API de búsqueda por catálogo heredada por motivos de compatibilidad, pero no todas las propiedades devuelven la misma información. En algunos casos, es diferente o está vacía.
diff --git a/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md b/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
index 38b4039f6..a853635c5 100644
--- a/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
+++ b/docs/known-issues/es/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
@@ -18,9 +18,7 @@ internalReference: 608120
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md b/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
index 3e2508a32..b08137ecf 100644
--- a/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
+++ b/docs/known-issues/es/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
@@ -18,9 +18,7 @@ internalReference: 1041874
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En la interfaz de usuario de gestión de vendedores, elimine o añada una nueva política comercial a un vendedor.
diff --git a/docs/known-issues/es/update-users-name-in-the-login-section.md b/docs/known-issues/es/update-users-name-in-the-login-section.md
index cb09e203c..f24cd412d 100644
--- a/docs/known-issues/es/update-users-name-in-the-login-section.md
+++ b/docs/known-issues/es/update-users-name-in-the-login-section.md
@@ -18,9 +18,7 @@ internalReference: 542029
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualizar el nombre del usuario en la sección de inicio de sesión
diff --git a/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md b/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
index 01d7e2d30..adc3265d9 100644
--- a/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
+++ b/docs/known-issues/es/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
@@ -18,9 +18,7 @@ internalReference: 301725
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 La respuesta JSON de GET Product Specification carece de una propiedad esencial para actualizar las especificaciones preexistentes si así lo necesita el usuario.
 
diff --git a/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md b/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md
index 229be0744..0f3fe69c1 100644
--- a/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md
+++ b/docs/known-issues/es/upload-file-not-working-on-adminportalsitesdefaultcode.md
@@ -18,9 +18,7 @@ internalReference: 897956
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar subir un nuevo fichero en admin/portal/#/sites/default/code no ocurre nada. Comprobando la consola en devTools podemos ver un mensaje de error:
diff --git a/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md b/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md
index ca0640217..f3eec0c97 100644
--- a/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md
+++ b/docs/known-issues/es/url-logo-field-in-the-update-seller-request-not-updating.md
@@ -18,9 +18,7 @@ internalReference: 271480
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al intentar actualizar el campo "UrlLogo" en la ruta /api/catalog_system/pvt/seller no se reflejan los cambios.
diff --git a/docs/known-issues/es/url-redirect-with-special-characters-non-ascii-return-errors.md b/docs/known-issues/es/url-redirect-with-special-characters-non-ascii-return-errors.md
index 268913ab1..53f51dc1f 100644
--- a/docs/known-issues/es/url-redirect-with-special-characters-non-ascii-return-errors.md
+++ b/docs/known-issues/es/url-redirect-with-special-characters-non-ascii-return-errors.md
@@ -18,9 +18,7 @@ internalReference: 457047
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si creamos una redirección con algunos caracteres especiales, por ejemplo `/televisão`, no funcionará, recibiremos el siguiente error:
diff --git a/docs/known-issues/es/urls-redirecionando-para-buscavazia.md b/docs/known-issues/es/urls-redirecionando-para-buscavazia.md
index 0d107022c..75289e22f 100644
--- a/docs/known-issues/es/urls-redirecionando-para-buscavazia.md
+++ b/docs/known-issues/es/urls-redirecionando-para-buscavazia.md
@@ -18,9 +18,7 @@ internalReference: 322251
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Algunas URL están redirigiendo a una respuesta EmptySearch.
diff --git a/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md b/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
index 3631c409b..d068bfd49 100644
--- a/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
+++ b/docs/known-issues/es/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
@@ -18,9 +18,7 @@ internalReference: 1046263
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si el usuario no tiene ninguno de los permisos de CMS el usuario no debería ser capaz de acceder o incluso ver los módulos de CMS. Pero esto no sucede.
diff --git a/docs/known-issues/es/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md b/docs/known-issues/es/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md
index 1b89eee08..f037227a0 100644
--- a/docs/known-issues/es/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md
+++ b/docs/known-issues/es/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md
@@ -18,9 +18,7 @@ internalReference: 623376
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando eliminamos o perdemos el acceso al usuario vinculado a una regla de aprobación de pedidos, este pedido no puede ser reprocesado para que un nuevo usuario pueda aprobar el pedido y con ello el pedido queda pendiente de aprobación.
diff --git a/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
index a429de0b2..5d60e2915 100644
--- a/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
+++ b/docs/known-issues/es/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -18,9 +18,7 @@ internalReference: 932666
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si un usuario administrador sólo tiene el rol "**Administrador de usuarios - RESTRINGIDO**" (recurso "**Guardar usuario**"), la lista de usuarios no está disponible y no es posible realizar las ediciones o eliminaciones necesarias.
diff --git a/docs/known-issues/es/user-receives-error-message-on-first-registration-in-my-account.md b/docs/known-issues/es/user-receives-error-message-on-first-registration-in-my-account.md
index a3b1c7513..25819fada 100644
--- a/docs/known-issues/es/user-receives-error-message-on-first-registration-in-my-account.md
+++ b/docs/known-issues/es/user-receives-error-message-on-first-registration-in-my-account.md
@@ -18,9 +18,7 @@ internalReference: 619909
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando un nuevo usuario se registra en **Mi Cuenta**, la página ejecuta dos peticiones, una enviando los datos y la otra consultando el `userid` de ese usuario, pero en esta segunda petición el retorno es 404 no encontrado, y la página muestra un mensaje de error al usuario.
diff --git a/docs/known-issues/es/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md b/docs/known-issues/es/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md
index daa59b7aa..39553286f 100644
--- a/docs/known-issues/es/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md
+++ b/docs/known-issues/es/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md
@@ -18,9 +18,7 @@ internalReference: 380931
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Los usuarios no pueden acceder a la interfaz de usuario de configuración de crédito de cliente en el Admin y hemos observado el siguiente error "Prohibido" en la operación SettingQueries.
diff --git a/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md b/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md
index d79683909..293c24095 100644
--- a/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md
+++ b/docs/known-issues/es/users-cant-access-gift-card-admin-looping-page.md
@@ -18,9 +18,7 @@ internalReference: 1025971
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si los usuarios bloquean las cookies de terceros (configuración del navegador) no podrán acceder al módulo de Tarjeta Regalo en admin, hay una cookie establecida en otro dominio VTEX.
diff --git a/docs/known-issues/es/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md b/docs/known-issues/es/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md
index dc8863187..8aa188d28 100644
--- a/docs/known-issues/es/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md
+++ b/docs/known-issues/es/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md
@@ -18,9 +18,7 @@ internalReference: 465652
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El usuario no puede acceder al sistema Master Data/CRM a través de la autenticación SAML
diff --git a/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md b/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
index 406a1cfec..e423c7b87 100644
--- a/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
+++ b/docs/known-issues/es/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
@@ -18,9 +18,7 @@ internalReference: 986324
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Debido a la unificación de perfiles algunos usuarios pueden tener pedidos con diferentes emails, y esto es un problema para mostrar los pedidos en la página de mi cuenta (mis pedidos).
diff --git a/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md b/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
index f17a5b0f0..83df21ae0 100644
--- a/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
+++ b/docs/known-issues/es/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 925049
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si una cuenta tiene configurado el toggle 'UseSessionRegionAtCheckout', al añadir un artículo y el orderForm no tiene 'shippingData', no se configura el vendedor, mostrando precios y disponibilidad diferentes.
diff --git a/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md b/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
index 78ac017b4..ae4d42355 100644
--- a/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
+++ b/docs/known-issues/es/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
@@ -18,9 +18,7 @@ internalReference: 756198
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El uso de filtros en la Lista de Gestión de Pedidos genera un parámetro en la URL que ayuda a definir lo que se muestra al cargar la página y a generar el informe de pedidos exportados. En ese sentido, a medida que usamos más y más filtros, los parámetros incluidos en la URL aumentan proporcionalmente, y la cadena de consulta también, alcanzando puntos (tamaño) que pueden generar varios tipos de comportamientos no deseados.
diff --git a/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md b/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
index 4a81dae4f..d66748aee 100644
--- a/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
+++ b/docs/known-issues/es/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
@@ -18,9 +18,7 @@ internalReference: 910125
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando tenemos un bloque slider-layout con la prop `navigationStep` puesta a 1 y el `itemsPerPage` diferente de 1 el último punto estará vacío y no es posible borrarlo.
diff --git a/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md b/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
index f85a8d004..2fbc60a39 100644
--- a/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
+++ b/docs/known-issues/es/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
@@ -18,9 +18,7 @@ internalReference: 372787
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md b/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md
index 6ce0c012c..ae7ec1faf 100644
--- a/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md
+++ b/docs/known-issues/es/validatecartmutation-failing-when-large-payload.md
@@ -18,9 +18,7 @@ internalReference: 985867
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/validation-of-credit-card-fields-at-checkout-not-working-properly.md b/docs/known-issues/es/validation-of-credit-card-fields-at-checkout-not-working-properly.md
index b3408c072..8f3054da2 100644
--- a/docs/known-issues/es/validation-of-credit-card-fields-at-checkout-not-working-properly.md
+++ b/docs/known-issues/es/validation-of-credit-card-fields-at-checkout-not-working-properly.md
@@ -18,19 +18,13 @@ internalReference: 552897
 
 ## Sumario
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Simulación
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en Inglês.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en Inglês.
 
diff --git a/docs/known-issues/es/vbase-responds-404-to-vtexpagesgraphql.md b/docs/known-issues/es/vbase-responds-404-to-vtexpagesgraphql.md
index 3f9e6b517..5f8a06170 100644
--- a/docs/known-issues/es/vbase-responds-404-to-vtexpagesgraphql.md
+++ b/docs/known-issues/es/vbase-responds-404-to-vtexpagesgraphql.md
@@ -18,9 +18,7 @@ internalReference: 822031
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 VBase está respondiendo 404 a la aplicación vtex.pages-graphql instalada en la cuenta, por alguna razón, la aplicación no está siendo encontrada y, como consecuencia, el comprador se verá impactado al no poder acceder a un producto o página específica en la tienda. Este error 404 se almacena en caché durante 2 horas, por lo que el problema suele cesar una vez finalizado el almacenamiento en caché. El problema es intermitente y aún no hemos podido encontrar la razón por la que se produce.
diff --git a/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md b/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
index b7df993ed..930165457 100644
--- a/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
+++ b/docs/known-issues/es/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
@@ -18,9 +18,7 @@ internalReference: 347084
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se guarda una tarjeta en el módulo MyCards, se genera una transacción de verificación por un monto de R$ 1,50 que, después de seguir el flujo de autorización y aprobación, debe ser cancelada automáticamente. Esta transacción tiene el objetivo de validar que la tarjeta guardada es auténtica y que realiza las transacciones sin problemas.
diff --git a/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
index 15f59d1a7..b59290cd1 100644
--- a/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
+++ b/docs/known-issues/es/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -18,9 +18,7 @@ internalReference: 914314
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando el cliente realiza una compra, el autor de la versión recibe un id de usuario (guid) o un servicio, seguido del login/nombre/descripción "`Note: Not found on VTEX ID.`" en el perfil.
diff --git a/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md b/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md
index 71a4e2c96..b58cfd0a7 100644
--- a/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md
+++ b/docs/known-issues/es/via-integration-not-sending-the-description-in-card.md
@@ -18,9 +18,7 @@ internalReference: 826488
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md b/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
index de7a5acdc..c74bef8f0 100644
--- a/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
+++ b/docs/known-issues/es/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 519412
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las integraciones VTEX<>VTEX no están pudiendo enviar atributos de vídeo del vendedor al mercado.
diff --git a/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md b/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md
index 0b60b19c0..21fcb645d 100644
--- a/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md
+++ b/docs/known-issues/es/video-component-doesnt-work-properly-on-ios-devices.md
@@ -18,9 +18,7 @@ internalReference: 609462
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El componente nativo Video muestra un comportamiento incoherente al intentar renderizar iFrame de YouTube o Vimeo en dispositivos iOS. En algunas pruebas, el iFrame no se renderizaba como se esperaba, o su colocación no se ajustaba a lo establecido en el código o en el Editor del Sitio.
diff --git a/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md b/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
index bc9528d4e..a25050401 100644
--- a/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
+++ b/docs/known-issues/es/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
@@ -18,9 +18,7 @@ internalReference: 1048306
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El evento view_cart sólo se recibe en el dataLayer cada dos por tres.
diff --git a/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md b/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
index 2f2fade43..179adffd5 100644
--- a/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
+++ b/docs/known-issues/es/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
@@ -18,9 +18,7 @@ internalReference: 1040772
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando cambiamos la cantidad de un producto en el minicart el evento view_cart se dispara dos veces
diff --git a/docs/known-issues/es/visited-product-feature-does-not-work-properly.md b/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
index 1668e9d07..c898ac503 100644
--- a/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/es/visited-product-feature-does-not-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 701169
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El activador de producto visitado, que utiliza los datos capturados por Request Capture, está configurado con el filtro "checkout" establecido en "null". Sin embargo, Request Capture necesita pasar por la caja para capturar los datos de usuario y de navegación y rellenarlos en los Datos Maestros. Como resultado, el activador no funciona correctamente porque RC no puede rellenar los datos antes de la salida.
diff --git a/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md b/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
index 84db0ec1a..bd67106b5 100644
--- a/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
+++ b/docs/known-issues/es/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
@@ -18,9 +18,7 @@ internalReference: 1053623
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Aunque es posible proporcionar varios términos de búsqueda al crear una regla de merchandising visual para la Búsqueda Inteligente, no se pueden utilizar. La regla se considerará inválida y no se aplicará.
diff --git a/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md b/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
index 773ebaa35..e44a60d15 100644
--- a/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
+++ b/docs/known-issues/es/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
@@ -18,9 +18,7 @@ internalReference: 1029719
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md b/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md
index 1b13b78dc..8d9260958 100644
--- a/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md
+++ b/docs/known-issues/es/vtexcontentplaceholder-idacessorios-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 466147
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 El control `<vtex:contentPlaceHolder id="Acessorios"/>` debería traer una vista de los productos relacionados establecidos como el tipo `acessorios` a la página del producto.
diff --git a/docs/known-issues/es/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md b/docs/known-issues/es/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md
index f7cc491fd..9fe64b0e8 100644
--- a/docs/known-issues/es/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md
+++ b/docs/known-issues/es/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md
@@ -18,9 +18,7 @@ internalReference: 348128
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 `vtex.events.addData` añadiendo el parámetro pageUrl usando http, no https
diff --git a/docs/known-issues/es/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md b/docs/known-issues/es/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md
index aaea3d51f..ae1f02d6b 100644
--- a/docs/known-issues/es/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md
+++ b/docs/known-issues/es/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md
@@ -18,9 +18,7 @@ internalReference: 573017
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se elimina un punto de recogida que está vinculado a un almacén (almacén inStore), el punto de recogida sigue vinculado al almacén si se consulta a través de la API.
diff --git a/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md b/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
index ffe5f1213..ad0d3c6eb 100644
--- a/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
+++ b/docs/known-issues/es/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
@@ -18,9 +18,7 @@ internalReference: 454388
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos un problema de validación en el campo ClientId en la pantalla de Giftcards. El campo que originalmente se llamaba CPF/CNPJ en portugués, fue traducido al inglés como clientId. Pero, cuando el usuario quiere crear una nueva Giftcard a través de la UI, el campo se formatea automáticamente insertando los caracteres ".", "-" y "/" para que los datos ingresados cumplan con los estándares CPF o CNPJ
diff --git a/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md b/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
index 6c29810a9..763045a6c 100644
--- a/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
+++ b/docs/known-issues/es/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
@@ -18,9 +18,7 @@ internalReference: 768059
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Actualmente, el viewpart de webanalytics no muestra ningún mensaje de error, incluso cuando falla y no entrega contenido de metadatos al usuario.
diff --git a/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md b/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md
index 11670a471..5290a5c9e 100644
--- a/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md
+++ b/docs/known-issues/es/webops-app-is-not-fully-integrated-with-headless-cms.md
@@ -18,9 +18,7 @@ internalReference: 1048810
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md b/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
index d8d05d707..b5c2a5a8c 100644
--- a/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
+++ b/docs/known-issues/es/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
@@ -18,9 +18,7 @@ internalReference: 694809
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al acceder a "mis pedidos", el nombre que aparece es el nombre del "ProductName" sin la información del "SKU Name", sólo en la interfaz IO.
diff --git a/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 7d111d3a1..0682e8110 100644
--- a/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/es/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -18,9 +18,7 @@ internalReference: 557978
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md b/docs/known-issues/es/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md
index bf7b7dd77..786781aa8 100644
--- a/docs/known-issues/es/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md
+++ b/docs/known-issues/es/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md
@@ -18,9 +18,7 @@ internalReference: 760458
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En ocasiones, pueden producirse errores al procesar nuestras operaciones a través de la pasarela. En el caso del conector de Firstdata, puede surgir un error inmediatamente después de la aprobación de la liquidación por nuestra parte. Para solucionarlo, tenemos que volver a solicitar una liquidación. Sin embargo, debido a la idempotencia, el proveedor no vuelve a enviar una respuesta de "aprobado", lo que puede provocar que la operación se quede atascada en estado "liquidando" hasta que se produzca una nueva actualización de estado.
diff --git a/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md b/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
index b24b57096..21cfbd1e6 100644
--- a/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
+++ b/docs/known-issues/es/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
@@ -18,9 +18,7 @@ internalReference: 770949
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index 2efbe4ad8..0ef1866b2 100644
--- a/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/es/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -18,9 +18,7 @@ internalReference: 717066
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md b/docs/known-issues/es/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md
index 565f19d1c..f97b19a30 100644
--- a/docs/known-issues/es/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md
+++ b/docs/known-issues/es/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md
@@ -18,9 +18,7 @@ internalReference: 529850
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se selecciona una opción de recogida que no está resaltada, la interfaz de usuario realiza una solicitud incorrecta a la API, y con ello, la solicitud recibe un error y no actualiza los datos de esta recogida seleccionada.
diff --git a/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 497a34519..d991a3159 100644
--- a/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/es/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -18,9 +18,7 @@ internalReference: 615050
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La documentación de la APP indica que cuando el proceso de reembolso no ha funcionado, el proveedor debe responder con un `null` a este campo, y también cuando el reembolso debe realizarse manualmente, el campo de código debe tener el valor "refund-manually".
diff --git a/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md b/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
index 775d2ceee..6491508fb 100644
--- a/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
+++ b/docs/known-issues/es/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
@@ -18,9 +18,7 @@ internalReference: 514835
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En el flujo de pago `deliverySlaInMinutes` entrega junto con los detalles de la transacción a la pasarela, este dato se calcula en base al `shippingEstimate` entregado por logística, sin embargo cuando este valor entregado por logística es = 0 la respuesta de pago para `deliverySlaInMinutes` es 0 nulo, cuando lo correcto sería 0; sin embargo esto termina afectando directamente el flujo desarrollado por la pasarela para antifraude;
diff --git a/docs/known-issues/es/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md b/docs/known-issues/es/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md
index ad68abf4b..fc2148b9a 100644
--- a/docs/known-issues/es/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md
+++ b/docs/known-issues/es/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md
@@ -18,9 +18,7 @@ internalReference: 334239
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Tenemos dos integraciones internas con Braspag, una de antifraude y otra de afiliación (ambas con el mismo nombre). Al intentar hacer clic en el antifraude para configurarlo, el usuario es dirigido a los campos de configuración de la afiliación. Por lo tanto, no es posible configurar el antifraude de Braspag a través de la interfaz de administración.
diff --git a/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md b/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
index dcb20847b..0bf4afd78 100644
--- a/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
+++ b/docs/known-issues/es/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
@@ -18,9 +18,7 @@ internalReference: 859382
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando la tienda está utilizando los filtros en la opción horizontal cada vez que haga clic en un filtro de sus opciones se derrumbará. Pero, cuando se hace clic en un filtro por tercera vez el filtro no se derrumbará más. Se bloqueará.
diff --git a/docs/known-issues/es/wrong-button-calltoaction-name-in-profile-step.md b/docs/known-issues/es/wrong-button-calltoaction-name-in-profile-step.md
index 866ce4c7b..8adf33a90 100644
--- a/docs/known-issues/es/wrong-button-calltoaction-name-in-profile-step.md
+++ b/docs/known-issues/es/wrong-button-calltoaction-name-in-profile-step.md
@@ -18,9 +18,7 @@ internalReference: 514532
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al rellenar los datos en el paso de perfil en la compra y pasar al paso de envío, al volver pulsando la flecha de retorno del navegador, al llegar de nuevo al perfil el botón para pasar al siguiente paso, debería estar con el nombre de '**Ir a la entrega**' sin embargo dice '**Ir al pago**', incluso con el componente de envío aún sin rellenar.
diff --git a/docs/known-issues/es/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md b/docs/known-issues/es/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md
index 80dd0edc9..453dfde23 100644
--- a/docs/known-issues/es/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md
+++ b/docs/known-issues/es/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md
@@ -18,9 +18,7 @@ internalReference: 709180
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Las solicitudes inválidas a la API "realizar pedido" devuelven un mensaje de error erróneo, informando "Id. inválido para el artículo" en lugar de señalar qué información es incorrecta.
diff --git a/docs/known-issues/es/wrong-message-error-when-using-a-nonexisting-gift-card.md b/docs/known-issues/es/wrong-message-error-when-using-a-nonexisting-gift-card.md
index 449d026d5..338ee60fd 100644
--- a/docs/known-issues/es/wrong-message-error-when-using-a-nonexisting-gift-card.md
+++ b/docs/known-issues/es/wrong-message-error-when-using-a-nonexisting-gift-card.md
@@ -18,9 +18,7 @@ internalReference: 584102
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 hay un manejo incorrecto de uno de los errores del Sistema de Tarjeta de Regalo VTEX. Cuando el usuario está rellenando el Código de Canje de la Tarjeta Regalo en el proceso de compra, si el usuario rellena un código de compra que no existe, en lugar de ser informado de que el código no es válido, se mostrará el siguiente error en el proceso de compra "_Se ha producido un error de comunicación con el sistema de la tarjeta regalo_". Pero en realidad, no hay ningún problema de conexión, sino que el vale no existe.
diff --git a/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md b/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
index e2e6f1309..80a2401ab 100644
--- a/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
+++ b/docs/known-issues/es/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
@@ -18,9 +18,7 @@ internalReference: 934687
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md b/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md
index 6819d7bc3..5074bbb7c 100644
--- a/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md
+++ b/docs/known-issues/es/wrong-translation-for-different-fields-under-the-same-original-value.md
@@ -18,9 +18,7 @@ internalReference: 982848
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La Búsqueda Inteligente puede utilizar una traducción errónea para un campo cuyo valor en el idioma primario es el mismo entre diferentes campos.
diff --git a/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md b/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
index 53e024b89..961267e58 100644
--- a/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
+++ b/docs/known-issues/es/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 663203
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La propiedad "priceDefinition" para órdenes en el nivel "cadena" en un mercado multinivel no está siguiendo el "sellingPrice" como se esperaba. En su lugar, está siguiendo la propiedad "precio".
diff --git a/docs/known-issues/es/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md b/docs/known-issues/es/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md
index f1b7ca1f1..1b52517cd 100644
--- a/docs/known-issues/es/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md
+++ b/docs/known-issues/es/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md
@@ -18,9 +18,7 @@ internalReference: 489481
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En un escenario de Payout Split, cuando hay una cancelación parcial antes de la captura, no cambiamos los campos de destinatarios para que los valores de cuándo recibirá cada participante sean diferentes a los correctos, es decir, los valores dentro de los destinatarios de la liquidación aparecen como si no hubiera habido una cancelación parcial.
diff --git a/docs/known-issues/es/xml-file-does-not-get-price-from-swl.md b/docs/known-issues/es/xml-file-does-not-get-price-from-swl.md
index 89aa5bb1d..3364abb62 100644
--- a/docs/known-issues/es/xml-file-does-not-get-price-from-swl.md
+++ b/docs/known-issues/es/xml-file-does-not-get-price-from-swl.md
@@ -18,9 +18,7 @@ internalReference: 425027
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Si creamos un archivo XML en un MarketPlace que cargue los precios de la marca blanca de los vendedores, nuestro XML no mostrará estos precios
diff --git a/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md b/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
index 7cb456da6..882967cd7 100644
--- a/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
+++ b/docs/known-issues/es/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
@@ -18,9 +18,7 @@ internalReference: 282231
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 En los archivos XML, el campo para la categoría global está entregando la información de la categoría global definida en el nivel de categoría y no en el nivel de producto (el nivel de producto debe ser priorizado).
diff --git a/docs/known-issues/es/xml-installment-currency-does-not-apply.md b/docs/known-issues/es/xml-installment-currency-does-not-apply.md
index c5a61850a..e29ad3d48 100644
--- a/docs/known-issues/es/xml-installment-currency-does-not-apply.md
+++ b/docs/known-issues/es/xml-installment-currency-does-not-apply.md
@@ -18,9 +18,7 @@ internalReference: 976295
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Cuando se configura una moneda en un XML, se aplica a todos los campos excepto al campo "Cuota".
diff --git a/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md b/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
index 6465cecaa..8e43caee5 100644
--- a/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
+++ b/docs/known-issues/es/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
@@ -18,9 +18,7 @@ internalReference: 974722
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 La integración XML carga cualquier etiqueta relacionada con el precio, como minPrice, maxPrice, currentPrice, se cargan como una etiqueta de valor nulo (<![CDATA[]]>) cuando el artículo no está disponible y también se establece para mostrar si no está disponible.
diff --git a/docs/known-issues/es/xml-url-on-the-admin-showing-wrong-link.md b/docs/known-issues/es/xml-url-on-the-admin-showing-wrong-link.md
index f0b9a5ee0..b3e28cf1c 100644
--- a/docs/known-issues/es/xml-url-on-the-admin-showing-wrong-link.md
+++ b/docs/known-issues/es/xml-url-on-the-admin-showing-wrong-link.md
@@ -18,9 +18,7 @@ internalReference: 407528
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 A veces podemos ver un enlace erróneo al XML en el admin de XML (`/admin/Site/Xml.aspx`)
diff --git a/docs/known-issues/es/xmlaspx-timeout.md b/docs/known-issues/es/xmlaspx-timeout.md
index 1296a10f3..83d0212a6 100644
--- a/docs/known-issues/es/xmlaspx-timeout.md
+++ b/docs/known-issues/es/xmlaspx-timeout.md
@@ -18,9 +18,7 @@ internalReference: 384719
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 
diff --git a/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
index cabb0ee22..03243832c 100644
--- a/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
+++ b/docs/known-issues/es/xmls-product-name-flag-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 925965
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Al crear un XML, tenemos dos opciones diferentes para establecer el nombre del producto, en las banderas "Nombre del producto" y "Nombre del producto + Nombre SKU". Sin embargo, la bandera "Nombre del producto" no se tiene en cuenta, y el nombre del producto en el archivo sigue la regla:
diff --git a/docs/known-issues/es/xmls-returning-500-error.md b/docs/known-issues/es/xmls-returning-500-error.md
index d0ed289c8..c85f5eaea 100644
--- a/docs/known-issues/es/xmls-returning-500-error.md
+++ b/docs/known-issues/es/xmls-returning-500-error.md
@@ -18,9 +18,7 @@ internalReference: 268042
 
 ## Sumario
 
-<div class="alert alert-info">
-  <p>Este problema conocido ha sido traducido automáticamente del inglés.</p>
-</div>
+>ℹ️ Este problema conocido ha sido traducido automáticamente del inglés.
 
 
 Eventualmente, el XML puede devolver un error 500, ocurre principalmente en archivos XML grandes.
diff --git a/docs/known-issues/pt/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md b/docs/known-issues/pt/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md
index 8335215c8..abb5f0f53 100644
--- a/docs/known-issues/pt/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md
+++ b/docs/known-issues/pt/12-digits-cardnumber-being-accepted-in-checkout-and-causing-stuck-transactions.md
@@ -18,9 +18,7 @@ internalReference: 452392
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um cliente insere um cartãoNumber de 12 dígitos, apesar deste número de dígitos não ser válido, nós o enviamos várias vezes ao adquirente mesmo sabendo que ele não aprovará, uma vez que o cartãoNumber não está no padrão: [0-9]{13,19}. O resultado é uma ordem de bloqueio por vários dias até ser cancelada.
diff --git a/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md b/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md
index 2e9290d1f..c18ec36f8 100644
--- a/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md
+++ b/docs/known-issues/pt/403-error-for-all-urls-containing-develop.md
@@ -18,9 +18,7 @@ internalReference: 975182
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que um URL possa conter qualquer palavra sem gerar um erro, mas a palavra "**develop "** seguida pelo caractere "**-**" gera um erro 403 automático.
diff --git a/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md b/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
index 112226125..9b2437d54 100644
--- a/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
+++ b/docs/known-issues/pt/a-sku-can-be-active-and-have-the-activate-if-possible-flag-unchecked.md
@@ -18,9 +18,7 @@ internalReference: 931324
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que uma SKU ativa tenha o sinalizador "ativar se possível" marcado; no entanto, esse nem sempre é o caso.
diff --git a/docs/known-issues/pt/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md b/docs/known-issues/pt/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md
index dbaa1c336..83dfb702f 100644
--- a/docs/known-issues/pt/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md
+++ b/docs/known-issues/pt/a-special-time-period-condition-may-not-behave-as-expected-when-having-it-as-a-single-payment-rule.md
@@ -18,9 +18,7 @@ internalReference: 712575
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Todo o cache combinado com o recurso de Data de Vencimento pode causar um comportamento muito estranho para nossos compradores durante o Checkout. Os maiores problemas vêm da forma como o Gateway indexa os Métodos de Pagamento:
diff --git a/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md b/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
index 0e0034929..263004bb1 100644
--- a/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
+++ b/docs/known-issues/pt/a-valid-product-specification-value-can-be-returned-blank-in-the-catalog-admin.md
@@ -18,9 +18,7 @@ internalReference: 966499
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que o administrador de especificações do produto sempre apresente os valores corretos para as especificações de um produto. No entanto, isso pode não ser sempre o caso.
diff --git a/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md b/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
index 6b2aa814e..c7de6b7ec 100644
--- a/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
+++ b/docs/known-issues/pt/ab-tester-app-shows-miscalculated-information-for-sessions-and-conversion.md
@@ -18,9 +18,7 @@ internalReference: 865727
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O aplicativo AB Tester mostra informações mal calculadas para sessões e conversão ao executar testes, causando interpretação indesejada dos resultados. A funcionalidade de divisão do espaço de trabalho ainda funciona conforme o esperado.
diff --git a/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md b/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
index 10ea3ebae..496f24794 100644
--- a/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
+++ b/docs/known-issues/pt/accounts-with-on-the-name-dont-have-metrics-on-search-report.md
@@ -18,9 +18,7 @@ internalReference: 793570
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se o nome da conta é algo como "minha conta", o relatório de busca não recebe dados. Mesmo com os eventos corretamente configurados.
diff --git a/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md b/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
index c5e44b0a0..2647d2f14 100644
--- a/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
+++ b/docs/known-issues/pt/activate-service-on-import-skuvincularvalorservicoaspx-not-working.md
@@ -18,9 +18,7 @@ internalReference: 339894
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, na usabilidade de importação do SkuVincularValorServico.aspx, ao tentar alterar os serviços que saíram anteriormente de inativos para ativos, os valores não são alterados. A interface do usuário avisa que os valores foram alterados, mas nada acontece de fato.
diff --git a/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md b/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md
index 7794467d3..d7cb6796c 100644
--- a/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md
+++ b/docs/known-issues/pt/adding-a-new-address-on-invoice-address-returns-null-api-results.md
@@ -18,9 +18,7 @@ internalReference: 748668
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há mais de um endereço registrado no Sistema de Perfil, há uma solicitação "nula" ao serviço de CEP se você adicionar um novo endereço em "Endereço de Fatura".
diff --git a/docs/known-issues/pt/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md b/docs/known-issues/pt/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md
index 5a4bf2657..eb1de9af9 100644
--- a/docs/known-issues/pt/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md
+++ b/docs/known-issues/pt/address-being-reviewed-in-the-geolocation-mode-even-for-complete-addresses.md
@@ -18,9 +18,7 @@ internalReference: 618724
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O botão "calculate shipping", usado para validação de endereço no modo de geolocalização (endereço inserido via Google Maps), está sendo mostrado mesmo para endereços completos. Ele deve ser mostrado apenas para endereços editados - devido a informações alteradas ou endereços incompletos no primeiro momento - para garantir que eles sejam válidos, mas não para endereços completos.
diff --git a/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md b/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
index e6bcb606d..5066d2f67 100644
--- a/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
+++ b/docs/known-issues/pt/address-form-is-not-shown-when-the-shopper-opts-to-insert-a-new-address.md
@@ -18,9 +18,7 @@ internalReference: 1061637
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, quando um comprador identificado tenta adicionar um novo endereço na etapa de envio do checkout, uma mensagem solicitando autenticação é solicitada, mas o formulário de endereço não é exibido e não pode ser preenchido.
diff --git a/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md b/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
index 7963a1f57..e257613fb 100644
--- a/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
+++ b/docs/known-issues/pt/address-in-orderform-with-excessive-size-for-multiples-cities-separated-by.md
@@ -18,9 +18,7 @@ internalReference: 287854
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns casos, o Checkout API usa "::" como separador quando há várias possibilidades de cidades do serviço de CEP, causando um erro sobre o tamanho excessivo no endereço de campo, impactando a colocação do pedido. Este comportamento acontece porque a API tem um autocompletar para endereço
diff --git a/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md b/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md
index 24a8cb364..a2cc5b444 100644
--- a/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md
+++ b/docs/known-issues/pt/address-review-flow-is-removing-essential-address-information.md
@@ -18,9 +18,7 @@ internalReference: 618756
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A validação do endereço no modo de geolocalização (endereço inserido via Google Maps) está removendo informações essenciais, como a rua e o número, de endereços válidos, afetando o fluxo de compras.
diff --git a/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md b/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
index 21a67282f..47db9d873 100644
--- a/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
+++ b/docs/known-issues/pt/addresses-are-shown-in-the-checkout-when-buyer-has-can-add-shipping-permission.md
@@ -18,9 +18,7 @@ internalReference: 1037067
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma função tem a permissão "Pode adicionar envio" nas configurações de checkout B2B e um comprador tem endereços registrados no sistema de perfil, clicar em "Entregar em outro endereço" na etapa de envio e clicar em "Voltar à lista de endereços" mostra os endereços do sistema de perfil.
diff --git a/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md b/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
index a933a9e1f..566e3db4e 100644
--- a/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
+++ b/docs/known-issues/pt/addresses-from-the-profile-system-is-shown-when-impersonated-using-vtex-telemarketing.md
@@ -18,9 +18,7 @@ internalReference: 860375
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comprador tem endereços registrados no Profile System e se faz passar por ele usando a VTEX Telemarketing, os endereços do Profile System e das Organizações são mostrados
diff --git a/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md b/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
index 39f802401..7cff97cda 100644
--- a/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
+++ b/docs/known-issues/pt/addressid-mismatch-causes-invalid-address-for-an-item-error.md
@@ -18,9 +18,7 @@ internalReference: 992503
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O anexo de carrinho `shippingData` suporta o campo `addressId` em alguns objetos diferentes: `logisticsInfo`, `address` e `selectedAddresses`.
diff --git a/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md b/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
index 134fe3c70..2abce9369 100644
--- a/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
+++ b/docs/known-issues/pt/addtocart-function-doesnt-work-correctly-with-attachments-and-assembly-options-components-attachment.md
@@ -18,9 +18,7 @@ internalReference: 830495
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A função addToCart não funciona corretamente quando um produto tem opções de montagem e anexos configurados e um dos componentes das opções de montagem também tem anexos. Somente o anexo do componente será adicionado ao carrinho.
diff --git a/docs/known-issues/pt/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md b/docs/known-issues/pt/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md
index 7e15857fd..637098925 100644
--- a/docs/known-issues/pt/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md
+++ b/docs/known-issues/pt/adjust-message-in-bridge-for-integration-with-wl-seller-facebook.md
@@ -18,9 +18,7 @@ internalReference: 600208
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ajustar mensagem em ponte para integração com o vendedor WL
diff --git a/docs/known-issues/pt/adjust-processing-tab-export.md b/docs/known-issues/pt/adjust-processing-tab-export.md
index db8e1c8fb..918996133 100644
--- a/docs/known-issues/pt/adjust-processing-tab-export.md
+++ b/docs/known-issues/pt/adjust-processing-tab-export.md
@@ -18,9 +18,7 @@ internalReference: 649311
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exportação na aba de processamento de skus está falhando:
diff --git a/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md b/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
index f112e35e9..f19dfea9f 100644
--- a/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
+++ b/docs/known-issues/pt/adjust-shipping-query-when-the-order-has-more-than-one-product-centauro.md
@@ -18,9 +18,7 @@ internalReference: 599380
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ajuste a consulta de envio quando o pedido tem mais de um produto
diff --git a/docs/known-issues/pt/admin-collection-brand-list-timeout.md b/docs/known-issues/pt/admin-collection-brand-list-timeout.md
index b034363ec..e83a1d866 100644
--- a/docs/known-issues/pt/admin-collection-brand-list-timeout.md
+++ b/docs/known-issues/pt/admin-collection-brand-list-timeout.md
@@ -18,9 +18,7 @@ internalReference: 639905
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, para lojas que têm mais de 4000 marcas em seu catálogo, a seguinte listagem de marcas não carrega nenhuma marca quando se tenta criar uma nova coleção:
diff --git a/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md b/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
index 2858606f3..373f52953 100644
--- a/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
+++ b/docs/known-issues/pt/admin-global-search-doesnt-recognize-profile-menu-items.md
@@ -18,9 +18,7 @@ internalReference: 969645
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Pesquisa global não reconhece "Itens do menu de perfil"
diff --git a/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md b/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
index 740e274a5..f65dbdc29 100644
--- a/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
+++ b/docs/known-issues/pt/admin-is-showing-image-extension-as-jpg-even-when-the-image-is-png.md
@@ -18,9 +18,7 @@ internalReference: 516269
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na página de exportação da imagem ou no relatório da imagem exportada, a URL das imagens está com a extensão .jpg mesmo quando a imagem é PNG. Entretanto, as informações incorretas no Admin não afetam o formato real da imagem, e ao acessar a URL da imagem pela frente você pode ver que a imagem ainda é PNG.
diff --git a/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md b/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
index 281c7f3f3..39a81c7b0 100644
--- a/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
+++ b/docs/known-issues/pt/admin-master-data-module-the-admin-search-engine-redirects-them-to-the-wrong-url.md
@@ -18,9 +18,7 @@ internalReference: 889045
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No módulo Master Data, o mecanismo de pesquisa do administrador redireciona para o URL errado.
diff --git a/docs/known-issues/pt/admin-review-global-search.md b/docs/known-issues/pt/admin-review-global-search.md
index b33d90076..1bde550e5 100644
--- a/docs/known-issues/pt/admin-review-global-search.md
+++ b/docs/known-issues/pt/admin-review-global-search.md
@@ -18,9 +18,7 @@ internalReference: 889993
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A pesquisa global não está encontrando informações sobre "usuários"
diff --git a/docs/known-issues/pt/admin-timeout.md b/docs/known-issues/pt/admin-timeout.md
index 5c3509ff6..c3e0ee993 100644
--- a/docs/known-issues/pt/admin-timeout.md
+++ b/docs/known-issues/pt/admin-timeout.md
@@ -18,9 +18,7 @@ internalReference: 1051070
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O aplicativo de mensagens está recebendo um erro de tempo limite aleatoriamente e algumas páginas de administração podem precisar de uma atualização para funcionar corretamente.
diff --git a/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md b/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md
index 5921ec459..c05b9d739 100644
--- a/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md
+++ b/docs/known-issues/pt/adress-without-country-disrupting-orderform-changes.md
@@ -18,9 +18,7 @@ internalReference: 579814
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se um endereço incompleto sem a informação "país" for inserido em um formulário de pedido, os itens não podem ser acrescentados a ele.
diff --git a/docs/known-issues/pt/advanced-store-settings-being-registered-globally-insted-of-by-binding.md b/docs/known-issues/pt/advanced-store-settings-being-registered-globally-insted-of-by-binding.md
index a35673702..1a4acb380 100644
--- a/docs/known-issues/pt/advanced-store-settings-being-registered-globally-insted-of-by-binding.md
+++ b/docs/known-issues/pt/advanced-store-settings-being-registered-globally-insted-of-by-binding.md
@@ -18,9 +18,7 @@ internalReference: 783835
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md b/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md
index ae78d1357..aff32ea6d 100644
--- a/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md
+++ b/docs/known-issues/pt/adyen-3ds2-double-request-generates-payment-authorization-denial.md
@@ -18,9 +18,7 @@ internalReference: 884154
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a solicitação 3DS2 da Adyen é enviada duas vezes, ela obtém um erro na resposta e o pagamento é automaticamente negado.
diff --git a/docs/known-issues/pt/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md b/docs/known-issues/pt/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md
index 4c51ab689..144d85d50 100644
--- a/docs/known-issues/pt/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md
+++ b/docs/known-issues/pt/adyenv1-connector-is-not-sending-pspreference-on-some-operations-and-thus-causing-error.md
@@ -18,9 +18,7 @@ internalReference: 758411
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Em algumas operações, o conector nativo da AdyenV1 não está enviando o código `pspsReference` para a Adyen. Como esse campo é obrigatório para essa integração, recebemos uma resposta de erro quando ele está ausente.
 
diff --git a/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md b/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
index b53be15fc..e8d6d3090 100644
--- a/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
+++ b/docs/known-issues/pt/adyenv1-does-not-correctly-send-the-paymentmethodtype-for-amex-when-using-apple-pay.md
@@ -18,9 +18,7 @@ internalReference: 920563
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Embora o Apple Pay permita que o usuário faça um pedido usando um cartão Amex, nosso conector legado AdyenV1 não é compatível com essa marca.
diff --git a/docs/known-issues/pt/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md b/docs/known-issues/pt/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md
index 640cc4cb2..ed4fbec3e 100644
--- a/docs/known-issues/pt/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md
+++ b/docs/known-issues/pt/adyenv2ppp-is-requiring-pspreference-to-cancel-transaction.md
@@ -18,9 +18,7 @@ internalReference: 486752
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a transação é reconhecida pelo fornecedor e o status nunca muda de indefinido, a AdyenV2 exige uma pspReferência para cancelar a transação. Este não é um comportamento esperado porque este campo não existe na PPP, assim o cliente fica preso no modal PIX na UI de checkout.
diff --git a/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md b/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
index 23605656b..04c1d7aa9 100644
--- a/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
+++ b/docs/known-issues/pt/alert-for-fill-the-scheduled-delivery-selection-appears-only-once.md
@@ -18,9 +18,7 @@ internalReference: 565982
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md b/docs/known-issues/pt/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md
index 35c6e6090..6b7e05adf 100644
--- a/docs/known-issues/pt/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md
+++ b/docs/known-issues/pt/allow-in-the-new-order-admin-ui-return-values-without-relating-an-item.md
@@ -18,9 +18,7 @@ internalReference: 519576
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para fluxos de devolução dentro de um pedido, é possível indicar quais produtos serão devolvidos e/ou valores associados, tais como custos de envio ou simplesmente uma parte do valor do pedido.
diff --git a/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md b/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
index bc9fe3270..87c3ccc9c 100644
--- a/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
+++ b/docs/known-issues/pt/alt-attribute-not-showing-in-vtexcmcproductimage-zoomon-.md
@@ -18,19 +18,13 @@ internalReference: 526563
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/amazon-category-implementation.md b/docs/known-issues/pt/amazon-category-implementation.md
index 04d73f369..8ea29d0f3 100644
--- a/docs/known-issues/pt/amazon-category-implementation.md
+++ b/docs/known-issues/pt/amazon-category-implementation.md
@@ -18,9 +18,7 @@ internalReference: 549924
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md b/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
index 39a868b09..d39441938 100644
--- a/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
+++ b/docs/known-issues/pt/amazon-error-code-13013-while-sending-product-to-amazon-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 926656
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md b/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
index 1f1a6f845..fc5205afc 100644
--- a/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
+++ b/docs/known-issues/pt/amazon-error-in-the-update-flow-sku-is-not-being-logged-into-the-bridge.md
@@ -18,9 +18,7 @@ internalReference: 990197
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Erro no fluxo de atualização: o sku não está sendo registrado na ponte
diff --git a/docs/known-issues/pt/amazon-global-category-not-working.md b/docs/known-issues/pt/amazon-global-category-not-working.md
index b03272951..c5615fed7 100644
--- a/docs/known-issues/pt/amazon-global-category-not-working.md
+++ b/docs/known-issues/pt/amazon-global-category-not-working.md
@@ -18,9 +18,7 @@ internalReference: 634199
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md b/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md
index 4cd1e35f6..8349d09cc 100644
--- a/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md
+++ b/docs/known-issues/pt/amazon-integration-attribute-number-of-itens.md
@@ -18,9 +18,7 @@ internalReference: 557788
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-integration-is-not-cancelling-orders-in-vtex.md b/docs/known-issues/pt/amazon-integration-is-not-cancelling-orders-in-vtex.md
index fd32bfa10..209e949e8 100644
--- a/docs/known-issues/pt/amazon-integration-is-not-cancelling-orders-in-vtex.md
+++ b/docs/known-issues/pt/amazon-integration-is-not-cancelling-orders-in-vtex.md
@@ -18,9 +18,7 @@ internalReference: 588456
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md b/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md
index 615da298e..297f23e7c 100644
--- a/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md
+++ b/docs/known-issues/pt/amazon-integration-stock-reservations-for-kits.md
@@ -18,9 +18,7 @@ internalReference: 829583
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md
index 80c6242e4..b791dc20c 100644
--- a/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/pt/amazon-object-reference-not-set-to-an-instance-of-an-object.md
@@ -18,9 +18,7 @@ internalReference: 482173
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazon-order-integration-error.md b/docs/known-issues/pt/amazon-order-integration-error.md
index 2386188a6..c82769123 100644
--- a/docs/known-issues/pt/amazon-order-integration-error.md
+++ b/docs/known-issues/pt/amazon-order-integration-error.md
@@ -18,9 +18,7 @@ internalReference: 557223
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md b/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md
index 498734ed8..2b135a0f4 100644
--- a/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md
+++ b/docs/known-issues/pt/amazoncasacaso-erros-de-rastreamento.md
@@ -18,9 +18,7 @@ internalReference: 360564
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md b/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md
index c7d225c10..52a8e7eeb 100644
--- a/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md
+++ b/docs/known-issues/pt/an-error-has-occurred-when-adding-tracking-information.md
@@ -18,9 +18,7 @@ internalReference: 409225
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Ao inserir as informações de rastreamento quando o número da fatura contém espaços, ocorre o seguinte erro (seja via UI ou API) "`An error has occurred`".
 
diff --git a/docs/known-issues/pt/analytics-duplicated-events.md b/docs/known-issues/pt/analytics-duplicated-events.md
index f595fd645..9ca30b756 100644
--- a/docs/known-issues/pt/analytics-duplicated-events.md
+++ b/docs/known-issues/pt/analytics-duplicated-events.md
@@ -18,9 +18,7 @@ internalReference: 771986
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/analytics-error-loading-data-in-sales-performance-dashboard.md b/docs/known-issues/pt/analytics-error-loading-data-in-sales-performance-dashboard.md
index 773ce73fd..9c1407341 100644
--- a/docs/known-issues/pt/analytics-error-loading-data-in-sales-performance-dashboard.md
+++ b/docs/known-issues/pt/analytics-error-loading-data-in-sales-performance-dashboard.md
@@ -18,9 +18,7 @@ internalReference: 799899
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Erro ao carregar dados no painel `desempenho de vendas
diff --git a/docs/known-issues/pt/android-button-with-unexpected-behavior-with-the-enter-button.md b/docs/known-issues/pt/android-button-with-unexpected-behavior-with-the-enter-button.md
index 3b882f538..37ae0692b 100644
--- a/docs/known-issues/pt/android-button-with-unexpected-behavior-with-the-enter-button.md
+++ b/docs/known-issues/pt/android-button-with-unexpected-behavior-with-the-enter-button.md
@@ -18,9 +18,7 @@ internalReference: 606718
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md b/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
index a182e0fef..2c92e1875 100644
--- a/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
+++ b/docs/known-issues/pt/api-shipping-estimate-returns-wrong-info-when-sc-is-null.md
@@ -18,9 +18,7 @@ internalReference: 554948
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md b/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
index 8220cb9db..80d685721 100644
--- a/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
+++ b/docs/known-issues/pt/api-to-list-pickup-points-does-not-return-additionalinfo-field.md
@@ -18,9 +18,7 @@ internalReference: 650714
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nossa API para listar os pontos de coleta por local está sempre retornando 'nulo' no campo 'informação adicional'. Entretanto, como estes dados normalmente vêm do API de logística, então estes dados estão presentes no pedidoFormulário de pedido ao colocar um pedido na caixa.
diff --git a/docs/known-issues/pt/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md b/docs/known-issues/pt/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
index 1ee420c8d..e2da96fdb 100644
--- a/docs/known-issues/pt/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
+++ b/docs/known-issues/pt/apis-who-saw-also-saw-who-saw-also-bought-who-bought-also-bought-not-always-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 712015
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md b/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md
index df51bff0e..144deecb1 100644
--- a/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md
+++ b/docs/known-issues/pt/app-settings-are-not-erased-when-you-delete-the-app.md
@@ -18,9 +18,7 @@ internalReference: 1065954
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você instala um aplicativo da App Store e acessa suas configurações, você tem a opção "**Uninstall**", que exclui o aplicativo do espaço de trabalho, mas mantém suas configurações, e a opção "**Delete**", que exclui o aplicativo e suas configurações.
diff --git a/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md b/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
index 1400aa0dd..9e856a531 100644
--- a/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
+++ b/docs/known-issues/pt/apply-the-discount-to-the-most-expensive-items-ui-not-saving-data.md
@@ -18,9 +18,7 @@ internalReference: 1011071
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar a UI de promoções, a tentativa de salvar manualmente a opção "Aplicar aos itens mais caros" não funcionará e o seletor permanecerá na opção do tipo mais barato.
diff --git a/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md b/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md
index 9e43e589d..701f4ac9e 100644
--- a/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md
+++ b/docs/known-issues/pt/approved-skus-spreadsheet-not-showing-price.md
@@ -18,9 +18,7 @@ internalReference: 552155
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 ao utilizar a opção de exportação na guia Aprovado SKUs Recebido, o arquivo excel não possui dados nos campos Preço de Venda, Moeda e Símbolo de Moeda.
diff --git a/docs/known-issues/pt/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md b/docs/known-issues/pt/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md
index 373146f85..4c8cf8de2 100644
--- a/docs/known-issues/pt/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md
+++ b/docs/known-issues/pt/assembly-options-being-ignored-when-selected-on-pdp-and-adding-to-cart.md
@@ -18,9 +18,7 @@ internalReference: 743529
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em uma opção de montagem PDP, quando o usuário seleciona diferentes quantidades para um único item e vai para o carrinho de compras, a seleção é ignorada e as quantidades são redefinidas para a quantidade inicial. Mas se o usuário aumenta, para **todos** os itens, em 1 quantidade pelo menos a seleção é persistida.
diff --git a/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md b/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
index 9071c4fe1..12c0df06e 100644
--- a/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
+++ b/docs/known-issues/pt/attachents-api-doesnt-allow-null-domainvalues-and-it-should.md
@@ -18,9 +18,7 @@ internalReference: 897480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As solicitações de atualização para a API /api/catalog/pvt/attachment/ não estão permitindo atualizações para o campo Valor do domínio como um valor nulo.
diff --git a/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md b/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
index 2d78ce577..f4ea831cc 100644
--- a/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
+++ b/docs/known-issues/pt/attachment-update-and-create-api-validation-on-field-domainvalues-not-working.md
@@ -18,9 +18,7 @@ internalReference: 751091
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Via UI (diretamente na VTEX admin) é possível criar um anexo sem o campo **Valores permitidos** preenchidos:
diff --git a/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md b/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
index edf781556..cf34c36da 100644
--- a/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
+++ b/docs/known-issues/pt/attachment-validation-only-in-the-marketplace-when-adding-an-item-from-a-seller-with-attachment.md
@@ -18,9 +18,7 @@ internalReference: 957343
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao adicionar um item de um vendedor com um anexo na mesma solicitação de API, a validação do anexo ocorre somente no marketplace.
diff --git a/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md b/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
index 32fbacaf1..e052ca6ee 100644
--- a/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
+++ b/docs/known-issues/pt/attachments-permitted-values-are-not-updated-when-its-added-to-items.md
@@ -18,9 +18,7 @@ internalReference: 920970
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os valores permitidos do anexo não são atualizados se ele foi adicionado a um item antes de alterar seus valores no administrador. Isso causará um erro no carrinho com a mensagem "Não foi possível se comunicar com o vendedor".
diff --git a/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md b/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md
index be5426020..3dca10938 100644
--- a/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md
+++ b/docs/known-issues/pt/attribute-melishippingmode-not-being-updated-in-meli-integration.md
@@ -18,9 +18,7 @@ internalReference: 873993
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md b/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
index 13dbd6308..d9ffddb0a 100644
--- a/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
+++ b/docs/known-issues/pt/audit-pricing-logs-showing-unknow-information.md
@@ -18,9 +18,7 @@ internalReference: 856420
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas ações do usuário relacionadas a modificações de preço estão sendo registradas no módulo de auditoria como "desconhecidas".
diff --git a/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md b/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
index d17a8b1e7..e384b5cbf 100644
--- a/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
+++ b/docs/known-issues/pt/authorization-status-is-stuck-for-asynchronous-transactions-with-2-or-more-payments-when-the-first-one-is-canceled.md
@@ -18,9 +18,7 @@ internalReference: 929517
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma transação tem vários pagamentos e se torna assíncrona devido ao modo Sherlock ou Defense, e se a primeira tentativa de autorização de pagamento falhar, isso pode fazer com que os outros pagamentos fiquem presos em um status "Autorizado". Isso ocorre porque a transação inteira é cancelada, mas nosso funcionário não reconhece isso e prossegue com uma tentativa de autorização para o segundo pagamento. Consequentemente, o segundo pagamento não pode ser cancelado, pois a transação já foi cancelada e não permite uma solicitação de cancelamento.
diff --git a/docs/known-issues/pt/auto-approve-api-accepts-any-values.md b/docs/known-issues/pt/auto-approve-api-accepts-any-values.md
index 5ba52dd80..73f9744bb 100644
--- a/docs/known-issues/pt/auto-approve-api-accepts-any-values.md
+++ b/docs/known-issues/pt/auto-approve-api-accepts-any-values.md
@@ -18,9 +18,7 @@ internalReference: 713704
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a API de aprovação automática não está verificando se o vendedor existe, o que pode levar a configurações incorretas.
diff --git a/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md b/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md
index b4e508fcd..72b9efafa 100644
--- a/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md
+++ b/docs/known-issues/pt/autocomplete-bringing-suggestion-products-shown-with-delay.md
@@ -18,9 +18,7 @@ internalReference: 615616
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/autocomplete-hover-on-search-suggestion-is-not-working-properly.md b/docs/known-issues/pt/autocomplete-hover-on-search-suggestion-is-not-working-properly.md
index 06d61f018..9d6bc632e 100644
--- a/docs/known-issues/pt/autocomplete-hover-on-search-suggestion-is-not-working-properly.md
+++ b/docs/known-issues/pt/autocomplete-hover-on-search-suggestion-is-not-working-properly.md
@@ -18,19 +18,13 @@ internalReference: 697406
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md b/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md
index a9ac6de77..afe39a488 100644
--- a/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md
+++ b/docs/known-issues/pt/autocomplete-not-answering-to-cold-starts.md
@@ -18,9 +18,7 @@ internalReference: 418573
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O recurso de pesquisa inteligente conhecido como **autocompletar** não está funcionando em algumas lojas novas, mesmo após a execução de um processo interno chamado _cold start_.
diff --git a/docs/known-issues/pt/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md b/docs/known-issues/pt/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md
index ca3ea6e30..61166bc73 100644
--- a/docs/known-issues/pt/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md
+++ b/docs/known-issues/pt/autocomplete-on-search-not-always-updating-when-changed-multiple-times.md
@@ -18,9 +18,7 @@ internalReference: 793275
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar qualquer termo sem clicar em enter, o autocompletar traz resultados de produtos que contêm esse termo.
diff --git a/docs/known-issues/pt/autocomplete-search-not-working-with-space.md b/docs/known-issues/pt/autocomplete-search-not-working-with-space.md
index e71222bca..a4378b8ba 100644
--- a/docs/known-issues/pt/autocomplete-search-not-working-with-space.md
+++ b/docs/known-issues/pt/autocomplete-search-not-working-with-space.md
@@ -18,9 +18,7 @@ internalReference: 568821
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md b/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
index bd84a1822..b270f9217 100644
--- a/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
+++ b/docs/known-issues/pt/autocomplete-suggestion-api-removes-the-dot-from-the-product-name.md
@@ -18,9 +18,7 @@ internalReference: 1014701
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Esse problema ocorre quando se pesquisa um termo e a sugestão de preenchimento automático retorna o nome do produto sem o caractere de ponto ".", mesmo que ele exista no nome do produto, resultando em resultados de pesquisa incorretos.
diff --git a/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md b/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md
index c341d5e18..b5730d078 100644
--- a/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md
+++ b/docs/known-issues/pt/automatic-payment-settlement-incorrectly-setup.md
@@ -18,9 +18,7 @@ internalReference: 1053010
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O problema é que o gateway ignorou o valor `delayToAutoSettleAfterAntifraud`.
diff --git a/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md b/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
index 20056a942..ed59617cb 100644
--- a/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
+++ b/docs/known-issues/pt/automatic-translation-of-urls-not-occurring-due-to-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 1062858
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o aplicativo `admin-catalog-translations` para traduzir automaticamente o conteúdo do catálogo, o linkId pode ter problemas para ser traduzido quando tiver caracteres especiais, como `ç`. O `admin-catalog-translations` usa o `messages app` para fazer as traduções e algumas palavras podem não ser traduzidas corretamente devido a esses caracteres.
diff --git a/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md b/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
index 3fdfce2e1..7e4682cee 100644
--- a/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
+++ b/docs/known-issues/pt/availability-field-is-incorrect-in-fulfillment-simulation-for-no-stock-or-price-products.md
@@ -18,9 +18,7 @@ internalReference: 773537
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um produto está fora de estoque ou não tem preço, a simulação de atendimento informa incorretamente o campo `disponibilidade` como `disponível`.
diff --git a/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md b/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
index c69ac1d36..64e96e7ba 100644
--- a/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
+++ b/docs/known-issues/pt/available-addresses-list-on-checkout-ui-missing-data-for-newly-created-address.md
@@ -18,9 +18,7 @@ internalReference: 1061630
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário adiciona um novo endereço durante a etapa de envio do Checkout, avança para a etapa de pagamento e, em seguida, retorna à lista de endereços disponíveis da etapa de envio, esse endereço recém-criado pode estar ausente da lista ou exibir informações incompletas na interface do usuário.
diff --git a/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md b/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
index 5ca4316fd..de6757ea5 100644
--- a/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
+++ b/docs/known-issues/pt/availablequantity-value-inconsistent-due-to-the-large-number-of-routes-created-to-deliver-the-item.md
@@ -18,9 +18,7 @@ internalReference: 1034211
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Durante o pipeline de indexação de um item, é realizada uma simulação sem o uso de um código postal para validar a disponibilidade, essa simulação, quando chega ao sistema de logística, realiza uma validação combinando todas as docas, armazéns e políticas de remessa disponíveis para um canal de vendas, a resposta a esse cálculo determina a disponibilidade do item, porém essa resposta tem um limite de leitura de 10.000 rotas, portanto, quando um cálculo resulta em mais de 10.000, as rotas restantes são desconsideradas, o que pode fazer com que o sistema retorne uma resposta inconsistente.
diff --git a/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md b/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md
index ee35771e4..a5f1246a3 100644
--- a/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md
+++ b/docs/known-issues/pt/b2b-impersonated-data-is-not-removed-after-logging-out.md
@@ -18,9 +18,7 @@ internalReference: 1067969
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O logout após a representação de um usuário no B2B Suite não remove as permissões de vitrine da sessão.
diff --git a/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md b/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md
index 62e1024fe..fe8a2e14c 100644
--- a/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md
+++ b/docs/known-issues/pt/b2b-orders-history-doesnt-work-in-the-website-domain.md
@@ -18,9 +18,7 @@ internalReference: 849394
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O histórico de pedidos B2B não funciona no domínio do site, mostrando a mensagem "Você não tem permissão para acessar isso".
diff --git a/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md b/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
index 2b2a885a9..f51592fe7 100644
--- a/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
+++ b/docs/known-issues/pt/b2b-organization-dont-consider-accounts-using-geolocation-when-registering-address.md
@@ -18,9 +18,7 @@ internalReference: 904907
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A organização B2B não tem nada para configurar um endereço quando as contas usam geolocalização, fazendo com que os itens fiquem indisponíveis.
diff --git a/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md b/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
index 0b4a318a3..de28432ad 100644
--- a/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
+++ b/docs/known-issues/pt/b2b-organizations-detail-ui-only-shows-100-first-sellers.md
@@ -18,9 +18,7 @@ internalReference: 966450
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface de usuário de detalhes das organizações B2B mostra apenas os 100 primeiros vendedores; a interface de usuário não tem paginação, tornando impossível selecionar um vendedor se não estiver na primeira página
diff --git a/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md b/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
index 3ee780f0a..2b336cd8c 100644
--- a/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
+++ b/docs/known-issues/pt/b2b-organizations-impersonate-feature-doesnt-register-information-in-orders.md
@@ -18,9 +18,7 @@ internalReference: 1056736
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As organizações B2B têm um recurso nativo para se passar por outros membros da organização ou do centro de custo.
diff --git a/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md b/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
index 99bb939a3..0d5cfe395 100644
--- a/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
+++ b/docs/known-issues/pt/b2b-quotes-doesnt-apply-discount-at-checkout-in-the-website-domain.md
@@ -18,9 +18,7 @@ internalReference: 849080
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma cotação tem um desconto aplicado por um vendedor, o B2B Quotes não aplica o desconto no checkout no domínio do site.
diff --git a/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md b/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
index bbc6997ce..eee7bd660 100644
--- a/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
+++ b/docs/known-issues/pt/b2b-suite-dont-use-geocoordinates-to-calculate-region-id.md
@@ -18,9 +18,7 @@ internalReference: 1055033
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 É possível usar taxas de remessa usando códigos postais ou coordenadas geográficas, mas as organizações B2B usam somente códigos postais para calcular IDs de região. Se uma conta tiver geolocalização (polígonos) registrada em suas taxas de envio, os produtos serão mostrados como indisponíveis na vitrine.
diff --git a/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md b/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
index 46d957a4d..962748d0a 100644
--- a/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
+++ b/docs/known-issues/pt/b2w-b2w-direct-order-fob-integrating-with-carrier.md
@@ -18,9 +18,7 @@ internalReference: 714879
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns pedidos da "b2wentregadirect" que devem entrar como (FOB), mas estão sendo integrados com o frete calculado aqui do nosso lado.
diff --git a/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md b/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md
index 7f452b72b..23a60934b 100644
--- a/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md
+++ b/docs/known-issues/pt/b2w-freight-value-in-oms-vtex.md
@@ -18,9 +18,7 @@ internalReference: 671748
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Estamos tendo alguns casos em que o valor do frete não é mostrado dentro dos detalhes das transações de pagamento - OMS
diff --git a/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md b/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md
index de4c5e989..6d30a450e 100644
--- a/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md
+++ b/docs/known-issues/pt/b2w-order-with-parameter-count-mismatch-error.md
@@ -18,9 +18,7 @@ internalReference: 776361
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas ordens da Skyhub não estão sendo integradas na plataforma, devido ao erro "Parameter count mismatch", onde a ordem não é criada em OMS (VTEX)
diff --git a/docs/known-issues/pt/b2w-tracking-status-not-updated-on-skyhub.md b/docs/known-issues/pt/b2w-tracking-status-not-updated-on-skyhub.md
index 8454ae93d..8137c5509 100644
--- a/docs/known-issues/pt/b2w-tracking-status-not-updated-on-skyhub.md
+++ b/docs/known-issues/pt/b2w-tracking-status-not-updated-on-skyhub.md
@@ -18,9 +18,7 @@ internalReference: 673597
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md b/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md
index 63404b0ff..907ae25cd 100644
--- a/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md
+++ b/docs/known-issues/pt/back-button-is-not-rendered-in-my-organization.md
@@ -18,9 +18,7 @@ internalReference: 797003
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O botão "Voltar" não é renderizado em Minha organização em celulares, impedindo que o comprador acesse outras opções em Minha conta.
diff --git a/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md b/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
index 54ec41d6f..f30f9db63 100644
--- a/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
+++ b/docs/known-issues/pt/back-to-site-button-takes-to-gatewaycallbacksuccess-instead-of-placeorder-page.md
@@ -18,9 +18,7 @@ internalReference: 786685
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cliente fecha uma compra utilizando um cartão presente e o aplicativo de pagamento MercadoPago, o botão "return to the site" não os leva à página de pedido do local, mas sim à página de pedido "/gatewayCallback//Success".
diff --git a/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md b/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
index 31c7277d3..e54a83db8 100644
--- a/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
+++ b/docs/known-issues/pt/bad-request-when-searching-terms-with-directly-via-url.md
@@ -18,9 +18,7 @@ internalReference: 775524
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar um termo com "%" diretamente via URL, a página retorna uma solicitação 400 Bad Request.
diff --git a/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md b/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
index dee5b61b2..f73da3c49 100644
--- a/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
+++ b/docs/known-issues/pt/bad-request-when-searching-terms-with-through-autocomplete.md
@@ -18,9 +18,7 @@ internalReference: 978136
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar um termo com "#" diretamente por meio do preenchimento automático, a página nunca é carregada
diff --git a/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md b/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
index 595c2e7d2..bfbc3a097 100644
--- a/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
+++ b/docs/known-issues/pt/bad-request-when-trying-to-access-an-inventory-with-a-huge-quantity-of-reserved-items.md
@@ -18,9 +18,7 @@ internalReference: 296066
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md b/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
index 09ba8021b..50773d743 100644
--- a/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
+++ b/docs/known-issues/pt/badly-formatted-text-for-search-titles-and-breadcrumbs-in-specific-scenarios-with-merchandising-rules.md
@@ -18,9 +18,7 @@ internalReference: 999476
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas páginas de resultados de pesquisa ocultam os filtros aplicados - já que eles já fazem parte da própria página, portanto, são definidos como "initialAttributes" - para se concentrar nos filtros adicionais que podem ser aplicados. Nesses cenários, os valores do título da página e dos breadcrumbs são basicamente definidos pelo primeiro produto da página.
diff --git a/docs/known-issues/pt/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md b/docs/known-issues/pt/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md
index c7bae6d83..1c1474207 100644
--- a/docs/known-issues/pt/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md
+++ b/docs/known-issues/pt/banner-not-respecting-the-specificity-of-the-search-level-in-search-pages.md
@@ -18,9 +18,7 @@ internalReference: 566809
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/banner-scheduling-is-deactivated-after-expiry-date.md b/docs/known-issues/pt/banner-scheduling-is-deactivated-after-expiry-date.md
index 757f0335a..286d7058a 100644
--- a/docs/known-issues/pt/banner-scheduling-is-deactivated-after-expiry-date.md
+++ b/docs/known-issues/pt/banner-scheduling-is-deactivated-after-expiry-date.md
@@ -18,19 +18,13 @@ internalReference: 301023
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md b/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
index 843c79452..8c6e613d2 100644
--- a/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
+++ b/docs/known-issues/pt/benefitsitems-array-inside-of-productcontextprovider-shuffle-items-when-the-promotion-is-a-buy-together-type.md
@@ -18,9 +18,7 @@ internalReference: 915213
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao examinar a matriz de benefícios dentro do ProductContextProvider no PDP de um produto, podemos ver que nem todos os produtos são retornados e os que são retornados são embaralhados. As duas listas de produtos dentro da promoção estão juntas na mesma matriz. Isso só acontece quando a promoção é do tipo Buy Together.
diff --git a/docs/known-issues/pt/bin-sent-does-not-match-an-associated-card-brand.md b/docs/known-issues/pt/bin-sent-does-not-match-an-associated-card-brand.md
index 0dcab525d..989824e66 100644
--- a/docs/known-issues/pt/bin-sent-does-not-match-an-associated-card-brand.md
+++ b/docs/known-issues/pt/bin-sent-does-not-match-an-associated-card-brand.md
@@ -18,9 +18,7 @@ internalReference: 308896
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A plataforma permite que você envie um BIN com outra bandeira de marca de cartão. Por exemplo, o BIN: Um BIN VISA pode ser informado, mas você pode marcar a bandeira de marca do cartão Mastercard.
diff --git a/docs/known-issues/pt/block-selector-not-working-at-site-editor-home-page.md b/docs/known-issues/pt/block-selector-not-working-at-site-editor-home-page.md
index d9405c178..e1dd221f3 100644
--- a/docs/known-issues/pt/block-selector-not-working-at-site-editor-home-page.md
+++ b/docs/known-issues/pt/block-selector-not-working-at-site-editor-home-page.md
@@ -18,9 +18,7 @@ internalReference: 431941
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao acessar o Site Editor, o seletor de blocos não funciona imediatamente.
diff --git a/docs/known-issues/pt/bmail-problems-with-filaumbro.md b/docs/known-issues/pt/bmail-problems-with-filaumbro.md
index 457bd7257..f33a9bc78 100644
--- a/docs/known-issues/pt/bmail-problems-with-filaumbro.md
+++ b/docs/known-issues/pt/bmail-problems-with-filaumbro.md
@@ -18,9 +18,7 @@ internalReference: 392798
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md b/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md
index 687691efb..c35f8d693 100644
--- a/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md
+++ b/docs/known-issues/pt/boolean-filter-on-form-application-does-not-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 918537
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um filtro booleano é selecionado, a seguinte mensagem é retornada:
diff --git a/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md b/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
index b882ecf9e..7074726bb 100644
--- a/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
+++ b/docs/known-issues/pt/boolean-videoaudio-html-properties-not-being-validated-on-legacy-cms.md
@@ -18,9 +18,7 @@ internalReference: 491898
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/brand-filter-export-selecting-fewer-skus-than-expected.md b/docs/known-issues/pt/brand-filter-export-selecting-fewer-skus-than-expected.md
index 6bd0ab6b9..3f40e2689 100644
--- a/docs/known-issues/pt/brand-filter-export-selecting-fewer-skus-than-expected.md
+++ b/docs/known-issues/pt/brand-filter-export-selecting-fewer-skus-than-expected.md
@@ -18,9 +18,7 @@ internalReference: 597038
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md b/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
index 878e3acf4..0d1aafae7 100644
--- a/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
+++ b/docs/known-issues/pt/brands-with-some-special-characters-are-not-searchable-on-the-brand-admin.md
@@ -18,9 +18,7 @@ internalReference: 503496
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface do usuário da marca, `.myvtex.com/admin/Site/Marca.aspx`, não permite que os usuários pesquisem marcas com alguns caracteres especiais no nome, como apóstrofos `'`. Além disso, letras de alfabetos não latinos também não podem ser pesquisadas, por exemplo, do alfabeto polonês, como `Ż`.
diff --git a/docs/known-issues/pt/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md b/docs/known-issues/pt/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md
index 6a6613203..ab56816d3 100644
--- a/docs/known-issues/pt/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md
+++ b/docs/known-issues/pt/braspag-error-when-capturing-or-canceling-due-to-an-error-with-code-bp901.md
@@ -18,9 +18,7 @@ internalReference: 490428
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas transações retornam uma falha de comunicação ou integração entre a Braspag e a aquisição, em outras palavras, um erro de timeout. O código de erro para este comportamento é BP901.
diff --git a/docs/known-issues/pt/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md b/docs/known-issues/pt/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md
index 73bf1173e..2d17835ea 100644
--- a/docs/known-issues/pt/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md
+++ b/docs/known-issues/pt/breadcrumb-not-being-read-by-crawlers-due-ssr-timeout.md
@@ -18,9 +18,7 @@ internalReference: 460999
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao carregar pela primeira vez o pão ralado, os dados da lista de categorias estão ficando mais rápidos do que os da árvore de categorias enviada pela consulta de facetas, isto está causando um comportamento inesperado no tempo de carga do pão ralado, porque a lista de categorias traz também categorias similares de produtos similares e não tem todas as informações necessárias para a json+ld.
diff --git a/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md b/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
index 89b4655f6..242f43c60 100644
--- a/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
+++ b/docs/known-issues/pt/broadcaster-not-notifying-all-the-stock-changes-to-the-intelligent-search-module.md
@@ -18,9 +18,7 @@ internalReference: 683345
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md b/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md
index b10e2be9e..b2e66548b 100644
--- a/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md
+++ b/docs/known-issues/pt/buscacep-not-working-in-create-giftlist-form.md
@@ -18,9 +18,7 @@ internalReference: 342418
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md b/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
index 606f4e42b..7d3b097d0 100644
--- a/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
+++ b/docs/known-issues/pt/button-cancel-inside-the-mycards-page-not-translated-to-spanish.md
@@ -18,9 +18,7 @@ internalReference: 431200
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para contas espanholas podemos ver o botão "cancelar" na página MyCards, mas deve ter escrito "cancelar", já que o site está em espanhol. Os outros botões e mensagens já estão em espanhol.
diff --git a/docs/known-issues/pt/button-to-see-more-pickup-points-not-being-presented-in-the-list.md b/docs/known-issues/pt/button-to-see-more-pickup-points-not-being-presented-in-the-list.md
index e2ef97f5d..f5515ccbd 100644
--- a/docs/known-issues/pt/button-to-see-more-pickup-points-not-being-presented-in-the-list.md
+++ b/docs/known-issues/pt/button-to-see-more-pickup-points-not-being-presented-in-the-list.md
@@ -18,9 +18,7 @@ internalReference: 685650
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O botão "ver mais" na lista de pontos de coleta pode não aparecer, ocultando algumas opções que são apresentadas no mapa.
diff --git a/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md b/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
index 5734378c1..893b0f103 100644
--- a/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
+++ b/docs/known-issues/pt/buttons-may-not-work-on-the-first-try-in-fullcleanup-admin.md
@@ -18,9 +18,7 @@ internalReference: 790828
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No administrador do Fullcleanup, espera-se que os botões ajam na primeira tentativa. No entanto, para executar a ação, pode ser necessário clicar no botão várias vezes.
diff --git a/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md b/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
index d68f75cba..b725f8147 100644
--- a/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
+++ b/docs/known-issues/pt/buy-together-promotion-with-lots-of-skus-may-let-the-eligible-products-not-to-load-on-the-front-timeout.md
@@ -18,9 +18,7 @@ internalReference: 301463
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A promoção Buy Together com muitos SKUs pode fazer com que os produtos qualificados não sejam carregados na frente devido ao tempo limite. As páginas de produto usam o controle de produto `<vtex.cmc:BuyTogether/>`. Esse controle é responsável por trazer informações de todos os SKUs qualificados definidos na promoção para a página do produto.
diff --git a/docs/known-issues/pt/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md b/docs/known-issues/pt/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md
index 2016882dc..bee7cd203 100644
--- a/docs/known-issues/pt/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md
+++ b/docs/known-issues/pt/buy-together-promotions-with-price-range-restriction-impact-in-gift-promotions.md
@@ -18,9 +18,7 @@ internalReference: 676382
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md b/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
index 0dd3fc320..d5cd44c86 100644
--- a/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
+++ b/docs/known-issues/pt/buyers-cant-login-if-there-is-misconfiguration-in-organizationscost-centers.md
@@ -18,9 +18,7 @@ internalReference: 945609
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário tem a primeira organização atribuída a ele inválida com o ID do centro de custo errado, o login falha sem nenhuma mensagem.
diff --git a/docs/known-issues/pt/cabals-regex-update.md b/docs/known-issues/pt/cabals-regex-update.md
index 719ebb913..df4a643ec 100644
--- a/docs/known-issues/pt/cabals-regex-update.md
+++ b/docs/known-issues/pt/cabals-regex-update.md
@@ -18,9 +18,7 @@ internalReference: 374652
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md b/docs/known-issues/pt/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md
index aa7498e63..f9ae5e0d9 100644
--- a/docs/known-issues/pt/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md
+++ b/docs/known-issues/pt/cache-layer-of-5-minutes-when-creating-or-deleting-merchandising-rules.md
@@ -18,9 +18,7 @@ internalReference: 841197
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar regras de merchandising visual ou excluir qualquer regra de merchandising, há um cache de 5 minutos para ficar disponível visualmente no admin.
diff --git a/docs/known-issues/pt/calculated-price-table-export-not-bringing-all-skus.md b/docs/known-issues/pt/calculated-price-table-export-not-bringing-all-skus.md
index 495eab44d..eee276741 100644
--- a/docs/known-issues/pt/calculated-price-table-export-not-bringing-all-skus.md
+++ b/docs/known-issues/pt/calculated-price-table-export-not-bringing-all-skus.md
@@ -18,9 +18,7 @@ internalReference: 722005
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/calculation-issue-in-comissionamount.md b/docs/known-issues/pt/calculation-issue-in-comissionamount.md
index 883c193a3..0c1651bb6 100644
--- a/docs/known-issues/pt/calculation-issue-in-comissionamount.md
+++ b/docs/known-issues/pt/calculation-issue-in-comissionamount.md
@@ -18,9 +18,7 @@ internalReference: 1001005
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Isso ocorre em um cenário específico de divisão de pagamento com vários pagamentos e vendedores (em que ambos são responsáveis por encargos de processamento de pagamento e estornos). A soma do `comissionAmount` dos vendedores não é igual ao `amount` do marketplace (problema de arredondamento), essa diferença pode causar uma recusa de liquidação pelo adquirente.
diff --git a/docs/known-issues/pt/calendar-in-english-for-stores-in-spanish.md b/docs/known-issues/pt/calendar-in-english-for-stores-in-spanish.md
index d7abe4622..7ddc5eb2f 100644
--- a/docs/known-issues/pt/calendar-in-english-for-stores-in-spanish.md
+++ b/docs/known-issues/pt/calendar-in-english-for-stores-in-spanish.md
@@ -18,9 +18,7 @@ internalReference: 412426
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md b/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
index 927e08986..5b32fb19f 100644
--- a/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
+++ b/docs/known-issues/pt/call-center-operators-email-is-sent-to-orderform-when-adding-items-to-cart-from-store-framework-frontend.md
@@ -18,9 +18,7 @@ internalReference: 1066571
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar os componentes do Store Framework para adicionar itens a um carrinho enquanto estiver conectado como um operador de call center e não estiver se passando por um cliente, o e-mail do operador é preenchido no anexo clientProfileData do formulário de pedido.
diff --git a/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md b/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
index 0c9ee9a43..961c95a2a 100644
--- a/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
+++ b/docs/known-issues/pt/callbacks-after-approval-may-trigger-paymentauthorizationworker-to-retry-payment-which-may-also-deny-it.md
@@ -18,9 +18,7 @@ internalReference: 740499
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o provedor envia um retorno de chamada logo após a autorização, ele pode acionar uma nova tentativa de autorização. Portanto, em alguns casos, quando a transação tiver mais de um pagamento e um deles for um cartão-presente, uma nova tentativa de autorização poderá cancelar a transação quando ela não tiver fundos.
diff --git a/docs/known-issues/pt/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md b/docs/known-issues/pt/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md
index 394b2a515..b3d6813ef 100644
--- a/docs/known-issues/pt/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md
+++ b/docs/known-issues/pt/callbackurl-always-returns-403-when-the-connector-owner-account-has-been-disabled.md
@@ -18,9 +18,7 @@ internalReference: 775235
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para conectores utilizando nosso PPP, a configuração do conector inclui um campo chamado `accountName` que especifica a conta utilizada para publicar o aplicativo. Normalmente, o valor `accountName` é o mesmo que o nome da conta do parceiro. Entretanto, quando o parceiro publica conectores com sua infra-estrutura, ele utiliza um ponto final específico, que não é relativo; é assim que os conectores que utilizam nossa infra-estrutura IO fazem.
diff --git a/docs/known-issues/pt/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md b/docs/known-issues/pt/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md
index 3141a1180..7a99f1354 100644
--- a/docs/known-issues/pt/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md
+++ b/docs/known-issues/pt/callcenter-users-cant-delete-a-customers-credit-card-via-my-account.md
@@ -18,19 +18,13 @@ internalReference: 294001
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/campaign-audience-doesnt-save-coupon-information.md b/docs/known-issues/pt/campaign-audience-doesnt-save-coupon-information.md
index 0206a8abf..077105ca9 100644
--- a/docs/known-issues/pt/campaign-audience-doesnt-save-coupon-information.md
+++ b/docs/known-issues/pt/campaign-audience-doesnt-save-coupon-information.md
@@ -18,9 +18,7 @@ internalReference: 521601
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O público da campanha não guarda informações sobre cupons
diff --git a/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md b/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
index b9d9e63f7..4f5ad85de 100644
--- a/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
+++ b/docs/known-issues/pt/campaign-audience-ui-changing-different-from-to-equal-to-with-a-collection.md
@@ -18,9 +18,7 @@ internalReference: 881131
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md b/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md
index 9dfc4c127..84864d405 100644
--- a/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md
+++ b/docs/known-issues/pt/campovalorformaspx-save-button-requires-two-clicks.md
@@ -18,9 +18,7 @@ internalReference: 525616
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md b/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md
index 281463dc3..c2e70d02b 100644
--- a/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md
+++ b/docs/known-issues/pt/canonical-tags-are-not-applied-after-3rd-category-level.md
@@ -18,9 +18,7 @@ internalReference: 932349
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As tags canônicas não são aplicadas após o terceiro nível de categoria quando há uma árvore de categorias com mais de três níveis (departamento, categoria e subcategoria), os outros níveis acima não são exibidos na canônica
diff --git a/docs/known-issues/pt/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md b/docs/known-issues/pt/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md
index b77b476f3..34dade83a 100644
--- a/docs/known-issues/pt/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md
+++ b/docs/known-issues/pt/cant-create-orders-with-promotions-applied-on-the-marketplace-layer-to-a-seller-under-the-multilevel-behavior.md
@@ -18,9 +18,7 @@ internalReference: 446938
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Não é possível concluir compras onde o mercado está aplicando promoções a itens de vendedores que estão sob comportamento multinível. O cliente verá uma mensagem de erro genérica.
diff --git a/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md b/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md
index f31cccf3c..7c78c25bf 100644
--- a/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md
+++ b/docs/known-issues/pt/cant-edit-the-name-of-the-styles-template.md
@@ -18,9 +18,7 @@ internalReference: 882147
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Depois de criar um novo estilo no módulo Styles, não é possível editar seu nome.
diff --git a/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md b/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md
index f9f26fac7..54e77c853 100644
--- a/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md
+++ b/docs/known-issues/pt/card-brands-incorrectly-processed-as-visa.md
@@ -18,9 +18,7 @@ internalReference: 1024823
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns cartões de crédito podem ser processados como Visa quando, na verdade, são de outra marca.
diff --git a/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md b/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md
index b21fd443c..585dc44ca 100644
--- a/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md
+++ b/docs/known-issues/pt/card-facebook-doesnt-save-some-settings.md
@@ -18,9 +18,7 @@ internalReference: 548763
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O facebook do cartão não salva algumas configurações.
diff --git a/docs/known-issues/pt/cardholderdocument-is-not-sent-to-antifraud.md b/docs/known-issues/pt/cardholderdocument-is-not-sent-to-antifraud.md
index 536804064..ca78fede8 100644
--- a/docs/known-issues/pt/cardholderdocument-is-not-sent-to-antifraud.md
+++ b/docs/known-issues/pt/cardholderdocument-is-not-sent-to-antifraud.md
@@ -18,9 +18,7 @@ internalReference: 829864
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
index 06ad0d1ab..7a5ffd7b7 100644
--- a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
+++ b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-assembly-options.md
@@ -18,9 +18,7 @@ internalReference: 1020278
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar um carrinho a partir de um pedido antigo (botão "Pedir novamente" na tela "Meus pedidos"), as opções de montagem do pedido original não serão mantidas.
diff --git a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
index e23a283fd..caf65f778 100644
--- a/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
+++ b/docs/known-issues/pt/cart-created-from-an-old-order-doesnt-bring-the-attachments.md
@@ -18,9 +18,7 @@ internalReference: 802464
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar um carrinho a partir de um pedido antigo (botão "Pedir novamente" na tela "Meus pedidos"), os anexos e serviços do pedido original não serão mantidos.
diff --git a/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md b/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
index 3b68dfbf9..066b6faf0 100644
--- a/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
+++ b/docs/known-issues/pt/cart-created-from-an-order-again-option-in-my-orders-the-customers-email-is-not-being-placed-as-expected-in-the-orderform.md
@@ -18,9 +18,7 @@ internalReference: 947563
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md b/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
index 3faa256ef..6103b8813 100644
--- a/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
+++ b/docs/known-issues/pt/cart-itemdeliverytype-is-missing-sent-by-checkout-in-additionaldata.md
@@ -18,9 +18,7 @@ internalReference: 1002115
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há uma divisão de quantidade na `priceDefinition` devido ao arredondamento do multiplicador de unidades, o gateway não pode receber nenhum valor para `deliveryType` no objeto do carrinho. Portanto, isso pode fazer com que o provedor de pagamento negue o pagamento se ele usar esse campo...
diff --git a/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md b/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md
index 2c01f9a87..37863eca7 100644
--- a/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md
+++ b/docs/known-issues/pt/cart-itens-are-kept-in-orders-with-total-value-zero.md
@@ -18,9 +18,7 @@ internalReference: 1054999
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Sempre que um carrinho tiver um valor total de "0", nenhuma transação será criada ao finalizar um pedido.  Ao concluir um pedido por meio da interface do usuário do checkout, não ocorre nenhuma solicitação de processamento de pedido, portanto, os itens e os dados do carrinho são mantidos e o comprador pode criar um pedido com o mesmo carrinho novamente.
diff --git a/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md b/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
index 839a71d63..f3acd887b 100644
--- a/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
+++ b/docs/known-issues/pt/cart-with-items-displays-empty-cart-message-while-screen-is-still-loading.md
@@ -18,9 +18,7 @@ internalReference: 303673
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Enquanto a tela do carrinho está carregando, eventualmente, uma mensagem de "carrinho vazio" aparece antes dos itens. Este cenário pode acontecer rapidamente, com menos de milissegundos, e tornar-se imperceptível, ou possivelmente mais lentamente, durando até um segundo ou até mais e gerando consultas por parte das lojas.
diff --git a/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md b/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
index 3d5643b6f..2493ac6f4 100644
--- a/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
+++ b/docs/known-issues/pt/cart-with-multiple-country-addresses-lose-the-pickup-address-if-store-cant-ship-to-all-the-countries.md
@@ -18,9 +18,7 @@ internalReference: 1068197
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se um comprador tiver vários endereços em seu perfil de diferentes países e a loja não fizer entregas em nenhum desses endereços, ao selecionar a retirada em um endereço válido e passar para a etapa de pagamento, a interface do usuário do checkout redirecionará o comprador de volta para a etapa de envio.
diff --git a/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md b/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
index 6a065b931..c060b49bf 100644
--- a/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
+++ b/docs/known-issues/pt/carts-created-from-order-replacement-do-not-receive-promotions-correctly.md
@@ -18,9 +18,7 @@ internalReference: 473424
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os carrinhos criados a partir de pedidos existentes por meio da funcionalidade "substituir pedidos" apresentada na página "meus pedidos" estão restritos à promoção original, mas sem considerar que a mesma promoção pode se aplicar a diferentes contextos, como diferentes métodos de pagamento ou opções de envio.
diff --git a/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md b/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md
index c02a1c158..736a1846d 100644
--- a/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md
+++ b/docs/known-issues/pt/cashback-promotions-do-not-consider-items-removed-from-orders.md
@@ -18,9 +18,7 @@ internalReference: 1019864
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, ao usar promoções de cashback, os cálculos são totalmente realizados no momento em que os itens são inseridos no carrinho.
diff --git a/docs/known-issues/pt/catalog-access-profile-gives-access-to-the-gift-card-module.md b/docs/known-issues/pt/catalog-access-profile-gives-access-to-the-gift-card-module.md
index b7d741009..f4936b12f 100644
--- a/docs/known-issues/pt/catalog-access-profile-gives-access-to-the-gift-card-module.md
+++ b/docs/known-issues/pt/catalog-access-profile-gives-access-to-the-gift-card-module.md
@@ -18,9 +18,7 @@ internalReference: 362165
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O acesso ao módulo de catálogo também dá acesso ao módulo de cartões-presente através da interface de usuário.
diff --git a/docs/known-issues/pt/catalog-api-create-sku-file-only-work-with-an-url.md b/docs/known-issues/pt/catalog-api-create-sku-file-only-work-with-an-url.md
index 4bc2d799a..9b3ac05fc 100644
--- a/docs/known-issues/pt/catalog-api-create-sku-file-only-work-with-an-url.md
+++ b/docs/known-issues/pt/catalog-api-create-sku-file-only-work-with-an-url.md
@@ -18,9 +18,7 @@ internalReference: 503153
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Catálogo API Criar arquivo SKU só funciona com a Opção 1 ( envie uma imagem através de URL)
diff --git a/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md b/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
index 53d50e4a6..73c6ffb86 100644
--- a/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
+++ b/docs/known-issues/pt/catalog-api-doesnt-respond-properly-to-space-at-the-end-of-strings.md
@@ -18,9 +18,7 @@ internalReference: 977033
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar a coleção de APIs de catálogo, se um campo JSON de cadeia de caracteres for enviado terminando com espaços (por exemplo, productName: "myProductName"), as APIs de catálogo responderão com uma resposta 400 imprópria e um corpo de resposta vazio, deixando o usuário sem saber o que foi enviado de forma imprópria.
diff --git a/docs/known-issues/pt/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md b/docs/known-issues/pt/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md
index 5f3431fe2..f0220fc9a 100644
--- a/docs/known-issues/pt/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md
+++ b/docs/known-issues/pt/catalog-brand-api-rest-allows-the-client-to-break-the-information-if-sending-request-with-wrong-values.md
@@ -18,9 +18,7 @@ internalReference: 269109
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há muitas rotas que suportam algum tipo de valor, mas se o cliente usar outro tipo de valor (por exemplo, inserir nulo em vez de booleano) pode quebrar a interface do produto / SKU / categoria / marca. Negar ao cliente a atualização das informações por meio do administrador.
diff --git a/docs/known-issues/pt/catalog-database-registers-skus-with-duplicate-specifications.md b/docs/known-issues/pt/catalog-database-registers-skus-with-duplicate-specifications.md
index f77da3e8a..cf8e4ed8c 100644
--- a/docs/known-issues/pt/catalog-database-registers-skus-with-duplicate-specifications.md
+++ b/docs/known-issues/pt/catalog-database-registers-skus-with-duplicate-specifications.md
@@ -18,9 +18,7 @@ internalReference: 536133
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em algumas situações aleatórias, o banco de dados do catálogo permite que os valores de uma especificação sejam duplicados na mesma SKU.
diff --git a/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md b/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md
index 6877ce106..7334c437a 100644
--- a/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md
+++ b/docs/known-issues/pt/catalog-export-cannot-handle-t-and-s-characters.md
@@ -18,9 +18,7 @@ internalReference: 950933
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o catálogo de importação/exportação corta os caracteres especiais ț e ș ao exportar dados.
diff --git a/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md b/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
index 6c3a837f3..b760d149c 100644
--- a/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
+++ b/docs/known-issues/pt/catalog-export-does-not-show-sales-channels-when-none-are-tagged.md
@@ -18,9 +18,7 @@ internalReference: 722001
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, os canais de venda a serem verificados na IU do produto têm uma lógica de "se nenhum for verificado, todos eles estão disponíveis".
diff --git a/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md b/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md
index cfd018dfd..52a6062a3 100644
--- a/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md
+++ b/docs/known-issues/pt/catalog-export-for-attachment-cuts-50-characters.md
@@ -18,9 +18,7 @@ internalReference: 953161
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao importar dados para anexos no módulo de catálogo, se o referido anexo tiver mais de 50 caracteres, a cadeia de caracteres é cortada, o que faz com que não haja atualizações para esses dados.
diff --git a/docs/known-issues/pt/catalog-filter-for-seller-1-brings-empty-results.md b/docs/known-issues/pt/catalog-filter-for-seller-1-brings-empty-results.md
index 1237fb2b7..75756407f 100644
--- a/docs/known-issues/pt/catalog-filter-for-seller-1-brings-empty-results.md
+++ b/docs/known-issues/pt/catalog-filter-for-seller-1-brings-empty-results.md
@@ -18,9 +18,7 @@ internalReference: 801538
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, ao filtrar exclusivamente o vendedor principal nos menus do Catálogo, nenhum resultado é exibido. Isso acontece porque esse filtro está procurando incorretamente por um vendedor específico quando, em vez disso, o vendedor = 1 (o vendedor principal da conta) é o próprio marketplace.
diff --git a/docs/known-issues/pt/catalog-filters-timeout.md b/docs/known-issues/pt/catalog-filters-timeout.md
index d612fa3cc..d9535c03c 100644
--- a/docs/known-issues/pt/catalog-filters-timeout.md
+++ b/docs/known-issues/pt/catalog-filters-timeout.md
@@ -18,9 +18,7 @@ internalReference: 922350
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para lojas com uma grande quantidade de skus (1 milhão ou mais), muitas vezes, ao filtrar usando os filtros da interface do usuário do catálogo, seja para o menu principal ou para a seção de relatórios, se a consulta de filtro retornar um resultado muito grande, a interface do usuário não funcionará mais (504 gateway timeout)
diff --git a/docs/known-issues/pt/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md b/docs/known-issues/pt/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md
index c9004d470..8ba62be9e 100644
--- a/docs/known-issues/pt/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md
+++ b/docs/known-issues/pt/catalog-fullcleanup-does-not-trigger-a-new-intelligent-search-indexation.md
@@ -18,9 +18,7 @@ internalReference: 449763
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao executar uma limpeza completa (https://{AccountName}.myvtex.com/admin/Site/fullcleanup.aspx) no catálogo, a emissora não envia a notificação de atualização para o indexador de Busca Inteligente, e os dados do produto podem ficar desatualizados, causando discrepâncias entre o conteúdo PDP e PLP.
diff --git a/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md b/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md
index 1f11ce315..02271726c 100644
--- a/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md
+++ b/docs/known-issues/pt/catalog-graphql-categoryinputtranslation-not-working.md
@@ -18,9 +18,7 @@ internalReference: 1024172
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o método CategoryInputTranslation, para o catálogo graphQL, não está gerando uma atualização nos dados traduzidos para as contas.
diff --git a/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md b/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md
index 36e36c50e..ed466208a 100644
--- a/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md
+++ b/docs/known-issues/pt/catalog-indexer-generating-invalid-translation-documents.md
@@ -18,9 +18,7 @@ internalReference: 991494
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao indexar um produto com informações traduzidas, as mensagens do aplicativo são solicitadas. Essas solicitações devem ter menos de 3s e, quando demoram mais do que isso, a indexação falha e gera um documento de tradução inválido.
diff --git a/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md b/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
index 2709ad53a..181844d46 100644
--- a/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
+++ b/docs/known-issues/pt/catalog-indexing-report-total-section-calculation-error.md
@@ -18,9 +18,7 @@ internalReference: 499450
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, no relatório de indexação do catálogo (RelatorioIndexação.aspx), a seção "Total Indexado" está considerando todos os produtos do catálogo ao atingir 100% da métrica, não subtraindo produtos não indexados se necessário.
diff --git a/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md b/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md
index b0ec7b32e..ff67f0dc9 100644
--- a/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md
+++ b/docs/known-issues/pt/catalog-integration-xml-fiscal-code-field-not-rendering.md
@@ -18,9 +18,7 @@ internalReference: 1031109
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a configuração XML do catálogo para o campo de código fiscal não está gerando os resultados esperados, pois sempre retorna um <![CDATA[]]>
diff --git a/docs/known-issues/pt/catalog-mapping-ui-taking-too-much-time-to-load.md b/docs/known-issues/pt/catalog-mapping-ui-taking-too-much-time-to-load.md
index 043da1e9f..21cac7f21 100644
--- a/docs/known-issues/pt/catalog-mapping-ui-taking-too-much-time-to-load.md
+++ b/docs/known-issues/pt/catalog-mapping-ui-taking-too-much-time-to-load.md
@@ -18,9 +18,7 @@ internalReference: 823218
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o marketplace tem muitos vendedores e usa as planilhas de mapeamento para a maioria deles, a UI de mapeamento de catálogo pode ser muito pesada e, cada vez que o comerciante tenta acessá-la, leva muito tempo para carregar.
diff --git a/docs/known-issues/pt/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md b/docs/known-issues/pt/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md
index 5104bafda..376842504 100644
--- a/docs/known-issues/pt/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md
+++ b/docs/known-issues/pt/catalog-myvtex-iframe-html-select-breaking-for-chrome-108.md
@@ -18,9 +18,7 @@ internalReference: 711637
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md b/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md
index 8eed2ab14..e0d1b0f7f 100644
--- a/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md
+++ b/docs/known-issues/pt/catalog-search-api-limited-to-2500-results.md
@@ -18,9 +18,7 @@ internalReference: 891184
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar a API Catalog Search, o máximo de resultados obtidos é 2500, mesmo que haja mais produtos.
diff --git a/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md b/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
index dae59fe0f..0ce4e8795 100644
--- a/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
+++ b/docs/known-issues/pt/catalog-search-facets-api-does-not-return-information-for-products-unavailable.md
@@ -18,9 +18,7 @@ internalReference: 583623
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Facetas de Pesquisa de Catálogo API / Portal Search Result Filtros não retornam informações para produtos indisponíveis e configurados para serem mostrados sem estoque. O produto aparecerá no Resultado da Busca, mas seus filtros não aparecerão.
diff --git a/docs/known-issues/pt/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md b/docs/known-issues/pt/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md
index 3543b8bf7..79fb8978f 100644
--- a/docs/known-issues/pt/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md
+++ b/docs/known-issues/pt/catalog-sku-specification-export-will-not-always-export-all-the-data-if-the-selected-category-is-a-department.md
@@ -18,9 +18,7 @@ internalReference: 465445
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exportação de especificações de SKU do catálogo nem sempre exportará todos os dados se for selecionado o departamento e não a subcategoria mais interna.
diff --git a/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md b/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md
index cf392f816..21aba6afb 100644
--- a/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md
+++ b/docs/known-issues/pt/catalog-translations-not-reflecting-on-the-frontend.md
@@ -18,9 +18,7 @@ internalReference: 861892
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comerciante executa uma ação no aplicativo Messages para que alguns dados do produto sejam traduzidos no frontend, essa ação não está sendo refletida de fato.
diff --git a/docs/known-issues/pt/catalogv2-user-roles-not-applying.md b/docs/known-issues/pt/catalogv2-user-roles-not-applying.md
index 7b93d7e4e..4547155dd 100644
--- a/docs/known-issues/pt/catalogv2-user-roles-not-applying.md
+++ b/docs/known-issues/pt/catalogv2-user-roles-not-applying.md
@@ -18,9 +18,7 @@ internalReference: 489297
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Atualmente, a IU do usuário para a aplicação CatalogV2 não está aplicando corretamente as permissões de controle de acesso quando um usuário está utilizando a IU para criar/ler/atualizar produtos.
 
diff --git a/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md b/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
index 212edafe9..30fd4a595 100644
--- a/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
+++ b/docs/known-issues/pt/categories-and-brands-spreadsheet-mapping-do-not-update-with-values-from-review-skus-tab.md
@@ -18,9 +18,7 @@ internalReference: 1026699
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um vendedor envia ao marketplace um sku com uma categoria ou marca que ainda não está mapeada na planilha, a planilha é atualizada com esse novo valor na 3ª coluna para ser mapeada.
diff --git a/docs/known-issues/pt/categoriesaspx-specification-timeout.md b/docs/known-issues/pt/categoriesaspx-specification-timeout.md
index cc3a61e9d..ff12b7a7a 100644
--- a/docs/known-issues/pt/categoriesaspx-specification-timeout.md
+++ b/docs/known-issues/pt/categoriesaspx-specification-timeout.md
@@ -18,9 +18,7 @@ internalReference: 433664
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Não há limite para o registro dos campos de especificação, o que pode gerar timeouts na administração do catálogo.
diff --git a/docs/known-issues/pt/category-commissioning-on-the-seller-config-generates-time-out.md b/docs/known-issues/pt/category-commissioning-on-the-seller-config-generates-time-out.md
index 61f12c82c..aa80c1cbc 100644
--- a/docs/known-issues/pt/category-commissioning-on-the-seller-config-generates-time-out.md
+++ b/docs/known-issues/pt/category-commissioning-on-the-seller-config-generates-time-out.md
@@ -18,9 +18,7 @@ internalReference: 310527
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se uma conta tem muitas categorias, na tela de configuração do vendedor ela pode não estar carregando o Comissionamento de Categoria devido a um intervalo de tempo.
diff --git a/docs/known-issues/pt/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/pt/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
index 23fb89fa7..7bb5b326e 100644
--- a/docs/known-issues/pt/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
+++ b/docs/known-issues/pt/category-linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -18,9 +18,7 @@ internalReference: 654951
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o gráfico do catálogo e traduzir a URL usando o linkId o reescritor deve armazenar o linkId, mas, isso não está acontecendo: https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization#category
diff --git a/docs/known-issues/pt/category-specs-do-not-open-in-admin-on-first-attempt.md b/docs/known-issues/pt/category-specs-do-not-open-in-admin-on-first-attempt.md
index c1edd8e63..9954dcd1c 100644
--- a/docs/known-issues/pt/category-specs-do-not-open-in-admin-on-first-attempt.md
+++ b/docs/known-issues/pt/category-specs-do-not-open-in-admin-on-first-attempt.md
@@ -18,9 +18,7 @@ internalReference: 664419
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, ao tentar abrir uma especificação de produto ou sku nas categorias admin a página não carrega corretamente e é atualizada de volta à página inicial da árvore de categorias.
diff --git a/docs/known-issues/pt/category-substitute-words-not-being-indexed.md b/docs/known-issues/pt/category-substitute-words-not-being-indexed.md
index ce1fa9618..256f3eff6 100644
--- a/docs/known-issues/pt/category-substitute-words-not-being-indexed.md
+++ b/docs/known-issues/pt/category-substitute-words-not-being-indexed.md
@@ -18,9 +18,7 @@ internalReference: 374204
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/category-translation-fields-being-overwritten-on-catalog-graphql.md b/docs/known-issues/pt/category-translation-fields-being-overwritten-on-catalog-graphql.md
index e0d4caee5..2cbfda413 100644
--- a/docs/known-issues/pt/category-translation-fields-being-overwritten-on-catalog-graphql.md
+++ b/docs/known-issues/pt/category-translation-fields-being-overwritten-on-catalog-graphql.md
@@ -18,9 +18,7 @@ internalReference: 654896
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao traduzir o conteúdo usando o aplicativo de catálogo-graphql ou a tradução do catálogo, os campos como nome, título ou descrição estão sendo sobregravados. Este comportamento só acontece se um destes campos (nome, título, descrição) for igual no registro do catálogo.
diff --git a/docs/known-issues/pt/categorycommissionpercentage-on-seller-api-allowing-any-value.md b/docs/known-issues/pt/categorycommissionpercentage-on-seller-api-allowing-any-value.md
index 276251fe8..4cd126190 100644
--- a/docs/known-issues/pt/categorycommissionpercentage-on-seller-api-allowing-any-value.md
+++ b/docs/known-issues/pt/categorycommissionpercentage-on-seller-api-allowing-any-value.md
@@ -18,9 +18,7 @@ internalReference: 382680
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No PUT Seller API, a categoria de propriedadeCommissionPercentage aceita qualquer tipo de entrada, por exemplo, entradas de texto. Isto pode até quebrar o processo de indexação para produtos que possuem SKUs nos quais este vendedor está incluído.
diff --git a/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md b/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md
index fde07d4f9..1c170352b 100644
--- a/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md
+++ b/docs/known-issues/pt/centauro-orders-with-pedido-sem-o-campo-packages-error.md
@@ -18,9 +18,7 @@ internalReference: 604422
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md b/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
index c2d693ceb..04c1560cf 100644
--- a/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
+++ b/docs/known-issues/pt/change-order-link-on-checkoutorderplaced-is-leading-to-myaccount-instead-of-the-order-page.md
@@ -18,9 +18,7 @@ internalReference: 844893
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a conta tiver configurado a possibilidade de o comprador alterar o pedido por conta própria, o link de alteração de pedido aparecerá no modelo checkout/orderPlaced.
diff --git a/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md b/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
index 8df6434eb..291a17f7a 100644
--- a/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
+++ b/docs/known-issues/pt/change-order-through-the-ui-does-not-take-into-account-the-calculation-of-promotions-take-3-pay-2.md
@@ -18,9 +18,7 @@ internalReference: 472882
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em pedidos com um Mais por Menos Promoção, é possível alterar o pedido e remover um ou mais itens na IU, mas o desconto ainda se aplica.
diff --git a/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md b/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md
index f9a57abe0..38e34985e 100644
--- a/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md
+++ b/docs/known-issues/pt/change-order-using-api-without-email-orderchanged.md
@@ -18,9 +18,7 @@ internalReference: 380509
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a administração de uma conta muda o pedido aplicando descontos no valor e não nos itens usando API o e-mail de Pedido de Mudança não está sendo enviado ao cliente final.
diff --git a/docs/known-issues/pt/change-the-number-of-characters-in-the-braspag-slip.md b/docs/known-issues/pt/change-the-number-of-characters-in-the-braspag-slip.md
index 7bcd355aa..356e5ed2d 100644
--- a/docs/known-issues/pt/change-the-number-of-characters-in-the-braspag-slip.md
+++ b/docs/known-issues/pt/change-the-number-of-characters-in-the-braspag-slip.md
@@ -18,9 +18,7 @@ internalReference: 771045
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um pedido é gerado via boleto com a Braspag e nos dados de endereço, se tiver mais de 40 caracteres, os dados de endereço estão sendo cortados. Você precisará fazer uma melhoria mudando o limite de caracteres do campo de endereço de 40 caracteres para 60.
diff --git a/docs/known-issues/pt/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md b/docs/known-issues/pt/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md
index ee505d293..fbbee32dc 100644
--- a/docs/known-issues/pt/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md
+++ b/docs/known-issues/pt/changes-made-in-site-editor-are-saved-but-dont-reflect-on-the-page.md
@@ -18,9 +18,7 @@ internalReference: 786145
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você cria uma nova página em Páginas e depois muda seu caminho para algo diferente, a rotaId não muda. Portanto, quando você cria outra página com o mesmo caminho que a primeira, a rotaId permanecerá a mesma. E então o editor do site terá problemas para salvar o conteúdo destas duas páginas devido a conflitos em suas rotas.
diff --git a/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md b/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
index b104ee9df..ba80436e9 100644
--- a/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
+++ b/docs/known-issues/pt/changes-made-in-the-styles-admin-page-are-not-saved-properly.md
@@ -18,9 +18,7 @@ internalReference: 971948
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As alterações feitas usando a página de estilos da interface do usuário do administrador não estão sendo salvas corretamente no momento e nem sempre são aplicadas ao site.
diff --git a/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md b/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md
index 210372962..e21a77075 100644
--- a/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md
+++ b/docs/known-issues/pt/changing-accessories-is-not-triggering-indexation.md
@@ -18,9 +18,7 @@ internalReference: 1037800
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comerciante faz alterações ou adiciona novos acessórios à sku, o indexador não está sendo acionado automaticamente.
diff --git a/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md b/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
index b42acc50d..0f2d5430b 100644
--- a/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
+++ b/docs/known-issues/pt/changing-the-order-of-a-sku-specification-on-the-admin-could-make-the-page-not-work-correctly.md
@@ -18,9 +18,7 @@ internalReference: 460329
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alterar a ordem de uma especificação SKU na Admin poderia fazer com que a página não funcionasse corretamente.
diff --git a/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md b/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md
index c51ab3d6f..079d8f17a 100644
--- a/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md
+++ b/docs/known-issues/pt/checkbox-requires-authentication-doesnt-work-on-pages-module.md
@@ -18,9 +18,7 @@ internalReference: 577306
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O recurso de autenticação, que é gerenciado por uma seleção de caixa de seleção no módulo Páginas, não funciona corretamente. O usuário não é redirecionado para uma página de pedido de autenticação quando a caixa de seleção é marcada.
diff --git a/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md b/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
index 8d60d35b4..caf70bbda 100644
--- a/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
+++ b/docs/known-issues/pt/checkout-allows-proceeding-to-payment-form-without-shipping-address-on-the-ui-only.md
@@ -18,9 +18,7 @@ internalReference: 699317
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um carrinho com SLA somente para entrega e o usuário digita um código postal correto, o checkout permite ao usuário prosseguir, no entanto, se o usuário retornar à página do carrinho novamente e mudar para a opção de retirada, então clique para continuar para a parte de pagamento, depois volte ao carrinho novamente, mude novamente para a opção de entrega e continue novamente, desta vez, o usuário vai para o formulário de pagamento. Além disso, há uma mensagem na parte do endereço de entrega dizendo que o componente está "esperando os dados para ser preenchido".
diff --git a/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md b/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md
index d0be7c284..ff6f658a6 100644
--- a/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md
+++ b/docs/known-issues/pt/checkout-allows-to-add-2-different-addresses-for-delivery.md
@@ -18,9 +18,7 @@ internalReference: 931225
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O checkout permite adicionar dois endereços diferentes para entrega no formulário de pedido, por exemplo, um "comercial" e um "residencial" (definido pelo campo "addressType"), quando um deles é descartável.
diff --git a/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md b/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
index 268fbfb34..e3cd73ea6 100644
--- a/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
+++ b/docs/known-issues/pt/checkout-allows-users-to-jump-to-payment-step-with-an-empty-shippingdata-when-using-geolocation.md
@@ -18,9 +18,7 @@ internalReference: 343056
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar a geolocalização no checkout, os usuários podem pular para a etapa de pagamento com o `shippingData` incompleto.
diff --git a/docs/known-issues/pt/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md b/docs/known-issues/pt/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md
index 5366da858..6fbcad47e 100644
--- a/docs/known-issues/pt/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md
+++ b/docs/known-issues/pt/checkout-api-may-not-group-packages-when-two-or-more-sellers-can-fulfill.md
@@ -18,9 +18,7 @@ internalReference: 802156
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando dois ou mais vendedores podem preencher um carrinho com mais de um item, a API do Checkout pode não agrupar pacotes selecionando vendedores diferentes para cada produto. Isso aumenta o valor do frete para o comprador.
diff --git a/docs/known-issues/pt/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md b/docs/known-issues/pt/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md
index 3fc5146ef..88ea082aa 100644
--- a/docs/known-issues/pt/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md
+++ b/docs/known-issues/pt/checkout-cant-remove-gift-item-when-unavailable-after-pickuppoint-selected.md
@@ -18,9 +18,7 @@ internalReference: 363885
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao utilizar um item em um carrinho com um benefício de promoção de presentes, o item dentro dele não pode ser removido se não estiver disponível após a seleção do ponto de coleta.
diff --git a/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md b/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
index 9a4145b5c..01c734c69 100644
--- a/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
+++ b/docs/known-issues/pt/checkout-does-not-correctly-calculate-shipping-value-for-single-item-that-has-free-shipping-and-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 529043
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o carrinho consiste em dois itens, e o tipo de entrega é programada, ao adicionar o primeiro item ao carrinho com envio gratuito, e é o mesmo SLA, o checkout acaba cobrando o valor desse envio, pois não sabe como lidar com a distribuição de cálculo de valores de frete entre os itens, pois é uma entrega programada e o preço de janela é para um pacote como um todo.
diff --git a/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md b/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
index 6f08edd84..4a2e0ab4c 100644
--- a/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
+++ b/docs/known-issues/pt/checkout-does-not-display-shipping-promotion-at-first-instant-for-specific-condition.md
@@ -18,9 +18,7 @@ internalReference: 280144
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O checkout (backend) tem o comportamento de pré-selecionar o melhor método de entrega para o usuário assim que um código postal é informado.
diff --git a/docs/known-issues/pt/checkout-does-not-show-option-to-change-zip-code.md b/docs/known-issues/pt/checkout-does-not-show-option-to-change-zip-code.md
index 5642e40ac..57d4907a3 100644
--- a/docs/known-issues/pt/checkout-does-not-show-option-to-change-zip-code.md
+++ b/docs/known-issues/pt/checkout-does-not-show-option-to-change-zip-code.md
@@ -18,9 +18,7 @@ internalReference: 321598
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para itens que estão restritos à coleta na loja para determinados endereços, a opção de alterar o código postal está desaparecendo enquanto o usuário estiver na guia de entrega, no carrinho .
diff --git a/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md b/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md
index 584cab92b..feb2b50c6 100644
--- a/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md
+++ b/docs/known-issues/pt/checkout-does-not-support-encoding-assembly-options-names.md
@@ -18,9 +18,7 @@ internalReference: 378842
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O nome das opções de montagem é usado na rota da API. Portanto, é necessário oferecer suporte à codificação desses nomes para não criar problemas na URL com caracteres especiais, como "/". Ao adicionar uma opção de montagem com "/" no carrinho, ela simplesmente não é adicionada e também não notifica o usuário.
diff --git a/docs/known-issues/pt/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md b/docs/known-issues/pt/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md
index 0a1022b18..8eb192908 100644
--- a/docs/known-issues/pt/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md
+++ b/docs/known-issues/pt/checkout-firing-google-analytics-pageview-events-multiplied-per-tracker.md
@@ -18,9 +18,7 @@ internalReference: 350780
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A implementação do Google Analytics do Checkout está disparando o evento de pageview uma vez por rastejador, mesmo que o rastejador não tenha a intenção de rastrear as informações de pageview.
diff --git a/docs/known-issues/pt/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md b/docs/known-issues/pt/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md
index db6bd0d71..65f81d436 100644
--- a/docs/known-issues/pt/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md
+++ b/docs/known-issues/pt/checkout-forcing-the-shipping-step-in-delivery-mode-while-the-address-and-pickup-point-option-was-defined-via-api.md
@@ -18,9 +18,7 @@ internalReference: 287444
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md b/docs/known-issues/pt/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md
index 4e8aaee05..8e359fc5e 100644
--- a/docs/known-issues/pt/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md
+++ b/docs/known-issues/pt/checkout-has-no-clarity-about-divergences-between-the-identified-and-the-logged-in-customer.md
@@ -18,9 +18,7 @@ internalReference: 442267
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Enquanto estiver no checkout, você precisará fazer login para ver/alterar informações pessoais e, em alguns casos, até mesmo concluir a compra. O processo de login é desconectado do formulário de pedido, portanto, você pode fazer login com qualquer e-mail e ser identificado com outro e-mail no fluxo de compra.
diff --git a/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md b/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md
index 1bd22b492..cb0016d2a 100644
--- a/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md
+++ b/docs/known-issues/pt/checkout-incorrectly-sending-item-details-to-transaction.md
@@ -18,9 +18,7 @@ internalReference: 535859
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md b/docs/known-issues/pt/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md
index a0b9c0a96..adb028294 100644
--- a/docs/known-issues/pt/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md
+++ b/docs/known-issues/pt/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md
@@ -18,9 +18,7 @@ internalReference: 258447
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao finalizar a compra com um e-mail informado e dados mascarados, será necessário fazer login se o comprador quiser alterar alguma informação. Na caixa de login que será aberta, o e-mail já estará preenchido com o contexto do carrinho, mas a interface permite que o e-mail "sugerido" seja modificado.
diff --git a/docs/known-issues/pt/checkout-orderplaced-boleto-bank-invoice-moip.md b/docs/known-issues/pt/checkout-orderplaced-boleto-bank-invoice-moip.md
index d13d29879..54c914549 100644
--- a/docs/known-issues/pt/checkout-orderplaced-boleto-bank-invoice-moip.md
+++ b/docs/known-issues/pt/checkout-orderplaced-boleto-bank-invoice-moip.md
@@ -18,9 +18,7 @@ internalReference: 376951
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O OrderPlaced tem um recurso automático que injeta o PDF do "Boleto - Bank Invoice" em um iframe dentro da página de pedido acabado.
diff --git a/docs/known-issues/pt/checkout-overwrites-receiver-name-with-customer-name.md b/docs/known-issues/pt/checkout-overwrites-receiver-name-with-customer-name.md
index 2b1c9d424..4df9e0653 100644
--- a/docs/known-issues/pt/checkout-overwrites-receiver-name-with-customer-name.md
+++ b/docs/known-issues/pt/checkout-overwrites-receiver-name-with-customer-name.md
@@ -18,9 +18,7 @@ internalReference: 324792
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O nome do receptor é reescrito com o nome do cliente após recarregar a página de checkout.
diff --git a/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md b/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
index 1bf54c8c9..18ec1f3a4 100644
--- a/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
+++ b/docs/known-issues/pt/checkout-payment-split-may-generate-incorrect-information-in-the-paymentdata.md
@@ -18,19 +18,13 @@ internalReference: 330802
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md b/docs/known-issues/pt/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md
index 6c82345c4..96d0a401f 100644
--- a/docs/known-issues/pt/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md
+++ b/docs/known-issues/pt/checkout-payment-step-doesnt-work-if-apple-pay-is-the-first-payment-method.md
@@ -18,19 +18,13 @@ internalReference: 704699
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md b/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
index 0bf3d882d..82ba63d74 100644
--- a/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
+++ b/docs/known-issues/pt/checkout-pipeline-doesnt-update-taxes-considering-the-correct-seller-when-merging-cart-information.md
@@ -18,9 +18,7 @@ internalReference: 759842
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há dois vendedores no método "SellerElection", um deles é selecionado como tendo o preço mais barato para entrega e o outro como o preço mais barato para retirada no ponto, a mesclagem de informações do carrinho não atualiza os impostos ao selecionar a retirada no ponto, causando um erro ao concluir a compra
diff --git a/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md b/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
index 3f8d7d981..7ebfabb1f 100644
--- a/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
+++ b/docs/known-issues/pt/checkout-simulation-returns-value-0-in-slastax-field-for-shipping-percentage-taxes.md
@@ -18,9 +18,7 @@ internalReference: 1012724
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os impostos de porcentagem de envio não são retornados no campo `logisticsInfo.slas.tax` ao realizar uma simulação de checkout, embora as informações de impostos individuais estejam disponíveis no campo `items.priceTags`.
diff --git a/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md b/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
index 99d4e1448..49506bafa 100644
--- a/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
+++ b/docs/known-issues/pt/checkout-simulation-with-a-great-quantity-of-the-same-sku-receives-a-logistics-timeout.md
@@ -18,9 +18,7 @@ internalReference: 330775
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Temos um erro no serviço de logística ao tentar simular uma compra com milhares de unidades da mesma SKU. Esse erro ocorre porque a solicitação para dividir o pacote leva muito tempo.
diff --git a/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md b/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
index 4896fc69d..2b05ee541 100644
--- a/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
+++ b/docs/known-issues/pt/checkout-ui-goes-to-payment-with-an-incomplete-invoice-address-for-shoppers-with-complete-profile.md
@@ -18,9 +18,7 @@ internalReference: 937615
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um comprador tiver um perfil completo e a loja estiver configurada para usar um endereço de fatura para retirada, a interface do usuário avançará para o pagamento com um endereço de fatura incompleto.
diff --git a/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md b/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
index 6f6ddceac..653fd20d4 100644
--- a/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
+++ b/docs/known-issues/pt/checkout-ui-is-not-automatically-using-lean-shipping-for-items-with-no-common-shipping-methods.md
@@ -18,9 +18,7 @@ internalReference: 329846
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As configurações da interface do usuário do checkout permitem que você desative o envio simples (otimizações do modo de entrega), mas isso só é possível se todos os itens no carrinho tiverem os mesmos métodos de entrega em comum. Caso contrário, o envio enxuto deve aparecer de forma forçada no carrinho, mesmo com a opção desativada.
diff --git a/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md b/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
index 37f7f8e71..4f0c1d208 100644
--- a/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
+++ b/docs/known-issues/pt/checkout-ui-loops-when-not-receiving-correct-sla-values-from-logistics-system.md
@@ -18,19 +18,13 @@ internalReference: 485016
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md b/docs/known-issues/pt/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md
index 7f1b1dbbb..6bce0c59c 100644
--- a/docs/known-issues/pt/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md
+++ b/docs/known-issues/pt/checkout-ui-overwrites-shipping-recipient-when-name-is-different-from-profile-data.md
@@ -18,9 +18,7 @@ internalReference: 822670
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se um comprador tiver um perfil completo em que o nome e o sobrenome sejam diferentes do destinatário da remessa, quando o perfil for preenchido automaticamente no checkout, a interface do usuário substituirá o destinatário da remessa pelo valor do nome e do sobrenome combinados.
diff --git a/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md b/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
index e14b1ee74..8ca75369a 100644
--- a/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
+++ b/docs/known-issues/pt/checkout-ui-sends-hyphen-in-the-postal-code-to-orderform.md
@@ -18,9 +18,7 @@ internalReference: 937692
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface do usuário do checkout envia um hífen para o código postal para o formulário de pedido, causando problemas no cálculo de SLAs quando um país tem 7 dígitos + o hífen. Isso acontece porque o módulo Logistics considera o hífen como um dígito e depende de como as taxas de envio foram registradas na política de envio.
diff --git a/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md b/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
index 3365dd796..efbf95aad 100644
--- a/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
+++ b/docs/known-issues/pt/checkout-ui-shows-free-shipping-when-the-user-switches-the-delivery-options.md
@@ -18,9 +18,7 @@ internalReference: 897109
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface de usuário do checkout mostra a entrega gratuita quando o usuário muda o método de entrega de envio normal para entrega programada. O problema ocorre somente na caixa de entrega e quando a conta tem o recurso LeanShipping configurado. Embora a interface do usuário mostre o frete grátis, os valores totais da compra são exibidos e cobrados corretamente.
diff --git a/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md b/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
index f96aa758d..15d7a02d2 100644
--- a/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
+++ b/docs/known-issues/pt/checkout-ui-unselects-the-schedule-all-toggle-after-refreshing-the-page.md
@@ -18,9 +18,7 @@ internalReference: 784693
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Checkout UI desmarca a opção "Schedule all" na etapa de envio depois de atualizar a página, mesmo que a API ainda esteja selecionada. Este comportamento não tem impacto; o pedido terá a entrega programada selecionada.
diff --git a/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md b/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
index 0a070a8fc..fae44c391 100644
--- a/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
+++ b/docs/known-issues/pt/city-and-state-are-not-sent-to-paypalplus-when-there-is-only-pickup-address-available.md
@@ -18,9 +18,7 @@ internalReference: 836025
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os campos "cidade" e "estado" não são enviados ao PayPalPlus quando o comprador adiciona apenas um endereço de retirada ao carrinho, fazendo com que a forma de pagamento não seja carregada.
diff --git a/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md b/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
index ecd221572..064ad1ff2 100644
--- a/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
+++ b/docs/known-issues/pt/clear-filter-button-doesnt-handle-multiple-filters-correctly.md
@@ -18,9 +18,7 @@ internalReference: 960905
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns cenários, como páginas de destino e páginas de coleção, os filtros adicionais não são limpos corretamente após clicar no botão "limpar filtro". O URL pode ir para filtros inválidos ou errados e a listagem de produtos pode ficar vazia ou com produtos inesperados.
diff --git a/docs/known-issues/pt/clicks-on-the-numericstepper-not-working.md b/docs/known-issues/pt/clicks-on-the-numericstepper-not-working.md
index 363904264..6d00d5cd4 100644
--- a/docs/known-issues/pt/clicks-on-the-numericstepper-not-working.md
+++ b/docs/known-issues/pt/clicks-on-the-numericstepper-not-working.md
@@ -18,9 +18,7 @@ internalReference: 537245
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os cliques do Stepper Numérico não estão funcionando como esperado - você ainda pode editar a caixa de texto mas os botões não aumentam ou diminuem o número da caixa de texto. As chamadas de rede parecem ser enviadas da mesma forma. O cliente relatou este problema ao usar o Windows 11 com o Chrome. Algumas considerações:
diff --git a/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md b/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
index 39f8a5f18..708a0c4cd 100644
--- a/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
+++ b/docs/known-issues/pt/client-document-value-will-not-update-correctly-sometimes-in-global-checkout-setting.md
@@ -18,9 +18,7 @@ internalReference: 863726
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o Global Checkout, a alteração do uso do documento padrão para um documento autoidentificado e o valor informado para o campo de número do documento não "pegará" corretamente.
diff --git a/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md b/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
index eb0cd1252..c403bd8c7 100644
--- a/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
+++ b/docs/known-issues/pt/clientprofiledata-gets-empty-if-request-add-client-profile-is-performed-twice.md
@@ -18,9 +18,7 @@ internalReference: 911203
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao enviar a solicitação Adicionar perfil de cliente duas vezes e o e-mail tiver um perfil completo, "clientProfileData" fica vazio, mostrando apenas o e-mail.
diff --git a/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md b/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
index f7fba702e..70bde7b6f 100644
--- a/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
+++ b/docs/known-issues/pt/cms-allows-the-creation-but-not-the-editing-of-folders-with-the-same-names-as-the-default-ones.md
@@ -18,9 +18,7 @@ internalReference: 566791
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o CMS permite a criação de pastas com os mesmos nomes que as pastas padrão, mas mais tarde não permite a edição/eliminação dessas novas pastas
diff --git a/docs/known-issues/pt/cms-legacy-collections-timeout.md b/docs/known-issues/pt/cms-legacy-collections-timeout.md
index 144b67fee..f6446dec8 100644
--- a/docs/known-issues/pt/cms-legacy-collections-timeout.md
+++ b/docs/known-issues/pt/cms-legacy-collections-timeout.md
@@ -18,9 +18,7 @@ internalReference: 434026
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Frequentemente, ao tentar salvar os dados de um grupo de coleções usando o aplicativo de coleções legado, no caminho /admin/a e ao tentar salvar o grupo, o usuário, em casos de catálogos grandes (grande quantidade de categorias, marcas, produtos), recebe uma mensagem de erro de tempo limite e não consegue salvar as alterações.
 
diff --git a/docs/known-issues/pt/cms-loyalty-value-settings-not-working.md b/docs/known-issues/pt/cms-loyalty-value-settings-not-working.md
index 3bf176bb1..f3259ff79 100644
--- a/docs/known-issues/pt/cms-loyalty-value-settings-not-working.md
+++ b/docs/known-issues/pt/cms-loyalty-value-settings-not-working.md
@@ -18,9 +18,7 @@ internalReference: 726849
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md b/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
index a2c45134e..b68975e63 100644
--- a/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
+++ b/docs/known-issues/pt/cms-settings-does-not-allow-removing-value-from-the-unit-of-mass-field.md
@@ -18,9 +18,7 @@ internalReference: 540756
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando você insere um valor no campo Unidade de massa nas configurações do CMS, o sistema não permite que o valor seja removido pela IU
diff --git a/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md b/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md
index 07c5c049b..0945cab00 100644
--- a/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md
+++ b/docs/known-issues/pt/cms-settings-role-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 538706
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A função de configurações do CMS não está funcionando como esperado. Às vezes, o usuário não consegue acessar o CMS mesmo depois de ser adicionado à função.
diff --git a/docs/known-issues/pt/cms-styles-selector-doesnt-work-in-development-workspaces.md b/docs/known-issues/pt/cms-styles-selector-doesnt-work-in-development-workspaces.md
index c3c906765..06743076e 100644
--- a/docs/known-issues/pt/cms-styles-selector-doesnt-work-in-development-workspaces.md
+++ b/docs/known-issues/pt/cms-styles-selector-doesnt-work-in-development-workspaces.md
@@ -18,9 +18,7 @@ internalReference: 388544
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/cobranded-saved-card-with-wrong-payment-system-id.md b/docs/known-issues/pt/cobranded-saved-card-with-wrong-payment-system-id.md
index bf8751092..9a7ee835d 100644
--- a/docs/known-issues/pt/cobranded-saved-card-with-wrong-payment-system-id.md
+++ b/docs/known-issues/pt/cobranded-saved-card-with-wrong-payment-system-id.md
@@ -18,9 +18,7 @@ internalReference: 833400
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, quando um pedido é pago com um cartão de marca compartilhada, o cartão salvo tem o ID do sistema de pagamento errado. Quando esse problema ocorre, as informações do cartão salvo são exibidas no método de pagamento errado no card-ui.
diff --git a/docs/known-issues/pt/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md b/docs/known-issues/pt/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md
index a0e5e7289..76351a13f 100644
--- a/docs/known-issues/pt/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md
+++ b/docs/known-issues/pt/cold-start-requests-failing-with-timeout-and-courier-retries-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 789499
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um aplicativo não recebe solicitações por algum tempo, ele entra em cold start. O Courier faz várias tentativas de enviar eventos até que o aplicativo "acorde". Quando o aplicativo não "acorda", as solicitações a ele podem falhar devido a um tempo limite. Como resultado, acontece que alguns eventos parecem nunca ser enviados. Esse é um comportamento intermitente
diff --git a/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md b/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md
index d309e8547..0999866dc 100644
--- a/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md
+++ b/docs/known-issues/pt/collapsible-menu-issues-rendering-all-the-items.md
@@ -18,9 +18,7 @@ internalReference: 542091
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, ao usar um submenu dobrável que tem muitos itens do tamanho do menu pode travar e com ele não exibir todos os itens dentro. Isto acontece devido a um valor calculado que define a altura do menu.
diff --git a/docs/known-issues/pt/collection-functionality-doesnt-work-on-giftcard.md b/docs/known-issues/pt/collection-functionality-doesnt-work-on-giftcard.md
index f3bed8e00..48cc9438d 100644
--- a/docs/known-issues/pt/collection-functionality-doesnt-work-on-giftcard.md
+++ b/docs/known-issues/pt/collection-functionality-doesnt-work-on-giftcard.md
@@ -18,19 +18,13 @@ internalReference: 319349
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/collection-ordering-not-working-as-expected.md b/docs/known-issues/pt/collection-ordering-not-working-as-expected.md
index 84ad85f51..6098bbc02 100644
--- a/docs/known-issues/pt/collection-ordering-not-working-as-expected.md
+++ b/docs/known-issues/pt/collection-ordering-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 502409
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em Coleções (Beta), devemos poder alterar a ordem dos produtos dentro de uma coleção usando o recurso "Mover para a posição":
diff --git a/docs/known-issues/pt/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md b/docs/known-issues/pt/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md
index ce255d81d..adfe755ce 100644
--- a/docs/known-issues/pt/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md
+++ b/docs/known-issues/pt/collection-searchtitle-doesnt-display-accents-when-accessed-through-mapproductclusternames.md
@@ -18,9 +18,7 @@ internalReference: 439856
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As páginas de coleção acessadas através de map=productClusterNames mostram o nome da coleção sem acentos no componente de busca-titulo.
diff --git a/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md b/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md
index d0f29ef26..3a0b97697 100644
--- a/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md
+++ b/docs/known-issues/pt/collections-does-not-allow-more-than-1000-skus-per-upload.md
@@ -18,9 +18,7 @@ internalReference: 793274
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o upload de itens para o novo módulo de coleções com uma lista que tem mais de 1000 SKUs não é possível, uma vez que o processo terá um timeout.
diff --git a/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md b/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
index e642f9d8f..23518d929 100644
--- a/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
+++ b/docs/known-issues/pt/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md
@@ -18,9 +18,7 @@ internalReference: 1043470
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As páginas de resultados de pesquisa personalizados configuradas com o ID da coleção não funcionam quando coleções de produtos diferentes são atribuídas a uma organização.
diff --git a/docs/known-issues/pt/collections-dont-open-on-subaccounts.md b/docs/known-issues/pt/collections-dont-open-on-subaccounts.md
index d5178c83b..e89f0d2e5 100644
--- a/docs/known-issues/pt/collections-dont-open-on-subaccounts.md
+++ b/docs/known-issues/pt/collections-dont-open-on-subaccounts.md
@@ -18,9 +18,7 @@ internalReference: 649948
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar abrir uma coleção no novo módulo de coleções de uma subconta, é retornado o erro "Desculpe, ocorreu um erro desconhecido".
diff --git a/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md b/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md
index 14c560df0..70676ae8c 100644
--- a/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md
+++ b/docs/known-issues/pt/collections-export-only-shows-1st-sku-of-inactive-product.md
@@ -18,9 +18,7 @@ internalReference: 1040753
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o módulo de coleções e tentar exportar registros, se o produto listado em uma determinada coleção tiver todos os seus skus definidos como inativos, a planilha exportada listará apenas um dos skus do produto, em vez de todos.
diff --git a/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md b/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
index 23a973c19..291fe6eb2 100644
--- a/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
+++ b/docs/known-issues/pt/collections-field-always-appearing-as-equal-to-on-the-campaign-audience-form.md
@@ -18,9 +18,7 @@ internalReference: 697168
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md b/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md
index 649a14451..52a8114cd 100644
--- a/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md
+++ b/docs/known-issues/pt/collections-named-with-special-characters-cannot-be-exported.md
@@ -18,9 +18,7 @@ internalReference: 683343
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que uma coleção possa ser exportada no administrador. Entretanto, coleções com nomes que contenham símbolos como `$` , `+` ou `,` não podem ser exportadas.
diff --git a/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md b/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md
index 962ce3911..64b6a156d 100644
--- a/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md
+++ b/docs/known-issues/pt/collections-page-in-organization-details-shows-only-20-collections.md
@@ -18,9 +18,7 @@ internalReference: 891511
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A página Coleções em Detalhes da organização mostra apenas 20 coleções, mesmo depois de alterar a quantidade de linhas na parte inferior da página.
diff --git a/docs/known-issues/pt/collections-schedule-end-date-not-working.md b/docs/known-issues/pt/collections-schedule-end-date-not-working.md
index 8e8abc6aa..4261ee4aa 100644
--- a/docs/known-issues/pt/collections-schedule-end-date-not-working.md
+++ b/docs/known-issues/pt/collections-schedule-end-date-not-working.md
@@ -18,9 +18,7 @@ internalReference: 497880
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando a data final de uma coleção programada é atingida, o processo de reindexação dos produtos contidos nela não é acionado, fazendo com que a programação da data final não funcione como um todo.
diff --git a/docs/known-issues/pt/collections-schedule-start-date-not-working.md b/docs/known-issues/pt/collections-schedule-start-date-not-working.md
index 0ebc4dafe..5a851aa9b 100644
--- a/docs/known-issues/pt/collections-schedule-start-date-not-working.md
+++ b/docs/known-issues/pt/collections-schedule-start-date-not-working.md
@@ -18,9 +18,7 @@ internalReference: 667328
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando a data de início de uma coleta programada é atingida, o processo de reindexação dos produtos nela contidos não é acionado, ou seja, a programação da data de início não funciona como um todo. Como conseqüência, os produtos não são indexados na coleção na data configurada.
diff --git a/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md b/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md
index eeeddf2b0..2b3bb8a6f 100644
--- a/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md
+++ b/docs/known-issues/pt/collections-trigger-not-working-as-expected-on-progressive-discounts.md
@@ -18,9 +18,7 @@ internalReference: 930849
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar uma promoção de desconto progressivo, o cliente pode definir o acionador por coleção, por uma lista de SKUs ou por ambos.
diff --git a/docs/known-issues/pt/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md b/docs/known-issues/pt/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md
index 950fe19ef..426975a90 100644
--- a/docs/known-issues/pt/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md
+++ b/docs/known-issues/pt/collections-ui-doesnt-allow-to-search-for-products-with-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 344451
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A nova coleção UI, `.myvtex.com/admin/collections', não permite que os usuários procurem produtos com caracteres especiais.
diff --git a/docs/known-issues/pt/comment-vtexcrm-field-is-not-showing-its-content.md b/docs/known-issues/pt/comment-vtexcrm-field-is-not-showing-its-content.md
index 428444944..5a7f131cb 100644
--- a/docs/known-issues/pt/comment-vtexcrm-field-is-not-showing-its-content.md
+++ b/docs/known-issues/pt/comment-vtexcrm-field-is-not-showing-its-content.md
@@ -18,9 +18,7 @@ internalReference: 565919
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md b/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
index 7b2db1973..69f1ae43e 100644
--- a/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
+++ b/docs/known-issues/pt/complete-orders-with-error-in-creation-due-to-failure-in-gatewaycallbak.md
@@ -18,9 +18,7 @@ internalReference: 416936
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Recebemos algumas consultas sobre pedidos que estavam presos no status de pagamento aprovado, mas já aprovados, o que não deveria acontecer no fluxo normal de pedidos.
diff --git a/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md b/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
index 0c0fc0be7..56d755e38 100644
--- a/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
+++ b/docs/known-issues/pt/component-drawer-doesnt-work-when-implemented-in-productsummary-for-ios.md
@@ -18,9 +18,7 @@ internalReference: 833338
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o componente "drawer" (gaveta) é implementado em "product-summary" (resumo do produto), ele faz com que a página seja recarregada após a página 3 no iOS, e uma mensagem de erro pode ser exibida.
diff --git a/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md b/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
index 635b51b83..f83aecba9 100644
--- a/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
+++ b/docs/known-issues/pt/component-seller-selector-may-present-inconsistency-in-deliveryshipping-prices.md
@@ -18,9 +18,7 @@ internalReference: 658452
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O componente Seletor do Vendedor apresenta inconsistência nos preços de entrega/remessa com base no valor do pedido.
diff --git a/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md b/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md
index d514d9791..549eea733 100644
--- a/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md
+++ b/docs/known-issues/pt/components-in-a-kit-with-the-same-price.md
@@ -18,9 +18,7 @@ internalReference: 989371
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os componentes em um kit têm o mesmo preço quando uma promoção de presente é configurada e um vendedor regular a cumpre.
diff --git a/docs/known-issues/pt/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md b/docs/known-issues/pt/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md
index 93f72d718..d7a1aabd5 100644
--- a/docs/known-issues/pt/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md
+++ b/docs/known-issues/pt/configuracao-de-quantidade-maxima-do-mesmo-item-no-carrinho-nao-pode-ser-alterada-por-contas-franquia.md
@@ -18,9 +18,7 @@ internalReference: 325273
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A configuração da quantidade máxima do mesmo item no carrinho não pode ser alterada pelas contas de franquia (vendedor whitelabel), pois ocorre em uma tela de catálogo legado (/admin/Site/ConfigForm.aspx) - módulo que é removido das contas de franquia, pois elas herdam os produtos da conta-mãe.
diff --git a/docs/known-issues/pt/confirmed-order-email-not-being-sent.md b/docs/known-issues/pt/confirmed-order-email-not-being-sent.md
index 3317b8fb0..315d35362 100644
--- a/docs/known-issues/pt/confirmed-order-email-not-being-sent.md
+++ b/docs/known-issues/pt/confirmed-order-email-not-being-sent.md
@@ -18,9 +18,7 @@ internalReference: 423628
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Checkout não mapeia todos os fluxos em que o "GatewayCallback" deve acionar o evento "Raised OrderPlaced", de modo que os fluxos não mapeados podem não acionar esse evento como esperado, afetando diretamente o e-mail de confirmação do pedido a ser enviado.
diff --git a/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md b/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
index 429bce919..0c9f5ebbd 100644
--- a/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
+++ b/docs/known-issues/pt/conflict-between-specifications-with-the-same-name-at-the-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 933958
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Várias especificações com o mesmo nome são agrupadas na mesma _"faceta"_ pela Pesquisa Inteligente, o que pode ser um problema se elas tiverem configurações diferentes.
diff --git a/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md b/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
index 34726445d..4a70ea5d3 100644
--- a/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
+++ b/docs/known-issues/pt/conflicts-with-price-filters-and-isavailablepersaleschannel-in-searches-portal-and-search-again.md
@@ -18,9 +18,7 @@ internalReference: 531277
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ## **Sumário***
 
diff --git a/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md b/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
index 44537903f..b1852e8e2 100644
--- a/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
+++ b/docs/known-issues/pt/console-error-report-only-refused-to-apply-inline-style-because-it-violates-the-following-content-security.md
@@ -18,9 +18,7 @@ internalReference: 1017370
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Temos alguns logs no console que relatam bloqueios de script devido a restrições por meio do cabeçalho CSP.
diff --git a/docs/known-issues/pt/cookie-broken-the-apisessions.md b/docs/known-issues/pt/cookie-broken-the-apisessions.md
index 81d76a1e7..961cf211d 100644
--- a/docs/known-issues/pt/cookie-broken-the-apisessions.md
+++ b/docs/known-issues/pt/cookie-broken-the-apisessions.md
@@ -18,9 +18,7 @@ internalReference: 779014
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há um script que gera um cookie para rastrear os usuários e seu cookie interrompe a chamada para /api/sessions, por exemplo, porque ele tem um caractere especial no cookie de valor. Então, precisamos descartar esses cookies malformados do nosso lado e manter todos os outros, para que isso não afete o comportamento.
diff --git a/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md b/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
index 18d8133d8..99045434f 100644
--- a/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
+++ b/docs/known-issues/pt/cost-center-dropdown-shows-only-25-options-in-b2b-admin-customers.md
@@ -18,9 +18,7 @@ internalReference: 921115
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao registrar um novo cliente usando o B2B Admin Customers, o menu suspenso do centro de custo mostra apenas 25 opções.
diff --git a/docs/known-issues/pt/cost-price-rounding-logic-diverges-on-computed-prices-api.md b/docs/known-issues/pt/cost-price-rounding-logic-diverges-on-computed-prices-api.md
index ac1d7d6de..74fe5c017 100644
--- a/docs/known-issues/pt/cost-price-rounding-logic-diverges-on-computed-prices-api.md
+++ b/docs/known-issues/pt/cost-price-rounding-logic-diverges-on-computed-prices-api.md
@@ -18,9 +18,7 @@ internalReference: 842336
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a API de preços computados tem uma propriedade chamada "preço de custo" que, em cenários específicos, pode mostrar uma diferença de 1 centavo entre seu valor na interface do usuário e a API de preços computados https://developers.vtex.com/docs/api-reference/pricing-api#get-/pricing/prices/-itemId-/computed/-priceTableId-
diff --git a/docs/known-issues/pt/country-field-as-null-in-invoicedata.md b/docs/known-issues/pt/country-field-as-null-in-invoicedata.md
index 7b6d91b41..e6115cc53 100644
--- a/docs/known-issues/pt/country-field-as-null-in-invoicedata.md
+++ b/docs/known-issues/pt/country-field-as-null-in-invoicedata.md
@@ -18,9 +18,7 @@ internalReference: 382175
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O campo Country em invoiceData pode ser nulo se for enviado via API ou se houver um endereço de fatura no Profile System com o país como nulo, portanto, os pedidos serão criados com dados incompletos em invoiceData.
diff --git a/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md b/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
index fae00a652..1403411d7 100644
--- a/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
+++ b/docs/known-issues/pt/country-selector-for-billing-address-while-in-international-mode-stays-restricted-to-the-delivery-countries.md
@@ -18,9 +18,7 @@ internalReference: 335581
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/coupon-usage-not-restored-for-incomplete-orders.md b/docs/known-issues/pt/coupon-usage-not-restored-for-incomplete-orders.md
index 1b1292e33..b6a47ea5d 100644
--- a/docs/known-issues/pt/coupon-usage-not-restored-for-incomplete-orders.md
+++ b/docs/known-issues/pt/coupon-usage-not-restored-for-incomplete-orders.md
@@ -18,9 +18,7 @@ internalReference: 639418
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md b/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md
index f54c18d57..2a3409806 100644
--- a/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md
+++ b/docs/known-issues/pt/coupons-created-as-archived-temporarrily.md
@@ -18,9 +18,7 @@ internalReference: 892041
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando um cupom é criado, a interface do usuário/API mostra que ele está arquivado por alguns minutos (~2) quando, na verdade (no banco de dados de preços), o cupom está ativo.
diff --git a/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md b/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md
index 643e7de07..5c1a5f182 100644
--- a/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md
+++ b/docs/known-issues/pt/create-product-api-doesnt-send-nulls-as-release-date-values.md
@@ -18,9 +18,7 @@ internalReference: 1024207
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar as APIs de criação ou atualização de produtos no aplicativo de catálogo: https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/product e enviar o campo releaseDate como nulo, em seu valor, ele é criado com a data atual.
diff --git a/docs/known-issues/pt/create-seller-with-additional-information-is-returning-an-error.md b/docs/known-issues/pt/create-seller-with-additional-information-is-returning-an-error.md
index 8670ac30a..1f7db614b 100644
--- a/docs/known-issues/pt/create-seller-with-additional-information-is-returning-an-error.md
+++ b/docs/known-issues/pt/create-seller-with-additional-information-is-returning-an-error.md
@@ -18,9 +18,7 @@ internalReference: 741110
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md b/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
index 31f2a3267..0400d7dc3 100644
--- a/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
+++ b/docs/known-issues/pt/creating-a-regionalized-sales-channel-with-an-already-used-binding-does-not-update-the-items-stockbalance.md
@@ -18,9 +18,7 @@ internalReference: 1005112
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para contas regionalizadas, o sistema de índice filtra, pelos canais de vendas regionalizados, o saldo de estoque que deve aparecer, para não mostrar vínculos de vendas que não são regionalizados.
diff --git a/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md b/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
index 99177cde5..7143db1f0 100644
--- a/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
+++ b/docs/known-issues/pt/creating-and-deleting-a-large-number-of-redirects-breaks-the-redirects-page.md
@@ -18,9 +18,7 @@ internalReference: 1010392
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Lidar com uma grande quantidade de redirecionamentos pode quebrar a página da interface do usuário. Se você tiver muitos redirecionamentos ou precisar excluir essa grande quantidade, isso poderá levar a um erro em que a página da interface do usuário estará sempre carregando e nunca retornará as informações dos redirecionamentos. Achamos que isso pode acontecer porque, quando excluímos uma grande quantidade de redirecionamentos, as primeiras páginas da consulta `listRedirects` ficam em branco e a interface do usuário procura essas primeiras páginas para carregar os primeiros redirecionamentos e nunca as encontra.
diff --git a/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md b/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
index b2b0de365..aac4be063 100644
--- a/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
+++ b/docs/known-issues/pt/creating-wrong-redirects-containing-charactersqueries-that-shouldnt-be-uploaded-the-uploaddownload-of-the-csv-through-the-cli-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference: 971936
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Após criar redirecionamentos incorretos contendo caracteres que não devem ser carregados, ou seja, #, consultas ou redirecionamentos que devem ser criados no nível do servidor, o upload/download em massa do csv por meio da CLI não funciona mais: #, consultas ou redirecionamentos que devem ser criados no nível do servidor, o upload/download em massa do csv por meio da CLI não funciona mais.
diff --git a/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md b/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md
index 5ade64065..2d7156fd3 100644
--- a/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md
+++ b/docs/known-issues/pt/criteria-composition-is-not-returned-on-the-explained-search-ui.md
@@ -18,9 +18,7 @@ internalReference: 852898
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você pesquisa um termo cuja resposta é apenas um produto, esse produto não terá a composição de critérios exibida na tela da pesquisa explicada.
diff --git a/docs/known-issues/pt/cultureinfo-does-not-allow-values-longer-than-10-characters.md b/docs/known-issues/pt/cultureinfo-does-not-allow-values-longer-than-10-characters.md
index 35ca601d9..42f103119 100644
--- a/docs/known-issues/pt/cultureinfo-does-not-allow-values-longer-than-10-characters.md
+++ b/docs/known-issues/pt/cultureinfo-does-not-allow-values-longer-than-10-characters.md
@@ -18,9 +18,7 @@ internalReference: 667652
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o campo CultureInfo no registro da política comercial tem uma limitação para valores de 10 caracteres, isto faz com que valores maiores que este gerem um erro SWW ao salvar a política.
diff --git a/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md b/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md
index 2d573f4fd..6129f19b6 100644
--- a/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md
+++ b/docs/known-issues/pt/currency-symbol-does-not-follow-admin-language.md
@@ -18,9 +18,7 @@ internalReference: 1000915
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário acessa a tela de configuração do carrinho na área de pedidos (`https://{accountname}}.myvtex.com/admin/checkout/#/configurations )` o símbolo da moeda segue as convenções da localidade indicada pelo administrador, a troca desse símbolo é feita sempre que o administrador indica uma localidade diferente, porém de acordo com nossa análise essa troca está falhando em determinados momentos, fazendo com que o símbolo da moeda indicada seja o padrão da página que nesse caso é R$.
diff --git a/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md b/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md
index a535016d4..25ee0997b 100644
--- a/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md
+++ b/docs/known-issues/pt/custom-attribute-mapper-mercado-livre.md
@@ -18,9 +18,7 @@ internalReference: 521197
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md b/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
index 0eb2cd3bc..79352db65 100644
--- a/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
+++ b/docs/known-issues/pt/custom-elements-on-legacy-cms-not-working-with-more-than-one-html.md
@@ -18,9 +18,7 @@ internalReference: 871480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar um elemento personalizado com mais de um elemento HTML, somente o primeiro é carregado no modelo.
diff --git a/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md b/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
index 49ed8b57d..c5af3c3df 100644
--- a/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
+++ b/docs/known-issues/pt/custom-video-thumbnail-image-is-not-displayed-on-mobile-version.md
@@ -18,9 +18,7 @@ internalReference: 412632
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O carregamento de uma imagem em miniatura para um bloco de vídeo só a atualiza para a versão desktop, a miniatura móvel se mantém vazia.
diff --git a/docs/known-issues/pt/customer-credit-doesnt-show-installments-correctly.md b/docs/known-issues/pt/customer-credit-doesnt-show-installments-correctly.md
index c58656073..fbcd09aea 100644
--- a/docs/known-issues/pt/customer-credit-doesnt-show-installments-correctly.md
+++ b/docs/known-issues/pt/customer-credit-doesnt-show-installments-correctly.md
@@ -18,9 +18,7 @@ internalReference: 501730
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 O crédito do cliente não exibe os diferentes valores entre regras com o mesmo número de parcelas e períodos diferentes. Para entender melhor este problema, devemos observar a porta de entrada e o comportamento do crédito do cliente:
 
diff --git a/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md b/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
index fc36411f9..41744e81b 100644
--- a/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
+++ b/docs/known-issues/pt/customer-credit-invoices-status-at-mycredits-page-are-not-correct.md
@@ -18,9 +18,7 @@ internalReference: 369457
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O status da fatura na MyCredits UI das lojas espanholas não são exibidos como deveriam, eles estão mostrando os nomes dos componentes em vez de "cancelado", "expirado", "pago" ou "aberto".
diff --git a/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md b/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md
index 49e07349d..c02fec782 100644
--- a/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md
+++ b/docs/known-issues/pt/customer-credit-total-due-value-updating-according-to-the-pagination.md
@@ -18,9 +18,7 @@ internalReference: 432587
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O valor "Total devido" em uma conta de Crédito ao Cliente não está mostrando o valor total, mas sim o valor total na paginação atual da IU
diff --git a/docs/known-issues/pt/customer-credits-invoice-list-cannot-be-exported.md b/docs/known-issues/pt/customer-credits-invoice-list-cannot-be-exported.md
index 7ab4eab19..545002728 100644
--- a/docs/known-issues/pt/customer-credits-invoice-list-cannot-be-exported.md
+++ b/docs/known-issues/pt/customer-credits-invoice-list-cannot-be-exported.md
@@ -18,9 +18,7 @@ internalReference: 327219
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há uma limitação com o módulo de Crédito ao Cliente que não permite ao usuário exportar mais de 150k faturas ao mesmo tempo.
diff --git a/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md b/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
index 3e94b035e..71e0edcef 100644
--- a/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
+++ b/docs/known-issues/pt/customer-information-being-lost-when-it-has-some-order-with-profileerroronloading.md
@@ -18,9 +18,7 @@ internalReference: 340036
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o pedido tem "profileErrorOnLoading=true", o comportamento esperado é que o perfil do cliente, o endereço e o cartão de crédito não sejam salvos/atualizados no Profile System.
diff --git a/docs/known-issues/pt/customer-information-being-removed-from-profile-system-without-clear-reason.md b/docs/known-issues/pt/customer-information-being-removed-from-profile-system-without-clear-reason.md
index b7b470a8c..4ad60422b 100644
--- a/docs/known-issues/pt/customer-information-being-removed-from-profile-system-without-clear-reason.md
+++ b/docs/known-issues/pt/customer-information-being-removed-from-profile-system-without-clear-reason.md
@@ -18,9 +18,7 @@ internalReference: 469823
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes recebemos relatórios onde as informações do cliente foram removidas das entidades CL e AD da Master Data, que podem ser gerenciadas de várias maneiras - uso direto da Master Data pela própria loja (UI, API, importação/exportação de dados) e outras integrações internas da plataforma, como o serviço CHK através do Sistema de Perfil.
diff --git a/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md b/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md
index a08d98a72..112e4567c 100644
--- a/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md
+++ b/docs/known-issues/pt/customer-information-is-not-saved-in-the-profile-system.md
@@ -18,9 +18,7 @@ internalReference: 784763
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, as informações de um novo cliente não são salvas no Profile System.
diff --git a/docs/known-issues/pt/customers-cant-see-products-catalog-page-after-logging-in.md b/docs/known-issues/pt/customers-cant-see-products-catalog-page-after-logging-in.md
index 0fef5612d..d4ed536db 100644
--- a/docs/known-issues/pt/customers-cant-see-products-catalog-page-after-logging-in.md
+++ b/docs/known-issues/pt/customers-cant-see-products-catalog-page-after-logging-in.md
@@ -18,19 +18,13 @@ internalReference: 550112
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md b/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
index d700008ea..3195707a6 100644
--- a/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
+++ b/docs/known-issues/pt/customized-cluster-expression-not-working-on-free-shipping-promotion-default-saleschannel-1.md
@@ -18,9 +18,7 @@ internalReference: 334027
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, as expressões de cluster personalizadas não estão trabalhando em promoções do tipo envio gratuito.
diff --git a/docs/known-issues/pt/cvv-without-validation-of-characters-type.md b/docs/known-issues/pt/cvv-without-validation-of-characters-type.md
index 0dc52990e..15840721b 100644
--- a/docs/known-issues/pt/cvv-without-validation-of-characters-type.md
+++ b/docs/known-issues/pt/cvv-without-validation-of-characters-type.md
@@ -18,9 +18,7 @@ internalReference: 425204
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No checkout, pedimos informações de cartão de crédito e permitimos apenas que o cliente digite números no campo Número do Cartão, apenas letras no campo Nome do Proprietário do Cartão. Entretanto, não fazemos uma validação semelhante para o campo CVV, permitindo que o cliente digite letras neste campo
diff --git a/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md b/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
index 704b43cd2..6d754c2f9 100644
--- a/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
+++ b/docs/known-issues/pt/dafiti-orders-that-are-in-awaiting-authorization-to-dispatch-at-vtex-but-are-still-paymentpending-at-dafiti.md
@@ -18,9 +18,7 @@ internalReference: 719606
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ordens que estão em `"Aguardando Autorização para Despachar" `na VTEX, mas que ainda estão `"pagando_dependendo" `na Dafiti.
diff --git a/docs/known-issues/pt/dafiti-quality-dafiti-images.md b/docs/known-issues/pt/dafiti-quality-dafiti-images.md
index 0033f6677..3120b05a2 100644
--- a/docs/known-issues/pt/dafiti-quality-dafiti-images.md
+++ b/docs/known-issues/pt/dafiti-quality-dafiti-images.md
@@ -18,9 +18,7 @@ internalReference: 675317
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A imagem perde qualidade quando chega à Dafiti.
diff --git a/docs/known-issues/pt/daily-metrics-on-search-report-showing-duplicated-date.md b/docs/known-issues/pt/daily-metrics-on-search-report-showing-duplicated-date.md
index 768088479..a430eaceb 100644
--- a/docs/known-issues/pt/daily-metrics-on-search-report-showing-duplicated-date.md
+++ b/docs/known-issues/pt/daily-metrics-on-search-report-showing-duplicated-date.md
@@ -18,9 +18,7 @@ internalReference: 508883
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um relatório de busca é baixado, a tabela contendo métricas como buscas, cliques e cliques únicos no final do relatório contém uma coluna de datas mostrando entradas duplicadas sem uma razão aparente, como você pode ver na imagem:
diff --git a/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md b/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md
index 22b83c782..79e5cd2cd 100644
--- a/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md
+++ b/docs/known-issues/pt/deactivated-payment-system-rendering-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 1049543
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O problema parece ocorrer apenas em subcontas, mesmo desativado (também excluído) o método de pagamento é renderizado no checkout
diff --git a/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md b/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md
index 1b3e33d1e..560366c5e 100644
--- a/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md
+++ b/docs/known-issues/pt/deadlocked-error-when-using-catalog-apis.md
@@ -18,9 +18,7 @@ internalReference: 862626
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O uso constante de algumas APIs de catálogo, como "Add SKU to Subcollection" (Adicionar SKU à subcoleção) ou a tentativa de vincular produtos por meio do módulo de sugestões pode causar erros de bloqueio para o comerciante.
diff --git a/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md b/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
index e50ea71dd..96e51dbd6 100644
--- a/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
+++ b/docs/known-issues/pt/debit-payments-using-firstdata-connector-cannot-be-settled-due-to-an-error-in-the-transactionstate-field.md
@@ -18,9 +18,7 @@ internalReference: 461095
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao utilizar o conector Firstdata para processar pagamentos de débito, nosso código foi projetado para esperar que o campo TransactionState seja definido como "CAPTURED". No entanto, encontramos um problema em que o provedor está enviando os valores "CAPTURED" e "SETTLED", o que está causando um erro:
diff --git a/docs/known-issues/pt/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md b/docs/known-issues/pt/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md
index 6174598ae..f6034c2a4 100644
--- a/docs/known-issues/pt/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md
+++ b/docs/known-issues/pt/decidirv1-connectors-inconsistent-rounding-method-for-csptgrandtotalamount-and-csittotalamount-fields.md
@@ -18,9 +18,7 @@ internalReference: 787367
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O conector DecidirV1 antigo utiliza um método interno para calcular os campos `CSPTGRANDTOTALAMOUNT` e `CSITTOTALAMOUNT`, que é o produto entre o valor e a quantidade do produto. Esta abordagem resulta em uma cadeia com duas casas decimais. Consequentemente, quando o preço do produto contém mais de duas casas decimais, o valor do campo `CSPTGRANDTOTALAMOUNT` diverge, pois é o próprio valor do pagamento.
diff --git a/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md b/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
index 7966b9c6a..4ade6ee60 100644
--- a/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
+++ b/docs/known-issues/pt/decidirv1-transaction-got-reprocessed-after-some-retries-to-authorization.md
@@ -18,9 +18,7 @@ internalReference: 384009
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Isto acontece quando uma transação recebe o status 480 que significa "REVIEW", e começa a tentar novamente até receber uma carga útil nula. Então, depois disso, "reprocessamos" a transação que causa uma falha e um cancelamento.
diff --git a/docs/known-issues/pt/default-value-on-specification-only-working-when-creating-products-through-admin.md b/docs/known-issues/pt/default-value-on-specification-only-working-when-creating-products-through-admin.md
index db59b3583..87225f7f3 100644
--- a/docs/known-issues/pt/default-value-on-specification-only-working-when-creating-products-through-admin.md
+++ b/docs/known-issues/pt/default-value-on-specification-only-working-when-creating-products-through-admin.md
@@ -18,9 +18,7 @@ internalReference: 550097
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar uma especificação em uma Categoria VTEX você pode configurar um valor padrão que será preenchido quando o sku/produto for criado sem esta informação.
diff --git a/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md b/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
index 6ae452d43..edc811984 100644
--- a/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
+++ b/docs/known-issues/pt/delay-in-processing-the-shipping-policy-locked-in-processing-status.md
@@ -18,9 +18,7 @@ internalReference: 396914
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao carregar uma planilha e depois clicar em "salvar mudanças" nas configurações da política de expedição, a planilha precisa ser processada por nosso módulo de Logística. O tempo de processamento pode variar de acordo com o tamanho do arquivo, mas normalmente leva alguns minutos. Em alguns casos, o tempo de processamento pode levar até algumas horas ou até dias, e o status permanece bloqueado no "processamento".
diff --git a/docs/known-issues/pt/delay-to-register-cancelreason-in-the-order-json.md b/docs/known-issues/pt/delay-to-register-cancelreason-in-the-order-json.md
index 87fc8b74c..3385e52eb 100644
--- a/docs/known-issues/pt/delay-to-register-cancelreason-in-the-order-json.md
+++ b/docs/known-issues/pt/delay-to-register-cancelreason-in-the-order-json.md
@@ -18,9 +18,7 @@ internalReference: 792650
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido à forma como o fluxo de atualização do pedido é executado de qualquer status a ser cancelado, é possível que o sistema de Pedido demore um pouco para registrar o CancelReason na ordem json, causando um breve cenário de inconsistência se o Json for consultado ou usado alguns segundos após a ação de cancelamento;
diff --git a/docs/known-issues/pt/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md b/docs/known-issues/pt/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md
index 94af5899f..32682d090 100644
--- a/docs/known-issues/pt/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md
+++ b/docs/known-issues/pt/delaytoautosettleafterantifraud-triggering-automatic-capture-even-without-antifraud.md
@@ -18,9 +18,7 @@ internalReference: 369633
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a transação **NÃO** possui antifraude, ela assume o menor valor entre `delayToAutoSettle` e `delayToAutoSettleAfterAntifraud`. Nesse caso, o `EarlySettlementWorker` é responsável pela captura, que é o worker para captura antecipada. Tecnicamente, é o worker que é chamado após a execução da antifraude, mas quando não há uma, ele inicia sua contagem regressiva após a autorização de pagamento.
diff --git a/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md b/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
index 55df12047..283a67fbb 100644
--- a/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
+++ b/docs/known-issues/pt/deleted-customer-credit-rules-will-appear-at-checkout-if-not-deactivated-previously.md
@@ -18,9 +18,7 @@ internalReference: 994066
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se você tiver o aplicativo `vtex.custom-payments` instalado e excluir uma regra de pagamento de crédito do cliente sem desativá-la primeiro, ela será processada no checkout.
diff --git a/docs/known-issues/pt/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md b/docs/known-issues/pt/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md
index e8a90e8f3..b20072e74 100644
--- a/docs/known-issues/pt/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md
+++ b/docs/known-issues/pt/deleting-collections-on-the-new-admin-is-not-reindexing-the-products.md
@@ -18,9 +18,7 @@ internalReference: 490740
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, se você tiver uma coleção criada inteiramente ou na nova/legacy (CMS) Collections admin, eliminando-a via UI não reindexará os produtos nela contidos, conseqüentemente não os removerá efetivamente da coleção.
diff --git a/docs/known-issues/pt/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md b/docs/known-issues/pt/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md
index b1c7ccd7c..8a28ab377 100644
--- a/docs/known-issues/pt/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md
+++ b/docs/known-issues/pt/delivery-capacity-as-zero-orders-allowing-schedule-carrier-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 471612
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md b/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
index ccfe96344..2d44be2e6 100644
--- a/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
+++ b/docs/known-issues/pt/delivery-capacity-is-not-respected-if-there-is-space-in-the-id-of-shipping-policy.md
@@ -18,9 +18,7 @@ internalReference: 862830
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se o recurso de agendamento de entrega estiver em uso e a capacidade de entrega estiver ativada, há dois cenários conhecidos que podem tornar a janela disponível mesmo depois de ter atingido o limite máximo de capacidade configurado.
diff --git a/docs/known-issues/pt/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md b/docs/known-issues/pt/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md
index 440b9afaf..1a12e0824 100644
--- a/docs/known-issues/pt/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md
+++ b/docs/known-issues/pt/delivery-flag-in-my-orders-due-to-an-error-in-filling-the-invoice.md
@@ -18,9 +18,7 @@ internalReference: 547053
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md b/docs/known-issues/pt/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md
index b7345d107..6efaafbac 100644
--- a/docs/known-issues/pt/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md
+++ b/docs/known-issues/pt/delivery-method-selector-disappears-in-specific-flow-when-there-is-only-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 296786
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O seletor de data/hora para entrega programada desaparece quando o usuário muda de "pegar" para "receber", este comportamento ocorre independentemente do uso do recurso de envio enxuto.
diff --git a/docs/known-issues/pt/delivery-method-selector-does-not-appear-in-some-scenarios.md b/docs/known-issues/pt/delivery-method-selector-does-not-appear-in-some-scenarios.md
index ade7c5100..dc0fcee01 100644
--- a/docs/known-issues/pt/delivery-method-selector-does-not-appear-in-some-scenarios.md
+++ b/docs/known-issues/pt/delivery-method-selector-does-not-appear-in-some-scenarios.md
@@ -18,9 +18,7 @@ internalReference: 293784
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As lojas que têm opções de entrega programada podem ter um mau funcionamento em relação à seleção do método de entrega. Isto pode acontecer com ou sem o uso do Envio Lean.
diff --git a/docs/known-issues/pt/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md b/docs/known-issues/pt/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md
index 336d54394..dd11a2714 100644
--- a/docs/known-issues/pt/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md
+++ b/docs/known-issues/pt/delivery-schedule-date-getting-empty-when-item-is-a-gift-added.md
@@ -18,9 +18,7 @@ internalReference: 586143
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md b/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md
index 277359696..1022c0181 100644
--- a/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md
+++ b/docs/known-issues/pt/delivery-split-with-lean-shipping-offering-invalid-sla.md
@@ -18,9 +18,7 @@ internalReference: 990155
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um carrinho de compras inclui produtos de diferentes vendedores, com diferentes canais de entrega e IDs de SLA entre eles, a interface do usuário do Checkout ativa o Lean Shipping, resumindo os SLAs disponíveis para exibir apenas as opções "mais rápida" e "mais barata" para cada item.
diff --git a/docs/known-issues/pt/deliverycontracttype-problem-b2w.md b/docs/known-issues/pt/deliverycontracttype-problem-b2w.md
index 7c482c3d8..eebb54bee 100644
--- a/docs/known-issues/pt/deliverycontracttype-problem-b2w.md
+++ b/docs/known-issues/pt/deliverycontracttype-problem-b2w.md
@@ -18,9 +18,7 @@ internalReference: 605908
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md b/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md
index 99a630cde..aa18b8f8b 100644
--- a/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md
+++ b/docs/known-issues/pt/departments-name-not-loading-on-seller-management-commissions-ui.md
@@ -18,9 +18,7 @@ internalReference: 1005799
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao selecionar um departamento para definir uma comissão específica no gerenciamento de vendedores, a tabela não está carregando o nome do departamento. O comportamento não ocorre em categorias secundárias.
diff --git a/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md b/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md
index 652de59a9..7874af0e8 100644
--- a/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md
+++ b/docs/known-issues/pt/diacritics-are-removed-on-catalogapi.md
@@ -18,9 +18,7 @@ internalReference: 623345
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md b/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md
index d8caa3102..6d5ff9f7c 100644
--- a/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md
+++ b/docs/known-issues/pt/difference-in-prices-between-pdp-plp-and-checkout-cart.md
@@ -18,9 +18,7 @@ internalReference: 853175
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md b/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md
index 6f9a478b1..862edcb10 100644
--- a/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md
+++ b/docs/known-issues/pt/differences-between-specification-value-on-apis-and-portal.md
@@ -18,9 +18,7 @@ internalReference: 853184
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md b/docs/known-issues/pt/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md
index 7038b8dad..1dbd70885 100644
--- a/docs/known-issues/pt/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md
+++ b/docs/known-issues/pt/different-payment-value-when-mixing-the-types-of-sellers-for-the-same-seller-in-a-cart.md
@@ -18,9 +18,7 @@ internalReference: 821741
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nos casos em que um vendedor atua como vendedor de marca branca e como vendedor regular para itens diferentes no mesmo carrinho, o valor do pagamento será duplicado com o valor do frete.
diff --git a/docs/known-issues/pt/dimension-text-fields-being-unselected-during-sku-creation.md b/docs/known-issues/pt/dimension-text-fields-being-unselected-during-sku-creation.md
index 7858b2b50..9244ee3bb 100644
--- a/docs/known-issues/pt/dimension-text-fields-being-unselected-during-sku-creation.md
+++ b/docs/known-issues/pt/dimension-text-fields-being-unselected-during-sku-creation.md
@@ -18,9 +18,7 @@ internalReference: 786048
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar uma SKU da Admin, é necessário registrar as dimensões para o transporte e as dimensões reais. Entretanto, ao preencher um dos campos de texto e clicar (ou usar a tecla tab) para preencher outro, este campo não está selecionado e é necessário clicar novamente no campo de texto para poder inserir/editar o valor.
diff --git a/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md b/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
index fc2ee810c..f46064350 100644
--- a/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
+++ b/docs/known-issues/pt/disclosure-layout-cant-be-used-properly-when-prop-animated-is-set-as-true.md
@@ -18,9 +18,7 @@ internalReference: 417947
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um problema no layout de divulgação que só está desencadeando o bloco a ser mostrado, mas não está fechando. Isto é causado pelo propulsor animado, que não está funcionando corretamente quando definido no layout de divulgação e não permite esconder o elemento após a abertura.
diff --git a/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md b/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
index 31bce83a0..3a52cff87 100644
--- a/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
+++ b/docs/known-issues/pt/discrepancy-on-coupon-usage-count-on-oms-and-coupons-ui.md
@@ -18,9 +18,7 @@ internalReference: 954959
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns pedidos não estão sendo recuperados no uso dos cupons, identificamos que alguns pedidos não estavam sendo contados pelo administrador de cupons.
diff --git a/docs/known-issues/pt/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md b/docs/known-issues/pt/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md
index b2e32b2c7..37ccb66fa 100644
--- a/docs/known-issues/pt/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md
+++ b/docs/known-issues/pt/divergence-between-the-total-value-of-each-product-and-the-subtotal-of-items-or-totalizers.md
@@ -18,9 +18,7 @@ internalReference: 331188
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Em alguns casos, o valor total da encomenda difere da soma do valor total dos produtos (adicionando também o custo de envio e possíveis descontos, se existirem). Isto acontece porque o valor apresentado para os artigos faz parte do "preço de venda", uma informação da orderForm de encomenda que perde precisão devido a razões de arredondamento.
 
diff --git a/docs/known-issues/pt/divergence-delivery-time-netshoes.md b/docs/known-issues/pt/divergence-delivery-time-netshoes.md
index 3658f1866..25c589950 100644
--- a/docs/known-issues/pt/divergence-delivery-time-netshoes.md
+++ b/docs/known-issues/pt/divergence-delivery-time-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 635509
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md b/docs/known-issues/pt/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md
index c335be2c9..d211a2b70 100644
--- a/docs/known-issues/pt/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md
+++ b/docs/known-issues/pt/divergence-in-kit-weight-after-calculations-involving-decimals-in-weight.md
@@ -18,9 +18,7 @@ internalReference: 657186
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em certos casos envolvendo kits, a política de embarque pode não estar disponível, isto pode acontecer devido à lógica usada para os cálculos que envolvem o peso.
diff --git a/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md b/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
index 66f26fd83..225b8e96e 100644
--- a/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
+++ b/docs/known-issues/pt/divergence-on-the-advanced-store-settings-on-new-accounts-or-workspaces.md
@@ -18,9 +18,7 @@ internalReference: 1064235
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em novos espaços de trabalho ou contas que nunca alteraram as configurações avançadas das Configurações da loja, é possível verificar uma inconsistência entre as informações na interface do usuário e o sinalizador aplicado à conta.
diff --git a/docs/known-issues/pt/divergence-rule-dafiti.md b/docs/known-issues/pt/divergence-rule-dafiti.md
index c62eb10e6..56f3f1c39 100644
--- a/docs/known-issues/pt/divergence-rule-dafiti.md
+++ b/docs/known-issues/pt/divergence-rule-dafiti.md
@@ -18,9 +18,7 @@ internalReference: 594648
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/divergencia-shipping-estimate-b2w.md b/docs/known-issues/pt/divergencia-shipping-estimate-b2w.md
index 0f3b8b9e6..075af7cda 100644
--- a/docs/known-issues/pt/divergencia-shipping-estimate-b2w.md
+++ b/docs/known-issues/pt/divergencia-shipping-estimate-b2w.md
@@ -18,9 +18,7 @@ internalReference: 642448
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md b/docs/known-issues/pt/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md
index f4d829226..508670eb5 100644
--- a/docs/known-issues/pt/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md
+++ b/docs/known-issues/pt/divergency-in-apportioned-freight-values-per-item-between-chk-and-ffm-orders.md
@@ -18,9 +18,7 @@ internalReference: 321111
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns casos, os valores de remessa repartidos por item entre o mercado (lado do checkout) e o vendedor (lado do cumprimento) os pedidos podem ser divergentes.
diff --git a/docs/known-issues/pt/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md b/docs/known-issues/pt/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md
index a44d19838..c3cdc433c 100644
--- a/docs/known-issues/pt/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md
+++ b/docs/known-issues/pt/divergent-order-value-between-marketplace-and-seller-while-using-price-override-and-promotions.md
@@ -18,9 +18,7 @@ internalReference: 756629
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o preço do item vendido _minus_ descontos de mercado tem um valor negativo, ele não pode ser aplicado ao item (eles não podem ter um preço negativo), então será considerado como zero e mexerá com outros cálculos. Isso acontece quando o mercado está usando o recurso de substituição do preço do vendedor, gerando valores maiores do que a própria conta do vendedor, e depois combinando com uma promoção.
diff --git a/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md b/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md
index 3f4f6d553..73268a87c 100644
--- a/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md
+++ b/docs/known-issues/pt/divergent-status-on-the-transaction-list-and-on-the-transaction.md
@@ -18,9 +18,7 @@ internalReference: 308919
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O status das transações é diferente quando você as abre em comparação com o que é mostrado na lista de transações.
diff --git a/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md b/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
index 2fefa9579..2dcb1007d 100644
--- a/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
+++ b/docs/known-issues/pt/divergent-value-while-mixing-paymentsystemtocheckfirstinstallment-configuration-and-splitted-items.md
@@ -18,9 +18,7 @@ internalReference: 766454
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a conta tiver configurado "paymentSystemToCheckFirstInstallment" em OrderForm Configuration, o cálculo de checkout enviará dois pedidos ao módulo de promoções. Se houver itens divididos no carrinho (por exemplo, Mais para menos promoção), a primeira solicitação enviará os itens corretamente, mas a segunda enviará os itens divididos com base na aplicação da promoção.
diff --git a/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md b/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
index 73e44d7c7..d037e6654 100644
--- a/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
+++ b/docs/known-issues/pt/document-number-field-rut-randomly-getting-last-digit-deleted-on-ios.md
@@ -18,9 +18,7 @@ internalReference: 921944
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Somente no Safari/iOS, ao preencher o número do documento e percorrer os campos de dados do cliente, o campo do número do documento (RUT) terá o último dígito excluído.
diff --git a/docs/known-issues/pt/drag-and-drop-issue-on-site-editor.md b/docs/known-issues/pt/drag-and-drop-issue-on-site-editor.md
index 26af005c8..f910dcc22 100644
--- a/docs/known-issues/pt/drag-and-drop-issue-on-site-editor.md
+++ b/docs/known-issues/pt/drag-and-drop-issue-on-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 685103
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os clientes não podem usar o recurso de arrastar e soltar no editor do site para carregar imagens, isto provavelmente ocorre em conjunto com nossa nova implementação de nosso novo Gerenciamento de Mídia CMS.
diff --git a/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md b/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
index 1d417cdbe..169d83a64 100644
--- a/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
+++ b/docs/known-issues/pt/duplicated-entries-for-categoriesspecification-values-on-the-same-level.md
@@ -18,9 +18,7 @@ internalReference: 562588
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md b/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md
index 0420a7ba8..8d86c072c 100644
--- a/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md
+++ b/docs/known-issues/pt/duplicated-organizations-in-modal-to-switch-between-organizations.md
@@ -18,9 +18,7 @@ internalReference: 986868
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário tem muitas organizações registradas e usa o modal para alternar entre organizações, algumas organizações serão mostradas duplicadas na lista.
diff --git a/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md b/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
index 707e344d7..2cc0a6de6 100644
--- a/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
+++ b/docs/known-issues/pt/ean-field-as-string-being-ignored-when-approved-on-received-skus.md
@@ -18,9 +18,7 @@ internalReference: 897301
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O vendedor envia o sku com todos os campos declarados neste artigo (https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-) para o marketplace aprovar no módulo Received Skus.
diff --git a/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md b/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
index f4bceb23f..2a09e479e 100644
--- a/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
+++ b/docs/known-issues/pt/early-capture-wrongfully-competing-with-automatic-capture-on-authorizedotnet.md
@@ -18,9 +18,7 @@ internalReference: 866068
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para que possamos entender esse comportamento, primeiro precisamos compreender a diferença entre captura automática e captura antecipada:
diff --git a/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md b/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
index 210cb95f2..b4c395217 100644
--- a/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
+++ b/docs/known-issues/pt/elos-card-brand-transactions-with-erederest-are-not-respecting-early-capture.md
@@ -18,9 +18,7 @@ internalReference: 350814
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para transações com a marca de cartão Elo, a configuração de captura antecipada não está sendo respeitada, e a transação está sendo capturada imediatamente após a aprovação.
diff --git a/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md b/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md
index 5afd8b1f5..0d34e2f9e 100644
--- a/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md
+++ b/docs/known-issues/pt/email-not-autofilling-for-new-buyers-after-logging-in.md
@@ -18,9 +18,7 @@ internalReference: 920634
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um novo comprador faz login e prossegue com o checkout, o e-mail não é preenchido automaticamente, exigindo que o cliente insira novamente o e-mail. Isso também acontece com o uso de APIs e o envio de cabeçalhos com os cookies do comprador.
diff --git a/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md b/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md
index dbc374bbc..4d7a2da44 100644
--- a/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md
+++ b/docs/known-issues/pt/email-not-autofilling-for-new-users-on-checkoutui.md
@@ -18,9 +18,7 @@ internalReference: 887949
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um novo usuário insere um novo e-mail na etapa de e-mail e prossegue para a próxima página, no componente de dados do cliente, o e-mail não é preenchido automaticamente.
diff --git a/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md b/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
index 6b6843704..d4de605bd 100644
--- a/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
+++ b/docs/known-issues/pt/emails-with-sales-roles-are-not-allowed-to-impersonate-using-the-b2b-organizations-feature.md
@@ -18,9 +18,7 @@ internalReference: 910328
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se os e-mails tiverem alguma função de vendas associada, eles não terão permissão para se passar por outra pessoa usando o recurso Organizações B2B.
diff --git a/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md b/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
index 90a89107f..a6cf1074d 100644
--- a/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
+++ b/docs/known-issues/pt/encoding-issues-for-specific-characters-leads-to-unexpected-product-search.md
@@ -18,9 +18,7 @@ internalReference: 1022550
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um problema de codificação pode afetar as pesquisas com caracteres especiais quando eles são indicados por meio do parâmetro "query", levando a resultados de pesquisa incorretos.
diff --git a/docs/known-issues/pt/erederest-only-allows-cancelation-when-the-status-code-is-359.md b/docs/known-issues/pt/erederest-only-allows-cancelation-when-the-status-code-is-359.md
index 5173e655b..9c34161d0 100644
--- a/docs/known-issues/pt/erederest-only-allows-cancelation-when-the-status-code-is-359.md
+++ b/docs/known-issues/pt/erederest-only-allows-cancelation-when-the-status-code-is-359.md
@@ -18,9 +18,7 @@ internalReference: 740084
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nosso conector legado ERedeRest executa um cancelamento através de uma solicitação ao fornecedor e espera um statusCode=359, o que significa que o cancelamento foi bem sucedido. Qualquer outro código significa para nosso gateway que o status é indefinido mesmo que, em alguns casos, isso significa que o pedido de reembolso/cancelamento também foi bem sucedido, o que nos levou a tentar novamente o cancelamento, porém ficando presos nesta etapa, uma vez que o cancelamento já foi concluído do lado do provedor.
diff --git a/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md b/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
index 65c21949b..72379a591 100644
--- a/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
+++ b/docs/known-issues/pt/erro-category-xxx-not-found-in-browse-node-mapping-for-skus-department-specification-choose-a-more-specific-global-category-persistente.md
@@ -18,9 +18,7 @@ internalReference: 417639
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ## **Sumário***
 
diff --git a/docs/known-issues/pt/erro-sqlerrm-no-tracking-brinox-b2w.md b/docs/known-issues/pt/erro-sqlerrm-no-tracking-brinox-b2w.md
index dbabc9b70..e9066d817 100644
--- a/docs/known-issues/pt/erro-sqlerrm-no-tracking-brinox-b2w.md
+++ b/docs/known-issues/pt/erro-sqlerrm-no-tracking-brinox-b2w.md
@@ -18,9 +18,7 @@ internalReference: 643287
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md b/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
index 8836c8efa..a076028e5 100644
--- a/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
+++ b/docs/known-issues/pt/error-approving-skus-that-were-rejected-or-reviewed-by-offer-quality.md
@@ -18,9 +18,7 @@ internalReference: 940998
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um sku é reprovado nas regras de Qualidade da Oferta criadas pelo Marketplace, ele vai diretamente para a "Guia Revisão" ou "Guia Rejeitado" dos Skus Recebidos.
diff --git a/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md b/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md
index e6d9c8b35..2a97456a4 100644
--- a/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md
+++ b/docs/known-issues/pt/error-cancelling-customer-credit-invoices.md
@@ -18,9 +18,7 @@ internalReference: 926563
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns casos, as faturas não podem ser canceladas; ao executar a API DELETE, recebemos um erro 500 com a resposta abaixo:
diff --git a/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md b/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
index fd86e892a..5dc90174b 100644
--- a/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
+++ b/docs/known-issues/pt/error-cant-create-search-criteria-error-filter-already-existsbrandid-when-creating-a-promotion-excluding-more-than-1-brand.md
@@ -18,9 +18,7 @@ internalReference: 663698
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar uma promoção, o cliente pode decidir a quais itens a promoção será aplicada.
diff --git a/docs/known-issues/pt/error-closing-customer-credit-account.md b/docs/known-issues/pt/error-closing-customer-credit-account.md
index c24d26a90..48cdd5289 100644
--- a/docs/known-issues/pt/error-closing-customer-credit-account.md
+++ b/docs/known-issues/pt/error-closing-customer-credit-account.md
@@ -18,9 +18,7 @@ internalReference: 904432
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando as contas principais e secundárias têm o aplicativo Customer Credit instalado, a criação de uma creditAccount ocorre em todas elas. Nesse cenário, há casos em que o fechamento da creditAccount não funciona, e o erro a seguir é exibido:
diff --git a/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md b/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md
index b516e9459..e346e5df1 100644
--- a/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md
+++ b/docs/known-issues/pt/error-exporting-entity-with-too-many-documents.md
@@ -18,9 +18,7 @@ internalReference: 857894
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exportação de um grande número de documentos de uma entidade resulta em processamento excessivo, causando erros na fila do processo e impedindo a exportação da lista de documentos.
diff --git a/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md b/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md
index f84f87b25..c1fd0df42 100644
--- a/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md
+++ b/docs/known-issues/pt/error-exporting-large-amount-of-giftcards.md
@@ -18,9 +18,7 @@ internalReference: 550658
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Erro de timeout ao tentar exportar uma grande quantidade de cartões presente, mesmo que o período de consulta seja curto.
diff --git a/docs/known-issues/pt/error-exporting-prices-with-metadata.md b/docs/known-issues/pt/error-exporting-prices-with-metadata.md
index 64ae1b6af..1e068b4ec 100644
--- a/docs/known-issues/pt/error-exporting-prices-with-metadata.md
+++ b/docs/known-issues/pt/error-exporting-prices-with-metadata.md
@@ -18,9 +18,7 @@ internalReference: 860290
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, ao tentar exportar os preços com a opção de metadados ativada e sem usar filtros, pode ocorrer um erro. Ao verificar a mensagem no devTools, aparecerá algo semelhante a "Polly broken circuit on service...".
diff --git a/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md b/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
index 8afcc860a..2691e8150 100644
--- a/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
+++ b/docs/known-issues/pt/error-generating-subscription-order-the-same-item-cannot-have-more-than-one-sla-selected.md
@@ -18,9 +18,7 @@ internalReference: 658185
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em cenários de pedidos de assinatura onde o mesmo item de compra acaba sendo dividido em entradas diferentes, como a compra de 10 unidades do mesmo item sendo apresentada como 7 unidades (A) e 3 unidades (B), o fluxo de execução do ciclo de assinatura pode eventualmente escolher métodos de entrega diferentes entre o item A e B, mesmo que sejam a mesma SKU.
diff --git a/docs/known-issues/pt/error-in-checkout-error-message.md b/docs/known-issues/pt/error-in-checkout-error-message.md
index 4fe8f6c15..484ade942 100644
--- a/docs/known-issues/pt/error-in-checkout-error-message.md
+++ b/docs/known-issues/pt/error-in-checkout-error-message.md
@@ -18,9 +18,7 @@ internalReference: 409895
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando ocorre um erro na afiliação MercadoPagov2 Fluxo de pagamento na página de checkout, os detalhes da mensagem são exibidos sem formatação para acentos e caracteres especiais.
diff --git a/docs/known-issues/pt/error-in-custom-payments-creation.md b/docs/known-issues/pt/error-in-custom-payments-creation.md
index 67d0d55ce..086fe0f3a 100644
--- a/docs/known-issues/pt/error-in-custom-payments-creation.md
+++ b/docs/known-issues/pt/error-in-custom-payments-creation.md
@@ -18,9 +18,7 @@ internalReference: 995110
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os comerciantes podem enfrentar um erro ao criar um pagamento personalizado. Depois de preencher tudo e clicar em salvar, a mensagem "O pagamento personalizado foi configurado com sucesso" aparece, mas a criação realmente falhou (não aparece na interface do usuário).
diff --git a/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
index 5b8303523..c0e21278d 100644
--- a/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/pt/error-in-refund-and-capture-operations-with-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -18,9 +18,7 @@ internalReference: 698005
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido a problemas de arredondamento ao recalcular os destinatários de uma transação com Payout Split, seja na captura ou no reembolso, recebemos a seguinte exceção do gateway, pois a soma do valor do destinatário é diferente do valor da transação.
diff --git a/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md b/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
index 7df765803..94804a75b 100644
--- a/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
+++ b/docs/known-issues/pt/error-in-refund-value-cannot-be-null-parameter-name-value.md
@@ -18,9 +18,7 @@ internalReference: 1049494
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar reembolsar uma transação, pode ocorrer um erro 500 com a mensagem:
diff --git a/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md b/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
index 7a26b67f5..4c26c3e89 100644
--- a/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
+++ b/docs/known-issues/pt/error-in-the-cancellation-process-erederest-and-erede-v2-only-allows-cancelation-when-the-returncode-is-359.md
@@ -18,9 +18,7 @@ internalReference: 740084
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os conectores legados, ERedeRest e E-Rede V2, iniciam os cancelamentos enviando uma solicitação ao provedor e esperam um "returnCode": "359" indicando um cancelamento bem-sucedido. Qualquer outro código é interpretado pelo nosso gateway como um status indefinido, fazendo com que a transação fique presa em um estado de cancelamento. Mesmo que, em alguns casos, a solicitação de reembolso/cancelamento seja bem-sucedida. Isso levou a repetidas tentativas de cancelamento, mesmo quando o cancelamento já havia sido processado pelo provedor.
diff --git a/docs/known-issues/pt/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md b/docs/known-issues/pt/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md
index 45d497051..b990ff062 100644
--- a/docs/known-issues/pt/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md
+++ b/docs/known-issues/pt/error-in-the-maximum-quantity-field-of-the-same-sku-in-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 587394
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a loja configura o campo "quantidade máxima da mesma SKU no carrinho" e é uma ordem proveniente de um mercado, se a quantidade de itens na ordem é maior do que a configurada no administrador, está permitindo que as ordens sejam integradas, não respeitando a quantidade máxima de skus configurados.
diff --git a/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md b/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
index 713136060..07b097ada 100644
--- a/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
+++ b/docs/known-issues/pt/error-in-viewing-the-orders-ui-after-requesting-the-invoice-via-app.md
@@ -18,9 +18,7 @@ internalReference: 1070299
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando executamos uma "alteração V2" removendo ou adicionando um item a um pedido, criamos uma alteração na lista de itens do pedido, o que pode aumentar ou diminuir o número de índices na lista de itens no json. Essa alteração, por sua vez, pode não ser consumida por todos os aplicativos ou bancos de dados envolvidos no processamento do pedido, como o aplicativo notificador de faturas;
diff --git a/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md b/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md
index 1343e88bb..d8d0f58dc 100644
--- a/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md
+++ b/docs/known-issues/pt/error-integrating-sku-field-may-not-be-null-magalu.md
@@ -18,9 +18,7 @@ internalReference: 639272
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md b/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
index abf058401..674709aef 100644
--- a/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
+++ b/docs/known-issues/pt/error-leituradedadosdoadministrador-when-trying-to-access-catalog-pages-on-admin.md
@@ -18,9 +18,7 @@ internalReference: 1055578
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns usuários, mesmo com a função correta, recebem um erro "O usuário xx não tem acesso à página solicitada (LeituraDeDadosDoAdministrador)" ao acessar páginas de catálogo no admin.
diff --git a/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md b/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
index fb7cdb130..73edad068 100644
--- a/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
+++ b/docs/known-issues/pt/error-message-on-offers-management-does-not-update-after-sku-is-binded-on-vtexvtex-integrations.md
@@ -18,9 +18,7 @@ internalReference: 712956
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md b/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
index 633579032..74bd5b83d 100644
--- a/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
+++ b/docs/known-issues/pt/error-occurs-when-attempting-to-perform-a-search-using-the-all-field-in-vtex-crm.md
@@ -18,9 +18,7 @@ internalReference: 925679
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Esse caso ocorre com entidades que contêm um grande número de campos e milhões de registros em uma entidade. O problema ocorre porque o mecanismo de busca usa o campo "All", que envia solicitações individuais para cada campo pesquisável da entidade e multiplica a carga de solicitações para cada documento.
diff --git a/docs/known-issues/pt/error-on-duplicate-payment-method.md b/docs/known-issues/pt/error-on-duplicate-payment-method.md
index 884f8462b..9477db833 100644
--- a/docs/known-issues/pt/error-on-duplicate-payment-method.md
+++ b/docs/known-issues/pt/error-on-duplicate-payment-method.md
@@ -18,9 +18,7 @@ internalReference: 929428
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao duplicar um método de pagamento que não possui parcelas, o operador recebe a seguinte mensagem na tela: "O sistema de pagamento atual não permite opções de parcelamento". Isso acontece porque, quando o corpo da solicitação de criação na nova regra é criado, alguns campos são inseridos por padrão, incluindo installmentOptions, mas esse campo não existe para pagamentos à vista, como débito e boleto.
diff --git a/docs/known-issues/pt/error-saving-netshoes-integration-card.md b/docs/known-issues/pt/error-saving-netshoes-integration-card.md
index 3fc35bd6c..bc919245e 100644
--- a/docs/known-issues/pt/error-saving-netshoes-integration-card.md
+++ b/docs/known-issues/pt/error-saving-netshoes-integration-card.md
@@ -18,9 +18,7 @@ internalReference: 591921
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md b/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
index ea81e7f2d..cb073a3be 100644
--- a/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
+++ b/docs/known-issues/pt/error-something-went-wrong-please-try-again-when-adding-images-via-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 932126
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao adicionar imagens por meio do Site Editor, a mensagem "`Algo deu errado. Tente novamente.`" pode ocorrer ocasionalmente.
diff --git a/docs/known-issues/pt/error-sww-on-product-pdp.md b/docs/known-issues/pt/error-sww-on-product-pdp.md
index e1f254573..c856e8e2d 100644
--- a/docs/known-issues/pt/error-sww-on-product-pdp.md
+++ b/docs/known-issues/pt/error-sww-on-product-pdp.md
@@ -18,9 +18,7 @@ internalReference: 738108
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em algumas ocasiões, ao abrir o PDP do produto por meio da página de administração (ou do domínio final), um erro Something Went Wrong (Algo deu errado) é exibido na tela.
diff --git a/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md b/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
index c0f892d47..148648476 100644
--- a/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
+++ b/docs/known-issues/pt/error-triggered-by-overridden-token-in-legacy-paypal-connector-for-pending-payment-status.md
@@ -18,9 +18,7 @@ internalReference: 308214
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em nosso conector legado do PayPal, enfrentamos um problema relacionado à substituição do campo `TOKEN` por `PAYMENTINFO_0_TRANSACTIONID`. O problema surge quando o provedor envia um status de pagamento como pendente. Consequentemente, o TOKEN é substituído por nossa implementação do conector, levando a um erro acionado pelo PayPal durante as solicitações subsequentes. Como resultado, a transação fica presa com uma mensagem de "token inválido".
diff --git a/docs/known-issues/pt/error-viewing-shippingestimatedate-in-new-ui.md b/docs/known-issues/pt/error-viewing-shippingestimatedate-in-new-ui.md
index b85e9405c..69b3610d1 100644
--- a/docs/known-issues/pt/error-viewing-shippingestimatedate-in-new-ui.md
+++ b/docs/known-issues/pt/error-viewing-shippingestimatedate-in-new-ui.md
@@ -18,9 +18,7 @@ internalReference: 661040
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md b/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md
index ca5019ef7..7d6498827 100644
--- a/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md
+++ b/docs/known-issues/pt/error-when-changing-an-index-if-the-fields-are-identical.md
@@ -18,9 +18,7 @@ internalReference: 854634
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Uma atualização de um índice de esquema pode resultar em um erro 500 Internal Server quando não há alterações a serem feitas, o que significa que os valores de campo são idênticos aos atuais.
diff --git a/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md b/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md
index 1dd736339..095b531a0 100644
--- a/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md
+++ b/docs/known-issues/pt/error-when-changing-delivery-type-when-seller-has-recursion.md
@@ -18,9 +18,7 @@ internalReference: 597915
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No cenário em que o vendedor tem recorrência, ao chegar na fase de checkout e mudar o tipo de entrega da entrega para a retirada, o usuário recebe o erro "Incapaz de se comunicar com o vendedor ....", mas na verdade o erro é "O endereço não pode ser usado para o canal de entrega dado". Isto é devido à recorrência onde a API não sabe como lidar com este tipo de cenário e a UI não seleciona um canal de entrega.
diff --git a/docs/known-issues/pt/error-when-including-many-filters-in-the-order-list.md b/docs/known-issues/pt/error-when-including-many-filters-in-the-order-list.md
index d5f3b7c5e..0a37753e7 100644
--- a/docs/known-issues/pt/error-when-including-many-filters-in-the-order-list.md
+++ b/docs/known-issues/pt/error-when-including-many-filters-in-the-order-list.md
@@ -18,9 +18,7 @@ internalReference: 347932
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em algumas lojas, a lista de Vendedores, promoções ou outros filtros pode ser bastante alta, e em alguns momentos eles podem querer fazer uma seleção bastante ampla.
diff --git a/docs/known-issues/pt/error-when-install-customer-credit-app.md b/docs/known-issues/pt/error-when-install-customer-credit-app.md
index 03b2e8441..297e4a833 100644
--- a/docs/known-issues/pt/error-when-install-customer-credit-app.md
+++ b/docs/known-issues/pt/error-when-install-customer-credit-app.md
@@ -18,9 +18,7 @@ internalReference: 336533
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao baixar o aplicativo de Crédito ao Cliente e inserir o nome da conta no campo à direita, a mensagem é devolvida: _a loja indicada não pôde ser encontrada_. este é um problema intermitente e não foi possível identificar o cenário específico que faz este erro aparecer.
diff --git a/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md b/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md
index 9223662b5..3da642c5d 100644
--- a/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md
+++ b/docs/known-issues/pt/error-when-publishing-dynamic-storage-data-entity.md
@@ -18,9 +18,7 @@ internalReference: 666357
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o armazenamento cria ou atualiza uma entidade de dados e tenta publicá-la, pode ocorrer o seguinte erro:
diff --git a/docs/known-issues/pt/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md b/docs/known-issues/pt/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md
index c976f5fa7..d5daf5c82 100644
--- a/docs/known-issues/pt/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md
+++ b/docs/known-issues/pt/error-when-reaching-pages-over-333-on-a-entity-list-more-than-10000-documents.md
@@ -18,9 +18,7 @@ internalReference: 334407
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a loja tem mais de 10.000 documentos, portanto mais de 333 páginas, ao tentar alcançar as últimas páginas sobre CRM, há um erro de mensagem:
diff --git a/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md b/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
index 50a9b8c04..af7eb2c8c 100644
--- a/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
+++ b/docs/known-issues/pt/error-when-running-vtex-link-for-the-first-time.md
@@ -36,8 +36,6 @@ A mensagem de autorização de erro pode mudar de `node` para `react` de acordo
 1. Preencha o [formulário](https://suportevtex1.typeform.com/to/SxXknn)
 2. Acesse o módulo de Gerenciamento da conta e garanta que o seu perfil tem as permissões de "VTEX IO Admin"
 
-<div class="alert alert-info">
-O preenchimento do formulário não garante o acesso à Whitelist de Node + GraphQL e Extensibilty. 
-</div>
+>ℹ️ O preenchimento do formulário não garante o acesso à Whitelist de Node + GraphQL e Extensibilty.
 
 
diff --git a/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md b/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md
index 24a6fc296..7966df5ba 100644
--- a/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md
+++ b/docs/known-issues/pt/error-when-settling-transaction-with-2-cards-mercadopagov1.md
@@ -18,9 +18,7 @@ internalReference: 395943
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ## **Sumário***
 
diff --git a/docs/known-issues/pt/error-when-trying-to-open-my-cards.md b/docs/known-issues/pt/error-when-trying-to-open-my-cards.md
index 95e2111f8..bae317394 100644
--- a/docs/known-issues/pt/error-when-trying-to-open-my-cards.md
+++ b/docs/known-issues/pt/error-when-trying-to-open-my-cards.md
@@ -18,9 +18,7 @@ internalReference: 370706
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns usuários específicos estão recebendo a seguinte mensagem de erro ao fazer o login em Meus Cartões:
diff --git a/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md b/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md
index 9ace037bd..0222de32d 100644
--- a/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md
+++ b/docs/known-issues/pt/error-when-trying-to-publish-or-link-an-app.md
@@ -18,9 +18,7 @@ internalReference: 1056882
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nossa equipe investigou que isso normalmente está associado ao desenvolvimento de um aplicativo de grande porte. Isso acontece porque o hub do construtor estourou sua memória devido a muitos arquivos no aplicativo. Atrasos na vinculação do aplicativo também podem estar associados a esse problema
diff --git a/docs/known-issues/pt/eternal-loading-in-checkout-ui-v5.md b/docs/known-issues/pt/eternal-loading-in-checkout-ui-v5.md
index 61658addc..245eaf191 100644
--- a/docs/known-issues/pt/eternal-loading-in-checkout-ui-v5.md
+++ b/docs/known-issues/pt/eternal-loading-in-checkout-ui-v5.md
@@ -18,9 +18,7 @@ internalReference: 332740
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No Checkout v5, em um cenário específico, a página está presa em uma carga infinita, e no console, podemos ver o erro: "Uncaught SyntaxError": Token u inesperado em JSON na posição 0 em JSON.parse (<anónimo>)".
diff --git a/docs/known-issues/pt/event-inconsistency.md b/docs/known-issues/pt/event-inconsistency.md
index d4516a55c..c29791043 100644
--- a/docs/known-issues/pt/event-inconsistency.md
+++ b/docs/known-issues/pt/event-inconsistency.md
@@ -18,9 +18,7 @@ internalReference: 267299
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md b/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
index ed04a7eeb..5b36d4e4b 100644
--- a/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
+++ b/docs/known-issues/pt/ew-ui-does-not-suggest-the-correct-item-to-be-returned-once-the-order-has-a-change.md
@@ -18,9 +18,7 @@ internalReference: 735854
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A nova IU não sugere o item correto a ser devolvido.
diff --git a/docs/known-issues/pt/exclude-products-from-collection-not-working.md b/docs/known-issues/pt/exclude-products-from-collection-not-working.md
index cae662afa..60e7af50a 100644
--- a/docs/known-issues/pt/exclude-products-from-collection-not-working.md
+++ b/docs/known-issues/pt/exclude-products-from-collection-not-working.md
@@ -18,9 +18,7 @@ internalReference: 923016
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A conta pode criar coleções usando a versão antiga e adicionar coleções e marcas inteiras.
diff --git a/docs/known-issues/pt/expiration-date-of-special-condition-is-not-deleted.md b/docs/known-issues/pt/expiration-date-of-special-condition-is-not-deleted.md
index 2db1bbe20..9142304c1 100644
--- a/docs/known-issues/pt/expiration-date-of-special-condition-is-not-deleted.md
+++ b/docs/known-issues/pt/expiration-date-of-special-condition-is-not-deleted.md
@@ -18,9 +18,7 @@ internalReference: 547046
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cliente configura uma Condição Especial por um período de tempo e deseja apagar esta configuração, apenas o período é apagado, a recorrência desta configuração não é apagada. Isto significa que mesmo que a configuração de programação da Condição de Pagamento seja removida, o campo `dateIntervals' continua a indexar e pára de indexar a Regra de Pagamento.
diff --git a/docs/known-issues/pt/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md b/docs/known-issues/pt/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md
index d0b872d85..51dbce088 100644
--- a/docs/known-issues/pt/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md
+++ b/docs/known-issues/pt/expired-prices-not-deletableupdatable-due-to-price-variation-limit.md
@@ -18,9 +18,7 @@ internalReference: 325695
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md b/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md
index e88d13f99..f040cd5c6 100644
--- a/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md
+++ b/docs/known-issues/pt/expired-temporary-redirects-not-pointing-back-to-old-route.md
@@ -18,9 +18,7 @@ internalReference: 898062
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md b/docs/known-issues/pt/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md
index f1f6e5639..c5fd31906 100644
--- a/docs/known-issues/pt/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md
+++ b/docs/known-issues/pt/explain-search-has-no-results-when-language-matches-with-admin-locale-also-configured-in-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 830490
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando mais de um idioma estiver configurado na Intelligent Search, a Explain Search não retornará nenhum resultado se houver correspondência com uma localidade de administrador que também esteja na Intelligent Search, mas que não seja a correspondência exata. Por exemplo:
diff --git a/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md b/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
index 8bd74dba9..74af378fd 100644
--- a/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
+++ b/docs/known-issues/pt/explained-search-interface-overlapping-long-texts-between-different-areas-or-products.md
@@ -18,9 +18,7 @@ internalReference: 904482
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A página de administração da pesquisa explicada tem problemas com as regras de comercialização e as áreas de campos pesquisáveis quando uma pesquisa ou um produto tem muitas informações, sobrepondo textos entre diferentes seções/produtos.
diff --git a/docs/known-issues/pt/export-from-order-list-in-column-creation-date-is-at-utc-0.md b/docs/known-issues/pt/export-from-order-list-in-column-creation-date-is-at-utc-0.md
index c46f45085..d0908f61c 100644
--- a/docs/known-issues/pt/export-from-order-list-in-column-creation-date-is-at-utc-0.md
+++ b/docs/known-issues/pt/export-from-order-list-in-column-creation-date-is-at-utc-0.md
@@ -18,9 +18,7 @@ internalReference: 619890
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md b/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
index 2f8a0a547..3ec12cfe0 100644
--- a/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
+++ b/docs/known-issues/pt/export-lots-of-productsskus-takes-long-time-and-sometimes-the-request-can-not-completed.md
@@ -18,9 +18,7 @@ internalReference: 284386
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exportação de muitos produtos/SKUs leva muito tempo e, às vezes, a solicitação não pode ser concluída. Esse problema também afeta outras exportações de catálogos.
diff --git a/docs/known-issues/pt/export-redirects-not-working-as-intended.md b/docs/known-issues/pt/export-redirects-not-working-as-intended.md
index 8b37d6145..3664f3c17 100644
--- a/docs/known-issues/pt/export-redirects-not-working-as-intended.md
+++ b/docs/known-issues/pt/export-redirects-not-working-as-intended.md
@@ -18,9 +18,7 @@ internalReference: 537962
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md b/docs/known-issues/pt/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md
index 86cc58740..640d4c85a 100644
--- a/docs/known-issues/pt/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md
+++ b/docs/known-issues/pt/export-sku-attachment-values-does-not-work-correctly-for-spanish-language-operating-systems.md
@@ -18,9 +18,7 @@ internalReference: 566393
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o idioma do sistema operacional é o espanhol (Peru), a exportação dos valores dos anexos da SKU gera uma planilha com as colunas "Valor" e "Custo" incorretamente preenchidas
diff --git a/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md b/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md
index f91050152..cc6bf5e12 100644
--- a/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md
+++ b/docs/known-issues/pt/export-the-csv-in-the-sales-performance-module.md
@@ -18,9 +18,7 @@ internalReference: 823878
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Estamos tendo problemas ao tentar exportar o CSV no módulo de desempenho de vendas.
diff --git a/docs/known-issues/pt/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md b/docs/known-issues/pt/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md
index 664da9faf..cad73b145 100644
--- a/docs/known-issues/pt/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md
+++ b/docs/known-issues/pt/exported-price-table-filtered-by-brand-does-not-bring-all-the-skus.md
@@ -18,9 +18,7 @@ internalReference: 594075
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao exportar a tabela de preços filtrada pela Marca para obter um resultado mais específico, a planilha está ficando incompleta para o cliente.
diff --git a/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md b/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
index 342a80466..784770b83 100644
--- a/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
+++ b/docs/known-issues/pt/exporting-sku-images-for-accounts-starting-with-ht-or-p-get-this-character-cut-in-the-image-url-rows.md
@@ -18,9 +18,7 @@ internalReference: 919199
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O relatório de imagem SKU, /admin/Site/ProdutoImagemExportacao.aspx, para nomes de contas que começam com "h", "t" ou "p", como "testaccount", mostrará um caractere ausente na planilha de exportação para a linha imageURL.
diff --git a/docs/known-issues/pt/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md b/docs/known-issues/pt/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md
index b0340401c..34e4fbc46 100644
--- a/docs/known-issues/pt/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md
+++ b/docs/known-issues/pt/exporting-spreadsheet-not-working-on-received-skus-processing-tab.md
@@ -18,9 +18,7 @@ internalReference: 792511
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar exportar a lista de skus que estão na guia de processamento do módulo Skus Recebido, um erro aparece na tela:
diff --git a/docs/known-issues/pt/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md b/docs/known-issues/pt/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md
index 5b1ada31f..01a9adb32 100644
--- a/docs/known-issues/pt/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md
+++ b/docs/known-issues/pt/extra-promissory-notes-do-not-consider-change-margin-for-upselling.md
@@ -18,9 +18,7 @@ internalReference: 525987
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O valor máximo para o upselling é calculado apenas para notas promissórias padrão, quando adicionamos notas extras, nosso gateway não considera o campo de variação de margem no cálculo.
diff --git a/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md b/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md
index 9269eaebc..1cb7446ec 100644
--- a/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md
+++ b/docs/known-issues/pt/ey-send-kit-is-not-recording-a-change-in-the-card.md
@@ -18,9 +18,7 @@ internalReference: 442215
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/facebook-review-skus-load-route-behavior-on-facebook.md b/docs/known-issues/pt/facebook-review-skus-load-route-behavior-on-facebook.md
index 25989fe11..dcf80bab4 100644
--- a/docs/known-issues/pt/facebook-review-skus-load-route-behavior-on-facebook.md
+++ b/docs/known-issues/pt/facebook-review-skus-load-route-behavior-on-facebook.md
@@ -18,9 +18,7 @@ internalReference: 660874
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Revisar o comportamento da rota de carga do skus no facebook
diff --git a/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md b/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
index a4b376efc..4abff36bf 100644
--- a/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
+++ b/docs/known-issues/pt/facebook-today-facebook-looks-at-sellingprice-and-listprice-to-update-the-price-in-the-facebook-catalog.md
@@ -18,9 +18,7 @@ internalReference: 924411
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Hoje, o Facebook analisa o sellingPrice e o listPrice para atualizar o preço no catálogo do Facebook.
diff --git a/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md b/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
index 20008b90f..285c89384 100644
--- a/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
+++ b/docs/known-issues/pt/facets-from-the-segment-affecting-breadcrumbs-page-title-and-additional-filters.md
@@ -18,9 +18,7 @@ internalReference: 1057254
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A propriedade "facets" armazenada no Segmento/Sessão para um contexto de navegação funciona para limitar os resultados da pesquisa a filtros predefinidos. Por exemplo, ela é usada por "B2B Organizations" para restringir o que um usuário pode ver na loja.
diff --git a/docs/known-issues/pt/failed-payments-created-by-checkout-ui-transaction-without-payments.md b/docs/known-issues/pt/failed-payments-created-by-checkout-ui-transaction-without-payments.md
index ecdabd20d..d412bdbd8 100644
--- a/docs/known-issues/pt/failed-payments-created-by-checkout-ui-transaction-without-payments.md
+++ b/docs/known-issues/pt/failed-payments-created-by-checkout-ui-transaction-without-payments.md
@@ -18,9 +18,7 @@ internalReference: 339243
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Casos de pedidos incompletos onde suas transações não têm pagamentos.
diff --git a/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md b/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md
index 0ae6bbf0d..3d761d998 100644
--- a/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md
+++ b/docs/known-issues/pt/failure-on-the-cancellation-ppp-when-cancellationidnull.md
@@ -18,9 +18,7 @@ internalReference: 333897
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md b/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
index ecf7916d2..48e35595b 100644
--- a/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
+++ b/docs/known-issues/pt/failure-to-add-data-in-the-deliver-to-another-address-step-causes-the-go-to-payment-button-to-disappear.md
@@ -18,9 +18,7 @@ internalReference: 467419
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Durante a etapa de checkout, na etapa de preenchimento dos dados de envio, ao clicar na opção "Entregar em outro endereço", se nenhum endereço for adicionado e o comprador voltar à lista de endereços (usando o botão "voltar ao catálogo de endereços"), o botão "Ir para o pagamento" desaparecerá.
diff --git a/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md b/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md
index 2ce99e68d..28d91f12e 100644
--- a/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md
+++ b/docs/known-issues/pt/faststore-cart-merges-assembly-line-items.md
@@ -18,9 +18,7 @@ internalReference: 1050068
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se a mesma opção de montagem for adicionada a produtos diferentes, o FastStore os mesclará em um único item de linha.
diff --git a/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md b/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
index db64bd581..4eabef871 100644
--- a/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
+++ b/docs/known-issues/pt/faststore-facets-considering-not-removing-facets-set-to-ne-hidden.md
@@ -18,9 +18,7 @@ internalReference: 1029837
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md b/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md
index bdb37adf1..7744df028 100644
--- a/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md
+++ b/docs/known-issues/pt/faststore-search-api-considering-fuzzy-as-auto-as-default.md
@@ -18,9 +18,7 @@ internalReference: 889321
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No pacote @fatstore/api, para o resolvedor da Pesquisa Inteligente, estamos considerando o fuzzy como automático por padrão quando deveria ser 0. Isso está fazendo com que o comportamento do fuzzy seja aplicado, causando uma "falsa correspondência incorreta" nos resultados da pesquisa quando realmente temos uma correspondência exata com o termo pesquisado, mas exibimos mais resultados independentemente disso
diff --git a/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md b/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md
index 0b26e221b..be8f0f150 100644
--- a/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md
+++ b/docs/known-issues/pt/faststore-v1-dont-return-seo-information-on-graphql-query.md
@@ -18,9 +18,7 @@ internalReference: 929029
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao acessar o playground do Graphql para executar consultas no Faststore V1, temos uma consulta de produto. A documentação afirma que o campo SEO dessa consulta deve retornar as informações de SEO, mas isso não está acontecendo.
diff --git a/docs/known-issues/pt/faststores-not-working-correctly-in-firefox-private-mode.md b/docs/known-issues/pt/faststores-not-working-correctly-in-firefox-private-mode.md
index e1d3a9e0a..5721fa635 100644
--- a/docs/known-issues/pt/faststores-not-working-correctly-in-firefox-private-mode.md
+++ b/docs/known-issues/pt/faststores-not-working-correctly-in-firefox-private-mode.md
@@ -18,9 +18,7 @@ internalReference: 828685
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md b/docs/known-issues/pt/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md
index 162a85234..090101cab 100644
--- a/docs/known-issues/pt/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md
+++ b/docs/known-issues/pt/feed-hook-indexing-feature-skipping-events-in-fromorders-filters.md
@@ -18,9 +18,7 @@ internalReference: 832400
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao configurar o filtro Feed/Hook, você define quais atualizações de pedidos devem ser exibidas no feed. Dois tipos de filtros podem ser usados no feed: FromWorkflow e FromOrders.
diff --git a/docs/known-issues/pt/fetchmore-bringing-repeated-values-between-the-to-and-from.md b/docs/known-issues/pt/fetchmore-bringing-repeated-values-between-the-to-and-from.md
index a8d511c77..f71e11938 100644
--- a/docs/known-issues/pt/fetchmore-bringing-repeated-values-between-the-to-and-from.md
+++ b/docs/known-issues/pt/fetchmore-bringing-repeated-values-between-the-to-and-from.md
@@ -18,9 +18,7 @@ internalReference: 835396
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A função fetchMore está trazendo entre a primeira e a segunda página alguns valores duplicados e isso faz com que a página exiba repetidamente alguns dos produtos.
diff --git a/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md b/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
index 11199f241..3cd946e73 100644
--- a/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
+++ b/docs/known-issues/pt/fetchmore-keeping-the-nextpage-status-and-crashing-the-pagination.md
@@ -18,9 +18,7 @@ internalReference: 560014
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se você acessar uma loja e clicar em mostrar mais, navegar por algumas páginas, e depois clicar novamente no link "categoria" para reiniciar a navegação, o fetch mais trará o status (página) da última navegação, não retornando ao início.
diff --git a/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md b/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
index e6ac52333..152c0ade4 100644
--- a/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
+++ b/docs/known-issues/pt/field-currency-decimal-places-in-trade-policy-not-reflecting-on-pdpplp.md
@@ -18,9 +18,7 @@ internalReference: 695044
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md b/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
index 103305f4e..f3705e9f0 100644
--- a/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
+++ b/docs/known-issues/pt/field-exchanges-and-returns-is-not-updating-on-seller-management-ui-after-save.md
@@ -18,9 +18,7 @@ internalReference: 689886
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Depois de salvar o campo "Trocas e devoluções" na interface do usuário, as informações são atualizadas pela primeira vez, mas se tentarmos sair da área de gerenciamento ou atualizar a página, as informações serão perdidas.
diff --git a/docs/known-issues/pt/field-reference-always-set-as-null.md b/docs/known-issues/pt/field-reference-always-set-as-null.md
index fb3d47fe3..8f8a24b3e 100644
--- a/docs/known-issues/pt/field-reference-always-set-as-null.md
+++ b/docs/known-issues/pt/field-reference-always-set-as-null.md
@@ -18,9 +18,7 @@ internalReference: 797989
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O campo `reference` do endereço do ponto de coleta é sempre definido como nulo, embora esteja registrado na API do ponto de coleta.
diff --git a/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md b/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
index ae7b2d25a..0c0ffa6a8 100644
--- a/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
+++ b/docs/known-issues/pt/fields-in-the-orderform-configuration-are-updated-to-null-when-there-is-any-change-in-order-management-settings.md
@@ -18,9 +18,7 @@ internalReference: 748404
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao atualizar qualquer informação nas configurações de gerenciamento de pedidos (no administrador), os campos `paymentSystemToCheckFirstInstallment` e `defaultPaymentSystemToApplyOnUserOrderForm` são definidos como `null` na configuração do formulário de pedido
diff --git a/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md b/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
index e041a2532..85ed9c065 100644
--- a/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
+++ b/docs/known-issues/pt/file-manager-upload-with-two-one-more-existent-files-does-not-update-all-the-files-only-the-first.md
@@ -18,9 +18,7 @@ internalReference: 418253
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O upload do gerenciador de arquivos com dois ou mais arquivos existentes não atualiza todos os arquivos, apenas o primeiro
diff --git a/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md b/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
index 09bec7dc8..654332ee1 100644
--- a/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
+++ b/docs/known-issues/pt/filter-by-skuname-on-sales-performance-is-not-accepting-uppercase.md
@@ -18,9 +18,7 @@ internalReference: 639219
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No Painel de Desempenho de Vendas, o filtro por um termo não aceita letras maiúsculas no SkuName.
diff --git a/docs/known-issues/pt/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md b/docs/known-issues/pt/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md
index 028f3b836..ca01df0d7 100644
--- a/docs/known-issues/pt/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md
+++ b/docs/known-issues/pt/filter-on-list-order-by-promotion-with-space-blank-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 523984
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na lista, peça um filtro por promoção, quando há um espaço extra em branco no nome da promoção na json não está correspondendo.
diff --git a/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md b/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
index 99d9d3753..21fe4904d 100644
--- a/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
+++ b/docs/known-issues/pt/filter-productclusterids-is-overwritten-by-productclusternames-while-applying-additional-filters.md
@@ -18,9 +18,7 @@ internalReference: 899508
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma pesquisa é iniciada com o filtro "productClusterIds", a aplicação de qualquer filtro adicional o converterá em "productClusterNames", perdendo a característica de apresentar os itens com a classificação definida manualmente na coleção de produtos.
diff --git a/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md b/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
index 70f0305ff..034a5a3ad 100644
--- a/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
+++ b/docs/known-issues/pt/filter-products-by-store-on-the-catalog-admin-can-show-the-wrong-ammount-of-results.md
@@ -18,9 +18,7 @@ internalReference: 756461
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Filtrar produtos por "Loja" no Catálogo Admin pode mostrar a quantidade errada de resultados
diff --git a/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md b/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md
index 8ac3cb41d..8ee1aed4b 100644
--- a/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md
+++ b/docs/known-issues/pt/filters-by-sku-specifications-not-considering-regionalized-availability.md
@@ -18,9 +18,7 @@ internalReference: 1045111
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A filtragem da pesquisa por uma especificação de SKU também aplicará um filtro por disponibilidade de SKU, removendo os produtos em que a variação selecionada estiver em falta, mas isso não se aplica a lojas regionalizadas.
diff --git a/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md b/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
index 5968e086d..e92e04758 100644
--- a/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
+++ b/docs/known-issues/pt/filters-hidden-from-the-store-are-also-hidden-from-intelligent-search-admin-pages.md
@@ -18,9 +18,7 @@ internalReference: 416638
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas especificações têm uso interno ou cenários que precisam ser ocultados, mas a loja precisa dessa especificação para fins de pesquisa, como usá-la para Regras de comercialização.
diff --git a/docs/known-issues/pt/filters-hide-scenarios-internals-and-usability.md b/docs/known-issues/pt/filters-hide-scenarios-internals-and-usability.md
index 86e5dfdce..fe28ec15e 100644
--- a/docs/known-issues/pt/filters-hide-scenarios-internals-and-usability.md
+++ b/docs/known-issues/pt/filters-hide-scenarios-internals-and-usability.md
@@ -18,9 +18,7 @@ internalReference: 416638
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas especificações têm uso interno e também escondem cenários, mas a loja precisa dessa especificação para um propósito na busca, como usá-la para regras de Mercadoria ou para fins de exibição.
diff --git a/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md b/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
index aa40a4b96..a37ec2b99 100644
--- a/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
+++ b/docs/known-issues/pt/final-domain-different-from-myvtex-due-to-old-component-version-on-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 948071
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, você pode fazer alterações no Site Editor e essas alterações são refletidas no ambiente myvtex, mas quando você tenta atualizar o domínio final, essas alterações não são refletidas. Isso normalmente acontece quando o componente que você está tentando alterar tem mais de uma versão. O front continua usando a versão inativa do componente, enquanto o myvtex está usando a versão ativa. A única maneira de resolver isso é excluir a versão inativa do componente.
diff --git a/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md b/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
index bc68d7443..c473eeadf 100644
--- a/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
+++ b/docs/known-issues/pt/first-address-in-the-address-list-incomplete-does-not-fill-the-profileshipping-data-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 366975
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário tem mais de um endereço em seu perfil e o primeiro endereço na lista de endereços está incompleto, independentemente de os outros serem válidos, o checkout não preenche automaticamente os dados de perfil/envio após a adição do e-mail.
diff --git a/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md b/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
index 4d7ad639d..24319e265 100644
--- a/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
+++ b/docs/known-issues/pt/first-digit-is-removed-from-corporatedocument-if-starts-with-letters.md
@@ -18,9 +18,7 @@ internalReference: 920703
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o documento corporativo de uma organização começa com letras, o primeiro dígito é removido após o acesso ao checkout.
diff --git a/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md b/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
index cb0065c8f..d251e12a2 100644
--- a/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
+++ b/docs/known-issues/pt/first-search-in-a-store-is-not-considered-on-ui-last-searches.md
@@ -18,9 +18,7 @@ internalReference: 570971
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar em uma loja pela primeira vez, sua primeira busca não aparecerá nas "últimas buscas", mas todas as outras serão consideradas.
diff --git a/docs/known-issues/pt/first-subscription-cycle-is-skipped.md b/docs/known-issues/pt/first-subscription-cycle-is-skipped.md
index 8e001f74c..93ef83d22 100644
--- a/docs/known-issues/pt/first-subscription-cycle-is-skipped.md
+++ b/docs/known-issues/pt/first-subscription-cycle-is-skipped.md
@@ -18,9 +18,7 @@ internalReference: 528556
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O sistema de assinatura usa informações como a frequência de compra e a data do ciclo de assinatura para gerar um pedido de assinatura. No entanto, dependendo do fuso horário do consumidor e da hora em que o pedido é feito, o primeiro ciclo é ignorado e gerado somente no segundo mês.
diff --git a/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md b/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
index e1a2943fe..f2bb5a613 100644
--- a/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
+++ b/docs/known-issues/pt/fixed-price-being-created-on-trade-policy-1-when-saving-bundle-prices.md
@@ -18,9 +18,7 @@ internalReference: 705869
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md b/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
index dcf0ddb6b..3774cca11 100644
--- a/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
+++ b/docs/known-issues/pt/flag-only-apply-discount-to-the-cheapest-shipping-option-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 672567
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md b/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
index b6301b7ad..fdcbc82d7 100644
--- a/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
+++ b/docs/known-issues/pt/fob-external-marketplace-integrate-an-order-erro-code-fmt010.md
@@ -18,9 +18,7 @@ internalReference: 532377
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O mercado externo (parceiro) ao tentar integrar as ordens FOB está recebendo o erro:
diff --git a/docs/known-issues/pt/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md b/docs/known-issues/pt/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md
index 149131393..fe61c830e 100644
--- a/docs/known-issues/pt/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md
+++ b/docs/known-issues/pt/for-debt-with-cielov3-we-are-not-respecting-the-status-of-the-response.md
@@ -18,9 +18,7 @@ internalReference: 367284
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ## **Sumário***
 
diff --git a/docs/known-issues/pt/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md b/docs/known-issues/pt/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md
index bfec5763d..0ba882574 100644
--- a/docs/known-issues/pt/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md
+++ b/docs/known-issues/pt/for-in-cash-payment-1-installment-is-being-processed-by-payment-conditions-that-have-not-1-installment-option.md
@@ -18,9 +18,7 @@ internalReference: 292781
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pois em pagamento à vista (1 parcela) está sendo ignorada para a regra de condição de pagamento, embora a condição de pagamento não tenha configuração para 1 parcela.
diff --git a/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md b/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
index 31dd2281e..3f91728ce 100644
--- a/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
+++ b/docs/known-issues/pt/free-shipping-promotion-being-applied-on-split-orders-outside-promotion-restriction.md
@@ -18,9 +18,7 @@ internalReference: 732302
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md b/docs/known-issues/pt/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md
index 460780b36..f04744a4b 100644
--- a/docs/known-issues/pt/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md
+++ b/docs/known-issues/pt/freight-values-update-api-taking-time-to-reflect-on-simulation-module.md
@@ -18,9 +18,7 @@ internalReference: 621230
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As atualizações do valor do frete estão levando mais de 1 dia para refletir sobre a simulação de embarque quando a atualização foi solicitada usando o método API POST. Esta questão é intermitente, geralmente a atualização leva apenas alguns minutos.
diff --git a/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md b/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
index 92778452c..6b8268b28 100644
--- a/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
+++ b/docs/known-issues/pt/fullcleanup-on-sellers-does-not-work-if-the-account-has-seller-groups-on-seller-management.md
@@ -18,9 +18,7 @@ internalReference: 922541
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na área de gerenciamento de vendedores, o marketplace pode agrupar seus vendedores como desejar e gerenciá-los na guia de gerenciamento de grupos.
diff --git a/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md b/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
index 0df9517bd..fa15bfca4 100644
--- a/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
+++ b/docs/known-issues/pt/ga4-purchase-event-doesnt-have-the-category-tree-on-itemcategory-in-datalayer.md
@@ -18,9 +18,7 @@ internalReference: 860655
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O evento de compra do GA4 não tem a árvore de categorias em item_category no dataLayer, portanto, a única categoria disponível é a categoria de último nível do produto.
diff --git a/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md b/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
index c44c387ec..388a4dc30 100644
--- a/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
+++ b/docs/known-issues/pt/geocoordinates-data-cant-be-informed-for-some-cultureinfo.md
@@ -18,9 +18,7 @@ internalReference: 582065
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md b/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
index 5700a788f..966e24681 100644
--- a/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
+++ b/docs/known-issues/pt/get-all-sku-suggestions-api-doesnt-keep-same-sku-order-when-changing-limits.md
@@ -18,9 +18,7 @@ internalReference: 367187
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ### **Resumo**
 
diff --git a/docs/known-issues/pt/get-category-tree-api-with-internal-cache.md b/docs/known-issues/pt/get-category-tree-api-with-internal-cache.md
index 0c0ac0603..64a10c989 100644
--- a/docs/known-issues/pt/get-category-tree-api-with-internal-cache.md
+++ b/docs/known-issues/pt/get-category-tree-api-with-internal-cache.md
@@ -18,9 +18,7 @@ internalReference: 480892
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Árvore de Categoria API GET tem um cache interno. Ao realizar uma solicitação utilizando o domínio interno VTEX e eles, realizando a mesma solicitação utilizando o domínio do cliente, a primeira solicitação será colocada em cache e na resposta da segunda solicitação, realizada utilizando o domínio do cliente, devolveremos as URLs das categorias com o domínio interno VTEX.
diff --git a/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md b/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
index bc8c615e9..d20f5f0b0 100644
--- a/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
+++ b/docs/known-issues/pt/get-coupon-usage-api-doesnt-list-multiple-orders-for-the-same-coupon.md
@@ -18,9 +18,7 @@ internalReference: 326662
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md b/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md
index 79c24c7b7..41d305e75 100644
--- a/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md
+++ b/docs/known-issues/pt/get-matched-offers-list-api-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 553456
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API Get Matched Offers List , documentada aqui: https://developers.vtex.com/vtex-rest-api/reference/getofferslist, não está funcionando corretamente quando o usuário tenta inserir os parâmetros de consulta sugeridos.
diff --git a/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md b/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
index c278631c7..5fb431e35 100644
--- a/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
+++ b/docs/known-issues/pt/get-product-by-refid-returning-null-when-not-found.md
@@ -18,9 +18,7 @@ internalReference: 826702
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A rota get product by refid (/catalog_system/pvt/products/productgetbyrefid) está retornando um valor nulo em vez de uma simples resposta 404 quando não encontra um ID válido em um determinado catálogo da loja
diff --git a/docs/known-issues/pt/get-seller-list-responding-with-empty-urllogo.md b/docs/known-issues/pt/get-seller-list-responding-with-empty-urllogo.md
index bc0756e46..ae11ea35a 100644
--- a/docs/known-issues/pt/get-seller-list-responding-with-empty-urllogo.md
+++ b/docs/known-issues/pt/get-seller-list-responding-with-empty-urllogo.md
@@ -18,9 +18,7 @@ internalReference: 387508
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o caminho `/api/catalog_system/pvt/seller/list` está respondendo com uma propriedade UrlLogo vazia para todos os vendedores, independentemente de eles terem ou não um arquivo de logotipo válido.
diff --git a/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md b/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md
index dc75d566b..65e477055 100644
--- a/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md
+++ b/docs/known-issues/pt/get-sku-by-ean-api-returns-only-active-skus.md
@@ -18,9 +18,7 @@ internalReference: 699007
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md b/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
index e3ec6e46b..5f06a46b7 100644
--- a/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
+++ b/docs/known-issues/pt/getcurrentproductwithvariations-function-from-vtexjs-brings-data-from-component-sku-and-not-from-kit-sku.md
@@ -18,9 +18,7 @@ internalReference: 324416
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Função `getCurrentProductWithVariations` da VTEX.js traz dados do Componente SKU em vez do KIT SKU.
diff --git a/docs/known-issues/pt/gift-card-creation-error-via-admin.md b/docs/known-issues/pt/gift-card-creation-error-via-admin.md
index 21d7d5a65..f900e7b0f 100644
--- a/docs/known-issues/pt/gift-card-creation-error-via-admin.md
+++ b/docs/known-issues/pt/gift-card-creation-error-via-admin.md
@@ -18,9 +18,7 @@ internalReference: 986327
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas contas não conseguirão criar um Gift Card pela primeira vez por meio do admin, a mensagem abaixo aparecerá na tela:
diff --git a/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md b/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
index 5b555d22c..bd807607b 100644
--- a/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
+++ b/docs/known-issues/pt/gift-card-expiration-date-does-not-match-with-the-date-chosen-when-it-was-created.md
@@ -18,9 +18,7 @@ internalReference: 378436
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os clientes estão recebendo um erro ao tentarem pagar com Cartões-Presente quando a data da compra coincide com a data de expiração.
diff --git a/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md b/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
index f1ff8c6bf..0532755c9 100644
--- a/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
+++ b/docs/known-issues/pt/gift-card-hub-accepts-invalidempty-id-in-response-to-create-transaction.md
@@ -18,9 +18,7 @@ internalReference: 855864
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A documentação do protocolo do nosso provedor de cartão-presente especifica que a API de criação de transação deve incluir um ID válido na resposta. No entanto, a implementação atual do protocolo permite que os provedores respondam a essa solicitação com um ID vazio ou inválido. Como resultado, ao tentar liquidar o pagamento, a transação fica presa porque a ID necessária está faltando. Isso faz com que um erro seja lançado e a transação permaneça presa no processo.
diff --git a/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md b/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
index e843bc359..d31d38ad8 100644
--- a/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
+++ b/docs/known-issues/pt/gift-card-hub-is-adding-an-extra-backslash-when-calling-providers.md
@@ -18,9 +18,7 @@ internalReference: 669575
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nossa API do hub Gift Card está adicionando uma contrabarra extra ao pedido ao ligar para os fornecedores. Isto é causado pela forma como convertemos o serviçoUrl e o concatenamos com a URL fornecida pelo conector.
diff --git a/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md b/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
index 9a6f57654..d4393db68 100644
--- a/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
+++ b/docs/known-issues/pt/gift-card-it-does-not-return-fields-caption-and-relationname-when-we-make-a-get-request.md
@@ -18,9 +18,7 @@ internalReference: 428725
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o método GET é executado para um cartão-presente existente, ele não retorna o campo "caption" nem o campo "relationName", embora esses parâmetros tenham valor.
diff --git a/docs/known-issues/pt/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md b/docs/known-issues/pt/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md
index df8d8c5ef..0fc25cd34 100644
--- a/docs/known-issues/pt/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md
+++ b/docs/known-issues/pt/gift-card-page-ui-loading-indefinitely-preventing-users-with-permission-from-accessing-it-properly.md
@@ -18,19 +18,13 @@ internalReference: 325007
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md b/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md
index e4ac17fd9..17456de72 100644
--- a/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md
+++ b/docs/known-issues/pt/gift-items-throws-a-generic-exception-if-it-has-no-price.md
@@ -18,9 +18,7 @@ internalReference: 510490
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A seleção de um item de presente no carrinho lançará uma exceção genérica se ele não tiver preço, especialmente se a loja utilizar um serviço de impostos externos. O cliente não pode ir em frente ao selecioná-lo.
diff --git a/docs/known-issues/pt/gift-list-error-incomplete-address.md b/docs/known-issues/pt/gift-list-error-incomplete-address.md
index 9572b4e17..00e599188 100644
--- a/docs/known-issues/pt/gift-list-error-incomplete-address.md
+++ b/docs/known-issues/pt/gift-list-error-incomplete-address.md
@@ -18,9 +18,7 @@ internalReference: 313576
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas Listas de Presentes são mostradas em vermelho com a mensagem "endereço incompleto". Ao clicar na URL da lista de presentes, eles a redirecionam para a seguinte mensagem de erro: `.myvtex.com/giftlist?GiftListAddressFail_ID``.
diff --git a/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md b/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
index 947ac73f0..1b9fa4dc8 100644
--- a/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
+++ b/docs/known-issues/pt/gift-promotions-not-working-as-expected-when-acting-alongside-other-gift-promotion.md
@@ -18,9 +18,7 @@ internalReference: 729980
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md b/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
index b5732e792..9e1c11fd4 100644
--- a/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
+++ b/docs/known-issues/pt/giftcard-hub-setting-r-as-the-automatic-currency-on-the-ui.md
@@ -18,9 +18,7 @@ internalReference: 690794
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/giftcard-not-getting-refund-after-transaction-cancellation.md b/docs/known-issues/pt/giftcard-not-getting-refund-after-transaction-cancellation.md
index ee0fac638..503c2c8b8 100644
--- a/docs/known-issues/pt/giftcard-not-getting-refund-after-transaction-cancellation.md
+++ b/docs/known-issues/pt/giftcard-not-getting-refund-after-transaction-cancellation.md
@@ -18,9 +18,7 @@ internalReference: 491195
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o pagamento é um cartão presente e ocorre um erro durante o processo de colocação do pedido e o pedido permanece incompleto, então o GC não é reembolsado após a transação ser cancelada.
diff --git a/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md b/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
index 643d890ed..98144af71 100644
--- a/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
+++ b/docs/known-issues/pt/giftcard-rechargeable-configuration-does-not-work-when-trying-to-add-credit-to-the-gift-card-through-api.md
@@ -18,9 +18,7 @@ internalReference: 583669
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar um cartão-presente, configuramos se ele é recarregável ou não. Entretanto, o impedimento de adicionar crédito a um cartão-presente não recarregável acontece apenas através da IU, através da API é possível adicionar crédito mesmo que o cartão-presente não seja recarregável.
diff --git a/docs/known-issues/pt/giftcard-transaction-api-always-returns-empty-response.md b/docs/known-issues/pt/giftcard-transaction-api-always-returns-empty-response.md
index a612f5c31..a6c957a3e 100644
--- a/docs/known-issues/pt/giftcard-transaction-api-always-returns-empty-response.md
+++ b/docs/known-issues/pt/giftcard-transaction-api-always-returns-empty-response.md
@@ -18,9 +18,7 @@ internalReference: 384430
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Obtenha o Giftcard Transaction e obtenha o GiftCard dos pontos finais API do Provedor de GiftCard sempre retorna uma resposta vazia
diff --git a/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md b/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
index ad5005ac8..1f950b15d 100644
--- a/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
+++ b/docs/known-issues/pt/giftlist-data-de-evento-salva-na-ui-nao-e-a-mesma-que-reflete-no-bd.md
@@ -18,9 +18,7 @@ internalReference: 402134
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Salvando o evento da lista de presentes datado de 31/12/2021, ele se registra na UI 30/12/2021, mas é 31/12/2021 na exportação (a data correta)
diff --git a/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md b/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md
index 640fc737e..4237ad0ee 100644
--- a/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md
+++ b/docs/known-issues/pt/global-categories-in-catalog-outdated-compared-to-google.md
@@ -18,9 +18,7 @@ internalReference: 754062
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Google atualizou recentemente suas categorias de taxonomia, chamadas de categoria global na VTEX. Entretanto, comparando as categorias descritas no arquivo do Google e dentro do catálogo VTEX, você pode ver que nossa referência está desatualizada.
diff --git a/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md b/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
index c962e4f11..b525673a9 100644
--- a/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
+++ b/docs/known-issues/pt/go-to-payment-button-doesnt-work-in-delivery-split-when-switching-between-delivery-and-pick-up-options.md
@@ -18,9 +18,7 @@ internalReference: 756587
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um carrinho com pelo menos 2 produtos onde há uma divisão de entrega em que um dos itens está disponível para retirada e o outro apenas para entrega programada, a IU não permitirá a etapa de pagamento quando você mudar entre as opções de retirada e entrega se o primeiro item no carrinho for aquele com entrega programada
diff --git a/docs/known-issues/pt/google-bot-terms-appearing-in-results.md b/docs/known-issues/pt/google-bot-terms-appearing-in-results.md
index 2d2bb165f..aab421cc3 100644
--- a/docs/known-issues/pt/google-bot-terms-appearing-in-results.md
+++ b/docs/known-issues/pt/google-bot-terms-appearing-in-results.md
@@ -18,9 +18,7 @@ internalReference: 627537
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os relatórios do Intelligent Search mostram termos consultados pelo Google Bot. Espera-se que isso seja filtrado.
diff --git a/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md b/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
index b0f66b6d7..0e61702b1 100644
--- a/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
+++ b/docs/known-issues/pt/google-customer-reviews-component-iframe-has-inconsistent-rendering.md
@@ -18,9 +18,7 @@ internalReference: 578443
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O iframe, responsável pelo emblema do Google Customer Review, tem renderização inconsistente dentro do elemento div do componente Google Customer Reviews.
diff --git a/docs/known-issues/pt/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md b/docs/known-issues/pt/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md
index bec102fc2..445b9f2bf 100644
--- a/docs/known-issues/pt/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md
+++ b/docs/known-issues/pt/google-maps-address-search-not-filtering-by-the-selected-country-in-some-scenarios.md
@@ -18,9 +18,7 @@ internalReference: 727408
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As pesquisas de endereços do Google Maps para países sem regras internas específicas não são filtradas para retornar somente este país selecionado.
diff --git a/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md b/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
index cad3daa14..36a576113 100644
--- a/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
+++ b/docs/known-issues/pt/group-by-delivery-method-on-sales-performance-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 639294
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando se tenta agrupar pelo Método de Entrega no Painel de Desempenho de Vendas, aparece um erro:
diff --git a/docs/known-issues/pt/group-name-is-not-automatically-updated-on-intelligent-search.md b/docs/known-issues/pt/group-name-is-not-automatically-updated-on-intelligent-search.md
index a77f2752f..181224a88 100644
--- a/docs/known-issues/pt/group-name-is-not-automatically-updated-on-intelligent-search.md
+++ b/docs/known-issues/pt/group-name-is-not-automatically-updated-on-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 821481
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, há dois módulos de coleta distintos:
diff --git a/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md b/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md
index 040310af3..ae1f833e6 100644
--- a/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md
+++ b/docs/known-issues/pt/headless-cms-ignores-array-validation-settings.md
@@ -18,9 +18,7 @@ internalReference: 1046372
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar configurar regras de validação de matriz no CMS Headless, como itens de matriz mínimos e máximos, os erros de validação não são mostrados ao usuário e é possível salvar o esquema sem passar pela validação.
diff --git a/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md b/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
index 82bab3624..597d58df1 100644
--- a/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
+++ b/docs/known-issues/pt/how-many-times-will-your-benefit-be-applied-in-your-store-saving-incorrectly-on-promotion-form-interface.md
@@ -18,9 +18,7 @@ internalReference: 268304
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md b/docs/known-issues/pt/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md
index 2eaf7a84b..ba404ac7e 100644
--- a/docs/known-issues/pt/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md
+++ b/docs/known-issues/pt/if-the-correios-tables-are-not-concatenated-in-the-ready-to-dispatch-filter-the-label-generation-does-not-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 517449
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A falta de agrupamento nas tabelas dos Correios dificulta o uso do filtro Ready to dispatch assim como pode levar a algum erro, e selecionar a tabela errada.
diff --git a/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md b/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
index f18396704..f4230ed39 100644
--- a/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
+++ b/docs/known-issues/pt/image-format-as-jpg-or-png-do-not-work-on-seller-portal-catalog.md
@@ -18,9 +18,7 @@ internalReference: 1020505
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar criar um produto com um formato de imagem definido como JPG ou PNG, o produto é criado com uma imagem quebrada. Esse comportamento não ocorre se o formato for definido como jpg ou png (sem capslock).
diff --git a/docs/known-issues/pt/image-spreadsheet-not-importing-error-message-fail-to-process-record.md b/docs/known-issues/pt/image-spreadsheet-not-importing-error-message-fail-to-process-record.md
index d6afcdaf9..b3e500b84 100644
--- a/docs/known-issues/pt/image-spreadsheet-not-importing-error-message-fail-to-process-record.md
+++ b/docs/known-issues/pt/image-spreadsheet-not-importing-error-message-fail-to-process-record.md
@@ -18,9 +18,7 @@ internalReference: 691803
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md b/docs/known-issues/pt/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md
index 1a2b52dcd..b21c3b1fa 100644
--- a/docs/known-issues/pt/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md
+++ b/docs/known-issues/pt/images-spreadsheet-not-exported-when-the-account-has-too-many-skus.md
@@ -18,9 +18,7 @@ internalReference: 623183
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Apesar da mensagem de sucesso na planilha de administração das imagens sendo processada e que em breve será enviada para o e-mail, o relatório nunca chega de fato.
diff --git a/docs/known-issues/pt/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md b/docs/known-issues/pt/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md
index 8d75f559b..eef782924 100644
--- a/docs/known-issues/pt/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md
+++ b/docs/known-issues/pt/impersonate-user-not-sending-impersonated-authentication-cookie-for-some-calls.md
@@ -18,9 +18,7 @@ internalReference: 790185
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você está em acesso de telemarketing e tenta imitar o acesso de um usuário que tem acesso a uma política comercial com restrições, algumas camadas de gráficos não estão enviando o cookie do usuário imitado, causando uma resposta de acesso proibido das APIs
diff --git a/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md b/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md
index a29ae402c..2eddf8a61 100644
--- a/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md
+++ b/docs/known-issues/pt/impersonation-is-ignored-after-one-purchase-is-completed.md
@@ -18,9 +18,7 @@ internalReference: 1003545
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um operador de call center se faz passar por um comprador, conclui uma compra e é enviado para a página orderPlaced, um novo orderForm será gerado.
diff --git a/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md b/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
index cd4f0b142..6c2698968 100644
--- a/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
+++ b/docs/known-issues/pt/impersonation-user-widget-not-shown-if-showmodal-is-enabled.md
@@ -18,9 +18,7 @@ internalReference: 1043039
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Após a representação de outro e-mail, espera-se que seja exibido um botão "Stop Impersonation", mas quando o `showModal` está ativado, ele não é exibido.
diff --git a/docs/known-issues/pt/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md b/docs/known-issues/pt/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md
index 41fbf3c3e..e8fd48aff 100644
--- a/docs/known-issues/pt/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md
+++ b/docs/known-issues/pt/import-and-export-productskus-category-filter-only-works-for-last-level-categories.md
@@ -18,9 +18,7 @@ internalReference: 550313
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para reduzir a quantidade de skus exportados na planilha Produto/Skus, o cliente pode utilizar os filtros.
diff --git a/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md b/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
index 467da6ae4..778db8c40 100644
--- a/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
+++ b/docs/known-issues/pt/import-collection-only-accepts-the-order-of-products-if-import-is-made-based-on-skuid.md
@@ -18,9 +18,7 @@ internalReference: 953862
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao importar uma planilha de produtos para uma coleção, o usuário pode optar por selecionar os produtos por "skuId", "productId", "skuRefId" ou "productRefId".
diff --git a/docs/known-issues/pt/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md b/docs/known-issues/pt/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md
index 13d242253..6f284c3c1 100644
--- a/docs/known-issues/pt/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md
+++ b/docs/known-issues/pt/impossibility-to-cancel-transactions-with-adyen-due-to-lack-of-pspreference.md
@@ -18,9 +18,7 @@ internalReference: 506914
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md b/docs/known-issues/pt/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md
index c7fc01e99..33fdf550e 100644
--- a/docs/known-issues/pt/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md
+++ b/docs/known-issues/pt/in-a-payout-split-scenario-when-the-amount-was-already-captured-the-gateway-no-longer-allows-a-cancellation-request.md
@@ -18,9 +18,7 @@ internalReference: 742046
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para um cenário dividido, quando o usuário faz um pedido de mudança ou mesmo um simples cancelamento após o pagamento já ter sido capturado, o gateway não permite mais receber um novo UpdateAdditionalData.
diff --git a/docs/known-issues/pt/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md b/docs/known-issues/pt/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md
index b03c0a56c..92923caf5 100644
--- a/docs/known-issues/pt/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md
+++ b/docs/known-issues/pt/in-fullcleanup-admin-the-reindex-database-button-may-not-work-on-the-first-try.md
@@ -18,9 +18,7 @@ internalReference: 790828
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No administrador Fullcleanup, há um botão para reindexar os produtos da conta. Espera-se que este botão execute a ação na primeira tentativa, porém, para que a ação seja executada, pode ser necessário clicar várias vezes no botão.
diff --git a/docs/known-issues/pt/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md b/docs/known-issues/pt/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md
index da0619064..926e36d96 100644
--- a/docs/known-issues/pt/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md
+++ b/docs/known-issues/pt/in-some-cases-checkoutui-does-not-show-the-correct-amount-to-be-paid-with-customer-credit-for-1x-installment.md
@@ -18,9 +18,7 @@ internalReference: 748320
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para um cenário onde o Crédito do Cliente é utilizado para pagar um valor inferior ao valor total do carrinho; ele mostra, para 1x a prestação no dropdown, o valor total ignorando débitos considerados como pagamento com outro método de pagamento como um cartão presente.
diff --git a/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md b/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
index cd58a3310..bf742200e 100644
--- a/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
+++ b/docs/known-issues/pt/in-some-cases-where-there-is-a-discount-on-the-order-we-have-a-discrepancy-in-the-total-value-of-the-items-to-invoice-field-in-the-order-ui.md
@@ -18,9 +18,7 @@ internalReference: 1028210
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Foi identificado que, em alguns pedidos em que há um desconto associado a um ou mais itens, podemos ter uma discrepância no valor total do campo "itens a faturar" na interface do usuário do pedido, pois o cálculo desse campo leva em conta o parâmetro "sellingPrice", em vez do parâmetro "priceDefinitions". Portanto, é possível notar diferenças de 0,01 ou um pouco mais no valor total do pedido.
diff --git a/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md b/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
index 2bb6dccbd..dbc1ce83d 100644
--- a/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
+++ b/docs/known-issues/pt/in-the-partial-return-the-tax-values-in-the-ui-appear-the-total.md
@@ -18,9 +18,7 @@ internalReference: 559458
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em uma ordem onde temos dois itens idênticos, e um dos itens é devolvido, as taxas para ambos os itens são exibidas na IU, ao invés de apenas as taxas para o item que foi devolvido sendo exibidas na IU. Esta informação sobre taxas é apenas para informação, pois o que será realmente devolvido é o que é preenchido na Nota de Devolução.
diff --git a/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md b/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md
index c5300422b..686c0d7ea 100644
--- a/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md
+++ b/docs/known-issues/pt/inability-to-make-partial-cancellation-with-mercadopagov1.md
@@ -18,9 +18,7 @@ internalReference: 286738
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cancelamento parcial é feito em um pagamento de débito, o portal não fez um pedido ao Mercado Pago e, consequentemente, o pedido de captura não é feito porque o status nos fez entender que o pagamento já foi capturado, o que significa que o dinheiro do cliente não é reembolsado
diff --git a/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md b/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
index 31f4095d6..619e4ba2a 100644
--- a/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
+++ b/docs/known-issues/pt/inability-to-use-two-or-more-different-paypal-credentials-for-the-same-account.md
@@ -18,9 +18,7 @@ internalReference: 459704
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o usuário registra duas afiliações diferentes na mesma conta usando o PayPalPlus, a plataforma não atualiza o cache para quando houver uma alteração em uma regra de pagamento, ou seja, é possível usar apenas uma credencial por conta.
diff --git a/docs/known-issues/pt/inactive-product-still-appearing-on-pdp-or-checkout.md b/docs/known-issues/pt/inactive-product-still-appearing-on-pdp-or-checkout.md
index ffc91c071..ebe466fcd 100644
--- a/docs/known-issues/pt/inactive-product-still-appearing-on-pdp-or-checkout.md
+++ b/docs/known-issues/pt/inactive-product-still-appearing-on-pdp-or-checkout.md
@@ -18,9 +18,7 @@ internalReference: 542264
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ativar somente o produto por API faz com que o produto permaneça ativo para o PDP e checkout
diff --git a/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md b/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md
index 11dd8acdb..63123138b 100644
--- a/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md
+++ b/docs/known-issues/pt/incomplete-transactions-appearing-with-brazilian-currency.md
@@ -18,9 +18,7 @@ internalReference: 1007953
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Transações incompletas (cliente "Sem nome") podem aparecer na seção Transações com a moeda R$, resultado de um erro de criação (os dados de pagamento não foram enviados), mas os pedidos são criados corretamente na moeda local.
diff --git a/docs/known-issues/pt/inconsistencies-in-billingaddress-field-sent-to-gateway.md b/docs/known-issues/pt/inconsistencies-in-billingaddress-field-sent-to-gateway.md
index fd3b947b3..49e18ff08 100644
--- a/docs/known-issues/pt/inconsistencies-in-billingaddress-field-sent-to-gateway.md
+++ b/docs/known-issues/pt/inconsistencies-in-billingaddress-field-sent-to-gateway.md
@@ -18,9 +18,7 @@ internalReference: 291688
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O gateway usa o endereço errado em cenários de compra recorrentes quando já existe um cartão salvo no perfil do usuário.
diff --git a/docs/known-issues/pt/inconsistency-between-unique-clicks-and-productids-on-is.md b/docs/known-issues/pt/inconsistency-between-unique-clicks-and-productids-on-is.md
index 733d1bc57..3813995b9 100644
--- a/docs/known-issues/pt/inconsistency-between-unique-clicks-and-productids-on-is.md
+++ b/docs/known-issues/pt/inconsistency-between-unique-clicks-and-productids-on-is.md
@@ -18,9 +18,7 @@ internalReference: 501802
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente temos um problema quando olhamos para o arquivo CSV, ele conta os cliques únicos e também exibe os produtosIds em ordem decrescente do mais alto para o mais baixo exibindo apenas os primeiros 30 devido a uma configuração.
diff --git a/docs/known-issues/pt/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md b/docs/known-issues/pt/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md
index 92ab13ff1..17eba6093 100644
--- a/docs/known-issues/pt/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md
+++ b/docs/known-issues/pt/inconsistency-in-payment-method-boleto-bancario-expiration-dates.md
@@ -18,9 +18,7 @@ internalReference: 489460
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns Boleto Bancário gerados a partir do conector ItauShopLine podem ter um prazo de validade diferente daquele configurado na afiliação
diff --git a/docs/known-issues/pt/inconsistency-on-the-deadlines-of-customer-credit-invoices.md b/docs/known-issues/pt/inconsistency-on-the-deadlines-of-customer-credit-invoices.md
index 50213f0b6..c2c399208 100644
--- a/docs/known-issues/pt/inconsistency-on-the-deadlines-of-customer-credit-invoices.md
+++ b/docs/known-issues/pt/inconsistency-on-the-deadlines-of-customer-credit-invoices.md
@@ -18,9 +18,7 @@ internalReference: 331279
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os pedidos feitos utilizando Crédito ao Cliente como forma de pagamento geram faturas de apenas uma única parcela devido a 60 dias. Se você verificar a conta no módulo de Crédito ao Cliente, diz que a fatura foi gerada sem problemas. No entanto, olhando através da API é possível notar que dentro do campo customData os prazos (datas de vencimento) são enviados com valores diferentes. Isto impacta a integração com outros sistemas que organizam o cumprimento.
diff --git a/docs/known-issues/pt/inconsistency-on-the-report-admin-page-data.md b/docs/known-issues/pt/inconsistency-on-the-report-admin-page-data.md
index 5020375eb..8bbdc4179 100644
--- a/docs/known-issues/pt/inconsistency-on-the-report-admin-page-data.md
+++ b/docs/known-issues/pt/inconsistency-on-the-report-admin-page-data.md
@@ -18,9 +18,7 @@ internalReference: 501829
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao clicar na página de administração de grandes lojas, ele retorna um erro do servidor, isto está acontecendo com a agregação feita que é muito pesada.
diff --git a/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md b/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
index 0d0250e3c..62ed83ef5 100644
--- a/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
+++ b/docs/known-issues/pt/inconsistency-payment-terms-information-between-cost-center-details-in-my-organization-and-b2b-checkout-settings.md
@@ -18,9 +18,7 @@ internalReference: 847340
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Informações inconsistentes entre os detalhes do centro de custo em Minha organização e as configurações de checkout B2B, em que Minha organização mostra uma condição de pagamento desativada, mas a condição de pagamento ainda é mostrada ao acessar o checkout.
diff --git a/docs/known-issues/pt/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md b/docs/known-issues/pt/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md
index cf73ce448..58ebee9d3 100644
--- a/docs/known-issues/pt/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md
+++ b/docs/known-issues/pt/inconsistency-when-searching-for-facets-that-contains-results-with-large-specification-values.md
@@ -18,9 +18,7 @@ internalReference: 824198
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API de facetas tem um campo specificationFilters e esse campo pode interromper o retorno da API quando os valores registrados em qualquer especificação dessa categoria forem muito grandes
diff --git a/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md b/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
index 4e8337a45..10796f332 100644
--- a/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
+++ b/docs/known-issues/pt/inconsistent-price-when-the-sku-has-unit-multiplier-different-than-1.md
@@ -18,9 +18,7 @@ internalReference: 651102
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando alguma SKU contém um multiplicador de unidade diferente de 1 (pode ser int como 10 ou 100, ou float como 0,8, por exemplo), em algumas situações, o preço retornado no store-graphql pode ter inconsistências com base na divisão do preço retornado da API de simulação:
diff --git a/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md b/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md
index 559a58da0..32a3da220 100644
--- a/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md
+++ b/docs/known-issues/pt/incorrect-address-format-on-the-my-cards-billing-addresses.md
@@ -18,9 +18,7 @@ internalReference: 791779
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao adicionar um novo endereço de cobrança no vtex.my-cards, o formato incorreto do endereço é exibido. Isto acontece quando o usuário está tentando adicionar um novo cartão de crédito, e ocorre somente quando o novo endereço que o usuário está tentando digitar é de um país diferente. O que acontece, por exemplo, é que o usuário escolhe um novo endereço dos EUA, enquanto os outros são do Canadá, todos os endereços do Canadá serão formatados como um endereço dos EUA.
diff --git a/docs/known-issues/pt/incorrect-currency-on-payment-form.md b/docs/known-issues/pt/incorrect-currency-on-payment-form.md
index 4d2995532..92303d39f 100644
--- a/docs/known-issues/pt/incorrect-currency-on-payment-form.md
+++ b/docs/known-issues/pt/incorrect-currency-on-payment-form.md
@@ -18,9 +18,7 @@ internalReference: 449286
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/incorrect-data-in-pickupstoreinfo-after-order-creation.md b/docs/known-issues/pt/incorrect-data-in-pickupstoreinfo-after-order-creation.md
index e1707ff2e..b72c235ff 100644
--- a/docs/known-issues/pt/incorrect-data-in-pickupstoreinfo-after-order-creation.md
+++ b/docs/known-issues/pt/incorrect-data-in-pickupstoreinfo-after-order-creation.md
@@ -18,9 +18,7 @@ internalReference: 347155
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em algumas ocasiões, onde temos 1 item com opção de entrega e o outro item com opção de retirada. Os dados da `pickupStoreInfo` são preenchidos incorretamente após o término do pedido.
diff --git a/docs/known-issues/pt/incorrect-display-of-package-quantity-at-checkout.md b/docs/known-issues/pt/incorrect-display-of-package-quantity-at-checkout.md
index 876f88e0a..c62b827e0 100644
--- a/docs/known-issues/pt/incorrect-display-of-package-quantity-at-checkout.md
+++ b/docs/known-issues/pt/incorrect-display-of-package-quantity-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 520369
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/incorrect-information-in-the-expiration-date-fields-of-promotions.md b/docs/known-issues/pt/incorrect-information-in-the-expiration-date-fields-of-promotions.md
index d6dcb7cf4..a9a6128b0 100644
--- a/docs/known-issues/pt/incorrect-information-in-the-expiration-date-fields-of-promotions.md
+++ b/docs/known-issues/pt/incorrect-information-in-the-expiration-date-fields-of-promotions.md
@@ -18,9 +18,7 @@ internalReference: 611284
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Intermitentemente, quando abrimos uma promoção, os campos Data de Início e Data Final exibem a data atual, e os campos Hora de Início e Hora Final exibem as 12:00 horas da manhã. Apesar das informações incorretas na IU, as datas definidas na promoção não são afetadas.
diff --git a/docs/known-issues/pt/incorrect-message-error-when-creatingediting-skus.md b/docs/known-issues/pt/incorrect-message-error-when-creatingediting-skus.md
index 1864a3dd2..e9cd067e4 100644
--- a/docs/known-issues/pt/incorrect-message-error-when-creatingediting-skus.md
+++ b/docs/known-issues/pt/incorrect-message-error-when-creatingediting-skus.md
@@ -18,9 +18,7 @@ internalReference: 774518
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para criar ou editar uma SKU é necessário preencher os campos necessários, tais como peso, altura, largura e comprimento da remessa. Entretanto, quando deixamos um desses campos sem um valor válido e salvamos a SKU, Admin retorna uma mensagem de erro sobre as especificações, mesmo quando não há especificações obrigatórias a serem preenchidas.
diff --git a/docs/known-issues/pt/incorrect-price-on-order-change-due-to-unit-multiplier.md b/docs/known-issues/pt/incorrect-price-on-order-change-due-to-unit-multiplier.md
index 09c697efd..882e37891 100644
--- a/docs/known-issues/pt/incorrect-price-on-order-change-due-to-unit-multiplier.md
+++ b/docs/known-issues/pt/incorrect-price-on-order-change-due-to-unit-multiplier.md
@@ -18,9 +18,7 @@ internalReference: 371066
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se você adicionar ou remover uma SKU de um pedido existente (o processo de pedido de modificação) e a SKU tiver uma unidade multiplicadora diferente de 1, o multiplicador de unidade não é considerado para o cálculo do novo valor do pedido.
diff --git a/docs/known-issues/pt/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md b/docs/known-issues/pt/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md
index c141ae6b9..cdf2097c4 100644
--- a/docs/known-issues/pt/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md
+++ b/docs/known-issues/pt/incorrect-price-rounding-when-unit-multiplier-is-different-from-1.md
@@ -18,9 +18,7 @@ internalReference: 426275
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O preço mostrado pelo bloco vtex.produto-preço diverge devido aos arredondamentos de multiplicação de unidades.
diff --git a/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md b/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
index 36f64092e..9b0e449a9 100644
--- a/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
+++ b/docs/known-issues/pt/incorrect-price-update-when-a-promotion-doesnt-apply-the-discount-to-all-the-same-items-in-a-cart.md
@@ -18,9 +18,7 @@ internalReference: 1025539
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma promoção aplica um desconto a apenas um item da mesma SKU (por exemplo, uma promoção Mais por Menos), se houver uma segunda promoção para essa mesma SKU, o cálculo do desconto será aplicado ao valor já descontado pela primeira promoção, resultando em um desconto menor do que o que seria concedido se a segunda promoção fosse aplicada ao preço inicial da SKU.
diff --git a/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md b/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
index fd3cdb134..e1abc7865 100644
--- a/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
+++ b/docs/known-issues/pt/incorrect-refund-calculation-in-payout-split-value-in-recipients-is-different-than-operation-value.md
@@ -18,9 +18,7 @@ internalReference: 1072285
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao chamar um reembolso (em transações com divisão de pagamento), o erro abaixo pode ocorrer com valores divergentes:
diff --git a/docs/known-issues/pt/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md b/docs/known-issues/pt/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md
index 919b48bb7..de1fc545a 100644
--- a/docs/known-issues/pt/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md
+++ b/docs/known-issues/pt/incorrect-refund-for-purchases-with-3-payment-methods-one-of-them-being-gc.md
@@ -18,9 +18,7 @@ internalReference: 464837
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As transações com 3 métodos de pagamento sendo um de seus cartões-presente têm valores de reembolso incorretos. Em alguns casos, temos um reembolso negativo que faz com que o pagamento seja cancelado.
diff --git a/docs/known-issues/pt/incorrect-shipping-preview-when-items-are-scheduled-delivery.md b/docs/known-issues/pt/incorrect-shipping-preview-when-items-are-scheduled-delivery.md
index 034083b2b..330ed2b7b 100644
--- a/docs/known-issues/pt/incorrect-shipping-preview-when-items-are-scheduled-delivery.md
+++ b/docs/known-issues/pt/incorrect-shipping-preview-when-items-are-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 545697
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exibição dos valores de entrega na visualização de remessa (carrinho) está incorreta quando os itens são entregues programados e todos esses itens deixam o mesmo SLA. Mesmo com a API devolvendo o valor correto, a IU não reflete esta informação e exibe o valor incorreto.
diff --git a/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md b/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md
index 73cadfe33..ca03386ec 100644
--- a/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md
+++ b/docs/known-issues/pt/incorrect-shippingestimatedate-for-order-fob.md
@@ -18,9 +18,7 @@ internalReference: 269104
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/incorrect-usd-currency-displayed-in-some-locales.md b/docs/known-issues/pt/incorrect-usd-currency-displayed-in-some-locales.md
index 82d807c7c..b67c12139 100644
--- a/docs/known-issues/pt/incorrect-usd-currency-displayed-in-some-locales.md
+++ b/docs/known-issues/pt/incorrect-usd-currency-displayed-in-some-locales.md
@@ -18,9 +18,7 @@ internalReference: 414901
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/incorrect-value-on-package-due-discount-division.md b/docs/known-issues/pt/incorrect-value-on-package-due-discount-division.md
index ea3a0a4ec..db4b3896f 100644
--- a/docs/known-issues/pt/incorrect-value-on-package-due-discount-division.md
+++ b/docs/known-issues/pt/incorrect-value-on-package-due-discount-division.md
@@ -18,9 +18,7 @@ internalReference: 605517
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O pacote tem um valor diferente do valor total do pedido sem valor de envio. Isso acontece por causa dos descontos que não têm divisão adequada com quantidade de itens do pedido.
diff --git a/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md b/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
index 3701543fa..9a0ee6b93 100644
--- a/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
+++ b/docs/known-issues/pt/incorrectlacking-indexings-for-accounts-where-the-accountname-is-different-from-the-one-registered-on-the-fulfillmentendpoint.md
@@ -18,9 +18,7 @@ internalReference: 1050023
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, uma conta de franquia pode ter seu registro fulFillmentEndpoint diferente de seu nome de conta "oficial", o que é uma prática comum para arquiteturas específicas de vendedor<>marketplace que precisam de vários preços e/ou estoque para canais de vendas distintos usando o recurso de franquia com vários vendedores para a mesma franquia.
diff --git a/docs/known-issues/pt/incorrectly-updated-inventory.md b/docs/known-issues/pt/incorrectly-updated-inventory.md
index 3408beb29..a410594fc 100644
--- a/docs/known-issues/pt/incorrectly-updated-inventory.md
+++ b/docs/known-issues/pt/incorrectly-updated-inventory.md
@@ -18,9 +18,7 @@ internalReference: 556514
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A emissora foi notificada para mudança de estoque no mesmo dia dentro de 2 minutos, mas apenas uma notificação chegou na integração.
diff --git a/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md b/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
index f8741b1eb..358e6fea1 100644
--- a/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
+++ b/docs/known-issues/pt/indexed-price-for-a-product-considering-the-sku-with-the-highest-instead-of-the-lowest-price.md
@@ -18,9 +18,7 @@ internalReference: 822120
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O preço indexado, que é um valor único para todo o produto (junto com seus SKUs) e usado para classificar e filtrar os produtos na Intelligent Search, está considerando o preço mais alto entre os SKUs, enquanto o esperado é considerar o SKU com o preço mais baixo - junto com regras adicionais sobre a política comercial e os vendedores dos SKUs.
diff --git a/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md b/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
index 1b49771ab..7111fd833 100644
--- a/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
+++ b/docs/known-issues/pt/individual-warehouse-inventory-exports-do-not-work-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 684464
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md b/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
index 57c2f3bbd..32557a915 100644
--- a/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
+++ b/docs/known-issues/pt/inference-invoice-system-is-not-working-properly-when-there-are-same-skuid-in-different-array-items.md
@@ -18,9 +18,7 @@ internalReference: 1008459
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns pedidos têm o mesmo SKUid em uma matriz separada de itens, o que acontece no momento da compra no checkout por diferentes motivos, como desconto a ser aplicado, por exemplo.
diff --git a/docs/known-issues/pt/infocard-mobile-images-wont-apply.md b/docs/known-issues/pt/infocard-mobile-images-wont-apply.md
index f8dc83bee..d2f112f68 100644
--- a/docs/known-issues/pt/infocard-mobile-images-wont-apply.md
+++ b/docs/known-issues/pt/infocard-mobile-images-wont-apply.md
@@ -18,9 +18,7 @@ internalReference: 909647
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você altera a imagem em um infocard para ser exibida na versão móvel, ela não será exibida. Em vez disso, a imagem principal continua sendo exibida.
diff --git a/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md b/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
index e998dea03..67229be49 100644
--- a/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
+++ b/docs/known-issues/pt/insert-sku-file-api-doesnt-accept-urls-from-servers-that-require-user-agents.md
@@ -18,9 +18,7 @@ internalReference: 1069222
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um **agente de usuário** é uma sequência de texto que um navegador da Web ou outro cliente envia a um servidor da Web em um cabeçalho de solicitação HTTP para se identificar. Essa cadeia contém informações sobre o tipo de navegador, o sistema operacional e, às vezes, detalhes adicionais, como a versão do navegador e o mecanismo de renderização usado.
diff --git a/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md b/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md
index cf65f4032..ca9a7d2dc 100644
--- a/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md
+++ b/docs/known-issues/pt/installment-options-not-updating-automatically-on-pdpplp.md
@@ -18,9 +18,7 @@ internalReference: 987467
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma conta altera as opções de parcelamento de um produto, apesar de o produto estar corretamente indexado, as opções de parcelamento não são atualizadas no PLP ou no PDP (às vezes em ambos).
diff --git a/docs/known-issues/pt/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md b/docs/known-issues/pt/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md
index 06f5e8a18..5f7bb3d85 100644
--- a/docs/known-issues/pt/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md
+++ b/docs/known-issues/pt/installmentoptions-from-orderform-api-doesnt-take-into-account-specific-installment-promotions.md
@@ -18,9 +18,7 @@ internalReference: 644563
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma promoção é restrita a uma quantidade específica de parcelas de cartão de crédito (por exemplo, "10% em dinheiro"), o valor descontado é aplicado mesmo para parcelas fora da faixa limitada, onde o objeto "parcelamentoOptions" do OrderForm API retornará valores errados.
diff --git a/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md b/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
index 4ee51fa95..4cc85f7fd 100644
--- a/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
+++ b/docs/known-issues/pt/installments-dropdown-on-checkout-ui-is-loose-when-scrolling-the-screen.md
@@ -18,9 +18,7 @@ internalReference: 540257
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao abrir a caixa de pagamento e rolar outra página de checkout, pode-se ver que a caixa de pagamento sai e está solta na tela de checkout.
diff --git a/docs/known-issues/pt/instore-does-not-read-properly-the-html-registred-in-the-product-information.md b/docs/known-issues/pt/instore-does-not-read-properly-the-html-registred-in-the-product-information.md
index b6baf544e..3a14d2db6 100644
--- a/docs/known-issues/pt/instore-does-not-read-properly-the-html-registred-in-the-product-information.md
+++ b/docs/known-issues/pt/instore-does-not-read-properly-the-html-registred-in-the-product-information.md
@@ -18,9 +18,7 @@ internalReference: 718136
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na página do produto, algumas informações sobre o produto têm tags HTML(<b>[...]</b>, <font>[...]</font>, <li>[...]</li> etc).
diff --git a/docs/known-issues/pt/integracao-de-pedido-amazon-quantidade-de-item-invalida.md b/docs/known-issues/pt/integracao-de-pedido-amazon-quantidade-de-item-invalida.md
index 2fca887f8..428ffc30c 100644
--- a/docs/known-issues/pt/integracao-de-pedido-amazon-quantidade-de-item-invalida.md
+++ b/docs/known-issues/pt/integracao-de-pedido-amazon-quantidade-de-item-invalida.md
@@ -18,9 +18,7 @@ internalReference: 385656
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md b/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
index 08a768d15..6c6d15192 100644
--- a/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
+++ b/docs/known-issues/pt/intelligent-search-banner-update-via-image-url-does-not-work-correctly.md
@@ -18,9 +18,7 @@ internalReference: 734833
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No Admin V4, no módulo Banners, o usuário tem a possibilidade de criar ou atualizar banners já criados. Ao selecionar um banner para atualização, o usuário pode escolher entre usar um campo HTML ou inserir um link de imagem direto com um URL externo. Ao selecionar a inserção do banner por meio de um link de imagem direto, é acionada a consulta GraphQL, que atualmente não está funcionando corretamente, retornando `syntaxError` e, consequentemente, o erro 500.
diff --git a/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md b/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
index 08389bb48..d9832fdc5 100644
--- a/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
+++ b/docs/known-issues/pt/intelligent-search-language-settings-not-in-sync-with-store-configurations.md
@@ -18,9 +18,7 @@ internalReference: 990343
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O idioma principal da Pesquisa Inteligente não é atualizado automaticamente de acordo com a política comercial e as configurações de vinculação, o que o torna fora de sincronia.
diff --git a/docs/known-issues/pt/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md b/docs/known-issues/pt/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md
index e2d8d0c8c..2b4d70296 100644
--- a/docs/known-issues/pt/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md
+++ b/docs/known-issues/pt/intelligent-search-multilanguage-doesnt-support-2-variations-of-the-same-languageidiom.md
@@ -18,9 +18,7 @@ internalReference: 841704
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando usarmos mais de uma localidade na conta, a tradução será feita com base no idioma ao qual a localidade se refere e se usarmos mais de uma localidade na conta, a tradução será feita com base no idioma ao qual a localidade se refere.
diff --git a/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md b/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md
index 5009acbcc..1b95b8862 100644
--- a/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md
+++ b/docs/known-issues/pt/intelligent-search-not-capturing-sales-events-for-faststore.md
@@ -18,9 +18,7 @@ internalReference: 1045163
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Intelligent Search não está capturando eventos de pedidos concluídos para lojas que usam o FastStore. Esses eventos compõem os critérios de relevância e a classificação de produtos por vendas.
diff --git a/docs/known-issues/pt/intelligent-search-not-returning-correct-sku-order.md b/docs/known-issues/pt/intelligent-search-not-returning-correct-sku-order.md
index d7b76d048..fc510e2ef 100644
--- a/docs/known-issues/pt/intelligent-search-not-returning-correct-sku-order.md
+++ b/docs/known-issues/pt/intelligent-search-not-returning-correct-sku-order.md
@@ -18,9 +18,7 @@ internalReference: 677937
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API de pesquisa inteligente não está retornando a ordem esperada das variações de SKU para um produto na pesquisa e nas prateleiras
diff --git a/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md b/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
index 164cc18c0..efc987040 100644
--- a/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
+++ b/docs/known-issues/pt/intelligent-search-redirect-settings-search-bar-is-case-sensitive.md
@@ -18,9 +18,7 @@ internalReference: 361894
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A página de configurações do Intelligent Search Redirect tem uma barra de pesquisa para ajudar a encontrar configurações de redirecionamento específicas, mas ela diferencia maiúsculas de minúsculas e só encontrará termos se eles corresponderem exatamente.
diff --git a/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md b/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
index 705976571..b696fe9dd 100644
--- a/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
+++ b/docs/known-issues/pt/intelligent-search-word-analyzer-not-normalizing-gender-in-portuguese-words.md
@@ -18,9 +18,7 @@ internalReference: 1072003
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que os termos pesquisados sejam normalizados entre suas diferentes formas (plural/singular, gênero e outras possibilidades), um processo formalmente chamado de stemming. O analisador é diferente para cada idioma para atender às suas necessidades.
diff --git a/docs/known-issues/pt/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md b/docs/known-issues/pt/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md
index 158c6e2af..d2dbf112b 100644
--- a/docs/known-issues/pt/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md
+++ b/docs/known-issues/pt/intelligent-searchs-pagination-of-field-values-is-limited-to-9999-items.md
@@ -18,9 +18,7 @@ internalReference: 428486
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Intelligent Search tem um problema com a paginação de valores. Isto resulta em alguns valores não serem exibidos ao selecioná-lo em um filtro de condições, como as condições das Regras de Merchandising, por exemplo. Se o campo selecionado contiver mais de 9.999 valores, somente os primeiros 9.999 serão exibidos no dropdown de visualização.
diff --git a/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md b/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
index 979db3fbb..2b0506424 100644
--- a/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
+++ b/docs/known-issues/pt/interacting-with-the-address-component-while-some-data-on-the-ui-is-still-in-a-loading-state-changes-the-address-insertion-mode.md
@@ -18,9 +18,7 @@ internalReference: 423811
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o usuário decide alterar seu endereço enquanto alguns dados respectivos ainda estão sendo carregados na página, o componente de endereço muda de geolocalização para o componente com um menu suspenso. Os dados podem ser, por exemplo, a seleção de uma loja para retirada. Enquanto os dados são carregados na interface, o usuário clica em "alterar endereço" e, com isso, o endereço de retorno fica em outro componente, não no componente de geolocalização.
diff --git a/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md b/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
index 1402d5854..54d921a7e 100644
--- a/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
+++ b/docs/known-issues/pt/interacting-with-the-payment-component-while-is-still-in-a-loading-state-sends-the-wrong-payment-option.md
@@ -18,9 +18,7 @@ internalReference: 952086
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comprador altera o método de pagamento enquanto o componente de pagamento ainda está sendo carregado na página, se o método de pagamento tiver opções, o pagamento enviado ao formulário de pedido está errado. Quando esse comportamento ocorre, o pedido não é criado e uma mensagem para revisar as informações de pagamento é exibida.
diff --git a/docs/known-issues/pt/intermitent-site-editor-content-loss.md b/docs/known-issues/pt/intermitent-site-editor-content-loss.md
index 7c4706e28..118529ac7 100644
--- a/docs/known-issues/pt/intermitent-site-editor-content-loss.md
+++ b/docs/known-issues/pt/intermitent-site-editor-content-loss.md
@@ -18,9 +18,7 @@ internalReference: 610533
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Cada alteração de conteúdo no Site Editor insere alterações no arquivo content.json, que é armazenado em um bucket no AWS S3. Alguns clientes relataram uma perda de conteúdo do Site Editor após alguns procedimentos comuns de atualizações de temas.
diff --git a/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md b/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md
index 1b628d607..84b0f1891 100644
--- a/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md
+++ b/docs/known-issues/pt/internalsearcherror-timeouts-on-portal.md
@@ -18,9 +18,7 @@ internalReference: 1043003
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, as lojas que usam a pesquisa legada do Portal podem enfrentar, ao usar vários filtros em sua loja, como filtros de coleção em modelos, tempos limite aleatórios e intermitentes que geralmente são exibidos como um erro "Algo deu errado" para os clientes.
diff --git a/docs/known-issues/pt/intl-not-considering-custom-currency-in-formatcurrency.md b/docs/known-issues/pt/intl-not-considering-custom-currency-in-formatcurrency.md
index 9069aa3c2..049227d00 100644
--- a/docs/known-issues/pt/intl-not-considering-custom-currency-in-formatcurrency.md
+++ b/docs/known-issues/pt/intl-not-considering-custom-currency-in-formatcurrency.md
@@ -18,9 +18,7 @@ internalReference: 736695
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md b/docs/known-issues/pt/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md
index 6b6c04e2d..cc1a8262c 100644
--- a/docs/known-issues/pt/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md
+++ b/docs/known-issues/pt/invalid-fields-card-security-code-securitycodelength-0-securitycodeisnumeric-true.md
@@ -18,9 +18,7 @@ internalReference: 442772
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O erro acontece em um cenário específico onde você preenche as informações do cartão, depois muda o método de pagamento para outro (MercadoPago, por exemplo) e depois volta novamente ao método de pagamento com cartão de crédito e depois confirma o pagamento.
diff --git a/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md b/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
index ffbf0e4be..1bb963130 100644
--- a/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
+++ b/docs/known-issues/pt/invalid-postal-code-message-in-checkout-ui-when-address-is-in-available-addresses-with-different-country.md
@@ -18,9 +18,7 @@ internalReference: 1053959
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface do usuário do checkout usa o país registrado em seu estado para validar a entrada do código postal.
diff --git a/docs/known-issues/pt/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md b/docs/known-issues/pt/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md
index eb47865d1..9c7bcc913 100644
--- a/docs/known-issues/pt/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md
+++ b/docs/known-issues/pt/inventory-divergence-in-ui-x-api-due-to-warehouse-id-being-case-sensitive.md
@@ -18,9 +18,7 @@ internalReference: 346163
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Como na verdade a mesma API cria e atualiza o armazém (Create/update warehouse: `POST https://{accountName}.{environment}.com.br/api/logistics/pvt/configuration/warehouses`), a Logística identifica pelo id qual ação deve ser tomada, e como o id é sensível a maiúsculas e minúsculas, se a intenção for atualizar o id "TEST" mas o id "test" for inserido, um novo armazém é criado, mas o inventário é replicado para ambos porque o inventário é insensível a maiúsculas e minúsculas.
 
diff --git a/docs/known-issues/pt/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md b/docs/known-issues/pt/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md
index 899ac0056..d5fd0f047 100644
--- a/docs/known-issues/pt/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md
+++ b/docs/known-issues/pt/inventory-divergence-logistics-handle-zero-on-left-as-another-sku.md
@@ -18,9 +18,7 @@ internalReference: 427610
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/inventory-management-search-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/pt/inventory-management-search-not-working-properly-on-seller-portal-accounts.md
index ea4ecf652..198ad78c2 100644
--- a/docs/known-issues/pt/inventory-management-search-not-working-properly-on-seller-portal-accounts.md
+++ b/docs/known-issues/pt/inventory-management-search-not-working-properly-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 694254
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Pesquisa de Gerenciamento de Inventário não se comporta como esperado nas contas do portal do vendedor. Isto acontece porque este tipo de contas utiliza uma versão diferente do catálogo.
diff --git a/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md b/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md
index efabd48cd..c62098b1b 100644
--- a/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md
+++ b/docs/known-issues/pt/inventory-notifications-to-indexer-are-cached.md
@@ -18,9 +18,7 @@ internalReference: 914545
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma conta de franquia ou um vendedor notifica a conta principal (ou o marketplace) sobre alterações no estoque, a conta envia o produto ao indexador para ter as informações mais atualizadas.
diff --git a/docs/known-issues/pt/inventory-reserved-items-error.md b/docs/known-issues/pt/inventory-reserved-items-error.md
index 042b8a016..b5f6b6fa4 100644
--- a/docs/known-issues/pt/inventory-reserved-items-error.md
+++ b/docs/known-issues/pt/inventory-reserved-items-error.md
@@ -18,9 +18,7 @@ internalReference: 347924
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md b/docs/known-issues/pt/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md
index 6d1634215..9f753aecb 100644
--- a/docs/known-issues/pt/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md
+++ b/docs/known-issues/pt/inventory-update-failure-using-broadcaster-for-integrations-to-notify-external-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 549645
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md b/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
index f62e526b3..89fd3d483 100644
--- a/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
+++ b/docs/known-issues/pt/invisible-characters-in-category-names-cause-page-not-found-errors.md
@@ -18,9 +18,7 @@ internalReference: 1061149
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar categorias por meio da API ou do painel de administração, o nome da categoria não é validado corretamente, permitindo a inclusão de caracteres invisíveis. Como o nome da categoria é usado para gerar o URL da categoria, esses caracteres invisíveis também são incluídos no URL. Isso faz com que a página da categoria não funcione corretamente e retorne um erro "Página não encontrada".
diff --git a/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md b/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
index fcaaefb50..f45189f03 100644
--- a/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
+++ b/docs/known-issues/pt/isavailablepersaleschannel-parameter-does-not-work-as-expected-on-the-search-api.md
@@ -18,9 +18,7 @@ internalReference: 656284
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar usar o parâmetro isAvailablePerSalesChannel para mostrar os produtos disponíveis (fq=isAvailablePerSalesChannel_{id}:1) ou indisponíveis (fq=isAvailablePerSalesChannel_{id}:0), o resultado não é consistente.
diff --git a/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md b/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md
index a12b8db98..09f0da862 100644
--- a/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md
+++ b/docs/known-issues/pt/issue-on-the-explained-search-for-searches-with-accent-marks.md
@@ -18,9 +18,7 @@ internalReference: 434752
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao utilizar a Busca Explicada no administrador para depurar e pesquisar um produto com acento no nome como por exemplo "Pão Francês", temos um sinônimo funcionando como esperado, mas esta informação não é refletida na tela para a equipe depurar e verificar se está funcionando.
diff --git a/docs/known-issues/pt/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md b/docs/known-issues/pt/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md
index 3be0a1e61..e0a0662fe 100644
--- a/docs/known-issues/pt/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md
+++ b/docs/known-issues/pt/issue-on-the-new-indexing-history-page-showing-as-updating-products-that-were-already-updated.md
@@ -18,9 +18,7 @@ internalReference: 680241
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md b/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md
index 5908ab983..4c5adaa60 100644
--- a/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md
+++ b/docs/known-issues/pt/issue-on-translating-titles-for-some-facets.md
@@ -18,9 +18,7 @@ internalReference: 776353
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há alguns casos em que o título da página está incorreto para lojas multilíngues em páginas como categoria, subcategoria e marcas, em que o caminho tem um valor e, ao examinar o título da página, ele tem um nome diferente que não corresponde ao esperado.
diff --git a/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md b/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
index e97933f6d..90fc944fd 100644
--- a/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
+++ b/docs/known-issues/pt/issue-with-session-apis-using-public-properties-beginning-with-the-same-prefix.md
@@ -18,9 +18,7 @@ internalReference: 885011
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API de sessão está gerando algumas inconsistências. A equipe de engenharia identificou o erro, que está relacionado a propriedades que começam com a mesma palavra.
diff --git a/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md b/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
index 078c626ac..cef2b67f4 100644
--- a/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
+++ b/docs/known-issues/pt/issues-inserting-values-in-loyalty-gift-card-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 943629
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o cartão-presente de fidelidade, os usuários podem ter uma experiência ruim ao selecionar a opção "Use only part of the value" (Usar apenas parte do valor), pois não há botão "Add" (Adicionar) após preencher "Value to use" (Valor a ser usado) (a entrada é aceita automaticamente), portanto, se um valor não for preenchido com rapidez suficiente, ele será atualizado apenas com os primeiros dígitos, fazendo com que o usuário tenha de repetir o procedimento. Essa experiência é pior no site para celular.
diff --git a/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md b/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md
index 8ceedc3c3..5a57059bc 100644
--- a/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md
+++ b/docs/known-issues/pt/issues-with-billingaddress-leading-to-transaction-cancellations.md
@@ -18,9 +18,7 @@ internalReference: 1027901
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/issues-with-my-account-links.md b/docs/known-issues/pt/issues-with-my-account-links.md
index 55aee3c38..153c15347 100644
--- a/docs/known-issues/pt/issues-with-my-account-links.md
+++ b/docs/known-issues/pt/issues-with-my-account-links.md
@@ -18,9 +18,7 @@ internalReference: 522514
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os links em Minha conta (menu do cabeçalho) não funcionam se o usuário já estiver na seção Minha conta
diff --git a/docs/known-issues/pt/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md b/docs/known-issues/pt/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md
index 52d89d22a..038808713 100644
--- a/docs/known-issues/pt/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md
+++ b/docs/known-issues/pt/isvaluechangeable-field-limitations-for-transaction-with-minimumvalue-of-001.md
@@ -18,9 +18,7 @@ internalReference: 825122
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há apenas duas maneiras de alterar o campo `isValueChangeable` de uma transação: quando ocorre uma divisão e quando o `maximumValue` é igual ao `minimumValue`. Além disso, vale a pena observar que toda transação é criada com um `minimumValue` de 0,01. Como resultado, quando uma transação é criada com um valor de 0,01, o campo `isValueChangeable` é automaticamente definido como `false`.
diff --git a/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md b/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
index 226f8c870..297880e1e 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-add-an-item-with-attachment-to-the-cart-if-there-is-already-another-unit-of-this-item-without-attachment-in-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 412041
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Durante o processo de compra, se o cliente adicionar um item que já tenha sido incluído no carrinho anteriormente e a nova inclusão tiver opções de montagem, o segundo item não será adicionado ao carrinho.
diff --git a/docs/known-issues/pt/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md b/docs/known-issues/pt/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md
index c51cf185c..2b8a4e107 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-cancel-a-transaction-with-maxipago.md
@@ -18,19 +18,13 @@ internalReference: 507480
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md b/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
index d8196ccb1..719cef4c7 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-create-a-path-using-content-type-via-ui.md
@@ -18,9 +18,7 @@ internalReference: 923619
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se tentarmos criar um caminho usando tipos de conteúdo por meio da interface do usuário, a página não funcionará. Ela só funcionará se a criarmos por meio do tema.
diff --git a/docs/known-issues/pt/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md b/docs/known-issues/pt/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md
index 9cd37588d..2f22dba6b 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-create-a-promotion-with-end-date-from-the-year-2100-onwards.md
@@ -18,9 +18,7 @@ internalReference: 833957
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
index 0a67f64f6..34d150004 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-argentina-in-my-account.md
@@ -18,9 +18,7 @@ internalReference: 385410
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
index bc15ecec1..f457305cc 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-save-some-addresses-from-chile-in-my-account.md
@@ -18,9 +18,7 @@ internalReference: 386030
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um caso de alguns endereços que não são possíveis de serem salvos na página da seção Minha Conta nas contas do Chile.
diff --git a/docs/known-issues/pt/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md b/docs/known-issues/pt/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md
index c0a7543ff..90d35dbba 100644
--- a/docs/known-issues/pt/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md
+++ b/docs/known-issues/pt/it-is-not-possible-to-settle-a-transaction-with-the-boleto-method-using-braspag.md
@@ -18,9 +18,7 @@ internalReference: 558065
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a transação com o Boleto Bancário usando o conector BrasPag é aprovada, pagamento em autorizado e o API Liquidar a transação é chamado, ocorre um erro na captura devido ao status é como liquidar, o que não permite que a transação seja efetivamente capturada.
diff --git a/docs/known-issues/pt/item-added-to-change-order-is-in-another-package-after-invoiced.md b/docs/known-issues/pt/item-added-to-change-order-is-in-another-package-after-invoiced.md
index 90c432f86..9d1372328 100644
--- a/docs/known-issues/pt/item-added-to-change-order-is-in-another-package-after-invoiced.md
+++ b/docs/known-issues/pt/item-added-to-change-order-is-in-another-package-after-invoiced.md
@@ -18,9 +18,7 @@ internalReference: 412526
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os itens removidos ou adicionados pelo fluxo da ordem de alteração não fazem parte do pacote, portanto, não serão exibidos no e-mail da fatura e, caso todos os itens de um pedido sejam removidos e adicionados posteriormente, o e-mail da fatura não será enviado, pois os itens adicionados não são adicionados ao pacote original do pedido;
diff --git a/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md b/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
index 2eeedae11..2dd9d680f 100644
--- a/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
+++ b/docs/known-issues/pt/item-autocomplete-not-shown-in-seller-whitelabel-change-order.md
@@ -18,9 +18,7 @@ internalReference: 348841
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao alterar um item (ordem de alteração) de uma conta de vendedor WhiteLabel, o preenchimento automático não mostra o item como esperado.
diff --git a/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md b/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md
index b2b58c989..60de2df35 100644
--- a/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md
+++ b/docs/known-issues/pt/item-available-when-customer-location-is-not-defined-with-no-stock.md
@@ -18,9 +18,7 @@ internalReference: 1073363
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a localização do cliente não é definida, os itens aparecem disponíveis mesmo quando não há estoque disponível e nenhuma etiqueta branca do vendedor é abrangente. Isso acontece somente se a SKU tiver estoque no vendedor de etiqueta branca em um depósito associado a um canal de vendas diferente daquele registrado no endpoint de atendimento do vendedor.
diff --git a/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md b/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
index 7fd6e236b..442e1e589 100644
--- a/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
+++ b/docs/known-issues/pt/itemname-of-purchase-event-is-different-from-itemname-of-add-to-cart-event-in-google-analytics.md
@@ -18,9 +18,7 @@ internalReference: 878629
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a SKU tem o mesmo nome que o produto, o item_name da compra é diferente do item_name do evento add-to-cart.
diff --git a/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md b/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
index 3dd8c41a9..dca889fe2 100644
--- a/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
+++ b/docs/known-issues/pt/items-in-benefits-not-generated-in-promotions-with-collections-associated.md
@@ -18,9 +18,7 @@ internalReference: 985850
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md b/docs/known-issues/pt/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md
index d2e0b4957..50ddf38a6 100644
--- a/docs/known-issues/pt/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md
+++ b/docs/known-issues/pt/items-not-displayed-in-item-association-listing-in-subscription-plans-configuration.md
@@ -18,9 +18,7 @@ internalReference: 648117
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md b/docs/known-issues/pt/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md
index 1ea4f3f56..903dd178d 100644
--- a/docs/known-issues/pt/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md
+++ b/docs/known-issues/pt/its-possible-to-go-from-order-to-transaction-but-the-inverse-flow-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference: 393483
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A "sequência", número que pode ser visto ao lado do número do pedido e também na transação, é responsável por ligar a transação ao pedido e ao inverso também.
diff --git a/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md b/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md
index deb9497ec..ee19f1758 100644
--- a/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md
+++ b/docs/known-issues/pt/kit-creation-api-is-not-calculating-component-prices.md
@@ -18,9 +18,7 @@ internalReference: 739693
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a carga útil da API de inserção de KIT tem um formato que solicita os componentes que compõem esse kit e suas respectivas quantidades e preços.
diff --git a/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md b/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md
index 10192f13f..3289640d7 100644
--- a/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md
+++ b/docs/known-issues/pt/kit-weight-can-be-overritten-by-apiwebservice.md
@@ -18,9 +18,7 @@ internalReference: 429993
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Atualmente, está definido no nosso catálogo de regras comerciais que o peso de um KIT SKU deve ser definido pela soma dos seus componentes - https://help.vtex.com/en/tutorial/cadastrando-kit--tutorials_215
 
diff --git a/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md b/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
index fab10d73c..89ee95009 100644
--- a/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
+++ b/docs/known-issues/pt/konduto-af-cannot-complete-a-request-when-the-accountid-is-missing.md
@@ -18,9 +18,7 @@ internalReference: 496298
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um problema para aprovar algumas transações relacionadas ao sistema antifraude da Konduto. Esse problema ocorre quando o sistema não consegue fazer a solicitação necessária devido à ausência do accountId, que é necessário para recuperar as informações de pagamento do banco de dados da conta. Você pode verificar isso examinando a rota "/payment", onde encontrará o nó "usedAccountId" com um valor de "False" nesses casos.
diff --git a/docs/known-issues/pt/lack-of-feedback-while-selecting-gift-items-that-arent-available.md b/docs/known-issues/pt/lack-of-feedback-while-selecting-gift-items-that-arent-available.md
index ba3c601f3..0d17f291b 100644
--- a/docs/known-issues/pt/lack-of-feedback-while-selecting-gift-items-that-arent-available.md
+++ b/docs/known-issues/pt/lack-of-feedback-while-selecting-gift-items-that-arent-available.md
@@ -18,9 +18,7 @@ internalReference: 648767
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A seleção de um item de presente no carrinho que não tenha estoque não dará nenhum retorno. Após selecionar o presente, o pedido de API será feito, mas quando ele responde, a seleção do presente é simplesmente removida.
diff --git a/docs/known-issues/pt/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md b/docs/known-issues/pt/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md
index 1d75b37ef..7324c7bf8 100644
--- a/docs/known-issues/pt/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md
+++ b/docs/known-issues/pt/lack-of-phone-number-validation-in-the-purchase-apis-allowing-invalid-data-in-the-orders.md
@@ -18,9 +18,7 @@ internalReference: 680500
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A validação de um número de telefone é restrita ao formulário onde ele é inserido ou editado através da interface na etapa de perfil de checkout. Os valores inseridos diretamente através das APIs REST a um formulário de pedido ou a um pedido, ou que vieram do perfil do cliente (que, a seu modo, podem ser inseridos por diferentes formas) não são validados pela plataforma.
diff --git a/docs/known-issues/pt/lack-of-validation-in-the-billingaddress-zip-code.md b/docs/known-issues/pt/lack-of-validation-in-the-billingaddress-zip-code.md
index a75328073..202633065 100644
--- a/docs/known-issues/pt/lack-of-validation-in-the-billingaddress-zip-code.md
+++ b/docs/known-issues/pt/lack-of-validation-in-the-billingaddress-zip-code.md
@@ -18,9 +18,7 @@ internalReference: 375481
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 É possível preencher e completar a compra preenchendo o código postal "faturamento/endereço" com caracteres não-numéricos
diff --git a/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md b/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md
index 52e590de7..dbcfb7082 100644
--- a/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md
+++ b/docs/known-issues/pt/large-importexport-spreadsheet-error-on-new-collections-admin.md
@@ -18,9 +18,7 @@ internalReference: 362017
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o carregamento de itens para o novo módulo de coleções com uma lista com mais de 1.000 SKUs é impossível, pois o processo atingirá o tempo limite. Ele retorna uma resposta de erro não específica:
diff --git a/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md b/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
index 732a39f06..ed5cc47cb 100644
--- a/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
+++ b/docs/known-issues/pt/large-indexed-text-and-indexed-text-not-being-changed-by-specification-import.md
@@ -18,9 +18,7 @@ internalReference: 322657
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md b/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
index d55cdecb8..f6817aae1 100644
--- a/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
+++ b/docs/known-issues/pt/lean-shipping-being-forced-even-when-the-items-have-the-same-slas-but-in-a-different-ordination.md
@@ -18,9 +18,7 @@ internalReference: 455218
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns cenários, é possível que, mesmo que o recurso LeanShipping esteja desativado nas configurações, o sistema ainda considere necessário agrupar as opções de envio e, com isso, não desative o LeanShipping, isso porque a regra usada pelo sistema para definir o uso ou não do LeanShipping além da configuração está ativada ou desativada e há SLAs iguais ou diferentes disponíveis para os itens do carrinho;
diff --git a/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md b/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
index bb1830009..1e5575ca0 100644
--- a/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
+++ b/docs/known-issues/pt/lean-shipping-causes-something-went-wrong-after-changing-pickup-points.md
@@ -18,9 +18,7 @@ internalReference: 1053609
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um comprador pode pesquisar diferentes pontos de coleta em diferentes códigos postais. Ao usar o envio enxuto, depois de adicionar um código postal com pontos de coleta disponíveis e mudar para um código postal sem pontos de coleta, a etapa de envio é bloqueada com a mensagem "Algo deu errado".
diff --git a/docs/known-issues/pt/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md b/docs/known-issues/pt/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md
index 3cdefd013..8afd0477c 100644
--- a/docs/known-issues/pt/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md
+++ b/docs/known-issues/pt/lean-shipping-doesnt-allow-selecting-regular-delivery-when-scheduled-delivery-is-the-cheapest-and-fastest.md
@@ -18,9 +18,7 @@ internalReference: 842018
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nos carrinhos em que há uma entrega programada e uma entrega normal, e o Lean Shipping está ativado, se a opção mais barata e mais rápida for a entrega programada, a interface do usuário mostrará a alternância normalmente, mas ao desmarcar, nada acontecerá e a entrega programada ainda será selecionada.
diff --git a/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md b/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
index 347032e3a..955902f8b 100644
--- a/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
+++ b/docs/known-issues/pt/lean-shipping-doesnt-deactivate-after-removing-items-from-cart.md
@@ -18,9 +18,7 @@ internalReference: 916461
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Lean Shipping não é desativado automaticamente após a remoção de itens do carrinho, mantendo apenas um onde deveria mostrar todas as opções.
diff --git a/docs/known-issues/pt/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md b/docs/known-issues/pt/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md
index db2a03324..5a361ba08 100644
--- a/docs/known-issues/pt/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md
+++ b/docs/known-issues/pt/lean-shipping-overrides-user-preferred-shipping-method-to-cheapest-option-in-different-sessionsbrowsers.md
@@ -18,9 +18,7 @@ internalReference: 607411
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em novas sessões (navegadores diferentes) para a mesma ordemFormulário, a opção selecionada anteriormente não é levada em conta, sendo sempre sobreposta à opção "mais barata", afeta especialmente os cenários de carrinho compartilhado
diff --git a/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md b/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
index 6431d71a8..aa50317d7 100644
--- a/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
+++ b/docs/known-issues/pt/legacy-catalog-ui-delete-button-not-functional.md
@@ -18,9 +18,7 @@ internalReference: 326408
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O botão para excluir produtos no catálogo não está funcionando, ele simplesmente não reconhece nenhum clique do usuário
diff --git a/docs/known-issues/pt/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md b/docs/known-issues/pt/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md
index 5c57ef415..e6c8b8d8f 100644
--- a/docs/known-issues/pt/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md
+++ b/docs/known-issues/pt/legacy-cms-does-not-create-folders-with-less-than-3-characters-in-the-name.md
@@ -18,9 +18,7 @@ internalReference: 825530
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O CMS legado não cria pastas com menos de 3 caracteres no nome
diff --git a/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md b/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md
index 8fb887ecc..2bdd8131e 100644
--- a/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md
+++ b/docs/known-issues/pt/legacy-cmss-banner-custom-element-not-working.md
@@ -18,9 +18,7 @@ internalReference: 978466
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a guia "elementos personalizados" das configurações do CMS legado não está funcionando corretamente.
diff --git a/docs/known-issues/pt/legacy-collection-import-timeout.md b/docs/known-issues/pt/legacy-collection-import-timeout.md
index 6288dd039..2d6a4ced5 100644
--- a/docs/known-issues/pt/legacy-collection-import-timeout.md
+++ b/docs/known-issues/pt/legacy-collection-import-timeout.md
@@ -18,9 +18,7 @@ internalReference: 483785
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando um usuário tenta importar dados através do botão de inserção de dados a granel, se a folha a ser utilizada for muito extensa, o processo pode falhar.
diff --git a/docs/known-issues/pt/legacy-collection-schedule-does-not-respect-sc-timezone.md b/docs/known-issues/pt/legacy-collection-schedule-does-not-respect-sc-timezone.md
index 8c137c9f8..cd88c1806 100644
--- a/docs/known-issues/pt/legacy-collection-schedule-does-not-respect-sc-timezone.md
+++ b/docs/known-issues/pt/legacy-collection-schedule-does-not-respect-sc-timezone.md
@@ -18,9 +18,7 @@ internalReference: 316054
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O cronograma de coleta legado não respeita o fuso horário SC.
diff --git a/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md b/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
index 35253f2c5..10eeb460b 100644
--- a/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
+++ b/docs/known-issues/pt/legacy-collection-ui-category-filter-selecting-products-wrongly-to-the-collection.md
@@ -18,9 +18,7 @@ internalReference: 590934
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Eventualmente, dependendo do número de produtos que temos dentro de uma categoria, se selecionarmos os filtros da categoria na IU de coleção legada, ela poderá devolver produtos que não pertencem a estas categorias.
diff --git a/docs/known-issues/pt/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md b/docs/known-issues/pt/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md
index 7c69814e2..38b552371 100644
--- a/docs/known-issues/pt/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md
+++ b/docs/known-issues/pt/legacy-collections-cms-special-character-validation-diverges-from-new-collections.md
@@ -18,9 +18,7 @@ internalReference: 450569
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md b/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
index 8daacbb3b..cbebd339c 100644
--- a/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
+++ b/docs/known-issues/pt/legacy-installment-template-and-shelf-controls-do-not-consider-unit-multipliers.md
@@ -18,9 +18,7 @@ internalReference: 979205
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, para a loja que usa o CMS legado, o modelo legado e os controles de prateleira não são ajustados se o SKU tiver um multiplicador de unidades.
diff --git a/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md b/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md
index dcd416037..637b7aad9 100644
--- a/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md
+++ b/docs/known-issues/pt/let-me-know-controller-texts-are-not-being-translated.md
@@ -18,9 +18,7 @@ internalReference: 517165
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar mudar o texto "nome" e "e-mail" do controlador Let Me Know via Store Text para outros idiomas além do EN-BR, o texto não é traduzido e permanece em português
diff --git a/docs/known-issues/pt/license-manager-access-for-sales-channel-management-is-not-working.md b/docs/known-issues/pt/license-manager-access-for-sales-channel-management-is-not-working.md
index 27eac1cfa..23c819525 100644
--- a/docs/known-issues/pt/license-manager-access-for-sales-channel-management-is-not-working.md
+++ b/docs/known-issues/pt/license-manager-access-for-sales-channel-management-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 380904
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na configuração do Gerente de Licenças, podemos selecionar qual recurso o usuário pode acessar. O gerenciamento dos Canais de Vendas não está dando acesso à página de configuração do Canal de Vendas: `account.myvtex.com/admin/Site/Store.aspx'.
diff --git a/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md b/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
index 068da9990..04c4f81ac 100644
--- a/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
+++ b/docs/known-issues/pt/link-service-values-to-skus-spreadsheet-only-returning-active-services.md
@@ -18,9 +18,7 @@ internalReference: 886486
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao exportar valores de serviços de uma categoria específica no admin, o resultado está trazendo apenas os serviços ativos. Não permitindo que o comerciante ative serviços anteriormente inativos por planilha.
diff --git a/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md b/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
index e86c5e232..a79a6c763 100644
--- a/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
+++ b/docs/known-issues/pt/link-why-fill-vtex-global-category-on-category-setup-only-works-opening-in-a-new-tab.md
@@ -18,9 +18,7 @@ internalReference: 544034
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Link "Por que preencher VTEX Global Category?" na configuração da categoria só funciona abrindo em uma nova aba. tentar abrir apenas clicando no link irá redirecionar para uma página de erro.
diff --git a/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md b/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
index d8c3a4b6a..7547c26b9 100644
--- a/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
+++ b/docs/known-issues/pt/linkid-is-not-being-registered-on-rewriter-when-translating-with-catalog-graphql.md
@@ -18,9 +18,7 @@ internalReference: 654951
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o catálogo graphQL e traduzir o URL usando o linkId, o reescritor deve armazenar o linkId, mas isso não está acontecendo: https://developers.vtex.com/docs/guides/catalog-internationalization
diff --git a/docs/known-issues/pt/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md b/docs/known-issues/pt/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md
index 9565f1417..d06803901 100644
--- a/docs/known-issues/pt/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md
+++ b/docs/known-issues/pt/listprice-shown-in-a-cart-doesnt-consider-if-the-regular-price-is-being-modified-by-a-unitmultiplier.md
@@ -18,9 +18,7 @@ internalReference: 578649
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O ListPrice de um carrinho interage com o preço exibido para mostrar um preço antigo versus o atual, em um assunto para destacar descontos.
diff --git a/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md b/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md
index 28b46a53b..778dc654a 100644
--- a/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md
+++ b/docs/known-issues/pt/locale-switcher-doesnt-work-in-myvtex-environment.md
@@ -18,9 +18,7 @@ internalReference: 778306
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Locale Switcher não funciona no ambiente myvtex sem definir explicitamente o espaço/ambiente de trabalho, mas não há impacto no site. Este comportamento afeta a navegação somente em myvtex e o gerenciamento de conteúdo para diferentes idiomas.
diff --git a/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md b/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md
index 2f455fb4d..7011c47cc 100644
--- a/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md
+++ b/docs/known-issues/pt/login-preference-with-password-cannot-be-undone-in-admin.md
@@ -18,9 +18,7 @@ internalReference: 1020548
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário faz logon na plataforma VTEX pela primeira vez (Admin), ele é solicitado a escolher sua preferência de login para a próxima vez que fizer logon. Em seguida, ele pode escolher entre digitar seu endereço de e-mail e senha ou digitar um código que será enviado para seu endereço de e-mail;
diff --git a/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md b/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md
index 807f3bc6a..0b52386f9 100644
--- a/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md
+++ b/docs/known-issues/pt/logistics-inventory-full-access-permission-did-not-work-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 482353
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md b/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
index bc1e1d16e..104c3ed1c 100644
--- a/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
+++ b/docs/known-issues/pt/logistics-simulation-with-minimum-and-maximum-price-in-shipping-policy-does-not-work-when-productprice-as-0-zero.md
@@ -18,9 +18,7 @@ internalReference: 553080
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md b/docs/known-issues/pt/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md
index 7438a71f0..b7c72a3ad 100644
--- a/docs/known-issues/pt/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md
+++ b/docs/known-issues/pt/logistics-simulator-is-showing-default-currency-instead-of-local-currency.md
@@ -18,9 +18,7 @@ internalReference: 514551
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md b/docs/known-issues/pt/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md
index ce2d91a1f..59120f6a0 100644
--- a/docs/known-issues/pt/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md
+++ b/docs/known-issues/pt/logs-stating-that-there-was-a-refund-but-due-to-an-error-on-the-part-of-the-acquirer-the-reversal-does-not-actually-occur.md
@@ -18,9 +18,7 @@ internalReference: 545331
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Mesmo com os registros das transações informando que o estorno foi feito, ocorreu um erro no adquirente.
diff --git a/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md b/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
index f7d03cb88..8a9367175 100644
--- a/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
+++ b/docs/known-issues/pt/loop-in-the-authentication-popup-when-the-first-payment-condition-requires-authentication.md
@@ -18,9 +18,7 @@ internalReference: 844192
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O pop-up de autenticação entra em loop quando a primeira condição de pagamento tem `requiresAuthentication: true`. A continuação da compra só será possível se a página for recarregada.
diff --git a/docs/known-issues/pt/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md b/docs/known-issues/pt/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md
index b7926f647..73cc91933 100644
--- a/docs/known-issues/pt/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md
+++ b/docs/known-issues/pt/looping-in-shipping-data-when-lean-shipping-is-active-and-have-two-shipping-methods-one-for-the-same-day.md
@@ -18,19 +18,13 @@ internalReference: 373868
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/loss-of-content-created-via-site-editor-from-cms-migration.md b/docs/known-issues/pt/loss-of-content-created-via-site-editor-from-cms-migration.md
index 17446f88d..c5c291623 100644
--- a/docs/known-issues/pt/loss-of-content-created-via-site-editor-from-cms-migration.md
+++ b/docs/known-issues/pt/loss-of-content-created-via-site-editor-from-cms-migration.md
@@ -18,9 +18,7 @@ internalReference: 610533
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/magalu-order-not-created-in-oms-and-without-log-in-bridge.md b/docs/known-issues/pt/magalu-order-not-created-in-oms-and-without-log-in-bridge.md
index 13dbef902..4188492d9 100644
--- a/docs/known-issues/pt/magalu-order-not-created-in-oms-and-without-log-in-bridge.md
+++ b/docs/known-issues/pt/magalu-order-not-created-in-oms-and-without-log-in-bridge.md
@@ -18,9 +18,7 @@ internalReference: 667547
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 057365b25..b74e441f1 100644
--- a/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/pt/magalu-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -18,9 +18,7 @@ internalReference: 707113
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As ordens não foram criadas em OMS+Bridge e no log mostra erro: "Referência de objeto não definida para uma instância de um objeto".
diff --git a/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md b/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
index b3a1d889f..cf8dbd577 100644
--- a/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
+++ b/docs/known-issues/pt/magalu-sku-being-integrated-with-specifications-from-another-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 689151
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns skus estão sendo integrados com especificações de outro Mercado.
diff --git a/docs/known-issues/pt/magazine-luiza-adjust-plaintextdescription-specification.md b/docs/known-issues/pt/magazine-luiza-adjust-plaintextdescription-specification.md
index 02473e05f..debb90681 100644
--- a/docs/known-issues/pt/magazine-luiza-adjust-plaintextdescription-specification.md
+++ b/docs/known-issues/pt/magazine-luiza-adjust-plaintextdescription-specification.md
@@ -18,9 +18,7 @@ internalReference: 754022
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md b/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
index 52c2fd9d0..f9aa7300e 100644
--- a/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
+++ b/docs/known-issues/pt/magazine-luiza-integrated-fob-order-with-conventional-delivery.md
@@ -18,9 +18,7 @@ internalReference: 721951
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Precisamos rever o fluxo e entender porque pedidos como "Magalu Entregas/FOB" estão sendo integrados com "selectedSla = "Convencional", por exemplo.
diff --git a/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md b/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md
index c8158278b..9f0a40f8f 100644
--- a/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md
+++ b/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-cancel-on-vtex.md
@@ -18,9 +18,7 @@ internalReference: 792618
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O pedido foi cancelado no mercado, mas na OMS foi cancelado e ainda está no status "Aguardando autorização para despacho".
diff --git a/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md b/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
index 892c202d8..82b6b795d 100644
--- a/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
+++ b/docs/known-issues/pt/magazine-luiza-order-canceled-on-marketplace-didnt-update-status-on-vtex.md
@@ -18,9 +18,7 @@ internalReference: 865926
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A ordem cancelada no marketplace não atualizou o status na VTEX
diff --git a/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md b/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
index 16290ea57..e11976338 100644
--- a/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
+++ b/docs/known-issues/pt/magazine-luiza-order-with-error-object-reference-not-set-to-an-instance-of-an-object.md
@@ -18,9 +18,7 @@ internalReference: 777298
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas ordens não foram criadas em OMS+Bridge e no log mostra erro: "Referência de objeto não definida para uma instância de um objeto".
diff --git a/docs/known-issues/pt/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md b/docs/known-issues/pt/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md
index 6238c4926..dca544922 100644
--- a/docs/known-issues/pt/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md
+++ b/docs/known-issues/pt/magazine-luiza-orders-with-approved-status-on-the-marketplace-are-not-being-approved-on-vtex.md
@@ -18,9 +18,7 @@ internalReference: 823443
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns pedidos com status APPROVED no marketplace não estão sendo aprovados na VTEX
diff --git a/docs/known-issues/pt/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md b/docs/known-issues/pt/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md
index c56dae8de..d8ef37928 100644
--- a/docs/known-issues/pt/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md
+++ b/docs/known-issues/pt/magazine-luiza-some-orders-do-not-update-status-for-delivered-on-the-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 827440
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns pedidos não estão atualizando o status para `DELIVERED` no marketplace
diff --git a/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md b/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md
index 8fe8d93ce..dd02dc225 100644
--- a/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md
+++ b/docs/known-issues/pt/magazine-luiza-some-skus-do-not-update-price.md
@@ -18,9 +18,7 @@ internalReference: 882919
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Precisamos entender por que alguns skus não atualizam o preço no marketplace.
diff --git a/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md b/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
index 3819cf842..12e021523 100644
--- a/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
+++ b/docs/known-issues/pt/magazine-luiza-tracking-erro-data-de-entrega-ao-cliente-deve-ser-maior-que-a-data-de-despacho-e-deve-ser-igual-ou-menor-a-data-de-hoje.md
@@ -18,9 +18,7 @@ internalReference: 856984
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na etapa de rastreamento, alguns pedidos estão retornando o seguinte erro `"Data de Entrega ao Cliente' deve ser maior que a 'Data de Despacho' e deve ser igual ou menor a data de hoje"`
diff --git a/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md b/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
index 2fd28ed5d..9163e6182 100644
--- a/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
+++ b/docs/known-issues/pt/main-account-is-being-selected-as-merchantname-in-the-subaccount-environment.md
@@ -18,9 +18,7 @@ internalReference: 780767
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma subconta está processando transações, o órgão solicitante está enviando o imóvel "nome do comerciante" com o nome da conta principal. Em alguns casos, devido a este comportamento, o conector não pode autorizar as transações do lado deles, causando a perda das ordens.
diff --git a/docs/known-issues/pt/mandatory-service-working-as-optional.md b/docs/known-issues/pt/mandatory-service-working-as-optional.md
index 8c23bcbe3..8967ac1f7 100644
--- a/docs/known-issues/pt/mandatory-service-working-as-optional.md
+++ b/docs/known-issues/pt/mandatory-service-working-as-optional.md
@@ -18,9 +18,7 @@ internalReference: 872411
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar um serviço, o comerciante pode escolher se será um campo obrigatório no checkout ou não.
diff --git a/docs/known-issues/pt/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md b/docs/known-issues/pt/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md
index 034cef601..8d53844a8 100644
--- a/docs/known-issues/pt/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md
+++ b/docs/known-issues/pt/mandatory-specifications-are-not-verified-when-creating-a-product-through-api.md
@@ -18,9 +18,7 @@ internalReference: 522293
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os produtos com especificações obrigatórias não devem estar ativos se pelo menos uma dessas especificações não for preenchida ou verificada.
diff --git a/docs/known-issues/pt/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md b/docs/known-issues/pt/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md
index e1950a1d6..2dfea63f5 100644
--- a/docs/known-issues/pt/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md
+++ b/docs/known-issues/pt/manual-price-input-restricted-to-work-with-2digit-decimal-precision.md
@@ -18,9 +18,7 @@ internalReference: 627719
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A entrada "preço manual" no carrinho é restrita ao trabalho com a precisão decimal de 2 dígitos. Se a loja usar apenas uma ou nenhuma casa decimal, o campo de entrada não funcionará corretamente.
diff --git a/docs/known-issues/pt/manual-sorting-of-collections-doesnt-work-as-expected.md b/docs/known-issues/pt/manual-sorting-of-collections-doesnt-work-as-expected.md
index 5ab2cc778..496dfa6dd 100644
--- a/docs/known-issues/pt/manual-sorting-of-collections-doesnt-work-as-expected.md
+++ b/docs/known-issues/pt/manual-sorting-of-collections-doesnt-work-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 295245
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A triagem manual das coleções não funciona como esperado. Há duas maneiras de ordenar as SKUs usando uma coleção:
diff --git a/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md b/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
index 6384fe2d6..d3b37c491 100644
--- a/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
+++ b/docs/known-issues/pt/marketingdata-is-not-saved-in-orders-when-using-multiple-coupons-feature-and-utms.md
@@ -18,9 +18,7 @@ internalReference: 936458
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o recurso de vários cupons e houver cupons e utms, ou 'marketingTags', no 'orderForm', nenhum 'marketingData' é salvo no pedido.
diff --git a/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md b/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md
index 7206576fb..8efac95a4 100644
--- a/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md
+++ b/docs/known-issues/pt/marketingtags-with-null-value-when-campaign-audience-is-matched.md
@@ -18,9 +18,7 @@ internalReference: 1052895
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma conta tem um público-alvo de campanha e um usuário conectado é correspondido, o checkout usa as informações registradas na sessão, que tem apenas o ID da campanha. Em `marketingTags`, ele deveria ter o nome da campanha, mas é `nulo`, pois não há informações disponíveis na sessão.
diff --git a/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md b/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
index 6129644c7..b14bc51af 100644
--- a/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
+++ b/docs/known-issues/pt/marketplace-and-fulfillment-can-expect-different-order-values-due-to-certain-purchase-conditions.md
@@ -18,9 +18,7 @@ internalReference: 1032473
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As camadas do Marketplace e do Fulfillment podem esperar valores diferentes para o pedido, impedindo a conclusão da compra.
diff --git a/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
index ecafa901c..f0f428056 100644
--- a/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
+++ b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-manual-price-for-discounts.md
@@ -18,9 +18,7 @@ internalReference: 932657
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a conta tem isMarketplaceResponsibleForTaxes configurado, a solicitação do hub de impostos não considera preços manuais para descontos de itens.
diff --git a/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
index 87bd27dc1..e8cb5f506 100644
--- a/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
+++ b/docs/known-issues/pt/marketplace-tax-hub-request-doesnt-consider-some-discount-types.md
@@ -18,9 +18,7 @@ internalReference: 945580
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a conta tem isMarketplaceResponsibleForTaxes configurado, a solicitação do hub de impostos não considera alguns tipos de desconto: Nominal, Porcentagem e Preço máximo por item. Isso afeta o cálculo do imposto, e o preço final é maior do que o esperado.
diff --git a/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md b/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md
index 2cb4793c2..b3fdedd2b 100644
--- a/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md
+++ b/docs/known-issues/pt/mastercard-credit-card-transactions-are-being-processed-as-visa.md
@@ -18,9 +18,7 @@ internalReference: 1026263
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas transações estão sendo registradas erroneamente sob a marca Visa, quando na verdade os cartões são Mastercard. Esse problema ocorre especificamente com cartões novos, embora possamos verificar se o BIN do cartão corresponde corretamente ao regex do validador para a marca correta.
diff --git a/docs/known-issues/pt/masterdata-export-download-link-unavailable.md b/docs/known-issues/pt/masterdata-export-download-link-unavailable.md
index 8f4cd08cf..6364b6a4a 100644
--- a/docs/known-issues/pt/masterdata-export-download-link-unavailable.md
+++ b/docs/known-issues/pt/masterdata-export-download-link-unavailable.md
@@ -18,9 +18,7 @@ internalReference: 613864
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, para entidades de dados com vários campos, quando há uma tentativa de exportar uma planilha e baixá-la, por e-mail ou diretamente pela interface do usuário, o link de download não salva o arquivo em seu navegador.
diff --git a/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md b/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
index b49334ed7..61d941d91 100644
--- a/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
+++ b/docs/known-issues/pt/match-multiple-received-skus-api-returning-invalid-sellerid.md
@@ -18,9 +18,7 @@ internalReference: 506660
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API Match Multiple Received SKUs (doc: https://developers.vtex.com/vtex-rest-api/reference/match-received-skus#matchmultiple) está retornando a mensagem de erro "Invalid sellerId" para qualquer tentativa de aprovação de novos produtos, mesmo que o vendedor esteja corretamente ativo no marketplace.
diff --git a/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md b/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md
index b9ced1744..2cbfc14c4 100644
--- a/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md
+++ b/docs/known-issues/pt/matcher-converting-height-width-weight-and-length-to-01.md
@@ -18,9 +18,7 @@ internalReference: 886168
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o Matcher processa os skus no módulo de sugestões do marketplace, as informações de Altura, Largura, Peso e Comprimento estão sendo definidas como 0,1 em vez de respeitar os valores enviados pelo vendedor.
diff --git a/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md b/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
index 16192e360..4a001ba3c 100644
--- a/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
+++ b/docs/known-issues/pt/matcher-does-not-work-as-expected-when-the-productsku-name-contains-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 736164
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao integrar produtos que têm caracteres especiais no nome, como `. - + # /` , o Matcher dá uma pontuação de 50% e faz com que os produtos fiquem em Pending. Com isso, os produtos dependem de aprovação manual ou via API.
diff --git a/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md b/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md
index 2e81d0eac..8d1662981 100644
--- a/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md
+++ b/docs/known-issues/pt/max-shipping-discount-not-updating-pricetags.md
@@ -18,9 +18,7 @@ internalReference: 904190
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md b/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
index c5193f416..47367a5d3 100644
--- a/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
+++ b/docs/known-issues/pt/maximum-number-of-eligible-items-for-each-cart-more-for-less-applies-incorrect-discount-when-using-the-same-item.md
@@ -18,9 +18,7 @@ internalReference: 1073080
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar um desconto do tipo "mais por menos" junto com outra promoção que usa o "máximo de itens por carrinho" para o mesmo item, ambos se acumulando, um desconto incorreto é concedido, excedendo a configuração inicialmente configurada.
diff --git a/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md b/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
index 60651d693..c68fd902d 100644
--- a/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
+++ b/docs/known-issues/pt/maximum-quantity-setting-of-the-same-item-in-the-cart-cannot-be-changed-by-franchise-accounts.md
@@ -18,9 +18,7 @@ internalReference: 325273
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A configuração da quantidade máxima do mesmo item no carrinho não pode ser alterada por contas de franquia (vendedor whitelabel), pois ocorre em uma tela de catálogo herdada (/admin/Site/ConfigForm.aspx) - módulo que é removido das contas de franquia, pois elas herdam os produtos da conta principal.
diff --git a/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md b/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
index 6fd2d163d..f7f9a24d2 100644
--- a/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
+++ b/docs/known-issues/pt/mdv2-returns-error-504-gateway-timeout-when-we-try-to-update-a-document-passing-a-symbol-or-special-character.md
@@ -18,9 +18,7 @@ internalReference: 852966
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O comportamento da API ao tentar atualizar um documento que contém um símbolo em um campo do tipo string, como `"name": "Product1 14€"`, retornará o erro 504 Gateway timeout e não atualizará o documento.
diff --git a/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md b/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
index e79526125..37a0c7b6c 100644
--- a/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
+++ b/docs/known-issues/pt/meli-attribute-is-being-sent-to-meli-without-being-mapped-from-seller.md
@@ -18,9 +18,7 @@ internalReference: 791380
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md b/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
index ac0a8ed94..6824573ea 100644
--- a/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
+++ b/docs/known-issues/pt/meli-attributes-negro000000-integration-with-a-non-expected-behavior.md
@@ -18,9 +18,7 @@ internalReference: 660703
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md b/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md
index 7e22b20d3..d10bf58f3 100644
--- a/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md
+++ b/docs/known-issues/pt/meli-automatic-messages-mercado-livre-messages.md
@@ -18,9 +18,7 @@ internalReference: 615164
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md b/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md
index 7ccb328a7..bdb14ffd1 100644
--- a/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md
+++ b/docs/known-issues/pt/meli-bridge-orders-menu-not-showing-the-orderid-information.md
@@ -18,9 +18,7 @@ internalReference: 881733
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md b/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
index 13426ce82..bb4454d39 100644
--- a/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
+++ b/docs/known-issues/pt/meli-buybox-ads-are-not-being-paused-when-the-marketplace-ad-is-paused.md
@@ -18,9 +18,7 @@ internalReference: 910371
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-buybox-ads-not-being-linked-to-bridge-products.md b/docs/known-issues/pt/meli-buybox-ads-not-being-linked-to-bridge-products.md
index e07c3fc2e..8a7c0efd7 100644
--- a/docs/known-issues/pt/meli-buybox-ads-not-being-linked-to-bridge-products.md
+++ b/docs/known-issues/pt/meli-buybox-ads-not-being-linked-to-bridge-products.md
@@ -18,9 +18,7 @@ internalReference: 780961
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-customdata-paymentfield.md b/docs/known-issues/pt/meli-customdata-paymentfield.md
index 943ca369b..57e57a8a2 100644
--- a/docs/known-issues/pt/meli-customdata-paymentfield.md
+++ b/docs/known-issues/pt/meli-customdata-paymentfield.md
@@ -18,9 +18,7 @@ internalReference: 542992
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-error-importing-some-orders.md b/docs/known-issues/pt/meli-error-importing-some-orders.md
index 7254c45ab..f19690b21 100644
--- a/docs/known-issues/pt/meli-error-importing-some-orders.md
+++ b/docs/known-issues/pt/meli-error-importing-some-orders.md
@@ -18,9 +18,7 @@ internalReference: 664351
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 identificamos que estamos fazendo a divisão por tipo de listagem, portanto, quando tentamos a divisão, e é Fulfillment, não estamos deixando que isso aconteça.
diff --git a/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md b/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
index 107169367..d00807d1c 100644
--- a/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
+++ b/docs/known-issues/pt/meli-error-sku-integration-input-string-was-not-in-a-correct-format.md
@@ -18,9 +18,7 @@ internalReference: 664010
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns skus estão tendo um erro na integração" "A cadeia de entrada não estava em um formato correto" "A cadeia de entrada não estava em um formato correto
diff --git a/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md b/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md
index 60bfbd2e1..46cabbe01 100644
--- a/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md
+++ b/docs/known-issues/pt/meli-error-while-sending-the-order-tracking.md
@@ -18,9 +18,7 @@ internalReference: 764885
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md b/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md
index 6bbce0a1b..835784a2a 100644
--- a/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md
+++ b/docs/known-issues/pt/meli-freight-quotation-for-multiple-officialstoreids.md
@@ -18,9 +18,7 @@ internalReference: 978358
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, temos um problema com a integração do MELI em relação à API de cotação de frete do MELI, que se aplica apenas a vendedores que usam vários officialStoreIDs no MELI, mas usam apenas uma conta na VTEX usando o mesmo sellerID no MELI
diff --git a/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md b/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md
index bcc1c2acb..5f944c12b 100644
--- a/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md
+++ b/docs/known-issues/pt/meli-full-orders-not-creating-invoice-in-vtex.md
@@ -18,9 +18,7 @@ internalReference: 976614
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-images-limitation.md b/docs/known-issues/pt/meli-images-limitation.md
index 224ea4c31..9f403ce27 100644
--- a/docs/known-issues/pt/meli-images-limitation.md
+++ b/docs/known-issues/pt/meli-images-limitation.md
@@ -18,9 +18,7 @@ internalReference: 571539
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md b/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md
index 3db72388f..0fafe4be2 100644
--- a/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md
+++ b/docs/known-issues/pt/meli-incorrect-value-when-client-has-coupon-on-meli.md
@@ -18,9 +18,7 @@ internalReference: 969297
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md b/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
index cfe7d22f6..9492c4e57 100644
--- a/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
+++ b/docs/known-issues/pt/meli-integration-is-receiving-errors-from-meli-429-too-many-requests.md
@@ -18,9 +18,7 @@ internalReference: 873998
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md b/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
index 3fe9da47d..1cc457e7d 100644
--- a/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
+++ b/docs/known-issues/pt/meli-integration-listing-types-for-peru-venezuela-equador-and-uruguai.md
@@ -18,9 +18,7 @@ internalReference: 925139
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-integration-missing-billingaddress.md b/docs/known-issues/pt/meli-integration-missing-billingaddress.md
index 8a01bacdb..e5a4b1992 100644
--- a/docs/known-issues/pt/meli-integration-missing-billingaddress.md
+++ b/docs/known-issues/pt/meli-integration-missing-billingaddress.md
@@ -18,9 +18,7 @@ internalReference: 771418
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md b/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
index 8cf29e181..6f0f87bc9 100644
--- a/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
+++ b/docs/known-issues/pt/meli-integration-zipcodes-11111-meli-limaperu.md
@@ -18,9 +18,7 @@ internalReference: 826566
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-kit-stock-integration.md b/docs/known-issues/pt/meli-kit-stock-integration.md
index df5da52c0..8261af0ae 100644
--- a/docs/known-issues/pt/meli-kit-stock-integration.md
+++ b/docs/known-issues/pt/meli-kit-stock-integration.md
@@ -18,9 +18,7 @@ internalReference: 489220
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Precisamos investigar e corrigir o problema ao enviar o saldo de estoque para a MELI quando o item for um KIT. Envie o saldo de estoque do KIT ao invés do estoque do SKU.
diff --git a/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md b/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md
index 28085f562..67f2bceaf 100644
--- a/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md
+++ b/docs/known-issues/pt/meli-mapper-incorrectly-sending-product-specification-as-variation.md
@@ -18,9 +18,7 @@ internalReference: 851021
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-oms-label-printing.md b/docs/known-issues/pt/meli-oms-label-printing.md
index 7783637ea..b10b2e57e 100644
--- a/docs/known-issues/pt/meli-oms-label-printing.md
+++ b/docs/known-issues/pt/meli-oms-label-printing.md
@@ -18,9 +18,7 @@ internalReference: 546542
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Estamos tendo alguns problemas ao clicar diretamente dentro do botão "etiqueta de entrega", para ordens do Mercado Livre dentro da OMS.
diff --git a/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md b/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
index dd4c3fe5c..f69effd8f 100644
--- a/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
+++ b/docs/known-issues/pt/meli-orders-not-being-cancelled-in-vtex-oms-for-multiples-accounts-scenario.md
@@ -18,9 +18,7 @@ internalReference: 977453
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-plaintextdescriptionmeli-not-working.md b/docs/known-issues/pt/meli-plaintextdescriptionmeli-not-working.md
index 25e24a742..3bbb987b4 100644
--- a/docs/known-issues/pt/meli-plaintextdescriptionmeli-not-working.md
+++ b/docs/known-issues/pt/meli-plaintextdescriptionmeli-not-working.md
@@ -18,9 +18,7 @@ internalReference: 555122
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-promotion-center-not-linking-skus-to-promotion.md b/docs/known-issues/pt/meli-promotion-center-not-linking-skus-to-promotion.md
index 72f562ecb..dfd381ac8 100644
--- a/docs/known-issues/pt/meli-promotion-center-not-linking-skus-to-promotion.md
+++ b/docs/known-issues/pt/meli-promotion-center-not-linking-skus-to-promotion.md
@@ -18,9 +18,7 @@ internalReference: 801348
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-promotion-center.md b/docs/known-issues/pt/meli-promotion-center.md
index e298a38d3..980c4d02d 100644
--- a/docs/known-issues/pt/meli-promotion-center.md
+++ b/docs/known-issues/pt/meli-promotion-center.md
@@ -18,9 +18,7 @@ internalReference: 600922
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-promotions-ui-error.md b/docs/known-issues/pt/meli-promotions-ui-error.md
index bad421331..7b56f09b8 100644
--- a/docs/known-issues/pt/meli-promotions-ui-error.md
+++ b/docs/known-issues/pt/meli-promotions-ui-error.md
@@ -18,9 +18,7 @@ internalReference: 797143
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md b/docs/known-issues/pt/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md
index 802e66394..057b28d56 100644
--- a/docs/known-issues/pt/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md
+++ b/docs/known-issues/pt/meli-publication-in-mercado-libre-is-paused-when-a-sku-is-inactivated.md
@@ -18,9 +18,7 @@ internalReference: 557293
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md b/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md
index 285f74ac4..ab5b9362f 100644
--- a/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md
+++ b/docs/known-issues/pt/meli-size-chart-not-working-for-sizes-with-letters.md
@@ -18,9 +18,7 @@ internalReference: 867262
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md b/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md
index d2dc67130..336e3deb1 100644
--- a/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md
+++ b/docs/known-issues/pt/meli-sizechart-issue-attribute-not-valid.md
@@ -18,9 +18,7 @@ internalReference: 996639
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md b/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
index d87d6f959..ddd76aa83 100644
--- a/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
+++ b/docs/known-issues/pt/meli-sku-integration-with-object-reference-not-set-to-an-instance-of-an-object-error.md
@@ -18,9 +18,7 @@ internalReference: 657515
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns skus no Mercado Livre estão com erro de registro: "Referência de objeto não definida para uma instância de um objeto".
diff --git a/docs/known-issues/pt/meli-update-stockprice-issue.md b/docs/known-issues/pt/meli-update-stockprice-issue.md
index e1e520bb6..52c563887 100644
--- a/docs/known-issues/pt/meli-update-stockprice-issue.md
+++ b/docs/known-issues/pt/meli-update-stockprice-issue.md
@@ -18,9 +18,7 @@ internalReference: 939329
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md b/docs/known-issues/pt/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md
index 887336c5a..5391ff61f 100644
--- a/docs/known-issues/pt/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md
+++ b/docs/known-issues/pt/meli-variation-attribute-is-duplicated-allowed-unique-attributes-combinations.md
@@ -18,9 +18,7 @@ internalReference: 758331
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md b/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
index 9210f3453..683556119 100644
--- a/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
+++ b/docs/known-issues/pt/mercado-livre-ad-buybox-doesnt-update-shippingmode-for-me2.md
@@ -18,9 +18,7 @@ internalReference: 1042779
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 AD BuyBox não atualiza shipping_mode para ME2
diff --git a/docs/known-issues/pt/mercado-livre-attribute-size-is-missing.md b/docs/known-issues/pt/mercado-livre-attribute-size-is-missing.md
index ae6295682..189bf4f84 100644
--- a/docs/known-issues/pt/mercado-livre-attribute-size-is-missing.md
+++ b/docs/known-issues/pt/mercado-livre-attribute-size-is-missing.md
@@ -18,9 +18,7 @@ internalReference: 658473
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
index be52b5826..c3384b79f 100644
--- a/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
+++ b/docs/known-issues/pt/mercado-livre-bridge-bridge-isnt-logging-some-error-messages.md
@@ -18,9 +18,7 @@ internalReference: 1053742
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Erro no fluxo de atualização: o sku não está sendo registrado na ponte
diff --git a/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md b/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
index c9345a5fc..3630e0a38 100644
--- a/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
+++ b/docs/known-issues/pt/mercado-livre-bridge-orders-menu-not-showing-the-shippingid-information.md
@@ -18,9 +18,7 @@ internalReference: 1001903
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, temos um problema que afeta apenas a visibilidade de alguns pedidos MELI. O que acontece é que estamos registrando o ShipmentID no menu de ponte de pedidos, mas algumas mensagens de erro não têm o OrderID, e isso é necessário em alguns casos, pois o OrderID é a informação que os vendedores têm no Portal MELI.
diff --git a/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md b/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md
index 9eebf740f..d9b992f24 100644
--- a/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md
+++ b/docs/known-issues/pt/mercado-livre-mapper-attribute-size.md
@@ -18,9 +18,7 @@ internalReference: 592577
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md b/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md
index d2a8c439c..29df88aa7 100644
--- a/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md
+++ b/docs/known-issues/pt/mercado-livre-remove-underreview-validation-in-update-sku.md
@@ -18,9 +18,7 @@ internalReference: 890658
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Remover a validação under_review no fluxo Update SKU porque quando o vendedor aplica as ações para corrigir os casos de moderação e estes estão relacionados com o catálogo, não estamos enviando essas alterações para o MELI e, finalmente, os anúncios MELI continuam sendo moderados.
diff --git a/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md b/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
index 370f0b6ea..0fc0f7989 100644
--- a/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
+++ b/docs/known-issues/pt/mercado-livre-sku-bridge-isnt-logging-some-error-messages.md
@@ -18,9 +18,7 @@ internalReference: 1069692
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Contexto correto: Em alguns casos, o vendedor não consegue integrar a SKU, pois a mensagem de erro com o motivo pelo qual o item foi moderado não aparece corretamente no Bridge.
diff --git a/docs/known-issues/pt/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md b/docs/known-issues/pt/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md
index 42c8e505d..b25009f83 100644
--- a/docs/known-issues/pt/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md
+++ b/docs/known-issues/pt/mercadopagov1-fails-to-authorize-transactions-when-it-comes-with-phone-user-data-value-as-0.md
@@ -18,9 +18,7 @@ internalReference: 778611
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se o checkout do cliente enviar dados do usuário sem validação adequada, como um número de telefone com menos de três dígitos, estes dados são passados para o gateway como está, o que pode causar erros inesperados durante o processamento. Por exemplo, nosso analisador pode acionar uma exceção e cancelar a transação.
diff --git a/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md b/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
index 5b90b83fa..abf5cc2bf 100644
--- a/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
+++ b/docs/known-issues/pt/merchandising-rules-not-working-for-the-facet-productclusterids.md
@@ -18,9 +18,7 @@ internalReference: 1062457
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As regras de merchandising não são aplicadas à faceta "productClusterIds". Isso acontece porque essa faceta tem o comportamento especial de classificar os produtos pela ordem da coleção, em vez de regras de relevância e de merchandising.
diff --git a/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md b/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
index 93debcbdc..9d5c9031a 100644
--- a/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
+++ b/docs/known-issues/pt/merchant-not-being-able-to-open-account-for-some-clients-in-customer-credit-api.md
@@ -18,9 +18,7 @@ internalReference: 906509
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Por algum motivo, ao tentar abrir uma nova conta para clientes específicos por meio da API, ele retorna o seguinte erro:
diff --git a/docs/known-issues/pt/merchants-are-not-receiving-the-fixed-price-report.md b/docs/known-issues/pt/merchants-are-not-receiving-the-fixed-price-report.md
index f6436317c..40bd2b7b8 100644
--- a/docs/known-issues/pt/merchants-are-not-receiving-the-fixed-price-report.md
+++ b/docs/known-issues/pt/merchants-are-not-receiving-the-fixed-price-report.md
@@ -18,9 +18,7 @@ internalReference: 674353
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md b/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md
index 3e5fffd52..f22fac59d 100644
--- a/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md
+++ b/docs/known-issues/pt/message-freight-value-has-changed-is-shown-incorrectly.md
@@ -18,9 +18,7 @@ internalReference: 775515
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao remover um item do carrinho, a mensagem "Valor do frete mudou" é mostrada mesmo que o Total do frete seja o mesmo após a mudança.
diff --git a/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md b/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md
index 3e0c9c49f..bf2c101c9 100644
--- a/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md
+++ b/docs/known-issues/pt/messages-app-taking-too-long-to-return-the-informations.md
@@ -18,9 +18,7 @@ internalReference: 567305
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No processo de indexação, chamamos o aplicativo de mensagens para salvar informações traduzidas sobre os produtos. O principal problema é que as solicitações estão demorando muito para retornar e, com isso, algumas lojas que têm muitos idiomas não indexam totalmente ou têm suas indexações travadas.
diff --git a/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md b/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
index f7aa68e09..c199fa3f3 100644
--- a/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
+++ b/docs/known-issues/pt/metatagdescription-field-cannot-be-deleted-through-admin.md
@@ -18,9 +18,7 @@ internalReference: 979691
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um comportamento inconsistente no campo `MetaTagDescription` no registro do produto, que não pode ser excluído por meio do Admin, mas é possível excluir por meio da API. No Admin, ao clicar em "salvar" com esse campo vazio, o valor do campo `Description` é copiado. Esse cenário não acontece quando se usa a API, o valor é excluído corretamente.
diff --git a/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md b/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md
index 330ee2e4d..55ef61a2d 100644
--- a/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md
+++ b/docs/known-issues/pt/minicart-coupon-error-messages-only-appear-after-a-second-try.md
@@ -18,9 +18,7 @@ internalReference: 938379
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As mensagens de erro de cupom no Minicart não aparecerão na primeira vez que você tentar um cupom, mesmo que ele não exista.
diff --git a/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md b/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md
index 2e1345464..4aec68bc4 100644
--- a/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md
+++ b/docs/known-issues/pt/minicart-does-not-show-sku-specs-in-b2b-scenario.md
@@ -18,9 +18,7 @@ internalReference: 687308
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao adicionar um item ao minicart em uma loja B2B, ele não apresenta informações relacionadas às suas especificações, registradas no Catálogo.
diff --git a/docs/known-issues/pt/minicart-error-when-updating-promotion.md b/docs/known-issues/pt/minicart-error-when-updating-promotion.md
index 8a510bf34..de80c63b3 100644
--- a/docs/known-issues/pt/minicart-error-when-updating-promotion.md
+++ b/docs/known-issues/pt/minicart-error-when-updating-promotion.md
@@ -18,9 +18,7 @@ internalReference: 552633
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md b/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
index 7c542ea90..d5076cf27 100644
--- a/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
+++ b/docs/known-issues/pt/misbehaviors-for-addtocart-mutation-from-checkoutgraphql-while-sending-options-for-already-added-items.md
@@ -18,9 +18,7 @@ internalReference: 452053
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Ao utilizar o "_addToCart"_ mutação do "_checkout-graphql"_ em um carrinho onde um determinado item já foi adicionado sem "_opções_", tentar incluí-lo novamente, desta vez com "_opções_", não vai funcionar corretamente. A mutação não registrará as "_opções_" enviadas e também retornará um erro se elas estiverem relacionadas com informações de "_subscrição_".
 
diff --git a/docs/known-issues/pt/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md b/docs/known-issues/pt/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md
index 9f07e4ebf..d8b224dd8 100644
--- a/docs/known-issues/pt/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md
+++ b/docs/known-issues/pt/missing-1x-installment-option-on-checkout-with-multiple-payment-conditions-and-default-configuration-set-to-a-different-option.md
@@ -18,9 +18,7 @@ internalReference: 709971
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há mais de uma condição de pagamento configurada para um sistema de pagamento e uma condição de pagamento diferente daquela com a opção de parcelamento em 1x está configurada como padrão, a opção de parcelamento em 1x não aparece na página de checkout. Nesses casos, apenas a opção de parcelamento em 1x é removida do checkout.
diff --git a/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md b/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
index c0a5402f0..461cd2bb8 100644
--- a/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
+++ b/docs/known-issues/pt/missing-minicartbuyerid-field-causes-antifraud-to-cancel-transactions.md
@@ -18,9 +18,7 @@ internalReference: 514335
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Houve casos em que determinadas transações estavam sendo recusadas durante a análise antifraude devido ao valor nulo no campo `minicart.buyer.id`. Portanto, espera-se que o `minicart.buyer.id` seja enviado do checkout para o gateway por meio de `sendAdditionalData`. No entanto, de acordo com a arquitetura atual do checkout, não há nenhum requisito específico para fornecer esse campo em `sendAdditionalData`, e sua definição pode ou não estar disponível em um estágio posterior.
diff --git a/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md b/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
index 6d8a102ba..28847221e 100644
--- a/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
+++ b/docs/known-issues/pt/missing-translation-for-the-price-facetfilter-at-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 974840
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Intelligent Search não aplica a tradução ao nome do filtro/faceta "price" para idiomas adicionais quando consultado via REST API.
diff --git a/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md b/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
index 9fa308790..4e53fb8ec 100644
--- a/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
+++ b/docs/known-issues/pt/modal-as-generic-reason-even-this-type-of-modal-are-configured-ok.md
@@ -18,9 +18,7 @@ internalReference: 488339
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um cenário onde há modais configurados OK também na SKU e na Polícia Marítima e a simulação está mostrando problemas na configuração modal.
diff --git a/docs/known-issues/pt/modal-values-with-different-texts-between-api-and-logistics-ui.md b/docs/known-issues/pt/modal-values-with-different-texts-between-api-and-logistics-ui.md
index d50a83521..cd129158c 100644
--- a/docs/known-issues/pt/modal-values-with-different-texts-between-api-and-logistics-ui.md
+++ b/docs/known-issues/pt/modal-values-with-different-texts-between-api-and-logistics-ui.md
@@ -18,9 +18,7 @@ internalReference: 775800
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ## **Sumário***
 
diff --git a/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md b/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md
index fd615baff..3854fd3c6 100644
--- a/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md
+++ b/docs/known-issues/pt/modals-deprecated-divergences-setup-shipping-policy.md
@@ -18,9 +18,7 @@ internalReference: 445866
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um cenário relativo aos modais usados e depreciados sem igual.
diff --git a/docs/known-issues/pt/moving-categories-does-not-update-the-department-id-on-the-products.md b/docs/known-issues/pt/moving-categories-does-not-update-the-department-id-on-the-products.md
index 4257a4779..86be93660 100644
--- a/docs/known-issues/pt/moving-categories-does-not-update-the-department-id-on-the-products.md
+++ b/docs/known-issues/pt/moving-categories-does-not-update-the-department-id-on-the-products.md
@@ -18,9 +18,7 @@ internalReference: 316694
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Mover categorias na árvore de categorias, por exemplo, mover um departamento para outra categoria não atualiza o ID do departamento nos produtos.
diff --git a/docs/known-issues/pt/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md b/docs/known-issues/pt/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md
index 255557943..6d334c4d6 100644
--- a/docs/known-issues/pt/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md
+++ b/docs/known-issues/pt/moving-categories-leads-to-unexpected-behaviors-in-the-categories-tree.md
@@ -18,9 +18,7 @@ internalReference: 367136
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, esta funcionalidade pode levar a inconsistências no banco de dados da sua árvore de categorias, dependendo do tipo de movimento. Esta funcionalidade não é, portanto, recomendada até que possa ser remediada.
diff --git a/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md b/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md
index c83d008dd..01a2af9db 100644
--- a/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md
+++ b/docs/known-issues/pt/multiple-sku-promotion-api-not-working.md
@@ -18,9 +18,7 @@ internalReference: 729990
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Apesar das informações de retorno de sucesso sobre a API e o e-mail, a promoção não é criada na administração.
diff --git a/docs/known-issues/pt/my-account-receiver-name-field-doesnt-recognize-input.md b/docs/known-issues/pt/my-account-receiver-name-field-doesnt-recognize-input.md
index fedc25bcf..0aa738a7d 100644
--- a/docs/known-issues/pt/my-account-receiver-name-field-doesnt-recognize-input.md
+++ b/docs/known-issues/pt/my-account-receiver-name-field-doesnt-recognize-input.md
@@ -18,9 +18,7 @@ internalReference: 568527
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar registrar o primeiro endereço nesta conta, através de "Minha conta > direciones", a informação é exibida como "obrigatória" para entrar em "Datos del Tercero Autorizado", mas mesmo após entrar com esta informação e clicar em "Anadir Dirección" o endereço não é registrado e a mensagem de que é "obrigatória" é exibida novamente, somente após a segunda tentativa é o endereço salvo com sucesso.
diff --git a/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md b/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
index e52f45963..e68bc7370 100644
--- a/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
+++ b/docs/known-issues/pt/my-cards-footer-is-shivering-when-trying-to-add-a-new-card.md
@@ -18,9 +18,7 @@ internalReference: 1012542
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O rodapé em "Meus cartões" treme na tela quando se tenta adicionar um novo cartão.
diff --git a/docs/known-issues/pt/my-cards-is-not-working-for-some-legacy-connectors.md b/docs/known-issues/pt/my-cards-is-not-working-for-some-legacy-connectors.md
index e85307009..d0be4a7c9 100644
--- a/docs/known-issues/pt/my-cards-is-not-working-for-some-legacy-connectors.md
+++ b/docs/known-issues/pt/my-cards-is-not-working-for-some-legacy-connectors.md
@@ -18,9 +18,7 @@ internalReference: 373636
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar salvar um cartão de crédito em My Cards dentro da sessão My Account ** sem ter feito qualquer compra com esse cartão antes** ocorrerá um erro ao tentar salvar o cartão com um conector legado interno.
diff --git a/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md b/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
index 2793a31c4..d8111e0fb 100644
--- a/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
+++ b/docs/known-issues/pt/my-cards-ui-allow-customers-to-save-credit-cards-without-number-field-filled-in-the-address-information.md
@@ -18,9 +18,7 @@ internalReference: 521542
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário deseja salvar um cartão em MyAccount, o endereço é necessário e sem as informações preenchidas, o botão não faz a ação de tentar salvar o cartão. Mas esta regra não é aplicada ao campo de número do formulário de endereço, que é obrigatório, mas pode ser deixado vazio e o usuário pode salvar o cartão sem esta validação.
diff --git a/docs/known-issues/pt/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md b/docs/known-issues/pt/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md
index 65bdb4fc1..9b87c29c9 100644
--- a/docs/known-issues/pt/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md
+++ b/docs/known-issues/pt/my-credits-doesnt-show-the-paymentlink-invoice-even-if-the-field-is-set.md
@@ -18,9 +18,7 @@ internalReference: 546267
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O link do campo PaymentLink não está sendo exibido na página Meus Créditos, dentro da MyAccount, embora tenha sido configurado e disponível na página de Faturas de Crédito do Cliente, dentro da Admin.
diff --git a/docs/known-issues/pt/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md b/docs/known-issues/pt/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md
index 41cc89577..0c6b08776 100644
--- a/docs/known-issues/pt/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md
+++ b/docs/known-issues/pt/my-orders-on-my-account-error-message-ocorreu-um-erro-inesperado-estamos-trabalhando-para-resolvelo-tente-novamente-mais-tarde.md
@@ -18,19 +18,13 @@ internalReference: 356936
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md b/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
index 94821994b..dacc8213b 100644
--- a/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
+++ b/docs/known-issues/pt/my-subscription-showing-error-message-when-subscription-is-associated-with-a-pick-up-point.md
@@ -18,9 +18,7 @@ internalReference: 692523
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md b/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
index 0b0b8ffee..a50a6c9dd 100644
--- a/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
+++ b/docs/known-issues/pt/my-subscriptions-when-entering-the-address-line-2-this-appear-as-null.md
@@ -18,9 +18,7 @@ internalReference: 588046
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md b/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md
index d91f269a3..1a4d08baa 100644
--- a/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md
+++ b/docs/known-issues/pt/mycards-spinner-button-is-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 780667
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Após clicar no botão "Salvar cartão novo", os usuários esperam ver algum feedback indicando que algo está sendo processado. Infelizmente, falta a experiência atual, já que o botão não exibe a animação "spinner" esperada. Isto pode ser frustrante para os usuários e diminuir a experiência geral do usuário.
diff --git a/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md b/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
index 55936934a..da99d0f74 100644
--- a/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
+++ b/docs/known-issues/pt/mycredits-has-an-error-when-accessing-from-an-dependent-account.md
@@ -18,9 +18,7 @@ internalReference: 367276
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Existe a possibilidade de criar um dependente adicional, ao criar uma conta no Crédito ao Cliente e quando você faz isso, a conta dependente está mostrando um erro ao acessar o MyCredits (dentro de Minha Conta)
diff --git a/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md b/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
index 9dcc3cb2e..84ed75428 100644
--- a/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
+++ b/docs/known-issues/pt/nao-e-possivel-inativar-este-produto-porque-ele-possui-um-ou-mais-skus-ativos-does-not-automatically-translate-on-the-product-admin.md
@@ -18,9 +18,7 @@ internalReference: 768603
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/native-gift-card-is-adding-credit-although-it-returns-500.md b/docs/known-issues/pt/native-gift-card-is-adding-credit-although-it-returns-500.md
index 42829fcf4..15a2a16a1 100644
--- a/docs/known-issues/pt/native-gift-card-is-adding-credit-although-it-returns-500.md
+++ b/docs/known-issues/pt/native-gift-card-is-adding-credit-although-it-returns-500.md
@@ -18,9 +18,7 @@ internalReference: 760896
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Depois de realizar alguns testes empíricos, observamos que a rota /transaction na API nativa de cartão-presente às vezes retorna um código de erro 500 ao adicionar o crédito solicitado, o que é um comportamento inesperado. Além disso, notamos que a solicitação está demorando mais do que o esperado para receber uma resposta, indicando um comportamento de tempo limite. Como resultado, não há um bloqueio eficaz para garantir que o saldo do cartão não seja creditado nesse cenário.
diff --git a/docs/known-issues/pt/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md b/docs/known-issues/pt/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md
index 94c1bbbb1..4ab8eb410 100644
--- a/docs/known-issues/pt/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md
+++ b/docs/known-issues/pt/nderstand-why-some-orders-placed-at-magalu-were-as-incomplet.md
@@ -18,9 +18,7 @@ internalReference: 597771
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/negative-amounts-in-split-recipients.md b/docs/known-issues/pt/negative-amounts-in-split-recipients.md
index 018b29eed..97f1eac36 100644
--- a/docs/known-issues/pt/negative-amounts-in-split-recipients.md
+++ b/docs/known-issues/pt/negative-amounts-in-split-recipients.md
@@ -18,9 +18,7 @@ internalReference: 388580
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um cenário de mercado com pagamento dividido quando o mercado não tem comissão sobre a transação, arredondar qualquer valor de referência (buyTotal ou totalSellers) pode resultar em um valor negativo para o mercado.
diff --git a/docs/known-issues/pt/new-collections-import-does-not-handle-non-existent-productid-import.md b/docs/known-issues/pt/new-collections-import-does-not-handle-non-existent-productid-import.md
index 808be583a..6883da5ac 100644
--- a/docs/known-issues/pt/new-collections-import-does-not-handle-non-existent-productid-import.md
+++ b/docs/known-issues/pt/new-collections-import-does-not-handle-non-existent-productid-import.md
@@ -18,9 +18,7 @@ internalReference: 398602
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md b/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md
index 9f74c962c..4e7a328bd 100644
--- a/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md
+++ b/docs/known-issues/pt/new-collections-newly-released-filter-is-not-working-for-exports.md
@@ -18,19 +18,13 @@ internalReference:
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/new-collections-page-not-loading.md b/docs/known-issues/pt/new-collections-page-not-loading.md
index e4b056191..029eb4262 100644
--- a/docs/known-issues/pt/new-collections-page-not-loading.md
+++ b/docs/known-issues/pt/new-collections-page-not-loading.md
@@ -18,9 +18,7 @@ internalReference: 419729
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A conta não poderia ser capaz de carregar a página de aplicativo de coleta, o pedido `api/catalog_system/pvt/collection/search/?an=&page=1&pageSize=10&orderByAsc=false` poderia retornar 500, devido ao timeout:
diff --git a/docs/known-issues/pt/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md b/docs/known-issues/pt/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md
index 492ff3e0d..97cdf2ba0 100644
--- a/docs/known-issues/pt/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md
+++ b/docs/known-issues/pt/new-ui-do-not-shows-on-orders-the-correct-delivery-window-estimated.md
@@ -18,9 +18,7 @@ internalReference: 620668
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Na nova IU, alguns pedidos não mostram corretamente a entrega estimada.
 
diff --git a/docs/known-issues/pt/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md b/docs/known-issues/pt/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md
index 3f061bf97..eab3d9fcb 100644
--- a/docs/known-issues/pt/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md
+++ b/docs/known-issues/pt/new-ui-does-not-show-items-pending-to-invoice-in-orders-with-partial-or-total-invoice.md
@@ -18,9 +18,7 @@ internalReference: 646253
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md b/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
index 2702a06b6..e37cebb6d 100644
--- a/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
+++ b/docs/known-issues/pt/new-ui-does-not-show-the-customers-id-document-for-example-cpf.md
@@ -18,9 +18,7 @@ internalReference: 713480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Nova UI não mostra o documento de identificação do cliente nos pedidos. Por exemplo, como CPF, isso acontece porque a política comercial de contas tem outro país configurado.
diff --git a/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md b/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
index 07c8c54ad..e3241792e 100644
--- a/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
+++ b/docs/known-issues/pt/new-ui-does-not-show-the-invoiced-value-on-return-items-page.md
@@ -18,9 +18,7 @@ internalReference: 664838
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Nova IU não está mostrando na página Itens de Retorno o valor total já faturado.
diff --git a/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md b/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
index ac410daed..31eee4685 100644
--- a/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
+++ b/docs/known-issues/pt/no-delivery-window-can-be-created-due-to-inconsistence-in-estimatedate-and-lastdeliveryday-for-high-timecost.md
@@ -18,9 +18,7 @@ internalReference: 995491
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/no-feedback-to-the-user-when-something-goes-wrong.md b/docs/known-issues/pt/no-feedback-to-the-user-when-something-goes-wrong.md
index 92477673a..64e702947 100644
--- a/docs/known-issues/pt/no-feedback-to-the-user-when-something-goes-wrong.md
+++ b/docs/known-issues/pt/no-feedback-to-the-user-when-something-goes-wrong.md
@@ -18,19 +18,13 @@ internalReference: 339072
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md b/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
index 6520beeeb..89138c337 100644
--- a/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
+++ b/docs/known-issues/pt/nominal-discount-based-on-formula-not-working-as-expected-with-subtraction-operations.md
@@ -18,9 +18,7 @@ internalReference: 886980
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar uma promoção usando o desconto nominal com base na fórmula, o comerciante pode usar as seguintes operações de acordo com esta documentação: https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV
diff --git a/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md b/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
index db9508aca..ae6c73725 100644
--- a/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
+++ b/docs/known-issues/pt/nominal-discount-is-not-being-distributed-among-all-items-in-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 334130
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md b/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
index 33dae2776..e3ccbb78d 100644
--- a/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
+++ b/docs/known-issues/pt/nominal-discount-more-for-less-split-for-second-item-incorrect-discount.md
@@ -18,9 +18,7 @@ internalReference: 1071119
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao configurar uma promoção de desconto nominal acumulada com a promoção "mais por menos", quando há um desconto na promoção "mais por menos" apenas para 1 de 2 itens, isso leva a um desconto incorreto no segundo item do pedido devido à divisão do checkout.
diff --git a/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md b/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
index f8f67c07e..b1fab5cbf 100644
--- a/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
+++ b/docs/known-issues/pt/not-able-to-open-proper-detached-sku-on-pdp-in-a-new-tab.md
@@ -18,9 +18,7 @@ internalReference: 871848
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o recurso de desanexação para dividir produtos por alguma especificação de SKU e tentar abrir uma nova guia do PLP para o PDP, ele não reconhece o parâmetro de propriedade que está sendo passado para o URL para selecionar o SKU correto, apenas exibe o SKU adequado ao abrir na mesma guia.
diff --git a/docs/known-issues/pt/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md b/docs/known-issues/pt/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md
index ee581a380..8957d1d91 100644
--- a/docs/known-issues/pt/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md
+++ b/docs/known-issues/pt/not-all-skus-are-returned-on-the-productsku-specification-spreadsheet.md
@@ -18,9 +18,7 @@ internalReference: 649316
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Este comportamento acontece quando uma categoria tem muitas especificações e muitos skus. Dessa forma, ao exportar a planilha, eventualmente o limite de excelência será atingido (cerca de 65k).
diff --git a/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md b/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
index 776b4289c..9ef18c801 100644
--- a/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
+++ b/docs/known-issues/pt/not-possible-to-upload-new-mediadocument-in-a-development-workspace-when-entity-has-more-than-10k-documents.md
@@ -18,9 +18,7 @@ internalReference: 795940
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md b/docs/known-issues/pt/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md
index e4a03f885..e08959544 100644
--- a/docs/known-issues/pt/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md
+++ b/docs/known-issues/pt/notes-not-shown-on-order-detail-ui-when-exceeding-limit.md
@@ -18,9 +18,7 @@ internalReference: 514992
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md b/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
index 5667de272..e273eb880 100644
--- a/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
+++ b/docs/known-issues/pt/notifyme-report-generates-a-corrupted-file-when-there-are-no-skus-found.md
@@ -18,9 +18,7 @@ internalReference: 956264
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o relatório "Notifique-me" não tiver SKUs, a tentativa de exportá-lo gerará um arquivo corrompido para o Excel
diff --git a/docs/known-issues/pt/nps-we-arent-accepting-response-with-more-than-65536-characters.md b/docs/known-issues/pt/nps-we-arent-accepting-response-with-more-than-65536-characters.md
index 6439f1664..9cd011f3f 100644
--- a/docs/known-issues/pt/nps-we-arent-accepting-response-with-more-than-65536-characters.md
+++ b/docs/known-issues/pt/nps-we-arent-accepting-response-with-more-than-65536-characters.md
@@ -18,9 +18,7 @@ internalReference: 317389
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Não estamos aceitando resposta NPS com mais de 65536 caracteres
diff --git a/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md b/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
index c2c8b5b95..874b2f694 100644
--- a/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
+++ b/docs/known-issues/pt/number-of-itens-on-pricing-filter-does-not-correspond-to-correct-number.md
@@ -18,9 +18,7 @@ internalReference: 371405
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na IU de Preços, somos capazes de filtrar por marca ou categoria. Depois de fazer um filtro, a IU retorna apenas os produtos no filtro, mas o total de itens retornados no menu é na verdade o total sem nenhum filtro, e os dados mostrados são filtrados como esperado.
diff --git a/docs/known-issues/pt/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md b/docs/known-issues/pt/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md
index 582c5e8bd..2196eb6c1 100644
--- a/docs/known-issues/pt/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md
+++ b/docs/known-issues/pt/offers-management-sku-status-is-not-reliable-in-vtexvtex-integrations.md
@@ -18,9 +18,7 @@ internalReference: 745738
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Atualmente o sistema de gerenciamento de ofertas mostra o status dos skus enviados de um vendedor para um mercado e suas interações e logs de ações como atualizações de preço e estoque.
 
diff --git a/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md b/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
index 1e4b1b28c..7880f6c93 100644
--- a/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
+++ b/docs/known-issues/pt/omnishipping-component-will-not-fill-the-pickupreceiver-field-when-the-client-first-informs-an-address-for-delivery.md
@@ -18,9 +18,7 @@ internalReference: 945896
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md b/docs/known-issues/pt/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md
index a1ecb872d..bb17ddd75 100644
--- a/docs/known-issues/pt/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md
+++ b/docs/known-issues/pt/on-list-orders-pages-the-export-orders-is-not-working-when-the-filter-selected-has-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 662821
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A nova IU tem uma limitação para exportar alguns pedidos uma vez que o filtro selecionado tem no nome um exemplo de caráter especial ("&" e "á" ou "ú") acontece porque mesmo a nova IU pode filtrar os pedidos que ela chama de antiga rota OMS para exportar os pedidos.
diff --git a/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md b/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
index b30c67453..45f3244d4 100644
--- a/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
+++ b/docs/known-issues/pt/on-my-account-the-address-edition-with-red-information-of-required-field-appears-even-after-filled-until-save-data.md
@@ -18,9 +18,7 @@ internalReference: 870891
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na página de edição My Address (Meu endereço) de Minha conta, mesmo que o endereço seja preenchido, a informação vermelha de "Campo obrigatório" aparece até que os dados sejam salvos.
diff --git a/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md b/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
index f82a5c081..585fed016 100644
--- a/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
+++ b/docs/known-issues/pt/on-the-order-placed-page-the-datalayer-only-captures-the-information-of-the.md
@@ -18,9 +18,7 @@ internalReference: 727339
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Quando a compra é concluída, o cliente vai para a página conhecida como **Order Placed**, nesta página temos um **Indicar evento de captura de pedido***(`RequestType: "orderPlaced"`) de nossa plataforma que captura alguns detalhes do pedido e serve para alimentar a **DataLayer*** com informações.
 
diff --git a/docs/known-issues/pt/oorderbypriceasc-could-bring-the-wrong-order.md b/docs/known-issues/pt/oorderbypriceasc-could-bring-the-wrong-order.md
index 6acb0371b..baa0d7832 100644
--- a/docs/known-issues/pt/oorderbypriceasc-could-bring-the-wrong-order.md
+++ b/docs/known-issues/pt/oorderbypriceasc-could-bring-the-wrong-order.md
@@ -18,9 +18,7 @@ internalReference: 582861
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O=OrderByPriceASC pode usar uma política errada para pedir preços
diff --git a/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md b/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
index ea00a3719..ab146d49c 100644
--- a/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
+++ b/docs/known-issues/pt/oorderbypriceasc-or-orderbypricedesc-could-bring-the-wrong-order.md
@@ -18,9 +18,7 @@ internalReference: 582861
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 **O=OrderByPriceASC** (ou **OrderByPriceDESC**) pode usar a política errada para pedir preços. Além disso, como o preço indexado tem apenas uma casa decimal, a segunda casa decimal do preço não será considerada.
diff --git a/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md b/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md
index 0e3460367..1d89ca26d 100644
--- a/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md
+++ b/docs/known-issues/pt/openclose-modal-hook-affects-all-modals-on-the-page.md
@@ -18,9 +18,7 @@ internalReference: 1042165
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao abrir/fechar um modal, a ação afeta todos os modais da página
diff --git a/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md b/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
index 0ff60c6ba..692bb34a1 100644
--- a/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
+++ b/docs/known-issues/pt/operations-cannot-be-performed-correctly-due-to-null-documenttype-field.md
@@ -18,9 +18,7 @@ internalReference: 697107
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns provedores precisam necessariamente que `documentType` seja diferente de `null`, ou seja, que seja preenchido corretamente para realizar algumas operações de pagamento.
diff --git a/docs/known-issues/pt/ord-reset-not-logging-out-other-sessions.md b/docs/known-issues/pt/ord-reset-not-logging-out-other-sessions.md
index 90cbefaf7..68c5d9bfd 100644
--- a/docs/known-issues/pt/ord-reset-not-logging-out-other-sessions.md
+++ b/docs/known-issues/pt/ord-reset-not-logging-out-other-sessions.md
@@ -18,9 +18,7 @@ internalReference: 530461
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md b/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md
index b73fcf00a..9777462f4 100644
--- a/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md
+++ b/docs/known-issues/pt/order-again-from-b2b-orders-history-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference: 819920
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o aplicativo B2B Orders History, a funcionalidade Order Again não funciona.
diff --git a/docs/known-issues/pt/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md b/docs/known-issues/pt/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md
index ed140cbcc..3b71ba71e 100644
--- a/docs/known-issues/pt/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md
+++ b/docs/known-issues/pt/order-approved-in-the-marketplace-but-not-integrated-into-vtex.md
@@ -18,9 +18,7 @@ internalReference: 547809
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md b/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md
index 1fc191d16..61e49caf5 100644
--- a/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md
+++ b/docs/known-issues/pt/order-authorization-lessthan-100-goes-with-the-flow.md
@@ -18,9 +18,7 @@ internalReference: 983031
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Identificamos que quando o sistema de Autorização de Pedidos (OrderAuth) é configurado com o valor "lessThan: 100", no "Rules-list.CreateDoEffect" , ele não consegue entender que é menor ou igual a 100%, apenas que é menor que 100% e quando o pedido tem um desconto de 100%, o sistema autoriza que o pedido siga o fluxo normal.
diff --git a/docs/known-issues/pt/order-cannot-be-created-when-seller-has-a-different-country-code.md b/docs/known-issues/pt/order-cannot-be-created-when-seller-has-a-different-country-code.md
index effeead32..3d4d65f83 100644
--- a/docs/known-issues/pt/order-cannot-be-created-when-seller-has-a-different-country-code.md
+++ b/docs/known-issues/pt/order-cannot-be-created-when-seller-has-a-different-country-code.md
@@ -18,9 +18,7 @@ internalReference: 763955
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um mercado, quando há um vendedor configurado com um Código de País diferente, o serviço de atendimento considerará o Código de País do vendedor ao fazer o pedido. Isso pode gerar um erro se o Código de País do vendedor definir campos obrigatórios diferentes dos do mercado.
diff --git a/docs/known-issues/pt/order-cant-be-created-due-to-invalid-credit-card.md b/docs/known-issues/pt/order-cant-be-created-due-to-invalid-credit-card.md
index 5a158b743..be1805910 100644
--- a/docs/known-issues/pt/order-cant-be-created-due-to-invalid-credit-card.md
+++ b/docs/known-issues/pt/order-cant-be-created-due-to-invalid-credit-card.md
@@ -18,9 +18,7 @@ internalReference: 607742
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A criação de uma ordem pode falhar com a exceção genérica "_Um erro de comunicação com gateway ocorreu e os dados de pagamento da transação {id} não foram recebidos com sucesso_", que têm causas de raiz diferentes. Uma delas estará relacionada à exceção interna "_As informações solicitadas da conta não existem_", que podem ser vistas no histórico da transação/pagamento relacionado ao pedido incompleto.
diff --git a/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md b/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md
index 9af6c8649..d8ce2fedc 100644
--- a/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md
+++ b/docs/known-issues/pt/order-card-info-causing-confusing-on-status.md
@@ -18,9 +18,7 @@ internalReference: 619778
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pedidos sobre o status Manuseio na nova visão UI, tem um ditado de informação de cartão (Pedido faturado), e é confuso para o cliente.
diff --git a/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md b/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
index 1e1fd5821..6b83f071f 100644
--- a/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
+++ b/docs/known-issues/pt/order-creation-failed-due-to-price-divergence-on-fulfillment-layer.md
@@ -18,9 +18,7 @@ internalReference: 512393
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-doesnt-update-status-in-oms.md b/docs/known-issues/pt/order-doesnt-update-status-in-oms.md
index 695bb96cc..8e34b8360 100644
--- a/docs/known-issues/pt/order-doesnt-update-status-in-oms.md
+++ b/docs/known-issues/pt/order-doesnt-update-status-in-oms.md
@@ -18,9 +18,7 @@ internalReference: 421529
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md b/docs/known-issues/pt/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md
index d68e329d6..343357f8d 100644
--- a/docs/known-issues/pt/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md
+++ b/docs/known-issues/pt/order-export-report-does-not-work-when-there-are-some-order-with-big-payload-on-the-list.md
@@ -18,9 +18,7 @@ internalReference: 832429
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exportação de pedidos não funciona corretamente porque a tarefa de exportação é cancelada quando há um pedido na lista com grande carga útil, por exemplo, no caso de um pedido com mais de 500 itens no json.
diff --git a/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md b/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
index 67001b9ae..a0b671d5d 100644
--- a/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
+++ b/docs/known-issues/pt/order-export-report-is-not-working-properly-due-double-space-on-promotion-name.md
@@ -18,9 +18,7 @@ internalReference: 786216
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O sistema de relatório de pedidos atualmente não consegue criar um arquivo a partir de filtros de promoção que contêm espaços duplos em seus nomes. Ao tentar criar o relatório, o sistema gera um erro e a exportação não é realizada, resultando na mensagem "_Exportação concluída. 0 pedidos foram enviados para seu e-mail"_.
diff --git a/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md b/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
index 8e2a19c36..ca6c2f000 100644
--- a/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
+++ b/docs/known-issues/pt/order-filter-doesnt-work-properly-due-to-double-quotes-in-the-promotion-name-or-sku-name.md
@@ -18,9 +18,7 @@ internalReference: 1045623
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o sistema de filtro de pedidos não retorna os pedidos com promoções que contenham aspas duplas `"` em seus nomes, o que também se aplica ao nome da SKU.
diff --git a/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md b/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md
index 75ae372c0..21f15cd48 100644
--- a/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md
+++ b/docs/known-issues/pt/order-not-notified-carrier-leaves-label-barcode-incomplete.md
@@ -18,9 +18,7 @@ internalReference: 872530
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os clientes que usam transportadoras parceiras da Shipping Network, ao solicitarem a emissão de etiquetas no Ready to Ship, podem receber o arquivo com o código de barras incompleto, o que pode impedir que o pacote seja postado.
diff --git a/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md b/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md
index 27fd4c20a..666546ca5 100644
--- a/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md
+++ b/docs/known-issues/pt/order-partial-return-triggered-the-transaction-total-refund.md
@@ -18,9 +18,7 @@ internalReference: 377044
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md b/docs/known-issues/pt/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md
index c0b037302..fc264fa47 100644
--- a/docs/known-issues/pt/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md
+++ b/docs/known-issues/pt/order-refund-email-not-getting-sent-when-additional-amount-is-refunded-using-new-ui-oms.md
@@ -18,9 +18,7 @@ internalReference: 563300
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma ordem é devolvida pelo Marketplace através da "nova IU" e um valor "adicional" é inserido na "nova IU", ela gera um cartão de presente erroneamente e com isso, o Checkout retorna um erro dizendo "que não há valor a ser revertido e o e-mail transacional "vtexcommerce-order-refunded" não é enviado para o cliente final.
diff --git a/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md b/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
index 3c81d6967..bc958fec0 100644
--- a/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
+++ b/docs/known-issues/pt/order-replacement-feature-doesnt-work-when-the-replaced-cart-and-original-order-have-the-same-value.md
@@ -18,9 +18,7 @@ internalReference: 866622
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O recurso de substituição de pedidos não funciona quando o carrinho substituído tem o mesmo valor do pedido original e o sistema de pagamento é "Reutilizar pagamento".
diff --git a/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md b/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
index 69b1c7650..dcfa9ba7d 100644
--- a/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
+++ b/docs/known-issues/pt/order-report-inconsistency-when-tid-field-is-duplicated-in-the-connectorresponses-field-from-get-payment-details-api.md
@@ -18,9 +18,7 @@ internalReference: 895664
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os conectores dessa lista precisam salvar mais campos para o conector que funciona com o aplicativo "Venda direta" - Vendas. Especificamente, para os conectores listados abaixo, e somente para eles, todo o conteúdo do payload deve ser direcionado para o campo "`connectorResponses`". Isso resulta em uma duplicação do campo "`tid`", que já existe em "`connectorResponses`". Embora essa duplicação não represente um problema em termos do ciclo de vida da transação, ela cria uma inconsistência ao gerar relatórios a partir da página do pedido.
diff --git a/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md b/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
index 4217221a7..a84175e49 100644
--- a/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
+++ b/docs/known-issues/pt/order-stuck-at-seller-status-cancellationrequestdeniedffm.md
@@ -18,9 +18,7 @@ internalReference: 1004978
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Identificamos que alguns vendedores, na estrutura do vendedor e do marketplace da VTEX, ao solicitarem o cancelamento, recusam esse cancelamento por meio da interface do usuário ou chamam a API "cancellation-request-denied-ffm", como se estivessem negando a própria solicitação de cancelamento, por algum motivo, a solicitação para negar o cancelamento se sobrepõe à solicitação de cancelamento.
diff --git a/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md b/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
index 145b955a9..0265cef55 100644
--- a/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
+++ b/docs/known-issues/pt/order-stuck-in-payment-pending-status-due-to-missing-payment-approved-notification.md
@@ -18,9 +18,7 @@ internalReference: 1031035
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md b/docs/known-issues/pt/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md
index 94b8bc86d..a9e032996 100644
--- a/docs/known-issues/pt/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md
+++ b/docs/known-issues/pt/order-with-change-itens-cannot-be-invoiced-referencing-the-items.md
@@ -18,9 +18,7 @@ internalReference: 784171
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md b/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
index 3b3b97b13..98baf66a7 100644
--- a/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
+++ b/docs/known-issues/pt/order-with-interest-has-problems-when-trying-to-return-all-the-items-and-refund-the-total-payment.md
@@ -18,9 +18,7 @@ internalReference: 376077
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ### **Resumo**
 
diff --git a/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md b/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
index 764db3f5f..9aceea1fb 100644
--- a/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
+++ b/docs/known-issues/pt/order-with-no-subscription-created-and-no-email-of-new-orders-on-cases-related-to-payment-method-using-conectors-like-payment-app-or-redirect.md
@@ -18,9 +18,7 @@ internalReference: 529143
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para pedidos com método de pagamento usando conectores como aplicativo de pagamento ou redirecionamento, não há GatewayCallback para Checkout, que é responsável por criar a assinatura e enviar um e-mail de novo pedido.
diff --git a/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md b/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md
index fb70c283c..ef5996185 100644
--- a/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md
+++ b/docs/known-issues/pt/order-with-status-of-canceled-but-the-payment-remains-authorized.md
@@ -18,9 +18,7 @@ internalReference: 420019
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns casos em que o pedido é incompleto ou cancelado quando há alguma falha de comunicação com o Gateway, o pagamento permanece autorizado e/ou aprovado, não entrando no fluxo de cancelamento e o valor pago não é reembolsado automaticamente. Além disso, e-mails transacionais podem ser enviados acidentalmente, o que também permite o pagamento de boletos bancários, pois a URL irá junto.
diff --git a/docs/known-issues/pt/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md b/docs/known-issues/pt/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md
index cc95dceac..419a5a9c3 100644
--- a/docs/known-issues/pt/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md
+++ b/docs/known-issues/pt/order-with-status-of-verifying-invoice-does-not-update-to-invoiced.md
@@ -18,9 +18,7 @@ internalReference: 500245
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido a uma inconsistência, há uma diferença entre o que foi realmente capturado e o que foi solicitado para a captura. Tornando impossível a fatura do pedido.
diff --git a/docs/known-issues/pt/order-xxx-with-invalid-status.md b/docs/known-issues/pt/order-xxx-with-invalid-status.md
index 4868f4bd9..b53982b45 100644
--- a/docs/known-issues/pt/order-xxx-with-invalid-status.md
+++ b/docs/known-issues/pt/order-xxx-with-invalid-status.md
@@ -18,9 +18,7 @@ internalReference: 514613
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md b/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
index b4cd79fea..4ea20dbfe 100644
--- a/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
+++ b/docs/known-issues/pt/orderform-api-preventing-the-shipping-method-selection-for-the-same-item-under-different-sellers.md
@@ -18,9 +18,7 @@ internalReference: 742139
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Embora um formulário de pedido ofereça suporte para que a mesma SKU seja adicionada várias vezes por meio de diferentes vendedores, ele não permite que o método de envio (SLA) seja selecionado individualmente, onde a logística de um vendedor é completamente independente dos outros.
diff --git a/docs/known-issues/pt/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md b/docs/known-issues/pt/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md
index 4e07bb473..64f065c34 100644
--- a/docs/known-issues/pt/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md
+++ b/docs/known-issues/pt/orderform-cant-be-retrieved-after-modifying-item-attachments-in-the-catalog.md
@@ -18,9 +18,7 @@ internalReference: 320044
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Após alterar (atualizar ou apagar) alguns itens anexos no catálogo de produtos, se você já tiver algum carrinho/forma de pedido que se refere a itens com anexo específico, o orderForm não pode mais ser carregado.
diff --git a/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md b/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
index a06a7584a..24595763c 100644
--- a/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
+++ b/docs/known-issues/pt/orderform-chk-api-suggesting-invalid-scheduled-delivery-that-cant-be-used.md
@@ -18,9 +18,7 @@ internalReference: 298665
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um carrinho/formulário de pedido tem vários itens com entrega programada do mesmo vendedor, as opções programadas com o mesmo ID (consideradas o mesmo método de envio) precisam ter as mesmas janelas de entrega entre elas. Se não houver interseção, o método de envio será descartado para alguns itens.
diff --git a/docs/known-issues/pt/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md b/docs/known-issues/pt/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md
index 378fd602b..f86770506 100644
--- a/docs/known-issues/pt/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md
+++ b/docs/known-issues/pt/orderform-not-resilient-to-changes-in-itemattachment-and-offerings.md
@@ -18,9 +18,7 @@ internalReference: 334191
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O OrderForm é sensível à mudança ou remoção de um item do catálogo de produtos. Se um itemAttachment deixar de existir ou começar a ter outro padrão de validação, um orderForm que já tenha dados antigos se tornará inacessível, e não será possível prosseguir com o fluxo de compra.
diff --git a/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md b/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md
index 97f9f184c..646b5f6e1 100644
--- a/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md
+++ b/docs/known-issues/pt/orderform-not-returning-customers-data-even-for-authorized-credentials.md
@@ -18,9 +18,7 @@ internalReference: 582070
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Interagir com um orderForm na situação específica em que os dados do cliente foram importados automaticamente após o login removerá seus dados do orderForm, mesmo para "superusuários", identificados por suas appKeys.
diff --git a/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md b/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md
index af76e1540..c0dd673a8 100644
--- a/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md
+++ b/docs/known-issues/pt/orderform-not-updating-after-order-is-placed.md
@@ -18,9 +18,7 @@ internalReference: 1056870
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md b/docs/known-issues/pt/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md
index 503188b20..f347ea875 100644
--- a/docs/known-issues/pt/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md
+++ b/docs/known-issues/pt/orderform-remains-with-credit-card-that-were-removed-via-myaccount-page.md
@@ -18,9 +18,7 @@ internalReference: 276823
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A remoção de um cartão de crédito usando a página da minha conta não atualiza o formulário de pedido, que manteria um cartão de crédito que não existe mais.
diff --git a/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved.md b/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved.md
index 0e73c4b3d..48e766be0 100644
--- a/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved.md
+++ b/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved.md
@@ -18,9 +18,7 @@ internalReference: 525127
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Quando você muda o pedido de produtos ou campos de SKUs em uma categoria diferente da principal, após clicar no botão de ordenação as mudanças não são salvas e os campos alterados não aparecem após a página ser recarregada.
 
diff --git a/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved1.md b/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved1.md
index d40687067..0dc745d4f 100644
--- a/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved1.md
+++ b/docs/known-issues/pt/ordering-of-product-fields-and-skus-is-not-saved1.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você muda o pedido de produtos ou campos de SKUs em uma categoria diferente da principal, após clicar no botão de ordenação as mudanças não são salvas e os campos alterados não aparecem após a página ser recarregada.
diff --git a/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md b/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md
index f28dce030..14572f8e2 100644
--- a/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md
+++ b/docs/known-issues/pt/ordering-of-specification-groups-from-the-root-category-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 634129
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando grupos de especificação são criados na categoria raiz, não é possível reordená-los por Admin ou API
diff --git a/docs/known-issues/pt/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md b/docs/known-issues/pt/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md
index 2fe7bc79c..2edc1e480 100644
--- a/docs/known-issues/pt/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md
+++ b/docs/known-issues/pt/orders-for-gift-items-arent-canceled-if-the-payment-is-refused-for-the-regular-items-order.md
@@ -18,9 +18,7 @@ internalReference: 679598
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As ordens são independentes quando não compartilham a mesma transação de pagamento. Pedidos criados para preencher apenas o item de presente através de um vendedor diferente dos outros itens de uma compra não têm nenhuma transação de pagamento porque são gratuitos.
diff --git a/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md b/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
index 88fd863c8..67dfa7b93 100644
--- a/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
+++ b/docs/known-issues/pt/orders-invoiced-at-vtex-but-that-dont-update-the-invoice-at-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 577219
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pedidos faturados na VTEX mas que não atualizam a fatura na Netshoes
diff --git a/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md b/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
index b722e6f52..3ae5d7285 100644
--- a/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
+++ b/docs/known-issues/pt/orders-invoicing-calculation-using-input-invoice-value-in-output-invoice-validation.md
@@ -18,9 +18,7 @@ internalReference: 930491
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Durante o processo de envio de faturas, é possível que o usuário envie faturas de saída e de entrada, mas se forem feitas duas faturas parciais em um pedido, uma de saída e outra de entrada, o sistema soma esses valores para validar se o pedido pode receber uma nova fatura, impossibilitando que pedidos cujo item foi faturado e depois devolvido não tenham seu valor total faturado.
diff --git a/docs/known-issues/pt/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md b/docs/known-issues/pt/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md
index f3583ea9d..da06d40a8 100644
--- a/docs/known-issues/pt/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md
+++ b/docs/known-issues/pt/orders-seller-1-has-no-notifications-on-hook-type-fromorders-for-state-payment-approved.md
@@ -18,9 +18,7 @@ internalReference: 640925
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Encomendas Vendedor 1, onde o MKT e FFMT está na mesma conta, não tem notificações sobre o tipo de gancho de Encomendas para o estado "Pagamento-Aprovado".
diff --git a/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md b/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md
index c34e51525..b14655ff3 100644
--- a/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md
+++ b/docs/known-issues/pt/orders-with-asterisks-in-the-address-and-profile.md
@@ -18,9 +18,7 @@ internalReference: 360783
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há pedidos em que `invoiceAddress`, `shippingAddress` ou `clientProfileData` estão sendo enviados como "mascarados" em vez do endereço real. Esse comportamento ocorre quando um usuário conclui a compra com um formulário de pedido que contém dados mascarados que são "stringificados". Como esses campos são de cadeia de caracteres, os dados do pedido são preenchidos com a máscara '***'.
diff --git a/docs/known-issues/pt/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md b/docs/known-issues/pt/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md
index ca74ec23d..e02862485 100644
--- a/docs/known-issues/pt/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md
+++ b/docs/known-issues/pt/orders-with-change-sellers-executed-is-not-respecting-the-cancellation-grace-period.md
@@ -18,9 +18,7 @@ internalReference: 656815
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pedidos com vendedor de mudança, tem o pedido de respeitabilidade no primeiro vendedor cancelado e um novo pedido no segundo vendedor será criado. Se mesmo o novo pedido estiver fora do período de carência de Cancelamento, o usuário ainda poderá cancelar o pedido.
diff --git a/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md b/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
index 6980ebf7f..5583e8d25 100644
--- a/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
+++ b/docs/known-issues/pt/orders-with-items-on-array-marketplaceitems-is-not-opening-on-new-ui-admin.md
@@ -18,9 +18,7 @@ internalReference: 656821
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md b/docs/known-issues/pt/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md
index a3477a61c..658448ea1 100644
--- a/docs/known-issues/pt/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md
+++ b/docs/known-issues/pt/orders-with-kit-in-newui-the-kit-id-is-being-displayed-where-it-should-show-the-sku-id.md
@@ -18,9 +18,7 @@ internalReference: 618388
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pedidos com KIT, em NEW_UI o KIT ID está sendo exibido, onde deve mostrar o SKU ID.
diff --git a/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md b/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md
index 2a9a27c2a..89a124338 100644
--- a/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md
+++ b/docs/known-issues/pt/orders-without-invoiceaddress-created-through-native-ui.md
@@ -18,9 +18,7 @@ internalReference: 306140
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns casos, ainda é possível criar pedidos sem o `invoiceAddress` por meio da interface de checkout.
diff --git a/docs/known-issues/pt/orders-without-some-details-in-the-shipping-sla-object.md b/docs/known-issues/pt/orders-without-some-details-in-the-shipping-sla-object.md
index f22ffe45f..103818c69 100644
--- a/docs/known-issues/pt/orders-without-some-details-in-the-shipping-sla-object.md
+++ b/docs/known-issues/pt/orders-without-some-details-in-the-shipping-sla-object.md
@@ -18,9 +18,7 @@ internalReference: 575219
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns pedidos de vendedores nativos (incluindo o "vendedor 1") foram relatados como não devolvendo alguns detalhes sobre o objeto SLA de envio, como o "transitTime" ou mesmo "deliveryIds". Mas as informações estão disponíveis no pedido de cumprimento (do lado do vendedor).
diff --git a/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md b/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md
index 3b2bfbbd4..4b57ea0b4 100644
--- a/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md
+++ b/docs/known-issues/pt/ordination-of-images-when-uploading-a-new-version-not-working.md
@@ -18,9 +18,7 @@ internalReference: 739814
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O filtro de pedidos no editor CMS/Site quando se carrega uma nova imagem não está funcionando corretamente
diff --git a/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
index 8b9bf0a32..a2cf3128a 100644
--- a/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/pt/outdated-elo-regex-is-causing-us-to-misidentify-some-bins.md
@@ -18,9 +18,7 @@ internalReference: 1015043
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns BINs não estão sendo identificados corretamente no checkout. A bandeira do cartão é determinada por um regex que pode ficar desatualizado, levando a marcas de cartão não identificadas ou identificadas incorretamente.
diff --git a/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md b/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
index a88ccca2e..78525e7a7 100644
--- a/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
+++ b/docs/known-issues/pt/outdated-indexed-information-when-performing-2-product-changes-in-a-row.md
@@ -18,9 +18,7 @@ internalReference: 907428
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para lojas que usam o mecanismo de pesquisa legado, se duas alterações nos dados de um produto forem feitas em uma sucessão rápida (ou seja, você inativou um produto e o reativou logo em seguida) e a última alteração retornar as informações do produto para o que era antes, o estado desse item pode ficar preso na primeira alteração, pois a última não é reconhecida corretamente.
diff --git a/docs/known-issues/pt/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md b/docs/known-issues/pt/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md
index 9108d4cde..129830880 100644
--- a/docs/known-issues/pt/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md
+++ b/docs/known-issues/pt/outdated-locale-zones-in-guatemalas-billing-address-on-the-checkout-page.md
@@ -18,9 +18,7 @@ internalReference: 373603
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os clientes guatemaltecos informaram que o formulário de endereço para faturamento está desatualizado. A causa principal é algumas mudanças locais de zona. A atualização já foi implementada no endereço de embarque e precisa ser feita também no endereço de faturamento.
diff --git a/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md b/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
index 09d6d0968..1ca9539f7 100644
--- a/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
+++ b/docs/known-issues/pt/outdated-mastercard-debit-regex-is-causing-us-to-misidentify-some-bins.md
@@ -18,9 +18,7 @@ internalReference: 642136
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns BINs não estão sendo identificados corretamente no checkout. A bandeira do cartão é determinada por um regex que pode eventualmente estar desatualizado, fazendo com que a bandeira do cartão não seja identificada ou seja identificada incorretamente.
diff --git a/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md b/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md
index a553d443b..14775c2f4 100644
--- a/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md
+++ b/docs/known-issues/pt/outdated-url-on-the-update-binding-ui.md
@@ -18,9 +18,7 @@ internalReference: 890791
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comerciante está atualizando uma oferta, a interface do usuário é a seguinte:
diff --git a/docs/known-issues/pt/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md b/docs/known-issues/pt/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md
index 3f48f43d8..95d5d3fab 100644
--- a/docs/known-issues/pt/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md
+++ b/docs/known-issues/pt/page-layout-changes-to-mobile-when-printing-ctrlp-is-used-in-chrome.md
@@ -18,9 +18,7 @@ internalReference: 454680
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 O layout da página muda para a versão móvel ao imprimir (CTRL+P) é ativado duas vezes no Google Chrome Desktop.
 
diff --git a/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md b/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md
index c3b8400f1..27d9c87dc 100644
--- a/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md
+++ b/docs/known-issues/pt/pageview-is-triggered-twice-when-accessing-my-account.md
@@ -18,9 +18,7 @@ internalReference: 854480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao acessar o My Account, o evento pageView é acionado duas vezes, duplicando os dados no Analytics.
diff --git a/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md b/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
index a9459b9da..df9bcae4c 100644
--- a/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
+++ b/docs/known-issues/pt/pageview-triggers-on-g4a-are-being-duplicated-in-custom-search-pages.md
@@ -18,9 +18,7 @@ internalReference: 888042
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O evento pageView está sendo exibido duplicado no dataLayer quando em páginas de pesquisa personalizadas
diff --git a/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md b/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md
index cf22fb3f9..b361b28dc 100644
--- a/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md
+++ b/docs/known-issues/pt/pagination-links-on-search-results-not-working-on-giftlist-pages.md
@@ -18,9 +18,7 @@ internalReference: 481330
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Links de paginação em `SearchResult' que não funcionam em `Giftlist'.
diff --git a/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md b/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
index 57cbedabb..bc510cacf 100644
--- a/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
+++ b/docs/known-issues/pt/pagination-on-searchpage-doesnt-reset-when-changing-search-context.md
@@ -18,9 +18,7 @@ internalReference: 857392
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao navegar em uma determinada página de um PLP, buscar para mostrar mais resultados e alterar o contexto para navegar em um departamento diferente, o parâmetro de paginação será mantido e o resultado da pesquisa começará na nova categoria na mesma página em que estávamos anteriormente
diff --git a/docs/known-issues/pt/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md b/docs/known-issues/pt/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md
index bf52ce928..182e04e4d 100644
--- a/docs/known-issues/pt/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md
+++ b/docs/known-issues/pt/partial-scheduled-delivery-window-selection-for-the-same-sla-affecting-the-purchase-flow.md
@@ -18,9 +18,7 @@ internalReference: 627261
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A alteração do endereço pode alterar as opções de remessa de um item e, naturalmente, pode remover a seleção da janela de entrega para entregas programadas, se as opções forem diferentes.
diff --git a/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md b/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
index 05bcd9279..58feaa0d7 100644
--- a/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
+++ b/docs/known-issues/pt/pasting-postal-code-in-shipping-preview-cart-sometimes-returns-null-api-result.md
@@ -18,9 +18,7 @@ internalReference: 481878
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Depois de inserir o código postal uma vez na visualização do envio e optar por colá-lo novamente, às vezes ocorre de fazer uma solicitação nula para a API do código postal.
diff --git a/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md b/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
index bdb79face..0c61d22b5 100644
--- a/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
+++ b/docs/known-issues/pt/payment-conditions-set-to-process-transactions-in-installments-other-than-1x-are-processing-transactions-as-prepaid-in-full.md
@@ -18,9 +18,7 @@ internalReference: 1030652
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As condições de pagamento configuradas para processar transações em um número de parcelas diferente de 1x estão sendo capazes de processar pagamentos em 1x. O problema ocorre apenas para pagamentos em que o usuário optou por pagar como pré-pago integralmente.
diff --git a/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md b/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
index 71d25252c..72c0fb456 100644
--- a/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
+++ b/docs/known-issues/pt/payment-method-from-marketplace-matches-with-swl-when-using-identical-typesids.md
@@ -18,9 +18,7 @@ internalReference: 402140
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a configuração do método de pagamento, no produto promocional, não se destina a ser passada através da solicitação/resposta de cumprimento.
diff --git a/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md b/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
index 02ac9e3db..697568cc1 100644
--- a/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
+++ b/docs/known-issues/pt/payment-methods-displayed-at-checkout-differ-from-active-payment-conditions.md
@@ -18,9 +18,7 @@ internalReference: 666469
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md b/docs/known-issues/pt/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md
index 283f2ec14..b3cbfd33b 100644
--- a/docs/known-issues/pt/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md
+++ b/docs/known-issues/pt/payment-methods-remain-on-the-checkout-page-even-when-the-associated-payment-condition-is-disabled.md
@@ -18,9 +18,7 @@ internalReference: 649237
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns métodos de pagamento permanecem na página de checkout mesmo quando a condição de pagamento associada é desativada por mais de 10 minutos. Esta é uma questão intermitente e não há evidências de como reproduzir este comportamento.
diff --git a/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md b/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
index 0115f00b3..e99664259 100644
--- a/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
+++ b/docs/known-issues/pt/payment-terms-changes-not-applied-in-the-b2b-checkout-settings.md
@@ -18,9 +18,7 @@ internalReference: 1019548
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A atualização das condições de pagamento na UI de detalhes da organização para uma organização não se aplica às configurações de checkout B2B.
diff --git a/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
index feffea2e8..83e5398ea 100644
--- a/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
+++ b/docs/known-issues/pt/payment-terms-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -18,9 +18,7 @@ internalReference: 989507
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As condições de pagamento configuradas nas configurações de organizações B2B não são salvas nos detalhes da organização.
diff --git a/docs/known-issues/pt/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md b/docs/known-issues/pt/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md
index 112981df3..5c942f7a7 100644
--- a/docs/known-issues/pt/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md
+++ b/docs/known-issues/pt/payments-gateway-does-not-correctly-send-subaccount-information-in-the-payload-to-the-connector.md
@@ -18,9 +18,7 @@ internalReference: 801012
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O problema está na formulação das URLs que são enviadas para o provedor de pagamento. Portanto, o que acontece é que, em cenários em que essas URLs são diferentes, como no caso de uma conta franqueada que processa pagamentos e lojas em um fast store, a diferença entre as URLs geradas no pagamento e a URL esperada pelo checkout faz com que o aplicativo não seja renderizado.
diff --git a/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md b/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
index 03c89975f..be1cb9f41 100644
--- a/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
+++ b/docs/known-issues/pt/paymentsystems-are-not-returned-in-orderform-when-a-cart-price-comes-exclusively-from-manualprice.md
@@ -18,9 +18,7 @@ internalReference: 1025321
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o valor total de um carrinho provém exclusivamente de um preço manual, os itens `preço` e `preço de entrega` são `0`, nenhum sistema de pagamento além do Gift Card (se ativo) é oferecido.
diff --git a/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md b/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
index bdcde572e..1d09df673 100644
--- a/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
+++ b/docs/known-issues/pt/payout-and-transaction-split-dont-work-in-the-same-order-for-multilevel-omnichannel-inventory.md
@@ -18,9 +18,7 @@ internalReference: 777201
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um mercado com relacionamento multinível (MOI) de vendedores, quando um carrinho é montado com pelo menos um vendedor usando divisão de transação e outros usando divisão de pagamento, as transações com divisão de pagamento serão duplicadas repetindo os itens de diferentes vendedores. Este cenário não permitirá colocar o pedido, e a mensagem "Desculpe. Não foi possível processar os pagamentos solicitados" será mostrada.
diff --git a/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md b/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md
index 2aa863264..749a2ae10 100644
--- a/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md
+++ b/docs/known-issues/pt/paypalplus-does-not-respect-the-minimum-installment-amount.md
@@ -18,9 +18,7 @@ internalReference: 370271
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Mesmo com o valor mínimo da parcela configurado no prazo de pagamento PayPalPlus, exibimos parcelas no checkout que não respeitam esta configuração
diff --git a/docs/known-issues/pt/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md b/docs/known-issues/pt/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md
index 12238bf4c..988edced3 100644
--- a/docs/known-issues/pt/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md
+++ b/docs/known-issues/pt/pdp-does-not-load-when-special-characters-are-passed-on-the-link.md
@@ -18,9 +18,7 @@ internalReference: 770893
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há alguns casos especiais em que a loja tem um link para uma página na qual é passado um caracter especial como '#' para passar uma propriedade, por exemplo, a cor do item, o que faz com que o PDP não carregue na primeira vez, ao invés disso ele continua tentando carregar, mas quando a página é atualizada ela carrega corretamente.
diff --git a/docs/known-issues/pt/phone-field-order-netshoes.md b/docs/known-issues/pt/phone-field-order-netshoes.md
index 770d6d3aa..2f5a40c77 100644
--- a/docs/known-issues/pt/phone-field-order-netshoes.md
+++ b/docs/known-issues/pt/phone-field-order-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 599271
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md b/docs/known-issues/pt/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md
index 2b849cf18..d094255d2 100644
--- a/docs/known-issues/pt/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md
+++ b/docs/known-issues/pt/pickup-option-does-not-return-selected-option-if-switching-between-delivery-and-pickup.md
@@ -18,9 +18,7 @@ internalReference: 588394
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comprador seleciona uma loja para retirada, muda para entrega e acrescenta um novo endereço não disponível para entrega quando devolve para retirada, outra loja retorna selecionada. Se alternarmos entre entrega e coleta, às vezes a loja selecionada aparece inicialmente intercalada com outra loja.
diff --git a/docs/known-issues/pt/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md b/docs/known-issues/pt/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md
index 7ea1c7ede..067225ea5 100644
--- a/docs/known-issues/pt/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md
+++ b/docs/known-issues/pt/pickup-point-cant-be-selected-in-marketplaces-with-multilevel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 524073
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um mercado com uma relação multinível (MOI), quando um ponto de coleta é selecionado, o mercado retorna um erro de comunicação com o vendedor, impedindo o uso de pontos de coleta no mercado junto com esses vendedores.
diff --git a/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md b/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
index 2cf3bb865..8603e13ce 100644
--- a/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
+++ b/docs/known-issues/pt/pickup-point-modal-doesnt-utilize-geocoordinates-without-a-google-maps-key.md
@@ -18,9 +18,7 @@ internalReference: 1041462
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A inserção de um código postal no modal do seletor de ponto de coleta aciona uma solicitação para obter os SLAs disponíveis para esse local. Se a conta não tiver uma chave de API do Google Maps definida em suas configurações de Checkout, essa solicitação não incluirá informações de geoCoordinates. Isso pode fazer com que os pontos de coleta dentro de um intervalo válido não sejam exibidos, como aqueles cujas tabelas de frete são baseadas em polígonos.
diff --git a/docs/known-issues/pt/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md b/docs/known-issues/pt/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md
index d0f99d7eb..3059d3652 100644
--- a/docs/known-issues/pt/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md
+++ b/docs/known-issues/pt/pickup-point-options-in-the-checkout-shows-even-inactive-or-invalid-options.md
@@ -18,9 +18,7 @@ internalReference: 328464
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O modal de pontos de coleta, do checkout, mostra em azul as opções válidas como SLA calculado para o carrinho e em cinza outras opções que não foram previamente calculadas como SLA, para que o comprador possa saber sobre essas opções e até mesmo verificar sua disponibilidade sob demanda. Estas opções vêm da API `/api/checkout/pub/pickup-points' (que é apenas um proxy para o serviço de Logística), que listará cada ponto de pickup da loja.
diff --git a/docs/known-issues/pt/pickup-point-selector-search-will-not-working-with-enterreturn.md b/docs/known-issues/pt/pickup-point-selector-search-will-not-working-with-enterreturn.md
index 29b71bd75..246bd4e14 100644
--- a/docs/known-issues/pt/pickup-point-selector-search-will-not-working-with-enterreturn.md
+++ b/docs/known-issues/pt/pickup-point-selector-search-will-not-working-with-enterreturn.md
@@ -18,9 +18,7 @@ internalReference: 829955
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No seletor de pontos de retirada, digitar um endereço e pressionar Enter/Return não exibirá as lojas mais próximas. O comprador sempre precisa digitar o endereço e selecionar uma opção na lista.
diff --git a/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md b/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
index 273ebce7e..7cd368068 100644
--- a/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
+++ b/docs/known-issues/pt/pickup-point-tags-continue-to-be-displayed-in-the-shipping-policy-after-deletion.md
@@ -18,9 +18,7 @@ internalReference: 1015158
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As tags registradas no ponto de coleta estão disponíveis em um menu suspenso nas políticas de remessa para vincular o PUP à política de remessa; no entanto, quando qualquer uma dessas tags é excluída no PUP, elas permanecem disponíveis no menu suspenso da política de remessa.
diff --git a/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md b/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
index 93594c717..8fe528cb6 100644
--- a/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
+++ b/docs/known-issues/pt/pickup-points-list-cant-be-scrolled-after-searching-addresses-in-map-mode.md
@@ -18,9 +18,7 @@ internalReference: 624646
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar um ponto de coleta no carrinho ou checkout enquanto em um layout estreito/resposta ao retrato (largura inferior a 1024px) usando a visualização do mapa, os resultados serão apresentados no modo lista em vez do próprio mapa, e esta lista não funcionará (o usuário não pode rolar a lista para baixo).
diff --git a/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md b/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md
index a5ef49f58..ba875fa70 100644
--- a/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md
+++ b/docs/known-issues/pt/pickup-points-not-indexed-in-master-data.md
@@ -18,9 +18,7 @@ internalReference: 530824
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o sistema de logística usa o MasterData para armazenar informações de pontos de coleta. Como resultado, podemos ter problemas para indexar essa entidade interna ao usar a rota de pesquisa. Isso pode levar a informações desatualizadas, como:
diff --git a/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md b/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
index 7ed2a10c1..5f347d494 100644
--- a/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
+++ b/docs/known-issues/pt/pickup-points-starting-with-the-same-id-pattern-show-product-available.md
@@ -18,9 +18,7 @@ internalReference: 964036
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando os dois pontos de coleta com IDs começam com o mesmo padrão, a interface do usuário do checkout os valida como a mesma loja, mostrando um produto disponível.
diff --git a/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md b/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
index c4723f729..717681b4f 100644
--- a/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
+++ b/docs/known-issues/pt/pickuppoint-and-schedule-delivery-in-the-same-cart-are-not-working-correctly.md
@@ -18,9 +18,7 @@ internalReference: 482256
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface do usuário não funciona corretamente em um carrinho com mais de um item com uma divisão de entrega em que um dos itens está disponível para retirada e os outros apenas para entrega programada.
diff --git a/docs/known-issues/pt/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md b/docs/known-issues/pt/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md
index 908f7f304..d589ce50c 100644
--- a/docs/known-issues/pt/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md
+++ b/docs/known-issues/pt/pickups-inherited-between-whitelabel-sellers-are-treated-as-differentindependent-pickups-on-the-purchase-flow.md
@@ -18,9 +18,7 @@ internalReference: 438630
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um recurso no módulo de Logística para herdar pontos de coleta entre contas de franquia e, portanto, entre vendedores de whitelabel. Enquanto registrados em um vendedor X, eles aparecerão como opções de pickup para um vendedor Y, de acordo com o que está configurado na estratégia de envio. Embora eles sejam os mesmos, sua identificação será diferente entre cada vendedor, e assim eles serão vistos como opções de retirada diferentes e independentes.
diff --git a/docs/known-issues/pt/placeholder-settings-in-the-cms-does-not-display-all-content.md b/docs/known-issues/pt/placeholder-settings-in-the-cms-does-not-display-all-content.md
index f79762977..add42e931 100644
--- a/docs/known-issues/pt/placeholder-settings-in-the-cms-does-not-display-all-content.md
+++ b/docs/known-issues/pt/placeholder-settings-in-the-cms-does-not-display-all-content.md
@@ -18,9 +18,7 @@ internalReference: 547555
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, ao adicionar muito conteúdo dentro de um espaço reservado em um layout CMS, Admin não permite a rolagem da página, o que pára a edição
diff --git a/docs/known-issues/pt/placeholders-showing-instead-of-the-correct-data.md b/docs/known-issues/pt/placeholders-showing-instead-of-the-correct-data.md
index 19236abe9..22be7d6c6 100644
--- a/docs/known-issues/pt/placeholders-showing-instead-of-the-correct-data.md
+++ b/docs/known-issues/pt/placeholders-showing-instead-of-the-correct-data.md
@@ -18,9 +18,7 @@ internalReference: 371183
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md b/docs/known-issues/pt/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md
index 3e44c3c71..6b3cccc1f 100644
--- a/docs/known-issues/pt/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md
+++ b/docs/known-issues/pt/placeorder-generating-wrong-discount-and-shipping-values-between-items-that-appear-more-than-once.md
@@ -18,9 +18,7 @@ internalReference: 732529
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o pedido de criação do pedido declara o mesmo item mais de uma vez, exigido para declarar preços diferentes ou valores de desconto entre as múltiplas unidades do item, o serviço de checkout somará todas as quantidades em um único item e aplicará apenas as condições do primeiro item em todos eles. Isso gerará um preço/desconto total errado e até mesmo o envio.
diff --git a/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md b/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
index 8e66a4fe2..e794ccbdb 100644
--- a/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
+++ b/docs/known-issues/pt/placing-postal-code-in-the-shipping-preview-of-the-cart-is-duplicating-address-options-for-recurring-customers.md
@@ -18,9 +18,7 @@ internalReference: 956338
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Temos alguns problemas quando se trata de colocar códigos postais no módulo **Shipping Preview** no carrinho, alguns deles estão descritos nestes KIs:
diff --git a/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md b/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
index 44656fe5f..ea00df684 100644
--- a/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
+++ b/docs/known-issues/pt/portal-doesnt-delete-cookies-when-client-logout-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 417322
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No checkout de uma loja, temos uma opção para fazer logout.
diff --git a/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md b/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md
index fdcb3d6d6..e51fe9fdd 100644
--- a/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md
+++ b/docs/known-issues/pt/portal-dont-respect-the-tag-principal-of-skus-image.md
@@ -18,9 +18,7 @@ internalReference: 712443
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Uma loja precisa configurar a imagem **Principal** independentemente da ordem na qual ela foi carregada no sistema. Atualmente o sistema não respeita a tag **Principal*** e acaba tomando a primeira imagem registrada como a principal.
diff --git a/docs/known-issues/pt/portal-etag-not-updating-when-changing-metadata.md b/docs/known-issues/pt/portal-etag-not-updating-when-changing-metadata.md
index af20b3fdb..5383252b0 100644
--- a/docs/known-issues/pt/portal-etag-not-updating-when-changing-metadata.md
+++ b/docs/known-issues/pt/portal-etag-not-updating-when-changing-metadata.md
@@ -18,9 +18,7 @@ internalReference: 411434
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md b/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
index cd9af05b5..029ecfc92 100644
--- a/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
+++ b/docs/known-issues/pt/portal-keeps-utms-after-logging-out-when-using-callcenter-operator.md
@@ -18,9 +18,7 @@ internalReference: 534838
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Portal mantém os UTM's após o log out quando se utiliza o Callcenter Operator.
diff --git a/docs/known-issues/pt/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md b/docs/known-issues/pt/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md
index 80d070b04..2df33605f 100644
--- a/docs/known-issues/pt/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md
+++ b/docs/known-issues/pt/portal-legacy-cms-redirect-with-parameters-in-url-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 444496
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Portal Legacy CMS Redirect não funcionará se o URL From tiver parâmetros. Se o parâmetro for um utm_source, ele funcionará. Se o parâmetro for de qualquer outro tipo, não funcionará.
diff --git a/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md b/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
index ea848355b..a05d3c772 100644
--- a/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
+++ b/docs/known-issues/pt/portal-reloads-all-search-results-when-accessing-the-url-with-pagination-parameter.md
@@ -18,9 +18,7 @@ internalReference: 342378
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O portal recarrega todos os resultados da busca ao acessar a URL com um parâmetro de paginação.
diff --git a/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md b/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
index b4311721f..85d2d6fc2 100644
--- a/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
+++ b/docs/known-issues/pt/position-of-the-trade-policy-depends-on-the-page-it-is-shown-on-the-admin-interface.md
@@ -18,9 +18,7 @@ internalReference: 286470
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um cliente com mais de 20 políticas comerciais acaba tendo mais de uma política comercial por posição. Isto é crítico porque as configurações vinculadas dependem do número da posição, portanto, deve haver apenas uma política comercial por posição.
diff --git a/docs/known-issues/pt/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md b/docs/known-issues/pt/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md
index 45793796e..2ee54c112 100644
--- a/docs/known-issues/pt/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md
+++ b/docs/known-issues/pt/position-on-selected-image-on-pdp-doesnt-reset-when-changing-product.md
@@ -18,9 +18,7 @@ internalReference: 595434
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao selecionar qualquer imagem no PDP de um produto, se você passar deste PDP diretamente para outro PDP, a posição da imagem não será apagada - se você estava vendo a terceira imagem, você verá diretamente a terceira imagem no novo PDP.
diff --git a/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md b/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md
index 5276ee315..841327806 100644
--- a/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md
+++ b/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-number-address-and-receiver-name-in-the-checkout-ui.md
@@ -18,9 +18,7 @@ internalReference: 554052
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao chegar à etapa de endereço de caixa, o usuário é capaz de completar o número do endereço e o nome do receptor com um espaço em branco e receber a confirmação de validação, incluindo a possibilidade de ir para a próxima etapa de pagamento. Mesmo sabendo que não pode concluir a compra com sucesso, é uma má usabilidade.
diff --git a/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md b/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md
index 9c5e47943..a24a8701f 100644
--- a/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md
+++ b/docs/known-issues/pt/possibility-to-proceed-to-payment-with-blank-postal-code-in-the-checkout-ui.md
@@ -18,9 +18,7 @@ internalReference: 334310
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você é um usuário que tem um login e vai ao checkout, onde os dados são mascarados, e no formulário de envio, escolhe a opção de entrega para outros endereços, há a possibilidade de ir ao pagamento sem a necessidade de preencher o código postal. Assim, chegando ao processo de pagamento com os dados de entrega vazios na UI.
diff --git a/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md b/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
index f742e3120..ac50216df 100644
--- a/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
+++ b/docs/known-issues/pt/possible-errors-in-change-orders-notification-in-the-ui-api-and-gateway.md
@@ -18,9 +18,7 @@ internalReference: 955489
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns problemas foram identificados na arquitetura Change Orders V1, onde alguns casos não eram notificados na interação do pedido na UI, não eram notificados na API Get Orders, porém, havia um desconto ou aumento no valor. Também vimos cenários em que a notificação ocorre na UI e na API, mas o desconto ou aumento não é feito no gateway.
diff --git a/docs/known-issues/pt/postal-code-request-in-loop-in-the-shipping-preview-component.md b/docs/known-issues/pt/postal-code-request-in-loop-in-the-shipping-preview-component.md
index cc46b8a59..9a41a6d89 100644
--- a/docs/known-issues/pt/postal-code-request-in-loop-in-the-shipping-preview-component.md
+++ b/docs/known-issues/pt/postal-code-request-in-loop-in-the-shipping-preview-component.md
@@ -18,9 +18,7 @@ internalReference: 352659
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Depois de alternar o código postal algumas vezes no componente de pré-visualização do envio do carrinho, o componente entra em um eterno looping de pedidos de `/api/checkout/pub/postal-code//`
diff --git a/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md b/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md
index 0c63193a6..36d55b96d 100644
--- a/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md
+++ b/docs/known-issues/pt/presales-of-the-legacy-cms-collection-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 885693
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Esperava-se que, ao marcar a caixa de seleção de pré-venda, a coleção fosse preenchida com produtos cuja data de lançamento tivesse sido preenchida para uma data futura.
diff --git a/docs/known-issues/pt/price-export-incomplete-when-using-category-filters.md b/docs/known-issues/pt/price-export-incomplete-when-using-category-filters.md
index f75535174..37b98434b 100644
--- a/docs/known-issues/pt/price-export-incomplete-when-using-category-filters.md
+++ b/docs/known-issues/pt/price-export-incomplete-when-using-category-filters.md
@@ -18,9 +18,7 @@ internalReference: 753466
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar exportar uma planilha de preços fixos usando os filtros de categoria, alguns skus não aparecem na planilha apesar de terem preços fixos. A quantidade usual de skus sendo devolvida é de 250.
diff --git a/docs/known-issues/pt/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md b/docs/known-issues/pt/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md
index 4dd7ca4e3..451ca642c 100644
--- a/docs/known-issues/pt/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md
+++ b/docs/known-issues/pt/price-exports-generated-with-a-format-that-is-not-accepted-by-the-import-process.md
@@ -18,9 +18,7 @@ internalReference: 584975
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes (há 50% de chance) os preços são exportados usando um novo formato que não é aceito pelo preço de importação.
diff --git a/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md b/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
index 2cf6bf0be..93d396a6b 100644
--- a/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
+++ b/docs/known-issues/pt/price-filter-applied-on-top-of-spot-price-instead-of-regular-price.md
@@ -18,9 +18,7 @@ internalReference: 982664
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os filtros de preço são aplicados sobre o valor "spotPrice", que é o preço para condições especiais de pagamento, em vez do preço normal do item.
diff --git a/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md b/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
index c6007a477..42ed3ab7c 100644
--- a/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
+++ b/docs/known-issues/pt/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md
@@ -18,9 +18,7 @@ internalReference: 997121
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As faixas de preço da API de facetas ("Obter lista das facetas possíveis para uma determinada consulta") podem variar entre o retorno de baldes de valores "de" e "para" com preços arredondados e os preços mínimo e máximo entre os resultados da pesquisa.
diff --git a/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md b/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
index 7581f7460..e7d311f9a 100644
--- a/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
+++ b/docs/known-issues/pt/price-range-slider-defaults-to-minimum-value-after-selecting-a-filter.md
@@ -18,9 +18,7 @@ internalReference: 843442
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Esta é uma faixa de preço, é um controle deslizante e tem dois seletores (marcadores), um para o mínimo e outro para o máximo, para que ele saiba onde se posicionar no controle deslizante.
diff --git a/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md b/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
index bdd0bfec5..15713ac83 100644
--- a/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
+++ b/docs/known-issues/pt/price-swapped-if-the-same-item-is-in-the-cart-twice-and-one-is-from-assembly-options.md
@@ -18,9 +18,7 @@ internalReference: 1070336
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se um item for adicionado ao carrinho como uma opção (também conhecida como filho) das Opções de montagem, e o mesmo item for adicionado ao carrinho como um item normal, os preços serão misturados e cada um será aplicado ao item incorreto.
diff --git a/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md b/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md
index cef035eb7..f2c782515 100644
--- a/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md
+++ b/docs/known-issues/pt/price-updates-with-cache-on-end-applications.md
@@ -18,9 +18,7 @@ internalReference: 896520
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As modificações de preço feitas na conta são atualizadas quase em tempo real nas APIs de preço. No entanto, as simulações de checkout levam cerca de 5 minutos para ter o preço mais atualizado no produto devido ao cache. Isso é esperado.
diff --git a/docs/known-issues/pt/price-variation-limit-only-works-in-the-main-policy.md b/docs/known-issues/pt/price-variation-limit-only-works-in-the-main-policy.md
index 3cfff2d35..2c11c403f 100644
--- a/docs/known-issues/pt/price-variation-limit-only-works-in-the-main-policy.md
+++ b/docs/known-issues/pt/price-variation-limit-only-works-in-the-main-policy.md
@@ -18,9 +18,7 @@ internalReference: 509540
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
index 83a1339f7..aa7da0519 100644
--- a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
+++ b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-change-price-api.md
@@ -18,9 +18,7 @@ internalReference: 566142
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Checkout REST API Change price não suporta preços maiores que um valor "Int32". Portanto, a aplicação de um "preço manual" será restrita ao número "2.147.483.647" (número em decimais).
diff --git a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md
index 59ed71efb..c3b3623fd 100644
--- a/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md
+++ b/docs/known-issues/pt/prices-restricted-to-int32-max-value-on-checkout-apis.md
@@ -18,9 +18,7 @@ internalReference: 566142
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os APIs REST não suportam preços superiores a um valor "Int32". Portanto, a aplicação de um "preço manual" será restrita ao número "2.147.483.647" (número em casas decimais).
diff --git a/docs/known-issues/pt/pricing-api-allows-negative-values.md b/docs/known-issues/pt/pricing-api-allows-negative-values.md
index 8784b1dc5..fc953e390 100644
--- a/docs/known-issues/pt/pricing-api-allows-negative-values.md
+++ b/docs/known-issues/pt/pricing-api-allows-negative-values.md
@@ -18,9 +18,7 @@ internalReference: 774548
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o PUT Price API permite a entrada de valores negativos via PUT API Payload, se você definir a marcação e o preço base para valores negativos, você definirá o produto como indisponível.
diff --git a/docs/known-issues/pt/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md b/docs/known-issues/pt/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md
index cebaba7b6..42c44c4f8 100644
--- a/docs/known-issues/pt/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md
+++ b/docs/known-issues/pt/pricing-modification-via-compatibility-post-prices-route-is-losing-data.md
@@ -18,9 +18,7 @@ internalReference: 487698
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Identificamos um problema na rota de preços pós-compatibilidade quando enviamos muitos pedidos em uma pequena janela não estamos usando o preço mais atualizado
diff --git a/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md b/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
index 7b893005b..3db857917 100644
--- a/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
+++ b/docs/known-issues/pt/prioritization-by-products-keyword-not-considering-stopwords.md
@@ -18,9 +18,7 @@ internalReference: 1041743
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os produtos podem ser priorizados nos resultados da pesquisa por sua "palavra-chave", uma palavra do nome do produto definida como relevante por um algoritmo. Stopwords são termos de pesquisa filtrados dos termos originais porque não são significativos para a pesquisa.
diff --git a/docs/known-issues/pt/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md b/docs/known-issues/pt/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md
index aafde80d4..7504a49d8 100644
--- a/docs/known-issues/pt/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md
+++ b/docs/known-issues/pt/problem-to-index-payment-methods-on-checkout-when-using-period-of-time-special-condition.md
@@ -18,9 +18,7 @@ internalReference: 402857
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Temos um problema para indexar os métodos de pagamento no checkout. Isso acontece com condições de pagamento que são configuradas com um período de tempo de condições especiais.
diff --git a/docs/known-issues/pt/problem-to-pay-with-giftcard-two-cards-option.md b/docs/known-issues/pt/problem-to-pay-with-giftcard-two-cards-option.md
index e242a94db..2976b9a9a 100644
--- a/docs/known-issues/pt/problem-to-pay-with-giftcard-two-cards-option.md
+++ b/docs/known-issues/pt/problem-to-pay-with-giftcard-two-cards-option.md
@@ -18,9 +18,7 @@ internalReference: 393958
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando os usuários aplicam um cartão presente e depois vão usar "Pague com Dois Cartões" para pagar a diferença, a tela salta e apenas escolhe um valor diferente daquele escolhido
diff --git a/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md b/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md
index ae286ff98..d467d72a9 100644
--- a/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md
+++ b/docs/known-issues/pt/problem-while-validating-value-field-when-buying-with-two-cards.md
@@ -18,9 +18,7 @@ internalReference: 460683
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um comprador decide pagar com dois cartões de crédito e também quer alterar o valor pago por cada cartão, acontece que ao digitar caracteres sem números no campo de valor, nossa validação tem comportamento diferente dependendo de onde o usuário insere esse caractere.
diff --git a/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md b/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md
index 3d9f2b34d..2ee51c76c 100644
--- a/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md
+++ b/docs/known-issues/pt/problem-with-phone-validation-on-mobile-devices.md
@@ -18,9 +18,7 @@ internalReference: 964802
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A validação do campo do telefone em dispositivos móveis não está se comportando como pretendido. Quando o número esperado de caracteres é atingido, a validação marca corretamente o campo com uma verificação. Entretanto, quando caracteres adicionais são adicionados e, em seguida, removidos um a um, a validação não reconhece que a contagem de caracteres ainda é maior do que a esperada, marcando incorretamente a entrada como válida. A validação também marca como válidas entradas com menos caracteres do que o esperado.
diff --git a/docs/known-issues/pt/problems-adding-items-to-cart-in-io-that-have-attachments.md b/docs/known-issues/pt/problems-adding-items-to-cart-in-io-that-have-attachments.md
index 8f4989205..bace1a45c 100644
--- a/docs/known-issues/pt/problems-adding-items-to-cart-in-io-that-have-attachments.md
+++ b/docs/known-issues/pt/problems-adding-items-to-cart-in-io-that-have-attachments.md
@@ -18,9 +18,7 @@ internalReference: 429724
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md b/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
index 93f4c2112..f0c83a842 100644
--- a/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
+++ b/docs/known-issues/pt/problems-opening-manage-inventory-by-admin-page-with-error-ui.md
@@ -18,9 +18,7 @@ internalReference: 466491
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Problemas ao abrir a página "Gerenciar inventário" por Admin com mensagem de erro:
diff --git a/docs/known-issues/pt/problems-with-payment-condition-storage.md b/docs/known-issues/pt/problems-with-payment-condition-storage.md
index ed5f64fab..fdbf95ff5 100644
--- a/docs/known-issues/pt/problems-with-payment-condition-storage.md
+++ b/docs/known-issues/pt/problems-with-payment-condition-storage.md
@@ -18,9 +18,7 @@ internalReference: 377684
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há uma conta e uma subconta com o mesmo sufixo, estamos tendo problemas para armazenar as Condições de Pagamento sempre que há mudanças nelas.
diff --git a/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md b/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md
index 5f1d0ecea..1f6ccfad0 100644
--- a/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md
+++ b/docs/known-issues/pt/product-availability-display-delayed-when-using-multiple-sales-channels.md
@@ -18,9 +18,7 @@ internalReference: 949411
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A exibição, para lojas de portais antigos, de produtos em PLPs é baseada no canal de vendas da loja e em seus dados básicos de disponibilidade.
diff --git a/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md b/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
index d98e480b3..f0494812f 100644
--- a/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
+++ b/docs/known-issues/pt/product-availability-is-incorrectly-showed-in-the-pickups-in-cart-display-modal.md
@@ -18,9 +18,7 @@ internalReference: 552875
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/product-category-information-from-datalayer-with-a-wrong-sorting.md b/docs/known-issues/pt/product-category-information-from-datalayer-with-a-wrong-sorting.md
index d0f140930..57269381c 100644
--- a/docs/known-issues/pt/product-category-information-from-datalayer-with-a-wrong-sorting.md
+++ b/docs/known-issues/pt/product-category-information-from-datalayer-with-a-wrong-sorting.md
@@ -18,9 +18,7 @@ internalReference: 328415
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As informações sobre a categoria do produto na dataLayer nas páginas de checkout são mostradas na ordenação errada. Isto é representado pela propriedade "categoryTree".
diff --git a/docs/known-issues/pt/product-comissioning-inconsistent-cache.md b/docs/known-issues/pt/product-comissioning-inconsistent-cache.md
index 4d767df28..e97f127ec 100644
--- a/docs/known-issues/pt/product-comissioning-inconsistent-cache.md
+++ b/docs/known-issues/pt/product-comissioning-inconsistent-cache.md
@@ -18,9 +18,7 @@ internalReference: 872364
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Existem, a partir de 2023, dois conjuntos de APIs distintos para atualizar as informações de um vendedor em um marketplace, são eles:
 https://developers.vtex.com/docs/api-reference/catalog-api#put-/api/catalog_system/pvt/seller
diff --git a/docs/known-issues/pt/product-created-with-id-0.md b/docs/known-issues/pt/product-created-with-id-0.md
index a1cf03b48..26b35f4ed 100644
--- a/docs/known-issues/pt/product-created-with-id-0.md
+++ b/docs/known-issues/pt/product-created-with-id-0.md
@@ -18,9 +18,7 @@ internalReference: 335840
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 É possível criar produtos com ID = 0 se eles utilizarem nosso API ou WebService.
diff --git a/docs/known-issues/pt/product-highlights-doesnt-work-into-a-product-list.md b/docs/known-issues/pt/product-highlights-doesnt-work-into-a-product-list.md
index f640deefd..b4ac7df5d 100644
--- a/docs/known-issues/pt/product-highlights-doesnt-work-into-a-product-list.md
+++ b/docs/known-issues/pt/product-highlights-doesnt-work-into-a-product-list.md
@@ -18,9 +18,7 @@ internalReference: 546844
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há uma promoção com destaque habilitado e o produto, que está incluído nesta promoção, está dentro de uma lista, como uma prateleira, o crachá que informa a promoção não é exibido.
diff --git a/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md b/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md
index 7d1490d81..d33eb8c6c 100644
--- a/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md
+++ b/docs/known-issues/pt/product-image-on-admin-changes-with-more-than-70-skus.md
@@ -18,9 +18,7 @@ internalReference: 1003966
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um produto tem mais de 70 variações de skus, sua imagem no admin (e somente no admin) é alterada para uma imagem de informações:
diff --git a/docs/known-issues/pt/product-image-sorting-doesnt-respect-the-catalog-order.md b/docs/known-issues/pt/product-image-sorting-doesnt-respect-the-catalog-order.md
index 9d9f5a43e..b33914452 100644
--- a/docs/known-issues/pt/product-image-sorting-doesnt-respect-the-catalog-order.md
+++ b/docs/known-issues/pt/product-image-sorting-doesnt-respect-the-catalog-order.md
@@ -18,9 +18,7 @@ internalReference: 682177
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você usa o adereço para mostrar uma imagem diferente ao pairar sobre um componente de resumo de produto atualmente ele chama a API de Busca Inteligente para retornar as imagens e com estes dados ele exibirá uma imagem diferente ao pairar, o que acontece hoje é que o pedido no Catálogo não é necessário a mesma ordem que a busca retornará causando divergências dentro dos resultados esperados.
diff --git a/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md b/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
index 1fe516354..48185fd6c 100644
--- a/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
+++ b/docs/known-issues/pt/product-insertupdate-api-allows-n-in-the-textlink-field.md
@@ -18,9 +18,7 @@ internalReference: 486459
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, as APIs para a inserção ou atualização de produtos do Catálogo permitem o caractere "\n" no textoLink
diff --git a/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md b/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
index 67d047176..45763745b 100644
--- a/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
+++ b/docs/known-issues/pt/product-name-contains-search-with-more-than-one-term-doesnt-work-on-catalogs-redesigned-ui.md
@@ -18,9 +18,7 @@ internalReference: 1044571
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na lista de produtos reformulada do catálogo, um dos campos de pesquisa é "Product name contains" (O nome do produto contém). Atualmente, ao pesquisar um nome de produto com mais de um termo, podem ocorrer duas situações:
diff --git a/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md b/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
index ad161ca6c..6faec2d54 100644
--- a/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
+++ b/docs/known-issues/pt/product-name-field-on-xml-returns-product-name-sku-name-when-the-product-has-only-1-sku.md
@@ -18,9 +18,7 @@ internalReference: 661089
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/product-page-sessions-not-working.md b/docs/known-issues/pt/product-page-sessions-not-working.md
index 936825a1d..c60b34f8e 100644
--- a/docs/known-issues/pt/product-page-sessions-not-working.md
+++ b/docs/known-issues/pt/product-page-sessions-not-working.md
@@ -18,9 +18,7 @@ internalReference: 961591
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A visão geral do administrador tem algumas informações de análise. A informação sobre as sessões da página do produto deveria retornar os valores desse evento, mas às vezes está retornando zero
diff --git a/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md b/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md
index 9cbc0c047..5be507455 100644
--- a/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md
+++ b/docs/known-issues/pt/product-price-not-considering-default-seller-in-pdp.md
@@ -18,9 +18,7 @@ internalReference: 429888
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao mostrar o preço no PDP, o componente ignora o Vendedor por Padrão, considerando o primeiro vendedor que foi registrado.
diff --git a/docs/known-issues/pt/product-quantity-selector-error-for-high-resolution-screens.md b/docs/known-issues/pt/product-quantity-selector-error-for-high-resolution-screens.md
index 807630afc..8b019cbbb 100644
--- a/docs/known-issues/pt/product-quantity-selector-error-for-high-resolution-screens.md
+++ b/docs/known-issues/pt/product-quantity-selector-error-for-high-resolution-screens.md
@@ -18,9 +18,7 @@ internalReference: 561921
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao renderizar altas resoluções, o seletor de quantidade não funciona.
diff --git a/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md b/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
index 38ed12b49..af3a1c310 100644
--- a/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
+++ b/docs/known-issues/pt/product-replacement-on-oms-order-not-working-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 753484
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Não está sendo possível alterar o sku de um pedido porque a OMS utiliza a API de busca (que está relacionada ao catálogo V1) e as contas do portal do vendedor utilizam uma nova versão do catálogo. Nenhum proxy foi implementado nesta área.
diff --git a/docs/known-issues/pt/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md b/docs/known-issues/pt/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md
index 41d6ad19d..a8e6eefdf 100644
--- a/docs/known-issues/pt/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md
+++ b/docs/known-issues/pt/product-rich-snippets-not-using-aggregateoffer-format-for-offers-with-more-than-one-seller.md
@@ -18,9 +18,7 @@ internalReference: 753505
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um único produto é associado a várias ofertas (por exemplo, o mesmo par de sapatos é oferecido por comerciantes diferentes), então a AggregateOffer pode ser usada para enviar esta informação para o google de uma forma que seu rastreador não rejeitará a oferta por preços errados.
diff --git a/docs/known-issues/pt/product-specification-export-index-out-of-range.md b/docs/known-issues/pt/product-specification-export-index-out-of-range.md
index f12fcbdfa..1a3daa10d 100644
--- a/docs/known-issues/pt/product-specification-export-index-out-of-range.md
+++ b/docs/known-issues/pt/product-specification-export-index-out-of-range.md
@@ -18,9 +18,7 @@ internalReference: 481095
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar exportar especificações de produtos da interface do usuário "Importar e exportar", se houver algum valor nulo ou relação nula na categoria a ser exportada, o processo falhará com uma mensagem "Índice fora do intervalo". Em outras palavras, a categoria deve ter registrado diretamente em seu nível um campo de produto, produtos e produtos com valores associados.
diff --git a/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md b/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
index 8a1400dbb..a8de5b9e3 100644
--- a/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
+++ b/docs/known-issues/pt/product-specification-filter-on-collection-module-assuming-incorrect-values.md
@@ -18,9 +18,7 @@ internalReference: 926593
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No módulo Collection, o filtro Product Specifications (Especificações do produto) não está funcionando corretamente quando a especificação tem o tipo "Text" (Texto) e "Large Text" (Texto grande). Quando esse tipo de especificação é selecionado, uma caixa de texto é aberta para inserir os valores possíveis separados por vírgula, tabulação ou enter. Entretanto, ao digitar apenas um caractere, o sistema o assume como um valor mesmo sem separar os termos.
diff --git a/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md b/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
index 924d3f9fe..91714cae8 100644
--- a/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
+++ b/docs/known-issues/pt/product-specification-filter-on-the-collection-module-does-not-list-root-category.md
@@ -18,9 +18,7 @@ internalReference: 918687
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No módulo de coleção, ao usar os filtros para adicionar produtos, o filtro Product Specification não lista os campos registrados na categoria raiz
diff --git a/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md b/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
index 87e1fc93f..c6b0a1501 100644
--- a/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
+++ b/docs/known-issues/pt/product-specification-import-with-type-text-does-not-trigger-the-products-indexation.md
@@ -18,9 +18,7 @@ internalReference: 998658
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao importar especificações de produtos, os tipos com valores pré-registrados (como Checkbox ou Radio) acionam a indexação do produto, mas quando o tipo é "Texto" o mesmo não ocorre.
diff --git a/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md b/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
index 74667d7e9..bf3d7a733 100644
--- a/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
+++ b/docs/known-issues/pt/product-taxpercentage-value-saved-by-searchresolver-is-incorrect-due-to-rounding.md
@@ -18,9 +18,7 @@ internalReference: 470143
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O vtex.search-resolver@1.x guarda informações sobre o percentual de impostos do produto, mas o valor registrado pode ser ligeiramente incorreto devido ao arredondamento de números.
diff --git a/docs/known-issues/pt/product-unavailable-even-with-franchised-stock.md b/docs/known-issues/pt/product-unavailable-even-with-franchised-stock.md
index 14806c4dc..95b912309 100644
--- a/docs/known-issues/pt/product-unavailable-even-with-franchised-stock.md
+++ b/docs/known-issues/pt/product-unavailable-even-with-franchised-stock.md
@@ -18,9 +18,7 @@ internalReference: 404499
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se o produto estiver fora de estoque no mercado, em qualquer outro vendedor regular e a bandeira **show out of stock** estiver desmarcada, o produto será exibido fora de estoque no portal, mesmo que tenha estoque em contas de franquias. É possível adicionar o produto ao carrinho.
diff --git a/docs/known-issues/pt/productclick-event-considers-the-incorrect-sku-id.md b/docs/known-issues/pt/productclick-event-considers-the-incorrect-sku-id.md
index 79b8ce38c..8a62e1bc9 100644
--- a/docs/known-issues/pt/productclick-event-considers-the-incorrect-sku-id.md
+++ b/docs/known-issues/pt/productclick-event-considers-the-incorrect-sku-id.md
@@ -18,9 +18,7 @@ internalReference: 788145
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 productClick event considera o SKU Id incorreto ao utilizar o bloco Seletor de SKU Resumo do Produto. Ele sempre utilizará o primeiro SKU da lista de produtos.
diff --git a/docs/known-issues/pt/productclick-event-not-triggering-in-searchbar.md b/docs/known-issues/pt/productclick-event-not-triggering-in-searchbar.md
index ac3867a52..55be91e6e 100644
--- a/docs/known-issues/pt/productclick-event-not-triggering-in-searchbar.md
+++ b/docs/known-issues/pt/productclick-event-not-triggering-in-searchbar.md
@@ -18,9 +18,7 @@ internalReference: 742754
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md b/docs/known-issues/pt/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md
index 46e90b5c7..78e1c9922 100644
--- a/docs/known-issues/pt/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md
+++ b/docs/known-issues/pt/productcomparison-doesnt-allow-changing-checkboxes-if-you-keep-the-drawer-open.md
@@ -18,9 +18,7 @@ internalReference: 568409
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md b/docs/known-issues/pt/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md
index 22e14bc92..b304412d9 100644
--- a/docs/known-issues/pt/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md
+++ b/docs/known-issues/pt/productimpression-doesnt-show-all-the-products-when-the-sku-is-individually-showed.md
@@ -18,9 +18,7 @@ internalReference: 717617
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a loja "separa" o SKU de um produto a ser exibido individualmente na fachada da loja, o ProductImpression do GTM só vê os produtos por seu productID, não por cada SKUId. Portanto, se o produto tiver 3 SKUs diferentes na página de busca, a ProductImpression o mostrará apenas como um produto.
diff --git a/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md b/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
index 281336c13..d9000614a 100644
--- a/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
+++ b/docs/known-issues/pt/products-in-the-productlist-that-have-an-itemattachment-duplicate-when-the-quantity-is-increased.md
@@ -18,9 +18,7 @@ internalReference: 337069
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se uma loja utiliza o componente de lista de produtos da Estrutura de Loja, utilizado no minicartão, os itens do carrinho podem ser duplicados ao aumentar a quantidade de um item que tem um anexo (itemAttachment).
diff --git a/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md b/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
index f0cf36780..9f6cc9b1f 100644
--- a/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
+++ b/docs/known-issues/pt/products-not-being-correctly-matched-when-the-productname-contains-numbers.md
@@ -18,9 +18,7 @@ internalReference: 762525
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o vendedor envia um sku para o marketplace, o sistema Matcher é responsável por consultar o catálogo do marketplace e verificar se já existe um produto semelhante aos skus do vendedor.
diff --git a/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md b/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md
index a56f84f99..505a5fc46 100644
--- a/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md
+++ b/docs/known-issues/pt/products-showing-flag-and-discount-after-promotion-ended.md
@@ -18,9 +18,7 @@ internalReference: 383911
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, as bandeiras de promoção e os descontos são exibidos no PLP e no PLP após a data de expiração da promoção. Isso acontece porque a promoção não aciona a indexação do produto, resultando na exibição incorreta do desconto.
diff --git a/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md b/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
index 0971cac0c..6d6e45b6f 100644
--- a/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
+++ b/docs/known-issues/pt/products-with-price-zero-shown-as-unavailable-at-intelligent-search.md
@@ -18,9 +18,7 @@ internalReference: 1045184
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os produtos com preço zero são mostrados como indisponíveis pela Pesquisa Inteligente. Diferentemente de um produto sem preço registrado, o preço definido como zero define um produto gratuito.
diff --git a/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md b/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
index b479fcf00..339da3e9f 100644
--- a/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
+++ b/docs/known-issues/pt/products-with-sku-variations-approved-on-received-skus-are-being-created-with-duplicated-skus-on-the-catalog.md
@@ -18,9 +18,7 @@ internalReference: 889676
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O vendedor pode enviar um produto com várias variações de sku.
diff --git a/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md b/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
index 15f22ee55..bcb657c24 100644
--- a/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
+++ b/docs/known-issues/pt/products-with-unitmultiplier-wrongly-flagged-as-with-promotion-for-search-filters.md
@@ -18,9 +18,7 @@ internalReference: 982830
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um produto cujo preço de venda é menor do que o preço de tabela será sinalizado como parte de uma promoção para fins de filtragem de pesquisa. Os produtos com algum multiplicador de unidade podem resultar em um cálculo incorreto que pode afetar essa comparação, fazendo com que eles recebam esse sinalizador erroneamente.
diff --git a/docs/known-issues/pt/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md b/docs/known-issues/pt/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md
index 065d85dd6..1db3b297c 100644
--- a/docs/known-issues/pt/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md
+++ b/docs/known-issues/pt/products-without-sku-are-not-returned-in-the-admin-when-searching-by-product-id.md
@@ -18,9 +18,7 @@ internalReference: 740431
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Produtos sem SKU não são devolvidos na administração ao pesquisar por ID do produto
diff --git a/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md b/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
index 87bddb035..b16a4f323 100644
--- a/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
+++ b/docs/known-issues/pt/products-without-stock-on-whitelabel-sellers-are-appearing-in-the-end-of-plp.md
@@ -18,9 +18,7 @@ internalReference: 495741
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os produtos que não têm estoque nos vendedores da WL estão aparecendo no final do PLP.
diff --git a/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md b/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md
index 89f0764bc..c47942504 100644
--- a/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md
+++ b/docs/known-issues/pt/productsku-upload-form-allows-utf16-format-uploaddownload.md
@@ -18,9 +18,7 @@ internalReference: 493402
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, se um usuário tentar carregar uma lista SKU para o formulário de promoção regular utilizando um arquivo .txt, se o arquivo carregado estiver no formato de codificação UTF-16, então será o arquivo carregado posteriormente.
diff --git a/docs/known-issues/pt/productsskus-import-does-not-support-lb.md b/docs/known-issues/pt/productsskus-import-does-not-support-lb.md
index 5f58d6954..d043905a5 100644
--- a/docs/known-issues/pt/productsskus-import-does-not-support-lb.md
+++ b/docs/known-issues/pt/productsskus-import-does-not-support-lb.md
@@ -18,9 +18,7 @@ internalReference: 337860
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a folha de catálogo de Produtos e SKUs não suporta a unidade de medição 'lb'. `/admin/Site/Relatorio_Skus.aspx'.
diff --git a/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md b/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
index 03b79e24c..4d6ce40e6 100644
--- a/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
+++ b/docs/known-issues/pt/profile-data-loaded-empty-in-the-ui-for-complete-profile-with-ignoreprofiledata.md
@@ -18,9 +18,7 @@ internalReference: 1016582
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao definir "ignoreProfileData" via API Ignore profile data on checkout, se o comprador tiver um perfil completo, mas não estiver conectado, os dados serão carregados vazios na interface do usuário.
diff --git a/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md b/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
index a2255e041..c6ce9bec5 100644
--- a/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
+++ b/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-client-preferences-data.md
@@ -18,9 +18,7 @@ internalReference: 842575
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao aplicar uma promoção Mais por Menos, o comportamento esperado é separar o item promocional dos itens regulares, mas os itens serão agrupados após a adição dos dados de preferências do cliente.
diff --git a/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-profile-data.md b/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-profile-data.md
index 617c75c3f..895b941d1 100644
--- a/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-profile-data.md
+++ b/docs/known-issues/pt/promotion-item-will-not-show-splitted-after-adding-profile-data.md
@@ -18,9 +18,7 @@ internalReference: 842575
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O comportamento esperado ao aplicar uma promoção Mais por Menos é ter o item promocional separado dos itens regulares, mas os itens serão agrupados depois de adicionar um e-mail ao checkout.
diff --git a/docs/known-issues/pt/promotion-more-for-less-not-working-alongside-regular-promotion.md b/docs/known-issues/pt/promotion-more-for-less-not-working-alongside-regular-promotion.md
index 92a80c02e..772ea4947 100644
--- a/docs/known-issues/pt/promotion-more-for-less-not-working-alongside-regular-promotion.md
+++ b/docs/known-issues/pt/promotion-more-for-less-not-working-alongside-regular-promotion.md
@@ -18,9 +18,7 @@ internalReference: 637586
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O desconto final no carrinho de compras não é correto quando um More for Less promotion está sendo aplicado ao lado de uma promoção regular. O desconto é maior do que o esperado.
diff --git a/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md b/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
index 17741fefe..4babb0592 100644
--- a/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
+++ b/docs/known-issues/pt/promotion-subscription-with-week-month-and-day-frequency-not-working-on-recurring-cycles.md
@@ -18,9 +18,7 @@ internalReference: 965484
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma promoção de assinatura é definida no módulo de assinatura, o comerciante tem a possibilidade de escolher a frequência com que essa promoção será aplicada à assinatura.
diff --git a/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md b/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
index b6a209f99..5f8d59fad 100644
--- a/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
+++ b/docs/known-issues/pt/promotional-price-table-in-large-shopping-carts-can-impact-performance-or-lead-to-timeout-errors.md
@@ -18,9 +18,7 @@ internalReference: 949389
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md b/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
index ac9b3dffc..96315e549 100644
--- a/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
+++ b/docs/known-issues/pt/promotions-and-taxes-restricted-by-shipping-method-doesnt-works-for-whitelabel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 315485
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As promoções e os impostos restritos por métodos de envio não funcionam para os vendedores Whitelabel. Eles não serão aplicados na solicitação de simulação (usada para o carrinho e o checkout) porque a solicitação do marketplace não especifica o `selectedSla` e, portanto, seus valores não serão apresentados ao usuário.
diff --git a/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md b/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
index eedcd088f..5f7526ceb 100644
--- a/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
+++ b/docs/known-issues/pt/promotions-by-order-of-payment-methods-do-not-appear-on-the-product-page.md
@@ -18,9 +18,7 @@ internalReference: 781523
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A página do produto mostra o preço do SKU apenas com algumas promoções, que não inclui as condições específicas para as formas de pagamento nem o número de parcelas. Estas só são aplicadas durante o checkout, após o usuário ter optado explicitamente pelo uso de uma determinada condição de pagamento.
diff --git a/docs/known-issues/pt/promotions-microrounding-divergence.md b/docs/known-issues/pt/promotions-microrounding-divergence.md
index 0b7f63d3a..807281d89 100644
--- a/docs/known-issues/pt/promotions-microrounding-divergence.md
+++ b/docs/known-issues/pt/promotions-microrounding-divergence.md
@@ -18,9 +18,7 @@ internalReference: 957369
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O módulo de promoções arredonda os descontos em até 3 dígitos significativos, o que pode, em cenários muito específicos, resultar em pequenas divergências no preço final de um carrinho.
diff --git a/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md b/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
index c2f6a9442..365daf041 100644
--- a/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
+++ b/docs/known-issues/pt/promotions-resulting-in-wrong-sorting-filtering-by-price-or-discount.md
@@ -18,9 +18,7 @@ internalReference: 888304
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 As listas de produtos e os resultados de pesquisa podem ser mal classificados/filtrados ao usar a classificação ou a filtragem por preço ou desconto se houver preços de itens desatualizados no nível do índice, mesmo que a vitrine esteja mostrando o preço correto.
 
diff --git a/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md b/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md
index c2eeade50..405ea3200 100644
--- a/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md
+++ b/docs/known-issues/pt/promotions-ui-loading-wrong-currency-information.md
@@ -18,9 +18,7 @@ internalReference: 718908
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao abrir o módulo Promoções muito rapidamente e várias vezes seguidas, um comportamento incorreto aparece na interface do usuário.
diff --git a/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md b/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md
index 5afd98189..8d1cf19e7 100644
--- a/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md
+++ b/docs/known-issues/pt/property-blockclass-from-infocard-not-working.md
@@ -18,9 +18,7 @@ internalReference: 743730
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md b/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
index cd08abdc2..fbc49bc61 100644
--- a/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
+++ b/docs/known-issues/pt/proportional-shipping-costs-shows-negative-values-when-there-are-promotion-that-split-items-and-free-shipping-applied.md
@@ -18,9 +18,7 @@ internalReference: 909925
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar promoções que dividem itens, como o tipo "Mais por menos", os custos de envio proporcionais podem exibir valores negativos.
diff --git a/docs/known-issues/pt/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md b/docs/known-issues/pt/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md
index 656c12e0a..360c7773a 100644
--- a/docs/known-issues/pt/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md
+++ b/docs/known-issues/pt/pse-redirect-does-not-happen-when-the-user-chooses-to-pay-with-giftcard-and-pse.md
@@ -18,19 +18,13 @@ internalReference: 580333
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md b/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md
index 7e5a9912c..8be379a60 100644
--- a/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md
+++ b/docs/known-issues/pt/pt-message-is-shown-in-the-license-manager-module.md
@@ -18,9 +18,7 @@ internalReference: 620782
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/publication-attributes-in-mercado-livre-are-not-integrated.md b/docs/known-issues/pt/publication-attributes-in-mercado-livre-are-not-integrated.md
index e2f8dcf6b..98b22b4d1 100644
--- a/docs/known-issues/pt/publication-attributes-in-mercado-livre-are-not-integrated.md
+++ b/docs/known-issues/pt/publication-attributes-in-mercado-livre-are-not-integrated.md
@@ -32,7 +32,5 @@ Não é reproduzível, uma vez que a configuração do Mercado Livre na VTEX Bri
 
 Também é possível carregar os atributos manualmente no Mercado Livre.
 
-<div class="alert alert-info">
-Este problema já foi solucionado pela nossa equipe. <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA">Saiba mais.</a>
-</div>
+>ℹ️ Este problema já foi solucionado pela nossa equipe. [Saiba mais.](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA)
 
diff --git a/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md b/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
index 4a54f3db0..5da6ed51f 100644
--- a/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
+++ b/docs/known-issues/pt/pubportalpagetype-not-mapping-correctly-when-2-categories-have-the-same-name.md
@@ -18,9 +18,7 @@ internalReference: 314551
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md b/docs/known-issues/pt/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md
index 11c167989..471758c73 100644
--- a/docs/known-issues/pt/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md
+++ b/docs/known-issues/pt/pup-options-do-not-change-when-changing-postal-code-in-stores-without-geopositioning-setup.md
@@ -18,9 +18,7 @@ internalReference: 648604
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md b/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
index 4dfe6c472..c9ef4ef13 100644
--- a/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
+++ b/docs/known-issues/pt/purchase-cant-be-finished-and-is-stuck-on-freight-type-has-changed.md
@@ -18,9 +18,7 @@ internalReference: 449341
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar qualquer promoção que cause a divisão de um item e dois vendedores diferentes forem selecionados, clicar em "Comprar agora" exibirá a mensagem "o tipo de frete foi alterado", impedindo a conclusão da compra.
diff --git a/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md b/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
index 96ef4b4b1..05c7fae62 100644
--- a/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
+++ b/docs/known-issues/pt/purchase-cant-be-finished-and-returns-the-error-receiver-name-field-is-invalid.md
@@ -18,9 +18,7 @@ internalReference: 313945
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um grande volume de erros no processo de criação de um pedido com a mensagem "_O campo do nome do receptor no anexo de envio é inválido_". Parece ser algo relacionado à nossa IU de checkout. Não temos recursos para entender o quanto isso está realmente afetando ou bloqueando as vendas.
diff --git a/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md b/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md
index a0faf4cca..81466240b 100644
--- a/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md
+++ b/docs/known-issues/pt/put-price-overwrites-kit-price-logic.md
@@ -18,9 +18,7 @@ internalReference: 404486
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A composição do preço do KIT deve ser baseada no cálculo de seus componentes e suas quantidades.
diff --git a/docs/known-issues/pt/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md b/docs/known-issues/pt/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md
index 8929031ef..eeb9cd0e8 100644
--- a/docs/known-issues/pt/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md
+++ b/docs/known-issues/pt/quantity-being-modified-in-the-wrong-item-with-product-list-component-io-sf.md
@@ -18,9 +18,7 @@ internalReference: 402976
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 No componente ["vtex.product-list"](https://github.com/vtex-apps/product-list), utilizado no Minicart IO/SF ([vtex.minicart](https://github.com/vtex-apps/minicart) v2) ou no "Cart v0" ([vtex.checkout-cart](https://github.com/vtex-apps/checkout-cart)), quando um carrinho tem o mesmo item fatiado em mais de uma ocorrência (por exemplo, quando é necessário para o rateio de descontos ou talvez quando tem itemAttachments), para alterar a quantidade para sua segunda ocorrência chamará o API para sua primeira ocorrência, portanto, a quantidade somada para o item estará errada.
 
diff --git a/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md b/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
index 74dc4aad9..b74859fff 100644
--- a/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
+++ b/docs/known-issues/pt/quantity-selector-component-doesnt-return-to-the-limit-value-when-user-quickly-clicks.md
@@ -18,9 +18,7 @@ internalReference: 659909
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Basicamente, existe uma função que recebe o estado atualizado do valor sendo controlado na tela pelo usuário (é um estado de uso). Esta função é usada em todo o componente para lidar com atualizações de estado de quantidade. Para que este estado seja atualizado automaticamente quando o usuário excede a quantidade retornada no contexto, relacionado à disponibilidade do item, ele é passado dentro de um useEffect.
diff --git a/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md b/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md
index 1e9df0302..ff7176383 100644
--- a/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md
+++ b/docs/known-issues/pt/quantity-selector-wont-let-me-change-the-value-by-typing.md
@@ -18,9 +18,7 @@ internalReference: 1057544
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O componente seletor de quantidade na Faststore está apresentando um bug. Se o valor mínimo de um produto for 10 e eu quiser digitar 15, o seletor não permitirá que eu exclua o 0 porque ele permitirá que digitemos 1, que seria um valor menor do que a quantidade mínima. Se eu quiser digitar 15, preciso digitar 150 e então poderei excluir o 0.
diff --git a/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md b/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
index ec1d9b8f3..a42c2bbbf 100644
--- a/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
+++ b/docs/known-issues/pt/quantityselector-on-stepper-mode-doesnt-refresh-after-reaching-max-available-qunatity.md
@@ -18,9 +18,7 @@ internalReference: 704458
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se você atingir a quantidade disponível do produto clicando mais de uma vez, o componente leva muito tempo para avisá-lo e nem mesmo atualiza o seletor de quantidade com a quantidade máxima disponível.
diff --git a/docs/known-issues/pt/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/pt/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
index 71b148917..4f52bbbfc 100644
--- a/docs/known-issues/pt/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
+++ b/docs/known-issues/pt/ransactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -18,9 +18,7 @@ internalReference: 541149
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md b/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
index 2c2f72b9f..7a6b9d805 100644
--- a/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
+++ b/docs/known-issues/pt/received-skus-association-approvals-dont-add-the-sellers-available-sales-channel-on-the-product-when-the-sku-is-sold-by-more-than-1-seller.md
@@ -18,9 +18,7 @@ internalReference: 562472
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um produto vendido por outro vendedor no catálogo do marketplace está disponível para ser vendido no canal de vendas desse vendedor.
diff --git a/docs/known-issues/pt/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md b/docs/known-issues/pt/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md
index 23510d696..634662038 100644
--- a/docs/known-issues/pt/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md
+++ b/docs/known-issues/pt/received-skus-export-function-not-working-for-admins-in-other-languages-only-pt-en-es.md
@@ -18,9 +18,7 @@ internalReference: 668122
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O recurso de exportação para recuperar uma planilha com os skus pendentes, aprovados ou rejeitados por vendedor não está funcionando quando o administrador está definido para qualquer outro idioma que não seja PT, EN, ES.
diff --git a/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md b/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md
index 99b930d60..34885004d 100644
--- a/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md
+++ b/docs/known-issues/pt/received-skus-filter-do-not-work-with-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 944533
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar filtrar os skus no módulo Received Skus, o marketplace pode optar por filtrar por vendedor, categoria e/ou marca.
diff --git a/docs/known-issues/pt/received-skus-review-tab-missing-products.md b/docs/known-issues/pt/received-skus-review-tab-missing-products.md
index f7c97130a..db897e6cf 100644
--- a/docs/known-issues/pt/received-skus-review-tab-missing-products.md
+++ b/docs/known-issues/pt/received-skus-review-tab-missing-products.md
@@ -18,9 +18,7 @@ internalReference: 939877
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As ofertas enviadas pelos vendedores podem eventualmente ir para a guia Revisão do Skus Recebido do Marketplace, dependendo se foram aprovadas ou não nas regras de Qualidade da Oferta.
diff --git a/docs/known-issues/pt/redirection-with-parameters-in-cms-builder-does-not-work.md b/docs/known-issues/pt/redirection-with-parameters-in-cms-builder-does-not-work.md
index 5e878db37..5302d9e77 100644
--- a/docs/known-issues/pt/redirection-with-parameters-in-cms-builder-does-not-work.md
+++ b/docs/known-issues/pt/redirection-with-parameters-in-cms-builder-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 593906
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o redirecionamento usando parâmetros gera um erro apesar da URL Bilder admin dizer que é possível usar parâmetros.
diff --git a/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md b/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md
index b8e09762e..4dd95ef20 100644
--- a/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md
+++ b/docs/known-issues/pt/redirects-are-being-counted-multiple-times.md
@@ -18,9 +18,7 @@ internalReference: 1066548
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar carregar um arquivo com mais de 200 redirecionamentos, o front entra em um loop e lê esses redirecionamentos três vezes. Isso pode levar a mais redirecionamentos na mensagem de erro na tela ou no modal de carregamento. Os redirecionamentos não estão sendo duplicados, mas estão sendo lidos mais de uma vez.
diff --git a/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md b/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
index ea1642c10..87ae35c89 100644
--- a/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
+++ b/docs/known-issues/pt/redirects-for-preview-links-when-using-in-the-final-of-the-url.md
@@ -18,9 +18,7 @@ internalReference: 927041
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na Faststore, se você acessar um link de visualização com o / no final do URL, o link será redirecionado para uma página como esta https://starter.prd-dv-fastorecloud-eks-n10-use1a.us-east-1.eksctl.io.ingress.vtex.io/s
diff --git a/docs/known-issues/pt/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md b/docs/known-issues/pt/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md
index 9ceba127d..bc2fb7f69 100644
--- a/docs/known-issues/pt/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md
+++ b/docs/known-issues/pt/refactor-our-reset-password-flow-to-call-the-new-corresponding-mutation-in-the-graphql-app.md
@@ -18,9 +18,7 @@ internalReference: 577825
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O usuário não pode fazer o login após mudar a senha temporária e é direcionado para a tela para solicitar acesso
diff --git a/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md b/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md
index d52eab647..1311e71be 100644
--- a/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md
+++ b/docs/known-issues/pt/refid-behavior-not-consistent-between-api-and-ui.md
@@ -18,9 +18,7 @@ internalReference: 910050
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md b/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
index cd3b862ff..8e0255a41 100644
--- a/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
+++ b/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-mastercard-as-visa.md
@@ -18,9 +18,7 @@ internalReference: 893588
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O conflito de regex nos faz identificar incorretamente a marca dos cartões no checkout.
diff --git a/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-the-cards-brand.md b/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-the-cards-brand.md
index e6831801e..22d261b3a 100644
--- a/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-the-cards-brand.md
+++ b/docs/known-issues/pt/regex-conflict-causes-us-to-misidentify-the-cards-brand.md
@@ -18,9 +18,7 @@ internalReference: 316213
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md b/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md
index 0008f29e9..c3fe7cd27 100644
--- a/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md
+++ b/docs/known-issues/pt/region-api-returns-seller-list-due-to-cache.md
@@ -18,9 +18,7 @@ internalReference: 969692
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar uma estrutura de subconta com região, se a API Get sellers by region or address for usada em ambas as contas para o mesmo canal de vendas e uma delas não estiver disponível para esse canal de vendas, ela retornará uma lista de vendedores devido ao cache.
diff --git a/docs/known-issues/pt/regionalization-or-trade-policies-arent-considered-while-filtering-or.md b/docs/known-issues/pt/regionalization-or-trade-policies-arent-considered-while-filtering-or.md
index 525ac8943..a92f49cae 100644
--- a/docs/known-issues/pt/regionalization-or-trade-policies-arent-considered-while-filtering-or.md
+++ b/docs/known-issues/pt/regionalization-or-trade-policies-arent-considered-while-filtering-or.md
@@ -18,9 +18,7 @@ internalReference: 571101
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Ao usar a Pesquisa Inteligente (via PLP ou mesmo sua API) junto com a regionalização (regionId) ou a variação da política comercial, a classificação e a filtragem de itens por preço não funcionam corretamente.
 
diff --git a/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md b/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
index 4ab302d59..3952db109 100644
--- a/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
+++ b/docs/known-issues/pt/regions-api-doesnt-calculate-the-seller-1-correctly-while-requesting-nonwhitelabel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 551402
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md b/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
index 32033374a..af6b2574b 100644
--- a/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
+++ b/docs/known-issues/pt/registered-users-not-logged-in-cannot-finish-checkout-when-changing-from-delivery-to-pickup-on-the-checkout-page.md
@@ -18,9 +18,7 @@ internalReference: 870845
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário registrado (não conectado) inicia o checkout com Entrega como opção de envio e, posteriormente, muda para retirada, ao tentar concluir o checkout, a mensagem de erro "O campo Número no anexo de envio é inválido" será exibida e não permitirá a realização do pedido.
diff --git a/docs/known-issues/pt/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md b/docs/known-issues/pt/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md
index e781cd8fc..1eabcb1fa 100644
--- a/docs/known-issues/pt/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md
+++ b/docs/known-issues/pt/regular-promotion-using-gift-conflicts-with-value-filters-on-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 445569
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md b/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
index 6bbf70f8d..fff0bbe52 100644
--- a/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
+++ b/docs/known-issues/pt/removing-ean-via-api-is-not-inactivating-skus-without-refids.md
@@ -18,9 +18,7 @@ internalReference: 626031
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/render-component-issues-on-site-editor.md b/docs/known-issues/pt/render-component-issues-on-site-editor.md
index 38348cc1c..f3c204fd6 100644
--- a/docs/known-issues/pt/render-component-issues-on-site-editor.md
+++ b/docs/known-issues/pt/render-component-issues-on-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 415674
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido à quantidade de informações na página, o editor do site pode ter problemas ao renderizar blocos. Esse comportamento ocorre de forma intermitente, às vezes os componentes não são renderizados e às vezes são renderizados duas vezes. Pode acontecer de nenhum bloco aparecer no editor do site:
diff --git a/docs/known-issues/pt/reorder-collection-failing-for-large-collections.md b/docs/known-issues/pt/reorder-collection-failing-for-large-collections.md
index daaa5acac..e11e9b306 100644
--- a/docs/known-issues/pt/reorder-collection-failing-for-large-collections.md
+++ b/docs/known-issues/pt/reorder-collection-failing-for-large-collections.md
@@ -18,9 +18,7 @@ internalReference: 408140
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na nova UI de administração de coleções, quando um usuário tenta reordenar a exibição de pedidos de produtos, a mutação GraphQL do catálogo que executa essa ação geralmente falha
diff --git a/docs/known-issues/pt/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md b/docs/known-issues/pt/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md
index f06169110..767eca9c3 100644
--- a/docs/known-issues/pt/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md
+++ b/docs/known-issues/pt/repeated-items-in-the-purchase-summary-for-carts-with-more-than-20-items.md
@@ -18,9 +18,7 @@ internalReference: 367339
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao chegar à caixa com mais de 20 itens, os itens mostrados no resumo de compras (lista de itens do topo direito) podem ser duplicados. Os totalizadores e até mesmo o API estão corretos. O cenário não acontece na lista principal de itens (etapa do carrinho de compras).
diff --git a/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md b/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md
index 122336871..a7e6597b2 100644
--- a/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md
+++ b/docs/known-issues/pt/replacing-orders-with-different-sales-channel.md
@@ -18,9 +18,7 @@ internalReference: 982965
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Identificamos que não é possível substituir uma SKU no pedido se o canal de vendas (SC), igual a 1, não estiver disponível para a conta.
diff --git a/docs/known-issues/pt/replicated-pending-payment-emails.md b/docs/known-issues/pt/replicated-pending-payment-emails.md
index 25f6ca5cb..30473fbd9 100644
--- a/docs/known-issues/pt/replicated-pending-payment-emails.md
+++ b/docs/known-issues/pt/replicated-pending-payment-emails.md
@@ -18,9 +18,7 @@ internalReference: 348932
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há alguns pedidos que têm um email replicado de pagamento pendente em poucos minutos. Até mesmo dez e-mails.
diff --git a/docs/known-issues/pt/request-capture-not-registering-new-events-when-using-legacy-stores.md b/docs/known-issues/pt/request-capture-not-registering-new-events-when-using-legacy-stores.md
index 821502a9a..081d2789c 100644
--- a/docs/known-issues/pt/request-capture-not-registering-new-events-when-using-legacy-stores.md
+++ b/docs/known-issues/pt/request-capture-not-registering-new-events-when-using-legacy-stores.md
@@ -18,9 +18,7 @@ internalReference: 604254
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, ao utilizar lojas portal VTEX (lojas não VTEX IO), a aplicação de captura de pedidos não está registrando eventos especificamente para as visitas às páginas de produtos.
diff --git a/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md b/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md
index 1289cb7ed..3cbe4efa5 100644
--- a/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md
+++ b/docs/known-issues/pt/request-routing-is-inconsistent-when-running-ab-tests.md
@@ -18,9 +18,7 @@ internalReference: 931246
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 As solicitações HTTP de navegação da loja não respeitam o cookie de seleção de espaço de trabalho durante a sessão. Na verdade, durante uma única sessão, um usuário pode receber respostas de todos os espaços de trabalho que estão sendo testados.
 
diff --git a/docs/known-issues/pt/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md b/docs/known-issues/pt/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md
index af5e4e18d..44a730dd5 100644
--- a/docs/known-issues/pt/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md
+++ b/docs/known-issues/pt/restrict-the-defaultsrc-of-the-header-content-security-policy-could-break-the-checkout.md
@@ -18,9 +18,7 @@ internalReference: 763359
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A restrição do cabeçalho da Política de Segurança de Conteúdo pode fazer com que os arquivos de checkout não sejam carregados. Por exemplo, a configuração `default-src 'self'` pode fazer com que arquivos provenientes do vtex.com não sejam carregados.
diff --git a/docs/known-issues/pt/retrieve-users-orders-api-does-not-return-paging.md b/docs/known-issues/pt/retrieve-users-orders-api-does-not-return-paging.md
index 35e27992e..caec4df35 100644
--- a/docs/known-issues/pt/retrieve-users-orders-api-does-not-return-paging.md
+++ b/docs/known-issues/pt/retrieve-users-orders-api-does-not-return-paging.md
@@ -18,9 +18,7 @@ internalReference: 516699
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md b/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
index cee827f55..95c43d341 100644
--- a/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
+++ b/docs/known-issues/pt/returned-itens-with-same-skuid-on-different-uniqueid-arrays-it-is-not-visible-properly.md
@@ -18,9 +18,7 @@ internalReference: 1050294
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/returned-package-as-delivering-to-final-customer-on-my-account.md b/docs/known-issues/pt/returned-package-as-delivering-to-final-customer-on-my-account.md
index 46f05c97c..4769af520 100644
--- a/docs/known-issues/pt/returned-package-as-delivering-to-final-customer-on-my-account.md
+++ b/docs/known-issues/pt/returned-package-as-delivering-to-final-customer-on-my-account.md
@@ -18,9 +18,7 @@ internalReference: 415482
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um cenário em que o pacote devolvido aparece como entrega na página **Minha conta > Minhas encomendas***. Parece que mais de um pacote será entregue ao cliente em vez de mostrar que o pacote já foi entregue ao cliente e que um novo pacote foi gerado simbolizando a devolução.
diff --git a/docs/known-issues/pt/review-flow-for-updatestock-netshoes.md b/docs/known-issues/pt/review-flow-for-updatestock-netshoes.md
index e5eda5828..66ee41a5d 100644
--- a/docs/known-issues/pt/review-flow-for-updatestock-netshoes.md
+++ b/docs/known-issues/pt/review-flow-for-updatestock-netshoes.md
@@ -18,9 +18,7 @@ internalReference: 646869
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Fluxo de revisão para UpdateStock
diff --git a/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md b/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
index 4c271a0ad..0537dcbaa 100644
--- a/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
+++ b/docs/known-issues/pt/reward-value-not-added-or-have-a-different-value-added-to-gift-card.md
@@ -18,9 +18,7 @@ internalReference: 844079
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O valor do prêmio pode não ser ou ter um valor diferente adicionado ao cartão-presente do comprador quando a promoção estiver configurada para aplicar o valor do prêmio quando o status do pedido mudar para pagamento aprovado.
diff --git a/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md b/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md
index 3a671d5c1..cc2973f0f 100644
--- a/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md
+++ b/docs/known-issues/pt/rewriter-is-not-receiving-url-updates.md
@@ -18,9 +18,7 @@ internalReference: 1066527
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando uma URL é alterada/excluída no catálogo, o reescritor não recebe essa alteração. Como o reescritor não é notificado sobre isso, o URL ainda está apontando para o tipo errado, o que também pode levar a problemas no IS.
diff --git a/docs/known-issues/pt/rounding-of-totalvalue-in-listorders.md b/docs/known-issues/pt/rounding-of-totalvalue-in-listorders.md
index 444a17b4e..4e610b3ef 100644
--- a/docs/known-issues/pt/rounding-of-totalvalue-in-listorders.md
+++ b/docs/known-issues/pt/rounding-of-totalvalue-in-listorders.md
@@ -18,9 +18,7 @@ internalReference: 756314
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando consultamos o valor do pedido através da IU, ele exibe um valor e quando o consultamos através da API Get Orders, vemos um valor 0,01 maior. Este comportamento ocorre devido ao arredondamento feito no banco de dados. Entretanto, este comportamento não afeta o valor total do pedido, ele é apenas uma visualização na ListOrders, o valor total do pedido ainda está correto.
diff --git a/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md b/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
index 2fa3534d1..db774a276 100644
--- a/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
+++ b/docs/known-issues/pt/roundingmode-ceilingfloor-not-working-properly-among-items-with-unitmultiplier-other-than-1.md
@@ -18,9 +18,7 @@ internalReference: 968349
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md b/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
index 8ede44a56..cd6c2fd1f 100644
--- a/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
+++ b/docs/known-issues/pt/route-prioritization-does-not-offer-the-best-option-in-terms-of-quantity-of-packages-and-items.md
@@ -18,9 +18,7 @@ internalReference: 927747
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na logística, o primeiro critério de desempate quando o sistema está escolhendo a rota (armazém + doca + política de remessa) está relacionado ao número de pacotes necessários para essa rota específica; menos pacotes significa que a rota deve ser melhor.
diff --git a/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md b/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
index 94f422ef2..a9da1cabc 100644
--- a/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
+++ b/docs/known-issues/pt/sales-channel-configured-in-b2b-settings-is-not-assigned-after-approving-organizations.md
@@ -18,9 +18,7 @@ internalReference: 866933
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O canal de vendas configurado nas configurações de organizações B2B não é salvo nos detalhes da organização.
diff --git a/docs/known-issues/pt/sales-channel-info-divergent-between-ui-and-api.md b/docs/known-issues/pt/sales-channel-info-divergent-between-ui-and-api.md
index 69d126059..78904b271 100644
--- a/docs/known-issues/pt/sales-channel-info-divergent-between-ui-and-api.md
+++ b/docs/known-issues/pt/sales-channel-info-divergent-between-ui-and-api.md
@@ -18,9 +18,7 @@ internalReference: 802560
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, as informações sobre o canal de vendas podem ser diferentes, dependendo de onde o cliente está verificando.
diff --git a/docs/known-issues/pt/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md b/docs/known-issues/pt/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md
index 4b7457893..2aa372968 100644
--- a/docs/known-issues/pt/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md
+++ b/docs/known-issues/pt/sales-performance-calendar-has-a-problem-with-some-european-time-zones.md
@@ -18,9 +18,7 @@ internalReference: 718470
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em nosso Painel de Controle de Desempenho de Vendas*** disponibilizamos, dentro dos filtros, a possibilidade de selecionar um período personalizado para validar as informações correspondentes. No entanto, neste momento temos um problema com nosso calendário quando se trata de alguns **fusos horários europeus*** (até agora identificamos o problema apenas em **Reino Unido e Portugal***).
diff --git a/docs/known-issues/pt/save-button-disabled-when-modifying-imported-search-synonyms.md b/docs/known-issues/pt/save-button-disabled-when-modifying-imported-search-synonyms.md
index 419ceb741..e5e500652 100644
--- a/docs/known-issues/pt/save-button-disabled-when-modifying-imported-search-synonyms.md
+++ b/docs/known-issues/pt/save-button-disabled-when-modifying-imported-search-synonyms.md
@@ -18,9 +18,7 @@ internalReference: 508893
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar fazer qualquer mudança em uma configuração de sinônimo que era anteriormente importada por um arquivo csv, o botão salvar é sempre desativado, não importando a mudança:
diff --git a/docs/known-issues/pt/scheduled-banners-doesnt-work-properly.md b/docs/known-issues/pt/scheduled-banners-doesnt-work-properly.md
index f84e7abd0..04a1fb9b8 100644
--- a/docs/known-issues/pt/scheduled-banners-doesnt-work-properly.md
+++ b/docs/known-issues/pt/scheduled-banners-doesnt-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 400194
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao programar um banner no CMS, ele não funciona como pretendido e muitas vezes o banner cai ou não mostra todas as informações nele contidas.
diff --git a/docs/known-issues/pt/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md b/docs/known-issues/pt/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md
index aeec58ba9..6049ecedb 100644
--- a/docs/known-issues/pt/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md
+++ b/docs/known-issues/pt/scheduled-delivery-may-show-incorrect-price-when-switching-between-delivery-and-scheduled.md
@@ -18,9 +18,7 @@ internalReference: 770250
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando é configurada uma promoção de valor máximo de remessa, se você começar a mudar entre entrega padrão e entrega programada várias vezes, pode haver um preço de entrega programada diferente na IU
diff --git a/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md b/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md
index 467e5b216..6d4dde308 100644
--- a/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md
+++ b/docs/known-issues/pt/schema-validation-failing-for-custom-types-in-headless-cms.md
@@ -18,9 +18,7 @@ internalReference: 903687
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md b/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md
index 47a5059ed..53e53fc32 100644
--- a/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md
+++ b/docs/known-issues/pt/scroll-issue-when-zooming-after-search-page-render.md
@@ -18,9 +18,7 @@ internalReference: 979464
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md b/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
index 36966e36b..6050170f4 100644
--- a/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
+++ b/docs/known-issues/pt/scroll-issues-when-swiping-in-mobile-in-quick-view-when-theres-a-slider-layout-on-background.md
@@ -18,9 +18,7 @@ internalReference: 985097
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao deslizar a imagem de um produto na visualização rápida em dispositivos móveis quando há um layout de controle deslizante em segundo plano, ambos os controles deslizantes são movidos para o próximo em vez de apenas a imagem na visualização rápida
diff --git a/docs/known-issues/pt/search-analytics-duplicated-events.md b/docs/known-issues/pt/search-analytics-duplicated-events.md
index 52093dfec..f73f7281a 100644
--- a/docs/known-issues/pt/search-analytics-duplicated-events.md
+++ b/docs/known-issues/pt/search-analytics-duplicated-events.md
@@ -18,9 +18,7 @@ internalReference: 771986
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns eventos dos relatórios da Pesquisa Inteligente estão duplicados, o que pode afetar a exibição de análise no módulo de administração de pesquisa.
diff --git a/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md b/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
index 1632028ff..14f5a8147 100644
--- a/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
+++ b/docs/known-issues/pt/search-analytics-report-divergences-between-versions-withwithout-funnel-metrics.md
@@ -18,9 +18,7 @@ internalReference: 980297
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O relatório de análise de pesquisa exportado como CSV pode divergir entre sua versão com métricas de funil e sua versão sem elas.
diff --git a/docs/known-issues/pt/search-api-does-not-accept-special-characters.md b/docs/known-issues/pt/search-api-does-not-accept-special-characters.md
index 6152be9ce..d42615a4b 100644
--- a/docs/known-issues/pt/search-api-does-not-accept-special-characters.md
+++ b/docs/known-issues/pt/search-api-does-not-accept-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 754363
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API de pesquisa de catálogo, documentada aqui: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/products/search/-search- , não aceita termos com caracteres especiais como "apóstrofo" ou "aspas".
diff --git a/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md b/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
index 92d4c9f84..c5bf9e890 100644
--- a/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
+++ b/docs/known-issues/pt/search-api-not-returning-showifnotavailabletrue-skus-for-fqspecificationfilter-queries.md
@@ -18,9 +18,7 @@ internalReference: 336896
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md b/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
index 0981fda61..d5c00c1ea 100644
--- a/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
+++ b/docs/known-issues/pt/search-api-not-working-properly-after-login-in-using-the-call-center-operator.md
@@ -18,9 +18,7 @@ internalReference: 304586
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Busca API que não funciona corretamente após o login no uso do Call Center Operator.
diff --git a/docs/known-issues/pt/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md b/docs/known-issues/pt/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md
index 447dab8de..f93a013a9 100644
--- a/docs/known-issues/pt/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md
+++ b/docs/known-issues/pt/search-api-using-oorderbynameasc-or-oorderbynamedesc-returns-results-considering-difference-in-lower-case-and-uppercase-for-first-letter.md
@@ -18,9 +18,7 @@ internalReference: 305247
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pesquisa API usando O=OrderByNameASC ou O=OrderByNameDESC retorna resultados considerando a diferença em minúsculas e maiúsculas para a primeira letra
diff --git a/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md b/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
index 8e89114d7..5b3d74edb 100644
--- a/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
+++ b/docs/known-issues/pt/search-autocomplete-providing-outdated-url-after-navigating-through-suggestions.md
@@ -18,9 +18,7 @@ internalReference: 968604
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No componente "barra de pesquisa" com "autocomplete-result-list.v2", passar o mouse sobre as sugestões de pesquisa também altera os produtos sugeridos, bem como o texto de "ver todos os {n} produtos" para mencionar a pesquisa selecionada, mas o hiperlink de "ver todos" segue o termo de pesquisa original em vez do selecionado.
diff --git a/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md b/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
index 0b9a03473..42f196a1d 100644
--- a/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
+++ b/docs/known-issues/pt/search-banners-not-following-the-operator-and-for-trigger-conditions.md
@@ -18,9 +18,7 @@ internalReference: 1053614
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As condições para banners de pesquisa (gerenciados por meio de "/admin/search/v4/banners/") não são compatíveis com o operador "AND", conforme apresentado em suas regras de acionamento. A interface do usuário está errada, e o operador se comporta como "OR" de forma fixa.
diff --git a/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md b/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md
index 25aebef11..72fbacbe5 100644
--- a/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md
+++ b/docs/known-issues/pt/search-by-ean-not-working-on-received-skus.md
@@ -18,9 +18,7 @@ internalReference: 510907
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O recurso de pesquisa Received Skus permite que o marketplace pesquise um produto ou sku pelos seguintes critérios:
diff --git a/docs/known-issues/pt/search-filters-disappear-intermittently.md b/docs/known-issues/pt/search-filters-disappear-intermittently.md
index 578410e2d..a76a3c298 100644
--- a/docs/known-issues/pt/search-filters-disappear-intermittently.md
+++ b/docs/known-issues/pt/search-filters-disappear-intermittently.md
@@ -18,9 +18,7 @@ internalReference: 734221
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns cenários, quando o usuário clica no botão para limpar os filtros selecionados na página de busca, os mesmos filtros param de renderizar e são exibidos na tela.
diff --git a/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md b/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
index 80629e5fb..aa402cd1e 100644
--- a/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
+++ b/docs/known-issues/pt/search-has-no-products-if-seller-1-name-in-the-seller-management-differs-from-trading-name-in-account-management-when-using-b2b-suite.md
@@ -18,9 +18,7 @@ internalReference: 946391
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As organizações B2B usam os nomes dos vendedores do Gerenciamento de vendedores. Se uma organização tiver o vendedor 1 atribuído, o nome salvo será do Gerenciamento de vendedores, mas nenhum produto poderá ser mostrado na pesquisa se for diferente do nome comercial no Gerenciamento de contas.
diff --git a/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md b/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md
index 8bdfd1a04..45c0833fe 100644
--- a/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md
+++ b/docs/known-issues/pt/search-navigator-filter-price-range-yielding-incorrect-results.md
@@ -18,9 +18,7 @@ internalReference: 504992
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, ao utilizar o filtro de busca da marca Navigator juntamente com uma faixa de preço em uma edição comercial da VTEX, produtos fora da marca filtrada podem ser mostrados.
diff --git a/docs/known-issues/pt/search-not-working-properly-on-store-framework-jamstack.md b/docs/known-issues/pt/search-not-working-properly-on-store-framework-jamstack.md
index 6f1e012a1..d0d24712d 100644
--- a/docs/known-issues/pt/search-not-working-properly-on-store-framework-jamstack.md
+++ b/docs/known-issues/pt/search-not-working-properly-on-store-framework-jamstack.md
@@ -18,9 +18,7 @@ internalReference: 383231
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As sugestões de busca não funcionam corretamente em SFJ devido à falta de eventos implementados.
diff --git a/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md b/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md
index a72bdf3d1..940103f6d 100644
--- a/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md
+++ b/docs/known-issues/pt/search-resolver-applying-messages-translations-over-already-translated-content.md
@@ -18,9 +18,7 @@ internalReference: 865918
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Search Resolver (camada GraphQL para Pesquisa Inteligente) solicita traduções do serviço de Mensagens, mesmo para lojas de um único idioma ou conteúdo já traduzido em uma loja de vários idiomas.
diff --git a/docs/known-issues/pt/searchable-flag-does-not-work-on-legacy-cms-collection.md b/docs/known-issues/pt/searchable-flag-does-not-work-on-legacy-cms-collection.md
index 77f936ce6..d4f9ba74e 100644
--- a/docs/known-issues/pt/searchable-flag-does-not-work-on-legacy-cms-collection.md
+++ b/docs/known-issues/pt/searchable-flag-does-not-work-on-legacy-cms-collection.md
@@ -18,9 +18,7 @@ internalReference: 322552
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A bandeira pesquisável não funciona na Coleção CMS herdada. Nosso documento explica que quando usamos esta bandeira, se pesquisarmos o nome da coleção, ela deve retornar os itens associados a esta coleção.
diff --git a/docs/known-issues/pt/searches-falls-into-fuzzy-when-using-special-characters.md b/docs/known-issues/pt/searches-falls-into-fuzzy-when-using-special-characters.md
index 236e7f1eb..b86dfb683 100644
--- a/docs/known-issues/pt/searches-falls-into-fuzzy-when-using-special-characters.md
+++ b/docs/known-issues/pt/searches-falls-into-fuzzy-when-using-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 382382
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao procurar termos com caracteres especiais como vírgulas (`,`), apóstrofes (```), hashes (``#`) e colons (`:``), isso desencadeia fallback e fuzzy, fazendo com que os resultados da busca pareçam estranhos.
diff --git a/docs/known-issues/pt/searches-with-at-the-end-not-working-correctly.md b/docs/known-issues/pt/searches-with-at-the-end-not-working-correctly.md
index dfc3cc6fd..8ab1d8ee7 100644
--- a/docs/known-issues/pt/searches-with-at-the-end-not-working-correctly.md
+++ b/docs/known-issues/pt/searches-with-at-the-end-not-working-correctly.md
@@ -18,9 +18,7 @@ internalReference: 509101
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar com uma % no final da busca não funciona como esperado devido a problemas de decodificação.
diff --git a/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md b/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
index 628c1e6cf..0ec29b015 100644
--- a/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
+++ b/docs/known-issues/pt/searching-not-return-document-when-the-value-contains-a-plus-symbol.md
@@ -18,9 +18,7 @@ internalReference: 828170
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao pesquisar um documento usando um valor de campo que inclui o símbolo "+", a pesquisa não retorna o documento. Isso acontece porque o símbolo "+" é interpretado incorretamente, o que faz com que o valor da pesquisa não corresponda ao valor existente.
diff --git a/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md b/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md
index 58bafd895..ef5dbcee7 100644
--- a/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md
+++ b/docs/known-issues/pt/segment-cookie-updated-only-after-refreshing-the-page.md
@@ -18,9 +18,7 @@ internalReference: 647116
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns recursos e componentes da VTEX podem usar dados solicitados do cookie de segmento para apresentar informações (como preço, dados de promoção, disponibilidade de SKU etc.) na vitrine. Esse cookie é armazenado no navegador do usuário quando a sessão é criada. Às vezes, principalmente em cenários dinâmicos em que é necessário fazer alterações na fachada, o que aciona uma atualização do Cookie Segment, o cookie em si perde alguns dados, o que é resultado de um comportamento no tempo de execução de renderização que não aciona a alteração do segmento no contexto
diff --git a/docs/known-issues/pt/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md b/docs/known-issues/pt/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md
index dc317cd82..75e22ab1c 100644
--- a/docs/known-issues/pt/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md
+++ b/docs/known-issues/pt/selection-of-sellers-available-in-the-commercial-policy-is-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 515480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A mudança de disponibilidade de um vendedor em uma política comercial não está sendo corretamente reconhecida no catálogo. Isto pode causar dois cenários: um produto de um vendedor não selecionado torna-se disponível ou um produto de um vendedor selecionado torna-se indisponível.
diff --git a/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md b/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md
index e101d0cbd..0a7bf0a6d 100644
--- a/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md
+++ b/docs/known-issues/pt/seller-commission-updates-does-not-index-binded-skus.md
@@ -18,9 +18,7 @@ internalReference: 891162
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o comerciante atualiza a comissão do vendedor na interface do usuário de gerenciamento do vendedor, os skus vinculados relacionados a esse vendedor não são indexados automaticamente.
diff --git a/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md b/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md
index 3edb77654..752947388 100644
--- a/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md
+++ b/docs/known-issues/pt/seller-group-creation-does-not-add-selected-sellers.md
@@ -18,9 +18,7 @@ internalReference: 926969
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O marketplace pode criar grupos com alguns vendedores na interface de gerenciamento do vendedor.
diff --git a/docs/known-issues/pt/seller-logo-not-being-saved-as-an-url.md b/docs/known-issues/pt/seller-logo-not-being-saved-as-an-url.md
index cd516f655..16318f954 100644
--- a/docs/known-issues/pt/seller-logo-not-being-saved-as-an-url.md
+++ b/docs/known-issues/pt/seller-logo-not-being-saved-as-an-url.md
@@ -18,9 +18,7 @@ internalReference: 736716
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/seller-portal-account-not-able-to-export-baseprice.md b/docs/known-issues/pt/seller-portal-account-not-able-to-export-baseprice.md
index e0ae92a0d..5cd52ede8 100644
--- a/docs/known-issues/pt/seller-portal-account-not-able-to-export-baseprice.md
+++ b/docs/known-issues/pt/seller-portal-account-not-able-to-export-baseprice.md
@@ -18,9 +18,7 @@ internalReference: 408868
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas contas do Portal do Vendedor não são capazes de exportar `basePrice'.
diff --git a/docs/known-issues/pt/seller-portal-product-doesnt-load-when-without-images.md b/docs/known-issues/pt/seller-portal-product-doesnt-load-when-without-images.md
index 30f86da2b..0abc6831f 100644
--- a/docs/known-issues/pt/seller-portal-product-doesnt-load-when-without-images.md
+++ b/docs/known-issues/pt/seller-portal-product-doesnt-load-when-without-images.md
@@ -18,9 +18,7 @@ internalReference: 800480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para contas do portal do vendedor, se você tiver um produto sem imagens para cada sku, a interface do usuário do produto não será carregada corretamente.
diff --git a/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md b/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
index 0c663e8ad..1fd077d6f 100644
--- a/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
+++ b/docs/known-issues/pt/seller-portal-promotion-minimum-item-price-condition-not-working-as-expected.md
@@ -18,9 +18,7 @@ internalReference: 928558
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md b/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md
index 3d131bbde..c3c8d2280 100644
--- a/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md
+++ b/docs/known-issues/pt/seller-portal-select-specifications-dropdown-malfunctioning.md
@@ -18,9 +18,7 @@ internalReference: 711303
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a caixa de seleção de especificação de produto da página accountname.myvtex.com/admin/products/new/ tem um comportamento defeituoso quando se tenta selecionar um valor para uma especificação de produto.
diff --git a/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md b/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
index 088205070..182794031 100644
--- a/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
+++ b/docs/known-issues/pt/seller-register-ui-doesnt-send-products-to-reindex-when-inactivating-a-seller.md
@@ -18,9 +18,7 @@ internalReference: 915970
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar a nova interface de usuário de experiência do vendedor, /admin/sellers, a ação de inativar um vendedor deve reindexar seus produtos relacionados para que possam ser removidos dos mercados associados, o que não está acontecendo atualmente.
diff --git a/docs/known-issues/pt/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md b/docs/known-issues/pt/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md
index 3ff0b056f..a0ad1d82f 100644
--- a/docs/known-issues/pt/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md
+++ b/docs/known-issues/pt/seller-selection-algorithm-doesnt-consider-the-real-availability-of-the-item-to-choose-the-best-option.md
@@ -18,9 +18,7 @@ internalReference: 360097
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O algoritmo de seleção do vendedor considera o estoque dos itens a fim de selecionar o melhor vendedor de whitelabel para um determinado contexto.
diff --git a/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md b/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md
index f9726f2d2..a200f914e 100644
--- a/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md
+++ b/docs/known-issues/pt/sellers-order-invoiced-with-problem-in-the-payment-capture.md
@@ -18,9 +18,7 @@ internalReference: 376646
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No momento, da forma como nossa arquitetura foi construída, tanto o vendedor quanto o marketplace são duas entidades totalmente diferentes. Funciona assim: o Marketplace é responsável por receber o dinheiro do cliente e o Vendedor é responsável por toda a logística até o momento em que entrega as mercadorias ao cliente.
diff --git a/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md b/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md
index 0e1abc943..9b0717bad 100644
--- a/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md
+++ b/docs/known-issues/pt/service-type-name-field-wrongly-returned-via-api.md
@@ -18,9 +18,7 @@ internalReference: 961278
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, as APIs do Catálogo de SKU não estão retornando corretamente o nome de um tipo de serviço. Em vez disso, está sendo retornado o nome do valor do serviço.
diff --git a/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md b/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md
index c98e387bd..b5ccb7c7a 100644
--- a/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md
+++ b/docs/known-issues/pt/services-prices-are-not-updated-when-added-to-items.md
@@ -18,9 +18,7 @@ internalReference: 822107
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os preços dos serviços não são atualizados se tiverem sido adicionados a um item antes da alteração do preço do serviço no administrador. Isso fará com que o pedido seja criado com um preço desatualizado.
diff --git a/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md b/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
index b7db56b26..e74d29f0c 100644
--- a/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
+++ b/docs/known-issues/pt/session-cookies-are-shared-between-different-bindings-when-they-are-not-in-the-same-path-level.md
@@ -18,9 +18,7 @@ internalReference: 925071
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os cookies para informações da sessão são exclusivos da vinculação de conta específica, mas as vinculações que não estão no mesmo nível de caminho podem receber cookies de níveis inferiores, causando problemas.
diff --git a/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md b/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
index cdc8eba97..0cc157ba7 100644
--- a/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
+++ b/docs/known-issues/pt/settings-ui-doesnt-update-expiration-period-of-quotes.md
@@ -18,9 +18,7 @@ internalReference: 876576
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A UI de configurações de cotação B2B não atualiza o valor do período de expiração; ele é sempre 30.
diff --git a/docs/known-issues/pt/shared-products-import-error.md b/docs/known-issues/pt/shared-products-import-error.md
index f51d658bd..563fe2096 100644
--- a/docs/known-issues/pt/shared-products-import-error.md
+++ b/docs/known-issues/pt/shared-products-import-error.md
@@ -18,9 +18,7 @@ internalReference: 647962
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, temos um erro em alguns casos em que o caminho da categoria contém "/" e os produtos não podem ser importados para produtos compartilhados
diff --git a/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md b/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md
index ef34fa090..ce0aa923d 100644
--- a/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md
+++ b/docs/known-issues/pt/shipping-component-locked-in-waiting-for-more-information-state.md
@@ -18,9 +18,7 @@ internalReference: 780673
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A UI de Checkout não torna o componente de envio ao acessar a página de checkout diretamente através de etapa específica na URL (exceto para /cart e /expedição), os "dados de envio" estão incompletos, e há um aumento da latência no pedidoFormar solicitações API. Você verá a mensagem "À espera de mais informações" e não poderá prosseguir com a compra.
diff --git a/docs/known-issues/pt/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md b/docs/known-issues/pt/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md
index e333b5328..40e4ea16c 100644
--- a/docs/known-issues/pt/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md
+++ b/docs/known-issues/pt/shipping-options-are-not-shown-in-the-cart-when-there-is-scheduled-delivery-and-lean-shipping-activated.md
@@ -18,9 +18,7 @@ internalReference: 362685
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No carrinho, quando o endereço é selecionado, as lojas com o Lean Shipping ativado e que oferecem entrega/coleta agendada não mostram todas as opções disponíveis na visualização do envio; somente a entrega regular é mostrada e selecionada.
diff --git a/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md b/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md
index de50dee7b..731231b76 100644
--- a/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md
+++ b/docs/known-issues/pt/shipping-options-gets-frozen-when-trying-to-select-an-option.md
@@ -18,9 +18,7 @@ internalReference: 898888
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar a configuração de checkout B2B e ir e voltar entre as etapas de envio e pagamento, o envio fica congelado ao tentar selecionar uma opção.
diff --git a/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md b/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
index a3dd6d00d..a80c2b3fd 100644
--- a/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
+++ b/docs/known-issues/pt/shipping-policy-not-prioritized-due-reason-dismissed-as-a-matter-of-priority-even-with-better-cost.md
@@ -18,9 +18,7 @@ internalReference: 379685
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cliente estabelece um custo do armazém até o cais na taxa de embarque, isso pode afetar a seleção da política de embarque. Isto pode acontecer porque o custo da doca não está incluído na priorização das políticas de embarque. Portanto, uma política de embarque mais cara para o consumidor pode ser priorizada, já que o cálculo do valor do frete não levou em consideração o custo do cais.
diff --git a/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md b/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
index 3fb06444e..728f43c06 100644
--- a/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
+++ b/docs/known-issues/pt/shipping-policy-stuck-in-processing-status-is-displayed-as-active-in-the-new-logistics-ui.md
@@ -18,9 +18,7 @@ internalReference: 925914
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, a política de remessa pode ficar presa no status de processamento, mas na nova interface de usuário de logística você não consegue vê-la porque ela informa que o status está ativo.
diff --git a/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md b/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
index c25fef962..21724155a 100644
--- a/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
+++ b/docs/known-issues/pt/shipping-policy-that-does-not-deliver-on-weekends-is-being-considered.md
@@ -18,9 +18,7 @@ internalReference: 594828
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Antes, a funcionalidade "**Fins de semana e feriados**" e "**Horário comercial**" funcionavam em conjunto, em outras palavras, uma informação dependia da outra.
diff --git a/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md b/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
index 1108c10d3..764e17328 100644
--- a/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
+++ b/docs/known-issues/pt/shipping-policy-with-incorrect-maxvolume-on-spreadsheet-does-not-show-message-error-on-simulation.md
@@ -18,9 +18,7 @@ internalReference: 380471
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a Política de Embarque tem o MaxVolume abaixo na planilha, não há erro de mensagem a respeito disso na Simulação.
diff --git a/docs/known-issues/pt/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md b/docs/known-issues/pt/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md
index 5a2b9c4c3..e2ab63754 100644
--- a/docs/known-issues/pt/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md
+++ b/docs/known-issues/pt/shipping-preview-delivery-selector-showing-wrong-time-in-case-of-multiple-packagesdeadlines.md
@@ -18,9 +18,7 @@ internalReference: 264441
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se o carrinho tiver vários pacotes com diferentes prazos de entrega, o seletor de entrega de Previsão de Entrega exibe apenas um dos termos, dando informações incorretas.
diff --git a/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md b/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
index 59d2e4172..f63941d9a 100644
--- a/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
+++ b/docs/known-issues/pt/shipping-preview-does-not-use-sla-name-for-display-in-ui.md
@@ -18,9 +18,7 @@ internalReference: 574651
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md b/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
index fe4783acb..a048c04a9 100644
--- a/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
+++ b/docs/known-issues/pt/shipping-preview-shows-pickup-postal-code-for-shipping-when-there-is-package-split-for-pickup-and-shipping.md
@@ -18,9 +18,7 @@ internalReference: 938124
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na visualização do envio, ao selecionar a retirada na loja, mas nem todos os itens estão disponíveis para essa retirada, o endereço exibido para envio é o da retirada escolhida, e não é possível alterá-lo. No formulário de pedido, o endereço selecionado para envio está correto.
diff --git a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
index 7094c5d0c..efba5d7bb 100644
--- a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
+++ b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-date-when-its-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 743774
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Checkout UI converte a hora usando o fuso horário do computador exibindo a data de entrega de forma incorreta na visualização da remessa (carrinho) quando os itens são entregues programados.
diff --git a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
index e801b5d6a..93491d751 100644
--- a/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
+++ b/docs/known-issues/pt/shipping-preview-wrongly-displaying-the-price-when-its-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 532487
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O preço de entrega exibido no shipping-preview (carrinho) está incorreto quando os itens têm entrega programada e todos esses itens saem no mesmo SLA. Mesmo com a API retornando o valor correto, a interface do usuário não reflete essa informação e exibe o valor incorreto.
diff --git a/docs/known-issues/pt/shipping-preview-wrongly-reporting-pickup-selection.md b/docs/known-issues/pt/shipping-preview-wrongly-reporting-pickup-selection.md
index dd170b273..1d693f6e2 100644
--- a/docs/known-issues/pt/shipping-preview-wrongly-reporting-pickup-selection.md
+++ b/docs/known-issues/pt/shipping-preview-wrongly-reporting-pickup-selection.md
@@ -18,9 +18,7 @@ internalReference: 552912
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No carrinho, ao informar sua localização, a visualização da remessa informa erroneamente qual pickup foi selecionado para esta pickup. Quando de fato, duas opções de coleta devem ser exibidas (houve uma quebra de pacote neste exemplo). E ao chegar na caixa, a informação é fornecida corretamente, com as retiradas nas respectivas pick-ups corretas.
diff --git a/docs/known-issues/pt/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md b/docs/known-issues/pt/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md
index 6eb803f80..09d422c5a 100644
--- a/docs/known-issues/pt/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md
+++ b/docs/known-issues/pt/shipping-preview-wrongly-showing-unavailability-message-for-pickup.md
@@ -18,9 +18,7 @@ internalReference: 764457
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você adiciona a "selectedSla" (deve ser uma pick-up) e "selectedAddresses" via API em um carrinho com promoção de presentes, a loja é configurada para geolocalização e usa polígonos, a pré-visualização do envio mostrará uma mensagem de indisponibilidade para a pick-up, que foi selecionada via API. Este comportamento terá impacto no fluxo de compra, uma vez que não permitirá avançar após o envio.
diff --git a/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md b/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md
index be9f7d74f..67e76bdc9 100644
--- a/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md
+++ b/docs/known-issues/pt/shipping-previews-postal-code-input-field-is-not-hidden.md
@@ -18,9 +18,7 @@ internalReference: 821984
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns países, o campo de entrada do código postal da visualização do envio não fica oculto após a inclusão de um código postal válido pela segunda vez.
diff --git a/docs/known-issues/pt/shipping-promotion-does-not-generate-highlights-flags.md b/docs/known-issues/pt/shipping-promotion-does-not-generate-highlights-flags.md
index a25a3199f..b9ab2b345 100644
--- a/docs/known-issues/pt/shipping-promotion-does-not-generate-highlights-flags.md
+++ b/docs/known-issues/pt/shipping-promotion-does-not-generate-highlights-flags.md
@@ -18,9 +18,7 @@ internalReference: 527111
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Porcentagens de remessa, remessa máxima, remessa gratuita e promoções de presentes não estão gerando destaque / bandeiras nos PDPs e PLPs.
diff --git a/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md b/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
index 6c9af3ee4..8321f9e28 100644
--- a/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
+++ b/docs/known-issues/pt/shipping-promotions-applying-in-different-slas-causing-divergence-in-tax-hub.md
@@ -18,9 +18,7 @@ internalReference: 916423
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando as promoções de frete se aplicam a diferentes SLAs, sendo um deles o frete grátis, isso causa divergência na solicitação enviada pelo Tax Hub, impedindo que o pedido seja feito.
diff --git a/docs/known-issues/pt/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md b/docs/known-issues/pt/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md
index 0968b7af9..08b58803d 100644
--- a/docs/known-issues/pt/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md
+++ b/docs/known-issues/pt/shipping-step-may-display-an-unavailability-message-while-the-shipping-options-are-being-calculated.md
@@ -18,9 +18,7 @@ internalReference: 650038
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um usuário que salvou endereço em seu perfil, ao chegar na etapa de endereço onde a seleção de envio é exibida, ao selecionar outra opção um aviso de "Entrega não está disponível para este endereço" é mostrado erroneamente, pode aparecer rapidamente devido ao carregamento de informações, isso pode acontecer de acordo com o atraso nesta busca, dependendo da complexidade da loja.
diff --git a/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md b/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
index ee6aae0ff..a353ac5ff 100644
--- a/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
+++ b/docs/known-issues/pt/shipping-step-with-postal-code-does-not-work-for-some-countries-united-arab-emirates.md
@@ -18,9 +18,7 @@ internalReference: 312132
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 ## **Resumo**
 
diff --git a/docs/known-issues/pt/shopee-could-not-create-product.md b/docs/known-issues/pt/shopee-could-not-create-product.md
index a90d91a69..1f2dff46f 100644
--- a/docs/known-issues/pt/shopee-could-not-create-product.md
+++ b/docs/known-issues/pt/shopee-could-not-create-product.md
@@ -18,9 +18,7 @@ internalReference: 685149
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/shopee-failed-to-create-product-variations.md b/docs/known-issues/pt/shopee-failed-to-create-product-variations.md
index b1e6c9bbc..42fd297a5 100644
--- a/docs/known-issues/pt/shopee-failed-to-create-product-variations.md
+++ b/docs/known-issues/pt/shopee-failed-to-create-product-variations.md
@@ -18,9 +18,7 @@ internalReference: 685160
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md b/docs/known-issues/pt/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md
index 84464d8c7..4d2095202 100644
--- a/docs/known-issues/pt/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md
+++ b/docs/known-issues/pt/shopee-sku-disabled-in-marketplace-shopeeskuhelper-sku-update-failed.md
@@ -18,9 +18,7 @@ internalReference: 685137
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md b/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md
index 38ac75d3a..f5927b7d3 100644
--- a/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md
+++ b/docs/known-issues/pt/similar-products-ui-brokes-with-too-many-products.md
@@ -18,9 +18,7 @@ internalReference: 868425
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md b/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
index 65d331550..fd4e0edc7 100644
--- a/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
+++ b/docs/known-issues/pt/simulation-is-not-possible-find-products-from-catalog-v2-on-shipping-simulation-page.md
@@ -18,9 +18,7 @@ internalReference: 488362
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um problema ao usar o módulo de Simulação de Produtos do Catálogo V2 para encontrar Produtos no módulo de Simulação.
diff --git a/docs/known-issues/pt/simultaneous-sending-of-information-generates-data-loss-in-the-api.md b/docs/known-issues/pt/simultaneous-sending-of-information-generates-data-loss-in-the-api.md
index 78db751f1..f7ce6af2b 100644
--- a/docs/known-issues/pt/simultaneous-sending-of-information-generates-data-loss-in-the-api.md
+++ b/docs/known-issues/pt/simultaneous-sending-of-information-generates-data-loss-in-the-api.md
@@ -18,19 +18,13 @@ internalReference: 280390
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-checkout.md b/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-checkout.md
index 165f8e9a0..42a75076f 100644
--- a/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-checkout.md
+++ b/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 605568
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao registrar uma condição de pagamento em que há apenas uma parcela, esta informação não aparece no checkout.
diff --git a/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md b/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md
index 030737d1f..54c0df0ed 100644
--- a/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md
+++ b/docs/known-issues/pt/single-installment-payment-condition-does-not-appear-at-chekout.md
@@ -18,9 +18,7 @@ internalReference: 605568
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao configurar uma única condição de pagamento com apenas uma opção de parcelamento ou várias condições de pagamento em que apenas uma opção de parcelamento está disponível para um carrinho específico, essa opção de parcelamento não é exibida no checkout. Embora seja exibida corretamente em `paymentData`, ela não é visível para o usuário. Em vez disso, apenas a opção de pagar o valor total é exibida. Entretanto, quando a transação é concluída, o pagamento é processado com a opção de parcelamento correta.
diff --git a/docs/known-issues/pt/single-sku-with-multiple-ean-in-merchant-center.md b/docs/known-issues/pt/single-sku-with-multiple-ean-in-merchant-center.md
index 01db2fd24..0276defb5 100644
--- a/docs/known-issues/pt/single-sku-with-multiple-ean-in-merchant-center.md
+++ b/docs/known-issues/pt/single-sku-with-multiple-ean-in-merchant-center.md
@@ -18,9 +18,7 @@ internalReference: 520345
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Confirmar como estamos enviando a propriedade EAN quando o produto tiver vários skus do mesmo produto no catálogo VTEX.
diff --git a/docs/known-issues/pt/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md b/docs/known-issues/pt/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md
index fa17fe5a8..680eba35a 100644
--- a/docs/known-issues/pt/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md
+++ b/docs/known-issues/pt/site-editor-content-set-to-apply-to-specific-categories-isnt-displayed-if-the-category-is-not-accessed-using-its-direct-link.md
@@ -18,9 +18,7 @@ internalReference: 371994
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md b/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md
index 04fd9697b..0f35d7853 100644
--- a/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md
+++ b/docs/known-issues/pt/site-editor-doesnt-allow-changes-on-the-conditional-template.md
@@ -18,9 +18,7 @@ internalReference: 861920
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um modelo é definido como condicional, não é possível fazer alterações nele por meio do editor do site.
diff --git a/docs/known-issues/pt/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md b/docs/known-issues/pt/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md
index 45b9e7603..9867dccf0 100644
--- a/docs/known-issues/pt/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md
+++ b/docs/known-issues/pt/site-editor-doesnt-load-blocks-when-accessing-the-landing-route-url.md
@@ -18,9 +18,7 @@ internalReference: 755993
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se você tentar acessar uma página no editor do site usando a página de desembarque, ela não carrega os blocos, ela permanece com carga infinita. Por exemplo `https://.myvtex.com/admin/cms/site-editor/.`
diff --git a/docs/known-issues/pt/site-editor-has-intermittent-rendering-issues-in-small-screen.md b/docs/known-issues/pt/site-editor-has-intermittent-rendering-issues-in-small-screen.md
index 8c5c22f40..df5607bf4 100644
--- a/docs/known-issues/pt/site-editor-has-intermittent-rendering-issues-in-small-screen.md
+++ b/docs/known-issues/pt/site-editor-has-intermittent-rendering-issues-in-small-screen.md
@@ -18,9 +18,7 @@ internalReference: 399339
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O editor do site tem problemas intermitentes de renderização em telas menores que 1366px de largura.
diff --git a/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md b/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
index bacc88945..ad9cd8876 100644
--- a/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
+++ b/docs/known-issues/pt/site-rendering-desktop-version-when-accessing-via-ipad-on-safari.md
@@ -18,9 +18,7 @@ internalReference: 735208
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md b/docs/known-issues/pt/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md
index d81afedfe..ea78a25c4 100644
--- a/docs/known-issues/pt/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md
+++ b/docs/known-issues/pt/sitemap-from-subaccounts-including-products-from-other-subaccounts-and-mainaccount.md
@@ -18,9 +18,7 @@ internalReference: 617974
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O mapa do site gerado está mostrando todos os produtos das subcontas e contas, não levando em consideração o canal de vendas dos produtos e se a subconta tem um site próprio.
diff --git a/docs/known-issues/pt/sitemap-isnt-being-generated.md b/docs/known-issues/pt/sitemap-isnt-being-generated.md
index 11f874630..42a7ce5e9 100644
--- a/docs/known-issues/pt/sitemap-isnt-being-generated.md
+++ b/docs/known-issues/pt/sitemap-isnt-being-generated.md
@@ -18,9 +18,7 @@ internalReference: 827104
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há dois cenários em que o mapa do site não está sendo gerado:
diff --git a/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md b/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md
index 639c77ebe..dad09fc80 100644
--- a/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md
+++ b/docs/known-issues/pt/sitemap-isnt-being-generatedupdated.md
@@ -18,9 +18,7 @@ internalReference: 827104
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/size-of-content-files-can-cause-problems-in-site-editor-features.md b/docs/known-issues/pt/size-of-content-files-can-cause-problems-in-site-editor-features.md
index 9d682705a..cc8f6357f 100644
--- a/docs/known-issues/pt/size-of-content-files-can-cause-problems-in-site-editor-features.md
+++ b/docs/known-issues/pt/size-of-content-files-can-cause-problems-in-site-editor-features.md
@@ -18,9 +18,7 @@ internalReference: 715480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Cada atualização de conteúdo ou estrutura em um tema de loja é registrada em arquivos chamados `content.json` e `template.json`, esses arquivos funcionam como "mapas" que mantêm as referências de todo o conteúdo que a vitrine mostra, portanto, é também baseada no que é exibido como uma prévia no Editor do Site.
diff --git a/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md b/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
index 9495f7459..c5af7024b 100644
--- a/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
+++ b/docs/known-issues/pt/sku-admin-breaks-when-sending-a-reference-code-longer-than-50-characters.md
@@ -18,9 +18,7 @@ internalReference: 884789
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que o usuário possa alterar o código de referência do SKU usando o administrador. No entanto, quando um valor maior que 50 caracteres é passado, o administrador falha, exibindo uma mensagem de "algo deu errado".
diff --git a/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md b/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
index 5e97ef51c..62ba41ae4 100644
--- a/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
+++ b/docs/known-issues/pt/sku-denied-on-received-skus-after-throttling-on-marketplace-catalog.md
@@ -18,9 +18,7 @@ internalReference: 970208
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao aprovar um novo produto em Skus recebidos (automática ou manualmente), o módulo de sugestões se comunica com o catálogo do Marketplace para executar a ação.
diff --git a/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md b/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md
index 35499d943..faf6170c3 100644
--- a/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md
+++ b/docs/known-issues/pt/sku-file-update-does-not-update-v-version-tags.md
@@ -18,9 +18,7 @@ internalReference: 852869
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, quando um arquivo de imagem SKU é atualizado por meio da API para ficar na mesma posição de um arquivo anterior, sua tag de versão (?v=) na página do produto não é atualizada corretamente.
diff --git a/docs/known-issues/pt/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md b/docs/known-issues/pt/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md
index b4c8a9408..2c1d240f9 100644
--- a/docs/known-issues/pt/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md
+++ b/docs/known-issues/pt/sku-inactive-updates-on-b2w-but-doesnt-log-correct-message-on-bridge.md
@@ -18,9 +18,7 @@ internalReference: 603761
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Sku inativo, atualizações na B2W mas não registra a mensagem correta na ponte
diff --git a/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md b/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
index 3e6337bc9..3f6f54277 100644
--- a/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
+++ b/docs/known-issues/pt/sku-insert-file-api-is-not-responding-with-the-text-property.md
@@ -18,9 +18,7 @@ internalReference: 1014787
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a API para criar um arquivo sku https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file não está respondendo corretamente à propriedade "Text".
diff --git a/docs/known-issues/pt/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md b/docs/known-issues/pt/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md
index 23cfc9139..db183fa6c 100644
--- a/docs/known-issues/pt/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md
+++ b/docs/known-issues/pt/sku-kit-weight-differs-between-shipping-simulation-and-registration-admin.md
@@ -18,19 +18,13 @@ internalReference: 389784
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md b/docs/known-issues/pt/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md
index 65f0d4fec..6da611f91 100644
--- a/docs/known-issues/pt/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md
+++ b/docs/known-issues/pt/sku-ordering-in-the-search-api-does-not-follow-the-sku-position-of-the-admin.md
@@ -18,9 +18,7 @@ internalReference: 515042
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a resposta da API de pesquisa não respeita o posicionamento de SKUs dentro do produto em Admin. Na resposta, as SKUs estão sendo classificadas em ordem ascendente de SkuId.
diff --git a/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md b/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
index 8200a2678..437802214 100644
--- a/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
+++ b/docs/known-issues/pt/sku-removed-from-amazon-sc-is-not-being-disable-in-amazon-portal.md
@@ -18,9 +18,7 @@ internalReference: 827760
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md b/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md
index 4382c8bf2..c873dfadc 100644
--- a/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md
+++ b/docs/known-issues/pt/sku-selector-display-mode-select-not-working-in-shelfs.md
@@ -18,9 +18,7 @@ internalReference: 682152
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você escolhe e diferente opção sku no modo de exibição SELECT em vez da opção padrão, ela apenas mostra "escolha e opção" em vez de marcar aquela que você escolher. Este comportamento só acontece em prateleiras no Firefox.
diff --git a/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md b/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
index a81f630d3..69d58a94c 100644
--- a/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
+++ b/docs/known-issues/pt/sku-selector-not-choosing-correct-sku-when-having-similar-variations-with-substrings.md
@@ -18,9 +18,7 @@ internalReference: 1047992
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando houver uma substring da variação na SKU escolhida em outra variação disponível, talvez não selecionemos a SKU escolhida
diff --git a/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md b/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md
index e4c25cac2..3bf51a43c 100644
--- a/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md
+++ b/docs/known-issues/pt/sku-selector-with-multilpe-contexts.md
@@ -18,9 +18,7 @@ internalReference: 341322
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md b/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
index 017a550d3..b60bdba44 100644
--- a/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
+++ b/docs/known-issues/pt/sku-specification-filters-arent-loaded-when-the-sku-is-only-available-in-a-whitelabel-seller.md
@@ -18,9 +18,7 @@ internalReference: 431888
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Desde uma atualização recente no comportamento da busca, os filtros de especificação das SKUs não disponíveis não são mostrados nas páginas de resultados de busca.
diff --git a/docs/known-issues/pt/sku-variations-doesnt-return-in-the-plp.md b/docs/known-issues/pt/sku-variations-doesnt-return-in-the-plp.md
index a1797d729..af208b531 100644
--- a/docs/known-issues/pt/sku-variations-doesnt-return-in-the-plp.md
+++ b/docs/known-issues/pt/sku-variations-doesnt-return-in-the-plp.md
@@ -18,9 +18,7 @@ internalReference: 569563
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A apresentação das variações da SKU no PLP é limitada às variações disponíveis, independentemente da configuração do prumo skusFilter. De acordo com nossa análise, o search-graphql não está fornecendo todas as variações conforme o retorno API, portanto o ProductContextProvider não recebe todas as variações.
diff --git a/docs/known-issues/pt/skus-expiring-in-merchant-center.md b/docs/known-issues/pt/skus-expiring-in-merchant-center.md
index 73132e8db..2c239e1b5 100644
--- a/docs/known-issues/pt/skus-expiring-in-merchant-center.md
+++ b/docs/known-issues/pt/skus-expiring-in-merchant-center.md
@@ -18,9 +18,7 @@ internalReference: 548044
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
index e00faa6b1..88003e332 100644
--- a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-accounts-with-autoapprove-flag-enabled.md
@@ -18,9 +18,7 @@ internalReference: 467112
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O vendedor envia um lote com skus do mesmo produto (todas as variações possíveis do produto).
diff --git a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
index 86dd4ee83..3f9d631de 100644
--- a/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
+++ b/docs/known-issues/pt/skus-from-the-same-product-being-created-separately-on-accounts-with-autoapprove-flag-enabled.md
@@ -18,9 +18,7 @@ internalReference: 962986
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O vendedor envia um lote com skus do mesmo produto (todas as variações possíveis do produto).
diff --git a/docs/known-issues/pt/skus-sent-by-sellers-are-created-with-images-out-of-order.md b/docs/known-issues/pt/skus-sent-by-sellers-are-created-with-images-out-of-order.md
index 77d08bb15..0f4fcf4e6 100644
--- a/docs/known-issues/pt/skus-sent-by-sellers-are-created-with-images-out-of-order.md
+++ b/docs/known-issues/pt/skus-sent-by-sellers-are-created-with-images-out-of-order.md
@@ -18,9 +18,7 @@ internalReference: 648349
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o sku é enviado por um vendedor e aprovado no módulo Skus Recebido, as imagens do novo sku no catálogo do mercado estão fora do pedido enviado pelo vendedor.
diff --git a/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md b/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
index 300f4d006..062cbc6fa 100644
--- a/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
+++ b/docs/known-issues/pt/skuservicoformaspx-not-listing-value-tables-at-first-for-a-value-type.md
@@ -18,9 +18,7 @@ internalReference: 335819
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Ao associar um serviço para uma SKU no nosso catálogo, para uma loja que tem múltiplos tipos de serviço e valores de serviço (campo Tipo de Valor), no início, quando um utilizador entra na UI, a lista de opções para um dado "Tipo de Serviço" está atualmente apenas a listar as opções associadas na tabela de Valores do primeiro tipo de serviço selecionado.
 
diff --git a/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md b/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
index a0e8955e3..dbe2ee92c 100644
--- a/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
+++ b/docs/known-issues/pt/sla-offer-fluctuating-between-different-shipping-policies-due-to-cache-in-estimated-date-of-30-seconds.md
@@ -18,9 +18,7 @@ internalReference: 1036916
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A simulação de logística pode oscilar entre a oferta de SLAs se o cliente tiver políticas de remessa com o mesmo preço, tempo de entrega, SlaType, custo de doca e configuração de armazém, mas prioridade de doca diferente.
diff --git a/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md b/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
index fce85ba37..d702b0926 100644
--- a/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
+++ b/docs/known-issues/pt/sliderlayout-bug-when-using-prop-infinite-as-always-on-mobile.md
@@ -18,9 +18,7 @@ internalReference: 920725
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o layout do controle deslizante é definido como `infinito: "sempre"` no celular, o componente apresenta um bug intermitente. Após algum tempo de rolagem da prateleira, os produtos param de aparecer e, em vez disso, aparece um espaço em branco.
diff --git a/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md b/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
index bc7f192b7..94f14c1aa 100644
--- a/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
+++ b/docs/known-issues/pt/slug-and-link-returned-in-the-catalog-facets-api-have-different-formats.md
@@ -18,9 +18,7 @@ internalReference: 998397
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 API do Catalog Facets descrita aqui: https://developers.vtex.com/docs/api-reference/search-api#get-/api/catalog_system/pub/facets/search/-term-
diff --git a/docs/known-issues/pt/sms-configuration-in-message-centre-module-returns-an-error.md b/docs/known-issues/pt/sms-configuration-in-message-centre-module-returns-an-error.md
index b86cbbc9c..572a97854 100644
--- a/docs/known-issues/pt/sms-configuration-in-message-centre-module-returns-an-error.md
+++ b/docs/known-issues/pt/sms-configuration-in-message-centre-module-returns-an-error.md
@@ -22,9 +22,7 @@ Ao configurar o envio de SMS pelo módulo de Central de mensagens, a UI devolve
 
 ## Simulação
 
-<div class="alert alert-info">
-É necessario ter a APP da movile instalada para simular o erro.
-</div>
+>ℹ️ É necessario ter a APP da movile instalada para simular o erro.
  
  1. Entrar no modulo de Central de mensagens; 
  2. Selecionar a opção MOVILE SMS;
diff --git a/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md b/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
index 96b042ebd..c862eed3d 100644
--- a/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
+++ b/docs/known-issues/pt/sms-configuration-link-in-email-template-redirects-user-to-404-page.md
@@ -18,9 +18,7 @@ internalReference: 1054007
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na tela de configuração do modelo do sistema do centro de mensagens, há um link que deve levar o usuário à configuração do aplicativo de envio de SMS, mas esse aplicativo não está mais disponível e o link agora retorna 404, exibindo uma tela com a mensagem "`store/not-found-box-title`".
diff --git a/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md b/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
index e7fbdb55b..72d39012d 100644
--- a/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
+++ b/docs/known-issues/pt/some-addresses-autocompleted-by-google-are-not-able-to-be-saved-on-my-account.md
@@ -18,9 +18,7 @@ internalReference: 415388
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns endereços retornados do campo de pesquisa do Google não estão sendo salvos quando adicionados por meio do fluxo Minha conta, e a interface do usuário não retorna nenhum feedback para o usuário.
diff --git a/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md b/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
index be097469c..95fc4cb6c 100644
--- a/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
+++ b/docs/known-issues/pt/some-functions-of-the-sticky-layout-component-wont-work-as-expected-when-viewed-through-safari-browser.md
@@ -18,9 +18,7 @@ internalReference: 868535
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas funções do componente sticky layout não funcionam como esperado quando visualizadas no navegador Safari
diff --git a/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md b/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
index 0af72c231..3038c0f84 100644
--- a/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
+++ b/docs/known-issues/pt/some-inventory-management-features-not-working-properly-on-seller-portal-accounts.md
@@ -18,9 +18,7 @@ internalReference: 1001665
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os recursos de gerenciamento de estoque (como os links para os produtos) não se comportam como esperado nas contas do portal do vendedor. Isso acontece porque esse tipo de conta usa uma versão diferente do catálogo.
diff --git a/docs/known-issues/pt/some-promotions-cant-be-displayed-in-search-context.md b/docs/known-issues/pt/some-promotions-cant-be-displayed-in-search-context.md
index a04e79f68..250bfaabe 100644
--- a/docs/known-issues/pt/some-promotions-cant-be-displayed-in-search-context.md
+++ b/docs/known-issues/pt/some-promotions-cant-be-displayed-in-search-context.md
@@ -18,9 +18,7 @@ internalReference: 475289
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns tipos de promoções não são recuperados no contexto do ProductSummaryProvider e, portanto, seus crachás não são entregues pelo componente vtex.product-highlights.
diff --git a/docs/known-issues/pt/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md b/docs/known-issues/pt/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md
index 961ea1e33..c15544081 100644
--- a/docs/known-issues/pt/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md
+++ b/docs/known-issues/pt/some-skus-are-not-being-uploaded-to-the-facebook-catalog.md
@@ -18,9 +18,7 @@ internalReference: 558926
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/some-skus-dont-integrate-dafiti.md b/docs/known-issues/pt/some-skus-dont-integrate-dafiti.md
index 34e011616..9e5d4ddbd 100644
--- a/docs/known-issues/pt/some-skus-dont-integrate-dafiti.md
+++ b/docs/known-issues/pt/some-skus-dont-integrate-dafiti.md
@@ -18,9 +18,7 @@ internalReference: 655574
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md b/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
index 72e8ea63a..f17eefcd6 100644
--- a/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
+++ b/docs/known-issues/pt/some-special-characters-are-not-stripped-from-product-searches-or-indexing.md
@@ -18,9 +18,7 @@ internalReference: 382382
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns caracteres especiais não são completamente removidos das palavras-chave pesquisadas ou da indexação de produtos, o que pode afetar as pesquisas em alguns cenários específicos.
diff --git a/docs/known-issues/pt/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md b/docs/known-issues/pt/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md
index eec2e32c3..95cfd2f47 100644
--- a/docs/known-issues/pt/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md
+++ b/docs/known-issues/pt/some-specs-are-not-displayed-in-admin-but-are-visible-via-api.md
@@ -18,9 +18,7 @@ internalReference: 418348
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas especificações não são exibidas no Admin, mas são visíveis via API.
diff --git a/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md b/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md
index b775b08b9..6b08a1dec 100644
--- a/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md
+++ b/docs/known-issues/pt/some-unexpected-behavior-in-masterdata.md
@@ -18,9 +18,7 @@ internalReference: 669048
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Mesmo com dados disponíveis (documentos), as informações não são retornadas como esperado.
diff --git a/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md b/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
index c89dbdde0..25b72821b 100644
--- a/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
+++ b/docs/known-issues/pt/something-went-wrong-error-is-displayed-in-the-catalog-admin.md
@@ -18,9 +18,7 @@ internalReference: 907567
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que o administrador seja usado sem restrições. No entanto, às vezes um erro **Algo deu errado** é exibido no administrador do catálogo.
diff --git a/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md b/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
index d4b39e756..b5ea03234 100644
--- a/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
+++ b/docs/known-issues/pt/something-went-wrong-message-when-accessing-a-and-p-routes-in-portal-stores.md
@@ -18,9 +18,7 @@ internalReference: 945226
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Espera-se que seja possível pesquisar qualquer termo nas lojas do Portal; no entanto, as letras "A" e "P" não são diretamente pesquisáveis por meio da URL.
diff --git a/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md b/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
index c491780b4..eb271e37c 100644
--- a/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
+++ b/docs/known-issues/pt/something-went-wrong-when-adding-an-incomplete-address-and-tried-to-edit-it.md
@@ -18,9 +18,7 @@ internalReference: 960064
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Durante a etapa de checkout, usando um comprador com um perfil completo, na etapa de preenchimento dos dados de envio, clicando na opção "Entregar em outro endereço", se apenas o código postal for adicionado e o comprador voltar à lista de endereços (usando o botão "voltar ao catálogo de endereços") e clicar em "Atualizar informações de endereço selecionadas", haverá um erro com a mensagem "Algo deu errado".
diff --git a/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md b/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md
index a47935adf..c74280430 100644
--- a/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md
+++ b/docs/known-issues/pt/sort-by-name-working-different-on-stores-integrated-before-a-date.md
@@ -18,9 +18,7 @@ internalReference: 600468
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a classificação pelo nome no PLP de uma loja pode ter comportamentos diferentes com palavras com letras maiúsculas e minúsculas e isto acontece devido a um normalizador que é realizado nas lojas para trabalhar as letras todas como minúsculas e a classificação não considera camelo ou palavras maiúsculas.
diff --git a/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md b/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
index 0c382c80a..3953aa627 100644
--- a/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
+++ b/docs/known-issues/pt/space-in-street-property-in-postal-code-json-affects-address-field-display-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 872935
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao ativar o uso da API de código postal no formulário de endereço para países que não estão no modelo BR (país, estado, cidade, bairro, rua), esses países que não têm todos esses campos preenchidos na API e precisam ser capazes de inserir os outros dados de endereço no formulário de endereço no checkout, o campo rua do bloco de endereço não estará disponível se a propriedade rua do JSON estiver com espaço, pois será entendido como preenchido e válido, o que não permite prosseguir com o pedido.
diff --git a/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md b/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
index 6c7bf652e..2d729fd08 100644
--- a/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
+++ b/docs/known-issues/pt/space-in-warehouse-id-causes-internal-logistics-requests-to-fail.md
@@ -18,9 +18,7 @@ internalReference: 654370
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A IU de logística permite que um usuário crie um depósito registrando uma identificação com espaço e isto afeta diretamente as solicitações feitas a este depósito e pode causar falhas na atualização do estoque.
diff --git a/docs/known-issues/pt/special-character-in-seller-name-report.md b/docs/known-issues/pt/special-character-in-seller-name-report.md
index 9686a0c32..a90648e4e 100644
--- a/docs/known-issues/pt/special-character-in-seller-name-report.md
+++ b/docs/known-issues/pt/special-character-in-seller-name-report.md
@@ -18,9 +18,7 @@ internalReference: 756243
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Especificamente para o caráter especial ":", quando temos um vendedor com este caráter especial no nome, e tentamos filtrá-lo para a elaboração de relatórios, temos o seguinte quando o vemos em "devtools":
diff --git a/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md b/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
index d41d06ac8..0cf92dac8 100644
--- a/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
+++ b/docs/known-issues/pt/special-characters-cannot-be-used-for-cnpj-search-on-masterdata.md
@@ -18,9 +18,7 @@ internalReference: 602054
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os tipos de campo CNPJ e CPF são utilizados entre várias partes da VTEX e são campos essenciais presentes também na entidade MasterData CL.
diff --git a/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md b/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
index 4a04812ee..306245f35 100644
--- a/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
+++ b/docs/known-issues/pt/special-characters-in-invoicenumber-cause-postpurchase-flow-to-fail.md
@@ -18,9 +18,7 @@ internalReference: 953285
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o SNO (Shipping Notification Order) aceita que um número de fatura (invoiceNumber) seja enviado via API e UI com um "caractere especial" no final ou no início dos dados, por exemplo: "#123456".
diff --git a/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md b/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
index eb91ad3da..fb93ae4be 100644
--- a/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
+++ b/docs/known-issues/pt/special-characters-on-the-sku-name-breaks-sku-selection-on-portal-web-store-pdp-pages-for-radio-box-category-type-of-selection.md
@@ -18,9 +18,7 @@ internalReference: 337933
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Caracteres especiais no nome da SKU quebra a seleção da SKU nas páginas PDP do Portal Web Store para caixa de rádio Tipo de seleção de categoria, por exemplo, caracteres como `%`.
diff --git a/docs/known-issues/pt/specification-field-delete-button-not-functional.md b/docs/known-issues/pt/specification-field-delete-button-not-functional.md
index 50d1a0d48..d4f21e900 100644
--- a/docs/known-issues/pt/specification-field-delete-button-not-functional.md
+++ b/docs/known-issues/pt/specification-field-delete-button-not-functional.md
@@ -18,9 +18,7 @@ internalReference: 328943
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na página de campos de especificação, nosso administrador legado tem um botão "remover" que não funciona, esta ação não está disponível para a loja.
diff --git a/docs/known-issues/pt/specification-value-ordering-is-not-saved.md b/docs/known-issues/pt/specification-value-ordering-is-not-saved.md
index 2d6dd477a..d8a8869c9 100644
--- a/docs/known-issues/pt/specification-value-ordering-is-not-saved.md
+++ b/docs/known-issues/pt/specification-value-ordering-is-not-saved.md
@@ -18,9 +18,7 @@ internalReference: 584182
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Não é possível alterar a ordem dos valores de especificação para contas com um grande volume de valores. Quando a ordem de algum valor é alterada, a página é recarregada e a alteração não é salva.
diff --git a/docs/known-issues/pt/specifications-multiplied-on-catalog.md b/docs/known-issues/pt/specifications-multiplied-on-catalog.md
index 52ed98e3c..2631b4488 100644
--- a/docs/known-issues/pt/specifications-multiplied-on-catalog.md
+++ b/docs/known-issues/pt/specifications-multiplied-on-catalog.md
@@ -18,9 +18,7 @@ internalReference: 919761
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O marketplace pode aprovar produtos enviados por vendedores no módulo Received Skus.
diff --git a/docs/known-issues/pt/split-items-order-with-value-as-0-zero-on-the-invoice.md b/docs/known-issues/pt/split-items-order-with-value-as-0-zero-on-the-invoice.md
index 5bd36d03e..d6a474839 100644
--- a/docs/known-issues/pt/split-items-order-with-value-as-0-zero-on-the-invoice.md
+++ b/docs/known-issues/pt/split-items-order-with-value-as-0-zero-on-the-invoice.md
@@ -18,19 +18,13 @@ internalReference: 387933
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/split-package-suggestion-not-working-properly.md b/docs/known-issues/pt/split-package-suggestion-not-working-properly.md
index bd3a3850b..201c1d5c5 100644
--- a/docs/known-issues/pt/split-package-suggestion-not-working-properly.md
+++ b/docs/known-issues/pt/split-package-suggestion-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 656810
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A sugestão do pacote dividido não está funcionando corretamente, quando você termina a compra a IU sugere os pacotes divididos em casos de docas diferentes ou tamanhos diferentes e estratégias de embarque diferentes.
diff --git a/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md b/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
index d9fccf72c..21154a8f8 100644
--- a/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
+++ b/docs/known-issues/pt/spotprice-from-the-skujson-is-incorrect-for-products-with-multiple-sellers.md
@@ -18,9 +18,7 @@ internalReference: 264791
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Valor do "spotPrice" (preço à vista) no "skuJson" do Portal incorreto em produtos com múltiplos vendedores.
diff --git a/docs/known-issues/pt/state-registration-is-not-filled-after-approving-the-organization-request.md b/docs/known-issues/pt/state-registration-is-not-filled-after-approving-the-organization-request.md
index 46a058fbf..040adc786 100644
--- a/docs/known-issues/pt/state-registration-is-not-filled-after-approving-the-organization-request.md
+++ b/docs/known-issues/pt/state-registration-is-not-filled-after-approving-the-organization-request.md
@@ -18,9 +18,7 @@ internalReference: 825127
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O campo Registro de Estado não é preenchido após a aprovação da Solicitação de Organização no administrador.
diff --git a/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md b/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md
index 871388301..6be3b8383 100644
--- a/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md
+++ b/docs/known-issues/pt/status-erro-de-processamento-shipping-policy.md
@@ -18,9 +18,7 @@ internalReference: 445793
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há um cenário relativo ao status da Política de Embarque após a criação/atualização dos valores de frete API. O status ainda pendente como "Erro no processamento" em caso de criação sem planilha de cálculo.
diff --git a/docs/known-issues/pt/status-in-the-order-list-is-different-from-the-current-order-status.md b/docs/known-issues/pt/status-in-the-order-list-is-different-from-the-current-order-status.md
index 8c70732ae..97e3d3d55 100644
--- a/docs/known-issues/pt/status-in-the-order-list-is-different-from-the-current-order-status.md
+++ b/docs/known-issues/pt/status-in-the-order-list-is-different-from-the-current-order-status.md
@@ -18,9 +18,7 @@ internalReference: 577103
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns casos, a lista de pedidos mostra um status diferente do status do pedido atual (cartão).
diff --git a/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md b/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md
index 466a9ec2b..82ba67f66 100644
--- a/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md
+++ b/docs/known-issues/pt/status-on-transactions-list-doesnt-match-actual-state.md
@@ -18,9 +18,7 @@ internalReference: 1004883
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas transações podem não corresponder ao estado real quando você as abre (problema de indexação).
diff --git a/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md b/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md
index 398fb47ea..e2a92283e 100644
--- a/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md
+++ b/docs/known-issues/pt/stock-change-is-completed-even-after-receiving-error-500.md
@@ -18,9 +18,7 @@ internalReference: 388176
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O cliente está tentando atualizar a quantidade de sku no inventário e a solicitação recebeu o erro 500. Apesar do erro, a quantidade em estoque é alterada.
diff --git a/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md b/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
index 2b4ed48a5..235dc4ad4 100644
--- a/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
+++ b/docs/known-issues/pt/stockkeepingunit-catalog-api-allows-invalid-commercial-condition-values.md
@@ -18,9 +18,7 @@ internalReference: 769053
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a unidade de estocagem API https://catalog.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit/{skuid} não realiza nenhuma verificação para o campo "CommercialConditionId".
diff --git a/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md b/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
index 317445303..532408b14 100644
--- a/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
+++ b/docs/known-issues/pt/stockkeepingunitbyean-returns-404-for-eans-with-.md
@@ -18,19 +18,13 @@ internalReference: 479244
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md b/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
index 1381f6cda..53ff18e03 100644
--- a/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
+++ b/docs/known-issues/pt/stockkeepingunitinsertupdate-webservice-method-allows-to-insert-existent-refid.md
@@ -18,9 +18,7 @@ internalReference: 419460
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Hoje não somos capazes de inserir/atualizar um RefId já registrado para outro SKU usando API REST, o upload de planilhas ou Administração de Catálogo, mas usando o WebService podemos inserir um RefId existente.
diff --git a/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md b/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md
index 5457fdc74..13b21be76 100644
--- a/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md
+++ b/docs/known-issues/pt/storefront-permissions-app-sets-documenttype-as-cpf.md
@@ -18,9 +18,7 @@ internalReference: 798330
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O aplicativo de permissões do storefront sempre define o campo "clientProfileData.documentType" como "cpf" no formulário de pedido. Isso pode fazer com que a transação seja negada pelo provedor.
diff --git a/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md b/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md
index ebe7fd8a3..70cd0ff24 100644
--- a/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md
+++ b/docs/known-issues/pt/storefront-permissions-considers-inactive-organizations.md
@@ -18,9 +18,7 @@ internalReference: 927174
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um usuário tem mais de uma organização atribuída a ele e a primeira registrada está inativa, ela não é reconhecida como uma organização atribuída após o login.
diff --git a/docs/known-issues/pt/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md b/docs/known-issues/pt/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md
index 84b7059e2..b808af090 100644
--- a/docs/known-issues/pt/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md
+++ b/docs/known-issues/pt/street-neighborhood-complement-and-reference-fields-are-not-requested-in-the-address-step-at-checkout.md
@@ -18,9 +18,7 @@ internalReference: 563507
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o endereço é inserido através do código postal API e estes dados são atualizados nos dados de envio antes de chegar ao checkout. Se nosso API postal não retornar todos os dados completos, por exemplo, rua, bairro, etc. Eles estarão faltando nos dados de envio. O problema é que quando o cliente usa o componente de geolocalização em seu checkout, ele não executa a validação que falta nestes campos, deixando o usuário para ir para a etapa de pagamento sem preencher os dados que não estão completos.
diff --git a/docs/known-issues/pt/stucked-not-found-routes-on-platform.md b/docs/known-issues/pt/stucked-not-found-routes-on-platform.md
index 2ab1b3b49..6680b7d3d 100644
--- a/docs/known-issues/pt/stucked-not-found-routes-on-platform.md
+++ b/docs/known-issues/pt/stucked-not-found-routes-on-platform.md
@@ -18,9 +18,7 @@ internalReference: 793457
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido à falta de notificações e a problemas de cache, algumas rotas são armazenadas em cache como não encontradas no vbase e no rewriter pelo store-indexer, afetando a experiência quando essas rotas estão disponíveis novamente, sendo necessário enviar uma nova indexação e novas notificações ou aguardar o tempo do store-indexer para acionar a nova indexação novamente
diff --git a/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md b/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md
index b7c8ea467..014857664 100644
--- a/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md
+++ b/docs/known-issues/pt/subscribers-report-does-not-show-active-subscriptions-correctly.md
@@ -18,9 +18,7 @@ internalReference: 587556
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando exportamos o relatório de assinantes, as informações nas colunas "TotalSubscrições" e "TotalSubscriçõesAtivos" são divergentes em comparação com as informações mostradas no painel de controle.
diff --git a/docs/known-issues/pt/subscription-event-history-out-of-order.md b/docs/known-issues/pt/subscription-event-history-out-of-order.md
index 6a34dfbe4..cf0ae3169 100644
--- a/docs/known-issues/pt/subscription-event-history-out-of-order.md
+++ b/docs/known-issues/pt/subscription-event-history-out-of-order.md
@@ -18,9 +18,7 @@ internalReference: 872697
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, o Histórico de assinatura na área Minha assinatura não exibe os eventos em uma ordem predefinida, portanto, pode mostrar os eventos em ordem não cronológica;
diff --git a/docs/known-issues/pt/subscription-options-translations-dont-work-properly-for-some-languages.md b/docs/known-issues/pt/subscription-options-translations-dont-work-properly-for-some-languages.md
index 939e92977..77fba0313 100644
--- a/docs/known-issues/pt/subscription-options-translations-dont-work-properly-for-some-languages.md
+++ b/docs/known-issues/pt/subscription-options-translations-dont-work-properly-for-some-languages.md
@@ -18,9 +18,7 @@ internalReference: 561186
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No carrinho, os períodos de assinatura estão errados na IU. Mas, se você olhar para o formulário de pedido, o período está mostrando corretamente.
diff --git a/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md b/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
index 88ab92d0a..43b61f81e 100644
--- a/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
+++ b/docs/known-issues/pt/subscription-plan-is-stuck-in-importing-after-uploading-the-skus-association-spreadsheet.md
@@ -18,9 +18,7 @@ internalReference: 571080
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md b/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md
index 5a7559964..dd005f0c4 100644
--- a/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md
+++ b/docs/known-issues/pt/subscriptions-dashboard-with-conflicting-information.md
@@ -18,9 +18,7 @@ internalReference: 587579
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md b/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
index 95cd2a824..402aa2fe8 100644
--- a/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
+++ b/docs/known-issues/pt/subscriptions-not-executed-due-to-data-indexing-failure-or-masterdata-query-failure.md
@@ -18,9 +18,7 @@ internalReference: 961526
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A criação de solicitações de assinatura depende do retorno de uma consulta feita ao banco de dados de assinaturas; essa consulta é feita periodicamente para identificar quais assinaturas devem ser executadas naquele período; se essa consulta falhar ou não retornar uma assinatura específica, seu ciclo não será executado e nenhum erro será registrado, resultando, assim, em uma assinatura com a nextPurchaseDate no passado.
diff --git a/docs/known-issues/pt/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md b/docs/known-issues/pt/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md
index cef199afb..87b6ced9d 100644
--- a/docs/known-issues/pt/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md
+++ b/docs/known-issues/pt/subscriptions-orders-can-not-be-created-once-the-sku-has-linked-to-a-gift-unavailable.md
@@ -18,9 +18,7 @@ internalReference: 395965
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Há uma condição em que os Pedidos de Assinatura não podem ser criados porque estão vinculados a um **presente indisponível**, mesmo que os itens de uma assinatura estejam disponíveis.
diff --git a/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md b/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
index 19d22b4d1..d3bb1c3c5 100644
--- a/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
+++ b/docs/known-issues/pt/subscriptions-simulation-returned-error-when-pickuppointid-contains-special-characters.md
@@ -18,9 +18,7 @@ internalReference: 903332
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para realizar um pedido de assinatura ou atualizar uma assinatura, o sistema de assinatura realiza uma simulação e, nessa simulação, utiliza os dados de entrega retornados pelo sistema de logística e, se nesses dados houver um ponto de coleta cujo ID esteja sublinhado, o sistema de assinatura não conseguirá escolher o SLA corretamente, gerando o erro "Invalid AddressProvider:...." na simulação e, consequentemente, não gerará o pedido.
diff --git a/docs/known-issues/pt/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md b/docs/known-issues/pt/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md
index 5ddd58bd0..69d31cada 100644
--- a/docs/known-issues/pt/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md
+++ b/docs/known-issues/pt/subscriptions-when-the-seller-is-a-pickup-point-and-does-not-have-one-of-the-skus.md
@@ -18,9 +18,7 @@ internalReference: 666701
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md b/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md
index ee859291c..7c9e655bb 100644
--- a/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md
+++ b/docs/known-issues/pt/substitute-words-with-less-than-3-characters-does-not-work.md
@@ -18,9 +18,7 @@ internalReference: 282500
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Palavras substitutas com menos de 3 caracteres não funcionam
diff --git a/docs/known-issues/pt/suggestions-transforming-unitmultiplier-less-than-1-to-0.md b/docs/known-issues/pt/suggestions-transforming-unitmultiplier-less-than-1-to-0.md
index f53ed21e7..869d66ce9 100644
--- a/docs/known-issues/pt/suggestions-transforming-unitmultiplier-less-than-1-to-0.md
+++ b/docs/known-issues/pt/suggestions-transforming-unitmultiplier-less-than-1-to-0.md
@@ -18,9 +18,7 @@ internalReference: 702056
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md b/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
index 92881fa7f..bd17f366c 100644
--- a/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
+++ b/docs/known-issues/pt/summary-information-translate-into-english-after-logging-in-via-update-selected-address-information.md
@@ -18,9 +18,7 @@ internalReference: 978571
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nas contas em espanhol, fazer login no checkout por meio de "Atualizar informações de endereço selecionadas" após a identificação com um perfil completo faz com que alguns textos do resumo sejam traduzidos para o inglês.
diff --git a/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md b/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
index fca50c734..dbdf7db34 100644
--- a/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
+++ b/docs/known-issues/pt/swiping-productimage-after-zooming-in-does-not-revert-the-zoom-causing-display-issues.md
@@ -18,9 +18,7 @@ internalReference: 491180
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o vtex.store-components product-image, ao deslizar uma imagem para o lado depois de clicar nela para aumentar o zoom, a primeira imagem continuará ampliada, causando problemas de renderização quando o usuário deslizar de volta para ela.
diff --git a/docs/known-issues/pt/sww-on-the-pages-with-collections-or-categories.md b/docs/known-issues/pt/sww-on-the-pages-with-collections-or-categories.md
index 547b3c99f..733654ca7 100644
--- a/docs/known-issues/pt/sww-on-the-pages-with-collections-or-categories.md
+++ b/docs/known-issues/pt/sww-on-the-pages-with-collections-or-categories.md
@@ -18,9 +18,7 @@ internalReference: 785324
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, quando carregamos uma categoria ou coleção, seja por parte da visualização ou da própria página de coleção/categoria, um erro SWW é exibido em toda a página.
diff --git a/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md b/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md
index ca6d8201a..c6d3c92b6 100644
--- a/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md
+++ b/docs/known-issues/pt/synonyms-import-presenting-success-even-for-failed-actions.md
@@ -18,9 +18,7 @@ internalReference: 984557
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A importação de sinônimos para arquivos CSV retornará uma mensagem de sucesso mesmo para ações que falharam.
diff --git a/docs/known-issues/pt/synonyms-not-reflecting-on-the-explained-search.md b/docs/known-issues/pt/synonyms-not-reflecting-on-the-explained-search.md
index 4b6e4b2a7..67c79cc2c 100644
--- a/docs/known-issues/pt/synonyms-not-reflecting-on-the-explained-search.md
+++ b/docs/known-issues/pt/synonyms-not-reflecting-on-the-explained-search.md
@@ -18,9 +18,7 @@ internalReference: 774307
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Tínhamos um cenário onde um produto, mesmo com um sinônimo aplicado a ele, não aparece na tela da Pesquisa Explicada. Isto geralmente acontece com sinônimos unidirecionais.
diff --git a/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md b/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md
index 4843a6d2d..26258dbad 100644
--- a/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md
+++ b/docs/known-issues/pt/synonyms-not-shown-in-the-explained-search.md
@@ -18,9 +18,7 @@ internalReference: 774307
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns produtos podem não apresentar seus sinônimos na página de administração da pesquisa explicada. Isso geralmente acontece com sinônimos unidirecionais.
diff --git a/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md b/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md
index a980b4f4e..56524be16 100644
--- a/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md
+++ b/docs/known-issues/pt/system-considering-seller-1-for-rule-sellers-limit.md
@@ -18,9 +18,7 @@ internalReference: 564614
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Hoje, em um cenário onde temos uma conta que usa uma arquitetura no modelo MOI (marketplace/multilevel seller), o sistema considera o vendedor 1 como parte do cálculo para limitar o número de vendedores no carrinho que pode ser configurado usando a chave maxNumberOfWhiteLabelSellers
diff --git a/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md b/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md
index c497f8ea5..5fea36186 100644
--- a/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md
+++ b/docs/known-issues/pt/tags-wont-sometimes-appear-on-list-format-plp-view.md
@@ -18,9 +18,7 @@ internalReference: 982200
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao exibir o PLP na visualização de lista, as tags dos itens.
diff --git a/docs/known-issues/pt/tax-apportionment-divergence.md b/docs/known-issues/pt/tax-apportionment-divergence.md
index 4b1da18ba..16286506a 100644
--- a/docs/known-issues/pt/tax-apportionment-divergence.md
+++ b/docs/known-issues/pt/tax-apportionment-divergence.md
@@ -18,9 +18,7 @@ internalReference: 561466
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O rateio de um valor fiscal feito pelo módulo Promoções considera decimais, resultando em um imposto de valor total diferente do conjunto.
diff --git a/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md b/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
index bd67a8865..806f9da9f 100644
--- a/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
+++ b/docs/known-issues/pt/tax-form-ui-is-not-displayng-marketing-tags-dropdown.md
@@ -18,9 +18,7 @@ internalReference: 1058148
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao salvar impostos no módulo de promoções, o valor do menu suspenso para "pelo menos um dos seguintes" ou "todos os seguintes" não é mostrado depois que o imposto é salvo. Consequentemente, o usuário não consegue descobrir qual deles está sendo usado.
diff --git a/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md b/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
index 6cf1117f1..bf9583b9c 100644
--- a/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
+++ b/docs/known-issues/pt/tax-hub-request-doesnt-sum-discounts-when-manual-price-is-applied.md
@@ -18,9 +18,7 @@ internalReference: 932667
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md b/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
index b83e31172..c62145ec3 100644
--- a/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
+++ b/docs/known-issues/pt/tax-service-consider-the-same-price-for-items-that-appear-more-than-once-when-using-assembly-option.md
@@ -18,9 +18,7 @@ internalReference: 906518
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar Opções de montagem, se o item for adicionado novamente ao carrinho, ele aparecerá duas vezes e o Serviço de impostos considerará apenas o preço do item que está primeiro no carrinho, causando divergência de valores de impostos ao fazer um pedido.
diff --git a/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md b/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
index 060c9fd16..d5d7a52a3 100644
--- a/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
+++ b/docs/known-issues/pt/tax-service-doesnt-apply-free-shipping-promotions-with-promotion-that-splits-items.md
@@ -18,9 +18,7 @@ internalReference: 995527
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o serviço de impostos, se houver uma promoção que divida os itens, por exemplo, uma promoção "Mais por menos" e uma promoção de frete grátis, o frete grátis não é aplicado corretamente para todos os itens na solicitação do serviço de impostos, causando um cálculo errado e evitando que o pedido seja criado com a mensagem "O pedido solicitado não pôde ser criado. Please try again."
diff --git a/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md b/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
index cd84d7c50..6cdf740d9 100644
--- a/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
+++ b/docs/known-issues/pt/tax-service-doesnt-consider-nominal-promotions-when-placing-orders.md
@@ -18,9 +18,7 @@ internalReference: 900120
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o serviço de impostos, se houver uma promoção nominal aplicada no carrinho e ocorrer uma divisão de item, o checkout da solicitação não terá a promoção nominal aplicada, não permitindo concluir a compra, e a mensagem "O pedido solicitado não pôde ser criado. Please try again" será exibida.
diff --git a/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md b/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
index 5fedc29d7..79768203e 100644
--- a/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
+++ b/docs/known-issues/pt/tax-service-request-uses-shippingdataaddress-even-when-a-cart-has-two-selected-address.md
@@ -18,9 +18,7 @@ internalReference: 1074168
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um carrinho com itens para retirada e entrega, a simulação do checkout considera apenas as informações do objeto shippingData.address para a solicitação do serviço de imposto. Por exemplo, considerando que esses endereços são de estados diferentes e que o provedor de impostos considera impostos diferentes para cada estado, um dos itens terá o imposto errado aplicado.
diff --git a/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md b/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md
index 560b58101..ea9292f7a 100644
--- a/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md
+++ b/docs/known-issues/pt/tax-service-uses-document-data-instead-of-customer-email.md
@@ -18,9 +18,7 @@ internalReference: 548671
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md b/docs/known-issues/pt/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md
index 24af82f46..f91c5b518 100644
--- a/docs/known-issues/pt/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md
+++ b/docs/known-issues/pt/telesales-app-not-working-properly-with-requiresauthenticationtoloadprofile.md
@@ -18,9 +18,7 @@ internalReference: 797651
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o sinalizador RequiresAuthenticationToLoadProfile das APIs de checkout com um aplicativo de televendas para personificar usuários, não está sendo acionado nenhum tipo de feedback para o usuário se a personificação foi feita com sucesso e causa algumas inconsistências no fluxo
diff --git a/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md b/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
index f589a6c34..0a8891867 100644
--- a/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
+++ b/docs/known-issues/pt/telesales-search-doesnt-accept-special-characters-aside-from.md
@@ -18,9 +18,7 @@ internalReference: 1072418
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, ao usar a caixa de pesquisa de televendas, um usuário pode se passar por comprador para ajudar nas compras e, para isso, é necessário inserir, na caixa de pesquisa nativa, o e-mail de quem será representado.
diff --git a/docs/known-issues/pt/term-makes-search-api-have-no-return.md b/docs/known-issues/pt/term-makes-search-api-have-no-return.md
index 2694cb659..3101bf1fe 100644
--- a/docs/known-issues/pt/term-makes-search-api-have-no-return.md
+++ b/docs/known-issues/pt/term-makes-search-api-have-no-return.md
@@ -18,9 +18,7 @@ internalReference: 570542
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Algumas palavras são ignoradas pela busca, no caso de "é", o termo deve ser convertido para "e" e depois ignorado pela busca. Mas uma busca com esse termo retornará uma busca vazia.
diff --git a/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md b/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
index 88fb295d4..e35cf0cf2 100644
--- a/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
+++ b/docs/known-issues/pt/text-in-add-to-cart-button-are-not-being-translated-using-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 1026103
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar traduzir um texto usando o editor do site para o botão Adicionar ao carrinho, as alterações não são aplicadas na frente da loja.
diff --git a/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md b/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md
index 5d1e56212..20fab354b 100644
--- a/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md
+++ b/docs/known-issues/pt/text-in-infocard-is-not-being-translated-using-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 1049491
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar traduzir um texto usando o editor do site para o componente do cartão de informações, as alterações não são aplicadas na frente da loja.
diff --git a/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md b/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md
index f1fc39598..47c0792d7 100644
--- a/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md
+++ b/docs/known-issues/pt/text-in-store-login-are-not-being-translated-using-site-editor.md
@@ -18,9 +18,7 @@ internalReference: 911757
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar traduzir um texto usando o editor do site para o login da loja, as alterações não serão aplicadas na frente da loja.
diff --git a/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md b/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
index e54910959..aff4025ab 100644
--- a/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
+++ b/docs/known-issues/pt/textlink-created-with-on-marketplace-upon-approvals-reoccurence.md
@@ -18,9 +18,7 @@ internalReference: 795900
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em alguns cenários, ao aprovar um produto em um Marketplace, no aplicativo Received SKUs, a solicitação falha ao inserir dados no catálogo e, ao tentar novamente, os campos de link de texto preenchem os caracteres "-" com " ", alterando o comportamento desejado.
diff --git a/docs/known-issues/pt/textlink-created-with-special-character.md b/docs/known-issues/pt/textlink-created-with-special-character.md
index fc04f1aa8..9f68c93a9 100644
--- a/docs/known-issues/pt/textlink-created-with-special-character.md
+++ b/docs/known-issues/pt/textlink-created-with-special-character.md
@@ -18,9 +18,7 @@ internalReference: 537159
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um produto tem caracteres especiais específicos no nome, tais como ®, o `textlink` é criado com esse caracter na URL.
diff --git a/docs/known-issues/pt/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md b/docs/known-issues/pt/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md
index 21e78aa45..a047abbf6 100644
--- a/docs/known-issues/pt/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md
+++ b/docs/known-issues/pt/the-api-to-createupdate-gift-card-providers-is-always-updating-the-current-provider-when-it-has-never-added-a-new-provider-before.md
@@ -18,9 +18,7 @@ internalReference: 768954
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar adicionar uma nova identificação de fornecedor pela primeira vez em uma conta, em vez de adicionar um novo fornecedor, o atual fornecedor nativo (VtexGiftCard) é atualizado.
diff --git a/docs/known-issues/pt/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md b/docs/known-issues/pt/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md
index f30e7a66d..68d2c4429 100644
--- a/docs/known-issues/pt/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md
+++ b/docs/known-issues/pt/the-apply-to-the-theme-feature-doesnt-work-on-the-site-editor-with-custom-pages.md
@@ -18,9 +18,7 @@ internalReference: 580543
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md b/docs/known-issues/pt/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md
index ac5b440b4..56b7fa528 100644
--- a/docs/known-issues/pt/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md
+++ b/docs/known-issues/pt/the-cardui-generates-an-error-when-the-user-chooses-to-pay-with-two-cards-changes-the-payment-method-and-returns-to-the-payment-with-two-cards.md
@@ -18,9 +18,7 @@ internalReference: 670424
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o usuário escolhe pagar com dois cartões, então muda o método de pagamento e volta a pagar com dois cartões, a mensagem "_Error inesperado"_ aparecerá na caixa de opção de pagamento._ _ _
diff --git a/docs/known-issues/pt/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md b/docs/known-issues/pt/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md
index 21b8c9e8c..02540923e 100644
--- a/docs/known-issues/pt/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md
+++ b/docs/known-issues/pt/the-changes-made-to-custom-payments-are-not-reflected-in-checkout.md
@@ -18,9 +18,7 @@ internalReference: 276250
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cliente tenta modificar as configurações feitas para pagamentos personalizados que já têm uma regra de pagamento associada, as mudanças não são refletidas no checkout.
diff --git a/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md b/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
index 4ab743156..a9346afe7 100644
--- a/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
+++ b/docs/known-issues/pt/the-cielo-3ds2-app-is-returning-an-approved-status-even-in-scenarios-when-the-authentication-has-failed.md
@@ -18,9 +18,7 @@ internalReference: 820060
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Hoje, nosso aplicativo cielo-authentication-app v1.2.1 está retornando um status "aprovado" na etapa final do fluxo ao chamar a etapa de autorização que avalia se a autenticação falhou ou não. No entanto, o aplicativo só aciona a etapa de falha quando há um erro lançado nessa etapa. Como resultado, mesmo que o status seja "failed" na etapa anterior, mas não haja nenhum erro lançado na etapa /authorize atual, o status ainda é considerado "approved" (aprovado), o que nos permite fazer uma solicitação ao adquirente. Esse não é o comportamento esperado, pois deveríamos estar negando a autorização de pagamento e alterando a transação para "autorização negada" nesse cenário.
diff --git a/docs/known-issues/pt/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md b/docs/known-issues/pt/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md
index 51cc377e3..6a18545f3 100644
--- a/docs/known-issues/pt/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md
+++ b/docs/known-issues/pt/the-clearsale-antifraud-connector-is-sending-the-wrong-cart-items-in-cases-where-two-or-more-items-share-the-same-name.md
@@ -18,9 +18,7 @@ internalReference: 799396
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O conector antifraude do ClearSale usa o nome do item como uma condição ao percorrer o mini carrinho enviado pelo checkout. Nos casos em que dois ou mais itens compartilham o mesmo nome, mesmo que tenham SKUs diferentes, apenas um desses itens é enviado ao sistema antifraude. O valor da transação para os itens restantes é enviado como frete.
diff --git a/docs/known-issues/pt/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md b/docs/known-issues/pt/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md
index e8fe1a879..15fe4c51a 100644
--- a/docs/known-issues/pt/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md
+++ b/docs/known-issues/pt/the-clustered-payment-conditions-app-is-causing-sync-problems-of-payment-rules.md
@@ -18,9 +18,7 @@ internalReference: 391569
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O aplicativo Clustered Payment Conditions App está causando problemas de sincronização das regras de pagamento e resulta no desaparecimento do método de pagamento do checkout. o recurso está em Beta Fechada e não foi instalado em novas contas. Mais detalhes na página **Enable Clustered Payment Conditions em sua loja***.
diff --git a/docs/known-issues/pt/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md b/docs/known-issues/pt/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md
index 7069a4464..2804f0a5f 100644
--- a/docs/known-issues/pt/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md
+++ b/docs/known-issues/pt/the-crmmasterdata-ui-is-not-deleting-documents-even-with-the-success-message.md
@@ -18,9 +18,7 @@ internalReference: 699374
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A IU CRM não está apagando documentos, embora a mensagem de sucesso seja mostrada.
diff --git a/docs/known-issues/pt/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md b/docs/known-issues/pt/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md
index 8e9b80ff9..e502fe38a 100644
--- a/docs/known-issues/pt/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md
+++ b/docs/known-issues/pt/the-current-gift-card-systems-transaction-route-returns-a-200-ok-status-code-when-adding-or-removing-credits-even-if-the-card-is-inactive.md
@@ -18,9 +18,7 @@ internalReference: 795997
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, nosso sistema de cartão-presente não inclui uma verificação para verificar se um cartão-presente está ativo antes de adicionar ou remover créditos. Embora essa rota se refira apenas à realização de transações com cartão-presente, é a única maneira de fazê-lo, portanto, espera-se que alguma validação seja feita.
diff --git a/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md b/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
index 06f0bbbfc..628485ded 100644
--- a/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
+++ b/docs/known-issues/pt/the-delivery-split-will-not-be-displayed-in-the-ui-or-in-my-orders-when-the-order-has-the-same-shipping-method.md
@@ -18,9 +18,7 @@ internalReference: 495352
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A sugestão do pacote dividido não está funcionando corretamente, quando você termina a compra a IU sugere os pacotes divididos em casos de docas diferentes ou tamanhos diferentes e estratégias de embarque diferentes.
diff --git a/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md b/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
index 9f59369d6..315a2837a 100644
--- a/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
+++ b/docs/known-issues/pt/the-field-judet-county-is-not-showing-as-saved-when-address-editing-on-romania-my-account.md
@@ -18,9 +18,7 @@ internalReference: 394658
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para lojas da Romênia, na página _**My Account**_, há um campo chamado "Judet", município em inglês, que não está sendo exibido como salvo ao editar o endereço.
diff --git a/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md b/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
index 57c6ee253..00ddec441 100644
--- a/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
+++ b/docs/known-issues/pt/the-holiday-is-not-shown-in-the-list-after-using-the-api-to-create-put.md
@@ -18,9 +18,7 @@ internalReference: 571040
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md b/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
index b1df82bd4..571eff46d 100644
--- a/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
+++ b/docs/known-issues/pt/the-installments-request-at-the-gateway-to-a-merchant-other-than-the-marketplace-is-always-done-with-saleschannel-1.md
@@ -18,9 +18,7 @@ internalReference: 391197
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os pedidos para obter parcelas externas na porta de entrada de um comerciante que não seja o mercado são sempre feitos com canal de vendas = 1.
diff --git a/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md b/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
index f40d9c019..4337b06da 100644
--- a/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
+++ b/docs/known-issues/pt/the-issuing-bank-special-condition-is-causing-for-some-bins-the-error-on-checkout-page-issuer-bank-for-this-bank-is-not-accepted.md
@@ -18,9 +18,7 @@ internalReference: 391549
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Usando as condições especiais no método de pagamento para filtrar o emissor está fazendo com que o caixa exiba um erro "Banco emissor não é aceito". O problema é intermitente e foi notado pela primeira vez ao utilizar o cartão de Co-branded de Pagamento Personalizado, mas também aconteceu no Método de Pagamento com Cartão de Crédito.
diff --git a/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md b/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
index dda20dae0..0336d267c 100644
--- a/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
+++ b/docs/known-issues/pt/the-legacy-adyen-connector-is-unable-of-asynchronously-denying-payment-capture.md
@@ -18,9 +18,7 @@ internalReference: 976005
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O conector antigo da Adyen captura o pagamento sempre que recebe o campo `"response":"[capture-received]"`. No entanto, esse evento indica apenas que a captura foi recebida e será processada de forma assíncrona. Esse comportamento evita que as capturas sejam negadas, pois a notificação assíncrona encontra um pagamento já capturado e não o reembolsa.
diff --git a/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
index e95947f3a..23b20e9f3 100644
--- a/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
+++ b/docs/known-issues/pt/the-mercadopagov1-and-v2-integration-does-not-work-with-save-card-functionality.md
@@ -18,9 +18,7 @@ internalReference: 283727
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A integração do MercadoPagoV1 e do MercadoPagoV2 não funciona corretamente com a funcionalidade de salvar cartão na seção "Minha conta" para países que não permitem transações com decimais.
diff --git a/docs/known-issues/pt/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md b/docs/known-issues/pt/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md
index d2c0ef20e..f16af39aa 100644
--- a/docs/known-issues/pt/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md
+++ b/docs/known-issues/pt/the-mercadopagov1-integration-does-not-work-with-save-card-functionality.md
@@ -18,9 +18,7 @@ internalReference: 283727
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A integração MercadoPagoV1 não funciona com a funcionalidade salvar cartão na seção Minha conta.
diff --git a/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md b/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
index 7788727c2..2a5130eef 100644
--- a/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
+++ b/docs/known-issues/pt/the-message-my-billing-address-is-on-the-credit-card-iframe-is-in-the-wrong-language-when-using-checkout-in-catalan-language.md
@@ -18,9 +18,7 @@ internalReference: 481181
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A mensagem "Meu endereço de cobrança é ..." no iFrame do cartão de crédito está no idioma errado ao usar o checkout no idioma catalão.
diff --git a/docs/known-issues/pt/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md b/docs/known-issues/pt/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md
index 7d19682ce..10c9cfa0c 100644
--- a/docs/known-issues/pt/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md
+++ b/docs/known-issues/pt/the-order-management-filter-does-not-find-results-for-criteria-that-have-double-spaces-in-the-name.md
@@ -18,9 +18,7 @@ internalReference: 353656
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md b/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
index c8c3db30c..80d106a4e 100644
--- a/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
+++ b/docs/known-issues/pt/the-payu-connector-is-unable-to-process-payments-when-there-is-shipping-data-containing-more-than-40-characters.md
@@ -18,9 +18,7 @@ internalReference: 902539
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O conector da PayU não trata os dados de endereço recebidos do checkout e os envia ao provedor como estão, sem nenhuma modificação. No entanto, a documentação do provedor afirma que esses dados não devem exceder 40 caracteres.
diff --git a/docs/known-issues/pt/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md b/docs/known-issues/pt/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md
index a6bc509ba..479c45fd9 100644
--- a/docs/known-issues/pt/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md
+++ b/docs/known-issues/pt/the-productimage-component-doesnt-update-its-images-based-on-sku-specifications-change.md
@@ -18,9 +18,7 @@ internalReference: 669619
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md b/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
index 808ce9a62..4bee0d8a6 100644
--- a/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
+++ b/docs/known-issues/pt/the-purchase-button-stays-active-even-with-insufficient-credit-of-payment-method-customer-credit.md
@@ -18,9 +18,7 @@ internalReference: 309820
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O botão de compra permanece ativo mesmo com crédito insuficiente no crédito do cliente.
diff --git a/docs/known-issues/pt/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md b/docs/known-issues/pt/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md
index 1ac7f8524..b1c28f6c1 100644
--- a/docs/known-issues/pt/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md
+++ b/docs/known-issues/pt/the-saml-solution-doesnt-allow-sending-the-samlrequest-as-query-string-in-the-crm-login.md
@@ -18,9 +18,7 @@ internalReference: 789146
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns provedores SAML precisam receber parâmetros como string de consulta, mas nossa solução SAML não permite o envio desses parâmetros (como parâmetros SAMLRequest e SAMLResponse) como string de consulta no login do CRM porque o sistema CRM usa uma versão do sistema de login, que não suporta esse recurso.
diff --git a/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md b/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
index 04c977d23..27eba12ed 100644
--- a/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
+++ b/docs/known-issues/pt/the-save-new-card-option-does-not-work-for-asynchronous-payment-providers.md
@@ -18,9 +18,7 @@ internalReference: 308892
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cliente tenta adicionar um novo cartão na seção Minha conta de lojas cujas afiliações não retornam uma resposta síncrona, o sistema retorna _ocorreu um erro ao tentar registrar o cartão_ e uma cobrança indevida de R$ 1,50 pode ser gerada.
diff --git a/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md b/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
index 0a8e5e864..3de0831f7 100644
--- a/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
+++ b/docs/known-issues/pt/the-scroll-api-returns-429-andor-408-errors-when-querying-entities-with-a-large-number-of-documents-typically-exceeding-millions.md
@@ -18,9 +18,7 @@ internalReference: 1035873
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API Scroll foi projetada para lidar com grandes conjuntos de dados, permitindo a recuperação de documentos de forma rolável. No entanto, ao consultar entidades com um número significativo de documentos, normalmente na casa dos milhões, os usuários podem encontrar erros 429 (Too Many Requests) e/ou 408 (Request Timeout). Esses erros ocorrem devido ao alto volume de dados que estão sendo processados, o que pode sobrecarregar a API e resultar em limitação da taxa de solicitações ou timeouts.
diff --git a/docs/known-issues/pt/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md b/docs/known-issues/pt/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md
index af766e7e0..5f100ba7c 100644
--- a/docs/known-issues/pt/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md
+++ b/docs/known-issues/pt/the-search-route-of-the-gift-card-system-intermittently-does-not-return-vouchers-when-the-restrange-header-is-less-than-10.md
@@ -18,9 +18,7 @@ internalReference: 770337
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um cenário onde o cliente tem comprovantes de fidelidade e chega à caixa, espera-se que a rota /_search devolva todos os comprovantes vinculados a esse usuário. Entretanto, o checkout passa o cabeçalho com a faixa de REST = 0-9. Em algumas contas, esta faixa não é suficiente e a API retorna uma matriz vazia. Quando simulamos a chamada diretamente à API com um intervalo maior que 10, podemos recuperar pelo menos um comprovante.
diff --git a/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md b/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
index 4635b3d5a..7623c987e 100644
--- a/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
+++ b/docs/known-issues/pt/the-system-does-not-allow-multiple-cancellation-with-giftcard.md
@@ -18,9 +18,7 @@ internalReference: 309117
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O sistema não está enviando o cancelamento parcial de uma transação de Giftcard.
diff --git a/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md b/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
index 52723e642..6e4e8112a 100644
--- a/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
+++ b/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for-debit-online-method.md
@@ -18,9 +18,7 @@ internalReference: 319750
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O sistema não funciona com mais de uma filiação de pagamento de extensão
diff --git a/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md b/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md
index 46200e2a3..8fc88b8e7 100644
--- a/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md
+++ b/docs/known-issues/pt/the-system-doesnt-work-with-more-than-one-extension-payment-affiliation-for.md
@@ -18,19 +18,13 @@ internalReference: 319750
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md b/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
index 5f77ee787..738185709 100644
--- a/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
+++ b/docs/known-issues/pt/the-template-relatoriodeimportacaodeestoque-does-not-support-multilanguage.md
@@ -18,9 +18,7 @@ internalReference: 585906
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a mensagem de retorno do relatório de importação do inventário está em _pt-BR_. Assim, quando a importação é concluída, o e-mail acionado através do modelo "relatorio-de-importacao-de-estoque" tem as informações em _pt-BR_, não considerando o local da loja.
diff --git a/docs/known-issues/pt/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md b/docs/known-issues/pt/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md
index 6da5d6c4c..a7d323a86 100644
--- a/docs/known-issues/pt/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md
+++ b/docs/known-issues/pt/the-transaction-ui-currently-has-a-limitation-where-it-cannot-display-logs-from-interactions-if-the-payload-exceeds-5000-lines.md
@@ -18,9 +18,7 @@ internalReference: 778408
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a API /interações só pode recuperar um máximo de 5000 linhas do arquivo S3 onde todos os dados são armazenados. Isto pode criar um problema quando uma transação gera logs que excedem este limite.
diff --git a/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md b/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
index 83cbffc73..453b6690c 100644
--- a/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
+++ b/docs/known-issues/pt/the-user-cannot-make-a-daily-subscription-directly-from-the-mysubscriptions-area.md
@@ -18,9 +18,7 @@ internalReference: 430650
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O usuário logado não pode fazer uma assinatura diária diretamente da guia Assinatura na Minha Conta. O botão parece não responder, e não aparece nenhuma mensagem de erro. Parece que outras freqüências, tais como assinaturas mensais ou anuais, estão operando normalmente.
diff --git a/docs/known-issues/pt/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md b/docs/known-issues/pt/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md
index 4d62275dd..cee0976d1 100644
--- a/docs/known-issues/pt/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md
+++ b/docs/known-issues/pt/the-validity-of-the-promissory-doesnt-cancel-the-transaction.md
@@ -18,9 +18,7 @@ internalReference: 325491
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se um cliente faz um pedido com as notas a pagar e o pagamento não é feito, a transação não é cancelada pela porta de entrada após a data de vencimento do pagamento. Consequentemente, como a OMS não pode identificar o evento de cancelamento, o pedido não é cancelado.
diff --git a/docs/known-issues/pt/this-is-a-test.md b/docs/known-issues/pt/this-is-a-test.md
index 5d2ca0fbd..05cc497c4 100644
--- a/docs/known-issues/pt/this-is-a-test.md
+++ b/docs/known-issues/pt/this-is-a-test.md
@@ -18,9 +18,7 @@ internalReference: 741722
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Descreva o erro de forma concisa.
diff --git a/docs/known-issues/pt/time-out-at-relatorioindexacaoaspx.md b/docs/known-issues/pt/time-out-at-relatorioindexacaoaspx.md
index ac3d9679f..269f72999 100644
--- a/docs/known-issues/pt/time-out-at-relatorioindexacaoaspx.md
+++ b/docs/known-issues/pt/time-out-at-relatorioindexacaoaspx.md
@@ -18,9 +18,7 @@ internalReference: 547844
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Contas com muitos produtos podem ter um tempo limite na tela do relatório de índice
diff --git a/docs/known-issues/pt/time-out-import-and-export-admin.md b/docs/known-issues/pt/time-out-import-and-export-admin.md
index fd3e93477..47a9ef1a8 100644
--- a/docs/known-issues/pt/time-out-import-and-export-admin.md
+++ b/docs/known-issues/pt/time-out-import-and-export-admin.md
@@ -18,9 +18,7 @@ internalReference: 424902
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Para algumas contas com muitos produtos, o administrador de importação e exportação não é carregado, gerando um tempo limite
diff --git a/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md b/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md
index 4b8da212d..3cd36adb3 100644
--- a/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md
+++ b/docs/known-issues/pt/time-out-on-category-keywords-change-with-many-products.md
@@ -18,9 +18,7 @@ internalReference: 497335
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 Impossível alterar as palavras-chave de uma categoria com muitos produtos, já que um timeout é retornado no processo, seja por admin ou por API
 
diff --git a/docs/known-issues/pt/timeout-api-get-accounts-approval-settings.md b/docs/known-issues/pt/timeout-api-get-accounts-approval-settings.md
index 9243258d2..ff82f8cc2 100644
--- a/docs/known-issues/pt/timeout-api-get-accounts-approval-settings.md
+++ b/docs/known-issues/pt/timeout-api-get-accounts-approval-settings.md
@@ -18,9 +18,7 @@ internalReference: 772840
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/timeout-generating-internal-application-keys.md b/docs/known-issues/pt/timeout-generating-internal-application-keys.md
index 03d4a183f..05b1c86e4 100644
--- a/docs/known-issues/pt/timeout-generating-internal-application-keys.md
+++ b/docs/known-issues/pt/timeout-generating-internal-application-keys.md
@@ -18,9 +18,7 @@ internalReference: 1029425
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md b/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
index 972c3bec8..d5d82a566 100644
--- a/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
+++ b/docs/known-issues/pt/timeout-in-the-query-to-analytics-preventing-to-check-the-inventory-log.md
@@ -18,9 +18,7 @@ internalReference: 984482
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O registro de atualização na interface do usuário do inventário às vezes retorna o erro: A solicitação falhou com o código de status 500 para algumas SKUs específicas, devido a um tempo limite na consulta ao Analytics (onde os dados são armazenados), e nenhum registro para a SKU será mostrado na interface do usuário.
diff --git a/docs/known-issues/pt/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md b/docs/known-issues/pt/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md
index b5010f48c..d9256b313 100644
--- a/docs/known-issues/pt/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md
+++ b/docs/known-issues/pt/top-searches-terms-presented-in-autocomplete-are-not-in-accordance-with-terms-presented-in-the-analytics-report.md
@@ -18,9 +18,7 @@ internalReference: 741999
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os dados apresentados nos relatórios da Intelligent Search Analytics, relacionados aos termos resultantes do autocompletar, não concordam com os termos da Top Search apresentados no autocompletar que estão sendo mostrados ao usuário ao utilizar a barra de busca na frente da loja. De acordo com a finalidade do módulo, os últimos 10 termos apresentados no autocompletar devem ser os mesmos que os termos apresentados no relatório analítico, ao selecionar a opção Autocompletar.
diff --git a/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md b/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md
index 837791954..dd07cc06e 100644
--- a/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md
+++ b/docs/known-issues/pt/total-reservation-item-with-negative-value-in-inventory-ui.md
@@ -18,9 +18,7 @@ internalReference: 991735
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/tracking-error.md b/docs/known-issues/pt/tracking-error.md
index 91a69a299..b5c3f9b92 100644
--- a/docs/known-issues/pt/tracking-error.md
+++ b/docs/known-issues/pt/tracking-error.md
@@ -18,9 +18,7 @@ internalReference: 514557
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O vendedor faturou alguns pedidos, mas as informações de rastreamento não foram enviadas à B2W.
diff --git a/docs/known-issues/pt/trade-policy-api-do-not-generate-reindexing-request.md b/docs/known-issues/pt/trade-policy-api-do-not-generate-reindexing-request.md
index c21764f60..f9d9070b6 100644
--- a/docs/known-issues/pt/trade-policy-api-do-not-generate-reindexing-request.md
+++ b/docs/known-issues/pt/trade-policy-api-do-not-generate-reindexing-request.md
@@ -18,9 +18,7 @@ internalReference: 276511
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Usar a API https://developers.vtex.com/vtex-rest-api/reference/catalog-api-trade-policy para inserir/excluir uma política comercial em um produto ou a API não gera uma solicitação de reindexação.
diff --git a/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md b/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
index cac9b7f42..231138bea 100644
--- a/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
+++ b/docs/known-issues/pt/transaction-canceled-by-timeout-timeout-no-request-para-o-sistema-de-parcelamento.md
@@ -18,9 +18,7 @@ internalReference: 533844
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md b/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
index 61a97d290..60a886837 100644
--- a/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
+++ b/docs/known-issues/pt/transaction-cancellation-error-with-unreachable-code-message.md
@@ -18,9 +18,7 @@ internalReference: 998435
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O cancelamento de uma transação completa pode falhar ao retornar a mensagem `Código inacessível` (visível apenas por meio da API).
diff --git a/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md b/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
index 3cb202874..4e451713c 100644
--- a/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
+++ b/docs/known-issues/pt/transaction-stuck-in-a-status-prior-to-the-state-that-it-should-be.md
@@ -18,9 +18,7 @@ internalReference: 1037765
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O caso mais comum é o de uma transação presa em autorizada quando deveria ser aprovada; nesse cenário, o pedido não pode ser faturado.
diff --git a/docs/known-issues/pt/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md b/docs/known-issues/pt/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md
index b48e15b4f..b619a0e34 100644
--- a/docs/known-issues/pt/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md
+++ b/docs/known-issues/pt/transaction-stuck-in-analyzing-risk-due-to-null-documenttype-field.md
@@ -18,9 +18,7 @@ internalReference: 697107
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As transações estão ficando presas no estágio "Analyzing Risk" porque o campo `documentType` é nulo.
diff --git a/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md b/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
index 6dffe719a..c65299113 100644
--- a/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
+++ b/docs/known-issues/pt/transaction-stuck-in-canceling-when-one-of-the-card-is-denied.md
@@ -18,19 +18,13 @@ internalReference: 429082
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md b/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md
index a18231a34..1974c9f23 100644
--- a/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md
+++ b/docs/known-issues/pt/transaction-stuck-in-status-approved-with-payment-canceled.md
@@ -18,9 +18,7 @@ internalReference: 1046365
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A transação ficou presa no status aprovado, mesmo que o pagamento tenha sido cancelado.
diff --git a/docs/known-issues/pt/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md b/docs/known-issues/pt/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md
index 606b8d455..84a9c2362 100644
--- a/docs/known-issues/pt/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md
+++ b/docs/known-issues/pt/transaction-stuck-on-approved-with-nps-connector-due-to-pspresponsecod-in-settlement-response.md
@@ -18,9 +18,7 @@ internalReference: 557051
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Depois de enviar a solicitação de captura para o conector NPS, recebemos a resposta. No entanto, atualmente, não temos nenhuma ação em vigor para quando o campo `psp_ResponseCod` retorna um valor diferente de 2. Isso faz com que a operação de captura falhe, impedindo que o pagamento seja capturado com êxito.
diff --git a/docs/known-issues/pt/transactions-entered-into-wrong-conditions.md b/docs/known-issues/pt/transactions-entered-into-wrong-conditions.md
index 23c39b44c..65cfa7ed0 100644
--- a/docs/known-issues/pt/transactions-entered-into-wrong-conditions.md
+++ b/docs/known-issues/pt/transactions-entered-into-wrong-conditions.md
@@ -18,9 +18,7 @@ internalReference: 392666
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Transações realizadas em condições erradas, mais abrangentes do que o esperado(configuradas)
diff --git a/docs/known-issues/pt/transactions-made-with-payu-do-not-change-from-cancelling-status.md b/docs/known-issues/pt/transactions-made-with-payu-do-not-change-from-cancelling-status.md
index d6552d8bc..864a60bb1 100644
--- a/docs/known-issues/pt/transactions-made-with-payu-do-not-change-from-cancelling-status.md
+++ b/docs/known-issues/pt/transactions-made-with-payu-do-not-change-from-cancelling-status.md
@@ -18,9 +18,7 @@ internalReference: 338124
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a transação entra em um status de **cancelamento** não é possível reconhecer, portanto não muda para **cancelado***.
diff --git a/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md b/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
index e87107095..448602d75 100644
--- a/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
+++ b/docs/known-issues/pt/transactions-with-konduto-are-taking-longer-than-expected-to-update-status.md
@@ -18,9 +18,7 @@ internalReference: 541149
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As novas tentativas automáticas estão ficando presas em algumas transações que usam o Kondutor como provedor antifraude e demoram mais do que o esperado para chamar uma nova tentativa a fim de alterar seu status. Isso está bloqueando o inventário dos clientes.
diff --git a/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md b/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
index 76cb0a56d..cc153c1d9 100644
--- a/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
+++ b/docs/known-issues/pt/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md
@@ -18,9 +18,7 @@ internalReference: 541687
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O padrão é que eles são cancelados e enviamos dois Pedidos de Autorização 3D, e você ainda não recebeu a resposta do Pedido de Autorização.
diff --git a/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md b/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
index 50b5f6997..bf7fdd9cf 100644
--- a/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
+++ b/docs/known-issues/pt/translation-issues-when-using-a-subaccount-to-implement-multilanguage-stores.md
@@ -18,9 +18,7 @@ internalReference: 848524
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A indexação unificada do catálogo considera as traduções das mensagens apenas da conta principal, mesmo quando se usa uma arquitetura de subconta para implementar armazenamentos internacionais.
diff --git a/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md b/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
index c07b0b6c5..89ec44597 100644
--- a/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
+++ b/docs/known-issues/pt/transliteration-only-being-saved-in-vbase-and-not-into-rewriter.md
@@ -18,9 +18,7 @@ internalReference: 738334
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md b/docs/known-issues/pt/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md
index ce48f3923..719a99886 100644
--- a/docs/known-issues/pt/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md
+++ b/docs/known-issues/pt/ts-not-possible-to-update-a-product-name-and-description-on-centauro.md
@@ -18,9 +18,7 @@ internalReference: 544084
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md b/docs/known-issues/pt/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md
index bbf955719..860dfc8a6 100644
--- a/docs/known-issues/pt/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md
+++ b/docs/known-issues/pt/two-different-workflows-for-the-same-order-resulting-in-status-detailstatenull.md
@@ -18,9 +18,7 @@ internalReference: 680919
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido a uma falha na etapa de criação do fluxo de trabalho, algumas ordens cujo fluxo de criação foi concluído corretamente, podem apresentar o seguinte valor no campo de status: `detail.state.null `e na listagem de ordens não apresentam nenhum valor de status;
diff --git a/docs/known-issues/pt/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md b/docs/known-issues/pt/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md
index c65a4cd43..f50750c93 100644
--- a/docs/known-issues/pt/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md
+++ b/docs/known-issues/pt/ui-automatically-changes-the-selected-sla-when-the-seller-has-scheduled-pickup-and-item-is-not-in-the-first-position.md
@@ -18,9 +18,7 @@ internalReference: 843602
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um carrinho em que há pelo menos dois produtos atendidos por vendedores diferentes, se ambos os vendedores tiverem agendado a retirada e o segundo item tiver várias opções de SLA, a interface do usuário se perde e seleciona automaticamente um SLA diferente e mostra a mensagem "Não há intervalos de tempo disponíveis para esta data.", não permitindo ir para a etapa de pagamento.
diff --git a/docs/known-issues/pt/ui-considers-only-the-available-items-to-calculate-sla.md b/docs/known-issues/pt/ui-considers-only-the-available-items-to-calculate-sla.md
index e45ae0691..de7be5259 100644
--- a/docs/known-issues/pt/ui-considers-only-the-available-items-to-calculate-sla.md
+++ b/docs/known-issues/pt/ui-considers-only-the-available-items-to-calculate-sla.md
@@ -18,9 +18,7 @@ internalReference: 797028
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Etiquetas brancas de vendedores diferentes podem ser selecionadas para atender aos produtos ao usar endereços diferentes para entrega e coleta. Quando a opção de retirada é selecionada e, ao mudar para entrega, a interface do usuário considera apenas os itens disponíveis para calcular o novo SLA para entrega, mesmo que os produtos estejam disponíveis. O preço de entrega considerará apenas os itens selecionados disponíveis para retirada.
diff --git a/docs/known-issues/pt/ui-does-not-reflect-invoice-address-selection-markup.md b/docs/known-issues/pt/ui-does-not-reflect-invoice-address-selection-markup.md
index d8d223f0c..1ebb02cfe 100644
--- a/docs/known-issues/pt/ui-does-not-reflect-invoice-address-selection-markup.md
+++ b/docs/known-issues/pt/ui-does-not-reflect-invoice-address-selection-markup.md
@@ -18,9 +18,7 @@ internalReference: 522946
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md b/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md
index 80572e771..9dbb27d42 100644
--- a/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md
+++ b/docs/known-issues/pt/ui-does-not-update-best-sla-choice-in-cart.md
@@ -18,9 +18,7 @@ internalReference: 550201
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando temos dois SKUs no carrinho cujo SLAID dos itens tem uma interseção, este é o SLA que será oferecido no carrinho com o leanShipping ativo;
diff --git a/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md b/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
index 28a4a62a6..23f81b899 100644
--- a/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
+++ b/docs/known-issues/pt/ui-doesnt-show-delivery-window-selection-for-pickup-points-when-an-item-from-a-seller-is-between-items-for-pickup-from-another-seller.md
@@ -18,9 +18,7 @@ internalReference: 954108
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um carrinho com pelo menos três produtos, onde os pedidos de itens são: O primeiro é para a retirada programada 1, o segundo é para a retirada programada 2 (vendedor diferente) e o terceiro é para a retirada programada 1, a interface do usuário não mostrará as janelas de entrega para selecionar a data/hora da segunda retirada. Isso acontece porque a API agrupará o 1º item e o 3º item, já que se trata do mesmo SLA.
diff --git a/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md b/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
index 5c940ccb1..9a8d2a70d 100644
--- a/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
+++ b/docs/known-issues/pt/ui-doesnt-show-the-form-to-edit-address-when-selecting-to-add-a-new-address-first.md
@@ -18,9 +18,7 @@ internalReference: 747772
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A interface do usuário não mostra o formulário correto para editar o endereço selecionado na etapa de envio ao selecionar a adição de um novo endereço primeiro.
diff --git a/docs/known-issues/pt/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md b/docs/known-issues/pt/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md
index ba0502240..6ebeb7ca9 100644
--- a/docs/known-issues/pt/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md
+++ b/docs/known-issues/pt/ui-duplicating-date-and-time-selection-for-scheduled-delivery-when-it-has-delivery-division.md
@@ -18,9 +18,7 @@ internalReference: 569132
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/ui-fails-to-change-state-between-delivery-and-collection-correctly.md b/docs/known-issues/pt/ui-fails-to-change-state-between-delivery-and-collection-correctly.md
index 93664ad36..e1d47e4b4 100644
--- a/docs/known-issues/pt/ui-fails-to-change-state-between-delivery-and-collection-correctly.md
+++ b/docs/known-issues/pt/ui-fails-to-change-state-between-delivery-and-collection-correctly.md
@@ -18,9 +18,7 @@ internalReference: 526736
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, quando o usuário muda o tipo de entrega entre a entrega e a retirada na caixa (importante estar na caixa e não no carrinho, embora isso provavelmente aconteça também no carrinho), o pedidoFormulário salva o estado de entrega em `logísticaInfo` quando o pickup é selecionado.
diff --git a/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md b/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
index fbeb861fd..401a4c512 100644
--- a/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
+++ b/docs/known-issues/pt/ui-gets-frozen-if-an-error-occurs-in-the-place-order-internal-process.md
@@ -18,9 +18,7 @@ internalReference: 943771
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando ocorre um erro durante o processo interno de colocação de pedido, a interface do usuário fica congelada no carregamento sem nenhuma mensagem de erro/aviso.
diff --git a/docs/known-issues/pt/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md b/docs/known-issues/pt/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md
index 138853b65..e6e1f3e3f 100644
--- a/docs/known-issues/pt/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md
+++ b/docs/known-issues/pt/ui-informs-that-there-is-no-sla-for-address-that-had-previously-available-sla.md
@@ -18,9 +18,7 @@ internalReference: 585249
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o usuário logado chega à fase de envio, com o endereço já pré-selecionado e com o SLA disponível para aquele local, ao editar seu endereço com exatamente as mesmas informações preenchidas anteriormente, a UI informa que não há entrega disponível. Mesmo a resposta API sendo que existe sim SLA disponível (já que é o mesmo endereço).
diff --git a/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md b/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
index fa1919e79..baf08e5ce 100644
--- a/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
+++ b/docs/known-issues/pt/ui-shows-a-pickup-was-selected-in-cart-with-subscriptions-but-it-wasnt-in-api.md
@@ -18,9 +18,7 @@ internalReference: 996976
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As opções de retirada são oferecidas aos compradores em um carrinho com um item com uma assinatura. Quando uma das retiradas é selecionada, o checkout muda automaticamente para entrega, mas a interface do usuário ainda mostra que a retirada foi selecionada.
diff --git a/docs/known-issues/pt/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md b/docs/known-issues/pt/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md
index ccefe2e65..88944c13e 100644
--- a/docs/known-issues/pt/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md
+++ b/docs/known-issues/pt/ui-shows-an-error-when-exporting-catalog-files-if-the-email-template-sender-has-its-own-smtp.md
@@ -18,9 +18,7 @@ internalReference: 771942
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md b/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
index 379c48023..e1cd4ec49 100644
--- a/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
+++ b/docs/known-issues/pt/ui-shows-duplicated-pickup-points-when-an-item-for-delivery-is-between-items-for-pickup.md
@@ -18,9 +18,7 @@ internalReference: 906549
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um carrinho com pelo menos três produtos, onde os pedidos de itens são: O primeiro é para retirada, o segundo é para entrega e o terceiro é para retirada, a interface do usuário mostrará o ponto de retirada duplicado. Isso acontece porque a API agrupará o 1º item e o 3º item, já que se trata do mesmo SLA.
diff --git a/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md b/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
index 1ee55fc53..e4d986750 100644
--- a/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
+++ b/docs/known-issues/pt/ui-shows-gifts-picked-when-using-order-replacement-feature.md
@@ -18,9 +18,7 @@ internalReference: 909137
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao usar o recurso de substituição de pedidos, a interface do usuário do checkout mostra "Presentes escolhidos!" mesmo que não haja nenhuma promoção de presentes configurada.
diff --git a/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md b/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
index f705d080c..6098cd3e7 100644
--- a/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
+++ b/docs/known-issues/pt/ui-triggers-separate-requests-for-each-keyfield-of-an-attachment.md
@@ -18,9 +18,7 @@ internalReference: 336371
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você define o valor de um campo de anexo de item por meio da interface do usuário, isso aciona uma solicitação para atualizar o orderForm, mesmo que ainda haja mais campos restantes.
diff --git a/docs/known-issues/pt/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md b/docs/known-issues/pt/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md
index 3937ca293..7333640f9 100644
--- a/docs/known-issues/pt/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md
+++ b/docs/known-issues/pt/ui-uses-the-wrong-sla-when-different-sellers-is-selected-for-delivery-and-pickup.md
@@ -18,9 +18,7 @@ internalReference: 797023
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Etiquetas brancas de vendedores diferentes podem ser selecionadas para atender aos produtos ao usar endereços diferentes para entrega e retirada. A interface do usuário considera o SLA errado ao alternar entre entrega e retirada.
diff --git a/docs/known-issues/pt/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md b/docs/known-issues/pt/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md
index 022b1e069..0c4990f22 100644
--- a/docs/known-issues/pt/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md
+++ b/docs/known-issues/pt/ui-wrongly-displaying-the-shipping-price-when-packages-are-split-for-scheduled-delivery.md
@@ -18,9 +18,7 @@ internalReference: 774155
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há um pacote dividido para entrega programada, o preço de um dos pacotes pode estar incorreto na IU, mas os preços estarão corretos na API.
diff --git a/docs/known-issues/pt/unable-to-access-vtex-payment-account.md b/docs/known-issues/pt/unable-to-access-vtex-payment-account.md
index 7154870a7..28d848ef8 100644
--- a/docs/known-issues/pt/unable-to-access-vtex-payment-account.md
+++ b/docs/known-issues/pt/unable-to-access-vtex-payment-account.md
@@ -18,9 +18,7 @@ internalReference: 550244
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Uma mensagem de erro é exibida quando se tenta acessar o módulo de pagamento VTEX
diff --git a/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md b/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md
index a0deac9e9..e789f5c80 100644
--- a/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md
+++ b/docs/known-issues/pt/unable-to-cancel-transactions-that-had-payout-split-config-change.md
@@ -18,9 +18,7 @@ internalReference: 364382
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando há uma mudança na configuração, adicionando a divisão do pagamento, e isto faz com que novas transações tenham informações que antes não estavam disponíveis e agora serão utilizadas na operação de cancelamento, o que faz com que as transações criadas antes desta configuração não sejam canceladas.
diff --git a/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md b/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
index aef2c13a3..cef256177 100644
--- a/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
+++ b/docs/known-issues/pt/unable-to-change-status-on-gateway-when-transaction-cart-object-in-transaction-is-unknown.md
@@ -18,9 +18,7 @@ internalReference: 776837
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A fim de cancelar ou alterar um pedido para cenários divididos, nossa porta de entrada requer um objeto de carrinho. Entretanto, se o processo de checkout via OMS enviar um objeto de carrinho nulo/ desconhecido, nosso gateway não pode processar estas operações, resultando em um erro de análise da biblioteca Newtonsoft utilizada no gateway.
diff --git a/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md b/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md
index 604a047e1..53d4377f4 100644
--- a/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md
+++ b/docs/known-issues/pt/unable-to-create-produtos-relacionados-custom-element.md
@@ -18,9 +18,7 @@ internalReference: 326899
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Incapaz de criar "Produtos Relacionados" Elemento Personalizado no CMS
diff --git a/docs/known-issues/pt/unable-to-delete-template-on-legacy-cms.md b/docs/known-issues/pt/unable-to-delete-template-on-legacy-cms.md
index c5dcd2849..4c95a3259 100644
--- a/docs/known-issues/pt/unable-to-delete-template-on-legacy-cms.md
+++ b/docs/known-issues/pt/unable-to-delete-template-on-legacy-cms.md
@@ -18,9 +18,7 @@ internalReference: 332033
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os clientes não são capazes de excluir os modelos do CMS antigo.
diff --git a/docs/known-issues/pt/unable-to-download-prices-importing-results.md b/docs/known-issues/pt/unable-to-download-prices-importing-results.md
index 79e20630b..2ad5cc2f4 100644
--- a/docs/known-issues/pt/unable-to-download-prices-importing-results.md
+++ b/docs/known-issues/pt/unable-to-download-prices-importing-results.md
@@ -18,9 +18,7 @@ internalReference: 579906
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/unable-to-export-more-than-65536-lines-in-cms-builder.md b/docs/known-issues/pt/unable-to-export-more-than-65536-lines-in-cms-builder.md
index 80e415c12..9dcd14381 100644
--- a/docs/known-issues/pt/unable-to-export-more-than-65536-lines-in-cms-builder.md
+++ b/docs/known-issues/pt/unable-to-export-more-than-65536-lines-in-cms-builder.md
@@ -18,9 +18,7 @@ internalReference: 492861
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Incapaz de exportar mais de 65.536 linhas em CMS Builder (.xls limite de linha)
diff --git a/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md b/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md
index 7fad9a014..aa3ce0d88 100644
--- a/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md
+++ b/docs/known-issues/pt/unable-to-log-in-through-the-google-app-on-ios.md
@@ -18,9 +18,7 @@ internalReference: 926239
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao fazer login na loja a partir do aplicativo do Google (somente no aplicativo do Google e não no navegador Google Chrome em dispositivos iOS), a opção entra em loop e nunca abre o Google para escolher a conta.
diff --git a/docs/known-issues/pt/unable-to-pause-seller.md b/docs/known-issues/pt/unable-to-pause-seller.md
index 54f27b630..f09d66075 100644
--- a/docs/known-issues/pt/unable-to-pause-seller.md
+++ b/docs/known-issues/pt/unable-to-pause-seller.md
@@ -18,9 +18,7 @@ internalReference: 682151
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes o mercado não consegue fazer uma pausa no vendedor via admin ou via API.
diff --git a/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md b/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
index 2f68a7ae5..a0dda3c8c 100644
--- a/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
+++ b/docs/known-issues/pt/unable-to-upload-spreadsheet-images-with-host-services-using-protocol-encryption-protocol-ssl13.md
@@ -18,9 +18,7 @@ internalReference: 851911
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o host de imagens da planilha usa um protocolo de criptografia SSL1.3, aparece um erro ao tentar carregar a planilha:
diff --git a/docs/known-issues/pt/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md b/docs/known-issues/pt/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md
index f9f13f1c7..140cc3544 100644
--- a/docs/known-issues/pt/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md
+++ b/docs/known-issues/pt/unavailable-items-breaking-the-orderform-calculation-in-a-specific-scenario-while-using-whitelabel-sellers.md
@@ -18,9 +18,7 @@ internalReference: 745047
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md b/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md
index 295f44a37..c72027474 100644
--- a/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md
+++ b/docs/known-issues/pt/unavailable-products-pdp-are-still-being-returned.md
@@ -18,9 +18,7 @@ internalReference: 1041920
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um produto não está disponível, seu PDP ainda pode ser devolvido.
diff --git a/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md b/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
index 6ef5bb6bd..fa490dd72 100644
--- a/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
+++ b/docs/known-issues/pt/unecessary-search-results-prioritization-by-diacritics-for-portuguese.md
@@ -18,9 +18,7 @@ internalReference: 1028763
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A Pesquisa Inteligente prioriza os resultados que têm uma correspondência exata, considerando os diacríticos do termo pesquisado e os produtos.
diff --git a/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md b/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md
index 0e96c9980..335cf8420 100644
--- a/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md
+++ b/docs/known-issues/pt/unecessary-simulation-requests-and-components-being-reloaded.md
@@ -18,9 +18,7 @@ internalReference: 648298
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pedidos múltiplos de simulação podem ser feitos após alterações na ordemFormulário. Isto está relacionado com o cálculo _lean shipping_ para calcular os pacotes de envio.
diff --git a/docs/known-issues/pt/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md b/docs/known-issues/pt/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md
index feccd47a4..c15d560f3 100644
--- a/docs/known-issues/pt/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md
+++ b/docs/known-issues/pt/unexpected-behavior-in-slider-layout-when-using-the-props-infinitetrue-and-navigationstep1.md
@@ -18,9 +18,7 @@ internalReference: 462895
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Um comportamento inesperado ocorre quando se utiliza o vtex.slider-layout, se estes dois prumos forem colocados juntos:
diff --git a/docs/known-issues/pt/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md b/docs/known-issues/pt/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md
index e19c4e133..bb464f723 100644
--- a/docs/known-issues/pt/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md
+++ b/docs/known-issues/pt/unexpected-multiple-pickup-point-selection-for-the-same-seller-when-not-every-item-is-available-through-the-same-option.md
@@ -18,9 +18,7 @@ internalReference: 467702
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md b/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md
index c211f8fc9..13d3925b3 100644
--- a/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md
+++ b/docs/known-issues/pt/unexpected-reload-happening-when-registeringupdating-a-product.md
@@ -18,9 +18,7 @@ internalReference: 863542
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md b/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
index 627f6f306..63b185e52 100644
--- a/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
+++ b/docs/known-issues/pt/unhandled-exception-error-when-changing-edition-of-account.md
@@ -18,9 +18,7 @@ internalReference: 907294
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes, quando alteramos a edição de uma conta ou espaço de trabalho, podemos encontrar o seguinte erro:
diff --git a/docs/known-issues/pt/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md b/docs/known-issues/pt/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md
index e96ee7e56..245f7ef10 100644
--- a/docs/known-issues/pt/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md
+++ b/docs/known-issues/pt/unrelated-transaction-returned-when-using-sequence-number-to-fetch-a-transaction-in-admin-ui.md
@@ -18,9 +18,7 @@ internalReference: 503446
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o usuário procura uma transação no administrador pelo número de seqüência, em alguns casos, o retorno é a transação desejada e transação não relacionada com o status de chargeback.
diff --git a/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md b/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
index 0003b8b3a..c2e96b091 100644
--- a/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
+++ b/docs/known-issues/pt/unspecific-error-message-when-exporting-produtoexportacaoimportacaoespecificacaov2aspx.md
@@ -18,9 +18,7 @@ internalReference: 314227
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a mensagem de erro da interface ProdutoExportacaoImportacaoEspecificacaoV2.aspx no catálogo de importação/exportação, quando um usuário está tentando exportar uma ficha de especificação de produto e não há produtos em uma determinada categoria (mas há especificações registradas), não apontam a origem do problema.
diff --git a/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md b/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
index 2433a33c2..4245f46f1 100644
--- a/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
+++ b/docs/known-issues/pt/unsupported-fields-by-the-intelligent-search-api-return-wrong-or-empty-data.md
@@ -18,9 +18,7 @@ internalReference: 1032531
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A API de pesquisa inteligente baseia-se principalmente na API de pesquisa de catálogo herdada por motivos de compatibilidade, mas nem todas as propriedades retornam as mesmas informações. Em alguns casos, elas são diferentes ou estão vazias.
diff --git a/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md b/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
index 2e8860a57..40e966c33 100644
--- a/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
+++ b/docs/known-issues/pt/update-seller-using-admin-is-setting-some-fields-back-to-the-default-value-after-changing-it-via-api.md
@@ -18,9 +18,7 @@ internalReference: 608120
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md b/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
index a6ef8a525..ae351f672 100644
--- a/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
+++ b/docs/known-issues/pt/update-sellers-available-trade-policies-does-not-trigger-automatic-indexation.md
@@ -18,9 +18,7 @@ internalReference: 1041874
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Na UI de gerenciamento do vendedor, remova ou adicione uma nova política comercial a um vendedor.
diff --git a/docs/known-issues/pt/update-users-name-in-the-login-section.md b/docs/known-issues/pt/update-users-name-in-the-login-section.md
index 17afc996b..cb7a3f5f6 100644
--- a/docs/known-issues/pt/update-users-name-in-the-login-section.md
+++ b/docs/known-issues/pt/update-users-name-in-the-login-section.md
@@ -18,9 +18,7 @@ internalReference: 542029
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualizar o nome do usuário na seção de login
diff --git a/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md b/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
index 7d7e1f6b5..517d3b32a 100644
--- a/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
+++ b/docs/known-issues/pt/updating-product-specifications-unviable-due-to-lacking-property-on-get-resp-json.md
@@ -18,9 +18,7 @@ internalReference: 301725
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 A resposta da GET Product Specification JSON carece de uma propriedade essencial para atualizar as especificações pré-existentes, se assim for necessário pelo usuário.
 
diff --git a/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md b/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md
index 5050f5259..eee67bb5b 100644
--- a/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md
+++ b/docs/known-issues/pt/upload-file-not-working-on-adminportalsitesdefaultcode.md
@@ -18,9 +18,7 @@ internalReference: 897956
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao tentar carregar um novo arquivo em admin/portal/#/sites/default/code, nada acontece. Ao verificar o console no devTools, podemos ver uma mensagem de erro:
diff --git a/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md b/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md
index 4b12f69c0..9cd9c924d 100644
--- a/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md
+++ b/docs/known-issues/pt/url-logo-field-in-the-update-seller-request-not-updating.md
@@ -18,9 +18,7 @@ internalReference: 271480
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Tentar atualizar o campo "UrlLogo" na rota /api/catalog_system/pvt/seller não está refletindo nenhuma mudança.
diff --git a/docs/known-issues/pt/url-redirect-with-special-characters-non-ascii-return-errors.md b/docs/known-issues/pt/url-redirect-with-special-characters-non-ascii-return-errors.md
index 83e35fe76..0ce109362 100644
--- a/docs/known-issues/pt/url-redirect-with-special-characters-non-ascii-return-errors.md
+++ b/docs/known-issues/pt/url-redirect-with-special-characters-non-ascii-return-errors.md
@@ -18,9 +18,7 @@ internalReference: 457047
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se criarmos um redirecionamento com alguns caracteres especiais, por exemplo `/televisão`, ele não funcionará, receberemos o seguinte erro:
diff --git a/docs/known-issues/pt/urls-redirecionando-para-buscavazia.md b/docs/known-issues/pt/urls-redirecionando-para-buscavazia.md
index 6274cbb0d..ef845dd56 100644
--- a/docs/known-issues/pt/urls-redirecionando-para-buscavazia.md
+++ b/docs/known-issues/pt/urls-redirecionando-para-buscavazia.md
@@ -18,9 +18,7 @@ internalReference: 322251
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Alguns URLs estão redirecionando para uma resposta EmptySearch.
diff --git a/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md b/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
index 5280216f2..4815a0758 100644
--- a/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
+++ b/docs/known-issues/pt/user-can-still-see-and-access-cms-features-even-without-the-correct-permission.md
@@ -18,9 +18,7 @@ internalReference: 1046263
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se o usuário não tiver nenhuma das permissões do CMS, ele não deverá ser capaz de acessar ou mesmo ver os módulos do CMS. Mas isso não está acontecendo.
diff --git a/docs/known-issues/pt/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md b/docs/known-issues/pt/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md
index 6250b1869..795a1c7ef 100644
--- a/docs/known-issues/pt/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md
+++ b/docs/known-issues/pt/user-deletion-from-order-authorization-rule-blocks-order-and-does-not-allow-ui-reprocessing.md
@@ -18,9 +18,7 @@ internalReference: 623376
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando apagamos ou perdemos o acesso ao usuário vinculado a uma regra de aprovação de ordem, esta ordem não pode ser reprocessada para que um novo usuário possa aprovar a ordem e com isso a ordem permanece pendente de aprovação.
diff --git a/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md b/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
index 465d6d519..bef3f3d3e 100644
--- a/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
+++ b/docs/known-issues/pt/user-only-with-the-role-user-administrator-restricted-is-not-able-to-list-the-users.md
@@ -18,9 +18,7 @@ internalReference: 932666
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se um usuário administrador tiver apenas a função "**User Administrator - RESTRICTED**" (recurso "**Save user**"), a lista de usuários não estará disponível e não será possível fazer as edições ou exclusões necessárias.
diff --git a/docs/known-issues/pt/user-receives-error-message-on-first-registration-in-my-account.md b/docs/known-issues/pt/user-receives-error-message-on-first-registration-in-my-account.md
index 1ebe15e5b..4f248db3f 100644
--- a/docs/known-issues/pt/user-receives-error-message-on-first-registration-in-my-account.md
+++ b/docs/known-issues/pt/user-receives-error-message-on-first-registration-in-my-account.md
@@ -18,9 +18,7 @@ internalReference: 619909
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um novo usuário se registra em **Minha conta***, a página executa duas solicitações, uma enviando os dados e a outra consultando o `ide do usuário` desse usuário, mas nesta segunda solicitação o retorno é 404 não encontrado, e a página exibe uma mensagem de erro para o usuário.
diff --git a/docs/known-issues/pt/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md b/docs/known-issues/pt/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md
index ec251012b..8cfda32d0 100644
--- a/docs/known-issues/pt/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md
+++ b/docs/known-issues/pt/users-are-unable-to-access-customer-credit-settings-ui-on-the-admin-due-to-a-forbidden-error.md
@@ -18,9 +18,7 @@ internalReference: 380931
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Os usuários não podem acessar a interface de configuração de crédito do cliente na interface de administração e observamos o seguinte erro "Proibido" na operação de configuração de consultas.
diff --git a/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md b/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md
index 5bae3b8f7..d5ba494b8 100644
--- a/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md
+++ b/docs/known-issues/pt/users-cant-access-gift-card-admin-looping-page.md
@@ -18,9 +18,7 @@ internalReference: 1025971
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se os usuários bloquearem cookies de terceiros (configurações do navegador), eles não poderão acessar o módulo Gift Card no admin, pois há um cookie definido em outro domínio da VTEX.
diff --git a/docs/known-issues/pt/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md b/docs/known-issues/pt/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md
index b4f46f701..d21a50977 100644
--- a/docs/known-issues/pt/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md
+++ b/docs/known-issues/pt/users-cant-access-master-datacrm-system-when-they-try-to-log-in-by-saml-authentication.md
@@ -18,9 +18,7 @@ internalReference: 465652
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O usuário não pode acessar o sistema Master Data/CRM via autenticação SAML
diff --git a/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md b/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
index d2e36c0ef..8b1b5a31b 100644
--- a/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
+++ b/docs/known-issues/pt/users-with-more-than-one-order-registered-on-bk-entity-with-different-emails-can-not-see-the-orders-on-my-account-page.md
@@ -18,9 +18,7 @@ internalReference: 986324
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Devido à unificação de perfis, alguns usuários podem ter pedidos com e-mails diferentes, e isso é um problema para mostrar os pedidos na página minha conta (meus pedidos).
diff --git a/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md b/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
index a7165c3a9..92f0c4c60 100644
--- a/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
+++ b/docs/known-issues/pt/usesessionregionatcheckout-doesnt-work-properly-when-adding-the-first-item-to-the-cart.md
@@ -18,9 +18,7 @@ internalReference: 925049
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se uma conta tiver a opção "UseSessionRegionAtCheckout" configurada, ao adicionar um item e o formulário de pedido não tiver "shippingData", o vendedor não será definido, mostrando preços e disponibilidade diferentes.
diff --git a/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md b/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
index 031c04a87..ab737fbcd 100644
--- a/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
+++ b/docs/known-issues/pt/using-many-filters-in-the-oms-list-affects-the-results-in-the-report.md
@@ -18,9 +18,7 @@ internalReference: 756198
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O uso de filtros na Lista de gerenciamento de pedidos gera um parâmetro no URL que ajuda a definir o que é mostrado quando a página é carregada e a gerar o relatório de pedidos exportados. Nesse sentido, à medida que usamos mais e mais filtros, os parâmetros incluídos no URL aumentam proporcionalmente e a string de consulta aumenta, chegando a pontos (tamanho) que podem gerar vários tipos de comportamentos indesejados.
diff --git a/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md b/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
index 3b052684d..f1b4cefe2 100644
--- a/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
+++ b/docs/known-issues/pt/using-sliderlayout-with-the-prop-navigationstep-to-1-causes-last-dots-to-be-empty.md
@@ -18,9 +18,7 @@ internalReference: 910125
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando temos um bloco de layout de controle deslizante com a propriedade `navigationStep` definida como 1 e `itemsPerPage` diferente de 1, o último ponto fica vazio e não é possível excluí-lo.
diff --git a/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md b/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
index ca72e1a76..a26d0162c 100644
--- a/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
+++ b/docs/known-issues/pt/utmip-e-utmipc-not-being-kept-on-the-url-after-login.md
@@ -18,9 +18,7 @@ internalReference: 372787
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md b/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md
index b0d4b49b9..acd2c2c71 100644
--- a/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md
+++ b/docs/known-issues/pt/validatecartmutation-failing-when-large-payload.md
@@ -18,9 +18,7 @@ internalReference: 985867
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/validation-of-credit-card-fields-at-checkout-not-working-properly.md b/docs/known-issues/pt/validation-of-credit-card-fields-at-checkout-not-working-properly.md
index 353299539..d2342b767 100644
--- a/docs/known-issues/pt/validation-of-credit-card-fields-at-checkout-not-working-properly.md
+++ b/docs/known-issues/pt/validation-of-credit-card-fields-at-checkout-not-working-properly.md
@@ -18,19 +18,13 @@ internalReference: 552897
 
 ## Sumário
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Simulação
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
 ## Workaround
 
-<div class="alert alert-warning">
-  <p>Este conteúdo só está disponível em Inglês.</p>
-</div>
+>⚠️ Este conteúdo só está disponível em Inglês.
 
diff --git a/docs/known-issues/pt/vbase-responds-404-to-vtexpagesgraphql.md b/docs/known-issues/pt/vbase-responds-404-to-vtexpagesgraphql.md
index 0d3e74919..c81ce698c 100644
--- a/docs/known-issues/pt/vbase-responds-404-to-vtexpagesgraphql.md
+++ b/docs/known-issues/pt/vbase-responds-404-to-vtexpagesgraphql.md
@@ -18,9 +18,7 @@ internalReference: 822031
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O VBase está respondendo 404 para o aplicativo vtex.pages-graphql instalado na conta, por algum motivo, o aplicativo não está sendo encontrado e, como consequência, o comprador será afetado por não conseguir acessar um produto ou uma página específica na loja. Esse erro 404 é armazenado em cache por 2 horas, portanto, o problema normalmente é interrompido após o término do cache. O problema é intermitente e ainda não conseguimos descobrir o motivo pelo qual ele está ocorrendo.
diff --git a/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md b/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
index b37034e42..db03997bb 100644
--- a/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
+++ b/docs/known-issues/pt/verification-transactions-when-saving-card-in-mycards-are-not-automatically-canceled.md
@@ -18,9 +18,7 @@ internalReference: 347084
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando um cartão é salvo no módulo MyCards, é gerada uma transação de verificação no valor de R$ 1,50, que, após seguir o fluxo de autorização e aprovação, deve ser automaticamente cancelada. Esta transação destina-se a validar que o cartão salvo é autêntico e está transacionando sem problemas.
diff --git a/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md b/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
index dfe8ea04d..345cd2746 100644
--- a/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
+++ b/docs/known-issues/pt/version-author-note-not-found-on-vtex-id-on-the-profile.md
@@ -18,9 +18,7 @@ internalReference: 914314
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando o cliente faz uma compra, o autor da versão recebe um ID de usuário (guid) ou um serviço, seguido pelo login/nome/descrição "`Note: Not found on VTEX ID.`" no perfil.
diff --git a/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md b/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md
index 80688dffc..973d5644c 100644
--- a/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md
+++ b/docs/known-issues/pt/via-integration-not-sending-the-description-in-card.md
@@ -18,9 +18,7 @@ internalReference: 826488
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md b/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
index bb0476b78..5dbf15512 100644
--- a/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
+++ b/docs/known-issues/pt/video-attribute-is-not-being-sent-from-seller-to-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 519412
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 As integrações VTEX<>VTEX não estão conseguindo enviar atributos de vídeo do vendedor para o marketplace.
diff --git a/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md b/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md
index 8cc6f48b2..4a02238f1 100644
--- a/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md
+++ b/docs/known-issues/pt/video-component-doesnt-work-properly-on-ios-devices.md
@@ -18,9 +18,7 @@ internalReference: 609462
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O componente nativo do Vídeo exibe comportamento inconsistente quando se tenta renderizar YouTube ou Vimeo iFrame em dispositivos iOS. Em alguns testes o iFrame não foi renderizado como esperado, ou sua colocação não foi de acordo com o que foi definido no código ou no Editor do site.
diff --git a/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md b/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
index 8f851af72..5f37beeac 100644
--- a/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
+++ b/docs/known-issues/pt/viewcart-event-is-only-received-on-the-datalayer-every-other-time.md
@@ -18,9 +18,7 @@ internalReference: 1048306
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O evento view_cart só é recebido no dataLayer a cada duas vezes.
diff --git a/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md b/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
index b1e03782d..c181ea262 100644
--- a/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
+++ b/docs/known-issues/pt/viewcart-event-is-triggered-twice-when-we-change-product-quantity-in-minicart.md
@@ -18,9 +18,7 @@ internalReference: 1040772
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando alteramos a quantidade de um produto no minicarro, o evento view_cart é acionado duas vezes
diff --git a/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md b/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
index 632e6b434..ed1fe743d 100644
--- a/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
+++ b/docs/known-issues/pt/visited-product-feature-does-not-work-properly.md
@@ -18,9 +18,7 @@ internalReference: 701169
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O gatilho do produto visitado, que utiliza os dados capturados por Request Capture, é configurado com o filtro "checkout" definido como "nulo". Entretanto, a Request Capture precisa passar pelo checkout para capturar os dados do usuário e de navegação e preenchê-los nos Dados Mestres. Como resultado, o gatilho não funciona corretamente porque o RC não pode preencher os dados antes do checkout.
diff --git a/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md b/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
index 527f4ca9a..f9e3a64cc 100644
--- a/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
+++ b/docs/known-issues/pt/visual-merchandising-rules-do-not-work-when-multiple-search-terms-are-provided.md
@@ -18,9 +18,7 @@ internalReference: 1053623
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Embora seja possível fornecer vários termos de pesquisa ao criar uma regra de visual merchandising para a Pesquisa Inteligente, eles não podem ser usados. A regra será considerada inválida e não será aplicada.
diff --git a/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md b/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
index ec35c96ca..d92c9ed00 100644
--- a/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
+++ b/docs/known-issues/pt/vtexcmc-productgifts-does-not-work-before-acessing-checkout.md
@@ -18,9 +18,7 @@ internalReference: 1029719
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md b/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md
index 7ddbadd38..d0b90c16a 100644
--- a/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md
+++ b/docs/known-issues/pt/vtexcontentplaceholder-idacessorios-is-not-working.md
@@ -18,9 +18,7 @@ internalReference: 466147
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O controle `<vtex:contentPlaceHolder id="Acessorios"/>` deve trazer uma visão dos produtos relacionados definidos como o tipo `acessorios` para a página do produto.
diff --git a/docs/known-issues/pt/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md b/docs/known-issues/pt/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md
index 331312299..184da5ea0 100644
--- a/docs/known-issues/pt/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md
+++ b/docs/known-issues/pt/vtexeventsadddata-adding-pageurl-parameter-using-http-not-https.md
@@ -18,9 +18,7 @@ internalReference: 348128
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 `vtex.events.addData` adicionando pageUrl Parameter utilizando http, não https
diff --git a/docs/known-issues/pt/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md b/docs/known-issues/pt/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md
index 85ea5d95a..5c9282d76 100644
--- a/docs/known-issues/pt/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md
+++ b/docs/known-issues/pt/warehouse-api-demonstrates-pickup-point-deleted-instore-warehouse.md
@@ -18,9 +18,7 @@ internalReference: 573017
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você apaga um ponto de coleta ligado a um depósito (inStore warehouse), o ponto de coleta permanece ligado ao depósito se você o consultar via API.
diff --git a/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md b/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
index 970aab24c..5c937f2a4 100644
--- a/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
+++ b/docs/known-issues/pt/we-have-a-problem-validating-the-clientid-field-of-the-giftcard-on-admin.md
@@ -18,9 +18,7 @@ internalReference: 454388
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Temos um problema de validação no campo ClientId na tela Giftcards. O campo originalmente chamado CPF/CNPJ em português, foi traduzido para o inglês como clientId. Mas, quando o usuário deseja criar um novo Giftcard através da UI, o campo é formatado automaticamente inserindo os caracteres ".", "-" e "/" para que os dados inseridos estejam de acordo com as normas do CPF ou CNPJ.
diff --git a/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md b/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
index bcbc1ebab..c451f1571 100644
--- a/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
+++ b/docs/known-issues/pt/webanalytics-viewpart-shows-success-even-when-it-isnt-working.md
@@ -18,9 +18,7 @@ internalReference: 768059
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Atualmente, a parte de visualização da webanalytics não apresenta nenhuma mensagem de erro, mesmo quando falha e não entrega o conteúdo dos metadados ao usuário.
diff --git a/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md b/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md
index 5ade74313..7feacf549 100644
--- a/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md
+++ b/docs/known-issues/pt/webops-app-is-not-fully-integrated-with-headless-cms.md
@@ -18,9 +18,7 @@ internalReference: 1048810
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O aplicativo `vtex.webops` não está totalmente integrado ao CMS headless, isso está relacionado aos repositórios do Github hospedados externamente e ao processo de publicação
diff --git a/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md b/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
index e441fcf1a..9f0f36f39 100644
--- a/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
+++ b/docs/known-issues/pt/when-accessing-my-orders-the-name-that-appears-is-the-name-of-the-productname-without-the-sku-name-information.md
@@ -18,9 +18,7 @@ internalReference: 694809
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao acessar "my orders", o nome que aparece é o nome do "ProductName" sem a informação "SKU Name", somente na interface IO.
diff --git a/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md b/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
index 4f193e236..3d914936d 100644
--- a/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
+++ b/docs/known-issues/pt/when-adding-a-sku-through-our-change-order-functionality-the-product-name-is-not-displayed-in-the-order-and-email-notification.md
@@ -18,9 +18,7 @@ internalReference: 557978
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md b/docs/known-issues/pt/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md
index 877317909..6275f2a96 100644
--- a/docs/known-issues/pt/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md
+++ b/docs/known-issues/pt/when-an-error-occurs-after-firstdata-approves-a-settlement-the-transaction-cannot-be-completed.md
@@ -18,9 +18,7 @@ internalReference: 760458
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 s vezes, podem ocorrer erros durante o processamento de nossas operações através da porta de entrada. No caso do conector da Firstdata, pode ocorrer um erro imediatamente após a aprovação do acordo do nosso lado. Para resolver isso, precisamos solicitar novamente um acordo. Entretanto, devido à idempotência, o provedor não envia uma resposta "aprovada" novamente, o que pode fazer com que a transação fique presa em um status de "liquidação" até que uma nova atualização de status seja fornecida.
diff --git a/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md b/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
index b7bfe59a1..8cb07c177 100644
--- a/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
+++ b/docs/known-issues/pt/when-disabling-native-service-worker-its-not-possible-to-use-a-custom-one.md
@@ -18,9 +18,7 @@ internalReference: 770949
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md b/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
index 9c874336d..831aa266b 100644
--- a/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
+++ b/docs/known-issues/pt/when-loading-the-catalog-maping-page-on-admin-the-initial-message-is-not-translated.md
@@ -18,9 +18,7 @@ internalReference: 717066
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md b/docs/known-issues/pt/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md
index fc30e93aa..3c12a797f 100644
--- a/docs/known-issues/pt/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md
+++ b/docs/known-issues/pt/when-selecting-pickup-not-highlighted-in-the-list-of-pickups-in-the-cart-ui-makes-incorrect-request-to-api.md
@@ -18,9 +18,7 @@ internalReference: 529850
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando você seleciona uma opção de pickup que não está destacada, a IU faz uma solicitação incorreta à API, e com isso, a solicitação recebe um erro e não atualiza os dados desta pickup selecionada.
diff --git a/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md b/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
index 271a7df09..e912008c5 100644
--- a/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
+++ b/docs/known-issues/pt/when-settleid-is-sent-as-null-and-code-as-refundmanually-our-gateway-performs-a-double-refund.md
@@ -18,9 +18,7 @@ internalReference: 615050
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A documentação do PPP indica que quando o processo de reembolso não funcionou, o provedor deve responder com um `nulo` a este campo, e também quando o reembolso deve ser feito manualmente, o campo de código deve ter o valor "reembolso-manual".
diff --git a/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md b/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
index 2c53150ab..3d63cc29c 100644
--- a/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
+++ b/docs/known-issues/pt/when-shippingestimate-is-0-the-deliveryslainminutes-calculation-returns-null.md
@@ -18,9 +18,7 @@ internalReference: 514835
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 No fluxo de checkout `deliverySlaInMinutes` delivery checkout juntamente com os detalhes da transação para o gateway, estes dados são calculados com base na `shippingEstimate` entregue pela logística, porém quando este valor entregue pela logística é = 0 a resposta de checkout para `deliverySlaInMinutes` é 0 zero, quando o correto seria 0; porém isto acaba afetando diretamente o fluxo desenvolvido pelo gateway para a anti-fraude;
diff --git a/docs/known-issues/pt/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md b/docs/known-issues/pt/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md
index 1c7b7588c..0f3accb8f 100644
--- a/docs/known-issues/pt/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md
+++ b/docs/known-issues/pt/when-trying-to-setup-the-braspag-antifraud-the-user-is-directed-to-the-braspag-affiliation-screen.md
@@ -18,9 +18,7 @@ internalReference: 334239
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Temos duas integrações internas com a Braspag, uma para a luta antifraude e outra para uma afiliação (ambas com o mesmo nome). Ao tentar clicar em anti-fraude para configurar, o usuário é direcionado para os campos de configuração de afiliação. Portanto, não é possível configurar o antifraude da Braspag através da UI Admin
diff --git a/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md b/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
index 2f9cab316..136ee598d 100644
--- a/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
+++ b/docs/known-issues/pt/when-using-horizontal-filters-after-choosing-three-of-them-the-filters-options-doesnt-colapse-anymore.md
@@ -18,9 +18,7 @@ internalReference: 859382
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Quando a loja estiver usando os filtros na opção horizontal, toda vez que você clicar em um filtro, suas opções serão recolhidas. Porém, quando você clica em um filtro pela terceira vez, o filtro não é mais recolhido. Ele travará.
diff --git a/docs/known-issues/pt/wrong-button-calltoaction-name-in-profile-step.md b/docs/known-issues/pt/wrong-button-calltoaction-name-in-profile-step.md
index d52c8f2db..66260845e 100644
--- a/docs/known-issues/pt/wrong-button-calltoaction-name-in-profile-step.md
+++ b/docs/known-issues/pt/wrong-button-calltoaction-name-in-profile-step.md
@@ -18,9 +18,7 @@ internalReference: 514532
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao preencher os dados na etapa de perfil no checkout e prosseguir para a etapa de envio, ao retornar clicando na seta de retorno do navegador, ao alcançar o perfil novamente o botão para prosseguir para a etapa seguinte, deve estar com o nome de '**Ir para entrega**' no entanto diz '**Ir para pagamento**', mesmo com o componente de envio ainda não preenchido.
diff --git a/docs/known-issues/pt/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md b/docs/known-issues/pt/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md
index 0e328a565..d2873ade3 100644
--- a/docs/known-issues/pt/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md
+++ b/docs/known-issues/pt/wrong-error-message-for-place-order-api-when-the-payload-request-is-invalid.md
@@ -18,9 +18,7 @@ internalReference: 709180
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Pedidos inválidos para a API "place order" retornam uma mensagem de erro errada, informando "Invalid id for item" em vez de apontar quais informações estão erradas.
diff --git a/docs/known-issues/pt/wrong-message-error-when-using-a-nonexisting-gift-card.md b/docs/known-issues/pt/wrong-message-error-when-using-a-nonexisting-gift-card.md
index 34da77424..bd05a6758 100644
--- a/docs/known-issues/pt/wrong-message-error-when-using-a-nonexisting-gift-card.md
+++ b/docs/known-issues/pt/wrong-message-error-when-using-a-nonexisting-gift-card.md
@@ -18,9 +18,7 @@ internalReference: 584102
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 há um manuseio incorreto de um dos erros do sistema de cartões-presente da VTEX. Quando o usuário estiver preenchendo o código de resgate do cartão-presente no checkout, se o usuário preencher um código de compra que não existe, ao invés de ser informado que o código é inválido, o seguinte erro será exibido no checkout "_Ocorreu um erro de comunicação com o sistema de cartão-presente_". Mas, na verdade, não há problema de conexão, é apenas que o vale não existe.
diff --git a/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md b/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
index b9f151d8b..b33eb0371 100644
--- a/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
+++ b/docs/known-issues/pt/wrong-spotprice-for-items-with-unitmultiplier-greater-than-1-in-intelligent-search-apis.md
@@ -18,9 +18,7 @@ internalReference: 934687
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nas APIs de pesquisa inteligente (GraphQL ou REST), a propriedade `spotPrice` do objeto `items.sellers.commertialOffer` está incorreta para itens em que o `unitMultiplier` é maior que `1`.
diff --git a/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md b/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md
index c108c18aa..21b9c0544 100644
--- a/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md
+++ b/docs/known-issues/pt/wrong-translation-for-different-fields-under-the-same-original-value.md
@@ -18,9 +18,7 @@ internalReference: 982848
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 O Intelligent Search pode usar a tradução errada para um campo cujo valor no idioma principal é o mesmo entre campos diferentes.
diff --git a/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md b/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
index 1a187a5e4..c6a256b0c 100644
--- a/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
+++ b/docs/known-issues/pt/wrong-value-for-pricedefinition-in-the-chain-order-for-a-multilevel-marketplace.md
@@ -18,9 +18,7 @@ internalReference: 663203
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A propriedade "priceDefinition" para pedidos no nível "chain" em um marketplace multinível não está seguindo o "sellingPrice" como esperado. Em vez disso, está seguindo a propriedade "price".
diff --git a/docs/known-issues/pt/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md b/docs/known-issues/pt/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md
index 01bc117e0..8861bf011 100644
--- a/docs/known-issues/pt/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md
+++ b/docs/known-issues/pt/wrong-values-in-recipients-of-a-transaction-split-with-partial-cancellation.md
@@ -18,9 +18,7 @@ internalReference: 489481
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Em um cenário de Payout Split, quando há um cancelamento parcial antes da captura, não alteramos os campos dos destinatários para que os valores para quando cada participante receberá sejam diferentes do correto, ou seja, os valores dentro dos destinatários da liquidação aparecem como se não tivesse havido cancelamento parcial.
diff --git a/docs/known-issues/pt/xml-file-does-not-get-price-from-swl.md b/docs/known-issues/pt/xml-file-does-not-get-price-from-swl.md
index 25445af0e..11a883ca9 100644
--- a/docs/known-issues/pt/xml-file-does-not-get-price-from-swl.md
+++ b/docs/known-issues/pt/xml-file-does-not-get-price-from-swl.md
@@ -18,9 +18,7 @@ internalReference: 425027
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Se criarmos um arquivo XML em um MarketPlace que carrega preços da White Label dos Vendedores, nosso XML não mostrará esses preços
diff --git a/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md b/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
index b91264011..64dcb384f 100644
--- a/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
+++ b/docs/known-issues/pt/xml-global-category-field-showing-the-information-defined-on-category-global-level.md
@@ -18,9 +18,7 @@ internalReference: 282231
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Nos arquivos XML, o campo para Categoria Global está fornecendo as informações da Categoria Global definida no Nível da Categoria e não no Nível do Produto (o nível do produto deve ser priorizado).
diff --git a/docs/known-issues/pt/xml-installment-currency-does-not-apply.md b/docs/known-issues/pt/xml-installment-currency-does-not-apply.md
index feaf748e3..a4887be67 100644
--- a/docs/known-issues/pt/xml-installment-currency-does-not-apply.md
+++ b/docs/known-issues/pt/xml-installment-currency-does-not-apply.md
@@ -18,9 +18,7 @@ internalReference: 976295
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao configurar uma moeda em um XML, ela se aplica a todos os campos, exceto ao campo "Parcela".
diff --git a/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md b/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
index 517e24b3f..5ac34f9fd 100644
--- a/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
+++ b/docs/known-issues/pt/xml-price-related-tags-do-not-load-contents-for-unavailable-items.md
@@ -18,9 +18,7 @@ internalReference: 974722
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 A integração XML carrega qualquer tag relacionada ao preço, como minPrice, maxPrice, currentPrice, que são carregadas como uma tag de valor nulo (<![CDATA[]]>) quando o item não está disponível e também são definidas para serem exibidas se não estiverem disponíveis.
diff --git a/docs/known-issues/pt/xml-url-on-the-admin-showing-wrong-link.md b/docs/known-issues/pt/xml-url-on-the-admin-showing-wrong-link.md
index f5ad903fc..45bbc112b 100644
--- a/docs/known-issues/pt/xml-url-on-the-admin-showing-wrong-link.md
+++ b/docs/known-issues/pt/xml-url-on-the-admin-showing-wrong-link.md
@@ -18,9 +18,7 @@ internalReference: 407528
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Às vezes podemos ver um link errado para o XML no XML admin (`/admin/Site/Xml.aspx`)
diff --git a/docs/known-issues/pt/xmlaspx-timeout.md b/docs/known-issues/pt/xmlaspx-timeout.md
index c9e39c2ea..5f0efcd15 100644
--- a/docs/known-issues/pt/xmlaspx-timeout.md
+++ b/docs/known-issues/pt/xmlaspx-timeout.md
@@ -18,9 +18,7 @@ internalReference: 384719
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 
diff --git a/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md b/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
index d91d5d9e0..ba5f18651 100644
--- a/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
+++ b/docs/known-issues/pt/xmls-product-name-flag-not-working-properly.md
@@ -18,9 +18,7 @@ internalReference: 925965
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Ao criar um XML, temos duas opções diferentes para definir o nome do produto, nos sinalizadores "Nome do produto" e "Nome do produto + Nome do SKU". No entanto, o sinalizador "Nome do produto" está sendo desconsiderado, e o nome do produto no arquivo segue a regra:
diff --git a/docs/known-issues/pt/xmls-returning-500-error.md b/docs/known-issues/pt/xmls-returning-500-error.md
index 032aa2e31..47eca57bc 100644
--- a/docs/known-issues/pt/xmls-returning-500-error.md
+++ b/docs/known-issues/pt/xmls-returning-500-error.md
@@ -18,9 +18,7 @@ internalReference: 268042
 
 ## Sumário
 
-<div class="alert alert-info">
-  <p>Este problema conhecido foi traduzido automaticamente do inglês.</p>
-</div>
+>ℹ️ Este problema conhecido foi traduzido automaticamente do inglês.
 
 
 Eventualmente, o XML pode retornar um erro 500, o que acontece principalmente em arquivos XML grandes.
diff --git a/docs/tracks/en/accounts-and-architecture.md b/docs/tracks/en/accounts-and-architecture.md
index 50ca9f68c..6940a1760 100644
--- a/docs/tracks/en/accounts-and-architecture.md
+++ b/docs/tracks/en/accounts-and-architecture.md
@@ -40,12 +40,17 @@ The following image is an overview to help you [choose between standard, franchi
 | Franchise account | <ul><li>Does not have its own frontend or website.</li><li>Has its own VTEX Admin environment to manage its operation.</li><li>Does not have its own catalog; instead, it follows the exact catalog structure of the main account.</li><li>Allows configuring prices and promotions.</li><li>Has its own warehouse and inventory.</li><li>The franchise account inventory can be sold on other VTEX marketplaces connected to the main account via <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI).</a></li></ul> |
 | Seller Portal account | <ul><li>Does not have its own frontend or website.</li><li>The main account has an area for <a href="https://help.vtex.com/en/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv"> managing sellers</a>, and each seller has its environment in the Seller Portal Admin.</li><li>The seller can configure inventory and pricing, manage products shared with the marketplace, invoice orders, activate promotions, process payments, and have their own logistics.</li></ul> |
 
-<div class="alert alert-info">
-<p><b>Marketplace on VTEX</p></b><p>Besides offering great flexibility in store architecture, our ecosystem allows each store to have multiple <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">marketplace strategies</a>, such as:</p><ul><li>Becoming a seller or marketplace for other VTEXstores.</li><li>Integrating with the big players such as <a href="https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> and <a href="https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP">Amazon</a>.</li>
-<li>Integrating with <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-marketplaces-partners">partner marketplaces</a> certified by VTEX.</li>
-<li>Being a marketplace for sellers with a <a href="https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK">Seller Portal</a> account.</li>
-<li>Being a <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a>.</li><li>Creating your own integrations with <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">external marketplaces and external sellers.</a></li></ul>
-</div>
+>ℹ️ **Marketplace on VTEX**
+> Besides offering great flexibility in store architecture, our ecosystem allows each store to have multiple [marketplace strategies](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402), such as:
+> *Becoming a seller or marketplace for other VTEXstores.
+> * Integrating with the big players such as [Mercado Libre](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) and [Amazon](https://help.vtex.com/en/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP).
+>
+> *Integrating with [partner marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-marketplaces-partners) certified by VTEX.
+>
+> *Being a marketplace for sellers with a [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) account.
+>
+> *Being a [white label seller](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
+> * Creating your own integrations with [external marketplaces and external sellers.](https://developers.vtex.com/docs/guides/external-seller-integration-guide)
 
 ## Store architecture
 
@@ -120,6 +125,4 @@ When building a store, it is common for agencies and [implementation partners](h
 
 The [VTEX Quadrant](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) is a program in which VTEX internally evaluates the performance and successful results of its partners' operations. This annual acknowledgment and reward is for those with the highest commitment and excellence. See the results of the 2022 Quadrant [here](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/). The VTEX Quadrant is an exclusive program for implementation partners in Brazil.
 
-<div class="alert alert-info">
-The <a href="https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/">VTEX Quadrant</a> is an exclusive program for implementation partners in Brazil.
-</div>
+>ℹ️ The [VTEX Quadrant](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) is an exclusive program for implementation partners in Brazil.
diff --git a/docs/tracks/en/add-an-image-to-the-sku.md b/docs/tracks/en/add-an-image-to-the-sku.md
index 35cc9925d..6dece7ca5 100644
--- a/docs/tracks/en/add-an-image-to-the-sku.md
+++ b/docs/tracks/en/add-an-image-to-the-sku.md
@@ -16,9 +16,7 @@ trackSlugEN: vtex-getting-started
 
 Every SKU needs to have at least one image to be displayed in the store.
 
-<div class="alert alert-warning">
-If no image is associated with an SKU, it will not be active.
-</div>
+>⚠️ If no image is associated with an SKU, it will not be active.
 
 Therefore, after you finish filling in the settings for your new SKU and click __Save__, you will be taken to the image registration screen, where the message below is displayed.
 
diff --git a/docs/tracks/en/add-on-products.md b/docs/tracks/en/add-on-products.md
index c736b94be..1d4245b61 100644
--- a/docs/tracks/en/add-on-products.md
+++ b/docs/tracks/en/add-on-products.md
@@ -16,9 +16,7 @@ trackSlugEN: next-steps-after-the-go-live
 
 Add-on products are solutions offered by VTEX to meet the specific business needs. They can be purchased separately through a subscription agreement.
 
-<div class="alert alert-warning">
-  <p>To implement the solutions below, contact our<a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ"> VTEX Sales Support</a>.</p>
-</div>
+>⚠️ To implement the solutions below, contact our[ VTEX Sales Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
 ## VTEX Ad Network
 
@@ -81,9 +79,7 @@ To watch an app demo or schedule a custom service with an expert, go to the[ VTE
 
 ## VTEX Shipping Network
 
-<div class="alert alert-warning">
-  <p>VTEX Shipping Network and VTEX Shipping Network Correios solutions are exclusive to Brazil.</p>
-</div>
+>⚠️ VTEX Shipping Network and VTEX Shipping Network Correios solutions are exclusive to Brazil.
 
 Explore options for shipping products to all regions of Brazil with [VTEX Shipping Network](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) and **VTEX Shipping Network Correios**.
 
diff --git a/docs/tracks/en/add-pickup-points.md b/docs/tracks/en/add-pickup-points.md
index 2c9190b17..8ef24686d 100644
--- a/docs/tracks/en/add-pickup-points.md
+++ b/docs/tracks/en/add-pickup-points.md
@@ -74,9 +74,7 @@ To upload a spreadsheet containing pickup points, follow the steps below:
 
 ## API REST
 
-<div class="alert alert-warning">
-Authentications for the Logisitics module API REST calls must be made using AppKey and AppToken. For more info, accesss our article on <a href="https://help.vtex.com/en/tutorial/create-appkey-and-apptoken-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2">how to create an Appkey and AppToken to authenticate your integrations</a>
-</div>
+>⚠️ Authentications for the Logisitics module API REST calls must be made using AppKey and AppToken. For more info, accesss our article on [how to create an Appkey and AppToken to authenticate your integrations](https://help.vtex.com/en/tutorial/create-appkey-and-apptoken-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2)
 
 To add a **Pickup Point** through API, you need to send a __POST__ to the following endpoint:
 
diff --git a/docs/tracks/en/add-sku-specifications.md b/docs/tracks/en/add-sku-specifications.md
index 971666048..3758e3331 100644
--- a/docs/tracks/en/add-sku-specifications.md
+++ b/docs/tracks/en/add-sku-specifications.md
@@ -16,9 +16,7 @@ trackSlugEN: catalog-101
 
 There are currently three ways of adding SKU specifications: either through admin, spreadsheet or ERP.
 
-<div class="alert alert-warning">
-<p>In VTEX, specifications follow a logic of "inheritance", that is, when creating a specification at a higher category level, the specification will be presented at all category levels below it. Therefore, if you need to create a product or SKU specification that applies to only one category, it should be created at that category's level.</p>
-</div>
+>⚠️ In VTEX, specifications follow a logic of "inheritance", that is, when creating a specification at a higher category level, the specification will be presented at all category levels below it. Therefore, if you need to create a product or SKU specification that applies to only one category, it should be created at that category's level.
 
 Follow the steps highlighted below in order to add specifications:
 
diff --git a/docs/tracks/en/adding-a-loading-dock.md b/docs/tracks/en/adding-a-loading-dock.md
index 7602ad8c0..0b4508794 100644
--- a/docs/tracks/en/adding-a-loading-dock.md
+++ b/docs/tracks/en/adding-a-loading-dock.md
@@ -39,9 +39,7 @@ Follow the steps below to add a loading dock to your store:
 - _Associated carriers_: carriers served by this loading dock.
 - _Processing time_: time that will added to the delivery due to the step involving this loading dock. For example, a processing time of 2 days plus a loading dock processing time of 3 days plus the carrier's processing time of 1 day means the delivery will be done in 6 days. 
 
-<div class="alert alert-info">
-<strong>Warning</strong>: the processing time of a loading dock is independent of whether a carrier operates - or not - on weekends and holidays. Delivery time will always be the sum of inventory, carrier, and loading dock time.
-</div>
+>ℹ️ **Warning**: the processing time of a loading dock is independent of whether a carrier operates - or not - on weekends and holidays. Delivery time will always be the sum of inventory, carrier, and loading dock time.
 
 - _Time overhead_: value that will be used to choose the best dock for a specific delivery. This value is added to the delivery time calculation.
 - _Priority_: Value to settle loading dock selection stalemates. The higher a loading dock's priority, the more chances it has of being chosen. 
@@ -50,9 +48,7 @@ Follow the steps below to add a loading dock to your store:
 
 ## API REST
 
-<div class="alert alert-warning">
-Inventory & Shipping module API REST calls must be made using AppKey and AppToken. For more info, read our article on <a href="https://help.vtex.com/en/tutorial/how-to-generate-an-appkey-and-apptoken-to-integrations--43tQeyQJgAKGEuCqQKAOI2">how to generate an Appkey and um AppToken ti authenticate your integrations</a>
-</div>
+>⚠️ Inventory & Shipping module API REST calls must be made using AppKey and AppToken. For more info, read our article on [how to generate an Appkey and um AppToken ti authenticate your integrations](https://help.vtex.com/en/tutorial/how-to-generate-an-appkey-and-apptoken-to-integrations--43tQeyQJgAKGEuCqQKAOI2)
 
 To add a **loading dock** using API, your need to send a __POST__ to the following endpoint:
 
diff --git a/docs/tracks/en/adding-a-price-rule.md b/docs/tracks/en/adding-a-price-rule.md
index da3ccaf37..dfca6a4a5 100644
--- a/docs/tracks/en/adding-a-price-rule.md
+++ b/docs/tracks/en/adding-a-price-rule.md
@@ -35,9 +35,7 @@ Follow the steps below to add a price rule to your store:
 
 ## API REST
 
-<div class="alert alert-warning">
-Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">how to generate an AppKey and AppToken to authenticate integrations</a>
-</div>
+>⚠️ Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on [how to generate an AppKey and AppToken to authenticate integrations](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 To add a **price rule**, you need to send a __POST__ to the following endpoint:
 
diff --git a/docs/tracks/en/adding-a-sender.md b/docs/tracks/en/adding-a-sender.md
index 42206e308..db55b7d25 100644
--- a/docs/tracks/en/adding-a-sender.md
+++ b/docs/tracks/en/adding-a-sender.md
@@ -42,8 +42,6 @@ Once that is done, go back to the Admin settings page and check the "This is the
 
 Whenever you deem it necessary, you can test if email sending is working by accessing the Senders section and clicking on the __Test__ button on the card with the desired sender.
 
-<div class="alert alert-warning">
-Warning: Whenever you make a change to the sender and save it, an email confirming that the SMTP was successfully registered will be sent to the address you entered. In all cases, it is essential to click on the link received in the email to complete the confirmation.
-</div>
+>⚠️ Warning: Whenever you make a change to the sender and save it, an email confirming that the SMTP was successfully registered will be sent to the address you entered. In all cases, it is essential to click on the link received in the email to complete the confirmation.
   
 
diff --git a/docs/tracks/en/adding-collections-track.md b/docs/tracks/en/adding-collections-track.md
index 7617e5ff6..20dd32ca0 100644
--- a/docs/tracks/en/adding-collections-track.md
+++ b/docs/tracks/en/adding-collections-track.md
@@ -14,9 +14,7 @@ trackId: 5AF0XfnjfWeopIFBgs3LIQ
 trackSlugEN: catalog-101
 ---
 
-<div class="alert alert-warning">
-  <p>Before creating a collection, you must configure the authorization by having a role with the <b>Write Collections</b> feature enabled in the <b>Collections</b> section of the Catalog profiles. Find out more <a href="https://help.vtex.com/en/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc">here</a>.</p>
-</div>
+>⚠️ Before creating a collection, you must configure the authorization by having a role with the **Write Collections** feature enabled in the **Collections** section of the Catalog profiles. Find out more [here](https://help.vtex.com/en/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc).
 
 Follow the step by step below to add a new collection:
 
diff --git a/docs/tracks/en/adding-extra-text-to-the-order-print.md b/docs/tracks/en/adding-extra-text-to-the-order-print.md
index bad208411..59ad09289 100644
--- a/docs/tracks/en/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/en/adding-extra-text-to-the-order-print.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: Adding extra text to the order print
 ---
 
-<div class="alert alert-danger">
-The configuration of extra text added to the order printout, explained in this article, involves changing the JavaScript file <code>checkout-instore-custom.js</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ The configuration of extra text added to the order printout, explained in this article, involves changing the JavaScript file `checkout-instore-custom.js`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 By default, the order summary print does not contain any custom text. If you want to add extra text to the order print, it is necessary to edit the file `checkout-instore-custom.js`.
 
@@ -28,9 +26,7 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionalities.
-</div>
+>❗ Do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionalities.
 
 After reloading inStore, whenever a salesperson prints an order, this text will appear on the printout.
 
diff --git a/docs/tracks/en/adding-holidays.md b/docs/tracks/en/adding-holidays.md
index e8a4c6f6a..9ce548cfe 100644
--- a/docs/tracks/en/adding-holidays.md
+++ b/docs/tracks/en/adding-holidays.md
@@ -28,9 +28,7 @@ To configure holidays, follow the step-by-step below:
 4. Fill in the holiday's start date (in __Date__) as well as its __end date__. 
 5. Click on __Salvar__.
 
-<div class="alert alert-warning">
-  Holidays will only be considered for carriers having the "Carrier <strong>does not deliver</strong> on weekends" option enabled.
-</div>
+>⚠️ Holidays will only be considered for carriers having the "Carrier **does not deliver** on weekends" option enabled.
 
 To enable a carrier's holiday feature, follow these steps:
 
@@ -41,9 +39,7 @@ To enable a carrier's holiday feature, follow these steps:
 5. Enable the __Carrier does not deliver on weekends__ options (either by clicking on the word "delivery" in "carrier delivery on weekends, thereby becoming "carrier does  not deliver on weekends", or by leaving it as it is in case the option already appears).
 6. Click on __Save__.
 
-<div class="alert alert-info">
-You can set future holidays in advance, creating a Christmas holiday for the next few years for example.
-</div>
+>ℹ️ You can set future holidays in advance, creating a Christmas holiday for the next few years for example.
 
 ## How the estimated shipping date is calculated
 
diff --git a/docs/tracks/en/adding-product-specifications.md b/docs/tracks/en/adding-product-specifications.md
index 6269e5059..0532c2e81 100644
--- a/docs/tracks/en/adding-product-specifications.md
+++ b/docs/tracks/en/adding-product-specifications.md
@@ -16,9 +16,7 @@ trackSlugEN: catalog-101
 
 There are three ways of adding product specifications: via Admin, spreadsheet, or API.
 
-<div class="alert alert-warning">
-<p>In VTEX, specifications follow a logic of "inheritance", that is, when creating a specification at a higher category level, the specification will be presented at all category levels below it. Therefore, if you need to create a product or SKU specification that applies to only one category, it should be created at that category's level.</p>
-</div>
+>⚠️ In VTEX, specifications follow a logic of "inheritance", that is, when creating a specification at a higher category level, the specification will be presented at all category levels below it. Therefore, if you need to create a product or SKU specification that applies to only one category, it should be created at that category's level.
 
 Follow the steps highlighted below to add specifications:
 
diff --git a/docs/tracks/en/adding-products.md b/docs/tracks/en/adding-products.md
index 77348df09..431810e31 100644
--- a/docs/tracks/en/adding-products.md
+++ b/docs/tracks/en/adding-products.md
@@ -40,6 +40,4 @@ We recommend that you add products and SKUs together when using a spreadsheet. Y
 
 To add a new product via API use the [Create Product](https://developers.vtex.com/vtex-rest-api/reference/post-product) request. 
 
-<div class="alert alert-info">
-If your product does not appear on your store's website after you have created it, check out the article <a href="https://help.vtex.com/pt/faq/why-is-the-product-not-shown-on-the-website--frequentlyAskedQuestions_382">Why is the product not shown on the website?</a> to understand how to solve this problem.
-</div>
+>ℹ️ If your product does not appear on your store's website after you have created it, check out the article [Why is the product not shown on the website?](https://help.vtex.com/pt/faq/why-is-the-product-not-shown-on-the-website--frequentlyAskedQuestions_382) to understand how to solve this problem.
diff --git a/docs/tracks/en/adding-skus.md b/docs/tracks/en/adding-skus.md
index dbef58c40..9326cdd72 100644
--- a/docs/tracks/en/adding-skus.md
+++ b/docs/tracks/en/adding-skus.md
@@ -70,9 +70,7 @@ After adding the images, you must add the SKU specifications. The next step on t
 9. Click on `Apply and close`.
 10. Lastly, click on `Save`, which you will find scrolling down the page.
 
-<div class="alert alert-danger">
-Before saving the configurations, make sure that all SKU mandatory information is filled out. Otherwise, the SKU will not be linked to the product.
-</div>
+>❗ Before saving the configurations, make sure that all SKU mandatory information is filled out. Otherwise, the SKU will not be linked to the product.
 
 ## Spreadsheet
 
diff --git a/docs/tracks/en/adding-the-magazine-luiza-integration.md b/docs/tracks/en/adding-the-magazine-luiza-integration.md
index cf02ac4da..b5b26ac79 100644
--- a/docs/tracks/en/adding-the-magazine-luiza-integration.md
+++ b/docs/tracks/en/adding-the-magazine-luiza-integration.md
@@ -24,8 +24,7 @@ The integration with Magazine Luiza happens through IntegraCommerce, an integrat
 
 With this integration, it will be possible to __create new accounts__ and also __migrate existing accounts (soon)__ in Magazine Luiza. The step-by-step below is suitable for both cases.
 
-<div class="alert alert-warning">
-<strong>Note:</strong> Currently <strong>you can not migrate old accounts</strong>. We are working on that and soon this migration will be done automatically.</div>
+>⚠️ **Note:** Currently **you can not migrate old accounts**. We are working on that and soon this migration will be done automatically.
 
 
 ## Detailing the fields
diff --git a/docs/tracks/en/adding-vendors.md b/docs/tracks/en/adding-vendors.md
index 85cbacdb5..aacb55ef5 100644
--- a/docs/tracks/en/adding-vendors.md
+++ b/docs/tracks/en/adding-vendors.md
@@ -35,6 +35,4 @@ After registering the vendor in VTEX admin, he or she will need to log in to you
 To create a password for this vendor, enter your account's __admin__: https://{{AccountName}}.myvtex.com/admin and then follow this article: https://help.vtex.com/en/faq/how-to-retrieve-the-access-password
 __If you try to create the password in the e-commerce website rather than in the admin, inStore login won't work.__
 
-<div class="alert alert-warning">
-<strong>Important</strong>: besides setting up the vendor in VTable, you must create the user in the Admin, linking him or her to the <b>inStore Sales Person</b> access profile.
-</div>
+>⚠️ **Important**: besides setting up the vendor in VTable, you must create the user in the Admin, linking him or her to the **inStore Sales Person** access profile.
diff --git a/docs/tracks/en/adding-warehouses.md b/docs/tracks/en/adding-warehouses.md
index 38c565312..9ee8e3e20 100644
--- a/docs/tracks/en/adding-warehouses.md
+++ b/docs/tracks/en/adding-warehouses.md
@@ -39,9 +39,7 @@ Follow the steps below to add a warehouse to your store:
 
 ## API REST
 
-<div class="alert alert-warning">
-Inventory & Shipping module API REST call authentications must be done with AppKey and AppToken. For more info, access our article on <a href="https://help.vtex.com/en/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2">how to create an AppKey and AppToken to authenticate your integrations.</a>
-</div>
+>⚠️ Inventory & Shipping module API REST call authentications must be done with AppKey and AppToken. For more info, access our article on [how to create an AppKey and AppToken to authenticate your integrations.](https://help.vtex.com/en/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2)
 
 To add a **warehouse** using API, you'll need to send a __POST__ to the following endpoint:
 
diff --git a/docs/tracks/en/amazon-account-settings.md b/docs/tracks/en/amazon-account-settings.md
index 9cc22ae1c..32c8e21a6 100644
--- a/docs/tracks/en/amazon-account-settings.md
+++ b/docs/tracks/en/amazon-account-settings.md
@@ -32,6 +32,4 @@ After creating your seller account, you will need to authorize VTEX in your Amaz
 
 After completing the authorization, you will be redirected to the VTEX Admin, and the integration step will be completed.  
 
-<div class="alert alert-info">
-If you have questions about this, please <a href="https://sellercentral.amazon.com/learn/courses?ref_=su_course_accordion&moduleId=1f61fcd3[…]-ed90359ff166&modLanguage=Portuguese&videoPlayer=youtube">refer to Amazon Seller Central documentation.</a>
-</div>
+>ℹ️ If you have questions about this, please [refer to Amazon Seller Central documentation.](https://sellercentral.amazon.com/learn/courses?ref_=su_course_accordion&moduleId=1f61fcd3[…]-ed90359ff166&modLanguage=Portuguese&videoPlayer=youtube)
diff --git a/docs/tracks/en/apple-pay.md b/docs/tracks/en/apple-pay.md
index 0518dded9..b06f7d943 100644
--- a/docs/tracks/en/apple-pay.md
+++ b/docs/tracks/en/apple-pay.md
@@ -19,9 +19,7 @@ Your customers can shop using Apple Pay, the [digital wallet](https://help.vtex.
 - Have an account in `developer.apple.com`.
 - Hire a provider that processes payments with Apple Pay.
 
-<div class="alert alert-warning">
-  Apple Pay currently only works on MacOs, IOS operating systems, and the Safari browser. For more information, go to <a href="https://support.apple.com/en-gb/HT208531">Devices compatible with Apple Pay</a>.
-</div>
+>⚠️ Apple Pay currently only works on MacOs, IOS operating systems, and the Safari browser. For more information, go to [Devices compatible with Apple Pay](https://support.apple.com/en-gb/HT208531).
 
 ## Setting up the payment provider
 
@@ -29,9 +27,7 @@ Firstly, you need to configure a provider in your store's Admin that processes t
 
 To check all the provider options available for this payment method, access the list as described in Step 5 of the section [Set up payment with Apple Pay](#setting-up-payment-with-apple-pay).
 
-<div class="alert alert-warning">
-  Before starting to configure the provider, you must <a href="register your Merchant ID with Apple Pay">register your Merchant ID with Apple Pay</a>.
-</div>
+>⚠️ Before starting to configure the provider, you must [register your Merchant ID with Apple Pay](register your Merchant ID with Apple Pay).
 
 ## Setting up payment with Apple Pay
 
diff --git a/docs/tracks/en/authenticating-your-google-shopping-account.md b/docs/tracks/en/authenticating-your-google-shopping-account.md
index f6b31ea7b..bf034f00b 100644
--- a/docs/tracks/en/authenticating-your-google-shopping-account.md
+++ b/docs/tracks/en/authenticating-your-google-shopping-account.md
@@ -24,6 +24,4 @@ After configuring the integration, you must authenticate your Google Shopping ac
 6. Click on the `Authenticate my account` button.
 7. Click `OK` to authorize the VTEX integration to connect with the ID Business Manager profile.
 
-<div class="alert alert-info">
-There may be a delay between completing the integration and the moment it goes live because the update is not synchronous.  But it takes no more than a few hours.
-</div>
+>ℹ️ There may be a delay between completing the integration and the moment it goes live because the update is not synchronous.  But it takes no more than a few hours.
diff --git a/docs/tracks/en/backend-integrations.md b/docs/tracks/en/backend-integrations.md
index 15f83c4d6..bd5ed55b9 100644
--- a/docs/tracks/en/backend-integrations.md
+++ b/docs/tracks/en/backend-integrations.md
@@ -131,9 +131,7 @@ After understanding and planning the store's [catalog architecture](https://help
 2. **Catalog API:** Create each category by making API calls. For more details, see [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category).
 3. **Back-office integration:** Import categories from an external back-office software (ERP or PIM) integrated with VTEX. The software may already offer native integration with VTEX or require the development of middleware that uses the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview). See [Category migration from ERP](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#category-migration-from-erps) for more details.
 
-<div class="alert alert-warning">
-When importing categories from external software, the category structure in the software may differ from that of VTEX. In this case, we recommend creating an inactive "mock" category. This category will remain invisible on the storefront and serve as a temporary repository to receive all products and SKUs during the import process. Once the import is complete, you can manually organize the products within the VTEX Admin to match the desired category tree.
-</div>
+>⚠️ When importing categories from external software, the category structure in the software may differ from that of VTEX. In this case, we recommend creating an inactive "mock" category. This category will remain invisible on the storefront and serve as a temporary repository to receive all products and SKUs during the import process. Once the import is complete, you can manually organize the products within the VTEX Admin to match the desired category tree.
 
 There are some limitations to be aware of when managing categories:
 
@@ -150,9 +148,7 @@ For more information about importing categories into the back office, check the
 2. **Catalog API:** Create each brand by making API calls. Learn more in [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand).
 3. **Back-office integration:** Import brands from an external back-office software (ERP or PIM) integrated with VTEX. The software may already offer native integration with VTEX or may require the development of middleware that uses the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Learn more in [Creating Brands in the Catalog configuration guide for back-office](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-brands).
 
-<div class="alert alert-warning">
-If the back-office system has no brand information, you can apply the same approach as mentioned previously for category migration by creating an inactive "mock" brand to be used exclusively for migration purposes. Subsequently, product information can then be manually entered.
-</div>
+>⚠️ If the back-office system has no brand information, you can apply the same approach as mentioned previously for category migration by creating an inactive "mock" brand to be used exclusively for migration purposes. Subsequently, product information can then be manually entered.
 
 For more information on importing brands into the back office, check the [Brands](https://developers.vtex.com/docs/guides/brands) article.
 
@@ -203,9 +199,7 @@ You should import products in the order shown in the table below:
 
 <br>
 
-<div class="alert alert-warning">
-The product information in the ERP is often not suitable for use and display in the ecommerce store. For this reason, the information will need to undergo an enhancement process. This can include restructuring categories and creating more descriptive and appealing product descriptions.
-</div>
+>⚠️ The product information in the ERP is often not suitable for use and display in the ecommerce store. For this reason, the information will need to undergo an enhancement process. This can include restructuring categories and creating more descriptive and appealing product descriptions.
 
 After the import, it's also important to ensure that product and SKU information is kept up to date. You can check the instructions in the [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information) article.
 
diff --git a/docs/tracks/en/basic-vtex-io-developer-setup.md b/docs/tracks/en/basic-vtex-io-developer-setup.md
index bf18a7d29..124325ccc 100644
--- a/docs/tracks/en/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/en/basic-vtex-io-developer-setup.md
@@ -40,9 +40,7 @@ When you are logged in, you can use the `vtex whoami` command to find out which
 
 ![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
-<div class="alert alert-info">
-PROTIP: You can configure your terminal to display your current account and workspace automatically. The easiest way to do it is to use our <a href="https://github.com/vtex/dotfiles">dotfiles</a>, which automatically configure <a href="https://fishshell.com/">Fish Shell</a> and add a <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">prompt function</a> for you.
-</div>
+>ℹ️ PROTIP: You can configure your terminal to display your current account and workspace automatically. The easiest way to do it is to use our [dotfiles](https://github.com/vtex/dotfiles), which automatically configure [Fish Shell](https://fishshell.com/) and add a [prompt function](https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish) for you.
 
 ## Workspaces: your isolated development environment
 
@@ -66,9 +64,7 @@ $ vtex use yourname
 
 This switches your toolbelt to a workspace called `yourname`, and creates it if it doesn’t exist. 
 
-<div class="alert alert-info">
-TIP: You can switch to <em>and reset</em> a workspace to master in a single command with the <code>-r</code> flag. This is useful if you want to start fresh from <code>master</code>.
-</div>
+>ℹ️ TIP: You can switch to *and reset* a workspace to master in a single command with the `-r` flag. This is useful if you want to start fresh from `master`.
 
 Workspaces can be named arbitrarily, but we find it’s usually convenient to name it after yourself when you want to develop something in your own environment.
 
diff --git a/docs/tracks/en/cadastrar-preco-base.md b/docs/tracks/en/cadastrar-preco-base.md
index cc4252675..8eed6494c 100644
--- a/docs/tracks/en/cadastrar-preco-base.md
+++ b/docs/tracks/en/cadastrar-preco-base.md
@@ -40,9 +40,7 @@ You may also add a **List Price** linked to an SKU base price by following the s
 
 ## API REST
 
-<div class="alert alert-warning">
-Authentications for the Prices module's API REST requests must be done using AppKey and AppToken. For more on this, read our article on <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">how to manage an AppKey and AppToken to authenticate your integrations.</a>
-</div>
+>⚠️ Authentications for the Prices module's API REST requests must be done using AppKey and AppToken. For more on this, read our article on [how to manage an AppKey and AppToken to authenticate your integrations.](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 To add a **base price** to an SKU, you'll have to send a __PUT__ request to the following endpoint:
 
diff --git a/docs/tracks/en/cadastrar-tabelas-de-preco.md b/docs/tracks/en/cadastrar-tabelas-de-preco.md
index 3fc4880c0..587673b89 100644
--- a/docs/tracks/en/cadastrar-tabelas-de-preco.md
+++ b/docs/tracks/en/cadastrar-tabelas-de-preco.md
@@ -31,9 +31,7 @@ Follow the steps below to add a price table in your store:
 
 ## API REST
 
-<div class="alert alert-warning">
-Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">how to generate an AppKey and AppToken to authenticate integrations</a>
-</div>
+>⚠️ Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on [how to generate an AppKey and AppToken to authenticate integrations](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 To add a **price table**, you need to send a __PUT__ to the following endpoint:
 
diff --git a/docs/tracks/en/cadastrar-trava-de-preco.md b/docs/tracks/en/cadastrar-trava-de-preco.md
index 47244ec42..7c39fa24d 100644
--- a/docs/tracks/en/cadastrar-trava-de-preco.md
+++ b/docs/tracks/en/cadastrar-trava-de-preco.md
@@ -31,9 +31,7 @@ Follow the steps below to add a price variation limiter:
 
 ## API REST
 
-<div class="alert alert-warning">
-Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">how to generate an AppKey and AppToken to authenticate integrations</a>
-</div>
+>⚠️ Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on [how to generate an AppKey and AppToken to authenticate integrations](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 To add a **price variation limiter**, you need to send a __POST__ to the following endpoint:
 
diff --git a/docs/tracks/en/canceling-an-order.md b/docs/tracks/en/canceling-an-order.md
index cd93e9dfe..8366884b5 100644
--- a/docs/tracks/en/canceling-an-order.md
+++ b/docs/tracks/en/canceling-an-order.md
@@ -19,9 +19,7 @@ You can cancel an order with VTEX in three different ways:
 - Through API.
 - Following the customer's request.
 
-<div class="alert alert-warning">
-Once an order is canceled, you cannot change its status. Orders that have <b>invoiced</b> status can not be canceled.
-</div>
+>⚠️ Once an order is canceled, you cannot change its status. Orders that have **invoiced** status can not be canceled.
 
 <div class = "alert alert-info">
 Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
diff --git a/docs/tracks/en/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md b/docs/tracks/en/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
index d89294de2..80191343e 100644
--- a/docs/tracks/en/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
+++ b/docs/tracks/en/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/categories-concept-definition.md b/docs/tracks/en/categories-concept-definition.md
index bd45fc31e..a352049fc 100644
--- a/docs/tracks/en/categories-concept-definition.md
+++ b/docs/tracks/en/categories-concept-definition.md
@@ -20,9 +20,7 @@ The three main category levels are called __Department__, __Category__, and __Su
 
 Categories are also where you need to configure the Specifications (or Fields), that represent the properties you will add to the products or SKUs. We will have a closer look at the relationship between categories, products, SKUs and specifications during the next steps.
 
-<div class="alert alert-info"> 
-We suggest that your store’s category trees have no more than three levels of hierarchy. This will allow your customers to browse your store with more ease. 
-</div>
+>ℹ️ We suggest that your store’s category trees have no more than three levels of hierarchy. This will allow your customers to browse your store with more ease.
 
 ## Department
 
@@ -34,9 +32,7 @@ It is the highest level within the categories tree. More specific categories sho
 
 The category tree’s second hierarchy level is called __Category__. This level is under the __Department__ level and above the __Subcategory__ level.
 
-<div class="alert alert-info">
-The term "category" is typically used to refer to a generic segmentation concept. At VTEX, the term "Category" is also used to refer to the category tree’s second hierarchy level.
-</div>
+>ℹ️ The term "category" is typically used to refer to a generic segmentation concept. At VTEX, the term "Category" is also used to refer to the category tree’s second hierarchy level.
 
 ## Subcategory 
 
diff --git a/docs/tracks/en/changing-the-instore-language.md b/docs/tracks/en/changing-the-instore-language.md
index 5ca03c9c0..b48ea4e83 100644
--- a/docs/tracks/en/changing-the-instore-language.md
+++ b/docs/tracks/en/changing-the-instore-language.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: changing-the-instore-language
 ---
 
-<div class="alert alert-danger">
-The language change explained in this article involves altering the JavaScript file <code>checkout-instore-custom.js</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ The language change explained in this article involves altering the JavaScript file `checkout-instore-custom.js`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 Currently, it is possible to use the inStore in __Portuguese__, __English__, or __Spanish__.
 
diff --git a/docs/tracks/en/cms-folder-structure.md b/docs/tracks/en/cms-folder-structure.md
index 9cb44638c..a4c4f092d 100644
--- a/docs/tracks/en/cms-folder-structure.md
+++ b/docs/tracks/en/cms-folder-structure.md
@@ -39,9 +39,7 @@ See below these basic folders in the CMS:
 
 These folders come by default in the environment of all VTEX stores.
 
-<div class="alert alert-danger">
-The names of the required folders must <b>not</b> be edited.
-</div>
+>❗ The names of the required folders must **not** be edited.
 
 Since folders refer to dynamic pages, their names don't appear on the customer's navigation. In other words, the fact that editing the names is banned does not affect the final text of your URLs, nor the internationalization of your site.
 
@@ -58,9 +56,7 @@ These are:
 
 For these two folders, what matters is the control or placeholder that reads their content. Their names can be freely edited.
 
-<div class="alert alert-warning">
-Since they are private folders, <code>/account</code> and <code>/account/orders</code> <b>must require authentication</b>. See <a href="http://help.vtex.com/en/tutorial/requering-authentication-on-store-pages">in this article</a> how to ensure they are configured to ask for user authentication.
-</div>
+>⚠️ Since they are private folders, `/account` and `/account/orders` **must require authentication**. See [in this article](http://help.vtex.com/en/tutorial/requering-authentication-on-store-pages) how to ensure they are configured to ask for user authentication.
 
 
 ## Useful folders
diff --git a/docs/tracks/en/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md b/docs/tracks/en/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
index 623accbd9..57c286f0f 100644
--- a/docs/tracks/en/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
+++ b/docs/tracks/en/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/como-funciona-o-adaptador-vtex.md b/docs/tracks/en/como-funciona-o-adaptador-vtex.md
index f427742b9..ec01dc471 100644
--- a/docs/tracks/en/como-funciona-o-adaptador-vtex.md
+++ b/docs/tracks/en/como-funciona-o-adaptador-vtex.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugEN: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md b/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md
index 0f4c5e398..569c1f967 100644
--- a/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md
+++ b/docs/tracks/en/configuracao-da-estrutura-para-suporte-humano.md
@@ -21,9 +21,7 @@ There are two pre-integrated partner options with VTEX Conversational Commerce:
 * [Zenvia](#zenvia-integration)
 * [Zendesk](#zendesk-integration)
 
-<div class="alert alert-info">
-  <p>Get in touch with the VTEX development team if you want to integrate with other platforms.</p>
-</div>
+>ℹ️ Get in touch with the VTEX development team if you want to integrate with other platforms.
 
 ## Zenvia Integration
 
diff --git a/docs/tracks/en/configurar-adaptador.md b/docs/tracks/en/configurar-adaptador.md
index 2c88532c4..14c405358 100644
--- a/docs/tracks/en/configurar-adaptador.md
+++ b/docs/tracks/en/configurar-adaptador.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugEN: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/configurar-erps.md b/docs/tracks/en/configurar-erps.md
index bc5110433..b28b9c92d 100644
--- a/docs/tracks/en/configurar-erps.md
+++ b/docs/tracks/en/configurar-erps.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugEN: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/configure-clustered-conditions.md b/docs/tracks/en/configure-clustered-conditions.md
index 28dce5532..7644ed7f4 100644
--- a/docs/tracks/en/configure-clustered-conditions.md
+++ b/docs/tracks/en/configure-clustered-conditions.md
@@ -16,17 +16,13 @@ trackSlugEN: clustered-payment-conditions
 
 As mentioned, Clustered Payment Conditions establish that a payment condition will apply to one or more customers. 
 
-<div class="alert alert-warning">
-Previously configured payment conditions can apply to customer clusters. 
-
-It means that you can edit existing payment conditions and apply clustering conditions to these rules.
-</div>
+>⚠️ Previously configured payment conditions can apply to customer clusters. 
+>
+> It means that you can edit existing payment conditions and apply clustering conditions to these rules.
 
 Let’s take a look at how we should configure an exclusive payment condition for clusters.
 
-<div class="alert alert-danger">
-<strong>Warning</strong>: you can only create five client clusters for each payment condition.
-</div>  
+>❗ **Warning**: you can only create five client clusters for each payment condition.  
 
 You can create a new payment condition by applying the clustering conditions. To do so, go to Admin > Payments > Settings > Payment Conditions.
 
diff --git a/docs/tracks/en/configure-integration.md b/docs/tracks/en/configure-integration.md
index 04db9a220..9db05e684 100644
--- a/docs/tracks/en/configure-integration.md
+++ b/docs/tracks/en/configure-integration.md
@@ -14,4 +14,4 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugEN: magazine-luiza-integration-set-up
 ---
 
-<div class="alert alert-warning">This is a regional exclusive content not applicable to English speaking countries.</div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tracks/en/configuring-banners.md b/docs/tracks/en/configuring-banners.md
index 1a804e4ef..5d3c1a57a 100644
--- a/docs/tracks/en/configuring-banners.md
+++ b/docs/tracks/en/configuring-banners.md
@@ -24,9 +24,7 @@ To set up a banner, follow the steps below:
 
 After configuring the banner, you have to add it to a page on your store. To do that, follow the steps described in the [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner) guide.
 
-<div class="alert alert-info">
-<p> This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: Multilanguage settings (Beta)</a>.</p>
-</div>
+>ℹ️ This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article [VTEX Intelligent Search: Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners).
 
 ![banner-form-en](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
 
diff --git a/docs/tracks/en/configuring-merchandising-rules.md b/docs/tracks/en/configuring-merchandising-rules.md
index 16790e8f3..f3240c828 100644
--- a/docs/tracks/en/configuring-merchandising-rules.md
+++ b/docs/tracks/en/configuring-merchandising-rules.md
@@ -32,9 +32,7 @@ Follow the steps below to configure a [merchandising rule](https://help.vtex.com
    Add one or more conditions to apply the desired customization effect in this step. To learn how to add a condition, see [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
 10. Click `Save`.
 
-<div class="alert alert-info">
-  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
-</div>
+>ℹ️ After saving, the changes to merchandising rules will take an average of two minutes to be updated.
 
 ## Example
 
@@ -74,18 +72,12 @@ Imagine the following example: You want to promote Beautyx products during the 4
 
 * **Remove**: Deletes the selected conditions from the result, so it removes products that would be displayed in the search results.
 
-  <div class="alert alert-info">
-  <p><strong>Add</strong> and <strong>Remove</strong> are compatible with other sorting types, not based on the configured relevance. So, suppose you add or remove a product using a merchandising rule, and the customer sorts the search results by price. In that case, the products will be sorted by price, and the products displayed will follow the merchandising rule.</p>
-  </div>
+  >ℹ️ **Add** and **Remove** are compatible with other sorting types, not based on the configured relevance. So, suppose you add or remove a product using a merchandising rule, and the customer sorts the search results by price. In that case, the products will be sorted by price, and the products displayed will follow the merchandising rule.
 
 * **Promote**: Highlights selected conditions in the result, giving more relevance to a product normally displayed in the search results. The order of the conditions affects the priority in which they are displayed. Besides, a product added to this field is only promoted in one result.
 
 * **Demote**: Hides the selected conditions in the result. This allows you to deprioritize a product normally displayed in the search results.
 
-  <div class="alert alert-info">
-  <p><strong>Promote</strong> and <strong>Demote</strong> only work when your customers sort the search results by relevance. If they sort it by price, the products will be sorted strictly by price, and the merchandising rule will not be applied.</p>
-  </div>
+  >ℹ️ **Promote** and **Demote** only work when your customers sort the search results by relevance. If they sort it by price, the products will be sorted strictly by price, and the merchandising rule will not be applied.
 
-  <div class="alert alert-warning">
-  <p>Do not set conditions that will affect the same products in the <strong>Promote</strong> and <strong>Demote</strong> sections, since these are opposite effects. This misconfiguration negatively influences the feature's behavior and does not produce the desired results.</p>
-  </div>
+  >⚠️ Do not set conditions that will affect the same products in the **Promote** and **Demote** sections, since these are opposite effects. This misconfiguration negatively influences the feature's behavior and does not produce the desired results.
diff --git a/docs/tracks/en/configuring-payment-connectors.md b/docs/tracks/en/configuring-payment-connectors.md
index cc305f4a0..c1217b58d 100644
--- a/docs/tracks/en/configuring-payment-connectors.md
+++ b/docs/tracks/en/configuring-payment-connectors.md
@@ -18,9 +18,7 @@ The __Payments__ module allows several payment providers (gateways, acquirers, s
 
 When a purchase is made in your store and the customer makes payment, data transmission between VTEX and the chosen provider occurs through communication protocols configured in the VTEX Admin.
 
-<div class="alert alert-info">
-  To check which payment providers are available in your region and the respective settings articles, visit <a href="https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp">List of payment providers by country</a>.</p>
-</div>
+>ℹ️ To check which payment providers are available in your region and the respective settings articles, visit [List of payment providers by country](https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp).</p>
 
 Below is an example of how to set up a payment provider:
 
diff --git a/docs/tracks/en/configuring-price-divergence-rule-amazon.md b/docs/tracks/en/configuring-price-divergence-rule-amazon.md
index 1968b9433..88e89ce78 100644
--- a/docs/tracks/en/configuring-price-divergence-rule-amazon.md
+++ b/docs/tracks/en/configuring-price-divergence-rule-amazon.md
@@ -20,8 +20,6 @@ In the VTEX Admin, in **ORDERS > Orders management > Orders authorization**, you
 
 The Price Divergence rule is composed of one or more authorization rules, each corresponding to a percentage range of the order price. Authorization rules can be configured to automatically deny, automatically approve, or require manual approval of the order.
 
-<div class="alert alert-warning">
-Once the price divergence rule is created, it is applied to all marketplaces where you act as a seller. These can be VTEX marketplaces, external marketplaces, <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner">certified connectors (partners)</a>, and other <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a> besides Amazon.
-</div>
+>⚠️ Once the price divergence rule is created, it is applied to all marketplaces where you act as a seller. These can be VTEX marketplaces, external marketplaces, <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner">certified connectors (partners)</a>, and other <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a> besides Amazon.
 
 We recommend that you configure the Price Divergence rule before proceeding to the next step of configuring the Amazon integration. Not following this recommendation does not prevent the integration from being configured; however, orders with divergent prices are held until the Price Divergence rule is created. You can track them in the VTEX Admin by clicking on **MARKETPLACE > Integrations > Orders**.
diff --git a/docs/tracks/en/configuring-price-divergence-rule-via.md b/docs/tracks/en/configuring-price-divergence-rule-via.md
index 575aa2404..07bfc1615 100644
--- a/docs/tracks/en/configuring-price-divergence-rule-via.md
+++ b/docs/tracks/en/configuring-price-divergence-rule-via.md
@@ -20,8 +20,6 @@ In the VTEX Admin, in **ORDERS > Orders management > Orders authorization**, you
 
 The Price Divergence rule is composed of one or more authorization rules, each corresponding to a percentage range of the order price. Authorization rules can be configured to automatically deny, automatically approve, or require manual approval of the order.
 
-<div class="alert alert-warning">
-Once the price divergence rule is created, it is applied to all marketplaces where you act as a seller. These can be VTEX marketplaces, external marketplaces, <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner">certified connectors (partners)</a>, and other <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a> besides Via.
-</div>
+>⚠️ Once the price divergence rule is created, it is applied to all marketplaces where you act as a seller. These can be VTEX marketplaces, external marketplaces, <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner">certified connectors (partners)</a>, and other <a href= "https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a> besides Via.
 
 We recommend that you configure the Price Divergence rule before proceeding to the next step of configuring the Via integration. Not following this recommendation does not prevent the integration from being configured; however, orders with divergent prices are held until the Price Divergence rule is created. You can track them in the VTEX Admin by clicking on **MARKETPLACE > Integrations > Orders**.
diff --git a/docs/tracks/en/configuring-ship-from-store.md b/docs/tracks/en/configuring-ship-from-store.md
index b969423a8..0574c95b2 100644
--- a/docs/tracks/en/configuring-ship-from-store.md
+++ b/docs/tracks/en/configuring-ship-from-store.md
@@ -28,9 +28,7 @@ First of all, you must consider the prerequisites that your store needs to ensur
 
 ## How to implement Ship From Store
 
-<div class="alert alert-info">
-Although it is possible to implement Ship From Store in other ways, in this article we will explain how to do it using the Franchise Account and Seller White Label features. This is the architecture most recommended by VTEX for this type of project.
-</div>
+>ℹ️ Although it is possible to implement Ship From Store in other ways, in this article we will explain how to do it using the Franchise Account and Seller White Label features. This is the architecture most recommended by VTEX for this type of project.
 
 These are the steps to implement __Ship From Store__:
 
diff --git a/docs/tracks/en/configuring-synonyms.md b/docs/tracks/en/configuring-synonyms.md
index 8890a00d0..9c4698cfe 100644
--- a/docs/tracks/en/configuring-synonyms.md
+++ b/docs/tracks/en/configuring-synonyms.md
@@ -40,9 +40,7 @@ Follow the step-by-step procedure to configure synonyms individually in the VTEX
 
 Changes can take up to two hours to take effect.
 
-<div class="alert alert-info">
-<p> This feature is available on VTEX Intelligent Search Multilanguage. Read our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#synonyms">VTEX Intelligent Search: Multilanguage settings (Beta)</a>to learn more.</p>
-</div>
+>ℹ️ This feature is available on VTEX Intelligent Search Multilanguage. Read our article [VTEX Intelligent Search: Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#synonyms)to learn more.
 
 ## Importing CSV spreadsheet
 
@@ -89,7 +87,5 @@ Stores using  [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/
     __Example:__
     - `tv,smart tv;true;en-GB`: When searching for one of these terms in the store in English (`locale en-GB`), the search results will return any product that contains one of these terms.
 
-<div class="alert alert-warning">
-  <p>If the imported .csv file does not have the <code>locale</code>, the synonym will be valid for all languages available in the store.</p>
-</div>
+>⚠️ If the imported .csv file does not have the `locale`, the synonym will be valid for all languages available in the store.
 
diff --git a/docs/tracks/en/configuring-the-amazon-integration.md b/docs/tracks/en/configuring-the-amazon-integration.md
index 8ac43dca3..6f54caaca 100644
--- a/docs/tracks/en/configuring-the-amazon-integration.md
+++ b/docs/tracks/en/configuring-the-amazon-integration.md
@@ -34,9 +34,7 @@ Once you have configured your VTEX store and your Amazon account, you must confi
 - __Not send price to Amazon:__ Amazon allows you to use their own system to parameterize product prices. To use this service, toggle the *ON* option so that the integration does not submit VTEX prices. If prices are sent through the integration, they will overwrite the ones in Amazon's system.
 - **Send KIT*:** if you click *No*, SKUs [registered as kits](https://help.vtex.com/en/tutorial/cadastrando-kit--tutorials_215) will not be sent to Amazon. By clicking Yes, all items in your trade policy will be sent to the marketplace, including SKUs created as kits. Changes to the connector configuration can be made at any time. This does not affect SKUs that have already been sent. For example, if you changed the setting from *Yes* to *No*, SKUs previously sent to Amazon would not be deleted or modified.
 
-<div class="alert alert-info">
-  If the <i>No</i> option is enabled, attempts to send SKUs registered as kits to Amazon will result in the following warning: "The connector is configured not to send SKUs of the Kit type". This message can be viewed in the Admin, in <b>Marketplace > Integrations > Products</b>, when you click on the SKU.
-</div>
+>ℹ️ If the <i>No</i> option is enabled, attempts to send SKUs registered as kits to Amazon will result in the following warning: "The connector is configured not to send SKUs of the Kit type". This message can be viewed in the Admin, in **Marketplace > Integrations > Products**, when you click on the SKU.
 
 - **Notify by email if an error occurs in an order:** enter the email address of the responsible technician. If any error occurs when integrating an order, a message will be sent to this email address.
 
diff --git a/docs/tracks/en/configuring-the-google-shopping-integration.md b/docs/tracks/en/configuring-the-google-shopping-integration.md
index 9ff92b434..5be8e0cb3 100644
--- a/docs/tracks/en/configuring-the-google-shopping-integration.md
+++ b/docs/tracks/en/configuring-the-google-shopping-integration.md
@@ -16,9 +16,7 @@ trackSlugEN: integrating-with-google-shopping
 
 Check out how to integrate your store with Google Shopping using the connector developed by VTEX. It should be your standard choice, as it provides more efficiency and security.
 
-<div class="alert alert-danger">
-The integration can be performed via <a href="https://help.vtex.com/en/tutorial/configurando-xml--tutorials_242">XML</a> . We do not recommend integrating with <a href="https://help.vtex.com/en/tutorial/como-configurar-xml-do-google-shopping--frequentlyAskedQuestions_372">Google Shopping using an XML file</a> and the native connector simultaneously, because this might lead to conflicting information and data discrepancy.
-</div>
+>❗ The integration can be performed via [XML](https://help.vtex.com/en/tutorial/configurando-xml--tutorials_242) . We do not recommend integrating with [Google Shopping using an XML file](https://help.vtex.com/en/tutorial/como-configurar-xml-do-google-shopping--frequentlyAskedQuestions_372) and the native connector simultaneously, because this might lead to conflicting information and data discrepancy.
 
 To integrate using the connector, **you must have a Google Merchant Center account.**  If you don't have one, check out the tutorial [sign up for Google Merchant Center](https://support.google.com/merchants/answer/188924?hl=en&ref_topic=7294166).
 
diff --git a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 15b5b18b5..eeb0e6674 100644
--- a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -33,9 +33,7 @@ Regardless of whether you have installed the <a href= "https://apps.vtex.com/vte
 8. Click on `Continue`.
 9. Choose which permissions must be granted to VTEX for the integration.
 
-  <div class="alert alert-danger">
-For the integration to work properly, we recommended that you grant all the permissions shown. By default, they are set as enabled.
-</div>
+  >❗ For the integration to work properly, we recommended that you grant all the permissions shown. By default, they are set as enabled.
 
 10. Click on `Next`.
 11. In the pop-up window, a confirmation that the integration has been configured will be displayed. Click on `Done`.
diff --git a/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index a172c25a3..549c694f3 100644
--- a/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -42,9 +42,7 @@ In this part of the form, you need to fill in information that will be used to i
 
 * **Trade policy:** a field to select the trade policy to be associated with a catalog integrated with TikTok. Currently, the integration only accepts trade policies with BRL as currency. See the [Sending product data to TikTok](#sending-product-data-to-tiktok) section for more information.
 
-<div class="alert alert-warning">
-<p>Do not change the affiliate configuration created automatically through this integration. Any future manual changes to the affiliate's configuration in <strong>Orders management > Settings > Affiliates</strong> may cause the integration to stop working.</p>
-</div>
+>⚠️ Do not change the affiliate configuration created automatically through this integration. Any future manual changes to the affiliate's configuration in **Orders management > Settings > Affiliates** may cause the integration to stop working.
 
 ### Company data
 
@@ -76,9 +74,7 @@ After completing the integration configuration form, you need to connect your Ti
 
 ## 3. Configuring TikTok for Business
 
-<div class="alert alert-warning">
-<p>We recommend disabling the extensions that block ads in your browser to avoid errors in the following steps.</p>
-</div>
+>⚠️ We recommend disabling the extensions that block ads in your browser to avoid errors in the following steps.
 
 On the **Set Up TikTok for Business page**, as illustrated below, please follow the configuration instructions described next.
 
@@ -105,9 +101,7 @@ When you complete this setting, you will be redirected back to **Marketplace > T
 
 ### Sending product data to TikTok
 
-<div class="alert alert-warning">
-  <p>TikTok only syncs products that comply with the platform's advertising policies. Read <a href="https://ads.tiktok.com/help/article?aid=9550&lang=pt">TikTok Advertising Policies</a> for more information.</p>
-</div>
+>⚠️ TikTok only syncs products that comply with the platform's advertising policies. Read [TikTok Advertising Policies](https://ads.tiktok.com/help/article?aid=9550&lang=pt) for more information.
 
 Once the integration is configured, sending products to TikTok will be an automatic process. The following data will be submitted:
 
diff --git a/docs/tracks/en/create-a-product.md b/docs/tracks/en/create-a-product.md
index 88de8b371..f1c9e12f9 100644
--- a/docs/tracks/en/create-a-product.md
+++ b/docs/tracks/en/create-a-product.md
@@ -16,13 +16,9 @@ trackSlugEN: vtex-getting-started
 
 Before anything else, it's important to understand the difference between SKU and product. This difference concerns the VTEX platform, but also the way most of e-commerce operations treat these concepts.
 
-<div class="alert alert-info">
-<strong>SKU:</strong> the smallest possible unit of items sold in the store. Stock and price, for example, are SKU properties.
-</div>
+>ℹ️ **SKU:** the smallest possible unit of items sold in the store. Stock and price, for example, are SKU properties.
 
-<div class="alert alert-info">
-<strong>Product:</strong> SKUs aggregator.
-</div>
+>ℹ️ **Product:** SKUs aggregator.
 
 See the following examples:
 
@@ -34,9 +30,7 @@ See the following examples:
 In the shop window, the customer will see only the product __Jeans__, not three separate SKUs: "Jeans S", "Jeans M" and "Jeans L".
 The management of your inventory sees each of the SKUs that make up this product separately. So it can know, for example, that you have 50 Jeans M in stock, but only 2 Jeans L.
 
-<div class="alert alert-info">
-<strong>Atention</strong>: Whenever you create an SKU, you need to create the product first.
-</div>
+>ℹ️ **Atention**: Whenever you create an SKU, you need to create the product first.
 
 Let's see how to create the product.
 
diff --git a/docs/tracks/en/create-an-account.md b/docs/tracks/en/create-an-account.md
index 2cccafbdc..f12e46c69 100644
--- a/docs/tracks/en/create-an-account.md
+++ b/docs/tracks/en/create-an-account.md
@@ -18,8 +18,6 @@ After hiring VTEX, the store receives its account. This account identifies the s
 
 To develop apps using VTEX IO, you must first have access to a store account. 
 
-<div class="alert alert-info">
-Every app created with VTEX IO is developed in the context of a VTEX account.
-</div>
+>ℹ️ Every app created with VTEX IO is developed in the context of a VTEX account.
 
 If you don't have access to any account yet and need to create one, contact VTEX sales team and then read the article on how to [link your account name to a website](/en/tutorial/linking-an-account-name-to-a-website-binding).
diff --git a/docs/tracks/en/create-an-sku.md b/docs/tracks/en/create-an-sku.md
index 26bcf4dc5..42be21532 100644
--- a/docs/tracks/en/create-an-sku.md
+++ b/docs/tracks/en/create-an-sku.md
@@ -33,6 +33,4 @@ You will be taken to the SKU registration screen.
 
 All fields available on this screen are listed in the article [SKU registration fields](/en/tutorial/sku-registration-fields).
 
-<div class="alert alert-info">
-Sometimes a product does not have variations that justify the creation of more than one SKU for it. In this case, there is no problem creating an SKU with the same product name. Just remember that you always need to create <strong>at least one SKU for each product</strong>.
-</div>
+>ℹ️ Sometimes a product does not have variations that justify the creation of more than one SKU for it. In this case, there is no problem creating an SKU with the same product name. Just remember that you always need to create **at least one SKU for each product**.
diff --git a/docs/tracks/en/create-the-category-tree.md b/docs/tracks/en/create-the-category-tree.md
index 7456fa3d9..4d7571141 100644
--- a/docs/tracks/en/create-the-category-tree.md
+++ b/docs/tracks/en/create-the-category-tree.md
@@ -22,9 +22,7 @@ So that's where we need to get started.
 
 # What is a category tree?
 
-<div class="alert alert-info">
-The category tree is the set of categories for your site, <strong>distributed according to hierarchy relationships</strong>.
-</div>
+>ℹ️ The category tree is the set of categories for your site, **distributed according to hierarchy relationships**.
 
 ## Example
 
@@ -44,15 +42,11 @@ __Note__: The names __Department__, __Category__ and __Subcategory__ are just a
 
 But attention:
 
-<div class="alert alert-info">
-We recommend creating <strong>a maximum of 3 category levels</strong>. More levels can make your catalog operation too complex.
-</div>
+>ℹ️ We recommend creating **a maximum of 3 category levels**. More levels can make your catalog operation too complex.
 
 Two key points:
 
 - Who plans the distribution of the categories of your site? __You! This planning should reflect the goals of your business.__
 - When should the distribution of the categories be defined? __Before any category is actually created in the site.__
 
-<div class="alert alert-warning">
-It's very important that your team define the composition of the <strong>category tree before</strong> you create it on the platform. Once you start inserting products, having to move categories may become quite a headache.
-</div>
+>⚠️ It's very important that your team define the composition of the **category tree before** you create it on the platform. Once you start inserting products, having to move categories may become quite a headache.
diff --git a/docs/tracks/en/creating-accounts.md b/docs/tracks/en/creating-accounts.md
index 78d739039..c3b08e376 100644
--- a/docs/tracks/en/creating-accounts.md
+++ b/docs/tracks/en/creating-accounts.md
@@ -20,9 +20,7 @@ The next step is to create accounts for the customers you want to offer credit t
 - [Multiple Accounts (Admin VTEX)](#create-multiple-accounts-bulk-import)
 - [Individual account (Customer Credit API)](#criar-conta-via-api)
 
-<div class="alert alert-info">
-Accounts created in the Customer Credit app have no relationship or share data with the customer base registered in the store's <a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#data-entities">Master Data entities</a>. For a customer to be able to use Customer Credit as a payment method, their account must be registered by the merchant in the app even if the customer already has an account in the store. 
-</div>
+>ℹ️ Accounts created in the Customer Credit app have no relationship or share data with the customer base registered in the store's [Master Data entities](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#data-entities). For a customer to be able to use Customer Credit as a payment method, their account must be registered by the merchant in the app even if the customer already has an account in the store.
 
 ## Create accounts individually
 
@@ -34,9 +32,7 @@ To register a new customer in Customer Credit, follow the steps below:
 4. In __Credit__, enter the __Credit Limit (BRL)__ and __Tolerance__ values that you want to make available to the customer.
 5. Click `Confirm`.
 
-<div class="alert alert-warning">
-Filling in the <b>Email</b> field is mandatory, as the VTEX platform uses this information to authenticate the customer's access to the credit limits of their account. For more information about data protection, visit <a href="https://help.vtex.com/en/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB">SmartCheckout Security</a>.
-</div>
+>⚠️ Filling in the **Email** field is mandatory, as the VTEX platform uses this information to authenticate the customer's access to the credit limits of their account. For more information about data protection, visit [SmartCheckout Security](https://help.vtex.com/en/tutorial/smartcheckout-security--3SrJuuhrqwePUg1rp1exfB).
 
 From this moment on, the new account created will be displayed on the __Accounts__ screen.
 
@@ -71,9 +67,7 @@ To create multiple accounts at the same time (in bulk) in Customer Credit, you c
 
 From this moment on, new accounts created via the .csv spreadsheet will be available on the __Accounts__ screen.
 
-<div class="alert alert-warning">
-It is also possible to track previous processes of creating multiple accounts, identifying whether the accounts were created correctly. To check this information, click on <b>Import History</b> on the <b>Accounts</b> screen.
-</div>  
+>⚠️ It is also possible to track previous processes of creating multiple accounts, identifying whether the accounts were created correctly. To check this information, click on **Import History** on the **Accounts** screen.  
 
 ### Update multiple accounts (bulk import)
 
diff --git a/docs/tracks/en/creating-and-editing-users.md b/docs/tracks/en/creating-and-editing-users.md
index 4fd4cf7e0..4311f5ac8 100644
--- a/docs/tracks/en/creating-and-editing-users.md
+++ b/docs/tracks/en/creating-and-editing-users.md
@@ -46,6 +46,4 @@ You cannot change the email. To do this, it is necessary to make a new registrat
 2. Select the desired user and click on the **trash can** icon in the Actions column.
 3. Click on **confirm**.
 
-<div class="alert alert-info">
-Although integration tokens de integração are listed as users, they cannot be excluded. To disable them, navigate to <em>Account settings > Account management > Account</em> in your Admin panel and uncheck the <strong>Token Status</strong> field.
-</div>
+>ℹ️ Although integration tokens de integração are listed as users, they cannot be excluded. To disable them, navigate to *Account settings > Account management > Account* in your Admin panel and uncheck the **Token Status** field.
diff --git a/docs/tracks/en/creating-discount-coupons.md b/docs/tracks/en/creating-discount-coupons.md
index ba27aadd1..79d1a6d17 100644
--- a/docs/tracks/en/creating-discount-coupons.md
+++ b/docs/tracks/en/creating-discount-coupons.md
@@ -37,9 +37,9 @@ To create a discount coupon, follow the steps below:
 6. Click on **Restrictions and limitations of use** and set the number of products that can be purchased using this coupon, regardless of how many purchases are made to reach that number.
 7. Click on **Save**.
 
-<div class="alert alert-info">
-It is not necessary to create an <code>utm_source</code> and an <code>utm_campaign</code>, but it is necessary to create <b>at least one</b> of them.<br>
-Read the article <a href="https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii">What are utm_source, utm_campaign, and utm_medium</a> to better understand what these UTMs are.
-</div>
+>ℹ️ It is not necessary to create an `utm_source` and an `utm_campaign`, but it is necessary to create **at least one** of them.
+>
+> 
+> Read the article [What are utm_source, utm_campaign, and utm_medium](https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) to better understand what these UTMs are.
 
 When creating a regular promotion, you must select the `utm_source` and/or the `utm_campaign` boxes and insert the UTMs informed during the creation of the coupon in the corresponding fields.
diff --git a/docs/tracks/en/creating-franchise-accounts.md b/docs/tracks/en/creating-franchise-accounts.md
index 5dd3811f6..a6938908b 100644
--- a/docs/tracks/en/creating-franchise-accounts.md
+++ b/docs/tracks/en/creating-franchise-accounts.md
@@ -24,9 +24,7 @@ When you create a franchise account, each one of your physical stores will have
 
 Your franchise accounts will function as [White Label Sellers](https://help.vtex.com/en/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa#what-is-a-seller-white-label). This means that whenever an order is placed through any channel, be it VTEX Sales App or ecommerce, the system will search for the store with the best [SLA](https://help.vtex.com/en/tutorial/what-the-platform-s-operation-sla-is--2cIFrsY5S8usk84OU4QOKm) delivery.
 
-<div class="alert alert-warning">
-  <p>Each seller must have a different company registration number for order payments to work correctly.</p>
-</div>
+>⚠️ Each seller must have a different company registration number for order payments to work correctly.
 
 You can manage the logistics for each franchise account using a separate VTEX Admin. To access it, use the URL `{name-of-franchise-account}.myvtex.com/admin URL`.
 
diff --git a/docs/tracks/en/creating-merchandising-rules-visual-editor.md b/docs/tracks/en/creating-merchandising-rules-visual-editor.md
index 7927b064f..5d120efb1 100644
--- a/docs/tracks/en/creating-merchandising-rules-visual-editor.md
+++ b/docs/tracks/en/creating-merchandising-rules-visual-editor.md
@@ -43,9 +43,7 @@ To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.co
       Learn more about these actions in items **IV, V, VI, VIII, IX**, and **XI** of the [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section.
 9.	Click `Save`.
 
-<div class="alert alert-info">
-  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
-</div>
+>ℹ️ After saving, the changes to merchandising rules will take an average of two minutes to be updated.
 
 ## Actions available in the Visual Editor
 
diff --git a/docs/tracks/en/creating-or-editing-a-page-template.md b/docs/tracks/en/creating-or-editing-a-page-template.md
index 54bb7013d..43712863c 100644
--- a/docs/tracks/en/creating-or-editing-a-page-template.md
+++ b/docs/tracks/en/creating-or-editing-a-page-template.md
@@ -32,15 +32,16 @@ Check out the walk-through:
 4. Click on __HTML Templates __.
 5. Just below, click on __New template__.
 6. Fill in the __Template Name__ field.
-<div class="alert alert-danger">
-  <p>When filling in the <b>Template Name</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ When filling in the **Template Name**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 7. Then fill in the __Template XHTML__ box with your template code. 
 ![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 9. Click on the __Save Template__ button.
diff --git a/docs/tracks/en/creating-regular-promotions.md b/docs/tracks/en/creating-regular-promotions.md
index 8d1f10fb1..a13eeeb1d 100644
--- a/docs/tracks/en/creating-regular-promotions.md
+++ b/docs/tracks/en/creating-regular-promotions.md
@@ -134,9 +134,7 @@ By default, you can add up to 20 payment methods per promotion. You can also cus
 </div>
 
 - **Number of installments:** Discount given if the number of installments selected by the customer is within the specified range. This field does not apply to boletos (Brazilian payment method).
-<div class="alert alert-warning">
-Promotions based on payment method and number of installments do not apply to orders paid for with two cards or vouchers.
-</div>
+>⚠️ Promotions based on payment method and number of installments do not apply to orders paid for with two cards or vouchers.
 
 - **UTM source:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion. Note that the customer can only enter one **utm_source** at checkout.
 - **UTM campaign:** The discount will apply if the customer navigation uses an utm_source parameter corresponding to a listed one in this promotion.
diff --git a/docs/tracks/en/credit-card-payment-flow.md b/docs/tracks/en/credit-card-payment-flow.md
index 22c0c148c..4bde5f170 100644
--- a/docs/tracks/en/credit-card-payment-flow.md
+++ b/docs/tracks/en/credit-card-payment-flow.md
@@ -42,7 +42,5 @@ The complete credit card payment flow at VTEX is shown in the following scheme:
 
 Upon the issuing bank's response, the reverse flow is performed and the **Payment Gateway** receives information whether the payment has been approved or denied.
 
-<div class="alert alert-info">
-It is possible to include Anti-fraud in this flow. In this case, the anti-fraud receives from the gateway the information that the payment has been pre-authorized by the issuing bank. With the information received from the gateway, the anti-fraud sends a payment approval or denial response. If the anti-fraud denies, the payment is canceled. If the payment is approved, the order can proceed its normal flow.
-</div>
+>ℹ️ It is possible to include Anti-fraud in this flow. In this case, the anti-fraud receives from the gateway the information that the payment has been pre-authorized by the issuing bank. With the information received from the gateway, the anti-fraud sends a payment approval or denial response. If the anti-fraud denies, the payment is canceled. If the payment is approved, the order can proceed its normal flow.
 
diff --git a/docs/tracks/en/cubic-size-shipping-factor-and-dimensional-weight-calculations.md b/docs/tracks/en/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
index 7f2eaf08e..da5be4e17 100644
--- a/docs/tracks/en/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
+++ b/docs/tracks/en/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
@@ -44,8 +44,6 @@ Example:
 
 For the example above, when comparing the package's net weight with its DIM weight, the carrier will charge for the real weight, since it's more than the DIM weight.
 
-<div class="alert alert-warning">
-Check your carrier's measurement unit, to see whether it's in grams and centimeters or pounds and inches. 
-</div>
+>⚠️ Check your carrier's measurement unit, to see whether it's in grams and centimeters or pounds and inches.
 
 When adding your carrier, this is the value that you need to fill into the Shipping Factor field. 
diff --git a/docs/tracks/en/customer-identification.md b/docs/tracks/en/customer-identification.md
index acae9fce8..da812f3ff 100644
--- a/docs/tracks/en/customer-identification.md
+++ b/docs/tracks/en/customer-identification.md
@@ -33,7 +33,5 @@ Just enter one of these data in the field and click on the `Confirm` button.
 
 Alternatively, if you have enabled the Anonymous User feature, it is possible to proceed without identifying the customer. To do this, just click on `Proceed without identification`.
 
-<div class="alert alert-info">
-Although it is possible to cater customers without identifying them, we always recommend doing so, as this gives the sales associate a series of contextual information that increases the chances of conversion.
-</div>
+>ℹ️ Although it is possible to cater customers without identifying them, we always recommend doing so, as this gives the sales associate a series of contextual information that increases the chances of conversion.
 
diff --git a/docs/tracks/en/customizing-instore.md b/docs/tracks/en/customizing-instore.md
index fc27853da..cd5e62c59 100644
--- a/docs/tracks/en/customizing-instore.md
+++ b/docs/tracks/en/customizing-instore.md
@@ -18,9 +18,7 @@ The VTEX Sales App experience is customizable: you can enable specific features
 
 This requires editing JavaScript and CSS files, as described in the [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app) developer guide.
 
-<div class="alert alert-warning">
-<p>Only people with programming experience should customize VTEX Sales App as incorrect changes to these files can cause critical errors.</p>
-</div>
+>⚠️ Only people with programming experience should customize VTEX Sales App as incorrect changes to these files can cause critical errors.
 
 You can see the available VTEX Sales App customizations below. You can click the name of each customization to access its respective implementation guide.
 
diff --git a/docs/tracks/en/customizing-instores-layout.md b/docs/tracks/en/customizing-instores-layout.md
index de7b76931..3420ed46c 100644
--- a/docs/tracks/en/customizing-instores-layout.md
+++ b/docs/tracks/en/customizing-instores-layout.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: customizing-instores-layout
 ---
 
-<div class="alert alert-danger">
-Customizing the inStore layout, as explained in this article, involves changing the CSS file <code>checkout-instore-custom.css</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ Customizing the inStore layout, as explained in this article, involves changing the CSS file `checkout-instore-custom.css`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 Through the VTEX administrative panel, the store has access to the editable CSS file that defines the styles of the inStore app. Therefore, it is possible to customize these styles.
 
diff --git a/docs/tracks/en/data-protection-roles.md b/docs/tracks/en/data-protection-roles.md
index 082007f96..febda3f96 100644
--- a/docs/tracks/en/data-protection-roles.md
+++ b/docs/tracks/en/data-protection-roles.md
@@ -48,9 +48,7 @@ VTEX does not use end-customer data for any purpose other than to perform ecomme
 
 The DPA used must correspond to the specific region of the data subject (store customer).
 
-<div class="alert alert-warning">
-  <p>Check the<a href="https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/"> Data Processing Addendum - VTEX</a> to view the standard VTEX DPA for each region.</p>
-</div>
+>⚠️ Check the[ Data Processing Addendum - VTEX](https://vtex.com/us-en/privacy-and-agreements/data-processing-addendum/) to view the standard VTEX DPA for each region.
 
 ## Shared responsibilities
 
diff --git a/docs/tracks/en/define-payment-methods-displayed-on-instore.md b/docs/tracks/en/define-payment-methods-displayed-on-instore.md
index fda337427..76da63d53 100644
--- a/docs/tracks/en/define-payment-methods-displayed-on-instore.md
+++ b/docs/tracks/en/define-payment-methods-displayed-on-instore.md
@@ -18,6 +18,4 @@ Once the payment condition has been created, you must create the filters that de
 
 To do this, your store developers must customize a JavaScript file. For more information, please refer to the guide [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/docs/guides/define-payment-methods-displayed-on-vtex-sales-app).
 
-<div class="alert alert-danger">
-<p>To enable payment conditions via the VTEX Sales App app, you must make changes to a JavaScript file. This operation must only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.</p>
-</div>
+>❗ To enable payment conditions via the VTEX Sales App app, you must make changes to a JavaScript file. This operation must only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
diff --git a/docs/tracks/en/defining-the-google-shopping-trade-policy.md b/docs/tracks/en/defining-the-google-shopping-trade-policy.md
index 5dc3d6023..f6bd9b2c8 100644
--- a/docs/tracks/en/defining-the-google-shopping-trade-policy.md
+++ b/docs/tracks/en/defining-the-google-shopping-trade-policy.md
@@ -53,10 +53,6 @@ To configure a discount linked to a payment method, see the following documentat
 
 After following these instructions, you should activate the connector by [configuring the connector](https://help.vtex.com/en/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
 
-<div class="alert alert-warning">
-  When multiple sellers are linked to a product in your store, the rule for Google Shopping is to offer the best discount available.
-  </div>
+>⚠️ When multiple sellers are linked to a product in your store, the rule for Google Shopping is to offer the best discount available.
 
- <div class="alert alert-danger">
-  Each promotion created can belinked to only one payment method for the discount to be sent to Google Shopping.
-  </div> 
+ >❗ Each promotion created can belinked to only one payment method for the discount to be sent to Google Shopping. 
diff --git a/docs/tracks/en/detaching-skus-by-specification.md b/docs/tracks/en/detaching-skus-by-specification.md
index 175f22bae..b397a2ca8 100644
--- a/docs/tracks/en/detaching-skus-by-specification.md
+++ b/docs/tracks/en/detaching-skus-by-specification.md
@@ -26,8 +26,7 @@ See the following example of detaching SKUs by color. In the image below, the fe
 
 ![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
-<div class="alert alert-info"><p>
-If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.</p></div>
+>ℹ️ If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.
 
 ## Configuration
 To configure which attributes will be used to detach SKUs, see our [Search Settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#) article.
diff --git a/docs/tracks/en/enable-clustered-payment-conditions.md b/docs/tracks/en/enable-clustered-payment-conditions.md
index 2db7a3032..1e09d0d49 100644
--- a/docs/tracks/en/enable-clustered-payment-conditions.md
+++ b/docs/tracks/en/enable-clustered-payment-conditions.md
@@ -22,10 +22,8 @@ The second step is to configure the Clustered Payment Conditions in your store.
 
 ## Enable Customer Credit
 
-<div class="alert alert-info">
-If Customer Credit is already installed and configured, jump to 
-"Enable Clustered Payment Conditions".
-</div>
+>ℹ️ If Customer Credit is already installed and configured, jump to 
+> "Enable Clustered Payment Conditions".
 
 ### 1. Installing the app
 
@@ -41,9 +39,7 @@ There are some [basic settings](https://help.vtex.com/en/tracks/customer-credit-
 
 ## Enable Clustered Payment Conditions in your store
 
-<div class="alert alert-warning">
-This functionality is currently in Closed Beta (testing stage) and is not available for installation in new stores.        
-</div>  
+>⚠️ This functionality is currently in Closed Beta (testing stage) and is not available for installation in new stores.  
 
 Now that your store uses Customer Credit, you can enable Clustered Payment Conditions. Contact our support team, open a [ticket](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM "ticket") and ask for the feature to be enabled in your store.
 
diff --git a/docs/tracks/en/enabling-2-factor-authentication-login.md b/docs/tracks/en/enabling-2-factor-authentication-login.md
index 5ac510e52..14f8fc207 100644
--- a/docs/tracks/en/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/en/enabling-2-factor-authentication-login.md
@@ -34,13 +34,9 @@ There are two authentication options:
 
 ![2FA - Select - EN](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
 
-<div class="alert alert-warning">
-  We recommend you to use a<a href="#enabling-2fa-por-aplicativo">authentication application</a> to prevent failures in your telephone provider from making your login impossible. Though the app, the access key will always be available for use.
-</div>
+>⚠️ We recommend you to use a[authentication application](#enabling-2fa-por-aplicativo) to prevent failures in your telephone provider from making your login impossible. Though the app, the access key will always be available for use.
 
-<div class="alert alert-info">
-As some companies restrict the use of cell phones by telesales operators, users with the <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator" target="_blank"> telesales role</a> do not have to enable the 2FA when logging in with email and password.
-</div>
+>ℹ️ As some companies restrict the use of cell phones by telesales operators, users with the [ telesales role](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator" target="_blank) do not have to enable the 2FA when logging in with email and password.
 
 ## Enabling the 2FA through an app
 
@@ -60,9 +56,7 @@ To use a key generated by authentication application:
 
   ![2FA - App Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
 
-<div class="alert alert-info">
-If you log in using your email and password on the same computer, you will be asked for your access key every 3 days. When this happens, check the code in the application.
-</div>.
+>ℹ️ If you log in using your email and password on the same computer, you will be asked for your access key every 3 days. When this happens, check the code in the application..
 
 ## Enabling 2FA via SMS
 
@@ -76,9 +70,7 @@ To use a key sent by text message:
 
    ![2FA - SMS Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
 
- <div class="alert alert-warning">
-We cannot guarantee that your telephone company will be able to deliver the access key whenever necessary. If the VTEX text message does not arrive, try resending the code or <a href="#enabling-2fa-through-an-app" >enable the 2FA per-application</a>.
-</div>
+ >⚠️ We cannot guarantee that your telephone company will be able to deliver the access key whenever necessary. If the VTEX text message does not arrive, try resending the code or <a href="#enabling-2fa-through-an-app" >enable the 2FA per-application</a>.
 
 ## Change 2FA settings
 
diff --git a/docs/tracks/en/enabling-a-sales-rep-code.md b/docs/tracks/en/enabling-a-sales-rep-code.md
index 1b9af7ed6..729fd9031 100644
--- a/docs/tracks/en/enabling-a-sales-rep-code.md
+++ b/docs/tracks/en/enabling-a-sales-rep-code.md
@@ -20,21 +20,15 @@ One possible customization offered by inStore is to change the [Observation](htt
 
 Once this customization is enabled, the `Vendor` field will be displayed at the top of the page, and a new step will be added to the purchase flow. The sales rep must identify the order with their code before proceeding to Shipping.
 
-<div class="alert alert-danger">
-<strong>Warning</strong>: In this case, you cannot complete a sale without entering the sales rep code in the <code>Vendor</code> field.
-</div>
+>❗ **Warning**: In this case, you cannot complete a sale without entering the sales rep code in the `Vendor` field.
 
 ## Editing the JavaScript file
 
 To enable the sales rep code, you must edit the JavaScript code `checkout-instore-custom.js` saved on the VTEX Admin dashboard.
 
-<div class="alert alert-warning">
-It is <strong>expressly recommended</strong> that the person responsible for editing the code has <strong>experience with programming</strong>.
-</div>  
+>⚠️ It is **expressly recommended** that the person responsible for editing the code has **experience with programming**.  
 
-<div class="alert alert-info">
-The sales rep code can <strong>only</strong> be enabled via JavaScript.
-</div>
+>ℹ️ The sales rep code can **only** be enabled via JavaScript.
 
 First, customize the file as described in the article [Enabling the remarks field in the order screen](https://help.vtex.com/en/tracks/instore-customizacoes--1z9kBm12oBPyVNDo1ivVc2/8Aj21R8bll0tdrxHWjVOs).
 
@@ -56,9 +50,7 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Do not delete any other property of the <code>window.INSTORE_CONFIG</code> object. Otherwise, this action will possibly affect other features of your store. Also, please note that the code above is only one example of several configuration possibilities.
-</div>
+>❗ Do not delete any other property of the `window.INSTORE_CONFIG` object. Otherwise, this action will possibly affect other features of your store. Also, please note that the code above is only one example of several configuration possibilities.
 
 The properties of the `window.INSTORE_CONFIG` object must be filled in according to how the customization is expected to work for the store.
 
diff --git a/docs/tracks/en/enabling-cart-transfer-between-devices.md b/docs/tracks/en/enabling-cart-transfer-between-devices.md
index b42e2f905..13e38b36f 100644
--- a/docs/tracks/en/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/en/enabling-cart-transfer-between-devices.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: enabling-cart-transfer-between-devices
 ---
 
-<div class="alert alert-danger">
-The feature that lets you enable Cart Transfer, explained in this article, involves changing the JavaScript file <code>checkout-instore-custom.js</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ The feature that lets you enable Cart Transfer, explained in this article, involves changing the JavaScript file `checkout-instore-custom.js`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 The __Cart Transfer__ functionality of the inStore allows a purchase initiated on one device to be completed on any other device present in the purchase flow, without the need to re-beep the products.
 
diff --git a/docs/tracks/en/enabling-order-filter-by-salesperson.md b/docs/tracks/en/enabling-order-filter-by-salesperson.md
index f20ce4a92..244e2caf3 100644
--- a/docs/tracks/en/enabling-order-filter-by-salesperson.md
+++ b/docs/tracks/en/enabling-order-filter-by-salesperson.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: enabling-order-filter-by-salesperson
 ---
 
-<div class="alert alert-danger">
-Changing the filter settings, as explained in this article, involves editing the <code>checkout-instore-custom.js</code> file. This operation should only be performed by people with programming experience. Incorrect changes to this file may cause critical errors.
-</div>
+>❗ Changing the filter settings, as explained in this article, involves editing the `checkout-instore-custom.js` file. This operation should only be performed by people with programming experience. Incorrect changes to this file may cause critical errors.
 
 In inStore, you can see the list of all orders completed in a store. However, it sometimes makes sense for a salesperson to see only the orders they have personally completed. To enable this option, it is necessary to edit the file `checkout-instore-custom.js`.
 
@@ -33,8 +31,6 @@ window.INSTORE_CONFIG = {
 
 With that, the app filters orders to display only those made by the salesperson currently logged in inStore.
 
-<div class="alert alert-danger">
-Do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionalities.
-</div>
+>❗ Do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionalities.
 
 After reloading the datain the inStore app, by clicking on the __Reset app local data__ button, the seller will see only the orders closed by him or her.
diff --git a/docs/tracks/en/enabling-product-recommendations.md b/docs/tracks/en/enabling-product-recommendations.md
index aa03e371c..86b1d5d77 100644
--- a/docs/tracks/en/enabling-product-recommendations.md
+++ b/docs/tracks/en/enabling-product-recommendations.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: enabling-product-recommendations
 ---
 
-<div class="alert alert-danger">
-The enablement of the product recommendation settings in inStore, explained in this article, involves changing the <code>checkout-instore-custom.js</code> and <code>checkout-instore-custom.css</code> files. This operation should only be performed by people with programming experience. Incorrect changes to these files can cause critical errors.
-</div>
+>❗ The enablement of the product recommendation settings in inStore, explained in this article, involves changing the `checkout-instore-custom.js` and `checkout-instore-custom.css` files. This operation should only be performed by people with programming experience. Incorrect changes to these files can cause critical errors.
 
 By default, inStore shows a list of suggested products to the salesperson in two stages of the order:
 - In the cart
@@ -54,6 +52,4 @@ window.INSTORE_CONFIG = {
 
 Save the file with the change, then open the inStore app menu and update the data by clicking the __Reset app local data__ button. Once this is done, the salespeople will no longer see product recommendations.
 
-<div class="alert alert-danger">
-Do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionalities.
-</div>
+>❗ Do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionalities.
diff --git a/docs/tracks/en/enabling-the-remarks-field-in-the-order-screen.md b/docs/tracks/en/enabling-the-remarks-field-in-the-order-screen.md
index f3d4f46e9..a992d240c 100644
--- a/docs/tracks/en/enabling-the-remarks-field-in-the-order-screen.md
+++ b/docs/tracks/en/enabling-the-remarks-field-in-the-order-screen.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: enabling-the-remarks-field-in-the-order-screen
 ---
 
-<div class="alert alert-danger">
-The customization explained in this article involves changing the JavaScript file <code>checkout-instore-custom.js</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ The customization explained in this article involves changing the JavaScript file `checkout-instore-custom.js`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 The inStore app allows the use of a "Remarks" field, where it's possible to store additional information regarding the order.
 
@@ -45,9 +43,7 @@ window.LOCALE_MESSAGES = {
 };
 ```
  
-<div class="alert alert-danger">
-Do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionalities.
-</div>
+>❗ Do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionalities.
                              
 If it's necessary to apply some validation logic or mask to the data entered in this field, you can include in the `checkout-instore-custom.js` file a function that listens to the `note.visible` event, which is triggered when the modal is open, and then develop your logic.
 
diff --git a/docs/tracks/en/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md b/docs/tracks/en/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
index 09b7c6b1f..2ad6e209a 100644
--- a/docs/tracks/en/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
+++ b/docs/tracks/en/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/exporting-an-order.md b/docs/tracks/en/exporting-an-order.md
index 64e28a3b5..1e96543e3 100644
--- a/docs/tracks/en/exporting-an-order.md
+++ b/docs/tracks/en/exporting-an-order.md
@@ -18,9 +18,7 @@ You can export orders through the **All Orders** module in VTEX Admin.
 
 In this process, the system generates a report in .csv format containing details about your store's orders. Find out what information is in the report in [our tutorial on the order spreadsheet fields](https://help.vtex.com/en/tutorial/orders-worksheet--31m1ewsmsEe0WS4So2aGMY).
 
-<div class="alert alert-info">
-<p>If the number of orders selected to be exported is very high, it might cause slow performance. Therefore, you can only select a limited number of orders. Currently, exports are limited to <b>50,000 orders at a time</b>.</p>
-</div>
+>ℹ️ If the number of orders selected to be exported is very high, it might cause slow performance. Therefore, you can only select a limited number of orders. Currently, exports are limited to **50,000 orders at a time**.
 
 Follow the instructions below to create the report:
 
diff --git a/docs/tracks/en/extensions-hub-partners.md b/docs/tracks/en/extensions-hub-partners.md
index c47523652..63cafdbc1 100644
--- a/docs/tracks/en/extensions-hub-partners.md
+++ b/docs/tracks/en/extensions-hub-partners.md
@@ -14,6 +14,4 @@ trackId: AW7klkYMh557y5IUOgzco
 trackSlugEN: extensions-hub
 ---
 
-<div class="alert alert-warning">
-Content is not available yet.
-</div>
+>⚠️ Content is not available yet.
diff --git a/docs/tracks/en/facebook-business-extension.md b/docs/tracks/en/facebook-business-extension.md
index 02ded3fa7..676941bdd 100644
--- a/docs/tracks/en/facebook-business-extension.md
+++ b/docs/tracks/en/facebook-business-extension.md
@@ -30,9 +30,7 @@ The _Facebook Business Extension and Conversions API_ app is fully compatible wi
 
 Learn more about the required configuration for each in our [Facebook Business Extension](https://developers.vtex.com/docs/guides/vtex-facebook-fbe#compatibility) guide on the Developer Portal.
 
-<div class="alert alert-warning">
-VTEX has a <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Facebook integration guide</a>. However, integration with the <i>Facebook Business Extension and Conversions API</i> app must be your default choice, as FBE is Facebook's most complete solution. Regardless of whether you have the other integration configured, you must proceed normally with the configuration of this integration.
-</div>
+>⚠️ VTEX has a <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Facebook integration guide</a>. However, integration with the <i>Facebook Business Extension and Conversions API</i> app must be your default choice, as FBE is Facebook's most complete solution. Regardless of whether you have the other integration configured, you must proceed normally with the configuration of this integration.
 
 ## Facebook Pixel
 
diff --git a/docs/tracks/en/filters.md b/docs/tracks/en/filters.md
index 92d6402bb..d7b90bfc3 100644
--- a/docs/tracks/en/filters.md
+++ b/docs/tracks/en/filters.md
@@ -20,17 +20,13 @@ By selecting a filter (price, color, size, or brand), customers can narrow searc
 
 **VTEX Intelligent Search** uses the context of products returned in search results to know exactly which filters should be displayed to the customer, according to the Catalog configuration.
 
-<div class="alert alert-info">
-  <p>The brand, department, category, and subcategory filters are sorted by the number of products registered for each filter.</p>
-</div>
+>ℹ️ The brand, department, category, and subcategory filters are sorted by the number of products registered for each filter.
 
 For example, consider that the *Size* filter has been configured in the store's catalog, and only the *sneakers* product has the *Size* specification filled in. So when the user searches for the term *sneakers*, the *Size* filter will be available. If they search for any other term, such as *hat*, this specification won’t be displayed as a filter.
 
 The search result will not display a specification when it the only existing filter or when the customer accesses it through the store menu. For example, if a customer selects the Electrical Appliances filter directly from the menu, it will not display Departments as a side filter.
 
-<div class="alert alert-info">
-  <p>If the search results returns more than 30,000 products, some filter values will be omitted, since only the specifications of some of these products will be considered.</p>
-</div>
+>ℹ️ If the search results returns more than 30,000 products, some filter values will be omitted, since only the specifications of some of these products will be considered.
 
 The Filters feature allows you to:
 
@@ -44,6 +40,4 @@ The Filters feature allows you to:
 
 Check out the [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) guide on the Developer Portal for more technical details on using filters.
 
-<div class="alert alert-warning">
-  <p>While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.</p>
-</div>
+>⚠️ While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.
diff --git a/docs/tracks/en/forcing-stock-availability.md b/docs/tracks/en/forcing-stock-availability.md
index 95f054e05..c9794d06c 100644
--- a/docs/tracks/en/forcing-stock-availability.md
+++ b/docs/tracks/en/forcing-stock-availability.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: forcing-stock-availability
 ---
 
-<div class="alert alert-danger">
-The configuration to force stock availability, explained in this article, involves changing the <code>checkout-instore-custom.js</code> file. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ The configuration to force stock availability, explained in this article, involves changing the `checkout-instore-custom.js` file. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 By default, if an SKU has zero stock in the store catalog, it is not possible to sell that SKU with inStore.
 
@@ -34,6 +32,4 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionalities.
-</div>
+>❗ Do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionalities.
diff --git a/docs/tracks/en/frontend-implementation.md b/docs/tracks/en/frontend-implementation.md
index e69089247..1911c6bd5 100644
--- a/docs/tracks/en/frontend-implementation.md
+++ b/docs/tracks/en/frontend-implementation.md
@@ -47,9 +47,7 @@ The <a href="#development-stages">development stage</a> can run in parallel with
 
 VTEX has three different technologies for storefront development: [FastStore](#faststore), [Store Framework](#store-framework) and [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). Legacy CMS Portal was VTEX's first technology for building storefronts, based on HTML, CSS, and JavaScript, and all development and code editing for this technology is done via the VTEX Admin.
 
-<div class="alert alert-warning">
-Although some stores still use it, the <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> is a legacy technology and is no longer available to new stores starting with VTEX.
-</div>
+>⚠️ Although some stores still use it, the [CMS Portal Legado](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) is a legacy technology and is no longer available to new stores starting with VTEX.
 
 The following sections are about the main characteristics and features of FastStore and Store Framework.
 
diff --git a/docs/tracks/en/get-visitors-from-my-website-and-social-networks-to-whatsapp.md b/docs/tracks/en/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
index fb3ee47c5..8d51671ba 100644
--- a/docs/tracks/en/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
+++ b/docs/tracks/en/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/getting-started-with-logistics.md b/docs/tracks/en/getting-started-with-logistics.md
index d5ab89c2f..224882b51 100644
--- a/docs/tracks/en/getting-started-with-logistics.md
+++ b/docs/tracks/en/getting-started-with-logistics.md
@@ -19,16 +19,16 @@ The **Inventory & shipping** module is where you set up the logistics of your VT
 
 This article is the first in a series of five articles for getting started with logistics in your store. The series contains essential information to help you understand logistics in VTEX stores and how settings are structured on the platform.
 
-<div class="alert alert-danger">
-Before setting up your store logistics, please configure the following:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE">Trade policy</li></a>
-<li><a href="https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR">Catalog</li></a>
-<li><a href="https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu">Prices</li></a>
-  </ol>
-  </body>
-</div>
+>❗ Before setting up your store logistics, please configure the following:
+> <body>
+>
+> [Trade policy](https://help.vtex.com/en/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE)
+>
+> [Catalog](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR)
+>
+> [Prices](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)
+>
+> </body>
 
 This walkthrough brings together the following articles:
 
diff --git a/docs/tracks/en/go-live-process.md b/docs/tracks/en/go-live-process.md
index 7a5515151..52fdd2898 100644
--- a/docs/tracks/en/go-live-process.md
+++ b/docs/tracks/en/go-live-process.md
@@ -30,9 +30,7 @@ Before going live, you need to ensure that you have set up all configurations fo
 
 Copy this [Store configuration checklist](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/be48d84768e5fb014f3903ad23927a11/Store_configuration_checklist_EN.xlsx) and check if you have configured each item according to your desired operation.
 
-<div class="alert alert-warning">
-The checklist above lists the basic features and configurations required to run a VTEX store. It is your team's responsibility to determine which features to implement in your store and how to configure them to create the desired store experience. Therefore, this list may only cover some of the features your store uses, and you must check all aspects of your store's operation, even if they are not on the suggested list.
-</div>
+>⚠️ The checklist above lists the basic features and configurations required to run a VTEX store. It is your team's responsibility to determine which features to implement in your store and how to configure them to create the desired store experience. Therefore, this list may only cover some of the features your store uses, and you must check all aspects of your store's operation, even if they are not on the suggested list.
 
 ## Instructions
 
diff --git a/docs/tracks/en/go-live.md b/docs/tracks/en/go-live.md
index e2fc5d720..f34bec656 100644
--- a/docs/tracks/en/go-live.md
+++ b/docs/tracks/en/go-live.md
@@ -58,9 +58,7 @@ Store host: www.store.mycompany.com.br
 
 Note that the subdomain (`store`, `www`, `www.store` or others) and the top-level domain (`.com`, `.com.br`, `.com.ar`, or others) are part of the `{hostname}` and must be in the CNAME destination.
 
-<div class="alert alert-danger">
-There can not be any type A pointing coexisting with the CNAME pointing described above. This coexistence may cause issues in your go-live. Maintain only the CNAME pointing described above.
-</div>
+>❗ There can not be any type A pointing coexisting with the CNAME pointing described above. This coexistence may cause issues in your go-live. Maintain only the CNAME pointing described above.
 
 It takes 24-48 hours for DNS pointing to propagate fully, which means that the configured address may not be accessible to everyone immediately after configuration. Also, [notifying the pointing](#notifying-the-pointing) is required for the store to be available.
 
diff --git a/docs/tracks/en/google-pay.md b/docs/tracks/en/google-pay.md
index 6ff1bcd4d..d49fe3934 100644
--- a/docs/tracks/en/google-pay.md
+++ b/docs/tracks/en/google-pay.md
@@ -18,9 +18,7 @@ Google Pay™ is a digital payments service that allows users not to share their
 
 The Google Pay API Terms of Service apply whenever the Google Pay service is offered by a merchant. To read the terms, please see [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
 
-<div class="alert alert-warning">
-<p>Google Pay is not available for Checkout V5 or earlier versions of Checkout.</p>
-</div>
+>⚠️ Google Pay is not available for Checkout V5 or earlier versions of Checkout.
 
 ## Enabling Google Pay
 
@@ -50,9 +48,7 @@ To use Google Pay, you must meet the following requirements:
 <p>For stores that have the <a href="https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> authentication flow configured and supported by the acquirer, payment with Google Pay will follow the card native flow and will use 3DS as well. For more information on how to configure the authentication flow, please refer to <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Setting up 3DS 2 authentication flow</a>.</p>
 </div>
 
-<div class="alert alert-info">
-<p>You can also set up Google Pay to be processed with Adyen or Stripe. To do this, access the <b>Payment Conditions</b> screen in Admin, click on <b>Google Pay</b> and select the desired option.</p>
-</div>
+>ℹ️ You can also set up Google Pay to be processed with Adyen or Stripe. To do this, access the **Payment Conditions** screen in Admin, click on **Google Pay** and select the desired option.
 
 ## Viewing transactions completed with Google Pay
 
@@ -64,9 +60,7 @@ After accessing the desired transaction, click on `+ Information` to verify the
 
 ![Google Pay Transaction_2](https://images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/a565b60f7ca5f541c836553140261985/Google_Pay_Transaction2_EN.png)
 
-<div class="alert alert-warning">
-  <p>It is also possible to identify transactions made with Google Pay through the <b>All Orders</b> page in Admin. You just need to select the desired search period, <a href="https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">export the orders</a> in a report in .csv and locate the Google Pay information in the "payment origin" field.</p>
-</div>
+>⚠️ It is also possible to identify transactions made with Google Pay through the **All Orders** page in Admin. You just need to select the desired search period, [export the orders](https://help.vtex.com/en/tracks/orders--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu) in a report in .csv and locate the Google Pay information in the "payment origin" field.
 
 ## Adding Google Pay information to the purchase template
 
diff --git a/docs/tracks/en/google-shopping-ads-install.md b/docs/tracks/en/google-shopping-ads-install.md
index 3fca6248e..6d08fb983 100644
--- a/docs/tracks/en/google-shopping-ads-install.md
+++ b/docs/tracks/en/google-shopping-ads-install.md
@@ -14,9 +14,7 @@ trackId: 47kz5PRQPK0IEaqGqiIuA
 trackSlugEN: how-to-campaign-through-google-ads
 ---
 
-<div class="alert alert-warning">
-Currently, Google Shopping Ads is <strong>only available for Brazilian stores</strong>.
-</div>
+>⚠️ Currently, Google Shopping Ads is **only available for Brazilian stores**.
 
 The first step to use the app is to install it. Follow the step-by-step below:
 
diff --git a/docs/tracks/en/google-shopping-ads-set-up.md b/docs/tracks/en/google-shopping-ads-set-up.md
index a7df8ffae..5e94ff1ec 100644
--- a/docs/tracks/en/google-shopping-ads-set-up.md
+++ b/docs/tracks/en/google-shopping-ads-set-up.md
@@ -27,9 +27,7 @@ In this step, you must define which store will use the app and which URL Google
 1. In the `Store` option select the sub-account that should be used for the app;
 2. In the `URL` option select the URL corresponding to the account's website chosen in the previous step.
 
-<div class="alert alert-warning">
-<strong>NOTE:</strong> Make sure the chosen URL is the correct one, as the options will show any URL that is registered on <a href="https://help.vtex.com/en/tutorial/configurando-dominios-no-license-manager?locale=en">your domains</a>. <strong>Usually, the URL is the one that has WWW</strong>.
-</div>
+>⚠️ **NOTE:** Make sure the chosen URL is the correct one, as the options will show any URL that is registered on [your domains](https://help.vtex.com/en/tutorial/configurando-dominios-no-license-manager?locale=en). **Usually, the URL is the one that has WWW**.
 
 ## Setting up an account at the Google Merchant Center
 
@@ -43,9 +41,7 @@ When you select __"Create new"__, it is very important to immediately [access th
 
 - __Link existing:__ The app will use your already existing GMC account. When logging in, you need to use the same email that you use for the GMC you want to link.
 
-<div class="alert alert-warning">
-<strong>NOTE:</strong> The URL set in GMC must be <strong>exactly the same</strong> as the one previously chosen. Also, remember to take the protocol into account (http or https).
-</div>
+>⚠️ **NOTE:** The URL set in GMC must be **exactly the same** as the one previously chosen. Also, remember to take the protocol into account (http or https).
 
 When you select __"Link to an existing GMC"__, you will have to define whether product integration with Google will be done through VTEX or through an external synchronization that you already use.
 
diff --git a/docs/tracks/en/google-shopping-marketplace.md b/docs/tracks/en/google-shopping-marketplace.md
index 4026c3c2a..91ee0c656 100644
--- a/docs/tracks/en/google-shopping-marketplace.md
+++ b/docs/tracks/en/google-shopping-marketplace.md
@@ -22,9 +22,7 @@ Using Google Shopping, you can display to potential customers some of the attrib
 
 The Google Shopping connector on the VTEX Platform allows you to use this service in a simple and efficient way. To integrate it with your store, follow the steps described in this article.
 
-<div class="alert alert-info">
-Before configuring the integration, read the <a href="https://support.google.com/google-ads/answer/6149970?hl=en"> Shopping ads policies</a> to learn what are the conditions required by Google.
-</div>
+>ℹ️ Before configuring the integration, read the [ Shopping ads policies](https://support.google.com/google-ads/answer/6149970?hl=en) to learn what are the conditions required by Google.
 
 | **LEARN MORE** |
 | ---------- |
diff --git a/docs/tracks/en/how-a-split-payment-transaction-works.md b/docs/tracks/en/how-a-split-payment-transaction-works.md
index 3ca6b708c..67f013efe 100644
--- a/docs/tracks/en/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/en/how-a-split-payment-transaction-works.md
@@ -23,9 +23,7 @@ Before we proceed, let’s look at some of the concepts related to this segmenta
 ## MDR
 When processing a transaction, acquirers deduct a percentage of the total purchase amount. This fee is called the Merchant Discount Rate (MDR). 
 
-<div class="alert alert-info">
-MDR is applied in __all__ transactions processed by the acquirer.
-</div>  
+>ℹ️ MDR is applied in __all__ transactions processed by the acquirer.  
 
 In the case of split payment, both the marketplace and the seller(s) may be responsible for this fee. Also, both recipients can be responsible for the payment.     
 
diff --git a/docs/tracks/en/how-clustered-conditions-work.md b/docs/tracks/en/how-clustered-conditions-work.md
index 6cabaf16a..3ee2f399a 100644
--- a/docs/tracks/en/how-clustered-conditions-work.md
+++ b/docs/tracks/en/how-clustered-conditions-work.md
@@ -20,9 +20,7 @@ These conditions are based on the data that Master Data saves on a store’s cus
 
 The deadline and installment rules will thereby be applied to the consumer(s) that fit the condition(s). 
 
-<div class="alert alert-danger">
-<strong>Warning</strong>: you can only create five client clusters per payment condition.
-</div>
+>❗ **Warning**: you can only create five client clusters per payment condition.
 
 To configure these clusters, choose a property and then select the parameters to create a cluster.
 
diff --git a/docs/tracks/en/how-does-vtex-intelligent-search-work.md b/docs/tracks/en/how-does-vtex-intelligent-search-work.md
index db87fd382..adec93591 100644
--- a/docs/tracks/en/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/en/how-does-vtex-intelligent-search-work.md
@@ -89,9 +89,7 @@ For example: The "color" specification is set as searchable and the product was
 
 You can include special characters ( `-` and `/`) when searching for a product.
 
-<div class="alert alert-warning">
-	<p>Choosing the search fields affects the <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">merchandising rule</a> options, as only searchable fields can be used to set up the rules. For example, if you set only the <strong><code>SKUID</code></strong> field as searchable, you cannot promote a<strong><code> ProductID</code></strong> or a <strong><code>ProductRefID</code></strong> using merchandising rules. </p>
-</div>
+>⚠️ Choosing the search fields affects the [merchandising rule](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) options, as only searchable fields can be used to set up the rules. For example, if you set only the **`SKUID`** field as searchable, you cannot promote a**` ProductID`** or a **`ProductRefID`** using merchandising rules.
 
 ### Defining and sorting filter fields
 
@@ -105,9 +103,7 @@ _For example_: a merchant configured that "promotion" has greater relevance than
 
 For more information on how to customize the order of results to meet your store's needs, read the article [Relevance settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
 
-<div class="alert alert-info">
-	<p>When using Intelligent Search, two options define the sorting order of your collections. By using the <code>map=productClusterIds</code> command, you are setting the order of your collections to be the one pre-defined by the merchant, with its relevance criteria. If you choose to use <code>productClusterNames</code>, you are setting that you want your collections to follow Intelligent Search's own relevance standards.</p>
-</div>
+>ℹ️ When using Intelligent Search, two options define the sorting order of your collections. By using the `map=productClusterIds` command, you are setting the order of your collections to be the one pre-defined by the merchant, with its relevance criteria. If you choose to use `productClusterNames`, you are setting that you want your collections to follow Intelligent Search's own relevance standards.
 
 ## Alternative ways to search
 
diff --git a/docs/tracks/en/how-the-payments-module-works.md b/docs/tracks/en/how-the-payments-module-works.md
index 9e458928e..752b0ffd4 100644
--- a/docs/tracks/en/how-the-payments-module-works.md
+++ b/docs/tracks/en/how-the-payments-module-works.md
@@ -18,9 +18,7 @@ The **Payments** module is the system responsible for managing all actions regar
 
 Before we explore the features within VTEX Admin *Payments*, let's clarify some important concepts regarding the payment flow of an order. This process is performed by some actors within the Brazilian financial system, which make up the Payments module architecture.
 
-<div class="alert alert-info">
-It is important to remember that each store has its own particularities and its own operation, which influence how to build your business' Payment module. To set up your cash flow, it is therefore crucial to keep in mind the real needs and purposes of the retailer and of the desired project.
-</div>
+>ℹ️ It is important to remember that each store has its own particularities and its own operation, which influence how to build your business' Payment module. To set up your cash flow, it is therefore crucial to keep in mind the real needs and purposes of the retailer and of the desired project.
 
 ## Gateway 
 
diff --git a/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
index 1d6b56d1f..8692a0d61 100644
--- a/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/en/how-to-configure-a-device-for-printout-the-order.md
@@ -38,9 +38,7 @@ configureDeviceEnabled: true,
       }
 }``
 
-<div class="alert alert-info">
-  <strong>NOTE</strong>: There is an option to automatically print the order summary once the order is completed. The configuration is very simple, just add the <strong><i>printPageAutomatically</i></strong> property with the value <strong><i>true</i></strong> inside the <strong><i>printingConfig</i></strong> object.
-   </div>
+>ℹ️ **NOTE**: There is an option to automatically print the order summary once the order is completed. The configuration is very simple, just add the **<i>printPageAutomatically</i>** property with the value **<i>true</i>** inside the **<i>printingConfig</i>** object.
    
 Do not delete any of the other properties present in this object. The result should be something like:
 
@@ -55,9 +53,7 @@ printPageAutomatically: true
 
 ## Configure printer device in inStore
 
-<div class="alert alert-warning">
-  <strong>IMPORTANT</strong>: For the configuration of the printer within inStore, it is necessary to have the <strong><i>AppKey</i></strong> and the <strong><i>AppToken</i></strong> with permissions of at least one profile as <i>“InStore Salesperson (inStore Sales Person)”</i>. It is worth clarifying that an <i>“Owner (Admin Super)”</i> profile can be used.
-  </div>
+>⚠️ **IMPORTANT**: For the configuration of the printer within inStore, it is necessary to have the **<i>AppKey</i>** and the **<i>AppToken</i>** with permissions of at least one profile as <i>“InStore Salesperson (inStore Sales Person)”</i>. It is worth clarifying that an <i>“Owner (Admin Super)”</i> profile can be used.
 
   1. Connect the printer to the computer where inStore is installed (to download the inStore you can go to [http://instore.vtex.com/download]). It must be a computer with Windows operating system (Windows 7 or higher are compatible).
   2. Open inStore application and enter the store in which you want to configure the printer.
diff --git a/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
index fb2e1071d..ef1f2a422 100644
--- a/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
@@ -33,9 +33,7 @@ The __preview__ rendered by this code is shown in the box below the HTML field.
 
 The __JSON Data__ field shows a JSON object *example* that contains information regarding the subject of the email. This object's braces can be used as variables in the template's HTML code. We will learn how to do this in the next article.
 
-<div class="alert alert-warning">
-Warning: To customize the email layout, you must enter <strong>inline CSS code</strong>. <u>Don't</u> insert CSS into the head of the template, because emails don't handle it well.
-</div>
+>⚠️ Warning: To customize the email layout, you must enter **inline CSS code**. <u>Don't</u> insert CSS into the head of the template, because emails don't handle it well.
 
 At the end, click on the __Save__ button.
 
diff --git a/docs/tracks/en/how-to-customize-the-observation-field.md b/docs/tracks/en/how-to-customize-the-observation-field.md
index fce894cdb..f10e6bd01 100644
--- a/docs/tracks/en/how-to-customize-the-observation-field.md
+++ b/docs/tracks/en/how-to-customize-the-observation-field.md
@@ -33,9 +33,7 @@ window.LOCALE_MESSAGES = {
 };
 ```
 
-<div class="alert alert-danger">
-To avoid rendering other functionalities useless, it is imperative that you do not delete any of the already existing <code>window.INSTORE_CONFIG</code> properties.
-</div>
+>❗ To avoid rendering other functionalities useless, it is imperative that you do not delete any of the already existing `window.INSTORE_CONFIG` properties.
 
 If you need to apply a mask or validation logic to data inserted in this field, you can do so by including an event listener function to the `checkout-instore-custom.js` archive. This `note.visible` function is triggered when the modal dialog window is open, thereby returning your logic.
 
diff --git a/docs/tracks/en/how-to-get-started.md b/docs/tracks/en/how-to-get-started.md
index 0644c1f6d..3b43148ec 100644
--- a/docs/tracks/en/how-to-get-started.md
+++ b/docs/tracks/en/how-to-get-started.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/including-order-variables-in-email-template.md b/docs/tracks/en/including-order-variables-in-email-template.md
index 4c0ecd742..f26c12174 100644
--- a/docs/tracks/en/including-order-variables-in-email-template.md
+++ b/docs/tracks/en/including-order-variables-in-email-template.md
@@ -22,9 +22,7 @@ These variables are JSON properties in the __JSON Data__ field and can be used i
 
 ### Example
 
-<div class="alert alert-warning">
-JSON Data examples will only appear in templates when you complete the desired action in your store. If you have not transacted an order, recurrence or any other action, JSON Data will appear blank.
-</div>
+>⚠️ JSON Data examples will only appear in templates when you complete the desired action in your store. If you have not transacted an order, recurrence or any other action, JSON Data will appear blank.
 
 Let's say you want to enter the carrier's name in the order sent email.
 
diff --git a/docs/tracks/en/initial-setup.md b/docs/tracks/en/initial-setup.md
index f95145c25..643828d87 100644
--- a/docs/tracks/en/initial-setup.md
+++ b/docs/tracks/en/initial-setup.md
@@ -20,17 +20,14 @@ Before you start developing, make sure that the steps below have been completed.
 
 You need to have npm or yarn installed on your computer. Both are package managers. And one of the two is required to install VTEX IO CLI.
 
-<div class="alert alert-info">
-If you're not used to working with package managers, dig further into these tools:<br>
-<ul>
-  <li>
-    <a href="https://www.npmjs.com/">npm</a>
-  </li>
-  <li>
-    <a href="https://yarnpkg.com/">yarn</a>
-  </li>
-</ul>
-</div>
+>ℹ️ If you're not used to working with package managers, dig further into these tools:
+>
+> 
+>
+> * [npm](https://www.npmjs.com/)
+>
+> * [yarn](https://yarnpkg.com/)
+> 
 
 ## Install VTEX IO CLI
 
diff --git a/docs/tracks/en/initializing-your-store-theme.md b/docs/tracks/en/initializing-your-store-theme.md
index ceb1cb6ce..714b91eae 100644
--- a/docs/tracks/en/initializing-your-store-theme.md
+++ b/docs/tracks/en/initializing-your-store-theme.md
@@ -72,9 +72,7 @@ Let's take a look at an example manifest file and all its properties:
 
 The store-theme init also created two different folders, named after the builders defined on the manifest: __store/__ and __styles/__. These will be processed by their respective builders in order to have the desired effects on your store.
 
-<div class="alert alert-info">
-Aside: Note that the <code>store-theme</code> depends on the <code>vtex.store</code> <a href="https://github.com/vtex-apps/store">app</a>. This app declares the basic configurations in order to have a functioning store, such as interfaces, routes, store settings, and more. You can think of it as part of the VTEX Store Framework. This app comes pre-installed with every VTEX account and cannot be uninstalled.
-</div>
+>ℹ️ Aside: Note that the `store-theme` depends on the `vtex.store` [app](https://github.com/vtex-apps/store). This app declares the basic configurations in order to have a functioning store, such as interfaces, routes, store settings, and more. You can think of it as part of the VTEX Store Framework. This app comes pre-installed with every VTEX account and cannot be uninstalled.
 
 We will start editing these files soon. First, let's link this app and see it working.
 
@@ -88,9 +86,7 @@ Run `vtex link`  and watch your template app be compiled and published to the ac
 
 ![vtex-link](https://images.ctfassets.net/alneenqid6w5/1peFxCLM0kF9JvC8AmPeFi/9cef3e4e5e5877a744c15ca3f6e8db18/vtex-link.svg)
 
-<div class="alert alert-info">
-Remember: run <code>vtex whoami</code> to make sure you are in the correct account and in a test workspace, otherwise <code>VTEX Toolbelt</code> will complain about linking directly to master.
-</div>
+>ℹ️ Remember: run `vtex whoami` to make sure you are in the correct account and in a test workspace, otherwise `VTEX Toolbelt` will complain about linking directly to master.
 
 ## Visiting our newly generated store
 
diff --git a/docs/tracks/en/instore-basic-settings.md b/docs/tracks/en/instore-basic-settings.md
index 4df951ff1..a8af67595 100644
--- a/docs/tracks/en/instore-basic-settings.md
+++ b/docs/tracks/en/instore-basic-settings.md
@@ -16,15 +16,11 @@ trackSlugEN: instore-first-steps-and-configurations
 
 VTEX Sales App is one of VTEX's main products for [unified commerce](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv) operations. It is an app that allows your store to provide a true omnichannel experience, integrating your online and physical channels and placing your customers at the core of the business.
 
-<div class="alert alert-info">
-<p>Before you start using VTEX Sales App, make sure your store meets all the <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">prerequisites</a>.</p>
-</div>
+>ℹ️ Before you start using VTEX Sales App, make sure your store meets all the [prerequisites](https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u).
 
 To use VTEX Sales App, you must follow the steps below in your main account.
 
-<div class="alert alert-warning">
-<p> It is not necessary to install or configure VTEX Sales App on franchise accounts that represent physical stores. The procedure described in this article must be performed only on the main brand account.</p>
-</div>
+>⚠️ It is not necessary to install or configure VTEX Sales App on franchise accounts that represent physical stores. The procedure described in this article must be performed only on the main brand account.
 
 ## Installing VTEX Sales App
 
@@ -68,9 +64,7 @@ If you choose to `Skip this step`, a fictitious store will be created for testin
 
 You must define an email and a name to be used as a sales associate’s login credentials. When you are ready, click on `Confirm`.
 
-<div class="alert alert-warning">
-<p>The email added in this screen <strong>cannot</strong> be in use on the VTEX platform Admin. Use sales associate emails that do not have Admin access.</p>
-</div>
+>⚠️ The email added in this screen **cannot** be in use on the VTEX platform Admin. Use sales associate emails that do not have Admin access.
 
 In this step, you’ll only add one of your sales associates. After configuring the basic settings, you can [add other sales associates](https://help.vtex.com/pt/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/5PSjRstg7UU4lOm0s8aqKN).
 
diff --git a/docs/tracks/en/instore-customizations.md b/docs/tracks/en/instore-customizations.md
index e8cc1588b..4d532ecbf 100644
--- a/docs/tracks/en/instore-customizations.md
+++ b/docs/tracks/en/instore-customizations.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugEN: instore-customizations
 ---
 
-<div class="alert alert-danger">
-Most inStore customizations involve changing the JavaScript file <code>checkout-instore-custom.js</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ Most inStore customizations involve changing the JavaScript file `checkout-instore-custom.js`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 ## Accessing the inStore customization file
 
@@ -50,9 +48,7 @@ To make any changes, simply add or modify the lines of code directly in the file
 
 ![20. inStore Customizations - 3 - EN.png?h=250](https://images.ctfassets.net/alneenqid6w5/6gxUvg8FcYg2b7zhNpoTj8/0137d152efa66e076f438e849a5bde87/20._inStore_Customizations_-_3_-_EN.png_h_250)
 
-<div class="alert alert-warning">
-Always follow the customization instructions in this documentation and only make changes as indicated here.
-</div>
+>⚠️ Always follow the customization instructions in this documentation and only make changes as indicated here.
 
 ## InStore customizations
 
diff --git a/docs/tracks/en/instore.md b/docs/tracks/en/instore.md
index 0d18e1816..2612c6c1c 100644
--- a/docs/tracks/en/instore.md
+++ b/docs/tracks/en/instore.md
@@ -52,9 +52,7 @@ Just enter one of these data in the field and click on the __Confirm__ button.
 
 Alternatively, if you have enabled the Anonymous User feature, it is possible to proceed without identifying the customer. To do this, just click on __Continue without identification__.
 
-<div class="alert alert-info">
-Although it is possible to cater customers without identifying them, we always recommend doing so, as this gives the salesperson a series of contextual information that increases the chances of conversion.
-</div>
+>ℹ️ Although it is possible to cater customers without identifying them, we always recommend doing so, as this gives the salesperson a series of contextual information that increases the chances of conversion.
 
 ## 3. Omnichannel search
 
diff --git a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
index 605f834f8..2492fb3f4 100644
--- a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
@@ -36,9 +36,7 @@ If necessary, InStore can send additional information. Example with the sub-acqu
 - `administrativePassword`: string - default password. For example, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-To create any extra configuration, you need to send to the inStore team (instoredevs@vtex.com.br) every extra the app needs to complete the transaction. With that, we will create a form on the Payments module so that customers can configure their acquirer.
-</div>
+>ℹ️ To create any extra configuration, you need to send to the inStore team (instoredevs@vtex.com.br) every extra the app needs to complete the transaction. With that, we will create a form on the Payments module so that customers can configure their acquirer.
 
 ## Sending URI and response URI for each action
 
@@ -184,9 +182,7 @@ For the integration to work, the customer must set up the InStore connector on t
 
 AppLinking integration doesn't include other dependencies, since communication between the inStore application and the payment application happens with specific URIs containing all the configuration and payment parameters required for the action.
 
-<div class="alert alert-warning">
-On Android, all communication must happen with a new <code>Intent</code>. This means that you should not send the response as a callback from the initial <code>Intent</code> call. Instead, send a new <code>Intent</code> to the inStore application with the previous response.
-</div>
+>⚠️ On Android, all communication must happen with a new `Intent`. This means that you should not send the response as a callback from the initial `Intent` call. Instead, send a new `Intent` to the inStore application with the previous response.
 
 To configure the inStore connector, follow the steps below:
 
diff --git a/docs/tracks/en/integration-configurations.md b/docs/tracks/en/integration-configurations.md
index dab608937..6a4d521f3 100644
--- a/docs/tracks/en/integration-configurations.md
+++ b/docs/tracks/en/integration-configurations.md
@@ -26,48 +26,46 @@ The following steps must be implemented in the app:
 
 Shipping items using Wish ranges from the all-encompassing to the very specific. You can set a general shipping value for any region worldwide, just as you can set a value for a country's specific subregion.
 
-<div class="alert alert-info">
- NOTE: Wish demands that product prices and shipping be sent in USD. However, it does convert order values into BRL directly, making issuing invoices much easier.
-
-This means to highlight that priority will always be given to the **more specific** shipping rate configuration. Let's have a look at the following example for further clarity:
-
-| Shipping      | Specification | Price   |
-| ---------- | ---------- | ---------- |
-| Standard     |            | U$ 30,00   |
-| By country   | Brazil  | U$ 25,00   |
-| By country   | US     | U$ 20,00   |
-| By subregion | New York (metropolitan region)  | U$ 10,00 |
-| By subregion | New York (state)              | U$ 15,00 |
-| By subregion | Chicago (metropolitan region) | U$ 10,00 |
-
-  - If we're shipping to Miami, for example, the cost would be U$ 20,00 as in fits under Cost to US, which is more specific than Standard Shipping.
-  - However if we're shipping to Germany, for example, the cost would fall under the Standard Shipping of U$ 30,00. 
-  - But if we're shipping to New York (State) the price would be _U$ 15,00_
-
-Let's get some more insight on each of the shipping types:
-
-### Standard shipping
-
-Represents the most macro shipping rate available and can be used for both worldwide and local shipping.
-
-_Ex: if you set the price for standard shipping at U$ 30,00 and don't have any other more specific shipping rate, then this will be the set shipping price for anywhere in the world. This means that shipping something to Mexico would cost the same as shipping something to Portugal, to New York or Seattle or anywhere else._
-
-### Shipping by country
-
-Refers to the default shipping rate for a specific country. It's therefore possible to have different shipping rates for different countries. [Click here for more on Wish's shipping by country settings](https://merchantfaq.wish.com/hc/pt/articles/205212607-Como-configuro-as-minhas-configura%C3%A7%C3%B5es-de-frete-).
-
-_Ex: the shipping price for Brazil is U$ 20,00 while for Argentina it stands at U$ 25,00._
-
-### Shipping by subregions
-
-Refers to the specific rate for a country's subregions. You can therefore set different shipping rates for different subregions belonging to the same country.
-
-_Ex: the shipping rate to New York (metropolitan region) is U$ 10,00, while the rate for NY (State) is U$ 15,00._
-
-<div class = "alert alert-info">
-  OBS: shipping by region is only available to sellers that use <strong>Wish Express</strong> <a href="[https://merchantfaq.wish.com/hc/en-us/articles/360018939394-How-to-Ship-Wish-Express-to-Brazil]">(additional info here).</a>
- To configure Wish Express, simply follow <a href="[https://merchantfaq.wish.com/hc/en-us/articles/232047747-Wish-Express-Sign-Up-Flow]">these steps.</a>
-  </div>
+>ℹ️ NOTE: Wish demands that product prices and shipping be sent in USD. However, it does convert order values into BRL directly, making issuing invoices much easier.
+>
+> This means to highlight that priority will always be given to the **more specific** shipping rate configuration. Let's have a look at the following example for further clarity:
+>
+> | Shipping      | Specification | Price   |
+> | ---------- | ---------- | ---------- |
+> | Standard     |            | U$ 30,00   |
+> | By country   | Brazil  | U$ 25,00   |
+> | By country   | US     | U$ 20,00   |
+> | By subregion | New York (metropolitan region)  | U$ 10,00 |
+> | By subregion | New York (state)              | U$ 15,00 |
+> | By subregion | Chicago (metropolitan region) | U$ 10,00 |
+>
+> - If we're shipping to Miami, for example, the cost would be U$ 20,00 as in fits under Cost to US, which is more specific than Standard Shipping.
+>   - However if we're shipping to Germany, for example, the cost would fall under the Standard Shipping of U$ 30,00. 
+>   - But if we're shipping to New York (State) the price would be _U$ 15,00_
+>
+> Let's get some more insight on each of the shipping types:
+>
+> ### Standard shipping
+>
+> Represents the most macro shipping rate available and can be used for both worldwide and local shipping.
+>
+> _Ex: if you set the price for standard shipping at U$ 30,00 and don't have any other more specific shipping rate, then this will be the set shipping price for anywhere in the world. This means that shipping something to Mexico would cost the same as shipping something to Portugal, to New York or Seattle or anywhere else._
+>
+> ### Shipping by country
+>
+> Refers to the default shipping rate for a specific country. It's therefore possible to have different shipping rates for different countries. [Click here for more on Wish's shipping by country settings](https://merchantfaq.wish.com/hc/pt/articles/205212607-Como-configuro-as-minhas-configura%C3%A7%C3%B5es-de-frete-).
+>
+> _Ex: the shipping price for Brazil is U$ 20,00 while for Argentina it stands at U$ 25,00._
+>
+> ### Shipping by subregions
+>
+> Refers to the specific rate for a country's subregions. You can therefore set different shipping rates for different subregions belonging to the same country.
+>
+> _Ex: the shipping rate to New York (metropolitan region) is U$ 10,00, while the rate for NY (State) is U$ 15,00._
+>
+> <div class = "alert alert-info">
+>   OBS: shipping by region is only available to sellers that use **Wish Express** [(additional info here).]([https://merchantfaq.wish.com/hc/en-us/articles/360018939394-How-to-Ship-Wish-Express-to-Brazil])
+>  To configure Wish Express, simply follow [these steps.]([https://merchantfaq.wish.com/hc/en-us/articles/232047747-Wish-Express-Sign-Up-Flow])
   
 Specify if you'll use Wish Express in the setup. In case you won't, you may skip to next step.
 
diff --git a/docs/tracks/en/integration-overview.md b/docs/tracks/en/integration-overview.md
index 21e6385a7..99660987a 100644
--- a/docs/tracks/en/integration-overview.md
+++ b/docs/tracks/en/integration-overview.md
@@ -16,9 +16,7 @@ trackSlugEN: facebook-integration
 
 This guide explains how to integrate with Facebook using the connector developed by VTEX. Integration through native connectors should be your default selection, as it implies more efficiency and security.
 
-<div class="alert alert-danger">
-It is possible to <a href="https://help.vtex.com/en/tutorial/configurando-xml--tutorials_242">set up the integration with an XML file</a>. However, it is not advisable to perform the integration simultaneously by an XML file and the native connector, as this causes conflicts and divergence in the information.
-</div>
+>❗ It is possible to [set up the integration with an XML file](https://help.vtex.com/en/tutorial/configurando-xml--tutorials_242). However, it is not advisable to perform the integration simultaneously by an XML file and the native connector, as this causes conflicts and divergence in the information.
 
 Before you proceed with the integration, you must have created:
 
@@ -35,8 +33,6 @@ The next steps to integrate your VTEX store with Facebook are:
 
 After these steps have been completed, the integration is finished. However, the product attributes will not have been sent.
 
-<div class="alert alert-info">
-If you want to send your product attributes to Facebook, you need to do a template mapping of categories and attributes. This mapping is optional. However, if you choose to do it, you must follow all the steps described above. Otherwise, errors can occur in the integration.
-</div>
+>ℹ️ If you want to send your product attributes to Facebook, you need to do a template mapping of categories and attributes. This mapping is optional. However, if you choose to do it, you must follow all the steps described above. Otherwise, errors can occur in the integration.
 
 The steps required to perform category and attribute mapping are described in more detail in the article [Sending products to Facebook](https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc/41qzoa7TWIYTyIhABHdgzI).
diff --git a/docs/tracks/en/intelligent-synonyms.md b/docs/tracks/en/intelligent-synonyms.md
index 409053c92..2bb94b75f 100644
--- a/docs/tracks/en/intelligent-synonyms.md
+++ b/docs/tracks/en/intelligent-synonyms.md
@@ -15,9 +15,7 @@ trackSlugEN: vtex-intelligent-search
 ---
 
 
-<div class="alert alert-info">
-  <p>This feature is available for accounts that have a minimum number of sessions and orders for training the artificial intelligence model. If you would like to implement it, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>. Additional fees may apply in the future.</p>
-</div>
+>ℹ️ This feature is available for accounts that have a minimum number of sessions and orders for training the artificial intelligence model. If you would like to implement it, please contact [our support](https://support.vtex.com/hc/pt-br/requests). Additional fees may apply in the future.
 
 The [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) allows you to add words, or similar sentences, as synonyms for customer search terms, increasing the chance of successful searches.
 
diff --git a/docs/tracks/en/introduction-to-vtex.md b/docs/tracks/en/introduction-to-vtex.md
index 704130b0d..009619fa6 100644
--- a/docs/tracks/en/introduction-to-vtex.md
+++ b/docs/tracks/en/introduction-to-vtex.md
@@ -20,17 +20,13 @@ The following image shows VTEX's solutions and possibilities, which will be cove
 
 ![vtex_composable_complete_EN](https://images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/d4622b765ea964b60da83fd11dffe865/vtex_composable_complete_EN.png)
 
-<div class="alert alert-info">
-Besides the resources available on the Help Center and <a href="https://developers.vtex.com/">Developer Portal</a>, as well as the <a href="https://community.vtex.com/">VTEX Community</a>, our <a href="https://vtex.com/us-en/">website</a> provides additional information about the platform through <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">demo videos</a> and <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> created by our <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">partners</a>. There is also a series of <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">onboarding videos</a> (available only in Portuguese).
-</div>
+>ℹ️ Besides the resources available on the Help Center and [Developer Portal](https://developers.vtex.com/), as well as the [VTEX Community](https://community.vtex.com/), our [website](https://vtex.com/us-en/) provides additional information about the platform through [demo videos](https://vtex.com/br-pt/resources-category/product-demo-videos-br/) and [ebooks](https://vtex.com/br-pt/resources-category/ebooks-br/) created by our [partners](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners). There is also a series of [onboarding videos](https://sites.google.com/vtex.com.br/onboardingvtex/trilha) (available only in Portuguese).
 
 ## Track overview
 
 This track presents the journey of a VTEX store from its initial settings to the go-live. But before configuring the platform [modules](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), planning [backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu), and choosing a [frontend](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) technology for building the storefront, there's a preliminary step: determining the [account type and architecture](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) that best align with your business needs.
 
-<div class="alert alert-warning">
-Each ecommerce operation has its own particularities and this content is not intended to encompass all possible scenarios. Our goal is to provide a general model and present the features and possibilities of the VTEX platform.
-</div>
+>⚠️ Each ecommerce operation has its own particularities and this content is not intended to encompass all possible scenarios. Our goal is to provide a general model and present the features and possibilities of the VTEX platform.
 
 The content is organized sequentially for educational purposes; however, this does not imply that the steps need to be executed in order or that the previous step is a block for the next. Some steps can be completed in parallel, at least partially, such as backend integrations, settings for some modules, and frontend implementation.
 
diff --git a/docs/tracks/en/inventory-and-shipping-module-overview.md b/docs/tracks/en/inventory-and-shipping-module-overview.md
index a3a58b0b6..31501a315 100644
--- a/docs/tracks/en/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/en/inventory-and-shipping-module-overview.md
@@ -14,9 +14,7 @@ trackId: 13TFDwDttPl9ki9OXQhyjx
 trackSlugEN: logistics-101
 ---
 
-<div class="alert alert-info">
-Warning: This documentation is being updated to reflect the concept change from Pannels to <a href="https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">shipping strategy</a>.
-</div>
+>ℹ️ Warning: This documentation is being updated to reflect the concept change from Pannels to [shipping strategy](https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 The __Inventory and Shipping__ module is the service responsible for your store's *logistics*. This system is used when adding __logistics route__ data that is used when delivering orders. In addition, you must use this module to __manage your inventory__, add __shipping prices__ and __shipping deadlines__ for each delivery type.
 
diff --git a/docs/tracks/en/legacy-cms-portal.md b/docs/tracks/en/legacy-cms-portal.md
index a43a92a3b..d3cabb6b0 100644
--- a/docs/tracks/en/legacy-cms-portal.md
+++ b/docs/tracks/en/legacy-cms-portal.md
@@ -72,9 +72,7 @@ See below these basic folders in the CMS:
 
 These folders come by default in the environment of all VTEX stores.
 
-<div class="alert alert-danger">
-The names of the required folders must <b>not</b> be edited.
-</div>
+>❗ The names of the required folders must **not** be edited.
 
 Since folders refer to dynamic pages, their names don't appear on the customer's navigation. In other words, the fact that editing the names is banned does not affect the final text of your URLs, nor the internationalization of your site.
 
@@ -90,9 +88,7 @@ These are:
 
 For these two folders, what matters is the control or placeholder that reads their content. Their names can be freely edited.
 
-<div class="alert alert-warning">
-Since they are private folders, <code>/account</code> and <code>/account/orders</code> <b>must require authentication</b>. See <a href="http://help.vtex.com/en/tutorial/requering-authentication-on-store-pages">in this article</a> how to ensure they are configured to ask for user authentication.
-</div>
+>⚠️ Since they are private folders, `/account` and `/account/orders` **must require authentication**. See [in this article](http://help.vtex.com/en/tutorial/requering-authentication-on-store-pages) how to ensure they are configured to ask for user authentication.
 
 ### Useful folders
 
diff --git a/docs/tracks/en/levar-os-contatos-do-whatsapp-para-um-crm.md b/docs/tracks/en/levar-os-contatos-do-whatsapp-para-um-crm.md
index ecbaba021..953b13206 100644
--- a/docs/tracks/en/levar-os-contatos-do-whatsapp-para-um-crm.md
+++ b/docs/tracks/en/levar-os-contatos-do-whatsapp-para-um-crm.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/live-support.md b/docs/tracks/en/live-support.md
index 309de69e6..c5fb3b24e 100644
--- a/docs/tracks/en/live-support.md
+++ b/docs/tracks/en/live-support.md
@@ -35,9 +35,7 @@ If you choose not to provide it, you need to define an unavailability message in
 ![fuso horário en](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/867851568c68409ae8242293cb30bdd6/horarios_de_funcionamento_en.png)
 3. Select the days and set the business hours of your live support. You can specify more than one window per weekday.
 
-<div class="alert alert-info">
-In case of bank or regional holidays or other dates when support will be unavailable, indicate the date and time. If the windows repeat yearly, you can select "Yearly recurrence," presetting the configuration for future windows.
-</div>
+>ℹ️ In case of bank or regional holidays or other dates when support will be unavailable, indicate the date and time. If the windows repeat yearly, you can select "Yearly recurrence," presetting the configuration for future windows.
 
 <ol start="4">
   <li>If there are any service exceptions, indicate the unavailability windows.<br><img src="//images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/21c42d8dfb5bb4657ee02d5595431f66/image_3_en.png" alt="exceções ou feriados"></li>
diff --git a/docs/tracks/en/login-e-senha.md b/docs/tracks/en/login-e-senha.md
index 2a02f3642..17d338b91 100644
--- a/docs/tracks/en/login-e-senha.md
+++ b/docs/tracks/en/login-e-senha.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugEN: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/manage-skus-in-inventory.md b/docs/tracks/en/manage-skus-in-inventory.md
index eef5827cc..b95995fd8 100644
--- a/docs/tracks/en/manage-skus-in-inventory.md
+++ b/docs/tracks/en/manage-skus-in-inventory.md
@@ -49,9 +49,7 @@ However, make sure that you're familiar with how to correctly fill in the spread
 
 ## API REST
 
-<div class="alert alert-warning">
-Price module REST API call authentications must be made using an AppKey and AppToken. For more info, access our article on  <a href="https://help.vtex.com/en/tutorial/creatoing-appkey-and-apptoken-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2">how to generate an Appkey and an AppToken to authenticate your integrations</a>
-</div>
+>⚠️ Price module REST API call authentications must be made using an AppKey and AppToken. For more info, access our article on  [how to generate an Appkey and an AppToken to authenticate your integrations](https://help.vtex.com/en/tutorial/creatoing-appkey-and-apptoken-to-authenticate-integrations--43tQeyQJgAKGEuCqQKAOI2)
 
 To use API to change the quantity of an SKU in inventory, you'll need to send a __PUT__ to the following endpoint:
 
diff --git a/docs/tracks/en/managing-accounts.md b/docs/tracks/en/managing-accounts.md
index 54a9fcb06..61cf8efe7 100644
--- a/docs/tracks/en/managing-accounts.md
+++ b/docs/tracks/en/managing-accounts.md
@@ -36,9 +36,7 @@ It presents information about the account status (active, inactive), identificat
 
 Displays the amount of credit available for the customer to use for purchases and the total amount to be paid (in invoices) for purchases already made using Customer Credit as a means of payment.
 
-<div class="alert alert-warning">
-When the customer makes a purchase using Customer Credit, but the order has not yet been billed (invoice issued), the <b>Reserved Credit</b> field is also displayed on this screen containing information on the order value.
-</div>
+>⚠️ When the customer makes a purchase using Customer Credit, but the order has not yet been billed (invoice issued), the **Reserved Credit** field is also displayed on this screen containing information on the order value.
 
 ## Manage
 
@@ -74,6 +72,4 @@ From this moment on, the customer and their dependent will be able to share the
 
 If you wish to close the customer's account, in the __Others__ section, click on `CLOSE ACCOUNT`.
 
-<div class="alert alert-warning">
-A closed Customer Credit account cannot be reopened again and invoice, statement and additional dependent data will be deleted. However, after completing the account closure, if you wish, you can <a href="https://help.vtex.com/en/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#creating-accounts-individually">open a new account</a> for the customer using the same email as the closed account.
-</div>
+>⚠️ A closed Customer Credit account cannot be reopened again and invoice, statement and additional dependent data will be deleted. However, after completing the account closure, if you wish, you can [open a new account](https://help.vtex.com/en/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#creating-accounts-individually) for the customer using the same email as the closed account.
diff --git a/docs/tracks/en/managing-customer-credit-invoices.md b/docs/tracks/en/managing-customer-credit-invoices.md
index 6b4aeba67..08f108ef8 100644
--- a/docs/tracks/en/managing-customer-credit-invoices.md
+++ b/docs/tracks/en/managing-customer-credit-invoices.md
@@ -27,9 +27,7 @@ The __Invoices__ screen in the VTEX Admin (__Apps > Customer Credit > Invoices__
 
 To select the list of invoices to be displayed, you can click on one of the four statuses (Open, Paid, Canceled or Expired), or enter the identification number of the order for which the invoice was issued.
 
-<div class="alert alert-warning">
-In Customer Credit, all invoices are created with the status <b>Open</b>.
-</div>
+>⚠️ In Customer Credit, all invoices are created with the status **Open**.
 
 ## Invoice details
 
@@ -42,9 +40,7 @@ To facilitate the payment process for a invoice, it is possible to provide a pay
 - Use the `IMPORT` function to insert data from a .csv spreadsheet.
 - Via [PUT Change Invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-) endpoint of the Customer Credit API.
 
-<div class="alert alert-info">
-After carrying out one of the procedures above, the customer will have access to the <b>PAY</b> button that is available in their customer area on the store's website (<b>My Account > My Credits</b>).
-</div>
+>ℹ️ After carrying out one of the procedures above, the customer will have access to the **PAY** button that is available in their customer area on the store's website (**My Account > My Credits**).
 
 ### Individual settlement
 
diff --git a/docs/tracks/en/managing-shipping-rates.md b/docs/tracks/en/managing-shipping-rates.md
index 8fba14ce1..8c9c7889a 100644
--- a/docs/tracks/en/managing-shipping-rates.md
+++ b/docs/tracks/en/managing-shipping-rates.md
@@ -35,9 +35,7 @@ After the store signed a contract with a carrier, it usually agrees upon the ZIP
 - **Country**: Country to where the order is shipped to. Must be filled out with the [country's 3 digit ISO code](https://countrycode.org/).
 - **MinimumValueInsurance**: It's an additional shipping fee with an absolute value, which is compared to the valued given in PricePercentage and then multiplied by the cart's value. Whichever value is greater is added to the shipping cost. Only one of the two possible values will be added to the shipping cost. For more details, see [what the Minimum Value Insurance field does](http://help.vtex.com/tutorial/what-is-the-minimum-value-insurance--frequentlyAskedQuestions_158).
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> If your spreadsheet size is over 10MB, you'll need to compress it into a <strong>.zip</strong> format. The .zip file must be less than 10MB for the upload to work. If, however, it still exceeds the size limit, we recommend splitting the spreadsheet among several carriers. 
-</div>
+>⚠️ **OBS:** If your spreadsheet size is over 10MB, you'll need to compress it into a **.zip** format. The .zip file must be less than 10MB for the upload to work. If, however, it still exceeds the size limit, we recommend splitting the spreadsheet among several carriers.
 
 ## Managing shipping rates without using the spreadsheet
 
diff --git a/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 97cccc993..08527d644 100644
--- a/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/en/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -73,11 +73,12 @@ Once disconnected, your integration with TikTok stops completely: TikTok Pixel a
 
 However, VTEX does not delete existing products from TikTok, which means they will continue to appear on TikTok. To delete them from TikTok, you need to manually delete the products in [TikTok Catalog Manager](https://ads.tiktok.com/help/article?aid=10001005).
 
-<div class="alert alert-warning">
-<p>If an error message appears when disconnecting TikTok from your VTEX store, follow the steps below to ensure that the integration has been correctly disabled.</p>
-<ol><li>Go to the <a href="https://ads.tiktok.com/ac/page/authorizations">Authorizations</a> page in TikTok Ads Manager.</li>
-  <li>Find the <strong>VTEX</strong> option.</li>
-  <li>Click <code>Remove</code>.</li></ol>
-</div>
+>⚠️ If an error message appears when disconnecting TikTok from your VTEX store, follow the steps below to ensure that the integration has been correctly disabled.
+>
+> Go to the [Authorizations](https://ads.tiktok.com/ac/page/authorizations) page in TikTok Ads Manager.
+>
+> 2. Find the **VTEX** option.
+>
+> 3. Click `Remove`.
 
 After disconnecting, it is possible to reactivate the integration at any time by repeating the steps described in [Configuring the integration with TikTok for Business](https://help.vtex.com/en/tracks/tiktok-integration--1r0yJSO11nrer1YVu3WTFd/4AEUg7pEdX1beOaQhFf0wC).
diff --git a/docs/tracks/en/merchandising-rule-conditions.md b/docs/tracks/en/merchandising-rule-conditions.md
index af616c674..a0a416cd3 100644
--- a/docs/tracks/en/merchandising-rule-conditions.md
+++ b/docs/tracks/en/merchandising-rule-conditions.md
@@ -22,9 +22,7 @@ Learn about the criteria and possible operators for each type of editing in the
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"> <thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Name</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operators</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Types of editing</th> </tr> </thead> <tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span></td> <td rowspan="2" class="t-body pa5">Word searched by the customer that will be related to the rule. Open input field.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td rowspan="2" class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br>Customization rules </td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contains</span></td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Searches for the exact ID of a catalog element related to the rule. Possible IDs are: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong>, and <strong>EAN</strong>. Open input field.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Customization rules</td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">category</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a category added to the store's catalog. </td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">department</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a department added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">brand</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a brand added to the store's catalog. </td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">productclusternames</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a collection added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promotion</span></td> <td rowspan="2" class="t-body pa5">Selectable value that validates if there is at least one promotion linked to the item (<span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">yes</span>).</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sellername</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents the name of a seller.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategory</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a subcategory added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{specification}}</span></td> <td rowspan="2" class="t-body pa5">Any active catalog specification appears as a custom criterion, with the same possible values. The name of the criterion is exactly the name of the added specification. For example, if there is an active specification called <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>, the displayed criterion is <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> </tbody></table>
 
-<div class="alert alert-warning">
-  <p>The <code>department</code>, <code>category</code>, and <code>subcategory</code> criteria only appear as options to be included in Merchandising Rules if all three category levels are previously configured in the <strong>Catalog</strong>.</p>
-</div>
+>⚠️ The `department`, `category`, and `subcategory` criteria only appear as options to be included in Merchandising Rules if all three category levels are previously configured in the **Catalog**.
 
 ## Operators
 
diff --git a/docs/tracks/en/monitor-da-integracao.md b/docs/tracks/en/monitor-da-integracao.md
index 9532d0869..0f4b4345d 100644
--- a/docs/tracks/en/monitor-da-integracao.md
+++ b/docs/tracks/en/monitor-da-integracao.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugEN: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/next-steps.md b/docs/tracks/en/next-steps.md
index dfa1fdc3c..c9eef798e 100644
--- a/docs/tracks/en/next-steps.md
+++ b/docs/tracks/en/next-steps.md
@@ -16,9 +16,7 @@ trackSlugEN: next-steps-after-the-go-live
 
 Now that the store is configured in the VTEX environment and has [gone live](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), it's time to learn about the features and [add-on solutions](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) available to help increase sales performance and expand operations, contributing to your business's continuous improvement.
 
-<div class="alert alert-warning">
-  <p>Through the <a href="https://partnerportal.vtex.com/">VTEX Partner Portal</a>, you can hire <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">partners</a> to help develop your store and manage the solutions described in this article. To log in to the portal, the user needs <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz">access to a store's VTEX Admin</a>.</p>
-</div>
+>⚠️ Through the [VTEX Partner Portal](https://partnerportal.vtex.com/), you can hire [partners](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) to help develop your store and manage the solutions described in this article. To log in to the portal, the user needs [access to a store's VTEX Admin](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz).
 
 ## VTEX launches
 
diff --git a/docs/tracks/en/order-flow.md b/docs/tracks/en/order-flow.md
index 4cf90e4a5..515f3631d 100644
--- a/docs/tracks/en/order-flow.md
+++ b/docs/tracks/en/order-flow.md
@@ -25,9 +25,7 @@ Order changes - whether caused by the customer, the store, or external systems -
 - __Marketplace__ is the environment where the order is closed, ie, where the customer performs the checkout process.
 - __Seller__ is the owner of the SKU. It is therefore responsible for the fulfillment - that is, for delivering the product to the customer.
 
-<div class="alert alert-info">
-Every store that sells products in its own environment and makes its own deliveries is a Marketplace and a Seller at the same time.
-</div>
+>ℹ️ Every store that sells products in its own environment and makes its own deliveries is a Marketplace and a Seller at the same time.
 
 It's important to understand these concepts because the Marketplace's order flow is different from the Seller's order flow.
 
@@ -71,14 +69,13 @@ Once the payment has been approved, the order goes to `Payment Approved` and the
 
 That is, in this case both payment and delivery steps are the store's responsibility.
 
-<div class="alert alert-info">
-There are only two possible final statuses for every order:<br>
-<ul>
-  <li>Invoiced</li>
-  <li>Canceled</li>
-</ul>
-</div>
-
-<div class="alert alert-info">
-To understand each order status in more detail, see a table with all statuses at <a href="https://help.vtex.com/en/tutorial/fluxo-de-pedido--tutorials_196#understanding-the-status">Understanding the Status</a>.
-</div>
+>ℹ️ There are only two possible final statuses for every order:
+>
+> 
+>
+> * Invoiced
+>
+> * Canceled
+> 
+
+>ℹ️ To understand each order status in more detail, see a table with all statuses at [Understanding the Status](https://help.vtex.com/en/tutorial/fluxo-de-pedido--tutorials_196#understanding-the-status).
diff --git a/docs/tracks/en/pickup-points-concept-definition.md b/docs/tracks/en/pickup-points-concept-definition.md
index cdb2a88b1..c347dc300 100644
--- a/docs/tracks/en/pickup-points-concept-definition.md
+++ b/docs/tracks/en/pickup-points-concept-definition.md
@@ -16,9 +16,7 @@ trackSlugEN: logistics-101
 
 A pickup point is a physical place from where customers can retrieve their packages by themselves. It is an optional step that closes the logistics route. 
 
-<div class="alert alert-info">
-The functionality of pickup points is only available to accounts that already use <b>Checkout V6</b>.
-</div>
+>ℹ️ The functionality of pickup points is only available to accounts that already use **Checkout V6**.
 
 
 ## Relationship with the carrier
diff --git a/docs/tracks/en/pickup-store.md b/docs/tracks/en/pickup-store.md
index 7e9075923..9b02209f5 100644
--- a/docs/tracks/en/pickup-store.md
+++ b/docs/tracks/en/pickup-store.md
@@ -14,9 +14,7 @@ trackId: t3DOYAJjWgqAMeAKq2MWS
 trackSlugEN: instore-setup
 ---
 
-<div class="alert alert-info">
-Warning: This documentation is being updated to reflect the concept change from Pannels to <a href="https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">shipping strategy</a>.
-</div>
+>ℹ️ Warning: This documentation is being updated to reflect the concept change from Pannels to [shipping strategy](https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 
 To set up the inStore with __Delivery at Home__, that is, to consider the inventory of your physical store, you need to do two things:
diff --git a/docs/tracks/en/planning-the-go-live.md b/docs/tracks/en/planning-the-go-live.md
index 8e1b86567..6ac22e079 100644
--- a/docs/tracks/en/planning-the-go-live.md
+++ b/docs/tracks/en/planning-the-go-live.md
@@ -68,9 +68,7 @@ After the official launch date, when the store is fully operational, developers
 
 Before going live, you must ensure that all essential settings are configured for your store to operate smoothly. To do this, we recommend checking the [Store configuration checklist](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx). Each item must be checked to ensure the settings have been completed to meet the store's operational characteristics.
 
-<div class="alert alert-warning">
-  <p>The checklist above lists basic features and settings necessary for running a VTEX store. It is up to each store's<a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners"> implementation team</a> to determine the features and settings to apply to deliver the desired shopping experience for customers. We recommend checking all the store's operational aspects and adding them to the list, if necessary.</p>
-</div>
+>⚠️ The checklist above lists basic features and settings necessary for running a VTEX store. It is up to each store's[ implementation team](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) to determine the features and settings to apply to deliver the desired shopping experience for customers. We recommend checking all the store's operational aspects and adding them to the list, if necessary.
 
 ## 3. Domain and account settings
 
@@ -80,9 +78,7 @@ Once the store's internal settings have been completed, you'll need to configure
 2. [Configure CAA records](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#configuring-caa-records): Indicate that the **Let's Encrypt** certificate authority (CA) is authorized to generate and renew certificates attesting to the domain's identity. This step is only necessary if there is a CAA record on the DNS server.
 3. [Put your account in production](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#putting-your-account-into-production): Activate the VTEX account in production. Even after this activation, the store remains unavailable for access by external customers. Viewing and purchasing products in the store will only be possible after the go-live has been completed, according to the steps described in the following sections of this article.
 
-<div class="alert alert-warning">
-  <p>Once the account is active in production, all orders will be automatically charged, and the <a href="https://help.vtex.com/en/tutorial/understanding-the-value-of-approved-revenues--tutorials_4322#understanding-the-values-of-approved-revenues">take rate</a> will be applied based on the plan agreed upon with VTEX. This includes orders placed on the <code>{accountname}.myvtex.com</code> domain, even if they were placed for testing purposes.</p>
-</div>
+>⚠️ Once the account is active in production, all orders will be automatically charged, and the [take rate](https://help.vtex.com/en/tutorial/understanding-the-value-of-approved-revenues--tutorials_4322#understanding-the-values-of-approved-revenues) will be applied based on the plan agreed upon with VTEX. This includes orders placed on the `{accountname}.myvtex.com` domain, even if they were placed for testing purposes.
 
 For more information, see the [Settings](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX) article, which is part of the detailed [Go-live](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/1iP90RcJvlrfQhnlxM54wo) track article.
 
@@ -94,9 +90,7 @@ On VTEX, you can create separate environments to run these tests. In this case,
 
 To plan the testing step, contact [our support](https://help.vtex.com/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy) team, so you can [request a test environment](https://help.vtex.com/en/tutorial/requesting-a-test-environment--2nmZAHlfQoGsCWmEWGIoGy).
 
-<div class="alert alert-warning">
-  <p>If the store is<a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#development-environment"> built using VTEX IO</a>, you can run A/B tests between workspaces, i.e., compare the performance of storefront development environments. For more details, see the<a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing"> Running A/B tests</a> developer guide.</p>
-</div>
+>⚠️ If the store is[ built using VTEX IO](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#development-environment), you can run A/B tests between workspaces, i.e., compare the performance of storefront development environments. For more details, see the[ Running A/B tests](https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing) developer guide.
 
 ### Quality Assurance (QA)
 
@@ -116,9 +110,7 @@ Once the necessary tests and fixes have been completed, you must prepare the sto
 
 1. [Register the domain on VTEX](https://help.vtex.com/en/tutorial/configuring-domains-in-account-management--tutorials_2450): Go to **Account settings** in the VTEX Admin to connect the address to the store.
 
-   <div class="alert alert-warning">
-    <p>Once you have registered the domain, you have seven days to complete the go-live. If the store does not complete the necessary go-live procedures within this period, you will need to go back to the registration and save it again.</p>
-   </div>
+   >⚠️ Once you have registered the domain, you have seven days to complete the go-live. If the store does not complete the necessary go-live procedures within this period, you will need to go back to the registration and save it again.
 
 2. **Request internal pointing:** Open a ticket to [VTEX Support](https://help.vtex.com/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy) to request internal DNS pointing. It can take up to three working days to complete this request.
 
@@ -152,9 +144,7 @@ Regardless of the request type, the ticket to VTEX Support must have the followi
 - Indicate if the store has conditional rules for [trade policies](https://help.vtex.com/en/tutorial/creating-a-trade-policy--563tbcL0TYKEKeOY4IAgAE).
 - If you are migrating a live site to VTEX, indicate whether it uses the Azion CDN or Cloudfront.
 
-<div class="alert alert-warning">
-  <p>After receiving confirmation of the internal pointing, you are required to complete the standard DNS pointing within five days. Otherwise, the internal pointing will be deleted, and you must submit a new request.</p>
-</div>
+>⚠️ After receiving confirmation of the internal pointing, you are required to complete the standard DNS pointing within five days. Otherwise, the internal pointing will be deleted, and you must submit a new request.
 
 ## 6. Go-live
 
@@ -162,15 +152,11 @@ At the time of go-live, after confirming the internal pointing from the previous
 
 1. [Set up DNS pointing](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#setting-up-dns-pointing): In the domain's DNS zone, create a CNAME entry in the desired subdomain for the destination ``{domain}.cdn.vtex.com``. The ``{domain}`` must be the same as the one registered on VTEX.
 
-   <div class="alert alert-warning">
-    <p>DNS propagation pointing can take between 24 and 48 hours. As a result, the configured address might not be immediately accessible to everyone after the configuration.</p>
-   </div>
+   >⚠️ DNS propagation pointing can take between 24 and 48 hours. As a result, the configured address might not be immediately accessible to everyone after the configuration.
 
 2. [Notify the pointing:](https://help.vtex.com/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#notifying-the-pointing) To make your store available to the general public, you must notify the VTEX platform that pointing has been completed. To do this, you must save your **Account settings** in the VTEX Admin again.
 
-   <div class="alert alert-warning">
-    <p>If the store was built using<a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#faststore"> FastStore</a>, you will also need to follow the steps described in the<a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns"> Configuring external DNS for a custom domain</a> article.</p>
-   </div>
+   >⚠️ If the store was built using[ FastStore](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#faststore), you will also need to follow the steps described in the[ Configuring external DNS for a custom domain](https://www.faststore.dev/docs/go-live/2-configuring-external-dns) article.
 
 Once the above steps have been completed, the store will be available on the registered domain, allowing customers to access it and make purchases.
 
diff --git a/docs/tracks/en/pre-go-live.md b/docs/tracks/en/pre-go-live.md
index 2275dd4ac..13848a7f1 100644
--- a/docs/tracks/en/pre-go-live.md
+++ b/docs/tracks/en/pre-go-live.md
@@ -20,9 +20,7 @@ This stage initiates the go-live as these steps need to be carefully scheduled b
 
 To connect the domain to the store, you must [register the domain in Account Management](https://help.vtex.com/en/tutorial/configurando-dominios-no-license-manager).
 
-<div class="alert alert-warning">
-After registering your domain, you have seven days to complete the go-live. Otherwise, you must go back to the registration and save it again.
-</div>
+>⚠️ After registering your domain, you have seven days to complete the go-live. Otherwise, you must go back to the registration and save it again.
 
 ## Requesting IO pointing
 
diff --git a/docs/tracks/en/preco-fixo-definicao-de-conceito.md b/docs/tracks/en/preco-fixo-definicao-de-conceito.md
index d7191119c..f2dbd0be9 100644
--- a/docs/tracks/en/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/en/preco-fixo-definicao-de-conceito.md
@@ -22,9 +22,7 @@ The fixed price therefore overlaps the __base price__, even when a __price rule_
 
 This means that for a price table, the fixed price has priority over both the base price and the configured price rule.
 
-<div class="alert alert-warning">
-  <p>Only <a href="https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj">fixed prices</a> are used by our native marketplace integrations. Other scenarios seen in our <a href="https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx">price system architecture</a> are available only in VTEX marketplaces.</p>
-</div>
+>⚠️ Only [fixed prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj) are used by our native marketplace integrations. Other scenarios seen in our [price system architecture](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) are available only in VTEX marketplaces.
 
 ## Functionalities
 
diff --git a/docs/tracks/en/printing-an-order-summary.md b/docs/tracks/en/printing-an-order-summary.md
index edf9cc087..1c64e7f77 100644
--- a/docs/tracks/en/printing-an-order-summary.md
+++ b/docs/tracks/en/printing-an-order-summary.md
@@ -38,9 +38,7 @@ To pair VTEX Sales App with a printer, the following prerequisites must be met:
 * Having VTEX Sales App installed on your computer. If you do not have it, you must install the app by following our [Installation](https://help.vtex.com/en/tracks/instore-using-the-app--4BYzQIwyOHvnmnCYQgLzdr/2rPSJ8519UCCZo5uEBkqxh) guide.
 * Obtaining a pair of credentials (AppKey and AppToken) with the corresponding access permissions. For more information, please refer to the article [Application keys](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet).
 
-<div class="alert alert-info">
-<p>We recommend that the access profile associated with these credentials be the <strong>VTEX Sales App Sales Person</strong>. However, you can also use a profile with access to other Admin modules, such as <strong>Super Admin</strong>.</p>
-</div>
+>ℹ️ We recommend that the access profile associated with these credentials be the **VTEX Sales App Sales Person**. However, you can also use a profile with access to other Admin modules, such as **Super Admin**.
 
 ### Step-by-step instructions
 
diff --git a/docs/tracks/en/promotions-for-specific-scenarios.md b/docs/tracks/en/promotions-for-specific-scenarios.md
index 19a07eab7..262bb7c29 100644
--- a/docs/tracks/en/promotions-for-specific-scenarios.md
+++ b/docs/tracks/en/promotions-for-specific-scenarios.md
@@ -25,9 +25,7 @@ In order to meet these scenarios, we offer the following types of promotions:
 - Progressive Discount
 - Buy One Get One
 
-<div class="alert alert-info">
-The configuration screens for any of the promotions mentioned above follow the same main sections as those explained in the Regular Promotion article. The options in these sections repeat themselves throughout the promotions, with the exception of some specific configurations regarding which conditions to apply the promotion to. Therefore, this article will focus on these specific configurations.
-</div>
+>ℹ️ The configuration screens for any of the promotions mentioned above follow the same main sections as those explained in the Regular Promotion article. The options in these sections repeat themselves throughout the promotions, with the exception of some specific configurations regarding which conditions to apply the promotion to. Therefore, this article will focus on these specific configurations.
 
 ### Buy Together - Bundle
 
@@ -85,9 +83,7 @@ To understand the Buy One Get One promotion in more detail, read our article on
 
 This setting determines how many items in the cart will be affected by a promotion. 
 
-<div class="alert alert-warning">
-It is important to note that such restrictions are only <strong>valid for regular promotions with percentage discounts</strong>.
-</div>
+>⚠️ It is important to note that such restrictions are only **valid for regular promotions with percentage discounts**.
 
 After filling in all the [regular promotion fields](https://help.vtex.com/en/tutorial/regular-promotion--tutorials_327) with the percentage discount, you can __set a maximum number of items affected per cart__ by checking the box for this option, found in the __restrictions__ section.
 
diff --git a/docs/tracks/en/redirect.md b/docs/tracks/en/redirect.md
index ed8580602..316bccf10 100644
--- a/docs/tracks/en/redirect.md
+++ b/docs/tracks/en/redirect.md
@@ -16,9 +16,7 @@ trackSlugEN: vtex-intelligent-search
 
 The **Redirects** feature directs customers to another page, either internal or external to the store. This redirection is done in the search area of your storefront, using terms or filters selected by the customer. This way, one of the advantages of the Redirects feature is to contemplate communication scenarios that are not covered by the store's catalog search, such as redirecting a search for a brand to its promotional page.
 
-<div class="alert alert-warning">
-<p>This feature is available in VTEX Intelligent Search: Multilanguage. To learn more, please refer to our article VTEX Intelligent Search: Multilanguage settings (Beta).</p>
-</div>
+>⚠️ This feature is available in VTEX Intelligent Search: Multilanguage. To learn more, please refer to our article VTEX Intelligent Search: Multilanguage settings (Beta).
 
 ## How redirects work
 
diff --git a/docs/tracks/en/register-the-barcode-of-the-skus-for-instore.md b/docs/tracks/en/register-the-barcode-of-the-skus-for-instore.md
index 5814969a4..13ed105a2 100644
--- a/docs/tracks/en/register-the-barcode-of-the-skus-for-instore.md
+++ b/docs/tracks/en/register-the-barcode-of-the-skus-for-instore.md
@@ -16,9 +16,7 @@ trackSlugEN: register-the-barcode-of-the-skus-for-the-instore
 
 To use the VTEX Sales App, products from the physical store must be added to the Catalog of your VTEX account. It's there that we insert all products and define their characteristics.
 
-<div class="alert alert-warning">
-Salespeople will only have access to products via VTEX Sales App once they are added to your store's catalog on VTEX.
-</div>
+>⚠️ Salespeople will only have access to products via VTEX Sales App once they are added to your store's catalog on VTEX.
 
 Among the information entered during the registration of a product in the Catalog, is the __EAN__. The EAN corresponds to the __barcode__ of the SKU. It's this code that allows the sales associate to easily add the product to the VTEX Sales App cart by reading the product's barcode. VTEX Sales App also allows the barcode to be entered in the search field.
 
@@ -35,6 +33,4 @@ To add the SKU's EAN, follow the steps below:
 
 Alternatively, the EAN field, as well as other SKU fields, can be filled out in bulk using a spreadsheet or your ERP. Check out the [Adding SKUs article](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ) for detailed information.
 
-<div class="alert alert-info">
-EAN information can take up to 10 minutes to update. After this procedure, it will be possible to add the SKU to the VTEX Sales App cart through the barcode reader machine.
-</div>
+>ℹ️ EAN information can take up to 10 minutes to update. After this procedure, it will be possible to add the SKU to the VTEX Sales App cart through the barcode reader machine.
diff --git a/docs/tracks/en/regra-de-preco-definicao-de-conceito.md b/docs/tracks/en/regra-de-preco-definicao-de-conceito.md
index 1ae353c73..ebae00df9 100644
--- a/docs/tracks/en/regra-de-preco-definicao-de-conceito.md
+++ b/docs/tracks/en/regra-de-preco-definicao-de-conceito.md
@@ -22,9 +22,7 @@ Price rules allow you to change the price of an SKU in a price table __without c
 
 However, when we combine this price rule with the SKU's base price, a new value is obtained. This value will represent the SKU's __computed price__ within a price table.
 
-<div class="alert alert-info">
-Using price rules is <strong>optional</strong>. If an SKU is not linked to any modifiers, its price in the price table in question will be the registered base price.
-</div>
+>ℹ️ Using price rules is **optional**. If an SKU is not linked to any modifiers, its price in the price table in question will be the registered base price.
 
 Price rules have __five configuration settings__:
 
diff --git a/docs/tracks/en/relevance.md b/docs/tracks/en/relevance.md
index 6e73145d5..e1b127284 100644
--- a/docs/tracks/en/relevance.md
+++ b/docs/tracks/en/relevance.md
@@ -38,9 +38,7 @@ The information considered for the relevance is:
 
 The set of weights and criteria distribution generates a score for the product, which determines its position in the search result ranking.
 
-<div class="alert alert-warning">
-  <p>IIf you want to use priority criteria, we recommend adding only one criterion in this field. Adding more criteria compromises the ordering or search results, since only the first criterion will be considered.</p>
-</div>
+>⚠️ IIf you want to use priority criteria, we recommend adding only one criterion in this field. Adding more criteria compromises the ordering or search results, since only the first criterion will be considered.
 
 So you can tailor the behavior of the search results to a specific strategy.
 
diff --git a/docs/tracks/en/reports-vtex-intelligent-search.md b/docs/tracks/en/reports-vtex-intelligent-search.md
index 3bfd24c1d..f774d5b39 100644
--- a/docs/tracks/en/reports-vtex-intelligent-search.md
+++ b/docs/tracks/en/reports-vtex-intelligent-search.md
@@ -40,9 +40,7 @@ The report data is updated every four hours and contains the following informati
 * **Orders**: number of orders placed from the search results. To calculate this metric, we consider all orders placed after the customer clicked on a search result, even if they ended up buying a different product than the one they clicked on.
 * **Sales**: the total revenue generated by orders placed from the search results. The calculation follows the same logic as the **Orders** metric, the difference being that the result reflects the revenue instead of the number of orders.
 
-<div class="alert alert-info">
-  <p>The data displayed in the report is limited to the top 10,000 search terms. If you want the complete search data for your store, you must <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exporting-reports">export the report</a>.</p>
-</div>
+>ℹ️ The data displayed in the report is limited to the top 10,000 search terms. If you want the complete search data for your store, you must [export the report](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exporting-reports).
 
 When you opt to [export a report](#exporting-reports), you can generate it **With funnel metrics**. If this option is selected, four new columns will be added to the file:
 
diff --git a/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md b/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md
index c4251a74b..b1bebf6f3 100644
--- a/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md
+++ b/docs/tracks/en/scheduled-deliveries-and-delivery-capacity.md
@@ -18,9 +18,9 @@ A VTEX store can offer scheduled deliveries to its customers. With this option,
 
 To offer [scheduled deliveries](https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi), you must add delivery windows to the [shipping policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140) of the [carrier](https://help.vtex.com/en/tutorial/carries-on-vtex--7u9duMD5UQa2QQwukAWMcE) in question. Once this is done, the periods and days available for this type of delivery will be displayed at your store's checkout. 
 
-<div class="alert alert-warning">
-For <a href="https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a> and <a href="https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Delivery capacity</a> to perform correctly, you must follow the rules below:<p><ul><li>The result from {<a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {shipping policy ID} cannot exceed 60 characters.</li><li>Do not use spaces in <a href="https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">shipping policy IDs</a>.</li></ul></p>
-</div>
+>⚠️ For [Scheduled delivery](https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) and [Delivery capacity](https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) to perform correctly, you must follow the rules below:
+> *The result from {[account name](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {shipping policy ID} cannot exceed 60 characters.
+> * Do not use spaces in [shipping policy IDs](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 Please note that the availability of scheduled deliveries depends on the services offered by the contracted carrier to your store, as defined in the shipping policy. You can track the availability of delivery windows and the number of items/orders that can still be placed in each delivery window on the [Delivery capacity](https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) page.
 
diff --git a/docs/tracks/en/seeing-order-details.md b/docs/tracks/en/seeing-order-details.md
index 6cd18d360..a2f630e5f 100644
--- a/docs/tracks/en/seeing-order-details.md
+++ b/docs/tracks/en/seeing-order-details.md
@@ -49,9 +49,7 @@ In VTEX platform there is also a feature to unify all email communication with t
 
 All customer data is entered at the time of closing the order and cannot be changed here. To view and manage this data, you can access Master Data.
 
-<div class="alert alert-info">
-If your store only acts as a seller of an order, the customer's email will not be displayed. We understand that the customer's relationship is with the marketplace, so it is not advisable to share your data with the seller without prior consent.
-  </div>
+>ℹ️ If your store only acts as a seller of an order, the customer's email will not be displayed. We understand that the customer's relationship is with the marketplace, so it is not advisable to share your data with the seller without prior consent.
 
 ### Total Value
 
diff --git a/docs/tracks/en/sending-product-data-to-dafiti.md b/docs/tracks/en/sending-product-data-to-dafiti.md
index e1c772f02..a120c3418 100644
--- a/docs/tracks/en/sending-product-data-to-dafiti.md
+++ b/docs/tracks/en/sending-product-data-to-dafiti.md
@@ -14,4 +14,4 @@ trackId: 4wF4RBx9ygEkimW6SsKw8i
 trackSlugEN: dafiti-integration-setup
 ---
 
-<div class="alert alert-warning">This is a regional exclusive content not applicable to English speaking countries.</div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tracks/en/sending-products-to-amazon.md b/docs/tracks/en/sending-products-to-amazon.md
index 4c849b5c6..0599b7515 100644
--- a/docs/tracks/en/sending-products-to-amazon.md
+++ b/docs/tracks/en/sending-products-to-amazon.md
@@ -18,16 +18,13 @@ Once you have configured the initial integration settings, you can send the prod
 
 To send your products to Amazon, you need to map the product [categories](https://help.vtex.com/en/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) and [attributes](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).  
 
-<div class="alert alert-info">
-Your products need to have the <a href="https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">warehouse</a> and <a href="https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">price</a> configured before sending them to Amazon.  </div>
+>ℹ️ Your products need to have the [warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) and [price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) configured before sending them to Amazon.
 
 ## Mapping categories  
 
 The mapping process can be done through the [VTEX Admin](#mapping-through-the-vtex-admin), or a [spreadsheet](#mapping-via-spreadsheet). See below how to do it in each case. 
 
-<div class="alert alert-danger">
-When mapping a category using the VTEX Admin, the category mapping previously done via a spreadsheet will be overwritten and cannot be recovered.
-</div>  
+>❗ When mapping a category using the VTEX Admin, the category mapping previously done via a spreadsheet will be overwritten and cannot be recovered.  
 
 ### Mapping through the VTEX Admin (BETA)  
 
@@ -54,10 +51,10 @@ To map a category, follow these steps:
 4. Match the attributes in the side window, as shown in the image below: ![Amazon Mapper Attributes](https://downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/da4ea7365efc744b036e55305feaea6f/mapper_amazon_atributos.gif)  
 5. Click the `Save Changes` button.  
 
-<div class="alert alert-danger">
-Fields with an * asterisks are required.
-<br>Completing an attribute can trigger new required fields that only become visible under <b>Marketplace > Connections > Products</b> after the mapping has been saved.</br>
-</div>
+>❗ Fields with an * asterisks are required.
+>
+>
+> Completing an attribute can trigger new required fields that only become visible under **Marketplace > Connections > Products** after the mapping has been saved.</br>
 
 ### Mapping via spreadsheet  
 
@@ -180,9 +177,7 @@ The template contains the following columns:
 | F | VTEXValue | Name of the value used in the SKU field on the VTEX platform |
 | G | AmazonValue | Name of the values accepted by Amazon |
 
-<div class="alert alert-info">
-The Amazon mapping template is case-sensitive.
-</div>
+>ℹ️ The Amazon mapping template is case-sensitive.
 
 Follow the steps below for each product:
 
@@ -199,9 +194,7 @@ Follow the steps below for each product:
 6. Fill in the **VTEXValue** column with the values of the product attribute on VTEX.
 7. Fill in the **AmazonValue** column with the attribute values accepted by Amazon. To view the values accepted by Amazon, go to the [Amazon required attribute spreadsheet](#2-amazon-attributes-template) and look for the `VALORES VÁLIDOS` tab.
 
-<div class="alert alert-warning">
-Depending on the category, the <b>VariationTheme</b> values may be similar. There are categories in which <b>VariationTheme</b> can be: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, while there are other categories in which it can be: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. The difference is in the order. In <i>SizeColor</i>, the checkboxes on the product page will be sorted by size and color, while in <i>ColorSize</I> they will be sorted by color and size. Pay attention to the values valid for each category that will be mapped. 
-</div>
+>⚠️ Depending on the category, the **VariationTheme** values may be similar. There are categories in which **VariationTheme** can be: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, while there are other categories in which it can be: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. The difference is in the order. In <i>SizeColor</i>, the checkboxes on the product page will be sorted by size and color, while in <i>ColorSize</I> they will be sorted by color and size. Pay attention to the values valid for each category that will be mapped.
 
 #### Example
 
diff --git a/docs/tracks/en/sending-products-to-facebook.md b/docs/tracks/en/sending-products-to-facebook.md
index c15644f84..ec8df0291 100644
--- a/docs/tracks/en/sending-products-to-facebook.md
+++ b/docs/tracks/en/sending-products-to-facebook.md
@@ -32,9 +32,7 @@ If you want to send product attributes to Facebook, an additional step needs to
 
 The additional step is mapping product specifications. Mapping allows matching the attributes from your VTEX store with the standards adopted by Facebook.
 
-<div class="alert alert-warning">
-ttribute mapping via spreadsheet is optional, but if you choose to do it, it must be done completely. Otherwise, it may lead to integration errors.
-</div>
+>⚠️ ttribute mapping via spreadsheet is optional, but if you choose to do it, it must be done completely. Otherwise, it may lead to integration errors.
 
 ## Sending attributes to Facebook
 
@@ -54,9 +52,7 @@ The first step in mapping is to download the file [Facebook Mapping Spreadsheet.
 
 The second step is to fill in the downloaded file. The spreadsheet consists of a single tab with five columns.
 
-<div class="alert alert-info">
-The Facebook mapping spreadsheet is case-sensitive.
-</div>
+>ℹ️ The Facebook mapping spreadsheet is case-sensitive.
 
 - **First column, _ID Category_:** must be filled in with the identification number of the product category on the VTEX platform. You can find the ID of a category in the Admin, in _Products > Catalog > Categories_. The category ID is the number to the left of the category name.
 - **Second column, _VTEX attribute name_:** must contain the name of the attribute on the VTEX platform.
@@ -65,9 +61,7 @@ The Facebook mapping spreadsheet is case-sensitive.
 - **Third column, _Facebook attribute name_:** must be populated with the corresponding term used by Facebook.
 > Example: the match for the _Cor_ attribute on Facebook is _Color_.
 
-  <div class="alert alert-info">
-For attribute names and reference values, refer to Facebook’s <a href="https://developers.facebook.com/docs/commerce-platform/catalog/fields?locale=en_US#universal-basic-attributes">Universal Basic Attributes</a> documentation. If there is no match for an attribute or value, populate the Facebook attribute name column with the same term used on VTEX.
-</div>
+  >ℹ️ For attribute names and reference values, refer to Facebook’s [Universal Basic Attributes](https://developers.facebook.com/docs/commerce-platform/catalog/fields?locale=en_US#universal-basic-attributes) documentation. If there is no match for an attribute or value, populate the Facebook attribute name column with the same term used on VTEX.
 
  **Fourth column, _VTEX attribute value_:** should be filled in with the values for your attributes on VTEX.
 > Example: let's say that one of the values for the gender attribute in your VTEX store is _Feminino_. Therefore, you should fill in the _VTEX attribute value_ column with the word _Feminino_.
diff --git a/docs/tracks/en/sending-products-to-google-shopping.md b/docs/tracks/en/sending-products-to-google-shopping.md
index b4b94633b..d7d05ac56 100644
--- a/docs/tracks/en/sending-products-to-google-shopping.md
+++ b/docs/tracks/en/sending-products-to-google-shopping.md
@@ -50,9 +50,7 @@ A product may eventually report the Insertion error: `Ineligible SKU`. This mean
 
 **If a product is disapproved, you will have to review its data and submit it again**. You can track the status of your products on Google Merchant Center.
 
-<div class="alert alert-info">
-Make sure your products meet the <a href="https://support.google.com/merchants/answer/7052112?visit_id=637492777706451215-3729304881&rd=1&hl=en">Product data specification</a> defined by Google. If a product is not in compliance with the requirements, the ad will be disapproved.
-</div>
+>ℹ️ Make sure your products meet the [Product data specification](https://support.google.com/merchants/answer/7052112?visit_id=637492777706451215-3729304881&rd=1&hl=en) defined by Google. If a product is not in compliance with the requirements, the ad will be disapproved.
 
 There are situations in which the product's disapproval happens after it has already been considered active. It happens more often for recently created accounts.
 
@@ -66,9 +64,7 @@ On Google Shopping, products automatically expire if they are not updated within
 
 However, you do not have to worry about that. Once the integration with the VTEX Platform connector is completed, **the system will automatically update products every 29 days.**
 
-<div class="alert alert-info">
-There may be a delay of up to 30 minutes between processing a product's data change and updating it in the feed.
-</div>
+>ℹ️ There may be a delay of up to 30 minutes between processing a product's data change and updating it in the feed.
 
 ## Modifying the automatic categorization
 
@@ -80,6 +76,4 @@ However, before considering there may be a categorization issue, make sure that
 
 To replace an incorrect category and ensure that the product will be approved, see the step-by-step instructions in the article [Google product category](https://support.google.com/merchants/answer/6324436?hl=en).
 
-<div class="alert alert-warning">
-Google will accept category changes only in the cases foreseen in the article <a href="https://support.google.com/merchants/answer/6324436?hl=en">Google product category.</a>
-</div>
+>⚠️ Google will accept category changes only in the cases foreseen in the article [Google product category.](https://support.google.com/merchants/answer/6324436?hl=en)
diff --git a/docs/tracks/en/set-a-price-for-the-sku.md b/docs/tracks/en/set-a-price-for-the-sku.md
index 94d5ecf45..cda16154a 100644
--- a/docs/tracks/en/set-a-price-for-the-sku.md
+++ b/docs/tracks/en/set-a-price-for-the-sku.md
@@ -16,9 +16,7 @@ trackSlugEN: vtex-getting-started
 
 Any SKU in your store needs a price to be displayed to the end user.
 
-<div class="alert alert-warning">
-Even an SKU that will be offered as a gift needs to have a price.
-</div>
+>⚠️ Even an SKU that will be offered as a gift needs to have a price.
 
 To register the price, follow the steps below.
 1. In the __Catalog__ module, hover over __Products Management__ tab, go to __Products and SKUs__ and click the __Products and SKUs Management__ option.
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
index 35ff11781..fa92bfe55 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy-2.md
@@ -38,8 +38,7 @@ In order to define the product catalog that will be sent to the marketplace, the
 4. Check the __Sales Policies__ flag for the chosen sales policies.
 5. Click __Save__.
 
-<div class="alert alert-danger"> VTEX does not recommend performing product catalog management for marketplace through collections. This mechanism brings many complexities in the organization. We recommend managing it through the Sales Policies flag instead.
-</div>
+>❗ VTEX does not recommend performing product catalog management for marketplace through collections. This mechanism brings many complexities in the organization. We recommend managing it through the Sales Policies flag instead.
 
 ## Defining the logistics
 
diff --git a/docs/tracks/en/setting-up-a-marketplace-trade-policy.md b/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
index ff0878c7d..33b7d66c9 100644
--- a/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/en/setting-up-a-marketplace-trade-policy.md
@@ -39,8 +39,7 @@ In order to define the product catalog that will be sent to the marketplace, the
 4. Check the __Sales Policies__ flag for the chosen sales policies.
 5. Click __Save__.
 
-<div class="alert alert-danger"> VTEX does not recommend performing product catalog management for marketplace through collections. This mechanism brings many complexities in the organization. We recommend managing it through the Sales Policies flag instead.
-</div>
+>❗ VTEX does not recommend performing product catalog management for marketplace through collections. This mechanism brings many complexities in the organization. We recommend managing it through the Sales Policies flag instead.
 
 ## Defining the logistics
 
diff --git a/docs/tracks/en/setting-up-a-smart-campaign.md b/docs/tracks/en/setting-up-a-smart-campaign.md
index 80a8e86af..be5db4e64 100644
--- a/docs/tracks/en/setting-up-a-smart-campaign.md
+++ b/docs/tracks/en/setting-up-a-smart-campaign.md
@@ -30,12 +30,8 @@ Follow this step-by-step to set it up:
     <br/>&bull; __Set a desired Return on Advertising Spend (ROAS):__ When marking this flag you must define which ROAS the campaign should pursue.
      <br/>_`Ex:` If you set a 800% ROAS, it means that for every $ 1.00 spent on the campaign it should convert $ 8.00._
 
-<div class="alert alert-warning">
-<strong>Note: We do not recommend setting up a ROAS</strong> as soon as you start a campaign for the first time. This is because the campaign needs some time before it learns how to deliver products on the search, which can take up to 4 weeks, according to Google. So until it's mature it is advisable not to set up a ROAS.
-</div>
+>⚠️ **Note: We do not recommend setting up a ROAS** as soon as you start a campaign for the first time. This is because the campaign needs some time before it learns how to deliver products on the search, which can take up to 4 weeks, according to Google. So until it's mature it is advisable not to set up a ROAS.
 
-<div class="alert alert-warning">
-<strong>Note 2:</strong> We also recommend that the <strong>campaign setting is not changed</strong> during the first 4 weeks, precisely because of the time the artificial intelligence needs to complete its initial learning process.
-</div>
+>⚠️ **Note 2:** We also recommend that the **campaign setting is not changed** during the first 4 weeks, precisely because of the time the artificial intelligence needs to complete its initial learning process.
 
 *__That's all!__ You now have your campaign set up and within a few days you should start seeing results in the app dashboard.*
diff --git a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
index e7730f273..902d2a7ef 100644
--- a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -36,9 +36,7 @@ If necessary, InStore can send additional information. Example with the sub-acqu
 - `administrativePassword`: string - default password. For example, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-To create any extra configuration, you need to send to the inStore team (instoredevs@vtex.com.br) every extra the app needs to complete the transaction. With that, we will create a form on Payments so that customers can configure their acquirer.
-</div>
+>ℹ️ To create any extra configuration, you need to send to the inStore team (instoredevs@vtex.com.br) every extra the app needs to complete the transaction. With that, we will create a form on Payments so that customers can configure their acquirer.
 
 ## Sending URI and response URI for each action
 
@@ -185,9 +183,7 @@ For the integration to work, the customer must set up the InStore connector on P
 
 AppLinking integration doesn't include other dependencies, since communication between the inStore application and the payment application happens with specific URIs containing all the configuration and payment parameters required for the action.
 
-<div class="alert alert-warning">
-On Android, all communication must happen with a new <code>Intent</code>. This means that you should not send the response as a callback from the initial <code>Intent</code> call. Instead, send a new <code>Intent</code> to the inStore application with the previous response.
-</div>
+>⚠️ On Android, all communication must happen with a new `Intent`. This means that you should not send the response as a callback from the initial `Intent` call. Instead, send a new `Intent` to the inStore application with the previous response.
 
 To configure the inStore connector, follow the steps below:
 
diff --git a/docs/tracks/en/setting-up-instore-as-a-pos.md b/docs/tracks/en/setting-up-instore-as-a-pos.md
index c9bb54a4d..16fd1b8ea 100644
--- a/docs/tracks/en/setting-up-instore-as-a-pos.md
+++ b/docs/tracks/en/setting-up-instore-as-a-pos.md
@@ -22,9 +22,7 @@ First of all, you must consider the prerequisites that your store needs to ensur
 
 ## Implement inStore as a POS
 
-<div class="alert alert-info">
-Although it is possible to implement inStore as a POS in other ways, in this article we explain how to do it using the franchise account and White Label Seller features. This is the architecture most recommended by VTEX for this type of project.
-</div>
+>ℹ️ Although it is possible to implement inStore as a POS in other ways, in this article we explain how to do it using the franchise account and White Label Seller features. This is the architecture most recommended by VTEX for this type of project.
 
 These are the steps to implement inStore as a POS:
 
diff --git a/docs/tracks/en/setting-up-pix.md b/docs/tracks/en/setting-up-pix.md
index fc70c49fd..8bab8c08d 100644
--- a/docs/tracks/en/setting-up-pix.md
+++ b/docs/tracks/en/setting-up-pix.md
@@ -14,6 +14,4 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugEN: instore-payments
 ---
 
-<div class="alert alert-warning">
-<p>This is a regional exclusive content not applicable to English speaking countries.</p>
-</div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tracks/en/setting-up-the-ads-template-description-in-mercado-livre.md b/docs/tracks/en/setting-up-the-ads-template-description-in-mercado-livre.md
index a7d16f894..ce7c212d2 100644
--- a/docs/tracks/en/setting-up-the-ads-template-description-in-mercado-livre.md
+++ b/docs/tracks/en/setting-up-the-ads-template-description-in-mercado-livre.md
@@ -18,9 +18,7 @@ In the integration with Mercado Livre, you can assemble the description of your
 
 ## Template settings
 
-<div class="alert alert-danger">
-For stores in Brazil and Argentina, <strong>Mercado Livre does not accept HTML or CSS template customizations</strong> (with the exception of the &lt;br&gt; tag for line breaks). For stores in other countries, Iframes, Scripts, Forms, Inputs, Meta, Object and Embed tags are not allowed.
-</div>
+>❗ For stores in Brazil and Argentina, **Mercado Livre does not accept HTML or CSS template customizations** (with the exception of the &lt;br&gt; tag for line breaks). For stores in other countries, Iframes, Scripts, Forms, Inputs, Meta, Object and Embed tags are not allowed.
 
 In order for your product to be offered in Mercado Livre, it is necessary to configure the ad template where the product will be displayed. To set up this template, follow the step-by-step instructions below:
 
@@ -43,8 +41,6 @@ If you want to include all attributes and attributes values in the template, you
 
 ``{{#each ATRIBUTOS}} {{NOME}} – {{VALOR}} <br> {{/each}}``
 
-<div class="alert alert-info">
-If you want to hide some attribute in the template, you can do this in the <strong>Integration's settings</strong> panel by filling in the <strong>Attributes hidden in the product template</strong> field as explained in the <strong>Set up the Mercado Livre panel at VTEX Bridge</strong> section from the previous step.
-</div>
+>ℹ️ If you want to hide some attribute in the template, you can do this in the **Integration's settings** panel by filling in the **Attributes hidden in the product template** field as explained in the **Set up the Mercado Livre panel at VTEX Bridge** section from the previous step.
 
 You have completed the *third stage* of the integration! Now, we will set up the logistics for the delivery of orders made in Mercado Livre.
diff --git a/docs/tracks/en/setting-up-the-app.md b/docs/tracks/en/setting-up-the-app.md
index d5267774a..6a719ffda 100644
--- a/docs/tracks/en/setting-up-the-app.md
+++ b/docs/tracks/en/setting-up-the-app.md
@@ -52,9 +52,7 @@ Activating this option allows a purchase to be completed even if its value excee
 
 For example, for an account created with a credit limit of $1,000.00 and a tolerance of 10%, the customer will be able to place an order with a maximum value of $1,100.00 using Customer Credit as a payment method. If the customer wishes to use the credit to pay for an order worth $1,250.00, the system will not allow the purchase to be completed.
 
-<div class="alert alert-warning">
-Tolerance values are configured in decimal numbers, with 0 representing 0% and 1 representing 100%. Example: to use a tolerance of 5%, the value to be configured is 0.05.
-</div>
+>⚠️ Tolerance values are configured in decimal numbers, with 0 representing 0% and 1 representing 100%. Example: to use a tolerance of 5%, the value to be configured is 0.05.
 
 ![CC_Configuration_2_EN](https://images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/42de816c9685f31074c0637dcbd6c5f1/CC_Configuration_2_EN.JPG)
 
@@ -76,9 +74,7 @@ The customer can access this page on your store's website at __My account > My C
 
 This configuration allows you to insert instructions related to payment in the invoices issued by Customer Credit. To edit the message to be displayed in the invoice, enter the information in the test box and click `Update`.
 
-<div class="alert alert-warning">
-The message registered in this configuration will be replicated on all invoices issued for all Customer Credit accounts. It is not possible to configure a unique message for each specific customer or invoice.
-</div>
+>⚠️ The message registered in this configuration will be replicated on all invoices issued for all Customer Credit accounts. It is not possible to configure a unique message for each specific customer or invoice.
 
 ![CC_Configuration_5_EN](https://images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/cdf9331ac0d8e46d6537c8f265bc621b/CC_Configuration_5_EN.JPG)
 
@@ -109,6 +105,4 @@ To create payment conditions for Customer Credit invoices, follow the steps belo
 
 <blockquote><ui>8. Click <b>Save</b>.</ui>
 
-<div class="alert alert-warning">
-It is not possible to set an interest rate for a payment condition created with just a single installment. 
-</div>
+>⚠️ It is not possible to set an interest rate for a payment condition created with just a single installment.
diff --git a/docs/tracks/en/setting-up-the-cappta-acquirer-for-instore.md b/docs/tracks/en/setting-up-the-cappta-acquirer-for-instore.md
index b65a2d901..b6ca41bfc 100644
--- a/docs/tracks/en/setting-up-the-cappta-acquirer-for-instore.md
+++ b/docs/tracks/en/setting-up-the-cappta-acquirer-for-instore.md
@@ -18,9 +18,7 @@ To allow transactions through card machines using inStore, you need an acquirer
 
 __Cappta__ is an inStore certified sub-acquirer in Brazil.
 
-<div class="alert alert-warning">
-If you want to use Cappta in a different country or if you want to use another acquirer that is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article <a href="https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrating inStore to a new payment acquirer</a>.
-</div>
+>⚠️ If you want to use Cappta in a different country or if you want to use another acquirer that is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article [Integrating inStore to a new payment acquirer](https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
 <div class=”alert alert-info”>
 Cappta is currently supported by the following platforms and devices:
diff --git a/docs/tracks/en/setting-up-the-cielo-lio-acquirer-for-instore.md b/docs/tracks/en/setting-up-the-cielo-lio-acquirer-for-instore.md
index 6fe3a9b0a..0b3141aff 100644
--- a/docs/tracks/en/setting-up-the-cielo-lio-acquirer-for-instore.md
+++ b/docs/tracks/en/setting-up-the-cielo-lio-acquirer-for-instore.md
@@ -18,13 +18,9 @@ To allow transactions through card machines using inStore, you need an acquirer
 
 __Cielo LIO__ is an inStore certified acquirer in Brazil.
 
-<div class="alert alert-warning">
-If you want to use Cielo LIO in a different country or if you want to use another acquirer which is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article <a href="https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrating inStore to a new payment acquirer</a>.
-</div>
+>⚠️ If you want to use Cielo LIO in a different country or if you want to use another acquirer which is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article [Integrating inStore to a new payment acquirer](https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Cielo LIO is currently supported only by Android systems. You may use CieloLio V2 or CieloLio+.
-</div>
+>ℹ️ Cielo LIO is currently supported only by Android systems. You may use CieloLio V2 or CieloLio+.
 
 Before installing Cielo LIO’s application, make sure you have completed the previous step of setting up the Payments module.
 
diff --git a/docs/tracks/en/setting-up-the-order-summary-printing.md b/docs/tracks/en/setting-up-the-order-summary-printing.md
index 19acc5790..65c5b3914 100644
--- a/docs/tracks/en/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/en/setting-up-the-order-summary-printing.md
@@ -25,9 +25,7 @@ Two steps are required:
 
 ## Enable the device configuration option
 
-<div class="alert alert-danger">
-Enabling the device configuration option is done through a change to the JavaScript file <code>checkout-instore-custom.js</code>. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
-</div>
+>❗ Enabling the device configuration option is done through a change to the JavaScript file `checkout-instore-custom.js`. This operation should only be performed by people with programming experience. Incorrect changes to this file can cause critical errors.
 
 First, open the file `checkout-instore-custom.js`, available in the Admin of your VTEX account (if you do not know how to access this file, check out the tutorial [How to customize inStore](https://help.vtex.com/en/tracks/instore-customizacoes--1z9kBm12oBPyVNDo1ivVc2)).
 
@@ -44,17 +42,13 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionality.
-</div>
+>❗ Do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionality.
 
 This change will make the __Configure device__ option appear in the inStore main menu, as shown in the image below. It is through this option that you will configure the printer.
 
 ![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
-<div class="alert alert-info">
-<strong>Note:</strong> There is an option to automatically print the order summary as soon as the order is completed. To enable it, add the <code>printPageAutomatically</code> property with the value <code>true</code> inside the <code>printingConfig</code> object. See below how the code would look like in this case.
-</div>
+>ℹ️ **Note:** There is an option to automatically print the order summary as soon as the order is completed. To enable it, add the `printPageAutomatically` property with the value `true` inside the `printingConfig` object. See below how the code would look like in this case.
 
 ```json
 window.INSTORE_CONFIG = { 
@@ -66,17 +60,13 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Again, do not remove any of the other properties present in the <code>window.INSTORE_CONFIG</code> object, to avoid breaking other functionality.
-</div>
+>❗ Again, do not remove any of the other properties present in the `window.INSTORE_CONFIG` object, to avoid breaking other functionality.
 
 ## Configure the printer device in inStore
 
 Now let's see how to set up a printer connected to the inStore to print order summaries.
 
-<div class="alert alert-warning">
-First of all, to connect a printer to the inStore system, it is necessary to have a pair of VTEX credentials (AppKey and AppToken) with the appropriate access permissions. We recommend that the role linked to these credentials is <code>inStore Sales Person</code>. However, a profile with more powers, such as Admin Super, can also be used.
-</div>
+>⚠️ First of all, to connect a printer to the inStore system, it is necessary to have a pair of VTEX credentials (AppKey and AppToken) with the appropriate access permissions. We recommend that the role linked to these credentials is `inStore Sales Person`. However, a profile with more powers, such as Admin Super, can also be used.
 
 With AppKey and AppToken in hand, follow the steps below:
 
diff --git a/docs/tracks/en/setting-up-the-pagar-me-acquirer-for-instore.md b/docs/tracks/en/setting-up-the-pagar-me-acquirer-for-instore.md
index 952e6236e..752a3691b 100644
--- a/docs/tracks/en/setting-up-the-pagar-me-acquirer-for-instore.md
+++ b/docs/tracks/en/setting-up-the-pagar-me-acquirer-for-instore.md
@@ -18,13 +18,9 @@ To allow transactions through card machines using inStore, you need an acquirer
 
 __Pagar.me__ is an inStore certified sub-acquirer in Brazil.
 
-<div class="alert alert-warning">
-If you want to use Pagar.me in a different country or if you want to use another acquirer that is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article <a href="https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrating inStore to a new payment acquirer</a>.
-</div>
+>⚠️ If you want to use Pagar.me in a different country or if you want to use another acquirer that is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article [Integrating inStore to a new payment acquirer](https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Pagar.me is currently supported only by <b>Android</b> systems, with <b>Gertec MOBIPIN</b> card machines.
-</div>
+>ℹ️ Pagar.me is currently supported only by **Android** systems, with **Gertec MOBIPIN** card machines.
 
 Before installing Pagar.me’s application, make sure you have completed the previous step of setting up the Payments module. If you have, follow the steps below to install and set up the Pagar.me acquirer for inStore.
 
diff --git a/docs/tracks/en/setting-up-the-sitef-acquirer-for-instore.md b/docs/tracks/en/setting-up-the-sitef-acquirer-for-instore.md
index ad696f591..03869db89 100644
--- a/docs/tracks/en/setting-up-the-sitef-acquirer-for-instore.md
+++ b/docs/tracks/en/setting-up-the-sitef-acquirer-for-instore.md
@@ -14,21 +14,15 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugEN: setting-up-the-sitef-acquirer-for-instore
 ---
 
-<div class="alert alert-warning">
-It is important to stress that the SiTef integration is a certified solution, but has not yet been tested on a large scale.
-</div>
+>⚠️ It is important to stress that the SiTef integration is a certified solution, but has not yet been tested on a large scale.
 
 To allow transactions through card machines using inStore, you need an acquirer or sub-acquirer that will process your payments.
 
 __SiTef__ is an inStore certified sub-acquirer in Brazil.
 
-<div class="alert alert-warning">
-If you want to use SiTef in a different country or if you want to use another acquirer that is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article <a href="https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrating inStore to a new payment acquirer</a>.
-</div>
+>⚠️ If you want to use SiTef in a different country or if you want to use another acquirer that is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article [Integrating inStore to a new payment acquirer](https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-SiTef is currently supported by <b>Android</b> and <b>iOS</b> systems, with Ingenico card machines or any other machine that is certified by SiTef.
-</div>
+>ℹ️ SiTef is currently supported by **Android** and **iOS** systems, with Ingenico card machines or any other machine that is certified by SiTef.
 
 Before installing SiTef’s application, make sure you have completed the previous step of setting up the Payments module.
 
diff --git a/docs/tracks/en/setting-up-the-stone-acquirer-for-instore.md b/docs/tracks/en/setting-up-the-stone-acquirer-for-instore.md
index 83f358ed9..437dfee3c 100644
--- a/docs/tracks/en/setting-up-the-stone-acquirer-for-instore.md
+++ b/docs/tracks/en/setting-up-the-stone-acquirer-for-instore.md
@@ -18,13 +18,9 @@ To allow transactions through card machines using inStore, you need an acquirer
 
 __Stone__ is an inStore certified sub-acquirer in Brazil.
 
-<div class="alert alert-warning">
-If you want to use Stone in a different country or if you want to use another acquirer which is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article <a href="https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrating inStore to a new payment acquirer</a>.
-</div>
+>⚠️ If you want to use Stone in a different country or if you want to use another acquirer which is not currently certified, you will need to build the integration with that acquirer’s application. To do so, refer to the article [Integrating inStore to a new payment acquirer](https://help.vtex.com/en/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Stone is currently supported only by <b>Android</b> systems, with <b>Gertec GPOS700</b> card machines. For other card machines, Stone recommends that you use <a href="https://help.vtex.com/en/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/1obqdkoH82yFWtaMbwcJKx">Pagar.me acquirer</a>.
-</div>
+>ℹ️ Stone is currently supported only by **Android** systems, with **Gertec GPOS700** card machines. For other card machines, Stone recommends that you use [Pagar.me acquirer](https://help.vtex.com/en/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/1obqdkoH82yFWtaMbwcJKx).
 
 Before installing Stone’s application, make sure you have completed the previous step of setting up the Payments module.
 
diff --git a/docs/tracks/en/settings.md b/docs/tracks/en/settings.md
index 95dae110f..ff5bf6d59 100644
--- a/docs/tracks/en/settings.md
+++ b/docs/tracks/en/settings.md
@@ -22,15 +22,11 @@ VTEX uses two CDN providers in the stores: **Cloudfront** and **Azion**. Your st
 
 So, if you have the store domain registered on the **Cloudfront** or **Azion** platform, delete it before pointing the DNS to VTEX.
 
-<div class="alert alert-warning">
-If you are unable to delete your store's domain registration on the <strong>Cloudfront</strong> or <strong>Azion</strong> platforms, please contact <a href="https://help.vtex.com/en/support">VTEX support</a> to explain the situation. VTEX will help you ensure your store is running smoothly at go-live.
-</div>
+>⚠️ If you are unable to delete your store's domain registration on the **Cloudfront** or **Azion** platforms, please contact [VTEX support](https://help.vtex.com/en/support) to explain the situation. VTEX will help you ensure your store is running smoothly at go-live.
 
 ## Configuring CAA records
 
-<div class="alert alert-warning">
-You will only need to configure CAA records, as described in this section if there is a CAA record in your DNS server. Otherwise, proceed to the next section of this guide.
-</div>
+>⚠️ You will only need to configure CAA records, as described in this section if there is a CAA record in your DNS server. Otherwise, proceed to the next section of this guide.
 
 CAA records indicate which certificate authorities (CAs) are entitled to generate and renew certificates to confirm your domain identity. Proper configuration of these records is necessary to generate [SSL certificates](https://help.vtex.com/en/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar--tutorials_1308) and use the VTEX CDN.
 
@@ -44,9 +40,7 @@ This means that the **Let's Encrypt** certificate authority can issue certificat
 
 Although not recommended, another alternative would be not including CAA records in your DNS server, indicating that all certificate authorities are authorized to issue and renew certificates for your domain.
 
-<div class="alert alert-info">
-These types of entries may not be available in the interface of your DNS manager, but you can usually manage them by calling the support of the specific tool.
-</div>
+>ℹ️ These types of entries may not be available in the interface of your DNS manager, but you can usually manage them by calling the support of the specific tool.
 
 To easily create/verify your CAA records, you can use [CAA Record Helper by SSLMate](https://sslmate.com/caa/). The [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) program can also help you verify your records with the `dig domain.com CAA` command – a `SERVFAIL` status can indicate non-compliance of your DNS server.
 
diff --git a/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
index d8ede6cc0..5e725815f 100644
--- a/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/en/sharing-shopping-cart-using-instore-social-selling.md
@@ -41,9 +41,7 @@ See the step-by-step instructions illustrated below.
 
 The same link is shareable with multiple customers as many times as they like. Each time a person accesses this link, a new shopping cart is generated, exactly like the one created in VTEX Sales App. Carts accessed are also associated with the sales associate account and their code, if they have one.
 
-<div class="alert alert-info">
-<p>If the sales associate code is enabled, you are required to fill it in before sharing your cart. For more information about the sales associate code, check the <a href="https://help.vtex.com/en/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/Rby973h1l9tEM4C1YrzwZ">Customize VTEX Sales App</a> guide and the <a href="https://developers.vtex.com/vtex-rest-api/docs/sales-associate-code">Enable the sales associate code</a> developer guide.</p>
-</div>
+>ℹ️ If the sales associate code is enabled, you are required to fill it in before sharing your cart. For more information about the sales associate code, check the [Customize VTEX Sales App](https://help.vtex.com/en/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/Rby973h1l9tEM4C1YrzwZ) guide and the [Enable the sales associate code](https://developers.vtex.com/vtex-rest-api/docs/sales-associate-code) developer guide.
 
 ## Payment link
 
diff --git a/docs/tracks/en/shipping-strategies.md b/docs/tracks/en/shipping-strategies.md
index 653c327d5..1991aa52a 100644
--- a/docs/tracks/en/shipping-strategies.md
+++ b/docs/tracks/en/shipping-strategies.md
@@ -78,9 +78,7 @@ When configuring [shipping strategies](https://help.vtex.com/en/tutorial/shippin
 6. [Geolocation](https://help.vtex.com/en/tutorial/registering-geolocation--tutorials_138);
 7. Configuration of the pickup points available at checkout.
 
-<div class="alert alert-warning">
-For more information, please refer to the article <a href="https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#setup">Configuring pickup points.</a> 
-</div>
+>⚠️ For more information, please refer to the article [Configuring pickup points.](https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#setup)
 
 ## Shipping time and holidays
 
@@ -97,9 +95,7 @@ For more details about the SLA calculation, read the article [How is the deliver
 
 Holidays are important in determining the shipping time, as they are directly related to the delivery time of your store's orders. VTEX considers holidays to be days when the store does not operate.
 
-<div class="alert alert-warning">
-We recommended that you register holidays after configuring the <a href="https://help.vtex.com/en/tutorial/shipping-strategy--58vLBDbjYVQzJ6rRc5QNz3">shipping strategies</a>.
-</div>
+>⚠️ We recommended that you register holidays after configuring the [shipping strategies](https://help.vtex.com/en/tutorial/shipping-strategy--58vLBDbjYVQzJ6rRc5QNz3).
 
 To register holidays on the platform, you can:
 
diff --git a/docs/tracks/en/specifications-concept-definition.md b/docs/tracks/en/specifications-concept-definition.md
index fcdbee0e8..80fd42a41 100644
--- a/docs/tracks/en/specifications-concept-definition.md
+++ b/docs/tracks/en/specifications-concept-definition.md
@@ -16,9 +16,7 @@ trackSlugEN: catalog-101
 
 Specifications are additional properties that can be added to your store's products or SKUs. At VTEX, these specifications are added in the **Categories** section and are called **Field**.
 
-<div class="alert alert-warning">
-<p>In VTEX, specifications follow a logic of "inheritance", that is, when creating a specification at a higher category level, the specification will be presented at all category levels below it. Therefore, if you need to create a product or SKU specification that applies to only one category, it should be created at that category's level.</p>
-</div>
+>⚠️ In VTEX, specifications follow a logic of "inheritance", that is, when creating a specification at a higher category level, the specification will be presented at all category levels below it. Therefore, if you need to create a product or SKU specification that applies to only one category, it should be created at that category's level.
 
 ## Product Specification
 
@@ -42,6 +40,4 @@ Your SKU specifications would have values such as **XS, S, M, L and XL**. These
 
 To understand the complete step-by-step for creating SKU specifications, check out the article [Adding SKU specifications or fields](https://help.vtex.com/en/tutorial/adding-sku-specifications-or-fields--tutorials_119).
 
-<div class="alert alert-warning">
-At VTEX, SKU specifications are mandatory fields required to add SKUs, meaning that if a specification were to be created in a category, all SKUs within that category would need to carry this new specification. All these SKUs are therefore disabled until this new specification is added to the SKUs of the category in question.
-</div>
+>⚠️ At VTEX, SKU specifications are mandatory fields required to add SKUs, meaning that if a specification were to be created in a category, all SKUs within that category would need to carry this new specification. All these SKUs are therefore disabled until this new specification is added to the SKUs of the category in question.
diff --git a/docs/tracks/en/subscription-orders.md b/docs/tracks/en/subscription-orders.md
index d0615c39d..d7ad4ffce 100644
--- a/docs/tracks/en/subscription-orders.md
+++ b/docs/tracks/en/subscription-orders.md
@@ -20,8 +20,6 @@ The customer indicates how often they want to repeat the purchase of a particula
 
 In the VTEX Admin, in **Orders > Subscriptions**, there are two pages —  [Dashboards](https://help.vtex.com/en/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x), where you can track and supervise existing subscriptions, and [Settings](https://help.vtex.com/en/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x#settings), for configuring your subscriptions. A subscription will only appear in the list after the first payment has been approved.
 
-<div class="alert alert-warning">
-Currently, only purchases made with <strong>credit cards</strong> are eligible for subscriptions. Please enable all credit card conditions already set for <a href="https://help.vtex.com/pt/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW">recurring purchases</a> in your payment settings. In addition, it is required that your payment connector accepts recurring payments. Contact your store's acquirer and make sure they support tokenized credit card payments (without the CVV) for recurring purchases.
-</div>
+>⚠️ Currently, only purchases made with **credit cards** are eligible for subscriptions. Please enable all credit card conditions already set for [recurring purchases](https://help.vtex.com/pt/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW) in your payment settings. In addition, it is required that your payment connector accepts recurring payments. Contact your store's acquirer and make sure they support tokenized credit card payments (without the CVV) for recurring purchases.
 
 For more information, see [How to configure subscriptions in your store](https://help.vtex.com/en/tutorial/how-to-configure-subscriptions--1FA9dfE7vJqxBna9Nft5Sj).
diff --git a/docs/tracks/en/teste-1.md b/docs/tracks/en/teste-1.md
index ec9b7bde2..3c1ecc230 100644
--- a/docs/tracks/en/teste-1.md
+++ b/docs/tracks/en/teste-1.md
@@ -32,9 +32,7 @@ The **Onboarding guide** has three tracks:
 - [Next steps after the go-live](https://help.vtex.com/en/tracks/next-steps-after-the-go-live--3J7WFZyvTcoiwkcIVFVhIS)
 - [Support at VTEX](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-<div class="alert alert-info">
-The tracks include content that complement one another, but they are intended to be standalone. This means you can explore the content freely, without following any specific order.
-</div>
+>ℹ️ The tracks include content that complement one another, but they are intended to be standalone. This means you can explore the content freely, without following any specific order.
 
 Our aim is to allow clients, partners, and the VTEX ecosystem to take advantage of the **Onboarding guide**. We took into account a comprehensive journey to make sure the content stayed relevant for different businesses.
 
diff --git a/docs/tracks/en/the-reservation.md b/docs/tracks/en/the-reservation.md
index 86062a28d..6524f71db 100644
--- a/docs/tracks/en/the-reservation.md
+++ b/docs/tracks/en/the-reservation.md
@@ -22,9 +22,7 @@ The reservation connects the logistics module to the orders module. It prevents
 
 ## How the reservation works
 
-<div class="alert alert-warning">
-Products only inserted into the cart <strong>do not</strong> create reservation or priority. A reservation is made only if an order is <strong>completed</strong>.
-</div>  
+>⚠️ Products only inserted into the cart **do not** create reservation or priority. A reservation is made only if an order is **completed**.  
 
 This is the reservation flow at VTEX:
 
@@ -36,6 +34,4 @@ This is the reservation flow at VTEX:
 
 ![reservation en](https://images.ctfassets.net/alneenqid6w5/7mm0YP3bcfb5fqZf5XhmZX/8798695363d5f4008f0a9c7078ebc386/reservation_en.png)
 
-<div class="alert alert-warning">
-VTEX does not automatically remove items from the inventory, even after they have moved to <code>Reservation Recognized</code> status. Purchased items will remain in this status until the ERP or the store remove them from the inventory.
-</div>
+>⚠️ VTEX does not automatically remove items from the inventory, even after they have moved to `Reservation Recognized` status. Purchased items will remain in this status until the ERP or the store remove them from the inventory.
diff --git a/docs/tracks/en/tiktok-for-business.md b/docs/tracks/en/tiktok-for-business.md
index 289bacaa6..9f0c279c4 100644
--- a/docs/tracks/en/tiktok-for-business.md
+++ b/docs/tracks/en/tiktok-for-business.md
@@ -14,9 +14,7 @@ trackId: 1r0yJSO11nrer1YVu3WTFd
 trackSlugEN: tiktok-integration
 ---
 
-<div class="alert alert-danger">
-  <p>The integration with TikTok is available only for stores in <strong>Brazil</strong>.</p>
-</div>
+>❗ The integration with TikTok is available only for stores in **Brazil**.
 
 [TikTok](https://www.tiktok.com/) is an entertainment platform for creating and sharing short videos that offers marketing tools for businesses. One of the key tools available in this context is TikTok Ads Manager, which contains advanced features for launching campaigns and managing advertising on TikTok.
 
diff --git a/docs/tracks/en/unified-commerce.md b/docs/tracks/en/unified-commerce.md
index d08fdd362..d32fe8932 100644
--- a/docs/tracks/en/unified-commerce.md
+++ b/docs/tracks/en/unified-commerce.md
@@ -38,9 +38,7 @@ Other advantages of working with franchise accounts are listed below:
 
 - Increased operational performance by using multiple requests at the store checkout. In a standard account, where the [shipping strategy](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistics-required-settings) is added to the main account, requests are processed separately and queued, generating a potential backlog of requests and increased timeouts. Whenever a timeout occurs, an error message appears at checkout, and the customer has to click F5 or the refresh button to proceed with the purchase. This behavior has a negative impact on the customer experience and lowers the store's conversion rate.
 
-<div class="alert alert-warning">
-  <p><a href="https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">Franchise accounts</a> act as a <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a> for the main account. When a customer adds products to the shopping cart and simulates shipping on the main account's website, the <a href="https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">white label seller selection algorithm</a> automatically determines which franchise account will <a href="https://help.vtex.com/en/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP">fulfill</a> the order. If one or more products in the cart are unavailable in the selected franchise account, the system will select another available account to ship the unavailable products, allowing more than one shipment for the same order. This process occurs internally on the platform, and the customer doesn't know the sellers involved.</p>
-</div>
+>⚠️ [Franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) act as a [white label seller](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) for the main account. When a customer adds products to the shopping cart and simulates shipping on the main account's website, the [white label seller selection algorithm](https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) automatically determines which franchise account will [fulfill](https://help.vtex.com/en/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) the order. If one or more products in the cart are unavailable in the selected franchise account, the system will select another available account to ship the unavailable products, allowing more than one shipment for the same order. This process occurs internally on the platform, and the customer doesn't know the sellers involved.
 
 ## Ship from store
 
diff --git a/docs/tracks/en/vtex-modules-i.md b/docs/tracks/en/vtex-modules-i.md
index e21a770f2..c65389a7a 100644
--- a/docs/tracks/en/vtex-modules-i.md
+++ b/docs/tracks/en/vtex-modules-i.md
@@ -21,9 +21,7 @@ The VTEX platform is structured in modules for each part of the store's operatio
 - [Promotions](#promotions)
 - [Logistics](#logistics)
 
-<div class="alert alert-info">
-The <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ">VTEX modules II</a> article describes the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments">Payments</a>, <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#orders">Orders</a>, and <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout">Checkout</a> modules.
-</div>
+>ℹ️ The [VTEX modules II](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ) article describes the [Payments](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#payments), [Orders](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#orders), and [Checkout](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout) modules.
 
 ## Catalog
 
@@ -63,9 +61,7 @@ The following table shows the store's main Catalog settings based on their creat
 
 <br>
 
-<div class="alert alert-warning">
-To learn how to import products from an ERP (Enterprise Resource Planning) or PIM (Product Information Manager) system to the VTEX platform, read the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
-</div>
+>⚠️ To learn how to import products from an ERP (Enterprise Resource Planning) or PIM (Product Information Manager) system to the VTEX platform, read the [Backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) article.
 
 #### Category tree
 
@@ -79,9 +75,7 @@ Before importing the store catalog to VTEX, we recommend that you start working
 
 ![catalog_arquitecture_table_EN](https://images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/f539ab283449f2aa2163be8b8ddd957e/catalog_arquitecture_table_EN.png)
 
-<div class="alert alert-info">
-For more information on how to import back-office specifications, read the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
-</div>
+>ℹ️ For more information on how to import back-office specifications, read the [Backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) article.
 
 #### Brands
 
@@ -174,9 +168,7 @@ There is a difference between price tables created for [trade policies](https://
 
 Price tables not associated with trade policies can be used in contexts such as __promotions__ and __customer clusters__. Tables created for trade policies can only be associated with the trade policy itself. Thus, the price table associated with a trade policy shows the SKU price specific to that policy and cannot be associated with other contexts.
 
-<div class="alert alert-warning">
-The concepts of <b>price table</b> and <a href="LINK">trade policy</a> are different. Trade policy is the context with which a price list is associated.
-</div>
+>⚠️ The concepts of **price table** and [trade policy](LINK) are different. Trade policy is the context with which a price list is associated.
 
 When setting up a trade policy, you must [specify the currency that will be used in the store](https://help.vtex.com/en/tutorial/creating-a-trade-policy--563tbcL0TYKEKeOY4IAgAE). Creating different trade policies associated with a different currency allows the store to display prices in different currencies to customers. 
 
@@ -227,9 +219,7 @@ For more information on how promotions can be applied, read the [Promotion examp
 
 You can create discount coupons through the [VTEX Admin](https://help.vtex.com/en/tutorial/creating-a-coupon-beta--7lMk3MmhNp2IEccyGApxU) ou via [API](https://developers.vtex.com/docs/guides/creating-and-managing-coupons-with-promotions-api). A coupon must be linked to at least one promotion to be applicable. 
 
-<div class="alert alert-warning">
-There is a maximum number of active coupons. We strongly recommend reusing coupons, as a large number of coupons can compromise the performance of the Promotions module.
-</div>
+>⚠️ There is a maximum number of active coupons. We strongly recommend reusing coupons, as a large number of coupons can compromise the performance of the Promotions module.
 
 ### Criar promoções de campanha
 
@@ -317,9 +307,7 @@ The [carrier](https://help.vtex.com/en/tutorial/carries-on-vtex--7u9duMD5UQa2QQw
 
 Store [inventory](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) corresponds to the stored items available for sale. Warehouse is the identification of the physical location of storage location, while inventory is the set of SKUs in stock that are available for sale.
 
-<div class="alert alert-danger">
-On VTEX, the store must manage inventory updates after selling items. Thus, after a sale, the merchant ensures proper control of the remaining items and invoice operations with ERP. Information on inventory import via the back office can be found in the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Backend integrations</a> article.
-</div>
+>❗ On VTEX, the store must manage inventory updates after selling items. Thus, after a sale, the merchant ensures proper control of the remaining items and invoice operations with ERP. Information on inventory import via the back office can be found in the [Backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) article.
 
 ### Lead time
 
diff --git a/docs/tracks/en/vtex-modules-ii.md b/docs/tracks/en/vtex-modules-ii.md
index cd32e6336..d51734fea 100644
--- a/docs/tracks/en/vtex-modules-ii.md
+++ b/docs/tracks/en/vtex-modules-ii.md
@@ -28,9 +28,7 @@ The [Payments](https://help.vtex.com/en/tracks/payments--6GAS7ZzGAm7AGoEAwDbwJG/
 
 To process and receive payments for purchases in a VTEX store, you need to have a service agreement with one or more payment providers. These agreements are established directly between the merchant and the provider, without mediation or participation from VTEX. To view available providers on VTEX in each country, check the [List of Payment Providers by Country](https://help.vtex.com/en/tutorial/list-of-payment-providers-by-country--2im3BEGXxSAcRuxEaIHPvp).
 
-<div class="alert alert-warning">
-We recommend integrating multiple payment providers in your store to enhance customer experience by offering a variety of payment methods and conditions. This approach also allows operating with diverse rates and costs, thereby improving business performance.
-</div>
+>⚠️ We recommend integrating multiple payment providers in your store to enhance customer experience by offering a variety of payment methods and conditions. This approach also allows operating with diverse rates and costs, thereby improving business performance.
 
 The payment settings described in this track can be configured at any time during the onboarding process. However, for the store to be able to process any type of payment transaction, the [Catalog](https://help.vtex.com/en/tracks/track-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog), [Pricing](https://help.vtex.com/en/tracks/track-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#prices), and [Logistics](https://help.vtex.com/en/tracks/track-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistic) modules must have been configured beforehand.
 
@@ -189,9 +187,7 @@ To find a purchase record in the VTEX Admin, you can either [filter orders](http
 - Customer email
 - Customer ID
 
-<div class="alert alert-warning">
-You can only access details about orders created in the last two years. This same period applies to customers accessing their orders via the <a href="">My Account</a> page.
-</div>
+>⚠️ You can only access details about orders created in the last two years. This same period applies to customers accessing their orders via the [My Account]() page.
 
 To enable customers to track their orders, VTEX offers two important features: [transactional emails](#transactional-emails) and a dedicated customer area called [My Account](#my-account-feature).
 
@@ -270,9 +266,7 @@ Learn more in [Setting up Cart Abandonment](https://help.vtex.com/en/tutorial/co
 
 On the VTEX platform, stores can manually adjust the price of an item (SKU) in the cart at checkout. This feature can be used to apply special discounts, correct pricing errors, create custom offers, address price-related complaints, or adjust shipping costs.
 
-<div class="alert alert-warning">
-Only users with the necessary <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> and permissions within the VTEX Admin can make these changes.
-</div>
+>⚠️ Only users with the necessary [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) and permissions within the VTEX Admin can make these changes.
 
 Learn more in [Change the price of an item in the shopping cart](https://help.vtex.com/en/tutorial/modificar-o-preco-de-um-item-no-carrinho-de-compras--7Cd37aCAmtL1qmoZJJvjNf).
 
diff --git a/docs/tracks/en/vtex-platform-settings.md b/docs/tracks/en/vtex-platform-settings.md
index f2e266bc1..4c88d74b8 100644
--- a/docs/tracks/en/vtex-platform-settings.md
+++ b/docs/tracks/en/vtex-platform-settings.md
@@ -51,14 +51,10 @@ If you would like to use the same shipping strategy defined for your VTEX store
 
 If you want to make sure that the configuration was successful, you can use the [shipping simulator](https://help.vtex.com/en/tutorial/simulacao-de-frete--tutorials_144). This tool allows you to check the delivery terms of a product without having to actually place an order.
 
-<div class="alert alert-info">
-Amazon selects the type of shipping according to the <a href="https://help.vtex.com/en/tutorial/como-montar-a-planilha-de-frete--tutorials_127">template</a> <a href="https://help.vtex.com/en/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034">exported</a> by the seller. Therefore, the template exported by the retailer must be aligned with the template registered on the VTEX platform, thus reducing the chance of divergences.
-</div>
+>ℹ️ Amazon selects the type of shipping according to the [template](https://help.vtex.com/en/tutorial/como-montar-a-planilha-de-frete--tutorials_127) [exported](https://help.vtex.com/en/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034) by the seller. Therefore, the template exported by the retailer must be aligned with the template registered on the VTEX platform, thus reducing the chance of divergences.
 
 ### Processing time
 
 Amazon has a field called *"fulfillment latency"*, which is used to configure the time to prepare the delivery of a certain product. To use it when integrating your store with Amazon, you must fill in the **Processing time** field when [registering the loading dock](https://help.vtex.com/en/tutorial/como-cadastrar-doca) associated with the [trade policy](#defining-the-trade-policy-in-amazon) used for Amazon. If this field is not filled in, Amazon will use its default value (2 days). 
 
-<div class="alert alert-warning">
-Filling in this field is essential, because if your store delays the delivery of an order, your account may be blocked. 
-</div>
+>⚠️ Filling in this field is essential, because if your store delays the delivery of an order, your account may be blocked.
diff --git a/docs/tracks/en/what-are-clustered-payment-conditions.md b/docs/tracks/en/what-are-clustered-payment-conditions.md
index 3c6995824..0c869c5d3 100644
--- a/docs/tracks/en/what-are-clustered-payment-conditions.md
+++ b/docs/tracks/en/what-are-clustered-payment-conditions.md
@@ -16,8 +16,6 @@ trackSlugEN: clustered-payment-conditions
 
 Clustered Payments Conditions are a new [Customer Credit](https://help.vtex.com/en/announcements/de-credito-aos-seus-melhores-clientes-com-o-customer-credit--6M2V1Oc1UIaGSM6QayWkmq?&utm_source=autocomplete "Customer Credit") feature that allows stores to set a given deadline and enact an installment rule that will be valid for one or more customers of their trust. This filter is made using clusters - a segmentation method.
 
-<div class="alert alert-info">
-This functionality is currently in Closed Beta (testing stage) and is not available for installation in new stores.
-</div>  
+>ℹ️ This functionality is currently in Closed Beta (testing stage) and is not available for installation in new stores.  
 
 This customization is done using our [Master Data](https://help.vtex.com/en/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw "Master Data") database. 
diff --git a/docs/tracks/en/what-are-permissions-and-access-profiles.md b/docs/tracks/en/what-are-permissions-and-access-profiles.md
index 5e3f08bd3..76ce5d300 100644
--- a/docs/tracks/en/what-are-permissions-and-access-profiles.md
+++ b/docs/tracks/en/what-are-permissions-and-access-profiles.md
@@ -20,6 +20,4 @@ Roles define which resources the user can view and/or change within each module
 
 You can create new profiles and set permissions for them. Or you can use the [predefined profiles](https://help.vtex.com/en/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc#description-of-predefined-profiles), which are configured on the platform by default. Predefined profiles usually meet the vast majority of needs across all stores.
 
-<div class="alert alert-danger">
-Poor management of your store's roles can have serious consequences for your business. See best practices in the article: <a href="https://help.vtex.com/faq/security-measures-for-creating-a-store-user-profiles--15YDwC9jGgqWi3rvcDaiGM">Security measures for creating a store's user profiles</a>.
-</div>
+>❗ Poor management of your store's roles can have serious consequences for your business. See best practices in the article: [Security measures for creating a store's user profiles](https://help.vtex.com/faq/security-measures-for-creating-a-store-user-profiles--15YDwC9jGgqWi3rvcDaiGM).
diff --git a/docs/tracks/en/what-is-conversational-commerce-vtex.md b/docs/tracks/en/what-is-conversational-commerce-vtex.md
index 05bb725e5..5a9369bf0 100644
--- a/docs/tracks/en/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/en/what-is-conversational-commerce-vtex.md
@@ -18,9 +18,7 @@ Message-to-Order is a Conversational Commerce solution by VTEX that allows custo
 
 To leverage human support, Message-to-Order is already pre-integrated with Zenvia (Zenvia Chat product) and Zendesk marketplace platforms. Customers without these platforms or those who won't offer human support can be redirected to the brand's standard support channels via customized messages.
 
-<div class="alert alert-info">
-Message-to-Order is still in its early stages of operation (alpha phase), and therefore, its scope is limited.  Currently, its customer base and markets are limited to Brazil and Latin America, and only a limited set of features are available.
-</div>
+>ℹ️ Message-to-Order is still in its early stages of operation (alpha phase), and therefore, its scope is limited.  Currently, its customer base and markets are limited to Brazil and Latin America, and only a limited set of features are available.
 
 To add VTEX Conversational Commerce to your store, you must configure it in two steps:
 
diff --git a/docs/tracks/en/what-is-lengow.md b/docs/tracks/en/what-is-lengow.md
index e81b90f99..cbfb208fd 100644
--- a/docs/tracks/en/what-is-lengow.md
+++ b/docs/tracks/en/what-is-lengow.md
@@ -22,8 +22,6 @@ The [Lengow connector](https://apps.vtex.com/vtex-lengow/p) for VTEX allows your
 
 Once the connector app is set up, your catalog feed will become available in Lengow and your products will be ready to be published on the channels of your choice. As you sell across different channels, orders and product stock levels will be automatically kept in sync between VTEX and Lengow.
 
-<div class="alert alert-warning">
-Importing orders from Lengow is currently only supported for Amazon and Ebay. This is because each marketplace has a different structure and order flow, so it is not possible to do a standard integration for all marketplaces. If you need to integrate orders from marketplaces other than Amazon and eBay, please reach out to the VTEX support team.
-</div>
+>⚠️ Importing orders from Lengow is currently only supported for Amazon and Ebay. This is because each marketplace has a different structure and order flow, so it is not possible to do a standard integration for all marketplaces. If you need to integrate orders from marketplaces other than Amazon and eBay, please reach out to the VTEX support team.
 
 Before you start, you should already have signed up for a Lengow account. If you don't have one yet, you can [sign up for a free trial](https://my.lengow.io/registration) or [request a demo](https://www.lengow.com/ask-for-a-demo/) on their website to test their platform.
diff --git a/docs/tracks/en/what-is-suiteshare.md b/docs/tracks/en/what-is-suiteshare.md
index d256597d5..6ae1cf86c 100644
--- a/docs/tracks/en/what-is-suiteshare.md
+++ b/docs/tracks/en/what-is-suiteshare.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugEN: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tracks/en/what-is-the-payment-split.md b/docs/tracks/en/what-is-the-payment-split.md
index 0ef360da8..5a3552c9e 100644
--- a/docs/tracks/en/what-is-the-payment-split.md
+++ b/docs/tracks/en/what-is-the-payment-split.md
@@ -24,9 +24,7 @@ However, this amount may or may not be equally divided among recipients. The dis
 
 This track will explain how this solution works, including some essential concepts for this dynamic and how to configure it.   
 
-<div class="alert alert-info">
-If you are already familiar with the solution, go to “Configure payment split.”  
-</div>
+>ℹ️ If you are already familiar with the solution, go to “Configure payment split.”
 
 ## Receivable 
 Before we proceed, it is essential to understand what a receivable is - a concept that is not only addressed by VTEX but also used in numerous market scenarios.
@@ -40,16 +38,12 @@ Currently, Split supports the following payment methods:
 - Credit card
 - Debit card
 
-<div class="alert alert-info">
-For credit cards, the payment split supports payments made using two different cards.
-</div>  
+>ℹ️ For credit cards, the payment split supports payments made using two different cards.  
 
 ## Transaction
 When a customer finishes a purchase and pays for it, this amount will not necessarily be captured and sent to the seller in real-time. 
 
-<div class="alert alert-info">
-There are exceptions to this rule, such as the FedNow instant payment service or Clearing House’s RTP Network - a real-time payments platform that all federally insured U.S. depository institutions are eligible to use for payments innovation.
-</div>  
+>ℹ️ There are exceptions to this rule, such as the FedNow instant payment service or Clearing House’s RTP Network - a real-time payments platform that all federally insured U.S. depository institutions are eligible to use for payments innovation.  
 
 On VTEX, the default behavior is for purchase data to be gathered in a transaction, which then goes through several validation steps meant to ensure that all data is valid. This verification process is what we call the [transaction flow](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/1xjzgJZvqwaI1rfxLMCC3Y "transaction flow"). 
 
diff --git a/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md b/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md
index d797ddc3a..39a03c86c 100644
--- a/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md
+++ b/docs/tracks/en/what-to-configure-in-wish-prior-to-the-integration.md
@@ -14,7 +14,7 @@ trackId: 50hbG4bzhSIhjz1lzqI1g4
 trackSlugEN: wish-integration
 ---
 
-<div class="alert alert-warning">Presently, the Wish app is only available to Brazilian stores.</div>
+>⚠️ Presently, the Wish app is only available to Brazilian stores.
 
 You'll need to prepare your Wish environment before starting the integration with VTEX. The main steps are as follows:
 
diff --git a/docs/tracks/en/what-to-configure-with-vtex-before-starting-the-integration.md b/docs/tracks/en/what-to-configure-with-vtex-before-starting-the-integration.md
index 42b6385c8..75d49ae50 100644
--- a/docs/tracks/en/what-to-configure-with-vtex-before-starting-the-integration.md
+++ b/docs/tracks/en/what-to-configure-with-vtex-before-starting-the-integration.md
@@ -21,13 +21,11 @@ To ensure that the integration functions properly, some initial VTEX platform co
 
 You'll need to define which trade policy will be used to integrate your products with Wish. This will be applied to main aspects: product assortment, inventory, price and currency. This implies that product price and availability on specific sales channel is wholly based on the trade policy you choose. [Click here for more info on how the trade policy works](https://help.vtex.com/en/tutorial/configuring-a-marketplace-trade-policy).
 
-<div class="alert alert-info">
- NOTE: Wish demands that product prices and shipping be sent in USD. However, it does convert order values into BRL directly, making issuing invoices much easier.
-
-This means that the integration should send prices in USD and accept orders in BRL. Thus, the architecture uses only BRL and converts within the integration.
-
-However, <strong>the Wish trade policy must be in BRL</strong>, while the entire conversion flow will be more detailed in [step 5](https://help.vtex.com/en/tracks/wish-integration--50hbG4bzhSIhjz1lzqI1g4/6EYEy1jRiAj465WOnhiczD).
- </div>
+>ℹ️ NOTE: Wish demands that product prices and shipping be sent in USD. However, it does convert order values into BRL directly, making issuing invoices much easier.
+>
+> This means that the integration should send prices in USD and accept orders in BRL. Thus, the architecture uses only BRL and converts within the integration.
+>
+> However, **the Wish trade policy must be in BRL**, while the entire conversion flow will be more detailed in [step 5](https://help.vtex.com/en/tracks/wish-integration--50hbG4bzhSIhjz1lzqI1g4/6EYEy1jRiAj465WOnhiczD).
 
 [Click here](https://help.vtex.com/en/faq/adding-new-trade-policies--frequentlyAskedQuestions_700) to find out how to add a new trade policy when needed.
 
@@ -48,10 +46,8 @@ To ensure that order integrate successfully, you'll need to link, on the VTEX pl
   3. Set the [carriers](https://help.vtex.com/en/tracks/logistics-101--13TFDwDttPl9ki9OXQhyjx/3fLedVI57srjBDDxxGgOWe) that will ship from Wish;
   4. Link carriers to warehouses.
  
-<div class="alert alert-info">
-NOTE: Wish transfers the commission by confirming order delivery, obtaining this information by directly consulting its partner carriers. <strong><i>However, in order to sell on Wish, you need to use partner carriers for order delivery.</i></strong>
-<a href="https://merchant.wish.com/documentation/shippingproviders"> Check out the Wish accepted carriers here.</a>
-  </div>
+>ℹ️ NOTE: Wish transfers the commission by confirming order delivery, obtaining this information by directly consulting its partner carriers. **<i>However, in order to sell on Wish, you need to use partner carriers for order delivery.</i>**
+> [ Check out the Wish accepted carriers here.](https://merchant.wish.com/documentation/shippingproviders)
 
 ## Defining prices
 
diff --git a/docs/tracks/es/accounts-and-architecture.md b/docs/tracks/es/accounts-and-architecture.md
index 531cc4736..5bb0c8907 100644
--- a/docs/tracks/es/accounts-and-architecture.md
+++ b/docs/tracks/es/accounts-and-architecture.md
@@ -40,12 +40,17 @@ Hay varios factores que se deben considerar al [elegir entre la cuenta estándar
 | Cuenta franquicia | <ul><li>No tiene frontend ni sito web propio.</li><li>Tiene un entorno propio en el Admin VTEX para gestionar la operación.</li><li>No tiene catálogo propio y refleja la estructura de catálogo exacta de la cuenta principal.</li><li>Puede configurar precios y promociones.</li><li>Tiene almacén y stock propios.</li><li>El stock de la cuenta franquicia puede ser vendido en otros marketplaces VTEX que estén conectados con la cuenta principal a través de <a href="https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a>.</li></ul> |
 | Cuenta Seller Portal | <ul><li>No tiene frontend ni sito web propio.</li><li>La cuenta principal tiene una página de <a href="https://help.vtex.com/es/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv">Gestión de sellers</a>. A su vez, cada seller cuenta un entorno independiente en el Admin del Seller Portal.</li><li>El seller puede configurar stock y precio, gestionar productos compartidos con el marketplace, facturar pedidos, activar promociones, procesar pagos y contar con logística propia.</li></ul> |  
 
-<div class="alert alert-info">
-<p><b>Marketplaces en VTEX</b></p><p>Además de proporcionar gran versatilidad en la arquitectura de la tienda, nuestro ecosistema permite que cada tienda cuente con una serie de <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">estrategias de marketplace</a> tales como:</p><ul><li>Convertirse en seller o marketplace para otras tiendas VTEX.</li><li>Integrarse con importantes actores del mercado como <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> y <a href="https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP">Amazon</a>.</li><li>Integrarse con los <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros">marketplaces partner</a> certificados por VTEX.</li>
-<li> Ser un marketplace para sellers que tengan una cuenta <a href="https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK">Seller Portal</a>.</li>
-<li> Ser un <a href="https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>.</li>
-<li> Crear integraciones propias con <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">marketplaces y sellers externos</a>.</li></ul>
-</div>
+>ℹ️ **Marketplaces en VTEX**
+> Además de proporcionar gran versatilidad en la arquitectura de la tienda, nuestro ecosistema permite que cada tienda cuente con una serie de [estrategias de marketplace](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) tales como:
+> *Convertirse en seller o marketplace para otras tiendas VTEX.
+> * Integrarse con importantes actores del mercado como [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) y [Amazon](https://help.vtex.com/es/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP).
+> * Integrarse con los [marketplaces partner](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros) certificados por VTEX.
+>
+> *Ser un marketplace para sellers que tengan una cuenta [Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK).
+>
+> *Ser un [seller white label](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
+>
+> *Crear integraciones propias con [marketplaces y sellers externos](https://developers.vtex.com/docs/guides/external-seller-integration-guide).
 
 ## Arquitectura de la tienda
 
diff --git a/docs/tracks/es/add-an-image-to-the-sku.md b/docs/tracks/es/add-an-image-to-the-sku.md
index 4b6e2c360..06d047172 100644
--- a/docs/tracks/es/add-an-image-to-the-sku.md
+++ b/docs/tracks/es/add-an-image-to-the-sku.md
@@ -16,9 +16,7 @@ trackSlugES: vtex-getting-started
 
 Todo SKU necesita al menos una imagen para que aparezca en la tienda.
 
-<div class="alert alert-warning">
-Si ninguna imagen está asociada a un SKU, no se activará.
-</div>
+>⚠️ Si ninguna imagen está asociada a un SKU, no se activará.
 
 Por lo tanto, después de terminar de llenar la configuración de su nuevo SKU y hacer clic en __Guardar__, usted será llevado a la pantalla de registro de imagen, donde se muestra el mensaje siguiente.
 
diff --git a/docs/tracks/es/add-on-products.md b/docs/tracks/es/add-on-products.md
index 17519ebd9..4854364af 100644
--- a/docs/tracks/es/add-on-products.md
+++ b/docs/tracks/es/add-on-products.md
@@ -16,9 +16,7 @@ trackSlugES: proximos-pasos-tras-el-go-live
 
 Los productos add-on son soluciones que VTEX ofrece para satisfacer demandas específicas de los negocios y que pueden adquirirse por separado mediante un contrato de suscripción.
 
-<div class="alert alert-warning">
-  <p>Para implementar las soluciones a continuación, debes ponerte en contacto con el equipo de<a href="https://help.vtex.com/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ"> soporte comercial de VTEX</a>.</p>
-</div>
+>⚠️ Para implementar las soluciones a continuación, debes ponerte en contacto con el equipo de[ soporte comercial de VTEX](https://help.vtex.com/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
 ## VTEX Ad Network
 
@@ -88,9 +86,7 @@ Explora las opciones de envío de productos a todas las regiones de Brasil con [
 
 Para más información, debes acceder a la página de VTEX Shipping Network.
 
-<div class="alert alert-warning">
-  <p>Las soluciones <strong>VTEX Shipping Network</strong> y <strong>VTEX Shipping Network Correios</strong> son exclusivas para las operaciones en Brasil.</p>
-</div>
+>⚠️ Las soluciones **VTEX Shipping Network** y **VTEX Shipping Network Correios** son exclusivas para las operaciones en Brasil.
 
 ## VTEX Shipping Network Correios (solo Brasil)
 
diff --git a/docs/tracks/es/add-pickup-points.md b/docs/tracks/es/add-pickup-points.md
index b929226e5..0049b1708 100644
--- a/docs/tracks/es/add-pickup-points.md
+++ b/docs/tracks/es/add-pickup-points.md
@@ -79,9 +79,7 @@ Para subir una plantilla con los puntos de recogida, siga los pasos a continuaci
 ## API REST
 
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Logística se deben realizar vía  AppKey y AppToken. Para entender más, acceda a nuestro artículo sobre  <a href="https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2">cómo generar un Appkey y un AppToken para autenticar sus integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Logística se deben realizar vía  AppKey y AppToken. Para entender más, acceda a nuestro artículo sobre  [cómo generar un Appkey y un AppToken para autenticar sus integraciones](https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2)
 
 Para registrar un **Punto de Recogida** por API, debe  enviar un __POST__ para el siguiente  endpoint:
 
diff --git a/docs/tracks/es/add-sku-specifications.md b/docs/tracks/es/add-sku-specifications.md
index ad9d4547d..a6dda77b4 100644
--- a/docs/tracks/es/add-sku-specifications.md
+++ b/docs/tracks/es/add-sku-specifications.md
@@ -16,9 +16,7 @@ trackSlugES: catalogo-101
 
 Hay tres maneras de registrar sus especificaciones de SKU: a través del admin, por plantilla o por ERP.
 
-<div class="alert alert-warning">
-<p>En VTEX, las especificaciones siguen una lógica de "herencia", es decir, cuando se crea una especificación en un nivel de categoría superior, la especificación se presentará en todos los niveles de categoría inferiores. Por lo tanto, si es necesario crear una especificación de producto o SKU que se aplique a una sola categoría, debe crearse en ese nivel de categoría.</p>
-</div>
+>⚠️ En VTEX, las especificaciones siguen una lógica de "herencia", es decir, cuando se crea una especificación en un nivel de categoría superior, la especificación se presentará en todos los niveles de categoría inferiores. Por lo tanto, si es necesario crear una especificación de producto o SKU que se aplique a una sola categoría, debe crearse en ese nivel de categoría.
 
 Siga el siguiente procedimiento para registrar las especificaciones:
 
diff --git a/docs/tracks/es/adding-a-loading-dock.md b/docs/tracks/es/adding-a-loading-dock.md
index bdc71b79b..0102739cf 100644
--- a/docs/tracks/es/adding-a-loading-dock.md
+++ b/docs/tracks/es/adding-a-loading-dock.md
@@ -38,11 +38,7 @@ Siga el procedimiento a continuación para registrar un muelle en su tienda:
 - _Transportadoras asociadas_: transportadoras que este muelle atenderá.
 - _Tiempo de Costo_: tiempo que se agregará al cálculo de la entrega debido a la etapa de este muelle. > _Ej.: _ Tiempo de costo del inventario (2 días) + Tiempo de costo del muelle (3 días) + Tiempo de costo de la transportadora (1 día) = La entrega se realizará en 6 días.
 
-<div class="alert alert-info">
-
-<strong>Atención</strong>: el plazo de un muelle es independiente de si una transportadora opera o no los fines de semana y feriados. El tiempo de entrega será siempre la suma del tiempo del stock, de la transportadora y del muelle.
-
-</div>
+>ℹ️ **Atención**: el plazo de un muelle es independiente de si una transportadora opera o no los fines de semana y feriados. El tiempo de entrega será siempre la suma del tiempo del stock, de la transportadora y del muelle.
 
 - _Overhead de tiempo de costo_: valor que se utilizará para elegir el muelle más ventajoso en una entrega determinada. Este valor no se agrega al cálculo del tiempo de entrega.
 > _Ej.: _ Los muelles A y B tienen tiempo de costo de 3 días, pero el muelle A tiene overhead de 1 día, mientras que el muelle B tiene overhead de 2 días. En este caso, se elegirá el muelle A.
@@ -53,9 +49,7 @@ Siga el procedimiento a continuación para registrar un muelle en su tienda:
 
 ## API REST
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Inventario y Envío deben realizarse a través de AppKey y AppToken. Para entender más, acceda a nuestro artículo sobre <a href="https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2"> cómo generar un Appkey y un AppToken para autenticar sus integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Inventario y Envío deben realizarse a través de AppKey y AppToken. Para entender más, acceda a nuestro artículo sobre [ cómo generar un Appkey y un AppToken para autenticar sus integraciones](https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2)
 
 Para registrar un **Muelle** por API, debe enviar un __POST__ para el siguiente  endpoint:
 
diff --git a/docs/tracks/es/adding-a-price-rule.md b/docs/tracks/es/adding-a-price-rule.md
index f0c045198..939bfc05c 100644
--- a/docs/tracks/es/adding-a-price-rule.md
+++ b/docs/tracks/es/adding-a-price-rule.md
@@ -35,9 +35,7 @@ Siga el procedimiento a continuación para registrar la regla de precio de su ti
 
 ## API REST
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para entender más, acceda a nuestro artículo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">cómo generar un Appkey y un AppToken para autenticar sus integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para entender más, acceda a nuestro artículo sobre [cómo generar un Appkey y un AppToken para autenticar sus integraciones](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para registrar una **regla de precio**, debe enviar un __POST__ para el siguiente endpoint:
 
diff --git a/docs/tracks/es/adding-a-sender.md b/docs/tracks/es/adding-a-sender.md
index 682359fe6..017d6e2fc 100644
--- a/docs/tracks/es/adding-a-sender.md
+++ b/docs/tracks/es/adding-a-sender.md
@@ -42,8 +42,6 @@ Una vez hecho esto,  vuelva a la página de configuraciones en el Admin y selecc
 
 Siempre que lo considere necesario, puede probar si el envío de correos electrónicos funciona. Para hacerlo, vaya a la sección Remitentes y haga clic en el botón __Prueba__ del card con el remitente deseado.
 
-<div class="alert alert-warning">
-Atención: cada vez que realice un cambio en el remitente y lo guarde, se enviará un correo electrónico de confirmación de SMTP registrado con éxito a la dirección que ingresó. En todos los casos, es imprescindible hacer clic en el enlace enviado en el correo electrónico para completar la confirmación.
-</div>
+>⚠️ Atención: cada vez que realice un cambio en el remitente y lo guarde, se enviará un correo electrónico de confirmación de SMTP registrado con éxito a la dirección que ingresó. En todos los casos, es imprescindible hacer clic en el enlace enviado en el correo electrónico para completar la confirmación.
   
 
diff --git a/docs/tracks/es/adding-extra-text-to-the-order-print.md b/docs/tracks/es/adding-extra-text-to-the-order-print.md
index ffcc7fdaf..7cf619df3 100644
--- a/docs/tracks/es/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/es/adding-extra-text-to-the-order-print.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: agregar-texto-adicional-a-la-impresion-del-pedido
 ---
 
-<div class="alert alert-danger">
-Para agregar texto adicional a la impresión del pedido, como explicado en este artículo, es necesario cambiar el archivo JavaScript <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ Para agregar texto adicional a la impresión del pedido, como explicado en este artículo, es necesario cambiar el archivo JavaScript `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 Por defecto, la impresión del resumen del pedido no contiene ningún texto personalizado. Si desea agregar texto adicional a la impresión del pedido, es necesario editar el archivo `checkout-instore-custom.js`.
 
@@ -28,9 +26,7 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-No elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ No elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
 
 Después de volver a cargar inStore, cada vez que un vendedor imprima un pedido, ese texto aparecerá en la impresión.
 
diff --git a/docs/tracks/es/adding-holidays.md b/docs/tracks/es/adding-holidays.md
index 4cef57580..6a82dc465 100644
--- a/docs/tracks/es/adding-holidays.md
+++ b/docs/tracks/es/adding-holidays.md
@@ -28,9 +28,7 @@ Para configurar los feriados, siga los pasos a continuación:
 4. En __Fecha__, escriba la fecha de inicio del feriado. En __Fecha Final__, escriba la fecha de fin del feriado.
 5. Haga clic en __Guardar__.
 
-<div class="alert alert-warning">
-Los feriados se considerarán apenas para las transportadoras que estén configuradas como "Transportadora	<strong>no entrega</strong> los fines de semana".
-</div>
+>⚠️ Los feriados se considerarán apenas para las transportadoras que estén configuradas como "Transportadora	**no entrega** los fines de semana".
 
 Para que la transportadora sea elegible para la funcionalidad de feriado, siga los pasos que se indican a continuación:
 
@@ -41,9 +39,7 @@ Para que la transportadora sea elegible para la funcionalidad de feriado, siga l
 5. Seleccione la opción __Transportadora no entrega los fines de semana__.
 6. Haga clic en __Guardar__.
 
-<div class="alert alert-info">
-Usted puede establecer con antecedencia los feriados para los próximos años. Por ejemplo, puede crear la Navidad 2019, la Navidad 2020, etc.
-</div>
+>ℹ️ Usted puede establecer con antecedencia los feriados para los próximos años. Por ejemplo, puede crear la Navidad 2019, la Navidad 2020, etc.
 
 ## ¿Cómo se hace el cálculo?
 
diff --git a/docs/tracks/es/adding-product-specifications.md b/docs/tracks/es/adding-product-specifications.md
index ab207bb0d..0d1382510 100644
--- a/docs/tracks/es/adding-product-specifications.md
+++ b/docs/tracks/es/adding-product-specifications.md
@@ -16,9 +16,7 @@ trackSlugES: catalogo-101
 
 Hay tres maneras de registrar sus especificaciones: a través del admin, por plantilla o por API.
 
-<div class="alert alert-warning">
-<p>En VTEX, las especificaciones siguen una lógica de "herencia", es decir, cuando se crea una especificación en un nivel de categoría superior, la especificación se presentará en todos los niveles de categoría inferiores. Por lo tanto, si es necesario crear una especificación de producto o SKU que se aplique a una sola categoría, debe crearse en ese nivel de categoría.</p>
-</div>
+>⚠️ En VTEX, las especificaciones siguen una lógica de "herencia", es decir, cuando se crea una especificación en un nivel de categoría superior, la especificación se presentará en todos los niveles de categoría inferiores. Por lo tanto, si es necesario crear una especificación de producto o SKU que se aplique a una sola categoría, debe crearse en ese nivel de categoría.
 
 Siga este procedimiento para registrar las especificaciones:
 
diff --git a/docs/tracks/es/adding-products.md b/docs/tracks/es/adding-products.md
index 6f3399871..6649c61a7 100644
--- a/docs/tracks/es/adding-products.md
+++ b/docs/tracks/es/adding-products.md
@@ -39,7 +39,5 @@ Para registrar sus productos por plantilla, recomendamos que los registre junto
 ## API
 Utilice la llamada [Create Product](https://developers.vtex.com/vtex-rest-api/reference/post-product) para crear un nuevo producto por medio de la API del Catálogo.
 
-<div class="alert alert-info">
-Si su producto no aparece en el sitio web de su tienda después del registro, consulte el artículo <a href="https://help.vtex.com/es/faq/por-que-el-producto-no-aparece-en-el-sitio--frequentlyAskedQuestions_382">¿Por qué el producto no aparece en el sitio?</a> para entender cómo resolver este problema.
-</div>
+>ℹ️ Si su producto no aparece en el sitio web de su tienda después del registro, consulte el artículo [¿Por qué el producto no aparece en el sitio?](https://help.vtex.com/es/faq/por-que-el-producto-no-aparece-en-el-sitio--frequentlyAskedQuestions_382) para entender cómo resolver este problema.
 
diff --git a/docs/tracks/es/adding-the-magazine-luiza-integration.md b/docs/tracks/es/adding-the-magazine-luiza-integration.md
index 96e362c86..74f5bbe31 100644
--- a/docs/tracks/es/adding-the-magazine-luiza-integration.md
+++ b/docs/tracks/es/adding-the-magazine-luiza-integration.md
@@ -24,8 +24,7 @@ La integración con Magazine Luiza se realiza a través de IntegraCommerce, una
 
 Con esa integración, será posible __crear nuevas cuentas__ y también __migrar cuentas ya existentes (pronto)__ en Magazine Luiza. El paso a paso siguiente se adecua a los dos casos.
 
-<div class="alert alert-warning">
-<strong>NB:</strong> actualmente <strong>no se puede migrar cuentas antiguas</strong>. Estamos trabajando y pronto esta migración se hará automáticamente.</div>
+>⚠️ **NB:** actualmente **no se puede migrar cuentas antiguas**. Estamos trabajando y pronto esta migración se hará automáticamente.
 
 
 ## Detalle de los campos
diff --git a/docs/tracks/es/adding-warehouses.md b/docs/tracks/es/adding-warehouses.md
index 0868b53ca..95257bef0 100644
--- a/docs/tracks/es/adding-warehouses.md
+++ b/docs/tracks/es/adding-warehouses.md
@@ -41,9 +41,7 @@ Siga el siguiente procedimiento para registrar un inventario en su tienda:
 
 ## API REST
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Inventario y Envío  deben realizarse a través de AppKey y AppToken. Para entender más, acceda a  nuestro artículo sobre <a href="https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2">cómo generar un Appkey y un AppToken para autenticar sus integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Inventario y Envío  deben realizarse a través de AppKey y AppToken. Para entender más, acceda a  nuestro artículo sobre [cómo generar un Appkey y un AppToken para autenticar sus integraciones](https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2)
 
 Para registrar un **Inventario** por API, debe enviar un __POST__ para el siguiente  endpoint:
 
diff --git a/docs/tracks/es/amazon-account-settings.md b/docs/tracks/es/amazon-account-settings.md
index 85def77df..4f19cba10 100644
--- a/docs/tracks/es/amazon-account-settings.md
+++ b/docs/tracks/es/amazon-account-settings.md
@@ -33,6 +33,4 @@ Tras crear tu cuenta de seller, deberás autorizas VTEX en tu cuenta de Amazon S
 
 Tras realizar la autorización, serás redirigido al Admin VTEX y se completará este paso de la integración.  
 
-<div class="alert alert-info">
-Si tiene alguna duda sobre este paso, consulte la <a href="https://sellercentral.amazon.com/learn/courses?ref_=su_course_accordion&moduleId=1f61fcd3[…]-ed90359ff166&modLanguage=Portuguese&videoPlayer=youtube">documentación de Seller Central Amazon.</a>
-</div>
+>ℹ️ Si tiene alguna duda sobre este paso, consulte la [documentación de Seller Central Amazon.](https://sellercentral.amazon.com/learn/courses?ref_=su_course_accordion&moduleId=1f61fcd3[…]-ed90359ff166&modLanguage=Portuguese&videoPlayer=youtube)
diff --git a/docs/tracks/es/apple-pay.md b/docs/tracks/es/apple-pay.md
index 1083dcbd5..c0e445bfd 100644
--- a/docs/tracks/es/apple-pay.md
+++ b/docs/tracks/es/apple-pay.md
@@ -19,9 +19,7 @@ Sus clientes pueden comprar con Apple Pay, la [cartera digital](https://help.vte
 - Tener cuenta en `developer.apple.com`.
 - Tener contrato con un proveedor que procese pagos con Apple Pay.
 
-<div class="alert alert-warning">
-  Actualmente, Apple Pay solo funciona en los sistemas operativos MacOs e IOS, y en el navegador Safari. Para obtener más información, vaya a <a href="https://support.apple.com/es-es/HT208531">Dispositivos compatibles con Apple Pay</a>.
-</div>
+>⚠️ Actualmente, Apple Pay solo funciona en los sistemas operativos MacOs e IOS, y en el navegador Safari. Para obtener más información, vaya a [Dispositivos compatibles con Apple Pay](https://support.apple.com/es-es/HT208531).
 
 ## Configurar proveedor de pago
 
diff --git a/docs/tracks/es/authenticating-your-google-shopping-account.md b/docs/tracks/es/authenticating-your-google-shopping-account.md
index 4732771c5..0facddbaf 100644
--- a/docs/tracks/es/authenticating-your-google-shopping-account.md
+++ b/docs/tracks/es/authenticating-your-google-shopping-account.md
@@ -24,6 +24,4 @@ Después de configurar la integración, debe autenticar su cuenta de Google Shop
 6. Haga clic en `Deseo autenticar mi cuenta`.
 7. Haga clic en el botón `OK` para autorizar que la integración VTEX se conecte con el perfil del ID Business Manager.
 
-<div class="alert alert-info">
-Puede haber un retraso entre la finalización de la integración y el momento en que surte efecto porque la actualización no es sincrónica. Sin embargo, generalmente no toma más de unas cuantas horas.
-</div>
+>ℹ️ Puede haber un retraso entre la finalización de la integración y el momento en que surte efecto porque la actualización no es sincrónica. Sin embargo, generalmente no toma más de unas cuantas horas.
diff --git a/docs/tracks/es/backend-integrations.md b/docs/tracks/es/backend-integrations.md
index 112c637c2..bde641cbf 100644
--- a/docs/tracks/es/backend-integrations.md
+++ b/docs/tracks/es/backend-integrations.md
@@ -131,9 +131,7 @@ Después de definir y planificar la [arquitectura del catálogo](https://help.vt
 2. **API de Catálogo:** crear cada categoría mediante llamadas de API. Consulta los detalles en [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category).
 3. **Integración con back office:** importar categorías a partir de un software de back office externo (ERP o PIM) integrado a VTEX. El software puede ofrecer una integración nativa con VTEX o requerir el desarrollo de middleware que utilice la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Consulta los detalles en [Category migration from ERPs](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#category-migration-from-erps).
 
-<div class="alert alert-warning">
-Al importar las categorías de un software externo, la estructura de categorías en el software puede diferir de la de VTEX. En este caso, recomendamos crear una categoría simulada inactiva que no será visible en el storefront y que se puede utilizar para recibir todos los productos y SKU durante la importación. Una vez finalizada la importación, los productos pueden organizarse manualmente en el Admin VTEX para ajustarse al árbol de categorías deseado.
-</div>
+>⚠️ Al importar las categorías de un software externo, la estructura de categorías en el software puede diferir de la de VTEX. En este caso, recomendamos crear una categoría simulada inactiva que no será visible en el storefront y que se puede utilizar para recibir todos los productos y SKU durante la importación. Una vez finalizada la importación, los productos pueden organizarse manualmente en el Admin VTEX para ajustarse al árbol de categorías deseado.
 
 Las categorías tienen algunas limitaciones:
 
@@ -150,9 +148,7 @@ Las [marcas](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ
 2. **API de Catálogo:** crear cada marca mediante llamadas de API. Consulta los detalles en [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand).
 3. **Integración con back office:** importar marcas a partir de un software de back office externo (ERP o PIM) integrado a VTEX. El software puede ofrecer una integración nativa con VTEX o requerir el desarrollo de middleware que utilice la [API de Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Consulta los detalles en la sección [Create Brands](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-brands) de la guía de configuración de Catálogo para back office.
 
-<div class="alert alert-warning">
-Si el sistema de back office no tiene la información sobre marcas, se puede aplicar el mismo procedimiento mencionado anteriormente para categorías en el que se crea una marca simulada inactiva que solo se usa para la migración. Luego, la información de los productos puede ingresarse manualmente.
-</div>
+>⚠️ Si el sistema de back office no tiene la información sobre marcas, se puede aplicar el mismo procedimiento mencionado anteriormente para categorías en el que se crea una marca simulada inactiva que solo se usa para la migración. Luego, la información de los productos puede ingresarse manualmente.
 
 Para más información sobre la importación de marcas al back office, consulta [Brands](https://developers.vtex.com/docs/guides/brands).
 
@@ -201,9 +197,7 @@ La importación de productos debe seguir el orden descrito en la tabla a continu
 
 <br>
 
-<div class="alert alert-warning">
-Es común que los datos de productos en el ERP no sean adecuados para uso y visualización en una tienda online. Por esta razón, debe llevarse a cabo un proceso de enriquecimiento, que puede incluir reestructuración de categorías y la creación de descripciones de productos más detalladas y atractivas.
-</div>
+>⚠️ Es común que los datos de productos en el ERP no sean adecuados para uso y visualización en una tienda online. Por esta razón, debe llevarse a cabo un proceso de enriquecimiento, que puede incluir reestructuración de categorías y la creación de descripciones de productos más detalladas y atractivas.
 
 Después de la importación, también es importante garantizar que los datos de los productos y SKU se mantengan actualizados. Consulta las instrucciones en el artículo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information).
 
diff --git a/docs/tracks/es/basic-vtex-io-developer-setup.md b/docs/tracks/es/basic-vtex-io-developer-setup.md
index d14e2ff88..756945e29 100644
--- a/docs/tracks/es/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/es/basic-vtex-io-developer-setup.md
@@ -40,9 +40,7 @@ Cuando esté conectado, usted puede utilizar el comando `vtex whoami` para descu
 
 ![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
-<div class="alert alert-info">
-Sugerencia: Usted puede configurar su terminal para mostrar automáticamente su cuenta y workspace. La manera más fácil de hacer esto es usar nuestros <a href="https://github.com/vtex/dotfiles">dotfiles</a>, que configuran automáticamente la <a href="https://fishshell.com/">Fish Shell</a> y añaden una <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">función de prompt</a> para usted.
-</div>
+>ℹ️ Sugerencia: Usted puede configurar su terminal para mostrar automáticamente su cuenta y workspace. La manera más fácil de hacer esto es usar nuestros [dotfiles](https://github.com/vtex/dotfiles), que configuran automáticamente la [Fish Shell](https://fishshell.com/) y añaden una [función de prompt](https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish) para usted.
 
 ## Workspaces: su ambiente de desarrollo aislado
 
@@ -66,9 +64,7 @@ $ vtex use sunombre
 
 Esto cambia su toolbelt a un workspace llamado `sunombre`, y lo crea si no existe.
 
-<div class="alert alert-info">
-Sugerencia: Usted puede cambiar a (<em>y restablecer</em>) un workspace master con un solo comando con la flag <code>-r</code>. Esto es útil si desea empezar desde cero en el <code>master</code>.
-</div>
+>ℹ️ Sugerencia: Usted puede cambiar a (*y restablecer*) un workspace master con un solo comando con la flag `-r`. Esto es útil si desea empezar desde cero en el `master`.
 
 Los workspaces pueden ser nombrados arbitrariamente, pero generalmente es conveniente asignar su propio nombre cuando usted desea desarrollar en su ambiente.
 
diff --git a/docs/tracks/es/cadastrar-preco-base.md b/docs/tracks/es/cadastrar-preco-base.md
index a2643601e..0f7eccd5d 100644
--- a/docs/tracks/es/cadastrar-preco-base.md
+++ b/docs/tracks/es/cadastrar-preco-base.md
@@ -40,9 +40,7 @@ Si lo desea, es posible registrar un **precio de lista** asociado al precio base
 
 ## API REST
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para comprender más, acceda a nuestro artículo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">cómo generar un Appkey y un AppToken para autenticar sus integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para comprender más, acceda a nuestro artículo sobre [cómo generar un Appkey y un AppToken para autenticar sus integraciones](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para registrar el **precio base** de un SKU, usted necesita enviar un __PUT__ para el siguiente endpoint:
 
diff --git a/docs/tracks/es/cadastrar-tabelas-de-preco.md b/docs/tracks/es/cadastrar-tabelas-de-preco.md
index 05c25deaa..61e9690bf 100644
--- a/docs/tracks/es/cadastrar-tabelas-de-preco.md
+++ b/docs/tracks/es/cadastrar-tabelas-de-preco.md
@@ -31,9 +31,7 @@ Siga el siguiente procedimiento para registrar las tablas de precio de su tienda
 
 ## API REST
 
-<div class="alert alert-warning">
-Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">how to generate an AppKey and AppToken to authenticate integrations</a>
-</div>
+>⚠️ Authentications for Prices module's API REST calls should be done using AppKey and AppToken. For more info, read our article on [how to generate an AppKey and AppToken to authenticate integrations](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para registrar la **tabla de precio**, necesita enviar un __PUT__ para el siguiente  endpoint:
 
diff --git a/docs/tracks/es/cadastrar-trava-de-preco.md b/docs/tracks/es/cadastrar-trava-de-preco.md
index 39cf78aa8..8e1e6ccb4 100644
--- a/docs/tracks/es/cadastrar-trava-de-preco.md
+++ b/docs/tracks/es/cadastrar-trava-de-preco.md
@@ -31,9 +31,7 @@ Siga el siguiente procedimiento para registrar el bloqueo de precio:
 
 ## API REST
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para entender más, acceda a nuestro  artículo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">cómo generar un Appkey y un AppToken para autenticar sus integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para entender más, acceda a nuestro  artículo sobre [cómo generar un Appkey y un AppToken para autenticar sus integraciones](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para registrar el **bloqueo de precio**, necesita enviar en __POST__ para el siguiente  endpoint:
 
diff --git a/docs/tracks/es/canceling-an-order.md b/docs/tracks/es/canceling-an-order.md
index 0b6f641bc..cfae8fee4 100644
--- a/docs/tracks/es/canceling-an-order.md
+++ b/docs/tracks/es/canceling-an-order.md
@@ -19,9 +19,7 @@ Usted puede cancelar un pedido con VTEX de tres maneras diferentes:
 - Por API.
 - A petición del cliente.
 
-<div class="alert alert-warning">
-Una vez cancelado el pedido, no se puede cambiar su status. Es posible cancelar el pedido hasta antes de <b>Facturado</b>, después el pedido no puede ser modificado.
-</div>
+>⚠️ Una vez cancelado el pedido, no se puede cambiar su status. Es posible cancelar el pedido hasta antes de **Facturado**, después el pedido no puede ser modificado.
 
 <div class = "alert alert-info">
 No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
diff --git a/docs/tracks/es/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md b/docs/tracks/es/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
index 9c1569a74..1103ef1bd 100644
--- a/docs/tracks/es/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
+++ b/docs/tracks/es/capturar-dados-do-lead-antes-de-iniciar-uma-conversa-no-whatsapp.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/categories-concept-definition.md b/docs/tracks/es/categories-concept-definition.md
index 6a1929e10..fc6c145a2 100644
--- a/docs/tracks/es/categories-concept-definition.md
+++ b/docs/tracks/es/categories-concept-definition.md
@@ -20,9 +20,7 @@ Los tres principales niveles de categorías se denominan __Departamento__, __Cat
 
 En las categorías que debe configurar las Especificaciones (o Campos), que son las propiedades que usted puede agregar a sus productos y SKUs. Más adelante, veremos con detalles la relación entre categorías, productos, SKUs y especificaciones. 
 
-<div class="alert alert-info">
-Atención: sugerimos que el árbol de categorías de su tienda tenga como máximo tres niveles jerárquicos. Esto facilita la navegación del cliente por su tienda.
-</div>
+>ℹ️ Atención: sugerimos que el árbol de categorías de su tienda tenga como máximo tres niveles jerárquicos. Esto facilita la navegación del cliente por su tienda.
 
 ## Departamento 
 
@@ -34,9 +32,7 @@ Es el nivel más amplio dentro del árbol de categorías. Dentro del departament
 
 El segundo nivel del árbol de categorías se denomina __Categoría__. Este nivel está por debajo del __Departamento__ y por encima de la __Subcategoría__.
 
-<div class="alert alert-info"> 
-Normalmente, el término "categoría" se utiliza para referirse a un concepto genérico de segmentación. En VTEX, el término "Categoría" también se utiliza para referirse al segundo nivel jerárquico de un árbol de categorías.
-</div> 
+>ℹ️ Normalmente, el término "categoría" se utiliza para referirse a un concepto genérico de segmentación. En VTEX, el término "Categoría" también se utiliza para referirse al segundo nivel jerárquico de un árbol de categorías. 
 
 ## Subcategoría
 
diff --git a/docs/tracks/es/changing-the-instore-language.md b/docs/tracks/es/changing-the-instore-language.md
index 6d84012b9..bb27fe40d 100644
--- a/docs/tracks/es/changing-the-instore-language.md
+++ b/docs/tracks/es/changing-the-instore-language.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: cambiar-el-idioma-de-instore
 ---
 
-<div class="alert alert-danger">
-El cambio de idioma explicado en este artículo implica cambiar el archivo JavaScript <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ El cambio de idioma explicado en este artículo implica cambiar el archivo JavaScript `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 Actualmente, es posible usar el inStore en __portugués__, __inglés__ o __español__.
 
diff --git a/docs/tracks/es/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md b/docs/tracks/es/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
index fcfdcc950..3a4503194 100644
--- a/docs/tracks/es/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
+++ b/docs/tracks/es/como-distribuir-o-atendimento-no-whatsapp-para-mais-de-um-numero.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/como-funciona-o-adaptador-vtex.md b/docs/tracks/es/como-funciona-o-adaptador-vtex.md
index 97be2fa03..0f0b90ede 100644
--- a/docs/tracks/es/como-funciona-o-adaptador-vtex.md
+++ b/docs/tracks/es/como-funciona-o-adaptador-vtex.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugES: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md b/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md
index 43c48dd7d..6d86f0c3a 100644
--- a/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md
+++ b/docs/tracks/es/configuracao-da-estrutura-para-suporte-humano.md
@@ -21,9 +21,7 @@ Hay dos opciones de _partners_ preintegrados con el comercio conversacional de V
 * [Zenvia](#integracion-zenvia)
 * [Zendesk](#integracion-zendesk)
 
-<div class="alert alert-info">
-<p>Comunícate con el equipo de desarrollo de VTEX si deseas hacer una integración con otras plataformas.</p>
-</div>
+>ℹ️ Comunícate con el equipo de desarrollo de VTEX si deseas hacer una integración con otras plataformas.
 
 ## Integración Zenvia
 
diff --git a/docs/tracks/es/configurar-adaptador.md b/docs/tracks/es/configurar-adaptador.md
index 8bba9f774..5046add5b 100644
--- a/docs/tracks/es/configurar-adaptador.md
+++ b/docs/tracks/es/configurar-adaptador.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugES: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/configurar-erps.md b/docs/tracks/es/configurar-erps.md
index b0552e316..428edba7c 100644
--- a/docs/tracks/es/configurar-erps.md
+++ b/docs/tracks/es/configurar-erps.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugES: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/configure-clustered-conditions.md b/docs/tracks/es/configure-clustered-conditions.md
index a29f708e1..653610dc7 100644
--- a/docs/tracks/es/configure-clustered-conditions.md
+++ b/docs/tracks/es/configure-clustered-conditions.md
@@ -16,17 +16,13 @@ trackSlugES: condiciones-de-pago-clusterizadas
 
 Como hemos mencionado, Clustered Payment Conditions determina que una condición de pago se aplicará a uno o más consumidores.
 
-<div class="alert alert-warning">
-La clusterización de clientes se puede aplicar en condiciones de pago que se han configurado previamente.
-
-Esto significa que usted puede editar condiciones de pago ya existentes y aplicar condiciones de clusterización a esas reglas.
-</div>  
+>⚠️ La clusterización de clientes se puede aplicar en condiciones de pago que se han configurado previamente.
+>
+> Esto significa que usted puede editar condiciones de pago ya existentes y aplicar condiciones de clusterización a esas reglas.  
 
 Aquí explicaremos cómo configurar una condición especial de pago a partir de clústeres.
 
-<div class="alert alert-danger">
-<strong>Atención</strong>: solo se permite crear cinco clústeres de clientes por condición de pago.
-</div>
+>❗ **Atención**: solo se permite crear cinco clústeres de clientes por condición de pago.
 
 ## Crear una nueva condición de pago
 
diff --git a/docs/tracks/es/configure-integration-of-pick-up-points.md b/docs/tracks/es/configure-integration-of-pick-up-points.md
index 66576db8d..18a04ce07 100644
--- a/docs/tracks/es/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/es/configure-integration-of-pick-up-points.md
@@ -22,9 +22,7 @@ Cuando los pedidos que utilizan la opción de recogida en la tienda llegan a VTE
 
 ![configurar pontosderetirada01 ES](https://images.contentful.com/alneenqid6w5/39DuF7GI3SC432EtzjWlwn/6361d5707ff1139a6dfed63d1c48380c/configurar_pontosderetirada01_ES.JPG)
 
-<div class="alert alert-info">
-Antes de crear los puntos de recogida, debe solicitar a Mercado Livre la activación de la modalidad “Recogida en la tienda”. Para eso, contacte a su asesor comercial de Mercado Libre o abra un ticket para el equipo de <a href="https://developers.mercadolivre.com.br/en_us/support/">Soporte.</a>
-</div>
+>ℹ️ Antes de crear los puntos de recogida, debe solicitar a Mercado Livre la activación de la modalidad “Recogida en la tienda”. Para eso, contacte a su asesor comercial de Mercado Libre o abra un ticket para el equipo de [Soporte.](https://developers.mercadolivre.com.br/en_us/support/)
 
 Para criar os pontos de retirada, você vai precisar:
 
diff --git a/docs/tracks/es/configure-integration.md b/docs/tracks/es/configure-integration.md
index 5b8d6c900..725b8cf56 100644
--- a/docs/tracks/es/configure-integration.md
+++ b/docs/tracks/es/configure-integration.md
@@ -14,5 +14,5 @@ trackId: 5Yx5IrNa7Y48c6aSC8wu2Y
 trackSlugES: configurar-la-integracion-de-magazine-luiza
 ---
 
-<div class="alert alert-warning">Este contenido es exclusivamente regional; 
-por lo tanto, no se aplica a los países de habla española.</div>
+>⚠️ Este contenido es exclusivamente regional; 
+> por lo tanto, no se aplica a los países de habla española.
diff --git a/docs/tracks/es/configuring-banners.md b/docs/tracks/es/configuring-banners.md
index 1acc1f111..1ab1b9eb3 100644
--- a/docs/tracks/es/configuring-banners.md
+++ b/docs/tracks/es/configuring-banners.md
@@ -24,9 +24,7 @@ Para configurar un banner, sigue estos pasos:
 
 Después de configurar el banner, debes agregarlo a una página de tu tienda. Para ello, sigue los pasos del artículo [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner).
 
-<div class="alert alert-info">
-<p> Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configuración Multidioma (Beta)</a>para saber más.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo [VTEX Intelligent Search: configuración Multidioma (Beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners)para saber más.
 
 ![banner-form-es](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
 
diff --git a/docs/tracks/es/configuring-dafiti-connector.md b/docs/tracks/es/configuring-dafiti-connector.md
index f3f3a7caf..47a8781e8 100644
--- a/docs/tracks/es/configuring-dafiti-connector.md
+++ b/docs/tracks/es/configuring-dafiti-connector.md
@@ -44,9 +44,7 @@ La configuración del conector se realiza en el Admin. Para completarla, siga la
 
 - **Enviar Kit*:** si selecciona _No_, los SKU [registrados como kits](https://help.vtex.com/es/tutorial/cadastrando-kit--tutorials_215) no se enviarán a Dafiti. Al activar el _Sí_, todos los ítems de su política comercial se enviarán al marketplace, sin filtrar los SKU registrados como kits. Se pueden realizar cambios en la configuración del conector en cualquier momento, y esto no afecta a los SKU que ya han sido enviados. Por ejemplo, si cambiara su configuración de _Sí_ a _No_, los SKU enviados previamente a Dafiti no se eliminarán ni tendrán ningún cambio.
 
-  <div class="alert alert-info">
-Si se activa la opción <i>No</i>, los intentos de enviar SKU registrados como kits a Dafiti generarán el siguiente mensaje de advertencia: <i>«El conector está configurado para no enviar los SKU del tipo Kit»</i>. Este mensaje puede verse en Admin, en el módulo <b>MARKETPLACE > Integraciones > Productos,</b> al hacer clic en el SKU.
-</div>
+  >ℹ️ Si se activa la opción <i>No</i>, los intentos de enviar SKU registrados como kits a Dafiti generarán el siguiente mensaje de advertencia: <i>«El conector está configurado para no enviar los SKU del tipo Kit»</i>. Este mensaje puede verse en Admin, en el módulo **MARKETPLACE > Integraciones > Productos,** al hacer clic en el SKU.
 
 - **Nombre de SKU*:** determina cuál será la regla para nombrar los SKU en el portal de Dafiti. Debe seleccionar una de las combinaciones disponibles de los siguientes atributos: _Marca_, _Nombre del Producto_ y _Nombre del SKU._
 
diff --git a/docs/tracks/es/configuring-merchandising-rules.md b/docs/tracks/es/configuring-merchandising-rules.md
index 198d7f896..6d1ef9c21 100644
--- a/docs/tracks/es/configuring-merchandising-rules.md
+++ b/docs/tracks/es/configuring-merchandising-rules.md
@@ -32,9 +32,7 @@ Si deseas configurar una [regla de merchandising](https://help.vtex.com/es/track
   Para aplicar el efecto de personalización deseado, debes definir una o varias condiciones en esta etapa. Si deseas conocer cómo registrar una condición, lee [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
 10. Haz clic en `Guardar`.
 
-<div class="alert alert-info">
-  <p>Una vez guardados, la actualización de los cambios en las reglas de merchandising demoran un promedio de dos minutos.</p>
-</div>
+>ℹ️ Una vez guardados, la actualización de los cambios en las reglas de merchandising demoran un promedio de dos minutos.
 
 ## Ejemplo
 
@@ -78,9 +76,7 @@ Considera el siguiente ejemplo: deseas promover productos de la marca Beautyx du
 
 * **Remover**: excluye las condiciones seleccionadas del resultado, es decir, elimina los productos que estarán en el resultado de la búsqueda.
 
-  <div class="alert alert-info">
-   <p><strong>Agregar</strong> y <strong>Eliminar</strong> son compatibles con otros tipos de formas de ordenar que no se basan en la relevancia configurada. Por lo tanto, si agregas o eliminas un producto utilizando una regla de <em>merchandising </em>y si, por ejemplo, el cliente de tu tienda ordena los resultados de búsqueda por precio, los productos se ordenarán por precio, pero los productos mostrados respetarán la regla de <em>merchandising</em>.</p>
-  </div>
+  >ℹ️ **Agregar** y **Eliminar** son compatibles con otros tipos de formas de ordenar que no se basan en la relevancia configurada. Por lo tanto, si agregas o eliminas un producto utilizando una regla de *merchandising *y si, por ejemplo, el cliente de tu tienda ordena los resultados de búsqueda por precio, los productos se ordenarán por precio, pero los productos mostrados respetarán la regla de *merchandising*.
 
 * **Promover**: resalta las condiciones seleccionadas en el resultado. Da más relevancia a un producto que ya aparecería en el resultado de la búsqueda.
 
@@ -88,10 +84,6 @@ Considera el siguiente ejemplo: deseas promover productos de la marca Beautyx du
 
 * **Dejar de promover**: oculta las condiciones seleccionadas en el resultado. Permite dejar de priorizar un producto que ya aparece en los resultados de la búsqueda.
 
-  <div class="alert alert-info">
-   <p><strong>Promover</strong> y <strong>Dejar de promover</strong> solo funcionan cuando el cliente de la tienda ordena los resultados de la búsqueda por relevancia. En cambio, si ordena los resultados por precio, por ejemplo, los productos se ordenarán estrictamente por precio y no se utilizará la regla de <em>merchandising</em>.</p>
-  </div>
+  >ℹ️ **Promover** y **Dejar de promover** solo funcionan cuando el cliente de la tienda ordena los resultados de la búsqueda por relevancia. En cambio, si ordena los resultados por precio, por ejemplo, los productos se ordenarán estrictamente por precio y no se utilizará la regla de *merchandising*.
 
-  <div class="alert alert-warning">
-   <p>No configures condiciones que afecten a los mismos productos tanto en la sección <strong>Promover</strong> como en la sección <strong>Dejar de promover</strong> porque se producirán efectos opuestos. Si la configuración de esta condición es incorrecta, esa configuración incorrecta afecta negativamente el comportamiento de la funcionalidad y no se mostrarán los resultados deseados.</p>
-  </div>
+  >⚠️ No configures condiciones que afecten a los mismos productos tanto en la sección **Promover** como en la sección **Dejar de promover** porque se producirán efectos opuestos. Si la configuración de esta condición es incorrecta, esa configuración incorrecta afecta negativamente el comportamiento de la funcionalidad y no se mostrarán los resultados deseados.
diff --git a/docs/tracks/es/configuring-price-divergence-rule-amazon.md b/docs/tracks/es/configuring-price-divergence-rule-amazon.md
index 08f78f7f5..b19467e07 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-amazon.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-amazon.md
@@ -20,8 +20,6 @@ En el Admin VTEX, en **PEDIDOS > Gestión de pedidos > Autorización de pedidos*
 
 La regla de Divergencia de precios se compone de una o varias reglas de autorización de pedidos, cada una de las cuales corresponde a un intervalo porcentual del precio del pedido. Las reglas de autorización se pueden configurar para negar automáticamente, autorizar automáticamente o exigir la autorización manual del pedido.
 
-<div class="alert alert-warning">
-Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Amazon.
-</div> 
+>⚠️ Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Amazon. 
 
 Se recomienda configurar la regla de Divergencia de precios antes de avanzar al siguiente paso de configuración de la integración con Amazon. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios. Puedes seguirlos en tu Admin VTEX, en **MARKETPLACE > Integraciones > Pedidos**.
diff --git a/docs/tracks/es/configuring-price-divergence-rule-dafiti.md b/docs/tracks/es/configuring-price-divergence-rule-dafiti.md
index 41fee498e..89e6b617c 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-dafiti.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-dafiti.md
@@ -20,8 +20,6 @@ En el Admin VTEX, en **PEDIDOS > Gestión de pedidos > Autorización de pedidos*
 
 La regla de Divergencia de precios se compone de una o varias reglas de autorización de pedidos, cada una de las cuales corresponde a un intervalo porcentual del precio del pedido. Las reglas de autorización se pueden configurar para negar automáticamente, autorizar automáticamente o exigir la autorización manual del pedido.
 
-<div class="alert alert-warning">
-Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Dafiti.
-</div> 
+>⚠️ Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Dafiti. 
 
 Se recomienda configurar la regla de Divergencia de precios antes de avanzar al siguiente paso de configuración de la integración con Dafiti. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios. Puedes seguirlos en tu Admin VTEX, en **MARKETPLACE > Integraciones > Pedidos**.
diff --git a/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md b/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md
index 0f9d5585f..5f1b7c3c6 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-mercado-libre.md
@@ -20,8 +20,6 @@ En el Admin VTEX, en **Configuración de la tienda > Pedidos > Autorización de
 
 La regla de Divergencia de precios se compone de una o varias reglas de autorización de pedidos, cada una de las cuales corresponde a un intervalo porcentual del precio del pedido. Las reglas de autorización se pueden configurar para negar automáticamente, autorizar automáticamente o exigir la autorización manual del pedido.
 
-<div class="alert alert-warning">
-Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Mercado Libre.
-</div> 
+>⚠️ Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Mercado Libre. 
 
 Se recomienda configurar la regla de Divergencia de precios antes de avanzar al siguiente paso de configuración de la integración con Mercado Libre. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios. Puedes seguirlos en tu Admin VTEX, en **Marketplace > Conexiones > Pedidos**.
diff --git a/docs/tracks/es/configuring-price-divergence-rule-via.md b/docs/tracks/es/configuring-price-divergence-rule-via.md
index cbe9f2fb5..dd0d17080 100644
--- a/docs/tracks/es/configuring-price-divergence-rule-via.md
+++ b/docs/tracks/es/configuring-price-divergence-rule-via.md
@@ -20,8 +20,6 @@ En el Admin VTEX, en **PEDIDOS > Gestión de pedidos > Autorización de pedidos*
 
 La regla de Divergencia de precios se compone de una o varias reglas de autorización de pedidos, cada una de las cuales corresponde a un intervalo porcentual del precio del pedido. Las reglas de autorización se pueden configurar para negar automáticamente, autorizar automáticamente o exigir la autorización manual del pedido.
 
-<div class="alert alert-warning">
-Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Via.
-</div> 
+>⚠️ Después de que hayas configurado la regla de Divergencia de valores, esta se aplicará a todos los marketplaces en los que actúes como seller. Estos pueden ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conectores certificados (partners)</a>, o otros <a href= "https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> además de Via. 
 
 Se recomienda configurar la regla de Divergencia de precios antes de avanzar al siguiente paso de configuración de la integración con Via. Si no se cumple esta recomendación la integración se realiza, pero los pedidos con divergencia de valores se retienen hasta que se crie la regla de Divergencia de precios. Puedes seguirlos en tu Admin VTEX, en **MARKETPLACE > Integraciones > Pedidos**.
diff --git a/docs/tracks/es/configuring-ship-from-store.md b/docs/tracks/es/configuring-ship-from-store.md
index f4daba01e..18e0f5eeb 100644
--- a/docs/tracks/es/configuring-ship-from-store.md
+++ b/docs/tracks/es/configuring-ship-from-store.md
@@ -28,9 +28,7 @@ En primer lugar, consideremos los requisitos previos que su tienda necesita para
 
 ## Cómo implementar el Ship From Store
 
-<div class="alert alert-info">
-Aunque es posible implementar el Ship From Store de otras maneras, en este artículo explicaremos cómo hacerlo utilizando las features de cuenta franquicia Seller White Label. Esto se debe a que esta es la arquitectura más recomendada por VTEX para este tipo de proyecto.
-</div>
+>ℹ️ Aunque es posible implementar el Ship From Store de otras maneras, en este artículo explicaremos cómo hacerlo utilizando las features de cuenta franquicia Seller White Label. Esto se debe a que esta es la arquitectura más recomendada por VTEX para este tipo de proyecto.
 
 Estos son los pasos para implementar el __Ship From Store__:
 
diff --git a/docs/tracks/es/configuring-synonyms.md b/docs/tracks/es/configuring-synonyms.md
index f598acc96..61cd61a35 100644
--- a/docs/tracks/es/configuring-synonyms.md
+++ b/docs/tracks/es/configuring-synonyms.md
@@ -41,9 +41,7 @@ Siga el proceso paso a paso para configurar sinónimos individualmente en VTEX A
 
 La alteración puede tardar hasta dos horas en aplicarse.
 
-<div class="alert alert-info">
-<p>Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos">VTEX Intelligent Search: configuración Multidioma (Beta)</a> para saber más.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo [VTEX Intelligent Search: configuración Multidioma (Beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos) para saber más.
 
 ## Importar CSV
 
@@ -90,7 +88,5 @@ Tiendas que utilizan configuración multidioma (beta) deben seguir la siguiente
    __Ejemplo:__
    - `tv,smart tv;true;en-GB`: al buscar cualquiera de estos términos en la tienda en el idioma inglés (`locale en-GB`), se mostrará cualquier producto que contenga uno de esos términos en los resultados de búsqueda.
 
-<div class="alert alert-warning">
-  <p> Si el archivo .csv importado no contiene el <code>locale</code>, el sinónimo será válido para todos los idiomas disponibles en la tienda. </p>
-</div>
+>⚠️ Si el archivo .csv importado no contiene el `locale`, el sinónimo será válido para todos los idiomas disponibles en la tienda.
 
diff --git a/docs/tracks/es/configuring-the-amazon-integration.md b/docs/tracks/es/configuring-the-amazon-integration.md
index 212ab029a..f52a329bd 100644
--- a/docs/tracks/es/configuring-the-amazon-integration.md
+++ b/docs/tracks/es/configuring-the-amazon-integration.md
@@ -34,9 +34,7 @@ Una vez que haya completado los pasos para configurar su tienda en VTEX y Amazon
 - **Don’t send price to Amazon:** Amazon le ofrece la posibilidad de utilizar su sistema para parametrizar los precios de los productos. Para utilizar este servicio, marque la opción *ON* para que la integración no envíe los precios de VTEX. Si los precios se envían a través de la integración, sobrescribirán los precios en el sistema de Amazon.
 - **Send KIT*:** si selecciona *No*, los SKU [registrados como kit](https://help.vtex.com/es/tutorial/cadastrando-kit--tutorials_215) no se envían a Amazon. Si selecciona Sí, todos los ítems de su política comercial se enviarán al marketplace, incluso los SKU registrados como kit. Se pueden realizar cambios en la configuración del conector en cualquier momento, sin afectar a los SKU que ya han sido enviados. Por ejemplo, si cambiara la configuración de *Sí* a *No*, los SKU enviados anteriormente a Amazon no se eliminarían ni modificarían.
 
-<div class="alert alert-info">
-Si se activa la opción <i>No</i>, los intentos de enviar SKU registrados como kit a Amazon resultarán en la siguiente advertencia: «El conector está configurado para no enviar SKU del tipo Kit». Este mensaje se puede ver en el Admin VTEX, en el módulo <b>MARKETPLACE > Integraciones > Productos</b>, haciendo clic en el SKU.
-</div>
+>ℹ️ Si se activa la opción <i>No</i>, los intentos de enviar SKU registrados como kit a Amazon resultarán en la siguiente advertencia: «El conector está configurado para no enviar SKU del tipo Kit». Este mensaje se puede ver en el Admin VTEX, en el módulo **MARKETPLACE > Integraciones > Productos**, haciendo clic en el SKU.
 
 - **Notify by email if an error occurs in an order:** ingrese el email del responsable técnico. Si se produce algún error al integrar el pedido, se enviará un mensaje a la dirección de email registrada. 
 
diff --git a/docs/tracks/es/configuring-the-google-shopping-integration.md b/docs/tracks/es/configuring-the-google-shopping-integration.md
index 5f1a787ee..4080a1775 100644
--- a/docs/tracks/es/configuring-the-google-shopping-integration.md
+++ b/docs/tracks/es/configuring-the-google-shopping-integration.md
@@ -16,9 +16,7 @@ trackSlugES: integracion-con-google-shopping
 
 Esta guía describe cómo llevar a cabo la integración con Google Shopping utilizando el conector desarrollado por VTEX, que debiera ser su elección estándar ya que es más eficiente y seguro.
 
-<div class="alert alert-danger">
-La integración puede ser <a href="https://help.vtex.com/es/tutorial/configurando-xml--tutorials_242">configurada por archivo XML.</a> Se desaconseja realizar simultáneamente la <a href="https://help.vtex.com/es/tutorial/como-configurar-xml-do-google-shopping--frequentlyAskedQuestions_372">configuración XML de Google Shopping</a> y del conector nativo porque puede crear conflictos y discrepancia de datos.
-</div>
+>❗ La integración puede ser [configurada por archivo XML.](https://help.vtex.com/es/tutorial/configurando-xml--tutorials_242) Se desaconseja realizar simultáneamente la [configuración XML de Google Shopping](https://help.vtex.com/es/tutorial/como-configurar-xml-do-google-shopping--frequentlyAskedQuestions_372) y del conector nativo porque puede crear conflictos y discrepancia de datos.
 
 Para llevar a cabo la integración por conector, **es requisito** **tener una cuenta en Google Merchant Center. **Si aún no tiene una cuenta, consulte el tutorial de Google [Regístrese en Google Merchant Center](https://support.google.com/merchants/answer/188924?hl=es-419&ref_topic=7294166). 
 
diff --git a/docs/tracks/es/configuring-the-integration-dafiti.md b/docs/tracks/es/configuring-the-integration-dafiti.md
index 7071cccad..2ba3753ae 100644
--- a/docs/tracks/es/configuring-the-integration-dafiti.md
+++ b/docs/tracks/es/configuring-the-integration-dafiti.md
@@ -22,6 +22,4 @@ Después de finalizar el [registro en el portal de Dafiti](https://www.dafiti.co
 2. [Configurar el conector](https://help.vtex.com/es/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i/3PV2OACP2E4O4uOKKW2sMg).
 3. [Enviar productos a Dafiti](https://help.vtex.com/es/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i/3b8BZfB1BC8G8SCe0ao46m).
 
-<div class="alert alert-warning">
-Es importante que la transportadora registrada en VTEX se encuentre entre las que Dafiti acepta. De lo contrario, se generará un error de seguimiento del pedido. Además, el nombre de la transportadora registrado debe ser estrictamente igual al nombre aceptado por Dafiti.
-</div>
+>⚠️ Es importante que la transportadora registrada en VTEX se encuentre entre las que Dafiti acepta. De lo contrario, se generará un error de seguimiento del pedido. Además, el nombre de la transportadora registrado debe ser estrictamente igual al nombre aceptado por Dafiti.
diff --git a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 9b18c3eb4..e580c518d 100644
--- a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -33,9 +33,7 @@ Independientemente de que tengas instalada la <a href= "https://apps.vtex.com/vt
 8. A continuación, haz clic en `Continuar`.
 9. Elige qué permisos deben concederse a VTEX en la integración.
 
-  <div class="alert alert-danger">
-Para que la integración funcione correctamente, se recomienda conceder todos los permisos indicados. Por estándar, aparecen como habilitados.
-</div>
+  >❗ Para que la integración funcione correctamente, se recomienda conceder todos los permisos indicados. Por estándar, aparecen como habilitados.
 
 10. Haz clic en `Siguiente`.
 11. En la ventana abierta, aparecerá una confirmación de que la integración se ha realizado. Haz clic en `Listo`.
diff --git a/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index ea164dcf9..27ff07f95 100644
--- a/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -41,9 +41,7 @@ En esta parte del formulario, debes rellenar la información que servirá para i
 * **ID del afiliado:** identificador del nuevo [afiliado](https://help.vtex.com/es/tutorial/que-es-afiliado--4bN3e1YarSEammk2yOeMc0) que deseas crear para la integración. El ID del afiliado debe contener solo 3 consonantes y no puede estar asociado a un afiliado existente. Sugerimos usar `TKT` para identificar fácilmente TikTok. Es importante que compruebes en **Gestión de pedidos > Configuración > Afiliados** que el ID no está en uso. El afiliado se creará automáticamente al finalizar la configuración. 
 * **Política comercial:** campo para seleccionar la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que se asociará a la integración del catálogo con TikTok. Actualmente, la integración solo acepta políticas comerciales con BRL como moneda. Consulta la sección [Envío de datos de productos a TikTok](#envio-de-datos-de-produtos-a-tiktok) para más información.
 
-<div class="alert alert-warning">
-  <p>No cambies la configuración del afiliado que se creó automáticamente durante la integración. Si, en el futuro, se introduce algún cambio manual en la configuración del afiliado en <strong>Gestión de pedidos > Configuración > Afiliados</strong>, la integración puede dejar de funcionar.</p>
-</div>
+>⚠️ No cambies la configuración del afiliado que se creó automáticamente durante la integración. Si, en el futuro, se introduce algún cambio manual en la configuración del afiliado en **Gestión de pedidos > Configuración > Afiliados**, la integración puede dejar de funcionar.
 
 ### Datos de la empresa
 
@@ -74,9 +72,7 @@ Después de rellenar el formulario de configuración de la integración, debes c
 
 ## 3. Configurar TikTok for Business
 
-<div class="alert alert-warning">
-  <p>Te recomendamos que desactives las extensiones que bloquean los anuncios en tu navegador para evitar errores en los pasos a continuación.</p>
-</div>
+>⚠️ Te recomendamos que desactives las extensiones que bloquean los anuncios en tu navegador para evitar errores en los pasos a continuación.
 
 En la página **Set up TikTok for Business** (Configurar TikTok for Business), que se muestra abajo, debes seguir las instrucciones de configuración que se describen a continuación.
 
@@ -103,9 +99,7 @@ Una vez completada esta configuración, serás redirigido a **Marketplace > TikT
 
 ### Envío de datos de productos a TikTok
 
-<div class="alert alert-warning">
-  <p>TikTok solo sincroniza productos que se ajustan a las políticas publicitarias de la plataforma. Consulta las <a href="https://ads.tiktok.com/help/article?aid=9550">Políticas publicitarias de TikTok</a> para obtener más información.</p>
-</div>
+>⚠️ TikTok solo sincroniza productos que se ajustan a las políticas publicitarias de la plataforma. Consulta las [Políticas publicitarias de TikTok](https://ads.tiktok.com/help/article?aid=9550) para obtener más información.
 
 Una vez configurada la integración, el envío de productos a TikTok es un proceso automático. Los datos enviados son:
 
diff --git a/docs/tracks/es/create-a-product.md b/docs/tracks/es/create-a-product.md
index 0e2b614d1..a6ecbf6cf 100644
--- a/docs/tracks/es/create-a-product.md
+++ b/docs/tracks/es/create-a-product.md
@@ -16,13 +16,9 @@ trackSlugES: vtex-getting-started
 
 En primer lugar, es importante entender la diferencia entre SKU y producto - esta diferencia se refiere a la plataforma VTEX, pero también al tratamiento dado a estos conceptos por la mayoría de las operaciones de e-commerce.
 
-<div class="alert alert-info">
-</strong>SKU:</strong> la unidad más pequeña posible de los artículos vendidos en la tienda. Stock y precio, por ejemplo, son propiedades del SKU.
-</div>
+>ℹ️ </strong>SKU:</strong> la unidad más pequeña posible de los artículos vendidos en la tienda. Stock y precio, por ejemplo, son propiedades del SKU.
 
-<div class="alert alert-info">
-<strong>Producto:</strong> agregador de SKUs.
-</div>
+>ℹ️ **Producto:** agregador de SKUs.
 
 Vea los ejemplos siguientes:
 
@@ -35,9 +31,7 @@ En la vitrina de la tienda, el cliente verá sólo el producto __Pantalones__, y
 
 La gestión de su inventario visualiza por separado cada uno de los SKUs que componen ese producto. Así que usted puede saber, por ejemplo, que tiene 50 pantalones M en stock, pero sólo 2 pantalones G.
 
-<div class="alert alert-info">
-<strong>Atención</strong>: Cada vez que crea un SKU, usted necesita antes crear el producto.
-</div>
+>ℹ️ **Atención**: Cada vez que crea un SKU, usted necesita antes crear el producto.
 
 Vamos a ver cómo crear el producto.
 
diff --git a/docs/tracks/es/create-an-account.md b/docs/tracks/es/create-an-account.md
index 20d9a1635..cfb9e2dbd 100644
--- a/docs/tracks/es/create-an-account.md
+++ b/docs/tracks/es/create-an-account.md
@@ -18,8 +18,6 @@ Al contratar a VTEX, la tienda recibe un account, es decir, la cuenta de la tien
 
 Para desarrollar apps con VTEX IO, es necesario antes que nada tener acceso al account de una tienda. 
 
-<div class="alert alert-info">
-Toda aplicación creada con VTEX IO se desarrolla en el contexto de una cuenta VTEX.
-</div>
+>ℹ️ Toda aplicación creada con VTEX IO se desarrolla en el contexto de una cuenta VTEX.
 
 Si usted todavía no tiene acceso a ninguna cuenta y necesita crear una, póngase en contacto con el equipo comercial de VTEX y después lea el artículo sobre cómo [enlazar su account name a un website](/es/tutorial/vincular-un-account-name-a-un-website-binding).
diff --git a/docs/tracks/es/create-an-sku.md b/docs/tracks/es/create-an-sku.md
index 8c7e1c763..4d909097b 100644
--- a/docs/tracks/es/create-an-sku.md
+++ b/docs/tracks/es/create-an-sku.md
@@ -33,6 +33,4 @@ Usted será llevado a la pantalla de registro de SKU.
 
 Todos los campos disponibles en esta pantalla se explican en el artículo [Campos de registro de SKU](/es/tutorial/campos-de-registro-de-sku).
 
-<div class="alert alert-info">
-A veces un producto no tiene variaciones que justifiquen la creación de más de un SKU para él. En este caso, no hay ningún problema en crear un SKU con el mismo nombre del producto. Sólo recuerde que siempre debe crear <strong>al menos un SKU para cada producto</strong>.
-</div>
+>ℹ️ A veces un producto no tiene variaciones que justifiquen la creación de más de un SKU para él. En este caso, no hay ningún problema en crear un SKU con el mismo nombre del producto. Sólo recuerde que siempre debe crear **al menos un SKU para cada producto**.
diff --git a/docs/tracks/es/create-the-category-tree.md b/docs/tracks/es/create-the-category-tree.md
index 7ee5ec126..6adaab3bb 100644
--- a/docs/tracks/es/create-the-category-tree.md
+++ b/docs/tracks/es/create-the-category-tree.md
@@ -22,9 +22,7 @@ Entonces es por ella que necesitamos empezar.
 
 ## ¿Qué es un árbol de categorías?
 
-<div class="alert alert-info">
-El árbol de categorías es el conjunto de categorías de su sitio, <strong>distribuidas según relaciones de jerarquía</strong>.
-</div>
+>ℹ️ El árbol de categorías es el conjunto de categorías de su sitio, **distribuidas según relaciones de jerarquía**.
 
 ## Ejemplo
 
diff --git a/docs/tracks/es/creating-accounts.md b/docs/tracks/es/creating-accounts.md
index 4a26629b3..16f52a940 100644
--- a/docs/tracks/es/creating-accounts.md
+++ b/docs/tracks/es/creating-accounts.md
@@ -20,9 +20,7 @@ El siguiente paso es crear cuentas para los clientes a los que desea ofrecer cr
 - [Múltiples cuentas masivas (Admin VTEX)](#crear-varias-cuentas-importacion-masiva)
 - [Cuenta individual (Customer Credit API)](#crear-cuenta-a-traves-de-api)
 
-<div class="alert alert-info">
-Las cuentas creadas en la aplicación Customer Credit no tienen relación ni comparten datos con la base de clientes registrada en <a href="https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-datos">entidades de Master Data</a> de la tienda. Para que un cliente pueda utilizar Customer Credit como método de pago, el comerciante debe registrar su cuenta en la aplicación, incluso si el cliente ya tiene una cuenta en la tienda. 
-</div>
+>ℹ️ Las cuentas creadas en la aplicación Customer Credit no tienen relación ni comparten datos con la base de clientes registrada en [entidades de Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-datos) de la tienda. Para que un cliente pueda utilizar Customer Credit como método de pago, el comerciante debe registrar su cuenta en la aplicación, incluso si el cliente ya tiene una cuenta en la tienda.
 
 ## Crear cuentas individualmente
 
@@ -34,9 +32,7 @@ Para registrar un nuevo cliente en Customer Credit, siga los pasos a continuaci
 4. En __Crédito__, ingrese los valores de __Límite de crédito (BRL)__ y __Tolerancia__ que desea poner a disposición del cliente.
 5. Haga clic en `Confirmar`.
 
-<div class="alert alert-warning">
-El llenado del campo <b>Email</b> es obligatorio, ya que la plataforma VTEX utiliza esta información para autentificar el acceso del cliente a los límites de crédito de su cuenta. Para obtener más información sobre protección de datos, visite <a href="https://help.vtex.com/es/tutorial/seguridad-de-smartcheckout--3SrJuuhrqwePUg1rp1exfB">Seguridad de SmartCheckout</a>.
-</div>
+>⚠️ El llenado del campo **Email** es obligatorio, ya que la plataforma VTEX utiliza esta información para autentificar el acceso del cliente a los límites de crédito de su cuenta. Para obtener más información sobre protección de datos, visite [Seguridad de SmartCheckout](https://help.vtex.com/es/tutorial/seguridad-de-smartcheckout--3SrJuuhrqwePUg1rp1exfB).
 
 A partir de este momento, la nueva cuenta creada se mostrará en la pantalla __Cuentas__.
 
@@ -71,9 +67,7 @@ Para crear varias cuentas al mismo tiempo (en masa) en Customer Credit, puede ut
 
 A partir de este momento, las nuevas cuentas creadas mediante la plantilla .csv estarán disponibles en la pantalla __Cuentas__.
 
-<div class="alert alert-warning">
-También es posible rastrear procesos anteriores de creación de múltiples cuentas, identificando si las cuentas se crearon correctamente. Para comprobar esta información, haga clic en <b>Historial de importación</b> en la pantalla <b>Cuentas</b>.
-</div>  
+>⚠️ También es posible rastrear procesos anteriores de creación de múltiples cuentas, identificando si las cuentas se crearon correctamente. Para comprobar esta información, haga clic en **Historial de importación** en la pantalla **Cuentas**.  
 
 ### Actualizar varias cuentas (importación masiva)
 
diff --git a/docs/tracks/es/creating-and-editing-users.md b/docs/tracks/es/creating-and-editing-users.md
index 8dbf81a8f..e645b973b 100644
--- a/docs/tracks/es/creating-and-editing-users.md
+++ b/docs/tracks/es/creating-and-editing-users.md
@@ -46,6 +46,4 @@ No se puede cambiar el correo electrónico. Para esto, es necesario hacer un nue
 2. Seleccione el usuario deseado y haga clic en el **ícono del bote de basura** en la columna de acciones.
 3. Haga clic en **confirmar**.
 
-<div class="alert alert-info">
-Aunque los tokens de integración aparecen en la lista de usuarios, no se pueden eliminar. Para deshabilitarlos, vaya a <em>Configuraciónes de la cuenta > Gestión de la cuenta > Cuenta</em> y desmarque el campo <strong>Estado de los tokens</strong>.
-</div>
+>ℹ️ Aunque los tokens de integración aparecen en la lista de usuarios, no se pueden eliminar. Para deshabilitarlos, vaya a *Configuraciónes de la cuenta > Gestión de la cuenta > Cuenta* y desmarque el campo **Estado de los tokens**.
diff --git a/docs/tracks/es/creating-discount-coupons.md b/docs/tracks/es/creating-discount-coupons.md
index 4a9fd73d6..0587d511e 100644
--- a/docs/tracks/es/creating-discount-coupons.md
+++ b/docs/tracks/es/creating-discount-coupons.md
@@ -36,9 +36,9 @@ Para crear un cupón de descuento, siga los pasos a continuación:
 6. Haga clic en **Restricciones y limitaciones de uso** y defina la cantidad de productos que se pueden comprar con este cupón, independientemente de cuántas compras se realicen para alcanzar ese número.
 7. Haga clic en el botón **Guardar**.
 
-<div class="alert alert-info">
-No es necesario crear un <code>utm_source</code> y un <code>utm_campaign</code>. Pero es necesario crear <b>por lo menos uno </b> de estos.<br>
-Consulte el artículo <a href="https://help.vtex.com/es/tutorial/que-son-utm-source-utm-campaign-y-utm-medium">Qué son utm_source, utm_campaign y utm_medium</a> para entender mejor lo que son estos UTMs.
-</div>
+>ℹ️ No es necesario crear un `utm_source` y un `utm_campaign`. Pero es necesario crear **por lo menos uno ** de estos.
+>
+> 
+> Consulte el artículo [Qué son utm_source, utm_campaign y utm_medium](https://help.vtex.com/es/tutorial/que-son-utm-source-utm-campaign-y-utm-medium) para entender mejor lo que son estos UTMs.
 
 Al momento de crear una promoción regular, debe seleccionar el flag  `utm_source` y/o `utm_campaign`e ingresar los UTM informados durante la creación del cupón en los campos correspondientes.
diff --git a/docs/tracks/es/creating-franchise-accounts.md b/docs/tracks/es/creating-franchise-accounts.md
index 32ae1eda9..8f9336c04 100644
--- a/docs/tracks/es/creating-franchise-accounts.md
+++ b/docs/tracks/es/creating-franchise-accounts.md
@@ -24,9 +24,7 @@ Al crear cuentas franquicia, cada una de tus tiendas físicas tendrá un Admin V
 
 Tus cuentas franquicia funcionarán como [Sellers White Label](https://help.vtex.com/es/tutorial/que-son-cuenta-franquicia-y-seller-white-label--5orlGHyDHGAYciQ64oEgKa#que-es-un-seller-white-label). Esto significa que cuando se realiza un pedido por cualquier canal, ya sea VTEX Sales App o ecommerce, el sistema buscará entre todos los sellers aquel que pueda entregar con el mejor [SLA](https://help.vtex.com/es/tutorial/que-es-el-sla-de-operacion-de-la-plataforma--2cIFrsY5S8usk84OU4QOKm).
 
-<div class="alert alert-warning">
-  <p>Cada seller debe tener un nro. de registro de persona jurídica diferente para que los pagos de los pedidos funcionen correctamente.</p>
-</div>
+>⚠️ Cada seller debe tener un nro. de registro de persona jurídica diferente para que los pagos de los pedidos funcionen correctamente.
 
 La logística de cada una de las cuentas franquicia se puede gestionar en un Admin VTEX separado. Para acceder, introduce la URL `(nombre-de-la-cuenta-franquicia).myvtex.com/admin`.
 
diff --git a/docs/tracks/es/creating-merchandising-rules-visual-editor.md b/docs/tracks/es/creating-merchandising-rules-visual-editor.md
index b54bc86a5..5e0237747 100644
--- a/docs/tracks/es/creating-merchandising-rules-visual-editor.md
+++ b/docs/tracks/es/creating-merchandising-rules-visual-editor.md
@@ -42,9 +42,7 @@ Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vte
       Más información sobre estas acciones en los puntos **4, 5, 6, 8, 9** y **11** de la sección [Acciones disponibles en el Editor visual](#acciones-disponibles-en-el-editor-visual).
 9. Haz clic en `Guardar`.
 
- <div class="alert alert-info">
-  <p>Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.</p>
-</div>
+ >ℹ️ Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.
 
 ## Acciones disponibles en el Editor visual
 
diff --git a/docs/tracks/es/creating-or-editing-a-page-template.md b/docs/tracks/es/creating-or-editing-a-page-template.md
index 53186a073..92be2ad6c 100644
--- a/docs/tracks/es/creating-or-editing-a-page-template.md
+++ b/docs/tracks/es/creating-or-editing-a-page-template.md
@@ -32,15 +32,16 @@ Vea a continuación el procedimiento:
 4. Haga clic en __HTML Templates__.
 5. Justo debajo, haga clic en __New template__.
 6. Rellene el campo __Template Name__.
-<div class="alert alert-danger">
-  <p>Al rellenar el <b>Template Name</b>, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Al rellenar el **Template Name**, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 7. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 8. En la esquina superior derecha, haga clic en el botón  __Save Template__.![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
diff --git a/docs/tracks/es/creating-regular-promotions.md b/docs/tracks/es/creating-regular-promotions.md
index 404b48fb3..b664cd6a0 100644
--- a/docs/tracks/es/creating-regular-promotions.md
+++ b/docs/tracks/es/creating-regular-promotions.md
@@ -137,9 +137,7 @@ técnica</a>.</p>.
 
 - **Número de cuotas:** el descuento se concederá si la cantidad de cuotas seleccionada por el cliente está en el intervalo registrado. Este campo no se aplica a la selección de boleto.
 
-<div class="alert alert-warning">
-Las promociones por medio de pago y número de cuotas no se aplican a pedidos pagados con dos tarjetas o tarjetas de regalo.
-</div>
+>⚠️ Las promociones por medio de pago y número de cuotas no se aplican a pedidos pagados con dos tarjetas o tarjetas de regalo.
 
 - **utm_source:** el descuento se concederá si la navegación utiliza un parámetro utm_source correspondiente a cualquiera de los valores registrados. Es importante resaltar que el cliente solo puede ingresar un **utm_source** en el checkout.
 - **utm_campaign:** el descuento se concederá si la navegación utiliza un parámetro utm_campaign con el valor registrado.
diff --git a/docs/tracks/es/credit-card-payment-flow.md b/docs/tracks/es/credit-card-payment-flow.md
index 31cb99c1d..925ae6f2f 100644
--- a/docs/tracks/es/credit-card-payment-flow.md
+++ b/docs/tracks/es/credit-card-payment-flow.md
@@ -45,7 +45,5 @@ Con la respuesta del banco emisor, se realiza el flujo inverso y el **Gateway de
 
 <br/>
 
-<div class="alert alert-info">
-Es posible incluir el Antifraude en este flujo. En este caso, el antifraude recibe la información del gateway de que el pago fue  preautorizado por el banco emisor. Con la información recibida del gateway, el antifraude envía una respuesta de aprobación o denegación del pago. Si el antifraude no lo aprueba, el pago se cancela. Si el pago es aprobado, el pedido puede continuar su flujo normal.
-</div>
+>ℹ️ Es posible incluir el Antifraude en este flujo. En este caso, el antifraude recibe la información del gateway de que el pago fue  preautorizado por el banco emisor. Con la información recibida del gateway, el antifraude envía una respuesta de aprobación o denegación del pago. Si el antifraude no lo aprueba, el pago se cancela. Si el pago es aprobado, el pedido puede continuar su flujo normal.
 
diff --git a/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md b/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
index f5d9274b5..7598d82eb 100644
--- a/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
+++ b/docs/tracks/es/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
@@ -43,9 +43,7 @@ Ejemplo:
 
 En este caso, al comparar el peso real con el peso cúbico del paquete, la transportadora cobrará por el peso real, porque es mayor que el peso cúbico.
 
-<div class="alert alert-warning">
-Verifique con su transportadora si la unidad de medida está en <strong>gramos</strong>,  que es la unidad utilizada en VTEX.
-</div>
+>⚠️ Verifique con su transportadora si la unidad de medida está en **gramos**,  que es la unidad utilizada en VTEX.
 
 Al realizar el registro de su transportadora, ese es el valor que debe completar  en el campo Factor Cúbico de Peso.
 
diff --git a/docs/tracks/es/customer-identification.md b/docs/tracks/es/customer-identification.md
index 4a3d025f5..d7cc0e645 100644
--- a/docs/tracks/es/customer-identification.md
+++ b/docs/tracks/es/customer-identification.md
@@ -33,6 +33,4 @@ Ingrese uno de estos datos en el campo y haga clic en el botón `Confirmar`.
 
 Alternativamente, si ha habilitado Usuario anónimo, es posible continuar sin identificar al cliente. Para hacer esto, haga clic en `Continuar sin identificación`.
 
-<div class="alert alert-info">
-Aunque es posible atender a los clientes sin identificarlos, siempre recomendamos hacerlo, ya que esto le brinda al vendedor una serie de información contextual que aumenta las posibilidades de conversión.
-</div>
+>ℹ️ Aunque es posible atender a los clientes sin identificarlos, siempre recomendamos hacerlo, ya que esto le brinda al vendedor una serie de información contextual que aumenta las posibilidades de conversión.
diff --git a/docs/tracks/es/customizing-instore.md b/docs/tracks/es/customizing-instore.md
index 2921e4a60..4b9354349 100644
--- a/docs/tracks/es/customizing-instore.md
+++ b/docs/tracks/es/customizing-instore.md
@@ -18,9 +18,7 @@ La experiencia VTEX Sales App es personalizable. Puede aplicar funcionalidades y
 
 Para ello, es necesario editar archivos JavaScript y CSS, tal y como se describe en la guía para desarrolladores[ How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app).
 
-<div class="alert alert-warning">
-<p>La personalización de VTEX Sales App debe ser realizada por personas con experiencia en programación, ya que modificaciones incorrectas en estos archivos pueden provocar errores críticos.</p>
-</div>
+>⚠️ La personalización de VTEX Sales App debe ser realizada por personas con experiencia en programación, ya que modificaciones incorrectas en estos archivos pueden provocar errores críticos.
 
 Vea a continuación las personalizaciones disponibles en VTEX Sales App. Puede hacer clic en el nombre de cada una para acceder a su respectiva guía de implementación.
 
diff --git a/docs/tracks/es/customizing-instores-layout.md b/docs/tracks/es/customizing-instores-layout.md
index d451d885b..7a204db07 100644
--- a/docs/tracks/es/customizing-instores-layout.md
+++ b/docs/tracks/es/customizing-instores-layout.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: personalizando-el-layout-del-instore
 ---
 
-<div class="alert alert-danger">
-Personalizar el layout del inStore, como explicado en este artículo, implica cambiar el archivo CSS <code>checkout-instore-custom.css</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ Personalizar el layout del inStore, como explicado en este artículo, implica cambiar el archivo CSS `checkout-instore-custom.css`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 A través del panel administrativo de VTEX, la tienda tiene acceso al archivo CSS editable que define los estilos del app de inStore. Por lo tanto, es posible personalizar estos estilos.
 
diff --git a/docs/tracks/es/data-protection-roles.md b/docs/tracks/es/data-protection-roles.md
index a901e0d90..81233e837 100644
--- a/docs/tracks/es/data-protection-roles.md
+++ b/docs/tracks/es/data-protection-roles.md
@@ -48,9 +48,7 @@ VTEX no utiliza los datos de los clientes finales para ningún otro fin que no s
 
 El DPA utilizado debe corresponder a la región específica del titular de los datos (cliente de la tienda).
 
-<div class="alert alert-warning">
-  <p>Accede a <a href="https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/">Data Processing Addendum - VTEX</a> para ver el DPA predeterminado de VTEX para cada región.</p>
-</div>
+>⚠️ Accede a [Data Processing Addendum - VTEX](https://vtex.com/co-es/privacy-and-agreements/data-processing-addendum/) para ver el DPA predeterminado de VTEX para cada región.
 
 ## Responsabilidades compartidas
 
diff --git a/docs/tracks/es/define-payment-methods-displayed-on-instore.md b/docs/tracks/es/define-payment-methods-displayed-on-instore.md
index 76863634e..08bb7ffc8 100644
--- a/docs/tracks/es/define-payment-methods-displayed-on-instore.md
+++ b/docs/tracks/es/define-payment-methods-displayed-on-instore.md
@@ -18,6 +18,4 @@ Ahora que la condición de pago ha sido creada, necesitas crear los filtros que
 
 Para ello, los desarrolladores de tu tienda deben personalizar un archivo JavaScript. Para más información, consulta la guía [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/docs/guides/define-payment-methods-displayed-on-vtex-sales-app).
 
-<div class="alert alert-danger">
-<p>Para habilitar los pagos a través de la aplicación VTEX Sales App, como se explica en este artículo, es necesario realizar cambios en un archivo JavaScript. Esta operación debe ser realizada por personas con experiencia en programación. Modificaciones incorrectas en este archivo pueden causar errores críticos.</p>
-</div>
+>❗ Para habilitar los pagos a través de la aplicación VTEX Sales App, como se explica en este artículo, es necesario realizar cambios en un archivo JavaScript. Esta operación debe ser realizada por personas con experiencia en programación. Modificaciones incorrectas en este archivo pueden causar errores críticos.
diff --git a/docs/tracks/es/defining-the-google-shopping-trade-policy.md b/docs/tracks/es/defining-the-google-shopping-trade-policy.md
index 4064e0315..c5c40924a 100644
--- a/docs/tracks/es/defining-the-google-shopping-trade-policy.md
+++ b/docs/tracks/es/defining-the-google-shopping-trade-policy.md
@@ -52,10 +52,6 @@ Para configurar un descuento vinculado a un medio de pago debes considerar la in
 
 Una vez realizados los pasos anteriormente descritos, la activación deberá realizarse a través de la [configuración del conector](https://help.vtex.com/es/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
 
-<div class="alert alert-warning">
-En caso de que haya varios sellers vinculados a un producto de tu tienda, Google Shopping aplicará la regla de anunciar la mejor oferta disponible.
-  </div>
+>⚠️ En caso de que haya varios sellers vinculados a un producto de tu tienda, Google Shopping aplicará la regla de anunciar la mejor oferta disponible.
 
-  <div class="alert alert-danger">
-Para que el descuento se envíe a Google Shopping, cada promoción creada solo puede tener vinculado un medio de pago.
-  </div>
+  >❗ Para que el descuento se envíe a Google Shopping, cada promoción creada solo puede tener vinculado un medio de pago.
diff --git a/docs/tracks/es/detaching-skus-by-specification.md b/docs/tracks/es/detaching-skus-by-specification.md
index 98f52f322..0205b4d3e 100644
--- a/docs/tracks/es/detaching-skus-by-specification.md
+++ b/docs/tracks/es/detaching-skus-by-specification.md
@@ -26,8 +26,7 @@ A continuación, vea un ejemplo de separación de SKUs por color. La sandalia qu
 
 ![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
-<div class="alert alert-info"><p>
-Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.</p></div>
+>ℹ️ Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.
 
 ## Configuración
 Para configurar los atributos que se usarán para separar los SKUs, acceda a nuestro artículo de [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
diff --git a/docs/tracks/es/enable-clustered-payment-conditions.md b/docs/tracks/es/enable-clustered-payment-conditions.md
index 612f25242..810ecac81 100644
--- a/docs/tracks/es/enable-clustered-payment-conditions.md
+++ b/docs/tracks/es/enable-clustered-payment-conditions.md
@@ -22,9 +22,7 @@ El segundo paso es configurar la propia Clustered Payment Conditions en su tiend
 
 ## Habilitar Customer Credit
 
-<div class="alert alert-info">
-Si Customer Credit ya está instalado y configurado en el Admin, diríjase al paso “Habilitar Clustered Payment Conditions”.
-</div>
+>ℹ️ Si Customer Credit ya está instalado y configurado en el Admin, diríjase al paso “Habilitar Clustered Payment Conditions”.
 
 ### 1. Instalación de la aplicación
 
@@ -40,9 +38,7 @@ Hay algunas [configuraciones básicas](https://help.vtex.com/es/tracks/customer-
 
 ## Habilitar Clustered Payment Conditions en la tienda
 
-<div class="alert alert-warning">
-Esta funcionalidad se encuentra actualmente en Beta Cerrada (etapa de prueba) y no está disponible para su instalación en tiendas nuevas.           
-</div>  
+>⚠️ Esta funcionalidad se encuentra actualmente en Beta Cerrada (etapa de prueba) y no está disponible para su instalación en tiendas nuevas.  
 
 Ahora que Customer Credit funciona en su tienda, puede habilitar Clustered Payment Conditions. Para esto, póngase en contacto con el equipo de soporte de VTEX. Abra un [ticket](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM "ticket") y pida que se active la funcionalidad de su tienda.
 
diff --git a/docs/tracks/es/enabling-2-factor-authentication-login.md b/docs/tracks/es/enabling-2-factor-authentication-login.md
index 78c13db36..3a24d2821 100644
--- a/docs/tracks/es/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/es/enabling-2-factor-authentication-login.md
@@ -33,14 +33,9 @@ Hay dos opciones de autenticación:
 
 ![2FA - Select - ES](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
 
-<div class="alert alert-warning">
-Recomendamos el uso de la <a href="#habilitar-o-2fa-por-aplicativo">aplicación de autenticación</a> para que las fallas del servicio de su operador de telefonía no impidan su inicio de sesión. A través de la aplicación, la clave de acceso siempre estará disponible para que la utilice.
+>⚠️ Recomendamos el uso de la [aplicación de autenticación](#habilitar-o-2fa-por-aplicativo) para que las fallas del servicio de su operador de telefonía no impidan su inicio de sesión. A través de la aplicación, la clave de acceso siempre estará disponible para que la utilice.
 
-</div>
-
-<div class="alert alert-info">
-Debido a que algunas empresas restringen el uso de celulares a los operadores de televenta, los usuarios que tienen el <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator" target="_blank"> perfil de acceso de televentas</a> no están obligados a habilitar 2FA cuando inician sesión utilizando el email y la contraseña.
-</div>
+>ℹ️ Debido a que algunas empresas restringen el uso de celulares a los operadores de televenta, los usuarios que tienen el [ perfil de acceso de televentas](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator" target="_blank) no están obligados a habilitar 2FA cuando inician sesión utilizando el email y la contraseña.
 
 ### Habilitar 2FA por aplicación
 
@@ -59,9 +54,7 @@ Para utilizar una clave generada a través de la aplicación de autenticación:
 
 ![2FA - App Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
 
-<div class="alert alert-info">
-Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso <strong> cada 3 días</strong>. Cuando eso suceda, basta con consultar el código en la aplicación.
-</div>
+>ℹ️ Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso ** cada 3 días**. Cuando eso suceda, basta con consultar el código en la aplicación.
 
 ### Habilitar 2FA por SMS
 
@@ -75,9 +68,7 @@ Para utilizar una clave enviada a través de mensaje de texto:
 
 ![2FA - SMS Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
 
-<div class="alert alert-warning">
-No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o <a href="#habilitar-o-2fa-por-aplicativo">habilitar 2FA a través de la aplicación</a>.
-</div>
+>⚠️ No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o [habilitar 2FA a través de la aplicación](#habilitar-o-2fa-por-aplicativo).
 
 ## Modificar la configuración de 2FA
 
diff --git a/docs/tracks/es/enabling-a-sales-rep-code.md b/docs/tracks/es/enabling-a-sales-rep-code.md
index 16afe7087..4ca2a7b68 100644
--- a/docs/tracks/es/enabling-a-sales-rep-code.md
+++ b/docs/tracks/es/enabling-a-sales-rep-code.md
@@ -20,21 +20,15 @@ Por lo tanto, una de las opciones de personalización de inStore es cambiar el c
 
 Una vez que se habilite, esta personalización muestra el campo `Vendor` en la parte superior de la página y añade una etapa al flujo de compra: antes del Envío, el vendedor está obligado a identificar esa venta con su código.
 
-<div class="alert alert-danger">
-<strong>Atención</strong>: en este caso, no es posible finalizar una venta sin completar el campo <code>Vendor</code> con el código del vendedor.
-</div>
+>❗ **Atención**: en este caso, no es posible finalizar una venta sin completar el campo `Vendor` con el código del vendedor.
 
 ## Editando el archivo Javascript
 
 Para habilitar el código del vendedor, se necesita realizar una alteración en el código JavaScript `checkout-custom-inStore.js` que está guardado en el panel administrativo de VTEX.
 
-<div class="alert alert-warning">
-Se <strong>recomienda expresamente</strong> que el responsable de modificar el código sea una persona con <strong>experiencia en programación</strong>. 
-</div>  
+>⚠️ Se **recomienda expresamente** que el responsable de modificar el código sea una persona con **experiencia en programación**.  
 
-<div class="alert alert-info">
-El código del vendedor es habilitado <strong>solo</strong> por JavaScript.
-</div>
+>ℹ️ El código del vendedor es habilitado **solo** por JavaScript.
 
 En primer lugar, realice los ajustes descritos en el artículo [Habilitar campo de observación en la pantalla de pedido](https://help.vtex.com/es/tracks/instore-customizacoes--1z9kBm12oBPyVNDo1ivVc2/8Aj21R8bll0tdrxHWjVOs).
 
@@ -56,9 +50,7 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-No remueva ninguna de las otras propiedades del objeto <code>window.INSTORE_CONFIG</code>. De lo contrario, las otras funcionalidades de su tienda podrían verse afectadas.
-</div>
+>❗ No remueva ninguna de las otras propiedades del objeto `window.INSTORE_CONFIG`. De lo contrario, las otras funcionalidades de su tienda podrían verse afectadas.
 
 Además, recuerde que el anterior código es solo una opción de configuración.  
 
diff --git a/docs/tracks/es/enabling-cart-transfer-between-devices.md b/docs/tracks/es/enabling-cart-transfer-between-devices.md
index 12f212d3b..0ad0b2808 100644
--- a/docs/tracks/es/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/es/enabling-cart-transfer-between-devices.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: habilitar-transferencia-de-carrito-entre-dispositivos
 ---
 
-<div class="alert alert-danger">
-La habilitación de la transferencia de carrito, explicada en este artículo, implica cambiar el archivo JavaScript <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ La habilitación de la transferencia de carrito, explicada en este artículo, implica cambiar el archivo JavaScript `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 La funcionalidad de __Transferencia de Carrito__ de inStore permite que una compra iniciada en un dispositivo se complete en cualquier otro dispositivo presente en el flujo de compra, sin la necesidad de leer otra vez el código de los productos.
 
diff --git a/docs/tracks/es/enabling-order-filter-by-salesperson.md b/docs/tracks/es/enabling-order-filter-by-salesperson.md
index 6a9213cef..debaa4ecc 100644
--- a/docs/tracks/es/enabling-order-filter-by-salesperson.md
+++ b/docs/tracks/es/enabling-order-filter-by-salesperson.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: habilitar-filtro-de-pedidos-por-vendedor
 ---
 
-<div class="alert alert-danger">
-El cambio en la configuración de filtro por vendedor, explicado en este artículo, implica editar el archivo <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ El cambio en la configuración de filtro por vendedor, explicado en este artículo, implica editar el archivo `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 En inStore, es posible ver la lista de todos los pedidos completados en una tienda. Sin embargo, a veces puede ser mejor que el vendedor vea solo los pedidos que ha completado. Para habilitar esta opción, es necesario editar el archivo `checkout-instore-custom.js`.
 
@@ -33,8 +31,6 @@ window.INSTORE_CONFIG = {
 
 Con eso, filtramos los pedidos para mostrar solo los realizados por el vendedor actualmente conectado en la tienda.
 
-<div class="alert alert-danger">
-No elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ No elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
 
 Después de volver a cargar los datos de inStore, al hacer clic en el botón __Restaurar datos__, el vendedor solo verá los pedidos cerrados por él o ella.
diff --git a/docs/tracks/es/enabling-product-recommendations.md b/docs/tracks/es/enabling-product-recommendations.md
index 2c3f6c96a..b99c903d0 100644
--- a/docs/tracks/es/enabling-product-recommendations.md
+++ b/docs/tracks/es/enabling-product-recommendations.md
@@ -54,6 +54,4 @@ window.INSTORE_CONFIG = {
 
 Guarde el archivo con el cambio, luego abra el menú de la aplicación inStore y actualice los datos haciendo clic en el botón __Restaurar datos__. Una vez hecho esto, los vendedores ya no verán recomendaciones de productos.
 
-<div class="alert alert-danger">
-No elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ No elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
diff --git a/docs/tracks/es/enabling-the-remarks-field-in-the-order-screen.md b/docs/tracks/es/enabling-the-remarks-field-in-the-order-screen.md
index 43fc0c9cb..374014aed 100644
--- a/docs/tracks/es/enabling-the-remarks-field-in-the-order-screen.md
+++ b/docs/tracks/es/enabling-the-remarks-field-in-the-order-screen.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: habilitar-campo-de-observacion-en-la-pantalla-de-pedido
 ---
 
-<div class="alert alert-danger">
-La personalización explicada en este artículo implica cambiar el archivo JavaScript <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Los cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ La personalización explicada en este artículo implica cambiar el archivo JavaScript `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Los cambios incorrectos en este archivo pueden causar errores críticos.
 
 El app del inStore permite el uso de un campo de "Comentarios", donde es posible guardar información adicional con respecto a cada pedido.
 
@@ -45,9 +43,7 @@ window.LOCALE_MESSAGES = {
 };
 ```
  
-<div class="alert alert-danger">
-No elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ No elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
                              
 Si es necesario aplicar alguna lógica o máscara de validación a los datos ingresados en este campo, es posible incluir en el archivo `checkout-instore-custom.js` una función que escuche el evento `note.visible`, que se activa cuando el modal se abre, y luego desarrollar su lógica.
 
diff --git a/docs/tracks/es/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md b/docs/tracks/es/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
index 000f68e2a..d53c7b410 100644
--- a/docs/tracks/es/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
+++ b/docs/tracks/es/entenda-como-os-clientes-chegam-ate-o-seu-whatsapp.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/exporting-an-order.md b/docs/tracks/es/exporting-an-order.md
index 5adbbe33f..bfb463547 100644
--- a/docs/tracks/es/exporting-an-order.md
+++ b/docs/tracks/es/exporting-an-order.md
@@ -18,9 +18,7 @@ El proceso de exportación de pedidos se puede realizar a través de la pantalla
 
 La exportación de pedidos genera un informe en formato .csv que contiene una serie de detalles sobre los pedidos de su tienda. Para saber qué información se muestra en el informe exportado, consulte el [tutorial sobre los campos de la plantilla de pedidos](https://help.vtex.com/es/tutorial/planilla-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
 
-<div class="alert alert-info">
-<p>Cuando el número de pedidos solicitados para la exportación es muy elevado, el proceso puede ser lento. Por lo tanto, hay una limitación en el número de pedidos seleccionados. Por el momento, es posible exportar <b>hasta 50 000 pedidos a la vez</b>.</p>
-</div>
+>ℹ️ Cuando el número de pedidos solicitados para la exportación es muy elevado, el proceso puede ser lento. Por lo tanto, hay una limitación en el número de pedidos seleccionados. Por el momento, es posible exportar **hasta 50 000 pedidos a la vez**.
 
 Siga las instrucciones a continuación para generar el informe:
 
diff --git a/docs/tracks/es/extensions-hub-partners.md b/docs/tracks/es/extensions-hub-partners.md
index 5b82db8d7..06d2af891 100644
--- a/docs/tracks/es/extensions-hub-partners.md
+++ b/docs/tracks/es/extensions-hub-partners.md
@@ -14,6 +14,4 @@ trackId: AW7klkYMh557y5IUOgzco
 trackSlugES: hub-de-extensiones
 ---
 
-<div class="alert alert-warning">
-Contenido aún no disponible.
-</div>
+>⚠️ Contenido aún no disponible.
diff --git a/docs/tracks/es/facebook-business-extension.md b/docs/tracks/es/facebook-business-extension.md
index 6d3467215..eac705f06 100644
--- a/docs/tracks/es/facebook-business-extension.md
+++ b/docs/tracks/es/facebook-business-extension.md
@@ -30,9 +30,7 @@ La aplicación _Facebook Business Extension y Conversions API_ es totalmente com
 
 Obtenga más información sobre la configuración requerida para cada uno en nuestra guía [Facebook Business Extension](https://developers.vtex.com/docs/guides/vtex-facebook-fbe#compatibility) en el Developer Portal.
 
-<div class="alert alert-warning">
-En VTEX, hay una <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">guía para la integración con Facebook </a>. Sin embargo, la integración con la aplicación <i>Facebook Business Extension y Conversions API</i> debería ser tu elección por defecto, ya que FBE es la solución más completa de Facebook. Independientemente de que tengas configurada la otra integración, debes proceder normalmente con la configuración de esta integración.
-</div>
+>⚠️ En VTEX, hay una <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">guía para la integración con Facebook </a>. Sin embargo, la integración con la aplicación <i>Facebook Business Extension y Conversions API</i> debería ser tu elección por defecto, ya que FBE es la solución más completa de Facebook. Independientemente de que tengas configurada la otra integración, debes proceder normalmente con la configuración de esta integración.
 
 ## Píxel de Facebook
 
diff --git a/docs/tracks/es/filters.md b/docs/tracks/es/filters.md
index dac085270..5cb8692ad 100644
--- a/docs/tracks/es/filters.md
+++ b/docs/tracks/es/filters.md
@@ -20,17 +20,13 @@ Cuando un cliente selecciona un filtro (precio, color, tamaño y marca), esta in
 
 **VTEX Intelligent Search** utiliza el contexto de los productos que se muestran como resultados de la búsqueda para saber exactamente qué filtros deben mostrarse al cliente, de acuerdo con la configuración del catálogo.
 
-<div class="alert alert-info">
-  <p>El orden de los filtros de marca, departamento, categoría y subcategoría se determina por la cantidad de productos registrados en cada uno de los filtros.</p>
-</div>
+>ℹ️ El orden de los filtros de marca, departamento, categoría y subcategoría se determina por la cantidad de productos registrados en cada uno de los filtros.
 
 Ejemplo: tenga en cuenta que el filtro *Tamaño* está registrado en el catálogo de una tienda y que solo el producto *zapatilla* tiene la especificación *Tamaño* rellenada. En una búsqueda por el término *zapatilla*, *Tamaño* aparecerá como un filtro. En la búsqueda de cualquier otro término, como *gorra*, esta especificación no se mostrará como un filtro.
 
 El resultado de búsqueda no mostrará una especificación si solo existe como filtro o si el cliente accede a ella a través del menú de la tienda. Ejemplo: si el cliente selecciona el filtro Electrodomésticos directamente en el menú, no se mostrará Departamento como filtro lateral.
 
-<div class="alert alert-info">
-  <p>Si el resultado de la búsqueda devuelve más de 30 mil productos, se omitirán algunos valores de filtros, ya que solo se considerarán las especificaciones de una parte de estos productos.</p>
-</div>
+>ℹ️ Si el resultado de la búsqueda devuelve más de 30 mil productos, se omitirán algunos valores de filtros, ya que solo se considerarán las especificaciones de una parte de estos productos.
 
 La funcionalidad Filtros tiene las siguientes funciones:
 
@@ -45,6 +41,4 @@ La funcionalidad Filtros tiene las siguientes funciones:
 
 Consulte la guía [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) en el Developer Portal para obtener más detalles técnicos sobre el uso de filtros.
 
-<div class="alert alert-warning">
-  <p>Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.</p>
-</div>
+>⚠️ Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.
diff --git a/docs/tracks/es/forcing-stock-availability.md b/docs/tracks/es/forcing-stock-availability.md
index bcd4391ad..d5c07ce2d 100644
--- a/docs/tracks/es/forcing-stock-availability.md
+++ b/docs/tracks/es/forcing-stock-availability.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: forzar-disponibilidad-de-stock
 ---
 
-<div class="alert alert-danger">
-La configuración para forzar la disponibilidad de stock, explicada en este artículo, implica cambiar el archivo <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ La configuración para forzar la disponibilidad de stock, explicada en este artículo, implica cambiar el archivo `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 Por defecto, si un SKU no tiene stock en el catálogo de la tienda, no es posible vender ese SKU con inStore.
 
@@ -34,6 +32,4 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-No elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ No elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
diff --git a/docs/tracks/es/frontend-implementation.md b/docs/tracks/es/frontend-implementation.md
index b5dd98e38..586fc5346 100644
--- a/docs/tracks/es/frontend-implementation.md
+++ b/docs/tracks/es/frontend-implementation.md
@@ -47,9 +47,7 @@ La <a href="#fases-de-desarrollo">fase de desarrollo</a> puede llevarse a cabo s
 
 VTEX cuenta con tres diferentes tecnologías para el desarrollo del storefront: [FastStore](#faststore), [Store Framework](#store-framework) y [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). CMS Portal Legado fue la primera tecnología de VTEX para la construcción de storefronts. Este sistema, basado en HTML, CSS y JavaScript, centraliza todo el proceso de desarrollo y edición de código a través del Admin VTEX.
 
-<div class="alert alert-warning">
-Aunque algunas tiendas aún lo utilizan, <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> es una tecnología heredada y ya no está disponible para tiendas que inician su trayectoria con VTEX.
-</div>
+>⚠️ Aunque algunas tiendas aún lo utilizan, [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) es una tecnología heredada y ya no está disponible para tiendas que inician su trayectoria con VTEX.
 
 Las siguientes secciones tratan sobre las principales características y funcionalidades de FastStore y Store Framework.
 
diff --git a/docs/tracks/es/get-visitors-from-my-website-and-social-networks-to-whatsapp.md b/docs/tracks/es/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
index a457ec653..e4c2b3f23 100644
--- a/docs/tracks/es/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
+++ b/docs/tracks/es/get-visitors-from-my-website-and-social-networks-to-whatsapp.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/getting-started-with-logistics.md b/docs/tracks/es/getting-started-with-logistics.md
index 9dd93b2ea..7fdf0494f 100644
--- a/docs/tracks/es/getting-started-with-logistics.md
+++ b/docs/tracks/es/getting-started-with-logistics.md
@@ -19,16 +19,16 @@ El módulo **Inventario y envío** es responsable de la configuración logístic
 
 Este artículo es el primero de una serie de primeros pasos para las configuraciones logísticas. La pista contiene información básica para ayudar a entender la logística en las tiendas VTEX y cómo se estructuran las configuraciones en la plataforma.
 
-<div class="alert alert-danger">
-Antes de configurar la logística de tu tienda, configura lo siguiente:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/es/tutorial/crear-una-politica-comercial--563tbcL0TYKEKeOY4IAgAE">Política comercial</li></a>
-<li><a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR">Catálogo</a></li>
-<li><a href="https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu">Precios</a></li>
-</ol>
-</body>
-</div>
+>❗ Antes de configurar la logística de tu tienda, configura lo siguiente:
+> <body>
+>
+> [Política comercial](https://help.vtex.com/es/tutorial/crear-una-politica-comercial--563tbcL0TYKEKeOY4IAgAE)
+>
+> [Catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR)
+>
+> [Precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)
+>
+> </body>
 
 La pista reúne los artículos:
 
diff --git a/docs/tracks/es/go-live-process.md b/docs/tracks/es/go-live-process.md
index 50d061518..344afef86 100644
--- a/docs/tracks/es/go-live-process.md
+++ b/docs/tracks/es/go-live-process.md
@@ -29,9 +29,7 @@ Antes de realizar el go live de tu tienda, es importante garantizar que hayas co
 
 Copia esta [Lista de verificación de tienda](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f254ea28c42f4fe323bb5ad29fd0da36/Lista_verificacion_tienda.xlsx) y comprueba, para cada ítem, si realizaste la configuración de acuerdo con el funcionamiento deseado de la tienda.
 
-<div class="alert alert-warning">
-La lista de verificación que se presenta aquí muestra las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. Tu equipo debe definir qué funcionalidades implementará en la tienda y cómo se deben configurar para crear la experiencia de tienda deseada. Esto significa que la lista no necesariamente incluye todas las funcionalidades que tu tienda utiliza. Sin embargo, es importante verificar todos los aspectos del funcionamiento de tu tienda aunque no estén en la lista sugerida.
-</div>
+>⚠️ La lista de verificación que se presenta aquí muestra las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. Tu equipo debe definir qué funcionalidades implementará en la tienda y cómo se deben configurar para crear la experiencia de tienda deseada. Esto significa que la lista no necesariamente incluye todas las funcionalidades que tu tienda utiliza. Sin embargo, es importante verificar todos los aspectos del funcionamiento de tu tienda aunque no estén en la lista sugerida.
 
 ## Guía paso a paso
 
diff --git a/docs/tracks/es/go-live.md b/docs/tracks/es/go-live.md
index 98d65aa61..1b67c6324 100644
--- a/docs/tracks/es/go-live.md
+++ b/docs/tracks/es/go-live.md
@@ -25,9 +25,7 @@ En la zona de DNS de tu dominio, debes crear una entrada de tipo CNAME en el sub
 
 Ten en cuenta que el `{dominio}` indicado anteriormente debe ser el mismo que [registraste en VTEX](https://help.vtex.com/es/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#registrar-el-dominio-en-vtex).
 
-<div class="alert alert-warning">
-Si utilizas Cloudflare como zona de DNS, puede que tengas que desactivar el proxy de DNS y, por lo tanto, desactivar los servicios de CDN y WAF de Cloudflare. Puedes ver más información en el artículo <a href="https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">Cómo desactivar el proxy de Cloudflare</a>.
-</div>
+>⚠️ Si utilizas Cloudflare como zona de DNS, puede que tengas que desactivar el proxy de DNS y, por lo tanto, desactivar los servicios de CDN y WAF de Cloudflare. Puedes ver más información en el artículo [Cómo desactivar el proxy de Cloudflare](https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 Ejemplos:
 
@@ -58,9 +56,7 @@ Host de tienda: www.tienda.miempresa.com.br
 
 Tenga en cuenta que el subdominio (`store`, `www`, `www.store` y otros) y el dominio de nivel superior (`.com`, `.com.br`, `.com.ar` y otros) forman parte del `{hostname}` y deben estar en el destino CNAME.
 
-<div class="alert alert-danger">
-No puede haber ningún apuntamiento de tipo A coexistiendo con el apuntamiento CNAME descrito anteriormente. Esta coexistencia puede causar problemas en su _go live_. Mantenga solo el apuntamiento CNAME descrito anteriormente.
-</div>
+>❗ No puede haber ningún apuntamiento de tipo A coexistiendo con el apuntamiento CNAME descrito anteriormente. Esta coexistencia puede causar problemas en su _go live_. Mantenga solo el apuntamiento CNAME descrito anteriormente.
 
 Los apuntamientos de DNS tardan entre 24 y 48 horas en propagarse completamente, lo que significa que la dirección configurada puede no ser accesible a todo el mundo inmediatamente después de la configuración. Además, para que la tienda esté disponible se requiere [notificar el apuntamiento](#notificar-el-apuntamiento).
 
diff --git a/docs/tracks/es/google-pay.md b/docs/tracks/es/google-pay.md
index daa330e37..46003b281 100644
--- a/docs/tracks/es/google-pay.md
+++ b/docs/tracks/es/google-pay.md
@@ -18,9 +18,7 @@ Google Pay™ es un servicio de pagos digitales que permite a los usuarios no co
 
 Los términos de la API de Google Pay se aplican siempre que el administrador de la tienda ofrezca Google Pay como medio de pago. Para leer los términos, accede a [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
 
-<div class="alert alert-warning">
-<p>Google Pay no está disponible para Checkout V5 o versiones anteriores de Checkout.h</p>
-</div>
+>⚠️ Google Pay no está disponible para Checkout V5 o versiones anteriores de Checkout.h
 
 ## Activar Google Pay
 
@@ -50,9 +48,7 @@ Para utilizar Google Pay deben cumplirse los siguientes requisitos:
   <p>En las tiendas que tengan el flujo de autenticación <a href="https://help.vtex.com/es/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado y admitido por el adquirente, el pago con Google Pay seguirá el flujo nativo de la tarjeta y también utilizará 3DS. Para más información sobre este tema, accede a <a href="https://help.vtex.com/es/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar flujo de autenticación 3DS 2</a>.</p>
 </div>
 
-<div class="alert alert-info">
-<p>También puedes configurar Google Pay para que se procese con Adyen o Stripe. Para hacer esto, acceda a la pantalla <b>Condiciones de pago</b> en Admin, haga clic en <b>Google Pay</b> y seleccione la opción deseada.</p>
-</div>
+>ℹ️ También puedes configurar Google Pay para que se procese con Adyen o Stripe. Para hacer esto, acceda a la pantalla **Condiciones de pago** en Admin, haga clic en **Google Pay** y seleccione la opción deseada.
 
 ## Consultar transacciones finalizadas con Google Pay
 
@@ -64,9 +60,7 @@ Después de acceder a la transacción deseada, haga clic en "+ Información" par
 
 ![Google Pay Transaction_2](https://images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/394481aab2e3d50703ab836080f1e1c9/Google_Pay_Transaction2_ES.png)
 
-<div class="alert alert-warning">
-  <p>También es posible identificar las transacciones realizadas con Google Pay a través de la página <b>Todos los pedidos</b> en Admin. Sólo necesitas seleccionar el periodo de búsqueda deseado, <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">exportar los pedidos</a> en un informe en formato . csv y localizar la información de Google Pay en el campo "payment origin".</p>
-</div>
+>⚠️ También es posible identificar las transacciones realizadas con Google Pay a través de la página **Todos los pedidos** en Admin. Sólo necesitas seleccionar el periodo de búsqueda deseado, [exportar los pedidos](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu) en un informe en formato . csv y localizar la información de Google Pay en el campo "payment origin".
 
 ## Agregar información de Google Pay en la plantilla de compra
 
diff --git a/docs/tracks/es/google-shopping-ads-install.md b/docs/tracks/es/google-shopping-ads-install.md
index 470662bf6..52c54cdb2 100644
--- a/docs/tracks/es/google-shopping-ads-install.md
+++ b/docs/tracks/es/google-shopping-ads-install.md
@@ -14,9 +14,7 @@ trackId: 47kz5PRQPK0IEaqGqiIuA
 trackSlugES: como-hacer-campanas-a-traves-de-google-ads
 ---
 
-<div class="alert alert-warning">
-Actualmente, Google Shopping Ads está disponible <strong>solamente para tiendas de Brasil.</strong>
-</div>
+>⚠️ Actualmente, Google Shopping Ads está disponible **solamente para tiendas de Brasil.**
 
 El primer paso para utilizar la app es instalarla. Siga el paso a paso abajo:
 
diff --git a/docs/tracks/es/google-shopping-ads-set-up.md b/docs/tracks/es/google-shopping-ads-set-up.md
index 1750d0ba4..df43f4a60 100644
--- a/docs/tracks/es/google-shopping-ads-set-up.md
+++ b/docs/tracks/es/google-shopping-ads-set-up.md
@@ -26,9 +26,7 @@ En este paso, se debe configurar qué tienda utilizará el app y para cuál URL
 1. En la opción `Tienda`, seleccione el sub-account que deberá utilizarse para el app;
 2. En la opción `URL`, seleccione la URL correspondiente al sitio web de la cuenta que haya elegido en el paso anterior.
 
-<div class="alert alert-warning">
-<strong>OBS:</ strong> asegúrese de que la URL elegida es la correcta, ya que las opciones mostrarán cualquier URL que esté registrada en <a href="https://help.vtex.com/es/tutorial/configurando-dominios-no-license-manager?locale=es">sus dominios</a>. <strong>Generalmente la URL usada es que la tiene WWW</strong>.
-</div>
+>⚠️ **OBS:</ strong> asegúrese de que la URL elegida es la correcta, ya que las opciones mostrarán cualquier URL que esté registrada en [sus dominios](https://help.vtex.com/es/tutorial/configurando-dominios-no-license-manager?locale=es). <strong>Generalmente la URL usada es que la tiene WWW**.
 
 ## Definiendo la cuenta en Google Merchant Center
 
@@ -42,9 +40,7 @@ Al seleccionar __"Crear nueva"__, es muy importante enseguida [acceder al GMC](h
 
 - __Asociar existente:__ el app utilizará la cuenta que ya posee en el GMC. Al  momento de iniciar sesión, debe utilizar exactamente el mismo correo electrónico que utiliza en el GMC que desea asociar.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> la URL configurada en el GMC debe ser <strong>exactamente la misma</strong> que fue elegida anteriormente. Inclusive, tomando en cuenta el protocolo (http o https).
-</div>
+>⚠️ **OBS:** la URL configurada en el GMC debe ser **exactamente la misma** que fue elegida anteriormente. Inclusive, tomando en cuenta el protocolo (http o https).
 
 Al seleccionar __"Asociar a un GMC existente"__, luego será necesario definir si la integración de productos con Google se hará a través de VTEX o a través de alguna sincronización externa que usted ya realice.
 
@@ -82,8 +78,6 @@ Aquí VTEX Shopping Ads crea una nueva cuenta en Google Ads. Al seleccionar esta
 
 En ambos casos, después que el usuario seleccione una opción que se adapte mejor a la realidad de su negocio, VTEX Shopping Ads lo dirigirá a una página de *loading* para completar el proceso de configuración.
 
-<div class="alert alert-danger">
-El usuario no puede salir de la página de <em>loading</em> hasta que se completen todas las configuraciones. De lo contrario, la integración no se realizará.
-</div>
+>❗ El usuario no puede salir de la página de *loading* hasta que se completen todas las configuraciones. De lo contrario, la integración no se realizará.
 
 *__¡Listo!__ Después que VTEX Shopping Ads termine este loading, puede comenzar a usarlo y crear una campaña. ¡Vea en el siguiente paso!*
diff --git a/docs/tracks/es/google-shopping-marketplace.md b/docs/tracks/es/google-shopping-marketplace.md
index 81d2ea1e1..82b7d370d 100644
--- a/docs/tracks/es/google-shopping-marketplace.md
+++ b/docs/tracks/es/google-shopping-marketplace.md
@@ -22,9 +22,7 @@ A través de Google Shopping, puede mostrar al consumidor algunos de los atribut
 
 El conector de Google Shopping de la plataforma VTEX le permite hacer uso de este servicio de manera sencilla y eficiente. Solo tiene que completar los pasos de configuración descritos a continuación.
 
-<div class="alert alert-info">
-Para que la integración funcione correctamente, familiarícese con las <a href="https://support.google.com/google-ads/answer/6149970?hl=es-419">Políticas de anuncios de Shopping</a> y conozca cuáles son las condiciones requeridas por Google.
-</div>
+>ℹ️ Para que la integración funcione correctamente, familiarícese con las [Políticas de anuncios de Shopping](https://support.google.com/google-ads/answer/6149970?hl=es-419) y conozca cuáles son las condiciones requeridas por Google.
 
 | **SEPA MÁS** |
 | ---------- |
diff --git a/docs/tracks/es/how-clustered-conditions-work.md b/docs/tracks/es/how-clustered-conditions-work.md
index ff903a858..0363a8c6f 100644
--- a/docs/tracks/es/how-clustered-conditions-work.md
+++ b/docs/tracks/es/how-clustered-conditions-work.md
@@ -20,9 +20,7 @@ Estas condiciones, a su vez, se basan en los datos que el Master Data almacena s
 
 De esta manera, las reglas de plazo y de pago en cuotas se aplicarán al consumidor o los consumidores que se ajusten a la condición o las condiciones.
 
-<div class="alert alert-danger">
-<strong>Atención</strong>: solo se permite crear cinco clústeres de clientes por condición de pago.
-</div>
+>❗ **Atención**: solo se permite crear cinco clústeres de clientes por condición de pago.
 
 Para configurarlas, escoja una propiedad y, luego, seleccione los parámetros para crear un clúster.
 
diff --git a/docs/tracks/es/how-does-vtex-intelligent-search-work.md b/docs/tracks/es/how-does-vtex-intelligent-search-work.md
index 0f7396f1a..875bb5344 100644
--- a/docs/tracks/es/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/es/how-does-vtex-intelligent-search-work.md
@@ -88,9 +88,7 @@ Ejemplo: se configuró que la especificación “color” se puede buscar y el p
 
 Se puede encontrar un producto realizando una búsqueda por caracteres especiales (`-` y `/`).
 
-<div class="alert alert-warning">
-	<p>La selección de los campos de búsqueda afecta las posibilidades de las <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">reglas de merchandising</a>, ya que solo se pueden utilizar los campos que permiten búsquedas para configurar reglas. Por ejemplo, al definir solo el campo <code>SKUID</code> para búsquedas, no se podrá promover un <code>ProductID</code> o un <code>ProductRefID</code> utilizando reglas de merchandising.</p>
-</div>
+>⚠️ La selección de los campos de búsqueda afecta las posibilidades de las [reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), ya que solo se pueden utilizar los campos que permiten búsquedas para configurar reglas. Por ejemplo, al definir solo el campo `SKUID` para búsquedas, no se podrá promover un `ProductID` o un `ProductRefID` utilizando reglas de merchandising.
 
 ### Definición y orden de los campos de filtro
 
@@ -104,9 +102,7 @@ Ejemplo: un administrador de la tienda configuró que el criterio “promoción
 
 Para obtener más información sobre cómo personalizar el orden de los resultados de acuerdo con las necesidades de tu tienda, consulta el artículo [Configuración de relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
 
-<div class="alert alert-info">
-	<p>Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Si utilizas el comando <code>map=productClusterIds</code>, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con su propio criterio de relevancia. Si eliges utilizar <code>productClusterNames</code>, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search.</p>
-</div>
+>ℹ️ Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Si utilizas el comando `map=productClusterIds`, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con su propio criterio de relevancia. Si eliges utilizar `productClusterNames`, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search.
 
 ## Formas alternativas de búsqueda
 
diff --git a/docs/tracks/es/how-the-payments-module-works.md b/docs/tracks/es/how-the-payments-module-works.md
index 1010e5493..8933278dc 100644
--- a/docs/tracks/es/how-the-payments-module-works.md
+++ b/docs/tracks/es/how-the-payments-module-works.md
@@ -18,9 +18,7 @@ El módulo de **Pagos** es el sistema responsable en VTEX de gestionar todas las
 
 Antes de explorar las funcionalidades dentro de *Pagos* en el Admin de VTEX, vamos a aclarar algunos conceptos importantes que están relacionados con el flujo de pago de un pedido. Este proceso es realizado por algunos actores dentro del sistema financiero brasileño, que componen la arquitectura del módulo de Pagos.
 
-<div class="alert alert-info">
-Es importante recordar que cada tienda tiene sus particularidades y su propio funcionamiento, lo que influye en la forma de construir el módulo de Pagos de su negocio. Para configurar su flujo financiero, es esencial, por lo tanto, tener en mente las necesidades y los propósitos reales del administrador de la tienda y del proyecto deseado.
-</div>
+>ℹ️ Es importante recordar que cada tienda tiene sus particularidades y su propio funcionamiento, lo que influye en la forma de construir el módulo de Pagos de su negocio. Para configurar su flujo financiero, es esencial, por lo tanto, tener en mente las necesidades y los propósitos reales del administrador de la tienda y del proyecto deseado.
 
 ## Gateway 
 
diff --git a/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
index 50b4c0492..178b0304b 100644
--- a/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/es/how-to-configure-a-device-for-printout-the-order.md
@@ -40,9 +40,7 @@ configureDeviceEnabled: true,
       }
 }``
 
-<div class="alert alert-info">
-  <strong>NOTA</strong>: Existe una opción para imprimir de forma automática el resumen del pedido, tan pronto sea completado el pedido. La configuración es muy sencilla, basta agregar la propiedad <strong><i>printPageAutomatically</i></strong> con el valor <strong><i>true</i></strong> dentro del objeto <strong><i>printingConfig</i></strong>.
-   </div>
+>ℹ️ **NOTA**: Existe una opción para imprimir de forma automática el resumen del pedido, tan pronto sea completado el pedido. La configuración es muy sencilla, basta agregar la propiedad **<i>printPageAutomatically</i>** con el valor **<i>true</i>** dentro del objeto **<i>printingConfig</i>**.
 
 No elimine ninguna de las otras propiedades presentes en este objeto, pero el resultado debería ser algo como:
 
@@ -56,9 +54,7 @@ printPageAutomatically: true
 
 ## Configurar dispositivo de impresora en inStore
 
-<div class="alert alert-warning">
-  <strong>IMPORTANTE</strong>: Para la configuración de la impresora en inStore, es necesario tener <strong><i>AppKey</i></strong> y <strong><i>AppToken</i></strong> con permisos de al menos un perfil como <i>“Vendedor inStore (inStore Sales Person)”</i>. Vale aclarar que puede ser utilizado un perfil de <i>“Propietario (administrador super)”</i>.
-  </div>
+>⚠️ **IMPORTANTE**: Para la configuración de la impresora en inStore, es necesario tener **<i>AppKey</i>** y **<i>AppToken</i>** con permisos de al menos un perfil como <i>“Vendedor inStore (inStore Sales Person)”</i>. Vale aclarar que puede ser utilizado un perfil de <i>“Propietario (administrador super)”</i>.
 
   1. Conecte la impresora al equipo donde se encuentre instalado inStore (para descargar inStore, acceda a [http://instore.vtex.com/download]). Recordando que debe ser una computadora con sistema operativo Windows (Windows 7 o superior son compatibles).
   2. Abra la aplicación inStore y entre a la tienda donde desea configurar la impresora.
diff --git a/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
index 2c7967eb0..79ad65dfd 100644
--- a/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
@@ -33,9 +33,7 @@ El __preview__ renderizado por este código se muestra en el box justo debajo. P
 
 El campo __JSON Data__ muestra un *ejemplo* de objeto JSON que contiene información sobre el asunto del correo electrónico. Las llaves de este objeto se pueden utilizar como variables en el código HTML del template. Aprenderemos cómo hacer esto en el próximo artículo.
 
-<div class="alert alert-warning">
-Atención: para personalizar el layout del correo electrónico, debe ingresar el <strong>código CSS inline</strong>. <u>No</u> ingrese el CSS en el head del template, ya que los correos electrónicos no lidian bien con eso.
-</div>
+>⚠️ Atención: para personalizar el layout del correo electrónico, debe ingresar el **código CSS inline**. <u>No</u> ingrese el CSS en el head del template, ya que los correos electrónicos no lidian bien con eso.
 
 Al final, haga clic en el botón __Guardar__.
 
diff --git a/docs/tracks/es/how-to-customize-the-observation-field.md b/docs/tracks/es/how-to-customize-the-observation-field.md
index aabd849ac..86e9d0b84 100644
--- a/docs/tracks/es/how-to-customize-the-observation-field.md
+++ b/docs/tracks/es/how-to-customize-the-observation-field.md
@@ -32,10 +32,8 @@ window.LOCALE_MESSAGES = {
   }
 };
 ```
-<div class="alert alert-danger">
-No quite ninguna de las otras propiedades presentes en el objeto
-<code>window.INSTORE_CONFIG</code>, para evitar que se rompan otras funcionalidades.
-</div>
+>❗ No quite ninguna de las otras propiedades presentes en el objeto
+> `window.INSTORE_CONFIG`, para evitar que se rompan otras funcionalidades.
 
 Si fuera necesario aplicar alguna lógica de validación o máscara a los datos ingresados en este campo, puede incluir en el archivo `checkout-instore-custom.js` una función que escuche el evento `note.visible` que se dispara cuando se abre la ventana modal y luego desarrollar su lógica.
 
diff --git a/docs/tracks/es/how-to-get-started.md b/docs/tracks/es/how-to-get-started.md
index 38ea2875f..e7aca6a59 100644
--- a/docs/tracks/es/how-to-get-started.md
+++ b/docs/tracks/es/how-to-get-started.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/including-order-variables-in-email-template.md b/docs/tracks/es/including-order-variables-in-email-template.md
index 88578d278..d6b34f839 100644
--- a/docs/tracks/es/including-order-variables-in-email-template.md
+++ b/docs/tracks/es/including-order-variables-in-email-template.md
@@ -22,9 +22,7 @@ Estas variables son propiedades del JSON que constan en el campo __JSON Data__ y
 
 ### Ejemplo
 
-<div class="alert alert-warning">
-Los ejemplos de JSON Data apenas aparecerán en los templates cuando complete la acción deseada en su tienda. Si no ha realizado la transacción de un pedido, una recurrencia o cualquier otra acción, el JSON Data aparecerá en blanco.
-</div>
+>⚠️ Los ejemplos de JSON Data apenas aparecerán en los templates cuando complete la acción deseada en su tienda. Si no ha realizado la transacción de un pedido, una recurrencia o cualquier otra acción, el JSON Data aparecerá en blanco.
 
 Supongamos que desea ingresar el nombre de la transportadora en el correo electrónico de pedido enviado.
 
diff --git a/docs/tracks/es/initial-setup.md b/docs/tracks/es/initial-setup.md
index 6f6ec7823..7cfd105c6 100644
--- a/docs/tracks/es/initial-setup.md
+++ b/docs/tracks/es/initial-setup.md
@@ -20,17 +20,14 @@ Antes de comenzar a desarrollar, asegúrese de que se han cumplido los pasos sig
 
 Es necesario tener npm o yarn instalado en su máquina. Ambos son gestores de paquetes. Y uno de los dos es necesario para instalar la CLI de VTEX IO.
 
-<div class="alert alert-info">
-Si no está acostumbrado a trabajar con gestores de paquetes, entienda más sobre estas herramientas:<br>
-<ul>
-  <li>
-    <a href="https://www.npmjs.com/">npm</a>
-  </li>
-  <li>
-    <a href="https://yarnpkg.com/">yarn</a>
-  </li>
-</ul>
-</div>
+>ℹ️ Si no está acostumbrado a trabajar con gestores de paquetes, entienda más sobre estas herramientas:
+>
+> 
+>
+> * [npm](https://www.npmjs.com/)
+>
+> * [yarn](https://yarnpkg.com/)
+> 
 
 ## Instalar la CLI de VTEX IO
 
diff --git a/docs/tracks/es/instore-basic-settings.md b/docs/tracks/es/instore-basic-settings.md
index c2b2b7964..f4eff7ebf 100644
--- a/docs/tracks/es/instore-basic-settings.md
+++ b/docs/tracks/es/instore-basic-settings.md
@@ -16,15 +16,11 @@ trackSlugES: instore-primeros-pasos-y-configuracion
 
 VTEX Sales App es uno de los principales productos de VTEX para las operaciones de [comercio unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv). Es una aplicación que permite a tu tienda ofrecer una verdadera experiencia <i>omnichannel</i>, integrando perfectamente tus canales <i>online</i> y físicos y poniendo a tus clientes en el centro del negocio.
 
-<div class="alert alert-info">
-<p>Comprueba que tu tienda cumple todos los <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">requisitos para utilizar VTEX Sales App</a> antes de empezar a configurarla.</p>
-</div>
+>ℹ️ Comprueba que tu tienda cumple todos los [requisitos para utilizar VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u) antes de empezar a configurarla.
 
 Para utilizar VTEX Sales App, debes seguir los pasos descritos a continuación en tu cuenta principal.
 
-<div class="alert alert-warning">
-<p> No es necesario instalar o configurar VTEX Sales App en las cuentas franquicia que representan tiendas físicas. Solo debes realizar el procedimiento descrito en este artículo en la cuenta principal de la marca.</p>
-</div>
+>⚠️ No es necesario instalar o configurar VTEX Sales App en las cuentas franquicia que representan tiendas físicas. Solo debes realizar el procedimiento descrito en este artículo en la cuenta principal de la marca.
 
 ## Instalar VTEX Sales App
 
@@ -68,9 +64,7 @@ Si decides `Saltar este paso`, se creará una tienda ficticia con fines de prueb
 
 Es necesario registrar un email y un nombre que se utilizarán como credenciales de inicio de sesión del vendedor. Haz clic en `Confirmar`.
 
-<div class="alert alert-warning">
-<p>El email registrado en esta página <strong>no</strong> puede ser un email ya en uso en el Admin de la plataforma VTEX. Utiliza los emails de vendedores que no tienen acceso al Admin.</p>
-</div>
+>⚠️ El email registrado en esta página **no** puede ser un email ya en uso en el Admin de la plataforma VTEX. Utiliza los emails de vendedores que no tienen acceso al Admin.
 
 En esta etapa, debes registrar solo a uno de tus vendedores. Después de realizar la configuración básica, puedes [añadir otros vendedores](https://help.vtex.com/pt/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/5PSjRstg7UU4lOm0s8aqKN).
 
diff --git a/docs/tracks/es/instore-customizations.md b/docs/tracks/es/instore-customizations.md
index 4c15746b3..e94ccd35a 100644
--- a/docs/tracks/es/instore-customizations.md
+++ b/docs/tracks/es/instore-customizations.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: instore-personalizaciones
 ---
 
-<div class="alert alert-danger">
-La mayoría de las personalizaciones de inStore implican cambiar el archivo JavaScript <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ La mayoría de las personalizaciones de inStore implican cambiar el archivo JavaScript `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 ## Acceso al archivo de personalización del inStore
 
@@ -50,9 +48,7 @@ Para realizar cualquier cambio, simplemente agregue o modifique las líneas de c
 
 ![20. inStore Customizations - 3 - ES.png?h=250](https://images.ctfassets.net/alneenqid6w5/7xWS4qln2lhLN1CgM9VwOy/69495b399f32730531e0b8eb553d6d94/20._inStore_Customizations_-_3_-_ES.png_h_250)
 
-<div class="alert alert-warning">
-Siga siempre las instrucciones de personalización en esta documentación y realice solo los cambios como se indica aquí.
-</div>
+>⚠️ Siga siempre las instrucciones de personalización en esta documentación y realice solo los cambios como se indica aquí.
 
 ## Personalizaciones en la tienda
 
diff --git a/docs/tracks/es/instore.md b/docs/tracks/es/instore.md
index d723dff92..58e240017 100644
--- a/docs/tracks/es/instore.md
+++ b/docs/tracks/es/instore.md
@@ -52,9 +52,7 @@ Ingrese uno de estos datos en el campo y haga clic en el botón __Confirmar__.
 
 Alternativamente, si ha habilitado Usuario anónimo, es posible continuar sin identificar al cliente. Para hacer esto, haga clic en __Continuar sin identificación__.
 
-<div class="alert alert-info">
-Aunque es posible atender a los clientes sin identificarlos, siempre recomendamos hacerlo, ya que esto le brinda al vendedor una serie de información contextual que aumenta las posibilidades de conversión.
-</div>
+>ℹ️ Aunque es posible atender a los clientes sin identificarlos, siempre recomendamos hacerlo, ya que esto le brinda al vendedor una serie de información contextual que aumenta las posibilidades de conversión.
 
 ## 3. Búsqueda omnicanal
 
diff --git a/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
index 1f338c15f..2f31febb4 100644
--- a/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/es/integrating-instore-to-a-new-payment-acquirer.md
@@ -36,9 +36,7 @@ Si es necesario, inStore puede enviar información adicional. Ejemplo con el sub
 - `administrativePassword`: string - contraseña predeterminada, por ejemplo, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-Para crear cualquier configuración extra, usted debe enviar al equipo de inStore (instoredevs@vtex.com) los extras que la aplicación necesita para completar la transacción. Así, crearemos un formulario en el módulo de Pagos para que el cliente pueda configurar su adquirente.
-</div>
+>ℹ️ Para crear cualquier configuración extra, usted debe enviar al equipo de inStore (instoredevs@vtex.com) los extras que la aplicación necesita para completar la transacción. Así, crearemos un formulario en el módulo de Pagos para que el cliente pueda configurar su adquirente.
 
 ## URI de envío y URI de respuesta para cada acción
 
@@ -123,9 +121,8 @@ URI final que la aplicación de pago recibirá para ejecutar la acción de reemb
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&autoConfirm=True&sellerName=instoreqa&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class="alert alert-warning">>
-<strong>NOTA:</strong> No todos los parámetros serán utilizados por todos los adquirentes/apps de pago. Ejemplo: <code>transactionId</code>. Este parámetro es el ID de una transacción en VTEX que identifica todos los pagos de un pedido completo en el PCI Gateway de VTEX. Una transacción puede contener varios pagos, como cuando un pedido se paga con varias tarjetas de crédito o débito.
-</div>
+>⚠️ >
+> **NOTA:** No todos los parámetros serán utilizados por todos los adquirentes/apps de pago. Ejemplo: `transactionId`. Este parámetro es el ID de una transacción en VTEX que identifica todos los pagos de un pedido completo en el PCI Gateway de VTEX. Una transacción puede contener varios pagos, como cuando un pedido se paga con varias tarjetas de crédito o débito.
 
 ## Ejemplos de URI de respuesta para cada acción
 
@@ -184,9 +181,8 @@ Para que la integración funcione, es necesario que el cliente configure en el m
 
 La integración de AppLinking no incluye otras dependencias, ya que la comunicación entre la app inStore y la appp de pago se realiza con URIs específicas que contienen todos los parámetros de configuración y pago necesarios para la acción.
 
-<div class="alert alert-warning">>
-En Android, toda comunicación debe suceder con un nuevo <code>Intent</code>. Esto significa que usted no debe enviar la respuesta como un retorno de llamada del <code>Intent</code> inicial. En su lugar, debe enviar un nuevo <code>Intent</code> a la aplicación inStore con la respuesta anterior.
-</div>
+>⚠️ >
+> En Android, toda comunicación debe suceder con un nuevo `Intent`. Esto significa que usted no debe enviar la respuesta como un retorno de llamada del `Intent` inicial. En su lugar, debe enviar un nuevo `Intent` a la aplicación inStore con la respuesta anterior.
 
 Para configurar el conector de InStore, usteddebe seguir estos pasos:
 
diff --git a/docs/tracks/es/integration-overview.md b/docs/tracks/es/integration-overview.md
index 75af202b3..9e5a0518a 100644
--- a/docs/tracks/es/integration-overview.md
+++ b/docs/tracks/es/integration-overview.md
@@ -16,9 +16,7 @@ trackSlugES: integracion-de-facebook
 
 Esta guía explica cómo realizar la integración con Facebook utilizando el conector desarrollado por VTEX. La integración a través de conectores nativos debe ser su selección predeterminada, ya que implica más eficiencia y seguridad.
 
-<div class="alert alert-danger">
-Se puede <a href="https://help.vtex.com/es/tutorial/configurando-xml--tutorials_242">configurar la integración por archivo XML</a>. Sin embargo, no es aconsejable realizar la integración simultáneamente por archivo XML y conector nativo, ya que esto genera conflictos y divergencia en la información.
-</div>
+>❗ Se puede [configurar la integración por archivo XML](https://help.vtex.com/es/tutorial/configurando-xml--tutorials_242). Sin embargo, no es aconsejable realizar la integración simultáneamente por archivo XML y conector nativo, ya que esto genera conflictos y divergencia en la información.
 
 Antes de realizar la integración, tiene que haber creado:
 
@@ -35,8 +33,6 @@ Los siguientes pasos para integrar su tienda VTEX con Facebook son:
 
 Después de realizar estos pasos, la integración estará finalizada. Sin embargo, los atributos del producto no habrán sido enviados.
 
-<div class="alert alert-info">
-Si desea enviar los atributos de sus productos a Facebook, es necesario que realice un mapeo por plantilla de las categorías y los atributos. Este mapeo es opcional. Sin embargo, si opta por realizarlo, debe hacerlo siguiendo todos las etapas descritas. De lo contrario, se pueden producir errores en la integración.
-</div>
+>ℹ️ Si desea enviar los atributos de sus productos a Facebook, es necesario que realice un mapeo por plantilla de las categorías y los atributos. Este mapeo es opcional. Sin embargo, si opta por realizarlo, debe hacerlo siguiendo todos las etapas descritas. De lo contrario, se pueden producir errores en la integración.
 
 Los pasos necesarios para realizar el mapeo de categorías y atributos se describen con más detalle en el artículo [Envío de productos a Facebook](https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc/41qzoa7TWIYTyIhABHdgzI).
diff --git a/docs/tracks/es/intelligent-synonyms.md b/docs/tracks/es/intelligent-synonyms.md
index 769155017..151c602ef 100644
--- a/docs/tracks/es/intelligent-synonyms.md
+++ b/docs/tracks/es/intelligent-synonyms.md
@@ -14,9 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad está disponible para cuentas que tengan una cantidad mínima de sesiones y pedidos para que el modelo de inteligencia artificial sea entrenado. Si estás interesado en implementarla, por favor, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>. Es posible que se apliquen tarifas adicionales en el futuro.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible para cuentas que tengan una cantidad mínima de sesiones y pedidos para que el modelo de inteligencia artificial sea entrenado. Si estás interesado en implementarla, por favor, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support). Es posible que se apliquen tarifas adicionales en el futuro.
 
 La funcionalidad [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) te permite registrar palabras o expresiones con el mismo significado para los términos de búsqueda utilizados por los clientes al realizar búsquedas en tu tienda, lo que aumenta las posibilidades de que obtengan resultados de búsqueda relevantes.
 
diff --git a/docs/tracks/es/introduction-to-vtex.md b/docs/tracks/es/introduction-to-vtex.md
index f11862b2c..9d2584eb2 100644
--- a/docs/tracks/es/introduction-to-vtex.md
+++ b/docs/tracks/es/introduction-to-vtex.md
@@ -20,17 +20,13 @@ La imagen a continuación muestra las soluciones y posibilidades de VTEX, que se
 
 ![vtex_composable_complete_ES](https://images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/80e21dd3aebbe2c74c752b8d61d7a2f9/vtex_composable_complete_ES.png)
 
-<div class="alert alert-info">
-Además de los portales Help Center y <a href="https://developers.vtex.com/">Developer Portal</a> y <a href="https://community.vtex.com/">VTEX Community</a>, en nuestro <a href="https://vtex.com/co-es/">sitio web</a>ofrecemos más información sobre la plataforma a través de <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">videos explicativos</a> (solo en inglés) y <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> creados por nuestros <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">partners</a>. También ponemos a disposición una serie de <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">videos de onboarding</a> (solamente en portugués).
-</div>
+>ℹ️ Además de los portales Help Center y [Developer Portal](https://developers.vtex.com/) y [VTEX Community](https://community.vtex.com/), en nuestro [sitio web](https://vtex.com/co-es/)ofrecemos más información sobre la plataforma a través de [videos explicativos](https://vtex.com/br-pt/resources-category/product-demo-videos-br/) (solo en inglés) y [ebooks](https://vtex.com/br-pt/resources-category/ebooks-br/) creados por nuestros [partners](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion). También ponemos a disposición una serie de [videos de onboarding](https://sites.google.com/vtex.com.br/onboardingvtex/trilha) (solamente en portugués).
 
 ## Visión general de esta serie
 
 Esta serie de artículos muestra la jornada de una tienda VTEX, desde la [configuración inicial](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) hasta el [go live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH). Antes de configurar los [módulos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) de la plataforma, planificar las [integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) y elegir una tecnología de [frontend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para la construcción del storefront, hay un paso previo: definir el [tipo de cuenta y la arquitectura](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) que mejor se ajuste a las necesidades específicas del negocio.
 
-<div class="alert alert-warning">
-Cada operación de ecommerce tiene sus propias particularidades y este contenido no busca abarcar todas las situaciones existentes. El objetivo es ofrecer un modelo general y presentar de forma contextualizada los recursos y posibilidades de la plataforma VTEX.
-</div>
+>⚠️ Cada operación de ecommerce tiene sus propias particularidades y este contenido no busca abarcar todas las situaciones existentes. El objetivo es ofrecer un modelo general y presentar de forma contextualizada los recursos y posibilidades de la plataforma VTEX.
 
 La organización secuencial del contenido tiene un propósito didáctico y no implica necesariamente que las etapas deban llevarse a cabo en orden lineal o que la conclusión de una etapa sea un requisito para iniciar la siguiente. En algunos casos, las etapas pueden llevarse a cabo en paralelo, o al menos parcialmente. Es el caso de las integraciones del backend, las configuraciones de determinados módulos y la implementación del frontend.
 
diff --git a/docs/tracks/es/inventory-and-shipping-module-overview.md b/docs/tracks/es/inventory-and-shipping-module-overview.md
index 1fee9e258..8fba20538 100644
--- a/docs/tracks/es/inventory-and-shipping-module-overview.md
+++ b/docs/tracks/es/inventory-and-shipping-module-overview.md
@@ -14,9 +14,7 @@ trackId: 13TFDwDttPl9ki9OXQhyjx
 trackSlugES: logistica-101
 ---
 
-<div class="alert alert-info">
-Aviso: Esta documentación está siendo actualizada con el fin de reflejar el cambio del concepto de Paneles a <a href="https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">Estrategia de Envío</a>.
-</div>
+>ℹ️ Aviso: Esta documentación está siendo actualizada con el fin de reflejar el cambio del concepto de Paneles a [Estrategia de Envío](https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 El módulo __Inventario y Envío__ es el servicio responsable de la *logística* de su tienda. Es en este sistema donde usted registrará los datos de las __rutas logísticas__ que realizan la entrega de sus pedidos. Además, es en este módulo que debe hacer la __gestión de inventario__, registrar los __precios de flete__ y el __plazo__ para cada tipo de entrega.
 
diff --git a/docs/tracks/es/levar-os-contatos-do-whatsapp-para-um-crm.md b/docs/tracks/es/levar-os-contatos-do-whatsapp-para-um-crm.md
index bf6eb36af..55e325f5a 100644
--- a/docs/tracks/es/levar-os-contatos-do-whatsapp-para-um-crm.md
+++ b/docs/tracks/es/levar-os-contatos-do-whatsapp-para-um-crm.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/live-support.md b/docs/tracks/es/live-support.md
index 8c5484cc0..e0317bfc1 100644
--- a/docs/tracks/es/live-support.md
+++ b/docs/tracks/es/live-support.md
@@ -35,9 +35,7 @@ Si eliges no utilizarlo, debes incluir un mensaje de indisponibilidad que indiqu
 2. Define la zona horaria. 
 3. Selecciona los días y establece el horario en el que tu tienda estará disponible para atender a los clientes vía WhatsApp. Es posible definir más de un período de servicio por día de la semana.
 ![fuso horário es](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/ee9b18b394f724ea9b8c6e31eb79fcb0/horarios_funcionamento_es.png)
-<div class="alert alert-info">
-Para los feriados nacionales, regionales u otras fechas en las que no vayas a prestar servicio: informa la fecha y hora en que el servicio no estará disponible. Si los periodos se repiten anualmente, es posible seleccionar “Recurrencia anual”, predefiniendo la configuración de los periodos seleccionados.
-</div>
+>ℹ️ Para los feriados nacionales, regionales u otras fechas en las que no vayas a prestar servicio: informa la fecha y hora en que el servicio no estará disponible. Si los periodos se repiten anualmente, es posible seleccionar “Recurrencia anual”, predefiniendo la configuración de los periodos seleccionados.
 <ol start="4">
   <li>En caso de existir alguna excepción, informa los periodos de indisponibilidad.<br><img src="//images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/ec040b052be986620bc101c9d56ce0f4/excecoes_ou_feriados_es.png"></li>
   <li>Establece un mensaje de indisponibilidad. Este mensaje se enviará cuando los clientes contacten por WhatsApp fuera de las ventanas de servicio previamente configuradas.<br><img src="//images.ctfassets.net/alneenqid6w5/16iLFjlXSqrrAW34s8PIXn/cd07b2d6e44515253f2d9b7a722c5a98/indisponibilidad.png" alt="Mensage de indisponibilidad"></li>
diff --git a/docs/tracks/es/login-e-senha.md b/docs/tracks/es/login-e-senha.md
index dab832440..6b90b9a60 100644
--- a/docs/tracks/es/login-e-senha.md
+++ b/docs/tracks/es/login-e-senha.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugES: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/manage-skus-in-inventory.md b/docs/tracks/es/manage-skus-in-inventory.md
index 2e869de3b..7b6cb47bd 100644
--- a/docs/tracks/es/manage-skus-in-inventory.md
+++ b/docs/tracks/es/manage-skus-in-inventory.md
@@ -50,9 +50,7 @@ Pero antes, preste atención para rellenar de forma correcta esta plantilla. Par
 
 ## API REST
 
-<div class="alert alert-warning">
-Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para saber más, vea nuestro artículo sobre <a href="https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2">cómo crear appKey y appToken para autenticar las integraciones</a>
-</div>
+>⚠️ Las autenticaciones para las llamadas de API REST del módulo de Precios deben realizarse a través de AppKey y AppToken. Para saber más, vea nuestro artículo sobre [cómo crear appKey y appToken para autenticar las integraciones](https://help.vtex.com/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones--43tQeyQJgAKGEuCqQKAOI2)
 
 Para cambiar la cantidad de un SKU en stock por API, debe enviar un __PUT__ al siguiente endpoint:
 
diff --git a/docs/tracks/es/managing-accounts.md b/docs/tracks/es/managing-accounts.md
index 54de3cbb6..bbc33f54f 100644
--- a/docs/tracks/es/managing-accounts.md
+++ b/docs/tracks/es/managing-accounts.md
@@ -36,9 +36,7 @@ Presenta información sobre el estado de la cuenta (activa, inactiva), código d
 
 Muestra el monto de crédito disponible para que el cliente lo utilice en compras y el monto total a pagar (en facturas) por compras ya realizadas utilizando Customer Credit como medio de pago.
 
-<div class="alert alert-warning">
-Cuando el cliente realiza una compra utilizando Customer Credit, pero aún no hay factura para el pedido, el campo <b>Crédito reservado</b> también se muestra en esta pantalla que contiene información sobre el valor del pedido.
-</div>
+>⚠️ Cuando el cliente realiza una compra utilizando Customer Credit, pero aún no hay factura para el pedido, el campo **Crédito reservado** también se muestra en esta pantalla que contiene información sobre el valor del pedido.
 
 ## Gestionar
 
@@ -74,6 +72,4 @@ A partir de este momento, el cliente y su dependiente podrán compartir el monto
 
 Si desea cerrar la cuenta del cliente, en la sección __Otro__, haga clic en `CERRAR CUENTA`.
 
-<div class="alert alert-warning">
-Una cuenta de Customer Credit cerrada no se puede volver a abrir y se eliminarán la factura, el status de cuenta y los datos adicionales de los dependientes. Sin embargo, luego de completar el cierre de cuenta, si lo desea, puede <a href="https://help.vtex.com/es/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#crear-cuentas-individualmente">abrir una nueva cuenta</a> para el cliente utilizando el mismo correo electrónico que la cuenta cerrada.
-</div>
+>⚠️ Una cuenta de Customer Credit cerrada no se puede volver a abrir y se eliminarán la factura, el status de cuenta y los datos adicionales de los dependientes. Sin embargo, luego de completar el cierre de cuenta, si lo desea, puede [abrir una nueva cuenta](https://help.vtex.com/es/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#crear-cuentas-individualmente) para el cliente utilizando el mismo correo electrónico que la cuenta cerrada.
diff --git a/docs/tracks/es/managing-customer-credit-invoices.md b/docs/tracks/es/managing-customer-credit-invoices.md
index 75fa6c0be..b081a4354 100644
--- a/docs/tracks/es/managing-customer-credit-invoices.md
+++ b/docs/tracks/es/managing-customer-credit-invoices.md
@@ -27,9 +27,7 @@ La pantalla __Facturas__ en el Admin de VTEX (__Aplicaciones > Customer Credit >
 
 Para seleccionar la lista de invoices que se mostrarán, puede hacer clic en uno de los cuatro estados (Abierto, Pagado, Cancelado o Vencido), o ingresar el número de identificación del pedido para el cual se emitió la invoice.
 
-<div class="alert alert-warning">
-En Customer Credit, todos los títulos se crean con el estado <b>Abierto</b>.
-</div>
+>⚠️ En Customer Credit, todos los títulos se crean con el estado **Abierto**.
 
 ## Detalhes de la factura
 
@@ -42,9 +40,7 @@ Para facilitar el proceso de pago de una factura, es posible proporcionar un lin
 - Utilice la función `IMPORTAR` para insertar datos desde una plantilla .csv.
 - Via endpoint [PUT Change Invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-) da API Customer Credit.
 
-<div class="alert alert-info">
-Luego de realizar uno de los trámites anteriores, el cliente tendrá acceso al botón <b>PAGAR</b> que estará disponible en su área de cliente en la web de la tienda (<b>Mi Cuenta > Mis Créditos</b >).
-</div>
+>ℹ️ Luego de realizar uno de los trámites anteriores, el cliente tendrá acceso al botón **PAGAR** que estará disponible en su área de cliente en la web de la tienda (<b>Mi Cuenta > Mis Créditos</b >).
 
 ### Liquidación individual
 
diff --git a/docs/tracks/es/managing-shipping-rates.md b/docs/tracks/es/managing-shipping-rates.md
index 5b267fabf..633f3783e 100644
--- a/docs/tracks/es/managing-shipping-rates.md
+++ b/docs/tracks/es/managing-shipping-rates.md
@@ -37,9 +37,7 @@ Después de que la tienda cierra el contrato con una trasportadora, normalmente
 - **Country**: País donde se realizará la entrega. Debe completarse con el  [código ISO de 3 dígitos del país](https://countrycode.org/).
 - **MinimumValueInsurance**: Es un adicional de flete con valor absoluto, que será comparado con el valor registrado en PricePercent y multiplicado por el valor del carrito. El valor mayor será el que se agregue al flete. Siempre se agregará al flete apenas uno de los dos. Ver más en [¿Para qué sirve el campo Minimum Value Insurance?](/pt/faq/para-que-serve-o-campo-na-tabela-de-frete-minimum-value-insurance).
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> Si la plantilla tiene más de 10 MB, deberá comprimirla en un formato <fuerte>.zip</strong>. Este archivo.zip también debe tener menos de 10 MB para que la carga funcione. Si el archivo sigue excediendo el límite, recomendamos dividir la plantilla entre más de una transportadora.
-</div>
+>⚠️ **OBS:** Si la plantilla tiene más de 10 MB, deberá comprimirla en un formato <fuerte>.zip</strong>. Este archivo.zip también debe tener menos de 10 MB para que la carga funcione. Si el archivo sigue excediendo el límite, recomendamos dividir la plantilla entre más de una transportadora.
 
 ## Gestionar las tarifas de envío fuera de la plantilla
 
diff --git a/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index e69500108..0fdb6abe6 100644
--- a/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/es/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -74,11 +74,12 @@ Al desconectarse, la integración con TikTok se detiene por completo: el píxel
 
 Por otro lado, VTEX no elimina los productos existentes en TikTok, es decir, siguen apareciendo en TikTok. Para eliminarlos de TikTok, debes eliminar manualmente los productos desde [TikTok Catalog Manager](https://ads.tiktok.com/help/article?aid=10001005).
 
-<div class="alert alert-warning">
-<p>Si aparece un mensaje de error al desconectar TikTok de tu tienda VTEX, sigue los pasos a continuación para asegurarte de que la integración se desactive correctamente.</p>
-<ol><li>Accede a la página <a href="https://ads.tiktok.com/ac/page/authorizations">Autorizaciones</a> en TikTok Ads Manager.</li>
-  <li>Busca la opción <strong>VTEX</strong>.</li>
-  <li>Haz clic en <code>Remover</code>.</li></ol>
-</div>
+>⚠️ Si aparece un mensaje de error al desconectar TikTok de tu tienda VTEX, sigue los pasos a continuación para asegurarte de que la integración se desactive correctamente.
+>
+> Accede a la página [Autorizaciones](https://ads.tiktok.com/ac/page/authorizations) en TikTok Ads Manager.
+>
+> 2. Busca la opción **VTEX**.
+>
+> 3. Haz clic en `Remover`.
 
 Después de la desconexión, puedes volver a conectar la integración en cualquier momento volviendo a realizar los pasos descritos en el link [Configuración de la integración con TikTok for Business](https://help.vtex.com/es/tracks/integracion-de-tiktok--1r0yJSO11nrer1YVu3WTFd/4AEUg7pEdX1beOaQhFf0wC).
diff --git a/docs/tracks/es/merchandising-rule-conditions.md b/docs/tracks/es/merchandising-rule-conditions.md
index ba058a932..de1ba997c 100644
--- a/docs/tracks/es/merchandising-rule-conditions.md
+++ b/docs/tracks/es/merchandising-rule-conditions.md
@@ -22,9 +22,7 @@ Conoce los criterios y los operadores posibles para cada forma de edición en la
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"><thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nombre</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descripción</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operadores</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tipo de edición</th> </tr></thead><tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span></td> <td rowspan="2" class="t-body pa5">Palabra que el cliente busca y estará relacionada con la regla. Campo para rellenar libremente.</td> <td class="t-body pa5">es</td> <td rowspan="2" class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br>Reglas de personalización</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">contiene</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Busca el ID exacto de algún ítem del catálogo que estará relacionado con la regla. Los ID posibles son: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong> y <strong>EAN</strong>. Campo para rellenar libremente.</td> <td class="t-body pa5">es</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de personalización</td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">categoría</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una categoría registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">departamento</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa un departamento registrado en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">marca</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una marca registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">nombresclusterproductos</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una colección registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoción</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que valida si existe al menos una promoción vinculada al ítem (sí).</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solamente </td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">nombreseller</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa el nombre de un seller.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategoría</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una subcategoría registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{especificación}}</span></td> <td rowspan="2" class="t-body pa5">Cualquier especificación activa del Catálogo aparece como un criterio personalizado, con los mismos valores posibles. El nombre del criterio es igual al nombre de la especificación registrada. Por ejemplo, si hay una especificación activa llamada <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>, el criterio mostrado será <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr></tbody></table>
 
-<div class="alert alert-warning">
-  <p>Los criterios <code>departamento</code>, <code>categoría</code> y <code>subcategoría</code> solo aparecen como opciones para componer las Reglas de merchandising si los tres niveles de categorías ya están configurados en el <strong>Catálogo</strong>.</p>
-</div>
+>⚠️ Los criterios `departamento`, `categoría` y `subcategoría` solo aparecen como opciones para componer las Reglas de merchandising si los tres niveles de categorías ya están configurados en el **Catálogo**.
 
 ## Operadores
 
diff --git a/docs/tracks/es/monitor-da-integracao.md b/docs/tracks/es/monitor-da-integracao.md
index 9f0d808ef..06551b3b6 100644
--- a/docs/tracks/es/monitor-da-integracao.md
+++ b/docs/tracks/es/monitor-da-integracao.md
@@ -14,6 +14,4 @@ trackId: 132YFN170Jvs6ZUBGh8w2e
 trackSlugES: adaptador-vtex
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/next-steps.md b/docs/tracks/es/next-steps.md
index 054eaa344..4c6887d69 100644
--- a/docs/tracks/es/next-steps.md
+++ b/docs/tracks/es/next-steps.md
@@ -16,9 +16,7 @@ trackSlugES: proximos-pasos-tras-el-go-live
 
 Ahora que la tienda está configurada en el entorno VTEX y el [go-live](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH) se completó con éxito, presentaremos las funcionalidades y [soluciones adicionales](https://help.vtex.com/en/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) disponibles que ayudan a optimizar el rendimiento de las ventas y la expansión de la operación con el objetivo de contribuir al desarrollo continuo del negocio.
 
-<div class="alert alert-warning">
-  <p>Puedes contratar <a href="https://partnerportal.vtex.com/">partners</a> para ayudar con el desarrollo de la tienda y la gestión de las soluciones descritas en este artículo a través de <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">VTEX Partner Portal</a> (solamente en portugués). Para acceder al portal, el usuario debe tener <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz">acceso al Admin VTEX</a> de una tienda.</p>
-</div>
+>⚠️ Puedes contratar [partners](https://partnerportal.vtex.com/) para ayudar con el desarrollo de la tienda y la gestión de las soluciones descritas en este artículo a través de [VTEX Partner Portal](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) (solamente en portugués). Para acceder al portal, el usuario debe tener [acceso al Admin VTEX](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) de una tienda.
 
 ## Lanzamientos en VTEX
 
diff --git a/docs/tracks/es/order-flow.md b/docs/tracks/es/order-flow.md
index 95a1d0ceb..27a9e7d6b 100644
--- a/docs/tracks/es/order-flow.md
+++ b/docs/tracks/es/order-flow.md
@@ -25,9 +25,7 @@ Los conceptos de [marketplace y seller](https://help.vtex.com/es/tutorial/estrat
 - __Marketplace__ es el ambiente donde se cierra el pedido, es decir, donde el cliente realiza el proceso de pago.
 - __Seller__ es el propietario del SKU. Por lo tanto, es responsable del fulfillment, es decir, de entregar el producto al cliente.
 
-<div class="alert alert-info">
-Cuando la tienda vende productos en su propio ambiente y realiza sus propias entregas es Marketplace y Seller al mismo tiempo.
-</div>
+>ℹ️ Cuando la tienda vende productos en su propio ambiente y realiza sus propias entregas es Marketplace y Seller al mismo tiempo.
 
 Es importante comprender estos conceptos porque el flujo de pedidos en el Marketplace es diferente del flujo en el Seller.
 
@@ -71,14 +69,13 @@ Una vez que el pago ha sido aprobado, el pedido pasa a `Pago Aprobado` y luego a
 
 Es decir, en este caso, los pasos de pago y entrega son responsabilidad de la tienda.
 
-<div class="alert alert-info">
-Cada pedido se completa solo en uno de dos estados posibles:<br>
-<ul>
-  <li>Facturado</li>
-  <li>Cancelado</li>
-</ul>
-</div>
-
-<div class="alert alert-info">
-Para comprender el status de cada pedido con más detalle, consulte nuestra tabla con todos los status en <a href="https://help.vtex.com/es/tutorial/fluxo-de-pedido--tutorials_196#entiendo-los-estados">Entendiendo los status</a>.
-</div>
+>ℹ️ Cada pedido se completa solo en uno de dos estados posibles:
+>
+> 
+>
+> * Facturado
+>
+> * Cancelado
+> 
+
+>ℹ️ Para comprender el status de cada pedido con más detalle, consulte nuestra tabla con todos los status en [Entendiendo los status](https://help.vtex.com/es/tutorial/fluxo-de-pedido--tutorials_196#entiendo-los-estados).
diff --git a/docs/tracks/es/pickup-points-concept-definition.md b/docs/tracks/es/pickup-points-concept-definition.md
index 493107e79..437337855 100644
--- a/docs/tracks/es/pickup-points-concept-definition.md
+++ b/docs/tracks/es/pickup-points-concept-definition.md
@@ -16,9 +16,7 @@ trackSlugES: logistica-101
 
 Un punto de recogida es un lugar físico donde el cliente tiene la opción de recoger su pedido por su cuenta. Por lo tanto, es una etapa opcional y que finaliza la ruta logística.
 
-<div class="alert alert-info">
-La funcionalidad de puntos de recogida está disponible apenas para las cuentas que ya tienen acceso al <b>Checkout V6</b>.
-</div>
+>ℹ️ La funcionalidad de puntos de recogida está disponible apenas para las cuentas que ya tienen acceso al **Checkout V6**.
      
 ## Relación con la transportadora
 
diff --git a/docs/tracks/es/pickup-store.md b/docs/tracks/es/pickup-store.md
index e11d74cf9..69d1723e7 100644
--- a/docs/tracks/es/pickup-store.md
+++ b/docs/tracks/es/pickup-store.md
@@ -14,9 +14,7 @@ trackId: t3DOYAJjWgqAMeAKq2MWS
 trackSlugES: instore-setup
 ---
 
-<div class="alert alert-info">
-Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a <a href="https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envío</a>.
-</div>
+>ℹ️ Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a [estratégia de envío](https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 Para configurar el inStore con el modo de __Retirada en la tienda__, es decir, para considerar el inventario de su tienda física, usted depende de dos factores:
 
diff --git a/docs/tracks/es/planning-the-go-live.md b/docs/tracks/es/planning-the-go-live.md
index fe912e0d8..b93bd55cf 100644
--- a/docs/tracks/es/planning-the-go-live.md
+++ b/docs/tracks/es/planning-the-go-live.md
@@ -68,9 +68,7 @@ Después de la fecha del lanzamiento oficial, con la tienda plenamente operativa
 
 Antes del go live, es muy importante comprobar las configuraciones esenciales para el buen funcionamiento de la tienda. Para esto recomendamos verificar la [Lista de configuración de la tienda](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx). En cada punto se debe confirmar que las configuraciones se completaron de acuerdo con las características de operación de la tienda.
 
-<div class="alert alert-warning">
- <p>La lista de comprobación indicada anteriormente enumera las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. El <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">equipo de implementación</a> de cada tienda es responsable de definir las funcionalidades y configuraciones que se deben aplicar para producir la experiencia de compra deseada para los clientes. Recomendamos comprobar todos los aspectos operativos de la tienda y añadirlos a la lista en caso de que no estén incluidos.</p>
-</div>
+>⚠️ La lista de comprobación indicada anteriormente enumera las funcionalidades y configuraciones básicas para el funcionamiento de una tienda VTEX. El [equipo de implementación](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion) de cada tienda es responsable de definir las funcionalidades y configuraciones que se deben aplicar para producir la experiencia de compra deseada para los clientes. Recomendamos comprobar todos los aspectos operativos de la tienda y añadirlos a la lista en caso de que no estén incluidos.
 
 ## 3. Configuración del dominio y la cuenta
 
@@ -80,9 +78,7 @@ Después de completar las configuraciones internas de la tienda se deben realiza
 2. [Configurar registro CAA](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#configurar-registro-caa): indicar que la autoridad de certificación (CA) **Let's Encrypt** está autorizada para generar y renovar certificados que acrediten la identidad del dominio. Este paso es necesario si hay un registro CAA en el servidor DNS.
 3. [Añadir cuenta en producción](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#colocar-conta-em-producao): activar la cuenta VTEX en producción. Aun después de la activación, la tienda sigue sin estar disponible para clientes externos. Solo se podrán ver y comprar productos en la tienda después de la finalización del go live, según los pasos que se describen en las próximas secciones de este artículo.
 
-<div class="alert alert-warning">
- <p>Desde el momento en que la cuenta se active en producción, todos los pedidos se cobrarán automáticamente y el <a href="https://help.vtex.com/es/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322#valores-da-receita-aprovada">take rate</a> se aplicará según el plan acordado con VTEX. Esto incluye los pedidos realizados en `{nombredelatienda}.myvtex.com`, incuso si fueron realizados como prueba.</p>
-</div>
+>⚠️ Desde el momento en que la cuenta se active en producción, todos los pedidos se cobrarán automáticamente y el [take rate](https://help.vtex.com/es/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322#valores-da-receita-aprovada) se aplicará según el plan acordado con VTEX. Esto incluye los pedidos realizados en `{nombredelatienda}.myvtex.com`, incuso si fueron realizados como prueba.
 
 Para más información, consulta el artículo [Configuración](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX), que forma parte de la serie [Go live](https://help.vtex.com/es/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/1iP90RcJvlrfQhnlxM54wo).
 
@@ -94,9 +90,7 @@ VTEX permite crear entornos independientes para estas pruebas. Cuando se crea un
 
 Para planificar una fase de pruebas ponte en contacto con [nuestro equipo de soporte](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy), que es el canal para [contratar un entorno de pruebas](https://help.vtex.com/es/tutorial/contratar-ambiente-de-testes--2nmZAHlfQoGsCWmEWGIoGy).
 
-<div class="alert alert-info">
- <p>Si la tienda fue<a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#entorno-de-desarrollo"> creada utilizando VTEX IO</a>, puedes realizar pruebas A/B entre workspaces, es decir, comparar el rendimiento de entornos de desarrollo de storefront. Para más información, consulta la guía de desarrolladores<a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing"> Running A/B tests</a>.</p>
-</div>
+>ℹ️ Si la tienda fue[ creada utilizando VTEX IO](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#entorno-de-desarrollo), puedes realizar pruebas A/B entre workspaces, es decir, comparar el rendimiento de entornos de desarrollo de storefront. Para más información, consulta la guía de desarrolladores[ Running A/B tests](https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing).
 
 ### Quality Assurance (QA)
 
@@ -116,9 +110,7 @@ Después de concluidas las pruebas y ajustes correspondientes, se debe preparar
 
 1. [Registrar el dominio en VTEX](https://help.vtex.com/es/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450): hay que acceder a **Configuración de la cuenta** en el Admin VTEX para conectar la dirección de la tienda.
 
-   <div class="alert alert-warning">
-     <p>Después del registro, hay un plazo de siete días para completar el go live. Si la tienda no completa los procedimientos requeridos para el go live en ese periodo, habrá que acceder al registro y guardarlo nuevamente.</p>
-   </div>
+   >⚠️ Después del registro, hay un plazo de siete días para completar el go live. Si la tienda no completa los procedimientos requeridos para el go live en ese periodo, habrá que acceder al registro y guardarlo nuevamente.
 
 2. **Solicitar apuntamiento interno:** hay que abrir un ticket con el [soporte VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy) para solicitar el apuntamiento de DNS interno. El plazo para completar esta solicitud es de hasta tres días laborables.
 
@@ -152,9 +144,7 @@ Independientemente del tipo de solicitud que se necesite, el ticket para el sopo
 - Indicar si la tienda tiene reglas condicionales de [políticas comerciales](https://help.vtex.com/es/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE).
 - Si ya hay un sitio web activo que se esté migrando a VTEX, indicar si se utiliza la red CDN de Azion o Cloudfront.
 
-<div class="alert alert-warning">
- <p>Después de recibir la confirmación de apuntamiento interno, hay que realizar el apuntamiento común de DNS en hasta cinco días. De lo contrario, el apuntamiento interno se eliminará y habrá que enviar una nueva solicitud.</p>
-</div>
+>⚠️ Después de recibir la confirmación de apuntamiento interno, hay que realizar el apuntamiento común de DNS en hasta cinco días. De lo contrario, el apuntamiento interno se eliminará y habrá que enviar una nueva solicitud.
 
 ## 6. Go live
 
@@ -162,15 +152,11 @@ Durante el go live, después de la confirmación del apuntamiento interno realiz
 
 1. [Realizar el apuntamiento DNS:](https://help.vtex.com/es/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dnshttps://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dns) en la zona DNS del dominio, crear una entrada de tipo CNAME en el subdominio deseado para el destino ``{dominio}.cdn.vtex.com``. El ``{dominio}`` debe ser el mismo que está registrado en VTEX.
 
-   <div class="alert alert-warning">
-    <p>La propagación del apuntamiento DNS puede tomar de 24 a 48 horas para completarse. Esto significa que la dirección configurada puede no estar accesible a todo el mundo justo después de la configuración.</p>
-   </div>
+   >⚠️ La propagación del apuntamiento DNS puede tomar de 24 a 48 horas para completarse. Esto significa que la dirección configurada puede no estar accesible a todo el mundo justo después de la configuración.
 
 2. [Notificar el apuntamiento:](https://help.vtex.com/es/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#notificar-apontamento) para que la tienda esté disponible al público general, se debe notificar a la plataforma VTEX que el apuntamiento fue realizado. Para esto, hay que guardar nuevamente la **Configuración de la cuenta** en el Admin VTEX.
 
-   <div class="alert alert-info">
-    <p>Si la tienda fue creada con<a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#faststore"> FastStore</a>, también se deben seguir los pasos descritos en el artículo<a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns"> Configuring external DNS for a custom domain</a>.</p>
-   </div>
+   >ℹ️ Si la tienda fue creada con[ FastStore](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#faststore), también se deben seguir los pasos descritos en el artículo[ Configuring external DNS for a custom domain](https://www.faststore.dev/docs/go-live/2-configuring-external-dns).
 
 Luego de completar las etapas anteriores, la tienda estará disponible en el dominio registrado para que los clientes puedan entrar y hacer compras.
 
diff --git a/docs/tracks/es/pre-go-live.md b/docs/tracks/es/pre-go-live.md
index 1f5b7c240..35b08eb43 100644
--- a/docs/tracks/es/pre-go-live.md
+++ b/docs/tracks/es/pre-go-live.md
@@ -20,9 +20,7 @@ Esta etapa inicia el _go live_, ya que estos pasos deben programarse cuidadosame
 
 Debes [registrar el dominio en Configuración de la cuenta](https://help.vtex.com/es/tutorial/configurando-dominios-no-license-manager). Eso es lo que conecta la dirección a la tienda.
 
-<div class="alert alert-warning">
-Después de registrar tu dominio, tienes siete días para completar el _go live_. En caso contrario, deberás acceder al registro realizado y volver a guardar.
-</div>
+>⚠️ Después de registrar tu dominio, tienes siete días para completar el _go live_. En caso contrario, deberás acceder al registro realizado y volver a guardar.
 
 ## Solicitar el apuntamiento IO
 
diff --git a/docs/tracks/es/preco-fixo-definicao-de-conceito.md b/docs/tracks/es/preco-fixo-definicao-de-conceito.md
index 63dbaebd5..2dfc9a25a 100644
--- a/docs/tracks/es/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/es/preco-fixo-definicao-de-conceito.md
@@ -23,9 +23,7 @@ De este modo, el precio fijo se sobrepone al __precio base__, incluso en los cas
 
 Esto significa que el precio fijo tiene una prioridad sobre el precio base y la regla de precio definida para una tabla.
 
-<div class="alert alert-warning">
-  <p>Solo los <a href="https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj">precios fijos</a> se utilizan en nuestras integraciones nativas con marketplaces. Los otros escenarios previstos en la <a href="https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx">arquitectura del sistema de precios</a> solo están disponibles para marketplaces VTEX-VTEX.</p>
-</div>
+>⚠️ Solo los [precios fijos](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj) se utilizan en nuestras integraciones nativas con marketplaces. Los otros escenarios previstos en la [arquitectura del sistema de precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) solo están disponibles para marketplaces VTEX-VTEX.
 
 ## Funcionalidades 
 
diff --git a/docs/tracks/es/printing-an-order-summary.md b/docs/tracks/es/printing-an-order-summary.md
index 7274e7968..a6510054d 100644
--- a/docs/tracks/es/printing-an-order-summary.md
+++ b/docs/tracks/es/printing-an-order-summary.md
@@ -38,9 +38,7 @@ Para emparejar VTEX Sales App con una impresora, deben cumplirse los siguientes
 * Si no tienes VTEX Sales App en tu computador, instala la aplicación siguiendo nuestra guía de [Instalación](https://help.vtex.com/es/tracks/instore-usando-el-app--4BYzQIwyOHvnmnCYQgLzdr/2rPSJ8519UCCZo5uEBkqxh).
 * Obtener un par de credenciales (AppKey y AppToken) con los permisos de acceso correspondientes. Lee el artículo [Claves de aplicación](https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet) para obtener más información.
 
-<div class="alert alert-info">
-<p>Recomendamos que el perfil de acceso relacionado con estas credenciales sea el <strong>VTEX Sales App Sales Person</strong>. Sin embargo, también se puede utilizar un perfil con acceso a otros módulos del Admin, como <strong>Admin Super</strong>.</p>
-</div>
+>ℹ️ Recomendamos que el perfil de acceso relacionado con estas credenciales sea el **VTEX Sales App Sales Person**. Sin embargo, también se puede utilizar un perfil con acceso a otros módulos del Admin, como **Admin Super**.
 
 ### Paso a paso
 
diff --git a/docs/tracks/es/promotions-for-specific-scenarios.md b/docs/tracks/es/promotions-for-specific-scenarios.md
index 5996dda25..8eda3df3f 100644
--- a/docs/tracks/es/promotions-for-specific-scenarios.md
+++ b/docs/tracks/es/promotions-for-specific-scenarios.md
@@ -26,9 +26,7 @@ Es para atender a estos escenarios que ofrecemos los tipos de promociones que se
 - Compre y gane
 - Límite de ítems con promoción en el carrito 
 
-<div class="alert alert-info">
-Las pantallas de configuración de todas las promociones tienen las mismas secciones principales explicadas en el artículo sobre Promoción Regular. Las opciones presentes en estas secciones se repiten en todas las promociones, con excepción de algunas configuraciones específicas de condiciones para aplicar la promoción. Por lo tanto, en este artículo nos enfocamos en estas configuraciones específicas.
-</div>
+>ℹ️ Las pantallas de configuración de todas las promociones tienen las mismas secciones principales explicadas en el artículo sobre Promoción Regular. Las opciones presentes en estas secciones se repiten en todas las promociones, con excepción de algunas configuraciones específicas de condiciones para aplicar la promoción. Por lo tanto, en este artículo nos enfocamos en estas configuraciones específicas.
 
 ### Comprar Juntos
 
@@ -87,9 +85,7 @@ Para entender la promoción Compre y Gane con más detalle, vea el artículo  <a
 
 Esta configuración define cuántos ítems del carrito serán objeto de la promoción.
 
-<div class="alert alert-warning">
-Es importante señalar que esta posibilidad es <strong>válida apenas para una promoción regular con descuento porcentual.</strong>
-</div>
+>⚠️ Es importante señalar que esta posibilidad es **válida apenas para una promoción regular con descuento porcentual.**
 
 Después de rellenar todos [los campos de una promoción regular](https://help.vtex.com/es/tutorial/regular-promotion--tutorials_327) con descuento porcentual, puede seleccionar la opción __Definir la cantidad máxima de ítems afectados por carrito__ en la sección __Restricciones y limitaciones de uso__.
 
diff --git a/docs/tracks/es/redirect.md b/docs/tracks/es/redirect.md
index 62d295aaf..5f699a7df 100644
--- a/docs/tracks/es/redirect.md
+++ b/docs/tracks/es/redirect.md
@@ -16,9 +16,7 @@ trackSlugES: vtex-intelligent-search
 
 La funcionalidad de **Redireccionamientos** direcciona al cliente a cualquier otra página, ya sea interna o externa a la tienda. Los redireccionamientos se hacen en el área de búsqueda de tu storefront, utilizando términos o filtros que el cliente haya seleccionado. De este modo, una de las ventajas de los redireccionamientos es contemplar escenarios de comunicación que la búsqueda en el catálogo de la tienda no cubre, como por ejemplo redirigir la búsqueda de una marca a su página promocional.
 
-<div class="alert alert-warning">
-<p>Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lee nuestro artículo VTEX Intelligent Search: configuración Multidioma (Beta) para obtener más información.</p>
-</div>
+>⚠️ Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lee nuestro artículo VTEX Intelligent Search: configuración Multidioma (Beta) para obtener más información.
 
 ## Cómo funciona un redireccionamiento
 
diff --git a/docs/tracks/es/register-mercado-livre-integration.md b/docs/tracks/es/register-mercado-livre-integration.md
index b0db9fa86..6f46dcfe8 100644
--- a/docs/tracks/es/register-mercado-livre-integration.md
+++ b/docs/tracks/es/register-mercado-livre-integration.md
@@ -20,9 +20,7 @@ trackSlugES: configurar-integracion-con-mercado-libre
 4.	Busque la integración __Mercado Livre Classic__ o __Mercado Livre Premium__ y haga clic en `Integrar`.
 5.	Rellene los campos indicados a continuación. El asterisco significa que es obligatorio completarlos. A continuación, haga clic en el botón `Guardar configuración`.
 
-<div class="alert alert-info">
-Cada cuenta VTEX debe estar vinculada a una sola cuenta en Mercado Libre, aunque se utilicen ambos conectores (Classic y Premium). Actualmente no es posible autenticarse con dos cuentas simultáneamente.
-</div>
+>ℹ️ Cada cuenta VTEX debe estar vinculada a una sola cuenta en Mercado Libre, aunque se utilicen ambos conectores (Classic y Premium). Actualmente no es posible autenticarse con dos cuentas simultáneamente.
 
 - **Integración (si elige desactivar la integración, se eliminará toda la configuración, incluyendo la autenticación y la afiliación)* :**  seleccione *Activada* para que se inicie la integración.
 - **ID del afiliado*:** código de identificación para crear un [afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado) que aún no está registrado en tu sistema. El código debe estar compuesto por tres consonantes, repetidas o no. No se aceptan vocales. Sugerencia: `MLC` (Classic) o `MLP` (Premium). La configuración del conector crea el afiliado automáticamente.
diff --git a/docs/tracks/es/register-the-barcode-of-the-skus-for-instore.md b/docs/tracks/es/register-the-barcode-of-the-skus-for-instore.md
index bd4c85204..0c8ea6aec 100644
--- a/docs/tracks/es/register-the-barcode-of-the-skus-for-instore.md
+++ b/docs/tracks/es/register-the-barcode-of-the-skus-for-instore.md
@@ -16,9 +16,7 @@ trackSlugES: registrar-el-codigo-de-barras-de-los-skus-para-el-instore
 
 Para usar el VTEX Sales App, los productos de la tienda física deben estar agregados en el Catálogo de su cuenta en VTEX. Es allí donde insertamos todos los productos y definimos sus características.
 
-<div class="alert alert-warning">
-Los vendedores solo tendrán acceso a los productos a través de VTEX Sales App una vez que los productos estén agregados en el catálogo de su tienda en VTEX.
-</div>
+>⚠️ Los vendedores solo tendrán acceso a los productos a través de VTEX Sales App una vez que los productos estén agregados en el catálogo de su tienda en VTEX.
 
 Entre la información ingresada en el registro de un producto en el Catálogo, se encuentra el __EAN__. El EAN corresponde al __código de barras__ del SKU. Es el que le permite al vendedor agregar fácilmente el producto al carrito del VTEX Sales App, a través de la máquina lectora. VTEX Sales App también permite ingresar el código de barras en el campo de búsqueda.
 
@@ -35,6 +33,4 @@ Para registrar el EAN del SKU, siga los pasos a continuación:
 
 Alternativamente, el campo EAN, así como otros campos del SKU, se pueden completar a través de planilla o su ERP. Consulte el artículo [Registrar SKUs](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ) para obtener información detallada.
 
-<div class="alert alert-info">
-La información de EAN puede tardar hasta 10 minutos en actualizarse. Después de este procedimiento, será posible agregar el SKU al carrito del VTEX Sales App a través de la máquina lectora de códigos de barras.
-</div>
+>ℹ️ La información de EAN puede tardar hasta 10 minutos en actualizarse. Después de este procedimiento, será posible agregar el SKU al carrito del VTEX Sales App a través de la máquina lectora de códigos de barras.
diff --git a/docs/tracks/es/regra-de-preco-definicao-de-conceito.md b/docs/tracks/es/regra-de-preco-definicao-de-conceito.md
index f69aac500..57d394ac3 100644
--- a/docs/tracks/es/regra-de-preco-definicao-de-conceito.md
+++ b/docs/tracks/es/regra-de-preco-definicao-de-conceito.md
@@ -22,9 +22,7 @@ Las reglas de precio permiten que cambie el precio de un SKU para apenas una tab
 
 Por tanto, cuando combinamos esta regla con el precio base de un SKU, tenemos un nuevo valor. Este será el __precio calculado__ de un SKU dentro de una tabla.
 
-<div class="alert alert-info">
-El uso de las reglas de precio es <strong>opcional</strong>. Si algún SKU no tiene ningún modificador asociado, su precio para la tabla de precios en cuestión será el precio base registrado. 
-</div>
+>ℹ️ El uso de las reglas de precio es **opcional**. Si algún SKU no tiene ningún modificador asociado, su precio para la tabla de precios en cuestión será el precio base registrado.
 
 Las reglas de precio funcionan a partir de __cinco condiciones de configuración__: 
 
diff --git a/docs/tracks/es/relevance.md b/docs/tracks/es/relevance.md
index 52c20b105..069b6e277 100644
--- a/docs/tracks/es/relevance.md
+++ b/docs/tracks/es/relevance.md
@@ -38,9 +38,7 @@ La información aplicada para establecer la relevancia es:
 
 El conjunto de distribución de pesos y criterios genera una puntuación para el producto, lo que ayuda a su posicionamiento en el orden del resultado de la búsqueda.
 
-<div class="alert alert-warning">
-  <p>Si deseas utilizar los criterios de prioridad, recomendamos agregar solo un criterio en este campo. Agregar más criterios compromete la ordenación de los resultados de búsqueda, ya que solo se considerará el primer criterio.</p>
-</div>
+>⚠️ Si deseas utilizar los criterios de prioridad, recomendamos agregar solo un criterio en este campo. Agregar más criterios compromete la ordenación de los resultados de búsqueda, ya que solo se considerará el primer criterio.
 
 De esta manera, es posible adaptar el comportamiento del resultado de búsqueda a una estrategia específica.
 
diff --git a/docs/tracks/es/reports-vtex-intelligent-search.md b/docs/tracks/es/reports-vtex-intelligent-search.md
index d447c7833..748c1490a 100644
--- a/docs/tracks/es/reports-vtex-intelligent-search.md
+++ b/docs/tracks/es/reports-vtex-intelligent-search.md
@@ -40,9 +40,7 @@ Los datos que componen el informe se actualizan cada 4 horas y contienen la sigu
 *   **Pedidos**: número de pedidos realizados desde la búsqueda. Para calcular esta métrica, consideramos que la búsqueda genera un pedido cada vez que, después buscar un término, el cliente hace clic en algún producto que aparece en los resultados y luego compra cualquier producto (no necesariamente el producto en el que hizo clic). 
 *   **Ventas**: ingresos totales generados por los pedidos realizados a partir de la búsqueda. El cálculo sigue la misma lógica que la métrica de **Pedidos**, la diferencia es que el resultado refleja los ingresos en lugar del número de pedidos.
 
-<div class="alert alert-info">
-  <p>Los datos mostrados en el informe se limitan a los 10 mil términos más buscados. Si deseas obtener los datos de búsqueda completos de tu tienda, tienes que <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacion">exportar el informe</a>.</p>
-</div>
+>ℹ️ Los datos mostrados en el informe se limitan a los 10 mil términos más buscados. Si deseas obtener los datos de búsqueda completos de tu tienda, tienes que [exportar el informe](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacion).
 
 Cuando se elige [exportar un informe](#exportacion), también existe la posibilidad de generarlo con las __métricas de embudo__. Si se selecciona esa opción, se agregarán 4 nuevas columnas al archivo:
 
diff --git a/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md b/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md
index b0c7b353f..a993262c1 100644
--- a/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md
+++ b/docs/tracks/es/scheduled-deliveries-and-delivery-capacity.md
@@ -18,9 +18,9 @@ Una tienda VTEX puede ofrecer entregas programadas a sus clientes. De esta forma
 
 Para poner a disposición de los clientes la [entrega programada](https://help.vtex.com/es/tutorial/entrega-programada--22g3HAVCGLFiU7xugShOBi), es necesario incluir ventanas de entrega en la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) de la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-en-vtex--7u9duMD5UQa2QQwukAWMcE) correspondiente. Una vez hecho esto, los períodos y los días disponibles para la entrega programada aparecerán en el checkout de tu tienda.
 
-<div class="alert alert-warning">
-Para que la <a href="https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> y la <a href="https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidad de entrega</a> funcionen correctamente, debes tener en cuenta que:<p><ul><li>La suma de {<a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID de la política de envío} no puede exceder los 60 caracteres.</li><li>No se debe utilizar espacio en el ID de la <a href="https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">política de envío</a>.</li></ul></p>
-</div>
+>⚠️ Para que la [Entrega programada](https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) y la [Capacidad de entrega](https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) funcionen correctamente, debes tener en cuenta que:
+> *La suma de {[account name](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {ID de la política de envío} no puede exceder los 60 caracteres.
+> * No se debe utilizar espacio en el ID de la [política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 Es importante tener en cuenta que la disponibilidad de las entregas programadas está en función del servicio que la transportadora contratada (registrada en la política de envío) ofrece a tu tienda. Para conocer la disponibilidad de las ventanas de entrega (o de los periodos de envío) y de la cantidad de ítems/pedidos que aún pueden atenderse en cada ventana de entrega, consulta la página [Capacidad de entrega](https://help.vtex.com/es/tutorial/gestionar-capacidad-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
diff --git a/docs/tracks/es/seeing-order-details.md b/docs/tracks/es/seeing-order-details.md
index 69e66a8ca..83d5ad027 100644
--- a/docs/tracks/es/seeing-order-details.md
+++ b/docs/tracks/es/seeing-order-details.md
@@ -49,9 +49,7 @@ En la plataforma VTEX también hay una funcionalidad para unificar la comunicaci
 
 Todos los datos del cliente se ingresan en el momento del cierre del pedido y no se pueden cambiar aquí. Para ver y administrar estos datos, usted puede acceder al Master Data.]
 
-<div class="alert alert-info">
-Si su tienda solo actúa como seller de un pedido, no se mostrará el correo electrónico del cliente. Entendemos que la relación del cliente es con el marketplace, por lo que no es recomendable compartir sus datos con el seller sin consentimiento previo.
-  </div>
+>ℹ️ Si su tienda solo actúa como seller de un pedido, no se mostrará el correo electrónico del cliente. Entendemos que la relación del cliente es con el marketplace, por lo que no es recomendable compartir sus datos con el seller sin consentimiento previo.
 
 ### Valor total
 
diff --git a/docs/tracks/es/sending-product-data-to-dafiti.md b/docs/tracks/es/sending-product-data-to-dafiti.md
index 356fe5ba1..a2fc2d5ea 100644
--- a/docs/tracks/es/sending-product-data-to-dafiti.md
+++ b/docs/tracks/es/sending-product-data-to-dafiti.md
@@ -23,9 +23,7 @@ Sigue estos pasos para realizar el mapeo:
 3. [Rellenar la plantilla de mapeo](#3-rellenar-la-plantilla-de-mapeo)
 4. [Cargar la plantilla de mapeo](#4-cargar-la-plantilla-de-mapeo)
 
-<div class="alert alert-warning">
-Para registrar un producto en VTEX, es obligatorio vincular el producto a una marca. Sin embargo, para evitar problemas con el envío de los productos, debes <a href="https://help.vtex.com/es/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke"> rellenar los nombres de las marcas aceptadas por Dafiti</a> en el campo <strong>Marca</strong> del producto que enviarás. Consulta el <a href="https://www.dafiti.com.co/marcas/">glosario de marcas</a> de Dafiti para conocer las marcas aceptadas.
-</div>
+>⚠️ Para registrar un producto en VTEX, es obligatorio vincular el producto a una marca. Sin embargo, para evitar problemas con el envío de los productos, debes [ rellenar los nombres de las marcas aceptadas por Dafiti](https://help.vtex.com/es/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) en el campo **Marca** del producto que enviarás. Consulta el [glosario de marcas](https://www.dafiti.com.co/marcas/) de Dafiti para conocer las marcas aceptadas.
 
 ## 1. Descargar la plantilla de consulta de Dafiti
 
@@ -55,9 +53,7 @@ El modelo de la plantilla de mapeo proporcionado se divide en tres pestañas:
 | **Attributenames** | Ejecuta la equivalencia entre el nombre del campo de la especificación en VTEX y el nombre de la variación/atributo en Dafiti. |
 | **Attributevalues** | Ejecuta la equivalencia entre los valores del campo de la especificación en VTEX y los valores de la variación/atributo en Dafiti. |
 
-<div class="alert alert-info">
-La plantilla de mapeo de Dafiti es case sensitive, es decir, distingue mayúsculas de minúsculas. Ten esto en cuenta al momento de rellenar la plantilla.
-</div>
+>ℹ️ La plantilla de mapeo de Dafiti es case sensitive, es decir, distingue mayúsculas de minúsculas. Ten esto en cuenta al momento de rellenar la plantilla.
 
 ### Categories
 
@@ -139,6 +135,4 @@ Después de rellenar la plantilla de mapeo de Dafiti, debes cargarla en el Admin
 
 Si no se ha producido ningún error en el envío, los productos se enviarán a Dafiti con sus respectivos atributos.
 
-<div class="alert alert-info">
-  La integración entre VTEX y Dafiti redimensiona automáticamente las fotos de los productos si son mayores que el tamaño solicitado por Dafiti (1000x1000).
-  </div>
+>ℹ️ La integración entre VTEX y Dafiti redimensiona automáticamente las fotos de los productos si son mayores que el tamaño solicitado por Dafiti (1000x1000).
diff --git a/docs/tracks/es/sending-products-to-amazon.md b/docs/tracks/es/sending-products-to-amazon.md
index 54a8f06af..0387f587a 100644
--- a/docs/tracks/es/sending-products-to-amazon.md
+++ b/docs/tracks/es/sending-products-to-amazon.md
@@ -18,17 +18,13 @@ Una vez realizada la configuración inicial de integración, ya puedes enviar lo
 
 Para enviar sus productos a Amazon, el seller debe mapear las [categorías](https://help.vtex.com/es/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) y los [atributos del producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).
 
-<div class="alert alert-info">
-Los productos deben tener el <a href="https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">stock</a> y los <a href="https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">precios</a> configurados antes de enviarlos a Amazon.
-</div>
+>ℹ️ Los productos deben tener el [stock](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) y los [precios](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) configurados antes de enviarlos a Amazon.
 
 ## Mapear categorías  
 
 El proceso de mapeo se puede realizar a través del [Admin VTEX](#mapeo-via-admin-vtex-(beta)), o mediante una [plantilla](#mapeo-mediante-plantilla). Consulta a continuación los detalles de cada caso.  
 
-<div class="alert alert-danger">
-Atención: si realizas el mapeo de una categoría a través del Admin VTEX, y anteriormente habías realizado el mapeo de esa misma categoría mediante una plantilla, se sobreescribirá el mapeo de la plantilla y no podrá recuperarse.
-</div>
+>❗ Atención: si realizas el mapeo de una categoría a través del Admin VTEX, y anteriormente habías realizado el mapeo de esa misma categoría mediante una plantilla, se sobreescribirá el mapeo de la plantilla y no podrá recuperarse.
 
 ### Mapeo vía Admin VTEX (beta)  
 
@@ -57,10 +53,10 @@ Para realizar el mapeo de categorías:
 
 5. Haz clic en el botón `Guardar cambios`.
 
-<div class="alert alert-danger">
-Los campos marcados con un asterisco * son obligatorios.
-<br>Al ingresar un atributo pueden activarse nuevos campos obligatorios que solo serán visibles en la página <b>Marketplace > Conexiones > Productos,</b> después de guardar el mapeo.</br>
-</div>
+>❗ Los campos marcados con un asterisco * son obligatorios.
+>
+>
+> Al ingresar un atributo pueden activarse nuevos campos obligatorios que solo serán visibles en la página **Marketplace > Conexiones > Productos,** después de guardar el mapeo.</br>
 
 ### Mapeo mediante plantilla 
 
@@ -183,9 +179,7 @@ La plantilla contiene las siguientes columnas:
 | F | VTEXValue | Nombre del valor utilizado en el campo SKU en VTEX |
 | G | AmazonValue | Nombre de los valores aceptados por Amazon |
 
-<div class="alert alert-info">
-La plantilla de mapeo de Amazon es case sensitive, es decir, distingue mayúsculas de minúsculas.
-</div>
+>ℹ️ La plantilla de mapeo de Amazon es case sensitive, es decir, distingue mayúsculas de minúsculas.
 
 Para cada producto, siga los pasos a continuación.
 
@@ -202,9 +196,7 @@ Para cada producto, siga los pasos a continuación.
 6. Rellene la columna **VTEXValue** con los valores del atributo del producto en VTEX
 7. Rellene la columna **AmazonValue** con los valores del atributo aceptados por Amazon. Para ver los valores aceptados por Amazon, ve a la [plantilla de atributos obligatorios de Amazon](#2-plantilla-de-atributos-de-amazon) y busca la pestaña `VALORES VÁLIDOS`.
 
-<div class="alert alert-warning">
-En algunos casos, los valores de <b>VariationTheme</b> pueden ser similares. Hay categorías en las que el <b>VariationTheme</b> puede ser: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, mientras en otras categorías puede ser: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. La diferencia está en el orden. En <i>SizeColor</i>, as casillas en la página del producto se ordenarán por tamaño y color, mientras que en <i>ColorSize</i> se ordenarán por color y tamaño. Tenga en cuenta los valores válidos de cada categoría que se va a mapear. 
-</div>
+>⚠️ En algunos casos, los valores de **VariationTheme** pueden ser similares. Hay categorías en las que el **VariationTheme** puede ser: <i>SizeColor</i>, <i>Color</i> e <i>Size</i>, mientras en otras categorías puede ser: <i>ColorSize</i>, <i>Color</i> e <i>Size</i>. La diferencia está en el orden. En <i>SizeColor</i>, as casillas en la página del producto se ordenarán por tamaño y color, mientras que en <i>ColorSize</i> se ordenarán por color y tamaño. Tenga en cuenta los valores válidos de cada categoría que se va a mapear.
 
 ##### Ejemplo de cómo rellenar la plantilla
 
diff --git a/docs/tracks/es/sending-products-to-facebook.md b/docs/tracks/es/sending-products-to-facebook.md
index dfc8ea931..90cd2e953 100644
--- a/docs/tracks/es/sending-products-to-facebook.md
+++ b/docs/tracks/es/sending-products-to-facebook.md
@@ -32,9 +32,7 @@ Si desea enviar los atributos de sus productos a Facebook, hay una etapa adicion
 
 La etapa adicional es la realización de un mapeo de las especificaciones de los productos. El mapeo permite la correspondencia entre los atributos registrados en su tienda VTEX y los estándares adoptados por Facebook.
 
-<div class="alert alert-warning">
-El mapeo de atributos por plantilla es opcional; sin embargo, si decide realizarlo debe efectuar todos los pasos que se describen en este artículo. De lo contrario, pueden producirse errores en la integración.
-</div>
+>⚠️ El mapeo de atributos por plantilla es opcional; sin embargo, si decide realizarlo debe efectuar todos los pasos que se describen en este artículo. De lo contrario, pueden producirse errores en la integración.
 
 ## Envío de atributos a Facebook
 
@@ -54,9 +52,7 @@ El primer paso para realizar el mapeo es descargar el archivo [Plantilla de mape
 
 El segundo paso para el mapeo es completar los datos en el archivo descargado. La plantilla consta de una sola pestaña, en la que se puede identificar cinco columnas.
 
-<div class="alert alert-info">
-La plantilla de mapeo de Facebook es case sensitive, es decir, distingue el uso de letras mayúsculas y minúsculas.
-</div>
+>ℹ️ La plantilla de mapeo de Facebook es case sensitive, es decir, distingue el uso de letras mayúsculas y minúsculas.
 
 - **Primera columna, ID Category:** se debe completar con el número de identificación de la categoría del producto en la plataforma VTEX. Puede encontrar el ID de una categoría en el Admin, en el módulo _Productos > Catálogo > Categorías_. El ID de la categoría es el número que se encuentra a la izquierda del nombre de la categoría.
 - **Segunda columna, VTEX attribute name:** debe contener el nombre del atributo registrado en VTEX.
@@ -65,9 +61,7 @@ La plantilla de mapeo de Facebook es case sensitive, es decir, distingue el uso
 - **Tercera columna, Facebook attribute name:** se debe completar con el término utilizado por Facebook que corresponde a cada atributo. 
 > Ejemplo: la correspondencia de Facebook para el atributo _Color_ es _Color_.
 
-  <div class="alert alert-info">
-Para conocer los nombres de los atributos y los valores de referencia, consulte la documentación de Facebook <a href="https://developers.facebook.com/docs/commerce-platform/catalog/fields?locale=es_LA#universal-basic-attributes">Universal Basic Attributes</a>. Si no hay ninguna correspondencia para un atributo o valor, complete la columna Facebook attribute name con el mismo término utilizado en VTEX.
-</div>
+  >ℹ️ Para conocer los nombres de los atributos y los valores de referencia, consulte la documentación de Facebook [Universal Basic Attributes](https://developers.facebook.com/docs/commerce-platform/catalog/fields?locale=es_LA#universal-basic-attributes). Si no hay ninguna correspondencia para un atributo o valor, complete la columna Facebook attribute name con el mismo término utilizado en VTEX.
 
 - **Cuarta columna, VTEX attribute value:** se debe completar con los valores de sus atributos en VTEX.
 > Ejemplo: supongamos que para el atributo _Género_ existe el valor _Femenino_ en su tienda VTEX. Por lo tanto, la columna VTEX attribute value se debe completar con la palabra _Femenino_. 
diff --git a/docs/tracks/es/sending-products-to-google-shopping.md b/docs/tracks/es/sending-products-to-google-shopping.md
index f18df8d33..6c396f06d 100644
--- a/docs/tracks/es/sending-products-to-google-shopping.md
+++ b/docs/tracks/es/sending-products-to-google-shopping.md
@@ -50,9 +50,7 @@ Algún producto podrá mostrar el error Insertion error: Ineligible SKU. Este me
 
 **Si algún producto es rechazado, debe revisar los datos y enviarlos nuevamente**. Puede realizar un seguimiento del status de sus productos en Google Merchant Center.
 
-<div class="alert alert-info">
-Asegúrese de que sus productos cumplen con las <a href="https://support.google.com/merchants/answer/7052112?visit_id=637492777706451215-3729304881&rd=1&hl=es-419">Especificaciones de datos de productos</a> definidas por Google. Si algún producto no cumple con los requisitos, el anuncio será rechazado.
-</div>
+>ℹ️ Asegúrese de que sus productos cumplen con las [Especificaciones de datos de productos](https://support.google.com/merchants/answer/7052112?visit_id=637492777706451215-3729304881&rd=1&hl=es-419) definidas por Google. Si algún producto no cumple con los requisitos, el anuncio será rechazado.
 
 En algunas circunstancias el rechazo del producto sucede después de que se ha considerado como activo. A veces esto ocurre cuando una cuenta ha sido creada recientemente.
 
@@ -66,9 +64,7 @@ En Google Shopping, los productos caducan automáticamente si no se actualizan e
 
 Sin embargo, no es algo que le deba preocupar ya que en la integración con la plataforma VTEX, **el sistema actualiza los productos automáticamente cada 29 días.**
 
-<div class="alert alert-info">
-Puede haber un retraso de hasta 30 minutos entre que se procesa el cambio de los datos de un producto y la actualización en el _feed_.
-</div>
+>ℹ️ Puede haber un retraso de hasta 30 minutos entre que se procesa el cambio de los datos de un producto y la actualización en el _feed_.
 
 ## Modificar la categorización automática
 
@@ -80,6 +76,4 @@ Pero antes de considerar un problema en la categorización, asegúrese de que su
 
 Para reemplazar una categoría incorrecta y asegurarse de que el producto sea aprobado, consulte las instrucciones en el artículo de Google [categoría producto Google](https://support.google.com/merchants/answer/6324436?hl=es-419). 
 
-<div class="alert alert-warning">
-Google aceptará un cambio de categoría solo en las situaciones previstas en el artículo <a href="https://support.google.com/merchants/answer/6324436?hl=pt-BR">categoría producto Google.</a>
-</div>
+>⚠️ Google aceptará un cambio de categoría solo en las situaciones previstas en el artículo [categoría producto Google.](https://support.google.com/merchants/answer/6324436?hl=pt-BR)
diff --git a/docs/tracks/es/setting-up-a-marketplace-trade-policy.md b/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
index b2b790b96..9858627a5 100644
--- a/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/es/setting-up-a-marketplace-trade-policy.md
@@ -41,9 +41,7 @@ Para definir el catálogo de productos que será enviado al marketplace, el admi
 6. Marque el flag __Tiendas__ para las políticas comerciales elegidas.
 7. Haga clic en __Guardar__.
 
-<div class="alert alert-danger">
-VTEX no recomienda realizar la gestión de catálogo de productos para marketplace a través de colecciones. Este mecanismo genera muchas complejidades en la organización, siendo recomendada la gestión a través del flag tiendas.
-</div>
+>❗ VTEX no recomienda realizar la gestión de catálogo de productos para marketplace a través de colecciones. Este mecanismo genera muchas complejidades en la organización, siendo recomendada la gestión a través del flag tiendas.
 
 ## Definiendo la logística
 
diff --git a/docs/tracks/es/setting-up-a-smart-campaign.md b/docs/tracks/es/setting-up-a-smart-campaign.md
index c49d8f0ff..bb942e3df 100644
--- a/docs/tracks/es/setting-up-a-smart-campaign.md
+++ b/docs/tracks/es/setting-up-a-smart-campaign.md
@@ -30,12 +30,8 @@ Siga este paso a paso para configurarla:
     <br/>&bull; __Definir un retorno de la inversión en publicidad (ROAS) deseado:__ al marcar esta flag usted deberá definir qué ROAS debe perseguir la campaña.
     <br/>_`Ejemplo:` si usted establece un ROAS de 800%, significa que, para cada $ 1,00 gastado en la campaña ella debe convertir $ 8,00._
 
-<div class="alert alert-warning">
-<strong>NB: no se recomienda configurar un ROAS</strong> al iniciar una campaña por primera vez. Esto es porque la campaña necesita un tiempo para aprender a entregar sus productos en las búsquedas y esto puede tardar hasta 4 semanas, según Google. Entonces, hasta que esté madura es recomendable no configurar un ROAS.
-</div>
+>⚠️ **NB: no se recomienda configurar un ROAS** al iniciar una campaña por primera vez. Esto es porque la campaña necesita un tiempo para aprender a entregar sus productos en las búsquedas y esto puede tardar hasta 4 semanas, según Google. Entonces, hasta que esté madura es recomendable no configurar un ROAS.
 
-<div class="alert alert-warning">
-<strong>NB 2:</strong> también recomendamos que la configuración de la campaña <strong>no se cambie</strong> durante las primeras 4 semanas, justamente por el tiempo que la inteligencia artificial lleva para aprender.
-</div>
+>⚠️ **NB 2:** también recomendamos que la configuración de la campaña **no se cambie** durante las primeras 4 semanas, justamente por el tiempo que la inteligencia artificial lleva para aprender.
 
 *__Listo!__ Ahora usted ya tiene su campaña configurada y, dentro de unos días, debe comenzar a ver resultados en el dashboard de la app.*
diff --git a/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
index 757d20372..a627774dd 100644
--- a/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/es/setting-up-app-linking-for-payments-app-in-instore.md
@@ -36,9 +36,7 @@ Si es necesario, inStore puede enviar información adicional. Ejemplo con el sub
 - `administrativePassword`: string - contraseña predeterminada, por ejemplo, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-Para crear cualquier configuración extra, usted debe enviar al equipo de inStore (instoredevs@vtex.com) los extras que la aplicación necesita para completar la transacción. Así, crearemos un formulario en el Pagos para que el cliente pueda configurar su adquirente.
-</div>
+>ℹ️ Para crear cualquier configuración extra, usted debe enviar al equipo de inStore (instoredevs@vtex.com) los extras que la aplicación necesita para completar la transacción. Así, crearemos un formulario en el Pagos para que el cliente pueda configurar su adquirente.
 
 ## URI de envío y URI de respuesta para cada acción
 
@@ -123,9 +121,8 @@ URI final que la aplicación de pago recibirá para ejecutar la acción de reemb
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&autoConfirm=True&sellerName=instoreqa&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class="alert alert-warning">>
-<strong>NOTA:</strong> No todos los parámetros serán utilizados por todos los adquirentes/apps de pago. Ejemplo: <code>transactionId</code>. Este parámetro es el ID de una transacción en VTEX que identifica todos los pagos de un pedido completo en el PCI Gateway de VTEX. Una transacción puede contener varios pagos, como cuando un pedido se paga con varias tarjetas de crédito o débito.
-</div>
+>⚠️ >
+> **NOTA:** No todos los parámetros serán utilizados por todos los adquirentes/apps de pago. Ejemplo: `transactionId`. Este parámetro es el ID de una transacción en VTEX que identifica todos los pagos de un pedido completo en el PCI Gateway de VTEX. Una transacción puede contener varios pagos, como cuando un pedido se paga con varias tarjetas de crédito o débito.
 
 ## Ejemplos de URI de respuesta para cada acción
 
@@ -185,9 +182,8 @@ Para que la integración funcione, es necesario que el cliente configure en el P
 
 La integración de AppLinking no incluye otras dependencias, ya que la comunicación entre la app inStore y la appp de pago se realiza con URIs específicas que contienen todos los parámetros de configuración y pago necesarios para la acción.
 
-<div class="alert alert-warning">>
-En Android, toda comunicación debe suceder con un nuevo <code>Intent</code>. Esto significa que usted no debe enviar la respuesta como un retorno de llamada del <code>Intent</code> inicial. En su lugar, debe enviar un nuevo <code>Intent</code> a la aplicación inStore con la respuesta anterior.
-</div>
+>⚠️ >
+> En Android, toda comunicación debe suceder con un nuevo `Intent`. Esto significa que usted no debe enviar la respuesta como un retorno de llamada del `Intent` inicial. En su lugar, debe enviar un nuevo `Intent` a la aplicación inStore con la respuesta anterior.
 
 Para configurar el conector de InStore, usteddebe seguir estos pasos:
 
diff --git a/docs/tracks/es/setting-up-instore-as-a-pos.md b/docs/tracks/es/setting-up-instore-as-a-pos.md
index 7b3e36291..8b2cbbd8d 100644
--- a/docs/tracks/es/setting-up-instore-as-a-pos.md
+++ b/docs/tracks/es/setting-up-instore-as-a-pos.md
@@ -22,9 +22,7 @@ En primer lugar, consideremos los requisitos previos que su tienda necesita. Con
 
 ## Implementar inStore como TPV
 
-<div class="alert alert-info">
-Aunque es posible implementar inStore como TPV de otras formas, en este artículo explicaremos cómo hacerlo utilizando las features de Cuenta Franquicia y Seller White Label. Esto se debe a que esta es la arquitectura más recomendada por VTEX para este tipo de proyecto.
-</div>
+>ℹ️ Aunque es posible implementar inStore como TPV de otras formas, en este artículo explicaremos cómo hacerlo utilizando las features de Cuenta Franquicia y Seller White Label. Esto se debe a que esta es la arquitectura más recomendada por VTEX para este tipo de proyecto.
 
 Estos son los pasos para implementar inStore como TPV:
 
diff --git a/docs/tracks/es/setting-up-pix.md b/docs/tracks/es/setting-up-pix.md
index 03a824c9c..53eb1c52c 100644
--- a/docs/tracks/es/setting-up-pix.md
+++ b/docs/tracks/es/setting-up-pix.md
@@ -14,6 +14,4 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugES: instore-pagos
 ---
 
-<div class="alert alert-warning">
-<p>Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.</p>
-</div>
+>⚠️ Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
diff --git a/docs/tracks/es/setting-up-the-ads-template-description-in-mercado-livre.md b/docs/tracks/es/setting-up-the-ads-template-description-in-mercado-livre.md
index f65dbf9d0..cfc067cfe 100644
--- a/docs/tracks/es/setting-up-the-ads-template-description-in-mercado-livre.md
+++ b/docs/tracks/es/setting-up-the-ads-template-description-in-mercado-livre.md
@@ -18,9 +18,7 @@ En la integración con Mercado Libre, usted puede hacer la descripción de sus a
 
 ## Configuración del template
 
-<div class="alert alert-danger">
-Mercado Libre <strong>no acepta personalizaciones de template en HTML o CSS</strong> (con excepción del tag &lt;br&gt; para saltos de línea). No se permiten tags de Iframes, Scripts, Forms, Inputs, Meta, Object y Embed.
-</div>
+>❗ Mercado Libre **no acepta personalizaciones de template en HTML o CSS** (con excepción del tag &lt;br&gt; para saltos de línea). No se permiten tags de Iframes, Scripts, Forms, Inputs, Meta, Object y Embed.
 
 Para que su producto esté disponible en Mercado Libre, es necesario configurar el template del anuncio donde el producto se mostrará. Para hacer la configuración, realice el siguiente procedimiento:
 
@@ -44,9 +42,7 @@ Si desea incluir todos los atributos y valores de los atributos en el template,
 
 ``{{#each ATRIBUTOS}} {{NOME}} – {{VALOR}} <br> {{/each}}``
 
-<div class="alert alert-info">
-Si desea omitir algún atributo en el template, usted puede hacer esto en la <strong>configuración de la integración</strong>, rellenando el campo <strong>Atributos omitidos en el template del producto</strong>, como se explica en la sección <strong>Configurar el panel de Mercado Libre en VTEX</strong> de la etapa anterior.
-</div>
+>ℹ️ Si desea omitir algún atributo en el template, usted puede hacer esto en la **configuración de la integración**, rellenando el campo **Atributos omitidos en el template del producto**, como se explica en la sección **Configurar el panel de Mercado Libre en VTEX** de la etapa anterior.
 
 Usted ha terminado la __tercera etapa__. Ahora, vamos a configurar la logística para las entregas de pedidos hechos en Mercado Libre.
 
diff --git a/docs/tracks/es/setting-up-the-app.md b/docs/tracks/es/setting-up-the-app.md
index ebd04fb0e..897b84781 100644
--- a/docs/tracks/es/setting-up-the-app.md
+++ b/docs/tracks/es/setting-up-the-app.md
@@ -52,9 +52,7 @@ Activar esta opción permite completar una compra incluso si su valor excede el
 
 Por ejemplo, para una cuenta creada con un límite de crédito de $1.000,00 y una tolerancia del 10%, el cliente podrá realizar un pedido con un valor máximo de $1.100,00 utilizando Customer Credit como método de pago. Si el cliente desea utilizar el crédito para pagar un pedido por valor de $1.250,00, el sistema no permitirá completar la compra.
 
-<div class="alert alert-warning">
-Los valores de tolerancia se configuran en números decimales, donde 0 representa el 0% y 1 representa el 100%. Ejemplo: para utilizar una tolerancia del 5%, el valor a configurar es 0,05.
-</div>
+>⚠️ Los valores de tolerancia se configuran en números decimales, donde 0 representa el 0% y 1 representa el 100%. Ejemplo: para utilizar una tolerancia del 5%, el valor a configurar es 0,05.
 
 ![CC_Configuracion_2_ES](https://images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/c87641a0ebdb835abfb632fcc2ebff90/CC_Configuracion_2_ES.JPG)
 
@@ -76,9 +74,7 @@ El cliente puede acceder a esta página en el sitio web de su tienda en __Mi Cue
 
 Esta configuración permite insertar instrucciones relacionadas con el pago en las facturas emitidas por Customer Credit. Para editar el mensaje que se mostrará en la factura, ingrese la información en el cuadro de texto y haga clic en `Actualizar`.
 
-<div class="alert alert-warning">
-El mensaje registrado en esta configuración se replicará en todos las facturas emitidas para todas las cuentas de clientes de Customer Credit. No es posible configurar un mensaje único para cada cliente o factura específica.
-</div>
+>⚠️ El mensaje registrado en esta configuración se replicará en todos las facturas emitidas para todas las cuentas de clientes de Customer Credit. No es posible configurar un mensaje único para cada cliente o factura específica.
 
 ![CC_Configuracion_5_ES](https://images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/791355858bde3d7fa86eaa8b142b56e9/CC_Configuracion_5_ES.JPG)
 
@@ -109,6 +105,4 @@ Para crear condiciones de pago para títulos de Customer Credit, siga los pasos
 
 <blockquote><ui>8. Clic en <b>Guardar</b>.</ui>
 
-<div class="alert alert-warning">
-No es posible establecer una tasa de interés para una condición de pago creada con una sola cuota. 
-</div>
+>⚠️ No es posible establecer una tasa de interés para una condición de pago creada con una sola cuota.
diff --git a/docs/tracks/es/setting-up-the-cappta-acquirer-for-instore.md b/docs/tracks/es/setting-up-the-cappta-acquirer-for-instore.md
index c60daf2a2..32fc4d844 100644
--- a/docs/tracks/es/setting-up-the-cappta-acquirer-for-instore.md
+++ b/docs/tracks/es/setting-up-the-cappta-acquirer-for-instore.md
@@ -18,17 +18,14 @@ Para permitir transacciones a través de máquinas de tarjetas con inStore, uste
 
 __Cappta__ es una sub-adquirente homologado por inStore en Brasil.
 
-<div class="alert alert-warning">
-Si desea utilizar Cappta en un país diferente o si desea utilizar otro adquiriente que no esté homologado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo <a href="https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod"> Integrar el inStore a un nuevo adquirente de pago</a>.
-</div>
-
-<div class="alert alert-info">
-Actualmente, Cappta es compatible con las siguientes plataformas y dispositivos:
-<ol>
-<li>Windows 8 o superior, con máquina de tarjeta USB Ingenico</li>
-<li>Android</li>
-</ol>
-</div>
+>⚠️ Si desea utilizar Cappta en un país diferente o si desea utilizar otro adquiriente que no esté homologado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo [ Integrar el inStore a un nuevo adquirente de pago](https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
+
+>ℹ️ Actualmente, Cappta es compatible con las siguientes plataformas y dispositivos:
+>
+> Windows 8 o superior, con máquina de tarjeta USB Ingenico
+>
+> Android
+> 
 
 Antes de instalar la aplicación Cappta, asegúrese de haber completado el paso anterior de configuración del módulo de Pagos. Si ha completado este paso, siga los pasos a continuación para instalar y configurar el adquirente Cappta para el inStore.
 
@@ -49,9 +46,7 @@ Actualmente, la integración funciona para sistemas Android y Windows. Si elige
 - **Android**: el flujo de configuración de la aplicación es el mismo que cualquier otra aplicación instalada en un smartphone o tablet. Abra la aplicación e ingrese la información de acceso (CNPJ, POS, Contraseña). Si no conoce esta información, comuníquese con Cappta.
 - **Windows**: para configurar, ejecute el archivo .exe y complete la información de acceso (CNPJ, POS, Contraseña). Si no conoce esta información, comuníquese con Cappta.
 
-<div class="alert alert-warning">
-Debe asegurarse de que la opción <strong>pago web</strong> esté habilitada en su cuenta de Cappta.
-</div>
+>⚠️ Debe asegurarse de que la opción **pago web** esté habilitada en su cuenta de Cappta.
 
 ## Empareje la máquina de tarjetas
 
diff --git a/docs/tracks/es/setting-up-the-cielo-lio-acquirer-for-instore.md b/docs/tracks/es/setting-up-the-cielo-lio-acquirer-for-instore.md
index 8c061bee1..d0c1a8b82 100644
--- a/docs/tracks/es/setting-up-the-cielo-lio-acquirer-for-instore.md
+++ b/docs/tracks/es/setting-up-the-cielo-lio-acquirer-for-instore.md
@@ -18,13 +18,9 @@ Para permitir transacciones a través de máquinas de tarjetas usando inStore, u
 
 __Cielo LIO__ es un adquirente homologado por inStore en Brasil.
 
-<div class="alert alert-warning">
-Si desea utilizar Cielo LIO en un país diferente o si desea utilizar otro adquiriente que no está homologado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo <a href="https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod"> Integrar inStore con un nuevo adquiriente de pagos</a>.
-</div>
+>⚠️ Si desea utilizar Cielo LIO en un país diferente o si desea utilizar otro adquiriente que no está homologado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo [ Integrar inStore con un nuevo adquiriente de pagos](https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Actualmente, Cielo LIO solo es compatible con sistemas Android. Es posible usar CieloLio V2 o CieloLio+.
-</div>
+>ℹ️ Actualmente, Cielo LIO solo es compatible con sistemas Android. Es posible usar CieloLio V2 o CieloLio+.
 
 Antes de instalar la aplicación Cielo LIO, asegúrese de haber completado el paso anterior de configuración del módulo de Pagos. Si lo ha terminado, siga los pasos a continuación para instalar y configurar el adquirente Cielo LIO para inStore.
 
diff --git a/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md b/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md
index 1d0d15085..62c1123f4 100644
--- a/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md
+++ b/docs/tracks/es/setting-up-the-logistics-for-mercado-livre.md
@@ -23,9 +23,7 @@ Las modalidades de envío son dos:
 - [Mercado Envíos 1 (ME1)](#mercado-envios-1-me1)
 - [Mercado Envíos (ME2)](#mercado-envios-2-me2)
 
-<div class="alert alert-warning">
-Debes tener un SLA configurado en VTEX independientemente de la modalidad de envío que utilizas en tu tienda. Si no se configura la modalidad, los pedidos realizados en Mercado Libre no se integrará a la plataforma VTEX.
-</div>
+>⚠️ Debes tener un SLA configurado en VTEX independientemente de la modalidad de envío que utilizas en tu tienda. Si no se configura la modalidad, los pedidos realizados en Mercado Libre no se integrará a la plataforma VTEX.
 
 ## Mercado Envíos 1 (ME1)
 
@@ -71,9 +69,7 @@ Algunos tipos de logística tienen la obligación de enviar una factura o config
 - [Flex](#flex)
 - [Mercado Envíos Full](#mercado-envios-full)
 
-<div class="alert alert-info">
-Para segmentar qué tipo de envío utiliza la tienda, es necesario crear un <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106"><i>atributo de producto</i></a> con el nombre <code>meli_shipping_mode</code>, donde estará completado si es ME1 o ME2.
-</div>
+>ℹ️ Para segmentar qué tipo de envío utiliza la tienda, es necesario crear un [<i>atributo de producto</i>](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106) con el nombre `meli_shipping_mode`, donde estará completado si es ME1 o ME2.
 
 ### Drop Off
 
@@ -109,7 +105,7 @@ En el tipo *[Flex](https://envios.mercadolibre.com.ar/mercado-envios-flex)*, el
 
 Todos los ajustes se realizan dentro de la plataforma de Mercado Libre.
 
-<div class="alert alert-info">Esta modalidad solo está disponible para los pedidos realizados en la misma ciudad que el seller.</div>
+>ℹ️ Esta modalidad solo está disponible para los pedidos realizados en la misma ciudad que el seller.
 
 ### Mercado Envios Full
 
@@ -117,9 +113,9 @@ Todos los ajustes se realizan dentro de la plataforma de Mercado Libre.
 
 Puede integrar este servicio a su tienda a través del [registro de un stock](https://help.vtex.com/es/tutorial/gerenciar-estoque) destinado exclusivamente para Mercado Envíos Full. Esa integración permite hacer seguimiento al nivel del stock, ya que la cantidad de productos se actualiza automáticamente a medida que se realizan las ventas mediante Mercado Libre Full.
 
-<div class="alert alert-danger">
-Si el vendedor elige el modelo logístico <b>Mercado Envíos Full</b>, es necesario seguir el siguiente orden de configuración: <p><ol><a href="#configurando-el-modelo-de-envio">Configurar modelo de envío</a> <br><a href="#configurar-mercado-envios-full">Configurar Mercado Envíos Full</a></br></ol></p>
-</div>
+>❗ Si el vendedor elige el modelo logístico **Mercado Envíos Full**, es necesario seguir el siguiente orden de configuración: [Configurar modelo de envío](#configurando-el-modelo-de-envio) 
+>
+> [Configurar Mercado Envíos Full](#configurar-mercado-envios-full)</br>
 
 #### Configurando Mercado Envíos Full
 
@@ -138,9 +134,7 @@ Después de definir qué modelo de envío se utilizará para la integración de
 
 Para crear un campo de producto, sigue las instrucciones del tutorial [Registrar especificaciones o campos de producto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
 
-<div class="alert alert-warning">
- El nombre del campo creado debe ser "meli_shipping_mode" y el valor del campo debe ser completado como "me1" o "me2". Si el nombre del campo o el valor es diferente, la integración no reconocerá el atributo. 
-</div>
+>⚠️ El nombre del campo creado debe ser "meli_shipping_mode" y el valor del campo debe ser completado como "me1" o "me2". Si el nombre del campo o el valor es diferente, la integración no reconocerá el atributo.
 
 ## Cómo consultar las facturas de Mercado Libre mediante API
 
diff --git a/docs/tracks/es/setting-up-the-order-summary-printing.md b/docs/tracks/es/setting-up-the-order-summary-printing.md
index c77b748a9..96922b26c 100644
--- a/docs/tracks/es/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/es/setting-up-the-order-summary-printing.md
@@ -25,9 +25,7 @@ Se requieren dos pasos:
 
 ## Habilite la opción de configuración del dispositivo
 
-<div class="alert alert-danger">
-La habilitación de la opción de configuración del dispositivo se realiza mediante un cambio en el archivo JavaScript <code>checkout-instore-custom.js</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
-</div>
+>❗ La habilitación de la opción de configuración del dispositivo se realiza mediante un cambio en el archivo JavaScript `checkout-instore-custom.js`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en este archivo pueden causar errores críticos.
 
 Primero, abra el archivo `checkout-instore-custom.js`, disponible en el Admin de su cuenta VTEX (si no sabe cómo acceder a este archivo, consulte el tutorial [Cómo personalizar el inStore](https://help.vtex.com/es/tracks/instore-customizacoes--1z9kBm12oBPyVNDo1ivVc2)).
 
@@ -44,17 +42,13 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-No elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ No elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
 
 Este cambio hará que la opción __Configurar dispositivo__ aparezca en el menú principal de inStore, como se muestra en la imagen a continuación. Es a través de esta opción que configuraremos la impresora.
 
 ![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
-<div class="alert alert-info">
-<strong>Nota:</strong> hay una opción para imprimir automáticamente el resumen del pedido tan pronto como se complete el pedido. Para habilitarla, agregue la propiedad <code>printPageAutomatically</code> con el valor <code>true</code> dentro del objeto <code>printingConfig</code>. Vea a continuación cómo se vería el código en este caso.
-</div>
+>ℹ️ **Nota:** hay una opción para imprimir automáticamente el resumen del pedido tan pronto como se complete el pedido. Para habilitarla, agregue la propiedad `printPageAutomatically` con el valor `true` dentro del objeto `printingConfig`. Vea a continuación cómo se vería el código en este caso.
 
 ```json
 window.INSTORE_CONFIG = { 
@@ -66,17 +60,13 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Nuevamente, no elimine ninguna de las otras propiedades presentes en el objeto <code>window.INSTORE_CONFIG</code>, para evitar romper otras funciones.
-</div>
+>❗ Nuevamente, no elimine ninguna de las otras propiedades presentes en el objeto `window.INSTORE_CONFIG`, para evitar romper otras funciones.
 
 ## Configure el dispositivo de impresora en inStore
 
 Ahora veamos cómo configurar una impresora conectada a inStore para imprimir resúmenes de pedidos.
 
-<div class="alert alert-warning">
-En primer lugar, para conectar una impresora al sistema de inStore, es necesario tener un par de credenciales VTEX (AppKey y AppToken) con los permisos de acceso adecuados. Recomendamos que el perfil de acceso vinculado a estas credenciales sea <code>inStore Sales Person</code>. Sin embargo, también se puede usar un perfil con más poderes, como Admin Super.
-</div>
+>⚠️ En primer lugar, para conectar una impresora al sistema de inStore, es necesario tener un par de credenciales VTEX (AppKey y AppToken) con los permisos de acceso adecuados. Recomendamos que el perfil de acceso vinculado a estas credenciales sea `inStore Sales Person`. Sin embargo, también se puede usar un perfil con más poderes, como Admin Super.
 
 Con AppKey y AppToken en mano, siga los pasos a continuación:
 
diff --git a/docs/tracks/es/setting-up-the-pagar-me-acquirer-for-instore.md b/docs/tracks/es/setting-up-the-pagar-me-acquirer-for-instore.md
index a532c1cd6..58db83223 100644
--- a/docs/tracks/es/setting-up-the-pagar-me-acquirer-for-instore.md
+++ b/docs/tracks/es/setting-up-the-pagar-me-acquirer-for-instore.md
@@ -18,13 +18,9 @@ Para permitir transacciones a través de máquinas de tarjetas usando inStore, u
 
 __Pagar.me__ es un sub-adquirente homologado por inStore en Brasil.
 
-<div class="alert alert-warning">
-Si desea utilizar Pagar.me en un país diferente o si desea utilizar otro adquiriente que no esté certificado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo <a href="https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrar el inStore con un nuevo adquiriente de pagos</a>.
-</div>
+>⚠️ Si desea utilizar Pagar.me en un país diferente o si desea utilizar otro adquiriente que no esté certificado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo [Integrar el inStore con un nuevo adquiriente de pagos](https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Actualmente, el Pagar.me solo es compatible con los sistemas <b>Android</b>, con máquinas de tarjetas <b>Gertec MOBIPIN</b>.
-</div>
+>ℹ️ Actualmente, el Pagar.me solo es compatible con los sistemas **Android**, con máquinas de tarjetas **Gertec MOBIPIN**.
 
 Antes de instalar la aplicación de Pagar.me, asegúrese de haber completado el paso anterior de configuración del módulo Pagos. Si lo ha terminado, siga los pasos a continuación para instalar y configurar el adquirente Pagar.me para el inStore.
 
diff --git a/docs/tracks/es/setting-up-the-sitef-acquirer-for-instore.md b/docs/tracks/es/setting-up-the-sitef-acquirer-for-instore.md
index b02f375ec..637080f7b 100644
--- a/docs/tracks/es/setting-up-the-sitef-acquirer-for-instore.md
+++ b/docs/tracks/es/setting-up-the-sitef-acquirer-for-instore.md
@@ -14,21 +14,15 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugES: configurar-el-adquirente-sitef-para-el-instore
 ---
 
-<div class="alert alert-warning">
-Es importante señalar que la integración con SiTef es una solución certificado, pero aún no se ha probado a gran escala.
-</div>
+>⚠️ Es importante señalar que la integración con SiTef es una solución certificado, pero aún no se ha probado a gran escala.
 
 Para permitir transacciones a través de máquinas de tarjetas usando el inStore, usted necesita un adquiriente o un sub-adquirente para procesar sus pagos.
 
 __SiTef__ es un sub-adquirente homologado por inStore en Brasil.
 
-<div class="alert alert-warning">
-Si desea utilizar SiTef en un país diferente o si desea utilizar otro adquiriente que no esté certificado actualmente, deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo <a href="https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrar el inStore con un nuevo adquiriente de pagos</a>.
-</div>
+>⚠️ Si desea utilizar SiTef en un país diferente o si desea utilizar otro adquiriente que no esté certificado actualmente, deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo [Integrar el inStore con un nuevo adquiriente de pagos](https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Actualmente, SiTef es compatible con los sistemas <b>Android</b> e <b>iOS</b>, con máquinas de tarjetas Ingenico o cualquier otra máquina certificada por SiTef.
-</div>
+>ℹ️ Actualmente, SiTef es compatible con los sistemas **Android** e **iOS**, con máquinas de tarjetas Ingenico o cualquier otra máquina certificada por SiTef.
 
 Antes de instalar la aplicación SiTef, asegúrese de haber completado el paso anterior de configuración del módulo de Pagos.
 
@@ -55,15 +49,17 @@ GSURF es una compañía que ofrece un servidor SiTef a través de VPN. Esto hace
 
 Al configurar el conector SiTef, disponible en VTEX Payments, deberá especificar `GSURF.SSL` como protocolo para que la aplicación VTEX SiTef envíe transacciones al servidor remoto.
 
-<div class="alert alert-warning">
-<strong>Importante:</strong>: cuando utilice GSURF como protocolo, asegúrese de que su red permita los siguientes accesos:<br>
-<b>Versiones de firewall (solo tráfico saliente):</b>
-<ol>
-<li><b>Rango de IP:</b> 187.103.176.0/20 189.85.171.160/28 18.231.194.64/26</li>
-<li><b>Puertos:</b> UDP-443; TCP-443; TCP-55844; TCP-55845</li>
-<li><b>DNS LOCAL:</b> UDP-53 (resolución de nombre en gsurfnet.com)</li>
-</ol>
-</div>
+>⚠️ **Importante:**: cuando utilice GSURF como protocolo, asegúrese de que su red permita los siguientes accesos:
+>
+> 
+> **Versiones de firewall (solo tráfico saliente):**
+>
+> **Rango de IP:** 187.103.176.0/20 189.85.171.160/28 18.231.194.64/26
+>
+> **Puertos:** UDP-443; TCP-443; TCP-55844; TCP-55845
+>
+> **DNS LOCAL:** UDP-53 (resolución de nombre en gsurfnet.com)
+> 
 
 ### Servidor local
 
diff --git a/docs/tracks/es/setting-up-the-stone-acquirer-for-instore.md b/docs/tracks/es/setting-up-the-stone-acquirer-for-instore.md
index 3e9f03351..20c63587d 100644
--- a/docs/tracks/es/setting-up-the-stone-acquirer-for-instore.md
+++ b/docs/tracks/es/setting-up-the-stone-acquirer-for-instore.md
@@ -18,13 +18,9 @@ Para permitir transacciones a través de máquinas de tarjetas usando el inStore
 
 __Stone__ es un sub-adquirente homologado por inStore en Brasil.
 
-<div class="alert alert-info">
-Si desea utilizar Stone en un país diferente o si desea utilizar otro adquiriente que no esté homologado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo <a href="https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrar el inStore con un nuevo adquiriente de pagos</a>.
-</div>
+>ℹ️ Si desea utilizar Stone en un país diferente o si desea utilizar otro adquiriente que no esté homologado actualmente, usted deberá crear la integración con la aplicación de ese adquiriente. Para hacerlo, consulte el artículo [Integrar el inStore con un nuevo adquiriente de pagos](https://help.vtex.com/es/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Actualmente, Stone solo es compatible con sistemas <b>Android</b>, con máquinas de tarjetas <b>Gertec GPOS700</b>. Para otras máquinas de tarjetas, Stone recomienda usar el <a href="https://help.vtex.com/es/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/1obqdkoH82yFWtaMbwcJKx">Pagar.me</a>.
-</div>
+>ℹ️ Actualmente, Stone solo es compatible con sistemas **Android**, con máquinas de tarjetas **Gertec GPOS700**. Para otras máquinas de tarjetas, Stone recomienda usar el [Pagar.me](https://help.vtex.com/es/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/1obqdkoH82yFWtaMbwcJKx).
 
 Antes de instalar la aplicación Stone, asegúrese de haber completado el paso anterior de configuración del módulo de Pagos.
 
diff --git a/docs/tracks/es/settings.md b/docs/tracks/es/settings.md
index 2c4bd1fc5..531115c76 100644
--- a/docs/tracks/es/settings.md
+++ b/docs/tracks/es/settings.md
@@ -22,15 +22,11 @@ VTEX utiliza dos proveedores de CDN para las tiendas: **Cloudfront** y **Azion**
 
 Por lo tanto, si tienes el dominio de la tienda registrado en la plataforma **Cloudfront** o **Azion**, remueve el registro antes de apuntar el DNS a VTEX.
 
-<div class="alert alert-warning">
-Si no puedes remover el registro de dominio de tu tienda de la plataforma <strong>Cloudfront</strong> o <strong>Azion</strong>, ponte en contacto con el <a href="https://help.vtex.com/es/support">equipo de soporte de VTEX</a> y explícales la situación. Así, el equipo VTEX te ayudará a asegurar el buen funcionamiento de la tienda en el go-live.
-</div>
+>⚠️ Si no puedes remover el registro de dominio de tu tienda de la plataforma **Cloudfront** o **Azion**, ponte en contacto con el [equipo de soporte de VTEX](https://help.vtex.com/es/support) y explícales la situación. Así, el equipo VTEX te ayudará a asegurar el buen funcionamiento de la tienda en el go-live.
 
 ## Configurar registros CAA
 
-<div class="alert alert-warning">
-La configuración de registros CAA según se describe en esta sección, solo es necesaria si tu servidor de DNS tiene un registro CAA. Si no, pasa al tema siguiente de esta guía.
-</div>
+>⚠️ La configuración de registros CAA según se describe en esta sección, solo es necesaria si tu servidor de DNS tiene un registro CAA. Si no, pasa al tema siguiente de esta guía.
 
 Los registros CAA indican qué autoridades de certificación (CA) están autorizadas para generar y renovar los certificados que validan la identidad de tu dominio. La configuración adecuada de los registros es necesaria para poder generar los [certificados SSL](https://help.vtex.com/es/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar--tutorials_1308) y utilizar la CDN de VTEX.
 
@@ -44,9 +40,7 @@ Esto significa que la autoridad de certificación **Let's Encrypt** puede emitir
 
 Otra alternativa, aunque no recomendada, sería no incluir registros CAA en tu servidor DNS, lo que indicaría que todas las autoridades de certificación pueden emitir y renovar certificados para tu dominio.
 
-<div class="alert alert-info">
-Puede que estos tipos de entrada no estén disponibles en la interfaz de tu gestor de DNS; sin embargo, muchas veces es posible gestionarlos a través de llamadas en el soporte de la herramienta específica.
-</div>
+>ℹ️ Puede que estos tipos de entrada no estén disponibles en la interfaz de tu gestor de DNS; sin embargo, muchas veces es posible gestionarlos a través de llamadas en el soporte de la herramienta específica.
 
 Para facilitar el trabajo de crear y verificar tus registros CAA, puedes utilizar [CAA Record Helper de SSLMate](https://sslmate.com/caa/). El programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) también puede ayudar a verificar los registros mediante el comando `dig domain.com CAA`; el status `SERVFAIL` puede indicar que tu servidor DNS no está en cumplimiento.
 
diff --git a/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
index 91de93c59..9da92a2c0 100644
--- a/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/es/sharing-shopping-cart-using-instore-social-selling.md
@@ -41,9 +41,7 @@ Vea el paso a paso que se muestra a continuación.
 
 El vendedor puede enviar el mismo enlace a varios clientes, tantas veces como lo desee. Cada vez que una persona acceda a este enlace, se generará un nuevo carrito de compra, exactamente igual al creado en VTEX Sales App. Cada carrito al que se accede también está asociado a la cuenta del vendedor y, si existe, al código del vendedor.
 
-<div class="alert alert-info">
-<p>Si el código de vendedor está activado, se le pide que lo rellene antes de compartir el carrito. Para obtener más información sobre el código de vendedor, visite la guía <a href="https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/Rby973h1l9tEM4C1YrzwZ">Personalización de VTEX Sales App</a> y la guía para desarrolladores <a href="https://developers.vtex.com/vtex-rest-api/docs/sales-rep-code">Enable the Sales Rep Code</a>.</p>
-</div>
+>ℹ️ Si el código de vendedor está activado, se le pide que lo rellene antes de compartir el carrito. Para obtener más información sobre el código de vendedor, visite la guía [Personalización de VTEX Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/Rby973h1l9tEM4C1YrzwZ) y la guía para desarrolladores [Enable the Sales Rep Code](https://developers.vtex.com/vtex-rest-api/docs/sales-rep-code).
 
 ## Link de pago
 
diff --git a/docs/tracks/es/shipping-strategies.md b/docs/tracks/es/shipping-strategies.md
index 7829b1c6c..587a8d39d 100644
--- a/docs/tracks/es/shipping-strategies.md
+++ b/docs/tracks/es/shipping-strategies.md
@@ -76,9 +76,7 @@ Para las [estrategias de envío](https://help.vtex.com/es/tutorial/estrategia-de
 6. [Registro de geolocalización](https://help.vtex.com/es/tutorial/registering-geolocation--tutorials_138)
 7. Configuración de los puntos de recogida disponibles en el _checkout_
 
-<div class="alert alert-warning">
-Consulta los pasos detallados sobre <a href="https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#como-configurar">cómo configurar un punto de recogida.</a> 
-</div>
+>⚠️ Consulta los pasos detallados sobre [cómo configurar un punto de recogida.](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#como-configurar)
 
 ## Tiempo de envío y feriados
 
@@ -95,9 +93,7 @@ Para ver más detalles sobre el cálculo del SLA, consulta el artículo [Cómo s
 
 Los feriados son importantes para determinar el plazo de envío, ya que está directamente relacionado con el plazo de entrega de los pedidos de tu tienda. VTEX considera que los feriados son los días en los que tu tienda no funcionará.
 
-<div class="alert alert-warning">
-Se recomienda que el registro de los feriados se realice después de la configuración de las estrategias de envío.
-</div>
+>⚠️ Se recomienda que el registro de los feriados se realice después de la configuración de las estrategias de envío.
 
 Para registrar los feriados en la plataforma, puedes:
 
diff --git a/docs/tracks/es/specifications-concept-definition.md b/docs/tracks/es/specifications-concept-definition.md
index 2a513b55f..463cf6bc6 100644
--- a/docs/tracks/es/specifications-concept-definition.md
+++ b/docs/tracks/es/specifications-concept-definition.md
@@ -16,9 +16,7 @@ trackSlugES: catalogo-101
 
 Las especificaciones son propiedades adicionales que se pueden registrar en los productos o SKUs de su tienda. En VTEX, estas especificaciones se registran en la pestaña **Categorías** y se denominan **Campo**.
 
-<div class="alert alert-warning">
-<p>En VTEX, las especificaciones siguen una lógica de "herencia", es decir, cuando se crea una especificación en un nivel de categoría superior, la especificación se presentará en todos los niveles de categoría inferiores. Por lo tanto, si es necesario crear una especificación de producto o SKU que se aplique a una sola categoría, debe crearse en ese nivel de categoría.</p>
-</div>
+>⚠️ En VTEX, las especificaciones siguen una lógica de "herencia", es decir, cuando se crea una especificación en un nivel de categoría superior, la especificación se presentará en todos los niveles de categoría inferiores. Por lo tanto, si es necesario crear una especificación de producto o SKU que se aplique a una sola categoría, debe crearse en ese nivel de categoría.
 
 ## Especificación de Producto
 
@@ -44,6 +42,4 @@ Las especificaciones de SKU tendrían los valores **PP, P, M, G y GG**. Estas po
 Para entender el paso a paso completo para la creación de especificaciones de productos, consulte el artículo [Registrar especificaciones o campos de SKU
 ](https://help.vtex.com/es/tutorial/registrar-especificaciones-o-campos-de-sku--tutorials_119).
 
-<div class="alert alert-warning">
-En VTEX, las especificaciones de SKU son campos obligatorios para concluir el registro de un SKU. Esto significa que, si se crea una nueva especificación dentro de una categoría, todos los SKUs dentro de esta categoría necesitan tener registrada esta nueva especificación. Así, todos estos SKUs estarán inactivos hasta que el registro de esta nueva especificación se haga en los SKUs de la categoría en cuestión.
-</div>
+>⚠️ En VTEX, las especificaciones de SKU son campos obligatorios para concluir el registro de un SKU. Esto significa que, si se crea una nueva especificación dentro de una categoría, todos los SKUs dentro de esta categoría necesitan tener registrada esta nueva especificación. Así, todos estos SKUs estarán inactivos hasta que el registro de esta nueva especificación se haga en los SKUs de la categoría en cuestión.
diff --git a/docs/tracks/es/subscription-orders.md b/docs/tracks/es/subscription-orders.md
index 9caa16fb1..11835803f 100644
--- a/docs/tracks/es/subscription-orders.md
+++ b/docs/tracks/es/subscription-orders.md
@@ -20,8 +20,6 @@ El cliente indica con qué frecuencia desea repetir la compra de un SKU particul
 
 En el Admin VTEX, en **Pedidos > Suscripciones**, hay una pestaña de [Dashboards](https://help.vtex.com/es/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x#dashboard) para el seguimiento y supervisión de las «Suscripciones» existentes y una pestaña de [Configuraciones](https://help.vtex.com/es/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x#configuraciones) de pedidos. La suscripción solo aparece en la lista después de que se aprueba el primer pago del cliente.
 
-<div class="alert alert-warning">
-Actualmente, solo los pedidos realizados con <strong>tarjeta de crédito</strong> permiten suscripciones. Active todas las condiciones de tarjeta de crédito ya definidas para <a href="https://help.vtex.com/es/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW">compras recurrentes</a> en sus métodos de pago. Además, su conector de pago debe aceptar pagos recurrentes. Póngase en contacto con el adquirente de su tienda y corrobore que este acepta transacciones de compras recurrentes cuyo origen sea tarjetas tokenizadas (sin código CVV).
-</div>
+>⚠️ Actualmente, solo los pedidos realizados con **tarjeta de crédito** permiten suscripciones. Active todas las condiciones de tarjeta de crédito ya definidas para [compras recurrentes](https://help.vtex.com/es/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW) en sus métodos de pago. Además, su conector de pago debe aceptar pagos recurrentes. Póngase en contacto con el adquirente de su tienda y corrobore que este acepta transacciones de compras recurrentes cuyo origen sea tarjetas tokenizadas (sin código CVV).
 
 Vea más instrucciones en el artículo [Cómo configurar Suscripciones en su tienda](https://help.vtex.com/es/tutorial/como-configurar-assinaturas--1FA9dfE7vJqxBna9Nft5Sj).
diff --git a/docs/tracks/es/teste-1.md b/docs/tracks/es/teste-1.md
index e33dfee01..9783c28af 100644
--- a/docs/tracks/es/teste-1.md
+++ b/docs/tracks/es/teste-1.md
@@ -32,9 +32,7 @@ La **Guía de onboarding** se compone de 3 series:
 * [Próximos pasos tras el go live](https://help.vtex.com/es/tracks/proximos-pasos-tras-el-go-live--3J7WFZyvTcoiwkcIVFVhIS)
 * [Soporte en VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-<div class="alert alert-info"> 
-Las series presentan contenidos complementarios, pero son independientes entre sí, lo que significa que se puede explorar el contenido libremente y sin necesidad de seguir una secuencia.
-</div>
+>ℹ️ Las series presentan contenidos complementarios, pero son independientes entre sí, lo que significa que se puede explorar el contenido libremente y sin necesidad de seguir una secuencia.
 
 Nuestra meta es asegurarnos de que tanto clientes como partners, así como todo el ecosistema de VTEX, puedan sacarle el máximo partido a la **Guía de onboarding**. Con este objetivo de garantizar la pertinencia del material para una amplia gama de negocios, hemos cubierto una jornada completa y abarcadora. 
 
diff --git a/docs/tracks/es/the-reservation.md b/docs/tracks/es/the-reservation.md
index 17d4f653c..185dc3561 100644
--- a/docs/tracks/es/the-reservation.md
+++ b/docs/tracks/es/the-reservation.md
@@ -22,9 +22,7 @@ La reserva conecta el módulo de logística al módulo de pedidos. Impide que el
 
 ## Cómo funciona la reserva
 
-<div class="alert alert-warning">
-Los productos solamente insertados en el carrito <strong>no</strong> generan reserva o prioridad. Una reserva se realiza solo si un pedido está <strong>finalizado</strong>.
-</div>  
+>⚠️ Los productos solamente insertados en el carrito **no** generan reserva o prioridad. Una reserva se realiza solo si un pedido está **finalizado**.  
 
 Este es el flujo de reserva en VTEX:  
 
@@ -36,6 +34,4 @@ Este es el flujo de reserva en VTEX:
 
 ![reservation es](https://images.ctfassets.net/alneenqid6w5/3qiFEUNLlkbc403lzwFCdS/31eaafb108b2e75685cc33441f127407/reservation_es.png)
 
-<div class="alert alert-warning">
-VTEX no quita automáticamente los artículos del inventario, incluso después de que hayan pasado al estado <code>Reserva Reconocida</code>. Los artículos comprados permanecerán en este estado hasta que el ERP o la tienda los quiten del inventario.
-</div>
+>⚠️ VTEX no quita automáticamente los artículos del inventario, incluso después de que hayan pasado al estado `Reserva Reconocida`. Los artículos comprados permanecerán en este estado hasta que el ERP o la tienda los quiten del inventario.
diff --git a/docs/tracks/es/tiktok-for-business.md b/docs/tracks/es/tiktok-for-business.md
index 61c923041..f61db51f1 100644
--- a/docs/tracks/es/tiktok-for-business.md
+++ b/docs/tracks/es/tiktok-for-business.md
@@ -14,9 +14,7 @@ trackId: 1r0yJSO11nrer1YVu3WTFd
 trackSlugES: integracion-de-tiktok
 ---
 
-<div class="alert alert-danger">
-  <p>La integración con TikTok solo está disponible para las tiendas de <strong>Brasil</strong>.</p>
-</div>
+>❗ La integración con TikTok solo está disponible para las tiendas de **Brasil**.
 
 [TikTok](https://www.tiktok.com/) es una plataforma de entretenimiento para crear y compartir videos cortos que también ofrece herramientas de _marketing_ para las empresas. TikTok Ads Manager es una de las principales herramientas disponibles en este contexto, e incluye funciones avanzadas que permiten lanzar campañas y gestionar publicidad en TikTok.
 
diff --git a/docs/tracks/es/unified-commerce.md b/docs/tracks/es/unified-commerce.md
index 710ce5e93..726949579 100644
--- a/docs/tracks/es/unified-commerce.md
+++ b/docs/tracks/es/unified-commerce.md
@@ -39,9 +39,7 @@ Otras ventajas de operar utilizando cuentas franquicia son:
 
 - Mejor rendimiento operativo gracias al uso de requests simultáneos en el checkout de la tienda. En una cuenta estándar, en la que se registra la [estrategia de envío](https://help.vtex.com/es/tracks/serie-general-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#ajustes-obligatorios-en-logistica) en la cuenta principal, los requests se procesan en fila, lo que puede resultar en una posible acumulación de requests y un aumento de interrupciones (timeouts). Cada vez que se produce una interrupción, se muestra un mensaje de error en el checkout y el cliente debe presionar F5 o hacer clic en el botón de actualizar para continuar con la compra. Este comportamiento afecta negativamente la experiencia del cliente y disminuye la tasa de conversión de la tienda.
 
-<div class="alert alert-warning">
-  <p>Las <a href="https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a> actúan como un <a href="https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a> de la cuenta principal. Cuando un cliente agrega productos al carrito y simula el envío en el sitio web de la cuenta principal, el <a href="https://help.vtex.com/es/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo de selección de sellers white label</a> asigna automáticamente la cuenta franquicia que se encargará del <a href="https://help.vtex.com/es/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP">fulfillment</a> del pedido. Si uno o más productos del carrito no están disponibles en la cuenta franquicia seleccionada, el sistema asignará otra cuenta disponible para realizar el envío de los productos faltantes, lo que permite que haya más de una entrega para el mismo pedido. Este proceso se lleva a cabo internamente, sin que el cliente vea los sellers.</p>
-</div>
+>⚠️ Las [cuentas franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) actúan como un [seller white label](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) de la cuenta principal. Cuando un cliente agrega productos al carrito y simula el envío en el sitio web de la cuenta principal, el [algoritmo de selección de sellers white label](https://help.vtex.com/es/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) asigna automáticamente la cuenta franquicia que se encargará del [fulfillment](https://help.vtex.com/es/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) del pedido. Si uno o más productos del carrito no están disponibles en la cuenta franquicia seleccionada, el sistema asignará otra cuenta disponible para realizar el envío de los productos faltantes, lo que permite que haya más de una entrega para el mismo pedido. Este proceso se lleva a cabo internamente, sin que el cliente vea los sellers.
 
 ## Envío desde la tienda
 
diff --git a/docs/tracks/es/vtex-modules-i.md b/docs/tracks/es/vtex-modules-i.md
index 2a7ef7ec4..fe7d41cca 100644
--- a/docs/tracks/es/vtex-modules-i.md
+++ b/docs/tracks/es/vtex-modules-i.md
@@ -21,9 +21,7 @@ La plataforma VTEX se compone de diferentes módulos, cada uno responsable de un
 - [Promociones](#promociones)
 - [Logística](#logistica)
 
-<div class="alert alert-info">
-El artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ">Módulos de VTEX II</a> presenta los módulos <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos">Pagos</a>, <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos">Pedidos</a>, y <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout">Checkout</a>.
-</div>
+>ℹ️ El artículo [Módulos de VTEX II](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ) presenta los módulos [Pagos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagos), [Pedidos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos), y [Checkout](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout).
 
 ## Catálogo
 
@@ -63,9 +61,7 @@ La siguiente tabla muestra los principales ajustes de Catálogo para la tienda,
 
 <br>
 
-<div class="alert alert-warning">
-Puedes obtener información detallada sobre la importación de productos a la plataforma VTEX desde un sistema ERP (Enterprise Resource Planning) o PIM (Product Information Manager) consultando el artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a>.
-</div>
+>⚠️ Puedes obtener información detallada sobre la importación de productos a la plataforma VTEX desde un sistema ERP (Enterprise Resource Planning) o PIM (Product Information Manager) consultando el artículo [Integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu).
 
 #### Árbol de categorías
 
@@ -79,9 +75,7 @@ Antes de importar el catálogo de la tienda a VTEX, recomendamos empezar a traba
 
 ![catalog_arquitecture_table_ES](https://images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/60756721b1e21b27b981dee2f2a5e9ad/catalog_arquitecture_table_ES.png)
 
-<div class="alert alert-info">
-En el artículo <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a> puedes consultar más información sobre cómo importar especificaciones para back office.
-</div>
+>ℹ️ En el artículo [Integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) puedes consultar más información sobre cómo importar especificaciones para back office.
 
 #### Marcas
 
@@ -174,9 +168,7 @@ Existe una diferencia entre las tablas de precios creadas para [políticas comer
 
 Las listas de precios no asociadas a políticas comerciales pueden utilizarse en contextos como __promociones__ y __clústeres de clientes__. Las tablas creadas para políticas comerciales solo pueden asociarse a la propia política comercial. Así, la tabla de precios asociada a una política comercial informa el precio de los SKU de esa política y no puede asociarse a otros contextos.
 
-<div class="alert alert-warning">
-Los conceptos de <b>tabla de precios</b> y <a href="LINK">política comercial</a> son diferentes. La política comercial es el contexto al que se asocia una tabla de precios.
-</div>
+>⚠️ Los conceptos de **tabla de precios** y [política comercial](LINK) son diferentes. La política comercial es el contexto al que se asocia una tabla de precios.
 
 A la hora de configurar una política comercial, es imprescindible [especificar la moneda que se utilizará en la tienda](https://help.vtex.com/es/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE). La creación de diferentes políticas comerciales, cada una asociada a una moneda distinta, permite a la tienda mostrar a los clientes los precios en diferentes monedas. 
 
@@ -227,9 +219,7 @@ Consulta más información sobre las posibilidades de aplicar promociones en el
 
 Puedes crear cupones de descuento en el [Admin VTEX](https://help.vtex.com/es/tutorial/criar-cupom-beta--7lMk3MmhNp2IEccyGApxU) o a través de [API](https://developers.vtex.com/docs/guides/creating-and-managing-coupons-with-promotions-api). Para utilizarlo, el cupón debe estar vinculado al menos a una promoción.
 
-<div class="alert alert-warning">
-Hay una cantidad limitada de cupones activos. Se recomienda encarecidamente la reutilización de los cupones, ya que un exceso de estos podría afectar el desempeño del módulo Promociones.
-</div>
+>⚠️ Hay una cantidad limitada de cupones activos. Se recomienda encarecidamente la reutilización de los cupones, ya que un exceso de estos podría afectar el desempeño del módulo Promociones.
 
 ### Crear promociones de campaña
 
@@ -317,9 +307,7 @@ La [transportadora](https://help.vtex.com/es/tutorial/o-que-e-uma-transportadora
 
 El [stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) de la tienda corresponde a los ítems almacenados que están disponibles para la venta. El almacén es la identificación de la ubicación física de almacenamiento, mientras que el stock es el conjunto de SKU disponibles para la venta.
 
-<div class="alert alert-danger">
-En VTEX, la actualización del stock una vez vendidos los ítems debe ser controlada por la propia tienda. De esta forma, tras la venta, el retailer garantiza un control de la cantidad de ítems restantes y de las operaciones de facturación con ERP. En el artículo  <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integraciones de backend</a> puedes consultar más información sobre cómo importar stock a través del back office.
-</div>
+>❗ En VTEX, la actualización del stock una vez vendidos los ítems debe ser controlada por la propia tienda. De esta forma, tras la venta, el retailer garantiza un control de la cantidad de ítems restantes y de las operaciones de facturación con ERP. En el artículo  [Integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) puedes consultar más información sobre cómo importar stock a través del back office.
 
 ### Lead time
 
diff --git a/docs/tracks/es/vtex-modules-ii.md b/docs/tracks/es/vtex-modules-ii.md
index e8542287c..05cf83ce6 100644
--- a/docs/tracks/es/vtex-modules-ii.md
+++ b/docs/tracks/es/vtex-modules-ii.md
@@ -28,9 +28,7 @@ El módulo [Pagos](https://help.vtex.com/es/tracks/pagos--6GAS7ZzGAm7AGoEAwDbwJG
 
 Para procesar y recibir los pagos de las compras realizadas en una tienda VTEX, es necesario contratar los servicios de uno o más proveedores de pago. Este contrato se realiza directamente entre el retailer y el proveedor respectivo, sin intervención ni participación de VTEX. Accede a la [Lista de proveedores de pago](https://help.vtex.com/es/tutorial/lista-de-proveedores-de-pago-por-pais--2im3BEGXxSAcRuxEaIHPvp) para consultar la disponibilidad de proveedores en VTEX en cada país.
 
-<div class="alert alert-warning">
-Recomendamos integrar más de un proveedor de pago en tu tienda para proporcionar una experiencia óptima al cliente al ofrecer diversos medios y condiciones de pago. Esto permite operar con diferentes tarifas y costos, mejorando el desempeño del negocio.
-</div>
+>⚠️ Recomendamos integrar más de un proveedor de pago en tu tienda para proporcionar una experiencia óptima al cliente al ofrecer diversos medios y condiciones de pago. Esto permite operar con diferentes tarifas y costos, mejorando el desempeño del negocio.
 
 Los ajustes de pago descritos en esta serie pueden realizarse en cualquier momento durante el proceso de onboarding. No obstante, para que la tienda pueda realizar cualquier tipo de transacción relacionada con pagos, es necesario que previamente se hayan configurado los módulos [Catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Precios](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precios) y [Logística](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica).
 
@@ -191,9 +189,7 @@ Para ubicar el registro de una compra en el Admin VTEX, además de poder [filtra
 - Email del cliente
 - Documento del cliente
 
-<div class="alert alert-warning">
-Solo se puede acceder a la información de los pedidos creados en los dos últimos años. Este mismo periodo es aplicable para que los clientes accedan a sus pedidos a través de <a href="">Mi cuenta</a>.
-</div>
+>⚠️ Solo se puede acceder a la información de los pedidos creados en los dos últimos años. Este mismo periodo es aplicable para que los clientes accedan a sus pedidos a través de [Mi cuenta]().
 
 VTEX proporciona dos funcionalidades importantes para que los clientes de la tienda puedan hacer un seguimiento de sus pedidos: [emails transaccionales](#emails-transaccionales) y el espacio de los clientes denominado [Mi Cuenta](#funcionalidad-mi-cuenta).
 
@@ -261,9 +257,7 @@ Más información en [Optimización de opciones de entrega en el checkout](https
 
 Funcionalidad que permite enviar emails a los clientes como recordatorio de un carrito que crearon previamente, pero no se completó la compra.
 
-<div class="alert alert-warning">
-Configurar el carrito abandonado durante el onboarding permite que todos los carritos que se creen se envíen nuevamente al cliente, brindándole la oportunidad de evaluarlos y completar la compra.
-</div>
+>⚠️ Configurar el carrito abandonado durante el onboarding permite que todos los carritos que se creen se envíen nuevamente al cliente, brindándole la oportunidad de evaluarlos y completar la compra.
 
 Más información en [Configurar carrito abandonado](https://help.vtex.com/es/tutorial/configurar-carrito-abandonado--tutorials_740).
 
@@ -271,9 +265,7 @@ Más información en [Configurar carrito abandonado](https://help.vtex.com/es/tu
 
 En la plataforma VTEX, las tiendas tienen la opción de ajustar manualmente el precio de un ítem (SKU) en el carrito de checkout. Esta funcionalidad puede utilizarse para aplicar descuentos especiales, corregir errores de precios, crear ofertas personalizadas, resolver reclamaciones relacionadas con precios o ajustar el costo de envío.
 
-<div class="alert alert-warning">
-Solo usuarios con <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> y permisos debidamente registrados en el VTEX Admin pueden realizar este cambio.
-</div>
+>⚠️ Solo usuarios con [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) y permisos debidamente registrados en el VTEX Admin pueden realizar este cambio.
 
 Más información en [Cambiar el precio de un ítem en el carrito de compras](https://help.vtex.com/es/tutorial/cambiar-el-precio-de-un-item-en-el-carrito-de-compras--7Cd37aCAmtL1qmoZJJvjNf).
 
diff --git a/docs/tracks/es/vtex-platform-settings.md b/docs/tracks/es/vtex-platform-settings.md
index fe44648ed..41b86e721 100644
--- a/docs/tracks/es/vtex-platform-settings.md
+++ b/docs/tracks/es/vtex-platform-settings.md
@@ -51,14 +51,10 @@ Si desea utilizar la misma Estrategia de Envío definida para su tienda VTEX en
 
 Si desea comprobar si la configuración se ha realizado correctamente, puede realizar una [simulación de envío](https://help.vtex.com/es/tutorial/simulacao-de-frete--tutorials_144). El simulador de envío es una herramienta que permite consultar las condiciones de entrega del producto sin necesidad de crear un pedido.
 
-<div class="alert alert-info">
-Amazon selecciona el tipo de envío a partir de la <a href="https://help.vtex.com/es/tutorial/como-montar-a-planilha-de-frete--tutorials_127">plantilla</a> que el administrador de la tienda <a href="https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034">exporta</a>. Por lo tanto, es importante que la plantilla que el administrador de la tienda exporta esté alineada con la plantilla registrada en VTEX, de modo que se reduzca la posibilidad de divergencias.
-</div>
+>ℹ️ Amazon selecciona el tipo de envío a partir de la [plantilla](https://help.vtex.com/es/tutorial/como-montar-a-planilha-de-frete--tutorials_127) que el administrador de la tienda [exporta](https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034). Por lo tanto, es importante que la plantilla que el administrador de la tienda exporta esté alineada con la plantilla registrada en VTEX, de modo que se reduzca la posibilidad de divergencias.
 
 ### Tiempo de procesamiento
 
 En Amazon hay el campo *“fulfillment latency”*, que se utiliza para configurar el tiempo de preparación de la entrega de un determinado producto. Para utilizarlo en la configuración con Amazon, debe rellenar el campo **Tiempo de Procesamiento** en el [registro del muelle](https://help.vtex.com/es/tutorial/como-cadastrar-doca) asociado a la [política comercial](#definir-la-política-comercial-en-amazon) utilizada para Amazon. Si este campo no se rellena, Amazon utilizará su valor por defecto (2 días).
 
-<div class="alert alert-warning">
-Filling in this field is essential, because if your store delays the delivery of an order, your account may be blocked. 
-</div>
+>⚠️ Filling in this field is essential, because if your store delays the delivery of an order, your account may be blocked.
diff --git a/docs/tracks/es/what-are-clustered-payment-conditions.md b/docs/tracks/es/what-are-clustered-payment-conditions.md
index 218ce8960..6a80db546 100644
--- a/docs/tracks/es/what-are-clustered-payment-conditions.md
+++ b/docs/tracks/es/what-are-clustered-payment-conditions.md
@@ -16,8 +16,6 @@ trackSlugES: condiciones-de-pago-clusterizadas
 
 Clustered Payments Conditions es una nueva funcionalidad de [Customer Credit](https://help.vtex.com/es/announcements/de-credito-aos-seus-melhores-clientes-com-o-customer-credit--6M2V1Oc1UIaGSM6QayWkmq?&utm_source=autocomplete "Customer Credit") que permite que los administradores de las tiendas determinen una regla de plazo y pago en cuotas que será válida para uno o más consumidores de su confianza. Este filtro se realiza por medio de clústeres, una forma de segmentación.
 
-<div class="alert alert-info">
-Esta funcionalidad se encuentra actualmente en Beta Cerrada (etapa de prueba) y no está disponible para su instalación en tiendas nuevas.
-</div>
+>ℹ️ Esta funcionalidad se encuentra actualmente en Beta Cerrada (etapa de prueba) y no está disponible para su instalación en tiendas nuevas.
 
 Esta personalización ocurre por medio de nuestro banco de datos, el [Master Data](https://help.vtex.com/es/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw "Master Data").
diff --git a/docs/tracks/es/what-are-permissions-and-access-profiles.md b/docs/tracks/es/what-are-permissions-and-access-profiles.md
index 19ce1f1fe..32447ebf7 100644
--- a/docs/tracks/es/what-are-permissions-and-access-profiles.md
+++ b/docs/tracks/es/what-are-permissions-and-access-profiles.md
@@ -20,7 +20,5 @@ Los perfiles de acceso definen qué funcionalidades el usuario puede visualizar
 
 Usted puede crear nuevos perfiles y definir permisos para estos.  O bien puede utilizar los [perfiles predeterminados](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#descripcion-de-los-perfiles-predefinidos) que ya están configurados en la plataforma. Los perfiles predeterminados generalmente satisfacen la gran mayoría de necesidades de todas las tiendas.
 
-<div class="alert alert-danger">
-La mala gestión de perfiles de acceso de su tienda puede ocasionar graves consecuencias para su negocio. Vea las mejores prácticas en el artículo: <a href="https://help.vtex.com/es/faq/metodos-de-seguridad-para-crear-perfiles-de-usuarios-en-una-tienda--15YDwC9jGgqWi3rvcDaiGM">Métodos de seguridad para crear perfiles de usuarios en una tienda</a>.
-</div>
+>❗ La mala gestión de perfiles de acceso de su tienda puede ocasionar graves consecuencias para su negocio. Vea las mejores prácticas en el artículo: [Métodos de seguridad para crear perfiles de usuarios en una tienda](https://help.vtex.com/es/faq/metodos-de-seguridad-para-crear-perfiles-de-usuarios-en-una-tienda--15YDwC9jGgqWi3rvcDaiGM).
 
diff --git a/docs/tracks/es/what-is-conversational-commerce-vtex.md b/docs/tracks/es/what-is-conversational-commerce-vtex.md
index 8f91a3650..41ffb1a46 100644
--- a/docs/tracks/es/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/es/what-is-conversational-commerce-vtex.md
@@ -20,9 +20,7 @@ Con esta solución, es posible comprar utilizando una lista de compras, ideal pa
 
 Para el uso de este servicio, Message-to-Order ya está preintegrado con las plataformas de mercado Zenvia (producto Zenvia Chat) y Zendesk. Si las tiendas no utilizan estas plataformas o no desean ofrecer servicio al cliente humano, existe la posibilidad de redirigir a los clientes a los canales de atención estándar a través de un mensaje personalizado.
 
-<div class="alert alert-info">
-Message-to-Order es un producto en fase inicial con alcance reducido (alfa). Por lo tanto, el perfil del cliente y los mercados cubiertos aún se limitan a Brasil y LATAM y solo está disponible un conjunto limitado de funciones.
-</div>
+>ℹ️ Message-to-Order es un producto en fase inicial con alcance reducido (alfa). Por lo tanto, el perfil del cliente y los mercados cubiertos aún se limitan a Brasil y LATAM y solo está disponible un conjunto limitado de funciones.
 
 Para agregar Conversational Commerce VTEX a tu tienda se requieren las siguientes configuraciones:
 
diff --git a/docs/tracks/es/what-is-suiteshare.md b/docs/tracks/es/what-is-suiteshare.md
index 31331498b..34f0d73fe 100644
--- a/docs/tracks/es/what-is-suiteshare.md
+++ b/docs/tracks/es/what-is-suiteshare.md
@@ -14,6 +14,4 @@ trackId: khP0p8mjIYRIpvM7Cb4Zr
 trackSlugES: suiteshare
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tracks/es/what-is-the-payment-split.md b/docs/tracks/es/what-is-the-payment-split.md
index 29e0ad1a4..ddb44d875 100644
--- a/docs/tracks/es/what-is-the-payment-split.md
+++ b/docs/tracks/es/what-is-the-payment-split.md
@@ -24,9 +24,7 @@ Sin embargo, ese monto no necesariamente se divide en partes iguales entre los r
 
 En este documento, explicaremos cómo funciona esta solución, incluyendo algunos conceptos importantes para esa dinámica, y cómo configurarla. 
 
-<div class="alert alert-info">
-Si usted ya conoce esta solución, vaya a la etapa Configurar *split* de pagos.
-</div>
+>ℹ️ Si usted ya conoce esta solución, vaya a la etapa Configurar *split* de pagos.
 
 ## Cuentas por cobrar 
 Antes de continuar, es importante explicar qué es una cuenta por cobrar, un concepto que no solo es abordado en VTEX, sino también en diversos escenarios del mercado de pagos. 
@@ -41,18 +39,14 @@ Actualmente, el split soporta los siguientes medios de pago:
 - Tarjeta de débito
 - Boleto bancario (exclusivo de Brasil)
 
-<div class="alert alert-info">
-En el caso de la tarjeta de crédito, el *split* soporta pagos realizados con dos tarjetas.
-</div>
+>ℹ️ En el caso de la tarjeta de crédito, el *split* soporta pagos realizados con dos tarjetas.
 
 ## Transacción
 Cuando un consumidor finaliza una compra y realiza el pago, ese valor no necesariamente se capturará y enviará al administrador de la tienda el mismo día.
 
-<div class="alert alert-info">
-En el caso de Brasil, existen excepciones como Pix —Sistema de Pagos Instantáneos del Banco Central— en el que la transacción se realiza en segundos. 
-
-Sin embargo, la mayoría de los medios de pago que actualmente están disponibles en el mercado no realizan la acreditación automática del pago al administrador de la tienda.
-</div>  
+>ℹ️ En el caso de Brasil, existen excepciones como Pix —Sistema de Pagos Instantáneos del Banco Central— en el que la transacción se realiza en segundos. 
+>
+> Sin embargo, la mayoría de los medios de pago que actualmente están disponibles en el mercado no realizan la acreditación automática del pago al administrador de la tienda.  
 
 En VTEX, el comportamiento estándar es que los datos de la compra se reúnan en una transacción. Esta, por su parte, pasará por varias etapas de validación para garantizar que todos los datos sean legítimos. Ese proceso de verificación se denomina [flujo de la transacción](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/1xjzgJZvqwaI1rfxLMCC3Y "flujo de la transación"). 
 
diff --git a/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md b/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md
index 6102e00b3..d0be0e030 100644
--- a/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md
+++ b/docs/tracks/es/what-to-configure-in-wish-prior-to-the-integration.md
@@ -14,7 +14,7 @@ trackId: 50hbG4bzhSIhjz1lzqI1g4
 trackSlugES: integracion-con-wish
 ---
 
-<div class="alert alert-warning">Actualmente, la app de Wish está disponible  solamente para tiendas brasileiras.</div>
+>⚠️ Actualmente, la app de Wish está disponible  solamente para tiendas brasileiras.
 
 Debe preparar su ambiente en Wish antes de iniciar la integración en VTEX. Los pasos principales son:
 
diff --git a/docs/tracks/es/what-to-configure-with-vtex-before-starting-the-integration.md b/docs/tracks/es/what-to-configure-with-vtex-before-starting-the-integration.md
index 3acfd34c9..01e3b5c3a 100644
--- a/docs/tracks/es/what-to-configure-with-vtex-before-starting-the-integration.md
+++ b/docs/tracks/es/what-to-configure-with-vtex-before-starting-the-integration.md
@@ -20,13 +20,11 @@ Para garantizar el correcto funcionamiento de la integración, es necesario real
 
 Es necesario definir qué política comercial se utilizará para integrar sus productos con Wish. Esta definición implicará cuatro aspectos principales: surtido de productos, stock, precio y moneda. Es decir, la disponibilidad y los precios de sus productos en un canal de venta determinado se basarán completamente en la política comercial que usted elija. [Haga clic aquí para entender con más detalle cómo funciona la política comercial](https://help.vtex.com/es/tutorial/configurando-a-politica-comercial-para-marketplace?locale=pt).
 
-<div class="alert alert-info">
-OBS: Wish exige que los precios del producto y flete se envíen en dólares (USD). Sin embargo, crea los pedidos con el valor ya convertido en reales (R$) para facilitar la emisión de la factura.
-
-Esto significa que la integración debe enviar precios en dólares y aceptar pedidos en reales. De esta manera, la arquitectura utiliza apenas Real (R$) y hace la conversión en la integración.
-
-Por lo tanto, <strong>la política comercial para Wish debe ser en reales (R$)</strong> y todo el flujo de conversión se detallará mejor en el [paso 5](https://help.vtex.com/es/tracks/integracion-con-wish--50hbG4bzhSIhjz1lzqI1g4/6EYEy1jRiAj465WOnhiczD).
-</div>
+>ℹ️ OBS: Wish exige que los precios del producto y flete se envíen en dólares (USD). Sin embargo, crea los pedidos con el valor ya convertido en reales (R$) para facilitar la emisión de la factura.
+>
+> Esto significa que la integración debe enviar precios en dólares y aceptar pedidos en reales. De esta manera, la arquitectura utiliza apenas Real (R$) y hace la conversión en la integración.
+>
+> Por lo tanto, **la política comercial para Wish debe ser en reales (R$)** y todo el flujo de conversión se detallará mejor en el [paso 5](https://help.vtex.com/es/tracks/integracion-con-wish--50hbG4bzhSIhjz1lzqI1g4/6EYEy1jRiAj465WOnhiczD).
 
 [Haga clic aquí](https://help.vtex.com/es/faq/por-que-nao-consigo-criar-uma-nova-politica-comercial?locale=pt) para saber cómo contratar una nueva política si fuera necesario.
 
@@ -47,10 +45,8 @@ Para garantizar que los pedidos se integren con éxito, deberá realizar toda la
   3. Defina las [transportadoras](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/3fLedVI57srjBDDxxGgOWe) que realizarán las entregas de Wish.
   4. Asocie las transportadoras con los muelles.
  
-<div class="alert alert-info">
-OBS: Wish realiza la transferencia de la comisión a través de la confirmación de entrega de los pedidos y consulta directamente a sus transportadoras asociadas para obtener esta información. <strong><i>Por lo tanto, para vender en Wish es obligatorio utilizar las transportadoras asociadas para realizar las entregas de los pedidos.</i></strong>
-<a href="https://merchant.wish.com/documentation/shippingproviders"> Consulte aquí la lista de transportadoras aceptadas por Wish.</a>
-</div>
+>ℹ️ OBS: Wish realiza la transferencia de la comisión a través de la confirmación de entrega de los pedidos y consulta directamente a sus transportadoras asociadas para obtener esta información. **<i>Por lo tanto, para vender en Wish es obligatorio utilizar las transportadoras asociadas para realizar las entregas de los pedidos.</i>**
+> [ Consulte aquí la lista de transportadoras aceptadas por Wish.](https://merchant.wish.com/documentation/shippingproviders)
 
 ## Definiendo precios
 
diff --git a/docs/tracks/pt/about-b2w-integration.md b/docs/tracks/pt/about-b2w-integration.md
index 2b8588473..465b6da6d 100644
--- a/docs/tracks/pt/about-b2w-integration.md
+++ b/docs/tracks/pt/about-b2w-integration.md
@@ -32,6 +32,4 @@ Existe também o serviço B2W Entregas Direct, resultado da parceria entre a B2W
 - Cadastrar na plataforma da B2W o status `order_invoiced` como sendo do tipo _Pagamento Faturado_.
 - Preencher na plataforma VTEX o campo `embeddedInvoice` da API de [Order invoice notification](https://developers.vtex.com/vtex-rest-api/reference/invoice) com os dados da nota fiscal.
 
-<div class="alert alert-warning">
-Sem o status <b>order_invoiced</b> criado no marketplace e o <b>embeddedInvoice</b> preenchido corretamente, não é possível avançar com o pedido na VTEX, pois o pedido só é faturado mediante inclusão dos dados em XML na nota fiscal. O campo <b>issuanceDate</b> também precisa estar preenchido com uma data válida.
-</div>
+>⚠️ Sem o status **order_invoiced** criado no marketplace e o **embeddedInvoice** preenchido corretamente, não é possível avançar com o pedido na VTEX, pois o pedido só é faturado mediante inclusão dos dados em XML na nota fiscal. O campo **issuanceDate** também precisa estar preenchido com uma data válida.
diff --git a/docs/tracks/pt/accounts-and-architecture.md b/docs/tracks/pt/accounts-and-architecture.md
index aaf06c1de..af9757c76 100644
--- a/docs/tracks/pt/accounts-and-architecture.md
+++ b/docs/tracks/pt/accounts-and-architecture.md
@@ -39,9 +39,14 @@ Existem vários fatores para [escolher entre conta padrão, conta franquia ou Se
 | Conta franquia | <ul><li>Não tem frontend e site próprio.</li><li>Possui ambiente próprio no Admin VTEX para gerir a operação.</li><li>Não possui <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo">catálogo</a> próprio, e sim reflete a exata estrutura de catálogo da conta principal.</li><li>Pode configurar <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos">preços e promoções</a>.</li><li>Tem estoque e inventário próprios.</li><li>O inventário da conta franquia pode ser vendido em outros marketplaces VTEX conectados à conta principal, por meio da <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory (MOI)</a>.</li></ul> |
 | Conta Seller Portal | <ul><li>Não tem frontend e site próprio.</li><li>A conta principal tem uma área para <a href="https://help.vtex.com/pt/tutorial/gerenciamento-de-sellers--6eEiOISwxuAWJ8w6MtK7iv">gerenciar os sellers</a> e cada seller tem um ambiente próprio separado no Admin do Seller Portal.</li><li>O seller pode configurar estoque e preço, gerenciar produtos compartilhados com o marketplace, faturar pedidos, ativar promoções, processar pagamentos e ter logística própria.</li></ul> |
 
-<div class="alert alert-info">
-<b>Marketplace na VTEX</b><p>Além de oferecer grande versatilidade na arquitetura da loja, nosso ecossistema possibilita a cada loja ter uma série de <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">estratégias de marketplace</a>, tais como:</p><p><ul><li>Tornar-se seller ou marketplace de outras lojas VTEX.</li><li>Integrar com os grandes players do mercado, como o <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre</a> e a <a href="https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP">Amazon</a>.</li><li>Integrar com os <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros">marketplaces parceiros</a> certificados pela VTEX.</li><li>Ser marketplace para sellers com conta <a href="https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK">Seller Portal</a>.</li><li>Ser <a href="https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>.</li><li>Criar integrações próprias com <a href="https://developers.vtex.com/docs/guides/external-seller-integration-guide">marketplaces e sellers externos</a>.</li></ul></p>
-</div>
+>ℹ️ **Marketplace na VTEX**Além de oferecer grande versatilidade na arquitetura da loja, nosso ecossistema possibilita a cada loja ter uma série de [estratégias de marketplace](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402), tais como:
+> 
+> *Tornar-se seller ou marketplace de outras lojas VTEX.
+> * Integrar com os grandes players do mercado, como o [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) e a [Amazon](https://help.vtex.com/pt/tracks/configurar-integracao-com-a-amazon--6sgd4Pagy3wNsWKBvmIFrP).
+> * Integrar com os [marketplaces parceiros](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-marketplaces-parceiros) certificados pela VTEX.
+> * Ser marketplace para sellers com conta [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK).
+> * Ser [seller white label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
+> * Criar integrações próprias com [marketplaces e sellers externos](https://developers.vtex.com/docs/guides/external-seller-integration-guide).
 
 ## Arquitetura da loja
 
@@ -116,7 +121,5 @@ Para auxiliar decisões sobre quais produtos e configurações incluir no planej
 
 O [Quadrante VTEX](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) é um programa em que a VTEX avalia internamente a performance e os resultados de sucesso da operação dos seus parceiros. Esta é uma forma de reconhecer e premiar anualmente aqueles que apresentam o maior nível de entrega e excelência. Veja [aqui](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) o resultado do Quadrante de 2023.
 
-<div class="alert alert-info">
-O <a href="https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/">Quadrante VTEX</a> é um programa exclusivo para parceiros de implementação do Brasil.
-</div>
+>ℹ️ O [Quadrante VTEX](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) é um programa exclusivo para parceiros de implementação do Brasil.
 
diff --git a/docs/tracks/pt/add-an-image-to-the-sku.md b/docs/tracks/pt/add-an-image-to-the-sku.md
index 73c85f722..3e102c68f 100644
--- a/docs/tracks/pt/add-an-image-to-the-sku.md
+++ b/docs/tracks/pt/add-an-image-to-the-sku.md
@@ -16,9 +16,7 @@ trackSlugPT: vtex-getting-started
 
 Todo SKU precisa de pelo menos uma imagem para ser exibido na loja.
 
-<div class="alert alert-warning">
-Se nenhuma imagem for associada a um SKU, ele não ficará ativo.
-</div>
+>⚠️ Se nenhuma imagem for associada a um SKU, ele não ficará ativo.
 
 Por isso, depois que terminar de preencher as configurações do seu novo SKU e clicar em __Salvar__, você será levado para a tela de cadastro de imagem, onde a mensagem abaixo é exibida.
 
diff --git a/docs/tracks/pt/add-on-products.md b/docs/tracks/pt/add-on-products.md
index a5bfde31e..af1c674d8 100644
--- a/docs/tracks/pt/add-on-products.md
+++ b/docs/tracks/pt/add-on-products.md
@@ -16,9 +16,7 @@ trackSlugPT: proximos-passos-apos-o-go-live
 
 Produtos Add-on são soluções oferecidas pela VTEX para atender demandas específicas de um negócio e que podem ser adquiridas separadamente por meio de um contrato de assinatura.
 
-<div class="alert alert-warning">
-  <p>Para implementar as soluções abaixo, é necessário entrar em contato com o nosso <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial VTEX</a>.</p> 
-</div>
+>⚠️ Para implementar as soluções abaixo, é necessário entrar em contato com o nosso [Suporte Comercial VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
 ## VTEX Ad Network
 
@@ -84,9 +82,7 @@ O **VTEX Shipping Network** proporciona a possibilidade de conectar transportado
 
 Para mais informações, é preciso acessar a página sobre [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/).
 
-<div class="alert alert-warning">
-  <p>As soluções <strong>VTEX Shipping Network</strong> e <strong>VTEX Shipping Network Correios</strong> são exclusivas para operações no Brasil.</p>
-</div>
+>⚠️ As soluções **VTEX Shipping Network** e **VTEX Shipping Network Correios** são exclusivas para operações no Brasil.
 
 ## VTEX Shipping Network Correios
 
diff --git a/docs/tracks/pt/add-pickup-points.md b/docs/tracks/pt/add-pickup-points.md
index 988336237..748dcfd52 100644
--- a/docs/tracks/pt/add-pickup-points.md
+++ b/docs/tracks/pt/add-pickup-points.md
@@ -70,9 +70,7 @@ Para subir uma planilha com os pontos de retirada, siga os passos abaixo:
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Logística devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Logística devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2)
 
 Para cadastrar um **Ponto de Retirada** por API, você precisa enviar um __POST__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/add-sku-specifications.md b/docs/tracks/pt/add-sku-specifications.md
index 1edd1dda6..205c6f1c8 100644
--- a/docs/tracks/pt/add-sku-specifications.md
+++ b/docs/tracks/pt/add-sku-specifications.md
@@ -16,9 +16,7 @@ trackSlugPT: catalogo-101
 
 Há três formas de cadastrar suas especificações de SKU: por meio do admin, por planilha ou por ERP.
 
-<div class="alert alert-warning">
-<p>Na VTEX, as especificações seguem uma lógica de “herança”, ou seja, ao criar uma especificação em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela. Portanto, se for necessário criar uma especificação de produto ou SKU que se aplique a apenas uma categoria, esta deve ser criada no nível dessa categoria.</p>
-</div>
+>⚠️ Na VTEX, as especificações seguem uma lógica de “herança”, ou seja, ao criar uma especificação em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela. Portanto, se for necessário criar uma especificação de produto ou SKU que se aplique a apenas uma categoria, esta deve ser criada no nível dessa categoria.
 
 Siga o passo a passo abaixo para cadastrar as especificações:
 
diff --git a/docs/tracks/pt/adding-a-loading-dock.md b/docs/tracks/pt/adding-a-loading-dock.md
index f7a07823d..a7559701b 100644
--- a/docs/tracks/pt/adding-a-loading-dock.md
+++ b/docs/tracks/pt/adding-a-loading-dock.md
@@ -43,9 +43,7 @@ Siga o passo a passo abaixo para cadastrar uma Doca na sua loja:
 -   _Tempo de Custo_: tempo que será adicionado ao cálculo da entrega por conta da etapa desta doca. 
 >_Ex.:_  tempo de custo do estoque (2 dias) + tempo de custo da doca (3 dias) + tempo de custo da transportadora (1 dia) = entrega será realizada em 6 dias.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: o prazo de uma doca independe de uma transportadora funcionar - ou não - em finais de semanas e feriados. O tempo de entrega sempre será a soma do tempo do estoque, da transportadora e da doca.  
-</div>
+>ℹ️ **Atenção**: o prazo de uma doca independe de uma transportadora funcionar - ou não - em finais de semanas e feriados. O tempo de entrega sempre será a soma do tempo do estoque, da transportadora e da doca.
 
 -   _Overhead de tempo de custo_: valor que será usado para a escolha da doca mais vantajosa em determinada entrega. Este valor não é adicionado ao cálculo de tempo de entrega.
 >_Ex.:_  as docas A e B têm tempo de custo de 3 dias, mas a doca A tem overhead de 1 dia, enquanto a doca B tem overhead de 2 dias. Neste caso, a doca A será escolhida.
@@ -58,9 +56,7 @@ Siga o passo a passo abaixo para cadastrar uma Doca na sua loja:
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Estoque & Entrega devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Estoque & Entrega devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2)
 
 Para cadastrar uma **Doca** por API, você precisa enviar um __POST__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/adding-a-price-rule.md b/docs/tracks/pt/adding-a-price-rule.md
index 4193667a3..d0a21612d 100644
--- a/docs/tracks/pt/adding-a-price-rule.md
+++ b/docs/tracks/pt/adding-a-price-rule.md
@@ -35,9 +35,7 @@ Siga o passo a passo abaixo para cadastrar a regra de preço da sua loja:
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para cadastrar uma **regra de preço**, você precisa enviar um __POST__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/adding-a-sender.md b/docs/tracks/pt/adding-a-sender.md
index 1447c8e82..306de566e 100644
--- a/docs/tracks/pt/adding-a-sender.md
+++ b/docs/tracks/pt/adding-a-sender.md
@@ -42,8 +42,6 @@ Feito isso, retorne para a página de configurações no Admin e selecione a fla
 
 Sempre que achar necessário, você pode testar se o envio de e-mails está funcionando. Para isso, acesse a seção Remetentes e clique no botão `Testar` do card com o remetente desejado.
 
-<div class="alert alert-warning">
-Atenção: sempre que você fizer uma alteração no remetente e salvá-la, será enviado um e-mail de confirmação de SMTP cadastrado com sucesso para o endereço informado. Em todos os casos, é imprescindível clicar no link enviado no e-mail para concluir a confirmação.
-</div>
+>⚠️ Atenção: sempre que você fizer uma alteração no remetente e salvá-la, será enviado um e-mail de confirmação de SMTP cadastrado com sucesso para o endereço informado. Em todos os casos, é imprescindível clicar no link enviado no e-mail para concluir a confirmação.
   
 
diff --git a/docs/tracks/pt/adding-collections-track.md b/docs/tracks/pt/adding-collections-track.md
index 2551dd141..fb031a3ac 100644
--- a/docs/tracks/pt/adding-collections-track.md
+++ b/docs/tracks/pt/adding-collections-track.md
@@ -14,9 +14,7 @@ trackId: 5AF0XfnjfWeopIFBgs3LIQ
 trackSlugPT: catalogo-101
 ---
 
-<div class="alert alert-warning">
-  <p>Antes de criar uma coleção, é preciso ter configurado a autorização. Para isso, é preciso ter um perfil de acesso com o recurso <b>Write Collections</b>, na seção <b>Collections</b> dos perfis do Catalog. Veja aqui <a href ="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">como configurar um recurso</a>.</p>
-</div>
+>⚠️ Antes de criar uma coleção, é preciso ter configurado a autorização. Para isso, é preciso ter um perfil de acesso com o recurso **Write Collections**, na seção **Collections** dos perfis do Catalog. Veja aqui <a href ="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">como configurar um recurso</a>.
 
 Siga o passo a passo abaixo para cadastrar uma nova coleção:
 
diff --git a/docs/tracks/pt/adding-extra-text-to-the-order-print.md b/docs/tracks/pt/adding-extra-text-to-the-order-print.md
index 1c4e32f99..3bf0329dc 100644
--- a/docs/tracks/pt/adding-extra-text-to-the-order-print.md
+++ b/docs/tracks/pt/adding-extra-text-to-the-order-print.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: adicionar-texto-extra-a-impressao-do-pedido
 ---
 
-<div class="alert alert-danger">
-A adicão de texto extra à impressão do pedido, explicada neste artigo, envolve e alteração do arquivo JavaScript <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A adicão de texto extra à impressão do pedido, explicada neste artigo, envolve e alteração do arquivo JavaScript `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 Por padrão, a impressão do resumo do pedido não contém nenhum texto personalizado. Caso deseje adicionar texto extra à impressão do pedido, é necessário editar o arquivo `checkout-instore-custom.js`.
 
@@ -28,9 +26,7 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
 
 Após recarregar o inStore, sempre que um vendedor imprimir um pedido, esse texto aparecerá na impressão.
 
diff --git a/docs/tracks/pt/adding-holidays.md b/docs/tracks/pt/adding-holidays.md
index fc5abfeee..3cf4b35a8 100644
--- a/docs/tracks/pt/adding-holidays.md
+++ b/docs/tracks/pt/adding-holidays.md
@@ -28,9 +28,7 @@ Para configurar os Feriados, siga os passos abaixo:
 4. Em __Data__, preencha com a data de início do feriado. Em __Data Final__, preencha com a data final do feriado.
 5. Clique em __Salvar__.
 
-<div class="alert alert-warning">
-  Os feriados serão considerados apenas para as transportadoras que estiverem configuradas como "Transportadora	<strong>não entrega</strong> aos finais de semana".
-</div>
+>⚠️ Os feriados serão considerados apenas para as transportadoras que estiverem configuradas como "Transportadora	**não entrega** aos finais de semana".
 
 Para tornar a transportadora elegível à feature de feriados, siga os passos abaixo:
 
@@ -41,9 +39,7 @@ Para tornar a transportadora elegível à feature de feriados, siga os passos ab
 5. Selecione a opção __Transportadora não entrega	aos finais de semana__.
 6. Clique em __Salvar__.
 
-<div class="alert alert-info">
-Você pode definir feriados para os próximos anos com antecedência. Por exemplo, pode criar Natal 2019, Natal 2020 etc.
-</div>
+>ℹ️ Você pode definir feriados para os próximos anos com antecedência. Por exemplo, pode criar Natal 2019, Natal 2020 etc.
 
 ## Como é feito o cálculo
 
diff --git a/docs/tracks/pt/adding-product-specifications.md b/docs/tracks/pt/adding-product-specifications.md
index c8c74d624..c73474b33 100644
--- a/docs/tracks/pt/adding-product-specifications.md
+++ b/docs/tracks/pt/adding-product-specifications.md
@@ -16,9 +16,7 @@ trackSlugPT: catalogo-101
 
 Há três formas de cadastrar suas especificações: por meio do admin, por planilha ou por API.
 
-<div class="alert alert-warning">
-<p>Na VTEX, as especificações seguem uma lógica de “herança”, ou seja, ao criar uma especificação em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela. Portanto, se for necessário criar uma especificação de produto ou SKU que se aplique a apenas uma categoria, esta deve ser criada no nível dessa categoria.</p>
-</div>
+>⚠️ Na VTEX, as especificações seguem uma lógica de “herança”, ou seja, ao criar uma especificação em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela. Portanto, se for necessário criar uma especificação de produto ou SKU que se aplique a apenas uma categoria, esta deve ser criada no nível dessa categoria.
 
 Siga o passo a passo abaixo para cadastrar as especificações:
 
diff --git a/docs/tracks/pt/adding-products.md b/docs/tracks/pt/adding-products.md
index 6c66f941a..abaecd823 100644
--- a/docs/tracks/pt/adding-products.md
+++ b/docs/tracks/pt/adding-products.md
@@ -40,6 +40,4 @@ Para cadastrar seus produtos por planilha, recomendamos que você cadastre ao me
 
 Para cadastrar um produto por API, use a chamada [Create Product](https://developers.vtex.com/vtex-rest-api/reference/post-product).
 
-<div class="alert alert-info">
-Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo <a href="https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382">Por que o produto não aparece no site?</a> para entender como resolver esse problema.
-</div>
+>ℹ️ Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo [Por que o produto não aparece no site?](https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382) para entender como resolver esse problema.
diff --git a/docs/tracks/pt/adding-the-magazine-luiza-integration.md b/docs/tracks/pt/adding-the-magazine-luiza-integration.md
index 673f0541a..665960cd5 100644
--- a/docs/tracks/pt/adding-the-magazine-luiza-integration.md
+++ b/docs/tracks/pt/adding-the-magazine-luiza-integration.md
@@ -40,9 +40,7 @@ Caso você esteja migrando uma conta, nós aproveitaremos o afiliado já usado p
 
 _`Ex:` imagine que você usa os Correios (PAC) como transportadora, seu Tipo de Transportadora na IntegraCommerce seja "Normal" e no painel logístico da VTEX se chama "Comum". Então, você deve preencher o primeiro campo com "Normal" e o segundo com "Comum". Lembre-se que as palavras devem ser exatamente iguais às cadastradas na logística._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> cada campo de mapeamento de SLA possui uma limitação de <strong>50</strong> caracteres.
-</div>
+>⚠️ **OBS:** cada campo de mapeamento de SLA possui uma limitação de **50** caracteres.
 
 &bull; __Estoque mínimo*:__ você deve preencher esse campo com um valor mínimo de estoque de segurança. Por mais que a comunicação entre os sistemas da VTEX e da Magazine Luiza seja rápida, o estoque exibido no marketplace pode ficar defasado em relação ao estoque real do produto na sua loja (mesmo que por alguns minutos). Assim, quando o estoque na VTEX chegar a esse valor, a integração vai zerar o estoque para que a venda de um produto sem estoque não aconteça.
 
diff --git a/docs/tracks/pt/adding-vendors.md b/docs/tracks/pt/adding-vendors.md
index 1ebfb06c5..eb3e4877f 100644
--- a/docs/tracks/pt/adding-vendors.md
+++ b/docs/tracks/pt/adding-vendors.md
@@ -24,9 +24,7 @@ Clique em __Admin dos vendedores__ para abrir a tabela onde incluiremos um novo
 
 Caso você já tenha cadastrado um vendedor através do __Easy Setup__, basta clicar em __New line__, inserir os dados do novo vendedor, copiar o ID da Loja da linha superior e clicar em __Save__, como mostra o vídeo abaixo (clique na imagem abaixo para visualizar):
  
-<div class="alert alert-danger">
-<strong>IMPORTANTE</strong>: o e-mail de cada vendedor <strong>NÃO</strong> pode ser o mesmo utilizado na plataforma VTEX, isso porque o seu e-mail de admin possui permissões que um vendedor não deveria ter, por isso é necessário utilizar algum outro e-mail sem privilégios na plataforma.
-</div>
+>❗ **IMPORTANTE**: o e-mail de cada vendedor **NÃO** pode ser o mesmo utilizado na plataforma VTEX, isso porque o seu e-mail de admin possui permissões que um vendedor não deveria ter, por isso é necessário utilizar algum outro e-mail sem privilégios na plataforma.
 
 ![inStore adicionando vendedor](https://images.ctfassets.net/alneenqid6w5/3WGuWnOeY8emcmuIqcE0uE/74586856739dcee97163835710a85780/inStore_adicionando_vendedor.png)
 
@@ -37,6 +35,4 @@ Após cadastrar o vendedor no admin da VTEX, ele precisará fazer login no e-com
 Para definir a senha desse vendedor acesse o __admin__ da sua conta: https://{{AccountName}}.myvtex.com/admin e depois siga esse artigo: https://help.vtex.com/pt/faq/como-recuperar-senha-de-acesso
 __Caso você tente definir a senha diretamente no site do e-commerce, o acesso ao inStore não funcionará.__
 
-<div class="alert alert-warning">
-<strong>Importante</strong>: além de configurar o vendedor no VTable, é necessário criar o usuário no Admin, associando a ele o perfil <b>inStore Sales Person</b>.
-</div>
+>⚠️ **Importante**: além de configurar o vendedor no VTable, é necessário criar o usuário no Admin, associando a ele o perfil **inStore Sales Person**.
diff --git a/docs/tracks/pt/adding-warehouses.md b/docs/tracks/pt/adding-warehouses.md
index c3d27e08b..630eaf1b7 100644
--- a/docs/tracks/pt/adding-warehouses.md
+++ b/docs/tracks/pt/adding-warehouses.md
@@ -39,9 +39,7 @@ Siga o passo a passo abaixo para cadastrar um estoque na sua loja:
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Estoque & Entrega devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Estoque & Entrega devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2)
 
 Para cadastrar um **Estoque** por API, você precisa enviar um __POST__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/amazon-account-settings.md b/docs/tracks/pt/amazon-account-settings.md
index 337225cde..f88dca476 100644
--- a/docs/tracks/pt/amazon-account-settings.md
+++ b/docs/tracks/pt/amazon-account-settings.md
@@ -32,6 +32,4 @@ Após criar sua conta de seller, você deverá autorizar a  VTEX na sua conta Am
 
 Após realizar a autorização, você será redirecionado para o Admin VTEX e esta etapa da integração estará concluída.  
 
-<div class="alert alert-info">
-Caso alguma dúvida sobre essa etapa persista, <a href="https://sellercentral.amazon.com/learn/courses?ref_=su_course_accordion&moduleId=1f61fcd3[…]-ed90359ff166&modLanguage=Portuguese&videoPlayer=youtube">acesse a documentação do Seller Central da Amazon.</a>
-</div>
+>ℹ️ Caso alguma dúvida sobre essa etapa persista, [acesse a documentação do Seller Central da Amazon.](https://sellercentral.amazon.com/learn/courses?ref_=su_course_accordion&moduleId=1f61fcd3[…]-ed90359ff166&modLanguage=Portuguese&videoPlayer=youtube)
diff --git a/docs/tracks/pt/apple-pay.md b/docs/tracks/pt/apple-pay.md
index 2b8dd8960..23ee3cfdd 100644
--- a/docs/tracks/pt/apple-pay.md
+++ b/docs/tracks/pt/apple-pay.md
@@ -19,9 +19,7 @@ Seus clientes podem fazer compras usando o Apple Pay, a [carteira digital](https
 - Ter uma conta em `developer.apple.com`.
 - Ter contrato com um provedor que processe pagamentos com Apple Pay.
 
-<div class="alert alert-warning">
-  O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse <a href="https://support.apple.com/pt-br/HT208531">Dispositivos compatíveis com o Apple Pay</a>.
-</div>
+>⚠️ O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse [Dispositivos compatíveis com o Apple Pay](https://support.apple.com/pt-br/HT208531).
 
 ## Configurar provedor de pagamento
 
@@ -29,9 +27,7 @@ Primeiramente é necessário configurar no Admin de sua loja um provedor que pro
 
 Para conferir todas as opções de provedores disponíveis para este meio de pagamento, acesse a lista conforme descrito no Passo 5 da seção [Configurar pagamento com Apple Pay](#configurar-pagamento-com-apple-pay).
 
-<div class="alert alert-warning">
-  Antes de iniciar a configuração do provedor é necessário <a href="registrar o Merchant ID no Apple Pay">registrar o Merchant ID no Apple Pay</a>.
-</div>
+>⚠️ Antes de iniciar a configuração do provedor é necessário [registrar o Merchant ID no Apple Pay](registrar o Merchant ID no Apple Pay).
 
 ## Configurar pagamento com Apple Pay
 
diff --git a/docs/tracks/pt/authenticating-your-google-shopping-account.md b/docs/tracks/pt/authenticating-your-google-shopping-account.md
index 8ddebcca5..a7385b3e3 100644
--- a/docs/tracks/pt/authenticating-your-google-shopping-account.md
+++ b/docs/tracks/pt/authenticating-your-google-shopping-account.md
@@ -24,6 +24,4 @@ Com a integração configurada, é necessário autenticar sua conta do Google Sh
 6. Clique em `Desejo autenticar minha conta`.
 7. Clique no botão `OK` para autorizar a integração VTEX a conectar com o perfil do ID Business Manager.
 
-<div class="alert alert-info">
-Pode haver um delay entre a conclusão da integração e o momento em que ela entra em vigor, pois a atualização não é síncrona. Isso, porém, não costuma levar mais do que poucas horas.
-</div>
+>ℹ️ Pode haver um delay entre a conclusão da integração e o momento em que ela entra em vigor, pois a atualização não é síncrona. Isso, porém, não costuma levar mais do que poucas horas.
diff --git a/docs/tracks/pt/backend-integrations.md b/docs/tracks/pt/backend-integrations.md
index 7c813c5c2..0c56bb739 100644
--- a/docs/tracks/pt/backend-integrations.md
+++ b/docs/tracks/pt/backend-integrations.md
@@ -131,9 +131,7 @@ Após compreender e planejar a [Arquitetura do Catálogo](https://help.vtex.com/
 2. __API do Catálogo:__ criar cada categoria fazendo chamadas de API. Veja os detalhes na [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/category).
 3. __Integração com back-office:__ importar as categorias a partir de um software externo de back-office (ERP ou PIM) integrado à VTEX. O software pode já oferecer integração nativa com a VTEX ou requerer o desenvolvimento de um middleware que utiliza a [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Veja os detalhes em [Migração de Categorias a partir do ERP](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#category-migration-from-erps).
 
-<div class="alert alert-warning">
-Ao importar as categorias de um software externo, a estrutura de categorias no software pode ser diferente da VTEX. Nesse caso, é recomendado criar uma categoria simulada inativa que não será visível no storefront e que pode ser usada para receber todos os produtos e SKUs durante a importação. Após a conclusão da importação, os produtos podem ser arranjados manualmente no Admin VTEX para se adequarem à árvore de categorias desejada.
-</div>
+>⚠️ Ao importar as categorias de um software externo, a estrutura de categorias no software pode ser diferente da VTEX. Nesse caso, é recomendado criar uma categoria simulada inativa que não será visível no storefront e que pode ser usada para receber todos os produtos e SKUs durante a importação. Após a conclusão da importação, os produtos podem ser arranjados manualmente no Admin VTEX para se adequarem à árvore de categorias desejada.
 
 Existem algumas limitações para lidar com categorias, são elas:
 
@@ -150,9 +148,7 @@ Mais informações sobre importação para back-office de categorias no artigo [
 2. __API do Catálogo:__ criar cada marca fazendo chamadas de API. Veja os detalhes na [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/brand).
 3. __Integração com back-office:__ importar as marcas a partir de um software externo de back-office (ERP ou PIM) integrado à VTEX. O software pode já oferecer a integração nativa com a VTEX ou pode requerer o desenvolvimento de um middleware que utiliza a [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Veja os detalhes em [Criar Marcas no guia de configuração do Catálogo para back-office](https://developers.vtex.com/docs/guides/erp-integration-set-up-catalog#create-brands).
 
-<div class="alert alert-warning">
-Caso o sistema de back-office não possua informação sobre marcas, pode ser feito o mesmo procedimento mencionado acima para migração de categorias, criando uma marca simulada inativa, exclusivamente para fins de migração. Posteriormente, as informações dos produtos podem ser inseridas manualmente.
-</div>
+>⚠️ Caso o sistema de back-office não possua informação sobre marcas, pode ser feito o mesmo procedimento mencionado acima para migração de categorias, criando uma marca simulada inativa, exclusivamente para fins de migração. Posteriormente, as informações dos produtos podem ser inseridas manualmente.
 
 Mais informações sobre importação para back-office de marcas para no artigo [Brands](https://developers.vtex.com/docs/guides/brands).
 
@@ -200,9 +196,7 @@ A importação de produtos segue os passos na ordem da tabela abaixo:
 | <a href="https://developers.vtex.com/docs/guides/sku-specifications">5. Importar especificações dos SKUs</a> | Preencher as especificações dos SKUs no Catálogo. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/specification">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119#preencher-especificacoes-de-sku">Admin VTEX</a>.</li></ul> |
 | <a href="https://developers.vtex.com/docs/guides/images">6. Importar imagens dos SKUs</a> | Adicionar imagens aos SKUs. | <ul><li>Integração usando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/stockkeepingunit/-skuId-/file">API do Catálogo</a>.</li><li>Entrada manual no <a href="https://help.vtex.com/pt/tutorial/como-atualizar-a-imagem-de-um-sku--5PMb54FnvUuWOq2qGyAosu">Admin VTEX</a>.</li></ul> |
 
-<div class="alert alert-warning">
-É comum que as informações de produtos no ERP não sejam adequadas para uso e exibição em um ecommerce. Por isso, deve ser feito um processo de enriquecimento, que pode incluir a reestruturação de categorias, e a criação de descrições de produtos mais descritivas e cativantes.
-</div>
+>⚠️ É comum que as informações de produtos no ERP não sejam adequadas para uso e exibição em um ecommerce. Por isso, deve ser feito um processo de enriquecimento, que pode incluir a reestruturação de categorias, e a criação de descrições de produtos mais descritivas e cativantes.
 
 Após a importação, também é importante garantir que as informações sobre produtos e SKUs se mantenham atualizadas. Veja as instruções no artigo [Update or delete information](https://developers.vtex.com/docs/guides/erp-integration-updating-and-deleting-information).
 
diff --git a/docs/tracks/pt/basic-vtex-io-developer-setup.md b/docs/tracks/pt/basic-vtex-io-developer-setup.md
index ad4f0dbe4..ddc3026ae 100644
--- a/docs/tracks/pt/basic-vtex-io-developer-setup.md
+++ b/docs/tracks/pt/basic-vtex-io-developer-setup.md
@@ -40,9 +40,7 @@ Quando estiver logado, você pode usar o comando `vtex whoami` para descobrir qu
 
 ![Command Line](https://images.ctfassets.net/alneenqid6w5/31AVvcWcRpL1CoKdUyARyu/9ea4d722d8955bb580a76402507e4013/Command_Line.svg)
 
-<div class="alert alert-info">
-Dica: Você pode configurar seu terminal para exibir sua conta e workspace atuais automaticamente. A maneira mais fácil de fazer isso é usar nossos <a href="https://github.com/vtex/dotfiles">dotfiles</a>, que configuram automaticamente  a <a href="https://fishshell.com/">Fish Shell</a> e adicionam uma <a href="https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish">função de prompt</a> para você.
-</div>
+>ℹ️ Dica: Você pode configurar seu terminal para exibir sua conta e workspace atuais automaticamente. A maneira mais fácil de fazer isso é usar nossos [dotfiles](https://github.com/vtex/dotfiles), que configuram automaticamente  a [Fish Shell](https://fishshell.com/) e adicionam uma [função de prompt](https://github.com/vtex/dotfiles/blob/master/fish/functions/fish_prompt.fish) para você.
 
 ## Workspaces: seu ambiente de desenvolvimento isolado
 
@@ -66,9 +64,7 @@ $ vtex use seunome
 
 Isso muda o seu toolbelt para um workspace chamado `seunome`, e o cria se ele não existir.
 
-<div class="alert alert-info">
-Dica: Você pode alternar para (<em>e redefinir</em>) um workspace master em um único comando com a flag <code>-r</code>. Isso é útil se você quiser começar do zero no <code>master</code>.
-</div>
+>ℹ️ Dica: Você pode alternar para (*e redefinir*) um workspace master em um único comando com a flag `-r`. Isso é útil se você quiser começar do zero no `master`.
 
 Os workspaces podem ser nomeados arbitrariamente, mas geralmente é conveniente atribuir o seu próprio nome quando você deseja desenvolver em seu ambiente.
 
diff --git a/docs/tracks/pt/cadastrar-preco-base.md b/docs/tracks/pt/cadastrar-preco-base.md
index e3b9bb819..e07c2d200 100644
--- a/docs/tracks/pt/cadastrar-preco-base.md
+++ b/docs/tracks/pt/cadastrar-preco-base.md
@@ -40,9 +40,7 @@ Caso você deseje, é possível cadastrar um **preço de lista** associado ao pr
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">como gerar um Appkey e um AppToken para autenticar suas integrações.</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações.](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para cadastrar o **preço base** de um SKU, você precisa enviar um __PUT__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/cadastrar-tabelas-de-preco.md b/docs/tracks/pt/cadastrar-tabelas-de-preco.md
index b65a8d285..8e5450d43 100644
--- a/docs/tracks/pt/cadastrar-tabelas-de-preco.md
+++ b/docs/tracks/pt/cadastrar-tabelas-de-preco.md
@@ -31,9 +31,7 @@ Siga o passo a passo abaixo para cadastrar as tabelas de preço da sua loja:
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para cadastrar a **tabela de preço**, você precisa enviar um __PUT__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/cadastrar-trava-de-preco.md b/docs/tracks/pt/cadastrar-trava-de-preco.md
index 28217acb5..b214063dc 100644
--- a/docs/tracks/pt/cadastrar-trava-de-preco.md
+++ b/docs/tracks/pt/cadastrar-trava-de-preco.md
@@ -30,9 +30,7 @@ Siga o passo a passo abaixo para cadastrar a trava de preço:
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://developers.vtex.com/vtex-developer-docs/docs/getting-started-authentication)
 
 Para cadastrar a **trava de preço**, você precisa enviar um __POST__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/canceling-an-order.md b/docs/tracks/pt/canceling-an-order.md
index 021466251..1c474bdad 100644
--- a/docs/tracks/pt/canceling-an-order.md
+++ b/docs/tracks/pt/canceling-an-order.md
@@ -19,9 +19,7 @@ trackSlugPT: pedidos
 - Por API.
 - Por solicitação do próprio cliente.
 
-<div class="alert alert-warning">
-Uma vez que o pedido seja cancelado, não é possível alterar o seu status. Pedidos com status <b>Faturado</b> não podem ser cancelados.
-</div>
+>⚠️ Uma vez que o pedido seja cancelado, não é possível alterar o seu status. Pedidos com status **Faturado** não podem ser cancelados.
 
 <div class = "alert alert-info">
 Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
diff --git a/docs/tracks/pt/categories-concept-definition.md b/docs/tracks/pt/categories-concept-definition.md
index dbe32c9c3..8293aeb9a 100644
--- a/docs/tracks/pt/categories-concept-definition.md
+++ b/docs/tracks/pt/categories-concept-definition.md
@@ -20,9 +20,7 @@ Os três principais níveis de categoria são chamados de __Departamento__, __Ca
 
 É na Categoria em que você deve configurar as Especificações (ou Campos), que são as propriedades que você pode adicionar aos seus produtos e SKUs. Mais à frente, veremos com detalhes a relação entre categorias, produtos, SKUs e especificações. 
 
-<div class="alert alert-info">
-Sugerimos que a árvore de categorias da sua loja tenha no máximo, três níveis hierárquicos. Isso facilita a navegação do cliente pela sua loja.  
-</div>
+>ℹ️ Sugerimos que a árvore de categorias da sua loja tenha no máximo, três níveis hierárquicos. Isso facilita a navegação do cliente pela sua loja.
 
 ## Departamento
 
@@ -32,9 +30,7 @@ O __Departamento__ é o primeiro nível de categoria de uma loja. É o nível ma
 
 O segundo nível da árvore de categorias é chamado de __Categoria__. Este nível fica abaixo do __Departamento__ e acima da __Subcategoria__.
 
-<div class="alert alert-info">
-Normalmente, o termo "categoria" é usado para se referir a um conceito genérico de segmentação. Na VTEX, o termo "Categoria" também é usado para se referir ao segundo nível hierárquico de uma árvore de categorias.
-</div>
+>ℹ️ Normalmente, o termo "categoria" é usado para se referir a um conceito genérico de segmentação. Na VTEX, o termo "Categoria" também é usado para se referir ao segundo nível hierárquico de uma árvore de categorias.
 
 ## Subcategoria
 
diff --git a/docs/tracks/pt/changing-the-instore-language.md b/docs/tracks/pt/changing-the-instore-language.md
index 50ed7102b..ee575e768 100644
--- a/docs/tracks/pt/changing-the-instore-language.md
+++ b/docs/tracks/pt/changing-the-instore-language.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: alterar-o-idioma-do-instore
 ---
 
-<div class="alert alert-danger">
-A alteração de idioma explicada neste artigo envolve e alteração do arquivo JavaScript <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A alteração de idioma explicada neste artigo envolve e alteração do arquivo JavaScript `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 Atualmente, é possível usar o inStore em __português__, __inglês__ ou __espanhol__.
 
diff --git a/docs/tracks/pt/como-funciona-o-adaptador-vtex.md b/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
index c09bb816a..88db3d532 100644
--- a/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
+++ b/docs/tracks/pt/como-funciona-o-adaptador-vtex.md
@@ -16,9 +16,7 @@ trackSlugPT: adaptador-vtex
 
 O Adaptador VTEX foi criado para clientes que já possuem integração do ERP com a plataforma de ecommerce CIASHOP. Utilizando o adaptador, o ERP deixará de enviar as informações para a CIASHOP e passará a enviá-las para a VTEX, mantendo a compatibilidade das integrações construídas.
 
-<div class="alert alert-info">
-  <p>Este guia se aplica apenas a lojas que já utilizam a integração entre um ERP e a CIASHOP. Nos demais casos, é necessário seguir o guia para desenvolvedores <a href="https://developers.vtex.com/docs/guides/erp-integration-guide">Back office integration guide (ERP/PIM/WMS)</a> para realizar a integração com um ERP.</p>
-</div>
+>ℹ️ Este guia se aplica apenas a lojas que já utilizam a integração entre um ERP e a CIASHOP. Nos demais casos, é necessário seguir o guia para desenvolvedores [Back office integration guide (ERP/PIM/WMS)](https://developers.vtex.com/docs/guides/erp-integration-guide) para realizar a integração com um ERP.
 
 ![imagem-adaptador-1](https://images.contentful.com/alneenqid6w5/3YzpvrWy5X48siMcATs5Ba/094e532302f3f96a66d21ecee0d96a72/image.png)
 
@@ -35,6 +33,4 @@ Por meio da tabela abaixo, você pode verificar o que a integração do adaptado
 
 ![image-adaptador-2](https://images.ctfassets.net/alneenqid6w5/4TsEw3tXkfK0IEAZlcRzwR/b9dc7e117331beacf34577442c69da0c/Group_1_9_.png)
 
-<div class="alert alert-warning">
-  <p>Para integração via WEBSERVICE, os pedidos na VTEX serão coletados quando estiverem com pagamento aprovado, no status <b>Pronto-para-manuseio</b>.</p>
-</div>
+>⚠️ Para integração via WEBSERVICE, os pedidos na VTEX serão coletados quando estiverem com pagamento aprovado, no status **Pronto-para-manuseio**.
diff --git a/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md b/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md
index bf8c87248..c0a539dc2 100644
--- a/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md
+++ b/docs/tracks/pt/configuracao-da-estrutura-para-suporte-humano.md
@@ -21,9 +21,7 @@ Há duas opções de parceiros pré-integrados com o Conversational Commerce VTE
 * [Zenvia](#integracao-zenvia)
 * [Zendesk](#integracao-zendesk)
 
-<div class="alert alert-info">
-<p>Converse com o time de desenvolvimento da VTEX caso deseje integrar com outras plataformas.</p>
-</div>
+>ℹ️ Converse com o time de desenvolvimento da VTEX caso deseje integrar com outras plataformas.
 
 ## Integração Zenvia
 
diff --git a/docs/tracks/pt/configurar-adaptador.md b/docs/tracks/pt/configurar-adaptador.md
index 5fad82143..63acbb975 100644
--- a/docs/tracks/pt/configurar-adaptador.md
+++ b/docs/tracks/pt/configurar-adaptador.md
@@ -33,9 +33,7 @@ Abaixo você encontrar informações sobre como você efetua a configuração do
 11. Preencha o campo  app-Key com o valor configurado no ambiente VTEX.
 12. Preencha o campo appToken com o valor gerado no ambiente VTEX.
 13. Por fim, clique no botão `SALVAR`. Aguarde o adaptador fazer a validação das configurações junto ao ambiente da VTEX. 
-<div class="alert alert-info">
-<p>Em caso de falha, você deve revisar as configurações inseridas em cada um dos campos. é importante garantir que não existem espaços (Antes e depois) dos valores contidos nas caixas.</p>
-</div>
+>ℹ️ Em caso de falha, você deve revisar as configurações inseridas em cada um dos campos. é importante garantir que não existem espaços (Antes e depois) dos valores contidos nas caixas.
 14. Após a confirmação de sucesso na autenticação, você já pode fechar a tela.
 
 ## Procedimento para configurar campos de controle da integração com ERP
@@ -44,9 +42,7 @@ Você deve criar os campos da tabela abaixo dentro do MasterData.
 
 ![imagem-adaptador-5](https://images.contentful.com/alneenqid6w5/5X8ejWR6ag2C9yv16v8Rjy/ef95d8b91860e8a3b1c170e067f15030/image.png)
 
-<div class="alert alert-warning">
-<p>Você deve criar estes campos antes de executar as operações de migração de dados da Ciashop para VTEX.</p>
-</div>
+>⚠️ Você deve criar estes campos antes de executar as operações de migração de dados da Ciashop para VTEX.
 
 Você deve criar os campos acima individualmente, para isso siga os passos a seguir:
 
@@ -74,9 +70,7 @@ Para colocar o campo criado dentro do fórmulário de clientes, você deve segui
 7. Arraste o campo da lista **Campos disponíveis** para coluna **Campos da coluna 2**.
 8. No canto inferior direito da tela, clique no botão `Salvar`.
 
-<div class="alert alert-warning">
-<p>Caso estes passos não sejam executados, não será possível enviar os clientes criados na VTEX para o ERP.</p>
-</div>
+>⚠️ Caso estes passos não sejam executados, não será possível enviar os clientes criados na VTEX para o ERP.
 
 ## Configurar campos customizados
 
diff --git a/docs/tracks/pt/configurar-erps.md b/docs/tracks/pt/configurar-erps.md
index 9f7feb824..4a93d8d1a 100644
--- a/docs/tracks/pt/configurar-erps.md
+++ b/docs/tracks/pt/configurar-erps.md
@@ -60,9 +60,7 @@ O código da tabela de preços no ERP deve ser cadastrada manualmente na VTEX ut
 2. Na lista de preços, abra o campo **PriceTables(1)** e, em seguida, clique em `+ Create New Price Tables`.
 3. No campo **Type the name of the price table that you want to create**, insira o código da tabela que você coletou do ERP (deve ser exatamente igual).
 
-<div class="alert alert-warning">
-  <p>O código da tabela de preços no ERP deve conter letras e números.</p>
-</div>  
+>⚠️ O código da tabela de preços no ERP deve conter letras e números.  
 
 ### Configurar a integração das Transportadoras
 
diff --git a/docs/tracks/pt/configure-clustered-conditions.md b/docs/tracks/pt/configure-clustered-conditions.md
index a486d161b..992169d9d 100644
--- a/docs/tracks/pt/configure-clustered-conditions.md
+++ b/docs/tracks/pt/configure-clustered-conditions.md
@@ -16,17 +16,13 @@ trackSlugPT: condicoes-de-pagamento-clusterizadas
 
 Como mencionamos, a Clustered Payment Conditions define que uma condição de pagamento será aplicada para um ou mais consumidores. 
 
-<div class="alert alert-warning">
-A clusterização de clientes pode ser aplicada em condições de pagamento que foram configuradas previamente. 
-
-Isso significa que você pode editar condições de pagamento que já existem e aplicar condições de clusterização a essas regras. 
-</div>  
+>⚠️ A clusterização de clientes pode ser aplicada em condições de pagamento que foram configuradas previamente. 
+>
+> Isso significa que você pode editar condições de pagamento que já existem e aplicar condições de clusterização a essas regras.  
 
 Aqui, explicaremos como configurar uma condição especial de pagamento a partir de clusters.
 
-<div class="alert alert-danger">
-<strong>Atenção</strong>: só é permitido criar cinco clusters de clientes por condição de pagamento.
-</div>
+>❗ **Atenção**: só é permitido criar cinco clusters de clientes por condição de pagamento.
 
 ## Criar uma nova condição de pagamento
 
diff --git a/docs/tracks/pt/configure-integration-of-pick-up-points.md b/docs/tracks/pt/configure-integration-of-pick-up-points.md
index 8909bb3e2..7605ef5d0 100644
--- a/docs/tracks/pt/configure-integration-of-pick-up-points.md
+++ b/docs/tracks/pt/configure-integration-of-pick-up-points.md
@@ -22,9 +22,7 @@ Quando os pedidos que utilizam a opção de retirada em loja chegam à VTEX, sã
 
 ![configurar pontosderetirada01 PT](https://images.contentful.com/alneenqid6w5/6V2QIEoUaOUIqNLf5Nfrg6/4a10e2e330c1fa333bbd62f34cf6bcc5/configurar_pontosderetirada01_PT.JPG)
 
-<div class="alert alert-info">
-Antes de criar os pontos de retirada, você deve solicitar ao Mercado Livre a ativação da modalidade de Retirada em Loja. Para isso, entre em contato com o seu assessor comercial do Mercado Livre ou abra um chamado com o time de <a href="https://developers.mercadolivre.com.br/devcenter/support">Suporte.</a>
-</div>
+>ℹ️ Antes de criar os pontos de retirada, você deve solicitar ao Mercado Livre a ativação da modalidade de Retirada em Loja. Para isso, entre em contato com o seu assessor comercial do Mercado Livre ou abra um chamado com o time de [Suporte.](https://developers.mercadolivre.com.br/devcenter/support)
 
 Para criar os pontos de retirada, você vai precisar:
 
diff --git a/docs/tracks/pt/configure-integration.md b/docs/tracks/pt/configure-integration.md
index 35c7fbc6b..3a6a9e64c 100644
--- a/docs/tracks/pt/configure-integration.md
+++ b/docs/tracks/pt/configure-integration.md
@@ -66,7 +66,5 @@ O preenchimento desse campo deve ser realizado da seguinte maneira:
 2. Preencha o campo PARA com o nome do novo campo.   `MGZ_ProductName` para nome do produto e `MGZ_ProductDescription` para descrição do produto.    
 3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
-</div>
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.
diff --git a/docs/tracks/pt/configuring-cash-payments-through-instore.md b/docs/tracks/pt/configuring-cash-payments-through-instore.md
index a4155eaa7..a1a80a363 100644
--- a/docs/tracks/pt/configuring-cash-payments-through-instore.md
+++ b/docs/tracks/pt/configuring-cash-payments-through-instore.md
@@ -38,6 +38,4 @@ Agora vamos criar a condição de pagamento.
 4. Dê um nome para essa condição de pagamento, mude o status para **Ativa** e, no seletor **Processar com a afiliação**, escolha o pagamento customizado que você criou no passo anterior.
 5. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Além das configurações acima, é necessário seguir o guia <strong><a href="https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1">Definir meios de pagamento exibidos no VTEX Sales App</a></strong> para que as opções de pagamento sejam exibidas corretamente no aplicativo.</p>
-</div>
+>ℹ️ Além das configurações acima, é necessário seguir o guia **[Definir meios de pagamento exibidos no VTEX Sales App](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1)** para que as opções de pagamento sejam exibidas corretamente no aplicativo.
diff --git a/docs/tracks/pt/configuring-dafiti-connector.md b/docs/tracks/pt/configuring-dafiti-connector.md
index 4be568d22..dd2b2132b 100644
--- a/docs/tracks/pt/configuring-dafiti-connector.md
+++ b/docs/tracks/pt/configuring-dafiti-connector.md
@@ -42,9 +42,7 @@ A configuração do conector é feita no Admin. Para realizá-la, siga as instru
 
 - **Enviar KIT*:** ao escolher _Não_, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Dafiti. Ao habilitar _Sim_, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de _Sim_ para _Não_, SKUs enviados anteriormente para a Dafiti não seriam removidos ou sofreriam qualquer alteração.
 
-  <div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a Dafiti de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>Marketplace> Conexões> Produtos,</b> ao se clicar sobre o SKU.
-</div>
+  >ℹ️ Com a opção <i>Não</i> ativada, tentativas de envio para a Dafiti de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo **Marketplace> Conexões> Produtos,** ao se clicar sobre o SKU.
 
 - **Nome do SKU*:** determina qual será a regra para nomeação de SKUs no portal da Dafiti. Você deve selecionar uma das combinações disponíveis dos seguintes atributos: _Marca_, _Nome do Produto_ e _Nome do SKU_.
 
@@ -74,8 +72,6 @@ O preenchimento desse campo deve ser realizado da seguinte maneira:
 2. Preencha o campo PARA com o nome do novo campo. `DFT_ProductName` para nome do produto e `DFT_ProductDescription` para descrição do produto.  
 3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
-</div>
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.
 
diff --git a/docs/tracks/pt/configuring-livelo-price-divergence-rule.md b/docs/tracks/pt/configuring-livelo-price-divergence-rule.md
index d721220a9..30775c0a4 100644
--- a/docs/tracks/pt/configuring-livelo-price-divergence-rule.md
+++ b/docs/tracks/pt/configuring-livelo-price-divergence-rule.md
@@ -21,13 +21,9 @@ No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedido
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar 
 automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido.    
 
-<div class="alert alert-warning">
-Para que a regra de Divergência de valores seja válida, após a configuração é
-necessário enviar o campo `isCreatedAsync` na API <a href="https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders">Place fulfillment order</a>, independente do tipo de conector utilizado, seja ele, marketplace externo, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outros <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Livelo.  
-</div>  
+>⚠️ Para que a regra de Divergência de valores seja válida, após a configuração é
+> necessário enviar o campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders), independente do tipo de conector utilizado, seja ele, marketplace externo, [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outros [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex) além da Livelo.  
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Livelo. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores e o envio do campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders). Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos,** ou digite **Pedidos** na barra de busca.  
 
-<div class="alert alert-warning">
-Incrementos de preço superiores a 20% do valor atual do produto só serão atualizados no sistema se realizados de forma gradual.
-</div>  
+>⚠️ Incrementos de preço superiores a 20% do valor atual do produto só serão atualizados no sistema se realizados de forma gradual.  
diff --git a/docs/tracks/pt/configuring-merchandising-rules.md b/docs/tracks/pt/configuring-merchandising-rules.md
index 544cb91ac..ffa8b7195 100644
--- a/docs/tracks/pt/configuring-merchandising-rules.md
+++ b/docs/tracks/pt/configuring-merchandising-rules.md
@@ -32,9 +32,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
     Para aplicar o efeito de customização desejado, é necessário cadastrar uma ou mais condições nesta etapa. Para entender como funciona o cadastro de uma condição, leia [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
 10. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
-</div>
+>ℹ️ Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.
 
 ## Exemplo
 
@@ -77,9 +75,7 @@ Considere o seguinte exemplo: você quer promover produtos da marca Beautyx dura
 
 * **Remover:** exclui as condições selecionadas do resultado, ou seja, remove produtos que estariam no resultado de busca.
 
-  <div class="alert alert-info">
-   <p><strong>Adicionar</strong> e <strong>Remover</strong> são compatíveis com outros tipos de ordenação que não são baseadas na relevância configurada. Ou seja, se você adicionar ou remover um produto através de uma regra de merchandising e o cliente da sua loja ordenar os resultados da busca por preço, por exemplo, os produtos serão ordenados por preço mas os produtos exibidos vão respeitar a regra de merchandising.</p>
-  </div>
+  >ℹ️ **Adicionar** e **Remover** são compatíveis com outros tipos de ordenação que não são baseadas na relevância configurada. Ou seja, se você adicionar ou remover um produto através de uma regra de merchandising e o cliente da sua loja ordenar os resultados da busca por preço, por exemplo, os produtos serão ordenados por preço mas os produtos exibidos vão respeitar a regra de merchandising.
 
 * **Promover:** oferece destaque às condições selecionadas no resultado. Isso concede maior relevância a um produto que já seria exibido no resultado de busca.
 
@@ -87,10 +83,6 @@ Considere o seguinte exemplo: você quer promover produtos da marca Beautyx dura
 
 * **Despromover**: oculta as condições selecionadas no resultado. Isso permite despriorizar um produto que já seria exibido no resultado de busca.
 
-  <div class="alert alert-info">
-   <p><strong>Promover </strong>e <strong>Despromover </strong>funcionam somente quando o cliente da sua loja ordena os resultados da busca por relevância. Caso ele(a) ordene os resultados por preço, por exemplo, os produtos serão ordenados estritamente pelo preço e a regra de merchandising não será utilizada.</p>
-  </div>
+  >ℹ️ **Promover **e **Despromover **funcionam somente quando o cliente da sua loja ordena os resultados da busca por relevância. Caso ele(a) ordene os resultados por preço, por exemplo, os produtos serão ordenados estritamente pelo preço e a regra de merchandising não será utilizada.
 
-  <div class="alert alert-warning">
-   <p>Não configure condições que afetem os mesmos produtos nas seções <strong>Promover</strong> e <strong>Despromover</strong>, pois são efeitos contrários. Essa configuração equivocada influencia negativamente no comportamento da funcionalidade e não apresenta os resultados desejados.</p>
-  </div>
+  >⚠️ Não configure condições que afetem os mesmos produtos nas seções **Promover** e **Despromover**, pois são efeitos contrários. Essa configuração equivocada influencia negativamente no comportamento da funcionalidade e não apresenta os resultados desejados.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-amazon.md b/docs/tracks/pt/configuring-price-divergence-rule-amazon.md
index 465102f3b..214b6d3ab 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-amazon.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-amazon.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Amazon.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Amazon.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Amazon. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-carrefour.md b/docs/tracks/pt/configuring-price-divergence-rule-carrefour.md
index 27b12682b..a7809fd9c 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-carrefour.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-carrefour.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Carrefour.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Carrefour.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com o Carrefour. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-centauro.md b/docs/tracks/pt/configuring-price-divergence-rule-centauro.md
index 502d7d98f..fec9d1946 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-centauro.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-centauro.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Centauro.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Centauro.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Centauro. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md b/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md
index d8fffeb3d..f255bbeda 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-dafiti.md
@@ -20,9 +20,7 @@ No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Para que a regra de Divergência de valores seja válida, após a configuração é
-necessário enviar o campo `isCreatedAsync` na API <a href="https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders">Place fulfillment order</a>, independente do tipo de conector utilizado, seja ele, marketplace externo, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outros <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Dafiti.  
-</div>  
+>⚠️ Para que a regra de Divergência de valores seja válida, após a configuração é
+> necessário enviar o campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders), independente do tipo de conector utilizado, seja ele, marketplace externo, [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outros [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex) além da Dafiti.  
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Dafiti. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos,** ou digite **Pedidos** na barra de busca.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-magazine-luiza.md b/docs/tracks/pt/configuring-price-divergence-rule-magazine-luiza.md
index c48c118c4..d69224f7a 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-magazine-luiza.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-magazine-luiza.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Magalu.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Magalu.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com o Magazine Luiza. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md b/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md
index 2a2ddb761..c7a8ad951 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-mercado-libre.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedidos
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Mercado Livre.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além do Mercado Livre.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com o Mercado Livre. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-netshoes.md b/docs/tracks/pt/configuring-price-divergence-rule-netshoes.md
index 17f047a19..422591dc1 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-netshoes.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-netshoes.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Netshoes.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Netshoes.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Netshoes. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule-via.md b/docs/tracks/pt/configuring-price-divergence-rule-via.md
index 353028d76..148265126 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule-via.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule-via.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Casas Bahia Marketplace.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Casas Bahia Marketplace.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Casas Bahia Marketplace. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-price-divergence-rule.md b/docs/tracks/pt/configuring-price-divergence-rule.md
index 8289f9121..73b7a7b11 100644
--- a/docs/tracks/pt/configuring-price-divergence-rule.md
+++ b/docs/tracks/pt/configuring-price-divergence-rule.md
@@ -20,8 +20,6 @@ No Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos > Autorização de pedido
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido. 
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da B2W.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você atue como seller. Podem ser marketplaces VTEX, marketplaces externos, <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conectores certificados (parceiros)</a> ou outros <a href= "https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da B2W.
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a B2W. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores. Será possível acompanhá-los no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**.
diff --git a/docs/tracks/pt/configuring-rappi-price-divergence-rule.md b/docs/tracks/pt/configuring-rappi-price-divergence-rule.md
index c81057a70..92d9f8dbe 100644
--- a/docs/tracks/pt/configuring-rappi-price-divergence-rule.md
+++ b/docs/tracks/pt/configuring-rappi-price-divergence-rule.md
@@ -21,9 +21,7 @@ No Admin VTEX, em **Configurações da loja > Pedidos > Autorização de pedido
 A regra de Divergência de valores é composta de uma ou mais regras de autorização, sendo que cada uma delas corresponde a um intervalo percentual do preço do pedido. As regras de autorização podem ser configuradas para negar 
 automaticamente, aprovar automaticamente, ou exigir autorização manual do pedido.    
 
-<div class="alert alert-warning">
-Para que a regra de Divergência de valores seja válida, após a configuração é
-necessário enviar o campo `isCreatedAsync` na API <a href="https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders">Place fulfillment order</a>, independente do tipo de conector utilizado, seja ele, marketplace externo, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outros <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> além da Rappi.  
-</div>  
+>⚠️ Para que a regra de Divergência de valores seja válida, após a configuração é
+> necessário enviar o campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders), independente do tipo de conector utilizado, seja ele, marketplace externo, [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outros [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex) além da Rappi.  
 
 É recomendável que a configuração da regra de Divergência de valores seja feita antes de você seguir para a próxima etapa da configuração da integração com a Rappi. Descumprir esta recomendação não impede que a integração seja concluída, mas pedidos com divergência de preço ficarão retidos até a criação da regra de Divergência de valores e o envio do campo `isCreatedAsync` na API [Place fulfillment order](https://developers.vtex.com/docs/api-reference/marketplace-protocol-external-marketplace-orders#post-/api/fulfillment/pvt/orders). Será possível acompanhá-los no Admin VTEX, em **Marketplace > Conexões > Pedidos,** ou digite **Pedidos** na barra de busca.  
diff --git a/docs/tracks/pt/configuring-ship-from-store.md b/docs/tracks/pt/configuring-ship-from-store.md
index 3208e88c2..166104fe4 100644
--- a/docs/tracks/pt/configuring-ship-from-store.md
+++ b/docs/tracks/pt/configuring-ship-from-store.md
@@ -28,9 +28,7 @@ Antes de mais nada, verifique os pré-requisitos que sua loja precisa garantir p
 
 ## Implementar Ship From Store
 
-<div class="alert alert-info">
-Embora seja possível implementar Ship From Store de outras maneiras, neste artigo vamos explicar como fazê-lo usando as features de Contra-franquia e Seller White Label. Isto porque essa é a arquitetura mais recomendada pela VTEX para esse tipo de projeto.
-</div>
+>ℹ️ Embora seja possível implementar Ship From Store de outras maneiras, neste artigo vamos explicar como fazê-lo usando as features de Contra-franquia e Seller White Label. Isto porque essa é a arquitetura mais recomendada pela VTEX para esse tipo de projeto.
 
 Estes são os passos para implementar o __Ship From Store__:
 
diff --git a/docs/tracks/pt/configuring-synonyms.md b/docs/tracks/pt/configuring-synonyms.md
index 0294d7ecd..028cd1365 100644
--- a/docs/tracks/pt/configuring-synonyms.md
+++ b/docs/tracks/pt/configuring-synonyms.md
@@ -89,6 +89,4 @@ Lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/p
      __Exemplo:__
      - `tv,smart tv;true;en-GB`: ao pesquisar por qualquer um dos termos na loja no idioma inglês (`locale = en-GB`), qualquer produto que contenha um desses termos irá aparecer nos resultados da busca.
 
-<div class="alert alert-warning">
-<p> Se o arquivo CSV importado não apresentar o <code>locale</code>, o sinônimo será válido para todos os idiomas disponíveis na loja.</p>
-</div>
+>⚠️ Se o arquivo CSV importado não apresentar o `locale`, o sinônimo será válido para todos os idiomas disponíveis na loja.
diff --git a/docs/tracks/pt/configuring-the-amazon-integration.md b/docs/tracks/pt/configuring-the-amazon-integration.md
index e270fd20d..4429e5b66 100644
--- a/docs/tracks/pt/configuring-the-amazon-integration.md
+++ b/docs/tracks/pt/configuring-the-amazon-integration.md
@@ -33,9 +33,7 @@ Uma vez terminadas as etapas de preparo da sua loja na VTEX e na Amazon, é nece
 - __Não enviar preço para a Amazon:__ a Amazon dá a possibilidade de usar o próprio sistema deles para parametrização de preços nos produtos. Para utilizar este serviço, marque a opção *ON* para que a integração não envie os preços da VTEX. Pois, se os preços forem enviados via integração, eles irão sobrescrever os preços do sistema da Amazon.
 - **Enviar KIT*:** ao escolher *Não*, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Amazon. Ao habilitar *Sim*, todos os itens da sua política comercial são enviados para o marketplace, inclusive SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sem que isso afete SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de *Sim* para *Não*, SKUs enviados anteriormente para a Amazon não seriam removidos nem sofreriam qualquer alteração.
 
-<div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a Amazon de SKUs cadastrados como kit resultarão no seguinte aviso: “o conector está configurado para não enviar SKUs do tipo Kit”. Esta mensagem pode ser visualizada no Admin VTEX, no módulo <b>MARKETPLACE > Integrações > Produtos</b>, ao se clicar sobre o SKU.
-</div>
+>ℹ️ Com a opção <i>Não</i> ativada, tentativas de envio para a Amazon de SKUs cadastrados como kit resultarão no seguinte aviso: “o conector está configurado para não enviar SKUs do tipo Kit”. Esta mensagem pode ser visualizada no Admin VTEX, no módulo **MARKETPLACE > Integrações > Produtos**, ao se clicar sobre o SKU.
 
 - **Notificar por e-mail se ocorrer um erro em um pedido:** preencher com o e-mail do responsável técnico. Caso ocorra algum erro na integração do pedido, será enviada uma mensagem para o e-mail cadastrado.
 
diff --git a/docs/tracks/pt/configuring-the-connector-b2w.md b/docs/tracks/pt/configuring-the-connector-b2w.md
index a3f59d84a..7ca842b1a 100644
--- a/docs/tracks/pt/configuring-the-connector-b2w.md
+++ b/docs/tracks/pt/configuring-the-connector-b2w.md
@@ -72,9 +72,7 @@ Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `Prod
 `B2W_ProductName` para nome do produto e `B2W_ProductDescription` para descrição do produto.    
 3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
-</div>
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.
 
 Após salvar a configuração, a integração envia automaticamente todos os produtos associados à política comercial determinada para a SkyHub, a integradora com a B2W.
diff --git a/docs/tracks/pt/configuring-the-google-shopping-integration.md b/docs/tracks/pt/configuring-the-google-shopping-integration.md
index 5979f0d28..b9b2e370b 100644
--- a/docs/tracks/pt/configuring-the-google-shopping-integration.md
+++ b/docs/tracks/pt/configuring-the-google-shopping-integration.md
@@ -16,9 +16,7 @@ trackSlugPT: configurar-integracao-com-o-google-shopping
 
 Este guia orienta como integrar com Google Shopping através do conector desenvolvido pela VTEX, que deve ser sua escolha padrão, pois representa mais eficiência e segurança.
 
-<div class="alert alert-danger">
-A integração pode ser <a href="https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242">configurada por arquivo XML</a> . É desaconselhável realizar simultaneamente a <a href="https://help.vtex.com/pt/tutorial/como-configurar-xml-do-google-shopping--frequentlyAskedQuestions_372">configuração XML do Google Shopping</a> e do conector nativo, pois isso acarreta conflitos e divergência de informações. 
-</div>
+>❗ A integração pode ser [configurada por arquivo XML](https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242) . É desaconselhável realizar simultaneamente a [configuração XML do Google Shopping](https://help.vtex.com/pt/tutorial/como-configurar-xml-do-google-shopping--frequentlyAskedQuestions_372) e do conector nativo, pois isso acarreta conflitos e divergência de informações.
 
 Para realizar a integração por conector, **é indispensável possuir uma conta no Google Merchant Center.**  Caso você ainda não tenha uma, confira o tutorial do Google [Inscrever-se no Google Merchant Center](https://support.google.com/merchants/answer/188924?hl=pt-BR&ref_topic=7294166).
 
diff --git a/docs/tracks/pt/configuring-the-integration-dafiti.md b/docs/tracks/pt/configuring-the-integration-dafiti.md
index c3c612e00..f39442af6 100644
--- a/docs/tracks/pt/configuring-the-integration-dafiti.md
+++ b/docs/tracks/pt/configuring-the-integration-dafiti.md
@@ -22,6 +22,4 @@ Após a conclusão do [cadastro no portal da Dafiti](https://www.dafiti.com.br/q
 2. [Configurar conector](https://help.vtex.com/pt/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i/3PV2OACP2E4O4uOKKW2sMg).
 3. [Enviar produtos para a Dafiti](https://help.vtex.com/pt/tracks/configurar-integracao-da-dafiti--4wF4RBx9ygEkimW6SsKw8i/3b8BZfB1BC8G8SCe0ao46m).
 
-<div class="alert alert-warning">
-É importante que a transportadora cadastrada na VTEX seja aceita pela Dafiti, caso contrário, um erro de rastreamento no pedido será gerado. Além disso, o nome cadastrado da transportadora precisa estar rigorosamente igual ao nome aceito pela Dafiti. Entre em contato com a Dafiti para para verificar quais os nomes aceitos.
-</div>
+>⚠️ É importante que a transportadora cadastrada na VTEX seja aceita pela Dafiti, caso contrário, um erro de rastreamento no pedido será gerado. Além disso, o nome cadastrado da transportadora precisa estar rigorosamente igual ao nome aceito pela Dafiti. Entre em contato com a Dafiti para para verificar quais os nomes aceitos.
diff --git a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 7c8baf56a..445130972 100644
--- a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -33,9 +33,7 @@ Independente de você ter instalado a <a href= "https://apps.vtex.com/vtex-faceb
 8. Em seguida, clique em `Continuar`.
 9. Escolha quais permissões devem ser conferidas à VTEX na integração.
 
-  <div class="alert alert-danger">
-Para que a integração funcione corretamente, o recomendável é conceder todas as permissões apresentadas. Por padrão, elas aparecem como habilitadas.
-</div>
+  >❗ Para que a integração funcione corretamente, o recomendável é conceder todas as permissões apresentadas. Por padrão, elas aparecem como habilitadas.
 
 10. Clique em `Avançar`.
 11. Na janela aberta, aparecerá uma confirmação de que a integração foi realizada. Clique em `Concluir`.
diff --git a/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
index d8ed2a9d0..7e0d9ea01 100644
--- a/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -42,9 +42,7 @@ Nesta parte do formulário, você precisa preencher informações que servirão
 * **ID do Afiliado:** identificador do novo [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) que você deseja criar para a integração. O ID do afiliado precisa conter apenas 3 consoantes e não pode estar associado a um afiliado já existente. Sugerimos utilizar `TKT` para identificar o TikTok com facilidade. É importante verificar em **Gerenciamento de pedidos > Configurações > Afiliados** se o ID não está em uso. O afiliado será criado automaticamente ao concluir a configuração. 
 * **Política Comercial:** campo para selecionar a [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será associada à integração do catálogo com o TikTok. Atualmente, a integração aceita apenas políticas comerciais com BRL como moeda. Confira a seção [Envio de dados dos produtos para o TikTok](#envio-de-dados-dos-produtos-para-o-tiktok) para mais informações.
 
-<div class="alert alert-warning">
-  <p>Não altere as configurações do afiliado criado automaticamente por essa integração. Qualquer alteração manual futura na configuração do afiliado em <strong>Gerenciamento de pedidos > Configurações > Afiliados</strong> pode fazer com que a integração pare de funcionar.</p>
-</div>
+>⚠️ Não altere as configurações do afiliado criado automaticamente por essa integração. Qualquer alteração manual futura na configuração do afiliado em **Gerenciamento de pedidos > Configurações > Afiliados** pode fazer com que a integração pare de funcionar.
 
 ### Dados da Empresa
 
@@ -109,9 +107,7 @@ Ao concluir essa configuração, você será conduzido novamente para **Marketpl
 
 ### Envio de dados dos produtos para o TikTok
 
-<div class="alert alert-warning">
-  <p>O TikTok sincroniza apenas produtos que estão de acordo com as políticas de publicidade da plataforma. Leia as <a href="https://ads.tiktok.com/help/article?aid=9550&lang=pt">Políticas de Anúncios do TikTok</a> para mais informações.</p>
-</div>
+>⚠️ O TikTok sincroniza apenas produtos que estão de acordo com as políticas de publicidade da plataforma. Leia as [Políticas de Anúncios do TikTok](https://ads.tiktok.com/help/article?aid=9550&lang=pt) para mais informações.
 
 Com a integração configurada, o envio de produtos para o TikTok é um processo automático. Os dados enviados são:
 
diff --git a/docs/tracks/pt/configuring-the-integration.md b/docs/tracks/pt/configuring-the-integration.md
index 841e35504..15a581730 100644
--- a/docs/tracks/pt/configuring-the-integration.md
+++ b/docs/tracks/pt/configuring-the-integration.md
@@ -18,9 +18,7 @@ trackSlugPT: integracao-livelo
 
 O primeiro passo para integrar sua loja VTEX à Livelo é ter as credenciais **AppKey** e **AppToken**, ambas são utilizadas para validar sua integração com o Marketplace.
 
-<div class="alert alert-danger">
-Para obter as suas credenciais e iniciar a integração, entre em contato através com o time de <a href="https://help.vtex.com/pt/support">suporte da VTEX</a>. 
-</div>
+>❗ Para obter as suas credenciais e iniciar a integração, entre em contato através com o time de [suporte da VTEX](https://help.vtex.com/pt/support).
 
 Após solicitar as credenciais, o seller pode seguir com as [Configurações da plataforma VTEX](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/HgIbZEzbPr8FQid5MXURQ#conguracoes-na-plataforma-vtex) e configuração da [Regra de divergência.](https://help.vtex.com/pt/tracks/integracao-livelo--4ZSHEiuTkh8HR9ubJQj8BP/4kocvdsHiLcLLcX6eQIVmD)
 
diff --git a/docs/tracks/pt/create-a-product.md b/docs/tracks/pt/create-a-product.md
index 7521baec3..42824517d 100644
--- a/docs/tracks/pt/create-a-product.md
+++ b/docs/tracks/pt/create-a-product.md
@@ -16,13 +16,9 @@ trackSlugPT: vtex-getting-started
 
 Antes de mais nada, é importante entender a diferença entre SKU e produto - esta diferença diz respeito à plataforma VTEX, mas também ao tratamento dado a esses conceitos pela maioria das operações de e-commerce.
 
-<div class="alert alert-info">
-<strong>SKU:</strong> a menor unidade possível dos itens vendidos na loja. Estoque e preço, por exemplo, são propriedades do SKU.
-</div>
+>ℹ️ **SKU:** a menor unidade possível dos itens vendidos na loja. Estoque e preço, por exemplo, são propriedades do SKU.
 
-<div class="alert alert-info">
-<strong>Produto:</strong> agregador de SKUs.
-</div>
+>ℹ️ **Produto:** agregador de SKUs.
 
 Veja os exemplos abaixo:
 
@@ -34,9 +30,7 @@ Veja os exemplos abaixo:
 Na vitrine da loja, o cliente verá apenas o produto __Calça jeans__, e não três produtos separados: "Calça jeans P", "Calça jeans M" e "Calça jeans G". 
 Já a gestão do seu estoque enxerga separadamente cada um dos SKUs que compõem esse produto. Assim ele consegue saber, por exemplo, que você tem 50 calças jeans M em estoque, mas apenas 2 calças jeans G.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: Sempre que for criar um SKU, você precisa antes criar o produto.
-</div>
+>ℹ️ **Atenção**: Sempre que for criar um SKU, você precisa antes criar o produto.
 
 Vamos ver como criar o produto.
 
diff --git a/docs/tracks/pt/create-an-account.md b/docs/tracks/pt/create-an-account.md
index 473b0f812..478cc691c 100644
--- a/docs/tracks/pt/create-an-account.md
+++ b/docs/tracks/pt/create-an-account.md
@@ -18,8 +18,6 @@ Ao contratar a VTEX, a loja recebe um account, ou seja, a conta da loja. É ele
 
 Para desenvolver no VTEX IO, é preciso antes de mais nada ter acesso ao account de uma loja. 
 
-<div class="alert alert-info">
-Toda app criada com o VTEX IO é desenvolvida no contexto de um account VTEX. 
-</div>
+>ℹ️ Toda app criada com o VTEX IO é desenvolvida no contexto de um account VTEX.
 
 Caso você ainda não tenha acesso a nenhum account e precise criar um, entre em contato com o time comercial da VTEX e depois leia o artigo sobre como [vincular seu account name a um website](/pt/tutorial/vincular-um-account-name-a-um-website-binding).
diff --git a/docs/tracks/pt/create-an-sku.md b/docs/tracks/pt/create-an-sku.md
index 40bca3c38..e1054ec0b 100644
--- a/docs/tracks/pt/create-an-sku.md
+++ b/docs/tracks/pt/create-an-sku.md
@@ -33,6 +33,4 @@ Você será levado para a tela de cadastro de SKU.
 
 Todos os campos disponíveis nessa tela estão listados no artigo [Campos de cadastro de SKU](/pt/tutorial/campos-de-cadastro-de-sku).
 
-<div class="alert alert-info">
-Às vezes um produto não tem variações que justifiquem a criação de mais de um SKU para ele. Nesse caso, não há nenhum problema em criar um SKU com o mesmo nome do produto. Apenas lembre-se que você sempre precisa criar <strong>pelo menos um SKU para cada produto</strong>.
-</div>
+>ℹ️ Às vezes um produto não tem variações que justifiquem a criação de mais de um SKU para ele. Nesse caso, não há nenhum problema em criar um SKU com o mesmo nome do produto. Apenas lembre-se que você sempre precisa criar **pelo menos um SKU para cada produto**.
diff --git a/docs/tracks/pt/create-the-category-tree.md b/docs/tracks/pt/create-the-category-tree.md
index 870aa155e..171da6266 100644
--- a/docs/tracks/pt/create-the-category-tree.md
+++ b/docs/tracks/pt/create-the-category-tree.md
@@ -22,9 +22,7 @@ Então é por ela que precisamos começar.
 
 ## O que é uma árvore de categorias?
 
-<div class="alert alert-info">
-A árvore de categorias é o conjunto de categorias do seu site, <strong>distribuídas segundo relações de hierarquia</strong>.
-</div>
+>ℹ️ A árvore de categorias é o conjunto de categorias do seu site, **distribuídas segundo relações de hierarquia**.
 
 ## Exemplo
 
@@ -44,15 +42,11 @@ __OBS__: a nomenclatura __Departamento / Categoria / Subcategoria__ é apenas um
 
 Mas atenção:
 
-<div class="alert alert-warning">
-Recomendamos que sejam criados <strong>no máximo 3 níveis de categoria</strong>. Mais níveis podem tornar a operação do seu catálogo muito complexa.
-</div>
+>⚠️ Recomendamos que sejam criados **no máximo 3 níveis de categoria**. Mais níveis podem tornar a operação do seu catálogo muito complexa.
 
 Dois pontos fundamentais:
 
 - Quem planeja a distribuição das categorias do seu site? __Você! Esse planejamento deve refletir os objetivos do seu negócio.__
 - Quando a distribuição das categorias deve ser definida? __Antes que as categorias sejam de fato inseridas no site.__
 
-<div class="alert alert-warning">
-É muito importante que sua equipe defina a composição da árvore de categorias <strong>antes</strong> de montá-la na plataforma. Depois que você começar a inserir produtos, precisar mover categorias pode se tornar uma dor de cabeça.
-</div>
+>⚠️ É muito importante que sua equipe defina a composição da árvore de categorias **antes** de montá-la na plataforma. Depois que você começar a inserir produtos, precisar mover categorias pode se tornar uma dor de cabeça.
diff --git a/docs/tracks/pt/creating-accounts.md b/docs/tracks/pt/creating-accounts.md
index 27e8be490..810ad13e5 100644
--- a/docs/tracks/pt/creating-accounts.md
+++ b/docs/tracks/pt/creating-accounts.md
@@ -20,9 +20,7 @@ O próximo passo é criar contas para os clientes que você deseja oferecer cré
 - [Múltiplas contas em massa (Admin VTEX)](#criar-multiplas-contas-importacao-em-massa)
 - [Conta individual (Customer Credit API)](#criar-conta-via-api)
 
-<div class="alert alert-info">
-As contas criadas na app do Customer Credit não tem relação ou compartilham dados com a base de clientes cadastrada nas <a href="https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-dados">entidades do Master Data</a> da loja. Para que um cliente possa utilizar o Customer Credit como meio de pagamento, a sua conta deve ser cadastrada pelo lojista na app mesmo que o cliente já possua uma conta na loja. 
-</div>
+>ℹ️ As contas criadas na app do Customer Credit não tem relação ou compartilham dados com a base de clientes cadastrada nas [entidades do Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#entidades-de-dados) da loja. Para que um cliente possa utilizar o Customer Credit como meio de pagamento, a sua conta deve ser cadastrada pelo lojista na app mesmo que o cliente já possua uma conta na loja.
 
 ## Criar contas individualmente
 
@@ -34,9 +32,7 @@ Para cadastrar um novo cliente no Customer Credit, siga os passos abaixo:
 4. Em __Crédito__, insira em os valores de __Limite de crédito (BRL)__ e da __Tolerância__ que deseja disponibilizar ao cliente.
 5. Clique em `Confirmar`.
 
-<div class="alert alert-warning">
-  O preenchimento do campo <b>Email</b> é obrigatório, pois a plataforma VTEX utiliza essa informação apra realizar a autenticação de acesso do cliente aos limites de crédito da sua conta. Para mais informações sobre proteção de dados, acesse <a href="https://help.vtex.com/pt/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB">Segurança do SmartCheckout</a>.
-</div>
+>⚠️ O preenchimento do campo **Email** é obrigatório, pois a plataforma VTEX utiliza essa informação apra realizar a autenticação de acesso do cliente aos limites de crédito da sua conta. Para mais informações sobre proteção de dados, acesse [Segurança do SmartCheckout](https://help.vtex.com/pt/tutorial/seguranca-do-smartcheckout--3SrJuuhrqwePUg1rp1exfB).
 
 A partir deste momento, a nova conta criada será exibida na tela de __Contas__.
 
@@ -71,9 +67,7 @@ Para criar múltiplas contas ao mesmo tempo (em massa) no Customer Credit, você
 
 A partir deste momento, as novas contas criadas via a planilha .csv estarão disponíveis na tela de __Contas__.
 
-<div class="alert alert-warning">
-  Também é possível rastrear processos anteriores de criação de múltiplas contas, identificando se as contas foram criadas de forma correta. Para verificar estas informações, clique em <b>Histórico de Importação</b> na tela de <b>Contas</b>.
-</div>  
+>⚠️ Também é possível rastrear processos anteriores de criação de múltiplas contas, identificando se as contas foram criadas de forma correta. Para verificar estas informações, clique em **Histórico de Importação** na tela de **Contas**.  
 
 ### Atualizar múltiplas contas (importação em massa)
 
diff --git a/docs/tracks/pt/creating-and-editing-users.md b/docs/tracks/pt/creating-and-editing-users.md
index 400ce477d..0ea094e1b 100644
--- a/docs/tracks/pt/creating-and-editing-users.md
+++ b/docs/tracks/pt/creating-and-editing-users.md
@@ -46,6 +46,4 @@ Não é possível alterar o e-mail. Para isso, é necessário fazer um novo cada
 2. Selecione o usuário desejado e clique no **ícone de lixeira**, na coluna de ações.  
 3. Clique em **confirmar**.
 
-<div class="alert alert-info">
-Embora tokens de integração apareçam na listagem de usuários, eles não podem ser excluídos. Para desativá-los, acesse <em>Configuração da conta > Gerenciamento da conta > Conta</em> e desmarque o campo <strong>Status dos Tokens</strong>.
-</div>
+>ℹ️ Embora tokens de integração apareçam na listagem de usuários, eles não podem ser excluídos. Para desativá-los, acesse *Configuração da conta > Gerenciamento da conta > Conta* e desmarque o campo **Status dos Tokens**.
diff --git a/docs/tracks/pt/creating-discount-coupons.md b/docs/tracks/pt/creating-discount-coupons.md
index dac32b583..4ab052055 100644
--- a/docs/tracks/pt/creating-discount-coupons.md
+++ b/docs/tracks/pt/creating-discount-coupons.md
@@ -36,9 +36,9 @@ Para criar um cupom de desconto, siga os passos abaixo:
 6. Clique em **Restrições e limitações de uso** e defina a quantidade de produtos que podem ser comprados por meio deste cupom, independente de quantas compras sejam realizadas para atingir esse número.
 7. Clique no botão **Salvar**.
 
-<div class="alert alert-info">
-Não é necessário criar uma <code>utm_source</code> e uma <code>utm_campaign</code>. Mas é necessário criar <b>pelo menos uma</b> delas.<br>
-Veja o artigo <a href="https://help.vtex.com/pt/tutorial/o-que-sao-utm_source-utm_campaign-e-utm_medium">O que são utm_source, utm_campaign e utm_medium</a> para entender melhor o que são essas UTMs.
-</div>
+>ℹ️ Não é necessário criar uma `utm_source` e uma `utm_campaign`. Mas é necessário criar **pelo menos uma** delas.
+>
+> 
+> Veja o artigo [O que são utm_source, utm_campaign e utm_medium](https://help.vtex.com/pt/tutorial/o-que-sao-utm_source-utm_campaign-e-utm_medium) para entender melhor o que são essas UTMs.
 
 No momento de criação de uma promoção regular, você deve selecionar a flag `utm_source` e/ou `utm_campaign` e inserir nos campos correspondentes as UTMs informadas durante a criação do cupom.
diff --git a/docs/tracks/pt/creating-franchise-accounts.md b/docs/tracks/pt/creating-franchise-accounts.md
index 04aedafbc..fb662afb9 100644
--- a/docs/tracks/pt/creating-franchise-accounts.md
+++ b/docs/tracks/pt/creating-franchise-accounts.md
@@ -24,9 +24,7 @@ Ao criar contas franquias, cada uma das suas lojas físicas terá um Admin VTEX
 
 Suas contas franquias funcionarão como [Sellers White Label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#o-que-e-um-seller-white-label). Isto significa que quando um pedido for realizado em qualquer canal, seja o VTEX Sales App ou o ecommerce, o sistema buscará entre todas elas aquela que consegue fazer a entrega com melhor [SLA](https://help.vtex.com/pt/tutorial/o-que-e-o-sla-de-operacao-da-plataforma--2cIFrsY5S8usk84OU4QOKm).
 
-<div class="alert alert-warning">
-  <p>Cada seller deve ter um CNPJ diferente para o funcionamento correto do pagamento dos pedidos.</p>
-</div>
+>⚠️ Cada seller deve ter um CNPJ diferente para o funcionamento correto do pagamento dos pedidos.
 
 A logística de cada uma das contas franquias pode ser gerenciada em um Admin VTEX separado. Para acessá-lo, entre na URL `{nome-da-conta-franquia}.myvtex.com/admin`.
 
diff --git a/docs/tracks/pt/creating-merchandising-rules-visual-editor.md b/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
index 0746e0d12..db0835c86 100644
--- a/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
+++ b/docs/tracks/pt/creating-merchandising-rules-visual-editor.md
@@ -40,9 +40,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
     Saiba mais sobre essas ações nos itens **IV, V, VI, VIII, IX** e **XI** da seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual]).
 9. Clique em `Salvar`.
 
-<div class="alert alert-info">
-  <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
-</div>
+>ℹ️ Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.
 
 ## Ações disponíveis no Editor visual
 
diff --git a/docs/tracks/pt/creating-or-editing-a-page-template.md b/docs/tracks/pt/creating-or-editing-a-page-template.md
index c047e70ec..43ed0f410 100644
--- a/docs/tracks/pt/creating-or-editing-a-page-template.md
+++ b/docs/tracks/pt/creating-or-editing-a-page-template.md
@@ -32,15 +32,16 @@ Confira o passo a passo a seguir:
 4. Clique em __HTML Templates__.__
 5. Logo abaixo, clique em __New template.
 6. Preencha o campo __Template Name__.
-<div class="alert alert-danger">
-  <p>Ao preencher o <b>Template Name</b> do template, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Ao preencher o **Template Name** do template, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 7. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 8. No canto superior direito, clique no botão __Save Template__.![4 2](https://images.ctfassets.net/alneenqid6w5/58ZckRTKZ2e6BbXPtx54xK/a638e74bf68dc437257a6c220d5a2c1c/4_2.png)
 
diff --git a/docs/tracks/pt/creating-regular-promotions.md b/docs/tracks/pt/creating-regular-promotions.md
index 980aa0a68..11f9ca4ec 100644
--- a/docs/tracks/pt/creating-regular-promotions.md
+++ b/docs/tracks/pt/creating-regular-promotions.md
@@ -134,9 +134,7 @@ O pedido do cliente deve atender às condições cadastradas nesta seção para
 Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o [nosso Suporte.](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue)
 </div>
 - **Número de parcelas:** o desconto será concedido caso o número de parcelas selecionadas pelo cliente estiver no intervalo cadastrado. Esse campo não se aplica para a seleção de boleto.
- <div class="alert alert-warning">
-Promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.
-</div>
+ >⚠️ Promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.
 - **utm_source:** o desconto será concedido caso a navegação seja realizada com as **utm_source** correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas um **utm_source** no checkout.
 - **utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
 - **Criar cupom a partir das UTMs acima:** cria um cupom a partir das UTMs cadastradas para dar ao cliente acesso à essa promoção sem a necessidade das utms, apenas com o código do cupom.
diff --git a/docs/tracks/pt/credit-card-payment-flow.md b/docs/tracks/pt/credit-card-payment-flow.md
index b976df8ca..d7fdf6329 100644
--- a/docs/tracks/pt/credit-card-payment-flow.md
+++ b/docs/tracks/pt/credit-card-payment-flow.md
@@ -42,6 +42,4 @@ O fluxo completo para pagamento por cartão de crédito na VTEX pode ser descrit
 
 Com a resposta do banco emissor, é realizado o fluxo inverso e o  **Gateway de Pagamentos**  recebe a informação se o pagamento foi aprovado ou negado.
 
-<div class="alert alert-info">
-É possível incluir o Antifraude neste fluxo. Neste caso, o antifraude recebe as informações do gateway de que o pagamento foi pré-autorizado pelo banco emissor. Com a informação recebida do gateway, o antifraude envia uma resposta de aprovação ou negação do pagamento. Caso o antifraude negue, o pagamento é cancelado. Caso o pagamento seja aprovado, o pedido pode prosseguir seu fluxo normal.
-</div>
+>ℹ️ É possível incluir o Antifraude neste fluxo. Neste caso, o antifraude recebe as informações do gateway de que o pagamento foi pré-autorizado pelo banco emissor. Com a informação recebida do gateway, o antifraude envia uma resposta de aprovação ou negação do pagamento. Caso o antifraude negue, o pagamento é cancelado. Caso o pagamento seja aprovado, o pedido pode prosseguir seu fluxo normal.
diff --git a/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md b/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
index db57eaa34..35c72448d 100644
--- a/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
+++ b/docs/tracks/pt/cubic-size-shipping-factor-and-dimensional-weight-calculations.md
@@ -44,9 +44,7 @@ Exemplo:
 
 Neste caso, ao comparar o peso real com o peso cubado do pacote, a transportadora fará a cobrança pelo peso real, pois ele é maior que o peso cubado.
 
-<div class="alert alert-warning">
-  Verifique com sua transportadora se a unidade de medidas está em <strong>gramas</strong>, que é a unidade utilizada na VTEX.
-</div>
+>⚠️ Verifique com sua transportadora se a unidade de medidas está em **gramas**, que é a unidade utilizada na VTEX.
 
 Ao realizar o cadastro da sua transportadora, esse é o valor que você deve preencher no campo Fator Cúbico de Peso.
 
diff --git a/docs/tracks/pt/customer-identification.md b/docs/tracks/pt/customer-identification.md
index 1f6adf697..2ad1791a3 100644
--- a/docs/tracks/pt/customer-identification.md
+++ b/docs/tracks/pt/customer-identification.md
@@ -33,7 +33,5 @@ Basta inserir um desses dados no campo e clicar em `Confirmar`.
 
 Alternativamente, caso você tenha habilitado Usuário Anônimo, é possível avançar sem identificar o cliente. Para isso, basta clicar em `Continuar sem identificação`.
 
-<div class="alert alert-info">
-Embora seja possível atender clientes sem identificá-los, recomendamos sempre fazer a identificação, uma vez que isso dá ao vendedor uma série de informações contextuais que aumentam as chances de conversão.
-</div>
+>ℹ️ Embora seja possível atender clientes sem identificá-los, recomendamos sempre fazer a identificação, uma vez que isso dá ao vendedor uma série de informações contextuais que aumentam as chances de conversão.
 
diff --git a/docs/tracks/pt/customizing-instore.md b/docs/tracks/pt/customizing-instore.md
index 2608c4a7f..7c0168a15 100644
--- a/docs/tracks/pt/customizing-instore.md
+++ b/docs/tracks/pt/customizing-instore.md
@@ -18,9 +18,7 @@ A experiência do VTEX Sales App é customizável: você pode aplicar funcionali
 
 Para isso, é necessário editar arquivos JavaScript e CSS, conforme descrito no guia para desenvolvedores [How to customize VTEX Sales App](https://developers.vtex.com/docs/guides/how-to-customize-vtex-sales-app).
 
-<div class="alert alert-warning">
-<p>Somente pessoas com experiência em programação devem customizar o VTEX Sales App, pois alterações incorretas nestes arquivos podem causar erros críticos.</p>
-</div>
+>⚠️ Somente pessoas com experiência em programação devem customizar o VTEX Sales App, pois alterações incorretas nestes arquivos podem causar erros críticos.
 
 Veja abaixo as customizações disponíveis para uso no VTEX Sales App. Você pode clicar no nome de cada uma para acessar seu respectivo guia de implementação.
 
diff --git a/docs/tracks/pt/customizing-instores-layout.md b/docs/tracks/pt/customizing-instores-layout.md
index 157974778..22c131766 100644
--- a/docs/tracks/pt/customizing-instores-layout.md
+++ b/docs/tracks/pt/customizing-instores-layout.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: customizando-o-layout-do-instore
 ---
 
-<div class="alert alert-danger">
-A customização do layout do inStore, explicada neste artigo, envolve e alteração do arquivo CSS <code>checkout-instore-custom.css</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A customização do layout do inStore, explicada neste artigo, envolve e alteração do arquivo CSS `checkout-instore-custom.css`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 Por meio do painel administrativo da VTEX, a loja tem acesso ao arquivo CSS editável que define os estilos do aplicativo do inStore. Portanto, é possível customizar esses estilos.
 
diff --git a/docs/tracks/pt/data-protection-roles.md b/docs/tracks/pt/data-protection-roles.md
index 482237686..2a3fc761f 100644
--- a/docs/tracks/pt/data-protection-roles.md
+++ b/docs/tracks/pt/data-protection-roles.md
@@ -48,9 +48,7 @@ A VTEX não utiliza dados de clientes finais para nenhuma outra finalidade que n
 
 O DPA utilizado deve ser o da região específica do titular dos dados (cliente da loja).
 
-<div class="alert alert-warning">
-  <p>Acesse <a href="https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/">Data Processing Addendum - VTEX</a> para visualizar o DPA padrão da VTEX para cada região.</p>
-</div>
+>⚠️ Acesse [Data Processing Addendum - VTEX](https://vtex.com/br-pt/privacy-and-agreements/data-processing-addendum/) para visualizar o DPA padrão da VTEX para cada região.
 
 ## Responsabilidades compartilhadas
 
diff --git a/docs/tracks/pt/define-payment-methods-displayed-on-instore.md b/docs/tracks/pt/define-payment-methods-displayed-on-instore.md
index cb189b995..bb339459e 100644
--- a/docs/tracks/pt/define-payment-methods-displayed-on-instore.md
+++ b/docs/tracks/pt/define-payment-methods-displayed-on-instore.md
@@ -18,6 +18,4 @@ Agora que a condição de pagamento está criada, é preciso criar os filtros qu
 
 Para isso, os desenvolvedores da sua loja precisam customizar um arquivo JavaScript. Leia o guia [Define payment methods displayed on VTEX Sales App](https://developers.vtex.com/docs/guides/define-payment-methods-displayed-on-vtex-sales-app) para mais informações.
 
-<div class="alert alert-danger">
-<p>Para habilitar pagamentos via aplicativo do VTEX Sales App, é necessário fazer alterações em um arquivo JavaScript. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas neste arquivo podem causar erros críticos.</p>
-</div>
+>❗ Para habilitar pagamentos via aplicativo do VTEX Sales App, é necessário fazer alterações em um arquivo JavaScript. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas neste arquivo podem causar erros críticos.
diff --git a/docs/tracks/pt/defining-the-google-shopping-trade-policy.md b/docs/tracks/pt/defining-the-google-shopping-trade-policy.md
index 1e65a1f21..f62cf0bba 100644
--- a/docs/tracks/pt/defining-the-google-shopping-trade-policy.md
+++ b/docs/tracks/pt/defining-the-google-shopping-trade-policy.md
@@ -40,9 +40,7 @@ Para que essas promoções apareçam no Google Shopping, é preciso que os produ
 
 Com seus produtos seguindo todos os requisitos acima, a ferramenta aplica o valor promocional previamente configurado na VTEX, nas visualizações do Google Shopping.  
 
-<div class="alert alert-warning">
-  Caso exista uma promoção de desconto à vista (condicionada ao método de pagamento boleto ou pix), esse benefício será aplicado ao valor do produto antes do envio.
-  </div>
+>⚠️ Caso exista uma promoção de desconto à vista (condicionada ao método de pagamento boleto ou pix), esse benefício será aplicado ao valor do produto antes do envio.
 
 ## Desconto vinculado ao método de pagamento  
 
@@ -58,10 +56,6 @@ Para configurar um desconto vinculado a um método de pagamento, é necessário
 
 Após seguir essas documentações, a ativação deverá ser realizada através da [Configuração do conector](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/wWyl0Njxgs5KfXvxYZJrl).
 
-<div class="alert alert-warning">
-  Quando há vários sellers vinculados a um produto na sua loja, para o Google Shopping a regra é anunciar a melhor oferta disponível.
-  </div>
+>⚠️ Quando há vários sellers vinculados a um produto na sua loja, para o Google Shopping a regra é anunciar a melhor oferta disponível.
 
-  <div class="alert alert-danger">
-  Cada promoção criada só pode ter um método de pagamento atrelado para que o desconto seja enviado ao Google Shooping.
-  </div>
+  >❗ Cada promoção criada só pode ter um método de pagamento atrelado para que o desconto seja enviado ao Google Shooping.
diff --git a/docs/tracks/pt/detaching-skus-by-specification.md b/docs/tracks/pt/detaching-skus-by-specification.md
index 1803808cd..bb998166c 100644
--- a/docs/tracks/pt/detaching-skus-by-specification.md
+++ b/docs/tracks/pt/detaching-skus-by-specification.md
@@ -26,8 +26,7 @@ A seguir, confira um exemplo de separação de SKUs por cor. Na imagem abaixo, a
 
 ![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
-<div class="alert alert-info"><p>
-Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.</p></div>
+>ℹ️ Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.
 
 ## Configuração
 Para configurar quais atributos serão usados para separar os SKUs, acesse nosso artigo de [Configurações da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
diff --git a/docs/tracks/pt/enable-clustered-payment-conditions.md b/docs/tracks/pt/enable-clustered-payment-conditions.md
index bbf15cc3c..b89ea7277 100644
--- a/docs/tracks/pt/enable-clustered-payment-conditions.md
+++ b/docs/tracks/pt/enable-clustered-payment-conditions.md
@@ -22,10 +22,8 @@ O segundo é configurar a própria Clustered Payment Conditions na sua loja.
 
 ## Habilitar Customer Credit
 
-<div class="alert alert-info">
-Caso o Customer Credit já esteja instalado e configurado no Admin, vá para o passo 
-“Habilitar Clustered Payment Conditions”.
-</div>  
+>ℹ️ Caso o Customer Credit já esteja instalado e configurado no Admin, vá para o passo 
+> “Habilitar Clustered Payment Conditions”.  
 
 ### 1. Instalação da app
 
@@ -41,9 +39,7 @@ Existem algumas [configurações básicas](https://help.vtex.com/pt/tracks/custo
 
 ## Habilitar Clustered Payment Conditions na loja
 
-<div class="alert alert-warning">
-Atualmente, esta funcionalidade encontra-se em Closed Beta (estágio de testes) e não está disponível para instalação em novas lojas.            
-</div>  
+>⚠️ Atualmente, esta funcionalidade encontra-se em Closed Beta (estágio de testes) e não está disponível para instalação em novas lojas.  
 
 Agora que o Customer Credit está funcionando na sua loja, você pode habilitar a Clustered Payment Conditions. Para isso, basta entrar em contato com o time de suporte da VTEX. [Abra um chamado](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM "Abra um chamado") e solicite a habilitação da feature da sua loja.
 
diff --git a/docs/tracks/pt/enabling-2-factor-authentication-login.md b/docs/tracks/pt/enabling-2-factor-authentication-login.md
index 9959e1d70..7b40664df 100644
--- a/docs/tracks/pt/enabling-2-factor-authentication-login.md
+++ b/docs/tracks/pt/enabling-2-factor-authentication-login.md
@@ -34,13 +34,9 @@ Há duas opções de autenticação:
 
 ![2FA - Select - PT](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
 
-<div class="alert alert-warning">
-  Recomendamos o uso de <a href="#habilitar-o-2fa-por-aplicativo">aplicativo de autenticação</a>, para que falhas na sua operadora de telefonia não inviabilizem seu login. Pelo aplicativo, a chave de acesso estará sempre disponível para uso.
-</div>
+>⚠️ Recomendamos o uso de [aplicativo de autenticação](#habilitar-o-2fa-por-aplicativo), para que falhas na sua operadora de telefonia não inviabilizem seu login. Pelo aplicativo, a chave de acesso estará sempre disponível para uso.
 
-<div class="alert alert-info">
-Como algumas empresas restringem o uso de celular por operadores de televendas, usuários com o <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator" target="_blank">perfil de acesso de televendas</a> não são obrigados a habilitar 2FA quando fazem login usando e-mail e senha.
-</div>
+>ℹ️ Como algumas empresas restringem o uso de celular por operadores de televendas, usuários com o [perfil de acesso de televendas](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#call-center-operator" target="_blank) não são obrigados a habilitar 2FA quando fazem login usando e-mail e senha.
 
 ## Habilitar o 2FA por aplicativo
 
@@ -60,9 +56,7 @@ Para usar uma chave gerada por aplicativo de autenticação:
 
   ![2FA - App Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/58da9e3065ebec81f1528554808eee56/2FA_-_App_Insert_Code_-_PT.png)
 
-<div class="alert alert-info">
-Se você fizer login usando e-mail e senha no mesmo computador, a chave de acesso será solicitada <strong>a cada 3 dias</strong>. Quando isso acontecer, basta consultar o código no aplicativo.
-</div>
+>ℹ️ Se você fizer login usando e-mail e senha no mesmo computador, a chave de acesso será solicitada **a cada 3 dias**. Quando isso acontecer, basta consultar o código no aplicativo.
 
 ## Habilitar o 2FA por SMS
 
@@ -76,9 +70,7 @@ Para usar uma chave enviada por mensagem de texto:
 
    ![2FA - SMS Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/bf998e866456c232965f4bd845b65db1/2FA_-_SMS_Insert_Code_-_PT.png)
 
-<div class="alert alert-warning">
-Não podemos garantir que sua operadora de telefonia conseguirá entregar a chave de acesso sempre que necessário. Caso a mensagem de texto da VTEX não chegue, tente reenviar o código ou <a href="#habilitar-o-2fa-por-aplicativo">habilitar o 2FA por aplicativo</a>.
-</div>
+>⚠️ Não podemos garantir que sua operadora de telefonia conseguirá entregar a chave de acesso sempre que necessário. Caso a mensagem de texto da VTEX não chegue, tente reenviar o código ou [habilitar o 2FA por aplicativo](#habilitar-o-2fa-por-aplicativo).
 
 ## Modificar configurações de 2FA
 
diff --git a/docs/tracks/pt/enabling-a-sales-rep-code.md b/docs/tracks/pt/enabling-a-sales-rep-code.md
index bf29478c7..9c621b33d 100644
--- a/docs/tracks/pt/enabling-a-sales-rep-code.md
+++ b/docs/tracks/pt/enabling-a-sales-rep-code.md
@@ -20,21 +20,15 @@ Uma das possibilidades de customização do inStore é alterar o campo de [Obser
 
 Uma vez habilitada, essa customização exibe o campo `Vendor` no topo da página e adiciona uma etapa ao fluxo de compra. Agora, antes do Shipping, o vendedor precisa obrigatoriamente identificar a venda com o seu código.
 
-<div class="alert alert-danger">
-<strong>Atenção</strong>: neste caso, não é possível finalizar uma venda sem preencher o campo <code>Vendor</code> com código do vendedor.
-</div>
+>❗ **Atenção**: neste caso, não é possível finalizar uma venda sem preencher o campo `Vendor` com código do vendedor.
 
 ## Editando o arquivo Javascript
 
 Para habilitar o código do vendedor, é preciso fazer uma alteração no código JavaScript `checkout-instore-custom.js` salvo no painel administrativo da VTEX.
 
-<div class="alert alert-warning">
-É <strong>expressamente recomendável</strong> que o responsável pela modificação no código seja uma pessoa com <strong>experiência em programação</strong>. 
-</div>  
+>⚠️ É **expressamente recomendável** que o responsável pela modificação no código seja uma pessoa com **experiência em programação**.  
 
-<div class="alert alert-info">
-O código do vendedor é habilitado <strong>apenas</strong> por JavaScript.
-</div>
+>ℹ️ O código do vendedor é habilitado **apenas** por JavaScript.
 
 Primeiro, faça as configurações descritas no artigo [Habilitar campo de observação na tela do pedido](https://help.vtex.com/pt/tracks/instore-customizacoes--1z9kBm12oBPyVNDo1ivVc2/8Aj21R8bll0tdrxHWjVOs).
 
@@ -56,9 +50,7 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades do objeto <code>window.INSTORE_CONFIG</code>. Caso contrário, outras funcionalidades da sua loja podem ser quebradas. Além disso, lembre-se que o código acima é apenas uma possibilidade de configuração. 
-</div>
+>❗ Não remova nenhuma das outras propriedades do objeto `window.INSTORE_CONFIG`. Caso contrário, outras funcionalidades da sua loja podem ser quebradas. Além disso, lembre-se que o código acima é apenas uma possibilidade de configuração.
 
 Cada responsável deve preencher as propriedades do objeto `window.INSTORE_CONFIG_` de acordo com o funcionamento esperado da customização para a sua loja. 
 
diff --git a/docs/tracks/pt/enabling-cart-transfer-between-devices.md b/docs/tracks/pt/enabling-cart-transfer-between-devices.md
index 17d86be15..9b3349da6 100644
--- a/docs/tracks/pt/enabling-cart-transfer-between-devices.md
+++ b/docs/tracks/pt/enabling-cart-transfer-between-devices.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: habilitar-transferencia-de-carrinho-entre-dispositivos
 ---
 
-<div class="alert alert-danger">
-A ativação de Transferência de carrinho, explicada neste artigo, envolve e alteração do arquivo JavaScript <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A ativação de Transferência de carrinho, explicada neste artigo, envolve e alteração do arquivo JavaScript `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 A funcionalidade de __Transferência de carrinho__ do inStore permite que uma compra iniciada em um dispositivo possa ser finalizada em qualquer outro dispositivo presente no fluxo da compra, sem a necessidade de re-bipar os produtos.
 
diff --git a/docs/tracks/pt/enabling-order-filter-by-salesperson.md b/docs/tracks/pt/enabling-order-filter-by-salesperson.md
index a393f8983..85bbd8208 100644
--- a/docs/tracks/pt/enabling-order-filter-by-salesperson.md
+++ b/docs/tracks/pt/enabling-order-filter-by-salesperson.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: habilitar-filtro-de-pedidos-por-vendedor
 ---
 
-<div class="alert alert-danger">
-A mudança das configurações de filtro por vendedor, explicada neste artigo, envolve e alteração do arquivo <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A mudança das configurações de filtro por vendedor, explicada neste artigo, envolve e alteração do arquivo `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 No inStore, é possível ver a listagem de todos os pedidos finalizados em uma loja:
 
@@ -37,9 +35,7 @@ window.INSTORE_CONFIG = {
 
 Com isso, filtramos os pedidos para exibir apenas aqueles realizados pelo vendedor atualmente logado no inStore.
 
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
 
 Após recarregar os dados do inStore, clicando no botão __Restaurar dados__, o vendedor verá apenas os pedidos fechados por ele, como no seguinte exemplo:
 
diff --git a/docs/tracks/pt/enabling-product-recommendations.md b/docs/tracks/pt/enabling-product-recommendations.md
index bea6eeacf..15eaa62f9 100644
--- a/docs/tracks/pt/enabling-product-recommendations.md
+++ b/docs/tracks/pt/enabling-product-recommendations.md
@@ -56,6 +56,4 @@ window.INSTORE_CONFIG = {
 
 Salve o arquivo com a alteração, depois abra o menu do aplicativo inStore e atualize os dados, clicando no botão __Restaurar dados__. Feito isso, os vendedores não verão mais recomendações de produto.
 
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
diff --git a/docs/tracks/pt/enabling-the-remarks-field-in-the-order-screen.md b/docs/tracks/pt/enabling-the-remarks-field-in-the-order-screen.md
index bbd92f4b7..a0522fabb 100644
--- a/docs/tracks/pt/enabling-the-remarks-field-in-the-order-screen.md
+++ b/docs/tracks/pt/enabling-the-remarks-field-in-the-order-screen.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: habilitar-campo-de-observacao-na-tela-do-pedido
 ---
 
-<div class="alert alert-danger">
-A customização explicada neste artigo envolve e alteração do arquivo JavaScript <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A customização explicada neste artigo envolve e alteração do arquivo JavaScript `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 O aplicativo do inStore permite o uso de um campo de "Observação", onde é possível guardar informações adicionais a respeito de cada pedido.
 
@@ -45,9 +43,7 @@ window.LOCALE_MESSAGES = {
 };
 ```
  
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
                              
 Se for necessário aplicar alguma lógica de validação ou máscara para os dados inseridos nesse campo, é possível incluir no arquivo `checkout-instore-custom.js` uma função que escute o evento `note.visible`, que é disparado quando o modal é aberto, e então desenvolver sua lógica.
 
diff --git a/docs/tracks/pt/exporting-an-order.md b/docs/tracks/pt/exporting-an-order.md
index 4fb6ee636..74388f38f 100644
--- a/docs/tracks/pt/exporting-an-order.md
+++ b/docs/tracks/pt/exporting-an-order.md
@@ -18,9 +18,7 @@ O processo de exportação de pedidos pode ser realizado através da tela **Todo
 
 A exportação de pedidos gera um relatório no formato .csv que contém uma série de detalhes sobre os pedidos da sua loja. Para saber quais são as informações apresentadas no relatório exportado, leia o tutorial sobre os [campos da planilha de pedidos](https://help.vtex.com/pt/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
 
-<div class="alert alert-info">
-<p>Quando o número de pedidos solicitados na exportação é muito alto, o processo pode causar lentidão. Por isso, existe uma limitação no número de pedidos selecionados. Atualmente, é possível exportar até 50 mil pedidos por vez</b>.</p>
-</div>
+>ℹ️ Quando o número de pedidos solicitados na exportação é muito alto, o processo pode causar lentidão. Por isso, existe uma limitação no número de pedidos selecionados. Atualmente, é possível exportar até 50 mil pedidos por vez</b>.
 
 Siga as instruções abaixo para gerar o relatório:
 
diff --git a/docs/tracks/pt/extensions-hub-app-store.md b/docs/tracks/pt/extensions-hub-app-store.md
index 7cb1ecbff..2cd0503ea 100644
--- a/docs/tracks/pt/extensions-hub-app-store.md
+++ b/docs/tracks/pt/extensions-hub-app-store.md
@@ -62,9 +62,7 @@ Para baixar um app para a sua conta:
 
 Após realizar estes passos, o app estará disponível na sua conta e será instalado na loja que estiver utilizando no momento.
 
-<div class="alert alert-warning">
-Antes de baixar um app, recomendamos ver os termos e condições do fornecedor e os termos da VTEX pelos links disponíveis abaixo do botão <b>Baixar App</b>.
-</div>
+>⚠️ Antes de baixar um app, recomendamos ver os termos e condições do fornecedor e os termos da VTEX pelos links disponíveis abaixo do botão **Baixar App**.
 
 O custo de um app pode ser uma das seguintes formas:
 
diff --git a/docs/tracks/pt/extensions-hub-partners.md b/docs/tracks/pt/extensions-hub-partners.md
index 658cfbbe7..18f753ed2 100644
--- a/docs/tracks/pt/extensions-hub-partners.md
+++ b/docs/tracks/pt/extensions-hub-partners.md
@@ -14,6 +14,4 @@ trackId: AW7klkYMh557y5IUOgzco
 trackSlugPT: hub-de-extensoes
 ---
 
-<div class="alert alert-warning">
-Conteúdo ainda não disponível.
-</div>
+>⚠️ Conteúdo ainda não disponível.
diff --git a/docs/tracks/pt/facebook-business-extension.md b/docs/tracks/pt/facebook-business-extension.md
index 8ddeda11f..0c2073faf 100644
--- a/docs/tracks/pt/facebook-business-extension.md
+++ b/docs/tracks/pt/facebook-business-extension.md
@@ -30,9 +30,7 @@ A app _Facebook Business Extension e Conversions API_ tem compatibilidade total
 
 Saiba mais sobre a configuração necessária para cada uma em nosso guia [Facebook Business Extension](https://developers.vtex.com/docs/guides/vtex-facebook-fbe#compatibility) no Developer Portal.
 
-<div class="alert alert-warning">
-Na VTEX, existe um <a href="https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">guia de integração com Facebook</a>. No entanto, a integração com a app <i>Facebook Business Extension e Conversions API</i> deve ser sua escolha padrão, pois o FBE é a solução mais completa do Facebook. Independente de ter a outra integração configurada, você deve prosseguir normalmente com a configuração desta integração.
-</div>
+>⚠️ Na VTEX, existe um [guia de integração com Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc). No entanto, a integração com a app <i>Facebook Business Extension e Conversions API</i> deve ser sua escolha padrão, pois o FBE é a solução mais completa do Facebook. Independente de ter a outra integração configurada, você deve prosseguir normalmente com a configuração desta integração.
 
 ## Pixel do Facebook
 
diff --git a/docs/tracks/pt/filters.md b/docs/tracks/pt/filters.md
index c9edb0a97..2a197ca36 100644
--- a/docs/tracks/pt/filters.md
+++ b/docs/tracks/pt/filters.md
@@ -20,17 +20,13 @@ Quando um cliente seleciona um filtro (preço, cor, tamanho e marca), essa infor
 
 O **VTEX Intelligent Search** usa o contexto dos produtos apresentados como resultados de busca para saber exatamente quais filtros devem ser exibidos para o cliente, seguindo as configurações do Catálogo.
 
-<div class="alert alert-info">
-  <p>A ordenação dos filtros de marca, departamento, categoria e subcategoria é determinada pela quantidade de produtos cadastrados em cada um dos filtros.</p>
-</div>
+>ℹ️ A ordenação dos filtros de marca, departamento, categoria e subcategoria é determinada pela quantidade de produtos cadastrados em cada um dos filtros.
 
 Exemplo: considere que o filtro *Tamanho* está cadastrado no catálogo de uma loja e somente o produto *tênis* possui a especificação *Tamanho* preenchida. Em uma pesquisa pelo termo *tênis*, *Tamanho* vai aparecer como um filtro. Já em uma pesquisa por qualquer outro termo, como *boné*, essa especificação não vai ser exibida como filtro.
 
 O resultado de busca não vai exibir uma especificação quando só existe ela como filtro ou o cliente a tenha acessado pelo menu da loja. Exemplo: se um cliente seleciona o filtro  Eletrodomésticos diretamente do menu, não será exibido Departamentos como um filtro lateral.
 
-<div class="alert alert-info">
-  <p>Caso o resultado da busca retorne mais de 30 mil produtos, alguns valores de filtros serão omitidos, uma vez que somente as especificações de uma parte desses produtos serão consideradas.</p>
-</div>
+>ℹ️ Caso o resultado da busca retorne mais de 30 mil produtos, alguns valores de filtros serão omitidos, uma vez que somente as especificações de uma parte desses produtos serão consideradas.
 
 A funcionalidade de Filtros apresenta as seguintes funções:
 
@@ -45,6 +41,4 @@ A funcionalidade de Filtros apresenta as seguintes funções:
 
 Confira o guia [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) no Developer Portal para mais detalhes técnicos sobre a utilização de filtros.
 
-<div class="alert alert-warning">
-  <p>Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.</p>
-</div>
+>⚠️ Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.
diff --git a/docs/tracks/pt/forcing-stock-availability.md b/docs/tracks/pt/forcing-stock-availability.md
index 700e2df68..5cfb33edf 100644
--- a/docs/tracks/pt/forcing-stock-availability.md
+++ b/docs/tracks/pt/forcing-stock-availability.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: forcar-disponibilidade-de-estoque
 ---
 
-<div class="alert alert-danger">
-A configuração para forçar disponibilidade de estoque, explicada neste artigo, envolve e alteração do arquivo <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div>
+>❗ A configuração para forçar disponibilidade de estoque, explicada neste artigo, envolve e alteração do arquivo `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
 
 Por padrão, se um SKU tem estoque zerado no catálogo da loja, não é possível realizar uma venda desse SKU com o inStore.
 
@@ -34,6 +32,4 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
diff --git a/docs/tracks/pt/frontend-implementation.md b/docs/tracks/pt/frontend-implementation.md
index 7731f240c..4b63e57e1 100644
--- a/docs/tracks/pt/frontend-implementation.md
+++ b/docs/tracks/pt/frontend-implementation.md
@@ -47,9 +47,7 @@ A <a href="#etapas-de-desenvolvimento">etapa de desenvolvimento</a> pode acontec
 
 A VTEX possui três tecnologias distintas para o desenvolvimento de frente de loja: a [FastStore](#FastStore), o [Store Framework](#store-framework) e o [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). O CMS Portal Legado foi a primeira tecnologia da VTEX para construção de frente de loja, baseada em HTML, CSS e JavaScript, e todo o desenvolvimento e a edição do código dessa tecnologia são feitos via Admin VTEX.
 
-<div class="alert alert-warning">
-Apesar de ainda ser usado por algumas lojas, o <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> é uma tecnologia legada e não está mais disponível para lojas que estão iniciando com a VTEX.
-</div>
+>⚠️ Apesar de ainda ser usado por algumas lojas, o [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) é uma tecnologia legada e não está mais disponível para lojas que estão iniciando com a VTEX.
 
 As próximas seções são sobre as principais características e funcionalidades da FastStore e do Store Framework.
 
diff --git a/docs/tracks/pt/getting-started-with-logistics.md b/docs/tracks/pt/getting-started-with-logistics.md
index f7137509d..201a3745e 100644
--- a/docs/tracks/pt/getting-started-with-logistics.md
+++ b/docs/tracks/pt/getting-started-with-logistics.md
@@ -19,17 +19,16 @@ O módulo **Estoque & entrega** é responsável pelas configurações logística
 
 Esse artigo é o primeiro de uma trilha de primeiros passos para as configurações logísticas. A trilha contém informações básicas para auxiliar no entendimento da logística em lojas VTEX e na forma como as configurações estão estruturadas na plataforma.
 
-<div class="alert alert-danger">
-Antes de configurar a logística da sua loja, você precisa ter configurado:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE">Política comercial</a></li>
-<li><a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR">Catálogo</a></li>
-<li><a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu">Preços</a></li>
-  </ol>
-  </body>
-
-</div>
+>❗ Antes de configurar a logística da sua loja, você precisa ter configurado:
+> <body>
+>
+> [Política comercial](https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE)
+>
+> [Catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR)
+>
+> [Preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3N9xYhnampRQOrfaTAOxNu)
+>
+> </body>
 
 A trilha reúne os artigos:
 
diff --git a/docs/tracks/pt/go-live-process.md b/docs/tracks/pt/go-live-process.md
index 369c838c6..52ab55ce2 100644
--- a/docs/tracks/pt/go-live-process.md
+++ b/docs/tracks/pt/go-live-process.md
@@ -30,9 +30,7 @@ Antes de realizar o go-live da sua loja, é essencial garantir que você tenha r
 
 Copie esta [Checklist de configuração de loja](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/f504033fb6e8bf38b639547c5fd8790a/Checklist_de_configura__o_de_loja.xlsx) e verifique, para cada item, se realizou as configurações de acordo com o funcionamento desejado da loja.
 
-<div class="alert alert-warning">
-A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. Cabe à sua equipe definir quais funcionalidades implementar na sua loja e como deverão ser configuradas de maneira a produzir a experiência de loja desejada. Isso significa que a lista pode não contemplar todas as funcionalidades usadas pela sua loja. Ainda assim, é importante verificar todos os aspectos do funcionamento da sua loja, mesmo que não estejam na lista sugerida.
-</div>
+>⚠️ A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. Cabe à sua equipe definir quais funcionalidades implementar na sua loja e como deverão ser configuradas de maneira a produzir a experiência de loja desejada. Isso significa que a lista pode não contemplar todas as funcionalidades usadas pela sua loja. Ainda assim, é importante verificar todos os aspectos do funcionamento da sua loja, mesmo que não estejam na lista sugerida.
 
 ## Passo a passo
 
diff --git a/docs/tracks/pt/go-live.md b/docs/tracks/pt/go-live.md
index f7e3b067f..4ae93e17d 100644
--- a/docs/tracks/pt/go-live.md
+++ b/docs/tracks/pt/go-live.md
@@ -25,9 +25,7 @@ Na zona de DNS do seu domínio, você deve criar uma entrada do tipo CNAME no su
 
 Note que o `{domínio}` indicado acima deve ser o mesmo que você [cadastrou na VTEX](https://help.vtex.com/pt/tracks/como-realizar-el-go-live-de-tu-tienda--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#cadastrar-dominio-na-vtex).
 
-<div class="alert alert-warning">
-Caso você utilize a Cloudflare como zona de DNS, pode ser necessário desabilitar o proxy de DNS e, consequentemente, desativar os serviços de CDN e WAF da Cloudflare. Mais informações podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">Como desabilitar o proxy no Cloudflare</a>.
-</div>
+>⚠️ Caso você utilize a Cloudflare como zona de DNS, pode ser necessário desabilitar o proxy de DNS e, consequentemente, desativar os serviços de CDN e WAF da Cloudflare. Mais informações podem ser encontradas no artigo [Como desabilitar o proxy no Cloudflare](https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 Alguns exemplos:
 
@@ -58,9 +56,7 @@ Endereço da loja: www.loja.minhaempresa.com.br
 
 Atente-se que o início do domínio ("loja", "www", "www.loja" ou qualquer outro) e a terminação (".com", ".com.br", ".com.ar" ou qualquer outro) fazem parte do `{hostname}`, e devem estar no CNAME de destino.
 
-<div class="alert alert-danger">
-Não pode haver nenhum apontamento tipo A coexistindo com o CNAME descrito acima. A coexistência destes dois apontamentos pode causar problemas no Go Live da sua loja. Mantenha apenas o apontamento CNAME descrito acima.
-</div>
+>❗ Não pode haver nenhum apontamento tipo A coexistindo com o CNAME descrito acima. A coexistência destes dois apontamentos pode causar problemas no Go Live da sua loja. Mantenha apenas o apontamento CNAME descrito acima.
 
 A propagação do apontamento de DNS demora de 24 a 48 horas para ocorrer completamente, o que significa que o endereço configurado pode não estar acessível a todas as pessoas logo após a configuração. Além disso é necessário [notificar o apontamento](#notificar-apontamento) para que a loja fique disponível.
 
diff --git a/docs/tracks/pt/google-pay.md b/docs/tracks/pt/google-pay.md
index a83cce218..44840adcc 100644
--- a/docs/tracks/pt/google-pay.md
+++ b/docs/tracks/pt/google-pay.md
@@ -18,9 +18,7 @@ O Google Pay™ é um serviço de pagamentos digitais que possibilita ao usuári
 
 Os termos de serviço da API do Google Pay se aplicam sempre que o serviço Google Pay for oferecido por um lojista. Para ler os termos, acesse [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
 
-<div class="alert alert-warning">
-<p>O Google Pay não está disponível para Checkout V5 ou versões anteriores do Checkout.</p>
-</div>
+>⚠️ O Google Pay não está disponível para Checkout V5 ou versões anteriores do Checkout.
 
 ## Ativar Google Pay
 
@@ -29,30 +27,22 @@ Para ativar o Google Pay, siga o passo a passo abaixo.
 1. No Admin VTEX, acesse **Configurações da loja > Pagamentos > Carteiras** ou digite **Carteiras **na barra de busca no topo da página.
 2. Selecione a opção **Ativar** para modificar o checkout para incluir a extensão do Google Pay.
 
-<div class="alert alert-info">
-<p>As bandeiras suportadas no Google Pay são as mesmas bandeiras configuradas nas condições de pagamento.</p>
-</div>
+>ℹ️ As bandeiras suportadas no Google Pay são as mesmas bandeiras configuradas nas condições de pagamento.
 
 Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como nova forma de pagamento. É possível que demore em torno de 10 minutos para que a configuração apareça no Checkout.
 
 ![google-pay-checkout-pt](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/6ba2af94c811c8cb76d553f68c5578d6/Screenshot_2024-08-01_at_14.21.25.png)
 
-<div class="alert alert-warning">
-<p>Google Pay, neste momento, não vai suportar assinatura.</p>
-</div>
+>⚠️ Google Pay, neste momento, não vai suportar assinatura.
 
 É necessário ter os seguintes requisitos para utilizar o Google Pay:
 
 * Ter pelo menos uma [condição de pagamento](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) ativa configurada para cartões de crédito ou débito com um [adquirente](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente), definindo qual adquirente irá processar o pagamento da carteira.
 * Utilizar o [Checkout VTEX](https://help.vtex.com/pt/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) na sua loja.
 
-<div class="alert alert-warning">
-  <p>Nas lojas que têm o fluxo de autenticação <a href="https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado e suportado pelo adquirente, o pagamento com o Google Pay seguirá o fluxo nativo de cartão, sendo submetido também ao 3DS. Para mais informações sobre como configurar o fluxo de autenticação, consulte <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar fluxo de autenticação 3DS 2</a>.</p>
-</div>
+>⚠️ Nas lojas que têm o fluxo de autenticação [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) configurado e suportado pelo adquirente, o pagamento com o Google Pay seguirá o fluxo nativo de cartão, sendo submetido também ao 3DS. Para mais informações sobre como configurar o fluxo de autenticação, consulte [Configurar fluxo de autenticação 3DS 2](https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2).
 
-<div class="alert alert-info">
-<p>Você também pode configurar o Google Pay para ser processado com a Adyen ou Stripe. Para isso, acesse a tela <b>Condições de Pagamento</b> no Admin, clique em <b>Google Pay</b> e selecione a opção desejada.</p>
-</div>
+>ℹ️ Você também pode configurar o Google Pay para ser processado com a Adyen ou Stripe. Para isso, acesse a tela **Condições de Pagamento** no Admin, clique em **Google Pay** e selecione a opção desejada.
 
 ## Consultar transações finalizadas com o Google Pay
 
@@ -64,9 +54,7 @@ Após acessar a transação desejada, clique em `+ Informações` para verificar
 
 ![Google Pay Transaction_2](https://images.ctfassets.net/alneenqid6w5/6nLdqOG38LEUbmSKth5FRP/904607c6df63c9168c35435b9bb5068e/Google_Pay_Transaction2_PT.png)
 
-<div class="alert alert-warning">
-  <p>Também é possível identificar transações realizadas com o Google Pay por meio da página <b>Todos os pedidos</b> no Admin. Você precisa somente selecionar o período desejado de busca, <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu">exportar os pedidos</a> em um relatório no formato .csv e localizar a informação Google Pay no campo "payment origin".</p>
-</div>
+>⚠️ Também é possível identificar transações realizadas com o Google Pay por meio da página **Todos os pedidos** no Admin. Você precisa somente selecionar o período desejado de busca, [exportar os pedidos](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/6rVCf9KLn1jgTaxS0xuByu) em um relatório no formato .csv e localizar a informação Google Pay no campo "payment origin".
 
 ## Adicionar informação do Google Pay no template de compra
 
@@ -80,9 +68,7 @@ Para adicionar a informação que o pedido foi realizado com um cartão advindo
 
 Com isso, após qualquer menção aos últimos quatro dígitos do cartão desses templates de email, será adicionada a informação "(Google Pay)" caso o pagamento tenha sido feito com a carteira.
 
-<div class="alert alert-info">
-<p>Para lojas provisionadas a partir de Março de 2023, os templates já estarão atualizados com a informação do pagamento do pedido feito com o Google Pay.</p>
-</div>
+>ℹ️ Para lojas provisionadas a partir de Março de 2023, os templates já estarão atualizados com a informação do pagamento do pedido feito com o Google Pay.
 
 ## FAQ
 
diff --git a/docs/tracks/pt/google-shopping-ads-install.md b/docs/tracks/pt/google-shopping-ads-install.md
index 85a02557d..5001cff76 100644
--- a/docs/tracks/pt/google-shopping-ads-install.md
+++ b/docs/tracks/pt/google-shopping-ads-install.md
@@ -14,9 +14,7 @@ trackId: 47kz5PRQPK0IEaqGqiIuA
 trackSlugPT: como-fazer-campanhas-atraves-do-google-ads
 ---
 
-<div class="alert alert-warning">
-Atualmente, o Google Shopping Ads está disponível <strong>somente para lojas brasileiras</strong>.
-</div>
+>⚠️ Atualmente, o Google Shopping Ads está disponível **somente para lojas brasileiras**.
 
 O primeiro passo para usar o app é instalá-lo. Siga o passo-a-passo abaixo:
 
diff --git a/docs/tracks/pt/google-shopping-ads-set-up.md b/docs/tracks/pt/google-shopping-ads-set-up.md
index 70b312ca2..b7d3b5a5c 100644
--- a/docs/tracks/pt/google-shopping-ads-set-up.md
+++ b/docs/tracks/pt/google-shopping-ads-set-up.md
@@ -27,9 +27,7 @@ Nesta etapa, deve-se configurar qual loja vai usar o app e para qual URL os anú
 1. Na opção `Loja` selecione o sub-account que deverá ser utilizado para o app
 2. Na opção `URL` selecione a URL correspondente ao site da conta que você escolheu no passo anterior.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> certifique-se de que a URL escolhida é a correta, pois as opções mostrarão qualquer URL que esteja cadastrada em <a href="http://help.vtex.com/pt/tutorial/configurando-dominios-no-license-manager/">seus domínios</a>. <strong>Geralmente a URL usada é que a possui WWW</strong>.
-</div>
+>⚠️ **OBS:** certifique-se de que a URL escolhida é a correta, pois as opções mostrarão qualquer URL que esteja cadastrada em [seus domínios](http://help.vtex.com/pt/tutorial/configurando-dominios-no-license-manager/). **Geralmente a URL usada é que a possui WWW**.
 
 
 ## Definindo conta no Google Merchant Center
@@ -44,9 +42,7 @@ Ao selecionar __"Criar nova"__, logo em seguida é muito importante [acessar o G
 
 - __Associar existente:__ o app usará a conta que você já possui no GMC. No momento do login, você precisa usar exatamente o e-mail que você usa no GMC que você deseja associar.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> a URL configurada no GMC deve ser <strong>exatamente a mesma</strong> que foi escolhida anteriormente. Inclusive, levando em conta o protocolo (http ou https).
-</div>
+>⚠️ **OBS:** a URL configurada no GMC deve ser **exatamente a mesma** que foi escolhida anteriormente. Inclusive, levando em conta o protocolo (http ou https).
 
 Ao selecionar __"Associar a um GMC existente"__, logo em seguida será necessário definir se a integração de produtos com o Google será feita através da VTEX ou através de alguma sincronização externa que você já faça.
 
diff --git a/docs/tracks/pt/google-shopping-marketplace.md b/docs/tracks/pt/google-shopping-marketplace.md
index c3192a5b3..036565a20 100644
--- a/docs/tracks/pt/google-shopping-marketplace.md
+++ b/docs/tracks/pt/google-shopping-marketplace.md
@@ -22,9 +22,7 @@ Através do Google Shopping, é possível exibir ao consumidor alguns dos atribu
 
 O conector para Google Shopping da Plataforma VTEX permite que você faça uso desse serviço de forma simples e eficiente. Basta realizar as etapas de configuração descritas adiante. 
 
-<div class="alert alert-info">
-Para que a integração funcione corretamente, conheça as <a href="https://support.google.com/google-ads/answer/6149970?hl=pt-BR">Políticas dos anúncios do Shopping</a>, e saiba quais são as condições exigidas pelo Google.
-</div>
+>ℹ️ Para que a integração funcione corretamente, conheça as [Políticas dos anúncios do Shopping](https://support.google.com/google-ads/answer/6149970?hl=pt-BR), e saiba quais são as condições exigidas pelo Google.
 
 | **SAIBA MAIS** |
 | ---------- |
diff --git a/docs/tracks/pt/how-a-split-payment-transaction-works.md b/docs/tracks/pt/how-a-split-payment-transaction-works.md
index 3f79ed1b4..c0e70ad57 100644
--- a/docs/tracks/pt/how-a-split-payment-transaction-works.md
+++ b/docs/tracks/pt/how-a-split-payment-transaction-works.md
@@ -23,9 +23,7 @@ Antes de prosseguirmos, vamos esclarecer alguns conceitos relacionados a essa di
 ## MDR
 Ao processar uma transação, o adquirente retira um percentual do valor total da compra para si. Essa taxa é a MDR - sigla em inglês para Merchant Discount Rate. 
 
-<div class="alert alert-info">
-A MDR é aplicada em todas as transações processadas pela adquirente. 
-</div>
+>ℹ️ A MDR é aplicada em todas as transações processadas pela adquirente.
 
 No caso do split, tanto marketplace quanto seller(s) podem ser os responsáveis pelo pagamento dessa taxa. Também existe a possibilidade dos dois recebedores se encarregarem do pagamento. 
 
diff --git a/docs/tracks/pt/how-clustered-conditions-work.md b/docs/tracks/pt/how-clustered-conditions-work.md
index f6746f729..e9626ab98 100644
--- a/docs/tracks/pt/how-clustered-conditions-work.md
+++ b/docs/tracks/pt/how-clustered-conditions-work.md
@@ -20,9 +20,7 @@ Essas condições, por sua vez, são baseadas nos dados que o [Master Data](http
 
 Desse modo, as regras de prazo e parcelamento serão aplicadas ao(s) consumidor(es) que se encaixarem na condição - ou condições. 
 
-<div class="alert alert-danger">
-<strong>Atenção</strong>: só é permitido criar cinco clusters de clientes por condição de pagamento.
-</div>  
+>❗ **Atenção**: só é permitido criar cinco clusters de clientes por condição de pagamento.  
 
 Para configurá-las, escolha uma propriedade e, em seguida, selecione os parâmetros para criar um cluster.
 
diff --git a/docs/tracks/pt/how-the-payments-module-works.md b/docs/tracks/pt/how-the-payments-module-works.md
index 3d9e2c38d..b23ff70d9 100644
--- a/docs/tracks/pt/how-the-payments-module-works.md
+++ b/docs/tracks/pt/how-the-payments-module-works.md
@@ -18,9 +18,7 @@ O módulo de **Pagamentos** é o sistema responsável na VTEX por gerenciar toda
 
 Antes de explorarmos as funcionalidades dentro de *Pagamentos* no Admin da VTEX, vamos esclarecer alguns conceitos importantes que estão envolvidos no fluxo de pagamento de um pedido. Esse processo é realizado por alguns atores dentro do sistema financeiro brasileiro, que compõem a arquitetura do módulo de Pagamentos.
 
-<div class="alert alert-info">
-É importante lembrar que cada loja possui particularidades, e funcionamento próprio, o que influencia a forma de construir o módulo de Pagamentos do seu negócio. Para configurar seu fluxo financeiro, é fundamental, portanto, ter em mente as reais necessidades e propósitos do lojista e do projeto desejado.
-</div>
+>ℹ️ É importante lembrar que cada loja possui particularidades, e funcionamento próprio, o que influencia a forma de construir o módulo de Pagamentos do seu negócio. Para configurar seu fluxo financeiro, é fundamental, portanto, ter em mente as reais necessidades e propósitos do lojista e do projeto desejado.
 
 ## Gateway 
 Um gateway (também chamado de gateway de pagamento) é um sistema que efetua a transmissão dos dados das compras realizadas na sua loja no momento do checkout.
diff --git a/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md b/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
index 6f0832a2e..e824ba58f 100644
--- a/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
+++ b/docs/tracks/pt/how-to-configure-a-device-for-printout-the-order.md
@@ -38,9 +38,7 @@ configureDeviceEnabled: true,
             printByBroker: true 
       }
 }``
-<div class="alert alert-info">
-  <strong>NOTA</strong>: Há uma opção para imprimir automaticamente o resumo do pedido, assim que o pedido for concluído. A configuração é muito simples, basta adicionar a propriedade <strong><i>printPageAutomatically</i></strong> com o valor <strong><i>true</i></strong> dentro do objeto <strong><i>printingConfig</i></strong>.
-</div>
+>ℹ️ **NOTA**: Há uma opção para imprimir automaticamente o resumo do pedido, assim que o pedido for concluído. A configuração é muito simples, basta adicionar a propriedade **<i>printPageAutomatically</i>** com o valor **<i>true</i>** dentro do objeto **<i>printingConfig</i>**.
 
 Não exclua nenhuma das outras propriedades presentes neste objeto. O resultado deve ser algo como:
 
@@ -54,9 +52,7 @@ printPageAutomatically: true
 
 ## Configurar dispositivo de impressora no inStore
 
-<div class="alert alert-warning">
-  <strong>IMPORTANTE</strong>: Para a configuração da impressora no inStore, é necessário ter o <strong><i>AppKey</i></strong> e o <strong><i>AppToken</i></strong> com permissões de pelo menos um perfil como <i>"Vendedor inStore (inStore Sales Person)"</i>. Vale esclarecer que um perfil de <i>"Proprietário (administrador super)"</i> pode ser usado.
-</div>
+>⚠️ **IMPORTANTE**: Para a configuração da impressora no inStore, é necessário ter o **<i>AppKey</i>** e o **<i>AppToken</i>** com permissões de pelo menos um perfil como <i>"Vendedor inStore (inStore Sales Person)"</i>. Vale esclarecer que um perfil de <i>"Proprietário (administrador super)"</i> pode ser usado.
 
   1. Conecte a impressora ao computador em que o inStore está instalado (para baixar o inStore, acesse [http://instore.vtex.com/download]). Lembrando que deve ser um computador com sistema operacional Windows (Windows 7 ou superior são suportados).
   2. Abra o aplicativo inStore e entre na loja onde deseja configurar a impressora.
diff --git a/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
index c9235e07a..d6f448462 100644
--- a/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
@@ -33,9 +33,7 @@ O __preview__ renderizado por esse código é mostrado no box logo abaixo. Você
 
 O campo __JSON Data__ mostra um *exemplo* de objeto JSON contendo informações referentes ao assunto do e-mail. As chaves desse objeto podem ser usadas como variáveis no código HTML do template. Vamos aprender a fazer isso no próximo artigo.
 
-<div class="alert alert-warning">
-Atenção: para customizar o layout do e-mail, você deve inserir <strong>código CSS inline</strong>. <u>Não</u> insira o CSS no head do template, pois e-mails não lidam bem com isso.
-</div>
+>⚠️ Atenção: para customizar o layout do e-mail, você deve inserir **código CSS inline**. <u>Não</u> insira o CSS no head do template, pois e-mails não lidam bem com isso.
 
 Ao final, clique no botão __Salvar__.
 
diff --git a/docs/tracks/pt/how-to-customize-the-observation-field.md b/docs/tracks/pt/how-to-customize-the-observation-field.md
index 1bde0021a..4a8923f45 100644
--- a/docs/tracks/pt/how-to-customize-the-observation-field.md
+++ b/docs/tracks/pt/how-to-customize-the-observation-field.md
@@ -32,9 +32,7 @@ window.LOCALE_MESSAGES = {
   }
 };
 ```
-<div class="alert alert-danger">
-Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
 
 Se for necessário aplicar alguma lógica de validação ou máscara para os dados inseridos nesse campo, é possível incluir no arquivo `checkout-instore-custom.js` uma função que escute o evento `note.visible` que é disparado quando o modal é aberto, e então desenvolver sua lógica.
 
diff --git a/docs/tracks/pt/how-vtex-support-works.md b/docs/tracks/pt/how-vtex-support-works.md
index e5d05f019..85d8d23b2 100644
--- a/docs/tracks/pt/how-vtex-support-works.md
+++ b/docs/tracks/pt/how-vtex-support-works.md
@@ -20,9 +20,7 @@ O Suporte VTEX é prestado de forma online e permite a abertura de tickets com d
 - Login usando a conta do Google.
 - Email e senha com autenticação de dois fatores via aplicativo ou SMS.
 
-<div class="alert alert-warning">
-Para obter a autorização de autenticação, é necessário que o <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512">usuário</a> tenha acesso ao Admin VTEX e um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete">perfil de acesso</a> associado a <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos do License Manager</a>.
-</div>
+>⚠️ Para obter a autorização de autenticação, é necessário que o [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) tenha acesso ao Admin VTEX e um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete) associado a [recursos do License Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
 
 O Suporte VTEX é dividido por regiões, e cada região possui sua própria definição de nível de serviço (SLA de atendimento), prioridade e disponibilidade da equipe de Customer Excellence (CX) daquela região. As regiões onde o suporte atua são as seguintes:
 
diff --git a/docs/tracks/pt/including-order-variables-in-email-template.md b/docs/tracks/pt/including-order-variables-in-email-template.md
index 73ab2674f..40f60b1c7 100644
--- a/docs/tracks/pt/including-order-variables-in-email-template.md
+++ b/docs/tracks/pt/including-order-variables-in-email-template.md
@@ -22,9 +22,7 @@ Essas variáveis são propriedades do JSON que consta no campo __JSON Data__ e p
 
 ### Exemplo
 
-<div class="alert alert-warning">
-Os exemplos de JSON Data apenas aparecerão nos templates quando você concluir a ação desejada em sua loja. Caso não tenha transacionado um pedido, uma recorrência ou qualquer outra ação, o JSON Data aparecerá em branco.
-</div>
+>⚠️ Os exemplos de JSON Data apenas aparecerão nos templates quando você concluir a ação desejada em sua loja. Caso não tenha transacionado um pedido, uma recorrência ou qualquer outra ação, o JSON Data aparecerá em branco.
 
 Digamos que você queira inserir o nome da transportadora no e-mail de pedido enviado.
 
diff --git a/docs/tracks/pt/initial-setup.md b/docs/tracks/pt/initial-setup.md
index a7ffbf7b9..2b5881a55 100644
--- a/docs/tracks/pt/initial-setup.md
+++ b/docs/tracks/pt/initial-setup.md
@@ -20,17 +20,14 @@ Antes de começar a desenvolver, certifique-se de que os passos abaixo foram cum
 
 Você precisa ter o npm ou o yarn instalado na sua máquina. Ambos são gerenciadores de pacotes. E um dos dois é necessário para instalar a CLI do VTEX IO.
 
-<div class="alert alert-info">
-Se você não está acostumado a trabalhar com gerenciadores de pacotes, entenda mais sobre essas ferramentas:<br>
-<ul>
-  <li>
-    <a href="https://www.npmjs.com/">npm</a>
-  </li>
-  <li>
-    <a href="https://yarnpkg.com/">yarn</a>
-  </li>
-</ul>
-</div>
+>ℹ️ Se você não está acostumado a trabalhar com gerenciadores de pacotes, entenda mais sobre essas ferramentas:
+>
+> 
+>
+> * [npm](https://www.npmjs.com/)
+>
+> * [yarn](https://yarnpkg.com/)
+> 
 
 ## Instalar a CLI do VTEX IO
 
diff --git a/docs/tracks/pt/instore-basic-settings.md b/docs/tracks/pt/instore-basic-settings.md
index 881245ded..ecaebefb8 100644
--- a/docs/tracks/pt/instore-basic-settings.md
+++ b/docs/tracks/pt/instore-basic-settings.md
@@ -16,15 +16,11 @@ trackSlugPT: instore-primeiros-passos-e-configuracoes
 
 O VTEX Sales App é um dos principais produtos da VTEX para operações de [Comércio Unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv). Ele é um aplicativo que permite à sua loja oferecer uma experiência omnichannel real, integrando seus canais online e físicos e colocando seus clientes no centro do negócio.
 
-<div class="alert alert-info">
-<p>Verifique se a sua loja cumpre todos os <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u">pré-requisitos para usar o VTEX Sales App</a> antes de começar a utilizá-lo.</p>
-</div>
+>ℹ️ Verifique se a sua loja cumpre todos os [pré-requisitos para usar o VTEX Sales App](https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb/1wtAanSRA3g2316dw7bw8u) antes de começar a utilizá-lo.
 
 Para utilizar o VTEX Sales App, você precisa seguir os passos descritos a seguir na sua conta principal.
 
-<div class="alert alert-warning">
-<p> Não é necessário instalar ou configurar o VTEX Sales App nas contas franquias que representam lojas físicas. Você deve realizar o procedimento descrito neste artigo apenas na conta principal da marca.</p>
-</div>
+>⚠️ Não é necessário instalar ou configurar o VTEX Sales App nas contas franquias que representam lojas físicas. Você deve realizar o procedimento descrito neste artigo apenas na conta principal da marca.
 
 ## Instalar o VTEX Sales App
 
@@ -68,9 +64,7 @@ Se você optar por `Pular este passo`, uma loja fictícia será criada para fins
 
 Você precisa definir um email e um nome para serem usados como credenciais de login de um vendedor. Quando estiver pronto, clique em `Confirmar`.
 
-<div class="alert alert-warning">
-<p>O email registrado nesta tela <strong>não</strong> pode ser um email já em uso no Admin da plataforma VTEX. Use emails de vendedores que não possuem acesso ao Admin.</p>
-</div>
+>⚠️ O email registrado nesta tela **não** pode ser um email já em uso no Admin da plataforma VTEX. Use emails de vendedores que não possuem acesso ao Admin.
 
 Nesta etapa, você registra apenas um de seus vendedores. Após as configurações básicas, você poderá [adicionar outros vendedores](https://help.vtex.com/pt/tracks/instore-setting-up--zav76TFEZlAjnyBVL5tRc/5PSjRstg7UU4lOm0s8aqKN).
 
diff --git a/docs/tracks/pt/instore-customizations.md b/docs/tracks/pt/instore-customizations.md
index b66809881..d41ded7c6 100644
--- a/docs/tracks/pt/instore-customizations.md
+++ b/docs/tracks/pt/instore-customizations.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugPT: instore-customizacoes
 ---
 
-<div class="alert alert-danger">
-A maior parte das customizações do inStore envolvem e alteração do arquivo JavaScript <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div> 
+>❗ A maior parte das customizações do inStore envolvem e alteração do arquivo JavaScript `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos. 
 
 ## Acessando o arquivo de customização do inStore
 
@@ -50,9 +48,7 @@ Para fazer qualquer alteração, basta incluir ou modificar as linhas de código
 
 ![20. inStore Customizations (intro) - 3](https://images.ctfassets.net/alneenqid6w5/4MRxgu5pLvZYTa8hGObbH1/96489ddb7665b702da05e72fd6d7e1bf/20._inStore_Customizations__intro__-_3.png)
 
-<div class="alert alert-warning">
-Siga sempre as instruções de customização desta documentação e faça apenas as alterações conforme indicadas aqui.
-</div>
+>⚠️ Siga sempre as instruções de customização desta documentação e faça apenas as alterações conforme indicadas aqui.
 
 ## Customizações do inStore
 
diff --git a/docs/tracks/pt/instore.md b/docs/tracks/pt/instore.md
index 8fe2fd311..c24e51624 100644
--- a/docs/tracks/pt/instore.md
+++ b/docs/tracks/pt/instore.md
@@ -52,9 +52,7 @@ Basta inserir um desses dados no campo e clicar no botão __Confirmar__.
 
 Alternativamente, caso você tenha habilitado Usuário Anônimo, é possível avançar sem identificar o cliente. Para isso, basta clicar em __Continuar sem identificação__.
 
-<div class="alert alert-info">
-Embora seja possível atender clientes sem identificá-los, recomendamos sempre fazer a identificação, uma vez que isso dá ao vendedor uma série de informações contextuais que aumentam as chances de conversão.
-</div>
+>ℹ️ Embora seja possível atender clientes sem identificá-los, recomendamos sempre fazer a identificação, uma vez que isso dá ao vendedor uma série de informações contextuais que aumentam as chances de conversão.
 
 ## 3. Busca Omnichannel
 
diff --git a/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
index 3c76e97cc..77b994eeb 100644
--- a/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/pt/integrating-instore-to-a-new-payment-acquirer.md
@@ -36,9 +36,7 @@ Se necessário, o inStore pode enviar informações adicionais. Exemplo com o su
 - `administrativePassword`: string - senha padrão. Por exemplo, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-Para criar qualquer configuração extra, você precisa enviar para a equipe do inStore (instoredevs@vtex.com.br) os extras que a app precisa para concluir a transação. Assim, criaremos um formulário no módulo de Pagamentos para que o cliente possa configurar seu adquirente.
-</div>
+>ℹ️ Para criar qualquer configuração extra, você precisa enviar para a equipe do inStore (instoredevs@vtex.com.br) os extras que a app precisa para concluir a transação. Assim, criaremos um formulário no módulo de Pagamentos para que o cliente possa configurar seu adquirente.
 
 ## URI de envio e URI de resposta para cada ação
 
@@ -123,9 +121,7 @@ URI final que a app de pagamento receberá para executar a ação de reembolso c
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&autoConfirm=True&sellerName=instoreqa&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class="alert alert-warning">
-<strong>OBSERVAÇÃO:</strong> Nem todos os parâmetros serão utilizados por todos os adquirentes/apps de pagamento. Exemplo: <code>transactionId</code>. Este parâmetro é o ID de uma transação na VTEX que identifica todos os pagamentos de um pedido completo no PCI Gateway da VTEX. Uma transação pode conter vários pagamentos, como quando um pedido é pago com vários cartões de crédito ou débito.
-</div>
+>⚠️ **OBSERVAÇÃO:** Nem todos os parâmetros serão utilizados por todos os adquirentes/apps de pagamento. Exemplo: `transactionId`. Este parâmetro é o ID de uma transação na VTEX que identifica todos os pagamentos de um pedido completo no PCI Gateway da VTEX. Uma transação pode conter vários pagamentos, como quando um pedido é pago com vários cartões de crédito ou débito.
 
 ## Exemplos de URI de resposta para cada ação
 
@@ -184,9 +180,7 @@ Para que a integração funcione, é preciso que o cliente configure no módulo
 
 A integração do AppLinking não inclui outras dependências, uma vez que a comunicação entre o aplicativo inStore e o aplicativo de pagamento acontece com URIs específicas contendo todos os parâmetros de configuração e pagamento necessários para a ação.
 
-<div class="alert alert-warning">
-No Android, toda comunicação deve acontecer com uma nova <code>Intent</code>. Isso significa que você não deve enviar a resposta como um retorno de chamada da <code>Intent</code> inicial. Em vez disso, você deve enviar um novo <code>Intent</code> ao aplicativo inStore com a resposta do anterior.
-</div>
+>⚠️ No Android, toda comunicação deve acontecer com uma nova `Intent`. Isso significa que você não deve enviar a resposta como um retorno de chamada da `Intent` inicial. Em vez disso, você deve enviar um novo `Intent` ao aplicativo inStore com a resposta do anterior.
 
 Para configurar o conector do InStore, você deve seguir os passos abaixo:
 
diff --git a/docs/tracks/pt/integrating-with-magazine-luiza.md b/docs/tracks/pt/integrating-with-magazine-luiza.md
index 593cd4205..4d4e03a58 100644
--- a/docs/tracks/pt/integrating-with-magazine-luiza.md
+++ b/docs/tracks/pt/integrating-with-magazine-luiza.md
@@ -16,9 +16,7 @@ trackSlugPT: configurar-integracao-com-o-magazine-luiza
 
 Para utilizar o conector da Plataforma VTEX e começar a vender no Magalu, primeiramente o [seller](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) precisa se [cadastrar no portal Magazine Luiza Marketplace](https://marketplace-vendamais.magazineluiza.com.br/). Após feito isso, será enviado para o email utilizado no cadastro, um login (Usuário API) e senha (Senha API).
 
-<div class="alert alert-danger">
-Se você não adquirir o Usuário API e Senha API do cadastro da sua loja no Magazine Luiza, não será possível realizar a integração.
-</div>
+>❗ Se você não adquirir o Usuário API e Senha API do cadastro da sua loja no Magazine Luiza, não será possível realizar a integração.
 <br/>
 Para dar seguimento à integração, os próximos passos são:
 
diff --git a/docs/tracks/pt/integration-overview.md b/docs/tracks/pt/integration-overview.md
index ea2ddcafb..075200b7e 100644
--- a/docs/tracks/pt/integration-overview.md
+++ b/docs/tracks/pt/integration-overview.md
@@ -16,9 +16,7 @@ trackSlugPT: integracao-com-o-facebook
 
 Este guia orienta como integrar com o Facebook através do conector desenvolvido pela VTEX. A integração por conector nativo deve ser sua escolha padrão, pois representa mais eficiência e segurança.
 
-<div class="alert alert-danger">
-É possível <a href="https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242">configurar a integração por arquivo XML</a>. Entretanto, é desaconselhável integrar simultaneamente por arquivo XML e conector nativo, pois isso acarreta conflitos e divergência de informações.
-</div>
+>❗ É possível [configurar a integração por arquivo XML](https://help.vtex.com/pt/tutorial/configurando-xml--tutorials_242). Entretanto, é desaconselhável integrar simultaneamente por arquivo XML e conector nativo, pois isso acarreta conflitos e divergência de informações.
 
 Antes de realizar a integração, é necessário que você tenha criado:
 
@@ -35,8 +33,6 @@ Os próximos passos para integrar sua loja VTEX ao Facebook são:
 
 Após a realização dessas etapas, a integração terá sido concluída. Entretanto, atributos de produtos não terão sido enviados.
 
-<div class="alert alert-info">
-Se for do seu interesse enviar os atributos dos seus produtos para o Facebook, é necessário fazer um mapeamento por planilha das categorias e atributos. Este mapeamento é opcional, mas se realizado deve seguir todas as etapas descritas. Caso contrário, podem ocorrer erros na integração.
-</div>
+>ℹ️ Se for do seu interesse enviar os atributos dos seus produtos para o Facebook, é necessário fazer um mapeamento por planilha das categorias e atributos. Este mapeamento é opcional, mas se realizado deve seguir todas as etapas descritas. Caso contrário, podem ocorrer erros na integração.
 
 Os passos necessários para efetuar o mapeamento de categorias e atributos estão descritos adiante no artigo [Envio de produtos para o Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc/41qzoa7TWIYTyIhABHdgzI).
diff --git a/docs/tracks/pt/intelligent-synonyms.md b/docs/tracks/pt/intelligent-synonyms.md
index b4133789c..a9411aa39 100644
--- a/docs/tracks/pt/intelligent-synonyms.md
+++ b/docs/tracks/pt/intelligent-synonyms.md
@@ -14,9 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade está  disponível para contas que tenham um número mínimo de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. É possível que taxas extras se apliquem futuramente.</p>
-</div>
+>ℹ️ Esta funcionalidade está  disponível para contas que tenham um número mínimo de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests). É possível que taxas extras se apliquem futuramente.
 
 A funcionalidade de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) permite cadastrar palavras, ou expressões de mesmo sentido, para termos de busca utilizados pelos clientes ao realizar pesquisas na sua loja, aumentando a chance deles obterem resultados relevantes nas buscas.
 
diff --git a/docs/tracks/pt/introduction-to-vtex.md b/docs/tracks/pt/introduction-to-vtex.md
index 5c497fae3..31caf27ae 100644
--- a/docs/tracks/pt/introduction-to-vtex.md
+++ b/docs/tracks/pt/introduction-to-vtex.md
@@ -20,17 +20,13 @@ A imagem a seguir apresenta as soluções e possibilidades da VTEX, que serão a
 
 ![vtex_composable_complete_PT](https://images.ctfassets.net/alneenqid6w5/7wKnayzJJYUKq2PLrGrfEc/c5b053eec0632543c254624f13bf6dbf/vtex_composable_complete_PT.png)
 
-<div class="alert alert-info">
-Além dos portais de documentação Help Center e <a href="https://developers.vtex.com/">Developer Portal</a> e da <a href="https://community.vtex.com/">VTEX Community</a>, em nosso <a href="https://vtex.com/br-pt/">site</a> disponibilizamos mais informações sobre a plataforma por meio de <a href="https://vtex.com/br-pt/resources-category/product-demo-videos-br/">demo videos</a> (somente inglês) e <a href="https://vtex.com/br-pt/resources-category/ebooks-br/">ebooks</a> criados por <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros</a>. Também é possível conferir uma série de <a href="https://sites.google.com/vtex.com.br/onboardingvtex/trilha">vídeos de onboarding</a> (somente português).
-</div>
+>ℹ️ Além dos portais de documentação Help Center e [Developer Portal](https://developers.vtex.com/) e da [VTEX Community](https://community.vtex.com/), em nosso [site](https://vtex.com/br-pt/) disponibilizamos mais informações sobre a plataforma por meio de [demo videos](https://vtex.com/br-pt/resources-category/product-demo-videos-br/) (somente inglês) e [ebooks](https://vtex.com/br-pt/resources-category/ebooks-br/) criados por [parceiros](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao). Também é possível conferir uma série de [vídeos de onboarding](https://sites.google.com/vtex.com.br/onboardingvtex/trilha) (somente português).
 
 ## Visão geral desta trilha
 
 Esta trilha apresenta a jornada de uma loja VTEX desde as [configurações iniciais](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) até o [go-live](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH). Mas antes de configurar os [módulos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) da plataforma, planejar as [integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) e escolher uma tecnologia de [frontend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ) para a construção da frente de loja, existe um passo anterior: definir o [tipo de conta e a arquitetura](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) que melhor atende às necessidades do negócio.
 
-<div class="alert alert-warning">
-Cada operação de ecommerce possui suas particularidades e este conteúdo não busca traduzir todas as situações existentes. O objetivo é fornecer um modelo geral e apresentar de forma contextualizada os recursos e as possibilidades da plataforma VTEX.
-</div>
+>⚠️ Cada operação de ecommerce possui suas particularidades e este conteúdo não busca traduzir todas as situações existentes. O objetivo é fornecer um modelo geral e apresentar de forma contextualizada os recursos e as possibilidades da plataforma VTEX.
 
 A organização sequencial do conteúdo existe para fins didáticos e não significa que as etapas devam ser realizadas de forma sequencial, ou que a etapa anterior seja um bloqueio para a seguinte, pois algumas etapas podem ser executadas em paralelo, ao menos parcialmente. É o caso das integrações de backend, as configurações de alguns módulos e a implementação de frontend.
 
diff --git a/docs/tracks/pt/live-support.md b/docs/tracks/pt/live-support.md
index c90e4679c..e6ac28813 100644
--- a/docs/tracks/pt/live-support.md
+++ b/docs/tracks/pt/live-support.md
@@ -36,9 +36,7 @@ Se optar por não utilizar, é necessário definir uma mensagem de indisponibili
 ![Fuso horário](https://images.ctfassets.net/alneenqid6w5/6cJ4PNNKSc4LQl7MHuBLNA/70da2f837c8ace1dcf4f03196d03eeb6/Hor__rios_de_funcionamento.png)
 3. Selecione os dias e defina os horários de funcionamento do seu Atendimento Humano. É possível definir mais de um período de atendimento por dia de semana. 
 
-<div class="alert alert-info">
-Em caso de feriados fixos, regionais ou outras datas em que não possua atendimento, informe a data e o horário em que o atendimento não estará disponível. Caso os períodos se repitam anualmente, é possível selecionar “recorrência anual”, pré-definindo a configuração para os próximos períodos.
-</div>
+>ℹ️ Em caso de feriados fixos, regionais ou outras datas em que não possua atendimento, informe a data e o horário em que o atendimento não estará disponível. Caso os períodos se repitam anualmente, é possível selecionar “recorrência anual”, pré-definindo a configuração para os próximos períodos.
 
 <ol start="4">
   <li>Se houver alguma exceção de atendimento, informe os períodos de indisponibilidade.<br><img src="//images.ctfassets.net/alneenqid6w5/2z0LWtsZqBbxpjbf060Hvu/b9e85eff01bcd5f86a685720b7b9a1f0/image4.png" alt="Exceções ou feriados"></li>
diff --git a/docs/tracks/pt/livelo-integration-overview.md b/docs/tracks/pt/livelo-integration-overview.md
index c7fa31b4b..3f6d60b93 100644
--- a/docs/tracks/pt/livelo-integration-overview.md
+++ b/docs/tracks/pt/livelo-integration-overview.md
@@ -20,8 +20,7 @@ A Livelo é a plataforma de marketplace com o maior programa de recompensas do B
 
 A configuração com a Livelo tem como objetivo conectar sua loja VTEX com o marketplace, permitindo que você anuncie seus produtos, aumente suas vendas e atingindo novos clientes a partir deste novo canal.   
 
-<div class="alert alert-info"> A funcionalidade <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> (MOI) não está disponível na integração com a Livelo.
-</div>  
+>ℹ️ A funcionalidade [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) (MOI) não está disponível na integração com a Livelo.  
 
 A configuração da integração está disponível somente para lojas VTEX do Brasil integrarem produtos de todas as categorias.  
 Para realizar a configuração entre VTEX e Livelo, é necessário concluir as etapas:  
diff --git a/docs/tracks/pt/livelo-integration-registration.md b/docs/tracks/pt/livelo-integration-registration.md
index 5bff26699..5b21845a0 100644
--- a/docs/tracks/pt/livelo-integration-registration.md
+++ b/docs/tracks/pt/livelo-integration-registration.md
@@ -22,9 +22,9 @@ Terminadas as etapas de configuração da sua conta na Livelo e da sua conta na
 4. Clique no botão **`GET APP`**.
 5. Retorne para a página **Marketplaces e Integrações** e preencha os campos da tela descritos logo abaixo e, em seguida, clique no botão `Salvar`.  
 
-<div class="alert alert-danger">
-Nesta etapa as credenciaisda Livelo são necessárias. <br>Todos os campos da tela de configuração da Livelo são obrigatórios.</br>
-</div>  
+>❗ Nesta etapa as credenciaisda Livelo são necessárias. 
+>
+> Todos os campos da tela de configuração da Livelo são obrigatórios.</br>  
 
 | **Campo** | **Descrição** | **Exemplo** |
 |---|---|---|
diff --git a/docs/tracks/pt/manage-skus-in-inventory.md b/docs/tracks/pt/manage-skus-in-inventory.md
index 89a5b3f8c..a0289047b 100644
--- a/docs/tracks/pt/manage-skus-in-inventory.md
+++ b/docs/tracks/pt/manage-skus-in-inventory.md
@@ -50,9 +50,7 @@ Mas atente-se antes para o preenchimento correto dessa planilha. Para isso, siga
 
 ## API REST
 
-<div class="alert alert-warning">
-As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre <a href="https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2">como gerar um Appkey e um AppToken para autenticar suas integrações</a>
-</div>
+>⚠️ As autenticações para as chamadas de API REST do módulo de Preços devem ser feitas via AppKey e AppToken. Para entender mais, acesse nosso artigo sobre [como gerar um Appkey e um AppToken para autenticar suas integrações](https://help.vtex.com/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes--43tQeyQJgAKGEuCqQKAOI2)
 
 Para alterar a quantidade de um SKU em estoque por API, você precisa enviar um __PUT__ para o seguinte endpoint:
 
diff --git a/docs/tracks/pt/managing-accounts.md b/docs/tracks/pt/managing-accounts.md
index 0a4cfe8f6..df5922774 100644
--- a/docs/tracks/pt/managing-accounts.md
+++ b/docs/tracks/pt/managing-accounts.md
@@ -36,9 +36,7 @@ Apresenta informações sobre o status da conta (ativa, inativa), código de ide
 
 Exibe o valor do crédito disponível para o cliente utilizar em compras e o valor total a ser pago (em títulos), por compras já realizadas utilizando o Customer Credit como meio de pagamento.
 
-<div class="alert alert-warning">
-Quando o cliente realiza uma compra utilizando o Customer Credit, mas o pedido ainda não foi faturado (título emitido), o campo <b>Crédito reservado</b> também é exibido nesta tela contendo a informação do valor do pedido.
-</div>
+>⚠️ Quando o cliente realiza uma compra utilizando o Customer Credit, mas o pedido ainda não foi faturado (título emitido), o campo **Crédito reservado** também é exibido nesta tela contendo a informação do valor do pedido.
 
 ## Gerenciar
 
@@ -74,6 +72,4 @@ A partir deste momento, o cliente e seu dependente poderão utilizar de forma co
 
 Caso deseje encerrar a conta do cliente, na seção __Outros__, clique em `FECHAR CONTA`.
 
-<div class="alert alert-warning">
-Uma conta do Customer Credit fechada não poderá ser reaberta novamente e os dados de títulos, extrato e dependentes adicionais serão apagados. Entretanto, após concluir o encerramento da conta, caso deseje, você poderá <a href="https://help.vtex.com/pt/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#criar-contas-individualmente">abrir uma nova conta</a> para o cliente utilizando o mesmo email da conta encerrada.
-</div>
+>⚠️ Uma conta do Customer Credit fechada não poderá ser reaberta novamente e os dados de títulos, extrato e dependentes adicionais serão apagados. Entretanto, após concluir o encerramento da conta, caso deseje, você poderá [abrir uma nova conta](https://help.vtex.com/pt/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/7FHLd0cmxqqGeEUuc8uioU#criar-contas-individualmente) para o cliente utilizando o mesmo email da conta encerrada.
diff --git a/docs/tracks/pt/managing-customer-credit-invoices.md b/docs/tracks/pt/managing-customer-credit-invoices.md
index 1ce9b84f7..86f20c5e1 100644
--- a/docs/tracks/pt/managing-customer-credit-invoices.md
+++ b/docs/tracks/pt/managing-customer-credit-invoices.md
@@ -27,9 +27,7 @@ A tela de __Títulos__ no Admin VTEX (__Aplicativos > Customer Credit > Títulos
 
 Para selecionar a lista de títulos a ser exibida é possível clicar em um dos quatro status (Aberto, Pago, Cancelado ou Vencido), ou inserir o número de identificação do pedido para qual o título foi emitido.
 
-<div class="alert alert-warning">
-No Customer Credit, todos os títulos são criados com o status <b>Aberto</b>.
-</div>
+>⚠️ No Customer Credit, todos os títulos são criados com o status **Aberto**.
 
 ## Detalhes do título
 
@@ -42,9 +40,7 @@ Para facilitar o processo de pagamento de um título, é possível fornecer um l
 - Utilizar a função `IMPORTAR` para inserir dados de uma planilha .csv.
 - Via endpoint [PUT Change Invoice](https://developers.vtex.com/docs/api-reference/customer-credit-api#put-/api/creditcontrol/accounts/-creditAccountId-/invoices/-invoiceId-) do Customer Credit API.
 
-<div class="alert alert-info">
-  Após você realizar um dos procedimentos acima, o cliente terá acesso ao botão <b>PAGAR</b> que ficará disponível na sua área do cliente no site da loja (<b>Minha Conta > Meus Créditos</b>).
-</div>
+>ℹ️ Após você realizar um dos procedimentos acima, o cliente terá acesso ao botão **PAGAR** que ficará disponível na sua área do cliente no site da loja (**Minha Conta > Meus Créditos**).
 
 ### Liquidação individual
 
diff --git a/docs/tracks/pt/managing-shipping-rates.md b/docs/tracks/pt/managing-shipping-rates.md
index 4856d5852..db30d1662 100644
--- a/docs/tracks/pt/managing-shipping-rates.md
+++ b/docs/tracks/pt/managing-shipping-rates.md
@@ -37,9 +37,7 @@ Depois que a loja fecha o contrato com uma transportadora, normalmente ela infor
 - **Country**: País onde a entrega será realizada. Deve ser preenchido com o [código ISO de 3 dígitos do país](https://countrycode.org/).
 - **MinimumValueInsurance**: É um adicional de frete com valor absoluto, que será comparado ao valor cadastrado em PricePercent e multiplicado pelo valor do carrinho. O valor que for maior será o adicionado ao frete. Sempre será adicionado ao frete apenas um dos dois. Veja mais em [Para que serve o campo Minimum Value Insurance?](/pt/faq/para-que-serve-o-campo-na-tabela-de-frete-minimum-value-insurance).
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato <strong>.zip</strong>. Esse arquivo .zip também deve ter menos de 10 MB para o upload funcionar. Se, ainda assim, o arquivo exceder o limite, recomendamos dividir a planilha entre mais de uma transportadora.
-</div>
+>⚠️ **OBS:** Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato **.zip**. Esse arquivo .zip também deve ter menos de 10 MB para o upload funcionar. Se, ainda assim, o arquivo exceder o limite, recomendamos dividir a planilha entre mais de uma transportadora.
 
 ## Gerenciar as tarifas de envio por fora da planilha
 
diff --git a/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md b/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
index 91401ca71..3cb75b7bf 100644
--- a/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
+++ b/docs/tracks/pt/managing-the-integration-with-tiktok-for-business-in-vtex-admin.md
@@ -73,11 +73,12 @@ Ao desconectar, a sua integração com o TikTok é interrompida por completo: o
 
 Por outro lado, os produtos já existentes não são excluídos do TikTok pela VTEX, ou seja, continuam aparecendo no TikTok. Para eliminá-los do TikTok, é necessário excluir manualmente os produtos no [TikTok Catalog Manager](https://ads.tiktok.com/help/article?aid=10001005).
 
-<div class="alert alert-warning">
-<p> Caso apareça uma mensagem de erro ao desconectar o TikTok da sua loja VTEX, siga os passos abaixo para garantir que a integração será desabilitada corretamente.</p>
-<ol><li>Acesse a página <a href="https://ads.tiktok.com/ac/page/authorizations">Autorizações</a> no TikTok Ads Manager.</li>
-  <li>Encontre a opção <strong>VTEX</strong>.</li>
-  <li>Clique em <code>Remover</code>.</li></ol>
-</div>
+>⚠️ Caso apareça uma mensagem de erro ao desconectar o TikTok da sua loja VTEX, siga os passos abaixo para garantir que a integração será desabilitada corretamente.
+>
+> Acesse a página [Autorizações](https://ads.tiktok.com/ac/page/authorizations) no TikTok Ads Manager.
+>
+> 2. Encontre a opção **VTEX**.
+>
+> 3. Clique em `Remover`.
 
 Após desconectar, é possível reconectar a integração a qualquer momento refazendo os passos descritos em [Configurar a integração com o TikTok for Business](https://help.vtex.com/pt/tracks/integracao-com-o-tiktok--1r0yJSO11nrer1YVu3WTFd/4AEUg7pEdX1beOaQhFf0wC).
diff --git a/docs/tracks/pt/mapping-categories-variations-and-attributes-in-netshoes.md b/docs/tracks/pt/mapping-categories-variations-and-attributes-in-netshoes.md
index b229a5082..177698f15 100644
--- a/docs/tracks/pt/mapping-categories-variations-and-attributes-in-netshoes.md
+++ b/docs/tracks/pt/mapping-categories-variations-and-attributes-in-netshoes.md
@@ -26,9 +26,7 @@ O mapeamento deve ser feito sempre que um produto for enviado pela primeira vez
 ### Preenchendo a Planilha de Mapeamento
 
 Os campos da **Planilha de Mapeamento** estão detalhados abaixo. Preencha-os de forma a realizar a correspondência _de/para_ entre os valores cadastrados na VTEX e os valores especificados na **Planilha de Consulta** da Netshoes.
-<div class="alert alert-danger">
-<strong>O uso de valores que não aparecem na Planilha de Consulta vai ocasionar um erro na integração.</strong> O preenchimento da Planilha de Mapeamento deve respeitar letras maiúsculas e minúsculas conforme elas aparecem na Planilha de Consulta.
-</div>
+>❗ **O uso de valores que não aparecem na Planilha de Consulta vai ocasionar um erro na integração.** O preenchimento da Planilha de Mapeamento deve respeitar letras maiúsculas e minúsculas conforme elas aparecem na Planilha de Consulta.
 
 *   **ID do SKU:** número de identificação do SKU. Se necessário, consulte [Descobrir o ID de um SKU](https://help.vtex.com/pt/tutorial/descobrir-o-id-de-um-sku--4VQZsYeb3igGK2YowuEYWW).
 
@@ -40,9 +38,7 @@ Os campos da **Planilha de Mapeamento** estão detalhados abaixo. Preencha-os de
 
 *   **Marca:** nome da empresa associada comercialmente ao produto.
 <br/>Exemplo: você está mapeando uma camisa da Nike. De acordo com a Planilha de Consulta, a coluna Marca deve ser preenchida com o valor _Nike_.
-<div class="alert alert-danger">
-Se a marca do seu produto não aparece na Planilha de Consulta, <strong>entre em contato com a Netshoes solicitando a inclusão da marca no sistema.</strong> Somente quando a Netshoes confirmar esse cadastro é que você poderá mapear a marca do produto. Caso contrário, haverá um erro na integração.
-</div>
+>❗ Se a marca do seu produto não aparece na Planilha de Consulta, **entre em contato com a Netshoes solicitando a inclusão da marca no sistema.** Somente quando a Netshoes confirmar esse cadastro é que você poderá mapear a marca do produto. Caso contrário, haverá um erro na integração.
 
 *   **Cor**: valor da coloração do seu produto.
 <br/>Exemplo: você está mapeando um short azul e branco. De acordo com a Planilha de Consulta, a coluna Cor deve ser preenchida com o valor _Azul+Branco._
@@ -58,9 +54,7 @@ Se a marca do seu produto não aparece na Planilha de Consulta, <strong>entre em
 
 *   **Departamento BS**: valor solicitado pela Netshoes para catalogar seus produtos mais rapidamente, utilizando o processo que eles chamam de Fast Lane. Os valores para preenchimento deste campo estão na coluna Atributos da Planilha de Consulta.
 <br/>Exemplo: você está mapeando bijuterias. De acordo com a Planilha de Consulta, a coluna Departamento BS deve ser preenchida com o valor _Acessórios._
-<div class="alert alert-info">
-Em geral, o valor Departamento BS se encontra ao final dos Atributos de um Departamento.
-</div>
+>ℹ️ Em geral, o valor Departamento BS se encontra ao final dos Atributos de um Departamento.
 
 ### Outras Especificações
 
@@ -79,9 +73,7 @@ Depois de preencher a planilha, acesse __Integrações__ no menu do Admin:
 3. Em seguida, clique em __Upload de Mapeamento__.
 4. Escolha a planilha com os dados e clique em __Enviar Arquivo__.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> caso a planilha tenha mais de 10 MB, será necessário separar o conteúdo da planilha em planihas menores de modo a reduzir o tamanho do arquivo.
-</div>
+>⚠️ **OBS:** caso a planilha tenha mais de 10 MB, será necessário separar o conteúdo da planilha em planihas menores de modo a reduzir o tamanho do arquivo.
 
 Com o upload concluído, a integração envia automaticamente todos os produtos da planilha para a Netshoes.
 
diff --git a/docs/tracks/pt/mapping-centauro-categories-variations-and-attributes.md b/docs/tracks/pt/mapping-centauro-categories-variations-and-attributes.md
index 3a53d4abb..8beb0e5d2 100644
--- a/docs/tracks/pt/mapping-centauro-categories-variations-and-attributes.md
+++ b/docs/tracks/pt/mapping-centauro-categories-variations-and-attributes.md
@@ -26,9 +26,7 @@ O objetivo da planilha de mapeamento é indicar para a integração a correspond
 
 O mapeamento só precisa ser feito uma vez para cada categoria. Novos produtos criados dentro de categorias previamente mapeadas serão integrados corretamente, com suas respectivas.
 
-<div class="alert alert-info">
-A planilha de mapeamento é case sensitive, ou seja, é sensível para o uso de letras maiúsculas e minúsculas.
-</div>
+>ℹ️ A planilha de mapeamento é case sensitive, ou seja, é sensível para o uso de letras maiúsculas e minúsculas.
 
 ## Categorização
 
diff --git a/docs/tracks/pt/mapping-product-categories-and-attributes.md b/docs/tracks/pt/mapping-product-categories-and-attributes.md
index 5baff52d4..d7479394d 100644
--- a/docs/tracks/pt/mapping-product-categories-and-attributes.md
+++ b/docs/tracks/pt/mapping-product-categories-and-attributes.md
@@ -27,6 +27,4 @@ Para realizar o mapeamento de categorias, siga as instruções abaixo.
 5. Clique em **Mapeamento de Atributos** e faça as correspondências dos campos que aparecerão na tela.  
 6. Clique no botão `Salvar Alterações` 
 
-<div class="alert alert-info">
-  Os campos de <b>Mapeamento de Atributos</b> com asterisco <b>(*)</b> são obrigatórios.  
-</div>
+>ℹ️ Os campos de **Mapeamento de Atributos** com asterisco **(*)** são obrigatórios.
diff --git a/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md b/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md
index ac86fb3bf..cc9c23db9 100644
--- a/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md
+++ b/docs/tracks/pt/mapping-rappi-product-categories-and-attributes.md
@@ -27,6 +27,4 @@ Para realizar o mapeamento de categorias, siga as instruções abaixo.
 5. Clique em **Mapeamento de Atributos** e faça as correspondências dos campos que aparecerão na tela.  
 6. Clique no botão `Salvar Alterações` 
 
-<div class="alert alert-info">
-  Os campos de <b>Mapeamento de Atributos</b> com asterisco <b>(*)</b> são obrigatórios.  
-</div>
+>ℹ️ Os campos de **Mapeamento de Atributos** com asterisco **(*)** são obrigatórios.
diff --git a/docs/tracks/pt/merchandising-rule-conditions.md b/docs/tracks/pt/merchandising-rule-conditions.md
index 0756b7f3e..522bb2fcb 100644
--- a/docs/tracks/pt/merchandising-rule-conditions.md
+++ b/docs/tracks/pt/merchandising-rule-conditions.md
@@ -22,9 +22,7 @@ Entenda os critérios e operadores possíveis para cada forma de edição nas ta
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"> <thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nome</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descrição</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operadores</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tipo de edição</th> </tr> </thead> <tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span></td> <td rowspan="2" class="t-body pa5">Palavra pesquisada pelo cliente que será relacionada à regra. Campo para preenchimento livre.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td rowspan="2" class="t-body pa5" ><strong>Editor manual:</strong><br>Regras de ativação<br>Regras de customização</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">contém</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Pesquisa pelo exato ID de algum elemento do catálogo que será relacionado à regra. Os possíveis IDs são: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong> e <strong>EAN</strong>. Campo para preenchimento livre.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de customização</td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">categoria</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma categoria cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">departamento</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa um departamento cadastrado no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">marca</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma marca cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">product cluster names</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma coleção cadastrada no Catálogo da loja. A ordem dos produtos é determinada pela relevância do Intelligent Search.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promocao</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que valida se existe ao menos uma promoção vinculada ao item (<span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">yes</span>).</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sellername</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa o nome de um seller.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategoria</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma subcategoria cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{especificação}}</span></td> <td rowspan="2" class="t-body pa5" >Qualquer especificação ativa no Catálogo aparece como critério customizado, com os mesmos valores possíveis. O nome do critério é exatamente o nome da especificação cadastrada. Por exemplo, se houver uma especificação ativa chamada <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Cor</span>, o critério exibido será <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Cor</span>.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> </tbody> </table>
 
-<div class="alert alert-warning">
-  <p>Os critérios <code>departamento</code>, <code>categoria</code> e <code>subcategoria</code> só aparecem como opções para compor as Regras de merchandising se os três níveis de categoria estiverem previamente configurados no <strong>Catálogo</strong>.</p>
-</div>
+>⚠️ Os critérios `departamento`, `categoria` e `subcategoria` só aparecem como opções para compor as Regras de merchandising se os três níveis de categoria estiverem previamente configurados no **Catálogo**.
 
 ## Operadores
 
diff --git a/docs/tracks/pt/next-steps.md b/docs/tracks/pt/next-steps.md
index 77a9306cf..c53eb2c89 100644
--- a/docs/tracks/pt/next-steps.md
+++ b/docs/tracks/pt/next-steps.md
@@ -16,9 +16,7 @@ trackSlugPT: proximos-passos-apos-o-go-live
 
 Agora que a loja está configurada no ambiente VTEX e realizou o [go-live](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/6xYnNxDHUcY6FyChgziCoH), é o momento de conhecer as funcionalidades e [soluções adicionais](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS/1t2QBZvrOBSLgvHaAV9fYm) disponíveis que auxiliam no aumento da performance de vendas e expansão das operações, contribuindo para o desenvolvimento contínuo do negócio.
 
-<div class="alert alert-warning">
-  <p>Através do <a href="https://partnerportal.vtex.com/">VTEX Partner Portal</a>, é possível contratar <a href="https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros</a> para auxiliar no desenvolvimento da loja e gestão das soluções apresentadas neste artigo. Para acessar o portal, o usuário precisa ter <a href="https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz">acesso ao Admin VTEX</a> de uma loja.</p>
-</div>
+>⚠️ Através do [VTEX Partner Portal](https://partnerportal.vtex.com/), é possível contratar [parceiros](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao) para auxiliar no desenvolvimento da loja e gestão das soluções apresentadas neste artigo. Para acessar o portal, o usuário precisa ter [acesso ao Admin VTEX](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4EPwTXx5oFdSG1dA3zIchz) de uma loja.
 
 ## Lançamentos na VTEX
 
diff --git a/docs/tracks/pt/order-flow.md b/docs/tracks/pt/order-flow.md
index d803ce08d..0c78bb451 100644
--- a/docs/tracks/pt/order-flow.md
+++ b/docs/tracks/pt/order-flow.md
@@ -25,9 +25,7 @@ Os conceitos de [Marketplace e Seller](https://help.vtex.com/pt/tutorial/estrate
 - __Marketplace__ é o ambiente onde é realizado o fechamento do pedido, ou seja, onde o cliente realiza o processo de checkout. 
 - __Seller__ é o dono do SKU. É, portanto, o responsável pelo fulfilment - ou seja, por fazer a entrega do produto ao cliente. 
 
-<div class="alert alert-info">
-Toda loja que vende produtos em seu próprio ambiente e realiza suas próprias entregas é Marketplace e Seller ao mesmo tempo.
-</div>
+>ℹ️ Toda loja que vende produtos em seu próprio ambiente e realiza suas próprias entregas é Marketplace e Seller ao mesmo tempo.
 
 É importante entender esses conceitos porque o fluxo do pedido no Marketplace é diferente do fluxo no Seller.
 
@@ -71,14 +69,13 @@ Depois de aprovado o pagamento, o pedido segue para `Pagamento aprovado` e em se
 
 Ou seja, neste caso tanto as etapas de pagamento quanto de entrega são responsabilidade da loja.
 
-<div class="alert alert-info">
-Todo pedido é finalizado em apenas um destes dois status possíveis:<br>
-<ul>
-  <li>Faturado</li>
-  <li>Cancelado</li>
-</ul>
-</div>
-
-<div class="alert alert-info">
-Para entender em mais detalhes cada status dos pedidos, veja uma tabela com todos os status em <a href="https://help.vtex.com/pt/tutorial/fluxo-de-pedido--tutorials_196#entendendo-os-status">Entendendo os status</a>. 
-</div>
+>ℹ️ Todo pedido é finalizado em apenas um destes dois status possíveis:
+>
+> 
+>
+> * Faturado
+>
+> * Cancelado
+> 
+
+>ℹ️ Para entender em mais detalhes cada status dos pedidos, veja uma tabela com todos os status em [Entendendo os status](https://help.vtex.com/pt/tutorial/fluxo-de-pedido--tutorials_196#entendendo-os-status).
diff --git a/docs/tracks/pt/orders-products-and-freight-settings-in-netshoes.md b/docs/tracks/pt/orders-products-and-freight-settings-in-netshoes.md
index 1dadf7a07..808fcd633 100644
--- a/docs/tracks/pt/orders-products-and-freight-settings-in-netshoes.md
+++ b/docs/tracks/pt/orders-products-and-freight-settings-in-netshoes.md
@@ -36,8 +36,6 @@ A implementação dessa API permite que a Netshoes consulte, em tempo real, pre
 
 `http://{accountName}.vtexcommercestable.com.br/api/netshoesintegration/freight`
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> se os Mapeamentos de Entrega não estiverem feitos, não haverá retorno de informações de entrega e frete para essa API.</div> 
+>⚠️ **OBS:** se os Mapeamentos de Entrega não estiverem feitos, não haverá retorno de informações de entrega e frete para essa API. 
 
-<div class="alert alert-danger">
-<strong>OBS 2:</strong> para que a consulta da API seja feita com sucesso, o ID da transportadora e o ID da doca na VTEX deve ser um valor que contenha somente números.</div>
+>❗ **OBS 2:** para que a consulta da API seja feita com sucesso, o ID da transportadora e o ID da doca na VTEX deve ser um valor que contenha somente números.
diff --git a/docs/tracks/pt/pickup-points-concept-definition.md b/docs/tracks/pt/pickup-points-concept-definition.md
index fb82bfad0..20fa8efc3 100644
--- a/docs/tracks/pt/pickup-points-concept-definition.md
+++ b/docs/tracks/pt/pickup-points-concept-definition.md
@@ -16,9 +16,7 @@ trackSlugPT: logistica-101
 
 Um ponto de retirada é um local físico onde o cliente tem a opção de retirar por conta própria o seu pedido. É, portanto, uma etapa opcional e que encerra a rota logística.
 
-<div class="alert alert-info">
-A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao <b>Checkout V6</b>.
-</div>
+>ℹ️ A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao **Checkout V6**.
 
 ## Relação com a transportadora
 Todo ponto de retirada precisa, necessariamente, ser associado a uma transportadora, o que é feito durante o cadastro da transportadora.
diff --git a/docs/tracks/pt/pickup-store.md b/docs/tracks/pt/pickup-store.md
index 6a26c11d7..42a2d8fed 100644
--- a/docs/tracks/pt/pickup-store.md
+++ b/docs/tracks/pt/pickup-store.md
@@ -14,10 +14,8 @@ trackId: t3DOYAJjWgqAMeAKq2MWS
 trackSlugPT: instore-setup
 ---
 
-<div class="alert alert-info">
-Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
-<a href="https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envio</a>.
-</div> 
+>ℹ️ Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
+> [estratégia de envio](https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl). 
 
 
 
diff --git a/docs/tracks/pt/planning-the-go-live.md b/docs/tracks/pt/planning-the-go-live.md
index 1b62d83f8..ae6db6c1b 100644
--- a/docs/tracks/pt/planning-the-go-live.md
+++ b/docs/tracks/pt/planning-the-go-live.md
@@ -68,9 +68,7 @@ Após a data do lançamento oficial, com a loja operando plenamente, os desenvol
 
 Antes de realizar o go-live, é essencial garantir todas as configurações essenciais para o bom funcionamento da loja. Para isso, recomendamos verificar a [Checklist de configuração de loja](https://assets.ctfassets.net/alneenqid6w5/3yv1ofQRJ5xeX7J5EGglGy/dbe5b9175ab01586916c6155ac5681fa/Checklist_de_configura____o_de_loja.xlsx). É preciso confirmar em cada item se as configurações foram concluídas de acordo com as características de operação da loja.
 
-<div class="alert alert-warning">
-  <p>A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. É de responsabilidade da <a href="https://help.vtex.com/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">equipe de implementação</a> de cada loja definir quais funcionalidades e configurações devem ser aplicadas de maneira a produzir a experiência de compra desejada para os clientes. Recomendamos verificar todos os aspectos operacionais da loja e acrescentá-los à lista, caso não estejam presentes.</p>
-</div>
+>⚠️ A checklist indicada acima lista funcionalidades e configurações básicas para o funcionamento de uma loja VTEX. É de responsabilidade da [equipe de implementação](https://help.vtex.com/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao) de cada loja definir quais funcionalidades e configurações devem ser aplicadas de maneira a produzir a experiência de compra desejada para os clientes. Recomendamos verificar todos os aspectos operacionais da loja e acrescentá-los à lista, caso não estejam presentes.
 
 ## 3. Configurações de domínio e conta
 
@@ -80,9 +78,7 @@ Assim que as configurações internas da lojas forem concluídas, será preciso
 2. [Configurar registro CAA](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#configurar-registro-caa): indicar que a autoridade certificadora (CA) **Let’s Encrypt** está autorizada a gerar e renovar certificados que atestam a identidade do domínio. Passo necessário apenas se há registro de CAA no servidor DNS.
 3. [Colocar conta em produção](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX#colocar-conta-em-producao): ativar a conta VTEX em produção. Mesmo após essa ativação, a loja permanece indisponível para acesso de clientes externos. A visualização e compra de produtos na loja só poderão ser efetuadas após a conclusão do go-live, conforme os passos descritos nas próximas seções deste artigo.
 
-<div class="alert alert-warning">
-  <p>A partir do momento em que a conta entra em produção, todos os pedidos serão cobrados automaticamente e o <a href="https://help.vtex.com/pt/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322#valores-da-receita-aprovada">Take Rate</a> será aplicado de acordo com o plano contratado com a VTEX. Isso inclui pedidos realizados no domínio <code>{nomedaloja}.myvtex.com</code>, mesmo que tenham sido realizados para testes.</p>
-</div>
+>⚠️ A partir do momento em que a conta entra em produção, todos os pedidos serão cobrados automaticamente e o [Take Rate](https://help.vtex.com/pt/tutorial/compreenda-o-valor-da-receita-aprovada--tutorials_4322#valores-da-receita-aprovada) será aplicado de acordo com o plano contratado com a VTEX. Isso inclui pedidos realizados no domínio `{nomedaloja}.myvtex.com`, mesmo que tenham sido realizados para testes.
 
 Para obter mais informações, basta consultar o artigo [Configurações](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/7wFsbWgN4rnZsbjhv8IItX), parte da trilha detalhada sobre [Go-live](https://help.vtex.com/pt/tracks/realizando-o-go-live-da-sua-loja--4Ns5FxIiksmjsdX2yOTduM/1iP90RcJvlrfQhnlxM54wo).
 
@@ -94,9 +90,7 @@ Na VTEX, é possível criar ambientes separados para esses testes. Nesse caso, 
 
 Para planejar a fase de testes, vale entrar em contato com o [nosso suporte](https://help.vtex.com/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy), que é por onde é feita a [contratação de um ambiente de teste](https://help.vtex.com/pt/tutorial/contratar-ambiente-de-testes--2nmZAHlfQoGsCWmEWGIoGy).
 
-<div class="alert alert-info">
-  <p>Se a loja for <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#ambiente-de-desenvolvimento">construída com VTEX IO</a>, é possível realizar testes A/B entre workspaces, ou seja, comparar a performance de ambientes de desenvolvimento de frente de loja. Para mais detalhes, basta acessar o guia para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing">Running A/B tests</a>.</p>
-</div>
+>ℹ️ Se a loja for [construída com VTEX IO](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#ambiente-de-desenvolvimento), é possível realizar testes A/B entre workspaces, ou seja, comparar a performance de ambientes de desenvolvimento de frente de loja. Para mais detalhes, basta acessar o guia para desenvolvedores [Running A/B tests](https://developers.vtex.com/docs/guides/vtex-io-documentation-running-native-ab-testing).
 
 ### _Quality Assurance_ (QA)
 
@@ -116,9 +110,7 @@ Após a conclusão dos testes e ajustes necessários, é preciso preparar a loja
 
 1. [Cadastrar domínio na VTEX](https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450): acessar as **Configurações da conta** no Admin VTEX para conectar o endereço à loja.
 
-   <div class="alert alert-warning">
-    <p>Após realizar o cadastro, existe um prazo de sete dias para concluir o go-live. Caso a loja não conclua os procedimentos necessários para go-live neste período, será preciso acessar o cadastro realizado e salvá-lo novamente.</p>
-   </div>
+   >⚠️ Após realizar o cadastro, existe um prazo de sete dias para concluir o go-live. Caso a loja não conclua os procedimentos necessários para go-live neste período, será preciso acessar o cadastro realizado e salvá-lo novamente.
 
 2. **Solicitar apontamento interno:** abrir um ticket para o [Suporte VTEX](https://help.vtex.com/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy) para solicitar o apontamento interno de DNS. O tempo para a conclusão desta solicitação pode ser de até três dias úteis.
 
@@ -152,9 +144,7 @@ Independente do tipo de solicitação a ser encaminhada, o ticket para o Suporte
 - Informar se a loja tem regras condicionais de [políticas comerciais](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE).
 - Caso já exista um site no ar que esteja sendo migrado para a VTEX, informar se utiliza a CDN da Azion ou Cloudfront.
 
-<div class="alert alert-warning">
- <p>Após receber a confirmação do apontamento interno, é necessário realizar o apontamento comum de DNS em até cinco dias. Caso contrário, o apontamento interno será excluído e uma nova solicitação será necessária.</p>
-</div>
+>⚠️ Após receber a confirmação do apontamento interno, é necessário realizar o apontamento comum de DNS em até cinco dias. Caso contrário, o apontamento interno será excluído e uma nova solicitação será necessária.
 
 ## 6. Go-live
 
@@ -162,15 +152,11 @@ No momento do go-live, após a confirmação do apontamento interno realizado na
 
 1. [Realizar apontamento de DNS](https://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dnshttps://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dns): na zona de DNS do domínio, criar uma entrada do tipo CNAME no subdomínio desejado para o destino ``{domínio}.cdn.vtex.com``. O ``{domínio}`` deve ser o mesmo cadastrado na VTEX.
 
-   <div class="alert alert-warning">
-    <p>A propagação do apontamento de DNS pode levar entre 24 a 48 horas para ser concluída, o que significa que o endereço configurado pode não estar acessível a todas as pessoas logo após a configuração.</p>
-   </div>
+   >⚠️ A propagação do apontamento de DNS pode levar entre 24 a 48 horas para ser concluída, o que significa que o endereço configurado pode não estar acessível a todas as pessoas logo após a configuração.
 
 2. [Notificar apontamento](https://help.vtex.com/pt/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#notificar-apontamento): para que a loja fique disponível ao público em geral, é preciso notificar a plataforma VTEX que o apontamento foi realizado. Para isso, é necessário salvar novamente as **Configurações da conta** no Admin VTEX.
 
-   <div class="alert alert-info">
-    <p>Se a loja tiver sido construída com <a href="link-implement-frontend-faststore">FastStore</a>, também será necessário seguir os passos descritos no artigo <a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns">Configuring external DNS for a custom domain</a>.</p>
-   </div>
+   >ℹ️ Se a loja tiver sido construída com [FastStore](link-implement-frontend-faststore), também será necessário seguir os passos descritos no artigo [Configuring external DNS for a custom domain](https://www.faststore.dev/docs/go-live/2-configuring-external-dns).
 
 Uma vez que as etapas acima forem concluídas, a loja estará disponível no domínio cadastrado para que clientes a acessem e realizem compras.
 
diff --git a/docs/tracks/pt/pre-go-live.md b/docs/tracks/pt/pre-go-live.md
index ca9b13468..3fdc3eb9a 100644
--- a/docs/tracks/pt/pre-go-live.md
+++ b/docs/tracks/pt/pre-go-live.md
@@ -20,9 +20,7 @@ Este estágio dá inicio ao go-live já que estes passos precisam ser cuidadosam
 
 Você deve [cadastrar o domínio no Gerenciamento da conta](https://help.vtex.com/pt/tutorial/configurando-dominios-no-license-manager). É isso que conecta o endereço à loja.
 
-<div class="alert alert-warning">
-Após o cadastro do seu domínio, você tem sete dias para concluir o go-live. Caso contrário, deverá acessar o cadastro realizado e salvar novamente.
-</div>
+>⚠️ Após o cadastro do seu domínio, você tem sete dias para concluir o go-live. Caso contrário, deverá acessar o cadastro realizado e salvar novamente.
 
 ## Solicitar apontamento IO
 
diff --git a/docs/tracks/pt/preco-fixo-definicao-de-conceito.md b/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
index a60b9918d..6a748dfd1 100644
--- a/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
+++ b/docs/tracks/pt/preco-fixo-definicao-de-conceito.md
@@ -22,9 +22,7 @@ Desse modo, o preço fixo se sobrepõe ao __preço base__, mesmo em casos que um
 
 Isso significa que o preço fixo tem uma prioridade sobre o preço base e a regra de preço definida para uma tabela.
 
-<div class="alert alert-warning">
-  <p>Apenas <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj">preços fixos</a> são utilizados nas nossas integrações nativas com marketplaces. Outros cenários previstos na <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx">arquitetura do sistema de preços</a> estão disponíveis apenas para marketplace VTEX-VTEX.</p>
-</div>
+>⚠️ Apenas [preços fixos](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj) são utilizados nas nossas integrações nativas com marketplaces. Outros cenários previstos na [arquitetura do sistema de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) estão disponíveis apenas para marketplace VTEX-VTEX.
 
 ## Funcionalidades 
 
diff --git a/docs/tracks/pt/printing-an-order-summary.md b/docs/tracks/pt/printing-an-order-summary.md
index 22736dc52..e2c39e634 100644
--- a/docs/tracks/pt/printing-an-order-summary.md
+++ b/docs/tracks/pt/printing-an-order-summary.md
@@ -38,9 +38,7 @@ Para fazer o pareamento com uma impressora, é necessário cumprir os pré-requi
 * Caso não tenha o VTEX Sales App em seu computador, instalar o aplicativo a partir do nosso guia de [Instalação](https://help.vtex.com/pt/tracks/instore-usando-o-app--4BYzQIwyOHvnmnCYQgLzdr/2rPSJ8519UCCZo5uEBkqxh).
 * Obter um par de credenciais (AppKey e AppToken) com as devidas permissões de acesso. Leia o artigo [Chaves de aplicação](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet) para mais informações.
 
-<div class="alert alert-info">
-<p>Nós recomendamos que o perfil de acesso relacionado a essas credenciais seja o <strong>VTEX Sales App Sales Person</strong>. Porém, um perfil com acesso a outros módulos do Admin, como o <strong>Admin Super</strong>, também pode ser utilizado.</p>
-</div>
+>ℹ️ Nós recomendamos que o perfil de acesso relacionado a essas credenciais seja o **VTEX Sales App Sales Person**. Porém, um perfil com acesso a outros módulos do Admin, como o **Admin Super**, também pode ser utilizado.
 
 ### Passo a passo
 
diff --git a/docs/tracks/pt/product-group-registration-in-netshoes.md b/docs/tracks/pt/product-group-registration-in-netshoes.md
index 79d190f4c..7d030c0c0 100644
--- a/docs/tracks/pt/product-group-registration-in-netshoes.md
+++ b/docs/tracks/pt/product-group-registration-in-netshoes.md
@@ -128,7 +128,7 @@ Para verificar como está estruturado seu catálogo, você pode acessar a seçã
 
 <p></p>
 
-<div class="alert alert-info">Você pode filtrar os resultados para exibir apenas produtos vinculados à política comercial escolhida para a Netshoes na etapa anterior. Para isso, basta clicar em <em>Filtrar resultados ou fazer uma busca</em> e selecionar a política comercial no seletor <em>Loja</em>.</div>
+>ℹ️ Você pode filtrar os resultados para exibir apenas produtos vinculados à política comercial escolhida para a Netshoes na etapa anterior. Para isso, basta clicar em *Filtrar resultados ou fazer uma busca* e selecionar a política comercial no seletor *Loja*.
 
 ## Cadastro do agrupamento de produtos
 
diff --git a/docs/tracks/pt/promotions-for-specific-scenarios.md b/docs/tracks/pt/promotions-for-specific-scenarios.md
index 857b7d4c4..d3d01a20e 100644
--- a/docs/tracks/pt/promotions-for-specific-scenarios.md
+++ b/docs/tracks/pt/promotions-for-specific-scenarios.md
@@ -26,9 +26,7 @@ No entanto, às vezes sua loja pode ter a necessidade de criar promoções para
 - Compre e Ganhe.
 - Limite de itens com promoção no carrinho.
 
-<div class="alert alert-info">
-As telas de configuração de todas as promoções apresentam as mesmas seções principais que as explicadas no artigo sobre Promoção Regular. As opções presentes nessas seções se repetem em todas as promoções, à exceção de algumas configurações específicas de condições para aplicação da promoção. Por isso, neste artigo nos concentramos nessas configurações específicas.
-</div>
+>ℹ️ As telas de configuração de todas as promoções apresentam as mesmas seções principais que as explicadas no artigo sobre Promoção Regular. As opções presentes nessas seções se repetem em todas as promoções, à exceção de algumas configurações específicas de condições para aplicação da promoção. Por isso, neste artigo nos concentramos nessas configurações específicas.
 
 ### Compre Junto
 
@@ -86,9 +84,7 @@ Para entender a promoção do tipo Compre e Ganhe em mais detalhes, veja o artig
 
 Esta configuração define quantos itens do carrinho serão afetados pela promoção.
 
-<div class="alert alert-warning">
-É importante ressaltar que essa possibilidade é <strong>válida apenas para uma promoção regular com desconto percentual</strong>.
-</div>
+>⚠️ É importante ressaltar que essa possibilidade é **válida apenas para uma promoção regular com desconto percentual**.
 
 Depois de preencher todos [os campos de uma promoção regular](https://help.vtex.com/pt/tutorial/regular-promotion--tutorials_327) com desconto percentual, você pode selecionar a opção __Definir quantidade máxima de itens afetados por carrinho__ na seção __Restrições e limites de uso__.
 
diff --git a/docs/tracks/pt/rappi-integration-overview.md b/docs/tracks/pt/rappi-integration-overview.md
index 7d9a9930f..e315848ac 100644
--- a/docs/tracks/pt/rappi-integration-overview.md
+++ b/docs/tracks/pt/rappi-integration-overview.md
@@ -20,13 +20,9 @@ A Rappi é uma plataforma que funciona como marketplace conectando compradores a
 
 A configuração com a Rappi tem o objetivo conectar sua loja VTEX com a plataforma, permitindo que você anuncie seus produtos, aumente suas vendas e alcance novos clientes a partir deste canal.
 
-<div class="alert alert-warning">
-A integração com a Rappi está disponível apenas para lojas VTEX do Brasil, que possuam loja física.
-</div>
+>⚠️ A integração com a Rappi está disponível apenas para lojas VTEX do Brasil, que possuam loja física.
 
-<div class="alert alert-info">
-A funcionalidade <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory</a> (MOI) não está disponível na integração com a Rappi.
-</div>
+>ℹ️ A funcionalidade [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) (MOI) não está disponível na integração com a Rappi.
 
 Para realizar a configuração entre VTEX e Rappi, é necessário concluir algumas etapas:
 
diff --git a/docs/tracks/pt/rappi-integration-registration.md b/docs/tracks/pt/rappi-integration-registration.md
index dd15485e1..d8a857ecf 100644
--- a/docs/tracks/pt/rappi-integration-registration.md
+++ b/docs/tracks/pt/rappi-integration-registration.md
@@ -20,9 +20,7 @@ Terminadas as etapas de configuração da sua conta na Rappi e da sua conta na
 2. Digite **Rappi** na barra de busca da página, clique no card da integração.  
 3. Clique no botão **`Conectar`**.    
 
-<div class="alert alert-info">
-Todos os campos da tela de configuração da Rappi são obrigatórios.
-</div>  
+>ℹ️ Todos os campos da tela de configuração da Rappi são obrigatórios.  
 
 | **Campo** | **Descrição** | **Exemplo** |
 |---|---|---|
diff --git a/docs/tracks/pt/receivables-management.md b/docs/tracks/pt/receivables-management.md
index 953194610..752dbc2f5 100644
--- a/docs/tracks/pt/receivables-management.md
+++ b/docs/tracks/pt/receivables-management.md
@@ -53,6 +53,4 @@ Isso significa que, caso o lojista queira receber o valor total de uma compra as
 
 Assim, o lojista tem a possibilidade de gerenciar melhor seu fluxo de caixa em momentos de queda de receita, por exemplo.
 
-<div class="alert alert-warning">
-  O limite máximo que o lojista pode receber em uma única transferência é de R$ 50.000,00 (cinquenta mil reais). Caso seja necessário retirar um valor maior que este limite, duas ou mais transferências devem ser realizadas.
-  </div>
+>⚠️ O limite máximo que o lojista pode receber em uma única transferência é de R$ 50.000,00 (cinquenta mil reais). Caso seja necessário retirar um valor maior que este limite, duas ou mais transferências devem ser realizadas.
diff --git a/docs/tracks/pt/redirect.md b/docs/tracks/pt/redirect.md
index e29c74ab0..5471b5c55 100644
--- a/docs/tracks/pt/redirect.md
+++ b/docs/tracks/pt/redirect.md
@@ -16,9 +16,7 @@ trackSlugPT: vtex-intelligent-search
 
 **Redirecionamentos** direciona o cliente para qualquer outra página, seja interna ou externa à loja. Esse redirecionamento é feito na área de busca do seu storefront, utilizando termos ou filtros selecionados pelo cliente. Desse modo, uma das vantagens dos Redirecionamentos é contemplar cenários de comunicação que a busca de catálogo da loja não abrange, como o redirecionamento de uma pesquisa por uma marca para a sua página promocional.
 
-<div class="alert alert-warning">
-<p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo VTEX Intelligent Search: configurações Multi-idioma (Beta) para saber mais.</p>
-</div>
+>⚠️ Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo VTEX Intelligent Search: configurações Multi-idioma (Beta) para saber mais.
 
 ## Como o redirecionamento funciona
 
diff --git a/docs/tracks/pt/register-mercado-livre-integration.md b/docs/tracks/pt/register-mercado-livre-integration.md
index e90821d59..1b59c9475 100644
--- a/docs/tracks/pt/register-mercado-livre-integration.md
+++ b/docs/tracks/pt/register-mercado-livre-integration.md
@@ -20,9 +20,7 @@ trackSlugPT: configurar-integracao-do-mercado-livre
 4.	Busque pelas caixas do __Mercado Livre Classic__ ou __Mercado Livre Premium__ e clique em `Integrar`.
 5.	Preencha os campos listados abaixo (o asterisco indica preenchimento obrigatório). Em seguida clique no botão `Salvar configuração`.
 
-<div class="alert alert-info">
-Cada conta VTEX deve estar vinculada a apenas uma conta no Mercado Livre, mesmo se forem utilizados ambos conectores (Classic e Premium). Atualmente não é possível autenticar com duas contas simultaneamente.
-</div>
+>ℹ️ Cada conta VTEX deve estar vinculada a apenas uma conta no Mercado Livre, mesmo se forem utilizados ambos conectores (Classic e Premium). Atualmente não é possível autenticar com duas contas simultaneamente.
 
 - **Integração (se optar por desativar a integração, toda a configuração, incluindo afiliado, serão excluídos)* :** selecione *Ativada* para que a integração comece a operar.
 - **ID do afiliado*:** código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestões: `MLC` (Classic) ou `MLP` (Premium). A configuração do conector cria automaticamente o afiliado.
diff --git a/docs/tracks/pt/register-the-barcode-of-the-skus-for-instore.md b/docs/tracks/pt/register-the-barcode-of-the-skus-for-instore.md
index fbf453c70..d4deccb61 100644
--- a/docs/tracks/pt/register-the-barcode-of-the-skus-for-instore.md
+++ b/docs/tracks/pt/register-the-barcode-of-the-skus-for-instore.md
@@ -16,9 +16,7 @@ trackSlugPT: cadastrar-o-codigo-de-barras-dos-skus-para-instore
 
 Para usar o VTEX Sales App, os produtos da loja física devem estar cadastrados no Catálogo da sua conta na VTEX. É lá que inserimos todos os produtos e definimos suas características.
 
-<div class="alert alert-warning">
-Os vendedores somente terão acesso aos produtos via VTEX Sales App uma vez que eles estejam cadastrados no catálogo da sua loja na VTEX.
-</div>
+>⚠️ Os vendedores somente terão acesso aos produtos via VTEX Sales App uma vez que eles estejam cadastrados no catálogo da sua loja na VTEX.
 
 Entre as informações inseridas no cadastro de um produto no Catálogo, está o __EAN__. O EAN corresponde ao __código de barras__ do SKU. É ele que permite ao vendedor adicionar facilmente o produto ao carrinho do VTEX Sales App, bastando passar o código de barras do produto na máquina leitora. O VTEX Sales App também permite que o código de barras seja digitado no campo de busca.
 
@@ -35,6 +33,4 @@ Para cadastrar o EAN dos SKUs, siga os passos abaixo:
 
 Alternativamente, o campo EAN, assim como demais campos do cadastro de SKU, pode ser preenchido em massa por planilha ou por seu ERP. Confira o artigo [Cadastrar SKUs](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ) para ver informações detalhadas.
 
-<div class="alert alert-info">
-A informação do EAN pode levar até 10 minutos para ser atualizada. Após este procedimento, já será possível adicionar o SKU ao carrinho do VTEX Sales App através da máquina leitora de código de barras.
-</div>
+>ℹ️ A informação do EAN pode levar até 10 minutos para ser atualizada. Após este procedimento, já será possível adicionar o SKU ao carrinho do VTEX Sales App através da máquina leitora de código de barras.
diff --git a/docs/tracks/pt/registering-the-carrefour-integration.md b/docs/tracks/pt/registering-the-carrefour-integration.md
index c3ba68a1a..4288457fd 100644
--- a/docs/tracks/pt/registering-the-carrefour-integration.md
+++ b/docs/tracks/pt/registering-the-carrefour-integration.md
@@ -35,8 +35,7 @@ O cadastro do conector é feito no Admin da VTEX. Para realizá-la, siga as inst
 - __Estoque mínimo:__ determina o valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização do Carrefour pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
 - __Enviar KIT*:__ ao escolher `Não`, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para o Carrefour. Ao habilitar `Sim`, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de `Sim` para `Não`, SKUs enviados anteriormente para o Carrefour não seriam removidos ou sofreriam qualquer alteração. Se você mudar sua configuração de `Não` para `Sim`, você precisará [reindexar a base](https://help.vtex.com/pt/tutorial/manutencao-de-base-full-cleanup--34P9LGs7BCIQK6acQom802) para que a configuração seja aplicada.
 
-<div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para o Carrefour de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b> MARKETPLACE > Integrações > Produtos</b>, ao se clicar sobre o SKU.</div>
+>ℹ️ Com a opção <i>Não</i> ativada, tentativas de envio para o Carrefour de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo ** MARKETPLACE > Integrações > Produtos**, ao se clicar sobre o SKU.
 
 - **Mapeamento de Certificados de Homologação (Opções aceitas pelo marketplace: ANATEL, INMETRO, ANVISA, MAPA e Não Se Aplica):** devido a uma definição do Carrefour, produtos de determinadas categorias deverão possuir obrigatoriamente uma [especificação de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) cadastrada com o código de homologação de cada agência reguladora para serem comercializados no marketplace. Por isso, para as [categorias elegíveis](#categorias-elegiveis), é necessário preencher este campo com o nome da especificação de produto criada e o código de homologação do produto disponibilizado pelas agências reguladoras.
 
@@ -75,10 +74,8 @@ Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `Prod
 `CRF_ProductName` para nome do produto e `CRF_ProductDescription` para descrição do produto.    
 3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
-</div>  
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.  
 
 ### Categorias elegíveis
 
diff --git a/docs/tracks/pt/registering-the-centauro-integration.md b/docs/tracks/pt/registering-the-centauro-integration.md
index 5307823bf..4abca4422 100644
--- a/docs/tracks/pt/registering-the-centauro-integration.md
+++ b/docs/tracks/pt/registering-the-centauro-integration.md
@@ -54,8 +54,6 @@ Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `Prod
 `CTR_ProductName` para nome do produto e `CTR_ProductDescription` para descrição do produto.    
 3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.   
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
-</div>
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.
 
diff --git a/docs/tracks/pt/registering-the-integration.md b/docs/tracks/pt/registering-the-integration.md
index bd81521ea..28f36ef09 100644
--- a/docs/tracks/pt/registering-the-integration.md
+++ b/docs/tracks/pt/registering-the-integration.md
@@ -30,12 +30,11 @@ O cadastro do conector é feito no Admin da VTEX. Para realizá-lo, siga as inst
 - **Estoque mínimo*:** determina o valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização da Casas Bahia Marketplace pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
 - **Enviar KIT*:** ao escolher `Não`, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Casas Bahia Marketplace. Ao habilitar `Sim`, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de `Sim` para `Não`, SKUs enviados anteriormente para a Casas Bahia Marketplace não seriam removidos ou sofreriam qualquer alteração. Se você mudar sua configuração de `Não` para `Sim`, você precisará [reindexar a base](https://help.vtex.com/pt/tutorial/manutencao-de-base-full-cleanup--34P9LGs7BCIQK6acQom802) para que a configuração seja aplicada.
 
-<div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a Casas Bahia Marketplace de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos</b>, ao se clicar sobre o SKU.</div>
+>ℹ️ Com a opção <i>Não</i> ativada, tentativas de envio para a Casas Bahia Marketplace de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo **MARKETPLACE > Integrações > Produtos**, ao se clicar sobre o SKU.
 
 - **E-mails Para Notificação de Pedidos Não Integrados*:** preencher com o e-mail do responsável técnico. Caso ocorra algum erro na integração do pedido, será enviada uma mensagem para o e-mail cadastrado.
 
-<div class="alert alert-warning">Caso você não aperte no botão <code>+</code> para inserir o E-MAIL PARA NOTIFICAÇÃO DE PEDIDOS NÃO INTEGRADOS, aparecerá um alerta de erro ao salvar a configuração.</div>  
+>⚠️ Caso você não aperte no botão `+` para inserir o E-MAIL PARA NOTIFICAÇÃO DE PEDIDOS NÃO INTEGRADOS, aparecerá um alerta de erro ao salvar a configuração.  
 
 **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
 
@@ -58,8 +57,6 @@ Obrigatoriamente `ProductName` para título do produto ou Obrigatoriamente `Prod
 `CBH_ProductName` para nome do produto e `CBH_ProductDescription` para descrição do produto.    
 4. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de <code>Título</code> ou <code>Descrição</code> cadastrados no catálogo.
-</div>
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.
 
diff --git a/docs/tracks/pt/registering-the-netshoes-integration.md b/docs/tracks/pt/registering-the-netshoes-integration.md
index ed38f2dd6..bd7c752bf 100644
--- a/docs/tracks/pt/registering-the-netshoes-integration.md
+++ b/docs/tracks/pt/registering-the-netshoes-integration.md
@@ -24,9 +24,7 @@ trackSlugPT: configurar-integracao-da-netshoes
 
    * **Ambiente*:** escolha a opção _Produção_ para utilizar o ambiente real de vendas da Netshoes. Esta é a configuração sugerida. Caso você queira realizar algum teste na integração, marque _QA_.
 <br/>
-<div class="alert alert-warning">
-<strong>Se você optou pelo ambiente QA</strong>, para que a integração funcione será necessário utilizar um token de teste no campo <strong>Chave de acesso à API da Netshoes</strong> (descrito adiante).
-</div>
+>⚠️ **Se você optou pelo ambiente QA**, para que a integração funcione será necessário utilizar um token de teste no campo **Chave de acesso à API da Netshoes** (descrito adiante).
    * **Id do afiliado*:** código identificador para criação de um [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado) que ainda não esteja cadastrado no seu sistema. O código deve ser composto de três consoantes, sejam elas repetidas ou não, vogais não são aceitas. Sugestão: NTS. A configuração do conector cria automaticamente o afiliado.
 
    * **Email do afiliado*:** preencha com um email para o afiliado que está sendo criado.
@@ -41,17 +39,13 @@ trackSlugPT: configurar-integracao-da-netshoes
 
    * **Mapeamento de Tipo de Entrega (SLA) - Expressa:** insira o tipo de [Política de envio](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/55MezrFTw2limlgT7KUg6l#campos-de-cadastro-de-transportadoras) que você deseja usar para entrega expressa. Exemplo: a XPTO é usada como transportadora, e sua Política de envio na Estratégia de envio da VTEX se chama _Entrega Rápida_. Neste caso, você deve preencher o campo com a palavra _Entrega Rápida_. O termo preenchido deve ser exatamente igual ao cadastrado no Admin, inclusive com relação a letras maiúsculas e minúsculas.
 <br/>
-<div class="alert alert-info">
-Se os campos do Mapeamento de Entrega não são preenchidos, a integração automaticamente escolhe a Política de Envio com o menor preço no momento da realização do pedido.
-</div>
+>ℹ️ Se os campos do Mapeamento de Entrega não são preenchidos, a integração automaticamente escolhe a Política de Envio com o menor preço no momento da realização do pedido.
 
    * **Estoque mínimo (se o saldo do SKU estiver igual ou abaixo do valor configurado, será enviado saldo 0 para o marketplace)*:** determina o valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio é pausado para evitar que sejam feitas vendas sem estoque durante o tempo de atualização da Netshoes pela VTEX. O valor de estoque mínimo é aplicado a todos os produtos, portanto verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
 
    * **Enviar Kit*:** ao escolher _Não_, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a Netshoes. Ao habilitar _Sim_, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de _Sim_ para _Não_, SKUs enviados anteriormente para a Netshoes não seriam removidos ou sofreriam qualquer alteração.
 
-  <div class="alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a Netshoes de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos,</b> ao se clicar sobre o SKU.
-</div> 
+  >ℹ️ Com a opção <i>Não</i> ativada, tentativas de envio para a Netshoes de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo **MARKETPLACE > Integrações > Produtos,** ao se clicar sobre o SKU. 
 
    * **Emails de notificação de erro de pedido:** adicione os endereços eletrônicos por meio dos quais você gostaria de ser notificado em caso de erro de integração de um pedido. Não há um número limite para esses emails.
    * **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
@@ -75,8 +69,6 @@ O preenchimento desse campo deve ser realizado da seguinte maneira:
 2. Preencha o campo PARA com o nome do novo campo.   `NTS_ProductName` para nome do produto e `NTS_ProductDescription` para descrição do produto.  
 3. Clique no botão e uma regra de mapeamento será adicionada a sua integração.  
 
-<div class="alert alert-info">
-Cada regra cadastrada mapeia apenas um campo.
-<p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.<p>
-</div>
+>ℹ️ Cada regra cadastrada mapeia apenas um campo.
+> <p>Caso o campo mapeado não tenha um valor preenchido, será enviado o valor padrão de `Título` ou `Descrição` cadastrados no catálogo.<p>
 
diff --git a/docs/tracks/pt/regra-de-preco-definicao-de-conceito.md b/docs/tracks/pt/regra-de-preco-definicao-de-conceito.md
index fb9519a08..570980b82 100644
--- a/docs/tracks/pt/regra-de-preco-definicao-de-conceito.md
+++ b/docs/tracks/pt/regra-de-preco-definicao-de-conceito.md
@@ -22,9 +22,7 @@ As regras de preço permitem que você mude o preço de um SKU para apenas uma t
 
 Portanto, quando combinamos esta regra ao preço base de um SKU, temos um novo valor. Este será o __preço computado__ de um SKU dentro de uma tabela.
 
-<div class="alert alert-info">
-O uso das regras de preço é <strong>opcional</strong>. Caso algum SKU não tenha nenhum modificador associado a ele, seu preço para a tabela de preços em questão será o preço base cadastrado.
-</div>
+>ℹ️ O uso das regras de preço é **opcional**. Caso algum SKU não tenha nenhum modificador associado a ele, seu preço para a tabela de preços em questão será o preço base cadastrado.
 
 As regras de preço funcionam a partir de __cinco condições de configuração__: 
 
diff --git a/docs/tracks/pt/relevance.md b/docs/tracks/pt/relevance.md
index fa471b97b..b78422041 100644
--- a/docs/tracks/pt/relevance.md
+++ b/docs/tracks/pt/relevance.md
@@ -38,9 +38,7 @@ As informações aplicadas para compor a relevância são:
 
 O conjunto de distribuição de pesos e critérios gera uma pontuação para o produto, o que auxilia no seu posicionamento na ordenação do resultado da pesquisa.
 
-<div class="alert alert-warning">
-  <p>Caso deseje utilizar critérios prioritários, recomendamos adicionar apenas um critério neste campo. Adicionar mais critérios compromete a ordenação do resultado de busca, visto que apenas o primeiro critério será considerado.</p>
-</div>
+>⚠️ Caso deseje utilizar critérios prioritários, recomendamos adicionar apenas um critério neste campo. Adicionar mais critérios compromete a ordenação do resultado de busca, visto que apenas o primeiro critério será considerado.
 
 Dessa forma, é possível adequar o comportamento do resultado de busca a uma estratégia específica.
 
diff --git a/docs/tracks/pt/reports-vtex-intelligent-search.md b/docs/tracks/pt/reports-vtex-intelligent-search.md
index 0a4f0a70e..d93486627 100644
--- a/docs/tracks/pt/reports-vtex-intelligent-search.md
+++ b/docs/tracks/pt/reports-vtex-intelligent-search.md
@@ -40,9 +40,7 @@ Os dados que compõem o relatório são atualizados a cada quatro horas e contê
 * **Pedidos**: quantidades de pedidos realizados a partir da busca. Para calcular essa métrica, consideramos que a busca gera um pedido sempre que, após buscar por um termo, o cliente clica em algum produto que aparece nos resultados e depois compra um produto qualquer (não necessariamente o que ele clicou).
 * **Vendas**: valor total de receitas geradas por pedidos realizados a partir da busca. O cálculo segue a mesma lógica da métrica de **Pedidos**, a diferença é que o resultado reflete as receitas em vez da quantidade de pedidos.
 
-<div class="alert alert-info">
-  <p>Os dados exibidos no relatório são limitados aos 10 mil termos mais pesquisados. Caso deseje os dados completos da busca da sua loja, é necessário <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacao">exportar o relatório</a>.</p>
-</div>
+>ℹ️ Os dados exibidos no relatório são limitados aos 10 mil termos mais pesquisados. Caso deseje os dados completos da busca da sua loja, é necessário [exportar o relatório](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacao).
 
 Quando você optar por [exportar um relatório](#exportacao), existe também a possibilidade de gerá-lo **Com métricas de funil**. Caso essa opção seja selecionada, quatro novas colunas serão adicionadas ao arquivo:
 
diff --git a/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md b/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md
index f0d924aa2..ac78dc130 100644
--- a/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md
+++ b/docs/tracks/pt/scheduled-deliveries-and-delivery-capacity.md
@@ -18,9 +18,9 @@ Uma loja VTEX pode oferecer entregas agendadas para seus clientes. Dessa forma,
 
 Para disponibilizar a [entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) para os clientes, é preciso incluir janelas de entrega na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) da [transportadora ](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE)relacionada. Feito isso, os períodos e dias para entrega agendada ficarão disponíveis no checkout da sua loja.
 
-<div class="alert alert-warning">
-Para que a <a href="https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> e a <a href="https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidade de entrega</a> funcionem corretamente, você deve observar que:<p><ul><li>A soma {<a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID da política de envio} não pode exceder 60 caracteres.</li><li>Não se deve utilizar espaçamento no ID de <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">políticas de envio</a>.</li></ul></p>
-</div>
+>⚠️ Para que a [Entrega agendada](https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) e a [Capacidade de entrega](https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) funcionem corretamente, você deve observar que:
+> *A soma {[account name](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {ID da política de envio} não pode exceder 60 caracteres.
+> * Não se deve utilizar espaçamento no ID de [políticas de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 É importante ressaltar que a disponibilidade das entregas agendadas está de acordo com o serviço que a transportadora contratada (cadastrada pela política de envio) oferece para sua loja. Para acompanhar a disponibilidade de janelas de entrega (ou períodos de envio) e a quantidade de itens/pedidos que ainda pode ser realizada em cada janela de entrega, confira a página de [Capacidade de entrega](https://help.vtex.com/pt/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz).
 
diff --git a/docs/tracks/pt/sending-product-data-to-dafiti.md b/docs/tracks/pt/sending-product-data-to-dafiti.md
index 6a6c1e9f1..874453114 100644
--- a/docs/tracks/pt/sending-product-data-to-dafiti.md
+++ b/docs/tracks/pt/sending-product-data-to-dafiti.md
@@ -23,9 +23,7 @@ Para fazer o mapeamento, siga os passos abaixo:
 3. [Preencher a planilha de mapeamento](#3-preencher-a-planilha-de-mapeamento)
 4. [Fazer upload da planilha de mapeamento](#4-fazer-upload-da-planilha-de-mapeamento)
 
-<div class="alert alert-warning">
-Para cadastrar um produto na VTEX, é obrigatório que você vincule o produto a uma marca. Entretanto, para evitar problemas com o envio de produtos, você deve <a href="https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">preencher</a> o campo <strong>Marca</strong> do produto que será enviado com os nomes das marcas aceitas na Dafiti. Consulte o <a href="https://www.dafiti.com.br/marcas/">glossário de marcas</a> da Dafiti para verificar as marcas aceitas.
-</div>
+>⚠️ Para cadastrar um produto na VTEX, é obrigatório que você vincule o produto a uma marca. Entretanto, para evitar problemas com o envio de produtos, você deve [preencher](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) o campo **Marca** do produto que será enviado com os nomes das marcas aceitas na Dafiti. Consulte o [glossário de marcas](https://www.dafiti.com.br/marcas/) da Dafiti para verificar as marcas aceitas.
 
 ## 1. Fazer download da planilha de consulta da Dafiti
 
@@ -55,9 +53,7 @@ O modelo de planilha de mapeamento fornecido é dividido em três abas:
 | **Attributenames** | Faz a equivalência entre o nome do campo de especificação na VTEX e nome da variação / atributo na Dafiti. |
 | **Attributevalues** | Faz a equivalência entre os valores do campo da especificação na VTEX e valores  da variação / atributo na Dafiti. |
 
-<div class="alert alert-info">
-  A planilha de mapeamento da Dafiti é <em>case sensitive</em>, ou seja, faz distinção entre letras maiúsculas e minúsculas. Leve este fato em consideração quando preencher a planilha.
-</div>
+>ℹ️ A planilha de mapeamento da Dafiti é *case sensitive*, ou seja, faz distinção entre letras maiúsculas e minúsculas. Leve este fato em consideração quando preencher a planilha.
 
 ### Categories
 
@@ -140,6 +136,4 @@ Depois de mapear todos os atributos dos SKUs da sua loja, você deverá fazer up
 
 Não tendo ocorrido nenhum erro com o envio, os produtos serão enviados para a Dafiti com seus respectivos atributos.
 
-<div class="alert alert-info">
- A integração entre VTEX e Dafiti realiza automaticamente o redimensionamento das fotos dos produtos caso elas sejam superiores ao tamanho solicitado pela Dafiti(1000x1000).
-</div>
+>ℹ️ A integração entre VTEX e Dafiti realiza automaticamente o redimensionamento das fotos dos produtos caso elas sejam superiores ao tamanho solicitado pela Dafiti(1000x1000).
diff --git a/docs/tracks/pt/sending-products-to-amazon.md b/docs/tracks/pt/sending-products-to-amazon.md
index 22feecf28..11007f588 100644
--- a/docs/tracks/pt/sending-products-to-amazon.md
+++ b/docs/tracks/pt/sending-products-to-amazon.md
@@ -18,17 +18,13 @@ Feitas as configurações iniciais da integração, é possível enviar os produ
 
 Para enviar os seus produtos para a Amazon, o seller deverá mapear as [categorias](https://help.vtex.com/pt/tutorial/o-que-e-uma-categoria--6HV4Q3E2FauUoOQoiCCgCg) e os [atributos dos produtos](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP).  
 
-<div class="alert alert-info">
-Seus produtos precisam ter o <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a> e <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">Preço</a> configurados antes de enviá-los à Amazon.
-</div>  
+>ℹ️ Seus produtos precisam ter o [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [Preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) configurados antes de enviá-los à Amazon.  
 
 ## Mapear Categorias  
 
 O processo de mapeamento pode ser realizado via Admin VTEX, ou via planilha, veja abaixo como executar em cada caso.  
 
-<div class="alert alert-danger">
-Ao realizar o mapeamento de uma categoria via Admin VTEX, o mapeamento daquela categoria realizado via planilha anteriormente, será sobrescrito e não poderá ser recuperado.
-</div>
+>❗ Ao realizar o mapeamento de uma categoria via Admin VTEX, o mapeamento daquela categoria realizado via planilha anteriormente, será sobrescrito e não poderá ser recuperado.
 
 ### Mapeamento via Admin VTEX (BETA)  
 
@@ -58,10 +54,8 @@ Para realizar o mapeamento de categorias:
 
 5. Clique no botão __`Salvar Alterações`__.  
 
-<div class="alert alert-danger">
-Os campos sinalizados com o asterisco <strong>*</strong> são obrigatórios.  
-O preenchimento de um atributo pode desencadear novos campos obrigatórios que só ficarão visíveis na página <strong> Marketplace> Conexões> Produtos, </strong> após salvar o mapeamento.
-</div>  
+>❗ Os campos sinalizados com o asterisco ***** são obrigatórios.  
+> O preenchimento de um atributo pode desencadear novos campos obrigatórios que só ficarão visíveis na página ** Marketplace> Conexões> Produtos, ** após salvar o mapeamento.  
 
 ### Mapeamento via Planilha  
 
@@ -183,9 +177,7 @@ A planilha possui as seguintes colunas:
 | F | VTEXValue | Nome do valor usado no campo SKU na VTEX |
 | G | AmazonValue | Nome dos valores aceitos pela Amazon |
 
-<div class="alert alert-info">
-A planilha de mapeamento da Amazon é case sensitive, ou seja, é sensível para o uso de letras maiúsculas e minúsculas.
-</div>
+>ℹ️ A planilha de mapeamento da Amazon é case sensitive, ou seja, é sensível para o uso de letras maiúsculas e minúsculas.
 
 Para cada produto, siga os passos a seguir:  
 
@@ -202,9 +194,7 @@ Para cada produto, siga os passos a seguir:
 6. Preencha a coluna **VTEXValue** com os valores do atributo do produto na VTEX.
 7. Preencha a coluna **AmazonValue** com os valores aceitos pela Amazon. Para visualizar os valores aceitos pela Amazon, acesse a [Planilha de atributos obrigatórios da Amazon](#2-planilha-de-atributos-obrigatorios-da-amazon) e busque pela aba `VALORES VÁLIDOS`
 
-<div class="alert alert-warning">
-Em alguns casos, os valores de <strong>VariationTheme</strong> podem ser parecidos. Há categorias em que o <strong>VariationTheme</strong> pode ser: <em>SizeColor</em>, <em>Color</em> e <em>Size</em>, enquanto há outras categorias em que pode ser: <em>ColorSize</em>, <em>Color</em> e <em>Size</em>. A diferença está na ordem, em <em>SizeColor</em>, as caixas de seleção na página do produto estarão ordenadas por tamanho e cor, enquanto em <em>ColorSize</em> estarão ordenadas por cor e tamanho. Esteja atento aos valores válidos de cada categoria que será mapeada. 
-</div>
+>⚠️ Em alguns casos, os valores de **VariationTheme** podem ser parecidos. Há categorias em que o **VariationTheme** pode ser: *SizeColor*, *Color* e *Size*, enquanto há outras categorias em que pode ser: *ColorSize*, *Color* e *Size*. A diferença está na ordem, em *SizeColor*, as caixas de seleção na página do produto estarão ordenadas por tamanho e cor, enquanto em *ColorSize* estarão ordenadas por cor e tamanho. Esteja atento aos valores válidos de cada categoria que será mapeada.
 
 ##### Exemplo de preenchimento 
 
diff --git a/docs/tracks/pt/sending-products-to-facebook.md b/docs/tracks/pt/sending-products-to-facebook.md
index f1b86d4a9..d34de7259 100644
--- a/docs/tracks/pt/sending-products-to-facebook.md
+++ b/docs/tracks/pt/sending-products-to-facebook.md
@@ -32,9 +32,7 @@ Caso você queira enviar atributos de produtos para o Facebook, existe uma etapa
 
 A etapa adicional é a realização de um mapeamento das especificações dos produtos. O mapeamento é o que faz a correspondência entre os atributos cadastrados na sua loja VTEX e os padrões adotados pelo Facebook.
 
-<div class="alert alert-warning">
-O mapeamento de atributos por planilha é opcional,  mas se você escolher realizá-lo, ele deve ser feito seguindo todos os passos descritos no artigo. Caso contrário, podem ocorrer erros na integração.
-</div>
+>⚠️ O mapeamento de atributos por planilha é opcional,  mas se você escolher realizá-lo, ele deve ser feito seguindo todos os passos descritos no artigo. Caso contrário, podem ocorrer erros na integração.
 
 ## Envio de atributos para o Facebook
 
@@ -54,9 +52,7 @@ O primeiro passo para realizar o mapeamento é fazer o download do arquivo [Plan
 
 O segundo passo para o mapeamento é preencher o arquivo baixado. Trata-se de uma planilha, constituída de uma única aba, na qual é possível identificar cinco colunas.
 
-<div class="alert alert-info">
-A planilha de mapeamento do Facebook é <i>case sensitive</i>, ou seja, é sensível para o uso de letras maiúsculas e minúsculas.
-</div>
+>ℹ️ A planilha de mapeamento do Facebook é <i>case sensitive</i>, ou seja, é sensível para o uso de letras maiúsculas e minúsculas.
 
 - **Primeira coluna, _ID Category_:** deve ser preenchida com o número de identificação da categoria do produto na plataforma VTEX. Você encontra o ID de uma categoria no Admin, no módulo _Produtos > Catálogo > Categorias_. O ID da categoria é o número à esquerda do nome da categoria.
 - **Segunda coluna, _VTEX attribute name_:** deve conter o nome do atributo cadastrado na VTEX.
@@ -65,9 +61,7 @@ A planilha de mapeamento do Facebook é <i>case sensitive</i>, ou seja, é sens
 - **Terceira coluna, _Facebook attribute name:_** deve ser preenchida com o termo correspondente utilizado pelo Facebook para um atributo.
 > Exemplo: a correspondência no Facebook para o atributo _Cor_ é _color_.
 
-  <div class="alert alert-info">
-Para saber os nomes de atributos e valores de referência, consulte a documentação do Facebook <a href="https://developers.facebook.com/docs/commerce-platform/catalog/fields?locale=pt_BR#universal-basic-attributes">Universal Basic Attributes</a>. Se não houver correspondência para um atributo ou valor, preencha a coluna Facebook attribute name com o mesmo termo utilizado na VTEX.
-</div>
+  >ℹ️ Para saber os nomes de atributos e valores de referência, consulte a documentação do Facebook [Universal Basic Attributes](https://developers.facebook.com/docs/commerce-platform/catalog/fields?locale=pt_BR#universal-basic-attributes). Se não houver correspondência para um atributo ou valor, preencha a coluna Facebook attribute name com o mesmo termo utilizado na VTEX.
 
 - **Quarta coluna, _VTEX attribute value_:** deve ser preenchida com os valores dos seus atributos na VTEX.
 > Exemplo: digamos que na sua loja VTEX, para o atributo _Gênero_ exista o valor _Feminino._ Portanto, você deve preencher a coluna _VTEX attribute value_ com a palavra _Feminino_.
diff --git a/docs/tracks/pt/sending-products-to-google-shopping.md b/docs/tracks/pt/sending-products-to-google-shopping.md
index a534a5718..4b1a41648 100644
--- a/docs/tracks/pt/sending-products-to-google-shopping.md
+++ b/docs/tracks/pt/sending-products-to-google-shopping.md
@@ -50,9 +50,7 @@ A aprovação dos seus produtos pelo Google vai torná-los ativos, e isso imedia
 
 **Se um produto é reprovado, é necessário revisar seus dados e enviá-los novamente**. Você pode acompanhar o status dos seus produtos no Google Merchant Center.
 
-<div class="alert alert-info">
-Verifique se os seus produtos atendem a <a href="https://support.google.com/merchants/answer/7052112?visit_id=637492777706451215-3729304881&rd=1&hl=pt-BR">Especificação dos dados do produto</a> definida pelo Google. Caso algum produto esteja em desacordo com as exigências, o anúncio será reprovado.
-</div>
+>ℹ️ Verifique se os seus produtos atendem a [Especificação dos dados do produto](https://support.google.com/merchants/answer/7052112?visit_id=637492777706451215-3729304881&rd=1&hl=pt-BR) definida pelo Google. Caso algum produto esteja em desacordo com as exigências, o anúncio será reprovado.
 
 Há situações nas quais a reprovação do produto acontece posteriormente a ele já ter sido considerado ativo. Isso é visto por vezes quando uma conta foi criada recentemente.
 
@@ -66,9 +64,7 @@ No Google Shopping, os produtos automaticamente expiram caso não sejam atualiza
 
 Entretanto, não é algo com o qual você precise se preocupar, pois na integração com o conector da Plataforma VTEX, **os produtos são automaticamente atualizados pelo sistema a cada 29 dias.**
 
-<div class="alert alert-info">
-É possível haver um delay de até 30 minutos entre o processamento da alteração de dados de um produto e sua atualização no feed.
-</div>
+>ℹ️ É possível haver um delay de até 30 minutos entre o processamento da alteração de dados de um produto e sua atualização no feed.
 
 ## Modificar categorização automática
 
@@ -80,6 +76,4 @@ Antes de considerar um problema na categorização, porém, tenha a certeza de q
 
 Para substituir uma categoria incorreta e garantir que o produto seja aprovado, veja o passo-a-passo no artigo do Google [categoria Google do produto](https://support.google.com/merchants/answer/6324436?hl=pt-BR). 
 
-<div class="alert alert-warning">
-O Google aceitará uma modificação de categoria apenas nas situações previstas no artigo <a href="https://support.google.com/merchants/answer/6324436?hl=pt-BR">categoria Google do produto.</a>
-</div>
+>⚠️ O Google aceitará uma modificação de categoria apenas nas situações previstas no artigo [categoria Google do produto.](https://support.google.com/merchants/answer/6324436?hl=pt-BR)
diff --git a/docs/tracks/pt/set-a-price-for-the-sku.md b/docs/tracks/pt/set-a-price-for-the-sku.md
index 966b717ab..d6c373198 100644
--- a/docs/tracks/pt/set-a-price-for-the-sku.md
+++ b/docs/tracks/pt/set-a-price-for-the-sku.md
@@ -16,9 +16,7 @@ trackSlugPT: vtex-getting-started
 
 Qualquer SKU da sua loja precisa de um preço para ser exibido ao cliente final.
 
-<div class="alert alert-warning">
-Mesmo um SKU que será oferecido como brinde precisa ter um preço cadastrado.
-</div>
+>⚠️ Mesmo um SKU que será oferecido como brinde precisa ter um preço cadastrado.
 
 Para cadastrar o preço, siga os passos abaixo.
 1. No módulo __Catalog__, passe o mouse sobre __Cadastro de Produtos__, vá até __Produtos e SKUs__ e clique na opção __Cadastro de Produtos e SKUs__.
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
index 7f5068ca0..51f782f7e 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy-2.md
@@ -36,8 +36,7 @@ Para definir o catálogo de produtos que vai ser enviado ao marketplace, o lojis
 4. Marque a flag __Políticas Comerciais__ para as políticas comerciais escolhidas.
 5. Clique em __Salvar__.
 
-<div class="alert alert-danger">A VTEX não recomenda realizar a gestão de catálogo de produtos para marketplace através de coleções. Esse mecanismo gera muitas complexidades na organização, sendo recomendada a gestão através da flag Políticas Comerciais.
-</div>
+>❗ A VTEX não recomenda realizar a gestão de catálogo de produtos para marketplace através de coleções. Esse mecanismo gera muitas complexidades na organização, sendo recomendada a gestão através da flag Políticas Comerciais.
 
 ## Definindo a logística
 
diff --git a/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md b/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md
index 713eb0c7c..f74d2bf76 100644
--- a/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md
+++ b/docs/tracks/pt/setting-up-a-marketplace-trade-policy.md
@@ -41,8 +41,7 @@ Para definir o catálogo de produtos que vai ser enviado ao marketplace, o lojis
 4. Marque a flag __Políticas Comerciais__ para as políticas comerciais escolhidas.
 5. Clique em __Salvar__.
 
-<div class="alert alert-danger">A VTEX não recomenda realizar a gestão de catálogo de produtos para marketplace através de coleções. Esse mecanismo gera muitas complexidades na organização, sendo recomendada a gestão através da flag Políticas Comerciais.
-</div>
+>❗ A VTEX não recomenda realizar a gestão de catálogo de produtos para marketplace através de coleções. Esse mecanismo gera muitas complexidades na organização, sendo recomendada a gestão através da flag Políticas Comerciais.
 
 ## Definindo a logística
 
diff --git a/docs/tracks/pt/setting-up-a-smart-campaign.md b/docs/tracks/pt/setting-up-a-smart-campaign.md
index f027484e9..f3767bef3 100644
--- a/docs/tracks/pt/setting-up-a-smart-campaign.md
+++ b/docs/tracks/pt/setting-up-a-smart-campaign.md
@@ -30,12 +30,8 @@ Siga este passo-a-passo para configurá-la:
     <br/>&bull; __Definir um retorno do investimento em publicidade (ROAS) desejado:__ ao marcar esta flag você deverá definir qual ROAS a campanha deve perseguir.
     <br/>_`Ex:` se você definir um ROAS 800%, significa que, para cada R$ 1,00 gasto na campanha ela deve converter R$ 8,00._
 
-<div class="alert alert-warning">
-<strong>OBS: não recomendamos configurar um ROAS </strong> logo ao iniciar uma campanha pela primeira vez. Isto porque a campanha precisa de um tempo para aprender a entregar seus produtos nas buscas e isto pode demorar de 4 semanas, segundo o Google. Então, até ela estar madura é recomendável não configurar um ROAS.
-</div>
+>⚠️ **OBS: não recomendamos configurar um ROAS ** logo ao iniciar uma campanha pela primeira vez. Isto porque a campanha precisa de um tempo para aprender a entregar seus produtos nas buscas e isto pode demorar de 4 semanas, segundo o Google. Então, até ela estar madura é recomendável não configurar um ROAS.
 
-<div class="alert alert-warning">
-<strong>OBS2:</strong> recomendamos também que a configuração da campanha <strong>não seja alterada</strong> durante as primeiras 4 semanas. Justamente pelo tempo que a inteligência artificial leva para aprender.
-</div>
+>⚠️ **OBS2:** recomendamos também que a configuração da campanha **não seja alterada** durante as primeiras 4 semanas. Justamente pelo tempo que a inteligência artificial leva para aprender.
 
 *__Pronto!__ Agora você já tem a sua campanha configurada e, dentro de alguns dias, deve começar a ver resultados no dashboard do app.*
diff --git a/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
index 16ce79347..b7e7ad8ef 100644
--- a/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/pt/setting-up-app-linking-for-payments-app-in-instore.md
@@ -36,9 +36,7 @@ Se necessário, o inStore pode enviar informações adicionais. Exemplo com o su
 - `administrativePassword`: string - senha padrão. Por exemplo, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-Para criar qualquer configuração extra, você precisa enviar para a equipe do inStore (instoredevs@vtex.com.br) os extras que a app precisa para concluir a transação. Assim, criaremos um formulário no Pagamentos para que o cliente possa configurar seu adquirente.
-</div>
+>ℹ️ Para criar qualquer configuração extra, você precisa enviar para a equipe do inStore (instoredevs@vtex.com.br) os extras que a app precisa para concluir a transação. Assim, criaremos um formulário no Pagamentos para que o cliente possa configurar seu adquirente.
 
 ## URI de envio e URI de resposta para cada ação
 
@@ -123,9 +121,7 @@ URI final que a app de pagamento receberá para executar a ação de reembolso c
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&autoConfirm=True&sellerName=instoreqa&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class="alert alert-warning">
-<strong>OBSERVAÇÃO:</strong> Nem todos os parâmetros serão utilizados por todos os adquirentes/apps de pagamento. Exemplo: <code>transactionId</code>. Este parâmetro é o ID de uma transação na VTEX que identifica todos os pagamentos de um pedido completo no PCI Gateway da VTEX. Uma transação pode conter vários pagamentos, como quando um pedido é pago com vários cartões de crédito ou débito.
-</div>
+>⚠️ **OBSERVAÇÃO:** Nem todos os parâmetros serão utilizados por todos os adquirentes/apps de pagamento. Exemplo: `transactionId`. Este parâmetro é o ID de uma transação na VTEX que identifica todos os pagamentos de um pedido completo no PCI Gateway da VTEX. Uma transação pode conter vários pagamentos, como quando um pedido é pago com vários cartões de crédito ou débito.
 
 ## Exemplos de URI de resposta para cada ação
 
@@ -185,9 +181,7 @@ Para que a integração funcione, é preciso que o cliente configure no PCI Gate
 
 A integração do AppLinking não inclui outras dependências, uma vez que a comunicação entre o aplicativo inStore e o aplicativo de pagamento acontece com URIs específicas contendo todos os parâmetros de configuração e pagamento necessários para a ação.
 
-<div class="alert alert-warning">
-No Android, toda comunicação deve acontecer com uma nova <code>Intent</code>. Isso significa que você não deve enviar a resposta como um retorno de chamada da <code>Intent</code> inicial. Em vez disso, você deve enviar um novo <code>Intent</code> ao aplicativo inStore com a resposta do anterior.
-</div>
+>⚠️ No Android, toda comunicação deve acontecer com uma nova `Intent`. Isso significa que você não deve enviar a resposta como um retorno de chamada da `Intent` inicial. Em vez disso, você deve enviar um novo `Intent` ao aplicativo inStore com a resposta do anterior.
 
 Para configurar o conector do InStore, você deve seguir os passos abaixo:
 
diff --git a/docs/tracks/pt/setting-up-credit-direct-sale.md b/docs/tracks/pt/setting-up-credit-direct-sale.md
index ca66d1e19..12c2981ad 100644
--- a/docs/tracks/pt/setting-up-credit-direct-sale.md
+++ b/docs/tracks/pt/setting-up-credit-direct-sale.md
@@ -24,6 +24,4 @@ Se você deseja receber pagamentos por cartão de crédito no VTEX Sales App, si
 6. Opcionalmente, você pode configurar condições especiais de pagamento clicando em `Adicionar condição especial`. Leia o artigo [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456) para mais informações.
 7. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Além das configurações acima, é necessário seguir o guia <strong><a href="https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1">Definir meios de pagamento exibidos no VTEX Sales App</a></strong> para que as opções de pagamento sejam exibidas corretamente no aplicativo.</p>
-</div>
+>ℹ️ Além das configurações acima, é necessário seguir o guia **[Definir meios de pagamento exibidos no VTEX Sales App](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1)** para que as opções de pagamento sejam exibidas corretamente no aplicativo.
diff --git a/docs/tracks/pt/setting-up-debit-direct-sale.md b/docs/tracks/pt/setting-up-debit-direct-sale.md
index 82bc5e820..ad61be5b8 100644
--- a/docs/tracks/pt/setting-up-debit-direct-sale.md
+++ b/docs/tracks/pt/setting-up-debit-direct-sale.md
@@ -23,6 +23,4 @@ Se você deseja receber seus pagamentos via cartão de débito no VTEX Sales App
 5. Opcionalmente, você pode configurar condições especiais de pagamento clicando em `Adicionar condição especial`. Leia o artigo [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456) para mais informações.
 6. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Além das configurações acima, é necessário seguir o guia <strong><a href="https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1">Definir meios de pagamento exibidos no VTEX Sales App</a></strong> para que as opções de pagamento sejam exibidas corretamente no aplicativo.</p>
-</div>
+>ℹ️ Além das configurações acima, é necessário seguir o guia **[Definir meios de pagamento exibidos no VTEX Sales App](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1)** para que as opções de pagamento sejam exibidas corretamente no aplicativo.
diff --git a/docs/tracks/pt/setting-up-instore-as-a-pos.md b/docs/tracks/pt/setting-up-instore-as-a-pos.md
index c20af68b4..6ba47ecfe 100644
--- a/docs/tracks/pt/setting-up-instore-as-a-pos.md
+++ b/docs/tracks/pt/setting-up-instore-as-a-pos.md
@@ -22,9 +22,7 @@ Antes de mais nada, verifique os pré-requisitos que sua loja precisa garantir.
 
 ## Implementar o inStore como PDV
 
-<div class="alert alert-info">
-Embora seja possível implementar o inStore como PDV de outras maneiras, neste artigo vamos explicar como fazê-lo usando as features de Contra-franquia e Seller White Label. Isto porque essa é a arquitetura mais recomendada pela VTEX para esse tipo de solução.
-</div>
+>ℹ️ Embora seja possível implementar o inStore como PDV de outras maneiras, neste artigo vamos explicar como fazê-lo usando as features de Contra-franquia e Seller White Label. Isto porque essa é a arquitetura mais recomendada pela VTEX para esse tipo de solução.
 
 Estes são os passos para implementar o inStore como PDV:
 
diff --git a/docs/tracks/pt/setting-up-payments-for-instore.md b/docs/tracks/pt/setting-up-payments-for-instore.md
index 20cfd0b1e..facb2e272 100644
--- a/docs/tracks/pt/setting-up-payments-for-instore.md
+++ b/docs/tracks/pt/setting-up-payments-for-instore.md
@@ -144,10 +144,9 @@ A GSURF é uma empresa que oferece um servidor SiTef via VPN. Isso facilita muit
 
 Ao configurar o conector SiTef, disponível no VTEX Pagamentos, você vai precisar especificar "__GSURF.SSL__" como protocolo para que a app VTEX SiTef envie as transações para o servidor remoto.
 
-<div class="alert alert-danger">
-<strong>IMPORTANTE</strong>: ao utilizar a GSURF como protocolo, certifique-se de que sua rede permite os seguintes acessos:
-<p>
-  <div><strong>Liberações no Firewall (apenas tráfego de saída):</strong></div>
+>❗ **IMPORTANTE**: ao utilizar a GSURF como protocolo, certifique-se de que sua rede permite os seguintes acessos:
+> <p>
+>   <div>**Liberações no Firewall (apenas tráfego de saída):**
   <div><strong>Range de IP’s:</strong> 187.103.176.0/20 189.85.171.160/28 18.231.194.64/26</div>
   <div><strong>Portas:</strong> UDP-443; TCP-443; TCP-55844; TCP-55845</div>
   <div><strong>DNS LOCAL:</strong> UDP-53 (resolução de nomes em gsurfnet.com)</div>
diff --git a/docs/tracks/pt/setting-up-pick-up-points.md b/docs/tracks/pt/setting-up-pick-up-points.md
index d754103e9..56f7c584b 100644
--- a/docs/tracks/pt/setting-up-pick-up-points.md
+++ b/docs/tracks/pt/setting-up-pick-up-points.md
@@ -21,9 +21,7 @@ Pontos de retirada permitem ao cliente final retirar produtos em um local físic
 
 Em qualquer um desses cenários, para que o cliente consiga retirar o produto, você precisa ter cadastrado um ponto de retirada.
 
-<div class="alert alert-info">
-Pontos de retirada não dependem das features de <a href="https://help.vtex.com/tutorial/definicoes-de-conta-franquia-e-seller-white-label">Conta-franquia e Seller White Label</a>. É possível ter pontos de retirada sem contas franquias. Neste guia, entretanto, vamos explicar o uso conjunto dessas features. O motivo é que, para a maior parte dos projetos de omnichannel, essa é a arquitetura recomendada.
-</div>
+>ℹ️ Pontos de retirada não dependem das features de [Conta-franquia e Seller White Label](https://help.vtex.com/tutorial/definicoes-de-conta-franquia-e-seller-white-label). É possível ter pontos de retirada sem contas franquias. Neste guia, entretanto, vamos explicar o uso conjunto dessas features. O motivo é que, para a maior parte dos projetos de omnichannel, essa é a arquitetura recomendada.
 
 ## Criar contas-franquias
 
diff --git a/docs/tracks/pt/setting-up-pix.md b/docs/tracks/pt/setting-up-pix.md
index dffc231fd..428cd6f7c 100644
--- a/docs/tracks/pt/setting-up-pix.md
+++ b/docs/tracks/pt/setting-up-pix.md
@@ -23,6 +23,4 @@ Se você deseja receber pagamentos via Pix no VTEX Sales App, siga os passos aba
 6. Opcionalmente, você pode configurar condições especiais de pagamento clicando em `Adicionar condição especial`. Leia o artigo [Configurar condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456) para mais informações.
 7. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Além das configurações acima, é necessário seguir o guia <strong><a href="https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1">Definir meios de pagamento exibidos no VTEX Sales App</a></strong> para que as opções de pagamento sejam exibidas corretamente no aplicativo.</p>
-</div>
+>ℹ️ Além das configurações acima, é necessário seguir o guia **[Definir meios de pagamento exibidos no VTEX Sales App](https://help.vtex.com/pt/tracks/instore-pagamentos--43B4Nr7uZva5UdwWEt3PEy/jHQQcyX3WKeUFidwSjmY1)** para que as opções de pagamento sejam exibidas corretamente no aplicativo.
diff --git a/docs/tracks/pt/setting-up-the-ads-template-description-in-mercado-livre.md b/docs/tracks/pt/setting-up-the-ads-template-description-in-mercado-livre.md
index 3cea9a9e6..de958e090 100644
--- a/docs/tracks/pt/setting-up-the-ads-template-description-in-mercado-livre.md
+++ b/docs/tracks/pt/setting-up-the-ads-template-description-in-mercado-livre.md
@@ -19,9 +19,7 @@ Na integração com o Mercado Livre, você pode montar a descrição dos seus an
 
 ## Configuração do template
 
-<div class="alert alert-danger">
-O Mercado Livre <strong>não aceita customizações de template em HTML ou CSS</strong> (com exceção da tag &lt;br&gt; para quebras de linha). Não são permitidas as tags de Iframes, Scripts, Forms, Inputs, Meta, Object e Embed.
-</div>
+>❗ O Mercado Livre **não aceita customizações de template em HTML ou CSS** (com exceção da tag &lt;br&gt; para quebras de linha). Não são permitidas as tags de Iframes, Scripts, Forms, Inputs, Meta, Object e Embed.
 
 Para que seu produto fique disponível no Mercado Livre, é necessário configurar o template do anúncio em que ele será exibido. Para fazer isso, siga o passo a passo abaixo:
 
@@ -45,8 +43,6 @@ Caso deseje incluir todos os atributos e valores dos atributos no template, voc
 
 ``{{#each ATRIBUTOS}} {{NOME}} – {{VALOR}} <br> {{/each}}``
 
-<div class="alert alert-info">
-Caso deseje omitir algum atributo no template, você pode fazer isso na <strong>configuração da integração</strong>. Basta preencher o campo <strong>Atributos omitidos no template do produto</strong>, conforme explicado na seção <strong>Configurar o painel do Mercado Livre na VTEX</strong> da etapa anterior.
-</div>
+>ℹ️ Caso deseje omitir algum atributo no template, você pode fazer isso na **configuração da integração**. Basta preencher o campo **Atributos omitidos no template do produto**, conforme explicado na seção **Configurar o painel do Mercado Livre na VTEX** da etapa anterior.
 
 Feito isso, você concluiu a _terceira etapa_. Agora, vamos configurar a logística para as entregas de pedidos feitos no Mercado Livre.
diff --git a/docs/tracks/pt/setting-up-the-app.md b/docs/tracks/pt/setting-up-the-app.md
index d622ab9d3..d8cd8e57d 100644
--- a/docs/tracks/pt/setting-up-the-app.md
+++ b/docs/tracks/pt/setting-up-the-app.md
@@ -52,9 +52,7 @@ Ativar esta opção permite que uma compra seja concluída mesmo que o seu valor
 
 Por exemplo, para uma conta criada com o limite de crédito de R$ 1.000,00 e tolerância de 10%, o cliente poderá realizar um pedido no valor máximo de R$ 1.100,00 utilizando o Customer Credit como meio de pagamento. Caso o cliente deseje utilizar o crédito para pagar um pedido no valor de R$ 1.250,00, o sistema não permitirá a conclusão da compra.
 
-<div class="alert alert-warning">
-Os valores de tolerância são configurados em números decimais, sendo 0 a representação de 0% e 1, a representação de 100%. Exemplo: para utilizar uma tolerância de 5%, o valor a ser configurado é de 0.05.
-</div>
+>⚠️ Os valores de tolerância são configurados em números decimais, sendo 0 a representação de 0% e 1, a representação de 100%. Exemplo: para utilizar uma tolerância de 5%, o valor a ser configurado é de 0.05.
 
 ![CC_Configurações_2_PT](https://images.ctfassets.net/alneenqid6w5/3kjEQ2OblMKqwumNWSFnSt/1fde698cc193dda7e6ed82de51f7c19e/CC_Configura__es_2_PT.JPG)
 
@@ -76,9 +74,7 @@ O cliente poderá acessar esta página no site da sua loja em __Minha Conta > Me
 
 Esta configuração permite você possa inserir instruções relacionadas ao pagamento nos títulos que forem emitidos pelo Customer Credit. Para editar a mensagem a ser exibida no título, insira as informações na caixa de texto e clique em `Atualizar`.
 
-<div class="alert alert-warning">
-A mensagem cadastrada nessa configuração será replicada em todos os títulos emitidos para todas as contas de clientes do Customer Credit. Não é possível configurar uma mensagem única para cada cliente ou título específico.
-</div>
+>⚠️ A mensagem cadastrada nessa configuração será replicada em todos os títulos emitidos para todas as contas de clientes do Customer Credit. Não é possível configurar uma mensagem única para cada cliente ou título específico.
 
 ![CC_Configurações_5_PT](https://images.ctfassets.net/alneenqid6w5/6UkZi827KKQqH8Yk1mmPKj/b2c97be162320e8ed8ef2da3729ecedd/CC_Configura__es_5_PT.JPG)
 
@@ -109,6 +105,4 @@ Para criar as condições de pagamento de títulos do Customer Credit, siga os p
 
 <blockquote><ui>8. Clique em <b>Salvar</b>.</ui>
 
-<div class="alert alert-warning">
-Não é possível configurar taxa de juros para uma condição de pagamento criada com apenas uma única parcela. 
-</div>
+>⚠️ Não é possível configurar taxa de juros para uma condição de pagamento criada com apenas uma única parcela.
diff --git a/docs/tracks/pt/setting-up-the-cappta-acquirer-for-instore.md b/docs/tracks/pt/setting-up-the-cappta-acquirer-for-instore.md
index 7e56012d2..fee82a1b0 100644
--- a/docs/tracks/pt/setting-up-the-cappta-acquirer-for-instore.md
+++ b/docs/tracks/pt/setting-up-the-cappta-acquirer-for-instore.md
@@ -18,17 +18,14 @@ Para permitir transações por meio de máquinas de cartão usando o inStore, vo
 
 A __Cappta__ é um sub-adquirente homologado pelo inStore no Brasil.
 
-<div class="alert alert-warning">
-Se você deseja usar a Cappta em um país diferente ou se deseja usar outro adquirente que não está homologado atualmente, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo <a href="https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod"> Integrar o inStore a um novo adquirente de pagamento</a>.
-</div>
-
-<div class="alert alert-info">
-Atualmente, a Cappta é suportada pelas seguintes plataformas e dispositivos:
-<ol>
-<li>Windows 8 ou superior, com máquina de cartão Ingenico USB</li>
-<li>Android</li>
-</ol>
-</div>
+>⚠️ Se você deseja usar a Cappta em um país diferente ou se deseja usar outro adquirente que não está homologado atualmente, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo [ Integrar o inStore a um novo adquirente de pagamento](https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
+
+>ℹ️ Atualmente, a Cappta é suportada pelas seguintes plataformas e dispositivos:
+>
+> Windows 8 ou superior, com máquina de cartão Ingenico USB
+>
+> Android
+> 
 
 Antes de instalar o aplicativo da Cappta, verifique se você concluiu a etapa anterior de configuração do módulo de Pagamentos. Se tiver concluído essa etapa, siga os passos abaixo para instalar e configurar o adquirente Cappta para o inStore.
 
@@ -49,9 +46,7 @@ Atualmente, a integração funciona para sistemas Android e Windows. Se você es
 - **Android**: o fluxo de configuração do aplicativo é igual a qualquer outro aplicativo instalado em um smartphone ou tablet. Abra o aplicativo e inserir as informações de acesso (CNPJ, POS, Senha). Se você não souber essas informações, entre em contato com a Cappta.
 - **Windows**: Para configurar, execute o arquivo .exe e preencher as informações de acesso (CNPJ, POS, Senha). Se você não souber essas informações, entre em contato com a Cappta.
 
-<div class="alert alert-warning">
-Você deve se certificar de que a opção <strong>web checkout</strong> esteja ativada na sua conta Cappta.
-</div>
+>⚠️ Você deve se certificar de que a opção **web checkout** esteja ativada na sua conta Cappta.
 
 ## Parear a máquina de cartões
 
diff --git a/docs/tracks/pt/setting-up-the-cielo-lio-acquirer-for-instore.md b/docs/tracks/pt/setting-up-the-cielo-lio-acquirer-for-instore.md
index 2e31dd2b3..5b7617829 100644
--- a/docs/tracks/pt/setting-up-the-cielo-lio-acquirer-for-instore.md
+++ b/docs/tracks/pt/setting-up-the-cielo-lio-acquirer-for-instore.md
@@ -18,13 +18,9 @@ Para permitir transações por meio de máquinas de cartão usando o inStore, vo
 
 A __Cielo LIO__ é um adquirente homologado pelo inStore no Brasil.
 
-<div class="alert alert-warning">
-Se você deseja usar a Cielo LIO em um país diferente ou se deseja usar outro adquirente que atualmente não é homologado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo <a href="https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod"> Integrar o inStore a um novo adquirente de pagamento</a>.
-</div>
+>⚠️ Se você deseja usar a Cielo LIO em um país diferente ou se deseja usar outro adquirente que atualmente não é homologado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo [ Integrar o inStore a um novo adquirente de pagamento](https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Atualmente, a Cielo LIO é suportada apenas pelos sistemas Android. Você pode usar a CieloLio V2 ou a CieloLio+.
-</div>
+>ℹ️ Atualmente, a Cielo LIO é suportada apenas pelos sistemas Android. Você pode usar a CieloLio V2 ou a CieloLio+.
 
 Antes de instalar o aplicativo da Cielo LIO, verifique se você concluiu a etapa anterior da configuração do módulo de Pagamentos. Se tiver concluído, siga as etapas abaixo para instalar e configurar o adquirente Cielo LIO para o inStore.
 
diff --git a/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md b/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md
index 45a73f455..eddec90e6 100644
--- a/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md
+++ b/docs/tracks/pt/setting-up-the-logistics-for-mercado-livre.md
@@ -23,9 +23,7 @@ Os modos de envio podem ser de dois tipos:
 - [Mercado Envios 1 (ME1)](#mercado-envios-1-me1)
 - [Mercado Envios (ME2)](#mercado-envios-2-me2)
 
-<div class="alert alert-warning">
-  Independente do modo de envio que sua loja utiliza, é necessário ter um SLA configurado na VTEX, caso contrário os pedidos realizados no Mercado Livre não serão integrados na plataforma da VTEX.
-  </div>
+>⚠️ Independente do modo de envio que sua loja utiliza, é necessário ter um SLA configurado na VTEX, caso contrário os pedidos realizados no Mercado Livre não serão integrados na plataforma da VTEX.
 
 ## Mercado Envios 1 (ME1)
 
@@ -71,9 +69,7 @@ Alguns tipos logísticos possuem a obrigatoriedade de envio de nota fiscal ou co
 - [Flex](#flex)
 - [Mercado Envios Full](#mercado-envios-full)
 
-<div class="alert alert-info">
-Para Segmentar qual tipo de frete utilizado pela loja, é necessário criar um <a href="https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106"><i>atributo de produto</i></a> com o nome <code>meli_shipping_mode</code>, onde estará preenchido se é ME1 ou ME2. 
-</div>
+>ℹ️ Para Segmentar qual tipo de frete utilizado pela loja, é necessário criar um [<i>atributo de produto</i>](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-produto--tutorials_106) com o nome `meli_shipping_mode`, onde estará preenchido se é ME1 ou ME2.
 
 ### Drop Off
 
@@ -113,9 +109,7 @@ A contratação do motoboy é de responsabilidade do seller e o entregador preci
 
 Todas as configurações são feitas dentro da plataforma do Mercado Livre.
 
-<div class="alert alert-info">
-Essa modalidade só está disponível para pedidos feitos na mesma cidade do seller. 
-</div>
+>ℹ️ Essa modalidade só está disponível para pedidos feitos na mesma cidade do seller.
 
 ### Mercado Envios Full
 
@@ -123,9 +117,9 @@ Essa modalidade só está disponível para pedidos feitos na mesma cidade do sel
 
 É possível configurar esse serviço na sua loja através do [cadastro de um estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque) exclusivo para o  Mercado Envios Full. Essa configuração permite acompanhar o nível do estoque uma vez que a quantidade dos produtos dos pedidos feitos através do Mercado Envios Full é atualizada automaticamente conforme a venda é realizada.
 
-<div class="alert alert-danger">
-  Caso o seller escolha o modelo logístico <b>Mercado Envios Full</b>, é necessário seguir a seguinte ordem de configuração: <p><ol><a href="#configurando-modelo-de-envio">Configurar modelo de envio</a> <br><a href="#configurar-o-mercado-envios-full">Configurar o Mercado Envios Full</a></br></ol></p>
-  </div>
+>❗ Caso o seller escolha o modelo logístico **Mercado Envios Full**, é necessário seguir a seguinte ordem de configuração: [Configurar modelo de envio](#configurando-modelo-de-envio) 
+>
+> [Configurar o Mercado Envios Full](#configurar-o-mercado-envios-full)</br>
 
 #### Configurar o Mercado Envios Full
 
@@ -145,9 +139,7 @@ Após definir qual modelo de envio será utilizado para a integração da sua lo
 
 Para criar um campo de produto, siga as instruções do tutorial [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106). 
 
-<div class="alert alert-warning">
-O nome do campo criado deve ser "meli_shipping_mode" e o valor do campo deve ser preenchido como "me1" ou "me2". Caso o nome do campo ou o preenchimento seja diferente, a integração não reconhecerá o atributo.
-</div>
+>⚠️ O nome do campo criado deve ser "meli_shipping_mode" e o valor do campo deve ser preenchido como "me1" ou "me2". Caso o nome do campo ou o preenchimento seja diferente, a integração não reconhecerá o atributo.
 
 ## Consultar as notas fiscais do Mercado Livre por API
 
diff --git a/docs/tracks/pt/setting-up-the-order-summary-printing.md b/docs/tracks/pt/setting-up-the-order-summary-printing.md
index 5faf6eac9..f997f61e6 100644
--- a/docs/tracks/pt/setting-up-the-order-summary-printing.md
+++ b/docs/tracks/pt/setting-up-the-order-summary-printing.md
@@ -25,9 +25,7 @@ São necessárias duas etapas:
 
 ## Ative a opção de configuração do dispositivo
 
-<div class="alert alert-danger">
-A ativação da opção de configuração do dispositivo é feita por meio de uma alteração no arquivo JavaScript <code>checkout-instore-custom.js</code>. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos.
-</div> 
+>❗ A ativação da opção de configuração do dispositivo é feita por meio de uma alteração no arquivo JavaScript `checkout-instore-custom.js`. Essa operação deve ser realizada somente por pessoas com experiência em programação. Alterações incorretas nesse arquivo podem causar erros críticos. 
 
 Primeiro, abra o arquivo `checkout-instore-custom.js`, disponível no Admin da sua conta VTEX (se não sabe como acessar esse arquivo, consulte o tutorial [Como customizar o inStore](https://help.vtex.com/pt/tracks/instore-customizacoes--1z9kBm12oBPyVNDo1ivVc2)).
 
@@ -44,17 +42,13 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-  Não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
 
 Essa alteração fará aparecer no menu principal do inStore a opção __Configurar o dispositivo__, como mostra a imagem abaixo. É por meio dessa opção que vamos configurar a impressora.
 
 ![15. Configurar impressão de resumo do pedido - 2](https://images.ctfassets.net/alneenqid6w5/KxD08Gfiwa8mj6y6KzaKu/7fab9110af8d1337f5646252b8c9387c/15._Configurar_impress__o_de_resumo_do_pedido_-_2.png)
 
-<div class="alert alert-info">
-<strong>Nota:</strong> Há uma opção para imprimir automaticamente o resumo do pedido, assim que o pedido for concluído. Para habilitar, basta adicionar a propriedade <code>printPageAutomatically</code> com o valor <code>true</code> dentro do objeto printingConfig. Veja abaixo como ficaria o trecho de código neste caso.
-</div>
+>ℹ️ **Nota:** Há uma opção para imprimir automaticamente o resumo do pedido, assim que o pedido for concluído. Para habilitar, basta adicionar a propriedade `printPageAutomatically` com o valor `true` dentro do objeto printingConfig. Veja abaixo como ficaria o trecho de código neste caso.
 
 ```json
 window.INSTORE_CONFIG = { 
@@ -66,17 +60,13 @@ window.INSTORE_CONFIG = {
 }
 ```
 
-<div class="alert alert-danger">
-Novamente, não remova nenhuma das outras propriedades presentes no objeto <code>window.INSTORE_CONFIG</code>, para evitar a quebra de outras funcionalidades.
-</div>
+>❗ Novamente, não remova nenhuma das outras propriedades presentes no objeto `window.INSTORE_CONFIG`, para evitar a quebra de outras funcionalidades.
 
 ## Configure o dispositivo de impressora no inStore
 
 Vamos agora ver como configurar uma impressora conectada ao inStore para impressão de resumos de pedido.
 
-<div class="alert alert-warning">
-Antes de mais nada, para conectar uma impressora ao sistema do inStore, é necessário ter um par de credenciais VTEX (AppKey e AppToken) com as devidas permissões de acesso. Recomendamos que o perfil de acesso atrelado a essas credenciais seja o <code>inStore Sales Person</code>. Porém, um perfil com mais poderes, como o Admin Super, também pode ser usado.
-</div>
+>⚠️ Antes de mais nada, para conectar uma impressora ao sistema do inStore, é necessário ter um par de credenciais VTEX (AppKey e AppToken) com as devidas permissões de acesso. Recomendamos que o perfil de acesso atrelado a essas credenciais seja o `inStore Sales Person`. Porém, um perfil com mais poderes, como o Admin Super, também pode ser usado.
 
 Tendo o AppKey e o AppToken em mãos, siga os passos abaixo:
 
diff --git a/docs/tracks/pt/setting-up-the-pagar-me-acquirer-for-instore.md b/docs/tracks/pt/setting-up-the-pagar-me-acquirer-for-instore.md
index d9e40ee37..220548151 100644
--- a/docs/tracks/pt/setting-up-the-pagar-me-acquirer-for-instore.md
+++ b/docs/tracks/pt/setting-up-the-pagar-me-acquirer-for-instore.md
@@ -18,13 +18,9 @@ Para permitir transações por meio de máquinas de cartão usando o inStore, vo
 
 __Pagar.me__ é um sub-adquirente homologado pelo inStore no Brasil.
 
-<div class="alert alert-warning">
-Se você deseja usar o Pagar.me em um país diferente ou se deseja usar outro adquirente que atualmente não é certificado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo <a href="https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrar o inStore a um novo adquirente de pagamento</a>.
-</div>
+>⚠️ Se você deseja usar o Pagar.me em um país diferente ou se deseja usar outro adquirente que atualmente não é certificado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo [Integrar o inStore a um novo adquirente de pagamento](https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Atualmente, o Pagar.me é suportado apenas por sistemas <b>Android</b>, com máquinas de cartão <b>Gertec MOBIPIN</b>.
-</div>
+>ℹ️ Atualmente, o Pagar.me é suportado apenas por sistemas **Android**, com máquinas de cartão **Gertec MOBIPIN**.
 
 Antes de instalar o aplicativo do Pagar.me, verifique se você concluiu a etapa anterior da configuração do módulo de Pagamentos. Se tiver concluído, siga as etapas abaixo para instalar e configurar o adquirente Pagar.me para o inStore.
 
diff --git a/docs/tracks/pt/setting-up-the-sitef-acquirer-for-instore.md b/docs/tracks/pt/setting-up-the-sitef-acquirer-for-instore.md
index 656770583..04db8a3d3 100644
--- a/docs/tracks/pt/setting-up-the-sitef-acquirer-for-instore.md
+++ b/docs/tracks/pt/setting-up-the-sitef-acquirer-for-instore.md
@@ -14,21 +14,15 @@ trackId: 43B4Nr7uZva5UdwWEt3PEy
 trackSlugPT: configurar-o-adquirente-sitef-para-o-instore
 ---
 
-<div class="alert alert-warning">
-É importante ressaltar que a integração com a SiTef é uma solução homologada, mas ainda não testada em larga escala.
-</div>
+>⚠️ É importante ressaltar que a integração com a SiTef é uma solução homologada, mas ainda não testada em larga escala.
 
 Para permitir transações por meio de máquinas de cartão usando o inStore, você precisa de um adquirente ou sub-adquirente que processe seus pagamentos.
 
 A __SiTef__ é um sub-adquirente homologado pelo inStore no Brasil.
 
-<div class="alert alert-warning">
-Se você deseja usar o SiTef em um país diferente ou se deseja usar outro adquirente que atualmente não é certificado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo <a href="https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrar o inStore a um novo adquirente de pagamento</a>.
-</div>
+>⚠️ Se você deseja usar o SiTef em um país diferente ou se deseja usar outro adquirente que atualmente não é certificado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo [Integrar o inStore a um novo adquirente de pagamento](https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Atualmente, a SiTef é suportada por sistemas <b>Android</b> e <b>iOS</b>, com máquinas de cartão Ingenico ou qualquer outra máquina certificada pela SiTef.
-</div>
+>ℹ️ Atualmente, a SiTef é suportada por sistemas **Android** e **iOS**, com máquinas de cartão Ingenico ou qualquer outra máquina certificada pela SiTef.
 
 Antes de instalar o aplicativo da SiTef, certifique-se de que você concluiu a etapa anterior da configuração do módulo de Pagamentos.
 
@@ -55,15 +49,17 @@ A GSURF é uma empresa que oferece um servidor SiTef via VPN. Isso facilita muit
 
 Ao configurar o conector SiTef, disponível no VTEX Payments, você precisará especificar `GSURF.SSL` como o protocolo para o aplicativo VTEX SiTef enviar transações ao servidor remoto.
 
-<div class="alert alert-warning">
-<strong>Importante:</strong>: ao usar o GSURF como um protocolo, verifique se sua rede permite os seguintes acessos:<br>
-<b>Liberações de firewall (somente tráfego de saída):</b>
-<ol>
-<li><b>Intervalo de IPs:</b> 187.103.176.0/20 189.85.171.160/28 18.231.194.64/26</li>
-<li><b>Portas:</b> UDP-443; TCP-443; TCP-55844; TCP-55845</li>
-<li><b>DNS LOCAL: </b> UDP-53 (resolução de nomes em gsurfnet.com)</li>
-</ol>
-</div>
+>⚠️ **Importante:**: ao usar o GSURF como um protocolo, verifique se sua rede permite os seguintes acessos:
+>
+> 
+> **Liberações de firewall (somente tráfego de saída):**
+>
+> **Intervalo de IPs:** 187.103.176.0/20 189.85.171.160/28 18.231.194.64/26
+>
+> **Portas:** UDP-443; TCP-443; TCP-55844; TCP-55845
+>
+> **DNS LOCAL: ** UDP-53 (resolução de nomes em gsurfnet.com)
+> 
 
 ### Servidor local
 
diff --git a/docs/tracks/pt/setting-up-the-stone-acquirer-for-instore.md b/docs/tracks/pt/setting-up-the-stone-acquirer-for-instore.md
index 0118f14d2..b68176b7a 100644
--- a/docs/tracks/pt/setting-up-the-stone-acquirer-for-instore.md
+++ b/docs/tracks/pt/setting-up-the-stone-acquirer-for-instore.md
@@ -18,13 +18,9 @@ Para permitir transações por meio de máquinas de cartão usando o inStore, vo
 
 A __Stone__ é um sub-adquirente homologado pelo inStore no Brasil.
 
-<div class="alert alert-info">
-Se você deseja usar a Stone em um país diferente ou se deseja usar outro adquirente que atualmente não é certificado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo <a href="https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod">Integrar o inStore a um novo adquirente de pagamento</a>.
-</div>
+>ℹ️ Se você deseja usar a Stone em um país diferente ou se deseja usar outro adquirente que atualmente não é certificado, precisará criar a integração com o aplicativo desse adquirente. Para fazer isso, consulte o artigo [Integrar o inStore a um novo adquirente de pagamento](https://help.vtex.com/pt/tracks/instore-integration--6NTqymtXmL9cNy8w1ouAod).
 
-<div class="alert alert-info">
-Atualmente, a Stone é suportada apenas por sistemas <b>Android</b>, com máquinas de cartão <b>Gertec GPOS700</b>. Para outras máquinas de cartão, a Stone recomenda o uso do <a href="https://help.vtex.com/pt/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/1obqdkoH82yFWtaMbwcJKx">Pagar.me</a>.
-</div>
+>ℹ️ Atualmente, a Stone é suportada apenas por sistemas **Android**, com máquinas de cartão **Gertec GPOS700**. Para outras máquinas de cartão, a Stone recomenda o uso do [Pagar.me](https://help.vtex.com/pt/tracks/instore-payments--43B4Nr7uZva5UdwWEt3PEy/1obqdkoH82yFWtaMbwcJKx).
 
 Antes de instalar o aplicativo da Stone, verifique se você concluiu a etapa anterior da configuração do módulo Pagamentos.
 
diff --git a/docs/tracks/pt/settings-on-via-marketplace.md b/docs/tracks/pt/settings-on-via-marketplace.md
index 93c3972b4..e47df3f4c 100644
--- a/docs/tracks/pt/settings-on-via-marketplace.md
+++ b/docs/tracks/pt/settings-on-via-marketplace.md
@@ -47,9 +47,7 @@ No campo Endereço URL, informe a seguinte rota de API, substituindo `{AccountNa
 
 `http://cnovaintegration.vtexcommercestable.com.br/api/viavarejointegration/pub/{{AccountName}}/freight?skuId={{skuId}},{{quantidade}}&zipcode={{cep}}`
 
-<div class="alert alert-info">
-Se o seller utiliza a solução logística <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01543&title=O%20que%20%C3%A9%20Envvias?#:~:text=O%20Envvias%20%C3%A9%20a%20plataforma,ele%20passa%20a%20ser%20automatizado!">Envvias</a>, deverá <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01538&title=Como%20cadastro%20minha%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">cadastrar</a> a URL de frete como <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01071&title=O%20que%20%C3%A9%20uma%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">tabela de contingência</a> ou abrir um chamado na Casas Bahia Marketplace para remover o Envvias e cadastrar a URL de Frete.
-</div>
+>ℹ️ Se o seller utiliza a solução logística <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01543&title=O%20que%20%C3%A9%20Envvias?#:~:text=O%20Envvias%20%C3%A9%20a%20plataforma,ele%20passa%20a%20ser%20automatizado!">Envvias</a>, deverá <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01538&title=Como%20cadastro%20minha%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">cadastrar</a> a URL de frete como <a href= "https://suportemarketplace.viavarejo.com.br/pt-BR/lojista/artigo/?kbid=KA-01071&title=O%20que%20%C3%A9%20uma%20Tabela%20de%20Conting%C3%AAncia?&cat=Gest%C3%A3o%20de%20Fretes">tabela de contingência</a> ou abrir um chamado na Casas Bahia Marketplace para remover o Envvias e cadastrar a URL de Frete.
 
 ## Cadastrar Integradora de Pedidos
 
diff --git a/docs/tracks/pt/settings.md b/docs/tracks/pt/settings.md
index f8b3d5e2d..d16659484 100644
--- a/docs/tracks/pt/settings.md
+++ b/docs/tracks/pt/settings.md
@@ -22,15 +22,11 @@ A VTEX usa dois provedores de CDN nas lojas: **Cloudfront** e **Azion**. É impo
 
 Portanto, se você tem o domínio da loja registrado na plataforma da **Cloudfront** ou **Azion**, remova este registro antes de realizar o apontamento de DNS para a VTEX.
 
-<div class="alert alert-warning">
-Se não for possível remover o registro do domínio da sua loja nas plataformas <strong>Cloudfront</strong> ou <strong>Azion</strong> entre em contato com o <a href="https://help.vtex.com/pt/support">suporte VTEX</a> explicando a situação. Dessa forma, o time da VTEX irá te auxiliar para garantir o bom funcionamento da loja no Go live.
-</div>
+>⚠️ Se não for possível remover o registro do domínio da sua loja nas plataformas **Cloudfront** ou **Azion** entre em contato com o [suporte VTEX](https://help.vtex.com/pt/support) explicando a situação. Dessa forma, o time da VTEX irá te auxiliar para garantir o bom funcionamento da loja no Go live.
 
 ## Configurar registro CAA
 
-<div class="alert alert-warning">
-A configuração de registros de CAA como descrita nesta seção só é necessária caso haja registro de CAA no seu servidor de DNS. Caso contrário, siga para o próximo tópico deste guia.
-</div>
+>⚠️ A configuração de registros de CAA como descrita nesta seção só é necessária caso haja registro de CAA no seu servidor de DNS. Caso contrário, siga para o próximo tópico deste guia.
 
 Registros CAA indicam quais autoridades certificadoras (CAs) estão autorizadas a gerar e renovar certificados que atestam a identidade do seu domínio. A configuração adequada desses registros é necessária para que seja possível gerar os [certificados SSL](https://help.vtex.com/pt/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar--tutorials_1308) e usar a CDN da VTEX.
 
@@ -44,9 +40,7 @@ Isso significa que a autoridade certificadora **Let’s Encrypt** pode emitir ce
 
 Outra alternativa, embora não recomendada, seria não incluir registros CAA no seu servidor DNS - isso sinalizaria que todas autoridades certificadoras estariam autorizadas a emitir e renovar certificados para o seu domínio.
 
-<div class="alert alert-info">
-Esses tipos de entrada podem não estar disponíveis na interface do seu gerenciador de DNS, mas muitas vezes é possível gerenciá-los através de chamados no suporte da ferramenta específica.
-</div>
+>ℹ️ Esses tipos de entrada podem não estar disponíveis na interface do seu gerenciador de DNS, mas muitas vezes é possível gerenciá-los através de chamados no suporte da ferramenta específica.
 
 Para facilitar o trabalho de criar/verificar seus registros CAA, você pode usar o [CAA Record Helper by SSLMate](https://sslmate.com/caa/). O programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) também pode ajudar na verificação dos registros, através do comando `dig domain.com CAA` - um status `SERVFAIL` pode indicar não-conformidade do seu servidor DNS.
 
diff --git a/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md b/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
index a075c1f19..2028c1d5b 100644
--- a/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
+++ b/docs/tracks/pt/sharing-shopping-cart-using-instore-social-selling.md
@@ -41,9 +41,7 @@ Veja o passo a passo ilustrado a seguir.
 
 O vendedor pode enviar o mesmo link para vários clientes, quantas vezes desejar. Cada vez que uma pessoa acessar esse link, um novo carrinho será gerado, exatamente igual ao criado no inStore. Cada carrinho acessado também fica associado à conta do vendedor e, se houver, ao código do vendedor.
 
-<div class="alert alert-info">
-<p>Se o código do vendedor estiver habilitado, será obrigatório preenchê-lo antes de compartilhar o carrinho. Para mais informações sobre o código do vendedor, acesse o guia <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/Rby973h1l9tEM4C1YrzwZ">Customizar o inStore</a> e o guia para desenvolvedores <a href="https://developers.vtex.com/vtex-rest-api/docs/sales-rep-code">Enable the Sales Rep Code</a>.</p>
-</div>
+>ℹ️ Se o código do vendedor estiver habilitado, será obrigatório preenchê-lo antes de compartilhar o carrinho. Para mais informações sobre o código do vendedor, acesse o guia [Customizar o inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/Rby973h1l9tEM4C1YrzwZ) e o guia para desenvolvedores [Enable the Sales Rep Code](https://developers.vtex.com/vtex-rest-api/docs/sales-rep-code).
 
 ## Link para pagamento
 
diff --git a/docs/tracks/pt/shipping-strategies.md b/docs/tracks/pt/shipping-strategies.md
index ae91a4909..e446f3d26 100644
--- a/docs/tracks/pt/shipping-strategies.md
+++ b/docs/tracks/pt/shipping-strategies.md
@@ -78,9 +78,7 @@ Para [estratégias de envio](https://help.vtex.com/pt/tutorial/estrategia-de-env
 6. [Cadastro de geolocalização](https://help.vtex.com/pt/tutorial/registering-geolocation--tutorials_138)
 7. Configuração dos pontos de retirada disponíveis no checkout
 
-<div class="alert alert-warning">
-Confira os passos detalhados no artigo <a href="https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#como-configurar">Como configurar um ponto de retirada.</a>
-</div>
+>⚠️ Confira os passos detalhados no artigo [Como configurar um ponto de retirada.](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#como-configurar)
 
 ## Tempo de envio e feriados
 
@@ -102,9 +100,7 @@ Para cadastrar feriados na plataforma, você pode:
 * Utilizar a seção [Feriados](https://help.vtex.com/pt/tutorial/cadastrar-feriados--2ItOthSEAoyAmcwsuiO6Yk) no Admin VTEX.
 * Utilizar a [API de Feriados](https://developers.vtex.com/vtex-rest-api/reference/holidays).
 
-<div class="alert alert-warning">
-É recomendado que o cadastro de feriados seja feito depois de configurar as <a href="https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3">Estratégias de envio</a>.
-</div>
+>⚠️ É recomendado que o cadastro de feriados seja feito depois de configurar as [Estratégias de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3).
 
 É possível cadastrar horários de entrega para envios agendados de transportadoras e pontos de retirada. A funcionalidade **[Entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)** permite que a loja ofereça janelas de entrega para seus clientes.
 
diff --git a/docs/tracks/pt/specifications-concept-definition.md b/docs/tracks/pt/specifications-concept-definition.md
index d3b6ed752..8df7e634c 100644
--- a/docs/tracks/pt/specifications-concept-definition.md
+++ b/docs/tracks/pt/specifications-concept-definition.md
@@ -16,9 +16,7 @@ trackSlugPT: catalogo-101
 
 Especificações são propriedades adicionais que podem ser cadastradas nos produtos ou SKUs da sua loja. Na VTEX, essas especificações são cadastradas na seção **Categorias** e são chamadas de **Campo**.
 
-<div class="alert alert-warning">
-<p>Na VTEX, as especificações seguem uma lógica de “herança”, ou seja, ao criar uma especificação em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela. Portanto, se for necessário criar uma especificação de produto ou SKU que se aplique a apenas uma categoria, esta deve ser criada no nível dessa categoria.</p>
-</div>
+>⚠️ Na VTEX, as especificações seguem uma lógica de “herança”, ou seja, ao criar uma especificação em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela. Portanto, se for necessário criar uma especificação de produto ou SKU que se aplique a apenas uma categoria, esta deve ser criada no nível dessa categoria.
 
 ## Especificação de Produto
 
@@ -42,7 +40,5 @@ As especificações de SKU teriam os valores de **PP, P, M, G e GG**. Elas poder
 
 Para entender o passo a passo completo para criar especificações de SKU, confira o artigo [Cadastrar especificações ou campos de SKU](https://help.vtex.com/pt/tutorial/cadastrar-especificacoes-ou-campos-de-sku--tutorials_119).
 
-<div class="alert alert-warning">
-Na VTEX, as especificações de SKU são campos obrigatórios para concluir o cadastro de um SKU. Isso significa que, se uma nova especificação for criada dentro de uma categoria, todos os SKUs dentro desta categoria precisam ter esta nova especificação cadastrada. Assim, todos esses SKUs ficarão inativos até que o cadastro desta nova especificação seja realizado nos SKUs da categoria em questão.
-</div>
+>⚠️ Na VTEX, as especificações de SKU são campos obrigatórios para concluir o cadastro de um SKU. Isso significa que, se uma nova especificação for criada dentro de uma categoria, todos os SKUs dentro desta categoria precisam ter esta nova especificação cadastrada. Assim, todos esses SKUs ficarão inativos até que o cadastro desta nova especificação seja realizado nos SKUs da categoria em questão.
 
diff --git a/docs/tracks/pt/subscription-orders.md b/docs/tracks/pt/subscription-orders.md
index 33cc01e0f..b9beea6c0 100644
--- a/docs/tracks/pt/subscription-orders.md
+++ b/docs/tracks/pt/subscription-orders.md
@@ -20,8 +20,6 @@ O cliente indica a periodicidade em que deseja repetir a compra de um determinad
 
 No seu Admin VTEX, em **Pedidos > Assinaturas**, você encontra um [dashboard](https://help.vtex.com/pt/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x#dashboard) para o acompanhamento e supervisão das Assinaturas existentes e uma aba para [configurações](https://help.vtex.com/pt/tutorial/como-gerenciar-assinaturas--6Jk50FPbv6iuz1OsFypv8x#configuracoes) de Assinaturas. A assinatura só aparece na listagem depois que o primeiro pagamento do cliente é aprovado.
 
-<div class="alert alert-warning">
-Atualmente, apenas pedidos feitos com <strong>cartão de crédito</strong> permitem assinaturas. Ative todas as condições de cartão de crédito já definidas para <a href="https://help.vtex.com/pt/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW">compras recorrentes</a> nas suas formas de pagamento. Além disso, é necessário que o seu conector de pagamentos aceite pagamento recorrente. Entre em contato com o adquirente da sua loja e certifique-se que ele aceita transações de compras recorrentes oriundas de cartões tokenizados (sem CVV).
-</div>
+>⚠️ Atualmente, apenas pedidos feitos com **cartão de crédito** permitem assinaturas. Ative todas as condições de cartão de crédito já definidas para [compras recorrentes](https://help.vtex.com/pt/tutorial/configurar-recorrencia-em-condicoes-de-pagamento--6EGuoAytLqU2CqUuaI2GUW) nas suas formas de pagamento. Além disso, é necessário que o seu conector de pagamentos aceite pagamento recorrente. Entre em contato com o adquirente da sua loja e certifique-se que ele aceita transações de compras recorrentes oriundas de cartões tokenizados (sem CVV).
 
 Veja o passo a passo no artigo [Como configurar Assinaturas na sua loja](https://help.vtex.com/pt/tutorial/como-configurar-assinaturas--1FA9dfE7vJqxBna9Nft5Sj).
diff --git a/docs/tracks/pt/teste-1.md b/docs/tracks/pt/teste-1.md
index dc3a4dc0c..69407defa 100644
--- a/docs/tracks/pt/teste-1.md
+++ b/docs/tracks/pt/teste-1.md
@@ -32,9 +32,7 @@ O **Guia de onboarding** é composto por três trilhas, são elas:
 - [Próximos passos após o go-live](https://help.vtex.com/pt/tracks/proximos-passos-apos-o-go-live--3J7WFZyvTcoiwkcIVFVhIS)
 - [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy)
 
-<div class="alert alert-info">
-As trilhas tem conteúdos complementares, mas são independentes entre si. Isso significa que você pode explorar o conteúdo com liberdade, sem precisar seguir uma sequência.
-</div>
+>ℹ️ As trilhas tem conteúdos complementares, mas são independentes entre si. Isso significa que você pode explorar o conteúdo com liberdade, sem precisar seguir uma sequência.
 
 Nosso objetivo é que clientes, parceiros e todo o ecossistema VTEX se beneficiem do **Guia de onboarding**. E para manter a relevância do material para diferentes negócios, consideramos uma jornada bastante abrangente. 
 Veja a seguir uma [introdução](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3QfoDZWg9YWl8lwS9MVrnU) do que você encontrará no guia.
diff --git a/docs/tracks/pt/the-reservation.md b/docs/tracks/pt/the-reservation.md
index defb5ed73..adc7e4839 100644
--- a/docs/tracks/pt/the-reservation.md
+++ b/docs/tracks/pt/the-reservation.md
@@ -22,9 +22,7 @@ A reserva conecta o módulo de logística ao módulo de pedidos. Ela impede que
 
 ## Como a reserva funciona
 
-<div class="alert alert-warning">
-Produtos apenas inseridos no carrinho <strong>não</strong> geram reserva ou prioridade. Uma reserva é feita apenas se um pedido for <strong>finalizado</strong>.
-</div>  
+>⚠️ Produtos apenas inseridos no carrinho **não** geram reserva ou prioridade. Uma reserva é feita apenas se um pedido for **finalizado**.  
 
 
 Este é o fluxo da reserva na VTEX: 
@@ -37,6 +35,4 @@ Este é o fluxo da reserva na VTEX:
 
 ![reservation pt](https://images.ctfassets.net/alneenqid6w5/7nDqT6kSvWTESRqZLzZutZ/9009856b729712a613d4d6c36612fd9a/reservation_pt.png)
 
-<div class="alert alert-warning">
-A VTEX não desconta automaticamente os itens dos estoques, mesmo depois que eles passam para o status <code>Reserva reconhecida</code>. Os itens comprados continuarão nesse status até que o ERP ou o lojista realizem a baixa no estoque.
-</div>
+>⚠️ A VTEX não desconta automaticamente os itens dos estoques, mesmo depois que eles passam para o status `Reserva reconhecida`. Os itens comprados continuarão nesse status até que o ERP ou o lojista realizem a baixa no estoque.
diff --git a/docs/tracks/pt/tiktok-for-business.md b/docs/tracks/pt/tiktok-for-business.md
index b955ca94f..6ea1983ba 100644
--- a/docs/tracks/pt/tiktok-for-business.md
+++ b/docs/tracks/pt/tiktok-for-business.md
@@ -14,9 +14,7 @@ trackId: 1r0yJSO11nrer1YVu3WTFd
 trackSlugPT: integracao-com-o-tiktok
 ---
 
-<div class="alert alert-danger">
-  <p>A integração com o TikTok está disponível apenas para lojas no <strong>Brasil</strong>.</p>
-</div>
+>❗ A integração com o TikTok está disponível apenas para lojas no **Brasil**.
 
 O [TikTok](https://www.tiktok.com/pt-BR/) é uma plataforma de entretenimento para criar e compartilhar vídeos curtos que oferece ferramentas de marketing para empresas. Uma das principais ferramentas disponíveis nesse contexto é o TikTok Ads Manager, que contém recursos avançados para lançar campanhas e gerenciar publicidade no TikTok.
 
diff --git a/docs/tracks/pt/unified-commerce.md b/docs/tracks/pt/unified-commerce.md
index 705c4005d..d2ee5cab2 100644
--- a/docs/tracks/pt/unified-commerce.md
+++ b/docs/tracks/pt/unified-commerce.md
@@ -33,9 +33,7 @@ Outras vantagens em operar com contas franquia estão listadas a seguir:
 - [Regionalização de sellers](https://help.vtex.com/pt/tutorial/configurar-a-regionalizacao-de-sellers--32t6wLpQCEnumoh8TjT5fw) (preço e inventário).
 - Aumento na performance operacional por meio da utilização de requisições simultâneas no checkout de cada loja. Em uma conta padrão, onde a [estratégia de envio](https://help.vtex.com/pt/tracks/trilha-geral-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#configuracoes-obrigatorias-em-logistica) é cadastrada na conta principal, as requisições são processadas em fila, gerando um possível acúmulo de requisições e aumento de interrupções (timeout). Sempre que a interrupção ocorre, uma mensagem de erro aparece no checkout e o cliente precisa clicar em F5 ou no botão de atualizar para prosseguir com a compra. Este comportamento gera impacto negativo na experiência do cliente e diminui a taxa de conversão da loja.
 
-<div class="alert alert-warning">
-  <p>As <a href="https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">contas franquias</a> atuam como um <a href="https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a> da conta principal. Quando um cliente adiciona produtos no carrinho de compras e simula o frete no site da conta principal, o <a href="https://help.vtex.com/pt/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo de seleção de sellers white label</a> define automaticamente qual conta franquia será responsável pelo <a href="https://help.vtex.com/pt/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP">fulfillment</a> do pedido. Caso ocorra o cenário onde um ou mais produtos do carrinho não estejam disponíveis na conta franquia selecionada, o sistema definirá um outra conta disponível para realizar o envio dos produtos faltantes, permitindo que ocorra mais de uma entrega para o mesmo pedido. Este processo acontece de forma interna na plataforma, sem que o cliente tenha conhecimento dos sellers envolvidos.</p>
-</div>
+>⚠️ As [contas franquias](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) atuam como um [seller white label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) da conta principal. Quando um cliente adiciona produtos no carrinho de compras e simula o frete no site da conta principal, o [algoritmo de seleção de sellers white label](https://help.vtex.com/pt/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) define automaticamente qual conta franquia será responsável pelo [fulfillment](https://help.vtex.com/pt/tutorial/fulfillment-logistica-vtex--53udnvI5eBy8DKo8FOjMoP) do pedido. Caso ocorra o cenário onde um ou mais produtos do carrinho não estejam disponíveis na conta franquia selecionada, o sistema definirá um outra conta disponível para realizar o envio dos produtos faltantes, permitindo que ocorra mais de uma entrega para o mesmo pedido. Este processo acontece de forma interna na plataforma, sem que o cliente tenha conhecimento dos sellers envolvidos.
 
 ## Ship from store
 
diff --git a/docs/tracks/pt/untitled-entry-2018-03-20-at-04-04-56.md b/docs/tracks/pt/untitled-entry-2018-03-20-at-04-04-56.md
index 63cf47ed8..c0daf9a8e 100644
--- a/docs/tracks/pt/untitled-entry-2018-03-20-at-04-04-56.md
+++ b/docs/tracks/pt/untitled-entry-2018-03-20-at-04-04-56.md
@@ -26,8 +26,6 @@ A integração envia o preço final de acordo com a simulação de fulfillment.
 </br>
 Os preços são enviados sempre que o produto é indexado. Ao alterar o preço de um SKU, a indexação ocorrerá automaticamente. No entanto, para preços com validade, quando a data expira o sistema não ativa a reindexação. Desta forma, o preço base só será enviado na próxima indexação do produto (seja por conta de alguma alteração no cadastro do produto, seja por atualização de estoque, ou até por uma reindexação agendada mesmo, etc...).
 
-<div class="alert alert-warning">
-OBS: como a forma de pagamento é feita no marketplace, as regras de pagamento são determinadas por ele. Por conta disto, não conseguimos enviar preços diferenciados em função da forma de pagamento.
-</br>
-<em>Ex: se na VTEX existem juros configurados para pagamentos parcelados, o preço enviado continuará sendo o que a simulação de fulfillment retorna.</em>
-</div>
+>⚠️ OBS: como a forma de pagamento é feita no marketplace, as regras de pagamento são determinadas por ele. Por conta disto, não conseguimos enviar preços diferenciados em função da forma de pagamento.
+> </br>
+> *Ex: se na VTEX existem juros configurados para pagamentos parcelados, o preço enviado continuará sendo o que a simulação de fulfillment retorna.*
diff --git a/docs/tracks/pt/vtex-modules-i.md b/docs/tracks/pt/vtex-modules-i.md
index 96153b5a5..de91ba7d6 100644
--- a/docs/tracks/pt/vtex-modules-i.md
+++ b/docs/tracks/pt/vtex-modules-i.md
@@ -21,9 +21,7 @@ A plataforma VTEX se organiza em diferentes módulos, cada um deles responsável
 - [Promoções](#promocoes)
 - [Logística](#logistica)
 
-<div class="alert alert-info">
-O artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ">Módulos da VTEX II</a> apresenta os módulos <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagamentos">Pagamentos</a>, <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos">Pedidos</a>, e <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout">Checkout</a>.
-</div>
+>ℹ️ O artigo [Módulos da VTEX II](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ) apresenta os módulos [Pagamentos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pagamentos), [Pedidos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#pedidos), e [Checkout](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/3MYcZaojb5HSUg6ufm6GxQ#checkout).
 
 ## Catálogo
 
@@ -63,9 +61,7 @@ A tabela a seguir apresenta as principais configurações de Catálogo da loja,
 
 <br>
 
-<div class="alert alert-warning">
-Para saber como importar produtos de um sistema ERP (Enterprise Resource Planning) ou PIM (Product Information Manager) para a plataforma VTEX, veja o artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
-</div>
+>⚠️ Para saber como importar produtos de um sistema ERP (Enterprise Resource Planning) ou PIM (Product Information Manager) para a plataforma VTEX, veja o artigo [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu).
 
 #### Árvore de categorias
 
@@ -79,9 +75,7 @@ Antes de importar o catálogo da loja para a VTEX, recomendamos começar a traba
 
 ![catalog_arquitecture_table_PT](https://images.ctfassets.net/alneenqid6w5/6Vg5pVKydPdMipVEqj1Spq/d28bf46e6d7b444f994f986068a3b49f/catalog_arquitecture_table_PT.png)
 
-<div class="alert alert-info">
-Informações sobre como importar especificações para back-office podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
-</div>
+>ℹ️ Informações sobre como importar especificações para back-office podem ser encontradas no artigo [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu).
 
 #### Marcas
 
@@ -174,9 +168,7 @@ Há uma diferença entre as tabelas de preços criadas para [políticas comercia
 
 As tabelas de preços não associadas a políticas comerciais podem ser usadas em contextos como __promoções__ e __clusters de clientes__. As tabelas criadas para políticas comerciais só podem ser associadas à própria política comercial. Assim, a tabela de preço associada a uma política comercial informa o preço dos SKUs para esta política e não pode ser associada a outros contextos.
 
-<div class="alert alert-warning">
-Os conceitos de <b>tabela de preços</b> e <a href="LINK">política comercial</a> são diferentes. A política comercial é o contexto ao qual uma tabela de preços é associada.
-</div>
+>⚠️ Os conceitos de **tabela de preços** e [política comercial](LINK) são diferentes. A política comercial é o contexto ao qual uma tabela de preços é associada.
 
 Ao configurar uma política comercial, é essencial [especificar a moeda que será utilizada na loja](https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE). A criação de políticas comerciais distintas, cada uma associada a uma moeda diferente, possibilita à loja exibir preços em diversas moedas para os clientes. 
 
@@ -227,9 +219,7 @@ Mais informações sobre possibilidades de aplicação de promoções podem ser
 
 É possível criar cupons de desconto pelo [Admin VTEX](https://help.vtex.com/pt/tutorial/criar-cupom-beta--7lMk3MmhNp2IEccyGApxU) ou por [API](https://developers.vtex.com/docs/guides/creating-and-managing-coupons-with-promotions-api). Para ser utilizado, um cupom precisa estar vinculado a pelo menos uma promoção. 
 
-<div class="alert alert-warning">
-Há uma quantidade limitada de cupons ativos. A reutilização de cupons é altamente recomendada, uma vez que um grande número de cupons pode comprometer o desempenho do módulo de Promoções.
-</div>
+>⚠️ Há uma quantidade limitada de cupons ativos. A reutilização de cupons é altamente recomendada, uma vez que um grande número de cupons pode comprometer o desempenho do módulo de Promoções.
 
 ### Criar promoções de campanha
 
@@ -316,9 +306,7 @@ A [transportadora](https://help.vtex.com/pt/tutorial/o-que-e-uma-transportadora-
 
 O [inventário](https://help.vtex.com/pt/tutorial/gerenciar-inventario--tutorials_139) da loja corresponde aos itens armazenados que estão disponíveis para a venda. O estoque é a identificação do local físico de armazenamento, enquanto o inventário é o conjunto de SKUs em estoque que estão prontos para serem vendidos.
 
-<div class="alert alert-danger">
-Na VTEX, a atualização de inventário após a venda dos itens precisa ser controlada pela própria loja. Desta forma, após a venda, o lojista garante o devido controle da quantidade de itens restantes e de operações de fatura com ERP. Informações sobre importação de inventário via back-office podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a>.
-</div>
+>❗ Na VTEX, a atualização de inventário após a venda dos itens precisa ser controlada pela própria loja. Desta forma, após a venda, o lojista garante o devido controle da quantidade de itens restantes e de operações de fatura com ERP. Informações sobre importação de inventário via back-office podem ser encontradas no artigo [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu).
 
 ### Lead time
 
diff --git a/docs/tracks/pt/vtex-modules-ii.md b/docs/tracks/pt/vtex-modules-ii.md
index b14f3dea4..264c81076 100644
--- a/docs/tracks/pt/vtex-modules-ii.md
+++ b/docs/tracks/pt/vtex-modules-ii.md
@@ -28,9 +28,7 @@ O módulo de [Pagamentos](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm
 
 Para processar e receber os pagamentos das compras realizadas em uma loja VTEX, é preciso contratar os serviços de um ou mais provedores de pagamento. Este contrato é realizado diretamente entre o lojista e o respectivo provedor, não havendo mediação ou participação da VTEX. Para verificar quais provedores estão disponíveis na VTEX em cada país, basta acessar a [Lista de provedores de pagamento](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).
 
-<div class="alert alert-warning">
-É recomendável utilizar mais de um provedor de pagamento na loja para prover uma boa experiência ao cliente por meio diversos tipos de meios e condições de pagamento, e ao mesmo tempo, operar com diferentes taxas e custos, melhorando o desempenho do negócio.
-</div>
+>⚠️ É recomendável utilizar mais de um provedor de pagamento na loja para prover uma boa experiência ao cliente por meio diversos tipos de meios e condições de pagamento, e ao mesmo tempo, operar com diferentes taxas e custos, melhorando o desempenho do negócio.
 
 As configurações de pagamento descritas nesta trilha podem ser realizadas a qualquer momento durante o processo de onboarding. Entretanto, para que a loja possa realizar qualquer tipo de transação de pagamento, é necessário que os módulos de [Catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo), [Preços](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#precos) e [Logística](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#logistica) tenham sido previamente configurados.
 
@@ -192,9 +190,7 @@ Para localizar o registro de uma compra no Admin VTEX, além de poder [filtrar p
 - Email do cliente
 - Documento do cliente 
 
-<div class="alert alert-warning">
-Só é possível acessar informações de pedidos criados nos últimos dois anos, sendo o mesmo período válido para os clientes acessarem seus pedidos pelo <a href="">Minha Conta</a>.
-</div>
+>⚠️ Só é possível acessar informações de pedidos criados nos últimos dois anos, sendo o mesmo período válido para os clientes acessarem seus pedidos pelo [Minha Conta]().
 
 #### Emails transacionais
 
@@ -270,9 +266,7 @@ Mais informações em [Configurar carrinho abandonado](https://help.vtex.com/pt/
 
 Na plataforma VTEX, as lojas têm a possibilidade de ajustar manualmente o preço de um item (SKU) presente no carrinho do Checkout. Esta funcionalidade pode ser usada para aplicar descontos especiais, corrigir erros de preço, criar ofertas personalizadas, resolver reclamações relacionadas a preços ou ajustar custos de envio.
 
-<div class="alert alert-warning">
-Apenas usuários com <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfis de acesso</a> e permissões devidamente registrados no Admin VTEX podem realizar esta modificação.
-</div>
+>⚠️ Apenas usuários com [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) e permissões devidamente registrados no Admin VTEX podem realizar esta modificação.
 
 Mais informações em [Modificar o preço de um item no carrinho de compras](https://help.vtex.com/pt/tutorial/modificar-o-preco-de-um-item-no-carrinho-de-compras--7Cd37aCAmtL1qmoZJJvjNf).
 
diff --git a/docs/tracks/pt/vtex-platform-settings.md b/docs/tracks/pt/vtex-platform-settings.md
index f94604f5d..3ce743300 100644
--- a/docs/tracks/pt/vtex-platform-settings.md
+++ b/docs/tracks/pt/vtex-platform-settings.md
@@ -51,14 +51,10 @@ Se for do seu interesse utilizar a mesma Estratégia de Envio definida para sua
 
 Caso você queira conferir se as configurações foram realizadas corretamente, você pode fazer uma [simulação de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144). O Simulador de envio é uma ferramenta que possibilita checar as condições de entrega do produto sem de fato abrir um pedido.
 
-<div class="alert alert-info">
-A Amazon seleciona o frete conforme a <a href="https://help.vtex.com/pt/tutorial/como-montar-a-planilha-de-frete--tutorials_127">planilha</a> exportada pelo lojista. Por isso, é importante que os dados da planilha <a href="https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034">exportada</a> correspondam aos da planilha cadastrada na VTEX, para reduzir a chance de erros de divergência.
-</div>
+>ℹ️ A Amazon seleciona o frete conforme a [planilha](https://help.vtex.com/pt/tutorial/como-montar-a-planilha-de-frete--tutorials_127) exportada pelo lojista. Por isso, é importante que os dados da planilha [exportada](https://help.vtex.com/pt/tutorial/importando-e-exportando-planilha-de-estoque--tutorials_2034) correspondam aos da planilha cadastrada na VTEX, para reduzir a chance de erros de divergência.
 
 ### Tempo de custo
 
 Na Amazon existe o campo *"fulfillment latency"*, que é usado para configurar o tempo de preparo da entrega de determinado produto. Para utilizá-lo na configuração com a Amazon, é necessário preencher o campo **Tempo de Custo** no [cadastro da doca](https://help.vtex.com/pt/tutorial/como-cadastrar-doca) associada à [política comercial](#definicao-da-politica-comercial-na-amazon) usada para a Amazon. Caso esse campo não esteja preenchido, a Amazon usará o valor padrão deles (2 dias).
 
-<div class="alert alert-warning">
-O preenchimento desse campo é fundamental, porque caso sua loja esteja atrasando na entrega do pedido, sua conta pode ser bloqueada. 
-</div>
+>⚠️ O preenchimento desse campo é fundamental, porque caso sua loja esteja atrasando na entrega do pedido, sua conta pode ser bloqueada.
diff --git a/docs/tracks/pt/what-are-clustered-payment-conditions.md b/docs/tracks/pt/what-are-clustered-payment-conditions.md
index fde9a6630..8563dda78 100644
--- a/docs/tracks/pt/what-are-clustered-payment-conditions.md
+++ b/docs/tracks/pt/what-are-clustered-payment-conditions.md
@@ -16,8 +16,6 @@ trackSlugPT: condicoes-de-pagamento-clusterizadas
 
 A Clustered Payments Conditions é uma nova funcionalidade do [Customer Credit](https://help.vtex.com/pt/announcements/de-credito-aos-seus-melhores-clientes-com-o-customer-credit--6M2V1Oc1UIaGSM6QayWkmq?&utm_source=autocomplete "Customer Credit") que permite ao lojista definir que uma determinada regra de prazo e parcelamento será válida especificamente para um ou mais consumidores de sua confiança. Esse filtro é feito por meio de clusters - uma forma de segmentação.
 
-<div class="alert alert-warning">
-Atualmente, esta funcionalidade encontra-se em Closed Beta (estágio de testes) e não está disponível para instalação em novas lojas.            
-</div>            
+>⚠️ Atualmente, esta funcionalidade encontra-se em Closed Beta (estágio de testes) e não está disponível para instalação em novas lojas.            
 
 A personalização das regras de prazo e parcelamento acontece por meio de nosso banco de dados - o [Master Data](https://help.vtex.com/pt/tutorial/what-is-master-data--4otjBnR27u4WUIciQsmkAw "Master Data"). 
diff --git a/docs/tracks/pt/what-are-permissions-and-access-profiles.md b/docs/tracks/pt/what-are-permissions-and-access-profiles.md
index dea6bce34..9b1069730 100644
--- a/docs/tracks/pt/what-are-permissions-and-access-profiles.md
+++ b/docs/tracks/pt/what-are-permissions-and-access-profiles.md
@@ -20,7 +20,5 @@ Os perfis de acesso definem quais funcionalidades o usuário poderá visualizar
 
 Você pode criar novos perfis e definir as permissões para eles. Ou então pode usar os [perfis predefinidos](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#descricao-dos-perfis-predefinidos) que, por padrão, já estão configurados na plataforma. Os perfis predefinidos costumam atender à grande maioria das necessidades de todas as lojas.
 
-<div class="alert alert-danger">
-A má gestão dos perfis de acesso da sua loja pode trazer graves consequências para o seu negócio. Veja as melhores práticas no artigo: <a href="https://help.vtex.com/pt/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM">Métodos de segurança para criação de perfis de usuários em uma loja</a>.
-</div>
+>❗ A má gestão dos perfis de acesso da sua loja pode trazer graves consequências para o seu negócio. Veja as melhores práticas no artigo: [Métodos de segurança para criação de perfis de usuários em uma loja](https://help.vtex.com/pt/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM).
 
diff --git a/docs/tracks/pt/what-is-conversational-commerce-vtex.md b/docs/tracks/pt/what-is-conversational-commerce-vtex.md
index a29f83a0c..23a5162d4 100644
--- a/docs/tracks/pt/what-is-conversational-commerce-vtex.md
+++ b/docs/tracks/pt/what-is-conversational-commerce-vtex.md
@@ -22,9 +22,7 @@ Para utilização do suporte humano, o Message-to-Order já está pré integrado
 
 ![chatbot-PT](https://images.ctfassets.net/alneenqid6w5/5w2PKYYmrGDYuiP0t4jQXU/2e05dae6dd79cd1352cade3533624f68/Captura_de_Tela_2022-07-28_a__s_11.13.08.png)
 
-<div class="alert alert-info">
-O Message-to-Order é um produto em fase de início de operação com escopo reduzido (Alpha). Portanto o perfil de cliente e mercados que abrange ainda é limitado a BR e LATAM e às capacidades disponibilizadas pelo cliente nesse estágio.
-</div>
+>ℹ️ O Message-to-Order é um produto em fase de início de operação com escopo reduzido (Alpha). Portanto o perfil de cliente e mercados que abrange ainda é limitado a BR e LATAM e às capacidades disponibilizadas pelo cliente nesse estágio.
 
 Para adicionar o Conversational Commerce VTEX à sua loja, são necessárias duas configurações:
 
diff --git a/docs/tracks/pt/what-is-the-payment-split.md b/docs/tracks/pt/what-is-the-payment-split.md
index 500a1cda9..de3ba1401 100644
--- a/docs/tracks/pt/what-is-the-payment-split.md
+++ b/docs/tracks/pt/what-is-the-payment-split.md
@@ -24,9 +24,7 @@ Entretanto, o montante pode, ou não, ser igualmente dividido entre os recebedor
 
 Nesta track, explicaremos como a solução funciona, incluindo alguns conceitos importantes para essa dinâmica, e como configurá-la. 
 
-<div class="alert alert-info">
-Se você já conhece a solução, vá para etapa  Configurar split de pagamento.
-</div>
+>ℹ️ Se você já conhece a solução, vá para etapa  Configurar split de pagamento.
 
 ## Recebível 
 
@@ -42,19 +40,15 @@ Atualmente, o split suporta os seguintes meios de pagamento:
 - Cartão de Débito
 - Boleto bancário
 
-<div class="alert alert-info">
-No caso do cartão de crédito, o split suporta pagamentos realizados com dois cartões diferentes.
-</div>
+>ℹ️ No caso do cartão de crédito, o split suporta pagamentos realizados com dois cartões diferentes.
 
 ## Transação 
 
 Quando um comprador finaliza uma compra e efetua o pagamento, esse valor não necessariamente será capturado e enviado para o lojista no mesmo dia. 
 
-<div class="alert alert-info">
-Existem exceções, como o Pix - Sistema de Pagamentos Instantâneos do Banco Central - em que a transação é efetuada em segundos. 
-
-Porém, a maioria dos meios de pagamento oferecido nos Brasil hoje não envia o pagamento automaticamente ao lojista.
-</div>
+>ℹ️ Existem exceções, como o Pix - Sistema de Pagamentos Instantâneos do Banco Central - em que a transação é efetuada em segundos. 
+>
+> Porém, a maioria dos meios de pagamento oferecido nos Brasil hoje não envia o pagamento automaticamente ao lojista.
 
 Na VTEX, o comportamento padrão é que os dados da compra sejam reunidos em uma transação. Essa transação, por sua vez, passará por várias etapas de validação para garantir que todos esses dados são legítimos. Esse processo de verificação é o que chamamos de [fluxo da transação](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/1xjzgJZvqwaI1rfxLMCC3Y "fluxo da transação"). 
 
diff --git a/docs/tracks/pt/what-is-vtex-payment.md b/docs/tracks/pt/what-is-vtex-payment.md
index 5b076f701..f8d5b9d5b 100644
--- a/docs/tracks/pt/what-is-vtex-payment.md
+++ b/docs/tracks/pt/what-is-vtex-payment.md
@@ -66,11 +66,7 @@ Siga o passo a passo abaixo para realizar o preenchimento destes campos:
 
 O VTEX Payment permite configurar cartão de crédito e boleto bancário como formas de pagamento. Para maiores informações, veja como [configurar condições de pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento--tutorials_455?&utm_source=autocomplete).
 
-<div class="alert alert-warning">
-No VTEX Payment, o prazo padrão para vencimento de boletos bancários é de 3 dias. Caso deseje alterar este prazo, entre em contato com o atendimento da VTEX.
-</div>
+>⚠️ No VTEX Payment, o prazo padrão para vencimento de boletos bancários é de 3 dias. Caso deseje alterar este prazo, entre em contato com o atendimento da VTEX.
 
-<div class="alert alert-warning">
-  Caso o VTEX Payment não esteja disponível no Admin da sua loja, entre em contato com a VTEX para que o seu perfil de acesso seja criado e o conector disponibilizado para instalação e configuração.
-  </div>
+>⚠️ Caso o VTEX Payment não esteja disponível no Admin da sua loja, entre em contato com a VTEX para que o seu perfil de acesso seja criado e o conector disponibilizado para instalação e configuração.
 
diff --git a/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md b/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md
index 109f6fa1c..d18a1dd9b 100644
--- a/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md
+++ b/docs/tracks/pt/what-to-configure-in-wish-prior-to-the-integration.md
@@ -14,7 +14,7 @@ trackId: 50hbG4bzhSIhjz1lzqI1g4
 trackSlugPT: integracao-com-a-wish
 ---
 
-<div class="alert alert-warning">Atualmente, o app da Wish está disponível somente para lojas brasileiras.</div>
+>⚠️ Atualmente, o app da Wish está disponível somente para lojas brasileiras.
 
 É necessário preparar o seu ambiente na Wish antes de iniciar a integração na VTEX. Os principais passos são:
 
diff --git a/docs/tracks/pt/what-to-configure-with-vtex-before-starting-the-integration.md b/docs/tracks/pt/what-to-configure-with-vtex-before-starting-the-integration.md
index 8fc1cbd04..7cc83b89a 100644
--- a/docs/tracks/pt/what-to-configure-with-vtex-before-starting-the-integration.md
+++ b/docs/tracks/pt/what-to-configure-with-vtex-before-starting-the-integration.md
@@ -20,12 +20,11 @@ Para garantir o correto funcionamento da integração, é necessário previament
 
 É necessário definir qual política comercial será usada para integrar seus produtos com a Wish. Esta definição implicará em quatro aspectos principais: sortimento de produtos, estoque, preço e moeda. Ou seja, a disponibilidade e os preços dos seus produtos em determinado canal de vendas estarão completamente baseados na política comercial que você escolher. [Clique aqui para entender com mais detalhes como funciona a política comercial](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace?locale=pt).
 
-<div class="alert alert-info">
-  OBS: a Wish exige que os preços do produto e de frete sejam enviados em dólar (USD). No entanto, ela cria os pedidos com o valor já convertido em reais (R$) para facilitar a emissão da nota fiscal.
-
-Isto significa que a integração deve enviar preços em dólar e aceitar pedidos em reais. Dessa maneira, a arquitetura usa apenas Real (R$) e faz a conversão na integração.
-
-Portanto, <strong>a política comercial para Wish deve ser em reais (R$)</strong> e todo fluxo de conversão será melhor detalhado no [passo 5](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4/6EYEy1jRiAj465WOnhiczD).</div>
+>ℹ️ OBS: a Wish exige que os preços do produto e de frete sejam enviados em dólar (USD). No entanto, ela cria os pedidos com o valor já convertido em reais (R$) para facilitar a emissão da nota fiscal.
+>
+> Isto significa que a integração deve enviar preços em dólar e aceitar pedidos em reais. Dessa maneira, a arquitetura usa apenas Real (R$) e faz a conversão na integração.
+>
+> Portanto, **a política comercial para Wish deve ser em reais (R$)** e todo fluxo de conversão será melhor detalhado no [passo 5](https://help.vtex.com/pt/tracks/integracao-com-a-wish--50hbG4bzhSIhjz1lzqI1g4/6EYEy1jRiAj465WOnhiczD).
 
 [Clique aqui](https://help.vtex.com/pt/faq/por-que-nao-consigo-criar-uma-nova-politica-comercial?locale=pt) para saber como contratar uma nova política caso necessário.
 
@@ -46,9 +45,8 @@ Para garantir que os pedidos integrem com sucesso, será necessário fazer toda
   3. Defina as [transportadoras](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/3fLedVI57srjBDDxxGgOWe) que farão as entregas da Wish;
   4. Associe as transportadoras às docas.
 
-<div class="alert alert-info">
-  OBS: a Wish realiza o repasse da comissão através da confirmação de entrega dos pedidos e consulta diretamente suas transportadoras parceiras para obter esta informação. <strong><i>Portanto, para vender na Wish é obrigatório usar as transportadoras parceiras para realizar as entregas dos pedidos.</i></strong>
-<a href="https://merchant.wish.com/documentation/shippingproviders"> Confira aqui a lista de transportadoras aceitas pela Wish.</a></div>
+>ℹ️ OBS: a Wish realiza o repasse da comissão através da confirmação de entrega dos pedidos e consulta diretamente suas transportadoras parceiras para obter esta informação. **<i>Portanto, para vender na Wish é obrigatório usar as transportadoras parceiras para realizar as entregas dos pedidos.</i>**
+> [ Confira aqui a lista de transportadoras aceitas pela Wish.](https://merchant.wish.com/documentation/shippingproviders)
 
 ## Definindo preços
 
diff --git a/docs/tutorials/en/account-management.md b/docs/tutorials/en/account-management.md
index 7db59a6c2..277a91915 100644
--- a/docs/tutorials/en/account-management.md
+++ b/docs/tutorials/en/account-management.md
@@ -19,9 +19,7 @@ Your accounts are managed on the Account management module. To access it, click
 
 On the page of each account, you find basic data about the virtual store, domain and multi-domain settings, access keys for APIs, the company logo and contact information.
 
-<div class="alert alert-info">
-Some of this data is useful solely for VTEX, and may not reflect in changes to the data displayed in the store.
-</div>
+>ℹ️ Some of this data is useful solely for VTEX, and may not reflect in changes to the data displayed in the store.
 
 ## Active/Inactive button
 
@@ -55,17 +53,15 @@ You can also click the `Configure this store` button to [Create a multistore](ht
 
 In the **Hosts** section, you need to add your store's main domain [set up with DNS pointing](https://help.vtex.com/en/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-danger">
-In case your operation has more than one VTEX account or subaccounts, do not trade domains among them. This will cause errors in different aspects of your store.
-</div>
+>❗ In case your operation has more than one VTEX account or subaccounts, do not trade domains among them. This will cause errors in different aspects of your store.
 
 Click `Add New Domain` to add a new host, and then enter the domain in the text field. 
 
-<div class="alert alert-warning">
-If you add more than one domain as your store's host, they will all display the same content. However, we recommend registering only one domain and using redirections for the other ones. Learn more about redirections:
-<ul><li><a href=”https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirection from other addresses</a></li>
-<li><a href=”https://help.vtex.com/en/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configuring access without www</a></li></ul>  
-</div>
+>⚠️ If you add more than one domain as your store's host, they will all display the same content. However, we recommend registering only one domain and using redirections for the other ones. Learn more about redirections:
+>
+> *<a href=”https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirection from other addresses</a>
+>
+> *<a href=”https://help.vtex.com/en/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configuring access without www</a>
 
 #### Subdomains
 
@@ -81,9 +77,7 @@ The **Contacts** part is only visible to users that are registered there. This r
 
 After a user has filled in and saved the **Name** and **E-mail** in the contacts field, an automatic e-mail is sent to it, informing about the registration and requesting the creation of a password (in the event he has no access to the admin).
 
-<div class="alert alert-info">
-The template for this automatic email can be changed in the <a href="https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84">Message Center</a> by modifying the <i>account registration</i> template.
-</div>
+>ℹ️ The template for this automatic email can be changed in the [Message Center](https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84) by modifying the <i>account registration</i> template.
 
 ![account registration](https://images.ctfassets.net/alneenqid6w5/I0CttFz6ayQW2Q8uOkKmc/19184a55a9a8de5cb3e04088251a9c93/account_registration.jpg)
 
diff --git a/docs/tutorials/en/actions-for-vtex-marketplace-operation.md b/docs/tutorials/en/actions-for-vtex-marketplace-operation.md
index 79f37efd7..1ac4c5629 100644
--- a/docs/tutorials/en/actions-for-vtex-marketplace-operation.md
+++ b/docs/tutorials/en/actions-for-vtex-marketplace-operation.md
@@ -47,9 +47,7 @@ The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-pa
 
 This tool is recommended for marketplaces that want to have more control over the curation of products they offer. 
 
-<div class="alert alert-info">
-To activate the Seller Portal for their sellers, the marketplace must request this feature by contacting their VTEX account CSM. 
-</div>
+>ℹ️ To activate the Seller Portal for their sellers, the marketplace must request this feature by contacting their VTEX account CSM.
 
 ## Cataloging offers
 
@@ -57,9 +55,7 @@ A product submitted by a seller to a marketplace with price and inventory inform
 
 The cataloging process is performed on the [Received SKUs](https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus/) page, in the **MARKETPLACE > Sellers** menu of your VTEX Admin, or using the [Match Received SKUs](https://developers.vtex.com/vtex-rest-api/reference/match) API. 
 
-<div class="alert alert-info">
-Before approving an offer, it is important to ensure that the product information submitted by the seller matches your business strategy. When listing offers, consider the quality of the information submitted by the seller, such as price, product description, and image.
-</div>
+>ℹ️ Before approving an offer, it is important to ensure that the product information submitted by the seller matches your business strategy. When listing offers, consider the quality of the information submitted by the seller, such as price, product description, and image.
 
 [VTEX Matcher](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424) is a tool used by marketplaces to analyze offers submitted by sellers and accelerate their cataloging process. You can configure VTEX Matcher to operate on rules other than the default configuration using the [Save Account's Approval Settings API](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig).
 
diff --git a/docs/tutorials/en/activating-new-vtex-cdn.md b/docs/tutorials/en/activating-new-vtex-cdn.md
index c71a2d289..64c8740b8 100644
--- a/docs/tutorials/en/activating-new-vtex-cdn.md
+++ b/docs/tutorials/en/activating-new-vtex-cdn.md
@@ -15,9 +15,7 @@ legacySlug: activating-new-vtex-cdn
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
-<div class="alert alert-warning">
-With a commitment of constant evolution of our product, VTEX is making available to its stores a new CDN (Content Delivery Network). In this new model, <strong>all pages of the website will be delivered through this new specialized CDN</strong>, not being limited to static files.
-</div>
+>⚠️ With a commitment of constant evolution of our product, VTEX is making available to its stores a new CDN (Content Delivery Network). In this new model, **all pages of the website will be delivered through this new specialized CDN**, not being limited to static files.
 
 A Content Delivery Network focus on security, low latency and high transfer speed, working with the best technologies for this goal, including being geographically close to the client that access the virtual store.
 
@@ -36,9 +34,7 @@ Once the requirements of this article have been fulfilled, [this form](https://d
 
 ### Enable HTTPS throughout the site
 
-<div class="alert alert-info">
-One of the requirements for the new CDN is that the site be fully available on HTTPS.
-</div>
+>ℹ️ One of the requirements for the new CDN is that the site be fully available on HTTPS.
 
 That's because, with the new CDN, any HTTP page will be automatically redirected to HTTPS. But first it is important to set up your store in VTEX so that it accepts the traffic in this protocol. Otherwise, it will be redirected back to HTTP - creating a redirect loop, which will break the navigation of these pages.
 
@@ -94,9 +90,7 @@ Old pointings use addresses like:
 
 Regardless of what is the case of your store, you should upgrade to the new standard.
 
-<div class="alert alert-danger">
-<strong>Important:</strong> the old CNAME<strong> must be removed</ strong>. Having two entries in your DNS is likely to cause problems. Only the new CNAME entry should be kept.
-</div>
+>❗ **Important:** the old CNAME<strong> must be removed</ strong>. Having two entries in your DNS is likely to cause problems. Only the new CNAME entry should be kept.
 
 Do not forget to request the final activation filling the [form](https://docs.google.com/forms/d/e/1FAIpQLSdI2FBXGmlSOXEtWxrYfVveln7xOJcmYotqrKfgFgmHn771Fg/viewform).The store will only work with CNAME and HTTPS, but its completion helps us activate CDN in advance for your store, so you can enjoy the new features.
 
diff --git a/docs/tutorials/en/activating-skus-in-bulk.md b/docs/tutorials/en/activating-skus-in-bulk.md
index 99f16d538..256307139 100644
--- a/docs/tutorials/en/activating-skus-in-bulk.md
+++ b/docs/tutorials/en/activating-skus-in-bulk.md
@@ -29,10 +29,9 @@ To activate all SKUs using VTEX Admin, follow the steps below:
 1. Access the URL `https://{accountName}.myvtex.com/admin/site/productskuactivateall.aspx`.
 2. Click on `Enable all SKUs`.
 
-<div class="alert alert-warning">
-<p>SKUs that are registered with invalid data will not have the <em>Activate SKU if possible</em> flag enabled.</p>
-<p>In case not all of the SKUs have been flagged with <em>Activate SKU if possible</em>, repeat the process described above.</p>
-</div>
+>⚠️ SKUs that are registered with invalid data will not have the *Activate SKU if possible* flag enabled.
+>
+> In case not all of the SKUs have been flagged with *Activate SKU if possible*, repeat the process described above.
 
 ## Activate a group of SKUs
 
diff --git a/docs/tutorials/en/active-campaign-suiteshare.md b/docs/tutorials/en/active-campaign-suiteshare.md
index 97f192123..a62c47334 100644
--- a/docs/tutorials/en/active-campaign-suiteshare.md
+++ b/docs/tutorials/en/active-campaign-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: active-campaign-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md b/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md
index 2c7323d11..cf9c45e85 100644
--- a/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md
+++ b/docs/tutorials/en/add-3ds-support-to-the-integration-with-adyen.md
@@ -30,9 +30,7 @@ To add support for [3DS](https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1e
 
 After configuring the connector on VTEX, go to the Adyen dashboard to enable 3DS for your store transactions.
 
-<div class="alert alert-warning">
-  We recommend that you set up the test environment before moving to the live environment. Validate the settings in the test environment, then access the <b>Live</b> environment to make final adjustments.
-  </div>
+>⚠️ We recommend that you set up the test environment before moving to the live environment. Validate the settings in the test environment, then access the **Live** environment to make final adjustments.
 
 1. Click on the links below to access Adyen's test and live environments:
 
diff --git a/docs/tutorials/en/adding-a-record-on-a-master-data-form.md b/docs/tutorials/en/adding-a-record-on-a-master-data-form.md
index 033d6bb6f..14fb0c774 100644
--- a/docs/tutorials/en/adding-a-record-on-a-master-data-form.md
+++ b/docs/tutorials/en/adding-a-record-on-a-master-data-form.md
@@ -19,21 +19,16 @@ To add a record in a Master Data form, you need to access Master Data and choose
 
 Fields can be configured as editable or not directly in the data entity. Learn more in [Data entity](https://help.vtex.com/en/tutorial/entidade-de-dados--tutorials_1265).
 
-<div class="alert alert-warning">
-This article covers Master Data v1. It is important to evaluate which version of Master Data meets your needs or is used in your operation. Learn more:
-<ul>
-<li>
-<a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version features
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article covers Master Data v1. It is important to evaluate which version of Master Data meets your needs or is used in your operation. Learn more:
+>
+> *<a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version features
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Adding a record
 
diff --git a/docs/tutorials/en/adding-a-seller-beta.md b/docs/tutorials/en/adding-a-seller-beta.md
index 5fec3b531..a2f173419 100644
--- a/docs/tutorials/en/adding-a-seller-beta.md
+++ b/docs/tutorials/en/adding-a-seller-beta.md
@@ -19,9 +19,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 To add an unidentifiable seller, aka [white label seller](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), this model must be provided for in your contract with VTEX. In case you need to make changes to your contract, please contact your VTEX sales representative and submit a request to [add a franchise account](https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) through our Support. Every franchise account is created as a white label seller. It is not possible to change the seller type after its creation. 
 
-<div class="alert alert-info">
-If you want to find new partners to sell in your marketplace, use the Marketplace Network, which facilitates the identification and the communication between marketplaces and sellers operating in the VTEX ecosystem, as well as certified partners.
-</div>
+>ℹ️ If you want to find new partners to sell in your marketplace, use the Marketplace Network, which facilitates the identification and the communication between marketplaces and sellers operating in the VTEX ecosystem, as well as certified partners.
 
 1. In your VTEX Admin, go to _MARKETPLACE > Sellers > Management_.    
 2. Click `Add Seller`.      
@@ -66,9 +64,7 @@ If you want to find new partners to sell in your marketplace, use the Marketplac
 - **Exchanges and returns**: Text describing the exchange and return policy previously agreed upon by the marketplace and the seller.  
 - **Privacy and security policy**: Text describing the security policy previously agreed upon by the marketplace and the seller.  
 
-<div class="alert alert-info">
-In the new version of the page, released on 2022, we have removed the Catalog Endpoint field from the screen, as it is no longer needed for integration with new sellers. If necessary, it is still possible to manage the fields via API.
-</div>
+>ℹ️ In the new version of the page, released on 2022, we have removed the Catalog Endpoint field from the screen, as it is no longer needed for integration with new sellers. If necessary, it is still possible to manage the fields via API.
 
 Once you have filled out the form and clicked **Save**, your seller will be added to the marketplace. To complete your store's configuration as a marketplace, you must also [map brands, categories, and specifications from the seller's catalog](https://help.vtex.com/en/tutorial/mapeando-categorias-e-marcas-para-marketplace/) and [approve the ads added](https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus/).
 
diff --git a/docs/tutorials/en/adding-a-seller.md b/docs/tutorials/en/adding-a-seller.md
index 1b106b102..dea877e9f 100644
--- a/docs/tutorials/en/adding-a-seller.md
+++ b/docs/tutorials/en/adding-a-seller.md
@@ -21,9 +21,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 To add an unidentifiable seller, aka [white label seller](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), this model must be provided for in your contract with VTEX. In case you need to make changes to your contract, please contact your VTEX sales representative and submit a request to [add a franchise account](https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) through our Support. Every franchise account is created as a white label seller. It is not possible to change the seller type after its creation. 
 
-<div class="alert alert-info">
-If you want to find new partners to sell in your marketplace, use the __Find sellers__, which facilitates the identification and the communication between marketplaces and sellers operating in the VTEX ecosystem, as well as certified partners.
-</div>
+>ℹ️ If you want to find new partners to sell in your marketplace, use the __Find sellers__, which facilitates the identification and the communication between marketplaces and sellers operating in the VTEX ecosystem, as well as certified partners.
 
 1. In your VTEX Admin, go to _MARKETPLACE > Management_.    
 2. Click `Add Seller`.      
@@ -68,9 +66,7 @@ If you want to find new partners to sell in your marketplace, use the __Find sel
 - **Exchanges and returns**: Text describing the exchange and return policy previously agreed upon by the marketplace and the seller.  
 - **Privacy and security policy**: Text describing the security policy previously agreed upon by the marketplace and the seller.  
 
-<div class="alert alert-info">
-In the new version of the page, released on 2022, we have removed the Catalog Endpoint field from the screen, as it is no longer needed for integration with new sellers. If necessary, it is still possible to manage the fields via API.
-</div>
+>ℹ️ In the new version of the page, released on 2022, we have removed the Catalog Endpoint field from the screen, as it is no longer needed for integration with new sellers. If necessary, it is still possible to manage the fields via API.
 
 Once you have filled out the form and clicked **Save**, your seller will be added to the marketplace. To complete your store's configuration as a marketplace, you must also [map brands, categories, and specifications from the seller's catalog](https://help.vtex.com/en/tutorial/mapeando-categorias-e-marcas-para-marketplace/) and [approve the ads added](https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus/).
 
diff --git a/docs/tutorials/en/adding-an-attachment.md b/docs/tutorials/en/adding-an-attachment.md
index aed618f2d..d28ec144c 100644
--- a/docs/tutorials/en/adding-an-attachment.md
+++ b/docs/tutorials/en/adding-an-attachment.md
@@ -39,9 +39,7 @@ After adding the attachment, you need to add the keys and **permitted values** r
 3. Click `Add New`. You can add other keys by repeating this process.
 4. Click on `Save`.
 
-<div class="alert alert-warning">
-  <p>The <strong>Maximum Number of Characters</strong> field is required. If you do not fill it in, the attachment will not be displayed to your customer as a selection option in the cart.</p>
-</div>
+>⚠️ The **Maximum Number of Characters** field is required. If you do not fill it in, the attachment will not be displayed to your customer as a selection option in the cart.
 
 ## Associating the attachment with a SKU
 
@@ -56,6 +54,4 @@ After creating the SKU attachment and configuring its keys and permitted values,
 
 You can also associate an attachment to an SKU by using the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuattachment).
 
-<div class="alert alert-warning">
-  <p>VTEX does not control the inventory of the attachment. This is the responsibility of the Marketplace or the Seller.</p>
-</div>
+>⚠️ VTEX does not control the inventory of the attachment. This is the responsibility of the Marketplace or the Seller.
diff --git a/docs/tutorials/en/adding-collections-cms.md b/docs/tutorials/en/adding-collections-cms.md
index 3d044614a..6ac798b2d 100644
--- a/docs/tutorials/en/adding-collections-cms.md
+++ b/docs/tutorials/en/adding-collections-cms.md
@@ -27,9 +27,7 @@ Follow the steps below to add a new collection:
 4. Fill out the Collection form fields. For more on the meaning of each one of these fields, read our article on [how to fill out new collection fields](https://help.vtex.com/en/tutorial/filling-out-collection-registration-fields--7eKL7CFRW3yGKlnDfQetbj).
 5. Click on __Save Product Cluster__.
 
-<div class="alert alert-warning">
-When the number of created collections surpasses twenty, those exceeding that number can be found through the search field on the admin interface. Search by the name of the collection you want to find.
-</div>
+>⚠️ When the number of created collections surpasses twenty, those exceeding that number can be found through the search field on the admin interface. Search by the name of the collection you want to find.
 
 Choosing the products that will make up a collection is done by clicking on __New Group__ in the desired collection, creating a __group__.
 
@@ -54,9 +52,7 @@ Of which:
 
 To this end, the first group that is created in any collection must necessarily be type *Inclusive*.
 
-<div class="alert alert-warning">
-Be mindful of the set group type. When adding products to an <i>Exclusive</i> group type, for example, these <strong>will not</strong> be added to a collection due to the nature of the group.
-</div>
+>⚠️ Be mindful of the set group type. When adding products to an <i>Exclusive</i> group type, for example, these **will not** be added to a collection due to the nature of the group.
 
 ## Selecting Products
 
@@ -103,15 +99,11 @@ In the __find SKUs__ field, you can type in as many SKU IDs as needed, separatin
 
 To remove an SKU from the list, click on the red button next to it.
 
-<div class="alert alert-info">
-When the number of listed SKUs surpasses ten, a page control becomes available.
-</div>
+>ℹ️ When the number of listed SKUs surpasses ten, a page control becomes available.
 
 ### By spreadsheet
 
- <div class="alert alert-info">
-Get the file template for adding SKUs to or removing them from a collection <a href="//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls">here</a>.
-</div>
+ >ℹ️ Get the file template for adding SKUs to or removing them from a collection [here](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls).
 
 #### Bulk Upload
 
@@ -135,15 +127,11 @@ To avoid having to remove SKUs one at a time, you can use the import function of
 
 In this specific case, the SKUs listed in the imported spreadsheet will be excluded from the group. Do this by clicking on __remove SKUs__ after the file has been loaded. 
 
-<div class="alert alert-warning">
-Disabled SKUs will not be removed or added, even if they appear as listed in the spreadsheet.
-</div>
+>⚠️ Disabled SKUs will not be removed or added, even if they appear as listed in the spreadsheet.
 
 ## Products by Market Launch date
 
-<div class="alert alert-warning">
-In the <strong>Other options</strong> section, the <strong>Pre-sales</strong> and <strong>Launches</strong> options are add-ons to choosing products by Category, Brand or SKU, meaning that these flags will only work if you have previously selected them.
-</div>
+>⚠️ In the **Other options** section, the **Pre-sales** and **Launches** options are add-ons to choosing products by Category, Brand or SKU, meaning that these flags will only work if you have previously selected them.
 
 Note that you can only select one of the two options. Should you want both add-ons, create two groups and configure each one with the respective option.
 
@@ -157,6 +145,4 @@ In order to create a product collection that has not been launched yet, select t
 
 The __Launches__ option allows you to create a recently launched product collection. Upon selecting this option, the system considers all of the products that were launched within a 30-day interval prior to the present date. The launch date taken into account is also the same one set in the _Market launch date_ in the product file.
 
-<div class="alert alert-info">
-To know more about how to exclude a product collection, read our article on <a href="https://help.vtex.com/en/tutorial/how-to-delete-a-collection--6C620yHzwsGoS8iaCocAM2">how to delete collections</a>.
-</div>
+>ℹ️ To know more about how to exclude a product collection, read our article on [how to delete collections](https://help.vtex.com/en/tutorial/how-to-delete-a-collection--6C620yHzwsGoS8iaCocAM2).
diff --git a/docs/tutorials/en/additional-shipping-costs.md b/docs/tutorials/en/additional-shipping-costs.md
index 451d5e381..dca92ae33 100644
--- a/docs/tutorials/en/additional-shipping-costs.md
+++ b/docs/tutorials/en/additional-shipping-costs.md
@@ -28,10 +28,8 @@ You can configure the following additional costs:
 
 ![adicionais frete EN](https://images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/eee27446335556a96fece61f8d2f0e8f/adicionais_frete_EN.svg)
 
-<div class="alert alert-danger">
-Note that all of them can be simultaneously considered for composing the shipping rate. The final calculation of the <a href="https://help.vtex.com/en/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">shipping rate</a> is the sum of all additional charges plus the flat rate. 
-The shipping rate is not the total shipping cost.
-</div>
+>❗ Note that all of them can be simultaneously considered for composing the shipping rate. The final calculation of the [shipping rate](https://help.vtex.com/en/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM) is the sum of all additional charges plus the flat rate. 
+> The shipping rate is not the total shipping cost.
 
 ## Weight-based additional shipping charge
 
@@ -93,9 +91,7 @@ Additional shipping charge: ($10+$0+$9+$5)x10%=$2,4
 Additional shipping costs:($9+$5+$2,4)=$16,4  
 Shipping rate: ($10+$16,4)=$26,4  
 
-<div class="alert alert-danger">
-Note that the calculation of the price-based charge considers the cart's total price — without discounts and promotions. If the price-based charge is lower than the insurance charge, it will not be considered for the total shipping cost.
-</div>
+>❗ Note that the calculation of the price-based charge considers the cart's total price — without discounts and promotions. If the price-based charge is lower than the insurance charge, it will not be considered for the total shipping cost.
 
 ### Configuration instructions 
 
@@ -132,9 +128,7 @@ Shipping rate: ($15 + $10.3) = $25.3
 
 You can only configure the additional insurance charge via the [shipping rate template](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127) in the _MinimumValueInsurance_ field.
 
-<div class="alert alert-danger">
-If the price-based charge is lower than the insurance charge, it will not be considered for the total shipping cost.
-</div>
+>❗ If the price-based charge is lower than the insurance charge, it will not be considered for the total shipping cost.
 
 ## Additional shipping charge
 
diff --git a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
index 4274e1086..178674ebf 100644
--- a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
@@ -52,9 +52,7 @@ VTEX currently offers a single ad format: search results. Learn more about this
 7. In the *Budget, bid, and schedule* section, click the edit button <i class="fas fa-pencil-alt"></i>.
 8. Set the bid amount for each product. You can set each value individually.
 
-  <div class="alert alert-info">
-The bid for a product is the cost per click (CPC), i.e., the amount spent when a user clicks an ad. Learn more about <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campaigns">campaigns</a> and how an <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ad-priority">auction</a> works.
-</div>
+  >ℹ️ The bid for a product is the cost per click (CPC), i.e., the amount spent when a user clicks an ad. Learn more about [campaigns](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campaigns) and how an [auction](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ad-priority) works.
 
 9. Click `Save`.
 10. Set the campaign's total budget and end date.
diff --git a/docs/tutorials/en/affiliates-program-app.md b/docs/tutorials/en/affiliates-program-app.md
index 9db445376..a12279442 100644
--- a/docs/tutorials/en/affiliates-program-app.md
+++ b/docs/tutorials/en/affiliates-program-app.md
@@ -86,9 +86,7 @@ Click the `Add Affiliate` button to create a new affiliate, fill in the fields d
 
 Enter any of the following information in the search bar to search for an affiliate: _Affiliate ID, Name, Store Name, Email_, or _Phone_.
 
-<div class="alert alert-warning">
-In the <b>Affiliates Program app</b>, not only is the term affiliate different from the <a href="https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0">usual VTEX affiliate concept</a>, but the <code>Affiliate ID</code> does not correspond to the default code. In the app, the <code>Affiliate ID</code> is an alphanumeric code automatically generated when you create a new affiliate.
-</div>
+>⚠️ In the **Affiliates Program app**, not only is the term affiliate different from the [usual VTEX affiliate concept](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0), but the `Affiliate ID` does not correspond to the default code. In the app, the `Affiliate ID` is an alphanumeric code automatically generated when you create a new affiliate.
 
 ### Filtering affiliates
 
@@ -150,9 +148,7 @@ You can filter the order search by the following criteria:
 
 The **Affiliates Program app** allows you to export a list with a CSV extension of your affiliate orders. 
 
-<div class="alert alert-warning">
-To enable the list export function, you must first set up email templates described in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app#email-templates">Affiliates Program app</a> developer's guide.
-</div>
+>⚠️ To enable the list export function, you must first set up email templates described in the [Affiliates Program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app#email-templates) developer's guide.
 
 After configuration, click **Export** on the **Order Management** page to export the list. The following confirmation message will be displayed:
 
diff --git a/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md
index 99b4a0292..45ba1e408 100644
--- a/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/en/amazon-multi-channel-fulfillment-mcf-app.md
@@ -16,9 +16,7 @@ subcategory: 1P1vFnzQ4TQJsBRDoPVKUI
 ---
 
 
-<div class="alert alert-info">
-This App is in beta, which means we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.
-</div>
+>ℹ️ This App is in beta, which means we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.
 
 The app allows you to integrate your business with the Amazon Multi-Channel Fulfillment (MCF) program. With the integration, VTEX clients can use Amazon's logistics network in their own stores. This way, you can sell items that are stored in Amazon fulfillment centers, and after each sale in your ecommerce, the VTEX platform sends the order information to Amazon, where it is picked, packed, and shipped to the shoppers.
 
@@ -36,11 +34,9 @@ Before installing the app:
 - Verify if the products in your store meet [Amazon's restriction policies](https://sellercentral.amazon.com/gp/help/external/200164330)
 - Ensure that your store is located in one of the countries where MCF is available. Amazon MCF is available in some countries, such as the United States, Australia, Mexico, Germany and Canada. Check out the updated list of countries where MCF is available on [Amazon's page](https://sell.amazon.com/fulfillment-by-amazon/fba-multi-channel).
 
-<div class="alert alert-danger">
-Once the app is installed, the VTEX platform will treat the integration as an Amazon external store and uses marketplace-type integration with Amazon.
-<p> The app must be installed on all VTEX accounts in which you want to use the feature.
-<p> We recommend using Checkout V6.
-</div>
+>❗ Once the app is installed, the VTEX platform will treat the integration as an Amazon external store and uses marketplace-type integration with Amazon.
+> <p> The app must be installed on all VTEX accounts in which you want to use the feature.
+> <p> We recommend using Checkout V6.
 
 ## Installation, configuration and access:
 
@@ -79,10 +75,8 @@ To configure this, please go to Admin and follow the steps below:
 
 In both steps 8 and 10, the key to be filled in is the Google geolocation key. To generate a key, [please refer to Google's developer guide on how to generate a key](https://developers.google.com/maps/documentation/geocoding/overview).
 
-<div class="alert alert-info">
-If you have questions about Google geolocation key, please read in detail how the VTEX platform uses this configuration in the articles <a href="https://help.vtex.com/en/tutorial/geolocation-at-checkout--tutorials_4345">Setting up geolocation at checkout</a>
- and <a href="https://help.vtex.com/en/tutorial/registering-geolocation--tutorials_138">Registering geolocation</a>.
-</div>
+>ℹ️ If you have questions about Google geolocation key, please read in detail how the VTEX platform uses this configuration in the articles [Setting up geolocation at checkout](https://help.vtex.com/en/tutorial/geolocation-at-checkout--tutorials_4345)
+>  and [Registering geolocation](https://help.vtex.com/en/tutorial/registering-geolocation--tutorials_138).
 
 ### Installing the app
 
@@ -104,9 +98,7 @@ To install the app, go to the VTEX App Store:
     - **ERP URL:** the address of the ERP that will include the order invoices (in case the **Automatic Invoice** field is set to Deactivated).
     - **Amazon Marketplace:** country where you will use Amazon MCF.
 
-<div class="alert alert-warning">
-The configurations made in the Automatic Invoice field will be applied to all orders.
-</div>
+>⚠️ The configurations made in the Automatic Invoice field will be applied to all orders.
 
 ![MCF](https://images.contentful.com/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/e26c0d8fc1ec3a9069d09e027e36aa98/Amazon_MCF_EN.PNG)
 
diff --git a/docs/tutorials/en/analytics.md b/docs/tutorials/en/analytics.md
index 60fb417fb..b87bebcdf 100644
--- a/docs/tutorials/en/analytics.md
+++ b/docs/tutorials/en/analytics.md
@@ -41,9 +41,7 @@ The report data is updated every four hours and contains the following informati
 * **Orders**: number of orders placed from the search results. To calculate this metric, we consider all orders placed after the customer clicked on a search result, even if they ended up buying a different product than the one they clicked on.
 * **Sales**: the total revenue generated by orders placed from the search results. The calculation follows the same logic as the **Orders** metric, the difference being that the result reflects the revenue instead of the number of orders.
 
-<div class="alert alert-info">
-  <p>The data displayed in the report is limited to the top 10,000 search terms. If you want the complete search data for your store, you must <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exporting-reports">export the report</a>.</p>
-</div>
+>ℹ️ The data displayed in the report is limited to the top 10,000 search terms. If you want the complete search data for your store, you must [export the report](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exporting-reports).
 
 When you opt to [export a report](#exporting-reports), you can generate it **With funnel metrics**. If this option is selected, four new columns will be added to the file:
 
diff --git a/docs/tutorials/en/analyze-suiteshare.md b/docs/tutorials/en/analyze-suiteshare.md
index bdf97f524..566e0b5e1 100644
--- a/docs/tutorials/en/analyze-suiteshare.md
+++ b/docs/tutorials/en/analyze-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: analyze
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/anapro-suiteshare.md b/docs/tutorials/en/anapro-suiteshare.md
index fab956a70..5a88b628f 100644
--- a/docs/tutorials/en/anapro-suiteshare.md
+++ b/docs/tutorials/en/anapro-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: anapro
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/antifraud-provider.md b/docs/tutorials/en/antifraud-provider.md
index 26844ca04..0c7284a93 100644
--- a/docs/tutorials/en/antifraud-provider.md
+++ b/docs/tutorials/en/antifraud-provider.md
@@ -142,9 +142,7 @@ These keys should be made available by you and will serve to identify the store
 ## Cardholder Document Configuration
 During payment transactions analysis, some anti-fraud providers may choose not to use additional information such as the cardholder’s personal identification. In these cases, the merchant has the autonomy to decide whether or not to request this document from his customer during the checkout procedure.
 
-<div class="alert alert-warning">
-  The configuration option <b>Cardholder document field</b> will only be available to the merchant if the anti-fraud provider declares in its <a href="https://developers.vtex.com/vtex-rest-api/reference/manifest">manifest</a>, the cardholder document field (<code>cardholderDocument</code>) as <code>optional</code>. Learn more at <a href="https://developers.vtex.com/vtex-rest-api/docs/cardholder-document-configuration">Cardholder Document Configuration</a>.
-  </div>
+>⚠️ The configuration option **Cardholder document field** will only be available to the merchant if the anti-fraud provider declares in its [manifest](https://developers.vtex.com/vtex-rest-api/reference/manifest), the cardholder document field (`cardholderDocument`) as `optional`. Learn more at [Cardholder Document Configuration](https://developers.vtex.com/vtex-rest-api/docs/cardholder-document-configuration).
 
 To set up the cardholder document field, follow the steps below:
 
diff --git a/docs/tutorials/en/application-keys.md b/docs/tutorials/en/application-keys.md
index 988405f84..a65012e32 100644
--- a/docs/tutorials/en/application-keys.md
+++ b/docs/tutorials/en/application-keys.md
@@ -33,9 +33,7 @@ External application keys are credentials generated in and managed by other VTEX
 
 ## Managing application keys
 
-<div class="alert alert-warning">
-  <p>A <a href="https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">role</a> with the <strong>Save User</strong> <a href="https://help.vtex.com/en/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">resource</a> is required to manage users and application keys. The default role for this purpose is <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, but it is also possible to <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role">create a custom role</a> with this resource.</p>
-</div>
+>⚠️ A [role](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) with the **Save User** [resource](https://help.vtex.com/en/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) is required to manage users and application keys. The default role for this purpose is [User Administrator - RESTRICTED](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted), but it is also possible to [create a custom role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role) with this resource.
 
 On the **Application Keys** page, you can manage the [internal](#internal-app-keys) and [external](#external-app-keys) app keys that have access to your account, including:
 
@@ -76,9 +74,7 @@ To create internal app keys in your account, follow the steps below:
 6. Click the `Generate` button.
 7. Click <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> to copy the **Application token**. _This secret will only be displayed once. Save it in a safe place._
 
-<div class="alert alert-warning">
-  <p>Secure your application keys and token pairs as you would with other credentials, such as usernames and passwords. If you suspect an application key is compromised, immediately deactivate the key in your account. To learn more, read the <a href="#activating-or-deactivating-application-keys">Activating or deactivating application keys</a> section of this article.</p>
-</div>
+>⚠️ Secure your application keys and token pairs as you would with other credentials, such as usernames and passwords. If you suspect an application key is compromised, immediately deactivate the key in your account. To learn more, read the [Activating or deactivating application keys](#activating-or-deactivating-application-keys) section of this article.
 
 ## Adding external application keys
 
@@ -94,9 +90,7 @@ To add third-party application keys, follow the steps below:
 
 For an application key to successfully make API requests to your account, it must both be active and have [roles](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) specifying the account resources it is allowed to access.
 
-<div class="alert alert-danger">
-<p>Unrestricted use of overly permissive roles increases the risk of store attacks through leaked login credentials.</p>
-</div>
+>❗ Unrestricted use of overly permissive roles increases the risk of store attacks through leaked login credentials.
 
 Application keys are created, by default, with no permission to access any account resources.
 
@@ -122,17 +116,13 @@ These are the visible fields on the **Application Keys** page:
 - **Account:** VTEX account managing the app key.
 - **Status:** Current status of the app key, which can be active or inactive.
 
-<div class="alert alert-info">
-  <p>Note that the <strong>Label</strong> field is not displayed on the <strong>Application Keys</strong>page. To see a description of the purpose of an internal app key, you will have to use the<strong>Key</strong> value to find it on the <strong>My Keys</strong> page. It is not possible to add labels to external app keys.</p>
-</div>
+>ℹ️ Note that the **Label** field is not displayed on the **Application Keys**page. To see a description of the purpose of an internal app key, you will have to use the**Key** value to find it on the **My Keys** page. It is not possible to add labels to external app keys.
 
 ## Activating or deactivating application keys
 
 If an application key that has access to your account is compromised, you should immediately revoke its access to your account. If you make a mistake, you can reactivate it to reestablish the impacted integration. This can be done in various ways depending on the [type of application key](#types-of-application-keys).
 
-<div class="alert alert-warning">
-  <p>You should only reactivate an app key if you are certain it has not been compromised. Anyone with the associated app token will regain privileged access to your account.</p>
-</div>
+>⚠️ You should only reactivate an app key if you are certain it has not been compromised. Anyone with the associated app token will regain privileged access to your account.
 
 ### Deactivating internal application keys
 
diff --git a/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
index 164eeee4c..865d92f8e 100644
--- a/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/en/approving-payment-of-the-bank-payment-slip.md
@@ -29,13 +29,9 @@ This approval can be done manually through the Orders Management module as shown
 
 **After approval of the payment, the order will go through the normal purchase flow.**
 
-<div class="alert alert-info">
-In the Account management module, the user must have a role that includes the <code>Notify payment</code> permission to be able to approve payments.
-</div>
+>ℹ️ In the Account management module, the user must have a role that includes the `Notify payment` permission to be able to approve payments.
 
 To approve payments through API, check the [documentation about the payment notification request](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/payments/-paymentId-/payment-notification).
 
-<div class="alert alert-warning">
-Since <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">ERP integrations</a> are governed by the <a href="https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#">orders flow</a>, manually approving a payment will continue the integration of this order with the store’s back office as usual. Therefore, caution is recommended when approving payments manually, in order to ensure that every order that is processed and shipped is received.
-</div>
+>⚠️ Since [ERP integrations](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) are governed by the [orders flow](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#), manually approving a payment will continue the integration of this order with the store’s back office as usual. Therefore, caution is recommended when approving payments manually, in order to ensure that every order that is processed and shipped is received.
 
diff --git a/docs/tutorials/en/apps-overview.md b/docs/tutorials/en/apps-overview.md
index f18886afe..a9f0f3744 100644
--- a/docs/tutorials/en/apps-overview.md
+++ b/docs/tutorials/en/apps-overview.md
@@ -28,9 +28,7 @@ A VTEX app extends the functionalities of the VTEX platform, helping merchants c
 
 Our plug and play solution allows third party developers to create apps for the VTEX ecosystem in multiple ways. Both first-party and third-party apps are available for download at the [VTEX App Store](https://apps.vtex.com/), and they can be either free or paid. 
 
-<div class="alert alert-info">
-If you are a developer, check the <a href = "https://developers.vtex.com">Developer Portal</a> for more information on how to develop your own VTEX apps.
-  </div>
+>ℹ️ If you are a developer, check the <a href = "https://developers.vtex.com">Developer Portal</a> for more information on how to develop your own VTEX apps.
 
 The Apps menu allows merchants to download new apps directly from the App Store and manage installed apps without leaving the VTEX Admin. Please notice that the Apps menu is flexible and might include custom sections related to the apps installed in your account. 
 
diff --git a/docs/tutorials/en/assembly-options-app.md b/docs/tutorials/en/assembly-options-app.md
index 0a596bef5..9ed624244 100644
--- a/docs/tutorials/en/assembly-options-app.md
+++ b/docs/tutorials/en/assembly-options-app.md
@@ -15,9 +15,7 @@ legacySlug: assembly-options-app
 subcategory: 3xpuy7xGlzKKg6vxqiExZ2
 ---
 
-<div class="alert alert-warning">
-<p>This app is only available for stores developed using<a href="https://vtex.com/br-pt/store-framework/"> VTEX IO</a>. Before proceeding, you need to <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer">install and configure Product Customizer</a> in your store.</p>
-</div>
+>⚠️ This app is only available for stores developed using[ VTEX IO](https://vtex.com/br-pt/store-framework/). Before proceeding, you need to [install and configure Product Customizer](https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer) in your store.
 
 Product customization options are available at VTEX when using [Assembly Options](https://help.vtex.com/en/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH). This solution helps create [attachments](https://help.vtex.com/en/tutorial/what-is-an-attachment--aGICk0RVbqKg6GYmQcWUm) for complex scenarios in which you need to manage different product combinations, quantities, additional items and costs.
 
@@ -27,9 +25,7 @@ As an alternative to implementing Assembly Options through Catalog attachments,
 
 You can install the app for free from the [VTEX App Store](https://apps.vtex.com/vtex-admin-assembly-options/p) or via [VTEX IO CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) by following the steps in the [Assembly Options guide for developers](https://developers.vtex.com/vtex-developer-docs/docs/assembly-options-app).
 
-<div class="alert alert-warning">
-<p>If you install the Assembly Options app in a <a href="https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w">seller account</a>, the product customization options will be displayed to your customers at checkout. If you want the options to be displayed in the product page, you need to install the app in a <a href="https://help.vtex.com/en/tutorial/what-is-a-marketplace--680lLJTnmEAmekcC0MIea8">marketplace account</a>.</p>
-</div>
+>⚠️ If you install the Assembly Options app in a [seller account](https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w), the product customization options will be displayed to your customers at checkout. If you want the options to be displayed in the product page, you need to install the app in a [marketplace account](https://help.vtex.com/en/tutorial/what-is-a-marketplace--680lLJTnmEAmekcC0MIea8).
 
 After installation, the **Catalog > Assembly Options** page will become available in the VTEX Admin. Below, you will find the app’s available features.
 
@@ -83,9 +79,7 @@ The **Products > Assembly Options > New Assembly Options** page contains a form
 
 When you save an assembly option, an attachment is automatically created in **Catalog > Attachments** with the prefix `vtex.assembly-option.` added to the name of the assembly option created. For example: `vtex.assembly-option.Ingredients`.
 
-<div class="alert alert-warning">
-  <p>For the customization options created in <b>Assembly Options</b> to appear in the storefront, you will need to associate the attachment created with a SKU in <strong>Catalog > Products and SKUs > Advanced settings > Attachments</strong>. To do so, follow the steps described in <a href="https://help.vtex.com/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU#associating-the-attachment-with-a-sku">Associating the attachment with a SKU</a>.</p>
-</div>
+>⚠️ For the customization options created in **Assembly Options** to appear in the storefront, you will need to associate the attachment created with a SKU in **Catalog > Products and SKUs > Advanced settings > Attachments**. To do so, follow the steps described in [Associating the attachment with a SKU](https://help.vtex.com/en/tutorial/adding-an-attachment--7zHMUpuoQE4cAskqEUWScU#associating-the-attachment-with-a-sku).
 
 ## Learn more
 
diff --git a/docs/tutorials/en/assembly-options.md b/docs/tutorials/en/assembly-options.md
index de0561d14..caf020ef7 100644
--- a/docs/tutorials/en/assembly-options.md
+++ b/docs/tutorials/en/assembly-options.md
@@ -15,9 +15,7 @@ legacySlug: assembly-options-en
 subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 ---
 
-<div class="alert alert-warning">
-  <p>This feature is only available for stores developed using <a href="https://vtex.com/us-en/store-framework/">VTEX IO</a>. Before proceeding, you need to <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer">install and configure Product Customizer</a> in your store. </p>
-</div>
+>⚠️ This feature is only available for stores developed using [VTEX IO](https://vtex.com/us-en/store-framework/). Before proceeding, you need to [install and configure Product Customizer](https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer) in your store.
 
 An assembly option is an [attachment](https://help.vtex.com/en/tutorial/what-is-an-attachment--aGICk0RVbqKg6GYmQcWUm) for complex scenarios, such as product customization, in which you need to manage different product combinations, quantity, additional items, costs, and product inventory management.
 
@@ -33,9 +31,7 @@ This article will explain how to start using Assembly Options in your store.
 
 There are two ways to implement Assembly Options: using the [Assembly Options app](#app-assembly-options) or the native Catalog [Custom Product Attributes](#custom-product-attributes) interface.
 
-<div class="alert alert-warning">
-  <p>If you implement Assembly Options in a <a href="https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w">seller account</a>, the product customization options will be displayed to your customers at checkout. If you want the options to be displayed on the product page, you need to install the app in a <a href="https://help.vtex.com/en/tutorial/what-is-a-marketplace--680lLJTnmEAmekcC0MIea8">marketplace account</a>.</p>
-</div>
+>⚠️ If you implement Assembly Options in a [seller account](https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w), the product customization options will be displayed to your customers at checkout. If you want the options to be displayed on the product page, you need to install the app in a [marketplace account](https://help.vtex.com/en/tutorial/what-is-a-marketplace--680lLJTnmEAmekcC0MIea8).
 
 ### Assembly Options App
 
diff --git a/docs/tutorials/en/audit.md b/docs/tutorials/en/audit.md
index 40a8ece2b..efb69a273 100644
--- a/docs/tutorials/en/audit.md
+++ b/docs/tutorials/en/audit.md
@@ -22,9 +22,7 @@ To access the Audit page in the VTEX Admin, go to **Apps > Installed Apps > Audi
 * [Query events in Audit](#querying-events-in-audit)
 * [View the last queries in Audit](#viewing-the-last-queries-in-audit)
 
-<div class="alert alert-info">
-  <p>To view Audit events, you must have a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> associated with the <em>Insights Metrics</em>  <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">resource</a>.</p>
-</div>
+>ℹ️ To view Audit events, you must have a [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) associated with the *Insights Metrics*  [resource](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
 
 ![audit-ui-en (1)](https://images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/9e040c47cb3220175bf368155f438813/audit-ui-en__1_.png)
 
diff --git a/docs/tutorials/en/authentication-page.md b/docs/tutorials/en/authentication-page.md
index 36ebf0ddc..cc721368d 100644
--- a/docs/tutorials/en/authentication-page.md
+++ b/docs/tutorials/en/authentication-page.md
@@ -35,9 +35,7 @@ There are currently four ways of logging in to a VTEX store:
 | Facebook     | Can be enabled | Not available    |
 | Google       | Can be enabled | Selectable       |
 
-<div class="alert alert-info">
-At least one of the four login methods must be enabled on the Webstore tab.
-</div>
+>ℹ️ At least one of the four login methods must be enabled on the Webstore tab.
 
 ## Online store
 
diff --git a/docs/tutorials/en/authentication-with-user-and-password-on-the-rest-interface.md b/docs/tutorials/en/authentication-with-user-and-password-on-the-rest-interface.md
index d2a4f9f0e..99fd93337 100644
--- a/docs/tutorials/en/authentication-with-user-and-password-on-the-rest-interface.md
+++ b/docs/tutorials/en/authentication-with-user-and-password-on-the-rest-interface.md
@@ -15,6 +15,4 @@ legacySlug: authentication-with-user-and-password-on-the-rest-interface
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-info">
-This article has been discontinued. To authenticate and integrate with the VTEX APIs, access our article <a href="http://help.vtex.com/en/tutorial/application-keys">Application Keys</a>.
-</div>
+>ℹ️ This article has been discontinued. To authenticate and integrate with the VTEX APIs, access our article [Application Keys](http://help.vtex.com/en/tutorial/application-keys).
diff --git a/docs/tutorials/en/authentication.md b/docs/tutorials/en/authentication.md
index 0096727d4..1ae140fba 100644
--- a/docs/tutorials/en/authentication.md
+++ b/docs/tutorials/en/authentication.md
@@ -35,13 +35,9 @@ You need to configure which authentication method will be available in each cont
 | Google | The user logs in using their Google account. Check out the [Configuring login with Facebook and Google](https://help.vtex.com/en/tutorial/configurar-login-com-facebook-e-google--tutorials_513) guide for more information. | Can be enabled | Can be enabled |
 | Integration with other ID providers | The user logs in using their account from other external ID providers through an integration. Read the [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) developer guide to learn more. | Can be enabled using the OAuth protocol.  Read the [Webstore (OAuth 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) developer guide to learn more. | Can be enabled using the SAML protocol. Read the [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) developer guide to learn more. |
 
-<div class="alert alert-info">
-  <p>At least one of the login methods in the table above must be enabled for the webstore.</p>
-</div>
+>ℹ️ At least one of the login methods in the table above must be enabled for the webstore.
 
-<div class="alert alert-warning">
-  <p>You must have a valid admin <a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512">user</a> to log in to the VTEX Admin. The <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> and permissions assigned to the user specify which<a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3"> resources</a> they can use in the Admin.</p>
-</div>
+>⚠️ You must have a valid admin [user](https://help.vtex.com/en/tutorial/managing-users--tutorials_512) to log in to the VTEX Admin. The [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) and permissions assigned to the user specify which[ resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) they can use in the Admin.
 
 ### Enabling login methods
 
diff --git a/docs/tutorials/en/bank-reconciliations.md b/docs/tutorials/en/bank-reconciliations.md
index d541f52e1..05e42f008 100644
--- a/docs/tutorials/en/bank-reconciliations.md
+++ b/docs/tutorials/en/bank-reconciliations.md
@@ -21,9 +21,7 @@ The complete flow is: purchase closed with slip option on the website&gt; order
 
 As explained in our document [How long until an order whose slip was not paid is cancelled?](/hc/pt-br/articles/215033318 "How long until an order whose slip was not paid is cancelled?"), there is a deadline for the cancellation of the order, if it is not reported as paid on the Approved Payment status (manually in the OMS or by bank reconciliation). In this case, the order will remain in the Pending Payment status until it is canceled.
 
-<div class="alert alert-warning">
-The procedures in this article are not applicable to integrations that perform bank reconciliation automatically.
-</div>
+>⚠️ The procedures in this article are not applicable to integrations that perform bank reconciliation automatically.
 
 ## How to upload
 
diff --git a/docs/tutorials/en/become-a-certified-connector-partner.md b/docs/tutorials/en/become-a-certified-connector-partner.md
index 783ec71ae..b48ca0740 100644
--- a/docs/tutorials/en/become-a-certified-connector-partner.md
+++ b/docs/tutorials/en/become-a-certified-connector-partner.md
@@ -17,8 +17,7 @@ subcategory: 6riYYNZCpO8wyksi8Ksgyq
 
 The VTEX ecosystem offers countless growth opportunities. To expand its collaboration network, VTEX has developed a business plan for external marketplaces that want to become VTEX partners. 
 
-<div class="alert alert-info">
-By joining a business plan, marketplaces get a certification and become certified connectors. Learn more in our <a href="https://vtex.com/us-en/partner/">business plan</a>.</div>
+>ℹ️ By joining a business plan, marketplaces get a certification and become certified connectors. Learn more in our [business plan](https://vtex.com/us-en/partner/).
 
 In addition to providing a set of APIs and instructions to facilitate the integration process with our partners, our team will be available to assist you in your connector's development and homologation processes. We will ensure that you are making proper use of the features so that the integration is set correctly.
 
diff --git a/docs/tutorials/en/best-practices-against-virtual-attacks.md b/docs/tutorials/en/best-practices-against-virtual-attacks.md
index b2ab72f92..62e75c354 100644
--- a/docs/tutorials/en/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/en/best-practices-against-virtual-attacks.md
@@ -33,9 +33,7 @@ Anti-fraud systems specialize in analyzing ecommerce purchases to identify fraud
 
 Learn more about [anti-fraud systems](https://help.vtex.com/en/tutorial/what-is-anti-fraud--69SjFCc4rC6Ii0OMAeYAsG) and how to use them on VTEX.
 
-<div class="alert alert-warning">
-  <p>To increase security, set up your anti-fraud solution for all the payment methods available in your store.</p>
-</div>
+>⚠️ To increase security, set up your anti-fraud solution for all the payment methods available in your store.
 
 ## Protection against transaction attacks
 
diff --git a/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md b/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md
index ceaf498f9..cd4532b00 100644
--- a/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md
+++ b/docs/tutorials/en/best-practices-for-accessing-the-store-without-www.md
@@ -69,6 +69,4 @@ Some DNS providers, such as [Cloudflare](https://www.cloudflare.com/pt-br/), pro
 
 So, if you want to use a pure domain with a CDN in a specific configuration, the first step is to check whether your DNS provider supports CNAME Flattening. If so, you can configure the pure domain accordingly.
 
-<div class="alert alert-warning">
-  <p>When the DNS Flattening solution is used, it will have the same behavior as a<a href="https://help.vtex.com/en/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir"> reverse-proxy</a>. In this case, a TXT verification entry must be configured.</p>
-</div>
+>⚠️ When the DNS Flattening solution is used, it will have the same behavior as a[ reverse-proxy](https://help.vtex.com/en/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir). In this case, a TXT verification entry must be configured.
diff --git a/docs/tutorials/en/billing-module-overview.md b/docs/tutorials/en/billing-module-overview.md
index 5fbdf33b8..85d19adf3 100644
--- a/docs/tutorials/en/billing-module-overview.md
+++ b/docs/tutorials/en/billing-module-overview.md
@@ -19,9 +19,7 @@ subcategory:
 
 To access this section, click on your **profile avatar**, which can be identified by the first letter of your email address, then click on **Billing**. Select the tab you wish to visit, such as  __Contracts__, __Invoices__, __Registration Data__ and __Billing Contracts__.
 
-<div class="alert alert-info">        
-Only users with the access profiles of <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> or with <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> resources linked to their access profile can view this section of the VTEX Admin.
-  </div>     
+>ℹ️ Only users with the access profiles of [Finance](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance), [Finance Full Access](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access) or with [Billing](https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy) resources linked to their access profile can view this section of the VTEX Admin.     
 
 ![Admin v4 Faturas menu EN](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/efc4c8a58bed888f975fa5aa2b0f2fad/Admin_v4_Faturas_menu_EN.jpg)
 
diff --git a/docs/tutorials/en/bitrix24.md b/docs/tutorials/en/bitrix24.md
index 526a042f7..6e83bf35f 100644
--- a/docs/tutorials/en/bitrix24.md
+++ b/docs/tutorials/en/bitrix24.md
@@ -15,6 +15,4 @@ legacySlug: bitrix24
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/black-friday-checklist.md b/docs/tutorials/en/black-friday-checklist.md
index 57aad0a43..0449422d6 100644
--- a/docs/tutorials/en/black-friday-checklist.md
+++ b/docs/tutorials/en/black-friday-checklist.md
@@ -15,4 +15,4 @@ legacySlug: checklist-black-friday
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/black-week.md b/docs/tutorials/en/black-week.md
index 737954c6c..0c0fcff85 100644
--- a/docs/tutorials/en/black-week.md
+++ b/docs/tutorials/en/black-week.md
@@ -15,7 +15,5 @@ legacySlug: black-week
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class="alert alert-warning">
-  This is a regional exclusive content not applicable to English speaking countries.
-</div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
 
diff --git a/docs/tutorials/en/brand-registration-fields.md b/docs/tutorials/en/brand-registration-fields.md
index 1decd543f..585ca4a6b 100644
--- a/docs/tutorials/en/brand-registration-fields.md
+++ b/docs/tutorials/en/brand-registration-fields.md
@@ -19,15 +19,16 @@ To better understand the meaning of each Brand creation field, read their descri
 
 - __Name__: Name of the brand you wish create and identify a product with. This field is mandatory and limited to 150 characters.
 
-<div class="alert alert-danger">
-  <p>When filling in then brand's <b>Name</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ When filling in then brand's **Name**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 - __Replacement Words__: Alternative search terms that will lead to the created brand.The user can find the desired brand even when misspelling it. Used especially when words are of foreign origin and have a distinct spelling that is transcribed into a generic one, or when small spelling mistakes occur.
 
diff --git a/docs/tutorials/en/call-to-action-suiteshare.md b/docs/tutorials/en/call-to-action-suiteshare.md
index dde88daa1..7784ac45f 100644
--- a/docs/tutorials/en/call-to-action-suiteshare.md
+++ b/docs/tutorials/en/call-to-action-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: call-to-action
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/campaign-audiences-list.md b/docs/tutorials/en/campaign-audiences-list.md
index 3e3d8cb92..2fc6c07fb 100644
--- a/docs/tutorials/en/campaign-audiences-list.md
+++ b/docs/tutorials/en/campaign-audiences-list.md
@@ -31,9 +31,7 @@ On this page, you can perform the following actions:
 
 To create a Campaign audience, in *Promotions > Campaign audience*, you must click the `New Campaign Audience` button and follow the steps described in the article [Creating a Campaign Audience](https://help.vtex.com/en/tutorial/creating-campaign-audiences--6cnuDZJzIkIeocewAQQK4K).
 
-<div class="alert alert-warning">
-  <p>To activate the newly created campaign audience, you must associate it to a <a href="https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume">Campaign promotion</a>.</p>
-</div>
+>⚠️ To activate the newly created campaign audience, you must associate it to a [Campaign promotion](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume).
 
 ### Viewing campaign audiences
 
diff --git a/docs/tutorials/en/campaign-promotion.md b/docs/tutorials/en/campaign-promotion.md
index a08e0c890..ddf7ad694 100644
--- a/docs/tutorials/en/campaign-promotion.md
+++ b/docs/tutorials/en/campaign-promotion.md
@@ -26,9 +26,7 @@ Before creating a campaign promotion, you need to create a campaign audience to
 
 For example, if you set up a [campaign audience](https://help.vtex.com/en/tutorial/creating-campaign-audiences--6cnuDZJzIkIeocewAQQK4K) whose target audience is customers who add product A to their cart, in the campaign promotion you can configure that this audience will receive a discount on product B.
 
-<div class="alert alert-info">
-  <p>Campaign audiences and their promotions are only valid for the main store account. This option is not available for seller accounts. If a campaign audience or a campaign promotion are created on a seller account, they will not be activated.</p>
-</div>
+>ℹ️ Campaign audiences and their promotions are only valid for the main store account. This option is not available for seller accounts. If a campaign audience or a campaign promotion are created on a seller account, they will not be activated.
 
 Once the [campaign audience](https://help.vtex.com/en/tutorial/creating-campaign-audiences--6cnuDZJzIkIeocewAQQK4K) is set, go to the Admin and follow the steps below to create a campaign promotion.
 
@@ -136,9 +134,7 @@ See an example below. In this case, the promotion includes all products from the
 
 In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
 
-<div class="alert alert-warning">
-  <p>If you select <b>Apply to the following products</b> and do not fill in any of the selection criteria, the promotion will not be created and the message <b>Define eligible products or apply to all products</b> will be displayed. In this case, you must go back and fill in the selection criteria or click on <b>Apply to all products</b>.</p>
-</div>
+>⚠️ If you select **Apply to the following products** and do not fill in any of the selection criteria, the promotion will not be created and the message **Define eligible products or apply to all products** will be displayed. In this case, you must go back and fill in the selection criteria or click on **Apply to all products**.
 
 To be eligible for the promotion, products must meet all the conditions added in this section.
 
diff --git a/docs/tutorials/en/capture-form-suiteshare.md b/docs/tutorials/en/capture-form-suiteshare.md
index 70bc529e8..c2c8db5e8 100644
--- a/docs/tutorials/en/capture-form-suiteshare.md
+++ b/docs/tutorials/en/capture-form-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: capture-form
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/carrier-working-hours.md b/docs/tutorials/en/carrier-working-hours.md
index 90aa2fe39..3a761d53e 100644
--- a/docs/tutorials/en/carrier-working-hours.md
+++ b/docs/tutorials/en/carrier-working-hours.md
@@ -29,9 +29,7 @@ The way you configure working hours will influence the delivery time calculation
 1. In the [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140), in the **Business Hours** section, click the `Shipping Window` card.
 2. If you wish to activate the option `Accept purchases outside working hours`, enable the toggle switch. Otherwise, leave it deactivated.
 
-  <div class="alert alert-danger">
-To authorize the carrier to receive orders on weekends, this toggle must be marked as <code>Active</code>. Even if Saturdays and Sundays are configured as valid windows, activating the toggle is mandatory to authorize the carrier to receive orders outside business hours.
-</div>
+  >❗ To authorize the carrier to receive orders on weekends, this toggle must be marked as `Active`. Even if Saturdays and Sundays are configured as valid windows, activating the toggle is mandatory to authorize the carrier to receive orders outside business hours.
 
   <div class = "alert alert-info">
 When this option is enabled, the order <a href="https://help.vtex.com/en/tutorial/how-shipping-calculation-works--tutorials_116">shipping calculation</a> is influenced, and the period from order placement to the carrier's business time is added to the total shipping time.
diff --git a/docs/tutorials/en/category-registration-fields.md b/docs/tutorials/en/category-registration-fields.md
index 2d9513c6b..2645d2659 100644
--- a/docs/tutorials/en/category-registration-fields.md
+++ b/docs/tutorials/en/category-registration-fields.md
@@ -19,15 +19,16 @@ To better understand the meaning of each category registration field, see the fu
 
 - __Name:__ the name you want to give to the department or category you're registering. Use simple words and avoid other languages or complex writing. This field is important for SEO and must respect the 150 character limit.
 
-  <div class="alert alert-danger">
-    <p>When filling in the category <b>Name</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-    <ul>
-      <li><code>a</code></li>
-      <li><code>meta</code></li>
-      <li><code>api</code></li>
-      <li><code>admin</code></li>
-    </ul></p>
-  </div>
+  >❗ When filling in the category **Name**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> * `a`
+>
+> * `meta`
+>
+> * `api`
+>
+> * `admin`
+>     
 
 - __Similar words:__ synonyms of terms related to the name given to your department or category. "Television", for example, can have as a substitute word like "TV". This field is important to make your searches more comprehensive and must respect the 200 character limit.
 - __Category Page Title (Tag Title):__ text that is displayed in the browser tab and corresponds to the page title of the category. This field is important for SEO search engines. It only supports plain text and cannot contain HTML tags.
diff --git a/docs/tutorials/en/category-variations-and-attributes-mapping.md b/docs/tutorials/en/category-variations-and-attributes-mapping.md
index 26ebed524..fcc8ee74d 100644
--- a/docs/tutorials/en/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/en/category-variations-and-attributes-mapping.md
@@ -92,14 +92,11 @@ Given this information, continue completing the spreadsheet by following the gui
 5. __MeliValue:__ in this column you must fill values accepted by Mercado Livre, corresponding to the values used in the `VtexValue` field. In the Mercado Livre Variation Spreadsheet, go to the tab corresponding to __your country__ and look for the accepted values for each specification you filled in the `MeliEspc` column.
 <br/>_`Ex:` If you filled in `MeliEspc` with "Size" and `VtexValue` with "Small", you will see that Mercado Livre accepted value is "S"._
 
-<div class="alert alert-warning">
-<strong>Note:</strong> Once an ad is first created, <strong>it's no longer possible to change its variations</strong>. If you want to make adjustments such as changing the color, for example, it will be necessary to finish the ad in Mercado Livre and then redo the spreadsheet mapping.</div>
+>⚠️ **Note:** Once an ad is first created, **it's no longer possible to change its variations**. If you want to make adjustments such as changing the color, for example, it will be necessary to finish the ad in Mercado Livre and then redo the spreadsheet mapping.
 
-<div class="alert alert-warning">
-<strong>Note 2:</strong> Mercado Livre <strong>does not allow you to use different prices</strong> for each variation of an ad. For example, a shirt can not cost R$ 40 for size "S" and R$ 50 for size "M".</div>
+>⚠️ **Note 2:** Mercado Livre **does not allow you to use different prices** for each variation of an ad. For example, a shirt can not cost R$ 40 for size "S" and R$ 50 for size "M".
 
-<div class="alert alert-warning">
-<strong>Note 3:</strong> If the SKU does not have a certain specification (such as color, for example), you will need to register it in VTEX before completing the integration process. We recommend adding the missing attribute as a <strong>product </strong> specification. Therefore, this information will not be displayed on the website.</div>
+>⚠️ **Note 3:** If the SKU does not have a certain specification (such as color, for example), you will need to register it in VTEX before completing the integration process. We recommend adding the missing attribute as a **product ** specification. Therefore, this information will not be displayed on the website.
 
 ## Attributes
 
@@ -211,8 +208,6 @@ After filling out the spreadsheet, access __Integrations__ from the Admin menu:
 
 After the upload is completed, the integration automatically sends all products from the categories used in the spreadsheet to Mercado Livre.
 
-<div class="alert alert-warning">
-<strong>Note:</strong> products will only be sent to Mercado Livre if integration authentication has already been performed. If you have not already done so, go to the next step of the tutorial.
-</div>
+>⚠️ **Note:** products will only be sent to Mercado Livre if integration authentication has already been performed. If you have not already done so, go to the next step of the tutorial.
 
 You have completed the fifth step of the integration. Now we are moving to the last step, where we will authorize Mercado Livre integration in VTEX panel.
diff --git a/docs/tutorials/en/change-seller-of-an-vtex-sales-app-order-beta.md b/docs/tutorials/en/change-seller-of-an-vtex-sales-app-order-beta.md
index 9123c6880..766243e7d 100644
--- a/docs/tutorials/en/change-seller-of-an-vtex-sales-app-order-beta.md
+++ b/docs/tutorials/en/change-seller-of-an-vtex-sales-app-order-beta.md
@@ -15,6 +15,4 @@ legacySlug: change-seller-of-an-instore-order-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
index b44617708..f2b8d02a9 100644
--- a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -20,10 +20,8 @@ At VTEX, stores can manually set the price of an item (SKU) available in the Che
 - **Access Profile**: Owner (Admin Super) or Call Center Operator (Telesales) 
 - **Permission**: Shopping Cart Full Access
 
-<div class="alert alert-warning">
-The steps below must be performed on the <i>myvtex</i> domain of each store
- ({accountName}.myvtex.com.br).
-</div>
+>⚠️ The steps below must be performed on the <i>myvtex</i> domain of each store
+>  ({accountName}.myvtex.com.br).
 
 ## Changing the item price
 
diff --git a/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
index 1a9a60afb..e5088b1ad 100644
--- a/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/en/changing-default-system-texts-displayed-in-the-store.md
@@ -47,9 +47,7 @@ To do this dynamically, I can change the text of the `topbarSaudacao` key to the
 
 That is, I'm using the variables `preposicaonomeloja2` and `nomeloja`.
 
-<div class="alert alert-warning">
-When using variables to compose a text, replace the <code>#</code> symbol with <code>@</code>. That is, <b>#variable#</b> becomes <b>@variable@</b>.
-</div>
+>⚠️ When using variables to compose a text, replace the `#` symbol with `@`. That is, **#variable#** becomes **@variable@**.
 
 ![textos-importantes en](https://images.ctfassets.net/alneenqid6w5/3ck7V4j6wgygm0qE2ia2m8/ec2d596e8fbee37f53d38568d797a401/textos_importantes_en.png)
 ![exemplos-textos-importantes en](https://images.ctfassets.net/alneenqid6w5/3qJmU7aPIcUowc6SkaYoSS/4c7d666cf29ef651c19ee837c9f42a75/3_en.png)
diff --git a/docs/tutorials/en/changing-items-from-a-complete-order.md b/docs/tutorials/en/changing-items-from-a-complete-order.md
index e144a15b5..413c0ab56 100644
--- a/docs/tutorials/en/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/en/changing-items-from-a-complete-order.md
@@ -22,9 +22,7 @@ There are two ways to make a change to an order:
 * [VTEX Admin:](#how-to-change-order-items) it is only possible if the order status is `Handling Shipping`.
 * [Order change API:](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes) in addition to changing items, you can create discounts and change the order price. You can only change it if the order status in the order API is `handling` or `waiting-for-fulfillment`.
 
-<div class="alert alert-warning">
-After it has been changed, the customer will receive an email notification if the <code>Change of information</code> template (<a href="https://help.vtex.com/en/tutorial/order-transactional-email-templates--3g2S2kqBOoSGcCaqMYK2my">transactional email template related to the order</a>) is enabled in Message Center. The customer receives the messages with the information that was filled in the item change form.
-</div>
+>⚠️ After it has been changed, the customer will receive an email notification if the `Change of information` template ([transactional email template related to the order](https://help.vtex.com/en/tutorial/order-transactional-email-templates--3g2S2kqBOoSGcCaqMYK2my)) is enabled in Message Center. The customer receives the messages with the information that was filled in the item change form.
 
 ## Restrictions
 
diff --git a/docs/tutorials/en/changing-the-total-cost-of-the-order.md b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
index c5de941a9..4bf4bed62 100644
--- a/docs/tutorials/en/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
@@ -17,9 +17,7 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 The [Order Details page](https://help.vtex.com/en/tutorial/order-details-page-beta--2Y75n54Cc9VizrlG1N6ZNl) allows you to change the final cost of orders that have not yet been invoiced. This occurs when there are discounts or additions to the order total.
 
-<div class="alert alert-warning">
-Remember that this feature is only available for orders whose status is <code>Preparing delivery</code>.
-</div>
+>⚠️ Remember that this feature is only available for orders whose status is `Preparing delivery`.
 
 To make the change, follow the steps below:
 
diff --git a/docs/tutorials/en/chat.md b/docs/tutorials/en/chat.md
index 2021a4869..c662fe8b2 100644
--- a/docs/tutorials/en/chat.md
+++ b/docs/tutorials/en/chat.md
@@ -15,6 +15,4 @@ legacySlug: chat
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/checking-for-errors-or-problems-in-a-transaction.md b/docs/tutorials/en/checking-for-errors-or-problems-in-a-transaction.md
index e02ace0a9..f41fadae0 100644
--- a/docs/tutorials/en/checking-for-errors-or-problems-in-a-transaction.md
+++ b/docs/tutorials/en/checking-for-errors-or-problems-in-a-transaction.md
@@ -21,9 +21,7 @@ The steps of a transaction are logged in a timeline, with the most recent intera
 
 VTEX gateway can communicate with acquirers, sub-acquirers, anti-frauds and other gateways. The __status changes in the transaction__ and the __partner's reply messages__ are displayed in boxes on the transaction details screen.
 
-<div class="alert alert-info">
-You can <a href="https://help.vtex.com/en/faq/credit-card-basic-payment-flow">click here</a> to find out how the flow of a credit card transaction works. Also visit <a href="https://help.vtex.com/en/faq/registered-ticket-flow">our article</a> with the basic scheme of a bank slip transaction.
-</div>
+>ℹ️ You can [click here](https://help.vtex.com/en/faq/credit-card-basic-payment-flow) to find out how the flow of a credit card transaction works. Also visit [our article](https://help.vtex.com/en/faq/registered-ticket-flow) with the basic scheme of a bank slip transaction.
 
 ## Check the transaction status
 
diff --git a/docs/tutorials/en/checkout-vtex-overview.md b/docs/tutorials/en/checkout-vtex-overview.md
index dd6bf5758..b03b63eaa 100644
--- a/docs/tutorials/en/checkout-vtex-overview.md
+++ b/docs/tutorials/en/checkout-vtex-overview.md
@@ -37,9 +37,7 @@ Every time a customer changes something in the cart (adds or removes items), or
 
 ![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/1c2b515127000db8b88c3a2cfa5996d0/Checkout_Overview_EN.png)
 
-<div class="alert alert-info">
-If one or more items selected by the customer are eligible for delivery by a <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#">Seller white label</a>, the seller responsible for delivering the items will be chosen based on shipping simulations, as shown in the right side of the picture. Learn more in <a href="https://help.vtex.com/en/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Selecting white label sellers</a>.
-</div>
+>ℹ️ If one or more items selected by the customer are eligible for delivery by a [Seller white label](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#), the seller responsible for delivering the items will be chosen based on shipping simulations, as shown in the right side of the picture. Learn more in [Selecting white label sellers](https://help.vtex.com/en/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#).
 
 ## VTEX Checkout features
 
@@ -55,8 +53,6 @@ Here are some highlights from the main features of the VTEX Checkout module:
 
 The VTEX Checkout module currently runs two versions: **Checkout v5** and **Checkout v6**.
 
-<div class="alert alert-info">
-  <b>Checkout v5</b> is no longer being updated or receiving direct operational support. Therefore, we recommend using <b>Checkout v6</b> for your store.
-</div>
+>ℹ️ **Checkout v5** is no longer being updated or receiving direct operational support. Therefore, we recommend using **Checkout v6** for your store.
 
 For more information about Checkout settings and APIs, please go to [Checkout Overview on Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/checkout-overview).
diff --git a/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md b/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
index 8b7ada43e..b3844dfb8 100644
--- a/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
+++ b/docs/tutorials/en/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
@@ -28,9 +28,7 @@ The VTEX platform allows creating different store architectures starting from a
 
 This article describes the differences between the multistore and additional environment architectures to help you choose the best one for different scenarios.
 
-<div class="alert alert-info">
-For marketplace architectures, you can also  <a href="https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Choose between a standard account, franchise account, and Seller Portal</a>  or use the <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory </a> configuration.
-</div>
+>ℹ️ For marketplace architectures, you can also  [Choose between a standard account, franchise account, and Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78)  or use the [Multilevel Omnichannel Inventory ](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) configuration.
 
 ## Comparing multistore and additional environment architectures
 
diff --git a/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
index 6e4f94144..c71eaa5a5 100644
--- a/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -23,7 +23,7 @@ There are three types of accounts on the VTEX platform and each one allows you t
 - **Franchise account:** It is associated with a standard account, inheriting its catalog. [Franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) can configure their own logistics, payment and prices, and use the VTEX platform modules partially. This type of seller is called a [white label seller](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 - **Seller Portal:** The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) is a feature of the VTEX platform that allows sellers to connect and sell their products on marketplaces of the VTEX ecosystem, regardless of whether the seller already has a VTEX account. The Seller Portal allows partial access to the platform modules, and the seller type can be standard or [white label seller](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 
-<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+>⚠️ The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.
 
 The table below presents the main use cases for each account type:
 
diff --git a/docs/tutorials/en/cms-folder-structure.md b/docs/tutorials/en/cms-folder-structure.md
index 3b1638a52..385ce9a05 100644
--- a/docs/tutorials/en/cms-folder-structure.md
+++ b/docs/tutorials/en/cms-folder-structure.md
@@ -37,9 +37,7 @@ See below these basic folders in the CMS:
 
 These folders come by default in the environment of all VTEX stores.
 
-<div class="alert alert-danger">
-  <p>The names of the required folders must <b>not</b> be edited. This can compromise the proper functioning of the store and prevent purchases from being made.</p>
-</div>
+>❗ The names of the required folders must **not** be edited. This can compromise the proper functioning of the store and prevent purchases from being made.
 
 Since folders refer to dynamic pages, their names don't appear on the customer's navigation. In other words, the fact that editing the names is banned does not affect the final text of your URLs, nor the internationalization of your site.
 
@@ -55,9 +53,7 @@ These are:
 
 For these two folders, what matters is the control or placeholder that reads their content. Their names can be freely edited.
 
-<div class="alert alert-warning">
-Since they are private folders, <code>/account</code> and <code>/account/orders</code> <b>must require authentication</b>. See <a href="http://help.vtex.com/en/tutorial/requering-authentication-on-store-pages">in this article</a> how to ensure they are configured to ask for user authentication.
-</div>
+>⚠️ Since they are private folders, `/account` and `/account/orders` **must require authentication**. See [in this article](http://help.vtex.com/en/tutorial/requering-authentication-on-store-pages) how to ensure they are configured to ask for user authentication.
 
 ## Useful folders
 
diff --git a/docs/tutorials/en/collection-highlight-control.md b/docs/tutorials/en/collection-highlight-control.md
index 4579b4cad..0e9ffb2c3 100644
--- a/docs/tutorials/en/collection-highlight-control.md
+++ b/docs/tutorials/en/collection-highlight-control.md
@@ -39,6 +39,4 @@ You can then customize the CSS to define how the `flag {CollectionName}` class w
 
 This feature can be used, for example, to make products in a collection called "Launch" always appear with a flag highlighting that they are new to the store. When you add the control to the category page template, for example, every product in the Launch collection that appears on a category page will be shown with that highlight.
 
-<div class="alert alert-warning">
-Remember that if it's a product page, the control that should be used is <code>&lt;vtex.cmc:HightLight/&gt;</code>. If it's a shop window page, you should use the <code>$product.HightLight</code> control.
-</div>
+>⚠️ Remember that if it's a product page, the control that should be used is `&lt;vtex.cmc:HightLight/&gt;`. If it's a shop window page, you should use the `$product.HightLight` control.
diff --git a/docs/tutorials/en/como-criar-usuario-webservice.md b/docs/tutorials/en/como-criar-usuario-webservice.md
index 6ae11fa55..198913d7b 100644
--- a/docs/tutorials/en/como-criar-usuario-webservice.md
+++ b/docs/tutorials/en/como-criar-usuario-webservice.md
@@ -15,9 +15,11 @@ legacySlug: como-criar-usuario-webservice
 subcategory: 63DHe3VQEEE6Uuua8gIs2M
 ---
 
-<div class="alert alert-danger"><p>Attention: Only SOAP methods related to the <strong>catalog</strong> are valid.</p>
-<p><strong> All the other Web Service methods will be deprecated as of 02/28/2017.</strong></p>
-<p>Use the equivalent REST APIs, available in our <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Attention: Only SOAP methods related to the **catalog** are valid.
+>
+> ** All the other Web Service methods will be deprecated as of 02/28/2017.**
+>
+> Use the equivalent REST APIs, available in our [Developer Docs](//help.vtex.com/developer-docs/).
 
 The creation of credentials for integrations with the Web Service must be done by License Manager, with the functionality of appKey and appToken.
 
diff --git a/docs/tutorials/en/como-funciona-a-integracao-da-netshoes.md b/docs/tutorials/en/como-funciona-a-integracao-da-netshoes.md
index d74657334..06823dd41 100644
--- a/docs/tutorials/en/como-funciona-a-integracao-da-netshoes.md
+++ b/docs/tutorials/en/como-funciona-a-integracao-da-netshoes.md
@@ -54,9 +54,7 @@ When the specifications are successfully sent for the first time, Netshoes recei
 
 _`Ex:` If the product description is changed, the integration will not update the description inside the marketplace._
 
-<div class="alert alert-warning">
-Note: The product can not be deleted in the Netshoes panel, so it may be sent by the integration again.
-</div>
+>⚠️ Note: The product can not be deleted in the Netshoes panel, so it may be sent by the integration again.
 
 At Netshoes, products have two possible statuses:
 - __Active:__ available for sale
@@ -76,9 +74,7 @@ Once the cataloging process is finished in Netshoes, the integration automatical
 
 After the products receive the first stock load, the update is made SKU by SKU whenever there's a stock change in VTEX.
 
-<div class="alert alert-warning">
-<strong>Note:</strong> The inventory data sent to Netshoes is registered to our system for only <strong>3 months</strong>.
-</div>
+>⚠️ **Note:** The inventory data sent to Netshoes is registered to our system for only **3 months**.
 
 ## 3 - Prices
 
@@ -94,11 +90,11 @@ _` Ex1:` benefit of 10% discount for a certain category_
 
 _`Ex2:` SKU X is $ 10.00 in the sales policy used in Netshoes and has a fixed price of $ 15.00 for the same sales policy. The integration will send $ 15,00.
 
-<div class="alert alert-warning">
-Note: since the payment method is made in the marketplace, the payment rules are determined by it. Because of this, we can't send differentiated prices depending on the payment method.
-<br />
-<em>Ex: If there are interests for installment payments configured in VTEX, the price sent will still be the one returned by the fulfillment simulation.</em>
-</div>
+>⚠️ Note: since the payment method is made in the marketplace, the payment rules are determined by it. Because of this, we can't send differentiated prices depending on the payment method.
+>
+>
+> 
+> *Ex: If there are interests for installment payments configured in VTEX, the price sent will still be the one returned by the fulfillment simulation.*
 
 ## 4 - Benefits
 
@@ -113,9 +109,7 @@ Only benefits that can be calculated in the fulfillment simulation are applied.
 | Maximum Shipping | - | Type of Shipping |
 | Free Shipping | - | - |
 
-<div class="alert alert-info">
-It is not possible to apply <strong>any</ strong> condition type in benefits whose fields were filled in as <strong>-</ strong>, that is, no condition will be taken into account in the integration.
-</div>
+>ℹ️ It is not possible to apply <strong>any</ strong> condition type in benefits whose fields were filled in as <strong>-</ strong>, that is, no condition will be taken into account in the integration.
 
 ## 5 - Order Flow
 
@@ -127,15 +121,19 @@ When an order is made in the marketplace there are some points that influence it
 
 In this integration there are two points that will influence the delivery: __Shipping Calculation__ and __Time of Shipping Preparation__. The sum of the two will be the __Total Delivery Time__.
 
-<div class="alert alert-info">
-Ex:
-<br />
-Normal Shipping = 3 days
-<br />
-Cost Time = 2 days
-<br />
-Total Delivery Time = 5 days
-</div>
+>ℹ️ Ex:
+>
+>
+> 
+> Normal Shipping = 3 days
+>
+>
+> 
+> Cost Time = 2 days
+>
+>
+> 
+> Total Delivery Time = 5 days
 
 - __Shipping__
 
@@ -147,46 +145,78 @@ The store can also register a __contingency table__ in Netshoes. Thus, if by any
 
 The shipping preparation time is based on the sum of the `Cost Time` field in the Inventory and the `Cost Time` at the warehouse dock. We send in bulk the same preparation time for all products.
 
-<div class="alert alert-info">
-Ex:
-<br />
-<strong>Inventory A</strong>
-<br />
-- Warehouse Dock 1: Cost Time = 3 days
-<br />
-<strong>Inventory B</strong>
-<br />
-- Warehouse Dock 1: Cost Time = 5 days
-<br />
-<br />
-<strong>Warehouse Dock 1:</strong>
-<br />
-- Cost Time = 2 days
-<br />
-<br />
-An order with Shipping Time = 3 days will have a different Total Delivery Time depending on where the product will depart from.
-<br />
-<br />
-<strong>Leaving Inventory A:</strong>
-<br />
-- Preparation time = 3 + 2 (warehouse dock 1) = 5 days
-<br />
-- Shipping time = 3 days
-<br />
-- Total delivery time = 8 days
-<br />
-<strong>Exiting inventory B:</strong>
-<br />
-- Preparation time = 5 + 2 (warehouse dock 1) = 7 days
-<br />
-- Shipping time = 3 days
-<br />
-- Total delivery time = 10 days
-</div>
-
-<div class="alert alert-warning">
-Note: In case of using the contingency table to calculate shipping, Netshoes does not query VTEX. In this case, the only factor that will be taken into account for <strong>Total Delivery Time</strong>, will be the <strong>Shipping</ strong> provided by them, ignoring the <strong>Preparation Time</strong>. You should be careful about this, as it may lead to discrepancies in the <strong>Total Delivery Time</strong>.
-</div>
+>ℹ️ Ex:
+>
+>
+> 
+> **Inventory A**
+>
+>
+> 
+> - Warehouse Dock 1: Cost Time = 3 days
+>
+>
+> 
+> **Inventory B**
+>
+>
+> 
+> - Warehouse Dock 1: Cost Time = 5 days
+>
+>
+> 
+>
+>
+> 
+> **Warehouse Dock 1:**
+>
+>
+> 
+> - Cost Time = 2 days
+>
+>
+> 
+>
+>
+> 
+> An order with Shipping Time = 3 days will have a different Total Delivery Time depending on where the product will depart from.
+>
+>
+> 
+>
+>
+> 
+> **Leaving Inventory A:**
+>
+>
+> 
+> - Preparation time = 3 + 2 (warehouse dock 1) = 5 days
+>
+>
+> 
+> - Shipping time = 3 days
+>
+>
+> 
+> - Total delivery time = 8 days
+>
+>
+> 
+> **Exiting inventory B:**
+>
+>
+> 
+> - Preparation time = 5 + 2 (warehouse dock 1) = 7 days
+>
+>
+> 
+> - Shipping time = 3 days
+>
+>
+> 
+> - Total delivery time = 10 days
+
+>⚠️ Note: In case of using the contingency table to calculate shipping, Netshoes does not query VTEX. In this case, the only factor that will be taken into account for **Total Delivery Time**, will be the **Shipping</ strong> provided by them, ignoring the <strong>Preparation Time**. You should be careful about this, as it may lead to discrepancies in the **Total Delivery Time**.
 
 #### Price/Availability:
 
diff --git a/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md b/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
index d562708d1..7c35442b6 100644
--- a/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
+++ b/docs/tutorials/en/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
@@ -31,8 +31,6 @@ See below the relationship between the folder in the CMS and the store's source
 
 ![CommerceContext](https://images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
 
-<div class="alert alert-info">
-This line of code is always commented out. Therefore, it has only informative function. That is, it does not take any action.
-</div>
+>ℹ️ This line of code is always commented out. Therefore, it has only informative function. That is, it does not take any action.
 
 This information is useful, for example, to know which folder the search for a certain term is returning in your store.
diff --git a/docs/tutorials/en/conditions-builder-usage-examples.md b/docs/tutorials/en/conditions-builder-usage-examples.md
index aa910f214..c5e78a33f 100644
--- a/docs/tutorials/en/conditions-builder-usage-examples.md
+++ b/docs/tutorials/en/conditions-builder-usage-examples.md
@@ -27,9 +27,8 @@ UTM (Marketing tag) is an information that relates to the origin of the customer
 
 ![utm_source_english](https://images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
 
-<div class="alert alert-warning"><strong>Note: </strong>
-It is possible that your store employs customizations and thereby the UTM information contained in the URL is not being passed on to our system. If you use JavaScript customization, read the article <a href="https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho">Por que as utms não estão sendo aplicadas ao carrinho</a>
-</div>
+>⚠️ **Note: **
+> It is possible that your store employs customizations and thereby the UTM information contained in the URL is not being passed on to our system. If you use JavaScript customization, read the article [Por que as utms não estão sendo aplicadas ao carrinho](https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho)
 
 ### utm_source
 
diff --git a/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md b/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
index 4d367904a..0fd99024d 100644
--- a/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
+++ b/docs/tutorials/en/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
@@ -15,9 +15,7 @@ legacySlug: configuration-errors-in-mercado-libre-accounts-with-multiple-officia
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-If you have official stores in Mercado Libre, this documentation may be relevant. Mercado Libre has its own parameters to certify sellers as official stores. For more information, please contact your Mercado Libre consultant.
-</div>
+>ℹ️ If you have official stores in Mercado Libre, this documentation may be relevant. Mercado Libre has its own parameters to certify sellers as official stores. For more information, please contact your Mercado Libre consultant.
 
 When a [seller](https://help.vtex.com/en/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) integrates their [subaccounts](https://help.vtex.com/en/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK?&utm_source=autocomplete) with a Mercado Libre user’s official stores, it may cause an error in product import.
 
diff --git a/docs/tutorials/en/configure-cartman.md b/docs/tutorials/en/configure-cartman.md
index 5960eb1a1..a95150b10 100644
--- a/docs/tutorials/en/configure-cartman.md
+++ b/docs/tutorials/en/configure-cartman.md
@@ -34,9 +34,7 @@ This article will cover the following topics:
   - [Define marketing data](#define-marketing-data)
 - [Disable Cartman](#disable-cartman) 
 
-<div class="alert alert-warning">
-  Only the merchant has access to <b>Cartman</b>. Its features are not available for use by users in a store.
-</div>
+>⚠️ Only the merchant has access to **Cartman**. Its features are not available for use by users in a store.
 
 ## Activate Cartman manually
 
@@ -106,7 +104,5 @@ Cartman can be deactivated at any time as required by the merchant. To disable i
 2. In the lower right corner of the screen, click the button  <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
 3. At the bottom of Cartman's menu, click  `Disable Cartman`.
 
-<div class="alert alert-info">
-  If you want to reactivate <b>Cartman</b>, re-add the query string <code>?cartman=on</code> in one of your store's Checkout pages. In this way, the blue icon will be available again in the lower right corner of the page.
-</div>
+>ℹ️ If you want to reactivate **Cartman**, re-add the query string `?cartman=on` in one of your store's Checkout pages. In this way, the blue icon will be available again in the lower right corner of the page.
 
diff --git a/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
index 1e8b26a32..8c69fa5e6 100644
--- a/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/en/configure-employee-benefits-using-master-data-clusters.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 In VTEX, a benefit or discount can be applied to a group of customers. This group of customers can be defined by properties that they have in common. 
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 This article shows how to configure a benefit for employees. It is considered that the employees are a group of customers, so they are identified using Master Data clusters.
 
diff --git a/docs/tutorials/en/configure-seller-regionalization.md b/docs/tutorials/en/configure-seller-regionalization.md
index a3d97ef69..60154f12a 100644
--- a/docs/tutorials/en/configure-seller-regionalization.md
+++ b/docs/tutorials/en/configure-seller-regionalization.md
@@ -43,6 +43,4 @@ To activate **Region** in your store, you need to perform the following steps:
 1. [Setting up price and availability of SKUs by Region](https://help.vtex.com/en/tutorial/setting-up-price-and-availability-of-skus-by-region--12ne58BmvYsYuGsimmugoc#)
 2. [Enable Region functionality](https://developers.vtex.com/docs/guides/enable-the-region-for-skus)
 
-<div class="alert alert-info">
-  <b>Region</b> is currently available for use in all VTEX stores in v2. Learn more in <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
-</div>
+>ℹ️ **Region** is currently available for use in all VTEX stores in v2. Learn more in <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
diff --git a/docs/tutorials/en/configure-template-in-smartcheckout-update.md b/docs/tutorials/en/configure-template-in-smartcheckout-update.md
index 3c6b90fa1..6377452c5 100644
--- a/docs/tutorials/en/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/en/configure-template-in-smartcheckout-update.md
@@ -19,9 +19,7 @@ The __Portal__ is used to render __Checkout__ (cart, personal data, address, pay
 
 The __Checkout__ module in the Admin, displays the sites that are registered for your account. Through it, it is also possible to create a new website, edit and configure information about existing websites.
 
-<div class="alert alert-info">
-Each registered site corresponds to a multidomain (if the account has contracted multidomains). For accounts that do not use multidomains, it is not necessary to register more than one site in this module. Learn more at <a href="https://help.vtex.com/en/tutorial/como-criar-multiloja-multidominio--tutorials_510#">Create a multistore/multidomain</a>.
-</div>
+>ℹ️ Each registered site corresponds to a multidomain (if the account has contracted multidomains). For accounts that do not use multidomains, it is not necessary to register more than one site in this module. Learn more at [Create a multistore/multidomain](https://help.vtex.com/en/tutorial/como-criar-multiloja-multidominio--tutorials_510#).
 
 ## Creating a new website
 
@@ -100,9 +98,7 @@ The HTML code filled in the template corresponds to what will appear on the __ch
 
 Of the available templates, the only ones that cannot be changed are __vtex-checkout__ and __vtex-orderPlaced__. These correspond to the native functioning of the platform, rendering the main content of the __checkout__ and __order placed__ pages.
 
-<div class="alert alert-warning">
-Javascripts included directly in any Portal templates will be ignored by the platform. The reason behind this is that only scripts that originated in Google Tag Manager are accepted by <a href="https://help.vtex.com/en/tutorial/smartcheckout-preenchimento-automatico-de-dados-do-cliente--2Nuu3xAFzdhIzJIldAdtan#">SmartCheckout</a>. aTherefore, whenever you need to customize something (or even to insert specific tags) using javascript, do this through <a href="https://help.vtex.com/en/tutorial/integration-with-google-tag-manager--frequentlyAskedQuestions_616#">Google Tag Manager</a>.
-</div>
+>⚠️ Javascripts included directly in any Portal templates will be ignored by the platform. The reason behind this is that only scripts that originated in Google Tag Manager are accepted by [SmartCheckout](https://help.vtex.com/en/tutorial/smartcheckout-preenchimento-automatico-de-dados-do-cliente--2Nuu3xAFzdhIzJIldAdtan#). aTherefore, whenever you need to customize something (or even to insert specific tags) using javascript, do this through [Google Tag Manager](https://help.vtex.com/en/tutorial/integration-with-google-tag-manager--frequentlyAskedQuestions_616#).
 
 ### Examples of how to fill out templates
 
diff --git a/docs/tutorials/en/configuring-a-data-entity.md b/docs/tutorials/en/configuring-a-data-entity.md
index e8b2d55f1..9ede02d77 100644
--- a/docs/tutorials/en/configuring-a-data-entity.md
+++ b/docs/tutorials/en/configuring-a-data-entity.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-06-21-at-09-16-27
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/configuring-a-marketplace-trade-policy.md b/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
index a51a24038..8c1d62719 100644
--- a/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/en/configuring-a-marketplace-trade-policy.md
@@ -77,9 +77,7 @@ Sellers can restrict the availability of products in their catalog by using diff
 
 This configuration can be done in the VTEX *Catalog*, when [adding products](https://help.vtex.com/en/tutorial/cadastrando-produtos--tutorials_2567), by indicating which trade policies are associated with it. If no restrictions are set when adding the product, it will be available in all trade policies.
 
-<div class="alert alert-warning">
-We do not recommend attaching trade policies to collections, when determining the product assortment, especially for external marketplaces. When a product is withdrawn from the collection associated to a trade policy, the VTEX system does not warn the marketplace of that update, making the product still available in the marketplace.
-  </div>
+>⚠️ We do not recommend attaching trade policies to collections, when determining the product assortment, especially for external marketplaces. When a product is withdrawn from the collection associated to a trade policy, the VTEX system does not warn the marketplace of that update, making the product still available in the marketplace.
 
 ![EN Catálogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/43607a48ab2590d2f58a50c8281f4879/EN_Cat__logo_Politica.jpg)
 
diff --git a/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md b/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md
index 3bcc8b0b5..d409134d2 100644
--- a/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md
+++ b/docs/tutorials/en/configuring-a-pricing-rule-for-a-sales-policy.md
@@ -15,9 +15,7 @@ legacySlug: setting-a-pricing-rule-for-a-sales-policy
 subcategory: wUepkh8pzimEywO8oGUIc
 ---
 
-<div class="alert alert-info">
-This article refers to the latest version of VTEX Pricing. If your store is not yet in this new version, you can request the migration by contacting our support team.
-</div>
+>ℹ️ This article refers to the latest version of VTEX Pricing. If your store is not yet in this new version, you can request the migration by contacting our support team.
 
 A __pricing rule__ is a set of conditions that determine the prices for a certain sales policy.
 
diff --git a/docs/tutorials/en/configuring-a-santander-registered-boleto.md b/docs/tutorials/en/configuring-a-santander-registered-boleto.md
index 0fdbe1cb6..8fe2da29f 100644
--- a/docs/tutorials/en/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/en/configuring-a-santander-registered-boleto.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-12-04-at-07-04-02
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/configuring-access-profiles-old.md b/docs/tutorials/en/configuring-access-profiles-old.md
index 4ffb6d882..5dcda8467 100644
--- a/docs/tutorials/en/configuring-access-profiles-old.md
+++ b/docs/tutorials/en/configuring-access-profiles-old.md
@@ -34,9 +34,7 @@ Here are some useful profiles:
 - __Financeiro:__ Gives access to the Financial submodule, within the License Manager, letting the user see payment tickets and tax invoices relating to payment of the VTEX service.
 - __Webservice:__ Allows users to access web service methods, used in some integrations (mostly related to the Catalog).
 
-<div class="alert alert-warning"> 
-<strong>Atention</strong>: Telephone sales (referred above as Televendas) profiles block access to the E-commerce module. In other words, you cannot access the products register for example. If it is necessary to access this module, the user should work with two different user IDs.
-</div>
+>⚠️ **Atention**: Telephone sales (referred above as Televendas) profiles block access to the E-commerce module. In other words, you cannot access the products register for example. If it is necessary to access this module, the user should work with two different user IDs.
 
 ## Creating new profiles
 
diff --git a/docs/tutorials/en/configuring-access-without-www.md b/docs/tutorials/en/configuring-access-without-www.md
index 72f18ab88..86afd45a3 100644
--- a/docs/tutorials/en/configuring-access-without-www.md
+++ b/docs/tutorials/en/configuring-access-without-www.md
@@ -41,9 +41,7 @@ You can also use DNS redirection, as provided by several services, including dom
 
 To perform a DNS redirection in a simple manner, there are instructions below on how to use the [redirect.center](http://redirect.center/) service.
 
-<div class="alert alert-warning">
-Note that Direcionar is not a VTEX service and does not work with HTTPS. There are other similar services, but VTEX does not recommend any specific one. VTEX is not responsible for problems caused by external redirect services.
-</div>
+>⚠️ Note that Direcionar is not a VTEX service and does not work with HTTPS. There are other similar services, but VTEX does not recommend any specific one. VTEX is not responsible for problems caused by external redirect services.
 
 See this other article to learn how to [configure redirection from other addresses](https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ).
 
diff --git a/docs/tutorials/en/configuring-affiliates.md b/docs/tutorials/en/configuring-affiliates.md
index 0ab5925dc..f7e2419b4 100644
--- a/docs/tutorials/en/configuring-affiliates.md
+++ b/docs/tutorials/en/configuring-affiliates.md
@@ -35,9 +35,7 @@ To create a new affiliate ID, follow the steps below:
 
 > Notice that the value **{NameOfMarketplace}** must be altered using the name of the marketplace account, while the value **{SellerId}** must be changed to the ID of the seller registered by the marketplace.
 
-> <div class="alert alert-danger">
-The <strong>{SellerId}</strong> value is <em>case sensitive</em>. In that way, it should be written in the URL exactly the same way it is registered in the marketplace.
-</div>
+> >❗ The **{SellerId}** value is *case sensitive*. In that way, it should be written in the URL exactly the same way it is registered in the marketplace.
 
 > For [external marketplaces](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrating-with-an-external-marketplace), fill in the value: `https://{endpointDoAfiliado}/api/notification/`.   
 
diff --git a/docs/tutorials/en/configuring-affirm.md b/docs/tutorials/en/configuring-affirm.md
index b1dc65f38..405c1b9f6 100644
--- a/docs/tutorials/en/configuring-affirm.md
+++ b/docs/tutorials/en/configuring-affirm.md
@@ -19,9 +19,7 @@ subcategory:
 
 When customers make a purchase and choose Affirm as a payment method, they will undergo a credit analysis. Based on their score, the tool will release the amount to pay for that transaction. After that, the client will pay the amount owed (the amount borrowed plus the interest, as defined at the time of the purchase) directly to Affirm.
 
-<div class="alert alert-warning">
-You can install the Affirm app using VTEX IO, a low-code development platform that allows programmers to develop applications and new components for VTEX stores. Access the documentation <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-install">Installing VTEX IO's CLI</a> and download the platform and its components before moving on to the next steps.
-</div>
+>⚠️ You can install the Affirm app using VTEX IO, a low-code development platform that allows programmers to develop applications and new components for VTEX stores. Access the documentation [Installing VTEX IO's CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-install) and download the platform and its components before moving on to the next steps.
 
 To configure Affirm, you have to:
 
diff --git a/docs/tutorials/en/configuring-banners.md b/docs/tutorials/en/configuring-banners.md
index 003dc18c6..3c6aa06e8 100644
--- a/docs/tutorials/en/configuring-banners.md
+++ b/docs/tutorials/en/configuring-banners.md
@@ -25,9 +25,7 @@ To set up a banner, follow the steps below:
 
 After configuring the banner, you have to add it to a page on your store. To do that, follow the steps described in the [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner) guide.
 
-<div class="alert alert-info">
-<p> This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: Multilanguage settings (Beta)</a>.</p>
-</div>
+>ℹ️ This feature is available on VTEX Intelligent Search Multilanguage. For more information, please refer to our article [VTEX Intelligent Search: Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#banners).
 
 ![banner-form-en](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/306bbd26bcadab589aeabe91903b0bcc/image.png)
 
diff --git a/docs/tutorials/en/configuring-carriers-cut-off-time.md b/docs/tutorials/en/configuring-carriers-cut-off-time.md
index 21478f413..e7515d4bc 100644
--- a/docs/tutorials/en/configuring-carriers-cut-off-time.md
+++ b/docs/tutorials/en/configuring-carriers-cut-off-time.md
@@ -15,9 +15,7 @@ legacySlug: setting-the-carriers-cut-off-time
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-warning">
-Warning: This documentation is being updated to reflect the concept change from Dashboards to <a href="https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">Shipping strategy</a>.
-</div>
+>⚠️ Warning: This documentation is being updated to reflect the concept change from Dashboards to [Shipping strategy](https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 The carriers, which are called Shipping Policies in the Admin, are the companies responsible for distributing the products sold through an e-commerce platform. It is common for a store to have multiple carriers associated with it. This is because the carriers’ operation and fleet profile **vary according to the route, shipping time, and type of product** that it will deliver.
 
diff --git a/docs/tutorials/en/configuring-cielo-acquirer.md b/docs/tutorials/en/configuring-cielo-acquirer.md
index acda49c53..ba15e7fee 100644
--- a/docs/tutorials/en/configuring-cielo-acquirer.md
+++ b/docs/tutorials/en/configuring-cielo-acquirer.md
@@ -40,9 +40,7 @@ To configure Cielo, follow the steps below.
     - __BpmpiAuthNotifyOnly:__ Choose whether the card transaction will be submitted in "notification only" mode. This option is only valid for Mastercard cards. In this mode, the authentication process will not be triggered, but the data will be submitted to the card company.
     - __BpmpiAuthSuppresschallenge:__ Choose whether the challenge must be suppressed when it exists. If a transaction is authorized after ignoring the challenge, the liability rests with the merchant.
 
-<div class="alert alert-warning">
-<strong>Warning</strong>: For the 3DS2 flow to work correctly, you need to install the payment app cielo-authentication-app.
-</div>
+>⚠️ **Warning**: For the 3DS2 flow to work correctly, you need to install the payment app cielo-authentication-app.
 
 11. In __Early capture__, select how soon the capture must take place (after transaction approval and anti-fraud analysis). You can also disable this option.
 12. Click on __Save__.
diff --git a/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
index 16e5c6773..e1fcbffdb 100644
--- a/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/en/configuring-clearsale-global-anti-fraud-solution.md
@@ -17,9 +17,7 @@ subcategory:
 
 ClearSale Global is an anti-fraud solution, available __exclusively for the international market__. Through customer behavior analysis, the solution identifies vulnerabilities and prevents possible fraud in the transactions of your store.
 
-<div class="alert alert-info">
-If you are in Brazil and would like to use ClearSale, VTEX offers integration with ClearSale V3, exclusive for Brazilian customers. Please refer to the tutorial <a href="https://help.vtex.com/en/tutorial/configurar-antifraude-clearsale-v3--2pPORygesIqQOa6cIG6agg?&utm_source=autocomplete">Configuring ClearSale V3 anti-fraud solution</a> to configure it.
-  </div>
+>ℹ️ If you are in Brazil and would like to use ClearSale, VTEX offers integration with ClearSale V3, exclusive for Brazilian customers. Please refer to the tutorial [Configuring ClearSale V3 anti-fraud solution](https://help.vtex.com/en/tutorial/configurar-antifraude-clearsale-v3--2pPORygesIqQOa6cIG6agg?&utm_source=autocomplete) to configure it.
 
 To configure ClearSale Global, you will need to:
 
diff --git a/docs/tutorials/en/configuring-clearsale-v3-antifraud.md b/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
index f519d1736..dafc9841d 100644
--- a/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/en/configuring-clearsale-v3-antifraud.md
@@ -39,10 +39,9 @@ To configure ClearSaleV3, follow the steps below:
 </ul>
 7. Click `Save`.
 
-<div class="alert alert-info">
-<p>If you have a mobile application that uses VTEX APIs at checkout, it is necessary to implement fingerprint data collection to be sent to Clearsale, according to the platform used by the application. Find out more at <a href="https://api.clearsale.com.br/docs/behavior-analytics" target="_blank">Clearsale Behavior Analytics</a>.</p>
-  <p>With the SDK implementation, it is necessary to collect the <span class="bg-muted-4">sessionId</span> value and send it in the <span class="bg-muted-4">deviceFingerprint</span> via <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">API when creating the payment</a>.</p>
-</div>
+>ℹ️ If you have a mobile application that uses VTEX APIs at checkout, it is necessary to implement fingerprint data collection to be sent to Clearsale, according to the platform used by the application. Find out more at [Clearsale Behavior Analytics](https://api.clearsale.com.br/docs/behavior-analytics" target="_blank).
+>
+> With the SDK implementation, it is necessary to collect the <span class="bg-muted-4">sessionId</span> value and send it in the <span class="bg-muted-4">deviceFingerprint</span> via [API when creating the payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
 
 ## Creating a Google Tag Manager tag
 
@@ -76,7 +75,7 @@ Configuring ClearSale v3 anti-fraud solution requires creating a tag in Google T
 
 ![Pasted image at 2017 10 20 01 11 PM](https://images.contentful.com/alneenqid6w5/2kdI4xh9IYwKI2mSiU20yW/b850c070cc8de2ec09e690ffe6cc9c15/Pasted_image_at_2017_10_20_01_11_PM.png)
 
-<div class="alert alert-info"> See the <a href="https://api.clearsale.com.br/docs/finger-print" target="_blank"> FingerPrint documentation</a> on ClearSale for more information on the above script. </div>
+>ℹ️ See the [ FingerPrint documentation](https://api.clearsale.com.br/docs/finger-print" target="_blank) on ClearSale for more information on the above script.
 
 ## CustomSLA field details
 
@@ -94,6 +93,4 @@ The `shippingEstimate` field can be obtained from the `shippingData.logisticsInf
 
 The `deliverySlaInMinutes` value is the conversion of `shippingEstimate` into minutes. If the unit is `m` (minutes), the value will be the same. If the unit is `h` (hours), the value is multiplied by 60, and if the unit is `d` (calendar days) or `bd` (working days), the value is multiplied by 1440. For example, three calendar days or `3d` is represented as `4320`. The `deliverySlaInMinutes` field is used in each item of the `minicart` in the request body of the <a href="https://developers.vtex.com/vtex-rest-api/reference/antifraud-flow#sendantifraudpreanalysisdata" target="_blank">Send Antifraud Pre-Analysis Data</a> and <a href="https://developers.vtex.com/vtex-rest-api/reference/antifraud-flow#sendantifrauddata" target="_blank">Send Antifraud Data</a> endpoints.
 
-<div class="alert alert-info">
-Although the time conversion in calendar days (<code>d</code>) and working days (<code>bd</code>) to minutes is the same in the <code>deliverySlaInMinutes</code> field, the delivery date may be different depending on the calendar (when there are weekends and holidays within the delivery window).
-</div>
+>ℹ️ Although the time conversion in calendar days (`d`) and working days (`bd`) to minutes is the same in the `deliverySlaInMinutes` field, the delivery date may be different depending on the calendar (when there are weekends and holidays within the delivery window).
diff --git a/docs/tutorials/en/configuring-dns-pointing-to-vtex.md b/docs/tutorials/en/configuring-dns-pointing-to-vtex.md
index 13979d0e0..07cbd43c0 100644
--- a/docs/tutorials/en/configuring-dns-pointing-to-vtex.md
+++ b/docs/tutorials/en/configuring-dns-pointing-to-vtex.md
@@ -30,9 +30,7 @@ Here are the steps:
 
 Before pointing a domain to VTEX, you must ensure that the below-mentioned requirements are met.
 
-<div class="alert alert-warning">
-If you are migrating your store from <strong>Loja Integrada</strong> to VTEX, contact our support before pointing the DNS. The Loja Integrada domain must be enabled to be used in the VTEX store.
-</div>
+>⚠️ If you are migrating your store from **Loja Integrada** to VTEX, contact our support before pointing the DNS. The Loja Integrada domain must be enabled to be used in the VTEX store.
 
 ### Registering a domain on VTEX
 
@@ -48,15 +46,11 @@ VTEX uses two CDN providers in the stores: **Cloudfront** and **Azion**. Your st
 
 So, if you have the store domain registered on the **Cloudfront** or **Azion** platform, delete it before pointing the DNS to VTEX.
 
-<div class="alert alert-warning">
-If you are unable to delete your store's domain registration on the <strong>Cloudfront</strong> or <strong>Azion</strong> platforms, please contact <a href="https://help.vtex.com/en/support">VTEX support</a> to explain the situation. VTEX will help you ensure your store is running smoothly at go-live.
-</div>
+>⚠️ If you are unable to delete your store's domain registration on the **Cloudfront** or **Azion** platforms, please contact [VTEX support](https://help.vtex.com/en/support) to explain the situation. VTEX will help you ensure your store is running smoothly at go-live.
 
 ## Configuring CAA records
 
-<div class="alert alert-warning">
-You will only need to configure CAA records, as described in this section if there is a CAA record in your DNS server. Otherwise, proceed to the next section of this guide.
-</div>
+>⚠️ You will only need to configure CAA records, as described in this section if there is a CAA record in your DNS server. Otherwise, proceed to the next section of this guide.
 
 CAA records indicate which certificate authorities (CAs) are entitled to generate and renew certificates to confirm your domain identity. Proper configuration of these records is necessary to generate [SSL certificates](https://help.vtex.com/en/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar--tutorials_1308) and use the VTEX CDN.
 
@@ -70,9 +64,7 @@ This means that the **Let's Encrypt** certificate authority can issue certificat
 
 Although not recommended, another alternative would be not including CAA records in your DNS server, indicating that all certificate authorities are authorized to issue and renew certificates for your domain.
 
-<div class="alert alert-info">
-These types of entries may not be available in the interface of your DNS manager, but you can usually manage them by calling the support of the specific tool.
-</div>
+>ℹ️ These types of entries may not be available in the interface of your DNS manager, but you can usually manage them by calling the support of the specific tool.
 
 To easily create/verify your CAA records, you can use [CAA Record Helper by SSLMate](https://sslmate.com/caa/). The [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) program can also help you verify your records with the `dig domain.com CAA` command – a `SERVFAIL` status can indicate non-compliance of your DNS server.
 
@@ -132,9 +124,7 @@ The certificate is generated through [Let's Encrypt](https://letsencrypt.org/) a
 
 ---
 
-<div class="alert alert-info">
-DNS pointing propagation takes 24-48 hours to occur completely, which means that the configured address may not be accessible to all people right after configuration.
-</div>
+>ℹ️ DNS pointing propagation takes 24-48 hours to occur completely, which means that the configured address may not be accessible to all people right after configuration.
 
 The above instructions deal exclusively with pointing a primary domain to your VTEX store. It's important that if your store has other domains, they are redirected to a single primary domain.
 
diff --git a/docs/tutorials/en/configuring-domains-in-account-management.md b/docs/tutorials/en/configuring-domains-in-account-management.md
index a6542bb53..1903ac461 100644
--- a/docs/tutorials/en/configuring-domains-in-account-management.md
+++ b/docs/tutorials/en/configuring-domains-in-account-management.md
@@ -17,15 +17,13 @@ subcategory: yMp6sKDiJEi66CGAIQ4ma
 
 Configuring domains ensures that the address access is directed correctly to the VTEX store. Below you can learn how to [register a new domain](#register-new-domain) or [change the domain of an active store](#change-store-domain).
 
-<div class="alert alert-danger">
-In case your operation has more than one VTEX account or subaccounts, do not trade domains among them. This will cause errors in different aspects of your store.
-</div>
+>❗ In case your operation has more than one VTEX account or subaccounts, do not trade domains among them. This will cause errors in different aspects of your store.
 
-<div class="alert alert-warning">
-If you add more than one domain as your store's host, they will all display the same content. However, we recommend registering only one domain and using redirections for the other ones. Learn more about redirections:
-<ul><li><a href=”https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirection from other addresses</a></li>
-<li><a href=”https://help.vtex.com/en/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configuring access without www</a></li></ul>  
-</div>
+>⚠️ If you add more than one domain as your store's host, they will all display the same content. However, we recommend registering only one domain and using redirections for the other ones. Learn more about redirections:
+>
+> *<a href=”https://help.vtex.com/en/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirection from other addresses</a>
+>
+> *<a href=”https://help.vtex.com/en/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configuring access without www</a>
 
 ## Subdomain
 
diff --git a/docs/tutorials/en/configuring-greenlist.md b/docs/tutorials/en/configuring-greenlist.md
index 2693b24a2..d795c7318 100644
--- a/docs/tutorials/en/configuring-greenlist.md
+++ b/docs/tutorials/en/configuring-greenlist.md
@@ -35,9 +35,7 @@ Whether or not the antifraud approves, once the service has been consulted the s
 
 __A Greenlist is a list of customers previously approved by the store owner according to certain criteria.__ Once these customers have made a certain number of purchases on your site, always giving the same details (such as email address and credit card number) they are marked as trustworthy. Then the next time they make a purchase on your site, their orders do not go through the antifraud, and your store saves the fee it would have to pay for this service.
 
-<div class="alert alert-warning">
-The more signature data you ask for, the stricter will be your rules, and the fewer customers will be added to the Greenlist.
-</div>
+>⚠️ The more signature data you ask for, the stricter will be your rules, and the fewer customers will be added to the Greenlist.
 
 ## Configuring the Greenlist
 
diff --git a/docs/tutorials/en/configuring-ideal-payment-method-in-adyen-integration.md b/docs/tutorials/en/configuring-ideal-payment-method-in-adyen-integration.md
index 983a2e2c0..2aa5dc38c 100644
--- a/docs/tutorials/en/configuring-ideal-payment-method-in-adyen-integration.md
+++ b/docs/tutorials/en/configuring-ideal-payment-method-in-adyen-integration.md
@@ -18,10 +18,8 @@ subcategory:
 __iDEAL__ is an online payment method available only to customers in The Netherlands which allows consumers to make payments directly in their own bank. 
 In this tutorial, you will go through the steps to configure it in your store through an integration with [Adyen](https://help.vtex.com/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337).
 
-<div class="alert alert-danger">
-  <b>Adyen</b> is currently the only partner that supports payments made with iDEAL. This means you need to get in touch with Adyen to check whether iDEAL is applicable for your location. 
-If so, consult the article <a href="https://help.vtex.com/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337?&utm_source=autocomplete">How to set up the Adyen gateway on VTEX</a> and configure the affiliation in your store.
-  </div>
+>❗ **Adyen** is currently the only partner that supports payments made with iDEAL. This means you need to get in touch with Adyen to check whether iDEAL is applicable for your location. 
+> If so, consult the article [How to set up the Adyen gateway on VTEX](https://help.vtex.com/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337?&utm_source=autocomplete) and configure the affiliation in your store.
 
 1. Access the VTEX __Admin__.
 2. Click on __Payments__ > __Settings__.
diff --git a/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
index 1700c1c1a..04e160bc2 100644
--- a/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/en/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -19,9 +19,7 @@ In this article, you'll learn how to configure the maximum payment settlement ti
 
 It is important to clarify the differences between __settlement after payment confirmation__, __automatic settlement__, and __payment with anticipated settlement authorization__ - three concepts from the payments market. For some payment connectors in the platform, these terms are referred to as __capture after payment confirmation__, __payment with anticipated capture authorization__ and __automatic capture__.
 
-<div class="alert alert-warning">
-The following information is valid for payments with credit cards.
-</div>
+>⚠️ The following information is valid for payments with credit cards.
 
 ## Settlement after payment confirmation
 
@@ -43,9 +41,7 @@ When the authorization process begins, the system waits for a previously set max
 
 The retailer and the acquirer agree on the time frame for the automatic settlement to be triggered. 
 
-<div class="alert alert-info">
-The maximum time frame set for payment settlement is usually four days. However, this is <strong>not</strong> a rule. Each acquirer can define the period they find most appropriate.
-</div>
+>ℹ️ The maximum time frame set for payment settlement is usually four days. However, this is **not** a rule. Each acquirer can define the period they find most appropriate.
 
 To configure the automatic settlement feature, follow the step-by-step instructions below:
 
diff --git a/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
index 8811a448b..67b717920 100644
--- a/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/en/configuring-mercado-pagos-device-fingerprint.md
@@ -19,9 +19,7 @@ __Device Fingerprint__ is an identifier that acts in payment processing to impro
 
 By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
 
 This article will explain how to associate the Device Fingerprint feature with the Mercado Pago affiliation.
 
diff --git a/docs/tutorials/en/configuring-openpay-payment-gateway.md b/docs/tutorials/en/configuring-openpay-payment-gateway.md
index f5f6a3900..616737b49 100644
--- a/docs/tutorials/en/configuring-openpay-payment-gateway.md
+++ b/docs/tutorials/en/configuring-openpay-payment-gateway.md
@@ -17,9 +17,7 @@ subcategory:
 
 [Openpay](https://www.openpay.mx/en/) is an online payment processor that allows you to receive payments made by credit cards, bank transfers, and in cash.
 
-<div class="alert alert-warning">
-  To configure it in your store, you need to have a verified Openpay account. If you do not have it yet, <a href="https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false">click here</a> to create your account.
-  </div>
+>⚠️ To configure it in your store, you need to have a verified Openpay account. If you do not have it yet, [click here](https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false) to create your account.
 
 To configure Openpay in your VTEX environment, you will need to:
 
diff --git a/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index 6654f7c3a..eac12ecf1 100644
--- a/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/en/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 At VTEX, it is possible to integrate with the payment provider Adyen. Through this connector, your store can offer payment transactions in physical stores (VTEX Sales App), using points of sale (POS). For more information access [What is VTEX Sales App?](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf).
 
-<div class="alert alert-info">
-To use the AdyenV3 affiliation in your store through other online sales channels (except VTEX Sales App), visit <a href="https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv">Configuring payment with AdyenV3</a>.
-</div>
+>ℹ️ To use the AdyenV3 affiliation in your store through other online sales channels (except VTEX Sales App), visit [Configuring payment with AdyenV3](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3--7xAz67E2Eg63LWCQNjVdwv).
 
 To use the AdyenV3 affiliation in the VTEX Sales App, you need to:
 
@@ -28,9 +26,7 @@ To use the AdyenV3 affiliation in the VTEX Sales App, you need to:
 - [Configure AdyenV3 Connector (VTEX Sales App) on VTEX](#configuring-adyenv3-connector-vtex-sales-app-on-vtex)
 - [Configure payment condition](#configuring-payment-condition)
 
-<div class="alert alert-warning">
-Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Adyen account for the latest information.
-</div>
+>⚠️ Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Adyen account for the latest information.
 
 ## Configuring point of sale (POS)
 
@@ -100,9 +96,7 @@ Follow the steps below to configure a webhook:
 
 ![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
-<div class="alert alert-info">
-If you have several stores, you need to configure a webhook for each of them.
-</div>
+>ℹ️ If you have several stores, you need to configure a webhook for each of them.
 
 ## Configuring AdyenV3 Connector (VTEX Sales App) on VTEX
 
diff --git a/docs/tutorials/en/configuring-payment-with-adyenv3.md b/docs/tutorials/en/configuring-payment-with-adyenv3.md
index 3e19ecac6..26bf1f2aa 100644
--- a/docs/tutorials/en/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/en/configuring-payment-with-adyenv3.md
@@ -22,13 +22,9 @@ To use the AdyenV3 affiliation, you must:
 - [Configure your Adyen environment](#configuring-your-adyen-environment)
 - [Configuring the AdyenV3 connector on VTEX](#configuring-the-adyenv3-connector-on-vtex)
 
-<div class="alert alert-warning">
-Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Adyen account for the latest information.
-</div>
+>⚠️ Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Adyen account for the latest information.
 
-<div class="alert alert-info">
-To use the AdyenV3 affiliation through <a href="https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf">Sales App</a> in your physical stores (point of sale), see <a href="https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3-in-instore--24yO6KloBn6DN6CbprHtgt">Configuring payments with AdyenV3 on Sales App</a>.
-</div>
+>ℹ️ To use the AdyenV3 affiliation through [Sales App](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) in your physical stores (point of sale), see [Configuring payments with AdyenV3 on Sales App](https://help.vtex.com/en/tutorial/configuring-payment-with-adyenv3-in-instore--24yO6KloBn6DN6CbprHtgt).
 
 ## Configuring your Adyen environment
 
@@ -51,9 +47,7 @@ To enable VTEX access to the Adyen environment, follow the instructions below:
 
 ### Getting the API Key and Client Key
 
-<div class="alert alert-warning">
-The steps below assume that the API Key and Client Key have been previously generated in the Adyen environment. If you need to create them, see the <a href="https://docs.adyen.com/">Adyen</a> documentation.
-</div>
+>⚠️ The steps below assume that the API Key and Client Key have been previously generated in the Adyen environment. If you need to create them, see the [Adyen](https://docs.adyen.com/) documentation.
 
 1. In the sidebar, click __Developers__ and, then, click __API credentials__.
 2. Select your API credential.
@@ -95,9 +89,7 @@ Follow the steps below to configure a webhook:
 
 ![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
-<div class="alert alert-info">
-If you have several stores, you need to configure a webhook for each of them.
-</div>
+>ℹ️ If you have several stores, you need to configure a webhook for each of them.
 
 ## Configuring the AdyenV3 connector on VTEX
 
@@ -124,9 +116,7 @@ If you wish to process credit card payments in your store using AdyenV3, in addi
 
 In the ticket you must also send the URL that will be authorized by Adyen to carry out the credit card transaction in your store. The URL format must be `https://{live URL prefix}-checkout-live.adyenpayments.com`, where the information "{live URL prefix}" must be the same as that entered by you in the Adyen settings in the VTEX Admin.  
 
-<div class="alert alert-warning">
-The full URL address must be written in lowercase letters only, even if the "Live URL prefix" configured in the VTEX Admin has some capital letters.
-</div>    
+>⚠️ The full URL address must be written in lowercase letters only, even if the "Live URL prefix" configured in the VTEX Admin has some capital letters.    
 
 ## Configure payment with Apple Pay on Adyen (optional) 
 
diff --git a/docs/tutorials/en/configuring-price-divergence-rule.md b/docs/tutorials/en/configuring-price-divergence-rule.md
index a8eaa0cf2..592981d67 100644
--- a/docs/tutorials/en/configuring-price-divergence-rule.md
+++ b/docs/tutorials/en/configuring-price-divergence-rule.md
@@ -71,9 +71,7 @@ To create the **2nd rule**, click on the `<img class="shadow-4" src="https:////i
 
 Configure the new authorization rule and, once you have configured all the rules you want, click on the **SAVE RULES** button. You will see the following message: _After saving, you can still edit or delete them at any time_. Click **OK** to confirm. Once this is done, the Price Divergence rule will be created.
 
-<div class="alert alert-warning">
-Once the Price Divergence rule is created, it is applied to all marketplaces where you act as a seller.
-</div>
+>⚠️ Once the Price Divergence rule is created, it is applied to all marketplaces where you act as a seller.
 
 ## Editing Price Divergence rule
 
@@ -95,9 +93,7 @@ Once you have made the desired changes, click on the **SAVE RULES** button, and
 
 When an authorization rule is configured with the option _Create a task in VTEX DO for approval_, this means that at least one user has been assigned to manually approve the order. [Managing orders with price divergence](https://help.vtex.com/en/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW#managing-orders-with-price-divergence) is similar to managing orders from any other sales channel, such as a physical store or ecommerce.
 
-<div class="alert alert-warning">
-It is important to regularly track orders in <b>Orders</b> module. To do this, go to <b>Orders > All Orders</b>. If they require manual approval, orders with price divergence errors remain pending, awaiting approval by an authorized user, defined when the authorization rule was created. Having at least two users authorized to perform manual processing is a good practice.
-</div>
+>⚠️ It is important to regularly track orders in **Orders** module. To do this, go to **Orders > All Orders**. If they require manual approval, orders with price divergence errors remain pending, awaiting approval by an authorized user, defined when the authorization rule was created. Having at least two users authorized to perform manual processing is a good practice.
 
 There are two ways to manually approve an order with price divergence:
 
diff --git a/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
index 9e3990a35..549d56d6f 100644
--- a/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
+++ b/docs/tutorials/en/configuring-seller-allocation-for-buying-xky.md
@@ -45,7 +45,6 @@ To assign sellers to a particular buying organization, follow the steps below:
 From now on, whenever the organization searches on the VTEX platform, only the products from the sellers assigned to it will be displayed.
 </ol>
 
-<div class="alert alert-warning">
-Buying organizations that do not assign sellers will be able to access information and purchase from all the sellers available on the marketplace.</div>
+>⚠️ Buying organizations that do not assign sellers will be able to access information and purchase from all the sellers available on the marketplace.
 
 For more information on how to integrate a new seller, read the[ Adding a seller](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392) article.
diff --git a/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
index 5282753ad..bce823896 100644
--- a/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
+++ b/docs/tutorials/en/configuring-sign-in-with-apple-id-beta.md
@@ -15,9 +15,7 @@ legacySlug: configuring-sign-in-with-apple-id-beta
 subcategory: 5uXA9a0laSLMkfbv6jQRDS
 ---
 
-<div class="alert alert-info">
-  <p>This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/en-us/">our support</a>.</p>
-</div>
+>ℹ️ This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact [our support](https://support.vtex.com/hc/en-us/).
 
 On VTEX, customers don't need to create an account or log in to make a purchase. However, if they want to change the information provided during their first purchase, they must prove the email belongs to them.
 
@@ -72,9 +70,7 @@ Once everything is configured, you can test it. We recommend that you test the c
 4. Complete the two-factor authentication if requested.
 5. Choose whether to share your email with the app or [hide it](https://support.apple.com/en-us/HT210425) and click `Continue`. We recommend sharing the email, as there are [limitations](#limitations) with hidden email on VTEX.
 
-<div class="alert alert-info">
-  <p>The option of whether to share your email appears only when you first access the store with your Apple ID. After that, you only need to click <code>Continue</code>. To reset the email sharing option, visit <a href="https://appleid.apple.com/us/">Apple ID management</a>, revoke your store authorization, and log in again.</p>
-</div>
+>ℹ️ The option of whether to share your email appears only when you first access the store with your Apple ID. After that, you only need to click `Continue`. To reset the email sharing option, visit [Apple ID management](https://appleid.apple.com/us/), revoke your store authorization, and log in again.
 
 By doing so, you will be logged in to the store.
 
diff --git a/docs/tutorials/en/configuring-spin-pay-gateway.md b/docs/tutorials/en/configuring-spin-pay-gateway.md
index a410acd3a..0b8ea468b 100644
--- a/docs/tutorials/en/configuring-spin-pay-gateway.md
+++ b/docs/tutorials/en/configuring-spin-pay-gateway.md
@@ -17,9 +17,7 @@ subcategory:
 
 You can now use the [Spin Pay](https://spinpay.com.br/) gateway to process payments in your VTEX store. This solution allows you to receive payments via PIX (Brazilian instant payment system) and the main digital wallets available on the market today.
 
-<div class="alert alert-warning">
-  To use Spin Pay on VTEX, you must have an <b>Application Key (App Key)</b> and an <b>Application Token (App Token)</b>. You can get these keys after Spin Pay approves your registration and you sign the contract. 
-   </div>
+>⚠️ To use Spin Pay on VTEX, you must have an **Application Key (App Key)** and an **Application Token (App Token)**. You can get these keys after Spin Pay approves your registration and you sign the contract.
 
 Once your registration has been approved and you have signed the contract, follow the steps below to configure Spin Pay in your store.
 
@@ -49,8 +47,6 @@ Once you have installed the gateway in your store, configure its [payment condit
 9. If you have an anti-fraud solution, check the box next to __Use anti-fraud__ and choose an option.
 10. Click on __Save__.
 
-<div class="alert alert-warning">
-  Spin Pay is a brazilian instant payment solution in which debits are made directly to the consumer's bank account. For this reason, it doesn’t offer the option to pay in installments.
-   </div>
+>⚠️ Spin Pay is a brazilian instant payment solution in which debits are made directly to the consumer's bank account. For this reason, it doesn’t offer the option to pay in installments.
 
 After completing all these steps, Spin Pay will be ready to process payments in your store.
diff --git a/docs/tutorials/en/configuring-stripe-gateway-affiliation.md b/docs/tutorials/en/configuring-stripe-gateway-affiliation.md
index ed8e951cc..dd0c67e88 100644
--- a/docs/tutorials/en/configuring-stripe-gateway-affiliation.md
+++ b/docs/tutorials/en/configuring-stripe-gateway-affiliation.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 [Stripe](https://stripe.com) is a payment platform that offers an integrated system for receiving payments, transfers, donations, and any typical financial transaction in ecommerce and other websites.
 
-<div class="alert alert-warning">
-You can integrate your store with Stripe via <strong>Application Key</strong> and <strong>Application Token</strong>. To obtain this data, you have to <a href="https://dashboard.stripe.com/register" target="_blank">create your account on the platform</a> and then access <a href="https://stripe.com/docs/keys" target="_blank">Stripe’s documentation</a> to get your <strong>Public key</strong> and <strong>Secret key</strong>. They are required for the setup in the VTEX environment.
-</div>
+>⚠️ You can integrate your store with Stripe via **Application Key** and **Application Token**. To obtain this data, you have to [create your account on the platform](https://dashboard.stripe.com/register" target="_blank) and then access [Stripe’s documentation](https://stripe.com/docs/keys" target="_blank) to get your **Public key** and **Secret key**. They are required for the setup in the VTEX environment.
 
 Stripe supports payments in over 40 countries. The list of available countries can be accessed on the [Stripe website](https://stripe.com/enterprise).
 
@@ -56,12 +54,13 @@ After configuration in the VTEX environment, you also need to configure Webhook
 8. Click on __Add events__.
 9. Click on __Add endpoint__.
 
-<div class="alert alert-info">
-  <p>If you wish to carry out credit card transactions on Stripe, you must open a ticket on Stripe as follows:</p>
-  <p>- Request the release of the "raw card data" function, indicating that VTEX and Stripe are payment partners.</p>
-  <p>- Please attach the VTEX AOC (Attestation of Compliance for Onsite Assessments – Service Providers). To check the latest version of AOC VTEX, access the <a href="https://vtex.com/us-en/compliance/certifications">VTEX certifications</a> page and download the file available in the PCI section.</p>
-  <p>The above actions will prevent errors related to the transmission of sensitive data from occurring in the integration between Stripe and VTEX.</p>
-</div>
+>ℹ️ If you wish to carry out credit card transactions on Stripe, you must open a ticket on Stripe as follows:
+>
+> - Request the release of the "raw card data" function, indicating that VTEX and Stripe are payment partners.
+>
+> - Please attach the VTEX AOC (Attestation of Compliance for Onsite Assessments – Service Providers). To check the latest version of AOC VTEX, access the [VTEX certifications](https://vtex.com/us-en/compliance/certifications) page and download the file available in the PCI section.
+>
+> The above actions will prevent errors related to the transmission of sensitive data from occurring in the integration between Stripe and VTEX.
 
 ## Configuring a payment condition
 
@@ -86,9 +85,7 @@ After this configuration, Google Pay will be displayed as one of the available p
 
 The Stripe connector allows you to add Apple Pay as a payment method in your store's checkout. 
 
-<div class="alert alert-warning">
-Apple Pay currently only works on MacOs and IOS operating systems, and with  Safari browser. For more information, visit <a href="https://support.apple.com/en-us/HT208531">Devices compatible with Apple Pay</a>.
-</div>
+>⚠️ Apple Pay currently only works on MacOs and IOS operating systems, and with  Safari browser. For more information, visit [Devices compatible with Apple Pay](https://support.apple.com/en-us/HT208531).
 
 Once the Stripe connector is configured, you can add Apple Pay by following the steps below.
 
diff --git a/docs/tutorials/en/configuring-telesales-features.md b/docs/tutorials/en/configuring-telesales-features.md
index b8381e047..d639122b8 100644
--- a/docs/tutorials/en/configuring-telesales-features.md
+++ b/docs/tutorials/en/configuring-telesales-features.md
@@ -62,6 +62,4 @@ To use this feature, the store's developers must first enable manual pricing usi
 
 Prices changed manually in the shopping cart need to be approved by the store administrator or an authorized user in the [Orders authorization](https://help.vtex.com/en/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn) system. Only after that can you proceed to the billing process.
 
-<div class="alert alert-info">
-It is not possible to change prices by accessing the store through its final URL (<i>www.storedomain.com.br</i>). The manual price functionality in telesales only works if the operator accesses the store through the <i>www.storedomain.myvtex.com</i> domain and has the <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator">Call Center operator</a> in their <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">Access profile</a>. 
-</div>
+>ℹ️ It is not possible to change prices by accessing the store through its final URL (<i>www.storedomain.com.br</i>). The manual price functionality in telesales only works if the operator accesses the store through the <i>www.storedomain.myvtex.com</i> domain and has the [Call Center operator](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator) in their [Access profile](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/tutorials/en/configuring-the-global-checkout.md b/docs/tutorials/en/configuring-the-global-checkout.md
index 62322b3fc..69174a4cf 100644
--- a/docs/tutorials/en/configuring-the-global-checkout.md
+++ b/docs/tutorials/en/configuring-the-global-checkout.md
@@ -58,9 +58,7 @@ Let us assume that you intend to make a delivery for a customer located in Engla
 1. [Create a new carrier](/en/tutorial/registering-a-carrier/).
 2. For the new carrier, create a shipping worksheet with the column “Country” using the 3-digit ISO code of the country.
 
-<div class="alert alert-info">
-The value of the column “Country” must be the 3-digit ISO code of the countries. In order to check the codes, we recommend the website<a href="https://countrycode.org/">https://countrycode.org/</a>.
-</div>
+>ℹ️ The value of the column “Country” must be the 3-digit ISO code of the countries. In order to check the codes, we recommend the website[https://countrycode.org/](https://countrycode.org/).
 
 After having defined the delivery settings for the countries intended, a new field will be shown on the delivery form of your checkout allowing the user to choose the desired international delivery option. 
 
diff --git a/docs/tutorials/en/configuring-the-pickup-in-store.md b/docs/tutorials/en/configuring-the-pickup-in-store.md
index d597b6638..2812cb10f 100644
--- a/docs/tutorials/en/configuring-the-pickup-in-store.md
+++ b/docs/tutorials/en/configuring-the-pickup-in-store.md
@@ -15,9 +15,7 @@ legacySlug: configuring-the-pickup-in-store
 subcategory: 1c5Btie9ou2Gg2iUo0ggqM
 ---
 
-<div class="alert alert-danger">
-This article is obsolete. To set up the pickup point correctly, go to the article <a href="https://help.vtex.com/en/tutorial/adding-pickup-points--2R5ClQiwe4KoSQgsuiOw4E">Registering Pickup Points</a>
-</div>
+>❗ This article is obsolete. To set up the pickup point correctly, go to the article [Registering Pickup Points](https://help.vtex.com/en/tutorial/adding-pickup-points--2R5ClQiwe4KoSQgsuiOw4E)
 
 
 The store pickup configuration enables the customer to opt not to receive the product at home, but to collect it at a store. The following steps show how to give the customer the option of selecting a store for pickup at checkout, during the purchase flow. The configuration is made on 3 different modules of the platform, as described below.
diff --git a/docs/tutorials/en/configuring-the-rede-acquirer.md b/docs/tutorials/en/configuring-the-rede-acquirer.md
index 826a30e51..abd053a82 100644
--- a/docs/tutorials/en/configuring-the-rede-acquirer.md
+++ b/docs/tutorials/en/configuring-the-rede-acquirer.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 At VTEX, you can integrate your store with the Rede acquirer. After you configure the __ERedev2__ connector, your store will be able to accept credit card payments from the main brands.
 
-<div class="alert alert-info">
-<strong>Warning</strong>: currently there is a more updated version of Rede’s connector. For more details on how to configure this acquirer, read the article on [ERedeREST](https://help.vtex.com/en/tutorial/configurar-adquirente-rede-con-erederest?locale=en "ERedeREST").
-</div>
+>ℹ️ **Warning**: currently there is a more updated version of Rede’s connector. For more details on how to configure this acquirer, read the article on [ERedeREST](https://help.vtex.com/en/tutorial/configurar-adquirente-rede-con-erederest?locale=en "ERedeREST").
 
 To configure Rede, follow the steps below:
 
diff --git a/docs/tutorials/en/configuring-the-scheduled-delivery.md b/docs/tutorials/en/configuring-the-scheduled-delivery.md
index 0c21f2256..978335919 100644
--- a/docs/tutorials/en/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/en/configuring-the-scheduled-delivery.md
@@ -15,9 +15,7 @@ legacySlug: configuring-the-scheduled-delivery
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Warning: This documentation is being updated to reflect the concept change from Dashboards to <a href="https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">shipping strategy</a>.
-</div>
+>ℹ️ Warning: This documentation is being updated to reflect the concept change from Dashboards to [shipping strategy](https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 
 The scheduled delivery is a feature that allows you to customize delivery times and to set specific deadlines and prices, as well as enables the customers to choose the period when they wish to receive your order. 
diff --git a/docs/tutorials/en/configuring-the-store-domain.md b/docs/tutorials/en/configuring-the-store-domain.md
index 4ce19a67a..af08d5242 100644
--- a/docs/tutorials/en/configuring-the-store-domain.md
+++ b/docs/tutorials/en/configuring-the-store-domain.md
@@ -82,13 +82,9 @@ To register a new host, they must comply with the guidelines specified in the [R
 
 After completing these steps, you can [configure DNS pointing to VTEX](https://help.vtex.com/en/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-  <p><a href="https://www.faststore.dev/">FastStore</a> stores also need to configure an address with the <code>secure</code> subdomain. Refer to the<a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns"> Configuring external DNS for a custom domain</a> guide for more details.</p>
-</div>
+>⚠️ [FastStore](https://www.faststore.dev/) stores also need to configure an address with the `secure` subdomain. Refer to the[ Configuring external DNS for a custom domain](https://www.faststore.dev/docs/go-live/2-configuring-external-dns) guide for more details.
 
-<div class="alert alert-danger">
-  <p>If your operation has more than one VTEX account or <a href="https://help.vtex.com/en/tutorial/como-criar-multiloja-multidominio--tutorials_510">sub-account</a>, don't change hosts from one account to another. This will cause failures in many aspects of your store.</p>
-</div>
+>❗ If your operation has more than one VTEX account or [sub-account](https://help.vtex.com/en/tutorial/como-criar-multiloja-multidominio--tutorials_510), don't change hosts from one account to another. This will cause failures in many aspects of your store.
 
 ## Changing host
 
diff --git a/docs/tutorials/en/configuring-tuna-gateway-affiliation.md b/docs/tutorials/en/configuring-tuna-gateway-affiliation.md
index da2ca40a7..92ee966a8 100644
--- a/docs/tutorials/en/configuring-tuna-gateway-affiliation.md
+++ b/docs/tutorials/en/configuring-tuna-gateway-affiliation.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 At VTEX, you can configure your store with the Tuna gateway to receive payments through: bank invoice, debit and credit cards, PIX and Bitcoin.
 
-<div class="alert alert-warning">
-  You can integrate your store with Tuna via <b>Application Key</b> and <b>Application Token.</b> To receive this information, you need to create your account first. To do so, please fill out <a href="https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform">this form</a> and wait to be contacted by Tuna with more details.
-  </div>
+>⚠️ You can integrate your store with Tuna via **Application Key** and **Application Token.** To receive this information, you need to create your account first. To do so, please fill out [this form](https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform) and wait to be contacted by Tuna with more details.
 
 Once you have created your account and obtained the __Application Key__ and __Application Token__, follow the steps below to configure Tuna in your store:
 
diff --git a/docs/tutorials/en/configuring-vtex-marketplace.md b/docs/tutorials/en/configuring-vtex-marketplace.md
index 4048b3f36..c8c15a3ee 100644
--- a/docs/tutorials/en/configuring-vtex-marketplace.md
+++ b/docs/tutorials/en/configuring-vtex-marketplace.md
@@ -83,9 +83,7 @@ A marketplace can obtain the user’s location information in the storefront and
 
 Even when VTEX Session does not have access to the consumer’s location, you still need to target an assortment of seller products in the shopping experience. In this scenario, the seller selection algorithm indicates [comprehensive sellers](https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI) that are able to deliver orders in all regions served by your marketplace.
 
-<div class="alert alert-info">
-The Region feature is only adapted for stores using VTEX IO, and it is not valid for the Legacy CMS Portal. 
-</div>
+>ℹ️ The Region feature is only adapted for stores using VTEX IO, and it is not valid for the Legacy CMS Portal.
 
 ## Configuring the storefront
 
diff --git a/docs/tutorials/en/configuring-xml.md b/docs/tutorials/en/configuring-xml.md
index 8a39cfd2d..830d82388 100644
--- a/docs/tutorials/en/configuring-xml.md
+++ b/docs/tutorials/en/configuring-xml.md
@@ -61,9 +61,7 @@ Once you have this, follow the steps below to configure your XML:
 13. Thereafter, you have to enter the tags in accordance with the what has been defined by the system you will be sending the XML to. You must check the selection box in the __Show content__ column, for the tags which have a name entered. The tags with this option checked, and which you cannot deselect, are mandatory.
 14. The URL used to access the XML is generated automatically, according to the [domain registered in the Web Site dictionary](https://help.vtex.com/en/tutorial/configuring-an-xml-domain--2RkGK4vHS0c6sYuUw0cUWC), in the __CMS__.
 
-<div class="alert alert-warning">
-  <p>In case the trade policy has restricted access, the XML will not be generated.</p>
-</div>
+>⚠️ In case the trade policy has restricted access, the XML will not be generated.
 
 ## Native connectors: an alternative to XML when integrating with marketplaces
 
diff --git a/docs/tutorials/en/coupons-beta.md b/docs/tutorials/en/coupons-beta.md
index e8532d0e0..de9b35e0b 100644
--- a/docs/tutorials/en/coupons-beta.md
+++ b/docs/tutorials/en/coupons-beta.md
@@ -21,9 +21,7 @@ A coupon consists of a promotional code composed of a sequence of letters and nu
 
 You can create and edit coupons in the VTEX Admin, in **Promotions** > [Coupons](https://help.vtex.com/en/tutorial/coupons-list-beta--5z5ya3IonsC2W4B5h4JrsZ) or via the [Promotions & Taxes API v2](https://developers.vtex.com/vtex-rest-api/reference/promotions-taxes-api-v2).
 
-<div class="alert alert-warning">
-<p>To be valid, the coupon must be associated with at least one promotion. The coupon can be associated with all types of promotions, except <a href="https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume">Campaign promotions</a>. Learn more in <a href="https://help.vtex.com/en/tutorial/creating-a-coupon-beta--7lMk3MmhNp2IEccyGApxU">Creating a coupon (Beta)</a>.</p>
-</div>
+>⚠️ To be valid, the coupon must be associated with at least one promotion. The coupon can be associated with all types of promotions, except [Campaign promotions](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume). Learn more in [Creating a coupon (Beta)](https://help.vtex.com/en/tutorial/creating-a-coupon-beta--7lMk3MmhNp2IEccyGApxU).
 
 ## Coupon types
 
diff --git a/docs/tutorials/en/creating-a-campaign-audience.md b/docs/tutorials/en/creating-a-campaign-audience.md
index 633f5344c..53837ec47 100644
--- a/docs/tutorials/en/creating-a-campaign-audience.md
+++ b/docs/tutorials/en/creating-a-campaign-audience.md
@@ -26,9 +26,7 @@ Follow the steps below to create a new campaign audience:
 5. Fill in the fields described in the [Create new target audience](#creating-a-new-target-audience) section.
 6. Click `Save`.
 
-<div class="alert alert-warning">
-  <p>After creating a campaign audience, you have to associate it with a campaign promotion to take effect. Follow the steps described in the <a href="https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume">Creating a campaign promotion</a> guide.</p>
-</div>
+>⚠️ After creating a campaign audience, you have to associate it with a campaign promotion to take effect. Follow the steps described in the [Creating a campaign promotion](https://help.vtex.com/en/tutorial/campaign-promotion--1ChYXhK2AQGuS6wAqS8Ume) guide.
 
 ## General data
 
@@ -45,10 +43,9 @@ When creating a new campaign audience, you must enter the following information
     * **End Date:** End date scheduled for deactivating the campaign audience.
     * **End Hour:** End hour scheduled for deactivating the campaign audience.
 
-<div class="alert alert-warning">
-  <p>When scheduling a campaign audience, the <strong>Start Date</strong> or <strong>Start Hour</strong> must be subsequent to your current date or hour.</p>
-<p>The time zone will be the same as the one on the user's device when creating the campaign audience — you cannot adjust the hour to a different time zone.</p>
-</div>
+>⚠️ When scheduling a campaign audience, the **Start Date** or **Start Hour** must be subsequent to your current date or hour.
+>
+> The time zone will be the same as the one on the user's device when creating the campaign audience — you cannot adjust the hour to a different time zone.
 
 ## Creating a new target audience
 
@@ -102,9 +99,7 @@ For example: The target audience includes items whose brand is **Nike**, as illu
 * **Shipping to postal code should Include / Exclude from __ to __:** Allows including or excluding shipping code ranges for order shipment. The campaign audience will be activated if the shipping code meets the rule set for the target audience.
 * **Affiliates:** Allows selecting [affiliates](https://help.vtex.com/en/tutorial/what-is-an-affiliate--4bN3e1YarSEammk2yOeMc0) from a list. A campaign audience will be activated if the purchase is made in one of those affiliate marketplaces.
 
-  <div class="alert alert-warning">
-    <p>The <strong>Affiliates</strong> option only applies if the affiliate is a VTEX store.</p>
-  </div>
+  >⚠️ The **Affiliates** option only applies if the affiliate is a VTEX store.
 
 * **utm_source:** Allows selecting the desired [utm_source](https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) or creating a new one to be linked to the campaign audience. The campaign audience will be activated if customer navigation is made using the utm_source corresponding to any entered values. It is important to note that customers can only enter one utm_source at checkout.
 * **utm_campaign:** Allows selecting the desired [utm_campaign](https://help.vtex.com/en/tutorial/what-are-utm-source-utm-campaign-and-utm-medium--2wTz7QJ8KUG6skGAoAQuii) or creating a new one to be linked to the campaign audience. The discount will be granted if the customer navigation uses a utm_campaign corresponding to the entered value.
@@ -112,9 +107,7 @@ For example: The target audience includes items whose brand is **Nike**, as illu
 * **Apply selected discount only when one of the above carriers is selected by the customer:** The campaign audience will be activated only after the customer selects the order delivery method.
 * **Payment system:** Allows selecting the payment methods that will be included in the target audience. The campaign audience will be activated if the payment method selected by the customer is the one configured for this target audience.
 
-  <div class="alert alert-warning">
-    <p>Campaign audiences defined by <strong>Payment system</strong> or <strong>Maximum number of installments</strong> will not apply to orders paid using two credit cards or vouchers.</p>
-  </div>
+  >⚠️ Campaign audiences defined by **Payment system** or **Maximum number of installments** will not apply to orders paid using two credit cards or vouchers.
 
 ## Learn more
 
diff --git a/docs/tutorials/en/creating-a-coupon-beta.md b/docs/tutorials/en/creating-a-coupon-beta.md
index 338b2c9da..8229139e5 100644
--- a/docs/tutorials/en/creating-a-coupon-beta.md
+++ b/docs/tutorials/en/creating-a-coupon-beta.md
@@ -71,9 +71,7 @@ The **General** section presents several fields you must fill in with general in
     * **Number of coupons:** Allows to define the number of codes generated in a coupon batch. The maximum number is 1000.
     * **Export coupons:** This button allows you to export the coupon codes within a coupon batch. This option only becomes available when editing already existing coupon batches.
 
-<div class="alert alert-warning">
-<p>You must define at least one UTM. This means it is required to fill in either the <strong>UTM source</strong> or the <strong>UTM campaign</strong> field. You can also fill in both fields.</p>
-</div>
+>⚠️ You must define at least one UTM. This means it is required to fill in either the **UTM source** or the **UTM campaign** field. You can also fill in both fields.
 
 ### Restrictions
 
@@ -83,9 +81,7 @@ In this section of the form, you can configure the following coupon usage restri
 
   If this option remains disabled, the coupon can be used for an unlimited number of times.
 
-  <div class="alert alert-warning">
-<p>In case an order with a limited usage coupon applied is canceled, the limit will be recalculated. This means that orders with the <strong>Canceled</strong> status will not be calculated into the coupon usage limit.</p>
-  </div>
+  >⚠️ In case an order with a limited usage coupon applied is canceled, the limit will be recalculated. This means that orders with the **Canceled** status will not be calculated into the coupon usage limit.
 
 ## Generated coupons
 
diff --git a/docs/tutorials/en/creating-a-coupon.md b/docs/tutorials/en/creating-a-coupon.md
index ac61f161c..0155f3485 100644
--- a/docs/tutorials/en/creating-a-coupon.md
+++ b/docs/tutorials/en/creating-a-coupon.md
@@ -30,9 +30,7 @@ This article will cover the following topics:
 
 ## Creating a coupon
 
-<div class="alert alert-warning">
-  <p>There is a limit to the amount of active coupons you can have in your store. We recommend reusing coupons, as having a high number of coupons can compromise the performance of the <b>Promotions & Taxes</b> module.</p>
-</div>
+>⚠️ There is a limit to the amount of active coupons you can have in your store. We recommend reusing coupons, as having a high number of coupons can compromise the performance of the **Promotions & Taxes** module.
 
 To create a coupon, follow the steps below:
 
@@ -41,9 +39,7 @@ To create a coupon, follow the steps below:
 3. Fill in the [coupon fields](#filling-in-coupon-fields).
 4. Click on `Save`.
 
-<div class="alert alert-info">
-  <p>You can only create one coupon at a time. To create coupons in bulk, read the article <a href="https://developers.vtex.com/vtex-rest-api/docs/creating-and-managing-coupons-with-promotions-api">Creating and managing coupons with the Promotions API</a>.</p>
-</div>
+>ℹ️ You can only create one coupon at a time. To create coupons in bulk, read the article [Creating and managing coupons with the Promotions API](https://developers.vtex.com/vtex-rest-api/docs/creating-and-managing-coupons-with-promotions-api).
 
 ### Filling in the coupon fields
 
@@ -53,9 +49,7 @@ In this section, you must fill in the coupon’s general information:
 
 - **Coupon Code**: the coupon’s activation code. This is a required field, and there is no character limit.
 
-<div class="alert alert-warning">
-  <p>You cannot use special characters, only letters, numbers and dashes.</p>
-</div>
+>⚠️ You cannot use special characters, only letters, numbers and dashes.
 
 - **utm_source**: the UTM source parameter.
 - **utm_campaign**: the UTM campaign parameter.
@@ -67,9 +61,7 @@ In this section, you can add restrictions on the use of a coupon.
 - **The customer may purchase up to X product(s), using this coupon in one or more purchases**: enter the number of products that can be purchased using this coupon, regardless of how many purchases are made to reach this number.
 - **Renew each coupon usage after X day(s)**: the coupon will be valid again after the number of days determined in this field.
 
-<div class="alert alert-info">
-  <p>To create single-use coupons, you need to <a href="https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327#4-restricoes-e-limitacoes-de-uso">restrict the number of promotion apps in your store and per customer</a>.</p>
-</div>
+>ℹ️ To create single-use coupons, you need to [restrict the number of promotion apps in your store and per customer](https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327#4-restricoes-e-limitacoes-de-uso).
 
 When customers apply a coupon for a limited promotion and their purchase is canceled, the coupon becomes valid again.
 
@@ -92,9 +84,7 @@ To disable a coupon, you must archive it. Follow the steps below:
 2. Click on the coupon you want to archive.
 3. On the editing screen, click on the `Archive` button.
 
-<div class="alert alert-warning">
-  <p>Coupons cannot be deleted, only archived. Note that you can only archive one coupon at a time. You can edit and reuse a coupon, but the <b>coupon code</b> cannot be modified.</p>
-</div>
+>⚠️ Coupons cannot be deleted, only archived. Note that you can only archive one coupon at a time. You can edit and reuse a coupon, but the **coupon code** cannot be modified.
 
 ## Application scenario
 
@@ -106,9 +96,7 @@ You need to create a promotion and publish it in a newsletter. However, we recom
 4. Include the coupon code in the newsletter.
 5. The promotion will be enabled in the shopping cart only when customers enter the coupon code in the **Coupon Code** field and add it.
 
-<div class="alert alert-info">
-  <p>You can also configure the newsletter links directly using <b>utm_source</b> and <b>utm_campaign</b>, instead of using a coupon.</p>
-</div>
+>ℹ️ You can also configure the newsletter links directly using **utm_source** and **utm_campaign**, instead of using a coupon.
 
 ## Using multiple coupons
 
diff --git a/docs/tutorials/en/creating-a-form-to-record-information-using-master-data-newsletter.md b/docs/tutorials/en/creating-a-form-to-record-information-using-master-data-newsletter.md
index 6c9062a4d..6cf4a9911 100644
--- a/docs/tutorials/en/creating-a-form-to-record-information-using-master-data-newsletter.md
+++ b/docs/tutorials/en/creating-a-form-to-record-information-using-master-data-newsletter.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-06-08-at-01-15-53
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/creating-a-product-collection.md b/docs/tutorials/en/creating-a-product-collection.md
index 0a64d12b6..f27fbfe5c 100644
--- a/docs/tutorials/en/creating-a-product-collection.md
+++ b/docs/tutorials/en/creating-a-product-collection.md
@@ -65,9 +65,7 @@ To create a product group with one of more brands, just select the brand desired
 
 To create a collection of products that have not yet been launched, select &#8220;Pré-venda&#8221; in &#8220;Outras Opções&#8221;. The system will consider all products with date beyond the current date, as defined in the field “Data de lançamento no mercado” (product register). Or, you can configure the collection to take into account recently launched products, by selection the &#8220;Lançamento&#8221; option. The system will consider all products with the date defined in the “Data de lançamento no mercado” (product register) field within the interval of 30 days prior to present day. See in the example below that it is possible to select one or other field. If you want both scenarios to be taken into account, create two collections and configure each of them with the respective collection.
 
-<div class="alert alert-warning">
-These flags are a <em>complement</em> to the choice of products. It is important to note that these flags will only work if you have chosen any category, brand, or combination of SKUs for the collection. These flags are to be used in conjunction with the selection of categories, brands or SKUs for the collection.
-</div>
+>⚠️ These flags are a *complement* to the choice of products. It is important to note that these flags will only work if you have chosen any category, brand, or combination of SKUs for the collection. These flags are to be used in conjunction with the selection of categories, brands or SKUs for the collection.
 
 ### Including specific SKUs in a group
 
diff --git a/docs/tutorials/en/creating-a-product-for-presale.md b/docs/tutorials/en/creating-a-product-for-presale.md
index 24b898ef3..1278b6ef3 100644
--- a/docs/tutorials/en/creating-a-product-for-presale.md
+++ b/docs/tutorials/en/creating-a-product-for-presale.md
@@ -34,15 +34,11 @@ To make a product available on presale, follow the steps below.
 5. Fill in the [remaining product fields](https://help.vtex.com/en/tutorial/product-registration-fields--4dYXWIK3zyS8IceKkQseke)
 6. Click `Save and add a new SKU`.
 7. On the SKU creation page, fill in the **Coming soon expected on** field with the date when the product will be available for delivery by the store in the `dd/mm/yyyy` format.
-<div class="alert alert-info">
-  <p>You need to consider both the launch date and the shipping cost to determine the arrival date: <code>final delivery time = delivery SLA + supply batch delivery time frame</code></p>  
-</div>
+>ℹ️ You need to consider both the launch date and the shipping cost to determine the arrival date: `final delivery time = delivery SLA + supply batch delivery time frame`
 8. Fill in the [remaining SKU fields](https://help.vtex.com/en/tutorial/sku-registration-fields--21DDItuEQc6mseiW8EakcY).
 9. Click `Save` to finish.
 
-<div class="alert alert-info">
-  <p>The presale item order should only be invoiced on or after the launch date, that is, when the product will be actually available in the inventory.</p>  
-</div>
+>ℹ️ The presale item order should only be invoiced on or after the launch date, that is, when the product will be actually available in the inventory.
 
 ## Scheduling prices
 To schedule your store's fixed prices for the presale of a product, follow the steps described in the article [Scheduling prices](https://help.vtex.com/en/tutorial/scheduling-prices--4vVha6TGzYkguWuMOqCcCk).  
diff --git a/docs/tutorials/en/creating-a-shipping-policy.md b/docs/tutorials/en/creating-a-shipping-policy.md
index b8ae29045..21acfa272 100644
--- a/docs/tutorials/en/creating-a-shipping-policy.md
+++ b/docs/tutorials/en/creating-a-shipping-policy.md
@@ -51,9 +51,7 @@ To create a shipping policy, follow the steps below:
         *   Select the `Day of the week` and the `Pickup time`.
         *   To add more days of the week, click on `Add pickup time`.
 
-<div class="alert alert-warning">
-The <b>Shipping Window</b> and <b>Pickup Time</b> are options that exclude each other since a period cannot simultaneously be allocated to different actions.
-</div> 
+>⚠️ The **Shipping Window** and **Pickup Time** are options that exclude each other since a period cannot simultaneously be allocated to different actions. 
 
 *   **[Scheduled delivery](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)**: this feature can be enabled if this service is included in your shipping policy. Here you must add the delivery windows that will be displayed to customers at checkout. To use this feature, click the toggle and fill in the following fields:
     *    **Maximum delivery time:** the maximum number of days to deliver a product.
diff --git a/docs/tutorials/en/creating-a-subscription-plan.md b/docs/tutorials/en/creating-a-subscription-plan.md
index f202df03a..fd474e0f5 100644
--- a/docs/tutorials/en/creating-a-subscription-plan.md
+++ b/docs/tutorials/en/creating-a-subscription-plan.md
@@ -23,9 +23,7 @@ There are two possible ways to create a subscription plan. The **most recommende
 
 Another possibility is to create a [SKU attachment related to the subscription in the Catalog](#sku-attachment-in-the-catalog) module. SKU attachments are equivalent to subscription plans.
 
-<div class="alert alert-warning">
-  <p>For this reason, you should <strong>not</strong> create both. Otherwise, the plan will be duplicated.</p>
-</div>
+>⚠️ For this reason, you should **not** create both. Otherwise, the plan will be duplicated.
 
 ## Creating a new plan in the Subscriptions module
 
@@ -37,9 +35,7 @@ Creating a new plan in the **Subscriptions** module is the most recommended opti
 4. Click on the [Associated Products](#associated-products) tab and select the products you want to associate with the subscription plan.
 5. Click on `Save`.
 
-<div class="alert alert-warning">
-  <p>By default, plans are saved as active, even if they do not have any associated products. Plans that do not have associated products are not available as an option for customers.</p>
-</div>
+>⚠️ By default, plans are saved as active, even if they do not have any associated products. Plans that do not have associated products are not available as an option for customers.
 
 ### Settings
 
@@ -68,9 +64,7 @@ To delete a previously created frequency, click on the <i class="far fa-trash-al
 
 You can provide multiple frequency options on the same plan. In this case, you should click the `Add frequency` button again and repeat the process by filling in the fields with the new frequency information. This way, customers can choose the frequency they prefer.
 
-<div class="alert alert-warning">
-  <p>You cannot assign a validity period to the subscription plan in the <strong>Subscriptions</strong> module. Only subscription plans configured as SKU attachments in the <strong>Catalog</strong> module can have validity periods configured.</p>
-</div>
+>⚠️ You cannot assign a validity period to the subscription plan in the **Subscriptions** module. Only subscription plans configured as SKU attachments in the **Catalog** module can have validity periods configured.
 
 ### Associated Products
 
diff --git a/docs/tutorials/en/creating-a-trade-policy.md b/docs/tutorials/en/creating-a-trade-policy.md
index c35690bd9..03b810e49 100644
--- a/docs/tutorials/en/creating-a-trade-policy.md
+++ b/docs/tutorials/en/creating-a-trade-policy.md
@@ -17,9 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 On VTEX, you can use [trade policies](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) to group catalog, price, promotion, inventory, shipping logistics, and payment settings for different sales channels. Sales channels include marketplaces, ecommerce websites, physical stores, or B2B stores, for example.  
 
-<div class="alert alert-danger">
-By default, new trade policies are applied to all active sellers. If you wish to apply them only to a specific group of sellers, please specify that in the ticket.
-</div>
+>❗ By default, new trade policies are applied to all active sellers. If you wish to apply them only to a specific group of sellers, please specify that in the ticket.
 
 ## Manage trade policies
 
@@ -34,9 +32,7 @@ To use the same catalog in more than one trade policy, access the
 
 To [request additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), contact our Growth Operations team through [VTEX Support](https://help.vtex.com/en/support) by selecting **Commercial** and `Create a trade policy`. When requesting the creation of a trade policy via ticket, consider a response time of up to three business days.
 
-<div class="alert alert-info">
-For the use of additional trade policy to integrate with <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a>, <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner">certified connectors (partners)</a>, or other VTEX stores to be exempt from fees, orders must be associated with it.
-</div>
+>ℹ️ For the use of additional trade policy to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), [certified connectors (partners)](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-certified-connector-partner), or other VTEX stores to be exempt from fees, orders must be associated with it.
 
 ## Learn more
 
diff --git a/docs/tutorials/en/creating-a-type-of-list.md b/docs/tutorials/en/creating-a-type-of-list.md
index 676847439..acd30f83c 100644
--- a/docs/tutorials/en/creating-a-type-of-list.md
+++ b/docs/tutorials/en/creating-a-type-of-list.md
@@ -26,9 +26,7 @@ Creating a type of list is configuring the lists to appear on the site. For exam
 
 After creating the types of list, clients can add their lists to the site.
 
-<div class="alert alert-warning">
-  <p>It is not possible to delete a list once it has been created.</p>
-</div>
+>⚠️ It is not possible to delete a list once it has been created.
 
 ## Form fields
 
diff --git a/docs/tutorials/en/creating-an-oauth2-authentication.md b/docs/tutorials/en/creating-an-oauth2-authentication.md
index 7f8e4739e..b77d3232f 100644
--- a/docs/tutorials/en/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/en/creating-an-oauth2-authentication.md
@@ -21,7 +21,7 @@ In some circumstances, you may want to create an additional authentication in VT
 
 To match those needs, VTEX provides a VTEX ID integrated __authentication OAuth2__ .
 
-<div class="alert alert-warning">As this is a complicated technical matter, we recommend that you consult a partner or IT team.</div>
+>⚠️ As this is a complicated technical matter, we recommend that you consult a partner or IT team.
 
 ### About OAuth2
 
@@ -155,7 +155,7 @@ Response:
 
 As soon as the service is developed and published, you can send the above-mentioned data to VTEX (by opening a ticket). VTEX will then be able to complete environment integration with VTEX ID, providing your store with another login option.
 
-<div class="alert alert-info">If you have multiple stores (subaccounts) listed in <strong>Account Settings > Account management > Account</strong>, please note that each one will require their own OAuth2 Identity Provider configuration.</div>
+>ℹ️ If you have multiple stores (subaccounts) listed in **Account Settings > Account management > Account**, please note that each one will require their own OAuth2 Identity Provider configuration.
 
 Important things to remember:
 
diff --git a/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
index afaf02dbb..ce172d4fc 100644
--- a/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/en/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -23,9 +23,7 @@ To apply different prices to products via XML, you must associate a SKU price ta
   3. Here, you must check if the fields related to SKU price (lowest product price, highest product price, original SKU price, current SKU price and current SKU price + taxes) are filled in. For the operation to work correctly, at least one of these fields must contain information.
   4. Fill in the **Price tables ** field with the name of the desired price table. Then, click on the check box corresponding to the tag in the column **Show content**. The selected price table must have fixed prices registered. Otherwise, the configuration will not be performed.
 ![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
-<div class="alert alert-warning">
-  <p>Once the price table is included in the XML, all price fields will be overwritten.</p>
-</div>
+>⚠️ Once the price table is included in the XML, all price fields will be overwritten.
   5. Click on `Save`.
 
 Thus, the platform will associate the values in the price table with the products registered in the XML file collection.
diff --git a/docs/tutorials/en/creating-appkeys-and-apptokens-to-authenticate-integrations.md b/docs/tutorials/en/creating-appkeys-and-apptokens-to-authenticate-integrations.md
index 293e8c29b..f82fd63ce 100644
--- a/docs/tutorials/en/creating-appkeys-and-apptokens-to-authenticate-integrations.md
+++ b/docs/tutorials/en/creating-appkeys-and-apptokens-to-authenticate-integrations.md
@@ -17,8 +17,7 @@ subcategory: 4uqMnZjwBO04uWgCom8QiA
 
 Every VTEX API integration needs to authenticate through appKey and appToken.
 
-<div class="alert alert-warning">Only the <b>Master user</b> of the store has permission to deal with tokens. The Master user is the one whose email is in the <b>Contact</b> section of the Accounts screen, in Account management.
-</div>
+>⚠️ Only the **Master user** of the store has permission to deal with tokens. The Master user is the one whose email is in the **Contact** section of the Accounts screen, in Account management.
 
 To create these keys, follow these steps:
 
@@ -30,8 +29,7 @@ To create these keys, follow these steps:
 6. Click on __Generate new Tokens__.
 7. The token is in the field that is shown next. For a matter of safety, __it is shown only once__. Copy this token and save it in a safe place.
 
-<div class="alert alert-warning"><strong>Attention</strong>: every appKey and appToken pair, once is created, is born without link to an access profile. So, after creating it, you should link it to the correspondent access profile.
-</div>
+>⚠️ **Attention**: every appKey and appToken pair, once is created, is born without link to an access profile. So, after creating it, you should link it to the correspondent access profile.
 
 For that, follow these steps:
 
diff --git a/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md b/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md
index ada0394d0..7ab7e56e4 100644
--- a/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md
+++ b/docs/tutorials/en/creating-customer-and-address-forms-in-new-stores.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 In Master Data, customer and address forms are not created by default for all new stores. They are available only in the main store account. This occurs whenever multi-stores are created.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 You can produce these forms automatically, following the instructions below for each store.
 
diff --git a/docs/tutorials/en/creating-data-entity.md b/docs/tutorials/en/creating-data-entity.md
index 53d83a265..113120e0f 100644
--- a/docs/tutorials/en/creating-data-entity.md
+++ b/docs/tutorials/en/creating-data-entity.md
@@ -23,21 +23,16 @@ For example, imagine the system that controls a library. This system controls bo
 
 Considering these concepts, it is possible to set up several data control scenarios in the Master Data. By default, the following data entities are considered: Customer, Address, Stores etc. You may create as many data entities as you wish in order to develop a customized environment according to the needs of your store.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Understanding the types
 
diff --git a/docs/tutorials/en/creating-landing-pages.md b/docs/tutorials/en/creating-landing-pages.md
index f3eb5a0d8..a1e53b8a1 100644
--- a/docs/tutorials/en/creating-landing-pages.md
+++ b/docs/tutorials/en/creating-landing-pages.md
@@ -21,10 +21,7 @@ In the Admin, you can create customized landing pages, such as pages for special
 
 1. In the VTEX Admin, access **Storefront > Pages**
 
-<div class="alert alert-warning">
-<p>If your store has multiple trade policies or is a cross-border store, select the <a href="https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W">binding</a> corresponding to the store to which you want to add a new landing page using the dropdown menu displayed at the top right.
-</p>
-</div>
+>⚠️ If your store has multiple trade policies or is a cross-border store, select the [binding](https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W) corresponding to the store to which you want to add a new landing page using the dropdown menu displayed at the top right.
 
 2.Click **CREATE NEW**.
 
@@ -40,10 +37,7 @@ In the Admin, you can create customized landing pages, such as pages for special
 | Description | Summary of the new web page to be displayed in search engine result pages. |
 | Keywords | Topics that define the page content and  help deliver the page to interested users in search engine results. |
 
-<div class="alert alert-warning">
-<p>To avoid conflicts and protect the integrity of the system, changing an existing URL route is not allowed. If you need to change a URL, we recommend creating a new page with the desired path and deactivating the old one if necessary.
-</p>
-</div>
+>⚠️ To avoid conflicts and protect the integrity of the system, changing an existing URL route is not allowed. If you need to change a URL, we recommend creating a new page with the desired path and deactivating the old one if necessary.
 
 <div class = "alert alert-info">
 <p>The five fields above have a direct impact on store hits and search engine results rankings. Before filling in the page metadata, keep SEO best practices in mind.
diff --git a/docs/tutorials/en/creating-merchandising-rules-manual-editor.md b/docs/tutorials/en/creating-merchandising-rules-manual-editor.md
index c930cff02..d3d048911 100644
--- a/docs/tutorials/en/creating-merchandising-rules-manual-editor.md
+++ b/docs/tutorials/en/creating-merchandising-rules-manual-editor.md
@@ -33,9 +33,7 @@ Follow the steps below to configure a [merchandising rule](https://help.vtex.com
    Add one or more conditions to apply the desired customization effect in this step. To learn how to add a condition, see [Merchandising rule conditions](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
 10. Click `Save`.
 
-<div class="alert alert-info">
-  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
-</div>
+>ℹ️ After saving, the changes to merchandising rules will take an average of two minutes to be updated.
 
 ## Example
 
@@ -75,18 +73,12 @@ Imagine the following example: You want to promote Beautyx products during the 4
 
 * **Remove**: Deletes the selected conditions from the result, so it removes products that would be displayed in the search results.
 
-  <div class="alert alert-info">
-  <p><strong>Add</strong> and <strong>Remove</strong> are compatible with other sorting types, not based on the configured relevance. So, suppose you add or remove a product using a merchandising rule, and the customer sorts the search results by price. In that case, the products will be sorted by price, and the products displayed will follow the merchandising rule.</p>
-  </div>
+  >ℹ️ **Add** and **Remove** are compatible with other sorting types, not based on the configured relevance. So, suppose you add or remove a product using a merchandising rule, and the customer sorts the search results by price. In that case, the products will be sorted by price, and the products displayed will follow the merchandising rule.
 
 * **Promote**: Highlights selected conditions in the result, giving more relevance to a product normally displayed in the search results. The order of the conditions affects the priority in which they are displayed. Besides, a product added to this field is only promoted in one result.
 
 * **Demote**: Hides the selected conditions in the result. This allows you to deprioritize a product normally displayed in the search results.
 
-  <div class="alert alert-info">
-  <p><strong>Promote</strong> and <strong>Demote</strong> only work when your customers sort the search results by relevance. If they sort it by price, the products will be sorted strictly by price, and the merchandising rule will not be applied.</p>
-  </div>
+  >ℹ️ **Promote** and **Demote** only work when your customers sort the search results by relevance. If they sort it by price, the products will be sorted strictly by price, and the merchandising rule will not be applied.
 
-  <div class="alert alert-warning">
-  <p>Do not set conditions that will affect the same products in the <strong>Promote</strong> and <strong>Demote</strong> sections, since these are opposite effects. This misconfiguration negatively influences the feature's behavior and does not produce the desired results.</p>
-  </div>
+  >⚠️ Do not set conditions that will affect the same products in the **Promote** and **Demote** sections, since these are opposite effects. This misconfiguration negatively influences the feature's behavior and does not produce the desired results.
diff --git a/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
index ff81e260e..52f089eee 100644
--- a/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/en/creating-merchandising-rules-visual-editor-beta.md
@@ -15,9 +15,7 @@ legacySlug: creating-merchandising-rules-visual-editor-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>This feature is in closed beta, which means that only selected customers can access it for now. If you are interested in implementing it for your business in the future, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a>.</p>
-</div>
+>ℹ️ This feature is in closed beta, which means that only selected customers can access it for now. If you are interested in implementing it for your business in the future, please contact our [Support team](https://support.vtex.com/hc/pt-br/requests).
 
 To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) using[ Visual Editor](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), follow the steps below.
 
@@ -48,9 +46,7 @@ To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.co
       Learn more about these actions in items **IV, V, VI, VIII, IX**, and **XI** of the [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section.
 9.	Click `Save`.
 
-<div class="alert alert-info">
-  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
-</div>
+>ℹ️ After saving, the changes to merchandising rules will take an average of two minutes to be updated.
 
 ## Actions available in the Visual Editor
 
diff --git a/docs/tutorials/en/creating-merchandising-rules-visual-editor.md b/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
index aa33eadd7..3f2b5179e 100644
--- a/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
+++ b/docs/tutorials/en/creating-merchandising-rules-visual-editor.md
@@ -44,9 +44,7 @@ To configure a VTEX Intelligent Search [merchandising rule](https://help.vtex.co
       Learn more about these actions in items **IV, V, VI, VIII, IX**, and **XI** of the [Actions available in the Visual Editor](#actions-available-in-the-visual-editor) section.
 9.	Click `Save`.
 
-<div class="alert alert-info">
-  <p>After saving, the changes to merchandising rules will take an average of two minutes to be updated.</p>
-</div>
+>ℹ️ After saving, the changes to merchandising rules will take an average of two minutes to be updated.
 
 ## Actions available in the Visual Editor
 
diff --git a/docs/tutorials/en/creating-pickup-points.md b/docs/tutorials/en/creating-pickup-points.md
index 8efe67328..b054020e6 100644
--- a/docs/tutorials/en/creating-pickup-points.md
+++ b/docs/tutorials/en/creating-pickup-points.md
@@ -24,9 +24,7 @@ There are two ways to create a pickup point in the Admin:
 * [Creating pickup points individually](#creating-pickup-points-individually)
 * [Creating pickup points using the template](#reating-pickup-points-using-the-template)
 
-<div class="alert alert-warning">
-Creating pickup points is one of the steps required for the feature to work properly. Please refer to the article <a href="https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R">pickup points</a> to see the other <a href="https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R#setup">settings necessary</a> to make pickup points available to your customers.
-</div>
+>⚠️ Creating pickup points is one of the steps required for the feature to work properly. Please refer to the article [pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R) to see the other [settings necessary](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R#setup) to make pickup points available to your customers.
 
 ## Creating pickup points individually
 
@@ -43,9 +41,7 @@ Creating pickup points is one of the steps required for the feature to work prop
 * **ID:** identification of the pickup point. If this field is not filled in, the system will choose an ID automatically. Do not use space characters.
 * **Third-party pickup point:** check this box if the pickup point is not related to your store. Third-party pickup points are displayed with less relevance than those of your own store.
 
-  <div class="alert alert-danger">
-The <b>Third-party pickup point</b> configuration currently is not available.
-</div>
+  >❗ The **Third-party pickup point** configuration currently is not available.
 
 Select <i class="fas fa-toggle-on"></i> to activate the pickup point.
 
@@ -73,9 +69,7 @@ The address information and the location on the map will be displayed at checkou
     4. Fill in the day and time;
     5. Click on `Add`.
 
-<div class="alert alert-warning">
-The business hours defined for a pickup point are for informative purposes only and are not used for SLA calculation. To change the settings that influence the delivery time frame, please specify the business hours in the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140">shipping policy</a> related to the pickup point. Holidays must be configured on the <a href="https://help.vtex.com/en/tutorial/registering-holidays--2ItOthSEAoyAmcwsuiO6Yk">Holidays page</a>, so that they can be considered in the delivery time calculation.
-</div>
+>⚠️ The business hours defined for a pickup point are for informative purposes only and are not used for SLA calculation. To change the settings that influence the delivery time frame, please specify the business hours in the [shipping policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140) related to the pickup point. Holidays must be configured on the [Holidays page](https://help.vtex.com/en/tutorial/registering-holidays--2ItOthSEAoyAmcwsuiO6Yk), so that they can be considered in the delivery time calculation.
 
 ## Creating pickup points using the template
 
diff --git a/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
index 1690ae7f6..21311a6c8 100644
--- a/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/en/creating-promotion-for-a-customer-cluster.md
@@ -33,9 +33,7 @@ After configuring the property, follow the instructions below.
 6. Fill in the field with the cluster you would like to link to the promotion. [See below for more information on how to fill in this field.](#filling-in-the-customer-cluster-field) You can add more than one cluster by clicking on the `+` button.
 7. Click on `Save`.
 
-<div class="alert alert-info">
-<p>You can enter a maximum of 50 clusters in the <strong>Customer cluster</strong> option.</p>
-</div>
+>ℹ️ You can enter a maximum of 50 clusters in the **Customer cluster** option.
 
 ## Filling in the Customer cluster field
 
@@ -60,9 +58,7 @@ You could also configure `employee=false`, where only `employee` entries with th
 
 Given a field of type **[Varchar](https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265)**, we could configure `employee="yes"` so that only customers with the value `"yes"` in the field receive the promotion.
 
-<div class="alert alert-warning">
-  <p>For fields of type <strong>Varchar</strong>, the value entered in the <strong>Customer cluster</strong> section of the promotion is case-sensitive. This means that if you fill in the option <strong>Customer cluster</strong> in a way that differs from the one determined for the field in the Master Data, the promotion will not be applied.</p>
-</div>
+>⚠️ For fields of type **Varchar**, the value entered in the **Customer cluster** section of the promotion is case-sensitive. This means that if you fill in the option **Customer cluster** in a way that differs from the one determined for the field in the Master Data, the promotion will not be applied.
 
 Therefore, considering the above example of a field of type **Varchar** with the values `"yes"` and `"no"`, the entry in the promotion must be `employee="yes"`. When entering, for example, `employee="Yes"` in the promotion, the customer cluster will not receive the promotion.
 
diff --git a/docs/tutorials/en/creating-roles.md b/docs/tutorials/en/creating-roles.md
index 858583bd1..4c06bae98 100644
--- a/docs/tutorials/en/creating-roles.md
+++ b/docs/tutorials/en/creating-roles.md
@@ -26,9 +26,7 @@ Check the steps for each of these options below:
 
 We recommend creating roles that are analogous to the store's hierarchical structures. This approach ensures that all employees are accountable for the information they have access to. Best practices for managing roles not only increase operational security but also heighten the awareness of those handling sensitive store data and customer information.
 
-<div class="alert alert-warning">
-  <p>Unrestricted use of overly permissive roles increases the risk of store attacks through leaked login credentials.</p>
-</div>
+>⚠️ Unrestricted use of overly permissive roles increases the risk of store attacks through leaked login credentials.
 
 ## Using predefined roles
 
@@ -75,9 +73,7 @@ To create a custom role that meets the access needs of a group of users, follow
     You can add resources from as many products as you need to the role.
 7. Type a name for the custom role in the **Role name** field.
 
-  <div class="alert alert-warning">
-    <p>Choose descriptive names for the roles, clearly indicating the type of user who should have access. We recommend indicating the position in the company or the activity to be carried out on the platform.</p>
-  </div>
+  >⚠️ Choose descriptive names for the roles, clearly indicating the type of user who should have access. We recommend indicating the position in the company or the activity to be carried out on the platform.
 8. Add admin users to the role by entering the user email address in **Add users to this role** and then click `Add`.
 
     ![Role users](https://images.ctfassets.net/alneenqid6w5/1lSnygEawddufMz9IZ45Mj/3d41ef2c9033f8f3add993039c4d8560/usuarios-en.PNG)
diff --git a/docs/tutorials/en/creating-service-for-a-sku.md b/docs/tutorials/en/creating-service-for-a-sku.md
index 6dc030015..5726272cd 100644
--- a/docs/tutorials/en/creating-service-for-a-sku.md
+++ b/docs/tutorials/en/creating-service-for-a-sku.md
@@ -86,9 +86,7 @@ To link a service to a SKU, please follow the steps below:
 ### Template fields
 Use the template carefully, always making sure that the information is correctly filled in. In order to avoid errors, all fields in the template must be filled in.
 
-<div class="alert alert-warning">
-  <p>When filling the spreadsheet, do not change or delete the column headings in row 1. Fill in the desired values in the rows after the column headings for the import to work correctly.</p>
-</div>  
+>⚠️ When filling the spreadsheet, do not change or delete the column headings in row 1. Fill in the desired values in the rows after the column headings for the import to work correctly.  
 
 - **Nome Serviço:** name of the service.
 - **Texto Serviço:** text that will be displayed along with the service.
diff --git a/docs/tutorials/en/creating-synonyms.md b/docs/tutorials/en/creating-synonyms.md
index 204c01fd8..5ce206008 100644
--- a/docs/tutorials/en/creating-synonyms.md
+++ b/docs/tutorials/en/creating-synonyms.md
@@ -41,9 +41,7 @@ Follow the step-by-step procedure to configure synonyms individually in the VTEX
 
 Changes can take up to two hours to take effect.
 
-<div class="alert alert-info">
-<p> This feature is available on VTEX Intelligent Search Multilanguage. Read our article <a href="https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#synonyms">VTEX Intelligent Search: Multilanguage settings (Beta)</a>to learn more.</p>
-</div>
+>ℹ️ This feature is available on VTEX Intelligent Search Multilanguage. Read our article [VTEX Intelligent Search: Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/vtex-intelligent-search-multilanguage-settings-beta--2WahlTESLXIJ9XBdQMdTYO#synonyms)to learn more.
 
 ## Importing CSV spreadsheet
 
@@ -90,7 +88,5 @@ Stores using  [Multilanguage settings (Beta)](https://help.vtex.com/en/tutorial/
     __Example:__
     - `tv,smart tv;true;en-GB`: When searching for one of these terms in the store in English (`locale en-GB`), the search results will return any product that contains one of these terms.
 
-<div class="alert alert-warning">
-  <p>If the imported .csv file does not have the <code>locale</code>, the synonym will be valid for all languages available in the store.</p>
-</div>
+>⚠️ If the imported .csv file does not have the `locale`, the synonym will be valid for all languages available in the store.
 
diff --git a/docs/tutorials/en/creating-the-files-structure-for-your-app-vtex-init.md b/docs/tutorials/en/creating-the-files-structure-for-your-app-vtex-init.md
index 1da37de62..389623012 100644
--- a/docs/tutorials/en/creating-the-files-structure-for-your-app-vtex-init.md
+++ b/docs/tutorials/en/creating-the-files-structure-for-your-app-vtex-init.md
@@ -33,8 +33,6 @@ IO will ask you a few questions in order to define important parameters for your
 
 IO will confirm that your manifest.json has been successfully generated and asks for the VTEX service that you want to use. 
 
-<div class="alert alert-info">
-For front-end development, the service should be react
-</div>
+>ℹ️ For front-end development, the service should be react
 
 Done! Your files and folders structure will be created.
diff --git a/docs/tutorials/en/creating-trigger-in-master-data.md b/docs/tutorials/en/creating-trigger-in-master-data.md
index fa454b318..adda56db3 100644
--- a/docs/tutorials/en/creating-trigger-in-master-data.md
+++ b/docs/tutorials/en/creating-trigger-in-master-data.md
@@ -15,9 +15,7 @@ legacySlug: creating-trigger-in-master-data
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
-<div class="alert alert-info">
-<p>This article is about Master Data v1. If you want to use Master Data v2, see the steps in the guide <a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2">Setting up triggers in Master Data v2</a>.</p>
-</div>
+>ℹ️ This article is about Master Data v1. If you want to use Master Data v2, see the steps in the guide [Setting up triggers in Master Data v2](https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2).
 
 Conceptually, a trigger is a programming resource that performs a specific action whenever an associated event occurs. In Master Data, a trigger consists of configuring one or more events that activate when a particular situation occurs based on different variables.
 
@@ -122,9 +120,7 @@ In this section, you must set the conditions that will fire the event(s) configu
 
    ![filters-en](https://images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/c0d93fda52ba199ee2101c62028d1c33/filters-en.png)
 
-<div class="alert alert-info">
-  <p>Master Data v1 does not allow the configuration of trigger reattempts, unlike Master Data v2.</p>
-</div>
+>ℹ️ Master Data v1 does not allow the configuration of trigger reattempts, unlike Master Data v2.
 
 ### Schedule
 
diff --git a/docs/tutorials/en/credit-card-basic-payment-flow.md b/docs/tutorials/en/credit-card-basic-payment-flow.md
index bf3128afc..75e125003 100644
--- a/docs/tutorials/en/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/en/credit-card-basic-payment-flow.md
@@ -27,8 +27,6 @@ This article aims to explain how the basic flow of a __credit card__ payment wor
 
 With the response from the issuing bank, the reverse flow is performed and the __Payment Gateway__ receives the information if the payment has been approved or denied.
 
-<div class="alert alert-info">
-You can include the <strong>Anti-Fraud</strong> in this stream. In such case, the anti-fraud receives the gateway information that the payment was pre-authorized by the issuing bank. With the information received from the gateway, the anti-fraud sends a payment approval or denial as response. If the anti-fraud denies, the payment is canceled. If the payment is approved, the order may continue its normal flow.
-</div>
+>ℹ️ You can include the **Anti-Fraud** in this stream. In such case, the anti-fraud receives the gateway information that the payment was pre-authorized by the issuing bank. With the information received from the gateway, the anti-fraud sends a payment approval or denial as response. If the anti-fraud denies, the payment is canceled. If the payment is approved, the order may continue its normal flow.
 
 
diff --git a/docs/tutorials/en/credit-control-overview.md b/docs/tutorials/en/credit-control-overview.md
index 426881b0f..b391c6808 100644
--- a/docs/tutorials/en/credit-control-overview.md
+++ b/docs/tutorials/en/credit-control-overview.md
@@ -15,10 +15,8 @@ legacySlug: credit-control-overview
 subcategory: 7EWKfPIGfmI0G8iMYK8Aiy
 ---
 
-<div class="alert alert-warning">
-<strong>WARNING:</strong> Credit Control is unavailable as of <strong> December 2018</strong>. Now, to offer credit as a payment method right on your store's checkout, you need to use <a href="https://help.vtex.com/en/tutorial/customer-credit-overview">Customer Credit</a>.</br>
-Learn more about the Customer Credit's setup process on this <a href="http://help.vtex.com/en/tracks/customer-credit-getting-started">article</a>. 
-</div>
+>⚠️ **WARNING:** Credit Control is unavailable as of ** December 2018**. Now, to offer credit as a payment method right on your store's checkout, you need to use [Customer Credit](https://help.vtex.com/en/tutorial/customer-credit-overview).</br>
+> Learn more about the Customer Credit's setup process on this [article](http://help.vtex.com/en/tracks/customer-credit-getting-started).
 
 
 ## What it is
diff --git a/docs/tutorials/en/criar-um-produto-beta.md b/docs/tutorials/en/criar-um-produto-beta.md
index eba98f530..833faee66 100644
--- a/docs/tutorials/en/criar-um-produto-beta.md
+++ b/docs/tutorials/en/criar-um-produto-beta.md
@@ -15,7 +15,7 @@ legacySlug: criar-um-produto-beta
 subcategory: 
 ---
 
-<div class="alert alert-info">This feature is currently in beta, which means we are working on improving it. If you have any questions, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a>.</div>
+>ℹ️ This feature is currently in beta, which means we are working on improving it. If you have any questions, please contact our [Support team](https://support.vtex.com/hc/pt-br/requests).
 
 The **Add Product (Beta)** page allows you to create and edit[ products](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) and their corresponding [SKUs](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) in the VTEX Admin. To add a new product, follow the steps below.
 
@@ -36,7 +36,7 @@ If you want to create a product as inactive, click the <i class="fas fa-toggle-o
 
 After that, the product will be activated and available in your store.
 
-<div class="alert alert-info">If the product is not visible on your store after creating it, read the <a href="https://Why is the product not visible on the website?">Why is the product not visible on the website?</a> article to find out how to solve this problem.</div>
+>ℹ️ If the product is not visible on your store after creating it, read the [Why is the product not visible on the website?](https://Why is the product not visible on the website?) article to find out how to solve this problem.
 
 ## Product
 
@@ -130,7 +130,7 @@ Under **Attributes**, the [specification groups](https://help.vtex.com/en/tutori
 
 In this tab, you will add the [SKUs](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) that will be linked to the product you created earlier.
 
-<div class="alert alert-info"> A product must have at least one active SKU to be available in your store. The SKU must have an image attached to it for it to be activated. </div>
+>ℹ️ A product must have at least one active SKU to be available in your store. The SKU must have an image attached to it for it to be activated.
 
 ### Specifications
 This is where the previously created [specifications](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/2NQoBv8m4Yz3oQaLgDRagP) for the SKUs will be displayed. If you have created any required SKU fields, the SKU will only be activated once this specification has been completed.
@@ -146,8 +146,7 @@ This is where the previously created [specifications](https://help.vtex.com/en/t
 
 ### Images
 
-<div class="alert alert-warning">
-SKUs must have at least one image to be active.</div>
+>⚠️ SKUs must have at least one image to be active.
 
 To add an image to your SKU, follow the steps below:
 
@@ -155,8 +154,7 @@ To add an image to your SKU, follow the steps below:
 2. Add the link to your image in the 🔗 field. You can add more than one image to your SKU. To do this, click `+ Add Image` and add the new link. ![image6](https://images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
 3. Click `Save`.
 
-<div class="alert alert-info">The first image added will be the main image of the SKU and will be displayed in the store and search results.
-</div>
+>ℹ️ The first image added will be the main image of the SKU and will be displayed in the store and search results.
 
 You can edit an image's metadata by clicking the &lt;i class="fas fa-ellipsis-v">&lt;/i> button and selecting <i class="fas fa-pencil-alt"></i>` Edit Metadata`.
 
diff --git a/docs/tutorials/en/crm-zen-suiteshare.md b/docs/tutorials/en/crm-zen-suiteshare.md
index bdfcdc8ae..0142c9373 100644
--- a/docs/tutorials/en/crm-zen-suiteshare.md
+++ b/docs/tutorials/en/crm-zen-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: crm-zen-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/custom-product-fields.md b/docs/tutorials/en/custom-product-fields.md
index 4611ab85f..099efc956 100644
--- a/docs/tutorials/en/custom-product-fields.md
+++ b/docs/tutorials/en/custom-product-fields.md
@@ -15,6 +15,4 @@ legacySlug: custom-product-fields
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning">
-This is a regional exclusive content not applicable to English speaking countries.
-</div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tutorials/en/customer-credit-overview.md b/docs/tutorials/en/customer-credit-overview.md
index b192e8da5..bb996f073 100644
--- a/docs/tutorials/en/customer-credit-overview.md
+++ b/docs/tutorials/en/customer-credit-overview.md
@@ -34,9 +34,7 @@ Using the VTEX Admin or [Customer Credit API](https://developers.vtex.com/docs/a
 - Configure deadlines and installments for invoices documents
 - Monitor and modify the status of issued invoices
 
-<div class="alert alert-info">
-When installed, Customer Credit appears as a payment option at Checkout only for customers selected by the retailer, displaying the amount of credit available to be used for the purchase.
-</div>
+>ℹ️ When installed, Customer Credit appears as a payment option at Checkout only for customers selected by the retailer, displaying the amount of credit available to be used for the purchase.
 
 See below the basic flow of how Customer Credit works in VTEX stores:
 
@@ -52,9 +50,7 @@ To use Customer Credit as a payment method for a purchase, the customer must hav
 
 Each account has a credit limit registered at the time of opening. This limit indicates the maximum amount that the customer can use to make one or more purchases at the same time via Customer Credit.
 
-<div class="alert alert-warning">
-An account's credit limit can be changed by the retailer at any time.
-</div>
+>⚠️ An account's credit limit can be changed by the retailer at any time.
 
 ### Available credit
 
@@ -62,9 +58,7 @@ Amount that the customer still has available in their account to make purchases
 
 Every time the customer completes a purchase and the order is billed, the amount of available credit decreases. However, after the customer makes payment for the issued invoice, the available credit value returns to the pre-purchase value.
 
-<div class="alert alert-warning">
-At the time of a purchase, the customer has visibility of how much credit can be used via Customer Credit. If the purchase value is greater than the available credit, payment cannot be made through Customer Credit.
-</div>
+>⚠️ At the time of a purchase, the customer has visibility of how much credit can be used via Customer Credit. If the purchase value is greater than the available credit, payment cannot be made through Customer Credit.
 
 ### Invoice
 
@@ -82,9 +76,7 @@ After the customer makes the purchase using Customer Credit, the payment is appr
 
 The flow in Customer Credit is similar to that of credit cards in regarding order modifications. When an order value change occurs during the pre-authorization period, the credit amount changes.
 
-<div class="alert alert-warning">
-If it is necessary to change an order to reduce its value after the settlement period (issuance of invoices), the system will update the invoices to the new value. If the order value is increased, the system will create new invoices.
-</div>
+>⚠️ If it is necessary to change an order to reduce its value after the settlement period (issuance of invoices), the system will update the invoices to the new value. If the order value is increased, the system will create new invoices.
 
 ## Installation and configuration
 
diff --git a/docs/tutorials/en/customizar-a-toolbar-de-televendas.md b/docs/tutorials/en/customizar-a-toolbar-de-televendas.md
index cde7b0c99..3b427e96e 100644
--- a/docs/tutorials/en/customizar-a-toolbar-de-televendas.md
+++ b/docs/tutorials/en/customizar-a-toolbar-de-televendas.md
@@ -15,7 +15,7 @@ legacySlug: customizar-a-toolbar-de-televendas
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-warning">It is not recommended changing the height of the toolbar element. If your store has a fixed header on top of the screen, it should receive the <code>top</code> css property with the necessary height not to overlap with the callcenter toolbar.</div>
+>⚠️ It is not recommended changing the height of the toolbar element. If your store has a fixed header on top of the screen, it should receive the `top` css property with the necessary height not to overlap with the callcenter toolbar.
 
 The new callcenter toolbar can be customized with the styles of your store or using JavaScript. To overwrite the original styles of the toolbar, do the customization in a **.css** or **.js** file and load it into the page template.
 
diff --git a/docs/tutorials/en/customize-suiteshare.md b/docs/tutorials/en/customize-suiteshare.md
index ff957940f..44c1ced59 100644
--- a/docs/tutorials/en/customize-suiteshare.md
+++ b/docs/tutorials/en/customize-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: customize
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md b/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md
index db0ef9fe3..4888c2c97 100644
--- a/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md
+++ b/docs/tutorials/en/customizing-the-checkout-confirmation-pages.md
@@ -40,7 +40,7 @@ It's important to notice that the customization with templates is the same for O
 
 ### Customizing styles
 
-<div class="alert alert-warning">All these forms of customization may be changed in the future. By using them, you understand that your store must track platform updates so that your customization continues to function properly.</div>
+>⚠️ All these forms of customization may be changed in the future. By using them, you understand that your store must track platform updates so that your customization continues to function properly.
 
 You can also edit the Checkout Confirmation interface via CSS classes. Your styles should be added in a `<style>` tag in one of the HTML templates loaded on the page.
 
diff --git a/docs/tutorials/en/customizing-the-my-orders-section.md b/docs/tutorials/en/customizing-the-my-orders-section.md
index 51db7d144..a3649474c 100644
--- a/docs/tutorials/en/customizing-the-my-orders-section.md
+++ b/docs/tutorials/en/customizing-the-my-orders-section.md
@@ -21,16 +21,16 @@ It's already available in beta environment (`accountname.vtexcommercebeta.com.br
 
 See below a list of the classes available to aid in the customization.
 
-<div class="alert alert-warning">
-Interface customizations <strong>are not officially supported by VTEX</strong>.
-<br />
-<br /> 
-These classes and configurations can be changed or removed in future updates. As a best practice, we recommed treating javascript errors so your customization code won't break in case any class is removed in the future.
-</div>
-
-<div class="alert alert-info">
-If you already have a customization file for the previous version of the My Orders, we recommend you put the new customization in a separate file.
-</div>
+>⚠️ Interface customizations **are not officially supported by VTEX**.
+>
+>
+> 
+>
+>
+>  
+> These classes and configurations can be changed or removed in future updates. As a best practice, we recommed treating javascript errors so your customization code won't break in case any class is removed in the future.
+
+>ℹ️ If you already have a customization file for the previous version of the My Orders, we recommend you put the new customization in a separate file.
 
 ### Order list
 
diff --git a/docs/tutorials/en/customizing-your-stores-typography.md b/docs/tutorials/en/customizing-your-stores-typography.md
index 7b717cf84..791974451 100644
--- a/docs/tutorials/en/customizing-your-stores-typography.md
+++ b/docs/tutorials/en/customizing-your-stores-typography.md
@@ -18,9 +18,7 @@ subcategory: 5HsDDU48ZP58JHWU3WbCPc
 The typography of your store website is a tool to communicate your brand identity to your clients. 
 In the Admin, you have the flexibility to customize your store’s typography to suit to your business needs.
 
-<div class="alert alert-warning">
-  <p>Keep in mind that changes to your store typography in the <b>Storefront</b> overwrite the typography changes made in your store code. Please contact your development team and make sure the changes will be done in the Storefront or through your store's code.</p>
-</div>
+>⚠️ Keep in mind that changes to your store typography in the **Storefront** overwrite the typography changes made in your store code. Please contact your development team and make sure the changes will be done in the Storefront or through your store's code.
 
 ## Adding custom font families
 
@@ -33,9 +31,7 @@ In the Admin, you have the flexibility to customize your store’s typography to
 
 4. Then, click **Add custom font** and upload the desired font file. In the **Font Family** input field, enter a name for the font.
 
-<div class="alert alert-warning">
-  <p>The font family file must be uploaded in the following file extensions: <i>.ttf</i> or <i>.woff</i>.</p>
-</div>
+>⚠️ The font family file must be uploaded in the following file extensions: <i>.ttf</i> or <i>.woff</i>.
 
 5. Click `Save` to save your changes. 
 
diff --git a/docs/tutorials/en/data-entity.md b/docs/tutorials/en/data-entity.md
index 5ae081492..43cf82ba2 100644
--- a/docs/tutorials/en/data-entity.md
+++ b/docs/tutorials/en/data-entity.md
@@ -23,13 +23,12 @@ For example, imagine a system that controls a library. This system controls book
 
 With these concepts in mind, you can set up several data control scenarios in Master Data. By default, the following data entities are considered: customer, address, stores, etc. You can create as many data entities as you want to develop a customized environment tailored to your store's needs.
 
-<div class="alert alert-warning">
-<p>This article outlines the Master Data v1 operation. You should evaluate which Master Data version meets your needs or is in use in your operation. Learn more:</p>
-	<ul>
-    	<li><a href="https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#available-versions">Master Data version features</a></li>
-    	<li><a href="https://developers.vtex.com/docs/guides/master-data-v2-basics">Master Data v2</a></li>
-	</ul>
-</div>
+>⚠️ This article outlines the Master Data v1 operation. You should evaluate which Master Data version meets your needs or is in use in your operation. Learn more:
+>
+> * [Master Data version features](https://help.vtex.com/en/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#available-versions)
+>
+> * [Master Data v2](https://developers.vtex.com/docs/guides/master-data-v2-basics)
+> 	
 
 ## Data types
 
@@ -104,6 +103,4 @@ Follow the steps below to configure a new data entity.
 19. In the row of the newly created entity, click the <i class="fas fa-save"></i> diskette button to publish the created data entity.
 20. Click `OK`.
 
-<div class="alert alert-info">
-	<p>After creating the data entity, <a href="https://help.vtex.com/en/tutorial/creating-form-in-master-data--tutorials_1047">create the form for adding, changing, and displaying data in Master Data</a>.</p>
-</div>
+>ℹ️ After creating the data entity, [create the form for adding, changing, and displaying data in Master Data](https://help.vtex.com/en/tutorial/creating-form-in-master-data--tutorials_1047).
diff --git a/docs/tutorials/en/data-subject-rights.md b/docs/tutorials/en/data-subject-rights.md
index 8f2cdf9b7..00fb2b712 100644
--- a/docs/tutorials/en/data-subject-rights.md
+++ b/docs/tutorials/en/data-subject-rights.md
@@ -25,9 +25,7 @@ This article explains how to comply with the following data subject rights:
 - [Consent](#consent)
 - [Erasure](#erasure)
 
-<div class="alert alert-danger">
-VTEX is not responsible for personal data stored by systems integrated with your store, such as ERPs, third-party marketplaces, third-party sellers, third-party applications available in the <a href="https://help.vtex.com/en/tutorial/visao-geral-apps--4xfsHXyAQTjbZNuiKl6Y0e">VTEX App Store</a> or customizations implemented by your development team. You must map this data and ensure the enforceability of the rights of personal data subjects in these instances, in addition to the processes described below.
-</div>
+>❗ VTEX is not responsible for personal data stored by systems integrated with your store, such as ERPs, third-party marketplaces, third-party sellers, third-party applications available in the [VTEX App Store](https://help.vtex.com/en/tutorial/visao-geral-apps--4xfsHXyAQTjbZNuiKl6Y0e) or customizations implemented by your development team. You must map this data and ensure the enforceability of the rights of personal data subjects in these instances, in addition to the processes described below.
 
 ## Access and portability
 
diff --git a/docs/tutorials/en/database-maintenance-full-cleanup.md b/docs/tutorials/en/database-maintenance-full-cleanup.md
index 123ebc1d9..b166a878c 100644
--- a/docs/tutorials/en/database-maintenance-full-cleanup.md
+++ b/docs/tutorials/en/database-maintenance-full-cleanup.md
@@ -29,14 +29,11 @@ These are the operations available:
 
 - __Delete indexer products__: If you delete products from the indexer, your store will no longer have any products to be displayed.
 
-<div class="alert alert-warning">
-  <p>The following rules apply to the <b>Delete Indexer Products</b> button:
-<UL> <LI>You can perform this action only for stores with less than 10,000 products. For stores with a more extensive catalog, you must <a href="https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">create a ticket for the VTEX support</a> requesting an indexer cleanup and a database reindexing.</LI>
-<LI>When a user deletes products from the indexer, the account is blocked from performing this action for 24 hours.</LI>
-<LI>There is a queue to process the requests generated by the <i>Delete Indexer Products</i> button. You can view the estimated waiting time in the page interface. The queue is global and applies to all users to ensure the security of the VTEX platform.
-</LI></UL>
-  </p>
-</div>
+>⚠️ The following rules apply to the **Delete Indexer Products** button:
+> <UL> <LI>You can perform this action only for stores with less than 10,000 products. For stores with a more extensive catalog, you must [create a ticket for the VTEX support](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) requesting an indexer cleanup and a database reindexing.</LI>
+> <LI>When a user deletes products from the indexer, the account is blocked from performing this action for 24 hours.</LI>
+> <LI>There is a queue to process the requests generated by the <i>Delete Indexer Products</i> button. You can view the estimated waiting time in the page interface. The queue is global and applies to all users to ensure the security of the VTEX platform.
+> </LI></UL>
 
 - __Delete products/SKUs and related items__: With this operation, your products, SKUs, and related items will be permanently removed from your store.
 
@@ -46,6 +43,4 @@ These are the operations available:
 
 - __Schedule full reindexing__: When you reindex the database, your products enter an indexing queue. __The store’s products remain available for sale during the indexing process__. They enter a queue for data updates and remain available for purchase on the website. Warning: After clicking on __Reindex Database__, the process starts automatically.
 
-<div class="alert alert-warning">
-  <p>Please remember that you must <b>Delete Indexer Products</b> after performing any other operations on this page. Otherwise, users may experience errors when accessing product, category, or search results pages. It is not necessary to <b>Delete indexer products</b> after you <b>Schedule full reindexing</b>.</p>
-</div>
+>⚠️ Please remember that you must **Delete Indexer Products** after performing any other operations on this page. Otherwise, users may experience errors when accessing product, category, or search results pages. It is not necessary to **Delete indexer products** after you **Schedule full reindexing**.
diff --git a/docs/tutorials/en/deactivating-and-reorganizing-categories.md b/docs/tutorials/en/deactivating-and-reorganizing-categories.md
index c955a1591..d298bffd5 100644
--- a/docs/tutorials/en/deactivating-and-reorganizing-categories.md
+++ b/docs/tutorials/en/deactivating-and-reorganizing-categories.md
@@ -45,9 +45,7 @@ If a category has subcategories, they appear below the parent category in the ca
 
 ## Changing the category tree
 
-<div class="alert alert-warning">
-  <p>Moving categories directly through the category tree can generate unexpected errors in your catalog. Therefore, we recommend following the instructions below to change category levels. Read the<a href="https://help.vtex.com/en/known-issues/mover-categorias-gera-comportamentos-inesperados-na-arvore-de-categorias--6JSa9nnYoAAUQO1zPtzfZD"> known issue</a> related to this for more information.</p>
-</div>
+>⚠️ Moving categories directly through the category tree can generate unexpected errors in your catalog. Therefore, we recommend following the instructions below to change category levels. Read the[ known issue](https://help.vtex.com/en/known-issues/mover-categorias-gera-comportamentos-inesperados-na-arvore-de-categorias--6JSa9nnYoAAUQO1zPtzfZD) related to this for more information.
 
 There are cases where you need to change the hierarchy level of a category. For example, imagine a store has a parent category called **Accessories** and a child category (subcategory) called **Shoes**, and they want to make **Shoes** a separate parent category.
 
diff --git a/docs/tutorials/en/declining-order-cancelation.md b/docs/tutorials/en/declining-order-cancelation.md
index 6486ccbbf..120bc54e3 100644
--- a/docs/tutorials/en/declining-order-cancelation.md
+++ b/docs/tutorials/en/declining-order-cancelation.md
@@ -44,13 +44,12 @@ The description of each step is the following:
 3. If the order is within the cancellation window, the order is automatically canceled, which is the platform’s default behavior. The next steps apply after the cancellation window is over.
 4. The seller receives the cancel order request and decides whether to accept it. The next steps apply when the seller decides not to cancel the order.
 
-  <div class="alert alert-danger">
-To decline an order cancellation request, the order status in the marketplace and seller must be the following:
-<ul>
-<li><b>Marketplace status:</b> waiting for seller decision.</li>
-<li><b>Seller status:</b> cancellation requested.</li>
-</ul>
-</div>
+  >❗ To decline an order cancellation request, the order status in the marketplace and seller must be the following:
+>
+> ***Marketplace status:** waiting for seller decision.
+>
+> ***Seller status:** cancellation requested.
+> 
 
 5. The seller declines the order cancellation and notifies the marketplace.
 6. After the marketplace receives the declined request, the order moves on in the order workflow.
@@ -61,9 +60,7 @@ The request to cancel an order can be made by the marketplace, or by the custome
 
 After that, the order will remain in the [order status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) `cancellation requested` for the marketplace and `waiting for seller decision` for the seller until the seller takes action, and accepts or declines the request.
 
-<div class="alert alert-warning">
-If within 30 days the seller takes no action regarding a cancellation order request, the order is automatically canceled by the VTEX platform.
-</div>
+>⚠️ If within 30 days the seller takes no action regarding a cancellation order request, the order is automatically canceled by the VTEX platform.
 
 To decline an order cancellation request via the VTEX Admin, follow the steps below:
 
@@ -77,9 +74,7 @@ To decline an order cancellation request via the VTEX Admin, follow the steps be
 
   ![deny_cancel_request_reason_EN](https://images.ctfassets.net/alneenqid6w5/5UUueX5kuj7OkBCHVhe0oL/022f068cefdd1e6588560d5bcba94ea3/deny_cancel_request_reason_EN.png)
 
-  <div class="alert alert-warning">
-Keep in mind that the message written in this field can be displayed to the customer via <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, or sent by the marketplace.
-</div>
+  >⚠️ Keep in mind that the message written in this field can be displayed to the customer via [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), or sent by the marketplace.
 
 5. Click `Decline Request`.
 
diff --git a/docs/tutorials/en/deleting-a-category.md b/docs/tutorials/en/deleting-a-category.md
index 648c7d194..e86d28b3a 100644
--- a/docs/tutorials/en/deleting-a-category.md
+++ b/docs/tutorials/en/deleting-a-category.md
@@ -37,7 +37,7 @@ Another option is to [empty the catalog](https://help.vtex.com/en/tutorial/enten
 2. Click on `Delete Products and SKUs`. Warning: your products, SKUs, and related items will be permanently removed from your store.
 3. Then click on `Delete Categories and brands`. Warning: your categories, tags, fields, and related items will be permanently removed from your store.
 
-<div class="alert alert-warning"> <p>For security reasons, only the <a href="https://help.vtex.com/en/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy">Sponsor user</a> of the account has access to the database cleaning feature. If another user tries to access this page, all buttons will be disabled.</p></div>
+>⚠️ For security reasons, only the [Sponsor user](https://help.vtex.com/en/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy) of the account has access to the database cleaning feature. If another user tries to access this page, all buttons will be disabled.
 
 ### Related articles
 - [Adding a category](/en/tutorial/registering-a-category)
diff --git a/docs/tutorials/en/deleting-customer-data.md b/docs/tutorials/en/deleting-customer-data.md
index 5453ca19a..a68bdcc87 100644
--- a/docs/tutorials/en/deleting-customer-data.md
+++ b/docs/tutorials/en/deleting-customer-data.md
@@ -33,17 +33,13 @@ If your store keeps customer information in other data entities, you need to man
 
 2. Use a [Delete Document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1) request
 
-<div class="alert alert-danger"> 
-  Do not do this for the <b>CL</b> and <b>AD</b> entities.
-</div> 
+>❗ Do not do this for the **CL** and **AD** entities. 
 
 ## Request deletion via support
 
 You must request the deletion of your customers' personal data from VTEX platform by opening a ticket with the [VTEX Support](https://help.vtex.com/en/support).
 
-<div class="alert alert-warning">
-Please request the deletion of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
-</div>
+>⚠️ Please request the deletion of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
 
 To request the deletion of customer personal data, follow the steps below.
 
diff --git a/docs/tutorials/en/detaching-skus-by-specification.md b/docs/tutorials/en/detaching-skus-by-specification.md
index 3df959678..b908fea3e 100644
--- a/docs/tutorials/en/detaching-skus-by-specification.md
+++ b/docs/tutorials/en/detaching-skus-by-specification.md
@@ -27,8 +27,7 @@ See the following example of detaching SKUs by color. In the image below, the fe
 
 ![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/234e5508195490b55170e047dd6a9377/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
-<div class="alert alert-info"><p>
-If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.</p></div>
+>ℹ️ If search results are sorted by relevance, the SKUs of a given product will be grouped together. In other words, they will be displayed side by side.
 
 ## Configuration
 To configure which attributes will be used to detach SKUs, see our [Search Settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#) article.
diff --git a/docs/tutorials/en/develop-the-front-end-for-the-list-feature-in-your-store.md b/docs/tutorials/en/develop-the-front-end-for-the-list-feature-in-your-store.md
index b7eb41309..0c0ce1eb8 100644
--- a/docs/tutorials/en/develop-the-front-end-for-the-list-feature-in-your-store.md
+++ b/docs/tutorials/en/develop-the-front-end-for-the-list-feature-in-your-store.md
@@ -117,15 +117,11 @@ This code renders a list with __three links__:
 2. __Create new List__: This link takes the client to the `/giftlist/create` route, where the client creates their lists. In the next steps, we'll explain how list creation is done.
 3. __Manage my Lists__: This link takes the client to the `/giftlist/manage` route, where the client can manage their lists. In the next steps, we'll explain how list management is done.
 
-<div class="alert alert-danger">
-Do not uncheck the <strong>Authentication Required</strong> flag already selected by default in the folders below. Identification is required for lists to be displayed for each specific user.
-</div>
+>❗ Do not uncheck the **Authentication Required** flag already selected by default in the folders below. Identification is required for lists to be displayed for each specific user.
 
 ## Editing the list creation template
 
-<div class="alert alert-info">
-Before editing this template, you must <a href="http://help.vtex.com/en/tutorial/creating-a-type-of-list">create the List Type</a> that will be offered in your store. <!--Reescrever o artigo de tipo de lista -->
-</div>
+>ℹ️ Before editing this template, you must [create the List Type](http://help.vtex.com/en/tutorial/creating-a-type-of-list) that will be offered in your store. <!--Reescrever o artigo de tipo de lista -->
 
 The template for creating lists is located in the `giftlist/create` route. The default template for this route is `new-GiftList-Create`, located in the `HTML Templates` section of your CMS.
 
diff --git a/docs/tutorials/en/direct-migration-magazine-luiza.md b/docs/tutorials/en/direct-migration-magazine-luiza.md
index d565b3d5b..674dbbde4 100644
--- a/docs/tutorials/en/direct-migration-magazine-luiza.md
+++ b/docs/tutorials/en/direct-migration-magazine-luiza.md
@@ -15,6 +15,4 @@ legacySlug: direct-migration-magazine-luiza
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning">
-This content is exclusively regional; therefore, it does not apply to Spanish-speaking countries.
-  </div>
+>⚠️ This content is exclusively regional; therefore, it does not apply to Spanish-speaking countries.
diff --git a/docs/tutorials/en/disable-cloudflare-proxy.md b/docs/tutorials/en/disable-cloudflare-proxy.md
index 2211ede9b..8a880a6f7 100644
--- a/docs/tutorials/en/disable-cloudflare-proxy.md
+++ b/docs/tutorials/en/disable-cloudflare-proxy.md
@@ -27,6 +27,4 @@ If the proxy is enabled, the icon will be orange with the text **Proxied**. If i
 
 Please note that it may take a while to see the result of disabling the CloudFlare proxy, as it requires the cache to be refreshed.
 
-<div class="alert alert-info">
-If you want to use Cloudflare's CDN and WAF, you can insert a reverse proxy in front of VTEX services. Note that you don't need to use this configuration, as VTEX already offers CDN and WAF services in its edge service. External CDNs failures do not imply failures of VTEX's systems. We are not responsible for third-party CDNs.
-</div>
+>ℹ️ If you want to use Cloudflare's CDN and WAF, you can insert a reverse proxy in front of VTEX services. Note that you don't need to use this configuration, as VTEX already offers CDN and WAF services in its edge service. External CDNs failures do not imply failures of VTEX's systems. We are not responsible for third-party CDNs.
diff --git a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
index 04319be01..fb24676b4 100644
--- a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -23,9 +23,7 @@ With [VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-
 
 To become a part of the VTEX Ad Network and start displaying ads in your store, install the VTEX Ad Network for stores app.
 
-<div class="alert alert-warning">
-Currently, VTEX stores can only offer ad space on stores using <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
-</div>
+>⚠️ Currently, VTEX stores can only offer ad space on stores using [Store Framework](https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework).
 
 ## Monitoring results
 
diff --git a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
index 633e2a838..5d57a96e1 100644
--- a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
@@ -15,10 +15,9 @@ legacySlug: dynamic-relevance-in-intelligent-search-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>.</p>
-  <p>For selected customers, the functionality is available for free use in the VTEX Admin during its Beta period, or until decided by VTEX. Extra fees may apply in the future.</p>
-</div>
+>ℹ️ This feature is in closed beta, which means that only specific customers can access it now. If you want to implement it in the future, please contact [our support](https://support.vtex.com/hc/pt-br/requests).
+>
+> For selected customers, the functionality is available for free use in the VTEX Admin during its Beta period, or until decided by VTEX. Extra fees may apply in the future.
 
 Relevance is the feature that defines the ranking of products in search results. This configuration allows you to set weights and prioritize certain criteria, such as popularity, release date, and participation in promotions. Intelligent Search determines the relevance of each product by combining weights and priorities defined by each merchant.
 
diff --git a/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md b/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md
index a6ea37e99..fd3e7cb62 100644
--- a/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md
+++ b/docs/tutorials/en/edit-a-required-field-on-profile-system-of-master-data.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Master Data is a module of the VTEX platform used to store and organize documents. Find out how to make a form field mandatory in Master Data in the instructions below.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 The following steps will allow you to select a field and make it mandatory:
 
diff --git a/docs/tutorials/en/editing-my-data-suiteshare.md b/docs/tutorials/en/editing-my-data-suiteshare.md
index 6750fcde6..d10fca6ef 100644
--- a/docs/tutorials/en/editing-my-data-suiteshare.md
+++ b/docs/tutorials/en/editing-my-data-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: editing-my-data-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/enable-https-throughout-the-site.md b/docs/tutorials/en/enable-https-throughout-the-site.md
index 2e4fef3cd..a374af153 100644
--- a/docs/tutorials/en/enable-https-throughout-the-site.md
+++ b/docs/tutorials/en/enable-https-throughout-the-site.md
@@ -58,10 +58,11 @@ All pages on the site must be changed individually according to the article [How
 
 You can change the protocol in all folders at once by using our API, documented [in this Postman collection](https://developers.vtex.com/reference/change-uri-schema). 
 
-<div class="alert alert-warning">
-<p><strong>Warning:</strong> avoid having HTTPS enabled on only a few pages. When you access an HTTPS page, then go to an HTTP page from the same store, the browser will try to read your resources forcibly over HTTPS, and this can cause problems.</p>
-<p>It is appropriate to enable HTTPS throughout the site at one time.</p>
-<p>The same goes for desktop and mobile websites (child website), where it is necessary to treat the HTTPS of both at the same time.</p></div>
+>⚠️ **Warning:** avoid having HTTPS enabled on only a few pages. When you access an HTTPS page, then go to an HTTP page from the same store, the browser will try to read your resources forcibly over HTTPS, and this can cause problems.
+>
+> It is appropriate to enable HTTPS throughout the site at one time.
+>
+> The same goes for desktop and mobile websites (child website), where it is necessary to treat the HTTPS of both at the same time.
 
 ## Limitations
 
diff --git a/docs/tutorials/en/enabling-2-factor-authentication-login.md b/docs/tutorials/en/enabling-2-factor-authentication-login.md
index 8c7395f56..76d6254ef 100644
--- a/docs/tutorials/en/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/en/enabling-2-factor-authentication-login.md
@@ -21,9 +21,11 @@ During the login process, in addition to email and password, the system asks for
 
 Since this key is generated at login and quickly expires, it becomes almost impossible for someone to access your store using your credentials without authorization. Without 2FA, someone would only need your email and password to have full access to your store's account.
 
-<div class="alert alert-danger">
-From <strong>November 16, 2017</strong>, 2-Factor Authentication (2FA) becomes <strong>mandatory for all emails</strong> that can access VTEX Admin.<br><br>Without 2FA, you <b>won't be able to log in</b> using just your email and password. This requirement only applies to email and password logins, not to other login methods (Google, Facebook and token).
-</div>
+>❗ From **November 16, 2017**, 2-Factor Authentication (2FA) becomes **mandatory for all emails** that can access VTEX Admin.
+>
+> 
+>
+> Without 2FA, you **won't be able to log in** using just your email and password. This requirement only applies to email and password logins, not to other login methods (Google, Facebook and token).
 
 ## How to enable 2FA
 
@@ -36,13 +38,9 @@ There are two authentication options:
 
 ![2FA - Select - EN](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/c95adad1f804b36a31e7388198a4740e/2FA_-_Select_-_EN.png)
 
-<div class="alert alert-danger">
-We strongly recommend that you <strong>choose the app authentication option</strong>, since, with SMS authentication, you will depend on your network provider. By using an app, you can generate an access key whenever you need it.
-</div>
+>❗ We strongly recommend that you **choose the app authentication option**, since, with SMS authentication, you will depend on your network provider. By using an app, you can generate an access key whenever you need it.
 
-<div class="alert alert-danger">
-If you chose 2FA through SMS, and the SMS code doesn't appear, your network operator is probably to blame. Use 2FA through the app, as explained below.
-</div>
+>❗ If you chose 2FA through SMS, and the SMS code doesn't appear, your network operator is probably to blame. Use 2FA through the app, as explained below.
 
 ### Enabling 2FA through an app
 
@@ -57,9 +55,7 @@ To use the key generated by the authentication app:
   *The app code is updated periodically. No need to memorize it; access the app whenever you need an access code.*
   ![2FA - App Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/693541b703dea58a6abf8365b766f0d8/2FA_-_App_Insert_Code_-_EN.png)
 
-<div class="alert alert-info">
-If you log in with your email and password on the same computer, the access key will be requested <strong> every three days</strong>. When this happens, check the code in the application.
-</div>
+>ℹ️ If you log in with your email and password on the same computer, the access key will be requested ** every three days**. When this happens, check the code in the application.
 
 ### Enable 2FA by SMS
 
@@ -73,9 +69,7 @@ To use a key sent by SMS:
 
    ![2FA - SMS Insert Code - EN](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/80a9fe80575ca4f4a50abb040ddaea06/2FA_-_SMS_Insert_Code_-_EN.png)
 
-<div class="alert alert-warning">
-We cannot guarantee that your network operator will be able to deliver the access key whenever necessary. If the text message does not arrive, try resending the code or <a href="#habilitate-o-2fa-per-application" >enable 2FA through the application</a>.
-</div>
+>⚠️ We cannot guarantee that your network operator will be able to deliver the access key whenever necessary. If the text message does not arrive, try resending the code or <a href="#habilitate-o-2fa-per-application" >enable 2FA through the application</a>.
 
 ### 2FA for telesales operators
 
diff --git a/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
index ab16d4fb4..78b051485 100644
--- a/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/en/enabling-3ds2-for-redsys-v2-integration.md
@@ -15,7 +15,7 @@ legacySlug: enabling-3ds2-for-redsys-v2-integration
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 The 3DS2 feature is now available for payments made with credit cards and processed by the [Redsýs](https://help.vtex.com/en/tutorial/configurar-gateway-redsys--7xRnMyzZS0kQoIG2ISagY8) payment gateway.
 
@@ -23,9 +23,7 @@ The 3DS2 feature is now available for payments made with credit cards and proces
 
 For more details, please see our article [3DS2 authentication flow: accept online payments more securely](https://help.vtex.com/en/announcements/fluxo-de-autenticacao-3ds2-aceite-pagamentos-on-line-de-forma-mais-segura--6UdTjjVU1AcEQ2aE3Ftxsl).
 
-<div class="alert alert-danger">
-Before enabling the 3DS2 feature, make sure Redsýs is already configured in your store and that the established business partnership enables 3DS2 for your account.
-  </div>
+>❗ Before enabling the 3DS2 feature, make sure Redsýs is already configured in your store and that the established business partnership enables 3DS2 for your account.
 
 In this tutorial, you will learn how to add the 3DS2 authentication to the Redsýs V2 integration via the VTEX Admin. 
 
diff --git a/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
index dbedf9b2f..444ed68ea 100644
--- a/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/en/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -25,9 +25,7 @@ Local stock sale allows the sales associate in a physical store to complete sale
 6. [Link the franchise account to the physical store](#linking-the-franchise-account-to-the-physical-store)
 7. [Integrate the point of sale](#integrating-the-point-of-sale)
 
-<div class="alert alert-info">
-<p>Local stock sale can only be set up for stores that use Sales App. Learn how to request and configure Sales App in our <a href="https://help.vtex.com/en/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc">Sales App - Getting started and setting up</a> documentation.</p>
-</div>
+>ℹ️ Local stock sale can only be set up for stores that use Sales App. Learn how to request and configure Sales App in our [Sales App - Getting started and setting up](https://help.vtex.com/en/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc) documentation.
 
 ## Creating a franchise account
 
@@ -64,9 +62,7 @@ If all your products are listed without quantity, you will need to add the quant
 
 You need to [enabling selling an out-of-stock item](#enabling-selling-an-out-of-stock-item-optional) if you want to ensure the item on hand will always be available for customers in the store.
 
-<div class="alert alert-info">
-<p>If you created two different warehouses, one for the ecommerce website and one for Sales App, it is important to manage stock quantity correctly for each.</p>
-</div>
+>ℹ️ If you created two different warehouses, one for the ecommerce website and one for Sales App, it is important to manage stock quantity correctly for each.
 
 ## Linking the franchise account to the physical store
 
@@ -79,9 +75,7 @@ You will need to select a sales associate from the store where you want to test
 
 ![instore-pdp-en](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/064cb3f0b499da4533cacdbea0fee4eb/image.png)
 
-<div class="alert alert-info">
-<p>If you enabled Infinite inventory, the item quantity will display as a number greater than one million, which can't be changed when a sale is completed.</p>
-</div>
+>ℹ️ If you enabled Infinite inventory, the item quantity will display as a number greater than one million, which can't be changed when a sale is completed.
 
 ## Enabling selling an out-of-stock item (optional)
 
diff --git a/docs/tutorials/en/enabling-payments-with-bitcoin.md b/docs/tutorials/en/enabling-payments-with-bitcoin.md
index 20f661e53..f85683758 100644
--- a/docs/tutorials/en/enabling-payments-with-bitcoin.md
+++ b/docs/tutorials/en/enabling-payments-with-bitcoin.md
@@ -19,9 +19,7 @@ The VTEX platform supports your store to receive payments in Bitcoin digital cur
 
 To use Bitcoin in your store, you must have registered a gateway affiliation capable of processing this payment method and perform the configuration described below:
 
-<div class="alert alert-warning">
-  If the connector to be chosen (in <b>Step 7.</b>) is not yet registered in your store, the message “(Configure)” will be displayed after the name of the connector. In this situation, choose another available connector or register. To learn more, access <a href="https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Registering gateway affiliations</a>.
-</div>
+>⚠️ If the connector to be chosen (in **Step 7.**) is not yet registered in your store, the message “(Configure)” will be displayed after the name of the connector. In this situation, choose another available connector or register. To learn more, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 ## Setting up bitcoin payment condition
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
diff --git a/docs/tutorials/en/enter-tracking-number-on-orders-already-invoiced.md b/docs/tutorials/en/enter-tracking-number-on-orders-already-invoiced.md
index 55d34fc22..0f2ff6609 100644
--- a/docs/tutorials/en/enter-tracking-number-on-orders-already-invoiced.md
+++ b/docs/tutorials/en/enter-tracking-number-on-orders-already-invoiced.md
@@ -24,9 +24,7 @@ You can enter the tracking number on orders already invoiced, by following the s
 5. Fill in the **Tracking number** field with the number.
 6. Click `Save`.
 
-<div class="alert alert-warning">
-VTEX Admin does not allow bulk importing of order tracking numbers through files upload. The method commonly used for this is via integration between VTEX and the ERP. If your ERP is integrated with VTEX, you can import the tracking numbers using the API.
-</div>
+>⚠️ VTEX Admin does not allow bulk importing of order tracking numbers through files upload. The method commonly used for this is via integration between VTEX and the ERP. If your ERP is integrated with VTEX, you can import the tracking numbers using the API.
 
 ### Learn more
 
diff --git a/docs/tutorials/en/entering-tax-receipts-in-the-order.md b/docs/tutorials/en/entering-tax-receipts-in-the-order.md
index a0c630e73..4d6b6c485 100644
--- a/docs/tutorials/en/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/en/entering-tax-receipts-in-the-order.md
@@ -25,9 +25,7 @@ Once the tax receipt is entered with the total amount of the order, the status c
 
 You may also enter a partial tax receipt, which happens when several tax receipts are required to arrive at the total amount of the purchase. 
 
-<div class="alert alert-info">
-<p>Only after the total amount of the order has been reached will the status be changed to <strong>Invoiced</strong>.</p>
-</div>
+>ℹ️ Only after the total amount of the order has been reached will the status be changed to **Invoiced**.
 
 The tax receipt requires attention to the following points: 
 
@@ -39,6 +37,4 @@ In other words, when the tracking URL and code are entered, every time the deliv
 
 The **Conversation Tracker** works only if information is inserted in those fields. In case you don´t have them, insert any value so to activate the notification system.
 
-<div class="alert alert-danger">
-It’s possible to add more than one invoice to the order; however, the total sum of the invoices amounts must match the total amount of the order.
-</div>
+>❗ It’s possible to add more than one invoice to the order; however, the total sum of the invoices amounts must match the total amount of the order.
diff --git a/docs/tutorials/en/erasing-customer-data.md b/docs/tutorials/en/erasing-customer-data.md
index 555c4e4a9..e9413e5c2 100644
--- a/docs/tutorials/en/erasing-customer-data.md
+++ b/docs/tutorials/en/erasing-customer-data.md
@@ -35,9 +35,7 @@ If your store keeps customer information in other data entities, you need to man
 
 2. Use a [Delete Document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1) request
 
-<div class="alert alert-danger"> 
-  Do not do this for the <b>CL</b> and <b>AD</b> entities.
-</div> 
+>❗ Do not do this for the **CL** and **AD** entities. 
 
 ## Request erasure via support
 
@@ -58,8 +56,6 @@ To request the deletion of customer personal data, follow the steps below.
 8. Fill in the **Describe what happened in detail** field with details of your request.
 9. Click `Submit`.
 
-<div class="alert alert-warning">
-Please request the erasure of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
-</div>
+>⚠️ Please request the erasure of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
 
 Your request will be sent to our support team. Upon completion of the ticket, a certificate will be issued to the email where the ticket was opened confirming the completion of the erasure of the data.
diff --git a/docs/tutorials/en/events-available-in-audit.md b/docs/tutorials/en/events-available-in-audit.md
index fec04100d..e0f62e390 100644
--- a/docs/tutorials/en/events-available-in-audit.md
+++ b/docs/tutorials/en/events-available-in-audit.md
@@ -39,9 +39,7 @@ Below, you will find a list of the potential events available in [Audit](https:/
 In case you encounter an event in Audit which has not been included in this list, please inform us through the <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">documentation feedback page</a>.
 </div>
 
-<div class="alert alert-warning">
-<p>In the Audit filter options, you can find <strong>Shipping Options</strong>, <strong>Profile System</strong>, and <strong>Billing</strong> options besides the applications listed in this guide. Since these options refer to internal resources or features in closed beta, most accounts will not have events associated with them.</p>
-</div>
+>⚠️ In the Audit filter options, you can find **Shipping Options**, **Profile System**, and **Billing** options besides the applications listed in this guide. Since these options refer to internal resources or features in closed beta, most accounts will not have events associated with them.
 
 ## OMS
 
diff --git a/docs/tutorials/en/exact-sales-suiteshare.md b/docs/tutorials/en/exact-sales-suiteshare.md
index 238ed1cc1..276520699 100644
--- a/docs/tutorials/en/exact-sales-suiteshare.md
+++ b/docs/tutorials/en/exact-sales-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: exact-sales-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
index 411c1a26e..4894319a9 100644
--- a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
@@ -49,9 +49,7 @@ In the import worksheet, the only column you have to complete is “ValorEspecif
 
 The structure of the spreadsheet presents one row for each product field or SKU, i.e., the same product or SKU will be presented several times according to the existing fields in its category.
 
-<div class="alert alert-warning">
-  <p>In the exported spreadsheet, the column for "ValorEspecificacao" is "NomeCampoValor (Not Changeable)". When filling the field, the spelling of the characteristics must be exact. Uppercase and lowercase letters make a difference in this case.</p>
-  </div>
+>⚠️ In the exported spreadsheet, the column for "ValorEspecificacao" is "NomeCampoValor (Not Changeable)". When filling the field, the spelling of the characteristics must be exact. Uppercase and lowercase letters make a difference in this case.
 
 Follow the steps below to import the spreadsheet:
 
diff --git a/docs/tutorials/en/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md b/docs/tutorials/en/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
index 610f5998e..90b8562af 100644
--- a/docs/tutorials/en/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
+++ b/docs/tutorials/en/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
@@ -15,9 +15,7 @@ legacySlug: exporting-clients-registered-in-the-availability-notification
 subcategory: 5yDQmr18K4GgQAeGwq8USa
 ---
 
-<div class="alert alert-warning">
-<p>This article applies only to the <strong>Notify me</strong> feature in stores that use <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">Legacy CMS Portal</a>. For stores using <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, it is necessary to follow the instructions on the <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify">Availability Notify</a> guide.</p>
-</div>
+>⚠️ This article applies only to the **Notify me** feature in stores that use [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). For stores using [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), it is necessary to follow the instructions on the [Availability Notify](https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify) guide.
 
 To export the data of customers who registered on the availability notification option ([Notify me](https://help.vtex.com/en/tutorial/setting-up-the-notify-me-option--2VqVifQuf6Co2KG048Yu6e)), follow the steps below:
 
diff --git a/docs/tutorials/en/exporting-data.md b/docs/tutorials/en/exporting-data.md
index b7391791d..9a69b9153 100644
--- a/docs/tutorials/en/exporting-data.md
+++ b/docs/tutorials/en/exporting-data.md
@@ -17,9 +17,7 @@ subcategory: 2AThnkEZAYbk4G4EIs53rL
 
 The mass export of data records in Master Data v1 can be made through the API or importing the worksheet. The purpose of this document is to show the steps required for exporting data by worksheet.
 
-<div class="alert alert-warning">
-Exporting data from Master Data is not an immediate operation, and its execution time depends on the amount of data in Master Data. Therefore, in stores with a very large amount of data and a high update frequency, the exported file may become outdated in relation to the new data. If this occurs, the solution may be to export the data again, preferably when there are not many updates taking place (for example, outside of business hours or on weekends).
-</div>
+>⚠️ Exporting data from Master Data is not an immediate operation, and its execution time depends on the amount of data in Master Data. Therefore, in stores with a very large amount of data and a high update frequency, the exported file may become outdated in relation to the new data. If this occurs, the solution may be to export the data again, preferably when there are not many updates taking place (for example, outside of business hours or on weekends).
 
 ## Export report with data from Master Data v1
 
diff --git a/docs/tutorials/en/exporting-orders-in-orders-module.md b/docs/tutorials/en/exporting-orders-in-orders-module.md
index 27924748a..da3784b1a 100644
--- a/docs/tutorials/en/exporting-orders-in-orders-module.md
+++ b/docs/tutorials/en/exporting-orders-in-orders-module.md
@@ -19,9 +19,7 @@ You can export orders through the **All Orders** module in VTEX Admin.
 
 In this process, the system generates a report in .csv format containing details about your store's orders. Find out what information is in the report in [our tutorial on the order spreadsheet fields](https://help.vtex.com/en/tutorial/orders-worksheet--31m1ewsmsEe0WS4So2aGMY).
 
-<div class="alert alert-info">
-<p>If the number of orders selected to be exported is very high, it might cause slow performance. Therefore, you can only select a limited number of orders. Currently, exports are limited to <b>50,000 orders at a time</b>.</p>
-</div>
+>ℹ️ If the number of orders selected to be exported is very high, it might cause slow performance. Therefore, you can only select a limited number of orders. Currently, exports are limited to **50,000 orders at a time**.
 
 Follow the instructions below to create the report:
 
diff --git a/docs/tutorials/en/facebook-liberacao-de-dominio-suiteshare.md b/docs/tutorials/en/facebook-liberacao-de-dominio-suiteshare.md
index 74e29562a..cdd10992c 100644
--- a/docs/tutorials/en/facebook-liberacao-de-dominio-suiteshare.md
+++ b/docs/tutorials/en/facebook-liberacao-de-dominio-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: facebook-liberacao-de-dominio
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/faq-security-restricted-content.md b/docs/tutorials/en/faq-security-restricted-content.md
index bccad63e3..5043184c1 100644
--- a/docs/tutorials/en/faq-security-restricted-content.md
+++ b/docs/tutorials/en/faq-security-restricted-content.md
@@ -17,9 +17,7 @@ subcategory:
 
 # FAQ - Security (restricted content)
 
-<div class="alert alert-danger">
-  <p>Please do not share the information in this FAQ with users who do not have access to the VTEX Admin.</p>
-</div>
+>❗ Please do not share the information in this FAQ with users who do not have access to the VTEX Admin.
 
 VTEX provides FAQ pages that address the main questions and answers concerning the platform's structure and security to assist in customer risk assessments. This content is restricted to users with access to the VTEX Admin. Public questions and answers are available in the Security FAQ in the VTEX Help Center.
 
diff --git a/docs/tutorials/en/fill-out-the-stock-spreadsheet.md b/docs/tutorials/en/fill-out-the-stock-spreadsheet.md
index f78643d06..250be8062 100644
--- a/docs/tutorials/en/fill-out-the-stock-spreadsheet.md
+++ b/docs/tutorials/en/fill-out-the-stock-spreadsheet.md
@@ -24,9 +24,7 @@ In addition, correctly filling out the spreadsheet depends on two rules, as foll
 - Each spreadsheet column must either contain a number or a text;
 - Updating the quantity of SKUs must be done through the __TotalQuantity__ column.
 
-<div class="alert alert-info">
-  <strong>Notice</strong>: If these rules are not followed, the system will either not accept importing the spreadsheet altogether or the item quantity available for sale may be incorrectly displayed.
-</div>
+>ℹ️ **Notice**: If these rules are not followed, the system will either not accept importing the spreadsheet altogether or the item quantity available for sale may be incorrectly displayed.
 
 Please refer to each inventory spreadsheet field's meaning below.
 
diff --git a/docs/tutorials/en/filling-in-fields-in-the-import-spreadsheet.md b/docs/tutorials/en/filling-in-fields-in-the-import-spreadsheet.md
index f10dc4758..78c10d28e 100644
--- a/docs/tutorials/en/filling-in-fields-in-the-import-spreadsheet.md
+++ b/docs/tutorials/en/filling-in-fields-in-the-import-spreadsheet.md
@@ -17,15 +17,16 @@ subcategory: 2u48reCb68K48EAcm86ccM
 
 On the VTEX platform, you can [import products and SKUs in bulk using a spreadsheet](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#planilha). To better understand the meaning of each field in the spreadsheet, see the complete description of the Product and SKU related fields in Excel.
 
-<div class="alert alert-danger">
-  <p>When filling in <b>CaptionLink</b>, <b>DepartmentName</b>, <b>CategoryName</b> and <b>Brand</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ When filling in **CaptionLink**, **DepartmentName**, **CategoryName** and **Brand**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 **SkuId:** the unique identifier number of the SKU. If this field is already filled in, you cannot change it. To add a new SKU, leave the column empty.
 
diff --git a/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 0f4ac127f..9bc498ab6 100644
--- a/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/en/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -34,4 +34,4 @@ The next spreadsheet fields are optional, being used only to make SKU identifica
 - **Ref ID (View Only):** unique reference code, usually created by a store's internal systems, that facilitates the catalog's product organization.
 - **EAN (View Only):** SKU's identification code (barcode).
 
-<div class="alert alert-warning">Imported price spreadsheets have a size limit of 1 MB. If your current spreadsheet exceeds that limit, we recommend dividing it into multiple files, <strong>making sure that prices that refer to the same SKU are kept together</strong>.</div>
+>⚠️ Imported price spreadsheets have a size limit of 1 MB. If your current spreadsheet exceeds that limit, we recommend dividing it into multiple files, **making sure that prices that refer to the same SKU are kept together**.
diff --git a/docs/tutorials/en/filtering-all-orders.md b/docs/tutorials/en/filtering-all-orders.md
index f7d06cda3..3b092ba68 100644
--- a/docs/tutorials/en/filtering-all-orders.md
+++ b/docs/tutorials/en/filtering-all-orders.md
@@ -65,9 +65,7 @@ Enter the desired term in the search bar to search on All orders. This will make
 
 ![search_bar_without_time_limit_EN](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c861b2b825068d861850bce56660aa30/search_bar_without_time_limit_EN.png)
 
-<div class="alert alert-danger">
-The search on All orders cannot be combined with other filters. So, once you remove the date limit from the search, any active filters become inactive. If the search term is removed or the <i class="fas fa-toggle-off"></i> <b>Remove date limit</b> is disabled, the previously configured filters become active again.
-</div>
+>❗ The search on All orders cannot be combined with other filters. So, once you remove the date limit from the search, any active filters become inactive. If the search term is removed or the <i class="fas fa-toggle-off"></i> **Remove date limit** is disabled, the previously configured filters become active again.
 
 ### Search by combining filters
 
diff --git a/docs/tutorials/en/filters.md b/docs/tutorials/en/filters.md
index a5bab03d0..a3bee0dfd 100644
--- a/docs/tutorials/en/filters.md
+++ b/docs/tutorials/en/filters.md
@@ -21,17 +21,13 @@ By selecting a filter (price, color, size, or brand), customers can narrow searc
 
 **VTEX Intelligent Search** uses the context of products returned in search results to know exactly which filters should be displayed to the customer, according to the Catalog configuration.
 
-<div class="alert alert-info">
-  <p>The brand, department, category, and subcategory filters are sorted by the number of products registered for each filter.</p>
-</div>
+>ℹ️ The brand, department, category, and subcategory filters are sorted by the number of products registered for each filter.
 
 For example, consider that the *Size* filter has been configured in the store's catalog, and only the *sneakers* product has the *Size* specification filled in. So when the user searches for the term *sneakers*, the *Size* filter will be available. If they search for any other term, such as *hat*, this specification won’t be displayed as a filter.
 
 The search result will not display a specification when it the only existing filter or when the customer accesses it through the store menu. For example, if a customer selects the Electrical Appliances filter directly from the menu, it will not display Departments as a side filter.
 
-<div class="alert alert-info">
-  <p>If the search results returns more than 30,000 products, some filter values will be omitted, since only the specifications of some of these products will be considered.</p>
-</div>
+>ℹ️ If the search results returns more than 30,000 products, some filter values will be omitted, since only the specifications of some of these products will be considered.
 
 The Filters feature allows you to:
 
@@ -45,6 +41,4 @@ The Filters feature allows you to:
 
 Check out the [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) guide on the Developer Portal for more technical details on using filters.
 
-<div class="alert alert-warning">
-  <p>While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.</p>
-</div>
+>⚠️ While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.
diff --git a/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
index 358166f32..c2d413a76 100644
--- a/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/en/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -38,9 +38,7 @@ To contact a member:
 4. Fill the **Send a message** field.    
 5. Click the __Send__ button.     
 
-<div class="alert alert-info">
-The potential business partner will receive an email with the information you entered. If both parties are interested, the person in charge of the seller or marketplace may contact you and negotiate a marketplace and seller agreement.
-</div>
+>ℹ️ The potential business partner will receive an email with the information you entered. If both parties are interested, the person in charge of the seller or marketplace may contact you and negotiate a marketplace and seller agreement.
 
 ## Store Profile
 ![Network profile EN](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/17a2b46b39a8fc853755fc91e974b904/Marketplace_store_profile_EN.gif)
diff --git a/docs/tutorials/en/find-sellers.md b/docs/tutorials/en/find-sellers.md
index 03c06c9bc..ffddc9144 100644
--- a/docs/tutorials/en/find-sellers.md
+++ b/docs/tutorials/en/find-sellers.md
@@ -19,10 +19,8 @@ The **Find Sellers** page enables contact with sellers operating in the VTEXecos
 
 To leverage the page,you need to create a **Store Profile**. Learn how by reading the documentation.
 
-<div class="alert alert-info">
-Note that <b>Find Sellers</b> is a tool that fosters contact between potential partners,but it is not a mandatory step to be a marketplace and seller on VTEX.
-If you want to be both,a marketplace and seller,please read the <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace">Marketplace Strategies at VTEX</a> documentation.
-</div>  
+>ℹ️ Note that **Find Sellers** is a tool that fosters contact between potential partners,but it is not a mandatory step to be a marketplace and seller on VTEX.
+> If you want to be both,a marketplace and seller,please read the [Marketplace Strategies at VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace) documentation.  
 
 To access the list of sellers, go to **Marketplace > Find Sellers** or type **Find Sellers** in the search bar.
 
@@ -52,6 +50,4 @@ To contact a member:
 1. Complete the **Contact Seller** field.
 1. Click the **Send** button.
 
-<div class="alert alert-info">
-The potential business partner will receive an email with your message. If the interest is mutual,the seller or marketplace administrator can contact you and negotiate the marketplace and seller agreement terms.
-</div>
+>ℹ️ The potential business partner will receive an email with your message. If the interest is mutual,the seller or marketplace administrator can contact you and negotiate the marketplace and seller agreement terms.
diff --git a/docs/tutorials/en/fromto-of-payment-means-on-webservice.md b/docs/tutorials/en/fromto-of-payment-means-on-webservice.md
index 9fae1f378..bd8151a51 100644
--- a/docs/tutorials/en/fromto-of-payment-means-on-webservice.md
+++ b/docs/tutorials/en/fromto-of-payment-means-on-webservice.md
@@ -15,9 +15,11 @@ legacySlug: fromto-of-payment-means-on-webservice
 subcategory: 1vwB9FtTSQmcSewQw02QoW
 ---
 
-<div class="alert alert-danger"><p>Atenção: only the SOAP methods relevent to the <strong>catalog</strong> are valid.</p>
-<p><strong>All other methods are deprecated.</strong></p>
-<p>Use the equivalent REST APIs avilable in our <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: only the SOAP methods relevent to the **catalog** are valid.
+>
+> **All other methods are deprecated.**
+>
+> Use the equivalent REST APIs avilable in our [Developer Docs](//help.vtex.com/developer-docs/).
 
 The payments Web Service uses some codes for each form of payment available in the PCI Gateway area. The code for each payment is fixed, and does not depend on the integrator.
 
diff --git a/docs/tutorials/en/geolocalizado-suiteshare.md b/docs/tutorials/en/geolocalizado-suiteshare.md
index a5b303cb8..ec25dae60 100644
--- a/docs/tutorials/en/geolocalizado-suiteshare.md
+++ b/docs/tutorials/en/geolocalizado-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: geolocalizado
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/geolocation-at-checkout.md b/docs/tutorials/en/geolocation-at-checkout.md
index d96ced230..3e9381651 100644
--- a/docs/tutorials/en/geolocation-at-checkout.md
+++ b/docs/tutorials/en/geolocation-at-checkout.md
@@ -44,9 +44,7 @@ Once you have an API Key, proceed as follows:
 
 ![Geolocalizacao 1 EN](https://images.ctfassets.net/alneenqid6w5/6pPXB9VKz6aQIA8YUWyyKk/ae4f7acd4ed20feac7edf6d27960c902/Geolocalizacao_1_EN.png)
 
-<div class="alert alert-info">
-In some countries, Google Maps does not provide high quality mapping. Therefore it is possible that some addresses will be written wrongly, or Google may indicate an incorrect address. In these cases, you must correct the address on the map itself.
-  </div>
+>ℹ️ In some countries, Google Maps does not provide high quality mapping. Therefore it is possible that some addresses will be written wrongly, or Google may indicate an incorrect address. In these cases, you must correct the address on the map itself.
 
 ### Setting up the polygon
 
diff --git a/docs/tutorials/en/gift-card.md b/docs/tutorials/en/gift-card.md
index 3ba3220ad..c12510384 100644
--- a/docs/tutorials/en/gift-card.md
+++ b/docs/tutorials/en/gift-card.md
@@ -46,13 +46,9 @@ To create a new gift card, follow the step by step:
   <li><b>Collection</b>: identifies the product collection that defines the items to which the voucher can be applied.</li>
 </ul><br>
 
-<div class="alert alert-warning">
-<strong>Warning</strong>: The “Value” and the “Expiration Date” fields are <strong>mandatory</strong>. If you do not fill them, the purchase voucher will not be saved.
-</div>
+>⚠️ **Warning**: The “Value” and the “Expiration Date” fields are **mandatory**. If you do not fill them, the purchase voucher will not be saved.
 
-<div class="alert alert-danger">
-The feature that creates gift cards limited by product collections is not working. More details about this issue are provided in the article <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
-</div>
+>❗ The feature that creates gift cards limited by product collections is not working. More details about this issue are provided in the article [Restricting the use of GiftCards to a collection of products does not work](https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank).
 
 After filling in the fields correctly, the user can select up to three configuration options:
 <ul>
@@ -63,9 +59,7 @@ After filling in the fields correctly, the user can select up to three configura
 <br>
   <li>Finally, click on the <b>Save</b> button.</li>
 <br>
-<div class="alert alert-info">
-There is no limit to the creation of gift cards, however only 8000 gift cards can be exported at a time.
-</div>
+>ℹ️ There is no limit to the creation of gift cards, however only 8000 gift cards can be exported at a time.
 
 </ol>  
 
@@ -86,12 +80,9 @@ To create more than one new voucher at the same time (a batch), follow the step
   <li><b>Expiration Date</b>: this is the effective date for using all vouchers of this batch.</li>
   <li><b>Collection</b>: identifies the product collection that defines the items to which the vouchers can be applied.</li>
 <br>
-<div class="alert alert-warning">
-<strong>Warning</strong>: The “Number of gift cards”, “Value” and the “Expiration Date” fields are <strong>mandatory</strong>. If you don’t fill them, the purchase vouchers will not be saved.</div>
+>⚠️ **Warning**: The “Number of gift cards”, “Value” and the “Expiration Date” fields are **mandatory**. If you don’t fill them, the purchase vouchers will not be saved.
 <br>
-<div class="alert alert-danger">
-The feature that creates gift cards limited by product collections is not working. More details about this issue are provided in the article <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
-</div>
+>❗ The feature that creates gift cards limited by product collections is not working. More details about this issue are provided in the article [Restricting the use of GiftCards to a collection of products does not work](https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank).
 <br>
   <li><b>Reloadable</b>: while these vouchers are available, their balances can be changed;</li>
   <li><b>Reusable</b>: it will be possible to make new purchases with these vouchers until their values are fully used.</li>
@@ -102,9 +93,7 @@ A new screen will appear confirming that the requested number of vouchers has be
 <br>
   <li>To end, click on the <b>Back</b> button.</li>
 <br>
-<div class="alert alert-info">
-There is no limit to the creation of gift cards, however only 8000 gift cards can be exported at a time.
-</div>
+>ℹ️ There is no limit to the creation of gift cards, however only 8000 gift cards can be exported at a time.
 </ol>
 
 ## How to set a Gift Card as a payment method
diff --git a/docs/tutorials/en/good-practices-for-the-golive-of-my-store.md b/docs/tutorials/en/good-practices-for-the-golive-of-my-store.md
index a01069b61..8c78988ba 100644
--- a/docs/tutorials/en/good-practices-for-the-golive-of-my-store.md
+++ b/docs/tutorials/en/good-practices-for-the-golive-of-my-store.md
@@ -18,36 +18,26 @@ subcategory: wz3FvYTctwuCwG206QUAi
 ## WarRoom pre-Go-live
 After all integration and navigation flows are established and developed, one of the most critical moments of the project are the end-to-end tests, where the user's navigation flows are validated and the billing tests are conducted. Certainly important issues to be solved will arise. 
 
-<div class="alert alert-info">
-The most important is that all decision makers are in the same desk (VTEX, Customer, Agency) to optimize the synergy and resilience of the team in case any issue or doubt arises. 
-</div>
+>ℹ️ The most important is that all decision makers are in the same desk (VTEX, Customer, Agency) to optimize the synergy and resilience of the team in case any issue or doubt arises.
 
 ## Pre-Golive validation checklist
 The following is a suggested spreadsheet including the main points of attention to validate the store, before performing Golive to the public: [Pre-Golive validation checklist](https://docs.google.com/spreadsheets/d/1demkpSZ2h7ut5TsKwiPdmK029BfaCp0wabeGADfA_W0/edit)
 
-<div class="alert alert-info">
-Recommended validation dates:
-1. One month before the Go-live (to have time to take action if a blocking issue is detected).
-2. One week before the Go-live (to have time to take action if a minor issue was forgotten or delayed).
-</div>
+>ℹ️ Recommended validation dates:
+> 1. One month before the Go-live (to have time to take action if a blocking issue is detected).
+> 2. One week before the Go-live (to have time to take action if a minor issue was forgotten or delayed).
 
 ## Security certificate and pointing VTEX domain
 
 This process is conducted at the time of the GoLive of the store. It enables the current party responsible for the domain to point to VTEX. After this action, when accessing www.mystore.com, your new store will be pointed to VTEX.
 
-<div class="alert alert-warning">
-If you use Cloudflare as a DNS zone, it may be necessary to disable the DNS proxy (and consequently disable CloudFlare's CDN and WAF services). You can find more information in the article <a href="https://help.vtex.com/en/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">How to disable Cloudflare proxy</a>.  
-</div>
+>⚠️ If you use Cloudflare as a DNS zone, it may be necessary to disable the DNS proxy (and consequently disable CloudFlare's CDN and WAF services). You can find more information in the article [How to disable Cloudflare proxy](https://help.vtex.com/en/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 The details of this process are presented here: [Setting up the pointing of DNS to VTEX](/en/tutorial/configuring-dns-pointing-to-vtex/).
 
-<div class="alert alert-info">
-The main recommendation is that a customer's employee with knowledge and experience in DNS performs this set up. If this set up is not correct, your store may be unavailable due to a human error. In case there is a problem, it is necessary to take action immediately to correct it and regain the stability of operations.
-</div>
+>ℹ️ The main recommendation is that a customer's employee with knowledge and experience in DNS performs this set up. If this set up is not correct, your store may be unavailable due to a human error. In case there is a problem, it is necessary to take action immediately to correct it and regain the stability of operations.
 
 ## Communication channel during Go-live
 While the Go-live process is ongoing, in addition to the WarRoom, it is convenient to keep an active communication channel to share critical issues or urgent needs. Everyone should be aligned regarding the path to follow. 
 
-<div class="alert alert-info">
-To do so, it is usually convenient to open a Slack, Whatsapp or Skype channel during the week prior or subsequent to the Go-live, including all those involved in the project. 
-</div>
+>ℹ️ To do so, it is usually convenient to open a Slack, Whatsapp or Skype channel during the week prior or subsequent to the Go-live, including all those involved in the project.
diff --git a/docs/tutorials/en/google-integration-warnings.md b/docs/tutorials/en/google-integration-warnings.md
index 05d3d3d59..795a39c0e 100644
--- a/docs/tutorials/en/google-integration-warnings.md
+++ b/docs/tutorials/en/google-integration-warnings.md
@@ -15,6 +15,4 @@ legacySlug: google-integration-warnings
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning">
-Content in translation.
-</div>
+>⚠️ Content in translation.
diff --git a/docs/tutorials/en/google-pay-beta.md b/docs/tutorials/en/google-pay-beta.md
index d6a2d738f..e5b229f79 100644
--- a/docs/tutorials/en/google-pay-beta.md
+++ b/docs/tutorials/en/google-pay-beta.md
@@ -23,9 +23,7 @@ Google Pay™ is a digital payments service that allows users not to share their
 
 The Google Pay API Terms of Service apply whenever the Google Pay service is offered by a merchant. To read the terms, please see [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
 
-<div class="alert alert-warning">
-<p>Google Pay is not available for Checkout V5 or earlier versions of Checkout.</p>
-</div>
+>⚠️ Google Pay is not available for Checkout V5 or earlier versions of Checkout.
 
 ## Enabling Google Pay
 
diff --git a/docs/tutorials/en/hiring-the-security-certificate-sll.md b/docs/tutorials/en/hiring-the-security-certificate-sll.md
index c07792f1f..3b0e5ad42 100644
--- a/docs/tutorials/en/hiring-the-security-certificate-sll.md
+++ b/docs/tutorials/en/hiring-the-security-certificate-sll.md
@@ -24,7 +24,5 @@ Whenever you access a safe webpage, that is, an Internet page that is protected
 
 Purchasing an SSL certificate (which used to be supplied by Digicert) is no longer required. Certificates are now issued through Let’s Encrypt, and their development is now under VTEX's responsibility, [at the moment of the store’s GoLive](https://help.vtex.com/en/tutorial/configuring-dns-pointing-to-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-Please note that VTEX generates an SSL certificate for your store and ensures its automatic renewal. Therefore, we do not recommend installing any other certificates. However, if you need to install another certificate, please make the request with our [support](https://help.vtex.com/en/support).
-</div>
+>⚠️ Please note that VTEX generates an SSL certificate for your store and ensures its automatic renewal. Therefore, we do not recommend installing any other certificates. However, if you need to install another certificate, please make the request with our [support](https://help.vtex.com/en/support).
 
diff --git a/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
index 734a76e40..10c7169b9 100644
--- a/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/en/how-can-i-change-the-domain-of-my-store.md
@@ -17,9 +17,7 @@ subcategory: yMp6sKDiJEi66CGAIQ4ma
 
 Changing the domain corresponds to changing the name of the site. In other words, if a VTEX store, for example, owns the domain **_mystore.com_** and it intends to change it to **_newdomain.com_**, the store must follow this tutorial.
 
-<div class="alert alert-warning">
-You should NOT delete the previously set up HOST, while the new setting is not propagated (Average propagation time: 15 minutes).
-</div>
+>⚠️ You should NOT delete the previously set up HOST, while the new setting is not propagated (Average propagation time: 15 minutes).
 
 The VTEX platform is prepared to support domain changes without adverse impacts. To do so, just follow the steps below:
 
diff --git a/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
index 861716ecc..c30449553 100644
--- a/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/en/how-can-i-create-a-field-in-master-data.md
@@ -42,7 +42,7 @@ Follow the step-by-step below:
 11. If required, fill out the __Description__ field.
 12. Click on __Save.__
 
-<div class="alert alert-info">More information about <strong>General Settings</strong> and <strong>Search and Filter Configurations</strong> can be found in our article on <a href="https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Creating a data entity</a>, subsection <strong>How to set up</strong>.</div>
+>ℹ️ More information about **General Settings** and **Search and Filter Configurations** can be found in our article on [Creating a data entity](https://help.vtex.com/en/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar), subsection **How to set up**.
 
 ![criar campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
diff --git a/docs/tutorials/en/how-can-i-create-callcenter-user.md b/docs/tutorials/en/how-can-i-create-callcenter-user.md
index 2e31c31a1..d4a66e50d 100644
--- a/docs/tutorials/en/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/en/how-can-i-create-callcenter-user.md
@@ -43,7 +43,5 @@ To create a user with the telesales role, follow the steps below.
 
 ![Animated GIF showing how to create call center operator ](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/c41d49badebeb869d2e9d4cef73c74b0/Adicionar_perfil_EN.gif)
 
-<div class="alert alert-warning">
-When creating a  <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">role</a>, avoid including call center <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">resources</a> with other resources. Otherwise, the role might not work as expected.
-</div>
+>⚠️ When creating a  [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#), avoid including call center [resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) with other resources. Otherwise, the role might not work as expected.
 
diff --git a/docs/tutorials/en/how-can-i-create-cluster-of-customers.md b/docs/tutorials/en/how-can-i-create-cluster-of-customers.md
index 4dcf3b440..e962a3044 100644
--- a/docs/tutorials/en/how-can-i-create-cluster-of-customers.md
+++ b/docs/tutorials/en/how-can-i-create-cluster-of-customers.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Creating a cluster of customers is the same as segmenting them. These two approaches give the storeowner a better idea of the customer’s profile, and enable you to be more proactive in dealing with this user.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 These details, once obtained, are very useful for the company’s marketing and advertising. Each store can define its own clusters and the rules for a customer to be included in each of them.
 
diff --git a/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md b/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md
index 663f9ed62..5638989c4 100644
--- a/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md
+++ b/docs/tutorials/en/how-can-i-export-from-the-newsletter-database-using-master-data.md
@@ -26,6 +26,4 @@ To export your customer base that have chosen to receive newsletter, follow the
 
   In the spreadsheet that has been sent to your email there will be a column titled `isNewsletterOptIn`, which assigns the value **true** to customers who receive newsletter and **false** to those who do not.
 
-<div class="alert alert-warning">
-  <p>This option is only valid for stores with their Newsletter registered in the CRM. If your store is not yet configured in this way, and still uses the page control, read the article <a href="https://help.vtex.com/en/tutorial/how-do-i-configure-the-inclusion-of-newsletter-in-master-data--frequentlyAskedQuestions_1816">Configuring the inclusion of a newsletter in Master Data</a> to find out how to do it.</p>
-</div>
+>⚠️ This option is only valid for stores with their Newsletter registered in the CRM. If your store is not yet configured in this way, and still uses the page control, read the article [Configuring the inclusion of a newsletter in Master Data](https://help.vtex.com/en/tutorial/how-do-i-configure-the-inclusion-of-newsletter-in-master-data--frequentlyAskedQuestions_1816) to find out how to do it.
diff --git a/docs/tutorials/en/how-change-order-works-beta.md b/docs/tutorials/en/how-change-order-works-beta.md
index a0748b4da..31980dd76 100644
--- a/docs/tutorials/en/how-change-order-works-beta.md
+++ b/docs/tutorials/en/how-change-order-works-beta.md
@@ -15,9 +15,7 @@ legacySlug: how-change-order-works-beta
 subcategory: 3LQ1Tl0u4frEOd45BkjFAm
 ---
 
-<div class="alert alert-info">
-This feature is in beta, which means that we are working to improve it. If you wish to use <b>Change order (Beta)</b>, please contact <a href="https://help.vtex.com/en/support">our Support</a> and provide the <a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> in which to activate it.
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you wish to use **Change order (Beta)**, please contact [our Support](https://help.vtex.com/en/support) and provide the [account name(s)](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) in which to activate it.
 
 The **Change order (beta)** feature allows you to edit an order in different ways, either due to customer requests, product unavailability, or other reasons. These are the main order changes that can be made:
 
diff --git a/docs/tutorials/en/how-cnova-via-varejo-integration-works.md b/docs/tutorials/en/how-cnova-via-varejo-integration-works.md
index 2fddb21be..9dc5eac60 100644
--- a/docs/tutorials/en/how-cnova-via-varejo-integration-works.md
+++ b/docs/tutorials/en/how-cnova-via-varejo-integration-works.md
@@ -79,12 +79,11 @@ The integration sends the catalogue prices/net prices along with the final price
 
 e.g. 1: sale with a 10% discount applied to a specific category
 e.g. 2: SKU “X” has a value of 10,00 BRL in the commercial policy used in CNova/Via Varejo and has a fixed price of 15,00 BRL for this same policy. The integration will send the 15,00 BRL value.
-<div class="alert alert-warning">
-Note: since payment is handled in the marketplace, it also determines the payment rules. As a consequence, we are unable to send prices that are differentiated according to the payment method. 
-<br />
-<em>e.g.: if installment payment are configured with interest rates in VTEX, the sent price would continue to be whichever one the fulfillment simulation gives.</em>
-
-</div>
+>⚠️ Note: since payment is handled in the marketplace, it also determines the payment rules. As a consequence, we are unable to send prices that are differentiated according to the payment method. 
+>
+>
+> 
+> *e.g.: if installment payment are configured with interest rates in VTEX, the sent price would continue to be whichever one the fulfillment simulation gives.*
 
 
 ## 4. Benefits
@@ -109,15 +108,19 @@ When placing an order in the marketplace, several factors may influence it, such
 #### Delivery:
 
 There are two factors that would influence the delivery in this integration: Shipping Cost and Shipping Time. The sum of these two will be the Total Delivery Time. 
-<div class="alert alert-info">
-e.g.:
-<br />
-Standard Shipping = 3 days
-<br />
-Latency Time = 2 days
-<br />
-Total Delivery Time = 5 days
-</div>
+>ℹ️ e.g.:
+>
+>
+> 
+> Standard Shipping = 3 days
+>
+>
+> 
+> Latency Time = 2 days
+>
+>
+> 
+> Total Delivery Time = 5 days
 
 - __Shipping__
 
@@ -128,47 +131,79 @@ The shopkeeper also has the possibility to register a contingency table in CNova
 
 The shipment lead time is based on the sum of the ‘Latency Time’ field in Stock together with the ‘Latency Time’ from Doca, and we send the same prep time massively for all products.
 
-<div class="alert alert-info">
-e.g.:
-<br />
-<strong>Stock A</strong>
-<br />
-- Doca 1: Latency Time = 3 days
-<br />
-<strong>Stock B</strong>
-<br />
-- Doca 1: : Latency Time = 5 days
-<br />
-<br />
-<strong>Doca 1:</strong>
-<br />
-- : Latency Time = 2 days
-<br />
-<br />
-An order with a Shipping Time = 3 days, would amount to a different Total Delivery Time depending on where the product is shipped from.
-<br />
-<br />
-<strong>Forwarding from stock A:</strong>
-<br />
-- Prep Time = 3 + 2 (doca 1) = 5 days
-<br />
-- Shipping Time = 3 days
-<br />
-- Total delivery time = 8 days
-<br />
-<strong> Forwarding from stock B:</strong>
-<br />
-- Prep Time = 5 + 2 (doca 1) = 7 days
-<br />
-- Shipping Time = 3 days
-<br />
-- Total delivery time = 10 days
-</div>
-
-
-<div class="alert alert-warning">
-Note: in case of using the contingency table to calculate shipping, CNova does not consult with VTEX. This way, the only factor to be taken into consideration for <strong>Total Delivery Time</strong>, would be the <strong>Shipping</strong> provided by them, not considering the <strong>Prep Time</strong>. Caution should be exercised with this, since it can give rise to divergences in the <strong>Total Delivery Time</strong>. 
-</div>
+>ℹ️ e.g.:
+>
+>
+> 
+> **Stock A**
+>
+>
+> 
+> - Doca 1: Latency Time = 3 days
+>
+>
+> 
+> **Stock B**
+>
+>
+> 
+> - Doca 1: : Latency Time = 5 days
+>
+>
+> 
+>
+>
+> 
+> **Doca 1:**
+>
+>
+> 
+> - : Latency Time = 2 days
+>
+>
+> 
+>
+>
+> 
+> An order with a Shipping Time = 3 days, would amount to a different Total Delivery Time depending on where the product is shipped from.
+>
+>
+> 
+>
+>
+> 
+> **Forwarding from stock A:**
+>
+>
+> 
+> - Prep Time = 3 + 2 (doca 1) = 5 days
+>
+>
+> 
+> - Shipping Time = 3 days
+>
+>
+> 
+> - Total delivery time = 8 days
+>
+>
+> 
+> ** Forwarding from stock B:**
+>
+>
+> 
+> - Prep Time = 5 + 2 (doca 1) = 7 days
+>
+>
+> 
+> - Shipping Time = 3 days
+>
+>
+> 
+> - Total delivery time = 10 days
+
+
+>⚠️ Note: in case of using the contingency table to calculate shipping, CNova does not consult with VTEX. This way, the only factor to be taken into consideration for **Total Delivery Time**, would be the **Shipping** provided by them, not considering the **Prep Time**. Caution should be exercised with this, since it can give rise to divergences in the **Total Delivery Time**.
 
 #### Price and availability:
 
diff --git a/docs/tutorials/en/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md b/docs/tutorials/en/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
index 30a3aaed5..bfbd56727 100644
--- a/docs/tutorials/en/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
+++ b/docs/tutorials/en/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
@@ -19,9 +19,7 @@ Newsletter inclusion is a form that can be entered on any page of your site (exc
 
 This article will also help configure the inclusion of email addresses of customers who want to receive a newsletter, using Master Data.
 
-<div class="alert alert-warning">
-The vtex.cmc:newsletterOptIn control is discontinued and should no longer be used.
-</div>
+>⚠️ The vtex.cmc:newsletterOptIn control is discontinued and should no longer be used.
 
 This option for configuration in Master Data is convenient because details of all your customers are kept in the same place, since all the store’s registered customers are already in Master Data. In other words, it is the appropriate place for customer maintenance and action, and having all the records in one place makes life easier.
 
diff --git a/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index f358a847f..0ab83b600 100644
--- a/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/en/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -23,10 +23,11 @@ The Layout module covers home, catalog (search, categories e products), landing
 
 You can change the protocol in all folders at once by using our API, documented [in this Postman collection](https://developers.vtex.com/reference/change-uri-schema). 
 
-<div class="alert alert-warning">
-<p><strong>Warning:</strong> avoid having HTTPS enabled on only a few pages. When you access an HTTPS page, then go to an HTTP page from the same store, the browser will try to read your resources forcibly over HTTPS, and this can cause problems.</p>
-<p>It is appropriate to enable HTTPS throughout the site at one time.</p>
-<p>The same goes for desktop and mobile websites (child website), where it is necessary to treat the HTTPS of both at the same time.</p></div>
+>⚠️ **Warning:** avoid having HTTPS enabled on only a few pages. When you access an HTTPS page, then go to an HTTP page from the same store, the browser will try to read your resources forcibly over HTTPS, and this can cause problems.
+>
+> It is appropriate to enable HTTPS throughout the site at one time.
+>
+> The same goes for desktop and mobile websites (child website), where it is necessary to treat the HTTPS of both at the same time.
 
 1. In the VTEX Admin, access **Storefront > Layout** and open the folder **CMS**.
 2. Access **Sites and channels**.
diff --git a/docs/tutorials/en/how-does-reservation-work.md b/docs/tutorials/en/how-does-reservation-work.md
index 1aa9e74dd..180e504e4 100644
--- a/docs/tutorials/en/how-does-reservation-work.md
+++ b/docs/tutorials/en/how-does-reservation-work.md
@@ -31,9 +31,7 @@ After an item is sold, it goes through the following statuses in your store's in
 
 You can track the reservation status in the VTEX Admin, [as described at the end of this article](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#how-to-track-reservation-status).
 
-<div class="alert alert-warning">
-Adding products to the cart does not generate a reservation or priority. The Authorized reservation status is only displayed after the order is placed by the customer.
-</div>
+>⚠️ Adding products to the cart does not generate a reservation or priority. The Authorized reservation status is only displayed after the order is placed by the customer.
 
 ## Authorized reservation
 
@@ -49,9 +47,7 @@ _Payment expiration period + inventory reservation period_
     - **five calendar days:** when the payment is due on a Wednesday, Thursday or Friday.
     - **six calendar days:** when the payment is due on a Saturday.
 
-<div class="alert alert-danger">
-Incomplete orders have a fixed reservation period of 11 calendar days. To learn more, please refer to the article <a href="https://help.vtex.com/en/tutorial/understanding-incomplete-orders--tutorials_294">How incomplete orders work.</a>
-</div>
+>❗ Incomplete orders have a fixed reservation period of 11 calendar days. To learn more, please refer to the article [How incomplete orders work.](https://help.vtex.com/en/tutorial/understanding-incomplete-orders--tutorials_294)
 
 For an external marketplace, if the reservation period is sent by the `lockTTL` field, the reservation will not be calculated by VTEX platform but determined by the period in the field. This can be done using the [Place order](https://developers.vtex.com/docs/api-reference/checkout-api#put-/api/checkout/pub/orders) endpoint.
 
@@ -85,9 +81,7 @@ A store's inventory holds three units of an item. A customer makes a purchase, a
 
 When the retailer or the ERP updates the quantity of that item in the inventory, removing the sold quantity (updating it to two units), the platform updates the quantity of available items. Thus, this may be interpreted as a removal from inventory. Consequently, only two units of the item remain in the platform's inventory and no reserved units.
 
-<div class="alert alert-danger">
-By confirming the order handling, the seller takes responsibility for reserving the order items. From that moment on, if there are any updates in the inventory, the VTEX platform dismisses these SKUs' reservation. Therefore, we recommended updating the SKU inventory for a specific order only after the order has been invoiced. By doing so, you avoid inventory discrepancies in the <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integration with your store's backoffice</a>.
-</div>
+>❗ By confirming the order handling, the seller takes responsibility for reserving the order items. From that moment on, if there are any updates in the inventory, the VTEX platform dismisses these SKUs' reservation. Therefore, we recommended updating the SKU inventory for a specific order only after the order has been invoiced. By doing so, you avoid inventory discrepancies in the [integration with your store's backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide).
 
 ## How to track reservation status
 
diff --git a/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index 5c51a4d60..3de19bbd4 100644
--- a/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/en/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -32,6 +32,4 @@ You can find both IDs through the report generated on the integration's panel on
 ![mercalo-livre-pedido-id-en](https://images.ctfassets.net/alneenqid6w5/5CZg21BumbrNw5QjimjuGt/67fefe0993b7ca80eb365428f389fd4d/mercalo-livre-pedido-id.png)
 
 
-<div class="alert alert-warning">
-This logic of operation applies to all types of delivery, except those that include pickup points. In such, the platform continues to use the old ID.
-</div>
+>⚠️ This logic of operation applies to all types of delivery, except those that include pickup points. In such, the platform continues to use the old ID.
diff --git a/docs/tutorials/en/how-does-vtex-search-work.md b/docs/tutorials/en/how-does-vtex-search-work.md
index 986c807dd..84ed0f6c5 100644
--- a/docs/tutorials/en/how-does-vtex-search-work.md
+++ b/docs/tutorials/en/how-does-vtex-search-work.md
@@ -38,9 +38,9 @@ In accordance with the search term, the system may render the following result p
 
 If the term searched for corresponds to the name of a folder which is set up in Portal Manager (the landing page), this folder will be rendered.
 
-<div class="alert alert-warning">
-<b>Notice</b>: a folder needs to have a layout in order to be searchable.<br><b>Even if the search in done in the subfolder, the parent folder also requires layout.</b>
-</div>
+>⚠️ **Notice**: a folder needs to have a layout in order to be searchable.
+>
+> **Even if the search in done in the subfolder, the parent folder also requires layout.**
 
 ### 2. Brand
 
diff --git a/docs/tutorials/en/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md b/docs/tutorials/en/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
index 3b3ca835b..e9e447d79 100644
--- a/docs/tutorials/en/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
+++ b/docs/tutorials/en/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
@@ -25,9 +25,7 @@ When there is more than one item in the cart, the shipping cost divided by each
 
 Let's look at how the cost of shipping calculation would be calculated on a cart with 5 items, with a total shipping cost of 200 currency units:
 
-<div class="alert alert-info">
-To find out the cost of shipping a cart, please make <a href="http://help.vtex.com/en/tutorial/freight-simulation">shipping simulation</a>. To find out the weight of a SKU, access the <strong>Products and SKU</strong> page in the Catalog menu and look for <strong>Shipping Weight</strong>.
-</div>
+>ℹ️ To find out the cost of shipping a cart, please make [shipping simulation](http://help.vtex.com/en/tutorial/freight-simulation). To find out the weight of a SKU, access the **Products and SKU** page in the Catalog menu and look for **Shipping Weight**.
 
 - __Total Cost of Shipping:__ 200
 - __Product A Weight:__ 20
diff --git a/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md b/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md
index 808eb80d4..a4f249cda 100644
--- a/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md
+++ b/docs/tutorials/en/how-is-the-platforms-operation-sla-determined.md
@@ -22,9 +22,7 @@ To determine SLA violations, i.e. to account for platform downtime, we consider
 - Interruptions in the online store that significantly affect the number of orders placed, for example: store outage, slow access, checkout failure.
 - Interruptions lasting at least 10 minutes.
 
-<div class="alert alert-warning">
-  <p>We do not count scheduled maintenance as downtime.</p>
-</div>
+>⚠️ We do not count scheduled maintenance as downtime.
 
 ### Checking VTEX status
 
diff --git a/docs/tutorials/en/how-long-does-the-platform-take-to-identify-my-payment.md b/docs/tutorials/en/how-long-does-the-platform-take-to-identify-my-payment.md
index 64d9f71af..25fd4ed05 100644
--- a/docs/tutorials/en/how-long-does-the-platform-take-to-identify-my-payment.md
+++ b/docs/tutorials/en/how-long-does-the-platform-take-to-identify-my-payment.md
@@ -17,9 +17,7 @@ subcategory: 6SJnrkKDjGwSqKkMuQMOmm
 
 If you paid through bank slip, compensation should occur within 48 business hours after payment. But rest easy, usually the compensation happens before this deadline and the release of your environment is done automatically after payment confirmation.
 
-<div class="alert alert-warning">
-If the title is not updated in 48 hours, open a call, via ticket, and send the proof of payment so we can understand what happened.
-</div>
+>⚠️ If the title is not updated in 48 hours, open a call, via ticket, and send the proof of payment so we can understand what happened.
 
 ### Related articles
 
diff --git a/docs/tutorials/en/how-my-account-works.md b/docs/tutorials/en/how-my-account-works.md
index fe8f41f35..027ca5d0c 100644
--- a/docs/tutorials/en/how-my-account-works.md
+++ b/docs/tutorials/en/how-my-account-works.md
@@ -176,9 +176,7 @@ To change an existing password, follow the instructions below:
 4. Click on `SAVE PASSWORD`.
 ![My Authentication change password EN](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/4a055c06066c293502ffb9652d220c93/My_Authentication_change_password_EN.png)
 
-<div class="alert alert-info">
-If you have forgotten your password, you cannot recover it using the option for resetting passwords. To recover your password, you must log out of your current session, try to log in using your email address and password, and click on <strong>I forgot my password</strong>.
-</div>
+>ℹ️ If you have forgotten your password, you cannot recover it using the option for resetting passwords. To recover your password, you must log out of your current session, try to log in using your email address and password, and click on **I forgot my password**.
 
 ### Session management
 
diff --git a/docs/tutorials/en/how-order-authorization-workss.md b/docs/tutorials/en/how-order-authorization-workss.md
index 5bb84e9a9..49cee63cb 100644
--- a/docs/tutorials/en/how-order-authorization-workss.md
+++ b/docs/tutorials/en/how-order-authorization-workss.md
@@ -47,6 +47,4 @@ When notified, the user should:
 
 The remaining orders, classified in the variation % rates with automatic rules will be automatically processed by the system.
 
-<div class="alert alert-warning">
-It's not possible to configure order Authorization to approve orders hierarchically or by approval chain, but instead by a single user.
-</div>
+>⚠️ It's not possible to configure order Authorization to approve orders hierarchically or by approval chain, but instead by a single user.
diff --git a/docs/tutorials/en/how-product-name-control-works.md b/docs/tutorials/en/how-product-name-control-works.md
index 2a6c93f39..c3b292b0c 100644
--- a/docs/tutorials/en/how-product-name-control-works.md
+++ b/docs/tutorials/en/how-product-name-control-works.md
@@ -19,9 +19,7 @@ The `<vtex.cmc:productName/>` control renders the product name as registered in
 
 Therefore, it works only on product pages.
 
-<div class="alert alert-info">
-The name rendered by this control is that of the <b>product</b>, not the SKU.
-</div>
+>ℹ️ The name rendered by this control is that of the **product**, not the SKU.
 
 This is an example of the HTML code rendered by the Product Name control.
 
diff --git a/docs/tutorials/en/how-promotion-competition-works.md b/docs/tutorials/en/how-promotion-competition-works.md
index 07836cf2a..5d3b42d1e 100644
--- a/docs/tutorials/en/how-promotion-competition-works.md
+++ b/docs/tutorials/en/how-promotion-competition-works.md
@@ -84,8 +84,7 @@ Therefore, promotions will be applied in the following order:
 
 ![promocao3 EN](https://images.ctfassets.net/alneenqid6w5/6nz2KJuFk4aS0eU0OGg0sM/7cf285654ec80894e0a346c90918cd33/promocao3_EN.png)
 
-<div class="alert alert-warning">
-Orders originating from the <a href="https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> (provided by the store) or Fulfillment (delivered by the store) do not support cumulative promotions. This is because the use of promotions is restricted to specific types on both VTEX and external marketplaces.</div>
+>⚠️ Orders originating from the [Marketplace](https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406) (provided by the store) or Fulfillment (delivered by the store) do not support cumulative promotions. This is because the use of promotions is restricted to specific types on both VTEX and external marketplaces.
 
 ## Promotion competition strategies
 
@@ -100,8 +99,7 @@ Here are the two strategies for promotion competition:
 - [Competition by scenario](#competition-by-scenario)
 - [Competition by item](#competition-by-item)
 
-<div class="alert alert-info">
-By default, all accounts follow the competition by scenariostrategy. In case the competition by item strategy is better suited for your business needs, please <a href="https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">open a ticket</a> with our support team and request the change.</div>
+>ℹ️ By default, all accounts follow the competition by scenariostrategy. In case the competition by item strategy is better suited for your business needs, please [open a ticket](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) with our support team and request the change.
 
 ### Competition by scenario
 
diff --git a/docs/tutorials/en/how-proportional-shipping-costs-are-calculated.md b/docs/tutorials/en/how-proportional-shipping-costs-are-calculated.md
index 7133aa61c..2e5143ba2 100644
--- a/docs/tutorials/en/how-proportional-shipping-costs-are-calculated.md
+++ b/docs/tutorials/en/how-proportional-shipping-costs-are-calculated.md
@@ -29,9 +29,7 @@ For example, suppose the total shipping cost is US$ 25 for five items (product A
 
 For readability purposes, the term "weight" was sometimes used to refer to "mass" in this documentation. Even though they have different meanings, we opted to use this terminology according to everyday use.
 
-<div class="alert alert-danger">
-The weight of the product cannot be zero. This can cause problems when calculating the shipping cost in the cart.
-</div>
+>❗ The weight of the product cannot be zero. This can cause problems when calculating the shipping cost in the cart.
 
 ## Viewing proportional shipping costs
 
diff --git a/docs/tutorials/en/how-shipping-calculation-works.md b/docs/tutorials/en/how-shipping-calculation-works.md
index 9cc4ed5bf..e824664b8 100644
--- a/docs/tutorials/en/how-shipping-calculation-works.md
+++ b/docs/tutorials/en/how-shipping-calculation-works.md
@@ -46,14 +46,13 @@ The selection of logistics combinations is made according to the criteria below,
   <li><b>Inventory availability:</b> The stock is the physical location where items are stored, while <a href="https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139">inventory</a> is the list of SKUs of available stocks for sale. This criterion confirms the order items are available in a stock, and that the stock has at least one loading dock available.</li>
 </ul>
 <br>
-  <div class="alert alert-warning">
-In case of a <a href="https://help.vtex.com/en/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28">kit</a> shipment, there are two conditions:
-  <ul>
-    <li>The kit components must have the same <a href="https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">loading dock</a>.</li>
-    <li>The kit components must be available in the <a href="https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/2XyUVa0UKMyHTmwqyA5Bx6">inventory</a>.</li>
-  </ul>
-For more information, please see the article <a href="https://help.vtex.com/en/tutorial/como-e-calculado-o-frete-do-kit--frequentlyAskedQuestions_154">How to calculate the kit shipping rate</a>.
-</div>
+  >⚠️ In case of a [kit](https://help.vtex.com/en/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28) shipment, there are two conditions:
+>
+> * The kit components must have the same [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
+>
+> * The kit components must be available in the [inventory](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/2XyUVa0UKMyHTmwqyA5Bx6).
+>
+> For more information, please see the article [How to calculate the kit shipping rate](https://help.vtex.com/en/tutorial/como-e-calculado-o-frete-do-kit--frequentlyAskedQuestions_154).
 
 2. **Inventory prioritization:** The previously selected logistics routes are organized with the [inventory](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139) as a priority criterion. The lower the order of SKU quantity in stock, the higher the priority of the logistics route selection. So inventories with small item quantities are not blocked out. The logistics routes are listed in order, placing the top priority item in the first place and the lowest priority item in the last place.
 3. **Package grouping:** The VTEX platform calculates how the item orders may be split into packages to estimate the division into packages and [consignments](https://help.vtex.com/en/tutorial/como-funciona-a-remessa--tutorials_118).
diff --git a/docs/tutorials/en/how-the-carrefour-integration-works.md b/docs/tutorials/en/how-the-carrefour-integration-works.md
index 994248b86..dcb700cee 100644
--- a/docs/tutorials/en/how-the-carrefour-integration-works.md
+++ b/docs/tutorials/en/how-the-carrefour-integration-works.md
@@ -47,14 +47,12 @@ For products to be displayed in Carrefour, the integration sends the following _
 _Caption:_
 `*` Required fields.<br />
 
-<div class="alert alert-warning">Carrefour does not accept products with variations (more than one SKU).</div>
+>⚠️ Carrefour does not accept products with variations (more than one SKU).
 
 ### Product display
 Since batches of products and offers are sent successfully and validated by Carrefour, all variations/SKUs of the same product are displayed together in the same group.
 
-<div class="alert alert-info">
-Ex: Blue Shirt (product) | S, M, L (variations/SKUs)
-</div>
+>ℹ️ Ex: Blue Shirt (product) | S, M, L (variations/SKUs)
 
 ### Product status
 With all products correctly processed and cataloged by Carrefour, offers can have the following statuses:
@@ -67,9 +65,7 @@ When sent successfully for the first time, the products undergo an internal cata
 
 For example, if the product description is changed, the integration will not update it in the marketplace. To make a change, you will need to contact Carrefour directly.
 
-<div class="alert alert-warning">
-<strong>NOTE:</strong> a product can not be deleted in the Carrefour panel. If this happens, the integration will not be able to send it again.
-</div>
+>⚠️ **NOTE:** a product can not be deleted in the Carrefour panel. If this happens, the integration will not be able to send it again.
 
 ## 2. Inventory
 When a product is sent for the first time, the inventory is sent as well. However, it is discarded by Carrefour, as they only accept inventories for products already cataloged. This policy exists so that the inventory available in the marketplace is always the most up-to-date.
@@ -85,9 +81,7 @@ However, Carrefour does not notify VTEX when everything has been approved. This
 
 Once products receive the first price load, the upgrade is made SKU by SKU whenever prices undergo any changes inside VTEX. This update is sent in batches every 6 minutes, which means the integration gathers all the updates from your store during 6 minutes and then sends everything at once. If the price update is taking longer than expected, there is probably a lot of information in queue to be updated.
 
-<div class="alert alert-warning">
-Note that for prices with expiration date the system does not notify affiliates when the date expires. Thus, the base price will only be sent at the next price load.
-</div>
+>⚠️ Note that for prices with expiration date the system does not notify affiliates when the date expires. Thus, the base price will only be sent at the next price load.
 
 For each SKU, the integration sends only the final price, based on the response of the fulfillment simulation. In a standard scenario, the price sent will always be determined considering the sales policy associated with the integration. However, there are factors that can influence the final price, such as benefits and fixed prices.
 
@@ -95,11 +89,11 @@ _`Example 1`: A promotion that offers a 10% discount for a certain category._
 
 _`Example 2`: In the sales policy used in Carrefour, an SKU is priced at $ 10 with a fixed price of $ 15. The value that the integration sends to the marketplace is $ 15._
 
-<div class="alert alert-warning">
-<strong>Attention:</strong> As the payment method is given in the marketplace, payment rules are also determined by it. Because of this, the integration can not send differentiated prices according to the payment method.
-<br />
-<em>Ex: If the interest rate for installment payments is configured in VTEX, the price that is sent will still be the one that was returned by the fulfillment simulation.</em>
-</div>
+>⚠️ **Attention:** As the payment method is given in the marketplace, payment rules are also determined by it. Because of this, the integration can not send differentiated prices according to the payment method.
+>
+>
+> 
+> *Ex: If the interest rate for installment payments is configured in VTEX, the price that is sent will still be the one that was returned by the fulfillment simulation.*
 
 ## 4. Benefits
 Unlike a benefit used for your store's website, a marketplace benefit only discounts the value of the product, but without indicating that it is a benefit. That is, the price sent is already modified and there is no benefit tag.
@@ -122,9 +116,7 @@ Order details are directly influenced by factors such as delivery, price and ava
 #### Shipping
 At the time of ordering, Carrefour querries the shipping table registered in VTEX. Our platform returns to them the available shipping options, according to the mapping informed in the integration settings. It's important to keep in mind that the query is only possible if the Shipping API is registered in the Carrefour panel.
 
-<div class="alert alert-warning">
-If none of the fields in the mapping is filled correctly, it will not be possible to simulate shipping in VTEX. With this, orders placed on Carrefour will not be integrated.
-</div>
+>⚠️ If none of the fields in the mapping is filled correctly, it will not be possible to simulate shipping in VTEX. With this, orders placed on Carrefour will not be integrated.
 
 If the Shipping API is not registered, Carrefour will use a __contingency table__ to do the calculation. In this case, Carrefour sends the order information and the integration tries to make a _match_ of the shipping calculated with the carrier that best fits within VTEX (we use the __type__ of carrier as a parameter). If there is no match, there will be an error in the order integration. To solve this, you will need to do the shipping mapping first and then reprocess the order.
 
@@ -149,9 +141,7 @@ During this process, the order may not be integrated for some reason. You can ch
 
 After the integration takes place, orders continue to be treated with the same ID used in Carrefour.
 
-<div class="alert alert-warning">
-Orders with some kind of incident are not integrated. If the incident happens after the order is integrated, a warning will be displayed on the Tracking tab in VTEX Admin.
-</div>
+>⚠️ Orders with some kind of incident are not integrated. If the incident happens after the order is integrated, a warning will be displayed on the Tracking tab in VTEX Admin.
 
 ### 5.3 Order interaction
 Once the order has been successfully integrated, you can interact with it both through VTEX Admin and through the Carrefour admin panel. However, some actions may or may not be applied on both sides.
diff --git a/docs/tutorials/en/how-the-integration-with-buscape-works.md b/docs/tutorials/en/how-the-integration-with-buscape-works.md
index bac21f325..efd415745 100644
--- a/docs/tutorials/en/how-the-integration-with-buscape-works.md
+++ b/docs/tutorials/en/how-the-integration-with-buscape-works.md
@@ -60,9 +60,7 @@ If the submission is successful, the SKU will also go through a cataloging proce
 
 After correct submission and after Buscapé's cataloging process has finished, all variations/SKUs of the same product are displayed together in the same grouping (provided it is correctly registered in VTEX).
 
-<div class="alert alert-info">
-Ex: Blue Shirt (product) | S, M, L (variations/SKUs)
-</div>
+>ℹ️ Ex: Blue Shirt (product) | S, M, L (variations/SKUs)
 
 
 ### Product updates
@@ -84,9 +82,7 @@ The Buscapé statuses reflect product inventory changes in VTEX. This means that
 
 Inventories are sent for the first time along with the first products sent. From there, the ads' inventory in Buscapé is updated automatically, SKU by SKU, whenever there is any change in VTEX. The update only takes a few seconds to reflect in the marketplace, but inventory logs may take a few minutes to be displayed in VTEX Admin.
 
-<div class="alert alert-info">
-To access the logs, click on the <strong>Integrations</strong> section of the Admin side menu. A list of options will open, and then you must click the <strong>Inventory</strong> option.
-</div>
+>ℹ️ To access the logs, click on the **Integrations** section of the Admin side menu. A list of options will open, and then you must click the **Inventory** option.
 
 
 ## 3. Price
@@ -96,17 +92,17 @@ However, the system does not notify affiliates when the end date of a price with
 
 For each SKU, the integration sends the __final price__ and the __list price__ (also known as `price from`) based on the response from the checkout simulation. Usually, the price that is sent is always the one determined by the trade policy associated with the integration. However, __Benefits__ and __Fixed prices__ may influence the final price.
 
-<div class="alert alert-info">
-<strong>Example 1:</strong>
-<br />
-A benefit that offers a 10% discount for ticket payment.
-</div>
-
-<div class="alert alert-info">
-<strong>Example 2:</strong>
-<br />
-In the sales policy used in Buscapé, an SKU is priced at $ 10 and has a fixed price of $ 15. The value that the integration sends to the marketplace is $ 15.
-</div>
+>ℹ️ **Example 1:**
+>
+>
+> 
+> A benefit that offers a 10% discount for ticket payment.
+
+>ℹ️ **Example 2:**
+>
+>
+> 
+> In the sales policy used in Buscapé, an SKU is priced at $ 10 and has a fixed price of $ 15. The value that the integration sends to the marketplace is $ 15.
 
 The integration sends prices according to the payment method. This means that if there are interests set for installment payments, the price sent to Buscapé will also bear interest.
 
diff --git a/docs/tutorials/en/how-the-relationship-between-websites-and-business-policies-works.md b/docs/tutorials/en/how-the-relationship-between-websites-and-business-policies-works.md
index 41e2531c1..02910d3c4 100644
--- a/docs/tutorials/en/how-the-relationship-between-websites-and-business-policies-works.md
+++ b/docs/tutorials/en/how-the-relationship-between-websites-and-business-policies-works.md
@@ -38,9 +38,7 @@ To know the ordering of trade policies, follow the steps below:
 1. In your VTEX Admin, access **Store Settings > Channels > Trade Policies**.
 2. In the __Position__ column, you will see the ordering of your trade policies. Position 1 displays the highest priority trade policy.
 
-<div class="alert alert-danger">
-We recommend that you do not change the position of the trade policy with <strong>ID 1</strong>.
-</div>
+>❗ We recommend that you do not change the position of the trade policy with **ID 1**.
 
 ### Examples
 
diff --git a/docs/tutorials/en/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md b/docs/tutorials/en/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
index aef340a1c..3cfb0c71e 100644
--- a/docs/tutorials/en/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
+++ b/docs/tutorials/en/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
@@ -28,9 +28,7 @@ There are to ways to manipulate data from the `orderForm` to enter a second addr
 - Using the vtex.js library.
 - Through a request to VTEX’s Checkout API.
  
-<div class="alert alert-warning">
-Although it is possible to create a custom interface superimposed on that of VTEX, containing the second address field, we do not recommend it.
-</div>
+>⚠️ Although it is possible to create a custom interface superimposed on that of VTEX, containing the second address field, we do not recommend it.
 
 ## vtex.js
 
diff --git a/docs/tutorials/en/how-to-add-customized-information-to-the-order-and-manipulate-it.md b/docs/tutorials/en/how-to-add-customized-information-to-the-order-and-manipulate-it.md
index f507efcce..738219ead 100644
--- a/docs/tutorials/en/how-to-add-customized-information-to-the-order-and-manipulate-it.md
+++ b/docs/tutorials/en/how-to-add-customized-information-to-the-order-and-manipulate-it.md
@@ -32,9 +32,7 @@ To work with this field, you must use VTEX’s Checkout API. Three steps are req
 
 Before populating the `customData` field, you need to use the [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration) call to create an app. This app will contain custom fields that will be populated during checkout.
 
-<div class="alert alert-warning">
-The Update orderForm configuration defines settings that apply to all orderForms generated in your account. This means that, from the moment you add an app through it, all the store’s orders will contain the extra fields defined in that app. To create an app and its fields, this call only needs to happen once.
-</div>
+>⚠️ The Update orderForm configuration defines settings that apply to all orderForms generated in your account. This means that, from the moment you add an app through it, all the store’s orders will contain the extra fields defined in that app. To create an app and its fields, this call only needs to happen once.
 
 Here is an example of an `app` object sent in the body of the request Update orderForm configuration:
 
diff --git a/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
index 08edfdd16..590e2c93b 100644
--- a/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/en/how-to-capture-the-ip-of-an-order.md
@@ -33,14 +33,10 @@ See more details on [How to visualize the order detail](/en/tutorial/how-to-view
 
 To capture the IP by integration, it is possible to check the API Get Order with the orderID.
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/orders#getorder">See documentation of API OMS</a>
-</div>
+>ℹ️ [See documentation of API OMS](https://developers.vtex.com/reference/orders#getorder)
 
 Once the Order Json is obtained, it is possible to capture the `transactionId` and check the API **Get Transaction Details** with the transaction ID.
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/transaction-process#transactiondetails">See documentation of API Transaction</a>
-</div>
+>ℹ️ [See documentation of API Transaction](https://developers.vtex.com/reference/transaction-process#transactiondetails)
 
 Finally, from this last call it is possible to check the `ipAddress` field.
diff --git a/docs/tutorials/en/how-to-change-order-items.md b/docs/tutorials/en/how-to-change-order-items.md
index 96289e567..e6b1ec456 100644
--- a/docs/tutorials/en/how-to-change-order-items.md
+++ b/docs/tutorials/en/how-to-change-order-items.md
@@ -22,9 +22,7 @@ There are two ways to make a change to an order:
 * [Via VTEX Admin:](#how-to-change-order-items) it is only possible if the order status is `Preparing delivery`.
 * [Via order change API:](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes) in addition to changing items, you can create discounts and change the order price. You can only change it if the order status in the order API is `handling` or `waiting-for-fulfillment`.
 
-<div class="alert alert-warning">
-After it has been changed, the customer will receive an email notification if the <code>Change of information</code> template (<a href="https://help.vtex.com/en/tutorial/order-transactional-email-templates--3g2S2kqBOoSGcCaqMYK2my">transactional email template related to the order</a>) is enabled in Message Center. The customer receives the messages with the information that was filled in the item change form.
-</div>
+>⚠️ After it has been changed, the customer will receive an email notification if the `Change of information` template ([transactional email template related to the order](https://help.vtex.com/en/tutorial/order-transactional-email-templates--3g2S2kqBOoSGcCaqMYK2my)) is enabled in Message Center. The customer receives the messages with the information that was filled in the item change form.
 
 You can edit order items provided they have not been invoiced yet. To add or remove an item or change its number, please follow the step-by-step instructions below.
 
diff --git a/docs/tutorials/en/how-to-change-orders-beta.md b/docs/tutorials/en/how-to-change-orders-beta.md
index 0d13aa715..75eab35b5 100644
--- a/docs/tutorials/en/how-to-change-orders-beta.md
+++ b/docs/tutorials/en/how-to-change-orders-beta.md
@@ -15,9 +15,7 @@ legacySlug: how-to-change-orders-beta
 subcategory: 3LQ1Tl0u4frEOd45BkjFAm
 ---
 
-<div class="alert alert-info">
-This feature is in beta, which means that we are working to improve it. If you wish to use <b>Change order (Beta)</b>, please contact <a href="https://help.vtex.com/en/support">our Support</a> and provide the <a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> in which to activate it.
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you wish to use **Change order (Beta)**, please contact [our Support](https://help.vtex.com/en/support) and provide the [account name(s)](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) in which to activate it.
 
 The [Change order (beta)](https://help.vtex.com/en/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ) feature allows you to edit an order in different ways, either due to customer requests, product unavailability, or other reasons.
 
@@ -28,9 +26,7 @@ This article explains how an order can be changed and how to do so. It comprises
 - [Common aspects](#common-aspects)
 - [Processing errors](#processing-errors)
 
-<div class="alert alert-warning">
-To learn about the <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#general-characteristics">general characteristics</a> of order change scenarios, including aspects like reservation, inventory update, and franchise accounts, or to understand details related to <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#price-changes">pricing, payment, and invoicing</a>, read the <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ">How Change order works (Beta)</a> article.
-</div>
+>⚠️ To learn about the [general characteristics](https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#general-characteristics) of order change scenarios, including aspects like reservation, inventory update, and franchise accounts, or to understand details related to [pricing, payment, and invoicing](https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#price-changes), read the [How Change order works (Beta)](https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ) article.
 
 ## Conditions
 
diff --git a/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md b/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md
index 47fe89bc1..a757d6c52 100644
--- a/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md
+++ b/docs/tutorials/en/how-to-change-the-order-of-payment-methods-at-checkout.md
@@ -19,9 +19,7 @@ There are to ways to change the display order of your store’s payment methods
 - Through Admin.
 - Through JavaScript customizations.
 
-<div class="alert alert-warning">
-<strong>Note:</strong> for security and performance reasons, <strong>we do not recommend</strong> that you alter the checkout JavaScript archives. VTEX does not take responsibility for any problems caused after the alteration of this code. 
-</div>
+>⚠️ **Note:** for security and performance reasons, **we do not recommend** that you alter the checkout JavaScript archives. VTEX does not take responsibility for any problems caused after the alteration of this code.
 
 ## How Sorting Works
 
diff --git a/docs/tutorials/en/how-to-change-the-sorting-of-delivery-types-in-the-cart.md b/docs/tutorials/en/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
index 88f2a773c..7a2d1ac5b 100644
--- a/docs/tutorials/en/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
+++ b/docs/tutorials/en/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
@@ -21,6 +21,4 @@ By clicking on the delivery types menu, the customer will be able to access othe
 
 This is a standard behavior of the platform, and if the merchant wants to modify it, it is possible to customize the cart (through CSS and JavaScript), according to the store's needs.
 
-<div class="alert alert-warning">
-Note that you should be very careful about any CSS or JavaScript changes in your cart. If it's not properly done, this kind of customization can compromise the conversion rate of your store and the security of your checkout.
-</div>
+>⚠️ Note that you should be very careful about any CSS or JavaScript changes in your cart. If it's not properly done, this kind of customization can compromise the conversion rate of your store and the security of your checkout.
diff --git a/docs/tutorials/en/how-to-configure-a-custom-payment.md b/docs/tutorials/en/how-to-configure-a-custom-payment.md
index c38c4563d..0c2c997d1 100644
--- a/docs/tutorials/en/how-to-configure-a-custom-payment.md
+++ b/docs/tutorials/en/how-to-configure-a-custom-payment.md
@@ -33,6 +33,4 @@ It allows the use of a store's credit card in partnership with one of the follow
 
 After this configuration, the creation of a [Payment Condition](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions) is required.
 
-<div class="alert alert-warning">
-We recommend using the automatic approval only in cases where the payment will be made upon delivery or pickup at the store. This option releases the payment of the order, meaning that the order automatically switches to the Preparing Delivery status, without payment verification.
-  </div>
+>⚠️ We recommend using the automatic approval only in cases where the payment will be made upon delivery or pickup at the store. This option releases the payment of the order, meaning that the order automatically switches to the Preparing Delivery status, without payment verification.
diff --git a/docs/tutorials/en/how-to-configure-mercado-pago-pro-as-a-payment-method.md b/docs/tutorials/en/how-to-configure-mercado-pago-pro-as-a-payment-method.md
index 08c83eceb..aaee0c6dc 100644
--- a/docs/tutorials/en/how-to-configure-mercado-pago-pro-as-a-payment-method.md
+++ b/docs/tutorials/en/how-to-configure-mercado-pago-pro-as-a-payment-method.md
@@ -45,7 +45,5 @@ On the right side of the screen, you can configure [special payment conditions](
 
 However, this step is optional. You can click directly on the __blue button “Save”__ to finish the payment method configuration.
 
-<div class="alert alert-warning">
-Remember that new payment conditions can take up to 10 minutes to be displayed in  SmartCheckout.
-</div>
+>⚠️ Remember that new payment conditions can take up to 10 minutes to be displayed in  SmartCheckout.
 
diff --git a/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index c82847ed5..0a18b9943 100644
--- a/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/en/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -32,9 +32,7 @@ In B2B operations, there is a need to maintain relationships with buyers who req
 
 ![Minimum Order Value - EN](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/871fa991d270c1e64c12f0cdf3c5a4ab/Minimum_Order_Value_-_EN.png)
 
-<div class="alert alert-warning">
-The customer is allowed to assemble a cart with a value less than that specified in the "Minimum total amount in cart" rule. However, at the time of closing the purchase, only orders that are equal to or greater than the specified amount will be completed.
-</div>
+>⚠️ The customer is allowed to assemble a cart with a value less than that specified in the "Minimum total amount in cart" rule. However, at the time of closing the purchase, only orders that are equal to or greater than the specified amount will be completed.
 
 ## Setting a maximum number of items of the same SKU per cart
 
@@ -44,9 +42,7 @@ The customer is allowed to assemble a cart with a value less than that specified
 
 ![Max quantity of the same SKU in cart](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/0a8cf8d7955ae90cea6332cafb6990ed/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_EN.png)
 
-<div class="alert alert-warning">
-There are no limits on the maximum number of <b>same SKU</b> items per cart. The only restriction refers to the maximum number of items from <b>different SKUs</b>, which must be a maximum of 300 items per cart.
-</div>
+>⚠️ There are no limits on the maximum number of **same SKU** items per cart. The only restriction refers to the maximum number of items from **different SKUs**, which must be a maximum of 300 items per cart.
 
 If you want to use actions that prevent the user from exceeding the specified values even during the purchase flow (for example, create a cart button lock when the maximum amount of items is reached), it will be necessary to create a customization in the front-end of the store.
 
diff --git a/docs/tutorials/en/how-to-configure-payment-conditions.md b/docs/tutorials/en/how-to-configure-payment-conditions.md
index 0a871aac8..adb5a06ec 100644
--- a/docs/tutorials/en/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/en/how-to-configure-payment-conditions.md
@@ -30,9 +30,7 @@ Once you have defined your gateway affiliation, for any pf the payment condition
 
 In addition, it's possible to define whether the payment will be in full or in installments, with or without interest and special conditions.
 
-<div class="alert alert-warning">
- Any changes in payment conditions may take up to 10 minutes to appear at your store's checkout.
-</div>
+>⚠️ Any changes in payment conditions may take up to 10 minutes to appear at your store's checkout.
 
 In the steps below, we will use the credit card as an example of a payment condition.
 
@@ -48,9 +46,7 @@ In the steps below, we will use the credit card as an example of a payment condi
 8. On __In full or in installments?*__, select __In full__.
 9. Click on __Save__.
 
-<div class="alert alert-info">
-In Step 5. you can choose other payment methods such as debit cards, cobranded, private, notes payable, bank invoices, PIX, among others.
-</div>
+>ℹ️ In Step 5. you can choose other payment methods such as debit cards, cobranded, private, notes payable, bank invoices, PIX, among others.
 
 ### Installments without interest
 
@@ -91,9 +87,7 @@ In Step 5. you can choose other payment methods such as debit cards, cobranded,
 
 In some countries, interest on installment purchases is charged directly by the financial institution. For these cases, you can activate the __External interest__ button. This button fills the amount of interest on the JSON sent to the connector with `null`. This `null` value indicates that interest will be charged at a later date by the financial institution. To activate this feature, click on the button __External interests__ in the configuration of installments with interests.
 
-<div class="alert alert-info">
-  Attention: the external interest functionality is only valid for some gateway affiliations (check that this option is available when registering the desired affiliation). Orders placed by affiliations that do not support this feature will be canceled in the system.
-</div>
+>ℹ️ Attention: the external interest functionality is only valid for some gateway affiliations (check that this option is available when registering the desired affiliation). Orders placed by affiliations that do not support this feature will be canceled in the system.
 
 ## Remove payment condition
 
diff --git a/docs/tutorials/en/how-to-configure-subscriptions.md b/docs/tutorials/en/how-to-configure-subscriptions.md
index 5810b056a..5854918e8 100644
--- a/docs/tutorials/en/how-to-configure-subscriptions.md
+++ b/docs/tutorials/en/how-to-configure-subscriptions.md
@@ -34,9 +34,7 @@ To activate this feature, you will need to:
 
 ## 1. Install the Subscriptions app
 
-<div class="alert alert-warning">
-Currently, the installation of the Subscriptions module is done only by <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.
-</div>
+>⚠️ Currently, the installation of the Subscriptions module is done only by [our Support](https://support.vtex.com/hc/en-us/requests).
 
 To install the free Subscriptions app from the [VTEX App Store](https://apps.vtex.com/), follow the steps below:
 
@@ -63,9 +61,7 @@ Currently, the following payment methods are enabled for subscription orders:
 * **Boleto (popular Brazilian off-line payment method)**
 * **Credit card**
 
-<div class="alert alert-info">
-  <p>To make the <strong>Credit card</strong> payment option available, contact your store's acquirer and make sure they accept recurring purchase transactions coming from tokenized cards (no CVV). The <strong>Subscriptions</strong> system will use the same card data from the first purchase to place subsequent subscription orders, ensuring the security of the entire process.</p>
-</div>
+>ℹ️ To make the **Credit card** payment option available, contact your store's acquirer and make sure they accept recurring purchase transactions coming from tokenized cards (no CVV). The **Subscriptions** system will use the same card data from the first purchase to place subsequent subscription orders, ensuring the security of the entire process.
 
 To enable this type of transaction in the connector, the store manager must ask the acquirer for permission to process recurring payments. Check out our article [Registering gateway affiliations](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
 
@@ -79,9 +75,7 @@ There is another option to create a subscription plan, which involves manually c
 
 There are a number of subscription-related features available in the **Roles** module of your store. These features allow your VTEX Admin users to access certain features in order to operate the Subscriptions module. To learn more about roles, please read this [article](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role).
 
-<div class="alert alert-warning">
-  <p>If the user does not have the permissions required to access the data on the <strong>Subscriptions</strong> pages, the system will display a warning stating that they do not have those permissions, and the user will be unable to view the data.</p>
-</div>
+>⚠️ If the user does not have the permissions required to access the data on the **Subscriptions** pages, the system will display a warning stating that they do not have those permissions, and the user will be unable to view the data.
 
 See the table below for features related to the Subscriptions module.
 
diff --git a/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md b/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md
index bdf3f5c45..f592b0c1e 100644
--- a/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md
+++ b/docs/tutorials/en/how-to-configure-the-fingerprint-device-for-stelo.md
@@ -19,15 +19,11 @@ __Device Fingerprint__ is an identifier that acts in payment processing to impro
 
 By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
 
 This article will explain how to associate the Device Fingerprint feature with the Stelo affiliation.
 
-<div class="alert alert-info">
-The configurations documented in this article are done in an environment outside VTEX. They may therefore be out of date.
-</div>
+>ℹ️ The configurations documented in this article are done in an environment outside VTEX. They may therefore be out of date.
 
 To enter the scripts that Stelo requires for the fingerprint device, you must use Google Tag Manager. To do this, log into your account at [http://www.google.com/tagmanager](http://www.google.com/tagmanager "http://www.google.com/tagmanager"). Then proceed as follows:
 
diff --git a/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md b/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
index 56820b965..3a5c79646 100644
--- a/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
+++ b/docs/tutorials/en/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
@@ -15,7 +15,7 @@ legacySlug:
 subcategory: 
 ---
 
-<div class="alert alert-warning">Google Shopping integration through XML is an <strong>outdated method</strong> and is no longer recommended. See [here](http://help.vtex.com/en/tutorial/new-google-shopping-api-integration) how the new Google Shopping integration through API works.</div>
+>⚠️ Google Shopping integration through XML is an **outdated method** and is no longer recommended. See [here](http://help.vtex.com/en/tutorial/new-google-shopping-api-integration) how the new Google Shopping integration through API works.
 
 According to the [2015 Update of the Specification for the Google Shopping feed and the Google](https://support.google.com/merchants/answer/6231410?hl=pt-BR "2015 Update of the Specification for the Google Shopping feed and the Google")[product Taxonomy](https://support.google.com/merchants/answer/6231410?hl=pt-BR " product Taxonomy"), we have included new fields in our XML creation form: Category separator, Global Category and product specifications.
 
diff --git a/docs/tutorials/en/how-to-create-a-page-template.md b/docs/tutorials/en/how-to-create-a-page-template.md
index e24a0c678..016b84f40 100644
--- a/docs/tutorials/en/how-to-create-a-page-template.md
+++ b/docs/tutorials/en/how-to-create-a-page-template.md
@@ -36,16 +36,18 @@ Check out the walk-through:
 3. Click on __HTML Templates __.
 4. Just below, click on __New template__.
 5. Fill in the __Template Name__ field.
-<div class="alert alert-danger">
-  <p>When filling in the <b>Template Name</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-<li><code>app</code></li>
-</ul></p>
-</div>
+>❗ When filling in the **Template Name**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+>
+> *`app`
+> 
 6. Then fill in the __Template XHTML__ box with your template code. 
 ![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. Click on the __Save Template__ button.
diff --git a/docs/tutorials/en/how-to-create-a-product.md b/docs/tutorials/en/how-to-create-a-product.md
index 5b3433e62..931f16e00 100644
--- a/docs/tutorials/en/how-to-create-a-product.md
+++ b/docs/tutorials/en/how-to-create-a-product.md
@@ -32,9 +32,7 @@ The form to add a new product contains the following sections:
 *   [SEO](#seo)
 *   [Storefront](#storefront)
 
-<div class="alert alert-info">
-  <p>Before creating a product, you must create the corresponding <a href="https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206">Category</a> for the product, if it has not been previously registered in your store.</p>
-</div>
+>ℹ️ Before creating a product, you must create the corresponding [Category](https://help.vtex.com/en/tutorial/registering-a-category--tutorials_206) for the product, if it has not been previously registered in your store.
 
 ## Basic information
 
@@ -83,9 +81,7 @@ To add images to the product, follow the instructions below:
 1. Click on the `Add images` button or drop the images within the dotted line frame.
 2. Insert all product images, including their variations, such as color and size. Images must be in JPEG, PNG, or GIF format, up to 5 MB each.
 
-<div class="alert alert-warning">
-<p>We recommend using images of at least 600 x 600 pixels, to ensure that they will be displayed properly in your store.</p>
-</div>
+>⚠️ We recommend using images of at least 600 x 600 pixels, to ensure that they will be displayed properly in your store.
 
 To rearrange the images and change their display order on the product page, you can click on an image and then drag and drop it to a certain position, as shown below.
 
@@ -144,9 +140,7 @@ Each product must have at least one [SKU](https://help.vtex.com/en/tutorial/what
 
  If you want to create **more than one SKU** according to your product's variations, click on the `+ Add variations` button.
 
-<div class="alert alert-warning">
-  <p>Clicking on <code>+ Add variations</code> will delete the data you have entered in the <b>SKU information fields</b>.</p>
-</div>
+>⚠️ Clicking on `+ Add variations` will delete the data you have entered in the **SKU information fields**.
 
 What differentiates one SKU or product variation from another is the many possible combinations of specifications.  For example, you add _a pair of sneakers_ and configure its _color_ specification with the _pink_ and _blue_ options and its _size_ specification with the sizes _7_ and _8_. This product's SKUs will be the combinations of the previous options: _pink sneakers size 7_, _pink sneakers size 8, blue sneakers size 7,_ and _blue sneakers size 8_.
 
@@ -175,9 +169,7 @@ In this section, you can find the specifications you’ve created and the option
 
 You can edit the specification info by clicking on the <i class="fas fa-pencil-alt"></i> button on each row.
 
-<div class="alert alert-info">
-  <p>Once you have configured product specifications, you cannot delete a specification or add a new one. While editing, you can only add new values to the existing specification.</p>
-</div>
+>ℹ️ Once you have configured product specifications, you cannot delete a specification or add a new one. While editing, you can only add new values to the existing specification.
 
 You can also click on the `+ Add specifications` button to include more specifications.
 
@@ -203,9 +195,7 @@ By clicking on the button, you can perform the following actions:
   * **Add images:** on this page, you can also upload new images by clicking on the `Add images` button or by dropping image files into the dotted space.
 * **Deactivate:** deactivate the SKU.
 
-<div class="alert alert-warning">
-<p>If you add specifications after configuring the variations, the system will recalculate all variations and redefine their fields.</p>
-</div>
+>⚠️ If you add specifications after configuring the variations, the system will recalculate all variations and redefine their fields.
 
 ###  Advanced Editing
 
diff --git a/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
index 5462dd46d..28e1f3820 100644
--- a/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/en/how-to-create-a-promotion-with-limitation-of-use.md
@@ -17,9 +17,7 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 
 If you want regular promotion to be applied only for a limited number of times, simply uncheck the **unlimited** option in restrictions and limitations of use. After that, a field becomes available, to register the number of times the promotion can be applied to purchases in your store. So, if you register the number 10, the promotion will only be granted to the first 10 completed orders that meet the rules of the promotion in your store.
 
-<div class="alert alert-warning">
-<p>Orders with status <code>Canceling</code> or <code>Canceled</code> do not count in the defined limit.</p>
-</div>
+>⚠️ Orders with status `Canceling` or `Canceled` do not count in the defined limit.
 
 ![promotion-with-restriction-en](https://images.ctfassets.net/alneenqid6w5/5yz4Gzh3nao86gISu8OsCu/d7a18088185d781c140916bc1bf2299e/Promotion_with_restriction_-_EN.png)
 
diff --git a/docs/tutorials/en/how-to-create-a-shelf-template.md b/docs/tutorials/en/how-to-create-a-shelf-template.md
index 574d5c3b0..24cb3cd8e 100644
--- a/docs/tutorials/en/how-to-create-a-shelf-template.md
+++ b/docs/tutorials/en/how-to-create-a-shelf-template.md
@@ -22,15 +22,16 @@ To create a shelf template, follow the steps below:
 3. Click __Shelves Templates__.
 4. Click __new template__.
 5. Fill in the __Shelf Template Name__ field.
-<div class="alert alert-danger">
-  <p>When filling in the <b>Shelf Template Name</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ When filling in the **Shelf Template Name**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 6. The __CSS Class__ field creates a *class* tag for this template. This field is optional.
 7. Click the __Rounded corners__ box so that the template has rounded edges.
 8. In __Template Code__ you must fill in the code of your template. Use the standard templates as a basis for creating the new one. [See here a basic code sample](https://gist.githubusercontent.com/DeboraFerreira/a4126e2a60a6a0abb6c0/raw/8600e6e4c718c626158e472cdcee60ed03009a0f/template-prateleira).
diff --git a/docs/tutorials/en/how-to-create-a-subscription-attachment.md b/docs/tutorials/en/how-to-create-a-subscription-attachment.md
index 3377d8f8d..7f5b57592 100644
--- a/docs/tutorials/en/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/en/how-to-create-a-subscription-attachment.md
@@ -15,9 +15,7 @@ legacySlug: how-to-create-a-subscription-attachment
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
- <div class="alert alert-info">
-  <p>If you have the <strong>Subscriptions Beta</strong> module, the recommended process to create a subscription plan is directly through the <strong>Subscriptions</strong> module. Read the article <a href="https://help.vtex.com/en/tutorial/como-criar-um-plano-de-assinatura-beta--1qGRoFczm98Wgt81f9mUqC">Creating a subscription plan (Beta)</a> for more information.</p>
-</div>
+ >ℹ️ If you have the **Subscriptions Beta** module, the recommended process to create a subscription plan is directly through the **Subscriptions** module. Read the article [Creating a subscription plan (Beta)](https://help.vtex.com/en/tutorial/como-criar-um-plano-de-assinatura-beta--1qGRoFczm98Wgt81f9mUqC) for more information.
 
 The SKU Attachment is responsible for indicating that the subscription functionality is active for that SKU, and also what will the available frequency be.
 
@@ -41,9 +39,7 @@ To create a SKU attachment, follow the steps below.
     * `vtex.subscription.test`
 5. Leave the **Attachment required** box unchecked.
 
- <div class="alert alert-warning">
-  <p>Make sure the <strong>Attachment required</strong> box is unchecked. If the attachment is marked as required, the <strong>Subscription</strong> system will attempt to send a recurring order for an item that already has a required attachment, causing an error in the system. In case you misconfigure this option, uncheck the required attachment field and ask your customer to try again.</p>
-</div>
+ >⚠️ Make sure the **Attachment required** box is unchecked. If the attachment is marked as required, the **Subscription** system will attempt to send a recurring order for an item that already has a required attachment, causing an error in the system. In case you misconfigure this option, uncheck the required attachment field and ask your customer to try again.
 
 6. In the **Status** field, check the **Enable/Disable attachment** box and click on `Save`.
 
@@ -77,9 +73,7 @@ Follow the step-by-step instructions below to configure available frequencies an
 
         ![EN Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/15AueDNpKyx3yBVjP0q7tY/415def684e81619e96155a1fb390a4f4/EN_Assinatura_Exemplo_Valores_month.png)
 
-<div class="alert alert-info">
-  <p>If the <strong>Permitted Values</strong> field is left blank, the date of the subscription cycle will be the same day of the week (if the frequency is weekly) or the same day of the month (if the frequency is monthly) as the original order.</p>
-</div>
+>ℹ️ If the **Permitted Values** field is left blank, the date of the subscription cycle will be the same day of the week (if the frequency is weekly) or the same day of the month (if the frequency is monthly) as the original order.
 
 ### Associating the attachment with an SKU
 
diff --git a/docs/tutorials/en/how-to-create-conditional-prices.md b/docs/tutorials/en/how-to-create-conditional-prices.md
index 69ead8238..7cf9e2292 100644
--- a/docs/tutorials/en/how-to-create-conditional-prices.md
+++ b/docs/tutorials/en/how-to-create-conditional-prices.md
@@ -15,9 +15,8 @@ legacySlug: creating-conditional-prices
 subcategory: 
 ---
 
-<div class="alert alert-warning"><strong>Note: </strong>
-In order to use Conditional Prices you have to first install the <strong>Conditions Builder</strong> app and create a condition there. (Read the article <a href="http://help.vtex.com/en/tutorial/how-to-use-conditions-builder-app">How to use Conditions Builder App</a>)
-</div>
+>⚠️ **Note: **
+> In order to use Conditional Prices you have to first install the **Conditions Builder** app and create a condition there. (Read the article [How to use Conditions Builder App](http://help.vtex.com/en/tutorial/how-to-use-conditions-builder-app))
 
 
 Conditional prices are managed in the pricing module.
diff --git a/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
index d5cf9adb3..de049e80f 100644
--- a/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/en/how-to-define-the-url-for-a-product-page.md
@@ -25,9 +25,7 @@ Check out the [Filling rules](#filling-rules) section to understand the restrict
 
 ![textlink.en](https://images.ctfassets.net/alneenqid6w5/2FDLvlMqvZNRCAiCoFNbfB/3485de69b69d5245045063e617177c70/textlink.en.png)
 
-<div class="alert alert-info">
-  <p>You can also change a product's page URL using the <a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview">Catalog API</a>. In this case, you must change the field <code>LinkId</code>. See <a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product">Update Product</a> for more information.</p>
-</div>
+>ℹ️ You can also change a product's page URL using the [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#overview). In this case, you must change the field `LinkId`. See [Update Product](https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product) for more information.
 
 ## Filling rules
 
@@ -42,9 +40,7 @@ Follow the rules below to fill in the **textLink** field:
     * `api`
     * `admin`
 
-<div class="alert alert-danger">
-  <p>Please note that not complying with the rules listed above to complete the <strong>textLink</strong> field can affect your store's performance, lead to search issues, and interfere with the proper functioning of pages defined in the VTEX Admin.</p>
-</div>
+>❗ Please note that not complying with the rules listed above to complete the **textLink** field can affect your store's performance, lead to search issues, and interfere with the proper functioning of pages defined in the VTEX Admin.
 
 ## Learn more
 
diff --git a/docs/tutorials/en/how-to-download-the-vtex-invoices.md b/docs/tutorials/en/how-to-download-the-vtex-invoices.md
index 5590cdd81..6c234be5c 100644
--- a/docs/tutorials/en/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/en/how-to-download-the-vtex-invoices.md
@@ -64,7 +64,7 @@ To download your "boleto", follow the steps below:
 6. Click on **Pay this Invoice**.
 7. A new "boleto" will be generated; and penalties and taxes will be included automatically when required. 
 
-<div class="alert alert-info">In Brazil, a purple invoice can indicate that it is overdue but that a new "boleto" with an upcoming due date has already been issued. In such cases, the invoice will continue as overdue until it's paid. If no payment is made, the invoice color will switch to red again.</div>
+>ℹ️ In Brazil, a purple invoice can indicate that it is overdue but that a new "boleto" with an upcoming due date has already been issued. In such cases, the invoice will continue as overdue until it's paid. If no payment is made, the invoice color will switch to red again.
 
 ![baixar boletos en](https://images.ctfassets.net/alneenqid6w5/4NxkYNfPImdKOMzCkuUAmp/4e545d21ada8b602c02ea337ff209d40/baixar_boletos_en.gif)
 
diff --git a/docs/tutorials/en/how-to-export-a-product-spreadsheet.md b/docs/tutorials/en/how-to-export-a-product-spreadsheet.md
index 340ceeaa8..6e48fb012 100644
--- a/docs/tutorials/en/how-to-export-a-product-spreadsheet.md
+++ b/docs/tutorials/en/how-to-export-a-product-spreadsheet.md
@@ -28,6 +28,4 @@ Here's the step-by-step to do so:
 
 Then check the inbox for the selected email. If the operation has worked, the user will have received an email with a link to download the complete spreadsheet.
 
-<div class="alert alert-warning">
-This only works properly when you're dealing with up to 10,000 products. If the required value is greater than this limit, the system does not send the spreadsheet to the email. Use the filters to refine your search.
-</div>
+>⚠️ This only works properly when you're dealing with up to 10,000 products. If the required value is greater than this limit, the system does not send the spreadsheet to the email. Use the filters to refine your search.
diff --git a/docs/tutorials/en/how-to-find-an-sku-id.md b/docs/tutorials/en/how-to-find-an-sku-id.md
index 53cc025b8..d414a33f6 100644
--- a/docs/tutorials/en/how-to-find-an-sku-id.md
+++ b/docs/tutorials/en/how-to-find-an-sku-id.md
@@ -46,6 +46,4 @@ To find out the SKU ID through the SKU registration URL, follow the steps below:
 4. Check the URL of the loaded page. You will see a URL with the following format: `https://{accountName}.myvtex.com/admin/Site/SkuForm.aspx?IdSku={number}`
  The SKU ID will be the number displayed in the place of `{number}`.
 
-<div class="alert alert-danger">
- To ensure the items added to the inventory will be available for sale on the store, the <a href="https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW">SKU ID</a> cannot contain <b>a leading zero</b>. For instance, the system does not read IDs with a <code>01</code>, <code>02</code>, <code>021</code> format because the expected format is <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ To ensure the items added to the inventory will be available for sale on the store, the [SKU ID](https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW) cannot contain **a leading zero**. For instance, the system does not read IDs with a `01`, `02`, `021` format because the expected format is `1`, `2`, `21`.
diff --git a/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
index 01a05e5ca..43e9b2843 100644
--- a/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/en/how-to-import-pickup-points-using-spreadsheets.md
@@ -19,9 +19,7 @@ Pickup points are a very important aspect of any [omnichannel](/en/announcement/
 
 You can [setup pickup points one by one](/en/tutorial/registering-pickup-points) or in bulk, through an XLS spreadsheet [(like this example file)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). By choosing to upload an XLS file, you can register all your pickup points at once (as long as it doesn't exceed 10 MB).
 
-<div class="alert alert-info">
-A <strong>10 MB</strong> XLS file allows you to register an average <strong>50.000 pickup points</strong>. If you have more pickup points to import, you'll need to split them into different spreadsheets and upload them separately.
-</div>
+>ℹ️ A **10 MB** XLS file allows you to register an average **50.000 pickup points**. If you have more pickup points to import, you'll need to split them into different spreadsheets and upload them separately.
 
 
 
diff --git a/docs/tutorials/en/how-to-include-a-registration-on-a-master-data-form.md b/docs/tutorials/en/how-to-include-a-registration-on-a-master-data-form.md
index 76d17e5a3..00e11e3dc 100644
--- a/docs/tutorials/en/how-to-include-a-registration-on-a-master-data-form.md
+++ b/docs/tutorials/en/how-to-include-a-registration-on-a-master-data-form.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 To include a registration, just access the Master Data module and choose the application you wish to view.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href=”https://developers.vtex.com/vtex-rest-api/docs/getting-started-1”>
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href=”https://developers.vtex.com/vtex-rest-api/docs/getting-started-1”>
+> Master Data v2
+> </a>
+> 
 
 Let us say, for example, that you want to edit the information of a customer of your store.
 
diff --git a/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md b/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
index 4cad8e6d9..da3d2beb7 100644
--- a/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
+++ b/docs/tutorials/en/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
@@ -15,10 +15,9 @@ legacySlug: why-we-do-not-recommend-inserting-a-reverse-proxy-in-front-of-vtex-s
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
-<div class="alert alert-danger">
-  <p><strong>Warning:</strong> The explanations in this article aim to address cases of rare exception. We do not recommend any store to use reverse proxy. When using a reverse proxy, all VTEX managed and optimized edge services (CDN) will be set aside, so that the store service is responsible for the site's actual provisioning, which is tasked with the settings, monitoring and feature management such as header forwarding, cookies and cache management. We do not provide documentation for any of the above-mentioned.</p>
-  <p>VTEX does not take responsibility for problems related to this system, be it the CDN itself, WAF service or any other resource that is in front of our servers. We will not have overview of any failures and therefore the solution will <strong>not</strong> be included in our SLA agreements.</p>
-</div>
+>❗ **Warning:** The explanations in this article aim to address cases of rare exception. We do not recommend any store to use reverse proxy. When using a reverse proxy, all VTEX managed and optimized edge services (CDN) will be set aside, so that the store service is responsible for the site's actual provisioning, which is tasked with the settings, monitoring and feature management such as header forwarding, cookies and cache management. We do not provide documentation for any of the above-mentioned.
+>
+> VTEX does not take responsibility for problems related to this system, be it the CDN itself, WAF service or any other resource that is in front of our servers. We will not have overview of any failures and therefore the solution will **not** be included in our SLA agreements.
 
 If even after reading the warning  above you still want to forward your own CDN to the VTEX CDN, you need to insert a reverse proxy in front of VTEX services. To this end, create the TXT entries indicated below. These will serve as a confirmation input to let us know that the host actually points to VTEX. Without this, VTEX cannot provide navigation.
 
@@ -32,11 +31,10 @@ Therefore, the configuration should look as follows:
 
 In addition to this, all `/.well-known/acme-challenge/*` traffic must reach VTEX. Some reverse proxies capture this route and therefore cannot issue or renew the SSL certificate.
 
-<div class="alert alert-warning">
-  <p>VTEX only provides navigation if:
-    <ul>
-      <li>We can confirm that the host points to VTEX (as per our CNAME).</li>
-      <li>We can issue/renew SSL certificates to the host.</li>
-    </ul>
-If either condition is not met, VTEX will stop delivering the site because it is characterized as being down.</p>
-</div>
+>⚠️ VTEX only provides navigation if:
+>
+> * We can confirm that the host points to VTEX (as per our CNAME).
+>
+> * We can issue/renew SSL certificates to the host.
+>
+> If either condition is not met, VTEX will stop delivering the site because it is characterized as being down.
diff --git a/docs/tutorials/en/how-to-integrate-vtex-using-zapier.md b/docs/tutorials/en/how-to-integrate-vtex-using-zapier.md
index 905bb7228..776b064d2 100644
--- a/docs/tutorials/en/how-to-integrate-vtex-using-zapier.md
+++ b/docs/tutorials/en/how-to-integrate-vtex-using-zapier.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-09-19-at-03-41-48
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/how-to-integrate-with-dafiti.md b/docs/tutorials/en/how-to-integrate-with-dafiti.md
index 167bb5605..27b70e461 100644
--- a/docs/tutorials/en/how-to-integrate-with-dafiti.md
+++ b/docs/tutorials/en/how-to-integrate-with-dafiti.md
@@ -64,9 +64,7 @@ The mapping should be done every time a product is sent to Dafiti for the first
 
 Follow the steps below, doing the to/from on the __Mapping Spreadsheet__ between what VTEX has registered with regards to your product and the specific values found in the Dafiti __Query Spreadsheet__.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> any value used that is not found in the Query Spreadsheet will trigger an integration error.
-</div>
+>⚠️ **OBS:** any value used that is not found in the Query Spreadsheet will trigger an integration error.
 
 1. __SKU:__ is the SKU ID in VTEX. This is the SKU ID that you want to send to Dafiti.
 
@@ -89,10 +87,11 @@ Follow the steps below, doing the to/from on the __Mapping Spreadsheet__ between
 <br/>_`Ex:` you are mapping a hoodie. Normally, the column __Model__ contains the value `Hoodie`._
 
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> in the Brazilian integration, Dafiti requires that the name of registered product follows the following guidelines: <strong>Type of Product + Brand + Model + Colour.</strong>
-<br/>
-That being the case, whenever we encounter values for these four fields in VTEX, we will automatically create a new product name. If some of the fields are not present, we send the product’s original name. </div>
+>⚠️ **OBS:** in the Brazilian integration, Dafiti requires that the name of registered product follows the following guidelines: **Type of Product + Brand + Model + Colour.**
+>
+>
+> 
+> That being the case, whenever we encounter values for these four fields in VTEX, we will automatically create a new product name. If some of the fields are not present, we send the product’s original name.
 
 
 ## Sending images
@@ -108,9 +107,7 @@ To send through the Mapping Spreadsheet, follow these step-by-step instructions:
 
 You can send up to __eight images__. In order to do this, you will need to add new columns, following the given pattern: `Image_2`, `Image_3`,..., `Image_8`.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> remember to use <code>http</code> or <code>https</code> at the beginning of your URLs. If you won’t do this, an error will occur when trying to upload the spreadsheet to VTEX.
-</div>
+>⚠️ **OBS:** remember to use `http` or `https` at the beginning of your URLs. If you won’t do this, an error will occur when trying to upload the spreadsheet to VTEX.
 
 
 ## Sending the Product Brand
@@ -118,9 +115,7 @@ You can send up to __eight images__. In order to do this, you will need to add n
 The integration will send the brand that is registered with your product to the VTEX catalogue.
 <br/>_`Ex:` if you are sending an Adidas shirt, the integration will send `Adidas` as the brand._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> similar to what happens with category and specifications, Dafiti has brands that are mapped on its platform. In this case, if any of your products have a brand that is not registered with Dafiti, an integration error will occur. If this happens, get in touch with Dafiti to ask for the brand in questions to be registered on their system.
-</div>
+>⚠️ **OBS:** similar to what happens with category and specifications, Dafiti has brands that are mapped on its platform. In this case, if any of your products have a brand that is not registered with Dafiti, an integration error will occur. If this happens, get in touch with Dafiti to ask for the brand in questions to be registered on their system.
 
 
 ## Uploading
diff --git a/docs/tutorials/en/how-to-integrate-with-facebook.md b/docs/tutorials/en/how-to-integrate-with-facebook.md
index a380eb626..d5426ee2d 100644
--- a/docs/tutorials/en/how-to-integrate-with-facebook.md
+++ b/docs/tutorials/en/how-to-integrate-with-facebook.md
@@ -52,14 +52,10 @@ __Store site URL__: Fill in the address of your store. Example: `https://www.you
 
 Once setup is complete, you must authorize VTEX to make changes to the shopper's Facebook account. To do this, you need to click the __Authorize__ button on the Facebook card, in the __Integrations__ section. With that, you will be asked to inform the required authorizations.
 
-<div class="alert alert-info">
-To enable the authorization, the Facebook account which has admin privileges in Business Manager must be used. If it lacks privileges, the authorization will not be granted and the process will be stuck in a loop.
-</div>
+>ℹ️ To enable the authorization, the Facebook account which has admin privileges in Business Manager must be used. If it lacks privileges, the authorization will not be granted and the process will be stuck in a loop.
 
 After this step, the integration will create a catalog named `VtexIntegration - {STORE NAME}` in Facebook.
 
 This is the catalog in which items will be created and become available.
 
-<div class="alert alert-info">
-You can use the Facebook pixel app to track and optimize your marketing campaigns' results on your store's Google Tag Manager. Learn the step-by-step <a href="https://www.facebook.com/business/help/1021909254506499">here</a>.
-</div>
+>ℹ️ You can use the Facebook pixel app to track and optimize your marketing campaigns' results on your store's Google Tag Manager. Learn the step-by-step [here](https://www.facebook.com/business/help/1021909254506499).
diff --git a/docs/tutorials/en/how-to-make-transfers.md b/docs/tutorials/en/how-to-make-transfers.md
index c062ea3e9..991f22299 100644
--- a/docs/tutorials/en/how-to-make-transfers.md
+++ b/docs/tutorials/en/how-to-make-transfers.md
@@ -66,6 +66,4 @@ The message informs you of the status - whether it was completed successfully or
 
 However, this is not the only way to check this information. If necessary, the retailer can also consult them in the __Statements__ module. In the __"Statements"__ tab, just select the desired statement to view its details.
 
-<div class="alert alert-info">
-As with bank transactions, the requested transfer may be denied if the retailer reaches his account limit. If necessary, a limit increase can be requested through a ticket on VTEX’s customer care platform.
-</div>
+>ℹ️ As with bank transactions, the requested transfer may be denied if the retailer reaches his account limit. If necessary, a limit increase can be requested through a ticket on VTEX’s customer care platform.
diff --git a/docs/tutorials/en/how-to-migrate-a-store-to-pricing.md b/docs/tutorials/en/how-to-migrate-a-store-to-pricing.md
index a59353144..d02dc1c5e 100644
--- a/docs/tutorials/en/how-to-migrate-a-store-to-pricing.md
+++ b/docs/tutorials/en/how-to-migrate-a-store-to-pricing.md
@@ -43,9 +43,7 @@ Pricing has some important differences over the first version. Here are its feat
 
 ## Migrating a store to Pricing v2
 
-<div class="alert alert-info">
-Every new VTEX store is already created with Pricing v2.
-</div>
+>ℹ️ Every new VTEX store is already created with Pricing v2.
 
 Pricing v2 is available for stores that wish to migrate to the new module. Currently, we have an automatic migration process, in which we verify the compatibility of Pricing v2 features with the features currently used by the store.
 
diff --git a/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md b/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md
index cbf999860..ac0ac0049 100644
--- a/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md
+++ b/docs/tutorials/en/how-to-modify-details-of-customers-addresses.md
@@ -25,19 +25,14 @@ To edit customer information you must do the following:
 6. Click `Save`.
 7. Click `Go Back` to see the list of addresses again.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
diff --git a/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
index a03d2234b..0c7abf0bd 100644
--- a/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
@@ -21,18 +21,14 @@ We don't recommend using <a href="https://help.vtex.com/en/tutorial/otimizar-as-
 ## How the search engine works 
 VTEX has an intelligent algorithm that, based on the term searched for, identifies the best result for the user, i.e., it always shoes the result that will generate more conversions into sales.
 
-<div class="alert alert-info">
-See more details on <a href="https://help.vtex.com/en/tutorial/how-does-vtex-search-work--tutorials_542">how the search engine works</a> at VTEX.
-</div>
+>ℹ️ See more details on [how the search engine works](https://help.vtex.com/en/tutorial/how-does-vtex-search-work--tutorials_542) at VTEX.
 
 ## How useful is a substitute word
 If the search engine does not identify the Landing Page, Brand or Department according to the term searched for, it applies a search for a Substitute Word (key work). 
 
 Despite having a low weight in the indexer, the use a substitute words is an extremely important resource, since it permits to reach users that search for grammatically incorrect terms (spagetti), phonetic writing (espagueti) or misspelled words due to typing mistakes (spaguetto), but with the same semantics of the original word (spaguetti).
 
-<div class="alert alert-info">
-A resource frequently used by the internal teams to expedite searches is to input RefId/EAN as the Substitute Word in the product. Therefore, it is possible to make faster searches, with only results and to quickly find the product searched for.
-</div>
+>ℹ️ A resource frequently used by the internal teams to expedite searches is to input RefId/EAN as the Substitute Word in the product. Therefore, it is possible to make faster searches, with only results and to quickly find the product searched for.
 
 ## How do I input a substitute word 
 
diff --git a/docs/tutorials/en/how-to-place-a-regular-order-using-vtex-apis.md b/docs/tutorials/en/how-to-place-a-regular-order-using-vtex-apis.md
index 59386d196..c14b35a52 100644
--- a/docs/tutorials/en/how-to-place-a-regular-order-using-vtex-apis.md
+++ b/docs/tutorials/en/how-to-place-a-regular-order-using-vtex-apis.md
@@ -19,8 +19,7 @@ In this tutorial, you will learn how to place a simple **REGULAR** order (placed
 
 Let's start!
 
-<div class="alert alert-warning">
-<strong>Important:</strong> For any authentication required by the APIs presented in this tutorial, you must provide a valid <b>AppToken</b> and <b>AppKey</b> registered in the <b>License Manager</b> module of your account and empowered with enough permissions.</div>
+>⚠️ **Important:** For any authentication required by the APIs presented in this tutorial, you must provide a valid **AppToken** and **AppKey** registered in the **License Manager** module of your account and empowered with enough permissions.
 
 **REQUIRED PERMISSIONS**
 
diff --git a/docs/tutorials/en/how-to-rank-the-best-selling-items.md b/docs/tutorials/en/how-to-rank-the-best-selling-items.md
index e9d467042..5eb3d6817 100644
--- a/docs/tutorials/en/how-to-rank-the-best-selling-items.md
+++ b/docs/tutorials/en/how-to-rank-the-best-selling-items.md
@@ -15,9 +15,7 @@ legacySlug: how-to-rank-the-best-selling-items
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-warning">
-The <strong>Orders</strong> module was not designed as a Business Intelligence (BI) tool. It's usually through the ERP that the store has access to sales reports.
-</div>
+>⚠️ The **Orders** module was not designed as a Business Intelligence (BI) tool. It's usually through the ERP that the store has access to sales reports.
 
 While the **Orders** module primary goal is to manage the order flow, it is possible to manipulate data from the [order report](https://help.vtex.com/tutorial/planilha-de-pedidos) to extract information that may be useful to your business.
 
diff --git a/docs/tutorials/en/how-to-register-your-salespersons-on-vtex-instore.md b/docs/tutorials/en/how-to-register-your-salespersons-on-vtex-instore.md
index ea474990f..3f256014d 100644
--- a/docs/tutorials/en/how-to-register-your-salespersons-on-vtex-instore.md
+++ b/docs/tutorials/en/how-to-register-your-salespersons-on-vtex-instore.md
@@ -15,6 +15,4 @@ legacySlug: how-to-register-your-salespersons-on-vtex-instore
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-<div class="alert alert-info">
-This article is deprecated. <a href="https://help.vtex.com/en/tracks/instore-setup?step=2">Click here</a> to access our step-by-step tutorial to register vendors on the inStore.
-</div>
+>ℹ️ This article is deprecated. [Click here](https://help.vtex.com/en/tracks/instore-setup?step=2) to access our step-by-step tutorial to register vendors on the inStore.
diff --git a/docs/tutorials/en/how-to-request-receivables-anticipation.md b/docs/tutorials/en/how-to-request-receivables-anticipation.md
index 36af65e58..5f4d46fa9 100644
--- a/docs/tutorials/en/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/en/how-to-request-receivables-anticipation.md
@@ -33,9 +33,7 @@ For example, if your lowest receivable is R$ 10, this is the minimum amount you
 
 ![antecipaçãoEN](https://images.ctfassets.net/alneenqid6w5/655LHSr6GS2RpCvCKYfAup/bade73d74e819b410247130a7662df03/image.png_h_250)
 
-<div class="alert alert-info">
-<strong>Warning</strong>: receivables in dispute or expected for the next business day cannot be anticipated.
-</div>
+>ℹ️ **Warning**: receivables in dispute or expected for the next business day cannot be anticipated.
 
 Check out the step by step to request the anticipation:
 
diff --git a/docs/tutorials/en/how-to-schedule-prices-for-a-range-of-hours.md b/docs/tutorials/en/how-to-schedule-prices-for-a-range-of-hours.md
index b4c5ea741..7098a984c 100644
--- a/docs/tutorials/en/how-to-schedule-prices-for-a-range-of-hours.md
+++ b/docs/tutorials/en/how-to-schedule-prices-for-a-range-of-hours.md
@@ -20,9 +20,7 @@ Among other scenarios, one of the most important points in a massive event such
 ## Scheduling through API
 One of the options to schedule prices by hour is through a price API:
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/pricing-api-overview">View API documentation</a>
-</div>
+>ℹ️ [View API documentation](https://developers.vtex.com/reference/pricing-api-overview)
 
 VTEX backend uses UTC time, where, for example, in Argentina that is GTM-3, to schedule a price x hour through API starting at 00h and finishing at 10h, it is necessary to send 3h more than the time to be scheduled. This is, if the price is to be valid at 00h, I should send 3h, and to finish at 10h, I should send 13h:
 
@@ -34,9 +32,7 @@ JSON Price API:
 
 The price will be automatically invalid at the scheduled time. 
 
-<div class="alert alert-warning">
-<strong>Important</strong>: In case of a price change through the manager’s price interface and the change is saved, the hour schedule will be lost and only the date schedule will be filed.
-</div>
+>⚠️ **Important**: In case of a price change through the manager’s price interface and the change is saved, the hour schedule will be lost and only the date schedule will be filed.
 
 ## Scheduling through the spreadsheet
 
@@ -54,6 +50,4 @@ Price Spreadsheet Columns:
 
 The price will be automatically invalid at the scheduled time.
 
-<div class="alert alert-warning">
-<strong>Important</strong>: Just like in the API, in case of a price change through the manager’s price interface and the change is saved, the hour schedule will be lost and only the date schedule will be valid.
-</div>
+>⚠️ **Important**: Just like in the API, in case of a price change through the manager’s price interface and the change is saved, the hour schedule will be lost and only the date schedule will be valid.
diff --git a/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
index d79ea05cf..fb966e00b 100644
--- a/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/en/how-to-set-up-fingerprint-for-payu.md
@@ -19,13 +19,11 @@ __Device Fingerprint__ is an identifier that acts in payment processing to impro
 
 By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
 
 This article will explain how to associate the Device Fingerprint feature with the PayU affiliation.
 
-<div class="alert alert-info">The settings documented in this article take place in an environment that is external to VTEX, therefore they may be outdated.</div>
+>ℹ️ The settings documented in this article take place in an environment that is external to VTEX, therefore they may be outdated.
 
 1. Login on http://www.google.com/tagmanager/ for the stored to be set up;
 2. Enter the tags section to set up the device session id;
diff --git a/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 5d1b0a247..aa8c31522 100644
--- a/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/en/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -15,9 +15,9 @@ legacySlug: how-to-configure-the-adyen-gateway-on-vtex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
-<div class="alert alert-warning">The configurations documented in this article are performed in an environment external to VTEX and, therefore, may be discontinued without prior notice.</div>
+>⚠️ The configurations documented in this article are performed in an environment external to VTEX and, therefore, may be discontinued without prior notice.
 
 If Adyen is your chosen affiliate, follow the necessary configuration in the step-by-step below for a seamless communication between Adyen and VTEX. 
 
diff --git a/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
index 08f55288b..367f9317f 100644
--- a/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/en/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -19,13 +19,11 @@ __Device Fingerprint__ is an identifier that acts in payment processing to impro
 
 By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
 
 This article will explain how to associate the Device Fingerprint feature with the Braspag affiliation.
 
-<div class="alert alert-info">The settings documented in this article take place in an environment that is external to VTEX, therefore they may be outdated.</div>
+>ℹ️ The settings documented in this article take place in an environment that is external to VTEX, therefore they may be outdated.
 
 To enter the device fingerprint scripts required by Braspag/CyberSource, you will need to use Google Tag Manager. To do so, go to [http://www.google.com/tagmanager](http://www.google.com/tagmanager/) and access your account.
 
diff --git a/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
index 82ba26cf0..1f6c20b0c 100644
--- a/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/en/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -33,9 +33,7 @@ Your customer’s schedule flow starts by choosing the physical store of his pre
 
 ![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
-<div class="alert alert-info">
-You can also provide your customers a link that takes them directly to a specific physical store form. You just have to add the store ID at the end of the URL. Hence, your seller can share your store’s link—for example, using a QR Code or on social media.
-</div>
+>ℹ️ You can also provide your customers a link that takes them directly to a specific physical store form. You just have to add the store ID at the end of the URL. Hence, your seller can share your store’s link—for example, using a QR Code or on social media.
 
 By clicking on a store, your customer is automatically redirected to the form. There they will find information about the store—defined in the implementation step—, and some fields to enter the information about the visit:
 
diff --git a/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index c3cd57359..8b55c4e45 100644
--- a/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/en/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -15,15 +15,11 @@ legacySlug: how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-<div class="alert alert-info">
-The <strong>Responsible for Pick Up</strong> field is only available for the <strong>SmartCheckout™ V6</strong>, version compatible with the Pick Up Points feature.
-</div>
+>ℹ️ The **Responsible for Pick Up** field is only available for the **SmartCheckout™ V6**, version compatible with the Pick Up Points feature.
 
 The [pick up points](/tutorial/configurar-pontos-de-retirada-pickup-points?locale=en) give your customers one more option: instead of waiting for delivery, they can choose to go to a determined point and collect the item in person. By default, this action is linked to the user who made the purchase. However, you can enable the `Responsible for pick up` field at your store checkout so that your customer can appoint someone else to pick up the product.
 
-<div class="alert alert-warning">
-If you have the <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> app installed on your store, the CSS code described in the procedure below must only be entered via the app. Scripts inserted via the VTEX Admin interface (<b>Code > Files</b>) are not reproduced in stores that have the application installed.
-</div>
+>⚠️ If you have the [Checkout UI Settings](https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings) app installed on your store, the CSS code described in the procedure below must only be entered via the app. Scripts inserted via the VTEX Admin interface (**Code > Files**) are not reproduced in stores that have the application installed.
 
 To set this field up (which is disabled by default), follow the steps below:
 
diff --git a/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md b/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md
index cde570400..ea12f2754 100644
--- a/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md
+++ b/docs/tutorials/en/how-to-set-up-your-store-on-seller-portal.md
@@ -53,7 +53,7 @@ Here are some details about the Seller Portal:
 
 ## Setting up your store
 
-<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+>⚠️ The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.
 
 To start selling your products on the marketplace, you need to configure your store on the Seller Portal. This article explains the complete flow of this initial setup and indicates other documentation for you to access each step in more detail. The basic configuration of the Seller Portal includes the steps listed below.
 
@@ -204,6 +204,4 @@ There will be no need for manual configuration for these modules, but we recomme
 
 To integrate with your ERP, check out our [ERP integration guide](https://developers.vtex.com/docs/guides/erp-integration-guide).
 
-<div class="alert alert-info"> 
- <p>To generate the access keys necessary to integrate with your ERP, click on your <strong>profile avatar</strong>, marked by the initial of your email and go to <strong>Account settings > Application keys</strong>.</p>
-</div>
+>ℹ️ To generate the access keys necessary to integrate with your ERP, click on your **profile avatar**, marked by the initial of your email and go to **Account settings > Application keys**.
diff --git a/docs/tutorials/en/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md b/docs/tutorials/en/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
index ca6cb9569..1df1dab5a 100644
--- a/docs/tutorials/en/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
+++ b/docs/tutorials/en/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
@@ -15,6 +15,4 @@ legacySlug: how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal
 subcategory: 1luKrYptdi8WoMYckakUaM
 ---
 
-<div class="alert alert-info">
-  <p>Content under translation.</p>
-</div>
+>ℹ️ Content under translation.
diff --git a/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md b/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md
index 8ce36b45d..f2456a0d1 100644
--- a/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md
+++ b/docs/tutorials/en/how-to-setup-google-analytics-in-vtex-store.md
@@ -20,9 +20,7 @@ subcategory: 1luKrYptdi8WoMYckakUaM
 1. [Configure Google Analytics 4](#configuring-google-analytics-4)
 2. [Configure Google Tag Manager](#configuring-google-tag-manager)
 
-<div class="alert alert-info">
-As of July 1, 2023, Google Analytics 4 will replace Universal Analytics, the previous version of the tool. Therefore, you need to follow this tutorial to make the necessary adjustments to your store. See details about the change in <a href="https://support.google.com/analytics/answer/11583528">this Google announcement</a>.
-</div>
+>ℹ️ As of July 1, 2023, Google Analytics 4 will replace Universal Analytics, the previous version of the tool. Therefore, you need to follow this tutorial to make the necessary adjustments to your store. See details about the change in [this Google announcement](https://support.google.com/analytics/answer/11583528).
 
 ## Configuring Google Analytics 4
 If you were using the previous version of Google Analytics (Universal Analytics) in your store, you need to add a GA4 property. To do so, follow this Google documentation: [Add a Google Analytics 4 property (to a site that already has Analytics)](https://support.google.com/analytics/answer/9744165?hl=pt-BR&ref_topic=9303319#zippy=%2Cneste-artigo).
diff --git a/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md b/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md
index c1b01645b..de4c313dc 100644
--- a/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md
+++ b/docs/tutorials/en/how-to-turn-my-store-website-into-a-pwa.md
@@ -23,9 +23,7 @@ PWA is the English abbreviation for Progressive Web App - a set of techniques us
 
 If you already have a website or web application, you can slowly implement the features that define a PWA, such as notifications, file caching, offline execution, and other features that make the user feel in a native application.
 
-<div class="alert alert-warning">
-VTEX <strong>platform</strong> does not have native features to turn your store into a PWA. It only provides the conditions for this implementation to be made. This resource is available natively for stores that were developed using VTEX IO Store Framework .
-</div>
+>⚠️ VTEX **platform** does not have native features to turn your store into a PWA. It only provides the conditions for this implementation to be made. This resource is available natively for stores that were developed using VTEX IO Store Framework .
 
 ## Google defines exactly what is expected from a PWA:
 
diff --git a/docs/tutorials/en/how-to-use-messages-on-your-io-apps.md b/docs/tutorials/en/how-to-use-messages-on-your-io-apps.md
index 6c51a9c36..6026dd370 100644
--- a/docs/tutorials/en/how-to-use-messages-on-your-io-apps.md
+++ b/docs/tutorials/en/how-to-use-messages-on-your-io-apps.md
@@ -17,9 +17,7 @@ subcategory: 54gbzsku02c4bKmgFbp3v3
 
 VTEX IO has a built-in internationalization service called __Messages__. In this tutorial you will learn how to internationalize your front end apps as well as the responses of your back end. 
 
-<div class="alert alert-info">
-This feature is only available for react/graphql/typedql apps.
-</div>
+>ℹ️ This feature is only available for react/graphql/typedql apps.
 
 ## Messages translation 
 
@@ -60,9 +58,7 @@ To leverage better automatic translations, create a file called `context.json` i
 
 This file works as a translation disambiguation. For example, the string ‘Ciao’ in italian means both ‘Hello’ and ‘Goodbye’ in english, therefore the description is important since it let's us know the exact meaning for a correct translation. 
 
-<div class="alert alert-warning">
-The `context.json` file is necessary and has to contain all translation keys
-</div>
+>⚠️ The `context.json` file is necessary and has to contain all translation keys
  
 ### Migrating from MessagesBuilder 0.x
 
diff --git a/docs/tutorials/en/how-to-use-the-index-report.md b/docs/tutorials/en/how-to-use-the-index-report.md
index 97e42bab2..b5753bfe7 100644
--- a/docs/tutorials/en/how-to-use-the-index-report.md
+++ b/docs/tutorials/en/how-to-use-the-index-report.md
@@ -19,9 +19,7 @@ The **Index Report** shows the indexing status of all products of the store.
 
 ![Indexingreport](https://images.ctfassets.net/alneenqid6w5/3eSr5kdaesUGkCmuAEkQQo/8f9466ec380b282176491d7f6424bbe1/Indexingreport.png)
 
-<div class="alert alert-info">
-<strong>Notice:</strong> For more information, access <a href="/en/tutorial/understanding-how-indexation-works">Understanding the operation of the indexation.</a>
-</div>
+>ℹ️ **Notice:** For more information, access [Understanding the operation of the indexation.](/en/tutorial/understanding-how-indexation-works)
 
 ## How to access the index report
 
diff --git a/docs/tutorials/en/how-to-use-the-meta-tags-control.md b/docs/tutorials/en/how-to-use-the-meta-tags-control.md
index 0e468fcf6..a1bf3a490 100644
--- a/docs/tutorials/en/how-to-use-the-meta-tags-control.md
+++ b/docs/tutorials/en/how-to-use-the-meta-tags-control.md
@@ -54,6 +54,4 @@ See an example of meta tags inserted by the `<vtex:metaTags/>` control for the p
 <link rel="canonical" href="http://lojadobreno.vtexcommercestable.com.br/climbing">
 ```
 
-<div class="alert alert-info">
-If you don't want to use the canonical tag (&lt;link rel="canonical"&gt;), you can disable it using a <a href="https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag">specific control</a>.
-</div>
+>ℹ️ If you don't want to use the canonical tag (&lt;link rel="canonical"&gt;), you can disable it using a [specific control](https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag).
diff --git a/docs/tutorials/en/how-to-use-the-search-result-control.md b/docs/tutorials/en/how-to-use-the-search-result-control.md
index 867ad38c5..19a2fb355 100644
--- a/docs/tutorials/en/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/en/how-to-use-the-search-result-control.md
@@ -17,9 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 The `<vtex.cmc:searchResult/>` control renders a shop window with the products returned by a search made by the user.
 
-<div class="alert alert-info">
-This control works only on pages with search context, ie pages where the displayed results were brought by a search made by the user.
-</div>
+>ℹ️ This control works only on pages with search context, ie pages where the displayed results were brought by a search made by the user.
 
 When the user performs a search in the store, VTEX system tries to bring results according to a priority order of filters. Understand the search in the article [How VTEX search works](/en/tutorial/how-does-vtex-search-work).
 
diff --git a/docs/tutorials/en/how-to-use-the-unavailable-product-class.md b/docs/tutorials/en/how-to-use-the-unavailable-product-class.md
index 00be9bf8a..5be39dd01 100644
--- a/docs/tutorials/en/how-to-use-the-unavailable-product-class.md
+++ b/docs/tutorials/en/how-to-use-the-unavailable-product-class.md
@@ -43,9 +43,7 @@ You can customize your CSS file so that this class displays, for example, a cut
 
 ## Determining to which specification the classed will be assigned
 
-<div class="alert alert-warning">
-The unavailable product class is only assigned to the specification that <b>last</b> appears in the SKU specifications list in the Catalog module.
-</div>
+>⚠️ The unavailable product class is only assigned to the specification that **last** appears in the SKU specifications list in the Catalog module.
 
 For example, in the case of a SKU that only the `Tamanho` specification will receive the unavailability class.
 
diff --git a/docs/tutorials/en/how-to-view-the-orders-details.md b/docs/tutorials/en/how-to-view-the-orders-details.md
index 9fa160351..96cd3fda8 100644
--- a/docs/tutorials/en/how-to-view-the-orders-details.md
+++ b/docs/tutorials/en/how-to-view-the-orders-details.md
@@ -38,9 +38,7 @@ In the left box are the information related to the payment method.
 
 For credit card transactions, each payment (there may be two cards) has an ID generated by VTEX. The acquirer also creates one called Transaction ID (TID). The TID is specific to each card, that is, if an order is paid with two cards, there will be two transactions and thus two TIDs.
 
-<div class="alert alert-warning">
-In transactions without TID, it can be interpreted that the acquirer did not process the payment, that is, that it doesn't have a TID. Occasionally this may generate an error, and a quick way to identify it is to check for a TID.
-</div>
+>⚠️ In transactions without TID, it can be interpreted that the acquirer did not process the payment, that is, that it doesn't have a TID. Occasionally this may generate an error, and a quick way to identify it is to check for a TID.
 
 The most important part of this screen is the transaction interaction log. Here, all VTEX communication with registered affiliates - anti-fraud, gateways and acquirers - is registered, including success and error messages, with their respective codes.
 
diff --git a/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
index e143164c2..8e3d704e3 100644
--- a/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/en/how-to-work-with-different-layouts-for-the-same-page.md
@@ -50,9 +50,7 @@ It happens that the offered conditions are not present on any page:
 
 Hence, it is not possible to asign conditions to specific product or to different layouts through a collection. You would need to register these together with the product condition.
 
-<div class="alert alert-info">
-According to the chosen conditions, an order of priority is established for the applicability of the template. The order first follows, if available, product template, category and, finally, brand. Thus, a template conditioned for a given product layout overlaps the template conditioned for the category in which this product is contained and so on.
-</div>
+>ℹ️ According to the chosen conditions, an order of priority is established for the applicability of the template. The order first follows, if available, product template, category and, finally, brand. Thus, a template conditioned for a given product layout overlaps the template conditioned for the category in which this product is contained and so on.
 
 In case of doubt with this set up, we recommend using the lid: [Layout Test](/en/faq/validating-a-layout-before-moving-it-to-production)
 
diff --git a/docs/tutorials/en/how-trade-policies-work.md b/docs/tutorials/en/how-trade-policies-work.md
index dda76bcbf..661e8823c 100644
--- a/docs/tutorials/en/how-trade-policies-work.md
+++ b/docs/tutorials/en/how-trade-policies-work.md
@@ -60,9 +60,7 @@ You can limit access to the store to specific audiences, for example, a B2B site
 
 ## Account management
 
-<div class="alert alert-warning">
-If you have many sub-accounts, or physical store operations that offer in-store pickup or ship from store, creating multiple trade policies is not the best solution. We suggest creating new <a href="https://help.vtex.com/en/tutorial/o-que-e-store-name">store names</a> for each store within an <a href="https://help.vtex.com/en/tutorial/o-que-e-account-name">account</a>. 
-</div>
+>⚠️ If you have many sub-accounts, or physical store operations that offer in-store pickup or ship from store, creating multiple trade policies is not the best solution. We suggest creating new [store names](https://help.vtex.com/en/tutorial/o-que-e-store-name) for each store within an [account](https://help.vtex.com/en/tutorial/o-que-e-account-name).
 
 Having too many trade policies in a VTEX environment slows down the process of indexing products and displaying them on your website, as well as simulating shipping rates at checkout, which might affect your order conversion rates. By segmenting the catalog based on multiple trade policies instead of creating store names with separate inventories, the store restricts its product offer, which leads to lost sales opportunities and worse delivery conditions. Learn more about [how to create a store name](https://help.vtex.com/en/tutorial/como-criar-um-store-name).
 
diff --git a/docs/tutorials/en/hubspot-suiteshare.md b/docs/tutorials/en/hubspot-suiteshare.md
index 2261a8a72..898276018 100644
--- a/docs/tutorials/en/hubspot-suiteshare.md
+++ b/docs/tutorials/en/hubspot-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: hubspot-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/i-forgot-my-password-suiteshare.md b/docs/tutorials/en/i-forgot-my-password-suiteshare.md
index 3654e9042..f917d8546 100644
--- a/docs/tutorials/en/i-forgot-my-password-suiteshare.md
+++ b/docs/tutorials/en/i-forgot-my-password-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: i-forgot-my-password-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/image-compression.md b/docs/tutorials/en/image-compression.md
index e74f1880b..160d55b49 100644
--- a/docs/tutorials/en/image-compression.md
+++ b/docs/tutorials/en/image-compression.md
@@ -32,9 +32,7 @@ We automatically convert images to the [WebP](https://developers.google.com/spee
 
 Using WebP can lead to a reduction in page load time by 1 to 2 seconds, depending on the layout. Below is an explanation of how image optimization functions with each format.
 
-<div class="alert alert-info">
-  <p>Browsers not yet <a href="https://developers.google.com/speed/webp/faq#which_web_browsers_natively_support_webp">compatible with the WebP format</a> and services, such as integrations and marketplaces, always receive unconverted images in any format. GIF files are not converted to WebP.</p>
-</div>
+>ℹ️ Browsers not yet [compatible with the WebP format](https://developers.google.com/speed/webp/faq#which_web_browsers_natively_support_webp) and services, such as integrations and marketplaces, always receive unconverted images in any format. GIF files are not converted to WebP.
 
 ## PNG
 
diff --git a/docs/tutorials/en/image-widget.md b/docs/tutorials/en/image-widget.md
index a4ff143d0..4026984ea 100644
--- a/docs/tutorials/en/image-widget.md
+++ b/docs/tutorials/en/image-widget.md
@@ -42,14 +42,10 @@ Now that you know how to access the Image Widget, see what you can do next:
 
 After [accessing the Image Widget](#accessing-image-widget), you can add images to it:
 
-<div class="alert alert-warning">
-When adding new images in the Image Widget modal using a <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">development workspace</a>,  the performed settings will be saved directly in the master workspace. In other words, they will immediately be reflected in your store's modal.
-</div>
+>⚠️ When adding new images in the Image Widget modal using a [development workspace](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace),  the performed settings will be saved directly in the master workspace. In other words, they will immediately be reflected in your store's modal.
 <br>
 
-<div class="alert alert-warning">
-  The maximum file size supported by Image Widget is 4 MB. 
-</div>
+>⚠️ The maximum file size supported by Image Widget is 4 MB.
 
 1. Click on `Add new.`
 2. Choose the image you want to add and click on `Open`.
@@ -84,6 +80,4 @@ Go to the block in which you want to replace a picture and:
 ### Removing an image
 To remove a picture in the desired block, click on `More actions` in an image thumbnail and select __remove__. After this, the image will no longer be visible in the block.
 
-<div class="alert alert-warning">
-  When you remove an image, it does not mean it was deleted from the repository. To do that, check the section <a href="#features-within-image-widget">Features within Image Widget</a>.
-</div>
+>⚠️ When you remove an image, it does not mean it was deleted from the repository. To do that, check the section [Features within Image Widget](#features-within-image-widget).
diff --git a/docs/tutorials/en/import-customer-data-brazil.md b/docs/tutorials/en/import-customer-data-brazil.md
index f01c73b93..7700f14c2 100644
--- a/docs/tutorials/en/import-customer-data-brazil.md
+++ b/docs/tutorials/en/import-customer-data-brazil.md
@@ -17,10 +17,9 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 The import of customer data must be made in Master Data. To find out more about sending data, use this article on [Importing data to Master Data](/en/tutorial/importing-data-into-master-data).
 
-<div class="alert alert-danger">
-  <p>This article refers to Master Data v1 fields specifically for stores in <strong>Brazil</strong>. You should check for valid values for different countries.</p>
-  <p>You can also see the guide on <a href="https://developers.vtex.com/docs/guides/import-customer-data">how to import customer information programattically using the Master Data v2 API</a>.</p>
-</div>
+>❗ This article refers to Master Data v1 fields specifically for stores in **Brazil**. You should check for valid values for different countries.
+>
+> You can also see the guide on [how to import customer information programattically using the Master Data v2 API](https://developers.vtex.com/docs/guides/import-customer-data).
 
 The checkout works with CL (customer) and AD (address) entities data.
 
diff --git a/docs/tutorials/en/importing-amazon-classic-fba-orders.md b/docs/tutorials/en/importing-amazon-classic-fba-orders.md
index 8a5178c65..14589399d 100644
--- a/docs/tutorials/en/importing-amazon-classic-fba-orders.md
+++ b/docs/tutorials/en/importing-amazon-classic-fba-orders.md
@@ -51,9 +51,7 @@ The values required will vary according to product segmentation:
 After creating the product specification, your product will be available for FBA Classic orders. If you want to change the shipping type of this product, you need to change the specification value.  
 
 ### 2. Defining a shipping strategy for FBA Classic orders   
-<div class="alert alert-info">
-You need to ensure that the <a href=https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV>trade policy</a> you choose is specifically for Amazon to guarantee that another integration will not use the inventory you create. 
-</div> 
+>ℹ️ You need to ensure that the <a href=https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV>trade policy</a> you choose is specifically for Amazon to guarantee that another integration will not use the inventory you create. 
 
 Then you need to create a dedicated [shipping strategy](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) for FBA Classic orders, telling us how you want your products to be delivered. Doing so will not affect the shipping strategy already defined in the "Defining a shipping strategy" on Amazon step.  
 
diff --git a/docs/tutorials/en/importing-data-into-master-data.md b/docs/tutorials/en/importing-data-into-master-data.md
index 95d45dc53..630844ed8 100644
--- a/docs/tutorials/en/importing-data-into-master-data.md
+++ b/docs/tutorials/en/importing-data-into-master-data.md
@@ -29,17 +29,13 @@ Additionally, to update the existing data, you must export data and change them
 
 Keep the value of column id empty, and a new entry will be created.
 
-<div class="alert alert-warning">
-When entering data in the spreadsheet, make sure that the cell value format matches the format expected by the corresponding column. Format examples are number, text, or date.
-</div>
+>⚠️ When entering data in the spreadsheet, make sure that the cell value format matches the format expected by the corresponding column. Format examples are number, text, or date.
 
 ## How to upload the worksheet
 
 After exporting and editing the worksheet exported, it is time to import the data. Follow the steps below to perform this task.
 
-<div class="alert alert-warning">
-Keep the same format of the worksheet (xls) for the import to be successful.
-</div>
+>⚠️ Keep the same format of the worksheet (xls) for the import to be successful.
 
 1. In the VTEX Admin, access **Store Settings** > **Storefront** > **Master Data**.
 2. Click on the **Applications** tab.
diff --git a/docs/tutorials/en/importing-images-from-a-spreadsheet.md b/docs/tutorials/en/importing-images-from-a-spreadsheet.md
index d6cdc4d53..af66465a6 100644
--- a/docs/tutorials/en/importing-images-from-a-spreadsheet.md
+++ b/docs/tutorials/en/importing-images-from-a-spreadsheet.md
@@ -35,10 +35,9 @@ Completion time will depend on the file size. If the template has more than 2,00
 
 Finally, if the products on the template rows are successfully processed, they will be placed on the indexing queue.
 
-<div class="alert alert-danger">
-<p>Every time you import a template including image information, the system uploads a new image for the SKU concerned. We advise you to be on the lookout for potential duplications.</p>
-<p>If you reimport a template with information previously sent to VTEX, the first image won't be overwritten during import: the image will be duplicated in the SKU registration.</p>
-</div>
+>❗ Every time you import a template including image information, the system uploads a new image for the SKU concerned. We advise you to be on the lookout for potential duplications.
+>
+> If you reimport a template with information previously sent to VTEX, the first image won't be overwritten during import: the image will be duplicated in the SKU registration.
 
 ## Filling in a template to import images
 
@@ -53,9 +52,7 @@ Below, you'll find information on how to fill in each field in the image import
 
 ### URL
 
-<div class="alert alert-info">
-<p>This is a mandatory field. No special characters, periods or accents are admitted on the image name.</p>
-</div>
+>ℹ️ This is a mandatory field. No special characters, periods or accents are admitted on the image name.
 
 It is the URL of the image to be linked to the SKU, which must be public and hosted on an FTP server where the image link originates. The URL must start with the HTTP protocol identifier (`http://`) and end with the file extension (`.jpg`, `.png` or `.gif`). Example: `http://www.imageexample.com.br/imagem03/teste01/exemplo15.jpg`.
 
@@ -65,15 +62,11 @@ You don't need to have your own FTP server to forward the image URLs. You may ho
 
 In addition, you can use an external provider to authenticate the URL.
 
-<div class="alert alert-warning">
-  <p>The recommended size for each image must be below 3,000 KB (3 MB).</p>
-</div>
+>⚠️ The recommended size for each image must be below 3,000 KB (3 MB).
 
 ### NomeImagem
 
-<div class="alert alert-info">
-<p>This is a mandatory field. Special characters, accents or blank spaces are not admitted.</p>
-</div>
+>ℹ️ This is a mandatory field. Special characters, accents or blank spaces are not admitted.
 
 The image name starts after the last /in the image URL and ends with the file extension. Therefore, this field must be filled in with the file name and extension (`.jpg`, `.png` or `.gif`). Example: `exemplo15.jpg`.
 
@@ -81,27 +74,23 @@ The file manager in CMS Legacy Portal will link the file name to the image.
 
 ### TextoImagem
 
-<div class="alert alert-info">
-<p>Special characters and accents are not allowed in this field.</p>
-<p>The <strong>Label</strong> and <strong>TextoImagem</strong> fields should have different values.</p>
-</div>
+>ℹ️ Special characters and accents are not allowed in this field.
+>
+> The **Label** and **TextoImagem** fields should have different values.
 
 The **TextoImagem** field needs to be filled in with the text to be linked to the image. It will remain in the SKU registration in the **Images** tab, in the **Text** field.
 
 ### Label
 
-<div class="alert alert-info">
-<p>This is a mandatory field. Special characters, accents or blank spaces are not admitted.</p>
-<p>The <strong>Label</strong> and <strong>TextoImagem</strong> fields should have different values.</p>
-</div>
+>ℹ️ This is a mandatory field. Special characters, accents or blank spaces are not admitted.
+>
+> The **Label** and **TextoImagem** fields should have different values.
 
 **Label** is the "tag" used to simplify template organization for your website pages, since it refers to its value. Examples: frontal, side, upper.
 
 ### IdSku
 
-<div class="alert alert-info">
-<p>This is a mandatory field. The informed ID must match an existing SKU ID in the catalog.</p>
-</div>
+>ℹ️ This is a mandatory field. The informed ID must match an existing SKU ID in the catalog.
 
 The SKU ID is the code that identifies the SKU to which the image will be linked to. You can get this code by exporting **Products and SKUs**. For further information, read [How to export a product spreadsheet](https://help.vtex.com/en/tutorial/how-to-export-a-product-spreadsheet--2sIroGeqZqaN3NAvaSGwWV).
 
diff --git a/docs/tutorials/en/importing-the-shipping-spreadsheet.md b/docs/tutorials/en/importing-the-shipping-spreadsheet.md
index b7ac1b9e6..720a2bf4e 100644
--- a/docs/tutorials/en/importing-the-shipping-spreadsheet.md
+++ b/docs/tutorials/en/importing-the-shipping-spreadsheet.md
@@ -15,9 +15,7 @@ legacySlug: importing-the-shipping-spreadsheet
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Warning: This documentation is being updated to reflect the concept change from Dashboards to <a href="https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">shipping strategy</a>.
-</div>
+>ℹ️ Warning: This documentation is being updated to reflect the concept change from Dashboards to [shipping strategy](https://help.vtex.com/en/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 
 Before importing the data, it is important to have the VTEX model worksheet saved on your machine, that is, a spreadsheet __identical to our model worksheet__, including the cells formatting, with the header, and already in _.xls_ format (Excel 97-2003). To get the template, click on the __Spreadsheet Model Download link__, which is inside the carrier's settings screen.
@@ -31,17 +29,11 @@ Before importing the data, it is important to have the VTEX model worksheet save
 
 After that, a color orange stripe will highlight the carrier included on the freight table, with the message _Processing_. The time of uploading depends on the size of the spreadsheet.
 
-<div class="alert alert-warning">
-Remember that each new import overwrites the information that was imported before.
-</div>
+>⚠️ Remember that each new import overwrites the information that was imported before.
 
-<div class="alert alert-warning">
-<strong>1st Note:</strong> If the 65,536 lines of the <em>.xls</em> version are insufficient for the registration of all freight values of the carrier, you must create a new tab, with the same header, on the same file, to continue filling out the information.
-</div>
+>⚠️ **1st Note:** If the 65,536 lines of the *.xls* version are insufficient for the registration of all freight values of the carrier, you must create a new tab, with the same header, on the same file, to continue filling out the information.
 
-<div class="alert alert-warning">
-<strong>2nd Note:</strong>Pay attention to the file size. If it is bigger than 10MB, you will need to compress it with a <em>.zip</em> extension. This Zip file must also have 10MB tops for the upload to be successful. If somehow it still exceeds that limit, we recommend you to split it between more carriers.
-</div>
+>⚠️ **2nd Note:**Pay attention to the file size. If it is bigger than 10MB, you will need to compress it with a *.zip* extension. This Zip file must also have 10MB tops for the upload to be successful. If somehow it still exceeds that limit, we recommend you to split it between more carriers.
 
 ## How to convert a shipping spreadsheet
 
diff --git a/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md b/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md
index 1d7904cbe..9f8679308 100644
--- a/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md
+++ b/docs/tutorials/en/including-order-variables-in-the-transactional-email-template.md
@@ -28,9 +28,7 @@ These variables are JSON properties that are in the __JSON Data__ field and can
 
 ### Example
 
-<div class="alert alert-warning">
-Examples of JSON Data will only appear in the templates when you come up with the desired action in your store. If you have not transacted an order, a recurrence, or any other action, JSON Data will be blank.
-</div>
+>⚠️ Examples of JSON Data will only appear in the templates when you come up with the desired action in your store. If you have not transacted an order, a recurrence, or any other action, JSON Data will be blank.
 
 Let's say you want to enter the name of the carrier in the "product sent" email.
 
diff --git a/docs/tutorials/en/indexes-in-master-data.md b/docs/tutorials/en/indexes-in-master-data.md
index 013919532..5bb6398ab 100644
--- a/docs/tutorials/en/indexes-in-master-data.md
+++ b/docs/tutorials/en/indexes-in-master-data.md
@@ -64,9 +64,7 @@ As a result, it will not be possible to enter a name that has already been enter
 
 In the example above, as there is already a record with the **Name** equal to **Mary**, you cannot add another one with the same value.
 
-<div class="alert alert-warning">
-  <p>Use the <strong>Unique values</strong> option with caution. If a value that you want to allow to be repeated is configured as unique, the system will block duplicate records, preventing another one from being entered.</p>
-</div>
+>⚠️ Use the **Unique values** option with caution. If a value that you want to allow to be repeated is configured as unique, the system will block duplicate records, preventing another one from being entered.
 
 #### Multiple fields in the index
 
@@ -82,7 +80,4 @@ In this case, the **Name** value can be repeated, or the **Document** value can
 
 In the example above, there is already a record with the **Name** as **Mary**. You can include another record with the same **Name** as long as the **Document** value is different.
 
-<div class="alert alert-warning">
-  <p>If the same combination of values repeats, the record will not be saved. Use the <strong>Unique values</strong> option only when you are certain that a set of values will not be repeated in different records.
-</p>
-</div>
+>⚠️ If the same combination of values repeats, the record will not be saved. Use the **Unique values** option only when you are certain that a set of values will not be repeated in different records.
diff --git a/docs/tutorials/en/installing-the-widget-with-gtm-suiteshare.md b/docs/tutorials/en/installing-the-widget-with-gtm-suiteshare.md
index 190a766a4..4794b3ea4 100644
--- a/docs/tutorials/en/installing-the-widget-with-gtm-suiteshare.md
+++ b/docs/tutorials/en/installing-the-widget-with-gtm-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: installing-the-widget-with-gtm
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/integrate-with-carrefour.md b/docs/tutorials/en/integrate-with-carrefour.md
index 32ae5a864..10f5fabab 100644
--- a/docs/tutorials/en/integrate-with-carrefour.md
+++ b/docs/tutorials/en/integrate-with-carrefour.md
@@ -50,9 +50,7 @@ The following options will appear:
 - **Mapeamento de SLA de tipo Econômica:** Here you must enter [type of carrier](/en/tutorial/how-does-the-type-of-delivery-work) VTEX that you want to use for `Economical` delivery.
 - **Mapeamento de SLA de tipo Agendada:** Here you must enter [type of carrier](/en/tutorial/how-does-the-type-of-delivery-work) VTEX that you want to use for `Scheduled` delivery.
 
-<div class="alert alert-warning">
-Warning: you must fill at least one of the SLA mapping fields. If none of them is filled, it will not be possible to simulate freight at VTEX and, consequently, the orders made at Carrefour will not be integrated. Also, it will not be possible to save the integration record without any of the fields being filled.
-</div>
+>⚠️ Warning: you must fill at least one of the SLA mapping fields. If none of them is filled, it will not be possible to simulate freight at VTEX and, consequently, the orders made at Carrefour will not be integrated. Also, it will not be possible to save the integration record without any of the fields being filled.
 
 After completing the setup of this screen, click on the **Salvar Configuração** button. 
 
diff --git a/docs/tutorials/en/integrating-with-amazon.md b/docs/tutorials/en/integrating-with-amazon.md
index a760faf20..75985f64d 100644
--- a/docs/tutorials/en/integrating-with-amazon.md
+++ b/docs/tutorials/en/integrating-with-amazon.md
@@ -15,21 +15,15 @@ legacySlug: integrating-with-amazon
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning"> 
-This integration is valid only for the <b>Outdoor</b>, <b>Luggage</b>, <b>Camera and Photo, <b>House and Garden</b>, <b>Computers</b>, <b>Electronics</b>, <b>Sports</b>, <b>Jewelry</b>, <b>Books</b>, <b>Office Material</b>, <b>Tool Kit</b>, <b>Games</b>, <b>Shoes</b> and <b>Clothing</b> categories.
-</div>
+>⚠️ This integration is valid only for the **Outdoor**, **Luggage**, **Camera and Photo, <b>House and Garden**, **Computers**, **Electronics**, **Sports**, **Jewelry**, **Books**, **Office Material**, **Tool Kit**, **Games**, **Shoes** and **Clothing** categories.
 
-<div class="alert alert-warning">
-This integration is available for Brazil, Mexico, the United States, Canada and Europe.
-</div>
+>⚠️ This integration is available for Brazil, Mexico, the United States, Canada and Europe.
 
 ## Authorize VTEX on the Amazon dashboard
 
 In order to integrate with the Amazon Marketplace, it is necessary for the retailer to give authorization to VTEX in his Amazon Seller Central account through the US Market (_www.amazon.com_).
 
-<div class="alert alert-danger">
-In the Amazon dashboard, make sure you're still connected to the US market (www.amazon.com) during all the steps. If it is not, you will receive an error message and you will need to change the market to the US (www.amazon.com) again.
-</div>
+>❗ In the Amazon dashboard, make sure you're still connected to the US market (www.amazon.com) during all the steps. If it is not, you will receive an error message and you will need to change the market to the US (www.amazon.com) again.
 
  When in the Amazon developer registration step, fill in the fields as follows:  
   - Developer’s Name: VTEX  
@@ -48,9 +42,7 @@ Before configuring the integration, you should make sure that all products that
   
   -  __Time Cost__: on Amazon there is the `fulfillment latency` field, which is __used to configure the time to prepare the delivery of a given product__. In order to fill it up massively via integration, it is necessary to fill in the [Cost Time](https://help.vtex.com/en/tutorial/how-to-register-a-dock) field in the dock associated with the sales policy used for Amazon. If this field is not filled, Amazon will use their _default_ value (2 days).
 
-<div class="alert alert-warning">
-NOTE: it is important to fill in this field because if your store is not perfoming according to the configured time, i.e. delayed delivery, your account may be blocked.
-</div>
+>⚠️ NOTE: it is important to fill in this field because if your store is not perfoming according to the configured time, i.e. delayed delivery, your account may be blocked.
 
 ## Integration settings
 
diff --git a/docs/tutorials/en/integrating-with-buscape-bp.md b/docs/tutorials/en/integrating-with-buscape-bp.md
index 96469dca1..8cf3179c9 100644
--- a/docs/tutorials/en/integrating-with-buscape-bp.md
+++ b/docs/tutorials/en/integrating-with-buscape-bp.md
@@ -32,9 +32,7 @@ Several steps are essential for us to initiate the configurations.
 4. Complete the fields as detailed below;
 5. Click on the **Salvar configuração** button. It will only be active if all configurations are correct.
 
-<div class="alert alert-warning">
-Attention! For the trade policy it is necessary at least one bank slip or a credit card to be configured. That is, it is necessary to configure the payment methods for the specific sales channel.
-</div>
+>⚠️ Attention! For the trade policy it is necessary at least one bank slip or a credit card to be configured. That is, it is necessary to configure the payment methods for the specific sales channel.
 
 ### Fields
 
diff --git a/docs/tutorials/en/integrating-with-mercado-livre.md b/docs/tutorials/en/integrating-with-mercado-livre.md
index 6602e97cf..52bc8a18b 100644
--- a/docs/tutorials/en/integrating-with-mercado-livre.md
+++ b/docs/tutorials/en/integrating-with-mercado-livre.md
@@ -68,9 +68,7 @@ The initial steps are essential for a successful configuration:
 
 &bull; __Atributos omitidos no template do produto__ (__Hidden Attributes in the Product Template__): We will see below that in the template configuration for Mercado Livre, you may include the product attributes that you want to be displayed in the template. Setting this field allows you to omit attributes that you do not want to appear in Mercado Livre template.
 
-<div class="alert alert-warning">
-The <em>Atualizar descrição do anúncio ("Refresh ad description"), Texto para avaliação automática do comprador ("Text for automatic buyer evaluation") and E-mail do afiliado ("Affiliate E-mail")</em> fields will be discontinued in the UI. Therefore, they do not need to be filled out. The APIs will continue to be active.
-</div>
+>⚠️ The *Atualizar descrição do anúncio ("Refresh ad description"), Texto para avaliação automática do comprador ("Text for automatic buyer evaluation") and E-mail do afiliado ("Affiliate E-mail")* fields will be discontinued in the UI. Therefore, they do not need to be filled out. The APIs will continue to be active.
 
 ### Sending Product Attributes to Mercado Livre
 
@@ -84,9 +82,7 @@ __You've finished configuring the *first step* of the integration. Now let's go
 
 ## Template configuration
 
-<div class="alert alert-danger">
-For stores in Brazil and Argentina, <strong>Mercado Livre does not accept HTML or CSS template customizations</strong> (with the exception of the &lt;br&gt; tag for line breaks). For stores in other countries, Iframes, Scripts, Forms, Inputs, Meta, Object and Embed tags are not allowed.
-</div>
+>❗ For stores in Brazil and Argentina, **Mercado Livre does not accept HTML or CSS template customizations** (with the exception of the &lt;br&gt; tag for line breaks). For stores in other countries, Iframes, Scripts, Forms, Inputs, Meta, Object and Embed tags are not allowed.
 
 In order for your product to be offered in Mercado Livre, it is necessary to configure the ad template where the product will be displayed. To set up this template, follow the step-by-step instructions below:
 
@@ -109,9 +105,7 @@ If you want to include all attributes and attributes values in the template, you
 
 ``{{#each ATRIBUTOS}} {{NOME}} – {{VALOR}} <br> {{/each}}``
 
-<div class="alert alert-info">
-If you want to hide some attribute in the template, you can do this in the <strong>Bridge</strong> panel by filling in the <strong>Atributos omitidos no template do produto</strong> field ("Attributes hidden in the product template") as explained in the <strong>Set up the Mercado Livre panel at VTEX Bridge</strong> section from the previous step.
-</div>
+>ℹ️ If you want to hide some attribute in the template, you can do this in the **Bridge** panel by filling in the **Atributos omitidos no template do produto** field ("Attributes hidden in the product template") as explained in the **Set up the Mercado Livre panel at VTEX Bridge** section from the previous step.
 
 __Great!__ You have completed the *second stage* of the integration! Now, we will set up the logistics for the delivery of orders made in Mercado Livre.
 
@@ -154,9 +148,7 @@ In this mode, there are two ways of delivering the products. These ways are defi
 
 In this scenario, Mercado Livre gets the products directly from the distribution centers used by your store and delivers them to the final customer.
 
-<div class="alert alert-warning">
-We do not recommend using the <em>Entrega a combinar</em> ("to be arranged") type. In closed orders with this type of delivery, as we do not have the delivery address information, the order will not be integrated with VTEX. For an order to be properly integrated, it must have the delivery information. Therefore, we always recommend using <strong>Mercado Envios</strong>.
-</div>
+>⚠️ We do not recommend using the *Entrega a combinar* ("to be arranged") type. In closed orders with this type of delivery, as we do not have the delivery address information, the order will not be integrated with VTEX. For an order to be properly integrated, it must have the delivery information. Therefore, we always recommend using **Mercado Envios**.
 
 
 ### 
@@ -175,9 +167,7 @@ To go through this process, read the [category, variations, and attributes mappi
 
 After completing the above configurations, you must authorize your integration with Mercado Livre. Follow the steps below:
 
-<div class="alert alert-warning">
-Mercado Livre requires that the authorization is made by the <strong>Master User</strong> of the Mercado Livre account.
-</div>
+>⚠️ Mercado Livre requires that the authorization is made by the **Master User** of the Mercado Livre account.
 
 1. Access the __Bridge__ module.
 2. Click on __Settings__.
diff --git a/docs/tutorials/en/integrating-with-netshoes.md b/docs/tutorials/en/integrating-with-netshoes.md
index 562814516..f2aaef1b0 100644
--- a/docs/tutorials/en/integrating-with-netshoes.md
+++ b/docs/tutorials/en/integrating-with-netshoes.md
@@ -45,17 +45,13 @@ Netshoes is one of the largest marketplaces of sporting goods and is available f
 
 _`Example:` suppose you use Correios (PAC) as a carrier and your Carrier Type in the Carriers dashboard is named "Normal". Then, you should write in the field the name __Normal__. Remember that the word should be exactly the same as the one registered in the Inventory & shipping section._
 
-<div class="alert alert-warning">
-<strong>Note:</strong> If the field is left blank, the integration will use the <strong>cheapest carrier available</strong> when integrating the order.
-</div>
+>⚠️ **Note:** If the field is left blank, the integration will use the **cheapest carrier available** when integrating the order.
 
 - __Delivery Type Mapping (SLA) -> Express:__ the [type of carrier](/en/tutorial/how-does-the-type-of-delivery-work) that you want to use for __express__ deliveries.
 
 _`Example:` Suppose  you use the XPTO carrier, which delivers faster but is more expensive. Your Carrier Type in the Carriers dashboard is called "Fast Delivery." Then, you must write in the field the name __Fast Delivery__. Remember that the word should be exactly the same as the one registered in the Inventory & shipping section_.
 
-<div class="alert alert-warning">
-<strong>Note:</strong> If the field is left blank, the integration will use the <strong>cheapest carrier available</strong> at the time of the order.
-</div>
+>⚠️ **Note:** If the field is left blank, the integration will use the **cheapest carrier available** at the time of the order.
 
 _Subtitle:_<br />
 `*` Required fields.<br />
@@ -86,11 +82,9 @@ The implementation of this API allows Netshoes to consult, in real time, the pri
 
 `http://{accountName}.vtexcommercestable.com.br/api/netshoesintegration/freight`
 
-<div class="alert alert-warning">
-<strong>Note:</strong> If Delivery Mappings are not made, there will be no return of shipping and delivery information for this API.</div>
+>⚠️ **Note:** If Delivery Mappings are not made, there will be no return of shipping and delivery information for this API.
 
-<div class="alert alert-warning">
-<strong>Note 2:</strong> For the API query to be successful, the carrier ID and the warehouse dock ID in VTEX must be a value that contains only numbers.</div>
+>⚠️ **Note 2:** For the API query to be successful, the carrier ID and the warehouse dock ID in VTEX must be a value that contains only numbers.
 
 This is the _second step_ of the integration. In order to complete the process, you must send the specifications of your products to Netshoes.
 
@@ -111,9 +105,7 @@ Mapping should be done whenever a product is first sent to Netshoes. This means
 
 Follow the step-by-step below making the correspondence in the __Mapping Spreadsheet__ between what is registered in your product in VTEX and the values specified according to the Netshoes __Query Spreadsheet__.
 
-<div class="alert alert-warning">
-<strong>Note:</strong> Any value that is not in the Query Spreadsheet will lead to an integration error.
-</div>
+>⚠️ **Note:** Any value that is not in the Query Spreadsheet will lead to an integration error.
 
 1. __SKU ID:__ it is the SKU ID in VTEX. This is the SKU ID that you want to send to Netshoes.
 
@@ -127,8 +119,7 @@ Follow the step-by-step below making the correspondence in the __Mapping Spreads
 <br/>_`Example:` You are mapping a Nike shirt. According to the Query Spreadsheet, the __Brand__ column must be filled with the value `Nike`._
 <br/>
 
-<div class="alert alert-warning">
-<strong>Note:</strong> if the brand you have in your products is not on the Query Spreadsheet, contact Netshoes and ask them to include it in the system. As soon as they confirm the registration, you can use the brand in the mapping. If they have not yet registered it, there will be an integration error for that product.</div>
+>⚠️ **Note:** if the brand you have in your products is not on the Query Spreadsheet, contact Netshoes and ask them to include it in the system. As soon as they confirm the registration, you can use the brand in the mapping. If they have not yet registered it, there will be an integration error for that product.
 
 5. __Color__: fill it in with the SKU Color value.
 <br/>_`Example:` you are mapping a blue and white shorts. According to the Query Spreadsheet, the __Color__ column must be filled with the value `Blue+White`._
diff --git a/docs/tutorials/en/integrating-with-viavarejo-cnova.md b/docs/tutorials/en/integrating-with-viavarejo-cnova.md
index b7dfed8ee..5ca32d717 100644
--- a/docs/tutorials/en/integrating-with-viavarejo-cnova.md
+++ b/docs/tutorials/en/integrating-with-viavarejo-cnova.md
@@ -39,9 +39,7 @@ This article aims to guide you through the process of registering the integratio
 
 &bull; __Name of the Product Specification field containing your Description__: If you want to use a different description than the one already registered in VTEX catalog, you have the option of [creating a product field](/en/tutorial/creating-a-product-field) with type _Long Text_. By filling in this field, the integration will prioritize the submission of the description contained in it (rather than the original description of the product).
 
-<div class="alert alert-danger">
-<strong>Note:</strong> Look at the settings in the creation of this new field so that new information created does <strong>not</strong> appear on your site.
-</div>
+>❗ **Note:** Look at the settings in the creation of this new field so that new information created does **not** appear on your site.
 
 &bull; __Price Divergence Rate*:__ this is the acceptance rate of the difference in value of an order. Any order that has a difference between the selling price in the marketplace and the price determined by the seller [will be compared to this value](/en/faq/why-was-the-order-closed-with-the-wrong-price). If the divergence, in percent, is less than the value defined in this field, the order will be correctly integrated. Otherwise, the order will not be integrated and you will be able to view it in the [orders tab (within the integrations section in the Admin)](/en/tutorial/checking-integrations-in-bridge).
 
diff --git a/docs/tutorials/en/integrating-with-walmart.md b/docs/tutorials/en/integrating-with-walmart.md
index 0773bc7f5..3f5aad2d1 100644
--- a/docs/tutorials/en/integrating-with-walmart.md
+++ b/docs/tutorials/en/integrating-with-walmart.md
@@ -45,9 +45,7 @@ Several steps are essential for us to initiate the configurations.
 
 After the configuration, the integration sends all the products associated with the sales policy determined for Walmart.
 
-<div class="alert alert-warning">
-<strong>Important:</strong> Walmart does not accept HTML code in the product description fields and specification fields.
-</div>
+>⚠️ **Important:** Walmart does not accept HTML code in the product description fields and specification fields.
 
 
 ## Integration Flow
@@ -68,6 +66,4 @@ The __order and shipping flows__ are Walmart's responsibility. VTEX receives que
 2 - [Authenticating your integration](/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations)
 After completing the steps above, you'll need to authenticate the integration with Walmart. All you need to do is send them your appKey (learn how to [generate an appKey for authentications](/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations)). If you have any questions about this process, get in touch with the Walmart support team.
 
-<div class="alert alert-warning">
-Remember that you must associate the appKey to the role <strong>IntegrationProfile - Fulfillment</strong>. It has all the necessary permissions to go through the entire marketplace integration process.
-</div>
+>⚠️ Remember that you must associate the appKey to the role **IntegrationProfile - Fulfillment**. It has all the necessary permissions to go through the entire marketplace integration process.
diff --git a/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md b/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
index c4fc1c7db..d99d3a79f 100644
--- a/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
+++ b/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
@@ -15,9 +15,7 @@ legacySlug: integracao-entre-marketplace-nao-vtex-e-sellers-vtex-acoes-referente
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">marketplace integration guide</a> in our Developer Portal. 
-</div>
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) in our Developer Portal.
 
 One of the steps in integrating a non-VTEX Marketplace with a VTEX Seller is to allow queries to VTEX __Catalog__ to get information on price, inventory, catalog, and shipping data changes.
 
@@ -293,9 +291,21 @@ The Marketplace should use the __API Fulfillment Simulation__ to get the followi
 
 This call simulates a cart in VTEX Checkout, responding with the most updated version of the data.
 
-<div class="alert alert-warning">
-The Fulfillment Simulation call must be used by the Marketplace whenever it needs to obtain updated price, inventory or shipping data. To offer a real-time integration and, consequently, a fluid buying experience, the Marketplace must obtain this data at every step of the client's journey in the store: :<br>- Window display<br>- Product page<br>- Cart<br>- Checkout<br>- Order Placed<br><br>Hence, you ensure that clients are not caught off-guard by potential SKU changes that the Seller failed to inform the Marketplace about. 
-</div>
+>⚠️ The Fulfillment Simulation call must be used by the Marketplace whenever it needs to obtain updated price, inventory or shipping data. To offer a real-time integration and, consequently, a fluid buying experience, the Marketplace must obtain this data at every step of the client's journey in the store: :
+>
+> - Window display
+>
+> - Product page
+>
+> - Cart
+>
+> - Checkout
+>
+> - Order Placed
+>
+> 
+>
+> Hence, you ensure that clients are not caught off-guard by potential SKU changes that the Seller failed to inform the Marketplace about.
 
 ### REST API call example:
 
@@ -341,9 +351,7 @@ Access a VTEX (*Seller*) store and search for SKU price, inventory and shipping
 | quantity       | integer       |   Quantity of desired SKU  |  Yes  |
 | seller       | string       |   ID of Seller selling desired SKU. In a fulfillment simulation context, the seller must always be equal to "1" - "seller 1" means that it's the fulfillment itself.  |   Yes   |
 
-<div class="alert alert-warning">
-The simulation to fetch price/availability must be done with only <strong>1 unit</strong> of the specific item. Cart simulations must obviously include all the desired items, so as to guarantee these items' context when bundled in the cart, which becomes especially important for shipping calculations. 
-</div>
+>⚠️ The simulation to fetch price/availability must be done with only **1 unit** of the specific item. Cart simulations must obviously include all the desired items, so as to guarantee these items' context when bundled in the cart, which becomes especially important for shipping calculations.
 
 #### Response body example
 
diff --git a/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller.md b/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller.md
index 21fcdd3b7..fc23d901b 100644
--- a/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller.md
+++ b/docs/tutorials/en/integration-between-non-vtex-marketplace-and-vtex-seller.md
@@ -15,9 +15,7 @@ legacySlug: integration-between-non-vtex-marketplace-and-vtex-seller
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">marketplace integration guide</a> in our Developer Portal. 
-</div> 
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) in our Developer Portal. 
 
 The final step in integrating a non-VTEX Marketplace with a VTEX Seller is to allow communication with the Seller about __orders__ placed on the Marketplace.
 
@@ -478,9 +476,13 @@ Endpoint: `https://{AccountName}.vtexcommercestable.com.br/api/fulfillment/pvt/o
 
 ## Marketplace Services Endpoint
 
-<div class="alert alert-info">
-  The <strong>Marketplace Services Endpoint</strong> is an endpoint that must be created by the Marketplace, with the objective of receiving 3 different bits of information sent by the Seller:<br>- Invoice<br>- Carrier tracking code (if any)<br>- Cancellation request (when it occurs)
-</div>
+>ℹ️ The **Marketplace Services Endpoint** is an endpoint that must be created by the Marketplace, with the objective of receiving 3 different bits of information sent by the Seller:
+>
+> - Invoice
+>
+> - Carrier tracking code (if any)
+>
+> - Cancellation request (when it occurs)
 
 For the next 3 integration steps, the Marketplace needs to:
 1. Implement this endpoint on your side, preparing it to receive a payload as in the example shown below.
@@ -565,9 +567,7 @@ The Seller sends the tracking code and URL to __Marketplace Services Endpoint__
 
 To receive the tracking code, the final endpoint must be as: `https://{marketplaceServicesEndpoint}/pvt/orders/{marketplaceOrderId}/invoice`
 
-<div class="alert alert-info">
-Even though the route to receive the tracking code is the same as the one used by the Marketplace to receive the invoice (<code>.../invoice</code>), these two processes take place in two distinct steps: a first call in which the Seller sends the invoice data; followed by a second containing the tracking information.
-</div>
+>ℹ️ Even though the route to receive the tracking code is the same as the one used by the Marketplace to receive the invoice (`.../invoice`), these two processes take place in two distinct steps: a first call in which the Seller sends the invoice data; followed by a second containing the tracking information.
 
 ## 6) Receive cancellation request - Seller calls Marketplace endpoint (Marketplace Services Endpoint)
 
diff --git a/docs/tutorials/en/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md b/docs/tutorials/en/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
index 7c614ae91..5900506f6 100644
--- a/docs/tutorials/en/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
+++ b/docs/tutorials/en/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
@@ -291,10 +291,6 @@ Receiving this payload, the integrator must use this information to decide which
 - If there has been a price or stock change, the integrator should call the `https://{accountName}.vtexcommercestable.com.br/api/fulfillment/pvt/orderForms/simulation?sc={salesChannel}&affiliateId={affiliateId}`, as described in the section [Obtain SKU price and inventory data](#3-obtain-sku-price-and-inventory-data).
 - If there has been a change in the SKU other than price or inventory, the integrator should call the `http://{{accountName}}.vtexcommercestable.com.br/api/catalog_system/pvt/sku/stockkeepingunitbyid/{{skuId}}`, as described in the section [Get the data about SKU properties](#2-get-the-data-about-sku-properties).
 
-<div class="alert alert-warning">
-If a new SKU is inserted into the catalog, it will be notified at the endpoint of each affiliate. Because it is a new SKU, it's necessary to fill in the data of this new SKU in the database of the external service. The integrator shall verify that the notified SKU does not yet exist in the external service database. If it's a new SKU, the integrator must follow the same steps described in the <strong>Perform the first load with SKU data</strong> section. If it's an existing SKU, the integrator must follow the steps in the section <strong>Update SKUs data</strong>
-</div>
+>⚠️ If a new SKU is inserted into the catalog, it will be notified at the endpoint of each affiliate. Because it is a new SKU, it's necessary to fill in the data of this new SKU in the database of the external service. The integrator shall verify that the notified SKU does not yet exist in the external service database. If it's a new SKU, the integrator must follow the same steps described in the **Perform the first load with SKU data** section. If it's an existing SKU, the integrator must follow the steps in the section **Update SKUs data**
 
-<div class="alert alert-info">
-If you want to integrate the payment methods of a VTEX seller with an external marketplace, <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">go to our documentation</a>.
-</div>
+>ℹ️ If you want to integrate the payment methods of a VTEX seller with an external marketplace, <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">go to our documentation</a>.
diff --git a/docs/tutorials/en/integration-guide-for-erps-express-catalog.md b/docs/tutorials/en/integration-guide-for-erps-express-catalog.md
index 21d8ac19f..4e8c83c6c 100644
--- a/docs/tutorials/en/integration-guide-for-erps-express-catalog.md
+++ b/docs/tutorials/en/integration-guide-for-erps-express-catalog.md
@@ -15,7 +15,7 @@ legacySlug: integration-guide-for-erps-express-catalog
 subcategory: 5fKgQZhrCw88ACy6Su6GUc
 ---
 
-<div class="alert alert-warning">This article is part of the <a href="https://help.vtex.com/tutorial/integration-guide-for-erps--3VuOwNLmb624ImooEIIkmO">ERP Integration Guide</a>.</div>
+>⚠️ This article is part of the [ERP Integration Guide](https://help.vtex.com/tutorial/integration-guide-for-erps--3VuOwNLmb624ImooEIIkmO).
 
 This document is intended to assist on the catalog, price and inventory integration of the ERP for a store hosted in VTEX, in a fast way.
 
diff --git a/docs/tutorials/en/integration-guide-for-erps-full-catalog.md b/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
index 07db17751..66893b719 100644
--- a/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
+++ b/docs/tutorials/en/integration-guide-for-erps-full-catalog.md
@@ -15,7 +15,7 @@ legacySlug: integration-guide-for-erps-full-catalog
 subcategory: 5fKgQZhrCw88ACy6Su6GUc
 ---
 
-<div class="alert alert-warning">This article is part of the <a href="https://help.vtex.com/tutorial/integration-guide-for-erps--3VuOwNLmb624ImooEIIkmO">ERP Integration Guide</a>.</div>
+>⚠️ This article is part of the [ERP Integration Guide](https://help.vtex.com/tutorial/integration-guide-for-erps--3VuOwNLmb624ImooEIIkmO).
 
 This document is intended to assist on the catalog integration (department, category, brand, images, fields, field values, SKUs activation) of the ERP for a store hosted in VTEX. In this type of integration most of the store's management is ERP.
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md b/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
index 39172be23..7d1a9a0de 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
@@ -15,9 +15,7 @@ legacySlug: integration-guide-for-marketplaces-marketplace-non-vtex-with-payment
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">marketplace integration guide</a> in our Developer Portal. 
-</div> 
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) in our Developer Portal. 
 
 ## Marketplace not Hosted on VTEX Platform selling to Sellers Hosted on VTEX Platform with Payment
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md b/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md
index b805e032e..ca2df66da 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md
@@ -15,9 +15,7 @@ legacySlug: integration-guide-for-marketplaces-marketplace-non-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">marketplace integration guide</a> in our Developer Portal. 
-</div> 
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) in our Developer Portal. 
 
 This document assists in integrating a non-VTEX-hosted Marketplace with a VTEX-hosted Seller.
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md b/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
index 50b626500..62ce31bc1 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
@@ -15,9 +15,7 @@ legacySlug: integration-guide-for-marketplaces-seller-non-vtex-with-payment
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector">marketplace integration guide</a> in our Developer Portal. 
-</div> 
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector) in our Developer Portal. 
 
 ## Seller not VTEX Selling in the Marketplace Hosted on VTEX Receiving Payment
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md b/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md
index f4d4c42ec..00da9f8c4 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces-seller-non-vtex.md
@@ -15,9 +15,7 @@ legacySlug: integration-guide-for-marketplaces-seller-non-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector">marketplace integration guide</a> in our Developer Portal. 
-</div> 
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector) in our Developer Portal. 
 
 ## Seller non VTEX Selling in Marketplace Hosted on VTEX
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces.md b/docs/tutorials/en/integration-guide-for-marketplaces.md
index f884d9817..03482d94c 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces.md
@@ -15,9 +15,7 @@ legacySlug: integration-guide-for-marketplaces
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Check out the updated version of this <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">marketplace integration guide</a> in our Developer Portal. 
-</div> 
+>⚠️ Check out the updated version of this [marketplace integration guide](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) in our Developer Portal. 
 
 ## Marketplaces and sellers
 
@@ -45,7 +43,7 @@ It's very important the integrator get the knowledge of this kind of tools, or o
 
 Every call made to REST APIs from VTEX must be made in “https” and must have in its header the authentication keys. The authentication keys of the header (to access the REST APIs) must be requested to the store administrator or to the operations team that is deploying the store.
 
-<div class="alert alert-warning"><strong>Warning</strong>An exclusive key and token must be created to each integrator, a key from the own store mustn't be used.</div>
+>⚠️ **Warning**An exclusive key and token must be created to each integrator, a key from the own store mustn't be used.
 
 ## Integration models
 
diff --git a/docs/tutorials/en/integration-interfaces.md b/docs/tutorials/en/integration-interfaces.md
index 507c159a7..92b8d10f1 100644
--- a/docs/tutorials/en/integration-interfaces.md
+++ b/docs/tutorials/en/integration-interfaces.md
@@ -46,9 +46,7 @@ See below the documentation required to help start integration through the API R
 
 ### Web Service
 
-<div class="alert alert-warning">
-The use of the VTEX Web Service in integration processes should be avoided as much as possible.
-</div>
+>⚠️ The use of the VTEX Web Service in integration processes should be avoided as much as possible.
 
 Except for the Catalog (Categories, Brands, Products and SKUs), whose API REST is being developed, all other VTEX modules have well defined and high performance API RESTs.
 
diff --git a/docs/tutorials/en/integration-with-google-tag-manager.md b/docs/tutorials/en/integration-with-google-tag-manager.md
index 0e289971a..ce1481056 100644
--- a/docs/tutorials/en/integration-with-google-tag-manager.md
+++ b/docs/tutorials/en/integration-with-google-tag-manager.md
@@ -15,9 +15,7 @@ legacySlug: integration-with-google-tag-manager
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-<div class="alert alert-warning">
-If your store is built with <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">Store Framework</a>, you also need to install the Google Tag Manager pixel app to integrate all pages. See how to do this in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">app documentation</a>.
-</div>
+>⚠️ If your store is built with [Store Framework](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), you also need to install the Google Tag Manager pixel app to integrate all pages. See how to do this in the [app documentation](https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager).
 
 Google Tag Manager is a tag management system created by Google to manage JavaScript and HTML tags used for website tracking and analytics.
 
@@ -52,9 +50,7 @@ After this, you have to set up the store identification code from Tag Manager on
 
 To check available events (triggers) and variables on the pages, which will be used in the tags, you can use the Google Tag Manager preview mode. For more information, check the [Google Tag Manager documentation](https://support.google.com/tagmanager/answer/6107056?hl=pt-BR).
 
-<div class="alert alert-info">
-You can use the Facebook pixel app among your store's Google Tag Manager to track and optimize your marketing campaigns' results on the social network. Learn the step-by-step <a href="https://www.facebook.com/business/help/1021909254506499">here</a>.
-</div>
+>ℹ️ You can use the Facebook pixel app among your store's Google Tag Manager to track and optimize your marketing campaigns' results on the social network. Learn the step-by-step [here](https://www.facebook.com/business/help/1021909254506499).
 
 ## VTEX IO: Installing the Google Tag Manager pixel app
 
diff --git a/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
index adfe3f1ef..46183c320 100644
--- a/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/en/intelligent-search-synonym-suggestions-beta.md
@@ -16,9 +16,7 @@ subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
 
-<div class="alert alert-info">
-  <p>This feature is available for accounts that have a minimum number of sessions and orders for the Artificial Intelligence model to be trained. If you want to implement it in the future, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>. Extra fees may apply in the future.</p>
-</div>
+>ℹ️ This feature is available for accounts that have a minimum number of sessions and orders for the Artificial Intelligence model to be trained. If you want to implement it in the future, please contact [our support](https://support.vtex.com/hc/pt-br/requests). Extra fees may apply in the future.
 
 The [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) allows you to add words, or similar sentences, as synonyms for customer search terms, increasing the chance of successful searches.
 
diff --git a/docs/tutorials/en/intelligent-synonyms.md b/docs/tutorials/en/intelligent-synonyms.md
index a5065203e..2972be636 100644
--- a/docs/tutorials/en/intelligent-synonyms.md
+++ b/docs/tutorials/en/intelligent-synonyms.md
@@ -16,9 +16,7 @@ subcategory: BBzMtJan1UTxC9QZODnlN
 ---
 
 
-<div class="alert alert-info">
-  <p>This feature is available for accounts that have a minimum number of sessions and orders for training the artificial intelligence model. If you would like to implement it, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our support</a>. Additional fees may apply in the future.</p>
-</div>
+>ℹ️ This feature is available for accounts that have a minimum number of sessions and orders for training the artificial intelligence model. If you would like to implement it, please contact [our support](https://support.vtex.com/hc/pt-br/requests). Additional fees may apply in the future.
 
 The [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) allows you to add words, or similar sentences, as synonyms for customer search terms, increasing the chance of successful searches.
 
diff --git a/docs/tutorials/en/interaction-details.md b/docs/tutorials/en/interaction-details.md
index bcddf1712..e73dce533 100644
--- a/docs/tutorials/en/interaction-details.md
+++ b/docs/tutorials/en/interaction-details.md
@@ -15,11 +15,9 @@ legacySlug: interaction-details
 subcategory: 
 ---
 
-<div class="alert alert-info">
-To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
-For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
-</div>  
+>ℹ️ To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module **Offer Management**. As a result, the module will not receive new updates or maintenance.
+> For connectors and marketplaces already integrated into the module, please contact the development team by email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the [Developer Portal's release notes section](https://developers.vtex.com/updates/release-notes) and [VTEX Help Center announcements page](https://help.vtex.com/pt/en/announcements).  
 
 The **Interaction details** page in the [Offer Management](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) module allows sellers to view all interactions of an offer regarding its sending and syncing processes in a comprehensive manner. Interaction details will be available for ten days after registration.
 
diff --git a/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
index 1eaf06bc0..236866cf4 100644
--- a/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/en/interpreting-the-data-of-the-oms-order-bar.md
@@ -35,9 +35,7 @@ In the screenshot of the metrics above, the following information will be displa
 - On the same day last week, the store received 1856 orders until 8:50 p.m.;
 - Finally, compared to one year ago, there was a significant increase in the number of orders: on the same day last year, until the same time, the store received 1425 orders, against 2464 this year.
 
-<div class="alert alert-info">
-The calculation of orders placed in the <b>last year</b> is done by subtracting 52 weeks from the current day. This keeps the reference to same the day of the week. For example: November 24/2017 will be compared with November 25/2016, where both dates are on a Friday.
-</div>
+>ℹ️ The calculation of orders placed in the **last year** is done by subtracting 52 weeks from the current day. This keeps the reference to same the day of the week. For example: November 24/2017 will be compared with November 25/2016, where both dates are on a Friday.
 
 The ranking containing these data is placed on the right corner of the bar, and it shows the position of the store among all VTEX stores. The metrics on its side indicates the evolution between yesterday and today. 
 
diff --git a/docs/tutorials/en/introduction-to-vtex-apis.md b/docs/tutorials/en/introduction-to-vtex-apis.md
index 61592b17a..682d7c04b 100644
--- a/docs/tutorials/en/introduction-to-vtex-apis.md
+++ b/docs/tutorials/en/introduction-to-vtex-apis.md
@@ -121,8 +121,6 @@ On the right side of these indications, Postman displays one Sample Request for
  
 Some APIs also have a Sample Response, which is an example of a response to that request.
  
-<div class="alert alert-warning">
-All content that appears between braces (**{{conteúdo}}**) is a variable, and you must replace it by the correct data before making the request. This is the case, for example, of your store's name, the environment wanted, and the values of AppKey and AppToken.
-</div>
+>⚠️ All content that appears between braces (**{{conteúdo}}**) is a variable, and you must replace it by the correct data before making the request. This is the case, for example, of your store's name, the environment wanted, and the values of AppKey and AppToken.
 
 Check how to create your appKey and appToken in article [Creating appKeys and appTokens to authenticate integrations](/en/tutorial/creating-appkeys-and-apptokens-to-authenticate-integrations).
diff --git a/docs/tutorials/en/inventory-update-history.md b/docs/tutorials/en/inventory-update-history.md
index e78e6cafc..64d99e215 100644
--- a/docs/tutorials/en/inventory-update-history.md
+++ b/docs/tutorials/en/inventory-update-history.md
@@ -36,9 +36,7 @@ To view the update history of a SKU, follow the steps below:
   * The quantity of items before the update.
   * The quantity of itemsafter the update.
 
-<div class="alert alert-warning">
-You can only see the last 50 updates in the update log of a given SKU.
-</div>
+>⚠️ You can only see the last 50 updates in the update log of a given SKU.
 
 The total quantity of items on the [Inventory Management](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139) page is updated in real-time, but it may take up to 1 hour to reflect in the inventory history.
 
diff --git a/docs/tutorials/en/kit-registration.md b/docs/tutorials/en/kit-registration.md
index eb48426ab..78b57a6f7 100644
--- a/docs/tutorials/en/kit-registration.md
+++ b/docs/tutorials/en/kit-registration.md
@@ -70,9 +70,7 @@ Example: A kit has two components. Consider Component 1 has 30 units in stock, w
 
 Kit components can be in different stocks, as long as they are shipped from the same dock. If they do not leave through the same dock, the entire kit becomes unavailable. 
 
-<div class="alert alert-info">
-<p>This is not applicable to the look kit, since it may be sold with the components that are still in stock, without the need for all the components to be in stock.</p>
-</div>
+>ℹ️ This is not applicable to the look kit, since it may be sold with the components that are still in stock, without the need for all the components to be in stock.
 
 ## Price
 
diff --git a/docs/tutorials/en/license-manager-resources.md b/docs/tutorials/en/license-manager-resources.md
index 71f60ef51..2be79704c 100644
--- a/docs/tutorials/en/license-manager-resources.md
+++ b/docs/tutorials/en/license-manager-resources.md
@@ -19,10 +19,8 @@ VTEX provides several pre-defined [roles](https://help.vtex.com/en/tutorial/role
 
 Therefore, the VTEX platform offers you the possibility to create custom access profiles, allowing you to choose precisely which custom profile can access specific resources. Below you will find the descriptions of the resources available on the VTEX platform by product.
 
-<div class="alert alert-danger">
-  <p>Unrestricted use of resources increases the risk of store attacks by leaking login credentials with access to critical resources.
-If you have questions about the description of a specific feature, please feel free to contact us.</p>
-</div>
+>❗ Unrestricted use of resources increases the risk of store attacks by leaking login credentials with access to critical resources.
+> If you have questions about the description of a specific feature, please feel free to contact us.
 
 <iframe src="https://help.vtex.com/tables/resources/en" title="License Manager resources" frameBorder="0" width="100%" height="850"></iframe>
 
diff --git a/docs/tutorials/en/limit-purchases-to-a-payment-method-through-checkout-customization.md b/docs/tutorials/en/limit-purchases-to-a-payment-method-through-checkout-customization.md
index 58ebd4718..b6414758d 100644
--- a/docs/tutorials/en/limit-purchases-to-a-payment-method-through-checkout-customization.md
+++ b/docs/tutorials/en/limit-purchases-to-a-payment-method-through-checkout-customization.md
@@ -19,4 +19,4 @@ We recommend that you limit purchases to a payment method only [through trade po
 
 Another perhaps simpler way is to customize the Checkout so that the CSS will omit the means of payment for the UTM in question. 
 
-<div class="alert alert-danger">But remember that VTEX does not recommend customizing the Checkout, since SmartCheckout exists to maximize efficiency in the purchase closing flow.</div>
+>❗ But remember that VTEX does not recommend customizing the Checkout, since SmartCheckout exists to maximize efficiency in the purchase closing flow.
diff --git a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-sales-policy.md b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-sales-policy.md
index d0775da57..d393a9fe4 100644
--- a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-sales-policy.md
+++ b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-sales-policy.md
@@ -19,21 +19,16 @@ You can limit access to a store for a number of different reasons, such as when
 
 This can be achieved by using Master Data v1 and the store’s sales policy.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Creating a cluster of customers
 
diff --git a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
index 049acfb82..5e248de67 100644
--- a/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
+++ b/docs/tutorials/en/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -19,21 +19,16 @@ You can limit access to a store for a number of different reasons, such as when
 
 This can be achieved by using Master Data v1 and the store’s sales policy.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Creating a cluster of customers
 
diff --git a/docs/tutorials/en/links-suiteshare.md b/docs/tutorials/en/links-suiteshare.md
index efe1d28b1..81cc46b6b 100644
--- a/docs/tutorials/en/links-suiteshare.md
+++ b/docs/tutorials/en/links-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: links
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/lista-da-vez.md b/docs/tutorials/en/lista-da-vez.md
index 2f4abbf0c..c58e60bb6 100644
--- a/docs/tutorials/en/lista-da-vez.md
+++ b/docs/tutorials/en/lista-da-vez.md
@@ -15,6 +15,4 @@ legacySlug: lista-da-vez
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>  
+>⚠️ This content is only available in Portuguese.  
diff --git a/docs/tutorials/en/magento-suiteshare.md b/docs/tutorials/en/magento-suiteshare.md
index 6218b6381..9cbad1175 100644
--- a/docs/tutorials/en/magento-suiteshare.md
+++ b/docs/tutorials/en/magento-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: magento-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/manage-the-sales-comissions-report.md b/docs/tutorials/en/manage-the-sales-comissions-report.md
index d634351a6..95831c17c 100644
--- a/docs/tutorials/en/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/en/manage-the-sales-comissions-report.md
@@ -19,9 +19,7 @@ The sales commission report is a feature that creates a .xlsx document listing t
 
 This article will explain how to generate sales commission reports and how to schedule periodic reports.
 
-<div class="alert alert-warning">
-Before proceeding to the configuration, check with your Customer Success Manager (CSM) if the sales commission report feature has been incorporated into your Admin.
-</div>
+>⚠️ Before proceeding to the configuration, check with your Customer Success Manager (CSM) if the sales commission report feature has been incorporated into your Admin.
 
 ## Generating sales commission reports 
 
@@ -43,9 +41,7 @@ Proceed to the next steps:
 7. Fill in the __"Email address"__ field.
 8. Click on the __"Generate"__ button.
 
-<div class="alert alert-danger">
-It is mandatory to set a start date and an end date. Otherwise, the sales commission report will not be generated.
-</div>
+>❗ It is mandatory to set a start date and an end date. Otherwise, the sales commission report will not be generated.
 
 <div cladd="alert alert-info">
 If you do not want to receive the report by email, do not select the "Receive by email" checkbox. 
@@ -57,9 +53,7 @@ The message "Your report was successfully generated" will be displayed on the sc
 
 Generating the report may take a while if the volume of data is big. In such cases, you can follow the processing as in the image below. 
 
-<div class="alert alert-info">
-Leaving the page will not affect the operation.
-</div>
+>ℹ️ Leaving the page will not affect the operation.
 
 ![Sales Comission Report EN](https://images.ctfassets.net/alneenqid6w5/3WoTE8ibcuYshdJf5sT6KV/e30dfb7f7de7b6dbcd506782e405d470/image.png)
 
@@ -70,13 +64,9 @@ There are situations in which the marketplace needs to analyze its commissions f
 
 For this reason, you can schedule reports to be generated automatically every predetermined time period. 
 
-<div class="alert alert-warning">
-In the Commissions module, only one schedule can be made per account.
-</div>
+>⚠️ In the Commissions module, only one schedule can be made per account.
 
-<div class="alert alert-info">
-Scheduling is an optional feature. You can still generate reports manually if you do not schedule them.
-</div>
+>ℹ️ Scheduling is an optional feature. You can still generate reports manually if you do not schedule them.
 
 Once you are in the Commissions module, click on the "Schedule" button on the right side of the screen. A modal window will be displayed.
 
diff --git a/docs/tutorials/en/managing-content-per-binding.md b/docs/tutorials/en/managing-content-per-binding.md
index 6926a2fd4..76913dad3 100644
--- a/docs/tutorials/en/managing-content-per-binding.md
+++ b/docs/tutorials/en/managing-content-per-binding.md
@@ -27,6 +27,4 @@ Through the VTEX Admin's Storefront, VTEX enables you to do so. Check below the
 
 4. Create, update or/and delete content for the predefined binding and locale, and then save your changes.
 
-<div class="alert alert-warning">
-Whereas editing a block content, you will not be able to change binding and locale data — the fields will be blocked. If you wish to change them, save or discard your changes and return to the Site Editor home page.
-</div>
+>⚠️ Whereas editing a block content, you will not be able to change binding and locale data — the fields will be blocked. If you wish to change them, save or discard your changes and return to the Site Editor home page.
diff --git a/docs/tutorials/en/managing-content-versions.md b/docs/tutorials/en/managing-content-versions.md
index 86e859069..24370f66a 100644
--- a/docs/tutorials/en/managing-content-versions.md
+++ b/docs/tutorials/en/managing-content-versions.md
@@ -49,14 +49,12 @@ After [creating a new content version in Site Editor](#creating-a-new-content-ve
 
 3. Choose the content you want to activate and click on `More options` > **Activate.**
 
-<div class="alert alert-warning">
-  <p>When accessing <i>Apply to</i>, the option <i>this URL</i> will always appear above <i>this template</i>. This means that if the block has two versions, each one with a different application option, the user will only be able to reactivate the version applied in the template if he deletes the version applied by URL.</p>
-
-After clicking on `more options` > **Activate**, the new content will be published on your store.
-
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-You can only have one content active at a time. If you activate one content, the others are deactivated.
-</div>
+>⚠️ When accessing <i>Apply to</i>, the option <i>this URL</i> will always appear above <i>this template</i>. This means that if the block has two versions, each one with a different application option, the user will only be able to reactivate the version applied in the template if he deletes the version applied by URL.
+>
+> After clicking on `more options` > **Activate**, the new content will be published on your store.
+>
+> <div>
+> You can only have one content active at a time. If you activate one content, the others are deactivated.
 
 ## Scheduling content updates
 
diff --git a/docs/tutorials/en/managing-delivery-capacity-beta.md b/docs/tutorials/en/managing-delivery-capacity-beta.md
index 63d5ead12..2ec2f714a 100644
--- a/docs/tutorials/en/managing-delivery-capacity-beta.md
+++ b/docs/tutorials/en/managing-delivery-capacity-beta.md
@@ -15,15 +15,11 @@ legacySlug: managing-delivery-capacity-beta
 subcategory: 
 ---
 
-<div class="alert alert-warning">
-This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a>.
-</div>
+>⚠️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/pt-br/requests).
 
 You can track the availability of delivery windows and the number of items/orders that can still be placed in each delivery window on the Delivery capacity page.
 
-<div class="alert alert-warning">
-To manage your delivery capacity, you must previously configure your shipping policies and enable scheduled deliveries. To learn how to do that, check out the articles[ Shipping policy](link) and [Scheduled delivery](link).
-</div>
+>⚠️ To manage your delivery capacity, you must previously configure your shipping policies and enable scheduled deliveries. To learn how to do that, check out the articles[ Shipping policy](link) and [Scheduled delivery](link).
 In the Admin, go to **Inventory & shipping > Delivery capacity**.
 
 The Delivery capacity page displays a list of your store's delivery windows. The list is based on the shipping policy selected in the Shipping policy filter and the time frame specified in the Date filter.
@@ -37,6 +33,4 @@ Once you have selected a shipping policy and a date, you will see the delivery w
 *   **Available**: number of items/orders that can still be scheduled (the total capacity minus the booked items).
 *   **Status**: classified as visible or not visible, depending on the availability of the delivery window. The delivery window will be shown as visible for your customers if its capacity hasn’t been reached yet.
 *   
-<div class="alert alert-info">
-By clicking on EDIT SHIPPING POLICY, you’ll be redirected to the shipping policy page selected in the Shipping policy filter, where you can edit it.
-</div>
+>ℹ️ By clicking on EDIT SHIPPING POLICY, you’ll be redirected to the shipping policy page selected in the Shipping policy filter, where you can edit it.
diff --git a/docs/tutorials/en/managing-delivery-capacity.md b/docs/tutorials/en/managing-delivery-capacity.md
index 6aab4b6c8..7bd93b2e8 100644
--- a/docs/tutorials/en/managing-delivery-capacity.md
+++ b/docs/tutorials/en/managing-delivery-capacity.md
@@ -19,9 +19,9 @@ You can track the availability of delivery windows and the number of items/order
 
 To manage your **Delivery capacity**, you must previously configure your [shipping policies](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) and enable [scheduled deliveries](https://help.vtex.com/en/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi). 
 
-<div class="alert alert-warning">
-For <a href="https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a> and <a href="https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Delivery capacity</a> to perform correctly, you must follow the rules below:<p><ul><li>The result from {<a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {shipping policy ID} cannot exceed 60 characters.</li><li>Do not use spaces in <a href="https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">shipping policy IDs</a>.</li></ul></p>
-</div>
+>⚠️ For [Scheduled delivery](https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) and [Delivery capacity](https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) to perform correctly, you must follow the rules below:
+> *The result from {[account name](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {shipping policy ID} cannot exceed 60 characters.
+> * Do not use spaces in [shipping policy IDs](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 In the VTEX Admin, go to **Shipping > Delivery capacity**, or type **Delivery capacity** in the search bar at the top of the page. The **Delivery capacity** displays a list of your store's delivery windows. The list is based on the shipping policy selected in the `Shipping policy` filter and the time frame specified in the `Date` filter.
 
diff --git a/docs/tutorials/en/managing-http-headers.md b/docs/tutorials/en/managing-http-headers.md
index 537e8fcb3..8601653b7 100644
--- a/docs/tutorials/en/managing-http-headers.md
+++ b/docs/tutorials/en/managing-http-headers.md
@@ -44,9 +44,7 @@ Below, check the headers that accept editing:
 
 It is possible to configure a custom header, which is a value that is not standardized and is specific to the store's particular requirements or functionalities.
 
-<div class="alert alert-warning">
-Each account is limited to adding a single custom header.
-</div>
+>⚠️ Each account is limited to adding a single custom header.
 
 If you need to configure a custom header, open a ticket to the VTEX Support, providing the keys and values to be set, as you are entirely responsible for this information. To guide you, refer to the MDN’s documentation about [Headers](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers). 
 
diff --git a/docs/tutorials/en/managing-loading-docks.md b/docs/tutorials/en/managing-loading-docks.md
index ef4d56f1a..b28bd2933 100644
--- a/docs/tutorials/en/managing-loading-docks.md
+++ b/docs/tutorials/en/managing-loading-docks.md
@@ -18,9 +18,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Loading docks are one of the logistical stages of your store. A loading dock represents an intermediate point between the warehouse and the carrier. It is the location where products will be shipped from. Loading docks receive items coming from warehouses or distribution centers and deliver them to carriers, which will deliver them to the final recipient. 
 
-<div class="alert alert-info">
-To learn more about loading docks in the VTEX system, see <a href="https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj">Loading docks</a>.
-</div>
+>ℹ️ To learn more about loading docks in the VTEX system, see [Loading docks](https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj).
 
 This article describes how to:
 
@@ -31,17 +29,18 @@ This article describes how to:
 
 To configure a loading dock correctly, you need to: create the loading dock, fill in the fields for adding it (which include working hours and priority), and associate the loading dock with a [trade policy](https://help.vtex.com/en/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE), a warehouse, and a [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140?&utm_source=autocomplete). 
 
-<div class="alert alert-warning">
-For the logistics system to work as expected, we suggest that you configure it in the following order:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Trade policy;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">Loading dock;</a></li>
-<li>Warehouse.</li>
-</ol>
-</body>
-</div>
+>⚠️ For the logistics system to work as expected, we suggest that you configure it in the following order:
+> <body>
+>
+> [Trade policy;](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. [Shipping policy;](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+>
+> 3. [Loading dock;](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+>
+> Warehouse.
+>
+> </body>
 
 ## Adding a loading dock
 
diff --git a/docs/tutorials/en/managing-page-and-template-content.md b/docs/tutorials/en/managing-page-and-template-content.md
index 27f1d70a1..be2dd65eb 100644
--- a/docs/tutorials/en/managing-page-and-template-content.md
+++ b/docs/tutorials/en/managing-page-and-template-content.md
@@ -17,9 +17,7 @@ subcategory: 9Arh3cJIOYlfSD1MUC2h3
 
 The Site Editor natively reflects the Store Theme app, enabling you to overwrite the predefined configurations for blocks and create new content for your store pages and templates.
 
-<div class="alert alert-info">
-The Site Editor does not allow you to add a new block to a template or specific page, only overwrite existing block configurations from the Store Theme app.  
-</div>
+>ℹ️ The Site Editor does not allow you to add a new block to a template or specific page, only overwrite existing block configurations from the Store Theme app.
 
 Exercise your autonomy over code and build the desired storefront scenario according to your business needs using a friendly interface in your favor!
 
@@ -36,21 +34,15 @@ In the VTEX Admin:
 
 2. Click on `Versions` on your top-right corner.
 
-<div class="alert alert-info">
-The content you see when you click on a block is the one currently active. For more information about <b>Versions</b>, access <a href="https://help.vtex.com/en/tutorial/managing-content-versions--4loXo98CZncY0NnjKrScbG">Managing content versions</a> and <a href="https://help.vtex.com/en/tutorial/scheduling-content-updates--5L93gED3wgSRoWpFJlJ2ns">Scheduling content <code>updates</code></a>
-</div>
+>ℹ️ The content you see when you click on a block is the one currently active. For more information about **Versions**, access [Managing content versions](https://help.vtex.com/en/tutorial/managing-content-versions--4loXo98CZncY0NnjKrScbG) and [Scheduling content `updates`](https://help.vtex.com/en/tutorial/scheduling-content-updates--5L93gED3wgSRoWpFJlJ2ns)
 
 3. Click on the `New content` button.
 4. Perform the desired changes according to the available configurations for the block. 
 5. Define if the content should be activated once saved by clicking on the `Activate now` checkbox. You can also define a start date and end date if desired. To do so, toggle the respective buttons and choose the suitable date in the calendar.
 
-  <div class="alert alert-warning">
-Once the <code>this URL</code> checkbox is checked, the content will only be visible in the specific URL in which you saved your changes. Therefore, be careful with parameters and other URL components that may impact the content display — the more specific your URL is, i.e., the more it has parameters and query strings, the more restricted the new content will be.
-</div>
+  >⚠️ Once the `this URL` checkbox is checked, the content will only be visible in the specific URL in which you saved your changes. Therefore, be careful with parameters and other URL components that may impact the content display — the more specific your URL is, i.e., the more it has parameters and query strings, the more restricted the new content will be.
 
-  <div class="alert alert-info">
-The Site Editor applies content configurations according to the parameter hierarchy. Natively reproduce content for all pages under the same parent parameter by only creating content for the latter. Consider a given category URL, for example. By creating content for it, all product pages' URLs whose father parameter is the category will also be updated.
-</div>
+  >ℹ️ The Site Editor applies content configurations according to the parameter hierarchy. Natively reproduce content for all pages under the same parent parameter by only creating content for the latter. Consider a given category URL, for example. By creating content for it, all product pages' URLs whose father parameter is the category will also be updated.
 
 6. Still in the `Visibility` section, check whether the content will only be created in the URL to which you initially navigated or in the whole template — including the URL you are currently on and all others from the template. 
 7. Save your changes.
@@ -64,9 +56,7 @@ The Site Editor applies content configurations according to the parameter hierar
 2. The available content is from the current active one. Edit the fields with the new values or click on `Versions` to edit other contents' configurations. 
 3. Save your changes.
 
-  <div class="alert alert-warning">
-Contents derived from the source code, i.e., the Store Theme app, can not have their visibility updated by you through Site Editor. Regardless of your actions, they are always displayed per template and not URL. Contents that were manually created on Site Editor, in turn, can have their visibility changed to URL or template, according to your needs.
-</div>
+  >⚠️ Contents derived from the source code, i.e., the Store Theme app, can not have their visibility updated by you through Site Editor. Regardless of your actions, they are always displayed per template and not URL. Contents that were manually created on Site Editor, in turn, can have their visibility changed to URL or template, according to your needs.
 
 ## Deleting and resetting content
 
@@ -78,9 +68,7 @@ Contents derived from the source code, i.e., the Store Theme app, can not have t
 3. Click on the desired content's kebab menu (three points). 
 4. Click on `Delete` or `Reset` and confirm your action.
 
-<div class="alert alert-warning">
-The actions <code>Delete</code> and <code>Reset</code> depend on the content type. Native contents, i.e., contents created in the source code, can not be deleted in the admin, only reset (if any update was performed using Site Editor). You can only delete contents that you manually created through the Site Editor.
-</div>
+>⚠️ The actions `Delete` and `Reset` depend on the content type. Native contents, i.e., contents created in the source code, can not be deleted in the admin, only reset (if any update was performed using Site Editor). You can only delete contents that you manually created through the Site Editor.
 
 ## Setting active and inactive content
 
@@ -92,7 +80,5 @@ Notice that by clicking on a given content's kebab menu (three dots), the only a
 
 The successful path to define which content should be active and inactive is to delete or reset the current active content to let the first inactive inline become activated instead. 
 
-<div class="alert alert-info">
-The line for inactive contents starts from the newest content to the oldest. Keep in mind that the contents created through Site Editor always prevail over what was defined in the Store Theme.
-</div>
+>ℹ️ The line for inactive contents starts from the newest content to the oldest. Keep in mind that the contents created through Site Editor always prevail over what was defined in the Store Theme.
 
diff --git a/docs/tutorials/en/managing-pages.md b/docs/tutorials/en/managing-pages.md
index 6a3cabac4..d28607e6a 100644
--- a/docs/tutorials/en/managing-pages.md
+++ b/docs/tutorials/en/managing-pages.md
@@ -34,9 +34,7 @@ In **Headless CMS**, you can manage all the URL routes and page templates for yo
 To create and manage a page, follow these steps:
 
 1. In your VTEX Admin, access **Headless CMS**.
-<div class="alert alert-warning">
-  Make sure you are in the correct project. If not, go to the <b>Project</b> menu in the upper left corner, select the name of the project where you want to create the page, and continue to step 2.
-</div>
+>⚠️ Make sure you are in the correct project. If not, go to the **Project** menu in the upper left corner, select the name of the project where you want to create the page, and continue to step 2.
 2. Click `Create document` and select the desired page type. 
 
 3. Under `Untitled`, name the page.
diff --git a/docs/tutorials/en/managing-projects.md b/docs/tutorials/en/managing-projects.md
index 8dd17bf7e..8c4552f42 100644
--- a/docs/tutorials/en/managing-projects.md
+++ b/docs/tutorials/en/managing-projects.md
@@ -23,9 +23,7 @@ Each project is customized with its own settings, content, and branding accordin
 
 In this guide, you will learn how to manage each frontend project of your store.
 
-<div class="alert alert-warning">
-  <a href="https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview"> FastStore WebOps users</a>: Changes made through the Headless CMS in VTEX Admin, such as creating new content types, adding sections, or updating fields, may not automatically appear in the storefront once you publish them. This is a known issue, and you should contact your development team to implement the necessary workaround. For detailed instructions, refer to the <a href="https://help.vtex.com/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW"> WebOps app is not fully integrated with Headless CMS</a> known issue article.
-</div>
+>⚠️ [ FastStore WebOps users](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview): Changes made through the Headless CMS in VTEX Admin, such as creating new content types, adding sections, or updating fields, may not automatically appear in the storefront once you publish them. This is a known issue, and you should contact your development team to implement the necessary workaround. For detailed instructions, refer to the [ WebOps app is not fully integrated with Headless CMS](https://help.vtex.com/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW) known issue article.
 
 ## Before you begin
 For the Headless CMS management, make sure the [resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar`, `Settings*`, and `CMS GraphQL API` are associated with your [user role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Otherwise, [create a custom user role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creating-a-role) and add these resources to it or add these resources to an existing user role.
diff --git a/docs/tutorials/en/managing-redirects-per-binding.md b/docs/tutorials/en/managing-redirects-per-binding.md
index b0506bf1c..97668eba0 100644
--- a/docs/tutorials/en/managing-redirects-per-binding.md
+++ b/docs/tutorials/en/managing-redirects-per-binding.md
@@ -50,17 +50,13 @@ In VTEX Admin:
 
 ![en-remove-redirect](https://images.ctfassets.net/alneenqid6w5/4Ki1noxgrPgStT4wZGbrCk/7de9c0c5b3a4b9c734657c96ae20cccf/remove-redirect.png)
 
-<div class="alert alert-warning">
-A bug may be found when trying to click on redirects with query strings. The VTEX product team is already aware of this unexpected behavior and working on the fix. If you cannot click on the desired redirect to delete it, opt to do it through the spreadsheet while the issue is not resolved. 
-</div>
+>⚠️ A bug may be found when trying to click on redirects with query strings. The VTEX product team is already aware of this unexpected behavior and working on the fix. If you cannot click on the desired redirect to delete it, opt to do it through the spreadsheet while the issue is not resolved.
 
 ## Importing and exporting redirects
 
 To manage your store's redirects in bulk, you can import and export a redirect spreadsheet. 
 
-<div class="alert alert-warning">
-The spreadsheet's inputs will be mandatorily created or deleted from the store's redirect list — it is not possible to create <i>and</i> delete redirects using the same spreadsheet. Before filling out and uploading yours to the admin, keep in mind your final goal with it.
-</div>
+>⚠️ The spreadsheet's inputs will be mandatorily created or deleted from the store's redirect list — it is not possible to create <i>and</i> delete redirects using the same spreadsheet. Before filling out and uploading yours to the admin, keep in mind your final goal with it.
 
 1. Click on the `Import` button and then on `Download Template`. Click on the `Export` button if you aim to download and modify the pre-saved redirect list. 
 2. Open the spreadsheet template once the download is done and fill out the cells in the suitable columns according to the table below:
@@ -79,9 +75,7 @@ The spreadsheet's inputs will be mandatorily created or deleted from the store's
 
   ![en-redirect-planilha](https://images.ctfassets.net/alneenqid6w5/1LA0kpUcu5NhfUgWWhkjea/b83ae63b44fa2367877b00daf47467c7/redirect-planilha.png)
 
-  <div class="alert alert-warning">
-By clicking on the <code>Save</code> button, you will create all the redirects listed in your spreadsheet, whereas clicking on the <code>Delete</code> button will remove all of them from your store's redirect database.
-</div>
+  >⚠️ By clicking on the `Save` button, you will create all the redirects listed in your spreadsheet, whereas clicking on the `Delete` button will remove all of them from your store's redirect database.
 
 6. Upload the spreadsheet from your local files.
 7. Click on the `Import file` button.
diff --git a/docs/tutorials/en/managing-shipping-policies.md b/docs/tutorials/en/managing-shipping-policies.md
index e5dbcbfbf..ee35cf66f 100644
--- a/docs/tutorials/en/managing-shipping-policies.md
+++ b/docs/tutorials/en/managing-shipping-policies.md
@@ -103,9 +103,7 @@ To activate or deactivate a shipping policy, follow the steps below:
 
 To delete a shipping policy, follow the steps below:
 
-<div class="alert alert-danger">
-Deleting a shipping policy is permanent and cannot be undone.
-</div>
+>❗ Deleting a shipping policy is permanent and cannot be undone.
 
 1. In the VTEX Admin, go to **Shipping > Shipping Strategy** or type **Shipping Strategy** in the search bar at the top of the page.
 2. In the **Shipping Policies** tab, in the row for the shipping policy you want, click the menu icon <i class="fas fa-ellipsis-v"></i>. You can [search](#searching-for-shipping-policies) for policies or [filter by](#filtering-shipping-policies) certain criteria.
diff --git a/docs/tutorials/en/managing-shipping-rates.md b/docs/tutorials/en/managing-shipping-rates.md
index a9c26f9c8..22337c8b4 100644
--- a/docs/tutorials/en/managing-shipping-rates.md
+++ b/docs/tutorials/en/managing-shipping-rates.md
@@ -22,9 +22,7 @@ Your store's [shipping rates](https://help.vtex.com/en/tutorial/tarifas-de-envio
 * [Edit shipping rates](#editing-shipping-rates).
 * [Delete shipping rates](#deleting-shipping-rates).
 
-<div class="alert alert-info">
-If you need to update or add multiple shipping rates, we recommend using the shipping rate template instead of the <b>Shipping rates</b> module. If you want to check out how shipping rates are added and displayed to the end customer, use the <b><a href="https://help.vtex.com/en/tutorial/simulacao-de-frete--tutorials_144">Shipping simulator</a></b> module.
-</div>
+>ℹ️ If you need to update or add multiple shipping rates, we recommend using the shipping rate template instead of the **Shipping rates** module. If you want to check out how shipping rates are added and displayed to the end customer, use the **[Shipping simulator](https://help.vtex.com/en/tutorial/simulacao-de-frete--tutorials_144)** module.
 
 ## Adding shipping rates
 
diff --git a/docs/tutorials/en/managing-singleton-content-types.md b/docs/tutorials/en/managing-singleton-content-types.md
index 7e83eb6e1..645288c8d 100644
--- a/docs/tutorials/en/managing-singleton-content-types.md
+++ b/docs/tutorials/en/managing-singleton-content-types.md
@@ -20,18 +20,14 @@ Singleton content types allow creating and managing a single page, ensuring that
 This content type avoids potential conflicts and inconsistencies when multiple pages of the same content type are created. For example, you can use Singleton for your store's Home page to ensure that there is only one Home page and that all updates and requests to this page always return the same result.
 ![singleton-en](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/336d3df9b113a1b919209c304856c339/singleton-en.gif)
 
-<div class="alert alert-warning">
-  To create the Singleton content type, check with your developer team if the <i>isSingleton</i> property is implemented or ask them to follow the instructions in <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> to add it to the desired content type.
-</div>
+>⚠️ To create the Singleton content type, check with your developer team if the <i>isSingleton</i> property is implemented or ask them to follow the instructions in [Using isSingleton in a content type](https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type) to add it to the desired content type.
 
 ## Creating the Singleton
 1. Access the **Admin > Storefront > Headless CMS**.
 2. Select `CREATE NEW` and choose the name of the singleton content type, for example, **Home**.
 3. Edit the page as you desire using new sections.
 
-<div class="alert alert-warning">
-You can only create the Singleton once. The Singleton page will not be displayed in the content type list if it already exists.
-</div>
+>⚠️ You can only create the Singleton once. The Singleton page will not be displayed in the content type list if it already exists.
 
 ## Editing the Singleton
 1. Access the **Admin > Storefront > Headless CMS**.
@@ -44,9 +40,7 @@ You can only create the Singleton once. The Singleton page will not be displayed
 2. Click the project where the Singleton was created.
 3. Click `Unpublish` > `Unpublish Now`.
 
-<div class="alert alert-warning">
-Before unpublishing, make sure there are no existing drafts. Otherwise, you won't be able to proceed. If you have drafts, either delete them or schedule them for publication.
-</div>
+>⚠️ Before unpublishing, make sure there are no existing drafts. Otherwise, you won't be able to proceed. If you have drafts, either delete them or schedule them for publication.
 
 4. A modal will display for you to confirm the unpublishing of the page.
 5. Click and hold `UNPUBLISH` to unpublish content.
@@ -55,6 +49,4 @@ Before unpublishing, make sure there are no existing drafts. Otherwise, you won'
 1. On the Singleton page, select `more`(kebab menu) and choose `Delete`.
 2. Choose`DELETE` and `BACK TO PAGES`. 
 
-<div class="alert alert-warning">
-  If you want to restore the page and its content, click <i>RESTORE</i>.
-</div>
+>⚠️ If you want to restore the page and its content, click <i>RESTORE</i>.
diff --git a/docs/tutorials/en/managing-stock-items.md b/docs/tutorials/en/managing-stock-items.md
index 1941045c3..293851ca1 100644
--- a/docs/tutorials/en/managing-stock-items.md
+++ b/docs/tutorials/en/managing-stock-items.md
@@ -22,9 +22,7 @@ This article contains information about the **Inventory Management** page. Learn
 * [The inventory information is divided](#inventory-information).
 * [The search filters are organized to make it easier to find specific SKUs](#search-filters).
 
-<div class="alert alert-info"> 
-To access the inventory using SKUs, loading docks, or warehouses via API, use the <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-"> Inventory API</a>.
-</div>
+>ℹ️ To access the inventory using SKUs, loading docks, or warehouses via API, use the [ Inventory API](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 Other possible actions in the **Inventory Management** page are:
 
@@ -50,9 +48,7 @@ In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type
     * **Infinite Inventory:** allows you to add infinite SKU units, making it always available for your store's checkout. This rules out the need to update the count for this SKU.
     * **Lead time (days):** Optional setting of shipping time at SKU level. When you define a time for the SKU of a warehouse, that is added to the [shipping time calculation](https://help.vtex.com/en/tutorial/como-funciona-o-calculo-de-envio--tutorials_116). By default, the [lead time](https://help.vtex.com/en/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) is set as zero days and counted as business days, but you can [change it to calendar days](https://help.vtex.com/en/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#configuring-lead-time-calculation-in-calendar-days-optional). To configure hours, minutes, and seconds, use the [Update inventory by SKU and warehouse endpoint](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
-<div class="alert alert-danger">
-To ensure the items added to the inventory will be available for sale on the store, the <a href="https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW">SKU ID</a> cannot contain <b>a leading zero</b>. For instance, the system does not read IDs with a <code>01</code>, <code>02</code>, <code>021</code> format because the expected format is <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ To ensure the items added to the inventory will be available for sale on the store, the [SKU ID](https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW) cannot contain **a leading zero**. For instance, the system does not read IDs with a `01`, `02`, `021` format because the expected format is `1`, `2`, `21`.
 
 The total quantity of items on the **Inventory Management** page is updated in real-time, but it may take up to 1 hour to reflect in the [inventory history](https://help.vtex.com/en/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2).
 
@@ -65,9 +61,7 @@ In the **Inventory Management** page, to perform a search, simply type the name
 - **Available:** shows the number of available items in stock. You can enter a value `Greater than or equal to`, `Less than or equal to`, or `Between` two values. If you do not enter a value, `All` items will be displayed.
 - **Warehouse:** select one or more warehouses to see all the items stored in them.
 
-<div class="alert alert-danger">
-The inventory list is limited to ten thousand rows. This means that even if a SKU is not available in the list, it can be found using the filters. The row limit for inventory improves query performance. To access a SKU that is not available on the page, search or use the filters for more accuracy.
-</div>
+>❗ The inventory list is limited to ten thousand rows. This means that even if a SKU is not available in the list, it can be found using the filters. The row limit for inventory improves query performance. To access a SKU that is not available on the page, search or use the filters for more accuracy.
 
 ## Related articles
 
diff --git a/docs/tutorials/en/managing-users.md b/docs/tutorials/en/managing-users.md
index 22f95b393..e9b37c1a2 100644
--- a/docs/tutorials/en/managing-users.md
+++ b/docs/tutorials/en/managing-users.md
@@ -21,9 +21,7 @@ This page displays the list of users with their __Name__, __Email__ and __MFA__
 
 ![Lista Usuários User Management EN](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/a8d2afc57a750d942cfe7e6e2cd98993/Lista_Usu__rios_User_Management_EN.png)
 
-<div class="alert alert-warning">
-Any user that wants to manage users or application keys must have a profile with the <b>Save User</b> <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete">resource</a>. You can use the default profile <a href="https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, for example.
-</div>
+>⚠️ Any user that wants to manage users or application keys must have a profile with the **Save User** [resource](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3?&utm_source=autocomplete). You can use the default profile [User Administrator - RESTRICTED](https://help.vtex.com/en/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted), for example.
 
 ## Creating a new user
 
diff --git a/docs/tutorials/en/managing-warehouses.md b/docs/tutorials/en/managing-warehouses.md
index 413eb0688..6999489ae 100644
--- a/docs/tutorials/en/managing-warehouses.md
+++ b/docs/tutorials/en/managing-warehouses.md
@@ -17,9 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Warehouses are physical storage facilities for the ecommerce business. On the VTEX platform, you can add items to the warehouses you have configured in your store. Then you will be able to track items, their availability and manage their shipping through [loading docks](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) and [shipping policies](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). 
 
-<div class="alert alert-info">
-To better understand how the VTEX platform interprets and defines warehouse operations, check out our article <a href="https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Warehouse</a>.
-</div>
+>ℹ️ To better understand how the VTEX platform interprets and defines warehouse operations, check out our article [Warehouse](https://help.vtex.com/en/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb).
 
 In addition, you can add warehouses, the loading docks where products will be sent to, the processing time for transporting products from a warehouse to a loading dock, and the amount charged for handling them.
 
@@ -30,17 +28,18 @@ This article describes how to:
 * [Edit a warehouse](https://help.vtex.com/en/tutorial/managing-warehouses--tutorials_137#editing-a-warehouse).  
 * [Delete a warehouse](https://help.vtex.com/en/tutorial/managing-warehouses--tutorials_137#editing-a-warehouse).
 
-<div class="alert alert-warning">
-For the logistics system to work as expected, we suggest that you configure it in the following order:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Trade policy;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">Loading dock;</a></li>
-<li>Warehouse.</li>
-</ol>
-</body>
-</div>
+>⚠️ For the logistics system to work as expected, we suggest that you configure it in the following order:
+> <body>
+>
+> [Trade policy;](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. [Shipping policy;](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+>
+> 3. [Loading dock;](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+>
+> Warehouse.
+>
+> </body>
 
 ## Adding a warehouse
 
@@ -82,6 +81,4 @@ For the logistics system to work as expected, we suggest that you configure it i
 3. On the card of the warehouse you want to delete, select <i class="fas fa-ellipsis-v"></i>.
 4. Click on `Delete`.
 
-<div class="alert alert-warning">
-To add items to a warehouse, first, they must be listed in your catalog. Once you have listed them in your <a href="https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catalog</a> and added a warehouse, you must associate items with the warehouse on the <a href="https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139">Inventory management page</a>. 
-</div>
+>⚠️ To add items to a warehouse, first, they must be listed in your catalog. Once you have listed them in your [catalog](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) and added a warehouse, you must associate items with the warehouse on the [Inventory management page](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139).
diff --git a/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md b/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md
index f95b66f20..3a766cb27 100644
--- a/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md
+++ b/docs/tutorials/en/manual-of-classes-and-methods-used-on-webservice.md
@@ -19,6 +19,8 @@ The Web Service interface enables access of storeowners in charge to practically
 
 [Download the manual of classes and methods.](https://assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
 
-<div class="alert alert-danger"><p>Important: only the SOAP methods relevent to the <strong>catalog</strong> are valid.</p>
-<p><strong>All other methods will be deprecated as of 02/28/2017.</strong></p>
-<p>Use the equivalent REST APIs avilable in our <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Important: only the SOAP methods relevent to the **catalog** are valid.
+>
+> **All other methods will be deprecated as of 02/28/2017.**
+>
+> Use the equivalent REST APIs avilable in our [Developer Docs](//help.vtex.com/developer-docs/).
diff --git a/docs/tutorials/en/mapping-categories-and-brands-for-the-marketplace.md b/docs/tutorials/en/mapping-categories-and-brands-for-the-marketplace.md
index 6720ef58e..e813471c5 100644
--- a/docs/tutorials/en/mapping-categories-and-brands-for-the-marketplace.md
+++ b/docs/tutorials/en/mapping-categories-and-brands-for-the-marketplace.md
@@ -52,8 +52,7 @@ To complete the template:
 4. Save the template __XLS file__.  
 5. In *Categories mapping*, upload the updated template using the __Change categories mapping button__.   
 
-<div class="alert alert-info"> 
-If the program you used for opening the template uses semicolons (“;”) as separators, you have to replace them with commas (“,”) before importing the file. </div>
+>ℹ️ If the program you used for opening the template uses semicolons (“;”) as separators, you have to replace them with commas (“,”) before importing the file.
 
 ### Example
 In this example, we downloaded the current template, which has the following values in the columns:
@@ -72,8 +71,7 @@ We will map the seller's categories, trying to find the best possible match with
 | [3] Women \| [28] Jeans                 | Jeans / Shorts            |                                    |
 | [3] Women \| [28] Jeans                 | Jeans / Bermudas          |                                    |
 
-<div class="alert alert-info">
-Note that more than one category in the seller's catalog fell in the same marketplace category (Women / Jeans). In that case, duplicate the row in <b>Marketplace categories</b> and paste the values from <i>Unmapped categories sent by seller</i> into each duplicated row. </div>
+>ℹ️ Note that more than one category in the seller's catalog fell in the same marketplace category (Women / Jeans). In that case, duplicate the row in **Marketplace categories** and paste the values from <i>Unmapped categories sent by seller</i> into each duplicated row.
 
 ## Mapping Brands
 After the seller [sends the products to the marketplace](https://help.vtex.com/en/tutorial/entendendo-a-catalogacao-de-produtos-para-o-marketplace), the marketplace has to map the brands. Matching between marketplace and seller brands is done through a template.  
@@ -93,9 +91,7 @@ You can download the updated template by clicking the Download current mapping t
 4. Save the template __XLS file__.  
 5. In *Brands mapping*, upload the updated template using the __Change categories mapping__ button.   
 
-<div class="alert alert-info">
-If the program you used for opening the template uses semicolons (“;”) as separators, you have to replace them with commas (“,”) before importing the file.
-</div>
+>ℹ️ If the program you used for opening the template uses semicolons (“;”) as separators, you have to replace them with commas (“,”) before importing the file.
 
 ### Example
 In this example, we downloaded the current template, which has the following values in the columns:
diff --git a/docs/tutorials/en/marketplace-invited-sellers.md b/docs/tutorials/en/marketplace-invited-sellers.md
index 4d98066f0..5ac24ed81 100644
--- a/docs/tutorials/en/marketplace-invited-sellers.md
+++ b/docs/tutorials/en/marketplace-invited-sellers.md
@@ -47,10 +47,8 @@ You can invite sellers by sending them a link by email with all the necessary in
 
 The seller will receive an invitation by email to sell on your marketplace. 
 
-<div class="alert alert-info">
-The link sent to the seller by email is valid for seven days. Once the link is opened, the seller has six hours to complete the registration form, without interruption. 
-If the registration cannot be completed within six hours, the marketplace needs to send the invitation again. To resend the invitation, access MARKETPLACE > Invite sellers. Select the seller in the list and click on the  <i class="fas fa-paper-plane"></i> Resend invitation button.
-</div>
+>ℹ️ The link sent to the seller by email is valid for seven days. Once the link is opened, the seller has six hours to complete the registration form, without interruption. 
+> If the registration cannot be completed within six hours, the marketplace needs to send the invitation again. To resend the invitation, access MARKETPLACE > Invite sellers. Select the seller in the list and click on the  <i class="fas fa-paper-plane"></i> Resend invitation button.
 
 ## Connecting sellers
 
diff --git a/docs/tutorials/en/marketplace-strategies-at-vtex.md b/docs/tutorials/en/marketplace-strategies-at-vtex.md
index 86481db6a..48a347047 100644
--- a/docs/tutorials/en/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/en/marketplace-strategies-at-vtex.md
@@ -34,9 +34,7 @@ The product assortment sent to a marketplace is defined when you choose the [tra
 
 [Additional trade policies can be requested](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) via a ticket to our [Support](https://help.vtex.com/pt/support) team by selecting the Commercial option and the New Trade Policy request type. A monthly fee is charged for each additional trade policy, whether used for integration with certified, partner, external, or VTEX marketplaces.  
 
-<div class="alert alert-info">
- Orders placed through marketplaces are subject to the same <a href="https://help.vtex.com/en/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">contractual rules</a> as the ones placed through other channels.  
-</div>  
+>ℹ️ Orders placed through marketplaces are subject to the same [contractual rules](https://help.vtex.com/en/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt) as the ones placed through other channels.  
 
 Here are the scenarios we will address next:  
 
@@ -101,10 +99,8 @@ At VTEX, you can sell on other channels in the following situations:
 - [Integrating with partner marketplaces](#integrating-with-partner-marketplaces)  
 - [Operating as a VTEX seller](#operating-as-a-vtex-seller)  
 
-<div class="alert alert-info">
-  A VTEX store can act simultaneously as a <a href="#selling-on-marketplaces">VTEX seller</a> and a <a href="#operating-as-a-vtex-marketplces">VTEX marketplace</a>.  
-The VTEX platform offers different fulfillment features that can be combined for scenarios such as dropshipping, where the seller receives and forwards the customer's order to a third party responsible for the fulfillment. The most fitting <a href="https://help.vtex.com/en/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP">logistics</a> solution for the seller will depend on the architecture and business model and can be implemented through <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">Back office integration (ERP/PIM/WMS)</a>.
-</div>  
+>ℹ️ A VTEX store can act simultaneously as a [VTEX seller](#selling-on-marketplaces) and a [VTEX marketplace](#operating-as-a-vtex-marketplces).  
+> The VTEX platform offers different fulfillment features that can be combined for scenarios such as dropshipping, where the seller receives and forwards the customer's order to a third party responsible for the fulfillment. The most fitting [logistics](https://help.vtex.com/en/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP) solution for the seller will depend on the architecture and business model and can be implemented through [Back office integration (ERP/PIM/WMS)](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide).  
 
 ### Integrating with an external marketplace
 
@@ -114,9 +110,7 @@ If you want to sell your products on a marketplace not integrated with VTEX, you
 
 Certified marketplaces are those whose integration has been developed by VTEX's engineering team. For these integrations, the additional trade policy is exempt from the monthly fee when orders are linked to the policy via the certified marketplace. Instead, fees will be based solely on the take rate of the orders.  
 
-<div class="alert alert-warning">
-Additional trade policies requested for integrating with certified marketplaces that are also used for integrating with other marketplace types are subject to a monthly fee.
-</div>  
+>⚠️ Additional trade policies requested for integrating with certified marketplaces that are also used for integrating with other marketplace types are subject to a monthly fee.  
 
 Currently, on the VTEX platform, you can find the following certified marketplaces:  
 
@@ -168,9 +162,7 @@ Below, you will find the partner marketplaces available in the VTEX catalog:
 - Fast Shop  
 - Hubplus  
 
-<div class="alert alert-info">
-Facebook, Google Shopping, Google Shopping Ads, and TikTok are not marketplaces, but they offer a similar experience of sending products from VTEX stores.
-</div>  
+>ℹ️ Facebook, Google Shopping, Google Shopping Ads, and TikTok are not marketplaces, but they offer a similar experience of sending products from VTEX stores.  
 
 ### Operating as a VTEX seller  
 
@@ -182,6 +174,4 @@ Setting up an [integration between VTEX stores](https://help.vtex.com/en/tutoria
 
 The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) is a VTEX platform edition for sellers to connect and sell their products on VTEX marketplaces. The portal allows sellers to access all the key features necessary to operate ecommerce on big storefronts, increasing visibility and sales conversion.  
 
-<div class="alert alert-info">
-At VTEX, it is possible to act as a <a href="https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label seller</a>, a seller unknown to the consumer in his shopping experience. This type of seller is the standard for <a href="https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">franchise accounts</a>, for example, and can be strategic for certain business models. To learn more, see the article <a href="https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Choosing between standard account, franchise account, or Seller Portal</a>.
-</div>
+>ℹ️ At VTEX, it is possible to act as a [white label seller](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), a seller unknown to the consumer in his shopping experience. This type of seller is the standard for [franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), for example, and can be strategic for certain business models. To learn more, see the article [Choosing between standard account, franchise account, or Seller Portal](https://help.vtex.com/en/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).
diff --git a/docs/tutorials/en/marketplaces-and-integrations.md b/docs/tutorials/en/marketplaces-and-integrations.md
index 49c8919e0..18679d2d4 100644
--- a/docs/tutorials/en/marketplaces-and-integrations.md
+++ b/docs/tutorials/en/marketplaces-and-integrations.md
@@ -24,10 +24,8 @@ Among the marketplaces available, there are VTEX marketplaces and external marke
 | **VTEX** | These are the profiles of VTEX clients that chose to make their environment available for sellers to sell products. |
 | **External** | Marketplaces that are not VTEX clients and did the integration, whether certified or partner. |  
 
-<div class="alert alert-info">
-Note that <b>Marketplaces and Integrations</b> is a tool that fosters contact between potential partners, yet it is not a mandatory step in becoming a VTEX marketplace.  
-If you want to act as a VTEX marketplace, read the <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex">Marketplace strategies at VTEX</a>.  
-</div>
+>ℹ️ Note that **Marketplaces and Integrations** is a tool that fosters contact between potential partners, yet it is not a mandatory step in becoming a VTEX marketplace.  
+> If you want to act as a VTEX marketplace, read the [Marketplace strategies at VTEX](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex).
 
 ## Looking for marketplaces  
 
diff --git a/docs/tutorials/en/master-data-v2.md b/docs/tutorials/en/master-data-v2.md
index 27713b9cb..13c738a6d 100644
--- a/docs/tutorials/en/master-data-v2.md
+++ b/docs/tutorials/en/master-data-v2.md
@@ -15,8 +15,7 @@ legacySlug: master-data-v2
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">
-<strong>Attention:</strong> This version isn't compliant with data entities of old version. It's possible to use this configuration only to new data entities.</div>
+>⚠️ **Attention:** This version isn't compliant with data entities of old version. It's possible to use this configuration only to new data entities.
 
 ## Introduction
 
diff --git a/docs/tutorials/en/master-data.md b/docs/tutorials/en/master-data.md
index 2a65a2f62..d4df71a3e 100644
--- a/docs/tutorials/en/master-data.md
+++ b/docs/tutorials/en/master-data.md
@@ -21,9 +21,7 @@ By default, Master Data is used to store and organize Customer data from your st
 
 In this article you will learn more about each available version of the Master Data, important concepts, and how to use it.
 
-<div class="alert alert-info">
-Note that depending on the functionality and version you wish to use, it is necessary to contact your development team.
-</div>
+>ℹ️ Note that depending on the functionality and version you wish to use, it is necessary to contact your development team.
 
 ## Versions available
 
@@ -224,9 +222,7 @@ Check the table below to learn more about the different functionalities of each
    </tbody>
 </table></div>
 
-<div class="alert alert-danger">
-Note that the data entities of the two versions are independent, even if some may be analogous. This means that a data created in a v1 entity cannot be queried or edited using v2 resources and vice versa.
-</div>
+>❗ Note that the data entities of the two versions are independent, even if some may be analogous. This means that a data created in a v1 entity cannot be queried or edited using v2 resources and vice versa.
 
 ## Basic components
 
diff --git a/docs/tutorials/en/match-offers-mercado-livre.md b/docs/tutorials/en/match-offers-mercado-livre.md
index e2a1627c7..84f3967bd 100644
--- a/docs/tutorials/en/match-offers-mercado-livre.md
+++ b/docs/tutorials/en/match-offers-mercado-livre.md
@@ -15,6 +15,4 @@ legacySlug: match-offers-mercado-livre
 subcategory: 
 ---
 
-<div class="alert alert-warning">
-This is a regional exclusive content not applicable to English speaking countries.
-  </div> 
+>⚠️ This is a regional exclusive content not applicable to English speaking countries. 
diff --git a/docs/tutorials/en/maximum-price-per-item.md b/docs/tutorials/en/maximum-price-per-item.md
index 49cd9e38e..637025a3d 100644
--- a/docs/tutorials/en/maximum-price-per-item.md
+++ b/docs/tutorials/en/maximum-price-per-item.md
@@ -21,9 +21,7 @@ You can create up to __10 promotions__ of this type, with a __limit of 100 SKUs_
 
 As it's a benefit, the prices registered at maximum prices can not be higher than the product's price.
 
-<div class="alert alert-warning">
-<strong>Attention:</strong> In order for the Maximum price per item to work, you must <strong>choose a payment method</strong>.
-</div>
+>⚠️ **Attention:** In order for the Maximum price per item to work, you must **choose a payment method**.
 
 ## General promotion data
 
@@ -42,9 +40,7 @@ As it's a benefit, the prices registered at maximum prices can not be higher tha
 - __Price:__ Set here the maximum price at which the product will be sold. You can only set the maximum price for one item at a time. To add products to the promotion, click the __+__ button.
 - __Payment system__: Select the payment methods that should activate the promotion.
 
-<div class="alert alert-info">
-You can import a list of SKUs, which must be saved in an .xls file, with each ID on a different line, followed by the corresponding maximum price. To see a template, click the <strong>Example spreadsheet download</strong> link.
-</div>
+>ℹ️ You can import a list of SKUs, which must be saved in an .xls file, with each ID on a different line, followed by the corresponding maximum price. To see a template, click the **Example spreadsheet download** link.
 
 ## Conditions for the promotion to be valid
 
diff --git a/docs/tutorials/en/media-overview.md b/docs/tutorials/en/media-overview.md
index b1c312aad..aedc5d17e 100644
--- a/docs/tutorials/en/media-overview.md
+++ b/docs/tutorials/en/media-overview.md
@@ -17,9 +17,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 
 Media is a feature responsible for managing your store's media files, such as images and videos. For images, you can upload and organize files up to 5 MB in the following formats: `png`, `jpg`, `gif`, `svg` and `webp`. For videos, you can add a URL to the externally hosted video provider, e.g. YouTube or Vimeo.
 
-<div class="alert alert-warning">
-  For upload, files must have a lowercase extension (e.g., <code>store.png</code>) and be up to <b>5 MB</b>.
-</div>
+>⚠️ For upload, files must have a lowercase extension (e.g., `store.png`) and be up to **5 MB**.
 
 ![Media Overview](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4151c07cdf6675310b41607256633894/en-media-overview.png)
 
@@ -39,9 +37,7 @@ There are three ways to access Media:
 
 - **Headless CMS**: In the VTEX Admin, go to **Storefront > Headless CMS**. Choose one of the created pages, such as a product page. From the available sections, select one to which you can add an image, e.g. , [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero), and click the Hero image component. A Media panel will open.
 
-<div class="alert alert-warning">
-Note that the section must use the <a href="https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms">media-gallery</a> to leverage Media. For <a href="https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore">FastStore</a> projects, the sections that use the <i>media-gallery</i> widget are <a href="https://developers.vtex.com/docs/guides/faststore/organisms-navbar">Navbar</a> and <a href="https://developers.vtex.com/docs/guides/faststore/organisms-hero">Hero</a>.
-</div>
+>⚠️ Note that the section must use the [media-gallery](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms) to leverage Media. For [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore) projects, the sections that use the <i>media-gallery</i> widget are [Navbar](https://developers.vtex.com/docs/guides/faststore/organisms-navbar) and [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero).
 
 In the following image, you can see an overview of the Media interface and the actions available for managing your media files:
 
@@ -63,15 +59,11 @@ In Media, you can upload images, and the feature supports the following formats:
 
 1. On the **Media** page or panel, click `Add New` and click `Image`.
 
-<div class="alert alert-warning">
-  <p>In the Media panel available in the Headless CMS and Site Editor, you can drag and drop images.</p>
-</div>
+>⚠️ In the Media panel available in the Headless CMS and Site Editor, you can drag and drop images.
 
 2. Choose the image you want to upload and click `Open`.
 
-<div class="alert alert-warning">
- Please note that Media accepts the following formats: <code>png</code>, <code>jpg</code>, <code>gif</code>, <code>svg</code>, and <code>webp</code>, in lowercase and with a file size limit of 5 MB.
-</div>
+>⚠️ Please note that Media accepts the following formats: `png`, `jpg`, `gif`, `svg`, and `webp`, in lowercase and with a file size limit of 5 MB.
 
 3. After the image is loaded, a success message will be displayed.
 
@@ -84,9 +76,7 @@ Now, you can perform other actions by clicking `More actions` (three vertical do
 | **Download** | Downloads the image to your computer. |
 | **Delete** |	Deletes the image from the repository. |
 
-<div class="alert alert-warning">
-Deleting the image will only remove it from the Media repository. If you have added the image to a Hero component, for example, the image will continue to be used in that component. However, you will not be able to use it in other components.
-</div>
+>⚠️ Deleting the image will only remove it from the Media repository. If you have added the image to a Hero component, for example, the image will continue to be used in that component. However, you will not be able to use it in other components.
 
 ### Adding videos
 Besides images, in Media, you can also store videos and then use them in your store to create visual appeal for users navigating the store.
diff --git a/docs/tutorials/en/mercado-libre-size-chart.md b/docs/tutorials/en/mercado-libre-size-chart.md
index 4bbfe5513..4a5a8bb12 100644
--- a/docs/tutorials/en/mercado-libre-size-chart.md
+++ b/docs/tutorials/en/mercado-libre-size-chart.md
@@ -15,6 +15,4 @@ legacySlug: mercado-libre-size-chart
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning">
-  This is a regional exclusive content not applicable to English speaking countries.
-  </div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tutorials/en/merchandising-rule-conditions.md b/docs/tutorials/en/merchandising-rule-conditions.md
index 7e1e385c4..810920f72 100644
--- a/docs/tutorials/en/merchandising-rule-conditions.md
+++ b/docs/tutorials/en/merchandising-rule-conditions.md
@@ -23,9 +23,7 @@ Learn about the criteria and possible operators for each type of editing in the
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"> <thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Name</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Description</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operators</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Types of editing</th> </tr> </thead> <tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Term</span></td> <td rowspan="2" class="t-body pa5">Word searched by the customer that will be related to the rule. Open input field.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td rowspan="2" class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br>Customization rules </td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contains</span></td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Searches for the exact ID of a catalog element related to the rule. Possible IDs are: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong>, and <strong>EAN</strong>. Open input field.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Customization rules</td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">category</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a category added to the store's catalog. </td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">department</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a department added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">brand</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a brand added to the store's catalog. </td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">productclusternames</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a collection added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promotion</span></td> <td rowspan="2" class="t-body pa5">Selectable value that validates if there is at least one promotion linked to the item (<span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">yes</span>).</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sellername</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents the name of a seller.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategory</span></td> <td rowspan="2" class="t-body pa5">Selectable value that represents a subcategory added to the store's catalog.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> <tr> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{specification}}</span></td> <td rowspan="2" class="t-body pa5">Any active catalog specification appears as a custom criterion, with the same possible values. The name of the criterion is exactly the name of the added specification. For example, if there is an active specification called <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>, the displayed criterion is <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">is</span></td> <td class="t-body pa5">All editing scenarios</td> </tr> <tr> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">only</span></td> <td class="t-body pa5"><strong>Manual Editor:</strong><br>Trigger rules<br> <br><strong>Visual Editor</strong></td> </tr> </tbody></table>
 
-<div class="alert alert-warning">
-  <p>The <code>department</code>, <code>category</code>, and <code>subcategory</code> criteria only appear as options to be included in Merchandising Rules if all three category levels are previously configured in the <strong>Catalog</strong>.</p>
-</div>
+>⚠️ The `department`, `category`, and `subcategory` criteria only appear as options to be included in Merchandising Rules if all three category levels are previously configured in the **Catalog**.
 
 ## Operators
 
diff --git a/docs/tutorials/en/meta-tags-suiteshare.md b/docs/tutorials/en/meta-tags-suiteshare.md
index 91e91a330..a81aadb02 100644
--- a/docs/tutorials/en/meta-tags-suiteshare.md
+++ b/docs/tutorials/en/meta-tags-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: meta-tags-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/migrating-to-the-new-version-of-smart-checkout.md b/docs/tutorials/en/migrating-to-the-new-version-of-smart-checkout.md
index dbbb20e2e..1328a781a 100644
--- a/docs/tutorials/en/migrating-to-the-new-version-of-smart-checkout.md
+++ b/docs/tutorials/en/migrating-to-the-new-version-of-smart-checkout.md
@@ -53,9 +53,7 @@ You can use the files `checkout5-custom.js` and `orderplaced2-custom.js` in o
 4. In the __Files__ menu, located on the right side of the page, click on the ones you want to make adjustments to the code.
 5. Click the `Save` button.
 
-<div class="alert alert-warning">
-  Customizing JavaScript files can damage your Checkout. VTEX <b>does not recommend</b> customizations and doesn't take responsibility for any damage caused by this code.
-</div>
+>⚠️ Customizing JavaScript files can damage your Checkout. VTEX **does not recommend** customizations and doesn't take responsibility for any damage caused by this code.
 
 __IMPORTANT:__ Do not use these files to insert marketing and integration tags. In case you need them, do so through Google Tag Manager.
 
diff --git a/docs/tutorials/en/mode-off-faq.md b/docs/tutorials/en/mode-off-faq.md
index b7cf3abb2..364dd5c1d 100644
--- a/docs/tutorials/en/mode-off-faq.md
+++ b/docs/tutorials/en/mode-off-faq.md
@@ -41,9 +41,7 @@ No, these payment methods require an online response and cannot be processed asy
 
 The mode-off feature is activated if the partner or integration presents any instability identified through error messages, such as 500 and 408, or a timeout longer than 30 seconds over the last five minutes. This rule applies to all payment methods processed in mode-off.
 
-<div class="alert alert-warning">
-Please remember that synchronous payment methods <strong>cannot</strong> be reprocessed. However, they count as errors for identifying whether a partner is stable.
-</div>  
+>⚠️ Please remember that synchronous payment methods **cannot** be reprocessed. However, they count as errors for identifying whether a partner is stable.  
 
 ## What is the rule to deactivate the mode-off?
 
@@ -53,8 +51,7 @@ Transactions shall be resumed when the partner stops experiencing a rate of five
 
 The time between transaction processing reattempts (_retries_) can be defined by the partner when sending payment information. When configuring the payment cancellation time (`delayToCancel` field) for a period of less than 1 day, retry attempts will be made every 1 hour. If the time to cancel the payment is set to be equal to or greater than 1 day, retry attempts will be made every 4 hours. For more information, visit [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol?endpoint=post-/payments).
 
-<div class="alert alert-info">
- If payment is made by <a href="https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf">PIX (Brazilian instant payment method)</a> or the payment cancellation time is set between 5 minutes and 1 hour, retry calls will occur every 5 minutes.</div>
+>ℹ️ If payment is made by [PIX (Brazilian instant payment method)](https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf) or the payment cancellation time is set between 5 minutes and 1 hour, retry calls will occur every 5 minutes.
 
 ## How to identify the mode-off? What to do if it is active?
 
diff --git a/docs/tutorials/en/moskit-suiteshare.md b/docs/tutorials/en/moskit-suiteshare.md
index faecdfb96..1b5269fc5 100644
--- a/docs/tutorials/en/moskit-suiteshare.md
+++ b/docs/tutorials/en/moskit-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: moskit-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/moving-order-to-start-handling-shipping.md b/docs/tutorials/en/moving-order-to-start-handling-shipping.md
index 7e51f2d4d..cad2e97f5 100644
--- a/docs/tutorials/en/moving-order-to-start-handling-shipping.md
+++ b/docs/tutorials/en/moving-order-to-start-handling-shipping.md
@@ -40,6 +40,4 @@ If the store doesn't have an ERP or some system that integrates the orders, it's
     - <a class="far fa-check-square"></a> I understand the consequences of this action in the order flow.
 5. Click `Proceed with status`.
 
-<div class="alert alert-warning">
-When you manually start an order handling, the order can not be integrated with the ERP later on.
-</div>
+>⚠️ When you manually start an order handling, the order can not be integrated with the ERP later on.
diff --git a/docs/tutorials/en/multilevel-omnichannel-inventory.md b/docs/tutorials/en/multilevel-omnichannel-inventory.md
index 25a89a2f2..20945bd2d 100644
--- a/docs/tutorials/en/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/en/multilevel-omnichannel-inventory.md
@@ -22,9 +22,7 @@ __Multilevel Omnichannel Inventory__ is the configuration on the VTEX platform t
 * [Restrictions](#restrictions)  
 * [How to configure it](#how-to-configure-it)  
 
-<div class="alert alert-info">
-Read our <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory">Developer Portal</a> article to learn more about the Multilevel Omnichannel Inventory order architecture and how to configure it via REST API. 
-</div>
+>ℹ️ Read our [Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory) article to learn more about the Multilevel Omnichannel Inventory order architecture and how to configure it via REST API.
 
 ## Account Architecture
 
@@ -48,9 +46,7 @@ Therefore, a marketplace can sell the products from its direct sellers and the p
 
 It means that when the main account seller configures an integration with a marketplace, the franchise accounts are also automatically integrated. There is no need to manage each franchise individually to configure its integration with the marketplace.
 
-<div class="alert alert-info">
-Currently, only one level of recursion is allowed. Thus, the marketplace can sell products from white-label sellers integrated with a direct seller.
-</div>
+>ℹ️ Currently, only one level of recursion is allowed. Thus, the marketplace can sell products from white-label sellers integrated with a direct seller.
 
 ## Benefits
 
@@ -87,9 +83,7 @@ Note that when direct sellers are not responsible for white-label sellers’ pay
 
 Once the configuration is done, only marketplace payment methods will be displayed as an option at checkout. Payment methods from direct sellers (level 2) and white-label sellers (level 3) are not imported to the account architecture. Therefore, the checkout only displays the marketplace's payment methods, even if the direct seller's affiliate is configured to use their payment methods.  
 
-<div class="alert alert-warning">
-The franchise account <a href="https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187">affiliate</a> must always have the setting for using payment methods disabled.
-</div>
+>⚠️ The franchise account [affiliate](https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187) must always have the setting for using payment methods disabled.
 
 ### Changing sellers
 
@@ -135,9 +129,7 @@ You can't create price tables using the [Price Table](https://help.vtex.com/en/t
 
 The marketplace must configure the __Multilevel Omnichannel Inventory__ in the VTEX Admin or via the [Rest API](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). This configuration can be done for integrated sellers and newly integrated ones. 
 
-<div class="alert alert-info">
-Note that the marketplace must configure the Multilevel Ominichannel Inventory for each direct seller (level 2) to which they want to apply the feature, but not for each white-label seller or franchise account (level 3).
-</div>
+>ℹ️ Note that the marketplace must configure the Multilevel Ominichannel Inventory for each direct seller (level 2) to which they want to apply the feature, but not for each white-label seller or franchise account (level 3).
 
 ### Integrated sellers
 
diff --git a/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md b/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md
index f187f4e66..c913d24a4 100644
--- a/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md
+++ b/docs/tutorials/en/my-orders-in-mercado-libre-have-errors.md
@@ -15,6 +15,4 @@ legacySlug: my-orders-in-mercado-libre-have-errors
 subcategory: 2LcLWCYaEm5qPmOuYUiKIS
 ---
 
-<div class="alert alert-warning">
-  This is a regional exclusive content not applicable to English speaking countries.
-  </div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tutorials/en/my-store-order-was-not-created.md b/docs/tutorials/en/my-store-order-was-not-created.md
index ad151e24e..23a7ab959 100644
--- a/docs/tutorials/en/my-store-order-was-not-created.md
+++ b/docs/tutorials/en/my-store-order-was-not-created.md
@@ -58,7 +58,5 @@ An error with product missing information can happen when the product has no inv
 3. In the `Edit XML` tab, for the option **Show unavailable SKUs**, select the checkbox `Show out-of-stock (sold-out) SKUs in the results`.
 4. Click `Save`.
 
-<div class="alert alert-warning">
-You can have invoicing errors when trying to invoice an order with incorrect or missing XML information.
-</div>
+>⚠️ You can have invoicing errors when trying to invoice an order with incorrect or missing XML information.
 
diff --git a/docs/tutorials/en/navigation.md b/docs/tutorials/en/navigation.md
index 883e5fa17..5c7e4c5e1 100644
--- a/docs/tutorials/en/navigation.md
+++ b/docs/tutorials/en/navigation.md
@@ -18,9 +18,7 @@ subcategory: oMrzcOMVbBpH0reeMFHFg
 The navigation dataset operates with two main tables: `pageviews` and `sessions`. A `pageview` refers to each new page that a user accesses while browsing a store, while a `session` is the set of all pageviews made by a user in a single visit.
 Each `session` remains active until no new `pageviews` occur for a period of 30 minutes.
 
-<div class="alert alert-warning">
-The navigation dataset does not capture all types of events that occur during browsing. For example, specific clicks, special events, and interactions with the mini cart are not recorded.
-  </div>
+>⚠️ The navigation dataset does not capture all types of events that occur during browsing. For example, specific clicks, special events, and interactions with the mini cart are not recorded.
 
 This section includes the following information:
 
@@ -39,10 +37,8 @@ This section includes the following information:
 | History | The data is retained for two years, starting 2022 for clients who already use the VTEX platform. |
 | Minimum update interval | One hour. |
 
-<div class="alert alert-warning">
-  Data Pipeline only provides data from sessions originating from VTEX storefront solutions: Legacy CMS, Store Framework, and FastStore. VTEX does not have access to sessions originating from third-party marketplaces or proprietary storefronts. Furthermore, storefront customizations   may interfere with or even disable the script, resulting in some sessions not being recorded, or in discrepancies in the conversion rate observed in the dashboard.
-To minimize the impact on store performance, the script is configured to be the last element to load on the page. This means that very brief sessions may not be captured.
-</div>
+>⚠️ Data Pipeline only provides data from sessions originating from VTEX storefront solutions: Legacy CMS, Store Framework, and FastStore. VTEX does not have access to sessions originating from third-party marketplaces or proprietary storefronts. Furthermore, storefront customizations   may interfere with or even disable the script, resulting in some sessions not being recorded, or in discrepancies in the conversion rate observed in the dashboard.
+> To minimize the impact on store performance, the script is configured to be the last element to load on the page. This means that very brief sessions may not be captured.
 
 ## Table: sessions
 
diff --git a/docs/tutorials/en/new-google-shopping-api-integration.md b/docs/tutorials/en/new-google-shopping-api-integration.md
index 787651c05..731413ca9 100644
--- a/docs/tutorials/en/new-google-shopping-api-integration.md
+++ b/docs/tutorials/en/new-google-shopping-api-integration.md
@@ -80,8 +80,6 @@ Google automatically gives products a 30 day expiration date unless updates are
 #### Title size
 The limit is 150 characters, however Google annoucements only display 70 characters. The integration sends up to 150 characters, made up of the Product Title + SKU Title; [read more about this here](https://support.google.com/merchants/answer/6098378?hl=en).
 
-<div class="alert alert-warning">
-<strong>Attention:</strong> The XML integration has not been discontinued, but if the integration is done by XML and the Integrations module (API) the products will appear duplicated.
-</div>
+>⚠️ **Attention:** The XML integration has not been discontinued, but if the integration is done by XML and the Integrations module (API) the products will appear duplicated.
 
 
diff --git a/docs/tutorials/en/new-my-orders-area.md b/docs/tutorials/en/new-my-orders-area.md
index 6fc6d173a..34da56580 100644
--- a/docs/tutorials/en/new-my-orders-area.md
+++ b/docs/tutorials/en/new-my-orders-area.md
@@ -15,12 +15,14 @@ legacySlug: new-my-orders-area
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-warning">
-This update is a <em>major</em> and <strong>not compatible with the customizations of the current My Orders section</strong>. 
-<br />
-<br />
-Because the new page structure is completely different, it will be necessary to remake the customizations to migrate to this version. See details on how to update your customization in <a href="http://help.vtex.com/pt/tutorial/customizando-a-secao-meus-pedidos">Customizando a Seção Meus Pedidos</a>.
-</div>
+>⚠️ This update is a *major* and **not compatible with the customizations of the current My Orders section**. 
+>
+>
+> 
+>
+>
+> 
+> Because the new page structure is completely different, it will be necessary to remake the customizations to migrate to this version. See details on how to update your customization in [Customizando a Seção Meus Pedidos](http://help.vtex.com/pt/tutorial/customizando-a-secao-meus-pedidos).
 
 VTEX is always looking to use a modern stack to create products that deliver more value to the ecosystem. For this reason, we started using the React JS library in our most recent systems and features: the new **My Orders** feature is one example. The newest version comes with new features and design, and was created from scratch using React.
 
diff --git a/docs/tutorials/en/offer-details.md b/docs/tutorials/en/offer-details.md
index 181e56f8b..fed484e45 100644
--- a/docs/tutorials/en/offer-details.md
+++ b/docs/tutorials/en/offer-details.md
@@ -15,11 +15,9 @@ legacySlug: offer-details
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class="alert alert-info">
-To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
-For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
-</div>  
+>ℹ️ To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module **Offer Management**. As a result, the module will not receive new updates or maintenance.
+> For connectors and marketplaces already integrated into the module, please contact the development team by email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the [Developer Portal's release notes section](https://developers.vtex.com/updates/release-notes) and [VTEX Help Center announcements page](https://help.vtex.com/pt/en/announcements).  
 
 An offer is an SKU from a seller that has been sent to different sales channels and whose price and inventory have been configured. The [Offer Management](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) module allows sellers to supervise the sending of their offers to marketplaces and see their sync status.
 
diff --git a/docs/tutorials/en/offer-management.md b/docs/tutorials/en/offer-management.md
index 916d69e88..722b957fc 100644
--- a/docs/tutorials/en/offer-management.md
+++ b/docs/tutorials/en/offer-management.md
@@ -15,11 +15,9 @@ legacySlug: offers-listing
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class="alert alert-info">
-To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
-For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
-</div>  
+>ℹ️ To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module **Offer Management**. As a result, the module will not receive new updates or maintenance.
+> For connectors and marketplaces already integrated into the module, please contact the development team by email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the [Developer Portal's release notes section](https://developers.vtex.com/updates/release-notes) and [VTEX Help Center announcements page](https://help.vtex.com/pt/en/announcements).  
 
 The **Offer Management** module allows sellers to track the sending and syncing of their offers on all sales channels integrated with the store. On the VTEX platform, an offer is a SKU from a seller that has been sent to a sales channel and whose price and inventory information have been configured.
 
diff --git a/docs/tutorials/en/offer-quality-filters.md b/docs/tutorials/en/offer-quality-filters.md
index f12ef8eb2..b1892979f 100644
--- a/docs/tutorials/en/offer-quality-filters.md
+++ b/docs/tutorials/en/offer-quality-filters.md
@@ -59,9 +59,7 @@ To view the rules that are already active by default, on the Offer quality filte
 - Ref ID has a maximum character limit of 50. 
 - EAN has a maximum character limit of 50. 
 
-<div class="alert alert-info">
-You can configure VTEX Matcher's auto-approval of offers via <a href="https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig">Save Account's Approval Settings</a> REST API calls. These are different criteria than the ones available on the Offer Quality filters page and apply to the automatic approval of offers from specific sellers.
-</div>
+>ℹ️ You can configure VTEX Matcher's auto-approval of offers via [Save Account's Approval Settings](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig) REST API calls. These are different criteria than the ones available on the Offer Quality filters page and apply to the automatic approval of offers from specific sellers.
 
 ## Creating requirement groups
 
@@ -83,9 +81,7 @@ Create requirement groups to set rules that apply to sellers, categories, or mar
 
 You can create mandatory and/or optional requirements. Learn more about the implications of each requirement in [Cataloging offers with requirements](#cataloging-offers-with-requirements).
 
-<div class="alert alert-info">
-Notice that each requirement group holds only one value. Therefore, you need to create another requirement group to add more than one value. For example, if the marketplace wants to add the words "Shirts" and "T-shirts" as mandatory requirements for the Seller brand field, you need to create a requirement group for "Shirts" and another one for "T-shirts".
-</div>
+>ℹ️ Notice that each requirement group holds only one value. Therefore, you need to create another requirement group to add more than one value. For example, if the marketplace wants to add the words "Shirts" and "T-shirts" as mandatory requirements for the Seller brand field, you need to create a requirement group for "Shirts" and another one for "T-shirts".
 
 Follow the steps below to create a new requirement group:
 
diff --git a/docs/tutorials/en/offer-status.md b/docs/tutorials/en/offer-status.md
index ec41fc8d4..35002986b 100644
--- a/docs/tutorials/en/offer-status.md
+++ b/docs/tutorials/en/offer-status.md
@@ -108,9 +108,7 @@ You will be redirected to the corresponding page to make the necessary changes.
 
 To export the published offer list in XLSX format, click the down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
 
-<div class="alert alert-info">
-  The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
-  </div>
+>ℹ️ The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
 
 ## Issues tab
 
@@ -181,9 +179,7 @@ You will be redirected to the corresponding page to make the necessary changes.
 
 To export the issues offer list in XLSX format, click the down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
 
-<div class="alert alert-info">
-  The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
-  </div>
+>ℹ️ The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
 
 ## Awaiting Completion tab
 
@@ -236,6 +232,4 @@ You will be redirected to the corresponding page to make the necessary changes.
 
 To export the awaiting offer list in XLSX format, click the down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
 
-<div class="alert alert-info">
-  The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
-  </div>
+>ℹ️ The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
diff --git a/docs/tutorials/en/opening-hours-suiteshare.md b/docs/tutorials/en/opening-hours-suiteshare.md
index d08c6532c..7529ee532 100644
--- a/docs/tutorials/en/opening-hours-suiteshare.md
+++ b/docs/tutorials/en/opening-hours-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: opening-hours-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/operational-capacity-beta.md b/docs/tutorials/en/operational-capacity-beta.md
index 48013a078..0c81c2432 100644
--- a/docs/tutorials/en/operational-capacity-beta.md
+++ b/docs/tutorials/en/operational-capacity-beta.md
@@ -31,9 +31,7 @@ When you go to the VTEX Admin under **Shipping > Operational Capacity**, you wil
 
 ![operational_capacity_image1_EN](https://images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/87f03e4f1a667a76349095e450244602/operational_capacity_image1_EN.png)
 
-<div class="alert alert-warning">
-The sellers displayed on the interface are your operation's sellers, previously configured by our team. To add a new seller, contact <a href="https://help.vtex.com/en/support">our Support</a> team.
-</div>
+>⚠️ The sellers displayed on the interface are your operation's sellers, previously configured by our team. To add a new seller, contact [our Support](https://help.vtex.com/en/support) team.
 
 The chart shows the following data:
 
@@ -99,9 +97,7 @@ The seller's operational capacity considers the number of orders or order items.
     - **Number of items:** The seller's operational capacity will be based on the number of items in an order.
 5. Click `Save Changes`.
 
-<div class="alert alert-warning">
-The platform has some restrictions regarding <a href="https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">comprehensive sellers</a>. Learn more in the <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#comprehensive-seller-operational-capacity">Comprehensive seller operational capacity</a> section.
-</div>
+>⚠️ The platform has some restrictions regarding [comprehensive sellers](https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI). Learn more in the [Comprehensive seller operational capacity](https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#comprehensive-seller-operational-capacity) section.
 
 ## Actions on the seller details page
 
@@ -119,9 +115,7 @@ At the top right of the seller's details page, you'll find a toggle switch to ac
 - **Activate:** Enable the toggle switch for `Active` and click `Activate`.
 - **Pause:** Toggle the switch for `Paused` and click `Pause`.
 
-<div class="alert alert-warning">
-The platform has some restrictions regarding <a href="https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">comprehensive sellers</a>. Learn more in the <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#comprehensive-seller-operational-capacity">Comprehensive seller operational capacity</a> section.
-</div>
+>⚠️ The platform has some restrictions regarding [comprehensive sellers](https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI). Learn more in the [Comprehensive seller operational capacity](https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#comprehensive-seller-operational-capacity) section.
 
 ### Monitoring capacity usage
 
diff --git a/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
index 191e26055..0c4e04b87 100644
--- a/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/en/optimization-of-shipping-options-at-checkout.md
@@ -34,17 +34,13 @@ VTEX's Checkout v6 combines information such as the customer's zip code, product
 - **Cheapest**: option with the lowest cost to the customer.
 - **Fastest**: option with the shortest shipping time.
 
-<div class="alert alert-warning">
-When only one type of shipping option is available for a given order, the <b>Cheapest</b> and <b>Fastest</b> options will not be shown at Checkout.
-</div>
+>⚠️ When only one type of shipping option is available for a given order, the **Cheapest** and **Fastest** options will not be shown at Checkout.
 
 ## Disable the Optimized Shipping Options function
 
 The **Optimized Shipping Options** functionality is enabled by default in Checkout v6. However, in some regions, there may be scenarios that contribute to this function not being used. In countries such as Spain or the United States, where the available shipping options are similar, consumers prefer to choose a carrier based on their level of trust in the company.
 
-<div class="alert alert-warning">
-By disabling this function in Admin VTEX, all available shipping options will be displayed in the Checkout process. However, if the <a href="https://help.vtex.com/en/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#">Multiple Deliveries</a> functionality is enabled in the store and there are different delivery options between the selected items in the cart, the <b>Optimized Delivery Options</b> will continue to be displayed. That is, delivery optimization will be needed to handle multiple packages (items with different delivery options).
-</div>
+>⚠️ By disabling this function in Admin VTEX, all available shipping options will be displayed in the Checkout process. However, if the [Multiple Deliveries](https://help.vtex.com/en/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#) functionality is enabled in the store and there are different delivery options between the selected items in the cart, the **Optimized Delivery Options** will continue to be displayed. That is, delivery optimization will be needed to handle multiple packages (items with different delivery options).
 
 To disable the __Optimized Shipping Options__ function, follow the steps below:
 
diff --git a/docs/tutorials/en/order-allocation-algorithm-beta.md b/docs/tutorials/en/order-allocation-algorithm-beta.md
index b0319a1ef..2b34fa44e 100644
--- a/docs/tutorials/en/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/en/order-allocation-algorithm-beta.md
@@ -15,9 +15,7 @@ legacySlug: order-allocation-algorithm-beta
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-<p>This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.
 
 **Order Allocation Algorithm** is the VTEX platform algorithm that aims to select the seller that will ship orders at the lowest cost given by their configured [carrier's shipping rate templates](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE).
 
diff --git a/docs/tutorials/en/order-cancellation-requested-by-the-customer.md b/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
index 0958c324f..b11f1506b 100644
--- a/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Customers may request to cancel their order for various reasons. They can [cancel an order automatically](https://help.vtex.com/en/tutorial/order-cancellation-requested-by-the-customer--3wEI6DUNtecooG2Ki4Akqo#cancellation-within-the-grace-period) within the **grace period for cancellation**, or after that period upon the [retailer cancellation approval](https://help.vtex.com/en/tutorial/order-cancellation-requested-by-the-customer--3wEI6DUNtecooG2Ki4Akqo#cancellation-approved-by-the-retailer). 
 
-<div class="alert alert-danger">
-Once an order is canceled, it is no longer possible to change its status.
-</div>
+>❗ Once an order is canceled, it is no longer possible to change its status.
 
 <div class = "alert alert-warning">
 Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
@@ -46,9 +44,7 @@ The retailer must approve or reject the cancellation request. If the retailer do
 
 Even if the retailer uses the [VTEX DO](https://help.vtex.com/en/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu) to deny the cancellation requested by the customer, the retailer must proceed with the order's [billing](https://help.vtex.com/en/tutorial/faturar-um-pedido--7p1h852V5t54KyscpgxE2v), which is what makes the order follow its flow.
 
-<div class="alert alert-warning">
-If the <a href="https://help.vtex.com/en/tutorial/order-replacement--2IK9mwQjBKseQmE8K8saO8#enabling-the-feature">Order replacement</a> feature is enabled, customers will be able to change or cancel orders at any time, including after the grace period for cancellation.
-</div>
+>⚠️ If the [Order replacement](https://help.vtex.com/en/tutorial/order-replacement--2IK9mwQjBKseQmE8K8saO8#enabling-the-feature) feature is enabled, customers will be able to change or cancel orders at any time, including after the grace period for cancellation.
 
 ## Cancellation reason
 
diff --git a/docs/tutorials/en/order-flow-and-status.md b/docs/tutorials/en/order-flow-and-status.md
index 6f0fba9ef..7349130b7 100644
--- a/docs/tutorials/en/order-flow-and-status.md
+++ b/docs/tutorials/en/order-flow-and-status.md
@@ -35,9 +35,7 @@ There are four possible order flows on the VTEX platform:
 - [Complete flow](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#complete-flow): The order flow visible to the store responsible for the order's sale and delivery. In this case, the store acts both as a seller and marketplace.
 - [Chain flow](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#chain-flow): The order flow visible to the store that acts as an intermediary between the marketplace and the seller. This flow is similar to the marketplace flow. However, the payment is made only in the marketplace, not in the store that acts as a chain. This flow occurs in [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4) sales scenarios.
 
-<div class="alert alert-warning">
-For incomplete orders, check out the article <a href="https://help.vtex.com/en/tutorial/entendendo-os-pedidos-incompletos--tutorials_294">How incomplete orders work</a> to understand their flow and cancellation.
-</div>
+>⚠️ For incomplete orders, check out the article [How incomplete orders work](https://help.vtex.com/en/tutorial/entendendo-os-pedidos-incompletos--tutorials_294) to understand their flow and cancellation.
 
 ### Marketplace flow
 
@@ -65,9 +63,7 @@ This is the order flow visible to the store responsible for shipping the order p
 1. When the seller receives the order, its initial status is `Order accepted`.
 2. Then the order status automatically changes to `Waiting for fulfillment authorization`. This is a waiting status for the marketplace to indicate that the order payment has been confirmed. 
 
-  <div class="alert alert-danger">
-The platform allows you to manually change the status <i>Waiting for fulfillment authorization</i> by clicking <i>Authorize fulfillment</i>. However, when the seller does that manually, it does not necessarily mean that the marketplace has authorized the order fulfillment, which can lead to a mismatch of information. So use this option with caution. We recommend using it only if the marketplace has authorized the order fulfillment.
-</div>
+  >❗ The platform allows you to manually change the status <i>Waiting for fulfillment authorization</i> by clicking <i>Authorize fulfillment</i>. However, when the seller does that manually, it does not necessarily mean that the marketplace has authorized the order fulfillment, which can lead to a mismatch of information. So use this option with caution. We recommend using it only if the marketplace has authorized the order fulfillment.
 
 3. The status automatically changes to `Cancellation window`. The order will remain at this status until the [cancellation window is closed](https://help.vtex.com/en/tutorial/configuracoes-gerais/#orders).
 
@@ -80,20 +76,17 @@ The <i>Cancellation window</i> allows the customer to cancel the purchase withou
     * **Canceled order**: If the customer has requested the order cancellation within the grace period, the order status will change to `Canceling`.
 5. The order will remain in the status `Ready for handling` until the seller changes it by confirming they have started the order handling. The seller can confirm it manually in the Admin, or via ERP API integration using the [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling) request.
 
-  <div class="alert alert-danger">
-By confirming the order handling, the seller takes responsibility for reserving the order items. From that moment on, if there are any updates in the inventory, the VTEX platform dismisses these SKUs' reservation. Therefore, update the inventory only after the order has been invoiced. By doing so, you avoid inventory discrepancies in the <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integration with your store's backoffice</a>.
-</div>
+  >❗ By confirming the order handling, the seller takes responsibility for reserving the order items. From that moment on, if there are any updates in the inventory, the VTEX platform dismisses these SKUs' reservation. Therefore, update the inventory only after the order has been invoiced. By doing so, you avoid inventory discrepancies in the [integration with your store's backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide).
 
 6. Once the order is handled, it is time to invoice it. You have to add the invoice to the platform to move to the next stage. In case there are any errors, the order status can remain at `Verifying invoice`. Check out the [most common reasons](https://help.vtex.com/en/tutorial/por-que-o-pedido-esta-no-status-verificando-fatura--5VJjxRjeH6SimiG0Wkk2gm) for the order to remain in this status. Remember that if the order is only partially invoiced, its status may go back to 'Payment approved', and the retailer must add the invoices (the sum of which corresponds to the total value of the order).
 7. The last status of this flow is `Invoiced`. After that, the seller must deliver the order.
 
-<div class="alert alert-danger">
-Please note that:
-<ul>
-  <li>The <b>order can be canceled</b> at various stages of the order flow, either by the customer or the store. In this case, once requested, the cancellation process occurs automatically, as well as the order refund to the customer. The cancellation process is finished when the order status is <i>Canceled</i>.</li>
-  <li>Sellers have the autonomy to manually change the order status when the order is <i>Waiting for fulfillment authorization</i>. In this case, the seller assumes the responsibility of delivering the order without the marketplace confirmation and without receiving the order payment. If the order status has been changed manually, it is the seller's responsibility to check whether the order is ready for handling and the payment has been confirmed.</li>
-</ul>
-</div>
+>❗ Please note that:
+>
+> * The **order can be canceled** at various stages of the order flow, either by the customer or the store. In this case, once requested, the cancellation process occurs automatically, as well as the order refund to the customer. The cancellation process is finished when the order status is <i>Canceled</i>.
+>
+> * Sellers have the autonomy to manually change the order status when the order is <i>Waiting for fulfillment authorization</i>. In this case, the seller assumes the responsibility of delivering the order without the marketplace confirmation and without receiving the order payment. If the order status has been changed manually, it is the seller's responsibility to check whether the order is ready for handling and the payment has been confirmed.
+> 
 
 ### Complete flow
 
@@ -108,9 +101,7 @@ The complete order flow is visible to the store that sells and delivers the orde
     * **The payment of the order is not approved:** The platform initiates the cancellation process. This happens automatically as the order status goes from `Payment denied` to `Canceling`. Once the platform completes the cancellation, the status changes to `Canceled`, which is the last stage of the flow. With the payment approved and the cancellation window expired, the order status changes to `Ready for handling`.
 4. This status shows the retailer that the payment has been confirmed, and they can start handling the order. The store must confirm the order handling has started for the order to advance in the flow. This confirmation can be done manually in the Admin or via an ERP [API](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) using the [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling) request.
 
-  <div class="alert alert-danger">
-By confirming the order handling, the seller takes responsibility for reserving the order items. From that moment on, if there are any updates in the inventory, the VTEX platform dismisses these SKUs' reservation. Therefore, update their inventory only after the order has been invoiced. By doing so, you avoid inventory discrepancies in the <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integration with your store's backoffice</a>.
-</div>
+  >❗ By confirming the order handling, the seller takes responsibility for reserving the order items. From that moment on, if there are any updates in the inventory, the VTEX platform dismisses these SKUs' reservation. Therefore, update their inventory only after the order has been invoiced. By doing so, you avoid inventory discrepancies in the [integration with your store's backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide).
 
 5. Once the order handling starts, the order status changes to `Handling shipping` and the next step is to invoice the order. The system waits for the invoice with status `Verifying invoice`. You must [add the invoice](https://help.vtex.com/en/tutorial/como-faturar-um-pedido-manualmente-beta--7p1h852V5t54KyscpgxE2v) that corresponds to the total value of the order. 
 6. Once this is done, the order status changes to the last status, which is `Invoiced` and the store must ship the order.
@@ -134,9 +125,7 @@ Learn more about cancellation and refunds in the articles <a href="https://help.
 
 While the cancellation is being processed, the order status remains at `Canceling`. The order status changes to `Canceled` when the cancellation is complete.
 
-<div class="alert alert-danger">
-Note that when the cancellation occurs before the store starts handling the order, the items have the <a href="https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92">reservation cancelled</a> in inventory.  However, if the cancellation is made after this stage, the <a href="https://help.vtex.com/en/tutorial/como-a-reserva-funciona--tutorials_92#acknowledged-reservation">items will already be reserved</a> in the inventory. So the store must update the number of items in stock. This will make the order SKUs available for sale again.
-</div>
+>❗ Note that when the cancellation occurs before the store starts handling the order, the items have the [reservation cancelled](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92) in inventory.  However, if the cancellation is made after this stage, the [items will already be reserved](https://help.vtex.com/en/tutorial/como-a-reserva-funciona--tutorials_92#acknowledged-reservation) in the inventory. So the store must update the number of items in stock. This will make the order SKUs available for sale again.
 
 Learn more about order cancellation in the article [Why was my order cancelled?](https://help.vtex.com/en/faq/por-que-meu-pedido-foi-cancelado--frequentlyAskedQuestions_493).
 
@@ -163,9 +152,7 @@ Here is a table with more details about each order status. The table is divided
 - **Viewed by**: The flow in which the status is visible (marketplace, seller, chain, and complete).
 - **Meaning:** The detailed status meaning.
 
-<div class="alert alert-warning">
-Note that the complete order flow (visible to the stores responsible for selling and delivering orders) matches the marketplace and seller flows. Some statuses are visible via API, but not in the order flow in <b>All Orders</b> module.
-</div>
+>⚠️ Note that the complete order flow (visible to the stores responsible for selling and delivering orders) matches the marketplace and seller flows. Some statuses are visible via API, but not in the order flow in **All Orders** module.
 
 <style type="text/css">
 .tg  {border-collapse:collapse;border-color:#ccc;border-spacing:0;}
diff --git a/docs/tutorials/en/order-replacement.md b/docs/tutorials/en/order-replacement.md
index 6f7d4c3e6..2bf9ef624 100644
--- a/docs/tutorials/en/order-replacement.md
+++ b/docs/tutorials/en/order-replacement.md
@@ -19,9 +19,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 [Changing items](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) is different from replacing orders. When replacing an order, the customer requests changes to the order, and when changing items, the store modifies the order.
 
-<div class="alert alert-danger">
-The feature is available for all stores. You must enable it so that your customers can use it. 
-</div>
+>❗ The feature is available for all stores. You must enable it so that your customers can use it.
 
 This article will cover:
 
@@ -31,9 +29,7 @@ This article will cover:
 
 ## Enabling the feature
 
-<div class="alert alert-danger">
-If Order Replacement is enabled in stores whose My Orders page has customization, you must recreate the customization. The feature replaces the previous version of the page (which is customized) with a new, non-customized page. For these cases, we recommend that before activating the feature in your store, you use a <a href="https://help.vtex.com/en/tutorial/accessing-the-beta-environment--3BHM289568gcSwk2O80Asu">beta environment</a> and validate the activation with customization.
-</div>
+>❗ If Order Replacement is enabled in stores whose My Orders page has customization, you must recreate the customization. The feature replaces the previous version of the page (which is customized) with a new, non-customized page. For these cases, we recommend that before activating the feature in your store, you use a [beta environment](https://help.vtex.com/en/tutorial/accessing-the-beta-environment--3BHM289568gcSwk2O80Asu) and validate the activation with customization.
 
 To enable the feature, follow the steps below:
 
@@ -82,8 +78,6 @@ With the feature enabled, your store customers have access to a new order tracki
 
 After clicking on `Change order` , the customer will be redirected to the shopping cart, and then to checkout. At checkout, they can make changes to the address, type of delivery, payment method, and SKU. The process is only finished when the purchase is completed. The customer is not charged twice for the same order.
 
-<div class="alert alert-warning">
- Reusing the original payment is only allowed if the amount of the new order is the same as the original order. If the previous credit card payment is not used, the charge is automatically refunded.
-<p>For payment methods that expire within 2 days, such as boleto bancário (Brazilian payment method), the payment cannot be reused.
-</div>
+>⚠️ Reusing the original payment is only allowed if the amount of the new order is the same as the original order. If the previous credit card payment is not used, the charge is automatically refunded.
+> <p>For payment methods that expire within 2 days, such as boleto bancário (Brazilian payment method), the payment cannot be reused.
 
diff --git a/docs/tutorials/en/order-split-and-delivery-split.md b/docs/tutorials/en/order-split-and-delivery-split.md
index 0e9629c55..46e11b8da 100644
--- a/docs/tutorials/en/order-split-and-delivery-split.md
+++ b/docs/tutorials/en/order-split-and-delivery-split.md
@@ -52,8 +52,6 @@ The order is fulfilled by a single seller, but more than one delivery is require
 
     This split is done automatically and natively for stores that have Checkout V6, through the `allowMultipleDeliveries` field indicated as `true` in the API [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm). The configuration is enabled by default so that it is possible to make purchases with different delivery methods in the same cart.
 
-<div class="alert alert-danger">
-  We do not recommend operating the store with the <code>allowMultipleDeliveries</code> field indicated as <i>false</i>. In this configuration, when there are items in the cart that do not have any delivery method in common, that is, the SLAIDs are different, and the cart has a pickup-point, it will not be possible to complete the order.
-</div>
+>❗ We do not recommend operating the store with the `allowMultipleDeliveries` field indicated as <i>false</i>. In this configuration, when there are items in the cart that do not have any delivery method in common, that is, the SLAIDs are different, and the cart has a pickup-point, it will not be possible to complete the order.
 
 * **Different loading docks:** a single store offers all the items in an order, but in the calculated logistic route they are related to different docks. Then, _the delivery packages must be split_, but without splitting the order between different stores. The platform does this automatically.
diff --git a/docs/tutorials/en/order-to-delivery.md b/docs/tutorials/en/order-to-delivery.md
index 962188b1e..a2efc5c9e 100644
--- a/docs/tutorials/en/order-to-delivery.md
+++ b/docs/tutorials/en/order-to-delivery.md
@@ -15,6 +15,4 @@ legacySlug: order-to-delivery
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>  
+>⚠️ This content is only available in Portuguese.  
diff --git a/docs/tutorials/en/order-transactional-email-templates.md b/docs/tutorials/en/order-transactional-email-templates.md
index d4963a1f6..2e9f7c2d2 100644
--- a/docs/tutorials/en/order-transactional-email-templates.md
+++ b/docs/tutorials/en/order-transactional-email-templates.md
@@ -17,9 +17,7 @@ subcategory: 4D5LrWwlHGmOWMomOaaGee
 
 The purpose of this article is to list the default transactional email templates that relate to the order flow. In addition, we will specify the triggers required to sent each email.
 
-<div class="alert alert-warning">
-Notice: fulfillment orders do not receive transactional emails from VTEX. In this case, the marketplace is reponsible for notification emails.
-</div>
+>⚠️ Notice: fulfillment orders do not receive transactional emails from VTEX. In this case, the marketplace is reponsible for notification emails.
 
 To view the available templates, follow the steps below:
 
diff --git a/docs/tutorials/en/orders-management-feed-v3-setup.md b/docs/tutorials/en/orders-management-feed-v3-setup.md
index b132cb558..2816b3a06 100644
--- a/docs/tutorials/en/orders-management-feed-v3-setup.md
+++ b/docs/tutorials/en/orders-management-feed-v3-setup.md
@@ -23,13 +23,9 @@ The Feed v3 allows for feed customization with filters and intervals necessary f
 
 This means that it's possible to define which status will be visible on your store's event feed through the [API Feed Configuration](https://developers.vtex.com/reference/feed-v3#feedconfiguration). The list of possible order statuses can be seen in the article [Order flow in Orders management](https://help.vtex.com/en/tutorial/fluxo-de-pedido/#understanding-the-status).
 
-<div class="alert alert-info">
-If the <code>filter</code> object is not configured in the API, <strong>all</strong> status updates are sent to the feed.
-</div>
+>ℹ️ If the `filter` object is not configured in the API, **all** status updates are sent to the feed.
 
-<div class="alert alert-info"> 
-The AppKey that will be used in the integration must be the same as the one used in the initial setup.
-</div>
+>ℹ️ The AppKey that will be used in the integration must be the same as the one used in the initial setup.
 
 An example of a body is as follows:
 
@@ -52,17 +48,13 @@ The field is defined with a default visibility timeout of 30 seconds, but it can
 
 Your feed's event retention time is defined in seconds in the `MessageRetentionPeriodInSeconds` field. If an event does not receive interactions within the configured time, it will be excluded from the feed queue and its pertaining data will be lost. The maximum time for this field is 345600 seconds (4 days). 
 
-<div class="alert alert-info">
-In order to configure and use Feed v3, a <code>Feed v3 and Hook</code> enabled <a href="https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?locale=en">role</a> within <strong>OMS</strong> is required.
-</div>
+>ℹ️ In order to configure and use Feed v3, a `Feed v3 and Hook` enabled [role](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?locale=en) within **OMS** is required.
 
 ## How Feed v3 APIs work
 
 Feed v3 works with two calls: one for readout and the other to inform that an event has already been read and should therefore be excluded.
 
-<div class="alert alert-warning"> 
-Don't forget to configure the Feed before using it!
-</div>
+>⚠️ Don't forget to configure the Feed before using it!
 
 ### Get Feed order status
 
@@ -70,9 +62,7 @@ The [call to read the feed](https://developers.vtex.com/reference/feed-v3#getfee
 
 The `maxLot` parameter indicates the maximum number of events that will be returned with each call. In Feed v3, you may specify __up to 10 events__.
 
-<div class="alert alert-warning">
-Each time a call for a feed readout is made, <strong>all</strong> returned events become invisible in the feed for the time defined in the <code>visibilityTimeoutInSeconds</code> of the Feed Configuration API.
-</div> 
+>⚠️ Each time a call for a feed readout is made, **all** returned events become invisible in the feed for the time defined in the `visibilityTimeoutInSeconds` of the Feed Configuration API. 
 
 ### Confirm item feed order status
 
@@ -82,15 +72,11 @@ After a feed readout, it's time to [commit events](https://developers.vtex.com/r
 
 Each array from the body can have as many `handles` as necessary, making it possible to commit more than one event at a time.
 
-<div class="alert alert-info">
-The <code>visibilityTimeoutInSeconds</code> field displays the time limit to <i>commit</i> an event.
-</div> 
+>ℹ️ The `visibilityTimeoutInSeconds` field displays the time limit to <i>commit</i> an event. 
 
 There are no cases where a feed event should not be committed. Your system should commit all events present in your queue. __Once an event has been committed, it's impossible to recover in the feed using the same appkey.__
 
-<div class="alert alert-warning">
-All possible order statuses (considering filtering, when applicable) must be dealt with during integration to avoid errors. Special attention should be given to <code>Status Null</code>, which may not be identified and ends up being mapped as another status, potentially leading to errors.
-</div> 
+>⚠️ All possible order statuses (considering filtering, when applicable) must be dealt with during integration to avoid errors. Special attention should be given to `Status Null`, which may not be identified and ends up being mapped as another status, potentially leading to errors. 
 
 For more on this, read our article on [how the Orders Management feed works](https://help.vtex.com/en/tutorial/how-the-orders-management-feed-v3-workds--5SzSKee2f666YCoWkm0eQC).
 
diff --git a/docs/tutorials/en/out-of-stock-errors-in-marketplace-integration-orders.md b/docs/tutorials/en/out-of-stock-errors-in-marketplace-integration-orders.md
index 3fd9db77a..940f9fffc 100644
--- a/docs/tutorials/en/out-of-stock-errors-in-marketplace-integration-orders.md
+++ b/docs/tutorials/en/out-of-stock-errors-in-marketplace-integration-orders.md
@@ -28,9 +28,7 @@ Out-of-stock errors can occur for different reasons. Here are the most common:
 
 After resolving the error, the order must be manually reprocessed. In your Admin, go to **MARKETPLACE > Connections > Orders** and click on the order with the error. Click on the **Actions** button and choose the **Reprocess** option.
 
-<div class="alert alert-info">
-If the error persists, please open a <a href="https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">VTEX support ticket</a>.
-</div>
+>ℹ️ If the error persists, please open a [VTEX support ticket](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
 ### Learn more
 
diff --git a/docs/tutorials/en/payment-provider-protocol.md b/docs/tutorials/en/payment-provider-protocol.md
index 70a76eb6a..4403d63da 100644
--- a/docs/tutorials/en/payment-provider-protocol.md
+++ b/docs/tutorials/en/payment-provider-protocol.md
@@ -70,9 +70,7 @@ The provider must forward the [AOC](https://www.pcisecuritystandards.org/documen
 - __Signature__: document signed by the company representative and the QSA.
 - __Expiration Date__: the validity of the AOC is 1 year after the signing date. The AOC issued more than 11 months ago must not be sent to VTEX, that is, less than 30 days before its expiration date.
 
-<div class="alert alert-danger">
-The SAQ (Self-Assessment Questionnaire) and AOC (Attestation of Compliance for Onsite Assessments – Merchants Version) documents are not accepted in the VTEX integration process.
-</div>
+>❗ The SAQ (Self-Assessment Questionnaire) and AOC (Attestation of Compliance for Onsite Assessments – Merchants Version) documents are not accepted in the VTEX integration process.
 <br>
 
 #### Payment providers with notes payables, Brazilian boleto or private label cards (or providers of any kind of card using redirect solutions)
@@ -97,10 +95,11 @@ After getting access information and implementing the backend, the provider has
 
 ![ppp-vtex-store-en](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/ea2026578b79d3c5edd33c997b62efa9/image.png)
 
-<div class="alert alert-warning">
-<p>To pass the homologation process, you need to implement specific logic to handle the test requirements. When sending requests to Test Suite, use the extra header <code>X-VTEX-API-Is-TestSuite = true</code> to identify them and mask any required case.<br><br>All communication with servers, whether during the homologation process or in production, must be via HTTPS, which by default uses port 443. Note that all HTTPS communication must be exclusively over TLS 1.2.
-</p>
-</div> 
+>⚠️ To pass the homologation process, you need to implement specific logic to handle the test requirements. When sending requests to Test Suite, use the extra header `X-VTEX-API-Is-TestSuite = true` to identify them and mask any required case.
+>
+> 
+>
+> All communication with servers, whether during the homologation process or in production, must be via HTTPS, which by default uses port 443. Note that all HTTPS communication must be exclusively over TLS 1.2. 
 
 After installing, click __Apps__ in the left menu of the Admin. Then, select the __Payment Provider Test Suite__ app to complete the setup.
 
@@ -113,10 +112,7 @@ Then, you will find a form with three sections: Service information, Payment met
 * **Service URL:** Define the URL of the service provider. This URL will be the base address for the protocol and must follow the format determined by it. For example, if the service URL is `https://example.com/`, the full URL for the /payments endpoint will be `https://example.com/payments`.
 * **AppKey and AppToken:** The Test with AppKey and AppToken button allows you to choose whether or not to configure the values of these fields, which can make testing easier during the development stage. If you do not enable this option, the credentials will be sent in the headers as an empty string.
 
-<div class="alert alert-info">
-<p>The gateway saves the store credentials configured in the affiliation and sends them in the X-VTEX-API-AppKey and X-VTEX-API-AppToken headers. The exceptions are integrations developed using VTEX IO, for which the headers will be sent as x-provider-api-appKey and x-provider-api-appToken. If you are developing using the <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework">Payment Provider Framework (IO)</a>, this is configured by the usesProviderHeadersName option. See the available settings <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework#available-configurable-options">here</a>.
-</p>
-</div>
+>ℹ️ The gateway saves the store credentials configured in the affiliation and sends them in the X-VTEX-API-AppKey and X-VTEX-API-AppToken headers. The exceptions are integrations developed using VTEX IO, for which the headers will be sent as x-provider-api-appKey and x-provider-api-appToken. If you are developing using the [Payment Provider Framework (IO)](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework), this is configured by the usesProviderHeadersName option. See the available settings [here](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework#available-configurable-options).
 
 ![Payment Provider Test Suite 0](https://images.ctfassets.net/alneenqid6w5/3V1eMOFEQ8Mg4ygC46G4AY/15d41dae35aaa91f3dd9b55e1bdcee1f/Payment_Provider_Test_Suite_0.jpg)
 
@@ -142,9 +138,7 @@ When you click the `Run Test` button, Test Suite will call the provided service
 * **Boleto flow:** Boleto is a popular payment method in Brazil. In this test, we send a[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to {{ServiceURL}}/payments, expecting the status undefined as a response and the bankIssueUrl field containing the boleto ticket URL. After 15 seconds, we expect to receive another response in the same format via a POST with the URL sent in the callbackUrl field and with status approved. When the integration is in production, this last call made by callbackUrl is authenticated with the partner’s environment keys: vtex-app-key and vtex-app-token. Learn more about the callback flow in the [Payment Authorization](#payment-authorization) section.
 * **Redirect flow:** This test is divided in two steps. First, we send a [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request to `{{ServiceURL}}/payments`, expecting the status undefined as a response and the redirectUrl field containing the URL that will be used to redirect the customer. After 15 seconds, we expect to receive another response in the same format via a POST with the URL sent in the callbackUrl field and with status approved. When the integration is in production, this last call made by callbackUrl is authenticated with the partner's environment keys: vtex-app-key and vtex-app-token. Learn more about the callback flow in the [Payment Authorization](#payment-authorization) section. Connectors that will use **Redirect** don’t need to pass all Test Suite tests, only the **Redirect** test.
 
-<div class="alert alert-warning"><p>
-For credit cards, the mandatory tests are Authorize, Denied, Cancel, Async Approved, and Async Denied.
-</p></div>
+>⚠️ For credit cards, the mandatory tests are Authorize, Denied, Cancel, Async Approved, and Async Denied.
 
 Use the following numbers to identify how to correctly respond to each credit card test:
 
@@ -172,8 +166,7 @@ It all starts with requesting a new payment after the creation of a new order. V
 
 ![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
 
-<div class="alert alert-info">
-  The default period of 7 days for asynchronous payment retries is only applied when the user does not specify a value in the <code>delayToCancel</code> field of the <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> endpoint or when sending the callbackURL.</div>
+>ℹ️ The default period of 7 days for asynchronous payment retries is only applied when the user does not specify a value in the `delayToCancel` field of the [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) endpoint or when sending the callbackURL.
 
 ### Payment Authorization
 
@@ -223,21 +216,15 @@ See below an example of a payload forwarded along with the callback URL:
 {"paymentId":"8B3BA2F4352545A8B1C5A215F356A01C","status":"approved","authorizationId":"184520","nsu":"21705348","tid":"21705348","acquirer":"pagarme","code":"0000","message":"Transação aprovada com sucesso","delayToAutoSettle":1200, "delayToAutoSettleAfterAntifraud":1200, "delayToCancel":86400,"cardBrand":"Mastercard","firstDigits":"534696","lastDigits":"6921","maxValue":16.6}
 ```
 
-<div class="alert alert-info">
-  The parameter values sent in the callback payload replace the original values informed in the <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> request.  
-</div>
+>ℹ️ The parameter values sent in the callback payload replace the original values informed in the [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) request.
 
-<div class="alert alert-warning">
-  If the waiting parameters (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) are not sent with the callback URL, these values will be automatically set to 24 hours.
-</div>
+>⚠️ If the waiting parameters (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) are not sent with the callback URL, these values will be automatically set to 24 hours.
 
 When making the callback request, we recommend that payment providers use the callback URL exactly as received, which guarantees that all the parameters are included.
 
 When calling Callback URL, your provider should send in the request the *X-VTEX-API-AppKey* and *X-VTEX-API-AppToken* headers. Check more information about this in the [VTEX credentials section](/en/tutorial/payment-provider-protocol#vtex-credentials).
 
-<div class="alert alert-danger">
-In addition to the Callback URL, if the status is <strong>undefined</strong>, VTEX will try again to call the payment authorization endpoint. If the status returned on these calls remains <strong>undefined</strong>, calls will continue for up to 7 days. That's why <strong>it's important that your provider be ready to receive the same payment authorization several times</strong>.
-</div>
+>❗ In addition to the Callback URL, if the status is **undefined**, VTEX will try again to call the payment authorization endpoint. If the status returned on these calls remains **undefined**, calls will continue for up to 7 days. That's why **it's important that your provider be ready to receive the same payment authorization several times**.
 
 Once the payment has been processed by your provider, either directly or asynchronously, we move the payment transaction within VTEX to the *authorized* or *canceled* status, according to the processing response status.
 
@@ -262,9 +249,7 @@ If the payment transaction is authorized in VTEX Payments, it can receive settle
 
 When the provider receives a request for settlement, it must settle the payment and respond with settlement information. If this call fails, we do some retries for up to 1 day.
 
-<div class="alert alert-danger">
-Your provider must be prepared to receive the same settlement call multiple times.
-</div>
+>❗ Your provider must be prepared to receive the same settlement call multiple times.
 
 If the settlement call works fine, we move the payment transaction to the *Finished* status, and the stream ends successfully.
 
diff --git a/docs/tutorials/en/payments-in-vtex-marketplaces.md b/docs/tutorials/en/payments-in-vtex-marketplaces.md
index 6d5314dd5..2df72016f 100644
--- a/docs/tutorials/en/payments-in-vtex-marketplaces.md
+++ b/docs/tutorials/en/payments-in-vtex-marketplaces.md
@@ -27,9 +27,7 @@ Orders placed in a marketplace may contain items from multiple sellers, which ar
 
 If the seller is the payment processor, they must operate under the conditions determined in our [Transaction split](https://help.vtex.com/en/tutorial/split-payment#transaction-split). Similarly, if the VTEX marketplace is the payment processor, it must follow the [Payout split](https://help.vtex.com/en/tutorial/split-payment#payout-split) flow or perform its transactions outside the VTEX environment.
 
-<div class="alert alert-info">
-VTEX clients in Brazil can use both transaction splits and payout splits. However, VTEX clients in other countries must only use transaction splits. Please note that some countries impose restrictions on transfers between sellers and marketplaces. Get in touch with your country's financial authorities to learn more about these restrictions before building your payment architecture.
-</div>
+>ℹ️ VTEX clients in Brazil can use both transaction splits and payout splits. However, VTEX clients in other countries must only use transaction splits. Please note that some countries impose restrictions on transfers between sellers and marketplaces. Get in touch with your country's financial authorities to learn more about these restrictions before building your payment architecture.
 
 Use the OMS reports to calculate commissions when setting the amounts for transfers outside the VTEX environment. In Brazil, transfers in external environments, without the participation of platforms such as VTEX, can only be performed by financial institutions.
 
@@ -37,9 +35,7 @@ Use the OMS reports to calculate commissions when setting the amounts for transf
 
 See below for the necessary configurations to create commissions for sellers and to configure a seller or a marketplace as the payment processor.
 
-<div class="alert alert-info">
-If your integration with external sellers or VTEX sellers is done via API, please refer to the article <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-seller-processing-payments">External seller processing payment</a>. 
-</div>
+>ℹ️ If your integration with external sellers or VTEX sellers is done via API, please refer to the article <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-seller-processing-payments">External seller processing payment</a>.
 
 ### Configuring commissions for sellers
 
diff --git a/docs/tutorials/en/payu-romania-refund-details.md b/docs/tutorials/en/payu-romania-refund-details.md
index c9c63a1b9..2afaa646b 100644
--- a/docs/tutorials/en/payu-romania-refund-details.md
+++ b/docs/tutorials/en/payu-romania-refund-details.md
@@ -15,9 +15,7 @@ legacySlug: payu-romania-refund-details
 subcategory: 3Gdgj9qfu8mO0c0S4Ukmsu
 ---
 
-<div class="alert alert-warning">
-This article applies only for payments made in <b>Romania</b>.
-</div>
+>⚠️ This article applies only for payments made in **Romania**.
 
 Payment cancellations (also called voids – they can be placed only for the full amount) or refunds (total or partial) are not processed immediately, but with a timeout instead. 
 
diff --git a/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md b/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md
index 12667cc96..eba0ba9ff 100644
--- a/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md
+++ b/docs/tutorials/en/penetration-testing-and-vulnerability-notice.md
@@ -15,13 +15,9 @@ legacySlug: security-assessment-and-vulnerability-report
 subcategory: vONCJSxwN5qZiElOEtKkH
 ---
 
-<div class="alert alert-info">
-  <p>This feature is part of <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/br-pt/contato/">contact form</a>.</p>
-</div>
+>ℹ️ This feature is part of [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our [contact form](https://vtex.com/br-pt/contato/).
 
-<div class="alert alert-warning">
-  <p>If you require an analysis of your penetration test report by a VTEX Security analyst, it is necessary to have VTEX Shield. Furthermore, all penetration tests must be previously <a href="#scheduling-penetration-tests">scheduled with VTEX</a>. Any test conducted autonomously without prior notice to VTEX will be considered an unauthorized action attempt.</p>
-</div>
+>⚠️ If you require an analysis of your penetration test report by a VTEX Security analyst, it is necessary to have VTEX Shield. Furthermore, all penetration tests must be previously [scheduled with VTEX](#scheduling-penetration-tests). Any test conducted autonomously without prior notice to VTEX will be considered an unauthorized action attempt.
 
 VTEX rigorously evaluates platform features by testing and detecting vulnerabilities through recurring scanning and penetration testing. These vulnerability checks are performed periodically.
 
@@ -40,9 +36,7 @@ In this guide, we explain how to schedule a penetration test and report any pote
 
 ## Scheduling penetration tests
 
-<div class="alert alert-warning">
-  <p>Only stores using <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a> can schedule a penetration test and are entitled to a reply from the Security team, with access to an in-depth test report analysis, as described in the procedures in this guide.</p>
-</div>
+>⚠️ Only stores using [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) can schedule a penetration test and are entitled to a reply from the Security team, with access to an in-depth test report analysis, as described in the procedures in this guide.
 
 To run a penetration test in your store's environment, you must align the test schedule with VTEX, for internal organization and planning by the Security team. Follow the instructions below:
 
@@ -58,9 +52,7 @@ To run a penetration test in your store's environment, you must align the test s
 6. Run the test on the scheduled date, subject to authorization from VTEX.
 7. Send a report with the results in the same ticket to [VTEX Support](https://help.vtex.com/en/support).
 
-   <div class="alert alert-warning">
-  <p>You must follow the guidelines described in <a href="#penetration-test-reports">Penetration test reports</a> to meet the analysis deadline set by VTEX.</p>
-   </div>
+   >⚠️ You must follow the guidelines described in [Penetration test reports](#penetration-test-reports) to meet the analysis deadline set by VTEX.
 
    Assign a person from your security team to be the point of contact for the VTEX Security team throughout the test report analysis.
 
@@ -68,9 +60,7 @@ The VTEX Security team is committed to conducting a comprehensive analysis of al
 
 Within 10 working days after receiving the [report](#penetration-test-reports), the team will identify false positives and reclassify the threat severity as necessary, following VTEX's best practices. Each decision in this process will include a detailed rationale to ensure full transparency and understanding.
 
-<div class="alert alert-warning">
-  <p>Stores planning their go-live and willing to run a penetration test must also schedule it in advance. In this case, they must send the report with the results to <a href="https://help.vtex.com/en/support">VTEX Support</a> at least <strong>45 days</strong> before the planned go-live date. During this period, VTEX will analyze the results and address any vulnerabilities identified. </p>
-</div>
+>⚠️ Stores planning their go-live and willing to run a penetration test must also schedule it in advance. In this case, they must send the report with the results to [VTEX Support](https://help.vtex.com/en/support) at least **45 days** before the planned go-live date. During this period, VTEX will analyze the results and address any vulnerabilities identified.
 
 ### Penetration test reports
 
@@ -113,9 +103,7 @@ We encourage our clients to responsibly report any security vulnerabilities they
 
 If you wish to report a vulnerability, you should first work with your security and development teams to conduct a security assessment and eliminate false positives or issues arising from custom configurations. Only cases compatible with the [definition of vulnerability](#vulnerability-definition) will be analyzed.
 
-<div class="alert alert-warning">
-  <p>Please review the<a href="https://vtex.com/us-en/security/security-practices/"> VTEX Security Practices</a> document and our<a href="https://help.vtex.com/en/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX#risk-assessment-at-vtex"> Security FAQ</a> before reporting any vulnerabilities. These documents clarify our processes and help eliminate false positives.</p>
-</div>
+>⚠️ Please review the[ VTEX Security Practices](https://vtex.com/us-en/security/security-practices/) document and our[ Security FAQ](https://help.vtex.com/en/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX#risk-assessment-at-vtex) before reporting any vulnerabilities. These documents clarify our processes and help eliminate false positives.
 
 After this, follow the steps below to report if there is a vulnerability:
 
@@ -124,9 +112,7 @@ After this, follow the steps below to report if there is a vulnerability:
 
    Vulnerabilities must be reported individually, following the template. If you encountered more than one vulnerability in your test, please complete multiple templates and attach them to your ticket.
 
-  <div class="alert alert-warning">
-    <p>All information must be provided and is essential for the assessment. The VTEX Security team will not address vulnerability notifications that do not follow the established template.</p>
-  </div>
+  >⚠️ All information must be provided and is essential for the assessment. The VTEX Security team will not address vulnerability notifications that do not follow the established template.
 
 3. Open a ticket with our [Support](https://help.vtex.com/en/support) to submit the security vulnerability notification. Do not forget to attach the completed vulnerability notification template in the ticket.
 4. Save your ticket number, as you may need it in future communications.
diff --git a/docs/tutorials/en/pickup-points-for-subscription-orders-beta.md b/docs/tutorials/en/pickup-points-for-subscription-orders-beta.md
index 9f576a515..17b7380e3 100644
--- a/docs/tutorials/en/pickup-points-for-subscription-orders-beta.md
+++ b/docs/tutorials/en/pickup-points-for-subscription-orders-beta.md
@@ -15,9 +15,7 @@ legacySlug: pickup-points-for-subscription-orders-beta
 subcategory: 3RmFd9bgAeRAVGeBd7XDUr
 ---
 
-<div class="alert alert-info">
-  <p>This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/pt-br/requests).
 
 A pickup point is a physical location where customers can pick up their orders, instead of having them delivered to their homes. A common usage scenario for this feature is the in-store pickup, for example.
 
@@ -28,9 +26,7 @@ Check out how to enable this feature:
 - [Requirements](#requirements)
 - [Choosing pickup points](#choosing-pickup-points)
 
-<div class="alert alert-info">
-  <p>The pickup points feature is available in beta only for accounts using the <b>Checkout V6</b>.</p>
-</div>
+>ℹ️ The pickup points feature is available in beta only for accounts using the **Checkout V6**.
 
 ## Requirements
 
diff --git a/docs/tutorials/en/pickup-points-for-subscription-orders.md b/docs/tutorials/en/pickup-points-for-subscription-orders.md
index f3dd39c32..4a7826259 100644
--- a/docs/tutorials/en/pickup-points-for-subscription-orders.md
+++ b/docs/tutorials/en/pickup-points-for-subscription-orders.md
@@ -24,9 +24,7 @@ Check out how to enable this feature:
 - [Requirements](#requirements)
 - [Choosing pickup points](#choosing-pickup-points)
 
-<div class="alert alert-info">
-  <p>The pickup points feature is available only for accounts using the <a href="https://help.vtex.com/en/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH">Checkout V6</a>.</p>
-</div>
+>ℹ️ The pickup points feature is available only for accounts using the [Checkout V6](https://help.vtex.com/en/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH).
 
 ## Requirements
 
diff --git a/docs/tutorials/en/pickup-points.md b/docs/tutorials/en/pickup-points.md
index 5f4f397d6..67a7863ae 100644
--- a/docs/tutorials/en/pickup-points.md
+++ b/docs/tutorials/en/pickup-points.md
@@ -80,7 +80,7 @@ VTEX considers the pickup point to be a shipping method, and therefore the setti
     - Step 1: In the VTEX Admin, go to **Store settings > Storefront > Checkout**, or type *Checkout* in the search bar at the top of the page.  
     - Step 2: Select the configuration used in the store and click the <i class="fas fa-cog"></i> icon.
     - Step 3: Click the **Checkout** tab in the top bar.
-    - Step 4: Select the <i class="fas fa-toggle-on"></i> from the **Invoice address in pickup**.![NFpontoretiradaEN](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/a221ea377c5b7629eba243f55cf80058/NFpontoretiradaEN.png)<div class="alert alert-warning">The option of <b>Invoice address in pickup</b> must be enabled in all stores in Brazil, as it is a requirement that the invoice issued contains the customer's address information, even if the option to delivery of the order is at the pick-up point. The address filled in by the customer will be recorded in the `invoiceData` field of the <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - Step 4: Select the <i class="fas fa-toggle-on"></i> from the **Invoice address in pickup**.![NFpontoretiradaEN](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/a221ea377c5b7629eba243f55cf80058/NFpontoretiradaEN.png)>⚠️ The option of **Invoice address in pickup** must be enabled in all stores in Brazil, as it is a requirement that the invoice issued contains the customer's address information, even if the option to delivery of the order is at the pick-up point. The address filled in by the customer will be recorded in the `invoiceData` field of the [orderForm](https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata).
 
 6. Set the amount of pickup points that are displayed at checkout:
     - Step 1: In the VTEX Admin, go to **Store settings > Shipping > Settings**, or type *Shipping* in the search bar at the top of the page and select *Store settings / Shipping*.    
diff --git a/docs/tutorials/en/pipedrive-suiteshare.md b/docs/tutorials/en/pipedrive-suiteshare.md
index a3ee9527d..2044b1726 100644
--- a/docs/tutorials/en/pipedrive-suiteshare.md
+++ b/docs/tutorials/en/pipedrive-suiteshare.md
@@ -15,7 +15,5 @@ legacySlug: pipedrive
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
 
diff --git a/docs/tutorials/en/piperun-suiteshare.md b/docs/tutorials/en/piperun-suiteshare.md
index f88e99067..108782775 100644
--- a/docs/tutorials/en/piperun-suiteshare.md
+++ b/docs/tutorials/en/piperun-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: piperun-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/planner-actions-on-releases-beta.md b/docs/tutorials/en/planner-actions-on-releases-beta.md
index a2facfb14..669306d88 100644
--- a/docs/tutorials/en/planner-actions-on-releases-beta.md
+++ b/docs/tutorials/en/planner-actions-on-releases-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-actions-on-releases-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>The <strong>Releases</strong> is in beta version, which means we are working to improve it. This feature is only available for stores using <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ The **Releases** is in beta version, which means we are working to improve it. This feature is only available for stores using [FastStore](https://www.faststore.dev/).
 
 The **Releases** module allows you to manage [releases](https://help.vtex.com/en/tutorial/planner-release-concept-beta--4pWhQTXG0aIIsi2TYxxRkZ) so that you can coordinate the creation, schedule and publication of the changes in your store. A release is a change or a group of changes that can be published together.
 
@@ -36,9 +34,7 @@ Each page displays a view of the releases and allows you to perform different ac
 * [Publish a release](#publish-a-release)
 * [Delete a release](#delete-a-release)
 
-<div class="alert alert-warning">
-  <p>In the beta version, releases must be <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>-related, because other VTEX platform modules are not yet included. To use the <strong>Releases</strong>, you must configure the CMS as described in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ In the beta version, releases must be [CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2)-related, because other VTEX platform modules are not yet included. To use the **Releases**, you must configure the CMS as described in [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Create a release
 
@@ -113,9 +109,7 @@ In order to publish a release and make the changes available in the storefront o
 
 A release can be deleted in every [release status](https://help.vtex.com/en/tutorial/planner-release-concept-beta--4pWhQTXG0aIIsi2TYxxRkZ#status-of-releases), i.e., it can be deleted permanently.
 
-<div class="alert alert-info">
-  <p>If instead of deleting a release you want to archive it, you should unpublish it so that it is not deleted and you can republish it at any time.</p>
-</div>
+>ℹ️ If instead of deleting a release you want to archive it, you should unpublish it so that it is not deleted and you can republish it at any time.
 
 When you delete a release in the `Published` status, its changes remain in the storefront of the store, the only thing that no longer exists is the release with the changes.
 
diff --git a/docs/tutorials/en/planner-calendar-page-beta.md b/docs/tutorials/en/planner-calendar-page-beta.md
index 3c32dbdd5..d96e52c9b 100644
--- a/docs/tutorials/en/planner-calendar-page-beta.md
+++ b/docs/tutorials/en/planner-calendar-page-beta.md
@@ -16,9 +16,7 @@ subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
 
-<div class="alert alert-info">
-  <p>The <strong>Releases</strong> is in beta version, which means we are working to improve it. This feature is only available for stores using <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ The **Releases** is in beta version, which means we are working to improve it. This feature is only available for stores using [FastStore](https://www.faststore.dev/).
 
 The **Releases** module allows you to [manage your releases](https://help.vtex.com/en/tutorial/planner-actions-on-releases-beta--1zsomdifPEQkdV6RW93JyW) so that you can coordinate the creation, schedule and publication of the changes in your store.
 
@@ -32,9 +30,7 @@ You can view the **Calendar** page in three ways:
 
 **Calendar** only shows [scheduled releases](https://help.vtex.com/en/tutorial/planner-actions-on-releases-beta--1zsomdifPEQkdV6RW93JyW#schedule). To view all your releases, access the [Releases](https://help.vtex.com/en/tutorial/planner-releases-page-beta--2p7IiVD6K8i1iRiwHph5sw) page.
 
-<div class="alert alert-warning">
-  <p>In the beta version, the releases must be <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>-related, because other VTEX platform modules are not yet included. To use the <strong>Releases</strong>, you must configure the CMS as described in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ In the beta version, the releases must be [CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2)-related, because other VTEX platform modules are not yet included. To use the **Releases**, you must configure the CMS as described in [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## View per month
 
diff --git a/docs/tutorials/en/planner-release-concept-beta.md b/docs/tutorials/en/planner-release-concept-beta.md
index f49f65f07..816a338d5 100644
--- a/docs/tutorials/en/planner-release-concept-beta.md
+++ b/docs/tutorials/en/planner-release-concept-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-release-concept-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>The <strong>Releases</strong> is in beta version, which means we are working to improve it. This feature is only available for stores using <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ The **Releases** is in beta version, which means we are working to improve it. This feature is only available for stores using [FastStore](https://www.faststore.dev/).
 
 Managing an ecommerce operation requires the retailer to perform a series of store updates to the store, which are often interconnected. For example, carrying out an advertising campaign in which different storefront elements need to be configured.
 
@@ -30,9 +28,7 @@ A release means a change or a group of changes that can be published together. T
 * Greater control when testing and reviewing modifications prior to their publication.
 * Ease in scheduling or deleting groups of modifications.
 
-<div class="alert alert-warning">
-  <p>In the beta version, releases must be <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>-related, because other VTEX platform modules are not yet included. To use the <strong>Releases</strong>, you must configure the CMS as described in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ In the beta version, releases must be [CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2)-related, because other VTEX platform modules are not yet included. To use the **Releases**, you must configure the CMS as described in [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 The feature can be accessed through the VTEX Admin **Releases** navigation menu, where you'll find the following pages:
 
diff --git a/docs/tutorials/en/planner-releases-page-beta.md b/docs/tutorials/en/planner-releases-page-beta.md
index cf3c530f4..45df39677 100644
--- a/docs/tutorials/en/planner-releases-page-beta.md
+++ b/docs/tutorials/en/planner-releases-page-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-releases-page-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>The <strong>Releases</strong> is in beta version, which means we are working to improve it. This feature is only available for stores using <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ The **Releases** is in beta version, which means we are working to improve it. This feature is only available for stores using [FastStore](https://www.faststore.dev/).
 
 The **Releases** module allows you to [manage your releases](https://help.vtex.com/en/tutorial/planner-release-concept-beta--4pWhQTXG0aIIsi2TYxxRkZ) so that you can coordinate the creation, schedule and publication of the changes in your store.
 
@@ -27,9 +25,7 @@ On the **Releases** page, you'll see all existing releases listed by the `Not sc
 
 The order of the scheduled releases is based on the publication date: The further into the future a release is, the sooner it'll appear on the list. However, the older the release is, the latest it'll appear.
 
-<div class="alert alert-warning">
-  <p>In the beta version, releases must be <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>-related, because other VTEX platform modules are not yet included. To use the <strong>Releases</strong>, you must configure the CMS as described in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ In the beta version, releases must be [CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2)-related, because other VTEX platform modules are not yet included. To use the **Releases**, you must configure the CMS as described in [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## List view
 
diff --git a/docs/tutorials/en/predefined-roles.md b/docs/tutorials/en/predefined-roles.md
index a25c5e7a5..a4aae9f5c 100644
--- a/docs/tutorials/en/predefined-roles.md
+++ b/docs/tutorials/en/predefined-roles.md
@@ -19,9 +19,7 @@ subcategory: 1HSqkejwuYcQSMC400uY84
 
 In this document, are listed the roles that are predefined for new VTEX stores and their respective resources. To access them directly, use the list below.
 
-<div class="alert alert-info">
-<p>Learn more about each resource listed in the roles below in <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">License Manager Resources</a>.</p>
-</div>
+>ℹ️ Learn more about each resource listed in the roles below in [License Manager Resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
 
 * [Admin - Start page only](#admin-start-page-only)
 * [Checkout Admin](#checkout-admin)
@@ -75,9 +73,7 @@ The Assisted Sales resource causes the user to be automatically redirected to th
 
 We therefore recommend using two separate accounts (with different emails) for telesales users: one account for the __Call center operator__ role (with the *Assisted Sales* and *View order* resources) and another account for carrying out operations in Admin, if necessary.
 
-<div class="alert alert-warning">
-When creating a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">role</a>, avoid including call center <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">resources</a> with other resources. Otherwise, the role might not work as expected.
-</div>
+>⚠️ When creating a [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#), avoid including call center [resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) with other resources. Otherwise, the role might not work as expected.
 
 Resource table:
 
@@ -144,9 +140,7 @@ Resource table:
 
 ## Sales App - Sales Associate
 
-<div class="alert alert-warning">
-  <p>Sales associates registered in Sales App cannot access the VTEX Admin, only Sales App.</p>
-</div>
+>⚠️ Sales associates registered in Sales App cannot access the VTEX Admin, only Sales App.
 
 Resource table:
 
diff --git a/docs/tutorials/en/price-divergence-rule.md b/docs/tutorials/en/price-divergence-rule.md
index df0de45d0..a7ee46ad8 100644
--- a/docs/tutorials/en/price-divergence-rule.md
+++ b/docs/tutorials/en/price-divergence-rule.md
@@ -19,9 +19,7 @@ When a seller uses a marketplace to sell their products, sometimes there is a di
 
 To optimize the processing of orders with price difference errors, you can use the Order authorization flow and [configure a Price Divergence rule](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe). In the VTEX Admin, go to **Store Settings > Orders > Order Authorization**, or type **Order Authorization** in the search bar at the top of the page.
 
-<div class="alert alert-warning">
-Once the Price Divergence rule is created, it is applied to all marketplaces.
-</div>
+>⚠️ Once the Price Divergence rule is created, it is applied to all marketplaces.
 
 The Price Divergence rule is composed of one or more order authorization rules. Each authorization rule corresponds to a percentage range of the order price and can vary from 0% to 100%. You must associate one of three actions with each authorization rule:
 
@@ -33,9 +31,7 @@ The Price Divergence rule is composed of one or more order authorization rules.
 
 When the [Price Divergence rule configuration](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) was not made, orders with price divergence errors are automatically approved. This applies to VTEX marketplaces, external marketplaces, and certified connectors (partners), but not to [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex).
 
-<div class="alert alert-warning">
-When a seller is integrated with a native connector, Amazon, but has not <a href="https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configured a Price Divergence rule</a>, orders with price difference errors remain pending until the rule is created. You can track them in your VTEX Admin by clicking on <b>Marketplace > Connections > Orders</b>.
-</div>
+>⚠️ When a seller is integrated with a native connector, Amazon, but has not [configured a Price Divergence rule](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), orders with price difference errors remain pending until the rule is created. You can track them in your VTEX Admin by clicking on **Marketplace > Connections > Orders**.
 
 Once the Price Divergence rule is created, orders from integrations with native connectors that have a price difference will be displayed in [All Orders](https://help.vtex.com/en/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi) page.
 
diff --git a/docs/tutorials/en/price-divergence-rules-beta.md b/docs/tutorials/en/price-divergence-rules-beta.md
index 049ed51de..af6a8b771 100644
--- a/docs/tutorials/en/price-divergence-rules-beta.md
+++ b/docs/tutorials/en/price-divergence-rules-beta.md
@@ -33,7 +33,7 @@ You can manage and manually approve orders via OMS or [VTEX DO](https://help.vte
 
 The default configuration in a price divergence rule is to `automatically deny` orders that present a divergence percentage from 0% to 30%. But you can change this configuration or even create new rules.
 
-<div class="alert alert-info">If you have a price divergence rule (Beta) configured, you no longer need to configure the Price Divergence field in the marketplace integration. If the Price Divergence field has already been configured in your integration, it will no longer be valid.</div>
+>ℹ️ If you have a price divergence rule (Beta) configured, you no longer need to configure the Price Divergence field in the marketplace integration. If the Price Divergence field has already been configured in your integration, it will no longer be valid.
 
 ## Configuring the price divergence rule (Beta)
 
@@ -84,10 +84,8 @@ You can approve orders with the status `Waiting for manual authorization` by:
 - [Manually authorizing orders in the OMS](#manually-authorizing-orders-in-the-oms)
 - [Authorizing orders via VTEX DO](#authorizing-orders-via-vtex-do)
 
-<div class="alert alert-warning">
-You must have permission from the account owner to authorize requests, otherwise, the following message will be displayed: 
-“You do not have authorization rules yet. Then all cases of divergences are automatically denied.”
-</div>
+>⚠️ You must have permission from the account owner to authorize requests, otherwise, the following message will be displayed: 
+> “You do not have authorization rules yet. Then all cases of divergences are automatically denied.”
 
 ### Manually authorizing orders in the OMS
 
diff --git a/docs/tutorials/en/product-list.md b/docs/tutorials/en/product-list.md
index 824023bf4..08cb0a81a 100644
--- a/docs/tutorials/en/product-list.md
+++ b/docs/tutorials/en/product-list.md
@@ -30,7 +30,7 @@ On the **Products** page, you can:
 
 By clicking on the `CREATE PRODUCT` button, you will be redirected to the page where you can add a new product to the catalog. Check out the article[ How to create a product](https://help.vtex.com/en/tutorial/how-to-create-a-product-beta--671zAWe0B9eCikzDu7kB1G) for more details.
 
-<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+>⚠️ The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.
 
 ## Searching for product
 
diff --git a/docs/tutorials/en/product-registration-fields.md b/docs/tutorials/en/product-registration-fields.md
index 661d34db1..87917c211 100644
--- a/docs/tutorials/en/product-registration-fields.md
+++ b/docs/tutorials/en/product-registration-fields.md
@@ -25,15 +25,16 @@ __Substitute words:__ synonyms of terms related to the name given to your depart
 
 __TextLink:__ used to create the product URL. Required field. For more information, read [How is a product URL set up?](https://help.vtex.com/en/tutorial/how-is-a-product-url-set-up--frequentlyAskedQuestions_368).
 
-<div class="alert alert-danger">
-  <p>When filling in the product’s <b>textLink</b>, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ When filling in the product’s **textLink**, avoid using the following reserved words, as this can hinder your store's performance and interfere with the functioning of VTEX Admin pages. See the list of reserved words below.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 __Page Title (Tag Title):__ text that is in the browser tab and corresponds to the title of the product page. This field is important for SEO.
 
@@ -73,9 +74,7 @@ Here's how to [create your product specifications](https://help.vtex.com/en/tuto
 
 If you have created any required product fields, the product can only be activated after this specification has been filled in.
 
-<div class="alert alert-info">
-If your product does not appear on your store's website after you have created it, check out the article <a href="https://help.vtex.com/pt/faq/why-is-the-product-not-shown-on-the-website--frequentlyAskedQuestions_382">Why is the product not shown on the website?</a> to understand how to solve this problem.
-</div>
+>ℹ️ If your product does not appear on your store's website after you have created it, check out the article [Why is the product not shown on the website?](https://help.vtex.com/pt/faq/why-is-the-product-not-shown-on-the-website--frequentlyAskedQuestions_382) to understand how to solve this problem.
 
 ### Learn more
 - [Products - Concept definition](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru)
diff --git a/docs/tutorials/en/products-and-skus-beta.md b/docs/tutorials/en/products-and-skus-beta.md
index c417193a9..4015f53c9 100644
--- a/docs/tutorials/en/products-and-skus-beta.md
+++ b/docs/tutorials/en/products-and-skus-beta.md
@@ -23,9 +23,7 @@ The **Products and SKUs** page allows you to view and manage the list of all pro
 
 ![products-skus-en](https://images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/f02b69940302cf42cf3eefd80ec56445/products-skus-en.png)
 
-<div class="alert alert-info">
-  <p>This page is only available to stores operating with the <a href="https://help.vtex.com/en/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">New VTEX Admin</a>. To access this page and be part of the new experience, join the New VTEX Admin <a href="https://content.vtex.com/participe-do-programa-beta-en/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">Beta program</a>.</p>
-</div>
+>ℹ️ This page is only available to stores operating with the [New VTEX Admin](https://help.vtex.com/en/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa). To access this page and be part of the new experience, join the New VTEX Admin [Beta program](https://content.vtex.com/participe-do-programa-beta-en/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta).
 
 This page allows you to: 
 
@@ -83,9 +81,7 @@ The list of products can be filtered according to your needs. You can use the fo
 
 Select the desired filters and click `Apply` to filter the products. To cancel the selection, click `Clear`.
 
-<div class="alert alert-warning">
-  <p>You cannot filter products by <a href="https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w">seller</a> or pre-sale date in this Catalog version.</p>
-</div>
+>⚠️ You cannot filter products by [seller](https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w) or pre-sale date in this Catalog version.
 
 ## Tracking product status
 
diff --git a/docs/tutorials/en/promotions-beta.md b/docs/tutorials/en/promotions-beta.md
index e6958a9e4..7a08115c1 100644
--- a/docs/tutorials/en/promotions-beta.md
+++ b/docs/tutorials/en/promotions-beta.md
@@ -15,9 +15,7 @@ legacySlug: promotions-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class="alert alert-danger">
-<p>This feature will be discontinued on May 16, 2022. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>❗ This feature will be discontinued on May 16, 2022. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.
 
 The VTEX platform allows you to optimally and practically add different promotion types suited for different scenarios. Through a centralized interface for managing promotions, your store can offer more benefits focused on customer attraction and retention.
 
@@ -98,9 +96,7 @@ This effect generates a total discount on the value of the product that is defin
 - __SKUs__: option that allows you to select the SKU of the giveaway.
 - __Maximum quantity per purchase__: allows you to choose the maximum number of giveaways per order.
 
-<div class="alert alert-warning">
-  <p>You must add prices for all <b>giveaway products</b>, even though they are given for free.</p>
-</div>
+>⚠️ You must add prices for all **giveaway products**, even though they are given for free.
 
 #### Shipping
 - __Discount type__
@@ -126,9 +122,7 @@ This effect generates a total discount on the value of the product that is defin
   - __UTM source__.
   - __ZIP code range__.
 
-<div class="alert alert-info">
-<p>If you want to link an <a href= "https://help.vtex.com/en/tutorial/como-criar-cupom--tutorials_319?&utm_source=autocomplete">existing coupon</a> to the new promotion, you must select UTM Campaign and UTM Source and inform the coupon codes. </p>
-</div>
+>ℹ️ If you want to link an <a href= "https://help.vtex.com/en/tutorial/como-criar-cupom--tutorials_319?&utm_source=autocomplete">existing coupon</a> to the new promotion, you must select UTM Campaign and UTM Source and inform the coupon codes.
 
 ### Coupons
 If you want to create a new coupon linked to the promotion, click on __NEW COUPON__ and fill in the following fields:
@@ -141,15 +135,11 @@ By clicking on __Advanced Settings__, you can also configure an additional field
 
 - __Limit use__: limits the number of times the coupon can be used.
 
-<div class="alert alert-warning">
-<p>To save this new coupon, click on the <b>OK</b> button. If you close the <b>NEW COUPON</b> window without saving the changes, the coupon will not be created.</p>
-</div>
+>⚠️ To save this new coupon, click on the **OK** button. If you close the **NEW COUPON** window without saving the changes, the coupon will not be created.
 
 When you create a new coupon for the new promotion, the coupon will also be displayed in the __Coupons__ tab of the __Promotions & Taxes__ module. In addition, your UTM Source and/or UTM Campaign conditions will be automatically linked to the new promotion in the __Specific customers__ filter.
 
-<div class="alert alert-warning">
-<p>If you change the UTM Source and UTM Campaign conditions in the <b>Specific customers</b> filter settings <b>after</b> creating the coupon, it will be deleted.</p>
-</div>
+>⚠️ If you change the UTM Source and UTM Campaign conditions in the **Specific customers** filter settings **after** creating the coupon, it will be deleted.
 
 ### Restrictions
 - __Limit use in the store__: limits the number of times the promotion can be used in the store.
diff --git a/docs/tutorials/en/promotions-simulator-beta.md b/docs/tutorials/en/promotions-simulator-beta.md
index e490c89b0..0c61cc451 100644
--- a/docs/tutorials/en/promotions-simulator-beta.md
+++ b/docs/tutorials/en/promotions-simulator-beta.md
@@ -15,9 +15,7 @@ legacySlug: promotions-simulator-beta
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-<div class="alert alert-warning">
-  <p>Users must have an authorized <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> that grants access to the <strong>Promotions</strong> module in the VTEX Admin to access the <strong>Promotion Simulator</strong>.</p>
-</div>
+>⚠️ Users must have an authorized [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) that grants access to the **Promotions** module in the VTEX Admin to access the **Promotion Simulator**.
 
 The **Promotion Simulator** is a tool that allows you to view not only the promotions created in the VTEX platform and applied to the shopping cart but also their activation conditions. You can also test the application of promotions before activating them, including scheduled and inactive promotions.
 
@@ -47,9 +45,7 @@ The **Promotion Simulator** interface displays the following information:
 | **Total** | Total price that will be charged for the product, considering the promotion discounts and the number of items. |
 | **Discount** | Discount status in the cart, which can be: `Applied` or `Not applied`. The `Applied` status indicates that at least one promotion has been applied to the product.  |
 
-<div class="alert alert-info">
-  <p>You can send us your feedback about your experience using the <strong>Promotion Simulator</strong> from the megaphone <i class="fas fa-megaphone"></i> button in the right corner of the screen.</p>
-</div>
+>ℹ️ You can send us your feedback about your experience using the **Promotion Simulator** from the megaphone <i class="fas fa-megaphone"></i> button in the right corner of the screen.
 
 ### Updating the simulator
 
@@ -92,9 +88,7 @@ To run a simulation, follow the instructions below:
 
     After running the simulation, you will see the results of the selected promotions. To verify if the tested promotions were applied to the cart items in the simulation, you can check the status of the **Discount** column or click the respective product.
 
-<div class="alert alert-info">
-  <p>You can apply promotions to products that already have an active promotion. However, please note that not all promotions can be applied. The VTEX system will always choose the most favorable one for your store customers, considering factors such as the total price of the items or the shipping cost.</p>
-</div>
+>ℹ️ You can apply promotions to products that already have an active promotion. However, please note that not all promotions can be applied. The VTEX system will always choose the most favorable one for your store customers, considering factors such as the total price of the items or the shipping cost.
 
 ### Learn more
 
diff --git a/docs/tutorials/en/promotions-simulator.md b/docs/tutorials/en/promotions-simulator.md
index b54965c02..b187c090b 100644
--- a/docs/tutorials/en/promotions-simulator.md
+++ b/docs/tutorials/en/promotions-simulator.md
@@ -15,9 +15,7 @@ legacySlug: promotions-simulator
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class="alert alert-info">
-<p>This module is in beta, which means we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>ℹ️ This module is in beta, which means we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.
 
 The **Promotions Simulator** allows you to view the promotions applied to shopping carts and their conditions. With several possibilities for setting up promotions, it is important to have visibility into their [competition](https://help.vtex.com/en/tutorial/understanding-competition-of-promotions--tutorials_2270) and [combination](https://help.vtex.com/en/tutorial/understanding-competition-of-promotions--tutorials_2270#accumulation) during purchase and how they work.
 
diff --git a/docs/tutorials/en/qr-code-suiteshare.md b/docs/tutorials/en/qr-code-suiteshare.md
index 51bceb934..0bb77cd18 100644
--- a/docs/tutorials/en/qr-code-suiteshare.md
+++ b/docs/tutorials/en/qr-code-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: qr-code-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/querying-data-on-master-data.md b/docs/tutorials/en/querying-data-on-master-data.md
index 0ec289654..4c685c0dc 100644
--- a/docs/tutorials/en/querying-data-on-master-data.md
+++ b/docs/tutorials/en/querying-data-on-master-data.md
@@ -15,4 +15,4 @@ legacySlug: querying-data-on-master-data
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/rdstation-crm-suiteshare.md b/docs/tutorials/en/rdstation-crm-suiteshare.md
index d2523b25d..4db08abed 100644
--- a/docs/tutorials/en/rdstation-crm-suiteshare.md
+++ b/docs/tutorials/en/rdstation-crm-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: rdstation-crm
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/rdstation-suiteshare.md b/docs/tutorials/en/rdstation-suiteshare.md
index 3db27d2db..c97c78ffc 100644
--- a/docs/tutorials/en/rdstation-suiteshare.md
+++ b/docs/tutorials/en/rdstation-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: rdstation
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/received-skus-beta.md b/docs/tutorials/en/received-skus-beta.md
index f69ccd278..a473ac75d 100644
--- a/docs/tutorials/en/received-skus-beta.md
+++ b/docs/tutorials/en/received-skus-beta.md
@@ -56,9 +56,7 @@ To check all the specifications of a product, click the name of the product. Thi
 
 The __Issues__ tab contains all the offers that haven't been approved because they have issues that need to be corrected by the seller. The filters, actions, and identification fields of the Issues tab are similar to the ones in the __[Pending](#pending)__ tab.  
 
-<div class="alert alert-info">
- The <b>Issues</b> tab doesn't have the option to request a correction.
-</div>
+>ℹ️ The **Issues** tab doesn't have the option to request a correction.
 
 To identify the issue of an offer, simply click the name of the product. This will open a window with the product information, an error message, and the offer reviewer.  
 
@@ -86,9 +84,7 @@ Each row in the list represents a product and contains the following information
 - __Seller:__ Name of the seller who sent the offer.  
 - __Submitted Date:__ Date when the offer was sent to the marketplace.  
 
-<div class="alert alert-info">
-The offers in this tab are being evaluated by Matcher and Offer Quality or autoApprove, if they're configured. After evaluation, the offer can be sent to the <b>Pending, Issues, Approved, or Blocked</b> tabs, depending on the requirements.
-</div>
+>ℹ️ The offers in this tab are being evaluated by Matcher and Offer Quality or autoApprove, if they're configured. After evaluation, the offer can be sent to the **Pending, Issues, Approved, or Blocked** tabs, depending on the requirements.
 
 ### Blocked  
 
@@ -127,17 +123,13 @@ In this case, the items will be sorted in ascending or descending order when you
 
 All the SKUs displayed in the list are available for cataloging. However, we recommend [mapping the categories and brands](https://help.vtex.com/pt/tutorial/mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta--6NU8LwR6i0tTb8nk30bnbE) before this step to streamline the cataloging process.  
 
-<div class="alert alert-warning">
-The offers in the Pending tab are only available for 30 days. After this period, they automatically expire and the seller will need to submit them again.
-</div>
+>⚠️ The offers in the Pending tab are only available for 30 days. After this period, they automatically expire and the seller will need to submit them again.
 
 ### Cataloging options
 
 To catalog an offer, access the __Received SKUs__ page on the VTEX Admin by going to __Marketplace > Received SKUs__ or typing __Received SKUs__ in the Admin search bar.  
 
-<div class="alert alert-info">
-All the offers on the Pending tab can be cataloged individually or in bulk.
-</div>
+>ℹ️ All the offers on the Pending tab can be cataloged individually or in bulk.
 
 The available cataloging actions are:  
 
@@ -148,9 +140,7 @@ The available cataloging actions are:
 3. 	Complete the Category and Brand fields for each product. If the mapping was previously completed, the fields will be filled automatically.  
 4. 	Click `Approve`.  
 
-<div class="alert alert-info">
-This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
-</div>
+>ℹ️ This action can be applied in the offer tabs **Pending** and **Issues**.
 
 ![received-skus-create-new-product-en](https://images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/2d18fb18e7711cb4cd341795ac0820b4/received-skus-create-new-product-en.png)
 
@@ -167,9 +157,7 @@ Imagine that a marketplace already has the White Shirt SKU in S, M, and L, and a
 
 Creating a new link groups the new sizes with the existing ones. After this, the product will have XS, S, M, L, and XL as available sizes.  
 
-<div class="alert alert-info">
-This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
-</div>  
+>ℹ️ This action can be applied in the offer tabs **Pending** and **Issues**.  
 
 ![received-skus-bind-to-product-en](https://images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/fc02d18fe2771b0603f861f8516ab7ae/received-skus-bind-to-product-en.png)
 
@@ -186,9 +174,7 @@ A possible use case would be a marketplace that has Phone XYZ with a 128 GB memo
 
 Now, let's say the marketplace received the same 128 GB SKU from Seller 2. To avoid duplicates in the catalog, the marketplace would have to link these two SKUs.  
 
-<div class="alert alert-info">
-This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
-</div>
+>ℹ️ This action can be applied in the offer tabs **Pending** and **Issues**.
 
 ![received-skus-bind-to-sku-en](https://images.ctfassets.net/alneenqid6w5/2326FaqSqhPfQ0qeiD8KWE/8bc6c9b98e03afe02252bd69342005d1/received-skus-bind-to-sku-en.png)
 
@@ -201,9 +187,7 @@ This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>.
 
 When the marketplace blocks a SKU, it won't be included with other submitted offers the next time that the seller sends products. A SKU can be unblocked using a REST API if the marketplace wants to receive it as a suggestion from the seller. To learn more about SKU approval, see [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).  
 
-<div class="alert alert-info">
-This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>. Blocked offers can be viewed in the <b>Blocked</b> tab.
-</div>
+>ℹ️ This action can be applied in the offer tabs **Pending** and **Issues**. Blocked offers can be viewed in the **Blocked** tab.
 
 ![received-skus-reject-and-block-en](https://images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/247d5dcfb554755d091b1367d84db2d5/received-skus-reject-and-block-en.png)
 
@@ -214,9 +198,7 @@ This action can be applied in the offer tabs <b>Pending</b> and <b>Issues</b>. B
 3. 	Enter the information that needs correction in the Corrections field.  
 4. 	Click Reject.  
 
-<div class="alert alert-info">
-	<p>This action can be applied in the offer tab <b>Pending</b>. The offers that need correction will show in the <b>Issues</b> tab.</p>
-</div>  
+>ℹ️ This action can be applied in the offer tab **Pending**. The offers that need correction will show in the **Issues** tab.  
 
 ![received-skus-reject-for-correction-en](https://images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/7d456cf95d5a4ed7011accdfe0550fba/received-skus-reject-for-correction-en.png)
 
diff --git a/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
index c57d0f9d1..3dd2f61cb 100644
--- a/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
+++ b/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -86,9 +86,7 @@ We recommend creating a new phone number exclusively for linking to WhatsApp Bus
   <li>Paste the phone number you copied in the previous step, select the option <strong>SMS</strong>, and click <code>Send Code</code>.</li>
 </ol>
 
-<div class="alert alert-warning">
-  The number generated may be American, but if your Facebook page is verified, your customers will see your company name. If it is not verified, we recommend following the <a href="https://www.facebook.com/business/help/2058515294227817?id=180505742745347">verification process with Meta</a>.
-</div>
+>⚠️ The number generated may be American, but if your Facebook page is verified, your customers will see your company name. If it is not verified, we recommend following the [verification process with Meta](https://www.facebook.com/business/help/2058515294227817?id=180505742745347).
 
 <ol start="13">
   <li>Copy the verification code displayed in the VTEX Admin.</li>
@@ -106,9 +104,7 @@ We recommend creating a new phone number exclusively for linking to WhatsApp Bus
   <li>Click <code>Complete</code>.</li>
 </ol>
 
-<div class="alert alert-warning">
-Once an abandoned checkout recovery campaign has been activated, it can take up to 48 hours for analytics metrics to start being displayed.
-</div>
+>⚠️ Once an abandoned checkout recovery campaign has been activated, it can take up to 48 hours for analytics metrics to start being displayed.
 
 <div class = "alert alert-info">
 Learn more about <a href="https://help.vtex.com/en/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">WhatsApp AI Campaigns management and details</a>.
diff --git a/docs/tutorials/en/redirect-from-other-addresses.md b/docs/tutorials/en/redirect-from-other-addresses.md
index 4d3cc2448..6c80ed58e 100644
--- a/docs/tutorials/en/redirect-from-other-addresses.md
+++ b/docs/tutorials/en/redirect-from-other-addresses.md
@@ -31,9 +31,7 @@ You can configure redirects in different ways; one of the most popular is using[
 
 Below are instructions for setting up redirects to your store's main address using the [Redirect Center](http://redirect.center/) tool.
 
-<div class="alert alert-warning">
-  <p><a href="http://redirect.center/">Redirect Center</a> is not a service provided by VTEX and does not support HTTPS. While there are other similar services available, VTEX does not endorse any specific one. VTEX is not liable for any issues caused by external redirect services.</p>
-</div>
+>⚠️ [Redirect Center](http://redirect.center/) is not a service provided by VTEX and does not support HTTPS. While there are other similar services available, VTEX does not endorse any specific one. VTEX is not liable for any issues caused by external redirect services.
 
 ### Address redirects without a subdomain (such as www)
 
diff --git a/docs/tutorials/en/redirection-from-other-addresses.md b/docs/tutorials/en/redirection-from-other-addresses.md
index acf7288bf..98131987f 100644
--- a/docs/tutorials/en/redirection-from-other-addresses.md
+++ b/docs/tutorials/en/redirection-from-other-addresses.md
@@ -28,9 +28,7 @@ You can also use DNS redirection, as provided by several services, including dom
 
 To perform a DNS redirection in a simple manner, there are instructions below on how to use the [redirect.center](http://redirect.center/) service.
 
-<div class="alert alert-warning">
-Note that Redirect Center is not a VTEX service and does not work with HTTPS. There are other similar services, but VTEX does not recommend any specific one. VTEX is not responsible for problems caused by external redirect services.
-</div>
+>⚠️ Note that Redirect Center is not a VTEX service and does not work with HTTPS. There are other similar services, but VTEX does not recommend any specific one. VTEX is not responsible for problems caused by external redirect services.
 
 This guide contains the instructions so you can redirect other domains to your store's main address. See this other article to learn [how to configure access without www](https://help.vtex.com/en/tutorial/configurando-acesso-sem-www--tutorials_4278).
 
diff --git a/docs/tutorials/en/redirects.md b/docs/tutorials/en/redirects.md
index 2023a30d1..65e7683d6 100644
--- a/docs/tutorials/en/redirects.md
+++ b/docs/tutorials/en/redirects.md
@@ -17,9 +17,7 @@ subcategory: 1wvyJwJhKgewxGeAGCVmM6
 
 The **Redirects** feature directs customers to another page, either internal or external to the store. This redirection is done in the search area of your storefront, using terms or filters selected by the customer. This way, one of the advantages of the Redirects feature is to contemplate communication scenarios that are not covered by the store's catalog search, such as redirecting a search for a brand to its promotional page.
 
-<div class="alert alert-warning">
-<p>This feature is available in VTEX Intelligent Search: Multilanguage. To learn more, please refer to our article VTEX Intelligent Search: Multilanguage settings (Beta).</p>
-</div>
+>⚠️ This feature is available in VTEX Intelligent Search: Multilanguage. To learn more, please refer to our article VTEX Intelligent Search: Multilanguage settings (Beta).
 
 ## How redirects work
 
diff --git a/docs/tutorials/en/regionalization-beta.md b/docs/tutorials/en/regionalization-beta.md
index f7ad68845..04410806a 100644
--- a/docs/tutorials/en/regionalization-beta.md
+++ b/docs/tutorials/en/regionalization-beta.md
@@ -15,9 +15,7 @@ legacySlug: regionalization-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-<p>This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/en-us/requests).
 
 Regionalization is a feature of [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) that allows for the optimization of search results according to the availability of sellers in the customer's region. To install and configure VTEX Intelligent Search in your store, read our article about [Search](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search).
 
@@ -36,9 +34,7 @@ To start using the Regionalization feature, you must follow the steps described
 2. [Request to activate the Regionalization feature](#2-request-to-activate-the-regionalization-feature)
 3. [Configuration in VTEX IO](#3-configuration-in-vtex-io)
 
-<div class="alert alert-warning">
-  <p>While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.</p>
-</div>
+>⚠️ While regionalized stores display only products available in a certain region on the product list page, filters do not take regionalization into account. This means that store customers may select filter values that result in products not being available in their region.
 
 ## 1. Seller configuration
 
diff --git a/docs/tutorials/en/registering-a-products-base-price.md b/docs/tutorials/en/registering-a-products-base-price.md
index 0764492a6..8a066f7fe 100644
--- a/docs/tutorials/en/registering-a-products-base-price.md
+++ b/docs/tutorials/en/registering-a-products-base-price.md
@@ -15,9 +15,7 @@ legacySlug: registering-a-products-base-price
 subcategory: 4id9W3RDyw02CasOm2C2iy
 ---
 
-<div class="alert alert-info">
-This article refers to the latest version of VTEX Pricing. If your store is not yet in this new version, you can request the migration by contacting our support team.
-</div>
+>ℹ️ This article refers to the latest version of VTEX Pricing. If your store is not yet in this new version, you can request the migration by contacting our support team.
 
 The __base price__ is the basic selling price of a product. It comprises the __cost price__ and the __markup__ wanted in the sale of the product.
 
@@ -30,9 +28,7 @@ To set the base price, follow the steps below:
 - In the __Markup__ field, fill in the profit margin to be obtained by selling this SKU.
 - The base price will be calculated according to the data provided in the previous steps.
 
-<div class="alert alert-info">
-If the SKU has a list price, you can add this information by clicking <strong>+ Set list price</strong>.
-</div>
+>ℹ️ If the SKU has a list price, you can add this information by clicking **+ Set list price**.
 
 ## Related articles
 
diff --git a/docs/tutorials/en/registering-geolocation.md b/docs/tutorials/en/registering-geolocation.md
index 65eb3c308..5ba93b66a 100644
--- a/docs/tutorials/en/registering-geolocation.md
+++ b/docs/tutorials/en/registering-geolocation.md
@@ -32,9 +32,7 @@ Access the [Generate your polygons with geojson.io](http://geojson.io/#map=2/20.
 
 This JSON will be used to add the polygon to the platform, that will translate that language to understand which Zip Codes are included in your area.
 
-<div class="alert alert-danger">
-When generating a polygon, it is not possible to delimit overlapping areas, meaning it is not possible to overlap geographic coordinates.
-</div>
+>❗ When generating a polygon, it is not possible to delimit overlapping areas, meaning it is not possible to overlap geographic coordinates.
 
 ## How to add a polygon
 
@@ -60,8 +58,7 @@ Example:
 
 Done! Now just use this same ID in the freight spreadsheet, at the **PolygonName** column. 
 
-<div class="alert alert-warning">It's important to pay attention to the filling, because this time the carrier will not use the <strong>ZipCodeStart</strong> and <strong>ZipCodeStart</strong> columns, which should be left blank.
-</div>
+>⚠️ It's important to pay attention to the filling, because this time the carrier will not use the **ZipCodeStart** and **ZipCodeStart** columns, which should be left blank.
 
 On the [Checkout tab](https://help.vtex.com/en/tutorial/geolocalizacao-no-checkout/) at **Store Settings > Storefront > Checkout**, the API Key field must be filled in with the same key that was used to enable geolocation.
 
diff --git a/docs/tutorials/en/registering-holidays.md b/docs/tutorials/en/registering-holidays.md
index 7393c5aaa..c09d5c121 100644
--- a/docs/tutorials/en/registering-holidays.md
+++ b/docs/tutorials/en/registering-holidays.md
@@ -34,9 +34,7 @@ To set up the Holidays, follow the steps below:
 3. In the **Weekends and Holidays** section, make sure the option `Holiday delivery` disabled <i class="fas fa-toggle-off"></i>.
 4. Click on `Save`.
 
-<div class="alert alert-info">
-You may configure holidays for the years to come.
-</div>
+>ℹ️ You may configure holidays for the years to come.
 
 ## How to consider holidays when calculating shipping time
 
@@ -57,9 +55,7 @@ From a technical standpoint, holidays are considered in the `shippingEstimateDat
 2. Tuesday (02/06) is a holiday.
 3. The estimated delivery date will be Thursday (02/08), as Tuesday will not be considered a business day.
 
-<div class="alert alert-warning">
-There is one exception in which the holiday counts as a business day: when the customer places an order on a holiday and the carrier has shipping hours set (<a href="https://help.vtex.com/en/tutorial/carrier-working-hours--2oGpbInIgdxSWUi3TZjdCS">Shipping Window</a>) for that same day.
-</div>
+>⚠️ There is one exception in which the holiday counts as a business day: when the customer places an order on a holiday and the carrier has shipping hours set ([Shipping Window](https://help.vtex.com/en/tutorial/carrier-working-hours--2oGpbInIgdxSWUi3TZjdCS)) for that same day.
 
 ### Example 2
 
diff --git a/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
index 6226e7d03..d89dced5e 100644
--- a/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/en/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -49,17 +49,13 @@ You can do a multiplication to calculate the desired discount percentage using [
 
 To indicate the order in which calculations should be done, write the calculation which comes first between parenthesis `()`. For example: If a store wants to apply a 40% discount on the total price of the order plus the shipping cost, the formula must be `(total + freight) * 0.4`.
 
-<div class="alert alert-info">
-  <p>You must always use the dot (<code>.</code>) as a decimal separator.</p>
-</div>
+>ℹ️ You must always use the dot (`.`) as a decimal separator.
 
 ## Functions
 
 If you want to [limit the discount](#limiting-the-discount), you can use the `min` function. Use the `max` function if you want to [prioritize the highest discount possible](#prioritizing-the-highest-discount-possible). Read on for more details about these functions.
 
-<div class="alert alert-info">
-<p>When using functions, there must be a space between the function and the opening parenthesis. For example: <code>min (total * 0.2, 10)</code>.</p>
-</div>
+>ℹ️ When using functions, there must be a space between the function and the opening parenthesis. For example: `min (total * 0.2, 10)`.
 
 ### Limiting the discount
 
diff --git a/docs/tutorials/en/releases-module-beta.md b/docs/tutorials/en/releases-module-beta.md
index 7a462055e..f83790af5 100644
--- a/docs/tutorials/en/releases-module-beta.md
+++ b/docs/tutorials/en/releases-module-beta.md
@@ -186,9 +186,7 @@ Another way to publish is to go to the release details page, following the steps
 
 To delete a release, follow the step-by-step instructions below: 
 
-<div class="alert alert-danger">
-Deleted releases cannot be recovered. The updates included in the release remain, but they are no longer grouped together.
-</div>
+>❗ Deleted releases cannot be recovered. The updates included in the release remain, but they are no longer grouped together.
 
 1. In the VTEX Admin, access **Store Settings > Releases**.
 2. On the line corresponding to the desired release, click the <i class="fas fa-ellipsis-v"></i> menu icon. 
diff --git a/docs/tutorials/en/releases-overview.md b/docs/tutorials/en/releases-overview.md
index f27362a57..2f7c7dbc4 100644
--- a/docs/tutorials/en/releases-overview.md
+++ b/docs/tutorials/en/releases-overview.md
@@ -15,15 +15,11 @@ legacySlug: releases-overview
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>The <strong>Releases</strong> is in beta version, which means we are working to improve it. This feature is only available for stores using <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ The **Releases** is in beta version, which means we are working to improve it. This feature is only available for stores using [FastStore](https://www.faststore.dev/).
 
 The **Releases** menu allows you to manage groups of related changes to coordinate the planning, creation, scheduling, and publishing of changes in your store. The changes or groups of changes that **Releases** can publish together are known as [releases](https://help.vtex.com/en/tutorial/planner-release-concept-beta--4pWhQTXG0aIIsi2TYxxRkZ).
 
-<div class="alert alert-warning">
-  <p>In the beta version, releases must be <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>-related, because other VTEX platform modules are not yet included. To use the <strong>Releases</strong>, you must configure the CMS as described in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ In the beta version, releases must be [CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2)-related, because other VTEX platform modules are not yet included. To use the **Releases**, you must configure the CMS as described in [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 Check out below the pages available in the **Releases** menu.
 
diff --git a/docs/tutorials/en/relevance-rules.md b/docs/tutorials/en/relevance-rules.md
index ec9a4a041..e1cb06c3e 100644
--- a/docs/tutorials/en/relevance-rules.md
+++ b/docs/tutorials/en/relevance-rules.md
@@ -39,9 +39,7 @@ The information considered for the relevance is:
 
 The set of weights and criteria distribution generates a score for the product, which determines its position in the search result ranking.
 
-<div class="alert alert-warning">
-  <p>IIf you want to use priority criteria, we recommend adding only one criterion in this field. Adding more criteria compromises the ordering or search results, since only the first criterion will be considered.</p>
-</div>
+>⚠️ IIf you want to use priority criteria, we recommend adding only one criterion in this field. Adding more criteria compromises the ordering or search results, since only the first criterion will be considered.
 
 So you can tailor the behavior of the search results to a specific strategy.
 
diff --git a/docs/tutorials/en/remarketing.md b/docs/tutorials/en/remarketing.md
index 5bd8bd8c5..58f617673 100644
--- a/docs/tutorials/en/remarketing.md
+++ b/docs/tutorials/en/remarketing.md
@@ -15,6 +15,4 @@ legacySlug: remarketing
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
index 35518e8d3..36942aeff 100644
--- a/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/en/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -85,6 +85,4 @@ If you want, you can also include the following functions in the script:
 - Automatically expire cookies containing special characters
 - Trigger page reload using the function `window.location.reload()`  
 
-<div class="alert alert-warning">
-  Deleting cookies via script is not a permanent solution. As described in the <b>Disabling cookies with special characters</b> section, you must identify the source and stop sending cookies with special characters.
-</div>
+>⚠️ Deleting cookies via script is not a permanent solution. As described in the **Disabling cookies with special characters** section, you must identify the source and stop sending cookies with special characters.
diff --git a/docs/tutorials/en/request-deletion-of-customer-personal-data-under-international-data-privacy.md b/docs/tutorials/en/request-deletion-of-customer-personal-data-under-international-data-privacy.md
index 6b9df5453..89bb06d53 100644
--- a/docs/tutorials/en/request-deletion-of-customer-personal-data-under-international-data-privacy.md
+++ b/docs/tutorials/en/request-deletion-of-customer-personal-data-under-international-data-privacy.md
@@ -32,9 +32,7 @@ Configuring the data in Master Data is the first step in deleting sensitive data
 
 Privacy laws stipulate that personal data must not be shared or unduly exposed. Therefore, settings are required to ensure protection of that data. 
 
-<div class="alert alert-warning">
-Settings that are saved cannot be reversed.
-</div>
+>⚠️ Settings that are saved cannot be reversed.
 
 To perform the configuration, follow the steps below: 
 
@@ -54,9 +52,7 @@ To perform the configuration, follow the steps below:
 
 Once you have configured the data in Master Data, you must request the deletion of your customers' personal data from the VTEX systems by opening a ticket with the [VTEX Support](https://help.vtex.com/en/support).
 
-<div class="alert alert-warning">
-Please request the deletion of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
-</div>
+>⚠️ Please request the deletion of data for only one account, i.e. one shopper email per ticket. If you include more than one email, the ticket will be returned.
 
 To request the deletion of customer personal data, follow the steps below.
 
diff --git a/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
index 542ae575a..be93bdb53 100644
--- a/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
+++ b/docs/tutorials/en/responsibilities-in-the-vtex-ecosystem.md
@@ -162,9 +162,7 @@ Even so, there may be strategic partner stores for your business that operate ou
 
 For merchants operating in this scenario, it's important to understand the responsibilities of each player involved in the operation, as detailed below.
 
-<div class="alert alert-warning">
-  <p>The following sections consider a store already integrated with an external marketplace via an external connector. Learn how to integrate your VTEX Catalog with an external connector for the first time, go to the <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Catalog Integration</a> guide.</p>
-</div>
+>⚠️ The following sections consider a store already integrated with an external marketplace via an external connector. Learn how to integrate your VTEX Catalog with an external connector for the first time, go to the [Catalog Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word) guide.
 
 ### Updating or sending new products and SKUs
 
diff --git a/docs/tutorials/en/returning-order-items.md b/docs/tutorials/en/returning-order-items.md
index 07c1a39e4..ba8984915 100644
--- a/docs/tutorials/en/returning-order-items.md
+++ b/docs/tutorials/en/returning-order-items.md
@@ -35,12 +35,13 @@ To return order items, follow the steps below:
 
 ![Returning order items](https://drive.google.com/uc?export=download&id=1T8YBwjDEQh3sGnpAybVkpuYqKjPy8zjQ)
 
-<div class="alert alert-warning">
-Please note that:
-<ul>
-<li>Returning a SKU in the Orders management module does not update its available inventory quantity. The store must update the number of items in <a href="https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139">Inventory management</a>.</li>
-<li>The number of the return invoice must be different from the sales invoice. </li>
-<li>Once the order is returned, the platform notifies the payment system to <a href="https://help.vtex.com/en/tutorial/como-funciona-estorno-quando-ha-devolucao-do-item">refund</a> the order.</li>
-<li>You can only return orders that contain at least one invoice on the platform.</li>
-</ul>
-</div>
+>⚠️ Please note that:
+>
+> *Returning a SKU in the Orders management module does not update its available inventory quantity. The store must update the number of items in [Inventory management](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+>
+> *The number of the return invoice must be different from the sales invoice.
+>
+> *Once the order is returned, the platform notifies the payment system to [refund](https://help.vtex.com/en/tutorial/como-funciona-estorno-quando-ha-devolucao-do-item) the order.
+>
+> *You can only return orders that contain at least one invoice on the platform.
+> 
diff --git a/docs/tutorials/en/risk-assessment.md b/docs/tutorials/en/risk-assessment.md
index 5b7fae382..bd18abc72 100644
--- a/docs/tutorials/en/risk-assessment.md
+++ b/docs/tutorials/en/risk-assessment.md
@@ -45,9 +45,7 @@ Some security information is restricted to VTEX Admin users, and it's not availa
 
 <iframe src="https://help.vtex.com/insertaccountname?id=7AmPOGXykmE9SYyYDzdAZ4" title="Enter your account name and click the button." frameBorder="0" width="400" height="50"></iframe>
 
-<div class="alert alert-warning">
-  If you are having dificulty accessing the FAQs, try installing the latest version of the app <code>vtex.admin-docs</code> using <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">VTEX CLI</a> and repeating the process.
-</div>
+>⚠️ If you are having dificulty accessing the FAQs, try installing the latest version of the app `vtex.admin-docs` using [VTEX CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) and repeating the process.
 
 ## FAQ - Security
 
diff --git a/docs/tutorials/en/roles.md b/docs/tutorials/en/roles.md
index 66b5c8774..38c3c44bd 100644
--- a/docs/tutorials/en/roles.md
+++ b/docs/tutorials/en/roles.md
@@ -39,9 +39,7 @@ The page displays a list of all roles added to the account and their respective
 
 In a newly created account, only the *Owner (Admin Super)* role will be listed. This role gives the user unrestricted access to all native resources of the platform.
 
-<div class="alert alert-warning">
-  <p>The number of users with the <em>Owner (Admin Super)</em> role should be as few as possible. In addition, make sure there is visibility and control over who is granted this access.</p>
-</div>
+>⚠️ The number of users with the *Owner (Admin Super)* role should be as few as possible. In addition, make sure there is visibility and control over who is granted this access.
 
 ## Creating a role
 
@@ -59,9 +57,7 @@ You can edit the resources and users associated with a role. To do so, click ⫶
 
 To delete a role, click `⫶` in the row of the role you want to delete, and then click <i class="far fa-trash-alt"></i> `Delete`.
 
-<div class="alert alert-warning">
-  <p>By deleting a role, users associated with that role will lose access to the <a href="https://help.vtex.com/entutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager resources</a> from the deleted role, unless they are also assigned other roles with the same permissions.</p>
-</div>
+>⚠️ By deleting a role, users associated with that role will lose access to the [License Manager resources](https://help.vtex.com/entutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) from the deleted role, unless they are also assigned other roles with the same permissions.
 
 ## Learn more
 
diff --git a/docs/tutorials/en/sales-associate-code-field-at-checkout.md b/docs/tutorials/en/sales-associate-code-field-at-checkout.md
index 4c8d6bee2..bbf515827 100644
--- a/docs/tutorials/en/sales-associate-code-field-at-checkout.md
+++ b/docs/tutorials/en/sales-associate-code-field-at-checkout.md
@@ -20,9 +20,7 @@ On VTEX, you can create a field to add the sales associate code at Checkout. It
 - Give exclusive discounts to the customer.
 - Manage your sales associates' performance, collecting data such as the number of sales / average ticket per sales associate and sales commission ranking.
 
-<div class="alert alert-warning">
-  The <b>sales associate code</b>  field does not replace the <b>discount coupon</b> field (native on the VTEX platform). By completing the settings outlined in this article, both can be used to give discounts.
-</div>
+>⚠️ The **sales associate code**  field does not replace the **discount coupon** field (native on the VTEX platform). By completing the settings outlined in this article, both can be used to give discounts.
 
 To create the field and add it to the Checkout page of your store, you need to complete three steps:
 
@@ -55,9 +53,7 @@ After creating the salesassociatecode entity, you need to link it to a promotion
 1. In the VTEX Admin, go to **Promotions > Promotions**, or type **Promotions** in the search bar at the top of the page.
 2. Create a new [regular promotion](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N). Complete the **Promotion overview** and the **To which items will this promotion apply?** fields.
 
-<div class="alert alert-info">
-  Callout Information: If you want to use the sales associate code field to give a discount on the purchase amount, complete the information in the <b>What is the type and amount of discount?</b>.
-</div>
+>ℹ️ Callout Information: If you want to use the sales associate code field to give a discount on the purchase amount, complete the information in the **What is the type and amount of discount?**.
 
 <blockquote><ui>3. In <b>To which items will this promotion apply?</b>, click the <b>utm_campaign</b> option and type <i>salesassociatecode</i>.</ui>
 
@@ -77,9 +73,7 @@ Additionally, you need to complete the following steps:
 
 1. When simulating a purchase and entering the sales associate code on the Checkout page, make sure that the GET [Search Documents](https://developers.vtex.com/docs/api-reference/master-data-api-v2#get-/api/dataentities/-dataEntityName-/search) call performs the search in the entity `salesassociatecode` and returns all the information added for the sales associate. Example call: https://{accountName}.{environment}.com.br/api/dataentities/codigovendedor/search?codigovendedor=12345.
 
-<div class="alert alert-warning">
-  The <b>status</b> field must return <b>true</b>, indicating that the sales associate code is valid.
-</div>
+>⚠️ The **status** field must return **true**, indicating that the sales associate code is valid.
 
 <blockquote><ui>2. Run the <a href="https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm">Update orderForm configuration</a> POST call to add the following information to the store <a href="https://developers.vtex.com/docs/guides/orderform-fields">orderForm</a></ui>:
 
@@ -87,9 +81,7 @@ Additionally, you need to complete the following steps:
 
 <blockquote><blockquote>- <b>openTextField</b> (optional): Add notes or comments (e.g., information for commissioning filters).
 
-<div class="alert alert-warning">
-  Only the sales associate name should be displayed on the Checkout page.
-</div>
+>⚠️ Only the sales associate name should be displayed on the Checkout page.
 
 After completing all the above steps, the **Sales associate code** field will be available on the Checkout page.
 
diff --git a/docs/tutorials/en/sales-funnel-suiteshare.md b/docs/tutorials/en/sales-funnel-suiteshare.md
index 7f13753d9..1d94b86a5 100644
--- a/docs/tutorials/en/sales-funnel-suiteshare.md
+++ b/docs/tutorials/en/sales-funnel-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: sales-funnel-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/sales-performance.md b/docs/tutorials/en/sales-performance.md
index 631b0647e..8f277f8fa 100644
--- a/docs/tutorials/en/sales-performance.md
+++ b/docs/tutorials/en/sales-performance.md
@@ -212,9 +212,7 @@ The list represents the metrics and filters applied to the chart in table format
   - __Absolute__: view in absolute numbers the increase or decrease of the metrics between one period and another.   
   - __Representative__: view the percentage of representativeness of an item within a metric.  
 
-<div class="alert alert-info">
-Note that the metrics <em>Average ticket</em> and <em>Items per order</em> do not have Percent or Representative views available, as these metrics are calculated by dividing others, and the sum of all the parts of each of them does not equal the Total.
-</div>
+>ℹ️ Note that the metrics *Average ticket* and *Items per order* do not have Percent or Representative views available, as these metrics are calculated by dividing others, and the sum of all the parts of each of them does not equal the Total.
 
 ### Exporting data
 
diff --git a/docs/tutorials/en/scheduled-delivery.md b/docs/tutorials/en/scheduled-delivery.md
index 9f15d8ad9..e9af0b163 100644
--- a/docs/tutorials/en/scheduled-delivery.md
+++ b/docs/tutorials/en/scheduled-delivery.md
@@ -21,9 +21,9 @@ The delivery time frames that are available to customers are called delivery win
 
 If this is the case, you can enable scheduled deliveries by configuring delivery windows and setting the delivery capacity for each of them. To do that, access the Scheduled delivery section on the Shipping Policy page.
 
-<div class="alert alert-warning">
-For <a href="https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Scheduled delivery</a> and <a href="https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Delivery capacity</a> to perform correctly, you must follow the rules below:<p><ul><li>The result from {<a href="https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {shipping policy ID} cannot exceed 60 characters.</li><li>Do not use spaces in <a href="https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">shipping policy IDs</a>.</li></ul></p>
-</div>
+>⚠️ For [Scheduled delivery](https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) and [Delivery capacity](https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) to perform correctly, you must follow the rules below:
+> *The result from {[account name](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {shipping policy ID} cannot exceed 60 characters.
+> * Do not use spaces in [shipping policy IDs](https://help.vtex.com/en/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 Once you've enabled the __Scheduled Delivery__ feature in the Shipping Policy, you can fill in the fields that will determine how it will work. Fill them to define the [maximum delivery time](#maximum-delivery-time), the [delivery window](#delivery-window), and the [delivery capacity limit](#delivery-capacity).
 
@@ -38,10 +38,7 @@ You can configure it through the Maximum delivery time field in the scheduled de
 ## Delivery window
 
 Delivery windows are the time frames during which packages are sent to customers. To configure them, set start and end times by day of the week. You can also set an additional shipping rate for certain days of the week.
-<div class="alert alert-info">
-A delivery window can't be selected after it has started. Only upcoming delivery windows —which have not yet started— will be available to customers.
-
-</div>
+>ℹ️ A delivery window can't be selected after it has started. Only upcoming delivery windows —which have not yet started— will be available to customers.
 
 ## Delivery capacity
 
@@ -49,9 +46,7 @@ Setting the delivery capacity is a way of limiting the number of items or orders
 
 When the customer completes the purchase and selects the scheduled delivery option, the date and time options displayed will take into account the delivery capacity of the delivery window. The customer will only be able to schedule deliveries in windows that still have at least 1 item/order available. 
 
-<div class="alert alert-info">
-If the delivery window has reached its full capacity, it will not be available to be selected. To make it available, increase the number of items/orders by editing the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140">Shipping policy</a>.
-</div> 
+>ℹ️ If the delivery window has reached its full capacity, it will not be available to be selected. To make it available, increase the number of items/orders by editing the [Shipping policy](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140). 
 
 For more information, read our article on [Delivery capacity](https://help.vtex.com/en/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz). 
 
diff --git a/docs/tutorials/en/scheduling-features-for-special-events.md b/docs/tutorials/en/scheduling-features-for-special-events.md
index 369c96241..9971955da 100644
--- a/docs/tutorials/en/scheduling-features-for-special-events.md
+++ b/docs/tutorials/en/scheduling-features-for-special-events.md
@@ -59,9 +59,7 @@ As with the promotion, you can schedule a tax while you are creating it. To sche
 
 Content scheduling via Site Editor can be done either while [creating](https://help.vtex.com/en/tutorial/managing-page-and-template-content--3tMbx6HXy4Fy5r9EhboG37#creating-content) or [editing](https://help.vtex.com/en/tutorial/managing-page-and-template-content--3tMbx6HXy4Fy5r9EhboG37#editing-content) a block. 
 
-<div class="alert alert-warning">
-  <p>Content scheduling is only available for stores developed with <a href="https://vtex.com/us-en/store-framework/">VTEX IO</a>.</p>
-</div>
+>⚠️ Content scheduling is only available for stores developed with [VTEX IO](https://vtex.com/us-en/store-framework/).
 
 To schedule content, follow the steps below:
 
diff --git a/docs/tutorials/en/scheduling-prices.md b/docs/tutorials/en/scheduling-prices.md
index 026b91523..6371b3986 100644
--- a/docs/tutorials/en/scheduling-prices.md
+++ b/docs/tutorials/en/scheduling-prices.md
@@ -48,9 +48,7 @@ To schedule prices in the Admin, please follow the steps below.
 - **End date:** indicates the date from which the fixed price will no longer be valid.  
 - **End time:** indicates the time from which the fixed price will no longer be valid.  
 
-<div class="alert alert-info">
-  <p>When scheduling prices in the Admin, the time zone considered will be the one used in the user’s computer.</p>
-</div>
+>ℹ️ When scheduling prices in the Admin, the time zone considered will be the one used in the user’s computer.
 
 ## Scheduling prices by importing a fixed price template
 
diff --git a/docs/tutorials/en/schemas-on-master-data.md b/docs/tutorials/en/schemas-on-master-data.md
index e0fa7c9d4..cfa3d1377 100644
--- a/docs/tutorials/en/schemas-on-master-data.md
+++ b/docs/tutorials/en/schemas-on-master-data.md
@@ -15,4 +15,4 @@ legacySlug:
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/search-behavior.md b/docs/tutorials/en/search-behavior.md
index e205e2d25..3fff4155a 100644
--- a/docs/tutorials/en/search-behavior.md
+++ b/docs/tutorials/en/search-behavior.md
@@ -89,9 +89,7 @@ For example: The "color" specification is set as searchable and the product was
 
 You can include special characters ( `-` and `/`) when searching for a product.
 
-<div class="alert alert-warning">
-	<p>Choosing the search fields affects the <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">merchandising rule</a> options, as only searchable fields can be used to set up the rules. For example, if you set only the <strong><code>SKUID</code></strong> field as searchable, you cannot promote a<strong><code> ProductID</code></strong> or a <strong><code>ProductRefID</code></strong> using merchandising rules. </p>
-</div>
+>⚠️ Choosing the search fields affects the [merchandising rule](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) options, as only searchable fields can be used to set up the rules. For example, if you set only the **`SKUID`** field as searchable, you cannot promote a**` ProductID`** or a **`ProductRefID`** using merchandising rules.
 
 ### Defining and sorting filter fields
 
@@ -105,9 +103,7 @@ _For example_: a merchant configured that "promotion" has greater relevance than
 
 For more information on how to customize the order of results to meet your store's needs, read the article [Relevance settings](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
 
-<div class="alert alert-info">
-	<p>When using Intelligent Search, two options define the sorting order of your collections. By using the <code>map=productClusterIds</code> command, you are setting the order of your collections to be the one pre-defined by the merchant, with its relevance criteria. If you choose to use <code>productClusterNames</code>, you are setting that you want your collections to follow Intelligent Search's own relevance standards.</p>
-</div>
+>ℹ️ When using Intelligent Search, two options define the sorting order of your collections. By using the `map=productClusterIds` command, you are setting the order of your collections to be the one pre-defined by the merchant, with its relevance criteria. If you choose to use `productClusterNames`, you are setting that you want your collections to follow Intelligent Search's own relevance standards.
 
 ## Alternative ways to search
 
diff --git a/docs/tutorials/en/search-by-geo-coordinates.md b/docs/tutorials/en/search-by-geo-coordinates.md
index 8f7f2ffb0..1ab1dc30f 100644
--- a/docs/tutorials/en/search-by-geo-coordinates.md
+++ b/docs/tutorials/en/search-by-geo-coordinates.md
@@ -15,8 +15,7 @@ legacySlug: search-by-geo-coordinates
 subcategory: 5tSNDlvmik8gGuKw2goW4q
 ---
 
-<div class="alert alert-warning">
-<strong>Attention:</strong> This is a BETA version.</div>
+>⚠️ **Attention:** This is a BETA version.
 
 ### Setting up JSON Schema
 
diff --git a/docs/tutorials/en/search-navigator-control.md b/docs/tutorials/en/search-navigator-control.md
index 2b2c073a3..4c5ac44f0 100644
--- a/docs/tutorials/en/search-navigator-control.md
+++ b/docs/tutorials/en/search-navigator-control.md
@@ -21,9 +21,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 The `<vtex.cmc:searchNavigator/>` control renders a menu of filters related to the result of a search.
 
-<div class="alert alert-info">
-This control works <b>only on pages with search context</b>, i.e. pages where the displayed results were fetched by a user search.
-</div>
+>ℹ️ This control works **only on pages with search context**, i.e. pages where the displayed results were fetched by a user search.
 
 When users perform a search on the store page, the VTEX system tries to fetch results according to filter priority order. [Know more about the VTEX search works here.](/en/tutorial/how-does-vtex-search-work)
 
@@ -54,10 +52,8 @@ This flag can be found on the category registration screen.
 
 ![How Search Navigator control works EN 2](https://images.ctfassets.net/alneenqid6w5/4lSSrBSvyUqEGUEw0oMiac/f132379724b8855996e6f41c2e195ce6/2018-10-23_2233_EN_2.png)
 
-<div class="alert alert-info">
-  <strong>Important</strong>: The <code>&lt;vtex.cmc:searchNavigator/&gt;</code> control displays, by default, only the primary-level categories (root) and the lowest-level sub-categories, within the current context. Intermediate splits in the categories tree are omitted. 
-  In addition, the control only functions on the first three levels, which traditionally are the Department, Category and Subcategory. If your <a href="https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catalog architecture</a> has any other subdivisions except the three levels mentioned above, these will not be displayed using the native control. 
-</div>
+>ℹ️ **Important**: The `&lt;vtex.cmc:searchNavigator/&gt;` control displays, by default, only the primary-level categories (root) and the lowest-level sub-categories, within the current context. Intermediate splits in the categories tree are omitted. 
+>   In addition, the control only functions on the first three levels, which traditionally are the Department, Category and Subcategory. If your [catalog architecture](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) has any other subdivisions except the three levels mentioned above, these will not be displayed using the native control.
 
 ## Brands
 
@@ -67,9 +63,7 @@ The brand registration page doesn't have a display flag in the menu rendered by
 
 So, by default, brands are always displayed.
 
-<div class="alert alert-warning">
-However, on department or category pages, brands will only be displayed by the Search Navigator control if the <b>Brand Filter</b> flag is checked when adding a category.
-</div>
+>⚠️ However, on department or category pages, brands will only be displayed by the Search Navigator control if the **Brand Filter** flag is checked when adding a category.
 
 ### In other pages:
 
@@ -95,6 +89,12 @@ Since they're filters registered in categories, price ranges are only displayed
 
 ---
 
-<div class="alert alert-info">
-Filters are <strong>always</strong> rendered based on the attributes of  search context products; meaning based on the category, specification (color, size), brand, collection, etc.<br><br>Therefore, in addition to the conditions listed above for these attributes to appear as filters in the menu, it's first of all necessary for the search term to return a context with products that have such attributes.<br><br>If the user searches, for example, for "cell" and the Shirts category does not contain any cell, it will not appear in the menu, even if the display flag in this category is checked.
-</div>
+>ℹ️ Filters are **always** rendered based on the attributes of  search context products; meaning based on the category, specification (color, size), brand, collection, etc.
+>
+> 
+>
+> Therefore, in addition to the conditions listed above for these attributes to appear as filters in the menu, it's first of all necessary for the search term to return a context with products that have such attributes.
+>
+> 
+>
+> If the user searches, for example, for "cell" and the Shirts category does not contain any cell, it will not appear in the menu, even if the display flag in this category is checked.
diff --git a/docs/tutorials/en/search-parameters.md b/docs/tutorials/en/search-parameters.md
index 9dd8491f9..ba4d914ba 100644
--- a/docs/tutorials/en/search-parameters.md
+++ b/docs/tutorials/en/search-parameters.md
@@ -80,9 +80,7 @@ In the example above, all products whose **Voltagem**(ID **1**) field is **110v*
 The parameters above can be matched in many ways. However, notice that the search order will be according to the order of the parameters informed. In other words, when you use a category parameter followed by a brand parameter, for example, the category will be searched first and, among the results found, a second search will be made for the brand.
 
 ### Default 2
-<div class="alert alert-info">
-  For stores hosted in VTEX IO, Default 2 should be used as standard.
-  </div>
+>ℹ️ For stores hosted in VTEX IO, Default 2 should be used as standard.
 
 URL: www.loja.com.br/**\[NomeCategoria\]**/**\[NomeMarca\]**/**\[IdColeção\]**/**\[ValorBuscado\]**?map=**c,b,productClusterIds,specificationFilter_\[IdCampoProduto/Sku\]**
 
diff --git a/docs/tutorials/en/searching-for-events-on-audit.md b/docs/tutorials/en/searching-for-events-on-audit.md
index 7ac19bec6..310466eb9 100644
--- a/docs/tutorials/en/searching-for-events-on-audit.md
+++ b/docs/tutorials/en/searching-for-events-on-audit.md
@@ -28,15 +28,11 @@ To start your search in Audit, select the **Audit events** tab. From the **Appli
 
 By clicking on the **Selected date** button, you can choose a pre-defined date for the search. To select an exact period, click the toggle the **Use custom dates.**
 
-<div class="alert alert-warning">
-The system only stores records for the last three months.
-</div>
+>⚠️ The system only stores records for the last three months.
 
 You can add more filters to search for events more precisely. Click the **+ Add Filter** button. Select the filtering parameter (_Action_, _Event Details_, or _Author_) and to which value this topic should be compared. 
 
-<div class="alert alert-info">
-The search results will match exactly the value entered in the field. To avoid unexpected results, make sure there are no extra spaces in the search terms.
-</div>
+>ℹ️ The search results will match exactly the value entered in the field. To avoid unexpected results, make sure there are no extra spaces in the search terms.
 
 Note that you can add more than one filter, even with the same value. In this case, search results will return events matching any of the values you have entered. 
 
@@ -48,9 +44,7 @@ After selecting the application, the date, and other search filters, click the *
 
 Every search you perform will be saved in the **Last searches** tab. To redo a search, go to this tab, and click the <img src="https://images.ctfassets.net/alneenqid6w5/4gWsOnbLMOUeWh0r5YRDz/9b7148d995c03ca84b39473f266b46a9/refresh.png" width="15"> button corresponding to the search you want to perform again.
 
-<div class="alert alert-warning">
-This page shows only the last 50 searches. If you want to save a search indefinitely, perform the same search and add it to your browser favorites.
-</div>
+>⚠️ This page shows only the last 50 searches. If you want to save a search indefinitely, perform the same search and add it to your browser favorites.
 
 <div class = "alert alert-info">
 You may find the full <a href="https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">list of events in Audit</a>.
diff --git a/docs/tutorials/en/searching-for-old-orders.md b/docs/tutorials/en/searching-for-old-orders.md
index 5a7a9f977..b33e86eef 100644
--- a/docs/tutorials/en/searching-for-old-orders.md
+++ b/docs/tutorials/en/searching-for-old-orders.md
@@ -25,7 +25,5 @@ To search through your old orders, follow the steps below:
 6. Choose a starting date/hour and an end date/hour
 7. Click on __Confirm__
 
-<div class="alert alert-info">
-Remember that the search by period is <strong>limited to a six months interval </strong>. As such, if you want to, for example, search for orders from 2017, the time interval chosen in <strong>step 6</strong> must comprise a period of 6 month. Example: Start date = 01/01/2017 e End Date = 30/06/2017.
-</div>
+>ℹ️ Remember that the search by period is **limited to a six months interval **. As such, if you want to, for example, search for orders from 2017, the time interval chosen in **step 6** must comprise a period of 6 month. Example: Start date = 01/01/2017 e End Date = 30/06/2017.
 
diff --git a/docs/tutorials/en/searching-for-orders-in-oms.md b/docs/tutorials/en/searching-for-orders-in-oms.md
index 85afaadff..a371b8984 100644
--- a/docs/tutorials/en/searching-for-orders-in-oms.md
+++ b/docs/tutorials/en/searching-for-orders-in-oms.md
@@ -15,9 +15,7 @@ legacySlug: searching-for-orders-in-oms
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-info">
-<strong>Warning:</strong> you may search in ranges of up to <b>6 months</b>.
-</div>
+>ℹ️ **Warning:** you may search in ranges of up to **6 months**.
 
 The Orders Management search bar enables you to find orders in a variety of ways. Just type in the desired term and press __Enter__ to check the results. It can also be used together with filters, whenever you need to [filter orders in Orders management](/en/tutorial/filtering-orders-in-oms).
 
diff --git a/docs/tutorials/en/security-certificate-ssl.md b/docs/tutorials/en/security-certificate-ssl.md
index 4d74dcffb..ac91ba61b 100644
--- a/docs/tutorials/en/security-certificate-ssl.md
+++ b/docs/tutorials/en/security-certificate-ssl.md
@@ -21,6 +21,4 @@ Whenever you access a safe web page, that is, an Internet page that is protected
 
 There is no need to request the purchase of an SSL certificate. VTEX generates an SSL certificate for your store and guarantees its automatic renewal. The certificate is issued via Let's Encrypt and its creation is VTEX's responsibility at [the time of the store's Go-Live](https://help.vtex.com/en/tutorial/configuring-dns-pointing-to-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-<p>We do not recommend installing other certificates. However, if necessary, please contact our <a href="https://help.vtex.com/pt/support">support</a>.</p>
-</div>
+>⚠️ We do not recommend installing other certificates. However, if necessary, please contact our [support](https://help.vtex.com/pt/support).
diff --git a/docs/tutorials/en/security-monitor.md b/docs/tutorials/en/security-monitor.md
index bb9224004..75c62c908 100644
--- a/docs/tutorials/en/security-monitor.md
+++ b/docs/tutorials/en/security-monitor.md
@@ -15,9 +15,7 @@ legacySlug: security-monitor
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>This feature is part of <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/br-pt/contato/">contact form</a>.</p>
-</div>
+>ℹ️ This feature is part of [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our [contact form](https://vtex.com/br-pt/contato/).
 
 Security Monitor is a dashboard that helps merchants identify and manage potential risks in their environment in real time. The tool identifies configuration risks and the behavior of admin users, then notifies merchants via email, enabling them to take preventive action against security vulnerabilities.
 
diff --git a/docs/tutorials/en/seletivo.md b/docs/tutorials/en/seletivo.md
index bc415860b..2f528b280 100644
--- a/docs/tutorials/en/seletivo.md
+++ b/docs/tutorials/en/seletivo.md
@@ -15,6 +15,4 @@ legacySlug: seletivo
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/seller-creating-an-account-in-the-seller-portal.md b/docs/tutorials/en/seller-creating-an-account-in-the-seller-portal.md
index d0e30605d..86398464a 100644
--- a/docs/tutorials/en/seller-creating-an-account-in-the-seller-portal.md
+++ b/docs/tutorials/en/seller-creating-an-account-in-the-seller-portal.md
@@ -35,9 +35,7 @@ The process of creating an account in the Seller Portal begins with an [invitati
 - [Creating an account for VTEX sellers](#connecting-the-vtex-account-with-the-marketplace): store hosted on the VTEX platform.    
 - [Creating an account for external sellers](#creating-an-account-for-external-sellers): store hosted on another ecommerce platform, or not yet hosted on any platform.    
 
-<div class="alert alert-info">
-The account creation link sent to the seller is valid for 7 days. Once the link is opened, the seller must complete the registration form within six hours, without interruption. If the registration cannot be completed within six hours, the marketplace needs to send the invitation again.
-</div>
+>ℹ️ The account creation link sent to the seller is valid for 7 days. Once the link is opened, the seller must complete the registration form within six hours, without interruption. If the registration cannot be completed within six hours, the marketplace needs to send the invitation again.
 
 ### Connecting the VTEX account with the marketplace
 
diff --git a/docs/tutorials/en/seller-management.md b/docs/tutorials/en/seller-management.md
index 3d75c1d84..be76a4377 100644
--- a/docs/tutorials/en/seller-management.md
+++ b/docs/tutorials/en/seller-management.md
@@ -90,9 +90,7 @@ By clicking on the <i class="fas fa-ellipsis-v"></i> button in the seller row, t
 - **Seller details:** Redirects to the Seller details page, where you can view or edit information.  
 - **Orders:** Redirects to the All orders page in the VTEX OMS, filtered by the orders from the selected seller.  
 
-<div class="alert alert-info">
-Please note that the list is sorted alphabetically. To view data for all sellers, navigate between the results pages by clicking on the <i class="fas fa-angle-left"></i> and <i class="fas fa-angle-right"></i> arrows at the bottom of the page. Use the filters to refine your results.
-  </div>
+>ℹ️ Please note that the list is sorted alphabetically. To view data for all sellers, navigate between the results pages by clicking on the <i class="fas fa-angle-left"></i> and <i class="fas fa-angle-right"></i> arrows at the bottom of the page. Use the filters to refine your results.
 
 ### Identifiable sellers and unidentifiable sellers (white label)
 
diff --git a/docs/tutorials/en/seller-portal-promotions.md b/docs/tutorials/en/seller-portal-promotions.md
index c78969cb0..934158d9b 100644
--- a/docs/tutorials/en/seller-portal-promotions.md
+++ b/docs/tutorials/en/seller-portal-promotions.md
@@ -91,7 +91,5 @@ To go to the **Archived Promotions** page, click the <i class="fas fa-ellipsis-v
 
 You can unarchive or duplicate archived promotions by clicking the <i class="fas fa-ellipsis-v"></i> icon.
 
-<div class="alert alert-info">
-  <p>When you unarchive a promotion, the status will change to <code>Paused</code>.</p>
-  </div>
+>ℹ️ When you unarchive a promotion, the status will change to `Paused`.
 
diff --git a/docs/tutorials/en/seller-portal-shared-products.md b/docs/tutorials/en/seller-portal-shared-products.md
index e2e3411f0..fb08c9178 100644
--- a/docs/tutorials/en/seller-portal-shared-products.md
+++ b/docs/tutorials/en/seller-portal-shared-products.md
@@ -16,7 +16,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
 
-<div class="alert alert-warning"> The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.</div>
+>⚠️ The limit for each Seller Portal account is 100 thousand products. For more information, please contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support.
 
 **Shared Products** is the module where you can manage the products in your catalog that are already offered in the marketplace. The shared products dashboard displays all the products that the marketplace has made available for your store to sell. These products have been synced with the marketplace catalog.
 
diff --git a/docs/tutorials/en/send-the-seller-white-label-payment-methods-to-the-marketplace.md b/docs/tutorials/en/send-the-seller-white-label-payment-methods-to-the-marketplace.md
index 3e2b19062..6e94eefbc 100644
--- a/docs/tutorials/en/send-the-seller-white-label-payment-methods-to-the-marketplace.md
+++ b/docs/tutorials/en/send-the-seller-white-label-payment-methods-to-the-marketplace.md
@@ -19,9 +19,7 @@ The objective of this tutorial is to teach how to send the payment options from
 
 This feature allows for purchases made on an e-commerce to be completed with the payment options of a physical store. This decreases the complexity of the operation, separating centers of cost, since the invoice and the payments will be attributed directly to the Registration Number of the physial store, which acts as White Label Seller of a Marketplace.
 
-<div class="alert alert-info">
-This configuration replaces the old feature of <strong> Alternative Accounts</strong> for this scenario.
-</div>
+>ℹ️ This configuration replaces the old feature of ** Alternative Accounts** for this scenario.
 
 ## Registering payment options on the Seller White Label
 
diff --git a/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md b/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
index 1497d2305..cd51b397e 100644
--- a/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
+++ b/docs/tutorials/en/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
@@ -15,9 +15,7 @@ legacySlug: sending-clothes-shoes-and-bags-attributes-to-mercado-livre
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-The sending of the products attributes Clothes, Shoes and Bags follows a different flow from the others. In this mapping process, the result is that the SKUs will all be shown in the same ad. For other product types, Mercado Livre performs an automatic mapping.
-</div>
+>ℹ️ The sending of the products attributes Clothes, Shoes and Bags follows a different flow from the others. In this mapping process, the result is that the SKUs will all be shown in the same ad. For other product types, Mercado Livre performs an automatic mapping.
 
 To send the attributes of the products of type __Clothes__, __Shoes__ and __Bags__ to Mercado Livre, follow the steps below:
 
@@ -25,9 +23,7 @@ To send the attributes of the products of type __Clothes__, __Shoes__ and __Bags
 2. Fill in the template worksheet with the SKU IDs to be sent to Mercado Livre and with the values of attributes accepted by Mercado Livre. The accepted values can be found in the links below.
 3. Save the template worksheet with the filled-in values.
 
-<div class="alert alert-info">
-The values accepted by Mercado Livre can be found in the following links. Click the name of your country to download. You will find codes for <u>Main Color</u>, <u>Secondary Color</u>, <u>Adult Size</u>, <u>Children's Footwear Size</u>, <u>Adult's Clothing Size</u> and <u>Children's Clothing Size</u>. These values must be filled in properly in the <strong>Main Color</strong>, <strong>Secondary Color</strong> and <strong>Size</strong> fields of the template worksheet. With the exception of the <em>Secondary Color</em> attribute, all other fields are required (SKU_ID, Main Color, and Size).
-</div>
+>ℹ️ The values accepted by Mercado Livre can be found in the following links. Click the name of your country to download. You will find codes for <u>Main Color</u>, <u>Secondary Color</u>, <u>Adult Size</u>, <u>Children's Footwear Size</u>, <u>Adult's Clothing Size</u> and <u>Children's Clothing Size</u>. These values must be filled in properly in the **Main Color**, **Secondary Color** and **Size** fields of the template worksheet. With the exception of the *Secondary Color* attribute, all other fields are required (SKU_ID, Main Color, and Size).
 
 __Links with the values accepted by Mercado Livre__:
 
diff --git a/docs/tutorials/en/sending-sku-attributes-to-amazon.md b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
index 5fbf0172d..31efcbc48 100644
--- a/docs/tutorials/en/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
@@ -24,9 +24,7 @@ The mapping will only be done once for each category. With that, even once you h
 2. Fill in the fields of the mapping spreadsheet as follows:
 
 
-<div class="alert alert-danger">
-Note: If <strong>none</strong> of the category attributes is required by Amazon, then <strong>no mapping is required</strong>. Just reindex your products so they are shipped directly through the integration.
-</div>
+>❗ Note: If **none** of the category attributes is required by Amazon, then **no mapping is required**. Just reindex your products so they are shipped directly through the integration.
 
 1. __ID category:__ it's the category ID in VTEX. You can find it next to the name of each category as you expand the tree.
 2. __VariationTheme:__ it's the way the SKU varies in the marketplace. You must fill with Variations Themes that fit the category of your products and respective PTDs.
diff --git a/docs/tutorials/en/sent-offers-beta.md b/docs/tutorials/en/sent-offers-beta.md
index a86329de3..ba359b0fb 100644
--- a/docs/tutorials/en/sent-offers-beta.md
+++ b/docs/tutorials/en/sent-offers-beta.md
@@ -32,9 +32,7 @@ By setting up the product’s price and inventory conditions, the seller prepare
 - **Containing errors**: when the system detects an issue that prevents an offer from being sent or updated on a channel. This status means that the offer requires manual review.  
 - **Unavailable**: when the offer is discarded for being inactive or not included in the trade policy determined for the channel.
 
-<div class="alert alert-info">
-By clicking on <code>View list</code>, you will be redirected to the <a href="https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE">Offers List</a>.
-</div>
+>ℹ️ By clicking on `View list`, you will be redirected to the [Offers List](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE).
 
 ## Channels
 
diff --git a/docs/tutorials/en/sent-offers-buybox-opportunities.md b/docs/tutorials/en/sent-offers-buybox-opportunities.md
index fa44d6bd8..816e1099b 100644
--- a/docs/tutorials/en/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/en/sent-offers-buybox-opportunities.md
@@ -15,11 +15,9 @@ legacySlug: sent-offers-buybox-opportunities-beta
 subcategory: 
 ---
 
-<div class="alert alert-info">
-To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module <b>Offer Management</b>. As a result, the module will not receive new updates or maintenance.
-For connectors and marketplaces already integrated into the module, please contact the development team by email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the <a href="https://developers.vtex.com/updates/release-notes">Developer Portal's release notes section</a> and <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center announcements page</a>.
-</div>  
+>ℹ️ To evolve your experience in synchronizing and updating offers, the VTEX team is developing a new functionality that will replace the current module **Offer Management**. As a result, the module will not receive new updates or maintenance.
+> For connectors and marketplaces already integrated into the module, please contact the development team by email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> For connectors interested in starting the integration, we ask you to wait for the release of the new module, as soon as it is available we will announce it to all customers through the [Developer Portal's release notes section](https://developers.vtex.com/updates/release-notes) and [VTEX Help Center announcements page](https://help.vtex.com/pt/en/announcements).  
 
 An offer is a SKU from a seller that has been sent to a sales channel and whose price and inventory have been configured. The [Offer Management](https://help.vtex.com/en/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) module in the VTEX Admin allows sellers to monitor their offers’ submission and sync on marketplaces. Besides, it can lead to an increase in your product sales. 
 
@@ -60,9 +58,7 @@ Follow the steps below to add your offer to the Buybox:
 4. On the **Offer opportunity** page, make sure your product is the same as the one already for sale on the marketplace. If they are the same, click on `Add to Buybox`. 
 5. Click on `Add`. 
 
-<div class="alert alert-warning">
-This action cannot be undone, so make sure you are offering the correct product. If your offer is not for the same product listed on the marketplace, you must not add it to the Buybox. Adding offers for different products to the Buybox can damage your reputation in that marketplace.  
-</div>
+>⚠️ This action cannot be undone, so make sure you are offering the correct product. If your offer is not for the same product listed on the marketplace, you must not add it to the Buybox. Adding offers for different products to the Buybox can damage your reputation in that marketplace.
 
 To be well-positioned on the Buybox, perform the configurations indicated in the [Winning or losing the Buybox](#winning-or-losing-the-buybox) section of this article.
 
diff --git a/docs/tutorials/en/sequencial-suiteshare.md b/docs/tutorials/en/sequencial-suiteshare.md
index b8c7ba261..135a4f9c5 100644
--- a/docs/tutorials/en/sequencial-suiteshare.md
+++ b/docs/tutorials/en/sequencial-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: sequencial
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/set-up-alelo-payment-method-for-cielo-v3.md b/docs/tutorials/en/set-up-alelo-payment-method-for-cielo-v3.md
index 318ba3f2e..3358372d8 100644
--- a/docs/tutorials/en/set-up-alelo-payment-method-for-cielo-v3.md
+++ b/docs/tutorials/en/set-up-alelo-payment-method-for-cielo-v3.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 This article will cover how to enable the Alelo grocery voucher card as a payment method in our Checkout module.
 
-<div class="alert alert-info">
-<strong>Warning</strong>: The Alelo grocery voucher card is a payment method valid only in Brazil.
-</div>
+>ℹ️ **Warning**: The Alelo grocery voucher card is a payment method valid only in Brazil.
 
 For the time being, on the VTEX platform, the payment acquirer Cielo is the only one to accept Alelo as a payment  method. The first step must therefore be to enable this payment acquirer as a gateway affiliation in your store. You can check out our full tutorial on these configuration steps [here](https://help.vtex.com/en/tutorial/configurar-adquirente-cielo--3avjZ7q65WcM02K8K0eeWu?locale=en "here"). 
 
@@ -41,6 +39,4 @@ Follow the instructions below:
 8. You can also add __special conditions__ for the payment method by clicking on “Add special condition”. 
 9. __Save__ change to complete the setup.
 
-<div class="alert alert-info">
-<strong>Warning</strong>: Remember that special payment conditions take up to 10 minutes to be applied to Checkout.
-</div>
+>ℹ️ **Warning**: Remember that special payment conditions take up to 10 minutes to be applied to Checkout.
diff --git a/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md b/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md
index 9fc9a93b5..d90bfe4a3 100644
--- a/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md
+++ b/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md
@@ -23,9 +23,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Before starting the configuration, it is necessary to open a ticket with the VTEX support team requesting the 3DS 2 activation in your store. For more information, see [how to open a ticket](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM).
 
-<div class="alert alert-warning">
-On VTEX, 3DS 2 does not make purchases with two cards. If an order is placed under these conditions, payment will be canceled.
-</div>            
+>⚠️ On VTEX, 3DS 2 does not make purchases with two cards. If an order is placed under these conditions, payment will be canceled.            
 
 ## Configuring 3DS 2
 
@@ -39,6 +37,4 @@ To configure 3DS 2 authentication on affiliations, follow the steps below:
 6. In the __Suporte 3DS 2.0__ field, select the __“Yes”__ option.
 7. Click on __Save__.
 
-<div class="alert alert-warning">
-  The 3DS 2 field description (<b>"Suporte 3DS 2.0"</b>, reported in Step 8) may vary according to the type of payment provider to be configured. Check with your chosen payment provider's technical support to identify the correct field to select to enable 3DS 2 authentication.
-</div>
+>⚠️ The 3DS 2 field description (**"Suporte 3DS 2.0"**, reported in Step 8) may vary according to the type of payment provider to be configured. Check with your chosen payment provider's technical support to identify the correct field to select to enable 3DS 2 authentication.
diff --git a/docs/tutorials/en/setting-up-a-personal-gift-message.md b/docs/tutorials/en/setting-up-a-personal-gift-message.md
index 309a82264..36cc4e281 100644
--- a/docs/tutorials/en/setting-up-a-personal-gift-message.md
+++ b/docs/tutorials/en/setting-up-a-personal-gift-message.md
@@ -50,6 +50,4 @@ You can view the written message on __My Account > My Orders__:
 
 ![](https://images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
 
-<div class="alert alert-info">
-  <p>After setting up the SKU service, wait for the indexing process for the registration to be effective on the website. Once the service is active, you will be able to test the purchase.</p>
-</div>
+>ℹ️ After setting up the SKU service, wait for the indexing process for the registration to be effective on the website. Once the service is active, you will be able to test the purchase.
diff --git a/docs/tutorials/en/setting-up-abandoned-carts.md b/docs/tutorials/en/setting-up-abandoned-carts.md
index 108d8a310..2c6aa1873 100644
--- a/docs/tutorials/en/setting-up-abandoned-carts.md
+++ b/docs/tutorials/en/setting-up-abandoned-carts.md
@@ -42,9 +42,7 @@ You can create your own custom email template or use the default template option
 
 ![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/d48bd1624a47451e2314e2296237992f/Template_XHTML.PNG)
 
-<div class="alert alert-warning">
-We recommend that template customization should be performed by professionals with experience in the CMS module, and preferably, who have already configured other page and shelf templates.
-</div>
+>⚠️ We recommend that template customization should be performed by professionals with experience in the CMS module, and preferably, who have already configured other page and shelf templates.
 
 1. In the VTEX Admin, go to __Storefront > Layout__, or type __Layout__ in the search bar at the top of the page.
 2. Under __CMS > HTML__ Templates, click on the `CEM-Abandoned-Cart` icon.
@@ -128,9 +126,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 ![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/6408ac4ab3b36d015790bcf1b1b5d667/Filter_Master_Data.PNG)
 
-<div class="alert alert-warning">
-  In addition to the filters indicated above, it is recommended to insert another filter in the following format: <code>Receives newsletter? - Equal to - True</code>. This ensures compliance with <a href="https://help.vtex.com/en/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">data subject rights</a>, as only customers subscribed to the newsletter will receive abandoned cart emails. Subscription to your store's newsletter can be managed at checkout or in the <a href="https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">My Account</a> section of your store.
-</div>
+>⚠️ In addition to the filters indicated above, it is recommended to insert another filter in the following format: `Receives newsletter? - Equal to - True`. This ensures compliance with [data subject rights](https://help.vtex.com/en/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM), as only customers subscribed to the newsletter will receive abandoned cart emails. Subscription to your store's newsletter can be managed at checkout or in the [My Account](https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile) section of your store.
 
 <blockquote><ui> 10. Click on the <b>Schedule</b> tab and select whether to send the email on a specific date or on a dynamic date.</ui>
 
@@ -142,8 +138,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 <blockquote><blockquote><ui>b. In <b>Recipient</b>, to perform a system test, enter your email and click <b>Add Static email</b>.</ui>
 
-<div class="alert alert-warning">Once you have completed the other settings below and verified that you have received the abandoned cart message in your email, return to this step, select the option <strong>CL</strong>: <strong>Email</strong>, click in <strong>Add Dynamic email</strong>, and then in <strong>Save</strong>.
-</div>
+>⚠️ Once you have completed the other settings below and verified that you have received the abandoned cart message in your email, return to this step, select the option **CL**: **Email**, click in **Add Dynamic email**, and then in **Save**.
 
 <blockquote><blockquote><ui>c. In <b>Email body format</b>, select <b>Html</b>.</ui>
 
@@ -159,8 +154,7 @@ In addition, we also have the "Cart" and "Last Cart" filters. Although they seem
 
 ![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)  
 
-<div class="alert alert-warning">The URL address must be the real one of the store, not the URL with vtexcommercestable.
-</div>
+>⚠️ The URL address must be the real one of the store, not the URL with vtexcommercestable.
 
 <blockquote><blockquote><ui>i. In <b>Add utm_source to all links whose value is</b>, fill with "CEM", to facilitate the identification of purchases by abandoned cart.</ui>
 
diff --git a/docs/tutorials/en/setting-up-alternative-accounts.md b/docs/tutorials/en/setting-up-alternative-accounts.md
index 30a653593..0c240a940 100644
--- a/docs/tutorials/en/setting-up-alternative-accounts.md
+++ b/docs/tutorials/en/setting-up-alternative-accounts.md
@@ -15,6 +15,4 @@ legacySlug: setting-up-alternative-accounts
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-info">
-The Alternative Accounts feature has been discontinued. To replace it, use the Franchise Accounts and Sellers White Label solution. For more details, refer to <a href="http://help.vtex.com/en/faq/what-are-franchise-account-and-seller-white-label">this article</a>.
-</div>
+>ℹ️ The Alternative Accounts feature has been discontinued. To replace it, use the Franchise Accounts and Sellers White Label solution. For more details, refer to [this article](http://help.vtex.com/en/faq/what-are-franchise-account-and-seller-white-label).
diff --git a/docs/tutorials/en/setting-up-amazonpay-beta.md b/docs/tutorials/en/setting-up-amazonpay-beta.md
index d9321c906..6d635ba64 100644
--- a/docs/tutorials/en/setting-up-amazonpay-beta.md
+++ b/docs/tutorials/en/setting-up-amazonpay-beta.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-amazonpay-beta
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-info">
-This feature is in beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/en-us/requests).
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/en-us/requests).
 
 AmazonPay Checkout, is a known payment processor and method used
 worldwide. This method is available at VTEX in the affiliations list on the **Settings** page. AmazonPay gateway affiliation supports the AmazonPay payment method.
diff --git a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
index d4751af23..ea57f5ac5 100644
--- a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -37,9 +37,7 @@ If necessary, InStore can send additional information. Example with the sub-acqu
 - `administrativePassword`: string - default password. For example, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-To create any extra configuration, you need to send to the inStore team (instoredevs@vtex.com.br) every extra the app needs to complete the transaction. With that, we will create a form on the Payments module so that customers can configure their acquirer.
-</div>
+>ℹ️ To create any extra configuration, you need to send to the inStore team (instoredevs@vtex.com.br) every extra the app needs to complete the transaction. With that, we will create a form on the Payments module so that customers can configure their acquirer.
 
 ## Sending URI and response URI for each action
 
@@ -185,9 +183,7 @@ For the integration to work, the customer must set up the InStore connector on t
 
 AppLinking integration doesn't include other dependencies, since communication between the inStore application and the payment application happens with specific URIs containing all the configuration and payment parameters required for the action.
 
-<div class="alert alert-warning">
-On Android, all communication must happen with a new <code>Intent</code>. This means that you should not send the response as a callback from the initial <code>Intent</code> call. Instead, send a new <code>Intent</code> to the inStore application with the previous response.
-</div>
+>⚠️ On Android, all communication must happen with a new `Intent`. This means that you should not send the response as a callback from the initial `Intent` call. Instead, send a new `Intent` to the inStore application with the previous response.
 
 To configure the inStore connector, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-b2b-on-vtex.md b/docs/tutorials/en/setting-up-b2b-on-vtex.md
index a1bad3d28..8acf36436 100644
--- a/docs/tutorials/en/setting-up-b2b-on-vtex.md
+++ b/docs/tutorials/en/setting-up-b2b-on-vtex.md
@@ -63,9 +63,7 @@ Users not registered on the website need an interface for pre-registration. The
 
 Accordingly, all pre-registration fields must be defined. B2B usually uses client information (name, email, phone etc.) and their address (street, district, city etc.) for purposes of pre-registration. Check our article [Import customer data - Brazil](https://help.vtex.com/en/tutorial/importando-dados-de-clientes-brasil--2zWYVOyj0sISYQmeUwCsI0 "Importar dados de clientes - Brasil") for more information about the required data.
 
-<div class="alert alert-warning">
-  <p>The field used as conditional rule in the commercial policy should not be included in this form, since users cannot approve themselves, this being under the responsibility of the store.</p>
-</div>
+>⚠️ The field used as conditional rule in the commercial policy should not be included in this form, since users cannot approve themselves, this being under the responsibility of the store.
 
 ## 4. Create a pre-registration form
 
@@ -75,6 +73,4 @@ Upon the definition of fields, the pre-registration form must be created on the
 
 Once the settings have been completed and the B2B is finally operating, the store owner’s routine will depend on their business rules and needs. Basically, at each new registration, the store owner should analyze and approve the user using the CRM interface, that they can access using the following URL: `http://{nome_da_conta}.vtexcrm.com.br/`.
 
-<div class="alert alert-info">
-  <p>This article describes basic B2B settings; however, there are several ways to customize the system according to this need, including by sending emails (triggers) based on pre-defined events.</p>
-</div>
+>ℹ️ This article describes basic B2B settings; however, there are several ways to customize the system according to this need, including by sending emails (triggers) based on pre-defined events.
diff --git a/docs/tutorials/en/setting-up-conductor-gateway.md b/docs/tutorials/en/setting-up-conductor-gateway.md
index 2b79dd940..a3cdb731e 100644
--- a/docs/tutorials/en/setting-up-conductor-gateway.md
+++ b/docs/tutorials/en/setting-up-conductor-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-conductor-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Conductor is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) with [PCI certification](/en/faq/what-is-the-pci-ssc) that is more than 20 years old. In VTEX, it can be configured to process payments made with __credit cards with store brand__.
 
diff --git a/docs/tutorials/en/setting-up-customized-payments-using-mercadopago-latin-america.md b/docs/tutorials/en/setting-up-customized-payments-using-mercadopago-latin-america.md
index b4dd28214..22aedbce8 100644
--- a/docs/tutorials/en/setting-up-customized-payments-using-mercadopago-latin-america.md
+++ b/docs/tutorials/en/setting-up-customized-payments-using-mercadopago-latin-america.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-customized-payments-using-mercadopago-latin-america
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-This article concerns settings which are applicable in stores that operate in the following Latin American countries: <strong>Argentina</strong>, <strong>Chile</strong>, <strong>Colombia</strong> and <strong>Uruguai</strong>.
-</div>
+>⚠️ This article concerns settings which are applicable in stores that operate in the following Latin American countries: **Argentina**, **Chile**, **Colombia** and **Uruguai**.
 
 You can use Mercado Pago to offer customized payments (using local credit cards) in your store. For this, you first need to register the [MercadoPagoV1 gateway affiliation](/en/tutorial/setting-up-mercadopagov1-sub-acquirer). Then, just follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-cybersource-antifraud.md b/docs/tutorials/en/setting-up-cybersource-antifraud.md
index ebe939523..6a71a7dbd 100644
--- a/docs/tutorials/en/setting-up-cybersource-antifraud.md
+++ b/docs/tutorials/en/setting-up-cybersource-antifraud.md
@@ -21,9 +21,7 @@ If you are looking for more details about __gateway__ CyberSource, read [this He
 
 ## Setting up the CyberSource Anti-Fraud
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before performing Step 6. of this section.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before performing Step 6. of this section.
 
 1. In the VTEX Admin, go to __Store Settings > Payment > Providers__, or type __Providers__ in the search bar at the top of the page.
 2. On the provider's screen, click the `New Provider` button.
@@ -51,6 +49,4 @@ After setting up CyberSource's anti-fraud system, it will be available for use i
 6. Select CyberSource.
 7. Click `Save`.
 
-<div class="alert alert-warning">
-For a transaction to go through antifraud analysis, <strong>the payment condition used by the customer must be associated with it</strong>.
-</div>
+>⚠️ For a transaction to go through antifraud analysis, **the payment condition used by the customer must be associated with it**.
diff --git a/docs/tutorials/en/setting-up-cybersource-gateway.md b/docs/tutorials/en/setting-up-cybersource-gateway.md
index d07646e9d..92248255a 100644
--- a/docs/tutorials/en/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/en/setting-up-cybersource-gateway.md
@@ -37,9 +37,7 @@ The following Cybersource apps must be installed in your store account:
 - __vtex.cybersource__
 - __vtex.cybersource-payer-auth__
 
-<div class="alert alert-warning">
-If you intend to use Cybersource's anti-fraud system, but want to transact payments on a non-Cybersource gateway, you will need to install the <b>vtex.cybersource-fraud</b> app.
-  </div>
+>⚠️ If you intend to use Cybersource's anti-fraud system, but want to transact payments on a non-Cybersource gateway, you will need to install the **vtex.cybersource-fraud** app.
 
 Learn more about installing applications on a VTEX account in [Installing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app). 
 
@@ -47,9 +45,7 @@ Learn more about installing applications on a VTEX account in [Installing an app
 
 After installing the apps, you must create authentication keys in the Cybersource environment.
 
-<div class="alert alert-warning">
-  Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Cybersource account for the latest information.
-  </div>
+>⚠️ Settings configured in an environment external to VTEX may be discontinued or modified without prior notice. Please check your Cybersource account for the latest information.
 
 Follow the steps below:
 
@@ -138,8 +134,7 @@ To process credit card payments through Cybersource, follow the steps below:
 8. If you wish, you can also [configure special payment conditions](https://help.vtex.com/en/tutorial/special-conditions--tutorials_456).
 9. Click __Save__.
 
-<div class="alert alert-warning">
-  If you have previously created credit card payment conditions for other gateways (including the legacy Cybersource provider), you can set those conditions to <b>Inactive</b>. In-progress transactions initiated from that provider will still be processed by that provider, even if it is inactive. Only new transactions will be processed by the new Cybersource IO provider. If you need to revert to your previous provider for any reason, simply set their payment conditions to <b>Active</b> and the Cybersource IO payment conditions to <b>Inactive</b>.</div>
+>⚠️ If you have previously created credit card payment conditions for other gateways (including the legacy Cybersource provider), you can set those conditions to **Inactive**. In-progress transactions initiated from that provider will still be processed by that provider, even if it is inactive. Only new transactions will be processed by the new Cybersource IO provider. If you need to revert to your previous provider for any reason, simply set their payment conditions to **Active** and the Cybersource IO payment conditions to **Inactive**.
 
 ## Setting up Cybersource IO Device Fingerprint (optional)
 
@@ -147,9 +142,7 @@ Device Fingerprint is an identifier that acts in payment processing to improve f
 
 By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
 
 To configure Cybersource IO Device Fingerprint, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-decidir-gateway.md b/docs/tutorials/en/setting-up-decidir-gateway.md
index e879091a0..75cfbe85a 100644
--- a/docs/tutorials/en/setting-up-decidir-gateway.md
+++ b/docs/tutorials/en/setting-up-decidir-gateway.md
@@ -35,9 +35,7 @@ To configure Decidir, follow the steps below:
 13. In the __Change Margin__ field, set the percentage margin to which the payment amount may be changed.
 14. Click __Save__.
 
-<div class="alert alert-warning">
-Warning: if you decide to contract <strong>CyberSource</strong> anti-fraud services, we recommend contacting the Cybersource team directly for more info on the Checkout configuration.
-</div>
+>⚠️ Warning: if you decide to contract **CyberSource** anti-fraud services, we recommend contacting the Cybersource team directly for more info on the Checkout configuration.
 
 ## Setting up the payment condition
 
diff --git a/docs/tutorials/en/setting-up-device-fingerprint-for-niubiz.md b/docs/tutorials/en/setting-up-device-fingerprint-for-niubiz.md
index 3f8a2f9d6..e82e257de 100644
--- a/docs/tutorials/en/setting-up-device-fingerprint-for-niubiz.md
+++ b/docs/tutorials/en/setting-up-device-fingerprint-for-niubiz.md
@@ -19,9 +19,7 @@ __Device Fingerprint__ is an identifier that acts in payment processing to impro
 
 By collecting non-sensitive data, Device Fingerprint identifies and analyzes the security level of the device used to perform a given transaction. It also analyzes transactions previously performed with that device.
 
-<div class="alert alert-info">
-Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
-</div>
+>ℹ️ Each store must have only one Device Fingerprint registered. Check if you have already registered the Device Fingerprint in another connector, before proceeding with the steps below.
 
 This article will explain how to associate the Device Fingerprint feature with the Niubiz affiliation.  
 
@@ -29,9 +27,7 @@ This requires generating an identifier using [Google Tag Manager](https://market
 
 ## Creating the identifier
 
-<div class="alert alert-info">
-This step may be outdated as it is performed in an external environment.
-</div>          
+>ℹ️ This step may be outdated as it is performed in an external environment.          
 
 First, you need to create the identifier.
 
@@ -104,9 +100,7 @@ Follow these instructions:
 
 Google Tag Manager will then create the identifier. 
 
-<div class="alert alert-warning">
-Please write down the ID in a place you can easily find it.
-</div>
+>⚠️ Please write down the ID in a place you can easily find it.
 
 ##  Configuration in the VTEX Admin
 
diff --git a/docs/tutorials/en/setting-up-firstdata-acquirer.md b/docs/tutorials/en/setting-up-firstdata-acquirer.md
index d2f6e6ed0..a4644d9a1 100644
--- a/docs/tutorials/en/setting-up-firstdata-acquirer.md
+++ b/docs/tutorials/en/setting-up-firstdata-acquirer.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-firstdata-acquirer
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 At VTEX, it is possible to integrate with FirstData. With this provider, your store can make sales using credit and debit cards, and Plan Ahora (Argentine payment system).
 
diff --git a/docs/tutorials/en/setting-up-future-inventory.md b/docs/tutorials/en/setting-up-future-inventory.md
index a0546d506..4e45decc0 100644
--- a/docs/tutorials/en/setting-up-future-inventory.md
+++ b/docs/tutorials/en/setting-up-future-inventory.md
@@ -15,17 +15,13 @@ legacySlug: setting-up-future-inventory
 subcategory: 32vrn4K2ZscjUaIBe6w5fm
 ---
 
-<div class="alert alert-info">
-<p>This feature is in closed beta, which means that we are working to improve it. If you have any questions, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in closed beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/pt-br/requests).
 
 For some ecommerce operations, it is useful to have the ability to sell an item that is not available for immediate delivery, but that has an estimated date of arrival at the stock. The __Future Inventory__ feature allows just that.
 
 ## How Future inventory works
 
-<div class="alert alert-warning">
-Currently the configuration of Future Inventory is available only <a target="_blank" href="https://developers.vtex.com/reference/inventory#savesupplylot">via API</a>.
-</div>
+>⚠️ Currently the configuration of Future Inventory is available only <a target="_blank" href="https://developers.vtex.com/reference/inventory#savesupplylot">via API</a>.
 
 The Future Inventory API allows you to register a __Supply Lot__. This lot represents future inventory and carries two main pieces of information:
 - Quantity of items.
@@ -37,8 +33,7 @@ In such case, purchases of these SKUs will consume the items available in the su
 
 >Final delivery time = Delivery SLA + Deadline for receiving the supply lot
 
-<div class="alert alert-info">
-If the date of receipt is earlier than the date of the shipping calculation, the additional time will be 0 (zero), since - in this case - the supply lot has already been received.</div>
+>ℹ️ If the date of receipt is earlier than the date of the shipping calculation, the additional time will be 0 (zero), since - in this case - the supply lot has already been received.
 
 Check out the documentation for the endpoint used to save Future Inventory:
 [Save Supply Lot](https://developers.vtex.com/reference/inventory#savesupplylot)
@@ -58,9 +53,7 @@ When using the Future Inventory API, be aware of the following restrictions:
 
 You can transfer inventory from a supply lot to immediate delivery inventories. This transfer causes the items to be considered immediately available. With that, there is no additional time in the shipping SLA.
 
-<div class="alert alert-info">
-The transfer to immediate delivery frees up space to register a new lot. That is, if your store has 10 registered lots (the limit currently allowed) and you transfer 2 of them to immediate delivery, you now have 8 registered lots and two spaces available.
-</div>
+>ℹ️ The transfer to immediate delivery frees up space to register a new lot. That is, if your store has 10 registered lots (the limit currently allowed) and you transfer 2 of them to immediate delivery, you now have 8 registered lots and two spaces available.
 
 Check out the documentation for the endpoint used to transfer a Future Inventory to immediate delivery:
 [Transfer Supply Lot](https://developers.vtex.com/reference/inventory#transfersupplylot)
diff --git a/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md b/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md
index 563be0c2b..5f591f6ed 100644
--- a/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md
+++ b/docs/tutorials/en/setting-up-itau-registered-ticket-itau-registrado.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-itau-registered-ticket-itau-registrado
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 To set up the Itaú registered boleto, you can choose between two connectors: __Invoice Itaú__ (also known as Itaú Registrado or Boleto Itaú, which you will learn how to configure on this very article) or [ItauShopline](https://help.vtex.com/en/tutorial/setting-up-itau-registered-ticket--3TqzCHPU7KIYGsOKuUeQcq). In __Invoice Itaú__'s case, the boleto is issued in a transparent way (without redirecting to Itaús's website). On the other hand, bank reconciliation must be done through reconciliation files.
 
diff --git a/docs/tutorials/en/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md b/docs/tutorials/en/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
index ecfe04324..f10c71d04 100644
--- a/docs/tutorials/en/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
+++ b/docs/tutorials/en/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
@@ -25,9 +25,7 @@ For each of these payment methods there are different setup requirements:
     - __Klarna__: you need to [setting up Klarna affiliation](/es/tutorial/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method#setting-up-klarna-affiliation) and install the _vtexdemoemea.klarna@2.0.9_ (or later version) in your store. Learn more how to install the app at [Installing an app](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-installing-an-app).
     - __Adyen__: you need to [setting up Adyen affiliation](https://help.vtex.com/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337#). To complete this configuration, ask Adyen to enable the field __Live Endpoint URL Prefix__ in your shop and fill in according to the information described in [this documentation](https://www.adyen.help/hc/en-us/articles/360014322079-How-can-I-find-the-endpoint-URL-for-my-LIVE-account-).
 
-<div class="alert alert-warning">
-Klarna Pay Now and Klarna Pay Later are only enabled for SmartCheckout V6, and only customers from the European and US markets can use their solutions, so they are not applicable payment methods for Brazilian customers.
-</div>
+>⚠️ Klarna Pay Now and Klarna Pay Later are only enabled for SmartCheckout V6, and only customers from the European and US markets can use their solutions, so they are not applicable payment methods for Brazilian customers.
 
 ## Setting up Klarna affiliation
 
@@ -41,9 +39,7 @@ To configure Klarna affiliation, follow the steps below:
 6. Fill in the __Application Key__ and __Application Token__ fields with data provided by Klarna.
 7. Click on __Save__.  
 
-<div class="alert alert-warning">
-  If you are using the Klarna connector in a Test environment, the <b>Application Key</b> must be set to <i>playground.{Klarna User}</i>. When used in a Production environment, the <b>Application Key</b> field should be your <i>Klarna User</i>.
-</div>
+>⚠️ If you are using the Klarna connector in a Test environment, the **Application Key** must be set to <i>playground.{Klarna User}</i>. When used in a Production environment, the **Application Key** field should be your <i>Klarna User</i>.
 
 ## Klarna Pay Now
 
diff --git a/docs/tutorials/en/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md b/docs/tutorials/en/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
index 2ee6e75ac..be520d2e1 100644
--- a/docs/tutorials/en/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
+++ b/docs/tutorials/en/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
@@ -41,9 +41,7 @@ To configure Mercado Pago Offline, follow these steps:
   <br>
   <li>Below, click on the <b>Status</b> button to activate the rule.</li>
 <br>
-<div class="alert alert-info">
-  It is not necessary to select the <strong>Process with affiliation</strong>, as the sub-acquirer MercadoPagoV2 is already configured as the default affiliation for MercadoPagoOff.
-</div>
+>ℹ️ It is not necessary to select the **Process with affiliation**, as the sub-acquirer MercadoPagoV2 is already configured as the default affiliation for MercadoPagoOff.
 <br>
   <li>If you choose to use antifraud, enable the <b>Use antifraud solution</b> option and choose one of the available antifraud options.</li>
   <br>
diff --git a/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md b/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md
index 1a0cd0db5..12d1293f5 100644
--- a/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md
+++ b/docs/tutorials/en/setting-up-mercadopagov1-sub-acquirer.md
@@ -15,13 +15,11 @@ legacySlug: setting-up-mercadopagov1-sub-acquirer
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 With the VTEX gateway, you can configure the MercadoPago [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) to operate in various ways. __MercadoPagoV1__ allows your store to receive payments using debit and credit cards, in addition to Mercado Pago's [digital wallet](/en/faq/what-is-an-e-wallet).
 
-<div class="alert alert-warning">
-  The <strong>MercadoPagoV1</strong> integration does not support payment using boleto bancario (payment method in Brazil).
-</div>
+>⚠️ The **MercadoPagoV1** integration does not support payment using boleto bancario (payment method in Brazil).
 
 The steps below will let you set up MercadoPagoV1:
 
diff --git a/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
index dded50683..a09d09527 100644
--- a/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/en/setting-up-merchant-id-in-apple-pay.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-merchant-id-in-apple-pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-This process will be simpler as soon as Apple validates integrations with VTEX platform. This article will then be updated to fit the new scenario.
-</div>
+>⚠️ This process will be simpler as soon as Apple validates integrations with VTEX platform. This article will then be updated to fit the new scenario.
 
 In order for your store to begin receiving payments with __Apple Pay__, you will need to set __Merchant ID__ in your Apple developer account (`developer.apple.com`). 
 
@@ -90,9 +88,7 @@ Firstly, you need to validate each of the desired URLs. Once this step is correc
 
 Lastly, you need to import this file to VTEX's system through Postman - an [API](https://help.vtex.com/en/tutorial/introduction-to-vtex-apis--3SjAqQ0BeUqu2ge8AiIkmW "APIs") management tool.
 
-<div class="alert alert-warning">
-<strong>Important:</strong>nThis validation can only be done one domain at a time. This means that if your store uses 10 different domains, the process will have to be repeated 10 times.
-</div>
+>⚠️ **Important:**nThis validation can only be done one domain at a time. This means that if your store uses 10 different domains, the process will have to be repeated 10 times.
 
 Follow these steps:
 
@@ -128,9 +124,7 @@ Lastly, you must generate a Merchant ID certificate, which will be used every ti
 
 To complete the action, you'll need to create a password to protect the exported data.
 
-<div class="alert alert-info">
-Notice: we recommend an easy to remember password, since it will be filled into the Apple Merchant Password field upon configuring the gateway affiliation on VTEX's platform.
-</div>  
+>ℹ️ Notice: we recommend an easy to remember password, since it will be filled into the Apple Merchant Password field upon configuring the gateway affiliation on VTEX's platform.  
 
 1. Access the __Certificate, Identifiers & Profilers__ module;
 2. From the left side menu, choose __Identifiers__;
diff --git a/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md b/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md
index dedc9d616..e06a615c6 100644
--- a/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md
+++ b/docs/tutorials/en/setting-up-mundipagg-fraud-prevention-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-mundipagg-fraud-prevention-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Mundipagg offers a version of its [gateway](/en/tutorial/what-is-a-payment-gateway) with anti-fraud functionality. Mundipagg Fraud Prevention brings even more security to the processing of purchases made with bank slips, bank transfers and major credit card brands.
 
diff --git a/docs/tutorials/en/setting-up-mundipagg-gateway.md b/docs/tutorials/en/setting-up-mundipagg-gateway.md
index 2d51abf6b..7a60508d1 100644
--- a/docs/tutorials/en/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/en/setting-up-mundipagg-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-mundipagg-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Mundipagg is a [gateway](/en/tutorial/what-is-a-payment-gateway) that processes payments made with bank slips, bank transfers and major credit card brands.
 
diff --git a/docs/tutorials/en/setting-up-my-account.md b/docs/tutorials/en/setting-up-my-account.md
index af19ff149..895fc8e0e 100644
--- a/docs/tutorials/en/setting-up-my-account.md
+++ b/docs/tutorials/en/setting-up-my-account.md
@@ -31,6 +31,4 @@ To customize the page, you need to:
 2. Authenticate yourself using the __Receive email access code__ or __Access using email and password__ option
 3. Enter __My Account__, located in the upper left side of your screen next to __My Cart__
 
-<div class="alert alert-info">
-Stores created after May 15th, 2019, need not worry about customization adjustments, since the platform already comes with the native app.
-</div>
+>ℹ️ Stores created after May 15th, 2019, need not worry about customization adjustments, since the platform already comes with the native app.
diff --git a/docs/tutorials/en/setting-up-nethone-antifraud.md b/docs/tutorials/en/setting-up-nethone-antifraud.md
index f05eb3ada..23a966053 100644
--- a/docs/tutorials/en/setting-up-nethone-antifraud.md
+++ b/docs/tutorials/en/setting-up-nethone-antifraud.md
@@ -17,9 +17,7 @@ subcategory:
 
 Nethone is an anti-fraud solution that identifies specific aspects of user behavior and minimizes the risk of fraud in your store's transactions by using artificial intelligence and machine learning.
 
-<div class="alert alert-warning">
-  You can integrate your store with Nethone via <b>Application Key (App Key)</b> and <b>Application Token (App Token)</b>. You will find this information in the plugin package that Nethone will send you after you sign the contract. If you have any questions, please contact the Nethone support team. 
-  </div>
+>⚠️ You can integrate your store with Nethone via **Application Key (App Key)** and **Application Token (App Token)**. You will find this information in the plugin package that Nethone will send you after you sign the contract. If you have any questions, please contact the Nethone support team.
 
 To set up Nethone in your store, you will need to:
 
@@ -72,9 +70,7 @@ The next step for configuring the Nethone affiliation is integrating with Google
 
 ## Configuring Google Tag Manager
 
-<div class="alert alert-warning">
-The configurations documented below are to be performed on a system external to VTEX and may be discontinued without notice.
-  </div>
+>⚠️ The configurations documented below are to be performed on a system external to VTEX and may be discontinued without notice.
 
 Once you have configured your account ID number at checkout, follow the instructions below to track purchase attempts made in your store.
 
diff --git a/docs/tutorials/en/setting-up-nexxpago-gateway.md b/docs/tutorials/en/setting-up-nexxpago-gateway.md
index fd2e2634c..877ea0c0a 100644
--- a/docs/tutorials/en/setting-up-nexxpago-gateway.md
+++ b/docs/tutorials/en/setting-up-nexxpago-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-nexxpago-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Nexxpago is a [PCI-certified](/en/faq/what-is-the-pci-ssc) company that offers a variety of payment solutions. The main one is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) that allows processing payments through bank and credit cards.
 
diff --git a/docs/tutorials/en/setting-up-nps-gateway.md b/docs/tutorials/en/setting-up-nps-gateway.md
index 91710997a..a8cf62233 100644
--- a/docs/tutorials/en/setting-up-nps-gateway.md
+++ b/docs/tutorials/en/setting-up-nps-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-nps-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Ingenico ePayments (NPS) is a [gateway](/en/tutorial/what-is-a-payment-gateway) with a strong presence in Latin America which allows your store to accept various payment conditions.
 
diff --git a/docs/tutorials/en/setting-up-offline-payment-conditions-using-mercadopago.md b/docs/tutorials/en/setting-up-offline-payment-conditions-using-mercadopago.md
index e3879df84..2b2c32253 100644
--- a/docs/tutorials/en/setting-up-offline-payment-conditions-using-mercadopago.md
+++ b/docs/tutorials/en/setting-up-offline-payment-conditions-using-mercadopago.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-offline-payment-conditions-using-mercadopago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-This article deals with configurations applicable in stores that operate in the following Latin American countries: <strong>Argentina</strong>, <strong>Chile</strong>, <strong>Colombia</strong>, <strong>Mexico</strong>, <strong>Peru</strong>, <strong>Uruguay</strong> and <strong>Venezuela</strong>.
-</div>
+>⚠️ This article deals with configurations applicable in stores that operate in the following Latin American countries: **Argentina**, **Chile**, **Colombia**, **Mexico**, **Peru**, **Uruguay** and **Venezuela**.
 
 You can use Mercado Pago to offer offline payment conditions in your store. For that, you first have to register [MercadoPagoV1](/en/tutorial/setting-up-mercadopagov1-sub-acquirer) gateway affiliation.
 
diff --git a/docs/tutorials/en/setting-up-pagarmev2-gateway.md b/docs/tutorials/en/setting-up-pagarmev2-gateway.md
index f4281bb50..1a13cfae9 100644
--- a/docs/tutorials/en/setting-up-pagarmev2-gateway.md
+++ b/docs/tutorials/en/setting-up-pagarmev2-gateway.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 At VTEX, it is possible to process payments with the PagarMe provider through V2 and V3 integrations.
 
-<div class="alert alert-warning">
-If you want to configure the V3 version of Pagarme in your store, go to <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-pagarmev3--5PMavdamrVijwIrHas9ndE">Setting up payments with PagarMeV3</a>.
-</div>
+>⚠️ If you want to configure the V3 version of Pagarme in your store, go to [Setting up payments with PagarMeV3](https://help.vtex.com/en/tutorial/setting-up-payments-with-pagarmev3--5PMavdamrVijwIrHas9ndE).
 
 To configure PagarMeV2, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-pagbrasil-gateway.md b/docs/tutorials/en/setting-up-pagbrasil-gateway.md
index abf1588d5..259e2eb58 100644
--- a/docs/tutorials/en/setting-up-pagbrasil-gateway.md
+++ b/docs/tutorials/en/setting-up-pagbrasil-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-pagbrasil-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 PagBrasil is a gateway specialized in Brazilian payment methods, mainly credit and debit cards, online transfers, and bank vouchers.
 
diff --git a/docs/tutorials/en/setting-up-paghiper-gateway.md b/docs/tutorials/en/setting-up-paghiper-gateway.md
index 0cfefd29e..2cb4b3aac 100644
--- a/docs/tutorials/en/setting-up-paghiper-gateway.md
+++ b/docs/tutorials/en/setting-up-paghiper-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-paghiper-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 PagHiper is a [gateway](/en/tutorial/what-is-a-payment-gateway) specialized in the processing of purchases made through bank slips.
 
diff --git a/docs/tutorials/en/setting-up-payment-with-paypal.md b/docs/tutorials/en/setting-up-payment-with-paypal.md
index df8bd2b48..108656e48 100644
--- a/docs/tutorials/en/setting-up-payment-with-paypal.md
+++ b/docs/tutorials/en/setting-up-payment-with-paypal.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payment-with-paypal
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 At VTEX gateway, you can set up the PayPal sub-acquirer to receive your payments. Through it, your customer chooses the PayPal __payment method__ and performs their authentication in the PayPal environment.
 
diff --git a/docs/tutorials/en/setting-up-paymentez-gateway.md b/docs/tutorials/en/setting-up-paymentez-gateway.md
index 86adf5e58..f950fb3b3 100644
--- a/docs/tutorials/en/setting-up-paymentez-gateway.md
+++ b/docs/tutorials/en/setting-up-paymentez-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-paymentez-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Paymentez is a [gateway](/en/tutorial/what-is-a-payment-gateway) with [PCI certification](/en/faq/what-is-the-pci-ssc) level 2 and has its operations concentrated in Latin America.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-alignet.md b/docs/tutorials/en/setting-up-payments-with-alignet.md
index 03d768380..66a8c60e5 100644
--- a/docs/tutorials/en/setting-up-payments-with-alignet.md
+++ b/docs/tutorials/en/setting-up-payments-with-alignet.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payments-with-alignet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 On VTEX platform, you can set up the Alignet [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) to receive payments in your store. With it, your client chooses the __payment method__ Alignet and is redirected for authentication in the sub-acquirer's environment.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-apple-pay.md b/docs/tutorials/en/setting-up-payments-with-apple-pay.md
index 17678bf4d..49b846dce 100644
--- a/docs/tutorials/en/setting-up-payments-with-apple-pay.md
+++ b/docs/tutorials/en/setting-up-payments-with-apple-pay.md
@@ -20,9 +20,7 @@ Your customers can shop using Apple Pay, the [digital wallet](/en/faq/what-is-an
 - Have an account in `developer.apple.com`.
 - Hire a gateway that processes payments with Apple Pay.
 
-<div class="alert alert-warning">
-  Apple Pay currently only works on MacOs, IOS operating systems, and the Safari browser. For more information, go to <a href="https://support.apple.com/en-gb/HT208531">Devices compatible with Apple Pay</a>.
-</div>
+>⚠️ Apple Pay currently only works on MacOs, IOS operating systems, and the Safari browser. For more information, go to [Devices compatible with Apple Pay](https://support.apple.com/en-gb/HT208531).
 
 ## Setting up the payment provider
 
@@ -30,9 +28,7 @@ Firstly, you need to configure a provider in your store's Admin that processes t
 
 To check all the provider options available for this payment method, access the list as described in Step 5 of the section [Set up payment with Apple Pay](#setting-up-payment-with-apple-pay).
 
-<div class="alert alert-warning">
-  Before starting to configure the provider, you must <a href="register your Merchant ID with Apple Pay">register your Merchant ID with Apple Pay</a>.
-</div>
+>⚠️ Before starting to configure the provider, you must [register your Merchant ID with Apple Pay](register your Merchant ID with Apple Pay).
 
 ## Setting up payment with Apple Pay
 
diff --git a/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md b/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md
index acf3bef8a..75ce5215c 100644
--- a/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md
+++ b/docs/tutorials/en/setting-up-payments-with-cieloecommerce.md
@@ -47,9 +47,7 @@ To configure CieloEcommerce, follow the steps below:
 
 <blockquote><ui>14. In <b>AntifraudProvider</b>, select the antifraud provider you want to use with CieloEcommerce.</ui>
 
-<blockquote><div class="alert alert-warning">
-  Check with Cielo whether the anti-fraud options in CieloEcommerce are already available for use. If still under development, both fields described in step 15 must be left blank. For more information about using anti-fraud options in your store, visit <a href="https://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud">Configuring the anti-fraud</a>.
-  </div></blockquote>
+<blockquote>>⚠️ Check with Cielo whether the anti-fraud options in CieloEcommerce are already available for use. If still under development, both fields described in step 15 must be left blank. For more information about using anti-fraud options in your store, visit [Configuring the anti-fraud](https://help.vtex.com/en/tutorial/how-to-configure-the-anti-fraud).</blockquote>
 <br>  
 <blockquote><ui>15. In <b>Antifraud</b> and <b>AntifraudSequenceCriteria</b>, select the options according to information from CieloEcommerce antifraud.</ui>
 
diff --git a/docs/tutorials/en/setting-up-payments-with-credimarcas.md b/docs/tutorials/en/setting-up-payments-with-credimarcas.md
index e4c08dbfb..b91fd0982 100644
--- a/docs/tutorials/en/setting-up-payments-with-credimarcas.md
+++ b/docs/tutorials/en/setting-up-payments-with-credimarcas.md
@@ -39,9 +39,7 @@ To configure Credimarcas provider, follow the steps below:
 
 ## Setting up Notes Payable
 
-<div class="alert alert-warning">
-  <p>If you have not yet configured the Notes Payable as a payment method in other connectors in your store, go to <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable">Setting up payments with Notes Payable</a>.</p>
-</div>
+>⚠️ If you have not yet configured the Notes Payable as a payment method in other connectors in your store, go to [Setting up payments with Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable).
 
 To use Credimarcas with notes payable, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-payments-with-itau-rede.md b/docs/tutorials/en/setting-up-payments-with-itau-rede.md
index 97e75cac9..8f05fdce3 100644
--- a/docs/tutorials/en/setting-up-payments-with-itau-rede.md
+++ b/docs/tutorials/en/setting-up-payments-with-itau-rede.md
@@ -25,9 +25,7 @@ To use Itaú Rede, you must:
 
 ## Obtain credentials in the Userede environment
 
-<div class="alert alert-warning">
-Configurations made in an environment external to VTEX may be discontinued or modified without prior notice. Check your Itaú Rede account for updated information.
-</div>
+>⚠️ Configurations made in an environment external to VTEX may be discontinued or modified without prior notice. Check your Itaú Rede account for updated information.
 
 To obtain the __App key__ and __App token__ credentials necessary to configure Itaú Rede on VTEX, follow the steps below:
 
@@ -59,9 +57,7 @@ To obtain the __App key__ and __App token__ credentials necessary to configure I
 
 <blockquote><ui>8. After creating the new key, click <b>copiar</b> and preserve the information in a safe location. This key must be used in the <b>Token de aplicação</b> field in the section <a href="#setting-up-itau-rede-on-vtex">Setting up Itaú Rede on VTEX</a>.
 
-<blockquote><ui><div class="alert alert-warning">
-Once an "chave de integração" is created in the Network environment, it cannot be accessed again from other locations. Record the "chave" information in a protected location, and if lost, repeat the process to generate a new key.
-  </div></ui></blockquote>
+<blockquote><ui>>⚠️ Once an "chave de integração" is created in the Network environment, it cannot be accessed again from other locations. Record the "chave" information in a protected location, and if lost, repeat the process to generate a new key.</ui></blockquote>
 
 ## Setting up Itaú Rede on VTEX
 
diff --git a/docs/tutorials/en/setting-up-payments-with-iugu.md b/docs/tutorials/en/setting-up-payments-with-iugu.md
index 583873c4b..8ca2188ca 100644
--- a/docs/tutorials/en/setting-up-payments-with-iugu.md
+++ b/docs/tutorials/en/setting-up-payments-with-iugu.md
@@ -44,9 +44,7 @@ To process credit card, pix and bank slip payment methods with iugu in your stor
 
 After following the indicated steps, iugu provider may take up to 10 minutes to appear at your store's checkout as a payment option.
 
-<div class="alert alert-warning">
-  Before carrying out transactions by credit card, PIX or bank slip with iugu in your store, check whether these payment methods are already enabled in <a href="https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento">your customer area on the iugu portal</a>.
-  </div>
+>⚠️ Before carrying out transactions by credit card, PIX or bank slip with iugu in your store, check whether these payment methods are already enabled in [your customer area on the iugu portal](https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento).
 
 ## Setting up split payment on the marketplace with iugu
 
@@ -64,15 +62,11 @@ To enable payout split with iugu in your store, follow the steps below:
 4. In __Payment control__, select the option __Enable payout split and send payment recipients__ and indicate the __Accountable for payment processing charges__ and __Accountable for chargebacks__ (marketplace, sellers or marketplaces and sellers).
 5. Click `Save`.
 
-<div class="alert alert-warning">
-  The payout split option is not available for use in a test environment.
-  </div>
+>⚠️ The payout split option is not available for use in a test environment.
 
 After following the steps indicated, the payout split functionality with the iugu provider may take up to 10 minutes to be activated in your store.
 
-<div class="alert alert-warning">
-  To define specific commissions for each seller in your store, access <b>Marketplace > Sellers> Management</b> in the VTEX Admin, select the desired seller and enter the commission values in <b>Commissions</b>.
-  </div>
+>⚠️ To define specific commissions for each seller in your store, access **Marketplace > Sellers> Management** in the VTEX Admin, select the desired seller and enter the commission values in **Commissions**.
 
 ## Setting up recurrence with iugu
 
diff --git a/docs/tutorials/en/setting-up-payments-with-koin.md b/docs/tutorials/en/setting-up-payments-with-koin.md
index c3cdc301e..e1bbf06fa 100644
--- a/docs/tutorials/en/setting-up-payments-with-koin.md
+++ b/docs/tutorials/en/setting-up-payments-with-koin.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payments-with-koin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 You can set up Koin to receive payments at your store. Through it, your customer chooses the Koin Post-pay payment method to make the purchase.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-mercado-pago.md b/docs/tutorials/en/setting-up-payments-with-mercado-pago.md
index 278409198..dbba3208a 100644
--- a/docs/tutorials/en/setting-up-payments-with-mercado-pago.md
+++ b/docs/tutorials/en/setting-up-payments-with-mercado-pago.md
@@ -39,9 +39,7 @@ Below are the settings for __Mercado Pago__ connector.
 12. In the __Tipo de estorno__ field ("Refund type"), choose between the automatic process or the manual request (in this case, MercadoPago will send an e-mail notifying the pending refund).
 13. Click __Save__.
 
-<div class="alert alert-warning">
-The step indicated in item <strong>11</strong> is performed in an environment outside VTEX. Therefore, such process can be updated without prior notice.
-</div>
+>⚠️ The step indicated in item **11** is performed in an environment outside VTEX. Therefore, such process can be updated without prior notice.
 
 ## Setting up MercadoPago payment condition
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings > Payment conditions**, or type **Settings** in the search bar at the top of the page. click on the  tab.
diff --git a/docs/tutorials/en/setting-up-payments-with-notes-payable.md b/docs/tutorials/en/setting-up-payments-with-notes-payable.md
index 40a70b788..f6e461092 100644
--- a/docs/tutorials/en/setting-up-payments-with-notes-payable.md
+++ b/docs/tutorials/en/setting-up-payments-with-notes-payable.md
@@ -25,9 +25,7 @@ On VTEX, your store can receive payments made with __Notes Payable__. To enable
 
 To set up a gateway affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
 
-<div class="alert alert-warning">
-Check that the desired gateway affiliation supports Notes Payable payment processing.
-</div>
+>⚠️ Check that the desired gateway affiliation supports Notes Payable payment processing.
 
 ## Notes Payable Setup
 
diff --git a/docs/tutorials/en/setting-up-payments-with-nuvei.md b/docs/tutorials/en/setting-up-payments-with-nuvei.md
index d82dab85c..834b9fd4c 100644
--- a/docs/tutorials/en/setting-up-payments-with-nuvei.md
+++ b/docs/tutorials/en/setting-up-payments-with-nuvei.md
@@ -38,17 +38,13 @@ To use Nuvei, follow the steps below:
 
 <blockquote><ui>7. To fill in the fields <b>Merchant Id</b>, <b>Merchant Site Id</b> and <b>Client Secret</b> (Secret Key), access the information available in <b>Settings > My Integration Settings</b> within the control panel of your account in the Nuvei environment.</ui>
 
-<blockquote><ui><div class="alert alert-warning">
- Nuvei has specific credentials (Merchant Id, Merchant Site Id and Client Secret) for each type of environment. Access the test <a href="sandbox.nuvei.com">(Integration)</a> and <a href="cpanel.nuvei.com">Live</a> environments to identify the credentials relating to each of them.
-  </div></blockquote>
+<blockquote><ui>>⚠️ Nuvei has specific credentials (Merchant Id, Merchant Site Id and Client Secret) for each type of environment. Access the test [(Integration)](sandbox.nuvei.com) and [Live](cpanel.nuvei.com) environments to identify the credentials relating to each of them.</blockquote>
 <br>  
 <blockquote><ui>8. In <b>Environment</b>, select whether you want to configure the Nuvei provider in the <b>Integration</b> or <b>Live</b> environment.</ui>
 
 <blockquote><ui>9. In <b>Test 3ds challenge Integration only</b>, if you have selected the test environment (<b>Integration</b>) it is possible to perform 3DS security tests using the <b>Force 3ds Challenge</b>, <b>Force 3ds Frictionless</b> or <b>User cardHolder name</b> options. For more information about the tests, access the <a href="https://docs.nuvei.com/documentation/integration/testing/testing-cards/?highlight=test%20cards#3d-secure-v2-test-scenarios">Nuvei</a> documentation.</ui>
 
- <blockquote><ui><div class="alert alert-warning">
-   Whenever the provider's <b>Environment</b> is configured as <b>Live</b>, the option selected for the <b>Test 3ds challenge Integration only</b> field must be <b>User cardHolder name</b>.
-  </div></blockquote>
+ <blockquote><ui>>⚠️ Whenever the provider's **Environment** is configured as **Live**, the option selected for the **Test 3ds challenge Integration only** field must be **User cardHolder name**.</blockquote>
 <br>  
 <blockquote><ui>10. Click <b>Save</b>.</ui>
 
diff --git a/docs/tutorials/en/setting-up-payments-with-pagosweb.md b/docs/tutorials/en/setting-up-payments-with-pagosweb.md
index 857427023..0851d2338 100644
--- a/docs/tutorials/en/setting-up-payments-with-pagosweb.md
+++ b/docs/tutorials/en/setting-up-payments-with-pagosweb.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payments-with-pagosweb
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 You can set up PagosWEB to receive payments in your store. With it, your customer chooses PaymentsWEB __payment method__ to make the purchase.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-payclub.md b/docs/tutorials/en/setting-up-payments-with-payclub.md
index 2f1790a30..fe632424b 100644
--- a/docs/tutorials/en/setting-up-payments-with-payclub.md
+++ b/docs/tutorials/en/setting-up-payments-with-payclub.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payments-with-payclub
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 You can configure PayClub [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) to receive payments at your store. With it, your client chooses the __payment method__ PayClub and performs the authentication in the external environment of the payment solution.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-promissory.md b/docs/tutorials/en/setting-up-payments-with-promissory.md
index 7f89f3c65..cde431021 100644
--- a/docs/tutorials/en/setting-up-payments-with-promissory.md
+++ b/docs/tutorials/en/setting-up-payments-with-promissory.md
@@ -25,9 +25,7 @@ On VTEX, your store can receive payments made with __Promissories__. To enable t
 
 To set up a gateway affiliation, access [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
-<div class="alert alert-warning">
-Check that the desired gateway affiliation supports promissory payment processing.
-</div>
+>⚠️ Check that the desired gateway affiliation supports promissory payment processing.
 
 ## Promissory Setup
 
diff --git a/docs/tutorials/en/setting-up-payments-with-pse.md b/docs/tutorials/en/setting-up-payments-with-pse.md
index 79d27816f..083661044 100644
--- a/docs/tutorials/en/setting-up-payments-with-pse.md
+++ b/docs/tutorials/en/setting-up-payments-with-pse.md
@@ -21,8 +21,7 @@ To enable PSE in your store, the following actions are required:
 - [Install and configure the Banks for PSE App](#installing-banks-for-pse-app).
 - [Setting up the PSE payment method](#setting-up-the-pse-payment-method).
 
-<div class="alert alert-warning">
-To configure the PSE app in your store, you must have permission to access the Payments module. If you still do not have this access, request it through the <a href="https://help.vtex.com/support">VTEX Support</a>.</div>
+>⚠️ To configure the PSE app in your store, you must have permission to access the Payments module. If you still do not have this access, request it through the [VTEX Support](https://help.vtex.com/support).
 
 ## Installing Banks for PSE App
 
diff --git a/docs/tutorials/en/setting-up-payments-with-stelo.md b/docs/tutorials/en/setting-up-payments-with-stelo.md
index 76e727ac9..15a686918 100644
--- a/docs/tutorials/en/setting-up-payments-with-stelo.md
+++ b/docs/tutorials/en/setting-up-payments-with-stelo.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payments-with-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 In addition to a [sub-acquirer](/en/tutorial/setting-up-sub-acquirer-stelo) that processes transactions carried out with various payment conditions, Stelo also offers a [digital wallet service](/en/faq/what-is-an-e-wallet). Your customer chooses to pay with it and is redirected to authentication in Stelo's environment.
 
diff --git a/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md b/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md
index a6279ee32..0823e4564 100644
--- a/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md
+++ b/docs/tutorials/en/setting-up-payments-with-store-card-cobranded.md
@@ -29,9 +29,7 @@ The first configuration step will be the creation of the custom payment __(cobra
 7. In __BIN ranges (optional)__, 
 you can enter a range of BINs (by entering the first and last code in the sequence, separated by a hyphen) or several (separating each range by a comma and without spaces).
 
-<div class="alert alert-warning">
-  When the customer enters a bin number outside the range specified in this field, the following message will be displayed "Check the digits printed on your card. We couldn't confirm if the card number is correct". If there is no error in the number entered, they can click on "YES, THE NUMBER IS CORRECT" to continue completing the order.
-</div>
+>⚠️ When the customer enters a bin number outside the range specified in this field, the following message will be displayed "Check the digits printed on your card. We couldn't confirm if the card number is correct". If there is no error in the number entered, they can click on "YES, THE NUMBER IS CORRECT" to continue completing the order.
 
 <blockquote><ui>8. In the field <b>Acquirer Payment Code (optional)</b>, enter the code to be sent and processed by the acquirer you have contracted.</ui>
 
@@ -42,9 +40,7 @@ you can enter a range of BINs (by entering the first and last code in the sequen
 ## Set up payment condition
 After configuring the card, you will need to configure the payment condition.
 
-<div class="alert alert-warning">
-  If the connector to be chosen (in <b>Step.8</b>)is not registered in your store, the message "(Configure)" will be displayed after the connector name. In this situation, choose another available connector or register it. For more information, see <a href="https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Registering gateway affiliations</a>.
-</div>
+>⚠️ If the connector to be chosen (in **Step.8**)is not registered in your store, the message "(Configure)" will be displayed after the connector name. In this situation, choose another available connector or register it. For more information, see [Registering gateway affiliations](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 1. In the VTEX Admin, go to **Store Settings** > **Payment** > **Settings**, or type **Settings** in the search bar at the top of the page.
 2. In the Gateway affiliations tab, click on the __"+"__ button.
diff --git a/docs/tutorials/en/setting-up-paypal-plus.md b/docs/tutorials/en/setting-up-paypal-plus.md
index 90e26eb78..5da90a6d6 100644
--- a/docs/tutorials/en/setting-up-paypal-plus.md
+++ b/docs/tutorials/en/setting-up-paypal-plus.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-paypal-plus
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 At VTEX Payments, you can set up the PayPal Plus sub-acquirer, PayPal's transparent checkout. Through this payment mode, the client simply enters their credit card information and finishes the purchase normally. Payment is made directly on your site, without the need to redirect your customers.
 
diff --git a/docs/tutorials/en/setting-up-payu-gateway.md b/docs/tutorials/en/setting-up-payu-gateway.md
index 4cbebce76..db75b2cbc 100644
--- a/docs/tutorials/en/setting-up-payu-gateway.md
+++ b/docs/tutorials/en/setting-up-payu-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payu-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 PayU is a [gateway](/en/tutorial/what-is-a-payment-gateway) that offers a number of solutions to make transactions in your store easier and safer. With [PCI certification](/en/faq/what-is-the-pci-ssc), this solution is exclusive for Argentina, Brazil, Chile, Colombia, Mexico, Panama and Peru.
 
diff --git a/docs/tutorials/en/setting-up-payu-global-gateway.md b/docs/tutorials/en/setting-up-payu-global-gateway.md
index 4d913ac51..9939255f0 100644
--- a/docs/tutorials/en/setting-up-payu-global-gateway.md
+++ b/docs/tutorials/en/setting-up-payu-global-gateway.md
@@ -17,8 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 PayU Global is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) that offers a number of solutions to make transactions in your store easier and safer. With [PCI certification](/en/faq/what-is-the-pci-ssc), this solution is exclusive to Romanian stores.
 
-<div class="alert alert-info"> Attention: currently, VTEX only supports versions 1.0.0 and 1.0.1 of PaymentsOS. 
-</div>
+>ℹ️ Attention: currently, VTEX only supports versions 1.0.0 and 1.0.1 of PaymentsOS.
 
 To set up Global PayU, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-payzen-gateway.md b/docs/tutorials/en/setting-up-payzen-gateway.md
index 146f63817..4dcbb4534 100644
--- a/docs/tutorials/en/setting-up-payzen-gateway.md
+++ b/docs/tutorials/en/setting-up-payzen-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-payzen-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 With VTEX, you can set up [PayZen gateway](/en/tutorial/what-is-a-payment-gateway) in your store. Easily integrated, it follows the security standards defined by [Payments](/en/faq/what-is-the-pci-ssc).
 
diff --git a/docs/tutorials/en/setting-up-place2pay-gateway.md b/docs/tutorials/en/setting-up-place2pay-gateway.md
index 85e10287d..999112d28 100644
--- a/docs/tutorials/en/setting-up-place2pay-gateway.md
+++ b/docs/tutorials/en/setting-up-place2pay-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-place2pay-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Place2Pay is the redirect version of the PlaceToPay gateway, which offers solutions for both large and small stores.
 
diff --git a/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md b/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md
index 42249754a..94c10d2b9 100644
--- a/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md
+++ b/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md
@@ -23,13 +23,9 @@ To regionalize SKU prices and availability, it is necessary:
 2. [White Label Sellers](https://help.vtex.com/en/faq/what-are-franchise-account-and-seller-white-label) can deliver orders from your store to determined ZIP code areas.
 3. The user's session browsing the store contains information about their zip code and country of origin.
 
-<div class="alert alert-info">
-In order to use this feature, a store must have installed the (<a href="https://help.vtex.com/pt/tutorial/vtex-session-visao-geral-do-sistema-de-sessoes--6C4Edou6bYqqEAOCAg2MQQ#">VTEX Session</a>) system. The VTEX Session is native to all stores and you can confirm its instalation by checking the presence of the <code>vtex_session</code> and <code>vtex_segment</code> when browsing the store.
-</div>
+>ℹ️ In order to use this feature, a store must have installed the ([VTEX Session](https://help.vtex.com/pt/tutorial/vtex-session-visao-geral-do-sistema-de-sessoes--6C4Edou6bYqqEAOCAg2MQQ#)) system. The VTEX Session is native to all stores and you can confirm its instalation by checking the presence of the `vtex_session` and `vtex_segment` when browsing the store.
 
-<div class="alert alert-warning">
-In case of <a href="https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#">Multilevel Omnichannel Inventory</a>, a marketplace (level 1) cannot configure the display of prices and availability of White Label Seller products (level 3) with the regionalization feature.
-</div>
+>⚠️ In case of [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#), a marketplace (level 1) cannot configure the display of prices and availability of White Label Seller products (level 3) with the regionalization feature.
 
 <div class = "alert alert-info">
 The feature <b>Region</b> works for both CMS Portal Legacy stores and stores developed using <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC">VTEX IO</a>, but the feature <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a> is available only for stores using VTEX IO. As a result, stores with CMS Portal Legacy have a limitation in indexing regionalized data, and it is not possible to correctly order the sellers that serve the storefront of a RegionId based on the availability of items.
@@ -48,5 +44,4 @@ To configure delivery, follow the steps below:
 5. Register an [Inventory](https://help.vtex.com/en/tutorial/gerenciar-estoque--tutorials_137#).
 6. [Add stock for SKUs](https://help.vtex.com/en/tutorial/managing-stock-items) that will be delivered through the configured route.
 
-<div class="alert alert-info">
-For an SKU to appear as available for sale, it needs to have stock and price associated with it.</div>
+>ℹ️ For an SKU to appear as available for sale, it needs to have stock and price associated with it.
diff --git a/docs/tutorials/en/setting-up-price-tables-for-specific-users.md b/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
index 6a411246b..0b30a575e 100644
--- a/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/en/setting-up-price-tables-for-specific-users.md
@@ -21,9 +21,7 @@ Unlike trade policies, which can also be used to segment prices, there is no lim
 
 For example, let's say you want customers in São Paulo to see a price different from the price seen by customers in Rio de Janeiro. In this case, you can create two different price lists, and associate the first one to the customers in São Paulo, and the second to those in Rio de Janeiro.
 
-<div class="alert alert-info">
-<p>You can define fixed prices or price rules to modify the price of an SKU in a price table.</p>
-</div>
+>ℹ️ You can define fixed prices or price rules to modify the price of an SKU in a price table.
 
 This gives the retailer more freedom to handle contextual information from their customers. 
 
@@ -63,9 +61,8 @@ Another way to use Price Tables is by declaring them directly on the customer fo
 10. In the row of the entity you have edited, click on the floppy disk icon to publish it.
 11. Then, click on the arrows icon to reindex it.
 
-<div class="alert alert-info">
-<p>Each customer can have up to 5 Price Tables associated with them.
-When the customer has more than one Price Table linked to them, the system will follow the order in which the Price Tables were created to determine the price of each SKU. If the SKU does not have a price configured in the first Price Table, the system will look for a price in the second one, and so on. In case there is no price configured in any of the Price Tables, the base price will be applied.</p></div>
+>ℹ️ Each customer can have up to 5 Price Tables associated with them.
+> When the customer has more than one Price Table linked to them, the system will follow the order in which the Price Tables were created to determine the price of each SKU. If the SKU does not have a price configured in the first Price Table, the system will look for a price in the second one, and so on. In case there is no price configured in any of the Price Tables, the base price will be applied.
 
 Now your Customers entity has a `priceTables` attribute, which can be populated directly in the Master Data UI or via API.
 
@@ -87,9 +84,7 @@ To update a fixed price in a specific table, on the column corresponding to that
 
 To enter and update prices from a specific table via API, check out the [Pricing API documentation](https://developers.vtex.com/reference/prices-and-fixed-prices#createeditfixedpricesonapricetableortradepolicy).
 
-<div class="alert alert-info">
-<p>The Price Table has priority over the prices from the trade Policy. If a given Price Table applies to a user's context, the price set in it will be used, even if that customer is also within the context of a trade policy with a different price.</p>
-</div>
+>ℹ️ The Price Table has priority over the prices from the trade Policy. If a given Price Table applies to a user's context, the price set in it will be used, even if that customer is also within the context of a trade policy with a different price.
 
 ## Displaying different prices for different users
 
@@ -104,6 +99,4 @@ When Daniel, who is linked to the Silver price table, is logged into the store,
 
 Breno, who is linked to the Gold price table, will see the prices set on this table. He would pay USD 60.50 for the same backpack.
 
-<div class="alert alert-warning">
-The customer <strong> must </ strong> be authenticated — through token, password, Google, or Facebook — to see the prices that apply to them. Otherwise, the price shown will be the default price. Please note that entering the email address at checkout is not enough, since in this process the customer is identified, but not authenticated.
-</div>
+>⚠️ The customer <strong> must </ strong> be authenticated — through token, password, Google, or Facebook — to see the prices that apply to them. Otherwise, the price shown will be the default price. Please note that entering the email address at checkout is not enough, since in this process the customer is identified, but not authenticated.
diff --git a/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md b/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md
index 074cfc219..8d049b35b 100644
--- a/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md
+++ b/docs/tutorials/en/setting-up-rede-acquirer-with-erederest.md
@@ -15,13 +15,11 @@ legacySlug: setting-up-rede-acquirer-with-erederest
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 In VTEX, you can integrate with the [acquirer](/en/tutorial/what-is-an-acquirer) Rede using the ERedeREST connector. This connector brings a number of enhancements, including pre-authorization support (__Visa__, __Mastercard__, __American Express__, __Diners__, __Hipercard__, __JCB__ and __Credz__).
 
-<div class="alert alert-warning">
-The <strong>Elo</strong> brand does not yet support pre-authorization.
-</div>
+>⚠️ The **Elo** brand does not yet support pre-authorization.
 
 Another important feature of the ERedeREST connector is that you can also configure it to accept payments with [__Apple Pay __](/en/tutorial/setting-up-payments-with-apple-pay).
 
diff --git a/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md b/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md
index 4bebe57b9..b517d3038 100644
--- a/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md
+++ b/docs/tutorials/en/setting-up-seller-white-label-as-a-pickup-point.md
@@ -23,9 +23,7 @@ As explained in the article [Definition of Franchise Account and Seller White La
 
 This way, the pickup point configured in the Franchise Account __ will be used to fulfill the deliveries of the orders placed in the Main Account__. In this scenario, the Franchise Account acts as the __Seller White Label__ of the Main Account.
 
-<div class="alert alert-danger">
-Settings must be made in the White Label Seller account. Items will only be available for pickup at the end customer checkout if the SKU is available in stock in both the master account and the White Label Seller account.
-</div>
+>❗ Settings must be made in the White Label Seller account. Items will only be available for pickup at the end customer checkout if the SKU is available in stock in both the master account and the White Label Seller account.
 
 ## Initial setup
 
@@ -48,9 +46,7 @@ To know more about filling out the spreadsheet fields, access our article [Fill
 
 If the pickup point configuration has been correctly made in the Franchise Account, SKUs with __stock available and price__ may be sold on the Main Account, where the Franchise Account will act as a __Seller White Label__ and the Main Account will function as a __Marketplace__.
 
-<div class="alert alert-warning">
-Make sure your franchise seller is active. In your VTEX Admin, go to <b>Marketplace > Sellers > Management</b>, and in the seller row in column <i>Status</i>, click <code>Active</code>.
-</div>
+>⚠️ Make sure your franchise seller is active. In your VTEX Admin, go to **Marketplace > Sellers > Management**, and in the seller row in column <i>Status</i>, click `Active`.
 
 ### Seller White Label/Franchise Account
 
diff --git a/docs/tutorials/en/setting-up-shipment.md b/docs/tutorials/en/setting-up-shipment.md
index 37ebd03ce..f68cfb359 100644
--- a/docs/tutorials/en/setting-up-shipment.md
+++ b/docs/tutorials/en/setting-up-shipment.md
@@ -17,9 +17,7 @@ subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 
 This configuration is widely used when a large volume of orders ends up generating a considerable logistic demand, so it's possible for a package to wait during the preparation time of another package, so they may be sent in a group, by the same transporter, to a final destination.
 
-<div class="alert alert-warning">
-The shipping groups are raised by the sum of the time cost from inventory to warehouse dock and the detention time of the dock itself.
-</div>
+>⚠️ The shipping groups are raised by the sum of the time cost from inventory to warehouse dock and the detention time of the dock itself.
 
 In the image below we see a __6 days__ shipment configuration. Each box represents the cost in days of a package, considering only the __stock and the dock cost.__
 
diff --git a/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md b/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md
index 20daaaba5..3d741ad02 100644
--- a/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md
+++ b/docs/tutorials/en/setting-up-sitef-gateway-with-pre-auth.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-sitef-gateway-with-pre-auth
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 In order to allow purchases made with credit card to have the amount reserved, you may set up the __Sitef gateway with pre-auth__ (pre-authorization) in your store.
 
diff --git a/docs/tutorials/en/setting-up-sitef-gateway.md b/docs/tutorials/en/setting-up-sitef-gateway.md
index dcda8cf0c..fa54a130e 100644
--- a/docs/tutorials/en/setting-up-sitef-gateway.md
+++ b/docs/tutorials/en/setting-up-sitef-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-sitef-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 In VTEX, you can configure the Sitef gateway. To configure it, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-up-sub-acquirer-stelo.md b/docs/tutorials/en/setting-up-sub-acquirer-stelo.md
index 2c9d861ce..8eae5a207 100644
--- a/docs/tutorials/en/setting-up-sub-acquirer-stelo.md
+++ b/docs/tutorials/en/setting-up-sub-acquirer-stelo.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-sub-acquirer-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 Stelo is a [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) that facilitates the integration of payment methods into your store.
 
diff --git a/docs/tutorials/en/setting-up-the-global-category.md b/docs/tutorials/en/setting-up-the-global-category.md
index 2e510e868..f72a260ef 100644
--- a/docs/tutorials/en/setting-up-the-global-category.md
+++ b/docs/tutorials/en/setting-up-the-global-category.md
@@ -19,9 +19,7 @@ The global category tree is the taxonomy created by Google for the [Merchant Cen
 
 The same global categories are available for products from all stores.
 
-<div class="alert alert-info">
-For every category of your store, you need to choose a global category.
-</div>
+>ℹ️ For every category of your store, you need to choose a global category.
 
 ### Why use it?
 
@@ -29,9 +27,7 @@ We have adopted this taxonomy because it's widely applicable to any context, and
 
 It is used, for example, as a reference for the integration of products with Amazon, Buscapé and marketplaces.
 
-<div class="alert alert-info">
-The default behavior of our integration with Google Shopping is <strong>not to send</strong> this information. Thus, most stores rely on Google's own automatic categorization. If you prefer manual categorization, <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM" target="_blank">contact support</a>.
-</div>
+>ℹ️ The default behavior of our integration with Google Shopping is **not to send** this information. Thus, most stores rely on Google's own automatic categorization. If you prefer manual categorization, [contact support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM" target="_blank).
 
 ### When is it applied?
 
@@ -59,9 +55,7 @@ You must choose the global category that most closely matches your product. Your
 
 Ideally, it would be best if you determined the global category in the category settings. This way, all products in a given category will belong to the same global category.
 
-<div class="alert alert-danger">
-Choosing a global category when adding a product is only recommended if it needs to be configured differently from the products in the category it belongs to.
-</div>
+>❗ Choosing a global category when adding a product is only recommended if it needs to be configured differently from the products in the category it belongs to.
 
 You must configure the global category in the Admin. Please follow the steps below:
 
@@ -74,6 +68,4 @@ You must configure the global category in the Admin. Please follow the steps bel
 7. Type the name of the category you want to find and click on the <i class="fas fa-search"></i> button.
 8. Select a category and then click on the `Save` button.
 
-<div class="alert alert-info">
-You can also configure the global category via <a href="https://help.vtex.com/en/tutorial/configuring-xml--tutorials_242">XML</a> file.
-</div>
+>ℹ️ You can also configure the global category via [XML](https://help.vtex.com/en/tutorial/configuring-xml--tutorials_242) file.
diff --git a/docs/tutorials/en/setting-up-the-logistics-for-instore.md b/docs/tutorials/en/setting-up-the-logistics-for-instore.md
index 611179281..607c71976 100644
--- a/docs/tutorials/en/setting-up-the-logistics-for-instore.md
+++ b/docs/tutorials/en/setting-up-the-logistics-for-instore.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-the-logistics-for-instore
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-<div class="alert alert-info">
-Warning: This documentation is being updated to reflect the concept change from Dashboards to <a href="https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">shipping strategy</a>.
-</div>
+>ℹ️ Warning: This documentation is being updated to reflect the concept change from Dashboards to [shipping strategy](https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).
 
 
 In order for inStore to work properly, you should create a specific logistics configuration. inStore must be configured with a __pickup point__. The process registering this pickup point consists of two steps:
diff --git a/docs/tutorials/en/setting-up-the-moip-sub-acquirer.md b/docs/tutorials/en/setting-up-the-moip-sub-acquirer.md
index 9ea8ff6b5..d4db115a0 100644
--- a/docs/tutorials/en/setting-up-the-moip-sub-acquirer.md
+++ b/docs/tutorials/en/setting-up-the-moip-sub-acquirer.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Moip is a [sub-acquirer](/en/tutorial/what-is-a-sub-acquirer) that provides a single integration to connect your store with all parties involved in the payment flow. as well as protection against fraud and a [transparent checkout solution](/en/tutorial/what-is-transparent-checkout) with no redirects.
 
-<div class="alert alert-warning">
-The information in this article are just configuration references for merchants who are already using the Moip sub-acquirer. For new affiliations, we recommend using the sub-acquirer <a href="https://help.vtex.com/en/tutorial/configurar-o-subadquirente-moipv2--4BipUcTxQ7cq2BiYzUDmEH">MoipV2</a>.
-  </div>
+>⚠️ The information in this article are just configuration references for merchants who are already using the Moip sub-acquirer. For new affiliations, we recommend using the sub-acquirer [MoipV2](https://help.vtex.com/en/tutorial/configurar-o-subadquirente-moipv2--4BipUcTxQ7cq2BiYzUDmEH).
 
 To configure Moip in your store, follow the steps below:
 
@@ -40,9 +38,7 @@ To configure Moip in your store, follow the steps below:
   6. Click on <b>Save</b>
   </ui><br><br>
 
-<div class="alert alert-warning">
-Moip does not process transactions if there are products costing "US$0" in the shopping cart.  For example, suppose you create a gift wrap product as an <a href="https://help.vtex.com/en/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete">attachment</a>. In this case, this item’s price will be US$0, preventing the payment from being processed.
-  </div>
+>⚠️ Moip does not process transactions if there are products costing "US$0" in the shopping cart.  For example, suppose you create a gift wrap product as an [attachment](https://help.vtex.com/en/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete). In this case, this item’s price will be US$0, preventing the payment from being processed.
 
 ## Setting up the payment condition
 
diff --git a/docs/tutorials/en/setting-up-the-notify-me-option.md b/docs/tutorials/en/setting-up-the-notify-me-option.md
index 99988f3a0..23108a19c 100644
--- a/docs/tutorials/en/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/en/setting-up-the-notify-me-option.md
@@ -15,9 +15,7 @@ legacySlug: set-up-the-notify-me
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-<div class="alert alert-warning">
-<p>This article explains how to set up the <strong>Notify me</strong> feature in stores that use <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">Legacy CMS Portal</a>. For stores using <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, the setup follows the steps described in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify">Availability Notify</a> guide.</p>
-</div>
+>⚠️ This article explains how to set up the **Notify me** feature in stores that use [Legacy CMS Portal](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). For stores using [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), the setup follows the steps described in the [Availability Notify](https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify) guide.
 
 When a product is out of [stock](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139), the retailer may choose to make the **Notify me** feature available to the customer. This feature allows interested customers to be notified by email when the item is available again.
 
diff --git a/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
index 76fa6773a..e6d786560 100644
--- a/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/en/setting-up-the-sales-funnel-on-google-analytics.md
@@ -19,9 +19,7 @@ subcategory: 1luKrYptdi8WoMYckakUaM
 
 With the sales funnel configured, you can track and analyze the customer's steps until the completion of an order. To set up the sales funnel, let's take into account that the purchase process starts on your product screen and goes through the shopping cart, checkout (personal data, shipping, payment) and reaches the goal, which is the order placed page.
 
-<div class="alert alert-info">
-To make it easier, the entire setup in this article can be <a href="https://support.google.com/analytics/answer/1032415?hl=en" target="_blank">imported directly into Google Analytics</a> with <a href="https://analytics.google.com/analytics/web/template?uid=tTp2GkIJRiGodszJbq8RsA" target="_blank">this template</a>.
-</div>
+>ℹ️ To make it easier, the entire setup in this article can be [imported directly into Google Analytics](https://support.google.com/analytics/answer/1032415?hl=en" target="_blank) with [this template](https://analytics.google.com/analytics/web/template?uid=tTp2GkIJRiGodszJbq8RsA" target="_blank).
 
 For manual configuration or editing of an existing goal, the first step is to access Analytics and click on the __Administrator__ button in the lower left corner. Then go to the __Goals__ option, from the "View" column.
 
@@ -62,30 +60,35 @@ Now just save the goal and wait for the time the system needs to start counting
 
 To view your funnel, see the Analytics reports and go to the __Conversions__ menu and then to the __Goals__ option.
 
-<div class="alert alert-warning">
-<p>If you have a multi-language store with languages as <a href="https://support.google.com/webmasters/answer/182192?hl=en#locale-specific-urls">subdirectories of the gTLD</a> you should replace every <a href="https://support.google.com/analytics/answer/1034376?hl=en&ref_topic=1034375">carret</a> (<code>^</code>) with a <a href="https://support.google.com/analytics/answer/1034324?hl=en">regex</a> that matches the different subdirectories. For instance, if your website is available in:</p>
-  <ul>
-    <li><strong>Italian: </strong><code>example.com/it</code></li>
-    <li><strong>Spanish: </strong><code>example.com/es</code></li>
-    <li><strong>French: </strong><code>example.com/fr</code></li>
-  </ul>
-  <p>You would have to change your destination:</p>
-  <ul>
-<li><strong>From: </strong><code>^/checkout/orderPlaced</code></li> 
-<li><strong>To: </strong><code>^/(it|es|fr)/checkout/orderPlaced</code></li>
-  </ul>
-  <p>This needs to be done for every funnel step as well.</p>
-</div>
-
-<div class="alert alert-warning">
-<p>The funnel settings in this article have been updated to follow the new version of <a href="http://help.vtex.com/en/tutorial/what-is-the-shared-cart">SmartCheckout shared cart</a>.</p>
-<p>For comparison purposes, see below the old settings:</p>
-<ol>
-<li>Product: <code>/p($|\?)</code> (not required)</li>
-<li>Cart: <code>^/checkout/(#/cart)?$</code></li>
-<li>Identification: <code>^/checkout/#/email</code></li>
-<li>Personal Data: <code>^/checkout/#/profile</code></li>
-<li>Delivery: <code>^/checkout/#/shipping</code></li>
-<li>Payment: <code>^/checkout/#/payment</code></li>
-</ol>
-</div>
+>⚠️ If you have a multi-language store with languages as [subdirectories of the gTLD](https://support.google.com/webmasters/answer/182192?hl=en#locale-specific-urls) you should replace every [carret](https://support.google.com/analytics/answer/1034376?hl=en&ref_topic=1034375) (`^`) with a [regex](https://support.google.com/analytics/answer/1034324?hl=en) that matches the different subdirectories. For instance, if your website is available in:
+>
+> * **Italian: **`example.com/it`
+>
+> * **Spanish: **`example.com/es`
+>
+> * **French: **`example.com/fr`
+>
+> You would have to change your destination:
+>
+> ***From: **`^/checkout/orderPlaced` 
+>
+> ***To: **`^/(it|es|fr)/checkout/orderPlaced`
+>
+> This needs to be done for every funnel step as well.
+
+>⚠️ The funnel settings in this article have been updated to follow the new version of [SmartCheckout shared cart](http://help.vtex.com/en/tutorial/what-is-the-shared-cart).
+>
+> For comparison purposes, see below the old settings:
+>
+> Product: `/p($|\?)` (not required)
+>
+> Cart: `^/checkout/(#/cart)?$`
+>
+> Identification: `^/checkout/#/email`
+>
+> Personal Data: `^/checkout/#/profile`
+>
+> Delivery: `^/checkout/#/shipping`
+>
+> Payment: `^/checkout/#/payment`
+> 
diff --git a/docs/tutorials/en/setting-up-the-tnspay-gateway.md b/docs/tutorials/en/setting-up-the-tnspay-gateway.md
index 4f44f5340..34e2443b1 100644
--- a/docs/tutorials/en/setting-up-the-tnspay-gateway.md
+++ b/docs/tutorials/en/setting-up-the-tnspay-gateway.md
@@ -15,7 +15,7 @@ legacySlug: setting-up-the-tnspay-gateway
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 TNSPay is a [payment gateway](/en/tutorial/what-is-a-payment-gateway) with PCI certification that offers a number of security features to facilitate the processing of [recurring purchases](/en/faq/how-does-recurring-purchase-work).
 
diff --git a/docs/tutorials/en/setting-up-the-type-of-interest-rate.md b/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
index 82973edf4..727fefdf1 100644
--- a/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/en/setting-up-the-type-of-interest-rate.md
@@ -41,6 +41,4 @@ The reply that the "GET Rule by ID" call returns will be the request of the ther
 
 https://developers.vtex.com/reference/configuration-1#putrulebyid
 
-<div class="alert alert-danger">
-IMPORTANT: At present, the only way to change a payment method is through API. Should it be necessary to change the payment method by using the user interface, the setup process through API would have to be repeated, since when saving the changes, the value will be considered empty by default.
-</div>
+>❗ IMPORTANT: At present, the only way to change a payment method is through API. Should it be necessary to change the payment method by using the user interface, the setup process through API would have to be repeated, since when saving the changes, the value will be considered empty by default.
diff --git a/docs/tutorials/en/setting-up-triggers.md b/docs/tutorials/en/setting-up-triggers.md
index c0d7d7f6a..bcd40885e 100644
--- a/docs/tutorials/en/setting-up-triggers.md
+++ b/docs/tutorials/en/setting-up-triggers.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-triggers
 subcategory: 5tSNDlvmik8gGuKw2goW4q
 ---
 
-<div class="alert alert-info">
-This article talks about Master Data v2. If you want to use Master Data v1, check out the steps explained in <a href="https://help.vtex.com/pt/tutorial/creating-trigger-in-master-data--tutorials_1270">this article</a>.
-</div>
+>ℹ️ This article talks about Master Data v2. If you want to use Master Data v1, check out the steps explained in [this article](https://help.vtex.com/pt/tutorial/creating-trigger-in-master-data--tutorials_1270).
 
 A Master Data trigger is an action executed after an insert or update. 
 
diff --git a/docs/tutorials/en/setup-safetypay.md b/docs/tutorials/en/setup-safetypay.md
index 611cc4084..a0e342761 100644
--- a/docs/tutorials/en/setup-safetypay.md
+++ b/docs/tutorials/en/setup-safetypay.md
@@ -15,7 +15,7 @@ legacySlug: setup-safetypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">This payment integration can no longer be configured on the platform due to the <a href="https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14">legacy provider removal process</a> and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.</div>
+>❗ This payment integration can no longer be configured on the platform due to the [legacy provider removal process](https://help.vtex.com/en/announcements/legacy-payment-connectors-will-be-discontinued-in-2024--4R5YIjUu1IWkiOHzXtQU14) and the article will soon be removed from the Help Center. Check with your provider for more information about developing the new payment integration and the steps required for migrating settings in your store.
 
 SafetyPay is a payment solution that directly connects your store's checkout to your customer's bank. With it, your customer chooses SafetyPay as a payment method and is *redirected* to the secure internet banking environment you choose. Once redirected, the customer can make a bank transfer and pay for the order.
 
diff --git a/docs/tutorials/en/sharpspring-suiteshare.md b/docs/tutorials/en/sharpspring-suiteshare.md
index 2f567ba58..a4b3c6799 100644
--- a/docs/tutorials/en/sharpspring-suiteshare.md
+++ b/docs/tutorials/en/sharpspring-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: sharpspring-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/shipping-options-beta.md b/docs/tutorials/en/shipping-options-beta.md
index becc474d3..6ac024055 100644
--- a/docs/tutorials/en/shipping-options-beta.md
+++ b/docs/tutorials/en/shipping-options-beta.md
@@ -15,9 +15,7 @@ legacySlug: delivery-options-beta
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-<p>This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href= "https://support.vtex.com/hc/en-us/requests">our Support</a>.
 
 The **shipping options** feature allows the retailer to create, edit, and manage the order shipping options in a single place, ensuring more simplicity and efficiency in managing your operation. The term "shipping" is the general way to indicate the order's delivery or pickup. In each shipping option configuration, the retailer determines:
 
diff --git a/docs/tutorials/en/shipping-rate-template.md b/docs/tutorials/en/shipping-rate-template.md
index 46540cf9c..f4b875014 100644
--- a/docs/tutorials/en/shipping-rate-template.md
+++ b/docs/tutorials/en/shipping-rate-template.md
@@ -24,9 +24,7 @@ To add shipping costs to the template, you have to:
 1. [Fill in the fields in the spreadsheet](#fill-in-the-fields-in-the-spreadsheet)
 2. [Upload the spreadsheet in VTEX Admin](#upload-the-spreadsheet-in-vtex-admin)
 
-<div class="alert alert-info"> 
-You can also add shipping costs in the Shipping rates module. We recommend using the <a href="https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127">shipping rate template</a> to include multiple ZIP code ranges and using the Shipping rates module to manage existing shipping costs and add ZIP code ranges individually. 
-</div>
+>ℹ️ You can also add shipping costs in the Shipping rates module. We recommend using the [shipping rate template](https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127) to include multiple ZIP code ranges and using the Shipping rates module to manage existing shipping costs and add ZIP code ranges individually.
 
 ## Fill in the fields in the spreadsheet
 
@@ -174,9 +172,7 @@ See below the spreadsheet columns content to understand each field in detail.
 </tbody>
 </table>
 
-<div class="alert alert-info"> 
-We used the term "weight" when referring to "mass" in this documentation for readability. 
-</div>
+>ℹ️ We used the term "weight" when referring to "mass" in this documentation for readability.
 
 Here is an example of how to fill in the fields in the spreadsheet.
 ![modelo_planilhanumerica](https://images.ctfassets.net/alneenqid6w5/15Dc2cfsXWbIwSt2vypWN3/20628e9acf5336c3fefcc84d334c08ec/freight_-_Debora_Moreno.png)
@@ -194,13 +190,9 @@ Follow the steps below:
 
 ![upload tarifas envioEN](https://images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/38cfc78b89a4e0e68bfec882af0ea9f4/upload_tarifas_envioEN.png)
 
-<div class="alert alert-warning">
-For <b>new</b> shipping policies, other steps are required. Check out the article <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy</a> for more information.
-</div>
+>⚠️ For **new** shipping policies, other steps are required. Check out the article [Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140) for more information.
 
-<div class="alert alert-danger"> 
-Each tab in the spreadsheet supports a maximum of 65,536 rows. You can create as many tabs as you want on the same worksheet, provided that it does not exceed the limit of rows and the maximum file size of 10MB. You can compress the file by saving it as <b>.zip</b>, if necessary. If the file is still too large to upload, you can split it into two files and create another shipping policy to upload the second file. 
-</div>
+>❗ Each tab in the spreadsheet supports a maximum of 65,536 rows. You can create as many tabs as you want on the same worksheet, provided that it does not exceed the limit of rows and the maximum file size of 10MB. You can compress the file by saving it as **.zip**, if necessary. If the file is still too large to upload, you can split it into two files and create another shipping policy to upload the second file.
 
 In the event that the spreadsheet contains an error, you will receive an email with details about the error. Make sure you have reviewed all the fields before uploading the file again.
 
diff --git a/docs/tutorials/en/shipping-rates.md b/docs/tutorials/en/shipping-rates.md
index c9aeb74d5..e300807e9 100644
--- a/docs/tutorials/en/shipping-rates.md
+++ b/docs/tutorials/en/shipping-rates.md
@@ -17,9 +17,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Shipping rates are the shipping options your store offers to customers, and they are related to your store's [shipping policies](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Prices agreed between your store and the responsible for the delivery service, such as carriers, pickup points, and service providers, must be configured as **shipping rates.**
 
-<div class="alert alert-warning">
-The <a href="https://help.vtex.com/en/tutorial/total-shipping-cost--5bwhIO108VA5Y2YOpef9lV">total shipping cost</a> to the customer includes the shipping rate, <a href="https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV">additional shipping costs</a> and, a loading dock fee.
-</div>
+>⚠️ The [total shipping cost](https://help.vtex.com/en/tutorial/total-shipping-cost--5bwhIO108VA5Y2YOpef9lV) to the customer includes the shipping rate, [additional shipping costs](https://help.vtex.com/en/tutorial/additional-shipping-costs--2vqGwMn0LabkOHY6zSHYNV) and, a loading dock fee.
 
 ![Tarifa envio EN](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/8aa8e3fcbe570f3862e3e31b3a7db0eb/Tarifa_envio_EN.svg)
 
@@ -28,10 +26,6 @@ You can add shipping rates in the Admin by using:
 * The `Shipping strategy` page: you must upload the [shipping rate template](https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127) when adding a `Shipping policy` or updating an existing one. We recommend this option for adding many postal codes and their shipping costs at a time. 
 * The `Shipping rates` page: for when you want to update existing rates or add a few. It allows you to edit and add shipping rates without using the shipping rate template. To learn more, see our tutorial [Managing shipping rates](https://help.vtex.com/en/tutorial/managing-shipping-rates--tutorials_141).
 
-<div class="alert alert-warning">
-The <b><a href="https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127">shipping rate template</b></a> is the only option for configuring the location polygon (geolocation), the <b>insurance cost</b> and <b>additional shipping costs</b>. 
-</div>
+>⚠️ The **[shipping rate template**](https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127) is the only option for configuring the location polygon (geolocation), the **insurance cost** and **additional shipping costs**.
 
-<div class="alert alert-info">
-If you need to update or add multiple shipping rates, we recommend using the <a href="https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127">shipping rate template</a> instead of the <b>Shipping rates</b> module. If you want to check out how shipping rates are added and displayed to the end customer, use the <b><a href="https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144">Shipping simulator</b></a> module.
-</div>
+>ℹ️ If you need to update or add multiple shipping rates, we recommend using the [shipping rate template](https://help.vtex.com/en/tutorial/shipping-rate-template--tutorials_127) instead of the **Shipping rates** module. If you want to check out how shipping rates are added and displayed to the end customer, use the **[Shipping simulator**](https://help.vtex.com/en/tutorial/shipping-simulation--tutorials_144) module.
diff --git a/docs/tutorials/en/shipping-simulation.md b/docs/tutorials/en/shipping-simulation.md
index 63e00fa8b..1f02d11e9 100644
--- a/docs/tutorials/en/shipping-simulation.md
+++ b/docs/tutorials/en/shipping-simulation.md
@@ -22,14 +22,12 @@ The simulator can also be used to validate the **[Shipping Strategy](https://hel
 * **Item Availability**: the simulator checks if the item is in stock and whether it is possible to ship it (checks if there are carriers for that region, for example). If one of the criteria is not met, the simulator assumes that the item is unavailable.
 * **White Label Sellers Availability:** the simulator selects the white label seller that is closest to the shipping address (the logistics settings are calculated in the _White Label Seller’s_ environment, not in the main account). 
 
-<div class="alert alert-warning"> 
-There may be a discrepancy between the final price indicated by the simulator and the actual price in your store since the simulation does not take into account the following:
-<ul>
-<li>Promotions applied to the items.
-<li>Shipping discounts configured through promotions.
-<li>The Total Delivery Time shown in the simulation results does not take into account the field <b>Expected Delivery Date (pre-sale)</b>  <a href="https://help.vtex.com/en/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY">in the item’s information in the system.</a>
-</ul>
-</div>
+>⚠️ There may be a discrepancy between the final price indicated by the simulator and the actual price in your store since the simulation does not take into account the following:
+>
+> <li>Promotions applied to the items.
+> <li>Shipping discounts configured through promotions.
+> <li>The Total Delivery Time shown in the simulation results does not take into account the field **Expected Delivery Date (pre-sale)**  [in the item’s information in the system.](https://help.vtex.com/en/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY)
+> 
 
 ## Simulating the shipping
 
diff --git a/docs/tutorials/en/shopify-suiteshare.md b/docs/tutorials/en/shopify-suiteshare.md
index f9c4b0b45..ac44e3683 100644
--- a/docs/tutorials/en/shopify-suiteshare.md
+++ b/docs/tutorials/en/shopify-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: shopify-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/sku-bindings.md b/docs/tutorials/en/sku-bindings.md
index f0e862f1e..71d303393 100644
--- a/docs/tutorials/en/sku-bindings.md
+++ b/docs/tutorials/en/sku-bindings.md
@@ -97,9 +97,7 @@ To remove the binding between the seller’s SKU and the marketplace SKU, follow
 2. On the row where you may find the desired item, click on the menu icon <i class="fas fa-ellipsis-v"></i>.
 3. Click on the <i class="far fa-trash-alt"></i> `Remove` button.
 
-<div class="alert alert-warning">
-When you remove a binding, the seller's SKU will no longer be part of the marketplace catalog. Therefore, it'll disappear from the list on the <b>SKU Bindings</b> page. You cannot recover a removed binding. However, the seller can resend the SKU to the marketplace, which will <a href="https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus--tutorials_396">catalog</a> the SKU again and make it available.
-</div>
+>⚠️ When you remove a binding, the seller's SKU will no longer be part of the marketplace catalog. Therefore, it'll disappear from the list on the **SKU Bindings** page. You cannot recover a removed binding. However, the seller can resend the SKU to the marketplace, which will [catalog](https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus--tutorials_396) the SKU again and make it available.
 
 ## Exporting
 
diff --git a/docs/tutorials/en/sku-registration-fields.md b/docs/tutorials/en/sku-registration-fields.md
index c0d26ebb0..a522a3503 100644
--- a/docs/tutorials/en/sku-registration-fields.md
+++ b/docs/tutorials/en/sku-registration-fields.md
@@ -15,9 +15,7 @@ legacySlug: sku-registration-fields
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class="alert alert-warning">
-  <p>There is a limit of 50 SKUs per product. To request an extension of the limit, please contact <a href= "https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
-</div>
+>⚠️ There is a limit of 50 SKUs per product. To request an extension of the limit, please contact <a href= "https://support.vtex.com/hc/pt-br/requests">our Support</a>.
 
 For more information on each field, read their complete description below.
 
@@ -131,7 +129,5 @@ After filling out the required fields, click on Save on the SKU tab.
 - [Filling in product registration fields](/en/tutorial/product-registration-fields--4dYXWIK3zyS8IceKkQseke)
 - [Filling in Import Spreadsheet fields](/en/tutorial/preencher-campos-da-planilha-de-importacao--4nYhx63Q5yokQWaMguaIgI)
 
-<div class="alert alert-danger">
- To ensure the items added to the inventory will be available for sale on the store, the <a href="https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW">SKU ID</a> cannot contain <b>a leading zero</b>. For instance, the system does not read IDs with a <code>01</code>, <code>02</code>, <code>021</code> format because the expected format is <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ To ensure the items added to the inventory will be available for sale on the store, the [SKU ID](https://help.vtex.com/en/tutorial/how-to-find-an-sku-id--4VQZsYeb3igGK2YowuEYWW) cannot contain **a leading zero**. For instance, the system does not read IDs with a `01`, `02`, `021` format because the expected format is `1`, `2`, `21`.
 
diff --git a/docs/tutorials/en/sla-errors-in-marketplace-integration-orders.md b/docs/tutorials/en/sla-errors-in-marketplace-integration-orders.md
index 195c1d247..4df9ae83b 100644
--- a/docs/tutorials/en/sla-errors-in-marketplace-integration-orders.md
+++ b/docs/tutorials/en/sla-errors-in-marketplace-integration-orders.md
@@ -31,9 +31,7 @@ Here are the most common problems that cause SLA errors:
 
 After resolving the error, the order must be manually reprocessed. In your Admin, go to **Marketplace > Connections > Orders** and click on the order with the error. Click on the **Actions** button and choose the **Reprocess** option.
 
-<div class="alert alert-info">
-If the error persists, open a <a href="https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt">VTEX support ticket</a>.
-</div>
+>ℹ️ If the error persists, open a [VTEX support ticket](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt).
 
 ### Learn more
 
diff --git a/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md b/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md
index 187356d8d..261fee757 100644
--- a/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md
+++ b/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md
@@ -17,9 +17,7 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 
 With SmartCheckout, the customer's information is automatically filled in at Checkout, and you are only required to enter your store's email. This function reduces the purchase time as customers do not need to re-enter their data for each purchase made at the same store.
 
-<div class="alert alert-info">
-For SmartCheckout to reuse the information at Checkout, the customer must have already made a previous purchase or must have created a profile in the store.
-</div>
+>ℹ️ For SmartCheckout to reuse the information at Checkout, the customer must have already made a previous purchase or must have created a profile in the store.
 
 ## Customer information
 
diff --git a/docs/tutorials/en/smartcheckout-v5-general-characteristics.md b/docs/tutorials/en/smartcheckout-v5-general-characteristics.md
index c0a4e4a1e..f7ca90fbb 100644
--- a/docs/tutorials/en/smartcheckout-v5-general-characteristics.md
+++ b/docs/tutorials/en/smartcheckout-v5-general-characteristics.md
@@ -53,9 +53,7 @@ You can use the files `checkout5-custom.js` and `orderplaced2-custom.js` in o
 4. In the __Files__ menu, located on the right side of the page, click on the ones you want to make adjustments to the code.
 5. Click the `Save` button.
 
-<div class="alert alert-warning">
-  Customizing JavaScript files can damage your Checkout. VTEX <b>does not recommend</b> customizations and doesn't take responsibility for any damage caused by this code.
-</div>
+>⚠️ Customizing JavaScript files can damage your Checkout. VTEX **does not recommend** customizations and doesn't take responsibility for any damage caused by this code.
 
 __IMPORTANT:__ Do not use these files to insert marketing and integration tags. In case you need them, do so through Google Tag Manager.
 
diff --git a/docs/tutorials/en/special-conditions.md b/docs/tutorials/en/special-conditions.md
index d3aba478b..c1a3fb7fd 100644
--- a/docs/tutorials/en/special-conditions.md
+++ b/docs/tutorials/en/special-conditions.md
@@ -136,9 +136,7 @@ Suppose that you want to offer a special payment condition to customers paying b
 
 In this case, you must select the issuing bank which responsible for this card followed by the name of your store in the __Co-brand__ field.
 
-<div class="alert alert-warning">
-Be aware that by default, the info as to whether or not a card has co-brand is <strong>not</strong> added in the VTEX database. Therefore, if you store wants to segment a payment condition according to cards, you need to send a ticket with the co-brand card list to the VTEX support team.
-</div>
+>⚠️ Be aware that by default, the info as to whether or not a card has co-brand is **not** added in the VTEX database. Therefore, if you store wants to segment a payment condition according to cards, you need to send a ticket with the co-brand card list to the VTEX support team.
 
 ## Period
 
diff --git a/docs/tutorials/en/split-payment.md b/docs/tutorials/en/split-payment.md
index 1dd91166e..32fa7acd7 100644
--- a/docs/tutorials/en/split-payment.md
+++ b/docs/tutorials/en/split-payment.md
@@ -15,9 +15,7 @@ legacySlug: split-payment
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-This is a marketplace payment solution.
-</div>
+>⚠️ This is a marketplace payment solution.
 
 To guarantee that our [marketplace](https://help.vtex.com/en/tutorial/what-is-a-marketplace--680lLJTnmEAmekcC0MIea8) clients automatically divide the payment between all [sellers](https://help.vtex.com/en/tutorial/what-is-a-seller--5FkLvhZ3Few4CWWIuYOK2w), set a commission based on a fixed percentage, and remain operating in accordance with current regulations, VTEX offers the __Split Payment__.
 
@@ -26,9 +24,7 @@ Below are two examples of split payment application scenarios where a consumer a
 1. When the marketplace is responsible for processing payment for the purchase, VTEX automatically divides this payment so that each beneficiary receives their share directly into their own bank account, thus carrying out the [Payout Split](https://help.vtex.com/tutorial/split-payment--6k5JidhYRUxileNolY2VLx#payout-split).
 2. When the cart involves sellers who are responsible for processing their own payment method (without depending on the marketplace), VTEX creates different payment transactions for the Marketplace and the sellers, performing the [Transaction Split](https://help.vtex.com/tutorial/split-payment--6k5JidhYRUxileNolY2VLx#transaction-split).
 
-<div class="alert alert-warning">
-The distribution of purchase amounts is always carried out in accordance with pre-defined commission percentage agreements between the marketplace and sellers.
-</div>
+>⚠️ The distribution of purchase amounts is always carried out in accordance with pre-defined commission percentage agreements between the marketplace and sellers.
 
 Check below for more details about each of the split payment models:
 
diff --git a/docs/tutorials/en/store-overview-beta.md b/docs/tutorials/en/store-overview-beta.md
index a9e6e56e4..293649db5 100644
--- a/docs/tutorials/en/store-overview-beta.md
+++ b/docs/tutorials/en/store-overview-beta.md
@@ -15,9 +15,7 @@ legacySlug: store-overview-beta
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class="alert alert-info">
-The updated version of the Store Overview (beta) page is available for use free of charge on the VTEX Admin during the beta phase or until stipulated by VTEX. It is important to note that charges may apply in the future. For the time being, the current version of the Store Overview page on the VTEX Admin will continue to be available.
-</div>
+>ℹ️ The updated version of the Store Overview (beta) page is available for use free of charge on the VTEX Admin during the beta phase or until stipulated by VTEX. It is important to note that charges may apply in the future. For the time being, the current version of the Store Overview page on the VTEX Admin will continue to be available.
 
 The Store Overview (Beta) page in your VTEX Admin provides real-time tracking of your operation on the current day, giving visibility into indicators that allow you and your team to get feedback about actions applied to the store and to quickly implement improvements.
 
@@ -65,8 +63,7 @@ You can use different metrics and monitoring charts for analyzing results, depen
 | Financial results | - Revenue captured <br>- [Average ticket](#monitoring) <br>- [Highest grossing products](#metrics)                                                                                                                                                                                         |
 | Conversion        | - [Conversion rate](#metrics) <br>- [Sales funnel](#sales-funnel) <br>- [Orders captured](#monitoring), compared to the number of canceled orders. Depending on the outcome, this can guide your team to identify operational problems in fulfillment or customer service that resulted in canceled orders. |
 
-<div class="alert alert-info"> Keep in mind that while the Monitoring charts are updated within three minutes, Metrics charts take fifteen minutes to be updated, which can influence the analysis of results. Learn more in <a href="#data-update">Data update</a>.
-</div>
+>ℹ️ Keep in mind that while the Monitoring charts are updated within three minutes, Metrics charts take fifteen minutes to be updated, which can influence the analysis of results. Learn more in [Data update](#data-update).
 
 ### Analyzing campaign results
 
diff --git a/docs/tutorials/en/subscription-plans.md b/docs/tutorials/en/subscription-plans.md
index 5895aeca2..3b79e8794 100644
--- a/docs/tutorials/en/subscription-plans.md
+++ b/docs/tutorials/en/subscription-plans.md
@@ -63,17 +63,13 @@ Each column of the subscription plan list displays different information. See be
     * **Active**: means that the plan is available for customers creating new subscriptions with associated products.
     * **Inactive**: means that the plan is not available for customers creating new subscriptions, even if they include associated products.
 
-<div class="alert alert-info">
-<p>Inactive plans are disabled only for new subscriptions. If a customer created a subscription when the plan was active, it would continue to place orders in the next cycle dates for that customer.</p>
-</div>
+>ℹ️ Inactive plans are disabled only for new subscriptions. If a customer created a subscription when the plan was active, it would continue to place orders in the next cycle dates for that customer.
 
 * <i class="fas fa-ellipsis-v"></i> **button**: by clicking on this button, you can perform the following actions.
     * **Edit**: opens the page to edit the subscription plan.
     * **Delete**: allows you to delete the plan permanently. Before deleting it, a window will appear asking you to confirm your choice. If you click on `Delete plan`, this action **cannot** be undone.
 
-<div class="alert alert-warning">
-  <p>When a plan is deleted, customers who have this plan will <strong>not</strong> have their orders placed in the next subscription cycles. To prevent this plan from being used in new subscriptions but keep placing future orders from its pre-existing subscriptions, you should disable the plan instead of deleting it.</p>
-</div>
+>⚠️ When a plan is deleted, customers who have this plan will **not** have their orders placed in the next subscription cycles. To prevent this plan from being used in new subscriptions but keep placing future orders from its pre-existing subscriptions, you should disable the plan instead of deleting it.
 
 ## Show rows
 
diff --git a/docs/tutorials/en/table-of-base-prices.md b/docs/tutorials/en/table-of-base-prices.md
index 5ba32f46a..75a88c6af 100644
--- a/docs/tutorials/en/table-of-base-prices.md
+++ b/docs/tutorials/en/table-of-base-prices.md
@@ -25,9 +25,7 @@ For a better understanding of how to fill the [table of base prices](https://hel
 
 - **List Price**: The list price functions as a SKU's former price assumed to be on sale. It's also known as the "original price" and can be shown in your store's window display. This field is optional when registering a price. 
 
-<div class="alert alert-info">
-<p>In <b>Cost Price</b>, <b>Base Price</b> and <b>List Price</b>, you can insert decimal values separated by dot. Example: <code>4.95</code>.</p>
-</div>
+>ℹ️ In **Cost Price**, **Base Price** and **List Price**, you can insert decimal values separated by dot. Example: `4.95`.
 
 The next spreadsheet fields are optional, used only to make SKU identification easier. To view these fields in the spreadsheet, you'll need to select the *include metadata in exported tables* export option.
 
diff --git a/docs/tutorials/en/telesales-toolbar.md b/docs/tutorials/en/telesales-toolbar.md
index 5bf3c84ed..e9acfdd0c 100644
--- a/docs/tutorials/en/telesales-toolbar.md
+++ b/docs/tutorials/en/telesales-toolbar.md
@@ -29,10 +29,7 @@ To enable this toolbar, the store administrator must [assign the Call Center Ope
 
 To learn how to customize the toolbar in the **CMS** module, check out the article [Customizing the telesales toolbar](https://help.vtex.com/en/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg).
 
-<div class="alert alert-warning">
-<p>For stores developed with <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, you must configure the <strong>VTEX Telemarketing</strong> app to enable and customize the telesales toolbar. Learn more about this process in our <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-telemarketing">VTEX Telemarketing</a> guide.
-</p>
-</div>
+>⚠️ For stores developed with [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), you must configure the **VTEX Telemarketing** app to enable and customize the telesales toolbar. Learn more about this process in our [VTEX Telemarketing](https://developers.vtex.com/vtex-developer-docs/docs/vtex-telemarketing) guide.
 
 ## Log in as customer
 
diff --git a/docs/tutorials/en/testing-webservice-using-soapui.md b/docs/tutorials/en/testing-webservice-using-soapui.md
index 8ad5143fe..f574751be 100644
--- a/docs/tutorials/en/testing-webservice-using-soapui.md
+++ b/docs/tutorials/en/testing-webservice-using-soapui.md
@@ -15,11 +15,13 @@ legacySlug: testing-webservice-using-soapui
 subcategory: 1vwB9FtTSQmcSewQw02QoW
 ---
 
-<div class="alert alert-danger"><p>Attention: Only SOAP methods related to the <strong>catalog</strong> are valid.</p>
-<p><strong> All the other Web Service methods will be deprecated as of 02/28/2017.</strong></p>
-<p>Use the equivalent REST APIs, available in our <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Attention: Only SOAP methods related to the **catalog** are valid.
+>
+> ** All the other Web Service methods will be deprecated as of 02/28/2017.**
+>
+> Use the equivalent REST APIs, available in our [Developer Docs](//help.vtex.com/developer-docs/).
 
-<div class="alert alert-warning">The configurations documented in this article take place in an environment external to VTEX, therefore they may be discontinued without prior notice.</div>
+>⚠️ The configurations documented in this article take place in an environment external to VTEX, therefore they may be discontinued without prior notice.
 
 SoapUI is a tool that can be used to simulate the connection and execution of methods of a given webservice without having to do this using programming alone.
 
@@ -44,6 +46,8 @@ Log in using the data of the webservice desired. After logging in, you will view
 3. Locate the button **Auth** and repeat the authentication before executing the method;
 4. Execute the method.
 
-<div class="alert alert-danger"><p>Atenção: only the SOAP methods relevent to the <strong>catalog</strong> are valid.</p>
-<p><strong>All other methods are deprecated.</strong></p>
-<p>Use the equivalent REST APIs avilable in our <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: only the SOAP methods relevent to the **catalog** are valid.
+>
+> **All other methods are deprecated.**
+>
+> Use the equivalent REST APIs avilable in our [Developer Docs](//help.vtex.com/developer-docs/).
diff --git a/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md b/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md
index a2e0de12b..2c9761c77 100644
--- a/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md
+++ b/docs/tutorials/en/the-order-was-split-into-packages-with-separate-deliveries.md
@@ -32,9 +32,7 @@ The delivery date for each package will be adjusted based on the `shippingEstima
 
 To avoid splitting packages in orders that include pre-sale products, you can configure [shipping groups](https://help.vtex.com/en/tutorial/como-funciona-a-remessa). This allows you to group all packages to be delivered by the same carrier and from the same [loading dock](https://help.vtex.com/en/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) into a single shipment.
 
-<div class="alert alert-danger">
-By configuring shipping groups, this behavior will be applied to all orders with different delivery dates, not just those containing pre-sale products.
-</div>
+>❗ By configuring shipping groups, this behavior will be applied to all orders with different delivery dates, not just those containing pre-sale products.
 
 ### Configuring shipping groups
 
diff --git a/docs/tutorials/en/the-risk-assessment-process.md b/docs/tutorials/en/the-risk-assessment-process.md
index ba2f0f889..3e7e384d6 100644
--- a/docs/tutorials/en/the-risk-assessment-process.md
+++ b/docs/tutorials/en/the-risk-assessment-process.md
@@ -62,6 +62,4 @@ Topics:
 Insert your VTEX [account name](https://help.vtex.com/en/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) below to access the documentation.
 <iframe src="https://help.vtex.com/insertaccountname?id=1ayXEtqawI9yuxFXutiITh" title="Insert your account name and click the button." frameBorder="0" width="400" height="50"></iframe>
 
-<div class="alert alert-warning">
-  If you are having dificulty accessing the FAQs, try installing the latest version of the app <code>vtex.admin-docs</code> using <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">VTEX CLI</a> and repeating the process.
-</div>
+>⚠️ If you are having dificulty accessing the FAQs, try installing the latest version of the app `vtex.admin-docs` using [VTEX CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) and repeating the process.
diff --git a/docs/tutorials/en/total-shipping-cost.md b/docs/tutorials/en/total-shipping-cost.md
index 70983c834..9186e5965 100644
--- a/docs/tutorials/en/total-shipping-cost.md
+++ b/docs/tutorials/en/total-shipping-cost.md
@@ -33,8 +33,6 @@ So, in general, the total shipping cost is calculated as follows:
 
 ![Custo-final-envio-EN](https://images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/4b04d0319eb18cd1ee0e9c03858c5bc1/Custo-final-envio-EN.svg)
 
-<div class="alert alert-danger">
-If the <b>price-based charge</b> is lower than the <b>insurance charge</b>, the system only considers the insurance charge. The price-based charge will not be taken into account for the total shipping cost.<p>
-The best carrier is chosen based on its shipping rate, which does not consider loading dock and warehouse costs (if any). To simulate shipping options for customers, use the <a href="https://help.vtex.com/en/tutorial/simulacao-de-frete--tutorials_144">Shipping simulator</a>.
-</div>
+>❗ If the **price-based charge** is lower than the **insurance charge**, the system only considers the insurance charge. The price-based charge will not be taken into account for the total shipping cost.<p>
+> The best carrier is chosen based on its shipping rate, which does not consider loading dock and warehouse costs (if any). To simulate shipping options for customers, use the [Shipping simulator](https://help.vtex.com/en/tutorial/simulacao-de-frete--tutorials_144).
 
diff --git a/docs/tutorials/en/tracking-your-sales-analytics.md b/docs/tutorials/en/tracking-your-sales-analytics.md
index ce3c8a167..07129520a 100644
--- a/docs/tutorials/en/tracking-your-sales-analytics.md
+++ b/docs/tutorials/en/tracking-your-sales-analytics.md
@@ -27,7 +27,7 @@ The table below describes the key metrics available in Insights. All metrics ref
 | Revenue        | Total amount determined by approved applications |
 | Average Ticket | Average revenue per order |
 
-<div class="alert alert-warning">We do not have access to session and conversion data concerning purchase flows made outside of VTEX stores. Therefore, orders placed in marketplaces are not included in Insights metrics.</div>
+>⚠️ We do not have access to session and conversion data concerning purchase flows made outside of VTEX stores. Therefore, orders placed in marketplaces are not included in Insights metrics.
 
 ## Getting to know the interface
 
diff --git a/docs/tutorials/en/understanding-competition-of-promotions.md b/docs/tutorials/en/understanding-competition-of-promotions.md
index 1b01fbbd3..dec022b0e 100644
--- a/docs/tutorials/en/understanding-competition-of-promotions.md
+++ b/docs/tutorials/en/understanding-competition-of-promotions.md
@@ -84,8 +84,7 @@ Therefore, promotions will be applied in the following order:
 
 ![promocao3 EN](https://images.ctfassets.net/alneenqid6w5/6nz2KJuFk4aS0eU0OGg0sM/7cf285654ec80894e0a346c90918cd33/promocao3_EN.png)
 
-<div class="alert alert-warning">
-Orders originating from the <a href="https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> (provided by the store) or Fulfillment (delivered by the store) do not support cumulative promotions. This is because the use of promotions is restricted to specific types on both VTEX and external marketplaces.</div>
+>⚠️ Orders originating from the [Marketplace](https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406) (provided by the store) or Fulfillment (delivered by the store) do not support cumulative promotions. This is because the use of promotions is restricted to specific types on both VTEX and external marketplaces.
 
 ## Promotion competition strategies
 
@@ -100,8 +99,7 @@ Here are the two strategies for promotion competition:
 - [Competition by scenario](#competition-by-scenario)
 - [Competition by item](#competition-by-item)
 
-<div class="alert alert-info">
-By default, all accounts follow the competition by scenariostrategy. In case the competition by item strategy is better suited for your business needs, please <a href="https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">open a ticket</a> with our support team and request the change.</div>
+>ℹ️ By default, all accounts follow the competition by scenariostrategy. In case the competition by item strategy is better suited for your business needs, please [open a ticket](https://help.vtex.com/en/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) with our support team and request the change.
 
 ### Competition by scenario
 
diff --git a/docs/tutorials/en/understanding-how-indexation-works.md b/docs/tutorials/en/understanding-how-indexation-works.md
index 06f3205df..9743447eb 100644
--- a/docs/tutorials/en/understanding-how-indexation-works.md
+++ b/docs/tutorials/en/understanding-how-indexation-works.md
@@ -15,11 +15,10 @@ legacySlug: understanding-how-indexation-works
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class="alert alert-warning">
-<p>This tutorial is valid only for stores using <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">Legacy CMS Portal</a> search.</p>
-<p>If your store uses <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>, check <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Indexing History
-</a> to follow the indexing process.</p>
-</div>
+>⚠️ This tutorial is valid only for stores using [Legacy CMS Portal](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) search.
+>
+> If your store uses [Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG), check <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Indexing History
+> </a> to follow the indexing process.
 
 Indexing is a process that prepares the general SKU data, such as catalogue data, prices and inventory, and updates the information to serve as a basis for searches and for setting up the site's product display shelves.
 
diff --git a/docs/tutorials/en/understanding-incomplete-orders.md b/docs/tutorials/en/understanding-incomplete-orders.md
index 4b8a49e95..1c6bef9fb 100644
--- a/docs/tutorials/en/understanding-incomplete-orders.md
+++ b/docs/tutorials/en/understanding-incomplete-orders.md
@@ -23,9 +23,7 @@ In addition, all incomplete orders do not have Workflow and this behavior is exp
 
 Because an incomplete order was interrupted, activating a Workflow for an inactive situation would not be functional.
 
-<div class="alert alert-danger"> 
-If there is an incomplete order, we recommend placing it again in the store. The platform will record the incomplete orders, but not process them. So if an order is incomplete and the customer still wants to purchase the items, they need to create a new order with the same items.
-</div>
+>❗ If there is an incomplete order, we recommend placing it again in the store. The platform will record the incomplete orders, but not process them. So if an order is incomplete and the customer still wants to purchase the items, they need to create a new order with the same items.
 
 Hence, the process proceeds as usual.
 
diff --git a/docs/tutorials/en/understanding-the-conversation-tracker.md b/docs/tutorials/en/understanding-the-conversation-tracker.md
index 32fce3579..4d8c4c64b 100644
--- a/docs/tutorials/en/understanding-the-conversation-tracker.md
+++ b/docs/tutorials/en/understanding-the-conversation-tracker.md
@@ -24,9 +24,7 @@ The Conversation Tracker can one of the following two settings:
 - **Hard** - Creates an unreadable alias (alternate email), thereby avoiding identification by external systems, in addition to linking any email sent to this address to the order's timeline. The alias of a store having such configuration would be similar to the following: `ff2e6348a53a4d449af92be2a1011328@ct.vtex.com.br`
 - **Soft** - Creates a less complex alias (alternate email) for the buying user's email, making this email readable in the OMS UI and when looking at the order's JSON. Another important aspect is that the store's address (issuer address) is also masked in the same way as the user's email in JSON, this being necessary to allow the system to link the emails associated with that purchase to the order's timeline. The alias in such as configured store would be similar to the following: `johndoe@vtex.com.br-207700027841b.ct.vtex.com.br`
 
-<div class="alert alert-info">
-NOTE: Stores are configured as <strong>hard by default</strong>.
-</div>
+>ℹ️ NOTE: Stores are configured as **hard by default**.
 
 This  Conversation Tracker offers several other advantages, mainly in terms of security:
 
diff --git a/docs/tutorials/en/understanding-the-cubic-weight-factor.md b/docs/tutorials/en/understanding-the-cubic-weight-factor.md
index 23d6f3f86..9515175f9 100644
--- a/docs/tutorials/en/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/en/understanding-the-cubic-weight-factor.md
@@ -34,9 +34,7 @@ Is the resulting coefficient of the relationship between weight and volume that
 
 The calculation of the cubic weight is performed by multiplying Length x Width x Height, and dividing the result by the cubic factor provided by the carrier.
 
-<div class="alert alert-warning">
-When calculating the cubic weight factor, VTEX platform does not consider measurement units, and the numbers generated are absolute. Therefore, the measurement units you consider for the calculation will be those of the final result. Notice that the your measurement unit must be the same one used by the carrier.
-</div>
+>⚠️ When calculating the cubic weight factor, VTEX platform does not consider measurement units, and the numbers generated are absolute. Therefore, the measurement units you consider for the calculation will be those of the final result. Notice that the your measurement unit must be the same one used by the carrier.
 
 Check out the following example:
 
diff --git a/docs/tutorials/en/understanding-the-updating-of-the-xml.md b/docs/tutorials/en/understanding-the-updating-of-the-xml.md
index b6e11b0ce..2eb8b141a 100644
--- a/docs/tutorials/en/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/en/understanding-the-updating-of-the-xml.md
@@ -23,4 +23,4 @@ You can view the date of the latest XML update. This information is shown in UTC
 
 [![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
 
-<div class="alert alert-info">If the option “Display SKUs without available stock (out of stock) in Inventory among the results” is not checked, out-of-stock products/SKUs will NOT be shown in the XML. Inactive products also do <strong>not</strong> appear in the XML.</div>
+>ℹ️ If the option “Display SKUs without available stock (out of stock) in Inventory among the results” is not checked, out-of-stock products/SKUs will NOT be shown in the XML. Inactive products also do **not** appear in the XML.
diff --git a/docs/tutorials/en/understanding-vtex-matcher-scoring.md b/docs/tutorials/en/understanding-vtex-matcher-scoring.md
index 1ef4346c0..e74bd15bf 100644
--- a/docs/tutorials/en/understanding-vtex-matcher-scoring.md
+++ b/docs/tutorials/en/understanding-vtex-matcher-scoring.md
@@ -42,9 +42,7 @@ The final score determines the product status as follows: Approved, Denied, or P
 ## Cataloging
 Check the table below to see the statuses generated by different scores and their corresponding actions.
 
-<div class="alert alert-info">
-The maximum VTEX Matcher score for automatic cataloging is 95. Scores greater than 95 require manual cataloging.
-</div>
+>ℹ️ The maximum VTEX Matcher score for automatic cataloging is 95. Scores greater than 95 require manual cataloging.
 
 | Score         | Status   | Scenario                                                                                                                                                         | Action                                                                                                                                                                                                                                                                                             |
 |---------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
diff --git a/docs/tutorials/en/understanding-vtexs-email-capture-system.md b/docs/tutorials/en/understanding-vtexs-email-capture-system.md
index a04ecceb6..e54c42577 100644
--- a/docs/tutorials/en/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/en/understanding-vtexs-email-capture-system.md
@@ -39,17 +39,13 @@ For better understanding, we will present a scenario (divided into 3 steps), whe
 |------------------|------------------|
 | Click on `Go to delivery`. | Checkout prompts RC.JS to transfer email address and cart information to Master Data (via Profile System). |
 
-<div class="alert alert-warning">
-So that the <a href="https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#">abandoned cart</a> function can be used , the user must have filled in the following information: e-mail, name, surname and CPF. The lack of one of these data, makes it impossible to use the abandoned cart.
-</div>
+>⚠️ So that the [abandoned cart](https://help.vtex.com/en/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#) function can be used , the user must have filled in the following information: e-mail, name, surname and CPF. The lack of one of these data, makes it impossible to use the abandoned cart.
 
 | __User__ | __VTEX Platform__ |
 |------------------|------------------|
 | Fill in the shipping and payment information. | The Checkout orderForm becomes an order and is transmitted to the VTEX OMS. The user's complete information (first name, last name, email, cart and all additional information) is transmitted to Master Data. Email capture can take up to 46 minutes to properly reflect in CRM. |
 
-<div class="alert alert-info">
-Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
-</div>
+>ℹ️ Each VTEX module is responsible for requesting RC.JS to transmit the data captured in the session. RC.JS is intended to act as a "messenger" of information.
 
 ![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/tutorials/en/updating-prices-in-marketplaces.md b/docs/tutorials/en/updating-prices-in-marketplaces.md
index a4e84ca76..6cdb38482 100644
--- a/docs/tutorials/en/updating-prices-in-marketplaces.md
+++ b/docs/tutorials/en/updating-prices-in-marketplaces.md
@@ -20,6 +20,4 @@ Marketplace price updates depend on two factors:
 - Editing product prices in the [price table](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) linked to the trade policy used by the marketplace integration.
 - [Product indexing](https://help.vtex.com/en/tutorial/understanding-how-indexation-works--tutorials_256) after new prices are added. 
 
-<div class="alert alert-warning">
-  <p>Only <a href="https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj">fixed prices</a> are used by our native marketplace integrations. Other scenarios seen in our <a href="https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx">price system architecture</a> are available only in VTEX marketplaces.</p>
-</div>
+>⚠️ Only [fixed prices](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj) are used by our native marketplace integrations. Other scenarios seen in our [price system architecture](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) are available only in VTEX marketplaces.
diff --git a/docs/tutorials/en/url-mapping-301-redirect.md b/docs/tutorials/en/url-mapping-301-redirect.md
index b23442a86..843970843 100644
--- a/docs/tutorials/en/url-mapping-301-redirect.md
+++ b/docs/tutorials/en/url-mapping-301-redirect.md
@@ -15,9 +15,7 @@ legacySlug: url-mapping-301-redirect
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-warning">
-<p>This tutorial is for stores using Legacy CMS Portal. For other stores, the configuration is made in <a href="https://help.vtex.com/en/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc">Pages</a>. Please refer to <a href="https://help.vtex.com/en/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV">Managing URL redirects</a> for more information.</p>
-</div>
+>⚠️ This tutorial is for stores using Legacy CMS Portal. For other stores, the configuration is made in [Pages](https://help.vtex.com/en/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc). Please refer to [Managing URL redirects](https://help.vtex.com/en/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV) for more information.
 
 URL mapping is used to redirect specific URLs to other URLs. This feature is useful when a store already has URLs indexed in search engines and wants to redirect them to more attractive ones without changing the SEO and avoiding indexing errors.
 
@@ -46,9 +44,7 @@ There are two ways to add and change URL mapping:
 - **Start date:** date and time when the mapping will no longer be considered.
 - **Active:** indicates if the mapping option is active or inactive.
 
-<div class="alert alert-info"> 
-  <p>To map a URL to home (root directory), fill in the <b>Url to</b> field with a slash <code>/</code>.</p>
-</div>
+>ℹ️ To map a URL to home (root directory), fill in the **Url to** field with a slash `/`.
 
 ## Via spreadsheet
 
diff --git a/docs/tutorials/en/using-header-block-to-achieve-greater-control-of-component-layout-and-positioning.md b/docs/tutorials/en/using-header-block-to-achieve-greater-control-of-component-layout-and-positioning.md
index f5f47dd14..e018ebc52 100644
--- a/docs/tutorials/en/using-header-block-to-achieve-greater-control-of-component-layout-and-positioning.md
+++ b/docs/tutorials/en/using-header-block-to-achieve-greater-control-of-component-layout-and-positioning.md
@@ -15,9 +15,7 @@ legacySlug: using-header-block-to-achieve-greater-control-of-component-layout-an
 subcategory: Z46a6rHVAaAucoiW0skQQ
 ---
 
-<div class="alert alert-info">
-This tutorial assumes you have read <a href="https://help.vtex.com/tutorial/understanding-storebuilder-and-stylesbuilder--16r1nkCNqZI29V00JgmAlE">Understanding Storesbuilder and Stylesbuilder</a> and <a href="https://help.vtex.com/tracks/build-a-store-using-vtex-io--5qJr8BIQXAKec9CpBWrTNv">build a store using VTEX IO</a>
-</div>
+>ℹ️ This tutorial assumes you have read [Understanding Storesbuilder and Stylesbuilder](https://help.vtex.com/tutorial/understanding-storebuilder-and-stylesbuilder--16r1nkCNqZI29V00JgmAlE) and [build a store using VTEX IO](https://help.vtex.com/tracks/build-a-store-using-vtex-io--5qJr8BIQXAKec9CpBWrTNv)
 
 Previously, the developer could only remove or include components, and then IO would determine where to position the components inside the blocks.
 
diff --git a/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 1f84fe31d..7bc8ff1b7 100644
--- a/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/en/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -32,7 +32,7 @@ For instance, a user with a specific campaign referral link might have a promoti
 
 Besides getting session information for a device navigating in the VTEX infrastructure, Session Manager allows you to store your own custom data in that session. This information is easily recoverable and allows you to avoid doing something like setting a cookie to keep track of a specific information on a user. 
 
-<div class="alert alert-info">Session Manager was also built to allow developers to create their own triggers and processing logic. We are still working on the details of that extensible solution, but in the future you should be able to set up the conditional execution of custom code, based on the presence of specific values for parameters in a user's session data.</div>
+>ℹ️ Session Manager was also built to allow developers to create their own triggers and processing logic. We are still working on the details of that extensible solution, but in the future you should be able to set up the conditional execution of custom code, based on the presence of specific values for parameters in a user's session data.
 
 ## Session data aggregation: create and transform calls
 Strictly speaking, Session Manager is a backend API system that stores and processes session data contained in JSON objects. Each VTEX account has settings that indicate which installed apps have a session dependency and how they intend to process this information. 
@@ -51,7 +51,7 @@ Transforms often trigger other transforms, repeating until no further parameter
 6. App C was monitoring session parameter Z, so that triggered Transform 3
 7. Transform 3 had no side-effects on parameters monitored by apps, so the cycle ended and the session was saved until other changes are made.
 
-<div class="alert alert-info">Transform calls are made to all apps simultaneously for the sake of performance. That's why App C was affected both by Transform 2 and Transform 3 - it had no way of knowing that the result of Transform 2 on App B would lead to further changes.</div>
+>ℹ️ Transform calls are made to all apps simultaneously for the sake of performance. That's why App C was affected both by Transform 2 and Transform 3 - it had no way of knowing that the result of Transform 2 on App B would lead to further changes.
 
 When a new session is created, a simpler version of this cycle is executed, which we call **create call**. All apps that have set their configuration with `RunOnCreate: true` will be notified to run simultaneously with an empty input. If these apps modify any parameters that are monitored by other apps, that triggers a transform cycle that will run until the input dependency is resolved.
 
diff --git a/docs/tutorials/en/using-tools-html.md b/docs/tutorials/en/using-tools-html.md
index c2dc4a61e..89f1720e3 100644
--- a/docs/tutorials/en/using-tools-html.md
+++ b/docs/tutorials/en/using-tools-html.md
@@ -15,4 +15,4 @@ legacySlug:
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/vtex-ad-network-beta.md b/docs/tutorials/en/vtex-ad-network-beta.md
index 87c960c8b..2fa9d6f93 100644
--- a/docs/tutorials/en/vtex-ad-network-beta.md
+++ b/docs/tutorials/en/vtex-ad-network-beta.md
@@ -72,8 +72,7 @@ This prioritization process consists of three stages:
 
 The bid amount is set once the ads displayed on the page have been defined. The winning bid will be the final amount of the second-highest bid plus $0.01 USD.
 
-<div class="alert alert-warning">
-Ads may not be selected through the prioritization process if the promoted products do not fit the customer behavior, store coverage, or available budget.</div>
+>⚠️ Ads may not be selected through the prioritization process if the promoted products do not fit the customer behavior, store coverage, or available budget.
 
 ### Quality score
 
@@ -108,9 +107,7 @@ See below how you can join **VTEX Ad Network** as a [merchant](#merchants) that
 
 ### Merchants
 
-<div class="alert alert-warning">
-Currently, only stores developed with <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> can offer ad space.
-</div>
+>⚠️ Currently, only stores developed with [Store Framework](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) can offer ad space.
 
 To make ad space available in your store, you need to contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) to request the installation of the __VTEX Ad Network app for merchants__ in your VTEX account.
 
diff --git a/docs/tutorials/en/vtex-admin-start-here.md b/docs/tutorials/en/vtex-admin-start-here.md
index e739ad2b7..f7942e291 100644
--- a/docs/tutorials/en/vtex-admin-start-here.md
+++ b/docs/tutorials/en/vtex-admin-start-here.md
@@ -52,9 +52,7 @@ Check out our articles for an overview of each menu in your VTEX Admin to learn
 - [User Settings](https://help.vtex.com/en/v4/docs/visao-geral-configuracoes-usuario--1qYAvOTZBVYMosJ7tQm3Ry)  
 - [Billing](https://help.vtex.com/en/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC)  
 
-<div class="alert alert-info">
-You can also use the search bar at the top of the VTEX Admin to find specific pages from the side menu. 
-</div>
+>ℹ️ You can also use the search bar at the top of the VTEX Admin to find specific pages from the side menu.
 
 ### Information Center
 
diff --git a/docs/tutorials/en/vtex-agreement.md b/docs/tutorials/en/vtex-agreement.md
index b381676ce..969dc37b9 100644
--- a/docs/tutorials/en/vtex-agreement.md
+++ b/docs/tutorials/en/vtex-agreement.md
@@ -29,6 +29,4 @@ The Master Agreement applicable to you is available under **Privacy Policy > Pri
 
 You can also find the most updated Master Agreements — the ones applicable to new clients and partners — on the [VTEX Agreement](https://vtex.com/br-pt/privacy-and-agreements/agreements/) page.
 
-<div class="alert alert-info">
-  If the <b>MSA, MPA, Appendix 1,</b> or <b>partnership-specific Terms and Conditions</b> signed with VTEX contain any information different from the one described in this documentation, prioritize your document signed with VTEX.
-  </div>
+>ℹ️ If the **MSA, MPA, Appendix 1,** or **partnership-specific Terms and Conditions** signed with VTEX contain any information different from the one described in this documentation, prioritize your document signed with VTEX.
diff --git a/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
index b25fd7022..53b407587 100644
--- a/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
+++ b/docs/tutorials/en/vtex-dashboard-guide-for-black-week-faq.md
@@ -47,9 +47,9 @@ To configure the reference filter, follow these steps:
 3. Set a date.  
 4. Click `Apply`.  
 
-<div class="alert alert-warning">
-A useful comparison during Black Week is with the same date last year. In the reference filter, select a date between November 21, 2022 and November 27, 2022, ideally the same days of the week. <br>This option is available for clients who were already using the VTEX platform during that period last year.</br>
-</div>
+>⚠️ A useful comparison during Black Week is with the same date last year. In the reference filter, select a date between November 21, 2022 and November 27, 2022, ideally the same days of the week. 
+>
+> This option is available for clients who were already using the VTEX platform during that period last year.</br>
 
 ![reference-en](https://images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/2d4ca5424f4c45e4e8104f37ca11186d/reference-en.png)
 
@@ -73,9 +73,7 @@ To view the best-selling products, in the **Metrics** section click the <i class
 
 ![best-selling-en](https://images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/61ac987b15602d8dfd633019a448fa04/best-selling-en.png)
 
-<div class="alert alert-warning">
-For analyzing or monitoring longer periods, we recommend using our Sales Performance dashboard, which will be explained in the next question.
-  </div>
+>⚠️ For analyzing or monitoring longer periods, we recommend using our Sales Performance dashboard, which will be explained in the next question.
 
 ## How can I track my ecommerce data beyond today?  
 
@@ -141,9 +139,9 @@ There are several reasons why metrics in the real-time Overview might differ fro
 
 To see the data from all stores, use the Sales Performance page, which shows aggregated data with an approximate refresh rate of 90 minutes.  
 
-<div class="alert alert-danger">
-  If your operation uses more than one currency, the <b>Overview dashboard</b> will sum your orders in the currency that is most used in your sales. <br>To make a comparison with the <b>Orders</b> page, you need to sum the order total from all your currencies.</br>
-  </div>
+>❗ If your operation uses more than one currency, the **Overview dashboard** will sum your orders in the currency that is most used in your sales. 
+>
+> To make a comparison with the **Orders** page, you need to sum the order total from all your currencies.</br>
 
 ![all-orders-en](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/70d18cf6c4a5489b7073a610f3dcbe13/all-orders-en.png)  
 
diff --git a/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
index a9402080e..0fd6c3da7 100644
--- a/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/en/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -15,17 +15,13 @@ legacySlug: vtex-intelligent-search-multilanguage-settings-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-<p>This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact [our Support](https://support.vtex.com/hc/pt-br/requests).
 
 [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) is an intelligent search application for ecommerce that is available for stores created with [VTEX IO](https://vtex.com/br-pt/store-framework/). To install and configure VTEX Intelligent Search in your store, read our [Search article](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search). The tool displays search and product suggestions that may interest the user, corrects spelling errors, and understands related words that are not included in the product information.
 
 VTEX Intelligent Search: Multilanguage expands [Intelligent Search’s](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) capabilities and offers a multilingual search experience, ideal for stores that operate in several countries. This feature facilitates adapting the store to new markets and allows users to search in many different languages.
 
-<div class="alert alert-info">
-<p> If you want to expand your ecommerce to another language, contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a> and the VTEX team will perform the necessary configurations.</p>
-</div>
+>ℹ️ If you want to expand your ecommerce to another language, contact [our Support](https://support.vtex.com/hc/pt-br/requests) and the VTEX team will perform the necessary configurations.
 
 After installing VTEX Intelligent Search: Multilanguage, your Catalog’s information will be translated by the [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) app, provided that you have added translations for the following fields: Name, Brand, Description, Categories, CategoryTrees, metadata, metadataKeyword, Specifications, SKU {name}. Read the developer guide on [Translating Catalog content](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) for more details.
 
@@ -50,9 +46,7 @@ To learn more about this field, read our article on [how to configure Merchandis
 ### Synonyms
 You can configure Synonyms for a multi-language store in the Admin by filling out a form or importing a .csv file.
 
-<div class="alert alert-warning">
-  <p> Settings created or changed in <b>Synonyms</b> can take up to 2 hours to be applied in the store. </p>
-</div>
+>⚠️ Settings created or changed in **Synonyms** can take up to 2 hours to be applied in the store.
 
 #### Creating Synonyms via form
 After installing the VTEX Intelligent Search: Multilanguage, the page for creating or editing Synonyms (available through — available on VTEX Admin through __Storefront__ > __Intelligent Search__ > __Synonyms__ —  will contain the additional __Locales__ field, which allows you to choose the locales to which the Synonyms will apply, as illustrated in the image below. Click on the languages you want to select.
@@ -71,9 +65,7 @@ If you prefer to import Synonyms for specific languages via .csv file, you must
 - __Bidirectional__: `<comma-separated terms>;<status>;<comma-separated locales>`
     - For example: `tv,smart tv;true;en-GB`: when searching for one of these terms in the store in English (`locale en-GB`), the search results will return any product that contains one of these terms.
 
-<div class="alert alert-warning">
-<p>If the imported .csv file does not have the column `locale`, the synonym will be valid for all languages available in the store.</p>
-</div>
+>⚠️ If the imported .csv file does not have the column `locale`, the synonym will be valid for all languages available in the store.
 
 To learn more about importing Synonyms spreadsheets, read our article on [how to configure Synonyms in VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
index 50d063c10..e6b9b320b 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
@@ -28,9 +28,7 @@ The **VTEX Pick and Pack Fulfillment** module is related to the order handling p
 * [Settings](#settings)
 * [Users](#users)
 
-<div class="alert alert-danger">
-<b>VTEX Pick and Pack</b> is not an invoicing system. After picking and packing, the order must be invoiced and updated as <code>Invoiced</code> in the OMS, so that <b>VTEX Fulfillment</b> can end the picking and packing flow and proceed to shipping.
-</div>
+>❗ **VTEX Pick and Pack** is not an invoicing system. After picking and packing, the order must be invoiced and updated as `Invoiced` in the OMS, so that **VTEX Fulfillment** can end the picking and packing flow and proceed to shipping.
 
 ## Picking and Packing
 
@@ -155,9 +153,7 @@ In the details page, you can do the actions below. The actions available on the
 * [Add shipping service](#add-shipping-service)
 * [Track order](#track-order)
 
-<div class="alert alert-danger">
-Although the actions above can be performed by <a href="https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#users">users</a> with access to the Admin, typically the actions with an <b>*</b> (asterisk) should be executed only by pickers using their mobile devices, without any access to the store's Admin.
-</div>
+>❗ Although the actions above can be performed by [users](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#users) with access to the Admin, typically the actions with an ***** (asterisk) should be executed only by pickers using their mobile devices, without any access to the store's Admin.
 
 #### Picking
 
@@ -296,9 +292,8 @@ To create a new package, follow the steps below:
 
 You can add a single product to a package or all products at once. After all products are packed, click `Close Packages`. Once you close packages, you are no longer able to add items or make any kind of change.
 
-<div class="alert alert-danger">
-<p><b>VTEX Pick and Pack</b> is not an invoicing system. Once the order gets to <code>Ready for invoicing</code> status, it must be invoiced and updated as <code>Invoiced</code> in OMS. Only after that, <b>VTEX Fulfillment</b> will end the picking and packing flow and proceed to shipping.</p><p>If the order is invoiced in a status different from <code>Ready for invoicing</code>, the system will consider it an external fulfillment and change the order status to <code>Idle</code>, unabling <b>VTEX Pick and Pack</b> to process it.</p>
-</div>
+>❗ **VTEX Pick and Pack** is not an invoicing system. Once the order gets to `Ready for invoicing` status, it must be invoiced and updated as `Invoiced` in OMS. Only after that, **VTEX Fulfillment** will end the picking and packing flow and proceed to shipping.
+> If the order is invoiced in a status different from `Ready for invoicing`, the system will consider it an external fulfillment and change the order status to `Idle`, unabling **VTEX Pick and Pack** to process it.
 
 #### Print receipt and voucher
 
@@ -338,9 +333,7 @@ In **VTEX Pick and Pack**, the **Insights** page provides data and analytics abo
 * [Picking and Packing](#insights-picking-and-packing)
 * [Operation](#insights-operation)
 
-<div class="alert alert-warning">
-To be able to access <b>Insights</b>, you need to have a VTEX Fulfillment Admin user profile, that is different from <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a>. For more information, see the <a href="https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#users">Users</a> section.
-</div>
+>⚠️ To be able to access **Insights**, you need to have a VTEX Fulfillment Admin user profile, that is different from [roles](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). For more information, see the [Users](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#users) section.
 
 ### Insights: Picking and Packing
 
@@ -410,9 +403,7 @@ In order to configure **VTEX Pick and Pack** for your store, in your Admin, go t
 * [Printing](#printing-settings)
 * [Webhooks](#webhooks-settings)
 
-<div class="alert alert-warning">
-To be able to access <b>Settings</b>, you need to be a <a href="https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#users">VTEX Fulfillment admin user</a> or a customer service user.
-</div>
+>⚠️ To be able to access **Settings**, you need to be a [VTEX Fulfillment admin user](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#users) or a customer service user.
 
 ### General settings
 
@@ -626,9 +617,7 @@ To generate an Api-Key, follow the steps below:
 4. Click `Generate`.
 5. Save the Api-Key in a safe place.
 
-  <div class="alert alert-danger">
-You only see the Api-Key once, you will not be able to access this information again, so make sure it is in a safe place.
-</div>
+  >❗ You only see the Api-Key once, you will not be able to access this information again, so make sure it is in a safe place.
 
 6. Enter the password.
 7. Click `Save`.
diff --git a/docs/tutorials/en/vtex-pick-and-pack-last-mile.md b/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
index ff9d60f5e..5c72541ac 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
@@ -26,9 +26,7 @@ With **Last Mile**, merchants have complete visibility of shipping and order tra
 * [Shipping services](#shipping-services)
 * [Settings](#settings)
 
-<div class="alert alert-info">
-To start using Last Mile, it is necessary to adjust the feature's Settings.
-</div>
+>ℹ️ To start using Last Mile, it is necessary to adjust the feature's Settings.
 
 ## Shipping services
 
@@ -88,9 +86,7 @@ To manually create a shipping service from an order, follow the steps below:
 2. Click `Create Service`.
 3. Search the order by entering the order ID in the search box or filter orders by creation date, using the `Filter` button. 
 
-  <div class="alert alert-warning">
-Only orders in the <code>invoiced</code> status will appear in the list and search results.
-</div>
+  >⚠️ Only orders in the `invoiced` status will appear in the list and search results.
 
 4. Click the order.  
 5. Click `Create From Order {order ID}` and you will be redirected to the _New Shipping Service_ page.   
@@ -283,9 +279,7 @@ To activate an external carrier, follow these steps:
 
 The **VTEX Pick and Pack** concept of _user_ is different from the common meaning of the term in VTEX. In **Last Mile**, there is the _admin_ user, but it does not mean the [Sponsor user](https://help.vtex.com/en/tutorial/what-is-the-sponsor-user--3oPr7YuIkEYqUGmEqIMSEy) - also referred as _Admin Super_ and _Owner_.
 
-<div class="alert alert-info">
- For more information, see the articles <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">Roles</a> and <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager</a> resources.
-</div>
+>ℹ️ For more information, see the articles [Roles](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) and [License Manager](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) resources.
 
 To become an admin user in the **Last Mile** module, you must have certain License Manager permissions. We recommend [creating a role](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) identified as “_Fulfillment admin”_, which must have at least the following products and resources associated with it:
 
@@ -294,9 +288,7 @@ To become an admin user in the **Last Mile** module, you must have certain Licen
 |     Insights    | Insights metrics                                                                                                                                                                                                                                                   |
 | License Manager | Get account by identifier<br>Get applications<br>Find user by email<br>View users with account access<br>View all admin users<br>Get resource by key<br>Get role<br>Get paged roles<br>Get paged users<br>Get admin status<br>Get accounts<br>Get accounts by host |
 |    Field Type   | Field's data type. For Read & Write permission, it can be:<br>Number<br>Text<br>Image<br>Date<br>Barcode<br>Check<br>Email<br>For Read Only permission, it can be Number, Text and Email.                                                                          |
-<div class="alert alert-warning">
-If you are an admin user in <a href="link">VTEX Fulfillment</a>, you will automatically be an admin user in Last Mile.
-</div>
+>⚠️ If you are an admin user in [VTEX Fulfillment](link), you will automatically be an admin user in Last Mile.
 
 In **Users**, you can perform the following actions:
 
@@ -361,9 +353,7 @@ To generate an Api-Key, follow the steps below:
 3. Click `Generate`.
 4. Save the Api-Key in a safe place.
 
-  <div class="alert alert-danger">
-You only see the Api-Key once, you will not be able to access this information again, so make sure it is in a safe place.
-</div>
+  >❗ You only see the Api-Key once, you will not be able to access this information again, so make sure it is in a safe place.
 
 5. Enter the password meant for who is using the mobile application.
 6. Click `Save`.
diff --git a/docs/tutorials/en/vtex-pick-and-pack-mobile.md b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
index 21c404a0e..343c2e155 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
@@ -47,9 +47,7 @@ When selecting this worksheet for handling, the app will display the following i
 
 The app will then help you pack each order with its respective items.
 
-<div class="alert alert-warning">
-Worksheets only apply to the order picking and packing steps. You must ship each order separately.
-</div>
+>⚠️ Worksheets only apply to the order picking and packing steps. You must ship each order separately.
 
 ## Creating worksheets
 
@@ -117,9 +115,7 @@ Once picked, the products will be listed in the __Summary__ tab.
 
 There are some scenarios in which products may have to be rejected due to store settings and item availability. 
 
-<div class="alert alert-warning">
-The option to reject items may not be available. If you have any questions, please contact the store admin.
-</div>
+>⚠️ The option to reject items may not be available. If you have any questions, please contact the store admin.
 
 To reject a product from the worksheet, follow the steps below:
 
@@ -135,17 +131,13 @@ To reject all the products from the worksheet at once, follow these steps:
 2. Click the **Set ready for packaging** option.
 3. Click **Reject All Available Items**.
 
-<div class="alert alert-danger">
-If all the items from an order are rejected, the order will be completed automatically.
-</div>
+>❗ If all the items from an order are rejected, the order will be completed automatically.
 
 ## Replacing items
 
 You can also replace the item with another one, depending on the store's settings and the item's availability.
 
-<div class="alert alert-warning">
-The option to replace items may not be available. If you have any questions, please contact the store admin.
-</div>
+>⚠️ The option to replace items may not be available. If you have any questions, please contact the store admin.
 
 To replace worksheet items, follow the steps below:
 
@@ -179,7 +171,7 @@ Follow the steps below to pack items:
 
 1. Under Packing, click the order you want to pack.
 2. Click the <i class="fas fa-plus"></i> button of the product you want to add to the package, or click <i class="fas fa-box"></i> to pack all products at once.
-<div class="alert alert-warning"> If you choose to pack all the order items, the remaining unpacked products will automatically be listed in a new package.</div>
+>⚠️ If you choose to pack all the order items, the remaining unpacked products will automatically be listed in a new package.
 3. Select an existing package or add a new one by clicking `+ Create Package`.
 4. Select the package type you want to add.
 5. Select the number of units of this product you want to add to that package.
@@ -203,9 +195,7 @@ Then, the order will be completed in the app. Depending on your store's settings
 
 The shipping step allows you to create shipping services for orders picked and packed.
 
-<div class="alert alert-warning">
-Shipping is an optional step in the app. It depends on your operation and the store settings.
-</div>
+>⚠️ Shipping is an optional step in the app. It depends on your operation and the store settings.
 
 To ship packages using the Pick and Pack app, follow the steps below:
 
diff --git a/docs/tutorials/en/vtex-shield.md b/docs/tutorials/en/vtex-shield.md
index 9e479ff02..a44757da9 100644
--- a/docs/tutorials/en/vtex-shield.md
+++ b/docs/tutorials/en/vtex-shield.md
@@ -15,9 +15,7 @@ legacySlug: vtex-shield
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/us-en/contato/">contact form</a>.</p>
-</div>
+>ℹ️ If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our [contact form](https://vtex.com/us-en/contato/).
 
 VTEX Shield offers additional, customizable protection layers for stores that prioritize platform resilience and the security standards guaranteed by VTEX's existing security [certifications and practices](https://vtex.com/us-en/security/security-practices/).
 
@@ -52,9 +50,7 @@ Only stores with VTEX Shield that request this feature can request WAF activatio
 
 ## Data Protection Plus
 
-<div class="alert alert-info">
-  <p>This feature is in closed beta and is only available in some regions. If you have any questions, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>.</p>
-</div>
+>ℹ️ This feature is in closed beta and is only available in some regions. If you have any questions, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
 [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) is a data architecture that offers an additional layer of protection for personal data. In this architecture, all PII (Personally Identifiable Information) data is stored in the [Profile System](https://developers.vtex.com/docs/guides/profile-system), a service developed specifically for processing PII following a [set of rules and processes](https://developers.vtex.com/docs/guides/pii-data-architecture-specifications) appropriate for this purpose. 
 
diff --git a/docs/tutorials/en/vtex-shipping-network-dashboard.md b/docs/tutorials/en/vtex-shipping-network-dashboard.md
index 722e45ce3..86feb9a45 100644
--- a/docs/tutorials/en/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/en/vtex-shipping-network-dashboard.md
@@ -15,9 +15,7 @@ legacySlug: vtex-log-dashboard
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-warning">
-Attention: This feature is in Open Beta stage.
-</div>
+>⚠️ Attention: This feature is in Open Beta stage.
 
 VTEX Shipping Network uses order tracking data directly from carriers, keeping you and your customer up to date on the status of each delivery. **VTEX Shipping Network dashboards** manage the data obtained from VTEX Shipping Network, so that you can extract intelligent information for your logistics management. 
 
diff --git a/docs/tutorials/en/vtex-status-page.md b/docs/tutorials/en/vtex-status-page.md
index 5cb14aae5..749091c3c 100644
--- a/docs/tutorials/en/vtex-status-page.md
+++ b/docs/tutorials/en/vtex-status-page.md
@@ -125,9 +125,7 @@ To view incidents from a specific day, hover over the date. To access the page w
 
 ![statuspage-8](https://images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/8ca30c0cd6d89aaca8d92dc21af7274e/statuspage-8.png)
 
-<div class="alert alert-warning">
-  <p>If the scheduled maintenance lasts longer than a day, only the start date will be selected in the calendar. You must open the <a href="#scheduled-maintenance-logs"> maintenance log</a> to see the start and end dates.</p>
-</div>
+>⚠️ If the scheduled maintenance lasts longer than a day, only the start date will be selected in the calendar. You must open the [ maintenance log](#scheduled-maintenance-logs) to see the start and end dates.
 
 Below, we detail the information available in the [incident log](#incident-logs) and the [scheduled maintenance log](#scheduled-maintenance-logs).
 
diff --git a/docs/tutorials/en/vtex-suiteshare.md b/docs/tutorials/en/vtex-suiteshare.md
index 957a0e69c..6cc2d3b83 100644
--- a/docs/tutorials/en/vtex-suiteshare.md
+++ b/docs/tutorials/en/vtex-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: vtex-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/vtex-support-apac.md b/docs/tutorials/en/vtex-support-apac.md
index 81ce333f9..e013c3256 100644
--- a/docs/tutorials/en/vtex-support-apac.md
+++ b/docs/tutorials/en/vtex-support-apac.md
@@ -29,9 +29,7 @@ Our regular support hours are Monday through Friday, from 9am GMT+8 to 7pm GMT+8
 
 Keep in mind that our first response time calculation is based on working hours. The criteria for ticket urgency are defined in the section below.  
 
-<div class="alert alert-warning">
-Emergency support will be available <b>exclusively</b> for Urgent requests and provided via <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Zendesk tickets</a>. Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in <a href="#ticket-urgency">Ticket Urgency</a>.
-</div>
+>⚠️ Emergency support will be available **exclusively** for Urgent requests and provided via [Zendesk tickets](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM). Urgent requests are defined as problems that directly prevent sales or the store’s operation, as described in [Ticket Urgency](#ticket-urgency).
 
 ## Ticket urgency
 
diff --git a/docs/tutorials/en/vtex-tracking-holidays.md b/docs/tutorials/en/vtex-tracking-holidays.md
index 9a1eb600a..cfaf36de7 100644
--- a/docs/tutorials/en/vtex-tracking-holidays.md
+++ b/docs/tutorials/en/vtex-tracking-holidays.md
@@ -17,9 +17,7 @@ subcategory: 7yiFRk9TGfMNeyhT83UljP
 
 IN PROGRESS...
 
-<div class="alert alert-info">
-Registering Holidays is solely linked to the delivery scheduling functionality which is only available for VTEX Tracking users with system integration.
-</div>
+>ℹ️ Registering Holidays is solely linked to the delivery scheduling functionality which is only available for VTEX Tracking users with system integration.
 
 Customers receive a communication via email or SMS containing the scheduled delivery date for their order. If the customer knows that they will not be available to receive their package at the given time, they can reschedule delivery for another date and delivery window.
 
diff --git a/docs/tutorials/en/warehouse.md b/docs/tutorials/en/warehouse.md
index 96feb8b9a..ec1c6cf46 100644
--- a/docs/tutorials/en/warehouse.md
+++ b/docs/tutorials/en/warehouse.md
@@ -22,17 +22,13 @@ It is important to pay attention to the inventory logistics and how the settings
 
 ![EstrategiaEnvio_EN](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/950f5a0342bba5b62dcd0bee100e8a71/Frame_2__3_.svg)
 
-<div class="alert alert-info">
-The carrier that will deliver a certain order is defined by the <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">shipping policy</a>. For a carrier to be selected to deliver the order, its shipping policy must meet the conditions required for the delivery of the order. The shipping policy is linked to the warehouse by the Loading dock.
-</div>
+>ℹ️ The carrier that will deliver a certain order is defined by the [shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140). For a carrier to be selected to deliver the order, its shipping policy must meet the conditions required for the delivery of the order. The shipping policy is linked to the warehouse by the Loading dock.
 
 On the VTEX platform, you can add the name of the warehouse, add items to the warehouse, [configure the loading docks](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) where products will be sent to, configure how long it takes for the order to be prepared before it is sent to the loading dock and the amount charged for its handling. 
 
 After adding a warehouse, you can add the products available there. You can have multiple warehouses and add specific items to each of them, and that will be reflected in your logistics configuration. 
 
-<div class="alert alert-info">
-To add products to a warehouse, they must be previously added to your <a href="https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catalog</a>. This way you can link them to the warehouse via the <a href="https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139">Inventory Management</a> page in the Admin. 
-</div>
+>ℹ️ To add products to a warehouse, they must be previously added to your [catalog](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR). This way you can link them to the warehouse via the [Inventory Management](https://help.vtex.com/en/tutorial/gerenciar-itens-em-estoque--tutorials_139) page in the Admin.
 
 The availability of products in your store represents items from different warehouses. This means that for the end customer, the items that are available during navigation in the store refer to all warehouses. Thus, it is possible that a single purchase includes products from different warehouses. For more information about inventory flow control and product availability, read the article on [Inventory Management](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
@@ -42,14 +38,15 @@ Learn more about how to manage logistics components on the VTEX platform:
 * To monitor and manage inventory items, read the article [Inventory management](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139). 
 * To configure and manage the relationship between warehouses and order pickup see the article on [Loading dock management.](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
 
-<div class="alert alert-warning">
-For the logistics system to work as expected, we suggest that you configure it in the following order:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Trade policy;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj">Loading dock;</a></li>
-<li>Warehouse.</li>
-</ol>
-</body>
-</div>
+>⚠️ For the logistics system to work as expected, we suggest that you configure it in the following order:
+> <body>
+>
+> [Trade policy;](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. [Shipping policy;](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140)
+>
+> 3. [Loading dock;](https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj)
+>
+> Warehouse.
+>
+> </body>
diff --git a/docs/tutorials/en/web-application-firewall-waf.md b/docs/tutorials/en/web-application-firewall-waf.md
index 827aaf49e..8c9edc1a9 100644
--- a/docs/tutorials/en/web-application-firewall-waf.md
+++ b/docs/tutorials/en/web-application-firewall-waf.md
@@ -15,9 +15,7 @@ legacySlug: web-application-firewall-waf
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>This feature is part of <a href="https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
-</div>
+>ℹ️ This feature is part of [VTEX Shield](https://help.vtex.com/en/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). If you are already a VTEX customer and want to adopt VTEX Shield for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Additional fees may apply. If you are not yet a customer but are interested in this solution, please complete our [contact form](https://vtex.com/us-en/contact/).
 
 The Web Application Firewall (WAF) is a security layer designed to protect web applications by monitoring and filtering internet traffic.
 
diff --git a/docs/tutorials/en/what-are-the-requirements-to-start-developing-with-vtex-io.md b/docs/tutorials/en/what-are-the-requirements-to-start-developing-with-vtex-io.md
index c71b2cf08..8216da1a7 100644
--- a/docs/tutorials/en/what-are-the-requirements-to-start-developing-with-vtex-io.md
+++ b/docs/tutorials/en/what-are-the-requirements-to-start-developing-with-vtex-io.md
@@ -47,6 +47,4 @@ Apollo (framework that helps React and GraphQL to work together)
 Fullstack (React + Apollo + GraphQL)
 - https://www.howtographql.com/react-apollo/0-introduction/
 
-<div class="alert alert-info">
-Initially, only front-end development is possible. Therefore, the required initial knowledge scope is limited to React.
-</div>
+>ℹ️ Initially, only front-end development is possible. Therefore, the required initial knowledge scope is limited to React.
diff --git a/docs/tutorials/en/what-are-utm-source-utm-campaign-and-utm-medium.md b/docs/tutorials/en/what-are-utm-source-utm-campaign-and-utm-medium.md
index 919d37b06..f564e01e4 100644
--- a/docs/tutorials/en/what-are-utm-source-utm-campaign-and-utm-medium.md
+++ b/docs/tutorials/en/what-are-utm-source-utm-campaign-and-utm-medium.md
@@ -23,9 +23,7 @@ Or you can define that, for that same UTM, certain benefits will be applied. Tha
 
 In a nutshell, the platform allows you to take certain actions according to the origin of the traffic to the store.
 
-<div class="alert alert-info">
-On the <strong>Orders Management</strong> screen, only utm_source is <a href="https://help.vtex.com/en/tutorial/filtering-orders-on-the-oms">available for filter</a>.
-</div>
+>ℹ️ On the **Orders Management** screen, only utm_source is [available for filter](https://help.vtex.com/en/tutorial/filtering-orders-on-the-oms).
 
 ### Types of UTM
 
@@ -38,9 +36,7 @@ But you can use these UTMs in whatever way meets your business rules best.
 
 Therefore, in practice, what matters is defining the correct action for the values of these parameters.
 
-<div class="alert alert-danger">
-Notice: <strong>special characters</strong> should not be used in UTMs. These variables on function properly when <strong> alphanumerical, hiphen and underscore </strong> characters are used.
-</div>
+>❗ Notice: **special characters** should not be used in UTMs. These variables on function properly when ** alphanumerical, hiphen and underscore ** characters are used.
 
 For more information about issues with adding UTMs to cart, go to [Why are the UTMs not being applied to the cart?](https://developers.vtex.com/vtex-rest-api/docs/check-marketing-utms-used-at-checkout#why-are-the-utms-not-being-applied-to-the-cart).
 
diff --git a/docs/tutorials/en/what-is-a-franchise-account.md b/docs/tutorials/en/what-is-a-franchise-account.md
index 84f2cf395..7e180d99a 100644
--- a/docs/tutorials/en/what-is-a-franchise-account.md
+++ b/docs/tutorials/en/what-is-a-franchise-account.md
@@ -46,14 +46,13 @@ Each franchise account automatically operates as a White Label Seller of the mai
 
 End customers do not choose or acknowledge the existence of White Label Sellers at any point in the process. In this logic, the consumers have a relationship with the brand (main account) and not with the physical stores (franchise accounts).
 
-<div class="alert alert-info">
-<p>Although all franchise accounts operate as White Label Sellers of the main account, these concepts do not mean the same thing. The franchise account is a type of account, while being White Label is a property of the seller.
-<ul>
-<li><strong>Account</strong>: can be a franchise account or a regular account.</li>
-<li><strong>Seller</strong>: can be of White Label type or non-White Label type.</li>
-</ul>
-As these concepts are independent, it is <strong>eventually</strong> possible that a franchise account operates as a non-White Label Seller of a marketplace other than the main account.</p>
-</div>
+>ℹ️ Although all franchise accounts operate as White Label Sellers of the main account, these concepts do not mean the same thing. The franchise account is a type of account, while being White Label is a property of the seller.
+>
+> ***Account**: can be a franchise account or a regular account.
+>
+> ***Seller**: can be of White Label type or non-White Label type.
+>
+> As these concepts are independent, it is **eventually** possible that a franchise account operates as a non-White Label Seller of a marketplace other than the main account.
 
 ## Franchise account configuration
 
@@ -96,9 +95,7 @@ Once you have [changed this configuration](#configuring-payment-methods-specific
 
 VTEX offers split payment solutions that can make the distribution of receivables to sellers automatic. For more information, please refer to the article about [Split payment](https://help.vtex.com/en/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx).
 
-<div class="alert alert-warning">
-<p>If you wish to implement the VTEX Sales App, it is necessary for physical stores to use the payment methods from the main account.</p>
-</div>
+>⚠️ If you wish to implement the VTEX Sales App, it is necessary for physical stores to use the payment methods from the main account.
 
 ## Request the creation of a franchise account
 
diff --git a/docs/tutorials/en/what-is-a-marketplace.md b/docs/tutorials/en/what-is-a-marketplace.md
index 1bff6e473..d7b814c4b 100644
--- a/docs/tutorials/en/what-is-a-marketplace.md
+++ b/docs/tutorials/en/what-is-a-marketplace.md
@@ -21,9 +21,7 @@ In a shopping experience, a user browses a website by selecting products to incl
 
 A marketplace can also be understood as a *showcase store*, displaying its own products and also products from other stores (the sellers). Usually, a marketplace is a store with good users traffic. This encourages other stores to display their products in the marketplace for greater conversion. In such scenario, the __marketplace__ is the shop responsible for closing the purchase, and the __seller__ is the store responsible for delivering the order.
 
-<div class="alert alert-info">
-Following this logic, we can conclude that a VTEX store that sells its own products in its own store acts as a marketplace and a seller simultaneously. In this context, payment is made within the store environment (marketplace) and the delivery of the order is a responsibility of that same store (seller). See more details on this subject at <a href="https://help.vtex.com/tutorial/o-que-sao-pedidos-com-origem-marketplace-e-origem-fulfillment--6eVYrmUAwMOeKICU2KuG06e">our article</a> on the origin of the orders.
-</div>
+>ℹ️ Following this logic, we can conclude that a VTEX store that sells its own products in its own store acts as a marketplace and a seller simultaneously. In this context, payment is made within the store environment (marketplace) and the delivery of the order is a responsibility of that same store (seller). See more details on this subject at [our article](https://help.vtex.com/tutorial/o-que-sao-pedidos-com-origem-marketplace-e-origem-fulfillment--6eVYrmUAwMOeKICU2KuG06e) on the origin of the orders.
 
 ## Related articles
 
diff --git a/docs/tutorials/en/what-is-an-affiliate.md b/docs/tutorials/en/what-is-an-affiliate.md
index d66a5ffdc..66b01d3a8 100644
--- a/docs/tutorials/en/what-is-an-affiliate.md
+++ b/docs/tutorials/en/what-is-an-affiliate.md
@@ -15,9 +15,7 @@ legacySlug: what-is-affiliate
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-<div class="alert alert-info"> 
-Affiliates in VTEX are different from the <a href="https://en.wikipedia.org/wiki/Affiliate_marketing">usual definition</a>. Read below to learn more. 
-</div>
+>ℹ️ Affiliates in VTEX are different from the [usual definition](https://en.wikipedia.org/wiki/Affiliate_marketing). Read below to learn more.
 
 [Configuring an affiliate](https://help.vtex.com/en/tutorial/como-configurar-afiliado) will only be necessary when the store acts as a seller in a marketplace.
 
diff --git a/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md b/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
index a8c0217ea..11f09c53a 100644
--- a/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
+++ b/docs/tutorials/en/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
@@ -73,6 +73,4 @@ It collects data about the behavior of users and compares them with suspicious p
 
 At VTEX, the payment operator first approves the purchase and then the anti-fraud assesses the order. If everything goes OK, it follows its normal flow. Some examples of anti-fraud are: ClearSale and Konduto. 
 
-<div class="alert alert-info">
-It is important to emphasize that each business depends on specific factors that influence the decision of which modality to use. There are several variables that can determine the choice of a payment method and what your financial flow will be. It is critical, therefore, to keep the actual needs and purposes of the retailer and desired project in mind.
-</div>
+>ℹ️ It is important to emphasize that each business depends on specific factors that influence the decision of which modality to use. There are several variables that can determine the choice of a payment method and what your financial flow will be. It is critical, therefore, to keep the actual needs and purposes of the retailer and desired project in mind.
diff --git a/docs/tutorials/en/what-is-the-period-considered-for-calculating-my-billing.md b/docs/tutorials/en/what-is-the-period-considered-for-calculating-my-billing.md
index f2905d65a..7d818376a 100644
--- a/docs/tutorials/en/what-is-the-period-considered-for-calculating-my-billing.md
+++ b/docs/tutorials/en/what-is-the-period-considered-for-calculating-my-billing.md
@@ -22,6 +22,4 @@ So, the period considered is always from the first to the last day of a given mo
 ## Example 
 An invoice is issued on 03/01, referring to "February". It will take into account all orders that got the __approved__ status in the period between 02/01 and 02/28.
 
-<div class="alert alert-warning">
-If you're charged before your store goes live, note that it relates to the <strong>monthly fee</strong> of your environment maintenance. This value is charged because even though the store is not in production it is already consuming VTEX structure.
-</div>
+>⚠️ If you're charged before your store goes live, note that it relates to the **monthly fee** of your environment maintenance. This value is charged because even though the store is not in production it is already consuming VTEX structure.
diff --git a/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
index 1d635a630..8c126ab04 100644
--- a/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/en/what-is-the-purpose-of-the-customized-control.md
@@ -33,9 +33,7 @@ To create a customized control tag, click on Add, enter a name, a tag name, and
 
 ![cms-custom-elements EN / ES](https://images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
 
-<div class="alert alert-warning">
-  <p><b>Warning:</b> do not create an HTML type control with an element <code>title</code>. This may interfere with your store operation.</p>
-</div>
+>⚠️ **Warning:** do not create an HTML type control with an element `title`. This may interfere with your store operation.
 
 ## Application of customized controls on a page template
 
diff --git a/docs/tutorials/en/what-is-the-shared-cart.md b/docs/tutorials/en/what-is-the-shared-cart.md
index d56fc9841..86a8c0d0a 100644
--- a/docs/tutorials/en/what-is-the-shared-cart.md
+++ b/docs/tutorials/en/what-is-the-shared-cart.md
@@ -33,15 +33,11 @@ Example:
 
 - **Shared cart URL**: `https://www.{storename}.com/checkout/?orderFormId=31155bb8fd6944c99829c171aa8ed5c4#/cart`
 
-<div class="alert alert-warning">
-When building the shared cart URL, make sure that the querystring <b>?orderFormId=...</b> is placed between <b>/checkout/</b> and <b>#/cart</b>.
-</div>
+>⚠️ When building the shared cart URL, make sure that the querystring **?orderFormId=...** is placed between **/checkout/** and **#/cart**.
 
 To gain access to cart identification information, access [Checkout API](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview).
 
-<div class="alert alert-info">
-The use of the abandoned cart functionality is optional, generating no impact for stores that do not use it.
-</div>
+>ℹ️ The use of the abandoned cart functionality is optional, generating no impact for stores that do not use it.
 
 ## Information security
 
@@ -53,6 +49,4 @@ To learn more about data protection, visit [SmartCheckout Security](https://help
 
 When new parameters are inserted into a URL, such as a `querystring`, page tracking can change, impacting assessments performed by systems such as the Google Analytics conversion funnel. To use page tracking service with additional parameters, see updated rules at [Setting up the sales funnel on Google Analytics](https://help.vtex.com/tutorial/configurar-funil-de-vendas-no-google-analytics#).
 
-<div class="alert alert-info">
-If you use another page tracking system in your store, check the internal documentation for that system.
-</div>
+>ℹ️ If you use another page tracking system in your store, check the internal documentation for that system.
diff --git a/docs/tutorials/en/what-is-the-sponsor-user.md b/docs/tutorials/en/what-is-the-sponsor-user.md
index f1c4d9f3b..6a9a66ce7 100644
--- a/docs/tutorials/en/what-is-the-sponsor-user.md
+++ b/docs/tutorials/en/what-is-the-sponsor-user.md
@@ -43,6 +43,4 @@ Only the Sponsor user can perform these critical maintenance and authorization a
 
 In addition, when VTEX needs to communicate store-sensitive information, such as changes in roles, such communication is done directly and exclusively with the Sponsor user.
 
-<div class="alert alert-info">
-The creation of <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet">authentication credentials</a> (appKey/appToken) for API integrations is no longer restricted to the Sponsor user. See this <a href="https://help.vtex.com/en/announcements/changes-in-the-name-and-restricted-actions-available-to-the-master-user">announcement</a> for more details about this change.
-</div>
+>ℹ️ The creation of [authentication credentials](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) (appKey/appToken) for API integrations is no longer restricted to the Sponsor user. See this [announcement](https://help.vtex.com/en/announcements/changes-in-the-name-and-restricted-actions-available-to-the-master-user) for more details about this change.
diff --git a/docs/tutorials/en/what-is-vtex-io.md b/docs/tutorials/en/what-is-vtex-io.md
index 9690ac311..2c46c0935 100644
--- a/docs/tutorials/en/what-is-vtex-io.md
+++ b/docs/tutorials/en/what-is-vtex-io.md
@@ -15,9 +15,7 @@ legacySlug: what-is-vtex-io
 subcategory: 5eBwrcLFVSwYGSOQqGKQYW
 ---
 
-<div class="alert alert-info">
-VTEX IO is a serverless development environment that enables you to build high-quality web apps fast, without dealing with infrastructure and scalability concerns.
-</div>
+>ℹ️ VTEX IO is a serverless development environment that enables you to build high-quality web apps fast, without dealing with infrastructure and scalability concerns.
 
 Today, in addition to developing the code that implements business logic, technology companies need to worry about much of the infrastructure behind the software they create (server configuration, access permissions, horizontal and vertical scaling, security, etc). VTEX IO is a service that envelops all the architectural complexity inherent to modern web software, removing that responsibility from the developer.
 
diff --git a/docs/tutorials/en/when-should-i-group-products-in-the-same-shipment.md b/docs/tutorials/en/when-should-i-group-products-in-the-same-shipment.md
index ec1ce49bb..6e13cfdb8 100644
--- a/docs/tutorials/en/when-should-i-group-products-in-the-same-shipment.md
+++ b/docs/tutorials/en/when-should-i-group-products-in-the-same-shipment.md
@@ -23,9 +23,7 @@ It's very common that within a single purchase products come from different inve
 
 This is a valid practice, for example, in the case of carriers such as Correios (in Brazil), where for each delivery the invoice is required, which is often the same for several items, or in a scenario where a tore has physically distant inventories, which share the same warehouse dock.
 
-<div class="alert alert-warning">
-Shipping groups are created by summing the cost of the inventory and warehouse costs.
-</div>
+>⚠️ Shipping groups are created by summing the cost of the inventory and warehouse costs.
 
 ### Related articles
 - [How to set up shipment](https://help.vtex.com/en/tutorial/como-funciona-a-remessa?locale=en)
diff --git a/docs/tutorials/en/white-label-sellers-selection.md b/docs/tutorials/en/white-label-sellers-selection.md
index ceccf5d2d..3df335615 100644
--- a/docs/tutorials/en/white-label-sellers-selection.md
+++ b/docs/tutorials/en/white-label-sellers-selection.md
@@ -51,9 +51,7 @@ When a customer is browsing the marketplace from an undefined location, only the
 
 When the marketplace has access to the customer's location, either through captured geolocation or customer provided data, the VTEX platform queries for all the sellers covering that specific region to display the product price and availability in the window display. Learn more in [Setting up price and availability of SKUs by Region](https://help.vtex.com/en/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc).
 
-<div class="alert alert-warning">
-When the customer location is known, the VTEX platform queries for all sellers by default, using the <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2</a> feature. However, some VTEX stores may still be operating with Region v1, which has a limited seller selection for the window display.
-</div>
+>⚠️ When the customer location is known, the VTEX platform queries for all sellers by default, using the [Region v2](https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release) feature. However, some VTEX stores may still be operating with Region v1, which has a limited seller selection for the window display.
 
 ## Seller selection in the shopping cart
 
diff --git a/docs/tutorials/en/why-does-payment-with-registered-bank-slip-require-authentication.md b/docs/tutorials/en/why-does-payment-with-registered-bank-slip-require-authentication.md
index ee2a460c0..a6f2a8013 100644
--- a/docs/tutorials/en/why-does-payment-with-registered-bank-slip-require-authentication.md
+++ b/docs/tutorials/en/why-does-payment-with-registered-bank-slip-require-authentication.md
@@ -23,6 +23,4 @@ This information is saved in the customer profile and is displayed in the regist
 
 Because of this, the login is requested both at the time of __choosing the registered bank slip as payment method__ and the time of __getting the bank slip in the page of Order Placed__.
 
-<div class="alert alert-info">
-Authentication is required only as of the second purchase. Since during the first purchase the data is being saved for the first time, there's no need for authentication. The registered bank slip will be issued with the data informed in this first purchase and only the person who filled the information will have access to them.
-</div>
+>ℹ️ Authentication is required only as of the second purchase. Since during the first purchase the data is being saved for the first time, there's no need for authentication. The registered bank slip will be issued with the data informed in this first purchase and only the person who filled the information will have access to them.
diff --git a/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index 2dd6b5ba4..a6f50424e 100644
--- a/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/en/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 This scenario usually happens because of an inconsistency in the user's registration fields. To verify it, we need to access this customer's data in your store's __Profile System__.
 
-<div class="alert alert-warning">
-This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Master Data version characteristics
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ This article describes how Master Data v1 works. It is important that you evaluate which Master Data version meets the needs of your operation or is already in use.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Master Data version characteristics
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 Follow the steps below to validate the information:
 
diff --git a/docs/tutorials/en/widget.md b/docs/tutorials/en/widget.md
index f58c24323..a5e2a6dc4 100644
--- a/docs/tutorials/en/widget.md
+++ b/docs/tutorials/en/widget.md
@@ -15,6 +15,4 @@ legacySlug: widget
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/wix-suiteshare.md b/docs/tutorials/en/wix-suiteshare.md
index e9fc0c2f1..1397eed0d 100644
--- a/docs/tutorials/en/wix-suiteshare.md
+++ b/docs/tutorials/en/wix-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: wix-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/wordpress-suiteshare.md b/docs/tutorials/en/wordpress-suiteshare.md
index 95d1a49c8..7f91f3955 100644
--- a/docs/tutorials/en/wordpress-suiteshare.md
+++ b/docs/tutorials/en/wordpress-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: wordpress
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/en/working-with-master-data-rest-api.md b/docs/tutorials/en/working-with-master-data-rest-api.md
index 42720195a..457863352 100644
--- a/docs/tutorials/en/working-with-master-data-rest-api.md
+++ b/docs/tutorials/en/working-with-master-data-rest-api.md
@@ -15,4 +15,4 @@ legacySlug: master-data-schemas
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Content under translation</div>
+>⚠️ Content under translation
diff --git a/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md b/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md
index 26d5fd9e9..28057bacb 100644
--- a/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md
+++ b/docs/tutorials/en/writing-an-effective-ticket-to-vtex-support.md
@@ -49,9 +49,7 @@ To check if the problem is associated with IO, follow the steps below:
     vtex uninstall {theme}
     ```
 
-    <div class="alert alert-info">
-    You can check for any installed themes using the <code>vtex list</code> command, which lists all the applications installed in the store.
-    </div>
+    >ℹ️ You can check for any installed themes using the `vtex list` command, which lists all the applications installed in the store.
 
 4.	Clone the default Store Framework theme on your computer.
 5.	At the command prompt, access the default theme folder.
@@ -59,7 +57,7 @@ To check if the problem is associated with IO, follow the steps below:
     ```
     vtex link
     ```
-    <div class="alert alert-warning"> If your store doesn't have the Reviews and Ratings app installed, you may receive an error when trying to create the link. To avoid this, remove this app from the `peer dependencies` list in the `manifest.json` file of the default theme. </div>
+    >⚠️ If your store doesn't have the Reviews and Ratings app installed, you may receive an error when trying to create the link. To avoid this, remove this app from the `peer dependencies` list in the `manifest.json` file of the default theme.
 
 7.	Access your workspace's storefront using the URL:
     ```
diff --git a/docs/tutorials/en/zapier-suiteshare.md b/docs/tutorials/en/zapier-suiteshare.md
index 82ce2e758..6d2a17e15 100644
--- a/docs/tutorials/en/zapier-suiteshare.md
+++ b/docs/tutorials/en/zapier-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: zapier
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>This content is only available in Portuguese.</p>
-</div>
+>⚠️ This content is only available in Portuguese.
diff --git a/docs/tutorials/es/account-management.md b/docs/tutorials/es/account-management.md
index 429433801..cb66ec8a3 100644
--- a/docs/tutorials/es/account-management.md
+++ b/docs/tutorials/es/account-management.md
@@ -19,9 +19,7 @@ Para acceder a la Configuración de la cuenta, haz clic en tu avatar de perfil,
 
 En la página de cada cuenta usted encuentra datos básicos sobre la tienda virtual, configuraciones de dominio y multidominio, claves de acceso a APIs, logotipo del empresa e información de contacto.
 
-<div class="alert alert-info">
-Algunos de esos datos son útiles solamente para VTEX, y pueden no reflejar modificación de la información exhibida en la tienda.
-</div>
+>ℹ️ Algunos de esos datos son útiles solamente para VTEX, y pueden no reflejar modificación de la información exhibida en la tienda.
 
 ## Botón de Activo/Inactivo
 
@@ -54,17 +52,15 @@ También puedes utilizar el botón `Configurar otra tienda` para [Crear multitie
 
 En la sección **Hosts** debes agregar el dominio principal de tu tienda, que ha sido [configurado con el apuntamiento de DNS](https://help.vtex.com/es/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-danger">
-En caso de que su operación tenga más de una cuenta o subcuentas VTEX, no intercambie dominios entre ellas. Esto provocará errores en diferentes aspectos de tu tienda.
-</div>
+>❗ En caso de que su operación tenga más de una cuenta o subcuentas VTEX, no intercambie dominios entre ellas. Esto provocará errores en diferentes aspectos de tu tienda.
 
 Para agregar un nuevo host, haz clic en `Agregar un nuevo dominio` e introduce el dominio en el campo de texto.
 
-<div class="alert alert-warning">
-Si agregas más de un dominio como host de tu tienda, todos ellos mostrarán el mismo contenido. Sin embargo, recomendamos registrar solo un dominio y utilizar redirecciones para los demás. Obtenga más información sobre redirecciones:
-<ul><li><a href=”https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirección de otras direcciones</a></li>
-  <li><a href=”https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acceso sin www</a></li></ul> 
-</div>
+>⚠️ Si agregas más de un dominio como host de tu tienda, todos ellos mostrarán el mismo contenido. Sin embargo, recomendamos registrar solo un dominio y utilizar redirecciones para los demás. Obtenga más información sobre redirecciones:
+>
+> *<a href=”https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirección de otras direcciones</a>
+>
+> * <a href=”https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acceso sin www</a>
 
 #### Subdominios
 
@@ -80,9 +76,7 @@ La parte de **Contatos** es visible solamente para el usuario que esté registra
 
 Después que un usuario llena y guarda **Nombre** e **E-mail**, en los campos de contacto, un email automático le es enviado informando sobre el registro y solicitando generación de contraseña (si él no posee ningún acceso al admin).
 
-<div class="alert alert-info">
-La plantilla para este correo electrónico automático se puede cambiar en el <a href="https://help.vtex.com/es/tutorial/understanding-the-message-center--tutorials_84">Centro de mensajes</a> modificando la plantilla de <i>registro de cuenta</i>.
-</div>
+>ℹ️ La plantilla para este correo electrónico automático se puede cambiar en el [Centro de mensajes](https://help.vtex.com/es/tutorial/understanding-the-message-center--tutorials_84) modificando la plantilla de <i>registro de cuenta</i>.
 
 ![registro de cuenta](https://images.ctfassets.net/alneenqid6w5/7uIJliLTJ6wEMeeoqiSMQ/6c37511bd70d8035b11e18abc99b36d0/registro_de_cuenta.jpg)
 
diff --git a/docs/tutorials/es/actions-for-vtex-marketplace-operation.md b/docs/tutorials/es/actions-for-vtex-marketplace-operation.md
index b7f89fa92..2bd787b2d 100644
--- a/docs/tutorials/es/actions-for-vtex-marketplace-operation.md
+++ b/docs/tutorials/es/actions-for-vtex-marketplace-operation.md
@@ -46,9 +46,7 @@ El [Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-pas
 
 Esta herramienta es una opción recomendada para los _marketplaces_ que deseen tener más control sobre la curación de los productos que ofrecen.
 
-<div class="alert alert-info">
-Para activar el Seller Portal para sus sellers, el marketplace debe solicitar esta funcionalidad poniéndose en contacto con el CSM de su cuenta VTEX. 
-</div>
+>ℹ️ Para activar el Seller Portal para sus sellers, el marketplace debe solicitar esta funcionalidad poniéndose en contacto con el CSM de su cuenta VTEX.
 
 ## Catalogar anuncios
 
@@ -56,9 +54,7 @@ Un producto de un_ seller_ que haya sido enviado al _marketplace_ con la informa
 
 El proceso de catalogación se realiza en la página de [SKU recibidos](https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus/) en el menú **MARKETPLACE > Sellers** de tu Admin VTEX o a través de llamadas a la API de [Match Received SKUs](https://developers.vtex.com/vtex-rest-api/reference/match). 
 
-<div class="alert alert-info">
-Antes de aprobar un anuncio, es importante asegurarse de que la información de producto enviada por el seller coincida con tu estrategia comercial. A la hora de catalogar anuncios, ten en cuenta la calidad de la información enviada por el seller, como el precio, la descripción del producto y la imagen.
-</div>
+>ℹ️ Antes de aprobar un anuncio, es importante asegurarse de que la información de producto enviada por el seller coincida con tu estrategia comercial. A la hora de catalogar anuncios, ten en cuenta la calidad de la información enviada por el seller, como el precio, la descripción del producto y la imagen.
 
 [VTEX Matcher](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424) es la herramienta utilizada por los _marketplaces_ para evaluar los anuncios enviados por los _sellers_ y acelerar el proceso de catalogación. Es posible configurar VTEX Matcher para que funcione con reglas diferentes a la configuración _por defecto_ a través de la [API de Aprobación automática](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig).
 
diff --git a/docs/tutorials/es/activating-new-vtex-cdn.md b/docs/tutorials/es/activating-new-vtex-cdn.md
index 285c81952..4d6fbe84f 100644
--- a/docs/tutorials/es/activating-new-vtex-cdn.md
+++ b/docs/tutorials/es/activating-new-vtex-cdn.md
@@ -15,9 +15,7 @@ legacySlug: activar-nueva-cdn-de-vtex
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
-<div class="alert alert-warning">
-En un compromiso de constante evolución de nuestro producto, VTEX está poniendo a disposición de tus tiendas una nueva CDN (Content Delivery Network). En este nuevo modelo, <strong>todas las páginas del sitio se entregarán a partir de esa nueva CDN especializada</strong>, sin limitarse a los archivos estáticos.
-</div>
+>⚠️ En un compromiso de constante evolución de nuestro producto, VTEX está poniendo a disposición de tus tiendas una nueva CDN (Content Delivery Network). En este nuevo modelo, **todas las páginas del sitio se entregarán a partir de esa nueva CDN especializada**, sin limitarse a los archivos estáticos.
 
 Una Red de Entrega de Contenido (traducción libre de su acrónimo) tiene su foco en seguridad, baja latencia y altas velocidades de transferencia, trabajando con las mejores tecnologías para este propósito, incluso siendo geográficamente cercana al cliente que accede a la tienda virtual.
 
@@ -94,9 +92,7 @@ Indicaciones antiguas usan direcciones como:
 
 Independientemente de cuál sea el caso de tu tienda, deberá realizar la actualización al nuevo estándar.
 
-<div class="alert alert-danger">
-<strong>Importante:</strong> el CNAME antiguo<strong> se debe eliminar</strong>. La existencia de dos entradas en su DNS probablemente va a ocasionar problemas. Se debe mantener sólo la nueva entrada CNAME.
-</div>
+>❗ **Importante:** el CNAME antiguo** se debe eliminar**. La existencia de dos entradas en su DNS probablemente va a ocasionar problemas. Se debe mantener sólo la nueva entrada CNAME.
 
 Não se esqueça de solicitar a ativação final pelo [formulário](https://docs.google.com/forms/d/e/1FAIpQLSdI2FBXGmlSOXEtWxrYfVveln7xOJcmYotqrKfgFgmHn771Fg/viewform). La tienda va a funcionar sólo con CNAME y HTTPS, pero su llenado nos ayuda a activar de forma anticipada la CDN para su tienda, para que disfrutes de las nuevas features.
 
diff --git a/docs/tutorials/es/activating-skus-in-bulk.md b/docs/tutorials/es/activating-skus-in-bulk.md
index 19388a1c1..407ee6912 100644
--- a/docs/tutorials/es/activating-skus-in-bulk.md
+++ b/docs/tutorials/es/activating-skus-in-bulk.md
@@ -29,10 +29,9 @@ Para activar sus SKUs usando VTEX Admin, siga los pasos siguientes:
 1. Acceda a la URL `https://{accountname}.myvtex.com/admin/site/productskuactivateall.aspx `.
 2. Haga clic en `Activar todos los SKUs`.
 
-<div class="alert alert-warning">
-<p>Los SKUs registrados con datos inválidos no tendrán el flag de <em>Activar SKU si es posible</em> activado.</p>
-<p>Si no todos los SKUs se han marcado con el flag de <em> Activar SKU si es posible </em>, repita el proceso descrito anteriormente.</p>
-</div>
+>⚠️ Los SKUs registrados con datos inválidos no tendrán el flag de *Activar SKU si es posible* activado.
+>
+> Si no todos los SKUs se han marcado con el flag de * Activar SKU si es posible *, repita el proceso descrito anteriormente.
 
 ## Activar un grupo de SKUs
 
diff --git a/docs/tutorials/es/active-campaign-suiteshare.md b/docs/tutorials/es/active-campaign-suiteshare.md
index d3cddd385..e7ba2208a 100644
--- a/docs/tutorials/es/active-campaign-suiteshare.md
+++ b/docs/tutorials/es/active-campaign-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: active-campaign-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md b/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md
index 67afd8673..5ccc3bc01 100644
--- a/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md
+++ b/docs/tutorials/es/add-3ds-support-to-the-integration-with-adyen.md
@@ -30,9 +30,7 @@ Para añadir soporte para [3DS](https://help.vtex.com/es/tutorial/what-is-3d-sec
 
 Después de configurar el conector en VTEX, tiene que acceder al panel de Adyen para habilitar el 3DS en las transacciones de su tienda.
 
-<div class="alert alert-warning">
-  Se recomienda que primero realice la configuración en el entorno Test. Solo después de realizar las validaciones adecuadas, acceda al entorno <B>Live</B> para la configuración final.
-  </div>
+>⚠️ Se recomienda que primero realice la configuración en el entorno Test. Solo después de realizar las validaciones adecuadas, acceda al entorno <B>Live</B> para la configuración final.
 
 1. Haga clic en los enlaces a continuación para acceder al entorno Test y Live de Adyen.
 
diff --git a/docs/tutorials/es/adding-a-record-on-a-master-data-form.md b/docs/tutorials/es/adding-a-record-on-a-master-data-form.md
index de574821b..1a7a192ba 100644
--- a/docs/tutorials/es/adding-a-record-on-a-master-data-form.md
+++ b/docs/tutorials/es/adding-a-record-on-a-master-data-form.md
@@ -20,21 +20,16 @@ Para agregar un registro en un formulario de Master Data, debes acceder a Master
 
 Los campos pueden configurarse como editables o no editables directamente en la entidad de datos. Más información en [Entidad de datos](https://help.vtex.com/es/tutorial/entidade-de-dados--tutorials_1265).
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar la versión de Master Data que es más adecuada para tu operación o verificar la que esté en uso. Más información:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar la versión de Master Data que es más adecuada para tu operación o verificar la que esté en uso. Más información:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Agregar un registro
 
diff --git a/docs/tutorials/es/adding-a-seller-beta.md b/docs/tutorials/es/adding-a-seller-beta.md
index f6626886b..bba05b583 100644
--- a/docs/tutorials/es/adding-a-seller-beta.md
+++ b/docs/tutorials/es/adding-a-seller-beta.md
@@ -19,9 +19,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 Para agregar un seller no identificable, también conocido como [seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), es necesario tener este modelo previsto en el contrato con VTEX. Una vez acordado un contrato con el representante de ventas de VTEX responsable de tu _marketplace_, solicita la [adición de una cuenta franquicia](https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) por medio de nuestro Soporte. Todas las cuentas franquicias se crean como un _seller white label_, y no es posible cambiar el tipo de _seller_ después de su creación. 
 
-<div class="alert alert-info">
-Si quieres encontrar nuevos partners para vender en tu marketplace, utiliza Marketplace Network que facilita la identificación y contacto entre marketplaces y sellers que operan en el ecosistema VTEX, además de conectores certificados (partners).
-</div> 
+>ℹ️ Si quieres encontrar nuevos partners para vender en tu marketplace, utiliza Marketplace Network que facilita la identificación y contacto entre marketplaces y sellers que operan en el ecosistema VTEX, además de conectores certificados (partners). 
 
 1. En tu Admin VTEX, accede a _MARKETPLACE > Sellers > Gestión_.  
 2. Haz clic en `Agregar seller`.  
@@ -65,9 +63,7 @@ Si quieres encontrar nuevos partners para vender en tu marketplace, utiliza Mark
 - **Cambios y devoluciones:** descripción de la política de cambios y devoluciones previamente acordada entre el _marketplace_ y el _seller_.
 - **Política de privacidad y seguridad:** descripción de la política de seguridad previamente acordada entre el _marketplace_ y el _seller_.
 
-<div class="alert alert-info">
-Con la nueva versión de la página, lanzada el 2022, eliminamos el campo Endpoint del Catálogo porque ya no es necesario para la integración con un nuevo seller. Si es necesario, aún es posible gestionar el campo a través de la API.
-</div>
+>ℹ️ Con la nueva versión de la página, lanzada el 2022, eliminamos el campo Endpoint del Catálogo porque ya no es necesario para la integración con un nuevo seller. Si es necesario, aún es posible gestionar el campo a través de la API.
 
 Después de rellenar los campos y hacer clic en **Guardar**, el _seller_ será agregado al _marketplace_. Para completar la configuración de tu tienda como _marketplace_ también debes [mapear las marcas, categorías y especificaciones del seller](https://help.vtex.com/es/tutorial/mapeando-categorias-e-marcas-para-marketplace/) y [aprobar los anuncios recibidos](https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus/).
 
diff --git a/docs/tutorials/es/adding-a-seller.md b/docs/tutorials/es/adding-a-seller.md
index fa03ef7e4..839877572 100644
--- a/docs/tutorials/es/adding-a-seller.md
+++ b/docs/tutorials/es/adding-a-seller.md
@@ -19,9 +19,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 Para agregar un seller no identificable, también conocido como [seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), es necesario tener este modelo previsto en el contrato con VTEX. Una vez acordado un contrato con el representante de ventas de VTEX responsable de tu _marketplace_, solicita la [adición de una cuenta franquicia](https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) por medio de nuestro Soporte. Todas las cuentas franquicias se crean como un _seller white label_, y no es posible cambiar el tipo de _seller_ después de su creación. 
 
-<div class="alert alert-info">
-Si quieres encontrar nuevos partners para vender en tu marketplace, utiliza  **Encontrar sellers**, que facilita la identificación y contacto entre marketplaces y sellers que operan en el ecosistema VTEX, además de conectores certificados (partners).
-</div> 
+>ℹ️ Si quieres encontrar nuevos partners para vender en tu marketplace, utiliza  **Encontrar sellers**, que facilita la identificación y contacto entre marketplaces y sellers que operan en el ecosistema VTEX, además de conectores certificados (partners). 
 
 1. En tu Admin VTEX, accede a _MARKETPLACE > Gestión_.  
 2. Haz clic en `Agregar seller`.  
@@ -65,9 +63,7 @@ Si quieres encontrar nuevos partners para vender en tu marketplace, utiliza  **E
 - **Cambios y devoluciones:** descripción de la política de cambios y devoluciones previamente acordada entre el _marketplace_ y el _seller_.
 - **Política de privacidad y seguridad:** descripción de la política de seguridad previamente acordada entre el _marketplace_ y el _seller_.
 
-<div class="alert alert-info">
-Con la nueva versión de la página, lanzada el 2022, eliminamos el campo Endpoint del Catálogo porque ya no es necesario para la integración con un nuevo seller. Si es necesario, aún es posible gestionar el campo a través de la API.
-</div>
+>ℹ️ Con la nueva versión de la página, lanzada el 2022, eliminamos el campo Endpoint del Catálogo porque ya no es necesario para la integración con un nuevo seller. Si es necesario, aún es posible gestionar el campo a través de la API.
 
 Después de rellenar los campos y hacer clic en **Guardar**, el _seller_ será agregado al _marketplace_. Para completar la configuración de tu tienda como _marketplace_ también debes [mapear las marcas, categorías y especificaciones del seller](https://help.vtex.com/es/tutorial/mapeando-categorias-e-marcas-para-marketplace/) y [aprobar los anuncios recibidos](https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus/).
 
diff --git a/docs/tutorials/es/adding-an-attachment.md b/docs/tutorials/es/adding-an-attachment.md
index c0989ff5f..9287630eb 100644
--- a/docs/tutorials/es/adding-an-attachment.md
+++ b/docs/tutorials/es/adding-an-attachment.md
@@ -39,9 +39,7 @@ Después de realizar el registro inicial del anexo, es necesario añadir las cla
 3. Haga clic en `Insertar nuevo`. Si lo desea, puede registrar otras claves repitiendo este proceso.
 4. Para finalizar, haga clic en `Guardar`.
 
-<div class="alert alert-warning">
-<p>Es obligatorio completar el campo <strong>Máximo de caracteres</strong>. Si este campo no se completa, el anexo no aparecerá como una opción de selección en el carrito de su cliente.</p>
-</div>
+>⚠️ Es obligatorio completar el campo **Máximo de caracteres**. Si este campo no se completa, el anexo no aparecerá como una opción de selección en el carrito de su cliente.
 
 ## Asociar el anexo a un SKU
 
@@ -56,6 +54,4 @@ Después de crear el anexo de SKU y de configurar las claves y los valores permi
 
 También puede asociar un anexo al SKU [por API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuattachment), si lo desea.
 
-<div class="alert alert-warning">
-<p>VTEX no controla el stock de un anexo. Esta es la función del marketplace o del seller.</p>
-</div>
+>⚠️ VTEX no controla el stock de un anexo. Esta es la función del marketplace o del seller.
diff --git a/docs/tutorials/es/adding-collections-cms.md b/docs/tutorials/es/adding-collections-cms.md
index 609090740..b11ddf352 100644
--- a/docs/tutorials/es/adding-collections-cms.md
+++ b/docs/tutorials/es/adding-collections-cms.md
@@ -27,9 +27,7 @@ Realice el siguiente paso a paso para registrar una nueva colección:
 4. Rellene los campos del formulario de Colección. Para entender mejor el significado de cada campo, acceda a nuestro artículo sobre [cómo rellenar campos de registro de colección](https://help.vtex.com/es/tutorial/rellenar-campos-de-registro-de-colección--7eKL7CFRW3yGKlnDfQetbj).
 5. Haga clic en __Save Product Cluster__.
 
-<div class="alert alert-warning">
-Cuando la cantidad de colecciones creadas supera el límite de veinte, las colecciones excedentes pueden encontrarse en la interfaz a través del campo de búsqueda. La búsqueda en este campo debe realizarse en base al nombre de la colección deseada. 
-</div>
+>⚠️ Cuando la cantidad de colecciones creadas supera el límite de veinte, las colecciones excedentes pueden encontrarse en la interfaz a través del campo de búsqueda. La búsqueda en este campo debe realizarse en base al nombre de la colección deseada.
 
 La elección de los productos que van a hacer parte de una colección se hace a través de la creación de un __grupo__. Para esto, basta con hacer clic en __New Group__ dentro de la colección deseada. 
 
@@ -54,9 +52,7 @@ Siendo:
 
 Por eso, el primer grupo creado para cualquier colección debe ser obligatoriamente del tipo _Inclusive_.
 
-<div class="alert alert-warning">
-Esté siempre atento al tipo de grupo definido en el registro. Al incluir productos en un grupo tipo <i>Exclusive</i>, por ejemplo, estos <strong>no</strong> se incluirán en una colección por causa de la naturaleza de su grupo. 
-</div>
+>⚠️ Esté siempre atento al tipo de grupo definido en el registro. Al incluir productos en un grupo tipo <i>Exclusive</i>, por ejemplo, estos **no** se incluirán en una colección por causa de la naturaleza de su grupo.
 
 ## Selección de productos
 
@@ -103,15 +99,11 @@ En el campo __Find SKUs__, es posible digitar el ID de cuantos SKUs se deseen, e
 
 Para excluir un SKU de la lista, basta con hacer clic en el botón rojo al lado de este.
 
-<div class="alert alert-info">
-Cuando el número de SKUs en la lista supere los 10 ítems, un control de paginación estará disponible.
-</div>
+>ℹ️ Cuando el número de SKUs en la lista supere los 10 ítems, un control de paginación estará disponible.
 
 #### Por plantilla  
 
-<div class="alert alert-info">
-Obtenga el modelo de archivo para la inclusión y exclusión de SKUs de la colección <a href="//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls">aquí</a>.
-</div>
+>ℹ️ Obtenga el modelo de archivo para la inclusión y exclusión de SKUs de la colección [aquí](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls).
 
 #### Inclusión masiva 
 
diff --git a/docs/tutorials/es/additional-shipping-costs.md b/docs/tutorials/es/additional-shipping-costs.md
index f72441610..767e3c5a4 100644
--- a/docs/tutorials/es/additional-shipping-costs.md
+++ b/docs/tutorials/es/additional-shipping-costs.md
@@ -31,10 +31,8 @@ Los valores adicionales pueden configurarse según:
 
 ![adicionais frete ES](https://images.ctfassets.net/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/9aef6304664af38fa0a9c03ed1916f7e/adicionais_frete_ES.svg)
 
-<div class="alert alert-danger">
-Es posible tener todos los adicionales configurados al mismo tiempo para una única tarifa de envío. El cálculo final de la <a href="https://help.vtex.com/es/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">tarifa de envío</a> es la suma de todos los adicionales registrados más la tarifa fija del flete. 
-La tarifa de envío no es el costo final de envío.
-</div>
+>❗ Es posible tener todos los adicionales configurados al mismo tiempo para una única tarifa de envío. El cálculo final de la [tarifa de envío](https://help.vtex.com/es/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM) es la suma de todos los adicionales registrados más la tarifa fija del flete. 
+> La tarifa de envío no es el costo final de envío.
 
 ## Adicional de peso
 
@@ -92,9 +90,7 @@ Adicional de flete: ($10+$0+$9+$5)x10%=$2,4
 Adicionales de flete: ($9+$5+$2,4)=$16,4  
 Tarifa de envío: ($10+$16,4)=$26,4  
 
-<div class="alert alert-danger">
-Es importante recordar que el cálculo del adicional de precio no tiene en cuenta los posibles descuentos y promociones, sino el valor integral del carito. Si el adicional de precio es inferior al adicional de seguro, el adicional de precio no se tiene en cuenta en el cálculo final de la tarifa de envío.
-</div>
+>❗ Es importante recordar que el cálculo del adicional de precio no tiene en cuenta los posibles descuentos y promociones, sino el valor integral del carito. Si el adicional de precio es inferior al adicional de seguro, el adicional de precio no se tiene en cuenta en el cálculo final de la tarifa de envío.
 
 ### Configuración 
 
@@ -128,9 +124,7 @@ Tarifa de envío: ($15+$10,3)=$25,3
 
 El adicional de seguro se configura en la [plantilla de flete](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127), en el campo _MinimumValueInsurance_.
 
-<div class="alert alert-danger">
-Si el adicional de precio es inferior al adicional de seguro, el adicional de precio no se tiene en cuenta en el cálculo final de la tarifa de envío.
-</div>
+>❗ Si el adicional de precio es inferior al adicional de seguro, el adicional de precio no se tiene en cuenta en el cálculo final de la tarifa de envío.
 
 ## Adicional de flete
 
diff --git a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
index 70470127d..b8719b824 100644
--- a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
@@ -51,9 +51,7 @@ Actualmente, VTEX cuenta con un único formato de anuncio: resultados de búsque
 
 7. En la sección **Presupuesto, oferta y cronograma**, haz clic en el botón de editar <i class="fas fa-pencil-alt"></i>.
 8. Define los valores de las ofertas para cada producto. Puedes definir cada valor individualmente.
-	<div class="alert alert-info">
-	La oferta de un producto es el costo por clic (CPC), el valor gastado cuando un usuario hace clic en el anuncio. Más información sobre <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanas">campañas</a> y cómo funciona la <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#priorizacion-de-anuncios">subasta</a>.
-	</div>
+	>ℹ️ La oferta de un producto es el costo por clic (CPC), el valor gastado cuando un usuario hace clic en el anuncio. Más información sobre [campañas](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanas) y cómo funciona la [subasta](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#priorizacion-de-anuncios).
 9. Haz clic en `Siguiente`.
 10. Define el presupuesto diario de la campaña.
 11. Define la duración de la campaña seleccionando la fecha de fin.
diff --git a/docs/tutorials/es/affiliates-program-app.md b/docs/tutorials/es/affiliates-program-app.md
index dd34260f9..ace15483f 100644
--- a/docs/tutorials/es/affiliates-program-app.md
+++ b/docs/tutorials/es/affiliates-program-app.md
@@ -84,9 +84,7 @@ Para crear un nuevo afiliado, haz clic en el botón "Agregar afiliado", rellena
 
 Para buscar un afiliado, escribe en la barra de búsqueda cualquiera de los siguientes datos: _ID de afiliado, nombre, nombre de la tienda, email_ o _teléfono._
 
-<div class="alert alert-warning">
-En la aplicación <b>Affiliates Program</b>, además de que el término afiliado es diferente al <a href="https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0">concepto habitual de afiliado en VTEX</a>, el <code>ID de afiliado</code> tampoco coincide con el código por defecto. En la aplicación, el <code>ID de afiliado</code> es un código alfanumérico que se genera automáticamente cuando creas un nuevo afiliado.
-</div>
+>⚠️ En la aplicación **Affiliates Program**, además de que el término afiliado es diferente al [concepto habitual de afiliado en VTEX](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0), el `ID de afiliado` tampoco coincide con el código por defecto. En la aplicación, el `ID de afiliado` es un código alfanumérico que se genera automáticamente cuando creas un nuevo afiliado.
 
 ### Filtrar afiliados
 
@@ -148,9 +146,7 @@ Puedes filtrar la búsqueda de pedidos por los siguientes criterios:
 
 La aplicación **Affiliates Program** te permite exportar una lista con extensión CSV de los pedidos de los afiliados.
 
-<div class="alert alert-warning">
-Para activar la función de exportación de listas, primero debes configurar las plantillas de email, como se describe en la guía para desarrolladores <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app#email-templates">Affiliates Program app</a>.
-</div>
+>⚠️ Para activar la función de exportación de listas, primero debes configurar las plantillas de email, como se describe en la guía para desarrolladores [Affiliates Program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app#email-templates).
 
 Tras la configuración, para exportar la lista basta con hacer clic en **Exportar** en la página **Gestión de pedidos**. El siguiente mensaje de confirmación deberá aparecer:
 
diff --git a/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
index 99ea9573b..5194dba21 100644
--- a/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/es/amazon-multi-channel-fulfillment-mcf-app.md
@@ -15,9 +15,7 @@ legacySlug: aplicacion-amazon-multi-channel-fulfillment-mcf
 subcategory: 1P1vFnzQ4TQJsBRDoPVKUI
 ---
 
-<div class="alert alert-info">
-La aplicación está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ La aplicación está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 La aplicación Amazon Multi-Channel Fulfillment (MCF) te permite integrar tu negocio con el programa del mismo nombre. Con la integración, los clientes VTEX pueden utilizar la red logística de Amazon en sus propias tiendas. Así, los ítems de venta se almacenan en los centros de distribución de Amazon, y después de cada venta en tu ecommerce, la plataforma VTEX envía los datos del pedido a Amazon para que los separe, empaquete y envíe a los destinatarios.
 
@@ -35,11 +33,9 @@ Antes de la instalación, es necesario:
 * Asegurarte de que los productos de tu tienda cumplen las [políticas de restricción de Amazon](https://sellercentral.amazon.com/gp/help/external/200164330).
 * Asegurarte de que tu tienda está situada en países donde la MCF está disponible. Países como Estados Unidos, Australia, México, Alemania y Canadá ya cuentan con la MCF de Amazon. Consulta la lista actualizada de países [en esta página de Amazon](https://sell.amazon.com/fulfillment-by-amazon/fba-multi-channel.html).
 
-<div class="alert alert-danger">
-Cuando se instala la aplicación, la plataforma VTEX trata la integración como una tienda externa de Amazon y utiliza la integración de tipo marketplace con Amazon.
-<p>La aplicación debe instalarse en todas las cuentas VTEX en las que se desee utilizar la funcionalidad. 
-<p>Recomendamos utilizar el Checkout V6.
-</div>
+>❗ Cuando se instala la aplicación, la plataforma VTEX trata la integración como una tienda externa de Amazon y utiliza la integración de tipo marketplace con Amazon.
+> <p>La aplicación debe instalarse en todas las cuentas VTEX en las que se desee utilizar la funcionalidad. 
+> <p>Recomendamos utilizar el Checkout V6.
 
 ## Instalación, configuración y acceso:
 
@@ -83,9 +79,7 @@ Para realizar esta configuración, accede al Admin y sigue los pasos a continuac
 
 En los pasos 8 y 10, la clave que hay que rellenar es la clave de geolocalización de Google. Consulta [cómo generar una clave en la guía para desarrolladores de Google.](https://developers.google.com/maps/documentation/geocoding/overview) 
 
-<div class="alert alert-info">
-Si tienes dudas sobre la clave de geolocalización de Google, consulta en detalle cómo utiliza esta configuración la plataforma VTEX en los artículos <a href="https://help.vtex.com/es/tutorial/geolocalizacion-en-el-checkout--tutorials_4345"> Configurar la geolocalización en el checkout</a> y <a href="https://help.vtex.com/es/tutorial/gestionar-geolocalizacion--tutorials_138">Registrar la geolocalización</a>.
-</div>
+>ℹ️ Si tienes dudas sobre la clave de geolocalización de Google, consulta en detalle cómo utiliza esta configuración la plataforma VTEX en los artículos [ Configurar la geolocalización en el checkout](https://help.vtex.com/es/tutorial/geolocalizacion-en-el-checkout--tutorials_4345) y [Registrar la geolocalización](https://help.vtex.com/es/tutorial/gestionar-geolocalizacion--tutorials_138).
 
 ### Instalación de la aplicación
 
@@ -106,9 +100,7 @@ Para instalar la aplicación, accede a VTEX App Store:
     * **ERP Hook URL:** es la dirección del ERP que incluirá las facturas de los pedidos (en el caso de que el campo **Automatic Invoice** esté configurado como Deactivate).
     * **Amazon Marketplace:** es el país en el que utilizarás Amazon MCF.
 
-<div class="alert alert-warning">
-Las configuraciones realizadas en el campo Automatic Invoice se aplicarán a todos los pedidos.
-</div>
+>⚠️ Las configuraciones realizadas en el campo Automatic Invoice se aplicarán a todos los pedidos.
 
 ![MCF](https://images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/604c465dd3344b9cc04b722d03cb5005/Amazon_MCF_EN.PNG)
 
diff --git a/docs/tutorials/es/analytics.md b/docs/tutorials/es/analytics.md
index 261b5b2f4..7a6e6f232 100644
--- a/docs/tutorials/es/analytics.md
+++ b/docs/tutorials/es/analytics.md
@@ -41,9 +41,7 @@ Los datos que componen el informe se actualizan cada 4 horas y contienen la sigu
 *   **Pedidos**: número de pedidos realizados desde la búsqueda. Para calcular esta métrica, consideramos que la búsqueda genera un pedido cada vez que, después buscar un término, el cliente hace clic en algún producto que aparece en los resultados y luego compra cualquier producto (no necesariamente el producto en el que hizo clic). 
 *   **Ventas**: ingresos totales generados por los pedidos realizados a partir de la búsqueda. El cálculo sigue la misma lógica que la métrica de **Pedidos**, la diferencia es que el resultado refleja los ingresos en lugar del número de pedidos.
 
-<div class="alert alert-info">
-  <p>Los datos mostrados en el informe se limitan a los 10 mil términos más buscados. Si deseas obtener los datos de búsqueda completos de tu tienda, tienes que <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacion">exportar el informe</a>.</p>
-</div>
+>ℹ️ Los datos mostrados en el informe se limitan a los 10 mil términos más buscados. Si deseas obtener los datos de búsqueda completos de tu tienda, tienes que [exportar el informe](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacion).
 
 Cuando se elige [exportar un informe](#exportacion), también existe la posibilidad de generarlo con las __métricas de embudo__. Si se selecciona esa opción, se agregarán 4 nuevas columnas al archivo:
 
diff --git a/docs/tutorials/es/analyze-suiteshare.md b/docs/tutorials/es/analyze-suiteshare.md
index 0ebcdb901..832a1c678 100644
--- a/docs/tutorials/es/analyze-suiteshare.md
+++ b/docs/tutorials/es/analyze-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: analizar
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/anapro-suiteshare.md b/docs/tutorials/es/anapro-suiteshare.md
index 9eac85fde..03920fda4 100644
--- a/docs/tutorials/es/anapro-suiteshare.md
+++ b/docs/tutorials/es/anapro-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: anapro
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/antifraud-provider.md b/docs/tutorials/es/antifraud-provider.md
index cc3f16499..b5817f64b 100644
--- a/docs/tutorials/es/antifraud-provider.md
+++ b/docs/tutorials/es/antifraud-provider.md
@@ -142,9 +142,7 @@ Estas llaves deben estar disponibles por usted y van a servir para identificar l
 ## Configuración del documento del titular de la tarjeta
 Durante el proceso de revisión de las transacciones de pago, algunos proveedores antifraude pueden optar por no utilizar información adicional como: la identificación personal del titular de la tarjeta. En estos casos, el administrador de la tienda tiene autonomía para decidir si solicita o no esta información a su cliente durante el proceso de checkout.
 
-<div class="alert alert-warning">
-  La opción de configuración <b>Campo de documento del titular de la tarjeta</b> solo estará disponible para el administrador de la tienda, si el provedor antifraude declara el campo del documento del titular de la tarjeta (<code>cardholderDocument</code>) como <code>opcional</code> em su <a href="https://developers.vtex.com/vtex-rest-api/reference/manifest">manifesto</a>. Mas información en <a href="https://developers.vtex.com/vtex-rest-api/docs/cardholder-document-configuration">Cardholder Document Configuration</a>.
-  </div>
+>⚠️ La opción de configuración **Campo de documento del titular de la tarjeta** solo estará disponible para el administrador de la tienda, si el provedor antifraude declara el campo del documento del titular de la tarjeta (`cardholderDocument`) como `opcional` em su [manifesto](https://developers.vtex.com/vtex-rest-api/reference/manifest). Mas información en [Cardholder Document Configuration](https://developers.vtex.com/vtex-rest-api/docs/cardholder-document-configuration).
 
 Para configurar la visualización del campo del documento del titular de la tarjeta, siga los siguientes pasos:
 
diff --git a/docs/tutorials/es/application-keys.md b/docs/tutorials/es/application-keys.md
index 14ab791b9..d85f7faba 100644
--- a/docs/tutorials/es/application-keys.md
+++ b/docs/tutorials/es/application-keys.md
@@ -33,9 +33,7 @@ Las claves de aplicación externas son credenciales generadas y administradas po
 
 ## Gestionar claves de aplicación
 
-<div class="alert alert-warning">
-  <p>Se requiere un <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">rol</a> con el recurso <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3"></a> <strong>Save user</strong> para gestionar usuarios y claves de aplicación. El rol predeterminado para este fin es <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, pero también es posible <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol">crear un rol personalizado</a> con este recurso.</p>
-</div>
+>⚠️ Se requiere un [rol](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) con el recurso [](https://help.vtex.com/es/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) **Save user** para gestionar usuarios y claves de aplicación. El rol predeterminado para este fin es [User Administrator - RESTRICTED](https://help.vtex.com/es/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted), pero también es posible [crear un rol personalizado](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol) con este recurso.
 
 En la página **Claves de aplicación** puedes gestionar las claves de aplicación [internas](#claves-de-aplicacion-internas) y [externas](#claves-de-aplicacion-externas) que tienen acceso a tu cuenta, incluyendo:
 
@@ -76,9 +74,7 @@ Para crear claves de aplicación internas en tu cuenta sigue los pasos a continu
 4. Haz clic en el botón `Agregar rol`.
 5. Haz clic en <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> para copiar el **Token de aplicación**. _Este secreto se mostrará una vez.  Guárdalo en un lugar seguro._
 
-<div class="alert alert-warning">
-  <p>Protege tus pares de claves y tokens de aplicación como lo harías con otras credenciales, como nombres de usuario y contraseñas. Si sospechas que una clave de aplicación está comprometida, debes desactivarla inmediatamente en tu cuenta. Para más detalles, consulta la sección <a href="#ativar-ou-desativar-chaves-de-aplicacao">Activar o desactivar claves de aplicación</a> de este artículo.</p>
-</div>
+>⚠️ Protege tus pares de claves y tokens de aplicación como lo harías con otras credenciales, como nombres de usuario y contraseñas. Si sospechas que una clave de aplicación está comprometida, debes desactivarla inmediatamente en tu cuenta. Para más detalles, consulta la sección [Activar o desactivar claves de aplicación](#ativar-ou-desativar-chaves-de-aplicacao) de este artículo.
 
 ## Agregar claves de aplicación externas
 
@@ -94,9 +90,7 @@ Para agregar claves de aplicación de terceros sigue los pasos a continuación:
 
 Para que una clave de aplicación pueda realizar requests de API a tu cuenta, debe estar activa y tener [roles](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) que especifiquen los recursos de la cuenta a los que puede acceder. 
 
-<div class="alert alert-danger">
-<p>El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas al filtrarse las credenciales de inicio de sesión.</p>
-</div>
+>❗ El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas al filtrarse las credenciales de inicio de sesión.
 
 Las claves de aplicación se crean, de manera predeterminada, sin permisos para acceder a ningún recurso de la cuenta.
 
@@ -122,17 +116,13 @@ Consulta a continuación los campos visibles en la página **Claves de aplicaci
 - **Cuenta:** cuenta VTEX responsable de gestionar la clave de aplicación.
 - **Status:** status actual de la clave de aplicación, que puede ser activa o inactiva.
 
-<div class="alert alert-info">
-  <p>Observa que el campo <strong>Etiqueta</strong> no se muestra en la página <strong>Claves de aplicación</strong>. Para ver la descripción de la finalidad de una clave de aplicación interna, utiliza el valor de la<strong>Clave</strong> para encontrarla en la página <strong>Mis claves</strong>. No es posible agregar etiquetas a claves de aplicación externas.</p>
-</div>
+>ℹ️ Observa que el campo **Etiqueta** no se muestra en la página **Claves de aplicación**. Para ver la descripción de la finalidad de una clave de aplicación interna, utiliza el valor de la**Clave** para encontrarla en la página **Mis claves**. No es posible agregar etiquetas a claves de aplicación externas.
 
 ## Activar y desactivar claves de aplicación
 
 Si una clave de aplicación que tiene acceso a tu cuenta se ve comprometida, debes cancelar su acceso inmediatamente. Si cometes un error puedes volver a activarla para restablecer la integración afectada. La forma de hacerlo dependerá del [tipo de clave de aplicación](#tipos-de-clave-de-aplicacion).
 
-<div class="alert alert-warning">
-  <p>Vuelve a activar una clave de aplicación solamente si estás seguro de que no ha sido comprometida. Cualquier usuario con el token de aplicación asociado recuperará el acceso privilegiado a tu cuenta.</p>
-</div>
+>⚠️ Vuelve a activar una clave de aplicación solamente si estás seguro de que no ha sido comprometida. Cualquier usuario con el token de aplicación asociado recuperará el acceso privilegiado a tu cuenta.
 
 ### Desactivar clave de aplicación interna
 
diff --git a/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
index 66fae1618..38afe4dab 100644
--- a/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/es/approving-payment-of-the-bank-payment-slip.md
@@ -29,13 +29,9 @@ Se puede hacer esa aprobación manualmente por el OMS de forma simple, conforme
 
 **Después de la aprobación del pago, el pedido entrará en el flujo normal de compra.**
 
-<div class="alert alert-info">
-En el módulo de Gestión de la cuenta, el usuario debe tener un perfil de acceso que incluya el permiso <code>Notify payment</code> para poder aprobar los pagos.
-</div>
+>ℹ️ En el módulo de Gestión de la cuenta, el usuario debe tener un perfil de acceso que incluya el permiso `Notify payment` para poder aprobar los pagos.
 
 Para aprobar pagos por API, vea la [documentación sobre la solicitud de notificación de pago](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/payments/-paymentId-/payment-notification).
 
-<div class="alert alert-warning">
-Como las <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integraciones con los ERP</a> se rigen por el <a href="https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#">flujo de pedidos</a>, la aprobación manual de un pago continuará la integración de este pedido con el back office de la tienda normalmente. Por lo tanto, se recomienda precaución al aprobar los pagos manualmente, para garantizar que se reciba cada pedido procesado y enviado.
-</div>
+>⚠️ Como las [integraciones con los ERP](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) se rigen por el [flujo de pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#), la aprobación manual de un pago continuará la integración de este pedido con el back office de la tienda normalmente. Por lo tanto, se recomienda precaución al aprobar los pagos manualmente, para garantizar que se reciba cada pedido procesado y enviado.
 
diff --git a/docs/tutorials/es/apps-overview.md b/docs/tutorials/es/apps-overview.md
index b92ee8f46..a8ed64fd9 100644
--- a/docs/tutorials/es/apps-overview.md
+++ b/docs/tutorials/es/apps-overview.md
@@ -28,9 +28,7 @@ Las apps de VTEX extienden las funcionalidades de la plataforma VTEX y ayudan a
 
 Nuestra solución _plug and play_ permite a los desarrolladores de terceros crear aplicaciones para el ecosistema VTEX de múltiples maneras. En la [VTEX App Store](https://apps.vtex.com/) pueden descargarse tanto aplicaciones _first-party_ como _third-party_, y estas pueden ser gratuitas o de pago. 
 
-<div class="alert alert-info">
-  Si es una persona desarrolladora, consulte el <a href = "https://developers.vtex.com">Developer Portal</a> para obtener más información sobre cómo desarrollar sus propias apps en VTEX.
-  </div> 
+>ℹ️ Si es una persona desarrolladora, consulte el <a href = "https://developers.vtex.com">Developer Portal</a> para obtener más información sobre cómo desarrollar sus propias apps en VTEX. 
 
 El menú de Apps permite a los comerciantes descargar nuevas aplicaciones directamente desde la App Store y gestionar las aplicaciones instaladas sin salir del VTEX Admin. Ten en cuenta que el menú de Apps es flexible y puede incluir secciones personalizadas relacionadas con las aplicaciones instaladas en tu cuenta. 
 
diff --git a/docs/tutorials/es/assembly-options-app.md b/docs/tutorials/es/assembly-options-app.md
index bff13cdd0..cfc71d1c0 100644
--- a/docs/tutorials/es/assembly-options-app.md
+++ b/docs/tutorials/es/assembly-options-app.md
@@ -15,9 +15,7 @@ legacySlug: aplicacion-assembly-options
 subcategory: 3xpuy7xGlzKKg6vxqiExZ2
 ---
 
-<div class="alert alert-warning">
-<p>Esta aplicación solo está disponible para las tiendas que usan<a href="https://vtex.com/br-pt/store-framework/"> VTEX IO</a>. Antes de continuar, debes <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer">instalar y configurar Product Customizer</a> en tu tienda.</p>
-</div>
+>⚠️ Esta aplicación solo está disponible para las tiendas que usan[ VTEX IO](https://vtex.com/br-pt/store-framework/). Antes de continuar, debes [instalar y configurar Product Customizer](https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer) en tu tienda.
 
 En VTEX, puedes tener opciones de personalización de productos disponibles cuando usas [Assembly Options](https://help.vtex.com/es/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH) (opciones de ensamblaje). Esta solución consiste en crear [anexos](https://help.vtex.com/es/tutorial/que-es-un-anexo--aGICk0RVbqKg6GYmQcWUm) para escenarios complejos en los cuales es necesario gestionar distintas combinaciones de productos, cantidades, ítems adicionales y costos.
 
@@ -27,9 +25,7 @@ La [aplicación Assembly Options](https://apps.vtex.com/vtex-admin-assembly-opti
 
 La aplicación puede instalarse de forma gratuita a través de [VTEX App Store](https://apps.vtex.com/vtex-admin-assembly-options/p) o a través de [VTEX IO CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference), siguiendo los pasos de la [guía para desarrolladores Assembly Options](https://developers.vtex.com/vtex-developer-docs/docs/assembly-options-app).
 
-<div class="alert alert-warning">
-<p>Cuando la aplicación Assembly Options se instala en una <a href="https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w">cuenta de seller</a>, los clientes de tu tienda pueden ver las opciones de personalización del producto en el <em>checkout</em>. Para que las opciones se muestren en la página del producto, debes instalar la aplicación en una <a href="https://help.vtex.com/es/tutorial/que-es-un-marketplace--680lLJTnmEAmekcC0MIea8">cuenta de marketplace</a>.</p>
-</div>
+>⚠️ Cuando la aplicación Assembly Options se instala en una [cuenta de seller](https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w), los clientes de tu tienda pueden ver las opciones de personalización del producto en el *checkout*. Para que las opciones se muestren en la página del producto, debes instalar la aplicación en una [cuenta de marketplace](https://help.vtex.com/es/tutorial/que-es-un-marketplace--680lLJTnmEAmekcC0MIea8).
 
 Una vez instalada, la página **Catálogo > Opciones de ensamblaje** estará disponible en el Admin VTEX. A continuación, puedes ver las funcionalidades que estarán disponibles tras la instalación.
 
@@ -83,9 +79,7 @@ La página **Productos > Opciones de ensamblaje > Nuevas opciones de ensamblaje*
 
 Al guardar la opción de ensamblaje, se creará un anexo automáticamente en **Catálogo > Anexos**, con el prefijo `vtex.assembly-option.` en el nombre de la opción de ensamblaje creada. Ejemplo: `vtex.assembly-option.Ingredientes`.
 
-<div class="alert alert-warning">
-<p>Para que las opciones de personalización registradas en la opción de ensamblaje aparezcan en el <em>storefront</em>, debes asociar el anexo creado a un SKU en <strong>Catálogo > Productos y SKU > Configuraciones avanzadas > Anexos</strong>. Para hacerlo, sigue los pasos descriptos en <a href="https://help.vtex.com/es/tutorial/registrar-un-anexo--7zHMUpuoQE4cAskqEUWScU#asociar-el-anexo-a-un-sku">Asociar el anexo a un SKU</a>.</p>
-</div>
+>⚠️ Para que las opciones de personalización registradas en la opción de ensamblaje aparezcan en el *storefront*, debes asociar el anexo creado a un SKU en **Catálogo > Productos y SKU > Configuraciones avanzadas > Anexos**. Para hacerlo, sigue los pasos descriptos en [Asociar el anexo a un SKU](https://help.vtex.com/es/tutorial/registrar-un-anexo--7zHMUpuoQE4cAskqEUWScU#asociar-el-anexo-a-un-sku).
 
 ## Más información
 
diff --git a/docs/tutorials/es/assembly-options.md b/docs/tutorials/es/assembly-options.md
index 600d5d101..30d5baded 100644
--- a/docs/tutorials/es/assembly-options.md
+++ b/docs/tutorials/es/assembly-options.md
@@ -15,9 +15,7 @@ legacySlug: assembly-options-es
 subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 ---
 
-<div class="alert alert-warning">
-  <p>Esta funcionalidad solo está disponible para las tiendas desarrolladas con <a href="https://vtex.com/es-es/store-framework/">VTEX IO</a>. Antes de seguir, debes <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer">instalar y configurar el Product Customizer</a> en tu tienda.</p>
-</div>
+>⚠️ Esta funcionalidad solo está disponible para las tiendas desarrolladas con [VTEX IO](https://vtex.com/es-es/store-framework/). Antes de seguir, debes [instalar y configurar el Product Customizer](https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer) en tu tienda.
 
 Una assembly option es un [anexo](https://help.vtex.com/es/tutorial/que-es-un-anexo--aGICk0RVbqKg6GYmQcWUm) para escenarios complejos, como la personalización de productos en las que es necesario controlar diferentes combinaciones de productos, la cantidad, ítems adicionales, costes y la gestión de stock.
 
@@ -33,9 +31,7 @@ En este artículo, explicamos cómo empezar a utilizar las opciones de ensamblaj
 
 Hay dos formas de implementar las opciones de ensamblaje: utilizando la [aplicación Assembly Options](#aplicacion-assembly-options) o la interfaz nativa de [Campos personalizados](#campos-personalizados) del __Catálogo__.
 
-<div class="alert alert-warning">
-  <p>Al implementar las opciones de ensamblaje en una <a href="https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w">cuenta de seller</a>, las opciones de personalización del producto se mostrarán a los clientes de tu tienda en el checkout. Para que las opciones se muestren en la página del producto, debes implementar la funcionalidad en una <a href="https://help.vtex.com/es/tutorial/que-es-un-marketplace--680lLJTnmEAmekcC0MIea8">cuenta de marketplace</a>.</p>
-</div>
+>⚠️ Al implementar las opciones de ensamblaje en una [cuenta de seller](https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w), las opciones de personalización del producto se mostrarán a los clientes de tu tienda en el checkout. Para que las opciones se muestren en la página del producto, debes implementar la funcionalidad en una [cuenta de marketplace](https://help.vtex.com/es/tutorial/que-es-un-marketplace--680lLJTnmEAmekcC0MIea8).
 
 ### Aplicación Assembly Options
 
diff --git a/docs/tutorials/es/audit.md b/docs/tutorials/es/audit.md
index c635d9bb8..0ace769e5 100644
--- a/docs/tutorials/es/audit.md
+++ b/docs/tutorials/es/audit.md
@@ -22,9 +22,7 @@ Para acceder a la página de Audit en el Admin VTEX, ve a **Apps > Apps instalad
 * [Consultar eventos en Audit](#consultar-eventos-en-audit)
 * [Verificar las últimas consultas realizadas en Audit](#verificar-las-ultimas-consultas-realizadas-en-audit)
 
-<div class="alert alert-info">
-  <p>Para visualizar los eventos de Audit, debe tener un <a href="https://help.vtex.com/es/tutorial/perfis-de-acceso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acceso</a> asociado al <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <em>Insights Metrics</em>.</p>
-</div>
+>ℹ️ Para visualizar los eventos de Audit, debe tener un [perfil de acceso](https://help.vtex.com/es/tutorial/perfis-de-acceso--7HKK5Uau2H6wxE1rH5oRbc) asociado al [recurso](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) *Insights Metrics*.
 
 ![audit-ui-es](https://images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/7c0a482122fe0605d75492f02b44f20d/audit-ui-es__1_.png)
 
diff --git a/docs/tutorials/es/authentication-page.md b/docs/tutorials/es/authentication-page.md
index 6694bb07d..c329f3af5 100644
--- a/docs/tutorials/es/authentication-page.md
+++ b/docs/tutorials/es/authentication-page.md
@@ -35,9 +35,7 @@ Actualmente, hay cuatro formas de iniciar sesión:
 | Facebook                  | Se puede activar | No disponible           |
 | Google                    | Se puede activar | Se puede seleccionar    |
 
-<div class="alert alert-info">
-Al menos una de las cuatro formas de inicio de sesión debe estar habilitada para la tienda virtual.
-</div>
+>ℹ️ Al menos una de las cuatro formas de inicio de sesión debe estar habilitada para la tienda virtual.
 
 ## Tienda virtual
 
diff --git a/docs/tutorials/es/authentication-with-user-and-password-on-the-rest-interface.md b/docs/tutorials/es/authentication-with-user-and-password-on-the-rest-interface.md
index e0610c46e..594feb3e0 100644
--- a/docs/tutorials/es/authentication-with-user-and-password-on-the-rest-interface.md
+++ b/docs/tutorials/es/authentication-with-user-and-password-on-the-rest-interface.md
@@ -15,6 +15,4 @@ legacySlug: autenticandose-con-usuario-y-contrasena-en-la-interfaz-rest
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-info">
-Este artículo ha sido descontinuado. Para autenticarse e integrarse con las APIs de VTEX, accede a nuestro artículo <a href="http://help.vtex.com/es/tutorial/claves-de-aplicacion">Claves de aplicación</a>.
-</div>
+>ℹ️ Este artículo ha sido descontinuado. Para autenticarse e integrarse con las APIs de VTEX, accede a nuestro artículo [Claves de aplicación](http://help.vtex.com/es/tutorial/claves-de-aplicacion).
diff --git a/docs/tutorials/es/authentication.md b/docs/tutorials/es/authentication.md
index e6b5a4a73..9396cea23 100644
--- a/docs/tutorials/es/authentication.md
+++ b/docs/tutorials/es/authentication.md
@@ -35,13 +35,9 @@ Es necesario configurar el método de autenticación que se ofrecerá en cada co
 | Google | El usuario inicia sesión utilizando su cuenta de Google. Consulta la guía [Configurar inicio de sesión con Facebook y Google](https://help.vtex.com/es/tutorial/configurar-login-com-facebook-e-google--tutorials_513) para más detalles. | Se puede activar | Se puede activar |
 | Integración con otros proveedores de identidad | El usuario puede iniciar sesión utilizando su cuenta de otros proveedores de identidad externos a partir de una integración. Consulta la guía para desarrolladores [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) para obtener más detalles. | Se puede activar utilizando el protocolo OAuth.  Consulta la guía para desarrolladores [Webstore (OAuth 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) para obtener más detalles. | Se puede activar utilizando o protocolo SAML. Consulta la guía para desarrolladores [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) para obtener más detalles. |
 
-<div class="alert alert-info">
-  <p>Al menos una de las opciones de inicio de sesión de la tabla anterior debe estar activa en la tienda virtual.</p>
-</div>
+>ℹ️ Al menos una de las opciones de inicio de sesión de la tabla anterior debe estar activa en la tienda virtual.
 
-<div class="alert alert-warning">
-  <p>Para acceder al Admin VTEX es necesario tener un <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512">usuario</a> administrativo registrado. Los <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">roles</a> relacionados con el usuario y los permisos propios de dicho rol determinan los <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recursos</a> que ese usuario puede utilizar en el Admin.</p>
-</div>
+>⚠️ Para acceder al Admin VTEX es necesario tener un [usuario](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512) administrativo registrado. Los [roles](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) relacionados con el usuario y los permisos propios de dicho rol determinan los [recursos](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) que ese usuario puede utilizar en el Admin.
 
 ### Activar formas de inicio de sesión
 
diff --git a/docs/tutorials/es/bank-reconciliations.md b/docs/tutorials/es/bank-reconciliations.md
index e63f6c69e..70e69697d 100644
--- a/docs/tutorials/es/bank-reconciliations.md
+++ b/docs/tutorials/es/bank-reconciliations.md
@@ -21,9 +21,7 @@ El flujo completo es: compra acordada con boleto en el sitio web &gt; pedido en
 
 Conforme explicado en el FAQ [¿Cuánto tiempo lleva para la cancelación de un pedido de boleto sin pago?](/hc/es-419/articles/215033318 "¿Cuánto tiempo lleva para la cancelación de un pedido de boleto sin pago?"), existe un plazo para la cancelación del pedido, caso este no sea notificado como pagado en el status de Pago Aprobado (ya sea manualmente en el OMS el por conciliación). En ese caso, el pedido permanecerá en el status de Pago Pendiente hasta que sea cancelado.
 
-<div class="alert alert-warning">
-Los procedimientos de este artículo no se aplican a las integraciones que realizan la conciliación bancaria de forma automática.
-</div>
+>⚠️ Los procedimientos de este artículo no se aplican a las integraciones que realizan la conciliación bancaria de forma automática.
 
 ## Cómo hacer el upload
 
diff --git a/docs/tutorials/es/become-a-certified-connector-partner.md b/docs/tutorials/es/become-a-certified-connector-partner.md
index f9d53db90..f5947631d 100644
--- a/docs/tutorials/es/become-a-certified-connector-partner.md
+++ b/docs/tutorials/es/become-a-certified-connector-partner.md
@@ -17,9 +17,7 @@ subcategory: 6riYYNZCpO8wyksi8Ksgyq
 
 El ecosistema VTEX ofrece numerosas oportunidades de crecimiento. Con la intención de ampliar su red de colaboración, VTEX ha desarrollado un plan comercial para _marketplaces_ externos que quieran convertirse en _partners_. 
 
-<div class="alert alert-info">
-Al formar parte de este plan comercial, el <i/>marketplace</i> obtiene una certificación y se convierte en un conector certificado. Sepa más en <a href="https://vtex.com/ar-es/partner/">plan comercial</a>.
-</div>
+>ℹ️ Al formar parte de este plan comercial, el <i/>marketplace</i> obtiene una certificación y se convierte en un conector certificado. Sepa más en [plan comercial](https://vtex.com/ar-es/partner/).
 
 Además de proporcionar un conjunto de API e instrucciones para facilitar el proceso de integración con _partners_, uno de nuestros equipos también hace un seguimiento del desarrollo y la homologación del conector. Es decir, VTEX verifica si las funcionalidades se están utilizando adecuadamente para que la integración se produzca correctamente.
 
diff --git a/docs/tutorials/es/best-practices-against-virtual-attacks.md b/docs/tutorials/es/best-practices-against-virtual-attacks.md
index fde43b901..6992ef0d4 100644
--- a/docs/tutorials/es/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/es/best-practices-against-virtual-attacks.md
@@ -32,9 +32,7 @@ Los sistemas de antifraude se especializan en analizar compras de tiendas online
 
 Aprende más sobre [sistemas antifraude](https://help.vtex.com/es/tutorial/what-is-anti-fraud) y cómo utilizarlos en VTEX.
 
-<div class="alert alert-warning">
-Para mayor seguridad, configura tu antifraude en todos los medios de pago disponibles en la tienda.
-</div>
+>⚠️ Para mayor seguridad, configura tu antifraude en todos los medios de pago disponibles en la tienda.
 
 ## Protección contra ataques a las transaciones
 
diff --git a/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md b/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md
index 392cac69d..bb61f3a55 100644
--- a/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md
+++ b/docs/tutorials/es/best-practices-for-accessing-the-store-without-www.md
@@ -68,6 +68,4 @@ Algunos proveedores de DNS, como [Cloudflare](https://www.cloudflare.com/pt-br/)
 
 Por lo tanto, si deseas utilizar un dominio puro con una CDN en una configuración específica, la primera etapa es comprobar si tu proveedor de DNS soporta CNAME Flattening. En caso afirmativo, puedes configurar el dominio puro de esa manera.
 
-<div class="alert alert-warning">
-  <p>Cuando se utiliza la solución DNS Flattening, se comportará de la misma forma que un <a href="https://help.vtex.com/es/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir">proxy inverso</a>. En este caso, se debe configurar una entrada de verificación TXT.</p>
-</div>
+>⚠️ Cuando se utiliza la solución DNS Flattening, se comportará de la misma forma que un [proxy inverso](https://help.vtex.com/es/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir). En este caso, se debe configurar una entrada de verificación TXT.
diff --git a/docs/tutorials/es/billing-module-overview.md b/docs/tutorials/es/billing-module-overview.md
index 5d6426a91..62ea552f1 100644
--- a/docs/tutorials/es/billing-module-overview.md
+++ b/docs/tutorials/es/billing-module-overview.md
@@ -19,9 +19,7 @@ subcategory:
 
 Para acceder a esta sección, haz clic en tu **avatar de perfil**, que se puede identificar por la primera letra de tu dirección de email, y luego haz clic en **Facturación**. Selecciona la pestaña que deseas visitar, como **Contratos, Facturas, Datos de registro y Contactos de facturación**.
 
-<div class="alert alert-info">            
-Solo los usuarios con perfil de acceso <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> o con recursos de <a href="https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> vinculadas a su Perfil de acceso tendrán acceso a esta sección del VTEX Admin.         
-</div>            
+>ℹ️ Solo los usuarios con perfil de acceso [Finance](https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance), [Finance Full Access](https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access) o con recursos de [Billing](https://help.vtex.com/es/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy) vinculadas a su Perfil de acceso tendrán acceso a esta sección del VTEX Admin.            
 
 ![Admin v4 Faturas menu ES](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/369081b189fa73fa6f87aa849e21ec58/Admin_v4_Faturas_menu_ES.jpg)
 
diff --git a/docs/tutorials/es/bitrix24.md b/docs/tutorials/es/bitrix24.md
index 9c072d67b..45438c694 100644
--- a/docs/tutorials/es/bitrix24.md
+++ b/docs/tutorials/es/bitrix24.md
@@ -15,6 +15,4 @@ legacySlug: bitrix24
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/black-friday-checklist.md b/docs/tutorials/es/black-friday-checklist.md
index f80b2a370..a18d8a77c 100644
--- a/docs/tutorials/es/black-friday-checklist.md
+++ b/docs/tutorials/es/black-friday-checklist.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-11-07-at-03-53-51
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/black-week.md b/docs/tutorials/es/black-week.md
index 4c36b6188..82a580054 100644
--- a/docs/tutorials/es/black-week.md
+++ b/docs/tutorials/es/black-week.md
@@ -15,6 +15,4 @@ legacySlug: black-week
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class="alert alert-warning">
-  Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
-  </div>
+>⚠️ Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
diff --git a/docs/tutorials/es/brand-registration-fields.md b/docs/tutorials/es/brand-registration-fields.md
index 55e3a819f..61d2e2afa 100644
--- a/docs/tutorials/es/brand-registration-fields.md
+++ b/docs/tutorials/es/brand-registration-fields.md
@@ -19,15 +19,16 @@ Para entender mejor el significado de los campos de registro de Marca, vea a con
 
 - __Nombre__: nombre de la marca que desea registrar para identificación en un producto. Este campo es obligatorio y debe respetar el límite de 150 caracteres.
 
-<div class="alert alert-danger">
-  <p>Al rellenar el <b>Nombre</b> de la marca, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Al rellenar el **Nombre** de la marca, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 - __Palabras Sustitutas__: términos alternativos que llevan a la marca registrada. El objetivo es facilitarle al usuario encontrar la marca, incluso si lo escribe de diferentes formas. Normalmente estas palabras son diferencias o errores ortográficos y/o formas genéricas y extranjeras de denominar a la marca.   
 
diff --git a/docs/tutorials/es/call-to-action-suiteshare.md b/docs/tutorials/es/call-to-action-suiteshare.md
index fc88754a4..c5255e5e1 100644
--- a/docs/tutorials/es/call-to-action-suiteshare.md
+++ b/docs/tutorials/es/call-to-action-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: call-to-action
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/campaign-audiences-list.md b/docs/tutorials/es/campaign-audiences-list.md
index 074c5a63f..eef03313e 100644
--- a/docs/tutorials/es/campaign-audiences-list.md
+++ b/docs/tutorials/es/campaign-audiences-list.md
@@ -31,9 +31,7 @@ Desde esta página, puedes realizar las acciones a continuación:
 
 Para crear una audiencia de campaña, debes dirigirte a *Promociones > Audiencia de campañas* y hacer clic en el botón `Nueva audiencia de campaña` y seguir los pasos que se describen en el artículo [Crear audiencia de campaña](https://help.vtex.com/es/tutorial/crear-audiencia-de-campanas--6cnuDZJzIkIeocewAQQK4K).
 
-<div class="alert alert-warning">
-  <p>Luego de crear una audiencia de campaña, debes asociarla a una <a href="https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume">Promoción de campaña</a> para que entre en efecto.</p>
-</div>
+>⚠️ Luego de crear una audiencia de campaña, debes asociarla a una [Promoción de campaña](https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume) para que entre en efecto.
 
 ### Ver audiencias de campaña
 
diff --git a/docs/tutorials/es/campaign-promotion.md b/docs/tutorials/es/campaign-promotion.md
index 2591f53b2..37c4065cf 100644
--- a/docs/tutorials/es/campaign-promotion.md
+++ b/docs/tutorials/es/campaign-promotion.md
@@ -26,9 +26,7 @@ Antes de crear una campaña de promoción, debe crear un público de campaña pa
 
 Ejemplo: si configura una [audiencia de campaña](https://help.vtex.com/es/tutorial/Crear-audiencia-de-campanas--6cnuDZJzIkIeocewAQQK4K) cuyo público objetivo son los clientes que ponen el «producto A» en el carrito, en la promoción de la campaña puede configurar que este público reciba un descuento en el «producto B».
 
-<div class="alert alert-info">
-  <p>Los públicos de las campañas y sus promociones solo son válidos para la cuenta principal de la tienda. Las cuentas de <i>sellers</i> no tienen esta opción. Si se crean en una cuenta de <i>seller</i>, el público de campaña o la promoción de campaña no se activarán.</p>
-</div>
+>ℹ️ Los públicos de las campañas y sus promociones solo son válidos para la cuenta principal de la tienda. Las cuentas de <i>sellers</i> no tienen esta opción. Si se crean en una cuenta de <i>seller</i>, el público de campaña o la promoción de campaña no se activarán.
 
 Después de definir la [audiencia de la campaña](https://help.vtex.com/es/tutorial/Crear-audiencia-de-campanas--6cnuDZJzIkIeocewAQQK4K), acceda al Admin y siga los pasos a continuación para crear una promoción de campaña.
 
@@ -135,9 +133,7 @@ Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en
 
 En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
 
-<div class="alert alert-warning">
-  <p>Si selecciona <b>Aplicar a los siguientes productos</b> y no rellena ninguno de los criterios de selección, la promoción no se creará y aparecerá el mensaje <b>Defina los productos elegibles o aplique a todos los productos</b>. En este caso, debe volver y rellenar los criterios de selección o elegir <b>Aplicar a todos los productos</b>.</p>
-</div>
+>⚠️ Si selecciona **Aplicar a los siguientes productos** y no rellena ninguno de los criterios de selección, la promoción no se creará y aparecerá el mensaje **Defina los productos elegibles o aplique a todos los productos**. En este caso, debe volver y rellenar los criterios de selección o elegir **Aplicar a todos los productos**.
 
 Para ser válidos en la promoción, los productos deben cumplir todas las condiciones registradas en esta sección.
 
diff --git a/docs/tutorials/es/capture-form-suiteshare.md b/docs/tutorials/es/capture-form-suiteshare.md
index a09469e94..fe207905d 100644
--- a/docs/tutorials/es/capture-form-suiteshare.md
+++ b/docs/tutorials/es/capture-form-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: formulario-de-captura
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/carrier-working-hours.md b/docs/tutorials/es/carrier-working-hours.md
index c34694458..3e10963fc 100644
--- a/docs/tutorials/es/carrier-working-hours.md
+++ b/docs/tutorials/es/carrier-working-hours.md
@@ -29,9 +29,7 @@ La configuración del horario laboral influye en el cálculo del tiempo de entre
 1. En la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140), en la seción **Horario laboral**, haga clic en `Ventana de envío`.
 2. Si quieres activar la opción `Aceptar compras fuera del horario laboral`, activa el interruptor. De lo contrario, déjelo desactivado.
 
-  <div class="alert alert-danger">
-Para autorizar la transportadora a recibir pedidos los fines de semana, este interruptor debe estar marcado como <code>Activo</code>. Incluso si los sábados y domingos están configurados como ventanas válidas, activar el interruptor es obligatorio para autorizar al transportista a recibir pedidos fuera del horario laboral.
-</div>
+  >❗ Para autorizar la transportadora a recibir pedidos los fines de semana, este interruptor debe estar marcado como `Activo`. Incluso si los sábados y domingos están configurados como ventanas válidas, activar el interruptor es obligatorio para autorizar al transportista a recibir pedidos fuera del horario laboral.
 
   <div class = "alert alert-info">
 Cuando esta opción está habilitada, el <a href="https://help.vtex.com/es/tutorial/how-shipping-calculation-works--tutorials_116">cálculo del envío</a> del pedido se ve influenciado y al tiempo total de envío se suma el tiempo desde que se realiza el pedido hasta la hora de apertura del transportista.
diff --git a/docs/tutorials/es/category-registration-fields.md b/docs/tutorials/es/category-registration-fields.md
index 6cc172dd3..9d78a574d 100644
--- a/docs/tutorials/es/category-registration-fields.md
+++ b/docs/tutorials/es/category-registration-fields.md
@@ -19,15 +19,16 @@ Para entender mejor el significado de cada campo del registro de categoría, vea
 
 - __Nombre:__ nombre que quiere dar al departamento o categoría. Utilice palabras sencillas y evite otros idiomas o escritura compleja. Este campo es importante para SEO y debe respetar el límite de 150 caracteres.
 
-  <div class="alert alert-danger">
-    <p>Al rellenar el <b>Nombre</b> de la categoría, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
-    <ul>
-      <li><code>a</code></li>
-                  <li><code>meta</code></li>
-            <li><code>api</code></li>
-      <li><code>admin</code></li>
-    </ul></p>
-  </div>
+  >❗ Al rellenar el **Nombre** de la categoría, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
+>
+> * `a`
+>
+> * `meta`
+>
+> * `api`
+>
+> * `admin`
+>     
 
 - __Palabras sustitutas:__ sinónimos o términos relacionados al nombre dado para su departamento o categoría. "Televisión", por ejemplo, puede tener "TV" como palabra sustituta. Este campo es importante para hacer sus búsquedas más amplias y debe respetar el límite de 200 caracteres.
 - __Título de la Página de la categoría (Tag Title):__ texto que queda en la pestaña del navegador y corresponde al título de la página de la categoría, importante para los motores de búsqueda y SEO. Este campo sólo admite texto plano y no puede contener etiquetas HTML.
diff --git a/docs/tutorials/es/category-variations-and-attributes-mapping.md b/docs/tutorials/es/category-variations-and-attributes-mapping.md
index 2d21eaab3..343452a62 100644
--- a/docs/tutorials/es/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/es/category-variations-and-attributes-mapping.md
@@ -91,14 +91,11 @@ Dado esta información, continue completando la planilla siguiendo las instrucci
 5. __MeliValue:__ en esta columna debe rellenar los valores aceptados por  Mercado Libre correspondientes a los valores utilizados en el campo `VtexValue`. En la __Planilla de Atributos de Mercado Libre__, acceda a la pestaña correspondiente a su país y busque los valores aceptados para cada especificación que usted ha llenado en la columna.
 <br/>_`Ex:` si has llenado el `MeliEspc` con "Tamaño" y el `VtexValue` con "Pequeño", ver que el valor aceptado por Mercado Libre_
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> después de que se crea un anuncio por primera vez, ya <strong>no</strong> es posible cambiar sus variaciones. Si desea hacer cualquier modificación en las variaciones del anuncio, como cambiar el color, por ejemplo, será necesario finalizar el anuncio en el Mercado Libre y luego rehacer el mapeo de la planilla.</div>
+>⚠️ **OBS:** después de que se crea un anuncio por primera vez, ya **no** es posible cambiar sus variaciones. Si desea hacer cualquier modificación en las variaciones del anuncio, como cambiar el color, por ejemplo, será necesario finalizar el anuncio en el Mercado Libre y luego rehacer el mapeo de la planilla.
 
-<div class="alert alert-warning">
-<strong>OBS2:</strong> Mercado Libre <strong>no</strong> permite usar precios diferentes para cada variación de un anuncio. Por ejemplo, una camisa no puede costar $ 40 para el tamaño "P" y $ 50 para el tamaño "M".</div>
+>⚠️ **OBS2:** Mercado Libre **no** permite usar precios diferentes para cada variación de un anuncio. Por ejemplo, una camisa no puede costar $ 40 para el tamaño "P" y $ 50 para el tamaño "M".
 
-<div class="alert alert-warning">
-<strong>OBS3:</strong> si el SKU no tiene una determinada especificación (como color, por ejemplo), necesitará registrarla en VTEX antes de completar el proceso de integración. Recomendamos que agregue el atributo que falta como una especificación de <strong>producto</strong>. Por lo tanto, esta información no se mostrará en el sitio.</div>
+>⚠️ **OBS3:** si el SKU no tiene una determinada especificación (como color, por ejemplo), necesitará registrarla en VTEX antes de completar el proceso de integración. Recomendamos que agregue el atributo que falta como una especificación de **producto**. Por lo tanto, esta información no se mostrará en el sitio.
 
 ## Atributos
 
diff --git a/docs/tutorials/es/change-seller-of-an-vtex-sales-app-order-beta.md b/docs/tutorials/es/change-seller-of-an-vtex-sales-app-order-beta.md
index b379142bd..f9d2e37ae 100644
--- a/docs/tutorials/es/change-seller-of-an-vtex-sales-app-order-beta.md
+++ b/docs/tutorials/es/change-seller-of-an-vtex-sales-app-order-beta.md
@@ -15,6 +15,4 @@ legacySlug: cambiar-el-seller-de-un-pedido-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
index 23bdf3150..6a27f5a52 100644
--- a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -20,9 +20,7 @@ En VTEX, las tiendas pueden configurar manualmente el precio de un artículo (SK
 - **Perfil de acceso**: Owner (Admin Super) o Call Center Operator (Telesales) 
 - **Permiso**: Shopping Cart Full Access
 
-<div class="alert alert-warning">
-  Los pasos a continuación se deben realizar en el dominio <i>myvtex</i> de cada tienda ({accountName}.myvtex.com.br).
-</div>
+>⚠️ Los pasos a continuación se deben realizar en el dominio <i>myvtex</i> de cada tienda ({accountName}.myvtex.com.br).
 
 ## Cambiar el precio del ítem
 
diff --git a/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
index 924fbfc0a..9b910068f 100644
--- a/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/es/changing-default-system-texts-displayed-in-the-store.md
@@ -47,9 +47,8 @@ Para hacer esto de manera dinámica, puedo cambiar el texto de la clave `topbarS
 
 Es decir, estoy usando las variables `preposicaonomeloja2` y `nomeloja`.
 
-<div class="alert alert-warning">>
-Al utilizar variables para crear un texto, reemplace el símbolo <code>#</code> por <code>@</code>. Es decir, <b>#variable#</b> se convierte <b>@variable@</b>.
-</div>
+>⚠️ >
+> Al utilizar variables para crear un texto, reemplace el símbolo `#` por `@`. Es decir, **#variable#** se convierte **@variable@**.
 
 ![textos-importantes es](https://images.ctfassets.net/alneenqid6w5/3Trct11oXCGe0EigiUA4g0/f701207101145a1222f5e45cb61d4073/textos_importantes_es.png)
 
diff --git a/docs/tutorials/es/changing-items-from-a-complete-order.md b/docs/tutorials/es/changing-items-from-a-complete-order.md
index dc2fa989c..db2ac54d0 100644
--- a/docs/tutorials/es/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/es/changing-items-from-a-complete-order.md
@@ -22,9 +22,7 @@ Hay dos formas de modificar un pedido:
 * [Admin VTEX:](#como-cambiar) esta opción se puede utilizar si el status del pedido es `Preparando entrega`.
 * [API de cambio de pedidos:](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes) además de cambiar los ítems, se puede crear descuentos y modificar el precio del pedido. El cambio solo se puede realizar si el status del pedido en la API de pedidos es `handling` o `waiting-for-fulfillment`.
 
-<div class="alert alert-warning">
-Tras el cambio, el cliente recibe una notificación por email si la plantilla <code>Change of information</code> (<a href="https://help.vtex.com/es/tutorial/plantillas-de-emails-transaccionales-del-pedido--3g2S2kqBOoSGcCaqMYK2my">plantillas de emails transaccionales referentes al pedido)</a> está activada en el Centro de mensajes. El cliente recibe los mensajes con la información que se ha rellenado en el formulario de cambio de ítems.
-</div>
+>⚠️ Tras el cambio, el cliente recibe una notificación por email si la plantilla `Change of information` ([plantillas de emails transaccionales referentes al pedido)](https://help.vtex.com/es/tutorial/plantillas-de-emails-transaccionales-del-pedido--3g2S2kqBOoSGcCaqMYK2my) está activada en el Centro de mensajes. El cliente recibe los mensajes con la información que se ha rellenado en el formulario de cambio de ítems.
 
 ## Restricciones
 
diff --git a/docs/tutorials/es/changing-the-total-cost-of-the-order.md b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
index 8dd951d3d..9f1be3758 100644
--- a/docs/tutorials/es/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
@@ -17,9 +17,7 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 La página [Detalles del pedido](https://help.vtex.com/es/tutorial/pagina-de-detalles-del-pedido-beta--2Y75n54Cc9VizrlG1N6ZNl) permite modificar el valor final del pedido para los pedidos que aún no han sido facturados. Esto ocurre en los escenarios en los que hay descuentos o adiciones al valor.
 
-<div class="alert alert-warning">
-Recuerda que la funcionalidad solo está disponible para los pedidos con el status <code>Preparando entrega</code>.
-</div>
+>⚠️ Recuerda que la funcionalidad solo está disponible para los pedidos con el status `Preparando entrega`.
 
 Para hacer el cambio, sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/chat.md b/docs/tutorials/es/chat.md
index ead5b31ae..b4e19fb7c 100644
--- a/docs/tutorials/es/chat.md
+++ b/docs/tutorials/es/chat.md
@@ -15,6 +15,4 @@ legacySlug: chat
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/checking-for-errors-or-problems-in-a-transaction.md b/docs/tutorials/es/checking-for-errors-or-problems-in-a-transaction.md
index 6fdc4d0b2..d258b3163 100644
--- a/docs/tutorials/es/checking-for-errors-or-problems-in-a-transaction.md
+++ b/docs/tutorials/es/checking-for-errors-or-problems-in-a-transaction.md
@@ -21,9 +21,7 @@ Los logs de una transacción se registran en una línea de tiempo, con las inter
 
 El gateway de VTEX puede comunicarse con adquirentes, subadquirentes, antifraudes y otros gateways. Los __cambios de status en la transacción__ y los __mensajes de respuesta de los socios__ se muestran en cuadros en la pantalla de detalles de transacción.
 
-<div class="alert alert-info">
-<a href="https://help.vtex.com/es/faq/tarjeta-de-credito-flujo-basico-de-un-pago">Haga clic aquí</a> para saber cómo funciona el flujo básico de una transacción de tarjeta de crédito. Usted puede también acceder a <a href="https://help.vtex.com/es/faq/boleto-bancario-registrado-flujo">nuestro artículo</a> con el esquema básico de una transacción con boleto bancario.
-</div>
+>ℹ️ [Haga clic aquí](https://help.vtex.com/es/faq/tarjeta-de-credito-flujo-basico-de-un-pago) para saber cómo funciona el flujo básico de una transacción de tarjeta de crédito. Usted puede también acceder a [nuestro artículo](https://help.vtex.com/es/faq/boleto-bancario-registrado-flujo) con el esquema básico de una transacción con boleto bancario.
 
 ## Comprobar el status de la transacción
 
diff --git a/docs/tutorials/es/checkout-vtex-overview.md b/docs/tutorials/es/checkout-vtex-overview.md
index 18078746b..56219661f 100644
--- a/docs/tutorials/es/checkout-vtex-overview.md
+++ b/docs/tutorials/es/checkout-vtex-overview.md
@@ -37,9 +37,7 @@ Siempre que el cliente realiza un cambio en el carrito (agrega o elimina ítems)
 
 ![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/435f909fb3e5493329a6a76fcb398134/Checkout_Overview_ES.png)
 
-<div class="alert alert-info">
-Si un <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#">Seller white label</a>, puede entregar uno o más ítems de los que eligió el cliente, se realizarán simulaciones (tal como se muestra a la derecha de la imagen) para determinar qué sellers serán los responsables de entregar los ítems. Obtén más información en <a href="https://help.vtex.com/es/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Selección de sellers white label</a>.
-</div>
+>ℹ️ Si un [Seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#), puede entregar uno o más ítems de los que eligió el cliente, se realizarán simulaciones (tal como se muestra a la derecha de la imagen) para determinar qué sellers serán los responsables de entregar los ítems. Obtén más información en [Selección de sellers white label](https://help.vtex.com/es/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#).
 
 ## Funcionalidades del módulo Checkout de VTEX
 
@@ -55,8 +53,6 @@ Entre las principales funcionalidades disponibles en el módulo Checkout de VTEX
 
 Actualmente, hay dos versiones operativas del módulo Checkout de VTEX: **Checkout v5** y **Checkout v6**.
 
-<div class="alert alert-info">
-  La versión <b>Checkout v5</b> ya no recibe actualizaciones ni soporte operativo directo. Es precisamente por esto que te recomendamos usar la versión <b>Checkout v6</b> en tu tienda.
-</div>
+>ℹ️ La versión **Checkout v5** ya no recibe actualizaciones ni soporte operativo directo. Es precisamente por esto que te recomendamos usar la versión **Checkout v6** en tu tienda.
 
 Para más información sobre las configuraciones y las API del módulo Checkout, accede a [Checkout Overview no Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/checkout-overview).
diff --git a/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md b/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
index 9c1a01485..060f3b22c 100644
--- a/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
+++ b/docs/tutorials/es/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
@@ -27,9 +27,7 @@ La plataforma VTEX permite crear diferentes arquitecturas para tu tienda, empeza
 
 Este artículo presenta las diferencias entre arquitectura multitienda y entorno adicional para que identifiques cuál es el más adecuado para los distintos escenarios. 
 
-<div class="alert alert-info">
-Para arquitecturas de marketplace, también se puede <a href="https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Elegir entre cuenta franquicia, Seller Portal o cuenta estándar</a>, o utilizar la configuración <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory </a>.
-  </div>
+>ℹ️ Para arquitecturas de marketplace, también se puede [Elegir entre cuenta franquicia, Seller Portal o cuenta estándar](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78), o utilizar la configuración [Multilevel Omnichannel Inventory ](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4).
 
 ## Comparación entre arquitectura multitienda y entorno adicional
 
diff --git a/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
index d902aa8f0..29b604f82 100644
--- a/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -23,7 +23,7 @@ En VTEX, existen tres tipos de cuenta, y cada una permite actuar con un perfil d
 - **Cuenta franquicia:** en el momento en que se crea, se asocia a una cuenta estándar, de la cual hereda el catálogo. La [cuenta franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) puede configurar su propia logística, pagos y precios, y tiene los módulos de la plataforma VTEX en forma parcial, además de un [seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 - **Seller Portal:** el [Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) es una edición de la plataforma VTEX que les permite a los _sellers_ conectarse y vender productos en _marketplaces_ del ecosistema VTEX, independientemente de si el _seller_ ya tiene una cuenta en VTEX o no. El Seller Portal brinda acceso parcial a los módulos de la plataforma, y el _seller_ puede ser normal o [white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 
-<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+>⚠️ El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.
 
 La tabla que figura a continuación muestra los principales escenarios de uso de cada tipo de cuenta:
 
diff --git a/docs/tutorials/es/cms-folder-structure.md b/docs/tutorials/es/cms-folder-structure.md
index 003146a2b..286fa2f62 100644
--- a/docs/tutorials/es/cms-folder-structure.md
+++ b/docs/tutorials/es/cms-folder-structure.md
@@ -37,9 +37,7 @@ A continuación, vea estas carpetas básicas en el CMS:
 
 Estas carpetas vienen de forma predeterminada en el ambiente de todas las tiendas VTEX.
 
-<div class="alert alert-danger">
-  <p>Los nombres de las carpetas obligatorias no deben modificarse. Esto puede comprometer el funcionamiento normal de la tienda e impedir que se realicen las compras.</p>
-</div>
+>❗ Los nombres de las carpetas obligatorias no deben modificarse. Esto puede comprometer el funcionamiento normal de la tienda e impedir que se realicen las compras.
 
 Como las carpetas se refieren a páginas dinámicas, sus nombres no aparecen en la navegación del cliente. Es decir, el hecho de que la edición de los nombres sea vetada no afecta el texto final de sus URLs ni, por lo tanto, la internacionalización de su sitio web.
 
@@ -55,9 +53,8 @@ Estas son:
 
 Para estas dos carpetas, lo que importa es el control o placeholder que lee su contenido. Sus nombres se pueden editar libremente.
 
-<div class="alert alert-warning">>
-Como son carpetas privadas, <code>/account</code> y <code>/account/orders</code> <b>deben requerir autenticación</b>. Ver <a href="http://help.vtex.com/es/tutorial/exigir-autenticacion-en-paginas-de-la-tienda">en este artículo</a> cómo asegurarse de que están configuradas para solicitar autenticación del usuario.
-</div>
+>⚠️ >
+> Como son carpetas privadas, `/account` y `/account/orders` **deben requerir autenticación**. Ver [en este artículo](http://help.vtex.com/es/tutorial/exigir-autenticacion-en-paginas-de-la-tienda) cómo asegurarse de que están configuradas para solicitar autenticación del usuario.
 
 ## Carpetas útiles
 
diff --git a/docs/tutorials/es/collection-highlight-control.md b/docs/tutorials/es/collection-highlight-control.md
index fe9aef535..ac8e57de0 100644
--- a/docs/tutorials/es/collection-highlight-control.md
+++ b/docs/tutorials/es/collection-highlight-control.md
@@ -38,6 +38,4 @@ Usted puede, entonces, personalizar el CSS para definir de qué manera la clase
 
 Esta feature se puede utilizar, por ejemplo, para hacer que los productos de una colección llamada "Lanzamiento" aparezcan siempre con una flag que señala que son novedad en la tienda. Al agregar el control en el template de la página de categoría, por ejemplo, todos los productos de la colección Lanzamiento que aparecen en una página de categoría se mostrarán con este destaque.
 
-<div class="alert alert-warning">
-Recuerde que si la página es de producto, el control que se debe utilizar es el <code>&lt;vtex.cmc:HightLight/&gt;</code>. Si es una página de vitrina, usted debe utilizar el <code>$product.HightLight</code>.
-</div>
+>⚠️ Recuerde que si la página es de producto, el control que se debe utilizar es el `&lt;vtex.cmc:HightLight/&gt;`. Si es una página de vitrina, usted debe utilizar el `$product.HightLight`.
diff --git a/docs/tutorials/es/como-criar-usuario-webservice.md b/docs/tutorials/es/como-criar-usuario-webservice.md
index f08db98ef..06a19dac5 100644
--- a/docs/tutorials/es/como-criar-usuario-webservice.md
+++ b/docs/tutorials/es/como-criar-usuario-webservice.md
@@ -15,9 +15,11 @@ legacySlug: como-crear-usuario-webservice
 subcategory: 63DHe3VQEEE6Uuua8gIs2M
 ---
 
-<div class="alert alert-danger"><p>Atención: sólo los métodos SOAP pertinentes al <strong>catálogo</strong> son válidos.</p>
-<p><strong>Todos los demás métodos del Web Service serán discontinuados después de 28/02/2017.</strong></p>
-<p>Utilice las API REST equivalentes disponibles en nuestro<a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atención: sólo los métodos SOAP pertinentes al **catálogo** son válidos.
+>
+> **Todos los demás métodos del Web Service serán discontinuados después de 28/02/2017.**
+>
+> Utilice las API REST equivalentes disponibles en nuestro[Developer Docs](//help.vtex.com/developer-docs/).
 
 La creación de credenciales para las integraciones con el Web Service debe ser hecha por License Manager, con la funcionalidad de appKey y appToken.
 
diff --git a/docs/tutorials/es/como-funciona-a-integracao-da-netshoes.md b/docs/tutorials/es/como-funciona-a-integracao-da-netshoes.md
index ebc7518d6..9e0726ca1 100644
--- a/docs/tutorials/es/como-funciona-a-integracao-da-netshoes.md
+++ b/docs/tutorials/es/como-funciona-a-integracao-da-netshoes.md
@@ -54,9 +54,7 @@ Al ser enviados con éxito por primera vez, Netshoes recibe los productos y real
 
 _`Ej:` si se cambia la descripción del producto, la integración no actualizará la descripción que se encuentra en el marketplace._
 
-<div class="alert alert-warning">
-Nota: el producto no se puede borrar en el panel de Netshoes, porque así no podría ser enviado por la integración de nuevo.
-</div>
+>⚠️ Nota: el producto no se puede borrar en el panel de Netshoes, porque así no podría ser enviado por la integración de nuevo.
 
 En Netshoes, los productos tienen dos status posibles:
 - __Activo:__ disponible para la venta
@@ -76,9 +74,7 @@ Una vez que el proceso de catalogación es finalizado en Netshoes, la integraci
 
 Una vez que los productos reciben la primera carga de inventario, la actualización se realiza SKU por SKU cada vez que se produce algún cambio de stock en VTEX.
 
-<div class="alert alert-warning">
-<strong>Nota:</strong> los datos de inventario enviados a Netshoes quedan registrados en nuestro sistema por sólo <strong>3 meses</strong>.
-</div>
+>⚠️ **Nota:** los datos de inventario enviados a Netshoes quedan registrados en nuestro sistema por sólo **3 meses**.
 
 ## 3 - Precios
 
@@ -94,11 +90,11 @@ _`Ej1:` promoción del 10% de descuento para una categoría determinada_
 
 _`Ej2:` SKU X está con precio de $ 10,00 en la política comercial usada en Netshoes y tiene un precio fijo de $ 15,00 para esa misma política. La integración enviará el precio de $ 15,00._
 
-<div class="alert alert-warning">
-Nota: Como la forma de pago se hace en el marketplace, las reglas de pago son determinadas por él. Por eso, no conseguimos enviar precios diferenciados en función de la forma de pago.
-<br />
-<em>Ej: si en VTEX existen intereses configurados para pagos parcelados, el precio enviado todavía será lo que la simulación de fulfillment devuelve.</em>
-</div>
+>⚠️ Nota: Como la forma de pago se hace en el marketplace, las reglas de pago son determinadas por él. Por eso, no conseguimos enviar precios diferenciados en función de la forma de pago.
+>
+>
+> 
+> *Ej: si en VTEX existen intereses configurados para pagos parcelados, el precio enviado todavía será lo que la simulación de fulfillment devuelve.*
 
 ## 4 - Promociones
 
@@ -113,9 +109,7 @@ Sólo se aplican promociones que se pueden calcular en la simulación de fulfill
 | Envío Máximo | - | Tipo de Envío |
 | Envío Gratis | - | - |
 
-<div class="alert alert-info">
-No es posible aplicar <strong>ninguna condición</strong> en las promociones cuyos campos se completaron como <strong>-</strong>, es decir, no se contemplará ninguna condición en la integración.
-</div>
+>ℹ️ No es posible aplicar **ninguna condición** en las promociones cuyos campos se completaron como **-**, es decir, no se contemplará ninguna condición en la integración.
 
 ## 5 - Flujo de Pedidos
 
@@ -127,15 +121,19 @@ Cuando un pedido se hace en el marketplace hay algunos puntos que influencian en
 
 En esta integración existen dos puntos que influenciarán en la entrega: __Cálculo del envío__ y el __Tiempo de Preparación de Envío__. La suma de los dos será el __Tiempo de Entrega Total__.
 
-<div class="alert alert-info">
-Ej:
-<br />
-Envío normal = 3 días
-<br />
-Tiempo de Costo = 2 días
-<br />
-Tiempo Total de Entrega = 5 días
-</div>
+>ℹ️ Ej:
+>
+>
+> 
+> Envío normal = 3 días
+>
+>
+> 
+> Tiempo de Costo = 2 días
+>
+>
+> 
+> Tiempo Total de Entrega = 5 días
 
 - __Envío__
 
@@ -149,46 +147,78 @@ Si la integración no puede encontrar un tipo de transportista igual, nosotros i
 
 El tiempo de preparación de envío se basa en la suma del campo `Tiempo de coste` en el Inventario con el `Tiempo de Coste` en el muelle. Y enviamos el mismo tiempo de preparación de forma masiva para todos los productos.
 
-<div class="alert alert-info">
-Ej:
-<br />
-<strong>Inventario A</strong>
-<br />
-- Muelle 1: Tiempo de Costo = 3 días
-<br />
-<strong>Inventario B</strong>
-<br />
-- Muelle 1: Tiempo de Costo = 5 días
-<br />
-<br />
-<strong>Muelle 1:</strong>
-<br />
-- Tiempo de Costo = 2 días
-<br />
-<br />
-Un pedido con tiempo de envío = 3 días se quedará con un total de entrega diferente dependiendo de dónde salga el producto.
-<br />
-<br />
-<strong>Saliendo del inventario A:</strong>
-<br />
-- Tiempo de preparación = 3 + 2 (muelle 1) = 5 días
-<br />
-- Tiempo de envío = 3 días
-<br />
-- Tiempo total de entrega = 8 días
-<br />
-<strong>Saliendo del inventario B:</strong>
-<br />
-- Tiempo de preparación = 5 + 2 (muelle 1) = 7 días
-<br />
-- Tiempo de envío = 3 días
-<br />
-- Tiempo total de entrega = 10 días
-</div>
-
-<div class="alert alert-warning">
-Nota: En el caso de usar la tabla de contingencia para hacer el cálculo del envío, Netshoes no consulta a VTEX. De esta forma, el único factor que se tendrá en cuenta para el <strong>Tiempo total de entrega</strong> será el <strong>envío</strong> proporcionado por ellos, ignorando el <strong>Tiempo de preparación</strong>. Se debe tener cuidado con esto, porque puede generar divergencias en el <strong>Tiempo total de entrega</strong>.
-</div>
+>ℹ️ Ej:
+>
+>
+> 
+> **Inventario A**
+>
+>
+> 
+> - Muelle 1: Tiempo de Costo = 3 días
+>
+>
+> 
+> **Inventario B**
+>
+>
+> 
+> - Muelle 1: Tiempo de Costo = 5 días
+>
+>
+> 
+>
+>
+> 
+> **Muelle 1:**
+>
+>
+> 
+> - Tiempo de Costo = 2 días
+>
+>
+> 
+>
+>
+> 
+> Un pedido con tiempo de envío = 3 días se quedará con un total de entrega diferente dependiendo de dónde salga el producto.
+>
+>
+> 
+>
+>
+> 
+> **Saliendo del inventario A:**
+>
+>
+> 
+> - Tiempo de preparación = 3 + 2 (muelle 1) = 5 días
+>
+>
+> 
+> - Tiempo de envío = 3 días
+>
+>
+> 
+> - Tiempo total de entrega = 8 días
+>
+>
+> 
+> **Saliendo del inventario B:**
+>
+>
+> 
+> - Tiempo de preparación = 5 + 2 (muelle 1) = 7 días
+>
+>
+> 
+> - Tiempo de envío = 3 días
+>
+>
+> 
+> - Tiempo total de entrega = 10 días
+
+>⚠️ Nota: En el caso de usar la tabla de contingencia para hacer el cálculo del envío, Netshoes no consulta a VTEX. De esta forma, el único factor que se tendrá en cuenta para el **Tiempo total de entrega** será el **envío** proporcionado por ellos, ignorando el **Tiempo de preparación**. Se debe tener cuidado con esto, porque puede generar divergencias en el **Tiempo total de entrega**.
 
 #### Precio/Disponibilidad:
 
diff --git a/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md b/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
index a396ec0a2..010105979 100644
--- a/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
+++ b/docs/tutorials/es/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
@@ -31,8 +31,6 @@ A continuación se muestra la relación entre la carpeta en el CMS y el código
 
 ![CommerceContext](https://images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
 
-<div class="alert alert-info">
-Esta línea de código está siempre comentada. Por lo tanto, tiene función sólo informativa. Es decir, no realiza ninguna acción.
-</div>
+>ℹ️ Esta línea de código está siempre comentada. Por lo tanto, tiene función sólo informativa. Es decir, no realiza ninguna acción.
 
 Esta información es útil, por ejemplo, para saber qué carpeta la búsqueda por cierto término está retornando en su tienda.
diff --git a/docs/tutorials/es/conditions-builder-usage-examples.md b/docs/tutorials/es/conditions-builder-usage-examples.md
index dea047382..1bec9f2f2 100644
--- a/docs/tutorials/es/conditions-builder-usage-examples.md
+++ b/docs/tutorials/es/conditions-builder-usage-examples.md
@@ -26,9 +26,8 @@ UTM (Marketing tag) es una información que se refiere al origen del tráfico de
 
 ![utm_source_english](https://images.ctfassets.net/alneenqid6w5/1eC4fEARZG84MYiSmekSIm/5c784e46e4ab63487f183f7cd2060ea9/utm_source_english.png)
 
-<div class="alert alert-warning"><strong>Nota: </strong>
-Es posible que su tienda utilice personalización y, por eso, las informaciones de UTM contenidas en la URL no se están pasando a nuestro sistema. Si utiliza personalización de Javascript, lea el artículo <a href="https://help.vtex.com/es/faq/por-que-las-utms-no-se-aplican-al-carrito">¿Por qué las UTMs no se aplican al carrito?</a>
-</div>
+>⚠️ **Nota: **
+> Es posible que su tienda utilice personalización y, por eso, las informaciones de UTM contenidas en la URL no se están pasando a nuestro sistema. Si utiliza personalización de Javascript, lea el artículo [¿Por qué las UTMs no se aplican al carrito?](https://help.vtex.com/es/faq/por-que-las-utms-no-se-aplican-al-carrito)
 
 ### utm_source
 
diff --git a/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md b/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
index ba59fa880..b40552cf7 100644
--- a/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
+++ b/docs/tutorials/es/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
@@ -15,9 +15,7 @@ legacySlug: error-de-configuracion-en-cuentas-de-mercado-libre-con-multiples-tie
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-En caso de que tenga tiendas oficiales en Mercado Libre, esta documentación puede ser relevante. Mercado Libre tiene sus propios parámetros de certificación para que los sellers sean tiendas oficiales. Si desea obtener más información, contacte a su asesor de Mercado Libre.
-</div>
+>ℹ️ En caso de que tenga tiendas oficiales en Mercado Libre, esta documentación puede ser relevante. Mercado Libre tiene sus propios parámetros de certificación para que los sellers sean tiendas oficiales. Si desea obtener más información, contacte a su asesor de Mercado Libre.
 
 El [seller](https://help.vtex.com/es/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) integra sus [subaccounts](https://help.vtex.com/es/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK?&utm_source=autocomplete) con las [tiendas oficiales](https://www.mercadolibre.com.ar/tiendas-oficiales) del usuario de [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/51oWBHvVxSs8eAwLQhSbSd), esto puede producir un error en la importación de productos desde la integración con dicha plataforma.
 
diff --git a/docs/tutorials/es/configure-cartman.md b/docs/tutorials/es/configure-cartman.md
index d6651207c..0debac69b 100644
--- a/docs/tutorials/es/configure-cartman.md
+++ b/docs/tutorials/es/configure-cartman.md
@@ -34,9 +34,7 @@ Este artículo cubrirá los siguientes temas:
   - [Establecer datos de marketing](#establecer-datos-de-marketing)
 - [Deshabilitar Cartman](#deshabilitar-cartman) 
 
-<div class="alert alert-warning">
-  Solo el comerciante tiene acceso a <b>Cartman</b>. Sus funciones no están disponibles para el uso de los usuarios en una tienda.
-</div>
+>⚠️ Solo el comerciante tiene acceso a **Cartman**. Sus funciones no están disponibles para el uso de los usuarios en una tienda.
 
 ## Activar Cartman manualmente
 
@@ -106,7 +104,5 @@ Cartman se puede desactivar en cualquier momento según lo requiera el lojista.
 2. En la esquina inferior derecha de la pantalla, haga clic en el botón <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
 3. En la parte inferior del menú de Cartman, haz clic en `Deshabilitar Cartman`.
 
-<div class="alert alert-info">
-  Si desea reactivar <b>Cartman</b>, vuelva a agregar la query string <code>?cartman=on</code> en una de las páginas de pago de su tienda. De esta forma, el icono azul volverá a estar disponible en la esquina inferior derecha de la página.
-</div>
+>ℹ️ Si desea reactivar **Cartman**, vuelva a agregar la query string `?cartman=on` en una de las páginas de pago de su tienda. De esta forma, el icono azul volverá a estar disponible en la esquina inferior derecha de la página.
 
diff --git a/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
index dd59caa7e..d5de63deb 100644
--- a/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/es/configure-employee-benefits-using-master-data-clusters.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 En VTEX, se puede aplicar una promoción o descuento a un grupo de clientes. Este grupo de clientes se puede definir por las propiedades que tienen en común.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 Este artículo muestra cómo configurar una promoción para los empleados. Se considera que los empleados son un grupo de clientes, por lo que se identifican mediante clústeres de Master Data.
 
diff --git a/docs/tutorials/es/configure-seller-regionalization.md b/docs/tutorials/es/configure-seller-regionalization.md
index c109dae29..152136f96 100644
--- a/docs/tutorials/es/configure-seller-regionalization.md
+++ b/docs/tutorials/es/configure-seller-regionalization.md
@@ -43,6 +43,4 @@ Para activar **Region** en tu tienda, debes realizar los siguientes pasos:
 1. [Configurar el precio y la disponibilidad de SKUs por Region](https://help.vtex.com/es/tutorial/configurar-el-precio-y-la-disponibilidad-de-skus-por-region--12ne58BmvYsYuGsimmugoc#)
 2. [Habilitar la funcionalidad Region](https://developers.vtex.com/docs/guides/enable-the-region-for-skus)
 
-<div class="alert alert-info">
-  Actualmente, el <b>Region</b> está disponible para su uso en todas las tiendas VTEX en v2. Obtenga más información en <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
-</div>
+>ℹ️ Actualmente, el **Region** está disponible para su uso en todas las tiendas VTEX en v2. Obtenga más información en <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
diff --git a/docs/tutorials/es/configure-template-in-smartcheckout-update.md b/docs/tutorials/es/configure-template-in-smartcheckout-update.md
index 8c362447f..82cdd7723 100644
--- a/docs/tutorials/es/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/es/configure-template-in-smartcheckout-update.md
@@ -19,9 +19,7 @@ El __portal__ es usado para renderizar las pantallas de __Checkout__ (carrito, d
 
 El módulo __Checkout__ en Admin, muestra los sitios que están registrados para su cuenta. A través de él, también es posible crear un nuevo sitio, editar y configurar información sobre sitios existentes.
 
-<div class="alert alert-info">
-Cada sitio registrado corresponde a un multidominio (si la cuenta tiene multidominios contratados). Para cuentas que no utilizan multidominios, no es necesario registrar más de un sitio en este módulo. Obtenga más información en <a href="https://help.vtex.com/es/tutorial/como-criar-multiloja-multidominio--tutorials_510#">Crear multitienda/multidominio</a>.
-</div>
+>ℹ️ Cada sitio registrado corresponde a un multidominio (si la cuenta tiene multidominios contratados). Para cuentas que no utilizan multidominios, no es necesario registrar más de un sitio en este módulo. Obtenga más información en [Crear multitienda/multidominio](https://help.vtex.com/es/tutorial/como-criar-multiloja-multidominio--tutorials_510#).
 
 ## Crear un nuevo sitio web
 
@@ -100,9 +98,7 @@ El código HTML completado en el template corresponde a lo que aparecerá en las
 
 De templates disponibles, los únicos que no se pueden cambiar son __vtex-checkout__ y __vtex-orderPlaced__. Estos corresponden al funcionamiento nativo de la plataforma, presentando el contenido principal de las páginas de __checkout__ y __order placed__.
 
-<div class="alert alert-warning">
-La plataforma ignorará los Javascripts incluidos directamente en cualquier template del Portal. Es decir, en el momento de renderizar la página, la plataforma la eliminará. Esto se debe a que <a href="https://help.vtex.com/es/tutorial/smartcheckout-preenchimento-automatico-de-dados-do-cliente--2Nuu3xAFzdhIzJIldAdtan#">SmartCheckout</a> solo acepta scripts originados en Google Tag Manager. Por lo tanto, siempre que sea necesario realizar alguna personalización (o incluso la inserción de etiquetas específicas) a través de javascript, utilice <a href="https://help.vtex.com/es/tutorial/integration-with-google-tag%20-%20gerente--frequentlyAskedQuestions_616#">Google Tag Manager</a>.
-</div>
+>⚠️ La plataforma ignorará los Javascripts incluidos directamente en cualquier template del Portal. Es decir, en el momento de renderizar la página, la plataforma la eliminará. Esto se debe a que [SmartCheckout](https://help.vtex.com/es/tutorial/smartcheckout-preenchimento-automatico-de-dados-do-cliente--2Nuu3xAFzdhIzJIldAdtan#) solo acepta scripts originados en Google Tag Manager. Por lo tanto, siempre que sea necesario realizar alguna personalización (o incluso la inserción de etiquetas específicas) a través de javascript, utilice [Google Tag Manager](https://help.vtex.com/es/tutorial/integration-with-google-tag%20-%20gerente--frequentlyAskedQuestions_616#).
 
 ### Ejemplos de cómo rellenar templates 
 
diff --git a/docs/tutorials/es/configuring-a-data-entity.md b/docs/tutorials/es/configuring-a-data-entity.md
index 61b19d511..e7ce52dcd 100644
--- a/docs/tutorials/es/configuring-a-data-entity.md
+++ b/docs/tutorials/es/configuring-a-data-entity.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-06-21-at-09-16-27
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/configuring-a-marketplace-trade-policy.md b/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
index 41d2504b1..958a2a5c0 100644
--- a/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/es/configuring-a-marketplace-trade-policy.md
@@ -78,9 +78,7 @@ Los *sellers* pueden restringir la disponibilidad de los productos en su catálo
 
 Esta configuración se realiza en el módulo *Catálogo*, al [registrar productos](https://help.vtex.com/es/tutorial/cadastrando-produtos--tutorials_2567) e indicar a qué políticas comerciales estarán vinculados. Si no se establecen restricciones al crear el producto, estará disponible en todas las políticas comerciales. 
 
-<div class="alert alert-warning">
-  No recomendamos vincular políticas comerciales a colecciones para determinar el surtido de productos, especialmente para los marketplaces fuera de VTEX. Cuando se elimina un producto de la colección de políticas comerciales, el sistema VTEX no notifica al marketplace de esta actualización, lo que hace que el producto continúe disponible en el marketplace.
-  </div>
+>⚠️ No recomendamos vincular políticas comerciales a colecciones para determinar el surtido de productos, especialmente para los marketplaces fuera de VTEX. Cuando se elimina un producto de la colección de políticas comerciales, el sistema VTEX no notifica al marketplace de esta actualización, lo que hace que el producto continúe disponible en el marketplace.
 
 [![ES Catalogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/7be99b14d44e2f31d29e740e71954830/ES_Catalogo_Politica.jpg)
 
diff --git a/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md b/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md
index 615c68be9..43e8d43ef 100644
--- a/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md
+++ b/docs/tutorials/es/configuring-a-pricing-rule-for-a-sales-policy.md
@@ -15,9 +15,7 @@ legacySlug: configurar-regla-de-precio-para-politica-comercial
 subcategory: wUepkh8pzimEywO8oGUIc
 ---
 
-<div class="alert alert-info">
-Este artículo hace referencia a la versión más reciente de pricing de VTEX. Si su tienda aún no está en esta nueva versión, usted puede solicitar la migración poniéndose en contacto con nuestro equipo de atención.
-</div>
+>ℹ️ Este artículo hace referencia a la versión más reciente de pricing de VTEX. Si su tienda aún no está en esta nueva versión, usted puede solicitar la migración poniéndose en contacto con nuestro equipo de atención.
 
 Una __regla de precio__ es un conjunto de condiciones que determinan los precios para una cierta política comercial.
 
diff --git a/docs/tutorials/es/configuring-a-santander-registered-boleto.md b/docs/tutorials/es/configuring-a-santander-registered-boleto.md
index c3e4174a1..d167739eb 100644
--- a/docs/tutorials/es/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/es/configuring-a-santander-registered-boleto.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-12-04-at-07-04-02
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/configuring-access-profiles-old.md b/docs/tutorials/es/configuring-access-profiles-old.md
index 8155261ce..4be01329f 100644
--- a/docs/tutorials/es/configuring-access-profiles-old.md
+++ b/docs/tutorials/es/configuring-access-profiles-old.md
@@ -34,9 +34,7 @@ Vea algunos perfiles útiles:
 - __Financeiro:__ concede acceso al submódulo Financiero, dentro del License Manager, permitiendo ver boletos y NFs relativos al pago del servicio VTEX.
 - __Webservice:__ permite que el usuario acceda a los métodos del webservice, necesarios para algunas integraciones (en general, con el catálogo).
 
-<div class="alert alert-warning">
-<strong>Atención</strong>: los perfiles de televenta bloquean el acceso al módulo Catalog. Es decir, no pueden acceder al registro de productos, por ejemplo. Si es necesario acceder a este módulo, el usuario debe trabajar con dos logins diferentes.
-</div>
+>⚠️ **Atención**: los perfiles de televenta bloquean el acceso al módulo Catalog. Es decir, no pueden acceder al registro de productos, por ejemplo. Si es necesario acceder a este módulo, el usuario debe trabajar con dos logins diferentes.
 
 ## Creando nuevos perfiles
 
diff --git a/docs/tutorials/es/configuring-access-without-www.md b/docs/tutorials/es/configuring-access-without-www.md
index 3ba2db4f0..ec424d54f 100644
--- a/docs/tutorials/es/configuring-access-without-www.md
+++ b/docs/tutorials/es/configuring-access-without-www.md
@@ -41,9 +41,7 @@ También se puede utilizar la redirección de DNS, según provista por diferente
 
 Para realizar una redirección de DNS de forma sencilla, a continuación están las instrucciones para la redirección con el servicio [redirect.center](http://redirect.center/).
 
-<div class="alert alert-warning">
-Cabe resaltar que Redirect Center no es un servicio de VTEX y no funciona con HTTPS. Hay otros servicios similares, pero VTEX no recomienda ninguno en específico. VTEX no se hace responsable por problemas causados por servicios externos de redirección.
-</div>
+>⚠️ Cabe resaltar que Redirect Center no es un servicio de VTEX y no funciona con HTTPS. Hay otros servicios similares, pero VTEX no recomienda ninguno en específico. VTEX no se hace responsable por problemas causados por servicios externos de redirección.
 
 Consulta este otro artículo para saber cómo [configurar redirección de otras direcciones](https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ).
 
diff --git a/docs/tutorials/es/configuring-affiliates.md b/docs/tutorials/es/configuring-affiliates.md
index 90503988a..7e496ba8c 100644
--- a/docs/tutorials/es/configuring-affiliates.md
+++ b/docs/tutorials/es/configuring-affiliates.md
@@ -36,9 +36,7 @@ Para crear un nuevo ID del afiliado, realice los siguientes pasos:
 
 > Fijate que el valor **{NombreDelMarketplace}** debe ser cambiado por el nombre de la cuenta del marketplace y el valor **{IdDelSeller}** debe ser cambiado por el ID del seller registrado por el marketplace.
 
-> <div class="alert alert-danger">
-El valor <strong>{IdDelSeller}</strong> es <em>case sensitive</em>. Así, debe escribirse en la URL exactamente de la misma manera que esté registrado en el marketplace.
-</div>
+> >❗ El valor **{IdDelSeller}** es *case sensitive*. Así, debe escribirse en la URL exactamente de la misma manera que esté registrado en el marketplace.
 
 > En el caso de [marketplaces externos a VTEX](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrado-con-un-marketplace-externo), llene el campo con el valor: `https://{endpointDoAfiliado}/api/notification/`.   
 
diff --git a/docs/tutorials/es/configuring-affirm.md b/docs/tutorials/es/configuring-affirm.md
index 42e586e06..9b06c1457 100644
--- a/docs/tutorials/es/configuring-affirm.md
+++ b/docs/tutorials/es/configuring-affirm.md
@@ -19,9 +19,7 @@ subcategory:
 
 Al realizar una compra y escoger Affirm como método de pago, el comprador pasará por un análisis de crédito y, según su puntuación de crédito, la herramienta autorizará el importe a pagar por esa transacción. Así, el cliente pagará el valor directamente a Affirm con los intereses definidos al momento de aceptar.
 
-<div class="alert alert-warning">
-La aplicación Affirm se instala mediante VTEX IO, una plataforma de desarrollo <i>low-code</i> que permite a los programadores desarrollar aplicaciones y nuevos componentes para las tiendas VTEX. Acceda a la documentación <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-install">Installing VTEX IO's CLI</a> y descargue la plataforma y sus componentes antes de seguir a los próximos pasos.
-</div>
+>⚠️ La aplicación Affirm se instala mediante VTEX IO, una plataforma de desarrollo <i>low-code</i> que permite a los programadores desarrollar aplicaciones y nuevos componentes para las tiendas VTEX. Acceda a la documentación [Installing VTEX IO's CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-install) y descargue la plataforma y sus componentes antes de seguir a los próximos pasos.
 
 Para configurar Affirm, necesitará:
 
diff --git a/docs/tutorials/es/configuring-banners.md b/docs/tutorials/es/configuring-banners.md
index 5c014ca79..989e68c58 100644
--- a/docs/tutorials/es/configuring-banners.md
+++ b/docs/tutorials/es/configuring-banners.md
@@ -25,9 +25,7 @@ Para configurar un banner, sigue estos pasos:
 
 Después de configurar el banner, debes agregarlo a una página de tu tienda. Para ello, sigue los pasos del artículo [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner).
 
-<div class="alert alert-info">
-<p> Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configuración Multidioma (Beta)</a>para saber más.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo [VTEX Intelligent Search: configuración Multidioma (Beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners)para saber más.
 
 ![banner-form-es](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/ae3e6e5ffd311ad1c25e3cd7104bc874/image.png)
 
diff --git a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index 4c9f05117..077655e69 100644
--- a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -17,9 +17,7 @@ subcategory: 6bSdupUQgvuXjBL9Igawxl
 
 La importación de datos en masa simplifica el proceso de actualización y mantenimiento de información para organizaciones compradoras y sus usuarios (miembros) y centros de costo.
 
-<div class="alert alert-warning">
-Antes de configurar la funcionalidad de importación en masa, necesitas tener la aplicación <a href="https://developers.vtex.com/docs/apps/vtex.b2b-suite">B2B Suite</a> instalada en tu tienda.
-</div>
+>⚠️ Antes de configurar la funcionalidad de importación en masa, necesitas tener la aplicación [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite) instalada en tu tienda.
 
 Para importar los datos en masa a la plataforma VTEX, sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/configuring-carriers-cut-off-time.md b/docs/tutorials/es/configuring-carriers-cut-off-time.md
index 741b275cb..9fe457589 100644
--- a/docs/tutorials/es/configuring-carriers-cut-off-time.md
+++ b/docs/tutorials/es/configuring-carriers-cut-off-time.md
@@ -15,10 +15,8 @@ legacySlug: configurar-los-horarios-de-la-transportadora
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Aviso: Esta documentación está siendo actualizada con el fin de reflejar el cambio del concepto de Paneles a
-<a href="https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">Estrategia de Envío</a>.
-</div> 
+>ℹ️ Aviso: Esta documentación está siendo actualizada con el fin de reflejar el cambio del concepto de Paneles a
+> [Estrategia de Envío](https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl). 
 
 Las transportadoras, que en su Admin se denominan Política de Envío, son las empresas responsables de hacer la distribución de los productos vendidos por un comercio electrónico. Es común que una tienda tenga varias transportadoras asociadas. Esto sucede porque el perfil de operación y de flota de las **transportadoras varía según la ruta, el plazo y el tipo de producto** que va a entregar.
 
diff --git a/docs/tutorials/es/configuring-cielo-acquirer.md b/docs/tutorials/es/configuring-cielo-acquirer.md
index dabf8bf03..3521d0449 100644
--- a/docs/tutorials/es/configuring-cielo-acquirer.md
+++ b/docs/tutorials/es/configuring-cielo-acquirer.md
@@ -40,9 +40,7 @@ Para configurar Cielo, siga los pasos continuación:
     - __BPMPIAuthNotifyOnly:__ Indicar si la transacción de la tarjeta se enviará o no en modo «solo notificación» (solo válido para tarjetas Mastercard). Este modo solo es válido para tarjetas Mastercard. Para este modo, el proceso de autenticación no se activará. Sin embargo, los datos se enviarán a la red de la tarjeta de crédito.
     - __BPMpiAuthSuppressChallenge:__ Indicar si ignora o no el desafío cuando exista. Si una transacción es autorizada después de ignorar el desafío, la responsabilidad recae en el establecimiento.
 
-<div class="alert alert-warning">
-<strong>Atención</strong>: Para que ek flujo 3DS2 funcione corretamente, debes instalar la aplicación de pago cielo-authentication-app.
-</div>
+>⚠️ **Atención**: Para que ek flujo 3DS2 funcione corretamente, debes instalar la aplicación de pago cielo-authentication-app.
 
 11. En __Captura de seguridad anticipada__, escoja en cuánto tiempo desea que la captura se realice después de la aprobación de la transacción y del análisis del antifraude. También es posible desactivar esta función.
 12. Haga clic en __Salvar__ para guardar.
diff --git a/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
index 3929e3a13..00b0fad78 100644
--- a/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/es/configuring-clearsale-global-anti-fraud-solution.md
@@ -17,9 +17,7 @@ subcategory:
 
 ClearSale Global es una solución antifraude, disponible exclusivamente para el mercado internacional. Mediante el análisis del comportamiento de los clientes, la solución identifica las vulnerabilidades y previene posibles fraudes en las transacciones de su tienda.
 
-<div class="alert alert-info">
-Si está en Brasil y quiere usar ClearSale, VTEX ofrece integración con ClearSale V3, exclusiva para clientes brasileños. Acceda al tutorial <a href="https://help.vtex.com/es/tutorial/configurar-antifraude-clearsale-v3--2pPORygesIqQOa6cIG6agg?&utm_source=autocomplete">Configurar antifraude ClearSale v3</a> para realizar la configuración.
-  </div>
+>ℹ️ Si está en Brasil y quiere usar ClearSale, VTEX ofrece integración con ClearSale V3, exclusiva para clientes brasileños. Acceda al tutorial [Configurar antifraude ClearSale v3](https://help.vtex.com/es/tutorial/configurar-antifraude-clearsale-v3--2pPORygesIqQOa6cIG6agg?&utm_source=autocomplete) para realizar la configuración.
 
 Para configurar ClearSale Global, deberá:
 
diff --git a/docs/tutorials/es/configuring-clearsale-v3-antifraud.md b/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
index 378aaa90d..58817f14b 100644
--- a/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/es/configuring-clearsale-v3-antifraud.md
@@ -38,10 +38,9 @@ Para configurar ClearSaleV3 siga los pasos a continuación:
 </ul>
 7. Haga clic en `Guardar`.
 
-<div class="alert alert-info">
-<p>Si tiene una aplicación móvil que utiliza API de VTEX en el momento del pago, es necesario implementar la recolección de datos de huellas dactilares para enviarlos a Clearsale, según la plataforma utilizada por la aplicación. Obtenga más información en <a href="https://api.clearsale.com.br/docs/behavior-analytics" target="_blank">Clearsale Behavior Analytics</a>.</p>
-  <p>Con la implementación del SDK es necesario recolectar el valor de <span class="bg-muted-4">sessionId</span> y enviarlo en el <span class="bg-muted-4">deviceFingerprint</span> a través de la <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">API al momento de crear el pago</a>.</p>  
-</div>
+>ℹ️ Si tiene una aplicación móvil que utiliza API de VTEX en el momento del pago, es necesario implementar la recolección de datos de huellas dactilares para enviarlos a Clearsale, según la plataforma utilizada por la aplicación. Obtenga más información en [Clearsale Behavior Analytics](https://api.clearsale.com.br/docs/behavior-analytics" target="_blank).
+>
+> Con la implementación del SDK es necesario recolectar el valor de <span class="bg-muted-4">sessionId</span> y enviarlo en el <span class="bg-muted-4">deviceFingerprint</span> a través de la [API al momento de crear el pago](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
 
 ## Creación de la etiqueta de Google Tag Manager
 
@@ -91,6 +90,4 @@ El `shippingEstimate` puede obtenerse en los ítems de `shippingData.logisticsIn
 
 El valor de `deliverySlaInMinutes` es la conversión de `shippingEstimate` en minutos. Si la unidad es `m` (minutos) será el mismo valor, si la unidad es `h` (horas) el valor se multiplica por 60 y si la unidad es `d` (días consecutivos) o `bd` (días hábiles) el valor se multiplica por 1440. Por ejemplo, tres días consecutivos o `3d` se representa como `4320`. El `deliverySlaInMinutes` se utiliza en cada ítem del `minicart` en el cuerpo de la solicitud de los endpoints <a href="https://developers.vtex.com/vtex-rest-api/reference/antifraud-flow#sendantifraudpreanalysisdata" target="_blank">Send Antifraud Pre-Analysis Data</a> y <a href="https://developers.vtex.com/vtex-rest-api/reference/antifraud-flow#sendantifrauddata" target="_blank">Send Antifraud Data</a>.
 
-<div class="alert alert-info">
-Aunque la conversión del tiempo en días consecutivos (<code>d</code>) y días hábiles (<code>bd</code>) a minutos es igual en el campo <code>deliverySlaInMinutes</code>, la fecha de entrega puede ser diferente en función del calendario (cuando hay fines de semana y feriados en el periodo de entrega).
-</div>
+>ℹ️ Aunque la conversión del tiempo en días consecutivos (`d`) y días hábiles (`bd`) a minutos es igual en el campo `deliverySlaInMinutes`, la fecha de entrega puede ser diferente en función del calendario (cuando hay fines de semana y feriados en el periodo de entrega).
diff --git a/docs/tutorials/es/configuring-dns-pointing-to-vtex.md b/docs/tutorials/es/configuring-dns-pointing-to-vtex.md
index b7417aa0f..6ddd333a5 100644
--- a/docs/tutorials/es/configuring-dns-pointing-to-vtex.md
+++ b/docs/tutorials/es/configuring-dns-pointing-to-vtex.md
@@ -30,9 +30,7 @@ Acá estan los pasos:
 
 Antes de apuntar un dominio a VTEX, se debe garantizar el cumplimiento de los requisitos mencionados a continuación.
 
-<div class="alert alert-warning">
-Atención: si estás migrando tu tienda de <strong>Loja Integrada</strong> a VTEX, ponte en contacto con nuestro equipo de soporte antes de direccionar el DNS. Hay que liberar el dominio de Loja Integrada para que pueda ser usado con la tienda VTEX.
-</div>
+>⚠️ Atención: si estás migrando tu tienda de **Loja Integrada** a VTEX, ponte en contacto con nuestro equipo de soporte antes de direccionar el DNS. Hay que liberar el dominio de Loja Integrada para que pueda ser usado con la tienda VTEX.
 
 ### Registrar el dominio en VTEX
 
@@ -48,15 +46,11 @@ VTEX utiliza dos proveedores de CDN para las tiendas: **Cloudfront** y **Azion**
 
 Por lo tanto, si tienes el dominio de la tienda registrado en la plataforma **Cloudfront** o **Azion**, remueve el registro antes de apuntar el DNS a VTEX.
 
-<div class="alert alert-warning">
-Si no puedes remover el registro de dominio de tu tienda de la plataforma <strong>Cloudfront</strong> o <strong>Azion</strong>, ponte en contacto con el <a href="https://help.vtex.com/es/support">equipo de soporte de VTEX</a> y explícales la situación. Así, el equipo VTEX te ayudará a asegurar el buen funcionamiento de la tienda en el go-live.
-</div>
+>⚠️ Si no puedes remover el registro de dominio de tu tienda de la plataforma **Cloudfront** o **Azion**, ponte en contacto con el [equipo de soporte de VTEX](https://help.vtex.com/es/support) y explícales la situación. Así, el equipo VTEX te ayudará a asegurar el buen funcionamiento de la tienda en el go-live.
 
 ## Configurar registros CAA
 
-<div class="alert alert-warning">
-La configuración de registros CAA según se describe en esta sección, solo es necesaria si tu servidor de DNS tiene un registro CAA. Si no, pasa al tema siguiente de esta guía.
-</div>
+>⚠️ La configuración de registros CAA según se describe en esta sección, solo es necesaria si tu servidor de DNS tiene un registro CAA. Si no, pasa al tema siguiente de esta guía.
 
 Los registros CAA indican qué autoridades de certificación (CA) están autorizadas para generar y renovar los certificados que validan la identidad de tu dominio. La configuración adecuada de los registros es necesaria para poder generar los [certificados SSL](https://help.vtex.com/es/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar--tutorials_1308) y utilizar la CDN de VTEX.
 
@@ -70,9 +64,7 @@ Esto significa que la autoridad de certificación **Let's Encrypt** puede emitir
 
 Otra alternativa, aunque no recomendada, sería no incluir registros CAA en tu servidor DNS, lo que indicaría que todas las autoridades de certificación pueden emitir y renovar certificados para tu dominio.
 
-<div class="alert alert-info">
-Puede que estos tipos de entrada no estén disponibles en la interfaz de tu gestor de DNS; sin embargo, muchas veces es posible gestionarlos a través de llamadas en el soporte de la herramienta específica.
-</div>
+>ℹ️ Puede que estos tipos de entrada no estén disponibles en la interfaz de tu gestor de DNS; sin embargo, muchas veces es posible gestionarlos a través de llamadas en el soporte de la herramienta específica.
 
 Para facilitar el trabajo de crear y verificar tus registros CAA, puedes utilizar [CAA Record Helper de SSLMate](https://sslmate.com/caa/). El programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) también puede ayudar a verificar los registros mediante el comando `dig domain.com CAA`; el status `SERVFAIL` puede indicar que tu servidor DNS no está en cumplimiento.
 
@@ -114,9 +106,7 @@ En la zona de DNS de tu dominio, debes crear una entrada de tipo CNAME en el sub
 
 Ten en cuenta que el `{dominio}` indicado anteriormente debe ser el mismo que [registraste en VTEX](#registrar-el-dominio-en-vtex).
 
-<div class="alert alert-warning">
-Si utilizas Cloudflare como zona de DNS, puede que tengas que desactivar el proxy de DNS y, por lo tanto, desactivar los servicios de CDN y WAF de Cloudflare. Puedes ver más información en el artículo <a href="https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">Cómo desactivar el proxy de Cloudflare</a>.
-</div>
+>⚠️ Si utilizas Cloudflare como zona de DNS, puede que tengas que desactivar el proxy de DNS y, por lo tanto, desactivar los servicios de CDN y WAF de Cloudflare. Puedes ver más información en el artículo [Cómo desactivar el proxy de Cloudflare](https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 ## Generar el certificado SSL
 
@@ -132,9 +122,7 @@ El certificado es generado vía [Let's Encrypt](https://letsencrypt.org/) y es v
 
 ---
 
-<div class="alert alert-info">
-La propagación del apuntamiento de DNS toma entre 24 y 48 horas en ocurrir completamente, esto significa que la dirección configurada puede no estar disponible justo luego de configurar todo correctamente.
-</div>
+>ℹ️ La propagación del apuntamiento de DNS toma entre 24 y 48 horas en ocurrir completamente, esto significa que la dirección configurada puede no estar disponible justo luego de configurar todo correctamente.
 
 Las instrucciones de arriba tienen que ver exclusivamente con el apuntamiento del dominio primario a su tienda VTEX. Es importante que si su tienda tiene otros dominios, ellos sean redirigidos a un dominio primario único. 
 
diff --git a/docs/tutorials/es/configuring-domains-in-account-management.md b/docs/tutorials/es/configuring-domains-in-account-management.md
index 3231991b7..de6bcb2d8 100644
--- a/docs/tutorials/es/configuring-domains-in-account-management.md
+++ b/docs/tutorials/es/configuring-domains-in-account-management.md
@@ -17,15 +17,13 @@ subcategory: yMp6sKDiJEi66CGAIQ4ma
 
 La configuración de dominios es necesaria para que la URL accedida sea correctamente direccionada a una tienda VTEX. A continuación puede aprender cómo [registrar un nuevo dominio](#registrar-nuevo-dominio) o [cambiar el dominio de una tienda activa](#cambiar-dominio-de-tienda).
 
-<div class="alert alert-danger">
-En caso de que su operación tenga más de una cuenta o subcuentas VTEX, no intercambie dominios entre ellas. Esto provocará errores en diferentes aspectos de tu tienda.
-</div>
+>❗ En caso de que su operación tenga más de una cuenta o subcuentas VTEX, no intercambie dominios entre ellas. Esto provocará errores en diferentes aspectos de tu tienda.
 
-<div class="alert alert-warning">
-Si agregas más de un dominio como host de tu tienda, todos ellos mostrarán el mismo contenido. Sin embargo, recomendamos registrar solo un dominio y utilizar redirecciones para los demás. Obtenga más información sobre redirecciones:
-<ul><li><a href=”https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirección de otras direcciones</a></li>
-  <li><a href=”https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acceso sin www</a></li></ul> 
-</div>
+>⚠️ Si agregas más de un dominio como host de tu tienda, todos ellos mostrarán el mismo contenido. Sin embargo, recomendamos registrar solo un dominio y utilizar redirecciones para los demás. Obtenga más información sobre redirecciones:
+>
+> *<a href=”https://help.vtex.com/es/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirección de otras direcciones</a>
+>
+> * <a href=”https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acceso sin www</a>
 
 ## Subdominio
 
diff --git a/docs/tutorials/es/configuring-ideal-payment-method-in-adyen-integration.md b/docs/tutorials/es/configuring-ideal-payment-method-in-adyen-integration.md
index 6292ccc03..2a012c732 100644
--- a/docs/tutorials/es/configuring-ideal-payment-method-in-adyen-integration.md
+++ b/docs/tutorials/es/configuring-ideal-payment-method-in-adyen-integration.md
@@ -19,10 +19,8 @@ __iDEAL__ es un medio de pago en línea disponible solo para los clientes de los
 
 En este tutorial, podrá consultar los pasos para configurarlo en su tienda a través de la integración con [Adyen](https://help.vtex.com/es/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337).
 
-<div class="alert alert-danger">
-  <div>Por el momento, <b>Adyen</b> es el único partner que acepta pagos con iDEAL. Por lo tanto, debe ponerse en contacto con Adyen para saber si iDEAL está disponible en su localidad.
-<p>Si lo está, consulte el artículo <a href="https://help.vtex.com/es/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337">Configurar el gateway Adyen en VTEX</a> y configure la afiliación en su tienda.
-  </div>
+>❗ <div>Por el momento, **Adyen** es el único partner que acepta pagos con iDEAL. Por lo tanto, debe ponerse en contacto con Adyen para saber si iDEAL está disponible en su localidad.
+> <p>Si lo está, consulte el artículo [Configurar el gateway Adyen en VTEX](https://help.vtex.com/es/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337) y configure la afiliación en su tienda.
 
 1. Inicie sesión en el _Admin_ VTEX. 
 2. Haga clic en __Pagos__ > __Configuración__. 
diff --git a/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
index faadeb13e..1acdcbc08 100644
--- a/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/es/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -19,9 +19,7 @@ En este artículo, se explicará cómo configurar el recurso del tiempo máximo
 
 Antes de comenzar con el procedimiento, es importante aclarar la diferencia entre la __liquidación por facturación__, la __liquidación automática__ y la __liquidación anticipada__, tres conceptos presentes en el mercado de pagos. En algunos conectores de pagos de plataforma, estos términos se conocen como __captura por facturación__, __captura anticipada__ y __captura automática__.
 
-<div class="alert alert-warning">
-La siguiente información es válida para los pagos con tarjeta de crédito.
-</div>
+>⚠️ La siguiente información es válida para los pagos con tarjeta de crédito.
 
 ## liquidación por facturación
 La liquidación por facturación es una de las etapas del [flujo de la transacción](https://help.vtex.com/es/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ# "flujo de la transacción"), el proceso interno de VTEX que ocurre después de que un cliente realiza el pago de un pedido. Es decir, el cliente no participa en esta dinámica.
@@ -42,9 +40,7 @@ Cuando el proceso de autorización inicia, el sistema espera un tiempo máximo,
 
 El administrador de la tienda y el adquirente establecen el límite de tiempo para que se active la liquidación automática.
 
-<div class="alert alert-info">
-Generalmente, el tiempo máximo predeterminado para que la liquidación ocurra es de cuatro días. Sin embargo, esto <strong>no</strong> es una regla. Cada adquirente puede definir el tiempo que considere más apropiado.
-</div>
+>ℹ️ Generalmente, el tiempo máximo predeterminado para que la liquidación ocurra es de cuatro días. Sin embargo, esto **no** es una regla. Cada adquirente puede definir el tiempo que considere más apropiado.
 
 Para configurar esta liquidación, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
index 56f548b03..666d239e2 100644
--- a/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/es/configuring-mercado-pagos-device-fingerprint.md
@@ -19,9 +19,7 @@ __Device Fingerprint__ es un identificador que actúa en el procesamiento de un
 
 Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
 
 En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliación Mercado Pago.
 
diff --git a/docs/tutorials/es/configuring-openpay-payment-gateway.md b/docs/tutorials/es/configuring-openpay-payment-gateway.md
index 90079881f..e53c4d790 100644
--- a/docs/tutorials/es/configuring-openpay-payment-gateway.md
+++ b/docs/tutorials/es/configuring-openpay-payment-gateway.md
@@ -17,9 +17,7 @@ subcategory:
 
 [Openpay](https://www.openpay.mx/) es un procesador de pagos en línea que permite recibir pagos realizados con tarjetas de crédito, efectivo y transferencias bancarias.
 
-<div class="alert alert-warning">
-  Antes de realizar la configuración, debe haber creado y verificado una cuenta de Openpay. Si aún no se ha registrado, <a href="https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false">haga clic aquí</a> y cree su cuenta.
-  </div>
+>⚠️ Antes de realizar la configuración, debe haber creado y verificado una cuenta de Openpay. Si aún no se ha registrado, [haga clic aquí](https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false) y cree su cuenta.
 
 Para configurar Openpay, necesitará:
 
diff --git a/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index 2c809ff5b..c4991bb8b 100644
--- a/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/es/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 En VTEX, es posible integrarse con el proveedor de pago Adyen. A través de este conector, su tienda puede ofrecer transacciones de pago en tiendas físicas (VTEX Sales App), utilizando puntos de venta (POS). Para más información acceda [¿Qué es VTEX Sales App?](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf).
 
-<div class="alert alert-info">
-Para utilizar la afiliación AdyenV3 en su tienda a través de otros canales de venta en línea (excepto VTEX Sales App), visite <a href="https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3--7xAz67E2Eg63LWCQNjVdwv">Configurar pagos con AdyenV3</a>.
-</div>
+>ℹ️ Para utilizar la afiliación AdyenV3 en su tienda a través de otros canales de venta en línea (excepto VTEX Sales App), visite [Configurar pagos con AdyenV3](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3--7xAz67E2Eg63LWCQNjVdwv).
 
 Para utilizar la afiliación AdyenV3 en la VTEX Sales App, es necesario:
 
@@ -28,9 +26,7 @@ Para utilizar la afiliación AdyenV3 en la VTEX Sales App, es necesario:
 - [Configurar el conector AdyenV3 (VTEX Sales App) en VTEX](#configurar-el-conector-adyenv3-vtex-sales-app-en-vtex)
 - [Configurar condición de pago](#configurar-condicion-de-pago)
 
-<div class="alert alert-warning">
-La configuración realizada en un entorno externo a VTEX puede interrumpirse o modificarse sin previo aviso. Consulta tu cuenta Adyen para obtener información actualizada.
-</div>
+>⚠️ La configuración realizada en un entorno externo a VTEX puede interrumpirse o modificarse sin previo aviso. Consulta tu cuenta Adyen para obtener información actualizada.
 
 ## Configurar punto de venda (POS)
 
@@ -100,9 +96,7 @@ Configura el webhook según los pasos a continuación:
 
 ![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
-<div class="alert alert-info">
-Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
-</div>
+>ℹ️ Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
 
 ## Configurar el conector AdyenV3 (VTEX Sales App) en VTEX
 
diff --git a/docs/tutorials/es/configuring-payment-with-adyenv3.md b/docs/tutorials/es/configuring-payment-with-adyenv3.md
index 6dec40150..1e72966f3 100644
--- a/docs/tutorials/es/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/es/configuring-payment-with-adyenv3.md
@@ -22,13 +22,9 @@ Para utilizar la afiliación AdyenV3, debes:
 - [Configurar el entorno Adyen](#configurar-el-entorno-adyen)
 - [Configurar el conector AdyenV3 en VTEX](#configurar-el-conector-adyenv3-en-vtex)
 
-<div class="alert alert-warning">
-La configuración realizada en un entorno externo a VTEX puede interrumpirse o modificarse sin previo aviso. Consulta tu cuenta Adyen para obtener información actualizada.
-</div>
+>⚠️ La configuración realizada en un entorno externo a VTEX puede interrumpirse o modificarse sin previo aviso. Consulta tu cuenta Adyen para obtener información actualizada.
 
-<div class="alert alert-info">
-Para utilizar la afiliación AdyenV3 a través de <a href="https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf">Sales App</a> en tus tiendas físicas (puntos de ventas), ve a <a href="https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3-en-vtex-sales-app--24yO6KloBn6DN6CbprHtgt">Configurar pago con AdyenV3 en Sales App</a>.
-</div>
+>ℹ️ Para utilizar la afiliación AdyenV3 a través de [Sales App](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) en tus tiendas físicas (puntos de ventas), ve a [Configurar pago con AdyenV3 en Sales App](https://help.vtex.com/es/tutorial/configurar-pagos-con-adyenv3-en-vtex-sales-app--24yO6KloBn6DN6CbprHtgt).
 
 ## Configurar el entorno Adyen
 
@@ -51,9 +47,7 @@ Para habilitar el acceso de VTEX en el entorno Adyen, sigue los pasos a continua
 
 ### Obtener la API Key y la Client Key
 
-<div class="alert alert-warning">
-La información a continuación supone que la API Key y la Client Key se han generado previamente en el entorno de Adyen. En caso de que necesites crearlas, consulta la documentación de <a href="https://docs.adyen.com/">Adyen</a>.
-</div>
+>⚠️ La información a continuación supone que la API Key y la Client Key se han generado previamente en el entorno de Adyen. En caso de que necesites crearlas, consulta la documentación de [Adyen](https://docs.adyen.com/).
 
 1. Haz clic en __Developers__ en la barra lateral y luego en __API credentials__.
 2. Selecciona tu credencial API.
@@ -95,9 +89,7 @@ Configura el webhook según los pasos a continuación:
 
 ![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
-<div class="alert alert-info">
-Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
-</div>
+>ℹ️ Si tienes varias tiendas, es necesario configurar el webhook para cada una de ellas.
 
 ## Configurar el conector AdyenV3 en VTEX
 
@@ -124,9 +116,7 @@ Si desea procesar pagos con tarjeta de crédito en su tienda utilizando AdyenV3,
 
 En el ticket también deberás enviar la URL que será autorizada por Adyen para realizar la transacción con tarjeta de crédito en tu tienda. El formato de la URL debe ser `https://{live URL prefix}-checkout-live.adyenpayments.com`, donde la información "{live URL prefix}" debe ser la misma que la ingresada por usted en las configuraciones de Adyen en el VTEX Admin .  
 
-<div class="alert alert-warning">
-La dirección URL completa debe escribirse únicamente en letras minúsculas, incluso si el "Live URL prefix" configurado en el VTEX Admin tiene algunas letras mayúsculas.
-</div>  
+>⚠️ La dirección URL completa debe escribirse únicamente en letras minúsculas, incluso si el "Live URL prefix" configurado en el VTEX Admin tiene algunas letras mayúsculas.  
 
 ## Configurar el pago con Apple Pay en Adyen (opcional) 
 
diff --git a/docs/tutorials/es/configuring-price-divergence-rule.md b/docs/tutorials/es/configuring-price-divergence-rule.md
index aaabe3953..34e94a42b 100644
--- a/docs/tutorials/es/configuring-price-divergence-rule.md
+++ b/docs/tutorials/es/configuring-price-divergence-rule.md
@@ -71,9 +71,7 @@ Para crear la **segunda regla**, haz clic en el `<img class="shadow-4" src="http
 
 Configura la nueva regla de autorización y, después de definir todas las reglas que desees, haz clic en el botón **GUARDAR REGLAS**. Verás el siguiente mensaje: _Después de guardar las reglas, puedes editarlas o eliminarlas cuando quieras_. Haz clic en **OK** para confirmar. Una vez que hayas hecho esto, se creará la regla de divergencia de precios.
 
-<div class="alert alert-warning">
-Después de que hayas configurado la regla de divergencia de precios, esta se aplicará a todos los <i>marketplaces</i> en los que actúes como seller.
-</div>
+>⚠️ Después de que hayas configurado la regla de divergencia de precios, esta se aplicará a todos los <i>marketplaces</i> en los que actúes como seller.
 
 ## Editar una regla de divergencia de precios
 
@@ -95,9 +93,7 @@ Una vez que hayas hecho los cambios deseados, haz clic en el botón **GUARDAR RE
 
 Cuando una regla de autorización se configura con la opción _Crear una tarea en VTEX DO para aprobación_, esto significa que se ha asignado al menos un usuario para autorizar manualmente el pedido. La [gestión de pedidos con divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW#gestion-de-pedidos-con-divergencia-de-precios) es similar a la de otros canales de venta, como la tienda física o el ecommerce.
 
-<div class="alert alert-warning">
-Es importante hacer un seguimiento regular de los pedidos en <b>Pedidos > Todos los pedidos</b>. Si requieren aprobación manual, los pedidos con errores de divergencia de precios quedan pendientes de autorización por parte de un usuario habilitado, definido al crear la regla de autorización. Una buena práctica es tener al menos dos usuarios con autorización para realizar el procesamiento manual.
-</div>
+>⚠️ Es importante hacer un seguimiento regular de los pedidos en **Pedidos > Todos los pedidos**. Si requieren aprobación manual, los pedidos con errores de divergencia de precios quedan pendientes de autorización por parte de un usuario habilitado, definido al crear la regla de autorización. Una buena práctica es tener al menos dos usuarios con autorización para realizar el procesamiento manual.
 
 Hay dos maneras de autorizar manualmente un pedido con divergencia de precios:
 
diff --git a/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
index ba3907bc6..aae7f1814 100644
--- a/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
+++ b/docs/tutorials/es/configuring-seller-allocation-for-buying-xky.md
@@ -44,8 +44,6 @@ Para asignar sellers a una determinada organización compradora sigue los pasos
 A partir de ahora, cada vez que la organización realice una búsqueda en la plataforma VTEX, solamente se mostrarán los productos de los sellers que tenga asignados.
 </ol>
 
-<div class="alert alert-warning">
-Las organizaciones compradoras que opten por no crear asignaciones de sellers, podrán acceder igualmente a la información y realizar compras a todos los sellers disponibles en el marketplace.
-</div>
+>⚠️ Las organizaciones compradoras que opten por no crear asignaciones de sellers, podrán acceder igualmente a la información y realizar compras a todos los sellers disponibles en el marketplace.
 
 Para más información sobre cómo integrar un nuevo seller, consulta el artículo [Agregar seller](https://help.vtex.com/es/tutorial/adicionar-seller--tutorials_392).
diff --git a/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
index a6ae4697d..85b100722 100644
--- a/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
+++ b/docs/tutorials/es/configuring-sign-in-with-apple-id-beta.md
@@ -15,9 +15,7 @@ legacySlug: configurar-inicio-de-sesion-con-apple-id-beta
 subcategory: 5uXA9a0laSLMkfbv6jQRDS
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support).
 
 En VTEX, no es necesario crear una cuenta o iniciar sesión para realizar una compra. Sin embargo, si el cliente desea editar los datos informados durante la primera compra, debe comprobar que el email en cuestión le pertenece.
 
@@ -72,9 +70,7 @@ Ahora que todo está listo, puedes probar la configuración. Recomendamos que re
 4. Completa la autenticación de dos factores, si se te solicita.
 5. Escoge si deseas compartir tu email con la aplicación u [Ocultar mi correo](https://support.apple.com/es-mx/HT210425) y haz clic en `Continuar`. Recomendamos compartir el email, ya que hay [limitaciones](#limitaciones) respecto al email oculto en VTEX.
 
-<div class="alert alert-info">
-  <p>La opción de compartir u ocultar el email solo aparece la primera vez que se accede a la tienda con el Apple ID. Después, solo es necesario hacer clic en <code>Continuar</code>. Para redefinir la opción de compartir el email, accede a la <a href="https://appleid.apple.com/mx/">página de administración de Apple ID</a>, revoca la autorización de la tienda y vuelve a iniciar sesión.</p>
-</div>
+>ℹ️ La opción de compartir u ocultar el email solo aparece la primera vez que se accede a la tienda con el Apple ID. Después, solo es necesario hacer clic en `Continuar`. Para redefinir la opción de compartir el email, accede a la [página de administración de Apple ID](https://appleid.apple.com/mx/), revoca la autorización de la tienda y vuelve a iniciar sesión.
 
 Luego de eso, estarás autenticado en la tienda.
 
diff --git a/docs/tutorials/es/configuring-spin-pay-gateway.md b/docs/tutorials/es/configuring-spin-pay-gateway.md
index 4dd21eb90..ef86f42a2 100644
--- a/docs/tutorials/es/configuring-spin-pay-gateway.md
+++ b/docs/tutorials/es/configuring-spin-pay-gateway.md
@@ -17,9 +17,7 @@ subcategory:
 
 En VTEX, ahora puede ofrecer el *gateway* [Spin Pay](https://spinpay.com.br/) para procesar los pagos en su tienda. A través de esta solución, podrá recibir pagos vía PIX (método de pago instantáneo en Brasil) y las principales billeteras digitales que actualmente están disponibles en el mercado. 
 
-<div class="alert alert-warning">
-  Para utilizar Spin Pay en VTEX, debe tener una <b>Application Key (App Key)</b> y una <b>Application Token (App Token)</b>. Estos datos únicamente se obtienen después de que Spin Pay aprueba su registro y usted firma el contrato de prestación de servicios. Si su registro ya ha sido aprobado y el contrato firmado, realice los siguientes pasos.
-   </div>
+>⚠️ Para utilizar Spin Pay en VTEX, debe tener una **Application Key (App Key)** y una **Application Token (App Token)**. Estos datos únicamente se obtienen después de que Spin Pay aprueba su registro y usted firma el contrato de prestación de servicios. Si su registro ya ha sido aprobado y el contrato firmado, realice los siguientes pasos.
 
 Realice los siguientes pasos para configurar Spin Pay en su tienda:
 
@@ -49,9 +47,7 @@ Cuando el gateway está instalado en su tienda, debe configurar la [condición d
 9. En __Usando Antifraude__, en caso de que haya contratado una solución, habilite el campo y seleccione la opción deseada.
 10. Haga clic en __Salva__ para guardar las configuraciones.
 
-<div class="alert alert-warning">
-  Spin Pay es una solución brasileña de pago instantáneo en la que el débito se efectúa directamente en la cuenta del consumidor. Por esta razón, no es posible ofrecer pagos en cuotas.
-   </div>
+>⚠️ Spin Pay es una solución brasileña de pago instantáneo en la que el débito se efectúa directamente en la cuenta del consumidor. Por esta razón, no es posible ofrecer pagos en cuotas.
 
 Cuando concluya todos los pasos, Spin Pay estará habilitado para procesar los pagos en su tienda.
 
diff --git a/docs/tutorials/es/configuring-stripe-gateway-affiliation.md b/docs/tutorials/es/configuring-stripe-gateway-affiliation.md
index 6478b07a1..d82123b3d 100644
--- a/docs/tutorials/es/configuring-stripe-gateway-affiliation.md
+++ b/docs/tutorials/es/configuring-stripe-gateway-affiliation.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 [Stripe](https://stripe.com/es) es una plataforma de pago que ofrece un sistema integrado enfocado en la recepción de pagos, transferencias, donaciones y cualquier tipo de transacción financiera habitual en los ecommerce y otras páginas web.
 
-<div class="alert alert-warning">
-La integración de tu tienda con Stripe se realiza a través de <strong>Application Key</strong> y <strong>Application Token</strong>. Para obtener estos datos, primero debes <a href="https://dashboard.stripe.com/register" target="_blank">crear tu cuenta</a> en la plataforma y. Cuando hayas terminado, accede a <a href="https://stripe.com/docs/keys" target="_blank">esta documentación</a> de Stripe para obtener acceso a tu <strong>clave publicable</strong> y <strong>clave secreta</strong>. Estas claves son obligatorias para las configuraciones en la plataforma VTEX.
-</div>
+>⚠️ La integración de tu tienda con Stripe se realiza a través de **Application Key** y **Application Token**. Para obtener estos datos, primero debes [crear tu cuenta](https://dashboard.stripe.com/register" target="_blank) en la plataforma y. Cuando hayas terminado, accede a [esta documentación](https://stripe.com/docs/keys" target="_blank) de Stripe para obtener acceso a tu **clave publicable** y **clave secreta**. Estas claves son obligatorias para las configuraciones en la plataforma VTEX.
 
 Stripe admite pagos en más de 40 países. Se puede acceder a la lista de países disponibles en el [sitio web de Stripe](https://stripe.com/es/enterprise).
 
@@ -56,12 +54,13 @@ Después de realizar la configuración en el ambiente VTEX, también debes confi
 8. Haga clic en __Añadir eventos__.
 9. Haga clic en __Añadir punto de conexión__.
 
-<div class="alert alert-info">
-  <p>Si deseas realizar transacciones con tarjeta de crédito en Stripe, debes abrir un ticket en Stripe de la siguiente manera:</p>
-  <p>- Solicitar la liberación de la función "raw card data", indicando que VTEX y Stripe son socios de pago.</p>
-  <p>- Enviar como archivo adjunto el VTEX AOC (Attestation of Compliance for Onsite Assessments – Service Providers). Para consultar la última versión de AOC VTEX acceda a la página de <a href="https://vtex.com/es-es/compliance/certifications">certificaciones VTEX</a> y descargue el archivo disponible en la sección PCI.</p>
-  <p>Las acciones anteriores evitarán que ocurran errores relacionados con la transmisión de datos sensibles en la integración entre Stripe y VTEX.</p>
-</div>
+>ℹ️ Si deseas realizar transacciones con tarjeta de crédito en Stripe, debes abrir un ticket en Stripe de la siguiente manera:
+>
+> - Solicitar la liberación de la función "raw card data", indicando que VTEX y Stripe son socios de pago.
+>
+> - Enviar como archivo adjunto el VTEX AOC (Attestation of Compliance for Onsite Assessments – Service Providers). Para consultar la última versión de AOC VTEX acceda a la página de [certificaciones VTEX](https://vtex.com/es-es/compliance/certifications) y descargue el archivo disponible en la sección PCI.
+>
+> Las acciones anteriores evitarán que ocurran errores relacionados con la transmisión de datos sensibles en la integración entre Stripe y VTEX.
 
 ## Configuración de condición de pago
 
@@ -86,9 +85,7 @@ Cuando hayas realizado estos pasos, Google Pay figurará en el *checkout* de la
 
 El conector Stripe te permite añadir Apple Pay como método de pago en el checkout de tu tienda.
 
-<div class="alert alert-warning">
-Apple Pay actualmente solo funciona en los sistemas operativos MacOs e IOS, y el navegador Safari. Para más información acceda a <a href="https://support.apple.com/es-es/HT208531">Dispositivos compatibles con Apple Pay</a>.
-</div>
+>⚠️ Apple Pay actualmente solo funciona en los sistemas operativos MacOs e IOS, y el navegador Safari. Para más información acceda a [Dispositivos compatibles con Apple Pay](https://support.apple.com/es-es/HT208531).
 
 Con el conector Stripe configurado, puedes añadir Apple Pay siguiendo los pasos que se indican a continuación:
 
diff --git a/docs/tutorials/es/configuring-telesales-features.md b/docs/tutorials/es/configuring-telesales-features.md
index 921712c57..e91efa975 100644
--- a/docs/tutorials/es/configuring-telesales-features.md
+++ b/docs/tutorials/es/configuring-telesales-features.md
@@ -62,7 +62,5 @@ Para ello, los desarrolladores de la tienda deben habilitar la funcionalidad de
 
 Los precios manuales registrados en el carrito deben ser aprobados por el administrador de la tienda o por un usuario con permiso de [Autorización de pedidos](https://help.vtex.com/es/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn) en el sistema para que el pedido siga el flujo de facturación.
 
-<div class="alert alert-info">
-No es posible modificar los precios accediendo a la tienda a través de su URL final (<i>www.dominiotienda.com.br</i>). La funcionalidad de precio manual en televenta solo funciona si el operador accede a la tienda a través del dominio <i>www.dominiotienda.myvtex.com</i> y tiene el permiso de <a href="https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator">Call Center operator</a> en su <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">Perfil de Acceso</a>. 
-</div>
+>ℹ️ No es posible modificar los precios accediendo a la tienda a través de su URL final (<i>www.dominiotienda.com.br</i>). La funcionalidad de precio manual en televenta solo funciona si el operador accede a la tienda a través del dominio <i>www.dominiotienda.myvtex.com</i> y tiene el permiso de [Call Center operator](https://help.vtex.com/es/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator) en su [Perfil de Acceso](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
 
diff --git a/docs/tutorials/es/configuring-the-global-checkout.md b/docs/tutorials/es/configuring-the-global-checkout.md
index c0cd7ac82..b70a9309a 100644
--- a/docs/tutorials/es/configuring-the-global-checkout.md
+++ b/docs/tutorials/es/configuring-the-global-checkout.md
@@ -58,9 +58,7 @@ Supones que tu queiras enviar para clientes en Reino Unido. Para eso, es necesar
 1. [Creación de nueva transportadora](/es/tutorial/gestionar-transportista/);
 2. Crea, para la nueva transportadora, una planilla de envío con la columna “Country” con el código ISO de 3 digito del país deseado.
 
-<div class="alert alert-info">
-El valor de la columna “Country” debe ser un código ISO de 3 digitos para países. Para consultar los códigos aceitos, sugerimos usar el sítio<a href="https://countrycode.org/">https://countrycode.org/</a>.
-</div>
+>ℹ️ El valor de la columna “Country” debe ser un código ISO de 3 digitos para países. Para consultar los códigos aceitos, sugerimos usar el sítio[https://countrycode.org/](https://countrycode.org/).
 
 Después de la configuración de envío para los países que desea, un nuevo campo será exhibido en el formulario de envío en el checkout de la tienda, permitiendo al usuario elegir la opción de envío internacional deseada.
 
diff --git a/docs/tutorials/es/configuring-the-pickup-in-store.md b/docs/tutorials/es/configuring-the-pickup-in-store.md
index 60f20fb0f..a0ba1f171 100644
--- a/docs/tutorials/es/configuring-the-pickup-in-store.md
+++ b/docs/tutorials/es/configuring-the-pickup-in-store.md
@@ -15,9 +15,7 @@ legacySlug: como-configurar-la-retirada-en-la-tienda-pickup-store
 subcategory: 1c5Btie9ou2Gg2iUo0ggqM
 ---
 
-<div class="alert alert-danger">
-Este artículo está obsoleto. Para configurar correctamente el punto de retirada, acceda al artículo <a href="https://help.vtex.com/es/tutorial/configurar-puntos-de-recogida-pickup-points">Configurar Puntos de Recogida (Pickup Points)</a>
-</div>
+>❗ Este artículo está obsoleto. Para configurar correctamente el punto de retirada, acceda al artículo [Configurar Puntos de Recogida (Pickup Points)](https://help.vtex.com/es/tutorial/configurar-puntos-de-recogida-pickup-points)
 
 La configuración de retirada en la tienda permite que el cliente opte por no recibir el producto en casa, sino que lo irá a buscar en una tienda. Con los pasos abajo es posible darle al cliente la opción de elegir la tienda donde desea retirar su compra en el checkout, durante el flujo de compra. La configuración se realiza en 3 módulos diferentes de la de la plataforma, descritos abajo.
 
diff --git a/docs/tutorials/es/configuring-the-rede-acquirer.md b/docs/tutorials/es/configuring-the-rede-acquirer.md
index 929611301..3872b88eb 100644
--- a/docs/tutorials/es/configuring-the-rede-acquirer.md
+++ b/docs/tutorials/es/configuring-the-rede-acquirer.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 En VTEX, es posible realizar la integración con el adquirente Rede. Configurando el conector __ERedev2__, su tienda podrá aceptar pagos con tarjetas de las principales redes.
 
-<div class="alert alert-info">
-<strong>Atención</strong>: actualmente, Rede cuenta con una versión más actualizada de su conector. Para saber más detalles de cómo configurar este adquirente, consulte el artículo sobre [ERedeREST](https://help.vtex.com/es/tutorial/configurar-adquirente-rede-con-erederest?locale=es "ERedeREST").
-</div>
+>ℹ️ **Atención**: actualmente, Rede cuenta con una versión más actualizada de su conector. Para saber más detalles de cómo configurar este adquirente, consulte el artículo sobre [ERedeREST](https://help.vtex.com/es/tutorial/configurar-adquirente-rede-con-erederest?locale=es "ERedeREST").
 
 Para configurar Rede, realice los siguientes pasos:
 
diff --git a/docs/tutorials/es/configuring-the-scheduled-delivery.md b/docs/tutorials/es/configuring-the-scheduled-delivery.md
index eb1a73936..b1e47441f 100644
--- a/docs/tutorials/es/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/es/configuring-the-scheduled-delivery.md
@@ -15,9 +15,7 @@ legacySlug: como-se-maneja-la-entrega-programada
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a <a href="https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envío</a>.
-</div>  
+>ℹ️ Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a [estratégia de envío](https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).  
 
 La entrega programada es un tipo de entrega que permite definir períodos de entrega personalizados, pudiendo definir plazos y precios específicos, y también permitir que el cliente elija el período que desea recibir su pedido. 
 
diff --git a/docs/tutorials/es/configuring-the-store-domain.md b/docs/tutorials/es/configuring-the-store-domain.md
index d0dd91f88..ca6f9ac14 100644
--- a/docs/tutorials/es/configuring-the-store-domain.md
+++ b/docs/tutorials/es/configuring-the-store-domain.md
@@ -81,13 +81,9 @@ Para registrar un nuevo host, el mismo debe cumplir con las prácticas descritas
 
 Después de estos pasos, puedes [configurar el apuntamiento de DNS a VTEX](https://help.vtex.com/es/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-  <p>Para las tiendas<a href="https://www.faststore.dev/"> FastStore</a>, también es necesario configurar una dirección con el subdominio <code>secure</code>. Para más información, consulta la guía <a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns">Configuring external DNS for a custom domain</a>.</p>
-</div>
+>⚠️ Para las tiendas[ FastStore](https://www.faststore.dev/), también es necesario configurar una dirección con el subdominio `secure`. Para más información, consulta la guía [Configuring external DNS for a custom domain](https://www.faststore.dev/docs/go-live/2-configuring-external-dns).
 
-<div class="alert alert-danger">
-  <p>Si tu operación tiene más de una cuenta VTEX o <a href="https://help.vtex.com/es/tutorial/crear-subconta-multitienda-multidominio--tutorials_510">subcuentas</a>, no cambies el host de una cuenta a otra. Esto causará fallas en varias partes de tu tienda.</p>
-</div>
+>❗ Si tu operación tiene más de una cuenta VTEX o [subcuentas](https://help.vtex.com/es/tutorial/crear-subconta-multitienda-multidominio--tutorials_510), no cambies el host de una cuenta a otra. Esto causará fallas en varias partes de tu tienda.
 
 ## Cambiar host
 
diff --git a/docs/tutorials/es/configuring-tuna-gateway-affiliation.md b/docs/tutorials/es/configuring-tuna-gateway-affiliation.md
index 471b1c9ef..eed51b992 100644
--- a/docs/tutorials/es/configuring-tuna-gateway-affiliation.md
+++ b/docs/tutorials/es/configuring-tuna-gateway-affiliation.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 En VTEX, puede configurar su tienda con el gateway Tuna para recibir pagos a través de: boleto, tarjetas de débito y crédito, PIX y Bitcoin.
 
-<div class="alert alert-warning">
-  La integración de su tienda con Tuna se realiza a través de una <b>Application Key</b> y un <b>Application Token.</b> Los datos de acceso para obtener esta información y habilitar la configuración en VTEX se le enviarán después de crear su cuenta. Para esto, debe rellenar <a href="https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform">este formulario</a> y esperar la respuesta de Tuna con más detalles.
-  </div>
+>⚠️ La integración de su tienda con Tuna se realiza a través de una **Application Key** y un **Application Token.** Los datos de acceso para obtener esta información y habilitar la configuración en VTEX se le enviarán después de crear su cuenta. Para esto, debe rellenar [este formulario](https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform) y esperar la respuesta de Tuna con más detalles.
 
 Después de crear su cuenta y obtener la __Application Key__ y el __Application Token__, siga los pasos a continuación para configurar Tuna en su tienda:
 
diff --git a/docs/tutorials/es/configuring-vtex-marketplace.md b/docs/tutorials/es/configuring-vtex-marketplace.md
index 88bd2e1ac..bad4d2771 100644
--- a/docs/tutorials/es/configuring-vtex-marketplace.md
+++ b/docs/tutorials/es/configuring-vtex-marketplace.md
@@ -83,9 +83,7 @@ Un _marketplace_ puede obtener la información de ubicación del usuario en el _
 
 Incluso cuando VTEX Session no tiene acceso a la ubicación del consumidor, sigue siendo necesario orientar un surtido de productos de los _sellers_ en la experiencia de compra. En este caso, el algoritmo de selección de _sellers_ indica [sellers de extensa cobertura](https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI) que pueden entregar pedidos en todas las regiones atendidas por tu _marketplace_.
 
-<div class="alert alert-info">
-La funcionalidad Region solo está adaptada a las tiendas que utilizan VTEX IO, y no es válida para el Portal CMS Legado. 
-</div>
+>ℹ️ La funcionalidad Region solo está adaptada a las tiendas que utilizan VTEX IO, y no es válida para el Portal CMS Legado.
 
 ## Configurar storefront
 
diff --git a/docs/tutorials/es/configuring-xml.md b/docs/tutorials/es/configuring-xml.md
index 4ff5c03d7..91b99572c 100644
--- a/docs/tutorials/es/configuring-xml.md
+++ b/docs/tutorials/es/configuring-xml.md
@@ -61,9 +61,7 @@ Con esto en manos, siga los siguientes pasos para configurar su XML:
 13.A partir de aquí debe rellenar los tags según lo definido por el sistema al que enviará el XML. Debe seleccionar la casilla __Exhibe contenido__ en los tags que haya ingresado el nombre. Los tags que ya estén con esa opción seleccionada  y no es posible deshacer la selección son obligatorios.
 14. La URL utilizada para acceder al XML se genera automáticamente, conforme al [dominio registrado en el diccionario del Sitio Web](https://help.vtex.com/es/tutorial/configurar-dominio-del-xml--2RkGK4vHS0c6sYuUw0cUWC), en el CMS.
 
-<div class="alert alert-warning">
-  <p>Si la política comercial tiene restricción de acceso, el XML no se generará.</p>
-</div>
+>⚠️ Si la política comercial tiene restricción de acceso, el XML no se generará.
 
 ## Conectores nativos: una alternativa a XML para integrar con marketplaces
 
diff --git a/docs/tutorials/es/coupons-beta.md b/docs/tutorials/es/coupons-beta.md
index 11706f338..43a169dac 100644
--- a/docs/tutorials/es/coupons-beta.md
+++ b/docs/tutorials/es/coupons-beta.md
@@ -21,9 +21,7 @@ Un cupón es un código promocional formado por una secuencia de letras y númer
 
 Puedes crear y editar cupones en el Admin VTEX, a través de **Promociones** > [Cupones](https://help.vtex.com/es/tutorial/lista-de-cupones-beta--5z5ya3IonsC2W4B5h4JrsZ) o de la [Promotions & Taxes API](https://developers.vtex.com/vtex-rest-api/reference/promotions-taxes-api-v2).
 
-<div class="alert alert-warning">
-<p>El cupón debe estar vinculado, al menos, a una promoción para poderse utilizar. Un cupón se puede asociar a cualquier tipo de promoción, excepto a una <a href="https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume">Promoción de campaña</a>. Obtén más información en <a href="https://help.vtex.com/es/tutorial/crear-cupon-beta--7lMk3MmhNp2IEccyGApxU">Crear cupón (Beta)</a>.</p>
-</div>
+>⚠️ El cupón debe estar vinculado, al menos, a una promoción para poderse utilizar. Un cupón se puede asociar a cualquier tipo de promoción, excepto a una [Promoción de campaña](https://help.vtex.com/es/tutorial/promocion-de-campana--1ChYXhK2AQGuS6wAqS8Ume). Obtén más información en [Crear cupón (Beta)](https://help.vtex.com/es/tutorial/crear-cupon-beta--7lMk3MmhNp2IEccyGApxU).
 
 ## Tipos de cupones
 
diff --git a/docs/tutorials/es/creating-a-campaign-audience.md b/docs/tutorials/es/creating-a-campaign-audience.md
index 3f3f54936..3cbe92ddd 100644
--- a/docs/tutorials/es/creating-a-campaign-audience.md
+++ b/docs/tutorials/es/creating-a-campaign-audience.md
@@ -26,9 +26,7 @@ Para crear una nueva audiencia de campaña, sigue los pasos a continuación:
 5. Rellena los campos de la sección [Crear nuevo público-objetivo](#crear-nuevo-publico-objetivo).
 6. Haz clic en `Guardar`.
 
-<div class="alert alert-warning">
-  <p>Luego de crear una audiencia de campaña, debes asociarla a una promoción de campaña para que entre en efecto. Sigue los pasos indicados en la guía <a href="https://help.vtex.com/es/tutorial/promocion-de-campanha--1ChYXhK2AQGuS6wAqS8Ume">Crear una promoción de campaña</a>.</p>
-</div>
+>⚠️ Luego de crear una audiencia de campaña, debes asociarla a una promoción de campaña para que entre en efecto. Sigue los pasos indicados en la guía [Crear una promoción de campaña](https://help.vtex.com/es/tutorial/promocion-de-campanha--1ChYXhK2AQGuS6wAqS8Ume).
 
 ## Datos generales
 
@@ -45,10 +43,9 @@ Al crear una nueva audiencia de campaña, debes completar la información en la
     * **Fecha de término:** fecha de finalización de la programación de la audiencia de campaña a partir de la cual la audiencia de campaña será válida.
     * **Hora de término:** horario de finalización de la programación de la audiencia de campaña a partir de la cual la audiencia de campaña será válida.
 
-<div class="alert alert-warning">
-  <p>Para programar una audiencia de campaña, debes completar una <strong>Fecha de inicio</strong> o una <strong>Hora de inicio</strong> posterior a la fecha u hora actual.</p>
-<p>La zona horaria que toma en cuenta el sistema es la misma que la del dispositivo del usuario que creó la audiencia de campaña. No se realizan ajustes en caso de que haya zonas horarias diferentes.</p>
-</div>
+>⚠️ Para programar una audiencia de campaña, debes completar una **Fecha de inicio** o una **Hora de inicio** posterior a la fecha u hora actual.
+>
+> La zona horaria que toma en cuenta el sistema es la misma que la del dispositivo del usuario que creó la audiencia de campaña. No se realizan ajustes en caso de que haya zonas horarias diferentes.
 
 ## Crear nuevo público-objetivo
 
@@ -102,9 +99,7 @@ Ejemplo: en la imagen a continuación, los ítems cuya marca es **Nike** forman
 * **El código postal de entrega debe Incluir / Excluir de __ hasta __:** permite incluir o excluir intervalos de códigos postales para el envío de los pedidos. La audiencia de campaña se activará si el código postal cumple con la regla configurada en el público-objetivo.
 * **Afiliados:** permite seleccionar [afiliados](https://help.vtex.com/es/tutorial/que-es-afiliado--4bN3e1YarSEammk2yOeMc0) a partir de una lista. La audiencia de campaña se activará si la compra se realiza en un _marketplace_ de los afiliados seleccionados.
 
-  <div class="alert alert-warning">
-    <p>La opción <strong>Afiliados</strong> solo se aplica si el afiliado es una tienda VTEX.</p>
-  </div>
+  >⚠️ La opción **Afiliados** solo se aplica si el afiliado es una tienda VTEX.
 
 * **utm_source:** permite seleccionar la [utm_source](https://help.vtex.com/es/tutorial/que-son-utm-source-utm-campaign-y-utm-medium--2wTz7QJ8KUG6skGAoAQuii) deseada o crear una nueva para vincularla a la audiencia de campaña. La audiencia de campaña se activará si el cliente navega con la utm_source correspondiente a cualquiera de los valores registrados. Cabe destacar que el cliente puede ingresar solo una utm_source en el _checkout_.
 * **utm_campaign:** permite seleccionar la [utm_campaign](https://help.vtex.com/es/tutorial/que-son-utm-source-utm-campaign-y-utm-medium--2wTz7QJ8KUG6skGAoAQuii) deseada o crear una nueva para vincularla a la audiencia de campaña. El descuento se aplicará si la navegación se realiza con la utm_campaign con el valor registrado.
@@ -112,9 +107,7 @@ Ejemplo: en la imagen a continuación, los ítems cuya marca es **Nike** forman
 * **Aplique el descuento solo cuando el cliente seleccione uno de los transportistas anteriores:** la audiencia de campaña se activará solo después que el cliente seleccione la forma de envío del pedido.
 * **Medio de pago:** permite seleccionar los medios de pago que se incluirán en el público-objetivo. La audiencia de campaña se activará si la forma de pago elegida por el cliente es la misma que la registrada.
 
-<div class="alert alert-warning">
-  <p>Las audiencias de campañas definidas por <strong>Medio de pago</strong> o<strong> Número máximo de cuotas</strong> no aplican a los pedidos que se pagan con dos tarjetas o con tarjetas de regalo.</p>
-</div>
+>⚠️ Las audiencias de campañas definidas por **Medio de pago** o** Número máximo de cuotas** no aplican a los pedidos que se pagan con dos tarjetas o con tarjetas de regalo.
 
 ## Más información
 
diff --git a/docs/tutorials/es/creating-a-coupon-beta.md b/docs/tutorials/es/creating-a-coupon-beta.md
index 76e4d11dc..82986e33f 100644
--- a/docs/tutorials/es/creating-a-coupon-beta.md
+++ b/docs/tutorials/es/creating-a-coupon-beta.md
@@ -69,9 +69,7 @@ La sección **General** muestra los campos que debes completar con la informaci
     * **Número de cupones:** permite definir la cantidad de códigos que se generarán a partir del prefijo definido en **Código del cupón**. La cantidad máxima es de 1000.
     * **Exportar cupones:** botón que permite exportar los códigos del cupón múltiple. Esta opción está disponible solo cuando se editan cupones ya existentes.
 
-<div class="alert alert-warning">
-<p>Se debe definir al menos una de las UTM, es decir que es obligatorio rellenar la <strong>Fuente UTM</strong> o la <strong>Campaña UTM</strong>. También se pueden rellenar ambos campos.</p>
-</div>
+>⚠️ Se debe definir al menos una de las UTM, es decir que es obligatorio rellenar la **Fuente UTM** o la **Campaña UTM**. También se pueden rellenar ambos campos.
 
 ### Restricciones
 
@@ -81,9 +79,7 @@ En esta sección del formulario, puedes configurar las siguientes restricciones
 
   Al mantener desactivada esta opción, el cupón podrá usarse ilimitadamente.
 
-  <div class="alert alert-warning">
-<p>En caso de que se cancele un pedido con un cupón de uso limitado, se recalculará el límite. Esto significa que los pedidos con status <strong>Cancelado</strong> no cuentan en el límite de veces que se podrá usar el cupón.</p>
-  </div>
+  >⚠️ En caso de que se cancele un pedido con un cupón de uso limitado, se recalculará el límite. Esto significa que los pedidos con status **Cancelado** no cuentan en el límite de veces que se podrá usar el cupón.
 
 ## Cupones existentes
 
diff --git a/docs/tutorials/es/creating-a-coupon.md b/docs/tutorials/es/creating-a-coupon.md
index 00f03810c..389d2863b 100644
--- a/docs/tutorials/es/creating-a-coupon.md
+++ b/docs/tutorials/es/creating-a-coupon.md
@@ -30,9 +30,7 @@ En este artículo trataremos:
 
 ## Cómo crear un cupón
 
-<div class="alert alert-warning">
-  <p>Hay un límite en la cantidad de cupones activos. Se recomienda reutilizar los cupones, ya que un número elevado puede comprometer el rendimiento del módulo <b>Tasas y Promociones</b>.</p>
-</div>
+>⚠️ Hay un límite en la cantidad de cupones activos. Se recomienda reutilizar los cupones, ya que un número elevado puede comprometer el rendimiento del módulo **Tasas y Promociones**.
 
 Para crear un cupón, siga los pasos a continuación.
 
@@ -41,9 +39,7 @@ Para crear un cupón, siga los pasos a continuación.
 4. Rellene los [campos de registro del cupón](#campos-de-registro-del-cupon).
 5. Haga clic en el botón `Guardar`.
 
-<div class="alert alert-info">
-  <p>Solo se puede crear un cupón a la vez en el Admin. Para crear cupones de forma masiva, lea el artículo <a href="https://developers.vtex.com/vtex-rest-api/docs/creating-and-managing-coupons-with-promotions-api">Creating and managing coupons with Promotions API</a>.</p>
-</div>
+>ℹ️ Solo se puede crear un cupón a la vez en el Admin. Para crear cupones de forma masiva, lea el artículo [Creating and managing coupons with Promotions API](https://developers.vtex.com/vtex-rest-api/docs/creating-and-managing-coupons-with-promotions-api).
 
 ### Campos de registro del cupón
 
@@ -53,9 +49,7 @@ En esta sección se definirá la información general del cupón.
 
 - **Cupón:** el código de activación del cupón. No hay límite de caracteres y el campo es obligatorio.
 
-<div class="alert alert-warning">
-  <p>No se puede utilizar caracteres especiales (solo letras, números y guiones).</p>
-</div>
+>⚠️ No se puede utilizar caracteres especiales (solo letras, números y guiones).
 
 - **utm_source:** la utm de origen.
 - **utm_campaign:** la utm de la campaña.
@@ -67,9 +61,7 @@ En esta sección se registran las posibles restricciones del cupón.
 - **El cliente puede comprar hasta X productos utilizando este cupón en una o más compras:**el número de productos que se pueden comprar con este cupón, independientemente de cuántas compras se realicen para alcanzar este número.
 - **Renovar cada uso del cupón después de X días:** la validez del cupón se renueva después de la cantidad de días seleccionada en este campo.
 
-<div class="alert alert-info">
-  <p>Para limitar el cupón a un solo uso, debe <a href="https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327#4-restricoes-e-limitacoes-de-uso">restringir el número de aplicaciones de la promoción en su tienda y por cliente</a>.</p>
-</div>
+>ℹ️ Para limitar el cupón a un solo uso, debe [restringir el número de aplicaciones de la promoción en su tienda y por cliente](https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327#4-restricoes-e-limitacoes-de-uso).
 
 Cuando se realiza una compra con una promoción que tiene una limitación y esa compra se cancela, este uso de la promoción vuelve a ser válido.
 
@@ -92,9 +84,7 @@ Para desactivar un cupón es necesario archivarlo. Para archivar un cupón, siga
 2. Seleccione el cupón que desea archivar.
 3. En la página de edición del cupón, haga clic en el botón `Archivar`.
 
-<div class="alert alert-warning">
-  <p>Los cupones no pueden ser eliminados, solo archivados. Solo se puede archivar un cupón a la vez. Puede editar y reutilizar un cupón, pero el <b>código del cupón</b> no se puede cambiar.</p>
-</div>
+>⚠️ Los cupones no pueden ser eliminados, solo archivados. Solo se puede archivar un cupón a la vez. Puede editar y reutilizar un cupón, pero el **código del cupón** no se puede cambiar.
 
 ## Escenario de aplicación
 
@@ -106,9 +96,7 @@ Debe crear una promoción y divulgarla en un <i>newsletter</i>. Sin embargo, la
 4. Introducir el código del cupón en el <i>newsletter</i>.
 5. La promoción se activará en el carrito solo cuando el cliente rellene el campo **Cupón de descuento** y lo aplique.
 
-<div class="alert alert-info">
-  <p>También es posible configurar los enlaces del <i>newsletter </i>directamente con la <b>utm_source</b> y <b>utm_campaign</b> y prescindir del uso del cupón.</p>
-</div>
+>ℹ️ También es posible configurar los enlaces del <i>newsletter </i>directamente con la **utm_source** y **utm_campaign** y prescindir del uso del cupón.
 
 ## Utilizar múltiples cupones
 
diff --git a/docs/tutorials/es/creating-a-product-collection.md b/docs/tutorials/es/creating-a-product-collection.md
index a04b7816d..debf56cf2 100644
--- a/docs/tutorials/es/creating-a-product-collection.md
+++ b/docs/tutorials/es/creating-a-product-collection.md
@@ -65,9 +65,7 @@ Para crear un grupo con productos de una o más marcas, basta con seleccionar la
 
 Para crear una colección de productos que aún no fueron lanzados, selecciones &#8220;Pré-venda&#8221; en &#8220;Outras Opções&#8221;. El sistema considerará todos los productos con fecha posterior a la actual, como definido en el campo “Data de lançamento no mercado” (registro de producto). O en cambio, puede configurar la colección para considerar productos lanzados recientemente. Para ello, seleccione la opción &#8220;Lançamento&#8221;. El sistema considerará todos los productos con la fecha definida en el campo “Data de lançamento no mercado” (registro de producto) dentro del intervalo de 30 días anteriores al actual. Vea en el ejemplo abajo que es posible seleccionar uno u otro campo. En caso que quiera que ambos escenarios sean contemplados, cree dos colecciones y configure cada una con la respectiva opción.
 
-<div class="alert alert-warning">
-Estas opcciones son un <em>complemento</ em> a la elección de los productos. Es importante resaltar que estas flags sólo funcionarán si usted ha elegido para la colección alguna categoría, marca o combinación de SKUs. Estas flags se utilizan junto con la selección de categorías, marcas o SKUs para la colección.
-</div>
+>⚠️ Estas opcciones son un <em>complemento</ em> a la elección de los productos. Es importante resaltar que estas flags sólo funcionarán si usted ha elegido para la colección alguna categoría, marca o combinación de SKUs. Estas flags se utilizan junto con la selección de categorías, marcas o SKUs para la colección.
 
 ### Incluir SKUs específicos en un grupo
 
diff --git a/docs/tutorials/es/creating-a-product-for-presale.md b/docs/tutorials/es/creating-a-product-for-presale.md
index 99a9dbb5e..dbccee8b1 100644
--- a/docs/tutorials/es/creating-a-product-for-presale.md
+++ b/docs/tutorials/es/creating-a-product-for-presale.md
@@ -34,15 +34,11 @@ Para que un producto esté disponible en preventa, sigue los pasos a continuaci
 5. Rellena los [campos restantes del producto](https://help.vtex.com/es/tutorial/campos-de-registro-de-producto--4dYXWIK3zyS8IceKkQseke).
 6. Haz clic en `Guardar y Crear SKU`.
 7. En la página de creación del SKU, rellena el campo **Fecha de previsión de llegada (preventa)** con la fecha en que el producto estará disponible para su entrega por parte de la tienda en el formato `dd/mm/aaaa`.
-<div class="alert alert-info">
-  <p>Para registrar la fecha de llegada, debe tenerse en cuenta tanto la fecha de lanzamiento como el cálculo del envío: <code>tiempo de entrega final = SLA de entrega + plazo para recibir el lote de suministro</code>.</p>  
-</div>
+>ℹ️ Para registrar la fecha de llegada, debe tenerse en cuenta tanto la fecha de lanzamiento como el cálculo del envío: `tiempo de entrega final = SLA de entrega + plazo para recibir el lote de suministro`.
 8. Rellena los [campos restantes del SKU](https://help.vtex.com/es/tutorial/campos-de-registro-de-sku--21DDItuEQc6mseiW8EakcY).
 9. Haz clic en `Guardar`.
 
-<div class="alert alert-info">
-  <p>El pedido del ítem en preventa solo debe facturarse a partir de la fecha de lanzamiento, es decir, cuando haya disponibilidad real de <i>stock</i> del producto.</p>  
-</div>
+>ℹ️ El pedido del ítem en preventa solo debe facturarse a partir de la fecha de lanzamiento, es decir, cuando haya disponibilidad real de <i>stock</i> del producto.
 
 ## Programar precios
 Para programar los precios fijos de tu tienda para la preventa de un producto, sigue los pasos descritos en el artículo [Programar precios](https://help.vtex.com/es/tutorial/programar-precio--4vVha6TGzYkguWuMOqCcCk). 
diff --git a/docs/tutorials/es/creating-a-shipping-policy.md b/docs/tutorials/es/creating-a-shipping-policy.md
index adb99b66b..c0063bd11 100644
--- a/docs/tutorials/es/creating-a-shipping-policy.md
+++ b/docs/tutorials/es/creating-a-shipping-policy.md
@@ -52,9 +52,7 @@ Para crear una nueva política de envío, siga los pasos a continuación:
         *   Seleccione `Día de la semana` y rellene el `Hora de recogida`. 
         *   Para añadir más días de la semana, haga clic en `Agregar hora de recogida`.
 
-<div class="alert alert-warning">
-La <b>Ventana de envío</b> y la <b>Hora de recogida</b> son opciones que se excluyen entre sí, ya que no se puede asignar el mismo período simultáneamente a acciones distintas.
-</div> 
+>⚠️ La **Ventana de envío** y la **Hora de recogida** son opciones que se excluyen entre sí, ya que no se puede asignar el mismo período simultáneamente a acciones distintas. 
 
 *   **[Entrega programada](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)**: esta funcionalidad puede habilitarse si la política de envío ofrece un servicio de entrega programada. Aquí es donde debe añadir las ventanas de entrega que estarán disponibles para el cliente al final de la compra. Para utilizarla, habilite `entrega programada` y rellene:
     *   **Tiempo máximo de entrega:** define el tiempo máximo de entrega, debe ser completado con el tiempo en días.
diff --git a/docs/tutorials/es/creating-a-subscription-plan.md b/docs/tutorials/es/creating-a-subscription-plan.md
index 2742bb126..da41898c5 100644
--- a/docs/tutorials/es/creating-a-subscription-plan.md
+++ b/docs/tutorials/es/creating-a-subscription-plan.md
@@ -23,9 +23,7 @@ Hay dos formas de crear un plan de suscripción. Lo más recomendable es crear u
 
 La otra manera es crear un [Anexo de SKU que haga referencia a la suscripción en el Catálogo](#anexo-de-sku-en-el-catalogo). El anexo de SKU equivale al plan.
 
-<div class="alert alert-warning">
-  <p>No debe realizar ambas configuraciones, basta elegir una de ellas. Solo tiene que crear el nuevo plan en el módulo <strong>Suscripciones</strong> o el anexo de SKU en <strong>Catálogo</strong>. De lo contrario, el plan se duplicará.</p>
-</div>
+>⚠️ No debe realizar ambas configuraciones, basta elegir una de ellas. Solo tiene que crear el nuevo plan en el módulo **Suscripciones** o el anexo de SKU en **Catálogo**. De lo contrario, el plan se duplicará.
 
 ## Nuevo plan en el módulo Suscripciones
 
@@ -37,9 +35,7 @@ La creación de un nuevo plan desde el módulo **Suscripciones** es la forma má
 4. Haga clic en la pestaña [Productos asociados](#productos-asociados) y seleccione los productos que desea asociar a los planes de suscripción.
 5. Haga clic en `Salvar` para guardar los cambios.
 
-<div class="alert alert-warning">
-  <p>Todos los planes se guardan como activos, aunque no tengan ningún producto asociado. Los planes que no tienen productos asociados no aparecen como opción para el cliente en el momento de la compra.</p>
-</div>
+>⚠️ Todos los planes se guardan como activos, aunque no tengan ningún producto asociado. Los planes que no tienen productos asociados no aparecen como opción para el cliente en el momento de la compra.
 
 ### Configuraciones
 
@@ -69,9 +65,7 @@ Para eliminar una frecuencia previamente creada, debe hacer clic en el botón de
 
 Si desea, puede ofrecer varias opciones de frecuencia en el mismo plan. En este caso, debe hacer clic de nuevo en el botón `Agregar frecuencia` y repetir el proceso de rellenar  la configuración con las otras frecuencias deseadas. De este modo, el cliente puede elegir la frecuencia que prefiera de entre las opciones.
 
-<div class="alert alert-warning">
-  <p>No es posible asignar un periodo de caducidad al plan de suscripción desde el módulo <strong>Suscripciones</strong>. Solo los planes de suscripción configurados como Anexos de SKU en <strong>Catálogo</strong> pueden tener periodos de caducidad configurados.</p>
-</div>
+>⚠️ No es posible asignar un periodo de caducidad al plan de suscripción desde el módulo **Suscripciones**. Solo los planes de suscripción configurados como Anexos de SKU en **Catálogo** pueden tener periodos de caducidad configurados.
 
 ### Productos asociados
 
diff --git a/docs/tutorials/es/creating-a-trade-policy.md b/docs/tutorials/es/creating-a-trade-policy.md
index d55514a9d..b7cdc5b39 100644
--- a/docs/tutorials/es/creating-a-trade-policy.md
+++ b/docs/tutorials/es/creating-a-trade-policy.md
@@ -17,9 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 En VTEX las [políticas comerciales](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) se utilizan para agrupar configuraciones de catálogo, precios, promociones, inventario, logística de envío y pagos para distintos canales de venta. Los canales de venta pueden incluir, por ejemplo, marketplaces, ecommerces, tiendas físicas o tiendas B2B.
 
-<div class="alert alert-danger">
-Por defecto, las nuevas políticas comerciales se aplican a todos los vendedores activos. Si desea aplicarlas solo a un grupo específico de vendedores, por favor, indíquelo en el ticket.
-</div>
+>❗ Por defecto, las nuevas políticas comerciales se aplican a todos los vendedores activos. Si desea aplicarlas solo a un grupo específico de vendedores, por favor, indíquelo en el ticket.
 
 ## Manejar políticas comerciales
 
@@ -33,9 +31,7 @@ Para utilizar el mismo catálogo en más de una política comercial, acceda a la
 
 Para [contratar políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), póngase en contacto con nuestro equipo de Growth Operations en *[Soporte](https://help.vtex.com/es/support)* seleccionando la opción **Comercial** y el tipo de solicitud `Creación de Política Comercial`. Al solicitar la creación de una política comercial a través de un ticket, tenga en cuenta un tiempo de respuesta de hasta tres días hábiles.
 
-<div class="alert alert-info">
-Para que el uso de política comercial adicional para integrarse con <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex"conector nativo</a>, un <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner">conector certificado (partner)</a> u otras tiendas VTEX esté exento de tarifas, los pedidos deben estar asociados a la misma.
-</div>
+>ℹ️ Para que el uso de política comercial adicional para integrarse con [conector certificado (partner)](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex"conector nativo</a>, un <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-certificado-partner) u otras tiendas VTEX esté exento de tarifas, los pedidos deben estar asociados a la misma.
 
 ## Más información
 
diff --git a/docs/tutorials/es/creating-a-type-of-list.md b/docs/tutorials/es/creating-a-type-of-list.md
index e4f07245f..a31ac8e98 100644
--- a/docs/tutorials/es/creating-a-type-of-list.md
+++ b/docs/tutorials/es/creating-a-type-of-list.md
@@ -26,9 +26,7 @@ La creación de un tipo de lista es la configuración de qué listas tendrá el
 
 Después de crear los tipos de listas, será posible que los clientes efectivamente creen sus listas en el sitio.
 
-<div class="alert alert-warning">
-  <p>No se puede eliminar una lista después de que se ha generado.</p>
-</div>
+>⚠️ No se puede eliminar una lista después de que se ha generado.
 
 ## Campos del formulario
 
diff --git a/docs/tutorials/es/creating-an-oauth2-authentication.md b/docs/tutorials/es/creating-an-oauth2-authentication.md
index ab982c90b..d50af7e57 100644
--- a/docs/tutorials/es/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/es/creating-an-oauth2-authentication.md
@@ -21,7 +21,7 @@ Para algunos administradores de tienda, existe la necesidad de crear una autenti
 
 Debido a esto, VTEX pone a disposición la __autenticación OAuth2__ integrada a VTEX ID.
 
-<div class="alert alert-warning">Como este es un asunto con aspectos bastante técnicos, recomendamos el acompañamiento de un compañero o equipo de TI.</div>
+>⚠️ Como este es un asunto con aspectos bastante técnicos, recomendamos el acompañamiento de un compañero o equipo de TI.
 
 ### ¿Qué es OAuth2?
 
@@ -156,7 +156,7 @@ Response:
 
 Una vez que el servicio está desarrollado y público en Internet, todos los datos de configuración deben ser direccionados a VTEX (vía ticket de soporte) para que sea configurado el ambiente de la tienda e integrado a VTEX ID, poniendo a disposición otra opción de login para sus clientes.
 
-<div class="alert alert-info">Si tienes varias tiendas (subcuentas) enumeradas en <strong>Configuraciónes de la cuenta > Gestión de la cuenta > Cuenta</strong>, cada una requerirá su propia configuración de Proveedor de identidad OAuth2.</div>
+>ℹ️ Si tienes varias tiendas (subcuentas) enumeradas en **Configuraciónes de la cuenta > Gestión de la cuenta > Cuenta**, cada una requerirá su propia configuración de Proveedor de identidad OAuth2.
 
 En resumen, estos son:
 
diff --git a/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
index dc341b1b1..08cab3480 100644
--- a/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/es/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -24,9 +24,7 @@ Para aplicar un precio diferenciado a los productos por XML, es necesario asocia
   3. Aquí debe verificar si los campos relacionados con el precio del SKU (menor precio del producto, mayor precio del producto, precio original del SKU, precio actual del SKU y precio actual del SKU + tasas) se rellenaron. Al menos uno de los campos debe contener información para que la operación funcione correctamente.
   4. Rellene el campo __Tablas de precios__ con el nombre de la tabla de precios deseada. A continuación, haga clic en la casilla correspondiente al tag en la columna __Exhibe contenido__. La tabla de precios seleccionada debe tener registrados los precios fijos. De lo contrario, la configuración no se realizará.
 ![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
-<div class="alert alert-warning">
-  <p>Cuando se incluya la tabla de precios en el XML, se sobrescribirán todos los campos de precios.</p>
-</div>
+>⚠️ Cuando se incluya la tabla de precios en el XML, se sobrescribirán todos los campos de precios.
   5. Haga clic en `Guardar`.
 
 Así, la plataforma hará la asociación de los valores de la tabla de precios con los productos registrados en la colección del archivo XML. 
diff --git a/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md b/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md
index d2748314f..b01ead7e5 100644
--- a/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md
+++ b/docs/tutorials/es/creating-customer-and-address-forms-in-new-stores.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 En el Master Data, los formularios de Cliente y Dirección no se crean por estándar en todas las nuevas tiendas. Están presentes solo en la tienda principal de la cuenta. Este escenario es recurrente en los casos en que se crean multi-tiendas.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 Es posible crear estos formularios automáticamente, bastando seguir las instrucciones a continuación para cada tienda que se desee.
 
diff --git a/docs/tutorials/es/creating-data-entity.md b/docs/tutorials/es/creating-data-entity.md
index 067659517..13c3b674a 100644
--- a/docs/tutorials/es/creating-data-entity.md
+++ b/docs/tutorials/es/creating-data-entity.md
@@ -23,21 +23,16 @@ Para ejemplificar, imagine un sistema de control de una biblioteca. Este sistema
 
 Con estos conceptos, es posible configurar los más diversos escenarios de control de datos por el Master Data. De forma predeterminada, se insertan las siguientes entidades de datos: Cliente, Dirección, Tiendas, etc. Es posible crear cuántas más entidades de datos desee, posibilitando un ambiente personalizado, orientado a las necesidades de cada tienda.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 ## Entendiendo los tipos
 
diff --git a/docs/tutorials/es/creating-landing-pages.md b/docs/tutorials/es/creating-landing-pages.md
index abee2719a..3a6f6d08c 100644
--- a/docs/tutorials/es/creating-landing-pages.md
+++ b/docs/tutorials/es/creating-landing-pages.md
@@ -21,9 +21,7 @@ En el Admin puedes crear páginas de destino personalizadas, como páginas para
 
 1. Accede al Admin VTEX y dirígete a acesse **Storefront > Páginas**
 
-<div class="alert alert-warning">
-<p>Si tu tienda tiene múltiples políticas comerciales o es transfronteriza, selecciona el <a href="https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W">binding</a> correspondiente a la tienda a la que desees añadir una nueva página de destino utilizando el menú desplegable que aparece en la parte superior derecha.</p>
-</div>
+>⚠️ Si tu tienda tiene múltiples políticas comerciales o es transfronteriza, selecciona el [binding](https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W) correspondiente a la tienda a la que desees añadir una nueva página de destino utilizando el menú desplegable que aparece en la parte superior derecha.
 
 2.Haz clic en **CREAR NUEVA**.
 
@@ -39,10 +37,7 @@ En el Admin puedes crear páginas de destino personalizadas, como páginas para
 | Descripción | Resumen de la nueva página web que se mostrará en las páginas de resultados de los motores de búsqueda. |
 | Palabras clave | Temas que definen el contenido de la página, ayudando a mostrar la página a los usuarios interesados en los resultados de los motores de búsqueda. |
 
-<div class="alert alert-warning">
-<p>Para evitar conflictos y garantizar la integridad del sistema, no se permite modificar la URL de una ruta existente. Si es necesario modificarla, se recomienda crear una nueva página con la nueva ruta y, de ser necesario, desactivar la anterior.
-</p>
-</div>
+>⚠️ Para evitar conflictos y garantizar la integridad del sistema, no se permite modificar la URL de una ruta existente. Si es necesario modificarla, se recomienda crear una nueva página con la nueva ruta y, de ser necesario, desactivar la anterior.
 
 <div class = "alert alert-info">
 <p>Los cinco campos anteriores impactan directamente en los accesos a la tienda y en el posicionamiento en las páginas de resultados de los motores de búsqueda. Antes de rellenar los metadatos de la página, ten en cuenta las mejores prácticas de SEO.
diff --git a/docs/tutorials/es/creating-merchandising-rules-manual-editor.md b/docs/tutorials/es/creating-merchandising-rules-manual-editor.md
index 6fef79910..313c0eda5 100644
--- a/docs/tutorials/es/creating-merchandising-rules-manual-editor.md
+++ b/docs/tutorials/es/creating-merchandising-rules-manual-editor.md
@@ -33,9 +33,7 @@ Si deseas configurar una [regla de merchandising](https://help.vtex.com/es/track
   Para aplicar el efecto de personalización deseado, debes definir una o varias condiciones en esta etapa. Si deseas conocer cómo registrar una condición, lee [Condiciones de las reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
 10. Haz clic en `Guardar`.
 
-<div class="alert alert-info">
-  <p>Una vez guardados, la actualización de los cambios en las reglas de merchandising demoran un promedio de dos minutos.</p>
-</div>
+>ℹ️ Una vez guardados, la actualización de los cambios en las reglas de merchandising demoran un promedio de dos minutos.
 
 ## Ejemplo
 
@@ -79,9 +77,7 @@ Considera el siguiente ejemplo: deseas promover productos de la marca Beautyx du
 
 * **Remover**: excluye las condiciones seleccionadas del resultado, es decir, elimina los productos que estarán en el resultado de la búsqueda.
 
-  <div class="alert alert-info">
-   <p><strong>Agregar</strong> y <strong>Eliminar</strong> son compatibles con otros tipos de formas de ordenar que no se basan en la relevancia configurada. Por lo tanto, si agregas o eliminas un producto utilizando una regla de <em>merchandising </em>y si, por ejemplo, el cliente de tu tienda ordena los resultados de búsqueda por precio, los productos se ordenarán por precio, pero los productos mostrados respetarán la regla de <em>merchandising</em>.</p>
-  </div>
+  >ℹ️ **Agregar** y **Eliminar** son compatibles con otros tipos de formas de ordenar que no se basan en la relevancia configurada. Por lo tanto, si agregas o eliminas un producto utilizando una regla de *merchandising *y si, por ejemplo, el cliente de tu tienda ordena los resultados de búsqueda por precio, los productos se ordenarán por precio, pero los productos mostrados respetarán la regla de *merchandising*.
 
 * **Promover**: resalta las condiciones seleccionadas en el resultado. Da más relevancia a un producto que ya aparecería en el resultado de la búsqueda.
 
@@ -89,10 +85,6 @@ Considera el siguiente ejemplo: deseas promover productos de la marca Beautyx du
 
 * **Dejar de promover**: oculta las condiciones seleccionadas en el resultado. Permite dejar de priorizar un producto que ya aparece en los resultados de la búsqueda.
 
-  <div class="alert alert-info">
-   <p><strong>Promover</strong> y <strong>Dejar de promover</strong> solo funcionan cuando el cliente de la tienda ordena los resultados de la búsqueda por relevancia. En cambio, si ordena los resultados por precio, por ejemplo, los productos se ordenarán estrictamente por precio y no se utilizará la regla de <em>merchandising</em>.</p>
-  </div>
+  >ℹ️ **Promover** y **Dejar de promover** solo funcionan cuando el cliente de la tienda ordena los resultados de la búsqueda por relevancia. En cambio, si ordena los resultados por precio, por ejemplo, los productos se ordenarán estrictamente por precio y no se utilizará la regla de *merchandising*.
 
-  <div class="alert alert-warning">
-   <p>No configures condiciones que afecten a los mismos productos tanto en la sección <strong>Promover</strong> como en la sección <strong>Dejar de promover</strong> porque se producirán efectos opuestos. Si la configuración de esta condición es incorrecta, esa configuración incorrecta afecta negativamente el comportamiento de la funcionalidad y no se mostrarán los resultados deseados.</p>
-  </div>
+  >⚠️ No configures condiciones que afecten a los mismos productos tanto en la sección **Promover** como en la sección **Dejar de promover** porque se producirán efectos opuestos. Si la configuración de esta condición es incorrecta, esa configuración incorrecta afecta negativamente el comportamiento de la funcionalidad y no se mostrarán los resultados deseados.
diff --git a/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
index 99849f184..8c66d403b 100644
--- a/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/es/creating-merchandising-rules-visual-editor-beta.md
@@ -15,9 +15,7 @@ legacySlug: crear-regla-de-merchandising-editor-visual-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solamente clientes seleccionados pueden acceder a ella. Si tienes interés en implementarla en tu negocio, comunícate con <a href="https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solamente clientes seleccionados pueden acceder a ella. Si tienes interés en implementarla en tu negocio, comunícate con [nuestro Soporte](https://support.vtex.com/hc/es-419/requests).
 
 Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) de VTEX Intelligent Search utilizando el [Editor visual](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), sigue los pasos a continuación.
 
@@ -47,9 +45,7 @@ Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vte
       Más información sobre estas acciones en los puntos **4, 5, 6, 8, 9** y **11** de la sección [Acciones disponibles en el Editor visual](#acciones-disponibles-en-el-editor-visual).
 9. Haz clic en `Guardar`.
 
- <div class="alert alert-info">
-  <p>Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.</p>
-</div>
+ >ℹ️ Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.
 
 ## Acciones disponibles en el Editor visual
 
diff --git a/docs/tutorials/es/creating-merchandising-rules-visual-editor.md b/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
index a007ccbe7..7c1291571 100644
--- a/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
+++ b/docs/tutorials/es/creating-merchandising-rules-visual-editor.md
@@ -43,9 +43,7 @@ Para configurar una [regla de merchandising](https://help.vtex.com/es/tracks/vte
       Más información sobre estas acciones en los puntos **4, 5, 6, 8, 9** y **11** de la sección [Acciones disponibles en el Editor visual](#acciones-disponibles-en-el-editor-visual).
 9. Haz clic en `Guardar`.
 
- <div class="alert alert-info">
-  <p>Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.</p>
-</div>
+ >ℹ️ Una vez guardados, los cambios en las reglas de merchandising tardan un promedio de dos minutos en actualizarse.
 
 ## Acciones disponibles en el Editor visual
 
diff --git a/docs/tutorials/es/creating-pickup-points.md b/docs/tutorials/es/creating-pickup-points.md
index c42774220..45955dc0a 100644
--- a/docs/tutorials/es/creating-pickup-points.md
+++ b/docs/tutorials/es/creating-pickup-points.md
@@ -24,8 +24,7 @@ Hay dos maneras de registrar los puntos de recogida a través de Admin:
 * [Registro individual](#registro-individual);
 * [Registro por plantilla](#registro-por-plantilla);
 
-<div class="alert alert-warning">El registro de los puntos de recogida es uno de los pasos necesarios para el correcto funcionamiento de la funcionalidad. Consulta el artículo <a href="https://help.vtex.com/es/tutorial/puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R">Puntos de recogida</a> y descubre la configuración necesaria para que los puntos de recogida estén disponibles para tus clientes.
-</div>
+>⚠️ El registro de los puntos de recogida es uno de los pasos necesarios para el correcto funcionamiento de la funcionalidad. Consulta el artículo [Puntos de recogida](https://help.vtex.com/es/tutorial/puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R) y descubre la configuración necesaria para que los puntos de recogida estén disponibles para tus clientes.
 
 ## Registro individual
 
@@ -42,9 +41,7 @@ Hay dos maneras de registrar los puntos de recogida a través de Admin:
 * **ID:** identificación del punto de recogida. Si no se rellena, el sistema elegirá un ID automáticamente. No dejes espacios en blanco.
 * **Punto de recogida de terceros:** marca esta casilla si el punto de recogida no está relacionado con tu tienda. Los puntos de recogida de terceros se muestran con menos relevancia que los de la propia tienda.
 
-  <div class="alert alert-danger">
-La configuración <b>Punto de recogida de terceros</b> actualmente no está disponible.
-</div>
+  >❗ La configuración **Punto de recogida de terceros** actualmente no está disponible.
 
 Selecciona <i class="fas fa-toggle-on"></i> para activar el punto de recogida.
 
@@ -74,9 +71,7 @@ La información de la dirección y la ubicación en el mapa se mostrarán en el
     2. Rellena el **día** y la **hora**;
     3. Haz clic en `Agregar`.
 
-<div class="alert alert-warning">
-La hora laborable registrada en el punto de recogida solo tiene carácter informativo y no se utiliza en el cálculo del SLA. Para cambiar la configuración que influye en el plazo de entrega, es necesario establecer el horario de funcionamiento en la <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">política de envío</a> relacionada con el punto de recogida. En el caso del registro de feriados, la configuración debe realizarse en el módulo de <a href="https://help.vtex.com/es/tutorial/registrar-feriados--2ItOthSEAoyAmcwsuiO6Yk">feriados</a> para que influya en el cálculo del plazo.
-</div>
+>⚠️ La hora laborable registrada en el punto de recogida solo tiene carácter informativo y no se utiliza en el cálculo del SLA. Para cambiar la configuración que influye en el plazo de entrega, es necesario establecer el horario de funcionamiento en la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) relacionada con el punto de recogida. En el caso del registro de feriados, la configuración debe realizarse en el módulo de [feriados](https://help.vtex.com/es/tutorial/registrar-feriados--2ItOthSEAoyAmcwsuiO6Yk) para que influya en el cálculo del plazo.
 
 ## Registro por plantilla
 
diff --git a/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
index ee9fca67a..b902af5ed 100644
--- a/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/es/creating-promotion-for-a-customer-cluster.md
@@ -33,11 +33,7 @@ Con la propiedad definida, siga las instrucciones que se indican a continuación
 6. Rellene el campo con el clúster que desea asociar a la promoción.[Vea a continuación más información sobre cómo completar este campo](#como-completar-el-campo-cluster-de-clientes). Puede añadir más de un clúster haciendo clic en el botón `+`.
 7. Haga clic en `Guardar`.
 
-<div class="alert alert-info">
-<p>
-El límite de clústeres que pueden ingresarse en la opción <strong>clúster de clientes</strong> es 50. 
-</p>
-</div>
+>ℹ️ El límite de clústeres que pueden ingresarse en la opción **clúster de clientes** es 50.
 
 ## Cómo completar el campo Clúster de clientes
 
@@ -48,11 +44,7 @@ Hay dos criterios posibles para seleccionar un clúster para la promoción y, po
 
 Nótese que en ambas opciones, `{nombredelapropriedad}` debe cambiarse por el nombre del campo en la entidad de datos y `{valor}` debe sustituirse por el valor definido en Master Data.
 
-<div class="alert alert-info">
-<p>
-El uso de las comillas varía en <a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#">función del tipo de campo</a> creado en Master Data.
-</p>
-</div>
+>ℹ️ El uso de las comillas varía en [función del tipo de campo](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#) creado en Master Data.
 
 ### Función de igualdad
 
@@ -68,11 +60,7 @@ De esta manera también se podría establecer `empleado=false`, donde solo los r
 
 Dado un campo **[Varchar](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#)**, podríamos configurar `empleado="sí"` para que solo los clientes con el valor `"sí"` en el campo recibieran la promoción.
 
-<div class="alert alert-warning">
-<p>
-Para los campos de tipo <strong>Varchar</strong>, el valor introducido en la sección <strong>Clúster de clientes</strong> de la promoción distingue los caracteres minúsculos de los mayúsculos. Esto significa que si se completa la opción de Clúster de Clientes de forma diferente a la definida para el campo en Master Data, la promoción no se aplicará.
-</p>
-</div>
+>⚠️ Para los campos de tipo **Varchar**, el valor introducido en la sección **Clúster de clientes** de la promoción distingue los caracteres minúsculos de los mayúsculos. Esto significa que si se completa la opción de Clúster de Clientes de forma diferente a la definida para el campo en Master Data, la promoción no se aplicará.
 
 Por lo tanto, considerando el ejemplo anterior de un campo de tipo **Varchar** con los valores `"sí"` y `"no"`, el registro en la promoción debe ser `empleado="sí"`. Si se introduce el término `empleado="Sí"` en la promoción, por ejemplo, el clúster de clientes deseado no recibirá la promoción.
 
diff --git a/docs/tutorials/es/creating-roles.md b/docs/tutorials/es/creating-roles.md
index 6ba50a900..6f3e75ca6 100644
--- a/docs/tutorials/es/creating-roles.md
+++ b/docs/tutorials/es/creating-roles.md
@@ -26,9 +26,7 @@ Consulta a continuación los pasos a seguir para cada una de estas opciones:
 
 Recomendamos crear roles análogos a las estructuras jerárquicas de la tienda. De este modo, todos los colaboradores son responsables de la información a la que pueden acceder. Las buenas prácticas de gestión de los roles de usuario no solo mejoran la seguridad de las operaciones, sino que también fortalecen el compromiso de todas las partes involucradas en la protección de los datos sensibles de la tienda y tus clientes.
 
-<div class="alert alert-warning">
-  <p>El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas en caso de que se filtren las credenciales de inicio de sesión.</p>
-</div>
+>⚠️ El uso sin restricciones de roles muy permisivos aumenta el riesgo de ataques en las tiendas en caso de que se filtren las credenciales de inicio de sesión.
 
 ## Rol predefinido
 
@@ -78,9 +76,7 @@ Sigue las instrucciones a continuación para crear un rol personalizado que resp
 
 7. Asigna un nombre para el rol personalizado en el campo **Nombre del rol**.
 
-  <div class="alert alert-warning">
-    <p>Es importante elegir nombres descriptivos para los roles, que indiquen claramente qué tipo de usuario debe tener ese acceso. Se recomienda especificar el cargo en la empresa o la función a desempeñar en la plataforma.</p>
-  </div>
+  >⚠️ Es importante elegir nombres descriptivos para los roles, que indiquen claramente qué tipo de usuario debe tener ese acceso. Se recomienda especificar el cargo en la empresa o la función a desempeñar en la plataforma.
 
 8. Agrega usuarios administrativos al rol rellenando el email del usuario en **Agregar usuarios para este rol** y haciendo clic en `Agregar`.
 
diff --git a/docs/tutorials/es/creating-service-for-a-sku.md b/docs/tutorials/es/creating-service-for-a-sku.md
index 0e6c0a6dc..5dc825dd1 100644
--- a/docs/tutorials/es/creating-service-for-a-sku.md
+++ b/docs/tutorials/es/creating-service-for-a-sku.md
@@ -86,9 +86,7 @@ Para vincular un servicio a un SKU, sigue los pasos a continuación:
 ### Campos de la plantilla
 Maneja la plantilla con cuidado, comprobando siempre que la información está correctamente rellenada. Todos los campos de la plantilla deben rellenarse para evitar errores.
 
-<div class="alert alert-warning">
-  <p>Al rellenar la plantilla, no cambie ni elimine los títulos de las columnas en la línea 1. Rellene los valores deseados en las líneas posteriores a los títulos de las columnas para que la importación funcione correctamente.</p>
-</div>  
+>⚠️ Al rellenar la plantilla, no cambie ni elimine los títulos de las columnas en la línea 1. Rellene los valores deseados en las líneas posteriores a los títulos de las columnas para que la importación funcione correctamente.  
 
 - **Nome Serviço:** es el nombre del servicio.
 - **Texto Serviço:** es el texto que se mostrará junto con el servicio.
diff --git a/docs/tutorials/es/creating-synonyms.md b/docs/tutorials/es/creating-synonyms.md
index 706b6ebce..5a2830a29 100644
--- a/docs/tutorials/es/creating-synonyms.md
+++ b/docs/tutorials/es/creating-synonyms.md
@@ -42,9 +42,7 @@ Siga el proceso paso a paso para configurar sinónimos individualmente en VTEX A
 
 La alteración puede tardar hasta dos horas en aplicarse.
 
-<div class="alert alert-info">
-<p>Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos">VTEX Intelligent Search: configuración Multidioma (Beta)</a> para saber más.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lea nuestro artículo [VTEX Intelligent Search: configuración Multidioma (Beta)](https://help.vtex.com/es/tutorial/vtex-intelligent-search-configuracion-multidioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos) para saber más.
 
 ## Importar CSV
 
@@ -91,6 +89,4 @@ Tiendas que utilizan configuración multidioma (beta) deben seguir la siguiente
    __Ejemplo:__
    - `tv,smart tv;true;en-GB`: al buscar cualquiera de estos términos en la tienda en el idioma inglés (`locale en-GB`), se mostrará cualquier producto que contenga uno de esos términos en los resultados de búsqueda.
 
-<div class="alert alert-warning">
-  <p> Si el archivo .csv importado no contiene el <code>locale</code>, el sinónimo será válido para todos los idiomas disponibles en la tienda. </p>
-</div>
+>⚠️ Si el archivo .csv importado no contiene el `locale`, el sinónimo será válido para todos los idiomas disponibles en la tienda.
diff --git a/docs/tutorials/es/creating-the-files-structure-for-your-app-vtex-init.md b/docs/tutorials/es/creating-the-files-structure-for-your-app-vtex-init.md
index fdec1f9e3..f561ae2de 100644
--- a/docs/tutorials/es/creating-the-files-structure-for-your-app-vtex-init.md
+++ b/docs/tutorials/es/creating-the-files-structure-for-your-app-vtex-init.md
@@ -33,8 +33,6 @@ Con ello, el IO hará algunas preguntas que se utilizarán para definir parámet
 
 El IO informa que su archivo manifest.json ha sido generado con éxito y le pregunta el servicio VTEX que desea utilizar. 
 
-<div class="alert alert-info">
-Para el desarrollo front-end, el servicio que se debe utilizar es el react.
-</div>
+>ℹ️ Para el desarrollo front-end, el servicio que se debe utilizar es el react.
 
 Listo! Su estructura de carpetas y archivos está creada.
diff --git a/docs/tutorials/es/creating-trigger-in-master-data.md b/docs/tutorials/es/creating-trigger-in-master-data.md
index 7c17d0687..34b481be7 100644
--- a/docs/tutorials/es/creating-trigger-in-master-data.md
+++ b/docs/tutorials/es/creating-trigger-in-master-data.md
@@ -15,9 +15,7 @@ legacySlug: creando-trigger-en-el-master-data
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
-<div class="alert alert-info">
-  <p>Este artículo hace referencia a Master Data v1. Si deseas utilizar Master Data v2, consulta los pasos de la guía <a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2">Setting up triggers in Master Data v2</a>.</p>
-</div>
+>ℹ️ Este artículo hace referencia a Master Data v1. Si deseas utilizar Master Data v2, consulta los pasos de la guía [Setting up triggers in Master Data v2](https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2).
 
 Conceptualmente, un trigger es un recurso de programación que ejecuta una acción específica siempre que se produce un evento asociado. En Master Data, un trigger es la configuración de uno o varios eventos disparadores que se activan cuando se produce una determinada situación, en función de diversas variables.
 
@@ -123,9 +121,7 @@ Aquí debes definir las condiciones que activarán el evento o eventos configura
 
    ![filters-es](https://images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/ce8019b7300c8c857ac71ffb4f0091c9/filters-es.png)
 
-<div class="alert alert-info">
-  <p>Master Data v1 no permite la configuración de reintentos de trigger, a diferencia de Master Data v2.</p>
-</div>
+>ℹ️ Master Data v1 no permite la configuración de reintentos de trigger, a diferencia de Master Data v2.
 
 ### Programar
 
diff --git a/docs/tutorials/es/credit-card-basic-payment-flow.md b/docs/tutorials/es/credit-card-basic-payment-flow.md
index ff1f881c9..fd9b378cf 100644
--- a/docs/tutorials/es/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/es/credit-card-basic-payment-flow.md
@@ -27,6 +27,4 @@ Este artículo tiene como objetivo explicar cómo funciona el flujo básico de u
 
 Con la respuesta del banco emisor, se realiza el flujo inverso y el __Gateway de Pagos__ recibe la información si el pago fue aprobado o negado.
 
-<div class="alert alert-info">
-Es posible incluir el <strong>Antifraude</strong> en este flujo. En este caso, el antifraude recibe la información del gateway de que el pago fue pre-autorizado por el banco emisor. Con la información recibida del gateway, el antifraude envía una respuesta de aprobación o denegación del pago. Si el antifraude niega, el pago se cancela. Si el pago se aprueba, el pedido puede proseguir su flujo normal.
-</div>
+>ℹ️ Es posible incluir el **Antifraude** en este flujo. En este caso, el antifraude recibe la información del gateway de que el pago fue pre-autorizado por el banco emisor. Con la información recibida del gateway, el antifraude envía una respuesta de aprobación o denegación del pago. Si el antifraude niega, el pago se cancela. Si el pago se aprueba, el pedido puede proseguir su flujo normal.
diff --git a/docs/tutorials/es/credit-control-overview.md b/docs/tutorials/es/credit-control-overview.md
index dc8609b66..438bb81e0 100644
--- a/docs/tutorials/es/credit-control-overview.md
+++ b/docs/tutorials/es/credit-control-overview.md
@@ -15,10 +15,8 @@ legacySlug: credit-control-vision-general
 subcategory: 7EWKfPIGfmI0G8iMYK8Aiy
 ---
 
-<div class="alert alert-warning">
-<strong>ATENCIÓN:</strong> el Credit Control se interrumpió en <strong>diciembre de 2018</strong>. Ahora, para su tienda ofrecer crédito como medio de pago directo en el checkout, es necesario <a href="https://help.vtex.com/es/tutorial/customer-credit-vision-general">utilizar el Customer Credit</a>.</br>
-Para saber cómo configurarlo en su tienda, siga los pasos descritos  <a href="http://help.vtex.com/es/tracks/customer-credit-como-empezar">aquí</a>.
-</div>
+>⚠️ **ATENCIÓN:** el Credit Control se interrumpió en **diciembre de 2018**. Ahora, para su tienda ofrecer crédito como medio de pago directo en el checkout, es necesario [utilizar el Customer Credit](https://help.vtex.com/es/tutorial/customer-credit-vision-general).</br>
+> Para saber cómo configurarlo en su tienda, siga los pasos descritos  [aquí](http://help.vtex.com/es/tracks/customer-credit-como-empezar).
 
 
 ## Qué es
diff --git a/docs/tutorials/es/criar-um-produto-beta.md b/docs/tutorials/es/criar-um-produto-beta.md
index 39e02aa0f..00a4d0ee5 100644
--- a/docs/tutorials/es/criar-um-produto-beta.md
+++ b/docs/tutorials/es/criar-um-produto-beta.md
@@ -15,8 +15,7 @@ legacySlug: criar-um-produto-beta
 subcategory: 
 ---
 
-<div class="alert alert-info">
-Esta funcionalidad se encuentra en fase beta, lo que significa que estamos trabajando para optimizarla. Si tienes alguna duda ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>.</div>
+>ℹ️ Esta funcionalidad se encuentra en fase beta, lo que significa que estamos trabajando para optimizarla. Si tienes alguna duda ponte en contacto con [nuestro equipo de soporte](https://support.vtex.com/hc/es/requests).
 
 La página **Agregar producto(Beta)** permite crear y editar [productos](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru) y sus correspondientes SKU en el Admin VTEX. Para agregar un nuevo producto sigue los pasos a continuación: 
 
@@ -33,7 +32,7 @@ La página **Agregar producto(Beta)** permite crear y editar [productos](https:/
 
 Una vez hecho esto, el producto se activará y estará disponible en tu tienda.
 
-<div class="alert alert-info">Si tras crear el producto no se muestra en el sitio web de tu tienda, consulta el artículo <a href="https://help.vtex.com/es/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382">¿Por qué el producto no aparece en el sitio web?</a>, para saber cómo solucionar este problema.</div>
+>ℹ️ Si tras crear el producto no se muestra en el sitio web de tu tienda, consulta el artículo [¿Por qué el producto no aparece en el sitio web?](https://help.vtex.com/es/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382), para saber cómo solucionar este problema.
 
 ## Producto
 
@@ -117,8 +116,7 @@ En la pestaña Atributos se mostrarán los grupos de especificaciones con las es
 
 En esta pestaña, registrarás los [SKUs](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA#) que estarán vinculados al producto que creaste anteriormente. 
 
-<div class="alert alert-info">
-El producto debe tener al menos un SKU activo para estar disponible en tu tienda. Es necesario adjuntar una imagen al SKU para activarlo.</div>
+>ℹ️ El producto debe tener al menos un SKU activo para estar disponible en tu tienda. Es necesario adjuntar una imagen al SKU para activarlo.
 
 ## Especificaciones
 Aquí se mostrarán las especificaciones anteriormente creadas para los SKU. Si creaste algún campo de SKU obligatorio, el SKU solo podrá activarse una vez que se haya rellenado esa especificación. 
diff --git a/docs/tutorials/es/crm-zen-suiteshare.md b/docs/tutorials/es/crm-zen-suiteshare.md
index 891816391..a14a361b5 100644
--- a/docs/tutorials/es/crm-zen-suiteshare.md
+++ b/docs/tutorials/es/crm-zen-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: crm-zen-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/custom-product-fields.md b/docs/tutorials/es/custom-product-fields.md
index 794c2dcde..c859641f1 100644
--- a/docs/tutorials/es/custom-product-fields.md
+++ b/docs/tutorials/es/custom-product-fields.md
@@ -42,9 +42,7 @@ Para crear un campo de producto, sigue los pasos a continuación:
 5. Haz clic en __Campo (Producto).__  
 6. Haz clic en __Nuevo campo.__  
 7. Completa la información del campo que estás creando:  
-<div class="alert alert-warning">
-El nombre del campo debe completarse exactamente como uno de los nombres presentados en la tabla de secciones<a href="#campos-personalizables">Campos personalizables</a>.
-</div>  
+>⚠️ El nombre del campo debe completarse exactamente como uno de los nombres presentados en la tabla de secciones[Campos personalizables](#campos-personalizables).  
 
   __Nombre:__ nombre de la especificación (campo) de producto.  
   __Texto:__ descripción del campo.  
diff --git a/docs/tutorials/es/customer-credit-overview.md b/docs/tutorials/es/customer-credit-overview.md
index 781f9df91..096f442bf 100644
--- a/docs/tutorials/es/customer-credit-overview.md
+++ b/docs/tutorials/es/customer-credit-overview.md
@@ -34,9 +34,7 @@ A través de VTEX Admin o [API de Customer Credit](https://developers.vtex.com/d
 - Configurar plazos y cuotas para documentos de facturas.
 - Monitorear y modificar el status de las facturas emitidas.
 
-<div class="alert alert-info">
-Cuando se instala, el Customer Credit aparece como una opción de pago en el momento del pago solo para los clientes seleccionados por el administrador de la tiend, y muestra la cantidad de crédito disponible para usar en la compra.
-</div>
+>ℹ️ Cuando se instala, el Customer Credit aparece como una opción de pago en el momento del pago solo para los clientes seleccionados por el administrador de la tiend, y muestra la cantidad de crédito disponible para usar en la compra.
 
 Vea a continuación el flujo básico de cómo funciona el Customer Credit en las tiendas VTEX:
 
@@ -52,9 +50,7 @@ Para utilizar Customer Credit como medio de pago de una compra, el cliente debe
 
 Cada cuenta tiene un límite de crédito registrado al momento de su apertura. Este límite indica el monto máximo que el cliente puede utilizar para realizar una o más compras al mismo tiempo a través de Customer Credit.
 
-<div class="alert alert-warning">
-El administrador de la tienda puede cambiar el límite de crédito de una cuenta en cualquier momento.
-</div>
+>⚠️ El administrador de la tienda puede cambiar el límite de crédito de una cuenta en cualquier momento.
 
 ### Crédito disponible
 
@@ -62,9 +58,7 @@ Monto que el cliente aún tiene disponible en su cuenta para realizar compras a
 
 Cada vez que el cliente completa una compra y se factura el pedido, la cantidad de crédito disponible disminuye. Sin embargo, después de que el cliente realiza el pago de la factura emitida, el valor del crédito disponible vuelve al valor previo a la compra.
 
-<div class="alert alert-warning">
-En el momento de una compra, el cliente tiene visibilidad de cuánto crédito puede utilizar a través del Customer Credit. Si el valor de la compra es mayor que el crédito disponible, no se podrá realizar el pago a través de Customer Credit.
-</div>
+>⚠️ En el momento de una compra, el cliente tiene visibilidad de cuánto crédito puede utilizar a través del Customer Credit. Si el valor de la compra es mayor que el crédito disponible, no se podrá realizar el pago a través de Customer Credit.
 
 ### Factura
 
@@ -82,9 +76,7 @@ Luego de que el cliente realiza la compra utilizando Customer Credit, el pago se
 
 El flujo en Customer Credit es similar al de las tarjetas de crédito en relación a las modificaciones de pedidos. Cuando se produce un cambio en el valor del pedido durante el período de preautorización, el monto del crédito cambia.
 
-<div class="alert alert-warning">
-Si es necesario cambiar una orden para reducir su valor después del período de liquidación (emisión de facturas), el sistema actualizará las facturas al nuevo valor. Si el valor del pedido aumenta, el sistema creará nuevas facturas.
-</div>
+>⚠️ Si es necesario cambiar una orden para reducir su valor después del período de liquidación (emisión de facturas), el sistema actualizará las facturas al nuevo valor. Si el valor del pedido aumenta, el sistema creará nuevas facturas.
 
 ## Instalacion y configuracion
 
diff --git a/docs/tutorials/es/customizar-a-toolbar-de-televendas.md b/docs/tutorials/es/customizar-a-toolbar-de-televendas.md
index b138d714d..c3da571d6 100644
--- a/docs/tutorials/es/customizar-a-toolbar-de-televendas.md
+++ b/docs/tutorials/es/customizar-a-toolbar-de-televendas.md
@@ -15,7 +15,7 @@ legacySlug: customizar-a-toolbar-de-televendas
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-warning">No se recomienda cambiar la altura del elemento HTML de la toolbar. Se tu tienda tiene un header fijo en la parte superior de la pantalla, hay que utilizar la propiedade css `top` con la altura necesaria para evitar sobreposición entre el header y la barra</div>
+>⚠️ No se recomienda cambiar la altura del elemento HTML de la toolbar. Se tu tienda tiene un header fijo en la parte superior de la pantalla, hay que utilizar la propiedade css `top` con la altura necesaria para evitar sobreposición entre el header y la barra
 
 
 La nueva toolbar de televentas puede ser personalizada con los estilos de su tienda o con javascript. Para anular los estilos originales de la toolbar, es necesario hacer la personalización en un archivo **.css** o **.js** y cargarlo en en template de la página.
diff --git a/docs/tutorials/es/customize-suiteshare.md b/docs/tutorials/es/customize-suiteshare.md
index c4d987cf4..2ed88b535 100644
--- a/docs/tutorials/es/customize-suiteshare.md
+++ b/docs/tutorials/es/customize-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: personalice
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md b/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md
index e3d9403fb..6e278c7d4 100644
--- a/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md
+++ b/docs/tutorials/es/customizing-the-checkout-confirmation-pages.md
@@ -40,7 +40,7 @@ Es importante recordar que los templates para personalización son los mismos pa
 
 ### Personalización de estilos
 
-<div class="alert alert-warning">Todas estas formas de personalización se pueden cambiar en el futuro. Al usarlas, usted entiende que su tienda debe seguir las actualizaciones de la plataforma para que su personalización siga funcionando correctamente.</div>
+>⚠️ Todas estas formas de personalización se pueden cambiar en el futuro. Al usarlas, usted entiende que su tienda debe seguir las actualizaciones de la plataforma para que su personalización siga funcionando correctamente.
 
 También se puede editar la interfaz del Checkout Confirmation mediante clases CSS. Sus estilos se deben agregar en una tag `<style>` en uno de los templates HTML cargadas en la página.
 
diff --git a/docs/tutorials/es/customizing-the-my-orders-section.md b/docs/tutorials/es/customizing-the-my-orders-section.md
index 176cccc5d..5dde5fe87 100644
--- a/docs/tutorials/es/customizing-the-my-orders-section.md
+++ b/docs/tutorials/es/customizing-the-my-orders-section.md
@@ -21,16 +21,16 @@ Ya está disponible en ambiente beta (`accountname.vtexcommercebeta.com.br`) par
 
 Vea abajo una lista con las clases disponibles para customización:
 
-<div class="alert alert-warning">
-Customizaciones de interface <strong>no son oficialmente soportadas por VTEX</strong>.
-<br />
-<br />
-Estas classes y configuraciones pueden ser alteradas o removidas en futuras actualizaciónes. Como buena práctica, recomendamos tratar errores de Javascript para que su código de customización no quiebre en caso de que una classe sea removida en el futuro.
-</div>
-
-<div class="alert alert-info">
-En el caso de que poseas un archivo de customización para la antigua versión de MyOrders, recomendamos que coloque la nueva customización en un nuevo archivo separado.
-</div>
+>⚠️ Customizaciones de interface **no son oficialmente soportadas por VTEX**.
+>
+>
+> 
+>
+>
+> 
+> Estas classes y configuraciones pueden ser alteradas o removidas en futuras actualizaciónes. Como buena práctica, recomendamos tratar errores de Javascript para que su código de customización no quiebre en caso de que una classe sea removida en el futuro.
+
+>ℹ️ En el caso de que poseas un archivo de customización para la antigua versión de MyOrders, recomendamos que coloque la nueva customización en un nuevo archivo separado.
 
 ### Lista de pedidos
 
diff --git a/docs/tutorials/es/customizing-your-stores-typography.md b/docs/tutorials/es/customizing-your-stores-typography.md
index 447eecea4..96f44ccb7 100644
--- a/docs/tutorials/es/customizing-your-stores-typography.md
+++ b/docs/tutorials/es/customizing-your-stores-typography.md
@@ -18,9 +18,7 @@ subcategory: 5HsDDU48ZP58JHWU3WbCPc
 La tipografía del sitio web de tu tienda es una herramienta para comunicar la identidad de tu marca a los clientes. 
 En el Admin, tienes la flexibilidad de personalizar la tipografía de tu tienda para acomodar las necesidades de tu negocio.
 
-<div class="alert alert-warning">
-  <p>Ten en cuenta que los cambios en la tipografía de tu tienda en el <b>Storefront</b> sobrescriben los cambios de tipografía en el código de tu tienda. Por favor, ponte en contacto con tu equipo de desarrollo y asegúrate de que los cambios se realicen en el Storefront o mediante el código de la tienda.</p>
-</div>
+>⚠️ Ten en cuenta que los cambios en la tipografía de tu tienda en el **Storefront** sobrescriben los cambios de tipografía en el código de tu tienda. Por favor, ponte en contacto con tu equipo de desarrollo y asegúrate de que los cambios se realicen en el Storefront o mediante el código de la tienda.
 
 ## Agregar familias de fuentes personalizadas
 
@@ -33,9 +31,7 @@ En el Admin, tienes la flexibilidad de personalizar la tipografía de tu tienda
 
 4. Luego, haz clic en **Add Custom Font (Agregar fuente personalizada)** y carga el archivo de fuente deseado. En el campo **Font Family (Familia de fuentes)**, ingresa un nombre para la fuente.
 
-<div class="alert alert-warning">
-  <p>Debes cargar el archivo de la familia de fuentes utilizando las siguientes extensiones de archivo: <i>.ttf</i> o <i>.woff</i>.</p>
-</div>
+>⚠️ Debes cargar el archivo de la familia de fuentes utilizando las siguientes extensiones de archivo: <i>.ttf</i> o <i>.woff</i>.
 
 5. Haz clic en Save (Guardar) para guardar los cambios. 
 
diff --git a/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md b/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md
index 06a0adc0e..7488b4b62 100644
--- a/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md
+++ b/docs/tutorials/es/data-dictionary-vtex-data-pipeline-beta.md
@@ -15,9 +15,7 @@ legacySlug: catalogo-vtex-data-pipeline-beta
 subcategory: oMrzcOMVbBpH0reeMFHFg
 ---
 
-<div class="alert alert-info">
-Esta funcionalidad se encuentra en fase beta, lo que significa que estamos trabajando para optimizarla. Si tienes alguna duda, ponte en contacto con <a  href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">nuestro soporte</a>.
-</div>  
+>ℹ️ Esta funcionalidad se encuentra en fase beta, lo que significa que estamos trabajando para optimizarla. Si tienes alguna duda, ponte en contacto con <a  href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">nuestro soporte</a>.  
 
 **VTEX Data Pipeline**, disponible exclusivamente para clientes VTEX, es una herramienta diseñada para explorar y analizar los datos de la tienda online almacenados en nuestros servidores. **Data Pipeline** es un producto add-on de VTEX que integra los datos del sitio web de tu tienda online con el almacén de datos y herramientas BI de tu preferencia, de forma limpia y segura.
 
diff --git a/docs/tutorials/es/data-entity.md b/docs/tutorials/es/data-entity.md
index e7ac33dab..baae30c29 100644
--- a/docs/tutorials/es/data-entity.md
+++ b/docs/tutorials/es/data-entity.md
@@ -23,13 +23,12 @@ Para ilustrarlo, imaginemos un sistema de control de bibliotecas. Este sistema c
 
 Estos conceptos permiten configurar los más diversos escenarios de control de datos en Master Data. De forma predeterminada, se ingresan las siguientes entidades de datos: Cliente, Dirección, Tiendas, etc. Puedes crear todas las entidades de datos que desees para personalizar el entorno de acuerdo con las necesidades de cada tienda.
 
-<div class="alert alert-warning">
-<p>Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar la versión de Master Data que satisface las necesidades de tu operación o que ya está en uso. Más información:</p>
-	<ul>
-    	<li><a href="https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versiones-disponibles">Características de las versiones de Master Data</a></li>
-    	<li><a href="https://developers.vtex.com/docs/guides/master-data-v2-basics">Master Data v2</a></li>
-	</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar la versión de Master Data que satisface las necesidades de tu operación o que ya está en uso. Más información:
+>
+> * [Características de las versiones de Master Data](https://help.vtex.com/es/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versiones-disponibles)
+>
+> * [Master Data v2](https://developers.vtex.com/docs/guides/master-data-v2-basics)
+> 	
 
 ## Tipos de datos
 
@@ -104,6 +103,4 @@ Sigue los pasos a continuación para configurar una nueva entidad de datos.
 19. En la fila de la nueva entidad, haz clic en el botón de disquete <i class="fas fa-save"></i> para publicar la entidad de datos creada.
 20. Haz clic en `OK`.
 
-<div class="alert alert-info">
-	<p>Después de crear la entidad de datos, debes <a href="https://help.vtex.com/es/tutorial/creando-formulario-en-master-data--tutorials_1047">crear el formulario para agregar, editar y mostrar los datos en Master Data</a>.</p>
-</div>
+>ℹ️ Después de crear la entidad de datos, debes [crear el formulario para agregar, editar y mostrar los datos en Master Data](https://help.vtex.com/es/tutorial/creando-formulario-en-master-data--tutorials_1047).
diff --git a/docs/tutorials/es/data-subject-rights.md b/docs/tutorials/es/data-subject-rights.md
index 08eed48be..c1aec6104 100644
--- a/docs/tutorials/es/data-subject-rights.md
+++ b/docs/tutorials/es/data-subject-rights.md
@@ -25,9 +25,7 @@ En este artículo, aprenderás cómo cumplir con los siguientes derechos de los
 - [Consentimiento](#consentimiento).
 - [Eliminación](#eliminacion).
 
-<div class="alert alert-danger">
-VTEX no es responsable por datos personales que los sistemas integrados con tu tienda almacenen, tales como: ERP, marketplaces externos, sellers externos, aplicaciones de terceros disponibles en la <a href="https://help.vtex.com/es/tutorial/visao-geral-apps--4xfsHXyAQTjbZNuiKl6Y0e">VTEX App Store</a> o personalizaciones implementadas por tu equipo de desarrollo. Debes dar seguimiento a estos datos y garantizar que se apliquen los derechos de los titulares de datos personales en dichas instancias, además de aplicar los procesos descritos aquí.
-</div>
+>❗ VTEX no es responsable por datos personales que los sistemas integrados con tu tienda almacenen, tales como: ERP, marketplaces externos, sellers externos, aplicaciones de terceros disponibles en la [VTEX App Store](https://help.vtex.com/es/tutorial/visao-geral-apps--4xfsHXyAQTjbZNuiKl6Y0e) o personalizaciones implementadas por tu equipo de desarrollo. Debes dar seguimiento a estos datos y garantizar que se apliquen los derechos de los titulares de datos personales en dichas instancias, además de aplicar los procesos descritos aquí.
 
 ## Acceso y portabilidad
 
diff --git a/docs/tutorials/es/database-maintenance-full-cleanup.md b/docs/tutorials/es/database-maintenance-full-cleanup.md
index e27ca8a86..90c9414e5 100644
--- a/docs/tutorials/es/database-maintenance-full-cleanup.md
+++ b/docs/tutorials/es/database-maintenance-full-cleanup.md
@@ -29,13 +29,10 @@ Estas son las operaciones disponibles:
 
 -  __Eliminar Productos del Indexador:__ al eliminar productos del indexador, ya no habrá productos que visualizar en su tienda.
 
-  <div class="alert alert-warning">
-    <p> Las siguientes reglas se aplican al botón <b>Eliminar productos del indexador</b>:
-  <UL> <LI>Solamente las tiendas que tengan menos de 10 mil productos pueden realizar esta acción. Las tiendas que tengan un catálogo mayor deben <a href="https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abrir un ticket con el equipo de soporte VTEX</a> para realizar la limpieza del indexador y la reindexación de la base de datos.</LI>
-   <LI>Cuando un usuario elimina productos del indexador, se bloquea la cuenta para que no se pueda realizar esta acción por 24 horas.</LI>
-   <LI>Hay una fila para procesar las solicitudes generadas por el botón <i>Eliminar productos del indexador</i>. Puede ver el tiempo de espera aproximado en la interfaz de la página. La fila es global y se aplica a todos los usuarios para garantizar la seguridad de la plataforma VTEX.</LI></UL>
-    </p>
-  </div>
+  >⚠️ Las siguientes reglas se aplican al botón **Eliminar productos del indexador**:
+>   <UL> <LI>Solamente las tiendas que tengan menos de 10 mil productos pueden realizar esta acción. Las tiendas que tengan un catálogo mayor deben [abrir un ticket con el equipo de soporte VTEX](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) para realizar la limpieza del indexador y la reindexación de la base de datos.</LI>
+>    <LI>Cuando un usuario elimina productos del indexador, se bloquea la cuenta para que no se pueda realizar esta acción por 24 horas.</LI>
+>    <LI>Hay una fila para procesar las solicitudes generadas por el botón <i>Eliminar productos del indexador</i>. Puede ver el tiempo de espera aproximado en la interfaz de la página. La fila es global y se aplica a todos los usuarios para garantizar la seguridad de la plataforma VTEX.</LI></UL>
 
 - __Eliminar Productos/SKU e ítems relacionados:__ al borrar productos y SKU, además de sus ítems relacionados, se eliminarán de forma definitiva de su tienda.
 
@@ -45,6 +42,4 @@ Estas son las operaciones disponibles:
 
 - __Programar reindexación completa:__ al reindexar la base, usted entra en una fila para iniciar el proceso de indexación de sus productos. __Los productos de la tienda continúan disponibles para la venta durante el proceso de indexación__. Estos apenas entran en una fila para la actualización de datos y siguen disponibles en el sitio web para su venta. Atención: después de hacer clic en __Reindexar base__, el proceso se inicia automáticamente.
 
-<div class="alert alert-warning">
-  <p>Es importante <b>Borrar productos del indexador</b> después de realizar cualquier otra operación en esta página. De lo contrario, su tienda puede experimentar errores al acceder a las páginas de productos, categorías o resultados de búsqueda. No es necesario <b>Borrar productos del indexador</b> después de <b>Programar reindexación completa</b>.</p>
-</div>
+>⚠️ Es importante **Borrar productos del indexador** después de realizar cualquier otra operación en esta página. De lo contrario, su tienda puede experimentar errores al acceder a las páginas de productos, categorías o resultados de búsqueda. No es necesario **Borrar productos del indexador** después de **Programar reindexación completa**.
diff --git a/docs/tutorials/es/deactivating-and-reorganizing-categories.md b/docs/tutorials/es/deactivating-and-reorganizing-categories.md
index 04133fa1f..485e1b923 100644
--- a/docs/tutorials/es/deactivating-and-reorganizing-categories.md
+++ b/docs/tutorials/es/deactivating-and-reorganizing-categories.md
@@ -45,9 +45,7 @@ En el árbol de categorías que se muestra en **Catálogo > Categorías** del Ad
 
 ## Editar el árbol de categorias
 
-<div class="alert alert-warning">
-  <p>Mover las categorías directamente a través del árbol de categorías puede generar errores inesperados en tu catálogo. Por lo tanto, te recomendamos seguir las instrucciones a continuación para realizar cualquier cambio en los niveles de las categorías. Consulta el<a href="https://help.vtex.com/es/known-issues/mover-categorias-genera-comportamientos-inesperados-en-el-arbol-de--6JSa9nnYoAAUQO1zPtzfZD"> problema conocido</a> relacionado con este escenario para obtener más información.</p>
-</div>
+>⚠️ Mover las categorías directamente a través del árbol de categorías puede generar errores inesperados en tu catálogo. Por lo tanto, te recomendamos seguir las instrucciones a continuación para realizar cualquier cambio en los niveles de las categorías. Consulta el[ problema conocido](https://help.vtex.com/es/known-issues/mover-categorias-genera-comportamientos-inesperados-en-el-arbol-de--6JSa9nnYoAAUQO1zPtzfZD) relacionado con este escenario para obtener más información.
 
 Hay escenarios en los que es necesario cambiar el nivel jerárquico de una categoría. Por ejemplo, imagina que una tienda tiene una categoría principal llamada **Accesorios** y una categoría secundaria (subcategoría) llamada **Zapatos**, pero quiere hacer de la subcategoría **Zapatos** una categoría principal independiente.
 
diff --git a/docs/tutorials/es/declining-order-cancelation.md b/docs/tutorials/es/declining-order-cancelation.md
index 6af90b769..3d76dca05 100644
--- a/docs/tutorials/es/declining-order-cancelation.md
+++ b/docs/tutorials/es/declining-order-cancelation.md
@@ -44,13 +44,12 @@ La descripción de cada paso es la siguiente:
 3. Si el pedido se encuentra dentro del periodo de cancelación, se cancelará automáticamente, siendo este el comportamiento predeterminado de la plataforma. Los próximos pasos reflejan lo que ocurre cuando el periodo de cancelación ha terminado.
 4. El seller recibe la **Solicitud de cancelación** del pedido y decide si la acepta o no. Los próximos pasos informan lo que ocurre cuando el seller decide no cancelar el pedido.
 
-  <div class="alert alert-danger">
-Para denegar una solicitud de cancelación, el status del pedido para marketplace y seller deben ser los siguientes:
-<ul>
-<li><b>Status del marketplace:</b> esperando decisión del seller.</li>
-<li><b>Status del seller:</b> cancelación solicitada.</li>
-</ul>
-</div>
+  >❗ Para denegar una solicitud de cancelación, el status del pedido para marketplace y seller deben ser los siguientes:
+>
+> ***Status del marketplace:** esperando decisión del seller.
+>
+> ***Status del seller:** cancelación solicitada.
+> 
 
 5. El seller deniega la solicitud de cancelación del pedido y se lo notifica al marketplace.
 6. Una vez que el marketplace recibe la respuesta del seller, el pedido continúa su progresión en el flujo de pedidos.
@@ -61,9 +60,7 @@ La solicitud de cancelación de un pedido puede realizarse por el marketplace o
 
 Después, el [status del pedido](https://help.vtex.com/es/tutorial/order-flow-and-status--tutorials_196) se mostrará de la siguiente manera: `cancelación solicitada` para el marketplace y `esperando decisión del seller` para el seller, hasta que este tome una decisión, ya sea para aceptar o denegar la solicitud.
 
-<div class="alert alert-warning">
-Si en el plazo de 30 días el seller no toma ninguna acción respecto a la solicitud de cancelación del pedido, el pedido será cancelado automáticamente por la plataforma VTEX.
-</div>
+>⚠️ Si en el plazo de 30 días el seller no toma ninguna acción respecto a la solicitud de cancelación del pedido, el pedido será cancelado automáticamente por la plataforma VTEX.
 
 Para denegar una solicitud de cancelación del pedido a través del Admin VTEX, sigue los pasos que se indican a continuación:
 
@@ -77,9 +74,7 @@ Para denegar una solicitud de cancelación del pedido a través del Admin VTEX,
 
   ![deny cancel request reason](https://images.ctfassets.net/alneenqid6w5/1okkX2L4JdZ57qcdZ758O4/fae33faa395d0aa0c51b2cd645bbf2f8/deny_cancel_request_reason_ES.png)
 
-  <div class="alert alert-warning">
-Atención: el cliente puede recibir el mensaje que ingreses en este campo a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi cuenta</a> o a través del marketplace.
-</div>
+  >⚠️ Atención: el cliente puede recibir el mensaje que ingreses en este campo a través de [Mi cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) o a través del marketplace.
 
 5. Haz clic en `Denegar`.
 
diff --git a/docs/tutorials/es/deleting-a-category.md b/docs/tutorials/es/deleting-a-category.md
index f26bffe6e..1e31da7c3 100644
--- a/docs/tutorials/es/deleting-a-category.md
+++ b/docs/tutorials/es/deleting-a-category.md
@@ -37,7 +37,7 @@ Otra opción es [limpiar el catálogo](https://help.vtex.com/es/tutorial/entende
 2. Haga clic en `Eliminar los productos y SKUs`. Atención: al eliminar estos elementos, sus «Productos» y «SKUs», así como sus ítems relacionados, serán borrados de forma definitiva de su tienda.
 3. Después, haga clic en `Eliminar Categorías y Marcas`. Atención: al eliminar estos elementos, «Categorías», «Marcas» y «Especificaciones», así como sus ítems relacionados, serán borrados de forma definitiva de su tienda.
 
-<div class="alert alert-warning"> <p>Por razones de seguridad, solo el <a href="https://help.vtex.com/es/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy">usuario Titular</a> de la cuenta tiene acceso a la limpieza de la base. Si otro usuario intenta acceder a esta página, todos los botones estarán inactivos.</p></div>
+>⚠️ Por razones de seguridad, solo el [usuario Titular](https://help.vtex.com/es/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy) de la cuenta tiene acceso a la limpieza de la base. Si otro usuario intenta acceder a esta página, todos los botones estarán inactivos.
 
 ### Artículos relacionados
 - [Registrar categoría](/es/tutorial/cadastrando-categoria)
diff --git a/docs/tutorials/es/deleting-customer-data.md b/docs/tutorials/es/deleting-customer-data.md
index 10c0c66c0..36ae537e4 100644
--- a/docs/tutorials/es/deleting-customer-data.md
+++ b/docs/tutorials/es/deleting-customer-data.md
@@ -33,17 +33,13 @@ Si tu tienda almacena la información de los clientes en otras entidades de dato
 
 2. Utiliza el request [Delete document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1)
 
-<div class="alert alert-danger">
-No realices este proceso para las entidades <b>CL</b> y <b>AD</b>. 
-</div>
+>❗ No realices este proceso para las entidades **CL** y **AD**.
 
 ## Pedir eliminación vía soporte
 
 Deberás solicitar la extensión de la eliminación de los datos personales de tus clientes en los sistemas de VTEX mediante la apertura de un ticket en nuestro [Soporte VTEX](https://help.vtex.com/es/support).
 
-<div class="alert alert-warning">
-Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará. 
-</div>
+>⚠️ Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará.
 
 Para solicitar la eliminación de los datos personales de clientes, sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/detaching-skus-by-specification.md b/docs/tutorials/es/detaching-skus-by-specification.md
index e60cfe626..89c28c4dc 100644
--- a/docs/tutorials/es/detaching-skus-by-specification.md
+++ b/docs/tutorials/es/detaching-skus-by-specification.md
@@ -27,8 +27,7 @@ A continuación, vea un ejemplo de separación de SKUs por color. La sandalia qu
 
 ![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
-<div class="alert alert-info"><p>
-Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.</p></div>
+>ℹ️ Si los resultados de búsqueda se ordenan por relevancia, los SKUs de un mismo producto se agrupan, es decir, se muestran uno al lado del otro.
 
 ## Configuración
 Para configurar los atributos que se usarán para separar los SKUs, acceda a nuestro artículo de [Configuración de la búsqueda](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
diff --git a/docs/tutorials/es/develop-the-front-end-for-the-list-feature-in-your-store.md b/docs/tutorials/es/develop-the-front-end-for-the-list-feature-in-your-store.md
index c999b45cc..78636c2f2 100644
--- a/docs/tutorials/es/develop-the-front-end-for-the-list-feature-in-your-store.md
+++ b/docs/tutorials/es/develop-the-front-end-for-the-list-feature-in-your-store.md
@@ -116,15 +116,11 @@ Este código representa una lista con __tres links__:
 2. __Crear nueva Lista__: Este enlace lleva al cliente a la ruta `/giftlist/create`, donde el cliente crea sus listas. En los próximos pasos, vamos a explicar cómo se hace la creación de listas.
 3. __Generación de mis Listas__: Este enlace lleva al cliente a la ruta `/giftlist/manage`, donde el cliente puede administrar sus listas. En los próximos pasos, vamos a explicar cómo se gestiona la lista.
 
-<div class="alert alert-danger">
-No desactive la bandera <strong>Authentication Required</strong> ya seleccionada por defecto en las carpetas siguientes. La identificación es necesaria para que las listas se muestren para cada usuario específico.
-</div>
+>❗ No desactive la bandera **Authentication Required** ya seleccionada por defecto en las carpetas siguientes. La identificación es necesaria para que las listas se muestren para cada usuario específico.
 
 ## Editar el template de creación de listas
 
-<div class="alert alert-info">
-Antes de editar esta plantilla, es necesario <a href="http://help.vtex.com/es/tutorial/criando-tipo-de-lista">crear el tipo de lista</a> que se ofrecerá en su lista tienda. <!--Reescrever o artigo de tipo de lista -->
-</div>
+>ℹ️ Antes de editar esta plantilla, es necesario [crear el tipo de lista](http://help.vtex.com/es/tutorial/criando-tipo-de-lista) que se ofrecerá en su lista tienda. <!--Reescrever o artigo de tipo de lista -->
 
 La plantilla para crear listas se encuentra en la ruta `giftlist/create`. La plantilla por defecto de esta ruta es el `new-GiftList-Create`, ubicado en la sección `HTML Templates` de su CMS.
 
diff --git a/docs/tutorials/es/direct-migration-magazine-luiza.md b/docs/tutorials/es/direct-migration-magazine-luiza.md
index 7d5dd2d0f..bfec8f78f 100644
--- a/docs/tutorials/es/direct-migration-magazine-luiza.md
+++ b/docs/tutorials/es/direct-migration-magazine-luiza.md
@@ -15,6 +15,4 @@ legacySlug: migracion-directa-magazine-luiza
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning">
-Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
-</div>
+>⚠️ Este contenido es exclusivamente regional; por lo tanto, no se aplica a los países de habla española.
diff --git a/docs/tutorials/es/disable-cloudflare-proxy.md b/docs/tutorials/es/disable-cloudflare-proxy.md
index 6e275e8c2..9853ecaa6 100644
--- a/docs/tutorials/es/disable-cloudflare-proxy.md
+++ b/docs/tutorials/es/disable-cloudflare-proxy.md
@@ -25,7 +25,5 @@ Para desactivar el proxy de CloudFlare (y, en consecuencia, deshabilite los serv
 
 Observa que si el proxy está activado, el ícono será de color naranja con el texto __*Proxied*__. De lo contrario, el ícono se mostrará en gris con el texto __*DNS Only*__.
 
-<div class="alert alert-info">
-Si deseas utilizar el CDN y el WAF de Cloudflare, puedes insertar un proxy inverso frente a los servicios de VTEX. Ten en cuenta que esta configuración no se recomienda, ya que VTEX ya ofrece servicios de CDN y WAF en su propio servicio de borde. Las fallas de CDN externos no implican fallas en los sistemas de VTEX. No tenemos ninguna responsabilidad sobre los CDN de terceros. 
-</div>
+>ℹ️ Si deseas utilizar el CDN y el WAF de Cloudflare, puedes insertar un proxy inverso frente a los servicios de VTEX. Ten en cuenta que esta configuración no se recomienda, ya que VTEX ya ofrece servicios de CDN y WAF en su propio servicio de borde. Las fallas de CDN externos no implican fallas en los sistemas de VTEX. No tenemos ninguna responsabilidad sobre los CDN de terceros.
 
diff --git a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
index aa8c2a8c5..a2baf35f1 100644
--- a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -23,9 +23,7 @@ subcategory: 2AksvvAtAsbAfE7HsBIVDU
 
 Para unirte a VTEX Ad Network y publicar anuncios en tu tienda, solo tienes que instalar la aplicación VTEX Ad Network para retailers.
 
-<div class="alert alert-warning">
-Por el momento, los retailers VTEX solo pueden disponibilizar inventario de anuncios en storefronts creados con <a href="https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
-</div>
+>⚠️ Por el momento, los retailers VTEX solo pueden disponibilizar inventario de anuncios en storefronts creados con [Store Framework](https://help.vtex.com/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework).
 
 ## Seguimiento de los resultados
 
diff --git a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
index 3b112a485..9190f5539 100644
--- a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
@@ -15,10 +15,9 @@ legacySlug: relevancia-dinamica-en-intelligent-search-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>.</p>
-  <p>Para los clientes seleccionados, la funcionalidad está disponible para su uso gratuito en VTEX Admin durante su período Beta, o hasta que lo decida VTEX. Es posible que en el futuro se apliquen tarifas adicionales.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en fase beta cerrada, lo que significa que por el momento solo tienen acceso a ella algunos clientes seleccionados. Si estás interesado en implementarla en el futuro, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support).
+>
+> Para los clientes seleccionados, la funcionalidad está disponible para su uso gratuito en VTEX Admin durante su período Beta, o hasta que lo decida VTEX. Es posible que en el futuro se apliquen tarifas adicionales.
 
 Intelligent Search es una solución de búsqueda de la plataforma VTEX que, de forma sencilla e intuitiva, devuelve resultados relevantes basados en el catálogo desde la primera interacción del usuario con la tienda, ya sea a través de la barra de búsqueda, al navegar por las categorías o incluso a través de las vitrinas de productos. 
 
diff --git a/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md b/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md
index 919d3099f..d2a07e29c 100644
--- a/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md
+++ b/docs/tutorials/es/edit-a-required-field-on-profile-system-of-master-data.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 El Master Data es un módulo de la plataforma VTEX utilizado para almacenar y organizar documentos. Descubre cómo hacer obligatorio un campo de formulario en Master Data en las instrucciones que aparecen a continuación.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 Los siguientes pasos te permitirán seleccionar un campo y hacerlo obligatorio:
 
diff --git a/docs/tutorials/es/editing-my-data-suiteshare.md b/docs/tutorials/es/editing-my-data-suiteshare.md
index c77dd85d9..cda10d51f 100644
--- a/docs/tutorials/es/editing-my-data-suiteshare.md
+++ b/docs/tutorials/es/editing-my-data-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: editando-mis-datos-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/enable-https-throughout-the-site.md b/docs/tutorials/es/enable-https-throughout-the-site.md
index 62629a029..a92770e3a 100644
--- a/docs/tutorials/es/enable-https-throughout-the-site.md
+++ b/docs/tutorials/es/enable-https-throughout-the-site.md
@@ -58,10 +58,11 @@ Todas las páginas del sitio deben modificarse individualmente conforme al artí
 
 Es posible cambiar el protocolo en todas las carpetas de una sola vez con el uso de nuestra API, documentada [en esta colección de Postman](https://developers.vtex.com/reference/change-uri-schema).
 
-<div class="alert alert-warning">
-<p><strong>Atención:</strong> evite tener el protocolo HTTPS activado sólo en algunas páginas. Al acceder a una página HTTPS, luego ir a una página HTTP de la misma tienda, el navegador intentará leer sus recursos forzosamente en HTTPS, y esto puede generar problemas.</p>
-<p>Lo adecuado es activar el HTTPS en todo el sitio de una sola vez.</p>
-<p>Lo mismo vale para los sitios de desktop y mobile (website secundario), donde es necesario tratar el HTTPS de ambos al mismo tiempo.</p></div>
+>⚠️ **Atención:** evite tener el protocolo HTTPS activado sólo en algunas páginas. Al acceder a una página HTTPS, luego ir a una página HTTP de la misma tienda, el navegador intentará leer sus recursos forzosamente en HTTPS, y esto puede generar problemas.
+>
+> Lo adecuado es activar el HTTPS en todo el sitio de una sola vez.
+>
+> Lo mismo vale para los sitios de desktop y mobile (website secundario), donde es necesario tratar el HTTPS de ambos al mismo tiempo.
 
 ## Limitaciones
 
diff --git a/docs/tutorials/es/enabling-2-factor-authentication-login.md b/docs/tutorials/es/enabling-2-factor-authentication-login.md
index 4351f5e97..d70ef8521 100644
--- a/docs/tutorials/es/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/es/enabling-2-factor-authentication-login.md
@@ -21,9 +21,15 @@ Esto porque, en el inicio de sesión, el sistema además de exigir el email y la
 
 Como esa clave se genera durante el inicio de sesión y tiene una validez corta, se vuelve casi imposible que alguien acceda a su tienda utilizando sus datos sin autorización. Sin 2FA, si alguien tiene su email y contraseña puede tener un acceso amplio a la cuenta de su tienda.
 
-<div class="alert alert-danger">
-Desde el <strong>16 de noviembre de 2017</strong>, la autenticación de dos factores (2FA) se volvió <strong>obligatoria para todos los emails</strong> en el Admin de VTEX.<br><br>Sin 2FA, usted <b>no podrá iniciar sesión</b> utilizando email y contraseña.<br><br>Ese requisito obligatorio no aplica para los otros métodos de inicio de sesión (como Google, Facebook y token).
-</div>
+>❗ Desde el **16 de noviembre de 2017**, la autenticación de dos factores (2FA) se volvió **obligatoria para todos los emails** en el Admin de VTEX.
+>
+> 
+>
+> Sin 2FA, usted **no podrá iniciar sesión** utilizando email y contraseña.
+>
+> 
+>
+> Ese requisito obligatorio no aplica para los otros métodos de inicio de sesión (como Google, Facebook y token).
 
 ## Cómo habilitar 2FA
 
@@ -36,13 +42,9 @@ Existen dos opciones de autenticación, a través de:
 
 ![2FA - Select - ES](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/e608a2a64a982983619918e515bbdb73/2FA_-_Select_-_ES.png)
 
-<div class="alert alert-danger">
-Recomendamos enfáticamente que <strong>elija la opción de autenticación por aplicación</strong>, toda vez que en la autenticación por SMS usted depende de que no haya fallas en el servicio de su operador de telefonía. A través de la aplicación, la clave de acceso siempre estará disponible cuando sea necesaria.
-</div>
+>❗ Recomendamos enfáticamente que **elija la opción de autenticación por aplicación**, toda vez que en la autenticación por SMS usted depende de que no haya fallas en el servicio de su operador de telefonía. A través de la aplicación, la clave de acceso siempre estará disponible cuando sea necesaria.
 
-<div class="alert alert-danger">
-Si configuró 2FA por SMS y el código está tardando en llegar, posiblemente este problema se deba a su operador de telefonía. Habilite 2FA por aplicación como se explica a continuación.  
-</div>
+>❗ Si configuró 2FA por SMS y el código está tardando en llegar, posiblemente este problema se deba a su operador de telefonía. Habilite 2FA por aplicación como se explica a continuación.
 
 ### Habilitar 2FA por aplicación
 
@@ -61,9 +63,7 @@ Para utilizar una clave generada a través de la aplicación de autenticación:
 
 ![2FA - App Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/5327fb40f54e16cd1f63abf16f7da89d/2FA_-_App_Insert_Code_-_ES.png)
 
-<div class="alert alert-info">
-Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso <strong> cada 3 días</strong>. Cuando eso suceda, basta con consultar el código en la aplicación.
-</div>
+>ℹ️ Si usted realiza el inicio de sesión utilizando email y contraseña en el mismo computador, se solicitará la clave de acceso ** cada 3 días**. Cuando eso suceda, basta con consultar el código en la aplicación.
 
 ### Habilitar 2FA por SMS
 
@@ -77,9 +77,7 @@ Para utilizar una clave enviada a través de mensaje de texto:
 
 ![2FA - SMS Insert Code - ES](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/dfcce0514f879ab5a2121d13579c82cb/2FA_-_SMS_Insert_Code_-_ES.png)
 
-<div class="alert alert-warning">
-No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o <a href="#habilitar-o-2fa-por-aplicativo">habilitar 2FA a través de la aplicación</a>.
-</div>
+>⚠️ No podemos garantizar que su operador de telefonía entregue la clave de acceso siempre que sea necesario. En caso de que el mensaje de texto de VTEX no llegue, intente reenviar el código o [habilitar 2FA a través de la aplicación](#habilitar-o-2fa-por-aplicativo).
 
 ### 2FA para operadores de televenta
 
diff --git a/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
index 8ebafd4e5..e7ad6f08d 100644
--- a/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/es/enabling-3ds2-for-redsys-v2-integration.md
@@ -15,7 +15,7 @@ legacySlug: anadir-soporte-a-3ds2-en-la-integracion-con-redsys-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 La funcionalidad 3DS2 ahora está disponible también para pagos realizados con tarjeta de crédito y procesados a través del *gateway* de pagos [Redsýs](https://help.vtex.com/pt/tutorial/configurar-gateway-redsys--7xRnMyzZS0kQoIG2ISagY8).
 
@@ -23,9 +23,7 @@ La funcionalidad 3DS2 ahora está disponible también para pagos realizados con
 
 Para obtener más detalles, consulte el artículo [Flujo de autenticación 3DS2: acepte pagos en línea de forma más segura](https://help.vtex.com/es/announcements/fluxo-de-autenticacao-3ds2-aceite-pagamentos-on-line-de-forma-mais-segura--6UdTjjVU1AcEQ2aE3Ftxsl).
 
-<div class="alert alert-danger">
-Antes de configurar 3DS2, es importante asegurarse de que Redsýs ya esté configurado en su tienda y la alianza comercial firmada esté habilitada para el uso de 3DS2.
-  </div>
+>❗ Antes de configurar 3DS2, es importante asegurarse de que Redsýs ya esté configurado en su tienda y la alianza comercial firmada esté habilitada para el uso de 3DS2.
 
 En este tutorial, le explicaremos cómo realizar esta integración a través del Admin de VTEX mediante el panel administrativo.
 
diff --git a/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
index df836ef06..c98ab2938 100644
--- a/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/es/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -25,9 +25,7 @@ Venta de inventario local permite al vendedor de una tienda física realizar ven
 6. [Conectar la cuenta franquicia a la tienda física](#conectar-la-cuenta-franquicia-a-la-tienda-fisica)
 7. [Integrar el punto de ventas](#integrar-el-punto-de-ventas)
 
-<div class="alert alert-info">
-<p>Venta de inventario local solo puede configurarse en tiendas que ya utilicen Sales App. Para más información sobre cómo solicitar y configurar Sales App, consulta <a href="https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc">Sales App - Primeros pasos y configuración</a>.</p>
-</div>
+>ℹ️ Venta de inventario local solo puede configurarse en tiendas que ya utilicen Sales App. Para más información sobre cómo solicitar y configurar Sales App, consulta [Sales App - Primeros pasos y configuración](https://help.vtex.com/es/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc).
 
 ## Crear una cuenta franquicia
 
@@ -64,9 +62,7 @@ Si todos tus productos se muestran sin cantidad, tendrás que agregar las cantid
 
 Puedes [habilitar la venta de un ítem sin stock](#habilitar-la-venta-de-un-item-sin-stock-opcional) si quieres asegurarte de que el ítem esté siempre disponible para los clientes en la tienda.
 
-<div class="alert alert-info">
-<p>Si has creado dos almacenes diferentes, uno para la tienda online y otro para Sales App, es importante gestionar correctamente la cantidad de ítems de cada uno.</p>
-</div>
+>ℹ️ Si has creado dos almacenes diferentes, uno para la tienda online y otro para Sales App, es importante gestionar correctamente la cantidad de ítems de cada uno.
 
 ## Conectar la cuenta franquicia a la tienda física
 
@@ -79,9 +75,7 @@ Deberás seleccionar un vendedor de la tienda en la que quieras probar Venta en
 
 ![instore-pdp-es](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/b2feab0b2eb3c3893ed654801743e5cd/image.png)
 
-<div class="alert alert-info">
-<p>Si has habilitado el stock infinito, el número mostrado será superior a 1 millón de ítems y no cambiará cuando se complete una venta.</p>
-</div>
+>ℹ️ Si has habilitado el stock infinito, el número mostrado será superior a 1 millón de ítems y no cambiará cuando se complete una venta.
 
 ### Habilitar la venta de un ítem sin stock (opcional)
 
diff --git a/docs/tutorials/es/enabling-payments-with-bitcoin.md b/docs/tutorials/es/enabling-payments-with-bitcoin.md
index 12e4b4829..303f17f07 100644
--- a/docs/tutorials/es/enabling-payments-with-bitcoin.md
+++ b/docs/tutorials/es/enabling-payments-with-bitcoin.md
@@ -19,9 +19,7 @@ La plataforma VTEX permite que su tienda acepte pagos en moneda digital Bitcoin.
 
 Para usar Bitcoin en su tienda, debe haber registrado una afiliación de gateway capaz de procesar este método de pago y relizar la configuración que se describe a configuración que se describe a continuación:
 
-<div class="alert alert-warning">
-  Si el conector a elegir (en <b>Paso 7.</b>) aún no está registrado en su tienda, se mostrará el mensaje “(Configurar)” después del nombre del conector. En esta situación, elija otro conector disponible o regístrese. Para obtener más información, visite <a href="https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Registrar afiliaciones de gateway</a>.
-</div>
+>⚠️ Si el conector a elegir (en **Paso 7.**) aún no está registrado en su tienda, se mostrará el mensaje “(Configurar)” después del nombre del conector. En esta situación, elija otro conector disponible o regístrese. Para obtener más información, visite [Registrar afiliaciones de gateway](https://help.vtex.com/en/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 ## Configurar la condición de pago bitcoin
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
diff --git a/docs/tutorials/es/enter-tracking-number-on-orders-already-invoiced.md b/docs/tutorials/es/enter-tracking-number-on-orders-already-invoiced.md
index 471ac4094..64e411768 100644
--- a/docs/tutorials/es/enter-tracking-number-on-orders-already-invoiced.md
+++ b/docs/tutorials/es/enter-tracking-number-on-orders-already-invoiced.md
@@ -24,9 +24,7 @@ Usted puede introducir el número de seguimiento de entrega en pedidos ya factur
 5. Introduzca el número en el campo **Número de rastreo**.
 6. Haga clic en `Guardar`.
 
-<div class="alert alert-warning">
-El Admin de VTEX no permite la importación en masa, por archivos, de los números de seguimiento de pedidos. El método normalmente utilizado para ello es a través de integración entre VTEX y el ERP de la tienda. Si su ERP está integrado a VTEX, es posible hacer esta importación vía API.
-</div>
+>⚠️ El Admin de VTEX no permite la importación en masa, por archivos, de los números de seguimiento de pedidos. El método normalmente utilizado para ello es a través de integración entre VTEX y el ERP de la tienda. Si su ERP está integrado a VTEX, es posible hacer esta importación vía API.
 
 ### Sepa más
 
diff --git a/docs/tutorials/es/entering-tax-receipts-in-the-order.md b/docs/tutorials/es/entering-tax-receipts-in-the-order.md
index 1363efdd2..26434ed2d 100644
--- a/docs/tutorials/es/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/es/entering-tax-receipts-in-the-order.md
@@ -25,9 +25,7 @@ Con la inserción de la nota fiscal con el valor completo del pedido, él pasar
 
 También es posible la inserción de la nota fiscal parcial, que es cuando son necesarias varias notas fiscales para que se alcance el valor total de la compra.
 
-<div class="alert alert-info">
-<p>Solamente después que se atinge el valor total del pedido se alterará el status para <strong>Facturado</strong>.</p>
-</div>
+>ℹ️ Solamente después que se atinge el valor total del pedido se alterará el status para **Facturado**.
 
 La nota fiscal demanda atención en los siguientes puntos:
 
@@ -39,6 +37,4 @@ O sea, cuando la URL y el código de rastreo están insertados, a cada actualiza
 
 El **Conversation Tracker** depende de la inserción de algún valor en ese campo. Si no tiene un número de rastreo, simplemente introduzca un valor cualquiera para activar el sistema de notificación.
 
-<div class="alert alert-danger">
-Es posible añadir más de una factura al pedido; sin embargo, la suma total de los valores de las facturas debe coincidir con el valor total del pedido.
-</div>
+>❗ Es posible añadir más de una factura al pedido; sin embargo, la suma total de los valores de las facturas debe coincidir con el valor total del pedido.
diff --git a/docs/tutorials/es/erasing-customer-data.md b/docs/tutorials/es/erasing-customer-data.md
index a3014b65d..ec9369029 100644
--- a/docs/tutorials/es/erasing-customer-data.md
+++ b/docs/tutorials/es/erasing-customer-data.md
@@ -35,9 +35,7 @@ Si tu tienda almacena la información de los clientes en otras entidades de dato
 
 2. Utiliza el request [Delete document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1)
 
-<div class="alert alert-danger">
-No realices este proceso para las entidades <b>CL</b> y <b>AD</b>. 
-</div>
+>❗ No realices este proceso para las entidades **CL** y **AD**.
 
 ## Pedir eliminación vía soporte
 
@@ -58,9 +56,7 @@ Para solicitar la eliminación de los datos personales de clientes, sigue los pa
 8. Rellena el campo **Describe en detalle lo sucedido** con los detalles de tu solicitud.
 9. Haz clic en `Enviar`.
 
-<div class="alert alert-warning">
-Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará. 
-</div>
+>⚠️ Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará.
 
 La solicitud se enviará a nuestro equipo de soporte. Al cerrar el ticket, se emitirá un certificado que se enviará al email relacionado con la cuenta por la cual se abrió el ticket para comprobar que realmente se eliminaron los datos.
 
diff --git a/docs/tutorials/es/events-available-in-audit.md b/docs/tutorials/es/events-available-in-audit.md
index de7727465..6ace6e0f4 100644
--- a/docs/tutorials/es/events-available-in-audit.md
+++ b/docs/tutorials/es/events-available-in-audit.md
@@ -39,9 +39,7 @@ A continuación, verás la lista de posibles eventos disponibles en [Audit] (htt
 Si, en Audit, ves algún evento no incluido en esta lista, por favor, envíanos más información a través de la <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback sobre documentación</a>.
 </div>
 
-<div class="alert alert-warning">
-En el módulo Audit, al hacer clic en los filtros de auditoría puedes encontrar <strong>Opciones de envío</strong>, <strong>Profile System</strong> y <strong>Billing</strong>, además de otras aplicaciones citadas a continuación. Estas opciónes se refieren a recursos internos o funcionalidades en beta cerrada, por lo que la mayoría de las cuentas no tendrán eventos asociados.
-</div>
+>⚠️ En el módulo Audit, al hacer clic en los filtros de auditoría puedes encontrar **Opciones de envío**, **Profile System** y **Billing**, además de otras aplicaciones citadas a continuación. Estas opciónes se refieren a recursos internos o funcionalidades en beta cerrada, por lo que la mayoría de las cuentas no tendrán eventos asociados.
 
 ## OMS
 
diff --git a/docs/tutorials/es/exact-sales-suiteshare.md b/docs/tutorials/es/exact-sales-suiteshare.md
index f004dc14e..19ad3a7f4 100644
--- a/docs/tutorials/es/exact-sales-suiteshare.md
+++ b/docs/tutorials/es/exact-sales-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: exact-sales-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
index b5060d309..a7edf30f0 100644
--- a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
@@ -53,9 +53,7 @@ En la planilla de importación, la única columna que debe rellenarse es la de 
 
 La estructura de la plantilla presenta una línea para cada campo de producto o de SKU, o sea, el mismo producto o SKU será presentado diversas veces de acuerdo a los campos existentes en su categoría.
 
-<div class="alert alert-warning">
-  <p>En plantilla exportada, la columna que hace referencia a "ValueSpecification" es "NameFieldValue (Não alterável)". Al rellenar el campo, la ortografía de las características debe ser exacta. Las mayúsculas y las minúsculas marcan la diferencia en este caso.</p>
-  </div>
+>⚠️ En plantilla exportada, la columna que hace referencia a "ValueSpecification" es "NameFieldValue (Não alterável)". Al rellenar el campo, la ortografía de las características debe ser exacta. Las mayúsculas y las minúsculas marcan la diferencia en este caso.
 
 Siga los pasos a continuación para importar la plantilla:
 
diff --git a/docs/tutorials/es/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md b/docs/tutorials/es/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
index 0a66919fa..1c23a9ebe 100644
--- a/docs/tutorials/es/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
+++ b/docs/tutorials/es/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
@@ -15,9 +15,7 @@ legacySlug: exportar-los-clientes-registrados-en-la-notificacion-de-disponibilid
 subcategory: 5yDQmr18K4GgQAeGwq8USa
 ---
 
-<div class="alert alert-warning">
-<p>Este articulo se aplica a la opción <strong>Avísame</strong> en las tiendas que usan <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>. En las tiendas que usan <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, hay que seguir las instrucciones de la guía <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify">Availability Notify</a>.</p>
-</div>
+>⚠️ Este articulo se aplica a la opción **Avísame** en las tiendas que usan [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). En las tiendas que usan [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), hay que seguir las instrucciones de la guía [Availability Notify](https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify).
 
 Para exportar los datos de los clientes que se han registrado en la base de [Avisame](https://help.vtex.com/es/tutorial/configurar-la-opcion-avisame--2VqVifQuf6Co2KG048Yu6e), siga los pasos abajo:
 
diff --git a/docs/tutorials/es/exporting-data.md b/docs/tutorials/es/exporting-data.md
index 654368134..87af793b6 100644
--- a/docs/tutorials/es/exporting-data.md
+++ b/docs/tutorials/es/exporting-data.md
@@ -17,9 +17,7 @@ subcategory: 2AThnkEZAYbk4G4EIs53rL
 
 La exportación de datos en lote de los registros en Master Data v1 puede hacerse por API o mediante planilla. Este documento tiene por objeto demostrar el paso a paso necesario para la exportación de datos por planilla.
 
-<div class="alert alert-warning">
-La operación de exportación de datos del Master Data no es inmediata, y su tiempo de ejecución depende de la cantidad de datos en el Master Data. Por lo tanto, en tiendas con muchos datos y con una alta frecuencia de actualización, el archivo exportado puede quedar desfasado con relación a los nuevos datos. Si esto ocurre, la solución es volver a exportar los datos, preferiblemente en un momento en el que no se estén produciendo muchas actualizaciones (por ejemplo, fuera del horario comercial o en los fines de semana).
-</div>
+>⚠️ La operación de exportación de datos del Master Data no es inmediata, y su tiempo de ejecución depende de la cantidad de datos en el Master Data. Por lo tanto, en tiendas con muchos datos y con una alta frecuencia de actualización, el archivo exportado puede quedar desfasado con relación a los nuevos datos. Si esto ocurre, la solución es volver a exportar los datos, preferiblemente en un momento en el que no se estén produciendo muchas actualizaciones (por ejemplo, fuera del horario comercial o en los fines de semana).
 
 ## Exportar informe con datos de Master Data v1
 
diff --git a/docs/tutorials/es/exporting-orders-in-orders-module.md b/docs/tutorials/es/exporting-orders-in-orders-module.md
index 051a72809..1055732bc 100644
--- a/docs/tutorials/es/exporting-orders-in-orders-module.md
+++ b/docs/tutorials/es/exporting-orders-in-orders-module.md
@@ -19,9 +19,7 @@ El proceso de exportación de pedidos se puede realizar a través de la pantalla
 
 La exportación de pedidos genera un informe en formato .csv que contiene una serie de detalles sobre los pedidos de su tienda. Para saber qué información se muestra en el informe exportado, consulte el [tutorial sobre los campos de la plantilla de pedidos](https://help.vtex.com/es/tutorial/planilla-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
 
-<div class="alert alert-info">
-<p>Cuando el número de pedidos solicitados para la exportación es muy elevado, el proceso puede ser lento. Por lo tanto, hay una limitación en el número de pedidos seleccionados. Por el momento, es posible exportar <b>hasta 50 000 pedidos a la vez</b>.</p>
-</div>
+>ℹ️ Cuando el número de pedidos solicitados para la exportación es muy elevado, el proceso puede ser lento. Por lo tanto, hay una limitación en el número de pedidos seleccionados. Por el momento, es posible exportar **hasta 50 000 pedidos a la vez**.
 
 Siga las instrucciones a continuación para generar el informe:
 
diff --git a/docs/tutorials/es/facebook-liberacao-de-dominio-suiteshare.md b/docs/tutorials/es/facebook-liberacao-de-dominio-suiteshare.md
index d15959486..9c6a9319c 100644
--- a/docs/tutorials/es/facebook-liberacao-de-dominio-suiteshare.md
+++ b/docs/tutorials/es/facebook-liberacao-de-dominio-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: facebook-liberacion-del-dominio
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/faq-security-restricted-content.md b/docs/tutorials/es/faq-security-restricted-content.md
index f1db171d1..12d08214a 100644
--- a/docs/tutorials/es/faq-security-restricted-content.md
+++ b/docs/tutorials/es/faq-security-restricted-content.md
@@ -17,9 +17,7 @@ subcategory:
 
 # FAQ - Seguridad (contenido restringido)
 
-<div class="alert alert-danger">
-  <p>No compartas las respuestas de estas preguntas frecuentes con usuarios que no tengan acceso al Admin VTEX.</p>
-</div>
+>❗ No compartas las respuestas de estas preguntas frecuentes con usuarios que no tengan acceso al Admin VTEX.
 
 Para asistir con las evaluaciones de riesgos de los clientes, VTEX proporciona páginas de preguntas frecuentes con respuestas a las principales preguntas sobre la estructura y seguridad de la plataforma. Este contenido solo está disponible para los usuarios con acceso al Admin VTEX. Las preguntas y respuestas públicas están disponibles en Preguntas frecuentes - Seguridad en VTEX Help Center.
 
diff --git a/docs/tutorials/es/fill-out-the-stock-spreadsheet.md b/docs/tutorials/es/fill-out-the-stock-spreadsheet.md
index e5f612b78..766516f67 100644
--- a/docs/tutorials/es/fill-out-the-stock-spreadsheet.md
+++ b/docs/tutorials/es/fill-out-the-stock-spreadsheet.md
@@ -24,9 +24,7 @@ Además, el correcto rellenado de la plantilla depende de dos reglas. Estas son:
 - Cada coluna de la plantilla debe contener un número o un texto;
 - La actualización de la cantidad de SKUs debe hacerse en la columna __TotalQuantity__. 
 
-<div class="alert alert-warning">
-<strong>Atención</strong>: si estas indicaciones no son respetadas, es posible que el sistema no acepte la importación de la plantilla o que el número de ítems en venta sea incorrecto.  
-</div>
+>⚠️ **Atención**: si estas indicaciones no son respetadas, es posible que el sistema no acepte la importación de la plantilla o que el número de ítems en venta sea incorrecto.
 
 A continuación, verifique el significado de cada campo de la plantilla de inventario.
 
diff --git a/docs/tutorials/es/filling-in-fields-in-the-import-spreadsheet.md b/docs/tutorials/es/filling-in-fields-in-the-import-spreadsheet.md
index bced9e048..aed14f9d2 100644
--- a/docs/tutorials/es/filling-in-fields-in-the-import-spreadsheet.md
+++ b/docs/tutorials/es/filling-in-fields-in-the-import-spreadsheet.md
@@ -17,15 +17,16 @@ subcategory: 2u48reCb68K48EAcm86ccM
 
 En VTEX, se puede [importar productos y SKU de forma masiva a través de una plantilla](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#plantilla). Para entender el significado de cada uno de los campos, vea a continuación una descripción completa de la lista de campos de Producto y SKU que aparecen en la plantilla.
 
-<div class="alert alert-danger">
-  <p>Al rellenar <b>CaptionLink</b>, <b>DepartamentName</b>, <b>CategoryName</b> y <b>Brand</b>, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX.  Consulta la lista de palabras reservadas a continuación.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Al rellenar **CaptionLink**, **DepartamentName**, **CategoryName** y **Brand**, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX.  Consulta la lista de palabras reservadas a continuación.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 __SkuId:__ número único de identificación del SKU. Si este campo ya está rellenado, no puede modificarlo. Para agregar un nuevo SKU, deje la columna vacía.
 
diff --git a/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 9f427c9b9..d754b941d 100644
--- a/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/es/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -35,4 +35,4 @@ Los siguientes campos son opcionales en la plantilla, se exportan solo para exhi
 - **Ref ID (View Only):** código de referencia único utilizado para facilitar la organización del catálogo de productos. Este id generalmente es creado por los sistemas internos de la tienda.
 - **EAN (View Only):** código de identificación único del SKU (código de barras).
 
-<div class="alert alert-warning">Plantillas de precios utilizadas para importación tienen un límite de tamaño de 1 MB. Si su plantilla actual excede este límite, le recomendamos dividirla en varios archivos, <strong>asegurándose de que los precios que se refieren al mismo SKU se mantengan juntos en la misma plantilla</strong>.</div>
+>⚠️ Plantillas de precios utilizadas para importación tienen un límite de tamaño de 1 MB. Si su plantilla actual excede este límite, le recomendamos dividirla en varios archivos, **asegurándose de que los precios que se refieren al mismo SKU se mantengan juntos en la misma plantilla**.
diff --git a/docs/tutorials/es/filtering-all-orders.md b/docs/tutorials/es/filtering-all-orders.md
index 35cf3072b..ffe812366 100644
--- a/docs/tutorials/es/filtering-all-orders.md
+++ b/docs/tutorials/es/filtering-all-orders.md
@@ -65,9 +65,7 @@ Para buscar en todos los pedidos, ingresa el término deseado en la casilla de b
 
 ![search_bar_without_time_limit_ES](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/3e96ddad7e6e25df9bfc57510655390b/search_bar_without_time_limit_ES.png)
 
-<div class="alert alert-danger">
-La búsqueda en todos los pedidos no se puede asociar a otros filtros. Es decir, al remover el límite de fechas de búsqueda, cualquier filtro activo pasa a estar inactivo. Si se remueve el término de búsqueda o se desactiva el botón de alternancia <i class="fas fa-toggle-off"></i>, los filtros configurados anteriormente se vuelven a activar.
-</div>
+>❗ La búsqueda en todos los pedidos no se puede asociar a otros filtros. Es decir, al remover el límite de fechas de búsqueda, cualquier filtro activo pasa a estar inactivo. Si se remueve el término de búsqueda o se desactiva el botón de alternancia <i class="fas fa-toggle-off"></i>, los filtros configurados anteriormente se vuelven a activar.
 
 ### Buscar asociando filtros
 
diff --git a/docs/tutorials/es/filters.md b/docs/tutorials/es/filters.md
index 19bc7793d..5d08874ec 100644
--- a/docs/tutorials/es/filters.md
+++ b/docs/tutorials/es/filters.md
@@ -21,17 +21,13 @@ Cuando un cliente selecciona un filtro (precio, color, tamaño y marca), esta in
 
 **VTEX Intelligent Search** utiliza el contexto de los productos que se muestran como resultados de la búsqueda para saber exactamente qué filtros deben mostrarse al cliente, de acuerdo con la configuración del catálogo.
 
-<div class="alert alert-info">
-  <p>El orden de los filtros de marca, departamento, categoría y subcategoría se determina por la cantidad de productos registrados en cada uno de los filtros.</p>
-</div>
+>ℹ️ El orden de los filtros de marca, departamento, categoría y subcategoría se determina por la cantidad de productos registrados en cada uno de los filtros.
 
 Ejemplo: tenga en cuenta que el filtro *Tamaño* está registrado en el catálogo de una tienda y que solo el producto *zapatilla* tiene la especificación *Tamaño* rellenada. En una búsqueda por el término *zapatilla*, *Tamaño* aparecerá como un filtro. En la búsqueda de cualquier otro término, como *gorra*, esta especificación no se mostrará como un filtro.
 
 El resultado de búsqueda no mostrará una especificación si solo existe como filtro o si el cliente accede a ella a través del menú de la tienda. Ejemplo: si el cliente selecciona el filtro Electrodomésticos directamente en el menú, no se mostrará Departamento como filtro lateral.
 
-<div class="alert alert-info">
-  <p>Si el resultado de la búsqueda devuelve más de 30 mil productos, se omitirán algunos valores de filtros, ya que solo se considerarán las especificaciones de una parte de estos productos.</p>
-</div>
+>ℹ️ Si el resultado de la búsqueda devuelve más de 30 mil productos, se omitirán algunos valores de filtros, ya que solo se considerarán las especificaciones de una parte de estos productos.
 
 La funcionalidad Filtros tiene las siguientes funciones:
 
@@ -46,6 +42,4 @@ La funcionalidad Filtros tiene las siguientes funciones:
 
 Consulte la guía [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) en el Developer Portal para obtener más detalles técnicos sobre el uso de filtros.
 
-<div class="alert alert-warning">
-  <p>Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.</p>
-</div>
+>⚠️ Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.
diff --git a/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
index e88b290e6..bfc08f98c 100644
--- a/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/es/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -38,9 +38,7 @@ Para entrar en contacto:
 4. Rellene el campo __Contactar al seller__.    
 5. Haga clic en el botón __Enviar__.     
 
-<div class="alert alert-info">
-El potencial partner comercial recibirá un email con la información ingresada. Si el interés es mutuo, este podrá ponerse en contacto e iniciar una negociación de los términos del acuerdo entre marketplace y seller.
-</div>
+>ℹ️ El potencial partner comercial recibirá un email con la información ingresada. Si el interés es mutuo, este podrá ponerse en contacto e iniciar una negociación de los términos del acuerdo entre marketplace y seller.
 
 ## Perfil de la tienda
 ![Network profile ES](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/ae9aa04caa553c344ab6e5f958469e68/Marketplace_store_profile_ES.gif)
diff --git a/docs/tutorials/es/find-sellers.md b/docs/tutorials/es/find-sellers.md
index 77f9fd3c4..c63d1f632 100644
--- a/docs/tutorials/es/find-sellers.md
+++ b/docs/tutorials/es/find-sellers.md
@@ -19,10 +19,8 @@ La página **Encontrar sellers** facilita la búsqueda y comunicación con selle
 
 Para utilizar la página,debes crear un **Perfil de la tienda**,según se describe en la documentación.
 
-<div class="alert alert-info">
-  Ten en cuenta que <b>Encontrar sellers</b> es una herramienta que promueve el contacto entre posibles partners, sin embargo, no es un paso obligatorio para operar como marketplace y seller en VTEX.
-Si deseas operar como marketplace y seller simultáneamente, lee la documentación <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace">Estrategias de marketplace en VTEX.</a>
-</div>  
+>ℹ️ Ten en cuenta que **Encontrar sellers** es una herramienta que promueve el contacto entre posibles partners, sin embargo, no es un paso obligatorio para operar como marketplace y seller en VTEX.
+> Si deseas operar como marketplace y seller simultáneamente, lee la documentación [Estrategias de marketplace en VTEX.](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace)  
 
 Para acceder a la lista de sellers registrados, ve a **Marketplace > Encontrar sellers** o ingresa **Encontrar sellers** en la barra de búsqueda.
 
@@ -52,6 +50,4 @@ Para ponerte en contacto:
 1. Rellena el campo **Contactar seller**.
 1. Haz clic en el botón **Enviar**.
 
-<div class="alert alert-info">
-El partner potencial recibirá un email con la información incluida. Si el interés es mutuo,el encargado del seller o el marketplace puede ponerse en contacto contigo y negociar las condiciones del acuerdo entre marketplace y seller.
-</div>
+>ℹ️ El partner potencial recibirá un email con la información incluida. Si el interés es mutuo,el encargado del seller o el marketplace puede ponerse en contacto contigo y negociar las condiciones del acuerdo entre marketplace y seller.
diff --git a/docs/tutorials/es/fromto-of-payment-means-on-webservice.md b/docs/tutorials/es/fromto-of-payment-means-on-webservice.md
index 4c788572c..2d46cc87e 100644
--- a/docs/tutorials/es/fromto-of-payment-means-on-webservice.md
+++ b/docs/tutorials/es/fromto-of-payment-means-on-webservice.md
@@ -15,9 +15,11 @@ legacySlug: depara-de-los-medios-de-pago-en-el-web-service
 subcategory: 1vwB9FtTSQmcSewQw02QoW
 ---
 
-<div class="alert alert-danger"><p>Atenção: sólo los métodos SOAP correspondientes al <strong>catálogo</strong> son válidos.</p>
-<p><strong>Todos los demás métodos están descontinuados.</strong></p>
-<p>Utilice las API REST equivalentes disponibles en nuestro <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: sólo los métodos SOAP correspondientes al **catálogo** son válidos.
+>
+> **Todos los demás métodos están descontinuados.**
+>
+> Utilice las API REST equivalentes disponibles en nuestro [Developer Docs](//help.vtex.com/developer-docs/).
 
 El Web Service de pagos utiliza algunos códigos para cada una de las formas de pagos disponibles en la área del PCI Gateway. Ese código de cada pago es fijo y no depende del integrador.
 
diff --git a/docs/tutorials/es/generating-a-har-file.md b/docs/tutorials/es/generating-a-har-file.md
index cf9e6a67e..a74cfef38 100644
--- a/docs/tutorials/es/generating-a-har-file.md
+++ b/docs/tutorials/es/generating-a-har-file.md
@@ -21,12 +21,9 @@ Una feature útil para esto es el log de requests generado por la herramienta de
 
 A través de él usted puede generar un __archivo HAR__, que contiene información detallada sobre cada request. Después, basta con enviarlo a nuestro equipo de soporte.
 
-<div class="alert alert-warning">
-El archivo HAR contiene información sensible sobre su tienda. Compartalo sólo con el equipo de soporte VTEX.
-</div>
+>⚠️ El archivo HAR contiene información sensible sobre su tienda. Compartalo sólo con el equipo de soporte VTEX.
 
-<div class="alert alert-warning"> Abajo tenemos el procedimiento para generar el  archivo HAR por <strong>Google Chrome</strong>, que es el modo que nosotros más recomendamos. Si desea hacer el proceso por medio de otros navegadores, como Mozilla Firefox o Microsoft Edge, verifique el procedimiento correcto <a href="https://support.zendesk.com/hc/pt-br/articles/204410413-Gera%25C3%25A7%25C3%25A3o-de-um-arquivo-HAR-para-resolu%25C3%25A7%25C3%25B5es-de-problemas#h_51858a69-ed0e-45a6-a25d-c9b8ba32ae32"> en este enlace /a>.
-</div>
+>⚠️ Abajo tenemos el procedimiento para generar el  archivo HAR por **Google Chrome**, que es el modo que nosotros más recomendamos. Si desea hacer el proceso por medio de otros navegadores, como Mozilla Firefox o Microsoft Edge, verifique el procedimiento correcto <a href="https://support.zendesk.com/hc/pt-br/articles/204410413-Gera%25C3%25A7%25C3%25A3o-de-um-arquivo-HAR-para-resolu%25C3%25A7%25C3%25B5es-de-problemas#h_51858a69-ed0e-45a6-a25d-c9b8ba32ae32"> en este enlace /a>.
 
 ### Cómo generar el archivo HAR en Google Chrome
 
diff --git a/docs/tutorials/es/geolocalizado-suiteshare.md b/docs/tutorials/es/geolocalizado-suiteshare.md
index c5c54c644..b99919183 100644
--- a/docs/tutorials/es/geolocalizado-suiteshare.md
+++ b/docs/tutorials/es/geolocalizado-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: geolocalizado
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/geolocation-at-checkout.md b/docs/tutorials/es/geolocation-at-checkout.md
index 8138f7492..18c175fcd 100644
--- a/docs/tutorials/es/geolocation-at-checkout.md
+++ b/docs/tutorials/es/geolocation-at-checkout.md
@@ -44,9 +44,7 @@ Cuando tengas la API, siga los pasos adelante:
 
 ![Geolocalizacao 1 ES](https://images.ctfassets.net/alneenqid6w5/3XL4C5B5SM48uGaeocUiw4/22560c9c40cc587cb7fa0884e48fcd5f/Geolocalizacao_1_ES.png)
 
-<div class="alert alert-info">
-En algunos paises, el Google Maps no hace un mapping de buena calidad, lo que hace con que las direcciones queden mal escritas o incorrectas. En estes casos, la dirección debe ser alterada directamente en el mapa.
-  </div>
+>ℹ️ En algunos paises, el Google Maps no hace un mapping de buena calidad, lo que hace con que las direcciones queden mal escritas o incorrectas. En estes casos, la dirección debe ser alterada directamente en el mapa.
 
 ### Configurando el poligono
 
diff --git a/docs/tutorials/es/gift-card.md b/docs/tutorials/es/gift-card.md
index 8499b2a24..93e539f2f 100644
--- a/docs/tutorials/es/gift-card.md
+++ b/docs/tutorials/es/gift-card.md
@@ -46,13 +46,9 @@ Para crear un nuevo vale de compra, siga los pasos a continuación:
   <li><b>Colección</b>: determina la colección de productos que define los ítems a los que se puede aplicar el vale.</li>
 </ul><br>
 
-<div class="alert alert-warning">
-<strong>Atención</strong>: los campos “Valor” y “Fecha de vencimiento” deben completarse de forma <strong>obligatoria</strong>. De lo contrario, el vale no se guardará.
-</div>
+>⚠️ **Atención**: los campos “Valor” y “Fecha de vencimiento” deben completarse de forma **obligatoria**. De lo contrario, el vale no se guardará.
 
-<div class="alert alert-danger">
-La funcionalidad de creación de tarjetas de regalo por colecciones de productos no está funcionando. Hay más información sobre este problema en el artículo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
-</div>
+>❗ La funcionalidad de creación de tarjetas de regalo por colecciones de productos no está funcionando. Hay más información sobre este problema en el artículo [Restricting the use of GiftCards to a collection of products does not work](https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank).
 
 Después de completar los campos correctamente, el usuario puede seleccionar hasta tres opciones de configuración: 
 <ul>
@@ -63,9 +59,7 @@ Después de completar los campos correctamente, el usuario puede seleccionar has
 <br>
   <li>Por último, haga clic en el botón <b>Guardar</b>.</li>
 <br>
-<div class="alert alert-info">
-La creación de cupones no tiene límite, sin embargo, solo se pueden exportar 8000 cupones a la vez.
-</div>
+>ℹ️ La creación de cupones no tiene límite, sin embargo, solo se pueden exportar 8000 cupones a la vez.
 
 </ol>
 
@@ -86,13 +80,9 @@ Para crear más de un nuevo vale de compra al mismo tiempo (un lote), siga los p
   <li><b>Fecha de vencimiento</b>: es la fecha de vigencia de uso de todos los vales de este lote.</li>
   <li><b>Colección</b>: determina la colección de productos que define los ítems a los que se pueden aplicar los vales.</li>
 <br>
-<div class="alert alert-warning">
-<strong>Atención</strong>: los campos “Cantidad de vales”, “Valor” y “Fecha de vencimiento” deben completarse de forma <strong>obligatoria</strong>. De lo contrario, los vales no se guardarán.
-</div>
+>⚠️ **Atención**: los campos “Cantidad de vales”, “Valor” y “Fecha de vencimiento” deben completarse de forma **obligatoria**. De lo contrario, los vales no se guardarán.
 <br>
-<div class="alert alert-danger">
-La funcionalidad de creación de tarjetas de regalo por colecciones de productos no está funcionando. Hay más información sobre este problema en el artículo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
-</div>
+>❗ La funcionalidad de creación de tarjetas de regalo por colecciones de productos no está funcionando. Hay más información sobre este problema en el artículo [Restricting the use of GiftCards to a collection of products does not work](https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank).
 <br>
   <li><b>Recargable</b>: mientras estos vales estén disponibles, sus saldos pueden alterarse.</li>
   <li><b>Reutilizable</b>: puede hacer nuevas compras con estos vales hasta que sus valores sean utilizados en su totalidad.</li>
@@ -103,9 +93,7 @@ Aparecerá una nueva pantalla confirmando que se ha generado el número solicita
 <br>
   <li>Por último, haga clic en el botón <b>Volver</b>.</li>
 <br>
-<div class="alert alert-info">
-La creación de cupones no tiene límite, sin embargo, solo se pueden exportar 8000 cupones a la vez.
-</div>
+>ℹ️ La creación de cupones no tiene límite, sin embargo, solo se pueden exportar 8000 cupones a la vez.
   </ol>
 
 ## Cómo configurar un Vale de Compra como un método de pago 
diff --git a/docs/tutorials/es/good-practices-for-the-golive-of-my-store.md b/docs/tutorials/es/good-practices-for-the-golive-of-my-store.md
index e52d70d2d..f18480909 100644
--- a/docs/tutorials/es/good-practices-for-the-golive-of-my-store.md
+++ b/docs/tutorials/es/good-practices-for-the-golive-of-my-store.md
@@ -18,35 +18,25 @@ subcategory: wz3FvYTctwuCwG206QUAi
 ## WarRoom pre-Golive
 Aún teniendo definidos y desarrollados todos los flujos de integraciones y de navegación, uno de los momentos más críticos del proyecto son las pruebas end-to-end, donde se validan los flujos de navegación de usuario y se realizan las pruebas de facturación. Seguramente, surgirán temas importantes a resolver. 
 
-<div class="alert alert-info">
-Lo más importante es que en una misma mesa se encuentren todos los tomadores de decisión (VTEX, Cliente, Agencia) para lograr optimizar la sinergia y resiliencia del equipo ante cualquier issue o duda que surja.
-</div>
+>ℹ️ Lo más importante es que en una misma mesa se encuentren todos los tomadores de decisión (VTEX, Cliente, Agencia) para lograr optimizar la sinergia y resiliencia del equipo ante cualquier issue o duda que surja.
 
 ## Checklist de validación pre-Golive
 La siguiente es una planilla que contiene un checklist sugerido con los principales puntos de atención al momento de validar la tienda, previamente a realizar el golive al público: [Checklist de Validación Pregolive](https://docs.google.com/spreadsheets/d/1demkpSZ2h7ut5TsKwiPdmK029BfaCp0wabeGADfA_W0/edit)
 
-<div class="alert alert-info">
-Momentos recomendados para validación:
-1. Un mes antes del Golive (dará tiempo a accionar si se detecta un issue bloqueante).
-2. Una semana antes del Golive (dará tiempo a accionar si quedó demorado u olvidado algún tema menor).
-</div>
+>ℹ️ Momentos recomendados para validación:
+> 1. Un mes antes del Golive (dará tiempo a accionar si se detecta un issue bloqueante).
+> 2. Una semana antes del Golive (dará tiempo a accionar si quedó demorado u olvidado algún tema menor).
 
 ## Certificado de seguridad y apuntar dominio a VTEX
 Este proceso es realizado en el momento de GoLive de la tienda. Habilita al actual responsable de su dominio a que apunte hacia VTEX. Luego de esta acción, al ingresar a www.mitienda.com, su nueva tienda estará apuntada hacia VTEX.
 
-<div class="alert alert-warning">
-Si se utiliza Cloudflare como zona DNS, puede ser necesario deshabilitar el proxy DNS (y en consecuencia deshabilitar los servicios CDN y WAF de CloudFlare). Puedes encontrar más información en el artículo <a href="https://help.vtex.com/es/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">Cómo deshabilitar el proxy de Cloudflare</a>.
-</div>
+>⚠️ Si se utiliza Cloudflare como zona DNS, puede ser necesario deshabilitar el proxy DNS (y en consecuencia deshabilitar los servicios CDN y WAF de CloudFlare). Puedes encontrar más información en el artículo [Cómo deshabilitar el proxy de Cloudflare](https://help.vtex.com/es/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 Ver los detalles del proceso aquí: [Configurando el apuntamiento del DNS para VTEX](/es/tutorial/configurando-el-apuntamiento-del-dns-para-vtex/).
 
-<div class="alert alert-info">
-La recomendación principal es que un funcionario del cliente, con conocimientos y experiencia en DNS, realice estas configuraciones. Si esta configuración no es correcta, su tienda puede sufrir una caída por un error humano. Si surge algún problema, se debe actuar rápidamente para corregirlo y retornar la estabilidad a las operaciones.
-</div>
+>ℹ️ La recomendación principal es que un funcionario del cliente, con conocimientos y experiencia en DNS, realice estas configuraciones. Si esta configuración no es correcta, su tienda puede sufrir una caída por un error humano. Si surge algún problema, se debe actuar rápidamente para corregirlo y retornar la estabilidad a las operaciones.
 
 ## Canal de comunicación durante Golive
 Mientras se desarrolla el proceso de Golive, adicionalmente al WarRoom, suele ser conveniente mantener un canal activo de comunicación, para poder compartir issues críticos o requerimientos urgentes. Todos deben estar alineados con respecto al camino a seguir.
 
-<div class="alert alert-info">
-Para esto, suele ser conveniente abrir un canal de Slack, Whatsapp o Skype, durante la semana anterior y posterior al Golive, donde se encuentren todos los participantes del proyecto.
-</div>
+>ℹ️ Para esto, suele ser conveniente abrir un canal de Slack, Whatsapp o Skype, durante la semana anterior y posterior al Golive, donde se encuentren todos los participantes del proyecto.
diff --git a/docs/tutorials/es/google-integration-warnings.md b/docs/tutorials/es/google-integration-warnings.md
index e1076c0c6..b36741776 100644
--- a/docs/tutorials/es/google-integration-warnings.md
+++ b/docs/tutorials/es/google-integration-warnings.md
@@ -15,6 +15,4 @@ legacySlug: avisos-de-integracion-de-google
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning">
-Contenido en traducción.
-</div>
+>⚠️ Contenido en traducción.
diff --git a/docs/tutorials/es/google-pay-beta.md b/docs/tutorials/es/google-pay-beta.md
index 047935aa9..359632e9c 100644
--- a/docs/tutorials/es/google-pay-beta.md
+++ b/docs/tutorials/es/google-pay-beta.md
@@ -23,9 +23,7 @@ Google Pay™ es un servicio de pagos digitales que permite a los usuarios no co
 
 Los términos de la API de Google Pay se aplican siempre que el administrador de la tienda ofrezca Google Pay como medio de pago. Para leer los términos, accede a [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
 
-<div class="alert alert-warning">
-<p>Google Pay no está disponible para Checkout V5 o versiones anteriores de Checkout.h</p>
-</div>
+>⚠️ Google Pay no está disponible para Checkout V5 o versiones anteriores de Checkout.h
 
 ## Activar Google Pay
 
diff --git a/docs/tutorials/es/hiring-the-security-certificate-sll.md b/docs/tutorials/es/hiring-the-security-certificate-sll.md
index 18c4157b7..e7f537e69 100644
--- a/docs/tutorials/es/hiring-the-security-certificate-sll.md
+++ b/docs/tutorials/es/hiring-the-security-certificate-sll.md
@@ -24,6 +24,4 @@ Siempre que tu accedes una página segura, que sea protegida por un certificado
 No necesita más solicitar la compra del certificado SSL (provido antes por Digicert).
 El certificado ahora es creado vía Let’s Encrypt y la creación es de responsabilidad de VTEX y es hecha [en el _GoLive_ de la tienda](https://help.vtex.com/es/tutorial/configurando-el-apuntamiento-del-dns-para-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-Ten en cuenta que VTEX genera un certificado SSL para tu tienda y garantiza su renovación automática. Por lo tanto, no recomendamos instalar ningún otro certificado. Sin embargo, si necesitas instalar otro certificado, solicítalo a nuestro [soporte](https://help.vtex.com/es/support)
-</div>
+>⚠️ Ten en cuenta que VTEX genera un certificado SSL para tu tienda y garantiza su renovación automática. Por lo tanto, no recomendamos instalar ningún otro certificado. Sin embargo, si necesitas instalar otro certificado, solicítalo a nuestro [soporte](https://help.vtex.com/es/support)
diff --git a/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
index eef69f568..c8696e2a4 100644
--- a/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/es/how-can-i-change-the-domain-of-my-store.md
@@ -17,9 +17,7 @@ subcategory: yMp6sKDiJEi66CGAIQ4ma
 
 El cambio de domínios es el cambio de la dirección de la tienda. Por ejemplo, si la tienda VTEX tiene el domínio **_mitienda.com_** y desea cambiar para **_nuestratienda.com_**, debe seguir los pasos de ese tutorial.
 
-<div class="alert alert-warning">
-Sugerimos NO borrar el HOST creado anteriormente, mientras que la nueva configuración no está propagada (Tiempo promedio de propagación: 15 minutos).
-</div>
+>⚠️ Sugerimos NO borrar el HOST creado anteriormente, mientras que la nueva configuración no está propagada (Tiempo promedio de propagación: 15 minutos).
 
 La plataforma VTEX está lista para cambios de domínio sin impactos negativos. Sólo es necesario seguir los pasos abajo:
 
diff --git a/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
index 6cfa250f4..4a0fcdd8a 100644
--- a/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/es/how-can-i-create-a-field-in-master-data.md
@@ -43,7 +43,7 @@ Verifique el procedimiento:
 12. Haga clic en el botón rojo __Ok.__
 13. Haga clic en el botón gris __Ok.__
 
-<div class="alert alert-info">Puede encontrar más información sobre <strong>Configuraciones generales</strong> y <strong>Configuraciones de búsqueda y filtro</strong> en la sesión <strong>Cómo configurar</strong> del artículo <a href="https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Crear entidad de datos</a>.</div>
+>ℹ️ Puede encontrar más información sobre **Configuraciones generales** y **Configuraciones de búsqueda y filtro** en la sesión **Cómo configurar** del artículo [Crear entidad de datos](https://help.vtex.com/es/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar).
 
 ![crear campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
diff --git a/docs/tutorials/es/how-can-i-create-callcenter-user.md b/docs/tutorials/es/how-can-i-create-callcenter-user.md
index 07301148c..c3912611f 100644
--- a/docs/tutorials/es/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/es/how-can-i-create-callcenter-user.md
@@ -43,6 +43,5 @@ Para crear un usuario con el rol de televentas, sigue los pasos a continuación:
 
 ![GIF animado que muestra cómo crear un usuario de televentas](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/4d432b47fca70a6203a566bbe9d61abc/Adicionar_perfil_ES.gif)
 
-<div class="alert alert-warning">Al crear un <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evita incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televentas junto con otros recursos. De lo contrario, puede que el perfil no funcione de forma esperada.
-</div>
+>⚠️ Al crear un [perfil](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#), evita incluir [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) de televentas junto con otros recursos. De lo contrario, puede que el perfil no funcione de forma esperada.
 
diff --git a/docs/tutorials/es/how-can-i-create-cluster-of-customers.md b/docs/tutorials/es/how-can-i-create-cluster-of-customers.md
index 150a11dfa..eb783ab73 100644
--- a/docs/tutorials/es/how-can-i-create-cluster-of-customers.md
+++ b/docs/tutorials/es/how-can-i-create-cluster-of-customers.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Un clúster es una agrupación de los clientes de una mismo segmento de clientes. Es un enfoque que sirve para identificar perfiles y obtener una mayor llegada en las actividades relacionadas con los usuarios.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 Estos datos son muy válidos para el marketing y la publicidad, por lo que se puede configurar su clúster y cuáles son las reglas para un cliente.
 
diff --git a/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md b/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md
index aef4fd4f9..2be8e17bc 100644
--- a/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md
+++ b/docs/tutorials/es/how-can-i-export-from-the-newsletter-database-using-master-data.md
@@ -26,6 +26,4 @@ Para exportar su base de clientes que han optado por recibir newsletter, siga el
 
    En la planilla que ha sido enviada a su e-mail habrá una columna titulada `isNewsletterOptIn`, que asigna el valor **true** para los clientes que reciben newsletter y **false** para aquellos que no la reciben.
 
-<div class="alert alert-warning">
-  <p>Esta opción sólo es válida para tiendas que tienen registro de newsletter por el Master Data. Si su tienda no tiene esa configuración y ella todavía se hace por un control de página, vea el artículo <a href="https://help.vtex.com/es/tutorial/como-configuro-la-captacion-de-newsletter-por-el-master-data--frequentlyAskedQuestions_1816">Configurar la captación de newsletter por Master Data</a> para saber como configurar.</p>
-</div>
+>⚠️ Esta opción sólo es válida para tiendas que tienen registro de newsletter por el Master Data. Si su tienda no tiene esa configuración y ella todavía se hace por un control de página, vea el artículo [Configurar la captación de newsletter por Master Data](https://help.vtex.com/es/tutorial/como-configuro-la-captacion-de-newsletter-por-el-master-data--frequentlyAskedQuestions_1816) para saber como configurar.
diff --git a/docs/tutorials/es/how-change-order-works-beta.md b/docs/tutorials/es/how-change-order-works-beta.md
index 9b198755f..abbb792c4 100644
--- a/docs/tutorials/es/how-change-order-works-beta.md
+++ b/docs/tutorials/es/how-change-order-works-beta.md
@@ -15,9 +15,7 @@ legacySlug: como-funciona-modificar-pedido-beta
 subcategory: 3LQ1Tl0u4frEOd45BkjFAm
 ---
 
-<div class="alert alert-info">
-Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar <b>Modificar pedido (Beta)</b>, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a> e informa el nombre del <a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> en que deseas activarla.
-</div>
+>ℹ️ Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar **Modificar pedido (Beta)**, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support) e informa el nombre del [account name(s)](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) en que deseas activarla.
 
 La funcionalidad **Modificar pedido (beta)** brinda la posibilidad de editar un pedido de múltiples maneras, ya sea para atender las preferencias del cliente, abordar la falta de disponibilidad de productos u otras razones. Los principales tipos de modificaciones en el pedido son:
 
diff --git a/docs/tutorials/es/how-cnova-via-varejo-integration-works.md b/docs/tutorials/es/how-cnova-via-varejo-integration-works.md
index 6e20cd569..e1a07d8d5 100644
--- a/docs/tutorials/es/how-cnova-via-varejo-integration-works.md
+++ b/docs/tutorials/es/how-cnova-via-varejo-integration-works.md
@@ -83,11 +83,11 @@ _`Ej.1:` promoción del 10% de descuento para una categoría determinada_.
 
 _`Ej.2:` SKU X está R$ 10,00 en la política comercial usada en CNova/Via Varejo y tiene un precio fijo de R$ 15,00 para esta misma política. La integración enviará R$ 15,00.
 
-<div class="alert alert-warning">
-OBS: como la forma de pago se hace en el marketplace, las reglas de pago son determinadas por este. Por eso, no conseguimos enviar precios diferenciales en función de la forma de pago.
-<br />
-<em>Ej.: si en VTEX existen intereses configurados para pagos en cuotas, el precio enviado continuará siendo lo que la simulación de fulfillment devuelve.</em>
-</div>
+>⚠️ OBS: como la forma de pago se hace en el marketplace, las reglas de pago son determinadas por este. Por eso, no conseguimos enviar precios diferenciales en función de la forma de pago.
+>
+>
+> 
+> *Ej.: si en VTEX existen intereses configurados para pagos en cuotas, el precio enviado continuará siendo lo que la simulación de fulfillment devuelve.*
 
 ## 4. Promociones
 
@@ -112,15 +112,19 @@ Cuando se hace un pedido en el marketplace hay algunos puntos que influyen en su
 
 En esta integración existen dos puntos que influenciarán en la entrega: __Cálculo del Flete__ y el __Tiempo de Preparación de Envío__. La suma de los dos será el __Tiempo de Entrega Total__.
 
-<div class="alert alert-info">
-Ej.:
-<br />
-Flete Normal = 3 días.
-<br />
-Tiempo de Costo = 2 días.
-<br />
-Tiempo Total de Entrega = 5 días.
-</div>
+>ℹ️ Ej.:
+>
+>
+> 
+> Flete Normal = 3 días.
+>
+>
+> 
+> Tiempo de Costo = 2 días.
+>
+>
+> 
+> Tiempo Total de Entrega = 5 días.
 
 - __Flete__
 
@@ -132,46 +136,78 @@ El comerciante tiene también la posibilidad de registrar en CNova/Via Varejo un
 
 El tiempo de preparación de envío se basa en la suma del campo `Tiempo de Costo` en el Stock con el `Tiempo de Costo` en el Muelle. Y nosotros enviamos el mismo tiempo de preparación de forma masiva para todos los productos.
 
-<div class="alert alert-info">
-Ej.:
-<br />
-<strong>Stock A</strong>
-<br />
-- Muelle 1: Tiempo de Costo = 3 días.
-<br />
-<strong>Stock B</strong>
-<br />
-- Muelle 1: Tiempo de Costo = 5 días.
-<br />
-<br />
-<strong>Muelle 1:</strong>
-<br />
-- Tiempo de Costo = 2 días.
- <br />
-<br />
-Un pedido con Tiempo de Flete = 3 días, se quedará con un Tiempo Total de Entrega diferente dependiendo de dónde salga el producto.
-<br />
-<br />
-<strong>Saliendo del Muelle A:</strong>
-<br />
-- Tiempo de preparación = 3 + 2 (muelle 1) = 5 días.
-<br />
-- Tiempo de flete = 3 días.
-<br />
-- Tiempo total de entrega = 8 días.
-<br />
-<strong>Saliendo del Muelle B:</strong>
-<br />
-- Tiempo de preparación = 5 + 2 (muelle 1) = 7 días
-<br />
-- Tiempo de flete = 3 días.
-<br />
-- Tiempo total de entrega = 10 días.
-</div>
-
-<div class="alert alert-warning">
-OBS: en caso de utilizar la tabla de contingencia para hacer el cálculo del flete, CNova no consulta a VTEX. De esta forma, el único factor que se tendrá en cuenta para el <strong>Tiempo Total de Entrega</strong>, será el <strong>Flete</strong> proporcionado por ellos, ignorando el <strong>Tiempo de Preparación</strong>. Se debe tener cuidado con esto, pues puede generar divergencias en el <strong>Tiempo Total de Entrega</strong>.
-</div>
+>ℹ️ Ej.:
+>
+>
+> 
+> **Stock A**
+>
+>
+> 
+> - Muelle 1: Tiempo de Costo = 3 días.
+>
+>
+> 
+> **Stock B**
+>
+>
+> 
+> - Muelle 1: Tiempo de Costo = 5 días.
+>
+>
+> 
+>
+>
+> 
+> **Muelle 1:**
+>
+>
+> 
+> - Tiempo de Costo = 2 días.
+>
+>
+> 
+>
+>
+> 
+> Un pedido con Tiempo de Flete = 3 días, se quedará con un Tiempo Total de Entrega diferente dependiendo de dónde salga el producto.
+>
+>
+> 
+>
+>
+> 
+> **Saliendo del Muelle A:**
+>
+>
+> 
+> - Tiempo de preparación = 3 + 2 (muelle 1) = 5 días.
+>
+>
+> 
+> - Tiempo de flete = 3 días.
+>
+>
+> 
+> - Tiempo total de entrega = 8 días.
+>
+>
+> 
+> **Saliendo del Muelle B:**
+>
+>
+> 
+> - Tiempo de preparación = 5 + 2 (muelle 1) = 7 días
+>
+>
+> 
+> - Tiempo de flete = 3 días.
+>
+>
+> 
+> - Tiempo total de entrega = 10 días.
+
+>⚠️ OBS: en caso de utilizar la tabla de contingencia para hacer el cálculo del flete, CNova no consulta a VTEX. De esta forma, el único factor que se tendrá en cuenta para el **Tiempo Total de Entrega**, será el **Flete** proporcionado por ellos, ignorando el **Tiempo de Preparación**. Se debe tener cuidado con esto, pues puede generar divergencias en el **Tiempo Total de Entrega**.
 
 #### Precio y disponibilidad:
 
diff --git a/docs/tutorials/es/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md b/docs/tutorials/es/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
index 4fb925608..6ff97e342 100644
--- a/docs/tutorials/es/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
+++ b/docs/tutorials/es/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
@@ -19,9 +19,7 @@ Captación de newsletter es un formulario que puede insertarse en cualquier pág
 
 Este artículo tiene como objetivo ayudar en la configuración para la captación de los emails de clientes interesados en recibir newsletter por el Master Data.
 
-<div class="alert alert-warning">
-El control vtex.cmc:newsletterOptIn está descontinuado y ya no se debe utilizar.
-</div>
+>⚠️ El control vtex.cmc:newsletterOptIn está descontinuado y ya no se debe utilizar.
 
 Esta opción de configuración por el Master Data ofrece la comodidad de tratar los datos de todos los clientes por el mismo lugar, visto que todos los clientes registrados en la tienda ya están en el Master Data. O sea, es el lugar propio para el mantenimiento y las acciones relacionadas con los clientes y mantener todos los registros en un único lugar es facilitar el día a día.
 
diff --git a/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index 1b3023b50..7f991f649 100644
--- a/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/es/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -23,10 +23,11 @@ El módulo Layout abarca home, catálogo (búsqueda, categorías y productos), l
 
 Es posible cambiar el protocolo en todas las carpetas de una sola vez con el uso de nuestra API, documentada [en esta colección de Postman](https://developers.vtex.com/reference/change-uri-schema).
 
-<div class="alert alert-warning">
-<p><strong>Atención:</strong> evite tener el protocolo HTTPS activado sólo en algunas páginas. Al acceder a una página HTTPS, luego ir a una página HTTP de la misma tienda, el navegador intentará leer sus recursos forzosamente en HTTPS, y esto puede generar problemas.</p>
-<p>Lo adecuado es activar el HTTPS en todo el sitio de una sola vez.</p>
-<p>Lo mismo vale para los sitios de desktop y mobile (website secundario), donde es necesario tratar el HTTPS de ambos al mismo tiempo.</p></div>
+>⚠️ **Atención:** evite tener el protocolo HTTPS activado sólo en algunas páginas. Al acceder a una página HTTPS, luego ir a una página HTTP de la misma tienda, el navegador intentará leer sus recursos forzosamente en HTTPS, y esto puede generar problemas.
+>
+> Lo adecuado es activar el HTTPS en todo el sitio de una sola vez.
+>
+> Lo mismo vale para los sitios de desktop y mobile (website secundario), donde es necesario tratar el HTTPS de ambos al mismo tiempo.
 
 1. En el Admin VTEX, accede a **Storefront > ** y abra la carpeta **CMS**;
 2. Acceda a **Sites and channels**;
diff --git a/docs/tutorials/es/how-does-reservation-work.md b/docs/tutorials/es/how-does-reservation-work.md
index 377fa0721..45511f57e 100644
--- a/docs/tutorials/es/how-does-reservation-work.md
+++ b/docs/tutorials/es/how-does-reservation-work.md
@@ -31,9 +31,7 @@ Después de ser vendido, un ítem pasa por los siguientes status en el_ stock _d
 
 Puedes seguir el status de la reserva de los ítems a través del Admin VTEX, [como se describe al final de este artículo. ](https://help.vtex.com/es/tutorial/como-se-maneja-la-reserva--tutorials_92#como-seguir-el-status-de-la-reserva)
 
-<div class="alert alert-warning">
-El hecho de añadir productos al carrito no genera reserva ni prioridad. Un ítem solo pasa al status Reserva autorizada tras el cliente finalizar el pedido.
-</div>
+>⚠️ El hecho de añadir productos al carrito no genera reserva ni prioridad. Un ítem solo pasa al status Reserva autorizada tras el cliente finalizar el pedido.
 
 ## Reserva autorizada
 
@@ -49,9 +47,7 @@ _plazo de vencimiento del pago + plazo de reserva en el stock_
     * **cinco días consecutivos:** cuando el día de vencimiento del pago sea miércoles, jueves o viernes.
     * **seis días consecutivos:** cuando el día de vencimiento del pago sea sábado.
 
-<div class="alert alert-danger">
-Los pedidos incompletos tienen un plazo de reserva fijo de 11 días consecutivos. Para saber más, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-encontrar-un-pedido--tutorials_294">Cómo funcionan los pedidos incompletos.</a> 
-</div>
+>❗ Los pedidos incompletos tienen un plazo de reserva fijo de 11 días consecutivos. Para saber más, consulta el artículo [Cómo funcionan los pedidos incompletos.](https://help.vtex.com/es/tutorial/como-encontrar-un-pedido--tutorials_294)
 
 Para el markeplace externo, si la información del tiempo de reserva se envía por el campo `lockTTL`, el tiempo de reserva no será calculado por la plataforma VTEX, es si determinado por la fecha límite en el campo. Esto se hace mediante el llamado [Place order](https://developers.vtex.com/docs/api-reference/checkout-api#put-/api/checkout/pub/orders).
 
@@ -86,9 +82,7 @@ El inventario de una tienda tiene tres unidades de un ítem. Un cliente realiza
 
 Cuando el administrador de la tienda o el ERP actualice la cantidad de ese ítem en el inventario, restando la cantidad vendida, la plataforma actualizará la cantidad de ítems disponibles a 2 unidades, lo cual puede interpretarse como una reducción del _stock_. En este caso, la plataforma tiene solo dos unidades de ese ítem en el inventario y ninguna unidad reservada.
 
-<div class="alert alert-danger">
-Al confirmar el inicio de la preparación, el seller pasa a ser el responsable de la reserva de los ítems del pedido. A partir de ese momento, si hay alguna actualización en el inventario, la plataforma de VTEX desestima la reserva de estos SKU. Por lo tanto, actualiza el inventario de los SKU de un pedido determinado únicamente al momento de la facturación. De este modo, se evitan las diferencias de inventario que dependen de la interacción con la <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integración del backoffice</a> de la tienda.
-</div>
+>❗ Al confirmar el inicio de la preparación, el seller pasa a ser el responsable de la reserva de los ítems del pedido. A partir de ese momento, si hay alguna actualización en el inventario, la plataforma de VTEX desestima la reserva de estos SKU. Por lo tanto, actualiza el inventario de los SKU de un pedido determinado únicamente al momento de la facturación. De este modo, se evitan las diferencias de inventario que dependen de la interacción con la [integración del backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) de la tienda.
 
 ## Cómo seguir el status de la reserva
 
diff --git a/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index d16093e9b..a19df2899 100644
--- a/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/es/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -31,6 +31,4 @@ Usted puede encontrar los dos IDs a través del informe enviado desde el panel d
 
 ![mercalo-livre-pedido-id-es](https://images.ctfassets.net/alneenqid6w5/5JOUHJijbIVncRSfvx5lnC/6cceef1724619d4cd8d332d0e5aad89b/mercalo-livre-pedido-id-es.png)
 
-<div class="alert alert-warning">
-Esta lógica de funcionamiento se aplica a todos los tipos de entrega, con excepción de aquellos que incluyen pickup points. En estos casos, la plataforma sigue utilizando el identificador antiguo.
-</div>
+>⚠️ Esta lógica de funcionamiento se aplica a todos los tipos de entrega, con excepción de aquellos que incluyen pickup points. En estos casos, la plataforma sigue utilizando el identificador antiguo.
diff --git a/docs/tutorials/es/how-does-vtex-search-work.md b/docs/tutorials/es/how-does-vtex-search-work.md
index ca3e42555..6cbf50e79 100644
--- a/docs/tutorials/es/how-does-vtex-search-work.md
+++ b/docs/tutorials/es/how-does-vtex-search-work.md
@@ -38,8 +38,9 @@ De acuerdo con el término buscado, el sistema puede renderizar los siguientes r
 
 Si el término buscado corresponde exactamente al nombre de una carpeta configurada en el CMS (es decir, a una landing page), esa carpeta será renderizada.
 
-<div class="alert alert-warning">
-<b>Atención</b>: para que una carpeta pueda buscarse, esta debe poseer un layout.<br><b>Aunque la búsqueda sea por una carpeta hija, el padre también requiere un layout.</b></div>
+>⚠️ **Atención**: para que una carpeta pueda buscarse, esta debe poseer un layout.
+>
+> **Aunque la búsqueda sea por una carpeta hija, el padre también requiere un layout.**
 
 ### 2. Marca
 
diff --git a/docs/tutorials/es/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md b/docs/tutorials/es/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
index 3d68cd249..f28945259 100644
--- a/docs/tutorials/es/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
+++ b/docs/tutorials/es/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
@@ -25,9 +25,7 @@ Cuando hay más de un elemento en el carrito, el costo del envío dividido por c
 
 Vamos a analizar cómo se calcula la división del costo de envío en un carro con 5 ítems, con un costo total de envío de 200 unidades monetarias:
 
-<div class="alert alert-info">
-Para descubrir el costo de envío de un carrito, haga una <a href="http://help.vtex.com/es/tutorial/simulacion-de-flete"> simulación de flete </a>. Para saber el peso de un SKU, acceda a <strong>Productos y SKUs</strong> en el menú Catálogo y busque por <strong>Peso para Envío</strong>.
-</div>
+>ℹ️ Para descubrir el costo de envío de un carrito, haga una [ simulación de flete ](http://help.vtex.com/es/tutorial/simulacion-de-flete). Para saber el peso de un SKU, acceda a **Productos y SKUs** en el menú Catálogo y busque por **Peso para Envío**.
 
 - __Costo total de envío: __ 200
 - __Peso del producto A: __ 20
diff --git a/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md b/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md
index 7142df077..ddda78676 100644
--- a/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md
+++ b/docs/tutorials/es/how-is-the-platforms-operation-sla-determined.md
@@ -22,9 +22,7 @@ Para determinar las violaciones del SLA, es decir, para contabilizar el tiempo d
 - Interrupciones en la tienda virtual que estén impactando significativamente el número de pedidos realizados, por ejemplo: interrupción de la tienda, acceso lento, error en el checkout.
 - Interrupciones que duren al menos 10 minutos.
 
-<div class="alert alert-warning">
-  <p>No contabilizamos el mantenimiento programado como tiempo de indisponibilidad.</p>
-</div>
+>⚠️ No contabilizamos el mantenimiento programado como tiempo de indisponibilidad.
 
 ## Verificar el status de VTEX
 
diff --git a/docs/tutorials/es/how-long-does-the-platform-take-to-identify-my-payment.md b/docs/tutorials/es/how-long-does-the-platform-take-to-identify-my-payment.md
index 2470e2968..c0ffdf1cd 100644
--- a/docs/tutorials/es/how-long-does-the-platform-take-to-identify-my-payment.md
+++ b/docs/tutorials/es/how-long-does-the-platform-take-to-identify-my-payment.md
@@ -17,9 +17,7 @@ subcategory: 6SJnrkKDjGwSqKkMuQMOmm
 
 Si usted pagó por boleto bancario, la compensación deberá ocurrir en hasta 48 horas hábiles después del pago. Pero quédese tranquilo, generalmente la compensación ocurre antes de este plazo y la liberación de su ambiente se realiza automáticamente después de la confirmación del pago.
 
-<div class="alert alert-warning">
-Si el título no se actualiza en 48 horas, abra un llamado, vía ticket, y envíe la comprobación de pago para que podamos entender lo ocurrido.
-</div>
+>⚠️ Si el título no se actualiza en 48 horas, abra un llamado, vía ticket, y envíe la comprobación de pago para que podamos entender lo ocurrido.
 
 ### Artículos relacionados
 
diff --git a/docs/tutorials/es/how-my-account-works.md b/docs/tutorials/es/how-my-account-works.md
index 4428be054..1d7cdd704 100644
--- a/docs/tutorials/es/how-my-account-works.md
+++ b/docs/tutorials/es/how-my-account-works.md
@@ -177,9 +177,7 @@ Para cambiar la contraseña actual:
 4. Haga clic en el botón `GUARDAR CONTRASEÑA` para completar el cambio de contraseña.  
 ![My Authentication change password ES](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/55e5cdfbb4f5daeb591eadbbccf82183/My_Authentication_change_password_ES.png)
 
-<div class="alert alert-info">
-Si ha olvidado su contraseña, no podrá recuperarla a través del componente de gestión de contraseña. Para ello, debe cerrar la sesión actual, hacer un intento de inicio de sesión con el email y la contraseña, y hacer clic en el link <strong>Olvidé mi contraseña</strong>.
-</div>
+>ℹ️ Si ha olvidado su contraseña, no podrá recuperarla a través del componente de gestión de contraseña. Para ello, debe cerrar la sesión actual, hacer un intento de inicio de sesión con el email y la contraseña, y hacer clic en el link **Olvidé mi contraseña**.
 
 ### Gestión de sesiones 
 
diff --git a/docs/tutorials/es/how-order-authorization-workss.md b/docs/tutorials/es/how-order-authorization-workss.md
index ee586311f..53d99ccce 100644
--- a/docs/tutorials/es/how-order-authorization-workss.md
+++ b/docs/tutorials/es/how-order-authorization-workss.md
@@ -47,7 +47,5 @@ Al ser notificado, el usuario entonces deberá:
  
 Los demás pedidos, clasificados en los rangos de variación de precio cuyas reglas son automatizadas, serán procesados por el sistema automáticamente.
  
-<div class="alert alert-warning">
-No siendo posible configurar la Autorización de pedidos para aprobaciones en cadena o jerárquicas, los pedidos deben ser aprobados por un usuario apenas.
-</div>
+>⚠️ No siendo posible configurar la Autorización de pedidos para aprobaciones en cadena o jerárquicas, los pedidos deben ser aprobados por un usuario apenas.
 
diff --git a/docs/tutorials/es/how-product-name-control-works.md b/docs/tutorials/es/how-product-name-control-works.md
index 665b2b6f0..43dcdb3e6 100644
--- a/docs/tutorials/es/how-product-name-control-works.md
+++ b/docs/tutorials/es/how-product-name-control-works.md
@@ -19,9 +19,7 @@ El control `<vtex.cmc:productName/>` renderiza el nombre del producto según se
 
 Por lo tanto, funciona __apenas en las páginas de producto__.
 
-<div class="alert alert-info">
-El nombre que ese control renderiza es el del <b>producto</b>, no del SKU.
-</div>
+>ℹ️ El nombre que ese control renderiza es el del **producto**, no del SKU.
 
 Este es un ejemplo del código HTML renderizado por el control Product Name.
 
diff --git a/docs/tutorials/es/how-promotion-competition-works.md b/docs/tutorials/es/how-promotion-competition-works.md
index 1f452c9e1..e9cd166b3 100644
--- a/docs/tutorials/es/how-promotion-competition-works.md
+++ b/docs/tutorials/es/how-promotion-competition-works.md
@@ -84,8 +84,7 @@ Por lo tanto, la secuencia de aplicación es:
 
 ![promocao3 ES](https://images.ctfassets.net/alneenqid6w5/1CAcjiuVQECwqcoA288Aey/251351f394db394a008ccdd699e47c6f/promocao3_ES.png)
 
-<div class="alert alert-warning">
-Los pedidos de origen <a href="https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> ((proporcionados por la tienda) y Fulfillment (entregados por la tienda) no permiten la acumulación de promociones, ya que el uso de las mismas en marketplaces VTEX o externos se limita a algunos tipos específicos.</div> 
+>⚠️ Los pedidos de origen [Marketplace](https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406) ((proporcionados por la tienda) y Fulfillment (entregados por la tienda) no permiten la acumulación de promociones, ya que el uso de las mismas en marketplaces VTEX o externos se limita a algunos tipos específicos. 
 
 ## Estrategia de competencia entre promociones
 
@@ -100,8 +99,7 @@ Consulta a continuación las dos estrategias de competencia de promociones:
 - [Competencia por escenario](#competencia-por-escenario)
 - [Competencia por ítem](#competencia-por-item)
 
-<div class="alert alert-info">
-De manera predeterminada, todas las cuentas siguen la estrategia de competencia por escenario. Si el modelo de competencia por ítem se adapta mejor a las necesidades de tu negocio, <a href="https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abre un ticket</a> con nuestro equipo de soporte y solicita el cambio.</div>
+>ℹ️ De manera predeterminada, todas las cuentas siguen la estrategia de competencia por escenario. Si el modelo de competencia por ítem se adapta mejor a las necesidades de tu negocio, [abre un ticket](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) con nuestro equipo de soporte y solicita el cambio.
 
 ### Competencia por escenario
 
diff --git a/docs/tutorials/es/how-proportional-shipping-costs-are-calculated.md b/docs/tutorials/es/how-proportional-shipping-costs-are-calculated.md
index ffc19dfe9..0814bd907 100644
--- a/docs/tutorials/es/how-proportional-shipping-costs-are-calculated.md
+++ b/docs/tutorials/es/how-proportional-shipping-costs-are-calculated.md
@@ -29,9 +29,7 @@ Por ejemplo, en un carrito de compras se calculó que el valor total del flete e
 
 Para facilitar la compresión a los usuarios, utilizamos el término «peso» en vez de «masa» en nuestra documentación, a pesar de que existe una diferencia entre ambos términos y un uso correcto.
 
-<div class="alert alert-danger">
-El peso del producto no puede ser cero. Esto puede provocar problemas en los costos del cálculo del flete.
-</div>
+>❗ El peso del producto no puede ser cero. Esto puede provocar problemas en los costos del cálculo del flete.
 
 ## Cómo visualizar el prorrateo del flete
 
diff --git a/docs/tutorials/es/how-shipping-calculation-works.md b/docs/tutorials/es/how-shipping-calculation-works.md
index a68c728e1..d9204d6c5 100644
--- a/docs/tutorials/es/how-shipping-calculation-works.md
+++ b/docs/tutorials/es/how-shipping-calculation-works.md
@@ -47,14 +47,13 @@ Para su selección, las combinaciones de logística siguen los criterios y el or
 </li>
 </ul>
 <br>
-  <div class="alert alert-warning">
-Si se debe enviar un <a href="https://help.vtex.com/es/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28">kit</a>, hay dos condiciones:  
-  <ul>
-    <li>Los componentes del kit deben tener el mismo<a href="https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">muelle de carga</a>.</li>
-    <li>Los componentes del kit deben estar disponibles en el <a href="https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/2XyUVa0UKMyHTmwqyA5Bx6">stock</a>.</li>
-  </ul>
-Para más información, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-e-calculado-o-frete-do-kit--frequentlyAskedQuestions_154">Cómo se calcula el envío de un kit</a>.
-</div>
+  >⚠️ Si se debe enviar un [kit](https://help.vtex.com/es/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28), hay dos condiciones:  
+>
+> * Los componentes del kit deben tener el mismo[muelle de carga](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
+>
+> * Los componentes del kit deben estar disponibles en el [stock](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/2XyUVa0UKMyHTmwqyA5Bx6).
+>
+> Para más información, consulta el artículo [Cómo se calcula el envío de un kit](https://help.vtex.com/es/tutorial/como-e-calculado-o-frete-do-kit--frequentlyAskedQuestions_154).
 
 2. **Prioridad del stock:** las rutas de logística seleccionadas anteriormente se organizan considerando al [stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) como criterio de prioridad. Cuantos menos SKU del pedido haya en stock, más prioridad tendrá la ruta de logística en la selección para evitar que se retenga stock con pocos ítems. A partir de esto, se crea una lista de rutas de logística ordenadas de mayor a menor prioridad, es decir, el ítem con más prioridad ocupa el primer lugar y el ítem con menos prioridad ocupa el último lugar.
 3. **Agrupamiento de paquetes:** la plataforma VTEX calcula la separación de los ítems del pedido en paquetes con el fin de estimar las divisiones de paquetes y [grupos de envíos](https://help.vtex.com/es/tutorial/como-funciona-a-remessa--tutorials_118).
diff --git a/docs/tutorials/es/how-the-carrefour-integration-works.md b/docs/tutorials/es/how-the-carrefour-integration-works.md
index cc3154d69..5f65f5e8c 100644
--- a/docs/tutorials/es/how-the-carrefour-integration-works.md
+++ b/docs/tutorials/es/how-the-carrefour-integration-works.md
@@ -47,14 +47,12 @@ Para que los productos se muestren en Carrefour, la integración envía los sigu
 _Leyenda: _
 `*` Campos obligatorios.<br />
 
-<div class="alert alert-warning">Carrefour no acepta productos con variación (más de uno SKU).</div>
+>⚠️ Carrefour no acepta productos con variación (más de uno SKU).
 
 ### Visualización del producto
 Una vez que los lotes de producto y oferta se envían con éxito y validados por Carrefour, todas las variaciones / SKU de un mismo producto se muestran juntas en una misma agrupación.
 
-<div class="alert alert-info">
-Ex: Camisa Azul (producto) | P, M, G (variaciones/SKUs)
-</div>
+>ℹ️ Ex: Camisa Azul (producto) | P, M, G (variaciones/SKUs)
 
 ### Status del producto
 Con todos los productos procesados correctamente y catalogados por Carrefour, sus ofertas pueden tener los siguientes status:
@@ -67,9 +65,7 @@ Al ser enviados con éxito por primera vez, los productos pasan por un proceso d
 
 Por ejemplo, si se cambia la descripción del producto, la integración no se actualizará en el marketplace. Para hacer algún tipo de cambio, usted necesitará entrar en contacto directo con Carrefour.
 
-<div class="alert alert-warning">
-El producto no se puede borrar en el panel de Carrefour. Si esto ocurre, la integración no podrá enviarlo de nuevo.
-</div>
+>⚠️ El producto no se puede borrar en el panel de Carrefour. Si esto ocurre, la integración no podrá enviarlo de nuevo.
 
 ## 2. Inventario
 Cuando un producto se envía por primera vez, el inventario también se envía. Sin embargo, es descartado por Carrefour, porque el marketplace sólo acepta recibir los inventarios para productos ya catalogados. Esta política existe para que el inventario disponible en el marketplace sea siempre el más actualizado.
@@ -85,9 +81,7 @@ Sin embargo, Carrefour no notifica a VTEX cuando todo ha sido aprobado. Esto sig
 
 Después de que los productos reciben la primera carga de precio, la actualización se hace SKU por SKU siempre que los precios en VTEX sufren algún cambio. Esta actualización se envía en lotes de 6 en 6 minutos. Esto significa que la integración acumula todas las actualizaciones de su tienda durante 6 minutos y envia todo a la vez. Si la actualización de precios tarda más de lo esperado, es probable que haya mucha información en la cola para que se actualice.
 
-<div class="alert alert-warning">
-Tenga en cuenta que, para los precios con validez, el sistema no notifica a los afiliados cuando la fecha expira. Así, el precio base sólo será enviado en la próxima modificación de precios.
-</div>
+>⚠️ Tenga en cuenta que, para los precios con validez, el sistema no notifica a los afiliados cuando la fecha expira. Así, el precio base sólo será enviado en la próxima modificación de precios.
 
 Para cada SKU, la integración envía sólo el precio final, basado en el retorno de la simulación de fulfillment. En un escenario estándar, el precio enviado va a ser siempre el determinado para la política comercial asociada a la integración. Sin embargo, existen factores que pueden influir en el precio final, como promociones y precios fijos.
 
@@ -95,11 +89,9 @@ _`Ejemplo 1:` una promoción que ofrece un 10% de descuento para una determinada
 
 _`Ejemplo 2:` En la política comercial utilizada en Carrefour, un SKU tiene un precio de $ 10 y un precio fijo de $ 15. El valor que la integración envía al marketplace es $ 15._
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> como la forma de pago se da en el marketplace, las reglas de pago también se determinan por él. A causa de ello, la integración no consigue enviar precios diferenciados de acuerdo con la forma de pago.
-<br/ >
-<em>Ejemplo: si en VTEX está configurada la incidencia de interés para pagos parcelados, el precio enviado seguirá siendo el que fue devuelto por la simulación de fulfillment.</em>
-</div>
+>⚠️ **Atención:** como la forma de pago se da en el marketplace, las reglas de pago también se determinan por él. A causa de ello, la integración no consigue enviar precios diferenciados de acuerdo con la forma de pago.
+> <br/ >
+> *Ejemplo: si en VTEX está configurada la incidencia de interés para pagos parcelados, el precio enviado seguirá siendo el que fue devuelto por la simulación de fulfillment.*
 
 ## 4. Promociones
 A diferencia de una promoción que se utiliza para el sitio web de su tienda, una promoción para el marketplace sólo descuenta el valor del producto, pero sin indicar que es una promoción. Es decir, el precio enviado ya está modificado y no hay un sello de promoción.
@@ -122,9 +114,7 @@ Los detalles del pedido se influencian directamente por factores como la entrega
 #### Envío
 Carrefour consulta, en el momento del pedido, la tabla de envío registrada en VTEX. Nuestra plataforma devuelve para ellos las opciones de envío disponibles, de acuerdo con el mapeo informado en la configuración de la integración. Es importante tener en cuenta que la consulta sólo es posible si la API de Envío está registrada en el panel del Carrefour.
 
-<div class="alert alert-warning">
-NOTA: Si ninguno de los campos del mapeo se rellena correctamente, no será posible simular el envío en VTEX. En consecuencia, los pedidos de Carrefour no se integrarán.
-</div>
+>⚠️ NOTA: Si ninguno de los campos del mapeo se rellena correctamente, no será posible simular el envío en VTEX. En consecuencia, los pedidos de Carrefour no se integrarán.
 
 Si la API de envío no está registrada, Carrefour utilizará una __tabla de contingencia__ para realizar el cálculo. En este caso, Carrefour envía la información del pedido y la integración intenta hacer un _match_ del envío calculado con el transportista que más se adecua dentro de VTEX (usamos el __tipo__ de transportista como parámetro). Si no hay una coincidencia, habrá un error en la integración del pedido. Para solucionarlo, usted tendrá que hacer primero el mapeo y, a continuación, volver a procesar el pedido.
 
@@ -149,9 +139,7 @@ Durante el proceso, puede que el pedido no sea integrado por algún motivo. Uste
 
 Una vez que la integración ocurre, los pedidos continúan siendo tratados con el mismo ID utilizado en Carrefour.
 
-<div class="alert alert-warning">
-Pedidos con algún tipo de incidente no serán integrados. En caso de que el incidente ocurra después de la integración del pedido, un aviso se mostrará en la pestaña de rastreo en el Admin de VTEX.
-</div>
+>⚠️ Pedidos con algún tipo de incidente no serán integrados. En caso de que el incidente ocurra después de la integración del pedido, un aviso se mostrará en la pestaña de rastreo en el Admin de VTEX.
 
 ### 5.3 Interacción del pedido
 Una vez que el pedido se ha integrado correctamente, usted puede interactuar con él tanto por el Admin de VTEX como por el panel de administrador de Carrefour. Sin embargo, algunas acciones pueden o no aplicarse a ambos lados.
diff --git a/docs/tutorials/es/how-the-integration-with-buscape-works.md b/docs/tutorials/es/how-the-integration-with-buscape-works.md
index da30a512e..6a2c7d12a 100644
--- a/docs/tutorials/es/how-the-integration-with-buscape-works.md
+++ b/docs/tutorials/es/how-the-integration-with-buscape-works.md
@@ -59,9 +59,7 @@ Si el envío se realiza con éxito, el SKU pasará también por un proceso de ca
 ### Visualización del producto
 Con el envío correcto y el proceso de catalogación de Buscapé concluido, todas las variaciones/SKUs de un mismo producto se muestran juntas, en una misma agrupación (siempre que se registre correctamente en VTEX).
 
-<div class="alert alert-info">
-Ex: Camisa Azul (producto) | P, M, G (variaciones/SKUs)
-</div>
+>ℹ️ Ex: Camisa Azul (producto) | P, M, G (variaciones/SKUs)
 
 
 ### Actualizaciones de producto
@@ -82,9 +80,7 @@ Los status de Buscapé reflejan los cambios de stock del producto en VTEX. Esto
 ## 2. Inventario
 Los inventarios se envían por primera vez junto con el primer envío de productos. A partir de ahí, los inventarios de los anuncios en Buscapé se actualizan automáticamente, SKU por SKU, siempre que haya algún cambio en VTEX. La actualización tarda sólo unos segundos para reflejarse en el marketplace, pero los logs de inventario pueden tardar unos minutos en aparecer en el Admin de VTEX.
 
-<div class="alert alert-info">
-Para acceder a los logs, haga clic en la sección <strong>Integraciones</strong> del menú lateral del Admin. Una lista de opciones se abrirá y, a continuación, usted debe hacer clic en la opción <strong>inventario</strong>.
-</div>
+>ℹ️ Para acceder a los logs, haga clic en la sección **Integraciones** del menú lateral del Admin. Una lista de opciones se abrirá y, a continuación, usted debe hacer clic en la opción **inventario**.
 
 ## 3. Precio
 Los precios se envían por primera vez junto con el primer envío de productos. A partir de ahí, los precios de los anuncios en Buscapé se actualizan automáticamente, SKU por SKU, siempre que haya algún cambio en VTEX. La actualización tarda sólo unos segundos para reflejarse en el marketplace, pero los logs de precios pueden tardar unos minutos en aparecer en el Admin de VTEX.
@@ -93,17 +89,17 @@ Sin embargo, el sistema __no__ notifica a los afiliados cuando llega la fecha fi
 
 Para cada SKU, la integración envía el __precio final__ y el __precio de lista__ (también conocido como `precio de`), basado en el retorno de la simulación de checkout. Normalmente, el precio enviado es siempre el que fue determinado por la política comercial asociada a la integración. Sin embargo, __Promociones__ y __Precios fijos__ pueden influenciar el precio final.
 
-<div class="alert alert-info">
-<strong>Ejemplo 1:</strong>
-<br />
-Una promoción que ofrezca un 10% de descuento para el pago en boleto.
-</div>
-
-<div class="alert alert-info">
-<strong>Ejemplo 2:</strong>
-<br />
-En la política comercial usada en Buscapé, un SKU tiene un precio de $ 10 y un precio fijo de $ 15. El valor que la integración envía al marketplace es de $ 15.
-</div>
+>ℹ️ **Ejemplo 1:**
+>
+>
+> 
+> Una promoción que ofrezca un 10% de descuento para el pago en boleto.
+
+>ℹ️ **Ejemplo 2:**
+>
+>
+> 
+> En la política comercial usada en Buscapé, un SKU tiene un precio de $ 10 y un precio fijo de $ 15. El valor que la integración envía al marketplace es de $ 15.
 
 La integración envía precios de acuerdo con la forma de pago. Esto significa que, si hay intereses configurados para pagos parcelados, el precio enviado al Buscapé también va a tener intereses.
 
diff --git a/docs/tutorials/es/how-the-order-replacement-works.md b/docs/tutorials/es/how-the-order-replacement-works.md
index 7e71e9fcc..cb471946e 100644
--- a/docs/tutorials/es/how-the-order-replacement-works.md
+++ b/docs/tutorials/es/how-the-order-replacement-works.md
@@ -70,6 +70,6 @@ Al seleccionar **Alterar pedido**, el cliente es llevado a una pantalla en la qu
 
 Para concluir la modificación, él es llevado al carrito y el Checkout, donde puede modificar dirección, tipo de flete, forma de pago y SKU.
 
-<div class="alert alert-warning">Es necesario cerrar la compra para concluir el proceso, pero <strong>el cliente jamás es cobrado dos veces</strong>. En algunos casos se reaprovechará el pago anterior; cuando esto no sea posible, la cobranza anterior en la tarjeta de crédito será automáticamente estornada.</div>
+>⚠️ Es necesario cerrar la compra para concluir el proceso, pero **el cliente jamás es cobrado dos veces**. En algunos casos se reaprovechará el pago anterior; cuando esto no sea posible, la cobranza anterior en la tarjeta de crédito será automáticamente estornada.
 
 La reutilización de pago sólo puede utilizarse si el valor del pedido nuevo es igual al del pedido original. Además, si el pago expira en hasta 2 días, no puede reutilizarse.
diff --git a/docs/tutorials/es/how-the-relationship-between-websites-and-business-policies-works.md b/docs/tutorials/es/how-the-relationship-between-websites-and-business-policies-works.md
index 90ef18401..0430b7991 100644
--- a/docs/tutorials/es/how-the-relationship-between-websites-and-business-policies-works.md
+++ b/docs/tutorials/es/how-the-relationship-between-websites-and-business-policies-works.md
@@ -38,9 +38,7 @@ Para saber la ordenación de las políticas, siga los pasos abajo:
 1. En su Admin VTEX, acceda a **Configuración de la tienda > Canales > Políticas Comerciales**.
 2. En la columna __Posición__, verá la ordenación de sus políticas comerciales. La posición 1 muestra la política comercial de mayor prioridad.
 
-<div class="alert alert-danger">
-Recomendamos no cambiar la posición de la política comercial de <strong>ID 1</strong>.
-</div>
+>❗ Recomendamos no cambiar la posición de la política comercial de **ID 1**.
 
 ### Ejemplos
 
diff --git a/docs/tutorials/es/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md b/docs/tutorials/es/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
index 1b84da408..cb3f57efb 100644
--- a/docs/tutorials/es/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
+++ b/docs/tutorials/es/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
@@ -27,9 +27,7 @@ Entonces, vamos a modificar algunos datos del `orderForm` para ingresar una segu
 - Utilizando la biblioteca vtex.js.
 - Por medio de un request a la API del Checkout de VTEX.
 
-<div class="alert alert-warning">
-Aunque es posible crear una interfaz personalizada superpuesta a la de VTEX, que contiene el segundo campo de dirección, no recomendamos hacerlo.
-</div>
+>⚠️ Aunque es posible crear una interfaz personalizada superpuesta a la de VTEX, que contiene el segundo campo de dirección, no recomendamos hacerlo.
 
 ## vtex.js
 
diff --git a/docs/tutorials/es/how-to-add-customized-information-to-the-order-and-manipulate-it.md b/docs/tutorials/es/how-to-add-customized-information-to-the-order-and-manipulate-it.md
index 116acc4aa..c29de649d 100644
--- a/docs/tutorials/es/how-to-add-customized-information-to-the-order-and-manipulate-it.md
+++ b/docs/tutorials/es/how-to-add-customized-information-to-the-order-and-manipulate-it.md
@@ -32,9 +32,7 @@ Para trabajar con este campo, debe utilizar la API del Checkout de VTEX. Son nec
 
 Antes de rellenar el campo `customData`, es necesario utilizar la llamada [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration) para crear una app. Esta app contendrá los campos personalizados que se rellenarán durante el checkout.
 
-<div class="alert alert-warning">
-La llamada Update orderForm configuration define configuraciones que se aplican a todos los orderForms generados en su cuenta. Es decir, a partir del momento en que añade una app por medio de esta, todos los pedidos de la tienda contendrán los campos adicionales definidos en esta app. Esta llamada solo necesita realizarse una vez para crear una app y sus campos.
-</div>
+>⚠️ La llamada Update orderForm configuration define configuraciones que se aplican a todos los orderForms generados en su cuenta. Es decir, a partir del momento en que añade una app por medio de esta, todos los pedidos de la tienda contendrán los campos adicionales definidos en esta app. Esta llamada solo necesita realizarse una vez para crear una app y sus campos.
 
 Veamos un ejemplo del objeto `app` enviado en el body del request  Update orderForm configuration:
 
diff --git a/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
index 7dd61d8d8..76017d2ea 100644
--- a/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/es/how-to-capture-the-ip-of-an-order.md
@@ -32,14 +32,10 @@ Ver más detalles en [Cómo visualizar detalle del pedido](/es/tutorial/como-vis
 ## Obtener la IP por API
 Para obtener la IP por integración, se podrá consultar la API Get Order mediante el orderID.
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/orders#getorder">Ver documentación de API OMS</a>
-</div>
+>ℹ️ [Ver documentación de API OMS](https://developers.vtex.com/reference/orders#getorder)
 
 Una vez obtenido el Json de la Orden, se podrá obtener el transactionId y consultar la API **Get Transaction Details** mediante el ID de la transacción.
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/transaction-process#transactiondetails">Ver documentación de API Transaction</a>
-</div>
+>ℹ️ [Ver documentación de API Transaction](https://developers.vtex.com/reference/transaction-process#transactiondetails)
 
 Finalmente, de esta última llamada se podrá consultar el campo `ipAddress`.
diff --git a/docs/tutorials/es/how-to-change-order-items.md b/docs/tutorials/es/how-to-change-order-items.md
index ca6ac2d9e..f06cd2537 100644
--- a/docs/tutorials/es/how-to-change-order-items.md
+++ b/docs/tutorials/es/how-to-change-order-items.md
@@ -22,9 +22,7 @@ Hay dos formas de modificar un pedido:
 * [Por el Admin VTEX:](#como-cambiar) esta opción se puede utilizar si el status del pedido es `Preparando entrega`.  
 * [Por la API de cambio de pedidos:](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes) además de cambiar los ítems, se puede crear descuentos y modificar el precio del pedido. El cambio solo se puede realizar si el status del pedido en la API de pedidos es `handling` o `waiting-for-fulfillment`.  
 
-<div class="alert alert-warning">
-Tras el cambio, el cliente recibe una notificación por email si la plantilla <code>Change of information</code> (<a href="https://help.vtex.com/es/tutorial/plantillas-de-emails-transaccionales-del-pedido--3g2S2kqBOoSGcCaqMYK2my">plantillas de emails transaccionales referentes al pedido)</a> está activada en el Centro de mensajes.  El cliente recibe los mensajes con la información que se ha rellenado en el formulario de cambio de ítems.
-</div>
+>⚠️ Tras el cambio, el cliente recibe una notificación por email si la plantilla `Change of information` ([plantillas de emails transaccionales referentes al pedido)](https://help.vtex.com/es/tutorial/plantillas-de-emails-transaccionales-del-pedido--3g2S2kqBOoSGcCaqMYK2my) está activada en el Centro de mensajes.  El cliente recibe los mensajes con la información que se ha rellenado en el formulario de cambio de ítems.
 
 Es posible editar ítems que aún no fueron facturados en un pedido. Para agregar nuevos ítems, remover ítems o modificar la cantidad de cada uno, realice los siguientes pasos.  
 
diff --git a/docs/tutorials/es/how-to-change-orders-beta.md b/docs/tutorials/es/how-to-change-orders-beta.md
index 96212978f..b9effa688 100644
--- a/docs/tutorials/es/how-to-change-orders-beta.md
+++ b/docs/tutorials/es/how-to-change-orders-beta.md
@@ -15,9 +15,7 @@ legacySlug: como-modificar-pedidos-beta
 subcategory: 3LQ1Tl0u4frEOd45BkjFAm
 ---
 
-<div class="alert alert-info">
-Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar <b>Modificar pedido (Beta)</b>, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a> e informa el nombre del <a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> en que deseas activarla.
-</div>
+>ℹ️ Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar **Modificar pedido (Beta)**, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support) e informa el nombre del [account name(s)](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) en que deseas activarla.
 
 La funcionalidad [Modificar pedido (beta)](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ) brinda la posibilidad de editar un pedido de múltiples maneras, ya sea para atender las preferencias del cliente, abordar la falta de disponibilidad de productos u otras razones. 
 
@@ -28,9 +26,7 @@ Este artículo muestra las formas en que se puede modificar un pedido y describe
 * [Acciones comunes](#acciones-comunes)
 * [Errores de procesamiento](#errores-de-procesamiento)
 
-<div class="alert alert-warning">
-Para conocer las <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ#caracteristicas-generales">características generales</a> en escenarios de modificación de pedido, incluyendo reserva, actualización de stock y cuentas franquicia, o para comprender cuestiones de <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ#cambios-de-precio">precio, pago y factura</a>, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Cómo funciona Modificar pedido (Beta)</a>.
-</div>
+>⚠️ Para conocer las [características generales](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ#caracteristicas-generales) en escenarios de modificación de pedido, incluyendo reserva, actualización de stock y cuentas franquicia, o para comprender cuestiones de [precio, pago y factura](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ#cambios-de-precio), consulta el artículo [Cómo funciona Modificar pedido (Beta)](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ).
 
 ## Requisitos
 
diff --git a/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md b/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md
index c150800d3..3078cf93b 100644
--- a/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md
+++ b/docs/tutorials/es/how-to-change-the-order-of-payment-methods-at-checkout.md
@@ -19,9 +19,7 @@ Usted puede modificar el orden de visualización de los medios de pago en el Che
 - Por el Admin.
 - Por medio de una personalización en JavaScript.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> aunque exista esta posibilidad, por cuestiones de seguridad y performance, <strong>no se recomienda</strong> que usted modifique los archivos JavaScript del Checkout. VTEX no se responsabiliza por cualquier problema generado luego de la edición de este código.
-</div>
+>⚠️ **Atención:** aunque exista esta posibilidad, por cuestiones de seguridad y performance, **no se recomienda** que usted modifique los archivos JavaScript del Checkout. VTEX no se responsabiliza por cualquier problema generado luego de la edición de este código.
 
 ## Cómo se establece el orden 
 
diff --git a/docs/tutorials/es/how-to-change-the-sorting-of-delivery-types-in-the-cart.md b/docs/tutorials/es/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
index c79a537d3..94dbe52f2 100644
--- a/docs/tutorials/es/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
+++ b/docs/tutorials/es/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
@@ -21,6 +21,4 @@ Al hacer clic en el menú de tipos de entrega, el cliente podrá acceder a otras
 
 Este es un comportamiento estándar de la plataforma, y ​​si el comerciante desea modificarlo, es posible personalizar el carrito (a través de CSS y JavaScript), de acuerdo con las necesidades de la tienda.
 
-<div class="alert alert-warning">
-Recordamos que se debe tener mucho cuidado en cualquier cambio de CSS o JavaScript en el carrito. Si no está bien hecho, este tipo de personalización puede comprometer la tasa de conversión de su tienda y la seguridad de su checkout.
-</div>
+>⚠️ Recordamos que se debe tener mucho cuidado en cualquier cambio de CSS o JavaScript en el carrito. Si no está bien hecho, este tipo de personalización puede comprometer la tasa de conversión de su tienda y la seguridad de su checkout.
diff --git a/docs/tutorials/es/how-to-configure-a-custom-payment.md b/docs/tutorials/es/how-to-configure-a-custom-payment.md
index 8e1c87749..ae2850e6c 100644
--- a/docs/tutorials/es/how-to-configure-a-custom-payment.md
+++ b/docs/tutorials/es/how-to-configure-a-custom-payment.md
@@ -33,6 +33,4 @@ Permite que usted utilice una tarjeta de crédito de la Tienda con una de las si
 
 Después de esta configuración, será necesaria la creación de la [Condición de Pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials).
 
-<div class="alert alert-warning">
-Cuando señale para autorizar automáticamente, el pedido sigue directamente para el status “Preparando Entrega”, o sea, no queda parado en el status “Pago pendiente” aguardando la aprobación, como ocurre caso la flag no esté señalada.
-  </div>
+>⚠️ Cuando señale para autorizar automáticamente, el pedido sigue directamente para el status “Preparando Entrega”, o sea, no queda parado en el status “Pago pendiente” aguardando la aprobación, como ocurre caso la flag no esté señalada.
diff --git a/docs/tutorials/es/how-to-configure-mercado-pago-pro-as-a-payment-method.md b/docs/tutorials/es/how-to-configure-mercado-pago-pro-as-a-payment-method.md
index 1b981b268..5a35303cc 100644
--- a/docs/tutorials/es/how-to-configure-mercado-pago-pro-as-a-payment-method.md
+++ b/docs/tutorials/es/how-to-configure-mercado-pago-pro-as-a-payment-method.md
@@ -45,6 +45,4 @@ Al lado derecho de la pantalla, es posible configurar las [condiciones especiale
 
 Sin embargo, esa etapa es opcional. Usted puede hacer clic directamente en el __botón azul «Salvar»__ para finalizar la configuración del medio de pago.
 
-<div class="alert alert-warning">
-<strong>Recuerde:</strong> las nuevas condiciones de pago pueden llevar hasta 10 minutos para ser mostrados en SmartCheckout.
-</div>
+>⚠️ **Recuerde:** las nuevas condiciones de pago pueden llevar hasta 10 minutos para ser mostrados en SmartCheckout.
diff --git a/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index 48ec8dd93..dc5d70ac3 100644
--- a/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/es/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -32,9 +32,7 @@ En las operaciones B2B, existe la necesidad de mantener relaciones con los compr
 
 ![Minimum Order Value - ES](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/3571a12b0a5367cc62e982c04e8e7ece/Minimum_Order_Value_-_ES.png)
 
-<div class="alert alert-warning">
-El cliente tiene permitido armar un carrito con un valor menor al especificado en la regla "Valor mínimo total de la compra". Sin embargo, en el momento de finalizar la compra, sólo se completarán los pedidos que sean iguales o superiores al valor especificado.
-</div>
+>⚠️ El cliente tiene permitido armar un carrito con un valor menor al especificado en la regla "Valor mínimo total de la compra". Sin embargo, en el momento de finalizar la compra, sólo se completarán los pedidos que sean iguales o superiores al valor especificado.
 
 ## Definir una cantidad máxima de ítems del mismo SKU por carrito
 
@@ -44,9 +42,7 @@ El cliente tiene permitido armar un carrito con un valor menor al especificado e
 
 ![Cantidad máxima de un mismo SKU en el carrito](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/cfcc10ac1d2bccfb10fcd174d832f3f3/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_ES.png)
 
-<div class="alert alert-warning">
-No hay límites en el número máximo de ítems <b>del mismo SKU</b> por carrito. La única restricción se refiere al número máximo de ítems de <b>SKUs diferentes</b>, que debe ser un máximo de 300 ítems por carrito.
-</div>
+>⚠️ No hay límites en el número máximo de ítems **del mismo SKU** por carrito. La única restricción se refiere al número máximo de ítems de **SKUs diferentes**, que debe ser un máximo de 300 ítems por carrito.
 
 Si desea utilizar acciones que eviten que el usuario exceda los valores especificados incluso durante el flujo de compra (por ejemplo, crear un bloqueo de botón del carrito cuando se alcance la cantidad máxima de artículos), será necesario crear una personalización en la parte delantera de la tienda.
 
diff --git a/docs/tutorials/es/how-to-configure-payment-conditions.md b/docs/tutorials/es/how-to-configure-payment-conditions.md
index e0d74ed92..79e55ca5f 100644
--- a/docs/tutorials/es/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/es/how-to-configure-payment-conditions.md
@@ -30,9 +30,7 @@ Una vez que hayas definido tu afiliación de gateway, para elegir cualquiera de
 
 Además, hay la posibilidad de definir si el pago será a vista o en cuotas, con o sin intereses y las condiciones especiales.
 
-<div class="alert alert-warning">
- Cualquier cambio en las condiciones de pago puede llevar hasta 10 minutos en aparecer en el checkout de su tienda.
-</div>
+>⚠️ Cualquier cambio en las condiciones de pago puede llevar hasta 10 minutos en aparecer en el checkout de su tienda.
 
 En los pasos siguientes, utilizaremos la tarjeta de crédito como ejemplo de condición de pago.
 
@@ -50,9 +48,7 @@ En los pasos siguientes, utilizaremos la tarjeta de crédito como ejemplo de con
 8. En el campo “A vista o en cuotas?”, seleccione A vista.
 9. Haga clic en __Guardar__.
 
-<div class="alert alert-info">
-En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobranded, privado, pagarés, boletos, PIX, entre otros.
-</div>
+>ℹ️ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobranded, privado, pagarés, boletos, PIX, entre otros.
 
 ### En cuotas sin interés
 
@@ -97,9 +93,7 @@ En el Paso 5. puede elegir otros métodos de pago como tarjetas de débito, cobr
 
 En algunos países, los intereses de las compras parceladas son cobrados directamente por la institución financiera. Para estos casos, es posible activar el botón __Intereses externos__. Este botón rellena con `null` el valor de los intereses en el JSON enviado al conector. Este valor `null` indica que los intereses serán cobrados posteriormente por la institución financiera. Para activar esta feature, basta hacer clic en el botón de __Intereses Externos__ en la configuración del pago en cuotas con interés.
 
-<div class="alert alert-info">
-  Atención: la funcionalidad de interés externo solo es válida para algunas afiliaciones de gateway (asegúrese de que esta opción esté disponible al registrar la afiliación deseada). Los pedidos realizados por afiliaciones que no soporten esta funcionalidad serán cancelados en el sistema.
-</div>
+>ℹ️ Atención: la funcionalidad de interés externo solo es válida para algunas afiliaciones de gateway (asegúrese de que esta opción esté disponible al registrar la afiliación deseada). Los pedidos realizados por afiliaciones que no soporten esta funcionalidad serán cancelados en el sistema.
 
 ## Remover condición de pago
 
diff --git a/docs/tutorials/es/how-to-configure-subscriptions.md b/docs/tutorials/es/how-to-configure-subscriptions.md
index 81b36fa2c..e85293b62 100644
--- a/docs/tutorials/es/how-to-configure-subscriptions.md
+++ b/docs/tutorials/es/how-to-configure-subscriptions.md
@@ -34,9 +34,7 @@ Para activar la funcionalidad, será necesario:
 
 ## 1. Instalar la app de Suscripciones
 
-<div class="alert alert-warning">
-Actualmente, la instalación del módulo de Suscripciones se realiza únicamente mediante solicitud a <a href="https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
-</div>
+>⚠️ Actualmente, la instalación del módulo de Suscripciones se realiza únicamente mediante solicitud a [nuestro Soporte](https://support.vtex.com/hc/es-419/requests).
 
 Para instalar la aplicación gratis de suscripciones en [VTEX App Store](https://apps.vtex.com/), sigue los pasos a continuación:
 
@@ -63,9 +61,7 @@ Actualmente, los siguientes medios de pago están habilitados para pedidos de su
 - **Tarjeta de crédito**
 - **Boleto bancario** (medio de pago disponible en Brasil)
 
-<div class="alert alert-info">
-  <p>Para colocar a disposición la opción de pago <strong>Tarjeta de crédito</strong>, contacte al adquirente de cu tienda y verifique si acepta transacciones de compras recurrentes de tarjetas con token (sin CVV). El sistema de <strong>Suscripciones</strong> utilizará los mismos datos de la tarjeta empleada en la primera compra para realizar las demás compras de suscripción, garantizando la seguridad de todo el proceso.</p>
-</div>
+>ℹ️ Para colocar a disposición la opción de pago **Tarjeta de crédito**, contacte al adquirente de cu tienda y verifique si acepta transacciones de compras recurrentes de tarjetas con token (sin CVV). El sistema de **Suscripciones** utilizará los mismos datos de la tarjeta empleada en la primera compra para realizar las demás compras de suscripción, garantizando la seguridad de todo el proceso.
 
 Para habilitar este tipo de transacción en el conector, el gestor de la tienda deberá solicitar al adquirente la habilitación para transaccionar pagos recurrentes. Acceda a nuestro artículo sobre [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
 
@@ -79,9 +75,7 @@ Existe otra opción para crear un plan de suscripción, que consiste en crear ma
 
 Hay una serie de recursos relacionados con Suscripciones que están disponibles en el módulo **Perfiles de acceso** de su tienda. Estos recursos permiten el acceso de los usuarios de su Admin VTEX a determinadas funcionalidades, para operar el módulo de Suscripciones. Para saber más sobre los perfiles de acceso, consulte nuestro [artículo](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso).
 
-<div class="alert alert-warning">
-Si el usuario no tiene los permisos necesarios para acceder a los datos en las pantallas de <b>Suscripciones</b>, el sistema mostrará una alerta indicando que no tiene estos permisos, y el usuario no podrá ver los datos.
-</div>
+>⚠️ Si el usuario no tiene los permisos necesarios para acceder a los datos en las pantallas de **Suscripciones**, el sistema mostrará una alerta indicando que no tiene estos permisos, y el usuario no podrá ver los datos.
 
 Vea los recursos relacionados con el módulo de Suscripciones en la siguiente tabla:
 
diff --git a/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md b/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md
index 42b5bd6b1..2d8d40a57 100644
--- a/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md
+++ b/docs/tutorials/es/how-to-configure-the-fingerprint-device-for-stelo.md
@@ -19,15 +19,11 @@ __Device Fingerprint__ es un identificador que actúa en el procesamiento de un
 
 Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
 
 En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliación Stelo.
 
-<div class="alert alert-info">
-Las configuraciones documentadas en este artículo se realizan en un ambiente exterior a VTEX. Por lo tanto, pueden estar desactualizadas.
-</div>
+>ℹ️ Las configuraciones documentadas en este artículo se realizan en un ambiente exterior a VTEX. Por lo tanto, pueden estar desactualizadas.
 
 Para insertar los scripts que exige Stelo al device fingerprint, es necessário usar el Google Tag Manager. Para ello, haga login en su cuenta en [http://www.google.com/tagmanager](http://www.google.com/tagmanager). Después, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md b/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
index e52c8627f..d81687bd8 100644
--- a/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
+++ b/docs/tutorials/es/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
@@ -15,7 +15,7 @@ legacySlug:
 subcategory: 
 ---
 
-<div class="alert alert-warning">La integración con el Google Shopping por XML es un <strong>método ultrapasado</strong> que no es más recomendado. Vea [aqui](http://help.vtex.com/es/tutorial/nueva-integracion-nativa-con-google-shopping-por-api) cómo funciona la nueva integración del Google Shopping por API.</div>
+>⚠️ La integración con el Google Shopping por XML es un **método ultrapasado** que no es más recomendado. Vea [aqui](http://help.vtex.com/es/tutorial/nueva-integracion-nativa-con-google-shopping-por-api) cómo funciona la nueva integración del Google Shopping por API.
 
 Siguiendo la [Actualización de 2015 de la Especificación del feed del Google Shopping y de la Taxonomía del producto de Google](https://support.google.com/merchants/answer/6231410?hl=pt-BR "Actualización de 2015 de la Especificación del feed del Google Shopping y de la Taxonomía del producto de Google"), incluimos nuevos campos en nuestro formulario de creaciónde XML: Separador de categorías, Categoría Global y Especificaciones de producto.
 
diff --git a/docs/tutorials/es/how-to-create-a-page-template.md b/docs/tutorials/es/how-to-create-a-page-template.md
index a8a1e9552..d91cabb26 100644
--- a/docs/tutorials/es/how-to-create-a-page-template.md
+++ b/docs/tutorials/es/how-to-create-a-page-template.md
@@ -36,16 +36,18 @@ Vea a continuación el procedimiento:
 3. Haga clic en __HTML Templates__.
 4. Justo debajo, haga clic en __New template__.
 5. Rellene el campo __Template Name__.
-<div class="alert alert-danger">
-  <p>Al rellenar el <b>Template Name</b>, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-<li><code>app</code></li>
-</ul></p>
-</div>
+>❗ Al rellenar el **Template Name**, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+>
+> *`app`
+> 
 6. A continuación, rellene el box __Template XHTML__ con el código de su template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. En la esquina superior derecha, haga clic en el botón  __Save Template__.
 
diff --git a/docs/tutorials/es/how-to-create-a-product.md b/docs/tutorials/es/how-to-create-a-product.md
index f227aeac2..5c3ee8275 100644
--- a/docs/tutorials/es/how-to-create-a-product.md
+++ b/docs/tutorials/es/how-to-create-a-product.md
@@ -32,9 +32,7 @@ El formulario de registro de nuevo producto tiene las siguientes secciones:
 *   [SEO](#seo)
 *   [Storefront](#storefront)
 
-<div class="alert alert-info">
-<p>Antes de crear un producto, debe crear la <a href="https://help.vtex.com/es/tutorial/registrando-categoria--tutorials_206">Categoría</a> correspondiente al producto si no se ha registrado anteriormente en su tienda.</p>
-</div>
+>ℹ️ Antes de crear un producto, debe crear la [Categoría](https://help.vtex.com/es/tutorial/registrando-categoria--tutorials_206) correspondiente al producto si no se ha registrado anteriormente en su tienda.
 
 ## Informaciones básicas
 
@@ -81,9 +79,7 @@ Para agregar imágenes al producto, siga las instrucciones a continuación:
 1. Haga clic en el botón `Agregar imágenes` o arrastre y suéltelas en el recuadro punteado.
 2. Inserte todas las imágenes del producto. Incluya las variaciones, como el color y el tamaño. Las imágenes deben estar en formato JPEG, PNG o GIF, con tamaño máximo de 5MB cada una.
 
-<div class="alert alert-warning">
-<p>Recomendamos utilizar imágenes con 600px o más para que la imagen se muestre correctamente en su tienda.</p>
-</div>
+>⚠️ Recomendamos utilizar imágenes con 600px o más para que la imagen se muestre correctamente en su tienda.
 
 Puede hacer clic en una imagen y arrastrarla para posicionarla antes o después de las otras si desea reorganizar las imágenes y cambiar el orden de visualización en la página del producto, como se ilustra a continuación.
 
@@ -142,9 +138,7 @@ Cada producto debe tener al menos un [SKU](https://help.vtex.com/es/tutorial/o-q
 
 Si desea crear más de un SKU, según las posibles variaciones de su producto, haga clic en el botón `+ Crear variacione`.
 
-<div class="alert alert-warning">
-  <p>Al hacer clic en <code>+ Crear variacione</code>, se eliminarán los campos que hubiere rellenado en <b>Información de SKU</b>.</p>
-</div>
+>⚠️ Al hacer clic en `+ Crear variacione`, se eliminarán los campos que hubiere rellenado en **Información de SKU**.
 
 Lo que diferencia entre los SKU o las variaciones de producto son las distintas combinaciones de especificaciones posibles. Por ejemplo: al crear el producto _zapatilla deportiva_ y configurar la especificación _color_ con las opciones _rosa_ y _azul_ y la especificación _tamaño_ con las opciones _36_ y _37_, los SKU serán combinaciones de estas opciones: _zapatilla deportiva rosa 36_, _zapatilla deportiva rosa 37_, _zapatilla deportiva azul 36_ y _zapatilla deportiva azul 37._
 
@@ -173,9 +167,7 @@ Las especificaciones que creó y sus respectivas opciones se muestran en esta se
 
 Puede cambiar la información de cada especificación al hacer clic en el botón <i class="fas fa-pencil-alt"></i> en la línea de cada una.
 
-<div class="alert alert-info">
-  <p>Después de definir la configuración de las especificaciones del producto, no puede eliminar una especificación ni añadir una nueva. Durante la edición, solo puede añadir nuevos valores a la especificación existente.</p>
-</div>
+>ℹ️ Después de definir la configuración de las especificaciones del producto, no puede eliminar una especificación ni añadir una nueva. Durante la edición, solo puede añadir nuevos valores a la especificación existente.
 
 También puede hacer clic en el botón `+ Agregar especificación` para incluir más especificaciones.
 
@@ -201,9 +193,7 @@ Al hacer clic en el botón <i class="fas fa-ellipsis-v"></i>, puede realizar las
   * **Agregar imágenes:** en este panel, también se puede cargar nuevas imágenes haciendo clic en el botón `Agregar imágenes` o arrastrando y soltando los archivos de imagen en el espacio delimitado por la línea punteada.
 * **Desactivar:** desactive la variación en su tienda. 
 
-<div class="alert alert-warning">
-<p>Si agrega especificaciones después de configurar las variaciones, se volverán a calcular todas las variaciones y se volverán a definir sus campos.</p>
-</div>
+>⚠️ Si agrega especificaciones después de configurar las variaciones, se volverán a calcular todas las variaciones y se volverán a definir sus campos.
 
 ### Edición avanzada
 El panel de edición avanzada de variaciones, que se ilustra a continuación, permite ver y editar toda la información y las imágenes relacionadas con cada variación del producto. 
diff --git a/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
index a2ead9ef7..ec656da67 100644
--- a/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/es/how-to-create-a-promotion-with-limitation-of-use.md
@@ -17,9 +17,7 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 
 Para que una promoción del tipo regular sea aplicada por un número limitado de veces, basta desmarcar la opción **ilimitado** en restricciones y limitaciones de uso. Cuando es desmarcada, es puesto a disposición un campo para registrar la cantidad de veces en la que podrá aplicarse la promoción en compras en su tienda. Esto significa que, si usted registra el número 10, sólo se concederá la promoción a los primeros 10 pedidos cerrados en su tienda que cumplan las reglas de la promoción.
 
-<div class="alert alert-warning">
-<p>Los pedidos con status <code>Iniciando cancelación</code> o <code>Cancelado</code> no cuentan para el límite establecido.</p>
-</div>
+>⚠️ Los pedidos con status `Iniciando cancelación` o `Cancelado` no cuentan para el límite establecido.
 
 ![Promocion con limite de uso](https://images.ctfassets.net/alneenqid6w5/6RuP1uG4Cc8MWm2OikwimK/9a4d5dcdf67edbd058cf1dae705fa1e9/Promocion_con_limite_de_uso.png)
 
diff --git a/docs/tutorials/es/how-to-create-a-shelf-template.md b/docs/tutorials/es/how-to-create-a-shelf-template.md
index 70c9269b1..d48b04a13 100644
--- a/docs/tutorials/es/how-to-create-a-shelf-template.md
+++ b/docs/tutorials/es/how-to-create-a-shelf-template.md
@@ -26,15 +26,16 @@ Para crear un template de estante, siga los pasos abajo:
 3. Haga clic en __Shelves Templates__.
 4. Haga clic en __new template__.
 5. Rellene el campo __Shelf Template Name__.
-<div class="alert alert-danger">
-  <p>Al rellenar el <b>Shelf Template Name</b>, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Al rellenar el **Shelf Template Name**, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX. Consulta la lista de palabras reservadas a continuación.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 6. El campo __CSS Class__ cree una *tag class* para este template. Este campo es opcional.
 7. Haga clic en el cuadro __Rounded corners__ para que el template tenga bordes redondeados.
 8. En __Template Code__ usted debe llenar el código de su template. Utilice los templates predeterminados como base para la creación del nuevo. [Vea aquí el ejemplo de un código básico](https://gist.githubusercontent.com/DeboraFerreira/a4126e2a60a6a0abb6c0/raw/8600e6e4c718c626158e472cdcee60ed03009a0f/template-prateleira).
diff --git a/docs/tutorials/es/how-to-create-a-subscription-attachment.md b/docs/tutorials/es/how-to-create-a-subscription-attachment.md
index 34e5cc0dd..e1c797d88 100644
--- a/docs/tutorials/es/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/es/how-to-create-a-subscription-attachment.md
@@ -15,9 +15,7 @@ legacySlug: como-crear-un-anexo-de-suscripcion
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
- <div class="alert alert-info">
-  <p>Si utiliza el módulo de <strong>Suscripciones Beta</strong>, la forma más recomendable de crear un plan de suscripción es directamente en el módulo de <strong>Suscripciones</strong>. Lea el artículo <a href="https://help.vtex.com/es/tutorial/como-criar-um-plano-de-assinatura-beta--1qGRoFczm98Wgt81f9mUqC">Cómo crear un plan de suscripción (Beta)</a> para obtener más información.</p>
-</div>
+ >ℹ️ Si utiliza el módulo de **Suscripciones Beta**, la forma más recomendable de crear un plan de suscripción es directamente en el módulo de **Suscripciones**. Lea el artículo [Cómo crear un plan de suscripción (Beta)](https://help.vtex.com/es/tutorial/como-criar-um-plano-de-assinatura-beta--1qGRoFczm98Wgt81f9mUqC) para obtener más información.
 
 El **Anexo de SKU** indica que la funcionalidad de Suscripción está activa para ese SKU y también cuál será la frecuencia disponible. 
 
@@ -41,9 +39,7 @@ Para crear un anexo de SKU, siga los pasos a continuación.
     * `vtex.subscription.prueba`
 5. Deje la casilla de selección **Anexo obligatorio** sin marcar.
 
-<div class="alert alert-warning">
-  <p>El campo <strong>Anexo obligatorio</strong> no se debe marcar. Si el anexo se marca como obligatorio, el sistema de <strong>Suscripciones</strong> intentará enviar un pedido de suscripción para un ítem que ya tiene un anexo obligatorio, lo que generará un error en el sistema. Si esto ocurre por equivocación, quite la marca de la casilla <strong>Anexo obligatorio</strong> y solicite al cliente de su tienda que intente realizar el pedido nuevamente.</p>
-</div>
+>⚠️ El campo **Anexo obligatorio** no se debe marcar. Si el anexo se marca como obligatorio, el sistema de **Suscripciones** intentará enviar un pedido de suscripción para un ítem que ya tiene un anexo obligatorio, lo que generará un error en el sistema. Si esto ocurre por equivocación, quite la marca de la casilla **Anexo obligatorio** y solicite al cliente de su tienda que intente realizar el pedido nuevamente.
 
 6. En **Status**, marque la casilla **Activa/Desactiva el anexo**, y haga clic en `Salvar` para guardar los cambios.
 
@@ -77,9 +73,7 @@ Siga las instrucciones a continuación para configurar la frecuencia y fechas de
 
         ![ES Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/5tbntKlv4WeYUXQtM8EMGz/84d58a31d1b449fdbdfad60fae5dec0d/ES_Assinatura_Exemplo_Valores_month.png)
 
-<div class="alert alert-info">
-  <p>Si no se introduce ningún valor en el campo <strong>Valores permitidos</strong>, la fecha del ciclo de suscripción será el mismo día de la semana (si la frecuencia es semanal) o día del mes (si la frecuencia es mensual) del pedido original.</p>
-</div>
+>ℹ️ Si no se introduce ningún valor en el campo **Valores permitidos**, la fecha del ciclo de suscripción será el mismo día de la semana (si la frecuencia es semanal) o día del mes (si la frecuencia es mensual) del pedido original.
 
 ### Asociar el anexo a un SKU
 
diff --git a/docs/tutorials/es/how-to-create-conditional-prices.md b/docs/tutorials/es/how-to-create-conditional-prices.md
index 736d3ac21..211350b06 100644
--- a/docs/tutorials/es/how-to-create-conditional-prices.md
+++ b/docs/tutorials/es/how-to-create-conditional-prices.md
@@ -15,9 +15,8 @@ legacySlug: crear-precios-condicionales
 subcategory: 
 ---
 
-<div class="alert alert-warning"><strong>Nota:</strong>
-Sólo es posible crear Precios Condicionales si usted ha instalado la aplicación <strong>Conditions Builder</strong> y ha creado alguna condición. (Vea el artículo <a href="http://help.vtex.com/es/tutorial/como-usar-el-app-conditions-builder">Cómo usar la app Conditions Builder</a>)
-</div>
+>⚠️ **Nota:**
+> Sólo es posible crear Precios Condicionales si usted ha instalado la aplicación **Conditions Builder** y ha creado alguna condición. (Vea el artículo [Cómo usar la app Conditions Builder](http://help.vtex.com/es/tutorial/como-usar-el-app-conditions-builder))
 
 Los precios condicionales se gestionan en el módulo de precios.
 
diff --git a/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
index 790d81879..801845cbd 100644
--- a/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/es/how-to-define-the-url-for-a-product-page.md
@@ -25,9 +25,7 @@ Consulta la sección [Reglas de llenado](#reglas-de-llenado) para conocer las re
 
 ![textlink.es](https://images.ctfassets.net/alneenqid6w5/7Fn3c82EFti8PUc2qME3Xa/74abc336ae433344083479d28014696d/textlink.es.png)
 
-<div class="alert alert-info">
-  <p>También puedes cambiar la URL de un producto utilizando la<a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview"> API del Catálogo</a>. En este caso, el campo a modificar es <code>LinkId</code>. Consulta el artículo<a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product"> Update product</a> para obtener más información.</p>
-</div>
+>ℹ️ También puedes cambiar la URL de un producto utilizando la[ API del Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). En este caso, el campo a modificar es `LinkId`. Consulta el artículo[ Update product](https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product) para obtener más información.
 
 ## Reglas de llenado
 
@@ -42,9 +40,7 @@ Al rellenar el campo **textLink**, deben respetarse las siguientes reglas:
     * `api`
     * `admin`
 
-<div class="alert alert-danger">
-  <p>Ten en cuenta que no cumplir con las reglas de llenado del campo <strong>textLink</strong> indicadas anteriormente puede afectar el rendimiento de tu tienda, causar problemas en las búsquedas e interferir en el funcionamiento de las páginas definidas en el Admin VTEX.</p>
-</div>
+>❗ Ten en cuenta que no cumplir con las reglas de llenado del campo **textLink** indicadas anteriormente puede afectar el rendimiento de tu tienda, causar problemas en las búsquedas e interferir en el funcionamiento de las páginas definidas en el Admin VTEX.
 
 ## Más información
 
diff --git a/docs/tutorials/es/how-to-download-the-vtex-invoices.md b/docs/tutorials/es/how-to-download-the-vtex-invoices.md
index b8726923c..caeb2a569 100644
--- a/docs/tutorials/es/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/es/how-to-download-the-vtex-invoices.md
@@ -64,7 +64,7 @@ Para descargar su boleto, realice los siguientes pasos:
 6. Haga clic en **Efectuar Pago**.
 7. Se generará un boleto, la multa y los intereses se incluirán automáticamente. 
 
-<div class="alert alert-info">En Brasil, una factura púrpura puede indicar que está atrasada pero se ha generado un nuevo boleto para una fecha cercana. En este caso, la factura permanecerá atrasada hasta que se realice el pago. Si no se paga el nuevo boleto, la factura se pondrá en rojo.</div>
+>ℹ️ En Brasil, una factura púrpura puede indicar que está atrasada pero se ha generado un nuevo boleto para una fecha cercana. En este caso, la factura permanecerá atrasada hasta que se realice el pago. Si no se paga el nuevo boleto, la factura se pondrá en rojo.
 
 ![baixar boletos es](https://images.ctfassets.net/alneenqid6w5/6JSRhGjBxWs4KDpVm9P5LL/57eb4cb973d27d600710cd8a91f7f4a6/baixar_boletos_es.gif)
 
diff --git a/docs/tutorials/es/how-to-export-a-product-spreadsheet.md b/docs/tutorials/es/how-to-export-a-product-spreadsheet.md
index fa15b7ccf..569f693a6 100644
--- a/docs/tutorials/es/how-to-export-a-product-spreadsheet.md
+++ b/docs/tutorials/es/how-to-export-a-product-spreadsheet.md
@@ -28,6 +28,4 @@ A continuación, compruebe el paso a paso para realizar esta operación:
 
 A continuación, compruebe la bandeja de entrada del correo electrónico seleccionado. Si la operación ha funcionado, el usuario ha recibido un email con un link para descargar la planilla completa.
 
-<div class="alert alert-warning">
-Esto sólo funciona adecuadamente en casos de hasta 10 mil productos. Si el valor requerido es mayor que ese límite, el sistema no envía la planilla al correo electrónico. Utilice los filtros para refinar su búsqueda.
-</div>
+>⚠️ Esto sólo funciona adecuadamente en casos de hasta 10 mil productos. Si el valor requerido es mayor que ese límite, el sistema no envía la planilla al correo electrónico. Utilice los filtros para refinar su búsqueda.
diff --git a/docs/tutorials/es/how-to-find-an-sku-id.md b/docs/tutorials/es/how-to-find-an-sku-id.md
index f1852f50b..af631bca4 100644
--- a/docs/tutorials/es/how-to-find-an-sku-id.md
+++ b/docs/tutorials/es/how-to-find-an-sku-id.md
@@ -46,7 +46,5 @@ Para descubrir el ID de un SKU por la URL de registro de SKU, siga los pasos aba
 4. Observe la dirección URL de la página cargada. Usted verá una URL con el siguiente formato: `https://{accountName}.myvtex.com/admin/Site/SkuForm.aspx?IdSku={number}`
  El ID del SKU será el número mostrado en lugar de `{number}`.
 
-<div class="alert alert-danger">
- Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el <a href="url">ID del SKU</a> no debe contener <b>el número cero a la izquierda</b>. Por ejemplo, el sistema no reconoce ID con el formato <code>01</code>, <code>02</code> , <code>021</code>, ya que espera el formato <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el [ID del SKU](url) no debe contener **el número cero a la izquierda**. Por ejemplo, el sistema no reconoce ID con el formato `01`, `02` , `021`, ya que espera el formato `1`, `2`, `21`.
 
diff --git a/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
index 4b345dc27..c4bc2313e 100644
--- a/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/es/how-to-import-pickup-points-using-spreadsheets.md
@@ -19,9 +19,7 @@ Los puntos de recogida, también conocidos como pickup points, son parte importa
 
 Puede [configurar puntos de recogida uno a uno](/es/tutorial/configurar-puntos-de-recogida-pickup-points) o hacer esto mediante la importación de una planilla XLS [(como la de este ejemplo)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Usando un archivo XLS, usted registra todos los pickup points de una sola vez (siempre que no supere los 10 MB).
 
-<div class="alert alert-info">
-Un archivo XLS de <strong>10 MB</strong> permite el registro de, aproximadamente, <strong>50 mil</strong> puntos de recogida. Para importar un número mayor, es necesario dividirlos en más de una planilla y hacer un upload a la vez.
-</div>
+>ℹ️ Un archivo XLS de **10 MB** permite el registro de, aproximadamente, **50 mil** puntos de recogida. Para importar un número mayor, es necesario dividirlos en más de una planilla y hacer un upload a la vez.
 
 
 
diff --git a/docs/tutorials/es/how-to-include-a-registration-on-a-master-data-form.md b/docs/tutorials/es/how-to-include-a-registration-on-a-master-data-form.md
index 5db18ff8d..8bd6805e9 100644
--- a/docs/tutorials/es/how-to-include-a-registration-on-a-master-data-form.md
+++ b/docs/tutorials/es/how-to-include-a-registration-on-a-master-data-form.md
@@ -19,21 +19,16 @@ Para incluir un registro, basta acceder al módulo Master Data y elegir la aplic
 
 Digamos, por ejemplo, que usted desee editar la información de un cliente de su tienda.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href=”https://developers.vtex.com/vtex-rest-api/docs/getting-started-1”>
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href=”https://developers.vtex.com/vtex-rest-api/docs/getting-started-1”>
+> Master Data v2
+>  </a>
+> 
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data**.
 2. En Master Data, haz clic en **Aplicações**.
diff --git a/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md b/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
index 3fd53d43c..66b6c8ce1 100644
--- a/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
+++ b/docs/tutorials/es/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
@@ -15,10 +15,9 @@ legacySlug: por-que-no-recomendamos-insertar-un-proxy-inverso-en-los-servicios-v
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
-<div class="alert alert-danger">
-  <p><strong>Atención:</strong> las explicaciones de este artículo están destinadas a abordar casos de extrema excepción. No recomendamos que ninguna tienda use proxy inverso. Cuando se usa un proxy inverso, todo servicio perimetral (CDN) gestionado y optimizados por VTEX se dejará de lado, de modo que el trabajo de la tienda es quién será responsable de proveer de forma efectiva el sitio web, siendo responsable de realizar sus configuraciones, acompañamiento y gestión de particularidades como reenvío de encabezados, cookies y gestión de caché. No proporcionamos documentación de estas particularidades.</p>
-  <p>VTEX no se responsabiliza por problemas en ese sistema, ya sea un CDN propio, servicio de WAF u otro recurso que se encuentre al frente de nuestros servidores. No tendremos visión de cualquier falla; por lo tanto, la solución <strong>no</strong> se encuadrará en nuestros acuerdos de SLA.</p>
-</div>
+>❗ **Atención:** las explicaciones de este artículo están destinadas a abordar casos de extrema excepción. No recomendamos que ninguna tienda use proxy inverso. Cuando se usa un proxy inverso, todo servicio perimetral (CDN) gestionado y optimizados por VTEX se dejará de lado, de modo que el trabajo de la tienda es quién será responsable de proveer de forma efectiva el sitio web, siendo responsable de realizar sus configuraciones, acompañamiento y gestión de particularidades como reenvío de encabezados, cookies y gestión de caché. No proporcionamos documentación de estas particularidades.
+>
+> VTEX no se responsabiliza por problemas en ese sistema, ya sea un CDN propio, servicio de WAF u otro recurso que se encuentre al frente de nuestros servidores. No tendremos visión de cualquier falla; por lo tanto, la solución **no** se encuadrará en nuestros acuerdos de SLA.
 
 Si incluso después de leer la alerta anterior desea apuntar su propia CDN a la CDN de VTEX, será necesario insertar un proxy inverso frente a los servicios de VTEX. Para hacer esto, cree las entradas TXT que se indican a continuación. Servirán como entrada de verificación para informarnos que el host de hecho apunta a VTEX. Sin esto, VTEX no puede proveer navegación.
 
@@ -32,11 +31,10 @@ Por lo tanto, la configuración debería quedar así:
 
 Además, también será necesario que todo el tráfico de `/.well-known /acme-challenge/*` llegue a VTEX. Algunos proxys inversos capturan esta ruta y, con eso, no podemos emitir o renovar el certificado SSL.
 
-<div class="alert alert-warning">
-  <p>VTEX solo provee navegación si:
-    <ul>
-      <li>Podemos ver que el host apunta a VTEX (conforme nuestro CNAME).</li>
-      <li>Conseguimos emitir/renovar certificados SSL para el host.</li>
-    </ul>
-Si no se cumplen ambas condiciones, VTEX dejará de entregar el sitio web, pues se caracteriza por estar fuera del aire.</p>
-</div>
+>⚠️ VTEX solo provee navegación si:
+>
+> * Podemos ver que el host apunta a VTEX (conforme nuestro CNAME).
+>
+> * Conseguimos emitir/renovar certificados SSL para el host.
+>
+> Si no se cumplen ambas condiciones, VTEX dejará de entregar el sitio web, pues se caracteriza por estar fuera del aire.
diff --git a/docs/tutorials/es/how-to-integrate-vtex-using-zapier.md b/docs/tutorials/es/how-to-integrate-vtex-using-zapier.md
index 8e9019316..5b9aab112 100644
--- a/docs/tutorials/es/how-to-integrate-vtex-using-zapier.md
+++ b/docs/tutorials/es/how-to-integrate-vtex-using-zapier.md
@@ -15,4 +15,4 @@ legacySlug: untitled-entry-2017-09-19-at-03-41-48
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/how-to-integrate-with-dafiti.md b/docs/tutorials/es/how-to-integrate-with-dafiti.md
index fa71fbd2d..97aee10da 100644
--- a/docs/tutorials/es/how-to-integrate-with-dafiti.md
+++ b/docs/tutorials/es/how-to-integrate-with-dafiti.md
@@ -62,9 +62,7 @@ El mapeo debe realizarse siempre que un producto se envíe por primera vez a Daf
 
 Siga el paso a paso siguiente, haciendo el de/para en la __Planilla de Mapeo__ entre el que está registrado en su producto en VTEX y los valores especificados de acuerdo con la __Planilla de Consulta__ de Dafiti.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> cualquier valor utilizado que no esté en la Planilla de Consulta ocasionará un error de integración.
-</div>
+>⚠️ **OBS:** cualquier valor utilizado que no esté en la Planilla de Consulta ocasionará un error de integración.
 
 1. __SKU:__ es el ID de SKU en VTEX. Este es el ID de SKU que desea enviar a Dafiti.
 
@@ -85,10 +83,11 @@ Siga el paso a paso siguiente, haciendo el de/para en la __Planilla de Mapeo__ e
 7. __Modelo:__ rellene el valor del modelo de su SKU. Este campo es libre para ser llenado de la manera que encuentre más adecuada.
 <br/>_`Ex:` usted está mapeando pantalones de chándal. El común es llenar la columna __Modelo__ con el valor `Chándal`._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> en la integración brasileña, Dafiti exige que el nombre de los productos registrados sigan el siguiente estándar: <strong>Tipo de Producto + Marca + Modelo + Color.</strong>
-<br/>
-Por lo tanto, siempre que encuentre valores para estos cuatro campos en VTEX, crearemos el nuevo nombre de producto automáticamente. Si alguno de los campos no está presente, le enviaremos el nombre original del producto.</div>
+>⚠️ **OBS:** en la integración brasileña, Dafiti exige que el nombre de los productos registrados sigan el siguiente estándar: **Tipo de Producto + Marca + Modelo + Color.**
+>
+>
+> 
+> Por lo tanto, siempre que encuentre valores para estos cuatro campos en VTEX, crearemos el nuevo nombre de producto automáticamente. Si alguno de los campos no está presente, le enviaremos el nombre original del producto.
 
 
 ## Envío de imágenes
@@ -104,17 +103,14 @@ Para hacer esto, siga este paso a paso:
 
 Puede enviar hasta __ocho imágenes__. De esta forma, agregue nuevas columnas siguiendo el estándar: `Image_2`, `Image_3`, ...,` Image_8`.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> recuerde siempre de utilizar <code>http</code> o <code>https</code> al principio de las URL, de lo contrario, habrá error al intentar cargar la hoja de cálculo en VTEX.</div>
+>⚠️ **OBS:** recuerde siempre de utilizar `http` o `https` al principio de las URL, de lo contrario, habrá error al intentar cargar la hoja de cálculo en VTEX.
 
 ## Envío de la marca del producto
 
 La integración enviará la marca que está registrada en su producto en catálogo de VTEX.
 <br/>_`Ex:` usted está enviando una camisa de Adidas, la integración enviará como marca `Adidas` también._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> similar a lo que sucede con categoría y especificaciones, Dafiti posee marcas mapeadas en su plataforma. En este caso, si alguno de sus productos tiene una marca que no está registrada en Dafiti, el mismo sufrirá un error de integración. Si esto ocurre, póngase en contacto con Dafiti para solicitar el registro de su marca en su sistema.
-</div>
+>⚠️ **OBS:** similar a lo que sucede con categoría y especificaciones, Dafiti posee marcas mapeadas en su plataforma. En este caso, si alguno de sus productos tiene una marca que no está registrada en Dafiti, el mismo sufrirá un error de integración. Si esto ocurre, póngase en contacto con Dafiti para solicitar el registro de su marca en su sistema.
 
 ## Haciendo el upload
 
diff --git a/docs/tutorials/es/how-to-integrate-with-facebook.md b/docs/tutorials/es/how-to-integrate-with-facebook.md
index 5820ae97f..f6407f4bf 100644
--- a/docs/tutorials/es/how-to-integrate-with-facebook.md
+++ b/docs/tutorials/es/how-to-integrate-with-facebook.md
@@ -55,7 +55,5 @@ Después de ese paso, la integración creará un catálogo con el nombre `VtexIn
 
 Es en este catálogo, dentro de Facebook, que se crearán los ítems y donde estarán disponibles para ser usados.
 
-<div class="alert alert-info">
-Puede utilizar el <i>pixel app</i> de Facebook para rastrear y optimizar los resultados de sus campañas de marketing en el Google Tag Manager de su tienda. Aprenda el paso a paso aquí
-<a href="https://www.facebook.com/business/help/1021909254506499">aquí</a>.
-</div>
+>ℹ️ Puede utilizar el <i>pixel app</i> de Facebook para rastrear y optimizar los resultados de sus campañas de marketing en el Google Tag Manager de su tienda. Aprenda el paso a paso aquí
+> [aquí](https://www.facebook.com/business/help/1021909254506499).
diff --git a/docs/tutorials/es/how-to-make-transfers.md b/docs/tutorials/es/how-to-make-transfers.md
index 192de0555..5d495dc47 100644
--- a/docs/tutorials/es/how-to-make-transfers.md
+++ b/docs/tutorials/es/how-to-make-transfers.md
@@ -68,6 +68,4 @@ El mensaje informa el status - si se completó con éxito o si se produjo algún
 
 Sin embargo, esta no es la única manera de verificar esta información. En caso de ser necesario, el administrador de la tienda también puede consultarla en el módulo de __Declaraciones (Extracto Financiero)__. En la pestaña __Declaraciones__, simplemente seleccione la opción  deseada para ver los detalles.
 
-<div class="alert alert-info">
-Al igual que en las transacciones bancarias, la transferencia solicitada puede ser denegada si el administrador de la tienda alcanza el límite de su cuenta. De ser necesario, se puede solicitar el aumento del límite mediante un ticket en la plataforma de atención VTEX.
-</div>
+>ℹ️ Al igual que en las transacciones bancarias, la transferencia solicitada puede ser denegada si el administrador de la tienda alcanza el límite de su cuenta. De ser necesario, se puede solicitar el aumento del límite mediante un ticket en la plataforma de atención VTEX.
diff --git a/docs/tutorials/es/how-to-migrate-a-store-to-pricing.md b/docs/tutorials/es/how-to-migrate-a-store-to-pricing.md
index 589c15b12..2a63d7e06 100644
--- a/docs/tutorials/es/how-to-migrate-a-store-to-pricing.md
+++ b/docs/tutorials/es/how-to-migrate-a-store-to-pricing.md
@@ -43,9 +43,7 @@ El Pricing tiene algunas diferencias importantes con respecto a la primera versi
 
 ## Migrar una tienda para el Pricing v2
 
-<div class="alert alert-info">
-Toda nueva tienda VTEX ya está creada con el Pricing v2.
-</div>
+>ℹ️ Toda nueva tienda VTEX ya está creada con el Pricing v2.
 
 Pricing v2 está disponible para las tiendas que desean migrar al nuevo módulo. Actualmente, tenemos un proceso de migración automática, en que verificamos la compatibilidad de las features del Pricing v2 con las features utilizadas actualmente por la tienda.
 
diff --git a/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md b/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md
index 3f50d641f..b8707d67b 100644
--- a/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md
+++ b/docs/tutorials/es/how-to-modify-details-of-customers-addresses.md
@@ -25,19 +25,14 @@ Para editar la información de los clientes es necesario que sigas los siguiente
 6. Clic en `Guardar`.
 7. Luego clic en `Volver`, para ver nuevamente el listado de direcciones.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
diff --git a/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
index b27b50ab5..4f113903c 100644
--- a/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
@@ -22,18 +22,14 @@ No recomendamos el uso de <a href="https://help.vtex.com/es/tutorial/otimizar-as
 ## Cómo funciona el buscador
 El buscador de VTEX posee un algoritmo inteligente que, a partir del término buscado, identifica cuál es el mejor resultado para presentarle al usuario, o sea, se le presenta siempre el resultado que generará más conversión de venta.
 
-<div class="alert alert-info">
-Ver más detalles de <a href="https://help.vtex.com/es/tutorial/como-funciona-la-busqueda-de-vtex--tutorials_542">como funciona la búsqueda</a> en VTEX.
-</div>
+>ℹ️ Ver más detalles de [como funciona la búsqueda](https://help.vtex.com/es/tutorial/como-funciona-la-busqueda-de-vtex--tutorials_542) en VTEX.
 
 ## Que utilidad tiene una palabra sustituta
 Si el sistema de búsqueda no identifica Landing Page, Marca o Departamento de acuerdo al término buscado, aplica una búsqueda por Palabra Sustituta (palabra clave). 
 
 Pese a tener un peso bajo para la puntuación del indexador, la utilización de palabras sustitutas es un recurso extremadamente importante, ya que hace posible alcanzar a usuarios que realizan búsquedas por términos con errores gramaticales (spagetti), redacción fonética (espagueti) o palabras mal escritas por accidentes al teclearlas (spaguetto), pero con la misma semántica que la palabra original (spaguetti).
 
-<div class="alert alert-info">
-Un recurso muy utilizado para agilizar las búsquedas del equipo interno es colocar el RefId/EAN como Palabra Sustituta en el producto. De este modo, se pueden hacer búsquedas más veloces, con resultados únicos y encontrar ágilmente el producto buscado.
-</div>
+>ℹ️ Un recurso muy utilizado para agilizar las búsquedas del equipo interno es colocar el RefId/EAN como Palabra Sustituta en el producto. De este modo, se pueden hacer búsquedas más veloces, con resultados únicos y encontrar ágilmente el producto buscado.
 
 ## Cómo cargo una palabra sustituta
 
diff --git a/docs/tutorials/es/how-to-place-a-regular-order-using-vtex-apis.md b/docs/tutorials/es/how-to-place-a-regular-order-using-vtex-apis.md
index a80af2789..80d93d3a7 100644
--- a/docs/tutorials/es/how-to-place-a-regular-order-using-vtex-apis.md
+++ b/docs/tutorials/es/how-to-place-a-regular-order-using-vtex-apis.md
@@ -19,9 +19,7 @@ En este tutorial, usted aprenderá a hacer un simple pedido **REGULAR** (hecho,
 
 ¡Vamos a empezar!
 
-<div class="alert alert-warning">
-<strong>Importante:</strong> para cualquier autenticación requerida por las APIs presentadas en este tutorial, usted debe proporcionar un <b>AppToken</b> y un <b>AppKey</b> válidos registrados en el módulo <b>License Manager</b> de su cuenta y habilitados con permisos suficientes.
-</div>
+>⚠️ **Importante:** para cualquier autenticación requerida por las APIs presentadas en este tutorial, usted debe proporcionar un **AppToken** y un **AppKey** válidos registrados en el módulo **License Manager** de su cuenta y habilitados con permisos suficientes.
 
 **PERMISOS NECESARIOS**
 
diff --git a/docs/tutorials/es/how-to-rank-the-best-selling-items.md b/docs/tutorials/es/how-to-rank-the-best-selling-items.md
index ec74819fa..ac01074d4 100644
--- a/docs/tutorials/es/how-to-rank-the-best-selling-items.md
+++ b/docs/tutorials/es/how-to-rank-the-best-selling-items.md
@@ -15,9 +15,7 @@ legacySlug: como-ver-un-ranking-de-los-productos-mas-vendidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-warning">
-El módulo <strong>Pedidos</strong> no fue creado con el objetivo de servir como herramienta de BI (Business Inteligence). Normalmente, es en el ERP que la tienda tiene acceso a informes de ventas.
-</div>
+>⚠️ El módulo **Pedidos** no fue creado con el objetivo de servir como herramienta de BI (Business Inteligence). Normalmente, es en el ERP que la tienda tiene acceso a informes de ventas.
 
 Aunque el objetivo principal del módulo **Pedidos** es gestionar el flujo de pedidos, es posible manipular los datos del [informe de pedidos](https://help.vtex.com/es/tutorial/planilha-de-pedidos) para extraer algunas informaciones que pueden ser útiles a su negocio.
 
diff --git a/docs/tutorials/es/how-to-register-your-salespersons-on-vtex-instore.md b/docs/tutorials/es/how-to-register-your-salespersons-on-vtex-instore.md
index 241dd5677..2a73d33b6 100644
--- a/docs/tutorials/es/how-to-register-your-salespersons-on-vtex-instore.md
+++ b/docs/tutorials/es/how-to-register-your-salespersons-on-vtex-instore.md
@@ -15,6 +15,4 @@ legacySlug: como-registrar-vendedores-en-el-vtex-instore
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-<div class="alert alert-info">
-Este artículo ha sido descontinuado. <a href="https://help.vtex.com/es/tracks/instore-setup?step=2">Haga clic aquí</a> para acceder a nuestro tutorial con el paso a paso para registrar vendedores en inStore.
-</div>
+>ℹ️ Este artículo ha sido descontinuado. [Haga clic aquí](https://help.vtex.com/es/tracks/instore-setup?step=2) para acceder a nuestro tutorial con el paso a paso para registrar vendedores en inStore.
diff --git a/docs/tutorials/es/how-to-request-receivables-anticipation.md b/docs/tutorials/es/how-to-request-receivables-anticipation.md
index 7fcf4ce0d..b28acf69b 100644
--- a/docs/tutorials/es/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/es/how-to-request-receivables-anticipation.md
@@ -33,9 +33,7 @@ Por ejemplo, si el menor valor que puede recibir es R$10, ese es el valor mínim
 
 ![antecipação](https://images.ctfassets.net/alneenqid6w5/2DQKbFjERNOa8wLmFq3nr9/ae2cced48c5774ced4415db9ab9756b6/image.png_h_250_h_250)
 
-<div class="alert alert-info">
-<strong>Atención</strong>: las cuentas por cobrar en disputa o programadas para el siguiente día hábil no pueden ser anticipadas.
-</div>
+>ℹ️ **Atención**: las cuentas por cobrar en disputa o programadas para el siguiente día hábil no pueden ser anticipadas.
 
 Por lo tanto, verifique el procedimiento para solicitar el anticipo:
 
diff --git a/docs/tutorials/es/how-to-schedule-prices-for-a-range-of-hours.md b/docs/tutorials/es/how-to-schedule-prices-for-a-range-of-hours.md
index f8dd388c2..ba2dd846e 100644
--- a/docs/tutorials/es/how-to-schedule-prices-for-a-range-of-hours.md
+++ b/docs/tutorials/es/how-to-schedule-prices-for-a-range-of-hours.md
@@ -20,9 +20,7 @@ Entre otros escenarios, uno de los puntos más importantes en un evento masivo c
 ## Agendar hora por API
 Una de las opciones para agendar precios por hora es hacerlo por API de precios:
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/pricing-api-overview">Ver documentación de APIs</a>
-</div>
+>ℹ️ [Ver documentación de APIs](https://developers.vtex.com/reference/pricing-api-overview)
 
 El backend de VTEX utiliza horario UTC, con lo cual, por ejemplo en Argentina que es GTM-3, si quisiera agendar un precio x hora mediante API y quisiera que un precio comience a las 00hs y termine a las 10hs, debería enviar 3hs más de las que actualmente deseo configurar. O sea, si quisiera que el precio inicie su validez a las 00hs, debo mandar 03hs, y si quisiera que termine a las 10hs, debo mandar 13hs.:
 
@@ -34,9 +32,7 @@ JSON API Precios:
 
 El precio se invalidará automáticamente luego de vencer la hora agendada.
 
-<div class="alert alert-warning">
-<strong>Importante</strong>: En caso de modificar el precio mediante la interfaz del precios del admin y guardar los cambios, se perderá la agenda de horas y quedará válida solamente la agenda de fechas.
-</div>
+>⚠️ **Importante**: En caso de modificar el precio mediante la interfaz del precios del admin y guardar los cambios, se perderá la agenda de horas y quedará válida solamente la agenda de fechas.
 
 ## Agendar hora por planilla
 La otra opción es realizar el agendamiento masivo por planilla de precios. Si bien el backend funciona en UTC, el import de planilla de precios tiene un pre-proceso que calcula el horario de la PC del cliente y ajusta automáticamente el horario de agendamiento, según la hora local. 
@@ -53,6 +49,4 @@ Columnas Planilla Precios:
 
 El precio se invalidará automáticamente luego de vencer la hora agendada.
 
-<div class="alert alert-warning">
-<strong>Importante</strong>: De igual modo que mediante API, en caso de modificar el precio mediante la interfaz del precios del admin y guardar los cambios, se perderá la agenda de horas y quedará válida solamente la agenda de fechas.
-</div>
+>⚠️ **Importante**: De igual modo que mediante API, en caso de modificar el precio mediante la interfaz del precios del admin y guardar los cambios, se perderá la agenda de horas y quedará válida solamente la agenda de fechas.
diff --git a/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md
index 912e8fd90..e43521dde 100644
--- a/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/es/how-to-set-up-fingerprint-for-payu.md
@@ -19,13 +19,11 @@ __Device Fingerprint__ es un identificador que actúa en el procesamiento de un
 
 Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
 
 En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliación PayU.
 
-<div class="alert alert-info">Las configuraciones documentadas en este artículo se realizan en un ambiente externo a VTEX. Por lo tanto, pueden estar desactualizadas.</div>
+>ℹ️ Las configuraciones documentadas en este artículo se realizan en un ambiente externo a VTEX. Por lo tanto, pueden estar desactualizadas.
 
 1. Hacer login en http://www.google.com/tagmanager/ para la tienda que vamos a configurar;
 2. Ingresar al apartado etiquetas (tags) para configurar el device sesión id;
diff --git a/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 4225298d1..9d8fa9f4e 100644
--- a/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/es/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -15,10 +15,9 @@ legacySlug: como-configurar-el-gateway-adyen-en-vtex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
-<div class="alert alert-warning">Las configuraciones documentadas en este artículo se realizan en un ambiente  externo a VTEX. Por lo tanto, pueden ser descontinuadas sin previo aviso.
-</div>
+>⚠️ Las configuraciones documentadas en este artículo se realizan en un ambiente  externo a VTEX. Por lo tanto, pueden ser descontinuadas sin previo aviso.
 
 Si su procesador de pagos elegido es Adyen, realice el siguiente procedimiento  con la configuración necesaria para que la comunicación entre VTEX y Adyen funcione perfectamente.
 
diff --git a/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
index bdc99adbe..7093a9bee 100644
--- a/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/es/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -19,13 +19,11 @@ __Device Fingerprint__ es un identificador que actúa en el procesamiento de un
 
 Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
 
 En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliación Braspag.
 
-<div class="alert alert-info">Las configuraciones documentadas en este artículo se realizan en un ambiente externo a VTEX. Por lo tanto, pueden estar desactualizadas.</div>
+>ℹ️ Las configuraciones documentadas en este artículo se realizan en un ambiente externo a VTEX. Por lo tanto, pueden estar desactualizadas.
 
 Para insertar  los scripts que Braspag/CyberSource requiere para el device fingerprint, es necesario el uso de Google Tag Manager. Para ello, inicie sesión en [http://www.google.com/tagmanager](http://www.google.com/tagmanager/) y acceda a su cuenta.
 
diff --git a/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
index 130867c4c..b32f5c91b 100644
--- a/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/es/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -21,9 +21,7 @@ A través de esta funcionalidad, su marca permite a sus clientes programar visit
 
 Este artículo explica cómo funciona esta funcionalidad y muestra el paso a paso para implementarla.
 
-<div class="alert alert-info">
-Su tienda no necesita tener una cuenta VTEX para usar la funcionalidad Atención Programada de Indeva.
-</div>
+>ℹ️ Su tienda no necesita tener una cuenta VTEX para usar la funcionalidad Atención Programada de Indeva.
 
 ## Formulario de programación
 
@@ -33,9 +31,7 @@ El flujo de la programación que recorre el cliente comienza en la elección de
 
 ![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
-<div class="alert alert-info">
-También es posible proporcionar al cliente un enlace que conduce directamente al formulario de una tienda física específica. Simplemente agregue el ID de la tienda al final de la URL. Con eso, el vendedor puede compartir el enlace de su tienda, por ejemplo, a través de un código QR o en los medios sociales.
-</div>
+>ℹ️ También es posible proporcionar al cliente un enlace que conduce directamente al formulario de una tienda física específica. Simplemente agregue el ID de la tienda al final de la URL. Con eso, el vendedor puede compartir el enlace de su tienda, por ejemplo, a través de un código QR o en los medios sociales.
 
 Al hacer clic en la tienda deseada, el cliente es conducido al formulario. Allí, encuentra información sobre la tienda (que debe definirse en la etapa de implementación), además de los campos para ingresar la información sobre la visita:
 
@@ -50,9 +46,7 @@ Finalmente, el cliente simplemente hace clic en Programar horario. Con eso, esta
 
 ![indeva2](https://images.ctfassets.net/alneenqid6w5/sD5kRl2jv7QxksElwMibF/5aa5ec8582c10891ee90bfcf556144aa/indeva2.png)
 
-<div class="alert alert-warning">
-Por el momento, la confirmación de la programación debe ser realizada de forma manual por la tienda. El cliente no recibirá ningún mensaje automático.
-</div>
+>⚠️ Por el momento, la confirmación de la programación debe ser realizada de forma manual por la tienda. El cliente no recibirá ningún mensaje automático.
 
 ## Aplicación de los vendedores
 
@@ -66,9 +60,7 @@ Si desea entrar en contacto con el cliente a partir de esa pantalla, el vendedor
 
 ![indeva4](https://images.ctfassets.net/alneenqid6w5/6xnGRcIBINTYj7n9HDnTJ4/97e54074b046a5295936d66bd17761fe/indeva4.png)
 
-<div class="alert alert-info">
-La aplicación puede ser instalada en diversos dispositivos de la misma tienda, pero recomendamos que su equipo utilice una app por tienda, y no por vendedor.
-</div>
+>ℹ️ La aplicación puede ser instalada en diversos dispositivos de la misma tienda, pero recomendamos que su equipo utilice una app por tienda, y no por vendedor.
 
 ## Implementación
 
@@ -85,15 +77,11 @@ Es allí donde debe definir la información que aparecerá en el formulario de p
 - Tiempo mínimo de anticipación para cada programación
 - Horarios de atención de la tienda
 
-<div class="alert alert-info">
-Cada tienda física debe ser registrada y configurada individualmente.
-</div>
+>ℹ️ Cada tienda física debe ser registrada y configurada individualmente.
 
 ### Implementación del formulario en la tienda en línea
 
-<div class="alert alert-info">
-Esta orientación está dirigida a tiendas que usan la plataforma VTEX. En otras plataformas, el método de implementación del formulario será diferente.
-</div>
+>ℹ️ Esta orientación está dirigida a tiendas que usan la plataforma VTEX. En otras plataformas, el método de implementación del formulario será diferente.
 
 Para insertar el iframe con el formulario en su tienda VTEX, debe crear una nueva página que contenga este iframe.
 
diff --git a/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index f310387f1..4c3797663 100644
--- a/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/es/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -15,15 +15,11 @@ legacySlug: como-configurar-el-campo-responsable-de-la-recogida-en-smartcheckout
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-<div class="alert alert-info">
-El campo <strong>Responsable de la recogida</strong> sólo está disponible para el <strong>SmartCheckout™ V6</strong>, versión compatible con la feature de Pick Up Points.
-</div>
+>ℹ️ El campo **Responsable de la recogida** sólo está disponible para el **SmartCheckout™ V6**, versión compatible con la feature de Pick Up Points.
 
 Los [puntos de recogida](/tutorial/configurar-pontos-de-retirada-pickup-points?locale=es) dan una opción más a sus clientes: en lugar de esperar la entrega, ellos pueden elegir ir hasta un punto definido y buscar los produtos personalmente. Por defecto, esta acción está vinculada al usuario registrado que efectuó la compra. Sin embargo, usted puede habilitar el campo `Responsable por la recogida` en el checkout de su tienda, para que su cliente pueda nombrar a otra persona para recoger el producto.
 
-<div class="alert alert-warning">
-Si tiene instalada la aplicación <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> en su tienda, el código CSS descrito en el procedimiento a continuación solo debe ingresarse a través de la aplicación. Los scripts insertados a través de la interfaz de administración VTEX (pestaña <b>Código > Archivos</b>) no se reproducen en las tiendas que tienen la aplicación instalada.
-</div>
+>⚠️ Si tiene instalada la aplicación [Checkout UI Settings](https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings) en su tienda, el código CSS descrito en el procedimiento a continuación solo debe ingresarse a través de la aplicación. Los scripts insertados a través de la interfaz de administración VTEX (pestaña **Código > Archivos**) no se reproducen en las tiendas que tienen la aplicación instalada.
 
 Para configurar el campo (que viene desactivado de forma predeterminada), siga los pasos abajo:
 
diff --git a/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md b/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md
index 99bdcf398..03ee37ee2 100644
--- a/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md
+++ b/docs/tutorials/es/how-to-set-up-your-store-on-seller-portal.md
@@ -53,7 +53,7 @@ Conozca algunos detalles sobre el lanzamiento de la versión Beta de Seller Port
 
 ## Configurar su tienda
 
-<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+>⚠️ El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.
 
 Para comenzar a vender sus productos en el marketplace, se debe configurar su tienda en el Seller Portal. Este artículo explica el flujo completo de esa configuración inicial, e indica otra documentación más detallada sobre los pasos a seguir. La configuración básica de Seller Portal incluye los pasos a continuación.
 
@@ -203,6 +203,4 @@ No habrá necesidad de configurar estos módulos manualmente a través de Seller
 
 Para integrar con su ERP, lea nuestra [guía de integración con ERP](https://developers.vtex.com/docs/guides/erp-integration-guide). 
 
-<div class="alert alert-info">  
-  <p>Para generar las claves de acceso necesarias para integrarse con su ERP, haga clic en el <strong>avatar de su perfil</strong>, marcado con la inicial de su correo electrónico y vaya a <strong>Configuración de la cuenta> Claves de aplicación</strong>.</p>
-</div>
+>ℹ️ Para generar las claves de acceso necesarias para integrarse con su ERP, haga clic en el **avatar de su perfil**, marcado con la inicial de su correo electrónico y vaya a **Configuración de la cuenta> Claves de aplicación**.
diff --git a/docs/tutorials/es/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md b/docs/tutorials/es/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
index 68e1211a3..e6dc3c877 100644
--- a/docs/tutorials/es/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
+++ b/docs/tutorials/es/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
@@ -15,6 +15,4 @@ legacySlug: configurar-el-google-analytics-4-en-tienda-vtex-en-cms-portal-legado
 subcategory: 1luKrYptdi8WoMYckakUaM
 ---
 
-<div class="alert alert-info">
-  <p>Contenido bajo traducción.</p>
-</div>
+>ℹ️ Contenido bajo traducción.
diff --git a/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md b/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md
index 720d6e52f..c7dda9ca3 100644
--- a/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md
+++ b/docs/tutorials/es/how-to-setup-google-analytics-in-vtex-store.md
@@ -20,9 +20,7 @@ subcategory: 1luKrYptdi8WoMYckakUaM
 1. [Configurar Google Analytics 4](#configurar-google-analytics-4)
 2. [Editar configuraciones de Google Tag Manager](#editar-configuraciones-de-google-tag-manager)
 
-<div class="alert alert-info">
-A partir del 1 de julio de 2023, Google Analytics 4 sustituirá a Universal Analytics, la versión anterior de la herramienta. Por lo tanto, debes seguir este tutorial para adaptar los cambios a tu tienda. Consulta los detalles <a href="https://support.google.com/analytics/answer/11583528">en este comunicado de Google</a>.
-</div>
+>ℹ️ A partir del 1 de julio de 2023, Google Analytics 4 sustituirá a Universal Analytics, la versión anterior de la herramienta. Por lo tanto, debes seguir este tutorial para adaptar los cambios a tu tienda. Consulta los detalles [en este comunicado de Google](https://support.google.com/analytics/answer/11583528).
 
 ## Configurar Google Analytics 4
 Si ya utilizabas la versión anterior de Google Analytics (Universal Analytics) en tu tienda, deberás agregar una propiedad GA4. Para ello, consulta esta documentación de Google: [Añadir una propiedad de Google Analytics 4 (a un sitio web que ya tiene Google Analytics)](https://support.google.com/analytics/answer/9744165?hl=es#zippy=%2Ccontenido-del-art%C3%ADculo).
diff --git a/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md b/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md
index ee081a33f..c045b0a51 100644
--- a/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md
+++ b/docs/tutorials/es/how-to-turn-my-store-website-into-a-pwa.md
@@ -23,9 +23,7 @@ PWA es la abreviatura en inglés de Progressive Web App - un conjunto de técnic
 
 Si ya tiene un sitio web o una aplicación web, puede implementar poco a poco las características que definen un PWA, como notificaciones, caché de archivos, ejecución en modo off-line y otras posibilidades que hacen que el usuario se sienta en una aplicación nativa.
 
-<div class="alert alert-warning">
-La plataforma VTEX <strong>no</strong> posee características nativas para transformar su tienda en PWA. Esta apenas ofrece las condiciones para que se realice esa implementación. Las tiendas desarrolladas con VTEX IO Store Framework tienen este recurso nativamente.
-</div>
+>⚠️ La plataforma VTEX **no** posee características nativas para transformar su tienda en PWA. Esta apenas ofrece las condiciones para que se realice esa implementación. Las tiendas desarrolladas con VTEX IO Store Framework tienen este recurso nativamente.
 
 ## Google define con exactitud lo que se espera de un PWA:
 
diff --git a/docs/tutorials/es/how-to-use-messages-on-your-io-apps.md b/docs/tutorials/es/how-to-use-messages-on-your-io-apps.md
index 59d0e6451..54e12791f 100644
--- a/docs/tutorials/es/how-to-use-messages-on-your-io-apps.md
+++ b/docs/tutorials/es/how-to-use-messages-on-your-io-apps.md
@@ -17,9 +17,7 @@ subcategory: 54gbzsku02c4bKmgFbp3v3
 
 El VTEX IO tiene un servicio de internacionalización embutido llamado __Messages__. En este tutorial usted aprenderá cómo internacionalizar su aplicación de frontend y las respuestas de su backend.
 
-<div class="alert alert-info">
-Esta funcionalidad sólo está disponible para las aplicaciones react/graphql/typedql.
-</div>
+>ℹ️ Esta funcionalidad sólo está disponible para las aplicaciones react/graphql/typedql.
 
 ## Traducción del Messages
 
@@ -60,9 +58,7 @@ Para obtener una traducción automática más precisa, cree un archivo llamado `
 
 Este archivo funciona para eliminar las posibles ambigüedades de las traducciones. Por ejemplo, la palabra 'Ciao' en italiano significa _Hola_ y también _Hasta luego_ en español. La descripción, por lo tanto, es importante para saber el significado exacto y tener una traducción correcta.
 
-<div class="alert alert-warning">
-El archivo `context.json` es obligatorio y debe contener todas las claves de traducción.
-</div>
+>⚠️ El archivo `context.json` es obligatorio y debe contener todas las claves de traducción.
 
 ### Migración del MessagesBuilder 0.x
 
diff --git a/docs/tutorials/es/how-to-use-the-index-report.md b/docs/tutorials/es/how-to-use-the-index-report.md
index 7d4a0d677..07255cb15 100644
--- a/docs/tutorials/es/how-to-use-the-index-report.md
+++ b/docs/tutorials/es/how-to-use-the-index-report.md
@@ -19,9 +19,7 @@ El **Informe de Indexación** es el reporte que indica el status de indexación
 
 ![productosindexados](https://images.ctfassets.net/alneenqid6w5/9KzymaEjoAeqO6Googkya/7eba6e62cb07e66f8a5952c6fcc10b2e/productosindexados.png)
 
-<div class="alert alert-info">
-<strong>Nota:</strong> Acceda a ver más información en <a href="/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion">Entendiendo el funcionamiento de la indexación.</a>
-</div>
+>ℹ️ **Nota:** Acceda a ver más información en [Entendiendo el funcionamiento de la indexación.](/es/tutorial/entendiendo-el-funcionamento-de-la-indexacion)
 
 ## Cómo acceder al informe de indexación
 
diff --git a/docs/tutorials/es/how-to-use-the-meta-tags-control.md b/docs/tutorials/es/how-to-use-the-meta-tags-control.md
index 819054f45..a3684cd39 100644
--- a/docs/tutorials/es/how-to-use-the-meta-tags-control.md
+++ b/docs/tutorials/es/how-to-use-the-meta-tags-control.md
@@ -54,6 +54,4 @@ A continuación puede observar un ejemplo de meta tags insertadas por el control
 <link rel="canonical" href="http://lojadobreno.vtexcommercestable.com.br/escalada">
 ```
 
-<div class="alert alert-info">
-Si usted no desea usar la tag canonical (&lt;link rel="canonical"&gt;), puede inhabilitarla a través de un <a href="https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag">control específico para eso</a>.
-</div>
+>ℹ️ Si usted no desea usar la tag canonical (&lt;link rel="canonical"&gt;), puede inhabilitarla a través de un [control específico para eso](https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag).
diff --git a/docs/tutorials/es/how-to-use-the-search-result-control.md b/docs/tutorials/es/how-to-use-the-search-result-control.md
index 46fc722cb..0006a5df1 100644
--- a/docs/tutorials/es/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/es/how-to-use-the-search-result-control.md
@@ -17,9 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 El control `<vtex.cmc:searchResult/>` renderiza una vitrina con los productos devueltos por una búsqueda del usuario.
 
-<div class="alert alert-info">
-Este control funciona <b>sólo en páginas con contexto de búsqueda</b>, o sea, páginas donde los resultados mostrados fueron traídos por una búsqueda del usuario.
-</div>
+>ℹ️ Este control funciona **sólo en páginas con contexto de búsqueda**, o sea, páginas donde los resultados mostrados fueron traídos por una búsqueda del usuario.
 
 Cuando el usuario realiza una búsqueda en la tienda, el sistema de VTEX intenta traer resultados de acuerdo con un orden de prioridad de filtros. Entienda la búsqueda en el artículo [Cómo funciona la búsqueda de VTEX](/es/tutorial/como-funciona-la-busqueda-de-vtex).
 
diff --git a/docs/tutorials/es/how-to-use-the-unavailable-product-class.md b/docs/tutorials/es/how-to-use-the-unavailable-product-class.md
index b005a4de7..562ba490f 100644
--- a/docs/tutorials/es/how-to-use-the-unavailable-product-class.md
+++ b/docs/tutorials/es/how-to-use-the-unavailable-product-class.md
@@ -43,9 +43,8 @@ Usted puede personalizar su archivo CSS para que esta clase muestre, por ejemplo
 
 ## Determinar amqué especificación se asignará la clase
 
-<div class="alert alert-warning">>
-La clase de producto sólo se asigna a la especificación que aparece por último en la lista de especificaciones de SKU en el módulo Catalog.
-</div>
+>⚠️ >
+> La clase de producto sólo se asigna a la especificación que aparece por último en la lista de especificaciones de SKU en el módulo Catalog.
 
 Por ejemplo, en el caso del SKU, solo la especificación `Tamanho` recibirá la clase de indisponibilidad.
 
diff --git a/docs/tutorials/es/how-to-view-the-orders-details.md b/docs/tutorials/es/how-to-view-the-orders-details.md
index 519084791..37d32cf57 100644
--- a/docs/tutorials/es/how-to-view-the-orders-details.md
+++ b/docs/tutorials/es/how-to-view-the-orders-details.md
@@ -38,9 +38,7 @@ En el cuadro de la izquierda se concentran las informaciones relacionadas con el
 
 Para tansaciones con tarjeta de crédito, cada pago (pueden ser dos tarjetas) tiene un ID generado por VTEX. El adquirente también crea una, llamada Transaction ID (TID). La TID es específica para cada tarjeta, es decir, si un pedido se paga con dos tarjetas, habrá dos transacciones y luego dos TIDs.
 
-<div class="alert alert-warning">
-En transacciones que no tienen TID, se puede interpretar que el adquirente no procesó el pago, es decir, que no tiene TID. Ocasionalmente esto puede generar un error, y una forma rápida de identificarlo es comprobar si hay una TID.
-</div>
+>⚠️ En transacciones que no tienen TID, se puede interpretar que el adquirente no procesó el pago, es decir, que no tiene TID. Ocasionalmente esto puede generar un error, y una forma rápida de identificarlo es comprobar si hay una TID.
 
 La parte más importante de esta pantalla es el registro de interacciones de la transacción. Aquí se registra toda la comunicación de VTEX con los afiliados registrados - antifraude, gateways y adquirentes -, incluyendo mensajes de éxito y error, con sus respectivos códigos.
 
diff --git a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
index 4170b30b9..e85a04563 100644
--- a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
@@ -51,9 +51,7 @@ Sucede que las condiciones ofrecidas no están presentes en ninguna página:
 
 Por lo tanto, no es posible asignar condiciones a un producto específico o a diferentes diseños a través de una colección. Deberá registrarlos junto con la condición del producto.
 
-<div class="alert alert-info">
-Según las condiciones elegidas, se establece un orden de prioridad para la aplicabilidad del layout. La ordenación es, si existe, template del producto, de la categoría y, finalmente, de la marca. Por lo tanto, un template acondicionado para un producto se superpone al template de la categoría en que está contenido este producto y así sucesivamente.
-</div>
+>ℹ️ Según las condiciones elegidas, se establece un orden de prioridad para la aplicabilidad del layout. La ordenación es, si existe, template del producto, de la categoría y, finalmente, de la marca. Por lo tanto, un template acondicionado para un producto se superpone al template de la categoría en que está contenido este producto y así sucesivamente.
 
 Si tiene dudas en esta configuración, le recomendamos que use la lid: [Prueba de Layout](/es/faq/validar-un-layout-antes-de-ir-a-produccion)
 
diff --git a/docs/tutorials/es/how-trade-policies-work.md b/docs/tutorials/es/how-trade-policies-work.md
index 20721d056..e4fe290b4 100644
--- a/docs/tutorials/es/how-trade-policies-work.md
+++ b/docs/tutorials/es/how-trade-policies-work.md
@@ -59,9 +59,7 @@ Puede limitar el acceso a la tienda a públicos específicos, como en un sitio B
 
 ## Gestión de la cuenta
 
-<div class="alert alert-warning">
-Para los clientes que tienen muchas subcuentas o con operaciones en tiendas físicas que permiten la recogida en la tienda o con el envío desde la tienda, la creación de múltiples políticas comerciales no es la mejor solución. Sugerimos abrir nuevos <a href="https://help.vtex.com/es/tutorial/o-que-e-store-name">nombres de tienda</a> para cada una de las tiendas que operan dentro de una <a href="https://help.vtex.com/es/tutorial/o-que-e-account-name">cuenta</a>. 
-</div>
+>⚠️ Para los clientes que tienen muchas subcuentas o con operaciones en tiendas físicas que permiten la recogida en la tienda o con el envío desde la tienda, la creación de múltiples políticas comerciales no es la mejor solución. Sugerimos abrir nuevos [nombres de tienda](https://help.vtex.com/es/tutorial/o-que-e-store-name) para cada una de las tiendas que operan dentro de una [cuenta](https://help.vtex.com/es/tutorial/o-que-e-account-name).
 
 Demasiadas políticas comerciales en un entorno VTEX hace que el proceso de indexación de los productos en la vitrina y la simulación del envío en el checkout sean más lentos, lo que puede afectar la conversión de los pedidos. Al segmentar el catálogo con múltiples políticas comerciales en lugar de crear nombres de tiendas con su propio stock, la tienda también puede perder oportunidades de venta y mejores condiciones de entrega al restringir la oferta de productos. Vea más información sobre [cómo crear un nombre de tienda](https://help.vtex.com/es/tutorial/como-criar-um-store-name).
 
diff --git a/docs/tutorials/es/hubspot-suiteshare.md b/docs/tutorials/es/hubspot-suiteshare.md
index a149147ed..f48c4c34a 100644
--- a/docs/tutorials/es/hubspot-suiteshare.md
+++ b/docs/tutorials/es/hubspot-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: hubspot-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/i-forgot-my-password-suiteshare.md b/docs/tutorials/es/i-forgot-my-password-suiteshare.md
index 795dfeb6c..a182a2a36 100644
--- a/docs/tutorials/es/i-forgot-my-password-suiteshare.md
+++ b/docs/tutorials/es/i-forgot-my-password-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: olvide-mi-contrasena-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/image-compression.md b/docs/tutorials/es/image-compression.md
index 17ad3ac4a..01e35d441 100644
--- a/docs/tutorials/es/image-compression.md
+++ b/docs/tutorials/es/image-compression.md
@@ -32,9 +32,7 @@ Realizamos una conversión al formato[ WebP](https://developers.google.com/speed
 
 El uso de WebP puede disminuir el tiempo de carga de páginas entre 1 a 2 segundos, dependiendo del layout. A continuación se describe cómo funciona la optimización de imágenes en cada formato.
 
-<div class="alert alert-info">
-  <p>Los navegadores que todavía no son<a href="https://developers.google.com/speed/webp/faq?hl=es-419#which_web_browsers_natively_support_webp"> compatibles con el formato WebP</a> y los servicios como integraciones y marketplaces siempre reciben imágenes no convertidas, sin importar el formato. Los archivos en formato GIF no se convierten a WebP.</p>
-</div>
+>ℹ️ Los navegadores que todavía no son[ compatibles con el formato WebP](https://developers.google.com/speed/webp/faq?hl=es-419#which_web_browsers_natively_support_webp) y los servicios como integraciones y marketplaces siempre reciben imágenes no convertidas, sin importar el formato. Los archivos en formato GIF no se convierten a WebP.
 
 ## PNG
 
diff --git a/docs/tutorials/es/image-widget.md b/docs/tutorials/es/image-widget.md
index 7f8f09f6e..4705b0326 100644
--- a/docs/tutorials/es/image-widget.md
+++ b/docs/tutorials/es/image-widget.md
@@ -41,13 +41,9 @@ Ahora que ya sabe cómo acceder a Image Widget, vea lo que puede hacer a continu
 ### Añadir una imagen
 Después de [acceder a Image Widget](#acceso-a-image-widget) y con él abierto podrá añadir imágenes:
 
-<div class="alert alert-warning">
-Al agregar nuevas imágenes en el modal Image Widget usando un <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">development workspace</a>, la configuración realizada se guardará directamente en el espacio de trabajo principal. Es decir, se reflejarán inmediatamente en el modal de tu tienda.
-</div>
+>⚠️ Al agregar nuevas imágenes en el modal Image Widget usando un [development workspace](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace), la configuración realizada se guardará directamente en el espacio de trabajo principal. Es decir, se reflejarán inmediatamente en el modal de tu tienda.
 <br>
-<div class="alert alert-warning">
-  El tamaño máximo que admite Image Widget es de 4 MB por archivo.
-</div>
+>⚠️ El tamaño máximo que admite Image Widget es de 4 MB por archivo.
 
 1. Haga clic en `Añadir imagen`.
 2. Elige la imagen que quiere añadir y haga clic en `Abrir`.
@@ -83,7 +79,5 @@ En el bloque en el que desea sustituir una imagen:
 ### Eliminar una imagen
 Para eliminar una imagen del bloque deseado, haga clic en `Más acciones` en la miniatura de la imagen y seleccione __Eliminar.__ Después de este procedimiento, la imagen ya no será visible en el bloque.
 
-<div class="alert alert-warning">
-  Cuando se remueve una imagen, no significa que se excluya del repositorio. Para ello, consulte la sección <a href="#funcionalidades-dentro-de-image-widget">Funcionalidades dentro de Image Widget</a>.
-</div>
+>⚠️ Cuando se remueve una imagen, no significa que se excluya del repositorio. Para ello, consulte la sección [Funcionalidades dentro de Image Widget](#funcionalidades-dentro-de-image-widget).
 
diff --git a/docs/tutorials/es/import-customer-data-brazil.md b/docs/tutorials/es/import-customer-data-brazil.md
index b875256b5..aa8b99914 100644
--- a/docs/tutorials/es/import-customer-data-brazil.md
+++ b/docs/tutorials/es/import-customer-data-brazil.md
@@ -17,10 +17,9 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 La importación de datos de clientes debe hacerse en el Master Data. Para el envío de datos, use el artículo [Importando datos en el Master Data](/es/tutorial/importar-datos-en-el-master-data).
 
-<div class="alert alert-danger">
-  <p>Este artículo se refiere a los campos del masterdata específicamente para las tiendas de <strong>Brasil</strong>. Debe verificar los valores válidos para diferentes países.</p>
-  <p>Vea también <a href="https://developers.vtex.com/docs/guides/import-customer-data">importar datos de clientes con la API de Master Data v2</a>.</p>
-</div>
+>❗ Este artículo se refiere a los campos del masterdata específicamente para las tiendas de **Brasil**. Debe verificar los valores válidos para diferentes países.
+>
+> Vea también [importar datos de clientes con la API de Master Data v2](https://developers.vtex.com/docs/guides/import-customer-data).
 
 El checkout trabaja con los datos de las entidades CL (cliente) y AD (dirección).
 
diff --git a/docs/tutorials/es/importing-data-into-master-data.md b/docs/tutorials/es/importing-data-into-master-data.md
index f743f8de3..111e440f1 100644
--- a/docs/tutorials/es/importing-data-into-master-data.md
+++ b/docs/tutorials/es/importing-data-into-master-data.md
@@ -30,17 +30,13 @@ La mejor manera de obtener la planilla de importación es [realizando la exporta
 
 Deje el valor de la columna id vacío y será creado un nuevo registro.
 
-<div class="alert alert-warning">
-Al ingresar los datos en la plantilla, asegúrate de que el formato de los valores de las celdas coincida con el formato esperado por la columna correspondiente. Ejemplos de formatos son número, texto o fecha.
-</div>
+>⚠️ Al ingresar los datos en la plantilla, asegúrate de que el formato de los valores de las celdas coincida con el formato esperado por la columna correspondiente. Ejemplos de formatos son número, texto o fecha.
 
 ## Cómo subir la planilla
 
 Tras la exportación y edición de la planilla exportada, es hora de realizar la importación de los datos. Para ello, siga los puntos a continuación para realizar esta operación:
 
-<div class="alert alert-warning">
-Mantenga el mismo formato de la planilla (xls) para realizar la importación con éxito.
-</div>
+>⚠️ Mantenga el mismo formato de la planilla (xls) para realizar la importación con éxito.
 
 1. En el Admin VTEX, accede **Configuración de la tienda** > **Storefront** > **Master Data.**
 2. Haga clic en la pestaña **Aplicações.**
diff --git a/docs/tutorials/es/importing-images-from-a-spreadsheet.md b/docs/tutorials/es/importing-images-from-a-spreadsheet.md
index 9d65dfff2..50b982afc 100644
--- a/docs/tutorials/es/importing-images-from-a-spreadsheet.md
+++ b/docs/tutorials/es/importing-images-from-a-spreadsheet.md
@@ -35,10 +35,9 @@ El tiempo que tarde este proceso dependerá del tamaño del archivo. Si la plant
 
 Por último, los productos de las filas de la plantilla cuyas imágenes se procesaron con éxito se pondrán en la cola de indexación.
 
-<div class="alert alert-danger">
-<p>Siempre que se importe una plantilla con información de imágenes, el sistema cargará la nueva imagen del SKU. Presta atención a posibles duplicaciones.</p>
-<p>Si se importa por segunda vez una plantilla con información que ya se envió previamente a VTEX, la información no sobrescribirá la imagen anterior: la imagen se duplicará en el registro del SKU.</p>
-</div>
+>❗ Siempre que se importe una plantilla con información de imágenes, el sistema cargará la nueva imagen del SKU. Presta atención a posibles duplicaciones.
+>
+> Si se importa por segunda vez una plantilla con información que ya se envió previamente a VTEX, la información no sobrescribirá la imagen anterior: la imagen se duplicará en el registro del SKU.
 
 ## Cómo completar la plantilla para importar imágenes
 
@@ -65,9 +64,7 @@ No es necesario que cuentes con un servidor FTP propio para enviar las URL de la
 
 Además, para verificar si las URL son correctas, puedes usar un servicio externo que verifique su validez.
 
-<div class="alert alert-warning">
-  <p>Recomendamos que cada imagen no pese más de 3000 KB (3 MB).</p>
-</div>
+>⚠️ Recomendamos que cada imagen no pese más de 3000 KB (3 MB).
 
 ### NomeImagem
 
diff --git a/docs/tutorials/es/importing-the-shipping-spreadsheet.md b/docs/tutorials/es/importing-the-shipping-spreadsheet.md
index d33b9bbed..51f4abc2a 100644
--- a/docs/tutorials/es/importing-the-shipping-spreadsheet.md
+++ b/docs/tutorials/es/importing-the-shipping-spreadsheet.md
@@ -15,9 +15,7 @@ legacySlug: importar-planilla-de-envio
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a <a href="https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envío</a>.
-</div>  
+>ℹ️ Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a [estratégia de envío](https://help.vtex.com/es/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).  
 
 Antes de hacer la importación, es importante ter la plantilla en el modelo VTEX guardada en su máquina, es decir, __idéntica a nuestra Planilla Modelo__, incluso en el formato de las células, con el header y ya en el formato _.xls_ (Excel 97-2003). Para obtener el modelo, haga clic en el enlace __Download de la plantilla modelo__, que queda dentro en la plantilla de configuraciones del transportista.
 
@@ -30,17 +28,11 @@ Antes de hacer la importación, es importante ter la plantilla en el modelo VTEX
 
 Después, quedará una cinta color naranja sobre el transportista que tuvo la inclusión de la tabla de flete, con la información _En procesamiento_. Dependiendo del tamaño del archivo, ese proceso será breve.
 
-<div class="alert alert-warning">
-Recuerde que cada nueva importación sobrescribe las informaciones que fueron importadas anteriormente.
-</div>
+>⚠️ Recuerde que cada nueva importación sobrescribe las informaciones que fueron importadas anteriormente.
 
-<div class="alert alert-warning">
-<strong>Nota 1:</strong> caso las 65.536 líneas de la versión <em>.xls</em> no sean suficientes para el catastro de todos los valores de flete del transportista, será necesario que cree una nueva pestaña dentro del mismo archivo, con el mismo encabezado para seguir llenando las informaciones.
-</div>
+>⚠️ **Nota 1:** caso las 65.536 líneas de la versión *.xls* no sean suficientes para el catastro de todos los valores de flete del transportista, será necesario que cree una nueva pestaña dentro del mismo archivo, con el mismo encabezado para seguir llenando las informaciones.
   
-<div class="alert alert-warning">  
-<strong>Nota 2:</strong>Ponga atención en el tamaño del archivo, pues si él pasa de 10MB será necesario con la extensión <em>.zip</em>. Este archivo .zip también debe tener menos de 10 MB para que el upload funcione. Si, aún así, el archivo excede el límite, recomendamos dividir en más transportistas.
-</div>
+>⚠️ **Nota 2:**Ponga atención en el tamaño del archivo, pues si él pasa de 10MB será necesario con la extensión *.zip*. Este archivo .zip también debe tener menos de 10 MB para que el upload funcione. Si, aún así, el archivo excede el límite, recomendamos dividir en más transportistas.
 
 Para saber cómo registrar el transportista, acceda al artículo [Gestionar transportista](http://help.vtex.com/es/tutorial/gestionar-transportista).
 
diff --git a/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md b/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md
index d2b442d24..b279f47af 100644
--- a/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md
+++ b/docs/tutorials/es/including-order-variables-in-the-transactional-email-template.md
@@ -28,9 +28,7 @@ Estas variables son propiedades de JSON que aparecen en el campo __JSON Data__ y
 
 ### Ejemplo
 
-<div class="alert alert-warning">
-Los ejemplos de JSON Data sólo aparecerán en los templates cuando usted termine la acción deseada en su tienda. Si no ha transacionado un pedido, una recurrencia o cualquier otra acción, el JSON Data aparecerá en blanco.
-</div>
+>⚠️ Los ejemplos de JSON Data sólo aparecerán en los templates cuando usted termine la acción deseada en su tienda. Si no ha transacionado un pedido, una recurrencia o cualquier otra acción, el JSON Data aparecerá en blanco.
 
 Digamos que usted desea insertar el nombre del transportista en el e-mail de pedido enviado.
 
diff --git a/docs/tutorials/es/indexes-in-master-data.md b/docs/tutorials/es/indexes-in-master-data.md
index 7b2c7aa3f..e9346b640 100644
--- a/docs/tutorials/es/indexes-in-master-data.md
+++ b/docs/tutorials/es/indexes-in-master-data.md
@@ -64,9 +64,7 @@ Como resultado, no será posible ingresar un nombre que ya haya sido registrado
 
 En el ejemplo anterior, como ya existe un registro con el **Nombre** igual a **María**, no es posible registrar otro con el mismo valor.
 
-<div class="alert alert-warning">
-  <p>Utiliza la opción <strong>Valores únicos</strong> con precaución: si deseas permitir que un valor se repita, configurarlo como único hará que el sistema bloquee la inserción de registros duplicados, impidiendo su registro.</p>
-</div>
+>⚠️ Utiliza la opción **Valores únicos** con precaución: si deseas permitir que un valor se repita, configurarlo como único hará que el sistema bloquee la inserción de registros duplicados, impidiendo su registro.
 
 #### Varios campos en el índice
 
@@ -82,6 +80,4 @@ En este caso, se puede repetir o el valor del **Nombre** o el valor del **Docume
 
 En el ejemplo anterior, ya existe un registro con el **Nombre** igual a **María**. Es posible incluir otro registro con el mismo **Nombre**, siempre que el valor del **Documento** sea diferente.
 
-<div class="alert alert-warning">
-  <p>Si se repite la misma combinación de valores, el registro no se guardará. Utiliza la opción <strong>Valores únicos</strong> solo cuando no haya ninguna posibilidad de que un conjunto de valores se repita en registros diferentes.</p>
-</div>
+>⚠️ Si se repite la misma combinación de valores, el registro no se guardará. Utiliza la opción **Valores únicos** solo cuando no haya ninguna posibilidad de que un conjunto de valores se repita en registros diferentes.
diff --git a/docs/tutorials/es/installing-the-widget-with-gtm-suiteshare.md b/docs/tutorials/es/installing-the-widget-with-gtm-suiteshare.md
index c6dae2359..0ce2fed6f 100644
--- a/docs/tutorials/es/installing-the-widget-with-gtm-suiteshare.md
+++ b/docs/tutorials/es/installing-the-widget-with-gtm-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: instalando-el-widget-con-gtm
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/integrate-with-carrefour.md b/docs/tutorials/es/integrate-with-carrefour.md
index 5e41bdd6e..f0913736d 100644
--- a/docs/tutorials/es/integrate-with-carrefour.md
+++ b/docs/tutorials/es/integrate-with-carrefour.md
@@ -49,9 +49,7 @@ Las opciones que aparecen son las siguientes:
 - **Mapeamento de SLA de tipo Econômica:** Aquí se debe insertar el [tipo de transportista](/es/tutorial/como-se-maneja-el-tipo-de-entrega) registrada en VTEX que desea utilizar para la entrega `Economica`.
 - **Mapeamento de SLA de tipo Agendada:** Aquí se debe insertar el [tipo de transportista](/es/tutorial/como-se-maneja-el-tipo-de-entrega) registrada en VTEX que desea utilizar para la entrega `Programada`.
 
-<div class="alert alert-warning">
-Atención: es necesario rellenar al menos uno de los campos del mapeo de SLA. En caso de que ninguno de ellos sea prenchido, no será posible simular el flete en VTEX y, consecuentemente, los pedidos hechos en el Carrefour no serán integrados. Además, tampoco será posible guardar el registro de la integración sin que alguno de los campos esté rellenado.
-</div>
+>⚠️ Atención: es necesario rellenar al menos uno de los campos del mapeo de SLA. En caso de que ninguno de ellos sea prenchido, no será posible simular el flete en VTEX y, consecuentemente, los pedidos hechos en el Carrefour no serán integrados. Además, tampoco será posible guardar el registro de la integración sin que alguno de los campos esté rellenado.
 
 Una vez terminada la configuración de esa pantalla, haga clic en el botón **Salvar Configuração**.
 
diff --git a/docs/tutorials/es/integrating-with-amazon.md b/docs/tutorials/es/integrating-with-amazon.md
index 4832358d1..95bc84dfd 100644
--- a/docs/tutorials/es/integrating-with-amazon.md
+++ b/docs/tutorials/es/integrating-with-amazon.md
@@ -15,13 +15,9 @@ legacySlug: integrar-con-amazon
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning"> 
-Esta integración es válida solo para las categorías <b>Actividades al aire libre</b>, <b>Equipaje</b>, <b>Cámara y Foto</b>, <b>Casa y Jardin</b>, <b>Computadoras</b>, <b>Electronicos</b>, <b>Deportes</b>, <b>Joyas</b>, <b>Libros</b>, <b>Materiales de Oficina</b>, <b>Herrajes</b>, <b>Juegos</b>, <b>Zapatos</b> y <b>Ropa</b>.
-</div>
+>⚠️ Esta integración es válida solo para las categorías **Actividades al aire libre**, **Equipaje**, **Cámara y Foto**, **Casa y Jardin**, **Computadoras**, **Electronicos**, **Deportes**, **Joyas**, **Libros**, **Materiales de Oficina**, **Herrajes**, **Juegos**, **Zapatos** y **Ropa**.
 
-<div class="alert alert-warning">
-Esta integración está disponible para Brasil, México, Estados Unidos, Canadá y Europa.
-</div>
+>⚠️ Esta integración está disponible para Brasil, México, Estados Unidos, Canadá y Europa.
 
 ## Autorizar VTEX en el panel Amazon
 
@@ -48,9 +44,7 @@ Antes de configurar la integración, usted debe comprobar si todos los productos
   
   - __Tiempo de Costo__: en Amazon existe el campo `fulfillment latency`, que es __usado para configurar el tiempo de preparación de la entrega de determinado producto.__ Para rellenarlo masivamente a través de la integración, es necesario rellenar el campo [Tiempo de Costo](https://help.vtex.com/es/tutorial/como-crear-muelle) en el registro del muelle asociado a la política comercial usada para Amazon. Si este campo no se rellena, Amazon utilizará el valor _default_ de ellos (2 días).
   
-<div class="alert alert-warning">
-NOTA: Es importante llenar este campo porque si su tienda no está perfomando conforme el tiempo de preparación configurado, retrasando la entrega, su cuenta puede ser bloqueada.
-</div>
+>⚠️ NOTA: Es importante llenar este campo porque si su tienda no está perfomando conforme el tiempo de preparación configurado, retrasando la entrega, su cuenta puede ser bloqueada.
 
 ## Configuración de la integración
 
diff --git a/docs/tutorials/es/integrating-with-buscape-bp.md b/docs/tutorials/es/integrating-with-buscape-bp.md
index 3a1ab05ac..f35caa484 100644
--- a/docs/tutorials/es/integrating-with-buscape-bp.md
+++ b/docs/tutorials/es/integrating-with-buscape-bp.md
@@ -32,9 +32,7 @@ Algunos pasos son esenciales para que empecemos las configuraciones.
 4. Rellene los campos conforme a lo detallado a continuación;
 5. Haga clic en el botón **Guardar Configuración**. Él estará activo sólo si todas las configuraciones están correctas.
 
-<div class="alert alert-warning">
-¡Atención! Para la política comercial hay que configurar por lo menos un boleto o una tarjeta de crédito. Es decir, es necesario que se configuren los medios de pago para el saleschannel específico.
-</div>
+>⚠️ ¡Atención! Para la política comercial hay que configurar por lo menos un boleto o una tarjeta de crédito. Es decir, es necesario que se configuren los medios de pago para el saleschannel específico.
 
 ### Campos
 
diff --git a/docs/tutorials/es/integrating-with-mercado-livre.md b/docs/tutorials/es/integrating-with-mercado-livre.md
index 47a55f4ec..bf70c0455 100644
--- a/docs/tutorials/es/integrating-with-mercado-livre.md
+++ b/docs/tutorials/es/integrating-with-mercado-livre.md
@@ -58,9 +58,7 @@ Los pasos iniciales son esenciales para que las configuraciones se realicen con
 
 &bull; __Descripción del producto__: Este campo se puede rellenar con *plain/text* o *html*. Las descripciones con HTML no son aceptadas para las tiendas de Brasil y Argentina, siendo obligatoria la elección de la opción *plain/text*. Para estos países, las tags HTML serán ignoradas por el Mercado Libre. Para los demás países, las personalizaciones en HTML todavía se permiten. Ver en la sección __Configuración del Template__ las tags aceptadas por el Mercado Libre.
 
-<div class="alert alert-danger">
-<strong>OBS:</strong> A pesar de existir la opción, las descripciones con HTML <strong>no son más aceptadas</strong> por Mercado Libre, siendo obligatoria la elección de la opción <em>plain/text</em>. En breve discontinuamos esta opción de la interfaz. En la sección <strong>Configuración del Template</strong> las tags aceptadas por el Mercado Libre.
-</div>
+>❗ **OBS:** A pesar de existir la opción, las descripciones con HTML **no son más aceptadas** por Mercado Libre, siendo obligatoria la elección de la opción *plain/text*. En breve discontinuamos esta opción de la interfaz. En la sección **Configuración del Template** las tags aceptadas por el Mercado Libre.
 
 
 &bull; __Associar productos a los pick-up points registrados__: Marque esta flag si desea que sus configuraciones de puntos de retirada sean reflejadas en el Mercado Libre. Es importante recordar que sólo son elegibles para esta flag las configuraciones hechas en la sección [Puntos de Retirada](/es/tutorial/configurar-puntos-de-recogida-pickup-points) del módulo __Logistics__.
@@ -71,9 +69,7 @@ Los pasos iniciales son esenciales para que las configuraciones se realicen con
 
 &bull; __Taxa de confiabilidade da categorização automática__: la integración da la opción de categorizar automáticamente sus anuncios a través de una __ferramenta del Mercado Libre__. Esta herramienta depende de la información como el nombre del producto y el precio, y, si no puede inferir correctamente, puede categorizar de manera incorrecta su producto. Por lo tanto, será necesario definir una tasa de confiabilidad en la configuración de la integración. Es decir, el producto sólo se integrará si la tasa devuelta por la herramienta de Mercado Libre está por encima de la que ha configurado. Llene con la tarifa que desee.
 
-  <div class="alert alert-danger">
-<strong>OBS:</strong> VTEX <strong>no</strong> recomienda realizar la categorización de manera automática. Indicamos utilizar la asignación de hoja de cálculo que se explica en <a href="http://help.vtex.com/es/tutorial/mapeo-de-categor%C3%ADas-y-variaciones#categorizacion">este artículo</a>.
-  </div>
+  >❗ **OBS:** VTEX **no** recomienda realizar la categorización de manera automática. Indicamos utilizar la asignación de hoja de cálculo que se explica en [este artículo](http://help.vtex.com/es/tutorial/mapeo-de-categor%C3%ADas-y-variaciones#categorizacion).
 
 &bull; __Stock mínimo__: Como la comunicación entre los sistemas de VTEX y del Mercado Libre no actualiza algunas de las informaciones en tiempo real, el stock exhibido en Mercado Libre puede quedar desfasado en relación a la acción real del producto en su tienda. Para que no se produzcan ventas de productos sin stock, usted debe rellenar este campo con un valor mínimo de stock de seguridad. Así, cuando el stock en el Mercado Libre llegue a este valor, el anuncio será pausado para que no suceda la venta de un producto sin stock.
 
@@ -85,25 +81,20 @@ Los pasos iniciales son esenciales para que las configuraciones se realicen con
   - __Mensagem de envio de tracking__: inserte en este campo el mensaje que desea enviar al cliente __cuando se ha despachado lo pedido__ y la __URL de rastreo está disponible para la consulta__. Es importante destacar que, automáticamente VTEX va insertar en este campo la URL de rastreo justo al lado de su mensaje. Entonces, si la URL no está disponible todavía, recomendamos facturar la pedido sin la URL. Una vez que esté disponible, inserte en el pedido.
 >Ex: "¡Hola! Usted ya puede seguir el estado de su entrega a través de la siguiente URL: http://status.transportadora.com.br/tracking/nº-del-pedido"
 
-  <div class="alert alert-danger">
-OBS: si la URL de rastreo no se rellena en la factura del pedido, este mensaje <strong>no</strong> se enviará.
-  </div>
+  >❗ OBS: si la URL de rastreo no se rellena en la factura del pedido, este mensaje **no** se enviará.
 
   - __Mensagem de pedido entregue__: inserte en este campo el mensaje que desea enviar al cliente cuando el pedido haya sido entregado por el transportista.
 
 &bull; __Atributos omitidos en la plantilla del producto__: Veremos más abajo que, en la configuración de la plantilla para el Mercado Libre, usted puede incluir los atributos del producto que desea que se muestren en el template. La configuración de este campo permite omitir atributos que no desea que aparezcan en la plantilla de Mercado Libre.
 
-<div class="alert alert-warning">>
-Los campos <em>Actualizar descripción del anuncio, el texto para la evaluación automática del comprador y el correo electrónico del afiliado</em> se suspenderán en la UI. Por lo tanto, no es necesario rellenarlos. Las APIs continuarán activas.
-</div>
+>⚠️ >
+> Los campos *Actualizar descripción del anuncio, el texto para la evaluación automática del comprador y el correo electrónico del afiliado* se suspenderán en la UI. Por lo tanto, no es necesario rellenarlos. Las APIs continuarán activas.
 
 
 
 ## Envío de los atributos de los productos para el Mercado Libre
 
-<div class="alert alert-danger">
-Este paso es necesario sólo para las tiendas que venden productos como <strong>ropa, calzado y bolsos</strong>. Si su tienda tiene estos tipos de producto, es necesario hacer el registro de las especificaciones de ellos. Acceda a <a href="https://help.vtex.com/es/tutorial/envio-de-los-atributos-de-ropa-calzado-y-bolsos-para-el-mercado-libre">este artículo</a> para saber cómo hacer este registro. Si su tienda no tiene estos productos, siga directamente a la sección <strong>Configuración del template</strong>
-</div>
+>❗ Este paso es necesario sólo para las tiendas que venden productos como **ropa, calzado y bolsos**. Si su tienda tiene estos tipos de producto, es necesario hacer el registro de las especificaciones de ellos. Acceda a [este artículo](https://help.vtex.com/es/tutorial/envio-de-los-atributos-de-ropa-calzado-y-bolsos-para-el-mercado-libre) para saber cómo hacer este registro. Si su tienda no tiene estos productos, siga directamente a la sección **Configuración del template**
 
 __Listo! __ Usted ha terminado la configuración del *primer paso* de la integración. Ahora vamos a la etapa de __Configuración del Template__.
 
@@ -132,9 +123,7 @@ Si desea incluir todos los atributos y valores de los atributos en la plantilla,
 
 ``{{#each ATRIBUTOS}} {{NOME}} – {{VALOR}} <br> {{/each}}``
 
-<div class="alert alert-info">
-Si desea omitir algún atributo en el template, usted puede hacer esta configuración en el la <strong>configuración de la integración</strong>, rellenando el campo <strong>Atributos omitidos en el template del producto</strong>, como se explica en la sección <strong>Configurar el panel del Mercado Libre en VTEX</strong> del paso anterior.
-</div>
+>ℹ️ Si desea omitir algún atributo en el template, usted puede hacer esta configuración en el la **configuración de la integración**, rellenando el campo **Atributos omitidos en el template del producto**, como se explica en la sección **Configurar el panel del Mercado Libre en VTEX** del paso anterior.
 
 __Muy bien!__ Usted ha terminado el *segundo paso* de la integración! Ahora, vamos a configurar la logística para las entregas de pedidos hechos en Mercado Libre.
 
@@ -178,9 +167,8 @@ En esta modalidad, __hay dos formas de el pedido ser entregado__. Estas formas d
 
 En este escenario, Mercado Libre busca el pedido directamente en los Centros de Distribución de su tienda y hace la entrega al cliente final.
 
-<div class="alert alert-warning">>
-No se recomienda el uso del tipo de entrega <em>Entrega combinada</em>. En pedidos cerrados con este tipo de entrega, como no tenemos la información de la dirección de entrega, el pedido no se integrará con VTEX. Para que un pedido sea integrado correctamente, es necesario que tenga la información de entrega. Por lo tanto, siempre recomendamos utilizar el <strong>Mercado Envíos</strong>.
-</div>
+>⚠️ >
+> No se recomienda el uso del tipo de entrega *Entrega combinada*. En pedidos cerrados con este tipo de entrega, como no tenemos la información de la dirección de entrega, el pedido no se integrará con VTEX. Para que un pedido sea integrado correctamente, es necesario que tenga la información de entrega. Por lo tanto, siempre recomendamos utilizar el **Mercado Envíos**.
 
 
 ### Convivencia Logística
@@ -189,13 +177,9 @@ Con el objetivo de mejorar la experiencia logística con la integración del Mer
 
 _`Ex:` usted vende electrodomésticos. La entrega de artículos grandes, como neveras y cocinas, es hecha por usted (modalidad ME1). Pero usted quiere que Mercado Libre haga la entrega (modo ME2) de elementos más pequeños, como tostadoras, licuadores, mezcladores, etc._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> sólo tiendas que ya son ME1 pueden tener ME2 también.
-</div>
+>⚠️ **OBS:** sólo tiendas que ya son ME1 pueden tener ME2 también.
 
-<div class="alert alert-warning">
-<strong>OBS2:</strong> para poder usar las dos opciones, primero deberá haber un acuerdo directamente con el asesor comercial de Mercado Libre, ya que esa aún no es una funcionalidad pública.
-</div>
+>⚠️ **OBS2:** para poder usar las dos opciones, primero deberá haber un acuerdo directamente con el asesor comercial de Mercado Libre, ya que esa aún no es una funcionalidad pública.
 
 De esta manera, es necesario segmentar sus productos indicando para la integración cuáles serán asignados a la modalidad ME2. Para ello, siga el paso a paso siguiente:
 
@@ -203,13 +187,15 @@ De esta manera, es necesario segmentar sus productos indicando para la integraci
 2. Esta especificación debe recibir el valor `me2`.
 3. Después de registrar la especificación, debe acceder al registro de cada producto y asignar el valor a la especificación. O lo hace de manera masiva a través [de este tutorial](/es/tutorial/importando-e-exportando-especificacao-de-produto-e-sku).
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> es importante comprobar si la categoría en la que está enviando los productos está apta para usar ME2. Acceda a la siguiente URL en el navegador (sustituyendo la variable entre claves {CategoryId} por el ID de la categoría de Mercado Libre) para comprobar.
-<br></br>
-api.mercadolibre.com/categories/{CategoryId}
-<br></br>
-Puede ver esto en el campo <em>"shipping_modes"</em>. Si el campo tiene el valor "me2", significa que la categoría acepta esta modalidad de entrega.
-</div>
+>⚠️ **OBS:** es importante comprobar si la categoría en la que está enviando los productos está apta para usar ME2. Acceda a la siguiente URL en el navegador (sustituyendo la variable entre claves {CategoryId} por el ID de la categoría de Mercado Libre) para comprobar.
+>
+>
+> </br>
+> api.mercadolibre.com/categories/{CategoryId}
+>
+>
+> </br>
+> Puede ver esto en el campo *"shipping_modes"*. Si el campo tiene el valor "me2", significa que la categoría acepta esta modalidad de entrega.
 
 
 __Listo!__ Usted cumplió el *tercer paso*! Ahora ya tiene la información necesaria para manejar el envío de pedidos realizados en Mercado Libre. Vamos a la última etapa: __Autorizar su integración__.
@@ -226,9 +212,8 @@ Para realizar este paso, accede a [este artículo](/es/tutorial/mapeo-de-categor
 
 Después de realizar las configuraciones anteriores, es necesario autorizar su integración con el Mercado Libre. Siga los pasos abajo:
 
-<div class="alert alert-warning">>
-El Mercado Libre requiere que la autorización sea efectuada por el <strong>usuario Master</strong> de la cuenta en Mercado Libre.
-</div>
+>⚠️ >
+> El Mercado Libre requiere que la autorización sea efectuada por el **usuario Master** de la cuenta en Mercado Libre.
 
 1. En el menu del Admin, haga clic en __Intgraciones__.
 2. Haga clic en __Configuración__.
diff --git a/docs/tutorials/es/integrating-with-netshoes.md b/docs/tutorials/es/integrating-with-netshoes.md
index 94a06c643..63c8d71fa 100644
--- a/docs/tutorials/es/integrating-with-netshoes.md
+++ b/docs/tutorials/es/integrating-with-netshoes.md
@@ -45,17 +45,13 @@ Netshoes es uno de los mayores marketplace de artículos deportivos y está disp
 
 _`Ej.: `imagine que usted utiliza Correios (PAC) como transportista y su Tipo de Transportista en el panel de transportadoras de VTEX se denomina "Común". Entonces, debe escribir en el campo el nombre __Común__. Recuerde que la palabra debe ser exactamente igual a la registrada en la sección Inventario y envío._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> si se deja el campo en blanco, la integración usará la transportadora <strong>más barato disponible</strong> en el momento de integrar el pedido.
-</div>	
+>⚠️ **OBS:** si se deja el campo en blanco, la integración usará la transportadora **más barato disponible** en el momento de integrar el pedido.	
 
 - **Mapeo de Tipo de Entrega (SLA) -> Expresa:** Ingresa el [tipo de transportadora](/es/tutorial/como-se-maneja-el-tipo-de-entrega) que desea utilizar para entrega __expresa__.
 
 _`Ej.:` imagine que usted utiliza la transportadora XPTO, que entrega más rápido, pero es más caro. Su Tipo de Transportista en el panel de transportadoras de VTEX se llama "Entrega Rápida". Entonces, debe escribir en el campo el nombre __Entrega Rápida__. Recuerde que la palabra debe ser exactamente igual a la registrada en la sección de Inventario y envío._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> si se deja el campo en blanco, la integración usará la transportadora <strong>más barato disponible</strong> en el momento de integrar el pedido.
-</div>
+>⚠️ **OBS:** si se deja el campo en blanco, la integración usará la transportadora **más barato disponible** en el momento de integrar el pedido.
 
 _Leyenda:_<br />
 `*` Campos obligatorios.<br />
@@ -83,13 +79,9 @@ La implementación de esta API permite que Netshoes consulte, en tiempo real, el
 
 `http://{accountName}.vtexcommercestable.com.br/api/netshoesintegration/freight`
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> si los Mapeos de Entrega no se han realizado, no habrá retorno de informaciones de entrega y flete para esta API.
-</div> 
+>⚠️ **OBS:** si los Mapeos de Entrega no se han realizado, no habrá retorno de informaciones de entrega y flete para esta API. 
 
-<div class="alert alert-warning">
-<strong>OBS 2:</strong> para que la consulta de la API se realice con éxito, el ID de la transportadora y el ID del muelle en VTEX debe ser un valor que contenga solamente números.
-</div>
+>⚠️ **OBS 2:** para que la consulta de la API se realice con éxito, el ID de la transportadora y el ID del muelle en VTEX debe ser un valor que contenga solamente números.
 
 Este es el _segundo paso_ de la integración. Para concluir el proceso, es necesario realizar el envío de las especificaciones de sus productos a Netshoes.
 
@@ -108,9 +100,7 @@ El Mapeo debe realizarse siempre que un producto se envíe por primera vez a Net
 
 Siga el paso a paso siguiente, haciendo el de / para en la __Planilla de Mapeo__ entre lo que está registrado en su producto en VTEX y los valores especificados de acuerdo con la __Planilla de Consulta__ de Netshoes.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> cualquier valor usado que no esté en la Planilla de Consulta va a ocasionar un error de integración.
-</div>
+>⚠️ **OBS:** cualquier valor usado que no esté en la Planilla de Consulta va a ocasionar un error de integración.
 
 1. __ID del SKU:__ es el ID del SKU en VTEX. Este es el Id del SKU que usted desea enviar a Netshoes.
 
@@ -124,8 +114,7 @@ Siga el paso a paso siguiente, haciendo el de / para en la __Planilla de Mapeo__
 <br/>_`Ej:` usted está mapeando una camisa Nike. De acuerdo con la Planilla de Consulta, la columna __Marca__ debe rellenarse con el valor `Nike`.
 
 <br/>
-<div class="alert alert-warning">
-<strong>OBS:</strong> si la marca de sus productos no está en la Planilla de Consulta, entre en contacto con Netshoes solicitando la inclusión de esta en el sistema. Una vez que confirmen el registro, usted podrá utilizar la marca en el mapeo. Si ellos no lo tienen registrado aún, el producto va a sufrir un error de integración.</div>
+>⚠️ **OBS:** si la marca de sus productos no está en la Planilla de Consulta, entre en contacto con Netshoes solicitando la inclusión de esta en el sistema. Una vez que confirmen el registro, usted podrá utilizar la marca en el mapeo. Si ellos no lo tienen registrado aún, el producto va a sufrir un error de integración.
 
 5. __Color__: rellene con el valor del Color del SKU.
 <br/>_`Ej.:` usted está mapeando un short azul y blanco. De acuerdo con la Planilla de Consulta, la columna __Color__ debe rellenarse con el valor `Azul+Blanco`._
diff --git a/docs/tutorials/es/integrating-with-viavarejo-cnova.md b/docs/tutorials/es/integrating-with-viavarejo-cnova.md
index 750b5f725..b61961815 100644
--- a/docs/tutorials/es/integrating-with-viavarejo-cnova.md
+++ b/docs/tutorials/es/integrating-with-viavarejo-cnova.md
@@ -39,9 +39,7 @@ Este artículo tiene por objetivo orientar el registro de la integración con Vi
 
 &bull; __Nombre del campo de especificación de producto que contiene su descripción__: si desea utilizar una descripción diferente de la que ya está registrada en el catálogo de VTEX, usted tiene la opción de crear un [campo de producto](/es/tutorial/criando-um-campo-de-produto) de tipo _Texto Grande_. Rellenando ese campo, la integración va a priorizar el envío de la descripción contenida en él (en lugar de la descripción original del producto).
 
-<div class="alert alert-danger">
-<strong>OBS:</strong> atente a las configuraciones en la creación de este nuevo campo para que la nueva información creada <strong>no</strong> aparezca en su sitio.
-</div>
+>❗ **OBS:** atente a las configuraciones en la creación de este nuevo campo para que la nueva información creada **no** aparezca en su sitio.
 
 & bull; __Tasa de Divergencia de Precio\*:__ es la tasa de aceptación de la diferencia de valor de un pedido. Cualquier pedido que tenga una diferencia entre el precio de venta en el marketplace y el precio determinado por el seller [será comparado con ese valor](/es/faq/por-que-el-pedido-fue-cerrado-con-el-precio-incorrecto). Si la divergencia, en porcentual, es menor que el valor definido en ese campo, el pedido se integrará normalmente. En caso contrario, el pedido no se integrará y usted podrá verlo en la pestaña de pedidos [dentro de la sección de integraciones en el Admin](/es/tutorial/como-verificar-la-integracion-en-bridge).
 
diff --git a/docs/tutorials/es/integrating-with-walmart.md b/docs/tutorials/es/integrating-with-walmart.md
index 2ed2d11f4..1056e7c5a 100644
--- a/docs/tutorials/es/integrating-with-walmart.md
+++ b/docs/tutorials/es/integrating-with-walmart.md
@@ -43,9 +43,7 @@ Algunos pasos son esenciales para iniciar la configuración.
 
 Después de la configuración, la integración envía todos los productos asociados a la poítica comercial determinada para Walmart.
 
-<div class="alert alert-warning">
-<strong>Importante:</strong> Walmart no acepta código HTML en los campos de descripción del producto y campos de especificación.
-</div>
+>⚠️ **Importante:** Walmart no acepta código HTML en los campos de descripción del producto y campos de especificación.
 
 
 ## Flujo de la integración
@@ -66,6 +64,4 @@ El __fluxo de pedidos__ y __consulta de envío__ está restringido a Walmart, qu
 2 - [Autenticar la integración](/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones)
 Después de realizar todos estos pasos, tendrá que autenticar la integración con Walmart. Para que esto suceda, sólo tiene que enviar el appKey a ellos (ver cómo [generar el appKey para la autenticación de las integraciones](/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones)). Si tiene alguna duda sobre el proceso, póngase en contacto con el equipo de Walmart.
 
-<div class="alert alert-warning">
-Recuerde que el appKey debe estar asociado al perfil de acceso <strong>IntegrationProfile - Fulfillment</strong>. Es el que tiene los permisos necesarios para realizar el proceso de integración con el marketplace.
-</div>
+>⚠️ Recuerde que el appKey debe estar asociado al perfil de acceso **IntegrationProfile - Fulfillment**. Es el que tiene los permisos necesarios para realizar el proceso de integración con el marketplace.
diff --git a/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md b/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
index 289c492da..ef99588cd 100644
--- a/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
+++ b/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
@@ -15,9 +15,7 @@ legacySlug: integracao-entre-marketplace-nao-vtex-e-sellers-vtex-acoes-referente
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div>
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) en nuestro Developer Portal.
 
 Uno de los pasos para integrar un Marketplace que no es VTEX a un Seller VTEX es permitir consultas al __Catálogo__ de VTEX con el objetivo de obtener informaciones de cambio de precio, inventario, catálogo y datos de flete.
 
@@ -293,9 +291,21 @@ El Marketplace debe entonces usar la __API de Fulfillment Simulation__ para obte
 
 Esa llamada simula un carrito en el Checkout de VTEX, devolviendo la versión más actualizada de esos datos.
 
-<div class="alert alert-warning">
-La llamada de Fulfillment Simulation debe ser usada por el Marketplace siempre que sea necesario obtener precio, inventario y datos de flete actualizados. Para ofrecer una integración en tiempo real y, como consecuencia, una experiencia de compra fluida, el Marketplace debe obtener esos dados en todas las etapas de la jornada del cliente en la tienda:<br>- Vitrina<br>- Página de producto<br>- Carrito<br>- Checkout<br>- Order Placed<br><br>Con eso, usted garantiza que el cliente no será sorprendido por posibles cambios en un SKU ocurridos en el Seller y no informados en el  Marketplace. 
-</div>
+>⚠️ La llamada de Fulfillment Simulation debe ser usada por el Marketplace siempre que sea necesario obtener precio, inventario y datos de flete actualizados. Para ofrecer una integración en tiempo real y, como consecuencia, una experiencia de compra fluida, el Marketplace debe obtener esos dados en todas las etapas de la jornada del cliente en la tienda:
+>
+> - Vitrina
+>
+> - Página de producto
+>
+> - Carrito
+>
+> - Checkout
+>
+> - Order Placed
+>
+> 
+>
+> Con eso, usted garantiza que el cliente no será sorprendido por posibles cambios en un SKU ocurridos en el Seller y no informados en el  Marketplace.
 
 ### Ejemplo de llamada API REST:
 
@@ -341,9 +351,7 @@ Accede a una tienda VTEX (*Seller*) y busca precio, inventario y datos de flete
 | quantity       | integer       |   Cantidad del SKU deseado  |  Sí  |
 | seller       | string       |   ID del seller que vende el SKU deseado. En el contexto de simulación de fulfillment, el seller debe ser siempre "1" - "seller 1" significa que es el mismo  fulfillment en cuestión.  |   Sí   |
 
-<div class="alert alert-warning">
-La simulación para obtener precio/disponibilidad solo debe hacerse con <strong>1 unidad</strong> del ítem específico. Las simulaciones de carrito deben naturalmente incluir todos los ítems deseados, para garantizar el contexto de esos ítems cuando están juntos en el carrito, lo cual es de especial importancia para el cálculo del flete.
-</div>
+>⚠️ La simulación para obtener precio/disponibilidad solo debe hacerse con **1 unidad** del ítem específico. Las simulaciones de carrito deben naturalmente incluir todos los ítems deseados, para garantizar el contexto de esos ítems cuando están juntos en el carrito, lo cual es de especial importancia para el cálculo del flete.
 
 #### Ejemplo de body de respuesta
 
diff --git a/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller.md b/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller.md
index 789f6583c..477ab2757 100644
--- a/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller.md
+++ b/docs/tutorials/es/integration-between-non-vtex-marketplace-and-vtex-seller.md
@@ -15,9 +15,7 @@ legacySlug: integración-entre-marketplace-que-no-es-vtex-y-seller-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div> 
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) en nuestro Developer Portal. 
 
 El último paso para integrar un  Marketplace que no es VTEX a un Seller VTEX es permitir la comunicación con el Seller sobre __pedidos__ realizados en el  Marketplace.
 
@@ -423,9 +421,13 @@ Endpoint: `https://{AccountName}.[vtexcommercestable.com.br/api/fulfillment/pvt/
 
 ## Marketplace Services Endpoint  
 
-<div class="alert alert-info">  
-El <strong>Marketplace Services Endpoint</strong> es un endpoint que debe ser creado por el Marketplace, con el objetivo de recibir tres informaciones diferentes enviadas por el Seller:<br>- Factura<br>- Código de rastreo de la transportadora (si existiera)<br>- Solicitación de cancelación (si sucediera)  
-</div>  
+>ℹ️ El **Marketplace Services Endpoint** es un endpoint que debe ser creado por el Marketplace, con el objetivo de recibir tres informaciones diferentes enviadas por el Seller:
+>
+> - Factura
+>
+> - Código de rastreo de la transportadora (si existiera)
+>
+> - Solicitación de cancelación (si sucediera)  
 
 Para los tres próximos pasos de la integración, el Marketplace necesita:
 
@@ -512,8 +514,7 @@ El vendedor envía el código y la URL de rastreo al __Marketplace Services Endp
 
 Para recibir el código de rastreo, el endpoint final esperado debe ser: `https://{marketplaceServicesEndpoint}/pvt/orders/{marketplaceOrderId}/invoice`  
 
-<div class="alert alert-info">  
-Aunque la ruta para recibir el código de rastreo sea la misma donde el Marketplace recibe la Factura (<code>.../invoice</code>), estos dos procesos ocurren en dos etapas. Es decir, en una primera llamada, el Seller envía los datos de la Factura; y, en una segunda llamada, envía los datos de rastreo.</div>
+>ℹ️ Aunque la ruta para recibir el código de rastreo sea la misma donde el Marketplace recibe la Factura (`.../invoice`), estos dos procesos ocurren en dos etapas. Es decir, en una primera llamada, el Seller envía los datos de la Factura; y, en una segunda llamada, envía los datos de rastreo.
 
 ## 6) Recibir solicitud de cancelación - Seller llama endpoint del Marketplace (Marketplace Services Endpoint)  
 
diff --git a/docs/tutorials/es/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md b/docs/tutorials/es/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
index b7fb26885..bd8b4e923 100644
--- a/docs/tutorials/es/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
+++ b/docs/tutorials/es/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
@@ -293,10 +293,6 @@ Recibiendo este payload, el integrador debe utilizar esta información para deci
 - Si se ha producido un cambio de precio o de stock, el integrador debe llamar a la ruta `https://{accountName}.vtexcommercestable.com.br/api/fulfillment/pvt/orderForms/simulation?sc={salesChannel}&affiliateId={affiliateId}`, como se describe en la sección [Obtener los datos de precio y stock de los SKUs](#3-obtener-los-datos-de-precio-y-stock-de-los-skus).
 - Si se ha producido un cambio en el SKU que no sea de precio o de stock, el integrador debe llamar a la ruta `http://{{accountName}}.vtexcommercestable.com.br/api/catalog_system/pvt/sku/stockkeepingunitbyid/{{skuId}}`, como se describe en la sección [Obtener los datos sobre las propiedades de los SKUs](#2-obtener-los-datos-sobre-las-propiedades-de-los-skus).
 
-<div class="alert alert-warning">
-Si se inserta un nuevo SKU en el catálogo, se le notificará en el endpoint de cada afiliado. Por tratarse de un nuevo SKU, es necesario realizar el llenado de los datos de este nuevo SKU en la base de datos del servicio externo. El integrador debe comprobar si el SKU notificado aún no existe en la base de datos del servicio externo. Si se trata de un nuevo SKU, el integrador debe seguir los mismos pasos descritos en la sección <strong>Realizar la primera carga con los datos de SKUs</strong>. Si es un SKU ya existente, el integrador debe seguir los pasos de la sección <strong>Actualizar los datos de SKUs</strong>.
-</div>
+>⚠️ Si se inserta un nuevo SKU en el catálogo, se le notificará en el endpoint de cada afiliado. Por tratarse de un nuevo SKU, es necesario realizar el llenado de los datos de este nuevo SKU en la base de datos del servicio externo. El integrador debe comprobar si el SKU notificado aún no existe en la base de datos del servicio externo. Si se trata de un nuevo SKU, el integrador debe seguir los mismos pasos descritos en la sección **Realizar la primera carga con los datos de SKUs**. Si es un SKU ya existente, el integrador debe seguir los pasos de la sección **Actualizar los datos de SKUs**.
 
-<div class="alert alert-info">
-Si desea integrar las formas de pago de un seller VTEX con un marketplace externo, <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">acceda a nuestra documentación</a>.
-</div>
+>ℹ️ Si desea integrar las formas de pago de un seller VTEX con un marketplace externo, [acceda a nuestra documentación](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
diff --git a/docs/tutorials/es/integration-guide-for-erps-express-catalog.md b/docs/tutorials/es/integration-guide-for-erps-express-catalog.md
index 966113cbb..730336284 100644
--- a/docs/tutorials/es/integration-guide-for-erps-express-catalog.md
+++ b/docs/tutorials/es/integration-guide-for-erps-express-catalog.md
@@ -15,7 +15,7 @@ legacySlug: guia-de-integracion-de-erps-catalogo-expreso
 subcategory: 5fKgQZhrCw88ACy6Su6GUc
 ---
 
-<div class="alert alert-warning">Este artículo es parte de la <a href="https://help.vtex.com/tutorial/guia-de-integracion-de-erps--3VuOwNLmb624ImooEIIkmO">Guía de integración de ERPs</a>.</div>
+>⚠️ Este artículo es parte de la [Guía de integración de ERPs](https://help.vtex.com/tutorial/guia-de-integracion-de-erps--3VuOwNLmb624ImooEIIkmO).
 
 Este documento tiene como objetivo auxiliar en la integración de catálogo del ERP para una tienda hospedada en VTEX, de una manera rápida.
 
diff --git a/docs/tutorials/es/integration-guide-for-erps-full-catalog.md b/docs/tutorials/es/integration-guide-for-erps-full-catalog.md
index 2d5db625b..68fd4e440 100644
--- a/docs/tutorials/es/integration-guide-for-erps-full-catalog.md
+++ b/docs/tutorials/es/integration-guide-for-erps-full-catalog.md
@@ -15,7 +15,7 @@ legacySlug: guia-de-integracion-de-erps-catalogo-completo
 subcategory: 5fKgQZhrCw88ACy6Su6GUc
 ---
 
-<div class="alert alert-warning">Este artículo es parte de la <a href="https://help.vtex.com/tutorial/guia-de-integracion-de-erps--3VuOwNLmb624ImooEIIkmO">Guía de integración de ERPs</a>.</div>
+>⚠️ Este artículo es parte de la [Guía de integración de ERPs](https://help.vtex.com/tutorial/guia-de-integracion-de-erps--3VuOwNLmb624ImooEIIkmO).
 
 Este documento tiene como objetivo auxiliar en la integración de catálogo (departamento, categoría, marca, imágenes, campos, valores de campo, activación de SKU) del ERP a una tienda alojada en VTEX. En este tipo de integración la mayoría de la administración de la tienda está ERP.
 
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-old.md b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-old.md
index 87b263b87..af8037ac2 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-old.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-old.md
@@ -15,6 +15,4 @@ legacySlug: guia-de-integracion-para-marketplaces-marketplace-non-vtex-old
 subcategory: 
 ---
 
-<div class="alert alert-info">     
-  Contenido en construcción
-</div>
+>ℹ️ Contenido en construcción
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
index bc6ab752b..b60230a88 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
@@ -15,6 +15,4 @@ legacySlug: guia-de-integracion-para-marketplaces-marketplace-non-vtex-con-pago
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div>
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) en nuestro Developer Portal.
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md
index f99721855..715103db1 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md
@@ -15,9 +15,7 @@ legacySlug: guia-de-integracion-para-marketplaces-marketplace-non-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div>
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) en nuestro Developer Portal.
 
 Este documento ayuda en la integración de un Marketplace no hospedado en la plataforma VTEX con un Seller hospedado en la plataforma VTEX. 
 
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md b/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
index b14fa575d..3881d9ebb 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
@@ -15,6 +15,4 @@ legacySlug: guia-de-integraccion-para-marketplaces-seller-non-vtex-con-pago
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div>
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector) en nuestro Developer Portal.
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md b/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md
index 8c72655de..6eee1a529 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-seller-non-vtex.md
@@ -15,7 +15,5 @@ legacySlug: guia-de-integracion-para-marketplaces-seller-non-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div> 
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector) en nuestro Developer Portal. 
 
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces.md b/docs/tutorials/es/integration-guide-for-marketplaces.md
index 5b2d891ff..f1cc79720 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces.md
@@ -15,6 +15,4 @@ legacySlug: guia-de-integracion-para-marketplaces
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Consulte la versión actualizada de esta <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guía de integración con marketplaces</a> en nuestro Developer Portal.
-</div>  
+>⚠️ Consulte la versión actualizada de esta [guía de integración con marketplaces](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) en nuestro Developer Portal.  
diff --git a/docs/tutorials/es/integration-interfaces.md b/docs/tutorials/es/integration-interfaces.md
index a370c42ef..e5faa9576 100644
--- a/docs/tutorials/es/integration-interfaces.md
+++ b/docs/tutorials/es/integration-interfaces.md
@@ -46,9 +46,7 @@ A continuación se incluyen documentación que puede ayudar a iniciar las integr
 
 ### Web Service
 
-<div class="alert alert-warning">
-El Web Service VTEX debe ser usado lo menos posible para los procesos de integración.
-</div>
+>⚠️ El Web Service VTEX debe ser usado lo menos posible para los procesos de integración.
 
 Con excepción del Catálogo (Categorías, Marcas, Productos y SKU), que está con su API REST en desarrollo, todos los demás módulos de VTEX poseen APIs REST bien definidas y de alto rendimiento.
 
diff --git a/docs/tutorials/es/integration-with-google-tag-manager.md b/docs/tutorials/es/integration-with-google-tag-manager.md
index fb2cd89a1..7798fa465 100644
--- a/docs/tutorials/es/integration-with-google-tag-manager.md
+++ b/docs/tutorials/es/integration-with-google-tag-manager.md
@@ -15,9 +15,7 @@ legacySlug: integracion-con-google-tag-manager
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-<div class="alert alert-warning">
-Si su tienda está construida en <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">Store Framework</a>, debe instalar la aplicación de pixel del Google Tag Manager para hacer la integración con todas las páginas. Vea cómo hacerlo en la <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">documentación de la app</a>.
-</div>
+>⚠️ Si su tienda está construida en [Store Framework](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), debe instalar la aplicación de pixel del Google Tag Manager para hacer la integración con todas las páginas. Vea cómo hacerlo en la [documentación de la app](https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager).
 
 Google Tag Manager es un sistema de gestión de etiquetas creado por Google para gestionar etiquetas JavaScript y HTML utilizadas para seguimiento y análisis de sitios web.
 
@@ -52,9 +50,7 @@ Después, debes configurar el código de identificación de la tienda en Tag Man
 
 Para verificar eventos (activadores) y variables disponibles en las páginas que se utilizarán en las etiquetas, puedes utilizar el modo de vista previa de Google Tag Manager. Consulta este artículo en [Google Tag Manager](https://support.google.com/tagmanager/answer/6261285?hl=es) para más información.
 
-<div class="alert alert-info">
-Puedes utilizar el píxel de Facebook junto al Google Tag Manager de tu tienda para realizar un seguimiento y optimizar los resultados de tus campañas de marketing en la red social. Consulta el paso a paso <a href="https://es-es.facebook.com/business/help/1021909254506499">en este artículo de Facebook</a>.
-</div>
+>ℹ️ Puedes utilizar el píxel de Facebook junto al Google Tag Manager de tu tienda para realizar un seguimiento y optimizar los resultados de tus campañas de marketing en la red social. Consulta el paso a paso [en este artículo de Facebook](https://es-es.facebook.com/business/help/1021909254506499).
 
 ## VTEX IO: instalar el píxel de Google Tag Manager
 
diff --git a/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
index 3c0724f12..773780dac 100644
--- a/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/es/intelligent-search-synonym-suggestions-beta.md
@@ -15,9 +15,7 @@ legacySlug: sugerencias-de-sinonimos-de-intelligent-search-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad está disponible para cuentas que tengan un número mínimo de sesiones y pedidos para que el modelo de Inteligencia Artificial sea entrenado. Si estás interesado en implementarla en el futuro, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>. Pueden aplicarse cargos adicionales en el futuro.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible para cuentas que tengan un número mínimo de sesiones y pedidos para que el modelo de Inteligencia Artificial sea entrenado. Si estás interesado en implementarla en el futuro, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support). Pueden aplicarse cargos adicionales en el futuro.
 
 La funcionalidad [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) te permite registrar palabras o expresiones con el mismo significado para los términos de búsqueda utilizados por los clientes al realizar búsquedas en tu tienda, lo que aumenta las posibilidades de que obtengan resultados de búsqueda relevantes.
 
diff --git a/docs/tutorials/es/intelligent-synonyms.md b/docs/tutorials/es/intelligent-synonyms.md
index b59ea3187..8e55b901a 100644
--- a/docs/tutorials/es/intelligent-synonyms.md
+++ b/docs/tutorials/es/intelligent-synonyms.md
@@ -15,9 +15,7 @@ legacySlug: sinonimos-inteligentes
 subcategory: BBzMtJan1UTxC9QZODnlN
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad está disponible para cuentas que tengan una cantidad mínima de sesiones y pedidos para que el modelo de inteligencia artificial sea entrenado. Si estás interesado en implementarla, por favor, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro Soporte</a>. Es posible que se apliquen tarifas adicionales en el futuro.</p>
-</div>
+>ℹ️ Esta funcionalidad está disponible para cuentas que tengan una cantidad mínima de sesiones y pedidos para que el modelo de inteligencia artificial sea entrenado. Si estás interesado en implementarla, por favor, ponte en contacto con [nuestro Soporte](https://help.vtex.com/es/support). Es posible que se apliquen tarifas adicionales en el futuro.
 
 La funcionalidad [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) te permite registrar palabras o expresiones con el mismo significado para los términos de búsqueda utilizados por los clientes al realizar búsquedas en tu tienda, lo que aumenta las posibilidades de que obtengan resultados de búsqueda relevantes.
 
diff --git a/docs/tutorials/es/interaction-details.md b/docs/tutorials/es/interaction-details.md
index 91aac4820..eeabc078c 100644
--- a/docs/tutorials/es/interaction-details.md
+++ b/docs/tutorials/es/interaction-details.md
@@ -15,12 +15,10 @@ legacySlug: detalles-del-interaccion
 subcategory: 
 ---
 
-<div class="alert alert-info">
-Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
-Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
-Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
- </div>  
+>ℹ️ Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de **Gestión de anuncios**.
+> Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+> Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del [Developer Portal](https://developers.vtex.com/updates/release-notes) y el [VTEX Help Center](https://help.vtex.com/pt/en/announcements).  
 
 La página **Detalles de la interacción** del módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) permite que los sellers visualicen de forma más completa todas las interacciones que ocurren en un anuncio durante su proceso de envío y sincronización con un canal. Detalles de la interacción estarán disponibles durante diez días después del registro.
 
diff --git a/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
index f1e2029db..990238091 100644
--- a/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/es/interpreting-the-data-of-the-oms-order-bar.md
@@ -35,9 +35,7 @@ En el screenshot de las métricas arriba, podemos ver la siguiente información:
 - Y el mismo día de la semana pasada, también hasta las 20h50, hubo 1856 pedidos;
 - Finalmene, en relación a un año atrás, hubo un incremento expresivo en el número de pedidos: el mismo día del año pasado, hasta la misma hora, fueron 1425 pedidos, contra los 2464 de este año.
 
-<div class="alert alert-info">
-El cálculo de pedidos realizados en el <b>año pasado</b> se hace restando 52 semanas del día actual. De esta forma, se mantiene el día de la semana. Por ejemplo: el día 24/noviembre/2017 se comparará con el día 25/noviembre/2016, donde ambas fechas son el viernes.
-</div>
+>ℹ️ El cálculo de pedidos realizados en el **año pasado** se hace restando 52 semanas del día actual. De esta forma, se mantiene el día de la semana. Por ejemplo: el día 24/noviembre/2017 se comparará con el día 25/noviembre/2016, donde ambas fechas son el viernes.
 
 El ranking ubicado en la esquina derecha de la barra con esos datos muestra la posición de la tienda entre todas las tiendas VTEX, con la métrica al lado indicando la evolución entre ayer y hoy.
 
diff --git a/docs/tutorials/es/introduction-to-vtex-apis.md b/docs/tutorials/es/introduction-to-vtex-apis.md
index 017e0d497..3ac1b7629 100644
--- a/docs/tutorials/es/introduction-to-vtex-apis.md
+++ b/docs/tutorials/es/introduction-to-vtex-apis.md
@@ -125,8 +125,6 @@ A la derecha de esas indicaciones, el Postman exhibe, para cada API, un Sample R
  
 Para algunas APIs, hay también una Sample Response, que es un ejemplo de respuesta a aquel request.
  
-<div class="alert alert-warning">
-Todo el contenido que aparece entre llaves (**{{contenido}}**) es una variable, y debe ser reemplazado por el dato correcto antes de que se realice el request. Es el caso, por ejemplo, del nombre de su tienda, del ambiente deseado y de los de AppKey y AppToken.
-</div>
+>⚠️ Todo el contenido que aparece entre llaves (**{{contenido}}**) es una variable, y debe ser reemplazado por el dato correcto antes de que se realice el request. Es el caso, por ejemplo, del nombre de su tienda, del ambiente deseado y de los de AppKey y AppToken.
 
 Vea cómo crear su appKey y appToken en el artículo [Crear appKey y appToken para autenticar las integraciones](/es/tutorial/crear-appkey-y-apptoken-para-autenticar-las-integraciones).
diff --git a/docs/tutorials/es/inventory-update-history.md b/docs/tutorials/es/inventory-update-history.md
index aafb711a4..2e032770c 100644
--- a/docs/tutorials/es/inventory-update-history.md
+++ b/docs/tutorials/es/inventory-update-history.md
@@ -36,8 +36,6 @@ Para ver los movimientos de un SKU:
   * La cantidad de ítems antes de la actualización.
   * La cantidad de ítems después de la actualización.
 
-<div class="alert alert-warning">
-Solo puedes consultar las últimas 50 actualizaciones en el registro de actualizaciones de un determinado SKU.
-</div>
+>⚠️ Solo puedes consultar las últimas 50 actualizaciones en el registro de actualizaciones de un determinado SKU.
 
 La cantidad total de ítems en la página [Gestión de stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139) se actualiza en tiempo real, pero puede haber un retraso de hasta 1 hora para que la información aparezca en el historial de movimientos.
diff --git a/docs/tutorials/es/kit-registration.md b/docs/tutorials/es/kit-registration.md
index 5c821c679..54c912be4 100644
--- a/docs/tutorials/es/kit-registration.md
+++ b/docs/tutorials/es/kit-registration.md
@@ -71,9 +71,7 @@ Ejemplo: El Kit tiene dos componentes. El componente 1 tiene 30 unidades en stoc
 
 Los componentes del Kit pueden estar en distintos stocks, siempre que se envíen desde el mismo muelle. Si no salen por el mismo muelle, todo el Kit deja de estar disponible. 
 
-<div class="alert alert-info">
-<p>Este escenario no ocurre con Kit Look, porque el Kit Look puede venderse con los componentes que quedan en stock, sin necesidad de tener todos los componentes del Kit con stock.</p>
-</div>
+>ℹ️ Este escenario no ocurre con Kit Look, porque el Kit Look puede venderse con los componentes que quedan en stock, sin necesidad de tener todos los componentes del Kit con stock.
 
 ## Precio
 
diff --git a/docs/tutorials/es/license-manager-resources.md b/docs/tutorials/es/license-manager-resources.md
index 8bfebb6bf..920f3a4dc 100644
--- a/docs/tutorials/es/license-manager-resources.md
+++ b/docs/tutorials/es/license-manager-resources.md
@@ -19,10 +19,8 @@ VTEX ofrece varios [roles de usuario predefinidos](https://help.vtex.com/es/tuto
 
 Por lo tanto, la plataforma VTEX ofrece la posibilidad de crear roles de usuario personalizados, lo que permite elegir con precisión a qué recursos puede acceder un determinado rol personalizado. A continuación, encontrarás los recursos de VTEX disponibles para cada producto.
 
-<div class="alert alert-danger">
-  <p>El uso sin restricciones de los recursos aumenta el riesgo de ataques a las tiendas por la filtración de credenciales de acceso a los recursos críticos.
-Si tienes alguna duda sobre la descripción de un recurso específico, no dudes en ponerse en contacto con nosotros.</p>
-</div>
+>❗ El uso sin restricciones de los recursos aumenta el riesgo de ataques a las tiendas por la filtración de credenciales de acceso a los recursos críticos.
+> Si tienes alguna duda sobre la descripción de un recurso específico, no dudes en ponerse en contacto con nosotros.
 
 <iframe src="https://help.vtex.com/tables/resources/es" title="Recursos del License Manager" frameBorder="0" width="100%" height="850"></iframe>
 
diff --git a/docs/tutorials/es/limit-purchases-to-a-payment-method-through-checkout-customization.md b/docs/tutorials/es/limit-purchases-to-a-payment-method-through-checkout-customization.md
index 2b30f24ba..7a14f32c6 100644
--- a/docs/tutorials/es/limit-purchases-to-a-payment-method-through-checkout-customization.md
+++ b/docs/tutorials/es/limit-purchases-to-a-payment-method-through-checkout-customization.md
@@ -19,4 +19,4 @@ Recomendamos limite compras a un medio de pago solamente [por política comercia
 
 Otra manera, tal vez más sencilla, es customizar el Checkout, de forma que el CSS omita los medios de pago cuando haya la utm. 
 
-<div class="alert alert-danger">Sin embargo, vale recordar que VTEX no recomienda customizaciones en el Checkout, una vez que el SmartCheckout fue hecho para maximizar la eficiencia en el flujo de cierre de compra.</div>
+>❗ Sin embargo, vale recordar que VTEX no recomienda customizaciones en el Checkout, una vez que el SmartCheckout fue hecho para maximizar la eficiencia en el flujo de cierre de compra.
diff --git a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-sales-policy.md b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-sales-policy.md
index 1005035be..b8c8a9a65 100644
--- a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-sales-policy.md
+++ b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-sales-policy.md
@@ -19,21 +19,16 @@ La limitación en el acceso a una tienda puede ser implementado por diversas raz
 
 Este escenario se puede cumplir mediante el uso de Master Data v1 y la política comercial utilizada en la tienda.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 ## Creación de cluster de clientes
 
diff --git a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
index f8998892d..a85ce6ca4 100644
--- a/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
+++ b/docs/tutorials/es/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -19,21 +19,16 @@ La limitación en el acceso a una tienda puede ser implementado por diversas raz
 
 Este escenario se puede cumplir mediante el uso de Master Data v1 y la política comercial utilizada en la tienda.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 ## Crear cluster de clientes
 
diff --git a/docs/tutorials/es/links-suiteshare.md b/docs/tutorials/es/links-suiteshare.md
index 6d0f5d4c5..6b78ca526 100644
--- a/docs/tutorials/es/links-suiteshare.md
+++ b/docs/tutorials/es/links-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: links
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/lista-da-vez.md b/docs/tutorials/es/lista-da-vez.md
index 8bc7a566f..7e46d5209 100644
--- a/docs/tutorials/es/lista-da-vez.md
+++ b/docs/tutorials/es/lista-da-vez.md
@@ -15,6 +15,4 @@ legacySlug: lista-da-vez
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>  
+>⚠️ Este contenido sólo está disponible en portugués.  
diff --git a/docs/tutorials/es/magento-suiteshare.md b/docs/tutorials/es/magento-suiteshare.md
index d48866b5a..7473637c8 100644
--- a/docs/tutorials/es/magento-suiteshare.md
+++ b/docs/tutorials/es/magento-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: magento-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/manage-the-sales-comissions-report.md b/docs/tutorials/es/manage-the-sales-comissions-report.md
index 2115d72e8..a657d59b2 100644
--- a/docs/tutorials/es/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/es/manage-the-sales-comissions-report.md
@@ -21,9 +21,7 @@ Esa dinámica se debe al split de pagos, funcionalidad sobre la cual puede apren
 
 En este artículo, explicaremos cómo generar ese informe de comisiones y cómo programar la creación del mismo de forma recurrente de acuerdo con una periodicidad.
 
-<div class="alert alert-warning">
-Antes de proceder con la configuración, verifique con su Customer Success Manager (CSM) si el informe de comisiones se incorporó al Admin de su cuenta.
-</div>  
+>⚠️ Antes de proceder con la configuración, verifique con su Customer Success Manager (CSM) si el informe de comisiones se incorporó al Admin de su cuenta.  
 
 ## Genere un informe de comisiones
 
@@ -45,23 +43,17 @@ Posteriormente:
 8. Complete el campo __Dirección de email__ con el email deseado.
 9. Haga clic en el __botón azul Generar__.
 
-<div class="alert alert-danger">
-Es obligatorio definir una fecha de inicio y una fecha de fin. De lo contrario, el informe de comisiones no será creado.
-</div>
+>❗ Es obligatorio definir una fecha de inicio y una fecha de fin. De lo contrario, el informe de comisiones no será creado.
 
-<div class="alert alert-info">
-Si no desea recibir el informe por email, no haga clic en el cuadro de selección Recibir en la dirección de email. 
-
-Haga clic en el botón "Generar". Esto creará un link en el Admin para descargar el informe.
-</div>  
+>ℹ️ Si no desea recibir el informe por email, no haga clic en el cuadro de selección Recibir en la dirección de email. 
+>
+> Haga clic en el botón "Generar". Esto creará un link en el Admin para descargar el informe.  
 
 De esta forma, el mensaje Su informe se generó con éxito se mostrará en la pantalla para indicar que la operación se realizó correctamente. Además, el documento será enviado a la carpeta Descargas de su computador. 
 
 La creación del informe puede demorarse si el volumen de datos analizados es extenso. En estos casos, puede seguir el proceso en la pantalla como se muestra en la siguiente imagen. 
 
-<div class="alert alert-info">
-Salir de la página no afectará la operación.
-</div>
+>ℹ️ Salir de la página no afectará la operación.
 
 ![Informe de Comisiones](https://images.ctfassets.net/alneenqid6w5/1VW72vERimVjQn1cXy5TRM/0bcdb6a335b163625ebee90c5b2ea467/image.png)
 
@@ -73,13 +65,9 @@ Hay situaciones en las que el marketplace necesita analizar sus comisiones con f
 
 Por esta razón, usted puede crear una programación para que el informe se genere automáticamente en cada periodo de tiempo predeterminado. 
 
-<div class="alert alert-warning">
-En el módulo Comisiones, solo se permite crear una programación por cuenta. 
-</div>
+>⚠️ En el módulo Comisiones, solo se permite crear una programación por cuenta.
 
-<div class="alert alert-info">
-La programación es opcional. Si no se configura no afecta la creación manual de los informes de comisiones de ninguna manera.
-</div>
+>ℹ️ La programación es opcional. Si no se configura no afecta la creación manual de los informes de comisiones de ninguna manera.
 
 Toda vez que está en el módulo Comisiones, haga clic en el botón «Programar» al lado derecho de la pantalla para crear una programación. Este se muestra como un modal, similar al de generación del informe. 
 
diff --git a/docs/tutorials/es/managing-content-per-binding.md b/docs/tutorials/es/managing-content-per-binding.md
index ca87847eb..6b6a0b2c2 100644
--- a/docs/tutorials/es/managing-content-per-binding.md
+++ b/docs/tutorials/es/managing-content-per-binding.md
@@ -27,7 +27,5 @@ A través de la sección Storefront del Admin, VTEX le permite personalizar su t
 
 4. Cree, actualice o elimine contenido para el *binding* y región predefinidos y guarde los cambios. 
 
-<div class="alert alert-warning">
-Mientras edita contenido en un bloque, no puede cambiar los datos de <i>binding</i> ni configuración regional: los campos estarán bloqueados. Si desea cambiarlos, guarde o descarte los cambios y vuelva a la página de inicio de Site Editor.
-</div>
+>⚠️ Mientras edita contenido en un bloque, no puede cambiar los datos de <i>binding</i> ni configuración regional: los campos estarán bloqueados. Si desea cambiarlos, guarde o descarte los cambios y vuelva a la página de inicio de Site Editor.
 
diff --git a/docs/tutorials/es/managing-content-versions.md b/docs/tutorials/es/managing-content-versions.md
index 653c11fba..4bfb51fcb 100644
--- a/docs/tutorials/es/managing-content-versions.md
+++ b/docs/tutorials/es/managing-content-versions.md
@@ -52,14 +52,12 @@ Después de [crear una nueva versión de contenido](#crear-una-nueva-version-de-
 
 3. Elige el contenido que deseas activar y haz clic en `Más opciones` > **Activar.**
 
-<div class="alert alert-warning">
-  <p>Al acceder a <i>Aplicar a</i>, siempre aparecerá la opción <i>esta URL</i> encima de <i>esta plantilla</i>. Esto significa que si el bloque tiene dos versiones, cada una con una opción de aplicación diferente, el usuario solo podrá reactivar la versión aplicada en la plantilla si elimina la versión aplicada por URL.</p>
-
-Después de hacer clic en `más opciones` > **Activar**, habrás publicado el nuevo contenido en tu tienda.
-
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Solo puedes tener un contenido activo a la vez. Si activas un contenido, los demás se desactivarán.
-</div>
+>⚠️ Al acceder a <i>Aplicar a</i>, siempre aparecerá la opción <i>esta URL</i> encima de <i>esta plantilla</i>. Esto significa que si el bloque tiene dos versiones, cada una con una opción de aplicación diferente, el usuario solo podrá reactivar la versión aplicada en la plantilla si elimina la versión aplicada por URL.
+>
+> Después de hacer clic en `más opciones` > **Activar**, habrás publicado el nuevo contenido en tu tienda.
+>
+> <div>
+> Solo puedes tener un contenido activo a la vez. Si activas un contenido, los demás se desactivarán.
 
 ## Programar actualizaciones de contenido
 
diff --git a/docs/tutorials/es/managing-delivery-capacity-beta.md b/docs/tutorials/es/managing-delivery-capacity-beta.md
index 34bc4d446..b2873a574 100644
--- a/docs/tutorials/es/managing-delivery-capacity-beta.md
+++ b/docs/tutorials/es/managing-delivery-capacity-beta.md
@@ -15,14 +15,10 @@ legacySlug: gestionar-capacidad-de-entrega-beta
 subcategory: 
 ---
 
-<div class="alert alert-warning">
-Esta funcionalidad está en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a  <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.
-</div>
+>⚠️ Esta funcionalidad está en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a  [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 Puede hacer un seguimiento de la disponibilidad de las ventanas de entrega y de la cantidad de ítems/pedidos que aún pueden atenderse en cada ventana de entrega a través de la página Capacidad de entrega.
-<div class="alert alert-warning">
- Para gestionar su capacidad de entrega, debe tener transportadoras previamente registradas y la capacidad de entrega previamente configurada. Lea [Registrar política de envío](link) y [Entrega programada](link) para saber cómo realizar este registro y configuración.
-</div>
+>⚠️ Para gestionar su capacidad de entrega, debe tener transportadoras previamente registradas y la capacidad de entrega previamente configurada. Lea [Registrar política de envío](link) y [Entrega programada](link) para saber cómo realizar este registro y configuración.
 
 La gestión de la capacidad de entrega se realiza desde el menú **Inventario y Envío > Capacidad de entrega** en el Admin.
 
@@ -37,7 +33,5 @@ Una vez que haya seleccionado la política de envío y la fecha que se mostrará
 *   **Disponible:** cuántos ítems/pedidos están disponibles para programarse (cantidad de capacidad menos reservado) 
 *   **Status:** puede ser visible o no visible, dependiendo de si la ventana de entrega todavía está disponible. Si todavía está disponible, la ventana tendrá el status visible para sus clientes. 
 
-<div class="alert alert-info">
-Puede hacer clic en EDITAR POLÍTICA DE ENVÍO para ser redirigido a la pantalla de edición de la política de envío seleccionada en el filtro Política de envío.
-</div>
+>ℹ️ Puede hacer clic en EDITAR POLÍTICA DE ENVÍO para ser redirigido a la pantalla de edición de la política de envío seleccionada en el filtro Política de envío.
 
diff --git a/docs/tutorials/es/managing-delivery-capacity.md b/docs/tutorials/es/managing-delivery-capacity.md
index 17462ef0f..0deefa1b7 100644
--- a/docs/tutorials/es/managing-delivery-capacity.md
+++ b/docs/tutorials/es/managing-delivery-capacity.md
@@ -19,9 +19,9 @@ Puede hacer un seguimiento de la disponibilidad de las ventanas de entrega y de
 
 Para gestionar su **Capacidad de entrega**, debe tener [políticas de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) previamente registradas y la [Capacidad de entrega](https://help.vtex.com/es/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi) previamente configurada. 
 
-<div class="alert alert-warning">
-Para que la <a href="https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> y la <a href="https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidad de entrega</a> funcionen correctamente, debes tener en cuenta que:<p><ul><li>La suma de {<a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID de la política de envío} no puede exceder los 60 caracteres.</li><li>No se debe utilizar espacio en el ID de la <a href="https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">política de envío</a>.</li></ul></p>
-</div>
+>⚠️ Para que la [Entrega programada](https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) y la [Capacidad de entrega](https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) funcionen correctamente, debes tener en cuenta que:
+> *La suma de {[account name](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {ID de la política de envío} no puede exceder los 60 caracteres.
+> * No se debe utilizar espacio en el ID de la [política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 En el Admin VTEX, accede a **Envío > Capacidad de entrega**, o escribe **Capacidad de entrega** en la barra de búsqueda en la parte superior de la página. La **Capacidad de entrega** contiene una lista de las ventanas de entrega de su tienda. La lista mostrada se refiere a la política de envío seleccionada en el filtro `Política de envío` y al periodo seleccionado en el filtro `Fecha`.
 
diff --git a/docs/tutorials/es/managing-http-headers.md b/docs/tutorials/es/managing-http-headers.md
index ea264acd4..e3ec3cf2f 100644
--- a/docs/tutorials/es/managing-http-headers.md
+++ b/docs/tutorials/es/managing-http-headers.md
@@ -45,9 +45,7 @@ A continuación se indican los encabezados que admiten modificación:
 
 Puedes configurar un encabezado personalizado, es decir, un valor que no está estandarizado y que es una adaptación a los requisitos o funcionalidades particulares de las necesidades de la tienda.
 
-<div class="alert alert-warning">
-Solo se puede agregar un encabezado personalizado por cuenta.
-</div>
+>⚠️ Solo se puede agregar un encabezado personalizado por cuenta.
 
 Si necesitas configurar un encabezado personalizado, abre un ticket con el soporte VTEX y proporciona las claves y valores. Esta información es tu responsabilidad. Puedes utilizar la documentación de [MDN HTTP headers](https://developer.mozilla.org/es/docs/Web/HTTP/Headers) como guía.
 
diff --git a/docs/tutorials/es/managing-loading-docks.md b/docs/tutorials/es/managing-loading-docks.md
index 3b7773306..963790ab3 100644
--- a/docs/tutorials/es/managing-loading-docks.md
+++ b/docs/tutorials/es/managing-loading-docks.md
@@ -18,8 +18,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 El muelle es una de las etapas logísticas de su tienda. Es un punto intermedio entre el almacén y la transportadora, que funciona como área de salida de productos. Los muelles reciben ítems procedentes de almacenes o centros de distribución y los entregan a las transportadoras para que éstas realicen la entrega al destinatario final. 
 
-<div class="alert alert-info">
-Para saber más sobre lo que es un muelle en VTEX, consulte el artículo <a href="https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj">Muelles</a>.</div>
+>ℹ️ Para saber más sobre lo que es un muelle en VTEX, consulte el artículo [Muelles](https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj).
 
 Este artículo contiene la información necesaria para:
 
@@ -30,18 +29,19 @@ Este artículo contiene la información necesaria para:
 
 Es importante saber que para configurar un muelle correctamente hay que: crear el muelle, rellenar los campos de registro (que determinan los horarios de funcionamiento, la prioridad), y también asociar el muelle con la [política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE), el [almacén](https://docs.google.com/document/u/0/d/1Nx2HYf58xSJLB3V_voySEW80sxkzzhR8dNrS6mytytM/edit) y la [política de envío](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140?&utm_source=autocomplete). 
 
-<div class="alert alert-warning">
-El orden de registro sugerido en la plataforma VTEX para el funcionamiento previsto del sistema logístico es:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
-</a></li>
-  <li><a href="https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">Muelle;</a></li>
-<li>Almacén.</li>
- </ol>
-</body>
-</div>
+>⚠️ El orden de registro sugerido en la plataforma VTEX para el funcionamiento previsto del sistema logístico es:
+> <body>
+>
+> [Política Comercial;](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
+> </a>
+>
+> 3. [Muelle;](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+>
+> Almacén.
+>
+> </body>
 
 ## Registrar
 
diff --git a/docs/tutorials/es/managing-page-and-template-content.md b/docs/tutorials/es/managing-page-and-template-content.md
index b396db9bd..1d7cc1c7b 100644
--- a/docs/tutorials/es/managing-page-and-template-content.md
+++ b/docs/tutorials/es/managing-page-and-template-content.md
@@ -17,18 +17,14 @@ subcategory: 9Arh3cJIOYlfSD1MUC2h3
 
 El Site Editor refleje de forma nativa la aplicación Store Theme, lo que le permite sobrescribir las configuraciones predefinidas para los bloques y crear nuevo contenido para las páginas y *templates* (plantillas) de la tienda.
 
-<div class="alert alert-info">
-Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una página específica, solo puede sobrescribir las configuraciones de bloques existentes de la aplicación Store Theme.  
-</div>
+>ℹ️ Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una página específica, solo puede sobrescribir las configuraciones de bloques existentes de la aplicación Store Theme.
 
 Utilice la autonomía que tiene sobre el código y cree el escenario de *storefront* deseado que se adapte a las necesidades de su negocio aprovechando la facilidad de la interfaz intuitiva.
 
 1. En el Admin VTEX, acceda a **Storefront > Site Editor**.
 2. Utilice el campo URL en la parte superior para navegar a la página que muestra el bloque cuyo contenido desea sobrescribir. 
 
-<div class="alert alert-info">
-Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una página específica, solo puede sobrescribir las configuraciones de bloques existentes de la aplicación Store Theme.  
-</div>
+>ℹ️ Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una página específica, solo puede sobrescribir las configuraciones de bloques existentes de la aplicación Store Theme.
 
 ## Crear contenido
 
@@ -38,21 +34,15 @@ Site Editor no le permite agregar un nuevo bloque a un <i>template</i> o a una p
 
 2. Haga clic en `Versiones` en la esquina superior derecha. 
 
-<div class="alert alert-info">
-El contenido que ve cuando hace clic en un bloque es el que está activo en ese momento. Para más información sobre <b>Versiones</b>, acceda <a href="https://help.vtex.com/es/tutorial/managing-content-versions--4loXo98CZncY0NnjKrScbG">Gestión de versiones de contenido</a> y <a href="https://help.vtex.com/es/tutorial/scheduling-content-updates--5L93gED3wgSRoWpFJlJ2ns">Programar actualizaciones de contenido</a>
-</div>
+>ℹ️ El contenido que ve cuando hace clic en un bloque es el que está activo en ese momento. Para más información sobre **Versiones**, acceda [Gestión de versiones de contenido](https://help.vtex.com/es/tutorial/managing-content-versions--4loXo98CZncY0NnjKrScbG) y [Programar actualizaciones de contenido](https://help.vtex.com/es/tutorial/scheduling-content-updates--5L93gED3wgSRoWpFJlJ2ns)
 
 3. Haga clic en el botón `Nuevo contenido`. 
 4. Realice los cambios deseados de acuerdo con las configuraciones disponibles para el bloque. 
 5. Define si el contenido debe activarse una vez guardado haciendo clic en la casilla de verificación `Activar ahora`. Es posible definir una fecha de inicio y una fecha final para el contenido si lo desea. Para definir las fechas, active los botones respectivos y elija la fecha adecuada en el calendario.
 
-  <div class="alert alert-warning">
-Después de que se marca la casilla esta URL, el contenido solo estará visible en la URL específica en la que guardó sus cambios. Por lo tanto, tenga cuidado con los parámetros y otros componentes de URL que puedan afectar la visualización del contenido: cuanto más específica sea su URL, más restringido estará el nuevo contenido.   
-</div>
+  >⚠️ Después de que se marca la casilla esta URL, el contenido solo estará visible en la URL específica en la que guardó sus cambios. Por lo tanto, tenga cuidado con los parámetros y otros componentes de URL que puedan afectar la visualización del contenido: cuanto más específica sea su URL, más restringido estará el nuevo contenido.
 
-  <div class="alert alert-info">
-Site Editor aplica la configuración de contenido según la jerarquía de parámetros. Puede reproducir contenido de forma nativa para todas las páginas al crear el contenido en el mismo parámetro primario. Considere una URL de categoría determinada, por ejemplo. Al crear contenido en ella, también se actualizarán las URL de todas las páginas de productos cuyo parámetro primario sea la categoría.  
-</div>
+  >ℹ️ Site Editor aplica la configuración de contenido según la jerarquía de parámetros. Puede reproducir contenido de forma nativa para todas las páginas al crear el contenido en el mismo parámetro primario. Considere una URL de categoría determinada, por ejemplo. Al crear contenido en ella, también se actualizarán las URL de todas las páginas de productos cuyo parámetro primario sea la categoría.
 
 6. Aún en la sección `Visibilidad`, indique si el contenido solo se creará en la URL a la que navegó inicialmente o en el *template* completo, incluida la URL en la que se encuentra y todas las demás. 
 7. Guarde los cambios.
@@ -66,9 +56,7 @@ Site Editor aplica la configuración de contenido según la jerarquía de parám
 2. El contenido disponible corresponde al que está activo ahora. Modifique los campos con los nuevos valores o haga clic en `Versiones` para cambiar la configuración de otro contenido. 
 3. Guarde los cambios.
 
-<div class="alert alert-warning">
-No puede actualizar la visibilidad del contenido que se derive del código fuente (de la aplicación Store Theme) en Site Editor. Independientemente de sus acciones, siempre se muestran por <i>template</i> y no por URL. Sin embargo, para contenido creado manualmente en Site Editor sí puede cambiar la visibilidad a URL o <i>template</i>, según sus necesidades. 
-</div>
+>⚠️ No puede actualizar la visibilidad del contenido que se derive del código fuente (de la aplicación Store Theme) en Site Editor. Independientemente de sus acciones, siempre se muestran por <i>template</i> y no por URL. Sin embargo, para contenido creado manualmente en Site Editor sí puede cambiar la visibilidad a URL o <i>template</i>, según sus necesidades.
 
 ## Eliminar y restablecer contenido
 
@@ -80,9 +68,7 @@ No puede actualizar la visibilidad del contenido que se derive del código fuent
 3. Haga clic en el menú del contenido deseado (tres puntos verticales). 
 4. Haga clic en `Eliminar` o `Restaurar` y confirme su acción.
 
-<div class="alert alert-warning">
-Las acciones <code>Eliminar</code> y <code>Restaurar</code> dependen del tipo de contenido. El contenido nativo, es decir, el contenido creado en el código fuente, no se puede eliminar a tráves del Admin, solo restaurar (si realizó alguna actualización). Solo puede eliminar contenido que haya creado manualmente a través del Site Editor.
-</div>
+>⚠️ Las acciones `Eliminar` y `Restaurar` dependen del tipo de contenido. El contenido nativo, es decir, el contenido creado en el código fuente, no se puede eliminar a tráves del Admin, solo restaurar (si realizó alguna actualización). Solo puede eliminar contenido que haya creado manualmente a través del Site Editor.
 
 ## Configurar contenido activo e inactivo
 
@@ -94,6 +80,4 @@ Tenga en cuenta que al hacer clic en el menú del contenido (tres puntos vertica
 
 La manera correcta de definir qué contenido debe estar activo e inactivo es eliminar o restaurar el contenido activo y dejar que el primer contenido de la fila inactiva se active. 
 
-<div class="alert alert-info">
-La fila de contenido inactivo comienza del contenido más reciente hasta el más antiguo. Tenga en cuenta que el contenido creado a través de Site Editor siempre prevalece sobre lo que se definió en el código fuente.
-</div>
+>ℹ️ La fila de contenido inactivo comienza del contenido más reciente hasta el más antiguo. Tenga en cuenta que el contenido creado a través de Site Editor siempre prevalece sobre lo que se definió en el código fuente.
diff --git a/docs/tutorials/es/managing-pages.md b/docs/tutorials/es/managing-pages.md
index 5f4424668..e31b31a22 100644
--- a/docs/tutorials/es/managing-pages.md
+++ b/docs/tutorials/es/managing-pages.md
@@ -34,9 +34,7 @@ En **Headless CMS**, puedes gestionar todas las rutas de URL y los modelos de p
 Para crear y gestionar una página, sigue estos pasos:
 
 1. En el Admin VTEX, accede a **Headless CMS**.
-<div class="alert alert-warning">
-  Asegúrate de estar en el proyecto correcto. De lo contrario, ve al menú <b>Proyecto</b> en la esquina superior izquierda, selecciona el nombre del proyecto en el que deseas crear la página y continúa en el paso 2.
-</div>
+>⚠️ Asegúrate de estar en el proyecto correcto. De lo contrario, ve al menú **Proyecto** en la esquina superior izquierda, selecciona el nombre del proyecto en el que deseas crear la página y continúa en el paso 2.
 2. Haz clic en `Crear documento` y selecciona el tipo de página deseado.
 3. En `Untitled`, nombra la página.
 4. Haz clic en `Secciones` y selecciona la sección deseada.
diff --git a/docs/tutorials/es/managing-projects.md b/docs/tutorials/es/managing-projects.md
index ff382283f..931adb7c3 100644
--- a/docs/tutorials/es/managing-projects.md
+++ b/docs/tutorials/es/managing-projects.md
@@ -23,9 +23,7 @@ Cada proyecto cuenta con sus propios ajustes, contenido y marca, pudiendo person
 
 En esta guía aprenderás a gestionar cada proyecto de frontend de tu tienda.
 
-<div class="alert alert-warning">
-  <a href="https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview"> FastStore WebOps usuarios</a>:Los cambios realizados a través del Headless CMS en el VTEX Admin, como la creación de nuevos tipos de contenido (content types), la adición de secciones o la actualización de campos, pueden no aparecer automáticamente en la tienda una vez que los publiques. Este es un problema conocido, y debes contactar a tu equipo de desarrollo para implementar la solución necesaria. Para obtener instrucciones detalladas, consulta el artículo sobre el problema conocido <a href="https://help.vtex.com/es/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW">La aplicación Webops no está totalmente integrada con Headless CMS</a>.
-</div>
+>⚠️ [ FastStore WebOps usuarios](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview):Los cambios realizados a través del Headless CMS en el VTEX Admin, como la creación de nuevos tipos de contenido (content types), la adición de secciones o la actualización de campos, pueden no aparecer automáticamente en la tienda una vez que los publiques. Este es un problema conocido, y debes contactar a tu equipo de desarrollo para implementar la solución necesaria. Para obtener instrucciones detalladas, consulta el artículo sobre el problema conocido [La aplicación Webops no está totalmente integrada con Headless CMS](https://help.vtex.com/es/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW).
 
 ## Antes de empezar
 Para gestionar el Headless CMS, asegúrese de que los [recursos](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar`, `Settings*`, and `CMS GraphQL API` estén asociados con su [rol de usuario](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). De lo contrario, [cree un rol de usuario](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-rol) y agregue estos recursos o añádalos a un rol de usuario existente.
diff --git a/docs/tutorials/es/managing-redirects-per-binding.md b/docs/tutorials/es/managing-redirects-per-binding.md
index 9876c9020..b9fd9e234 100644
--- a/docs/tutorials/es/managing-redirects-per-binding.md
+++ b/docs/tutorials/es/managing-redirects-per-binding.md
@@ -54,17 +54,13 @@ En la pestaña Redirecciones del módulo Páginas:
 
 ![es-remover-redirect](https://images.ctfassets.net/alneenqid6w5/5khhDBT5o6ESJjwlaFClr5/a6d978fecd07eba1007ea1b28d2675b6/remover-redirect.png)
 
-<div class="alert alert-warning">
-Puede ocurrir un error al intentar hacer clic en las redirecciones que tienen cadenas de query. El equipo de producto de VTEX está al tanto de este comportamiento inesperado y está trabajando en la corrección. Si no puede hacer clic en la redirección que desea eliminar, puede utilizar la hoja de cálculo para eliminarla mientras arreglamos el error. 
-</div>
+>⚠️ Puede ocurrir un error al intentar hacer clic en las redirecciones que tienen cadenas de query. El equipo de producto de VTEX está al tanto de este comportamiento inesperado y está trabajando en la corrección. Si no puede hacer clic en la redirección que desea eliminar, puede utilizar la hoja de cálculo para eliminarla mientras arreglamos el error.
 
 ## Importar y exportar redirecciones
 
 Para gestionar las redirecciones de su tienda en masa, puede importar y exportar la plantilla de redirecciones. 
 
-<div class="alert alert-warning">
-Las entradas de la plantilla se crearán o eliminarán obligatoriamente en la lista de las redirecciones de la tienda. No es posible crear <i>y</i> eliminar redirecciones con la misma plantilla. Antes de rellenar y cargar la plantilla al Admin, defina cuál es el objetivo final de esta acción.
-</div>
+>⚠️ Las entradas de la plantilla se crearán o eliminarán obligatoriamente en la lista de las redirecciones de la tienda. No es posible crear <i>y</i> eliminar redirecciones con la misma plantilla. Antes de rellenar y cargar la plantilla al Admin, defina cuál es el objetivo final de esta acción.
 
 En la pestaña Redirecciones del módulo Páginas:
 
@@ -85,9 +81,7 @@ En la pestaña Redirecciones del módulo Páginas:
 
   ![es-redirect-planilha](https://images.ctfassets.net/alneenqid6w5/4jcHxndX1LyV74UdFJgWNV/7efcfc5207e0972a2b31a4be847b7000/planilha-redirect.png)
 
-  <div class="alert alert-warning">
-Al seleccionar la opción <code>Guardar</code>, creará todas las redirecciones enumeradas en la plantilla, mientras que seleccionar la opción <code>Eliminar</code> las eliminará todas de la base de datos de su tienda.
-</div>
+  >⚠️ Al seleccionar la opción `Guardar`, creará todas las redirecciones enumeradas en la plantilla, mientras que seleccionar la opción `Eliminar` las eliminará todas de la base de datos de su tienda.
 
 6. Cargue la plantilla desde sus archivos locales.
 7. Haga clic en el botón `Importar archivo`.
diff --git a/docs/tutorials/es/managing-shipping-policies.md b/docs/tutorials/es/managing-shipping-policies.md
index c7a80ee49..a20bf09e0 100644
--- a/docs/tutorials/es/managing-shipping-policies.md
+++ b/docs/tutorials/es/managing-shipping-policies.md
@@ -103,9 +103,7 @@ Para activar o desactivar una política de envío, sigue estos pasos:
 
 Para eliminar una política de envío, sigue estos pasos:
 
-<div class="alert alert-danger">
-La acción de eliminar una política de envío es permanente y no se puede deshacer.
-</div>
+>❗ La acción de eliminar una política de envío es permanente y no se puede deshacer.
 
 1. En el Admin VTEX, accede a **Envío > Estrategia de envío** o ingresa **Estrategia de envío** en la barra de búsqueda en la parte superior de la página.
 2. En la pestaña **Políticas de envío**, en la fila correspondiente al política deseada, haz clic en el ícono de menú <i class="fas fa-ellipsis-v"></i>. Puedes [buscar](#buscar-politicas-de-envio) o [filtrar](#filtrar-politicas-de-envio) políticas.
diff --git a/docs/tutorials/es/managing-shipping-rates.md b/docs/tutorials/es/managing-shipping-rates.md
index 105b6f01f..7051345be 100644
--- a/docs/tutorials/es/managing-shipping-rates.md
+++ b/docs/tutorials/es/managing-shipping-rates.md
@@ -22,9 +22,7 @@ Las [tarifas de envío](https://help.vtex.com/es/tutorial/tarifas-de-envio--1Bal
 * [Editar](#editar) las tarifas de envío;
 * [Eliminar](#eliminar) las tarifas de envío.
 
-<div class="alert alert-info">
-Cuando tenga que actualizar o registrar varios precios de envío, recomendamos utilizar la Plantilla de envío (flete) en vez del módulo Tarifas de envío. Si desea comprobar cómo se mostrarán las tarifas de envío registradas al cliente final, utilice el módulo <b><a href="https://help.vtex.com/es/tutorial/simulacao-de-frete--tutorials_144">Simulador de envío</a></b>.
-</div>
+>ℹ️ Cuando tenga que actualizar o registrar varios precios de envío, recomendamos utilizar la Plantilla de envío (flete) en vez del módulo Tarifas de envío. Si desea comprobar cómo se mostrarán las tarifas de envío registradas al cliente final, utilice el módulo **[Simulador de envío](https://help.vtex.com/es/tutorial/simulacao-de-frete--tutorials_144)**.
 
 ## Registrar
 
diff --git a/docs/tutorials/es/managing-singleton-content-types.md b/docs/tutorials/es/managing-singleton-content-types.md
index bbe45e103..f5a4fe2b8 100644
--- a/docs/tutorials/es/managing-singleton-content-types.md
+++ b/docs/tutorials/es/managing-singleton-content-types.md
@@ -20,18 +20,14 @@ El content type de tipo Singleton permite la creación y gestión de una única
 Su uso evita conflictos e incoherencias que pueden ocurrir cuando se crean varias páginas del mismo content type. Por ejemplo, puedes utilizar Singleton para la página de inicio (Home) de tu tienda, asegurándote de que solo haya una página de inicio y todas las actualizaciones y solicitudes realizadas en ella siempre devuelvan el mismo resultado.
 ![singleton-es](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7e816ec8a05d8731dfaee66ca0258641/singleton-es.gif)
 
-<div class="alert alert-warning">
-  Para crear un content type Singleton, verifica con tu equipo de desarrolladores que la propiedad <i>isSingleton</i> ya esté implementada o solicita que sigan las instrucciones en <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> para agregarla al content type deseado.
-</div>
+>⚠️ Para crear un content type Singleton, verifica con tu equipo de desarrolladores que la propiedad <i>isSingleton</i> ya esté implementada o solicita que sigan las instrucciones en [Using isSingleton in a content type](https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type) para agregarla al content type deseado.
 
 ## Crear el Singleton
 1. Accede a **Admin > Storefront > Headless CMS**.
 2. Selecciona `CREAR NUEVO` y elige el nombre del content type singleton, por ejemplo **Home**.
 3. Edita la página y agrega nuevas secciones según tu preferencia.
 
-<div class="alert alert-warning">
-Solamente se puede crear el Singleton una vez. Si creaste la página Singleton, esta ya no aparecerá en la lista de content types.
-</div>
+>⚠️ Solamente se puede crear el Singleton una vez. Si creaste la página Singleton, esta ya no aparecerá en la lista de content types.
 
 Cuando hayas terminado de editar la página, puedes publicar el contenido seleccionando `Publicar` o guardar la página como borrador.
 
@@ -48,9 +44,7 @@ Para editar o eliminar contenido, consulta las secciones a continuación:
 2. Haz clic en el proyecto en que se creó el Singleton.
 3. Haz clic en `Despublicar` > `Despublicar ahora`.
 
-<div class="alert alert-warning">
-Antes de despublicar, asegúrate de que no haya ningún borrador o no podrás continuar. Si hay alguno, puedes eliminarlo o programarlo para publicación.
-</div>
+>⚠️ Antes de despublicar, asegúrate de que no haya ningún borrador o no podrás continuar. Si hay alguno, puedes eliminarlo o programarlo para publicación.
 
 4. Se mostrará una ventana emergente para que confirmes la acción de despublicar la página.
 5. Haz clic y mantén presionado el botón `DESPUBLICAR` para despublicar el contenido.
@@ -59,6 +53,4 @@ Antes de despublicar, asegúrate de que no haya ningún borrador o no podrás co
 1. En la página del Singleton, selecciona `Más` (menu kebab) y haz clic en `Eliminar`.
 2. Después haz clic en `VOLVER A LAS PÁGINAS`.
 
-<div class="alert alert-warning">
-  Si quieres restaurar la página y su contenido, haz clic en `RESTAURAR`.
-</div>
+>⚠️ Si quieres restaurar la página y su contenido, haz clic en `RESTAURAR`.
diff --git a/docs/tutorials/es/managing-stock-items.md b/docs/tutorials/es/managing-stock-items.md
index 9b7555e8a..ff38765d9 100644
--- a/docs/tutorials/es/managing-stock-items.md
+++ b/docs/tutorials/es/managing-stock-items.md
@@ -22,9 +22,7 @@ Este artículo detalla la información de la página **Gestión del stock**. Apr
 * [Los datos del _stock_ están divididos](#datos-del-stock).
 * [Los filtros de búsqueda están dispuestos para facilitar la búsqueda de SKU específicos](#filtros).
 
-<div class="alert alert-info"> 
-Para acceder al <i>stock</i> utilizando SKU, muelles o almacenes a través de API, utiliza la <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-"> Inventory API</a>.
-</div>
+>ℹ️ Para acceder al <i>stock</i> utilizando SKU, muelles o almacenes a través de API, utiliza la [ Inventory API](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 Otras acciones disponibles en la página **Gestión del stock** son:
 
@@ -50,9 +48,7 @@ En el Admin VTEX, accede a **Catálogo > Stock > Gestión de stock**, o escribe
     * **Stock infinito**: permite registrar unidades infinitas del SKU para que siempre esté disponible en el _checkout_ de tu tienda. Esto elimina la necesidad de actualizar el recuento del SKU.
     * **Lead time (días):** configuración opcional del tiempo de envío al nivel de SKU. Al definir un tiempo para el SKU de un almacén, él se agregará al [cálculo de tiempo total de envío](https://help.vtex.com/es/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) del pedido. Por defecto, el [lead time](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) está definido como zero días y su contaje se realiza en días laborables. Puedes [alterarlo para días naturales](https://help.vtex.com/es/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional) y, si quieres configurar periodos en horas, minutos y segundos, puedes utilizar el endpoint [Update inventory by SKU and warehouse endpoint](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
-<div class="alert alert-danger">
-Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el <a href="url">ID del SKU</a> no debe contener <b>el número cero a la izquierda</b>. Por ejemplo, el sistema no reconoce ID con el formato <code>01</code>, <code>02</code> , <code>021</code>, ya que espera el formato <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el [ID del SKU](url) no debe contener **el número cero a la izquierda**. Por ejemplo, el sistema no reconoce ID con el formato `01`, `02` , `021`, ya que espera el formato `1`, `2`, `21`.
 
 La cantidad total de ítems en la página **Gestión de stock** se actualiza en tiempo real, pero puede haber un retraso de hasta 1 hora para que la información aparezca en el [historial de movimientos](https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2).
 
@@ -68,9 +64,7 @@ En la página **Gestión del stock**, para realizar una búsqueda en la barra, s
 
 *   **Almacén**: selecciona uno o más almacenes deseados para devolver todos los ítems presentes.
 
-<div class="alert alert-danger">
-La lista de <i>stock</i> está limitada a diez mil filas. Esto significa que incluso si un SKU no está disponible en la lista, se puede encontrar o acceder utilizando los filtros. El límite de filas del <i>stock</i> mejora el rendimiento de las consultas. Para acceder a un SKU que no está disponible en la página, busca o utiliza los filtros para obtener una búsqueda más precisa.
-</div>
+>❗ La lista de <i>stock</i> está limitada a diez mil filas. Esto significa que incluso si un SKU no está disponible en la lista, se puede encontrar o acceder utilizando los filtros. El límite de filas del <i>stock</i> mejora el rendimiento de las consultas. Para acceder a un SKU que no está disponible en la página, busca o utiliza los filtros para obtener una búsqueda más precisa.
 
 ## Artículos relacionados
 
diff --git a/docs/tutorials/es/managing-url-redirects.md b/docs/tutorials/es/managing-url-redirects.md
index 95c198670..2228d2a5d 100644
--- a/docs/tutorials/es/managing-url-redirects.md
+++ b/docs/tutorials/es/managing-url-redirects.md
@@ -46,7 +46,5 @@ Algunos editores, como Google Sheets, exportan los archivos CSV con la coma (<co
 
 Si deseas exportar tus redirecciones, haz clic en <i class="fas fa-download"></i> `Exportar` y se descargarán a tu computadora.
 
-<div class="alert alert-info">
-No se puede crear redirecciones con rutas predefinidas como “home” "/", "login", "account", etc. Recomendamos la creación manual según las instrucciones descritas anteriormente.
-</div>
+>ℹ️ No se puede crear redirecciones con rutas predefinidas como “home” "/", "login", "account", etc. Recomendamos la creación manual según las instrucciones descritas anteriormente.
 
diff --git a/docs/tutorials/es/managing-users.md b/docs/tutorials/es/managing-users.md
index 7475de4a1..7930262c6 100644
--- a/docs/tutorials/es/managing-users.md
+++ b/docs/tutorials/es/managing-users.md
@@ -21,9 +21,7 @@ En esta sección, se mostrará la lista de usuarios con sus respectivos __Nombre
 
 ![Lista Usuários User Management ES](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/e5e96de76d8d66202887bd3339e0f01d/Lista_Usu__rios_User_Management_ES.png)
 
-<div class="alert alert-warning">
-Cualquier usuario que desee gestionar usuarios o claves de aplicación debe tener un perfil que contenga el <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <b>Save User</b>. Puedes utilizar, por ejemplo, el perfil predeterminado <a href="https://help.vtex.com/es/tutorial/roles-de-usuario-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>.
-</div>
+>⚠️ Cualquier usuario que desee gestionar usuarios o claves de aplicación debe tener un perfil que contenga el [recurso](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) **Save User**. Puedes utilizar, por ejemplo, el perfil predeterminado [User Administrator - RESTRICTED](https://help.vtex.com/es/tutorial/roles-de-usuario-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted).
 
 ## Creando un nuevo usuario
 
diff --git a/docs/tutorials/es/managing-warehouses.md b/docs/tutorials/es/managing-warehouses.md
index 9e5bb49fc..f4eadc80f 100644
--- a/docs/tutorials/es/managing-warehouses.md
+++ b/docs/tutorials/es/managing-warehouses.md
@@ -17,9 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 El almacén es el espacio de almacenamiento físico del ecommerce. En la plataforma VTEX, puede añadir ítems a los almacenes registrados en su tienda. De este modo, puede controlar los movimientos, la disponibilidad y gestionar el envío de ítems mediante los [muelles](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) y las [políticas de envío](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). 
 
-<div class="alert alert-info">
-Para comprender mejor cómo la plataforma VTEX interpreta y define el funcionamiento de los almacenes, consulte lo artículo <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Almacén</a>.
- </div>
+>ℹ️ Para comprender mejor cómo la plataforma VTEX interpreta y define el funcionamiento de los almacenes, consulte lo artículo [Almacén](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb).
 
 Además, es posible registrar el almacén, los muelles por los que saldrán los productos, el tiempo que tardan los ítems en ser transportados desde el almacén hasta el muelle y el importe cobrado por este transporte.
 
@@ -30,18 +28,19 @@ Este artículo contiene la información necesaria para:
 * [Editar un almacén existente](https://help.vtex.com/es/tutorial/gestionar-almacenes--tutorials_137#editar-almacen).
 * [Eliminar un almacén](https://help.vtex.com/es/tutorial/gestionar-almacenes--tutorials_137#eliminar-almacen).
 
-<div class="alert alert-warning">
-Como el almacén forma parte del sistema logístico de su tienda, le sugerimos que registre los módulos relacionados con la operación logística en el siguiente orden:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
-</a></li>
-  <li><a href="https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">Muelle;</a></li>
-<li>Almacén.</li>
- </ol>
-</body>
-</div>
+>⚠️ Como el almacén forma parte del sistema logístico de su tienda, le sugerimos que registre los módulos relacionados con la operación logística en el siguiente orden:
+> <body>
+>
+> [Política Comercial;](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
+> </a>
+>
+> 3. [Muelle;](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+>
+> Almacén.
+>
+> </body>
 
 ## Registrar almacén
 
@@ -83,6 +82,4 @@ Como el almacén forma parte del sistema logístico de su tienda, le sugerimos q
 3. En la tarjeta del almacén que desea eliminar, haga clic en <i class="fas fa-ellipsis-v"></i>
 4. Seleccione la opción `Eliminar`.
 
-<div class="alert alert-warning">
-Para añadir ítems al almacén, primero debe registrarlos en el catálogo. Después de registrar los ítems a través del <a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catálogo</a> y tener un almacén registrado, debe asociar los ítems a su respectivo almacén en la página <a href="https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139">Gestión del stock</a>.
-</div>
+>⚠️ Para añadir ítems al almacén, primero debe registrarlos en el catálogo. Después de registrar los ítems a través del [catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) y tener un almacén registrado, debe asociar los ítems a su respectivo almacén en la página [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
diff --git a/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md b/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md
index d6efbd0b8..8bf7a6f6b 100644
--- a/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md
+++ b/docs/tutorials/es/manual-of-classes-and-methods-used-on-webservice.md
@@ -19,7 +19,9 @@ La interfaz de Web Service permite que el responsable de la tienda acceda práct
 
 [Download](https://assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
 
-<div class="alert alert-danger"><p>Atenção: sólo los métodos SOAP correspondientes al <strong>catálogo</strong> son válidos.</p>
-<p><strong>Todos los demás métodos serán descontinuados a partir del 28/02/2017.</strong></p>
-<p>Utilice las API REST equivalentes disponibles en nuestro <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: sólo los métodos SOAP correspondientes al **catálogo** son válidos.
+>
+> **Todos los demás métodos serán descontinuados a partir del 28/02/2017.**
+>
+> Utilice las API REST equivalentes disponibles en nuestro [Developer Docs](//help.vtex.com/developer-docs/).
 
diff --git a/docs/tutorials/es/mapping-categories-and-brands-for-the-marketplace.md b/docs/tutorials/es/mapping-categories-and-brands-for-the-marketplace.md
index 4b3767bda..c97b9772b 100644
--- a/docs/tutorials/es/mapping-categories-and-brands-for-the-marketplace.md
+++ b/docs/tutorials/es/mapping-categories-and-brands-for-the-marketplace.md
@@ -53,9 +53,7 @@ Para rellenar la plantilla:
 4. Guarde el __archivo XLS__ de la plantilla.  
 5. En «Mapeo de categorías», haga clic en el botón __Cambiar mapeo de categorías__ para enviar la plantilla actualizada.  
 
-<div class="alert alert-info">
-Si el programa utilizado para abrir la plantilla utiliza los separadores estándar «;», debe reemplazarlos por «,» antes de enviar el archivo.
-</div>
+>ℹ️ Si el programa utilizado para abrir la plantilla utiliza los separadores estándar «;», debe reemplazarlos por «,» antes de enviar el archivo.
 
 ### Ejemplo
 Este es un ejemplo de la plantilla actual que contiene los siguientes valores en las columnas:
@@ -75,9 +73,7 @@ con las categorías que ya existen en el marketplace. Una vez completado el mape
 | [3] Mujer \|<br>[28] Jeans                     | Jeans / Shorts            |                                    |
 | [3] Mujer \|<br>[28] Jeans                     | Jeans / Bermudas          |                                    |
 
-<div class="alert alert-info">
-Observe que más de una categoría del catálogo del seller coincide con la misma categoría en el marketplace (Mujer / Jeans).  En ese caso, duplique la línea correspondiente en «Marketplace categories» y pegue los valores de la columna «Unmapped categories sent by seller» en cada línea duplicada.
-</div>
+>ℹ️ Observe que más de una categoría del catálogo del seller coincide con la misma categoría en el marketplace (Mujer / Jeans).  En ese caso, duplique la línea correspondiente en «Marketplace categories» y pegue los valores de la columna «Unmapped categories sent by seller» en cada línea duplicada.
 
 ## Mapeo de marcas
 
@@ -98,9 +94,7 @@ Puede descargar el modelo de plantilla actualizado desde el botón Descargar la
 4. Guarde el __archivo XLS__ de la plantilla.  
 5. En «Mapeo de marcas», haga clic en el botón __Cambiar el mapeo de marcas__ para enviar la plantilla actualizada.  
 
-<div class="alert alert-info">
-Si el programa utilizado para abrir la plantilla utiliza los separadores estándar «;», debe reemplazarlos por «,» antes de importar el archivo.
-</div>
+>ℹ️ Si el programa utilizado para abrir la plantilla utiliza los separadores estándar «;», debe reemplazarlos por «,» antes de importar el archivo.
 
 ### Ejemplo
 Este es un ejemplo de la plantilla actual que contiene los siguientes valores en las columnas:
diff --git a/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md b/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
index 237fae886..e8aa04901 100644
--- a/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
+++ b/docs/tutorials/es/mapping-mercado-livre-categories-variations-and-attributes.md
@@ -15,9 +15,7 @@ legacySlug: mapeo-de-categorias-variaciones-y-atributos-de-mercado-libre
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-Si va a enviar sus productos a Mercado Libre por primera vez, le recomendamos que utilice la <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA">nueva documentación de Mapeo de categorías.</a>
-</div>
+>ℹ️ Si va a enviar sus productos a Mercado Libre por primera vez, le recomendamos que utilice la [nueva documentación de Mapeo de categorías.](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA)
 
 Después de realizar la [configuración inicial para la integración con Mercado Libre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/15NZiQstCET8zyQUIa7nhw), es necesario categorizar las variaciones y los atributos de los productos y enviarlos al marketplace. El envío de esta información se realiza mediante la **carga de la plantilla de mapeo**, que hace la correspondencia entre las categorías, variaciones y atributos de su tienda con los estándares adoptados por Mercado Libre.
 
@@ -83,9 +81,9 @@ El nombre de estas debe estar exactamente de acuerdo con los valores aceptados p
 
 Son variaciones adicionales que se pueden crear de acuerdo con su necesidad. Solo se puede tener una variación personalizable por producto. El nombre de la variación y sus valores son de libre elección.  
 
-<div class="alert alert-info">Mercado Libre no permite usar precios diferentes para cada variación de un anuncio, los precios de los SKUs tienen que ser rigurosamente los mismos. Para modificar el precio de su producto, acceda en el Admin a Productos > Precios > Lista de precios.</div>
+>ℹ️ Mercado Libre no permite usar precios diferentes para cada variación de un anuncio, los precios de los SKUs tienen que ser rigurosamente los mismos. Para modificar el precio de su producto, acceda en el Admin a Productos > Precios > Lista de precios.
 
-<div class="alert alert-info">En caso de que el SKU no tenga una especificación (color, por ejemplo), será necesario <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin">registrarla en VTEX</a> antes de completar el proceso de integración. Se recomienda agregar el atributo que falta como una especificación de producto. </div>
+>ℹ️ En caso de que el SKU no tenga una especificación (color, por ejemplo), será necesario [registrarla en VTEX](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin) antes de completar el proceso de integración. Se recomienda agregar el atributo que falta como una especificación de producto.
 
 ## Atributos
 
@@ -97,7 +95,7 @@ Para descubrir las especificaciones de su producto en Mercado Libre, copie la UR
 
 http://portal.vtexcommercestable.com.br/api/meliintegration/category/{CategoryId}/attributes
 
-<div class="alert alert-info">Si está mapeando la categoría “Camisetas” (MLB31447), usted notará que se pueden registrar varios atributos, entre ellos “Género” que solo acepta los valores “Masculino”, “Femenino”, “Niñas”, “Niños”, “Bebés”, “Sin género”. Cualquier valor que sea diferente no será aceptado por Mercado Libre. También tome en cuenta que se pueden registrar atributos con valores que tienen <strong>Texto libre</strong>, es decir, en los que se puede ingresar cualquier valor para los atributos.</div>
+>ℹ️ Si está mapeando la categoría “Camisetas” (MLB31447), usted notará que se pueden registrar varios atributos, entre ellos “Género” que solo acepta los valores “Masculino”, “Femenino”, “Niñas”, “Niños”, “Bebés”, “Sin género”. Cualquier valor que sea diferente no será aceptado por Mercado Libre. También tome en cuenta que se pueden registrar atributos con valores que tienen **Texto libre**, es decir, en los que se puede ingresar cualquier valor para los atributos.
 
 ## Ingresando las variaciones y atributos en la plantilla de mapeo 
 
@@ -180,5 +178,4 @@ Al concluir las etapas para rellenar la plantilla de mapeo, usted debe seguir lo
 
 Después de finalizar la carga, la integración envía a Mercado Libre todos los productos de las categorías utilizadas en la plantilla de forma automática. 
 
-<div class="alert alert-warning">
-Si después de cargar una plantilla usted desea cargar otra, debe saber que la nueva plantilla reemplazará a la antigua. Por eso, recomendamos que la nueva plantilla que cargue contenga los datos antiguos y nuevos. </div>
+>⚠️ Si después de cargar una plantilla usted desea cargar otra, debe saber que la nueva plantilla reemplazará a la antigua. Por eso, recomendamos que la nueva plantilla que cargue contenga los datos antiguos y nuevos.
diff --git a/docs/tutorials/es/marketplace-invited-sellers.md b/docs/tutorials/es/marketplace-invited-sellers.md
index 1ef9726a6..0035c46d8 100644
--- a/docs/tutorials/es/marketplace-invited-sellers.md
+++ b/docs/tutorials/es/marketplace-invited-sellers.md
@@ -47,9 +47,8 @@ La invitación se realiza mediante un enlace enviado al seller por email que con
 
 El seller recibirá por email una invitación para vender en su marketplace. 
 
-<div class="alert alert-info">
-El enlace enviado por email al seller es válido durante 7 días. Después de hacer clic en el enlace, el seller tiene seis horas para completar el formulario de registro. 
-Si no es posible completar el registro dentro de este período, el marketplace tiene que enviar la invitación de nuevo. Para ello, vaya a MARKETPLACE > Invitación de sellers. Busque al seller en la lista y haga clic en <i class="fas fa-paper-plane"></i> «Reenviar invitación». </div>
+>ℹ️ El enlace enviado por email al seller es válido durante 7 días. Después de hacer clic en el enlace, el seller tiene seis horas para completar el formulario de registro. 
+> Si no es posible completar el registro dentro de este período, el marketplace tiene que enviar la invitación de nuevo. Para ello, vaya a MARKETPLACE > Invitación de sellers. Busque al seller en la lista y haga clic en <i class="fas fa-paper-plane"></i> «Reenviar invitación».
 
 ## Conectar seller
 
diff --git a/docs/tutorials/es/marketplace-strategies-at-vtex.md b/docs/tutorials/es/marketplace-strategies-at-vtex.md
index a24c30359..0fe07d9a6 100644
--- a/docs/tutorials/es/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/es/marketplace-strategies-at-vtex.md
@@ -34,9 +34,7 @@ La selección de productos enviados a un marketplace se define al elegir [la pol
 
 La [contratación de políticas comerciales adicionales](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) se realiza a través de la apertura de un ticket en nuestro servicio de soporte, seleccionando la opción __Comercial__ y el tipo de solicitud “Creación de política comercial”. Se cobra una tarifa mensual por cada política comercial adicional, independientemente de si se utiliza para la integración con marketplaces certificados, partners, externos o VTEX.  
 
-<div class="alert alert-info">
-Los pedidos aprobados en los marketplaces están sujetos a las mismas <a href="https://help.vtex.com/es/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">normas contractuales</a> de pedidos realizados a través de otros canales.  
-</div>
+>ℹ️ Los pedidos aprobados en los marketplaces están sujetos a las mismas [normas contractuales](https://help.vtex.com/es/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt) de pedidos realizados a través de otros canales.
 
 A continuación, abordaremos los siguientes escenarios:  
 
@@ -100,10 +98,8 @@ En VTEX, puedes vender en otros canales en las siguientes situaciones:
 - [Integrado con un marketplace partner](#integrado-con-un-marketplace-partner)
 - [Como seller VTEX](#como-seller-vtex)  
 
-<div class="alert alert-info">
-Una tienda VTEX puede actuar simultáneamente como <a href="#vender-en-un-marketplace">seller VTEX</a> y <a href="#actuar-como-marketplace">marketplace VTEX</a>.
-La plataforma VTEX tiene diferentes funcionalidades de fulfillment que se pueden combinar para escenarios como el dropshipping, es decir, cuando el seller recibe y envía el pedido del cliente a un tercero que estará a cargo del fulfillment. La solución logística más adecuada para el seller dependerá de la arquitectura y su modelo de negocio, y puede realizarse a través de la <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integración de Back office (ERP/PIM/WMS)</a>.
-</div>
+>ℹ️ Una tienda VTEX puede actuar simultáneamente como [seller VTEX](#vender-en-un-marketplace) y [marketplace VTEX](#actuar-como-marketplace).
+> La plataforma VTEX tiene diferentes funcionalidades de fulfillment que se pueden combinar para escenarios como el dropshipping, es decir, cuando el seller recibe y envía el pedido del cliente a un tercero que estará a cargo del fulfillment. La solución logística más adecuada para el seller dependerá de la arquitectura y su modelo de negocio, y puede realizarse a través de la [integración de Back office (ERP/PIM/WMS)](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide).
 
 ### Integrado con un marketplace externo
 
@@ -113,9 +109,7 @@ En caso de que tu tienda desee vender en un marketplace que no tiene conexión c
 
 Los marketplaces certificados son aquellos cuya integración ha sido desarrollada por el equipo de desarrolladores de VTEX. Con la política comercial adicional contratada para este tipo de integración, estás exento de la tarifa mensual si hay pedidos asociados a dicha política a través del marketplace certificado. En este caso, solo pagarás la comisión por pedidos (take rate).  
 
-<div class="alert alert-warning">
-Las políticas comerciales adicionales contratadas para la integración con marketplaces certificados que también se utilicen en la integración con otros tipos de marketplaces estarán sujetas al cobro de la tarifa mensual.
-</div>
+>⚠️ Las políticas comerciales adicionales contratadas para la integración con marketplaces certificados que también se utilicen en la integración con otros tipos de marketplaces estarán sujetas al cobro de la tarifa mensual.
 
 Actualmente, la plataforma VTEX cuenta con los siguientes marketplaces certificados:  
 
@@ -168,9 +162,7 @@ Consulta a continuación los marketplaces partners disponibles en el catálogo d
 - Fast Shop  
 - Hubplus  
 
-<div class="alert alert-info">
-Aunque Facebook, Google Shopping, Google Shopping Ads y TikTok no son marketplaces, ofrecen una experiencia similar de envío de productos desde las tiendas VTEX.
-</div>
+>ℹ️ Aunque Facebook, Google Shopping, Google Shopping Ads y TikTok no son marketplaces, ofrecen una experiencia similar de envío de productos desde las tiendas VTEX.
 
 ### Como seller VTEX
 
@@ -182,6 +174,4 @@ La configuración de la [integración entre tiendas VTEX](https://help.vtex.com/
 
 [Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) es una edición de la plataforma VTEX destinada a que los sellers se conecten y vendan sus productos en marketplaces alojados en VTEX. A través de este portal, los sellers acceden a todas las funcionalidades esenciales para la operación del ecommerce en grandes vitrinas, aportando visibilidad y conversión de ventas.  
 
-<div class="alert alert-info">
-En VTEX, es posible actuar como un <a href="https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>, un seller no identificado por el consumidor en la experiencia de compra. Este tipo de seller es el estándar para las <a href="https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a>, por ejemplo, y puede ser estratégico para determinados modelos de negocio. Para más información, consulta el artículo <a href="https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Elegir entre cuenta estándar, cuenta franquicia o Seller Portal</a>.
-</div>
+>ℹ️ En VTEX, es posible actuar como un [seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), un seller no identificado por el consumidor en la experiencia de compra. Este tipo de seller es el estándar para las [cuentas franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), por ejemplo, y puede ser estratégico para determinados modelos de negocio. Para más información, consulta el artículo [Elegir entre cuenta estándar, cuenta franquicia o Seller Portal](https://help.vtex.com/es/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).
diff --git a/docs/tutorials/es/marketplaces-and-integrations.md b/docs/tutorials/es/marketplaces-and-integrations.md
index e510d7093..a32c68028 100644
--- a/docs/tutorials/es/marketplaces-and-integrations.md
+++ b/docs/tutorials/es/marketplaces-and-integrations.md
@@ -24,10 +24,8 @@ Entre los marketplaces disponibles, existen marketplaces VTEX y marketplaces ext
 | **VTEX** | Estos son los perfiles de los clientes VTEX que optaron por abrir su entorno para que otros sellers pongan sus productos a la venta. |
 | **Externo** | Se trata de marketplaces que no son clientes de VTEX pero desarrollaron la integración, siendo esta certificada o partner. |  
 
-<div class="alert alert-info">
-  Importante: <b>Marketplaces e integraciones</b> es una herramienta que promueve el contacto entre posibles partners, pero no es obligatorio hacer uso de ella para convertirse en un marketplace VTEX.  
-Si quieres actuar como marketplace VTEX, lee el artículo <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex">Estrategias de marketplace en VTEX</a>.
-</div>  
+>ℹ️ Importante: **Marketplaces e integraciones** es una herramienta que promueve el contacto entre posibles partners, pero no es obligatorio hacer uso de ella para convertirse en un marketplace VTEX.  
+> Si quieres actuar como marketplace VTEX, lee el artículo [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex).  
 
 ## Encontrar marketplaces
 
@@ -82,9 +80,7 @@ En la pantalla aparecerá un mensaje de éxito.
 
 Si el seller necesita establecer un nuevo contacto con el mismo marketplace, repite los pasos anteriores.  
 
-<div class="alert alert-info">
-El potencial partner comercial recibirá un email con la información en el campo Mensaje. Si el interés es mutuo, la persona responsable del seller o del marketplace puede ponerse en contacto contigo y negociar las condiciones del acuerdo entre marketplace y seller.
-</div>
+>ℹ️ El potencial partner comercial recibirá un email con la información en el campo Mensaje. Si el interés es mutuo, la persona responsable del seller o del marketplace puede ponerse en contacto contigo y negociar las condiciones del acuerdo entre marketplace y seller.
 
 ## Editar
 
diff --git a/docs/tutorials/es/master-data-v2.md b/docs/tutorials/es/master-data-v2.md
index 54de0beaf..4d30eb3eb 100644
--- a/docs/tutorials/es/master-data-v2.md
+++ b/docs/tutorials/es/master-data-v2.md
@@ -15,8 +15,7 @@ legacySlug: master-data-v2
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> Esta versión no es compatible con las entidades de datos de la versión anterior. Se puede utilizar esta configuración sólo para nuevas entidades de datos.</div>
+>⚠️ **Atención:** Esta versión no es compatible con las entidades de datos de la versión anterior. Se puede utilizar esta configuración sólo para nuevas entidades de datos.
 
 ## Introducción
 
diff --git a/docs/tutorials/es/master-data.md b/docs/tutorials/es/master-data.md
index f63f8ed3e..90a2029a4 100644
--- a/docs/tutorials/es/master-data.md
+++ b/docs/tutorials/es/master-data.md
@@ -21,9 +21,7 @@ Por defecto, Master Data se usa para almacenar y organizar los datos de los clie
 
 En este artículo, encontrarás más detalles sobre cada versión disponible de Master Data, así como conceptos importantes y cómo utilizarlo.
 
-<div class="alert alert-info">
-Ten en cuenta que, según la funcionalidad y la versión que desees utilizar, se recomienda ponerse en contacto con el equipo de desarrollo de tu operación.
-</div>
+>ℹ️ Ten en cuenta que, según la funcionalidad y la versión que desees utilizar, se recomienda ponerse en contacto con el equipo de desarrollo de tu operación.
 
 ## Versiones disponibles
 
@@ -240,9 +238,7 @@ En la tabla a continuación, obtendrás más información sobre las diferencias
   </tr>
 </table>
 
-<div class="alert alert-danger">
-Las entidades de datos de ambas versiones son independientes, aunque algunas pueden ser análogas. Esto significa que un dato creado en una entidad de la v1 no se puede consultar ni editar usando recursos de la v2 y viceversa.
-</div>
+>❗ Las entidades de datos de ambas versiones son independientes, aunque algunas pueden ser análogas. Esto significa que un dato creado en una entidad de la v1 no se puede consultar ni editar usando recursos de la v2 y viceversa.
 
 ## Componentes básicos
 
diff --git a/docs/tutorials/es/match-offers-mercado-livre.md b/docs/tutorials/es/match-offers-mercado-livre.md
index c1046dca1..632954bb8 100644
--- a/docs/tutorials/es/match-offers-mercado-livre.md
+++ b/docs/tutorials/es/match-offers-mercado-livre.md
@@ -15,9 +15,7 @@ legacySlug: match-de-anuncios-mercado-livre
 subcategory: 
 ---
 
-<div class="alert alert-info">
-Esta funcionalidad está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro equipo de <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">soporte</a>
-</div>  
+>ℹ️ Esta funcionalidad está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro equipo de [soporte](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue)  
 
 Al realizar la [integración con Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), el seller envía al marketplace los anuncios que desea vender en la plataforma. De este modo, Mercado Libre ofrece al seller oportunidades de match con anuncios de tipo **catálogo**, que pueden ocupar un espacio resaltado en el marketplace.
 
diff --git a/docs/tutorials/es/maximum-price-per-item.md b/docs/tutorials/es/maximum-price-per-item.md
index cb3366695..424a35117 100644
--- a/docs/tutorials/es/maximum-price-per-item.md
+++ b/docs/tutorials/es/maximum-price-per-item.md
@@ -21,9 +21,7 @@ Es posible crear hasta __10 promociones__ de este tipo, con un __límite de 100
 
 Por tratarse de una promoción, los precios catastrados como máximos no podrán ser mayores que el precio del producto.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> Para que la promoción Precio máximo por Artículo funcione es <strong>obligatorio elegir un medio de pago</strong>.
-</div>
+>⚠️ **Atención:** Para que la promoción Precio máximo por Artículo funcione es **obligatorio elegir un medio de pago**.
 
 ## Datos generales de la promoción
 
@@ -42,9 +40,7 @@ Por tratarse de una promoción, los precios catastrados como máximos no podrán
 - __Precio:__ En este campo se debe definir el precio máximo por el que se vendrá el producto. Sólo se puede definir el precio máximo de un artículo a la vez. Para añadir productos a la promoción, haga clic en el botón __+__.
 - __Medio de pago__: Seleccione los medios de pago deseados para activar la promoción.
 
-<div class="alert alert-info">
-Es posible importar una lista de SKUs, que debe guardarse en un archivo .xls, con cada ID en una línea diferente, seguido del precio máximo correspondiente. Para ver una plantilla, haga clic en el enlace <strong>Descarga ejemplo de hoja de cálculo</strong>.
-</div>
+>ℹ️ Es posible importar una lista de SKUs, que debe guardarse en un archivo .xls, con cada ID en una línea diferente, seguido del precio máximo correspondiente. Para ver una plantilla, haga clic en el enlace **Descarga ejemplo de hoja de cálculo**.
 
 ## Condiciones para la promoción ser válida
 
diff --git a/docs/tutorials/es/media-overview.md b/docs/tutorials/es/media-overview.md
index d1c52907a..6a6479975 100644
--- a/docs/tutorials/es/media-overview.md
+++ b/docs/tutorials/es/media-overview.md
@@ -17,9 +17,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 
 En la página Multimedia puedes gestionar los archivos multimedia de tu tienda, tales como imágenes y videos. Para las imágenes puedes cargar y organizar archivos de hasta 5 MB en los siguientes formatos: `png`, `jpg`, `gif`, `svg` y `webp`, mientras que para los videos puedes agregar una URL del proveedor de videos hospedado externamente como YouTube o Vimeo.
 
-<div class="alert alert-warning">
-Para cargar, los archivos deben tener una extensión en minúsculas, por ejemplo, <code>store.png</code>, y el límite de tamaño de archivo para cargar en Multimedia es de <b>5 MB</b>.
-</div>
+>⚠️ Para cargar, los archivos deben tener una extensión en minúsculas, por ejemplo, `store.png`, y el límite de tamaño de archivo para cargar en Multimedia es de **5 MB**.
 
 ![Multimedia Visión general](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/4b7fca26bb4f3b1f72d3a6fff9eca887/es-multimedia-overview.png)
 
@@ -39,9 +37,7 @@ Hay tres formas de acceder al módulo Multimedia:
 
 - **Headless CMS**: en el Admin VTEX, accede a **Storefront > Headless CMS** y elige una de las páginas creadas, como una página de producto. De las secciones disponibles, selecciona una en la que puedas agregar una imagen, como por ejemplo, [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero). Haz clic en el componente de imagen Hero y se abrirá un panel de Multimedia.
 
-<div class="alert alert-warning">
-Ten en cuenta que la sección debe utilizar la <a href="https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms">media-gallery</a> para beneficiarse de Multimedia. Para proyectos de <a href="https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore">FastStore</a>, las secciones que utilizan el widget media-gallery son <a href="https://developers.vtex.com/docs/guides/faststore/organisms-navbar">Navbar</a> y <a href="https://developers.vtex.com/docs/guides/faststore/organisms-hero">Hero</a>.
-</div>
+>⚠️ Ten en cuenta que la sección debe utilizar la [media-gallery](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms) para beneficiarse de Multimedia. Para proyectos de [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), las secciones que utilizan el widget media-gallery son [Navbar](https://developers.vtex.com/docs/guides/faststore/organisms-navbar) y [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero).
 
 En la siguiente imagen se muestra una visión general de la interfaz de Multimedia y las acciones disponibles para gestionar tus archivos multimedia:
 
@@ -64,15 +60,11 @@ En Multimedia puedes cargar imágenes en los siguientes formatos: `png`, `jpg`,
 
 1. En la página o panel de **Multimedia**, haz clic en `Agregar nuevo` y luego en `Imagen`.
 
-<div class="alert alert-warning">
-  <p>En el panel de Multimedia de Headless CMS y en Site Editor, puedes arrastrar y soltar imágenes.</p>
-</div>
+>⚠️ En el panel de Multimedia de Headless CMS y en Site Editor, puedes arrastrar y soltar imágenes.
 
 2. Elige en tu dispositivo la imagen que deseas agregar y haz clic en `Abrir`.
 
-<div class="alert alert-warning">
-Recuerda que en Multimedia se admiten los siguientes formatos: <code>png</code>, <code>jpg</code>, <code>gif</code>, <code>svg</code>, y <code>webp</code>, en minúsculas y con un límite de tamaño de archivo de 5 MB.
-</div>
+>⚠️ Recuerda que en Multimedia se admiten los siguientes formatos: `png`, `jpg`, `gif`, `svg`, y `webp`, en minúsculas y con un límite de tamaño de archivo de 5 MB.
 
 3. Una vez cargada la imagen, aparecerá un mensaje de éxito. 
 
@@ -85,9 +77,7 @@ Ahora, puedes realizar otras operaciones haciendo clic en `Más acciones` (tres
 | **Descargar** | Descarga la imagen en tu computadora. |
 | **Eliminar** |	Elimina la imagen del repositorio. |
 
-<div class="alert alert-warning">
-Si eliminas la imagen solo se borrará del repositorio de Multimedia. Si agregaste la imagen a un componente Hero, por ejemplo, seguirá utilizándose en ese componente, pero no podrá utilizarse en otros.
-</div>
+>⚠️ Si eliminas la imagen solo se borrará del repositorio de Multimedia. Si agregaste la imagen a un componente Hero, por ejemplo, seguirá utilizándose en ese componente, pero no podrá utilizarse en otros.
 
 ### Agregar videos
 Además de imágenes, Multimedia te permite almacenar videos que puedes utilizar en tu sitio web para crear un atractivo visual para los usuarios que naveguen por la tienda.
diff --git a/docs/tutorials/es/mercado-libre-size-chart.md b/docs/tutorials/es/mercado-libre-size-chart.md
index 08627acfd..2c3259f07 100644
--- a/docs/tutorials/es/mercado-libre-size-chart.md
+++ b/docs/tutorials/es/mercado-libre-size-chart.md
@@ -109,9 +109,7 @@ La plantilla de la tabla de medidas para ropa de la parte inferior tiene las sig
 | **Person_height_from** | Altura de la persona. Inicio del intervalo de medidas. | Rellena cada fila con la medida mínima de la altura de una persona en centímetros. Ejemplo: 188 cm. |
 | **Person_height_to** | Altura de la persona. Fin del intervalo de medidas. | Rellena cada fila con la medida máxima de la altura de una persona en centímetros. Ejemplo: 193 cm. |
 
-<div class="alert alert-info">
-Es importante reforzar la necesidad de usar espacio entre el número y la medida (cm), separar los números con puntos (.), rellenar todas las columnas y verificar si los campos <b>Género</b> y <b>Tamaño</b> fueron seleccionados correctamente.
-  </div>
+>ℹ️ Es importante reforzar la necesidad de usar espacio entre el número y la medida (cm), separar los números con puntos (.), rellenar todas las columnas y verificar si los campos **Género** y **Tamaño** fueron seleccionados correctamente.
 
 ## Cargar la tabla de medidas
 
@@ -127,6 +125,4 @@ Luego de completar la plantilla de mapeo, debes cargarla. Para hacerlo, accede a
 
 Al terminar, habrás creado tu tabla de medidas personalizada con éxito.  
 
-<div class="alert alert-info">
-Si ocurre un error en la tabla, se indicará el problema en la pantalla de carga. Debes resolver el error y cargar la plantilla nuevamente.
-</div>
+>ℹ️ Si ocurre un error en la tabla, se indicará el problema en la pantalla de carga. Debes resolver el error y cargar la plantilla nuevamente.
diff --git a/docs/tutorials/es/mercado-livre-faq.md b/docs/tutorials/es/mercado-livre-faq.md
index 07f1b9a67..d00e69f26 100644
--- a/docs/tutorials/es/mercado-livre-faq.md
+++ b/docs/tutorials/es/mercado-livre-faq.md
@@ -118,7 +118,7 @@ Por regla de Mercado Libre, no se puede reenviar información de los productos l
 
 Si el producto aún no se vendió, podrás hacer modificaciones. Si la modificación es en el valor de la variación/atributo, el cambio se debe hacer en la [página de mapeo](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA). Si la modificación es en el valor de la especificación del producto, consulta el artículo [Registrar especificaciones de producto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin).
 
-<div class="alert alert-warning">Luego de eliminar un producto, no es posible recuperar la relevancia del anuncio.</div>
+>⚠️ Luego de eliminar un producto, no es posible recuperar la relevancia del anuncio.
 
 ## ¿Por qué mi producto fue categorizado equivocadamente en Mercado Libre?
 
diff --git a/docs/tutorials/es/merchandising-rule-conditions.md b/docs/tutorials/es/merchandising-rule-conditions.md
index 12a4d6adf..bc4a87e6a 100644
--- a/docs/tutorials/es/merchandising-rule-conditions.md
+++ b/docs/tutorials/es/merchandising-rule-conditions.md
@@ -23,9 +23,7 @@ Conoce los criterios y los operadores posibles para cada forma de edición en la
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"><thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nombre</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descripción</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operadores</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tipo de edición</th> </tr></thead><tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Término</span></td> <td rowspan="2" class="t-body pa5">Palabra que el cliente busca y estará relacionada con la regla. Campo para rellenar libremente.</td> <td class="t-body pa5">es</td> <td rowspan="2" class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br>Reglas de personalización</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">contiene</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Busca el ID exacto de algún ítem del catálogo que estará relacionado con la regla. Los ID posibles son: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong> y <strong>EAN</strong>. Campo para rellenar libremente.</td> <td class="t-body pa5">es</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de personalización</td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">categoría</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una categoría registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">departamento</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa un departamento registrado en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">marca</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una marca registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">nombresclusterproductos</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una colección registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promoción</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que valida si existe al menos una promoción vinculada al ítem (sí).</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solamente </td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">nombreseller</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa el nombre de un seller.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategoría</span></td> <td rowspan="2" class="t-body pa5">Valor seleccionable que representa una subcategoría registrada en el catálogo de la tienda.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{especificación}}</span></td> <td rowspan="2" class="t-body pa5">Cualquier especificación activa del Catálogo aparece como un criterio personalizado, con los mismos valores posibles. El nombre del criterio es igual al nombre de la especificación registrada. Por ejemplo, si hay una especificación activa llamada <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>, el criterio mostrado será <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Color</span>.</td> <td class="t-body pa5">es</td> <td class="t-body pa5">Todos los escenarios de edición</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5">solo</td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Reglas de activación<br><strong>Editor visual</strong></td> </tr></tbody></table>
 
-<div class="alert alert-warning">
-  <p>Los criterios <code>departamento</code>, <code>categoría</code> y <code>subcategoría</code> solo aparecen como opciones para componer las Reglas de merchandising si los tres niveles de categorías ya están configurados en el <strong>Catálogo</strong>.</p>
-</div>
+>⚠️ Los criterios `departamento`, `categoría` y `subcategoría` solo aparecen como opciones para componer las Reglas de merchandising si los tres niveles de categorías ya están configurados en el **Catálogo**.
 
 ## Operadores
 
diff --git a/docs/tutorials/es/meta-tags-suiteshare.md b/docs/tutorials/es/meta-tags-suiteshare.md
index 8b1922849..91786e305 100644
--- a/docs/tutorials/es/meta-tags-suiteshare.md
+++ b/docs/tutorials/es/meta-tags-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: meta-tags-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/migrating-ads-in-mercado-livre.md b/docs/tutorials/es/migrating-ads-in-mercado-livre.md
index 71ae3cedf..eda703902 100644
--- a/docs/tutorials/es/migrating-ads-in-mercado-livre.md
+++ b/docs/tutorials/es/migrating-ads-in-mercado-livre.md
@@ -33,9 +33,7 @@ El primer paso para migrar tus anuncios de Mercado Libre es configurar la integr
 
 Durante la etapa [Registro del conector de Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), deberás rellenar el campo `ID de política comercial` con el número 0. De esta manera, los anuncios que se migrarán de la plantilla no se duplicarán en la plataforma de Mercado Libre
 
-<div class="alert alert-danger">
-Si usas el ID de una política comercial ya existente, la integración creará nuevos anuncios en Mercado Libre y tu catálogo se duplicará. La única forma de resolver este problema será desactivando manualmente los anuncios duplicados en el panel de Mercado Libre.
-</div>
+>❗ Si usas el ID de una política comercial ya existente, la integración creará nuevos anuncios en Mercado Libre y tu catálogo se duplicará. La única forma de resolver este problema será desactivando manualmente los anuncios duplicados en el panel de Mercado Libre.
 
 ## 2. Descargar la plantilla de migración 
 
@@ -45,9 +43,7 @@ Primero, descarga la [plantilla de migración](https://assets.ctfassets.net/alne
 
 El producto registrado en VTEX solo se podrá mapear con un anuncio en Mercado Libre. En el caso de los [anuncios Clásicos y Premium](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/2MR2USqcvDGaoAkGNdCfGi), el mismo producto podrá anunciarse en ambos tipos de anuncios, ya que tienen configuraciones separadas.
 
-<div class="alert alert-info">
-La integración entre VTEX y Mercado Libre permite asociar un SKU registrado en VTEX a un único anuncio en Mercado Libre por vez. Por lo tanto, es necesario separar los anuncios Clásicos de los Premium cuando se rellena la plantilla de migración. 
-</div>
+>ℹ️ La integración entre VTEX y Mercado Libre permite asociar un SKU registrado en VTEX a un único anuncio en Mercado Libre por vez. Por lo tanto, es necesario separar los anuncios Clásicos de los Premium cuando se rellena la plantilla de migración.
 
 ## 3. Rellenar la plantilla de migración de los anuncios
 
diff --git a/docs/tutorials/es/migrating-to-the-new-version-of-smart-checkout.md b/docs/tutorials/es/migrating-to-the-new-version-of-smart-checkout.md
index f741c73b6..f50383488 100644
--- a/docs/tutorials/es/migrating-to-the-new-version-of-smart-checkout.md
+++ b/docs/tutorials/es/migrating-to-the-new-version-of-smart-checkout.md
@@ -53,9 +53,7 @@ Usted puede utilizar los archivos `checkout5-custom.js` y `orderplaced2-custo
 4. En el menú __Archivos__, ubicado en el lado derecho de la página, haga clic en los que desea realizar ajustes en el código.
 5. Haga clic en `Guardar`
 
-<div class="alert alert-warning">
-  Personalizar archivos de JavaScript puede ser dañino para su Checkout. VTEX <b>no recomienda</b> personalizaciones y no es responsable de los daños causados por este código.
-</div>
+>⚠️ Personalizar archivos de JavaScript puede ser dañino para su Checkout. VTEX **no recomienda** personalizaciones y no es responsable de los daños causados por este código.
 
 __IMPORTANTE:__ no utilize estos archivos para insertar tags de marketing e integraciones. Si las necesita, utilize Google Tag Manager.
 
diff --git a/docs/tutorials/es/mode-off-faq.md b/docs/tutorials/es/mode-off-faq.md
index 7b153d337..511b72559 100644
--- a/docs/tutorials/es/mode-off-faq.md
+++ b/docs/tutorials/es/mode-off-faq.md
@@ -45,9 +45,7 @@ Por lo tanto, para estos medios de pago, las transacciones no serán reprocesada
 
 Mode-off se activa cuando el partner o la integración presentan una inestabilidad que se identifica a partir de la respuesta de mensajes de error del tipo 500, 408 o timeout superior a 30 segundos en los últimos cinco minutos. Esta regla es válida para todos los medios de pago que mode-off procesa.
 
-<div class="alert alert-warning">
-Cabe recordar que los medios de pago sincrónos <strong>no</strong> se pueden volver a procesar. Sin embargo, entran en el recuento de errores para identificar si un partner es inestable o no.
-</div>
+>⚠️ Cabe recordar que los medios de pago sincrónos **no** se pueden volver a procesar. Sin embargo, entran en el recuento de errores para identificar si un partner es inestable o no.
 
 ## ¿Cuál es la regla para desactivar mode-off?
 
diff --git a/docs/tutorials/es/moskit-suiteshare.md b/docs/tutorials/es/moskit-suiteshare.md
index 8a9f6fdd2..f04c172f4 100644
--- a/docs/tutorials/es/moskit-suiteshare.md
+++ b/docs/tutorials/es/moskit-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: moskit-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/moving-order-to-start-handling-shipping.md b/docs/tutorials/es/moving-order-to-start-handling-shipping.md
index cc16ca4a4..03ca69887 100644
--- a/docs/tutorials/es/moving-order-to-start-handling-shipping.md
+++ b/docs/tutorials/es/moving-order-to-start-handling-shipping.md
@@ -40,6 +40,4 @@ Si la tienda no tiene ERP o algún sistema que integre los pedidos, usted puede
     - <a class="far fa-check-square"></a> Entiendo las consecuencias de esta acción en el flujo del pedido.
 5. Haga clic en `Proceder com el status`.
 
-<div class="alert alert-warning">
-Al iniciar el preparo de um pedido manualmente, el pedido no se puede integrar al ERP posteriormente.
-</div>
+>⚠️ Al iniciar el preparo de um pedido manualmente, el pedido no se puede integrar al ERP posteriormente.
diff --git a/docs/tutorials/es/multilevel-omnichannel-inventory.md b/docs/tutorials/es/multilevel-omnichannel-inventory.md
index 06734f1bb..45d3d78cd 100644
--- a/docs/tutorials/es/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/es/multilevel-omnichannel-inventory.md
@@ -22,9 +22,7 @@ __Multilevel omnichannel inventory__ es la configuración de VTEX que permite qu
 - [Restricciones](#restricciones)  
 - [Cómo configurar](#como-configurar)  
 
-<div class="alert alert-info">
-Para obtener más información sobre la arquitectura de los pedidos de tipo Multilevel Omnichannel Inventory y aprender a realizar la configuración a través de la API REST, consulta nuestro artículo en el <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory">Developer Portal</a>.
-</div>
+>ℹ️ Para obtener más información sobre la arquitectura de los pedidos de tipo Multilevel Omnichannel Inventory y aprender a realizar la configuración a través de la API REST, consulta nuestro artículo en el [Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
 
 ## Arquitectura de cuentas
 
@@ -46,9 +44,7 @@ De este modo, es posible que un _marketplace_ venda los productos de sus _seller
 
 Esto significa que cuando el _seller_ de la cuenta principal configura una integración con un _marketplace_, las cuentas franquicia también se integran automáticamente con él, por lo que no es necesario gestionar cada franquicia individualmente para configurar su integración con el _marketplace_.
 
-<div class="alert alert-info">
-Actualmente, solo se permite un nivel de recursión. En otras palabras, el marketplace puede vender productos de sellers white label integrados con un seller directo.
-</div>
+>ℹ️ Actualmente, solo se permite un nivel de recursión. En otras palabras, el marketplace puede vender productos de sellers white label integrados con un seller directo.
 
 ## Beneficios
 
@@ -87,9 +83,7 @@ Es importante destacar que cuando el _seller directo_ no es responsable de las c
 
 Una vez realizada la configuración, solo los medios de pago del _marketplace_ aparecerán como opción en el _checkout_. Los medios de pago de los _sellers_ directos (nivel 2) y de los _sellers white label_ (nivel 3) no se importan a la arquitectura de las cuentas. Por lo tanto, el _checkout_ solo muestra los medios de pago del _marketplace_, incluso si el afiliado del _seller_ directo está configurado para utilizar sus medios de pago. 
 
-<div class="alert alert-warning">
-  El <a href="https://help.vtex.com/es/tutorial/como-configurar-afiliado--tutorials_187">afiliado</a> de la cuenta franquicia debe tener siempre desmarcada la opción de usar los medios de pago.
-</div>
+>⚠️ El [afiliado](https://help.vtex.com/es/tutorial/como-configurar-afiliado--tutorials_187) de la cuenta franquicia debe tener siempre desmarcada la opción de usar los medios de pago.
 
 ### Cambio de seller
 
@@ -131,9 +125,7 @@ No es posible crear tablas de precios mediante la funcionalidad [Tablas de preci
 
 La configuración de la funcionalidad __Multilevel omnichannel inventory__ debe ser realizada por el _marketplace_ en tu Admin VTEX o a través de la [API Rest](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). Esta configuración puede realizarse tanto para los _sellers_ ya integrados como para los _sellers_ agregados por primera vez.
 
-<div class="alert alert-info">
-Ten en cuenta que la configuración debe realizarse para cada seller directo (nivel 2) al que quieras aplicar la funcionalidad, pero no para cada cuenta de seller white label o cuenta franquicia (nivel 3).
-</div>
+>ℹ️ Ten en cuenta que la configuración debe realizarse para cada seller directo (nivel 2) al que quieras aplicar la funcionalidad, pero no para cada cuenta de seller white label o cuenta franquicia (nivel 3).
 
 ### Sellers ya integrados
 
diff --git a/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md b/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md
index 9a84397aa..ec350e1f0 100644
--- a/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md
+++ b/docs/tutorials/es/my-orders-in-mercado-libre-have-errors.md
@@ -50,12 +50,14 @@ Haz clic en `Realizar mapeo`.
 Haz clic en la categoría que presenta error.
 Realiza nuevamente el mapeo de acuerdo con las categorías y atributos existentes en Mercado Libre.
 
-<div class="alert alert-info">
-Para identificar el atributo indicado en el mensaje de error, consulta el número inicial de los códigos determinados por Mercado Libre. Haz clic en el nombre de tu país para descargar la plantilla de referencia:
-<p><ul>
-<p><a href="https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip">Brasil</a></p>
-<p><a href="https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar">Argentina</a></p> 
-<p><a href="https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar">Colombia</a></p> 
-<p><a href="https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar">México</a></p>
-</ul></p></div>
+>ℹ️ Para identificar el atributo indicado en el mensaje de error, consulta el número inicial de los códigos determinados por Mercado Libre. Haz clic en el nombre de tu país para descargar la plantilla de referencia:
+>
+> <p>[Brasil](https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
+>
+> [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar) 
+>
+> [Colombia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar) 
+>
+> [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+> </p>
 
diff --git a/docs/tutorials/es/my-store-order-was-not-created.md b/docs/tutorials/es/my-store-order-was-not-created.md
index ab62bb0ff..2c6cf41fb 100644
--- a/docs/tutorials/es/my-store-order-was-not-created.md
+++ b/docs/tutorials/es/my-store-order-was-not-created.md
@@ -58,7 +58,5 @@ Puede ocurrir un error debido a la falta de información del producto cuando no
 3. En la pestaña `Editar XML`, en la opción **Mostrar SKU no disponibles,** selecciona la casilla `Mostrar SKU sin stock (agotados) en los resultados`.
 4. Haz clic en `Guardar`.
 
-<div class="alert alert-warning">
-Pueden ocurrir errores al intentar facturar un pedido si hay información XML incorrecta o faltante.
-</div>
+>⚠️ Pueden ocurrir errores al intentar facturar un pedido si hay información XML incorrecta o faltante.
 
diff --git a/docs/tutorials/es/navigation.md b/docs/tutorials/es/navigation.md
index a5ca2b245..6274bcc74 100644
--- a/docs/tutorials/es/navigation.md
+++ b/docs/tutorials/es/navigation.md
@@ -18,9 +18,7 @@ subcategory: oMrzcOMVbBpH0reeMFHFg
 El conjunto de datos de navegación opera con dos tablas principales: `pageviews` y `sessions`. `Pageview` se refiere a cada nueva página a la que accede el usuario mientras navega por la tienda, mientras que `session` se define como el conjunto de todas las pageviews realizadas por un usuario en una única visita.
 Cada `session` permanece activa si no se produce una nueva `pageview` durante un periodo de 30 minutos.
 
-<div class="alert alert-warning">
-El conjunto de datos de navegación no captura todos los tipos de eventos que ocurren durante la navegación. Por ejemplo, no se registran clics específicos, eventos especiales ni interacciones con el minicarrito.
-</div>  
+>⚠️ El conjunto de datos de navegación no captura todos los tipos de eventos que ocurren durante la navegación. Por ejemplo, no se registran clics específicos, eventos especiales ni interacciones con el minicarrito.  
 
 En esta sección puedes consultar la siguiente información:
 
@@ -39,10 +37,8 @@ En esta sección puedes consultar la siguiente información:
 | **Historial** | Los datos se conservan durante dos años, a partir de 2022 para los clientes que ya utilizan la plataforma VTEX. |
 | **Intervalo mínimo de actualización** | Una hora. |
 
-<div class="alert alert-warning">
-Data Pipeline solo proporciona datos de sesiones originadas en las soluciones de <i>storefront</i> de VTEX: CMS Legado, Store Framework y FastStore. VTEX no tiene acceso a sesiones originadas en marketplaces de terceros o storefronts de tiendas propietarias. Además, las personalizaciones realizadas en el <i>frontend</i> de la tienda pueden interferir o incluso desactivar el <i>script,</i> provocando que algunas sesiones no se registren o que la tasa de conversión observada en el dashboard no sea precisa.
-<p>Para minimizar el impacto en el desempeño de la tienda, el <i>script</i> está configurado para ser el último elemento en cargarse en la página. Esto significa que es posible que no se capturen sesiones muy breves.</p>
-  </div>  
+>⚠️ Data Pipeline solo proporciona datos de sesiones originadas en las soluciones de <i>storefront</i> de VTEX: CMS Legado, Store Framework y FastStore. VTEX no tiene acceso a sesiones originadas en marketplaces de terceros o storefronts de tiendas propietarias. Además, las personalizaciones realizadas en el <i>frontend</i> de la tienda pueden interferir o incluso desactivar el <i>script,</i> provocando que algunas sesiones no se registren o que la tasa de conversión observada en el dashboard no sea precisa.
+> Para minimizar el impacto en el desempeño de la tienda, el <i>script</i> está configurado para ser el último elemento en cargarse en la página. Esto significa que es posible que no se capturen sesiones muy breves.  
 
 ## Tabla sessions  
 
diff --git a/docs/tutorials/es/new-google-shopping-api-integration.md b/docs/tutorials/es/new-google-shopping-api-integration.md
index 334139c8d..c5da2503c 100644
--- a/docs/tutorials/es/new-google-shopping-api-integration.md
+++ b/docs/tutorials/es/new-google-shopping-api-integration.md
@@ -81,7 +81,5 @@ Google hace con que los productos enviados expiren automáticamente después de
 #### Tamaño del título
 El límite es de 150 caracteres, pero los anuncios de Google solo muestran 70 caracteres de todos modos ([entienda más aquí](https://support.google.com/merchants/answer/6098378?hl=es)). La integración envía hasta 150 caracteres que se compone de Título del Producto + Título de SKU.
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> La integración por XML no fue discontinuada, pero si la integración es hecha por XML y por el módulo de Integraciones (API) los productos aparecerán duplicados.
-</div>
+>⚠️ **Atención:** La integración por XML no fue discontinuada, pero si la integración es hecha por XML y por el módulo de Integraciones (API) los productos aparecerán duplicados.
 
diff --git a/docs/tutorials/es/new-my-orders-area.md b/docs/tutorials/es/new-my-orders-area.md
index 2484ee8f3..c7067c937 100644
--- a/docs/tutorials/es/new-my-orders-area.md
+++ b/docs/tutorials/es/new-my-orders-area.md
@@ -15,12 +15,14 @@ legacySlug: nueva-seccion-de-mis-pedidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-warning">
-Esta actualización és una <em>major</em> y <strong>no és compatible con las customizaciones de la página actual de Mis Pedidos</strong>. 
-<br />
-<br />
-Dado que la nueva estrutura de páginas es completamente diferente, será necesário volver a modificar las customizaciones para migrar a esta versión. Ver detalles sobre cómo actualizar su customización en <a href="http://help.vtex.com/es/tutorial/customizando-la-seccion-mis-pedidos">Customizando la sección Mis Pedidos</a>.
-</div>
+>⚠️ Esta actualización és una *major* y **no és compatible con las customizaciones de la página actual de Mis Pedidos**. 
+>
+>
+> 
+>
+>
+> 
+> Dado que la nueva estrutura de páginas es completamente diferente, será necesário volver a modificar las customizaciones para migrar a esta versión. Ver detalles sobre cómo actualizar su customización en [Customizando la sección Mis Pedidos](http://help.vtex.com/es/tutorial/customizando-la-seccion-mis-pedidos).
 
 VTEX busca usar estrategias modernas para crear productos que atiendan cada vez mejor al mercado de e-commerce. Por esa razón, comenzamos a usar las librerías de desarrollo React JS en nuestras features más recientes: la nueva página de **Mis Pedidos** es un ejemplo. Ella viene con nuevas features y nuevo diseño, y fue creada de cero usando React.
 
diff --git a/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md b/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
index d95afcb15..21ff68bc2 100644
--- a/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
+++ b/docs/tutorials/es/newsletter-records-with-less-than-vtex-cmc-newsletteroptin-greater-than.md
@@ -15,7 +15,7 @@ legacySlug: registros-del-newsletter-con-control-vtex-cmc-newsletteroptin
 subcategory: 7ogirQ8NClawO2X6xdgCKc
 ---
 
-<div class="alert alert-warning">__IMPORTANTE__: No se recomienda el uso de este control para el manejo de los registros de datos de clientes, teniendo en cuenta que los registros quedan almacenados sólo en el Administrador de __VTEX__, por lo que no es recomendable tener por separado datos de los clientes, por un lado las suscripciones al Newsletter y por el otro los registros del Checkout. Al no hacer parte del módulo __Master Data (MD)__, solo tendrá la funcionalidad de exportar el listado de los registros, búsqueda o filtros. Por otro lado, teniendo los registros del Newsletter en __Master Data (MD)__ usted tendrá los datos de los clientes centralizados, podrá administrar la información por medio de API, configurar triggers para envíos de correo, realizar integraciones con sistemas externos, entre otros.</div>
+>⚠️ __IMPORTANTE__: No se recomienda el uso de este control para el manejo de los registros de datos de clientes, teniendo en cuenta que los registros quedan almacenados sólo en el Administrador de __VTEX__, por lo que no es recomendable tener por separado datos de los clientes, por un lado las suscripciones al Newsletter y por el otro los registros del Checkout. Al no hacer parte del módulo __Master Data (MD)__, solo tendrá la funcionalidad de exportar el listado de los registros, búsqueda o filtros. Por otro lado, teniendo los registros del Newsletter en __Master Data (MD)__ usted tendrá los datos de los clientes centralizados, podrá administrar la información por medio de API, configurar triggers para envíos de correo, realizar integraciones con sistemas externos, entre otros.
  
 Los registros que se generen del formulario se pueden encontrar en la siguiente ruta:
   1. Ingresar al módulo E-Commerce (E-C).
diff --git a/docs/tutorials/es/offer-details.md b/docs/tutorials/es/offer-details.md
index 7545f63cb..00d82ef11 100644
--- a/docs/tutorials/es/offer-details.md
+++ b/docs/tutorials/es/offer-details.md
@@ -15,12 +15,10 @@ legacySlug: detalles-del-anuncio
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class="alert alert-info">
-Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
-Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
-Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
- </div>  
+>ℹ️ Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de **Gestión de anuncios**.
+> Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+> Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del [Developer Portal](https://developers.vtex.com/updates/release-notes) y el [VTEX Help Center](https://help.vtex.com/pt/en/announcements).  
 
 Un anuncio es un SKU cuyo precio y stock fueron configurados por un seller y que fue enviado a diferentes canales de venta. En el módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE), los sellers supervisan el envío de sus anuncios a marketplaces y su sincronización.
 
diff --git a/docs/tutorials/es/offer-management.md b/docs/tutorials/es/offer-management.md
index 89ab911e6..4e3c74328 100644
--- a/docs/tutorials/es/offer-management.md
+++ b/docs/tutorials/es/offer-management.md
@@ -15,12 +15,10 @@ legacySlug: lista-de-anuncios
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class="alert alert-info">
-Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
-Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
-Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
- </div>  
+>ℹ️ Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de **Gestión de anuncios**.
+> Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+> Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del [Developer Portal](https://developers.vtex.com/updates/release-notes) y el [VTEX Help Center](https://help.vtex.com/pt/en/announcements).  
 
 El módulo **Gestión de anuncios** permite a los _sellers_ hacer el seguimiento del envío y la sincronización de los anuncios de las integraciones con los canales de venta. En VTEX, un anuncio es un SKU cuyo precio y stock fueron configurados por un _seller_ y que fue enviado a un canal de ventas.
 
diff --git a/docs/tutorials/es/offer-quality-filters.md b/docs/tutorials/es/offer-quality-filters.md
index ea3a4edf2..969683df5 100644
--- a/docs/tutorials/es/offer-quality-filters.md
+++ b/docs/tutorials/es/offer-quality-filters.md
@@ -59,9 +59,7 @@ Para ver las reglas activas de forma predeterminada, en la página de «Calidad
 -	ID de ref. tiene un máximo de caracteres de 50
 -	EAN tiene un máximo de caracteres de 50
 
-<div class="alert alert-info">
-Se puede configurar VTEX Matcher para que apruebe anuncios automáticamente mediante las llamadas de API REST <a href="https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig">Save Account's Approval Settings</a>. Estos criterios son diferentes de los que se pueden ver en la página Calidad de anuncios y se aplican a la aprobación automática de anuncios de determinados sellers.
-</div>
+>ℹ️ Se puede configurar VTEX Matcher para que apruebe anuncios automáticamente mediante las llamadas de API REST [Save Account's Approval Settings](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig). Estos criterios son diferentes de los que se pueden ver en la página Calidad de anuncios y se aplican a la aprobación automática de anuncios de determinados sellers.
 
 ## Crear grupos de requisitos
 
@@ -83,9 +81,7 @@ Crea grupos de requisitos para definir las reglas aplicadas a sellers, categorí
 
 Puedes crear requisitos obligatorios y/u opcionales. Aprende más sobre las implicaciones de cada requisito en  [Catalogar anuncios con requisitos](#catalogar-anuncios-con-requisitos).
 
-<div class="alert alert-info">
-Ten en cuenta que cada grupo de requisitos solo contiene un valor. Por lo tanto, para agregar más de un valor tienes que crear otro grupo de requisitos. Por ejemplo, si el marketplace desea agregar las palabras «blusas» y «camisas» como requisitos obligatorios en el campo Marca del seller, tiene que crear un grupo de requisitos para «blusas» y otro para «camisas».
-</div>
+>ℹ️ Ten en cuenta que cada grupo de requisitos solo contiene un valor. Por lo tanto, para agregar más de un valor tienes que crear otro grupo de requisitos. Por ejemplo, si el marketplace desea agregar las palabras «blusas» y «camisas» como requisitos obligatorios en el campo Marca del seller, tiene que crear un grupo de requisitos para «blusas» y otro para «camisas».
 
 Para crear un nuevo grupo de requisitos:
 
diff --git a/docs/tutorials/es/offer-status.md b/docs/tutorials/es/offer-status.md
index 458730b32..95382b708 100644
--- a/docs/tutorials/es/offer-status.md
+++ b/docs/tutorials/es/offer-status.md
@@ -108,9 +108,7 @@ Serás redirigido a la página correspondiente para realizar los cambios necesar
 
 Para exportar la lista de anuncios publicados en formato XLSX, haz clic sobre el ícono flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
 
-<div class="alert alert-info">
-El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
-  </div>
+>ℹ️ El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
 
 ## Pestaña Problemas
 
@@ -185,9 +183,7 @@ Serás redirigido a la página correspondiente para realizar los cambios necesar
 
 Para exportar la lista de anuncios con problemas en formato XLSX, haz clic sobre el ícono flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
 
-<div class="alert alert-info">
-El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
-  </div>
+>ℹ️ El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
 
 ## Pestaña A la espera de finalización
 
@@ -242,6 +238,4 @@ Serás redirigido a la página correspondiente para realizar los cambios necesar
 
 Para exportar la lista de anuncios en espera de finalización en formato XLSX, haz clic sobre el ícono flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
 
-<div class="alert alert-info">
-El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
-  </div>
+>ℹ️ El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
diff --git a/docs/tutorials/es/oms-page-structure.md b/docs/tutorials/es/oms-page-structure.md
index e8dfd81ba..b023e2cb5 100644
--- a/docs/tutorials/es/oms-page-structure.md
+++ b/docs/tutorials/es/oms-page-structure.md
@@ -33,9 +33,7 @@ La barra no muestra la posición exacta de las tiendas que están en las 5 prime
 
 Para todos los datos de variaciones de pedidos, y también para los números de evolución en el ranking, el color verde indica un resultado positivo; azul, neutro; y rojo, negativo.
 
-<div class="alert alert-warning">
-Importante: si la comparación de pedidos se realiza en base a 0 pedidos en el pasado, la variación es de 0%.
-</div>
+>⚠️ Importante: si la comparación de pedidos se realiza en base a 0 pedidos en el pasado, la variación es de 0%.
 
 ![barra-status-oms es](https://images.ctfassets.net/alneenqid6w5/6fv6Fd07ra6KMOwS0ecgUm/02d1b532b5fb183d420ced0ecbb6d235/barra_de_status.png)
 
diff --git a/docs/tutorials/es/opening-hours-suiteshare.md b/docs/tutorials/es/opening-hours-suiteshare.md
index c0b2439ec..d606b8eee 100644
--- a/docs/tutorials/es/opening-hours-suiteshare.md
+++ b/docs/tutorials/es/opening-hours-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: horario-de-atencion-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/operational-capacity-beta.md b/docs/tutorials/es/operational-capacity-beta.md
index a3040e98d..ff80a051b 100644
--- a/docs/tutorials/es/operational-capacity-beta.md
+++ b/docs/tutorials/es/operational-capacity-beta.md
@@ -31,9 +31,7 @@ Al acceder a **Envío > Capacidad operativa** en el Admin VTEX, verás una pági
 
 ![operational_capacity_image1_ES](https://images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/defaa51c729689fdd70aa1e00e018d40/operational_capacity_image1_ES.png)
 
-<div class="alert alert-warning">
-Los sellers que aparecen en la interfaz son los sellers de tu operación, configurados previamente por nuestro equipo. Para agregar un nuevo seller, ponte en contacto con <a href="https://help.vtex.com/es/support">nuestro soporte</a>.
-</div>
+>⚠️ Los sellers que aparecen en la interfaz son los sellers de tu operación, configurados previamente por nuestro equipo. Para agregar un nuevo seller, ponte en contacto con [nuestro soporte](https://help.vtex.com/es/support).
 
 El gráfico muestra los siguientes datos:
 
@@ -99,9 +97,7 @@ La capacidad operativa del seller puede medirse por número de pedidos o ítems
     - **Cantidad de ítems:** la capacidad del seller se medirá por número de ítems del pedido.
 5. Haz clic en `Guardar cambios`.
 
-<div class="alert alert-warning">
-La plataforma tiene algunas restricciones con respecto a <a href="https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers de extensa cobertura</a>. La sección <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidad-operativa-de-sellers-de-extensa-cobertura">Capacidad operativa de sellers de extensa cobertura</a> contiene más información.
-</div>
+>⚠️ La plataforma tiene algunas restricciones con respecto a [sellers de extensa cobertura](https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI). La sección [Capacidad operativa de sellers de extensa cobertura](https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidad-operativa-de-sellers-de-extensa-cobertura) contiene más información.
 
 ## Acciones en la página de detalles del seller
 
@@ -119,9 +115,7 @@ En la esquina superior derecha de la página de detalles del seller, hay un bot
 - **Activar:** habilita el botón de alternancia para que el status esté `Activo` y haz clic en `Activar`.
 - **Desactivar:** inhabilita el botón de alternancia para que el status esté `Pausado` y haz clic en `Pausar`.
 
-<div class="alert alert-warning">
-La plataforma tiene algunas restricciones en relación con <a href="https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers de extensa cobertura</a>. La sección <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidad-operativa-de-sellers-de-extensa-cobertura">Capacidad operativa de sellers de extensa cobertura</a> contiene más información.
-</div>
+>⚠️ La plataforma tiene algunas restricciones en relación con [sellers de extensa cobertura](https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI). La sección [Capacidad operativa de sellers de extensa cobertura](https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidad-operativa-de-sellers-de-extensa-cobertura) contiene más información.
 
 ### Monitorear la capacidad utilizada
 
diff --git a/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
index 813cac91f..927436332 100644
--- a/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/es/optimization-of-shipping-options-at-checkout.md
@@ -34,17 +34,13 @@ Checkout v6 de VTEX combina información como el código postal del cliente, la
 - **Más económica**: opción con el menor costo para el cliente.
 - **Más rápida**: opción con el tiempo de entrega más corto.
 
-<div class="alert alert-warning">
-Cuando solo se encuentra disponible un tipo de opción de entrega para un pedido determinado, las opciones <b>Más económica</b> y <b>Más rápida</b> no se mostrarán al finalizar la compra.
-</div>
+>⚠️ Cuando solo se encuentra disponible un tipo de opción de entrega para un pedido determinado, las opciones **Más económica** y **Más rápida** no se mostrarán al finalizar la compra.
 
 ## Deshabilitar la función Opciones de entrega optimizadas
 
 La funcionalidad **Opciones de entrega optimizadas** está habilitada de forma predeterminada en Checkout v6. Sin embargo, en algunas regiones puede haber escenarios que contribuyan a que esta función no se utilice. En países como España o Estados Unidos, donde las opciones de envío disponibles son similares, los consumidores prefieren elegir una transportadora en función de su nivel de confianza en la empresa.
 
-<div class="alert alert-warning">
-Al deshabilitar esta función en Admin VTEX, todas las opciones de entrega disponibles se mostrarán en el proceso de Checkout. Sin embargo, si la funcionalidad de <a href="https://help.vtex.com/es/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#">Entregas Múltiples</a> está habilitada en la tienda y hay diferentes opciones de entrega entre los artículos seleccionados en el carrito, las <b>Opciones de entrega optimizadas</b> seguirán mostrándose. Es decir, se necesitará optimizar la entrega para manejar múltiples paquetes (artículos con diferentes opciones de entrega).
-</div>
+>⚠️ Al deshabilitar esta función en Admin VTEX, todas las opciones de entrega disponibles se mostrarán en el proceso de Checkout. Sin embargo, si la funcionalidad de [Entregas Múltiples](https://help.vtex.com/es/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#) está habilitada en la tienda y hay diferentes opciones de entrega entre los artículos seleccionados en el carrito, las **Opciones de entrega optimizadas** seguirán mostrándose. Es decir, se necesitará optimizar la entrega para manejar múltiples paquetes (artículos con diferentes opciones de entrega).
 
 Para deshabilitar la función __Opciones de entrega optimizadas__, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/order-allocation-algorithm-beta.md b/docs/tutorials/es/order-allocation-algorithm-beta.md
index e0c9fa4e5..1edf52964 100644
--- a/docs/tutorials/es/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/es/order-allocation-algorithm-beta.md
@@ -15,9 +15,7 @@ legacySlug: order-allocation-algorithm-beta
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-<p>Esta funcionalidad se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarla. Si tienes alguna duda, ponte en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarla. Si tienes alguna duda, ponte en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
 
 **Order Allocation Algorithm** es el algoritmo de la plataforma VTEX que busca seleccionar el seller que enviará los pedidos al menor costo dado por las [plantillas de envío](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127) de las [transportadoras](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) configuradas.
 
diff --git a/docs/tutorials/es/order-cancellation-requested-by-the-customer.md b/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
index 694778537..97a1323fc 100644
--- a/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Hay situaciones en las que los clientes pueden solicitar la cancelación de un pedido. Puede ser la [cancelación automática dentro de la ventana](https://help.vtex.com/es/tutorial/cancelacion-de-pedido-solicitada-por-el-cliente--3wEI6DUNtecooG2Ki4Akqo#cancelacion-en-la-ventana-de-cancelacion) de **cancelación** o, después de ese periodo, la cancelación [aprobada por el administrador de la tienda](https://help.vtex.com/es/tutorial/cancelacion-de-pedido-solicitada-por-el-cliente--3wEI6DUNtecooG2Ki4Akqo#cancelacion-aprobada-por-el-administrador-de-la-tienda). 
 
-<div class="alert alert-danger">
-Después que se cancela el pedido, no se le puede cambiar el status.
-</div>
+>❗ Después que se cancela el pedido, no se le puede cambiar el status.
 
 <div class = "alert alert-warning">
 No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
@@ -46,9 +44,7 @@ El administrador de la tienda debe aprobar o denegar la cancelación. Si el admi
 
 Incluso si el cancelamiento solicitado por el cliente es negado por el administrador de la tienda utilizando [VTEX DO](https://help.vtex.com/es/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu), es necesario que el administrador proceda con la [facturación](https://help.vtex.com/es/tutorial/faturar-um-pedido--7p1h852V5t54KyscpgxE2v) del pedido, ya que esto es lo que hace que el pedido siga su curso.
 
-<div class="alert alert-warning">
-Si la funcionalidad <a href="https://help.vtex.com/es/tutorial/cambio-de-pedido--2IK9mwQjBKseQmE8K8saO8#como-activar-la-funcionalidad">Cambio de pedido</a> está activada, los pedidos pueden ser modificados o cancelados en cualquier momento, incluso después de la ventana de cancelación.
-</div>
+>⚠️ Si la funcionalidad [Cambio de pedido](https://help.vtex.com/es/tutorial/cambio-de-pedido--2IK9mwQjBKseQmE8K8saO8#como-activar-la-funcionalidad) está activada, los pedidos pueden ser modificados o cancelados en cualquier momento, incluso después de la ventana de cancelación.
 
 ## Motivo de la cancelación
 
diff --git a/docs/tutorials/es/order-flow-and-status.md b/docs/tutorials/es/order-flow-and-status.md
index 99916f0a3..537ab6a0a 100644
--- a/docs/tutorials/es/order-flow-and-status.md
+++ b/docs/tutorials/es/order-flow-and-status.md
@@ -34,9 +34,7 @@ Hay cuatro tipos de flujo de pedidos en VTEX:
 - **[Flujo completo](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#flujo-completo):** es el flujo de pedidos realizados en la tienda responsable de la venta y envío del pedido. En este caso, la tienda actúa como _seller_ y _marketplace_ simultáneamente.
 - **[Flujo de cadena](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#flujo-de-cadena)**: es el flujo de pedidos visto por la tienda que media la venta entre el _marketplace_ y el _seller_. Este flujo es similar al de _marketplace_, sin embargo, el proceso de pago se realiza solo en el _marketplace_ y no en la tienda que actúa como cadena. Este flujo se ve en escenarios de venta de [Multilevel Omnichannel Inventory](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4).
 
-<div class="alert alert-warning">
-Para los casos de pedidos incompletos, consulta el artículo <a href="https://help.vtex.com/es/tutorial/entendendo-os-pedidos-incompletos--tutorials_294">Cómo funcionan los pedidos incompletos</a> para entender las razones de este flujo y de su cancelación.
-</div>
+>⚠️ Para los casos de pedidos incompletos, consulta el artículo [Cómo funcionan los pedidos incompletos](https://help.vtex.com/es/tutorial/entendendo-os-pedidos-incompletos--tutorials_294) para entender las razones de este flujo y de su cancelación.
 
 ### Flujo de marketplace
 
@@ -64,9 +62,7 @@ Este es el flujo del pedido visto por la tienda responsable de enviar los produc
 1. Cuando el _seller_ recibe el pedido, el status inicial es `Pedido aceptado`.
 2. Después de que el seller recibe el pedido, el status cambia automáticamente a `Esperando autorización para fufillment`. Este es un status de espera para que el marketplace indique que obtuvo la confirmación del pago del pedido.
 
-  <div class="alert alert-danger">
-La plataforma permite adelantar manualmente el status <i>Esperando autorización para fufillment</i> al hacer clic en <i>Autorizar fulfillment</i>. Sin embargo, si el seller adelanta el status manualmente no significa que el marketplace haya liberado el pedido para preparación, lo que puede implicar discrepancias en la información. Utiliza el cambio manual con precaución. Recomendamos su uso solo cuando se tiene la autorización del marketplace para el envío del pedido.
-</div>
+  >❗ La plataforma permite adelantar manualmente el status <i>Esperando autorización para fufillment</i> al hacer clic en <i>Autorizar fulfillment</i>. Sin embargo, si el seller adelanta el status manualmente no significa que el marketplace haya liberado el pedido para preparación, lo que puede implicar discrepancias en la información. Utiliza el cambio manual con precaución. Recomendamos su uso solo cuando se tiene la autorización del marketplace para el envío del pedido.
 
 3. El status cambia automáticamente a `Periodo de cancelación`. El pedido permanecerá en esta etapa hasta que haya transcurrido el [tiempo de espera para cancelar configurado](https://help.vtex.com/es/tutorial/configuracoes-gerais/#pedidos). 
 
@@ -79,20 +75,17 @@ El Periodo de cancelación existe para que el cliente pueda cancelar la compra s
     * **Pedido cancelado:** si el cliente solicita la cancelación del pedido durante el tiempo de espera para cancelar, en vez de pasar a la preparación, pasará a la cancelación y el status cambiará a `Cancelando`. 
 5. El pedido permanecerá en el status `Listo para preparación` hasta que el _seller_ confirme. Esta confirmación significa que el _seller_ inició la preparación del pedido, que puede realizarse manualmente mediante el Admin o por integración con el ERP utilizando el request [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
 
-  <div class="alert alert-danger">
-Al confirmar el inicio de la preparación, el seller asume la responsabilidad de la reserva de los ítems del pedido. A partir de ese momento, si hay alguna actualización en el stock, la plataforma VTEX desestima la reserva de estos SKU. Por lo tanto, actualiza el stock para los SKU de un pedido determinado únicamente al facturarlo. De este modo, se evitan las divergencias de stock que dependen de la interacción con la <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integración backoffice</a> de tu tienda.
-</div>
+  >❗ Al confirmar el inicio de la preparación, el seller asume la responsabilidad de la reserva de los ítems del pedido. A partir de ese momento, si hay alguna actualización en el stock, la plataforma VTEX desestima la reserva de estos SKU. Por lo tanto, actualiza el stock para los SKU de un pedido determinado únicamente al facturarlo. De este modo, se evitan las divergencias de stock que dependen de la interacción con la [integración backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) de tu tienda.
 
 6. Una vez iniciada la preparación, es momento de facturar el pedido. La plataforma espera a que se incluya la factura, el status del pedido puede estar en `Verificando factura` si hay un error. Consulta [los casos más comunes](https://help.vtex.com/es/tutorial/por-que-o-pedido-esta-no-status-verificando-fatura--5VJjxRjeH6SimiG0Wkk2gm) para que el pedido se quede en este status. Es importante recordar que si el pedido se factura parcialmente, puede volver al status `Pago aprobado` hasta que el administrador de la tienda incluya las facturas que sumadas corresponden al valor total del pedido.
 7. El último status del flujo es `Facturado`. Después de eso, el seller debe completar el envío del pedido.
 
-<div class="alert alert-danger">
-Ten en cuenta que:
-  <ul>
-    <li>La <b>cancelación del pedido</b> puede iniciarse en varias etapas del flujo del pedido, ya sea por parte del cliente o de la tienda. En este caso, después de solicitar la cancelación, el proceso se realiza de forma automática, incluyendo el reembolso del valor pagado al cliente. La cancelación finaliza cuando el pedido cambia al status <i>Cancelado</i></li>.
-    <li>Los sellers tienen la autonomía de forzar manualmente el cambio del pedido durante el status <i>Esperando autorización para fufillment</i>. Esto significa realizar la entrega sin que el marketplace haya confirmado la liberación y sin recibir el pago del pedido. En caso de cambio manual, es obligación del seller comprobar que el pedido está en condiciones de ser preparado, incluyendo si el pago ha sido confirmado.</li>
-    </ul>
-</div>
+>❗ Ten en cuenta que:
+>
+> * La **cancelación del pedido** puede iniciarse en varias etapas del flujo del pedido, ya sea por parte del cliente o de la tienda. En este caso, después de solicitar la cancelación, el proceso se realiza de forma automática, incluyendo el reembolso del valor pagado al cliente. La cancelación finaliza cuando el pedido cambia al status <i>Cancelado</i>.
+>
+> * Los sellers tienen la autonomía de forzar manualmente el cambio del pedido durante el status <i>Esperando autorización para fufillment</i>. Esto significa realizar la entrega sin que el marketplace haya confirmado la liberación y sin recibir el pago del pedido. En caso de cambio manual, es obligación del seller comprobar que el pedido está en condiciones de ser preparado, incluyendo si el pago ha sido confirmado.
+>     
 
 ### Flujo completo
 
@@ -109,9 +102,7 @@ El flujo completo del pedido es visto por la tienda que realiza la venta y el en
     *  De forma manual, en el Admin, haciendo clic en la flecha que se encuentra encima del status `Iniciar preparación`.
     * A través de la [API con un ERP](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide), por ejemplo, utilizando la ruta [Start handling order.](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling)
 
-  <div class="alert alert-danger">
-Al confirmar el inicio de la preparación, el seller asume la responsabilidad de la reserva de los ítems del pedido. A partir de ese momento, si hay alguna actualización en el stock, la plataforma VTEX desestima la reserva de estos SKUs. Por lo tanto, actualiza el stock para los SKUs de un pedido determinado únicamente al facturarlo. De este modo, se evitan las divergencias de stock que dependen de la interacción con la <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integración backoffice</a> de tu tienda.
-</div>
+  >❗ Al confirmar el inicio de la preparación, el seller asume la responsabilidad de la reserva de los ítems del pedido. A partir de ese momento, si hay alguna actualización en el stock, la plataforma VTEX desestima la reserva de estos SKUs. Por lo tanto, actualiza el stock para los SKUs de un pedido determinado únicamente al facturarlo. De este modo, se evitan las divergencias de stock que dependen de la interacción con la [integración backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) de tu tienda.
 
 5. Una vez iniciada la preparación, el status del pedido cambia a `Preparando envío` y la próxima etapa es facturar el pedido. El sistema espera la factura en el status `Verificando factura`. Se debe [incluir la factura](https://help.vtex.com/es/tutorial/como-inserir-a-nota-fiscal) que corresponde al valor total del pedido. 
 6. Después de incluir las facturas, el status del pedido cambia a `Facturado`, el último status del flujo, y la tienda debe completar el envío del pedido.
@@ -136,9 +127,7 @@ Ve más información sobre la cancelación y el reembolso en los artículos <a h
 
 Mientras se realiza el proceso de cancelación, el status permanece en `Cancelando`. Una vez completada la cancelación, el status del pedido cambia a `Cancelado`. 
 
-<div class="alert alert-danger">
-Ten en cuenta que cuando la cancelación se realiza antes de que la tienda inicie la preparación del pedido (status <i>Preparando envío</i>), los ítems tienen la <a href="https://help.vtex.com/es/tutorial/how-does-reservation-work--tutorials_92">reserva cancelada</a> en el stock. Sin embargo, si la cancelación se realiza después de este status, los ítems ya tienen la <a href="https://help.vtex.com/es/tutorial/como-a-reserva-funciona--tutorials_92#reserva-reconocida">reserva reconocida</a> en el stock y la tienda debe actualizar la cantidad de ítems del stock para que se cancele la reserva de los SKUs de un pedido cancelado (que fueron reservados). 
-</div>
+>❗ Ten en cuenta que cuando la cancelación se realiza antes de que la tienda inicie la preparación del pedido (status <i>Preparando envío</i>), los ítems tienen la [reserva cancelada](https://help.vtex.com/es/tutorial/how-does-reservation-work--tutorials_92) en el stock. Sin embargo, si la cancelación se realiza después de este status, los ítems ya tienen la [reserva reconocida](https://help.vtex.com/es/tutorial/como-a-reserva-funciona--tutorials_92#reserva-reconocida) en el stock y la tienda debe actualizar la cantidad de ítems del stock para que se cancele la reserva de los SKUs de un pedido cancelado (que fueron reservados).
 
 Para saber más sobre la cancelación de pedidos, consulta el artículo [¿Por qué un pedido fue cancelado?](https://help.vtex.com/es/faq/por-que-meu-pedido-foi-cancelado--frequentlyAskedQuestions_493).
 
@@ -164,9 +153,7 @@ A continuación se muestra la tabla con los status de los pedidos. La informaci
 - **Visto por:** en qué flujo es visible el status (_marketplace_, _seller_, cadena y completo).
 - **Significado:** significado del status detallado.   
 
-<div class="alert alert-warning">
-Ten en cuenta que los status del flujo de pedido completo (flujo visto por las tiendas responsables de la venta y envío de los pedidos) coincide con los status del marketplace y seller. Algunos status pueden ser vistos a través de API, pero no son visibles en el flujo del pedido que se ve en el Admin en «Todos los pedidos».
-</div>
+>⚠️ Ten en cuenta que los status del flujo de pedido completo (flujo visto por las tiendas responsables de la venta y envío de los pedidos) coincide con los status del marketplace y seller. Algunos status pueden ser vistos a través de API, pero no son visibles en el flujo del pedido que se ve en el Admin en «Todos los pedidos».
 
 <style type="text/css">
 .tg  {border-collapse:collapse;border-color:#ccc;border-spacing:0;}
diff --git a/docs/tutorials/es/order-replacement.md b/docs/tutorials/es/order-replacement.md
index dff0392cd..cc7cd28ac 100644
--- a/docs/tutorials/es/order-replacement.md
+++ b/docs/tutorials/es/order-replacement.md
@@ -19,9 +19,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 [Sustituir ítems](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) es diferente a cambio de pedidos. Al cambiar un pedido, el cliente solicita cambios en el pedido, y al sustituir ítems, la tienda modifica el pedido.
 
-<div class="alert alert-danger">
-Esta funcionalidad está disponible para todas las tiendas, sin embargo, debes activarla para que tus clientes puedan utilizarla. 
-</div>
+>❗ Esta funcionalidad está disponible para todas las tiendas, sin embargo, debes activarla para que tus clientes puedan utilizarla.
 
 En este artículo puedes consultar:
 
@@ -31,8 +29,7 @@ En este artículo puedes consultar:
 
 ## Cómo activar la funcionalidad
 
-<div class="alert alert-danger"> Si el Cambio de pedidos se activa en tiendas cuya página Mis pedidos tiene personalización, debes volver a crear la personalización. La funcionalidad sustituye la versión antigua de la página (que está personalizada) por una nueva página no personalizada. Para estos casos, recomendamos que antes de activar la funcionalidad en tu tienda, utilices un  <a href="https://help.vtex.com/es/tutorial/acceder-al-ambiente-beta--3BHM289568gcSwk2O80Asu"> entorno beta</a> y valides la activación con personalización.
-</div>
+>❗ Si el Cambio de pedidos se activa en tiendas cuya página Mis pedidos tiene personalización, debes volver a crear la personalización. La funcionalidad sustituye la versión antigua de la página (que está personalizada) por una nueva página no personalizada. Para estos casos, recomendamos que antes de activar la funcionalidad en tu tienda, utilices un  [ entorno beta](https://help.vtex.com/es/tutorial/acceder-al-ambiente-beta--3BHM289568gcSwk2O80Asu) y valides la activación con personalización.
 
 Para activar la funcionalidad, siga los pasos a continuación:
 
@@ -81,7 +78,5 @@ Con la funcionalidad activada, los clientes de tu tienda tienen acceso a una nue
 
 Después de hacer clic en `Cambiar pedido`, el cliente será redirigido al carrito y luego al _checkout._ En el _checkout_, puede realizar los cambios deseados (dirección, tipo de entrega, forma de pago y SKU). El proceso solo se completa cuando se finaliza la compra. Al cliente no se le cobra dos veces por el mismo pedido.
 
-<div class="alert alert-warning">
-El pago realizado anteriormente solo puede utilizarse si el valor del nuevo pedido es igual al del pedido original. Si no se utiliza el pago anterior con tarjeta de crédito, este se reembolsa automáticamente.
-<p>En el caso de las formas de pago que expiran en un plazo de 2 días (como el boleto bancario), no se puede reutilizar el pago.
-</div>
+>⚠️ El pago realizado anteriormente solo puede utilizarse si el valor del nuevo pedido es igual al del pedido original. Si no se utiliza el pago anterior con tarjeta de crédito, este se reembolsa automáticamente.
+> <p>En el caso de las formas de pago que expiran en un plazo de 2 días (como el boleto bancario), no se puede reutilizar el pago.
diff --git a/docs/tutorials/es/order-split-and-delivery-split.md b/docs/tutorials/es/order-split-and-delivery-split.md
index bf0a69a65..0487657c8 100644
--- a/docs/tutorials/es/order-split-and-delivery-split.md
+++ b/docs/tutorials/es/order-split-and-delivery-split.md
@@ -54,8 +54,6 @@ El pedido lo atiende un solo _seller_, pero es necesario realizar más de una en
 
     Esta división se realiza de forma automática y nativa para las tiendas que cuentan con Checkout V6, a través del campo `allowMultipleDeliveries` indicado como `true` en la API [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm). La configuración viene activa por defecto para que sea posible realizar compras con diferentes modalidades de entrega en el mismo carrito.
 
-<div class="alert alert-danger">
-  No recomendamos operar la tienda con el campo <code>allowMultipleDeliveries</code> indicado como <i>false</i>. En esta configuración, cuando hay artículos en el carrito que no tienen ningún método de entrega en común, es decir, los SLAID son diferentes y el carrito tiene un punto de recogida, no será posible completar el pedido.
-</div>
+>❗ No recomendamos operar la tienda con el campo `allowMultipleDeliveries` indicado como <i>false</i>. En esta configuración, cuando hay artículos en el carrito que no tienen ningún método de entrega en común, es decir, los SLAID son diferentes y el carrito tiene un punto de recogida, no será posible completar el pedido.
 
 * **Muelles diferentes:** una misma tienda ofrece todos los ítems de un pedido, pero en el cálculo de la ruta logística están asociados a diferentes muelles. Entonces hay que _dividir los paquetes de entrega_, pero sin dividir el pedido entre diferentes tiendas. La plataforma lo hace automáticamente.
diff --git a/docs/tutorials/es/order-to-delivery.md b/docs/tutorials/es/order-to-delivery.md
index 21f7c74bf..e44e309de 100644
--- a/docs/tutorials/es/order-to-delivery.md
+++ b/docs/tutorials/es/order-to-delivery.md
@@ -15,6 +15,4 @@ legacySlug: pedidos-de-entrega
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>  
+>⚠️ Este contenido sólo está disponible en portugués.  
diff --git a/docs/tutorials/es/order-transactional-email-templates.md b/docs/tutorials/es/order-transactional-email-templates.md
index 5e98c6bfc..36dfd19d5 100644
--- a/docs/tutorials/es/order-transactional-email-templates.md
+++ b/docs/tutorials/es/order-transactional-email-templates.md
@@ -17,9 +17,7 @@ subcategory: 4D5LrWwlHGmOWMomOaaGee
 
 El objetivo de este artículo es listar las plantillas de e-mails transaccionales que tenemos como estándar en VTEX para el flujo del pedido. Además, vamos a especificar el gatillo necesario para el disparo de cada e-mail.
 
-<div class="alert alert-warning">
-Atención: las solicitudes de origen Fulfillment no reciben correos electrónicos transaccionales de VTEX. En este caso, el disparo de correos electrónicos queda a cargo del propio mercado.
-</div>
+>⚠️ Atención: las solicitudes de origen Fulfillment no reciben correos electrónicos transaccionales de VTEX. En este caso, el disparo de correos electrónicos queda a cargo del propio mercado.
 
 Para acceder a las plantillas, siga los siguientes pasos:
 
diff --git a/docs/tutorials/es/orders-management-feed-v3-setup.md b/docs/tutorials/es/orders-management-feed-v3-setup.md
index a059db371..d1561d040 100644
--- a/docs/tutorials/es/orders-management-feed-v3-setup.md
+++ b/docs/tutorials/es/orders-management-feed-v3-setup.md
@@ -23,13 +23,9 @@ Feed v3 hace posible la personalización del _feed_ con filtros e intervalos nec
 
 Esto significa que es posible definir qué status estarán visibles en el _feed_ de eventos de su tienda a través de la [API Feed Configuration](https://developers.vtex.com/reference/feed-v3#feedconfiguration). Se puede ver la lista con los posibles status de pedido en el artículo [Flujo de pedido en Gestión de pedidos](https://help.vtex.com/es/tutorial/fluxo-de-pedido/#entiendo-los-estados).
 
-<div class="alert alert-info">
-Si el objeto <code>filter</code> no se configura en la API, las actualizaciones de <strong>todos</strong> los status se enviarán al <i>feed</i>. 
-</div>
+>ℹ️ Si el objeto `filter` no se configura en la API, las actualizaciones de **todos** los status se enviarán al <i>feed</i>.
 
-<div class="alert alert-info"> 
-La AppKey que se utilizará en la integración debe ser la misma que la utilizada en la configuración inicial.
-</div>
+>ℹ️ La AppKey que se utilizará en la integración debe ser la misma que la utilizada en la configuración inicial.
 
 Un ejemplo de _body_ sería el siguiente:
 
@@ -52,17 +48,13 @@ El tiempo de espera _default_ definido en el campo es de 30 segundos, pero se pu
 
 El tiempo de permanencia de un evento en su _feed_ se define en segundos en el campo `MessageRetentionPeriodInSeconds`. Si un evento no recibe interacciones dentro del tiempo configurado, se excluirá de la fila del _feed_ y se perderán los datos referentes a este. El tiempo máximo que se puede definir en el campo es de hasta 345600 segundos (4 días). 
 
-<div class="alert alert-info">
-Para configurar y utilizar el Feed v3, debe tener un <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?locale=es">perfil de acceso</a> habilitado con el recurso <code>Feed v3 and Hook</code>, dentro del producto de <strong>OMS</strong>.
-</div>
+>ℹ️ Para configurar y utilizar el Feed v3, debe tener un [perfil de acceso](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?locale=es) habilitado con el recurso `Feed v3 and Hook`, dentro del producto de **OMS**.
 
 ## Cómo funcionan las APIs del Feed v3
 
 El Feed v3 trabaja con dos llamadas: una para su lectura y otra para informar que un evento ya ha sido leído y debe ser excluido.
 
-<div class="alert alert-warning"> 
-¡No olvide configurar el Feed antes de usarlo!
-</div>
+>⚠️ ¡No olvide configurar el Feed antes de usarlo!
 
 ### Get feed order status
 
@@ -70,9 +62,7 @@ La [llamada de lectura del _feed_](https://developers.vtex.com/reference/feed-v3
 
 El parámetro `maxLot` indica el número máximo de eventos que serán devueltos a cada llamada. En el Feed v3, puede especificar __hasta 10 eventos__. 
 
-<div class="alert alert-warning">
-Cada vez que se realiza una llamada de lectura del _feed_, <strong>todos</strong> los eventos devueltos se mantienen invisibles en el _feed_ durante el tiempo definido en el campo <code>visibilityTimeoutInSeconds</code> de la API de Feed Configuration.
-</div> 
+>⚠️ Cada vez que se realiza una llamada de lectura del _feed_, **todos** los eventos devueltos se mantienen invisibles en el _feed_ durante el tiempo definido en el campo `visibilityTimeoutInSeconds` de la API de Feed Configuration. 
 
 #### Confirm item feed order status
 
@@ -82,15 +72,11 @@ En el _body_ del _commit_ se debe pasar el valor del `handles`. Este valor es de
 
 En el _body_, cada _array_ puede contener tantos `handles` como sean necesarios. Esto significa que es posible _commitar_ más de un evento a la vez.
 
-<div class="alert alert-info">
-El campo <code>visibilityTimeoutInSeconds</code> indica el tiempo máximo para realizar un <i>commit</i> de un evento. 
-</div> 
+>ℹ️ El campo `visibilityTimeoutInSeconds` indica el tiempo máximo para realizar un <i>commit</i> de un evento. 
 
 No hay casos en los que un evento del _feed_ no deba ser _commitado_. Su sistema debe _commitar_ todos los eventos de su fila. __Una vez que un evento ha sido _commitado_, no se puede recuperar en el _feed_ con el mismo _appkey_.__
 
-<div class="alert alert-warning">
-Todos los posibles status de pedido (considerando el filtrado, cuando corresponda) deben tratarse en la integración para evitar errores. Debe prestarse especial atención al <code>Status Null</code>, que puede no ser identificado y terminar siendo mapeado como otro status, lo que puede generar errores.
-</div> 
+>⚠️ Todos los posibles status de pedido (considerando el filtrado, cuando corresponda) deben tratarse en la integración para evitar errores. Debe prestarse especial atención al `Status Null`, que puede no ser identificado y terminar siendo mapeado como otro status, lo que puede generar errores. 
 
 Para entender más sobre cómo funciona el _feed_, acceda a nuestro artículo sobre [cómo funciona el _feed_ del módulo de Gestión de Pedidos](https://help.vtex.com/es/tutorial/como-funciona-el-feed-v3-del-modulo-de-gestion-de-pedidos--5SzSKee2f666YCoWkm0eQC).
 
diff --git a/docs/tutorials/es/out-of-stock-errors-in-marketplace-integration-orders.md b/docs/tutorials/es/out-of-stock-errors-in-marketplace-integration-orders.md
index 0798fe43e..5000409d7 100644
--- a/docs/tutorials/es/out-of-stock-errors-in-marketplace-integration-orders.md
+++ b/docs/tutorials/es/out-of-stock-errors-in-marketplace-integration-orders.md
@@ -28,9 +28,7 @@ Los errores de falta de _stock_ se pueden producir por diferentes razones, las m
 
 Después de solucionar el error, el pedido se debe reprocesar manualmente. En su Admin, en el módulo **MARKETPLACE > Conexiones > Pedidos**, haga clic en el pedido con error. Luego, el botón **Acciones** se vuelve visible, haga clic en el mismo y elija la opción **Reprocesar**.
 
-<div class="alert alert-info">
-Si el error persiste, abra un <a href="https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">ticket para el soporte VTEX</a>.
-</div>
+>ℹ️ Si el error persiste, abra un [ticket para el soporte VTEX](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
 ### Sepa más
 
diff --git a/docs/tutorials/es/payment-provider-protocol.md b/docs/tutorials/es/payment-provider-protocol.md
index 9b8b449b2..19434f127 100644
--- a/docs/tutorials/es/payment-provider-protocol.md
+++ b/docs/tutorials/es/payment-provider-protocol.md
@@ -69,9 +69,7 @@ El proveedor debe enviar el  [AOC](https://www.pcisecuritystandards.org/document
 - __Firma__: documento firmado por el representante de la empresa y por el QSA.
 - __Fecha de vencimiento__: la validez del AOC es de 1 año después de la fecha de firma. No debe reenviarse a VTEX, el AOC emitido hace más de 11 meses, es decir, con menos de 30 días para la fecha de vencimiento.
 
-<div class="alert alert-danger">
-Los documentos SAQ (Self-Assessment Questionnaire) y AOC (Attestation of Compliance for Onsite Assessments – Merchants Version) no se aceptan en el proceso de integración de VTEX.
-</div>
+>❗ Los documentos SAQ (Self-Assessment Questionnaire) y AOC (Attestation of Compliance for Onsite Assessments – Merchants Version) no se aceptan en el proceso de integración de VTEX.
 <br>
 
 #### Proveedores de pagos offline o tarjeta private label (o tarjetas en general), pero que implican soluciones con redirect
@@ -97,11 +95,11 @@ Después de recibir los datos de acceso e implementar el backend, el proveedor d
 
 ![ppp-vtex-store-es](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/aa2d1e30c83c7d35c7313c112a5b69d1/image.png)
 
-<div class="alert alert-warning">
-<p>
-Para completar el proceso de homologación, se debe implementar una lógica específica para abordar los requisitos de la prueba. En los requests enviados a Test Suite, utiliza el encabezado adicional <code>X-VTEX-API-Is-TestSuite = true</code> para identificarlos y enmascarar cualquier escenario requerido.<br><br> Toda comunicación con los servidores, ya sea durante el proceso de homologación o en producción, debe llevarse a cabo a través de HTTPS, que utiliza el puerto 443 de forma predeterminada. Es importante recordar que toda comunicación HTTPS debe usar exclusivamente TLS 1.2.
-</p>
-</div> 
+>⚠️ Para completar el proceso de homologación, se debe implementar una lógica específica para abordar los requisitos de la prueba. En los requests enviados a Test Suite, utiliza el encabezado adicional `X-VTEX-API-Is-TestSuite = true` para identificarlos y enmascarar cualquier escenario requerido.
+>
+> 
+>
+>  Toda comunicación con los servidores, ya sea durante el proceso de homologación o en producción, debe llevarse a cabo a través de HTTPS, que utiliza el puerto 443 de forma predeterminada. Es importante recordar que toda comunicación HTTPS debe usar exclusivamente TLS 1.2. 
 
 <!-----
 
@@ -135,11 +133,7 @@ Luego, verás un formulario que tiene tres secciones: Información de servicio,
 * **URL de servicio:** define la URL del servicio de tu proveedor. Esta URL será la dirección base del protocolo y debe seguir el formato determinado por el proveedor. Por ejemplo, si la URL del servicio es [https://example.com/](https://example.com/), la URL completa del endpoint /payments será [https://example.com/payments](https://example.com/payments).
 * **Clave de aplicación y token de aplicación:** el botón de alternancia con clave de aplicación y token de aplicación te permite escoger si se configuran estos campos o no, lo que puede facilitar las pruebas durante la etapa de desarrollo. Si no se activa esta opción, las credenciales se enviarán en los encabezados como una string vacía.
 
-<div class="alert alert-info">
-  <p>
-El gateway almacena las credenciales de las tiendas configuradas en la afiliación y las envía en los encabezados X-VTEX-API-AppKey y X-VTEX-API-AppToken. La excepción son las integraciones desarrolladas con VTEX IO, en cuyo caso, los encabezados se envían como x-provider-api-appKey y x-provider-api-appToken. Si estás desarrollando usando <a href="https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework">Payment Provider Framework (IO)</a>, esto lo define la opción usesProviderHeadersName. Consulta los ajustes disponibles <a href="https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework#available-configurable-options">aquí</a>.
-</p>
-  </div>
+>ℹ️ El gateway almacena las credenciales de las tiendas configuradas en la afiliación y las envía en los encabezados X-VTEX-API-AppKey y X-VTEX-API-AppToken. La excepción son las integraciones desarrolladas con VTEX IO, en cuyo caso, los encabezados se envían como x-provider-api-appKey y x-provider-api-appToken. Si estás desarrollando usando [Payment Provider Framework (IO)](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework), esto lo define la opción usesProviderHeadersName. Consulta los ajustes disponibles [aquí](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-provider-framework#available-configurable-options).
 
 #### Medio de pago
 
@@ -162,9 +156,7 @@ Cuando haces clic en el botón `Ejecutar prueba`, Test Suite llama la URL de ser
 * **Flujo de boleto:** en esta prueba, se envía un request[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera una respuesta con status undefined y el campo `bankIssueInvoiceUrl` rellenado con la URL del ticket. Después de 15 segundos, se espera otra respuesta en el mismo formato mediante un POST de la URL enviada en el campo callbackUrl y con el status approved. Con la integración en producción, esta última llamada realizada por callbackUrl se autentica con las claves de entorno del partner: vtex-app-key y vtex-app-token. Para más información sobre el flujo de callback consulta la sección [Autorización del pago](#autorizacion-de-pago).
 * **Flujo de redirección:** esta prueba se divide en dos pasos. Primero, se envía un request [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) a {{ServiceURL}}/payments y se espera una respuesta con status undefined y el campo redirectUrl rellenado con la URL que se utilizará para redirigir al cliente. Después de 15 segundos, se espera otra respuesta en el mismo formato mediante un POST de la URL enviada en el campo callbackUrl y con el status approved. Con la integración en producción, esta última llamada realizada por callbackUrl se autentica con las claves de entorno del partner: vtex-app-key y vtex-app-token. Para más información sobre el flujo de callback consulta la sección [Autorización del pago](#autorizacion-de-pago). El conector que utilizará redirección no tiene que pasar todas las pruebas de Test Suite, solo la prueba de Redirección.
 
-<div class="alert alert-warning">
-  En el caso de las tarjetas de crédito, las pruebas obligatorias son: Autorizar, Denegado, Cancelar, Aprobado asíncrono y Denegado asíncrono.
-  </div>
+>⚠️ En el caso de las tarjetas de crédito, las pruebas obligatorias son: Autorizar, Denegado, Cancelar, Aprobado asíncrono y Denegado asíncrono.
 
 Para identificar cómo responder a cada una de las pruebas con tarjetas de crédito, utiliza los siguientes números específicos:
 
@@ -192,8 +184,7 @@ Todo comienza con la solicitud de un nuevo pago, después de la creación de un
 
 ![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
 
-<div class="alert alert-info">
-  El período predeterminado de 7 días para reintentos (retries) de pago asíncronos solo se aplica cuando el usuario no especifica un valor en el campo <code>delayToCancel</code> del endpoint <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> o al enviar la URL de devolución de llamada.</div>
+>ℹ️ El período predeterminado de 7 días para reintentos (retries) de pago asíncronos solo se aplica cuando el usuario no especifica un valor en el campo `delayToCancel` del endpoint [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) o al enviar la URL de devolución de llamada.
 
 ### Autorización de pago
 En este punto, VTEX llama al endpoint __*/payments*__ y envía un payload con los datos de pago para su proveedor. El proveedor debe procesar estos datos y enviar la respuesta, que debe contener uno de los valores de status: __approved__, __denied__ o __undefined__.
@@ -242,21 +233,15 @@ Vea a continuación, um ejemplo de payload enviada junto con la callback URL:
 {"paymentId":"8B3BA2F4352545A8B1C5A215F356A01C","status":"approved","authorizationId":"184520","nsu":"21705348","tid":"21705348","acquirer":"pagarme","code":"0000","message":"Transação aprovada com sucesso","delayToAutoSettle":1200, "delayToAutoSettleAfterAntifraud":1200, "delayToCancel":86400,"cardBrand":"Mastercard","firstDigits":"534696","lastDigits":"6921","maxValue":16.6}
 ```
 
-<div class="alert alert-info">
-  Los valores de los parámetros enviados en el payload de callback reemplazan los valores originales informados en la llamada de <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a>.  
-</div>
+>ℹ️ Los valores de los parámetros enviados en el payload de callback reemplazan los valores originales informados en la llamada de [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
 
-<div class="alert alert-warning">
-  Si los parámetros de tiempo de espera (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) no se envían con la URL de devolución de llamada, los valores se establecerán automáticamente en 24 horas.
-</div>
+>⚠️ Si los parámetros de tiempo de espera (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) no se envían con la URL de devolución de llamada, los valores se establecerán automáticamente en 24 horas.
 
 Al realizar el request de _callback_, recomendamos que los proveedores de pago utilicen la URL de _callback_ exactamente como la recibieron, lo que garantiza que se incluyan todos los parámetros.
 
 Al llamar a CallbackURL, su proveedor debe enviar en el request los headers *X-VTEX-API-AppKey* y *X-VTEX-API-AppToken*. Más información sobre esto en la [sección de credenciales VTEX](/es/tutorial/payment-provider-protocol#credenciales-vtex).
 
-<div class="alert alert-danger">
-Además de CallbackURL, si el status es <strong>undefined</strong>, VTEX intentará de nuevo llamar al endpoint de la autorización de pago. Si el status devuelto en estas llamadas permanece como <strong>undefined</strong>, las llamadas continuarán por 7 días. Por lo tanto, <strong>es importante que su proveedor esté preparado para recibir la misma autorización de pago varias veces</strong>.
-</div>
+>❗ Además de CallbackURL, si el status es **undefined**, VTEX intentará de nuevo llamar al endpoint de la autorización de pago. Si el status devuelto en estas llamadas permanece como **undefined**, las llamadas continuarán por 7 días. Por lo tanto, **es importante que su proveedor esté preparado para recibir la misma autorización de pago varias veces**.
 
 Una vez que el pago ha sido procesado por su proveedor, de forma directa o asincrónica, movemos la transacción de pago dentro de VTEX al status *autorizado* o *cancelado*, de acuerdo con el status de la respuesta del procesamiento.
 
@@ -280,9 +265,7 @@ Si la transacción de pago está autorizada en VTEX Payments, puede recibir soli
 
 Cuando el proveedor recibe una solicitud de liquidación, debe liquidar el pago y responder con información de liquidación. Si esta llamada falla, hacemos algunas retentaciones, por hasta 1 día.
 
-<div class="alert alert-danger">
-Su proveedor debe estar preparado para recibir la misma llamada de liquidación varias veces.
-</div>
+>❗ Su proveedor debe estar preparado para recibir la misma llamada de liquidación varias veces.
 
 Si la llamada de liquidación funciona bien, movemos la transacción de pago al estado *Finalizado*, y el flujo termina con éxito.
 
diff --git a/docs/tutorials/es/payments-in-vtex-marketplaces.md b/docs/tutorials/es/payments-in-vtex-marketplaces.md
index 3311c6a4e..9767adaca 100644
--- a/docs/tutorials/es/payments-in-vtex-marketplaces.md
+++ b/docs/tutorials/es/payments-in-vtex-marketplaces.md
@@ -27,9 +27,7 @@ Los pedidos realizados en un marketplace pueden contener ítems de varios seller
 
 Si el _seller _es el procesador de pagos, debe operar bajo las condiciones establecidas en nuestro [Split de transacción](https://help.vtex.com/es/tutorial/split-payment#split-de-transacao). Asimismo, si el marketplace VTEX se encarga de procesar los pagos, debe seguir el flujo del [Split de cobros](https://help.vtex.com/es/tutorial/split-payment--6k5JidhYRUxileNolY2VLx#split-de-recebiveis) o realizar sus transferencias fuera del entorno VTEX. 
 
-<div class="alert alert-info">
-Los clientes de VTEX en Brasil pueden utilizar tanto el split de transacción como el split de cobros. Los clientes de VTEX en otros países solo deben utilizar el split de transacción. Ten en cuenta que algunos países imponen restricciones a la transferencia de valores entre sellers y marketplaces. Infórmate de las restricciones con las autoridades financieras de tu país antes de construir tu arquitectura de pagos.
-</div>
+>ℹ️ Los clientes de VTEX en Brasil pueden utilizar tanto el split de transacción como el split de cobros. Los clientes de VTEX en otros países solo deben utilizar el split de transacción. Ten en cuenta que algunos países imponen restricciones a la transferencia de valores entre sellers y marketplaces. Infórmate de las restricciones con las autoridades financieras de tu país antes de construir tu arquitectura de pagos.
 
 Para establecer los valores de transferencias externas al entorno VTEX, utiliza los [informes del OMS](https://help.vtex.com/es/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY) para calcular las comisiones. En Brasil, la transferencia de valores en un entorno externo, sin la participación de la plataforma VTEX, solo puede realizarse por las instituciones financieras.
 
@@ -37,9 +35,7 @@ Para establecer los valores de transferencias externas al entorno VTEX, utiliza
 
 Consulta a continuación la configuración necesaria en tu Admin VTEX para crear comisiones sobre pedidos de _sellers _y para hacer que el _seller_ o el _marketplace_ sea el procesador de pagos.
 
-<div class="alert alert-info">
-En caso de que la integración con sellers externos o sellers VTEX se haga mediante API, consulta <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-seller-processing-payments">External seller processing payment</a>. 
-</div>
+>ℹ️ En caso de que la integración con sellers externos o sellers VTEX se haga mediante API, consulta <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-seller-processing-payments">External seller processing payment</a>.
 
 ### Configurar comisiones para los _sellers_
 
diff --git a/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md b/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md
index 5bbb88c0d..f233bc902 100644
--- a/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md
+++ b/docs/tutorials/es/penetration-testing-and-vulnerability-notice.md
@@ -15,13 +15,9 @@ legacySlug: evaluaciones-de-seguridad-e-informes-de-vulnerabilidad
 subcategory: vONCJSxwN5qZiElOEtKkH
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad es parte de <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>.  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad es parte de [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh).  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
-<div class="alert alert-warning">
-  <p>Si requiere un análisis de tu informe de prueba de penetración por parte del equipo de Seguridad de VTEX, es necesario contar con VTEX Shield. Además, todas las pruebas de penetración deben <a href="#programar-prueba-de-penetracion">programarse previamente con VTEX</a>. Se considerará un intento de acción no autorizada cualquier prueba realizada de forma autónoma sin notificación previa a VTEX.</p>
-</div>
+>⚠️ Si requiere un análisis de tu informe de prueba de penetración por parte del equipo de Seguridad de VTEX, es necesario contar con VTEX Shield. Además, todas las pruebas de penetración deben [programarse previamente con VTEX](#programar-prueba-de-penetracion). Se considerará un intento de acción no autorizada cualquier prueba realizada de forma autónoma sin notificación previa a VTEX.
 
 VTEX evalúa rigurosamente los recursos de la plataforma, probando e identificando vulnerabilidades mediante escaneos y pruebas de penetración recurrentes. Las verificaciones de vulnerabilidad se realizan de forma continua.
 
@@ -40,9 +36,7 @@ Consulta en esta guía el procedimiento para programar una prueba de penetració
 
 ## Programar prueba de penetración
 
-<div class="alert alert-warning">
-  <p>Únicamente las tiendas con <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a> pueden programar pruebas de penetración y recibir una respuesta por parte del equipo de seguridad, que incluye acceso a un análisis detallado del informe de la prueba, como se describe en los procedimientos de esta guía.</p>
-</div>
+>⚠️ Únicamente las tiendas con [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) pueden programar pruebas de penetración y recibir una respuesta por parte del equipo de seguridad, que incluye acceso a un análisis detallado del informe de la prueba, como se describe en los procedimientos de esta guía.
 
 Para realizar una prueba de penetración en el entorno de tu tienda es necesario programar una fecha con VTEX, para la organización interna y la planificación por parte del equipo de Seguridad. Sigue las instrucciones a continuación:
 
@@ -58,9 +52,7 @@ Para realizar una prueba de penetración en el entorno de tu tienda es necesario
 6. Realiza la prueba en la fecha programada (sujeta a la autorización de VTEX).
 7. Envía un informe con los resultados en el mismo ticket al [soporte VTEX](https://help.vtex.com/es/support).
 
-   <div class="alert alert-warning">
-  <p>Para garantizar el cumplimiento del plazo de análisis por parte de VTEX, es obligatorio seguir las pautas descritas en <a href="#informes-de-pruebas-de-penetracion">Informes de pruebas de penetración</a>.</p>
-   </div>
+   >⚠️ Para garantizar el cumplimiento del plazo de análisis por parte de VTEX, es obligatorio seguir las pautas descritas en [Informes de pruebas de penetración](#informes-de-pruebas-de-penetracion).
 
    Designa a un miembro de tu equipo de seguridad como punto de contacto del equipo de seguridad de VTEX durante el proceso de análisis del informe de la prueba.
 
@@ -68,9 +60,7 @@ El equipo de seguridad de VTEX tiene como cometido realizar un análisis complet
 
 En un plazo de 10 días laborables desde la recepción del [informe](https://docs.google.com/document/d/1rQKXS8G2GWUwxxz9uwDFfFJLoYvkWD4L/edit#bookmark=id.17dp8vu), el equipo identificará los falsos positivos y reclasificará la gravedad de las amenazas identificadas según sea necesario, siguiendo las prácticas recomendadas de VTEX. Cada decisión de este proceso estará justificada detalladamente para garantizar su total transparencia y comprensión.
 
-<div class="alert alert-warning">
-  <p>Las tiendas que se están preparando para el go live y desean realizar una prueba de penetración también deben programarlo con anticipación. En este caso, es obligatorio enviar el informe con los resultados al <a href="https://help.vtex.com/es/support">soporte VTEX</a> por lo menos <strong>45 días</strong> antes de la fecha prevista para el go live. Durante este periodo, VTEX analizará el resultado y abordará cualquier vulnerabilidad detectada en el proceso.</p>
-</div>
+>⚠️ Las tiendas que se están preparando para el go live y desean realizar una prueba de penetración también deben programarlo con anticipación. En este caso, es obligatorio enviar el informe con los resultados al [soporte VTEX](https://help.vtex.com/es/support) por lo menos **45 días** antes de la fecha prevista para el go live. Durante este periodo, VTEX analizará el resultado y abordará cualquier vulnerabilidad detectada en el proceso.
 
 ### Informes de pruebas de penetración
 
@@ -118,9 +108,7 @@ Animamos a nuestros clientes a que informen responsablemente de cualquier vulner
 
 Quienes deseen informar una vulnerabilidad deben trabajar primero con sus propios equipos de seguridad y desarrollo para realizar una evaluación de seguridad y eliminar falsos positivos o problemas derivados de configuraciones personalizadas. Se analizarán únicamente los casos que sean compatibles con la [definición de vulnerabilidad](#definicion-de-vulnerabilidad).
 
-<div class="alert alert-warning">
-  <p>Consulta el documento <a href="https://vtex.com/mx-es/security/security-practices/">Prácticas de seguridad de VTEX</a> y nuestras <a href="https://help.vtex.com/es/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX">Preguntas frecuentes sobre seguridad</a> antes de informar cualquier vulnerabilidad. Estos documentos aclaran nuestros procesos y ayudan a eliminar los falsos positivos.</p>
-</div>
+>⚠️ Consulta el documento [Prácticas de seguridad de VTEX](https://vtex.com/mx-es/security/security-practices/) y nuestras [Preguntas frecuentes sobre seguridad](https://help.vtex.com/es/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX) antes de informar cualquier vulnerabilidad. Estos documentos aclaran nuestros procesos y ayudan a eliminar los falsos positivos.
 
 Después de este procedimiento, si existe una vulnerabilidad, sigue los pasos a continuación para reportarla:
 
@@ -129,9 +117,7 @@ Después de este procedimiento, si existe una vulnerabilidad, sigue los pasos a
 
     Las vulnerabilidades se deben informar de manera individual según el modelo establecido. Si encontraste más de una vulnerabilidad en tu prueba, rellena varios modelos y adjúntalos a tu ticket.
 
-  <div class="alert alert-warning">
-    <p>Toda la información solicitada debe rellenarse, dado que es importante para la evaluación. El equipo de Seguridad de VTEX no atenderá vulnerabilidades que no sigan el patrón establecido.</p>
-  </div>
+  >⚠️ Toda la información solicitada debe rellenarse, dado que es importante para la evaluación. El equipo de Seguridad de VTEX no atenderá vulnerabilidades que no sigan el patrón establecido.
 
 3. Abre un ticket para nuestro [Soporte](https://help.vtex.com/support?/cultureInfo=es-419) para registrar el aviso de vulnerabilidad de seguridad. No olvides adjuntar el modelo de comunicación de vulnerabilidades y rellena todos los datos solicitados en el ticket de soporte.
 4. Guarda tu número de ticket, ya que puedes necesitarlo en futuras comunicaciones.
diff --git a/docs/tutorials/es/pickup-points-for-subscription-orders-beta.md b/docs/tutorials/es/pickup-points-for-subscription-orders-beta.md
index 82873504e..6ff3a8f68 100644
--- a/docs/tutorials/es/pickup-points-for-subscription-orders-beta.md
+++ b/docs/tutorials/es/pickup-points-for-subscription-orders-beta.md
@@ -15,9 +15,7 @@ legacySlug: puntos-de-recogida-para-pedidos-de-suscripcion-beta
 subcategory: 3RmFd9bgAeRAVGeBd7XDUr
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad se encuentra en fase Beta, lo que significa que estamos trabajando para mejorarla. En caso de que tenga alguna duda, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en fase Beta, lo que significa que estamos trabajando para mejorarla. En caso de que tenga alguna duda, contacte a [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 Un punto de recogida es un lugar físico donde el cliente tiene la opción de recoger su pedido, en vez de recibirlo en casa. Un ejemplo de escenario para esta funcionalidad es la recogida en la tienda.
 
@@ -28,9 +26,7 @@ A continuación, vea lo que se requiere para habilitar esta funcionalidad.
 - [Requisitos](#requisitos)
 - [Eligir puntos de recogida](#eligir-puntos-de-recogida)
 
-<div class="alert alert-info">
-  <p>La funcionalidad de puntos de recogida solo está disponible para las cuentas que ya tienen acceso a <b>Checkout V6</b>.</p>
-</div>
+>ℹ️ La funcionalidad de puntos de recogida solo está disponible para las cuentas que ya tienen acceso a **Checkout V6**.
 
 ## Requisitos
 
diff --git a/docs/tutorials/es/pickup-points-for-subscription-orders.md b/docs/tutorials/es/pickup-points-for-subscription-orders.md
index d422511d2..a62224ee6 100644
--- a/docs/tutorials/es/pickup-points-for-subscription-orders.md
+++ b/docs/tutorials/es/pickup-points-for-subscription-orders.md
@@ -24,9 +24,7 @@ A continuación, vea lo que se requiere para habilitar esta funcionalidad.
 - [Requisitos](#requisitos)
 - [Eligir puntos de recogida](#eligir-puntos-de-recogida)
 
-<div class="alert alert-info">
-  <p>La funcionalidad de puntos de recogida solo está disponible para las cuentas que ya tienen acceso a <a href="https://help.vtex.com/es/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH">Checkout V6</a>.</p>
-</div>
+>ℹ️ La funcionalidad de puntos de recogida solo está disponible para las cuentas que ya tienen acceso a [Checkout V6](https://help.vtex.com/es/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH).
 
 ## Requisitos
 
diff --git a/docs/tutorials/es/pickup-points.md b/docs/tutorials/es/pickup-points.md
index c8cc678a0..79ce7593b 100644
--- a/docs/tutorials/es/pickup-points.md
+++ b/docs/tutorials/es/pickup-points.md
@@ -76,7 +76,7 @@ VTEX considera que el punto de recogida es una forma de envío. Es por eso que l
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Checkout**, o escribe *Checkout* en la barra de búsqueda en la parte superior de la página.  
     - Paso 2: Selecciona la configuración utilizada en la tienda y haz clic en el ícono <i class="fas fa-cog"></i>.
     - Paso 3: Haz clic en la pestaña **Checkout** en la barra superior.
-    - Paso 4: Selecciona el botón <i class="fas fa-toggle-on"></i> del campo **Dirección de la factura para recogida en la tienda**. ![NFpontoretiradaES](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/c81afd5e90d05deec1684dba401f569e/NFpontoretiradaES.png)<div class="alert alert-warning">La opción de <b>Dirección en la factura para recogida en la tienda</b> debe estar habilitada en todas las tiendas en Brasil, ya que es requisito que la factura emitida contenga la información de la dirección del cliente, incluso si la opción de entrega de el pedido está en el punto de recogida. La dirección ingresada por el cliente se registrará en el campo `invoiceData` del <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - Paso 4: Selecciona el botón <i class="fas fa-toggle-on"></i> del campo **Dirección de la factura para recogida en la tienda**. ![NFpontoretiradaES](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/c81afd5e90d05deec1684dba401f569e/NFpontoretiradaES.png)>⚠️ La opción de **Dirección en la factura para recogida en la tienda** debe estar habilitada en todas las tiendas en Brasil, ya que es requisito que la factura emitida contenga la información de la dirección del cliente, incluso si la opción de entrega de el pedido está en el punto de recogida. La dirección ingresada por el cliente se registrará en el campo `invoiceData` del [orderForm](https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata).
 
 6. Para configurar la cantidad de puntos de recogida que se muestran en el checkout:
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Envío > Configuración**, o escribe *Envío* en la barra de búsqueda en la parte superior de la página, y haga clic en *Configuración de la tienda / Envío*.    
diff --git a/docs/tutorials/es/pipedrive-suiteshare.md b/docs/tutorials/es/pipedrive-suiteshare.md
index c680d9ab8..fac894460 100644
--- a/docs/tutorials/es/pipedrive-suiteshare.md
+++ b/docs/tutorials/es/pipedrive-suiteshare.md
@@ -15,7 +15,5 @@ legacySlug: pipedrive
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
 
diff --git a/docs/tutorials/es/piperun-suiteshare.md b/docs/tutorials/es/piperun-suiteshare.md
index 63fc55de9..000a4710f 100644
--- a/docs/tutorials/es/piperun-suiteshare.md
+++ b/docs/tutorials/es/piperun-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: piperun-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/planner-actions-on-releases-beta.md b/docs/tutorials/es/planner-actions-on-releases-beta.md
index abf111571..1d3f6fca3 100644
--- a/docs/tutorials/es/planner-actions-on-releases-beta.md
+++ b/docs/tutorials/es/planner-actions-on-releases-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-acciones-en-los-lanzamientos-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>El <strong>Releases</strong> se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ El **Releases** se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan [FastStore](https://www.faststore.dev/).
 
 El módulo **Releases** te permite gestionar [releases](https://help.vtex.com/es/tutorial/planner-concepto-de-release-beta--4pWhQTXG0aIIsi2TYxxRkZ) para que puedas coordinar la creación, programación y publicación de los cambios en tu tienda. Un release es un cambio o un grupo de cambios que pueden publicarse en conjunto.
 
@@ -36,9 +34,7 @@ Cada página muestra una vista de los releases y te permite realizar distintas a
 * [Publicar un release](#publicar-un-release)
 * [Eliminar un release](#eliminar-un-release)
 
-<div class="alert alert-warning">
-  <p>En la etapa Beta, los releases deben estar relacionados al <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a> porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el <strong>Releases</strong>, se debe configurar el CMS tal como se describe en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ En la etapa Beta, los releases deben estar relacionados al [CMS](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el **Releases**, se debe configurar el CMS tal como se describe en [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Crear un release
 
@@ -113,9 +109,7 @@ Para publicar un release y hacer visibles los cambios en el _storefront_ de la t
 
 Todos los [status de releases](https://help.vtex.com/es/tutorial/planner-concepto-de-release-beta--4pWhQTXG0aIIsi2TYxxRkZ#status-de-los-releases) permiten eliminar un release, es decir, que el release se elimine permanentemente.
 
-<div class="alert alert-info">
-  <p>Si en lugar de eliminar un release quieres archivarlo, debes quitar el release de la publicación. De esta manera, no se eliminará y podrás volver a publicarlo en cualquier momento.</p>
-</div>
+>ℹ️ Si en lugar de eliminar un release quieres archivarlo, debes quitar el release de la publicación. De esta manera, no se eliminará y podrás volver a publicarlo en cualquier momento.
 
 Cuando se elimina un release que está en el status `Publicado`, los cambios que agrupaba se mantienen en el _storefront_ de la tienda. Lo único que deja de existir es el release que agrupaba los cambios.
 
diff --git a/docs/tutorials/es/planner-calendar-page-beta.md b/docs/tutorials/es/planner-calendar-page-beta.md
index 56355e857..9fe3ef089 100644
--- a/docs/tutorials/es/planner-calendar-page-beta.md
+++ b/docs/tutorials/es/planner-calendar-page-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-pagina-calendario-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>El <strong>Releases</strong>se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ El **Releases**se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan [FastStore](https://www.faststore.dev/).
 
 El módulo **Releases** te permite [gestionar tus releases](https://help.vtex.com/es/tutorial/planner-acciones-en-los-releases-beta--1zsomdifPEQkdV6RW93JyW) para que puedas coordinar la creación, programación y publicación de los cambios en tu tienda.
 
@@ -30,9 +28,7 @@ Existen tres maneras de ver la página **Calendario**:
 
 El **Calendario** muestra solamente [releases programados](https://help.vtex.com/es/tutorial/planner-acciones-en-los-releases-beta--1zsomdifPEQkdV6RW93JyW#programar). Para ver todos tus releases, ingresa a la página [Releases](https://help.vtex.com/es/v4/docs/planner-pagina-de-releases--1tQNCNwoMvxV4EoizajqJw).
 
-<div class="alert alert-warning">
-  <p>En la etapa Beta, los releases deben estar relacionados al <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a> porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el <strong>Releases</strong>, se debe configurar el CMS tal como se describe en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ En la etapa Beta, los releases deben estar relacionados al [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el **Releases**, se debe configurar el CMS tal como se describe en [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Vista por mes
 
diff --git a/docs/tutorials/es/planner-release-concept-beta.md b/docs/tutorials/es/planner-release-concept-beta.md
index 6b32f9c83..1d3fb1553 100644
--- a/docs/tutorials/es/planner-release-concept-beta.md
+++ b/docs/tutorials/es/planner-release-concept-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-concepto-de-lanzamiento-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>El <strong>Releases</strong> se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ El **Releases** se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan [FastStore](https://www.faststore.dev/).
 
 La gestión de una operación de _ecommerce_ exige que el _retailer_ haga una serie de actualizaciones en su tienda que, muchas veces, suelen relacionarse entre sí. Por ejemplo, una campaña publicitaria en la cual se deben configurar distintos elementos del _storefront_.
 
@@ -30,9 +28,7 @@ Un release es un cambio o un grupo de cambios que pueden publicarse en conjunto.
 * Mayor control al probar y revisar los cambios antes de publicarlos.
 * Facilidad para programar o eliminar grupos de cambios.
 
-<div class="alert alert-warning">
-  <p>En la etapa Beta, los releases deben estar relacionados al <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a> porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el <strong>Releases</strong>, se debe configurar el CMS tal como se describe en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ En la etapa Beta, los releases deben estar relacionados al [CMS](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el **Releases**, se debe configurar el CMS tal como se describe en [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 Se puede acceder a esta funcionalidad a través del menú de navegación del **Releases** en el Admin VTEX, donde encontrarás las siguientes páginas:
 
diff --git a/docs/tutorials/es/planner-releases-page-beta.md b/docs/tutorials/es/planner-releases-page-beta.md
index 45307a25a..713b5ce6a 100644
--- a/docs/tutorials/es/planner-releases-page-beta.md
+++ b/docs/tutorials/es/planner-releases-page-beta.md
@@ -16,9 +16,7 @@ subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
 
-<div class="alert alert-info">
-  <p>El <strong>Releases</strong>se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ El **Releases**se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan [FastStore](https://www.faststore.dev/).
 
 El módulo **Releases** te permite [gestionar tus releases](https://help.vtex.com/es/tutorial/planner-concepto-de-release-beta--4pWhQTXG0aIIsi2TYxxRkZ) para que puedas coordinar la creación, programación y publicación de los cambios en tu tienda.
 
@@ -28,9 +26,7 @@ En la página **Releases**, podrás visualizar una lista con todos los releases
 
 El orden de los releases programados se basa en la fecha de publicación: cuanto más lejano en el futuro sea un release, antes aparecerá en la lista; y cuanto más distante en el pasado, más hacia el final aparecerá.
 
-<div class="alert alert-warning">
-  <p>En la etapa Beta, los releases deben estar relacionados al <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a> porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el <strong>Releases</strong>, se debe configurar el CMS tal como se describe en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ En la etapa Beta, los releases deben estar relacionados al [CMS](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el **Releases**, se debe configurar el CMS tal como se describe en [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Vista en lista
 
diff --git a/docs/tutorials/es/predefined-roles.md b/docs/tutorials/es/predefined-roles.md
index b3ba518c1..cdaaa43f7 100644
--- a/docs/tutorials/es/predefined-roles.md
+++ b/docs/tutorials/es/predefined-roles.md
@@ -19,9 +19,7 @@ subcategory: 1HSqkejwuYcQSMC400uY84
 
 En este documento, se enumeran roles que están predefinidos para las nuevas tiendas VTEX y sus respectivos recursos. Para acceder a ellos directamente, utilice la lista a continuación.
 
-<div class="alert alert-info">
-<p>Para obtener más información sobre cada recurso listado en los perfiles a continuación, consulte el artículo <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">Recursos del License Manager</a>.</p>
-</div>
+>ℹ️ Para obtener más información sobre cada recurso listado en los perfiles a continuación, consulte el artículo [Recursos del License Manager](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
 
 * [Admin - Start page only](#admin-start-page-only)
 * [Checkout Admin](#checkout-admin)
@@ -76,8 +74,7 @@ El recurso __Assisted Sales__ hace que el usuario sea redirigido automáticament
 
 Por lo tanto, recomendamos utilizar dos cuentas separadas (con correos electrónicos separados) para los usuarios de televenta: una cuenta para el rol de __Call center operator__ (con los recursos *Assisted Sales* y *View order*) y otra cuenta para realizar operaciones en Admin, si es necesario.
 
-<div class="alert alert-warning">Al crear un <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">rol</a>, evita incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televentas junto con otros recursos. De lo contrario, puede que el rol no funcione de forma esperada.
-</div>
+>⚠️ Al crear un [rol](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#), evita incluir [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) de televentas junto con otros recursos. De lo contrario, puede que el rol no funcione de forma esperada.
 
 Tabla de recursos:
 
@@ -144,9 +141,7 @@ Tabla de recursos:
 
 ## Sales App - Sales Associate
 
-<div class="alert alert-warning">
-  <p>Los vendedores registrados en Sales App no tienen acceso a VTEX Admin, sólo a Sales App.</p>
-</div>
+>⚠️ Los vendedores registrados en Sales App no tienen acceso a VTEX Admin, sólo a Sales App.
 
 Tabla de recursos:
 
diff --git a/docs/tutorials/es/price-divergence-rule.md b/docs/tutorials/es/price-divergence-rule.md
index 2597b77da..30fd3f4c0 100644
--- a/docs/tutorials/es/price-divergence-rule.md
+++ b/docs/tutorials/es/price-divergence-rule.md
@@ -19,9 +19,7 @@ Cuando un _seller_ vende en un _marketplace_, a veces hay una diferencia entre e
 
 Para optimizar el procesamiento de los pedidos con errores de diferencia de precios, existe el flujo de Autorización de pedidos, en el que el _seller_ puede [configurar una regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe). En el Admin VTEX, accede a **Configuración de la tienda > Pedidos > Autorización de pedidos**, o escribe **Autorización de pedidos** en la barra de búsqueda en la parte superior de la página.
 
-<div class="alert alert-warning">
-Una vez que el seller ha creado la regla de Divergencia de precios, esta se aplica a todos los marketplaces.
-</div>
+>⚠️ Una vez que el seller ha creado la regla de Divergencia de precios, esta se aplica a todos los marketplaces.
 
 La regla de Divergencia de precios se compone de una o varias reglas de autorización de pedidos. Cada regla de autorización corresponde a un rango porcentual del precio del pedido y puede variar del 0% al 100%. Se debe asociar una de las tres acciones a cada regla de autorización:
 
@@ -33,9 +31,7 @@ La regla de Divergencia de precios se compone de una o varias reglas de autoriza
 
 Cuando no se ha [configurado la regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), los pedidos con errores de divergencia de precios se aprueban automáticamente. Esto se aplica a los _marketplaces_ VTEX, a los _marketplaces_ externos y a los conectores certificados (_partners_), pero no a los [conectores nativos](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex).
 
-<div class="alert alert-warning">
-Cuando un seller está integrado con un conector nativo, como Mercado Libre, pero no ha configurado una regla de Divergencia de precios, los pedidos con error por diferencia de valores quedan pendientes hasta que se cree la regla. Puedes seguirlos en tu Admin VTEX, en <b>Marketplace > Conexiones > Pedidos</b>.
-</div>
+>⚠️ Cuando un seller está integrado con un conector nativo, como Mercado Libre, pero no ha configurado una regla de Divergencia de precios, los pedidos con error por diferencia de valores quedan pendientes hasta que se cree la regla. Puedes seguirlos en tu Admin VTEX, en **Marketplace > Conexiones > Pedidos**.
 
 Tras la creación de la regla de Divergencia de precios, los pedidos de integraciones con conectores nativos que presentan una diferencia de valores se mostrarán en la página [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi).
 
diff --git a/docs/tutorials/es/price-divergence-rules-beta.md b/docs/tutorials/es/price-divergence-rules-beta.md
index 39305bd8c..e5a0da898 100644
--- a/docs/tutorials/es/price-divergence-rules-beta.md
+++ b/docs/tutorials/es/price-divergence-rules-beta.md
@@ -15,9 +15,7 @@ legacySlug: reglas-de-autorizacion-en-divergencia-de-valores-para-sellers
 subcategory: 4ZBiXqnPntLbsijZ0djFcD
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad está en versión Beta, lo que significa que estamos trabajando para mejorarla. Si tiene alguna pregunta, póngase en contacto con <a href="https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad está en versión Beta, lo que significa que estamos trabajando para mejorarla. Si tiene alguna pregunta, póngase en contacto con [nuestro Soporte](https://support.vtex.com/hc/es-419/requests).
 
 Las integraciones entre los sellers VTEX y los [conectores nativos](https://help.vtex.com/es/tutorial/integrando-com-marketplace--tutorials_402#integrado-con-un-conector-nativo-vtex) pueden presentar divergencias en los precios configurados en VTEX y lo que se exhibe en el estante del marketplace. Esto puede generar errores en el OMS.
 
@@ -33,9 +31,7 @@ Los pedidos se deben gestionar y aprobar manualmente a través del OMS o por [VT
 
 Una regla se configura automáticamente con el porcentaje de divergencia de 0% a 30% para `Negar automáticamente` los pedidos en su Admin VTEX. Además, se puede alterar o inclusive crear más de una regla al realizar la configuración.
 
-<div class="alert alert-info">
-Una vez que haya configurado el mecanismo de regla de autorización (Beta), ya no tendrá que configurar el campo Divergencia de valores en la integración del marketplace. Si ya configuró el campo en la integración, la configuración realizada ya no será válida.
-</div>
+>ℹ️ Una vez que haya configurado el mecanismo de regla de autorización (Beta), ya no tendrá que configurar el campo Divergencia de valores en la integración del marketplace. Si ya configuró el campo en la integración, la configuración realizada ya no será válida.
 
 ## Configuración de una regla de autorización (Beta)
 
@@ -86,10 +82,8 @@ Hay dos formas de autorizar los pedidos que tienen el status `Esperando autoriza
 - [Autorizar manualmente en el OMS](#autorizacion-manual-en-el-oms)
 - [Autorizar por VTEX DO](#autorizacion-por-vtex-do)
 
-<div class="alert alert-warning">
-Debe tener permiso del propietario de la cuenta para autorizar los pedidos, de lo contrario aparecerá el siguiente mensaje en la pantalla: 
-«Usted aún no posee reglas de autorización. Por lo tanto, todos los casos de divergencia son negados automáticamente».
-</div>
+>⚠️ Debe tener permiso del propietario de la cuenta para autorizar los pedidos, de lo contrario aparecerá el siguiente mensaje en la pantalla: 
+> «Usted aún no posee reglas de autorización. Por lo tanto, todos los casos de divergencia son negados automáticamente».
 
 ### Autorización manual en el OMS
 
diff --git a/docs/tutorials/es/product-list.md b/docs/tutorials/es/product-list.md
index 3a9a6c353..b9d77652f 100644
--- a/docs/tutorials/es/product-list.md
+++ b/docs/tutorials/es/product-list.md
@@ -30,7 +30,7 @@ Desde la lista de productos puede llevar a cabo varias acciones:
 
 Al hacer clic en el botón **CREAR PRODUCTO**, se abrirá la página para registrar un nuevo producto en el catálogo. Consulte el artículo [Cómo crear un producto](https://help.vtex.com/es/tutorial/como-crear-un-producto-beta--671zAWe0B9eCikzDu7kB1G) para obtener información sobre cómo realizar este procedimiento.
 
-<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+>⚠️ El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.
 
 ## Buscar productos
 
diff --git a/docs/tutorials/es/product-registration-fields.md b/docs/tutorials/es/product-registration-fields.md
index 9e486832b..de7258b97 100644
--- a/docs/tutorials/es/product-registration-fields.md
+++ b/docs/tutorials/es/product-registration-fields.md
@@ -25,15 +25,16 @@ __Palabras Sustitutas:__ sinónimos de términos relacionados al nombre dado par
 
 __TextLink:__ utilizado para crear la URL del producto. Campo obligatorio. Para más información, consulte el artículo [¿Cómo es montada la URL de producto?](https://help.vtex.com/es/tutorial/como-es-montada-la-url-de-producto--frequentlyAskedQuestions_368).
 
-<div class="alert alert-danger">
-  <p>Al rellenar el <b>textLink</b> del producto, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX.  Consulta la lista de palabras reservadas a continuación.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Al rellenar el **textLink** del producto, evita utilizar las siguientes palabras reservadas, ya que esto puede perjudicar el rendimiento de tu tienda e interferir con el funcionamiento de las páginas del Admin VTEX.  Consulta la lista de palabras reservadas a continuación.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 __Título de la página (Metatag Title):__ texto que queda en la pestaña del navegador y corresponde al título de la página del producto. Este campo es importante para SEO.
 
@@ -73,9 +74,7 @@ Vea cómo crear las [especificaciones de sus productos](https://help.vtex.com/es
 
 Si ha creado algún campo de producto obligatorio, el producto sólo podrá activarse después de haber rellenado esta especificación.
 
-<div class="alert alert-info">
-Si su producto no aparece en el sitio web de su tienda después del registro, consulte el artículo <a href="https://help.vtex.com/es/faq/por-que-el-producto-no-aparece-en-el-sitio--frequentlyAskedQuestions_382">¿Por qué el producto no aparece en el sitio?</a> para entender cómo resolver este problema.
-</div>
+>ℹ️ Si su producto no aparece en el sitio web de su tienda después del registro, consulte el artículo [¿Por qué el producto no aparece en el sitio?](https://help.vtex.com/es/faq/por-que-el-producto-no-aparece-en-el-sitio--frequentlyAskedQuestions_382) para entender cómo resolver este problema.
 
 ### Más información
 - [Productos - Definición de concepto](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru)
diff --git a/docs/tutorials/es/products-and-skus-beta.md b/docs/tutorials/es/products-and-skus-beta.md
index f840589ec..e75891e6d 100644
--- a/docs/tutorials/es/products-and-skus-beta.md
+++ b/docs/tutorials/es/products-and-skus-beta.md
@@ -15,17 +15,13 @@ legacySlug: productos-y-skus-beta
 subcategory: 6XPsLadoT3moZ7eTduCg3c
 ---
 
-<div class="alert alert-info">
-<p>Esta funcionalidad se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarla. Si tienes alguna duda, ponte en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarla. Si tienes alguna duda, ponte en contacto con [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 La página **Productos y SKUs** permite ver y gestionar toda la lista de productos registrados en la tienda, incluyendo la información de los SKU, fecha de actualización y status. Para acceder a la página, ve a **Catálogo > Productos y SKUs**. 
 
 ![products-skus-es](https://images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/1d07f47ff5411ae7b264cd9c74fbb21a/products-skus-es.png)
 
-<div class="alert alert-info">
-  <p>Esta página solo está disponible para las tiendas que operan con el <a href="https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">nuevo Admin VTEX</a>. Para acceder a esta página y formar parte de una nueva experiencia, únete al <a href="https://content.vtex.com/participe-do-programa-beta-es/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> del nuevo Admin VTEX.</p>
-</div>
+>ℹ️ Esta página solo está disponible para las tiendas que operan con el [nuevo Admin VTEX](https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa). Para acceder a esta página y formar parte de una nueva experiencia, únete al [programa Beta](https://content.vtex.com/participe-do-programa-beta-es/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta) del nuevo Admin VTEX.
 
 La página te permite realizar las siguientes acciones:
 
@@ -83,9 +79,7 @@ Puedes filtrar la lista de productos según tus necesidades. Puedes utilizar los
 
 Selecciona los filtros deseados y haz clic en `Aplicar` para filtrar los productos. Para cancelar la selección, haz clic en `Limpiar`.
 
-<div class="alert alert-warning">
-  <p>No es posible filtrar productos por <a href="https://help.vtex.com/es/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w">seller</a> o fecha de preventa en esta versión del Catálogo.</p>
-</div>
+>⚠️ No es posible filtrar productos por [seller](https://help.vtex.com/es/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) o fecha de preventa en esta versión del Catálogo.
 
 ## Monitorear el status de los productos
 
diff --git a/docs/tutorials/es/promotions-beta.md b/docs/tutorials/es/promotions-beta.md
index 8e7812ce7..b7d7b90bf 100644
--- a/docs/tutorials/es/promotions-beta.md
+++ b/docs/tutorials/es/promotions-beta.md
@@ -15,9 +15,7 @@ legacySlug: promociones-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class="alert alert-danger">
-<p>Esta funcionalidad será descontinuada el 16 de mayo de 2022. Si tiene alguna duda, póngase en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>❗ Esta funcionalidad será descontinuada el 16 de mayo de 2022. Si tiene alguna duda, póngase en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
 
 La plataforma VTEX proporciona una forma optimizada y práctica de registrar varios tipos de promociones que se adaptan a diferentes escenarios. A través de una interfaz centralizada para la gestión de promociones, su tienda puede ofrecer más beneficios centrados en atraer y retener a los clientes.
 
@@ -98,9 +96,7 @@ Este efecto genera un descuento total sobre el valor del producto definido como
 - __SKU__: opción que permite seleccionar el SKU que será el regalo de la compra.
 - __Cantidad máxima por compra__: opción que permite seleccionar la cantidad máxima de regalos que una compra puede recibir.
 
-<div class="alert alert-warning">
-  <p>El producto de <b>Regalo</b> también debe tener un precio registrado, aunque se entrega gratuitamente al cliente.</p>
-</div>
+>⚠️ El producto de **Regalo** también debe tener un precio registrado, aunque se entrega gratuitamente al cliente.
 
 #### Envío
 - __Tipo de descuento__
@@ -126,9 +122,7 @@ Este efecto genera un descuento total sobre el valor del producto definido como
   - __UTM Source__.
   - __Rango de códigos postales__.
 
-<div class="alert alert-info">
-<p>Si desea vincular un <a href= "https://help.vtex.com/es/tutorial/crear-cupon-de-descuento--tutorials_319">cupón existente</a> a la nueva promoción, debe seleccionar las opciones UTM Campaign y UTM Source e ingresar los códigos del cupón.</p>
-</div>
+>ℹ️ Si desea vincular un <a href= "https://help.vtex.com/es/tutorial/crear-cupon-de-descuento--tutorials_319">cupón existente</a> a la nueva promoción, debe seleccionar las opciones UTM Campaign y UTM Source e ingresar los códigos del cupón.
 
 ### Cupones
 Si desea crear un nuevo cupón asociado a la promoción, haga clic en __NUEVO CUPÓN__ y rellene los siguientes campos:
@@ -141,15 +135,11 @@ Al hacer clic en __Opciones Avanzadas__, existe la posibilidad de configurar un
 
 - __Limitar el uso__: opción que limita la cantidad de veces que se puede utilizar el cupón.
 
-<div class="alert alert-warning">
-  <p>Para guardar el nuevo cupón, es necesario hacer clic en el botón <b>OK</b>. Si se cierra la ventana sin esta confirmación, no se creará el cupón.</p>
-</div>
+>⚠️ Para guardar el nuevo cupón, es necesario hacer clic en el botón **OK**. Si se cierra la ventana sin esta confirmación, no se creará el cupón.
 
 Al crear un nuevo cupón para la nueva promoción, este se mostrará también en la pestaña __Cupones__ del módulo __Tasas y Promociones__. Además, sus condiciones de UTM Source y/o UTM Campaign se vincularán automáticamente a la nueva promoción en el filtro __Clientes Específicos__.
 
-<div class="alert alert-warning">
-<p>Si se cambian las condiciones de UTM Source y UTM Campaign en la configuración del filtro <b>Clientes Específicos</b> después de haber creado el cupón mediante este flujo, el cupón se eliminará.</p>
-</div>
+>⚠️ Si se cambian las condiciones de UTM Source y UTM Campaign en la configuración del filtro **Clientes Específicos** después de haber creado el cupón mediante este flujo, el cupón se eliminará.
 
 ### Restricciones
 - __Limitar el uso en su tienda__: limita la cantidad de veces que la promoción se puede aplicar a la tienda.
diff --git a/docs/tutorials/es/promotions-simulator-beta.md b/docs/tutorials/es/promotions-simulator-beta.md
index ee161192f..f2cf7ceb2 100644
--- a/docs/tutorials/es/promotions-simulator-beta.md
+++ b/docs/tutorials/es/promotions-simulator-beta.md
@@ -15,9 +15,7 @@ legacySlug: simulador-de-promociones-beta
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-<div class="alert alert-warning">
-  <p>Los usuarios deben tener un <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol</a> con permisos para ver el módulo <strong>Promociones</strong> en el Admin VTEX para poder acceder al <strong>Simulador de promociones</strong>.</p>
-</div>
+>⚠️ Los usuarios deben tener un [rol](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) con permisos para ver el módulo **Promociones** en el Admin VTEX para poder acceder al **Simulador de promociones**.
 
 El **Simulador de promociones** es una herramienta que permite ver las promociones creadas en tu tienda VTEX que se aplicaron al carrito y sus condiciones de activación. También puedes probar la aplicación de promociones antes de activarlas, incluyendo promociones inactivas y programadas.
 
@@ -48,9 +46,7 @@ La interfaz del **Simulador de promociones** presenta la siguiente información:
 | **Total** | Precio total que se cobrará por el producto, considerando los descuentos de la promoción y la cantidad de ítems. |
 | **Descuento** | Status del descuento en el carrito, el cual puede ser: `Aplicado` o `No aplicado`. El status `Aplicado` indica que al menos una promoción fue aplicada al producto. |
 
-<div class="alert alert-info">
-  <p>En la esquina derecha de la pantalla, encontrarás un botón de megáfono que te permitirá enviar tu opinión sobre tu experiencia usando el <strong>Simulador de promociones</strong>.</p>
-</div>
+>ℹ️ En la esquina derecha de la pantalla, encontrarás un botón de megáfono que te permitirá enviar tu opinión sobre tu experiencia usando el **Simulador de promociones**.
 
 ### Actualizar el simulador
 
@@ -90,9 +86,7 @@ Para ejecutar una simulación, sigue estos pasos:
 
    Verás el resultado de la simulación a partir de las promociones seleccionadas. Para ver si las promociones probadas se aplicaron a los ítems del carrito en la simulación, fíjate en el status de la columna **Descuento** o haz clic en el producto.
 
-<div class="alert alert-info">
-  <p>Se pueden aplicar promociones en productos que ya tienen una promoción activa. A pesar del conflicto que se genera entre las promociones, el sistema de VTEX siempre elegirá la promoción más beneficiosa para los clientes de tu tienda, tomando en consideración el precio total de los ítems o el envío.</p>
-</div>
+>ℹ️ Se pueden aplicar promociones en productos que ya tienen una promoción activa. A pesar del conflicto que se genera entre las promociones, el sistema de VTEX siempre elegirá la promoción más beneficiosa para los clientes de tu tienda, tomando en consideración el precio total de los ítems o el envío.
 
 ### Más información
 
diff --git a/docs/tutorials/es/promotions-simulator.md b/docs/tutorials/es/promotions-simulator.md
index fa37591d1..9113f6261 100644
--- a/docs/tutorials/es/promotions-simulator.md
+++ b/docs/tutorials/es/promotions-simulator.md
@@ -15,9 +15,7 @@ legacySlug: simulador-de-promocoes
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class="alert alert-info">
-<p>Este módulo está en versión beta, lo que significa que estamos trabajando para mejorarlo. Si tiene alguna duda, póngase en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Este módulo está en versión beta, lo que significa que estamos trabajando para mejorarlo. Si tiene alguna duda, póngase en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
 
 El **Simulador de promociones** te permite ver las promociones aplicadas a tu carrito y sus condiciones. Con varias posibilidades de configuración de las promociones, es importante tener visibilidad sobre la [competencia](https://help.vtex.com/es/tutorial/entendiendo-la-competencia-de-las-promociones-2--tutorials_2270) y la [acumulación](https://help.vtex.com/es/tutorial/entendiendo-la-competencia-de-las-promociones-2--tutorials_2270#acumulacion) de las promociones durante la compra y las causas de la activación de las promociones.
 
diff --git a/docs/tutorials/es/qr-code-suiteshare.md b/docs/tutorials/es/qr-code-suiteshare.md
index 13d3f273a..48d8f5e08 100644
--- a/docs/tutorials/es/qr-code-suiteshare.md
+++ b/docs/tutorials/es/qr-code-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: qr-code-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/querying-data-on-master-data.md b/docs/tutorials/es/querying-data-on-master-data.md
index 5e0e6014a..9976767f0 100644
--- a/docs/tutorials/es/querying-data-on-master-data.md
+++ b/docs/tutorials/es/querying-data-on-master-data.md
@@ -15,4 +15,4 @@ legacySlug: consultando-datos-en-el-master-data
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/rdstation-crm-suiteshare.md b/docs/tutorials/es/rdstation-crm-suiteshare.md
index 1a4ac56e8..f112232e8 100644
--- a/docs/tutorials/es/rdstation-crm-suiteshare.md
+++ b/docs/tutorials/es/rdstation-crm-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: rdstation-crm
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/rdstation-suiteshare.md b/docs/tutorials/es/rdstation-suiteshare.md
index 0d5460874..b8436bc44 100644
--- a/docs/tutorials/es/rdstation-suiteshare.md
+++ b/docs/tutorials/es/rdstation-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: rdstation
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/received-skus-beta.md b/docs/tutorials/es/received-skus-beta.md
index 92a1da972..b70e7aa00 100644
--- a/docs/tutorials/es/received-skus-beta.md
+++ b/docs/tutorials/es/received-skus-beta.md
@@ -56,9 +56,7 @@ Para consultar todas las especificaciones de un producto, haz clic en el nombre
 
 En la pestaña __Problemas__ están disponibles todos los anuncios que aún no se aprobaron debido a problemas que requieren corrección por parte del seller. Los filtros, acciones y campos de identificación disponibles en la pestaña **[Pendientes](#pendientes)** son similares a los de la pestaña Problemas.  
 
-<div class="alert alert-info">
-La acción de solicitar corrección no está disponible en la pestaña <b>Problemas.</b>
-</div>  
+>ℹ️ La acción de solicitar corrección no está disponible en la pestaña **Problemas.**  
 
 Para identificar el problema de un anuncio solo hay que hacer clic en el nombre del producto deseado. Se mostrará una nueva ventana con la información del producto, el mensaje de error y el revisor del anuncio.  
 
@@ -86,9 +84,7 @@ Cada fila de la lista representa un producto con la siguiente información:
 - __Seller:__ nombre del seller que envió el anuncio.  
 - __Fecha de envío:__ muestra la fecha en que se envió el anuncio al marketplace.  
 
-<div class="alert alert-info">
-Los anuncios aquí listados están siendo evaluados por Matcher y por Offer Quality o autoApprove, en caso de que se hayan configurado. Tras la evaluación, el anuncio puede pasar a las pestañas <b>Pendientes, Problemas, Aprobados o Bloqueados</b>, dependiendo del cumplimiento de los requisitos establecidos.
-</div>  
+>ℹ️ Los anuncios aquí listados están siendo evaluados por Matcher y por Offer Quality o autoApprove, en caso de que se hayan configurado. Tras la evaluación, el anuncio puede pasar a las pestañas **Pendientes, Problemas, Aprobados o Bloqueados**, dependiendo del cumplimiento de los requisitos establecidos.  
 
 ### Bloqueados
 
@@ -127,16 +123,12 @@ En este caso, los ítems se ordenarán de forma ascendente o descendente al hace
 
 Todos los SKU que se muestran en la lista ya están disponibles para catalogación. No obstante, se recomienda realizar el [mapeo de categorías y marcas](https://help.vtex.com/es/tutorial/mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta--6NU8LwR6i0tTb8nk30bnbE) antes de este paso para agilizar el proceso de catalogación.  
 
-<div class="alert alert-warning">
-Los anuncios de la pestaña Pendientes permanecen disponibles solamente durante 30 días. Pasado este periodo, expiran automáticamente y el seller tendrá que volver a enviarlos.
-</div>
+>⚠️ Los anuncios de la pestaña Pendientes permanecen disponibles solamente durante 30 días. Pasado este periodo, expiran automáticamente y el seller tendrá que volver a enviarlos.
 
 ### Opciones de catalogación  
 
 Para catalogar un anuncio, accede a la página __SKUs recibidos__ en el Admin VTEX haciendo clic en __Marketplace > SKUs recibidos__ o ingresando __SKUs recibidos__ en la barra de búsqueda del Admin.  
-<div class="alert alert-info">
-Todos los anuncios de la pestaña Pendientes se pueden catalogar individualmente o en masa.
-</div>
+>ℹ️ Todos los anuncios de la pestaña Pendientes se pueden catalogar individualmente o en masa.
 
 Las acciones disponibles para la catalogación son:  
 
@@ -147,9 +139,7 @@ Las acciones disponibles para la catalogación son:
 3. Completa los campos __Categoría__ y __Marca__ para cada producto. Si el mapeo ya se ha realizado previamente, estos campos ya estarán completados.  
 4. Haz clic en `Aprobar`.  
 
-<div class="alert alert-info">
-Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
-</div>
+>ℹ️ Esta acción puede realizarse en las pestañas **Pendientes** y **Problemas**.
 
 ![skus-recibidos-crear-nuevo-producto-es](https://images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/4b686bea24c2df091c8739ecc398a645/skus-recibidos-crear-nuevo-producto-es.png)
 
@@ -166,9 +156,7 @@ Imagina el siguiente escenario: el marketplace ya tiene el SKU Camisa blanca en
 
 Al crear una nueva asociación, las nuevas tallas se agrupan con las demás que ya estaban previamente registradas. Por lo tanto, el producto estará disponible en las tallas XS, S, M, L y XL.  
 
-<div class="alert alert-info">
-Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>.
-</div>
+>ℹ️ Esta acción puede realizarse en las pestañas **Pendientes** y **Problemas**.
 
 ![skus-recibidos-vincular-al-producto-es](https://images.ctfassets.net/alneenqid6w5/2fAWptfykAdJ3UTDSCpNhW/7bf8dee7e2b09fa4c36aefa485a461c8/skus-recibidos-vincular-al-producto-es.png)
 
@@ -200,9 +188,7 @@ Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas<
 
 Cuando el marketplace bloquea un SKU, significa que la próxima vez que el seller envíe sus productos, aquellos que hayan sido bloqueados ya no serán incluidos entre los enviados. Es posible desbloquear un SKU a través de la API REST, si el marketplace desea volver a recibirlo como sugerencia del seller. Para más información sobre la aprobación de SKU, consulta nuestra documentación [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).  
 
-<div class="alert alert-info">
-Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas</b>. Los anuncios bloqueados se mostrarán en la pestaña <b>Bloqueados</b>.
-</div>
+>ℹ️ Esta acción puede realizarse en las pestañas **Pendientes** y **Problemas**. Los anuncios bloqueados se mostrarán en la pestaña **Bloqueados**.
 
 ![skus-recibidos-rechazar-y-bloquear-es](https://images.ctfassets.net/alneenqid6w5/3rfJ5AjzArgvv7thlD3keQ/bb22e0cfd4ff98513d5da66696b2e5d5/skus-recibidos-rechazar-y-bloquear-es.png)
 
@@ -213,9 +199,7 @@ Esta acción puede realizarse en las pestañas <b>Pendientes</b> y <b>Problemas<
 3. Completa el campo __Correcciones__ con la información que el seller debe corregir.  
 4. Haz clic en `Rechazar`.  
 
-<div class="alert alert-info">
-Esta acción puede realizarse en la pestaña <b>Pendientes</b>. Los anuncios que necesitan corrección se mostrarán en la pestaña <b>Problemas</b>.
-</div>  
+>ℹ️ Esta acción puede realizarse en la pestaña **Pendientes**. Los anuncios que necesitan corrección se mostrarán en la pestaña **Problemas**.  
 
 ![skus-recibidos-rechazar-para-correccion-es](https://images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/bc526e9f64a729781f5ebebcd6a62ee0/skus-recibidos-rechazar-para-correccion-es.png)
 
diff --git a/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
index aeaf3e84d..9a88c47ed 100644
--- a/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
+++ b/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -87,9 +87,7 @@ Se recomienda crear un nuevo número de teléfono exclusivamente para vincularlo
   <li>Pega el número de teléfono que has copiado en la etapa anterior y selecciona la opción <strong>SMS</strong>. Haz clic en <code>Continuar</code>.</li>
 </ol>
 
-<div class="alert alert-warning">
-  El número generado puede ser estadounidense, pero si tu página de Meta está verificada, tus clientes verán el nombre de tu empresa. Si no está verificada, recomendamos seguir el <a href="https://www.facebook.com/business/help/2058515294227817?id=180505742745347">proceso de verificación con Meta</a>.
-</div>
+>⚠️ El número generado puede ser estadounidense, pero si tu página de Meta está verificada, tus clientes verán el nombre de tu empresa. Si no está verificada, recomendamos seguir el [proceso de verificación con Meta](https://www.facebook.com/business/help/2058515294227817?id=180505742745347).
 
 <ol start="13">
   <li>Copia el código de verificación que se muestra en el Admin VTEX.</li>
@@ -107,9 +105,7 @@ Se recomienda crear un nuevo número de teléfono exclusivamente para vincularlo
   <li>Haz clic en <code>Finalizar</code>.</li>
 </ol>
 
-<div class="alert alert-warning">
-Una vez que se ha activado una campaña de recuperación de checkout abandonado pueden transcurrir hasta 48 horas para que comiencen a mostrarse las métricas de análisis.
-</div>
+>⚠️ Una vez que se ha activado una campaña de recuperación de checkout abandonado pueden transcurrir hasta 48 horas para que comiencen a mostrarse las métricas de análisis.
 
 <div class = "alert alert-info">
 Aprende más sobre <a href="https://help.vtex.com/es/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">Gestión y detalles de WhatsApp AI Campaigns</a>.
diff --git a/docs/tutorials/es/redirect-from-other-addresses.md b/docs/tutorials/es/redirect-from-other-addresses.md
index 78eb61fcf..810e51ac4 100644
--- a/docs/tutorials/es/redirect-from-other-addresses.md
+++ b/docs/tutorials/es/redirect-from-other-addresses.md
@@ -31,9 +31,7 @@ Existen diversas formas de configurar las redirecciones, y una de las más conoc
 
 Consulta a continuación instrucciones para configurar redirecciones a la dirección principal de tu tienda utilizando esta sencilla herramienta: [Redirect Center](http://redirect.center/).
 
-<div class="alert alert-warning">
-  <p><a href="http://redirect.center/">Redirect Center</a> no es un servicio de VTEX y no funciona con HTTPS. Existen otros servicios similares, y VTEX no recomienda ninguno en particular. VTEX no se hace responsable de los problemas causados por servicios externos de redirección.</p>
-</div>
+>⚠️ [Redirect Center](http://redirect.center/) no es un servicio de VTEX y no funciona con HTTPS. Existen otros servicios similares, y VTEX no recomienda ninguno en particular. VTEX no se hace responsable de los problemas causados por servicios externos de redirección.
 
 ### Redirección de direcciones sin subdominio (como www)
 
diff --git a/docs/tutorials/es/redirection-from-other-addresses.md b/docs/tutorials/es/redirection-from-other-addresses.md
index e0eca473e..f8b582d43 100644
--- a/docs/tutorials/es/redirection-from-other-addresses.md
+++ b/docs/tutorials/es/redirection-from-other-addresses.md
@@ -28,9 +28,7 @@ También se puede utilizar la redirección de DNS, según provista por diferente
 
 Para realizar una redirección de DNS de forma sencilla, a continuación están las instrucciones para la redirección con el servicio [redirect.center](http://redirect.center/).
 
-<div class="alert alert-warning">
-Cabe resaltar que Redirect Center no es un servicio de VTEX y no funciona con HTTPS. Hay otros servicios similares, pero VTEX no recomienda ninguno en específico. VTEX no se hace responsable por problemas causados por servicios externos de redirección.
-</div>
+>⚠️ Cabe resaltar que Redirect Center no es un servicio de VTEX y no funciona con HTTPS. Hay otros servicios similares, pero VTEX no recomienda ninguno en específico. VTEX no se hace responsable por problemas causados por servicios externos de redirección.
 
 Este artículo contiene instrucciones redirigir otros dominios a la dirección principal de tu tienda. Consulta este otro artículo para saber cómo [configurar el acceso sin www](https://help.vtex.com/es/tutorial/configurando-acesso-sem-www--tutorials_4278).
 
diff --git a/docs/tutorials/es/redirects.md b/docs/tutorials/es/redirects.md
index eb6245f27..b48f4ef83 100644
--- a/docs/tutorials/es/redirects.md
+++ b/docs/tutorials/es/redirects.md
@@ -17,9 +17,7 @@ subcategory: 1wvyJwJhKgewxGeAGCVmM6
 
 La funcionalidad de **Redireccionamientos** direcciona al cliente a cualquier otra página, ya sea interna o externa a la tienda. Los redireccionamientos se hacen en el área de búsqueda de tu storefront, utilizando términos o filtros que el cliente haya seleccionado. De este modo, una de las ventajas de los redireccionamientos es contemplar escenarios de comunicación que la búsqueda en el catálogo de la tienda no cubre, como por ejemplo redirigir la búsqueda de una marca a su página promocional.
 
-<div class="alert alert-warning">
-<p>Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lee nuestro artículo VTEX Intelligent Search: configuración Multidioma (Beta) para obtener más información.</p>
-</div>
+>⚠️ Esta funcionalidad está disponible en VTEX Intelligent Search Multidioma. Lee nuestro artículo VTEX Intelligent Search: configuración Multidioma (Beta) para obtener más información.
 
 ## Cómo funciona un redireccionamiento
 
diff --git a/docs/tutorials/es/regionalization-beta.md b/docs/tutorials/es/regionalization-beta.md
index 13737aae1..5791f1c62 100644
--- a/docs/tutorials/es/regionalization-beta.md
+++ b/docs/tutorials/es/regionalization-beta.md
@@ -15,9 +15,7 @@ legacySlug: regionalizacion-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-<p>Esta funcionalidad está en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a <a href="https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad está en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a [nuestro Soporte](https://support.vtex.com/hc/es-419/requests).
 
 La Regionalización es una funcionalidad de [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) que permite optimizar los resultados de búsqueda según la disponibilidad de sellers en la región del cliente. Para instalar y configurar VTEX Intelligent Search en tu tienda, lee nuestro artículo Search.
 
@@ -36,9 +34,7 @@ Para empezar a utilizar la Regionalización, sigue los pasos a continuación.
 2. [Solicitud de activación de la Regionalización](#2-solicitud-de-activacion-de-la-regionalizacion)
 3. [Configuración en VTEX IO](#3-configuracion-en-vtex-io)
 
-<div class="alert alert-warning">
-  <p>Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.</p>
-</div>
+>⚠️ Aunque las tiendas regionalizadas solo muestran productos disponibles en una determinada región en la página de lista de productos, los filtros no tienen en cuenta la regionalización. Debido a esta limitación, es posible que los clientes de la tienda seleccionen filtros que resulten en productos que no están disponibles en su región.
 
 ## 1. Configuración de sellers 
 
diff --git a/docs/tutorials/es/registering-a-products-base-price.md b/docs/tutorials/es/registering-a-products-base-price.md
index e43bab49c..e8b0fffb9 100644
--- a/docs/tutorials/es/registering-a-products-base-price.md
+++ b/docs/tutorials/es/registering-a-products-base-price.md
@@ -15,9 +15,7 @@ legacySlug: registrar-el-precio-base-de-un-producto
 subcategory: 4id9W3RDyw02CasOm2C2iy
 ---
 
-<div class="alert alert-info">
-Este artículo se refiere a la versión más reciente del VTEX Pricing. Si su tienda todavía no está en esta nueva versión, usted puede solicitar la migración poniéndose en contacto con nuestro equipo de soporte.
-</div>
+>ℹ️ Este artículo se refiere a la versión más reciente del VTEX Pricing. Si su tienda todavía no está en esta nueva versión, usted puede solicitar la migración poniéndose en contacto con nuestro equipo de soporte.
 
 El __precio base__ es el precio básico de venta de un producto. Se compone del __precio de costo__ más el __markup__ deseado en la venta del producto.
 
@@ -30,9 +28,7 @@ Para configurar el precio base, siga los pasos abajo:
 - En el campo __Markup__, rellene el porcentaje del margen de lucro que se obtendrá con la venta del SKU.
 - El precio base de venta se calculará en función de los datos proporcionados en los pasos anteriores.
 
-<div class="alert alert-info">
-Si el SKU tiene algún precio de lista, usted puede añadir esta información haciendo clic en <strong>+ Precio de lista</strong>. Este precio funciona como el "precio de". El precio base funcionará como el "precio por".
-</div>
+>ℹ️ Si el SKU tiene algún precio de lista, usted puede añadir esta información haciendo clic en **+ Precio de lista**. Este precio funciona como el "precio de". El precio base funcionará como el "precio por".
 
 ## Artículos relacionados
 
diff --git a/docs/tutorials/es/registering-geolocation.md b/docs/tutorials/es/registering-geolocation.md
index 270d2d4db..eaaa5ff18 100644
--- a/docs/tutorials/es/registering-geolocation.md
+++ b/docs/tutorials/es/registering-geolocation.md
@@ -32,9 +32,7 @@ Accediendo a través del enlace [Genere sus polígonos con geojson.io](http://ge
 
 Usted usará ese JSon para añadir el polígono en la plataforma, que comprenderá a partir de ese lenguaje cuáles códigos postales están incluidos en esa área.
 
-<div class="alert alert-danger">
-En la configuración de un polígono, no es posible delimitar áreas superpuestas, o sea, no es posible superponer coordenadas geográficas.
-</div>
+>❗ En la configuración de un polígono, no es posible delimitar áreas superpuestas, o sea, no es posible superponer coordenadas geográficas.
 
 ## Cómo añadir un Polígono
 
diff --git a/docs/tutorials/es/registering-holidays.md b/docs/tutorials/es/registering-holidays.md
index cb958bf4d..6bce26704 100644
--- a/docs/tutorials/es/registering-holidays.md
+++ b/docs/tutorials/es/registering-holidays.md
@@ -34,9 +34,7 @@ Solo se considerarán **Feriados** para las transportadoras con la configuració
 3. En la sección **Fines de semana y feriados**, asegúrese de que la opción `Entrega feriados` esté desactivada <i class="fas fa-toggle-off"></i>.
 4. Haga clic en `Guardar`.
 
-<div class="alert alert-info">
-Usted puede definir Feriados para los próximos años con antelación.
-</div>
+>ℹ️ Usted puede definir Feriados para los próximos años con antelación.
 
 ## Cómo se calcula el tiempo de envío con feriados
 
@@ -57,9 +55,7 @@ Desde un punto de vista técnico, los feriados se consideran en la variable `shi
 2. Hay un feriado registrado el martes (06/02).
 3. La fecha estimada para que el cliente reciba el pedido será el jueves (08/02), ya que el martes no se considera día laboral.
 
-<div class="alert alert-warning">
-Existe una excepción en la que el feriado registrado cuenta como día laboral: cuando el cliente realiza un pedido en un feriado y la transportadora tiene configurado el horario de envío (<a href="https://help.vtex.com/es/tutorial/carrier-working-hours--2oGpbInIgdxSWUi3TZjdCS">periodo de envío</a>) para ese mismo día.
-</div>
+>⚠️ Existe una excepción en la que el feriado registrado cuenta como día laboral: cuando el cliente realiza un pedido en un feriado y la transportadora tiene configurado el horario de envío ([periodo de envío](https://help.vtex.com/es/tutorial/carrier-working-hours--2oGpbInIgdxSWUi3TZjdCS)) para ese mismo día.
 
 ### Ejemplo 2
 
diff --git a/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
index 3a6f455ae..9df1f0f21 100644
--- a/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/es/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -48,17 +48,13 @@ Puedes hacer una multiplicación para calcular el porcentaje de descuento desead
 
 Para priorizar un cálculo antes que otro, escribe entre paréntesis el cálculo que se debe realizar primero`()`. Por ejemplo: si una tienda quiere aplicar un descuento del 40% sobre el valor total más el envío, la fórmula debe ser `(total + freight) * 0.4`.
 
-<div class="alert alert-info">
-  <p>Usa siempre el punto (<code>.</code>) como separador decimal.</p>
-</div>
+>ℹ️ Usa siempre el punto (`.`) como separador decimal.
 
 ## Funciones
 
 Si quieres, puedes usar la función `min` para [limitar el valor del descuento](#limitar-el-valor-del-descuento) o la función `max` para [priorizar el mayor descuento posible](#priorizar-el-mayor-descuento-posible). Sigue leyendo para obtener más detalles sobre estas posibilidades.
 
-<div class="alert alert-info">
-<p>Al usar las funciones, debes incluir un espacio entre la función y los paréntesis de apertura. Por ejemplo: <code>min (total * 0.2,  10)</code>.</p>
-</div>
+>ℹ️ Al usar las funciones, debes incluir un espacio entre la función y los paréntesis de apertura. Por ejemplo: `min (total * 0.2,  10)`.
 
 ### Limitar el valor del descuento
 
diff --git a/docs/tutorials/es/releases-module-beta.md b/docs/tutorials/es/releases-module-beta.md
index 4e81def91..47c6bfca6 100644
--- a/docs/tutorials/es/releases-module-beta.md
+++ b/docs/tutorials/es/releases-module-beta.md
@@ -186,9 +186,7 @@ Otra forma de publicar es ingresar en la página de detalles del lanzamiento y s
 
 Sigue estas instrucciones paso a paso para eliminar un lanzamiento:
 
-<div class="alert alert-danger">
-Los lanzamientos eliminados se borran y son irrecuperables. Se mantienen las actualizaciones que formaban parte del lanzamiento, pero deja de existir como grupo.
-</div>
+>❗ Los lanzamientos eliminados se borran y son irrecuperables. Se mantienen las actualizaciones que formaban parte del lanzamiento, pero deja de existir como grupo.
 
 1. En el Admin VTEX, accede a **Configuración de la tienda > Lanzamientos**.
 2. En la línea correspondiente al lanzamiento deseado, haz clic en el ícono de menú <i class="fas fa-ellipsis-v"></i>. 
diff --git a/docs/tutorials/es/releases-overview.md b/docs/tutorials/es/releases-overview.md
index 808002138..3ad3f8028 100644
--- a/docs/tutorials/es/releases-overview.md
+++ b/docs/tutorials/es/releases-overview.md
@@ -15,15 +15,11 @@ legacySlug: introduccion-a-releases
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>El <strong>Releases</strong>se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ El **Releases**se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan [FastStore](https://www.faststore.dev/).
 
 El menú **Releases** te permite gestionar grupos de cambios relacionados para coordinar la planificación, creación, programación y publicación de los cambios de tu tienda. A los cambios o grupos de cambios que **Releases** puede publicar en conjunto se les conoce como releases.
 
-<div class="alert alert-warning">
-  <p>En la etapa Beta, los releases deben estar relacionados al <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a> porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el <strong>Releases</strong>, se debe configurar el CMS tal como se describe en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ En la etapa Beta, los releases deben estar relacionados al [CMS](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) porque hay otros módulos de la plataforma VTEX que aún no están incluidos. Para usar el **Releases**, se debe configurar el CMS tal como se describe en [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Calendario
 
diff --git a/docs/tutorials/es/relevance-rules.md b/docs/tutorials/es/relevance-rules.md
index c1cf456a6..bdefd297c 100644
--- a/docs/tutorials/es/relevance-rules.md
+++ b/docs/tutorials/es/relevance-rules.md
@@ -39,9 +39,7 @@ La información aplicada para establecer la relevancia es:
 
 El conjunto de distribución de pesos y criterios genera una puntuación para el producto, lo que ayuda a su posicionamiento en el orden del resultado de la búsqueda.
 
-<div class="alert alert-warning">
-  <p>Si deseas utilizar los criterios de prioridad, recomendamos agregar solo un criterio en este campo. Agregar más criterios compromete la ordenación de los resultados de búsqueda, ya que solo se considerará el primer criterio.</p>
-</div>
+>⚠️ Si deseas utilizar los criterios de prioridad, recomendamos agregar solo un criterio en este campo. Agregar más criterios compromete la ordenación de los resultados de búsqueda, ya que solo se considerará el primer criterio.
 
 De esta manera, es posible adaptar el comportamiento del resultado de búsqueda a una estrategia específica.
 
diff --git a/docs/tutorials/es/remarketing.md b/docs/tutorials/es/remarketing.md
index 89179f068..92daa8507 100644
--- a/docs/tutorials/es/remarketing.md
+++ b/docs/tutorials/es/remarketing.md
@@ -15,6 +15,4 @@ legacySlug: remarketing
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
index 70567901f..ccf4ae88d 100644
--- a/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/es/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -85,7 +85,5 @@ Si lo deseas, también puedes incluir las siguientes funciones en el script:
 - Hacer que las cookies que contengan caracteres especiales expiren automáticamente
 - Activar la recarga de la página mediante la función `window.location.reload()`  
 
-<div class="alert alert-warning">
-  Remover las cookies mediante script no es una solución definitiva. Como se describe en la sección <b>Desactivar cookies con caracteres especiales</b>, es necesario identificar su origen e interrumpir el proceso de envío de cookies con caracteres especiales.
-</div>
+>⚠️ Remover las cookies mediante script no es una solución definitiva. Como se describe en la sección **Desactivar cookies con caracteres especiales**, es necesario identificar su origen e interrumpir el proceso de envío de cookies con caracteres especiales.
 
diff --git a/docs/tutorials/es/request-deletion-of-customer-personal-data-under-international-data-privacy.md b/docs/tutorials/es/request-deletion-of-customer-personal-data-under-international-data-privacy.md
index c10c9f897..ee89efbb4 100644
--- a/docs/tutorials/es/request-deletion-of-customer-personal-data-under-international-data-privacy.md
+++ b/docs/tutorials/es/request-deletion-of-customer-personal-data-under-international-data-privacy.md
@@ -32,9 +32,7 @@ Configurar los datos en el Master Data es la primera etapa para eliminar los dat
 
 Las leyes de privacidad determinan que los datos personales de los titulares no se deben compartir o exponer de forma indebida. Por ende, se necesitan ciertas configuraciones para garantizar la protección de esos datos.
 
-<div class="alert alert-warning">
-Las configuraciones guardadas no se podrán modificar.
-</div>
+>⚠️ Las configuraciones guardadas no se podrán modificar.
 
 Para activar esta configuración, sigue los pasos a continuación:
 
@@ -54,9 +52,7 @@ Para activar esta configuración, sigue los pasos a continuación:
 
 Después de configurar los datos en el Master Data, deberás solicitar la extensión de la eliminación de los datos personales de tus clientes también en los sistemas de VTEX mediante la apertura de un ticket en nuestro [Soporte VTEX](https://help.vtex.com/es/support).
 
-<div class="alert alert-warning">
-Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará. 
-</div>
+>⚠️ Solicita la eliminación de los datos de una sola cuenta, es decir, se podrá eliminar el email de un solo comprador por ticket. Si incluyes más de un email, el ticket se rechazará.
 
 Para solicitar la eliminación de los datos personales de clientes, sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
index ee3bf6fc0..a133c43a5 100644
--- a/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
+++ b/docs/tutorials/es/responsibilities-in-the-vtex-ecosystem.md
@@ -164,9 +164,7 @@ Aun así, pueden existir tiendas partner estratégicas para tu empresa que opere
 
 Respecto al soporte a una operación en este contexto, es importante que el retailer comprenda las responsabilidades de cada participante en la operación, que se detallan a continuación.
 
-<div class="alert alert-warning">
-  <p>Las secciones siguientes contemplan una tienda en operación integrada con un marketplace externo vía conector externo. Para saber cómo integrar por primera vez tu catálogo de VTEX con un conector externo, consulta el tutorial <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Catalog Integration</a>.</p>
-</div>
+>⚠️ Las secciones siguientes contemplan una tienda en operación integrada con un marketplace externo vía conector externo. Para saber cómo integrar por primera vez tu catálogo de VTEX con un conector externo, consulta el tutorial [Catalog Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word).
 
 ### Actualización o envío de nuevos productos y SKU
 
diff --git a/docs/tutorials/es/returning-order-items.md b/docs/tutorials/es/returning-order-items.md
index ddf8530a5..da04fc799 100644
--- a/docs/tutorials/es/returning-order-items.md
+++ b/docs/tutorials/es/returning-order-items.md
@@ -35,12 +35,13 @@ Para realizar la devolución en el VTEX Admin:
 
 ![Devolucion de items](https://drive.google.com/uc?export=download&id=1kZVs7Kq2zTOGz8KxkT_Y8LqnObagdi4f)
 
-<div class="alert alert-warning">
-Ten en cuenta que:
-<ul>
-<li>La devolución de un SKU en el módulo Gestión de pedidos no actualiza la cantidad de SKU que están disponibles en el stock. La tienda debe actualizar la cantidad de ítems en el <a href="https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139">stock</a>.</li>
-<li>El número de la factura de devolución debe ser diferente al de la factura de venta.</li>
-<li>Tras la devolución, se notifica al sistema de pago para que realice el <a href="https://help.vtex.com/es/tutorial/como-funciona-estorno-quando-ha-devolucao-do-item">reembolso</a>.</li>
-<li>Solo es posible devolver pedidos que tengan al menos una factura insertada en la plataforma.</li>
-</ul>
-</div>
+>⚠️ Ten en cuenta que:
+>
+> *La devolución de un SKU en el módulo Gestión de pedidos no actualiza la cantidad de SKU que están disponibles en el stock. La tienda debe actualizar la cantidad de ítems en el [stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+>
+> *El número de la factura de devolución debe ser diferente al de la factura de venta.
+>
+> *Tras la devolución, se notifica al sistema de pago para que realice el [reembolso](https://help.vtex.com/es/tutorial/como-funciona-estorno-quando-ha-devolucao-do-item).
+>
+> *Solo es posible devolver pedidos que tengan al menos una factura insertada en la plataforma.
+> 
diff --git a/docs/tutorials/es/risk-assessment.md b/docs/tutorials/es/risk-assessment.md
index 29f50bafe..8f97c5494 100644
--- a/docs/tutorials/es/risk-assessment.md
+++ b/docs/tutorials/es/risk-assessment.md
@@ -44,7 +44,7 @@ Parte de la información sobre seguridad está restringida a usuarios con acceso
 Ingrese su [nombre de cuenta](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) VTEX para acceder a la documentación.
 <iframe src="https://help.vtex.com/insertaccountname?id=1ayXEtqawI9yuxFXutiITh" title="Ingrese su nombre de cuenta y haz click en el botón." frameBorder="0" width="400" height="50"></iframe>
 
-<div class="alert alert-warning">Si tiene dificultades para acceder a las preguntas frecuentes, intente instalar la última versión de la aplicación <code>vtex.admin-docs</code> usando la <a href="https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">CLI de VTEX</a> y repetir el proceso.</div>
+>⚠️ Si tiene dificultades para acceder a las preguntas frecuentes, intente instalar la última versión de la aplicación `vtex.admin-docs` usando la [CLI de VTEX](https://developers.vtex.com/docs/guides/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) y repetir el proceso.
 
 ## Preguntas frecuentes - Seguridad
 
diff --git a/docs/tutorials/es/roles.md b/docs/tutorials/es/roles.md
index 97b351b51..495151ab3 100644
--- a/docs/tutorials/es/roles.md
+++ b/docs/tutorials/es/roles.md
@@ -38,9 +38,7 @@ La página muestra en formato de tabla una lista con todos los roles registrados
 
 En una cuenta recién creada, solo aparecerá en la lista el rol _Owner (Admin Super)_. Dicho rol permite al usuario acceder sin restricciones a todos los recursos nativos de la plataforma.
 
-<div class="alert alert-warning">
-  <p>El número de usuarios con el rol <em>Owner (Admin Super)</em> debe ser el menor posible. También hay que asegurarse de que haya visibilidad y control sobre quién recibe este acceso.</p>
-</div>
+>⚠️ El número de usuarios con el rol *Owner (Admin Super)* debe ser el menor posible. También hay que asegurarse de que haya visibilidad y control sobre quién recibe este acceso.
 
 ## Crear rol
 
@@ -58,9 +56,7 @@ Puedes editar los recursos y usuarios relacionados con un determinado rol; solo
 
 Para eliminar un rol, haz clic en el ícono de ⫶ en la fila del rol que deseas eliminar y a continuación en <i class="far fa-trash-alt"></i> `Eliminar`.
 
-<div class="alert alert-warning">
-  <p>Al eliminar un rol, los usuarios asociados al mismo perderán el acceso a los <a href="https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3">recursos del License Manager</a> relacionados con él, a menos que tengan otros roles con los mismos permisos.</p>
-</div>
+>⚠️ Al eliminar un rol, los usuarios asociados al mismo perderán el acceso a los [recursos del License Manager](https://help.vtex.com/es/tutorial/recursos-del-license-manager--3q6ztrC8YynQf6rdc6euk3) relacionados con él, a menos que tengan otros roles con los mismos permisos.
 
 ## Más información
 
diff --git a/docs/tutorials/es/sales-associate-code-field-at-checkout.md b/docs/tutorials/es/sales-associate-code-field-at-checkout.md
index 12c96cdee..08cb84bb7 100644
--- a/docs/tutorials/es/sales-associate-code-field-at-checkout.md
+++ b/docs/tutorials/es/sales-associate-code-field-at-checkout.md
@@ -20,9 +20,7 @@ En VTEX, puedes crear un campo para registrar el código de vendedor en el Check
 - Ofrecer descuentos exclusivos al consumidor.
 - Gestionar el desempeño de tus vendedores, extrayendo datos como número de ventas o ticket promedio por vendedor y ranking para comisiones de ventas, entre otros.
 
-<div class="alert alert-warning">
-  El campo <b>Código de vendedor</b> no sustituye el campo <b>Cupón de descuento</b> (que es nativo en la plataforma VTEX). Al realizar la configuración que se describe en este artículo, puedes utilizar los dos para ofrecer descuentos.
-</div>
+>⚠️ El campo **Código de vendedor** no sustituye el campo **Cupón de descuento** (que es nativo en la plataforma VTEX). Al realizar la configuración que se describe en este artículo, puedes utilizar los dos para ofrecer descuentos.
 
 Para crear el campo y agregarlo a la pantalla del Checkout de tu tienda, debes completar tres pasos:
 
@@ -55,9 +53,7 @@ Después de crear la entidad *codigovendedor*, debes asociarla a una promoción.
 1. En el Admin VTEX, accede a **Promociones > Promociones**, o escribe **Promociones** en la barra de búsqueda en la parte superior de la página.
 2. Crea una nueva [promoción regular](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/2a2D0K85Ahvs4hLnL3Ag7N). Rellena la información de **Resumen de la promoción** y **¿A qué ítems se aplicará esta promoción?** según lo desees.
 
-<div class="alert alert-info">
- Si deseas utilizar el campo Código de vendedor para ofrecer un descuento en el valor de la compra, rellena la información de <b>¿Cuál es el tipo y valor del descuento?</b>.
-</div>
+>ℹ️ Si deseas utilizar el campo Código de vendedor para ofrecer un descuento en el valor de la compra, rellena la información de **¿Cuál es el tipo y valor del descuento?**.
 
 <blockquote><ui>3. En <b>¿Cuáles son las condiciones para que la promoción sea válida?</b>, haz clic en la opción <b>utm_campaign</b> e ingresa <i>codigovendedor</i> en el campo.</ui>
 
@@ -77,9 +73,7 @@ También debes completar los siguientes pasos:
 
 1. Al simular una compra e ingresar el código del vendedor en la pantalla del Checkout, asegúrate de que la llamada GET [Search Documents](https://developers.vtex.com/docs/api-reference/master-data-api-v2#get-/api/dataentities/-dataEntityName-/search) realice la búsqueda en la entidad `codigovendedor` y devuelva toda la información registrada de dicho vendedor. Ejemplo de llamada: https://{accountName}.{environment}.com.br/api/dataentities/codigovendedor/search?codigovendedor=12345.
 
-<div class="alert alert-warning">
-  El campo <b>status</b> debe devolver el valor <b>true</b> para indicar que el código del vendedor es válido.
-</div>
+>⚠️ El campo **status** debe devolver el valor **true** para indicar que el código del vendedor es válido.
 
 <blockquote><ui>2. Realiza la llamada POST <a href="https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm">Update orderForm configuration</a> para incluir la siguiente información en el <a href="https://developers.vtex.com/docs/guides/orderform-fields">orderForm</a> de tu tienda</ui>:
 
@@ -87,9 +81,7 @@ También debes completar los siguientes pasos:
 
   <blockquote><blockquote>- <b>openTextField</b> (opcional): ingresa observaciones o comentarios como, por ejemplo, información para filtros de comisiones.
 
-<div class="alert alert-warning">
-  En la pantalla del Checkout solo debe aparecer el nombre del vendedor.
-</div>
+>⚠️ En la pantalla del Checkout solo debe aparecer el nombre del vendedor.
 
 Después de ejecutar todos los pasos descritos anteriormente, el campo **Código de vendedor** estará disponible en la pantalla del Checkout.
 
diff --git a/docs/tutorials/es/sales-funnel-suiteshare.md b/docs/tutorials/es/sales-funnel-suiteshare.md
index c280dfd75..1c55cac0a 100644
--- a/docs/tutorials/es/sales-funnel-suiteshare.md
+++ b/docs/tutorials/es/sales-funnel-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: funil-de-ventas-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/sales-performance.md b/docs/tutorials/es/sales-performance.md
index ac4d1bee7..b72153d30 100644
--- a/docs/tutorials/es/sales-performance.md
+++ b/docs/tutorials/es/sales-performance.md
@@ -211,9 +211,7 @@ La lista representa las métricas y los filtros aplicados al gráfico en formato
   - __Absoluta__: visualiza en números absolutos el aumento o disminución de las métricas de la lista entre un periodo y otro.   
   - __Representativa__: visualiza el porcentaje de representatividad de un elemento dentro de una métrica.  
 
-<div class="alert alert-info">
-Ten en cuenta que las métricas <i>Ticket promedio</i> y <i>Ítems por pedido</i> no tendrán disponible una vista de Porcentaje o Representativa, ya que son métricas que se calculan dividiendo otras, y la suma de todas las partes de cada una no es igual al Total.
-  </div>
+>ℹ️ Ten en cuenta que las métricas <i>Ticket promedio</i> y <i>Ítems por pedido</i> no tendrán disponible una vista de Porcentaje o Representativa, ya que son métricas que se calculan dividiendo otras, y la suma de todas las partes de cada una no es igual al Total.
 
 ### Exportar datos
 
diff --git a/docs/tutorials/es/scheduled-delivery.md b/docs/tutorials/es/scheduled-delivery.md
index d4d644b3c..7b5675281 100644
--- a/docs/tutorials/es/scheduled-delivery.md
+++ b/docs/tutorials/es/scheduled-delivery.md
@@ -21,9 +21,9 @@ Los periodos de entrega que están disponibles para los clientes se denominan ve
 
 En caso de que la política de envío ofrezca el servicio, puede habilitar la entrega programada configurando las ventanas de entrega y estableciendo la capacidad de realización de entregas para cada ventana, si así lo desea.
 
-<div class="alert alert-warning">
-Para que la <a href="https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega programada</a> y la <a href="https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidad de entrega</a> funcionen correctamente, debes tener en cuenta que:<p><ul><li>La suma de {<a href="https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID de la política de envío} no puede exceder los 60 caracteres.</li><li>No se debe utilizar espacio en el ID de la <a href="https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">política de envío</a>.</li></ul></p>
-</div>
+>⚠️ Para que la [Entrega programada](https://help.vtex.com/es/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) y la [Capacidad de entrega](https://help.vtex.com/es/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) funcionen correctamente, debes tener en cuenta que:
+> *La suma de {[account name](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {ID de la política de envío} no puede exceder los 60 caracteres.
+> * No se debe utilizar espacio en el ID de la [política de envío](https://help.vtex.com/es/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 La entrega programada se habilita a través del campo Entrega programada que se muestra en la pantalla de creación o edición de [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140). 
 
@@ -43,9 +43,7 @@ El periodo de entrega, también denominado ventana de entrega, especifica los pe
 
 Los periodos/ventanas se definen a partir de las horas de inicio y fin de la operación para cada día de la semana. Además, puede definir un valor adicional para el flete en determinados días de la semana. 
 
-<div class="alert alert-info">
-Una entrega de entrega no está disponible para su selección después de que ha iniciado. Solo estarán disponibles para los clientes las ventanas de entrega cercanas (aún no iniciadas).
-</div>
+>ℹ️ Una entrega de entrega no está disponible para su selección después de que ha iniciado. Solo estarán disponibles para los clientes las ventanas de entrega cercanas (aún no iniciadas).
 
 ## Capacidad de entrega
 
@@ -53,8 +51,6 @@ Definir la capacidad de entrega le permite limitar el número de ítems o pedido
 
 Cuando el cliente finaliza la compra y selecciona la entrega programada, las opciones de fecha y hora que se muestran consideran la capacidad de entrega. De esta forma, el cliente solo podrá programar las entregas en las ventanas que aún tienen disponibilidad de 1 ítem o pedido. 
 
-<div class="alert alert-info"> 
-Si la ventana alcanza la capacidad total de ítems/pedidos, ya no se podrá elegir. Para que la ventana vuelva a estar disponible, debe aumentar el número de ítems/pedidos de la capacidad de entrega. Esto se puede realizar editando una <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">Registrar política de envío</a>.
-</div>
+>ℹ️ Si la ventana alcanza la capacidad total de ítems/pedidos, ya no se podrá elegir. Para que la ventana vuelva a estar disponible, debe aumentar el número de ítems/pedidos de la capacidad de entrega. Esto se puede realizar editando una [Registrar política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 Lea el artículo [Gestionar capacidad de entrega](https://help.vtex.com/es/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz) para saber más.
 
diff --git a/docs/tutorials/es/scheduling-features-for-special-events.md b/docs/tutorials/es/scheduling-features-for-special-events.md
index e074f9f4d..97fe27c7b 100644
--- a/docs/tutorials/es/scheduling-features-for-special-events.md
+++ b/docs/tutorials/es/scheduling-features-for-special-events.md
@@ -59,9 +59,7 @@ Al igual que la promoción, la programación de las tasas se realiza durante su
 
 La programación de contenidos a través de Site Editor se puede hacer tanto al [crear](https://help.vtex.com/es/tutorial/managing-page-and-template-content--3tMbx6HXy4Fy5r9EhboG37#crear-contenido) como al [editar](https://help.vtex.com/es/tutorial/managing-page-and-template-content--3tMbx6HXy4Fy5r9EhboG37#editar-contenido) un bloque.  
 
-<div class="alert alert-warning">
-  <p>La programación de contenidos solo está disponible para las tiendas desarrolladas en <a href="https://vtex.com/es-es/store-framework/">VTEX IO</a>.</p>
-</div> 
+>⚠️ La programación de contenidos solo está disponible para las tiendas desarrolladas en [VTEX IO](https://vtex.com/es-es/store-framework/). 
 
 Para programar un contenido, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/scheduling-prices.md b/docs/tutorials/es/scheduling-prices.md
index d29797337..c48c63c41 100644
--- a/docs/tutorials/es/scheduling-prices.md
+++ b/docs/tutorials/es/scheduling-prices.md
@@ -48,9 +48,7 @@ Para hacer la programación por el Admin, siga los pasos a continuación.
 - **Fecha de término:** indica el día a partir del cual el precio fijo dejará de ser válido. 
 - **Hora de término:** indica la hora a partir de la cual el precio fijo dejará de ser válido. 
 
-<div class="alert alert-info">
-  <p>En la programación realizada a través del Admin, la zona horaria considerada será la utilizada por el computador del usuario.</p>
-</div>
+>ℹ️ En la programación realizada a través del Admin, la zona horaria considerada será la utilizada por el computador del usuario.
 
 ## Programación mediante la importación de una plantilla de precios fijos
 
diff --git a/docs/tutorials/es/schemas-on-master-data.md b/docs/tutorials/es/schemas-on-master-data.md
index 81c025042..ee3784522 100644
--- a/docs/tutorials/es/schemas-on-master-data.md
+++ b/docs/tutorials/es/schemas-on-master-data.md
@@ -15,4 +15,4 @@ legacySlug:
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/search-behavior.md b/docs/tutorials/es/search-behavior.md
index db2a47cc4..1d8c134cb 100644
--- a/docs/tutorials/es/search-behavior.md
+++ b/docs/tutorials/es/search-behavior.md
@@ -88,9 +88,7 @@ Ejemplo: se configuró que la especificación “color” se puede buscar y el p
 
 Se puede encontrar un producto realizando una búsqueda por caracteres especiales (`-` y `/`).
 
-<div class="alert alert-warning">
-	<p>La selección de los campos de búsqueda afecta las posibilidades de las <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">reglas de merchandising</a>, ya que solo se pueden utilizar los campos que permiten búsquedas para configurar reglas. Por ejemplo, al definir solo el campo <code>SKUID</code> para búsquedas, no se podrá promover un <code>ProductID</code> o un <code>ProductRefID</code> utilizando reglas de merchandising.</p>
-</div>
+>⚠️ La selección de los campos de búsqueda afecta las posibilidades de las [reglas de merchandising](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), ya que solo se pueden utilizar los campos que permiten búsquedas para configurar reglas. Por ejemplo, al definir solo el campo `SKUID` para búsquedas, no se podrá promover un `ProductID` o un `ProductRefID` utilizando reglas de merchandising.
 
 ### Definición y orden de los campos de filtro
 
@@ -104,9 +102,7 @@ Ejemplo: un administrador de la tienda configuró que el criterio “promoción
 
 Para obtener más información sobre cómo personalizar el orden de los resultados de acuerdo con las necesidades de tu tienda, consulta el artículo [Configuración de relevancia](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
 
-<div class="alert alert-info">
-	<p>Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Si utilizas el comando <code>map=productClusterIds</code>, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con su propio criterio de relevancia. Si eliges utilizar <code>productClusterNames</code>, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search.</p>
-</div>
+>ℹ️ Al utilizar Intelligent Search, hay dos opciones que definirán el orden de tus colecciones. Si utilizas el comando `map=productClusterIds`, estás definiendo que el orden de tus colecciones será el predefinido por el administrador de la tienda, con su propio criterio de relevancia. Si eliges utilizar `productClusterNames`, estás definiendo que quieres que tus colecciones sigan los estándares de relevancia de Intelligent Search.
 
 ## Formas alternativas de búsqueda
 
diff --git a/docs/tutorials/es/search-by-geo-coordinates.md b/docs/tutorials/es/search-by-geo-coordinates.md
index f38226ec7..d84e0274f 100644
--- a/docs/tutorials/es/search-by-geo-coordinates.md
+++ b/docs/tutorials/es/search-by-geo-coordinates.md
@@ -15,8 +15,7 @@ legacySlug: busqueda-por-geocoordenadas
 subcategory: 5tSNDlvmik8gGuKw2goW4q
 ---
 
-<div class="alert alert-warning">
-<strong>Atención:</strong> Esta funcionalidad todavía se encuentra en BETA.</div>
+>⚠️ **Atención:** Esta funcionalidad todavía se encuentra en BETA.
 
 ### Configurar el JSON Schema
 
diff --git a/docs/tutorials/es/search-navigator-control.md b/docs/tutorials/es/search-navigator-control.md
index 497e475e7..4ad0bb4e0 100644
--- a/docs/tutorials/es/search-navigator-control.md
+++ b/docs/tutorials/es/search-navigator-control.md
@@ -21,9 +21,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 El control `<vtex.cmc:searchNavigator/>` renderiza un menú de filtros relacionados con el resultado de una búsqueda.
 
-<div class="alert alert-info">
-Este control funciona <b>apenas en páginas con contexto de búsqueda</b>; es decir, páginas donde los resultados mostrados fueron traídos por una búsqueda de usuario.
-</div>
+>ℹ️ Este control funciona **apenas en páginas con contexto de búsqueda**; es decir, páginas donde los resultados mostrados fueron traídos por una búsqueda de usuario.
 
 Cuando el usuario realiza una búsqueda en la tienda, el sistema de VTEX intenta traer resultados de acuerdo con un orden de prioridad de filtros. [Entienda cómo funciona la búsqueda aquí.](/es/tutorial/como-funciona-la-busqueda-de-vtex)
 
@@ -54,9 +52,7 @@ Este flag está en la pantalla de registro de la categoría.
 
 ![Cómo funciona el control Search Navigator ES 2](https://images.ctfassets.net/alneenqid6w5/5Qg0LcxqSc6e2UuEo2M0me/457a81b3196c932f1d3f157582598599/2018-10-23_22-41-18_ES_2.png)
 
-<div class="alert alert-info">
-  <strong>Importante</strong>: El control  <code>&lt;vtex.cmc:searchNavigator/&gt;</code> exhibe, por estándar, apenas la categoría base (primer nivel) y la subcategoría más específica (último nivel) dentro del contexto actual. Se omiten las divisiones intermedias en el árbol de categorías. Además, el control solo funciona en los primeros tres niveles, que son tradicionalmente Departamento, Categoría y Subcategoría. Si su  <a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">arquitectura de catálogo</a> contiene subdivisiones más allá del tercer nivel, no se mostrarán con el control nativo.
-</div>
+>ℹ️ **Importante**: El control  `&lt;vtex.cmc:searchNavigator/&gt;` exhibe, por estándar, apenas la categoría base (primer nivel) y la subcategoría más específica (último nivel) dentro del contexto actual. Se omiten las divisiones intermedias en el árbol de categorías. Además, el control solo funciona en los primeros tres niveles, que son tradicionalmente Departamento, Categoría y Subcategoría. Si su  [arquitectura de catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) contiene subdivisiones más allá del tercer nivel, no se mostrarán con el control nativo.
 
 ## Marcas
 
@@ -66,9 +62,7 @@ La página de registro de marca no tiene un flag de exhibición en el menú rend
 
 Entonces, por estándar, las marcas siempre se muestran.
 
-<div class="alert alert-warning">
-Sin embargo, en las páginas de departamento o categoría, las marcas solo se mostrarán mediante el control Search Navigator si, en el registro de categoría, el flag <b>Filtro de Marca</b> está seleccionado.
-</div>
+>⚠️ Sin embargo, en las páginas de departamento o categoría, las marcas solo se mostrarán mediante el control Search Navigator si, en el registro de categoría, el flag **Filtro de Marca** está seleccionado.
 
 ### En otras páginas:
 
@@ -95,6 +89,12 @@ Por ser filtros registrados en las categorías, los rangos de precio solo se vis
 
 ---
 
-<div class="alert alert-info">
-Los filtros <strong>siempre</strong> se renderizan en función de los atributos de los productos del contexto de búsqueda. Es decir, en base a la categoría, especificación (color, tamaño), marca, colección, etc.<br><br>Por lo tanto, además de las condiciones señaladas anteriormente para que estos atributos aparezcan como filtros en el menú, es necesario antes de todo que el término buscado devuelva un contexto con productos que tienen esos atributos.<br><br>Si el usuario hace, por ejemplo, una búsqueda por "celular" y la categoría Camisas no contiene ningún celular, esta no aparecerá en el menú, aunque en el registro de esa categoría el flag de exhibición esté seleccionado.
-</div>
+>ℹ️ Los filtros **siempre** se renderizan en función de los atributos de los productos del contexto de búsqueda. Es decir, en base a la categoría, especificación (color, tamaño), marca, colección, etc.
+>
+> 
+>
+> Por lo tanto, además de las condiciones señaladas anteriormente para que estos atributos aparezcan como filtros en el menú, es necesario antes de todo que el término buscado devuelva un contexto con productos que tienen esos atributos.
+>
+> 
+>
+> Si el usuario hace, por ejemplo, una búsqueda por "celular" y la categoría Camisas no contiene ningún celular, esta no aparecerá en el menú, aunque en el registro de esa categoría el flag de exhibición esté seleccionado.
diff --git a/docs/tutorials/es/search-parameters.md b/docs/tutorials/es/search-parameters.md
index 38450bad3..9138c581f 100644
--- a/docs/tutorials/es/search-parameters.md
+++ b/docs/tutorials/es/search-parameters.md
@@ -81,9 +81,7 @@ Los parámetros arriba pueden ser combinados de diversas formas, pero vale refor
 
 ### Estándar 2
 
-<div class="alert alert-info">
-  Para tiendas en VTEX IO, el Estándar es el modelo indicado.
-  </div>
+>ℹ️ Para tiendas en VTEX IO, el Estándar es el modelo indicado.
 
 URL: www.loja.com.br/**\[NomeCategoria\]**/**\[NomeMarca\]**/**\[IdColeção\]**/**\[ValorBuscado\]**?map=**c,b,productClusterIds,specificationFilter_\[IdCampoProduto/Sku\]**
 
diff --git a/docs/tutorials/es/searching-for-events-on-audit.md b/docs/tutorials/es/searching-for-events-on-audit.md
index 9c9931adb..633d66928 100644
--- a/docs/tutorials/es/searching-for-events-on-audit.md
+++ b/docs/tutorials/es/searching-for-events-on-audit.md
@@ -28,15 +28,11 @@ Para iniciar una búsqueda en Audit, selecciona la pestaña **Eventos de Auditor
 
 Puedes elegir una fecha predefinida para la búsqueda utilizando el botón **Fecha seleccionada**. Para seleccionar el periodo exacto en el que debe realizarse la búsqueda, haz clic en el botón **Usar fechas personalizadas.**
 
-<div class="alert alert-warning">
-Solo se almacenan los registros de los últimos 3 meses.
-</div>
+>⚠️ Solo se almacenan los registros de los últimos 3 meses.
 
 Es posible añadir más filtros para realizar la búsqueda de eventos con mayor precisión. Para ello, haz clic en **Añadir filtro.** Selecciona el parámetro de filtrado (_Acción_, _Detalles del evento_ o _Autor_) y con qué valor debe compararse. 
 
-<div class="alert alert-info">
-Los resultados de la búsqueda corresponden exactamente al contenido escrito en el tema del filtro. Para evitar resultados inesperados, asegúrate de que no se han introducido espacios adicionales en los términos de búsqueda.
-</div>
+>ℹ️ Los resultados de la búsqueda corresponden exactamente al contenido escrito en el tema del filtro. Para evitar resultados inesperados, asegúrate de que no se han introducido espacios adicionales en los términos de búsqueda.
 
 Ten en cuenta que es posible añadir más de un filtro, incluso con el mismo tema. En este caso, se buscarán los eventos que correspondan a cualquiera de los valores introducidos. 
 
@@ -48,9 +44,7 @@ Tras seleccionar la aplicación, la fecha y los demás filtros de búsqueda, haz
 
 Observa que cada búsqueda que realizas se guarda en la pestaña **Últimas búsquedas.** Para volver a realizar una búsqueda, haz clic en esta pestaña y luego en el botón <img src="https://images.ctfassets.net/alneenqid6w5/4gWsOnbLMOUeWh0r5YRDz/9b7148d995c03ca84b39473f266b46a9/refresh.png" width="15"> correspondiente a la búsqueda que deseas volver a hacer.
 
-<div class="alert alert-warning">
-Solo se registran 50 búsquedas en este panel. Si quieres guardar una búsqueda por tiempo indefinido, realízala y añádela a los favoritos de tu navegador.
-</div>
+>⚠️ Solo se registran 50 búsquedas en este panel. Si quieres guardar una búsqueda por tiempo indefinido, realízala y añádela a los favoritos de tu navegador.
 
 <div class = "alert alert-info">
 Revisa la <a href="https://help.vtex.com/es/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista completa de eventos de Audit</a>.
diff --git a/docs/tutorials/es/searching-for-old-orders.md b/docs/tutorials/es/searching-for-old-orders.md
index a289c1566..14cfdc07c 100644
--- a/docs/tutorials/es/searching-for-old-orders.md
+++ b/docs/tutorials/es/searching-for-old-orders.md
@@ -24,8 +24,5 @@ Para buscar sus pedidos antiguos, siga los pasos a continuación:
 6. Escoja una fecha/hora inicial y una fecha/hora final. 
 7. Haga clic en el botón __Confirme__.
 
-<div class="alert alert-info">
-
-Recuerde que la búsqueda por periodo es <strong>limitada a un intervalo de 6 meses</strong>. Así, si usted desea, por ejemplo, buscar pedidos del año de 2017, el intervalo de tiempo escogido en el <strong>paso 6</strong> debe ser un periodo de 6 meses. Ejemplo: Fecha Inicial = 01/01/2017 y Fecha Final = 30/06/2017.
-</div>
+>ℹ️ Recuerde que la búsqueda por periodo es **limitada a un intervalo de 6 meses**. Así, si usted desea, por ejemplo, buscar pedidos del año de 2017, el intervalo de tiempo escogido en el **paso 6** debe ser un periodo de 6 meses. Ejemplo: Fecha Inicial = 01/01/2017 y Fecha Final = 30/06/2017.
 
diff --git a/docs/tutorials/es/searching-for-orders-in-oms.md b/docs/tutorials/es/searching-for-orders-in-oms.md
index f6c8cfdec..53aad1309 100644
--- a/docs/tutorials/es/searching-for-orders-in-oms.md
+++ b/docs/tutorials/es/searching-for-orders-in-oms.md
@@ -15,9 +15,7 @@ legacySlug: como-buscar-el-pedido
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-info">
-<strong>Atención:</strong> sólo es posible hacer consultas utilizando un intervalo máximo de <b>6 meses</b>.
-</div>
+>ℹ️ **Atención:** sólo es posible hacer consultas utilizando un intervalo máximo de **6 meses**.
 
 La barra de búsqueda de Gestión de pedidos permite encontrar los pedidos de varias formas diferentes. Basta digitar una de esas opciones en la barra y pulsar __Enter__. También se puede utilizar junto con los filtros, siempre que sea necesario [filtrar pedidos en Gestión de pedidos](/es/tutorial/como-filtrar-pedidos).
 
diff --git a/docs/tutorials/es/security-certificate-ssl.md b/docs/tutorials/es/security-certificate-ssl.md
index 756340c4d..2e9228061 100644
--- a/docs/tutorials/es/security-certificate-ssl.md
+++ b/docs/tutorials/es/security-certificate-ssl.md
@@ -21,6 +21,4 @@ Siempre que tu accedes una página segura, que sea protegida por un certificado
 
 No es necesario solicitar la compra de un certificado SSL. VTEX genera un certificado SSL para tu tienda y garantiza su renovación automática. El certificado se emite a través de Let's Encrypt y su creación es responsabilidad de VTEX en [el momento del Go-Live de la tienda](https://help.vtex.com/es/tutorial/configurando-el-apuntamiento-del-dns-para-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-<p>No recomendamos instalar otros certificados. No obstante, si es necesario, póngase en contacto con nuestro <a href="https://help.vtex.com/es/support">soporte</a>.</p>
-</div>
+>⚠️ No recomendamos instalar otros certificados. No obstante, si es necesario, póngase en contacto con nuestro [soporte](https://help.vtex.com/es/support).
diff --git a/docs/tutorials/es/security-monitor.md b/docs/tutorials/es/security-monitor.md
index 9456cef89..e95357ba8 100644
--- a/docs/tutorials/es/security-monitor.md
+++ b/docs/tutorials/es/security-monitor.md
@@ -15,9 +15,7 @@ legacySlug: security-monitor
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad es parte de <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>.  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad es parte de [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh).  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 Security Monitor es un dashboard que ayuda a los retailers a identificar y gestionar riesgos potenciales en su entorno en tiempo real. La herramienta identifica y notifica por email a los retailers sobre riesgos relacionados con la configuración y el comportamiento de los usuarios administrativos, lo que permite tomar medidas preventivas contra las vulnerabilidades de seguridad.
 
diff --git a/docs/tutorials/es/seletivo.md b/docs/tutorials/es/seletivo.md
index 08d90026c..bc0854a42 100644
--- a/docs/tutorials/es/seletivo.md
+++ b/docs/tutorials/es/seletivo.md
@@ -15,7 +15,5 @@ legacySlug: seletivo
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
 
diff --git a/docs/tutorials/es/seller-creating-an-account-in-the-seller-portal.md b/docs/tutorials/es/seller-creating-an-account-in-the-seller-portal.md
index fd39fe0c2..de5024725 100644
--- a/docs/tutorials/es/seller-creating-an-account-in-the-seller-portal.md
+++ b/docs/tutorials/es/seller-creating-an-account-in-the-seller-portal.md
@@ -35,9 +35,7 @@ El proceso de creación de una cuenta en el Seller Portal comienza con una [invi
 - [Crear una cuenta para_ sellers_ VTEX](#conectar-la-cuenta-vtex-con-el-marketplace): tienda hospedada en la plataforma VTEX.  
 - [Crear una cuenta para _sellers_ externos](#crear-una-cuenta-para-sellers-externos): tienda hospedada en otra plataforma de ecommerce o que aún no está hospedada en ninguna plataforma.  
 
-<div class="alert alert-info">
-El enlace para crear la cuenta enviado al seller es válido durante 7 días. Después de hacer clic en el enlace, el seller tiene seis horas para completar el formulario de registro. Si no es posible completar el registro dentro de este periodo, debes pedir al marketplace que envíe la invitación de nuevo.
-</div>
+>ℹ️ El enlace para crear la cuenta enviado al seller es válido durante 7 días. Después de hacer clic en el enlace, el seller tiene seis horas para completar el formulario de registro. Si no es posible completar el registro dentro de este periodo, debes pedir al marketplace que envíe la invitación de nuevo.
 
 ### Conectar la cuenta VTEX con el _marketplace_
 
diff --git a/docs/tutorials/es/seller-management.md b/docs/tutorials/es/seller-management.md
index e12b6914e..f23ad1a30 100644
--- a/docs/tutorials/es/seller-management.md
+++ b/docs/tutorials/es/seller-management.md
@@ -89,9 +89,7 @@ Al hacer clic en el botón <i class="fas fa-ellipsis-v"></i> de la línea del _s
 - **Detalles del seller:** redirige a la página de detalles del _seller_ para ver o editar la información.  
 - **Pedidos:** redirige a la página de Todos los Pedidos en el OMS de VTEX, ya filtrando por los pedidos de ese _seller_.  
 
-<div class="alert alert-info">
-  Ten en cuenta que la lista está ordenada por orden alfabético. Para ver los datos de todos los sellers, navega entre las páginas de resultados haciendo clic en las flechas <i class="fas fa-angle-left"></i> y <i class="fas fa-angle-right"></i> en la parte inferior de la página. Utiliza los filtros y la búsqueda para refinar tus resultados.
-  </div>
+>ℹ️ Ten en cuenta que la lista está ordenada por orden alfabético. Para ver los datos de todos los sellers, navega entre las páginas de resultados haciendo clic en las flechas <i class="fas fa-angle-left"></i> y <i class="fas fa-angle-right"></i> en la parte inferior de la página. Utiliza los filtros y la búsqueda para refinar tus resultados.
 
 ### Seller identificable y no identificable (white label)
 
diff --git a/docs/tutorials/es/seller-portal-promotions.md b/docs/tutorials/es/seller-portal-promotions.md
index ea9cc693b..45d735e23 100644
--- a/docs/tutorials/es/seller-portal-promotions.md
+++ b/docs/tutorials/es/seller-portal-promotions.md
@@ -91,6 +91,4 @@ Para acceder a la página **Promociones archivadas**, haz clic en el ícono <i c
 
 Puedes desarchivar o duplicar promociones archivadas haciendo clic en el ícono <i class="fas fa-ellipsis-v"></i>. 
 
- <div class="alert alert-info">
-  <p>Al desarchivar una promoción, su status cambiará a <code>Pausada</code>.</p>
-  </div>
+ >ℹ️ Al desarchivar una promoción, su status cambiará a `Pausada`.
diff --git a/docs/tutorials/es/seller-portal-shared-products.md b/docs/tutorials/es/seller-portal-shared-products.md
index 1211ce4c5..a35433ae4 100644
--- a/docs/tutorials/es/seller-portal-shared-products.md
+++ b/docs/tutorials/es/seller-portal-shared-products.md
@@ -16,7 +16,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
 
-<div class="alert alert-warning"> El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.</div>
+>⚠️ El límite para cada cuenta en el Seller Portal es de 100 mil productos. Para obtener más información, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro equipo de soporte.
 
 **Productos compartidos** es el módulo donde usted gestiona los productos en común entre su catálogo y lo que ya se oferta en el marketplace. El panel de productos compartidos informa todos los productos que el marketplace ha puesto a disposición de su tienda para venta. Son productos sincronizados con el catálogo del marketplace. 
 
diff --git a/docs/tutorials/es/send-the-seller-white-label-payment-methods-to-the-marketplace.md b/docs/tutorials/es/send-the-seller-white-label-payment-methods-to-the-marketplace.md
index afc4f5e82..e80e1346d 100644
--- a/docs/tutorials/es/send-the-seller-white-label-payment-methods-to-the-marketplace.md
+++ b/docs/tutorials/es/send-the-seller-white-label-payment-methods-to-the-marketplace.md
@@ -19,9 +19,7 @@ El objetivo de este tutorial es enseñar cómo enviar los medios de pago de un S
 
 Este feature permite que las compras realizadas en un e-commerce sean hechas con los medios de pago de una tienda física. Esto disminuye la complejidad de la operación, separando centros de costo, pues la factura y los pagos serán vinculados directamente al CNPJ de la tienda física, que actúa como Seller White Label de un Marketplace.
 
-<div class="alert alert-info">
-Esta configuración substituye el uso del antiguo feature de <strong>Cuentas Alternativas</strong> para este escenario.
-</div>
+>ℹ️ Esta configuración substituye el uso del antiguo feature de **Cuentas Alternativas** para este escenario.
 
 ## Registrar medios de pago en el Seller White Label
 
diff --git a/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md b/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
index 500692826..a1c810419 100644
--- a/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
+++ b/docs/tutorials/es/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
@@ -15,9 +15,7 @@ legacySlug: envio-de-los-atributos-de-ropa-calzado-y-bolsos-para-el-mercado-libr
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-El envío de los atributos de productos de tipo Ropas, Calzados o Bolsas sigue un flujo diferente de los demás. En este proceso de mapeo, el resultado es que los SKUs se mostrarán todos en el mismo anuncio. Para los demás tipos de producto, Mercado Libre realiza un mapeo automático.
-</div>
+>ℹ️ El envío de los atributos de productos de tipo Ropas, Calzados o Bolsas sigue un flujo diferente de los demás. En este proceso de mapeo, el resultado es que los SKUs se mostrarán todos en el mismo anuncio. Para los demás tipos de producto, Mercado Libre realiza un mapeo automático.
 
 Para enviar los atributos de los productos de los tipos __Ropas__, __Calzados__ y __Bolsas__ para el Mercado Libre, siga los pasos abajo:
 
@@ -25,9 +23,7 @@ Para enviar los atributos de los productos de los tipos __Ropas__, __Calzados__
 2. Rellene la planilla modelo con los IDs de los SKUs a ser enviados al Mercado Libre y con los valores de atributos aceptados por Mercado Libre. Los valores aceptados se pueden encontrar en los enlaces más abajo.
 3. Guarde la planilla con los valores rellenados.
 
-<div class="alert alert-info">
-Los valores aceptados por Mercado Libre se pueden encontrar en los siguientes abajo. Haga clic en el nombre de su país para descargar. Usted encontrará códigos referentes a <u>Color principal</u>, <u>Color secundario</u>, <u>Talla de calzado para adultos</u>, <u>Talla de calzado para niños</u>, <u>Talla de ropa para adultos</u> y <u>Talla de ropa para niños</u>. Estos valores se deben rellenar correctamente en los campos <strong>Color Principal</strong>, <strong>Color Secundario</strong> y <strong>Talla</strong> de la plantilla. Con excepción del atributo <en>Color Secundario</em>, todos los demás campos son obligatorios (SKU_ID, Color principal y Talla).
-</div>
+>ℹ️ Los valores aceptados por Mercado Libre se pueden encontrar en los siguientes abajo. Haga clic en el nombre de su país para descargar. Usted encontrará códigos referentes a <u>Color principal</u>, <u>Color secundario</u>, <u>Talla de calzado para adultos</u>, <u>Talla de calzado para niños</u>, <u>Talla de ropa para adultos</u> y <u>Talla de ropa para niños</u>. Estos valores se deben rellenar correctamente en los campos **Color Principal**, **Color Secundario** y **Talla** de la plantilla. Con excepción del atributo <en>Color Secundario</em>, todos los demás campos son obligatorios (SKU_ID, Color principal y Talla).
 
 __Links con los valores aceptados por Mercado Libre__:
 
diff --git a/docs/tutorials/es/sending-sku-attributes-to-amazon.md b/docs/tutorials/es/sending-sku-attributes-to-amazon.md
index fabe5fd80..bf0c46b02 100644
--- a/docs/tutorials/es/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/es/sending-sku-attributes-to-amazon.md
@@ -23,9 +23,7 @@ La asignación sólo se realizará una vez para cada categoría. De esta forma,
 
 2. Rellene los campos de la hoja de asignación de acuerdo con las indicaciones siguientes:
 
-<div class="alert alert-danger">
-Nota: si <strong>ningún</strong> de los atributos de su categoría es requerido obligatoriamente por Amazon, entonces <strong>no es necesario hacer el mapeo</strong>. Basta con reindexar sus productos para que sean enviados directamente por la integración.
-</div>
+>❗ Nota: si **ningún** de los atributos de su categoría es requerido obligatoriamente por Amazon, entonces **no es necesario hacer el mapeo**. Basta con reindexar sus productos para que sean enviados directamente por la integración.
 
 1. __ID categoría:__ es el ID de categoría en VTEX. Usted puede encontrarlo en el lado del nombre de cada categoría al expandir el árbol.
 2. __VariationTheme:__ es la manera que el SKU varía en el mercado. Usted debe llenar con los Variations Themes que se adecuan a la categoría de sus productos y respectivos PTDs.
@@ -47,9 +45,7 @@ Planilla de ejemplo usando la categoría Clothing & Accessories:
 
 ![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
-<div class="alert alert-danger">
-Recuerde que estos valores deben estar de acuerdo con los valores acceptados por Amazon. Consulte los términos permitidos y haga el De/Para entre lo que está registrado en su campo SKU en VTEX y los valores acceptador por Amazon.
-</div>
+>❗ Recuerde que estos valores deben estar de acuerdo con los valores acceptados por Amazon. Consulte los términos permitidos y haga el De/Para entre lo que está registrado en su campo SKU en VTEX y los valores acceptador por Amazon.
 
 Después de rellenar la hoja de trabajo, acceda a __Integraciones__ en el menú Admin:
 
diff --git a/docs/tutorials/es/sent-offers-beta.md b/docs/tutorials/es/sent-offers-beta.md
index c232e7f3c..48776310a 100644
--- a/docs/tutorials/es/sent-offers-beta.md
+++ b/docs/tutorials/es/sent-offers-beta.md
@@ -31,9 +31,7 @@ Cuando un seller configura condiciones de precios y stock, prepara su producto p
 - **Con error:** cuando el sistema encuentra un problema que impide que un anuncio se envíe o actualice en un canal. Este status indica que el anuncio requiere corrección manual.  
 - **Indisponible:** cuando el anuncio queda indisponible, porque está inactivo o no está incluido en la Política Comercial determinada para el canal.
 
-<div class="alert alert-info">
-Al hacer clic en <code>Ver lista</code>, será redirigido a la  <a href="https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE">pagina de Anúncios</a>.
-</div>
+>ℹ️ Al hacer clic en `Ver lista`, será redirigido a la  [pagina de Anúncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE).
 
 ## Canales
 
diff --git a/docs/tutorials/es/sent-offers-buybox-opportunities.md b/docs/tutorials/es/sent-offers-buybox-opportunities.md
index dd529c3c7..31c6588c1 100644
--- a/docs/tutorials/es/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/es/sent-offers-buybox-opportunities.md
@@ -15,12 +15,10 @@ legacySlug: anuncios-enviados-oportunidades-de
 subcategory: 
 ---
 
-<div class="alert alert-info">
-Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de <b>Gestión de anuncios</b>.
-Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
-Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del <a href="https://developers.vtex.com/updates/release-notes">Developer Portal</a> y el <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center</a>.
- </div>  
+>ℹ️ Para evolucionar su experiencia al sincronizar y actualizar anuncios, el equipo de VTEX está desarrollando una nueva funcionalidad que sustituirá el módulo de **Gestión de anuncios**.
+> Por este motivo, Gestión de anuncios no recibirá más actualizaciones ni mantenimiento.
+> Para conectores y marketplaces que ya se integraron con el módulo, comuníquese con nuestro equipo de desarrollo por email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para los conectores interesados en comenzar la integración, les pedimos que esperen el lanzamiento del nuevo módulo, tan pronto como esté disponible, notificaremos a todos los clientes a través del [Developer Portal](https://developers.vtex.com/updates/release-notes) y el [VTEX Help Center](https://help.vtex.com/pt/en/announcements).  
 
 Un Anuncio es un SKU cuyo precio y stock fueron configurados por un seller y que fue enviado a diferentes canales de venta. El módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) del Admin VTEX permite a los sellers supervisar el envío y la sincronización de sus productos a los marketplaces y también brinda oportunidades para obtener más ventas con sus anuncios. 
 
@@ -65,9 +63,7 @@ Siga los pasos a continuación para añadir su anuncio a la Catálogo MeLi:
 4. En la página **Oportunidad del anuncio**, evalúe si su anuncio es compatible con el anuncio que ya está en el *marketplace*. Si son compatibles, haga clic en `Agregar a lo Catálogo MeLi`. 
 5. Haga clic en `Agregar`. 
 
-<div class="alert alert-warning">
-Esta acción no se puede deshacer, así que debe asegurarse de que los anuncios sean compatibles. Si un anuncio no es compatible con el producto que ya está presente en el marketplace, no lo añada a lo Catálogo MeLi. Añadir anuncios que no son parte del producto puede perjudicar su reputación como seller en el marketplace. 
-</div>
+>⚠️ Esta acción no se puede deshacer, así que debe asegurarse de que los anuncios sean compatibles. Si un anuncio no es compatible con el producto que ya está presente en el marketplace, no lo añada a lo Catálogo MeLi. Añadir anuncios que no son parte del producto puede perjudicar su reputación como seller en el marketplace.
 
 Para que su anuncio esté bien posicionado en lo Catálogo MeLi, finalice los ajustes indicados en la sección de este artículo [Ganando y perdiendo en la Buybox](#ganando-y-perdiendo-en-la-buybox).
 
diff --git a/docs/tutorials/es/sequencial-suiteshare.md b/docs/tutorials/es/sequencial-suiteshare.md
index 8a4ae87ac..6fb40b754 100644
--- a/docs/tutorials/es/sequencial-suiteshare.md
+++ b/docs/tutorials/es/sequencial-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: sequencial
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/set-up-alelo-payment-method-for-cielo-v3.md b/docs/tutorials/es/set-up-alelo-payment-method-for-cielo-v3.md
index 17d98a2ee..2172cbb70 100644
--- a/docs/tutorials/es/set-up-alelo-payment-method-for-cielo-v3.md
+++ b/docs/tutorials/es/set-up-alelo-payment-method-for-cielo-v3.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 En este artículo, explicaremos cómo habilitar el vale de alimentación Alelo como medio de pago en el Checkout.
 
-<div class="alert alert-info">
-<strong>Atención</strong>: el vale de alimentación Alelo es un medio de pago aceptado apenas entre clientes brasileños.
-</div>
+>ℹ️ **Atención**: el vale de alimentación Alelo es un medio de pago aceptado apenas entre clientes brasileños.
 
 Actualmente, en VTEX, Cielo es el adquirente que acepta a Alelo como medio de pago. Por lo tanto, el primer paso es habilitar este adquirente como afiliación de gateway en su tienda. Puede consultar el tutorial completo sobre cómo hacer esta configuración [aquí](https://help.vtex.com/es/tutorial/configurar-adquirente-cielo--3avjZ7q65WcM02K8K0eeWu?locale=es "aquí"). 
 
@@ -41,6 +39,4 @@ Ahora, siga las instrucciones:
 8. En el lado derecho de la pantalla, establezca las __condiciones especiales__ de pago.
 9. Haga clic en el botón azul __“Guardar”__ para terminar.
 
-<div class="alert alert-info">
-<strong>Atención</strong>: recuerde que las condiciones especiales de pago tardan unos 10 minutos en aplicarse en el Checkout.
-</div>
+>ℹ️ **Atención**: recuerde que las condiciones especiales de pago tardan unos 10 minutos en aplicarse en el Checkout.
diff --git a/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md b/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md
index 5e15dc3db..124394481 100644
--- a/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md
+++ b/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md
@@ -23,9 +23,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Antes de iniciar la configuración, es necesario abrir un ticket con el equipo de soporte de VTEX solicitando la activación de 3DS 2 en su tienda. Para más información acceda al [cómo abrir un ticket](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-<div class="alert alert-warning">
-En VTEX, el flujo 3DS 2 no se aplica para realizar compras con dos tarjetas. En caso de que un pedido se realice en esas condiciones, el pago se cancelará.
-</div>
+>⚠️ En VTEX, el flujo 3DS 2 no se aplica para realizar compras con dos tarjetas. En caso de que un pedido se realice en esas condiciones, el pago se cancelará.
 
 ## Configuración de 3DS 2
 
@@ -39,6 +37,4 @@ Para configurar la autenticación 3DS 2 en las afiliaciones, siga los pasos a co
 6. En el campo __Suporte 3DS 2.0__, seleccione la opción __“Yes”__.
 7. Haga clic en __Guardar__. 
 
-<div class="alert alert-warning">
-  La descripción del campo 3DS 2 (<b>"Suporte 3DS 2.0"</b>, informado en el Paso 8) puede variar según el tipo de proveedor de pago que se configure. Consulte con el soporte técnico de su proveedor de pago elegido para identificar el campo correcto para seleccionar para habilitar la autenticación 3DS 2.
-</div>
+>⚠️ La descripción del campo 3DS 2 (**"Suporte 3DS 2.0"**, informado en el Paso 8) puede variar según el tipo de proveedor de pago que se configure. Consulte con el soporte técnico de su proveedor de pago elegido para identificar el campo correcto para seleccionar para habilitar la autenticación 3DS 2.
diff --git a/docs/tutorials/es/setting-up-a-personal-gift-message.md b/docs/tutorials/es/setting-up-a-personal-gift-message.md
index 66acede0a..e1950fc0a 100644
--- a/docs/tutorials/es/setting-up-a-personal-gift-message.md
+++ b/docs/tutorials/es/setting-up-a-personal-gift-message.md
@@ -50,6 +50,4 @@ Puede ver el mensaje escrito en la página de __Mi Cuenta > Mis Pedidos__:
 
 ![](https://images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
 
-<div class="alert alert-info">
-  <p>Después de configurar el servicio en el SKU aguarde la indexación para que el registro tenga efecto en el sitio. Después de esto ya será posible probar la compra con este servicio activo.</p>
-</div>
+>ℹ️ Después de configurar el servicio en el SKU aguarde la indexación para que el registro tenga efecto en el sitio. Después de esto ya será posible probar la compra con este servicio activo.
diff --git a/docs/tutorials/es/setting-up-abandoned-carts.md b/docs/tutorials/es/setting-up-abandoned-carts.md
index 7ecb5270e..9b1a38a1f 100644
--- a/docs/tutorials/es/setting-up-abandoned-carts.md
+++ b/docs/tutorials/es/setting-up-abandoned-carts.md
@@ -42,9 +42,7 @@ Puede crear su propio template de email personalizado o utilizar la opción de e
 
 ![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
 
-<div class="alert alert-warning">
-Recomendamos que lo realicen profesionales familiarizados con el módulo CMS, que ya hayan realizado la configuración de otros templates de página y expositor.
-</div>
+>⚠️ Recomendamos que lo realicen profesionales familiarizados con el módulo CMS, que ya hayan realizado la configuración de otros templates de página y expositor.
 
 1. En el Admin VTEX, accede a __Storefront > Layout__, o escribe __Envío por geolocalización__ en la barra de búsqueda en la parte superior de la página.
 2. En __CMS > HTML Templates__, haga clic en el icono `CEM-Abandoned-Cart`.
@@ -95,8 +93,7 @@ El filtro "Checkout" establece una de las condiciones para que se dispare el tri
 
 Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho que ambos sean semejantes, los comportamientos son diferentes. El "Carrito" se refiere a los últimos productos que el cliente agregó en el carrito de compras propiamente dicho. El "Último carrito" consiste en el registro de fecha y hora en que se creó el carrito.
 
-<div class="alert alert-warning">Para que se realice el disparo de trigger, los tres filtros deben, obligatoriamente, rellenarse de acuerdo con el siguiente ejemplo. 
-</div>
+>⚠️ Para que se realice el disparo de trigger, los tres filtros deben, obligatoriamente, rellenarse de acuerdo con el siguiente ejemplo.
 
 <blockquote><ui>1. En el Admin VTEX, accede <b>Configuración de la tienda</b> > <b>Storefront</b> > <b>Master Data.</b></ui>
 
@@ -128,9 +125,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 ![Filter master data 2](https://images.ctfassets.net/alneenqid6w5/6aME0zp72kjwJiulRdoRNl/d6c7e5d4e84c5d2b8b870de4ee0db4bc/Filter_Master_Data.PNG)
 
-<div class="alert alert-warning">
-  Además de los filtros indicados anteriormente, se recomienda insertar otro filtro en el siguiente formato: <code>Receives newsletter? - Equal to - True</code>. Esto garantiza el cumplimiento de los <a href="https://help.vtex.com/es/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM">derechos de los titulares de datos</a>, ya que solo los clientes suscritos al boletín recibirán correos electrónicos de carritos abandonados. La suscripción al boletín de su tienda se puede realizar en el momento de la compra o en la sección <a href="https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile">Mi Cuenta</a> de su tienda.
-</div>
+>⚠️ Además de los filtros indicados anteriormente, se recomienda insertar otro filtro en el siguiente formato: `Receives newsletter? - Equal to - True`. Esto garantiza el cumplimiento de los [derechos de los titulares de datos](https://help.vtex.com/es/tutorial/data-subject-rights--6imchxTx09icupKMbzHVIM), ya que solo los clientes suscritos al boletín recibirán correos electrónicos de carritos abandonados. La suscripción al boletín de su tienda se puede realizar en el momento de la compra o en la sección [Mi Cuenta](https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh#profile) de su tienda.
 
 <blockquote><ui> 10. Haga clic en pestaña <b>Schedule</b> (Programación) y seleccione si desea enviar el correo electrónico en una fecha específica o en una fecha dinámica.</ui>
 
@@ -142,8 +137,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><blockquote><ui>b. En <b>Recipient</b> (Destinatario), para realizar una prueba del sistema, ingrese su email y haga clic en <b>Add Static email</b> (Añadir email estático).</ui>
 
-<div class="alert alert-warning">Una vez que haya completado las otras configuraciones a continuación y haya verificado que recibió el mensaje de carrito abandonado en su email, regrese a este paso, seleccione la opción <strong>CL</strong>: <strong>Email</strong>, haga clic en <strong>Add Dynamic email</strong> (Añadir email dinámico), y luego en <strong>Save</strong>.
-</div>
+>⚠️ Una vez que haya completado las otras configuraciones a continuación y haya verificado que recibió el mensaje de carrito abandonado en su email, regrese a este paso, seleccione la opción **CL**: **Email**, haga clic en **Add Dynamic email** (Añadir email dinámico), y luego en **Save**.
 
 <blockquote><blockquote><ui>c. En <b>Email body format</b> (Formato del cuerpo del email), seleccione <b>Html</b>.</ui>
 
@@ -159,8 +153,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
   ![PastasCarrinhoAbandonado](https://images.ctfassets.net/alneenqid6w5/4DSsVaeDvWmaaw2iwySCOy/b579eb818e0bcda140dba0ae96ecc90f/PastasCarrinhoAbandonado.png)
 
-<div class="alert alert-warning">Esta URL debe ser la final de la tienda, y no la URL con vtexcommercestable.
-</div>
+>⚠️ Esta URL debe ser la final de la tienda, y no la URL con vtexcommercestable.
 
 <blockquote><blockquote><ui>i. En <b>Add utm_source to all links whose value is</b>, rellene con "CEM", para facilitar la identificación de compras por el carrito abandonado.</ui>
 
@@ -168,8 +161,7 @@ Además, tenemos incluso los filtros "Carrito" y "Último carrito". Por mucho qu
 
 <blockquote><blockquote><ui>k. Haga clic en el botón <b>Save</b>.</ui>
 
-<div class="alert alert-warning">La sesión de una página expira en 30 minutos. Solamente después de ese tiempo consideramos la programación del disparo de trigger de Carrito Abandonado. Es decir, el tiempo a ser considerado es el tiempo de la sesión + la programación de trigger. 
-</div>
+>⚠️ La sesión de una página expira en 30 minutos. Solamente después de ese tiempo consideramos la programación del disparo de trigger de Carrito Abandonado. Es decir, el tiempo a ser considerado es el tiempo de la sesión + la programación de trigger.
 
 ![If positive tab](https://images.ctfassets.net/alneenqid6w5/2GDAJ2St3ayiKjcWoONDRc/d863f83956f876035351cd222a0482ad/If_positive_Tab.PNG)
 
diff --git a/docs/tutorials/es/setting-up-alternative-accounts.md b/docs/tutorials/es/setting-up-alternative-accounts.md
index ad15fef2e..5de9ee73c 100644
--- a/docs/tutorials/es/setting-up-alternative-accounts.md
+++ b/docs/tutorials/es/setting-up-alternative-accounts.md
@@ -15,6 +15,4 @@ legacySlug: configurar-cuentas-alternativas
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-info">
-El recurso de Cuentas Alternativas fue descontinuado. Para sustituirlo, utiliza la solución de Cuentas Franquicia y Sellers White Label. Lee <a href="http://help.vtex.com/es/faq/que-son-cuenta-franquicia-y-seller-white-label">este artículo</a> para obtener más detalles.
-</div>
+>ℹ️ El recurso de Cuentas Alternativas fue descontinuado. Para sustituirlo, utiliza la solución de Cuentas Franquicia y Sellers White Label. Lee [este artículo](http://help.vtex.com/es/faq/que-son-cuenta-franquicia-y-seller-white-label) para obtener más detalles.
diff --git a/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
index 193bdaf91..98a088433 100644
--- a/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/es/setting-up-app-linking-for-payments-app-in-instore.md
@@ -37,9 +37,7 @@ Si es necesario, inStore puede enviar información adicional. Ejemplo con el sub
 - `administrativePassword`: string - contraseña predeterminada, por ejemplo, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-Para crear cualquier configuración extra, usted debe enviar al equipo de inStore (instoredevs@vtex.com) los extras que la aplicación necesita para completar la transacción. Así, crearemos un formulario en el módulo de Pagos para que el cliente pueda configurar su adquirente.
-</div>
+>ℹ️ Para crear cualquier configuración extra, usted debe enviar al equipo de inStore (instoredevs@vtex.com) los extras que la aplicación necesita para completar la transacción. Así, crearemos un formulario en el módulo de Pagos para que el cliente pueda configurar su adquirente.
 
 ## URI de envío y URI de respuesta para cada acción
 
@@ -124,9 +122,8 @@ URI final que la aplicación de pago recibirá para ejecutar la acción de reemb
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&autoConfirm=True&sellerName=instoreqa&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class="alert alert-warning">>
-<strong>NOTA:</strong> No todos los parámetros serán utilizados por todos los adquirentes/apps de pago. Ejemplo: <code>transactionId</code>. Este parámetro es el ID de una transacción en VTEX que identifica todos los pagos de un pedido completo en el PCI Gateway de VTEX. Una transacción puede contener varios pagos, como cuando un pedido se paga con varias tarjetas de crédito o débito.
-</div>
+>⚠️ >
+> **NOTA:** No todos los parámetros serán utilizados por todos los adquirentes/apps de pago. Ejemplo: `transactionId`. Este parámetro es el ID de una transacción en VTEX que identifica todos los pagos de un pedido completo en el PCI Gateway de VTEX. Una transacción puede contener varios pagos, como cuando un pedido se paga con varias tarjetas de crédito o débito.
 
 ## Ejemplos de URI de respuesta para cada acción
 
@@ -185,9 +182,8 @@ Para que la integración funcione, es necesario que el cliente configure en el m
 
 La integración de AppLinking no incluye otras dependencias, ya que la comunicación entre la app inStore y la appp de pago se realiza con URIs específicas que contienen todos los parámetros de configuración y pago necesarios para la acción.
 
-<div class="alert alert-warning">>
-En Android, toda comunicación debe suceder con un nuevo <code>Intent</code>. Esto significa que usted no debe enviar la respuesta como un retorno de llamada del <code>Intent</code> inicial. En su lugar, debe enviar un nuevo <code>Intent</code> a la aplicación inStore con la respuesta anterior.
-</div>
+>⚠️ >
+> En Android, toda comunicación debe suceder con un nuevo `Intent`. Esto significa que usted no debe enviar la respuesta como un retorno de llamada del `Intent` inicial. En su lugar, debe enviar un nuevo `Intent` a la aplicación inStore con la respuesta anterior.
 
 Para configurar el conector de InStore, usteddebe seguir estos pasos:
 
diff --git a/docs/tutorials/es/setting-up-b2b-on-vtex.md b/docs/tutorials/es/setting-up-b2b-on-vtex.md
index ba8568ce6..61a469f9d 100644
--- a/docs/tutorials/es/setting-up-b2b-on-vtex.md
+++ b/docs/tutorials/es/setting-up-b2b-on-vtex.md
@@ -65,9 +65,7 @@ El usuario que aún no está registrado en el sitio necesita tener una interface
 
 Así, es necesario definir los campos de este registro previo. Normalmente, los B2Bs usan información de cliente (nombre, e-mail, teléfono, etc.) y dirección (calle, barrio, ciudad, etc.) para este registro previo. Consulte el artículo [Importar datos de clientes](https://help.vtex.com/es/tutorial/importando-dados-de-clientes-brasil--2zWYVOyj0sISYQmeUwCsI0 "Importar datos de clientes - Brasil") para obtener más información sobre los datos necesarios.
 
-<div class="alert alert-warning">
-  <p>El campo utilizado como regla condicional en la política comercial nunca podrá hacer parte de este formulario, una vez que el propio usuario no puede realizar su propia aprobación. Esta responsabilidad es de la tienda.</p>
-</div>
+>⚠️ El campo utilizado como regla condicional en la política comercial nunca podrá hacer parte de este formulario, una vez que el propio usuario no puede realizar su propia aprobación. Esta responsabilidad es de la tienda.
 
 ## 4. Crear formulario de registro prévio
 
@@ -79,6 +77,4 @@ La información colocada en el formulario deberá ser enviada al CRM a través d
 
 Con todo configurado y, finalmente, el B2B en producción, la rutina del dueño de la tienda dependerá de las reglas y necesidades de su negocio. Básicamente, a cada nuevo registro, el dueño de la tienda deberá evaluar al usuario, aprobándolo o no, en la interface del CRM, al que se puede acceder a través de la URL `http://{nombre_de_cuenta}.vtexcrm.com.br/`.
 
-<div class="alert alert-info">
-  <p>Este artículo describe las configuraciones básicas de un B2B, pero, es posible personalizar el sistema para esa necesidad de varias formas, incluso enviando emails (triggers) a partir de eventos predefinidos.</p>
-</div>
+>ℹ️ Este artículo describe las configuraciones básicas de un B2B, pero, es posible personalizar el sistema para esa necesidad de varias formas, incluso enviando emails (triggers) a partir de eventos predefinidos.
diff --git a/docs/tutorials/es/setting-up-conductor-gateway.md b/docs/tutorials/es/setting-up-conductor-gateway.md
index 19e517d05..867692aa6 100644
--- a/docs/tutorials/es/setting-up-conductor-gateway.md
+++ b/docs/tutorials/es/setting-up-conductor-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-conductor
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Conductor es un [gateway de pagos](/es/tutorial/que-es-un-gateway-de-pagos) con certificación [PCI](/es/faq/que-es-el-pci-ssc) que actúa desde hace más de 20 años con el procesamiento de pagos. En VTEX, se puede configurar para procesar pagos realizados con __tarjetas de crédito con bandera propia__.
 
diff --git a/docs/tutorials/es/setting-up-cybersource-antifraud.md b/docs/tutorials/es/setting-up-cybersource-antifraud.md
index 3760516c8..3ce051dab 100644
--- a/docs/tutorials/es/setting-up-cybersource-antifraud.md
+++ b/docs/tutorials/es/setting-up-cybersource-antifraud.md
@@ -21,9 +21,7 @@ Si usted está buscando más detalles sobre el __gateway__ CyberSource, lea [est
 
 ## Configurar antifraude CyberSource
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de realizar el Paso 6. de esta sección.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de realizar el Paso 6. de esta sección.
 
 1. En el Admin VTEX, accede a  __Configuración de la tienda > Pago > Proveedores__, o escribe __Proveedores__ en la barra de búsqueda en la parte superior de la página.
 2. En la pantalla de proveedores, haga clic en el botón `Nuevo proveedor`.
@@ -51,6 +49,4 @@ Después de configurar el antifraude de CyberSource, estará disponible para uso
 6. Seleccione CyberSource.
 7. Haga clic en `Guardar`.
 
-<div class="alert alert-warning">
-Para que una transacción pase por el análisis del antifraude, <strong>la condición de pago utilizada por el cliente debe estar asociada a él</strong>.
-</div>
+>⚠️ Para que una transacción pase por el análisis del antifraude, **la condición de pago utilizada por el cliente debe estar asociada a él**.
diff --git a/docs/tutorials/es/setting-up-cybersource-gateway.md b/docs/tutorials/es/setting-up-cybersource-gateway.md
index a3cd5e592..6973fec72 100644
--- a/docs/tutorials/es/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/es/setting-up-cybersource-gateway.md
@@ -37,9 +37,7 @@ Las siguientes aplicaciones Cybersource deben estar instaladas en su cuenta de t
 - __vtex.cybersource__
 - __vtex.cybersource-payer-auth__
 
-<div class="alert alert-warning">
-Si tiene la intención de utilizar el sistema antifraude de Cybersource, pero desea realizar transacciones de pagos en un gateway que no sea de Cybersource, deberá instalar la aplicación <b>vtex.cybersource-fraud</b>.
-  </div>
+>⚠️ Si tiene la intención de utilizar el sistema antifraude de Cybersource, pero desea realizar transacciones de pagos en un gateway que no sea de Cybersource, deberá instalar la aplicación **vtex.cybersource-fraud**.
 
 Conozca más sobre la instalación de aplicaciones en una cuenta VTEX en [Installing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app). 
 
@@ -47,9 +45,7 @@ Conozca más sobre la instalación de aplicaciones en una cuenta VTEX en [Instal
 
 Después de instalar las aplicaciones, debe crear claves de autenticación en el entorno Cybersource.
 
-<div class="alert alert-warning">
-  Las configuraciones realizadas en un ambiente externo a VTEX podrán ser discontinuadas o modificadas sin previo aviso. Consulte su cuenta Cybersource para obtener información actualizada.
-  </div>
+>⚠️ Las configuraciones realizadas en un ambiente externo a VTEX podrán ser discontinuadas o modificadas sin previo aviso. Consulte su cuenta Cybersource para obtener información actualizada.
 
 Siga los pasos a continuación:
 
@@ -139,8 +135,7 @@ Para procesar pagos con tarjeta de crédito a través de Cybersource, siga los p
 8. Si desea, puede [configurar condiciones especiales de pago](https://help.vtex.com/es/tutorial/condiciones-especiales--tutorials_456). 
 9. Haga clic en __Guardar__.
 
-<div class="alert alert-warning">
-  Si anteriormente creó condiciones de pago con tarjeta de crédito para otros gateways (incluido el proveedor Cybersource legado), puede establecer esas condiciones en <b>Inactivas</b>. Las transacciones en curso iniciadas desde ese proveedor seguirán siendo procesadas por ese proveedor, incluso si está inactivo. El nuevo proveedor de Cybersource IO solo procesará las transacciones nuevas. Si necesita volver a su proveedor anterior por algún motivo, simplemente establezca sus condiciones de pago en <b>Activas</b> y las condiciones de pago de Cybersource IO en <b>Inactivas</b>.</div>
+>⚠️ Si anteriormente creó condiciones de pago con tarjeta de crédito para otros gateways (incluido el proveedor Cybersource legado), puede establecer esas condiciones en **Inactivas**. Las transacciones en curso iniciadas desde ese proveedor seguirán siendo procesadas por ese proveedor, incluso si está inactivo. El nuevo proveedor de Cybersource IO solo procesará las transacciones nuevas. Si necesita volver a su proveedor anterior por algún motivo, simplemente establezca sus condiciones de pago en **Activas** y las condiciones de pago de Cybersource IO en **Inactivas**.
 
 ## Configurar Cybersource IO Device Fingerprint (opcional)
 
@@ -148,9 +143,7 @@ Device Fingerprint es un identificador que actúa en el procesamiento de un pago
 
 Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
 
 Para configurar Device Fingerprint Cybersource IO, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/setting-up-device-fingerprint-for-niubiz.md b/docs/tutorials/es/setting-up-device-fingerprint-for-niubiz.md
index b1eb35a51..f110bca6d 100644
--- a/docs/tutorials/es/setting-up-device-fingerprint-for-niubiz.md
+++ b/docs/tutorials/es/setting-up-device-fingerprint-for-niubiz.md
@@ -19,9 +19,7 @@ __Device Fingerprint__ es un identificador que actúa en el procesamiento de un
 
 Mediante la recolección de datos no sensibles, Device Fingerprint identifica y analiza el nivel de seguridad del dispositivo utilizado para realizar la transacción, así como las transacciones que se realizaron previamente con este mismo dispositivo.
 
-<div class="alert alert-info">
-Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
-</div>
+>ℹ️ Cada tienda debe tener solo un registro de Device fingerprint. Verifique si ya ha registrado el Device Fingerprint en otro conector, antes de continuar con los pasos siguientes.
 
 En este artículo, explicaremos cómo asociar Device Fingerprint con la afiliación Niubiz.  
 
@@ -29,9 +27,7 @@ Para ello, es necesario generar un identificador a través de [Google Tag Manage
 
 ### Crear el identificador
 
-<div class="alert alert-info">
-Las instrucciones para esta etapa del artículo se realizan en un ambiente externo. Por lo tanto, pueden estar desactualizadas.
-</div>
+>ℹ️ Las instrucciones para esta etapa del artículo se realizan en un ambiente externo. Por lo tanto, pueden estar desactualizadas.
 
 En primer lugar, tendrá que crear el identificador.
 
@@ -104,9 +100,7 @@ Dicho esto, consulte las instrucciones:
 
 De esta forma, Google Tag Manager creará el identificador. 
 
-<div class="alert alert-warning">
-Anote el ID en un lugar donde no lo vaya a perder.
-</div>
+>⚠️ Anote el ID en un lugar donde no lo vaya a perder.
 
 ###  Configuración en el Admin de VTEX 
 
diff --git a/docs/tutorials/es/setting-up-firstdata-acquirer.md b/docs/tutorials/es/setting-up-firstdata-acquirer.md
index 673c4a69a..060591ac1 100644
--- a/docs/tutorials/es/setting-up-firstdata-acquirer.md
+++ b/docs/tutorials/es/setting-up-firstdata-acquirer.md
@@ -15,7 +15,7 @@ legacySlug: configurar-adquirente-firstdata
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En VTEX es posible la integración con FirstData. Con este proveedor tu comercio podrá realizar ventas mediante tarjetas de crédito, débito y Plan Ahora (sistema de pagos argentino).
 
diff --git a/docs/tutorials/es/setting-up-future-inventory.md b/docs/tutorials/es/setting-up-future-inventory.md
index be8575131..b60c0f1a3 100644
--- a/docs/tutorials/es/setting-up-future-inventory.md
+++ b/docs/tutorials/es/setting-up-future-inventory.md
@@ -15,17 +15,13 @@ legacySlug: configurar-inventario-futuro
 subcategory: 32vrn4K2ZscjUaIBe6w5fm
 ---
 
-<div class="alert alert-info">
-<p>Esta funcionalidad está en etapa closed Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad está en etapa closed Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 Para algunas operaciones de e-commerce, es útil tener la capacidad de vender un artículo que no está disponible para entrega inmediata, pero que tiene una fecha estimada de llegada al stock. La funcionalidad __Inventario Futuro__ permite precisamente eso.
 
 ## Cómo funciona el Inventario Futuro
 
-<div class="alert alert-warning">
-Actualmente, la configuración de Inventario Futuro solo está disponible <a target="_blank" href="https://developers.vtex.com/reference/inventory#savesupplylot">a través de API</a>.
-</div>
+>⚠️ Actualmente, la configuración de Inventario Futuro solo está disponible <a target="_blank" href="https://developers.vtex.com/reference/inventory#savesupplylot">a través de API</a>.
 
 La API de Inventario Futuro le permite registrar un __lote de suministro__. Este lote representa el inventario futuro y contiene dos datos principales:
 - Cantidad de artículos.
@@ -37,8 +33,7 @@ En este caso, las compras de estos SKU consumirán los artículos disponibles en
 
 >Tiempo de entrega final = SLA de entrega + Fecha límite para recibir el lote de suministro
 
-<div class="alert alert-info">
-Si la fecha de recepción es anterior a la fecha del cálculo del envío, el tiempo adicional será 0 (cero), ya que, en este caso, el lote de suministro ya se recibió.</div>
+>ℹ️ Si la fecha de recepción es anterior a la fecha del cálculo del envío, el tiempo adicional será 0 (cero), ya que, en este caso, el lote de suministro ya se recibió.
 
 Consulte la documentación del endpoint utilizado para guardar un inventario futuro:
 [Guardar lote de suministros](https://developers.vtex.com/reference/inventory#savesupplylot)
@@ -58,9 +53,7 @@ Cuando utilice la API de Inventario Futuro, tenga en cuenta las siguientes restr
 
 Es posible transferir el inventario de un lote de suministro al inventario de entrega inmediata. Esta transferencia hace que los artículos se consideren disponibles de inmediato. Con eso, ya no hay que agregar tiempo al SLA de entrega para ellos.
 
-<div class="alert alert-info">
-La transferencia para entrega inmediata libera espacio para registrar un nuevo lote. Es decir, si su tienda tiene 10 lotes registrados (límite permitido) y transfiere 2 de ellos para entrega inmediata, ahora tiene 8 lotes registrados y 2 espacios disponibles.
-</div>
+>ℹ️ La transferencia para entrega inmediata libera espacio para registrar un nuevo lote. Es decir, si su tienda tiene 10 lotes registrados (límite permitido) y transfiere 2 de ellos para entrega inmediata, ahora tiene 8 lotes registrados y 2 espacios disponibles.
 
 Consulte la documentación del endpoint utilizado para transferir un inventario futuro para entrega inmediata:
 [Transferir lote de suministros](https://developers.vtex.com/reference/inventory#transfersupplylot)
diff --git a/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md b/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md
index fdf54ee33..9d3d9c920 100644
--- a/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md
+++ b/docs/tutorials/es/setting-up-itau-registered-ticket-itau-registrado.md
@@ -15,7 +15,7 @@ legacySlug: configurar-boleto-registrado-itau-itau-registrado
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Para configurar el boleto registrado de Itaú, usted puede elegir entre dos conectores diferentes: __Invoice Itaú__ (también conocido como Itaú Registrado o Boleto Itaú, que vas a aprender a configurar en este artículo) o el [ItauShopline](https://help.vtex.com/es/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq). En el caso del __Invoice Itaú__, la generación del boleto es hecha de forma transparente (sin redireccionamiento para el sitio del Itaú), pero la conciliación es hecha a través de archivos.
 
diff --git a/docs/tutorials/es/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md b/docs/tutorials/es/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
index 337dbfd7a..574fcc6c7 100644
--- a/docs/tutorials/es/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
+++ b/docs/tutorials/es/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
@@ -25,9 +25,7 @@ Para cada uno de estos métodos de pago existen diferentes requisitos de configu
     - __Klarna__: es necesario [configurar la afiliación Klarna](/es/tutorial/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method#configurar-afiliacion-klarna) y instalar la aplicación _vtexdemoemea.klarna@2.0.9_ (o una versión superior) en su tienda. Obtenga más información sobre cómo instalar la aplicación en [Installing an app](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-installing-an-app).
     - __Adyen__: es necesario [configurar la afiliación Adyen](https://help.vtex.com/es/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337). Para completar esta configuración, solicite a Adyen que habilite el campo __Live Endpoint URL Prefix__ en su tienda e rellene el de acuerdo con la información descrita en [esta documentación de Adyen](https://www.adyen.help/hc/en-us/articles/360014322079-How-can-I-find-the-endpoint-URL-for-my-LIVE-account-).
 
-<div class="alert alert-warning">
-Las soluciones Klarna Pay Now y Klarna Pay Later solo están habilitadas para SmartCheckout V6, y solamente los clientes del mercado europeo y estadounidense pueden utilizarlas. Estos medios de pago no son aplicables para clientes brasileños.
-</div>
+>⚠️ Las soluciones Klarna Pay Now y Klarna Pay Later solo están habilitadas para SmartCheckout V6, y solamente los clientes del mercado europeo y estadounidense pueden utilizarlas. Estos medios de pago no son aplicables para clientes brasileños.
 
 ## Configurar afiliación Klarna 
 
@@ -41,9 +39,7 @@ Para configurar la afiliación Klarna, siga las instrucciones a continuación:
 6. Rellene los campos de registro __Application Key__ y __Application Token__ con la información proporcionada por el proveedor de pago Klarna.
 7. Haga clic en __Guardar__.  
 
-<div class="alert alert-warning">
-  Si utiliza el conector de Klarna en un ambiente de Prueba, el campo <b>Application Key</b> debe ser configurado como <i>playground.{Klarna User}</i>. Cuando se utiliza en un ambiente de Producción, el campo <b>Application Key</b> debe ser su <i>Klarna User</i>.
-</div>
+>⚠️ Si utiliza el conector de Klarna en un ambiente de Prueba, el campo **Application Key** debe ser configurado como <i>playground.{Klarna User}</i>. Cuando se utiliza en un ambiente de Producción, el campo **Application Key** debe ser su <i>Klarna User</i>.
 
 ## Configurar Klarna Pay Now
 
diff --git a/docs/tutorials/es/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md b/docs/tutorials/es/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
index 570998445..c8eeb6a82 100644
--- a/docs/tutorials/es/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
+++ b/docs/tutorials/es/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
@@ -41,9 +41,7 @@ Para configurar Mercado Pago Offline, siga estos pasos:
   <br>
   <li>Haga clic en el botón <b>Status</b> para activar la regra.</li>
 <br>
-<div class="alert alert-info">
-  No es necesario seleccionar el campo <strong>Proceso com la afiliación</strong>, ya que el subadquirente MercadoPagoV2 ya está configurado como afiliación por defecto para MercadoPagoOff.
-</div>
+>ℹ️ No es necesario seleccionar el campo **Proceso com la afiliación**, ya que el subadquirente MercadoPagoV2 ya está configurado como afiliación por defecto para MercadoPagoOff.
 <br>
   <li>Si opta por utilizar la función antifraude, habilite la opción <b>Usando Antifraude</b> y elija una de las opciones antifraude disponibles.</li>
   <br>
diff --git a/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md b/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md
index ad81a5078..e293b040d 100644
--- a/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md
+++ b/docs/tutorials/es/setting-up-mercadopagov1-sub-acquirer.md
@@ -15,13 +15,11 @@ legacySlug: configurar-el-subadquirente-mercadopagov1
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En el Gateway de VTEX, puede configurar el [subadquirente](/es/tutorial/que-es-un-subadquirente) MercadoPago para operar de varias formas. El __MercadoPagoV1__ permite que su tienda reciba pagos con tarjetas de débito y crédito, además de la [cartera digital](/es/faq/que-es-una-billetera-digital-e-wallet) Mercado Pago.
 
-<div class="alert alert-warning">
-La integración <strong>MercadoPagoV1</strong> no admite pagos por boleto bancario.
-</div>
+>⚠️ La integración **MercadoPagoV1** no admite pagos por boleto bancario.
 
 Para configurar MercadoPagoV1, siga los siguientes pasos:
 
diff --git a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
index 1e010b856..660f0b4f9 100644
--- a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
@@ -15,9 +15,7 @@ legacySlug: configurar-merchant-id-en-apple-pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Este proceso será más sencillo cuando Apple valide las integraciones con la plataforma VTEX. Este artículo se actualizará para satisfacer al nuevo escenario.
-</div>
+>⚠️ Este proceso será más sencillo cuando Apple valide las integraciones con la plataforma VTEX. Este artículo se actualizará para satisfacer al nuevo escenario.
 
 Para que su tienda reciba pagos con __Apple Pay__, necesitará configurar el __Merchant ID__ en su cuenta de desarrollador en Apple (`developer.apple.com`). 
 
@@ -133,9 +131,7 @@ Ahora, debe generar un certificado del Merchant ID, que se utilizará cada vez q
 
 Para completar la acción, deberá crear una contraseña para proteger los datos exportados.
 
-<div class="alert alert-info">
-Atención: Recomendamos que la contraseña sea fácil de recordar, ya que se ingresará en el campo Apple Merchant Password en el momento de la configuración de la afiliación de gateway en VTEX.
-</div>
+>ℹ️ Atención: Recomendamos que la contraseña sea fácil de recordar, ya que se ingresará en el campo Apple Merchant Password en el momento de la configuración de la afiliación de gateway en VTEX.
 
 1. Acceda al módulo __Certificates, Identifiers & Profilers__.
 2. En el menú del lado izquierdo, haga clic en __Identifiers__.
diff --git a/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md b/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md
index 71ca35aa3..60a49ce1a 100644
--- a/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md
+++ b/docs/tutorials/es/setting-up-mundipagg-fraud-prevention-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-mundipagg-fraud-prevention
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Mundipagg ofrece una versión de su [gateway](/es/tutorial/que-es-un-gateway-de-pagos) con la funcionalidad de antifraude. El Mundipagg Fraud Prevention trae aún más seguridad para el procesamiento de compras hechas con boletos, transferencias bancarias y las principales banderas de tarjetas de crédito.
 
@@ -36,9 +36,7 @@ Para configurar Mundipagg Fraud Prevention, siga los pasos abajo:
 13. En __Usa Antifraude__, informe si su tienda tiene la funcionalidad antifraude contratada con Mundipagg.
 14. Haga clic en __Guardar__.
 
-<div class="alert alert-info">
-Los pasos indicados en <strong>8</strong>, <strong>9</strong>, <strong>11</strong> y <strong>12</strong> se deben completar si usted desea ofrecer boletos bancarios como condición de pago en su tienda.
-</div>
+>ℹ️ Los pasos indicados en **8**, **9**, **11** y **12** se deben completar si usted desea ofrecer boletos bancarios como condición de pago en su tienda.
 
 ## Configurar la condición de pago
 Después de seguir los pasos indicados arriba, Mundipagg Fraud Prevention estará configurado en su tienda. Por lo tanto, cuando se registre una condición de pago, estará disponible en el campo __Procesar con la afiliación__ (siempre que el medio de pago sea compatible con Mundipagg Fraud Prevention). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
diff --git a/docs/tutorials/es/setting-up-mundipagg-gateway.md b/docs/tutorials/es/setting-up-mundipagg-gateway.md
index df302be45..8d95f3333 100644
--- a/docs/tutorials/es/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/es/setting-up-mundipagg-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-mundipagg
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Mundipagg es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que procesa pagos hechos con boletos, transferencias bancarias y las principales banderas de tarjetas de crédito.
 
@@ -35,9 +35,7 @@ Para configurar Mundipagg, siga estos pasos:
 12. En el campo __Captura de seguridad anticipada__, escoja en cuánto tiempo desea que la captura se realice (después de la aprobación de la transacción y del análisis del antifraude). También es posible desactivar esta función.
 13. Haga clic en __Guardar__.
 
-<div class="alert alert-info">
-Los pasos <strong>8</strong>, <strong>9</strong>, <strong>11</strong> y <strong>12</strong> se deben cumprir si desea ofrecer boletos bancarios como condición de pago en su tienda.
-</div>
+>ℹ️ Los pasos **8**, **9**, **11** y **12** se deben cumprir si desea ofrecer boletos bancarios como condición de pago en su tienda.
 
 ## Configurar la condición de pago
 Después de seguir los pasos indicados arriba, Mundipagg estará configurada en su tienda. Por lo tanto, cuando se registre una condición de pago, estará disponible en el campo __Procesar con la afiliación__ (siempre que el medio de pago sea compatible con Mundipagg). Para saber cómo definir condiciones de pago, acceda a [este artículo del Help](/es/tutorial/condiciones-de-pago).
diff --git a/docs/tutorials/es/setting-up-my-account.md b/docs/tutorials/es/setting-up-my-account.md
index 2e96fccf0..ef700a21f 100644
--- a/docs/tutorials/es/setting-up-my-account.md
+++ b/docs/tutorials/es/setting-up-my-account.md
@@ -31,6 +31,4 @@ Para realizar las personalizaciones en la página, es necesario:
 2. Autenticarse a través de las opciones __Recibir código de acceso por e-mail__ o __Entrar con e-mail y contraseña__
 3. Ingrese a la sección __Mi cuenta__, ubicada en la esquina superior izquierda de la pantalla al lado de __Mi carrito__
 
-<div class="alert alert-info">
-Para las tiendas creadas a partir del 15 de mayo de 2019, no se requiere ningún ajuste de personalización, ya que el nuevo My Account ya se ha instalado nativamente en la plataforma.
-</div>
+>ℹ️ Para las tiendas creadas a partir del 15 de mayo de 2019, no se requiere ningún ajuste de personalización, ya que el nuevo My Account ya se ha instalado nativamente en la plataforma.
diff --git a/docs/tutorials/es/setting-up-nethone-antifraud.md b/docs/tutorials/es/setting-up-nethone-antifraud.md
index 7b9c2abfd..253091785 100644
--- a/docs/tutorials/es/setting-up-nethone-antifraud.md
+++ b/docs/tutorials/es/setting-up-nethone-antifraud.md
@@ -17,9 +17,7 @@ subcategory:
 
 [Nethone](https://nethone.com/) es una solución antifraude que a través de la inteligencia artificial y el aprendizaje automático (o *machine learning*) identifica aspectos de comportamiento específicos del usuario y minimiza los riesgos y las posibilidades de fraude en las transacciones de su tienda.
 
-<div class="alert alert-warning">
-  La integración de Nethone en VTEX se realiza mediante <b>Application Key (App Key)</b> y <b>Application Token (App Token)</b>. Puede encontrar esta información en el paquete del <i>plugin</i> que Nethone le enviará después de firmar el contrato. Si tiene alguna duda, póngase en contacto con el equipo de soporte de Nethone.
-  </div>
+>⚠️ La integración de Nethone en VTEX se realiza mediante **Application Key (App Key)** y **Application Token (App Token)**. Puede encontrar esta información en el paquete del <i>plugin</i> que Nethone le enviará después de firmar el contrato. Si tiene alguna duda, póngase en contacto con el equipo de soporte de Nethone.
 
 Para configurar Nethone, necesitará:
 
@@ -72,9 +70,7 @@ El siguiente paso de configuración de Nethone se realiza a través de Javascrip
 
 ## Configurar Google Tag Manager
 
-<div class="alert alert-warning">
-Las configuraciones documentadas a continuación se realizan en un sistema externo a VTEX y pueden descontinuarse sin previo aviso.
-  </div>
+>⚠️ Las configuraciones documentadas a continuación se realizan en un sistema externo a VTEX y pueden descontinuarse sin previo aviso.
 
 Con el número de identificación de la cuenta instalado en el checkout, configure los ajustes a continuación para dar seguimiento a los intentos de compra que ocurran en su tienda. 
 
diff --git a/docs/tutorials/es/setting-up-nexxpago-gateway.md b/docs/tutorials/es/setting-up-nexxpago-gateway.md
index 03057d3e0..3f570c3c3 100644
--- a/docs/tutorials/es/setting-up-nexxpago-gateway.md
+++ b/docs/tutorials/es/setting-up-nexxpago-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-nexxpago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Nexxpago es una empresa con certificación [PCI](/es/faq/que-es-el-pci-ssc) que ofrece diversas soluciones de pago. La principal de ellas es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que permite el procesamiento de pagos por medio de boletos bancarios y tarjetas de crédito.
 
diff --git a/docs/tutorials/es/setting-up-nps-gateway.md b/docs/tutorials/es/setting-up-nps-gateway.md
index 0a2260380..36d58b20c 100644
--- a/docs/tutorials/es/setting-up-nps-gateway.md
+++ b/docs/tutorials/es/setting-up-nps-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-nps
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Ingenico ePayments (NPS) es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) con fuerte actuación en América Latina y que permite que su tienda acepte diversas condiciones de pago.
 
diff --git a/docs/tutorials/es/setting-up-offline-payment-conditions-using-mercadopago.md b/docs/tutorials/es/setting-up-offline-payment-conditions-using-mercadopago.md
index ca1cb6662..e8c67fe60 100644
--- a/docs/tutorials/es/setting-up-offline-payment-conditions-using-mercadopago.md
+++ b/docs/tutorials/es/setting-up-offline-payment-conditions-using-mercadopago.md
@@ -15,9 +15,7 @@ legacySlug: configurar-condiciones-de-pago-offline-mediante-mercadopago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Este artículo se ocupa de las configuraciones aplicables en las tiendas que actúan en los siguientes países de América Latina: <strong>Argentina</strong>, <strong>Chile</strong>, <strong>Colombia</strong>, <strong>México</strong>, <strong>Perú</strong>, <strong>Uruguay</strong> y <strong>Venezuela</strong>.
-</div>
+>⚠️ Este artículo se ocupa de las configuraciones aplicables en las tiendas que actúan en los siguientes países de América Latina: **Argentina**, **Chile**, **Colombia**, **México**, **Perú**, **Uruguay** y **Venezuela**.
 
 Usted puede utilizar el Mercado Pago para ofrecer condiciones de pago offline en su tienda. Para ello, primero usted debe registrar la afiliación de gateway [MercadoPagoV1](/es/tutorial/configurar-el-subadquirente-mercadopagov1).
 
diff --git a/docs/tutorials/es/setting-up-pagarmev2-gateway.md b/docs/tutorials/es/setting-up-pagarmev2-gateway.md
index 63f1bd72b..fd7c8dde7 100644
--- a/docs/tutorials/es/setting-up-pagarmev2-gateway.md
+++ b/docs/tutorials/es/setting-up-pagarmev2-gateway.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 En VTEX es posible procesar pagos con el proveedor PagarMe a través de integraciones V2 y V3.
 
-<div class="alert alert-warning">
-Si quieres configurar la versión V3 de Pagarme en tu tienda, accede a <a href="https://help.vtex.com/es/tutorial/configurar-pago-con-pagarmev3--5PMavdamrVijwIrHas9ndE">Configurar pago con PagarMeV3</a>.
-</div>
+>⚠️ Si quieres configurar la versión V3 de Pagarme en tu tienda, accede a [Configurar pago con PagarMeV3](https://help.vtex.com/es/tutorial/configurar-pago-con-pagarmev3--5PMavdamrVijwIrHas9ndE).
 
 Para configurar PagarMeV2, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/setting-up-pagbrasil-gateway.md b/docs/tutorials/es/setting-up-pagbrasil-gateway.md
index f78c448d5..fb7cb8774 100644
--- a/docs/tutorials/es/setting-up-pagbrasil-gateway.md
+++ b/docs/tutorials/es/setting-up-pagbrasil-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-pagbrasil
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 PagBrasil es un gateway de pagos especializada en medios de pago brasileños, principalmente tarjetas de crédito y débito, transferencias en línea y boletos bancarios.
 
diff --git a/docs/tutorials/es/setting-up-paghiper-gateway.md b/docs/tutorials/es/setting-up-paghiper-gateway.md
index d89296e8c..ff1e3ae4e 100644
--- a/docs/tutorials/es/setting-up-paghiper-gateway.md
+++ b/docs/tutorials/es/setting-up-paghiper-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-paghiper
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 PagHiper es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que se dedica al procesamiento de compras realizadas por boletos bancarios.
 
diff --git a/docs/tutorials/es/setting-up-payment-with-paypal.md b/docs/tutorials/es/setting-up-payment-with-paypal.md
index b67b18c44..11fb41f8b 100644
--- a/docs/tutorials/es/setting-up-payment-with-paypal.md
+++ b/docs/tutorials/es/setting-up-payment-with-paypal.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pago-con-paypal
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En el gateway de VTEX, usted puede configurar el subadquirente de PayPal para recibir sus pagos. En esta modalidad, su cliente elige el pago de PayPal y realiza su autenticación en el ambiente de PayPal.
 
diff --git a/docs/tutorials/es/setting-up-paymentez-gateway.md b/docs/tutorials/es/setting-up-paymentez-gateway.md
index b912d8c65..823013ace 100644
--- a/docs/tutorials/es/setting-up-paymentez-gateway.md
+++ b/docs/tutorials/es/setting-up-paymentez-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-paymentez
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Paymentez es un [gateway de pago](/es/tutorial/que-es-un-gateway-de-pagos) con [certificación PCI](/es/faq/que-es-el-pci-ssc) nivel 2 y tiene su actuación concentrada en América Latina.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-alignet.md b/docs/tutorials/es/setting-up-payments-with-alignet.md
index 3a14751d7..bffea7404 100644
--- a/docs/tutorials/es/setting-up-payments-with-alignet.md
+++ b/docs/tutorials/es/setting-up-payments-with-alignet.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagos-com-alignet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En la plataforma VTEX, es posible configurar el [subadquirente](/es/tutorial/que-es-un-subadquirente) Alignet para recibir pagos en su tienda. En esta modalidad, el cliente escoge el __medio de pago__ Alignet y se redirige a la autenticación en el ambiente del subadquirente.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-apple-pay.md b/docs/tutorials/es/setting-up-payments-with-apple-pay.md
index ac342fa81..0fe6f25c5 100644
--- a/docs/tutorials/es/setting-up-payments-with-apple-pay.md
+++ b/docs/tutorials/es/setting-up-payments-with-apple-pay.md
@@ -20,9 +20,7 @@ Sus clientes pueden comprar con Apple Pay, la [cartera digital](/es/faq/que-es-u
 - Tener cuenta en `developer.apple.com`.
 - Tener contrato con un gateway que procese pagos con Apple Pay.
 
-<div class="alert alert-warning">
-  Actualmente, Apple Pay solo funciona en los sistemas operativos MacOs e IOS, y en el navegador Safari. Para obtener más información, vaya a <a href="https://support.apple.com/es-es/HT208531">Dispositivos compatibles con Apple Pay</a>.
-</div>
+>⚠️ Actualmente, Apple Pay solo funciona en los sistemas operativos MacOs e IOS, y en el navegador Safari. Para obtener más información, vaya a [Dispositivos compatibles con Apple Pay](https://support.apple.com/es-es/HT208531).
 
 ## Configurar proveedor de pago
 
diff --git a/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md b/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md
index a4390ef37..b0ea0d54d 100644
--- a/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md
+++ b/docs/tutorials/es/setting-up-payments-with-cieloecommerce.md
@@ -47,9 +47,7 @@ Para configurar CieloEcommerce, siga los siguientes pasos:
 
 <blockquote><ui>14. En <b>AntifraudProvider</b>, seleccione el proveedor antifraude que desea utilizar con CieloEcommerce.</ui>
 
-<blockquote><div class="alert alert-warning">
-  Consulte con Cielo si las opciones antifraude en CieloEcommerce ya están disponibles para su uso. Si aún está en desarrollo, ambos campos descritos en el paso 15 deben dejarse en blanco. Para obtener más información sobre el uso de opciones antifraude en su tienda, visite <a href="https://help.vtex.com/es/tutorial/como-configurar-antifraude">Configurar el antifraude</a>.
-  </div></blockquote>
+<blockquote>>⚠️ Consulte con Cielo si las opciones antifraude en CieloEcommerce ya están disponibles para su uso. Si aún está en desarrollo, ambos campos descritos en el paso 15 deben dejarse en blanco. Para obtener más información sobre el uso de opciones antifraude en su tienda, visite [Configurar el antifraude](https://help.vtex.com/es/tutorial/como-configurar-antifraude).</blockquote>
 <br>
 
 <blockquote><ui>15. En <b>Antifraud</b> y <b>AntifraudSequenceCriteria</b>, seleccione las opciones según información de CieloEcommerce antifraude. Consulta con CieloEcommerce si el antifraude ya está disponible para su uso, si aún está en desarrollo debes dejar ambos campos en blanco.</ui>
diff --git a/docs/tutorials/es/setting-up-payments-with-credimarcas.md b/docs/tutorials/es/setting-up-payments-with-credimarcas.md
index 815115af5..844226003 100644
--- a/docs/tutorials/es/setting-up-payments-with-credimarcas.md
+++ b/docs/tutorials/es/setting-up-payments-with-credimarcas.md
@@ -39,9 +39,7 @@ Para configurar la afiliación Credimarcas, siga los pasos a continuación:
 
 ## Configurar Pagaré
 
-<div class="alert alert-warning">
-  <p>Si aún no has configurado el pagaré como método de pago en otros conectores de tu tienda, accede a <a href="https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ">Configurar pagos con Pagaré</a>.</p>
-</div>
+>⚠️ Si aún no has configurado el pagaré como método de pago en otros conectores de tu tienda, accede a [Configurar pagos con Pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ).
 
 Para utilizar Credimarcas con pagarés, sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/setting-up-payments-with-itau-rede.md b/docs/tutorials/es/setting-up-payments-with-itau-rede.md
index 2b946b3e2..e87703303 100644
--- a/docs/tutorials/es/setting-up-payments-with-itau-rede.md
+++ b/docs/tutorials/es/setting-up-payments-with-itau-rede.md
@@ -25,9 +25,7 @@ Para utilizar Itaú Rede, debes:
 
 ## Obtener credenciales en el entorno de Userede
 
-<div class="alert alert-warning">
-Las configuraciones realizadas en un entorno externo a VTEX podrán ser discontinuadas o modificadas sin previo aviso. Consulta tu cuenta de Itaú Rede para obtener información actualizada.
-</div>
+>⚠️ Las configuraciones realizadas en un entorno externo a VTEX podrán ser discontinuadas o modificadas sin previo aviso. Consulta tu cuenta de Itaú Rede para obtener información actualizada.
 
 Para obtener las credenciales __Clave de aplicación__ y __Token de aplicación__ necesarias para configurar Itaú Rede en VTEX, siga los pasos a continuación:
 
@@ -59,9 +57,7 @@ Para obtener las credenciales __Clave de aplicación__ y __Token de aplicación_
 
 <blockquote><ui>8. Después de crear la nueva clave, haga clic en <b>copiar</b> y conserve la información en un lugar seguro. Esta clave debe ser utilizada en el campo <b>Token de aplicación</b> de la sección <a href="#configurar-itau-rede-en-vtex">Configurar Itaú Rede en VTEX</a>.</ui>
 
-<blockquote><ui><div class="alert alert-warning">
-Una vez que se crea una "chave de integração" en el entorno de red, no se puede volver a acceder a ella desde otras ubicaciones. Registre la información de la clave en una ubicación protegida y, si se pierde, repita el proceso para generar una nueva clave.
-  </div></ui></blockquote>
+<blockquote><ui>>⚠️ Una vez que se crea una "chave de integração" en el entorno de red, no se puede volver a acceder a ella desde otras ubicaciones. Registre la información de la clave en una ubicación protegida y, si se pierde, repita el proceso para generar una nueva clave.</ui></blockquote>
 
 ## Configurar Itaú Rede en VTEX
 
diff --git a/docs/tutorials/es/setting-up-payments-with-iugu.md b/docs/tutorials/es/setting-up-payments-with-iugu.md
index e468d3cfc..5c3f6bec0 100644
--- a/docs/tutorials/es/setting-up-payments-with-iugu.md
+++ b/docs/tutorials/es/setting-up-payments-with-iugu.md
@@ -44,9 +44,7 @@ Para procesar métodos de pago con tarjeta de crédito, pix y boleto bancario co
 
 Después de seguir los pasos indicados, el proveedor iugu puede tardar hasta 10 minutos en aparecer en el checkout de tu tienda como una opción de pago.
 
-<div class="alert alert-warning">
-  Antes de realizar transacciones con tarjeta de crédito, pix o boleto bancario con iugu en tu tienda, verifica si estos métodos de pago ya están habilitados en <a href="https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento">tu área de clientes en el portal iugu</a>.
-  </div>
+>⚠️ Antes de realizar transacciones con tarjeta de crédito, pix o boleto bancario con iugu en tu tienda, verifica si estos métodos de pago ya están habilitados en [tu área de clientes en el portal iugu](https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento).
 
 ## Configurar el split de pago en marketplace con iugu
 
@@ -64,15 +62,11 @@ Para habilitar el split de cobros con iugu en su tienda, siga los pasos a contin
 4. En __Control de pago__, seleccione la opción __Activar split de cobros y enviar destinatarios de pago__ e indique el __Responsable de cargos de procesamiento de pagos__ y el __Responsable de contracargos__ (marketplace, sellers o marketplace y sellers).
 5. Haga clic en `Guardar`.
 
-<div class="alert alert-warning">
-  La opción de split de cobros no está disponible para su uso en un entorno de prueba.
-  </div>
+>⚠️ La opción de split de cobros no está disponible para su uso en un entorno de prueba.
 
 Luego de seguir los pasos indicados, la funcionalidad de split de cobros con el proveedor iugu puede tardar hasta 10 minutos en activarse en tu tienda.
 
-<div class="alert alert-warning">
-  Para definir comisiones específicas para cada seller de su tienda, acceda a  <b>Marketplace > Sellers> Gestión</b> en el Admin de VTEX, seleccione el vendedor deseado e ingrese los valores de las comisiones en <b>Comisiones</b>.
-  </div>
+>⚠️ Para definir comisiones específicas para cada seller de su tienda, acceda a  **Marketplace > Sellers> Gestión** en el Admin de VTEX, seleccione el vendedor deseado e ingrese los valores de las comisiones en **Comisiones**.
 
 ## Configurar la recurrencia con iugu
 
diff --git a/docs/tutorials/es/setting-up-payments-with-koin.md b/docs/tutorials/es/setting-up-payments-with-koin.md
index f8ad36790..203ccdee1 100644
--- a/docs/tutorials/es/setting-up-payments-with-koin.md
+++ b/docs/tutorials/es/setting-up-payments-with-koin.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagos-con-koin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Usted puede configurar Koin para recibir pagos en su tienda. En esta modalidad, su cliente escoge el __medio de pago__ Koin Pospago para efectuar la compra.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-mercado-pago.md b/docs/tutorials/es/setting-up-payments-with-mercado-pago.md
index d88a919b0..ce1780aec 100644
--- a/docs/tutorials/es/setting-up-payments-with-mercado-pago.md
+++ b/docs/tutorials/es/setting-up-payments-with-mercado-pago.md
@@ -39,9 +39,7 @@ A continuación se muestran las configuraciones para el conector __Mercado Pago_
 12. En el campo __Tipo de estorno__ ("Tipo de retorno"), elija entre el proceso automático o la solicitud manual (en este caso, MercadoPago enviará un e-mail avisando del retorno pendiente).
 13. Haga clic en __Guardar__.
 
-<div class="alert alert-warning">
-El paso indicado en el item <strong>11</strong> es realizado en ambiente externo a VTEX. Por lo tanto, el proceso indicado puede ser actualizado sin previo aviso.
-</div>
+>⚠️ El paso indicado en el item **11** es realizado en ambiente externo a VTEX. Por lo tanto, el proceso indicado puede ser actualizado sin previo aviso.
 
 ## Configurar la condición de pago MercadoPago
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración > Planes de pago**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
diff --git a/docs/tutorials/es/setting-up-payments-with-notes-payable.md b/docs/tutorials/es/setting-up-payments-with-notes-payable.md
index 007027b52..a0dbd03d1 100644
--- a/docs/tutorials/es/setting-up-payments-with-notes-payable.md
+++ b/docs/tutorials/es/setting-up-payments-with-notes-payable.md
@@ -25,9 +25,7 @@ En VTEX, su tienda puede recibir pagos a través de pagarés. Para habilitar est
 
 Para configurar una afiliación de gateway, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
 
-<div class="alert alert-warning">
-Verifique que la afiliación de gateway deseada admita el procesamiento de pagos de pagarés.
-</div>
+>⚠️ Verifique que la afiliación de gateway deseada admita el procesamiento de pagos de pagarés.
 
 ## Configurar Pagaré
 
diff --git a/docs/tutorials/es/setting-up-payments-with-nuvei.md b/docs/tutorials/es/setting-up-payments-with-nuvei.md
index 61274fb23..1bb9643af 100644
--- a/docs/tutorials/es/setting-up-payments-with-nuvei.md
+++ b/docs/tutorials/es/setting-up-payments-with-nuvei.md
@@ -39,19 +39,15 @@ Para utilizar Nuvei, siga los pasos a continuación:
 <blockquote><ui>7. Para rellenar los campos <b>Merchant Id</b>, <b>Merchant Site Id</b> y <b>Client Secret</b> (Secret Key), 
 acceder a la información disponible en <b>Settings > My Integration Settings</b> dentro del panel de control de su cuenta en el entorno Nuvei.</ui>
 
-<blockquote><ui><div class="alert alert-warning">
- Nuvei tiene credenciales (Merchant Id, Merchant Site Id e Client Secret) específicas para cada tipo de entorno. Acceder a entornos de prueba <a href="sandbox.nuvei.com">(Integration)</a> y <a href="cpanel.nuvei.com">Live</a> 
-identificar las credenciales relativas a cada uno de ellos.
-  </div></blockquote>
+<blockquote><ui>>⚠️ Nuvei tiene credenciales (Merchant Id, Merchant Site Id e Client Secret) específicas para cada tipo de entorno. Acceder a entornos de prueba [(Integration)](sandbox.nuvei.com) y [Live](cpanel.nuvei.com) 
+> identificar las credenciales relativas a cada uno de ellos.</blockquote>
 <br>  
 <blockquote><ui>8. En <b>Environment</b>, seleccione si desea configurar el proveedor Nuvei en el entorno <b>Integration</b> o <b>Live</b>.</ui>
 
 <blockquote><ui>9. En <b>Test 3ds challenge Integration only</b>, si ha seleccionado el entorno de prueba (<b>Integration</b>) es posible realizar pruebas de seguridad 3DS a través de las opciones <b>Force 3ds Challenge</b>, <b>Force 3ds Frictionless</b> o <b>User cardHolder name</b>. 
 Para más información sobre las pruebas accede a la documentación <a href="https://docs.nuvei.com/documentation/integration/testing/testing-cards/?highlight=test%20cards#3d-secure-v2-test-scenarios">Nuvei</a>.</ui>
 
- <blockquote><ui><div class="alert alert-warning">
-   Siempre que el <b>Environment</b> del proveedor esté configurado como <b>Live</b>, la opción seleccionada para el campo <b>Test 3ds challenge Integration only</b> debe ser <b>User cardHolder name</b>.
-  </div></blockquote>
+ <blockquote><ui>>⚠️ Siempre que el **Environment** del proveedor esté configurado como **Live**, la opción seleccionada para el campo **Test 3ds challenge Integration only** debe ser **User cardHolder name**.</blockquote>
 <br>  
 <blockquote><ui>10. Haga clic en <b>Guardar</b>.</ui>
 
diff --git a/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md b/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md
index 321c1bbf5..ce8ef3ac3 100644
--- a/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md
+++ b/docs/tutorials/es/setting-up-payments-with-pagoefectivo.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagos-con-pagoefectivo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Usted puede configurar PagoEfectivo para recibir pagos en su tienda. En esta modalidad, su cliente escoge el __medio de pago__ PagoEfectivo para efectuar la compra.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-pagosweb.md b/docs/tutorials/es/setting-up-payments-with-pagosweb.md
index 3ac9f4a22..cbada6dae 100644
--- a/docs/tutorials/es/setting-up-payments-with-pagosweb.md
+++ b/docs/tutorials/es/setting-up-payments-with-pagosweb.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagos-con-pagosweb
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Usted puede configurar PagosWEB para recibir pagos en su tienda. En esta modalidad, su cliente escoge el __meio de pago__ PagosWEB para efectuar la compra.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-payclub.md b/docs/tutorials/es/setting-up-payments-with-payclub.md
index cdc536c4a..1c14a4b9b 100644
--- a/docs/tutorials/es/setting-up-payments-with-payclub.md
+++ b/docs/tutorials/es/setting-up-payments-with-payclub.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagos-con-payclub
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Usted puede configurar el [subadquirente](/es/tutorial/que-es-un-subadquirente) PayClub para recibir pagos en su tienda. En esta modalidad, su cliente elige el __medio de pago__ PayClub y realiza la autenticación en el ambiente externo de la solución de pagos.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-promissory.md b/docs/tutorials/es/setting-up-payments-with-promissory.md
index 188eb599f..752c0d522 100644
--- a/docs/tutorials/es/setting-up-payments-with-promissory.md
+++ b/docs/tutorials/es/setting-up-payments-with-promissory.md
@@ -25,9 +25,7 @@ En VTEX, su tienda puede recibir pagos a través de pagarés. Para habilitar est
 
 Para configurar una afiliación de gateway, acceda a [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
-<div class="alert alert-warning">
-Verifique que la afiliación de gateway deseada admita el procesamiento de pagos de pagarés.
-</div>
+>⚠️ Verifique que la afiliación de gateway deseada admita el procesamiento de pagos de pagarés.
 
 ## Configurar Pagaré
 
diff --git a/docs/tutorials/es/setting-up-payments-with-pse.md b/docs/tutorials/es/setting-up-payments-with-pse.md
index c36fc42e6..27bb0f030 100644
--- a/docs/tutorials/es/setting-up-payments-with-pse.md
+++ b/docs/tutorials/es/setting-up-payments-with-pse.md
@@ -21,8 +21,7 @@ Para habilitar PSE en su tienda, se requieren las siguientes acciones:
 - [Instalar y configurar la aplicación Banks for PSE](#instalacion-de-la-aplicación-banks-for-pse).
 - [Configuración la condición de pago PSE](#configuracion-la-condicion-de-pago-pse).
 
-<div class="alert alert-warning">
-Para configurar la aplicación PSE en su tienda, debe tener permiso para acceder al módulo de Pagos. Si aún no dispone de este acceso, solicítelo a través del <a href="https://help.vtex.com/support">VTEX Support</a>.</div>
+>⚠️ Para configurar la aplicación PSE en su tienda, debe tener permiso para acceder al módulo de Pagos. Si aún no dispone de este acceso, solicítelo a través del [VTEX Support](https://help.vtex.com/support).
 
 ## Instalación de la aplicación Banks for PSE
 
diff --git a/docs/tutorials/es/setting-up-payments-with-stelo.md b/docs/tutorials/es/setting-up-payments-with-stelo.md
index 31f89d0d9..ddbcd40a6 100644
--- a/docs/tutorials/es/setting-up-payments-with-stelo.md
+++ b/docs/tutorials/es/setting-up-payments-with-stelo.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagos-con-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Además de un [subadquirente](/es/tutorial/configurar-subadquirente-stelo) para procesar transacciones realizadas con diversas condiciones de pago, Stelo también ofrece un servicio de [cartera digital](/es/faq/que-es-una-cartera-digital). Su cliente elige pagar con ella y se redirige a la autenticación en el ambiente de Stelo.
 
diff --git a/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md b/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md
index 352caadf4..936691367 100644
--- a/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md
+++ b/docs/tutorials/es/setting-up-payments-with-store-card-cobranded.md
@@ -29,9 +29,7 @@ El primer paso de configuración será la creación del pago personalizado  __ta
 6. En __Red de la tarjeta__, escoja la franquicia a la cual la tarjeta de su tienda está vinculada. Actualmente, las franquicias posibles son: American Express, Cabal, Diners, Elo, Mastercard y Visa.
 7. En __Rangos de Bin (opcional)__, puedes ingresar un rango de BIN (ingresando el primer y último código de la secuencia, separados por un guión) o varios (separando cada rango por una coma y sin espacios).
 
-<div class="alert alert-warning">
-  Cuando el cliente ingresa un número de contenedor fuera del rango especificado en este campo, se mostrará el siguiente mensaje "Verifique los dígitos impresos en su tarjeta. No pudimos confirmar si el número de la tarjeta es correcto". Si no hay ningún error en el número ingresado, podrán hacer clic en "SÍ, EL NÚMERO DE LA TARJETA ES CORRECTO" para continuar completando el pedido.
-</div>
+>⚠️ Cuando el cliente ingresa un número de contenedor fuera del rango especificado en este campo, se mostrará el siguiente mensaje "Verifique los dígitos impresos en su tarjeta. No pudimos confirmar si el número de la tarjeta es correcto". Si no hay ningún error en el número ingresado, podrán hacer clic en "SÍ, EL NÚMERO DE LA TARJETA ES CORRECTO" para continuar completando el pedido.
 
 <blockquote><ui>8. En el campo <b>Código de pago del adquiriente (opcional)</b>, indique el código a ser enviado y procesado por el adquiriente contratado por usted.</ui>
 
@@ -42,9 +40,7 @@ El primer paso de configuración será la creación del pago personalizado  __ta
 ## Configurar condición de pago
 Después de configurar la tarjeta, deberá configurar la condición de pago.
 
-<div class="alert alert-warning">
-  Si el conector para ser elegido (en el <b>Paso 8.</b>)no está registrado en su tienda, se mostrará el mensage "(Configurar)" después del nombre del conector. En esta situación, elija otro conector disponible o regístrelo. Para obtener más información, acceda <a href="https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Registrar afiliaciones de gateway</a>.
-</div>
+>⚠️ Si el conector para ser elegido (en el **Paso 8.**)no está registrado en su tienda, se mostrará el mensage "(Configurar)" después del nombre del conector. En esta situación, elija otro conector disponible o regístrelo. Para obtener más información, acceda [Registrar afiliaciones de gateway](https://help.vtex.com/es/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 1. En el Admin VTEX, accede a **Configuración de la tienda** > **Pago** > **Configuración**, o escribe **Configuración** en la barra de búsqueda en la parte superior de la página.
 2. En la pestaña __Condiciones de pago__, haga clic en el botón __“+”__.
diff --git a/docs/tutorials/es/setting-up-paypal-plus.md b/docs/tutorials/es/setting-up-paypal-plus.md
index 5182c5f9c..1450b2892 100644
--- a/docs/tutorials/es/setting-up-paypal-plus.md
+++ b/docs/tutorials/es/setting-up-paypal-plus.md
@@ -15,7 +15,7 @@ legacySlug: configurar-paypal-plus-paypal-transparente
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En el gateway de VTEX, usted puede configurar el subadquirente PayPal Plus, el checkout transparente de PayPal. En esta modalidad, basta con que el cliente introduzca la información de tarjeta de crédito y finalice la compra normalmente. El pago se realiza directamente en su sitio, sin redirigir a sus clientes.
 
diff --git a/docs/tutorials/es/setting-up-payu-gateway.md b/docs/tutorials/es/setting-up-payu-gateway.md
index 79ee1f48c..0005d8c5e 100644
--- a/docs/tutorials/es/setting-up-payu-gateway.md
+++ b/docs/tutorials/es/setting-up-payu-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-payu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 PayU es un [gateway](/es/tutorial/que-es-un-gateway-de-pagos) que ofrece una serie de soluciones para facilitar (y dejar más seguras) las transacciones realizadas en su tienda. Con certificación [PCI](/es/faq/que-es-el-pci-ssc), esta solución es exclusiva para Argentina, Brasil, Chile, Colombia, México, Panamá y Perú.
 
diff --git a/docs/tutorials/es/setting-up-payu-global-gateway.md b/docs/tutorials/es/setting-up-payu-global-gateway.md
index 4f7e08ef9..e43267ebe 100644
--- a/docs/tutorials/es/setting-up-payu-global-gateway.md
+++ b/docs/tutorials/es/setting-up-payu-global-gateway.md
@@ -17,8 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 PayU Global es un [gateway de pagos](/es/tutorial/que-es-un-gateway-de-pagos) que ofrece una serie de soluciones para facilitar (y dejar más seguras) las transacciones realizadas en su tienda. Con la [certificación PCI](/es/faq/que-es-el-pci-ssc), esta solución es exclusiva para las tiendas de Rumania.
 
-<div class="alert alert-info"> Atención: actualmente, VTEX solo es compatible con las versiones 1.0.0 y 1.0.1 de PaymentsOS. 
-</div>
+>ℹ️ Atención: actualmente, VTEX solo es compatible con las versiones 1.0.0 y 1.0.1 de PaymentsOS.
 
 Para configurar PayU Global, siga los pasos abajo:
 
diff --git a/docs/tutorials/es/setting-up-payzen-gateway.md b/docs/tutorials/es/setting-up-payzen-gateway.md
index 9d3b917d4..8ccee51c8 100644
--- a/docs/tutorials/es/setting-up-payzen-gateway.md
+++ b/docs/tutorials/es/setting-up-payzen-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-el-gateway-payzen
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En VTEX, usted puede configurar el [gateway PayZen](/es/tutorial/que-es-un-gateway-de-pagos) en su tienda. De fácil integración, sigue los estándares de seguridad definidos por [Pagos](/es/faq/que-es-el-pci-ssc).
 
diff --git a/docs/tutorials/es/setting-up-place2pay-gateway.md b/docs/tutorials/es/setting-up-place2pay-gateway.md
index 64bcbfb61..cbf7181e1 100644
--- a/docs/tutorials/es/setting-up-place2pay-gateway.md
+++ b/docs/tutorials/es/setting-up-place2pay-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-place2pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Place2Pay es la versión con redirect del gateway PlaceToPay, que ofrece soluciones para grandes y pequeñas tiendas.
 
diff --git a/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md b/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md
index ac9560868..76e588dea 100644
--- a/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md
+++ b/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md
@@ -23,13 +23,9 @@ Para regionalizar los precios y la disponibilidad de SKU, debe:
 2. [Sellers White Label](/es/faq/que-son-cuenta-franquicia-y-seller-white-label) realicen entregas de pedidos hechos en su tienda para determinados rangos de Códigos Postales.
 3. La sesión del usuario navegando por la tienda contiene información sobre su código postal y país de origen.
 
-<div class="alert alert-info">
-Para utilizar esta función, la tienda debe tener el sistema (<a href="https://help.vtex.com/pt/tutorial/vtex-session-visao-geral-do-sistema-de-sessoes--6C4Edou6bYqqEAOCAg2MQQ#">VTEX Session</a>). VTEX Session es nativo de todas las tiendas y usted puede confirmar su instalación por la presencia de las cookies <code>vtex_session<code> y <code>vtex_segment<code> al navegar por la tienda.
-</div>
+>ℹ️ Para utilizar esta función, la tienda debe tener el sistema ([VTEX Session](https://help.vtex.com/pt/tutorial/vtex-session-visao-geral-do-sistema-de-sessoes--6C4Edou6bYqqEAOCAg2MQQ#)). VTEX Session es nativo de todas las tiendas y usted puede confirmar su instalación por la presencia de las cookies <code>vtex_session<code> y <code>vtex_segment<code> al navegar por la tienda.
 
-<div class="alert alert-warning">
-Para <a href="https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#">Multilevel Omnichannel Inventory</a>, un marketplace (nivel 1) no puede configurar la exhibición de los precios y la disponibilidad de los productos para los sellers white label (nivel 3) con la funcionalidad de regionalización.
-</div>
+>⚠️ Para [Multilevel Omnichannel Inventory](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#), un marketplace (nivel 1) no puede configurar la exhibición de los precios y la disponibilidad de los productos para los sellers white label (nivel 3) con la funcionalidad de regionalización.
 
 <div class = "alert alert-info">
 La funcionalidad <b>Region</b> funciona tanto para las tiendas Portal CMS Legado como para las tiendas desarrolladas con <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC">VTEX IO</a>, pero la funcionalidad <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a> solo es válida para las tiendas VTEX IO. Como resultado, las tiendas con Portal CMS Legado tienen una limitación en la indexación de datos regionalizados y no es posible ordenar correctamente los sellers que atienden la ventana de un RegionId en función de la disponibilidad de ítems.
@@ -48,6 +44,4 @@ Para configurar la entrega, siga los pasos a continuación:
 6. Registre un [inventario](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137#).
 7. [Agregue stock a los SKUs](https://help.vtex.com/es/tutorial/managing-stock-items) que se entregarán por la ruta configurada.
 
-<div class="alert alert-info">
-Para que un SKU aparezca como disponible para la venta, es necesario que tenga stock y precio asociados a este. 
-</div>
+>ℹ️ Para que un SKU aparezca como disponible para la venta, es necesario que tenga stock y precio asociados a este.
diff --git a/docs/tutorials/es/setting-up-price-tables-for-specific-users.md b/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
index dd2316c21..1570f8073 100644
--- a/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/es/setting-up-price-tables-for-specific-users.md
@@ -21,9 +21,7 @@ A diferencia de las políticas comerciales, que también se pueden utilizar para
 
 Por ejemplo, digamos que usted desea que los clientes de Buenos Aires vean un precio diferente del que ven los clientes de Córdoba. En este caso, puede crear dos tablas de precio diferentes, y asociar la primera a los clientes de Buenos Aires, y la segunda a los de Córdoba.
 
-<div class="alert alert-info">
-<p>Se pueden establecer precios fijos o reglas de precios para modificar el precio de un SKU en una tabla de precio.</p>
-</div>
+>ℹ️ Se pueden establecer precios fijos o reglas de precios para modificar el precio de un SKU en una tabla de precio.
 
 Esto permite al comerciante más libertad para tratar con informaciones contextuales de sus clientes.
 
@@ -63,9 +61,7 @@ Otra manera de usar tablas de precio es declarándolas directamente en el formul
 10. En la línea de la entidad cambiada, haga clic en el icono del disco para publicar.
 11. Entonces, en la misma línea de la entidad editada, haga clic en el icono de flechas para reindexar la entidad.
 
-<div class="alert alert-info">
-<p>Cada cliente puede tener un máximo de 5 tablas de precios vinculadas a él. Cuando el cliente tiene más de una tabla de precios vinculada, el sistema seguirá el orden de las tablas de precios registradas para determinar el precio de cada SKU. Si la SKU no tiene un precio configurado en la primera tabla de precios, el sistema buscará a partir de la segunda. Si no hay ningún precio configurado en ninguna tabla vinculada al cliente, el precio aplicado será el precio base.</p>
-</div>
+>ℹ️ Cada cliente puede tener un máximo de 5 tablas de precios vinculadas a él. Cuando el cliente tiene más de una tabla de precios vinculada, el sistema seguirá el orden de las tablas de precios registradas para determinar el precio de cada SKU. Si la SKU no tiene un precio configurado en la primera tabla de precios, el sistema buscará a partir de la segunda. Si no hay ningún precio configurado en ninguna tabla vinculada al cliente, el precio aplicado será el precio base.
 
 Ahora su entidad de __Clientes__ tiene un atributo `priceTables`, que puede ser completado directamente en la UI del Master Data o por API.
 
@@ -81,9 +77,7 @@ Para actualizar el precio fijo en una tabla específica, haga clic en la columna
 
 Para ingresar y actualizar los precios de una tabla específica por API, vea esta [documentación de API](https://developers.vtex.com/reference/prices-and-fixed-prices#createeditfixedpricesonapricetableortradepolicy).
 
-<div class="alert alert-info">
-<p>La tabla de precios tiene prioridad sobre el precio de la Política Comercial. Eso significa que, si determinada tabla de precios se aplica al contexto de un usuario, el precio definido en este será el usado, aunque ese cliente esté también en el contexto de una política comercial que defina un precio diferente.</p>
-</div>
+>ℹ️ La tabla de precios tiene prioridad sobre el precio de la Política Comercial. Eso significa que, si determinada tabla de precios se aplica al contexto de un usuario, el precio definido en este será el usado, aunque ese cliente esté también en el contexto de una política comercial que defina un precio diferente.
 
 ## Mostrando precios diferentes para usuarios diferentes 
 
@@ -97,6 +91,4 @@ Por ejemplo, estos dos clientes están vinculados a tablas de precios diferentes
 Cuando el cliente Daniel, que está vinculado a la tabla Silver, inicie sesión en la tienda, verá los precios establecidos en dicha tabla. La mochila del ejemplo anterior aparecerá a USD 50.
 En cambio, el cliente Breno, que está vinculado a la tabla Gold, verá los precios definidos en esta otra tabla. Para él, la mochila costará USD 60,50.
 
-<div class="alert alert-warning">
-Recuerde que los precios varían según la sesión. Es decir, el cliente <strong>necesita</strong> ser autenticado para que haya alteración (ya sea a través de token, contraseña, Google o Facebook). Sin la autenticación del usuario, el precio siempre será el estándar. Y atención: el hecho de ingresar el e-mail en el proceso de checkout no es suficiente, ya que en ese proceso él realiza su identificación, pero no la autenticación.
-</div>
+>⚠️ Recuerde que los precios varían según la sesión. Es decir, el cliente **necesita** ser autenticado para que haya alteración (ya sea a través de token, contraseña, Google o Facebook). Sin la autenticación del usuario, el precio siempre será el estándar. Y atención: el hecho de ingresar el e-mail en el proceso de checkout no es suficiente, ya que en ese proceso él realiza su identificación, pero no la autenticación.
diff --git a/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md b/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md
index 73bb70ee4..2f6364c08 100644
--- a/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md
+++ b/docs/tutorials/es/setting-up-rede-acquirer-with-erederest.md
@@ -15,13 +15,11 @@ legacySlug: configurar-adquirente-rede-con-erederest
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En VTEX, usted puede hacer la integración con el [adquirente](/es/tutorial/que-es-un-adquirente) Rede usando el conector ERedeREST. Este conector trae una serie de mejoras, entre ellas el soporte a medios de pago con pre-autorización (__Visa__, __Mastercard__, __American Express__, __Diners__, __Hipercard__, __JCB__ y __Credz__).
 
-<div class="alert alert-warning">
-La bandera <strong>Elo</strong> todavía no es compatible con pre-autorización.
-</div>
+>⚠️ La bandera **Elo** todavía no es compatible con pre-autorización.
 
 Otra característica importante del conector ERedeREST es que también se puede configurarlo para aceptar pagos con [__Apple Pay__](/es/tutorial/configurar-pagos-con-apple-pay), la cartera digital de Apple.
 
diff --git a/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md b/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md
index 924cc9d84..477f70cdd 100644
--- a/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md
+++ b/docs/tutorials/es/setting-up-seller-white-label-as-a-pickup-point.md
@@ -23,9 +23,7 @@ Como se explica en el artículo [Definiciones de Cuenta Franquicia y Seller Whit
 
 De esta manera, el punto de recogida configurado en la Cuenta Franquicia __servirá para atender las entregas de los pedidos realizados en la Cuenta Principal__. En este escenario, la Cuenta Franquicia actúa como __Seller White Label__ de la cuenta principal.
 
-<div class="alert alert-danger">
-Las configuraciones se deben realizar en la cuenta del seller White Label. Los ítems estarán disponibles para la recogida en el checkout del cliente final  solamente si el SKU está disponible en el stock de la cuenta principal y de la cuenta del seller White Label.
-</div>
+>❗ Las configuraciones se deben realizar en la cuenta del seller White Label. Los ítems estarán disponibles para la recogida en el checkout del cliente final  solamente si el SKU está disponible en el stock de la cuenta principal y de la cuenta del seller White Label.
 
 ## Configuración inicial
 
@@ -48,9 +46,7 @@ Para saber en detalle cómo llenar los campos de la plantilla, ingrese a nuestro
 
 Si la configuración del punto de recogida se ha efectuado correctamente en la Cuenta Franquicia, los SKUs con __stock disponible y precio__ podrán venderse en la Cuenta Principal, donde la Cuenta Franquicia actuará como un __Seller White Label__ y la Cuenta Principal funcionará como un __Marketplace__.
 
-<div class="alert alert-warning">
-Asegúrese de que el seller white label esté activo. Acceda a el Admin VTEX, en <b>Marketplace > Sellers > Gestión de sellers</b>, y en la línea del seller y la columna <i>Status</i>, haga clic en <code>Activo</code>.
-</div>
+>⚠️ Asegúrese de que el seller white label esté activo. Acceda a el Admin VTEX, en **Marketplace > Sellers > Gestión de sellers**, y en la línea del seller y la columna <i>Status</i>, haga clic en `Activo`.
 
 ### Seller White Label/Cuenta Franquicia
 
diff --git a/docs/tutorials/es/setting-up-shipment.md b/docs/tutorials/es/setting-up-shipment.md
index 9b43e4118..4261fd586 100644
--- a/docs/tutorials/es/setting-up-shipment.md
+++ b/docs/tutorials/es/setting-up-shipment.md
@@ -17,9 +17,7 @@ subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 
 Esta es una configuración ampliamente utilizada cuando un flujo muy grande de pedidos acaba generando una demanda logística considerable, pues posibilita que un paquete espere el tiempo de preparación de otro para ser enviado en grupo, por una misma transportadora, a un destinatario final.
 
-<div class="alert alert-warning">
-Los grupos de envío son creados por la suma del tiempo de costo del inventario hasta el muelle y el tiempo de costo del muelle.
-</div>
+>⚠️ Los grupos de envío son creados por la suma del tiempo de costo del inventario hasta el muelle y el tiempo de costo del muelle.
 
 En la siguiente imagen vemos una configuración de envío de __6 días__. Cada caja representa el costo en días de un paquete, considerando sólo el __costo de inventario y el costo del muelle__.
 
diff --git a/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md b/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md
index 39db9f330..c7acb2522 100644
--- a/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md
+++ b/docs/tutorials/es/setting-up-sitef-gateway-with-pre-auth.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-sitef-con-pre-auth
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Para permitir que las compras realizadas con tarjeta de crédito tengan el valor reservado, usted puede configurar el gateway __Sitef con pre-auth__ (pre-autorización) en su tienda.
 
diff --git a/docs/tutorials/es/setting-up-sitef-gateway.md b/docs/tutorials/es/setting-up-sitef-gateway.md
index 8a712057a..a749a5af6 100644
--- a/docs/tutorials/es/setting-up-sitef-gateway.md
+++ b/docs/tutorials/es/setting-up-sitef-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-sitef
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 En VTEX, usted puede configurar el gateway Sitef. Para configurarlo, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/setting-up-sub-acquirer-stelo.md b/docs/tutorials/es/setting-up-sub-acquirer-stelo.md
index 56ee8cc38..449f6cf7e 100644
--- a/docs/tutorials/es/setting-up-sub-acquirer-stelo.md
+++ b/docs/tutorials/es/setting-up-sub-acquirer-stelo.md
@@ -15,7 +15,7 @@ legacySlug: configurar-subadquirente-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 Stelo es un [subadquirente](/es/tutorial/que-es-un-subadquirente) que facilita la integración de medios de pago a su tienda.
 
diff --git a/docs/tutorials/es/setting-up-the-global-category.md b/docs/tutorials/es/setting-up-the-global-category.md
index cd4e1fd27..6d7d594fd 100644
--- a/docs/tutorials/es/setting-up-the-global-category.md
+++ b/docs/tutorials/es/setting-up-the-global-category.md
@@ -19,9 +19,7 @@ El árbol de la categoría global es la taxonomía creada por Google para el [Me
 
 Las mismas categorías globales están disponibles para los productos de todas las tiendas.
 
-<div class="alert alert-info">
-Para todas las categorías de su tienda es necesario elegir una categoría global.
-</div>
+>ℹ️ Para todas las categorías de su tienda es necesario elegir una categoría global.
 
 ### ¿Por qué usar?
 
@@ -59,9 +57,7 @@ Siempre debe elegir la categoría global que más se ajuste a los productos de l
 
 Lo ideal es que una categoría global se determine en la configuración de categoría. Esto permite que todos los productos de una categoría pertenezcan a la misma categoría global.
 
-<div class="alert alert-danger">
-La elección de una categoría global en el registro del producto solo se recomienda si tiene que configurarse de manera diferente a la categoría en la que se incorporó.
-</div>
+>❗ La elección de una categoría global en el registro del producto solo se recomienda si tiene que configurarse de manera diferente a la categoría en la que se incorporó.
 
 La configuración global de la categoría se realiza en el Admin y es obligatorio rellenarla. Para su configuración, realice los siguientes pasos:
 
@@ -74,6 +70,4 @@ La configuración global de la categoría se realiza en el Admin y es obligatori
 7. Escriba el nombre de la categoría que desea encontrar y haga clic en el ícono <i class="fas fa-search"></i>. Puede utilizar el campo de búsqueda para encontrar la categoría deseada. 
 8. Haga clic en la categoría deseada para seleccionarla y, a continuación, haga clic en el botón `Guardar`. 
 
-<div class="alert alert-info">
-La categoría global también se puede configurar a través de <a href="https://help.vtex.com/es/tutorial/configuring-xml--tutorials_242">XML</a>.
-</div>
+>ℹ️ La categoría global también se puede configurar a través de [XML](https://help.vtex.com/es/tutorial/configuring-xml--tutorials_242).
diff --git a/docs/tutorials/es/setting-up-the-logistics-for-instore.md b/docs/tutorials/es/setting-up-the-logistics-for-instore.md
index fc9f6bd7b..3747075e5 100644
--- a/docs/tutorials/es/setting-up-the-logistics-for-instore.md
+++ b/docs/tutorials/es/setting-up-the-logistics-for-instore.md
@@ -15,9 +15,7 @@ legacySlug: configurar-logistica-para-el-instore
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-<div class="alert alert-info">
-Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a <a href="https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envío</a>.
-</div>  
+>ℹ️ Atención: Esa documentación está en proceso de actualizarse para reflejar los cambios del término Paneles a [estratégia de envío](https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl).  
 
 Para que el inStore funcione correctamente, es necesario registrar una logística específica para él. inStore debe configurarse con un __punto de retirada__. El registro de la logística sigue dos etapas:
 
diff --git a/docs/tutorials/es/setting-up-the-moip-sub-acquirer.md b/docs/tutorials/es/setting-up-the-moip-sub-acquirer.md
index 7e8fe7e2d..bad5e2819 100644
--- a/docs/tutorials/es/setting-up-the-moip-sub-acquirer.md
+++ b/docs/tutorials/es/setting-up-the-moip-sub-acquirer.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Moip es un [subadquirente](/es/tutorial/que-es-un-subadquirente) que ofrece una integración única para conectar su tienda a todas las partes del flujo de pago, ofreciendo protección contra fraudes y una solución de [checkout transparente](/es/tutorial/que-es-el-checkout-transparente) (sin redireccionamientos).
 
-<div class="alert alert-warning">
-La información de este artículo son solamente referencias de configuración para los comerciantes que ya utilizan el subadquirente Moip. Para nuevas afiliaciones, recomendamos utilizar el subadquirente <a href="https://help.vtex.com/es/tutorial/configurar-o-subadquirente-moipv2--4BipUcTxQ7cq2BiYzUDmEH">MoipV2</a>.
-  </div>
+>⚠️ La información de este artículo son solamente referencias de configuración para los comerciantes que ya utilizan el subadquirente Moip. Para nuevas afiliaciones, recomendamos utilizar el subadquirente [MoipV2](https://help.vtex.com/es/tutorial/configurar-o-subadquirente-moipv2--4BipUcTxQ7cq2BiYzUDmEH).
 
 Para configurar Moip, siga los pasos a continuación:
 
@@ -40,9 +38,7 @@ Para configurar Moip, siga los pasos a continuación:
 6. Haga clic en <b>Salvar.</b>
   </ui><br><br>
 
-<div class="alert alert-warning">
-MOIP no procesa las transacciones cuando hay productos con un valor de $0,00 en el carrito. Por ejemplo: si se crea un <a href="https://help.vtex.com/es/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete">anexo</a> de empaque de regalo, el valor del ítem será de $0,00, lo que imposibilita el procesamiento del pago.
-  </div>
+>⚠️ MOIP no procesa las transacciones cuando hay productos con un valor de $0,00 en el carrito. Por ejemplo: si se crea un [anexo](https://help.vtex.com/es/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete) de empaque de regalo, el valor del ítem será de $0,00, lo que imposibilita el procesamiento del pago.
 
 ## Configurar la condición de pago
 
diff --git a/docs/tutorials/es/setting-up-the-notify-me-option.md b/docs/tutorials/es/setting-up-the-notify-me-option.md
index 45ba498de..01c1a0882 100644
--- a/docs/tutorials/es/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/es/setting-up-the-notify-me-option.md
@@ -15,9 +15,7 @@ legacySlug: configurar-el-aviseme
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-<div class="alert alert-warning">
-<p>Este articulo explica cómo configurar la opción <strong>Avísame</strong> en las tiendas que usan <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Legado</a>. En las tiendas que usan <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, la configuración se debe hacer siguiendo los pasos de la guía <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify">Availability Notify</a>.</p>
-</div>
+>⚠️ Este articulo explica cómo configurar la opción **Avísame** en las tiendas que usan [CMS Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). En las tiendas que usan [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), la configuración se debe hacer siguiendo los pasos de la guía [Availability Notify](https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify).
 
 Cuando no hay [stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139) de un producto, el administrador de la tienda puede optar por ofrecer al cliente la opción **Avísame**. Esta funcionalidad permite que los clientes interesados en un producto reciban una notificación por email cuando el ítem vuelva a estar disponible.
 
diff --git a/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
index e02454f26..1609f3277 100644
--- a/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/es/setting-up-the-sales-funnel-on-google-analytics.md
@@ -19,9 +19,7 @@ Las metas de **Google Analytics** sirven para ayudarle a evaluar si se cumplen l
 
 Con el embudo de ventas configurado, es posible acompañar y analizar los pasos del cliente hasta la finalización de un pedido. Para configurar el embudo de ventas vamos a tener en cuenta que el proceso de compra se inicia en la pantalla de su producto y pasa por el carrito de compras, checkout (datos personales, entrega, pago) y llega hasta la meta, que es la página de pedido confirmado.
 
-<div class="alert alert-info">
-Para facilitar, toda la configuración que se muestra en este artículo se puede <a href="https://support.google.com/analytics/answer/1032415?hl=es" target="_blank">importar directamente a Google Analytics</a> con <a href="https://analytics.google.com/analytics/web/template?uid=tTp2GkIJRiGodszJbq8RsA" target="_blank">esta plantilla</a>.
-</div>
+>ℹ️ Para facilitar, toda la configuración que se muestra en este artículo se puede [importar directamente a Google Analytics](https://support.google.com/analytics/answer/1032415?hl=es" target="_blank) con [esta plantilla](https://analytics.google.com/analytics/web/template?uid=tTp2GkIJRiGodszJbq8RsA" target="_blank).
 
 Para la configuración manual o la edición de una meta existente, el primer paso es acceder a Analytics y hacer clic en el botón __Administrador__ en la esquina inferior izquierda. A continuación, vaya a la opción __Metas__, de la columna "Vista".
 
@@ -62,30 +60,35 @@ Ahora sólo hay que guardar la meta y esperar el tiempo que el sistema tarda en
 
 Para ver su embudo, consulte los informes de Analytics y acceda al menú __Conversiones__ y a la opción __Metas__.
 
-<div class="alert alert-warning">
-<p>Si tienes una tienda en varios idiomas con idiomas como <a href="https://support.google.com/webmasters/answer/182192?hl=es#locale-specific-urls">subdirectorios con gTLD</a> debes reemplazar cada <a href="https://support.google.com/analytics/answer/1034376?hl=es&ref_topic=1034375">símbolo de intercalación</a> (<code>^</code>) con una <a href="https://support.google.com/analytics/answer/1034324?hl=es">regex</a> que coincide con los diferentes subdirectorios. Por ejemplo, si su sitio web está disponible en:</p>
-  <ul>
-    <li><strong>Italiano: </strong><code>example.com/it</code></li>
-    <li><strong>Español: </strong><code>example.com/es</code></li>
-    <li><strong>Francés: </strong><code>example.com/fr</code></li>
-  </ul>
-  <p>Tendrías que cambiar su destino:</p>
-  <ul>
-<li><strong>De: </strong><code>^/checkout/orderPlaced</code></li> 
-<li><strong>Para: </strong><code>^/(it|es|fr)/checkout/orderPlaced</code></li>
-  </ul>
-  <p>Esto también debe hacerse para cada paso del embudo.</p>
-</div>
-
-<div class="alert alert-warning">
-<p>La configuración de embudo de este artículo ha sido actualizada para acompañar la nueva versión de <a href="http://help.vtex.com/es/tutorial/que-es-el-carrito-compartido">carrito compartido del SmartCheckout</a>.</p>
-<p>Para efectos de comparación, abajo tenemos la configuración antigua:</p>
-<ol>
-<li>Producto: <code>/p($|\?)</code> (no obligatorio)</li>
-<li>Carrito: <code>^/checkout/(#/cart)?$</code></li>
-<li>Identificación: <code>^/checkout/#/email</code></li>
-<li>Fatos Personales: <code>^/checkout/#/profile</code></li>
-<li>Envío: <code>^/checkout/#/shipping</code></li>
-<li>Pago: <code>^/checkout/#/payment</code></li>
-</ol>
-</div>
+>⚠️ Si tienes una tienda en varios idiomas con idiomas como [subdirectorios con gTLD](https://support.google.com/webmasters/answer/182192?hl=es#locale-specific-urls) debes reemplazar cada [símbolo de intercalación](https://support.google.com/analytics/answer/1034376?hl=es&ref_topic=1034375) (`^`) con una [regex](https://support.google.com/analytics/answer/1034324?hl=es) que coincide con los diferentes subdirectorios. Por ejemplo, si su sitio web está disponible en:
+>
+> * **Italiano: **`example.com/it`
+>
+> * **Español: **`example.com/es`
+>
+> * **Francés: **`example.com/fr`
+>
+> Tendrías que cambiar su destino:
+>
+> ***De: **`^/checkout/orderPlaced` 
+>
+> ***Para: **`^/(it|es|fr)/checkout/orderPlaced`
+>
+> Esto también debe hacerse para cada paso del embudo.
+
+>⚠️ La configuración de embudo de este artículo ha sido actualizada para acompañar la nueva versión de [carrito compartido del SmartCheckout](http://help.vtex.com/es/tutorial/que-es-el-carrito-compartido).
+>
+> Para efectos de comparación, abajo tenemos la configuración antigua:
+>
+> Producto: `/p($|\?)` (no obligatorio)
+>
+> Carrito: `^/checkout/(#/cart)?$`
+>
+> Identificación: `^/checkout/#/email`
+>
+> Fatos Personales: `^/checkout/#/profile`
+>
+> Envío: `^/checkout/#/shipping`
+>
+> Pago: `^/checkout/#/payment`
+> 
diff --git a/docs/tutorials/es/setting-up-the-tnspay-gateway.md b/docs/tutorials/es/setting-up-the-tnspay-gateway.md
index 873bf5f76..c8ac8db4a 100644
--- a/docs/tutorials/es/setting-up-the-tnspay-gateway.md
+++ b/docs/tutorials/es/setting-up-the-tnspay-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-el-gateway-tnspay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 TNSPay es un [gateway de pago](/es/tutorial/que-es-un-gateway-de-pagos) con certificación PCI que proporciona una serie de features de seguridad para facilitar el procesamiento de [compras recurrentes](/es/faq/como-funciona-la-compra-recurrente).
 
diff --git a/docs/tutorials/es/setting-up-the-type-of-interest-rate.md b/docs/tutorials/es/setting-up-the-type-of-interest-rate.md
index b7b782ed2..9fa98b6b3 100644
--- a/docs/tutorials/es/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/es/setting-up-the-type-of-interest-rate.md
@@ -41,6 +41,4 @@ El response que devolvió la llamada "GET Rule by ID" anterior, será el request
 
 https://developers.vtex.com/reference/configuration-1#putrulebyid
 
-<div class="alert alert-danger">
-IMPORTANTE: Actualmente, solo se logra modificar la forma de pago mediante API. En caso de necesitar modificar la forma de pago desde la interfáz de usuario, se deberá repetir el proceso de configuración por API, ya que al Guardar los cambios, se irá a tomar valor vacío por defecto.
-</div>
+>❗ IMPORTANTE: Actualmente, solo se logra modificar la forma de pago mediante API. En caso de necesitar modificar la forma de pago desde la interfáz de usuario, se deberá repetir el proceso de configuración por API, ya que al Guardar los cambios, se irá a tomar valor vacío por defecto.
diff --git a/docs/tutorials/es/setting-up-triggers.md b/docs/tutorials/es/setting-up-triggers.md
index ced91c946..aafd54b17 100644
--- a/docs/tutorials/es/setting-up-triggers.md
+++ b/docs/tutorials/es/setting-up-triggers.md
@@ -15,9 +15,7 @@ legacySlug: configurar-triggers
 subcategory: 5tSNDlvmik8gGuKw2goW4q
 ---
 
-<div class="alert alert-info">
-Este artículo hace referencia al Master Data v2. Si desea utilizar el Master Data v1, vea los pasos de <a href="https://help.vtex.com/es/tutorial/creando-trigger-en-el-master-data--tutorials_1270">este artículo</a>.
-</div>
+>ℹ️ Este artículo hace referencia al Master Data v2. Si desea utilizar el Master Data v1, vea los pasos de [este artículo](https://help.vtex.com/es/tutorial/creando-trigger-en-el-master-data--tutorials_1270).
 
 Un trigger de Master Data es una acción ejecutada después de una inserción o una actualización.
 
diff --git a/docs/tutorials/es/setting-up-webpay2p-gateway.md b/docs/tutorials/es/setting-up-webpay2p-gateway.md
index 527acf14a..27e7bb9c8 100644
--- a/docs/tutorials/es/setting-up-webpay2p-gateway.md
+++ b/docs/tutorials/es/setting-up-webpay2p-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-webpay2p
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 [WebPay](https://publico.transbank.cl/productos-y-servicios/soluciones-para-ventas-internet/webpay.cl) es una [afiliación](https://help.vtex.com/es/tutorial/o-que-e-um-gateway-de-pagamentos) exclusiva para los clientes chilenos.  Para configurar la solución y procesar sus pagos con WebPay, realice los siguientes pasos:
 
diff --git a/docs/tutorials/es/setup-safetypay.md b/docs/tutorials/es/setup-safetypay.md
index fb8e48498..6d764d27a 100644
--- a/docs/tutorials/es/setup-safetypay.md
+++ b/docs/tutorials/es/setup-safetypay.md
@@ -15,7 +15,7 @@ legacySlug: configurar-safetypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Esta integración de pago ya no se puede configurar en la plataforma debido al <a href="https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14">proceso de descontinuación de los proveedores legados</a> y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.</div>
+>❗ Esta integración de pago ya no se puede configurar en la plataforma debido al [proceso de descontinuación de los proveedores legados](https://help.vtex.com/es/announcements/descontinuacion-de-conectores-de-pago-legados-en-2024--4R5YIjUu1IWkiOHzXtQU14) y el artículo pronto se eliminará del Help Center. Consulte con su proveedor para obtener más información sobre el desarrollo de la nueva integración de pago y los pasos necesarios para migrar la configuración en su tienda.
 
 SafetyPay es una solución de pago que conecta directamente el checkout de su tienda al banco de su cliente. En esta solución, su cliente elige SafetyPay como medio de pago y es *redireccionado* para el ambiente seguro de Internet banking elegido. Una vez redireccionado, el cliente puede hacer una transferencia bancaria y realizar el pago del pedido.
 
diff --git a/docs/tutorials/es/sharpspring-suiteshare.md b/docs/tutorials/es/sharpspring-suiteshare.md
index 8b4b93a8a..11affd4c9 100644
--- a/docs/tutorials/es/sharpspring-suiteshare.md
+++ b/docs/tutorials/es/sharpspring-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: sharpspring-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/shipping-options-beta.md b/docs/tutorials/es/shipping-options-beta.md
index eb1934972..c01bd2c73 100644
--- a/docs/tutorials/es/shipping-options-beta.md
+++ b/docs/tutorials/es/shipping-options-beta.md
@@ -15,9 +15,7 @@ legacySlug: delivery-options-beta
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-<p>Esta funcionalidad se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarla. Si tienes alguna duda, ponte en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarla. Si tienes alguna duda, ponte en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
 
 **Opciones de envío** es la funcionalidad que permite a los administradores de la tienda crear, editar y gestionar las opciones de envío desde un mismo lugar y garantizar mayor simplicidad y eficiencia en la gestión de su operación. El término «envío» es la forma general de referirse a la entrega o recogida de un pedido. Al configurar cada opción de envío, el administrador de la tienda determina:
 
diff --git a/docs/tutorials/es/shipping-policy-beta.md b/docs/tutorials/es/shipping-policy-beta.md
index f96e97256..642eade80 100644
--- a/docs/tutorials/es/shipping-policy-beta.md
+++ b/docs/tutorials/es/shipping-policy-beta.md
@@ -20,11 +20,7 @@ Política de envío es un conjunto de reglas que definen las opciones y condicio
 
 Todos estos ajustes se basan principalmente en el contrato que su tienda tiene con una [transportadora](https://help.vtex.com/es/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE), un prestador de servicios o cualquier otro tipo de contrato de servicio de envío que su tienda ofrece a los consumidores.
 
-<div class="alert alert-info">
-
-Es posible que una misma transportadora sea la base de varias políticas de envío, cada una con sus particularidades. A continuación, se explica cómo crear, editar y eliminar políticas de envío
-
-</div>
+>ℹ️ Es posible que una misma transportadora sea la base de varias políticas de envío, cada una con sus particularidades. A continuación, se explica cómo crear, editar y eliminar políticas de envío
 
 A través de la plataforma VTEX es posible: 
 
diff --git a/docs/tutorials/es/shipping-rate-template.md b/docs/tutorials/es/shipping-rate-template.md
index b18688507..b02fdb7de 100644
--- a/docs/tutorials/es/shipping-rate-template.md
+++ b/docs/tutorials/es/shipping-rate-template.md
@@ -24,9 +24,7 @@ Para registrar los precios de envío a través de la plantilla de flete es neces
 1. [Completar los campos de la plantilla](#completar-los-campos-de-la-plantilla)
 2. [Enviar el archivo por el Admin VTEX](#enviar-el-archivo-por-el-admin-vtex)
 
-<div class="alert alert-info"> 
-También hay una forma de registrar los precios de envío a través del módulo Tarifas de envío. Recomendamos que utilice la <a href="https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127">plantilla de flete</a> cuando se incluyan múltiples rangos de código postal, y utilizar Tarifas de envío para administrar los precios de los fletes registrados y para registrar cada rango de código postal individualmente. 
-</div>
+>ℹ️ También hay una forma de registrar los precios de envío a través del módulo Tarifas de envío. Recomendamos que utilice la [plantilla de flete](https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127) cuando se incluyan múltiples rangos de código postal, y utilizar Tarifas de envío para administrar los precios de los fletes registrados y para registrar cada rango de código postal individualmente.
 
 ## Completar los campos de la plantilla
 
@@ -175,9 +173,7 @@ Vea la siguiente tabla para entender cada campo en detalle.
 </tbody>
 </table>
 
-<div class="alert alert-info"> 
-Para facilitar el uso de los términos en nuestra documentación utilizamos «peso» en vez de «masa». 
-</div>  
+>ℹ️ Para facilitar el uso de los términos en nuestra documentación utilizamos «peso» en vez de «masa».  
 
 Vea el siguiente ejemplo de cómo rellenar los campos, teniendo en cuenta el formato aceptado en cada columna. 
 
@@ -196,13 +192,9 @@ El envío de la plantilla se realiza en el registro o en la edición de la _Pol
 
   ![upload tarifas envioES](https://images.ctfassets.net/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/b788e6926bffa8aa5a70db06ca1ccba7/upload_tarifas_envioES.png)
 
-<div class="alert alert-warning">
-Para registrar una <b>nueva</b> Política de envío se debe completar otros campos además de la plantilla de flete.  Aprenda cómo crear, editar y completar todos los campos necesarios en el artículo <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">Política de envío</a>.
-</div>
+>⚠️ Para registrar una **nueva** Política de envío se debe completar otros campos además de la plantilla de flete.  Aprenda cómo crear, editar y completar todos los campos necesarios en el artículo [Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 
-<div class="alert alert-danger">
-Cada pestaña de la plantilla no debe superar las 65 536 filas. Se pueden crear varias pestañas en la misma plantilla, respetando el límite de filas. No hay un límite en el número de pestañas dentro del archivo. Sin embargo, el archivo no puede superar los 10MB. En caso de que sea necesario, comprima el archivo en formato <b>.zip</b>. Si esto no es suficiente, divídalo en dos archivos y registre otra política de envío para cargar el segundo archivo creado. 
-</div>
+>❗ Cada pestaña de la plantilla no debe superar las 65 536 filas. Se pueden crear varias pestañas en la misma plantilla, respetando el límite de filas. No hay un límite en el número de pestañas dentro del archivo. Sin embargo, el archivo no puede superar los 10MB. En caso de que sea necesario, comprima el archivo en formato **.zip**. Si esto no es suficiente, divídalo en dos archivos y registre otra política de envío para cargar el segundo archivo creado.
 
 Si hay algún problema al completar los campos del archivo enviado, recibirá un <i>_email</i>_ para informarle del error. Asegúrese de revisar si la plantilla se completó correctamente antes de hacer un nuevo intento de envío.
 
diff --git a/docs/tutorials/es/shipping-rates.md b/docs/tutorials/es/shipping-rates.md
index ea8346772..541947852 100644
--- a/docs/tutorials/es/shipping-rates.md
+++ b/docs/tutorials/es/shipping-rates.md
@@ -18,9 +18,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 Las tarifas de envío son los costos de envío que su tienda ofrece a los clientes, y están relacionadas a las [Políticas de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140) de su tienda. Por lo tanto, debe configurar los precios acordados entre su tienda y los responsables de las entregas (como transportadoras, puntos de recogida, proveedores de servicios) como **Tarifas de envío.**
 
-<div class="alert alert-warning">
-El <a href="https://help.vtex.com/es/tutorial/costo-final-del-envio--5bwhIO108VA5Y2YOpef9lV">costo final del envío</a> para el cliente incluye la tarifa de envío, los <a href="https://help.vtex.com/es/tutorial/adicionales-de-flete--2vqGwMn0LabkOHY6zSHYNV">adicionales de flete</a> y el costo del muelle con stock.
-</div>
+>⚠️ El [costo final del envío](https://help.vtex.com/es/tutorial/costo-final-del-envio--5bwhIO108VA5Y2YOpef9lV) para el cliente incluye la tarifa de envío, los [adicionales de flete](https://help.vtex.com/es/tutorial/adicionales-de-flete--2vqGwMn0LabkOHY6zSHYNV) y el costo del muelle con stock.
 
 ![Tarifa envio ES](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/d97d710440d9d301191074a193396a96/Tarifa_envio_ES.svg)
 
@@ -29,10 +27,6 @@ En el Admin VTEX, hay dos maneras de registrar las tarifas de envío:
 * En la página `Estrategia de envío`: al añadir una nueva `Política de envío` o actualizar una política ya registrada, debe cargar la [plantilla de flete](https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127). Esta es la forma de registro de tarifas de envío más indicada para cuando hay que agregar muchos códigos postales con sus tarifas de precios de entrega. 
 * En la página `Tarifas de envío`: para cuando desea actualizar tarifas ya registradas o agregar pocas tarifas.  Puede editar y agregar nuevos precios de envío sin tener que usar la plantilla de flete. Para saber más, acceda al [tutorial de gestión de tarifas](https://help.vtex.com/es/tutorial/gestionar-las-tarifas-de-envio--tutorials_141).
 
-<div class="alert alert-warning">
-Puede configurar la ubicación por polígono, el <b>costo de seguro</b> y el <b>adicional de flete</b> solo utilizando la <b><a href="https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127">plantilla de flete</b>. 
-</div>
+>⚠️ Puede configurar la ubicación por polígono, el **costo de seguro** y el **adicional de flete** solo utilizando la **<a href="https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127">plantilla de flete**.
 
-<div class="alert alert-info">
-Cuando tenga que actualizar o registrar varios precios de envío, recomendamos utilizar la <a href="https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127">plantilla de flete</a> en vez del módulo <b>Tarifas de envío</b>. Si desea comprobar cómo se mostrarán las tarifas de envío registradas al cliente final, utilice el módulo <b><a href="https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144">Simulador de envío</b></a>.
-</div>
+>ℹ️ Cuando tenga que actualizar o registrar varios precios de envío, recomendamos utilizar la [plantilla de flete](https://help.vtex.com/es/tutorial/plantilla-de-flete--tutorials_127) en vez del módulo **Tarifas de envío**. Si desea comprobar cómo se mostrarán las tarifas de envío registradas al cliente final, utilice el módulo **[Simulador de envío**](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144).
diff --git a/docs/tutorials/es/shipping-simulation.md b/docs/tutorials/es/shipping-simulation.md
index 575689f96..1cec1ee0c 100644
--- a/docs/tutorials/es/shipping-simulation.md
+++ b/docs/tutorials/es/shipping-simulation.md
@@ -22,14 +22,14 @@ El simulador también se puede utilizar para validar la configuración de la  **
 * **Disponibilidad de un ítem:** el simulador verifica si el ítem cuenta con _stock_ y si se puede realizar su entrega (si hay transportadoras registradas para esa región, por ejemplo). Si uno de los dos criterios no se cumple, el simulador entiende que el ítem no está disponible.
 * **Disponibilidad de Sellers White Label:** el simulador selecciona al franquiciado más cercano a la dirección de entrega (la configuración logística es calculada a través del ambiente del _Seller White Label_, y no por la Main Account).
 
-<div class="alert alert-warning"> 
-Puede haber una divergencia entre el precio final indicado por el simulador y el precio real en su tienda, ya que la simulación no considera:
-<ul>
-<li>Promociones aplicadas a esos ítems.</li>
-<li>Descuentos de flete configurados a través de promociones.</li>
-<li>El plazo de entrega total que se muestra en el resultado de la simulación no contempla el campo <b>Fecha de previsión de llegada (Preventa)</b>  <a href="https://help.vtex.com/es/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY">del registro del ítem.</li></a>
-</ul>
-</div>
+>⚠️ Puede haber una divergencia entre el precio final indicado por el simulador y el precio real en su tienda, ya que la simulación no considera:
+>
+> *Promociones aplicadas a esos ítems.
+>
+> *Descuentos de flete configurados a través de promociones.
+>
+> *El plazo de entrega total que se muestra en el resultado de la simulación no contempla el campo **Fecha de previsión de llegada (Preventa)**  [del registro del ítem.](https://help.vtex.com/es/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY)
+> 
 
 ## Simular el envío
 
diff --git a/docs/tutorials/es/shopify-suiteshare.md b/docs/tutorials/es/shopify-suiteshare.md
index 90a7db481..17b0f87e9 100644
--- a/docs/tutorials/es/shopify-suiteshare.md
+++ b/docs/tutorials/es/shopify-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: shopify-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/sku-bindings.md b/docs/tutorials/es/sku-bindings.md
index 506b5fa73..7927af52a 100644
--- a/docs/tutorials/es/sku-bindings.md
+++ b/docs/tutorials/es/sku-bindings.md
@@ -97,9 +97,7 @@ Para remover el vínculo entre el SKU del _seller_ y el SKU del _marketplace_, s
 2. En la línea del ítem deseado, haz clic en el ícono menú <i class="fas fa-ellipsis-v"></i>.
 3. Haz clic en <i class="far fa-trash-alt"></i> `Remover`.
 
-<div class="alert alert-warning">
-Remover un vínculo hace que el SKU del <i>seller</i> deje de formar parte del catálogo del <i>marketplace</i>; por lo tanto, desaparece de la lista de la página <b>Vínculos de SKU</b>. No se puede recuperar un vínculo que se removió, pero el <i>seller</i> puede reenviarle el SKU al <i>marketplace</i>, el cual <a href="https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus--tutorials_396">cataloga</a> el SKU nuevamente y hace que esté disponible otra vez.
-</div>
+>⚠️ Remover un vínculo hace que el SKU del <i>seller</i> deje de formar parte del catálogo del <i>marketplace</i>; por lo tanto, desaparece de la lista de la página **Vínculos de SKU**. No se puede recuperar un vínculo que se removió, pero el <i>seller</i> puede reenviarle el SKU al <i>marketplace</i>, el cual [cataloga](https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus--tutorials_396) el SKU nuevamente y hace que esté disponible otra vez.
 
 ## Exportar
 
diff --git a/docs/tutorials/es/sku-registration-fields.md b/docs/tutorials/es/sku-registration-fields.md
index 0a2a43d74..5be8d1b41 100644
--- a/docs/tutorials/es/sku-registration-fields.md
+++ b/docs/tutorials/es/sku-registration-fields.md
@@ -15,9 +15,7 @@ legacySlug: campos-de-registro-de-sku
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class="alert alert-warning">
-  <p>Hay un límite de 50 SKU por producto. Para solicitar que se amplíe el límite, ponte en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>⚠️ Hay un límite de 50 SKU por producto. Para solicitar que se amplíe el límite, ponte en contacto con <a href= "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
 
 Para entender mejor el significado de cada campo del registro, vea la descripción completa de los ítems relacionados en la página:
 
@@ -77,9 +75,7 @@ Luego de rellenar los campos, haga clic en Guardar. Para continuar con el regist
 
 ## Imágenes
 
-<div class="alert alert-info">
-  <p>La imagen del SKU tiene un límite de tamaño de 3200 x 3200 píxeles.</p>
-</div>
+>ℹ️ La imagen del SKU tiene un límite de tamaño de 3200 x 3200 píxeles.
 
 Cómo registrar una nueva imagen:
 
@@ -138,7 +134,5 @@ Luego de rellenar los campos necesarios, basta con hacer clic en Guardar, en la
 - [Rellenar campos de registro del producto](/es/tutorial/campos-de-registro-de-producto--4dYXWIK3zyS8IceKkQseke)
 - [Rellenar campos de la plantilla de importación](/es/tutorial/preencher-campos-da-planilha-de-importacao--4nYhx63Q5yokQWaMguaIgI)
 
-<div class="alert alert-danger">
- Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el <a href="url">ID del SKU</a> no debe contener <b>el número cero a la izquierda</b>. Por ejemplo, el sistema no reconoce ID con el formato <code>01</code>, <code>02</code> , <code>021</code>, ya que espera el formato <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ Para garantizar que los ítems agregados al stock estén disponibles para venta en la tienda, el [ID del SKU](url) no debe contener **el número cero a la izquierda**. Por ejemplo, el sistema no reconoce ID con el formato `01`, `02` , `021`, ya que espera el formato `1`, `2`, `21`.
 
diff --git a/docs/tutorials/es/sla-errors-in-marketplace-integration-orders.md b/docs/tutorials/es/sla-errors-in-marketplace-integration-orders.md
index 500da52c9..2c60a262c 100644
--- a/docs/tutorials/es/sla-errors-in-marketplace-integration-orders.md
+++ b/docs/tutorials/es/sla-errors-in-marketplace-integration-orders.md
@@ -31,9 +31,7 @@ Los problemas más comunes que causan errores de SLA son:
 
 Después de solucionar el error, el pedido se debe reprocesar manualmente. En su Admin, en el módulo **MARKETPLACE > Integraciones > Pedidos**, haga clic en el pedido con error. Después de eso, el botón **Acciones** se vuelve visible, haga clic en el mismo y elija la opción **Reprocesar**.
 
-<div class="alert alert-info">
-Si el error persiste, abra un <a href="https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt">ticket para el soporte VTEX</a>.
-</div>
+>ℹ️ Si el error persiste, abra un [ticket para el soporte VTEX](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt).
 
 ### Sepa más
 
diff --git a/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md b/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md
index 8b55b64cd..10c4b903d 100644
--- a/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md
+++ b/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md
@@ -17,9 +17,7 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 
 SmartCheckout permite que los datos del cliente se completen automáticamente durante el Checkout. Para que esto suceda, el cliente solo debe ingresar el email registrado en la tienda. Esta funcionalidad reduce el tiempo de compra y elimina la necesidad de ingresar los datos cada vez que se realiza una compra en la misma tienda.
 
-<div class="alert alert-info">
-Para que SmartCheckout reutilice los datos del cliente durante el Checkout, es necesario que el cliente haya realizado alguna compra o que tenga un perfil registrado en la tienda.
-</div>
+>ℹ️ Para que SmartCheckout reutilice los datos del cliente durante el Checkout, es necesario que el cliente haya realizado alguna compra o que tenga un perfil registrado en la tienda.
 
 ## Datos de registro del cliente
 
diff --git a/docs/tutorials/es/smartcheckout-v5-general-characteristics.md b/docs/tutorials/es/smartcheckout-v5-general-characteristics.md
index 76acfa084..53580dec7 100644
--- a/docs/tutorials/es/smartcheckout-v5-general-characteristics.md
+++ b/docs/tutorials/es/smartcheckout-v5-general-characteristics.md
@@ -53,9 +53,7 @@ Usted puede utilizar los archivos `checkout5-custom.js` y `orderplaced2-custo
 4. En el menú __Archivos__, ubicado en el lado derecho de la página, haga clic en los que desea realizar ajustes en el código.
 5. Haga clic en `Guardar`
 
-<div class="alert alert-warning">
-  Personalizar archivos de JavaScript puede ser dañino para su Checkout. VTEX <b>no recomienda</b> personalizaciones y no es responsable de los daños causados por este código.
-</div>
+>⚠️ Personalizar archivos de JavaScript puede ser dañino para su Checkout. VTEX **no recomienda** personalizaciones y no es responsable de los daños causados por este código.
 
 __IMPORTANTE:__ no utilize estos archivos para insertar tags de marketing e integraciones. Si las necesita, utilize Google Tag Manager.
 
diff --git a/docs/tutorials/es/special-conditions.md b/docs/tutorials/es/special-conditions.md
index 1b260f437..9e683caf9 100644
--- a/docs/tutorials/es/special-conditions.md
+++ b/docs/tutorials/es/special-conditions.md
@@ -136,9 +136,7 @@ Digamos que desea ofrecer una condición especial de pago para clientes que pagu
 
 En este caso, debe seleccionar el banco emisor responsable de esta tarjeta seguido del nombre de su tienda en el campo __Co-brand__.
 
-<div class="alert alert-warning">
-Tenga en cuenta que, de manera predeterminada, la información sobre si una tarjeta tiene o no una marca compartida <strong>no</strong> se agrega a la base de datos VTEX. Por lo tanto, si su tienda desea segmentar una condición de pago de acuerdo con las tarjetas, debe enviar un ticket con la lista de tarjetas de marca compartida al equipo de soporte de VTEX.
-</div>
+>⚠️ Tenga en cuenta que, de manera predeterminada, la información sobre si una tarjeta tiene o no una marca compartida **no** se agrega a la base de datos VTEX. Por lo tanto, si su tienda desea segmentar una condición de pago de acuerdo con las tarjetas, debe enviar un ticket con la lista de tarjetas de marca compartida al equipo de soporte de VTEX.
 
 ## Período
 
@@ -160,7 +158,5 @@ Cómo configurar el período en la condición de pago
 
 Imagine que su tienda normalmente ofrece un pago en cuotas en hasta 6x sin intereses, pero usted desea aprovechar las ventas del final de año para ofrecer un pago en cuotas en hasta 12x sin intereses. En ese caso, bastaría seguir los pasos arriba y catastrar el período para la condición de pago, dejar de ser aplicada el 01 de janeiro del año siguiente, por ejemplo.
 
-<div class="alert alert-warning">
-Las condiciones de pago poseen un caché de hasta 10 minutos en el Smart Checkout. Luego, cualquier cambio en las Condiciones de Pago del modulo <strong>Pagos</strong> puede llevar hasta 10 minutos para entrar en producción en el Smart Checkout.
-</div>
+>⚠️ Las condiciones de pago poseen un caché de hasta 10 minutos en el Smart Checkout. Luego, cualquier cambio en las Condiciones de Pago del modulo **Pagos** puede llevar hasta 10 minutos para entrar en producción en el Smart Checkout.
 
diff --git a/docs/tutorials/es/split-payment.md b/docs/tutorials/es/split-payment.md
index 526206c17..ca16ca6c1 100644
--- a/docs/tutorials/es/split-payment.md
+++ b/docs/tutorials/es/split-payment.md
@@ -15,9 +15,7 @@ legacySlug: split-de-pagos
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Esta es una solución de pagos para marketplace.
-</div>
+>⚠️ Esta es una solución de pagos para marketplace.
 
 Para garantizar que nuestros clientes de [marketplace](https://help.vtex.com/es/tutorial/que-es-un-marketplace--680lLJTnmEAmekcC0MIea8) automáticamente dividan el pago entre todos los [sellers](https://help.vtex.com/es/tutorial/que-es-un-seller--5FkLvhZ3Few4CWWIuYOK2w), establezcan comisiones basadas en un porcentaje fijo y permanece operando de acuerdo con las regulaciones vigentes, VTEX ofrece el __Split de pagos__.
 
diff --git a/docs/tutorials/es/store-overview-beta.md b/docs/tutorials/es/store-overview-beta.md
index 0b15015d1..ff74cbf1f 100644
--- a/docs/tutorials/es/store-overview-beta.md
+++ b/docs/tutorials/es/store-overview-beta.md
@@ -15,9 +15,7 @@ legacySlug: vista-general-de-la-tienda-beta
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class="alert alert-info"> 
-La versión actualizada de la página Vista general de la tienda (Beta) está disponible para uso gratuito en el Admin VTEX durante su periodo beta, o hasta que VTEX lo decida. Es importante tener en cuenta que en el futuro podrían aplicarse tarifas adicionales. Además, la página de Vista general, actualmente presente en el VTEX Admin, seguirá estando disponible para su uso por el momento.
-</div>
+>ℹ️ La versión actualizada de la página Vista general de la tienda (Beta) está disponible para uso gratuito en el Admin VTEX durante su periodo beta, o hasta que VTEX lo decida. Es importante tener en cuenta que en el futuro podrían aplicarse tarifas adicionales. Además, la página de Vista general, actualmente presente en el VTEX Admin, seguirá estando disponible para su uso por el momento.
 
 La página Vista general (Beta) de tu Admin VTEX proporciona un seguimiento en tiempo real de tu operación en el día actual, ofreciendo visibilidad en las métricas para que tu equipo y tú tengan un rápido feedback sobre las acciones realizadas en la tienda y puedan actuar con prontitud para implementar mejoras. 
 
@@ -65,9 +63,7 @@ Puedes utilizar diferentes  [métricas](#metricas) y gráficos de [monitoreo](#m
 | Resultados financieros  | - [Ingresos capturados](#monitoreo) <br>- [Ticket promedio](#metricas) <br>- [Productos con mayores ingresos](#metricas)                                                                                                                                                                                                               |
 | Conversión              | - [Tasa de conversión](#metricas) <br>- [Embudo de ventas](#embudo-de-ventas) <br>- [Pedidos capturados](#monitoreo), comparado con el número de Pedidos cancelados. Los resultados obtenidos pueden guiar a tu equipo a identificar aquellos problemas operativos en el fulfillment o atención al cliente que causaron los pedidos cancelados. |
 
-<div class="alert alert-info"> 
-Importante: mientras que los gráficos de Monitoreo se actualizan en hasta tres minutos, las Métricas se actualizan cada quince minutos, lo que puede influir en tu análisis de resultados. Más información en <a href="#atualizacion-de-datos">Actualización de datos</a>.
-</div>
+>ℹ️ Importante: mientras que los gráficos de Monitoreo se actualizan en hasta tres minutos, las Métricas se actualizan cada quince minutos, lo que puede influir en tu análisis de resultados. Más información en [Actualización de datos](#atualizacion-de-datos).
 
 ### Analizar resultados de campañas
 
diff --git a/docs/tutorials/es/subscription-plans.md b/docs/tutorials/es/subscription-plans.md
index 20dda4ffd..f9862a242 100644
--- a/docs/tutorials/es/subscription-plans.md
+++ b/docs/tutorials/es/subscription-plans.md
@@ -63,17 +63,13 @@ Cada columna de la lista de planes de suscripción muestra información sobre el
     * **Activo:** significa que el plan está disponible para que los clientes lo utilicen al crear nuevas suscripciones con los productos asociados.
     * **Inactivo:** significa que el plan no está disponible al crear nuevas suscripciones, aunque tenga productos asociados.
 
-<div class="alert alert-info">
-<p>Los planes inactivos se desactivan solo para las nuevas compras. Si hay clientes que ya habían creado suscripciones mientras el plan estaba activo, el plan seguirá creando pedidos con las frecuencias establecidas durante los siguientes ciclos de esos clientes incluso después de ser desactivado.</p>
-</div>
+>ℹ️ Los planes inactivos se desactivan solo para las nuevas compras. Si hay clientes que ya habían creado suscripciones mientras el plan estaba activo, el plan seguirá creando pedidos con las frecuencias establecidas durante los siguientes ciclos de esos clientes incluso después de ser desactivado.
 
 * **Botón** <i class="fas fa-ellipsis-v"></i>**:** al hacer clic en este botón, puede seleccionar las siguientes acciones.
     * **Editar:** abre la página para editar el plan de suscripción.
     * **Eliminar:** permite eliminar el plan de forma permanente. Antes de eliminar, aparece una pantalla para confirmar la acción. Después de hacer clic en `Eliminar plan`, esta acción **no** puede revertirse.
 
-<div class="alert alert-warning">
-  <p>Cuando elimina un plan, <strong>no</strong> se generarán los pedidos de los clientes que compraban con las frecuencias de ese plan a partir del siguiente ciclo de suscripción. Para evitar que se use el plan al crear nuevas suscripciones, pero mantener los próximos pedidos de los clientes que tienen suscripciones existentes, debe desactivar el plan en lugar de eliminarlo.</p>
-</div>
+>⚠️ Cuando elimina un plan, **no** se generarán los pedidos de los clientes que compraban con las frecuencias de ese plan a partir del siguiente ciclo de suscripción. Para evitar que se use el plan al crear nuevas suscripciones, pero mantener los próximos pedidos de los clientes que tienen suscripciones existentes, debe desactivar el plan en lugar de eliminarlo.
 
 ## Mostrar filas
 
diff --git a/docs/tutorials/es/table-of-base-prices.md b/docs/tutorials/es/table-of-base-prices.md
index 24c069b3a..a6233a51f 100644
--- a/docs/tutorials/es/table-of-base-prices.md
+++ b/docs/tutorials/es/table-of-base-prices.md
@@ -25,9 +25,7 @@ Para comprender mejor el significado de cada campo de la [plantilla de registro
 
 - **List Price**: El precio de lista es un precio que funciona como un precio antiguo de SKU que recibió un descuento. También se conoce como "precio De" y puede mostrarse en la vitrina de su tienda. Este es un campo opcional en el registro de un precio.
 
-<div class="alert alert-info">
-<p>En las columnas <b>Cost Price</b>, <b>Base Price</b> y <b>List Price</b>, puede introducir valores con decimales separados por punto. Ejemplo: <code>4.95</code>.</p>
-</div>
+>ℹ️ En las columnas **Cost Price**, **Base Price** y **List Price**, puede introducir valores con decimales separados por punto. Ejemplo: `4.95`.
 
 Los siguientes campos son opcionales en la plantilla, se exportan solo para exhibición y para facilitar la identificación de un SKU. Para visualizar estos campos en la plantilla, debe seleccionar la opción *Incluir metadatos en las tablas exportadas* en la exportación.
 
diff --git a/docs/tutorials/es/telesales-toolbar.md b/docs/tutorials/es/telesales-toolbar.md
index add71d64e..23993670c 100644
--- a/docs/tutorials/es/telesales-toolbar.md
+++ b/docs/tutorials/es/telesales-toolbar.md
@@ -29,9 +29,7 @@ Para habilitar la barra de herramientas de televentas, el administrador de la ti
 
 Para saber cómo personalizar la apariencia de la barra de herramientas en el módulo CMS, consulte el artículo [Personalizar la barra de herramientas de televentas](https://help.vtex.com/es/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg).
 
-<div class="alert alert-warning">
-<p>Para las tiendas desarrolladas en <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, se necesita configurar la aplicación <strong>VTEX Telemarketing</strong> para habilitar y personalizar la barra de herramientas de televentas. Para saber más sobre este proceso, acceda a la guía <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-telemarketing">VTEX Telemarketing</a>.</p>
-</div>
+>⚠️ Para las tiendas desarrolladas en [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), se necesita configurar la aplicación **VTEX Telemarketing** para habilitar y personalizar la barra de herramientas de televentas. Para saber más sobre este proceso, acceda a la guía [VTEX Telemarketing](https://developers.vtex.com/vtex-developer-docs/docs/vtex-telemarketing).
 
 ## Entrar como cliente
 
diff --git a/docs/tutorials/es/testing-webservice-using-soapui.md b/docs/tutorials/es/testing-webservice-using-soapui.md
index 13bb64f0c..ba8820504 100644
--- a/docs/tutorials/es/testing-webservice-using-soapui.md
+++ b/docs/tutorials/es/testing-webservice-using-soapui.md
@@ -15,11 +15,13 @@ legacySlug: probando-webservice-con-soapui
 subcategory: 1vwB9FtTSQmcSewQw02QoW
 ---
 
-<div class="alert alert-danger"><p>Atención: sólo los métodos SOAP pertinentes al <strong>catálogo</strong> son válidos.</p>
-<p><strong>Todos los demás métodos del Web Service serán discontinuados después de 28/02/2017.</strong></p>
-<p>Utilice las API REST equivalentes disponibles en nuestro<a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atención: sólo los métodos SOAP pertinentes al **catálogo** son válidos.
+>
+> **Todos los demás métodos del Web Service serán discontinuados después de 28/02/2017.**
+>
+> Utilice las API REST equivalentes disponibles en nuestro[Developer Docs](//help.vtex.com/developer-docs/).
 
-<div class="alert alert-warning">Las configuraciones documentadas en este artículo son realizadas en un ambiente fuera de VTEX, por lo tanto, pueden ser discontinuadas sin previo aviso.</div>
+>⚠️ Las configuraciones documentadas en este artículo son realizadas en un ambiente fuera de VTEX, por lo tanto, pueden ser discontinuadas sin previo aviso.
 
 SoapUI es una herramienta que puede ser utilizada para simular conexión y ejecución de métodos de un determinado webservice, sin tener la necesidad de hacer eso vía desarrollo.
 
@@ -44,6 +46,8 @@ Efectúe el login con los datos de webservice deseado. Después de efectuar el l
 3. Localice el botón __"Auth"__ y repita la autenticación antes de ejecutar el método;
 4. Ejecute el método.
 
-<div class="alert alert-danger"><p>Atenção: sólo los métodos SOAP correspondientes al <strong>catálogo</strong> son válidos.</p>
-<p><strong>Todos los demás métodos están descontinuados.</strong></p>
-<p>Utilice las API REST equivalentes disponibles en nuestro <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: sólo los métodos SOAP correspondientes al **catálogo** son válidos.
+>
+> **Todos los demás métodos están descontinuados.**
+>
+> Utilice las API REST equivalentes disponibles en nuestro [Developer Docs](//help.vtex.com/developer-docs/).
diff --git a/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md b/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md
index 8daa841e3..b9784c76b 100644
--- a/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md
+++ b/docs/tutorials/es/the-order-was-split-into-packages-with-separate-deliveries.md
@@ -32,9 +32,7 @@ La fecha de entrega de cada paquete se modifica en función del valor de `shippi
 
 Para evitar que se dividan los paquetes de pedidos que incluyen productos de preventa, puedes configurar [grupos de envío](https://help.vtex.com/es/tutorial/como-funciona-a-remessa). De este modo, puedes agrupar en un solo conjunto todos los paquetes que serán entregados por la misma transportadora y provenientes del mismo [muelle](https://help.vtex.com/es/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
 
-<div class="alert alert-danger">
-Configurar los grupos de envío aplicará este comportamiento a todos los pedidos con fechas de entrega diferentes y no solo a los que tengan productos de preventa.
-</div>
+>❗ Configurar los grupos de envío aplicará este comportamiento a todos los pedidos con fechas de entrega diferentes y no solo a los que tengan productos de preventa.
 
 ### Configurar grupos de envío
 
diff --git a/docs/tutorials/es/the-risk-assessment-process.md b/docs/tutorials/es/the-risk-assessment-process.md
index 48a18c820..25b5c48be 100644
--- a/docs/tutorials/es/the-risk-assessment-process.md
+++ b/docs/tutorials/es/the-risk-assessment-process.md
@@ -62,6 +62,4 @@ Temas:
 Ingrese su [nombre de cuenta](https://help.vtex.com/es/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) VTEX para acceder a la documentación.
 <iframe src="https://help.vtex.com/insertaccountname?id=1ayXEtqawI9yuxFXutiITh" title="Ingrese su nombre de cuenta y haga click en el botón." frameBorder="0" width="400" height="50"></iframe>
 
-<div class="alert alert-warning">
-  Si tiene dificultades para acceder a las preguntas frecuentes, intente instalar la última versión de la aplicación <code>vtex.admin-docs</code> usando la <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">CLI de VTEX</a> y repetir el proceso.
-</div>
+>⚠️ Si tiene dificultades para acceder a las preguntas frecuentes, intente instalar la última versión de la aplicación `vtex.admin-docs` usando la [CLI de VTEX](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) y repetir el proceso.
diff --git a/docs/tutorials/es/total-shipping-cost.md b/docs/tutorials/es/total-shipping-cost.md
index 61bc5e138..d65022b15 100644
--- a/docs/tutorials/es/total-shipping-cost.md
+++ b/docs/tutorials/es/total-shipping-cost.md
@@ -33,7 +33,5 @@ Así que, en general, el costo final del envío puede calcularse así:
 
 ![Custo-final-envio-ES](https://images.ctfassets.net/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/48b3d941065ab47cb55c7b4590b993bd/Custo-final-envio-ES.svg)
 
-<div class="alert alert-danger">
-Si el <b>adicional de precio</b> es inferior al <b>adicional de seguro,</b> la tarifa considerada es el adicional de seguro. El adicional de precio no se tomará en cuenta en el cálculo de la tarifa final.<p>
-La elección de la transportadora para el envío de los ítems considera únicamente el precio de la Tarifa de envío, sin tener en cuenta los costos del muelle y del almacén (si existen). Para simular el escenario de entrega para el cliente utilice el<a href="https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144">Simulador de envío</a>.
-</div>
+>❗ Si el **adicional de precio** es inferior al **adicional de seguro,** la tarifa considerada es el adicional de seguro. El adicional de precio no se tomará en cuenta en el cálculo de la tarifa final.<p>
+> La elección de la transportadora para el envío de los ítems considera únicamente el precio de la Tarifa de envío, sin tener en cuenta los costos del muelle y del almacén (si existen). Para simular el escenario de entrega para el cliente utilice el[Simulador de envío](https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144).
diff --git a/docs/tutorials/es/tracking-your-sales-analytics.md b/docs/tutorials/es/tracking-your-sales-analytics.md
index bd532ba04..7e94c87d4 100644
--- a/docs/tutorials/es/tracking-your-sales-analytics.md
+++ b/docs/tutorials/es/tracking-your-sales-analytics.md
@@ -27,7 +27,7 @@ La siguiente tabla describe las principales métricas disponibles en Insights. T
 | Ingresos        | Valor total calculado según los pedidos aprobados.       |
 | Ticket promedio | Valor promedio de los ingresos por pedido.       |
 
-<div class="alert alert-warning">No tenemos acceso a los datos de sesiones y conversión que se refieren a los flujos de compras realizados fuera de las tiendas VTEX. Por eso, los pedidos hechos en los marketplaces no se incluyen en las métricas de Insights.</div>
+>⚠️ No tenemos acceso a los datos de sesiones y conversión que se refieren a los flujos de compras realizados fuera de las tiendas VTEX. Por eso, los pedidos hechos en los marketplaces no se incluyen en las métricas de Insights.
 
 ## Conociendo la interfaz
 
diff --git a/docs/tutorials/es/understanding-competition-of-promotions.md b/docs/tutorials/es/understanding-competition-of-promotions.md
index 89416d15f..c4d4508f1 100644
--- a/docs/tutorials/es/understanding-competition-of-promotions.md
+++ b/docs/tutorials/es/understanding-competition-of-promotions.md
@@ -84,8 +84,7 @@ Por lo tanto, la secuencia de aplicación es:
 
 ![promocao3 ES](https://images.ctfassets.net/alneenqid6w5/1CAcjiuVQECwqcoA288Aey/251351f394db394a008ccdd699e47c6f/promocao3_ES.png)
 
-<div class="alert alert-warning">
-Los pedidos de origen <a href="https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> ((proporcionados por la tienda) y Fulfillment (entregados por la tienda) no permiten la acumulación de promociones, ya que el uso de las mismas en marketplaces VTEX o externos se limita a algunos tipos específicos.</div> 
+>⚠️ Los pedidos de origen [Marketplace](https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406) ((proporcionados por la tienda) y Fulfillment (entregados por la tienda) no permiten la acumulación de promociones, ya que el uso de las mismas en marketplaces VTEX o externos se limita a algunos tipos específicos. 
 
 ## Estrategia de competencia entre promociones
 
@@ -100,8 +99,7 @@ Consulta a continuación las dos estrategias de competencia de promociones:
 - [Competencia por escenario](#competencia-por-escenario)
 - [Competencia por ítem](#competencia-por-item)
 
-<div class="alert alert-info">
-De manera predeterminada, todas las cuentas siguen la estrategia de competencia por escenario. Si el modelo de competencia por ítem se adapta mejor a las necesidades de tu negocio, <a href="https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abre un ticket</a> con nuestro equipo de soporte y solicita el cambio.</div>
+>ℹ️ De manera predeterminada, todas las cuentas siguen la estrategia de competencia por escenario. Si el modelo de competencia por ítem se adapta mejor a las necesidades de tu negocio, [abre un ticket](https://help.vtex.com/es/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) con nuestro equipo de soporte y solicita el cambio.
 
 ### Competencia por escenario
 
diff --git a/docs/tutorials/es/understanding-how-indexation-works.md b/docs/tutorials/es/understanding-how-indexation-works.md
index 394450912..6319ed3ef 100644
--- a/docs/tutorials/es/understanding-how-indexation-works.md
+++ b/docs/tutorials/es/understanding-how-indexation-works.md
@@ -15,10 +15,9 @@ legacySlug: entendiendo-el-funcionamento-de-la-indexacion
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class="alert alert-warning">
-<p>Este tutorial sólo es válido para las tiendas que utilizan la búsqueda del <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>.</p>
-<p>Si su tienda utiliza el <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>, consulte la página <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Historial de indexación</a> para seguir el proceso de indexación.</p>
-</div>
+>⚠️ Este tutorial sólo es válido para las tiendas que utilizan la búsqueda del [CMS Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
+>
+> Si su tienda utiliza el [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG), consulte la página [Historial de indexación](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) para seguir el proceso de indexación.
 
 La indexación es un proceso que prepara los datos generales del SKU, tales como datos de catálogo, de precio y de stock y actualiza la información para servir de base para búsquedas y montajes de las estantes del sitio.
 
diff --git a/docs/tutorials/es/understanding-incomplete-orders.md b/docs/tutorials/es/understanding-incomplete-orders.md
index 29d3738c1..52d45ccdd 100644
--- a/docs/tutorials/es/understanding-incomplete-orders.md
+++ b/docs/tutorials/es/understanding-incomplete-orders.md
@@ -23,9 +23,7 @@ Además, todos los pedidos incompletos no tienen Workflow y ese es un comportami
 
 Como un pedido incompleto fue interrumpido, activar un Workflow para una situación inactiva no sería funcional. 
 
-<div class="alert alert-danger"> 
-En el caso de un pedido incompleto, recomendamos que se vuelva a hacer el pedido en la tienda. Los pedidos incompletos sirven únicamente como registro, por lo que la plataforma no realizará nuevas solicitudes para este tipo de pedidos. Por lo tanto, si un pedido está incompleto y el cliente quiere realizarlo, debe crear un nuevo pedido con los mismos ítems.
-</div>
+>❗ En el caso de un pedido incompleto, recomendamos que se vuelva a hacer el pedido en la tienda. Los pedidos incompletos sirven únicamente como registro, por lo que la plataforma no realizará nuevas solicitudes para este tipo de pedidos. Por lo tanto, si un pedido está incompleto y el cliente quiere realizarlo, debe crear un nuevo pedido con los mismos ítems.
 
 De este modo, el proceso continúa como de costumbre.
 
diff --git a/docs/tutorials/es/understanding-the-conversation-tracker.md b/docs/tutorials/es/understanding-the-conversation-tracker.md
index b31e9a2bb..dd23f16f4 100644
--- a/docs/tutorials/es/understanding-the-conversation-tracker.md
+++ b/docs/tutorials/es/understanding-the-conversation-tracker.md
@@ -24,9 +24,7 @@ Conversation Tracker puede tener dos configuraciones:
 - **Compleja** - crea un alias (correo electrónico alternativo) de forma ilegible, evitando así la identificación del correo electrónico por sistemas externos, también vincula cualquier correo electrónico enviado a esta dirección a la línea de tiempo del pedido. Normalmente, la tienda con esta configuración presenta el alias de la siguiente forma: `ff2e6348a53a4d449af92be2a1011328@ct.vtex.com.br`
 - **Simple** - crea un alias (correo electrónico alternativo) menos complejo para el correo electrónico del usuario comprador, esto hace que el correo electrónico continúe legible en la UI del OMS y cuando se visualice en el JSON del pedido. Otro punto importante es que la dirección del remitente (tienda) también está enmascarada de la misma manera que el correo electrónico del usuario en el JSON. Esto es necesario para que el sistema pueda vincular los correos electrónicos de esta compra a la línea de tiempo del pedido. Por lo general, la tienda con esta configuración mostrará el alias de la siguiente forma:`juanvaldez@vtex.com.br-207700027841b.ct.vtex.com.br`
 
-<div class="alert alert-info">
-Todas las tiendas vienen con la configuración <strong>Compleja</strong> por default.
-</div>
+>ℹ️ Todas las tiendas vienen con la configuración **Compleja** por default.
 
 Conversation Tracker ofrece diversas otras ventajas, principalmente en cuestión de seguridad:
 
diff --git a/docs/tutorials/es/understanding-the-cubic-weight-factor.md b/docs/tutorials/es/understanding-the-cubic-weight-factor.md
index d1687b7b6..6f7f226ca 100644
--- a/docs/tutorials/es/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/es/understanding-the-cubic-weight-factor.md
@@ -34,9 +34,7 @@ Es el coeficiente resultante de la relación entre peso y volumen más adecuada
 
 El cálculo del peso volumétrico se realiza efectuando la multiplicación de la Longitud x Anchura X Altura y división por el factor volumétrico proporcionado por la trasportadora.
 
-<div class="alert alert-warning">
-Al calcular el factor de peso volumétrico, la plataforma VTEX no utiliza unidades de medida y los números generados son absolutos. Por lo tanto, los números y medidas que tengas en cuenta serán los del resultado final. Vale la pena señalar que la unidad de medida utilizada en su cálculo debe ser la misma utilizada por la transportadora.
-</div>
+>⚠️ Al calcular el factor de peso volumétrico, la plataforma VTEX no utiliza unidades de medida y los números generados son absolutos. Por lo tanto, los números y medidas que tengas en cuenta serán los del resultado final. Vale la pena señalar que la unidad de medida utilizada en su cálculo debe ser la misma utilizada por la transportadora.
 
 Vea el ejemplo siguiente:
 
diff --git a/docs/tutorials/es/understanding-the-updating-of-the-xml.md b/docs/tutorials/es/understanding-the-updating-of-the-xml.md
index ff3f4739f..22c75d64f 100644
--- a/docs/tutorials/es/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/es/understanding-the-updating-of-the-xml.md
@@ -23,4 +23,4 @@ Es posible visualizar la última fecha de actualización del XML. Esa informaci
 
 ![](https://images.contentful.com/alneenqid6w5/5YwPKBeb5ekeGEu6gcQgUG/585efc76d9e56c5ed434d4faa6e526f0/xml.png)
 
-<div class="alert alert-info">Caso la opción "Exhibir los SKUs sin saldo disponible (agotados) en Stock entre los resultados" no esté señalada, los productos/SKUs que estén agotados <strong>no</strong> surgirán en el XML. Productos inactivos también <strong>no</strong> surgen en el XML.</div>
+>ℹ️ Caso la opción "Exhibir los SKUs sin saldo disponible (agotados) en Stock entre los resultados" no esté señalada, los productos/SKUs que estén agotados **no** surgirán en el XML. Productos inactivos también **no** surgen en el XML.
diff --git a/docs/tutorials/es/understanding-vtex-matcher-scoring.md b/docs/tutorials/es/understanding-vtex-matcher-scoring.md
index 87c82a634..a0c116f92 100644
--- a/docs/tutorials/es/understanding-vtex-matcher-scoring.md
+++ b/docs/tutorials/es/understanding-vtex-matcher-scoring.md
@@ -43,9 +43,7 @@ La puntuación final determina el status del producto, desde *Aprobado, Negado*
 ## Catalogación
 En la siguiente tabla se puede ver cómo cada puntuación genera un status y una acción correspondiente.
 
-<div class="alert alert-info">
-La puntuación máxima de VTEX Matcher para la catalogación automática es 95. Las puntuaciones superiores a 95 requieren catalogación manual.
-</div>
+>ℹ️ La puntuación máxima de VTEX Matcher para la catalogación automática es 95. Las puntuaciones superiores a 95 requieren catalogación manual.
 
 | Puntuación           | Status    | Escenario                                                                                                                                                        | Acción                                                                                                                                                                                                                                                                                                                    |
 |----------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
diff --git a/docs/tutorials/es/understanding-vtexs-email-capture-system.md b/docs/tutorials/es/understanding-vtexs-email-capture-system.md
index 09c86a001..c49a1a0ce 100644
--- a/docs/tutorials/es/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/es/understanding-vtexs-email-capture-system.md
@@ -39,17 +39,13 @@ Para una mejor comprensión, presentaremos un escenario (dividido en 3 pasos), d
 |------------------|------------------|
 | Haga clic en `Ir para la Entrega`. | Checkout solicita a RC.JS que transfiera la dirección de correo electrónico y la información del carrito a Master Data (a través del Profile System). |
 
-<div class="alert alert-warning">
-Para que se pueda utilizar la función <a href="https://help.vtex.com/es/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#">carrito abandonado</a>, es necesario que el usuario haya rellenado los siguientes datos: e-mail, nombre, apellidos y CPF. La falta de alguno de estos datos, imposibilita la utilización del carrito abandonado.
-</div>
+>⚠️ Para que se pueda utilizar la función [carrito abandonado](https://help.vtex.com/es/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#), es necesario que el usuario haya rellenado los siguientes datos: e-mail, nombre, apellidos y CPF. La falta de alguno de estos datos, imposibilita la utilización del carrito abandonado.
 
 | __Usuario__ | __Plataforma VTEX__ |
 |------------------|------------------|
 | Rellena los datos de envío y pago. | The Checkout orderForm becomes an order and is transmitted to the VTEX OMS. El orderForm de Checkout se convierte en un pedido y se transmite al VTEX OMS. La información completa del usuario (nombre, apellido, correo electrónico, carrito y toda la información adicional) se transmite a Master Data. La captura de correo electrónico puede tardar hasta 46 minutos en reflejarse correctamente en CRM. |
 
-<div class="alert alert-info">
-Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
-</div>
+>ℹ️ Cada módulo VTEX es responsable de solicitar RC.JS para transmitir los datos capturados en la sesión. RC.JS está destinado a actuar como un "mensajero" de información.
 
 ![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
 
diff --git a/docs/tutorials/es/updating-prices-in-marketplaces.md b/docs/tutorials/es/updating-prices-in-marketplaces.md
index 2b47a4740..b1afdec68 100644
--- a/docs/tutorials/es/updating-prices-in-marketplaces.md
+++ b/docs/tutorials/es/updating-prices-in-marketplaces.md
@@ -20,7 +20,5 @@ La actualización de precios en los marketplaces depende de dos factores:
 - Registro de precios para los productos en la [tabla de precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) asociada con la política comercial utilizada en la integración con el marketplace.
 - [Indexación del producto](https://help.vtex.com/es/tutorial/understanding-how-indexation-works--tutorials_256) después del registro del nuevo precio. 
 
-<div class="alert alert-warning">
-  <p>Solo los <a href="https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj">precios fijos</a> se utilizan en nuestras integraciones nativas con marketplaces. Los otros escenarios previstos en la <a href="https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx">arquitectura del sistema de precios</a> solo están disponibles para marketplaces VTEX-VTEX.</p>
-</div>
+>⚠️ Solo los [precios fijos](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj) se utilizan en nuestras integraciones nativas con marketplaces. Los otros escenarios previstos en la [arquitectura del sistema de precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) solo están disponibles para marketplaces VTEX-VTEX.
 
diff --git a/docs/tutorials/es/url-mapping-301-redirect.md b/docs/tutorials/es/url-mapping-301-redirect.md
index 2c27a9c9e..1842327ba 100644
--- a/docs/tutorials/es/url-mapping-301-redirect.md
+++ b/docs/tutorials/es/url-mapping-301-redirect.md
@@ -15,9 +15,7 @@ legacySlug: mapeo-de-url-redireccion-301
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-warning">
-<p>Este tutorial es para tiendas en el CMS legado. Para otras tiendas, esta configuración se realiza a través de <a href="https://help.vtex.com/es/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Páginas</a>. Acceda a la documentación <a href="https://help.vtex.com/es/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Gestión de redirecciones de URL</a> para obtener más información.</p>
-</div>
+>⚠️ Este tutorial es para tiendas en el CMS legado. Para otras tiendas, esta configuración se realiza a través de [Páginas](https://help.vtex.com/es/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word). Acceda a la documentación [Gestión de redirecciones de URL](https://help.vtex.com/es/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word) para obtener más información.
 
 Los mapeos de URL se utilizan para redirigir URL específicas a otras URL. Este recurso es muy útil cuando la tienda ya tiene URL indexadas en los buscadores y se quiere redirigirlas a otras más atractivas, manteniendo el SEO y evitando errores de indexación.
 
@@ -45,9 +43,7 @@ Hay dos maneras de añadir y cambiar un Mapeo de URL:
 - **End date:** fecha y hora en que se dejará de considerar el mapeo.
 - **Active:** opción para determinar si el mapeo está activo o inactivo.
 
-<div class="alert alert-info"> 
-  <p>Para crear un mapeo para la home (directorio raíz), rellene el campo <b>Url to</b> con una barra <code>/</code>.</p>
-</div>
+>ℹ️ Para crear un mapeo para la home (directorio raíz), rellene el campo **Url to** con una barra `/`.
 
 ## Importación por plantilla
 
diff --git a/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index be09dedba..e18769a24 100644
--- a/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/es/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -33,8 +33,7 @@ Por ejemplo, un usuario con un enlace de campaña específico podría tener una
 
 Además de obtener información de sesión para un dispositivo que esté navegando por la infraestructura de VTEX, Session Manager le permite almacenar *datos personalizados* en aquella sesión. Esta información es fácilmente recuperable y le permite evitar hacer algo como configurar una cookie para registrar información específica sobre un usuario.
 
-<div class="alert alert-info">Session Manager también fue construido para permitir a los desarrolladores crear sus propios triggers y lógica de procesamiento. Todavía estamos finalizando el desarrollo de esta solución expandible, pero en el futuro usted debería ser capaz de configurar la ejecución condicional de código personalizado, de acuerdo con la presencia de valores específicos de parámetros en los datos de sesión de un usuario.
-</div>
+>ℹ️ Session Manager también fue construido para permitir a los desarrolladores crear sus propios triggers y lógica de procesamiento. Todavía estamos finalizando el desarrollo de esta solución expandible, pero en el futuro usted debería ser capaz de configurar la ejecución condicional de código personalizado, de acuerdo con la presencia de valores específicos de parámetros en los datos de sesión de un usuario.
 
 ## Agregar datos de sesión: llamadas create y transform
 Estrictamente hablando, Session Manager es un sistema backend de API que almacena y procesa datos de sesión contenidos en objetos JSON. Cada cuenta VTEX tiene configuraciones que indican qué apps instaladas tienen una dependencia de sesión y cómo estas pretenden procesar esta información.
@@ -53,7 +52,7 @@ Transforms frecuentemente disparan otros transforms, repitiendo hasta que ningun
 6. App C monitoreaba el parámetro de sesión Z, lo que disparó el Transform 3
 7. Transform 3 no tuvo efectos colaterales en parámetros monitoreados por apps, por lo tanto, el ciclo se cerró y la sesión se guardó hasta que otros cambios sean hechos. 
 
-<div class="alert alert-info">Llamadas transform se realizan a todas las apps simultáneamente para optimizar el desempeño. Es por esto que la App C fue afectada por el Transform 2 y por el Transform 3 - no tenía forma de saber que el resultado de Transform 2 en la  App B llevaría a la necesidad de cambios adicionales en sus parámetros de salida.</div>
+>ℹ️ Llamadas transform se realizan a todas las apps simultáneamente para optimizar el desempeño. Es por esto que la App C fue afectada por el Transform 2 y por el Transform 3 - no tenía forma de saber que el resultado de Transform 2 en la  App B llevaría a la necesidad de cambios adicionales en sus parámetros de salida.
 
 Cuando se crea una nueva sesión, se ejecuta una versión más sencilla de este ciclo, que llamamos **llamada create**. Todas las apps que tengan la configuración `RunOnCreate: true` serán notificadas para que se ejecuten simultáneamente con una entrada vacía. Si estas apps modifican cualquier parámetro monitoreado por otras apps, esto dispara un ciclo de transform que se ejecutará hasta que se resuelvan las dependencias de entrada.
 
diff --git a/docs/tutorials/es/using-tools-html.md b/docs/tutorials/es/using-tools-html.md
index 9baba8728..f682f12ad 100644
--- a/docs/tutorials/es/using-tools-html.md
+++ b/docs/tutorials/es/using-tools-html.md
@@ -15,4 +15,4 @@ legacySlug:
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/vtex-ad-network-beta.md b/docs/tutorials/es/vtex-ad-network-beta.md
index 600e226b1..bf58ce5d0 100644
--- a/docs/tutorials/es/vtex-ad-network-beta.md
+++ b/docs/tutorials/es/vtex-ad-network-beta.md
@@ -72,9 +72,7 @@ Este proceso de priorización se desarrolla en tres etapas:
 
 Una vez determinados los anuncios que se muestran en la página, se determina el valor de las ofertas. La oferta ganadora de la subasta tendrá el valor final de la segunda mayor oferta más USD 0.01.
 
-<div class="alert alert-danger">
-Puede ocurrir que no se seleccione ningún anuncio con el proceso de priorización si no hay productos promocionados que se ajusten al contexto de navegación, a la cobertura de la tienda o que no tienen presupuesto disponible.
-</div>
+>❗ Puede ocurrir que no se seleccione ningún anuncio con el proceso de priorización si no hay productos promocionados que se ajusten al contexto de navegación, a la cobertura de la tienda o que no tienen presupuesto disponible.
 
 ### Nivel de calidad
 
@@ -109,9 +107,7 @@ Consulta a continuación cómo puedes formar parte de **VTEX Ad Network** ya sea
 
 ### Retailers
 
-<div class="alert alert-warning">
-Por el momento, solamente tiendas desarrolladas con <a href="https://help.vtex.com/es/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> pueden ofrecer espacios para anuncios.
-</div>
+>⚠️ Por el momento, solamente tiendas desarrolladas con [Store Framework](https://help.vtex.com/es/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) pueden ofrecer espacios para anuncios.
 
 Para disponibilizar espacios para anuncios en tu tienda, debe ponerse en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar la instalación de la aplicación VTEX Ad Network para tiendas en su cuenta VTEX.
 
diff --git a/docs/tutorials/es/vtex-admin-start-here.md b/docs/tutorials/es/vtex-admin-start-here.md
index 5bfb9aca9..5e903dee0 100644
--- a/docs/tutorials/es/vtex-admin-start-here.md
+++ b/docs/tutorials/es/vtex-admin-start-here.md
@@ -52,9 +52,7 @@ Consulta nuestros artículos sobre la vista general de cada menú del Admin VTEX
 - [Configuración del usuario](https://help.vtex.com/es/v4/docs/visao-geral-configuracoes-usuario--1qYAvOTZBVYMosJ7tQm3Ry)  
 - [Facturas](https://help.vtex.com/es/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC)  
 
-<div class="alert alert-info">
-También puedes utilizar la barra de búsqueda en la parte superior del Admin VTEX para encontrar páginas específicas del menú lateral. 
-</div>
+>ℹ️ También puedes utilizar la barra de búsqueda en la parte superior del Admin VTEX para encontrar páginas específicas del menú lateral.
 
 ### Centro de información
 
diff --git a/docs/tutorials/es/vtex-agreement.md b/docs/tutorials/es/vtex-agreement.md
index c7f738a59..d832c0d80 100644
--- a/docs/tutorials/es/vtex-agreement.md
+++ b/docs/tutorials/es/vtex-agreement.md
@@ -29,7 +29,5 @@ El Master Agreement aplicable está disponible en la sección **Política de pri
 
 También puedes encontrar los Master Agreements más actualizados, es decir, los aplicables a nuevos clientes y partners, en la página [Contratos VTEX](https://vtex.com/mx-es/privacy-and-agreements/agreements/).
 
-<div class="alert alert-info">
-Si el <b>MSA, MPA, Anexo 1</b> o los <b>Términos y condiciones específicos de la asociación</b> firmados con VTEX incluyen información que difiere de lo descrito en esta documentación, prioriza tu documento firmado con VTEX.
-</div>
+>ℹ️ Si el **MSA, MPA, Anexo 1** o los **Términos y condiciones específicos de la asociación** firmados con VTEX incluyen información que difiere de lo descrito en esta documentación, prioriza tu documento firmado con VTEX.
 
diff --git a/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
index 7db8ee7c2..d167a13b1 100644
--- a/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
+++ b/docs/tutorials/es/vtex-dashboard-guide-for-black-week-faq.md
@@ -47,9 +47,9 @@ Para configurar la referencia sigue los pasos a continuación:
 3. Define una fecha.
 4. Haz clic en **`Aplicar`.**  
 
-<div class="alert alert-warning">
-Una comparación valiosa durante la Black Week se realiza al contrastar datos con la misma fecha del año anterior. En la configuración de referencia, se recomienda establecer preferiblemente una fecha entre el 21/11/2022 y el 27/11/2022, preferentemente los mismos días de la semana. <br>Esta opción está dirigida a clientes que utilizaron el Admin VTEX durante ese periodo el año pasado.</br>
-</div>  
+>⚠️ Una comparación valiosa durante la Black Week se realiza al contrastar datos con la misma fecha del año anterior. En la configuración de referencia, se recomienda establecer preferiblemente una fecha entre el 21/11/2022 y el 27/11/2022, preferentemente los mismos días de la semana. 
+>
+> Esta opción está dirigida a clientes que utilizaron el Admin VTEX durante ese periodo el año pasado.</br>  
 
 ![referencia-es](https://images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/4466f9301343f19f0ff79d89f5c44821/referencia-es.png)  
 
@@ -72,9 +72,7 @@ Para consultar los productos más vendidos, en la sección **Métricas**  haz cl
 
 ![mas-vendidos-es](https://images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/22b06efc2dd15dded404a1c4b1f23f2c/mas-vendidos-es.png)   
 
-<div class="alert alert-danger">
-Para análisis o seguimientos de periodos más extensos, recomendamos el uso de nuestro dashboard Desempeño de ventas, que se detalla en la siguiente pregunta.
-</div>
+>❗ Para análisis o seguimientos de periodos más extensos, recomendamos el uso de nuestro dashboard Desempeño de ventas, que se detalla en la siguiente pregunta.
 
 ## ¿Cómo puedo monitorear los datos de mi tienda online más allá del día de hoy?  
 
@@ -139,9 +137,9 @@ Hay varias razones por las cuales las métricas de la Vista general en tiempo re
 
 Para obtener una visión completa de las métricas combinadas de todas las tiendas, te recomendamos acceder al dashboard Desempeño de ventas. Este dashboard ofrece datos agregados con una tasa de actualización de aproximadamente 90 minutos.  
 
-<div class="alert alert-danger">
-Si tu tienda online opera con más de una moneda puedes consultar los pedidos en el <b>dashboard Vista general;</b> el total de los mismos se presentan sumados en la moneda más utilizada en tus ventas. <br>Para comparar con la pantalla <b>Pedidos,</b> debes sumar el total de pedidos en todas las monedas.</br>
-</div>    
+>❗ Si tu tienda online opera con más de una moneda puedes consultar los pedidos en el **dashboard Vista general;** el total de los mismos se presentan sumados en la moneda más utilizada en tus ventas. 
+>
+> Para comparar con la pantalla **Pedidos,** debes sumar el total de pedidos en todas las monedas.</br>    
 
 ![todos-los-pedidos-es](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/7207f5239991e648867ab5b201629a8b/todos-los-pedidos-es.png)
 
diff --git a/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
index d32c24455..774b94b44 100644
--- a/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/es/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -15,17 +15,13 @@ legacySlug: vtex-intelligent-search-configuracion-multidioma-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-<p>Esta funcionalidad está en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad está en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de dudas, contacte a [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) es una aplicación de búsqueda inteligente para ecommerce que está disponible para tiendas desarrolladas con [VTEX IO](https://vtex.com/es-es/store-framework/). Para instalar y configurar VTEX Intelligent Search en su tienda, [lea nuestro artículo Search](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search). La herramienta muestra sugerencias de búsqueda y productos que pueden ser del interés del usuario, además corrige errores de ortografía e identifica palabras que no están en el registro del producto.
 
 VTEX Intelligent Search Multidioma expande las funcionalidades de [Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) y ofrece una experiencia de búsqueda multidioma, ideal para las tiendas que realizan operaciones en diversos países. Este recurso facilita la adaptación de la tienda a múltiples idiomas y garantiza la búsqueda en todos los idiomas registrados.
 
-<div class="alert alert-info">
-<p> En caso de que desee expandir su ecommerce a otro idioma, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a> para que el equipo de VTEX realice las configuraciones necesarias.</p>
-</div>
+>ℹ️ En caso de que desee expandir su ecommerce a otro idioma, contacte a [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests) para que el equipo de VTEX realice las configuraciones necesarias.
 
 Cuando tiene VTEX Intelligent Search Multidioma instalada, la información del Catálogo de su tienda es traducida por la aplicación [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization). Para eso, es importante registrar la traducción de los siguientes campos: Nombre, Marca (solo si hay una traducción registrada por el administrador de la tienda), Descripción, Categorías, CategoryTrees, metadata, metadataKeyword, Especificaciones, SKU {name}. Lea la guía para desarrolladores [Traducción del contenido del catálogo](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) para obtener más información.
 
@@ -50,9 +46,7 @@ Para saber más sobre los campos, lea nuestro artículo sobre [cómo configurar
 ### Sinónimos
 Hay dos formas de configurar Sinónimos en una tienda multidioma en el Admin: completar un formulario o importar un archivo .csv.
 
-<div class="alert alert-warning">
-<p> Las configuraciones creadas o alteradas en <b>Sinónimos</b> pueden tardar hasta 2 horas en aplicarse en la tienda.</p>
-</div>
+>⚠️ Las configuraciones creadas o alteradas en **Sinónimos** pueden tardar hasta 2 horas en aplicarse en la tienda.
 
 #### Crear Sinónimos vía formulario
 Cuando tiene VTEX Intelligent Search Multidioma instalada,  la página de edición o creación de Sinónimos — que se accede en el Admin VTEX en __Storefront__ > __Intelligent Search__ > __Sinónimos__ — exhibe el campo adicional __Regiones__, que permite elegir los idiomas a los que se aplicará los sinónimos registrados, como se muestra en la siguiente imagen. Haga clic en los idiomas deseados para seleccionarlos.  
@@ -71,9 +65,7 @@ En caso de que prefiera importar Sinónimos para idiomas específicos mediante a
 - __Bidireccional__: `<Términos separados por coma>;<status>;<locales separados por coma>`.
     - Ejemplo: `tv,smart tv;true;en-GB`: al buscar cualquiera de estos términos en la tienda en el idioma inglés (`locale en-GB`), se mostrará cualquier producto que contenga uno de esos términos en los resultados de búsqueda.
 
-<div class="alert alert-warning">
-<p> Si el archivo .csv importado no contiene la columna `locale`, el sinónimo será válido para todos los idiomas disponibles en la tienda. </p>
-</div>
+>⚠️ Si el archivo .csv importado no contiene la columna `locale`, el sinónimo será válido para todos los idiomas disponibles en la tienda.
 
 Para saber más sobre la importación de una plantilla de Sinónimos, lea nuestro artículo sobre [cómo configurar Sinónimos en VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
index 6fc3f866b..b0b9bf312 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
@@ -380,9 +380,7 @@ Los límites de cambios de cantidad y precio de ítems en el pedido te permiten
 
 #### Tags de hojas de trabajo
 
-<div class="alert alert-warning">
-Solo debes hacer clic sobre el campo para crearlo o eliminarlo del listado.
-</div>
+>⚠️ Solo debes hacer clic sobre el campo para crearlo o eliminarlo del listado.
 
 Las tags ayudan como identificadores de las hojas de trabajo para poder realizar configuraciones, filtros o asignaciones  necesarias dentro del sistema.
 
@@ -403,9 +401,7 @@ Puedes seleccionar los tres tipos de configuraciones para la tienda.
 Si quieres eliminar un tipo puedes hacerlo dentro del campo haciendo clic sobre la X que lo acompaña.
 </div>
 
-<div class="alert alert-danger">
-EAN dinámico es un código que se genera con el peso del producto para calcular el precio.
-</div>
+>❗ EAN dinámico es un código que se genera con el peso del producto para calcular el precio.
 
 ### Configuración de categorías
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-mobile.md b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
index d0f0be66c..e593b799e 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
@@ -48,9 +48,7 @@ Al seleccionar esta hoja de trabajo para su preparación, la aplicación indicar
 
 A continuación, la aplicación dará soporte para el empaque de cada pedido con sus respectivos ítems.
 
-<div class="alert alert-warning">
-Las hojas de trabajo solo se aplican a las etapas de alistamiento y empaque de los pedidos. Los envíos de cada pedido deben realizarse por separado.
-</div>
+>⚠️ Las hojas de trabajo solo se aplican a las etapas de alistamiento y empaque de los pedidos. Los envíos de cada pedido deben realizarse por separado.
 
 ## Crear hoja de trabajo
 
@@ -116,9 +114,7 @@ Una vez alistados, los productos aparecen en la pestaña __Resumen__.
 
 Hay situaciones en las que puede ser necesario rechazar productos debido a la configuración de la tienda y a la disponibilidad de ítems en stock. 
 
-<div class="alert alert-warning">
-La opción Rechazar ítems puede no estar disponible. En caso de duda, ponte en contacto con la gerencia de la tienda.
-</div>
+>⚠️ La opción Rechazar ítems puede no estar disponible. En caso de duda, ponte en contacto con la gerencia de la tienda.
 
 Para rechazar un producto de la hoja de trabajo sigue los pasos que se indican a continuación:
 
@@ -134,17 +130,13 @@ Para descartar todos los productos de la hoja de trabajo de una sola vez, sigue
 2. Haz clic en la opción **Listo para empaque.** 
 3. Haz clic en **Descartar todos los ítems disponibles.**
 
-<div class="alert alert-danger">
-Si se descartan todos los ítems de un pedido, el pedido se completará automáticamente.
-</div>
+>❗ Si se descartan todos los ítems de un pedido, el pedido se completará automáticamente.
 
 ## Reemplazar ítems
 
 Otra opción para ítems no disponibles es sustituirlos por otros, dependiendo de la configuración de la tienda y de la disponibilidad de los ítems en stock.
 
-<div class="alert alert-warning">
-La opción Rechazar ítems puede no estar disponible. En caso de duda, ponte en contacto con la gerencia de la tienda.
-</div>
+>⚠️ La opción Rechazar ítems puede no estar disponible. En caso de duda, ponte en contacto con la gerencia de la tienda.
 
 Para reemplazar ítems de la hoja de trabajo sigue los pasos que se indican a continuación:
 
@@ -178,9 +170,7 @@ Sigue los pasos que se indican a continuación para empacar ítems:
 
 1. En __Empaque__, haz clic en el pedido que deseas empacar. 
 2. Haz clic en el botón <i class="fas fa-plus"></i> del producto que deseas agregar al paquete o haz clic en <i class="fas fa-box"></i> para agregar todos los productos a la vez.
-<div class="alert alert-warning">
-Si optas por empacar todos los ítems del pedido, los productos que aún no se hayan empacado se registrarán en un único nuevo empaque.
-</div>
+>⚠️ Si optas por empacar todos los ítems del pedido, los productos que aún no se hayan empacado se registrarán en un único nuevo empaque.
 5. Selecciona un tipo de paquete ya registrado o agrega uno nuevo haciendo clic en `+ Crear paquete`. 
 6. Selecciona el tipo de paquete que deseas agregar.
 7. Selecciona cuántas unidades del producto deseas agregar a ese paquete.
@@ -204,9 +194,7 @@ A continuación, se finalizará el pedido en la aplicación. Dependiendo de la c
 
 La fase de envío permite crear servicios de envío para los pedidos alistados y empacados.
 
-<div class="alert alert-warning">
-El envío es una etapa opcional de la aplicación, dependiendo de tu operación y de la configuración realizada por el administrador de la tienda.
-</div>
+>⚠️ El envío es una etapa opcional de la aplicación, dependiendo de tu operación y de la configuración realizada por el administrador de la tienda.
 
 Para enviar paquetes desde la aplicación Pick and Pack, sigue los pasos que se indican a continuación:
 
diff --git a/docs/tutorials/es/vtex-shield.md b/docs/tutorials/es/vtex-shield.md
index 1ce579ee8..494a8725a 100644
--- a/docs/tutorials/es/vtex-shield.md
+++ b/docs/tutorials/es/vtex-shield.md
@@ -15,9 +15,7 @@ legacySlug: vtex-shield
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 VTEX Shield ofrece capas de protección adicionales y personalizables para tiendas que priorizan la resiliencia de la plataforma, además de los estándares de seguridad garantizados por las certificaciones y [prácticas de seguridad](https://vtex.com/mx-es/security/security-practices/) existentes en VTEX.
 
@@ -52,9 +50,7 @@ Solo las tiendas con VTEX Shield que opten por este recurso pueden solicitar la
 
 ## Data Protection Plus
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad se encuentra en fase beta cerrada y está disponible solo en algunas regiones. Si tienes alguna duda, ponte en contacto con <a href="https://help.vtex.com/es/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">nuestro soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en fase beta cerrada y está disponible solo en algunas regiones. Si tienes alguna duda, ponte en contacto con [nuestro soporte](https://help.vtex.com/es/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
 [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) es una arquitectura de datos que proporciona una capa adicional de protección para datos personales. En esta arquitectura, todos los datos de información de identificación personal (PII, Personally Identifiable Information) se almacenan en [Profile System](https://developers.vtex.com/docs/guides/profile-system), un servicio desarrollado específicamente para procesar PII siguiendo un [conjunto de reglas y procesos](https://developers.vtex.com/docs/guides/pii-data-architecture-specifications) apropiado para este objetivo.
 
diff --git a/docs/tutorials/es/vtex-shipping-network-dashboard.md b/docs/tutorials/es/vtex-shipping-network-dashboard.md
index da1f4fa64..afd6cec9e 100644
--- a/docs/tutorials/es/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/es/vtex-shipping-network-dashboard.md
@@ -15,9 +15,7 @@ legacySlug: panel-vtex-log
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-warning">
-Atención: Esta funcionalidad se encuentra en fase beta abierta
-</div>
+>⚠️ Atención: Esta funcionalidad se encuentra en fase beta abierta
 
 VTEX Shipping Network utiliza los datos de rastreo de los pedidos directamente de las transportadoras, manteniéndolo a usted y a su cliente actualizados sobre el status de cada entrega. Los **paneles de VTEX Shipping Network** gestionan los datos obtenidos de VTEX Shipping Network, para que usted pueda extraer información inteligente para la gestión de su logística. 
 
diff --git a/docs/tutorials/es/vtex-status-page.md b/docs/tutorials/es/vtex-status-page.md
index bba43b9f2..8cf93352a 100644
--- a/docs/tutorials/es/vtex-status-page.md
+++ b/docs/tutorials/es/vtex-status-page.md
@@ -125,9 +125,7 @@ Para ver los eventos ocurridos en un día específico, pasa el mouse sobre la fe
 
 ![statuspage-8](https://images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/0fff21b4393a61f149857c0bb353ef4a/statuspage-8.png)
 
-<div class="alert alert-warning">
-  <p>Si un mantenimiento programado dura más de un día, solo se marcará la fecha de inicio en el calendario. Debes abrir el <a href="#registro-de-mantenimiento-programado">registro de mantenimiento</a> para ver la fecha de inicio y la fecha de fin.</p>
-</div>
+>⚠️ Si un mantenimiento programado dura más de un día, solo se marcará la fecha de inicio en el calendario. Debes abrir el [registro de mantenimiento](#registro-de-mantenimiento-programado) para ver la fecha de inicio y la fecha de fin.
 
 A continueación, describimos la información disponible en el registro del incidente y en el registro de mantenimiento programado.
 
diff --git a/docs/tutorials/es/vtex-suiteshare.md b/docs/tutorials/es/vtex-suiteshare.md
index 33953c952..ee0fba225 100644
--- a/docs/tutorials/es/vtex-suiteshare.md
+++ b/docs/tutorials/es/vtex-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: vtex-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/vtex-tracking-holidays.md b/docs/tutorials/es/vtex-tracking-holidays.md
index f22b6f2de..9ba2d6def 100644
--- a/docs/tutorials/es/vtex-tracking-holidays.md
+++ b/docs/tutorials/es/vtex-tracking-holidays.md
@@ -17,9 +17,7 @@ subcategory: 7yiFRk9TGfMNeyhT83UljP
 
 IN PROGRESS...
 
-<div class="alert alert-info">
-El registro de «Feriados» solo está vinculado a la funcionalidad de programación de entrega que únicamente está disponible para los usuarios de VTEX Tracking con integración de sistemas. 
-</div>
+>ℹ️ El registro de «Feriados» solo está vinculado a la funcionalidad de programación de entrega que únicamente está disponible para los usuarios de VTEX Tracking con integración de sistemas.
 
 Los clientes reciben una comunicación por *email* o SMS con la predicción de entrega de su pedido. Si el cliente sabe de antemano que no estará disponible para recibir su paquete en el periodo indicado, puede reprogramar la entrega para otra fecha y periodo.
 
diff --git a/docs/tutorials/es/warehouse.md b/docs/tutorials/es/warehouse.md
index 6fa067952..bc7b0e58e 100644
--- a/docs/tutorials/es/warehouse.md
+++ b/docs/tutorials/es/warehouse.md
@@ -22,35 +22,34 @@ Es importante prestar atención a la etapa logística del almacén y al modo en
 
 ![EstrategiaEnvio_ES](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/ed9784e5cbc67a42358ad4f37c3baa00/Frame_2__2_.svg)
 
-<div class="alert alert-info">
-La transportadora que llevará a cabo la entrega de un determinado pedido es definida por la <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">política de envío</a>. Para que una transportadora sea elegida para efectuar la entrega del pedido, es necesario que la política de envío de esa transportadora cumpla con las condiciones necesarias para la entrega del pedido. La política de envío está vinculada al almacén por el muelle.
-</div>
+>ℹ️ La transportadora que llevará a cabo la entrega de un determinado pedido es definida por la [política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140). Para que una transportadora sea elegida para efectuar la entrega del pedido, es necesario que la política de envío de esa transportadora cumpla con las condiciones necesarias para la entrega del pedido. La política de envío está vinculada al almacén por el muelle.
 
 En la plataforma VTEX, es posible registrar el nombre del almacén, añadir ítems al almacén, [configurar los muelles](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW) a los que se enviarán los productos, configurar cuánto tiempo se tarda en preparar el pedido antes de enviarlo al muelle y el valor cobrado por esa manipulación. 
 
 Después de añadir un almacén, puede añadir los productos disponibles en él. Puede tener varios almacenes y añadir ítems específicos a cada uno de ellos, esto se reflejará en su configuración logística. 
 
-<div class="alert alert-info">
-Para añadir ítems a su almacén, los productos deben estar previamente registrados en el <a href="https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catálogo</a>. Con ello, es posible asociarlos al almacén mediante la <a href="https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139"> gestión del stock</a>. 
-<div>
-
-La disponibilidad de los productos en su tienda está dada por los productos registrados en los diferentes almacenes. Esto significa que para el cliente final los ítems que están disponibles durante la navegación en la tienda son ítems de todos los almacenes. Así, existe la posibilidad de contar con productos de diferentes almacenes de su tienda en una misma compra. Para controlar el movimiento de los almacenes y la disponibilidad de los ítems en su tienda, acceda a [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
-
-Conozca más sobre cómo gestionar los componentes logísticos en la plataforma VTEX: 
-
-* Para saber cómo registrar, modificar y hacer un seguimiento de los almacenes, consulte el artículo [Gestión del almacén](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137).
-* Para hacer un seguimiento y gestionar los ítems del almacén, consulte [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
-* Para configurar y gestionar la relación entre los almacenes y la retirada de pedidos, consulte [Gestión de muelles](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW).
-
-  <div class="alert alert-warning">
-Como el almacén forma parte del sistema logístico de su tienda, le sugerimos que registre los módulos relacionados con la operación logística en el siguiente orden:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
-</a></li>
-  <li><a href="https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj">Muelle;</a></li>
-<li>Almacén.</li>
- </ol>
-</body>
-</div>
+>ℹ️ Para añadir ítems a su almacén, los productos deben estar previamente registrados en el [catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR). Con ello, es posible asociarlos al almacén mediante la [ gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139). 
+> <div>
+>
+> La disponibilidad de los productos en su tienda está dada por los productos registrados en los diferentes almacenes. Esto significa que para el cliente final los ítems que están disponibles durante la navegación en la tienda son ítems de todos los almacenes. Así, existe la posibilidad de contar con productos de diferentes almacenes de su tienda en una misma compra. Para controlar el movimiento de los almacenes y la disponibilidad de los ítems en su tienda, acceda a [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+>
+> Conozca más sobre cómo gestionar los componentes logísticos en la plataforma VTEX: 
+>
+> * Para saber cómo registrar, modificar y hacer un seguimiento de los almacenes, consulte el artículo [Gestión del almacén](https://help.vtex.com/es/tutorial/gerenciar-estoque--tutorials_137).
+> * Para hacer un seguimiento y gestionar los ítems del almacén, consulte [Gestión del stock](https://help.vtex.com/es/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+> * Para configurar y gestionar la relación entre los almacenes y la retirada de pedidos, consulte [Gestión de muelles](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW).
+>
+> <div class="alert alert-warning">
+> Como el almacén forma parte del sistema logístico de su tienda, le sugerimos que registre los módulos relacionados con la operación logística en el siguiente orden:
+> <body>
+>
+> [Política Comercial;](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. <a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Política de envío;
+> </a>
+>
+> 3. [Muelle;](https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj)
+>
+> Almacén.
+>
+> </body>
diff --git a/docs/tutorials/es/web-application-firewall-waf.md b/docs/tutorials/es/web-application-firewall-waf.md
index c990efe10..dc33a5ddd 100644
--- a/docs/tutorials/es/web-application-firewall-waf.md
+++ b/docs/tutorials/es/web-application-firewall-waf.md
@@ -15,9 +15,7 @@ legacySlug: web-application-firewall-waf
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidad es parte de <a href="https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>.  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad es parte de [VTEX Shield](https://help.vtex.com/es/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh).  Si ya es cliente de VTEX y desea adoptar VTEX Shield para su negocio, por favor, póngase en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 Web Application Firewall (WAF) es una capa de seguridad diseñada para proteger aplicaciones web mediante monitoreo y filtrado del tráfico de internet.
 
diff --git a/docs/tutorials/es/what-are-the-requirements-to-start-developing-with-vtex-io.md b/docs/tutorials/es/what-are-the-requirements-to-start-developing-with-vtex-io.md
index dbcc4f51f..0ff4a65e8 100644
--- a/docs/tutorials/es/what-are-the-requirements-to-start-developing-with-vtex-io.md
+++ b/docs/tutorials/es/what-are-the-requirements-to-start-developing-with-vtex-io.md
@@ -47,6 +47,4 @@ Fullstack (React + Apollo + GraphQL):
   - https://www.howtographql.com/react-apollo/0-introduction/
 
 
-<div class="alert alert-info">
-Inicialmente, sólo el desarrollo front-end es posible. Por lo tanto, el ámbito de conocimiento inicial necesario se limita al React.
-</div>
+>ℹ️ Inicialmente, sólo el desarrollo front-end es posible. Por lo tanto, el ámbito de conocimiento inicial necesario se limita al React.
diff --git a/docs/tutorials/es/what-are-utm-source-utm-campaign-and-utm-medium.md b/docs/tutorials/es/what-are-utm-source-utm-campaign-and-utm-medium.md
index 34c7c4c67..08eab3c7a 100644
--- a/docs/tutorials/es/what-are-utm-source-utm-campaign-and-utm-medium.md
+++ b/docs/tutorials/es/what-are-utm-source-utm-campaign-and-utm-medium.md
@@ -23,9 +23,7 @@ O bien, usted puede definir que, para esa misma UTM, determinada promoción ser
 
 Así, la plataforma le permite tomar ciertas acciones de acuerdo con el origen del tráfico de la tienda.
 
-<div class="alert alert-info">
-En la pantalla de <strong>Gestión de pedidos</strong>, sólo utm_source está <a href="https://help.vtex.com/es/tutorial/como-filtrar-pedidos">disponible para filtro</a>.
-</div>
+>ℹ️ En la pantalla de **Gestión de pedidos**, sólo utm_source está [disponible para filtro](https://help.vtex.com/es/tutorial/como-filtrar-pedidos).
 
 ### Tipos de UTM
 
@@ -38,9 +36,7 @@ Pero usted puede utilizar estas UTMs de la manera que mejor se adapte a sus regl
 
 Por lo tanto, en la práctica, lo que importa es definir la acción correcta para los valores de estos parámetros.
 
-<div class="alert alert-danger">
-Atención: caracteres <strong>especiales no</strong> deben utilizarse en UTMs. Estas variables solo funcionan correctamente en caso de que sean utilizados caracteres <strong> alfanuméricos, guiones y underscore </strong>.
-</div>
+>❗ Atención: caracteres **especiales no** deben utilizarse en UTMs. Estas variables solo funcionan correctamente en caso de que sean utilizados caracteres ** alfanuméricos, guiones y underscore **.
 
 Para obtener más información sobre problemas con la adición de UTM al carrito, vaya a [Why are the UTMs not being applied to the cart?](https://developers.vtex.com/vtex-rest-api/docs/check-marketing-utms-used-at-checkout#why-are-the-utms-not-being-applied-to-the-cart).
 
diff --git a/docs/tutorials/es/what-is-a-franchise-account.md b/docs/tutorials/es/what-is-a-franchise-account.md
index bdf19f2d4..12b8908ea 100644
--- a/docs/tutorials/es/what-is-a-franchise-account.md
+++ b/docs/tutorials/es/what-is-a-franchise-account.md
@@ -46,14 +46,13 @@ Cada cuenta franquicia opera automáticamente como un _Seller White Label_ de la
 
 Los clientes finales no eligen ni tienen visibilidad de la existencia de los _Sellers White Label_ en ningún momento del proceso. En esta lógica, la relación de los consumidores es con la marca (cuenta principal) y no con cada tienda física (cuenta franquicia).
 
-<div class="alert alert-info">
-<p>Aunque todas las cuentas franquicia operan como <em>Sellers White Label</em> de la cuenta principal, estos conceptos no significan lo mismo. La cuenta franquicia es un tipo de cuenta, mientras que ser <em>White Label</em> es una propiedad del <em>seller</em>.
-<ul>
-<li><strong>Cuenta</strong>: puede ser del tipo franquicia o puede ser una cuenta normal.</li>
-<li><strong><em>Seller</em></strong>: puede ser del tipo <em>White Label </em>o puede ser del tipo no <em>White Label.</em></li>
-</ul>
-Como estos conceptos son independientes, <strong>eventualmente</strong> es posible que una cuenta franquicia opere como seller no White Label de un marketplace que no es la cuenta principal.</p>
-</div>
+>ℹ️ Aunque todas las cuentas franquicia operan como *Sellers White Label* de la cuenta principal, estos conceptos no significan lo mismo. La cuenta franquicia es un tipo de cuenta, mientras que ser *White Label* es una propiedad del *seller*.
+>
+> ***Cuenta**: puede ser del tipo franquicia o puede ser una cuenta normal.
+>
+> ****Seller***: puede ser del tipo *White Label *o puede ser del tipo no *White Label.*
+>
+> Como estos conceptos son independientes, **eventualmente** es posible que una cuenta franquicia opere como seller no White Label de un marketplace que no es la cuenta principal.
 
 ## Configuración de la cuenta franquicia
 
@@ -96,9 +95,7 @@ VTEX ofrece soluciones de _split_ de pagos que pueden hacer que la distribución
 
 Existen varios tipos de configuración posibles para los precios y medios de pago relacionados con las cuentas franquicia en VTEX, que se indican a continuación. Puedes elegir la forma de uso que mejor se adecue a tu negocio.
 
-<div class="alert alert-warning">
-<p>Si deseas implementar la aplicación VTEX Sales App, es necesario que las tiendas físicas utilicen los medios de pago de la cuenta principal.</p>
-</div>
+>⚠️ Si deseas implementar la aplicación VTEX Sales App, es necesario que las tiendas físicas utilicen los medios de pago de la cuenta principal.
 
 ## Solicitar la creación de una cuenta franquicia
 
diff --git a/docs/tutorials/es/what-is-a-marketplace.md b/docs/tutorials/es/what-is-a-marketplace.md
index 4285c4d20..1ae5e2596 100644
--- a/docs/tutorials/es/what-is-a-marketplace.md
+++ b/docs/tutorials/es/what-is-a-marketplace.md
@@ -21,9 +21,7 @@ En una experiencia de compra, un usuario navega por un sitio web seleccionando p
 
 Un marketplace también puede ser entendido como una *tienda vitrina*, que exhibe los propios productos y también productos de otras tiendas (sellers). Generalmente, un marketplace es una tienda con un buen tráfico de usuarios. Esto alienta a otras tiendas a exhibir sus productos en el marketplace, buscando una mayor conversión. En este escenario, el __marketplace__ es la tienda responsable del cierre de la compra y el __seller__ es la tienda responsable de realizar la entrega del pedido.
 
-<div class="alert alert-info">
-Siguiendo esta lógica, podemos concluir que una tienda VTEX que vende sus propios productos en su propia tienda actúa como marketplace y seller de forma simultánea. En este contexto, el pago se hace dentro del ambiente de la tienda (marketplace) y la entrega del pedido es responsabilidad de esa misma tienda (seller). Ver más detalles sobre este tema en <a href="https://help.vtex.com/tutorial/o-que-sao-pedidos-com-origem-marketplace-e-origem-fulfillment--6eVYrmUAwMOeKICU2KuG06">nuestro artículo</a> sobre el origen de los pedidos.
-</div>
+>ℹ️ Siguiendo esta lógica, podemos concluir que una tienda VTEX que vende sus propios productos en su propia tienda actúa como marketplace y seller de forma simultánea. En este contexto, el pago se hace dentro del ambiente de la tienda (marketplace) y la entrega del pedido es responsabilidad de esa misma tienda (seller). Ver más detalles sobre este tema en [nuestro artículo](https://help.vtex.com/tutorial/o-que-sao-pedidos-com-origem-marketplace-e-origem-fulfillment--6eVYrmUAwMOeKICU2KuG06) sobre el origen de los pedidos.
 
 ## Artículos relacionados
 
diff --git a/docs/tutorials/es/what-is-an-affiliate.md b/docs/tutorials/es/what-is-an-affiliate.md
index 7b91df18a..f9ee9fa47 100644
--- a/docs/tutorials/es/what-is-an-affiliate.md
+++ b/docs/tutorials/es/what-is-an-affiliate.md
@@ -15,9 +15,7 @@ legacySlug: que-es-afiliado
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-<div class="alert alert-info"> 
-Los afiliados en VTEX son diferente de la <a href="https://es.wikipedia.org/wiki/Marketing_de_afiliaci%C3%B3n"> definición habitual</a>. Lea a continuación para obtener más información.
-</div>
+>ℹ️ Los afiliados en VTEX son diferente de la [ definición habitual](https://es.wikipedia.org/wiki/Marketing_de_afiliaci%C3%B3n). Lea a continuación para obtener más información.
 
 [Configurar un afiliado](https://help.vtex.com/es/tutorial/como-configurar-afiliado) solo será necesario en los casos en que la tienda actúe como seller en un marketplace.
 
diff --git a/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md b/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
index b093b7140..e1bd64a70 100644
--- a/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
+++ b/docs/tutorials/es/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
@@ -71,7 +71,5 @@ Recolecta datos sobre el comportamiento de los usuarios y los compara con patron
 
 En VTEX, primero el operador del pago aprueba la compra y, a continuación, el antifraude evalúa el pedido. Con todo en orden, el sistema sigue su flujo normal. Son ejemplos de antifraude: ClearSale y Konduto. 
 
-<div class="alert alert-info">
-Es importante resaltar que cada negocio depende de factores específicos que influencian en la decisión sobre qué modalidad usar. Son varias las variables que pueden determinar la elección del medio de pago y cuál será su flujo financiero. Es fundamental, por lo tanto, tener en mente las necesidades y los propósitos reales del comerciante y del proyecto deseado.
-</div>
+>ℹ️ Es importante resaltar que cada negocio depende de factores específicos que influencian en la decisión sobre qué modalidad usar. Son varias las variables que pueden determinar la elección del medio de pago y cuál será su flujo financiero. Es fundamental, por lo tanto, tener en mente las necesidades y los propósitos reales del comerciante y del proyecto deseado.
 
diff --git a/docs/tutorials/es/what-is-the-difference-between-sales-policy-affiliate-and-seller.md b/docs/tutorials/es/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
index 3fc55f427..48312a5b5 100644
--- a/docs/tutorials/es/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
+++ b/docs/tutorials/es/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
@@ -45,9 +45,7 @@ Cada marketplace debe tener un __identificador único de afiliado__.
 
 Después de crear un [afiliado](/es/tutorial/como-configurar-afiliado/), usted debe asociar una política comercial a él. La política comercial contiene la información de los surtidos de producto, logística y precio que se enviará al afiliado en cuestión.
 
-<div class="alert alert-info">
-Si la configuración del marketplace es hecha por el módulo <a href="http://help.vtex.com/es/tutorial/configurar-politica-comercial-para-marketplace/">Bridge</a>, el afiliado se creará automáticamente en el OMS.
-</div>
+>ℹ️ Si la configuración del marketplace es hecha por el módulo [Bridge](http://help.vtex.com/es/tutorial/configurar-politica-comercial-para-marketplace/), el afiliado se creará automáticamente en el OMS.
 
 #### **SEPA MÁS**
 
diff --git a/docs/tutorials/es/what-is-the-period-considered-for-calculating-my-billing.md b/docs/tutorials/es/what-is-the-period-considered-for-calculating-my-billing.md
index 6b4df651f..95f42f6eb 100644
--- a/docs/tutorials/es/what-is-the-period-considered-for-calculating-my-billing.md
+++ b/docs/tutorials/es/what-is-the-period-considered-for-calculating-my-billing.md
@@ -22,6 +22,4 @@ Por lo tanto, el periodo que deberá tenerse en cuenta es siempre del primero al
 ## Ejemplo
 En el día 01/03 se emite una factura con la referencia "Febrero". Todos los pedidos que pasaron por el status __aprobado__, del día 01/02 hasta el 28/02, serán considerados en esa factura.
 
-<div class="alert alert-warning">
-Si recibe un cobro sin que su tienda esté en producción, sepa que se refiere al <strong>fee mensual</strong> de la tasa de mantenimiento de su ambiente. Este valor es cobrado pues aunque la tienda no esté en producción ya está consumiendo la estructura VTEX.
-</div>
+>⚠️ Si recibe un cobro sin que su tienda esté en producción, sepa que se refiere al **fee mensual** de la tasa de mantenimiento de su ambiente. Este valor es cobrado pues aunque la tienda no esté en producción ya está consumiendo la estructura VTEX.
diff --git a/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
index fa1dbf2d1..f8cf6f793 100644
--- a/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/es/what-is-the-purpose-of-the-customized-control.md
@@ -37,9 +37,7 @@ Para crear una tag de control personalizado, basta hacer clic en __Add__, regist
 
 ![cms-custom-elements EN / ES](https://images.ctfassets.net/alneenqid6w5/6pGE6dFRJuawKcMWce0Gem/87bbe6dfb66e75a8402b4be8935eeb18/custom_elements_EN_E_ES.png)
 
-<div class="alert alert-warning">
-  <p><b>Atención:</b> no cree un control del tipo HTML con un elemento <code>title</code>. Esto puede interferir con el buen funcionamiento de su tienda.</p>
-</div>
+>⚠️ **Atención:** no cree un control del tipo HTML con un elemento `title`. Esto puede interferir con el buen funcionamiento de su tienda.
 
 ## Aplicando un control personalizado a un template de página
 
diff --git a/docs/tutorials/es/what-is-the-shared-cart.md b/docs/tutorials/es/what-is-the-shared-cart.md
index bf3bd2620..03b2908e4 100644
--- a/docs/tutorials/es/what-is-the-shared-cart.md
+++ b/docs/tutorials/es/what-is-the-shared-cart.md
@@ -33,15 +33,11 @@ Ejemplo:
 
 - **URL del carrito compartido**: `https://www.{nombredelatienda}.com/checkout/?orderFormId=31155bb8fd6944c99829c171aa8ed5c4#/cart`
 
-<div class="alert alert-warning">
-Al ensamblar la URL del carrito compartido, verifique que la querystring <b>?orderFormId=...</b> posicionarse entre <b>/checkout/</b> y <b>#/cart</b>.
-</div>
+>⚠️ Al ensamblar la URL del carrito compartido, verifique que la querystring **?orderFormId=...** posicionarse entre **/checkout/** y **#/cart**.
 
 Para obtener acceso a la información de identificación del carrito, acceda [Checkout API](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview).
 
-<div class="alert alert-info">
-El uso de la funcionalidad de carrito abandonado es opcional, no generando impacto para las tiendas que no la utilizan.
-</div>
+>ℹ️ El uso de la funcionalidad de carrito abandonado es opcional, no generando impacto para las tiendas que no la utilizan.
 
 ## Seguridad de información
 
@@ -54,6 +50,4 @@ Para saber más sobre protección de datos, visite [Seguridad de SmartCheckout](
 Cuando se insertan nuevos parámetros en una URL, como una `querystring`, el seguimiento de la página puede cambiar, lo que afecta las evaluaciones realizadas por sistemas como el embudo de conversión de Google Analytics. Para utilizar el servicio de seguimiento de páginas con parámetros adicionales, consulte las reglas actualizadas en 
 [Configurar embudo de ventas en Google Analytics](https://help.vtex.com/es/tutorial/configurar-funil-de-vendas-no-google-analytics).
 
-<div class="alert alert-info">
-Si utiliza otro sistema de seguimiento de páginas en su tienda, consulte la documentación interna de ese sistema.
-</div>
+>ℹ️ Si utiliza otro sistema de seguimiento de páginas en su tienda, consulte la documentación interna de ese sistema.
diff --git a/docs/tutorials/es/what-is-the-sponsor-user.md b/docs/tutorials/es/what-is-the-sponsor-user.md
index 004e1058f..5d6892241 100644
--- a/docs/tutorials/es/what-is-the-sponsor-user.md
+++ b/docs/tutorials/es/what-is-the-sponsor-user.md
@@ -43,6 +43,4 @@ Solo el usuario titular puede realizar estas acciones críticas de mantenimiento
 
 Además, cuando VTEX necesita comunicar información importante sobre la tienda, como cambios de roles, dicha comunicación se lleva a cabo directa y exclusivamente con el usuario titular.
 
-<div class="alert alert-info">
-La creación de <a href="https://help.vtex.com/es/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet">credenciales de autenticación</a> (appKey/appToken) para integraciones de API ya no está restringida al usuario titular. Vea este <a href="https://help.vtex.com/es/announcements/changes-in-the-name-and-restricted-actions-available-to-the-master-user">anuncio</a> para saber más detalles sobre este cambio.
-</div>
+>ℹ️ La creación de [credenciales de autenticación](https://help.vtex.com/es/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) (appKey/appToken) para integraciones de API ya no está restringida al usuario titular. Vea este [anuncio](https://help.vtex.com/es/announcements/changes-in-the-name-and-restricted-actions-available-to-the-master-user) para saber más detalles sobre este cambio.
diff --git a/docs/tutorials/es/what-is-vtex-io.md b/docs/tutorials/es/what-is-vtex-io.md
index 4ab2b9630..7c3f3600b 100644
--- a/docs/tutorials/es/what-is-vtex-io.md
+++ b/docs/tutorials/es/what-is-vtex-io.md
@@ -15,9 +15,7 @@ legacySlug: o-que-e-o-vtex-io
 subcategory: 5eBwrcLFVSwYGSOQqGKQYW
 ---
 
-<div class="alert alert-info">
-VTEX IO es un ambiente de desarrollo serverless que le permite construir software web de alta calidad con bajo costo, sin preocupaciones de infraestructura y escalabilidad.
-</div>
+>ℹ️ VTEX IO es un ambiente de desarrollo serverless que le permite construir software web de alta calidad con bajo costo, sin preocupaciones de infraestructura y escalabilidad.
 
 Hoy, además de desarrollar el código que implementa las reglas de negocio, las empresas de tecnología necesitan preocuparse por buena parte de la infraestructura detrás del software que crean (configuración de servidores, permisos de acceso, escalabilidad horizontal y vertical, seguridad, etc). VTEX IO es un servicio que cubre toda la complejidad de la arquitectura de un servicio web moderno, retirando esa responsabilidad del desarrollador.
 
diff --git a/docs/tutorials/es/when-should-i-group-products-in-the-same-shipment.md b/docs/tutorials/es/when-should-i-group-products-in-the-same-shipment.md
index 828e5ff0d..9a48d3545 100644
--- a/docs/tutorials/es/when-should-i-group-products-in-the-same-shipment.md
+++ b/docs/tutorials/es/when-should-i-group-products-in-the-same-shipment.md
@@ -23,9 +23,7 @@ Es muy común que dentro de una misma compra los productos salgan de diferentes
 
 Esta es una práctica válida, por ejemplo, en el caso de transportistas como los Correios (en Brasil), donde para cada entrega es necesaria una factura, que a menudo es la misma para varios ítems, o en un escenario que la tienda posea inventarios físicamente distantes, pero que comparten el mismo muelle.
 
-<div class="alert alert-warning">
-Los grupos de envío son creados por la suma del tiempo de costo del inventario hasta el muelle y el tiempo de costo del muelle.
-</div>
+>⚠️ Los grupos de envío son creados por la suma del tiempo de costo del inventario hasta el muelle y el tiempo de costo del muelle.
 
 ### Artículos relacionados
 - [Cómo se maneja el envío](https://help.vtex.com/es/tutorial/como-funciona-a-remessa?locale=es)
diff --git a/docs/tutorials/es/white-label-sellers-selection.md b/docs/tutorials/es/white-label-sellers-selection.md
index 1c613de59..55a78946c 100644
--- a/docs/tutorials/es/white-label-sellers-selection.md
+++ b/docs/tutorials/es/white-label-sellers-selection.md
@@ -51,9 +51,7 @@ Cuando un cliente navega por el _marketplace_ y se desconoce su ubicación, los
 
 Cuando el _marketplace_ conoce la ubicación del cliente, ya sea por medio de geocoordenadas captadas o mediante datos que brindó el cliente, la plataforma VTEX puede consultar a todos los _sellers_ que cubren dicha región a fin de mostrar el precio y la disponibilidad de los productos en la vitrina. Obtén más información en [Configurar el precio y la disponibilidad de los SKU por región](https://help.vtex.com/es/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc).
 
-<div class="alert alert-warning">
-Cuando se conoce la ubicación del cliente, la plataforma VTEX consulta a todos los <i>sellers</i> de manera predeterminada, de acuerdo con la funcionalidad <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Región v2</a>. Sin embargo, es posible que algunas tiendas VTEX aún operen con Región v1, la cual tiene limitaciones en cuanto a la selección de <i>sellers</i> para la vitrina.
-</div>
+>⚠️ Cuando se conoce la ubicación del cliente, la plataforma VTEX consulta a todos los <i>sellers</i> de manera predeterminada, de acuerdo con la funcionalidad [Región v2](https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release). Sin embargo, es posible que algunas tiendas VTEX aún operen con Región v1, la cual tiene limitaciones en cuanto a la selección de <i>sellers</i> para la vitrina.
 
 ## Selección de sellers en el carrito
 
diff --git a/docs/tutorials/es/why-does-payment-with-registered-bank-slip-require-authentication.md b/docs/tutorials/es/why-does-payment-with-registered-bank-slip-require-authentication.md
index bab5eb877..1ab2265a8 100644
--- a/docs/tutorials/es/why-does-payment-with-registered-bank-slip-require-authentication.md
+++ b/docs/tutorials/es/why-does-payment-with-registered-bank-slip-require-authentication.md
@@ -23,6 +23,4 @@ Esta información se guarda en el perfil del cliente y se muestra en el boleto r
 
 Por su cuenta, el login se solicita tanto en el momento de __elegir el boleto registrado como medio de pago__ cuanto para __bajar el boleto en la página de cierre de compra (order placed)__.
 
-<div class="alert alert-info">
-La autenticación se requiere sólo a partir de la segunda compra. Como en la primera compra los datos se guardan por primera vez, no hay necesidad de autenticación. El boleto registrado será emitido con los datos informados en esta primera compra y solamente la persona que llenó las informaciones tendrá acceso a ellas.
-</div>
+>ℹ️ La autenticación se requiere sólo a partir de la segunda compra. Como en la primera compra los datos se guardan por primera vez, no hay necesidad de autenticación. El boleto registrado será emitido con los datos informados en esta primera compra y solamente la persona que llenó las informaciones tendrá acceso a ellas.
diff --git a/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index a8b5bab15..99ef418fd 100644
--- a/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/es/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Este escenario suele ocurrir debido a una inconsistencia en los campos de registro del usuario. Para verificar el escenario, necesitamos acceder a los datos de este cliente en el __Profile System__ de su tienda.
 
-<div class="alert alert-warning">
-Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
- <ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características de las versiones de Master Data
- </a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
- </a>
-</li>
-</ul>
-</div>
+>⚠️ Este artículo describe el funcionamiento de Master Data v1. Es importante evaluar cuál versión de Master Data satisface las necesidades de tu operación o ya está en uso.
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características de las versiones de Master Data
+>  </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+>  </a>
+> 
 
 Siga estos pasos para validar la información:
 
diff --git a/docs/tutorials/es/widget.md b/docs/tutorials/es/widget.md
index 04772b2fa..12fc63523 100644
--- a/docs/tutorials/es/widget.md
+++ b/docs/tutorials/es/widget.md
@@ -15,6 +15,4 @@ legacySlug: widget
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/wix-suiteshare.md b/docs/tutorials/es/wix-suiteshare.md
index fc53e742c..02945b59e 100644
--- a/docs/tutorials/es/wix-suiteshare.md
+++ b/docs/tutorials/es/wix-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: wix-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/wordpress-suiteshare.md b/docs/tutorials/es/wordpress-suiteshare.md
index a609fa267..01e74ad67 100644
--- a/docs/tutorials/es/wordpress-suiteshare.md
+++ b/docs/tutorials/es/wordpress-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: wordpress
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/es/working-with-master-data-rest-api.md b/docs/tutorials/es/working-with-master-data-rest-api.md
index f493c2ddf..3a0300f50 100644
--- a/docs/tutorials/es/working-with-master-data-rest-api.md
+++ b/docs/tutorials/es/working-with-master-data-rest-api.md
@@ -15,4 +15,4 @@ legacySlug: armazenando-dados-no-master-data-com-json-schema
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">Contenido bajo traducción</div>
+>⚠️ Contenido bajo traducción
diff --git a/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md b/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md
index 5d99ffc31..1c66fc6a0 100644
--- a/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md
+++ b/docs/tutorials/es/writing-an-effective-ticket-to-vtex-support.md
@@ -48,9 +48,7 @@ Para comprobar si el problema está asociado a IO, sigue los pasos a a continuac
     ```
     vtex uninstall {tema}
     ```
-    <div class="alert alert-info">
-    Puedes comprobar si hay algún tema instalado utilizando el comando <code>vtex list</code>, que muestra una lista de todas las aplicaciones instaladas en la tienda.
-    </div>
+    >ℹ️ Puedes comprobar si hay algún tema instalado utilizando el comando `vtex list`, que muestra una lista de todas las aplicaciones instaladas en la tienda.
 4.	Clona el tema predeterminado de Store Framework en tu computadora.
 5.	En la línea de comandos, accede a la carpeta del tema predeterminado.
 6.	Ejecuta el comando:
@@ -59,7 +57,7 @@ Para comprobar si el problema está asociado a IO, sigue los pasos a a continuac
     vtex link
     ```
 
-    <div class="alert alert-warning">Si tu tienda no tiene la aplicación Reviews and Ratings instalada, puede aparecer un error al intentar establecer el vínculo. Para evitar este problema, remueve esta aplicación de la lista de `peer dependencies` del archivo `manifest.json` del tema predeterminado. </div>
+    >⚠️ Si tu tienda no tiene la aplicación Reviews and Ratings instalada, puede aparecer un error al intentar establecer el vínculo. Para evitar este problema, remueve esta aplicación de la lista de `peer dependencies` del archivo `manifest.json` del tema predeterminado.
 
 7.	Accede al storefront de tu workspace mediante la URL:
     ```
diff --git a/docs/tutorials/es/zapier-suiteshare.md b/docs/tutorials/es/zapier-suiteshare.md
index 7b5d4409a..1ae083992 100644
--- a/docs/tutorials/es/zapier-suiteshare.md
+++ b/docs/tutorials/es/zapier-suiteshare.md
@@ -15,6 +15,4 @@ legacySlug: zapier
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-warning">
-  <p>Este contenido sólo está disponible en portugués.</p>
-</div>
+>⚠️ Este contenido sólo está disponible en portugués.
diff --git a/docs/tutorials/pt/account-management.md b/docs/tutorials/pt/account-management.md
index 8ab57771b..bc96cca44 100644
--- a/docs/tutorials/pt/account-management.md
+++ b/docs/tutorials/pt/account-management.md
@@ -19,9 +19,7 @@ O gerenciamento das suas contas é feito no **Gerenciamento da conta**. Dentro d
 
 Na página de cada conta você encontra dados básicos sobre a loja virtual, configurações de domínio e multidomínio, chaves de acesso para APIs, logotipo da empresa e informações de contato.
 
-<div class="alert alert-info">
-Alguns desses dados são úteis somente para a VTEX, e podem não refletir em alteração das informações exibidas na loja.
-</div>
+>ℹ️ Alguns desses dados são úteis somente para a VTEX, e podem não refletir em alteração das informações exibidas na loja.
 
 ## Botão de Ativo/Inativo
 
@@ -54,17 +52,15 @@ Você também pode usar o botão `Configurar outra loja` para [Criar multiloja](
 
 Na seção **Hosts** você deve adicionar o domínio principal da sua loja, que foi [configurado com apontamento de DNS](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-danger">
-Caso a sua operação possua mais de uma conta VTEX ou subcontas, não troque o domínio de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.
-</div>
+>❗ Caso a sua operação possua mais de uma conta VTEX ou subcontas, não troque o domínio de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.
 
 Para adicionar um novo host, basta clicar em `Adicionar novo domínio` e inserir o domínio no campo de texto.
 
-<div class="alert alert-warning">
-Se você adicionar mais de um domínio como host da sua loja, todos exibirão o mesmo conteúdo. No entanto, para atingir este objetivo recomendamos que cadastre apenas um domínio e use redirecionamentos para os outros. Saiba mais sobre redirecionamentos:
-<ul><li><a href=”https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirecionamento de outros endereços</a></li>
-<li><a href=”https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acesso sem www</a></li></ul> 
-</div>
+>⚠️ Se você adicionar mais de um domínio como host da sua loja, todos exibirão o mesmo conteúdo. No entanto, para atingir este objetivo recomendamos que cadastre apenas um domínio e use redirecionamentos para os outros. Saiba mais sobre redirecionamentos:
+>
+> *<a href=”https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirecionamento de outros endereços</a>
+>
+> *<a href=”https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acesso sem www</a>
 
 #### Subdomínios
 
@@ -80,9 +76,7 @@ A parte de **Contatos** é visível somente para o usuário que estiver cadastr
 
 Depois que um usuário preenche e salva **Nome** e **E-mail**, nos campos de contato, um e-mail automático é enviado a ele informando sobre o cadastro e solicitando geração de senha (caso este não possua nenhum acesso ao admin).
 
-<div class="alert alert-info">
-O template deste e-mail automático pode ser alterado na <a href="https://help.vtex.com/pt/tutorial/understanding-the-message-center--tutorials_84">Central de mensagens</a> modificando o template <i>account registration</i>.
-</div>
+>ℹ️ O template deste e-mail automático pode ser alterado na [Central de mensagens](https://help.vtex.com/pt/tutorial/understanding-the-message-center--tutorials_84) modificando o template <i>account registration</i>.
 
 ![cadastro de conta](https://images.ctfassets.net/alneenqid6w5/5tBCNxqBxeWkqOgiIcEaQw/4e044e1f46911db85da4e5ea0a195226/cadastro_de_conta.jpg)
 
diff --git a/docs/tutorials/pt/accounts-payable-brazil.md b/docs/tutorials/pt/accounts-payable-brazil.md
index 469a11598..ff308d3ef 100644
--- a/docs/tutorials/pt/accounts-payable-brazil.md
+++ b/docs/tutorials/pt/accounts-payable-brazil.md
@@ -17,9 +17,7 @@ subcategory: 22TaEgFhwE6a6CG2KASYkC
 
 Para garantir a conformidade dos pagamentos dos fornecedores, esse artigo contém informações referentes aos procedimentos de contas a pagar das empresas VTEX Brasil.
 
-<div class="alert alert-info">
-Os documentos e informações que não estiverem adequados à política da VTEX serão devolvidos para as devidas providências de adequação.
-</div>
+>ℹ️ Os documentos e informações que não estiverem adequados à política da VTEX serão devolvidos para as devidas providências de adequação.
 
 - Não são aceitas notas fiscais emitidas e recebidas após o dia 20 de cada mês. O solicitante deve garantir que o fornecedor cancele a cobrança e reemita na data entre dia 1 até dia 20 do mês seguinte.  
 - Os pagamentos são realizados até o dia 26 de cada mês.    
diff --git a/docs/tutorials/pt/actions-for-vtex-marketplace-operation.md b/docs/tutorials/pt/actions-for-vtex-marketplace-operation.md
index 9a2a186c6..2267c5514 100644
--- a/docs/tutorials/pt/actions-for-vtex-marketplace-operation.md
+++ b/docs/tutorials/pt/actions-for-vtex-marketplace-operation.md
@@ -46,9 +46,7 @@ O [Seller Portal (Beta)](https://help.vtex.com/pt/tutorial/seller-portal-primeir
 
 Essa ferramenta é uma opção recomendada para marketplaces que desejam ter mais controle sobre a curadoria de produtos que ofertam. 
 
-<div class="alert alert-info">
-Para ativar o Seller Portal para seus sellers, o marketplace deve solicitar essa funcionalidade entrando em contato com o CSM da sua conta na VTEX. 
-</div>
+>ℹ️ Para ativar o Seller Portal para seus sellers, o marketplace deve solicitar essa funcionalidade entrando em contato com o CSM da sua conta na VTEX.
 
 ## Catalogar anúncios
 
@@ -56,9 +54,7 @@ Um produto de um seller que foi enviado para o marketplace com informações de
 
 O processo de catalogação é realizado na página [SKUs Recebidos](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus/), no menu **MARKETPLACE > Sellers** do seu Admin VTEX, ou através de chamadas de API de [Match Received SKUs](https://developers.vtex.com/vtex-rest-api/reference/match). 
 
-<div class="alert alert-info">
-Antes de aprovar um anúncio, é importante garantir que as informações de produtos enviadas pelo seller correspondam à estratégia do seu negócio. Ao catalogar anúncios, considere a qualidade das informações enviadas pelo seller, como preço, descrição do produto e imagem.
-</div>
+>ℹ️ Antes de aprovar um anúncio, é importante garantir que as informações de produtos enviadas pelo seller correspondam à estratégia do seu negócio. Ao catalogar anúncios, considere a qualidade das informações enviadas pelo seller, como preço, descrição do produto e imagem.
 
 O [VTEX Matcher](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424) é a ferramenta usada por marketplaces para avaliar anúncios enviados por sellers e acelerar o processo de catalogação. É possível configurar o VTEX Matcher para que opere sobre regras diferentes da configuração _default_, por meio da [API de Aprovação automática](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig).
 
diff --git a/docs/tutorials/pt/activating-new-vtex-cdn.md b/docs/tutorials/pt/activating-new-vtex-cdn.md
index bf9f93383..6dbebaaa1 100644
--- a/docs/tutorials/pt/activating-new-vtex-cdn.md
+++ b/docs/tutorials/pt/activating-new-vtex-cdn.md
@@ -15,9 +15,7 @@ legacySlug: ativar-nova-cdn-da-vtex
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
-<div class="alert alert-warning">
-Em um compromisso de constante evolução do nosso produto, a VTEX está disponibilizando às suas lojas uma nova CDN (Content Delivery Network). Neste novo modelo, <strong>todas as páginas do site serão entregues a partir dessa nova CDN especializada</strong>, não se limitando aos arquivos estáticos.
-</div>
+>⚠️ Em um compromisso de constante evolução do nosso produto, a VTEX está disponibilizando às suas lojas uma nova CDN (Content Delivery Network). Neste novo modelo, **todas as páginas do site serão entregues a partir dessa nova CDN especializada**, não se limitando aos arquivos estáticos.
 
 Uma Rede de Entrega de Conteúdo (tradução livre de seu acrônimo) foca em segurança, baixa latência e altas velocidades de transferência, trabalhando com as melhores tecnologias para este fim, inclusive sendo geograficamente próxima do cliente que acessa a loja virtual.
 
@@ -36,9 +34,7 @@ Cumpridos os requisitos deste artigo, deve ser feito o preenchimento [deste form
 
 ### Ativar HTTPS em todo o site
 
-<div class="alert alert-info">
-Um dos requisitos para a nova CDN é que o site seja disponibilizado totalmente em HTTPS.
-</div>
+>ℹ️ Um dos requisitos para a nova CDN é que o site seja disponibilizado totalmente em HTTPS.
 
 Isto porque, com a nova CDN, qualquer página HTTP será automaticamente redirecionada para HTTPS. Mas antes é importante configurar sua loja na VTEX para que ela aceite o tráfego neste protocolo. Em caso contrário, ela será redirecionada novamente para HTTP - criando um loop de redirecionamento, o que quebrará a navegação destas páginas.
 
@@ -94,9 +90,7 @@ Apontamentos antigos usam endereços como:
 
 Independentemente de qual for o caso da sua loja, você deverá fazer a atualização para o novo padrão.
 
-<div class="alert alert-danger">
-<strong>Importante:</strong> o CNAME antigo <strong>deve ser removido</strong>. A existência de duas entradas em seu DNS provavelmente vão ocasionar em problemas. Deve ser mantida somente a nova entrada CNAME.
-</div>
+>❗ **Importante:** o CNAME antigo **deve ser removido**. A existência de duas entradas em seu DNS provavelmente vão ocasionar em problemas. Deve ser mantida somente a nova entrada CNAME.
 
 Não se esqueça de solicitar a ativação final pelo [formulário](https://docs.google.com/forms/d/e/1FAIpQLSdI2FBXGmlSOXEtWxrYfVveln7xOJcmYotqrKfgFgmHn771Fg/viewform). A loja vai funcionar somente com o CNAME e HTTPS, mas o seu preenchimento nos ajuda a ativar de forma antecipada a CDN para sua loja, para que sua loja possa desfrutar dos novos recursos.
 
diff --git a/docs/tutorials/pt/activating-skus-in-bulk.md b/docs/tutorials/pt/activating-skus-in-bulk.md
index 7ae8f2191..42610a59c 100644
--- a/docs/tutorials/pt/activating-skus-in-bulk.md
+++ b/docs/tutorials/pt/activating-skus-in-bulk.md
@@ -29,10 +29,9 @@ Para ativar todos os SKUs utilizando o Admin VTEX, siga os passos abaixo:
 1. Acesse a URL  `https://{accountName}.myvtex.com/admin/site/productskuactivateall.aspx `.
 2. Clique em `Ativar todos os SKUs`.
 
-<div class="alert alert-warning">
-<p>SKUs cadastrados com dados inválidos não terão a opção de <em>Ativar o SKU se possível</em> ativada.</p>
-<p>Caso nem todos os SKUs tenham sido marcados com a opção de <em>Ativar o SKU se possível</em>, repita o processo descrito acima.</p>
-</div>
+>⚠️ SKUs cadastrados com dados inválidos não terão a opção de *Ativar o SKU se possível* ativada.
+>
+> Caso nem todos os SKUs tenham sido marcados com a opção de *Ativar o SKU se possível*, repita o processo descrito acima.
 
 ## Ativar um grupo de SKUs 
 
diff --git a/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md b/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md
index a99dd90c5..e067f965c 100644
--- a/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md
+++ b/docs/tutorials/pt/add-3ds-support-to-the-integration-with-adyen.md
@@ -30,9 +30,7 @@ Para adicionar suporte ao [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-sec
 
 Depois de configurar o conector na VTEX, é necessário acessar o painel da Adyen para habilitar o 3DS nas transações da sua loja.
 
-<div class="alert alert-warning">
-  Recomendamos que as configurações sejam feitas primeiramente em ambiente Test. Somente após as devidas validações, acesse o ambiente <b>Live</b> para para as configurações finais.
-  </div>
+>⚠️ Recomendamos que as configurações sejam feitas primeiramente em ambiente Test. Somente após as devidas validações, acesse o ambiente **Live** para para as configurações finais.
 
 1. Clique nos links abaixo para acessar o ambiente Test e Live, da Adyen
 
diff --git a/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md b/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md
index 52b539937..1261bee5a 100644
--- a/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md
+++ b/docs/tutorials/pt/adding-a-record-on-a-master-data-form.md
@@ -19,13 +19,12 @@ Para incluir um registro em um formulário do Master Data, é necessário acessa
 
 Os campos podem ser configurados como editáveis ou não diretamente na entidade de dados. Saiba mais em [Entidade de dados](https://help.vtex.com/pt/tutorial/entidade-de-dados--tutorials_1265).
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
- <ul>
-  <li><a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">Características das versões do Master Data</a></li>
-  <li><a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">Master Data v2</a></li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> * [Características das versões do Master Data](https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available)
+>
+> * [Master Data v2](https://developers.vtex.com/vtex-rest-api/docs/getting-started-1)
+> 
 
 ## Adicionar um registro
 
diff --git a/docs/tutorials/pt/adding-a-seller-beta.md b/docs/tutorials/pt/adding-a-seller-beta.md
index a93fc8273..5a4db2c3a 100644
--- a/docs/tutorials/pt/adding-a-seller-beta.md
+++ b/docs/tutorials/pt/adding-a-seller-beta.md
@@ -19,9 +19,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 Para adicionar um seller não identificável, também chamado de [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), é necessário ter esse modelo previsto no contrato com a VTEX. Uma vez ajustado o contrato com o representante comercial da VTEX responsável por seu marketplace, solicite a [adição de uma conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) por meio do nosso Suporte. Toda conta franquia é criada como seller white label e não é possível mudar o tipo de seller após a sua criação. 
 
-<div class="alert alert-info">
-Se quiser encontrar novos parceiros para venderem em seu marketplace, utilize o Marketplace Network, que facilita a identificação e contato entre marketplaces e sellers que operam no ecossistema VTEX, além de conectores certificados (parceiros).
-</div>
+>ℹ️ Se quiser encontrar novos parceiros para venderem em seu marketplace, utilize o Marketplace Network, que facilita a identificação e contato entre marketplaces e sellers que operam no ecossistema VTEX, além de conectores certificados (parceiros).
 
 1. No seu Admin VTEX, acesse *MARKETPLACE > Sellers > Gerenciamento*.
 2. Clique em `Adicionar Seller`.
@@ -65,9 +63,7 @@ Se quiser encontrar novos parceiros para venderem em seu marketplace, utilize o
 - **Trocas e devoluções:** descrição da política de trocas e devoluções acordadas previamente entre marketplace e seller.     
 - **Política de Privacidade de Segurança:** descrição da política de segurança acordada previamente entre marketplace e seller.  
 
-<div class="alert alert-info">
-Com a nova versão da página, lançada em 2022, retiramos da tela o campo Endpoint de Catálogo, pois não é mais necessário para a integração com um novo seller. Caso necessário, ainda é possível realizar o gerenciamento do campo por meio de API.
-</div>
+>ℹ️ Com a nova versão da página, lançada em 2022, retiramos da tela o campo Endpoint de Catálogo, pois não é mais necessário para a integração com um novo seller. Caso necessário, ainda é possível realizar o gerenciamento do campo por meio de API.
 
 Uma vez preenchido o formulário e clicado em **Salvar**, seu seller será adicionado ao marketplace. Para que a configuração da sua loja como marketplace seja concluída, é preciso também [Mapear marcas, categorias e especificações do catálogo do seller](https://help.vtex.com/pt/tutorial/mapeando-categorias-e-marcas-para-marketplace/) e [Aprovar anúncios recebidos](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus/).
 
diff --git a/docs/tutorials/pt/adding-a-seller.md b/docs/tutorials/pt/adding-a-seller.md
index e17039c94..6428b0a90 100644
--- a/docs/tutorials/pt/adding-a-seller.md
+++ b/docs/tutorials/pt/adding-a-seller.md
@@ -19,9 +19,7 @@ subcategory: 2xWRgEIlR2ookieEmm4KQu
 
 Para adicionar um seller não identificável, também chamado de [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), é necessário ter esse modelo previsto no contrato com a VTEX. Uma vez ajustado o contrato com o representante comercial da VTEX responsável por seu marketplace, solicite a [adição de uma conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) por meio do nosso Suporte. Toda conta franquia é criada como seller white label e não é possível mudar o tipo de seller após a sua criação. 
 
-<div class="alert alert-info">
-Se quiser encontrar novos parceiros para venderem em seu marketplace, utilize o __Encontrar sellers__, que facilita a identificação e contato entre marketplaces e sellers que operam no ecossistema VTEX, além de conectores certificados (parceiros).
-</div>
+>ℹ️ Se quiser encontrar novos parceiros para venderem em seu marketplace, utilize o __Encontrar sellers__, que facilita a identificação e contato entre marketplaces e sellers que operam no ecossistema VTEX, além de conectores certificados (parceiros).
 
 1. No seu Admin VTEX, acesse *MARKETPLACE > Gerenciamento*.
 2. Clique em `Adicionar Seller`.
@@ -65,9 +63,7 @@ Se quiser encontrar novos parceiros para venderem em seu marketplace, utilize o
 - **Trocas e devoluções:** descrição da política de trocas e devoluções acordadas previamente entre marketplace e seller.     
 - **Política de Privacidade de Segurança:** descrição da política de segurança acordada previamente entre marketplace e seller.  
 
-<div class="alert alert-info">
-Com a nova versão da página, lançada em 2022, retiramos da tela o campo Endpoint de Catálogo, pois não é mais necessário para a integração com um novo seller. Caso necessário, ainda é possível realizar o gerenciamento do campo por meio de API.
-</div>
+>ℹ️ Com a nova versão da página, lançada em 2022, retiramos da tela o campo Endpoint de Catálogo, pois não é mais necessário para a integração com um novo seller. Caso necessário, ainda é possível realizar o gerenciamento do campo por meio de API.
 
 Uma vez preenchido o formulário e clicado em **Salvar**, seu seller será adicionado ao marketplace. Para que a configuração da sua loja como marketplace seja concluída, é preciso também [Mapear marcas, categorias e especificações do catálogo do seller](https://help.vtex.com/pt/tutorial/mapeando-categorias-e-marcas-para-marketplace/) e [Aprovar anúncios recebidos](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus/).
 
diff --git a/docs/tutorials/pt/adding-an-attachment.md b/docs/tutorials/pt/adding-an-attachment.md
index da54f571e..49c640a6b 100644
--- a/docs/tutorials/pt/adding-an-attachment.md
+++ b/docs/tutorials/pt/adding-an-attachment.md
@@ -39,9 +39,7 @@ Após realizar o cadastro inicial do anexo, você precisa adicionar as chaves e
 3. Clique em `Inserir Novo`. Você pode cadastrar outras chaves repetindo esse processo, se desejar.
 4. Para finalizar, clique em `Salvar`.
 
-<div class="alert alert-warning">
-<p>É obrigatório preencher o campo <strong>Máximo de Caracteres</strong>. Caso esse campo não seja preenchido, o anexo não vai aparecer para o seu cliente como uma opção de seleção no carrinho.</p>
-</div>
+>⚠️ É obrigatório preencher o campo **Máximo de Caracteres**. Caso esse campo não seja preenchido, o anexo não vai aparecer para o seu cliente como uma opção de seleção no carrinho.
 
 ## Associar o anexo a um SKU
 
@@ -56,6 +54,4 @@ Após criar o anexo de SKU e configurar as chaves e os valores permitidos, você
 
 Você também pode associar um anexo ao SKU utilizando a [Catalog API](https://developers.vtex.com/docs/api-reference/catalog-api#post-/api/catalog/pvt/skuattachment), se desejar.
 
-<div class="alert alert-warning">
-<p>A VTEX não controla o estoque de um anexo. Essa função é do Marketplace ou do Seller.</p>
-</div>
+>⚠️ A VTEX não controla o estoque de um anexo. Essa função é do Marketplace ou do Seller.
diff --git a/docs/tutorials/pt/adding-collections-cms.md b/docs/tutorials/pt/adding-collections-cms.md
index dedb8c959..c09b28db0 100644
--- a/docs/tutorials/pt/adding-collections-cms.md
+++ b/docs/tutorials/pt/adding-collections-cms.md
@@ -27,9 +27,7 @@ Siga o passo a passo abaixo para cadastrar uma nova coleção:
 4. Preencha os campos do formulário de Coleção. Para entender melhor o significado de cada campo, acesse nosso artigo sobre [como preencher campos de cadastro de coleção](https://help.vtex.com/pt/tutorial/preencher-campos-de-cadastro-de-colecao--7eKL7CFRW3yGKlnDfQetbj).
 5. Clique em __Save Product Cluster__.
 
-<div class="alert alert-warning">
-  Quando a quantidade de coleções criadas ultrapassar o limite de vinte, as coleções excedentes podem ser encontradas na interface através do campo de pesquisa. A busca nesse campo deve ser feita com base no nome da coleção desejada.
-</div>
+>⚠️ Quando a quantidade de coleções criadas ultrapassar o limite de vinte, as coleções excedentes podem ser encontradas na interface através do campo de pesquisa. A busca nesse campo deve ser feita com base no nome da coleção desejada.
 
 A escolha dos produtos que vão compor uma coleção é feita através da criação de um __grupo__. Para isso, basta clicar em __New Group__ dentro da coleção desejada. 
 
@@ -54,9 +52,7 @@ Sendo:
 
 Por isso, o primeiro grupo criado para qualquer coleção deve ser obrigatoriamente do tipo _Inclusive_.
 
-<div class="alert alert-warning">
-Esteja sempre atento ao tipo de grupo definido no cadastro. Ao incluir produtos em um grupo tipo <i>Exclusive</i>, por exemplo, eles <strong>não</strong> serão incluídos a uma coleção por conta da natureza do seu grupo. 
-</div>
+>⚠️ Esteja sempre atento ao tipo de grupo definido no cadastro. Ao incluir produtos em um grupo tipo <i>Exclusive</i>, por exemplo, eles **não** serão incluídos a uma coleção por conta da natureza do seu grupo.
 
 ## Seleção de produtos
 
@@ -103,15 +99,11 @@ No campo __Find SKUs__, é possível digitar o ID de quantos SKUs forem desejado
 
 Para excluir um SKU da lista, basta clicar no botão vermelho ao lado dele.
 
-<div class="alert alert-info">
-Quando o número de SKUs na listagem ultrapassar 10 itens, um controle de paginação ficará disponível.
-</div>
+>ℹ️ Quando o número de SKUs na listagem ultrapassar 10 itens, um controle de paginação ficará disponível.
 
 ### Por planilha 
 
-<div class="alert alert-info">
-Obtenha o modelo de arquivo para a inclusão e exclusão de SKUs da coleção <a href="//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls">aqui</a>.
-</div>
+>ℹ️ Obtenha o modelo de arquivo para a inclusão e exclusão de SKUs da coleção [aqui](//assets.contentful.com/alneenqid6w5/Lo7Y0tXh6eKyyUSs4MESQ/209e614248978f0e86a37e4ddff50162/Colecao.xls).
 
 #### Inclusão massiva
 
@@ -135,15 +127,11 @@ Para evitar a exclusão manual de um SKU por vez, também é possível usar o re
 
 Nesse caso em específico, os SKUs listados na planilha importada serão excluídos do grupo. Para isso, clique na opção __excluir skus__ depois que o arquivo for carregado.
 
-<div class="alert alert-warning">
-Os SKUs inativos não terão seus IDs considerados para inclusão ou exclusão mesmo que estejam listados na planilha.
-</div>
+>⚠️ Os SKUs inativos não terão seus IDs considerados para inclusão ou exclusão mesmo que estejam listados na planilha.
 
 ## Produtos por data de lançamento no mercado
 
-<div class="alert alert-warning">
-Na seção de <strong>Other options</strong>, as opções <strong>Pre-sales</strong> e <strong>Launches</strong> são um complemento à escolha dos produtos por Categorias, Marcas ou SKUs. Isso significa que essas flags só vão funcionar se você já tiver selecionado anteriormente
-</div>
+>⚠️ Na seção de **Other options**, as opções **Pre-sales** e **Launches** são um complemento à escolha dos produtos por Categorias, Marcas ou SKUs. Isso significa que essas flags só vão funcionar se você já tiver selecionado anteriormente
 
 Note que apenas é possível selecionar uma das duas opções. Caso queira que ambos os cenários sejam contemplados, crie dois grupos e configure cada um deles com a respectiva opção.
 
@@ -157,6 +145,4 @@ Para criar uma coleção de produtos que ainda não foram lançados na sua loja,
 
 A opção __Launches__ permite criar uma coleção de produtos recentemente lançados. Ao selecionar essa opção, o sistema considerará todos os produtos lançados dentro do intervalo de 30 dias anteriores ao vigente. A data de lançamento considerada é também aquela definida no campo _Data de lançamento no mercado_ no cadastro do produto. 
 
-<div class="alert alert-info">
-Se quiser entender como funciona a exclusão de uma coleção de produtos, acesse nosso artigo sobre <a href="https://help.vtex.com/pt/tutorial/como-deletar-colecao--6C620yHzwsGoS8iaCocAM2">como deletar coleções</a>.
-</div>
+>ℹ️ Se quiser entender como funciona a exclusão de uma coleção de produtos, acesse nosso artigo sobre [como deletar coleções](https://help.vtex.com/pt/tutorial/como-deletar-colecao--6C620yHzwsGoS8iaCocAM2).
diff --git a/docs/tutorials/pt/additional-shipping-costs.md b/docs/tutorials/pt/additional-shipping-costs.md
index e5e54569f..99453f92c 100644
--- a/docs/tutorials/pt/additional-shipping-costs.md
+++ b/docs/tutorials/pt/additional-shipping-costs.md
@@ -29,10 +29,8 @@ Os valores adicionais podem ser configurados conforme:
 
 ![adicionais frete PT](https://images.contentful.com/alneenqid6w5/3j3VNUKq6qTGJRfGWGbc14/32b53f2163eed7c9497bacfb95101b65/adicionais_frete_PT.svg)
 
-<div class="alert alert-danger">
-É importante ressaltar que é possível ter todos os adicionais configurados simultaneamente para uma única tarifa de envio. O cálculo final da <a href="https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM">tarifa de envio</a> é a soma de todos os adicionais cadastrados mais a tarifa fixa do frete. 
-A tarifa de envio não é o custo final de envio.
-</div>
+>❗ É importante ressaltar que é possível ter todos os adicionais configurados simultaneamente para uma única tarifa de envio. O cálculo final da [tarifa de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg3rv0854udEPedvMM) é a soma de todos os adicionais cadastrados mais a tarifa fixa do frete. 
+> A tarifa de envio não é o custo final de envio.
 
 ## Adicional por peso
 
@@ -88,9 +86,7 @@ Adicional de frete: ($10+$0+$9+$5)x10%=$2,4
 Adicionais de frete: ($9+$5+$2,4)=$16,4  
 Tarifa de envio: ($10+$16,4)=$26,4  
 
-<div class="alert alert-danger">
-É importante lembrar que o cálculo do adicional por preço não considera possíveis descontos e promoções, e sim o valor cheio do carrinho. Se o adicional por preço for menor que o adicional de seguro, o adicional por preço é desconsiderado no cálculo final da tarifa de envio.
-</div>
+>❗ É importante lembrar que o cálculo do adicional por preço não considera possíveis descontos e promoções, e sim o valor cheio do carrinho. Se o adicional por preço for menor que o adicional de seguro, o adicional por preço é desconsiderado no cálculo final da tarifa de envio.
 
 ![faixa-peso PT](https://images.contentful.com/alneenqid6w5/4s9nSGox3lNthbGiDUdOFq/dbe9c301826e8e91104cd7a8ded70690/faixa-peso_PT.png)
 
@@ -126,9 +122,7 @@ Tarifa de envio: ($15+10,3)=$25,3
 
 O adicional de seguro é configurado apenas pela [planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) pelo campo _MinimumValueInsurance._
 
-<div class="alert alert-danger">
-Se o adicional por preço for menor que o adicional de seguro, o adicional por preço é desconsiderado no cálculo final da tarifa de envio.
-</div>
+>❗ Se o adicional por preço for menor que o adicional de seguro, o adicional por preço é desconsiderado no cálculo final da tarifa de envio.
 
 ## Adicional de frete
 
diff --git a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
index 06992835a..3379a2e71 100644
--- a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
@@ -54,9 +54,7 @@ Atualmente a VTEX disponibiliza um único formato de anúncio: resultados de pes
 8. Na seção *Orçamento, bid e cronograma*, clique no botão de editar <i class="fas fa-pencil-alt"></i>.
 9. Defina os valores dos lances para cada produto. Você pode definir cada valor individualmente.
 
-  <div class="alert alert-info">
-O lance de um produto é o custo por clique (CPC), valor gasto quando um usuário clica em um anúcio. Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanhas">campanhas</a> e como fuciona o <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#priorizacao-de-anuncios">leilão</a>.
-</div>
+  >ℹ️ O lance de um produto é o custo por clique (CPC), valor gasto quando um usuário clica em um anúcio. Saiba mais sobre [campanhas](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanhas) e como fuciona o [leilão](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#priorizacao-de-anuncios).
 
 10. Clique em `Salvar`.
 11. Defina o orçamento total e a data final da campanha.
diff --git a/docs/tutorials/pt/affiliates-program-app.md b/docs/tutorials/pt/affiliates-program-app.md
index db8b7c58d..2def9fcb3 100644
--- a/docs/tutorials/pt/affiliates-program-app.md
+++ b/docs/tutorials/pt/affiliates-program-app.md
@@ -84,9 +84,7 @@ Para criar um novo afiliado, clique no botão `Adicionar afiliado`, preencha os
 
 Para pesquisar um afiliado, digite na barra de busca por alguma das seguintes informações: _ID do afiliado, Nome, Nome da Loja, Email_ ou_ Telefone. _
 
-<div class="alert alert-warning">
-No aplicativo <b>Affiliates Program</b>, além do termo afiliado ser diferente do <a href="https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0">conceito usual de afiliado na VTEX</a>, o <code>ID do Afiliado</code> também não corresponde ao código padrão. No aplicativo, o <code>ID do Afiliado</code> é um código alfanumérico gerado automaticamente quando você cria um novo afiliado.
-</div>
+>⚠️ No aplicativo **Affiliates Program**, além do termo afiliado ser diferente do [conceito usual de afiliado na VTEX](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0), o `ID do Afiliado` também não corresponde ao código padrão. No aplicativo, o `ID do Afiliado` é um código alfanumérico gerado automaticamente quando você cria um novo afiliado.
 
 ### Filtrar afiliados
 
@@ -148,9 +146,7 @@ Para pesquisar um pedido, digite na barra de busca o `ID do afiliado` relacionad
 
 O aplicativo **Affiliates Program** permite que você exporte uma lista com extensão CSV dos pedidos de afiliados. 
 
-<div class="alert alert-warning">
-Para habilitar a função de exportar lista, primeiro é necessário configurar templates de email, conforme descrito no guia para desenvolvedores <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app#email-templates">Affiliates Program app</a>.
-</div>
+>⚠️ Para habilitar a função de exportar lista, primeiro é necessário configurar templates de email, conforme descrito no guia para desenvolvedores [Affiliates Program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app#email-templates).
 
 Após a configuração, para exportar a lista basta clicar em **Exportar**, na página **Gerenciamento de Pedidos**. A seguinte mensagem de confirmação deve aparecer:
 
diff --git a/docs/tutorials/pt/amaro-integration.md b/docs/tutorials/pt/amaro-integration.md
index ef71b0559..cc762b4c3 100644
--- a/docs/tutorials/pt/amaro-integration.md
+++ b/docs/tutorials/pt/amaro-integration.md
@@ -64,9 +64,7 @@ Para configurar uma nova chave, siga os passos abaixo:
 5. Clique em Adicionar perfis e selecione os perfis desejados.  
 6. Clique em Gerar.  
 
-<div class="alert alert-danger">
-  O <i>AppToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
-</div>
+>❗ O <i>AppToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
 
 ### Criar ID do afiliado  
 
@@ -101,7 +99,5 @@ __- Política comercial:__ número da política comercial determinada na etapa [
 
 Uma vez que o seller tenha reunido esses dados, deverá enviá-los para o contato informado pelo time de Marcas Parceiras da AMARO. Desta forma,a integração será concluída pelo marketplace.  
 
-<div class="alert alert-info">
-Após a primeira conexão com o seller center AMARO e verificação inicial do sucesso da integração, o time de Marcas Parceiras AMARO irá orientar o seller a adicionar os demais produtos na política comercial para a etapa final de curadoria e exibição dos itens no amaro.com e aplicativos AMARO.
-</div>
+>ℹ️ Após a primeira conexão com o seller center AMARO e verificação inicial do sucesso da integração, o time de Marcas Parceiras AMARO irá orientar o seller a adicionar os demais produtos na política comercial para a etapa final de curadoria e exibição dos itens no amaro.com e aplicativos AMARO.
 
diff --git a/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md b/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
index 2d85f99d8..230236164 100644
--- a/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
+++ b/docs/tutorials/pt/amazon-multi-channel-fulfillment-mcf-app.md
@@ -15,9 +15,7 @@ legacySlug: aplicativo-amazon-multi-channel-fulfillment-mcf
 subcategory: 1P1vFnzQ4TQJsBRDoPVKUI
 ---
 
-<div class="alert alert-info">
-Esse aplicativo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ Esse aplicativo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 O aplicativo Amazon Multi-Channel Fulfillment (MCF) possibilita a integração do seu negócio com o programa homônimo. Com a integração, clientes VTEX podem usar a rede de logística da Amazon em suas próprias lojas. Assim, os itens de venda ficam armazenados nos centros de distribuição Amazon, e após cada venda no seu ecommerce, a plataforma VTEX envia os dados do pedido para que a Amazon separe, embale e envie aos destinatários.
 
@@ -35,11 +33,9 @@ Antes de instalar, é preciso:
 * Conferir se os produtos da sua loja atendem às [políticas de restrições da Amazon](https://sellercentral.amazon.com/gp/help/external/200164330).
 * Garantir que sua loja está localizada nos países onde o MCF está disponível. Países como Estados Unidos, Austrália, México, Alemanha e Canadá já possuem o MCF da Amazon. Confira a lista atualizada de países [nesta página da Amazon](https://sell.amazon.com/fulfillment-by-amazon/fba-multi-channel.html).
 
-<div class="alert alert-danger">
-Ao instalar o aplicativo, a plataforma VTEX trata a integração como uma loja externa Amazon e utiliza a integração do tipo marketplace com a Amazon.
-<p>A instalação do aplicativo deve ser feita em todas as contas VTEX em que se deseja utilizar a funcionalidade. 
-<p>Recomendamos utilizar o Checkout V6.
-</div>
+>❗ Ao instalar o aplicativo, a plataforma VTEX trata a integração como uma loja externa Amazon e utiliza a integração do tipo marketplace com a Amazon.
+> <p>A instalação do aplicativo deve ser feita em todas as contas VTEX em que se deseja utilizar a funcionalidade. 
+> <p>Recomendamos utilizar o Checkout V6.
 
 ## Instalação, configuração e acesso:
 
@@ -83,10 +79,8 @@ Para realizar essa configuração, acesse o Admin e siga os passos abaixo.
 
 Nos passos 8 e 10, a chave que deve ser preenchida é a chave de geolocalização Google. Confira [como gerar uma chave no guia de desenvolvedores do Google.](https://developers.google.com/maps/documentation/geocoding/overview) 
 
-<div class="alert alert-info">
-Se tiver dúvidas sobre a chave de geolocalização Google, confira detalhadamente como essa configuração é utilizada pela plataforma VTEX nos artigos <a href="https://help.vtex.com/pt/tutorial/geolocalizacao-no-checkout--tutorials_4345">Configurar geolocalização no checkout</a>
-  e <a href="https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138">Cadastrar geolocalização</a>.
-</div>
+>ℹ️ Se tiver dúvidas sobre a chave de geolocalização Google, confira detalhadamente como essa configuração é utilizada pela plataforma VTEX nos artigos [Configurar geolocalização no checkout](https://help.vtex.com/pt/tutorial/geolocalizacao-no-checkout--tutorials_4345)
+>   e [Cadastrar geolocalização](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138).
 
 ### Instalação do aplicativo
 
@@ -107,9 +101,7 @@ Para instalar o aplicativo, acesse a App Store VTEX:
     * **ERP Hook URL:** Endereço do ERP que incluirá as notas fiscais dos pedidos (para o caso em que o campo **Automatic Invoice** estiver como Deactivate).
     * **Amazon Marketplace:** país em que você irá utilizar o Amazon MCF.
 
-<div class="alert alert-warning">
-As configurações feitas no campo Automatic Invoice serão aplicadas a todos os pedidos.
-</div>
+>⚠️ As configurações feitas no campo Automatic Invoice serão aplicadas a todos os pedidos.
 
 ![MCF](https://images.ctfassets.net/alneenqid6w5/1fPmofbBRr6kge5qzfHvXV/7e61a4ea7adc5595f583f55dd644b99d/Amazon_MCF_PT.PNG)
 
diff --git a/docs/tutorials/pt/analytics.md b/docs/tutorials/pt/analytics.md
index ed548ebe1..fe9646e13 100644
--- a/docs/tutorials/pt/analytics.md
+++ b/docs/tutorials/pt/analytics.md
@@ -41,9 +41,7 @@ Os dados que compõem o relatório são atualizados a cada quatro horas e contê
 * **Pedidos**: quantidades de pedidos realizados a partir da busca. Para calcular essa métrica, consideramos que a busca gera um pedido sempre que, após buscar por um termo, o cliente clica em algum produto que aparece nos resultados e depois compra um produto qualquer (não necessariamente o que ele clicou).
 * **Vendas**: valor total de receitas geradas por pedidos realizados a partir da busca. O cálculo segue a mesma lógica da métrica de **Pedidos**, a diferença é que o resultado reflete as receitas em vez da quantidade de pedidos.
 
-<div class="alert alert-info">
-  <p>Os dados exibidos no relatório são limitados aos 10 mil termos mais pesquisados. Caso deseje os dados completos da busca da sua loja, é necessário <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacao">exportar o relatório</a>.</p>
-</div>
+>ℹ️ Os dados exibidos no relatório são limitados aos 10 mil termos mais pesquisados. Caso deseje os dados completos da busca da sua loja, é necessário [exportar o relatório](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3JcuptYAkwr1GLZEM3IQ2m#exportacao).
 
 Quando você optar por [exportar um relatório](#exportacao), existe também a possibilidade de gerá-lo **Com métricas de funil**. Caso essa opção seja selecionada, quatro novas colunas serão adicionadas ao arquivo:
 
diff --git a/docs/tutorials/pt/antifraud-provider.md b/docs/tutorials/pt/antifraud-provider.md
index 1aff25212..caf758c01 100644
--- a/docs/tutorials/pt/antifraud-provider.md
+++ b/docs/tutorials/pt/antifraud-provider.md
@@ -142,9 +142,7 @@ Essas chaves devem ser disponibilizadas por você e vão servir para identificar
 ## Campo de documento do titular do cartão
 Durante o processo de análise das transações de pagamento, alguns provedores de antifraude podem optar por não utilizar informações adicionais como: a identificação pessoal do titular do cartão. Nestes casos, o lojista tem a autonomia para decidir se irá solicitar ou não esta informação do seu cliente durante o procedimento de checkout.
 
-<div class="alert alert-warning">
-  A opção de configuração <b>Campo de documento do titular do cartão</b> somente será disponibilizada ao lojista, caso o provedor de antifraude declare no seu <a href="https://developers.vtex.com/vtex-rest-api/reference/manifest">manifesto</a> o campo do documento do titular do cartão (<code>cardholderDocument</code>) como <code>optional</code>. Saiba mais em <a href="https://developers.vtex.com/vtex-rest-api/docs/cardholder-document-configuration">Cardholder Document Configuration</a>.
-  </div>
+>⚠️ A opção de configuração **Campo de documento do titular do cartão** somente será disponibilizada ao lojista, caso o provedor de antifraude declare no seu [manifesto](https://developers.vtex.com/vtex-rest-api/reference/manifest) o campo do documento do titular do cartão (`cardholderDocument`) como `optional`. Saiba mais em [Cardholder Document Configuration](https://developers.vtex.com/vtex-rest-api/docs/cardholder-document-configuration).
 
 Para configurar a exibição do campo de documento do titular do cartão, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/application-keys.md b/docs/tutorials/pt/application-keys.md
index 290a78422..1da17b1d3 100644
--- a/docs/tutorials/pt/application-keys.md
+++ b/docs/tutorials/pt/application-keys.md
@@ -33,9 +33,7 @@ As chaves de aplicação externas são credenciais geradas e administradas por o
 
 ## Gerenciar chaves de aplicação
 
-<div class="alert alert-warning">
-  <p>É necessário ter um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> com o <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <strong>Save User</strong> para gerenciar usuários e chaves de aplicação. O perfil predefinido para essa finalidade é o <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>, mas também é possível <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso">criar um perfil de acesso customizado</a> com esse recurso.</p>  
-</div>
+>⚠️ É necessário ter um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) com o [recurso](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) **Save User** para gerenciar usuários e chaves de aplicação. O perfil predefinido para essa finalidade é o [User Administrator - RESTRICTED](https://help.vtex.com/pt/tutorial/perfis-de-acesso-predefinidos--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted), mas também é possível [criar um perfil de acesso customizado](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso) com esse recurso.
 
 Na página **Chaves de aplicação**, você pode gerenciar as chaves de aplicação [internas](#chaves-de-aplicacao-internas) e [externas](#chaves-de-aplicacao-externas) que têm acesso à sua conta, inclusive:
 
@@ -76,9 +74,7 @@ Para criar chaves de aplicação internas na sua conta, siga os passos abaixo.
 4. Clique no botão `Gerar`.
 5. Clique em <img src="https://images.contentful.com/alneenqid6w5/3OX5lRYiaSEtQUDXoYJD32/6628b57d4ec1651bcb184ab31c4acd72/image1.png" alt="copy-button"/> para copiar o **Token de aplicação**. _Esse segredo será exibido apenas uma vez. Salve-o em um local seguro._
 
-<div class="alert alert-warning">
-  <p>Proteja os seus pares de chaves e tokens de aplicação do mesmo modo que faria com outras credenciais, como nomes de usuário e senhas. Se você suspeitar que uma chave de aplicação esteja comprometida, desative imediatamente a chave em sua conta. Para mais detalhes, confira a seção <a href="#ativar-ou-desativar-chaves-de-aplicacao">Ativar ou desativar chaves de aplicação</a> deste artigo.</p>
-</div>
+>⚠️ Proteja os seus pares de chaves e tokens de aplicação do mesmo modo que faria com outras credenciais, como nomes de usuário e senhas. Se você suspeitar que uma chave de aplicação esteja comprometida, desative imediatamente a chave em sua conta. Para mais detalhes, confira a seção [Ativar ou desativar chaves de aplicação](#ativar-ou-desativar-chaves-de-aplicacao) deste artigo.
 
 ## Adicionar chaves de aplicação externas
 
@@ -94,9 +90,7 @@ Para adicionar chaves de aplicação de terceiros, siga os passos abaixo:
 
 Para que uma chave de aplicação faça solicitações de API à sua conta com sucesso, ela precisa estar ativa e ter [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) especificando os recursos da conta que tem permissão para acessar. 
 
-<div class="alert alert-danger">
-<p>O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas por vazamento de credenciais de login.</p>
-</div>
+>❗ O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas por vazamento de credenciais de login.
 
 As chaves de aplicação são criadas, por padrão, sem permissão de acesso a quaisquer recursos da conta.
 
@@ -122,17 +116,13 @@ Estes são os campos visíveis na página **Chaves de aplicação**:
 - **Conta:** conta VTEX responsável por gerenciar a chave de aplicação.
 - **Status:** estado atual da chave de aplicação, que pode estar ativa ou inativa.
 
-<div class="alert alert-info">
-  <p>Observe que o campo <strong>Rótulo</strong> não é exibido na página <strong>Chaves de aplicação</strong>. Para ver a descrição da finalidade de uma chave de aplicação interna, use o valor da <strong>Chave</strong> e busque por ela na página <strong>Minhas chaves</strong>. Não é possível adicionar rótulos a chaves de aplicação externas.</p>
-</div>
+>ℹ️ Observe que o campo **Rótulo** não é exibido na página **Chaves de aplicação**. Para ver a descrição da finalidade de uma chave de aplicação interna, use o valor da **Chave** e busque por ela na página **Minhas chaves**. Não é possível adicionar rótulos a chaves de aplicação externas.
 
 ## Ativar ou desativar chaves de aplicação
 
 Se uma chave de aplicação que tenha acesso à sua conta for comprometida, você deve revogar imediatamente o acesso dela à sua conta. Caso cometa algum erro, é possível reabilitá-la para restabelecer a integração impactada. O modo como você fará isso dependerá do [tipo de chave de aplicação](#tipos-de-chaves-de-aplicacao).
 
-<div class="alert alert-warning">
-  <p>Apenas reative a chave de aplicação se tiver certeza de que ela não foi comprometida. Qualquer pessoa com o token de aplicação associado recuperará o acesso privilegiado à sua conta.</p>
-</div>
+>⚠️ Apenas reative a chave de aplicação se tiver certeza de que ela não foi comprometida. Qualquer pessoa com o token de aplicação associado recuperará o acesso privilegiado à sua conta.
 
 ### Desativar chave de aplicação interna
 
diff --git a/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md b/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
index 3cb3e73bd..2c1ccc4ec 100644
--- a/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
+++ b/docs/tutorials/pt/approving-payment-of-the-bank-payment-slip.md
@@ -29,13 +29,9 @@ Essa aprovação pode ser feita manualmente no módulo Pedidos, conforme abaixo.
 
 **Após a aprovação do pagamento, o pedido entrará no fluxo normal de compra.**
 
-<div class="alert alert-info">
-No módulo de Gerenciamento da Conta, o usuário precisa ter um perfil de acesso que inclua a permissão <code>Notify payment</code> para ser capaz de aprovar pagamentos.
-</div>
+>ℹ️ No módulo de Gerenciamento da Conta, o usuário precisa ter um perfil de acesso que inclua a permissão `Notify payment` para ser capaz de aprovar pagamentos.
 
 Para aprovar o pagamento por API, veja a [documentação da chamada de notificação de pagamento](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/payments/-paymentId-/payment-notification).
 
-<div class="alert alert-warning">
-Como <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integrações com ERPs</a> são regidas pelo <a href="https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#">fluxo de pedidos</a>, a aprovação manual de um pagamento dará continuidade à integração deste pedido com o back office da loja normalmente. Portanto recomenda-se cautela ao aprovar pagamentos manualmente, de modo a garantir o recebimento por cada pedido que é processado e enviado.
-</div>
+>⚠️ Como [integrações com ERPs](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) são regidas pelo [fluxo de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#), a aprovação manual de um pagamento dará continuidade à integração deste pedido com o back office da loja normalmente. Portanto recomenda-se cautela ao aprovar pagamentos manualmente, de modo a garantir o recebimento por cada pedido que é processado e enviado.
 
diff --git a/docs/tutorials/pt/apps-overview.md b/docs/tutorials/pt/apps-overview.md
index f66d35b0f..176e1f900 100644
--- a/docs/tutorials/pt/apps-overview.md
+++ b/docs/tutorials/pt/apps-overview.md
@@ -28,9 +28,7 @@ Um aplicativo VTEX amplia as funcionalidades da plataforma VTEX, ajudando os com
 
 Nossa solução Plug and Play permite que desenvolvedores externos criem aplicativos para o ecossistema VTEX de várias formas. Os aplicativos próprios e de terceiros estão disponíveis para download na [VTEX App Store](https://apps.vtex.com/), e podem ser gratuitos ou pagos. 
 
-<div class="alert alert-info">
-Se você é uma pessoa desenvolvedora, acesse nosso <a href = "https://developers.vtex.com">Developer Portal</a> para mais informações sobre como construir seus próprios apps na VTEX.
-  </div>
+>ℹ️ Se você é uma pessoa desenvolvedora, acesse nosso <a href = "https://developers.vtex.com">Developer Portal</a> para mais informações sobre como construir seus próprios apps na VTEX.
 
 O menu Aplicativos permite que os comerciantes baixem novos aplicativos diretamente da App Store e gerenciem os aplicativos instalados sem sair do Admin VTEX. Observe que o menu Aplicativos é flexível e pode incluir seções personalizadas relacionadas aos aplicativos instalados na sua conta.
 
diff --git a/docs/tutorials/pt/assembly-options-app.md b/docs/tutorials/pt/assembly-options-app.md
index 06964b494..28ee30134 100644
--- a/docs/tutorials/pt/assembly-options-app.md
+++ b/docs/tutorials/pt/assembly-options-app.md
@@ -15,9 +15,7 @@ legacySlug: app-assembly-options
 subcategory: 3xpuy7xGlzKKg6vxqiExZ2
 ---
 
-<div class="alert alert-warning">
-<p>Este aplicativo está disponível apenas para lojas que utilizam <a href="https://vtex.com/br-pt/store-framework/">VTEX IO</a>. Antes de prosseguir, você deve <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer">instalar e configurar o Product Customizer</a> na sua loja.</p>
-</div>
+>⚠️ Este aplicativo está disponível apenas para lojas que utilizam [VTEX IO](https://vtex.com/br-pt/store-framework/). Antes de prosseguir, você deve [instalar e configurar o Product Customizer](https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer) na sua loja.
 
 Na VTEX, é possível disponibilizar opções de customização de produtos utilizando [Assembly Options](https://help.vtex.com/pt/tutorial/assembly-options--5x5FhNr4f5RUGDEGWzV1nH). Essa solução consiste em criar [anexos](https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm) para cenários complexos, em que é necessário gerenciar diferentes combinações de produtos, quantidades, itens adicionais e custos.
 
@@ -27,9 +25,7 @@ O [app Assembly Options](https://apps.vtex.com/vtex-admin-assembly-options/p) di
 
 Você pode instalar o aplicativo gratuitamente pela [VTEX App Store](https://apps.vtex.com/vtex-admin-assembly-options/p) ou pelo [VTEX IO CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference), seguindo os passos do [guia para desenvolvedores Assembly Options](https://developers.vtex.com/vtex-developer-docs/docs/assembly-options-app).
 
-<div class="alert alert-warning">
-<p>Quando o aplicativo Assembly Options é instalado em uma <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w">conta de seller</a>, as opções de customização do produto são exibidas para os clientes da sua loja no checkout. Para que as opções sejam exibidas na página do produto, você precisa instalar o aplicativo em uma <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8">conta de marketplace</a>.</p>
-</div>
+>⚠️ Quando o aplicativo Assembly Options é instalado em uma [conta de seller](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w), as opções de customização do produto são exibidas para os clientes da sua loja no checkout. Para que as opções sejam exibidas na página do produto, você precisa instalar o aplicativo em uma [conta de marketplace](https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8).
 
 Após a instalação, a página **Catálogo > Assembly Options** se torna disponível no Admin VTEX. Veja a seguir as funcionalidades disponíveis uma vez que o aplicativo é instalado.
 
@@ -83,9 +79,7 @@ A página **Produtos > Assembly options > Novas Assembly options** contém um fo
 
 Ao salvar a Assembly Option, um anexo é criado automaticamente em **Catálogo > Anexos**, com o prefixo `vtex.assembly-option.` adicionado ao nome da Assembly Option criada. Exemplo: `vtex.assembly-option.Ingredientes`.
 
-<div class="alert alert-warning">
-<p>Para que as opções de customização cadastradas na Assembly Option apareçam no storefront, é necessário associar o anexo criado a um SKU em<em> <strong>Catálogo > Produtos e SKUs > SKU > Configurações Avançadas > Anexos</strong></em>. Para isso, siga os passos descritos em <a href="https://help.vtex.com/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU#associar-o-anexo-a-um-sku">Associar o anexo a um SKU</a>.</p>
-</div>
+>⚠️ Para que as opções de customização cadastradas na Assembly Option apareçam no storefront, é necessário associar o anexo criado a um SKU em* **Catálogo > Produtos e SKUs > SKU > Configurações Avançadas > Anexos***. Para isso, siga os passos descritos em [Associar o anexo a um SKU](https://help.vtex.com/pt/tutorial/cadastrar-um-anexo--7zHMUpuoQE4cAskqEUWScU#associar-o-anexo-a-um-sku).
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/assembly-options.md b/docs/tutorials/pt/assembly-options.md
index eee80ef6f..909d5f692 100644
--- a/docs/tutorials/pt/assembly-options.md
+++ b/docs/tutorials/pt/assembly-options.md
@@ -15,9 +15,7 @@ legacySlug: assembly-options-pt
 subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 ---
 
-<div class="alert alert-warning">
-  <p>Esta funcionalidade está disponível apenas para lojas desenvolvidas usando <a href="https://vtex.com/br-pt/store-framework/">VTEX IO</a>. Antes de prosseguir, você deve <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer">instalar e configurar o Product Customizer</a> na sua loja.</p>
-</div>
+>⚠️ Esta funcionalidade está disponível apenas para lojas desenvolvidas usando [VTEX IO](https://vtex.com/br-pt/store-framework/). Antes de prosseguir, você deve [instalar e configurar o Product Customizer](https://developers.vtex.com/vtex-developer-docs/docs/vtex-product-customizer) na sua loja.
 
 Uma Assembly Option é um [anexo](https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm) para cenários complexos, como a customização de produtos, em que é necessário gerenciar diferentes combinações de produtos, quantidade, itens adicionais, custos e estoque.
 
@@ -33,9 +31,7 @@ Neste artigo, explicamos como começar a utilizar Assembly Options na sua loja.
 
 Existem duas formas de implementar Assembly Options: utilizando o [app Assembly Options](#app-assembly-options) ou utilizando a interface nativa de [Campos personalizados](#campos-personalizados) do Catálogo.
 
-<div class="alert alert-warning">
-  <p>Ao implementar Assembly Options em uma <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w">conta de seller</a>, as opções de customização do produto são exibidas para os clientes da sua loja no checkout. Para que as opções sejam exibidas na página do produto, você precisa implementar a funcionalidade em uma <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8">conta de marketplace</a>.</p>
-</div>
+>⚠️ Ao implementar Assembly Options em uma [conta de seller](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w), as opções de customização do produto são exibidas para os clientes da sua loja no checkout. Para que as opções sejam exibidas na página do produto, você precisa implementar a funcionalidade em uma [conta de marketplace](https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8).
 
 ### App Assembly Options
 
diff --git a/docs/tutorials/pt/audit.md b/docs/tutorials/pt/audit.md
index 7ccc82dd7..1867c00e7 100644
--- a/docs/tutorials/pt/audit.md
+++ b/docs/tutorials/pt/audit.md
@@ -22,9 +22,7 @@ Para acessar a página do Audit no Admin VTEX, acesse **Apps > Apps instalados >
 * [Buscar eventos no Audit](#buscar-eventos-no-audit)
 * [Verificar últimas buscas realizadas no Audit](#verificar-ultimas-buscas-realizadas-no-audit)
 
-<div class="alert alert-info">
-  <p>Para visualizar os eventos do Audit, é necessário ter um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> associado ao <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recurso</a> <em>Insights Metrics</em>.</p>
-</div>
+>ℹ️ Para visualizar os eventos do Audit, é necessário ter um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) associado ao [recurso](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) *Insights Metrics*.
 
 ![audit-ui-pt 1](https://images.ctfassets.net/alneenqid6w5/5IFUH95vspIgJVYg9CrWMW/42032a1aa1700f58ffaf92b1e00ecfd2/audit-ui-pt_1.png)
 
diff --git a/docs/tutorials/pt/authentication-page.md b/docs/tutorials/pt/authentication-page.md
index 13d45cf25..c95be4e6c 100644
--- a/docs/tutorials/pt/authentication-page.md
+++ b/docs/tutorials/pt/authentication-page.md
@@ -35,9 +35,7 @@ Atualmente, há quatro formas disponíveis de fazer login:
 | Facebook         | Pode ser habilitada | Não está disponível    |
 | Google           | Pode ser habilitada | É selecionável         |
 
-<div class="alert alert-info">
-Pelo menos uma das quatro formas de login deve estar habilitada para a loja virtual
-</div>
+>ℹ️ Pelo menos uma das quatro formas de login deve estar habilitada para a loja virtual
 
 ## Loja virtual
 
diff --git a/docs/tutorials/pt/authentication-with-user-and-password-on-the-rest-interface.md b/docs/tutorials/pt/authentication-with-user-and-password-on-the-rest-interface.md
index b76744269..7e1241d5d 100644
--- a/docs/tutorials/pt/authentication-with-user-and-password-on-the-rest-interface.md
+++ b/docs/tutorials/pt/authentication-with-user-and-password-on-the-rest-interface.md
@@ -15,6 +15,4 @@ legacySlug: autenticando-com-usuario-e-senha-na-interface-rest-2
 subcategory: 54gbzsku02c4bKmgFbp3v3
 ---
 
-<div class="alert alert-info">
-Este artigo foi descontinuado. Para se autenticar e integrar com as APIs da VTEX, acesse nosso artigo <a href="http://help.vtex.com/pt/tutorial/chaves-de-aplicacao">Chaves de aplicação</a>.
-</div>
+>ℹ️ Este artigo foi descontinuado. Para se autenticar e integrar com as APIs da VTEX, acesse nosso artigo [Chaves de aplicação](http://help.vtex.com/pt/tutorial/chaves-de-aplicacao).
diff --git a/docs/tutorials/pt/authentication.md b/docs/tutorials/pt/authentication.md
index 515bd7de7..7047c5226 100644
--- a/docs/tutorials/pt/authentication.md
+++ b/docs/tutorials/pt/authentication.md
@@ -35,13 +35,9 @@ Na VTEX, a autenticação por login ocorre em dois contextos: na loja virtual, q
 | Google | O usuário faz login usando sua conta do Google. Confira o guia [Configurar login com Facebook e Google](https://help.vtex.com/pt/tutorial/configurar-login-com-facebook-e-google--tutorials_513) para mais detalhes. | Pode ser habilitada | Pode ser habilitada |
 | Integração com outros provedores de identidades | O usuário pode fazer login usando sua conta de outros provedores de identidades externos, a partir de uma integração. Confira o guia para desenvolvedores [Login (SSO)](https://developers.vtex.com/docs/guides/login-integration-guide) para mais detalhes. | Pode ser habilitada, utilizando o protocolo OAuth.  Confira o guia para desenvolvedores [Webstore (OAuth 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-webstore-oauth2) para mais detalhes. | Pode ser habilitada, utilizando o protocolo SAML. Confira o guia para desenvolvedores [Admin (SAML 2.0)](https://developers.vtex.com/docs/guides/login-integration-guide-admin-saml2) para mais detalhes. |
 
-<div class="alert alert-info">
-  <p>Pelo menos uma das formas de login da tabela acima deve estar habilitada para a loja virtual.</p>
-</div>
+>ℹ️ Pelo menos uma das formas de login da tabela acima deve estar habilitada para a loja virtual.
 
-<div class="alert alert-warning">
-  <p>Para logar no Admin VTEX, é preciso ter um <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512">usuário</a> administrativo cadastrado. Os <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfis de acesso</a> relacionados ao usuário e as permissões incluídas no perfil determinam quais <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos</a> ele pode utilizar no Admin.</p>
-</div>
+>⚠️ Para logar no Admin VTEX, é preciso ter um [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) administrativo cadastrado. Os [perfis de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) relacionados ao usuário e as permissões incluídas no perfil determinam quais [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) ele pode utilizar no Admin.
 
 ### Habilitar formas de login
 
diff --git a/docs/tutorials/pt/bank-reconciliations.md b/docs/tutorials/pt/bank-reconciliations.md
index f4e53b749..f1714055f 100644
--- a/docs/tutorials/pt/bank-reconciliations.md
+++ b/docs/tutorials/pt/bank-reconciliations.md
@@ -21,9 +21,7 @@ O fluxo completo é: compra fechada com boleto no site &gt; pedido entra como Pa
 
 Conforme explicado em nosso documento [Em quanto tempo um pedido de boleto sem pagamento é cancelado?](/faq/em-quanto-tempo-um-pedido-de-boleto-sem-pagamento-e-cancelado/), existe um prazo para o cancelamento do pedido, caso este não seja notificado como pago no status de Pagamento Aprovado (seja manualmente no OMS ou por conciliação bancária). Nesse caso, o pedido permanecerá no status de Pagamento Pendente até ser cancelado.
 
-<div class="alert alert-warning">
-Os procedimentos deste artigo não são aplicáveis para as integrações que realizam a conciliação bancária de forma automática.
-</div>
+>⚠️ Os procedimentos deste artigo não são aplicáveis para as integrações que realizam a conciliação bancária de forma automática.
 
 ## Como fazer o upload
 
diff --git a/docs/tutorials/pt/become-a-certified-connector-partner.md b/docs/tutorials/pt/become-a-certified-connector-partner.md
index f183fcd20..e4f4ab78b 100644
--- a/docs/tutorials/pt/become-a-certified-connector-partner.md
+++ b/docs/tutorials/pt/become-a-certified-connector-partner.md
@@ -17,8 +17,7 @@ subcategory: 6riYYNZCpO8wyksi8Ksgyq
 
 O ecossistema VTEX oferece inúmeras oportunidades de crescimento. Visando ampliar sua rede de colaboração, a VTEX desenvolveu um plano comercial para marketplaces externos que queiram se tornar parceiros.
 
-<div class="alert alert-info">
-Ao aderir ao plano comercial, um marketplace obtém uma certificação e passa a ser chamado de conector certificado. Veja mais em <a href="https://vtex.com/br-pt/partner/">plano comercial</a>.</div>
+>ℹ️ Ao aderir ao plano comercial, um marketplace obtém uma certificação e passa a ser chamado de conector certificado. Veja mais em [plano comercial](https://vtex.com/br-pt/partner/).
 
 Além de disponibilizarmos um conjunto de APIs e instruções para facilitar o processo de integração com parceiros, uma de nossas equipes também acompanha o desenvolvimento e homologação do conector. Ou seja, a VTEX verifica se está sendo feito um uso adequado das funcionalidades para que a integração aconteça corretamente.
 
diff --git a/docs/tutorials/pt/best-practices-against-virtual-attacks.md b/docs/tutorials/pt/best-practices-against-virtual-attacks.md
index 47edd3e57..2f76e953b 100644
--- a/docs/tutorials/pt/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/pt/best-practices-against-virtual-attacks.md
@@ -33,9 +33,7 @@ Sistemas antifraude são especializados em analisar compras de ecommerces com o
 
 Saiba mais sobre [sistemas antifraude](https://help.vtex.com/pt/tutorial/what-is-anti-fraud) e como utilizá-los na VTEX.
 
-<div class="alert alert-warning"> 
-  <p>Para aumentar a segurança, configure seu antifraude para todos os métodos de pagamento disponíveis na sua loja.</p>
-</div>
+>⚠️ Para aumentar a segurança, configure seu antifraude para todos os métodos de pagamento disponíveis na sua loja.
 
 ## Proteção contra ataques de transações
 
diff --git a/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md b/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md
index 87465342e..b5bceef0f 100644
--- a/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md
+++ b/docs/tutorials/pt/best-practices-for-accessing-the-store-without-www.md
@@ -68,6 +68,4 @@ Alguns provedores de DNS, como o [Cloudflare](https://www.cloudflare.com/pt-br/)
 
 Portanto, se você deseja usar um domínio puro com um CDN em uma configuração específica, a primeira etapa é verificar se o seu provedor de DNS suporta o CNAME Flattening. Se sim, você poderá configurar o domínio puro dessa forma.
 
-<div class="alert alert-warning">
-  <p>Quando utilizada, a solução de DNS Flattening implica o mesmo comportamento de um <a href="https://help.vtex.com/pt/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir">proxy-reverso</a>. Nesse caso, é necessário configurar uma entrada TXT de verificação.</p>
-</div>
+>⚠️ Quando utilizada, a solução de DNS Flattening implica o mesmo comportamento de um [proxy-reverso](https://help.vtex.com/pt/tutorial/por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-servicos-da--4PFWsfRAKviNVPf1bYdiir). Nesse caso, é necessário configurar uma entrada TXT de verificação.
diff --git a/docs/tutorials/pt/billing-module-overview.md b/docs/tutorials/pt/billing-module-overview.md
index 72bf0c224..15ed7c62c 100644
--- a/docs/tutorials/pt/billing-module-overview.md
+++ b/docs/tutorials/pt/billing-module-overview.md
@@ -19,9 +19,7 @@ subcategory:
 
 Para acessar essa página, clique no seu **avatar**, que pode ser identificado pela inicial do seu email, e clique no botão **Faturas**. Selecione a aba que você deseja visitar, como **Contratos, Títulos, Dados de registro e Contatos de faturamento**.
 
-<div class="alert alert-info">
-Somente usuários com o perfil de acesso <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance">Finance</a>, <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access">Finance Full Access</a> ou com recursos de <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy">Billing</a> vinculados ao seu perfil de acesso terão acesso a essa seção do Admin VTEX.
-            </div>
+>ℹ️ Somente usuários com o perfil de acesso [Finance](https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance), [Finance Full Access](https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#finance-full-access) ou com recursos de [Billing](https://help.vtex.com/pt/tutorial/recursos-do-license-manager-billing--13qKy6rwf9chc8ta90rDcy) vinculados ao seu perfil de acesso terão acesso a essa seção do Admin VTEX.
 
 ![Admin v4 Faturas menu PT](https://images.ctfassets.net/alneenqid6w5/6EzhdPvM8Foexk2GJUZ3KA/3102e348f966683a32c36512bdf2ba16/Admin_v4_Faturas_menu_PT.jpg)
 
diff --git a/docs/tutorials/pt/black-week.md b/docs/tutorials/pt/black-week.md
index f8b6626f0..b94d2da86 100644
--- a/docs/tutorials/pt/black-week.md
+++ b/docs/tutorials/pt/black-week.md
@@ -17,9 +17,7 @@ subcategory: QPnz120TdtLcXSh65c4Gs
 
 # Black Week (Beta)
 
-<div class="alert alert-warning">
-O painel Black Week é uma página temporária, e só estará disponível durante a Black Week dos dias 21 a 27 de novembro de 2022, exclusivamente para clientes no Brasil.
-</div>
+>⚠️ O painel Black Week é uma página temporária, e só estará disponível durante a Black Week dos dias 21 a 27 de novembro de 2022, exclusivamente para clientes no Brasil.
 
 A black week é uma das semanas mais importantes para a VTEX e para nossos clientes, dado que uma parte considerável da receita do varejo vem das estratégias de promoção durante esse período. A tomada rápida de decisões e análise em tempo real dos resultados são essenciai para o sucesso da black week. 
 
@@ -63,9 +61,7 @@ Os gráficos da página incluem as seguintes métricas:
 
 Não captamos dados de navegação para storefronts que não são VTEX, ou de sellers que somente anunciam produtos em marketplaces externos. Por isso os tipos de gráficos presentes na Black Week podem variar, dependendo se captamos dados de navegação da sua loja ou não.
 
-<div class="alert alert-info">
-  É possível que exista uma diferença de até 3% entre o número de pedidos no OMS e na página Black Week, já que o painel é em tempo real.  
-  </div>
+>ℹ️ É possível que exista uma diferença de até 3% entre o número de pedidos no OMS e na página Black Week, já que o painel é em tempo real.
 
 ### Selecionar anos
 
diff --git a/docs/tutorials/pt/brand-registration-fields.md b/docs/tutorials/pt/brand-registration-fields.md
index 65eeea8e5..150da2c76 100644
--- a/docs/tutorials/pt/brand-registration-fields.md
+++ b/docs/tutorials/pt/brand-registration-fields.md
@@ -19,15 +19,16 @@ Para entender melhor o significado dos campos de cadastro de Marca, veja abaixo
 
 - __Nome__: nome da marca que deseja cadastrar para identificação num produto. Esse campo é obrigatório e deve respeitar o limite de 150 caracteres.
 
-<div class="alert alert-danger">
-  <p>Ao preencher o <b>Nome</b> da marca, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Ao preencher o **Nome** da marca, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 - __Palavras Substitutas__: termos alternativos que levam à marca cadastrada. O objetivo é facilitar o usuário a encontrar a marca, mesmo que escreva de diferentes formas. Normalmente essas palavras são diferenças ou erros ortográficos e/ou formas genéricas e estrangeiras de chamar a marca.   
 
diff --git a/docs/tutorials/pt/campaign-audiences-list.md b/docs/tutorials/pt/campaign-audiences-list.md
index 4cb14ba63..b55b16d3a 100644
--- a/docs/tutorials/pt/campaign-audiences-list.md
+++ b/docs/tutorials/pt/campaign-audiences-list.md
@@ -31,9 +31,7 @@ A partir desta página, você pode realizar as seguintes ações:
 
 Para criar uma Audiência de campanha, em *Promoções > Audiências de campanhas*, você precisa clicar no botão `Nova Audiência de campanha` e seguir os passos descritos no artigo [Criar Audiência de campanha](https://help.vtex.com/pt/tutorial/criar-audiencia-de-campanhas--6cnuDZJzIkIeocewAQQK4K).
 
-<div class="alert alert-warning">
-  <p>Após a criação da audiência de campanha, é preciso associá-la a uma <a href="https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume">Promoção de campanha</a> para que ela tenha efeito.</p>
-</div>
+>⚠️ Após a criação da audiência de campanha, é preciso associá-la a uma [Promoção de campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume) para que ela tenha efeito.
 
 ### Visualizar audiências de campanha
 
diff --git a/docs/tutorials/pt/campaign-promotion.md b/docs/tutorials/pt/campaign-promotion.md
index 9d0aeddcd..f4e37d98e 100644
--- a/docs/tutorials/pt/campaign-promotion.md
+++ b/docs/tutorials/pt/campaign-promotion.md
@@ -26,9 +26,7 @@ Antes de criar uma promoção de campanha, você precisa criar uma audiência de
 
 Exemplo: se você configurar uma [audiência de campanha](https://help.vtex.com/pt/tutorial/criar-audiencia-de-campanhas--6cnuDZJzIkIeocewAQQK4K) cujo público alvo é de clientes que colocam o produto A no carrinho, na promoção de campanha você pode configurar que esse público vai receber um desconto sobre o produto B.
 
-<div class="alert alert-info">
-  <p>Audiências de campanha e suas promoções são válidas apenas para a conta principal da loja. Contas de sellers não apresentam essa opção. Caso sejam criadas em uma conta de sellers, a audiência de campanha ou a promoção de campanha não serão ativadas.</p>
-</div>
+>ℹ️ Audiências de campanha e suas promoções são válidas apenas para a conta principal da loja. Contas de sellers não apresentam essa opção. Caso sejam criadas em uma conta de sellers, a audiência de campanha ou a promoção de campanha não serão ativadas.
 
 Uma vez definida a [audiência de campanha](https://help.vtex.com/pt/tutorial/criar-audiencia-de-campanhas--6cnuDZJzIkIeocewAQQK4K), acesse o Admin e siga os passos abaixo para criar uma promoção de campanha.
 
@@ -136,9 +134,7 @@ Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção to
 
 Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
 
-<div class="alert alert-warning">
-  <p>Se você selecionar <b>Aplicar aos seguintes produtos</b> e não preencher nenhum dos critérios de seleção, a promoção não será cadastrada e a mensagem <b>Defina os produtos elegíveis ou aplique a todos os produtos</b> será exibida. Nesse caso, você deve retornar e preencher os critérios de seleção ou optar por <b>Aplicar a todos os produtos</b>.</p>
-</div>
+>⚠️ Se você selecionar **Aplicar aos seguintes produtos** e não preencher nenhum dos critérios de seleção, a promoção não será cadastrada e a mensagem **Defina os produtos elegíveis ou aplique a todos os produtos** será exibida. Nesse caso, você deve retornar e preencher os critérios de seleção ou optar por **Aplicar a todos os produtos**.
 
 Para serem válidos na promoção, os produtos precisam atender a todas as condições cadastradas nesta seção.
 
diff --git a/docs/tutorials/pt/carrier-working-hours.md b/docs/tutorials/pt/carrier-working-hours.md
index 0571d6099..5e0b09634 100644
--- a/docs/tutorials/pt/carrier-working-hours.md
+++ b/docs/tutorials/pt/carrier-working-hours.md
@@ -29,9 +29,7 @@ As configurações de horário de funcionamento influenciam o cálculo do tempo
 1. Na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140), na seção **Horário de funcionamento**, clique em `Janela de envio`.
 2. Se você deseja ativar a opção `Aceitar compras fora do horário de funcionamento`, ative o toggle. Caso contrário, deixe-o desativado.
 
-  <div class="alert alert-danger">
-Para autorizar a transportadora a receber pedidos nos finais de semana, este toggle deve ser marcado como <code>Ativo</code>. Mesmo se sábados e domingos estiverem configurados como janelas válidas, a ativação do toggle é obrigatória para autorizar a transportadora a receber pedidos fora do horário de funcionamento.
-</div>
+  >❗ Para autorizar a transportadora a receber pedidos nos finais de semana, este toggle deve ser marcado como `Ativo`. Mesmo se sábados e domingos estiverem configurados como janelas válidas, a ativação do toggle é obrigatória para autorizar a transportadora a receber pedidos fora do horário de funcionamento.
 
   <div class = "alert alert-info">
 Quando esta opção está habilitada, o <a href="https://help.vtex.com/pt/tutorial/how-shipping-calculation-works--tutorials_116">cálculo de envio</a> do pedido é influenciado, e o tempo desde a realização do pedido até o horário de início de funcionamento da transportadora é somado ao tempo de envio total de envio.
diff --git a/docs/tutorials/pt/category-registration-fields.md b/docs/tutorials/pt/category-registration-fields.md
index 8a3406496..df8e64dbc 100644
--- a/docs/tutorials/pt/category-registration-fields.md
+++ b/docs/tutorials/pt/category-registration-fields.md
@@ -19,15 +19,16 @@ Para entender melhor o significado de cada campo do cadastro de categoria, veja
 
 - __Nome:__ relacionado ao departamento ou categoria que estiver cadastrando. Use palavras simples e evite outros idiomas ou escrita complexa. Esse campo é importante para SEO e deve respeitar o limite de 150 caracteres.
 
-  <div class="alert alert-danger">
-    <p>Ao preencher o <b>Nome</b> da categoria, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-    <ul>
-      <li><code>a</code></li>
-      <li><code>meta</code></li>
-      <li><code>api</code></li>
-      <li><code>admin</code></li>
-    </ul></p>
-  </div>
+  >❗ Ao preencher o **Nome** da categoria, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> * `a`
+>
+> * `meta`
+>
+> * `api`
+>
+> * `admin`
+>     
 
 - __Palavras Substitutas:__ sinônimos de termos relacionados ao nome dado para seu departamento ou categoria. "Televisão", por exemplo, pode ter como palavra substituta, "TV" ou "Tevê".  Esse campo é importante para tornar suas buscas mais abrangentes e deve respeitar o limite de 200 caracteres.
 - __Título da Página da Categoria (Tag Title):__ texto que fica na aba do navegador e corresponde ao título da página da categoria, importante para motores de busca (SEO). Este campo suporta apenas texto simples e não pode conter tags HTML.
diff --git a/docs/tutorials/pt/category-variations-and-attributes-mapping.md b/docs/tutorials/pt/category-variations-and-attributes-mapping.md
index 50fc63670..d6b113c3e 100644
--- a/docs/tutorials/pt/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/pt/category-variations-and-attributes-mapping.md
@@ -88,14 +88,11 @@ Dadas essas informações, continue o preenchimento da planilha seguindo as orie
 5. __MeliValue:__ nessa coluna você deve preencher valores aceitos pelo Mercado Livre, correspondentes aos valores usados no campo `VtexValue`. Na Planilha de Variações do Mercado Livre, acesse a aba corresponde ao __seu país__ e busque pelos valores aceitos para cada especificação que você preencheu na coluna `MeliEspc`.
 <br/>_`Ex:` se você preencheu o `MeliEspc` com Tamanho e o `VtexValue` com "Pequeno", verá que o valor aceito pelo Mercado Livre é "P"._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> depois que um anúncio é criado pela primeira vez, <strong>não é mais possível alterar suas variações</strong>. Caso queira fazer ajustes como mudar a cor, por exemplo, será necessário finalizar o anúncio no Mercado Livre e depois refazer o mapeamento da planilha.</div>
+>⚠️ **OBS:** depois que um anúncio é criado pela primeira vez, **não é mais possível alterar suas variações**. Caso queira fazer ajustes como mudar a cor, por exemplo, será necessário finalizar o anúncio no Mercado Livre e depois refazer o mapeamento da planilha.
 
-<div class="alert alert-warning">
-<strong>OBS 2:</strong> o Mercado Livre <strong>não permite usar preços diferentes</strong> para cada variação de um anúncio. Por exemplo, uma camisa não pode custar $ 40 para o tamanho "P" e $ 50 para o tamanho "M".</div> 
+>⚠️ **OBS 2:** o Mercado Livre **não permite usar preços diferentes** para cada variação de um anúncio. Por exemplo, uma camisa não pode custar $ 40 para o tamanho "P" e $ 50 para o tamanho "M". 
 
-<div class="alert alert-warning">
-<strong>OBS 3:</strong> caso o SKU não tenha uma certa especificação (como cor, por exemplo), você vai precisar cadastrá-la na VTEX antes de completar o processo de integração. Recomendamos que você adicione o atributo que falta como uma especificação de <strong>produto</strong>. Assim, essa informação não será exibida no site.</div>
+>⚠️ **OBS 3:** caso o SKU não tenha uma certa especificação (como cor, por exemplo), você vai precisar cadastrá-la na VTEX antes de completar o processo de integração. Recomendamos que você adicione o atributo que falta como uma especificação de **produto**. Assim, essa informação não será exibida no site.
 
 ## Atributos
 
@@ -203,6 +200,4 @@ Depois de preencher a planilha, acesse __Integrações__ no menu do Admin:
 
 Com o upload concluído, a integração envia automaticamente todos os produtos das categorias usadas na planilha para o Mercado Livre.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> os produtos só serão enviados ao Mercado Livre caso a autenticação da integração já tenha sido realizada. Se você ainda não fez isso, siga o passo a passo <a href="https://help.vtex.com/pt/tutorial/integrando-com-mercado-livre#autorizar-integracao-no-painel-da-vtex">neste artigo</a>.
-</div>
+>⚠️ **OBS:** os produtos só serão enviados ao Mercado Livre caso a autenticação da integração já tenha sido realizada. Se você ainda não fez isso, siga o passo a passo [neste artigo](https://help.vtex.com/pt/tutorial/integrando-com-mercado-livre#autorizar-integracao-no-painel-da-vtex).
diff --git a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
index d930f0e51..5bac99754 100644
--- a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -21,9 +21,7 @@ Na VTEX, as lojas podem definir manualmente o preço de um item (SKU) disponíve
 
 - **Permissão**: Shopping Cart Full Access
 
-<div class="alert alert-warning">
-  Os passos abaixo indicados devem ser realizados no domínio <i>myvtex</i> de cada loja ({accountName}.myvtex.com.br).
-</div>
+>⚠️ Os passos abaixo indicados devem ser realizados no domínio <i>myvtex</i> de cada loja ({accountName}.myvtex.com.br).
 
 ## Modificando o preço do item
 
diff --git a/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md b/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
index aef809a91..d4e548f1c 100644
--- a/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
+++ b/docs/tutorials/pt/changing-default-system-texts-displayed-in-the-store.md
@@ -47,9 +47,7 @@ Para fazer isso de maneira dinâmica, eu posso trocar o texto da chave `topbarSa
 
 Ou seja, estou usando as variáveis `preposicaonomeloja2` e `nomeloja`.
 
-<div class="alert alert-warning">
-Ao usar variáveis para compor um texto, substitua o símbolo <code>#</code> por <code>@</code>. Ou seja, <b>#variavel#</b> torna-se <b>@variavel@</b>.
-</div>
+>⚠️ Ao usar variáveis para compor um texto, substitua o símbolo `#` por `@`. Ou seja, **#variavel#** torna-se **@variavel@**.
 
 ![textos-importante pt](https://images.ctfassets.net/alneenqid6w5/6B5XvqyDYI4G4eaC8OGEUw/8e55774262373bc01757e12736fe8f39/textos_importantes_pt.png)
 
diff --git a/docs/tutorials/pt/changing-items-from-a-complete-order.md b/docs/tutorials/pt/changing-items-from-a-complete-order.md
index ad11278eb..07bf49c4c 100644
--- a/docs/tutorials/pt/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/pt/changing-items-from-a-complete-order.md
@@ -22,10 +22,8 @@ Há duas formas de realizar a alteração de um pedido:
 * [Admin VTEX:](#como-alterar) é possível se o status do pedido estiver como `Preparando entrega`.
 * [API de alteração de pedidos:](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes) é possível, além de alterar itens, criar descontos e mudar o preço do pedido. A alteração só é possível se o status do pedido na API de pedidos for `handling` ou `waiting-for-fulfillment`.
 
-<div class="alert alert-warning">
-Após a alteração, o cliente recebe uma notificação por email caso o template <code>Change of information</code> (<a href="https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">
-template de emails transacionais referentes ao pedido</a>) esteja habilitado na Central de Mensagens. O cliente recebe as mensagens com as informações que foram preenchidas no formulário de alteração de itens.
-</div>
+>⚠️ Após a alteração, o cliente recebe uma notificação por email caso o template `Change of information` (<a href="https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">
+> template de emails transacionais referentes ao pedido</a>) esteja habilitado na Central de Mensagens. O cliente recebe as mensagens com as informações que foram preenchidas no formulário de alteração de itens.
 
 ## Cuidados e limitações
 
diff --git a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
index 2f908bcb0..a74b35fcd 100644
--- a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
@@ -17,9 +17,7 @@ subcategory: 3VNOhxDrvYxJThhuJClrYZ
 
 A página de [Detalhes do pedido](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido-beta--2Y75n54Cc9VizrlG1N6ZNl) permite alterar o valor final do pedido para pedidos que ainda não foram faturados. Isso ocorre em cenários em que há descontos ou acréscimos ao valor.
 
-<div class="alert alert-warning">
-Lembre-se que a funcionalidade só fica disponível para pedidos que estão no status <code>Preparando entrega</code>.
- </div>
+>⚠️ Lembre-se que a funcionalidade só fica disponível para pedidos que estão no status `Preparando entrega`.
 
 Para fazer a alteração, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/checking-for-errors-or-problems-in-a-transaction.md b/docs/tutorials/pt/checking-for-errors-or-problems-in-a-transaction.md
index 7fb83b019..ac8134256 100644
--- a/docs/tutorials/pt/checking-for-errors-or-problems-in-a-transaction.md
+++ b/docs/tutorials/pt/checking-for-errors-or-problems-in-a-transaction.md
@@ -21,9 +21,7 @@ Os logs de uma transação ficam registrados numa linha do tempo, com as intera
 
 O gateway da VTEX pode se comunicar com adquirentes, subadquirentes, antifraudes e com outros gateways. As __mudanças de status na transação__ e as __mensagens de resposta dos parceiros__ estão exibidas em caixas na tela dos detalhes da transação.
 
-<div class="alert alert-info">
-Você pode <a href="https://help.vtex.com/pt/faq/cartao-de-credito-fluxo-basico-de-um-pagamento">clicar aqui</a> para saber como funciona o fluxo básico de uma transação de cartão de crédito. Acesse também <a href="https://help.vtex.com/pt/faq/boleto-bancario-registrado-fluxo-basico-de-um-pagamento">nosso artigo</a> com o esquema básico de uma transação via boleto bancário.
-</div>
+>ℹ️ Você pode [clicar aqui](https://help.vtex.com/pt/faq/cartao-de-credito-fluxo-basico-de-um-pagamento) para saber como funciona o fluxo básico de uma transação de cartão de crédito. Acesse também [nosso artigo](https://help.vtex.com/pt/faq/boleto-bancario-registrado-fluxo-basico-de-um-pagamento) com o esquema básico de uma transação via boleto bancário.
 
 ## Verificar status da transação
 
diff --git a/docs/tutorials/pt/checkout-vtex-overview.md b/docs/tutorials/pt/checkout-vtex-overview.md
index 87889095d..9412832ff 100644
--- a/docs/tutorials/pt/checkout-vtex-overview.md
+++ b/docs/tutorials/pt/checkout-vtex-overview.md
@@ -37,9 +37,7 @@ Sempre que o cliente realiza uma modificação no carrinho (adição ou remoçã
 
 ![Checkout overview](https://images.ctfassets.net/alneenqid6w5/6U3DBHywYW2RnlM94QQFg5/c25d968b81626de55ab890ef67834bb8/Checkout_Overview_PT.png)
 
-<div class="alert alert-info">
-Caso um ou mais itens escolhidos pelo cliente sejam elegíveis para entrega por um <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#o-que-e-um-seller-white-label">Seller white label</a>, serão realizadas simulações (conforme exibido no lado direito da figura), de modo a determinar quais sellers serão responsáveis pela entrega dos itens. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#">Seleção de sellers white label</a>.
-</div>
+>ℹ️ Caso um ou mais itens escolhidos pelo cliente sejam elegíveis para entrega por um [Seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#o-que-e-um-seller-white-label), serão realizadas simulações (conforme exibido no lado direito da figura), de modo a determinar quais sellers serão responsáveis pela entrega dos itens. Saiba mais em [Seleção de sellers white label](https://help.vtex.com/pt/tutorial/white-label-sellers-selection--3MemNQ4pKkWCpMdzI27AHa#).
 
 ## Funcionalidades do Checkout VTEX
 
@@ -55,9 +53,7 @@ Dentre as principais funcionalidades disponíveis no módulo de Checkout VTEX, p
 
 Atualmente, o módulo de Checkout VTEX possui duas versões em operação: **Checkout v5** e **Checkout v6**.
 
-<div class="alert alert-info">
-  O <b>Checkout v5</b> não recebe mais atualizações ou suporte operacional direto. Por este motivo, recomendamos a utilização do <b>Checkout v6</b> em sua loja.
-</div>
+>ℹ️ O **Checkout v5** não recebe mais atualizações ou suporte operacional direto. Por este motivo, recomendamos a utilização do **Checkout v6** em sua loja.
 
 Para maiores informações sobre configurações e APIs do Checkout, acesse o [Checkout Overview no Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/checkout-overview).
 
diff --git a/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md b/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
index 9671c4537..b5d5d921a 100644
--- a/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
+++ b/docs/tutorials/pt/choosing-between-a-multi-store-architecture-or-an-additional-environment.md
@@ -27,9 +27,7 @@ A plataforma VTEX permite a criação de arquiteturas diferentes para a sua loja
 
 Este artigo apresenta as diferenças entre arquitetura multi-loja e ambiente adicional para que você identifique qual a mais adequada para diferentes cenários. 
 
-<div class="alert alert-info">
-Para arquiteturas de marketplace, também é possível <a href="https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78"> Escolher entre Conta Franquia, Seller Portal ou Conta Padrão</a>, ou utilizar a configuração de <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4">Multilevel Omnichannel Inventory </a>. 
-</div>
+>ℹ️ Para arquiteturas de marketplace, também é possível [ Escolher entre Conta Franquia, Seller Portal ou Conta Padrão](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78), ou utilizar a configuração de [Multilevel Omnichannel Inventory ](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4).
 
 ## Comparando arquitetura multi-loja e ambiente adicional
 
diff --git a/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
index e120fb9b0..05c892087 100644
--- a/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -23,7 +23,7 @@ Na VTEX, existem três tipos de conta e cada uma permite atuar com um perfil de
 - **Conta franquia:** é criada associada a uma conta padrão, de quem ela herda o [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR), ou seja, categorias, produtos e especificações são importados para o ambiente da [conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), que não cria produtos próprios. No entanto, ela pode configurar logística, pagamento e preços próprios. A conta franquia dispõe parcialmente dos módulos da plataforma VTEX e atua como [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) da conta padrão.
 - **Seller Portal:** o [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é uma edição da plataforma VTEX que permite a sellers se conectarem e venderem produtos em marketplaces do ecossistema VTEX, independente do seller já ter ou não uma conta na VTEX. O Seller Portal permite acesso parcial aos módulos da plataforma e o seller pode ser do tipo normal ou [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa).
 
-  <div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+  >⚠️ O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.
 
 A tabela a seguir apresenta os principais cenários de uso de cada tipo de conta:
 
diff --git a/docs/tutorials/pt/cms-folder-structure.md b/docs/tutorials/pt/cms-folder-structure.md
index 5cc1ee3e6..25b5d60c3 100644
--- a/docs/tutorials/pt/cms-folder-structure.md
+++ b/docs/tutorials/pt/cms-folder-structure.md
@@ -37,9 +37,7 @@ Veja abaixo estas pastas básicas no CMS:
 
 Estas pastas vêm por padrão no ambiente de todas as lojas VTEX.
 
-<div class="alert alert-danger">
-  <p>Os nomes das pastas obrigatórias <b>não</b> devem ser editados. Isso pode comprometer o funcionamento correto da loja e impedir que compras sejam realizadas.</p>
-</div>
+>❗ Os nomes das pastas obrigatórias **não** devem ser editados. Isso pode comprometer o funcionamento correto da loja e impedir que compras sejam realizadas.
 
 Como as pastas se referem a páginas dinâmicas, seus nomes não aparecem na navegação do cliente. Ou seja, o fato de a edição dos nomes ser vetada não afeta o texto final das suas URLs nem, portanto, a internacionalização do seu site.
 
@@ -55,9 +53,7 @@ São elas:
 
 Para estas duas pastas, o que importa é o controle ou placeholder que lê o conteúdo delas. Os nomes delas podem ser livremente editados.
 
-<div class="alert alert-warning">
-Como são pastas privadas, <code>/account</code> e <code>/account/orders</code> <b>precisam requerer autenticação</b>. Veja <a href="http://help.vtex.com/pt/tutorial/exigir-autenticacao-em-paginas-da-loja">neste artigo</a> como garantir que elas estejam configuradas para pedir autenticação do usuário.
-</div>
+>⚠️ Como são pastas privadas, `/account` e `/account/orders` **precisam requerer autenticação**. Veja [neste artigo](http://help.vtex.com/pt/tutorial/exigir-autenticacao-em-paginas-da-loja) como garantir que elas estejam configuradas para pedir autenticação do usuário.
 
 ## Pastas úteis
 
diff --git a/docs/tutorials/pt/collection-highlight-control.md b/docs/tutorials/pt/collection-highlight-control.md
index 4cbc78231..e536375c1 100644
--- a/docs/tutorials/pt/collection-highlight-control.md
+++ b/docs/tutorials/pt/collection-highlight-control.md
@@ -38,6 +38,4 @@ Você pode, então, customizar o CSS para definir de que maneira a classe `flag
 
 Este recurso pode ser usado, por exemplo, para fazer com que os produtos de uma coleção chamada "Lançamento" apareçam sempre com uma flag destacando que eles são novidade na loja. Ao adicionar o controle no template da página de categoria, por exemplo, todo produto da coleção Lançamento exibido em uma página de categoria aparecerá com esse destaque.
 
-<div class="alert alert-warning">
-Lembre-se que, se a página for de produto, o controle que deve ser usado é o <code>&lt;vtex.cmc:HightLight/&gt;</code>. Já se for uma página de vitrine, você deve usar o <code>$product.HightLight</code>.
-</div>
+>⚠️ Lembre-se que, se a página for de produto, o controle que deve ser usado é o `&lt;vtex.cmc:HightLight/&gt;`. Já se for uma página de vitrine, você deve usar o `$product.HightLight`.
diff --git a/docs/tutorials/pt/como-criar-usuario-webservice.md b/docs/tutorials/pt/como-criar-usuario-webservice.md
index d4614e635..21c39e098 100644
--- a/docs/tutorials/pt/como-criar-usuario-webservice.md
+++ b/docs/tutorials/pt/como-criar-usuario-webservice.md
@@ -15,9 +15,11 @@ legacySlug: como-criar-usuario-webservice
 subcategory: 63DHe3VQEEE6Uuua8gIs2M
 ---
 
-<div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
-<p><strong>Todos os outros métodos do Web Service serão descontinuados no dia 28/02/2017.</strong></p>
-<p>Use as APIs REST equivalentes, disponíveis em nosso <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: somente os métodos SOAP pertinentes ao **catálogo** são válidos.
+>
+> **Todos os outros métodos do Web Service serão descontinuados no dia 28/02/2017.**
+>
+> Use as APIs REST equivalentes, disponíveis em nosso [Developer Docs](//help.vtex.com/developer-docs/).
 
 A criação de credenciais para integrações com o Web Service deve ser feita pelo License Manager, com a funcionalidade de appKey e appToken.
 
diff --git a/docs/tutorials/pt/como-funciona-a-integracao-da-magazine-luiza.md b/docs/tutorials/pt/como-funciona-a-integracao-da-magazine-luiza.md
index d6774d155..78960c107 100644
--- a/docs/tutorials/pt/como-funciona-a-integracao-da-magazine-luiza.md
+++ b/docs/tutorials/pt/como-funciona-a-integracao-da-magazine-luiza.md
@@ -52,11 +52,11 @@ Se o envio for realizado com sucesso, você já poderá encontrar os produtos no
 
 Caso o mapeamento tenha sido feito corretamente, todas as variações serão exibidas em um único anúncio.
 
-<div class="alert alert-info">
-Ex.: 
-<br />
-<strong>Anúncio</strong> = Forno Elétrico (produto) | 110V, 220V (variações/skus)
-</div>
+>ℹ️ Ex.: 
+>
+>
+> 
+> **Anúncio** = Forno Elétrico (produto) | 110V, 220V (variações/skus)
 
 ### Atualizações de produto
 
@@ -80,9 +80,7 @@ No caso de haver alguma especificação cadastrada apenas no lado da Magazine Lu
 
 Os estoques são enviados pela primeira vez junto com o primeiro envio de produtos. A partir daí, os estoques dos anúncios na Magazine Luiza são atualizados automaticamente, SKU por SKU, sempre que há alguma alteração de estoque na VTEX. A atualização demora apenas alguns segundos para refletir no marketplace, mas os logs de estoque podem demorar alguns minutos para aparecer no Admin da VTEX. 
 
-<div class="alert alert-info">
-Para acessar os logs, clique na seção <strong>Integrações</strong> do menu lateral do Admin. Uma lista de opções vai se abrir e, então, você deve clicar na opção <strong>Estoque</strong>. 
-</div>
+>ℹ️ Para acessar os logs, clique na seção **Integrações** do menu lateral do Admin. Uma lista de opções vai se abrir e, então, você deve clicar na opção **Estoque**.
 
 
 
@@ -92,21 +90,19 @@ Os preços são enviados pela primeira vez junto com o primeiro envio de produto
 
 Para cada SKU, a integração envia apenas o preço final, baseado no retorno da simulação de fulfillment. Normalmente, o preço enviado é sempre o que foi determinado pela política comercial associada à integração. No entanto, __Promoções__ e __Preços fixos__ podem influenciar o preço final.
 
-<div class="alert alert-info">
-<strong>Exemplo 1:</strong>
-<br />
-Uma promoção que ofereça 10% de desconto para uma determinada categoria.
-</div>
-
-<div class="alert alert-info">
-<strong>Exemplo 2:</strong>
-<br />
-Na política comercial usada na Magazine Luiza, um SKU tem preço de R$ 10 e um preço fixo de R$ 15. O valor que a integração envia para o marketplace é R$ 15.
-</div>
-
-<div class="alert alert-warning">
-<strong>OBS:</strong> a integração não envia preços de acordo com a forma de pagamento. Isso significa que, mesmo se estiver configurada a incidência de juros para pagamentos parcelados, o preço enviado para a Magazine Luiza vai continuar sendo o que foi retornado pela simulação de fulfillment.
-</div>
+>ℹ️ **Exemplo 1:**
+>
+>
+> 
+> Uma promoção que ofereça 10% de desconto para uma determinada categoria.
+
+>ℹ️ **Exemplo 2:**
+>
+>
+> 
+> Na política comercial usada na Magazine Luiza, um SKU tem preço de R$ 10 e um preço fixo de R$ 15. O valor que a integração envia para o marketplace é R$ 15.
+
+>⚠️ **OBS:** a integração não envia preços de acordo com a forma de pagamento. Isso significa que, mesmo se estiver configurada a incidência de juros para pagamentos parcelados, o preço enviado para a Magazine Luiza vai continuar sendo o que foi retornado pela simulação de fulfillment.
 
 
 ## 4. Promoções
diff --git a/docs/tutorials/pt/como-funciona-a-integracao-da-netshoes.md b/docs/tutorials/pt/como-funciona-a-integracao-da-netshoes.md
index a38941bbb..16ba56531 100644
--- a/docs/tutorials/pt/como-funciona-a-integracao-da-netshoes.md
+++ b/docs/tutorials/pt/como-funciona-a-integracao-da-netshoes.md
@@ -54,9 +54,7 @@ Ao serem enviados com sucesso pela primeira vez, a Netshoes recebe os produtos e
 
 _`Ex:` se a descrição do produto for alterada, a integração não atualizará a descrição que está no marketplace._
 
-<div class="alert alert-warning">
-OBS: o produto não pode ser apagado no painel da Netshoes, do contrário não conseguirá ser enviado pela integração novamente.
-</div>
+>⚠️ OBS: o produto não pode ser apagado no painel da Netshoes, do contrário não conseguirá ser enviado pela integração novamente.
 
 Na Netshoes, os produtos possuem dois status possíveis:
 - __Ativo:__ disponível para venda
@@ -74,9 +72,7 @@ A Netshoes só aceita receber os estoques para produtos que já foram enviados c
 
 Depois que os produtos recebem a primeira carga de estoque, a atualização é feita SKU por SKU sempre que ocorre alguma alteração de estoque na VTEX.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> os dados de estoque enviados para a Netshoes ficam registrados em nosso sistema por apenas <strong>3 meses</strong>. 
-</div>
+>⚠️ **OBS:** os dados de estoque enviados para a Netshoes ficam registrados em nosso sistema por apenas **3 meses**.
 
 ## Preços
 
@@ -90,11 +86,11 @@ _`Ex1:` promoção de 10% de desconto para determinada categoria_
 
 _`Ex2:` SKU X está R$ 10,00 na política comercial usada na Netshoes e tem um preço fixo de R$ 15,00 para essa mesma política. A integração enviará R$ 15,00._
 
-<div class="alert alert-warning">
-OBS: como a forma de pagamento é feita no marketplace, as regras de pagamento são determinadas por ele. Por conta disto, não conseguimos enviar preços diferenciados em função da forma de pagamento.
-<br />
-<em>Ex: se na VTEX existem juros configurados para pagamentos parcelados, o preço enviado continuará sendo o que a simulação de fulfillment retorna.</em>
-</div>
+>⚠️ OBS: como a forma de pagamento é feita no marketplace, as regras de pagamento são determinadas por ele. Por conta disto, não conseguimos enviar preços diferenciados em função da forma de pagamento.
+>
+>
+> 
+> *Ex: se na VTEX existem juros configurados para pagamentos parcelados, o preço enviado continuará sendo o que a simulação de fulfillment retorna.*
 
 ## Promoções
 
@@ -109,9 +105,7 @@ Só são aplicadas promoções que conseguem ser calculadas na simulação de fu
 | Frete Máximo| - | Tipo de Frete |
 | Frete Grátis| - | - |
 
-<div class="alert alert-info">
-Não é possível aplicar <strong>nenhum</strong> tipo de condição nas promoções cujos campos foram preenchidos com <strong>-</strong>, isso é, nenhuma condição será contemplada na integração. 
-</div>
+>ℹ️ Não é possível aplicar **nenhum** tipo de condição nas promoções cujos campos foram preenchidos com **-**, isso é, nenhuma condição será contemplada na integração.
 
 ## Fluxo de Pedidos
 
@@ -123,15 +117,19 @@ Quando um pedido é feito no marketplace, existem alguns pontos que influenciam
 
 Nesta integração existem dois pontos que influenciarão na entrega: __Cálculo do Frete__ e o __Tempo de Preparo de Envio__. O somatório dos dois será o __Tempo de Entrega Total__.
 
-<div class="alert alert-info">
-Ex:
-<br />
-Frete Normal = 3 dias
-<br />
-Tempo de Custo = 2 dias
-<br />
-Tempo Total de Entrega = 5 dias
-</div>
+>ℹ️ Ex:
+>
+>
+> 
+> Frete Normal = 3 dias
+>
+>
+> 
+> Tempo de Custo = 2 dias
+>
+>
+> 
+> Tempo Total de Entrega = 5 dias
 
 - __Frete__
 
@@ -143,46 +141,78 @@ O lojista tem também a possibilidade de cadastrar na Netshoes uma __tabela de c
 
 O tempo de preparo de envio é baseado no somatório do  campo `Tempo de custo` no Estoque com o `Tempo de Custo` na Doca. E nós enviamos o mesmo tempo de preparo massivamente para todos os produtos.
 
-<div class="alert alert-info">
-Ex:
-<br />
-<strong>Estoque A</strong>
-<br />
-- Doca 1: Tempo de Custo = 3 dias
-<br />
-<strong>Estoque B</strong>
-<br />
-- Doca 1: Tempo de Custo = 5 dias
-<br />
-<br />
-<strong>Doca 1:</strong>
-<br />
-- Tempo de Custo = 2 dias
-<br />
-<br />
-Um pedido com Tempo de Frete = 3 dias, ficará com um Tempo Total de Entrega diferente dependendo de onde o produto sairá.
-<br />
-<br />
-<strong>Saindo do estoque A:</strong>
-<br />
-- Tempo de preparo = 3 + 2 (doca 1) = 5 dias
-<br />
-- Tempo de frete = 3 dias
-<br />
-- Tempo total de entrega = 8 dias
-<br />
-<strong>Saindo do estoque B:</strong>
-<br />
-- Tempo de preparo = 5 + 2 (doca 1) = 7 dias
-<br />
-- Tempo de frete = 3 dias
-<br />
-- Tempo total de entrega = 10 dias
-</div>
-
-<div class="alert alert-warning">
-OBS: no caso de usar a tabela de contingência para fazer o cálculo do frete, a Netshoes não consulta a VTEX. Desta forma, o único fator que será levado em consideração para o <strong>Tempo Total de Entrega</strong>, será o <strong>Frete</strong> fornecido por eles, ignorando o <strong>Tempo de Preparo</strong>. Deve-se tomar cuidado com isto, pois pode gerar divergências no <strong>Tempo Total de Entrega</strong>.
-</div>
+>ℹ️ Ex:
+>
+>
+> 
+> **Estoque A**
+>
+>
+> 
+> - Doca 1: Tempo de Custo = 3 dias
+>
+>
+> 
+> **Estoque B**
+>
+>
+> 
+> - Doca 1: Tempo de Custo = 5 dias
+>
+>
+> 
+>
+>
+> 
+> **Doca 1:**
+>
+>
+> 
+> - Tempo de Custo = 2 dias
+>
+>
+> 
+>
+>
+> 
+> Um pedido com Tempo de Frete = 3 dias, ficará com um Tempo Total de Entrega diferente dependendo de onde o produto sairá.
+>
+>
+> 
+>
+>
+> 
+> **Saindo do estoque A:**
+>
+>
+> 
+> - Tempo de preparo = 3 + 2 (doca 1) = 5 dias
+>
+>
+> 
+> - Tempo de frete = 3 dias
+>
+>
+> 
+> - Tempo total de entrega = 8 dias
+>
+>
+> 
+> **Saindo do estoque B:**
+>
+>
+> 
+> - Tempo de preparo = 5 + 2 (doca 1) = 7 dias
+>
+>
+> 
+> - Tempo de frete = 3 dias
+>
+>
+> 
+> - Tempo total de entrega = 10 dias
+
+>⚠️ OBS: no caso de usar a tabela de contingência para fazer o cálculo do frete, a Netshoes não consulta a VTEX. Desta forma, o único fator que será levado em consideração para o **Tempo Total de Entrega**, será o **Frete** fornecido por eles, ignorando o **Tempo de Preparo**. Deve-se tomar cuidado com isto, pois pode gerar divergências no **Tempo Total de Entrega**.
 
 #### Preço/Disponibilidade:
 
diff --git a/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md b/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
index 9766f67cd..d3b621e48 100644
--- a/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
+++ b/docs/tutorials/pt/como-saber-qual-pagina-do-sistema-esta-sendo-renderizada-no-site.md
@@ -31,8 +31,6 @@ Veja abaixo a relação entre a pasta no CMS e o código-fonte da loja.
 
 ![CommerceContext](https://images.contentful.com/alneenqid6w5/6diTrNVvl6OuwGKmoICSA0/4e958baa7ab163bcf06ac5963795feff/CommerceContext.png)
 
-<div class="alert alert-info">
-Essa linha de código está sempre comentada. Portanto, ela tem função apenas informativa. Ou seja, não realiza nenhuma ação.
-</div>
+>ℹ️ Essa linha de código está sempre comentada. Portanto, ela tem função apenas informativa. Ou seja, não realiza nenhuma ação.
 
 Essa informação é útil, por exemplo, para saber qual pasta a busca da sua loja por determinado termo está retornando.
diff --git a/docs/tutorials/pt/conditions-builder-usage-examples.md b/docs/tutorials/pt/conditions-builder-usage-examples.md
index 9b578ea90..b204d546e 100644
--- a/docs/tutorials/pt/conditions-builder-usage-examples.md
+++ b/docs/tutorials/pt/conditions-builder-usage-examples.md
@@ -25,9 +25,8 @@ UTM (Marketing tag) é uma informação que diz respeito a origem do tráfego do
 
 ![utm_source_port](https://images.ctfassets.net/alneenqid6w5/1X8rOnz0wwOgMWKE2IccGe/97a3907728c129ec075f425c9e221230/utm_source_port.png)  
 
-<div class="alert alert-warning"><strong>Nota: </strong>
-É possível que sua loja utilize customização e por isso as informações de UTM contidas na URL não estão sendo passadas para o nosso sistema. Caso use customização de Javascript, leia o artigo <a href="https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho">Por que as utms não estão sendo aplicadas ao carrinho</a>
-</div>
+>⚠️ **Nota: **
+> É possível que sua loja utilize customização e por isso as informações de UTM contidas na URL não estão sendo passadas para o nosso sistema. Caso use customização de Javascript, leia o artigo [Por que as utms não estão sendo aplicadas ao carrinho](https://help.vtex.com/pt/faq/por-que-as-utms-nao-estao-sendo-aplicadas-ao-carrinho)
 
 ### utm_source
 
diff --git a/docs/tutorials/pt/conecta-la-integration.md b/docs/tutorials/pt/conecta-la-integration.md
index 27584a02b..615cd3047 100644
--- a/docs/tutorials/pt/conecta-la-integration.md
+++ b/docs/tutorials/pt/conecta-la-integration.md
@@ -22,9 +22,7 @@ Este artigo orienta sobre as etapas necessárias para integrar sua loja VTEX com
 - [Configurações na plataforma VTEX](#configuracoes-na-plataforma-vtex)
 - [Configurações na Conecta Lá](#configuracoes-na-conecta-la)
 
-<div class="alert alert-info">
-Você também pode conferir as orientações para a integração por meio do vídeo <a href="https://conectala.agidesk.com/br/central-de-ajuda/como-obter-os-dados-para-integracao">Como obter os dados para integração?</a> da Conecta Lá, ou consultar a documentação do parceiro fazendo o <a href="https://drive.google.com/uc?export=download&id=1jbKK7fR68jfH6rBNmy-gq5d1lQZ-2cBs">download Conecta La (documentacao parceiro).pdf</a>.
-</div>
+>ℹ️ Você também pode conferir as orientações para a integração por meio do vídeo [Como obter os dados para integração?](https://conectala.agidesk.com/br/central-de-ajuda/como-obter-os-dados-para-integracao) da Conecta Lá, ou consultar a documentação do parceiro fazendo o [download Conecta La (documentacao parceiro).pdf](https://drive.google.com/uc?export=download&id=1jbKK7fR68jfH6rBNmy-gq5d1lQZ-2cBs).
 
 ## Configurações na plataforma VTEX
 
@@ -44,9 +42,7 @@ A chave de integração, chamada de _access key_, é o que possibilita o fluxo d
 3. Em _Segurança_, clique em `Gerar access key e secret`.
 4. Preencha com um nome para o novo _access key_ e clique em `Gerar novos secrets`.
 
-<div class="alert alert-danger">
-O <i/>secret</i> gerado, também chamado de <i/>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
-</div>
+>❗ O <i/>secret</i> gerado, também chamado de <i/>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
 
 ### Configurar perfil de acesso
 
@@ -116,8 +112,6 @@ Uma vez concluídas as configurações na plataforma VTEX, dê continuidade à i
 
 - **Endpoint de Search:** o mesmo que foi utilizado no cadastro da etapa [Criar ID do afiliado](#criar-id-do-afiliado).
 
-<div class="alert alert-info">
-Você também pode conferir as orientações para a integração por meio do vídeo <a href="https://conectala.agidesk.com/br/central-de-ajuda/como-obter-os-dados-para-integracao">Como obter os dados para integração?</a> da Conecta Lá, ou consultar a documentação do parceiro fazendo o <a href="https://drive.google.com/uc?export=download&id=1jbKK7fR68jfH6rBNmy-gq5d1lQZ-2cBs">download Conecta La (documentacao parceiro).pdf</a>.
-</div>
+>ℹ️ Você também pode conferir as orientações para a integração por meio do vídeo [Como obter os dados para integração?](https://conectala.agidesk.com/br/central-de-ajuda/como-obter-os-dados-para-integracao) da Conecta Lá, ou consultar a documentação do parceiro fazendo o [download Conecta La (documentacao parceiro).pdf](https://drive.google.com/uc?export=download&id=1jbKK7fR68jfH6rBNmy-gq5d1lQZ-2cBs).
 
 Em caso de dúvidas, consulte a página da Conecta Lá sobre [treinamentos e perguntas frequentes](https://conectala.agidesk.com/br/central-de-ajuda).
diff --git a/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md b/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
index 2442f9388..96233bd3c 100644
--- a/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
+++ b/docs/tutorials/pt/configuration-errors-in-mercado-libre-accounts-with-multiple-official-stores.md
@@ -15,9 +15,7 @@ legacySlug: erro-de-configuracao-de-lojas-guarda-chuva
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-Caso você possua lojas oficiais no Mercado Livre, essa documentação pode ser relevante. O Mercado Livre possui parâmetros próprios para certificar sellers para serem lojas oficiais. Para mais informações, entre em contato com o seu consultor do Mercado Livre.
-</div>
+>ℹ️ Caso você possua lojas oficiais no Mercado Livre, essa documentação pode ser relevante. O Mercado Livre possui parâmetros próprios para certificar sellers para serem lojas oficiais. Para mais informações, entre em contato com o seu consultor do Mercado Livre.
 
 Chamamos de lojas guarda chuva as contas no [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/51oWBHvVxSs8eAwLQhSbSd) que possuem múltiplas [lojas oficiais](https://www.mercadolivre.com.br/lojas-oficiais/catalogo) vinculadas ao mesmo usuário no Mercado Livre. A arquitetura funciona da seguinte forma: o [seller](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) integra suas [subaccounts](https://help.vtex.com/pt/tutorial/o-que-e-store-name--3gh9mTNeMgs6Qe44e8IqQK?&utm_source=autocomplete) com o Mercado Livre de forma que as lojas oficiais do usuário do Mercado Livre ficam vinculadas às subaccounts do seller.
 
diff --git a/docs/tutorials/pt/configure-cartman.md b/docs/tutorials/pt/configure-cartman.md
index 511f08ced..8cc809842 100644
--- a/docs/tutorials/pt/configure-cartman.md
+++ b/docs/tutorials/pt/configure-cartman.md
@@ -34,9 +34,7 @@ Neste artigo serão abordados os seguintes tópicos:
   - [Definir dados de marketing](#definir-dados-de-marketing)
 - [Desativar o Cartman](#desativar-o-cartman) 
 
-<div class="alert alert-warning">
-  Somente o lojista tem acesso ao <b>Cartman</b>. Suas funcionalidades não estão disponíveis para utilização dos usuários em uma loja.
-</div>
+>⚠️ Somente o lojista tem acesso ao **Cartman**. Suas funcionalidades não estão disponíveis para utilização dos usuários em uma loja.
 
 ## Ativar o Cartman manualmente
 
@@ -106,7 +104,5 @@ O Cartman pode ser desativado a qualquer momento, conforme a necessidade do loji
 2. No canto inferior direito da tela, clique no botão <img src="//images.ctfassets.net/alneenqid6w5/2Z1d5lHtVM7E7SvL58C8UW/acc0fa24cc8ae2e008d4a8d0f466b035/cartman-removebg-preview.png" alt="cartman-icon" width="25"/>.
 3. Na parte inferior do menu do Cartman, clique em `Desativar o Cartman`.
 
-<div class="alert alert-info">
-  Caso deseje reativar o <b>Cartman</b>, adicione novamente a query string <code>?cartman=on</code> em uma das páginas do Checkout de sua loja. Desta forma, o ícone azul estará novamente disponível no canto inferior direito da página.
-</div>
+>ℹ️ Caso deseje reativar o **Cartman**, adicione novamente a query string `?cartman=on` em uma das páginas do Checkout de sua loja. Desta forma, o ícone azul estará novamente disponível no canto inferior direito da página.
 
diff --git a/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md b/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
index 6a36a777d..9555105de 100644
--- a/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
+++ b/docs/tutorials/pt/configure-employee-benefits-using-master-data-clusters.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Na VTEX, uma promoção ou desconto pode ser aplicado a um grupo de clientes. Este grupo pode ser definido pelas propriedades que os clientes têm em comum.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 Este artigo mostra como configurar uma promoção para colaboradores. Considera-se que os colaboradores são um grupo de clientes, portanto são identificados usando clusters do Master Data.
 
diff --git a/docs/tutorials/pt/configure-seller-regionalization.md b/docs/tutorials/pt/configure-seller-regionalization.md
index b48ec7f6b..490444f43 100644
--- a/docs/tutorials/pt/configure-seller-regionalization.md
+++ b/docs/tutorials/pt/configure-seller-regionalization.md
@@ -43,6 +43,4 @@ Para ativar o **Region** em sua loja, é necessário realizar os seguintes passo
 1. [Configurar preço e disponibilidade de SKUs por Region](https://help.vtex.com/pt/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc#)
 2. [Habilitar a funcionalidade Region](https://developers.vtex.com/docs/guides/enable-the-region-for-skus)
 
-<div class="alert alert-info">
-  Atualmente, o <b>Region</b> está disponível para utilização em todas as lojas VTEX na versão v2. Saiba mais em <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
-</div>
+>ℹ️ Atualmente, o **Region** está disponível para utilização em todas as lojas VTEX na versão v2. Saiba mais em <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2<a/>.
diff --git a/docs/tutorials/pt/configure-template-in-smartcheckout-update.md b/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
index 80900dcf8..af29b5da7 100644
--- a/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
+++ b/docs/tutorials/pt/configure-template-in-smartcheckout-update.md
@@ -19,9 +19,7 @@ O __Portal__ é usado para renderizar as telas de __Checkout__ (Carrinho, Dados
 
 O módulo __Checkout__ no Admin, exibe os sites que estão cadastrados para a sua conta. Por meio dele, também é possível criar um novo site, editar e configurar informações sobre os sites já existentes.
 
-<div class="alert alert-info">
-Cada site cadastrado corresponde a um multidomínio (caso a conta possua multidomínios contratados). Para contas que não utilizam multidomínios, não é necessário cadastrar mais de um site neste módulo. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510#">Criar multiloja/multidomínio</a>.
-</div>
+>ℹ️ Cada site cadastrado corresponde a um multidomínio (caso a conta possua multidomínios contratados). Para contas que não utilizam multidomínios, não é necessário cadastrar mais de um site neste módulo. Saiba mais em [Criar multiloja/multidomínio](https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510#).
 
 ## Criar novo site
 
@@ -97,9 +95,7 @@ O código HTML preenchido no template corresponde ao que aparecerá nas páginas
 
 Dos templates disponíveis templates, os únicos que não podem ser alterados são __vtex-checkout__ e __vtex-orderPlaced__. Estes correspondem ao funcionamento nativo da plataforma, renderizando o conteúdo principal das páginas de __checkout__ e __order placed__.
 
-<div class="alert alert-warning">
-Javascripts incluídos diretamente em quaisquer templates do Portal serão ignorados pela plataforma. Ou seja, no momento da renderização da página, a plataforma o removerá. Isso porque o <a href="https://help.vtex.com/pt/tutorial/smartcheckout-preenchimento-automatico-de-dados-do-cliente--2Nuu3xAFzdhIzJIldAdtan#">SmartCheckout</a> apenas aceita scripts originados no Google Tag Manager. Assim, sempre que houver necessidade de realizar alguma customização (ou mesmo inserção de tags específicas) via javascript, utilize <a href="https://help.vtex.com/pt/tutorial/integration-with-google-tag-manager--frequentlyAskedQuestions_616#">Google Tag Manager</a>.
-</div>
+>⚠️ Javascripts incluídos diretamente em quaisquer templates do Portal serão ignorados pela plataforma. Ou seja, no momento da renderização da página, a plataforma o removerá. Isso porque o [SmartCheckout](https://help.vtex.com/pt/tutorial/smartcheckout-preenchimento-automatico-de-dados-do-cliente--2Nuu3xAFzdhIzJIldAdtan#) apenas aceita scripts originados no Google Tag Manager. Assim, sempre que houver necessidade de realizar alguma customização (ou mesmo inserção de tags específicas) via javascript, utilize [Google Tag Manager](https://help.vtex.com/pt/tutorial/integration-with-google-tag-manager--frequentlyAskedQuestions_616#).
 
 ### Exemplos de preenchimento de templates
 
diff --git a/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md b/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
index 2009e5da0..2964907c8 100644
--- a/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
+++ b/docs/tutorials/pt/configuring-a-marketplace-trade-policy.md
@@ -79,9 +79,7 @@ Sellers podem restringir a disponibilidade dos produtos em seu catálogo por mei
 
 Essa configuração é feita no *Catálogo* da VTEX, ao [cadastrar produtos](https://help.vtex.com/pt/tutorial/cadastrando-produtos--tutorials_2567), indicando para cada produto quais políticas comerciais estão vinculadas a ele. Se nenhuma restrição é feita na criação do produto, o produto estará disponível em todas as políticas comerciais. 
 
-<div class="alert alert-warning">
-Não é recomendado vincular políticas comerciais a coleções, para determinar o sortimento de produtos, sobretudo em casos de marketplaces externos à VTEX. Quando um produto é retirado da coleção da política comercial, o sistema VTEX não avisa o marketplace dessa atualização, fazendo com que o produto continue disponível no marketplace. 
-</div>  
+>⚠️ Não é recomendado vincular políticas comerciais a coleções, para determinar o sortimento de produtos, sobretudo em casos de marketplaces externos à VTEX. Quando um produto é retirado da coleção da política comercial, o sistema VTEX não avisa o marketplace dessa atualização, fazendo com que o produto continue disponível no marketplace.  
 
 ![Pt Catálogo Politica](https://images.ctfassets.net/alneenqid6w5/cXoXS1QSCxmbh89SwVfVP/63eea6b22e93fa4e94840a5c9a88db94/Pt_Cat__logo_Politica.jpg)
 
diff --git a/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md b/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md
index 565ffc9af..f759dd6c3 100644
--- a/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md
+++ b/docs/tutorials/pt/configuring-a-pricing-rule-for-a-sales-policy.md
@@ -15,9 +15,7 @@ legacySlug: configurar-regra-de-preco-para-politica-comercial
 subcategory: wUepkh8pzimEywO8oGUIc
 ---
 
-<div class="alert alert-info">
-Este artigo se refere à versão mais recente do Pricing da VTEX. Caso a sua loja ainda não esteja nessa nova versão, você pode solicitar a migração entrando em contato com o nosso time de atendimento.
-</div>
+>ℹ️ Este artigo se refere à versão mais recente do Pricing da VTEX. Caso a sua loja ainda não esteja nessa nova versão, você pode solicitar a migração entrando em contato com o nosso time de atendimento.
 
 Uma __regra de preço__ é um conjunto de condições que determinam os preços para uma certa política comercial. 
 
diff --git a/docs/tutorials/pt/configuring-a-santander-registered-boleto.md b/docs/tutorials/pt/configuring-a-santander-registered-boleto.md
index 4e92772c2..092ef60e6 100644
--- a/docs/tutorials/pt/configuring-a-santander-registered-boleto.md
+++ b/docs/tutorials/pt/configuring-a-santander-registered-boleto.md
@@ -15,14 +15,17 @@ legacySlug: configurar-boleto-registrado-santander
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 O boleto bancário é uma das formas de pagamento mais populares no Brasil. Apesar de não apresentar a mesma praticidade dos cartões de crédito, muitos compradores a consideram uma opção mais segura e acessível para adquirir bens de valor elevado. Dessa maneira, disponibilizar o boleto bancário é uma boa opção para aumentar as vendas no e-commerce.
 
 Para utilizar o Boleto Registrado Santander na sua loja, siga as instruções abaixo.
 
-<div class="alert alert-warning">
-A configuração na VTEX só é feita após uma série de etapas exigidas pelo Santander, incluindo a Contratação do serviço e Emissão do certificado digital.<br/><br/>Caso precise de apoio técnico nessas etapas, procure uma agência parceira VTEX ou seu gerente de relacionamento do Santander.</div>
+>⚠️ A configuração na VTEX só é feita após uma série de etapas exigidas pelo Santander, incluindo a Contratação do serviço e Emissão do certificado digital.
+>
+> 
+>
+> Caso precise de apoio técnico nessas etapas, procure uma agência parceira VTEX ou seu gerente de relacionamento do Santander.
 
 ## Contratação do serviço
 Antes de tudo, é preciso [abrir uma Conta Empresarial](https://www.santander.com.br/conta-pessoa-juridica "abrir uma conta empresarial") no Santander e contratar o serviço [Cobrança Registrada Online XML](https://www.santander.com.br/servicos-financeiros/solucoes-de-recebimento/cobrancas "Cobrança Registrada Online XML"), informando que utilizará a integração homologada da VTEX. Guarde os dados fornecidos pelo banco, eles serão necessários para a etapa de configuração.
@@ -32,9 +35,7 @@ Para possibilitar um canal de comunicação segura entre sua loja VTEX e o siste
 
 Após escolher sua certificadora, você deve entrar em contato solicitando um Certificado tipo Client de 2048 bits. Recomendamos que a validade seja de 10 anos, para reduzir a necessidade de atualização das configurações na VTEX. 
 
-<div class="alert alert-info">
-Na maioria dos casos, o certificado usado para emissão de nota fiscal pode ser reaproveitado. Consulte seu gerente de relacionamento do Santander em caso de dúvidas.
-</div>
+>ℹ️ Na maioria dos casos, o certificado usado para emissão de nota fiscal pode ser reaproveitado. Consulte seu gerente de relacionamento do Santander em caso de dúvidas.
 
 Recomendamos o apoio de uma equipe técnica para preparação dos arquivos necessários para emissão e instalação do certificado digital adquirido. Caso seja seu primeiro contato com esses processos, recomendamos a familiarização com os conceitos relacionados à Infraestrutura de Chaves Públicas (ICP) vistos neste site: [Public Key Infrastructure (PKI) Overview](https://www.sslshopper.com/public-key-infrastructure-pki-overview.html "Public Key Infrastructure (PKI) Overview").
 
@@ -43,9 +44,7 @@ Para iniciar o processo de emissão do seu certificado digital, a certificadora
 
 Sua equipe técnica deve ser capaz de criar este arquivo seguindo os passos deste site: [What is a CSR (Certificate Signing Request)?](https://www.sslshopper.com/what-is-a-csr-certificate-signing-request.html "What is a CSR (Certificate Signing Request)?") O arquivo CSR deve ser enviado para a certificadora.
 
-<div class="alert alert-warning">
-Uma <a href="https://www.ssls.com/knowledgebase/how-can-i-find-the-private-key-for-my-ssl-certificate/">chave privada</a> é criada quando um arquivo CSR é gerado. Guarde esta chave em local seguro, pois ela será necessária para a instalação do certificado.
-</div>
+>⚠️ Uma [chave privada](https://www.ssls.com/knowledgebase/how-can-i-find-the-private-key-for-my-ssl-certificate/) é criada quando um arquivo CSR é gerado. Guarde esta chave em local seguro, pois ela será necessária para a instalação do certificado.
 
 Quando seu certificado digital for emitido, a certificadora enviará o arquivo [CER](https://www.file-extension.info/pt/format/cer "CER") correspondente. O arquivo CER deve ser enviado para o Santander para instalação do seu certificado no ambiente de segurança do banco.
 
@@ -53,9 +52,7 @@ Para a configuração da integração na VTEX, será preciso instalar o certific
 
 Sua equipe técnica deve ser capaz de fazer isso seguindo os passos deste site: [SSL Converter](https://www.sslshopper.com/ssl-converter.html "SSL Converter"). O arquivo PFX e senha do certificado serão usados para a configuração na VTEX. 
 
-<div class="alert alert-warning">
-É altamente recomendável que a geração dos arquivos CSR e PFX seja feita na sua própria máquina usando OpenSSL (MacOS / Linux) ou o Assistente para Exportação de Certificados (Windows) para que você possa manter a segurança da chave privada e senha do certificado.
-</div>
+>⚠️ É altamente recomendável que a geração dos arquivos CSR e PFX seja feita na sua própria máquina usando OpenSSL (MacOS / Linux) ou o Assistente para Exportação de Certificados (Windows) para que você possa manter a segurança da chave privada e senha do certificado.
 
 ## Homologação
 
@@ -95,6 +92,4 @@ Para finalizar a configuração do boleto registrado Santander e disponibilizar
 
 Se todos passos forem concluídos com sucesso, basta reativar a condição de pagamento para começar a oferecer o boleto registrado Santander como meio de pagamento para seus clientes.
 
-<div class="alert alert-info">
-O serviço do Santander não possui conciliação automática dos boletos emitidos pela VTEX. Por isso, é necessário importar um arquivo de retorno tipo .RET nos formatos CNAB (240/400) para aprovação dos pedidos pagos com boleto.
-</div>
+>ℹ️ O serviço do Santander não possui conciliação automática dos boletos emitidos pela VTEX. Por isso, é necessário importar um arquivo de retorno tipo .RET nos formatos CNAB (240/400) para aprovação dos pedidos pagos com boleto.
diff --git a/docs/tutorials/pt/configuring-access-profiles-old.md b/docs/tutorials/pt/configuring-access-profiles-old.md
index de9a6d149..403a02f4d 100644
--- a/docs/tutorials/pt/configuring-access-profiles-old.md
+++ b/docs/tutorials/pt/configuring-access-profiles-old.md
@@ -34,7 +34,7 @@ Veja alguns perfis úteis:
 - __Financeiro:__ concede acesso ao submódulo Financeiro, dentro do License Manager, permitindo ver boletos e NFs relativos ao pagamento do serviço VTEX.
 - __Webservice:__ permite que o usuário acesse os métodos do webservice, necessário para determinadas integrações (em geral, com o catálogo).
 
-<div class="alert alert-warning"><strong>Atenção</strong>: os perfis de televendas bloqueiam o acesso ao módulo Catalog. Ou seja, não conseguem acessar o cadastro de produtos, por exemplo. Se for necessário acessar este módulo, o usuário deverá trabalhar com dois logins diferentes.</div>
+>⚠️ **Atenção**: os perfis de televendas bloqueiam o acesso ao módulo Catalog. Ou seja, não conseguem acessar o cadastro de produtos, por exemplo. Se for necessário acessar este módulo, o usuário deverá trabalhar com dois logins diferentes.
 
 ## Criando novos perfis
 
diff --git a/docs/tutorials/pt/configuring-access-without-www.md b/docs/tutorials/pt/configuring-access-without-www.md
index 57e193e24..92beae5bb 100644
--- a/docs/tutorials/pt/configuring-access-without-www.md
+++ b/docs/tutorials/pt/configuring-access-without-www.md
@@ -41,9 +41,7 @@ Também existe a possibilidade de usar redirecionamento de DNS, como disponibili
 
 Afim de realizar um redirecionamento de DNS de forma simples, você encontra abaixo as instruções para realizar o redirecionamento com o serviço [Direcionar.com.br](http://direcionar.com.br).
 
-<div class="alert alert-warning">
-Vale ressaltar que o Direcionar não é um serviço da VTEX e não funciona com HTTPS. Existem outros serviços similares, e a VTEX não recomenda nenhum específico. A VTEX não se responsabiliza por problemas causados por serviços externos de redirecionamento.
-</div>
+>⚠️ Vale ressaltar que o Direcionar não é um serviço da VTEX e não funciona com HTTPS. Existem outros serviços similares, e a VTEX não recomenda nenhum específico. A VTEX não se responsabiliza por problemas causados por serviços externos de redirecionamento.
 
 Confira este outro artigo para saber como [configurar redirecionamentos de outros endereços](https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ).
 
diff --git a/docs/tutorials/pt/configuring-affiliates.md b/docs/tutorials/pt/configuring-affiliates.md
index 852a23545..a45e25724 100644
--- a/docs/tutorials/pt/configuring-affiliates.md
+++ b/docs/tutorials/pt/configuring-affiliates.md
@@ -36,9 +36,7 @@ Para criar um novo ID do afiliado, siga os passos abaixo:
 
 > Perceba que o valor __{NomeDoMarketplace}__ deve ser alterado pelo nome da conta do marketplace e o valor __{IdDoSeller}__ deve ser alterado para o ID do seller cadastrado pelo marketplace.
 
-> <div class="alert alert-danger">
-  O valor <strong>{IdDoSeller}</strong> é <em>case sensitive</em>. Dessa forma, ele deverá ser escrito na URL exatamente da mesma maneira que estiver cadastrado no marketplace.  
-</div>
+> >❗ O valor **{IdDoSeller}** é *case sensitive*. Dessa forma, ele deverá ser escrito na URL exatamente da mesma maneira que estiver cadastrado no marketplace.
 
 > Para casos de [marketplaces externos à VTEX](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#integrado-a-marketplace-externo), preencha com o valor: `https://{endpointDoAfiliado}/api/notification/`.   
 
diff --git a/docs/tutorials/pt/configuring-affirm.md b/docs/tutorials/pt/configuring-affirm.md
index ab537dbf5..35ad6b8dc 100644
--- a/docs/tutorials/pt/configuring-affirm.md
+++ b/docs/tutorials/pt/configuring-affirm.md
@@ -19,9 +19,7 @@ subcategory:
 
 Ao realizar uma compra e escolher o Affirm como meio de pagamento, o comprador passará por uma análise de crédito e, com base no seu score, a ferramenta irá liberar o valor para pagamento daquela transação. Com isso, o cliente pagará o valor diretamente ao Affirm com os juros definidos no momento da adesão.
 
-<div class="alert alert-warning">
-A instalação do <b>aplicativo</b> Affirm é feita utilizando o <b>VTEX IO</b>, uma plataforma de desenvolvimento <i>low-code</i> que permite programadores desenvolverem aplicações e novos componentes para lojas VTEX. Acesse a documentação <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-install">Installing VTEX IO's CLI</a> e baixe a plataforma e seus componentes antes de seguir para as próximas etapas.
-</div>
+>⚠️ A instalação do **aplicativo** Affirm é feita utilizando o **VTEX IO**, uma plataforma de desenvolvimento <i>low-code</i> que permite programadores desenvolverem aplicações e novos componentes para lojas VTEX. Acesse a documentação [Installing VTEX IO's CLI](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-install) e baixe a plataforma e seus componentes antes de seguir para as próximas etapas.
 
 Para configurar o Affirm, você precisa:
 
diff --git a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index cb07b16e9..426cc3af5 100644
--- a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -17,9 +17,7 @@ subcategory: 6bSdupUQgvuXjBL9Igawxl
 
 A importação em massa de dados permite a simplificação do processo de atualização e manutenção de informações para organizações compradoras, seus usuários (membros) e centros de custo.
 
-<div class="alert alert-warning">
-Antes de configurar a funcionalidade de importação em massa, é necessário ter instalado em sua loja o aplicativo <a href="https://developers.vtex.com/docs/apps/vtex.b2b-suite">B2B Suite</a>. 
-</div>
+>⚠️ Antes de configurar a funcionalidade de importação em massa, é necessário ter instalado em sua loja o aplicativo [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite).
 
 Veja abaixo como realizar a importação em massa de dados na plataforma VTEX:
 
diff --git a/docs/tutorials/pt/configuring-carriers-cut-off-time.md b/docs/tutorials/pt/configuring-carriers-cut-off-time.md
index 9daebce54..22dd90d7c 100644
--- a/docs/tutorials/pt/configuring-carriers-cut-off-time.md
+++ b/docs/tutorials/pt/configuring-carriers-cut-off-time.md
@@ -15,10 +15,8 @@ legacySlug: configurar-o-horario-de-corte-da-transportadora
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-warning">
-Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
-<a href="https://help.vtex.com/pt/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envio</a>.
-</div> 
+>⚠️ Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
+> [estratégia de envio](https://help.vtex.com/pt/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl). 
 
 
 As transportadoras, que são chamadas de Política de Envio no seu Admin, são as empresas responsáveis por fazerem a distribuição dos produtos vendidos por um e-commerce. É comum que uma loja tenha diversas transportadoras associadas a ela. Isto acontece pois o perfil de operação e de frota das **transportadoras varia de acordo com a rota, prazo e tipo de produto** que ela irá entregar.
diff --git a/docs/tutorials/pt/configuring-cielo-acquirer.md b/docs/tutorials/pt/configuring-cielo-acquirer.md
index 9712c398a..b5f3eb3c7 100644
--- a/docs/tutorials/pt/configuring-cielo-acquirer.md
+++ b/docs/tutorials/pt/configuring-cielo-acquirer.md
@@ -40,9 +40,7 @@ Para configurar a Cielo, siga os passos abaixo:
     - __BpmpiAuthNotifyOnly:__ Informar se a transação com cartão será submetida ou não no modo “somente notificação”. Este modo é válido somente para cartões Mastercard. Nele, o processo de autenticação não será acionado, porém os dados serão submetidos à bandeira.
     - __BpmpiAuthSuppresschallenge:__ Informar se ignora ou não o desafio quando houver. Se uma transação é autorizada após ignorar o desafio, o liability permanece com o estabelecimento.
 
-<div class="alert alert-warning">
-<strong>Atenção</strong>: Para que o fluxo 3DS2 funcione corretamente, é necessário a instalação da payment app cielo-authentication-app.
-</div>
+>⚠️ **Atenção**: Para que o fluxo 3DS2 funcione corretamente, é necessário a instalação da payment app cielo-authentication-app.
 
 11. Em __Captura de segurança antecipada__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude). Você também pode desativar a função.
 12. Clique em __Salvar__.
diff --git a/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md b/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md
index 16db2b525..edaaeee9b 100644
--- a/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md
+++ b/docs/tutorials/pt/configuring-clearsale-global-anti-fraud-solution.md
@@ -17,9 +17,7 @@ subcategory:
 
 A ClearSale Global é uma solução antifraude, disponível __exclusivamente para o mercado internacional__. Através da análise comportamental dos clientes, a solução identifica vulnerabilidades e evita possíveis fraudes nas transações da sua loja.
 
-<div class="alert alert-info">
-Caso você esteja no Brasil e queira utilizar a ClearSale, a VTEX oferece integração com a ClearSale V3, exclusiva para clientes brasileiros. Acesse o tutorial <a href="https://help.vtex.com/pt/tutorial/configurar-antifraude-clearsale-v3--2pPORygesIqQOa6cIG6agg?&utm_source=autocomplete">Configurar antifraude ClearSale v3</a> para realizar a configuração.
-  </div>
+>ℹ️ Caso você esteja no Brasil e queira utilizar a ClearSale, a VTEX oferece integração com a ClearSale V3, exclusiva para clientes brasileiros. Acesse o tutorial [Configurar antifraude ClearSale v3](https://help.vtex.com/pt/tutorial/configurar-antifraude-clearsale-v3--2pPORygesIqQOa6cIG6agg?&utm_source=autocomplete) para realizar a configuração.
 
 Para configurar a __ClearSale Global__, será necessário:
 
diff --git a/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md b/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
index 8348fe82a..e8bb5e2be 100644
--- a/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
+++ b/docs/tutorials/pt/configuring-clearsale-v3-antifraud.md
@@ -38,10 +38,9 @@ Para configurar o ClearSaleV3, siga os passos abaixo:
 </ul>
 7. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Caso possua uma aplicação mobile que utilize as APIs da VTEX na finalização da compra é necessário realizar a implementação da coleta de dados do fingerprint a serem enviados para Clearsale, de acordo com a plataforma utilizada pelo aplicativo. Saiba mais em <a href="https://api.clearsale.com.br/docs/behavior-analytics" target="_blank">Clearsale Behavior Analytics</a>.</p>
-<p>Com a implementação do SDK é necessário coletar o valor de <span class="bg-muted-4">sessionId</span> e enviá-lo no campo <span class="bg-muted-4">deviceFingerprint</span> via <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">API na criação do pagamento</a>.</p>  
-</div>
+>ℹ️ Caso possua uma aplicação mobile que utilize as APIs da VTEX na finalização da compra é necessário realizar a implementação da coleta de dados do fingerprint a serem enviados para Clearsale, de acordo com a plataforma utilizada pelo aplicativo. Saiba mais em [Clearsale Behavior Analytics](https://api.clearsale.com.br/docs/behavior-analytics" target="_blank).
+>
+> Com a implementação do SDK é necessário coletar o valor de <span class="bg-muted-4">sessionId</span> e enviá-lo no campo <span class="bg-muted-4">deviceFingerprint</span> via [API na criação do pagamento](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
 
 ## Criando a tag do Google Tag Manager
 
@@ -91,6 +90,4 @@ O `shippingEstimate` pode ser obtido nos itens de `shippingData.logisticsInfo[]`
 
 O valor de `deliverySlaInMinutes` é a conversão de `shippingEstimate` em minutos. Se a unidade for `m` (minutos) será o mesmo valor, se a unidade for `h` (horas) o valor é multiplicado por 60 e se a unidade for `d` (dias corridos) ou `bd` (dias úteis) o valor é multiplicado por 1440. Por exemplo, três dias corridos ou `3d` é representado como `4320`. O `deliverySlaInMinutes` é utilizado em cada item do `minicart` no request body dos endpoints <a href="https://developers.vtex.com/vtex-rest-api/reference/antifraud-flow#sendantifraudpreanalysisdata" target="_blank">Send Antifraud Pre-Analysis Data</a> e <a href="https://developers.vtex.com/vtex-rest-api/reference/antifraud-flow#sendantifrauddata" target="_blank">Send Antifraud Data</a>.
 
-<div class="alert alert-info">
-Apesar de a conversão do tempo em dias corridos (<code>d</code>) e dias úteis (<code>bd</code>) para minutos  ser a mesma no campo <code>deliverySlaInMinutes</code>, a data da entrega pode divergir dependendo do calendário (quando há finais de semana e feriados dentro do período de entrega).
-</div>
+>ℹ️ Apesar de a conversão do tempo em dias corridos (`d`) e dias úteis (`bd`) para minutos  ser a mesma no campo `deliverySlaInMinutes`, a data da entrega pode divergir dependendo do calendário (quando há finais de semana e feriados dentro do período de entrega).
diff --git a/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md b/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md
index feaed3a21..540ba19dc 100644
--- a/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md
+++ b/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md
@@ -30,9 +30,7 @@ Veja as etapas:
 
 Antes de apontar um domínio à VTEX, é necessário garantir o cumprimento dos requisitos citados abaixo.
 
-<div class="alert alert-warning">
-Se você estiver migrando a sua loja da <strong>Loja Integrada</strong> para a VTEX, contate o nosso suporte antes de apontar o DNS. É necessário liberar o domínio da Loja Integrada para que ele seja usado na loja VTEX.
-</div>
+>⚠️ Se você estiver migrando a sua loja da **Loja Integrada** para a VTEX, contate o nosso suporte antes de apontar o DNS. É necessário liberar o domínio da Loja Integrada para que ele seja usado na loja VTEX.
 
 ### Cadastro de domínio na VTEX
 
@@ -48,15 +46,11 @@ A VTEX usa dois provedores de CDN nas lojas: **Cloudfront** e **Azion**. É impo
 
 Portanto, se você tem o domínio da loja registrado na plataforma da **Cloudfront** ou **Azion**, remova este registro antes de realizar o apontamento de DNS para a VTEX.
 
-<div class="alert alert-warning">
-Se não for possível remover o registro do domínio da sua loja nas plataformas <strong>Cloudfront</strong> ou <strong>Azion</strong> entre em contato com o <a href="https://help.vtex.com/pt/support">suporte VTEX</a> explicando a situação. Dessa forma, o time da VTEX irá te auxiliar para garantir o bom funcionamento da loja no Go live.
-</div>
+>⚠️ Se não for possível remover o registro do domínio da sua loja nas plataformas **Cloudfront** ou **Azion** entre em contato com o [suporte VTEX](https://help.vtex.com/pt/support) explicando a situação. Dessa forma, o time da VTEX irá te auxiliar para garantir o bom funcionamento da loja no Go live.
 
 ## Configurar registros CAA
 
-<div class="alert alert-warning">
-A configuração de registros de CAA como descrita nesta seção só é necessária caso haja registro de CAA no seu servidor de DNS. Caso contrário, siga para o próximo tópico deste guia.
-</div>
+>⚠️ A configuração de registros de CAA como descrita nesta seção só é necessária caso haja registro de CAA no seu servidor de DNS. Caso contrário, siga para o próximo tópico deste guia.
 
 Registros CAA indicam quais autoridades certificadoras (CAs) estão autorizadas a gerar e renovar certificados que atestam a identidade do seu domínio. A configuração adequada desses registros é necessária para que seja possível gerar os [certificados SSL](https://help.vtex.com/pt/tutorial/certificado-de-seguranca-ssl-a-que-se-refere-e-como-contratar--tutorials_1308) e usar a CDN da VTEX.
 
@@ -70,9 +64,7 @@ Isso significa que a autoridade certificadora **Let’s Encrypt** pode emitir ce
 
 Outra alternativa, embora não recomendada, seria não incluir registros CAA no seu servidor DNS - isso sinalizaria que todas autoridades certificadoras estariam autorizadas a emitir e renovar certificados para o seu domínio.
 
-<div class="alert alert-info">
-Esses tipos de entrada podem não estar disponíveis na interface do seu gerenciador de DNS, mas muitas vezes é possível gerenciá-los através de chamados no suporte da ferramenta específica.
-</div>
+>ℹ️ Esses tipos de entrada podem não estar disponíveis na interface do seu gerenciador de DNS, mas muitas vezes é possível gerenciá-los através de chamados no suporte da ferramenta específica.
 
 Para facilitar o trabalho de criar/verificar seus registros CAA, você pode usar o [CAA Record Helper by SSLMate](https://sslmate.com/caa/). O programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) também pode ajudar na verificação dos registros, através do comando `dig domain.com CAA` - um status `SERVFAIL` pode indicar não-conformidade do seu servidor DNS.
 
@@ -114,9 +106,7 @@ Na zona de DNS do seu domínio, você deve criar uma entrada do tipo CNAME no su
 
 Note que o `{domínio}` indicado acima deve ser o mesmo que você [cadastrou na VTEX](#cadastro-de-dominio-na-vtex).
 
-<div class="alert alert-warning">
-Caso você utilize a Cloudflare como zona de DNS, pode ser necessário desabilitar o proxy de DNS e, consequentemente, desativar os serviços de CDN e WAF da Cloudflare. Mais informações podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">Como desabilitar o proxy no Cloudflare</a>.
-</div>
+>⚠️ Caso você utilize a Cloudflare como zona de DNS, pode ser necessário desabilitar o proxy de DNS e, consequentemente, desativar os serviços de CDN e WAF da Cloudflare. Mais informações podem ser encontradas no artigo [Como desabilitar o proxy no Cloudflare](https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 Alguns exemplos:
 
@@ -147,9 +137,7 @@ Endereço da loja: www.loja.minhaempresa.com.br
 
 Atente-se que o início do domínio ("loja", "www", "www.loja" ou qualquer outro) e a terminação (".com", ".com.br", ".com.ar" ou qualquer outro) fazem parte do `{hostname}`, e devem estar no CNAME de destino.
 
-<div class="alert alert-danger">
-Não pode haver nenhum apontamento tipo A coexistindo com o CNAME descrito acima. A coexistência destes dois apontamentos pode causar problemas no Go Live da sua loja. Mantenha apenas o apontamento CNAME descrito acima.
-</div>
+>❗ Não pode haver nenhum apontamento tipo A coexistindo com o CNAME descrito acima. A coexistência destes dois apontamentos pode causar problemas no Go Live da sua loja. Mantenha apenas o apontamento CNAME descrito acima.
 
 ## Gerar certificado SSL
 
@@ -165,9 +153,7 @@ O certificado é gerado por meio da [Let's Encrypt](https://letsencrypt.org/) e
 
 ---
 
-<div class="alert alert-info">
-A propagação do apontamento de DNS demora de 24 a 48 horas para ocorrer completamente, o que significa que o endereço configurado pode não estar acessível a todas as pessoas logo após a configuração.
-</div>
+>ℹ️ A propagação do apontamento de DNS demora de 24 a 48 horas para ocorrer completamente, o que significa que o endereço configurado pode não estar acessível a todas as pessoas logo após a configuração.
 
 As instruções acima tratam apenas do apontamento de um domínio principal à sua loja na VTEX. É importante que, caso sua loja tenha outros domínios, eles sejam redirecionados a um único domínio principal. 
 
diff --git a/docs/tutorials/pt/configuring-domains-in-account-management.md b/docs/tutorials/pt/configuring-domains-in-account-management.md
index 7ff2f13e8..7d09bb00d 100644
--- a/docs/tutorials/pt/configuring-domains-in-account-management.md
+++ b/docs/tutorials/pt/configuring-domains-in-account-management.md
@@ -17,15 +17,13 @@ subcategory: yMp6sKDiJEi66CGAIQ4ma
 
 A configuração de domínios é necessária para que o endereço acessado seja corretamente direcionado a uma loja na VTEX. Abaixo você pode ver como [cadastrar um novo domínio](#cadastrar-um-novo-dominio) ou [mudar o domínio de uma loja ativa](#mudar-o-dominio-da-loja).
 
-<div class="alert alert-danger">
-Caso a sua operação possua mais de uma conta VTEX ou subcontas, não troque o domínio de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.
-</div>
+>❗ Caso a sua operação possua mais de uma conta VTEX ou subcontas, não troque o domínio de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.
 
-<div class="alert alert-warning">
-Se você adicionar mais de um domínio como host da sua loja, todos exibirão o mesmo conteúdo. No entanto, para atingir este objetivo recomendamos que cadastre apenas um domínio e use redirecionamentos para os outros. Saiba mais sobre redirecionamentos:
-<ul><li><a href=”https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirecionamento de outros endereços</a></li>
-<li><a href=”https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acesso sem www</a></li></ul> 
-</div>
+>⚠️ Se você adicionar mais de um domínio como host da sua loja, todos exibirão o mesmo conteúdo. No entanto, para atingir este objetivo recomendamos que cadastre apenas um domínio e use redirecionamentos para os outros. Saiba mais sobre redirecionamentos:
+>
+> *<a href=”https://help.vtex.com/pt/tutorial/redirecionamento-de-outros-enderecos--3Xi2AeLUx2QpJQu8DTX8KQ”>Redirecionamento de outros endereços</a>
+>
+> *<a href=”https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278”>Configurar acesso sem www</a>
 
 ## Subdomínio
 
diff --git a/docs/tutorials/pt/configuring-greenlist.md b/docs/tutorials/pt/configuring-greenlist.md
index 41558a383..64d81942d 100644
--- a/docs/tutorials/pt/configuring-greenlist.md
+++ b/docs/tutorials/pt/configuring-greenlist.md
@@ -35,9 +35,7 @@ Havendo ou não aprovação por parte do antifraude, uma vez que este serviço j
 
 __A Greenlist é uma lista de clientes pré-aprovados pelo lojista de acordo com determinadas condições.__ Uma vez que esses clientes façam um certo número de compras em seu site, sempre informando os mesmos dados (como e-mail e número do cartão de crédito), eles são marcados como confiáveis. Assim, nas próximas vezes em que fizerem uma compra no seu site, os pedidos deles não passarão pelo antifraude, e sua loja economizará o valor que teria de pagar por esse serviço.
 
-<div class="alert alert-warning">
-Quanto mais dados de assinatura você exigir, mais rígidas serão suas regras, e menos clientes entrarão na Greenlist.
-</div>
+>⚠️ Quanto mais dados de assinatura você exigir, mais rígidas serão suas regras, e menos clientes entrarão na Greenlist.
 
 ## Configurar a Greenlist
 
diff --git a/docs/tutorials/pt/configuring-ideal-payment-method-in-adyen-integration.md b/docs/tutorials/pt/configuring-ideal-payment-method-in-adyen-integration.md
index 0e9bb4aa9..5b19432e2 100644
--- a/docs/tutorials/pt/configuring-ideal-payment-method-in-adyen-integration.md
+++ b/docs/tutorials/pt/configuring-ideal-payment-method-in-adyen-integration.md
@@ -19,10 +19,8 @@ __iDEAL__ é um método de pagamento online  disponível apenas para clientes da
 
 Neste tutorial, você confere as etapas para para configurá-lo em sua loja por meio da integração com a [Adyen](https://help.vtex.com/en/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337). 
 
-<div class="alert alert-danger">
-  Atualmente, a <b>Adyen</b> é o único parceiro que suporta pagamentos realizados com o iDEAL. Dessa forma, é preciso entrar em contato com a Adyen para saber se o iDEAL é aplicável ou não para sua localidade. 
-Caso seja, acesse o artigo <a href="https://help.vtex.com/pt/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337?&utm_source=autocomplete">Configurar o gateway Adyen na VTEX</a> e configure a afiliação na sua loja.
-  </div>
+>❗ Atualmente, a **Adyen** é o único parceiro que suporta pagamentos realizados com o iDEAL. Dessa forma, é preciso entrar em contato com a Adyen para saber se o iDEAL é aplicável ou não para sua localidade. 
+> Caso seja, acesse o artigo [Configurar o gateway Adyen na VTEX](https://help.vtex.com/pt/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337?&utm_source=autocomplete) e configure a afiliação na sua loja.
 
 1. Acesse o __Admin__ VTEX.
 2. Clique em __Pagamentos__ > __Configurações__.
diff --git a/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md b/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
index 000367c5a..f3c25f224 100644
--- a/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
+++ b/docs/tutorials/pt/configuring-maximum-automatic-payment-settlement-time-frame.md
@@ -19,9 +19,7 @@ Neste artigo, explicaremos como configurar o recurso de prazo máximo para liqui
 
 Antes de partirmos para o passo a passo em si, é importante esclarecermos a diferença entre __liquidação por faturamento__, __liquidação automática__ e __liquidação antecipada__ - três conceitos presentes no mercado de pagamentos. Em alguns conectores de pagamentos da plataforma, esses termos são referidos como __captura por faturamento__, __captura automática__ e __captura antecipada__.
 
-<div class="alert alert-warning">
-As informações a seguir são válidas para pagamentos realizados com cartão de crédito
-</div>
+>⚠️ As informações a seguir são válidas para pagamentos realizados com cartão de crédito
 
 ## Liquidação por faturamento
 A liquidação por faturamento é uma das etapas do [fluxo da transação](https://help.vtex.com/pt/tutorial/fluxo-da-transacao-no-pagamentos--Er2oWmqPIWWyeIy4IoEoQ "fluxo da transação") - o processo interno da VTEX que ocorre depois que um cliente realiza o pagamento de um pedido. Ou seja, o cliente não participa dessa dinâmica.
@@ -42,9 +40,7 @@ No momento que o processo de autorização começa, o sistema espera um limite d
 
 Lojista e adquirente acordam qual será o limite de tempo para que a liquidação automática seja acionada. 
 
-<div class="alert alert-info">
-Geralmente, o tempo máximo definido para que a liquidação aconteça é de quatro dias. Entretanto, essa <strong>não</strong> é uma regra. Cada adquirente pode definir o período que achar mais adequado.
-</div>
+>ℹ️ Geralmente, o tempo máximo definido para que a liquidação aconteça é de quatro dias. Entretanto, essa **não** é uma regra. Cada adquirente pode definir o período que achar mais adequado.
 
 Para configurar essa liquidação, siga o passo a passo:
 
diff --git a/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md b/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md
index b4d3e0cf8..40a440693 100644
--- a/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md
+++ b/docs/tutorials/pt/configuring-mercado-pagos-device-fingerprint.md
@@ -19,9 +19,7 @@ __Device Fingerprint__ é um identificador que atua no processamento de um pagam
 
 Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
 
 Neste artigo, explicaremos como associar o recurso Device Fingerprint à afiliação Mercado Pago.
 
diff --git a/docs/tutorials/pt/configuring-openpay-payment-gateway.md b/docs/tutorials/pt/configuring-openpay-payment-gateway.md
index 5e9c28120..11a07b6ec 100644
--- a/docs/tutorials/pt/configuring-openpay-payment-gateway.md
+++ b/docs/tutorials/pt/configuring-openpay-payment-gateway.md
@@ -17,9 +17,7 @@ subcategory:
 
 [Openpay](https://www.openpay.mx/) é um processador de pagamentos online que permite receber pagamentos realizados com cartão de crédito, dinheiro e transferências bancárias.
 
-<div class="alert alert-warning">
-  Antes de realizar as configurações, é preciso que sua conta na Openpay já esteja criada e verificada. Caso você ainda não tenha se registrado, <a href="https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false">clique aqui</a> e crie sua conta.
-  </div>
+>⚠️ Antes de realizar as configurações, é preciso que sua conta na Openpay já esteja criada e verificada. Caso você ainda não tenha se registrado, [clique aqui](https://sandbox-dashboard.openpay.mx/login/register?isCandidateForNewStyles=false) e crie sua conta.
 
 Para configurar o Openpay você precisará:
 
diff --git a/docs/tutorials/pt/configuring-order-recurrence.md b/docs/tutorials/pt/configuring-order-recurrence.md
index 0921cc498..3f51a6596 100644
--- a/docs/tutorials/pt/configuring-order-recurrence.md
+++ b/docs/tutorials/pt/configuring-order-recurrence.md
@@ -55,9 +55,7 @@ Os pedidos recorrentes estão disponíveis em valores que podem ser:
 
 Ao adicionar um produto habilitado para recorrência no checkout, o cliente seleciona a frequência dos itens que deseja receber recorrentemente e fecha o pedido normalmente, selecionando o meio de pagamento **Cartão de Crédito**.
 
-<div class="alert alert-warning">
-A recorrência apenas será ativada quando o meio de pagamento for Cartão de Crédito.
-</div>
+>⚠️ A recorrência apenas será ativada quando o meio de pagamento for Cartão de Crédito.
 
 Depois do período de tempo escolhido, o sistema automaticamente gera o pedido. Após a aprovação do pagamento, a recorrência será ativada.
 
diff --git a/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md b/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
index 307335d49..8fa8259ba 100644
--- a/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/configuring-payment-with-adyenv3-in-vtex-sales-app.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Na VTEX, é possível realizar a integração com o provedor de pagamento Adyen. Por meio deste conector, sua loja pode oferecer transações de pagamento em lojas físicas (VTEX Sales App), utilizando pontos de vendas (POS). Para mais informações, acesse [O que é o VTEX Sales App?](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf).
 
-<div class="alert alert-info">
-Para utilizar a afiliação AdyenV3 em sua loja por outros canais de venda online (exceto VTEX Sales App), acesse <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3--7xAz67E2Eg63LWCQNjVdwv">Configurar pagamento com AdyenV3</a>.
-</div>
+>ℹ️ Para utilizar a afiliação AdyenV3 em sua loja por outros canais de venda online (exceto VTEX Sales App), acesse [Configurar pagamento com AdyenV3](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3--7xAz67E2Eg63LWCQNjVdwv).
 
 Para utilizar a afiliação AdyenV3 no VTEX Sales App, é necessário:
 
@@ -28,9 +26,7 @@ Para utilizar a afiliação AdyenV3 no VTEX Sales App, é necessário:
 - [Configurar conector AdyenV3 (VTEX Sales App) na VTEX](#configurar-conector-adyenv3-vtex-sales-app-na-vtex)
 - [Configurar condição de pagamento](#configurar-condicao-de-pagamento)
 
-<div class="alert alert-warning">
-As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Adyen para informações atualizadas.
-</div>
+>⚠️ As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Adyen para informações atualizadas.
 
 ## Configurar ponto de venda (POS)
 
@@ -100,9 +96,7 @@ Configure o webhook conforme os passos abaixo:
 
 ![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
-<div class="alert alert-info">
-Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
-</div>
+>ℹ️ Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
 
 ## Configurar conector AdyenV3 (VTEX Sales App) na VTEX
 
diff --git a/docs/tutorials/pt/configuring-payment-with-adyenv3.md b/docs/tutorials/pt/configuring-payment-with-adyenv3.md
index 7a36365a6..12f96792c 100644
--- a/docs/tutorials/pt/configuring-payment-with-adyenv3.md
+++ b/docs/tutorials/pt/configuring-payment-with-adyenv3.md
@@ -22,13 +22,9 @@ Para utilizar a afiliação AdyenV3, é necessário:
 - [Configurar ambiente Adyen](#configurar-ambiente-adyen)
 - [Configurar conector AdyenV3 na VTEX](#configurar-conector-adyenv3-na-vtex)
 
-<div class="alert alert-warning">
-As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Adyen para informações atualizadas.
-</div>
+>⚠️ As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Adyen para informações atualizadas.
 
-<div class="alert alert-info">
-Para utilizar a afiliação AdyenV3 por meio do <a href="https://help.vtex.com/pt/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf#">Sales App</a> em suas lojas físicas (ponto de venda), acesse <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3-no-instore--24yO6KloBn6DN6CbprHtgt">Configurar pagamento com AdyenV3 no VTEX Sales App</a>.
-</div>
+>ℹ️ Para utilizar a afiliação AdyenV3 por meio do [Sales App](https://help.vtex.com/pt/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf#) em suas lojas físicas (ponto de venda), acesse [Configurar pagamento com AdyenV3 no VTEX Sales App](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-adyenv3-no-instore--24yO6KloBn6DN6CbprHtgt).
 
 ## Configurar ambiente Adyen
 
@@ -51,9 +47,7 @@ Para habilitar o acesso da VTEX no ambiente Adyen, siga as instruções abaixo:
 
 ### Obtenha a API Key e Client Key
 
-<div class="alert alert-warning">
-As informações abaixo consideram que a API Key e Client Key já foram previamente geradas no ambiente da Adyen. Caso seja necessário criá-las, consulte a documentação da <a href="https://docs.adyen.com/">Adyen</a>.
-</div>
+>⚠️ As informações abaixo consideram que a API Key e Client Key já foram previamente geradas no ambiente da Adyen. Caso seja necessário criá-las, consulte a documentação da [Adyen](https://docs.adyen.com/).
 
 1. Clique em __Developers__ na barra lateral e em seguida em __API credentials__.
 2. Selecione a sua credencial API.
@@ -95,9 +89,7 @@ Configure o webhook conforme os passos abaixo:
 
 ![Adyenv3_7](https://images.ctfassets.net/alneenqid6w5/dEbiVnYj1Ic4eYgkSNolQ/79bba40bd6820d29de275e3cab19f22e/Adyenv3_7.PNG)
 
-<div class="alert alert-info">
-Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
-</div>
+>ℹ️ Se você possui múltiplas lojas, é necessário realizar a configuração do webhook para cada uma delas.
 
 ## Configurar conector AdyenV3 na VTEX
 
@@ -124,9 +116,7 @@ Se você deseja processar pagamentos com cartões de crédito em sua loja utiliz
 
 No ticket você também deverá enviar a URL que será autorizada pela Adyen a realizar a transação no cartão de crédito em sua loja. O formato da URL deverá ser `https://{live URL prefix}-checkout-live.adyenpayments.com`, onde a informação "{live URL prefix}" deve ser a mesma inserida por você nas configurações da Adyen no Admin VTEX.
 
-<div class="alert alert-warning">
-O endereço completo da URL deve ser escrito somente em letras minúsculas, mesmo se o "Live URL prefix" configurado no Admin VTEX possuir alguma letra maíuscula.
-</div>    
+>⚠️ O endereço completo da URL deve ser escrito somente em letras minúsculas, mesmo se o "Live URL prefix" configurado no Admin VTEX possuir alguma letra maíuscula.    
 
 ## Configurar pagamento com Apple Pay na Adyen (opcional) 
 
diff --git a/docs/tutorials/pt/configuring-price-divergence-rule.md b/docs/tutorials/pt/configuring-price-divergence-rule.md
index 48dda8607..1a7735443 100644
--- a/docs/tutorials/pt/configuring-price-divergence-rule.md
+++ b/docs/tutorials/pt/configuring-price-divergence-rule.md
@@ -71,9 +71,7 @@ Para criar a **2ª regra**, clique no `<img class="shadow-4" src="https:////imag
 
 Configure a nova regra de autorização e, após definir todas as regras desejadas, clique no botão **SALVAR REGRAS**. Você verá a seguinte mensagem: _Após salvar, você ainda poderá editá-las ou excluí-las quando quiser_. Clique em **OK** para  confirmar. Feito isso, você terá concluído a criação da regra de Divergência de valores.
 
-<div class="alert alert-warning">
-Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você seja seller.
-</div>
+>⚠️ Uma vez que você configure a regra de Divergência de valores, ela passa a valer para todos os marketplaces nos quais você seja seller.
 
 ## Editar regra de Divergência de valores
 
@@ -95,9 +93,7 @@ Uma vez concluídas as alterações desejadas, clique no botão **SALVAR REGRAS*
 
 Quando uma regra de autorização de pedido é configurada para _Criar uma tarefa no VTEX DO para aprovação_, isso significa que ao menos um usuário foi designado para autorizar manualmente o pedido. O [gerenciamento de pedidos com Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW#gerenciamento-de-pedidos-com-divergencia-de-valores) é similar ao de outros canais de venda, como loja física ou ecommerce.
 
-<div class="alert alert-warning">
-É importante acompanhar regularmente os pedidos pelo módulo <b>Pedidos</b>, em <b>Pedidos > Todos os pedidos</b>. Caso exijam aprovação manual, os pedidos com erro de divergência de valores permanecem pendentes, aguardando a autorização de um usuário habilitado, definido na criação da regra de autorização. Uma boa prática é ter ao menos dois usuários habilitados a autorizar a aprovação manual.
-</div>
+>⚠️ É importante acompanhar regularmente os pedidos pelo módulo **Pedidos**, em **Pedidos > Todos os pedidos**. Caso exijam aprovação manual, os pedidos com erro de divergência de valores permanecem pendentes, aguardando a autorização de um usuário habilitado, definido na criação da regra de autorização. Uma boa prática é ter ao menos dois usuários habilitados a autorizar a aprovação manual.
 
 Existem duas maneiras de um usuário habilitado autorizar manualmente um pedido com divergência de preço:
 
diff --git a/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md b/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
index 9a5dcc4f4..79a2120ec 100644
--- a/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
+++ b/docs/tutorials/pt/configuring-seller-allocation-for-buying-xky.md
@@ -45,8 +45,7 @@ Para atribuir sellers à uma determinada organização compradora, siga os passo
 A partir deste momento, sempre que a organização realizar uma busca na plataforma VTEX, serão exibidos apenas os produtos dos sellers atribuídos a ela.
 </ol>
 
-<div class="alert alert-warning">
-Organizações compradoras que não criem atribuições de sellers poderão acessar informações e realizar compras de todos os sellers disponíveis no marketplace.</div>
+>⚠️ Organizações compradoras que não criem atribuições de sellers poderão acessar informações e realizar compras de todos os sellers disponíveis no marketplace.
 
 Para mais informações sobre como integrar um novo seller, acesse [Adicionar seller](https://help.vtex.com/pt/tutorial/adicionar-seller--tutorials_392).
 
diff --git a/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md b/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
index 8c7463f81..25ed8f203 100644
--- a/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
+++ b/docs/tutorials/pt/configuring-sign-in-with-apple-id-beta.md
@@ -15,9 +15,7 @@ legacySlug: configurar-login-com-apple-id-beta
 subcategory: 5uXA9a0laSLMkfbv6jQRDS
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br).
 
 Na VTEX, não é necessário criar uma conta ou fazer login para realizar uma compra. No entanto, caso o cliente queira efetuar alguma alteração nos dados informados durante a primeira compra, é necessário que ele comprove a posse do email em questão.
 
@@ -72,9 +70,7 @@ Com tudo configurado, você já pode testar o login. Recomendamos que faça isso
 4. Realize a autenticação de dois fatores, se solicitada.
 5. Escolha se deseja compartilhar seu email com o app ou [ocultar o seu email](https://support.apple.com/pt-br/HT210425) e clique em `Continuar`. Recomendamos compartilhar o email, porque existem [limitações](#limitacoes) com relação ao email oculto na VTEX.
 
-<div class="alert alert-info">
-  <p>A opção por compartilhar ou não o email só aparece no primeiro acesso à loja com o Apple ID. Nas demais vezes, é necessário apenas clicar em <code>Continuar</code>. Para redefinir a opção de compartilhamento do email, visite o <a href="https://appleid.apple.com/br/">gerenciamento de Apple ID</a>, revogue a autorização da loja e volte a fazer login.</p>
-</div>
+>ℹ️ A opção por compartilhar ou não o email só aparece no primeiro acesso à loja com o Apple ID. Nas demais vezes, é necessário apenas clicar em `Continuar`. Para redefinir a opção de compartilhamento do email, visite o [gerenciamento de Apple ID](https://appleid.apple.com/br/), revogue a autorização da loja e volte a fazer login.
 
 Feito isso, você estará autenticado(a) na loja.
 
diff --git a/docs/tutorials/pt/configuring-spin-pay-gateway.md b/docs/tutorials/pt/configuring-spin-pay-gateway.md
index 5f7adb8db..2c1a30e7f 100644
--- a/docs/tutorials/pt/configuring-spin-pay-gateway.md
+++ b/docs/tutorials/pt/configuring-spin-pay-gateway.md
@@ -17,9 +17,7 @@ subcategory:
 
 Na VTEX, agora é possível oferecer o gateway [Spin Pay](https://spinpay.com.br/) para processar os pagamentos na sua loja. Com essa solução, você poderá receber via [PIX](https://help.vtex.com/pt/tutorial/pix-faq--3lx7zCU2lQroTEBCYKYbo3) e principais carteiras digitais disponíveis hoje no mercado.
 
-<div class="alert alert-warning">
-  Para utilizar o Spin Pay, na VTEX, é preciso que você tenha uma <b>Application Key (App Key)</b> e uma <b>Application Token (App Token)</b>. Esses dados são obtidos somente após a aprovação do seu cadastro pela Spin Pay e assinatura do contrato ou aceite do termo de adesão. Caso seu cadastro já tenha sido aprovado e o contrato assinado, siga as etapas a seguir.
-   </div>
+>⚠️ Para utilizar o Spin Pay, na VTEX, é preciso que você tenha uma **Application Key (App Key)** e uma **Application Token (App Token)**. Esses dados são obtidos somente após a aprovação do seu cadastro pela Spin Pay e assinatura do contrato ou aceite do termo de adesão. Caso seu cadastro já tenha sido aprovado e o contrato assinado, siga as etapas a seguir.
 
 Siga as etapas abaixo para configurar o Spin Pay na sua loja:
 
@@ -49,9 +47,7 @@ Com o gateway instalado em sua loja, é preciso configurar a [condição de paga
 9. Em __Usar Antifraude__, se você tiver uma solução contratada, habilite o campo e selecione a opção desejada.
 10. Clique em __Salvar__.
 
-<div class="alert alert-warning">
-  O Spin Pay é uma solução brasileira para pagamento instantâneo onde o débito acontece diretamente na conta do consumidor. Por este motivo, não é possível oferecer parcelamento.
-   </div>
+>⚠️ O Spin Pay é uma solução brasileira para pagamento instantâneo onde o débito acontece diretamente na conta do consumidor. Por este motivo, não é possível oferecer parcelamento.
 
 Com todas as etapas concluídas, o Spin Pay estará habilitado para processar os pagamentos em sua loja.
 
diff --git a/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md b/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md
index 0ac28ebf9..4d8293bb0 100644
--- a/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md
+++ b/docs/tutorials/pt/configuring-stripe-gateway-affiliation.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 A [Stripe](https://stripe.com/br) é uma plataforma de pagamentos que oferece um sistema integrado com foco no recebimento de pagamentos online e qualquer tipo de transação financeira comum a ecommerces e outros sites da web.
 
-<div class="alert alert-warning">
-A integração da sua loja com a Stripe é feita por meio de uma <strong>Application Key</strong> e <strong>Application Token</strong>. Para obter esses dados, primeiramente <a href="https://dashboard.stripe.com/register" target="_blank">crie sua conta na plataforma</a> e, ao finalizar, acesse <a href="https://stripe.com/docs/keys" target="_blank"> esta documentação da Stripe</a> para ter acesso à sua <strong>Chave publicável</strong> e <strong>Chave secreta</strong>. Elas são mandatórias para as configurações no ambiente VTEX.
-</div>
+>⚠️ A integração da sua loja com a Stripe é feita por meio de uma **Application Key** e **Application Token**. Para obter esses dados, primeiramente [crie sua conta na plataforma](https://dashboard.stripe.com/register" target="_blank) e, ao finalizar, acesse [ esta documentação da Stripe](https://stripe.com/docs/keys" target="_blank) para ter acesso à sua **Chave publicável** e **Chave secreta**. Elas são mandatórias para as configurações no ambiente VTEX.
 
 A Stripe suporta pagamentos em mais de 40 países. A lista de países disponíveis pode ser acessada no [site da Stripe](https://stripe.com/br/enterprise).
 
@@ -56,12 +54,13 @@ Após a configuração no ambiente VTEX, você também precisa configurar o Webh
 8. Clique em __Adicionar eventos__.
 9. Clique em __Adicionar endpoint__.
 
-<div class="alert alert-info">
-  <p>Caso você deseje realizar transações com cartão de crédito na Stripe, é necessário abrir um ticket na própria Stripe da seguinte maneira:</p>
-  <p>- Solicitar a liberação da função "raw card data", indicando que a VTEX e a Stripe são parceiros de pagamento.</p>
-  <p>- Encaminhar em anexo o AOC (Attestation of Compliance for Onsite Assessments – Service Providers) da VTEX. Para verificar a versão mais recente do AOC VTEX, acesse a página de <a href="https://vtex.com/br-pt/compliance/certifications">certificações da VTEX</a> e baixe o arquivo na seção PCI.</p>
-  <p>As ações acima evitarão que erros relacionados a transmissão de dados sensíveis ocorram na integração entre a Stripe e a VTEX.</p>
-</div>
+>ℹ️ Caso você deseje realizar transações com cartão de crédito na Stripe, é necessário abrir um ticket na própria Stripe da seguinte maneira:
+>
+> - Solicitar a liberação da função "raw card data", indicando que a VTEX e a Stripe são parceiros de pagamento.
+>
+> - Encaminhar em anexo o AOC (Attestation of Compliance for Onsite Assessments – Service Providers) da VTEX. Para verificar a versão mais recente do AOC VTEX, acesse a página de [certificações da VTEX](https://vtex.com/br-pt/compliance/certifications) e baixe o arquivo na seção PCI.
+>
+> As ações acima evitarão que erros relacionados a transmissão de dados sensíveis ocorram na integração entre a Stripe e a VTEX.
 
 ## Configurar condição de pagamento
 
@@ -86,9 +85,7 @@ Após esse procedimento, o Google Pay aparecerá no checkout da loja como um dos
 
 O conector Stripe permite adicionar o Apple Pay como método de pagamento no checkout da sua loja. 
 
-<div class="alert alert-warning">
-O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse <a href="https://support.apple.com/pt-br/HT208531">Dispositivos compatíveis com o Apple Pay</a>.
-</div>
+>⚠️ O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse [Dispositivos compatíveis com o Apple Pay](https://support.apple.com/pt-br/HT208531).
 
 Com o conector Stripe configurado, você pode adicionar o Apple Pay com os seguintes passos:
 
diff --git a/docs/tutorials/pt/configuring-telesales-features.md b/docs/tutorials/pt/configuring-telesales-features.md
index 02b680d2a..ba3eba170 100644
--- a/docs/tutorials/pt/configuring-telesales-features.md
+++ b/docs/tutorials/pt/configuring-telesales-features.md
@@ -60,6 +60,4 @@ Para isso, é necessário que a funcionalidade de preço manual tenha sido habil
 
 Preços manuais cadastrados no carrinho precisam ser aprovados pelo administrador da loja ou por um usuário com permissão no sistema de [Autorização de Pedidos](https://help.vtex.com/pt/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn) para que o pedido siga o fluxo de faturamento.
 
-<div class="alert alert-info">
-Não é possível alterar preços acessando a loja pela URL final  (<i>www.dominioloja.com.br</i>). A funcionalidade de preço manual no televendas só funciona se o operador acessar a loja pelo dominio <i>www.dominioloja.myvtex.com</i> e tiver a permissão de <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator">Call Center operator</a> em seu <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a>. 
-</div>
+>ℹ️ Não é possível alterar preços acessando a loja pela URL final  (<i>www.dominioloja.com.br</i>). A funcionalidade de preço manual no televendas só funciona se o operador acessar a loja pelo dominio <i>www.dominioloja.myvtex.com</i> e tiver a permissão de [Call Center operator](https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#call-center-operator) em seu [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc).
diff --git a/docs/tutorials/pt/configuring-the-global-checkout.md b/docs/tutorials/pt/configuring-the-global-checkout.md
index 1102089a5..5da4887d3 100644
--- a/docs/tutorials/pt/configuring-the-global-checkout.md
+++ b/docs/tutorials/pt/configuring-the-global-checkout.md
@@ -60,9 +60,7 @@ Suponha que você queira que a sua loja entregue para clientes na Inglaterra. Pa
 1. [Crie uma nova transportadora](/pt/tutorial/gerenciar-transportadora/);
 2. Crie, para a nova transportadora, uma planilha de frete com a coluna "Country" com o código ISO de 3 dígitos do país.
 
-<div class="alert alert-info">
-O valor da coluna "Country" deve ser o código ISO de 3 dígitos para países. Para consultar os códigos, recomendamos usar o site <a href="https://countrycode.org/">https://countrycode.org/</a>.
-</div>
+>ℹ️ O valor da coluna "Country" deve ser o código ISO de 3 dígitos para países. Para consultar os códigos, recomendamos usar o site [https://countrycode.org/](https://countrycode.org/).
 
 Após ter configurado as entregas para os países que deseja, um novo campo aparecerá no formulário de entrega no seu checkout permitindo a escolha de entegra internacional. 
 
diff --git a/docs/tutorials/pt/configuring-the-pickup-in-store.md b/docs/tutorials/pt/configuring-the-pickup-in-store.md
index 984c89211..e4efb6add 100644
--- a/docs/tutorials/pt/configuring-the-pickup-in-store.md
+++ b/docs/tutorials/pt/configuring-the-pickup-in-store.md
@@ -15,9 +15,7 @@ legacySlug: como-configurar-a-retirada-na-loja-pickup-store
 subcategory: 1c5Btie9ou2Gg2iUo0ggqM
 ---
 
-<div class="alert alert-danger">
-Este artigo está obsoleto. Para configurar corretamente o ponto de retirada, acesse o artigo <a href="https://help.vtex.com/pt/tutorial/configurar-pontos-de-retirada-pickup-points">Configurar Pontos de Retirada (Pickup Points)</a>
-</div>
+>❗ Este artigo está obsoleto. Para configurar corretamente o ponto de retirada, acesse o artigo [Configurar Pontos de Retirada (Pickup Points)](https://help.vtex.com/pt/tutorial/configurar-pontos-de-retirada-pickup-points)
 
 A configuração de retirada na loja possibilita ao cliente a escolha de não receber o produto em casa, e sim, ir buscá-lo em uma loja. Com os passos abaixo, é possível dar ao cliente a opção da escolha da loja que deseja retirar sua compra no checkout, durante o fluxo de compra. A configuração é realizada em 3 módulos diferentes da plataforma, descritos abaixo.
 
diff --git a/docs/tutorials/pt/configuring-the-rede-acquirer.md b/docs/tutorials/pt/configuring-the-rede-acquirer.md
index b0c8be469..f5cb88708 100644
--- a/docs/tutorials/pt/configuring-the-rede-acquirer.md
+++ b/docs/tutorials/pt/configuring-the-rede-acquirer.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Na VTEX, é possível realizar a integração com o adquirente Rede. Configurando o conector __ERedev2__, sua loja poderá aceitar pagamentos de cartões com as principais bandeiras.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: atualmente, a Rede conta com uma versão mais atualizada do conector. Para saber mais detalhes de como configurar esse adquirente, consulte o artigo sobre o [ERedeREST](https://help.vtex.com/pt/tutorial/configurar-adquirente-rede-con-erederest?locale=pt "ERedeREST"). 
-</div>
+>ℹ️ **Atenção**: atualmente, a Rede conta com uma versão mais atualizada do conector. Para saber mais detalhes de como configurar esse adquirente, consulte o artigo sobre o [ERedeREST](https://help.vtex.com/pt/tutorial/configurar-adquirente-rede-con-erederest?locale=pt "ERedeREST").
 
 Para configurar a Rede, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/configuring-the-scheduled-delivery.md b/docs/tutorials/pt/configuring-the-scheduled-delivery.md
index d3abc6f3f..dd13f76a5 100644
--- a/docs/tutorials/pt/configuring-the-scheduled-delivery.md
+++ b/docs/tutorials/pt/configuring-the-scheduled-delivery.md
@@ -15,10 +15,8 @@ legacySlug: como-funciona-a-entrega-agendada
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
-<a href="https://help.vtex.com/pt/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envio</a>.
-</div> 
+>ℹ️ Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
+> [estratégia de envio](https://help.vtex.com/pt/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl). 
 
 
 A entrega agendada é uma funcionalidade que permite definir períodos de entrega personalizados, podendo definir prazos e preços específicos, disponibilizando para o cliente a escolha do intervalo de horário em que deseja receber seu pedido. 
diff --git a/docs/tutorials/pt/configuring-the-store-domain.md b/docs/tutorials/pt/configuring-the-store-domain.md
index c833b7ff3..221582afb 100644
--- a/docs/tutorials/pt/configuring-the-store-domain.md
+++ b/docs/tutorials/pt/configuring-the-store-domain.md
@@ -82,13 +82,9 @@ Para cadastrar um novo host, ele deve estar de acordo com as práticas apresenta
 
 Após essas etapas, será possível [configurar o apontamento de DNS para a VTEX](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-  <p>Lojas <a href="https://www.faststore.dev/">FastStore</a> também precisam configurar um endereço com o subdomínio <code>secure</code>. Acesse o guia <a href="https://www.faststore.dev/docs/go-live/2-configuring-external-dns">Configuring external DNS for a custom domain</a> para mais detalhes.</p>
-</div>
+>⚠️ Lojas [FastStore](https://www.faststore.dev/) também precisam configurar um endereço com o subdomínio `secure`. Acesse o guia [Configuring external DNS for a custom domain](https://www.faststore.dev/docs/go-live/2-configuring-external-dns) para mais detalhes.
 
-<div class="alert alert-danger">
-  <p>Caso a sua operação possua mais de uma conta VTEX ou <a href="https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510">subcontas</a>, não troque o host de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.</p>
-</div>
+>❗ Caso a sua operação possua mais de uma conta VTEX ou [subcontas](https://help.vtex.com/pt/tutorial/como-criar-multiloja-multidominio--tutorials_510), não troque o host de uma conta para outra. Isso provocará falhas em diversos aspectos da sua loja.
 
 ## Mudar o host
 
diff --git a/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md b/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md
index 6f0c984fa..0a9d87e4f 100644
--- a/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md
+++ b/docs/tutorials/pt/configuring-tuna-gateway-affiliation.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Na VTEX, você pode configurar a sua loja com o gateway Tuna para receber pagamentos por meio de: boleto, cartões de débito, crédito, PIX e Bitcoin.
 
-<div class="alert alert-warning">
-  A integração da sua loja com a Tuna é feita por meio de uma <b>Application Key</b> e <b>Application Token.</b> Os dados de acesso para obter essas informações e permitir as configurações na VTEX serão enviados após a criação da sua conta. Para isso, preencha <a href="https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform">este formulário</a> e aguarde o retorno da Tuna com mais detalhes.
-  </div>
+>⚠️ A integração da sua loja com a Tuna é feita por meio de uma **Application Key** e **Application Token.** Os dados de acesso para obter essas informações e permitir as configurações na VTEX serão enviados após a criação da sua conta. Para isso, preencha [este formulário](https://docs.google.com/forms/d/e/1FAIpQLScWk5fsmkIfGaW2Z6qhdGH-JJ5iU6Fv5TGghUR1Pod5dY5Z2Q/viewform) e aguarde o retorno da Tuna com mais detalhes.
 
 Após ter criado sua conta e obtido as __Application Key__ e __Token__, siga as etapas abaixo para configurar a Tuna na sua loja:
 
diff --git a/docs/tutorials/pt/configuring-vtex-marketplace.md b/docs/tutorials/pt/configuring-vtex-marketplace.md
index e59c75c90..773a5c428 100644
--- a/docs/tutorials/pt/configuring-vtex-marketplace.md
+++ b/docs/tutorials/pt/configuring-vtex-marketplace.md
@@ -47,9 +47,7 @@ Para adicionar sellers ao seu marketplace pelo Admin VTEX, siga as instruções
 
 O [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é uma edição da plataforma VTEX que permite que sellers se conectem e vendam seus produtos em marketplaces. Marketplaces hospedados na VTEX podem convidar sellers que já têm uma conta VTEX para se conectarem por meio do Seller Portal. Também é possível convidar sellers hospedados em outras plataformas ou aqueles que ainda não estão hospedados em nenhuma plataforma para criar uma conta no Seller Portal de forma rápida e sem atritos.
 
-<div class="alert alert-info">
-Para ativar o Seller Portal para seus sellers, é necessário que o marketplace solicite essa funcionalidade entrando em contato com o CSM da sua conta na VTEX.
-</div>
+>ℹ️ Para ativar o Seller Portal para seus sellers, é necessário que o marketplace solicite essa funcionalidade entrando em contato com o CSM da sua conta na VTEX.
 
 Uma vez contratado o uso do Seller Portal, para adicionar sellers a uma conta de Seller Portal, siga as instruções em [Convite de Sellers](https://help.vtex.com/pt/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A).
 
@@ -85,9 +83,7 @@ Um marketplace pode obter a informação da localização do usuário na vitrine
 
 Quando o VTEX Session não tem acesso à localização do consumidor, ainda é preciso apontar um sortimento de produtos de sellers na experiência de compra. Nesse cenário, o algoritmo de seleção de sellers indica [sellers abrangentes](https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI), que são capazes de entregar pedidos em todas as regiões atendidas pelo seu marketplace.
 
-<div class="alert alert-info">
-A funcionalidade Region está adaptada apenas para lojas que utilizam o VTEX IO, e não é válida para o Portal CMS Legado. 
-</div>
+>ℹ️ A funcionalidade Region está adaptada apenas para lojas que utilizam o VTEX IO, e não é válida para o Portal CMS Legado.
 
 ## Configurar storefront
 
diff --git a/docs/tutorials/pt/configuring-xml.md b/docs/tutorials/pt/configuring-xml.md
index c6abbb370..0be7c1199 100644
--- a/docs/tutorials/pt/configuring-xml.md
+++ b/docs/tutorials/pt/configuring-xml.md
@@ -62,9 +62,7 @@ Com isso em mãos, siga os passos abaixo para configurar o seu XML:
 13. A partir daqui, preencha as *tags* conforme definido pelo sistema para o qual enviará o XML. Marque a caixa de seleção da coluna __Mostrar conteúdo__, nas tags que tiver preenchido o nome. As tags que já estiverem com essa opção marcada e cuja seleção não for possível desfazer são de preenchimento obrigatório.
 14. A URL usada para acessar o XML é gerada automaticamente, conforme o [domínio cadastrado no dicionário do Web Site](https://help.vtex.com/pt/tutorial/configurar-dominio-do-xml--2RkGK4vHS0c6sYuUw0cUWC), no __CMS__.
 
-<div class="alert alert-warning">
-  <p>Se a política comercial possuir restrição de acesso, o XML não será gerado.</p>
-</div>
+>⚠️ Se a política comercial possuir restrição de acesso, o XML não será gerado.
 
 ## Conectores nativos: uma alternativa ao XML para integrar com marketplaces
 
diff --git a/docs/tutorials/pt/coupons-beta.md b/docs/tutorials/pt/coupons-beta.md
index ebe4adb1f..c204deeea 100644
--- a/docs/tutorials/pt/coupons-beta.md
+++ b/docs/tutorials/pt/coupons-beta.md
@@ -21,9 +21,7 @@ Um cupom consiste em um código promocional, composto de uma sequência de letra
 
 É possível criar e editar cupons pelo Admin VTEX, em **Promoções** > [Cupons](https://help.vtex.com/pt/tutorial/lista-de-cupons-beta--5z5ya3IonsC2W4B5h4JrsZ), ou pela [Promotions & Taxes API v2](https://developers.vtex.com/vtex-rest-api/reference/promotions-taxes-api-v2).
 
-<div class="alert alert-warning">
-<p>Para ser utilizado, o cupom precisa estar vinculado a pelo menos uma promoção. É possível associar um cupom a qualquer tipo de promoção, exceto a <a href="https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume">Promoção de campanha</a>. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/criar-cupom-beta--7lMk3MmhNp2IEccyGApxU">Criar cupom (Beta)</a>.</p>
-</div>
+>⚠️ Para ser utilizado, o cupom precisa estar vinculado a pelo menos uma promoção. É possível associar um cupom a qualquer tipo de promoção, exceto a [Promoção de campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume). Saiba mais em [Criar cupom (Beta)](https://help.vtex.com/pt/tutorial/criar-cupom-beta--7lMk3MmhNp2IEccyGApxU).
 
 ## Tipos de cupons
 
diff --git a/docs/tutorials/pt/creating-a-campaign-audience.md b/docs/tutorials/pt/creating-a-campaign-audience.md
index e7ece28b4..01be8a00f 100644
--- a/docs/tutorials/pt/creating-a-campaign-audience.md
+++ b/docs/tutorials/pt/creating-a-campaign-audience.md
@@ -26,9 +26,7 @@ Siga os passos abaixo para criar uma nova audiência de campanha:
 5. Preencha os campos descritos na seção [Criar novo público-alvo](#criar-novo-publico-alvo).
 6. Clique em `Salvar`.
 
-<div class="alert alert-warning">
-  <p>Após criar uma audiência de campanha, é preciso associá-la a uma promoção de campanha para ter efeito. Siga os passos indicados no guia <a href="https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume">Criar promoção de campanha</a>.</p>
-</div>
+>⚠️ Após criar uma audiência de campanha, é preciso associá-la a uma promoção de campanha para ter efeito. Siga os passos indicados no guia [Criar promoção de campanha](https://help.vtex.com/pt/tutorial/promocao-de-campanha--1ChYXhK2AQGuS6wAqS8Ume).
 
 ## Dados gerais
 
@@ -45,10 +43,9 @@ Ao criar uma nova audiência de campanha, em **Quais os dados gerais desta audi
     * **Data Fim:** data de fim do agendamento da audiência de campanha, a partir da qual a audiência de campanha será válida.
     * **Hora Fim:** horário de fim do agendamento da audiência de campanha, a partir do qual audiência de campanha será válida.
 
-<div class="alert alert-warning">
-<p>Para agendar uma audiência de campanha, você precisa inserir <strong>Data Início</strong> ou <strong>Hora Início</strong> posteriores à data ou horário atual.</p>
-<p>O fuso horário considerado pelo sistema é o mesmo do dispositivo do usuário que criou a audiência de campanha – não há ajuste em relação a fusos horários diferentes.</p>
-</div>
+>⚠️ Para agendar uma audiência de campanha, você precisa inserir **Data Início** ou **Hora Início** posteriores à data ou horário atual.
+>
+> O fuso horário considerado pelo sistema é o mesmo do dispositivo do usuário que criou a audiência de campanha – não há ajuste em relação a fusos horários diferentes.
 
 ## Criar novo público-alvo
 
@@ -102,9 +99,7 @@ Exemplo: participam do público-alvo os itens cuja marca é __Nike__, conforme i
 * **O CEP de entrega deve Incluir / Excluir de __ até __:** permite incluir ou excluir intervalos de CEPs para envio de pedidos. A audiência de campanha será ativada caso o CEP atenda à regra configurada no público-alvo.
 * **Afiliados:** permite selecionar [afiliados](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) a partir de uma lista. A audiência de campanha será ativada se a compra for realizada em um marketplace dos afiliados selecionados.
 
-  <div class="alert alert-warning">
-    <p>A opção <strong>Afiliados</strong> se aplica somente se o afiliado for uma loja VTEX.</p>
-  </div>
+  >⚠️ A opção **Afiliados** se aplica somente se o afiliado for uma loja VTEX.
 
 * **utm_source:** permite selecionar a [utm_source](https://help.vtex.com/pt/tutorial/o-que-sao-utm_source-utm_campaign-e-utm_medium--2wTz7QJ8KUG6skGAoAQuii) desejada ou criar uma nova para vincular à audiência de campanha. A audiência de campanha será ativada caso a navegação do cliente seja realizada com a utm_source correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas uma utm_source no checkout.
 * **utm_campaign:** permite selecionar a [utm_campaign](https://help.vtex.com/pt/tutorial/o-que-sao-utm_source-utm_campaign-e-utm_medium--2wTz7QJ8KUG6skGAoAQuii) desejada ou criar uma nova para vincular à audiência de campanha. O desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
@@ -112,9 +107,7 @@ Exemplo: participam do público-alvo os itens cuja marca é __Nike__, conforme i
 * **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente:** a audiência de campanha será ativada somente após o cliente selecionar a forma de envio do pedido.
 * **Meio de pagamento:** permite selecionar os meios de pagamento que serão incluídos no público-alvo. A audiência de campanha será ativada se a forma de pagamento escolhida pelo cliente for a mesma cadastrada. 
 
-  <div class="alert alert-warning">
-    <p>Audiências de campanhas definidas por <strong>Meio de pagamento</strong> ou<strong> Número máximo de parcelas</strong> não atendem a pedidos pagos com dois cartões ou vale-compras.</p>
-  </div>
+  >⚠️ Audiências de campanhas definidas por **Meio de pagamento** ou** Número máximo de parcelas** não atendem a pedidos pagos com dois cartões ou vale-compras.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/creating-a-coupon-beta.md b/docs/tutorials/pt/creating-a-coupon-beta.md
index 25281403f..382d03e62 100644
--- a/docs/tutorials/pt/creating-a-coupon-beta.md
+++ b/docs/tutorials/pt/creating-a-coupon-beta.md
@@ -69,9 +69,7 @@ A seção **Geral** apresenta campos que você deve preencher com as informaçõ
     * **Número de cupons:** permite definir o número de códigos a serem gerados a partir do prefixo definido em **Código do cupom**. O número máximo é 1000.
     * **Exportar cupons:** botão que permite exportar os códigos do grupo de cupons. Essa opção fica disponível apenas ao editar um grupo de cupons já existente.
 
-<div class="alert alert-warning">
-<p>Ao menos uma das UTMs precisa ser definida, ou seja, é obrigatório preencher a <strong>UTM source</strong> ou a <strong>UTM campaign</strong>. Também é possível preencher ambos os campos.</p>
-</div>
+>⚠️ Ao menos uma das UTMs precisa ser definida, ou seja, é obrigatório preencher a **UTM source** ou a **UTM campaign**. Também é possível preencher ambos os campos.
 
 ### Restrições
 
@@ -81,9 +79,7 @@ Nesta seção do formulário, você pode configurar as seguintes restrições de
 
   Ao manter essa opção desativada, o cupom pode ser utilizado por uma quantidade ilimitada de vezes.
 
-  <div class="alert alert-warning">
-<p>Caso ocorra o cancelamento de um pedido com cupom de uso limitado, o limite será recalculado. Isso significa que pedidos com status <strong>Cancelado </strong>não contam no limite de vezes que o cupom poderá ser utilizado.</p>
-  </div>
+  >⚠️ Caso ocorra o cancelamento de um pedido com cupom de uso limitado, o limite será recalculado. Isso significa que pedidos com status **Cancelado **não contam no limite de vezes que o cupom poderá ser utilizado.
 
 ## Cupons gerados
 
diff --git a/docs/tutorials/pt/creating-a-coupon.md b/docs/tutorials/pt/creating-a-coupon.md
index 74e4d3130..02a2a72c9 100644
--- a/docs/tutorials/pt/creating-a-coupon.md
+++ b/docs/tutorials/pt/creating-a-coupon.md
@@ -30,9 +30,7 @@ Neste artigo vamos abordar:
 
 ## Como criar um cupom
 
-<div class="alert alert-warning">
-  <p>Há um limite para a quantidade de cupons ativos. Recomendamos reutilizar os cupons,  já que um número elevado pode comprometer o desempenho do módulo <b>Promoções e Taxas</b>.</p>
-</div>
+>⚠️ Há um limite para a quantidade de cupons ativos. Recomendamos reutilizar os cupons,  já que um número elevado pode comprometer o desempenho do módulo **Promoções e Taxas**.
 
 Para criar um cupom, siga os passos abaixo.
 
@@ -41,9 +39,7 @@ Para criar um cupom, siga os passos abaixo.
 3. Preencha os [campos de cadastro do cupom](#campos-de-cadastro-do-cupom).
 4. Clique no botão `Salvar`.
 
-<div class="alert alert-info">
-  <p>Você pode criar apenas um cupom por vez pelo Admin. Para criar cupons massivamente leia o guia <a href="https://developers.vtex.com/vtex-rest-api/docs/creating-and-managing-coupons-with-promotions-api">Creating and managing coupons with Promotions API</a>.</p>
-</div>
+>ℹ️ Você pode criar apenas um cupom por vez pelo Admin. Para criar cupons massivamente leia o guia [Creating and managing coupons with Promotions API](https://developers.vtex.com/vtex-rest-api/docs/creating-and-managing-coupons-with-promotions-api).
 
 ### Campos de cadastro do cupom
 
@@ -53,9 +49,7 @@ Nesta seção serão definidas as informações gerais do cupom.
 
 - **Código do Cupom:** código de ativação do cupom. Não há limite de caracteres e o campo é obrigatório.
 
-<div class="alert alert-warning">
-  <p>Não é possível usar caracteres especiais (somente letras, números e traços).</p>
-</div>
+>⚠️ Não é possível usar caracteres especiais (somente letras, números e traços).
 
 - **utm_source:** utm de origem.
 - **utm_campaign:** utm da campanha.
@@ -67,9 +61,7 @@ Nesta seção serão definidas as informações gerais do cupom.
 - **O cliente pode comprar até X produto(s), utilizando esse cupom em uma ou mais compras:** quantidade de produtos que podem ser comprados por este cupom, independentes de quantas compras sejam realizadas para atingir este número.
 - **Renovar cada utilização do cupom após X dia(s):**  a validade do cupom é renovada a partir da quantidade de dias determinados na seleção.
 
-<div class="alert alert-info">
-  <p>Para limitar o cupom a um único uso, é preciso <a href="https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327#4-restricoes-e-limitacoes-de-uso">restringir a quantidade de aplicações da promoção na sua loja e por cliente</a>.</p>
-</div>
+>ℹ️ Para limitar o cupom a um único uso, é preciso [restringir a quantidade de aplicações da promoção na sua loja e por cliente](https://help.vtex.com/pt/tutorial/promocao-regular--tutorials_327#4-restricoes-e-limitacoes-de-uso).
 
 Quando uma compra é realizada com uma promoção que possui limitação e essa compra é cancelada, esse uso da promoção volta a ser válido.
 
@@ -92,9 +84,7 @@ Para inativar um cupom é preciso arquivá-lo. Para arquivar um cupom, siga os p
 2. Selecione o cupom que deseja arquivar.
 3. Na tela de edição do cupom, clique no botão `Arquivar`.
 
-<div class="alert alert-warning">
-  <p>Cupons não podem ser deletados, apenas arquivados. É importante enfatizar que você só pode arquivar um cupom de cada vez. Você pode editar e reutilizar um cupom, mas o <b>código do cupom</b> não pode ser modificado.</p>
-</div>
+>⚠️ Cupons não podem ser deletados, apenas arquivados. É importante enfatizar que você só pode arquivar um cupom de cada vez. Você pode editar e reutilizar um cupom, mas o **código do cupom** não pode ser modificado.
 
 ## Cenário de aplicação
 
@@ -106,9 +96,7 @@ Para inativar um cupom é preciso arquivá-lo. Para arquivar um cupom, siga os p
 4. Insira o código do cupom na newsletter.
 5. A promoção será ativada no carrinho de compras somente quando o cliente preencher o campo **Cupom de desconto** e aplicar.
 
-<div class="alert alert-info">
-  <p>Também é possível configurar os links da newsletter diretamente com as <b>utm_source</b> e <b>utm_campaign</b> e dispensar o uso do cupom.</p>
-</div>
+>ℹ️ Também é possível configurar os links da newsletter diretamente com as **utm_source** e **utm_campaign** e dispensar o uso do cupom.
 
 ## Como usar múltiplos cupons
 
diff --git a/docs/tutorials/pt/creating-a-product-collection.md b/docs/tutorials/pt/creating-a-product-collection.md
index b5a91e39f..e0fff5aae 100644
--- a/docs/tutorials/pt/creating-a-product-collection.md
+++ b/docs/tutorials/pt/creating-a-product-collection.md
@@ -76,9 +76,7 @@ Para criar uma coleção de produtos que ainda não foram lançados ou que foram
 
 Não é possível selecionar os dois campos (**Pré-venda** e **Lançamento**) na mesma coleção. Caso queira que ambas os cenários sejam contemplados, crie duas coleções e configure cada uma com a respectiva opção.
 
-<div class="alert alert-warning">
-<p>Os campos <strong>Pré-venda</strong> e <strong>Lançamento</strong> só funcionam se você tiver selecionado no grupo alguma categoria, marca ou combinação de SKUs.</p>
-</div>
+>⚠️ Os campos **Pré-venda** e **Lançamento** só funcionam se você tiver selecionado no grupo alguma categoria, marca ou combinação de SKUs.
 
 ### Incluir SKUs específicos em um grupo
 
@@ -109,9 +107,7 @@ Depois que a planilha for importada pelo sistema, os SKUs são apresentados da s
 
 SKUs que estiverem inativos não terão seus IDs importados mesmo que estejam incluídos na planilha.
 
-<div class="alert alert-warning">
-<p>Ao selecionar mais de um tipo de grupo, apenas os produtos na interseção desses dois conjuntos estarão na coleção. Por exemplo, se você selecionar categoria AA e marca BB, apenas os produtos que forem dessa categoria e dessa marca estarão na coleção. Os produtos da categoria AA de outra marca não estarão na coleção, assim como produtos da marca BB de outras categorias não estarão na coleção.</p>
-</div>
+>⚠️ Ao selecionar mais de um tipo de grupo, apenas os produtos na interseção desses dois conjuntos estarão na coleção. Por exemplo, se você selecionar categoria AA e marca BB, apenas os produtos que forem dessa categoria e dessa marca estarão na coleção. Os produtos da categoria AA de outra marca não estarão na coleção, assim como produtos da marca BB de outras categorias não estarão na coleção.
 
 ### Excluir múltiplos SKUs de uma coleção
 
diff --git a/docs/tutorials/pt/creating-a-product-for-presale.md b/docs/tutorials/pt/creating-a-product-for-presale.md
index 3ef52115d..c724174bc 100644
--- a/docs/tutorials/pt/creating-a-product-for-presale.md
+++ b/docs/tutorials/pt/creating-a-product-for-presale.md
@@ -34,15 +34,11 @@ Para disponibilizar um produto via pré-venda, siga os passos abaixo.
 5. Preencha os [restantes campos do produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke).
 6. Clique em `Salvar e Cadastrar um novo SKU`.
 7. Na página de criação do SKU, preencha o campo **Data Previsão Chegada (pré-venda)** com a data em que o produto estará disponível para entrega pela loja no formato `dd/mm/aaaa`.
-<div class="alert alert-info">
-  <p>É preciso levar em consideração tanto a data de lançamento quanto o cálculo do frete para o cadastro da data de chegada: <code>tempo final de entrega = SLA de entrega + prazo de recebimento do lote de abastecimento</code></p>  
-</div>
+>ℹ️ É preciso levar em consideração tanto a data de lançamento quanto o cálculo do frete para o cadastro da data de chegada: `tempo final de entrega = SLA de entrega + prazo de recebimento do lote de abastecimento`
 8. Preencha os [restantes campos do SKU](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY).
 9. Clique em `Salvar` para finalizar.
 
-<div class="alert alert-info">
-  <p>O pedido do item em pré-venda só deverá ser faturado a partir da data de lançamento, isto é, quando haverá a disponibilidade real de estoque do produto.</p>  
-</div>
+>ℹ️ O pedido do item em pré-venda só deverá ser faturado a partir da data de lançamento, isto é, quando haverá a disponibilidade real de estoque do produto.
 
 ## Agendar preços
 Para agendar os preços fixos da sua loja para a pré-venda de um produto, siga os passos descritos no artigo [Agendar preços](https://help.vtex.com/pt/tutorial/agendar-preco--4vVha6TGzYkguWuMOqCcCk). 
diff --git a/docs/tutorials/pt/creating-a-shipping-policy.md b/docs/tutorials/pt/creating-a-shipping-policy.md
index 4439b2c3c..91ae7649a 100644
--- a/docs/tutorials/pt/creating-a-shipping-policy.md
+++ b/docs/tutorials/pt/creating-a-shipping-policy.md
@@ -51,9 +51,7 @@ Para criar uma nova política de envio, siga os passos abaixo:
         *   Selecione o `Dia da semana` e preencha o `Horário da coleta`. 
         *   Para adicionar mais dias da semana, clique em `Adicionar horário de coleta`.
 
-<div class="alert alert-warning">
-A <b>Janela de envio</b> e <b>Horário de coleta</b> são opções excludentes, pois um mesmo período não pode ser simultaneamente destinado a ações diferentes.
-</div>
+>⚠️ A **Janela de envio** e **Horário de coleta** são opções excludentes, pois um mesmo período não pode ser simultaneamente destinado a ações diferentes.
 
 *   **[Entrega agendada:](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)** essa funcionalidade pode ser habilitada caso a política de envio ofereça o serviço de entrega agendada. É aqui que você deverá adicionar as janelas de entrega que ficarão disponíveis para o cliente ao final da compra. Para utilizar, habilite `entrega agendada` e preencha:
     *   **Tempo máximo de entrega:** define o tempo máximo de entrega, deve ser preenchido com o tempo em dias.
diff --git a/docs/tutorials/pt/creating-a-subscription-plan.md b/docs/tutorials/pt/creating-a-subscription-plan.md
index cdc9b7482..28691aa62 100644
--- a/docs/tutorials/pt/creating-a-subscription-plan.md
+++ b/docs/tutorials/pt/creating-a-subscription-plan.md
@@ -23,9 +23,7 @@ Existem dois caminhos possíveis para criar um plano de assinatura. O caminho **
 
 Outra possibilidade é criar um [Anexo de SKU referente à assinatura no Catálogo](#caminho-alternativo-anexo-de-sku-no-catalogo). O Anexo de SKU é equivalente ao plano.
 
-<div class="alert alert-warning">
-  <p>Você <strong>não</strong> deve realizar ambas as configurações, basta optar por uma delas. Crie apenas o novo plano no módulo de <strong>Assinaturas</strong> ou o anexo de SKU no <strong>Catálogo</strong>. Caso contrário, o plano será duplicado.</p>
-</div>
+>⚠️ Você **não** deve realizar ambas as configurações, basta optar por uma delas. Crie apenas o novo plano no módulo de **Assinaturas** ou o anexo de SKU no **Catálogo**. Caso contrário, o plano será duplicado.
 
 ## Novo plano no módulo de Assinaturas
 
@@ -37,9 +35,7 @@ Criar um novo plano a partir do módulo de **Assinaturas** é o caminho mais rec
 4. Clique na aba [Produtos Associados](#produtos-associados) e selecione os produtos que você deseja associar aos planos de assinatura.
 5. Clique em `Salvar`.
 
-<div class="alert alert-warning">
-  <p>Todo plano é salvo como ativo, mesmo que não tenha nenhum produto associado. Planos sem produtos associados não aparecem como opção para o cliente no momento da compra.</p>
-</div>
+>⚠️ Todo plano é salvo como ativo, mesmo que não tenha nenhum produto associado. Planos sem produtos associados não aparecem como opção para o cliente no momento da compra.
 
 ### Configurações
 
@@ -69,9 +65,7 @@ Para excluir uma frequência criada anteriormente, você precisa clicar no botã
 
 Você pode disponibilizar múltiplas opções de frequência no mesmo plano, se desejar. Nesse caso, você deve clicar novamente no botão `Adicionar frequência` e repetir esse processo, preenchendo as configurações com as outras frequências desejadas. Dessa forma, o cliente poderá escolher a frequência que preferir dentre as opções.
 
-<div class="alert alert-warning">
-  <p>Não é possível atribuir um prazo de validade ao plano de assinatura pelo módulo de <strong>Assinaturas</strong>. Somente planos de assinatura configurados como Anexos de SKU no <strong>Catálogo</strong> podem ter prazos de validade configurados.</p>
-</div>
+>⚠️ Não é possível atribuir um prazo de validade ao plano de assinatura pelo módulo de **Assinaturas**. Somente planos de assinatura configurados como Anexos de SKU no **Catálogo** podem ter prazos de validade configurados.
 
 ### Produtos Associados
 
diff --git a/docs/tutorials/pt/creating-a-trade-policy.md b/docs/tutorials/pt/creating-a-trade-policy.md
index 6324acc52..fafac0af5 100644
--- a/docs/tutorials/pt/creating-a-trade-policy.md
+++ b/docs/tutorials/pt/creating-a-trade-policy.md
@@ -17,9 +17,7 @@ subcategory: 6J3wx7KM4oysymsWuUACyY
 
 [Políticas comerciais](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) são usadas na VTEX para agrupar configurações de catálogo, preços, promoções, inventário, logística, segmentação de clientes e pagamentos para diferentes canais de venda. Canais de venda podem incluir marketplaces, ecommerce próprio, lojas físicas, ou lojas B2B, por exemplo.
 
-<div class="alert alert-danger">
-Por padrão, novas políticas comerciais são aplicadas a todos os sellers ativos. Se desejar aplicar apenas a um grupo específico de sellers, por favor informe isto no ticket.
-</div>
+>❗ Por padrão, novas políticas comerciais são aplicadas a todos os sellers ativos. Se desejar aplicar apenas a um grupo específico de sellers, por favor informe isto no ticket.
 
 ## Gerenciar políticas comerciais
 
@@ -33,9 +31,7 @@ Para utilizar o mesmo catálogo em mais de uma política comercial, acesse a doc
 
 Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta solicitar via [suporte VTEX](https://help.vtex.com/pt/support) selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`. Ao solicitar a criação de uma política comercial via ticket, considere um tempo de resposta de até três dias úteis.
 
-<div class="alert alert-info">
-Para que o uso de política comercial adicional para integrar com <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conector nativo</a>, <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> ou outras lojas VTEX seja isenta de taxas, é encessário que pedidos sejam associados a ela.
-</div>
+>ℹ️ Para que o uso de política comercial adicional para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX seja isenta de taxas, é encessário que pedidos sejam associados a ela.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/creating-a-type-of-list.md b/docs/tutorials/pt/creating-a-type-of-list.md
index f2c36a88a..8e41cb026 100644
--- a/docs/tutorials/pt/creating-a-type-of-list.md
+++ b/docs/tutorials/pt/creating-a-type-of-list.md
@@ -26,9 +26,7 @@ A criação de um tipo de lista é a configuração de quais listas o site terá
 
 Após a criação dos tipos de listas, será possível que clientes criem efetivamente suas listas no site.
 
-<div class="alert alert-warning">
-  <p>Não é possível excluir uma lista após ela ter sido gerada.</p>
-</div>
+>⚠️ Não é possível excluir uma lista após ela ter sido gerada.
 
 ## Campos do formulário
 
diff --git a/docs/tutorials/pt/creating-an-oauth2-authentication.md b/docs/tutorials/pt/creating-an-oauth2-authentication.md
index eb9e2adcb..f82820761 100644
--- a/docs/tutorials/pt/creating-an-oauth2-authentication.md
+++ b/docs/tutorials/pt/creating-an-oauth2-authentication.md
@@ -21,7 +21,7 @@ Para alguns lojistas, existe a necessidade de criar uma autenticação adicional
 
 Por conta disso, a VTEX disponibiliza autenticação OAuth2 integrada ao VTEX ID.
 
-<div class="alert alert-warning">Como este é um assunto com aspectos bastante técnicos, recomendamos o acompanhamento de um parceiro ou equipe de TI.</div>
+>⚠️ Como este é um assunto com aspectos bastante técnicos, recomendamos o acompanhamento de um parceiro ou equipe de TI.
 
 ## O que é OAuth2
 
@@ -156,7 +156,7 @@ Response:
 
 Assim que o serviço estiver desenvolvido e público na internet, todos os dados de configuração devem ser encaminhados à VTEX (via ticket de suporte) para que seja configurado o ambiente da loja e integrado ao VTEX ID, disponibilizando mais uma opção de login para seus clientes.
 
-<div class="alert alert-info">Se você tiver múltiplas lojas (subcontas) listadas em <strong>Configurações da conta > Gerenciamento da conta > Conta</strong>, cada uma exigirá sua própria configuração de provedor de identidade OAuth2.</div>
+>ℹ️ Se você tiver múltiplas lojas (subcontas) listadas em **Configurações da conta > Gerenciamento da conta > Conta**, cada uma exigirá sua própria configuração de provedor de identidade OAuth2.
 
 Em resumo, são eles:
 
diff --git a/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md b/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
index 97d89ab47..633677615 100644
--- a/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
+++ b/docs/tutorials/pt/creating-an-xml-with-promotional-price-using-a-price-table.md
@@ -23,9 +23,7 @@ Com o fim de aplicar um preço diferenciado a produtos pelo XML, é preciso asso
   3. Aqui, você deve checar se os campos relacionados ao preço do SKU (Menor Preço do Produto, Maior Preço do Produto, Preço Original do SKU, Preço Atual do SKU e Preço Atual do SKU + Taxas) estão preenchidos. Pelo menos um dos campos deve ser preenchido para a operação funcionar corretamente.
   4. Preencha o campo **Tabelas de Preços** com o nome da tabela de preços desejada. Em seguida, clique na caixa de seleção referente à tag na coluna **Exibe Conteúdo**. É necessário que a tabela de preços selecionada tenha preços fixos cadastrados. Caso contrário, a configuração não será realizada.
 ![PT-tabela de precos](https://images.ctfassets.net/alneenqid6w5/3WM4imKTVz2bpddr5MO1X1/b3741b0744059913db5a9eda668f7d0f/PT-tabela_de_precos.png)
-<div class="alert alert-warning">
-  <p>Uma vez que a tabela de preços seja incluída no XML, todos os campos de preço serão sobrescritos.</p>
-</div>
+>⚠️ Uma vez que a tabela de preços seja incluída no XML, todos os campos de preço serão sobrescritos.
   5. Clique em `Salvar`.
 
 Assim, a plataforma vai associar os valores da tabela de preços com os produtos cadastrados na coleção do arquivo XML.
diff --git a/docs/tutorials/pt/creating-appkeys-and-apptokens-to-authenticate-integrations.md b/docs/tutorials/pt/creating-appkeys-and-apptokens-to-authenticate-integrations.md
index 1b01138ce..3f24ffac0 100644
--- a/docs/tutorials/pt/creating-appkeys-and-apptokens-to-authenticate-integrations.md
+++ b/docs/tutorials/pt/creating-appkeys-and-apptokens-to-authenticate-integrations.md
@@ -17,8 +17,7 @@ subcategory: 4uqMnZjwBO04uWgCom8QiA
 
 Toda integração com APIs VTEX precisa se autenticar por meio de appKey e appToken.
 
-<div class="alert alert-warning">Apenas o <b>usuário Master</b> da loja tem permissão para manipular tokens. O usuário Master é aquele cujo e-mail consta na seção <b>Contato</b> da tela Contas, no License Manager.
-</div>
+>⚠️ Apenas o **usuário Master** da loja tem permissão para manipular tokens. O usuário Master é aquele cujo e-mail consta na seção **Contato** da tela Contas, no License Manager.
 
 Para gerar essas chaves, siga os passos abaixo:
 
@@ -30,8 +29,7 @@ Para gerar essas chaves, siga os passos abaixo:
 6. Clique em __Gerar novos tokens__.
 7. No campo que é exibido em seguida, fica o token. Por uma questão de segurança, ele é __exibido apenas uma vez__. Copie esse token e guarde-o em local seguro.
 
-<div class="alert alert-warning"><strong>Atenção</strong>: todo par de appKey e appToken, quando é criado, nasce sem estar vinculado a um perfil de acessso. Então, depois de criá-lo, é necessário vinculá-lo ao perfil de acesso desejado.
-</div>
+>⚠️ **Atenção**: todo par de appKey e appToken, quando é criado, nasce sem estar vinculado a um perfil de acessso. Então, depois de criá-lo, é necessário vinculá-lo ao perfil de acesso desejado.
 
 Para isso, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md b/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md
index 5c42d203b..208fd6fe6 100644
--- a/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md
+++ b/docs/tutorials/pt/creating-customer-and-address-forms-in-new-stores.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 No Master Data, os formulários de Cliente e Endereço não são criados por padrão em todas as novas lojas. Estão presentes somente na loja principal da conta. Este cenário é recorrente nos casos em que são criadas multi-lojas.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 É possível criar estes formulários automaticamente, bastando seguir as instruções abaixo para cada loja que desejar.
 
diff --git a/docs/tutorials/pt/creating-data-entity.md b/docs/tutorials/pt/creating-data-entity.md
index e14d9e184..5f18d52c4 100644
--- a/docs/tutorials/pt/creating-data-entity.md
+++ b/docs/tutorials/pt/creating-data-entity.md
@@ -23,21 +23,16 @@ Para exemplificar, imagine um sistema de controle de uma biblioteca. Esse sistem
 
 Com esses conceitos, é possível configurar os mais diversos cenários de controle de dados pelo Master Data. Por padrão, são inseridas as seguintes entidades de dados: Cliente, Endereço, Stores etc. É possível criar quantas mais entidades de dados desejar, possibilitando um ambiente personalizado, voltado às necessidade de cada loja.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href=”https://developers.vtex.com/vtex-rest-api/docs/getting-started-1”>
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href=”https://developers.vtex.com/vtex-rest-api/docs/getting-started-1”>
+> Master Data v2
+> </a>
+> 
 
 ## Entendendo os tipos
 
diff --git a/docs/tutorials/pt/creating-landing-pages.md b/docs/tutorials/pt/creating-landing-pages.md
index d41f5570f..1650851aa 100644
--- a/docs/tutorials/pt/creating-landing-pages.md
+++ b/docs/tutorials/pt/creating-landing-pages.md
@@ -21,10 +21,7 @@ No Admin, você pode criar landing pages personalizadas, como páginas para ofer
 
 1. No Admin VTEX, acesse **Storefront > Páginas**.
 
-<div class="alert alert-warning">
-  <p> Se sua loja tem múltiplas políticas comerciais ou é uma loja internacional, selecione o <a href="https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W">binding</a> correspondente à loja à qual você deseja adicionar uma nova landing page usando o menu suspenso no canto superior direito.
-</p>
-</div>
+>⚠️ Se sua loja tem múltiplas políticas comerciais ou é uma loja internacional, selecione o [binding](https://help.vtex.com/en/tutorial/o-que-e-binding--4NcN3NJd0IeYccgWCI8O2W) correspondente à loja à qual você deseja adicionar uma nova landing page usando o menu suspenso no canto superior direito.
 
 2.Clique em **CRIAR PÁGINA**.
 
@@ -40,10 +37,7 @@ No Admin, você pode criar landing pages personalizadas, como páginas para ofer
 | Descrição | Resumo da nova página que será exibida nas páginas de resultados dos mecanismos de busca. |
 | Palavras-chave | Tópicos que definem o conteúdo da página e ajudam a mostrar a página aos usuários interessados nos resultados dos mecanismos de busca. |
 
-<div class="alert alert-warning">
-<p>Para evitar conflitos e garantir a integridade do sistema, não é permitida a alteração da URL de uma rota já existente. Caso precise modificar uma URL, recomenda-se criar uma nova página com o caminho desejado e desativar a antiga, se necessário.
-</p>
-</div>
+>⚠️ Para evitar conflitos e garantir a integridade do sistema, não é permitida a alteração da URL de uma rota já existente. Caso precise modificar uma URL, recomenda-se criar uma nova página com o caminho desejado e desativar a antiga, se necessário.
 
 <div class = "alert alert-info">
 <p>Os cinco campos acima têm um impacto direto nos acessos à loja e em seu posicionamento nos resultados dos mecanismos de busca. Ao preencher os metadados da página, considere as melhores práticas de SEO.
diff --git a/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md b/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md
index a4a868911..692f4dcf0 100644
--- a/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md
+++ b/docs/tutorials/pt/creating-merchandising-rules-manual-editor.md
@@ -33,9 +33,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
     Para aplicar o efeito de customização desejado, é necessário cadastrar uma ou mais condições nesta etapa. Para entender como funciona o cadastro de uma condição, leia [Condições de Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3Dvava8LSVcFKeS2S6J7XW).
 10. Clique em `Salvar`.
 
-<div class="alert alert-info">
-<p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
-</div>
+>ℹ️ Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.
 
 ## Exemplo
 
@@ -78,9 +76,7 @@ Considere o seguinte exemplo: você quer promover produtos da marca Beautyx dura
 
 * **Remover:** exclui as condições selecionadas do resultado, ou seja, remove produtos que estariam no resultado de busca.
 
-  <div class="alert alert-info">
-   <p><strong>Adicionar</strong> e <strong>Remover</strong> são compatíveis com outros tipos de ordenação que não são baseadas na relevância configurada. Ou seja, se você adicionar ou remover um produto através de uma regra de merchandising e o cliente da sua loja ordenar os resultados da busca por preço, por exemplo, os produtos serão ordenados por preço mas os produtos exibidos vão respeitar a regra de merchandising.</p>
-  </div>
+  >ℹ️ **Adicionar** e **Remover** são compatíveis com outros tipos de ordenação que não são baseadas na relevância configurada. Ou seja, se você adicionar ou remover um produto através de uma regra de merchandising e o cliente da sua loja ordenar os resultados da busca por preço, por exemplo, os produtos serão ordenados por preço mas os produtos exibidos vão respeitar a regra de merchandising.
 
 * **Promover:** oferece destaque às condições selecionadas no resultado. Isso concede maior relevância a um produto que já seria exibido no resultado de busca.
 
@@ -88,10 +84,6 @@ Considere o seguinte exemplo: você quer promover produtos da marca Beautyx dura
 
 * **Despromover**: oculta as condições selecionadas no resultado. Isso permite despriorizar um produto que já seria exibido no resultado de busca.
 
-  <div class="alert alert-info">
-   <p><strong>Promover </strong>e <strong>Despromover </strong>funcionam somente quando o cliente da sua loja ordena os resultados da busca por relevância. Caso ele(a) ordene os resultados por preço, por exemplo, os produtos serão ordenados estritamente pelo preço e a regra de merchandising não será utilizada.</p>
-  </div>
+  >ℹ️ **Promover **e **Despromover **funcionam somente quando o cliente da sua loja ordena os resultados da busca por relevância. Caso ele(a) ordene os resultados por preço, por exemplo, os produtos serão ordenados estritamente pelo preço e a regra de merchandising não será utilizada.
 
-  <div class="alert alert-warning">
-   <p>Não configure condições que afetem os mesmos produtos nas seções <strong>Promover</strong> e <strong>Despromover</strong>, pois são efeitos contrários. Essa configuração equivocada influencia negativamente no comportamento da funcionalidade e não apresenta os resultados desejados.</p>
-  </div>
+  >⚠️ Não configure condições que afetem os mesmos produtos nas seções **Promover** e **Despromover**, pois são efeitos contrários. Essa configuração equivocada influencia negativamente no comportamento da funcionalidade e não apresenta os resultados desejados.
diff --git a/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md b/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
index 7759c4685..8862817df 100644
--- a/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
+++ b/docs/tutorials/pt/creating-merchandising-rules-visual-editor-beta.md
@@ -15,9 +15,7 @@ legacySlug: criar-regra-de-merchandising-editor-visual-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0) do VTEX Intelligent Search utilizando o [Editor visual](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0#tipos-de-edicao), siga os passos abaixo.
 
@@ -45,9 +43,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
     Saiba mais sobre essas ações nos itens **IV, V, VI, VIII, IX** e **XI** da seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual]).
 9. Clique em `Salvar`.
 
-<div class="alert alert-info">
-  <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
-</div>
+>ℹ️ Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.
 
 ## Ações disponíveis no Editor visual
 
diff --git a/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md b/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
index 73feaab83..c91fd7dc9 100644
--- a/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
+++ b/docs/tutorials/pt/creating-merchandising-rules-visual-editor.md
@@ -41,9 +41,7 @@ Para configurar uma [regra de merchandising](https://help.vtex.com/pt/tracks/vte
     Saiba mais sobre essas ações nos itens **IV, V, VI, VIII, IX** e **XI** da seção [Ações disponíveis no Editor visual](#acoes-disponiveis-no-editor-visual]).
 9. Clique em `Salvar`.
 
-<div class="alert alert-info">
-  <p>Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.</p>
-</div>
+>ℹ️ Após salvar, as alterações de regras de merchandising levam em média dois minutos para serem atualizadas.
 
 ## Ações disponíveis no Editor visual
 
diff --git a/docs/tutorials/pt/creating-pickup-points.md b/docs/tutorials/pt/creating-pickup-points.md
index e1ff6cece..1fdea9359 100644
--- a/docs/tutorials/pt/creating-pickup-points.md
+++ b/docs/tutorials/pt/creating-pickup-points.md
@@ -24,9 +24,7 @@ Há duas formas de cadastrar pontos de retirada pelo Admin:
 * [Cadastro individual](#cadastro-individual).
 * [Cadastro por planilha](#cadastro-por-planilha).
 
-<div class="alert alert-warning">
-O cadastro dos pontos de retirada é um dos passos para o funcionamento correto da funcionalidade. Confira o artigo <a href="https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R">Pontos de retirada</a> e veja as demais <a href="https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#como-configurar">configurações necessárias</a> para disponibilizar os pontos de retirada para os seus clientes.
-</div>
+>⚠️ O cadastro dos pontos de retirada é um dos passos para o funcionamento correto da funcionalidade. Confira o artigo [Pontos de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) e veja as demais [configurações necessárias](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R#como-configurar) para disponibilizar os pontos de retirada para os seus clientes.
 
 ## Cadastro individual
 
@@ -43,9 +41,7 @@ O cadastro dos pontos de retirada é um dos passos para o funcionamento correto
 * **ID:** identificação do ponto de retirada. Se não for preenchido, o sistema escolherá um ID automaticamente. Não utilize caracteres de espaço.
 * **Ponto de retirada de terceiros:** marque com <i class="far fa-check-square"></i>  se o ponto de retirada não for um endereço relacionado à sua loja. Endereços de terceiros são sugeridos com menos relevância do que pontos da própria loja.
 
-  <div class="alert alert-danger">
-A configuração <b>Ponto de retirada de terceiros</b> atualmente não está disponível. 
-</div>
+  >❗ A configuração **Ponto de retirada de terceiros** atualmente não está disponível.
 
 Selecione <i class="fas fa-toggle-on"></i> para que o ponto de retirada fique ativo.
 
@@ -76,9 +72,7 @@ As informações de endereço e a localização no mapa serão exibidas no check
     4. Preencha **Dia** e **Horário;**
     5. Clique em`Adicionar`.
 
-<div class="alert alert-warning">
-O horário de funcionamento cadastrado no ponto de retirada é apenas informativo para o cliente, mas não é utilizado para o cálculo do SLA. Para alterar as configurações que influenciam no prazo de entrega, é preciso estabelecer o horário de funcionamento na <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">política de envio</a> relacionada ao ponto de retirada. No caso do cadastro de feriados, as configurações devem ser feitas pela seção de <a href="https://help.vtex.com/pt/tutorial/registrar-feriados--2ItOthSEAoyAmcwsuiO6Yk">feriados</a> para que influenciem no cálculo de prazo.
-</div>
+>⚠️ O horário de funcionamento cadastrado no ponto de retirada é apenas informativo para o cliente, mas não é utilizado para o cálculo do SLA. Para alterar as configurações que influenciam no prazo de entrega, é preciso estabelecer o horário de funcionamento na [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) relacionada ao ponto de retirada. No caso do cadastro de feriados, as configurações devem ser feitas pela seção de [feriados](https://help.vtex.com/pt/tutorial/registrar-feriados--2ItOthSEAoyAmcwsuiO6Yk) para que influenciem no cálculo de prazo.
 
 ## Cadastro por planilha
 
diff --git a/docs/tutorials/pt/creating-price-tables.md b/docs/tutorials/pt/creating-price-tables.md
index fa7f24a13..de02e451c 100644
--- a/docs/tutorials/pt/creating-price-tables.md
+++ b/docs/tutorials/pt/creating-price-tables.md
@@ -32,11 +32,7 @@ Para criar uma Tabela de Preços siga os seguintes passos:
 
 Para incluir preços na tabela de preços, você precisará cadastrar um preço base aos seus SKUs. Veja como fazer neste [tutorial](https://help.vtex.com/pt/tutorial/cadastrar-o-preco-base-de-um-produto--4S9SbPWlVmOAAWO6yq8wE6).
 
-<div class="alert alert-info">
-Não é possível criar tabelas de preço com nomes iguais.
-Não é possível adicionar caracteres especiais aos nomes das tabelas de preços. Apenas letras e números.
-</div>
-
-<div class="alert alert-warning">
-Por questões de segurança, não é possível excluir tabelas de preço manualmente. Caso precise deletar uma tabela de preço, abra um chamado com o suporte da VTEX.
-</div>
+>ℹ️ Não é possível criar tabelas de preço com nomes iguais.
+> Não é possível adicionar caracteres especiais aos nomes das tabelas de preços. Apenas letras e números.
+
+>⚠️ Por questões de segurança, não é possível excluir tabelas de preço manualmente. Caso precise deletar uma tabela de preço, abra um chamado com o suporte da VTEX.
diff --git a/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md b/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
index b59d3d213..1ece950f2 100644
--- a/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
+++ b/docs/tutorials/pt/creating-promotion-for-a-customer-cluster.md
@@ -33,11 +33,7 @@ Com a propriedade definida, siga as instruções abaixo.
 6. Preencha o campo com o cluster que deseja relacionar à promoção — [veja abaixo mais informações sobre como preencher este campo](#como-preencher-o-campo-cluster-de-clientes). Você pode adicionar mais de um cluster, clicando no botão `+`.
 7. Clique no botão `Salvar`.
 
-<div class="alert alert-info">
-<p>
-Você pode inserir no máximo 50 clusters na opção <strong>Cluster de clientes</strong>. 
-</p>
-</div>
+>ℹ️ Você pode inserir no máximo 50 clusters na opção **Cluster de clientes**.
 
 ## Como preencher o campo Cluster de clientes
 
@@ -48,11 +44,7 @@ Existem dois critérios possíveis para a seleção de um cluster para a promoç
 
 Perceba que, em ambas opções, `{nomedapropriedade}` deve ser alterado pelo nome do campo na entidade de dados e `{valor}` deve ser substituído pelo valor definido no Master Data.
 
-<div class="alert alert-info">
-<p>
-O uso das aspas duplas varia <a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos">de acordo com o tipo de campo</a> criado no Master Data.
-</p>
-</div>
+>ℹ️ O uso das aspas duplas varia [de acordo com o tipo de campo](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos) criado no Master Data.
 
 ### Função de igualdade
 
@@ -68,11 +60,7 @@ Dessa forma, você poderia configurar também `funcionario=false`, em que apenas
 
 Considerando um campo do tipo **[Varchar](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#entendendo-os-tipos)**, poderíamos configurar `funcionario="sim"` para que apenas clientes com valor `"sim"` no campo recebessem a promoção.
 
-<div class="alert alert-warning">
-<p>
-Para campos do tipo <strong>Varchar</strong>, o valor informado na seção <strong>Cluster de clientes </strong>da promoção diferencia caracteres minúsculos e maiúsculos. Isso quer dizer que, ao preencher a opção <strong>Cluster de clientes</strong> de forma diferente daquela definida para o campo no Master Data, a promoção não será aplicada.
-</p>
-</div>
+>⚠️ Para campos do tipo **Varchar**, o valor informado na seção **Cluster de clientes **da promoção diferencia caracteres minúsculos e maiúsculos. Isso quer dizer que, ao preencher a opção **Cluster de clientes** de forma diferente daquela definida para o campo no Master Data, a promoção não será aplicada.
 
 Portanto, considerando o exemplo acima de um campo tipo **Varchar** com os valores cadastrados `"sim"` e `"não"`, o cadastro na promoção obrigatoriamente será `funcionario="sim"`. Ao cadastrar na promoção o termo `funcionario="Sim"`, por exemplo, o cluster de clientes desejado não receberá a promoção.
 
diff --git a/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md b/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
index 32a5de438..b01a4ead6 100644
--- a/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
+++ b/docs/tutorials/pt/creating-relationships-between-master-data-entities-using-admin.md
@@ -19,9 +19,7 @@ Um relacionamento entre entidades é uma referência entre documentos que perten
 
 Por exemplo, sua loja tem uma entidade **Clientes** e outra **Lista de Compras**, e você quer que cada cliente possa ter várias listas de compras. Para isso, é necessário criar um campo na entidade **Lista de Compras** para informar a qual cliente ela pertence. 
 
-<div class="alert alert-info">
-<p>O Master Data já possui por padrão alguns relacionamentos pré-definidos, como os de Cliente (CL) e Endereço (AD).</p>
-</div>
+>ℹ️ O Master Data já possui por padrão alguns relacionamentos pré-definidos, como os de Cliente (CL) e Endereço (AD).
 
 ## Criar um relacionamento entre entidades de dados
 
diff --git a/docs/tutorials/pt/creating-roles.md b/docs/tutorials/pt/creating-roles.md
index 2f93ca917..7d9744cd6 100644
--- a/docs/tutorials/pt/creating-roles.md
+++ b/docs/tutorials/pt/creating-roles.md
@@ -26,9 +26,7 @@ Confira a seguir o passo a passo para cada uma dessas opções:
 
 Recomendamos a criação de perfis que sejam análogos às estruturas hierárquicas da loja. Desta forma, todos os colaboradores são responsáveis pelas informações a que podem ter acesso. Boas práticas de gerenciamento dos perfis de acesso aumentam a segurança de uma operação, além de se reforçar a atenção de todos os envolvidos com dados sensíveis de uma loja e de seus clientes. 
 
-<div class="alert alert-warning">
-  <p>O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas caso ocorra o vazamento de credenciais de login.</p>
-</div>
+>⚠️ O uso irrestrito de perfis de acesso muito permissivos aumenta o risco de ataques nas lojas caso ocorra o vazamento de credenciais de login.
 
 ## Utilizar perfil de acesso predefinido
 
@@ -80,9 +78,7 @@ Para criar  um perfil de acesso personalizado para atender as necessidades de ac
 
 7. Escreva um nome para o perfil personalizado no campo **Nome do perfil**.
 
-  <div class="alert alert-warning">
-    <p>É importante escolher nomes descritivos para os perfis de acesso, deixando claro que tipo de usuário deve ter aquele acesso. Recomendamos indicar o cargo na empresa ou atividade a ser desempenhada na plataforma.</p>
-  </div>
+  >⚠️ É importante escolher nomes descritivos para os perfis de acesso, deixando claro que tipo de usuário deve ter aquele acesso. Recomendamos indicar o cargo na empresa ou atividade a ser desempenhada na plataforma.
 
 8. Adicione usuários administrativos ao perfil de acesso, preenchendo o email do usuário a ser inserido em **Adicionar usuários para este perfil de acesso** e clicando em `Adicionar`.
 
diff --git a/docs/tutorials/pt/creating-service-for-a-sku.md b/docs/tutorials/pt/creating-service-for-a-sku.md
index f38a45e72..a2a2d0874 100644
--- a/docs/tutorials/pt/creating-service-for-a-sku.md
+++ b/docs/tutorials/pt/creating-service-for-a-sku.md
@@ -87,9 +87,7 @@ Para vincular um serviço a um SKU, siga os passos abaixo:
 ### Campos da planilha
 Manipule a planilha com cautela, sempre verificando se as informações contidas estão preenchidas corretamente. A planilha precisa estar com todos os campos preenchidos para evitar erros.
 
-<div class="alert alert-warning">
-  <p>Ao preencher a planilha, não altere ou apague os cabeçalhos das colunas na linha 1. Preencha os valores desejados nas linhas após os cabeçalhos das colunas para que a importação funcione corretamente.</p>
-</div>  
+>⚠️ Ao preencher a planilha, não altere ou apague os cabeçalhos das colunas na linha 1. Preencha os valores desejados nas linhas após os cabeçalhos das colunas para que a importação funcione corretamente.  
 
 - **Nome Serviço:** nome do serviço.
 - **Texto Serviço:** texto que será exibido junto com o serviço.
diff --git a/docs/tutorials/pt/creating-synonyms.md b/docs/tutorials/pt/creating-synonyms.md
index b5874aa8c..e9d1b853f 100644
--- a/docs/tutorials/pt/creating-synonyms.md
+++ b/docs/tutorials/pt/creating-synonyms.md
@@ -90,6 +90,4 @@ Lojas que utilizam [Configurações Multi-idioma (Beta)](https://help.vtex.com/p
      __Exemplo:__
      - `tv,smart tv;true;en-GB`: ao pesquisar por qualquer um dos termos na loja no idioma inglês (`locale = en-GB`), qualquer produto que contenha um desses termos irá aparecer nos resultados da busca.
 
-<div class="alert alert-warning">
-<p> Se o arquivo CSV importado não apresentar o <code>locale</code>, o sinônimo será válido para todos os idiomas disponíveis na loja.</p>
-</div>
+>⚠️ Se o arquivo CSV importado não apresentar o `locale`, o sinônimo será válido para todos os idiomas disponíveis na loja.
diff --git a/docs/tutorials/pt/creating-the-files-structure-for-your-app-vtex-init.md b/docs/tutorials/pt/creating-the-files-structure-for-your-app-vtex-init.md
index b081d4c57..f41262f57 100644
--- a/docs/tutorials/pt/creating-the-files-structure-for-your-app-vtex-init.md
+++ b/docs/tutorials/pt/creating-the-files-structure-for-your-app-vtex-init.md
@@ -33,8 +33,6 @@ Com isso, o IO fará algumas perguntas que serão usadas para definir parâmetro
 
 O IO informa que seu arquivo manifest.json foi gerado com sucesso e pergunta o serviço VTEX que você deseja usar.
 
-<div class="alert alert-info">
-Para desenvolvimento front-end, o serviço que deve ser usado é o react.
-</div>
+>ℹ️ Para desenvolvimento front-end, o serviço que deve ser usado é o react.
 
 Pronto, sua estrutura de pastas e arquivos está criada.
diff --git a/docs/tutorials/pt/creating-trigger-in-master-data.md b/docs/tutorials/pt/creating-trigger-in-master-data.md
index da3df8f68..3d94d360b 100644
--- a/docs/tutorials/pt/creating-trigger-in-master-data.md
+++ b/docs/tutorials/pt/creating-trigger-in-master-data.md
@@ -15,9 +15,7 @@ legacySlug: criando-trigger-no-master-data
 subcategory: 2nx7hMJmisofwqwy2P9l2i
 ---
 
-<div class="alert alert-info">
-<p>Este artigo se refere ao Master Data v1. Se você quiser utilizar o Master Data v2, veja os passos do guia <a href="https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2">Setting up triggers in Master Data v2</a>.</p>
-</div>
+>ℹ️ Este artigo se refere ao Master Data v1. Se você quiser utilizar o Master Data v2, veja os passos do guia [Setting up triggers in Master Data v2](https://developers.vtex.com/docs/guides/setting-up-triggers-in-master-data-v2).
 
 Conceitualmente, trigger é um recurso de programação que executa uma ação específica sempre que um evento associado ocorre. No Master Data, um trigger é a configuração de um ou mais disparos (eventos) que são acionados quando uma determinada situação ocorre, baseada em diversas variáveis.
 
@@ -123,9 +121,7 @@ Aqui, você deve definir as condições que vão disparar o(s) evento(s) configu
 
    ![filters-pt](https://images.ctfassets.net/alneenqid6w5/go7XW0mqWsuA4ygwYsoMS/34cbeea173c7f4944ee87c22eb406c02/filters-pt.png)
 
-<div class="alert alert-info">
-  <p>O Master Data v1 não permite configuração de retentativas de trigger, diferente do Master Data v2.</p>
-</div>
+>ℹ️ O Master Data v1 não permite configuração de retentativas de trigger, diferente do Master Data v2.
 
 ### Agendar
 
diff --git a/docs/tutorials/pt/credit-card-basic-payment-flow.md b/docs/tutorials/pt/credit-card-basic-payment-flow.md
index a80df1528..be9001cdc 100644
--- a/docs/tutorials/pt/credit-card-basic-payment-flow.md
+++ b/docs/tutorials/pt/credit-card-basic-payment-flow.md
@@ -27,6 +27,4 @@ Este artigo tem como objetivo explicar como funciona o fluxo básico de um pagam
 
 Com a resposta do banco emissor, é realizado o fluxo inverso e o __Gateway de Pagamentos__ recebe a informação se o pagamento foi aprovado ou negado.
 
-<div class="alert alert-info">
-É possível incluir o <strong>Antifraude</strong> neste fluxo. Neste caso, o antifraude recebe as informações do gateway de que o pagamento foi pré-autorizado pelo banco emissor. Com a informação recebida do gateway, o antifraude envia uma resposta de aprovação ou negação do pagamento. Caso o antifraude negue, o pagamento é cancelado. Caso o pagamento seja aprovado, o pedido pode prosseguir seu fluxo normal.
-</div>
+>ℹ️ É possível incluir o **Antifraude** neste fluxo. Neste caso, o antifraude recebe as informações do gateway de que o pagamento foi pré-autorizado pelo banco emissor. Com a informação recebida do gateway, o antifraude envia uma resposta de aprovação ou negação do pagamento. Caso o antifraude negue, o pagamento é cancelado. Caso o pagamento seja aprovado, o pedido pode prosseguir seu fluxo normal.
diff --git a/docs/tutorials/pt/credit-control-overview.md b/docs/tutorials/pt/credit-control-overview.md
index 19f80b372..aef0661b7 100644
--- a/docs/tutorials/pt/credit-control-overview.md
+++ b/docs/tutorials/pt/credit-control-overview.md
@@ -15,10 +15,8 @@ legacySlug: credit-control-visao-geral
 subcategory: 7EWKfPIGfmI0G8iMYK8Aiy
 ---
 
-<div class="alert alert-warning">
-<strong>ATENÇÃO:</strong> o Credit Control foi descontinuado em <strong>dezembro de 2018</strong>. Agora, para sua loja oferecer crédito como meio de pagamento direto no checkout, é necessário <a href="https://help.vtex.com/pt/tutorial/customer-credit-visao-geral">utilizar o Customer Credit</a>.</br>
-Para saber como configurá-lo na sua loja, siga os passos descritos <a href="https://help.vtex.com/pt/tracks/customer-credit-como-comecar">aqui</a>. 
-</div>
+>⚠️ **ATENÇÃO:** o Credit Control foi descontinuado em **dezembro de 2018**. Agora, para sua loja oferecer crédito como meio de pagamento direto no checkout, é necessário [utilizar o Customer Credit](https://help.vtex.com/pt/tutorial/customer-credit-visao-geral).</br>
+> Para saber como configurá-lo na sua loja, siga os passos descritos [aqui](https://help.vtex.com/pt/tracks/customer-credit-como-comecar).
 
 
 ## O que é
diff --git a/docs/tutorials/pt/criar-um-produto-beta.md b/docs/tutorials/pt/criar-um-produto-beta.md
index 5e2b512fb..50e63083d 100644
--- a/docs/tutorials/pt/criar-um-produto-beta.md
+++ b/docs/tutorials/pt/criar-um-produto-beta.md
@@ -15,7 +15,7 @@ legacySlug: criar-um-produto-beta
 subcategory: 
 ---
 
-<div class="alert alert-info"> Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso<a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.</div>
+>ℹ️ Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso[Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 A página **Adicionar produto (Beta)** possibilita criar e editar produtos e seus SKUs relacionados de forma completa no Admin VTEX. Para adicionar um novo produto, siga o passo a passo abaixo. 
 
@@ -33,7 +33,7 @@ Caso você queira criar um produto no modo inativo, clique no botão <i class="f
 
 Feito isso, o produto será ativado e estará disponível na sua loja.
 
-<div class="alert alert-info">Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo  <a href="https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382">Por que o produto não aparece no site?</a> para entender como resolver esse problema.</div>
+>ℹ️ Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo  [Por que o produto não aparece no site?](https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382) para entender como resolver esse problema.
 
 # Produto
 Nesta aba, você vai realizar o cadastro do produto preenchendo os campos descritos abaixo com as características do item.
@@ -127,7 +127,7 @@ Aqui serão exibidas as especificações criadas anteriormente para os SKUs. Se
 
 ## Imagens
 
-<div class="alert alert-warning">SKUs devem ter pelo menos uma imagem para estar ativo.</div>
+>⚠️ SKUs devem ter pelo menos uma imagem para estar ativo.
 
 Para adicionar uma imagem a seu SKU, siga os passos abaixo:
 
@@ -135,7 +135,7 @@ Para adicionar uma imagem a seu SKU, siga os passos abaixo:
 2. Adicione o link da sua imagem no campo 🔗. Você pode adicionar mais de uma imagem ano seu SKU. Para isso, clique em + Adicionar imagem e adicione o novo link.![image6](https://images.ctfassets.net/alneenqid6w5/7lEnztWcQFXIAPFdMkHIaH/96ff215f5caef65e23ecac650111ee50/image6.png)
 3. Clique em `Salvar`.
 
-<div class="alert alert-info"> A primeira imagem adicionada será a imagem principal do SKU que será exibida na loja e nos resultados de busca. </div>
+>ℹ️ A primeira imagem adicionada será a imagem principal do SKU que será exibida na loja e nos resultados de busca.
 
  Você pode editar os metadados de uma imagem clicando no botão <i class="fas fa-ellipsis-v"></i> e selecione <i class="fas fa-pencil-alt"></i> Editar metadados.
 
diff --git a/docs/tutorials/pt/custom-product-fields.md b/docs/tutorials/pt/custom-product-fields.md
index 852e734e7..d16ee4feb 100644
--- a/docs/tutorials/pt/custom-product-fields.md
+++ b/docs/tutorials/pt/custom-product-fields.md
@@ -42,9 +42,7 @@ Para criar um campo de produto, siga os passos abaixo:
 5. Clique em **Campo (Produto).**  
 6. Clique em **Novo Campo.**  
 7. Preencha as informações referentes ao campo que está sendo criado:  
-<div class="alert alert-warning">
-O nome do campo deve ser preenchido exatamente como um dos nomes apresentados na tabela da seção <a href="#campos-customizaveis">Campos customizáveis</a>.
-</div>  
+>⚠️ O nome do campo deve ser preenchido exatamente como um dos nomes apresentados na tabela da seção [Campos customizáveis](#campos-customizaveis).  
 
   **Nome:** nome da especificação (campo) de produto.  
   **Texto:** descrição sobre o campo.  
diff --git a/docs/tutorials/pt/customer-credit-overview.md b/docs/tutorials/pt/customer-credit-overview.md
index 03c5ded50..565da4eeb 100644
--- a/docs/tutorials/pt/customer-credit-overview.md
+++ b/docs/tutorials/pt/customer-credit-overview.md
@@ -34,9 +34,7 @@ Por meio do Admin VTEX ou da [API do Customer Credit](https://developers.vtex.co
 - Configurar prazos e parcelamentos de títulos de cobrança
 - Acompanhar e modificar o status dos títulos emitidos
 
-<div class="alert alert-info">
-Quando instalado, o Customer Credit aparece como uma opção de pagamento no Checkout somente para os clientes selecionados pelo lojista, exibindo o valor de crédito disponível para ser utilizado na compra.
-</div>
+>ℹ️ Quando instalado, o Customer Credit aparece como uma opção de pagamento no Checkout somente para os clientes selecionados pelo lojista, exibindo o valor de crédito disponível para ser utilizado na compra.
 
 Veja abaixo o fluxo básico de funcionamento do Customer Credit nas lojas VTEX:
 
@@ -52,9 +50,7 @@ Para utilizar o Customer Credit como meio de pagamento em uma compra, o cliente
 
 Cada conta possui um limite de crédito cadastrado no momento de sua abertura. Esse limite indica o valor máximo que o cliente pode utilizar para realizar uma ou mais compras  ao mesmo tempo via Customer Credit.
 
-<div class="alert alert-warning">
-O limite de crédito de uma conta pode ser alterado pelo lojista a qualquer momento.
-</div>
+>⚠️ O limite de crédito de uma conta pode ser alterado pelo lojista a qualquer momento.
 
 ### Crédito disponível
 
@@ -62,9 +58,7 @@ Valor que o cliente ainda tem disponível em sua conta para realizar compras por
 
 Sempre que o cliente conclui uma compra e o pedido é faturado, o valor do crédito disponível diminui. Entretanto, após o cliente efetuar o pagamento do título emitido, o valor de crédito disponível retorna ao valor pré-compra.
 
-<div class="alert alert-warning">
-No momento de uma compra, o cliente tem visibilidade de quanto crédito é possível utilizar via Customer Credit. Caso o valor da compra seja maior que o crédito disponível, o pagamento não poderá ser realizado por meio do Customer Credit.
-</div>
+>⚠️ No momento de uma compra, o cliente tem visibilidade de quanto crédito é possível utilizar via Customer Credit. Caso o valor da compra seja maior que o crédito disponível, o pagamento não poderá ser realizado por meio do Customer Credit.
 
 ### Título
 
@@ -82,9 +76,7 @@ Após o cliente realizar a compra utilizando o Customer Credit, o pagamento é a
 
 O fluxo no Customer Credit é similar ao de cartões de crédito em relação a modificações no pedido. Quando uma alteração de valor no pedido ocorre durante o período de pré-autorização, o valor do crédito é alterado.
 
-<div class="alert alert-warning">
-Se for necessário alterar  uma ordem para diminuir o seu valor após o período de liquidação (emissão de títulos), o sistema irá atualizar os títulos para o novo valor. Caso o valor do pedido seja aumentado, o sistema criará novos títulos.
-</div>
+>⚠️ Se for necessário alterar  uma ordem para diminuir o seu valor após o período de liquidação (emissão de títulos), o sistema irá atualizar os títulos para o novo valor. Caso o valor do pedido seja aumentado, o sistema criará novos títulos.
 
 ## Instalação e configuração
 Para instalar e configurar o Customer Credit em sua loja, acesse a Track [Customer Credit - Como começar](https://help.vtex.com/pt/tracks/customer-credit-como-comecar--1hCRg21lXYy2seOKgqQ2CC/36grlQ69NK6OCuioeekyCs).
diff --git a/docs/tutorials/pt/customizar-a-toolbar-de-televendas.md b/docs/tutorials/pt/customizar-a-toolbar-de-televendas.md
index 3acad5a40..c40062aab 100644
--- a/docs/tutorials/pt/customizar-a-toolbar-de-televendas.md
+++ b/docs/tutorials/pt/customizar-a-toolbar-de-televendas.md
@@ -15,7 +15,7 @@ legacySlug: customizar-a-toolbar-de-televendas
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-warning">Não é recomendável alterar a altura do elemento da toolbar. Caso sua loja tenha um header ou outro elemento fixo no topo da tela, ele deve receber a propriedade <code>top</code> com a altura necessária para compensar presença da toolbar de televendas.</div>
+>⚠️ Não é recomendável alterar a altura do elemento da toolbar. Caso sua loja tenha um header ou outro elemento fixo no topo da tela, ele deve receber a propriedade `top` com a altura necessária para compensar presença da toolbar de televendas.
 
 A nova toolbar de televendas pode ser customizada com os estilos da sua loja ou com javascript. Para sobrescrever os estilos originais da toolbar, faça a customização em um arquivo **.css **ou **.js** e carregue-o no template da página.
 
diff --git a/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md b/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md
index ae4ff9eaa..1e445192b 100644
--- a/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md
+++ b/docs/tutorials/pt/customizing-the-checkout-confirmation-pages.md
@@ -40,7 +40,7 @@ Para adicionar seu código nesses templates, basta acessar o módulo Portal e, n
 
 ### Customização de estilos
 
-<div class="alert alert-warning">Todas estas formas de customização podem ser alteradas no futuro. Ao usá-las, você entende que sua loja deve acompanhar atualizações da plataforma para que sua customização continue funcionando corretamente.</div>
+>⚠️ Todas estas formas de customização podem ser alteradas no futuro. Ao usá-las, você entende que sua loja deve acompanhar atualizações da plataforma para que sua customização continue funcionando corretamente.
 
 Também é possível editar a interface do Checkout Confirmation via classes CSS. Seus estilos devem ser adicionados numa `<style>` tag em um dos templates HTML carregados na página.
 
diff --git a/docs/tutorials/pt/customizing-the-my-orders-section.md b/docs/tutorials/pt/customizing-the-my-orders-section.md
index 4f350ff87..3d2ab2170 100644
--- a/docs/tutorials/pt/customizing-the-my-orders-section.md
+++ b/docs/tutorials/pt/customizing-the-my-orders-section.md
@@ -21,16 +21,16 @@ Ela já está disponível no ambiente beta (`sualoja.vtexcommercebeta.com.br`) p
 
 Veja abaixo uma lista com as classes disponíveis para customização.
 
-<div class="alert alert-warning">
-Customizações de interface <strong>não são oficialmente suportadas pela VTEX</strong>.
-<br />
-<br /> 
-Estas classes e configurações podem ser alteradas ou removidas em futuras atualizações. Como boa prática, recomendamos tratar erros de javascript para que seu código de customização não quebre caso uma classe seja removida no futuro.
-</div>
+>⚠️ Customizações de interface **não são oficialmente suportadas pela VTEX**.
+>
+>
+> 
+>
+>
+>  
+> Estas classes e configurações podem ser alteradas ou removidas em futuras atualizações. Como boa prática, recomendamos tratar erros de javascript para que seu código de customização não quebre caso uma classe seja removida no futuro.
 
-<div class="alert alert-info">
-Caso você já possua um arquivo de customização para a antiga versão do My Orders, recomendamos que coloque a nova customização em um arquivo separado.
-</div>
+>ℹ️ Caso você já possua um arquivo de customização para a antiga versão do My Orders, recomendamos que coloque a nova customização em um arquivo separado.
 
 ### Lista de pedidos
 
diff --git a/docs/tutorials/pt/customizing-your-stores-typography.md b/docs/tutorials/pt/customizing-your-stores-typography.md
index c3f650c3f..e8ab1d4ec 100644
--- a/docs/tutorials/pt/customizing-your-stores-typography.md
+++ b/docs/tutorials/pt/customizing-your-stores-typography.md
@@ -18,9 +18,7 @@ subcategory: 5HsDDU48ZP58JHWU3WbCPc
 A tipografia da sua loja online é uma ferramenta para mostrar a identidade de sua marca para os seus clientes. 
 No Admin, você tem flexibilidade para personalizar a tipografia da sua loja de acordo com as necessidades de seu negócio.
 
-<div class="alert alert-warning">
-  <p>Lembre-se de que as mudanças realizadas na tipografia da sua loja no <b>Storefront</b> substituem as mudanças de tipografia feitas no código da loja. Por favor, entre em contato com sua equipe de desenvolvimento e certifique-se de que essas mudanças serão definidas no Storefront ou pelo código da sua loja.</p>
-</div>
+>⚠️ Lembre-se de que as mudanças realizadas na tipografia da sua loja no **Storefront** substituem as mudanças de tipografia feitas no código da loja. Por favor, entre em contato com sua equipe de desenvolvimento e certifique-se de que essas mudanças serão definidas no Storefront ou pelo código da sua loja.
 
 ## Adicionar famílias de fontes personalizadas
 
@@ -33,9 +31,7 @@ No Admin, você tem flexibilidade para personalizar a tipografia da sua loja de
 
 4. Depois, clique em **Add custom font (Adicionar fonte personalizada)** e faça o upload do arquivo da fonte desejada. No campo **Font Family (Família da fonte)**, crie um nome para a fonte.
 
-<div class="alert alert-warning">
-  <p>O arquivo da família de fontes deve ser baixado nas seguintes extensões de arquivo: <i>.ttf</i> ou <i>.woff</i>.</p>
-</div>
+>⚠️ O arquivo da família de fontes deve ser baixado nas seguintes extensões de arquivo: <i>.ttf</i> ou <i>.woff</i>.
 
 5. Clique em `Save` (Salvar) para salvar as mudanças. 
 
diff --git a/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md b/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md
index 592ef2096..dcac248f4 100644
--- a/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md
+++ b/docs/tutorials/pt/data-dictionary-vtex-data-pipeline-beta.md
@@ -15,9 +15,7 @@ legacySlug: catalogo-vtex-data-pipeline-beta
 subcategory: oMrzcOMVbBpH0reeMFHFg
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">Suporte</a>.
-</div>  
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso [Suporte](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue).  
 
 O **VTEX Data Pipeline** é uma ferramenta acessível exclusivamente aos clientes VTEX, que deve ser utilizada para exploração e análise dos dados do ecommerce que atualmente estão disponíveis em nossos servidores. O **Data Pipeline** é um produto add-on da VTEX que integra dados do seu ecommerce, de maneira limpa e segura ao *data warehouse* e às ferramentas de BI de sua preferência.  
 
diff --git a/docs/tutorials/pt/data-entity.md b/docs/tutorials/pt/data-entity.md
index 20bdb6136..61d32da69 100644
--- a/docs/tutorials/pt/data-entity.md
+++ b/docs/tutorials/pt/data-entity.md
@@ -23,13 +23,12 @@ Para exemplificar, imagine um sistema de controle de uma biblioteca. Esse sistem
 
 Com esses conceitos, é possível configurar os mais diversos cenários de controle de dados pelo Master Data. Por padrão, são inseridas as seguintes entidades de dados: Cliente, Endereço, Stores etc. É possível criar quantas mais entidades de dados desejar, possibilitando um ambiente personalizado, voltado às necessidade de cada loja.
 
-<div class="alert alert-warning">
-<p>Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:</p>
-    <ul>
-        <li><a href="https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versoes-disponiveis">Características das versões do Master Data</a></li>
-        <li><a href="https://developers.vtex.com/docs/guides/master-data-v2-basics">Master Data v2</a></li>
-    </ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> * [Características das versões do Master Data](https://help.vtex.com/pt/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versoes-disponiveis)
+>
+> * [Master Data v2](https://developers.vtex.com/docs/guides/master-data-v2-basics)
+>     
 
 ## Tipos de dados
 
@@ -104,6 +103,4 @@ Siga o passo a passo abaixo para configurar uma nova entidade de dados.
 19. Na linha da nova entidade criada, clique no botão de disquete <i class="fas fa-save"></i> para publicar a entidade de dados criada.
 20. Clique em `OK`.
 
-<div class="alert alert-info">
-    <p>Após a criação da entidade de dados, é necessário <a href="https://help.vtex.com/pt/tutorial/criando-formulario-no-master-data--tutorials_1047">criar o formulário para a inserção, alteração e exibição de dados no Master Data</a>.</p>
-</div>
+>ℹ️ Após a criação da entidade de dados, é necessário [criar o formulário para a inserção, alteração e exibição de dados no Master Data](https://help.vtex.com/pt/tutorial/criando-formulario-no-master-data--tutorials_1047).
diff --git a/docs/tutorials/pt/data-subject-rights.md b/docs/tutorials/pt/data-subject-rights.md
index c2a11e7c1..0034752f6 100644
--- a/docs/tutorials/pt/data-subject-rights.md
+++ b/docs/tutorials/pt/data-subject-rights.md
@@ -25,9 +25,7 @@ Neste artigo, você aprenderá como cumprir com os seguintes direitos dos titula
 - [Consentimento](#consentimento)
 - [Exclusão](#exclusão)
 
-<div class="alert alert-danger">
-A VTEX não se responsabiliza por dados pessoais armazenados por sistemas integrados à sua loja, como por exemplo: ERPs, marketplaces externos, sellers externos, aplicativos de terceiros disponíveis na <a href="https://help.vtex.com/pt/tutorial/visao-geral-apps--4xfsHXyAQTjbZNuiKl6Y0e">VTEX App Store</a> ou customizações implementadas pelo seu time de desenvolvimento. Você deve mapear estes dados e garantir a aplicabilidade dos direitos dos titulares de dados pessoais nestas instâncias, além dos processos descritos abaixo.
-</div>
+>❗ A VTEX não se responsabiliza por dados pessoais armazenados por sistemas integrados à sua loja, como por exemplo: ERPs, marketplaces externos, sellers externos, aplicativos de terceiros disponíveis na [VTEX App Store](https://help.vtex.com/pt/tutorial/visao-geral-apps--4xfsHXyAQTjbZNuiKl6Y0e) ou customizações implementadas pelo seu time de desenvolvimento. Você deve mapear estes dados e garantir a aplicabilidade dos direitos dos titulares de dados pessoais nestas instâncias, além dos processos descritos abaixo.
 
 ## Acesso e portabilidade
 
diff --git a/docs/tutorials/pt/database-maintenance-full-cleanup.md b/docs/tutorials/pt/database-maintenance-full-cleanup.md
index e6aa21d84..c17db2816 100644
--- a/docs/tutorials/pt/database-maintenance-full-cleanup.md
+++ b/docs/tutorials/pt/database-maintenance-full-cleanup.md
@@ -29,12 +29,10 @@ Estas são as operações disponíveis:
 
 - __Apagar Produtos do Indexador:__ ao apagar produtos do indexador, sua loja ficará sem produtos para serem visualizados.
 
-  <div class="alert alert-warning"> 
-    <p>As seguintes regras se aplicam ao botão <b>Apagar Produtos do Indexador</b>:
-<UL> <LI>Apenas lojas com menos de 10 mil produtos podem realizar essa ação. Lojas com um catálogo maior devem <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abrir um chamado para o suporte VTEX</a> para realizar a limpeza do indexador e reindexação da base de dados.</LI>
-<LI>Quando um usuário apaga produtos do indexador, a conta é bloqueada de executar essa ação por 24 horas.</LI>
-<LI>Existe uma fila para processar as solicitações geradas pelo botão <i>Apagar Produtos do Indexador</i>. Você pode visualizar o tempo estimado de espera na interface da página. A fila é global e se aplica a todos os usuários, para garantir a segurança da plataforma VTEX.</LI></UL></p>
-  </div>
+  >⚠️ As seguintes regras se aplicam ao botão **Apagar Produtos do Indexador**:
+> <UL> <LI>Apenas lojas com menos de 10 mil produtos podem realizar essa ação. Lojas com um catálogo maior devem [abrir um chamado para o suporte VTEX](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) para realizar a limpeza do indexador e reindexação da base de dados.</LI>
+> <LI>Quando um usuário apaga produtos do indexador, a conta é bloqueada de executar essa ação por 24 horas.</LI>
+> <LI>Existe uma fila para processar as solicitações geradas pelo botão <i>Apagar Produtos do Indexador</i>. Você pode visualizar o tempo estimado de espera na interface da página. A fila é global e se aplica a todos os usuários, para garantir a segurança da plataforma VTEX.</LI></UL>
 
 - __Apagar Produtos/Skus e itens relacionados:__ ao apagar esses elementos, seus produtos e SKUs, além dos seus itens relacionados, serão removidos de forma definitiva da sua loja.
 
@@ -44,6 +42,4 @@ Estas são as operações disponíveis:
 
 - __Agendar reindexação Completa:__ ao reindexar a base, você entra em uma fila para iniciar o processo de indexação dos seus produtos. Os produtos da loja continuam à venda durante o processo de indexação. Eles apenas entram em uma fila para atualização de dados e seguem disponíveis no site para venda. Após clicar em __Reindexar Base__, o processo é iniciado automaticamente.
 
-<div class="alert alert-warning">
-  <p>É importante <b>Apagar Produtos do Indexador</b> após realizar qualquer outra operação nesta página. Caso contrário, sua loja pode apresentar erros ao acessar páginas de produtos, de categorias ou resultados de busca. Não é necessário <b>Apagar Produtos do Indexador</b> após <b>Agendar reindexação completa</b>.
-</div>
+>⚠️ <p>É importante **Apagar Produtos do Indexador** após realizar qualquer outra operação nesta página. Caso contrário, sua loja pode apresentar erros ao acessar páginas de produtos, de categorias ou resultados de busca. Não é necessário **Apagar Produtos do Indexador** após **Agendar reindexação completa**.
diff --git a/docs/tutorials/pt/deactivating-and-reorganizing-categories.md b/docs/tutorials/pt/deactivating-and-reorganizing-categories.md
index 5c7352626..b97134412 100644
--- a/docs/tutorials/pt/deactivating-and-reorganizing-categories.md
+++ b/docs/tutorials/pt/deactivating-and-reorganizing-categories.md
@@ -45,9 +45,7 @@ Na árvore de categorias exibida na página **Catálogo > Categorias** do Admin
 
 ## Alterar a árvore de categorias
 
-<div class="alert alert-warning">
-  <p>Mover categorias diretamente pela árvore de categorias pode gerar erros inesperados no seu catálogo. Por isso, recomendamos seguir as instruções abaixo para qualquer alteração nos níveis de categorias. Leia o <a href="https://help.vtex.com/pt/known-issues/mover-categorias-gera-comportamentos-inesperados-na-arvore-de-categorias--6JSa9nnYoAAUQO1zPtzfZD">problema conhecido</a> relacionado a esse cenário para mais informações.</p>
-</div>
+>⚠️ Mover categorias diretamente pela árvore de categorias pode gerar erros inesperados no seu catálogo. Por isso, recomendamos seguir as instruções abaixo para qualquer alteração nos níveis de categorias. Leia o [problema conhecido](https://help.vtex.com/pt/known-issues/mover-categorias-gera-comportamentos-inesperados-na-arvore-de-categorias--6JSa9nnYoAAUQO1zPtzfZD) relacionado a esse cenário para mais informações.
 
 Existem cenários em que é necessário mudar o nível hierárquico de uma categoria. Por exemplo, imagine que uma loja tem uma categoria pai chamada **Acessórios** e uma categoria filha (subcategoria) chamada **Sapatos**, mas deseja transformar a subcategoria **Sapatos** em uma outra categoria pai.
 
diff --git a/docs/tutorials/pt/deadline-indicators.md b/docs/tutorials/pt/deadline-indicators.md
index e5f238f71..7ccd025dc 100644
--- a/docs/tutorials/pt/deadline-indicators.md
+++ b/docs/tutorials/pt/deadline-indicators.md
@@ -16,9 +16,7 @@ subcategory: 2A1RNDhwU4kqCN3XimtaD2
 ---
 
 
-<div class="alert alert-info"> 
- Esse artigo está relacionado com a funcionalidade de <b>Relatório de Indicadores</b>. Caso queira saber mais, acesse<a href="https://help.vtex.com/pt/tutorial/relatorio-de-indicadores--7lbICsrCArXDxUYeeHJ2c5">  Relatório de Indicadores</a>.
-</div>
+>ℹ️ Esse artigo está relacionado com a funcionalidade de **Relatório de Indicadores**. Caso queira saber mais, acesse[  Relatório de Indicadores](https://help.vtex.com/pt/tutorial/relatorio-de-indicadores--7lbICsrCArXDxUYeeHJ2c5).
 
 ## Data Limite
 
diff --git a/docs/tutorials/pt/declining-order-cancelation.md b/docs/tutorials/pt/declining-order-cancelation.md
index 2f8cc25ad..fe48ea5ce 100644
--- a/docs/tutorials/pt/declining-order-cancelation.md
+++ b/docs/tutorials/pt/declining-order-cancelation.md
@@ -43,13 +43,12 @@ Segue a descrição de cada etapa:
 3. Se o pedido estiver dentro da janela para cancelamento, ele será cancelado automaticamente, seguindo o comportamento padrão da plataforma. As próximas etapas se aplicam quando a janela para cancelamento termina.
 4. O seller recebe a solicitação de cancelamento do pedido e decide se vai aceitá-la ou não. As próximas etapas se aplicam quando o seller decide não cancelar o pedido.
 
-  <div class="alert alert-danger">
-Para recusar uma solicitação de cancelamento do pedido, o status do pedido para o marketplace e para o seller deve ser o seguinte:
-<ul>
-<li><b>Status do marketplace:</b> Aguardando decisão do seller.</li>
-<li><b>Status do seller:</b> Cancelamento solicitado.</li>
-</ul>
-</div>
+  >❗ Para recusar uma solicitação de cancelamento do pedido, o status do pedido para o marketplace e para o seller deve ser o seguinte:
+>
+> ***Status do marketplace:** Aguardando decisão do seller.
+>
+> ***Status do seller:** Cancelamento solicitado.
+> 
 
 5. O seller recusa o cancelamento do pedido e notifica o marketplace.
 6. Depois que o marketplace recebe a solicitação recusada, o pedido progride no fluxo de pedidos.
@@ -60,9 +59,7 @@ A solicitação de cancelamento de um pedido pode ser feita pelo marketplace ou
 
 Depois disso, o pedido permanecerá com o [status](https://help.vtex.com/en/tutorial/order-flow-and-status--tutorials_196) de `cancelamento solicitado` para o marketplace e `aguardando decisão do seller` para o seller até que ele aceite ou não a solicitação. 
 
-<div class="alert alert-warning">
-Se, dentro de 30 dias, o seller não fizer nada em relação à solicitação de cancelamento do pedido, o pedido será cancelado automaticamente pela plataforma da VTEX.
-</div>
+>⚠️ Se, dentro de 30 dias, o seller não fizer nada em relação à solicitação de cancelamento do pedido, o pedido será cancelado automaticamente pela plataforma da VTEX.
 
 Para recusar uma solicitação de cancelamento do pedido pelo Admin VTEX, siga os passos a seguir:
 
@@ -76,9 +73,7 @@ Para recusar uma solicitação de cancelamento do pedido pelo Admin VTEX, siga o
 
   ![deny_cancel_request_reason_PT_v2](https://images.ctfassets.net/alneenqid6w5/2j1DgDKBaWJFMeVfuxfwYL/08eae24f54f83caa4d8449a3dd465d31/deny_cancel_request_reason_PT_v2.png)
 
-  <div class="alert alert-warning">
-Lembre-se de que a mensagem contida nesse campo poderá ser exibida ao cliente pela <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha conta</a> ou enviada pelo marketplace.
-</div>
+  >⚠️ Lembre-se de que a mensagem contida nesse campo poderá ser exibida ao cliente pela [Minha conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh) ou enviada pelo marketplace.
 
 5. Clique em `Recusar solicitação`.
 
diff --git a/docs/tutorials/pt/deleting-a-category.md b/docs/tutorials/pt/deleting-a-category.md
index 8fa3f722f..77d2177f0 100644
--- a/docs/tutorials/pt/deleting-a-category.md
+++ b/docs/tutorials/pt/deleting-a-category.md
@@ -37,7 +37,7 @@ Outra opção é [limpar o catálogo](https://help.vtex.com/pt/tutorial/entenden
 2. Clique em `Apagar Produtos/SKUs`. Atenção: ao apagar esses elementos, seus Produtos e SKUs, além dos seus itens relacionados, serão removidos de forma definitiva da sua loja. 
 3. Depois, clique em `Apagar Categorias e Marcas`. Atenção: ao apagar esses elementos, Categorias, Marcas e Especificações, além dos seus itens relacionados, serão removidos de forma definitiva da sua loja.
 
-<div class="alert alert-warning"> <p>Por questões de segurança, somente o <a href="https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy">usuário Titular</a> da conta possui acesso à limpeza da base de dados. Caso outro usuário tente acessar esta página, todos os botões estarão inativos.</p></div>
+>⚠️ Por questões de segurança, somente o [usuário Titular](https://help.vtex.com/pt/tutorial/o-que-e-o-usuario-master--3oPr7YuIkEYqUGmEqIMSEy) da conta possui acesso à limpeza da base de dados. Caso outro usuário tente acessar esta página, todos os botões estarão inativos.
 
 ### Artigos relacionados
 - [Cadastrar uma categoria](/pt/tutorial/cadastrando-categoria)
diff --git a/docs/tutorials/pt/deleting-a-folder-from-cms.md b/docs/tutorials/pt/deleting-a-folder-from-cms.md
index 70270b3fa..253e602fe 100644
--- a/docs/tutorials/pt/deleting-a-folder-from-cms.md
+++ b/docs/tutorials/pt/deleting-a-folder-from-cms.md
@@ -27,9 +27,11 @@ Para apagar uma pasta do CMS, siga os passoa abaixo:
 
 ![erroDeletarPasta2](https://images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
 
-<div class="alert alert-danger">
-Algumas pastas são obrigatórias. Sua loja não funcionará corretamente sem elas. Outras são importantes, portanto não é uma boa ideia apagá-las.<br><br>Entenda melhor este assunto no artigo <a href="http://help.vtex.com/pt/tutorial/estrutura-de-pastas-do-cms">Estrutura de pastas do CMS</a>.
-</div>
+>❗ Algumas pastas são obrigatórias. Sua loja não funcionará corretamente sem elas. Outras são importantes, portanto não é uma boa ideia apagá-las.
+>
+> 
+>
+> Entenda melhor este assunto no artigo [Estrutura de pastas do CMS](http://help.vtex.com/pt/tutorial/estrutura-de-pastas-do-cms).
 
 Se uma pasta contém outras pastas, antes de apagá-la é necessário apagar todas as pastas internas. Caso contrário, o sistema retornará o erro "Object reference not set to an instance of an object", como na imagem abaixo.
 
diff --git a/docs/tutorials/pt/deleting-customer-data.md b/docs/tutorials/pt/deleting-customer-data.md
index 066e17c9d..6682a6f4f 100644
--- a/docs/tutorials/pt/deleting-customer-data.md
+++ b/docs/tutorials/pt/deleting-customer-data.md
@@ -33,9 +33,7 @@ Se a sua loja armazena informações de clientes em outras entidades de dados, v
 
 2. Utilize a requisição [Delete document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1)
 
-<div class="alert alert-danger">
-Não realize esse processo para as entidades <b>CL</b> e <b>AD</b>.
-</div>
+>❗ Não realize esse processo para as entidades **CL** e **AD**.
 
 ## Solicitar exclusão via suporte
 
diff --git a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
index 2a08ca13f..985fab019 100644
--- a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
+++ b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
@@ -15,13 +15,13 @@ legacySlug: entregas-correios-vtex-log
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/).
 
-<div class="alert alert-warning">
-<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a></li><li><a href="https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92">Painel VTEX Shipping Network</a></li><li>Entregas Correios</li></ul></p>
-</div>
+>⚠️ O [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:
+> 
+> *[Pronto para envio](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs)
+> * [Painel VTEX Shipping Network](https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92)
+> * Entregas Correios
 
 **Entregas Correios** é a funcionalidade do [VTEX Shipping Network](https://vtex.com/br-pt/log/) que permite ao lojista acompanhar as informações e o andamento de pacotes postados nos [Correios](https://www.correios.com.br/). A solução permite solicitar um Pedido de Informação (PI) para entregas que estão atrasadas, extraviadas ou foram feitas indevidamente.
 
diff --git a/docs/tutorials/pt/detaching-skus-by-specification.md b/docs/tutorials/pt/detaching-skus-by-specification.md
index 54bc520af..1439ada86 100644
--- a/docs/tutorials/pt/detaching-skus-by-specification.md
+++ b/docs/tutorials/pt/detaching-skus-by-specification.md
@@ -27,8 +27,7 @@ A seguir, confira um exemplo de separação de SKUs por cor. Na imagem abaixo, a
 
 ![screencapture-footnotes-sandals-2021-02-11-14 21 21](https://images.ctfassets.net/alneenqid6w5/3wDeiYyhcz0BNUyJrDo7zI/d5d68b1a11e1c117ca11653239037005/screencapture-footnotes-sandals-2021-02-11-14_21_21.png)
 
-<div class="alert alert-info"><p>
-Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.</p></div>
+>ℹ️ Caso os resultados de busca sejam ordenados por relevância, os SKUs de um mesmo produto são agrupados, ou seja, aparecem um ao lado do outro.
 
 ## Configuração
 Para configurar quais atributos serão usados para separar os SKUs, acesse nosso artigo de [Configurações da busca](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5t75L6lYNwix93l41s1Yrx#).
diff --git a/docs/tutorials/pt/develop-the-front-end-for-the-list-feature-in-your-store.md b/docs/tutorials/pt/develop-the-front-end-for-the-list-feature-in-your-store.md
index 59a299ee2..180e6b386 100644
--- a/docs/tutorials/pt/develop-the-front-end-for-the-list-feature-in-your-store.md
+++ b/docs/tutorials/pt/develop-the-front-end-for-the-list-feature-in-your-store.md
@@ -116,15 +116,11 @@ Este código renderiza uma lista com __três links__:
 2. __Criar nova Lista__: Este link leva o cliente para a rota `/giftlist/create`, onde o cliente cria suas listas. Nos próximos passos, vamos explicar como é feita a criação de listas.
 3. __Gerenciar minhas Listas__: Este link leva o cliente para a rota `/giftlist/manage`, onde o cliente pode gerenciar suas listas. Nos próximos passos, vamos explicar como é feito o gerenciamento de listas.
 
-<div class="alert alert-danger">
-Não desmarque a flag <strong>Authentication Required</strong> já selecionada por default nas pastas abaixo. A identificação é necessária para que as listas sejam exibidas para cada usuário específico.
-</div>
+>❗ Não desmarque a flag **Authentication Required** já selecionada por default nas pastas abaixo. A identificação é necessária para que as listas sejam exibidas para cada usuário específico.
 
 ## Editar o template de criação de listas
 
-<div class="alert alert-info">
-Antes de editar este template, é necessário <a href="http://help.vtex.com/pt/tutorial/criando-tipo-de-lista">criar o Tipo de Lista</a> que será oferecido na sua loja. <!--Reescrever o artigo de tipo de lista -->
-</div>
+>ℹ️ Antes de editar este template, é necessário [criar o Tipo de Lista](http://help.vtex.com/pt/tutorial/criando-tipo-de-lista) que será oferecido na sua loja. <!--Reescrever o artigo de tipo de lista -->
 
 O template para criação de listas está localizado na rota `giftlist/create`. O template default desta rota é o `new-GiftList-Create`, localizado na seção `HTML Templates` do seu CMS.
 
diff --git a/docs/tutorials/pt/disable-cloudflare-proxy.md b/docs/tutorials/pt/disable-cloudflare-proxy.md
index 0e23da548..a4a22250a 100644
--- a/docs/tutorials/pt/disable-cloudflare-proxy.md
+++ b/docs/tutorials/pt/disable-cloudflare-proxy.md
@@ -27,6 +27,4 @@ Observe que, se o proxy estiver ligado, o ícone estará em laranja com o texto
 
 É importante notar que o resultado da desabilitação do proxy da CloudFlare pode demorar um pouco para ser observado, pois é necessário que o cache seja renovado.
 
-<div class="alert alert-info">
-Caso queira usar o CDN e o WAF da Cloudflare, pode-se inserir um proxy reverso em frente aos serviços da VTEX. Note que essa configuração não é recomendada, visto que a VTEX já oferece serviços de CDN e WAF no seu próprio serviço de borda. Falhas de CDNs externas não implicam em falhas nos sistemas da VTEX. Não temos responsabilidade por CDNs de terceiros. 
-</div>
+>ℹ️ Caso queira usar o CDN e o WAF da Cloudflare, pode-se inserir um proxy reverso em frente aos serviços da VTEX. Note que essa configuração não é recomendada, visto que a VTEX já oferece serviços de CDN e WAF no seu próprio serviço de borda. Falhas de CDNs externas não implicam em falhas nos sistemas da VTEX. Não temos responsabilidade por CDNs de terceiros.
diff --git a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
index 4c1359a74..c5ce5e9ba 100644
--- a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -23,9 +23,7 @@ Com [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-b
 
 Para aderir ao VTEX Ad Network e exibir anúncios na sua loja, basta instalar o aplicativo VTEX Ad Network para lojas.
 
-<div class="alert alert-warning">
-Por ora, lojas VTEX podem disponibilizar inventário de anúncios apenas em frentes de loja que utilizam <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a>.
-</div>
+>⚠️ Por ora, lojas VTEX podem disponibilizar inventário de anúncios apenas em frentes de loja que utilizam [Store Framework](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework).
 
 ## Acompanhar resultados
 
diff --git a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
index 4614a54a2..4763cab09 100644
--- a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
@@ -15,10 +15,9 @@ legacySlug: relevancia-dinamica-no-intelligent-search-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-  <p>Para os clientes selecionados, a funcionalidade está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É possível que taxas extras se apliquem futuramente.</p>
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
+>
+> Para os clientes selecionados, a funcionalidade está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É possível que taxas extras se apliquem futuramente.
 
 O Intelligent Search é uma solução de busca da plataforma VTEX. Ele apresenta resultados relevantes com base no catálogo desde a primeira interação do usuário com a loja, seja por meio da barra de busca, navegando pelas categorias, ou mesmo pelas vitrines de produtos. 
 
diff --git a/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md b/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md
index 511a34ffe..29ea2a83f 100644
--- a/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md
+++ b/docs/tutorials/pt/edit-a-required-field-on-profile-system-of-master-data.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 O Master Data é um módulo da plataforma VTEX usado para armazenar e organizar documentos. Descubra como tornar obrigatório um campo de formulário no Master Data nas instruções abaixo.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 Para selecionar um campo de preenchimento que deseja tornar obrigatório, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/enable-https-throughout-the-site.md b/docs/tutorials/pt/enable-https-throughout-the-site.md
index 436d5ceb1..bab729b32 100644
--- a/docs/tutorials/pt/enable-https-throughout-the-site.md
+++ b/docs/tutorials/pt/enable-https-throughout-the-site.md
@@ -58,10 +58,11 @@ Todas as páginas do site podem ser alteradas individualmente conforme o artigo
 
 É possível alterar o protocolo em todas as pastas de uma única vez com o uso de nossa API, documentada [nesta coleção do Postman](https://developers.vtex.com/reference/change-uri-schema).
 
-<div class="alert alert-warning">
-<p><strong>Atenção:</strong> evite ter o protocolo HTTPS ativado somente em algumas páginas. Ao acessar uma página HTTPS, depois ir para uma página HTTP da mesma loja, o navegador tentará fazer a leitura dos seus recursos forçadamente em HTTPS, e isso pode gerar problemas.</p>
-<p>O adequado é ativar o HTTPS em todo o site de uma única vez.</p>
-<p>O mesmo vale para websites desktop e mobile (website filho), aonde é necessário tratar o HTTPS de ambos ao mesmo tempo.</p></div>
+>⚠️ **Atenção:** evite ter o protocolo HTTPS ativado somente em algumas páginas. Ao acessar uma página HTTPS, depois ir para uma página HTTP da mesma loja, o navegador tentará fazer a leitura dos seus recursos forçadamente em HTTPS, e isso pode gerar problemas.
+>
+> O adequado é ativar o HTTPS em todo o site de uma única vez.
+>
+> O mesmo vale para websites desktop e mobile (website filho), aonde é necessário tratar o HTTPS de ambos ao mesmo tempo.
 
 ## Limitações
 
diff --git a/docs/tutorials/pt/enabling-2-factor-authentication-login.md b/docs/tutorials/pt/enabling-2-factor-authentication-login.md
index dec14e58e..a322b393e 100644
--- a/docs/tutorials/pt/enabling-2-factor-authentication-login.md
+++ b/docs/tutorials/pt/enabling-2-factor-authentication-login.md
@@ -21,9 +21,15 @@ Isto porque, no momento do login, além de exigir o e-mail e a senha, o sistema
 
 Como essa chave é gerada no momento do login e tem prazo de validade curto, torna-se quase impossível que alguém entre em sua loja usando seus dados sem autorização. Sem o 2FA, basta que alguém saiba seu e-mail e sua senha para ter amplo acesso à conta da sua loja.
 
-<div class="alert alert-danger">
-A partir do dia <strong>16 de novembro de 2017</strong>, a autenticação de 2 fatores (2FA) torna-se <strong>obrigatória para todos os e-mails</strong> no Admin da VTEX.<br><br>Sem 2FA, você <b>não conseguirá logar</b> usando e-mail e senha.<br><br>Essa obrigatoriedade vale apenas para login com e-mail e senha, e não para os demais métodos de login (Google, Facebook e token).
-</div>
+>❗ A partir do dia **16 de novembro de 2017**, a autenticação de 2 fatores (2FA) torna-se **obrigatória para todos os e-mails** no Admin da VTEX.
+>
+> 
+>
+> Sem 2FA, você **não conseguirá logar** usando e-mail e senha.
+>
+> 
+>
+> Essa obrigatoriedade vale apenas para login com e-mail e senha, e não para os demais métodos de login (Google, Facebook e token).
 
 ## Como habilitar o 2FA
 
@@ -36,13 +42,9 @@ Há duas opções de autenticação:
 
 ![2FA - Select - PT](https://images.ctfassets.net/alneenqid6w5/3WRZKKU8LuW00UkeoUoIEY/d7db18f01bf30d5c5838f27b24f08e32/2FA_-_Select_-_PT.png)
 
-<div class="alert alert-danger">
-Recomendamos fortemente que você <strong>escolha a opção de autenticação por aplicativo</strong>, uma vez que na autenticação por SMS você depende de que não haja falhas na operadora de telefonia. Pelo aplicativo, a chave de acesso estará sempre à disposição quando for necessária.
-</div>
+>❗ Recomendamos fortemente que você **escolha a opção de autenticação por aplicativo**, uma vez que na autenticação por SMS você depende de que não haja falhas na operadora de telefonia. Pelo aplicativo, a chave de acesso estará sempre à disposição quando for necessária.
 
-<div class="alert alert-danger">
-Se você configurou o 2FA por SMS e o código está demorando a chegar, provavelmente a causa do problema está na operadora de telefone. Habilite o 2FA por aplicativo, como explicado abaixo.
-</div>
+>❗ Se você configurou o 2FA por SMS e o código está demorando a chegar, provavelmente a causa do problema está na operadora de telefone. Habilite o 2FA por aplicativo, como explicado abaixo.
 
 ### Habilitar o 2FA por aplicativo
 
@@ -57,9 +59,7 @@ Para usar uma chave gerada por aplicativo de autenticação:
   *O código do app é atualizado periodicamente. Não será necessário memorizá-lo, basta consultar o aplicativo sempre que precisar.*
   ![2FA - App Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/NUKFyLNA9fWsBewD445Uy/58da9e3065ebec81f1528554808eee56/2FA_-_App_Insert_Code_-_PT.png)
 
-<div class="alert alert-info">
-Se você fizer login usando e-mail e senha no mesmo computador, a chave de acesso será solicitada <strong>a cada 3 dias</strong>. Quando isso acontecer, basta consultar o código no aplicativo.
-</div>
+>ℹ️ Se você fizer login usando e-mail e senha no mesmo computador, a chave de acesso será solicitada **a cada 3 dias**. Quando isso acontecer, basta consultar o código no aplicativo.
 
 ### Habilitar o 2FA por SMS
 
@@ -73,9 +73,7 @@ Para usar uma chave enviada por mensagem de texto:
 
    ![2FA - SMS Insert Code - PT](https://images.ctfassets.net/alneenqid6w5/6KbuUvMFupmJEMN6kTOZ4E/bf998e866456c232965f4bd845b65db1/2FA_-_SMS_Insert_Code_-_PT.png)
 
-<div class="alert alert-warning">
-Não podemos garantir que sua operadora de telefonia conseguirá entregar a chave de acesso sempre que necessário. Caso a mensagem de texto da VTEX não chegue, tente reenviar o código ou <a href="#habilitar-o-2fa-por-aplicativo">habilitar o 2FA por aplicativo</a>.
-</div>
+>⚠️ Não podemos garantir que sua operadora de telefonia conseguirá entregar a chave de acesso sempre que necessário. Caso a mensagem de texto da VTEX não chegue, tente reenviar o código ou [habilitar o 2FA por aplicativo](#habilitar-o-2fa-por-aplicativo).
 
 ### 2FA para operadores de televendas
 
diff --git a/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md b/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
index 64be5c20e..cbfb06ae1 100644
--- a/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
+++ b/docs/tutorials/pt/enabling-3ds2-for-redsys-v2-integration.md
@@ -15,7 +15,7 @@ legacySlug: adicionar-suporte-a-3ds2-na-integracao-com-a-redsys-v2
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Agora, a funcionalidade 3DS2 também está disponível para pagamentos realizados via cartão de crédito e processados pelo gateway de pagamentos [Redsýs](https://help.vtex.com/pt/tutorial/configurar-gateway-redsys--7xRnMyzZS0kQoIG2ISagY8).
 
@@ -23,9 +23,7 @@ Agora, a funcionalidade 3DS2 também está disponível para pagamentos realizado
 
 Para mais detalhes, acesse o artigo [Fluxo de autenticação 3DS2: aceite pagamentos on-line de forma mais segura](https://help.vtex.com/pt/announcements/fluxo-de-autenticacao-3ds2-aceite-pagamentos-on-line-de-forma-mais-segura--6UdTjjVU1AcEQ2aE3Ftxsl).
 
-<div class="alert alert-danger">
-Antes de configurar o 3DS2, é importante garantir que a Redsýs já esteja configurada em sua loja e que a parceria comercial firmada esteja habilitada para a utilização do 3DS2.
-  </div>
+>❗ Antes de configurar o 3DS2, é importante garantir que a Redsýs já esteja configurada em sua loja e que a parceria comercial firmada esteja habilitada para a utilização do 3DS2.
 
 Neste tutorial, explicaremos como realizar essa integração por meio do Admin da VTEX via painel administrativo. 
 
diff --git a/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md b/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
index 6f2af423f..497a899fc 100644
--- a/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
+++ b/docs/tutorials/pt/enabling-local-stock-sale-in-vtex-sales-app.md
@@ -25,9 +25,7 @@ A Venda de estoque local permite o vendedor de uma loja física realizar vendas
 6. [Conectar conta franquia a loja física](#conectar-conta-franquia-a-loja-fisica)
 7. [Integração de ponto de venda](#integracao-de-ponto-de-venda)
 
-<div class="alert alert-info">
-<p>A Venda de estoque local só pode ser configurada em lojas que já utilizam o VTEX Sales App. Saiba como contratar e configurar na nossa track <a href="https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc">VTEX Sales App - Primeiros passos e configurações</a>.</p> 
-</div>
+>ℹ️ A Venda de estoque local só pode ser configurada em lojas que já utilizam o VTEX Sales App. Saiba como contratar e configurar na nossa track [VTEX Sales App - Primeiros passos e configurações](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc).
 
 ## Criar uma conta franquia
 
@@ -64,9 +62,7 @@ Caso todos os seus produtos estejam listados sem quantidade, será necessário a
 
 Você pode [habilitar venda de item sem estoque](#habilitar-venda-de-item-sem-estoque-opcional), caso você queira garantir que o item em mãos estará sempre disponível para o cliente em loja. 
 
-<div class="alert alert-info">
-Caso você tenha criado dois estoques diferentes - um para o ecommerce e outro para o VTEX Sales App -, fique atento para gerenciar corretamente a quantidade de peças para cada um dos estoques.
-</div>
+>ℹ️ Caso você tenha criado dois estoques diferentes - um para o ecommerce e outro para o VTEX Sales App -, fique atento para gerenciar corretamente a quantidade de peças para cada um dos estoques.
 
 ## Conectar conta franquia a loja física
 
@@ -79,9 +75,7 @@ Para isso, escolha um vendedor cadastrado na loja em que deseja testar a Venda e
 2. Busque por um item que existe no estoque da conta franquia cadastrado. Este item deverá estar exibindo a quantidade disponível correspondente ao inventário do seller.
 ![instore-pdp-pt](https://images.ctfassets.net/alneenqid6w5/7CtYO9vUzaunI2qO8onP7B/861791e5b4f8f2304ae1a5a7ae577ad8/image.png)
 
-<div class="alert alert-info">
-<p>Caso você tenha habilitado estoque infinito, o número exibido será uma quantidade acima de 1 milhão de itens e não será alterado ao realizar uma venda.</p> 
-</div>
+>ℹ️ Caso você tenha habilitado estoque infinito, o número exibido será uma quantidade acima de 1 milhão de itens e não será alterado ao realizar uma venda.
 
 ### Habilitar venda de item sem estoque (opcional)
 
diff --git a/docs/tutorials/pt/enabling-payments-with-bitcoin.md b/docs/tutorials/pt/enabling-payments-with-bitcoin.md
index 27b94f312..2f5f6780f 100644
--- a/docs/tutorials/pt/enabling-payments-with-bitcoin.md
+++ b/docs/tutorials/pt/enabling-payments-with-bitcoin.md
@@ -19,9 +19,7 @@ A plataforma VTEX oferece suporte para sua loja receber pagamentos na moeda digi
 
 Para utilizar o Bitcoin em sua loja, você precisa ter cadastrado uma afiliação de gateway capaz de processar esse meio de pagamento e realizar a configuração descrita abaixo:
 
-<div class="alert alert-warning">
-  Caso o conector a ser escolhido (no <b>Passo 7.</b>) ainda não estiver cadastrado em sua loja, será exibida a mensagem “(Configurar)” após o nome do conector. Nesta situação, escolha outro conector disponível ou realize o seu cadastro. Para saber mais, acesse <a href="https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Cadastrar afiliações de gateway</a>.
-</div>
+>⚠️ Caso o conector a ser escolhido (no **Passo 7.**) ainda não estiver cadastrado em sua loja, será exibida a mensagem “(Configurar)” após o nome do conector. Nesta situação, escolha outro conector disponível ou realize o seu cadastro. Para saber mais, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 ## Configurar condição de pagamento bitcoin
 
diff --git a/docs/tutorials/pt/enter-tracking-number-on-orders-already-invoiced.md b/docs/tutorials/pt/enter-tracking-number-on-orders-already-invoiced.md
index 5616727a7..40c4fdbd2 100644
--- a/docs/tutorials/pt/enter-tracking-number-on-orders-already-invoiced.md
+++ b/docs/tutorials/pt/enter-tracking-number-on-orders-already-invoiced.md
@@ -24,9 +24,7 @@ Você pode inserir o número de rastreio (tracking number) em pedidos já fatura
 5. Preencha o campo **Número de rastreio** com o número.
 6. CLique em `Salvar`.
 
-<div class="alert alert-warning">
-O Admin VTEX não permite a importação em massa, por arquivos, dos números de rastreio de pedidos. O método normalmente usado para isso é a integração entre a VTEX e o ERP da loja. Se o seu ERP está integrado à VTEX, é possível fazer essa importação via API.
-</div>
+>⚠️ O Admin VTEX não permite a importação em massa, por arquivos, dos números de rastreio de pedidos. O método normalmente usado para isso é a integração entre a VTEX e o ERP da loja. Se o seu ERP está integrado à VTEX, é possível fazer essa importação via API.
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/entering-tax-receipts-in-the-order.md b/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
index a97a94461..0c86ee1c1 100644
--- a/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
+++ b/docs/tutorials/pt/entering-tax-receipts-in-the-order.md
@@ -25,9 +25,7 @@ Com a inserção da nota fiscal com o valor completo do pedido, o mesmo passará
 
 Também é possível a inserção da nota fiscal parcial, quando são necessárias várias notas fiscais para atingir o valor total da compra. 
 
-<div class="alert alert-info">
-  <p>Somente após atingir o valor total do pedido o status será alterado para <strong>Faturado</strong>.</p>
-</div>
+>ℹ️ Somente após atingir o valor total do pedido o status será alterado para **Faturado**.
 
 A nota fiscal demanda atenção nos seguintes pontos:
 
@@ -39,6 +37,4 @@ Quando a URL e o código de rastreio estão inseridos, a cada atualização do s
 
 O **Conversation Tracker** depende da inserção de algum valor nesses campos. Caso não tenha um número de rastreamento, basta inserir um valor qualquer para ativar o sistema de notificação.
 
-<div class="alert alert-danger">
-É possível inserir mais de uma nota fiscal no pedido, no entanto a soma total dos valores das notas deve coincidir com o valor total do pedido.
-</div>
+>❗ É possível inserir mais de uma nota fiscal no pedido, no entanto a soma total dos valores das notas deve coincidir com o valor total do pedido.
diff --git a/docs/tutorials/pt/erasing-customer-data.md b/docs/tutorials/pt/erasing-customer-data.md
index c6556442f..ba50aa2bb 100644
--- a/docs/tutorials/pt/erasing-customer-data.md
+++ b/docs/tutorials/pt/erasing-customer-data.md
@@ -35,9 +35,7 @@ Se a sua loja armazena informações de clientes em outras entidades de dados, v
 
 2. Utilize a requisição [Delete document](https://developers.vtex.com/vtex-rest-api/reference/deletedocument-1)
 
-<div class="alert alert-danger">
-Não realize esse processo para as entidades <b>CL</b> e <b>AD</b>.
-</div>
+>❗ Não realize esse processo para as entidades **CL** e **AD**.
 
 ## Solicitar exclusão via suporte
 
diff --git a/docs/tutorials/pt/events-available-in-audit.md b/docs/tutorials/pt/events-available-in-audit.md
index 0d69b5c79..ec10c00c2 100644
--- a/docs/tutorials/pt/events-available-in-audit.md
+++ b/docs/tutorials/pt/events-available-in-audit.md
@@ -39,9 +39,7 @@ Confira a seguir a lista dos possíveis eventos disponíveis no [Audit](https://
   <p>Caso você visualize no Audit algum evento que não esteja listado aqui, por favor nos informe usando a <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback de documentação</a>.</p>
   </div>
 
-<div class="alert alert-warning">
-  <p>Nas opções de filtros do Audit, você pode encontrar <strong>Opções de envio</strong>, <strong>Profile System</strong> e <strong>Billing</strong> além das aplicações citadas abaixo. Essas opções se referem a recursos internos ou funcionalidades em fase beta fechada, portanto, a maior parte das contas não terão eventos associados.</p>
-</div>
+>⚠️ Nas opções de filtros do Audit, você pode encontrar **Opções de envio**, **Profile System** e **Billing** além das aplicações citadas abaixo. Essas opções se referem a recursos internos ou funcionalidades em fase beta fechada, portanto, a maior parte das contas não terão eventos associados.
 
 ## OMS
 
diff --git a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
index c4d928fd3..d55a00ec8 100644
--- a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
@@ -51,9 +51,7 @@ Na planilha de importação, a única coluna a ser preenchida é a `ValorEspecif
 
 A estrutura da planilha apresenta uma linha para cada campo do produto ou SKU, ou seja, o mesmo produto ou SKU será apresentado diversas vezes de acordo com os campos existentes em sua categoria.
 
-<div class="alert alert-warning">
-  <p>Na planilha exportada, a coluna referente a "ValorEspecificacao" é "NomeCampoValor (Não alterável)". Ao preencher o campo, a grafia das características deve ser exata. Letras maiúsculas e minúsculas fazem diferença nesse caso.</p>
-  </div>
+>⚠️ Na planilha exportada, a coluna referente a "ValorEspecificacao" é "NomeCampoValor (Não alterável)". Ao preencher o campo, a grafia das características deve ser exata. Letras maiúsculas e minúsculas fazem diferença nesse caso.
 
 Siga os passos abaixo para importar a planilha:
 
diff --git a/docs/tutorials/pt/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md b/docs/tutorials/pt/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
index 3daab0afc..977265d3b 100644
--- a/docs/tutorials/pt/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
+++ b/docs/tutorials/pt/exporting-customers-who-signed-up-for-the-availability-notification-notify-me.md
@@ -15,9 +15,7 @@ legacySlug: como-exportar-os-clientes-cadastrados-no-avise-me
 subcategory: 5yDQmr18K4GgQAeGwq8USa
 ---
 
-<div class="alert alert-warning">
-  <p>Este artigo se aplica à opção <strong>Avise-me</strong> apenas em lojas que utilizam o <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>. Em lojas que utilizam <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, é necessário seguir as instruções do guia <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify">Availability Notify</a>.</p>
-</div>
+>⚠️ Este artigo se aplica à opção **Avise-me** apenas em lojas que utilizam o [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). Em lojas que utilizam [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), é necessário seguir as instruções do guia [Availability Notify](https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify).
 
 Para exportar os dados dos clientes que se cadastraram na base de notificação de disponibilidade ([Avise-me](https://help.vtex.com/pt/tutorial/configurar-o-avise-me--2VqVifQuf6Co2KG048Yu6e)), siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/exporting-data.md b/docs/tutorials/pt/exporting-data.md
index f449fb7d3..65bd9fbba 100644
--- a/docs/tutorials/pt/exporting-data.md
+++ b/docs/tutorials/pt/exporting-data.md
@@ -17,9 +17,7 @@ subcategory: 2AThnkEZAYbk4G4EIs53rL
 
 A exportação de dados em massa de registros no Master Data v1 pode ser feita tanto por API quanto por planilha. Este documento tem como objetivo demonstrar o passo a passo necessário para a exportação de dados por planilha.
 
-<div class="alert alert-warning">
-A operação de exportar dados do Master Data não é instantânea, e o tempo de execução dela depende da quantidade de dados no Master Data. Por isso, em lojas com muitos dados e com uma alta frequência de atualização, o arquivo exportado pode ficar desatualizado em relação aos novos dados. Caso isso ocorra, a solução deve ser exportar os dados novamente, de preferência quando não há muitas atualizações ocorrendo (por exemplo, fora do horário comercial ou em fins de semana).
-</div>
+>⚠️ A operação de exportar dados do Master Data não é instantânea, e o tempo de execução dela depende da quantidade de dados no Master Data. Por isso, em lojas com muitos dados e com uma alta frequência de atualização, o arquivo exportado pode ficar desatualizado em relação aos novos dados. Caso isso ocorra, a solução deve ser exportar os dados novamente, de preferência quando não há muitas atualizações ocorrendo (por exemplo, fora do horário comercial ou em fins de semana).
 
 ## Exportar relatório com dados do Master Data v1
 
diff --git a/docs/tutorials/pt/exporting-orders-in-orders-module.md b/docs/tutorials/pt/exporting-orders-in-orders-module.md
index e980c3654..9d0c00245 100644
--- a/docs/tutorials/pt/exporting-orders-in-orders-module.md
+++ b/docs/tutorials/pt/exporting-orders-in-orders-module.md
@@ -19,9 +19,7 @@ O processo de exportação de pedidos pode ser realizado através da tela **Todo
 
 A exportação de pedidos gera um relatório no formato .csv que contém uma série de detalhes sobre os pedidos da sua loja. Para saber quais são as informações apresentadas no relatório exportado, [leia o tutorial sobre os campos da planilha de pedidos](https://help.vtex.com/pt/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
 
-<div class="alert alert-info">
-<p>Quando o número de pedidos solicitados na exportação é muito alto, o processo pode causar lentidão. Por isso, existe uma limitação no número de pedidos selecionados. Atualmente, é possível exportar até 50 mil pedidos por vez</b>.</p>
-</div>
+>ℹ️ Quando o número de pedidos solicitados na exportação é muito alto, o processo pode causar lentidão. Por isso, existe uma limitação no número de pedidos selecionados. Atualmente, é possível exportar até 50 mil pedidos por vez</b>.
 
 Siga as instruções abaixo para gerar o relatório:
 
diff --git a/docs/tutorials/pt/faq-security-restricted-content.md b/docs/tutorials/pt/faq-security-restricted-content.md
index 92388cb00..a4d3e9ebf 100644
--- a/docs/tutorials/pt/faq-security-restricted-content.md
+++ b/docs/tutorials/pt/faq-security-restricted-content.md
@@ -17,9 +17,7 @@ subcategory:
 
 # FAQ - Segurança (conteúdo restrito)
 
-<div class="alert alert-danger">
-  <p>Não compartilhe as informações desta FAQ com usuários que não possuem acesso ao Admin VTEX.</p>
-</div>
+>❗ Não compartilhe as informações desta FAQ com usuários que não possuem acesso ao Admin VTEX.
 
 Para apoiar as avaliações de risco de seus clientes, a VTEX disponibiliza páginas de FAQ com as principais perguntas e respostas relacionadas à estrutura e à segurança da plataforma. Este conteúdo é restrito a usuários com acesso ao Admin VTEX. As perguntas e respostas de teor público estão disponíveis na [FAQ - Segurança](https://help.vtex.com/pt/tutorial/risk-assessment--4K97IpqkpCpDYsZOSxtfkX) no VTEX Help Center.
 
diff --git a/docs/tutorials/pt/fill-out-the-stock-spreadsheet.md b/docs/tutorials/pt/fill-out-the-stock-spreadsheet.md
index 88839ca8c..e97917cb8 100644
--- a/docs/tutorials/pt/fill-out-the-stock-spreadsheet.md
+++ b/docs/tutorials/pt/fill-out-the-stock-spreadsheet.md
@@ -24,9 +24,7 @@ Além disso, o preenchimento correto da planilha depende de duas regras. São el
 - Cada coluna da planilha deve conter ou um número ou um texto;
 - A atualização da quantidade de SKUs deve ser feita na coluna __TotalQuantity__. 
 
-<div class="alert alert-warning">
-<strong>Atenção</strong>: caso estas indicações não sejam respeitadas, o sistema pode não aceitar a importação da planilha ou o número de itens a venda pode ficar incorreto.
-</div>
+>⚠️ **Atenção**: caso estas indicações não sejam respeitadas, o sistema pode não aceitar a importação da planilha ou o número de itens a venda pode ficar incorreto.
 
 A seguir, confira o significado de cada campo da planilha de estoque.
 
diff --git a/docs/tutorials/pt/filling-in-fields-in-the-import-spreadsheet.md b/docs/tutorials/pt/filling-in-fields-in-the-import-spreadsheet.md
index 0c20138e3..62f462f45 100644
--- a/docs/tutorials/pt/filling-in-fields-in-the-import-spreadsheet.md
+++ b/docs/tutorials/pt/filling-in-fields-in-the-import-spreadsheet.md
@@ -17,15 +17,16 @@ subcategory: 2u48reCb68K48EAcm86ccM
 
 Na VTEX, é possível [importar produtos e SKUs em massa por meio de uma planilha](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/17PxekVPmVYI4c3OCQ0ddJ#planilha). Para entender o significado de cada campo da planilha, veja abaixo a descrição completa dos campos de Produto e SKU relacionados no Excel.
 
-<div class="alert alert-danger">
-  <p>Ao preencher <b>TextoLink</b>, <b>NomeDepartamento</b>, <b>NomeCategoria</b> e <b>Marca</b>, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Ao preencher **TextoLink**, **NomeDepartamento**, **NomeCategoria** e **Marca**, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 **SkuId:** número único identificador do SKU. Caso esse campo já esteja preenchido, não é possível alterá-lo. Para adicionar um novo SKU, deixe a coluna vazia.
 
diff --git a/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md b/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
index 474c1e0f1..5e4026369 100644
--- a/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
+++ b/docs/tutorials/pt/filling-out-an-import-spreadsheets-fixed-price-fields.md
@@ -35,4 +35,8 @@ Os próximos campos são opcionais na planilha, exportados somente para exibiç
 - **Ref ID (View Only):** código de referência único utilizado para facilitar a organização do catálogo de produtos. Esse ID geralmente é criado pelos sistemas internos da loja.
 - **EAN (View Only):** código de identificação único do SKU (código de barras).
 
-<div class="alert alert-warning">Planilhas de preços usadas para importação têm um limite de tamanho de 1 MB. <br/><br/>Se sua planilha atual excede este limite, recomendamos dividí-la em vários arquivos, <strong>certificando-se que os preços que se referem ao mesmo SKU sejam mantidos juntos na mesma planilha</strong>.</div>
+>⚠️ Planilhas de preços usadas para importação têm um limite de tamanho de 1 MB. 
+>
+> 
+>
+> Se sua planilha atual excede este limite, recomendamos dividí-la em vários arquivos, **certificando-se que os preços que se referem ao mesmo SKU sejam mantidos juntos na mesma planilha**.
diff --git a/docs/tutorials/pt/filtering-all-orders.md b/docs/tutorials/pt/filtering-all-orders.md
index 0f7966021..614118c8e 100644
--- a/docs/tutorials/pt/filtering-all-orders.md
+++ b/docs/tutorials/pt/filtering-all-orders.md
@@ -65,9 +65,7 @@ Para buscar em todos os pedidos, digite o termo desejado na caixa de busca. Isso
 
 ![search_bar_without_time_limit_PT](https://images.ctfassets.net/alneenqid6w5/2ii9VFh5uRpG4Ad0nwIIN0/c87949487d1e9ad947ea437c3f368431/search_bar_without_time_limit_PT.png)
 
-<div class="alert alert-danger">
-A busca em todos os pedidos não pode ser associada a outros filtros. Ou seja, ao remover o limite de datas da busca, qualquer filtro ativo se torna inativo. Se o termo da busca é removido ou o switch <i class="fas fa-toggle-off"></i> de busca em todos os pedidos é desativado, os filtros anteriormente configurados se tornam ativos novamente.
-</div>
+>❗ A busca em todos os pedidos não pode ser associada a outros filtros. Ou seja, ao remover o limite de datas da busca, qualquer filtro ativo se torna inativo. Se o termo da busca é removido ou o switch <i class="fas fa-toggle-off"></i> de busca em todos os pedidos é desativado, os filtros anteriormente configurados se tornam ativos novamente.
 
 ### Buscar associando filtros
 
diff --git a/docs/tutorials/pt/filters.md b/docs/tutorials/pt/filters.md
index a66695dc5..1eff0049b 100644
--- a/docs/tutorials/pt/filters.md
+++ b/docs/tutorials/pt/filters.md
@@ -21,17 +21,13 @@ Quando um cliente seleciona um filtro (preço, cor, tamanho e marca), essa infor
 
 O **VTEX Intelligent Search** usa o contexto dos produtos apresentados como resultados de busca para saber exatamente quais filtros devem ser exibidos para o cliente, seguindo as configurações do Catálogo.
 
-<div class="alert alert-info">
-  <p>A ordenação dos filtros de marca, departamento, categoria e subcategoria é determinada pela quantidade de produtos cadastrados em cada um dos filtros.</p>
-</div>
+>ℹ️ A ordenação dos filtros de marca, departamento, categoria e subcategoria é determinada pela quantidade de produtos cadastrados em cada um dos filtros.
 
 Exemplo: considere que o filtro *Tamanho* está cadastrado no catálogo de uma loja e somente o produto *tênis* possui a especificação *Tamanho* preenchida. Em uma pesquisa pelo termo *tênis*, *Tamanho* vai aparecer como um filtro. Já em uma pesquisa por qualquer outro termo, como *boné*, essa especificação não vai ser exibida como filtro.
 
 O resultado de busca não vai exibir uma especificação quando só existe ela como filtro ou o cliente a tenha acessado pelo menu da loja. Exemplo: se um cliente seleciona o filtro  Eletrodomésticos diretamente do menu, não será exibido Departamentos como um filtro lateral.
 
-<div class="alert alert-info">
-  <p>Caso o resultado da busca retorne mais de 30 mil produtos, alguns valores de filtros serão omitidos, uma vez que somente as especificações de uma parte desses produtos serão consideradas.</p>
-</div>
+>ℹ️ Caso o resultado da busca retorne mais de 30 mil produtos, alguns valores de filtros serão omitidos, uma vez que somente as especificações de uma parte desses produtos serão consideradas.
 
 A funcionalidade de Filtros apresenta as seguintes funções:
 
@@ -46,6 +42,4 @@ A funcionalidade de Filtros apresenta as seguintes funções:
 
 Confira o guia [Search Result](https://developers.vtex.com/docs/apps/vtex.search-result#:~:text=%7D-,filter%2Dnavigator.v3%20block,-This%20block%20renders) no Developer Portal para mais detalhes técnicos sobre a utilização de filtros.
 
-<div class="alert alert-warning">
-  <p>Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.</p>
-</div>
+>⚠️ Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.
diff --git a/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md b/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
index 3e6633d41..41ca22cb4 100644
--- a/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
+++ b/docs/tutorials/pt/find-marketplaces-and-sellers-in-the-vtex-network.md
@@ -39,9 +39,7 @@ Para entrar em contato:
 4. Preencha o campo **Envie uma mensagem**.  
 5. Clique no botão __Enviar__.   
 
-<div class="alert alert-info">
-O potencial parceiro comercial receberá um e-mail com as informações preenchidas. Caso o interesse seja mútuo, o encarregado pelo seller ou marketplace poderá entrar em contato e negociar os termos do acordo entre marketplace e seller.
-</div>
+>ℹ️ O potencial parceiro comercial receberá um e-mail com as informações preenchidas. Caso o interesse seja mútuo, o encarregado pelo seller ou marketplace poderá entrar em contato e negociar os termos do acordo entre marketplace e seller.
 
 ## Perfil da loja
 ![Network profile PT](https://images.ctfassets.net/alneenqid6w5/0F1E1mqf6hD5FLzVGqBA7/3566eb996b94604d3449fa0ae773cf27/Marketplace_store_profile_PT.gif)
@@ -56,9 +54,7 @@ O potencial parceiro comercial receberá um e-mail com as informações preenchi
 8. Clique em __Aceitar__.  
 9. Clique em __Criar perfil__.   
 
-<div class="alert alert-warning">
-É necessário ativar o perfil de seller ou marketplace para receber mensagens e entrar em contato com outros parceiros. 
-</div>
+>⚠️ É necessário ativar o perfil de seller ou marketplace para receber mensagens e entrar em contato com outros parceiros.
 
 ### Informações da loja
 - __Logo__: imagem do logo da sua loja, com tamanho máximo de 500kB, que identificará sua loja no Marketplace Network.   
diff --git a/docs/tutorials/pt/find-sellers.md b/docs/tutorials/pt/find-sellers.md
index ab497c4dc..f2d1def79 100644
--- a/docs/tutorials/pt/find-sellers.md
+++ b/docs/tutorials/pt/find-sellers.md
@@ -19,9 +19,7 @@ Apágina **Encontrar sellers** disponibiliza e facilita o encontro e a comunica
 
 Para utilizar a página,você precisa criar um **Perfil da loja,** saiba como acessando a documentação.
 
-<div class="alert alert-info">
-Note que a <b>Encontra sellers</b> é uma ferramenta que promove o contato entre potenciais parceiros,mas não é uma etapa obrigatória para atuar como Marketplace e seller na VTEX. Se você deseja atuar como marketplace e seller simultaneamente,leia a documentação <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace">Estratégias de marketplace na VTEX</a>.
-</div>
+>ℹ️ Note que a **Encontra sellers** é uma ferramenta que promove o contato entre potenciais parceiros,mas não é uma etapa obrigatória para atuar como Marketplace e seller na VTEX. Se você deseja atuar como marketplace e seller simultaneamente,leia a documentação [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#atuar-como-marketplace).
 
 Para acessar a listagem de sellers cadastrados navegue em **Marketplace > Encontrar Sellers** ou digite **Encontrar Sellers** na barra de busca.
 
diff --git a/docs/tutorials/pt/fromto-of-payment-means-on-webservice.md b/docs/tutorials/pt/fromto-of-payment-means-on-webservice.md
index db3a7a3b9..e1a51c595 100644
--- a/docs/tutorials/pt/fromto-of-payment-means-on-webservice.md
+++ b/docs/tutorials/pt/fromto-of-payment-means-on-webservice.md
@@ -15,9 +15,11 @@ legacySlug: depara-dos-meios-de-pagamentos-no-webservice
 subcategory: 1vwB9FtTSQmcSewQw02QoW
 ---
 
-<div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
-<p><strong>Todos os outros métodos estão descontinuados.</strong></p>
-<p>Use as APIs REST equivalentes, disponíveis em nosso <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: somente os métodos SOAP pertinentes ao **catálogo** são válidos.
+>
+> **Todos os outros métodos estão descontinuados.**
+>
+> Use as APIs REST equivalentes, disponíveis em nosso [Developer Docs](//help.vtex.com/developer-docs/).
 
 O Web Service de pagamentos utiliza alguns códigos para cada uma das formas de pagamentos disponíveis na área do PCI Gateway. Esse código de cada pagamento é fixo e não depende do integrador.
 
diff --git a/docs/tutorials/pt/fulfillment-magalu.md b/docs/tutorials/pt/fulfillment-magalu.md
index d5c17a1a8..b01e9367e 100644
--- a/docs/tutorials/pt/fulfillment-magalu.md
+++ b/docs/tutorials/pt/fulfillment-magalu.md
@@ -19,9 +19,7 @@ Ao finalizar a [integração](https://help.vtex.com/pt/tracks/configurar-integra
 
 Além da integração básica, lojistas VTEX podem integrar com o [**Fulfillment Magalu**](https://unimagalu.com.br/full/), que é um serviço disponível a lojistas que já vendem no Magalu Marketplace. Este serviço disponibiliza a operação de armazenamento e entrega do Magalu para seus produtos mais vendidos no marketplace. 
 
-<div class="alert alert-warning">
-Somente os produtos mais vendidos de uma loja, podem ser configurados com a opção de venda pelo Fulfillment Magalu.
-</div>
+>⚠️ Somente os produtos mais vendidos de uma loja, podem ser configurados com a opção de venda pelo Fulfillment Magalu.
 
 Todos os pedidos do tipo __Fulfillment Magalu__ podem ser acompanhados na tela de [Pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi) do Admin VTEX. O status desses pedidos são atualizados pelo Magalu Marketplace.
 
@@ -106,9 +104,7 @@ Para preencher especificações de produtos em massa por planilha, é necessári
 10. Clique em __Select__ para selecionar o arquivo com a planilha preenchida no seu computador.  
 11. Clique em `Importar`.  
 
-<div class="alert alert-danger">
-  Os SKUs que estiverem com o valor da especificação <code> magalu_fulfillment</code> preenchida como <code> false </code> ou um valor diferente de <code> true</code>, não serão apresentados no Magalu marketplace com a opção de envio Fulfillment Magalu.
-</div>
+>❗ Os SKUs que estiverem com o valor da especificação ` magalu_fulfillment` preenchida como ` false ` ou um valor diferente de ` true`, não serão apresentados no Magalu marketplace com a opção de envio Fulfillment Magalu.
 
 ### Configuração do conector  
 
diff --git a/docs/tutorials/pt/generating-a-har-file.md b/docs/tutorials/pt/generating-a-har-file.md
index 8e5e89a2f..92443452a 100644
--- a/docs/tutorials/pt/generating-a-har-file.md
+++ b/docs/tutorials/pt/generating-a-har-file.md
@@ -21,12 +21,9 @@ Um recurso útil para isso é o log de requests gerado pela ferramenta de desenv
 
 Por meio dele você pode gerar um __arquivo HAR__, que contém informações detalhadas sobre cada request. Depois, basta enviá-lo ao nosso time de suporte.
 
-<div class="alert alert-warning">
-O arquivo HAR contém informações sensíveis sobre sua loja. Compartilhe-o somente com o time de suporte VTEX.
-</div>
+>⚠️ O arquivo HAR contém informações sensíveis sobre sua loja. Compartilhe-o somente com o time de suporte VTEX.
 
-<div class="alert alert-warning"> Abaixo temos o passo a passo para gerar o arquivo HAR pelo <strong>Google Chrome</strong>, que é o modo mais recomendado por nós. Caso você deseje fazer o processo por meio de outros navegadores, como o Mozilla Firefox ou o Microsoft Edge, confira o procedimento correto <a href="https://support.zendesk.com/hc/pt-br/articles/204410413-Gera%25C3%25A7%25C3%25A3o-de-um-arquivo-HAR-para-resolu%25C3%25A7%25C3%25B5es-de-problemas#h_51858a69-ed0e-45a6-a25d-c9b8ba32ae32">neste link</a>.
-</div>
+>⚠️ Abaixo temos o passo a passo para gerar o arquivo HAR pelo **Google Chrome**, que é o modo mais recomendado por nós. Caso você deseje fazer o processo por meio de outros navegadores, como o Mozilla Firefox ou o Microsoft Edge, confira o procedimento correto [neste link](https://support.zendesk.com/hc/pt-br/articles/204410413-Gera%25C3%25A7%25C3%25A3o-de-um-arquivo-HAR-para-resolu%25C3%25A7%25C3%25B5es-de-problemas#h_51858a69-ed0e-45a6-a25d-c9b8ba32ae32).
 
 ### Como gerar o arquivo HAR no Google Chrome
 
diff --git a/docs/tutorials/pt/geolocation-at-checkout.md b/docs/tutorials/pt/geolocation-at-checkout.md
index 7afb57cd8..57a4e8a1c 100644
--- a/docs/tutorials/pt/geolocation-at-checkout.md
+++ b/docs/tutorials/pt/geolocation-at-checkout.md
@@ -44,9 +44,7 @@ Com a API Key em mãos, siga os passos abaixo:
 
 ![Geolocalizacao 1 PT](https://images.ctfassets.net/alneenqid6w5/1WnSV74cA82WY8kGscAiy2/68eeec258fd124695047187dc5e15b51/Geolocalizacao_1_PT.png)
 
-<div class="alert alert-info">
-Em alguns países, o Google Maps não realiza um mapping de alta qualidade. Com isso, pode acontecer de certos endereços serem mal escritos ou de o Google indicar um endereço incorreto. Nestes casos, deve-se corrigir o endereço diretamente no mapa.
-  </div>
+>ℹ️ Em alguns países, o Google Maps não realiza um mapping de alta qualidade. Com isso, pode acontecer de certos endereços serem mal escritos ou de o Google indicar um endereço incorreto. Nestes casos, deve-se corrigir o endereço diretamente no mapa.
 
 ### Configurando o polígono
 
diff --git a/docs/tutorials/pt/gift-card.md b/docs/tutorials/pt/gift-card.md
index c2b04b082..953c1703e 100644
--- a/docs/tutorials/pt/gift-card.md
+++ b/docs/tutorials/pt/gift-card.md
@@ -46,13 +46,9 @@ Para criar um novo vale-presente, confira o passo a passo:
   <li><b>Coleção</b>: determina a coleção de produtos que define os itens em que o vale poderá ser aplicado.</li>
 </ul><br>
 
-<div class="alert alert-warning">
-<strong>Atenção</strong>: o preenchimento dos campos “Valor” e “Data de expiração” é <strong>obrigatório</strong>. Caso o contrário, o vale-presente não será salvo.
-</div>
+>⚠️ **Atenção**: o preenchimento dos campos “Valor” e “Data de expiração” é **obrigatório**. Caso o contrário, o vale-presente não será salvo.
 
-<div class="alert alert-danger">
-A funcionalidade de criação de vales-presente limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
-</div>
+>❗ A funcionalidade de criação de vales-presente limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo [Restricting the use of GiftCards to a collection of products does not work](https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank).
 
 Depois de preencher os campos corretamente, o usuário poderá assinalar até três opções de configuração: 
 <ul>
@@ -62,9 +58,7 @@ Depois de preencher os campos corretamente, o usuário poderá assinalar até tr
 <br>
   <li>Por fim, clique no botão <b>Salvar</b>.</li>
 <br>
-<div class="alert alert-info">
-Não há limite para a criação de vales, porém apenas 8000 vales podem ser exportados por vez.
-</div>
+>ℹ️ Não há limite para a criação de vales, porém apenas 8000 vales podem ser exportados por vez.
 
 </ol>
 
@@ -85,13 +79,9 @@ Para criar mais de um vale-presente ao mesmo tempo (um lote), confira o passo a
   <li><b>Data de expiração</b>: trata-se da data de vigência da utilização de todos os vales do lote.</li>
   <li><b>Coleção</b>: determina a coleção de produtos que define os itens em que os vales poderão ser aplicados.</li>
   <br>
-  <div class="alert alert-warning">
-<strong>Atenção</strong>: o preenchimento dos campos “Quantidade de vales-presente”, “Valor” e “Data de Validade” é <strong>obrigatório</strong>. Caso o contrário, os vales-presente não serão salvos.
-</div>
+  >⚠️ **Atenção**: o preenchimento dos campos “Quantidade de vales-presente”, “Valor” e “Data de Validade” é **obrigatório**. Caso o contrário, os vales-presente não serão salvos.
 <br>
-  <div class="alert alert-danger">
-A funcionalidade de criação de vales-presente limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo <a href="https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank">Restricting the use of GiftCards to a collection of products does not work</a>.
-</div>
+  >❗ A funcionalidade de criação de vales-presente limitados por coleções de produtos não está funcionando. Mais informações sobre este problema podem ser encontrados no artigo [Restricting the use of GiftCards to a collection of products does not work](https://help.vtex.com/en/known-issues/restricting-the-use-of-giftcards-to-a-collection-of-products-does-not-work--7kdbZUdscJLo1sGY6bo1jp" target="_blank).
 <br>
   <li><b>Recarregável</b>: enquanto estes vales estiverem disponíveis, seus saldos poderão ser alterados.</li>
   <li><b>Reutilizável</b>: será possível realizar novas compras com estes vales até que seus valores sejam totalmente utilizados.</li>
@@ -102,9 +92,7 @@ Uma nova tela irá aparecer confirmando que foram gerados o número de vales-pre
 <br>
   <li>Por fim, clique no botão <b>Voltar</b>.</li>
 <br>
-<div class="alert alert-info">
-Não há limite para a criação de vales, porém apenas 8000 vales podem ser exportados por vez.
-</div>
+>ℹ️ Não há limite para a criação de vales, porém apenas 8000 vales podem ser exportados por vez.
 </ol>
 
 ## Como configurar o Vale-presente como meio de pagamento
diff --git a/docs/tutorials/pt/good-practices-for-the-golive-of-my-store.md b/docs/tutorials/pt/good-practices-for-the-golive-of-my-store.md
index 713222ce0..960b6e26f 100644
--- a/docs/tutorials/pt/good-practices-for-the-golive-of-my-store.md
+++ b/docs/tutorials/pt/good-practices-for-the-golive-of-my-store.md
@@ -18,35 +18,25 @@ subcategory: wz3FvYTctwuCwG206QUAi
 ## WarRoom pre-Golive
 Mesmo tendo definidos e desenvolvidos todos os fluxos de integrações e de navegação, um dos momentos mais críticos do projeto são os testes end-to-end, nos quais são validados os fluxos de navegação de usuário e são realizados os testes de faturamento. Certamente, surgirão temas importantes a resolver. 
 
-<div class="alert alert-info">
-O mais importante é que estejam em uma mesma mesa todos os tomadores de decisão (VTEX, Cliente, Agência) para otimizar a sinergia e resiliência da equipe diante de qualquer questão ou dúvida que possa surgir.
-</div>
+>ℹ️ O mais importante é que estejam em uma mesma mesa todos os tomadores de decisão (VTEX, Cliente, Agência) para otimizar a sinergia e resiliência da equipe diante de qualquer questão ou dúvida que possa surgir.
 
 ## Checklist de validação pré-Golive
 Segue uma planilha que contém um checklist sugerido com os principais pontos de atenção no momento de validar a loja, antes de realizar o Golive ao público: [Checklist de Validação pré-Golive](https://docs.google.com/spreadsheets/d/1demkpSZ2h7ut5TsKwiPdmK029BfaCp0wabeGADfA_W0/edit)
 
-<div class="alert alert-info">
-Momentos recomendados para validação:
-1. Um mês antes do Golive (dará tempo de agir se for detectada uma questão de bloqueio).
-2. Uma semana antes do Golive (dará tempo de agir em caso de demora ou esquecimento de algum tema de menor importância).
-</div>
+>ℹ️ Momentos recomendados para validação:
+> 1. Um mês antes do Golive (dará tempo de agir se for detectada uma questão de bloqueio).
+> 2. Uma semana antes do Golive (dará tempo de agir em caso de demora ou esquecimento de algum tema de menor importância).
 
 ## Certificado de segurança e apontamento de domínio para VTEX
 Este processo é realizado no momento do GoLive da loja. Permite que o atual responsável por seu domínio aponte para VTEX. Depois desta ação, ao acessar www.minhaloja.com, a nova loja estará apontada para a VTEX.
 
-<div class="alert alert-warning">
-Caso você utilize a Cloudflare como zona de DNS, pode ser necessário desabilitar o proxy de DNS e, consequentemente, desativar os serviços de CDN e WAF da Cloudflare. Mais informações podem ser encontradas no artigo <a href="https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb">Como desabilitar o proxy no Cloudflare</a>.
-</div>
+>⚠️ Caso você utilize a Cloudflare como zona de DNS, pode ser necessário desabilitar o proxy de DNS e, consequentemente, desativar os serviços de CDN e WAF da Cloudflare. Mais informações podem ser encontradas no artigo [Como desabilitar o proxy no Cloudflare](https://help.vtex.com/pt/tutorial/disable-cloudflare-proxy--75QqsXAqR7NdkRc1GZPiXb).
 
 Veja os detalhes do processo aqui: [Configurar o apontamento de DNS para a VTEX](/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex).
 
-<div class="alert alert-info">
-A recomendação principal é que um funcionário do cliente, com conhecimentos e experiência em DNS, realize estas configurações. Se esta configuração não estiver correta, sua loja pode sofrer uma queda por um erro humano. Caso venha a surgir algum problema, deve-se agir rapidamente para corrigí-lo e retomar a estabilidade das operações.
-</div>
+>ℹ️ A recomendação principal é que um funcionário do cliente, com conhecimentos e experiência em DNS, realize estas configurações. Se esta configuração não estiver correta, sua loja pode sofrer uma queda por um erro humano. Caso venha a surgir algum problema, deve-se agir rapidamente para corrigí-lo e retomar a estabilidade das operações.
 
 ## Canal de comunicação durante Golive
 Enquanto se desenvolve o processo de Golive, adicionalmente ao WarRoom, costuma ser conveniente manter um canal de comunicação ativo para compartilhar questões críticas ou requerimentos urgentes. Todos devem estar alinhados quanto ao caminho a seguir.
 
-<div class="alert alert-info">
-Para isto, costuma ser conveniente abrir um canal de Slack, Whatsapp ou Skype, durante a semana anterior e posterior ao Golive, onde se encontrem todos os participantes do projeto.
-</div>
+>ℹ️ Para isto, costuma ser conveniente abrir um canal de Slack, Whatsapp ou Skype, durante a semana anterior e posterior ao Golive, onde se encontrem todos os participantes do projeto.
diff --git a/docs/tutorials/pt/google-integration-warnings.md b/docs/tutorials/pt/google-integration-warnings.md
index 43141d966..9fccc2e8a 100644
--- a/docs/tutorials/pt/google-integration-warnings.md
+++ b/docs/tutorials/pt/google-integration-warnings.md
@@ -43,9 +43,7 @@ A seguir saiba em que situação ele é obrigatório e como preencher cada campo
 - **EAN/UPC:** é um campo obrigatório, existente no [módulo de Catálogo](https://help.vtex.com/pt/tutorial/catalogo-visao-geral--77M8ItLhDXs6aBdQTqToVe) e deve ser preenchido com o código de identificação único do SKU (código de barras), aceita até 13 caracteres numéricos.  
 - **Manufacturer code ou Código do fabricante:** é um campo obrigatório, existente no [módulo de Catálogo](https://help.vtex.com/pt/tutorial/catalogo-visao-geral--77M8ItLhDXs6aBdQTqToVe) e deve ser preenchido com o código fornecido pelo fabricante para identificar seu produto. Caso algum produto tenha um código específico, esse campo deve se preenchido.  
 
-<div class="alert alert-info">
-Os códigos EAN/UPC e Código do fabricante são obrigatórios em venda de produtos manufaturados. Saiba quando aplicar o <a href="https://support.google.com/merchants/answer/6324461?hl=pt-BR&ref_topic=6324338&sjid=10867212756007821438-SA">EAN/UPC</a> ou o <a href="https://support.google.com/merchants/answer/6324482?hl=pt-BR&ref_topic=6324338&sjid=10867212756007821438-SA">Código do fabricante</a> a um produto. 
-</div>  
+>ℹ️ Os códigos EAN/UPC e Código do fabricante são obrigatórios em venda de produtos manufaturados. Saiba quando aplicar o [EAN/UPC](https://support.google.com/merchants/answer/6324461?hl=pt-BR&ref_topic=6324338&sjid=10867212756007821438-SA) ou o [Código do fabricante](https://support.google.com/merchants/answer/6324482?hl=pt-BR&ref_topic=6324338&sjid=10867212756007821438-SA) a um produto.  
 
 - **Size:** é um campo obrigatório apenas para todos os produtos de vestuário que corresponde à categoria [ID1604](https://support.google.com/merchants/answer/6324492?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) e calçados que correspondem à categoria [ID187](https://support.google.com/merchants/answer/6324492?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) no Google. Se aplicável ao seu produto preencha com o tamanho referente ao SKU.  
 
@@ -67,9 +65,7 @@ O campo Color ou cor, é um [campo customizado](https://help.vtex.com/pt/tutoria
 
 Campo desse tipo suporta o preenchimento de valores alfanuméricos como, **Verde, Preto, Amarelo, Rosa**.
 
-<div class="alert alert-info">
-Cada SKU só permite uma cor.
-</div>  
+>ℹ️ Cada SKU só permite uma cor.  
 
 - **Gender:** é um campo obrigatório apenas para todos os itens de vestuário e acessórios que corresponde à [categoria ID166](https://support.google.com/merchants/answer/6324479?sjid=6190195010935556339-SA&visit_id=638479454885115656-3876849034&rd=1) no Google. Se aplicável ao seu produto preencha com a cor referente ao SKU.  
 
diff --git a/docs/tutorials/pt/google-pay-beta.md b/docs/tutorials/pt/google-pay-beta.md
index d263d0927..e8ea60c05 100644
--- a/docs/tutorials/pt/google-pay-beta.md
+++ b/docs/tutorials/pt/google-pay-beta.md
@@ -23,9 +23,7 @@ O Google Pay™ é um serviço de pagamentos digitais que possibilita ao usuári
 
 Os termos de serviço da API do Google Pay se aplicam sempre que o serviço Google Pay for oferecido por um lojista. Para ler os termos, acesse [Google Pay API Terms of Service](https://payments.developers.google.com/terms/sellertos).
 
-<div class="alert alert-warning">
-<p>O Google Pay não está disponível para Checkout V5 ou versões anteriores do Checkout.</p>
-</div>
+>⚠️ O Google Pay não está disponível para Checkout V5 ou versões anteriores do Checkout.
 
 ## Ativar Google Pay
 
@@ -34,26 +32,20 @@ Para ativar o Google Pay, siga o passo a passo abaixo.
 1. No Admin VTEX, acesse **Configurações da loja > Pagamentos > Carteiras** ou digite **Carteiras **na barra de busca no topo da página.
 2. Selecione a opção **Ativar** para modificar o checkout para incluir a extensão do Google Pay.
 
-<div class="alert alert-info">
-<p>As bandeiras suportadas no Google Pay são as mesmas bandeiras configuradas nas condições de pagamento.</p>
-</div>
+>ℹ️ As bandeiras suportadas no Google Pay são as mesmas bandeiras configuradas nas condições de pagamento.
 
 Feito isso, o Google Pay estará disponível no checkout da sua loja VTEX como nova forma de pagamento. É possível que demore em torno de 10 minutos para que a configuração apareça no Checkout.
 
 ![google pay - PT](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/a8bca906bd64bf229ac9521848a7c029/image.png)
 
-<div class="alert alert-warning">
-<p>Google Pay, neste momento, não vai suportar assinatura.</p>
-</div>
+>⚠️ Google Pay, neste momento, não vai suportar assinatura.
 
 É necessário ter os seguintes requisitos para utilizar o Google Pay:
 
 * Ter pelo menos uma [condição de pagamento](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) ativa configurada para cartões de crédito ou débito com um [adquirente](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente), definindo qual adquirente irá processar o pagamento da carteira.
 * Utilizar o [Checkout VTEX](https://help.vtex.com/pt/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) na sua loja.
 
-<div class="alert alert-warning">
-  <p>Nas lojas que têm o fluxo de autenticação <a href="https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado e suportado pelo adquirente, o pagamento com o Google Pay seguirá o fluxo nativo de cartão, sendo submetido também ao 3DS. Para mais informações sobre como configurar o fluxo de autenticação, consulte <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar fluxo de autenticação 3DS 2</a>.</p>
-</div>
+>⚠️ Nas lojas que têm o fluxo de autenticação [3DS](https://help.vtex.com/pt/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) configurado e suportado pelo adquirente, o pagamento com o Google Pay seguirá o fluxo nativo de cartão, sendo submetido também ao 3DS. Para mais informações sobre como configurar o fluxo de autenticação, consulte [Configurar fluxo de autenticação 3DS 2](https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2).
 
 ## Consultar transações finalizadas com o Google Pay
 
@@ -71,9 +63,7 @@ Para adicionar a informação que o pedido foi realizado com um cartão advindo
 
 Com isso, após qualquer menção aos últimos quatro dígitos do cartão desses templates de email, será adicionada a informação "(Google Pay)" caso o pagamento tenha sido feito com a carteira.
 
-<div class="alert alert-info">
-<p>Para lojas provisionadas a partir de Março de 2023, os templates já estarão atualizados com a informação do pagamento do pedido feito com o Google Pay.</p>
-</div>
+>ℹ️ Para lojas provisionadas a partir de Março de 2023, os templates já estarão atualizados com a informação do pagamento do pedido feito com o Google Pay.
 
 ## FAQ
 
diff --git a/docs/tutorials/pt/hiring-the-security-certificate-sll.md b/docs/tutorials/pt/hiring-the-security-certificate-sll.md
index 07e36d297..9127cf044 100644
--- a/docs/tutorials/pt/hiring-the-security-certificate-sll.md
+++ b/docs/tutorials/pt/hiring-the-security-certificate-sll.md
@@ -23,7 +23,5 @@ Sempre que você acessa uma página segura, isto é, protegida por um certificad
 
 Não é mais necessário solicitar a compra do certificado SSL (antes fornecido pela Digicert). O certificado agora é emitido via Let’s Encrypt e sua criação passou a ser responsabilidade da VTEX, a qual é feita [momento do _GoLive_ da loja](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-Note que a VTEX gera um certificado SSL para a sua loja e garante sua renovação automática. Por isso, não recomendamos a instalação de outros certificados. No entanto, caso seja necessário instalar outro certificado, faça a solicitação com nosso [suporte](https://help.vtex.com/pt/support).
-</div>
+>⚠️ Note que a VTEX gera um certificado SSL para a sua loja e garante sua renovação automática. Por isso, não recomendamos a instalação de outros certificados. No entanto, caso seja necessário instalar outro certificado, faça a solicitação com nosso [suporte](https://help.vtex.com/pt/support).
 
diff --git a/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md b/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
index 2261d96f3..f24e18b55 100644
--- a/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
+++ b/docs/tutorials/pt/how-can-i-change-the-domain-of-my-store.md
@@ -17,7 +17,7 @@ subcategory: yMp6sKDiJEi66CGAIQ4ma
 
 A mudança de domínio consiste na mudança do nome do site. Ou seja, se alguma loja VTEX, por exemplo, possui o domínio **_minhaloja.com_** e deseja mudar para **_nossaloja.com_**, deve seguir esse tutorial.
 
-<div class="alert alert-warning"> Indicamos a NÃO exclusão de HOST previamente configurados, enquanto a nova configuração não estiver propagada (Tempo médio de propagação: 15 minutos ).</div>
+>⚠️ Indicamos a NÃO exclusão de HOST previamente configurados, enquanto a nova configuração não estiver propagada (Tempo médio de propagação: 15 minutos ).
 
 A plataforma VTEX é preparada para suportar mudanças de domínios sem impactos negativos. Para isso, basta seguir o passo a passo abaixo:
 
diff --git a/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md b/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
index 8d02dc86d..919c1f400 100644
--- a/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
+++ b/docs/tutorials/pt/how-can-i-create-a-field-in-master-data.md
@@ -43,7 +43,7 @@ Confira o passo a passo:
 12. Clique no botão vermelho __Ok.__
 13. Clique no botão cinza __Ok.__
 
-<div class="alert alert-info">Mais informações sobre <strong>Configurações gerais</strong> e <strong>Configurações de busca e de filtro</strong> podem ser encontradas na sessão <strong>Como configurar</strong> do artigo <a href="https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar">Criar entidade de dados</a>.</div>
+>ℹ️ Mais informações sobre **Configurações gerais** e **Configurações de busca e de filtro** podem ser encontradas na sessão **Como configurar** do artigo [Criar entidade de dados](https://help.vtex.com/pt/tutorial/criando-entidade-de-dados--tutorials_1265#como-configurar).
 
 ![criar campo master data ds](https://images.ctfassets.net/alneenqid6w5/5cWru1fi0SyEAOoEbgShOI/95cabcfa4a60032d87c3294773ba4fd0/criar_campo_master_data_ds.gif)
 
diff --git a/docs/tutorials/pt/how-can-i-create-callcenter-user.md b/docs/tutorials/pt/how-can-i-create-callcenter-user.md
index ea7e9fcdc..609c45c51 100644
--- a/docs/tutorials/pt/how-can-i-create-callcenter-user.md
+++ b/docs/tutorials/pt/how-can-i-create-callcenter-user.md
@@ -43,7 +43,5 @@ Para criar um usuário com perfil de televendas, siga os seguintes passos:
 
 ![GIF animado mostrando como criar usuário televendas](https://images.ctfassets.net/alneenqid6w5/3oF5zuTnHu0Db8EQ2KdPCY/575304556410712f649e94cda1b3bdce/Adicionar_perfil.gif)
 
-<div class="alert alert-warning">
-  Ao criar um <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil</a>, evite incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
-</div>
+>⚠️ Ao criar um [perfil](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#), evite incluir [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
 
diff --git a/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md b/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md
index 25ff45b4e..a5f8ebd89 100644
--- a/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md
+++ b/docs/tutorials/pt/how-can-i-create-cluster-of-customers.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Clusterização de clientes é o mesmo que segmentação de clientes. Essas duas abordagens servem para dar ao lojista uma maior identificação de qual é o perfil do cliente, para obter mais assertividade nas atividades relacionadas a esse usuário.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 Esse dado, quando adquirido, é muito válido para o marketing e a publicidade da empresa. Cada loja pode definir quais serão seus clusters e quais serão as regras para que um cliente entre em cada um deles.
 
diff --git a/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md b/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md
index eced16281..1bae9a7bd 100644
--- a/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md
+++ b/docs/tutorials/pt/how-can-i-export-from-the-newsletter-database-using-master-data.md
@@ -26,6 +26,4 @@ Para exportar sua base de clientes que optaram por receber newsletter, siga o pa
 
    Na planilha que terá sido enviada para o seu e-mail haverá uma coluna entitulada `isNewsletterOptIn`, que atribui o valor **true** para os clientes que recebem newsletter e **false** para os que não recebem.
 
-<div class="alert alert-warning">
-  <p>Essa opção somente é válida para lojas que têm cadastro de newsletter pelo Master Data. Caso sua loja ainda não possua essa configuração e ela ainda seja feita pelo controle de página, leia o artigo <a href="https://help.vtex.com/pt/tutorial/como-configuro-a-captacao-de-newsletter-pelo-master-data--frequentlyAskedQuestions_1816">Configurar a captação de newsletter pelo Master Data</a> para saber como configurar.</p>
-</div>
+>⚠️ Essa opção somente é válida para lojas que têm cadastro de newsletter pelo Master Data. Caso sua loja ainda não possua essa configuração e ela ainda seja feita pelo controle de página, leia o artigo [Configurar a captação de newsletter pelo Master Data](https://help.vtex.com/pt/tutorial/como-configuro-a-captacao-de-newsletter-pelo-master-data--frequentlyAskedQuestions_1816) para saber como configurar.
diff --git a/docs/tutorials/pt/how-change-order-works-beta.md b/docs/tutorials/pt/how-change-order-works-beta.md
index 4fb5057d4..41690909b 100644
--- a/docs/tutorials/pt/how-change-order-works-beta.md
+++ b/docs/tutorials/pt/how-change-order-works-beta.md
@@ -15,9 +15,7 @@ legacySlug: como-funciona-a-alterar-pedido-beta
 subcategory: 3LQ1Tl0u4frEOd45BkjFAm
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a <b>Alterar pedido (Beta)</b>, entre em contato com <a href="https://help.vtex.com/pt/support">nosso Suporte</a> e informe o(s) <a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> nos quais deseja ativá-la.
-</div>
+>ℹ️ Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a **Alterar pedido (Beta)**, entre em contato com [nosso Suporte](https://help.vtex.com/pt/support) e informe o(s) [account name(s)](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) nos quais deseja ativá-la.
 
 A funcionalidade **Alterar pedido (beta)** permite que você mude um pedido de diversas maneiras, seja a mudança motivada pela vontade do cliente, pela indisponibilidade de produtos ou outros motivos. Os principais tipos de alteração de pedidos são: 
 
diff --git a/docs/tutorials/pt/how-cnova-via-varejo-integration-works.md b/docs/tutorials/pt/how-cnova-via-varejo-integration-works.md
index d67e8e126..39cb073c9 100644
--- a/docs/tutorials/pt/how-cnova-via-varejo-integration-works.md
+++ b/docs/tutorials/pt/how-cnova-via-varejo-integration-works.md
@@ -82,11 +82,11 @@ _`Ex1:` promoção de 10% de desconto para determinada categoria_
 
 _`Ex2:` SKU X está R$ 10,00 na política comercial usada na CNova/Via Varejo e tem um preço fixo de R$ 15,00 para essa mesma política. A integração enviará R$ 15,00._
 
-<div class="alert alert-warning">
-OBS: como a forma de pagamento é feita no marketplace, as regras de pagamento são determinadas por ele. Por conta disto, não conseguimos enviar preços diferenciados em função da forma de pagamento.
-<br />
-<em>Ex: se na VTEX existem juros configurados para pagamentos parcelados, o preço enviado continuará sendo o que a simulação de fulfillment retorna.</em>
-</div>
+>⚠️ OBS: como a forma de pagamento é feita no marketplace, as regras de pagamento são determinadas por ele. Por conta disto, não conseguimos enviar preços diferenciados em função da forma de pagamento.
+>
+>
+> 
+> *Ex: se na VTEX existem juros configurados para pagamentos parcelados, o preço enviado continuará sendo o que a simulação de fulfillment retorna.*
 
 ## 4. Promoções
 
@@ -111,15 +111,19 @@ Quando um pedido é feito no marketplace existem alguns pontos que influenciam e
 
 Nesta integração existem dois pontos que influenciarão na entrega: __Cálculo do Frete__ e o __Tempo de Preparo de Envio__. O somatório dos dois será o __Tempo de Entrega Total__.
 
-<div class="alert alert-info">
-Ex:
-<br />
-Frete Normal = 3 dias
-<br />
-Tempo de Custo = 2 dias
-<br />
-Tempo Total de Entrega = 5 dias
-</div>
+>ℹ️ Ex:
+>
+>
+> 
+> Frete Normal = 3 dias
+>
+>
+> 
+> Tempo de Custo = 2 dias
+>
+>
+> 
+> Tempo Total de Entrega = 5 dias
 
 - __Frete__
 
@@ -131,46 +135,78 @@ O lojista tem também a possibilidade de cadastrar na CNova/Via Varejo uma __tab
 
 O tempo de preparo de envio é baseado no somatório do  campo `Tempo de custo` no Estoque com o `Tempo de Custo` na Doca. E nós enviamos o mesmo tempo de preparo massivamente para todos os produtos.
 
-<div class="alert alert-info">
-Ex:
-<br />
-<strong>Estoque A</strong>
-<br />
-- Doca 1: Tempo de Custo = 3 dias
-<br />
-<strong>Estoque B</strong>
-<br />
-- Doca 1: Tempo de Custo = 5 dias
-<br />
-<br />
-<strong>Doca 1:</strong>
-<br />
-- Tempo de Custo = 2 dias
-<br />
-<br />
-Um pedido com Tempo de Frete = 3 dias, ficará com um Tempo Total de Entrega diferente dependendo de onde o produto sairá.
-<br />
-<br />
-<strong>Saindo do estoque A:</strong>
-<br />
-- Tempo de preparo = 3 + 2 (doca 1) = 5 dias
-<br />
-- Tempo de frete = 3 dias
-<br />
-- Tempo total de entrega = 8 dias
-<br />
-<strong>Saindo do estoque B:</strong>
-<br />
-- Tempo de preparo = 5 + 2 (doca 1) = 7 dias
-<br />
-- Tempo de frete = 3 dias
-<br />
-- Tempo total de entrega = 10 dias
-</div>
-
-<div class="alert alert-warning">
-OBS: no caso de usar a tabela de contingência para fazer o cálculo do frete, a CNova não consulta a VTEX. Desta forma, o único fator que será levado em consideração para o <strong>Tempo Total de Entrega</strong>, será o <strong>Frete</strong> fornecido por eles, ignorando o <strong>Tempo de Preparo</strong>. Deve-se tomar cuidado com isto, pois pode gerar divergências no <strong>Tempo Total de Entrega</strong>.
-</div>
+>ℹ️ Ex:
+>
+>
+> 
+> **Estoque A**
+>
+>
+> 
+> - Doca 1: Tempo de Custo = 3 dias
+>
+>
+> 
+> **Estoque B**
+>
+>
+> 
+> - Doca 1: Tempo de Custo = 5 dias
+>
+>
+> 
+>
+>
+> 
+> **Doca 1:**
+>
+>
+> 
+> - Tempo de Custo = 2 dias
+>
+>
+> 
+>
+>
+> 
+> Um pedido com Tempo de Frete = 3 dias, ficará com um Tempo Total de Entrega diferente dependendo de onde o produto sairá.
+>
+>
+> 
+>
+>
+> 
+> **Saindo do estoque A:**
+>
+>
+> 
+> - Tempo de preparo = 3 + 2 (doca 1) = 5 dias
+>
+>
+> 
+> - Tempo de frete = 3 dias
+>
+>
+> 
+> - Tempo total de entrega = 8 dias
+>
+>
+> 
+> **Saindo do estoque B:**
+>
+>
+> 
+> - Tempo de preparo = 5 + 2 (doca 1) = 7 dias
+>
+>
+> 
+> - Tempo de frete = 3 dias
+>
+>
+> 
+> - Tempo total de entrega = 10 dias
+
+>⚠️ OBS: no caso de usar a tabela de contingência para fazer o cálculo do frete, a CNova não consulta a VTEX. Desta forma, o único fator que será levado em consideração para o **Tempo Total de Entrega**, será o **Frete** fornecido por eles, ignorando o **Tempo de Preparo**. Deve-se tomar cuidado com isto, pois pode gerar divergências no **Tempo Total de Entrega**.
 
 #### Preço e disponibilidade:
 
diff --git a/docs/tutorials/pt/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md b/docs/tutorials/pt/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
index ebe214e21..b7e582ac0 100644
--- a/docs/tutorials/pt/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
+++ b/docs/tutorials/pt/how-do-i-configure-the-inclusion-of-newsletter-in-master-data.md
@@ -19,9 +19,7 @@ Captação de newsletter é um formulário que pode ser inserido em qualquer pá
 
 Esse artigo tem com objetivo auxiliar na configuração para a captação dos e-mails de clientes interessados em receber newsletter pelo Master Data.
 
-<div class="alert alert-warning">
-O controle vtex.cmc:newsletterOptIn está descontinuado e não deve mais ser usado.
-</div>
+>⚠️ O controle vtex.cmc:newsletterOptIn está descontinuado e não deve mais ser usado.
 
 Esta opção de configuração pelo Master Data oferece a comodidade de tratar os dados de todos os clientes pelo mesmo local, visto que todos os clientes cadastrado na loja já estão no Master Data. Ou seja, é o local próprio para a manutenção e ações relacionadas aos clientes e manter todos os cadastros em um só lugar é facilitar o dia a dia.
 
diff --git a/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md b/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
index 788ebc7f7..a66a3184c 100644
--- a/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
+++ b/docs/tutorials/pt/how-do-i-use-the-https-protocol-on-my-stores-pages.md
@@ -23,11 +23,11 @@ O módulo Layout abrange a home, catálogo (busca, categorias e produtos), landi
 
 É possível alterar o protocolo em todas as pastas de uma única vez com o uso de nossa API, documentada [nesta coleção do Postman](https://developers.vtex.com/reference/change-uri-schema).
 
-<div class="alert alert-warning">
-<p><strong>Atenção:</strong> evite ter o protocolo HTTPS ativado somente em algumas páginas. Ao acessar uma página HTTPS, depois ir para uma página HTTP da mesma loja, o navegador tentará fazer a leitura dos seus recursos forçadamente em HTTPS, e isso pode gerar problemas.</p>
-<p>O adequado é ativar o HTTPS em todo o site de uma única vez.</p>
-<p>O mesmo vale para websites desktop e mobile (website filho), aonde é necessário tratar o HTTPS de ambos ao mesmo tempo.</p>
-</div>
+>⚠️ **Atenção:** evite ter o protocolo HTTPS ativado somente em algumas páginas. Ao acessar uma página HTTPS, depois ir para uma página HTTP da mesma loja, o navegador tentará fazer a leitura dos seus recursos forçadamente em HTTPS, e isso pode gerar problemas.
+>
+> O adequado é ativar o HTTPS em todo o site de uma única vez.
+>
+> O mesmo vale para websites desktop e mobile (website filho), aonde é necessário tratar o HTTPS de ambos ao mesmo tempo.
 
 1. No admin VTEX, acesse **Storefront > Layout** e abra a pasta **CMS**.
 2. Acesse **Sites and channels**.
diff --git a/docs/tutorials/pt/how-does-reservation-work.md b/docs/tutorials/pt/how-does-reservation-work.md
index 3b48b2422..9cf0aa472 100644
--- a/docs/tutorials/pt/how-does-reservation-work.md
+++ b/docs/tutorials/pt/how-does-reservation-work.md
@@ -32,9 +32,7 @@ Após ser vendido, um item passa pelos seguintes status no inventário da sua lo
 
 É possível acompanhar o status da reserva dos itens pelo Admin VTEX, [como descrito ao final deste artigo.](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#como-acompanhar-o-status-da-reserva)
 
-<div class="alert alert-warning">
-Produtos inseridos no carrinho não geram reserva ou prioridade. Um item só passa para o status de Reserva autorizada após o cliente finalizar o pedido.
-</div>
+>⚠️ Produtos inseridos no carrinho não geram reserva ou prioridade. Um item só passa para o status de Reserva autorizada após o cliente finalizar o pedido.
 
 ## Reserva autorizada
 
@@ -50,9 +48,7 @@ _Tempo de expiração do pagamento + tempo de reserva no estoque_
     * **cinco dias corridos:** quando o dia de expiração do pagamento for quarta, quinta ou sexta.
     * **seis dias corridos:** quando o dia de expiração do pagamento for sábado.
 
-<div class="alert alert-danger">
-Pedidos incompletos têm o tempo fixo de reserva de 11 dias corridos. Para saber mais, confira o artigo <a href="https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos">Como funcionam os pedidos incompletos</a>. 
-</div>
+>❗ Pedidos incompletos têm o tempo fixo de reserva de 11 dias corridos. Para saber mais, confira o artigo [Como funcionam os pedidos incompletos](https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos).
 
 Para marketplace externo, se a informação do tempo da reserva for enviada pelo campo `lockTTL`, o tempo de reserva não será calculado pela plataforma VTEX, e sim determinado pelo prazo no campo. Isso é feito pela chamada [Place order](https://developers.vtex.com/docs/api-reference/checkout-api#put-/api/checkout/pub/orders).
 
@@ -86,9 +82,7 @@ O inventário de uma loja possui três unidades de um item. Um cliente faz uma c
 
 Quando o lojista ou o ERP atualizarem a quantidade desse item no inventário  retirando a quantidade vendida (atualizando com duas unidades), a plataforma atualiza a quantidade de itens disponíveis, o que pode ser interpretado como uma baixa no estoque. A plataforma, nesse caso, mantém apenas duas unidades do item no inventário e nenhuma unidade reservada.
 
-<div class="alert alert-danger">
-Ao confirmar o início do manuseio, o seller assume a responsabilidade da reserva dos itens do pedido. A partir desse momento, se houver qualquer atualização no inventário, a plataforma VTEX desconsidera a reserva destes SKUs. Portanto, atualize o inventário para SKUs de um dado pedido apenas quando este for faturado. Dessa forma evita-se divergência de inventário dependendo da interação com a <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integração de backoffice</a> da sua loja.
-</div>
+>❗ Ao confirmar o início do manuseio, o seller assume a responsabilidade da reserva dos itens do pedido. A partir desse momento, se houver qualquer atualização no inventário, a plataforma VTEX desconsidera a reserva destes SKUs. Portanto, atualize o inventário para SKUs de um dado pedido apenas quando este for faturado. Dessa forma evita-se divergência de inventário dependendo da interação com a [integração de backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) da sua loja.
 
 ## Como acompanhar o status da reserva
 
diff --git a/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md b/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
index 3d0b16af3..2afb20ee7 100644
--- a/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
+++ b/docs/tutorials/pt/how-does-the-cart-with-multiple-items-work-in-mercado-livre.md
@@ -33,6 +33,4 @@ Você pode encontrar os dois IDs através do relatório enviado a partir do pain
 
 ![Pedidos Mercado Livre](https://images.ctfassets.net/alneenqid6w5/2NFqrrWGlqQMYSOugYo8kQ/deba1c9f1ffb01e0db3f2874fb7ee8a3/Pedidos_Mercado_Livre.png)
 
-<div class="alert alert-warning">
-Essa lógica de funcionamento se aplica a todos os tipos de entrega, com exceção daqueles que incluem pickup points. Nesses casos, a plataforma continua a utilizar o ID antigo.
-</div>
+>⚠️ Essa lógica de funcionamento se aplica a todos os tipos de entrega, com exceção daqueles que incluem pickup points. Nesses casos, a plataforma continua a utilizar o ID antigo.
diff --git a/docs/tutorials/pt/how-does-vtex-search-work.md b/docs/tutorials/pt/how-does-vtex-search-work.md
index ca117f444..de625d704 100644
--- a/docs/tutorials/pt/how-does-vtex-search-work.md
+++ b/docs/tutorials/pt/how-does-vtex-search-work.md
@@ -37,9 +37,7 @@ De acordo com o termo buscado, o sistema pode renderizar os resultados abaixo,
 
 Se o termo buscado corresponder exatamente ao nome de uma pasta configurada no CMS (ou seja, a uma landing page), essa pasta será renderizada.
 
-<div class="alert alert-warning">
-  <p>Para uma pasta ser buscável ela deve possuir um layout. Mesmo que a pesquisa seja por uma pasta filha, a pai também requer um layout.</p>
-</div>
+>⚠️ Para uma pasta ser buscável ela deve possuir um layout. Mesmo que a pesquisa seja por uma pasta filha, a pai também requer um layout.
 
 ### 2. Marca
 
diff --git a/docs/tutorials/pt/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md b/docs/tutorials/pt/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
index a538af290..1bd6ae308 100644
--- a/docs/tutorials/pt/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
+++ b/docs/tutorials/pt/how-is-shipping-cost-calculated-when-theres-an-item-with-shipping-benefit-on-the-cart.md
@@ -25,11 +25,11 @@ Quando há mais de um item no carrinho, o custo do envio dividido por cada item
 
 Vamos analisar como seria feito o cálculo da divisão do custo de envio num carrinho com 5 itens, com custo total de envio de 200 unidades monetárias:
 
-<div class="alert alert-info">
-Para descobrir o custo de envio de um carrinho, faça uma <a href="http://help.vtex.com/pt/tutorial/simulacao-de-frete/">simulação de frete</a>.
-<br>
-Para saber o peso de um SKU, acesse o cadastro do SKU na página <strong>Produtos e SKUs</strong> no menu <strong>Catálogo</strong> e busque por <strong>Peso para Frete</strong>.
-</div>
+>ℹ️ Para descobrir o custo de envio de um carrinho, faça uma [simulação de frete](http://help.vtex.com/pt/tutorial/simulacao-de-frete/).
+>
+>
+> 
+> Para saber o peso de um SKU, acesse o cadastro do SKU na página **Produtos e SKUs** no menu **Catálogo** e busque por **Peso para Frete**.
 
 - __Custo Total de Envio:__ 200
 - __Peso do Produto A:__ 20
diff --git a/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md b/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md
index dd2a02723..7ac3a9983 100644
--- a/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md
+++ b/docs/tutorials/pt/how-is-the-platforms-operation-sla-determined.md
@@ -22,9 +22,7 @@ Para apurar violações do SLA, ou seja, contabilizar tempo de indisponibilidade
 - Interrupções na loja virtual que estejam impactando significativamente o número de pedidos realizados, por exemplo: loja fora do ar, lentidão no acesso, erro no checkout.
 - Interrupções com duração de no mínimo 10 minutos.
 
-<div class="alert alert-warning">
-  <p>Não contabilizamos manutenções agendadas como tempo de indisponibilidade.</p>
-</div>
+>⚠️ Não contabilizamos manutenções agendadas como tempo de indisponibilidade.
 
 ## Verificar o status da VTEX
 
diff --git a/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md b/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
index 13d0eb543..92730300c 100644
--- a/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
+++ b/docs/tutorials/pt/how-long-does-it-take-to-cancel-an-order-with-an-unpaid-boleto.md
@@ -32,9 +32,7 @@ Alguns provedores de pagamento permitem que a validade de um boleto seja configu
 3. Na tela de configuração do provedor, verifique se existe algum campo disponível para configurar a validade do boleto e preencha com o valor desejado (em dias) .
 4. Clique em `Salvar`.
 
-<div class="alert alert-warning">
-Caso o seu provedor de pagamento não permita modificar a validade de boleto no Admin VTEX, é necessário entrar em contato com o suporte técnico do provedor e verificar os procedimentos necessários para a configuração de validade do boleto.
-</div>
+>⚠️ Caso o seu provedor de pagamento não permita modificar a validade de boleto no Admin VTEX, é necessário entrar em contato com o suporte técnico do provedor e verificar os procedimentos necessários para a configuração de validade do boleto.
 
 ## Prazo para cancelamento da reserva dos produtos
 
diff --git a/docs/tutorials/pt/how-long-does-the-platform-take-to-identify-my-payment.md b/docs/tutorials/pt/how-long-does-the-platform-take-to-identify-my-payment.md
index 7493229db..b025c8b4d 100644
--- a/docs/tutorials/pt/how-long-does-the-platform-take-to-identify-my-payment.md
+++ b/docs/tutorials/pt/how-long-does-the-platform-take-to-identify-my-payment.md
@@ -17,9 +17,7 @@ subcategory: 6SJnrkKDjGwSqKkMuQMOmm
 
 Se você pagou por boleto bancário, a compensação deverá ocorrer em até 48 horas úteis após o pagamento. Mas fique tranquilo, geralmente a compensação acontece antes deste prazo e a liberação do seu ambiente é feita automaticamente após a confirmação do pagamento.
 
-<div class="alert alert-warning">
-Caso o título não seja atualizado em 48 horas, abra um chamado, via ticket, e envie a comprovação de pagamento para que possamos entender o ocorrido.
-</div>
+>⚠️ Caso o título não seja atualizado em 48 horas, abra um chamado, via ticket, e envie a comprovação de pagamento para que possamos entender o ocorrido.
 
 ### Artigos relacionados
 
diff --git a/docs/tutorials/pt/how-my-account-works.md b/docs/tutorials/pt/how-my-account-works.md
index ec841830f..54763a2ab 100644
--- a/docs/tutorials/pt/how-my-account-works.md
+++ b/docs/tutorials/pt/how-my-account-works.md
@@ -177,9 +177,7 @@ Para mudar a senha atual:
 4. Clique no botão `SALVAR SENHA` para concluir a mudança de senha.  
 ![My Authentication change password PT](https://images.ctfassets.net/alneenqid6w5/7qyiWDAjdSBEjppq6Ti94c/94f7323e8d97d28a4d5dac042c5c620b/My_Authentication_change_password_PT.png)
 
-<div class="alert alert-info">
-Caso você tenha esquecido a senha, não é possível recuperá-la pelo componente de gerenciamento de senha. Para isso você deve sair da sessão atual, fazer uma tentativa de login usando email e senha, e clicar no link <strong>Esqueci minha senha</strong>.
-</div>
+>ℹ️ Caso você tenha esquecido a senha, não é possível recuperá-la pelo componente de gerenciamento de senha. Para isso você deve sair da sessão atual, fazer uma tentativa de login usando email e senha, e clicar no link **Esqueci minha senha**.
 
 ### Gerenciamento de sessões
 
diff --git a/docs/tutorials/pt/how-order-authorization-workss.md b/docs/tutorials/pt/how-order-authorization-workss.md
index c56b6df26..9b5a749b2 100644
--- a/docs/tutorials/pt/how-order-authorization-workss.md
+++ b/docs/tutorials/pt/how-order-authorization-workss.md
@@ -57,9 +57,7 @@ Ao ser notificado, o usuário deverá:
 
 Os demais pedidos, classificados nas faixas de variação de preço cujas regras não pedem aprovação por usuário, serão aprovados ou negados pelo sistema automaticamente. 
 
-<div class="alert alert-info">
-É possível configurar uma hierarquia de usuários para aprovações de pedidos, isso é, para aprovações em cadeia. Para isso, basta inserir mais de um e-mail em Pessoas autorizadas e escolher a ordenação desejada dos usuários cadastrados.  
-</div>
+>ℹ️ É possível configurar uma hierarquia de usuários para aprovações de pedidos, isso é, para aprovações em cadeia. Para isso, basta inserir mais de um e-mail em Pessoas autorizadas e escolher a ordenação desejada dos usuários cadastrados.
 
 
 
diff --git a/docs/tutorials/pt/how-product-name-control-works.md b/docs/tutorials/pt/how-product-name-control-works.md
index 4d4ebe034..27b8a6259 100644
--- a/docs/tutorials/pt/how-product-name-control-works.md
+++ b/docs/tutorials/pt/how-product-name-control-works.md
@@ -19,9 +19,7 @@ O controle `<vtex.cmc:productName/>` renderiza o nome do produto conforme cadast
 
 Portanto, ele funciona __apenas em páginas de produto__.
 
-<div class="alert alert-info">
-O nome que esse controle imprime é o do <b>produto</b>, não do SKU.
-</div>
+>ℹ️ O nome que esse controle imprime é o do **produto**, não do SKU.
 
 Este é um exemplo do código HTML renderizado pelo controle Product Name.
 
diff --git a/docs/tutorials/pt/how-promotion-competition-works.md b/docs/tutorials/pt/how-promotion-competition-works.md
index 4fe353306..a1ba8ed02 100644
--- a/docs/tutorials/pt/how-promotion-competition-works.md
+++ b/docs/tutorials/pt/how-promotion-competition-works.md
@@ -84,8 +84,7 @@ Logo, a sequência de aplicação é:
 
 ![promocao3 PT](https://images.ctfassets.net/alneenqid6w5/1LKDzbLkhua8Gk284SEwsk/997fdac9b6380c68a729bf4d48e20af8/promocao3_PT.png)
 
-<div class="alert alert-warning">
-Pedidos de origem <a href="https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> e Fulfillment não reconhecem acúmulo de promoção, uma vez que o uso de promoções em Marketplaces VTEX ou externos é restrito a alguns tipos específicos.</div>
+>⚠️ Pedidos de origem [Marketplace](https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406) e Fulfillment não reconhecem acúmulo de promoção, uma vez que o uso de promoções em Marketplaces VTEX ou externos é restrito a alguns tipos específicos.
 
 ## Estratégias de concorrência de promoções
 
@@ -100,8 +99,7 @@ Veja a seguir as duas estratégias de concorrência de promoções:
 - [Concorrência por cenário](#concorrencia-por-cenario)
 - [Concorrência por item](#concorrencia-por-item)
 
-<div class="alert alert-info">
-Por padrão, todas as contas seguem a estratégia de concorrência por cenário. Caso o modelo de concorrência por item atenda melhor suas necessidades de negócio, <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abra um chamado com nosso time de suporte</a> e solicite a mudança.</div>
+>ℹ️ Por padrão, todas as contas seguem a estratégia de concorrência por cenário. Caso o modelo de concorrência por item atenda melhor suas necessidades de negócio, [abra um chamado com nosso time de suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) e solicite a mudança.
 
 ### Concorrência por cenário
 
diff --git a/docs/tutorials/pt/how-proportional-shipping-costs-are-calculated.md b/docs/tutorials/pt/how-proportional-shipping-costs-are-calculated.md
index a79b668e0..f4218ccd1 100644
--- a/docs/tutorials/pt/how-proportional-shipping-costs-are-calculated.md
+++ b/docs/tutorials/pt/how-proportional-shipping-costs-are-calculated.md
@@ -29,9 +29,7 @@ Por exemplo, em um carrinho o frete foi calculado no valor de $25,00 para cinco
 
 Para fins de usabilidade de termos, utilizamos em nossa documentação o termo "peso" ao invés de "massa". Mesmo conhecendo a diferença entre os termos e a forma correta de uso, mantemos o uso de "peso" para melhor compreensão dos usuários.
 
-<div class="alert alert-danger">
-O peso do produto não pode ser zero. Isso pode causar problemas no cálculo do custo de frete no carrinho.
-</div>
+>❗ O peso do produto não pode ser zero. Isso pode causar problemas no cálculo do custo de frete no carrinho.
 
 ## Como visualizar o rateio do frete
 
diff --git a/docs/tutorials/pt/how-shipping-calculation-works.md b/docs/tutorials/pt/how-shipping-calculation-works.md
index a6600435e..5ab2d1d27 100644
--- a/docs/tutorials/pt/how-shipping-calculation-works.md
+++ b/docs/tutorials/pt/how-shipping-calculation-works.md
@@ -46,14 +46,13 @@ A seleção de combinações logísticas acontece de acordo com os seguintes cri
   <li><b>Disponibilidade do inventário:</b> estoque é o local físico de armazenamento de itens, enquanto <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">inventário</a> é a relação dos SKUs dos estoques disponíveis para venda. Este critério valida se os itens do pedido estão disponíveis em um estoque, e se esse estoque tem pelo menos uma doca disponível.</li>
 </ul>
 <br>
-  <div class="alert alert-warning">
-Para o caso de se tratar do envio de um <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28">kit</a>, existem duas condições:
-  <ul>
-    <li>Os componentes do kit devem possuir a mesma <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">doca</a>.</li>
-    <li>Deve haver disponibilidade de componentes do kit no <a href="https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/2XyUVa0UKMyHTmwqyA5Bx6">inventário</a>.</li>
-  </ul>
-Para mais informações, veja o artigo <a href="https://help.vtex.com/pt/tutorial/como-e-calculado-o-frete-do-kit--frequentlyAskedQuestions_154">Como é calculado o frete do kit</a>.
-</div>
+  >⚠️ Para o caso de se tratar do envio de um [kit](https://help.vtex.com/pt/tutorial/o-que-e-um-kit--5ov5s3eHM4AqAAgqWwoc28), existem duas condições:
+>
+> * Os componentes do kit devem possuir a mesma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
+>
+> * Deve haver disponibilidade de componentes do kit no [inventário](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/2XyUVa0UKMyHTmwqyA5Bx6).
+>
+> Para mais informações, veja o artigo [Como é calculado o frete do kit](https://help.vtex.com/pt/tutorial/como-e-calculado-o-frete-do-kit--frequentlyAskedQuestions_154).
 
 2. **Priorização de inventário:** as rotas logísticas selecionadas anteriormente são organizadas tendo o [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) como critério de priorização. Quanto menor a quantidade de SKUs do pedido em estoque, maior é a prioridade da rota logística na seleção, de forma que inventários com pequenas quantidades de itens não fiquem represados. A partir disso, é composta uma lista ordenada de rotas logísticas, que vai do item mais prioritário em primeiro lugar, até o menos prioritário em último lugar.
 3. **Agrupamento de pacotes:** a plataforma VTEX calcula a separação dos itens do pedido em pacotes, de forma a estimar as divisões de pacotes e [remessas](https://help.vtex.com/pt/tutorial/como-funciona-a-remessa--tutorials_118).
diff --git a/docs/tutorials/pt/how-the-carrefour-integration-works.md b/docs/tutorials/pt/how-the-carrefour-integration-works.md
index 4b2cd9395..68061a275 100644
--- a/docs/tutorials/pt/how-the-carrefour-integration-works.md
+++ b/docs/tutorials/pt/how-the-carrefour-integration-works.md
@@ -47,14 +47,12 @@ Para os produtos serem exibidos no Carrefour, a integração envia os seguintes
 _Legenda:_
 `*` Campos obrigatórios.<br /> 
 
-<div class="alert alert-warning">O Carrefour não aceita produtos com variação (mais de um SKU).</div>
+>⚠️ O Carrefour não aceita produtos com variação (mais de um SKU).
 
 ### Exibição do produto
 Uma vez que os lotes de produto e oferta são enviados com sucesso e validados pelo Carrefour, todas as variações/SKUs de um mesmo produto são exibidas juntas, em um mesmo agrupamento.
 
-<div class="alert alert-info">
-Ex: Camisa Azul (produto) | P, M, G (variações/skus)
-</div>
+>ℹ️ Ex: Camisa Azul (produto) | P, M, G (variações/skus)
 
 ### Status do produto
 Com todos os produtos processados corretamente e catalogados pelo Carrefour, suas ofertas podem ter os seguintes status:
@@ -67,9 +65,7 @@ Ao serem enviados com sucesso pela primeira vez, os produtos passam por um proce
 
 Por exemplo, se a descrição do produto for alterada, a integração não vai atualizá-la no marketplace. Para fazer algum tipo de alteração, você vai precisar entrar em contato direto com o Carrefour.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> o produto não pode ser apagado no painel do Carrefour. Se isso acontecer, a integração não vai conseguir enviá-lo novamente.
-</div>
+>⚠️ **OBS:** o produto não pode ser apagado no painel do Carrefour. Se isso acontecer, a integração não vai conseguir enviá-lo novamente.
 
 ## 2. Estoque
 Quando um produto é enviado pela primeira vez, o estoque também é enviado. No entanto, ele é descartado pelo Carrefour, pois eles só aceitam receber os estoques para produtos já catalogados. Essa política existe para que o estoque disponível no marketplace seja sempre o mais atualizado.
@@ -85,9 +81,7 @@ Porém, o Carrefour não notifica a VTEX quando tudo foi aprovado. Isso signific
 
 Depois que os produtos recebem a primeira carga de preço, a atualização é feita SKU por SKU sempre que os preços na VTEX sofrem alguma mudança. Essa atualização é mandada em lotes de 6 em 6 minutos. Isso significa que a integração acumula todas as atualizações da sua loja por 6 minutos e mandar tudo de uma vez. Caso a atualização de preços esteja demorando mais do que o esperado, é provável que haja muitas informações na fila para serem atualizadas.
 
-<div class="alert alert-warning">
-Note que, para preços com validade, o sistema não notifica os afiliados quando a data expira. Assim, o preço base só será enviado na próxima modificação de preços. 
-</div>
+>⚠️ Note que, para preços com validade, o sistema não notifica os afiliados quando a data expira. Assim, o preço base só será enviado na próxima modificação de preços.
 
 Para cada SKU, a integração envia apenas o preço final, baseado no retorno da simulação de fulfillment. Em um cenário padrão, o preço enviado vai ser sempre o determinado para a política comercial associada à integração. Porém, existem fatores que podem influenciar no preço final, como promoções e preços fixos.
 
@@ -95,11 +89,11 @@ _`Exemplo 1:` uma promoção que oferece 10% de desconto para uma determinada ca
 
 _`Exemplo 2:` na política comercial usada no Carrefour, um SKU tem preço de R$ 10 e um preço fixo de R$ 15. O valor que a integração envia para o marketplace é R$ 15._
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> como a forma de pagamento é dada no marketplace, as regras de pagamento também são determinadas por ele. Por causa disso, a integração não consegue enviar preços diferenciados de acordo com a forma de pagamento.
-<br />
-<em>Ex: se na VTEX estiver configurada a incidência de juros para pagamentos parcelados, o preço enviado vai continuar sendo o que foi retornado pela simulação de fulfillment.</em>
-</div>
+>⚠️ **Atenção:** como a forma de pagamento é dada no marketplace, as regras de pagamento também são determinadas por ele. Por causa disso, a integração não consegue enviar preços diferenciados de acordo com a forma de pagamento.
+>
+>
+> 
+> *Ex: se na VTEX estiver configurada a incidência de juros para pagamentos parcelados, o preço enviado vai continuar sendo o que foi retornado pela simulação de fulfillment.*
 
 ## 4. Promoções
 Diferente de uma promoção usada para o site da sua loja, uma promoção para marketplace apenas desconta o valor do produto, mas sem indicar que é uma promoção. Ou seja, o preço enviado já está modificado e não há um selo de promoção.
@@ -122,9 +116,7 @@ Os detalhes do pedido são influenciados diretamente por fatores como entrega, p
 #### Frete
 O Carrefour consulta, no momento do pedido, a tabela de frete cadastrada na VTEX. Nossa plataforma retorna para eles as opções de frete disponíveis, de acordo com o mapeamento preenchido na configuração da integração. É importante ter em mente que a consulta só é possível se a [API de Frete](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-carrefour--2wYlj07cNuA8k8mmwY86K2/6FacWWJszKw0Um42uYcQai) for cadastrada no painel do Carrefour.
 
-<div class="alert alert-warning">
-OBS: caso nenhum dos campos do mapeamento seja preenchido corretamente, não será possível simular o frete na VTEX. Consequentemente, os pedidos feitos no Carrefour não serão integrados.
-</div>
+>⚠️ OBS: caso nenhum dos campos do mapeamento seja preenchido corretamente, não será possível simular o frete na VTEX. Consequentemente, os pedidos feitos no Carrefour não serão integrados.
 
 Se a API de Frete não for cadastrada, o Carrefour vai usar uma __tabela de contingência__ para fazer o cálculo. Nesse caso, o Carrefour envia as informações do pedido e a integração tenta fazer um _match_ do frete calculado com a transportadora que mais se adequa dentro da VTEX (usamos o __tipo__ de transportadora como parâmetro). Caso não haja uma correspondência, haverá um erro na integração do pedido. Para solucionar isso, você precisará fazer primeiro o mapeamento de frete e, depois, reprocessar o pedido.
 
@@ -149,9 +141,7 @@ Durante o processo, pode ser que o pedido não seja integrado por algum motivo.
 
 Depois que a integração acontece, os pedidos continuam sendo tratados com o mesmo ID usado no Carrefour.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> pedidos com algum tipo de incidente não são integrados. Caso o incidente ocorra depois da integração do pedido, um aviso vai ser exibido na aba de Rastreamento no Admin da VTEX.
-</div>
+>⚠️ **OBS:** pedidos com algum tipo de incidente não são integrados. Caso o incidente ocorra depois da integração do pedido, um aviso vai ser exibido na aba de Rastreamento no Admin da VTEX.
 
 ### 5.3 Interação do pedido
 Depois que o pedido foi integrado com sucesso, você pode interagir com ele tanto pelo Admin da VTEX quanto pelo painel de administrador do Carrefour. No entanto, algumas ações podem ou não ser aplicadas nos dois lados.
diff --git a/docs/tutorials/pt/how-the-integration-with-buscape-works.md b/docs/tutorials/pt/how-the-integration-with-buscape-works.md
index e5903f37f..70497a278 100644
--- a/docs/tutorials/pt/how-the-integration-with-buscape-works.md
+++ b/docs/tutorials/pt/how-the-integration-with-buscape-works.md
@@ -53,23 +53,27 @@ Se o envio for realizado com sucesso, você já poderá encontrar os produtos no
 
 Caso o mapeamento tenha sido feito corretamente, todas as variações serão exibidas em um único anúncio.
 
-<div class="alert alert-info">
-Ex.: 
-<br />
-<strong>Anúncio</strong> = Camisa Azul (produto) | P, M, G (variações/skus)
-</div>
+>ℹ️ Ex.: 
+>
+>
+> 
+> **Anúncio** = Camisa Azul (produto) | P, M, G (variações/skus)
 
 Se o mapeamento __não__ for feito, as diferentes variações do mesmo produto serão exibidas em anúncios separados.
 
-<div class="alert alert-info">
-Ex.: 
-<br />
-<strong>Anúncio 1</strong> = Camisa Azul P  
-<br />
-<strong>Anúncio 2</strong> = Camisa Azul M 
-<br />
-<strong>Anúncio 3</strong> = Camisa Azul G 
-</div>
+>ℹ️ Ex.: 
+>
+>
+> 
+> **Anúncio 1** = Camisa Azul P  
+>
+>
+> 
+> **Anúncio 2** = Camisa Azul M 
+>
+>
+> 
+> **Anúncio 3** = Camisa Azul G
 
 ### Atualizações de produto
 
@@ -92,9 +96,7 @@ Com tudo certo, os produtos enviados ao Buscapé podem ter os seguintes status:
 
 Os estoques são enviados pela primeira vez junto com o primeiro envio de produtos. A partir daí, os estoques dos anúncios no Buscapé são atualizados automaticamente, SKU por SKU, sempre que há alguma alteração de estoque na VTEX. A atualização demora apenas alguns segundos para refletir no marketplace, mas os logs de estoque podem demorar alguns minutos para aparecer no Admin da VTEX. 
 
-<div class="alert alert-info">
-Para acessar os logs, clique na seção <strong>Integrações</strong> do menu lateral do Admin. Uma lista de opções vai se abrir e, então, você deve clicar na opção <strong>Estoque</strong>. 
-</div>
+>ℹ️ Para acessar os logs, clique na seção **Integrações** do menu lateral do Admin. Uma lista de opções vai se abrir e, então, você deve clicar na opção **Estoque**.
 
 ## 3. Preço
 
@@ -104,21 +106,19 @@ No entanto, o sistema __não__ notifica os afiliados quando chega a data final d
 
 Para cada SKU, a integração envia apenas o preço final, baseado no retorno da simulação de fulfillment. Normalmente, o preço enviado é sempre o que foi determinado pela política comercial associada à integração. No entanto, __Promoções__ e __Preços fixos__ podem influenciar o preço final.
 
-<div class="alert alert-info">
-<strong>Exemplo 1:</strong>
-<br />
-Uma promoção que ofereça 10% de desconto para uma determinada categoria.
-</div>
-
-<div class="alert alert-info">
-<strong>Exemplo 2:</strong>
-<br />
-Na política comercial usada no Buscapé, um SKU tem preço de R$ 10 e um preço fixo de R$ 15. O valor que a integração envia para o marketplace é R$ 15.
-</div>
-
-<div class="alert alert-warning">
-<strong>Atenção:</strong> a integração não envia preços de acordo com a forma de pagamento. Isso significa que, mesmo se estiver configurada a incidência de juros para pagamentos parcelados, o preço enviado para o Buscapé vai continuar sendo o que foi retornado pela simulação de fulfillment.
-</div>
+>ℹ️ **Exemplo 1:**
+>
+>
+> 
+> Uma promoção que ofereça 10% de desconto para uma determinada categoria.
+
+>ℹ️ **Exemplo 2:**
+>
+>
+> 
+> Na política comercial usada no Buscapé, um SKU tem preço de R$ 10 e um preço fixo de R$ 15. O valor que a integração envia para o marketplace é R$ 15.
+
+>⚠️ **Atenção:** a integração não envia preços de acordo com a forma de pagamento. Isso significa que, mesmo se estiver configurada a incidência de juros para pagamentos parcelados, o preço enviado para o Buscapé vai continuar sendo o que foi retornado pela simulação de fulfillment.
 
 ## 4. Promoções
 
diff --git a/docs/tutorials/pt/how-the-order-replacement-works.md b/docs/tutorials/pt/how-the-order-replacement-works.md
index dcbe75487..46f2a8726 100644
--- a/docs/tutorials/pt/how-the-order-replacement-works.md
+++ b/docs/tutorials/pt/how-the-order-replacement-works.md
@@ -72,6 +72,6 @@ Ao selecionar **Alterar pedido**, o cliente é levado para uma tela onde escolhe
 
 Para concluir a alteração, ele é levado para o carrinho e o Checkout, onde pode alterar endereço, tipo de frete, forma de pagamento e SKU.
 
-<div class="alert alert-warning">É necessário fechar a compra para concluir o processo, mas <strong>o cliente nunca é cobrado duas vezes</strong>. Em alguns casos o pagamento anterior será reaproveitado; quando isso não for possível, a cobrança anterior no cartão de crédito será automaticamente estornada.</div>
+>⚠️ É necessário fechar a compra para concluir o processo, mas **o cliente nunca é cobrado duas vezes**. Em alguns casos o pagamento anterior será reaproveitado; quando isso não for possível, a cobrança anterior no cartão de crédito será automaticamente estornada.
 
 A reutilização de pagamento só pode ser usada se o valor do pedido novo for igual ao do pedido original. Além disso, se o pagamento expira em até 2 dias, ele não pode ser reutilizado.
diff --git a/docs/tutorials/pt/how-the-relationship-between-websites-and-business-policies-works.md b/docs/tutorials/pt/how-the-relationship-between-websites-and-business-policies-works.md
index 75eb82a35..14b3eb1e9 100644
--- a/docs/tutorials/pt/how-the-relationship-between-websites-and-business-policies-works.md
+++ b/docs/tutorials/pt/how-the-relationship-between-websites-and-business-policies-works.md
@@ -38,9 +38,7 @@ Para saber a ordenação das políticas comerciais, siga os passos abaixo:
 1. Em seu Admin VTEX, acesse **Configurações da loja > Canais > Políticas Comerciais**.
 2. Na coluna __Posição__, você verá a ordenação das suas políticas comerciais. A posição 1 exibe a política comercial de maior prioridade.
 
-<div class="alert alert-danger">
-Recomendamos não alterar a posição da política comercial de <strong>ID 1</strong>.
-</div>
+>❗ Recomendamos não alterar a posição da política comercial de **ID 1**.
 
 ### Exemplos
 
diff --git a/docs/tutorials/pt/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md b/docs/tutorials/pt/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
index aed4957f3..30a2b24da 100644
--- a/docs/tutorials/pt/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
+++ b/docs/tutorials/pt/how-to-add-a-second-address-to-the-order-for-invoicing-purposes.md
@@ -27,9 +27,7 @@ Vamos, então, manipular alguns dados do `orderForm` para inserir um segundo end
 - Usando a biblioteca vtex.js.
 - Por meio de um request à API de Checkout da VTEX.
 
-<div class="alert alert-warning">
-Embora seja possível criar uma interface customizada sobreposta à da VTEX, contendo o segundo campo de endereço, não recomendamos que se faça isso.
-</div>
+>⚠️ Embora seja possível criar uma interface customizada sobreposta à da VTEX, contendo o segundo campo de endereço, não recomendamos que se faça isso.
 
 ## vtex.js
 
diff --git a/docs/tutorials/pt/how-to-add-customized-information-to-the-order-and-manipulate-it.md b/docs/tutorials/pt/how-to-add-customized-information-to-the-order-and-manipulate-it.md
index 38d9e8fde..c52085176 100644
--- a/docs/tutorials/pt/how-to-add-customized-information-to-the-order-and-manipulate-it.md
+++ b/docs/tutorials/pt/how-to-add-customized-information-to-the-order-and-manipulate-it.md
@@ -32,9 +32,7 @@ Para trabalhar com esse campo, você deve usar a API do Checkout da VTEX. Três
 
 Antes de popular o campo `customData`, você precisa usar a chamada [Update orderForm configuration](https://developers.vtex.com/reference/configuration#updateorderformconfiguration) para criar uma app. Essa app vai conter os campos customizados que depois serão populados durante o checkout.
 
-<div class="alert alert-warning">
-A chamada Update orderForm configuration define configurações que se aplicam a todos os orderForms gerados na sua conta. Ou seja, a partir do momento em que você adicionar uma app por meio dela, todos os pedidos da loja conterão os campos extras definidos nessa app. Para criar uma app e seus campos, essa chamada só precisa acontecer uma vez.
-</div>
+>⚠️ A chamada Update orderForm configuration define configurações que se aplicam a todos os orderForms gerados na sua conta. Ou seja, a partir do momento em que você adicionar uma app por meio dela, todos os pedidos da loja conterão os campos extras definidos nessa app. Para criar uma app e seus campos, essa chamada só precisa acontecer uma vez.
 
 Vamos ver um exemplo de objeto `app` enviado no body do request Update orderForm configuration:
 
diff --git a/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md b/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
index 58130741e..32e9f1523 100644
--- a/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
+++ b/docs/tutorials/pt/how-to-capture-the-ip-of-an-order.md
@@ -33,14 +33,10 @@ Veja mais detalhes em: [Como visualizar detalhe do pedido](/pt/tutorial/como-vis
 
 Para obter o IP por integração, é possível consultar a API Get Order mediante o orderID.
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/orders#getorder">Ver documentação da API OMS</a>
-</div>
+>ℹ️ [Ver documentação da API OMS](https://developers.vtex.com/reference/orders#getorder)
 
 Uma vez obtido o JSON do pedido, é possível obter o `transactionId` e consultar a API **Get Transaction Details** mediante o ID da transação.
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/transaction-process#transactiondetails">Ver documentação da API Transaction</a>
-</div>
+>ℹ️ [Ver documentação da API Transaction](https://developers.vtex.com/reference/transaction-process#transactiondetails)
 
 Por fim, desta última chamada, será possível consultar o campo `ipAddress`.
diff --git a/docs/tutorials/pt/how-to-change-order-items.md b/docs/tutorials/pt/how-to-change-order-items.md
index 9dd26b8e6..bfea2469c 100644
--- a/docs/tutorials/pt/how-to-change-order-items.md
+++ b/docs/tutorials/pt/how-to-change-order-items.md
@@ -24,10 +24,8 @@ Há duas formas de realizar a alteração de um pedido:
 * [Via Admin VTEX](#como-alterar): é possível se o status do pedido estiver como `Preparando entrega`.
 * [Via API de alteração de pedidos](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes) é possível, além de alterar itens, criar descontos e mudar o preço do pedido. A alteração só é possível se o status do pedido na API de pedidos for`handling` ou `waiting-for-fulfillment`.
 
-<div class="alert alert-warning">
-Após a alteração, o cliente recebe uma notificação por email caso o template <code>Change of information</code> (<a href="https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">
-template de emails transacionais referentes ao pedido</a>) esteja habilitado na Central de Mensagens. O cliente recebe as mensagens com as informações que foram preenchidas no formulário de alteração de itens.
-</div>
+>⚠️ Após a alteração, o cliente recebe uma notificação por email caso o template `Change of information` (<a href="https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">
+> template de emails transacionais referentes ao pedido</a>) esteja habilitado na Central de Mensagens. O cliente recebe as mensagens com as informações que foram preenchidas no formulário de alteração de itens.
 
 É possível editar itens que não foram faturados ainda em um pedido. Para adicionar novos itens, retirar itens, ou mudar a quantidade de cada um, confira os passos abaixo.  
 
diff --git a/docs/tutorials/pt/how-to-change-orders-beta.md b/docs/tutorials/pt/how-to-change-orders-beta.md
index fc03dbc0b..8dc6dc899 100644
--- a/docs/tutorials/pt/how-to-change-orders-beta.md
+++ b/docs/tutorials/pt/how-to-change-orders-beta.md
@@ -15,9 +15,7 @@ legacySlug: como-alterar-pedidos-beta
 subcategory: 3LQ1Tl0u4frEOd45BkjFAm
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a <b>Alterar pedido (Beta)</b>, entre em contato com <a href="https://help.vtex.com/pt/support">nosso Suporte</a> e informe o(s) <a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name(s)</a> nos quais deseja ativá-la.
-</div>
+>ℹ️ Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a **Alterar pedido (Beta)**, entre em contato com [nosso Suporte](https://help.vtex.com/pt/support) e informe o(s) [account name(s)](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC) nos quais deseja ativá-la.
 
 A funcionalidade [Alterar pedido (beta)](https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ) permite que você edite um pedido de diversas formas, seja a mudança motivada pela vontade do cliente, indisponibilidade de produtos ou outros motivos. 
 
@@ -28,9 +26,7 @@ Este artigo apresenta de quais maneiras o pedido pode ser alterado e como realiz
 - [Aspectos comuns](#aspectos-comuns)
 - [Erros de processamento](#erros-de-processamento)
 
-<div class="alert alert-warning">
-Para saber sobre as <a href="https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#caracteristicas-gerais">características gerais</a> em cenários de alteração de pedidos, incluindo reserva, atualização de inventário e contas franquia, ou para entender questões de <a href="https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#mudancas-de-preco">preço, pagamento e fatura</a>, veja o artigo <a href="https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ">Como funciona a Alterar pedido (Beta)</a>.
-</div>
+>⚠️ Para saber sobre as [características gerais](https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#caracteristicas-gerais) em cenários de alteração de pedidos, incluindo reserva, atualização de inventário e contas franquia, ou para entender questões de [preço, pagamento e fatura](https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ#mudancas-de-preco), veja o artigo [Como funciona a Alterar pedido (Beta)](https://help.vtex.com/pt/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ).
 
 ## Requisitos
 
diff --git a/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md b/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md
index c7f10f158..9b333a6c4 100644
--- a/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md
+++ b/docs/tutorials/pt/how-to-change-the-order-of-payment-methods-at-checkout.md
@@ -19,9 +19,7 @@ Você pode mudar a ordem de exibição dos meios de pagamento no Checkout da sua
 - Pelo Admin.
 - Por meio de uma customização no JavaScript. 
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> ainda que exista essa possibilidade, por questões de segurança e performance, <strong>não recomendamos</strong> que você modifique os arquivos JavaScript do Checkout. A VTEX não se responsabiliza por qualquer problema gerado após a edição desse código.
-</div>
+>⚠️ **Atenção:** ainda que exista essa possibilidade, por questões de segurança e performance, **não recomendamos** que você modifique os arquivos JavaScript do Checkout. A VTEX não se responsabiliza por qualquer problema gerado após a edição desse código.
 
 ## Como funciona o ordenação
 
diff --git a/docs/tutorials/pt/how-to-change-the-sorting-of-delivery-types-in-the-cart.md b/docs/tutorials/pt/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
index 6b1270efb..b59f5fc09 100644
--- a/docs/tutorials/pt/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
+++ b/docs/tutorials/pt/how-to-change-the-sorting-of-delivery-types-in-the-cart.md
@@ -21,6 +21,4 @@ Ao clicar sobre o menu de tipos de entrega, o cliente poderá acessar outras op
 
 Este é um comportamento padrão da plataforma, e caso o lojista deseje modificá-lo, é possível customizar o carrinho (por meio de CSS e JavaScript), de acordo com as necessidades da loja.
 
-<div class="alert alert-warning">
-Lembramos que deve-se tomar muito cuidado em qualquer alteração de CSS ou JavaScript no carrinho. Se não for bem feito, esse tipo de customização pode comprometer a taxa de conversão da sua loja e a segurança do seu checkout 
-</div>
+>⚠️ Lembramos que deve-se tomar muito cuidado em qualquer alteração de CSS ou JavaScript no carrinho. Se não for bem feito, esse tipo de customização pode comprometer a taxa de conversão da sua loja e a segurança do seu checkout
diff --git a/docs/tutorials/pt/how-to-configure-a-custom-payment.md b/docs/tutorials/pt/how-to-configure-a-custom-payment.md
index 5fadb0f43..fc69d6be0 100644
--- a/docs/tutorials/pt/how-to-configure-a-custom-payment.md
+++ b/docs/tutorials/pt/how-to-configure-a-custom-payment.md
@@ -30,6 +30,4 @@ Permite que você utilize um cartão de crédito da Loja com uma das seguintes b
 
 Após essa configuração, será necessária a criação da [Condição de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento).
 
-<div class="alert alert-warning">
-Recomendamos o uso da aprovação automática apenas em casos em que o pagamento será realizado no momento da entrega ou da retirada na loja. Essa opção autoriza o pagamento do pedido, ou seja, o pedido passa automaticamente para o status de Preparando Entrega, sem a verificação do pagamento.
-  </div>
+>⚠️ Recomendamos o uso da aprovação automática apenas em casos em que o pagamento será realizado no momento da entrega ou da retirada na loja. Essa opção autoriza o pagamento do pedido, ou seja, o pedido passa automaticamente para o status de Preparando Entrega, sem a verificação do pagamento.
diff --git a/docs/tutorials/pt/how-to-configure-mercado-pago-pro-as-a-payment-method.md b/docs/tutorials/pt/how-to-configure-mercado-pago-pro-as-a-payment-method.md
index 2eeef43e4..62db5aab5 100644
--- a/docs/tutorials/pt/how-to-configure-mercado-pago-pro-as-a-payment-method.md
+++ b/docs/tutorials/pt/how-to-configure-mercado-pago-pro-as-a-payment-method.md
@@ -43,10 +43,6 @@ Do lado direito da tela, é possível configurar as [condições especiais de pa
 
 Entretanto, essa etapa é opcional. Você pode simplesmente clicar diretamente no __botão azul “Salvar”__ para finalizar a configuração do meio de pagamento. 
 
-<div class="alert alert-info">
-Para processar pagamentos feitos com o Pix, basta <a href="https://www.mercadopago.com.br/pix/">cadastrar uma chave Pix no Mercado Pago</a> após concluir a configuração do meio de pagamento. 
-</div>
+>ℹ️ Para processar pagamentos feitos com o Pix, basta [cadastrar uma chave Pix no Mercado Pago](https://www.mercadopago.com.br/pix/) após concluir a configuração do meio de pagamento.
 
-<div class="alert alert-warning">
-<strong>Lembre-se:</strong> novas condições de pagamento podem levar até 10 minutos para ser exibidas no SmartCheckout.
-</div>
+>⚠️ **Lembre-se:** novas condições de pagamento podem levar até 10 minutos para ser exibidas no SmartCheckout.
diff --git a/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md b/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
index 05455d4fa..2062d0b25 100644
--- a/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
+++ b/docs/tutorials/pt/how-to-configure-minimum-order-value-and-maximum-quantity-of-items-per-sku.md
@@ -32,9 +32,7 @@ Já em operações B2B, há necessidade de se manter relações com os comprador
 
 ![Minimum Order Value - PT](https://images.ctfassets.net/alneenqid6w5/6bJ49E109ewRg9VUoP16rP/4b4ff920a4c1a9a98ad3450e00f47d6c/Minimum_Order_Value_-_PT.png)
 
-<div class="alert alert-warning">
-Ao cliente é permitido montar um carrinho com um valor menor que o especificado na regra de "Valor mínimo total do carrinho". Entretanto, no momento de fechamento da compra, só serão concluídos os pedidos que estiverem com o valor igual ou acima do especificado.
-</div>
+>⚠️ Ao cliente é permitido montar um carrinho com um valor menor que o especificado na regra de "Valor mínimo total do carrinho". Entretanto, no momento de fechamento da compra, só serão concluídos os pedidos que estiverem com o valor igual ou acima do especificado.
 
 ## Definir uma quantidade máxima de itens do mesmo SKU por carrinho
 
@@ -44,8 +42,6 @@ Ao cliente é permitido montar um carrinho com um valor menor que o especificado
 
 ![Quantidade Maxima de um mesmo SKU no carrinho](https://images.ctfassets.net/alneenqid6w5/Tb4rS7FposwzygY5HlEpr/bb659e068dfde3a2e4d05480422a7113/Quantidade_Maxima_de_um_mesmo_SKU_no_carrinho_PT.png)
 
-<div class="alert alert-warning">
-Não existem limites para a quantidade máxima de itens do <b>mesmo SKU</b> por carrinho. A única restrição é referente a quantidade máxima de itens de <b>SKUs diferentes</b>, que devem ser no máximo de 300 itens por carrinho. 
-</div>
+>⚠️ Não existem limites para a quantidade máxima de itens do **mesmo SKU** por carrinho. A única restrição é referente a quantidade máxima de itens de **SKUs diferentes**, que devem ser no máximo de 300 itens por carrinho.
 
 Caso deseja utilizar ações que impeça o usuário de exceder os valores específicados ainda durante o fluxo de compra (por exemplo, criar uma trava do botão de acionar ao carrinho quando a quantida máxima de itens for atingida), será necessário criar uma customização no front-end da loja.
diff --git a/docs/tutorials/pt/how-to-configure-payment-conditions.md b/docs/tutorials/pt/how-to-configure-payment-conditions.md
index eeb47ebbc..2ef2f9f71 100644
--- a/docs/tutorials/pt/how-to-configure-payment-conditions.md
+++ b/docs/tutorials/pt/how-to-configure-payment-conditions.md
@@ -30,9 +30,7 @@ Uma vez definido a sua afiliação de gateway, para qualquer uma das condições
 
 Além disso, existe a possibilidade de definir se o pagamento será: à vista ou em parcelas, com ou sem juros, ou com [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456#).
 
-<div class="alert alert-warning">
-Quaisquer alterações nas condições de pagamento podem demorar até 10 minutos para aparecerem no checkout da sua loja.
-</div>
+>⚠️ Quaisquer alterações nas condições de pagamento podem demorar até 10 minutos para aparecerem no checkout da sua loja.
 
 Nas etapas abaixo, iremos utilizar o cartão de crédito como exemplo de condição de pagamento.
 
@@ -50,9 +48,7 @@ Nas etapas abaixo, iremos utilizar o cartão de crédito como exemplo de condiç
 8. No campo __À vista ou parcelado?__, selecione __À vista__.
 9. Clique em __Salvar__.
 
-<div class="alert alert-info">
-No Passo 5. você pode escolher outros métodos de pagamento como cartões de débito, cobranded, private, promissórias, boletos, PIX, entre outros.
-</div>
+>ℹ️ No Passo 5. você pode escolher outros métodos de pagamento como cartões de débito, cobranded, private, promissórias, boletos, PIX, entre outros.
 
 ### Parcelado sem juros
 
@@ -97,9 +93,7 @@ No Passo 5. você pode escolher outros métodos de pagamento como cartões de d
 
 Em alguns países, os juros das compras parceladas são cobrados diretamente pela instituição financeira. Para estes casos, é possível ativar o botão __Juros Externo__. Este botão preenche com `null` o valor dos juros no JSON enviado para o conector. O valor `null` indica que os juros serão cobrados posteriormente pela instituição financeira. Para ativar esta funcionalidade, clique no botão de __Juros Externo__ na configuração do parcelado com juros.
 
-<div class="alert alert-info">
-Atenção: a funcionalidade de juros externos é válida apenas para algumas afiliações de gateway (verifique se esta opção está disponível no momento de cadastrar a afiliação desejada). Os pedidos realizados por afiliações que não suportam esta funcionalidade serão cancelados no sistema.
-</div>
+>ℹ️ Atenção: a funcionalidade de juros externos é válida apenas para algumas afiliações de gateway (verifique se esta opção está disponível no momento de cadastrar a afiliação desejada). Os pedidos realizados por afiliações que não suportam esta funcionalidade serão cancelados no sistema.
 
 ## Remover condição de pagamento
 
diff --git a/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md b/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
index 0d1920157..2bc23562e 100644
--- a/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
+++ b/docs/tutorials/pt/how-to-configure-rating-and-review-controls.md
@@ -15,9 +15,7 @@ legacySlug: como-configurar-controle-de-avaliacao-e-resenha
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-danger">
-Este recurso está obsoleto. Sugerimos utilizar serviços de avaliação externos.
-</div>
+>❗ Este recurso está obsoleto. Sugerimos utilizar serviços de avaliação externos.
 
 Esse artigo tem o intuito de ensinar como utilizar os controles de avaliação e resenha.
 
diff --git a/docs/tutorials/pt/how-to-configure-subscriptions.md b/docs/tutorials/pt/how-to-configure-subscriptions.md
index a90a69be2..f3c86e013 100644
--- a/docs/tutorials/pt/how-to-configure-subscriptions.md
+++ b/docs/tutorials/pt/how-to-configure-subscriptions.md
@@ -34,9 +34,7 @@ Para ativar a funcionalidade será necessário:
 
 ## 1. Instalar o app de Assinaturas
 
-<div class="alert alert-warning">
-No momento, a instalação do módulo Assinaturas é feita somente por solicitação ao <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>⚠️ No momento, a instalação do módulo Assinaturas é feita somente por solicitação ao [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Para instalar o app gratuito de Assinaturas na [VTEX App Store](https://apps.vtex.com/), siga os passos abaixo:
 
@@ -63,9 +61,7 @@ Atualmente, os seguintes meios de pagamento estão habilitados para pedidos de a
 * **Boleto Bancário**
 * **Cartão de Crédito**
 
-<div class="alert alert-info">
-  <p>Para disponibilizar a opção de pagamento <strong>Cartão de Crédito</strong>, entre em contato com o adquirente da sua loja e certifique-se que ele aceita transações de compras recorrentes oriundas de cartões tokenizados (sem CVV). O sistema de <strong>Assinaturas</strong> utilizará os mesmos dados do cartão da primeira compra para realizar os pedidos seguintes da assinatura, garantindo a segurança de todo o processo.</p>
-</div>
+>ℹ️ Para disponibilizar a opção de pagamento **Cartão de Crédito**, entre em contato com o adquirente da sua loja e certifique-se que ele aceita transações de compras recorrentes oriundas de cartões tokenizados (sem CVV). O sistema de **Assinaturas** utilizará os mesmos dados do cartão da primeira compra para realizar os pedidos seguintes da assinatura, garantindo a segurança de todo o processo.
 
 Para habilitar esse tipo de transação no conector, o gestor da loja deverá solicitar ao adquirente a liberação para transacionar pagamentos recorrentes. Confira o nosso artigo sobre [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
 
@@ -79,9 +75,7 @@ Existe uma outra opção para criar um plano de assinatura, que consiste em cria
 
 Existe uma série de recursos relacionados a assinaturas, disponíveis no módulo de **Perfis de Acesso** da sua loja. São esses recursos que permitem o acesso dos usuários do seu Admin VTEX a determinadas funcionalidades, para operarem o módulo de Assinaturas. Para saber mais sobre perfis de acesso, confira o nosso [artigo](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso).
 
-<div class="alert alert-warning">
-<p>Se o usuário não tiver as permissões necessárias para acessar os dados das telas de <strong>Assinaturas</strong>, o sistema exibe um alerta informando que ele não tem essas permissões, e o usuário não consegue ver os dados.</p>
-</div>
+>⚠️ Se o usuário não tiver as permissões necessárias para acessar os dados das telas de **Assinaturas**, o sistema exibe um alerta informando que ele não tem essas permissões, e o usuário não consegue ver os dados.
 
 Veja a tabela abaixo para saber quais são os recursos relacionados ao módulo de Assinaturas.
 
diff --git a/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md b/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md
index 7ab252119..015d2fdf4 100644
--- a/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md
+++ b/docs/tutorials/pt/how-to-configure-the-fingerprint-device-for-stelo.md
@@ -19,15 +19,11 @@ __Device Fingerprint__ é um identificador que atua no processamento de um pagam
 
 Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
 
 Neste artigo, explicaremos como associar o recurso Device Fingerprint à afiliação Stelo.
 
-<div class="alert alert-info">
-As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.
-</div>
+>ℹ️ As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.
 
 Para inserir os scripts que a Stelo exige para o device fingerprint, é necessário usar o Google Tag Manager. Para isso, faça login na sua conta em [http://www.google.com/tagmanager](http://www.google.com/tagmanager). Depois, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md b/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
index d4d6ef75f..b381b083a 100644
--- a/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
+++ b/docs/tutorials/pt/how-to-configure-xml-vtex-for-the-2015-update-of-the-specification-for-the-google-shopping-feed-and-the-google-product-taxonomy.md
@@ -15,7 +15,7 @@ legacySlug:
 subcategory: 
 ---
 
-<div class="alert alert-warning">A integração com o Google Shopping por XML é um <strong>método ultrapassado</strong> e que não é mais recomendado. Veja [aqui](http://help.vtex.com/tutorial/nova-integracao-google-shopping-api "Nova integração do Google Shopping") como funciona a nova integração do Google Shopping por API.</div>
+>⚠️ A integração com o Google Shopping por XML é um **método ultrapassado** e que não é mais recomendado. Veja [aqui](http://help.vtex.com/tutorial/nova-integracao-google-shopping-api "Nova integração do Google Shopping") como funciona a nova integração do Google Shopping por API.
 
 Seguindo a [Atualização de 2015 da Especificação do feed do Google Shopping e da Taxonomia do produto do Google](https://support.google.com/merchants/answer/6231410?hl=pt-BR "Atualização de 2015 da Especificação do feed do Google Shopping e da Taxonomia do produto do Google"), incluímos novos campos em nosso formulário de criação de XML: Separador de categorias, Categoria Global e Especificações de produto.
 
diff --git a/docs/tutorials/pt/how-to-create-a-page-template.md b/docs/tutorials/pt/how-to-create-a-page-template.md
index 7d6b7e886..4c958cb48 100644
--- a/docs/tutorials/pt/how-to-create-a-page-template.md
+++ b/docs/tutorials/pt/how-to-create-a-page-template.md
@@ -36,16 +36,18 @@ Confira o passo a passo a seguir:
 3. Clique em __HTML Templates__.__
 4. Logo abaixo, clique em __New template.
 5. Preencha o campo __Template Name__.
-<div class="alert alert-danger">
-  <p>Ao preencher o <b>Template Name</b> do template, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-<li><code>app</code></li>
-</ul></p>
-</div>
+>❗ Ao preencher o **Template Name** do template, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+>
+> *`app`
+> 
 6. Em seguida, preencha o box __Template XHTML__ com o código do seu template.![4 1](https://images.ctfassets.net/alneenqid6w5/1BJRfbclbjHPUSztB6y0kP/bd95af131b622a00d9b41dee47789987/4_1.png)
 7. No canto superior direito, clique no botão __Save Template__.
 
diff --git a/docs/tutorials/pt/how-to-create-a-product.md b/docs/tutorials/pt/how-to-create-a-product.md
index a6848e12f..5640ed41e 100644
--- a/docs/tutorials/pt/how-to-create-a-product.md
+++ b/docs/tutorials/pt/how-to-create-a-product.md
@@ -32,9 +32,7 @@ O formulário de cadastro de um novo produto contém as seguintes seções:
 *   [SEO](#seo)
 *   [Frente de loja](#frente-de-loja)
 
-<div class="alert alert-info">
-  <p>Antes de criar um produto, você precisa criar a <a href="https://help.vtex.com/pt/tutorial/cadastrando-categoria--tutorials_206?&utm_source=autocomplete">Categoria</a> correspondente a esse produto, caso ela não tenha sido cadastrada anteriormente na sua loja.</p>
-</div>
+>ℹ️ Antes de criar um produto, você precisa criar a [Categoria](https://help.vtex.com/pt/tutorial/cadastrando-categoria--tutorials_206?&utm_source=autocomplete) correspondente a esse produto, caso ela não tenha sido cadastrada anteriormente na sua loja.
 
 ## Informações Básicas
 
@@ -83,9 +81,7 @@ Para adicionar imagens ao produto, siga o passo a passo abaixo:
 1. Clique no botão **Adicionar imagens** ou solte-as no espaço pontilhado.
 2. Insira todas as imagens do produto, incluindo suas variações, como cor e tamanho. As imagens devem estar no formato JPEG, PNG ou GIF, com até 5MB cada.
 
-<div class="alert alert-warning">
-<p>Recomendamos o uso de imagens com 600px ou mais, para que a exibição da imagem aconteça adequadamente na sua loja.</p>
-</div>
+>⚠️ Recomendamos o uso de imagens com 600px ou mais, para que a exibição da imagem aconteça adequadamente na sua loja.
 
 Você pode clicar em uma imagem e arrastá-la para antes ou depois das outras, caso deseje reorganizar as imagens e alterar a ordem de exibição na página do produto, conforme ilustrado abaixo.
 
@@ -144,9 +140,7 @@ Todo produto precisa ter pelo menos um [SKU](https://help.vtex.com/pt/tutorial/o
 
 Se você desejar criar mais de um SKU, de acordo com as variações possíveis do seu produto, opte por clicar no botão `+ Criar variações`.
 
-<div class="alert alert-warning">
-  <p>Ao clicar em <code>+ Criar variações</code>, os campos que tiverem sido preenchidos em <b>Informações do SKU</b> serão apagados.</p>
-</div>
+>⚠️ Ao clicar em `+ Criar variações`, os campos que tiverem sido preenchidos em **Informações do SKU** serão apagados.
 
 O que diferencia os SKUs ou variações do produto entre si são as diversas combinações de especificações possíveis. Exemplo: ao criar o produto _tênis_ e configurar a especificação _cor_ com as opções _rosa_ e _azul_ e a especificação _tamanho_ com as opções _36_ e _37_, os SKUs serão as combinações dessas opções: _tênis rosa 36_, _tênis rosa 37, tênis azul 36_ e _tênis azul 37_.
 
@@ -175,9 +169,7 @@ As especificações que você criou e suas respectivas opções são listadas ne
 
 Você pode alterar informações de cada especificação clicando no botão <i class="fas fa-pencil-alt"></i> na linha de cada uma.
 
-<div class="alert alert-info">
-  <p>Depois de definir as configurações de especificações do produto, não é possível excluir uma especificação nem adicionar uma nova. Durante a edição, você pode apenas adicionar novos valores para a especificação existente.</p>
-</div>
+>ℹ️ Depois de definir as configurações de especificações do produto, não é possível excluir uma especificação nem adicionar uma nova. Durante a edição, você pode apenas adicionar novos valores para a especificação existente.
 
 Também é possível clicar no botão **+ Adicionar especificações** para incluir mais especificações.
 
@@ -203,9 +195,7 @@ Ao clicar no botão <i class="fas fa-ellipsis-v"></i>, é possível realizar as
   * **Adicionar imagens:** neste painel, também é possível fazer upload de novas imagens, clicando no botão `Adicionar imagens` ou soltando arquivos de imagem no espaço pontilhado.
 * **Desativar:** desativar a variação na sua loja. 
 
-<div class="alert alert-warning">
-<p>Caso você adicione especificações após configurar as variações, todas as variações serão recalculadas e terão seus campos redefinidos.</p>
-</div>
+>⚠️ Caso você adicione especificações após configurar as variações, todas as variações serão recalculadas e terão seus campos redefinidos.
 
 ### Edição avançada
 
diff --git a/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md b/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md
index 1cda72103..d6804b2e5 100644
--- a/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md
+++ b/docs/tutorials/pt/how-to-create-a-promotion-with-limitation-of-use.md
@@ -17,9 +17,7 @@ subcategory: 1yTYB5p4b6iwMsUg8uieyq
 
 Para que uma promoção do tipo regular seja aplicada por um número limitado de vezes, basta desmarcar a opção **ilimitado** em restrições e limitações de uso. Quando desmarcada, é disponibilizado um campo para cadastrar a quantidade de vezes, em que a promoção poderá ser aplicada em compras na sua loja. Isso significa que se cadastrar o número 10, a promoção somente será concedida aos primeiros 10 pedidos fechados na sua loja, que atendam às regras da promoção.
 
-<div class="alert alert-warning">
-<p>Pedidos com status <code>Iniciando cancelamento</code> ou <code>Cancelado</code> não contam no limite definido.</p>
-</div>
+>⚠️ Pedidos com status `Iniciando cancelamento` ou `Cancelado` não contam no limite definido.
 
 ![LimitacaoPromocao](https://images.contentful.com/alneenqid6w5/1LsDiScSuE4g0Ww0QiKYEw/2584d871c716ee0abb46471e52b96d0e/LimitacaoPromocao.png)
 
diff --git a/docs/tutorials/pt/how-to-create-a-shelf-template.md b/docs/tutorials/pt/how-to-create-a-shelf-template.md
index a50b83adf..078739c7c 100644
--- a/docs/tutorials/pt/how-to-create-a-shelf-template.md
+++ b/docs/tutorials/pt/how-to-create-a-shelf-template.md
@@ -26,15 +26,16 @@ Para criar um template de prateleira, siga os passos abaixo:
 3. Clique em __Shelves Templates__.
 4. Clique em __new template__.
 5. Preencha o campo __Shelf Template Name__.
-<div class="alert alert-danger">
-  <p>Ao preencher o <b>Shelf Template Name</b> do template, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Ao preencher o **Shelf Template Name** do template, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 6. O campo __CSS Class__ cria uma *tag class* para este template. Este campo é opcional.
 7. Clique na caixa __Rounded corners__ para que o template tenha bordas arredondadas.
 8. Em __Template Code__ você deve preencher com o código do seu template. Utilize os templates padrões como uma base para a criação do novo. [Veja aqui o exemplo de um código básico](https://gist.githubusercontent.com/DeboraFerreira/a4126e2a60a6a0abb6c0/raw/8600e6e4c718c626158e472cdcee60ed03009a0f/template-prateleira).
diff --git a/docs/tutorials/pt/how-to-create-a-subscription-attachment.md b/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
index 81c22184f..af3d6f7a9 100644
--- a/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
+++ b/docs/tutorials/pt/how-to-create-a-subscription-attachment.md
@@ -15,9 +15,7 @@ legacySlug: como-criar-um-anexo-de-assinatura
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
- <div class="alert alert-info">
-  <p>Caso você utilize o módulo de <strong>Assinaturas Beta</strong>, o caminho mais recomendado para criar um plano de assinatura é diretamente no módulo de <strong>Assinaturas</strong>. Leia o artigo <a href="https://help.vtex.com/pt/tutorial/como-criar-um-plano-de-assinatura-beta--1qGRoFczm98Wgt81f9mUqC">Como criar um plano de assinatura (Beta)</a> para mais informações.</p>
-</div>
+ >ℹ️ Caso você utilize o módulo de **Assinaturas Beta**, o caminho mais recomendado para criar um plano de assinatura é diretamente no módulo de **Assinaturas**. Leia o artigo [Como criar um plano de assinatura (Beta)](https://help.vtex.com/pt/tutorial/como-criar-um-plano-de-assinatura-beta--1qGRoFczm98Wgt81f9mUqC) para mais informações.
 
 O **Anexo de SKU** é responsável por indicar que a funcionalidade de Assinatura está ativa para esse SKU, e também quais são as frequências disponíveis.
 
@@ -41,9 +39,7 @@ Para criar um anexo de SKU, siga os passos descritos abaixo.
      * `vtex.subscription.teste`
 5. Deixe a caixa de seleção **Anexo obrigatório** desmarcada.
 
- <div class="alert alert-warning">
-  <p>O campo <strong>Anexo obrigatório</strong> não pode ser marcado. Se o anexo for marcado como obrigatório, o sistema de <strong>Assinaturas</strong> tenta enviar um pedido com assinatura para um item que já possui um anexo obrigatório, gerando um erro no sistema. Caso isso ocorra por engano, desmarque a obrigatoriedade do anexo e, em seguida, solicite ao cliente da sua loja uma nova tentativa de realizar o pedido.</p>
-</div>
+ >⚠️ O campo **Anexo obrigatório** não pode ser marcado. Se o anexo for marcado como obrigatório, o sistema de **Assinaturas** tenta enviar um pedido com assinatura para um item que já possui um anexo obrigatório, gerando um erro no sistema. Caso isso ocorra por engano, desmarque a obrigatoriedade do anexo e, em seguida, solicite ao cliente da sua loja uma nova tentativa de realizar o pedido.
 
 6. Em **Status**, marque a caixa de seleção **Ativa/Desativa o anexo** e clique em `Salvar`.
 
@@ -77,9 +73,7 @@ Siga o passo a passo abaixo para configurar as frequências e datas de ciclo de
 
         ![PT Assinatura Exemplo Valores month](https://images.ctfassets.net/alneenqid6w5/3ogGjc6DLexe7YeL3qyiuI/748b3dd8e63870c539b58f3404521031/PT_Assinatura_Exemplo_Valores_month.png)
 
-<div class="alert alert-info">
-  <p>Caso nenhum valor seja inserido no campo <strong>Valores Permitidos</strong>, a data do ciclo de assinatura será o mesmo dia da semana (caso a frequência seja semanal) ou dia do mês (caso a frequência seja mensal) do pedido original.</p>
-</div>
+>ℹ️ Caso nenhum valor seja inserido no campo **Valores Permitidos**, a data do ciclo de assinatura será o mesmo dia da semana (caso a frequência seja semanal) ou dia do mês (caso a frequência seja mensal) do pedido original.
 
 ### Associar o anexo a um SKU
 
diff --git a/docs/tutorials/pt/how-to-create-conditional-prices.md b/docs/tutorials/pt/how-to-create-conditional-prices.md
index e44c771c6..28667cf7b 100644
--- a/docs/tutorials/pt/how-to-create-conditional-prices.md
+++ b/docs/tutorials/pt/how-to-create-conditional-prices.md
@@ -15,9 +15,8 @@ legacySlug: criar-precos-condicionais
 subcategory: 
 ---
 
-<div class="alert alert-warning"><strong>Nota: </strong>
-Só é possivel criar Preços Condicionais caso você tenha instalado a app <strong>Conditions Builder</strong> e tenha criado alguma condição. (Veja o artigo <a href="http://help.vtex.com/pt/tutorial/como-usar-o-conditions-builder-app">Como usar o Conditions Builder app</a>)
-</div>
+>⚠️ **Nota: **
+> Só é possivel criar Preços Condicionais caso você tenha instalado a app **Conditions Builder** e tenha criado alguma condição. (Veja o artigo [Como usar o Conditions Builder app](http://help.vtex.com/pt/tutorial/como-usar-o-conditions-builder-app))
 
 Preços condicionais são administrados no módulo de preços.
 
diff --git a/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md b/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
index 3753bf6c3..bf94a68e1 100644
--- a/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
+++ b/docs/tutorials/pt/how-to-define-the-url-for-a-product-page.md
@@ -25,9 +25,7 @@ Confira a seção [Regras de preenchimento](#regras-de-preenchimento) para enten
 
 ![textlink.pt](https://images.ctfassets.net/alneenqid6w5/3K8sFWVJYkESKC7EVWP4zZ/37e4b22a4f177d28c197042ad027c3de/textlink.pt.png)
 
-<div class="alert alert-info">
-  <p>Também é possível alterar a URL de um produto utilizando a <a href="https://developers.vtex.com/docs/api-reference/catalog-api#overview">API do Catálogo</a>. Nesse caso, o campo a ser alterado é o <code>LinkId</code>. Confira <a href="https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product">Update Product</a> para mais informações.</p>
-</div>
+>ℹ️ Também é possível alterar a URL de um produto utilizando a [API do Catálogo](https://developers.vtex.com/docs/api-reference/catalog-api#overview). Nesse caso, o campo a ser alterado é o `LinkId`. Confira [Update Product](https://developers.vtex.com/vtex-rest-api/reference/catalog-api-put-product) para mais informações.
 
 ## Regras de preenchimento
 
@@ -42,9 +40,7 @@ Ao preencher o campo **textLink**, é necessário respeitar as seguintes regras:
     * `api`
     * `admin`
 
-<div class="alert alert-danger">
-  <p>Observe que não cumprir as regras de preenchimento do <strong>textLink</strong> listadas acima pode prejudicar o desempenho da sua loja, causar problemas na busca e interferir no funcionamento de páginas definidas no Admin VTEX.</p>
-</div>
+>❗ Observe que não cumprir as regras de preenchimento do **textLink** listadas acima pode prejudicar o desempenho da sua loja, causar problemas na busca e interferir no funcionamento de páginas definidas no Admin VTEX.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/how-to-download-the-vtex-invoices.md b/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
index 070897087..b855f8100 100644
--- a/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
+++ b/docs/tutorials/pt/how-to-download-the-vtex-invoices.md
@@ -65,7 +65,7 @@ Para fazer o download de seu boleto, siga os passos abaixo:
 6. Clique em **Efetuar Pagamento**.
 7. Será gerado um boleto, e multa e juros serão incluídos automaticamente. 
 
-<div class="alert alert-info"> No Brasil, uma fatura roxa pode indicar que está atrasada mas com um novo boleto gerado para uma data próxima. Nesse caso, a fatura continuará em atraso até a quitação do pagamento. Caso não seja efetuado o pagamento do novo boleto, a fatura voltará a cor vermelha.</div>
+>ℹ️ No Brasil, uma fatura roxa pode indicar que está atrasada mas com um novo boleto gerado para uma data próxima. Nesse caso, a fatura continuará em atraso até a quitação do pagamento. Caso não seja efetuado o pagamento do novo boleto, a fatura voltará a cor vermelha.
 
 ![baixar boletos pt](https://images.ctfassets.net/alneenqid6w5/3gRniiqHrpZZHNTsQC8Gfm/21d45f702de76ea5c866b61a3c80be8f/baixar_boletos_pt.gif)
 
diff --git a/docs/tutorials/pt/how-to-export-a-product-spreadsheet.md b/docs/tutorials/pt/how-to-export-a-product-spreadsheet.md
index 33fed5bfd..27b156999 100644
--- a/docs/tutorials/pt/how-to-export-a-product-spreadsheet.md
+++ b/docs/tutorials/pt/how-to-export-a-product-spreadsheet.md
@@ -28,6 +28,4 @@ A seguir, confira o passo a passo para realizar esta operação:
 
 Em seguida, confira a caixa de entrada do email selecionado. Caso a operação tenha funcionado, o usuário terá recebido um email com um link para baixar a planilha completa.
 
-<div class="alert alert-warning">
-O comando só funciona adequadamente em casos de até 10 mil produtos. Caso o valor requerido seja maior que esse limite, o sistema não envia a planilha para o email. Use os filtros para refinar sua busca.
-</div>
+>⚠️ O comando só funciona adequadamente em casos de até 10 mil produtos. Caso o valor requerido seja maior que esse limite, o sistema não envia a planilha para o email. Use os filtros para refinar sua busca.
diff --git a/docs/tutorials/pt/how-to-find-an-sku-id.md b/docs/tutorials/pt/how-to-find-an-sku-id.md
index c8759a9a1..dbfe77780 100644
--- a/docs/tutorials/pt/how-to-find-an-sku-id.md
+++ b/docs/tutorials/pt/how-to-find-an-sku-id.md
@@ -46,6 +46,4 @@ Para descobrir o ID de um SKU pela URL de cadastro do SKU, siga os passos abaixo
 4. Observe a URL da página carregada. Você verá uma URL com o seguinte formato: `https://{accountName}.myvtex.com/admin/Site/SkuForm.aspx?IdSku={number}`
  O ID do SKU será o número exibido no lugar de `{number}`.
 
-<div class="alert alert-danger">
-Para garantir que itens adicionados ao estoque fiquem disponíveis para venda na loja, o <a href="https://help.vtex.com/pt/tutorial/descobrir-o-id-de-um-sku--4VQZsYeb3igGK2YowuEYWW"> ID do SKU </a> não deve conter <b>o número zero à esquerda</b>. O sistema não reconhece, por exemplo, IDs no formato <code>01</code>, <code>02</code>, <code>021</code>, pois é esperado o formato  <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ Para garantir que itens adicionados ao estoque fiquem disponíveis para venda na loja, o [ ID do SKU ](https://help.vtex.com/pt/tutorial/descobrir-o-id-de-um-sku--4VQZsYeb3igGK2YowuEYWW) não deve conter **o número zero à esquerda**. O sistema não reconhece, por exemplo, IDs no formato `01`, `02`, `021`, pois é esperado o formato  `1`, `2`, `21`.
diff --git a/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md b/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
index 943919156..c9a095a9a 100644
--- a/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
+++ b/docs/tutorials/pt/how-to-import-pickup-points-using-spreadsheets.md
@@ -19,9 +19,7 @@ Os pontos de retirada, também conhecidos como pickup points, são parte importa
 
 Você pode [configurar pontos de retirada um a um](/pt/tutorial/configurar-pontos-de-retirada-pickup-points) ou fazer isso através da importação de uma planilha XLS [(como a deste exemplo)](https://assets.ctfassets.net/alneenqid6w5/2QZFVRKdaoOkykE4AUkw6m/bdf62b6d028819b5b8c08ef7a27eadc6/pickups_example.xls). Usando um arquivo XLS, você cadastra todos os pickup points de uma única vez (desde que ele não ultrapasse 10 MB).
 
-<div class="alert alert-info">
-Um arquivo XLS de <strong>10 MB</strong> permite o cadastro de, aproximadamente, <strong>50 mil</strong> pontos de retirada. Para importar um número maior, é necessário dividi-los em mais de uma planilha e fazer um upload de cada vez.
-</div>
+>ℹ️ Um arquivo XLS de **10 MB** permite o cadastro de, aproximadamente, **50 mil** pontos de retirada. Para importar um número maior, é necessário dividi-los em mais de uma planilha e fazer um upload de cada vez.
 
 
 ## Como fazer o upload da planilha
diff --git a/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md b/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md
index 06090e085..5d845b850 100644
--- a/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md
+++ b/docs/tutorials/pt/how-to-include-a-registration-on-a-master-data-form.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Para incluir um registro, basta acessar o módulo Master Data e escolher a aplicação que você deseja visualizar.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 Vamos dizer, por exemplo, que voce deseje editar as informações de um cliente da sua loja.
 
diff --git a/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md b/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
index 50b4fce8c..c9485704b 100644
--- a/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
+++ b/docs/tutorials/pt/how-to-insert-a-reverse-proxy-in-front-of-vtex-services.md
@@ -15,10 +15,9 @@ legacySlug: por-que-nao-recomendamos-inserir-um-proxy-reverso-em-frente-aos-serv
 subcategory: 2Za4fjGfxYOo6oqykukgyy
 ---
 
-<div class="alert alert-danger">
-<p><strong>Atenção:</strong> as explicações deste artigo visam a atender a casos de extrema exceção. Não recomendamos que nenhuma loja utilize proxy reverso. Ao utilizar um proxy reverso, todo serviço de borda (CDN) gerenciado e otimizado pela VTEX será deixado de lado, de modo que o serviço da loja é quem ficará responsável pelo fornecimento efetivo do site, sendo este o responsável por fazer suas configurações, acompanhamento e gerenciamento de particularidades como repasse de cabeçalhos, cookies e gestão de cache. Não disponibilizamos documentação dessas especificidades.</p>
-<p>A VTEX não se responsabiliza por problemas nesse sistema, seja um CDN próprio, serviço de WAF ou outro recurso que fique à frente de nossos servidores. Não teremos visão de quaisquer falhas, e, portanto, a solução <strong>não</strong> se enquadrará em nossos acordos de SLA.</p>
-</div>
+>❗ **Atenção:** as explicações deste artigo visam a atender a casos de extrema exceção. Não recomendamos que nenhuma loja utilize proxy reverso. Ao utilizar um proxy reverso, todo serviço de borda (CDN) gerenciado e otimizado pela VTEX será deixado de lado, de modo que o serviço da loja é quem ficará responsável pelo fornecimento efetivo do site, sendo este o responsável por fazer suas configurações, acompanhamento e gerenciamento de particularidades como repasse de cabeçalhos, cookies e gestão de cache. Não disponibilizamos documentação dessas especificidades.
+>
+> A VTEX não se responsabiliza por problemas nesse sistema, seja um CDN próprio, serviço de WAF ou outro recurso que fique à frente de nossos servidores. Não teremos visão de quaisquer falhas, e, portanto, a solução **não** se enquadrará em nossos acordos de SLA.
 
 Se mesmo após ler o alerta acima você deseja apontar sua própria CDN para a CDN da VTEX, será necessário inserir um proxy reverso em frente aos serviços da VTEX.
 
@@ -34,11 +33,10 @@ Portanto, a configuração deve ficar assim:
 
 Além disso, também será necessário que todo o tráfego de `/.well-known/acme-challenge/*` chegue até a VTEX. Alguns proxys reversos capturam essa rota, e, com isso, não conseguimos emitir ou renovar o certificado SSL.
 
-<div class="alert alert-warning">
-<p>A VTEX somente provê navegação se for possível:
-  <ul>
-    <li>Observar que o host aponta para a VTEX (conforme nosso CNAME).</li>
-    <li>Emitir e renovar certificados SSL para o host.</li>
-  </ul>
-Se ambas as condições não forem atendidas, a navegação não funciona, pois fica caracterizado que o site está fora do ar.</p>
-</div>
+>⚠️ A VTEX somente provê navegação se for possível:
+>
+> * Observar que o host aponta para a VTEX (conforme nosso CNAME).
+>
+> * Emitir e renovar certificados SSL para o host.
+>
+> Se ambas as condições não forem atendidas, a navegação não funciona, pois fica caracterizado que o site está fora do ar.
diff --git a/docs/tutorials/pt/how-to-integrate-with-dafiti.md b/docs/tutorials/pt/how-to-integrate-with-dafiti.md
index 6f7cd9c4b..ccb3c959b 100644
--- a/docs/tutorials/pt/how-to-integrate-with-dafiti.md
+++ b/docs/tutorials/pt/how-to-integrate-with-dafiti.md
@@ -65,9 +65,7 @@ O mapeamento deve ser feito sempre que um produto for enviado pela primeira vez
 
 Siga o passo a passo abaixo, fazendo o de/para na __Planilha de Mapeamento__ entre o que está cadastrado no seu produto na VTEX e os valores especificados na __Planilha de Consulta__ da Dafiti.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> qualquer valor usado que não esteja na Planilha de Consulta vai ocasionar em um erro de integração.
-</div>
+>⚠️ **OBS:** qualquer valor usado que não esteja na Planilha de Consulta vai ocasionar em um erro de integração.
 
 1. __SKU:__ é o ID do SKU na VTEX. Esse é o ID do SKU que você deseja enviar para a Dafiti.
 
@@ -89,10 +87,11 @@ Siga o passo a passo abaixo, fazendo o de/para na __Planilha de Mapeamento__ ent
 7. __Modelo:__ preencha com o valor do modelo do seu SKU. Esse campo é livre para ser preenchido da maneira que você achar mais adequada.
 <br/>_`Ex:` você está mapeando uma calça de moletom. Normalmente, a coluna __Modelo__ é preenchida com o valor `Moletom`._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> na integração brasileira, a Dafiti exige que o nome dos produtos cadastrados sigam o seguinte padrão: <strong>Tipo de Produto + Marca + Modelo + Cor.</strong>
-<br/>
-Sendo assim, sempre que encontrarmos valores para esses quatro campos na VTEX, criaremos o novo nome de produto automaticamente. Se algum dos campos não estiver presente, enviaremos o nome original do produto.</div>
+>⚠️ **OBS:** na integração brasileira, a Dafiti exige que o nome dos produtos cadastrados sigam o seguinte padrão: **Tipo de Produto + Marca + Modelo + Cor.**
+>
+>
+> 
+> Sendo assim, sempre que encontrarmos valores para esses quatro campos na VTEX, criaremos o novo nome de produto automaticamente. Se algum dos campos não estiver presente, enviaremos o nome original do produto.
 
 
 ## Envio de imagens
@@ -108,9 +107,7 @@ Para fazer o envio pela Planilha de Mapeamento, siga este passo a passo:
 
 Você pode enviar até __oito imagens__. Para isso, você vai precisar adicionar novas colunas, seguindo o padrão indicado: `Image_2`, `Image_3`,..., `Image_8`.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> lembre-se de sempre usar <code>http</code> ou <code>https</code> no início das URLs. Se você não fizer isso, haverá erro ao tentar realizar o upload da planilha na VTEX.
-</div>
+>⚠️ **OBS:** lembre-se de sempre usar `http` ou `https` no início das URLs. Se você não fizer isso, haverá erro ao tentar realizar o upload da planilha na VTEX.
 
 
 ## Envio da Marca do Produto
@@ -118,9 +115,7 @@ Você pode enviar até __oito imagens__. Para isso, você vai precisar adicionar
 A integração vai enviar a marca que está cadastrada no seu produto no catálogo da VTEX.
 <br/>_`Ex:` se você estiver enviando uma camisa da Adidas, a integração vai enviar `Adidas` como marca._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> semelhante ao que acontece com categoria e especificações, a Dafiti possui marcas mapeadas em sua plataforma. Nesse caso, se algum de seus produtos tem uma marca que não esteja cadastrada na Dafiti, ele vai sofrer um erro de integração. Se isso acontecer, entre em contato com a Dafiti para solicitar o cadastro da marca em questão no sistema deles.
-</div>
+>⚠️ **OBS:** semelhante ao que acontece com categoria e especificações, a Dafiti possui marcas mapeadas em sua plataforma. Nesse caso, se algum de seus produtos tem uma marca que não esteja cadastrada na Dafiti, ele vai sofrer um erro de integração. Se isso acontecer, entre em contato com a Dafiti para solicitar o cadastro da marca em questão no sistema deles.
 
 
 ## Fazendo o upload
diff --git a/docs/tutorials/pt/how-to-integrate-with-facebook.md b/docs/tutorials/pt/how-to-integrate-with-facebook.md
index b1f57c216..62f64beda 100644
--- a/docs/tutorials/pt/how-to-integrate-with-facebook.md
+++ b/docs/tutorials/pt/how-to-integrate-with-facebook.md
@@ -49,18 +49,12 @@ __URL do site da loja__: Preencha com o endereço da sua loja. Exemplo: `https:/
 
 Após realizada a configuração, é necessário autorizar a VTEX a fazer alterações na conta do Facebook do lojista. Para isso, é necessário clicar no botão __Autorizar__, no card do Facebook, na seção de __Integrações__. Com isso, as autorizações necessárias serão solicitadas.
 
-<div class="alert alert-info">
-  Para fazer a autorização, deve ser usada a conta do Facebook que tem privilégios administrativos no Business Manager do Facebook. Caso ela não possua privilégios, a autorização não será concedida e o processo ficará em loop.
-</div>
+>ℹ️ Para fazer a autorização, deve ser usada a conta do Facebook que tem privilégios administrativos no Business Manager do Facebook. Caso ela não possua privilégios, a autorização não será concedida e o processo ficará em loop.
 
 Após esse passo, a integração criará um catálogo com o nome `VtexIntegration – {NOME DA LOJA}` no Facebook.
 
 É neste catálogo, dentro do Facebook, que os itens serão criados e ficarão disponíveis para serem usados.
 
-<div class="alert alert-info">
-  Para fazer a autorização, deve ser usada a conta do Facebook que tem privilégios administrativos no Business Manager do Facebook. Caso ela não possua privilégios, a autorização não será concedida e o processo ficará em loop.
-</div>
+>ℹ️ Para fazer a autorização, deve ser usada a conta do Facebook que tem privilégios administrativos no Business Manager do Facebook. Caso ela não possua privilégios, a autorização não será concedida e o processo ficará em loop.
 
-<div class="alert alert-info">
-É possível usar o *pixel app* do Facebook para acompanhar e otimizar os resultados das suas campanhas de marketing através do Google Tag Manager da sua loja. Aprenda o passo a passo <a href="https://www.facebook.com/business/help/1021909254506499">aqui</a>.
-</div>
+>ℹ️ É possível usar o *pixel app* do Facebook para acompanhar e otimizar os resultados das suas campanhas de marketing através do Google Tag Manager da sua loja. Aprenda o passo a passo [aqui](https://www.facebook.com/business/help/1021909254506499).
diff --git a/docs/tutorials/pt/how-to-make-transfers.md b/docs/tutorials/pt/how-to-make-transfers.md
index 717e8f74e..2ea3fdfac 100644
--- a/docs/tutorials/pt/how-to-make-transfers.md
+++ b/docs/tutorials/pt/how-to-make-transfers.md
@@ -68,6 +68,4 @@ A mensagem informa o status - se foi concluída com sucesso ou se ocorreu algum
 
 Contudo, essa não é a única forma de conferir essas informações. Se necessário, o lojista também pode consultá-las no módulo __Extrato Financeiro__. Na aba __“Consolidado”__, basta selecionar o recebimento desejado para visualizar os detalhes.
 
-<div class="alert alert-info">
-Assim como em operações bancárias, a transferência solicitada pode ser negada no caso em que o lojista alcança o limite de sua conta. Caso necessário, o aumento de limite pode ser solicitado por meio de um ticket na plataforma de atendimento VTEX.
-</div>
+>ℹ️ Assim como em operações bancárias, a transferência solicitada pode ser negada no caso em que o lojista alcança o limite de sua conta. Caso necessário, o aumento de limite pode ser solicitado por meio de um ticket na plataforma de atendimento VTEX.
diff --git a/docs/tutorials/pt/how-to-migrate-a-store-to-pricing.md b/docs/tutorials/pt/how-to-migrate-a-store-to-pricing.md
index 20b0ce519..c0432a8de 100644
--- a/docs/tutorials/pt/how-to-migrate-a-store-to-pricing.md
+++ b/docs/tutorials/pt/how-to-migrate-a-store-to-pricing.md
@@ -43,9 +43,7 @@ O Pricing possui algumas diferenças importantes em relação à primeira versã
 
 ## Migração da loja para o Pricing v2
 
-<div class="alert alert-info">
-Toda nova loja VTEX já é criada com o Pricing v2. 
-</div>
+>ℹ️ Toda nova loja VTEX já é criada com o Pricing v2.
 
 O Pricing v2 está disponível para as lojas que desejarem migrar para o novo módulo. Atualmente, temos um processo de migração automática, em que verificamos a compatibilidade das features do Pricing v2 com as features utilizadas atualmente pela loja. 
 
diff --git a/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md b/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md
index 88f1b445f..437628a41 100644
--- a/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md
+++ b/docs/tutorials/pt/how-to-modify-details-of-customers-addresses.md
@@ -25,19 +25,14 @@ Para editar as informações do cliente é necessário seguir os seguintes passo
 6. Clique em `Salvar`.
 7. Em seguida, clique em `Voltar` para ver novamente a lista de endereços.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
diff --git a/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
index 30e0ae5b2..129d3fd57 100644
--- a/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
@@ -31,9 +31,7 @@ Se o sistema de busca não identifica Landing Page, Marca ou Departamento de aco
 
 Apesar de ter um peso baixo para a pontuação do indexador, a utilização de palavras substitutas é um recurso extremamente importante, já que torna possível alcançar usuários que realizam buscas por termos com erros gramaticais (spagetti), redação fonética (espagueti) ou palavras mal escritas por erros de digitação (spaguetto), mas com a mesma semântica da palavra original (spaguetti).
 
-<div class="alert alert-info">
-Um recurso muito utilizado para agilizar as buscas da equipe interna é colocar o RefId/EAN como Palavra Substituta no produto. Assim, é possível fazer buscas mais rápidas, com resultados únicos e encontrar agilmente o produto buscado.
-</div>
+>ℹ️ Um recurso muito utilizado para agilizar as buscas da equipe interna é colocar o RefId/EAN como Palavra Substituta no produto. Assim, é possível fazer buscas mais rápidas, com resultados únicos e encontrar agilmente o produto buscado.
 
 ## Como carrego uma palavra substituta
 
diff --git a/docs/tutorials/pt/how-to-place-a-regular-order-using-vtex-apis.md b/docs/tutorials/pt/how-to-place-a-regular-order-using-vtex-apis.md
index ddee04538..d9c12c333 100644
--- a/docs/tutorials/pt/how-to-place-a-regular-order-using-vtex-apis.md
+++ b/docs/tutorials/pt/how-to-place-a-regular-order-using-vtex-apis.md
@@ -19,9 +19,7 @@ Neste tutorial, você aprenderá a fazer um simples pedido **REGULAR** (feito, p
 
 Vamos começar!
 
-<div class="alert alert-warning">
-<strong>Importante:</strong> para qualquer autenticação requerida pelas APIs apresentadas neste tutorial, você deve fornecer um <b>AppToken</b> e um <b>AppKey</b> válidos, registrados no módulo <b>License Manager</b> da sua conta e habilitados com permissões suficientes.
-</div>
+>⚠️ **Importante:** para qualquer autenticação requerida pelas APIs apresentadas neste tutorial, você deve fornecer um **AppToken** e um **AppKey** válidos, registrados no módulo **License Manager** da sua conta e habilitados com permissões suficientes.
 
 **PERMISSÕES NECESSÁRIAS**
 
diff --git a/docs/tutorials/pt/how-to-rank-the-best-selling-items.md b/docs/tutorials/pt/how-to-rank-the-best-selling-items.md
index 74e97f4d7..d82fdbb9c 100644
--- a/docs/tutorials/pt/how-to-rank-the-best-selling-items.md
+++ b/docs/tutorials/pt/how-to-rank-the-best-selling-items.md
@@ -15,9 +15,7 @@ legacySlug: como-vejo-um-ranking-dos-produtos-mais-vendidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-warning">
-O módulo <strong>Pedidos</strong> não tem o objetivo de servir como ferramenta de BI (Business Inteligence). Normalmente, é no ERP que a loja tem acesso aos relatórios de vendas.
-</div>
+>⚠️ O módulo **Pedidos** não tem o objetivo de servir como ferramenta de BI (Business Inteligence). Normalmente, é no ERP que a loja tem acesso aos relatórios de vendas.
 
 Embora o objetivo principal do módulo **Pedidos** seja gerenciar o fluxo de pedidos, é possível manipular os dados da [planilha de pedidos](https://help.vtex.com/tutorial/planilha-de-pedidos) para extrair informações que podem ser úteis ao seu negócio.
 
diff --git a/docs/tutorials/pt/how-to-register-your-salespersons-on-vtex-instore.md b/docs/tutorials/pt/how-to-register-your-salespersons-on-vtex-instore.md
index 82619d6b5..8e372db70 100644
--- a/docs/tutorials/pt/how-to-register-your-salespersons-on-vtex-instore.md
+++ b/docs/tutorials/pt/how-to-register-your-salespersons-on-vtex-instore.md
@@ -15,6 +15,4 @@ legacySlug: como-cadastrar-vendedores-no-vtex-instore
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-<div class="alert alert-info">
-Este artigo está obsoleto. <a href="https://help.vtex.com/pt/tracks/instore-setup?step=2">Clique aqui</a> para acessar nosso tutorial com o passo a passo para cadastrar vendedores no inStore.
-</div>
+>ℹ️ Este artigo está obsoleto. [Clique aqui](https://help.vtex.com/pt/tracks/instore-setup?step=2) para acessar nosso tutorial com o passo a passo para cadastrar vendedores no inStore.
diff --git a/docs/tutorials/pt/how-to-request-receivables-anticipation.md b/docs/tutorials/pt/how-to-request-receivables-anticipation.md
index fd3877a04..f16580bf0 100644
--- a/docs/tutorials/pt/how-to-request-receivables-anticipation.md
+++ b/docs/tutorials/pt/how-to-request-receivables-anticipation.md
@@ -33,9 +33,7 @@ Por exemplo, caso o seu menor recebível seja de R$10, esse é o valor mínimo q
 
 ![image](https://images.ctfassets.net/alneenqid6w5/oWY3RyEekfyjuBEjI27m3/18aba6b309f1acb3f945100927d25ead/image.png)
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: recebíveis em disputa ou previstos para o próximo dia útil não podem ser antecipados.
-</div>
+>ℹ️ **Atenção**: recebíveis em disputa ou previstos para o próximo dia útil não podem ser antecipados.
 
 Desse modo, confira o passo a passo para solicitar a antecipação:
 
diff --git a/docs/tutorials/pt/how-to-schedule-prices-for-a-range-of-hours.md b/docs/tutorials/pt/how-to-schedule-prices-for-a-range-of-hours.md
index 908f84af9..cae6e14d0 100644
--- a/docs/tutorials/pt/how-to-schedule-prices-for-a-range-of-hours.md
+++ b/docs/tutorials/pt/how-to-schedule-prices-for-a-range-of-hours.md
@@ -20,9 +20,7 @@ Entre outros cenários, um dos pontos mais importantes em um evento massivo como
 ## Agendar hora por API
 Uma das opções para agendar preços por hora é fazer isso por API de preços:
 
-<div class="alert alert-info">
-<a href="https://developers.vtex.com/reference/pricing-api-overview">Ver documentação de APIs</a>
-</div>
+>ℹ️ [Ver documentação de APIs](https://developers.vtex.com/reference/pricing-api-overview)
 
 O backend da VTEX utiliza o horário UTC, o que, por exemplo, na Argentina é GTM-3. Se você quiser agendar um preço x hora por meio de API e quiser que os preços comecem às 00h00 e terminem às 10h00, deve enviar 03h00 a mais das que efetivamente deseja configurar. Ou seja, se a validade do preço comece à 00h00, deve-se enviar 03h00, e se quiser que termine às 10h00, deve-se enviar 13h00:
 
diff --git a/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md b/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
index 01c966959..2b35642c4 100644
--- a/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
+++ b/docs/tutorials/pt/how-to-set-up-fingerprint-for-payu.md
@@ -19,13 +19,11 @@ __Device Fingerprint__ é um identificador que atua no processamento de um pagam
 
 Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
 
 Neste artigo, explicaremos como associar o recurso Device Fingerprint à afiliação PayU.
 
-<div class="alert alert-info">As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.</div>
+>ℹ️ As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.
 
 1. Fazer login em http://www.google.com/tagmanager/ para a loja que vamos configurar;
 2. Introduzir o item etiquetas (tags) para configurar o id da sessão do device;
diff --git a/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md b/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
index 33ef54fc5..d42422261 100644
--- a/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
+++ b/docs/tutorials/pt/how-to-set-up-the-connector-to-accept-payments-with-adyen-at-vtex.md
@@ -15,9 +15,9 @@ legacySlug: como-configurar-o-gateway-adyen-na-vtex
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
-<div class="alert alert-warning">As configurações documentadas neste artigo são realizadas em um ambiente externo à VTEX. Portanto, podem ser descontinuadas sem prévio aviso.</div>
+>⚠️ As configurações documentadas neste artigo são realizadas em um ambiente externo à VTEX. Portanto, podem ser descontinuadas sem prévio aviso.
 
 Caso o seu processador de pagamentos escolhido seja a Adyen, siga o passo a passo abaixo com a configuração necessária para que a comunicação entre VTEX e Adyen funcione perfeitamente.
 
diff --git a/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md b/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
index 1061ba7c6..eeb8fd5a6 100644
--- a/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
+++ b/docs/tutorials/pt/how-to-set-up-the-device-fingerprint-for-braspag.md
@@ -19,13 +19,11 @@ __Device Fingerprint__ é um identificador que atua no processamento de um pagam
 
 Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
 
 Neste artigo, explicaremos como associar o recurso Device Fingerprint à afiliação Braspag.
 
-<div class="alert alert-info">As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.</div>
+>ℹ️ As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.
 
 Para inserir os scripts que a Braspag/CyberSource exige para o device fingerprint, é necessário o uso do Google Tag Manager. Para isso, faça login em [http://www.google.com/tagmanager](http://www.google.com/tagmanager/) e entre em sua conta.
 
diff --git a/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md b/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
index ccf676ca2..fc7797641 100644
--- a/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
+++ b/docs/tutorials/pt/how-to-set-up-the-indeva-scheduled-appointment.md
@@ -33,9 +33,7 @@ O fluxo de agendamento percorrido pelo cliente se inicia na escolha da loja fís
 
 ![indeva1](https://images.ctfassets.net/alneenqid6w5/3QXzMhoJN1qYZZ6c8mlfcB/4cf28e34420ac49bfcaa6f78a9b2951a/indeva1.png)
 
-<div class="alert alert-info">
-É possível também fornecer ao cliente um link que conduz diretamente ao formulário de uma loja física específica. Basta adicionar o ID da loja ao final da URL. Dessa forma, o vendedor pode compartilhar o link de sua loja – por exemplo, por meio de um QR Code ou nas mídias sociais.
-</div>
+>ℹ️ É possível também fornecer ao cliente um link que conduz diretamente ao formulário de uma loja física específica. Basta adicionar o ID da loja ao final da URL. Dessa forma, o vendedor pode compartilhar o link de sua loja – por exemplo, por meio de um QR Code ou nas mídias sociais.
 
 Ao clicar na loja desejada, o cliente é levado ao formulário. Ali, ele encontra informações sobre a loja (que devem ser definidas na etapa de implementação), além dos campos para inserir as informações sobre a visita:
 
diff --git a/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md b/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
index 091692c60..ea5f296de 100644
--- a/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
+++ b/docs/tutorials/pt/how-to-set-up-the-responsible-for-pick-up-field-in-smartcheckout-v6.md
@@ -15,15 +15,11 @@ legacySlug: como-configurar-o-campo-responsavel-pela-retirada-no-smartcheckout-t
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-<div class="alert alert-info">
-O campo <strong>Responsável pela retirada</strong> só está disponível para o <strong>SmartCheckout™ V6</strong>, versão compatível com a feature de Pontos de Retirada (Pickup Points).
-</div>
+>ℹ️ O campo **Responsável pela retirada** só está disponível para o **SmartCheckout™ V6**, versão compatível com a feature de Pontos de Retirada (Pickup Points).
 
 Os [pontos de retirada](/pt/tutorial/configurar-pontos-de-retirada-pickup-points) dão mais uma opção aos seus clientes: ao invés de esperar a entrega, eles podem escolher ir até um ponto definido e buscar o item pessoalmente. Por default, essa ação está vinculada ao usuário cadastrado que efetuou a compra. No entanto, você pode habilitar o campo `Responsável pela retirada` no checkout da sua loja, para que seu cliente possa nomear outra pessoa para retirar o produto.
 
-<div class="alert alert-warning">
-Caso você possua o app <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings">Checkout UI Settings</a> instalado em sua loja, o código CSS descrito no procedimento abaixo deverá ser inserido somente via o app. Os scripts inseridos via interface do Admin VTEX (aba <b>Código > Files</b>) não são reproduzidos em lojas que possuem o aplicativo instalado.
-</div>
+>⚠️ Caso você possua o app [Checkout UI Settings](https://developers.vtex.com/vtex-developer-docs/docs/vtex-checkout-ui-settings) instalado em sua loja, o código CSS descrito no procedimento abaixo deverá ser inserido somente via o app. Os scripts inseridos via interface do Admin VTEX (aba **Código > Files**) não são reproduzidos em lojas que possuem o aplicativo instalado.
 
 Para configurar o campo (que vem desativado por padrão), siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md b/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md
index 02ebacc5b..b88556bec 100644
--- a/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md
+++ b/docs/tutorials/pt/how-to-set-up-your-store-on-seller-portal.md
@@ -44,7 +44,7 @@ Saiba alguns detalhes sobre o Seller Portal:
 
 ## Configurar sua loja
 
-<div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+>⚠️ O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.
 
 Para começar a vender seus produtos no marketplace, é preciso configurar a sua loja no Seller Portal. Este artigo explica o fluxo completo dessa configuração inicial e indica outras documentações para que você acesse cada passo em mais detalhes. A configuração básica do Seller Portal inclui os passos listados abaixo.
 
@@ -203,6 +203,4 @@ Optando pela integração, não haverá necessidade de configuração manual por
 
 Para realizar esta ação, siga as instruções em nosso [guia de integração com ERP](https://developers.vtex.com/docs/guides/erp-integration-guide).
 
-<div class="alert alert-info"> 
-<p>Para gerar as chaves de acesso necessárias para integrar com seu ERP, clique no <strong>avatar do seu perfil</strong>, marcado pela inicial do seu email e acesse <strong>Configurações da conta > Chaves de aplicação</strong>.</p>
-</div>
+>ℹ️ Para gerar as chaves de acesso necessárias para integrar com seu ERP, clique no **avatar do seu perfil**, marcado pela inicial do seu email e acesse **Configurações da conta > Chaves de aplicação**.
diff --git a/docs/tutorials/pt/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md b/docs/tutorials/pt/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
index 95a74a4c7..f515908af 100644
--- a/docs/tutorials/pt/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
+++ b/docs/tutorials/pt/how-to-setup-google-analytics-4-in-vtex-stores-in-legacy-cms-portal.md
@@ -15,18 +15,14 @@ legacySlug: configurar-google-analytics-4-em-loja-vtex-no-cms-portal-legado
 subcategory: 1luKrYptdi8WoMYckakUaM
 ---
 
-<div class="alert alert-info">
-  <p>Este artigo se aplica somente a lojas que utilizam o <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS - Portal Legado</a>.</p>
-</div>
+>ℹ️ Este artigo se aplica somente a lojas que utilizam o [CMS - Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
 
 O [Google Analytics 4](https://support.google.com/analytics/answer/10089681) (GA4) é a versão atual da ferramenta de análise de dados do Google.  Para obter dados sobre a navegação em sua loja VTEX pelo Google Analytics 4, você precisa:
 
 - [Configurar Google Analytics 4](#configurar-google-analytics-4)
 - [Editar configurações do Checkout](#editar-configuracoes-do-checkout)
 
-<div class="alert alert-warning">
-  <p>A partir de 1º de julho de 2023, o Google Analytics 4 vai substituir o Universal Analytics, versão anterior da ferramenta. Portanto, é necessário seguir este tutorial para adaptar a sua loja. Confira detalhes sobre a mudança <a href="https://support.google.com/analytics/answer/11583528">neste comunicado do Google</a>.</p>
-</div>
+>⚠️ A partir de 1º de julho de 2023, o Google Analytics 4 vai substituir o Universal Analytics, versão anterior da ferramenta. Portanto, é necessário seguir este tutorial para adaptar a sua loja. Confira detalhes sobre a mudança [neste comunicado do Google](https://support.google.com/analytics/answer/11583528).
 
 ## Configurar Google Analytics 4
 
diff --git a/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md b/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md
index 9af32d91d..db4b11afd 100644
--- a/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md
+++ b/docs/tutorials/pt/how-to-setup-google-analytics-in-vtex-store.md
@@ -20,9 +20,7 @@ O [Google Analytics 4 (GA4)](https://support.google.com/analytics/answer/1008968
 1. [Configurar Google Analytics 4](#configurar-google-analytics-4)
 2. [Configurar Google Tag Manager](#configurar-google-tag-manager)
 
-<div class="alert alert-info">
-A partir de 1º de julho de 2023, o Google Analytics 4 vai substituir o Universal Analytics, versão anterior da ferramenta. Portanto, é necessário seguir este tutorial para adaptar a sua loja. Confira detalhes sobre a mudança <a href="https://support.google.com/analytics/answer/11583528">neste comunicado do Google</a>.
-</div>
+>ℹ️ A partir de 1º de julho de 2023, o Google Analytics 4 vai substituir o Universal Analytics, versão anterior da ferramenta. Portanto, é necessário seguir este tutorial para adaptar a sua loja. Confira detalhes sobre a mudança [neste comunicado do Google](https://support.google.com/analytics/answer/11583528).
 
 ## Configurar Google Analytics 4
 
diff --git a/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md b/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md
index b48b816f2..0a6270032 100644
--- a/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md
+++ b/docs/tutorials/pt/how-to-turn-my-store-website-into-a-pwa.md
@@ -23,8 +23,7 @@ PWA é a abreviação em inglês de Progressive Web App - um conjunto de técnic
 
 Se você já tem um site ou uma aplicação web, pode implementar aos poucos as características que definem um PWA, como notificações, cache de arquivos, execução em modo off-line e outras possibilidades que fazem o usuário se sentir em um aplicativo nativo.
 
-<div class="alert alert-warning">
-A plataforma VTEX <strong>não</strong> possui features nativas para transformar sua loja em PWA. Ela apenas oferece as condições para que essa implementação seja feita. Lojas desenvolvidas com o VTEX IO Store Framework possuem este recurso nativamente.</div>
+>⚠️ A plataforma VTEX **não** possui features nativas para transformar sua loja em PWA. Ela apenas oferece as condições para que essa implementação seja feita. Lojas desenvolvidas com o VTEX IO Store Framework possuem este recurso nativamente.
 
 ## O Google define com exatidão o que é esperado de um PWA:
 
diff --git a/docs/tutorials/pt/how-to-update-the-image-of-an-sku.md b/docs/tutorials/pt/how-to-update-the-image-of-an-sku.md
index 042d43bfe..7a2af1039 100644
--- a/docs/tutorials/pt/how-to-update-the-image-of-an-sku.md
+++ b/docs/tutorials/pt/how-to-update-the-image-of-an-sku.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Você pode atualizar uma imagem de SKU no Admin VTEX ou utilizando a Catalog API.
 
-<div class="alert alert-danger">
-Este procedimento deve ser realizado com muito cuidado, pois envolve a <em>exclusão de todas as imagens</em> de um SKU, o que vai torná-lo <strong>INATIVO</strong>. Fique atento às recomendações nos passos abaixo para que a atualização das imagens ocorra com sucesso.
-</div>
+>❗ Este procedimento deve ser realizado com muito cuidado, pois envolve a *exclusão de todas as imagens* de um SKU, o que vai torná-lo **INATIVO**. Fique atento às recomendações nos passos abaixo para que a atualização das imagens ocorra com sucesso.
 
 Como este procedimento envolve a exclusão de todas as imagens de um SKU, tornando-o inativo, recomendamos que o processo de substituição de imagens seja realizado em pequenos lotes de SKUs.
 
@@ -33,9 +31,7 @@ Como este procedimento envolve a exclusão de todas as imagens de um SKU, tornan
 4. Clique na aba __Imagens__.
 5. Escolha as imagens que deseja apagar e clique em __Retirar__.
 
-<div class="alert alert-danger">
-Recomendamos que essas atualizações de imagens sejam feitas em pequenos lotes. Lembre-se que ao apagar todas as imagens de um SKU ele ficará inativo.
-</div>
+>❗ Recomendamos que essas atualizações de imagens sejam feitas em pequenos lotes. Lembre-se que ao apagar todas as imagens de um SKU ele ficará inativo.
 
 ### Adicionar as novas imagens
 
diff --git a/docs/tutorials/pt/how-to-use-messages-on-your-io-apps.md b/docs/tutorials/pt/how-to-use-messages-on-your-io-apps.md
index 07b7eb774..532efac51 100644
--- a/docs/tutorials/pt/how-to-use-messages-on-your-io-apps.md
+++ b/docs/tutorials/pt/how-to-use-messages-on-your-io-apps.md
@@ -17,9 +17,7 @@ subcategory: 54gbzsku02c4bKmgFbp3v3
 
 O VTEX IO possui um serviço de internacionalização embutido chamado __Messages__. Neste tutorial você vai aprender como internacionalizar seu app de front end e as respostas dos seu back end. 
 
-<div class="alert alert-info">
-Essa funcionalidade é disponível apenas para aplicativos react/graphql/typedql.
-</div>
+>ℹ️ Essa funcionalidade é disponível apenas para aplicativos react/graphql/typedql.
 
 ## Tradução do Messages
 
@@ -60,9 +58,7 @@ Para obter uma tradução automática mais precisa, crie um arquivo chamado `con
 
 Esse arquivo funciona para remover as possíveis ambiguidades das traduções. Por exemplo, a palavra 'Ciao' em italiano significa _Oi_ e _Tchau_ ao mesmo tempo em português . A descrição, portanto, é importante para saber o significado exato e ter uma tradução correta. 
 
-<div class="alert alert-warning">
-O arquivo `context.json` é obrigatório e precisa conter todas as chaves de traduções. 
-</div>
+>⚠️ O arquivo `context.json` é obrigatório e precisa conter todas as chaves de traduções.
 
 ### Migrando do MessagesBuilder 0.x
 
diff --git a/docs/tutorials/pt/how-to-use-the-index-report.md b/docs/tutorials/pt/how-to-use-the-index-report.md
index 28c806eb8..39c1cd159 100644
--- a/docs/tutorials/pt/how-to-use-the-index-report.md
+++ b/docs/tutorials/pt/how-to-use-the-index-report.md
@@ -19,9 +19,7 @@ O **Relatório de Indexação** é o relatório que indica o status de indexaç
 
 ![RelatorioIndexação](https://images.contentful.com/alneenqid6w5/6Y212qGxIAU4KWuWw8Uou2/306e536e7b5196abf04513915550a9f6/RelatorioIndexa_C3_A7_C3_A3o.png)
 
-<div class="alert alert-info">
-<strong>Nota:</strong> Para mais informações, acesse <a href="http://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao">Entendendo o funcionamento da indexação.</a>
-</div>
+>ℹ️ **Nota:** Para mais informações, acesse [Entendendo o funcionamento da indexação.](http://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao)
 
 ## Como acessar o relatório de indexação
 
diff --git a/docs/tutorials/pt/how-to-use-the-meta-tags-control.md b/docs/tutorials/pt/how-to-use-the-meta-tags-control.md
index f7f2db61f..0a32262ff 100644
--- a/docs/tutorials/pt/how-to-use-the-meta-tags-control.md
+++ b/docs/tutorials/pt/how-to-use-the-meta-tags-control.md
@@ -54,6 +54,4 @@ Veja abaixo um exemplo de meta tags inseridas pelo controle `<vtex:metaTags/>` p
 <link rel="canonical" href="http://lojadobreno.vtexcommercestable.com.br/escalada">
 ```
 
-<div class="alert alert-info">
-Caso não queira usar a tag canonical (&lt;link rel="canonical"&gt;), você pode desabilitá-la por meio de um <a href="https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag">controle específico para isso</a>.
-</div>
+>ℹ️ Caso não queira usar a tag canonical (&lt;link rel="canonical"&gt;), você pode desabilitá-la por meio de um [controle específico para isso](https://developers.vtex.com/docs/guides/control-to-disable-the-canonical-tag).
diff --git a/docs/tutorials/pt/how-to-use-the-search-result-control.md b/docs/tutorials/pt/how-to-use-the-search-result-control.md
index dfa97bbd6..470095ee3 100644
--- a/docs/tutorials/pt/how-to-use-the-search-result-control.md
+++ b/docs/tutorials/pt/how-to-use-the-search-result-control.md
@@ -17,9 +17,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 O controle `<vtex.cmc:searchResult/>` renderiza uma vitrine com os produtos retornados por uma busca do usuário.
 
-<div class="alert alert-info">
-Esse controle funciona <b>apenas em páginas com contexto de busca</b>, ou seja, páginas onde os resultados exibidos foram trazidos por uma busca do usuário.
-</div>
+>ℹ️ Esse controle funciona **apenas em páginas com contexto de busca**, ou seja, páginas onde os resultados exibidos foram trazidos por uma busca do usuário.
 
 Quando o usuário faz uma busca na loja, o sistema da VTEX tenta trazer resultados de acordo com uma ordem de prioridade de filtros. Entenda como funciona a busca no artigo [Como funciona a busca da VTEX](/pt/tutorial/como-funciona-a-busca-da-vtex).
 
diff --git a/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md b/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md
index ea5ea4b91..6cf23b492 100644
--- a/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md
+++ b/docs/tutorials/pt/how-to-use-the-unavailable-product-class.md
@@ -43,9 +43,7 @@ Você pode customizar seu arquivo CSS para que essa classe exiba, por exemplo, o
 
 ## Determinar a qual especificação será atribuída a classe
 
-<div class="alert alert-warning">
-A classe de produto indisponível apenas é atribuída à especificação que aparece <b>por último</b> na lista de especificações do SKU, no módulo Catalog.
-</div>
+>⚠️ A classe de produto indisponível apenas é atribuída à especificação que aparece **por último** na lista de especificações do SKU, no módulo Catalog.
 
 Por exemplo, se a especificação `Tamanho` aparecer por último, ela receberá a classe de indisponibilidade.
 
diff --git a/docs/tutorials/pt/how-to-view-the-orders-details.md b/docs/tutorials/pt/how-to-view-the-orders-details.md
index b95500cf0..0c6f6d822 100644
--- a/docs/tutorials/pt/how-to-view-the-orders-details.md
+++ b/docs/tutorials/pt/how-to-view-the-orders-details.md
@@ -38,9 +38,7 @@ Na caixa da esquerda, estão concentradas as informações relacionadas ao meio
 
 Para tansações com cartão de crédito, cada pagamento (podem ser dois cartões) possui um ID gerado pela VTEX. A adquirente também cria uma, chamada Transaction ID (TID). A TID é específica para cada cartão, ou seja, se um pedido é pago com dois cartões, haverá duas transações e, logo, duas TIDs.
 
-<div class="alert alert-warning">
-Em transações que não possuem TID, pode ser interpretado que a adquirente não processou o pagamento, isto é, que não possui TID. Ocasionalmente isso pode gerar um erro, e uma forma rápida de identificá-lo é verificar se existe uma TID.
-</div>
+>⚠️ Em transações que não possuem TID, pode ser interpretado que a adquirente não processou o pagamento, isto é, que não possui TID. Ocasionalmente isso pode gerar um erro, e uma forma rápida de identificá-lo é verificar se existe uma TID.
 
 A parte mais importante dessa tela é o log de interações da transação. Aqui fica registrada toda a comunicação da VTEX com os afiliados cadastrados – antifraude, gateways e adquirentes –, inclusive mensagens de sucesso e erro, com seus respectivos códigos.
 
diff --git a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
index 7da10893d..8d833a66f 100644
--- a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
@@ -50,8 +50,6 @@ Ocorre que as condições ofertadas não estarão presentes em qualquer página:
 
 Sendo assim, não é possível, por exemplo, condicionar produtos específicos a layouts diferentes através de uma coleção. Nesse cenário é necessário cadastrá-los com a condição de produto.
 
-<div class="alert alert-info">
-De acordo com as condições configuradas, existe uma ordem de prioridade estabelecida para a aplicabilidade do template. A ordenação é, caso exista, template de produto, de categoria e, por último, de marca. Dessa forma, um template condicionado para determinado produto se sobrepõe aquele condicionado à categoria na qual este produto está contido e assim sucessivamente. 
-</div>
+>ℹ️ De acordo com as condições configuradas, existe uma ordem de prioridade estabelecida para a aplicabilidade do template. A ordenação é, caso exista, template de produto, de categoria e, por último, de marca. Dessa forma, um template condicionado para determinado produto se sobrepõe aquele condicionado à categoria na qual este produto está contido e assim sucessivamente.
 
 Em caso de dúvidas nessa configuração, recomendamos que use o "lid": [Teste de Layout](/pt/faq/como-validar-um-layout-antes-de-ir-para-producao)
diff --git a/docs/tutorials/pt/image-compression.md b/docs/tutorials/pt/image-compression.md
index e84c57b08..cfc1e9ec4 100644
--- a/docs/tutorials/pt/image-compression.md
+++ b/docs/tutorials/pt/image-compression.md
@@ -32,9 +32,7 @@ Fazemos uma conversão automática para o formato [WebP](https://developers.goog
 
 O uso do WebP pode gerar um ganho de 1 a 2 segundos no tempo de carregamento das páginas, variando conforme o layout. Confira a seguir como funciona a otimização de imagens em cada formato.
 
-<div class="alert alert-info">
-  <p>Navegadores que ainda não são <a href="https://developers.google.com/speed/webp/faq?hl=pt-br#which_web_browsers_natively_support_webp">compatíveis com o formato WebP</a> e serviços como integrações e marketplaces sempre recebem imagens não convertidas, em qualquer formato. Arquivos no formato GIF não passam pela conversão para WebP.</p>
-</div>
+>ℹ️ Navegadores que ainda não são [compatíveis com o formato WebP](https://developers.google.com/speed/webp/faq?hl=pt-br#which_web_browsers_natively_support_webp) e serviços como integrações e marketplaces sempre recebem imagens não convertidas, em qualquer formato. Arquivos no formato GIF não passam pela conversão para WebP.
 
 ## PNG
 
diff --git a/docs/tutorials/pt/image-widget.md b/docs/tutorials/pt/image-widget.md
index d67ea39ca..9da8ee8f2 100644
--- a/docs/tutorials/pt/image-widget.md
+++ b/docs/tutorials/pt/image-widget.md
@@ -42,13 +42,9 @@ Agora que você sabe como acessar o Image Widget, verifique o que você pode faz
 
 Depois de [acessar Image Widget](#acessando-image-widget) e com ele aberto você consegue adicionar imagens:
 
-<div class="alert alert-warning">
-Ao adicionar novas imagens no modal Image Widget usando um <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace">development workspace</a>, as configurações performadas serão salvas diretamente em master, ou seja, imediatamente refletirão no modal da sua loja.
-</div>
+>⚠️ Ao adicionar novas imagens no modal Image Widget usando um [development workspace](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-workspace), as configurações performadas serão salvas diretamente em master, ou seja, imediatamente refletirão no modal da sua loja.
 <br>
-<div class="alert alert-warning">
-  O tamanho máximo que o Image Widget suporta é 4 MB por arquivo.
-</div>
+>⚠️ O tamanho máximo que o Image Widget suporta é 4 MB por arquivo.
 
 1. Clique em `Adicionar novo.`
 2. Escolha a imagem que deseja adicionar e clique em `Abrir.`
@@ -86,7 +82,5 @@ No bloco que você deseja substituir uma imagem:
 
 Para remover uma imagem do bloco desejado, clique em `Mais ações` na miniatura de uma imagem e selecione __remover__. Após esse procedimento, a imagem não estará mais visível no bloco.
 
-<div class="alert alert-warning">
-  Quando você remove uma imagem, isso não significa que ela seja excluída do repositório. Para isso, verifique a seção <a href="#recursos-dentro-do-image-widget">Recursos dentro do Image Widget</a>.
-</div>
+>⚠️ Quando você remove uma imagem, isso não significa que ela seja excluída do repositório. Para isso, verifique a seção [Recursos dentro do Image Widget](#recursos-dentro-do-image-widget).
 
diff --git a/docs/tutorials/pt/import-customer-data-brazil.md b/docs/tutorials/pt/import-customer-data-brazil.md
index d835eb732..611ef35d9 100644
--- a/docs/tutorials/pt/import-customer-data-brazil.md
+++ b/docs/tutorials/pt/import-customer-data-brazil.md
@@ -17,10 +17,9 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 A importação de dados de clientes deve ser feita no Master Data. Para o envio de dados, use o artigo [Importando dados no Master Data](/pt/tutorial/importando-dados-no-master-data).
 
-<div class="alert alert-danger">
-<p>Este artigo se refere aos campos do Master Data v1 especificamente para as lojas do <strong>Brasil</strong>.</p>
-<p>Você também pode conferir o guia sobre como <a href="https://developers.vtex.com/docs/guides/import-customer-data">importar dados de clientes programaticamente com a API do Master Data v2</a>.</p>
-</div>
+>❗ Este artigo se refere aos campos do Master Data v1 especificamente para as lojas do **Brasil**.
+>
+> Você também pode conferir o guia sobre como [importar dados de clientes programaticamente com a API do Master Data v2](https://developers.vtex.com/docs/guides/import-customer-data).
 
 O checkout trabalha com os dados das entidades CL (cliente) e AD (endereço).
 
diff --git a/docs/tutorials/pt/importing-data-into-master-data.md b/docs/tutorials/pt/importing-data-into-master-data.md
index 36ba9d5d3..3460ad0f9 100644
--- a/docs/tutorials/pt/importing-data-into-master-data.md
+++ b/docs/tutorials/pt/importing-data-into-master-data.md
@@ -30,17 +30,13 @@ A melhor maneira de obter a planilha de importação é [realizando a exportaç
 
 Deixe o valor da coluna id vazio e será criado um novo registro.
 
-<div class="alert alert-warning">
-Ao inserir os dados na planilha, certifique-se que o formato dos valores nas células corresponde ao formato esperado pela respectiva coluna. Exemplos de formatos são número, texto ou data.
-</div>
+>⚠️ Ao inserir os dados na planilha, certifique-se que o formato dos valores nas células corresponde ao formato esperado pela respectiva coluna. Exemplos de formatos são número, texto ou data.
 
 ## Como subir a planilha
 
 Após a exportação e edição da planilha exportada, é hora de realizar a importação dos dados. Para isso, siga os pontos abaixo para realizar esta operação.
 
-<div class="alert alert-warning">
-Mantenha o mesmo formato da planilha (xls) para realizar a importação com sucesso.
-</div>
+>⚠️ Mantenha o mesmo formato da planilha (xls) para realizar a importação com sucesso.
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Storefront** > **Master Data.**
 2. Clique na aba **Aplicações.**
diff --git a/docs/tutorials/pt/importing-images-from-a-spreadsheet.md b/docs/tutorials/pt/importing-images-from-a-spreadsheet.md
index 0277dba94..9991458a8 100644
--- a/docs/tutorials/pt/importing-images-from-a-spreadsheet.md
+++ b/docs/tutorials/pt/importing-images-from-a-spreadsheet.md
@@ -35,10 +35,9 @@ O tempo até a conclusão do processo depende do tamanho do arquivo. Caso a plan
 
 Por fim, os produtos das linhas da planilha cujas imagens forem processadas com sucesso serão colocados na fila de indexação.
 
-<div class="alert alert-danger">
-<p>Sempre que uma planilha com a informação de imagens for importada, o sistema fará o upload de uma nova imagem para o SKU. Fique atento(a) a possíveis duplicações.</p>
-<p>Se uma planilha com informações enviadas anteriormente para a VTEX for importada uma segunda vez, a importação não irá sobrescrever a imagem antiga: a imagem será <strong>duplicada</strong> no cadastro do SKU.</p>
-</div>
+>❗ Sempre que uma planilha com a informação de imagens for importada, o sistema fará o upload de uma nova imagem para o SKU. Fique atento(a) a possíveis duplicações.
+>
+> Se uma planilha com informações enviadas anteriormente para a VTEX for importada uma segunda vez, a importação não irá sobrescrever a imagem antiga: a imagem será **duplicada** no cadastro do SKU.
 
 ## Como preencher a planilha para importar imagens
 
@@ -53,9 +52,7 @@ A seguir, explicamos o preenchimento de cada campo da planilha de importação d
 
 ### URL
 
-<div class="alert alert-info">
-<p>Este campo é obrigatório. Não é permitido o uso de caracteres especiais, pontos no nome da imagem ou acentos.</p>
-</div>
+>ℹ️ Este campo é obrigatório. Não é permitido o uso de caracteres especiais, pontos no nome da imagem ou acentos.
 
 Este campo precisa ser preenchido com a URL da imagem a ser associada ao SKU, que deve estar pública e hospedada em um servidor FTP, de onde se origina o link da imagem. A URL deve obrigatoriamente iniciar com o identificador de protocolo HTTP (`http://`) e terminar com a extensão do arquivo (`.jpg`, `.png` ou `.gif`). Exemplo: `http://www.exemploimagem.com.br/imagem03/teste01/exemplo15.jpg`.
 
@@ -65,15 +62,11 @@ Você não precisa ter um servidor FTP próprio para enviar as URLs das imagens.
 
 Além disso, para verificar se as URLs estão corretas, você pode utilizar um serviço externo, o qual verifica se estas são válidas.
 
-<div class="alert alert-warning">
-  <p>Recomendamos que cada imagem não ultrapasse 3000 KB (3 MB).</p>
-</div>
+>⚠️ Recomendamos que cada imagem não ultrapasse 3000 KB (3 MB).
 
 ### NomeImagem
 
-<div class="alert alert-info">
-<p>Este campo é obrigatório. Não é permitido o uso de caracteres especiais, acentos e espaços em branco.</p>
-</div>
+>ℹ️ Este campo é obrigatório. Não é permitido o uso de caracteres especiais, acentos e espaços em branco.
 
 O nome da imagem é o que vem depois da última `/` na URL da imagem, incluindo a extensão do arquivo. Portanto, esse campo precisa ser preenchido com o nome e a extensão do arquivo (`.jpg`, `.png` ou `.gif`). Exemplo: `exemplo15.jpg`.
 
@@ -81,27 +74,23 @@ Esse nome será relacionado à imagem no gerenciador de arquivos do Portal CMS L
 
 ### TextoImagem
 
-<div class="alert alert-info">
-<p>Não é permitido o uso de caracteres especiais e acentos neste campo.</p>
-<p>Não é permitido utilizar o mesmo valor no campo <strong>Label</strong> e no campo <strong>TextoImagem</strong>.</p>
-</div>
+>ℹ️ Não é permitido o uso de caracteres especiais e acentos neste campo.
+>
+> Não é permitido utilizar o mesmo valor no campo **Label** e no campo **TextoImagem**.
 
 O __TextoImagem__ precisa ser preenchido com o texto que será associado à sua imagem. Ele ficará registrado no cadastro do SKU na aba __Imagens__, no campo __Texto__.
 
 ### Label
 
-<div class="alert alert-info">
-<p>Este campo é obrigatório. Não é permitido o uso de caracteres especiais, acentos e espaços em branco.</p>
-<p>Não é permitido utilizar o mesmo valor no campo <strong>Label</strong> e no campo <strong>TextoImagem</strong>.</p>
-</div>
+>ℹ️ Este campo é obrigatório. Não é permitido o uso de caracteres especiais, acentos e espaços em branco.
+>
+> Não é permitido utilizar o mesmo valor no campo **Label** e no campo **TextoImagem**.
 
 __Label__ é a “etiqueta” usada para facilitar na organização do template das páginas do seu site, através do referenciamento do valor preenchido nesta. Exemplos: frontal, lateral, superior.
 
 ### IdSku
 
-<div class="alert alert-info">
-<p>O preenchimento deste campo é obrigatório. A ID informada precisa ser correspondente à ID de um SKU já existente no <strong>Catálogo</strong>.</p>
-</div>
+>ℹ️ O preenchimento deste campo é obrigatório. A ID informada precisa ser correspondente à ID de um SKU já existente no **Catálogo**.
 
 O ID do SKU é o código que identifica o SKU que será associado à imagem. É possível obter este código através da exportação de __Produtos e SKUs__ — leia o artigo [Como exportar planilha de produtos
 ](https://help.vtex.com/pt/tutorial/como-exportar-planilha-de-produtos--2sIroGeqZqaN3NAvaSGwWV) para mais informações.
diff --git a/docs/tutorials/pt/importing-the-shipping-spreadsheet.md b/docs/tutorials/pt/importing-the-shipping-spreadsheet.md
index fd1385209..6771f4a17 100644
--- a/docs/tutorials/pt/importing-the-shipping-spreadsheet.md
+++ b/docs/tutorials/pt/importing-the-shipping-spreadsheet.md
@@ -15,10 +15,8 @@ legacySlug: importar-planilha-de-frete
 subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 ---
 
-<div class="alert alert-info">
-Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
-<a href="https://help.vtex.com/pt/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envio</a>.
-</div> 
+>ℹ️ Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
+> [estratégia de envio](https://help.vtex.com/pt/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl). 
 
 
 Antes de fazer a importação, é importante ter a planilha no modelo VTEX, ou seja, __idêntica à nossa Planilha Modelo__, inclusive na formatação das células, com o cabeçalho e formato _.xls_ (Excel 97-2003). Para obter o modelo, clique no link __Download da Planilha Modelo__, que fica dentro de configurações da transportadora.
@@ -32,17 +30,11 @@ Antes de fazer a importação, é importante ter a planilha no modelo VTEX, ou s
 
 Depois disso, será possível visualizar uma tarja laranja sobre a transportadora que teve a inclusão da tabela de frete, com a informação __Em processamento__. O tempo para a planilha ser consumida dependerá da quantidade de linhas contidas nela.
 
-<div class="alert alert-warning">
-Lembre-se que cada nova importação sobrescreve as informações que foram importadas anteriormente.
-</div>
+>⚠️ Lembre-se que cada nova importação sobrescreve as informações que foram importadas anteriormente.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> caso as 65.536 linhas da versão <em>.xls</em> não sejam suficiente para o cadastro de todos os valores de frete da transportadora, será necessário criar uma nova aba dentro do arquivo, com o mesmo cabeçalho para continuar preenchendo as informações.
-</div>
+>⚠️ **OBS:** caso as 65.536 linhas da versão *.xls* não sejam suficiente para o cadastro de todos os valores de frete da transportadora, será necessário criar uma nova aba dentro do arquivo, com o mesmo cabeçalho para continuar preenchendo as informações.
 
-<div class="alert alert-warning">
-<strong>OBS2:</strong>Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato <strong>.zip</strong>. Esse arquivo .zip também deve ter menos de 10 MB para o upload funcionar. Se, ainda assim, o arquivo exceder o limite, recomendamos dividir em mais transportadoras.
-</div>
+>⚠️ **OBS2:**Caso a planilha tenha mais de 10 MB, será necessário compactá-la no formato **.zip**. Esse arquivo .zip também deve ter menos de 10 MB para o upload funcionar. Se, ainda assim, o arquivo exceder o limite, recomendamos dividir em mais transportadoras.
 
 ## Gerar planilha automaticamente para os Correios
 
diff --git a/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md b/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md
index 533d09012..cae2e0b2f 100644
--- a/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md
+++ b/docs/tutorials/pt/including-order-variables-in-the-transactional-email-template.md
@@ -28,9 +28,7 @@ Estas variáveis são propriedades do JSON que consta no campo __JSON Data__ e p
 
 ### Exemplo
 
-<div class="alert alert-warning">
-Os exemplos de JSON Data apenas aparecerão nos templates quando você concluir a ação desejada em sua loja. Caso não tenha transacionado um pedido, uma recorrência ou qualquer outra ação, o JSON Data aparecerá em branco.
-</div>
+>⚠️ Os exemplos de JSON Data apenas aparecerão nos templates quando você concluir a ação desejada em sua loja. Caso não tenha transacionado um pedido, uma recorrência ou qualquer outra ação, o JSON Data aparecerá em branco.
 
 Digamos que você queira inserir o nome da transportadora no e-mail de pedido enviado.
 
diff --git a/docs/tutorials/pt/indexes-in-master-data.md b/docs/tutorials/pt/indexes-in-master-data.md
index d1ed2835c..fa6296dc0 100644
--- a/docs/tutorials/pt/indexes-in-master-data.md
+++ b/docs/tutorials/pt/indexes-in-master-data.md
@@ -63,9 +63,7 @@ Com isso, não será possível inserir um nome que já tenha sido cadastrado em
 
 No exemplo acima, como já existe um registro com o **Nome** igual a **Maria**, não é possível cadastrar outro com o mesmo valor.
 
-<div class="alert alert-warning">
-  <p>Use a opção <strong>Valores Únicos</strong> com cautela. Se um valor que você deseja permitir se repetir for configurado como único, o sistema bloqueará a inserção de registros duplicados, impedindo seu cadastro.</p>
-</div>
+>⚠️ Use a opção **Valores Únicos** com cautela. Se um valor que você deseja permitir se repetir for configurado como único, o sistema bloqueará a inserção de registros duplicados, impedindo seu cadastro.
 
 #### Vários campos no índice
 
@@ -81,6 +79,4 @@ Nesse caso, o valor do **Nome** pode se repetir ou o valor do **Documento** pode
 
 No exemplo acima, já existe um registro com o **Nome** igual a **Maria**. É possível incluir outro registro com o mesmo **Nome**, desde que o valor do **Documento** seja diferente.
 
-<div class="alert alert-warning">
-  <p>Se a mesma combinação de valores se repetir, o registro não será salvo. Utilize a opção <strong>Valores únicos</strong> somente quando não existir a possibilidade de um conjunto de valores se repetir em registros diferentes.</p>
-</div>
+>⚠️ Se a mesma combinação de valores se repetir, o registro não será salvo. Utilize a opção **Valores únicos** somente quando não existir a possibilidade de um conjunto de valores se repetir em registros diferentes.
diff --git a/docs/tutorials/pt/integrate-with-carrefour.md b/docs/tutorials/pt/integrate-with-carrefour.md
index 8268d00ef..f4e728e6c 100644
--- a/docs/tutorials/pt/integrate-with-carrefour.md
+++ b/docs/tutorials/pt/integrate-with-carrefour.md
@@ -57,9 +57,7 @@ _`Ex:` imagine que você usa a transportadora XPTO, que entrega mais devagar, po
 
 _`Ex:` imagine que você usa a transportadora XPTO, que entrega mais devagar, porém é mais barata. Seu Tipo de Transportadora no painel logístico da VTEX se chama "Agendada". Então, você deve escrever no campo o nome __Agendada__. Lembre-se que a palavra deve ser exatamente igual à cadastrada na logística._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> é necessário preencher pelo menos um dos campos do mapeamento de SLA. Caso nenhum deles seja prenchido, <strong>não</strong> será possível simular o frete na VTEX e, consequentemente, os pedidos feitos no Carrefour não serão integrados. Além disso, também não será possível salvar o cadastro da integração sem que algum dos campos esteja preenchido.
-</div>
+>⚠️ **OBS:** é necessário preencher pelo menos um dos campos do mapeamento de SLA. Caso nenhum deles seja prenchido, **não** será possível simular o frete na VTEX e, consequentemente, os pedidos feitos no Carrefour não serão integrados. Além disso, também não será possível salvar o cadastro da integração sem que algum dos campos esteja preenchido.
 
 _Legenda:_<br />
 `*` Campos obrigatórios.<br />
diff --git a/docs/tutorials/pt/integrating-with-amazon.md b/docs/tutorials/pt/integrating-with-amazon.md
index ac6ab902c..3554bb7a7 100644
--- a/docs/tutorials/pt/integrating-with-amazon.md
+++ b/docs/tutorials/pt/integrating-with-amazon.md
@@ -15,21 +15,15 @@ legacySlug: integrar-com-a-amazon
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-warning"> 
-Esta integração é válida apenas para as categorias <b>Atividades ao Ar Livre<b>, <b>Bagagens</b> <b>Computadores</b>, <b>Câmera e Foto</b>, <b>Casa e Jardim</b>, <b>Computadores</b>, <b>Eletrônicos</b>, <b>Esportes</b>, <b>Jóias</b>, <b>Livros</b>, <b>Materiais de Escritório</b>, <b>Ferragens</b>, <b>Games</b>, <b>Sapatos</b> e <b>Roupas</b>.
-</div>
+>⚠️ Esta integração é válida apenas para as categorias **Atividades ao Ar Livre<b>, <b>Bagagens** **Computadores**, **Câmera e Foto**, **Casa e Jardim**, **Computadores**, **Eletrônicos**, **Esportes**, **Jóias**, **Livros**, **Materiais de Escritório**, **Ferragens**, **Games**, **Sapatos** e **Roupas**.
 
-<div class="alert alert-warning">
-Esta integração está disponível para Brasil, México, Estados Unidos, Canadá e Europa.
-</div>
+>⚠️ Esta integração está disponível para Brasil, México, Estados Unidos, Canadá e Europa.
 
 ## Autorizar a VTEX no painel da Amazon
 
 Para realizar a integração com o Marketplace da Amazon, é necessário que o lojista dê, através da sua conta Amazon Seller Central pelo mercado dos Estados Unidos (_www.amazon.com_), a autorização para VTEX. 
 
-<div class="alert alert-warning">
-No painel da Amazon, sempre verifique se você ainda está conectado ao mercado dos Estados Unidos (www.amazon.com). Caso não esteja, você receberá uma mensagem de erro durante o processo de autorização e será necessária a troca do mercado para EUA(www.amazon.com) novamente.
-</div>
+>⚠️ No painel da Amazon, sempre verifique se você ainda está conectado ao mercado dos Estados Unidos (www.amazon.com). Caso não esteja, você receberá uma mensagem de erro durante o processo de autorização e será necessária a troca do mercado para EUA(www.amazon.com) novamente.
 
 Quando na etapa de cadastro de developer da Amazon, preencha os campos da seguinte forma:
 - Developer’s Name: VTEX  
@@ -47,9 +41,7 @@ Antes de configurar a integração, você deve verificar os seguintes pontos:
 
  - __Tempo de Custo:__ na Amazon existe o campo `fulfillment latency`, que é __usado para configurar o tempo de preparo da entrega de determinado produto__. Para preenche-lo massivamente via integração, é necessário preencher o campo [Tempo de Custo](http://help.vtex.com/pt/tutorial/como-cadastrar-doca) no cadastro da doca associada à política comercial usada para a Amazon. Caso este campo não esteja preenchido, a Amazon usará o valor *default* deles (2 dias).
   
-<div class="alert alert-warning">
-OBS: é importante preencher este campo pois, se a sua loja não estiver perfomando conforme o tempo de preparo configurado, ou seja, atrasando na entrega, a sua conta pode ser bloqueada.
-</div>
+>⚠️ OBS: é importante preencher este campo pois, se a sua loja não estiver perfomando conforme o tempo de preparo configurado, ou seja, atrasando na entrega, a sua conta pode ser bloqueada.
 
 ## Configuração da integração
   
diff --git a/docs/tutorials/pt/integrating-with-buscape-bp.md b/docs/tutorials/pt/integrating-with-buscape-bp.md
index 8696e79f9..3103ca784 100644
--- a/docs/tutorials/pt/integrating-with-buscape-bp.md
+++ b/docs/tutorials/pt/integrating-with-buscape-bp.md
@@ -32,9 +32,7 @@ Alguns passos são essenciais para iniciarmos as configurações.
 4. Preencha os campos conforme detalhado abaixo;
 5. Clique no botão **Salvar Configuração**. Ele estará ativo somente se todas as configurações estiverem corretas.
 
-<div class="alert alert-warning">
-Atenção! Para a política comercial é preciso que pelo menos um boleto ou um cartão de crédito seja configurado. Ou seja, é necessário que sejam configurados os meios de pagamento para o sales channel específico.
-</div>
+>⚠️ Atenção! Para a política comercial é preciso que pelo menos um boleto ou um cartão de crédito seja configurado. Ou seja, é necessário que sejam configurados os meios de pagamento para o sales channel específico.
 
 ### Campos
 
diff --git a/docs/tutorials/pt/integrating-with-enjoei.md b/docs/tutorials/pt/integrating-with-enjoei.md
index f2025a4b2..6c39e9b3a 100644
--- a/docs/tutorials/pt/integrating-with-enjoei.md
+++ b/docs/tutorials/pt/integrating-with-enjoei.md
@@ -45,9 +45,7 @@ Caso seja do seu interesse ter configurações específicas para vender no Enjoe
 
 A [contratação de políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) para integrar com conectores certificados, certificados nativos ou outras lojas VTEX é isenta de taxas. Saiba mais sobre quem são esses parceiros em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/integrando-com-marketplace--tutorials_402).
 
-<div class="alert alert-warning">
-Os produtos que você deseja enviar para o Enjoei devem estar <a href="https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb">associados à política comercial</a> definida. Caso contrário, eles não serão integrados. 
-</div>
+>⚠️ Os produtos que você deseja enviar para o Enjoei devem estar [associados à política comercial](https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb) definida. Caso contrário, eles não serão integrados.
 
 ### Definir a Estratégia de Envio
 
@@ -73,9 +71,7 @@ Para configurar uma nova chave, siga os passos abaixo:
 4. Preencha com um nome para o novo access key.
 5. Clique em `Gerar novos secrets`.
 
-<div class="alert alert-warning">
-O secret gerado, também chamado de appToken, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
-</div>
+>⚠️ O secret gerado, também chamado de appToken, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
 
 ### Criar perfil de acesso 
 
@@ -143,6 +139,4 @@ Depois de concluir o preenchimento do formulário com as informações solicitad
 
 Uma vez que você tenha concluído todas as etapas anteriores, sua loja será integrada na plataforma do Enjoei e a integração será concluída pelo parceiro.
 
-<div class="alert alert-info">
-Você também pode conferir as orientações para integração fornecidas pelo Enjoei na documentação <a href="https://drive.google.com/uc?export=download&id=1bOR_Kc37kRXWWy8b68tShnb2TNbW9BUp">Configuração VTEX</a>.
-</div>
+>ℹ️ Você também pode conferir as orientações para integração fornecidas pelo Enjoei na documentação [Configuração VTEX](https://drive.google.com/uc?export=download&id=1bOR_Kc37kRXWWy8b68tShnb2TNbW9BUp).
diff --git a/docs/tutorials/pt/integrating-with-loopi.md b/docs/tutorials/pt/integrating-with-loopi.md
index a02473778..f1e817c18 100644
--- a/docs/tutorials/pt/integrating-with-loopi.md
+++ b/docs/tutorials/pt/integrating-with-loopi.md
@@ -36,9 +36,7 @@ Feito isso, o próximo passo é informar à Loopi os seguintes dados:
 
 É a partir do fornecimento destes dados que a Loopi realiza determinadas configurações no próprio ambiente. Você receberá um email da Loopi confirmando que as configurações foram concluídas, além de ser informado sobre credenciais e próximos passos relacionados ao ambiente do parceiro.
 
-<div class="alert alert-danger">
-Se as informações mencionadas não forem concedidas à Loopi, os produtos não serão cadastrados em etapas posteriores.
-</div>
+>❗ Se as informações mencionadas não forem concedidas à Loopi, os produtos não serão cadastrados em etapas posteriores.
 
 ## Visão geral da integração
 
@@ -70,9 +68,7 @@ A seguir, algumas considerações importantes sobre condições para o cadastro
 - **Regra de preço:** não são aceitos preços diferentes para variações de tamanho de um mesmo produto, ou seja, SKUs com tamanhos diferentes devem ter o mesmo preço. Por exemplo, não é aceito o cadastro de um produto com um preço para uma camiseta tamanho P, e outro preço para o produto no tamanho M. 
 - **Fotos:** todo produto deve ter uma imagem cadastrada no seu Admin VTEX.
 
-<div class="alert alert-danger">
-O descumprimento de qualquer das exigências mencionadas impossibilita o cadastramento do produto.
-</div>
+>❗ O descumprimento de qualquer das exigências mencionadas impossibilita o cadastramento do produto.
 
 ### Agrupamento de produtos na Loopi
 
@@ -106,9 +102,7 @@ A desativação de produtos e SKUs no marketplace pode ser feita pela exclusão
 
 Na Loopi, a desativação do último SKU de um produto ocasiona automaticamente a exclusão daquele produto da base de dados. Porém, quando existem notificações de criação de SKUs para um produto desativado, esse produto é automaticamente reativado na Loopi.
 
-<div class="alert alert-warning">
-Só é possível atualizar produtos e SKUs na base de dados da Loopi quando a configuração de um SKU está marcada como <i>ativa</i>.
-</div>
+>⚠️ Só é possível atualizar produtos e SKUs na base de dados da Loopi quando a configuração de um SKU está marcada como <i>ativa</i>.
 
 ### Status de pedidos na Loopi
 
@@ -153,9 +147,7 @@ A [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-poli
 
 Caso seja do seu interesse ter configurações específicas para vender na Loopi, você pode [configurar uma política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/). Não existe cobrança para a contratação de políticas comerciais adicionais para integrar lojas VTEX com conectores nativos, conectores certificados ou outras lojas VTEX. Saiba mais em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/integrando-com-marketplace--tutorials_402).
 
-<div class="alert alert-warning">
-Os produtos que você deseja enviar para a Loopi devem estar <a href="https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb">associados à política comercial</a> definida. Caso contrário, eles não serão integrados.
-</div>
+>⚠️ Os produtos que você deseja enviar para a Loopi devem estar [associados à política comercial](https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb) definida. Caso contrário, eles não serão integrados.
 
 ### Definir estratégia de envio
 
@@ -199,9 +191,7 @@ Para prosseguir com a integração, siga os passos abaixo:
 
 Por padrão, não é necessário se ocupar dos campos **ID do afiliado** e **Endpoint de notificação**, que são gerados de forma automática e aparecem desabilitados para edição. No entanto, caso deseje editar o **ID do afiliado**, clique sobre o ícone <i class="fas fa-cog"></i> engrenagem. Isso fará com que você seja redirecionado para a página de edição de códigos de identificação de [afiliados](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0).
 
-<div class="alert alert-danger">
-Conforme mencionado na etapa <a href="https://help.vtex.com/pt/tutorial/integracao-com-loopi--2wmap3hWksLxJ0IYe7nYFP#antes-de-comecar">Antes de começar</a>, para realizar a ativação da integração é necessário já ter concedido à Loopi alguns dados. É a partir disso que o parceiro realiza configurações que possibilitam a integração com a plataforma VTEX.
-</div>
+>❗ Conforme mencionado na etapa [Antes de começar](https://help.vtex.com/pt/tutorial/integracao-com-loopi--2wmap3hWksLxJ0IYe7nYFP#antes-de-comecar), para realizar a ativação da integração é necessário já ter concedido à Loopi alguns dados. É a partir disso que o parceiro realiza configurações que possibilitam a integração com a plataforma VTEX.
 
 ### Mapear categorias, especificações e atributos
 
diff --git a/docs/tutorials/pt/integrating-with-madeiramadeira.md b/docs/tutorials/pt/integrating-with-madeiramadeira.md
index 8c423a815..67e4dab32 100644
--- a/docs/tutorials/pt/integrating-with-madeiramadeira.md
+++ b/docs/tutorials/pt/integrating-with-madeiramadeira.md
@@ -43,9 +43,7 @@ Caso seja do seu interesse ter configurações específicas para vender na Madei
 
 A [contratação de políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) para integrar com conectores certificados, certificados nativos ou outras lojas VTEX é isenta de taxas. Saiba mais sobre quem são esses parceiros em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/integrando-com-marketplace--tutorials_402).
 
-<div class="alert alert-warning">
-Os produtos que você deseja enviar para a MadeiraMadeira devem estar <a href="https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb">associados à política comercial</a> definida. Caso contrário, eles não serão integrados. 
-</div>
+>⚠️ Os produtos que você deseja enviar para a MadeiraMadeira devem estar [associados à política comercial](https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb) definida. Caso contrário, eles não serão integrados.
 
 ### Definir a Estratégia de Envio
 
@@ -79,9 +77,7 @@ Para configurar uma nova chave, siga os passos abaixo:
 4. Preencha com um nome para o novo access key.
 5. Clique em `Gerar novos secrets`.
 
-<div class="alert alert-warning">
-O secret gerado, também chamado de appToken, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
-</div>
+>⚠️ O secret gerado, também chamado de appToken, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
 
 ### Criar perfil de acesso 
 
@@ -144,6 +140,4 @@ Depois de concluir o preenchimento do formulário com as informações solicitad
 
 Uma vez que você tenha concluído todas as etapas anteriores, sua loja será integrada na plataforma da MadeiraMadeira e a integração será concluída pelo parceiro.
 
-<div class="alert alert-info">
-Você também pode conferir as orientações para integração fornecidas pela MadeiraMadeira pela página <a href="https://madeiramadeira.zendesk.com/hc/pt-br/articles/360016223591-Integra%C3%A7%C3%A3o-via-Vtex-In%C3%ADcio">Integração via VTEX - Início</a>.
-</div>
+>ℹ️ Você também pode conferir as orientações para integração fornecidas pela MadeiraMadeira pela página [Integração via VTEX - Início](https://madeiramadeira.zendesk.com/hc/pt-br/articles/360016223591-Integra%C3%A7%C3%A3o-via-Vtex-In%C3%ADcio).
diff --git a/docs/tutorials/pt/integrating-with-magazine-luiza.md b/docs/tutorials/pt/integrating-with-magazine-luiza.md
index 4f9061f1b..3b0a8cc9b 100644
--- a/docs/tutorials/pt/integrating-with-magazine-luiza.md
+++ b/docs/tutorials/pt/integrating-with-magazine-luiza.md
@@ -26,8 +26,7 @@ A integração com a Magazine Luiza acontece através da IntegraCommerce, uma in
 
 Com essa integração, será possível __criar novas contas__ e também __migrar contas já existentes (em breve)__ na Magazine Luiza. O passo a passo abaixo se adequa aos dois casos.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> atualmente <strong>não é possível migrar contas antigas</strong>. Estamos trabalhando e, em breve, essa migração será feita automaticamente.</div>
+>⚠️ **OBS:** atualmente **não é possível migrar contas antigas**. Estamos trabalhando e, em breve, essa migração será feita automaticamente.
 
 
 ## Detalhamento dos campos
diff --git a/docs/tutorials/pt/integrating-with-mercado-livre.md b/docs/tutorials/pt/integrating-with-mercado-livre.md
index 8ad9fa4f1..37c7ed504 100644
--- a/docs/tutorials/pt/integrating-with-mercado-livre.md
+++ b/docs/tutorials/pt/integrating-with-mercado-livre.md
@@ -56,15 +56,11 @@ As etapas iniciais são essenciais para que as configurações sejam realizadas
 
 Caso deseje usar um formato diferente, ou até títulos diferentes dos que estão cadastrados no catálogo da VTEX, você tem a opção de [criar um campo de produto](/pt/tutorial/criando-um-campo-de-produto) de tipo _Texto Grande_ que deve ter o nome `meli_title`. Com esse campo preenchido, a integração vai priorizar o envio dos valores usados aqui ao invés do título original do produto/SKU.
 
-<div class="alert alert-danger">
-<strong>OBS:</strong> preste atenção às configurações na criação desse novo campo, para que as novas informações criadas <strong>não</strong> sejam exibidas no seu site.
-</div>
+>❗ **OBS:** preste atenção às configurações na criação desse novo campo, para que as novas informações criadas **não** sejam exibidas no seu site.
 
 &bull; __Descrição do produto__: esse campo indica como a descrição de seus produtos no catálogo da VTEX será enviada ao Mercado Livre. As opções são _plain/text_ ou _html_.
 
-<div class="alert alert-danger">
-<strong>OBS:</strong> apesar de existir a opção, descrições com HTML <strong>não são mais aceitas</strong> pelo Mercado Livre, sendo obrigatória a escolha da opção <em>plain/text</em>. Em breve, também descontinuaremos essa opção da interface. Veja na seção <strong>Configuração do Template</strong> as tags aceitas pelo Mercado Livre.
-</div>
+>❗ **OBS:** apesar de existir a opção, descrições com HTML **não são mais aceitas** pelo Mercado Livre, sendo obrigatória a escolha da opção *plain/text*. Em breve, também descontinuaremos essa opção da interface. Veja na seção **Configuração do Template** as tags aceitas pelo Mercado Livre.
 
 &bull; __Associar produtos aos pick-up points cadastrados__: marque essa flag se você deseja que suas configurações de Pontos de Retirada sejam refletidas no Mercado Livre. Vale lembrar que só estão elegíveis as configurações feitas na seção [Pontos de Retirada](/pt/tutorial/configurar-pontos-de-retirada-pickup-points) do módulo __Logistics__.
 
@@ -74,9 +70,7 @@ Caso deseje usar um formato diferente, ou até títulos diferentes dos que estã
 
 &bull; __Taxa de confiabilidade da categorização automática__: a integração dá a opção de categorizar automaticamente os seus anúncios através de uma __ferramenta do Mercado Livre__. Essa ferramenta depende de informações (como nome do produto e preço) e, se não consegue inferi-las corretamente, seu produto pode ser categorizado errado. Por isso, é necessário definir uma taxa de confiabilidade na configuração da integração. Ou seja, o produto só vai ser integrado se a taxa retornada pela ferramenta do Mercado Livre estiver acima da que você configurou. Preencha com a taxa que você deseja.
 
-<div class="alert alert-danger">
-<strong>OBS:</strong> a VTEX <strong>não</strong> recomenda fazer a categorização de maneira automática. Indicamos usar o mapeamento de planilha explicado <a href="http://help.vtex.com/pt/tutorial/mapeamento-de-categorias-e-variacoes#categorizacao">neste artigo</a>.
-</div>
+>❗ **OBS:** a VTEX **não** recomenda fazer a categorização de maneira automática. Indicamos usar o mapeamento de planilha explicado [neste artigo](http://help.vtex.com/pt/tutorial/mapeamento-de-categorias-e-variacoes#categorizacao).
 
 &bull; __Estoque mínimo__: como a comunicação entre os sistemas da VTEX e do Mercado Livre não atualiza algumas das informações em tempo real, o estoque exibido no marketplace pode ficar defasado em relação ao estoque real do produto na sua loja. Para que não ocorram vendas de produtos sem estoque, você deve preencher esse campo com um valor mínimo de estoque de segurança. Assim, quando o estoque no Mercado Livre chegar a esse valor, o anúncio será pausado para que a venda de um produto sem estoque não aconteça.
 
@@ -87,23 +81,17 @@ Caso deseje usar um formato diferente, ou até títulos diferentes dos que estã
   - __Mensagem de envio de tracking__: insira nesse campo a mensagem que você deseja enviar ao cliente __quando o pedido tiver sido enviado__ e a __URL de rastreio estiver disponível para consulta__. Vale destacar que a VTEX vai preencher automaticamente esse campo com a URL de rastreio logo ao lado da sua mensagem. Então, caso a URL não esteja disponível ainda, recomendamos faturar o pedido sem ela. Assim que a URL estiver disponível, é só inseri-la no pedido.
 >Ex: "Olá! Você já pode acompanhar o status da sua entrega através da URL a seguir: http://status.transportadora.com.br/tracking/nº-do-pedido"
 
-  <div class="alert alert-danger">
-<strong>OBS:</strong>caso a URL de rastreio não seja preenchida na fatura do pedido, essa mensagem <strong>não</strong> será enviada.
-  </div>
+  >❗ **OBS:**caso a URL de rastreio não seja preenchida na fatura do pedido, essa mensagem **não** será enviada.
 
   - __Mensagem de pedido entregue__: insira nesse campo a mensagem que você deseja enviar ao cliente __quando o pedido tiver sido entregue pela transportadora__.  
 
 &bull; __Atributos omitidos no template do produto__: veremos mais à frente que, na configuração do template para o Mercado Livre, você pode incluir os atributos do produto que deseja exibir. A configuração desse campo permite omitir atributos que você não deseja que apareçam no template do Mercado Livre.
 
-<div class="alert alert-warning">
-Os campos <code>Atualizar descrição do anúncio</code>, <code>Texto para avaliação automática do comprador</code> e <code>E-mail do afiliado</code> serão descontinuados na UI. Por essa razão, eles não precisam ser preenchidos. As APIs, no entanto, vão continuar ativas.
-</div>
+>⚠️ Os campos `Atualizar descrição do anúncio`, `Texto para avaliação automática do comprador` e `E-mail do afiliado` serão descontinuados na UI. Por essa razão, eles não precisam ser preenchidos. As APIs, no entanto, vão continuar ativas.
 
 ## Configuração do template
 
-<div class="alert alert-danger">
-Para as lojas do Brasil e da Argentina, <strong>o Mercado Livre não aceita customizações de template em HTML ou CSS</strong> (com exceção da tag &lt;br&gt; para quebras de linha). As tags de Iframes, Scripts, Forms, Inputs, Meta, Object e Embed não são permitidas para nenhum país.
-</div>
+>❗ Para as lojas do Brasil e da Argentina, **o Mercado Livre não aceita customizações de template em HTML ou CSS** (com exceção da tag &lt;br&gt; para quebras de linha). As tags de Iframes, Scripts, Forms, Inputs, Meta, Object e Embed não são permitidas para nenhum país.
 
 Para que seu produto fique disponível no Mercado Livre, é necessário configurar o template do anúncio em que ele será exibido. Para fazer isso, siga o passo a passo abaixo:
 
@@ -127,9 +115,7 @@ Caso deseje incluir todos os atributos e valores dos atributos no template, voc
 
 ``{{#each ATRIBUTOS}} {{NOME}} – {{VALOR}} <br> {{/each}}``
 
-<div class="alert alert-info">
-Caso deseje omitir algum atributo no template, você pode fazer isso na <strong>configuração da integração</strong>. Basta preencher o campo <strong>Atributos omitidos no template do produto</strong>, conforme explicado na seção <strong>Configurar o painel do Mercado Livre na VTEX</strong> da etapa anterior.
-</div>
+>ℹ️ Caso deseje omitir algum atributo no template, você pode fazer isso na **configuração da integração**. Basta preencher o campo **Atributos omitidos no template do produto**, conforme explicado na seção **Configurar o painel do Mercado Livre na VTEX** da etapa anterior.
 
 Feito isso, você concluiu a _segunda etapa_. Agora, vamos configurar a logística para as entregas de pedidos feitos no Mercado Livre.
 
@@ -171,9 +157,7 @@ No ME2, __há duas formas de o pedido ser entregue__. Essas formas de entrega __
 
 Nesse cenário, o Mercado Livre busca o pedido diretamente nos Centros de Distribuição da sua loja e realiza a entrega ao cliente final.
 
-<div class="alert alert-warning">
-Não recomendamos a utilização do tipo de entrega <strong>Entrega a combinar</strong>. Como pedidos fechados assim não oferecem a informação do endereço do destinatário, <strong>a integração com a VTEX não consegue ser realizada</strong>. Para que um pedido seja integrado corretamente, é necessário que ele tenha as informações de entrega. Por isso, recomendamos sempre a utilização do <strong>Mercado Envios</strong>.
-</div>
+>⚠️ Não recomendamos a utilização do tipo de entrega **Entrega a combinar**. Como pedidos fechados assim não oferecem a informação do endereço do destinatário, **a integração com a VTEX não consegue ser realizada**. Para que um pedido seja integrado corretamente, é necessário que ele tenha as informações de entrega. Por isso, recomendamos sempre a utilização do **Mercado Envios**.
 
 ### Convivência Logística
 
@@ -181,13 +165,9 @@ Visando melhorar a experiência logística com a integração do Mercado Livre,
 
 _`Ex:` sua loja vende eletrodomésticos. A entrega de itens grandes, como geladeiras e fogões, é feita por você (modalidade ME1). Mas você quer que o Mercado Livre entregue (modalidade ME2) itens menores, como torradeiras, liquidificadores, mixers etc._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> somente lojas que já são ME1 poderão ter ME2 também.
-</div>
+>⚠️ **OBS:** somente lojas que já são ME1 poderão ter ME2 também.
 
-<div class="alert alert-warning">
-<strong>OBS2:</strong> para poder usar as duas opções, primeiro deverá haver um acordo diretamente com o assessor comercial do Mercado Livre, já que essa ainda não é uma funcionalidade pública.
-</div>
+>⚠️ **OBS2:** para poder usar as duas opções, primeiro deverá haver um acordo diretamente com o assessor comercial do Mercado Livre, já que essa ainda não é uma funcionalidade pública.
 
 Então, é necessário segmentar seus produtos indicando para a integração quais serão atribuídos à modalidade ME2. Para fazer isso, siga o passo a passo abaixo:
 
@@ -195,13 +175,15 @@ Então, é necessário segmentar seus produtos indicando para a integração qua
 2. Essa especificação deverá receber o valor `me2`.
 3. Depois de cadastrar a especificação, você deve acessar o cadastro de cada produto e atribuir o valor à especificação. Você também pode fazer isso de maneira massiva através [deste tutorial](/pt/tutorial/importando-e-exportando-especificacao-de-produto-e-sku).
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> confira se a categoria na qual você está enviando os produtos está apta a usar ME2. Para isso, acesse a seguinte URL no navegador (substituindo a variável entre chaves <code>{CategoryId}</code> pelo ID da categoria do Mercado Livre):
-<br></br>
-api.mercadolibre.com/categories/{CategoryId}
-<br></br>
-Você poderá ver essa informação no campo <strong>shipping_modes</strong>. Se o campo tiver o valor "me2", significa que a categoria aceita essa modalidade de entrega.
-</div>
+>⚠️ **OBS:** confira se a categoria na qual você está enviando os produtos está apta a usar ME2. Para isso, acesse a seguinte URL no navegador (substituindo a variável entre chaves `{CategoryId}` pelo ID da categoria do Mercado Livre):
+>
+>
+> </br>
+> api.mercadolibre.com/categories/{CategoryId}
+>
+>
+> </br>
+> Você poderá ver essa informação no campo **shipping_modes**. Se o campo tiver o valor "me2", significa que a categoria aceita essa modalidade de entrega.
 
 
 Concluindo essas instruções, você vai ter completado a _terceira etapa_ da integração. Agora, você já tem as informações necessárias para lidar com o frete de pedidos realizados no Mercado Livre. Vamos para o próximo passo.
@@ -216,9 +198,7 @@ Para realizar este passo, acesse [este artigo](/pt/tutorial/mapeamento-de-catego
 
 Depois de realizar as configurações acima, você precisa autorizar sua integração com o Mercado Livre. Para isso, basta seguir os passos abaixo:
 
-<div class="alert alert-warning">
-O Mercado Livre exige que a autorização seja efetuada pelo <strong>Usuário Master</strong> da conta no Mercado Livre.
-</div>
+>⚠️ O Mercado Livre exige que a autorização seja efetuada pelo **Usuário Master** da conta no Mercado Livre.
 
 1. No menu do Admin, clique em __Integrações__.
 2. Acesse o item __Configurações__.
diff --git a/docs/tutorials/pt/integrating-with-netshoes.md b/docs/tutorials/pt/integrating-with-netshoes.md
index c6c0fc882..1f9cdca4e 100644
--- a/docs/tutorials/pt/integrating-with-netshoes.md
+++ b/docs/tutorials/pt/integrating-with-netshoes.md
@@ -44,17 +44,13 @@ A Netshoes é um dos maiores marketplaces de artigos esportivos e está disponí
 - __Mapeamento de Tipo de Entrega (SLA) -> Normal:__ aqui deve ser inserido o [tipo de transportadora](/pt/tutorial/como-funciona-o-tipo-de-entrega) que você deseja usar para entrega __normal__.
 _`Ex:` imagine que você usa o Correios (PAC) como transportadora e seu Tipo de transportadora no painel de transportadoras da VTEX se chama "Comum". Então, você deve escrever no campo o nome __Comum__. Lembre-se que a palavra deve ser exatamente igual à cadastrada na seção de Estoque & entrega._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> se o campo for deixado em branco, a integração usará a transportadora <strong>mais barata disponível</strong> no momento de integrar o pedido.
-</div>
+>⚠️ **OBS:** se o campo for deixado em branco, a integração usará a transportadora **mais barata disponível** no momento de integrar o pedido.
 
 - __Mapeamento de Tipo de Entrega (SLA) -> Expressa:__ o [tipo de transportadora](/pt/tutorial/como-funciona-o-tipo-de-entrega) que você deseja usar para entrega __expressa__.
 - 
 _`Ex:` imagine que você usa a transportadora XPTO, que entrega mais rápido, mas é mais cara. Seu Tipo de transportadora no painel de transportadoras da VTEX se chama "Entrega Rápida". Então, você deve escrever no campo o nome __Entrega Rápida__. Lembre-se que a palavra deve ser exatamente igual à cadastrada na seção de Estoque & entrega._
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> se o campo for deixado em branco, a integração usará a transportadora <strong>mais barata disponível<strong> no momento de integrar o pedido.
-</div>
+>⚠️ **OBS:** se o campo for deixado em branco, a integração usará a transportadora <strong>mais barata disponível<strong> no momento de integrar o pedido.
 
 _Legenda:_<br />
 `*` Campos obrigatórios.<br />
@@ -86,11 +82,9 @@ A implementação dessa API permite que a Netshoes consulte, em tempo real, pre
 
 `http://{accountName}.vtexcommercestable.com.br/api/netshoesintegration/freight`
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> se os Mapeamentos de Entrega não estiverem feitos, não haverá retorno de informações de entrega e frete para essa API.</div> 
+>⚠️ **OBS:** se os Mapeamentos de Entrega não estiverem feitos, não haverá retorno de informações de entrega e frete para essa API. 
 
-<div class="alert alert-warning">
-<strong>OBS 2:</strong> para que a consulta da API seja feita com sucesso, o ID da transportadora e o ID da doca na VTEX deve ser um valor que contenha somente números.</div>
+>⚠️ **OBS 2:** para que a consulta da API seja feita com sucesso, o ID da transportadora e o ID da doca na VTEX deve ser um valor que contenha somente números.
 
 Esse é o _segundo passo_ da integração. Para concluir o processo, é necessário realizar o envio das especificações dos seus produtos à Netshoes.
 
@@ -111,9 +105,7 @@ O mapeamento deve ser feito sempre que um produto for enviado pela primeira vez
 
 Siga o passo a passo abaixo, fazendo o de/para na __Planilha de Mapeamento__ entre o que está cadastrado no seu produto na VTEX e os valores especificados de acordo com a __Planilha de Consulta__ da Netshoes.
 
-<div class="alert alert-warning">
-<strong>OBS:</strong> qualquer valor usado que não esteja na Planilha de Consulta vai ocasionar em um erro de integração.
-</div>
+>⚠️ **OBS:** qualquer valor usado que não esteja na Planilha de Consulta vai ocasionar em um erro de integração.
 
 1. __ID do SKU:__ é o ID do SKU na VTEX. Esse é o Id do SKU que você deseja enviar para a Netshoes.
 
@@ -126,8 +118,7 @@ Siga o passo a passo abaixo, fazendo o de/para na __Planilha de Mapeamento__ ent
 4. __Marca:__ preencha com o valor correspondente à Marca do Produto na VTEX. 
 <br/>_`Ex:` você está mapeando uma camisa da Nike. De acordo com a Planilha de Consulta, a coluna __Marca__ deve ser preenchida com o valor `Nike`._
 <br/>
-<div class="alert alert-warning">
-<strong>OBS:</strong> se a marca que você tem em seus produtos não está na Planilha de Consulta, entre em contato com a Netshoes solicitando a inclusão dela no sistema. Assim que eles confirmarem o cadastro, você poderá usar a marca no mapeamento. Caso eles não tenham cadastrado ainda, o produto vai sofrer um erro de integração.</div>
+>⚠️ **OBS:** se a marca que você tem em seus produtos não está na Planilha de Consulta, entre em contato com a Netshoes solicitando a inclusão dela no sistema. Assim que eles confirmarem o cadastro, você poderá usar a marca no mapeamento. Caso eles não tenham cadastrado ainda, o produto vai sofrer um erro de integração.
 
 5. __Cor__: preencha com o valor da Cor do SKU.
 <br/>_`Ex:` você está mapeando um short azul e branco. De acordo com a Planilha de Consulta, a coluna __Cor__ deve ser preenchida com o valor `Azul+Branco`._
diff --git a/docs/tutorials/pt/integrating-with-renner-and-camicado.md b/docs/tutorials/pt/integrating-with-renner-and-camicado.md
index f8bfab2b6..cfe7d1a1a 100644
--- a/docs/tutorials/pt/integrating-with-renner-and-camicado.md
+++ b/docs/tutorials/pt/integrating-with-renner-and-camicado.md
@@ -19,9 +19,7 @@ A [Renner](https://www.lojasrenner.com.br/) é uma marca do segmento fashion, e
 
 Tanto a Renner quanto a Camicado firmaram uma parceria com a VTEX e se tornaram [conectores certificados](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro), também chamados de parceiros. Este artigo orienta como configurar a integração com a Renner ou a Camicado.
 
-<div class="alert alert-info">
-Caso seja do seu interesse integrar sua loja VTEX tanto com a Renner quanto com a Camicado, você deverá realizar uma integração para cada um dos parceiros.
-</div>
+>ℹ️ Caso seja do seu interesse integrar sua loja VTEX tanto com a Renner quanto com a Camicado, você deverá realizar uma integração para cada um dos parceiros.
 
 Cada marketplace possui um método de cadastro:
 
@@ -60,9 +58,7 @@ Se você for integrar com os dois parceiros, Renner e Camicado, será necessári
 5. Clique em `Adicionar perfis` e selecione os perfis desejados.  
 6. Clique em `Gerar`.  
 
-<div class="alert alert-danger">
-O <i>secret</i> gerado, também chamado de <i>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
-</div>
+>❗ O <i>secret</i> gerado, também chamado de <i>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
 
 ### Criar ID do afiliado
 
@@ -123,8 +119,6 @@ Alguns dos dados a serem enviados são encontrados no seu Admin, são eles:
 
 Uma vez que você tenha reunido esses dados, você deverá enviá-los para o contato informado pela Renner ou pela Camicado, e a integração será concluída pelo parceiro. Vale ressaltar que o processo de _onboarding_ com conectores certificados é responsabilidade dos próprios parceiros.
 
-<div class="alert alert-info">
-A Camicado disponibiliza documentação sobre a integração. Para consultá-la, faça o <a href="https://drive.google.com/uc?export=download&id=10IHQLiaRImT5pcJ45hNZ01G3pUSgwxry">download do Tutorial de Auxílio ao parceiro.pdf</a>.
-</div>
+>ℹ️ A Camicado disponibiliza documentação sobre a integração. Para consultá-la, faça o [download do Tutorial de Auxílio ao parceiro.pdf](https://drive.google.com/uc?export=download&id=10IHQLiaRImT5pcJ45hNZ01G3pUSgwxry).
 
 Caso você tenha dúvidas sobre a integração com a Renner, você pode utilizar o [formulário de suporte Renner](https://atendimento.lojasrenner.com.br/hc/pt-br/requests/new?ticket_form_id=360004738294). Se as dúvidas forem relativas à Camicado, entre em contato pelo email _suporte_marketplace@camicado.com.br_.
diff --git a/docs/tutorials/pt/integrating-with-riachuelo.md b/docs/tutorials/pt/integrating-with-riachuelo.md
index 9accd01fc..75b854e83 100644
--- a/docs/tutorials/pt/integrating-with-riachuelo.md
+++ b/docs/tutorials/pt/integrating-with-riachuelo.md
@@ -25,9 +25,7 @@ Feito isso, dê continuidade às etapas da integração, que foram organizadas e
 - [Envio de informações para Riachuelo](#envio-de-informacoes-para-riachuelo)
 - [Cadastro do Endpoint de Search do afiliado](#cadastro-do-endpoint-de-search-do-afiliado)
 
-<div class="alert alert-info">
-Você também pode conferir as orientações para a integração fornecidas pela Riachuelo na página <a href="https://riachuelomarketplace.zendesk.com/hc/pt-br/articles/1500008432221-Integra%C3%A7%C3%A3o-VTEX-Orienta%C3%A7%C3%B5es-gerais">MANUAL DE INTEGRAÇÃO VTEX</a>.
-</div>
+>ℹ️ Você também pode conferir as orientações para a integração fornecidas pela Riachuelo na página [MANUAL DE INTEGRAÇÃO VTEX](https://riachuelomarketplace.zendesk.com/hc/pt-br/articles/1500008432221-Integra%C3%A7%C3%A3o-VTEX-Orienta%C3%A7%C3%B5es-gerais).
 
 ## Configurações na plataforma VTEX
 
@@ -45,9 +43,7 @@ A [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-poli
 
 Caso seja do seu interesse ter configurações específicas para vender na Riachuelo, você pode [configurar uma política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/). Não existe cobrança para a contratação de políticas comerciais adicionais para integrar lojas VTEX com conectores nativos, conectores certificados ou outras lojas VTEX. Saiba mais em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/integrando-com-marketplace--tutorials_402).
 
-<div class="alert alert-warning">
-Os produtos que você deseja enviar para o Riachuelo Marketplace devem estar <a href="https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb">associados à política comercial</a> definida. Caso contrário, eles não serão integrados. 
-</div>
+>⚠️ Os produtos que você deseja enviar para o Riachuelo Marketplace devem estar [associados à política comercial](https://help.vtex.com/pt/tutorial/associacao-de-sku-a-politica-comercial--1qFAiybogHCStRO65sy4vb) definida. Caso contrário, eles não serão integrados.
 
 ### Criar afiliado
 
@@ -65,9 +61,7 @@ O [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk
 - **E-mail de Follow Up:** endereço eletrônico que receberá notificações sobre a integração.
 - **Endpoint de Search:** URL da aplicação que receberá notificações de produtos, preço, estoque, dentre outros.
 
-<div class="alert alert-danger">
-Esta informação ficará pendente e será retomada na parte final deste artigo, em <a href="">Cadastro do Endpoint de Search do afiliado</a>.
-</div>
+>❗ Esta informação ficará pendente e será retomada na parte final deste artigo, em [Cadastro do Endpoint de Search do afiliado]().
 
 - **Versão do Endpoint de Search:** só existe a opção padrão _1.x.x_.
 - Deixe desmarcada a flag _Usar meu meio de pagamento_.
@@ -95,9 +89,7 @@ A chave de integração, chamada de _access key_, é o que possibilita o fluxo d
 3. Em _Segurança_, clique em `Gerar access key e secret`.
 4. Preencha com um nome para o novo _access key_ e clique em `Gerar novos secrets`.
 
-<div class="alert alert-danger">
-O <i>secret</i> gerado, também chamado de <i>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
-</div>
+>❗ O <i>secret</i> gerado, também chamado de <i>appToken</i>, só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em local seguro.
 
 ### Criar novo usuário
 
@@ -126,9 +118,7 @@ Uma vez concluídas as configurações na plataforma VTEX, para dar continuidade
 
 Na etapa [Criar afiliado](#criar-afiliado), o preenchimento do campo Endpoint de Search havia ficado pendente e agora será realizado.
 
-<div class="alert alert-danger">
-O cadastro do <i>Endpoint de Search</i> só pode ser feito após a confirmação da Riachuelo de que o catálogo da sua loja VTEX foi integrado.
-</div>
+>❗ O cadastro do <i>Endpoint de Search</i> só pode ser feito após a confirmação da Riachuelo de que o catálogo da sua loja VTEX foi integrado.
 
 Uma vez recebida a confirmação do parceiro, realize os passos abaixo:
 
@@ -141,7 +131,5 @@ Uma vez recebida a confirmação do parceiro, realize os passos abaixo:
 
 Feito isso, a integração com a Riachuelo terá sido concluída. Vale ressaltar que o processo de _onboarding_ com conectores certificados é responsabilidade dos parceiros. A Riachuelo disponibiliza conteúdo de [treinamento sobre o Portal do Seller](https://riachuelomarketplace.zendesk.com/hc/pt-br/articles/1500010648222-Portal-do-Seller-Cadastro-de-senha-e-primeiro-acesso).
 
-<div class="alert alert-info">
-Você também pode conferir as orientações para a integração fornecidas pela Riachuelo pela página <a href="https://riachuelomarketplace.zendesk.com/hc/pt-br/articles/1500008432221-Integra%C3%A7%C3%A3o-VTEX-Orienta%C3%A7%C3%B5es-gerais">MANUAL DE INTEGRAÇÃO VTEX</a>. Em caso de dúvidas, entre em contato pela <a href="https://riachuelomarketplace.zendesk.com/hc/pt-br">central de ajuda da Riachuelo</a>.
-</div>
+>ℹ️ Você também pode conferir as orientações para a integração fornecidas pela Riachuelo pela página [MANUAL DE INTEGRAÇÃO VTEX](https://riachuelomarketplace.zendesk.com/hc/pt-br/articles/1500008432221-Integra%C3%A7%C3%A3o-VTEX-Orienta%C3%A7%C3%B5es-gerais). Em caso de dúvidas, entre em contato pela [central de ajuda da Riachuelo](https://riachuelomarketplace.zendesk.com/hc/pt-br).
 
diff --git a/docs/tutorials/pt/integrating-with-viavarejo-cnova.md b/docs/tutorials/pt/integrating-with-viavarejo-cnova.md
index 15874a01c..71145245a 100644
--- a/docs/tutorials/pt/integrating-with-viavarejo-cnova.md
+++ b/docs/tutorials/pt/integrating-with-viavarejo-cnova.md
@@ -39,9 +39,7 @@ Este artigo tem por objetivo orientar o cadastro da integração com a Via Varej
 
 &bull; __Nome do campo de Especificação de Produto que contém sua Descrição__: caso deseje usar uma descrição diferente da que já está cadastrada no catálogo da VTEX, você tem a opção de [criar um campo de produto](/pt/tutorial/criando-um-campo-de-produto) de tipo _Texto Grande_. Preenchendo esse campo, a integração vai priorizar o envio da descrição contida nele (ao invés da descrição original do produto).
 
-<div class="alert alert-danger">
-<strong>OBS:</strong> atente-se às configurações na criação desse novo campo para que as novas informações criadas <strong>não</strong> sejam exibidas no seu site.
-</div>
+>❗ **OBS:** atente-se às configurações na criação desse novo campo para que as novas informações criadas **não** sejam exibidas no seu site.
 
 &bull; __Taxa de Divergência de Preço*:__ é a taxa de aceitação da diferença de valor de um pedido. Qualquer pedido que possua uma diferença entre o preço de venda no marketplace e o preço determinado pelo seller [será comparado com esse valor](/pt/faq/por-que-o-pedido-foi-fechado-com-um-preco-errado). Se a divergência, em percentual, for menor que o valor definido nesse campo, o pedido será integrado normalmente. Caso contrário, o pedido não será integrado e você poderá visualizá-lo na [aba de pedidos (dentro da seção de integrações no Admin)](/pt/tutorial/verificando-integracao-no-bridge).
 
diff --git a/docs/tutorials/pt/integrating-with-walmart.md b/docs/tutorials/pt/integrating-with-walmart.md
index dfef31b01..99f24428a 100644
--- a/docs/tutorials/pt/integrating-with-walmart.md
+++ b/docs/tutorials/pt/integrating-with-walmart.md
@@ -45,9 +45,7 @@ Alguns passos são essenciais para iniciarmos as configurações.
 
 Após as configurações, a integração envia todos os produtos associados à política comercial determinada para o Walmart.
 
-<div class="alert alert-warning">
-<strong>Importante:</strong> o Walmart não aceita código HTML nos campos de descrição do produto e campos de especificação.
-</div>
+>⚠️ **Importante:** o Walmart não aceita código HTML nos campos de descrição do produto e campos de especificação.
 
 ## Fluxo da integração
 
@@ -64,6 +62,4 @@ O __fluxo de pedidos__ e __consulta de frete__ são feitos pelo Walmart, que con
 2 - [Autenticar a integração](/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes)
 Depois de realizar todos esses passos, você vai precisar autenticar a integração com Walmart. Para isso, você só precisa enviar o appKey para eles (veja como [gerar o appKey para autenticação de integrações](/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes)). Se tiver alguma dúvida sobre o processo, entre em contato com a equipe do Walmart.
 
-<div class="alert alert-warning">
-Lembre-se de que o appKey precisa estar associado ao perfil de acesso <strong>IntegrationProfile - Fulfillment</strong>. Ele é o que possui as permissões necessárias para a realizar o processo de integração com o marketplace.
-</div>
+>⚠️ Lembre-se de que o appKey precisa estar associado ao perfil de acesso **IntegrationProfile - Fulfillment**. Ele é o que possui as permissões necessárias para a realizar o processo de integração com o marketplace.
diff --git a/docs/tutorials/pt/integrating-with-zoom.md b/docs/tutorials/pt/integrating-with-zoom.md
index fbe6bee25..b7fc54c05 100644
--- a/docs/tutorials/pt/integrating-with-zoom.md
+++ b/docs/tutorials/pt/integrating-with-zoom.md
@@ -33,9 +33,7 @@ Para integrar com o Zoom, é necessário realizar as seguintes etapas:
 - [Configurar conector](#configurar-conector)
 - [Reindexar base](#reindexar-base)
 
-<div class="alert alert-info">
-Se for do seu interesse consultar a documentação do Zoom, faça o <a href="https://drive.google.com/uc?export=download&id=1hZzqJgyQtozHNJKGBgDZiu6_5eKtHaU5">download do arquivo Integração VTEX.pdf</a>. Em caso de dúvidas, você pode entrar em contato com o Zoom pelo email <i/>integracao@zoom.com.br</i>. 
-</div>
+>ℹ️ Se for do seu interesse consultar a documentação do Zoom, faça o [download do arquivo Integração VTEX.pdf](https://drive.google.com/uc?export=download&id=1hZzqJgyQtozHNJKGBgDZiu6_5eKtHaU5). Em caso de dúvidas, você pode entrar em contato com o Zoom pelo email <i/>integracao@zoom.com.br</i>.
 
 ### Configurar perfil de acesso
 
@@ -67,9 +65,7 @@ Só será necessário ter uma política comercial diferente daquela utilizada na
 
 A contratação de política comercial adicional para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) ou outras lojas VTEX é isenta de taxas.
 
-<div class="alert alert-danger">
-Caso seja feita alguma alteração na sua política comercial, o Zoom deverá ser avisado. Você pode entrar em contato pelo email <i/>integracao@zoom.com.br</i>.
-</div>
+>❗ Caso seja feita alguma alteração na sua política comercial, o Zoom deverá ser avisado. Você pode entrar em contato pelo email <i/>integracao@zoom.com.br</i>.
 
 ### Criar ID do afiliado
 
@@ -126,6 +122,4 @@ Uma vez que todas as etapas das [Configurações na plataforma VTEX](#configurac
    - **Dados bancários:** conta para a qual deve ser feito o repasse de vendas.
    - **Logotipo da sua loja:** a imagem deve ter alta resolução e, preferencialmente, ser em formato .png.
 
-<div class="alert alert-info">
-Você pode consultar a documentação do Zoom sobre a integração, para isso faça o <a href="https://drive.google.com/uc?export=download&id=1hZzqJgyQtozHNJKGBgDZiu6_5eKtHaU5">download do arquivo Integração VTEX.pdf</a>. Em caso de dúvidas, entre em contato com o Zoom pelo email <i/>integracao@zoom.com.br</i>.
-</div>
+>ℹ️ Você pode consultar a documentação do Zoom sobre a integração, para isso faça o [download do arquivo Integração VTEX.pdf](https://drive.google.com/uc?export=download&id=1hZzqJgyQtozHNJKGBgDZiu6_5eKtHaU5). Em caso de dúvidas, entre em contato com o Zoom pelo email <i/>integracao@zoom.com.br</i>.
diff --git a/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md b/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
index 02267aa2e..434cab1d3 100644
--- a/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
+++ b/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller-catalog-updates.md
@@ -15,9 +15,7 @@ legacySlug: integracao-entre-marketplace-nao-vtex-e-seller-vtex-acoes-referentes
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) em nosso Developer Portal. 
 
 Um dos passos para integrar um Marketplace não VTEX a um Seller VTEX é permitir consultas ao __Catálogo__ da VTEX com o objetivo de obter informações de mudança de preço, estoque, catálogo e dados de frete.
 
@@ -293,9 +291,21 @@ O Marketplace deve então usar a __API de Fulfillment Simulation__ para obter os
 
 Essa chamada simula um carrinho no Checkout da VTEX, retornando a versão mais atualizada desses dados.
 
-<div class="alert alert-warning">
-A chamada de Fulfillment Simulation deve ser usada pelo Marketplace sempre que for necessário obter preço, estoque e dados de frete atualizados. Para oferecer uma integração em tempo real e, como consequência, uma experiência de compra fluida, o Marketplace deve obter esses dados em todas as etapas da jornada do cliente na loja:<br>- Vitrine<br>- Página de produto<br>- Carrinho<br>- Checkout<br>- Order Placed<br><br>Com isso, você garante que o cliente não será surpreendido por possíveis mudanças em um SKU ocorridas no Seller e não informadas no Marketplace. 
-</div>
+>⚠️ A chamada de Fulfillment Simulation deve ser usada pelo Marketplace sempre que for necessário obter preço, estoque e dados de frete atualizados. Para oferecer uma integração em tempo real e, como consequência, uma experiência de compra fluida, o Marketplace deve obter esses dados em todas as etapas da jornada do cliente na loja:
+>
+> - Vitrine
+>
+> - Página de produto
+>
+> - Carrinho
+>
+> - Checkout
+>
+> - Order Placed
+>
+> 
+>
+> Com isso, você garante que o cliente não será surpreendido por possíveis mudanças em um SKU ocorridas no Seller e não informadas no Marketplace.
 
 ### Exemplo de chamada API REST:
 
@@ -341,9 +351,7 @@ Acessa uma loja VTEX (*Seller*) e busca preço, estoque e dados de frete de um S
 | quantity       | integer       |   Quantidade do SKU desejado  |  Sim  |
 | seller       | string       |   ID do seller que vende o SKU desejado. No contexto de simulação de fulfillment, o seller deve ser sempre "1" - "seller 1" significa que é o próprio fulfillment em questão.  |   Sim   |
 
-<div class="alert alert-warning">
-A simulação para obter preço/disponibilidade deve ser feita somente com <strong>1 unidade</strong> do item específico. Já simulações de carrinho devem naturalmente incluir todos os itens desejados, a fim de garantir o contexto desses itens quando em conjunto no carrinho, o que é especialmente importante para o cálculo do frete.
-</div>
+>⚠️ A simulação para obter preço/disponibilidade deve ser feita somente com **1 unidade** do item específico. Já simulações de carrinho devem naturalmente incluir todos os itens desejados, a fim de garantir o contexto desses itens quando em conjunto no carrinho, o que é especialmente importante para o cálculo do frete.
 
 #### Exemplo de body de resposta
 
diff --git a/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller.md b/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller.md
index 4c7104786..99ec33a3e 100644
--- a/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller.md
+++ b/docs/tutorials/pt/integration-between-non-vtex-marketplace-and-vtex-seller.md
@@ -15,9 +15,7 @@ legacySlug: integracao-entre-marketplace-nao-vtex-e-seller-vtex-acoes-referentes
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) em nosso Developer Portal. 
 
 O passo final para integrar um Marketplace não VTEX a um Seller VTEX é permitir a comunicação com o Seller sobre __pedidos__ feitos no Marketplace.
 
@@ -478,9 +476,13 @@ Endpoint: `https://{AccountName}.vtexcommercestable.com.br/api/fulfillment/pvt/o
 
 ## Marketplace Services Endpoint
 
-<div class="alert alert-info">
-  O <strong>Marketplace Services Endpoint</strong> é um endpoint que deve ser criado pelo Marketplace, com o objetivo de receber três informações diferentes enviadas pelo Seller:<br>- Nota Fiscal<br>- Código de rastreamento da transportadora (se houver)<br>- Solicitação de cancelamento (se acontecer)
-</div>
+>ℹ️ O **Marketplace Services Endpoint** é um endpoint que deve ser criado pelo Marketplace, com o objetivo de receber três informações diferentes enviadas pelo Seller:
+>
+> - Nota Fiscal
+>
+> - Código de rastreamento da transportadora (se houver)
+>
+> - Solicitação de cancelamento (se acontecer)
 
 Para os três próximos passos da integração, o Marketplace precisa:
 1. Implementar esse endpoint do seu lado, preparando-o para receber um payload como o do exemplo abaixo.
@@ -565,9 +567,7 @@ O Seller envia o código e a URL de rastreamento para o __Marketplace Services E
 
 Para receber o código de rastreamento, o endpoint final esperado deve ser: `https://{marketplaceServicesEndpoint}/pvt/orders/{marketplaceOrderId}/invoice`
 
-<div class="alert alert-info">
-Embora a rota para recebimento do código de rastreamento seja a mesma onde o Marketplace recebe a Nota Fiscal (<code>.../invoice</code>), esses dois processos acontecem em duas etapas. Ou seja, numa primeira chamada o Seller envia os dados da Nota Fiscal; e numa segunda chamada envia os dados de rastreamento.
-</div>
+>ℹ️ Embora a rota para recebimento do código de rastreamento seja a mesma onde o Marketplace recebe a Nota Fiscal (`.../invoice`), esses dois processos acontecem em duas etapas. Ou seja, numa primeira chamada o Seller envia os dados da Nota Fiscal; e numa segunda chamada envia os dados de rastreamento.
 
 ## 6) Receber solicitação de cancelamento - Seller chama endpoint do Marketplace (Marketplace Services Endpoint)
 
diff --git a/docs/tutorials/pt/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md b/docs/tutorials/pt/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
index 9b6ed8e3e..4caa75692 100644
--- a/docs/tutorials/pt/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
+++ b/docs/tutorials/pt/integration-guide-consuming-catalog-information-for-use-in-an-external-service.md
@@ -293,10 +293,6 @@ Recebendo este payload, o integrador deve utilizar estas informações para deci
 - Caso tenha ocorrido alteração de preço ou estoque, o integrador deve chamar a rota `https://{accountName}.vtexcommercestable.com.br/api/fulfillment/pvt/orderForms/simulation?sc={salesChannel}&affiliateId={affiliateId}`, conforme descrito na seção [Obter os dados de preço e estoque dos SKUs](#3-obter-os-dados-de-preco-e-estoque-dos-skus).
 - Caso tenha ocorrido uma alteração no SKU que não seja de preço ou estoque, o integrador deve chamar a rota `http://{{accountName}}.vtexcommercestable.com.br/api/catalog_system/pvt/sku/stockkeepingunitbyid/{{skuId}}`, conforme descrito na seção [Obter os dados sobre as propriedades dos SKUs](#2-obter-os-dados-sobre-as-propriedades-dos-skus).
 
-<div class="alert alert-warning">
-Caso um novo SKU seja inserido no Catálogo, ele será notificado no Endpoint de cada afiliado. Por se tratar de um novo SKU, é necessário realizar o preenchimento dos dados deste novo SKU na base de dados do serviço externo. O integrador deve verificar se o SKU notificado se trata de um SKU que ainda não existe na base de dados do serviço externo. Caso se trate de um novo SKU, o integrador deve seguir os mesmos passos descritos na seção <strong>Realizar a primeira carga com os dados dos SKUs</strong>. Caso seja um SKU já existente, o integrador deve seguir os passos da seção <strong>Atualizar os dados dos SKUs</strong>
-</div>
+>⚠️ Caso um novo SKU seja inserido no Catálogo, ele será notificado no Endpoint de cada afiliado. Por se tratar de um novo SKU, é necessário realizar o preenchimento dos dados deste novo SKU na base de dados do serviço externo. O integrador deve verificar se o SKU notificado se trata de um SKU que ainda não existe na base de dados do serviço externo. Caso se trate de um novo SKU, o integrador deve seguir os mesmos passos descritos na seção **Realizar a primeira carga com os dados dos SKUs**. Caso seja um SKU já existente, o integrador deve seguir os passos da seção **Atualizar os dados dos SKUs**
 
-<div class="alert alert-info">
-Caso queira integrar as formas de pagamento de um seller VTEX com um marketplace externo, <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">acesse nossa documentação</a>.
-</div>
+>ℹ️ Caso queira integrar as formas de pagamento de um seller VTEX com um marketplace externo, [acesse nossa documentação](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
diff --git a/docs/tutorials/pt/integration-guide-for-erps-express-catalog.md b/docs/tutorials/pt/integration-guide-for-erps-express-catalog.md
index 1cdce1980..aadb5ad9e 100644
--- a/docs/tutorials/pt/integration-guide-for-erps-express-catalog.md
+++ b/docs/tutorials/pt/integration-guide-for-erps-express-catalog.md
@@ -15,7 +15,7 @@ legacySlug: guia-de-integracao-de-erps-catalogo-expresso
 subcategory: 5fKgQZhrCw88ACy6Su6GUc
 ---
 
-<div class="alert alert-warning">Este artigo é parte do <a href="https://help.vtex.com/tutorial/guia-de-integracao-de-erps--3VuOwNLmb624ImooEIIkmO">Guia de integração de ERPs</a>.</div>
+>⚠️ Este artigo é parte do [Guia de integração de ERPs](https://help.vtex.com/tutorial/guia-de-integracao-de-erps--3VuOwNLmb624ImooEIIkmO).
 
 Este documento tem por objetivo auxiliar na integração de catálogo do ERP para uma loja hospedada na VTEX, de uma maneira rápida.
 
diff --git a/docs/tutorials/pt/integration-guide-for-erps-full-catalog.md b/docs/tutorials/pt/integration-guide-for-erps-full-catalog.md
index 307bb2754..5c539851c 100644
--- a/docs/tutorials/pt/integration-guide-for-erps-full-catalog.md
+++ b/docs/tutorials/pt/integration-guide-for-erps-full-catalog.md
@@ -15,7 +15,7 @@ legacySlug: guia-de-integracao-de-erps-catalogo-completo
 subcategory: 5fKgQZhrCw88ACy6Su6GUc
 ---
 
-<div class="alert alert-warning">Este artigo é parte do <a href="https://help.vtex.com/tutorial/guia-de-integracao-de-erps--3VuOwNLmb624ImooEIIkmO">Guia de integração de ERPs</a>.</div>
+>⚠️ Este artigo é parte do [Guia de integração de ERPs](https://help.vtex.com/tutorial/guia-de-integracao-de-erps--3VuOwNLmb624ImooEIIkmO).
 
 Este documento tem por objetivo auxiliar na integração de catálogo (departamento, categoria, marca, imagens, campos, valores de campos, ativação de SKUs) do ERP para a uma loja hospedada na VTEX. Nesse tipo de integração a maioria da administração da loja está ERP.
 
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md b/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
index 5a759d428..3454e9fed 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex-with-payment.md
@@ -15,9 +15,7 @@ legacySlug: guia-de-integracao-para-marketplaces-marketplace-nao-vtex-com-pagame
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) em nosso Developer Portal. 
 
 ## Marketplace Não Hospedado na Plataforma VTEX vendendo para Sellers Hospedados na Plataforma VTEX com Pagamento
 
@@ -116,7 +114,7 @@ O Marketplace irá usar esse endpoint para autorizar o andamento do pagamento no
  [Exemplo Completo: Informar tracking de um pedido](#a13)<br/>
  [Exemplo Completo: Solicitar cancelamento de um pedido sem nota fiscal](#a14)<br/>
 
-<div class="alert alert-warning">No POST do pedido feito pelo Marketplace, o campo <code>marketplaceserviceendpoint</code> deve vir preenchido com o url base de serviços do Marketplace.</div>
+>⚠️ No POST do pedido feito pelo Marketplace, o campo `marketplaceserviceendpoint` deve vir preenchido com o url base de serviços do Marketplace.
 
 12. Implementar rotina que captura ou cancela o pagamento no Seller - Marketplace vai chamar endpoint do Seller.
 O Marketplace deve capturar o pagamento ao receber a nota fiscal e deve cancelar o pagamento ao receber um cancelamento de pedido.
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md b/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md
index ddeaa41bc..c8a5f7b16 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md
@@ -15,9 +15,7 @@ legacySlug: guia-de-integracao-para-marketplaces-marketplace-nao-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) em nosso Developer Portal. 
 
 Este documento auxilia na integração de um Marketplace não hospedado na plataforma VTEX com um Seller hospedado na plataforma VTEX.
 
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md b/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
index 5abbc9888..cf0682747 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex-with-payment.md
@@ -15,9 +15,7 @@ legacySlug: guia-de-integracao-para-marketplaces-seller-nao-vtex-com-pagamento
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector) em nosso Developer Portal. 
 
 ## Seller Não VTEX Vendendo em Marketplace Hospedado na VTEX Recebendo Pagamento
 
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md b/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md
index 050c7cb9c..0097ad112 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces-seller-non-vtex.md
@@ -15,9 +15,7 @@ legacySlug: guia-de-integracao-para-marketplaces-seller-nao-vtex
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-connector) em nosso Developer Portal. 
 
 ## Seller Não VTEX Vendendo em Marketplace Hospedado na VTEX
 
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces.md b/docs/tutorials/pt/integration-guide-for-marketplaces.md
index b09ee81ec..8cf11ad58 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces.md
@@ -15,9 +15,7 @@ legacySlug: guia-de-integracao-para-marketplaces
 subcategory: 6riYYNZCpO8wyksi8Ksgyq
 ---
 
-<div class="alert alert-warning">
-Confira a versão atualizada desse <a href="https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide">guia de integração com marketplace</a> em nosso Developer Portal. 
-</div> 
+>⚠️ Confira a versão atualizada desse [guia de integração com marketplace](https://developers.vtex.com/vtex-developer-docs/docs/external-marketplace-integration-guide) em nosso Developer Portal. 
 
 ## Marketplaces e sellers
 
@@ -45,7 +43,7 @@ Extensão do navegador chrome, nesta ferramenta pode se testar, armazenar histó
 
 Toda chamada feita as APIs REST da VTEX devem ser feitas em "https" e devem conter em seu header as chaves de autenticação. As chaves de autenticação do header(para acessar as APIs REST) devem ser solicitados ao administrador da loja, ou ao time de operações que está implantando a loja.
 
-<div class="alert alert-warning"><strong>Atenção</strong>: Deverá ser criada uma chave e um token exclusivos para cada integrador. **Não** se deve usar a chave da própria loja.</div>
+>⚠️ **Atenção**: Deverá ser criada uma chave e um token exclusivos para cada integrador. **Não** se deve usar a chave da própria loja.
 
 ## Modelos de integração
 
diff --git a/docs/tutorials/pt/integration-interfaces.md b/docs/tutorials/pt/integration-interfaces.md
index 8d8c15d4d..34abd19e4 100644
--- a/docs/tutorials/pt/integration-interfaces.md
+++ b/docs/tutorials/pt/integration-interfaces.md
@@ -46,9 +46,7 @@ Veja abaixo documentações que podem auxiliar a iniciar as integrações pela i
 
 ### Web Service
 
-<div class="alert alert-warning">
-O Web Service VTEX deve ser usado o mínimo possível para os processos de integração.
-</div>
+>⚠️ O Web Service VTEX deve ser usado o mínimo possível para os processos de integração.
 
 Com exceção do Catálogo (Categorias, Marcas, Produtos e SKUs), que está com sua API REST em desenvolvimento, todos os outros módulos da VTEX possuem APIs REST bem definidas e de alta performance.
 
diff --git a/docs/tutorials/pt/integration-with-google-tag-manager.md b/docs/tutorials/pt/integration-with-google-tag-manager.md
index 9114ab7d2..8239b7606 100644
--- a/docs/tutorials/pt/integration-with-google-tag-manager.md
+++ b/docs/tutorials/pt/integration-with-google-tag-manager.md
@@ -15,9 +15,7 @@ legacySlug: integracao-com-o-google-tag-manager
 subcategory: 6XAvmMxp7yyY06ewYMuggs
 ---
 
-<div class="alert alert-warning">
-Se sua loja é desenvolvida com base no <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">Store framework</a>, para fazer a integração funcionar em todas as páginas é necessário também instalar o aplicativo do pixel do Google Tag Manager. Veja como fazer isso na <a href="https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager">documentação sobre a app</a>.
-</div>
+>⚠️ Se sua loja é desenvolvida com base no [Store framework](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), para fazer a integração funcionar em todas as páginas é necessário também instalar o aplicativo do pixel do Google Tag Manager. Veja como fazer isso na [documentação sobre a app](https://developers.vtex.com/vtex-developer-docs/docs/google-tag-manager).
 
 O Google Tag Manager é um sistema de gerenciamento de tags criado pelo Google para gerenciar tags JavaScript e HTML usadas para tracking e analytics de sites da web.
 
@@ -53,9 +51,7 @@ Depois, você deve configurar o código de identificação da loja no Tag Manage
 
 Para verificar eventos (acionadores) e variáveis disponíveis nas páginas, que serão usados nas tags, você pode utilizar o modo de visualização do Google Tag Manager. Consulte a [documentação do Google Tag Manager](https://support.google.com/tagmanager/answer/6107056?hl=pt-BR) para mais detalhes.
 
-<div class="alert alert-info">
-É possível usar o *pixel app* do Facebook junto ao Google Tag Manager da sua loja para acompanhar e otimizar os resultados das suas campanhas de marketing na rede social. Aprenda o passo a passo <a href="https://www.facebook.com/business/help/1021909254506499">na documentação do Facebook</a>.
-</div>
+>ℹ️ É possível usar o *pixel app* do Facebook junto ao Google Tag Manager da sua loja para acompanhar e otimizar os resultados das suas campanhas de marketing na rede social. Aprenda o passo a passo [na documentação do Facebook](https://www.facebook.com/business/help/1021909254506499).
 
 ## VTEX IO: instalar pixel app do Google Tag Manager
 
diff --git a/docs/tutorials/pt/integration-with-vtex-tracking.md b/docs/tutorials/pt/integration-with-vtex-tracking.md
index c1c9673af..9c85224c8 100644
--- a/docs/tutorials/pt/integration-with-vtex-tracking.md
+++ b/docs/tutorials/pt/integration-with-vtex-tracking.md
@@ -17,15 +17,13 @@ subcategory: t5ai1r0dN7J4U1IYLbHmG
 
 O [VTEX Tracking ](https://help.vtex.com/pt/tutorial/vtex-tracking-overview--1uDRquVudbPuoK05MtbZGh) é uma solução para rastreio de entregas. A plataforma permite acompanhar e gerenciar cada entrega da sua loja. Para que as informações necessárias para realização das entregas dos pedidos estejam disponíveis na plataforma VTEX Tracking é preciso realizar uma integração de pedidos. Dessa forma, os pedidos e serviços ficam disponíveis para criação de rotas no VTEX Tracking.
 
-<div class="alert alert-warning">
-Para importar pedidos, é necessário cumprir os requisitos abaixo:
-<body>
-<ol>
-<li>Os pedidos precisam estar faturados.</li>
-<li>Nos casos em que o pedido é roteirizado externamente (fora do VTEX Tracking), a roteirização precisa ser feita antes da importação.</i>
-</ol>
-</body>
-</div>
+>⚠️ Para importar pedidos, é necessário cumprir os requisitos abaixo:
+> <body>
+>
+> Os pedidos precisam estar faturados.
+> <li>Nos casos em que o pedido é roteirizado externamente (fora do VTEX Tracking), a roteirização precisa ser feita antes da importação.</i>
+>
+> </body>
 
 Há dois cenários de integração:
 
diff --git a/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md b/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
index 7afe5afd8..1a95181df 100644
--- a/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
+++ b/docs/tutorials/pt/intelligent-search-synonym-suggestions-beta.md
@@ -15,9 +15,7 @@ legacySlug: sugestoes-de-sinonimos-do-intelligent-search-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade está  disponível para contas que tenham uma quantidade mínima de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la futuramente, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. É possível que taxas extras se apliquem futuramente.</p>
-</div>
+>ℹ️ Esta funcionalidade está  disponível para contas que tenham uma quantidade mínima de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la futuramente, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests). É possível que taxas extras se apliquem futuramente.
 
 A funcionalidade de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) permite cadastrar palavras, ou expressões de mesmo sentido, para termos de busca utilizados pelos clientes ao realizar pesquisas na sua loja, aumentando a chance deles obterem resultados relevantes nas buscas.
 
diff --git a/docs/tutorials/pt/intelligent-synonyms.md b/docs/tutorials/pt/intelligent-synonyms.md
index 9ce546f30..1243b774a 100644
--- a/docs/tutorials/pt/intelligent-synonyms.md
+++ b/docs/tutorials/pt/intelligent-synonyms.md
@@ -15,9 +15,7 @@ legacySlug: sinonimos-inteligentes
 subcategory: BBzMtJan1UTxC9QZODnlN
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade está  disponível para contas que tenham um número mínimo de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>. É possível que taxas extras se apliquem futuramente.</p>
-</div>
+>ℹ️ Esta funcionalidade está  disponível para contas que tenham um número mínimo de sessões e pedidos para que o modelo de Inteligência Artificial seja treinado. Caso tenha interesse em implementá-la, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests). É possível que taxas extras se apliquem futuramente.
 
 A funcionalidade de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) permite cadastrar palavras, ou expressões de mesmo sentido, para termos de busca utilizados pelos clientes ao realizar pesquisas na sua loja, aumentando a chance deles obterem resultados relevantes nas buscas.
 
diff --git a/docs/tutorials/pt/interaction-details.md b/docs/tutorials/pt/interaction-details.md
index 69c09e523..51fd2348f 100644
--- a/docs/tutorials/pt/interaction-details.md
+++ b/docs/tutorials/pt/interaction-details.md
@@ -15,12 +15,10 @@ legacySlug: detalhes-da-interacao
 subcategory: 
 ---
 
-<div class="alert alert-info">
-Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
-Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
-Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
-</div>   
+>ℹ️ Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo **Gerenciamento de anúncios**.
+> Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+> Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do [Developer portal na página de release notes](https://developers.vtex.com/updates/release-notes) e [VTEX Help Center na página de novidades](https://help.vtex.com/pt/en/announcements).   
 
 A página de **Detalhes da interação**, do módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE), permite que sellers visualizem de forma mais completa as interações ocorridas a um anúncio durante seu processo de envio e sincronização com um canal. Cada interação do anúncio fica disponível por dez dias a partir do seu registro.
 
diff --git a/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md b/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
index 9bff065ff..6e1199339 100644
--- a/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
+++ b/docs/tutorials/pt/interpreting-the-data-of-the-oms-order-bar.md
@@ -35,9 +35,7 @@ No screenshot das métricas acima, podemos ver as seguintes informações:
 - Já no mesmo dia da semana passada, também até 20h50, houve 1856 pedidos;
 - Por fim, em relação a um ano atrás houve um aumento expressivo no número de pedidos: no mesmo dia do ano passado, até o mesmo horário, foram 1425 pedidos, contra os 2464 deste ano.
 
-<div class="alert alert-info">
-O cálculo de pedidos feitos no <b>ano passado</b> é feito subtraindo 52 semanas do dia atual. Dessa forma, mantém-se o dia da semana. Por exemplo: o dia 24/novembro/2017 será comparado com o dia 25/novembro/2016, aonde ambas as datas caem numa sexta-feira.
-</div>
+>ℹ️ O cálculo de pedidos feitos no **ano passado** é feito subtraindo 52 semanas do dia atual. Dessa forma, mantém-se o dia da semana. Por exemplo: o dia 24/novembro/2017 será comparado com o dia 25/novembro/2016, aonde ambas as datas caem numa sexta-feira.
 
 O ranking localizado no canto direito da barra com esses dados mostra a posição da loja entre todas as lojas VTEX, com a métrica ao lado indicando a evolução entre ontem e hoje.
 
diff --git a/docs/tutorials/pt/introduction-to-vtex-apis.md b/docs/tutorials/pt/introduction-to-vtex-apis.md
index 1c36f0139..c77ab5e82 100644
--- a/docs/tutorials/pt/introduction-to-vtex-apis.md
+++ b/docs/tutorials/pt/introduction-to-vtex-apis.md
@@ -118,8 +118,6 @@ Elas ficam divididas por módulo ou funcionalidade. Entrando em um destes, você
  
 Para algumas APIs, há também uma Sample Response, que é um exemplo de resposta àquele request.
 
-<div class="alert alert-warning">
-Todo conteúdo que aparece entre chaves (**{{conteúdo}}**) é uma variável, e deve ser substituído pelo dado correto antes de se realizar o request. É o caso, por exemplo, do nome da sua loja, do ambiente desejado e dos valores de AppKey e AppToken.
-</div>
+>⚠️ Todo conteúdo que aparece entre chaves (**{{conteúdo}}**) é uma variável, e deve ser substituído pelo dado correto antes de se realizar o request. É o caso, por exemplo, do nome da sua loja, do ambiente desejado e dos valores de AppKey e AppToken.
 
 Veja como criar o seu appKey e appToken no artigo [Criar appKey e appToken para autenticar integrações](/pt/tutorial/criar-appkey-e-apptoken-para-autenticar-integracoes).
diff --git a/docs/tutorials/pt/inventory-update-history.md b/docs/tutorials/pt/inventory-update-history.md
index fb0927a4d..3feadb095 100644
--- a/docs/tutorials/pt/inventory-update-history.md
+++ b/docs/tutorials/pt/inventory-update-history.md
@@ -36,8 +36,6 @@ Para visualizar as movimentações de um SKU:
   * A quantidade de itens antes da atualização.
   * A quantidade de itens após a atualização.
 
-<div class="alert alert-warning">
-Só é possível consultar as últimas 50 movimentações no registro de atualizações de um determinado SKU.
-</div>
+>⚠️ Só é possível consultar as últimas 50 movimentações no registro de atualizações de um determinado SKU.
 
 A quantidade total de itens na página [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) é atualizada em tempo real, mas pode haver um atraso de até 1 hora para a informação aparecer no registro de atualizações.
diff --git a/docs/tutorials/pt/kabum-integration.md b/docs/tutorials/pt/kabum-integration.md
index 8d9d571c1..970d0675a 100644
--- a/docs/tutorials/pt/kabum-integration.md
+++ b/docs/tutorials/pt/kabum-integration.md
@@ -61,9 +61,7 @@ Para configurar uma nova chave, siga os passos abaixo:
 
 Aguarde a chave porque ela será utilizada na etapa [Envio de informações para o KaBuM!](#envio-de-informacoes-para-o-kabum)
 
-<div class="alert alert-warning">
-A chave de acesso gerada só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em um local seguro.
-</div>
+>⚠️ A chave de acesso gerada só aparece para o usuário esta única vez, não é possível recuperar a informação pelo sistema posteriormente. Portanto, tenha a certeza de guardá-lo em um local seguro.
 
 ### Criar afiliado
 
diff --git a/docs/tutorials/pt/kit-registration.md b/docs/tutorials/pt/kit-registration.md
index 0969fb1da..0b067bdc7 100644
--- a/docs/tutorials/pt/kit-registration.md
+++ b/docs/tutorials/pt/kit-registration.md
@@ -70,9 +70,7 @@ Exemplo: um kit possui dois componentes. Considere que o componente 1 possui 30
 
 Os componentes do kit podem estar em estoques diferentes, contanto que eles sejam enviados a partir da mesma doca. Se não saírem pela mesma doca, o kit inteiro se torna indisponível. 
 
-<div class="alert alert-info">
-<p>Este cenário não acontece com um kit look, pois o kit look pode ser vendido com os componentes que restaram no inventário, sem a necessidade de se ter todos os componentes do kit no inventário.</p>
-</div>
+>ℹ️ Este cenário não acontece com um kit look, pois o kit look pode ser vendido com os componentes que restaram no inventário, sem a necessidade de se ter todos os componentes do kit no inventário.
 
 ## Preço
 
diff --git a/docs/tutorials/pt/license-manager-resources.md b/docs/tutorials/pt/license-manager-resources.md
index ea2a5b181..982d9f1ff 100644
--- a/docs/tutorials/pt/license-manager-resources.md
+++ b/docs/tutorials/pt/license-manager-resources.md
@@ -19,10 +19,8 @@ A VTEX disponibiliza vários [perfis de acesso](https://help.vtex.com/pt/tutoria
 
 Por isso, a plataforma VTEX oferece a possibilidade de criar perfis de acessos customizados, permitindo que você escolha precisamente quais recursos poderão ser acessados por um dado perfil customizado. Abaixo, você encontra a descrição dos recursos da VTEX disponíveis para cada produto.
 
-<div class="alert alert-danger">
-  <p>O uso irrestrito de recursos aumenta o risco de ataques às lojas por vazamento de credenciais de login com acesso a recursos críticos.
-    Caso haja dúvidas sobre a descrição de um recurso específico, não hesite em nos contatar.</p>
-</div>
+>❗ O uso irrestrito de recursos aumenta o risco de ataques às lojas por vazamento de credenciais de login com acesso a recursos críticos.
+>     Caso haja dúvidas sobre a descrição de um recurso específico, não hesite em nos contatar.
 
 <iframe src="https://help.vtex.com/tables/resources/pt" title="Recursos do License Manager" frameBorder="0" width="100%" height="850"></iframe>
 
diff --git a/docs/tutorials/pt/limit-purchases-to-a-payment-method-through-checkout-customization.md b/docs/tutorials/pt/limit-purchases-to-a-payment-method-through-checkout-customization.md
index 04fdadcf2..5e49c289c 100644
--- a/docs/tutorials/pt/limit-purchases-to-a-payment-method-through-checkout-customization.md
+++ b/docs/tutorials/pt/limit-purchases-to-a-payment-method-through-checkout-customization.md
@@ -19,4 +19,4 @@ Recomendamos limitar compras a um meio de pagamento [por política comercial](/p
 
 Outra forma, talvez mais simples, é customizar o Checkout, de forma que o CSS omita os meios de pagamentos quando houver a utm correspondente.
 
-<div class="alert alert-danger">Mas vale lembrar que a VTEX não recomenda customizações no Checkout, uma vez que o SmartCheckout foi feito para maximizar a eficiência no fluxo de fechamento de compra.</div>
+>❗ Mas vale lembrar que a VTEX não recomenda customizações no Checkout, uma vez que o SmartCheckout foi feito para maximizar a eficiência no fluxo de fechamento de compra.
diff --git a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-sales-policy.md b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-sales-policy.md
index 0572ff94a..5d27dd1c5 100644
--- a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-sales-policy.md
+++ b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-sales-policy.md
@@ -19,21 +19,16 @@ A limitação no acesso de uma loja pode ser implementado por diversos motivos,
 
 Esse cenário pode ser atendido através do uso do Master Data v1 e da política comercial utilizada na loja.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Criando cluster de clientes
 
diff --git a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
index 38baf0407..9115972c6 100644
--- a/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
+++ b/docs/tutorials/pt/limiting-access-to-the-store-by-means-of-the-trade-policy.md
@@ -19,21 +19,16 @@ A limitação no acesso de uma loja pode ser implementado por diversos motivos,
 
 Esse cenário pode ser atendido através do uso do Master Data v1 e da política comercial utilizada na loja.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 ## Criar cluster de clientes
 
diff --git a/docs/tutorials/pt/lista-da-vez.md b/docs/tutorials/pt/lista-da-vez.md
index d358a427f..32f581d17 100644
--- a/docs/tutorials/pt/lista-da-vez.md
+++ b/docs/tutorials/pt/lista-da-vez.md
@@ -15,9 +15,7 @@ legacySlug: lista-da-vez
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>  
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).  
 
 O aplicativo **Lista da Vez** permite organizar a fila de atendimento dos vendedores e consultar campanhas, rankings e metas já cadastradas pela plataforma Indeva. Nele, é possível encontrar as seguintes abas:
 
@@ -61,9 +59,7 @@ Para encerrar o atendimento de um vendedor, clique no vendedor desejado ou arras
   - **Reserva de outro vendedor:** o atendimento estava reservado para outro vendedor.
 - **Múltiplos atendimentos:** o vendedor atendeu mais de um cliente durante um único atendimento. Nessa opção, é possível selecionar a quantidade de clientes atendidos.
 
-<div class="alert alert-info">
-  <p>Os motivos de movimentação de vendedores podem ser customizados conforme a necessidade da loja. Para editar essas opções, entre em contato com o suporte da plataforma Indeva.</p>
-</div>
+>ℹ️ Os motivos de movimentação de vendedores podem ser customizados conforme a necessidade da loja. Para editar essas opções, entre em contato com o suporte da plataforma Indeva.
 
 Selecione a opção desejada e clique em `Concluir` para finalizar.
 
diff --git a/docs/tutorials/pt/locations-details-page-beta.md b/docs/tutorials/pt/locations-details-page-beta.md
index 4c5744f39..67b8b1351 100644
--- a/docs/tutorials/pt/locations-details-page-beta.md
+++ b/docs/tutorials/pt/locations-details-page-beta.md
@@ -15,9 +15,7 @@ legacySlug: pagina-de-detalhes-da-localidade
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 No [módulo Localidades](https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy) do seu Admin VTEX, em **Envio > Localidades**, ao clicar sobre uma localidade você é direcionado para sua página de detalhes, como a imagem a seguir:
 
diff --git a/docs/tutorials/pt/locations-module-beta.md b/docs/tutorials/pt/locations-module-beta.md
index 88fe7097e..84bb518c5 100644
--- a/docs/tutorials/pt/locations-module-beta.md
+++ b/docs/tutorials/pt/locations-module-beta.md
@@ -15,9 +15,7 @@ legacySlug: modulo-localidades
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 As localidades são pontos físicos envolvidos no processo de [fulfillment](https://help.vtex.com/pt/tutorial/fulfillment-logistics-vtex--53udnvI5eBy8DKo8FOjMoP) de pedidos e englobam etapas como coleta, empacotamento, emissão de faturas, entre outros. Alguns exemplos de localidades são lojas físicas e centros de distribuição.
 
@@ -82,9 +80,7 @@ Para realizar a primeira etapa de **Configurações básicas**, siga os passos a
 4. Em **Identificação**, determine o nome da localidade sendo criada. Este nome é visível somente no seu Admin VTEX.
 5. Em **Seller**, selecione um seller para associar à localidade. O seller é quem possui os produtos sendo vendidos.
 
-  <div class="alert alert-warning">
-Cada localidade pode ser associada a um único seller.
-</div>
+  >⚠️ Cada localidade pode ser associada a um único seller.
 
 6. Em **Endereço**, defina o local físico onde se situa a localidade.
 7. Clique no botão `Próximo`.
@@ -180,9 +176,7 @@ Para ativar ou pausar várias localidades, realize os seguintes passos:
 
 A ação de excluir uma localidade é permanente e não pode ser desfeita. 
 
-<div class="alert alert-warning">
-Quando uma localidade é excluída, isso não tem efeito sobre o seller ao qual ela estava associada. Ou seja, o seller continua recebendo pedidos normalmente.
-</div>
+>⚠️ Quando uma localidade é excluída, isso não tem efeito sobre o seller ao qual ela estava associada. Ou seja, o seller continua recebendo pedidos normalmente.
 
 Você pode realizar esta ação de forma individual ou massiva. Para excluir uma única localidade, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/magento-suiteshare.md b/docs/tutorials/pt/magento-suiteshare.md
index 7a58e919b..cbc0f4acb 100644
--- a/docs/tutorials/pt/magento-suiteshare.md
+++ b/docs/tutorials/pt/magento-suiteshare.md
@@ -25,8 +25,6 @@ Na página seguinte, selecione **Visual** (Design) e então clique em **Cabeç
 
 Desça na página até encontrar o campo **Outros Scripts** e cole o código do VTEX Assisted Sales (SuiteShare) dentro dele. Não se esqueça de salvar as mudanças clicando no botão **Salvar Configurações**.
 
-<div class="alert alert-warning">
-  <p>Você pode localizar o script do VTEX Assisted Sales (SuiteShare) acessando respectivamente o menu: <b> Atrair > Chat > Editar > Instruções de instalação</b>.</p>
-</div>
+>⚠️ Você pode localizar o script do VTEX Assisted Sales (SuiteShare) acessando respectivamente o menu: ** Atrair > Chat > Editar > Instruções de instalação**.
 
 À partir de agora, aproveite todos os benefícios do chat no seu site.
diff --git a/docs/tutorials/pt/manage-the-sales-comissions-report.md b/docs/tutorials/pt/manage-the-sales-comissions-report.md
index c2a5c0d81..a0237e28a 100644
--- a/docs/tutorials/pt/manage-the-sales-comissions-report.md
+++ b/docs/tutorials/pt/manage-the-sales-comissions-report.md
@@ -21,9 +21,7 @@ Essa dinâmica acontece por conta do split de pagamento e você pode saber mais
 
 Neste artigo, explicaremos como gerar esse relatório de comissionamento e como agendar a criação recorrente do relatório de acordo com uma certa periodicidade.
 
-<div class="alert alert-warning">
-Antes de prosseguir para as configurações, verifique com o seu Customer Success Manager (CSM) se o relatório de comissionamento foi incorporado ao Admin da sua conta.
-</div>
+>⚠️ Antes de prosseguir para as configurações, verifique com o seu Customer Success Manager (CSM) se o relatório de comissionamento foi incorporado ao Admin da sua conta.
 
 ## Gere um relatório de comissionamento
 
@@ -45,23 +43,17 @@ Prossiga:
 7. Preencha o campo “Endereço de e-mail” com o __e-mail__ desejado.
 8. Clique no __botão azul__ __“Gerar”__.
 
-<div class="alert alert-danger">
-É obrigatório definir uma data inicial e uma data final. Caso contrário, o relatório de comissionamento não será criado.
-</div>
+>❗ É obrigatório definir uma data inicial e uma data final. Caso contrário, o relatório de comissionamento não será criado.
 
-<div class="alert alert-info">
-Caso você não queira receber o relatório por e-mail, basta não clicar na caixa de seleção “Receber no endereço de email”. 
-
-Clique diretamente no botão “Gerar”. Assim, será criado um link para download do relatório no Admin.
-</div>  
+>ℹ️ Caso você não queira receber o relatório por e-mail, basta não clicar na caixa de seleção “Receber no endereço de email”. 
+>
+> Clique diretamente no botão “Gerar”. Assim, será criado um link para download do relatório no Admin.  
 
 Desse modo, a mensagem “Seu relatório foi gerado com sucesso” será exibida na tela para indicar que a operação foi realizada corretamente. Além disso, o documento será enviado para a pasta “Downloads” do seu computador.  
 
 A criação do relatório pode demorar caso o volume de dados analisados seja extenso. Nesses casos, você pode acompanhar o processamento como na imagem abaixo. 
 
-<div class="alert alert-info">
-Sair da página não afetará a operação.
-</div>
+>ℹ️ Sair da página não afetará a operação.
 
 ![comissionamento PT](https://images.ctfassets.net/alneenqid6w5/7bWvI8TAgRPvtF4kr00TbC/6a3805d30656ad30c9afae6cb3079fce/comissionamento_PT.png)
 
@@ -73,13 +65,9 @@ Existem situações em que o marketplace precisa fazer a análise dos seus comis
 
 Por conta disso, você pode criar um agendamento para que o relatório será gerado automaticamente a cada período predeterminado de tempo.
 
-<div class="alert alert-warning">
-No módulo de Comissionamento, só é permitido criar apenas um agendamento por conta.
-</div>
+>⚠️ No módulo de Comissionamento, só é permitido criar apenas um agendamento por conta.
 
-<div class="alert alert-info">
-O agendamento é opcional. Não configurá-lo não afeta em nada a criação manual dos relatórios de comissionamento.
-</div>
+>ℹ️ O agendamento é opcional. Não configurá-lo não afeta em nada a criação manual dos relatórios de comissionamento.
 
 Considerando que você já está no módulo de Comissionamento, clique no botão “Agendar” do lado direito da tela. Semelhante à geração do relatório, será exibido um modal na tela.
 
diff --git a/docs/tutorials/pt/managing-content-per-binding.md b/docs/tutorials/pt/managing-content-per-binding.md
index a09ac7dc1..461daed04 100644
--- a/docs/tutorials/pt/managing-content-per-binding.md
+++ b/docs/tutorials/pt/managing-content-per-binding.md
@@ -27,6 +27,4 @@ Por meio do módulo Storefront no Admin, a VTEX permite que você faça isso. Co
 
 4. Crie, atualize ou/e exclua conteúdo para o *binding* e a localidade predefinidos e, em seguida, salve suas alterações.
 
-<div class="alert alert-warning">
-Ao editar um conteúdo de bloco, você não poderá alterar os dados de <i>binding</i> e localidade - os campos serão bloqueados. Se você deseja alterá-los durante o processo, salve ou descarte suas alterações primeiramente e retorne à página inicial do Site Editor.
-</div>
+>⚠️ Ao editar um conteúdo de bloco, você não poderá alterar os dados de <i>binding</i> e localidade - os campos serão bloqueados. Se você deseja alterá-los durante o processo, salve ou descarte suas alterações primeiramente e retorne à página inicial do Site Editor.
diff --git a/docs/tutorials/pt/managing-content-versions.md b/docs/tutorials/pt/managing-content-versions.md
index 7502b1525..8d2a6e66b 100644
--- a/docs/tutorials/pt/managing-content-versions.md
+++ b/docs/tutorials/pt/managing-content-versions.md
@@ -49,14 +49,12 @@ Depois de [criar uma nova versão de conteúdo](#criando-uma-nova-versão-de-con
 
 3. Escolha o conteúdo que deseja ativar e clique em `Mais opções`> **Ativar**.
 
-<div class="alert alert-warning">
-  <p>Ao acessar <i>Aplicar para</i>, a opção <i>esta URL<i> sempre aparecerá acima de <i>este template<i>. Isso significa que caso o bloco tenha duas versões, cada uma com uma opção diferente de aplicação, o usuário só conseguirá reativar a versão aplicada em template se excluir a versão aplicada por URL.</p>
-
-Após clicar em `mais opções`> **Ativar**, você terá publicado o novo conteúdo em sua loja.
-
-<div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
-Você só pode ter um conteúdo ativo por vez. Se você ativar um conteúdo, os outros serão desativados.
-</div>
+>⚠️ Ao acessar <i>Aplicar para</i>, a opção <i>esta URL<i> sempre aparecerá acima de <i>este template<i>. Isso significa que caso o bloco tenha duas versões, cada uma com uma opção diferente de aplicação, o usuário só conseguirá reativar a versão aplicada em template se excluir a versão aplicada por URL.
+>
+> Após clicar em `mais opções`> **Ativar**, você terá publicado o novo conteúdo em sua loja.
+>
+> <div>
+> Você só pode ter um conteúdo ativo por vez. Se você ativar um conteúdo, os outros serão desativados.
 
 ## Agendando atualizações de conteúdo
 
diff --git a/docs/tutorials/pt/managing-delivery-capacity-beta.md b/docs/tutorials/pt/managing-delivery-capacity-beta.md
index d5e591798..e33451ac0 100644
--- a/docs/tutorials/pt/managing-delivery-capacity-beta.md
+++ b/docs/tutorials/pt/managing-delivery-capacity-beta.md
@@ -15,15 +15,11 @@ legacySlug: gerenciar-capacidade-de-entrega-beta
 subcategory: 
 ---
 
-<div class="alert alert-warning">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>⚠️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Você pode acompanhar a disponibilidade de janelas de entrega e a quantidade de itens/pedidos que ainda podem ser realizados em cada janela de entrega através da página de Capacidade de entrega.
 
-<div class="alert alert-warning">
-Para gerenciar sua capacidade de entrega você precisa ter políticas de envio previamente cadastradas, entrega agendada habilitada e capacidade de entrega previamente configurada. Leia [Política de envio](colocarlink) e [Entrega agendada](colocarlink) para saber como realizar este cadastro e configuração.
-</div>
+>⚠️ Para gerenciar sua capacidade de entrega você precisa ter políticas de envio previamente cadastradas, entrega agendada habilitada e capacidade de entrega previamente configurada. Leia [Política de envio](colocarlink) e [Entrega agendada](colocarlink) para saber como realizar este cadastro e configuração.
 O gerenciamento da capacidade de entrega é feito no menu **Estoque & Entrega > Capacidade de entrega** no Admin. 
 
 Ao clicar em Capacidade de entrega, você verá uma página que contém uma lista das janelas de entrega da sua loja. A lista apresentada se refere à política de envio selecionada no filtro Política de envio e ao período selecionado no filtro Data.
@@ -37,6 +33,4 @@ Uma vez selecionada a política de envio e a data a serem apresentadas na lista,
 *   **Disponível**: quantos itens/pedidos ainda estão disponíveis para agendamento (a quantidade de capacidade menos reservado)
 *   **Status**: pode ser visível ou não visível, dependendo da janela de entrega ainda está disponível. A janela ficará com status visível para seus clientes se ela ainda estiver disponível.
 
-<div class="alert alert-info">
-Você pode clicar em EDITAR POLÍTICA DE ENVIO para ser redirecionado à tela de edição da política de envio selecionada no filtro Política de envio.
-</div>
+>ℹ️ Você pode clicar em EDITAR POLÍTICA DE ENVIO para ser redirecionado à tela de edição da política de envio selecionada no filtro Política de envio.
diff --git a/docs/tutorials/pt/managing-delivery-capacity.md b/docs/tutorials/pt/managing-delivery-capacity.md
index 867c02c4e..845ba3a68 100644
--- a/docs/tutorials/pt/managing-delivery-capacity.md
+++ b/docs/tutorials/pt/managing-delivery-capacity.md
@@ -19,9 +19,9 @@ Você pode acompanhar a disponibilidade de janelas de entrega e a quantidade de
 
 Para gerenciar sua **Capacidade de entrega**, você precisa ter [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) previamente cadastradas, [Entrega agendada](https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) habilitada e capacidade de entrega previamente configurada.
 
-<div class="alert alert-warning">
-Para que a <a href="https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> e a <a href="https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidade de entrega</a> funcionem corretamente, você deve observar que:<p><ul><li>A soma {<a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID da política de envio} não pode exceder 60 caracteres.</li><li>Não se deve utilizar espaçamento no ID de <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">políticas de envio</a>.</li></ul></p>
-</div>
+>⚠️ Para que a [Entrega agendada](https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) e a [Capacidade de entrega](https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) funcionem corretamente, você deve observar que:
+> *A soma {[account name](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {ID da política de envio} não pode exceder 60 caracteres.
+> * Não se deve utilizar espaçamento no ID de [políticas de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 No Admin VTEX, acesse **Envio > Capacidade de entrega** ou digite **Capacidade de entrega** na barra de busca no topo da página. A **Capacidade de entrega** contém uma lista das janelas de entrega da sua loja, sendo essa lista referente à política de envio selecionada no filtro `Política de envio` e ao período selecionado no filtro `Data`.
 
diff --git a/docs/tutorials/pt/managing-http-headers.md b/docs/tutorials/pt/managing-http-headers.md
index 9c583049c..cf91dc8c4 100644
--- a/docs/tutorials/pt/managing-http-headers.md
+++ b/docs/tutorials/pt/managing-http-headers.md
@@ -45,9 +45,7 @@ Veja abaixo os cabeçalhos que aceitam edição:
 
 É possível configurar um cabeçalho personalizado, ou seja, um valor que não padronizado e é específico para os requisitos ou as funcionalidades específicas da loja.
 
-<div class="alert alert-warning">
-Cada conta só pode adicionar um único cabeçalho personalizado.
-</div>
+>⚠️ Cada conta só pode adicionar um único cabeçalho personalizado.
 
 Se você precisar configurar um cabeçalho personalizado, abra um ticket para o Suporte da VTEX, fornecendo as chaves e os valores a serem definidos, pois você será totalmente responsável por essas informações. Consulte a documentação do MDN sobre [cabeçalhos](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers) para usar como guia.
 
diff --git a/docs/tutorials/pt/managing-loading-docks.md b/docs/tutorials/pt/managing-loading-docks.md
index 1aac2ee08..0f706d9f4 100644
--- a/docs/tutorials/pt/managing-loading-docks.md
+++ b/docs/tutorials/pt/managing-loading-docks.md
@@ -17,9 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 A doca é uma das etapas logísticas da sua loja. Ela é um ponto intermediário entre o estoque e a transportadora, funcionando como área de escoamento de produtos. As docas recebem itens vindos de estoques ou centros de distribuição, e entrega às transportadoras para que a entrega seja feita ao destinatário final. 
 
-<div class="alert alert-info">
-Para saber mais sobre o que é uma doca para a VTEX, consulte o artigo de <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">Doca</a>.
-</div>
+>ℹ️ Para saber mais sobre o que é uma doca para a VTEX, consulte o artigo de [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
 
 Este artigo contém as informações necessárias para:
 
@@ -30,17 +28,18 @@ Este artigo contém as informações necessárias para:
 
 É importante saber que para ter uma doca configurada corretamente é preciso: criar a doca, preencher os campos de cadastro (que determinaram horário de funcionamento, prioridade), e também associar a doca a [política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE), ao estoque e a [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140?&utm_source=autocomplete). 
 
-<div class="alert alert-warning">
-A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de Envio;</a></li>
-<li>Doca;</li>
-<li>Estoque.</li>
-</ol>
-</body>
-</div>
+>⚠️ A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
+> <body>
+>
+> [Política Comercial;](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. [Política de Envio;](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
+>
+> Doca;
+>
+> Estoque.
+>
+> </body>
 
 ## Cadastrar
 
diff --git a/docs/tutorials/pt/managing-page-and-template-content.md b/docs/tutorials/pt/managing-page-and-template-content.md
index 2f787743f..4fddbc601 100644
--- a/docs/tutorials/pt/managing-page-and-template-content.md
+++ b/docs/tutorials/pt/managing-page-and-template-content.md
@@ -34,9 +34,7 @@ Exercite sua autonomia sobre o código e construa o cenário de loja desejado de
 
 2. Clique em `Versões` no canto superior direito.
 
-<div class="alert alert-info">
-O conteúdo que você vê ao clicar em um bloco é o que está ativo no momento. Para mais informações sobre o recurso <b>Versões</b>, acesse <a href="https://help.vtex.com/pt/tutorial/managing-content-versions--4loXo98CZncY0NnjKrScbG">Gerenciando versões de conteúdo</a> e <a href="https://help.vtex.com/pt/tutorial/scheduling-content-updates--5L93gED3wgSRoWpFJlJ2ns">Agendando atualizações de conteúdo</a>
-</div>
+>ℹ️ O conteúdo que você vê ao clicar em um bloco é o que está ativo no momento. Para mais informações sobre o recurso **Versões**, acesse [Gerenciando versões de conteúdo](https://help.vtex.com/pt/tutorial/managing-content-versions--4loXo98CZncY0NnjKrScbG) e [Agendando atualizações de conteúdo](https://help.vtex.com/pt/tutorial/scheduling-content-updates--5L93gED3wgSRoWpFJlJ2ns)
 
 3. Clique no botão `Novo conteúdo`.
 4. Faça as alterações desejadas de acordo com as configurações disponíveis para o bloco.
diff --git a/docs/tutorials/pt/managing-pages.md b/docs/tutorials/pt/managing-pages.md
index 29f36f95a..8f5dc603f 100644
--- a/docs/tutorials/pt/managing-pages.md
+++ b/docs/tutorials/pt/managing-pages.md
@@ -34,9 +34,7 @@ No **Headless CMS**, você pode gerenciar todas as rotas de URL e modelos de pá
 Para criar e gerenciar uma página, siga estas etapas:
 
 1. No Admin VTEX, acesse **Headless CMS**.
-<div class="alert alert-warning">
-  Certifique-se de estar no projeto correto. Caso contrário, vá até o menu <b>Projeto</b> no canto superior esquerdo, selecione o nome do projeto em que deseja criar a página e continue no passo 2.
-</div>
+>⚠️ Certifique-se de estar no projeto correto. Caso contrário, vá até o menu **Projeto** no canto superior esquerdo, selecione o nome do projeto em que deseja criar a página e continue no passo 2.
 2. Clique em `Criar documento` e selecione o tipo de página desejado. 
 
 3. Em `Untitled`, nomeie a página.
diff --git a/docs/tutorials/pt/managing-projects.md b/docs/tutorials/pt/managing-projects.md
index 6a3a7652d..ac99542db 100644
--- a/docs/tutorials/pt/managing-projects.md
+++ b/docs/tutorials/pt/managing-projects.md
@@ -23,9 +23,7 @@ Cada projeto tem suas configurações, conteúdo e marca personalizados de acord
 
 Neste guia, você aprenderá como gerenciar cada projeto de frontend da sua loja.
 
-<div class="alert alert-warning">
-  <a href="https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview"> FastStore WebOps usuários</a>:As alterações feitas pelo Headless CMS no VTEX Admin, como a criação de novos tipos de conteúdo (content types), a adição de seções ou a atualização de campos, podem não aparecer automaticamente na loja uma vez que você as publique. Isso é um problema conhecido, e você deve entrar em contato com sua equipe de desenvolvimento para implementar a solução necessária. Para instruções detalhadas, consulte o artigo de problema conhecido <a href="https://help.vtex.com/pt/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW"> O aplicativo WebOps não está totalmente integrado com o Headless CMS</a>.
-</div>
+>⚠️ [ FastStore WebOps usuários](https://developers.vtex.com/docs/guides/faststore/1-onboarding-overview):As alterações feitas pelo Headless CMS no VTEX Admin, como a criação de novos tipos de conteúdo (content types), a adição de seções ou a atualização de campos, podem não aparecer automaticamente na loja uma vez que você as publique. Isso é um problema conhecido, e você deve entrar em contato com sua equipe de desenvolvimento para implementar a solução necessária. Para instruções detalhadas, consulte o artigo de problema conhecido [ O aplicativo WebOps não está totalmente integrado com o Headless CMS](https://help.vtex.com/pt/known-issues/webops-app-is-not-fully-integrated-with-headless-cms--577fIocKB9BYYCOkN9dZfW).
 
 ## Antes de começar
 Certifique-se de que os [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) `See CMS menu on the top-bar`, `Settings` e `CMS GraphQL API` estão associados ao seu [Perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc?&utm_source=autocomplete). Do contrário, [crie um perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#criando-um-perfil-de-acesso) e adicione esses recursos a eles ou adicione esses recursos a um perfil de acesso existente.
diff --git a/docs/tutorials/pt/managing-redirects-per-binding.md b/docs/tutorials/pt/managing-redirects-per-binding.md
index 5e5692be4..0b7aebfe1 100644
--- a/docs/tutorials/pt/managing-redirects-per-binding.md
+++ b/docs/tutorials/pt/managing-redirects-per-binding.md
@@ -50,17 +50,13 @@ No Admin VTEX:
 
 ![pt-redirectdelete](https://images.ctfassets.net/alneenqid6w5/3dRsZxKTYJTaOPrm6rBU84/3e5a9c1f27986e34fa7fd7b32f1a636e/pt-redirectdelete.png)
 
-<div class="alert alert-warning">
-Um <i>bug</i> pode ser encontrado ao tentar clicar em redirecionamentos com parâmetros de consulta na URL (<i>query strings</i>). O time de produto da VTEX já está ciente do comportamento inesperado e trabalhando na correção. Caso você não consiga clicar no redirecionamento desejado para excluí-lo, prefira fazê-lo por meio da importação da planilha enquanto o problema não é resolvido.
-</div>
+>⚠️ Um <i>bug</i> pode ser encontrado ao tentar clicar em redirecionamentos com parâmetros de consulta na URL (<i>query strings</i>). O time de produto da VTEX já está ciente do comportamento inesperado e trabalhando na correção. Caso você não consiga clicar no redirecionamento desejado para excluí-lo, prefira fazê-lo por meio da importação da planilha enquanto o problema não é resolvido.
 
 ## Importando e exportando redirecionamentos
 
 Para gerenciar em massa os redirecionamentos da sua loja, você pode usar uma planilha de importação e exportação.
 
-<div class="alert alert-warning">
-Os redirecionamentos listados na planilha serão obrigatoriamente criados ou excluídos da lista de redirecionamentos da loja - não é possível criar <i>e</i> excluir redirecionamentos usando a mesma planilha. Antes de preencher e enviar a sua planilha no admin, tenha em mente seu objetivo final com ela.
-</div>
+>⚠️ Os redirecionamentos listados na planilha serão obrigatoriamente criados ou excluídos da lista de redirecionamentos da loja - não é possível criar <i>e</i> excluir redirecionamentos usando a mesma planilha. Antes de preencher e enviar a sua planilha no admin, tenha em mente seu objetivo final com ela.
 
 1. Clique no botão `Importar` e depois em` Baixar modelo`. Clique no botão `Exportar` se desejar fazer o download da lista de redirecionamentos pré-salva na loja e modificá-la.
 2. Abra a planilha assim que o *download* for concluído e preencha as células das colunas de acordo com a tabela abaixo:
@@ -79,9 +75,7 @@ Os redirecionamentos listados na planilha serão obrigatoriamente criados ou exc
 
 ![pt-planilharedirect](https://images.ctfassets.net/alneenqid6w5/1Vjku4KoOrCbO7mcdehcCt/e7979dca1ef4b2f159bb3c09a42d9716/pt-planilharedirect.png)
 
-<div class="alert alert-warning">
-Ao clicar no botão <code>Salvar</code>, você criará todos os redirecionamentos listados em sua planilha, ao passo que clicar no botão <code>Excluir</couirde> removerá todos eles do banco de dados de redirecionamentos da sua loja.
-</div>
+>⚠️ Ao clicar no botão `Salvar`, você criará todos os redirecionamentos listados em sua planilha, ao passo que clicar no botão <code>Excluir</couirde> removerá todos eles do banco de dados de redirecionamentos da sua loja.
 
 6. Carregue a planilha a partir dos seus arquivos locais.
 7. Clique no botão `Importar arquivo`.
diff --git a/docs/tutorials/pt/managing-shipping-policies.md b/docs/tutorials/pt/managing-shipping-policies.md
index 9c5a7a45a..15d52a23e 100644
--- a/docs/tutorials/pt/managing-shipping-policies.md
+++ b/docs/tutorials/pt/managing-shipping-policies.md
@@ -105,9 +105,7 @@ Para ativar ou desativar uma política de envio, realize os passos abaixo:
 
 Para excluir uma política de envio, realize os passos abaixo:
 
-<div class="alert alert-danger">
-A ação de excluir uma política de envio é permanente e não pode ser desfeita.
-</div>
+>❗ A ação de excluir uma política de envio é permanente e não pode ser desfeita.
 
 1. No Admin VTEX, acesse **Envio > Estratégia de Envio** ou digite **Estratégia de envio** na barra de busca no topo da página.
 2. Na aba **Políticas de envio**, na linha correspondente à política desejada, clique no ícone menu <i class="fas fa-ellipsis-v"></i>. Você pode [pesquisar](#pesquisar-politica-de-envio) ou [filtrar](#filtrar-politicas-de-envio) políticas.
diff --git a/docs/tutorials/pt/managing-shipping-rates.md b/docs/tutorials/pt/managing-shipping-rates.md
index 50f20addf..4b3817ee4 100644
--- a/docs/tutorials/pt/managing-shipping-rates.md
+++ b/docs/tutorials/pt/managing-shipping-rates.md
@@ -22,9 +22,7 @@ As [tarifas de envio](https://help.vtex.com/pt/tutorial/tarifas-de-envio--1Balpg
 * [Editar](#editar) as tarifas de envio;
 * [Excluir](#excluir) as tarifas de envio.
 
-<div class="alert alert-info">
-Para casos em que há vários preços de envio para serem atualizados ou cadastrados, recomendamos utilizar a Planilha de frete em vez do módulo <b>Tarifas de envio</b>. Caso queira conferir como as tarifas de envio cadastradas serão apresentadas ao cliente final, utilize o módulo <b><a href="https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144">Simulador de envio</b></a>.
-</div>
+>ℹ️ Para casos em que há vários preços de envio para serem atualizados ou cadastrados, recomendamos utilizar a Planilha de frete em vez do módulo **Tarifas de envio**. Caso queira conferir como as tarifas de envio cadastradas serão apresentadas ao cliente final, utilize o módulo **[Simulador de envio**](https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144).
 
 ## Cadastrar
 
diff --git a/docs/tutorials/pt/managing-singleton-content-types.md b/docs/tutorials/pt/managing-singleton-content-types.md
index 67ca53215..c52ca3a2a 100644
--- a/docs/tutorials/pt/managing-singleton-content-types.md
+++ b/docs/tutorials/pt/managing-singleton-content-types.md
@@ -20,18 +20,14 @@ Content types do tipo Singleton permitem a criação e o gerenciamento de uma ú
 Esse content type evita conflitos e inconsistências que podem ocorrer quando várias páginas do mesmo content type são criadas. Por exemplo, você poder usar o Singleton para a Página Inicial (Home) da sua loja, garantindo que exista apenas uma Página Inicial e todas as atualizações e solicitações feitas a essa página sempre retornem o mesmo resultado.
 ![singleton-br](https://images.ctfassets.net/alneenqid6w5/6aMWhl66yiP8YLJr5Bzuo5/7030fc9c4424018f377c56ad3c02c25e/singleton-br.gif)
 
-<div class="alert alert-warning">
-Para criar um content type Singleton, verifique com o seu time de desenvolvimento se a propriedade <i>isSingleton</i> já está implementada ou peça para que o time siga as intruções em <a href="https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type">Using isSingleton in a content type</a> para adicioná-la ao content type desejado.
-</div>
+>⚠️ Para criar um content type Singleton, verifique com o seu time de desenvolvimento se a propriedade <i>isSingleton</i> já está implementada ou peça para que o time siga as intruções em [Using isSingleton in a content type](https://v1.faststore.dev/how-to-guides/cms/vtex-headless-cms/Using%20isSingleton%20property%20in%20a%20contenty%20type) para adicioná-la ao content type desejado.
 
 ## Criando o Singleton
 1. Acesse o **Admin > Storefront > Headless CMS**.
 2. Selecione `CRIAR NOVO` e escolha o nome do content type singleton, por exemplo, **Home**.
 3. Edite a página como desejar com novas seções.
 
-<div class="alert alert-warning">
-É possível criar o Singleton apenas uma vez. Se você já criou a página Singleton, ela não aparecerá mais na lista de content types.
-</div>
+>⚠️ É possível criar o Singleton apenas uma vez. Se você já criou a página Singleton, ela não aparecerá mais na lista de content types.
 
 Após terminar de editar a página, você pode publicar o conteúdo selecionando `Publicar` ou salvando a página como rascunho.
 Para editar ou excluir um conteúdo, verifique as seções a seguir.
@@ -47,9 +43,7 @@ Para editar ou excluir um conteúdo, verifique as seções a seguir.
 2. Clique no projeto em que o Singleton foi criado.
 3. Clique em `Despublicar` > `Despublicar agora`.
 
-<div class="alert alert-warning">
-Antes de despublicar, certifique-se de que não há nenhum rascunho existente. Caso contrário, não será possível continuar. Se houver rascunhos, exclua-os ou agende-os para publicação.
-</div>
+>⚠️ Antes de despublicar, certifique-se de que não há nenhum rascunho existente. Caso contrário, não será possível continuar. Se houver rascunhos, exclua-os ou agende-os para publicação.
 
 4. Uma mensagem pop-up aparecerá para você confirmar a despublicação da página.
 5. Mantenha o botão `DESPUBLICAR` clicado para despublicar o conteúdo.
@@ -58,7 +52,5 @@ Antes de despublicar, certifique-se de que não há nenhum rascunho existente. C
 1. Na página do Singleton, selecione `mais`(menu kebab) e clique `Excluir`.
 2. Clique  `EXCLUIR` e, depois, clique em `VOLTAR PARA PÁGINAS`. 
 
-<div class="alert alert-warning">
-  Se você deseja restaurar a página e seu conteúdo, clique <i>RESTAURAR</i>.
-</div>
+>⚠️ Se você deseja restaurar a página e seu conteúdo, clique <i>RESTAURAR</i>.
 
diff --git a/docs/tutorials/pt/managing-stock-items.md b/docs/tutorials/pt/managing-stock-items.md
index 075a46247..da64bf779 100644
--- a/docs/tutorials/pt/managing-stock-items.md
+++ b/docs/tutorials/pt/managing-stock-items.md
@@ -22,9 +22,7 @@ Este artigo contém informações sobre a página **Gerenciamento de inventário
 * [As informações do inventário estão divididas](#informacoes-do-inventario).
 * [Os filtros de busca estão dispostos para facilitar a procura de SKUs específicos](#filtros-de-busca).
 
-<div class="alert alert-info"> 
-Para acessar o inventário utilizando SKUs, docas ou estoques via API, utilize a <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-"> Inventory API </a>.
-</div>
+>ℹ️ Para acessar o inventário utilizando SKUs, docas ou estoques via API, utilize a [ Inventory API ](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 Outras ações possíveis na página **Gerenciamento de inventário** são:
 
@@ -50,9 +48,7 @@ No Admin VTEX, acesse **Catálogo > Inventário > Gerenciamento de inventário**
     * **Estoque infinito:** permite registrar unidades infinitas do SKU, fazendo com que ele esteja sempre disponível para o checkout da sua loja. Isso descarta a necessidade de atualização da contagem desse SKU.
     * **Lead time (dias):** configuração opcional do tempo de envio a nível de SKU. Defina um tempo para o SKU de um estoque e ele será considerado no [cálculo](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-envio--tutorials_116) do tempo de envio do pedido. Por padrão, o [lead time](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B) vem definido como zero dias e sua contagem é feita em dias úteis. Você pode alterar a [contagem para dias corridos](https://help.vtex.com/pt/tutorial/lead_time-shipping-time-at-sku-level--16yv5Mkj6bTyWR1hCN2f4B#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional) e, se desejar configurar horas, minutos e segundos, pode usar o endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
-<div class="alert alert-warning">
-Para garantir que os itens adicionados ao estoque fiquem disponíveis para venda na loja, o ID dos SKUs não deve conter o número zero à esquerda. O sistema não reconhece, por exemplo, IDs no formato <code>01, 02, 021,</code> pois é esperado o formato<code> 1, 2, 21</code>.
-</div>
+>⚠️ Para garantir que os itens adicionados ao estoque fiquem disponíveis para venda na loja, o ID dos SKUs não deve conter o número zero à esquerda. O sistema não reconhece, por exemplo, IDs no formato `01, 02, 021,` pois é esperado o formato` 1, 2, 21`.
 
 A quantidade total de itens na página **Gerenciamento de inventário** é atualizada em tempo real, mas pode haver um atraso de até 1 hora para a informação aparecer no [registro de atualizações](https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2).
 
@@ -68,9 +64,7 @@ Na **Gerenciamento de inventário**, para realizar uma busca pela barra, basta d
 
 *   **Estoque:** selecione um ou mais estoques desejados para retornar todos os itens presentes.
 
-<div class="alert alert-danger">
-A lista do inventário é limitada em até dez mil linhas. Isso significa que, mesmo que um SKU não esteja disponível na lista, ele pode ser encontrado ou acessado utilizando os filtros. O limite de linhas para o inventário melhorar a performance das consultas. Para acessar um SKU que não está disponível na página, busque ou utilize os filtros para maior precisão na busca.
-</div>
+>❗ A lista do inventário é limitada em até dez mil linhas. Isso significa que, mesmo que um SKU não esteja disponível na lista, ele pode ser encontrado ou acessado utilizando os filtros. O limite de linhas para o inventário melhorar a performance das consultas. Para acessar um SKU que não está disponível na página, busque ou utilize os filtros para maior precisão na busca.
 
 ## Artigos relacionados
 
diff --git a/docs/tutorials/pt/managing-url-redirects.md b/docs/tutorials/pt/managing-url-redirects.md
index 6025b5f78..4301d0bfe 100644
--- a/docs/tutorials/pt/managing-url-redirects.md
+++ b/docs/tutorials/pt/managing-url-redirects.md
@@ -50,7 +50,5 @@ Alguns editores, como o Google Sheets, exportam arquivos CSV utilizando vírgula
 
 Se deseja exportar seus redirecionamentos, clique em <i class="fas fa-download"></i> `Exportar` e eles serão baixados no seu computador. 
 
-<div class="alert alert-info">
-Não é possível criar redirecionamentos por meio de rotas pré-definidas como “home” "/", "login", "account", etc.). É recomendada a criação manual seguindo as instruções mencionadas acima.
-</div>
+>ℹ️ Não é possível criar redirecionamentos por meio de rotas pré-definidas como “home” "/", "login", "account", etc.). É recomendada a criação manual seguindo as instruções mencionadas acima.
 
diff --git a/docs/tutorials/pt/managing-users.md b/docs/tutorials/pt/managing-users.md
index 3c7c6f67b..f7695843b 100644
--- a/docs/tutorials/pt/managing-users.md
+++ b/docs/tutorials/pt/managing-users.md
@@ -21,9 +21,7 @@ Esta página mostra a lista de usuários com os respectivos __Nome__, __Email__
 
 ![Lista Usuários User Management PT](https://images.ctfassets.net/alneenqid6w5/1IjRv0l2rDBrSWtHj82CDm/3440b1f6633113c14bf91d9147d4eb0a/Lista_Usu__rios_User_Management_PT.png)
 
-<div class="alert alert-warning">
-Qualquer usuário que deseje gerenciar usuários ou chaves de aplicação deve ter um perfil que contenha o <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recurso</a> <b>Save User</b>. Você pode usar, por exemplo, o perfil predefinido <a href="https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted">User Administrator - RESTRICTED</a>.
-</div>
+>⚠️ Qualquer usuário que deseje gerenciar usuários ou chaves de aplicação deve ter um perfil que contenha o [recurso](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) **Save User**. Você pode usar, por exemplo, o perfil predefinido [User Administrator - RESTRICTED](https://help.vtex.com/pt/tutorial/predefined-roles--jGDurZKJHvHJS13LnO7Dy#user-administrator-restricted).
 
 ## Criar um novo usuário
 
diff --git a/docs/tutorials/pt/managing-warehouses.md b/docs/tutorials/pt/managing-warehouses.md
index ff7dfe514..95eeae9ae 100644
--- a/docs/tutorials/pt/managing-warehouses.md
+++ b/docs/tutorials/pt/managing-warehouses.md
@@ -18,9 +18,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 O estoque é o espaço físico de armazenamento do ecommerce. Na plataforma VTEX, você pode adicionar itens aos estoques cadastrados na sua loja. Com os itens em estoque, é possível controlar movimentações, disponibilidade e gerenciar o envio dos itens pelas docas e [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). 
 
-<div class="alert alert-info">
-Para entender melhor como a plataforma VTEX interpreta e define o funcionamento do estoque, consulte o artigo de <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a>.
-</div>
+>ℹ️ Para entender melhor como a plataforma VTEX interpreta e define o funcionamento do estoque, consulte o artigo de [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb).
 
 Além disso, é possível cadastrar o estoque, as docas que escoarão os produtos, o tempo que os itens levam para ser transportados do estoque até a doca e o valor cobrado por esse transporte.
 
@@ -31,17 +29,18 @@ Este artigo contém as informações necessárias para:
 * [Editar um estoque existente](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#editar-estoque).  
 * [Excluir um estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#excluir-estoque).  
 
-<div class="alert alert-warning">
-A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de Envio;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">Doca;</a></li>
-<li>Estoque.</li>
-</ol>
-</body>
-</div>
+>⚠️ A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
+> <body>
+>
+> [Política Comercial;](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. [Política de Envio;](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
+>
+> 3. [Doca;](https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)
+>
+> Estoque.
+>
+> </body>
 
 ## Cadastrar estoque
 
@@ -83,6 +82,4 @@ A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do
 3. No card do estoque desejado, selecione o <i class="fas fa-ellipsis-v"></i>.
 4. Selecione a opção `Deletar`.  
 
-<div class="alert alert-warning">
-Para adicionar itens ao estoque, é preciso cadastrar os itens primeiramente no catálogo. Depois de cadastrar os itens pelo <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catálogo</a>, e ter um estoque cadastrado, você deve associar os itens ao seu respectivo estoque pelo <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">gerenciamento de inventário</a>.
-</div>
+>⚠️ Para adicionar itens ao estoque, é preciso cadastrar os itens primeiramente no catálogo. Depois de cadastrar os itens pelo [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR), e ter um estoque cadastrado, você deve associar os itens ao seu respectivo estoque pelo [gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
diff --git a/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md b/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md
index fb43b7572..da211f5c9 100644
--- a/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md
+++ b/docs/tutorials/pt/manual-of-classes-and-methods-used-on-webservice.md
@@ -20,6 +20,8 @@ O manual das classes e métodos usados no Web Service é um material complementa
 [Download do manual de classes e métodos](https://assets.ctfassets.net/alneenqid6w5/4OdeCFbcVQtEgkuWsuuidl/80b79448cf2b327e07b567a8411afaa0/vtex_WebServiceGuide.pdf)
 
 
-<div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
-<p><strong>Todos os outros métodos estão descontinuados a partir de 28/02/2017.</strong></p>
-<p>Use as APIs REST equivalentes, disponíveis em nosso <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: somente os métodos SOAP pertinentes ao **catálogo** são válidos.
+>
+> **Todos os outros métodos estão descontinuados a partir de 28/02/2017.**
+>
+> Use as APIs REST equivalentes, disponíveis em nosso [Developer Docs](//help.vtex.com/developer-docs/).
diff --git a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
index 8a0402116..1c7566edd 100644
--- a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
+++ b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
@@ -15,9 +15,7 @@ legacySlug: mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta
 subcategory: 24EN0qRBg4yK0uusGUGosu
 ---
 
-<div class="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 A arquitetura de uma loja VTEX possibilita [anunciar e vender produtos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402) em outras lojas, sejam elas VTEX ou não. Ao vender produtos de outros sellers em seu ambiente, a loja VTEX se torna um [marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb). 
 
diff --git a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace.md b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace.md
index 90a6b0330..e6ea85120 100644
--- a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace.md
+++ b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace.md
@@ -53,9 +53,7 @@ Para preencher a planilha:
 4. Salve o __arquivo XLS__ da planilha.  
 5. Em *Mapear categorias*, envie a planilha atualizada pelo botão __Atualizar mapeamento de categorias__.   
 
-<div class="alert alert-info">
-Caso o programa utilizado para abrir a planilha utilize o padrão de separadores “;”, deve-se substituí-los para “,” antes de enviar o arquivo.
-</div>
+>ℹ️ Caso o programa utilizado para abrir a planilha utilize o padrão de separadores “;”, deve-se substituí-los para “,” antes de enviar o arquivo.
 
 ### Exemplo
 Neste exemplo, baixamos a planilha atual que veio com os seguintes valores em cada coluna:
@@ -74,9 +72,7 @@ Faremos o mapeamento das categorias do seller, buscando a melhor correspondênci
 | [3] Feminino\| <br>[28] Jeans                       | Jeans / Shorts            |                                    |
 | [3] Feminino\| <br>[28] Jeans                       | Jeans / Bermudas          |                                    |
 
-<div class="alert alert-info">
-Note que mais de uma categoria no catálogo do seller se encaixou na mesma categoria do marketplace (Feminino / Jeans). Nesse caso, duplique a linha correspondente em <b>Marketplace categories</b>, e cole os valores de <i>Unmapped categories</i> sent by seller em cada linha duplicada. 
-</div>
+>ℹ️ Note que mais de uma categoria no catálogo do seller se encaixou na mesma categoria do marketplace (Feminino / Jeans). Nesse caso, duplique a linha correspondente em **Marketplace categories**, e cole os valores de <i>Unmapped categories</i> sent by seller em cada linha duplicada.
 
 ## Mapeamento de marcas
 Depois que o seller completar o [envio de produtos para o Marketplace](https://help.vtex.com/pt/tutorial/entendendo-a-catalogacao-de-produtos-para-o-marketplace), é necessário que o marketplace faça o mapeamento de marcas. A correspondência entre marcas do marketplace e as marcas do seller é feita através de uma planilha.
@@ -96,9 +92,7 @@ Você pode baixar o modelo atualizado da planilha no botão **Baixar tabela atua
 4. Salve o __arquivo XLS__ da planilha.    
 5. Em *Mapear marca*s, envie a planilha atualizada pelo botão __Atualizar mapeamento de marcas__.     
 
-<div class="alert alert-info">
-Caso o programa utilizado para abrir a planilha utilize o padrão de separadores “;”, deve-se substituí-los para “,” antes de importar o arquivo.
-</div>
+>ℹ️ Caso o programa utilizado para abrir a planilha utilize o padrão de separadores “;”, deve-se substituí-los para “,” antes de importar o arquivo.
 
 ### Exemplo
 Neste exemplo, baixamos a planilha atual que veio com os seguintes valores em cada coluna:
diff --git a/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md b/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md
index 4f08189da..8efb8a3a8 100644
--- a/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md
+++ b/docs/tutorials/pt/mapping-mercado-livre-categories-variations-and-attributes.md
@@ -15,9 +15,7 @@ legacySlug: mapeamento-de-categorias-variacoes-e-atributos-do-mercado-libre
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-Se você enviará seus produtos para o Mercado Livre pela primeira vez, recomendamos usar a <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA">nova interface de Mapeamento de Categorias.</a>
-</div>
+>ℹ️ Se você enviará seus produtos para o Mercado Livre pela primeira vez, recomendamos usar a [nova interface de Mapeamento de Categorias.](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA)
 
 Depois de fazer as [configurações iniciais para a integração com o Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/15NZiQstCET8zyQUIa7nhw), é preciso categorizar e enviar as variações e atributos dos produtos e enviá-las para o marketplace. O envio dessas informações é feito por meio do upload da planilha de mapeamento, que faz a equivalência entre as categorias, variações e atributos da sua loja e os padrões adotados pelo Mercado Livre.
 
@@ -184,6 +182,4 @@ Ao concluir as etapas de preenchimento da planilha de mapeamento, você deve seg
 
 Com o upload concluído, a integração envia automaticamente todos os produtos das categorias usadas na planilha para o Mercado Livre.
 
-<div class="alert alert-warning">
-Caso, após subir uma planilha, você tente fazer upload de outra, saiba que a planilha nova irá substituir a antiga. Por isso, recomendamos fazer upload da nova planilha, contendo os dados antigos e os novos.
-</div>
+>⚠️ Caso, após subir uma planilha, você tente fazer upload de outra, saiba que a planilha nova irá substituir a antiga. Por isso, recomendamos fazer upload da nova planilha, contendo os dados antigos e os novos.
diff --git a/docs/tutorials/pt/marketplace-invited-sellers.md b/docs/tutorials/pt/marketplace-invited-sellers.md
index 15fce3d25..9b77d043c 100644
--- a/docs/tutorials/pt/marketplace-invited-sellers.md
+++ b/docs/tutorials/pt/marketplace-invited-sellers.md
@@ -48,10 +48,8 @@ O convite é feito por meio de um link enviado por email ao seller, que contém
 
 O seller receberá por email o convite para vender em seu marketplace. 
 
-<div class="alert alert-info">
-O link enviado por email para o seller é válido por 7 dias. Uma vez aberto, o seller tem seis horas para completar o formulário de cadastro, sem interrupções. 
-Caso não seja possível concluir o cadastro nesse período, o marketplace precisa enviar o convite novamente. Isso pode ser feito acessando o módulo MARKETPLACE > Convidar sellers > selecione o seller na lista > clique no botão  <i class="fas fa-paper-plane"></i> Reenviar convite. 
-</div>
+>ℹ️ O link enviado por email para o seller é válido por 7 dias. Uma vez aberto, o seller tem seis horas para completar o formulário de cadastro, sem interrupções. 
+> Caso não seja possível concluir o cadastro nesse período, o marketplace precisa enviar o convite novamente. Isso pode ser feito acessando o módulo MARKETPLACE > Convidar sellers > selecione o seller na lista > clique no botão  <i class="fas fa-paper-plane"></i> Reenviar convite.
 
 ## Conectar seller
 
diff --git a/docs/tutorials/pt/marketplace-strategies-at-vtex.md b/docs/tutorials/pt/marketplace-strategies-at-vtex.md
index ba6386423..6056c5e9c 100644
--- a/docs/tutorials/pt/marketplace-strategies-at-vtex.md
+++ b/docs/tutorials/pt/marketplace-strategies-at-vtex.md
@@ -34,9 +34,7 @@ O sortimento de produtos enviados para um marketplace é definido na escolha da
 
 A [contratação de políticas comerciais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) adicionais é realizada via ticket em nosso [suporte](https://help.vtex.com/pt/support), selecionando a opção **Comercial** e o tipo de solicitação Criação de Política Comercial. Para cada política comercial adicional, é cobrado um valor mensal, seja ela utilizada para integração com marketplaces certificados, parceiros, externos ou VTEX.
 
-<div class="alert alert-info">
-Pedidos aprovados em marketplaces estão sujeitos às mesmas <a href="https://help.vtex.com/pt/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt">regras contratuais</a> de pedidos efetuados por outros canais.
-</div>
+>ℹ️ Pedidos aprovados em marketplaces estão sujeitos às mesmas [regras contratuais](https://help.vtex.com/pt/tutorial/o-que-a-vtex-considera-como-receita-para-apuracao--58j4cfoXfisWyemASACwSq?locale=pt) de pedidos efetuados por outros canais.
 
 Os próximos cenários abordados neste artigo são:  
 
@@ -109,9 +107,7 @@ Pode ser que sua loja queira vender em um marketplace que não possua conexão c
 
 Marketplaces certificados são aqueles cuja integração foi desenvolvida pelo time de desenvolvedores da VTEX. A política comercial adicional contratada para esse tipo de integração, está isenta da taxa mensal se houver pedidos atrelados à política através do marketplace certificado e pagará apenas o take rate dos pedidos.
 
-<div class="alert alert-warning">
-As políticas comerciais adicionais contratadas para integração com marketplaces certificados que forem utilizadas também em integração com outros tipos de marketplaces, está sujeita à cobrança da taxa mensal.
-</div>  
+>⚠️ As políticas comerciais adicionais contratadas para integração com marketplaces certificados que forem utilizadas também em integração com outros tipos de marketplaces, está sujeita à cobrança da taxa mensal.  
 
 Atualmente, na plataforma VTEX você encontra os seguintes marketplaces certificados:  
 
@@ -165,9 +161,7 @@ Abaixo você encontra os marketplaces parceiros disponíveis no catálogo da VTE
 - Fast Shop  
 - Hubplus  
 
-<div class="alert alert-info">
-O Facebook, Google Shopping, Google Shopping Ads e Tik Tok não são marketplaces, porém oferecerem uma experiência similar de envio de produtos a partir de lojas VTEX.
-</div>
+>ℹ️ O Facebook, Google Shopping, Google Shopping Ads e Tik Tok não são marketplaces, porém oferecerem uma experiência similar de envio de produtos a partir de lojas VTEX.
 
 ### Ser um seller VTEX
 
@@ -179,7 +173,5 @@ A configuração da [integração entre lojas VTEX](https://help.vtex.com/pt/tut
 
 O [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é uma edição da plataforma VTEX voltada para sellers se conectarem e venderem seus produtos em marketplaces hospedados na VTEX. Com o portal, sellers acessam todas as funcionalidades essenciais para a operação de ecommerce em grandes vitrines, trazendo visibilidade e conversão de vendas.
 
-<div class="alert alert-info">
-Na VTEX, é possível atuar como <a href="https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa">seller white label</a>, um seller não identificado pelo consumidor na experiência de compra. Este tipo de seller é o padrão para <a href="https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">contas franquia</a>, por exemplo, e pode ser estratégico para determinados modelos de negócio. Para saber mais, veja o artigo <a href="https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78">Escolher entre conta padrão, conta franquia ou Seller Portal</a>.
-</div>
+>ℹ️ Na VTEX, é possível atuar como [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa), um seller não identificado pelo consumidor na experiência de compra. Este tipo de seller é o padrão para [contas franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl), por exemplo, e pode ser estratégico para determinados modelos de negócio. Para saber mais, veja o artigo [Escolher entre conta padrão, conta franquia ou Seller Portal](https://help.vtex.com/pt/tutorial/escolher-entre-conta-padrao-conta-franquia-ou-seller-portal--4S90HzzhMyZESsHqrnUs78).
 
diff --git a/docs/tutorials/pt/master-data-v2.md b/docs/tutorials/pt/master-data-v2.md
index f6c07e731..20c8a449b 100644
--- a/docs/tutorials/pt/master-data-v2.md
+++ b/docs/tutorials/pt/master-data-v2.md
@@ -15,8 +15,7 @@ legacySlug: master-data-v2
 subcategory: 5gtjaqCG7eIseyCI0aSqc2
 ---
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> Esta versão não é compatível com entidades de dados da versão antiga. É possível usar esta configuração somente para novas entidades de dados.</div>
+>⚠️ **Atenção:** Esta versão não é compatível com entidades de dados da versão antiga. É possível usar esta configuração somente para novas entidades de dados.
 
 Este artigo explica como salvar, validar e obter documentos no Master Data da VTEX. Nesta versão, usamos **JSON Schema** para validar documentos.
 
diff --git a/docs/tutorials/pt/master-data.md b/docs/tutorials/pt/master-data.md
index d61e49745..356aeeb58 100644
--- a/docs/tutorials/pt/master-data.md
+++ b/docs/tutorials/pt/master-data.md
@@ -209,9 +209,7 @@ Confira a tabela abaixo para saber mais sobre as funcionalidades de cada versão
    </table>
 </div>
 
-<div class="alert alert-danger">
-Note que as entidades de dados das duas versões são independentes, mesmo que algumas possam ser análogas. Isso significa que um dado criado em uma entidade da v1 não pode ser consultado nem editado usando recursos da v2 e vice versa.
-</div>
+>❗ Note que as entidades de dados das duas versões são independentes, mesmo que algumas possam ser análogas. Isso significa que um dado criado em uma entidade da v1 não pode ser consultado nem editado usando recursos da v2 e vice versa.
 
 ## Componentes básicos
 
diff --git a/docs/tutorials/pt/match-offers-mercado-livre.md b/docs/tutorials/pt/match-offers-mercado-livre.md
index 2221052d5..f9e79de82 100644
--- a/docs/tutorials/pt/match-offers-mercado-livre.md
+++ b/docs/tutorials/pt/match-offers-mercado-livre.md
@@ -15,9 +15,7 @@ legacySlug: match-de-anuncios-mercado-livre
 subcategory: 
 ---
 
-<div class="alert alert-info">
-  Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">Suporte</a>.
-  </div>  
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com nosso [Suporte](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue).  
 
 Antes de iniciar a leitura do artigo, é importante a leitura da tabela abaixo para compreendimento de alguns termos de uso específico da funcionalidade **Match de anúncios Mercado Livre.**
 
diff --git a/docs/tutorials/pt/maximum-price-per-item.md b/docs/tutorials/pt/maximum-price-per-item.md
index 6f9837685..7f19e3891 100644
--- a/docs/tutorials/pt/maximum-price-per-item.md
+++ b/docs/tutorials/pt/maximum-price-per-item.md
@@ -21,9 +21,7 @@ A promoção __Preço máximo por item__ é utilizada para definir um preço má
 
 Por se tratar de uma promoção, os preços cadastrados como máximo não poderão ser maiores do que o preço do produto.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> Para que a promoção Preço máximo por item funcione é <strong>obrigatório escolher um meio de pagamento</strong>.
-</div>
+>⚠️ **Atenção:** Para que a promoção Preço máximo por item funcione é **obrigatório escolher um meio de pagamento**.
 
 ## Dados gerais da promoção
 
@@ -42,9 +40,7 @@ Por se tratar de uma promoção, os preços cadastrados como máximo não poder
 - __Preço:__ Neste campo deve ser definido o preço máximo pelo qual será vendido o produto. Só é possível definir o preço máximo de um item por vez. Para adicionar produtos à promoção, clique no botão __+__.
 - __Meio de  pagamento__: Selecione os meios de pagamento desejados para ativar a promoção.
 
-<div class="alert alert-info">
-É possível fazer a importação de uma lista de SKUs, que deve estar salva em um arquivo .xls, com cada ID em uma linha diferente, seguido pelo preço máximo correspondente. Para ver um modelo, clique no link <strong>download de planilha exemplo</strong>.
-</div>
+>ℹ️ É possível fazer a importação de uma lista de SKUs, que deve estar salva em um arquivo .xls, com cada ID em uma linha diferente, seguido pelo preço máximo correspondente. Para ver um modelo, clique no link **download de planilha exemplo**.
 
 ## Condições para a promoção ser válida
 
diff --git a/docs/tutorials/pt/media-overview.md b/docs/tutorials/pt/media-overview.md
index 45ea3f4f8..bdb49d43d 100644
--- a/docs/tutorials/pt/media-overview.md
+++ b/docs/tutorials/pt/media-overview.md
@@ -17,9 +17,7 @@ subcategory: 27t6x0lngvjI3bnUg5AgEO
 
 O Mídia é uma funcionalidade responsável por gerenciar os arquivos de mídia da sua loja, como imagens e vídeos. Para imagens, você pode fazer o upload e organizar arquivos de mídia de até 5 MB usando o Mídia nos seguintes formatos: `png`, `jpg`, `gif`, `svg` e `webp`. Para vídeos, você pode adicionar uma URL para o provedor de vídeo hospedado externamente, como YouTube ou Vimeo.
 
-<div class="alert alert-warning">
-  Para upload, os arquivos devem ter uma extensão em minúsculo, por exemplo, <code>store.png</code>, e tamanho de até <b>5 MB</b>.
-</div>
+>⚠️ Para upload, os arquivos devem ter uma extensão em minúsculo, por exemplo, `store.png`, e tamanho de até **5 MB**.
 
 ![Mídia Visão Geral](https://images.ctfassets.net/alneenqid6w5/3HL6n5pBx5OpIyJMmPccuZ/1daf233a39aa1f3e4bd5b42b1f4b8805/pt-m__dia-overview.png)
 
@@ -39,9 +37,7 @@ Há três maneiras de acessar o Mídia no Admin:
 
 - **Headless CMS**:  no VTEX Admin, acesse **Storefront > Headless CMS** e escolha uma das páginas criadas, por exemplo, uma Página de Produto. Nas seções disponíveis, selecione uma na qual você possa adicionar uma imagem, por exemplo, [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero). Clique no componente de imagem do Hero e um painel do Mídia será aberto.
 
-<div class="alert alert-warning">
-A seção disponível deve utilizar o <a href="https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms">media-gallery</a> para aproveitar o Mídia. Para projetos <a href="https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore">FastStore</a>, as seções que utilizam o widget  <i>media-gallery</i> são <a href="https://developers.vtex.com/docs/guides/faststore/organisms-navbar">Navbar</a> and <a href="https://developers.vtex.com/docs/guides/faststore/organisms-hero">Hero</a>.
-</div>
+>⚠️ A seção disponível deve utilizar o [media-gallery](https://developers.vtex.com/docs/guides/faststore/headless-cms-3-adding-content-types-and-sections#step-3-adding-sections-to-the-headless-cms) para aproveitar o Mídia. Para projetos [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), as seções que utilizam o widget  <i>media-gallery</i> são [Navbar](https://developers.vtex.com/docs/guides/faststore/organisms-navbar) and [Hero](https://developers.vtex.com/docs/guides/faststore/organisms-hero).
 
 Na imagem a seguir, confira a visão geral da interface do Mídia e as ações disponíveis para gerenciar seus arquivos de mídia:
 
@@ -64,15 +60,11 @@ No Mídia, você pode fazer upload de imagens nos seguintes formatos: `png`, `jp
 
 1. Na página ou no painel **Mídia**, clique em `Adicionar novo(a)` e clique em `Imagem`.
 
-<div class="alert alert-warning">
-  <p>No painel Mídia disponível no Headless CMS e no Site Editor, você pode arrastar e soltar imagens.</p>
-</div>
+>⚠️ No painel Mídia disponível no Headless CMS e no Site Editor, você pode arrastar e soltar imagens.
 
 2. Escolha a imagem que deseja adicionar e clique em `Abrir`.
 
-<div class="alert alert-warning">
- Lembre-se, o Mídia aceita os seguintes formatos: <code>png</code>, <code>jpg</code>, <code>gif</code>, <code>svg</code>, e <code>webp</code>, em minúsculo e com um limite de tamanho de arquivo de 5 MB.
-</div>
+>⚠️ Lembre-se, o Mídia aceita os seguintes formatos: `png`, `jpg`, `gif`, `svg`, e `webp`, em minúsculo e com um limite de tamanho de arquivo de 5 MB.
 
 3. Depois que a imagem é carregada, uma mensagem de sucesso será exibida. Agora, você pode executar outras ações clicando em `Mais ações` (três pontos verticais) na miniatura da imagem e escolhendo uma das seguintes ações:
 
@@ -83,9 +75,7 @@ No Mídia, você pode fazer upload de imagens nos seguintes formatos: `png`, `jp
 | **Baixar** | Faz o download da imagem para o seu computador. |
 | **Excluir** |	Remove a imagem do repositório. |
 
-<div class="alert alert-warning">
-Excluir a imagem apenas a removerá do repositório do Mídia. Se você adicionou a imagem em um componente Hero, por exemplo, a imagem continuará sendo utilizada neste componente. Porém, você não poderá usá-la em outros componentes.
-</div>
+>⚠️ Excluir a imagem apenas a removerá do repositório do Mídia. Se você adicionou a imagem em um componente Hero, por exemplo, a imagem continuará sendo utilizada neste componente. Porém, você não poderá usá-la em outros componentes.
 
 ### Adicionar vídeos
 
diff --git a/docs/tutorials/pt/mercado-libre-size-chart.md b/docs/tutorials/pt/mercado-libre-size-chart.md
index d0ceb2334..c748d38c2 100644
--- a/docs/tutorials/pt/mercado-libre-size-chart.md
+++ b/docs/tutorials/pt/mercado-libre-size-chart.md
@@ -113,9 +113,7 @@ O template da tabela de medidas para roupas da parte inferior possui as seguinte
 | **Person_height_from** | Altura da pessoa - início do intervalo de medidas. | Preencha cada linha com a medida mínima da altura de uma pessoa em centímetros. Por exemplo, 188 cm. |
 | **Person_height_to** | Altura da pessoa - fim do intervalo de medidas. | Preencha cada linha com a medida mínima da altura de uma pessoa em centímetros. Por exemplo, 193 cm. |
 
-<div class="alert alert-info">
-  É necessário utilizar espaço entre o número e a medida (cm), separar os números utilizando pontos (.), preencher todas as colunas com o tamanho do corpo, e conferir se os campos <b>Gênero</b> e <b>Tamanho</b> foram selecionados corretamente.
-  </div>
+>ℹ️ É necessário utilizar espaço entre o número e a medida (cm), separar os números utilizando pontos (.), preencher todas as colunas com o tamanho do corpo, e conferir se os campos **Gênero** e **Tamanho** foram selecionados corretamente.
 
 ## Fazer upload da Tabela de medidas
 
@@ -132,6 +130,4 @@ Após preencher a planilha de mapeamento, faça o seu upload:
 
 Ao finalizar, sua tabela de medida personalizada terá sido criada com sucesso.  
 
-<div class="alert alert-info">
-  Caso ocorra algum erro, o problema será indicado na tela de upload. O erro deve ser resolvido e o upload deverá ser realizado novamente.
-  </div>
+>ℹ️ Caso ocorra algum erro, o problema será indicado na tela de upload. O erro deve ser resolvido e o upload deverá ser realizado novamente.
diff --git a/docs/tutorials/pt/mercado-livre-faq.md b/docs/tutorials/pt/mercado-livre-faq.md
index d695c2f58..cc76f9661 100644
--- a/docs/tutorials/pt/mercado-livre-faq.md
+++ b/docs/tutorials/pt/mercado-livre-faq.md
@@ -147,7 +147,7 @@ Pela regra do Mercado Livre, não é possível reenviar informações dos produt
 
 Caso o produto não tenha sido vendido ainda, será possível fazer alterações. Se a alteração for no valor da variação/atributo, essa mudança deve ser realizada na [página de mapeamento](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA). Se a alteração for no valor da especificação do produto, leia nosso artigo [Cadastrar especificações de produto](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/4fcdmJzQ6QYA9zWf3bLWin).
 
-<div class="alert alert-warning">Após excluir um produto, não é possível recuperar a relevância do seu anúncio.</div>
+>⚠️ Após excluir um produto, não é possível recuperar a relevância do seu anúncio.
 
 ### Por que meu produto foi categorizado de forma errada no Mercado Livre?
 
diff --git a/docs/tutorials/pt/merchandising-rule-conditions.md b/docs/tutorials/pt/merchandising-rule-conditions.md
index 1d677cc14..1a0dfde4a 100644
--- a/docs/tutorials/pt/merchandising-rule-conditions.md
+++ b/docs/tutorials/pt/merchandising-rule-conditions.md
@@ -23,9 +23,7 @@ Entenda os critérios e operadores possíveis para cada forma de edição nas ta
 
 <table class="w-100 center mv7 bb b--gray" style="border-spacing: 0px; border-collapse: collapse;"> <thead> <tr class="bb b--muted-3"> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Nome</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Descrição</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Operadores</th> <th class="t-body fw5 c-muted-1 bb bw1 pa2 pb3 b--muted-3 tl">Tipo de edição</th> </tr> </thead> <tbody> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Termo</span></td> <td rowspan="2" class="t-body pa5">Palavra pesquisada pelo cliente que será relacionada à regra. Campo para preenchimento livre.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td rowspan="2" class="t-body pa5" ><strong>Editor manual:</strong><br>Regras de ativação<br>Regras de customização</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">contém</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">ID</span></td> <td class="t-body pa5">Pesquisa pelo exato ID de algum elemento do catálogo que será relacionado à regra. Os possíveis IDs são: <strong>ProductID</strong>, <strong>ProductRefID</strong>, <strong>SKUID</strong>, <strong>SKURefID</strong> e <strong>EAN</strong>. Campo para preenchimento livre.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de customização</td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">categoria</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma categoria cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">departamento</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa um departamento cadastrado no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">marca</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma marca cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">product cluster names</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma coleção cadastrada no Catálogo da loja. A ordem dos produtos é determinada pela relevância do Intelligent Search.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">promocao</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que valida se existe ao menos uma promoção vinculada ao item (<span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">yes</span>).</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">sellername</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa o nome de um seller.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">subcategoria</span></td> <td rowspan="2" class="t-body pa5" >Valor selecionável que representa uma subcategoria cadastrada no catálogo da loja.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> <tr class="bb b--muted-3"> <td rowspan="2" class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">{{especificação}}</span></td> <td rowspan="2" class="t-body pa5" >Qualquer especificação ativa no Catálogo aparece como critério customizado, com os mesmos valores possíveis. O nome do critério é exatamente o nome da especificação cadastrada. Por exemplo, se houver uma especificação ativa chamada <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Cor</span>, o critério exibido será <span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">Cor</span>.</td> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">é</span></td> <td class="t-body pa5">Todos os cenários de edição</td> </tr> <tr class="bb b--muted-3"> <td class="t-body pa5"><span class="t-body c-on-base pa2 mw6 br2 bg-muted-4">somente</span></td> <td class="t-body pa5"><strong>Editor manual:</strong><br>Regras de ativação<br><strong>Editor visual</strong></td> </tr> </tbody> </table>
 
-<div class="alert alert-warning">
-  <p>Os critérios <code>departamento</code>, <code>categoria</code> e <code>subcategoria</code> só aparecem como opções para compor as Regras de merchandising se os três níveis de categoria estiverem previamente configurados no <strong>Catálogo</strong>.</p>
-</div>
+>⚠️ Os critérios `departamento`, `categoria` e `subcategoria` só aparecem como opções para compor as Regras de merchandising se os três níveis de categoria estiverem previamente configurados no **Catálogo**.
 
 ## Operadores
 
diff --git a/docs/tutorials/pt/meta-tags-suiteshare.md b/docs/tutorials/pt/meta-tags-suiteshare.md
index 487a39ef5..da470fbf2 100644
--- a/docs/tutorials/pt/meta-tags-suiteshare.md
+++ b/docs/tutorials/pt/meta-tags-suiteshare.md
@@ -27,9 +27,7 @@ Meta tag no Facebook:
 
 As Meta Tags servem como uma prévia do que o usuário irá encontrar quando clicar no seu link.
 
-<div class="alert alert-warning">
-  <p><b>Importante</b>: Antes de começar, você já deverá ter criado um link para cada número de WhatsApp. Se ainda não fez isso, é só acessar esse <a href="http://help.suiteshare.com/support/solutions/articles/67000192026-links">link</a>.</p>
-</div>
+>⚠️ **Importante**: Antes de começar, você já deverá ter criado um link para cada número de WhatsApp. Se ainda não fez isso, é só acessar esse [link](http://help.suiteshare.com/support/solutions/articles/67000192026-links).
 
 No painel da VTEX Assisted Sales (SuiteShare), acesse a opção _**Atrair > Links**_.
 
diff --git a/docs/tutorials/pt/migrating-ads-in-mercado-livre.md b/docs/tutorials/pt/migrating-ads-in-mercado-livre.md
index 08a83d890..0b25da140 100644
--- a/docs/tutorials/pt/migrating-ads-in-mercado-livre.md
+++ b/docs/tutorials/pt/migrating-ads-in-mercado-livre.md
@@ -33,9 +33,7 @@ O primeiro passo para migrar seus anúncios do Mercado Livre é configurar a int
 
 Durante a etapa [Cadastro do conector Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), você deverá preencher o campo `ID da Política comercial` com o número 0. Dessa forma, os anúncios que serão migrados da planilha não serão duplicados pela plataforma do Mercado Livre.
 
-<div class="alert alert-danger">
-Caso utilize o ID de uma política comercial existente, a integração criará novos anúncios no Mercado Livre e seu catálogo será duplicado. A única forma de resolver esse problema será desativando manualmente os anúncios criados em duplicidade no painel do Mercado Livre.
-</div>
+>❗ Caso utilize o ID de uma política comercial existente, a integração criará novos anúncios no Mercado Livre e seu catálogo será duplicado. A única forma de resolver esse problema será desativando manualmente os anúncios criados em duplicidade no painel do Mercado Livre.
 
 ## 2. Fazer download da planilha de migração
 
@@ -45,9 +43,7 @@ Primeiro, faça download da [Planilha de migração](https://assets.ctfassets.ne
 
 O produto cadastrado na VTEX só poderá ser mapeado com um anúncio no Mercado Livre. No caso de [anúncios dos tipos Clássico e Premium](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/2MR2USqcvDGaoAkGNdCfGi), por serem configurações separadas, o mesmo produto pode estar anunciado em ambos tipos de anúncios.
 
-<div class="alert alert-warning">
-A integração entre a VTEX e o Mercado Livre permite associar um SKU cadastrado na VTEX a um único anúncio no Mercado Livre por vez. Por isso, é necessário separar os tipos de anúncios do tipo Clássico e os do tipo Premium quando for preencher a planilha de migração. 
-</div>
+>⚠️ A integração entre a VTEX e o Mercado Livre permite associar um SKU cadastrado na VTEX a um único anúncio no Mercado Livre por vez. Por isso, é necessário separar os tipos de anúncios do tipo Clássico e os do tipo Premium quando for preencher a planilha de migração.
 
 ## 3. Preencher a planilha de migração dos anúncios
 
diff --git a/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md b/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md
index 58f169e8f..2ae51ae31 100644
--- a/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md
+++ b/docs/tutorials/pt/migrating-to-the-new-version-of-smart-checkout.md
@@ -55,9 +55,7 @@ Você pode usar os arquivos `checkout5-custom.js` e `orderplaced2-custom.js` p
 4. No menu __Arquivos__, localizado no lado direito da página, clique naqueles em que desejar realizar ajustes no código.
 5. Clique no botão `Salvar`.
 
-<div class="alert alert-warning">
-  Customizar arquivos de Javascript pode danificar seu Checkout. A VTEX <b>não recomenda</b> customizações e não se responsabiliza por qualquer dano causado por esse código.
-</div>
+>⚠️ Customizar arquivos de Javascript pode danificar seu Checkout. A VTEX **não recomenda** customizações e não se responsabiliza por qualquer dano causado por esse código.
 
 __IMPORTANTE:__ não use esses arquivos para inserir tags de marketing e integrações. Se precisar delas, faça isso pelo Google Tag Manager.
 
diff --git a/docs/tutorials/pt/mode-off-faq.md b/docs/tutorials/pt/mode-off-faq.md
index 38295973d..91408bf62 100644
--- a/docs/tutorials/pt/mode-off-faq.md
+++ b/docs/tutorials/pt/mode-off-faq.md
@@ -45,9 +45,7 @@ Desse modo, para esses meios de pagamento, as transações não serão reprocess
 
 O mode-off é ligado quando o parceiro ou a integração apresentam instabilidade identificada a partir do retorno de mensagens de erro do tipo: 500, 408 ou timeout maior que 30 segundos nos últimos cinco minutos. Essa regra é válida para todos os meios de pagamento que ele processa.
 
-<div class="alert alert-warning">
-Vale lembrar que os meios de pagamento síncronos <strong>não</strong> poderão ser reprocessados. Porém, entram na contagem de erros para identificarmos se um parceiro está instável ou não.  
-</div>
+>⚠️ Vale lembrar que os meios de pagamento síncronos **não** poderão ser reprocessados. Porém, entram na contagem de erros para identificarmos se um parceiro está instável ou não.
 
 ## Qual a regra para o mode-off ser desligado?
 
@@ -57,8 +55,7 @@ As transações serão liberadas normalmente quando o parceiro parar de apresent
 
 O tempo entre retentativas de processamento da transação (_retries_) pode ser definido pelo parceiro no momento do envio das informações de pagamento. Ao configurar o tempo para cancelamento do pagamento (campo `delayToCancel`) para um período menor que 1 dia, as retentativas serão realizadas a cada 1 hora. Se o tempo para cancelar o pagamento for definido como igual ou maior que 1 dia, as retentativas serão realizadas a cada 4 horas. Para mais informações, acesse [Create Payment endpoint](https://developers.vtex.com/docs/api-reference/payment-provider-protocol?endpoint=post-/payments).
 
-<div class="alert alert-info">
- Caso o pagamento seja realizado por <a href="https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf">PIX</a> ou o tempo para cancelamento do pagamento seja configurado entre 5 minutos e 1 hora, as chamadas de retry ocorrerão a cada 5 minutos.</div>
+>ℹ️ Caso o pagamento seja realizado por [PIX](https://help.vtex.com/pt/tutorial/configurar-pix-como-meio-de-pagamento--5sbNavMSJY4jyLmLKRHiOf) ou o tempo para cancelamento do pagamento seja configurado entre 5 minutos e 1 hora, as chamadas de retry ocorrerão a cada 5 minutos.
 
 ## Como identificar o mode-off e o que fazer quando ele estiver ligado?
 
diff --git a/docs/tutorials/pt/moving-order-to-start-handling-shipping.md b/docs/tutorials/pt/moving-order-to-start-handling-shipping.md
index 4fcf1d6b7..d4eccaea3 100644
--- a/docs/tutorials/pt/moving-order-to-start-handling-shipping.md
+++ b/docs/tutorials/pt/moving-order-to-start-handling-shipping.md
@@ -40,6 +40,4 @@ Se a loja não tiver ERP ou algum sistema que integre os pedidos, é possível f
     - <a class="far fa-check-square"></a> Eu entendo as consequências desta ação no fluxo do pedido.
 5. Clique em `Avançar com status`.
 
-<div class="alert alert-warning">
-Ao iniciar o manuseio do pedido manualmente, o pedido não poderá ser integrado ao ERP posteriormente.
-</div>
+>⚠️ Ao iniciar o manuseio do pedido manualmente, o pedido não poderá ser integrado ao ERP posteriormente.
diff --git a/docs/tutorials/pt/multilevel-omnichannel-inventory.md b/docs/tutorials/pt/multilevel-omnichannel-inventory.md
index a1ed8a7c4..a7569e5cf 100644
--- a/docs/tutorials/pt/multilevel-omnichannel-inventory.md
+++ b/docs/tutorials/pt/multilevel-omnichannel-inventory.md
@@ -22,9 +22,7 @@ __Multilevel Omnichannel Inventory__ é a configuração na VTEX que permite uma
 * [Restrições](#restricoes)
 * [Como configurar](#como-configurar)
 
-<div class="alert alert-info">
-Para saber mais sobre a arquitetura dos pedidos do tipo Multilevel Omnichannel Inventory, e como fazer a configuração via API REST, confira nosso <a href="https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory">artigo do Developer Portal</a>.
-  </div>
+>ℹ️ Para saber mais sobre a arquitetura dos pedidos do tipo Multilevel Omnichannel Inventory, e como fazer a configuração via API REST, confira nosso [artigo do Developer Portal](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory).
 
 ## Arquitetura de contas
 
@@ -46,9 +44,7 @@ Desta maneira, é possível que um marketplace venda os produtos dos seus seller
 
 Isso significa que, quando o seller com a conta principal configurar uma integração com um marketplace, as contas franquia estarão automaticamente integradas a ele também, não sendo preciso gerenciar cada franquia individualmente para configurar sua integração ao marketplace.
 
-<div class="alert alert-info">
-Atualmente, só é permitido um nível de recursividade. Ou seja, o marketplace pode vender produtos dos sellers white label integrados a um seller direto.
-</div>
+>ℹ️ Atualmente, só é permitido um nível de recursividade. Ou seja, o marketplace pode vender produtos dos sellers white label integrados a um seller direto.
 
 ## Benefícios
 
@@ -67,9 +63,7 @@ Para saber mais detalhes sobre a arquitetura de pedidos aplicada em Multilevel O
 
 Algumas das funcionalidades que fazem parte do modelo tradicional de marketplace não estão disponíveis para um cenário _Multilevel Omnichannel Inventory_. É importante conhecer essas restrições antes de habilitar a configuração.
 
-<div class="alert alert-warning">
-Note que, no Brasil, o Banco Central (BACEN) regulamenta a atuação de marketplaces varejistas como concentradores e repassadores de dinheiro. Dado essa restrição, recomendamos a implementação do Multilevel Omnichannel Marketplace em lojas que se adequam à circular 3.815 do BACEN. Saiba mais em <a href="https://vtex.com/pt-br/blog/estrategia/bacen-e-a-regulamentacao-para-marketplaces-no-brasil/"> BACEN e a regulamentação para marketplaces no Brasil - VTEX</a>.
- </div>
+>⚠️ Note que, no Brasil, o Banco Central (BACEN) regulamenta a atuação de marketplaces varejistas como concentradores e repassadores de dinheiro. Dado essa restrição, recomendamos a implementação do Multilevel Omnichannel Marketplace em lojas que se adequam à circular 3.815 do BACEN. Saiba mais em [ BACEN e a regulamentação para marketplaces no Brasil - VTEX](https://vtex.com/pt-br/blog/estrategia/bacen-e-a-regulamentacao-para-marketplaces-no-brasil/).
 
 ### Disponibilidade
 
@@ -91,9 +85,7 @@ A solução pode ser suficiente em casos em que o seller direto faz parte do mes
 
 Uma vez que a configuração é feita, somente os meios de pagamento do marketplace aparecerão como opção no checkout. Os meios de pagamento dos sellers diretos (nível 2) e sellers white label (nível 3) não são importados na arquitetura de contas. Portanto, o checkout só mostra os meios de pagamento do marketplace, mesmo que o afiliado do seller direto esteja configurado para usar os meios de pagamento dele.
 
-<div class="alert alert-warning">
-  O <a href="https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187">afiliado</a> da conta franquia sempre deve estar com a configuração de usar os meios de pagamento desativada.
-</div>
+>⚠️ O [afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187) da conta franquia sempre deve estar com a configuração de usar os meios de pagamento desativada.
 
 ### Alteração de seller
 
@@ -139,9 +131,7 @@ Não é possível criar tabelas de preço por meio da funcionalidade [Price Tabl
 
 A configuração da funcionalidade **Multilevel Omnichannel Inventory** deve ser feita pelo marketplace em seu Admin VTEX ou via [API Rest](https://developers.vtex.com/vtex-rest-api/docs/multilevel-omnichannel-inventory). Essa configuração pode ser feita tanto em sellers já integrados, quanto em sellers adicionados pela primeira vez. 
 
-<div class="alert alert-info">
-Note que a configuração deve ser feita para cada seller direto (nível 2) em que se deseja aplicar a funcionalidade, mas não em cada seller white label ou conta franquia (nível 3).
-</div>
+>ℹ️ Note que a configuração deve ser feita para cada seller direto (nível 2) em que se deseja aplicar a funcionalidade, mas não em cada seller white label ou conta franquia (nível 3).
 
 ### Sellers já integrados
 
diff --git a/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md b/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md
index 4a24a7b30..d48020c93 100644
--- a/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md
+++ b/docs/tutorials/pt/my-orders-in-mercado-libre-have-errors.md
@@ -52,12 +52,14 @@ Para verificar as categorias e atributos enviados, acesse **Marketplace > Conex
 4. Clique na categoria que apresenta o erro.  
 5. Realize novamente o mapeamento conforme as categorias e atributos existentes no Mercado Livre.  
 
-<div class="alert alert-info">
-Para identificar o atributo indicado na mensagem de erro, consulte o número inicial dos códigos determinados pelo Mercado Livre.<p> Clique no nome do seu país para fazer o download da planilha de referência:</p>
-<p><ul>
-<p><a href="https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip">Brasil</a></p>
-<p><a href="https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar">Argentina</a></p> 
-<p><a href="https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar">Colômbia</a></p> 
-<p><a href="https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar">México</a></p>
-</ul></p>
-</div>
+>ℹ️ Para identificar o atributo indicado na mensagem de erro, consulte o número inicial dos códigos determinados pelo Mercado Livre.Clique no nome do seu país para fazer o download da planilha de referência:
+>
+> 
+> <p>[Brasil](https://assets.contentful.com/alneenqid6w5/22NlNdUIBK8qWic8cYw2sg/11c88bb0b439c7c7f8ce5909923af3d6/Brasil.zip)
+>
+> [Argentina](https://assets.contentful.com/alneenqid6w5/3c61gJrH7GWOywMCGMECg4/dc7a2ce73a99d41345dde2092eb1fec6/Argentina.rar) 
+>
+> [Colômbia](https://assets.contentful.com/alneenqid6w5/5RePTJoKrYi4qA66WCCYKw/33910300057806b554d566210aa2310a/Colombia.rar) 
+>
+> [México](https://assets.contentful.com/alneenqid6w5/3Z3xgpPyvuYEAIO2me4GSG/e4f4198463d8a3ba05124a30031302fa/Mexico.rar)
+> </p>
diff --git a/docs/tutorials/pt/my-store-order-was-not-created.md b/docs/tutorials/pt/my-store-order-was-not-created.md
index a5c44ef76..53ad4ceb1 100644
--- a/docs/tutorials/pt/my-store-order-was-not-created.md
+++ b/docs/tutorials/pt/my-store-order-was-not-created.md
@@ -58,7 +58,5 @@ Quando o produto não tem estoque e a integração não está configurada para e
 3. Na aba `Editar XML`, na opção **Exibir SKUs indisponíveis**, marque a caixa de seleção `Exibir SKUs fora de estoque (esgotados) entre os resultados`.
 4. Clique em `Salvar`. 
 
-<div class="alert alert-warning">
-Podem ocorrer erros ao tentar faturar um pedido com informações XML incorretas ou faltantes.
-</div>
+>⚠️ Podem ocorrer erros ao tentar faturar um pedido com informações XML incorretas ou faltantes.
 
diff --git a/docs/tutorials/pt/navigation.md b/docs/tutorials/pt/navigation.md
index b4970649b..a44c863fa 100644
--- a/docs/tutorials/pt/navigation.md
+++ b/docs/tutorials/pt/navigation.md
@@ -18,9 +18,8 @@ subcategory: oMrzcOMVbBpH0reeMFHFg
 O conjunto de dados de navegação opera com duas tabelas principais: `pageviews` e `sessions`. Uma `pageview` refere-se a cada nova página acessada pelo usuário durante a navegação na loja, enquanto uma `session` é definida como o conjunto de todos os `pageviews` realizados por um usuário em uma única visita.  
 Cada `session` permanece ativa até que não ocorra uma nova `pageview` por um período de 30 minutos.  
 
-<div class="alert alert-warning">
-O conjunto de dados de navegação não captura todos os tipos de eventos que ocorrem durante a navegação.</br>
-Ex: cliques específicos, eventos especiais e interações com o mini carrinho.</br></div>
+>⚠️ O conjunto de dados de navegação não captura todos os tipos de eventos que ocorrem durante a navegação.</br>
+> Ex: cliques específicos, eventos especiais e interações com o mini carrinho.</br>
 
 - [Características dos dados de navegação](#caracteristicas-dos-dados-de-navegacao)
 - [Tabela sessions](#tabela_sessions)
@@ -37,10 +36,8 @@ Ex: cliques específicos, eventos especiais e interações com o mini carrinho.<
 | Histórico | Os dados são mantidos por dois anos, a partir de 2022 para clientes que já utilizam a plataforma VTEX. |
 | Menor intervalo de atualização possível | Uma hora. |  
 
-<div class="alert alert-warning">
-  O <i>script</i> em um site não é capaz de capturar dados de sessões que se originam em marketplaces, aplicativos ou implementações <i>headless</i>, nas quais não gerenciamos o <i>frontend</i>. Além disso, personalizações realizadas no <i>frontend</i> da loja podem interferir ou mesmo inativar o <i>script</i> levando à falta de registro de algumas sessões, ou taxa de conversão observada no dashboard.</br>
-Para minimizar o impacto no desempenho da loja, o <i>script</i> é configurado para ser o último elemento a carregar na página, o que significa que sessões muito breves podem não ser capturadas.</br>
-</div>
+>⚠️ O <i>script</i> em um site não é capaz de capturar dados de sessões que se originam em marketplaces, aplicativos ou implementações <i>headless</i>, nas quais não gerenciamos o <i>frontend</i>. Além disso, personalizações realizadas no <i>frontend</i> da loja podem interferir ou mesmo inativar o <i>script</i> levando à falta de registro de algumas sessões, ou taxa de conversão observada no dashboard.</br>
+> Para minimizar o impacto no desempenho da loja, o <i>script</i> é configurado para ser o último elemento a carregar na página, o que significa que sessões muito breves podem não ser capturadas.</br>
 
 ## Tabela sessions
 
diff --git a/docs/tutorials/pt/new-google-shopping-api-integration.md b/docs/tutorials/pt/new-google-shopping-api-integration.md
index eb383007f..b3d2edb54 100644
--- a/docs/tutorials/pt/new-google-shopping-api-integration.md
+++ b/docs/tutorials/pt/new-google-shopping-api-integration.md
@@ -81,7 +81,5 @@ O Google faz com que os produtos enviados expirem automaticamente após 30 dias
 #### Tamanho do título
 O limite é de 150  caracteres, mas os anúncios do Google só exibem 70 caracteres de qualquer maneira ([entenda mais aqui](https://support.google.com/merchants/answer/6098378?hl=pt)). A integração envia até 150 caracteres que é composto por Título do Produto + Título do SKU.
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> A integração por XML não foi descontinuada, porém se a integração for feita por XML e pelo módulo de Integrações (API) os produtos aparecerão duplicados. 
-</div>
+>⚠️ **Atenção:** A integração por XML não foi descontinuada, porém se a integração for feita por XML e pelo módulo de Integrações (API) os produtos aparecerão duplicados.
 
diff --git a/docs/tutorials/pt/new-my-orders-area.md b/docs/tutorials/pt/new-my-orders-area.md
index e0b07c019..5f699d2f1 100644
--- a/docs/tutorials/pt/new-my-orders-area.md
+++ b/docs/tutorials/pt/new-my-orders-area.md
@@ -15,12 +15,14 @@ legacySlug: nova-secao-de-meus-pedidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-warning">
-Esta atualização é uma <em>major</em> e <strong>não é compatível com as customizações da página atual de Meus Pedidos</strong>. 
-<br />
-<br />
-Como a nova estrutura de páginas é completamente diferente, será necessário refazer as customizações para migrar para esta versão. Veja detalhes sobre como atualizar sua customização em <a href="http://help.vtex.com/pt/tutorial/customizando-a-secao-meus-pedidos">Customizando a Seção Meus Pedidos</a>.
-</div>
+>⚠️ Esta atualização é uma *major* e **não é compatível com as customizações da página atual de Meus Pedidos**. 
+>
+>
+> 
+>
+>
+> 
+> Como a nova estrutura de páginas é completamente diferente, será necessário refazer as customizações para migrar para esta versão. Veja detalhes sobre como atualizar sua customização em [Customizando a Seção Meus Pedidos](http://help.vtex.com/pt/tutorial/customizando-a-secao-meus-pedidos).
 
 A VTEX busca usar uma stack moderna para criar produtos que atendam cada vez melhor ao mercado de e-commerce. Por essa razão, começamos a usar a library React JS em nossas features mais recentes: a nova página de **Meus Pedidos** é um exemplo. Ela vem com novas features e novo design, e foi criada do zero usando React. 
 
diff --git a/docs/tutorials/pt/new-route.md b/docs/tutorials/pt/new-route.md
index 7f46b1b73..79125d79f 100644
--- a/docs/tutorials/pt/new-route.md
+++ b/docs/tutorials/pt/new-route.md
@@ -35,9 +35,7 @@ A lista de entregas apresenta as seguintes colunas ordenáveis:
 
 Você deve selecionar as entregas que deseja colocar na [Rota a ser criada](#rota_a_ser_criada). A seleção é feita clicando na caixa de seleção, à esquerda da de cada entrega na lista. 
 
-<div class="alert alert-info"> 
-Caso você queira colocar na rota uma entrega específica, utilize a pesquisa selecionando o filtro desejado, preenchendo o campo de texto e clicando no botão de lupa.
-</div>
+>ℹ️ Caso você queira colocar na rota uma entrega específica, utilize a pesquisa selecionando o filtro desejado, preenchendo o campo de texto e clicando no botão de lupa.
 
 Ao selecionar a entrega desejada para compor a rota, a entrega selecionada aparecerá automaticamente na lista da Rota a ser criada, que é atualizada automaticamente à medida que as entregas são selecionadas.
 
@@ -58,9 +56,7 @@ Quando todas as entregas estiverem na lista, antes de finalizar a criação da n
 
 Vale ressaltar que a posição das entregas na lista é a ordem de entrega da rota. 
 
-<div class="alert alert-warning">  
-  O recurso de <b>Ordenar Serviços</b> se limita a 21 entregas.
-</div>
+>⚠️ O recurso de **Ordenar Serviços** se limita a 21 entregas.
 
 ### Selecionar Portador
 
@@ -91,9 +87,7 @@ Remover entregas clicando  no __X__ à direta da entrega.
 - Alterar manualmente a ordem de entregas segurando e arrastando para a posição que deseja.
 - Trocar a data de entrega.
 
-<div class="alert alert-danger">
-Só é possível editar uma rota se ela ainda estiver no status Ativo. Não é indicado alterar uma rota se ela já foi iniciada - isso pode causar inconsistências na plataforma do VTEX Tracking e no aplicativo do portador.
-</div>
+>❗ Só é possível editar uma rota se ela ainda estiver no status Ativo. Não é indicado alterar uma rota se ela já foi iniciada - isso pode causar inconsistências na plataforma do VTEX Tracking e no aplicativo do portador.
 
 ![Cadastro de nova rota](https://images.ctfassets.net/alneenqid6w5/3m2JhopNd3vcscWEOYSnvn/f739888039df88f13fc7bcab16325253/Nova_Rota.gif)
 
diff --git a/docs/tutorials/pt/o-que-e-uma-disputa.md b/docs/tutorials/pt/o-que-e-uma-disputa.md
index 300cb1ff2..053b4dff2 100644
--- a/docs/tutorials/pt/o-que-e-uma-disputa.md
+++ b/docs/tutorials/pt/o-que-e-uma-disputa.md
@@ -27,9 +27,7 @@ Geralmente, isso acontece quando:
 
 Desse modo, existem duas possibilidades para o resultado de uma disputa: ou o lojista ganha a disputa e fica com o dinheiro da compra ou perde e ocorre o chargeback. 
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: o chargeback é um tipo de estorno típico do cenário de e-commerce. Aqui, compras feitas por meio de cartão de crédito são canceladas ou estornadas quando o titular do cartão ganha a disputa.
-</div>
+>ℹ️ **Atenção**: o chargeback é um tipo de estorno típico do cenário de e-commerce. Aqui, compras feitas por meio de cartão de crédito são canceladas ou estornadas quando o titular do cartão ganha a disputa.
 
 Nesse cenário, o VTEX Payment fica responsável por:
 
diff --git a/docs/tutorials/pt/offer-details.md b/docs/tutorials/pt/offer-details.md
index e8d3c41d0..97f302588 100644
--- a/docs/tutorials/pt/offer-details.md
+++ b/docs/tutorials/pt/offer-details.md
@@ -15,12 +15,10 @@ legacySlug: detalhes-do-anuncio
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class="alert alert-info">
-Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
-Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
-Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
-</div>  
+>ℹ️ Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo **Gerenciamento de anúncios**.
+> Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+> Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do [Developer portal na página de release notes](https://developers.vtex.com/updates/release-notes) e [VTEX Help Center na página de novidades](https://help.vtex.com/pt/en/announcements).  
 
 Anúncio é um SKU de um seller que teve seu  preço e estoque configurados e foi enviado para diferentes canais de venda. É no módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) que sellers supervisionam o envio e sincronização de seus anúncios para marketplaces.
 
diff --git a/docs/tutorials/pt/offer-management.md b/docs/tutorials/pt/offer-management.md
index ea4a8cdd6..eae246c6f 100644
--- a/docs/tutorials/pt/offer-management.md
+++ b/docs/tutorials/pt/offer-management.md
@@ -15,12 +15,10 @@ legacySlug: listagem-de-anuncios
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class="alert alert-info">
-Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
-Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
-Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
-</div>  
+>ℹ️ Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo **Gerenciamento de anúncios**.
+> Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+> Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do [Developer portal na página de release notes](https://developers.vtex.com/updates/release-notes) e [VTEX Help Center na página de novidades](https://help.vtex.com/pt/en/announcements).  
 
 O módulo **Gerenciamento de anúncios** permite aos sellers acompanhar o envio e a sincronização de anúncios de integrações com canais de venda. Na VTEX, anúncio é um SKU de um seller que teve seu preço e estoque configurados e foi enviado para um canal de venda.
 
diff --git a/docs/tutorials/pt/offer-quality-filters.md b/docs/tutorials/pt/offer-quality-filters.md
index bd5f73fd2..89271d3ef 100644
--- a/docs/tutorials/pt/offer-quality-filters.md
+++ b/docs/tutorials/pt/offer-quality-filters.md
@@ -58,9 +58,7 @@ Não é possível desativar as "Default requirements", e estão à mostra na pá
 * Ref ID possui quantidade de caracteres máximo de 50
 * EAN possui quantidade de caracteres máximo de 50
 
-<div class="alert alert-info">
-  É possível configurar a auto aprovação de anúncios pelo VTEX Matcher por meio de chamadas de API REST <a href="https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig">Save Account's Approval Settings</a>. São critérios diferentes dos disponíveis para visualização na página de Filtros de qualidade dos anúncios e se aplicam à aprovação automática de anúncios de determinados sellers.
-  </div>
+>ℹ️ É possível configurar a auto aprovação de anúncios pelo VTEX Matcher por meio de chamadas de API REST [Save Account's Approval Settings](https://developers.vtex.com/vtex-rest-api/reference/saveaccountconfig). São critérios diferentes dos disponíveis para visualização na página de Filtros de qualidade dos anúncios e se aplicam à aprovação automática de anúncios de determinados sellers.
 
 ## Criar grupos de requisitos 
 Crie grupo de requisitos para definir as regras aplicadas a sellers, categorias ou marketplaces. Os grupos de requisitos aplicam regras aos campos listados a seguir. Saiba mais sobre a definição de cada Tipo de requisito.
@@ -81,9 +79,7 @@ Crie grupo de requisitos para definir as regras aplicadas a sellers, categorias
 
 É possível criar requisitos obrigatórios e/ou opcionais. Saiba mais sobre as implicações de cada requisito em [Catalogar anúncios com requisitos](#catalogar-anuncios-com-requisitos). 
 
-<div class="alert alert-info">
-Note que cada grupo de requisito só comporta um valor. Portanto, para adicionar mais de um valor é necessário criar outro grupo de requisito. Por exemplo, se o marketplace quiser adicionar as palavras "Blusas" e "Camisas" como requisitos obrigatórios para o campo Marca do seller, é necessário criar um grupo de requisito para "Blusas" e outro para "Camisas".
-  </div>
+>ℹ️ Note que cada grupo de requisito só comporta um valor. Portanto, para adicionar mais de um valor é necessário criar outro grupo de requisito. Por exemplo, se o marketplace quiser adicionar as palavras "Blusas" e "Camisas" como requisitos obrigatórios para o campo Marca do seller, é necessário criar um grupo de requisito para "Blusas" e outro para "Camisas".
 
 Para criar um novo grupo de requisitos:
 
diff --git a/docs/tutorials/pt/offer-status.md b/docs/tutorials/pt/offer-status.md
index 69209301d..2e0544fce 100644
--- a/docs/tutorials/pt/offer-status.md
+++ b/docs/tutorials/pt/offer-status.md
@@ -108,9 +108,7 @@ Você será redirecionado à página correspondente para realizar as alteraçõe
 
 Para exportar a lista de anúncios publicados em formato XLSX, clique sobre o  ícone seta para baixo <i class="fas fa-download"></i>, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação dependerá do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX.
 
-<div class="alert alert-info">
-O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
-</div>
+>ℹ️ O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
 
 ## Aba Problemas
 
@@ -180,9 +178,7 @@ Você será redirecionado à página correspondente para realizar as alteraçõe
 
 Para exportar a lista de anúncios com problemas em formato XLSX, clique sobre o  ícone seta para baixo <i class="fas fa-download"></i>, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação dependerá do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX. 
 
-<div class="alert alert-info">
-  O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
-  </div>
+>ℹ️ O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
 
 ## Aba Aguardando Conclusão
 
@@ -234,6 +230,4 @@ Você será redirecionado à página correspondente para realizar as alteraçõe
 
 Para exportar a lista de anúncios aguardando conclusão em formato XLSX, clique sobre o ícone seta para baixo <i class="fas fa-download"></i>, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação dependerá do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX.
 
-<div class="alert alert-info">
-O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
-</div>
+>ℹ️ O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
diff --git a/docs/tutorials/pt/oms-page-structure.md b/docs/tutorials/pt/oms-page-structure.md
index 7bb29494d..2bff6096c 100644
--- a/docs/tutorials/pt/oms-page-structure.md
+++ b/docs/tutorials/pt/oms-page-structure.md
@@ -33,9 +33,7 @@ A barra não mostra a posição exata das lojas que estão nas 5 primeiras posi
 
 Para todos os dados de variações de pedidos, e também para os números de evolução no ranking, a cor verde indica um resultado positivo; azul, neutro; e vermelho, negativo.
 
-<div class="alert alert-warning">
-Importante: se a comparação de pedidos é feita com base em 0 pedidos no passado, a variação é de 0%.
-</div>
+>⚠️ Importante: se a comparação de pedidos é feita com base em 0 pedidos no passado, a variação é de 0%.
 
 ![barra-de-status-oms pt](https://images.ctfassets.net/alneenqid6w5/4LWth3g02ACyIe4kAAgaW4/375d254b73d0fe7a0b2ae42da0a35b12/barra_de_status_pt.png)
 
diff --git a/docs/tutorials/pt/opening-hours-suiteshare.md b/docs/tutorials/pt/opening-hours-suiteshare.md
index 6c6c0aac0..d20a47eb3 100644
--- a/docs/tutorials/pt/opening-hours-suiteshare.md
+++ b/docs/tutorials/pt/opening-hours-suiteshare.md
@@ -15,9 +15,7 @@ legacySlug: horario-de-atendimento-suiteshare
 subcategory: 4y4ylvqceE6vVqEF8IWZix
 ---
 
-<div class="alert alert-danger">
-  <p>Funcionalidade disponível apenas para os planos Business e Enterprise.</p>
-</div>
+>❗ Funcionalidade disponível apenas para os planos Business e Enterprise.
 
 Além de organizar e distribuir os atendimentos, você pode definir horários de atendimento ou os turnos que sua equipe está atendendo. Quando o horário de atendimento estiver desabilitado ou fora do horário, será possível realizar as seguintes opções de configurações:  
 - [**Seletiva**](https://help.vtex.com/pt/tutorial/seletivo--7zjQVFhGbwYZ7NW8yKRSKX): o atendente/setor não aparecerão na listagem.
@@ -26,9 +24,7 @@ Além de organizar e distribuir os atendimentos, você pode definir horários de
 
 ![horario_suitshare_1](https://images.ctfassets.net/alneenqid6w5/5SYhzGHjrNpxQbrJ93Op0b/388d8adf88bb0d50c43cccaa34bde610/horario_suitshare_1.png)
 
-<div class="alert alert-warning">
-  <p><b>Nota</b>: Para configurar o horário de atendimento você deve ter organizado seu atendimento de forma seletiva, sequencial ou geolocalizado.</p>
-</div>
+>⚠️ **Nota**: Para configurar o horário de atendimento você deve ter organizado seu atendimento de forma seletiva, sequencial ou geolocalizado.
 
 Acesse o **link âncora** que irá distribuir os atendimentos. 
 
@@ -40,9 +36,7 @@ Defina o horário de atendimento clicando no **botão de relógio** localizado a
 
 ![horario_suitshare_4](https://images.ctfassets.net/alneenqid6w5/4Wf7YIwXrwTE4InVBvoy4n/3a3961c1508758b73776cb7a071ab70a/horario_suitshare_4.png)
 
-<div class="alert alert-danger">
-  <p>A disponibilidade padrão de todos os atendentes está configurada para 24 horas. Dessa forma, qualquer modificação deve ser feita de forma individual.</p>
-</div>
+>❗ A disponibilidade padrão de todos os atendentes está configurada para 24 horas. Dessa forma, qualquer modificação deve ser feita de forma individual.
 
 Defina os dias disponíveis e horários de cada atendente. 
 
@@ -50,12 +44,8 @@ Defina os dias disponíveis e horários de cada atendente. 
 
 Clique no botão **Finalizar**. 
 
-<div class="alert alert-danger">
-  <p>Caso você tenha um atendente fixo e ele não esteja no seu horário de atendimento, não será aplicado a regra de atendente fixo. Ou seja, seu cliente será redirecionado para o próximo atendente habilitado. .</p>
-</div>
+>❗ Caso você tenha um atendente fixo e ele não esteja no seu horário de atendimento, não será aplicado a regra de atendente fixo. Ou seja, seu cliente será redirecionado para o próximo atendente habilitado. .
 
-<div class="alert alert-warning">
-  <p>As alterações de disponibilidade (dia e horário) somente serão salvas se forem confirmadas por meio do botão <b>Finalizar</b>.</p>
-</div>
+>⚠️ As alterações de disponibilidade (dia e horário) somente serão salvas se forem confirmadas por meio do botão **Finalizar**.
 
 Pronto, agora é só configurar os horários de toda a sua equipe.
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
index 755945565..4b0bfd960 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
@@ -57,17 +57,13 @@ Essa classificação é importante para que o time de suporte priorize os chamad
 
 *Se o nível indicado não se aplicar ao cenário da solicitação, o agente pode modificá-lo.*
 
-<div class="alert alert-info">
-<strong>Normal:</strong> perguntas em geral.
-</div>
+>ℹ️ **Normal:** perguntas em geral.
 
 <div class = "alert alert-warning">
 <strong>Alto:</strong> documentações importantes estão inviabilizando o processo.
 </div>
 
-<div class="alert alert-danger">
-<strong>Urgente:</strong> Admin bloqueado, ameaçando o lucro dos seus negócios.
-</div>
+>❗ **Urgente:** Admin bloqueado, ameaçando o lucro dos seus negócios.
 
 ## Interagindo no chamado
 
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support.md b/docs/tutorials/pt/opening-tickets-to-vtex-support.md
index 4621a4a8d..4ac1b2a47 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support.md
@@ -17,7 +17,7 @@ subcategory: 1VvCpaa8NCA6a0MK6W6oWg
 
 Todos os clientes têm acesso a atendimento fornecido pelo time de especialistas do [Suporte VTEX](https://help.vtex.com/pt/faq/como-funciona-o-suporte-da-vtex--3kACEfni4m8Yxa1vnf2ebe). Os especialistas estão preparados para proporcionar a melhor experiência possível para a solução dos chamados. Para contatá-los, é necessário abrir um chamado por meio do sistema de tickets.
 
-<div class="alert alert-info">É necessário <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">habilitar a autorização de suporte</a> no <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">License Manager</a> para que o usuário tenha acesso ao Suporte da VTEX. Esta configuração é válida apenas para contas no Brasil.</div>
+>ℹ️ É necessário [habilitar a autorização de suporte](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) no [License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) para que o usuário tenha acesso ao Suporte da VTEX. Esta configuração é válida apenas para contas no Brasil.
 
 Este artigo explica como clientes devem abrir chamados no Suporte VTEX e acompanhar o status dos chamados. Para saber mais sobre disponibilidade, tempo estimado de resposta (SLA) e recursos disponíveis para clientes no Brasil, leia o artigo [Suporte VTEX - Brasil](https://help.vtex.com/pt/faq/suporte-vtex-brasil--5q861sTw1n7H2BENOu7ls9).
 
diff --git a/docs/tutorials/pt/operational-capacity-beta.md b/docs/tutorials/pt/operational-capacity-beta.md
index 11220fc89..c3d3cc66f 100644
--- a/docs/tutorials/pt/operational-capacity-beta.md
+++ b/docs/tutorials/pt/operational-capacity-beta.md
@@ -31,9 +31,7 @@ Ao acessar no Admin VTEX **Envio > Capacidade operacional**, você encontra uma
 
 ![operational_capacity_image1_PT](https://images.ctfassets.net/alneenqid6w5/5k7wWTuVZk7Ylc2IHpNE5C/750c0ac19cbb24293a58ccadeb4604b8/operational_capacity_image1_PT.png)
 
-<div class="alert alert-warning">
-Os sellers que aparecem na interface são os sellers da sua operação, e eles são previamente configurados pela nossa equipe. Para acrescentar um novo seller, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>⚠️ Os sellers que aparecem na interface são os sellers da sua operação, e eles são previamente configurados pela nossa equipe. Para acrescentar um novo seller, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 O gráfico apresenta os dados abaixo:
 
@@ -99,9 +97,7 @@ A capacidade operacional do seller pode ser contabilizada em número de pedidos
     * **Quantidade de itens:** a capacidade operacional do seller será contada por número de itens do pedido.
 5. Clique em `Salvar alterações`.
 
-<div class="alert alert-warning">
-A plataforma tem algumas restrições com relação a <a href="https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers abrangentes</a>, saiba mais na seção <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidade-operacional-de-seller-abrangente">Capacidade operacional de seller abrangente</a>.
-</div>
+>⚠️ A plataforma tem algumas restrições com relação a [sellers abrangentes](https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI), saiba mais na seção [Capacidade operacional de seller abrangente](https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidade-operacional-de-seller-abrangente).
 
 ## Ações na página de detalhes do seller
 
@@ -119,9 +115,7 @@ No topo direito da página de detalhes do seller, existe um toggle para ativar o
 * **Ativar:** habilite o toggle para `Ativo` e clique em `Ativar`.
 * **Desativar:** desabilite o toggle para `Pausado` e clique em `Pausar`.
 
-<div class="alert alert-warning">
-A plataforma tem algumas restrições com relação a <a href="https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers abrangentes</a>, saiba mais na seção <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidade-operacional-de-seller-abrangente">Capacidade operacional de seller abrangente</a>.
-</div>
+>⚠️ A plataforma tem algumas restrições com relação a [sellers abrangentes](https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI), saiba mais na seção [Capacidade operacional de seller abrangente](https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#capacidade-operacional-de-seller-abrangente).
 
 ### Acompanhar capacidade utilizada
 
diff --git a/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md b/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
index f21734143..80921b68a 100644
--- a/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
+++ b/docs/tutorials/pt/optimization-of-shipping-options-at-checkout.md
@@ -34,17 +34,13 @@ O Checkout v6 da VTEX combina informações como CEP do cliente, localização d
 - **Mais econômica**: opção com o menor custo para o cliente.
 - **Mais rápida**: opção com o menor tempo de entrega.
 
-<div class="alert alert-warning">
-Quando somente um tipo de opção de entrega estiver disponível para um determinado pedido, as opções <b>Mais econômica</b> e <b>Mais rápida</b> não serão mostradas no Checkout.
-</div>
+>⚠️ Quando somente um tipo de opção de entrega estiver disponível para um determinado pedido, as opções **Mais econômica** e **Mais rápida** não serão mostradas no Checkout.
 
 ## Desabilitar a função Opções de entrega otimizadas
 
 A funcionalidade de **Opções de entrega otimizadas** está ativada por padrão no Checkout v6. Entretanto, em algumas regiões podem ocorrer cenários que contribuam para que esta função não seja utilizada. Em países como Espanha ou Estados Unidos, onde as opções disponíveis de entrega são similares, os consumidores preferem escolher a transportadora baseados no seu nível de confiança na empresa.
 
-<div class="alert alert-warning">
-Ao desabilitar esta função no Admin VTEX, todas as opções disponíveis de entrega serão exibidas no processo do Checkout. Entretanto, caso a funcionalidade de <a href="https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#">múltiplas entregas</a> esteja habilitada na loja e existam opções de entrega diferentes entre os itens selecionados no carrinho, as <b>Opções de entrega otimizadas</b> continuarão a ser exibidas. Ou seja, a otimização de entrega será necessária para lidar com os múltiplos pacotes (itens com diferentes opções de entrega).
-</div>
+>⚠️ Ao desabilitar esta função no Admin VTEX, todas as opções disponíveis de entrega serão exibidas no processo do Checkout. Entretanto, caso a funcionalidade de [múltiplas entregas](https://help.vtex.com/pt/tutorial/divisao-de-pedidos-e-divisao-de-entregas--jQvzA6QgSd51e2p6bthoV#) esteja habilitada na loja e existam opções de entrega diferentes entre os itens selecionados no carrinho, as **Opções de entrega otimizadas** continuarão a ser exibidas. Ou seja, a otimização de entrega será necessária para lidar com os múltiplos pacotes (itens com diferentes opções de entrega).
 
 Para desabilitar a função __Opções de entrega otimizadas__, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/order-allocation-algorithm-beta.md b/docs/tutorials/pt/order-allocation-algorithm-beta.md
index 54c11f689..c4f8b5229 100644
--- a/docs/tutorials/pt/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/pt/order-allocation-algorithm-beta.md
@@ -15,9 +15,7 @@ legacySlug: order-allocation-algorithm-beta
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 **Order Allocation Algorithm** é o algoritmo da plataforma VTEX que busca selecionar os sellers capazes de enviar os pedidos com os menores custos de [planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) e de [transportadoras](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) configuradas.
 
diff --git a/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md b/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
index a7d39d59f..e22908de7 100644
--- a/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Existem cenários em que os clientes podem solicitar o cancelamento de um pedido. Pode ser o [cancelamento automático no período](https://help.vtex.com/pt/tutorial/cancelamento-de-pedido-por-parte-do-cliente--3wEI6DUNtecooG2Ki4Akqo#cancelamento-no-prazo-de-carencia) de **carência para cancelamento,** ou, depois desse período, o [cancelamento aprovado pelo lojista](https://help.vtex.com/pt/tutorial/cancelamento-de-pedido-por-parte-do-cliente--3wEI6DUNtecooG2Ki4Akqo#cancelamento-aprovado-pelo-lojista).
 
-<div class="alert alert-danger">
-Uma vez que o pedido é cancelado, não é mais possível alterar o status do pedido.
-</div>
+>❗ Uma vez que o pedido é cancelado, não é mais possível alterar o status do pedido.
 
 <div class = "alert alert-warning">
 Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
@@ -46,9 +44,7 @@ O lojista deve aprovar ou rejeitar o pedido de cancelamento. Se o lojista não a
 
 Mesmo se o cancelamento solicitado pelo cliente for negado pelo lojista utilizando o [VTEX DO](https://help.vtex.com/pt/tutorial/vtex-do--7KMbRL4OslN8DTX9oiuCiu), é necessário que o lojista prossiga com o [faturamento](https://help.vtex.com/pt/tutorial/faturar-um-pedido--7p1h852V5t54KyscpgxE2v) do pedido, sendo isso que realmente faz o pedido seguir o seu fluxo.
 
-<div class="alert alert-warning">
-Se a funcionalidade <a href="https://help.vtex.com/pt/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8#ativacao-da-funcionalidade">Substituição de Pedidos</a> estiver ativada, os pedidos poderão ser alterados ou cancelados a qualquer momento, inclusive após o período de carência para cancelamento.
-</div>
+>⚠️ Se a funcionalidade [Substituição de Pedidos](https://help.vtex.com/pt/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8#ativacao-da-funcionalidade) estiver ativada, os pedidos poderão ser alterados ou cancelados a qualquer momento, inclusive após o período de carência para cancelamento.
 
 ## Motivo do cancelamento
 
diff --git a/docs/tutorials/pt/order-flow-and-status.md b/docs/tutorials/pt/order-flow-and-status.md
index 56e37258e..db54d3d61 100644
--- a/docs/tutorials/pt/order-flow-and-status.md
+++ b/docs/tutorials/pt/order-flow-and-status.md
@@ -34,9 +34,7 @@ Há quatro fluxos de pedidos possíveis na VTEX:
 - [Fluxo completo](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#fluxo-completo): é o fluxo de um pedido feito na loja responsável pela venda e entrega do pedido. Nesse caso, a loja atua simultaneamente como seller e marketplace. 
 - [Fluxo chain](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#fluxo-chain): é o fluxo do pedido visto pela loja que intermedia a venda entre marketplace e seller. Esse fluxo é similar ao fluxo de marketplace, no entanto, o processo de pagamento é feito somente no marketplace, e não na loja que atua como chain. Esse fluxo ocorre nos cenários de venda de [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4).
 
-<div class="alert alert-warning">
-Para os casos de pedidos incompletos, confira o artigo <a href="https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos--tutorials_294">Como funcionam os pedidos incompletos</a> para entender os motivos desse fluxo e de seu cancelamento.
-</div>
+>⚠️ Para os casos de pedidos incompletos, confira o artigo [Como funcionam os pedidos incompletos](https://help.vtex.com/pt/tutorial/entendendo-os-pedidos-incompletos--tutorials_294) para entender os motivos desse fluxo e de seu cancelamento.
 
 ### Fluxo do marketplace
 
@@ -64,9 +62,7 @@ Esse é o fluxo do pedido visto pela loja responsável pelo envio dos produtos q
 1. Quando o pedido é recebido pelo seller, seu status inicial é `Pedido aceito`.
 2. Logo após o pedido ser recebido pelo seller, o status do pedido passa automaticamente para `Aguardando autorização para despachar`. Esse é um status de espera, para que o marketplace sinalize que obteve a confirmação do pagamento do pedido.
 
-  <div class="alert alert-danger">
-  A plataforma permite o avanço manual do status <i>Aguardando autorização para despachar</i> clicando em <code>Autorizar despacho</code>. Porém, quando o seller avança manualmente, não significa que o marketplace liberou o pedido para manuseio, e isso implica em um desencontro de informações. Utilize a movimentação manual com cautela. Recomendamos utilizá-la somente mediante autorização do marketplace para o despacho do pedido.
-</div>
+  >❗ A plataforma permite o avanço manual do status <i>Aguardando autorização para despachar</i> clicando em `Autorizar despacho`. Porém, quando o seller avança manualmente, não significa que o marketplace liberou o pedido para manuseio, e isso implica em um desencontro de informações. Utilize a movimentação manual com cautela. Recomendamos utilizá-la somente mediante autorização do marketplace para o despacho do pedido.
 
 3. O status passa automaticamente para `Janela para cancelamento`. O pedido ficará nesse estágio até o limite da [janela para cancelamento](https://help.vtex.com/pt/tutorial/configuracoes-gerais/#pedidos).
 
@@ -78,20 +74,17 @@ A carência do cancelamento existe para que o cliente possa cancelar a compra se
     * **Pedido não cancelado**: se o tempo de carência expira e o cliente não solicita o cancelamento da compra, o status segue para `Pronto para manuseio`. Esse é o status que indica ao seller que o pedido já deve ser preparado para o envio.
     * **Pedido cancelado**: caso o cliente tenha solicitado o cancelamento, ao invés de seguir para o manuseio, o pedido segue para cancelamento, e o status passará para `Iniciando cancelamento`. 
 5. O pedido permanecerá no status `Pronto para manuseio` até que haja uma confirmação do seller de que ele iniciou o manuseio do pedido. A confirmação pode ser feita manualmente pelo Admi ou via integração com ERP utilizando a API [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
-<div class="alert alert-danger">
-Ao confirmar o início do manuseio, o seller assume a responsabilidade da reserva dos itens do pedido. A partir desse momento, se houver qualquer atualização no inventário, a plataforma VTEX desconsidera a reserva destes SKUs. Portanto, atualize o inventário para SKUs de um dado pedido apenas quando este for faturado. Dessa forma, evita-se a divergência de inventário dependendo da interação com a <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integração de backoffice</a> da sua loja.
-</div>
+>❗ Ao confirmar o início do manuseio, o seller assume a responsabilidade da reserva dos itens do pedido. A partir desse momento, se houver qualquer atualização no inventário, a plataforma VTEX desconsidera a reserva destes SKUs. Portanto, atualize o inventário para SKUs de um dado pedido apenas quando este for faturado. Dessa forma, evita-se a divergência de inventário dependendo da interação com a [integração de backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) da sua loja.
 
 6. Uma vez que o manuseio foi iniciado, é hora de faturar o pedido. A plataforma espera que a nota fiscal seja incluída. Caso haja algum erro, o status do pedido poderá permanecer em `Verificando nota fiscal`. Confira os [casos mais comuns](https://help.vtex.com/pt/tutorial/por-que-o-pedido-esta-no-status-verificando-fatura--5VJjxRjeH6SimiG0Wkk2gm) para que o pedido permaneça nesse status. Vale lembrar que se o pedido estiver parcialmente faturado, ele poderá voltar para o status `Pagamento aprovado` até que o lojista [inclua as notas fiscais](https://help.vtex.com/pt/tutorial/como-faturar-um-pedido-manualmente-beta--7p1h852V5t54KyscpgxE2v), que somadas devem corresponder ao valor total do pedido.
 7. O último status do fluxo é o `Faturado`, após o qual o seller deve concluir o envio do pedido.
 
-<div class="alert alert-danger">
-Note que:
-<ul>
-<li>O <b>cancelamento do pedido</b> pode ser iniciado em vários estágios do fluxo do pedido, seja por parte do cliente ou da loja. Nesse caso, após solicitado, o cancelamento o processo se dá de forma automática, incluindo o ressarcimento do valor pago ao cliente. O processo de cancelamento é finalizado quando chega ao estágio <i>Cancelado</i>.</li>
-<li>Sellers têm autonomia para forçar manualmente a movimentação de pedido durante o status <i>Aguardando autorização para despachar</i>. Isso implica em realizar a entrega sem que o marketplace tenha confirmado a liberação e sem o recebimento do pagamento do pedido. Em caso de movimentação manual, é dever do seller conferir se o pedido está apto a ser manuseado, inclusive se o pagamento foi confirmado.</li>
-</ul>
-</div>
+>❗ Note que:
+>
+> *O **cancelamento do pedido** pode ser iniciado em vários estágios do fluxo do pedido, seja por parte do cliente ou da loja. Nesse caso, após solicitado, o cancelamento o processo se dá de forma automática, incluindo o ressarcimento do valor pago ao cliente. O processo de cancelamento é finalizado quando chega ao estágio <i>Cancelado</i>.
+>
+> *Sellers têm autonomia para forçar manualmente a movimentação de pedido durante o status <i>Aguardando autorização para despachar</i>. Isso implica em realizar a entrega sem que o marketplace tenha confirmado a liberação e sem o recebimento do pagamento do pedido. Em caso de movimentação manual, é dever do seller conferir se o pedido está apto a ser manuseado, inclusive se o pagamento foi confirmado.
+> 
 
 ### Fluxo completo
 
@@ -105,8 +98,7 @@ O fluxo completo do pedido é visto pela loja que realiza a venda e entrega do p
     * **O pagamento do pedido é aprovado:** o status do pedido passa para `Pagamento aprovado` e começa o status `Janela para cancelamento`. Esse status delimita o tempo que o cliente tem para cancelar a compra sem a aprovação da loja. O pedido permanece nesse status até o [limite de tempo que foi configurado](https://help.vtex.com/pt/tutorial/configuracoes-gerais/#pedidos).
     * **O pagamento do pedido não é aprovado:** a plataforma inicia o processo de cancelamento. Isso acontece automaticamente com o status do pedido passando por `Pagamento negado` e `Cancelando`. O pedido permanece nesse status até que a plataforma finalize o cancelamento, e o status mude para `Cancelado`. Depois de o pedido ser cancelado, o fluxo é finalizado.
 4. Com o pagamento aprovado e o tempo de cancelamento expirado, o status do pedido passa para `Pronto para manuseio`. Esse status sinaliza para o lojista que o pagamento foi confirmado e que agora deve ser feito o manuseio do pedido. A loja deve confirmar para a plataforma que iniciou o manuseio para o pedido progredir no fluxo. A confirmação pode ser feita manualmente pelo Admin ou via [API](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) com um ERP, por exemplo, utilizando a rota [Start handling order](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/start-handling).
-<div class="alert alert-danger">
-Ao confirmar o início do manuseio, o seller assume a responsabilidade da reserva dos itens do pedido. A partir desse momento, se houver qualquer atualização no inventário, a plataforma VTEX desconsidera a reserva destes SKUs. Portanto, atualize o inventário para SKUs de um dado pedido apenas quando este for faturado. Dessa forma, evita-se divergência de inventário dependendo da interação com a <a href="https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide">integração de backoffice</a> da sua loja.</div>
+>❗ Ao confirmar o início do manuseio, o seller assume a responsabilidade da reserva dos itens do pedido. A partir desse momento, se houver qualquer atualização no inventário, a plataforma VTEX desconsidera a reserva destes SKUs. Portanto, atualize o inventário para SKUs de um dado pedido apenas quando este for faturado. Dessa forma, evita-se divergência de inventário dependendo da interação com a [integração de backoffice](https://developers.vtex.com/vtex-rest-api/docs/erp-integration-guide) da sua loja.
 
 5. Com o manuseio iniciado, o status do pedido passa para `Preparando entrega` e a próxima etapa é faturar o pedido. O sistema espera a nota fiscal com o status  `Verificando nota fiscal`. É preciso [incluir a Nota Fiscal](https://help.vtex.com/pt/tutorial/como-faturar-um-pedido-manualmente-beta--7p1h852V5t54KyscpgxE2v) que corresponda ao valor total do pedido. 
 6. Com as notas fiscais incluídas, o status do pedido passa para o último status do fluxo: `Faturado`. A loja deve então concluir o envio do pedido.
@@ -131,9 +123,7 @@ Saiba mais sobre cancelamento e reembolso nos artigos <a href="https://help.vtex
 
 Enquanto o cancelamento está sendo processado, o status do pedido permanece em `Cancelando`. Depois que o cancelamento é concluído, o status do pedido passa para `Cancelado`. 
 
-<div class="alert alert-danger">
-Observe que quando o cancelamento ocorre antes da loja iniciar o manuseio do pedido (status <i>Preparando manuseio</i>), os itens têm a <a href="https://help.vtex.com/pt/tutorial/how-does-reservation-work--tutorials_92">reserva cancelada</a> no inventário.  No entanto, se o cancelamento é feito após esse status, os itens já terão a <a href="https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#reserva-reconhecida">reserva reconhecida</a> no inventário e a loja deve atualizar a quantidade de itens do inventário para que os SKUs de um pedido cancelado tenham também a sua reserva cancelada. 
-</div>
+>❗ Observe que quando o cancelamento ocorre antes da loja iniciar o manuseio do pedido (status <i>Preparando manuseio</i>), os itens têm a [reserva cancelada](https://help.vtex.com/pt/tutorial/how-does-reservation-work--tutorials_92) no inventário.  No entanto, se o cancelamento é feito após esse status, os itens já terão a [reserva reconhecida](https://help.vtex.com/pt/tutorial/como-a-reserva-funciona--tutorials_92#reserva-reconhecida) no inventário e a loja deve atualizar a quantidade de itens do inventário para que os SKUs de um pedido cancelado tenham também a sua reserva cancelada.
 
 Para saber mais sobre cancelamento de pedidos, confira o artigo [Por que meu pedido foi cancelado](https://help.vtex.com/pt/faq/por-que-meu-pedido-foi-cancelado--frequentlyAskedQuestions_493).
 
@@ -160,9 +150,7 @@ Veja abaixo a tabela com os status de pedido. As informações da tabela estão
 - **Visto por:** em qual fluxo o status fica visível (marketplace, seller, chain e completo).
 - **Significado:** significado detalhado do status.  
 
-<div class="alert alert-warning">
-Observe que os status do fluxo completo do pedido (fluxo visto pelas lojas responsáveis pela venda e entrega dos pedidos) coincidem com os status de marketplace e seller. Alguns status podem ser vistos via API, mas não ficam visíveis no fluxo do pedido visto no Admin no módulo <b>Todos os pedidos</b>.
-</div>
+>⚠️ Observe que os status do fluxo completo do pedido (fluxo visto pelas lojas responsáveis pela venda e entrega dos pedidos) coincidem com os status de marketplace e seller. Alguns status podem ser vistos via API, mas não ficam visíveis no fluxo do pedido visto no Admin no módulo **Todos os pedidos**.
 
 <style type="text/css">
 .tg  {border-collapse:collapse;border-color:#ccc;border-spacing:0;}
diff --git a/docs/tutorials/pt/order-replacement.md b/docs/tutorials/pt/order-replacement.md
index 3305f9e45..2d3461a7d 100644
--- a/docs/tutorials/pt/order-replacement.md
+++ b/docs/tutorials/pt/order-replacement.md
@@ -19,9 +19,7 @@ subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 
 A [Alteração de itens](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190) é diferente da substituição de pedidos. Na substituição de pedido o cliente solicita as mudanças no pedido, e na alteração de itens a loja modifica o pedido.
 
-<div class="alert alert-danger">
-A funcionalidade está disponível para todas as lojas, no entanto, é preciso ativá-la para que seus clientes possam utilizá-la. 
-</div>
+>❗ A funcionalidade está disponível para todas as lojas, no entanto, é preciso ativá-la para que seus clientes possam utilizá-la.
 
 Neste artigo é possível consultar:
 
@@ -31,9 +29,7 @@ Neste artigo é possível consultar:
 
 ## Ativação da funcionalidade
 
-<div class="alert alert-danger">
-Se a Substituição de pedidos for ativada em lojas que têm customização na página Meus Pedidos, é preciso recriar a customização. A funcionalidade substitui a versão antiga da página (que está customizada) por uma página nova não customizada. Para esses casos, recomendamos que, antes de ativar a funcionalidade na sua loja, utilize um <a href="https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu">ambiente beta</a> e valide a ativação com customização.
-</div>
+>❗ Se a Substituição de pedidos for ativada em lojas que têm customização na página Meus Pedidos, é preciso recriar a customização. A funcionalidade substitui a versão antiga da página (que está customizada) por uma página nova não customizada. Para esses casos, recomendamos que, antes de ativar a funcionalidade na sua loja, utilize um [ambiente beta](https://help.vtex.com/pt/tutorial/acessar-o-ambiente-beta-pelo-dominio-myvtex-com--3BHM289568gcSwk2O80Asu) e valide a ativação com customização.
 
 Para ativar a funcionalidade, siga os passos abaixo:
 
@@ -83,8 +79,6 @@ Com a funcionalidade ativada, os clientes da sua loja têm acesso a uma nova pá
 
 Depois de clicar em `Alterar pedido` , o cliente é levado ao carrinho de compras e depois para o checkout, onde é possível realizar as alterações desejadas (endereço, tipo de entrega, forma de pagamento e SKU). O processo só é concluído quando a compra é finalizada. O cliente não é cobrado duas vezes pelo mesmo pedido.
 
-<div class="alert alert-warning">
-O aproveitamento do pagamento (utilizar o pagamento efetuado anteriormente) só pode ser usado se o valor do pedido novo for igual ao do pedido original. Se o pagamento anterior por cartão de crédito não for aproveitado, a cobrança anterior é automaticamente estornada.
-<p>Para formas de pagamento que expiram em até 2 dias (como boleto), o pagamento não pode ser reutilizado.
-</div>
+>⚠️ O aproveitamento do pagamento (utilizar o pagamento efetuado anteriormente) só pode ser usado se o valor do pedido novo for igual ao do pedido original. Se o pagamento anterior por cartão de crédito não for aproveitado, a cobrança anterior é automaticamente estornada.
+> <p>Para formas de pagamento que expiram em até 2 dias (como boleto), o pagamento não pode ser reutilizado.
 
diff --git a/docs/tutorials/pt/order-split-and-delivery-split.md b/docs/tutorials/pt/order-split-and-delivery-split.md
index cb60e608f..fe28e76f8 100644
--- a/docs/tutorials/pt/order-split-and-delivery-split.md
+++ b/docs/tutorials/pt/order-split-and-delivery-split.md
@@ -52,8 +52,6 @@ O pedido é atendido por um único seller, mas é preciso realizar mais de uma e
 
     Essa divisão é feita de forma automática e nativa para as lojas que possuem o Checkout V6, por meio do campo `allowMultipleDeliveries` indicado como `true` na API [Update orderForm configuration](https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm). A configuração padrão vem como "ativa" para que seja possível a realização de compras com modalidades de entrega diferentes em um mesmo carrinho.
 
-<div class="alert alert-danger">
-  Não recomendamos operar a loja com o campo <code>allowMultipleDeliveries</code> indicado como <i>false</i>. Nesta configuração, quando existirem itens no carrinho que não possuam nenhum método de entrega do tipo delivery em comum, ou seja, os SLAIDs são distintos, e o carrinho tenha algum pickup-point, não será possível concluir o pedido.
-</div>
+>❗ Não recomendamos operar a loja com o campo `allowMultipleDeliveries` indicado como <i>false</i>. Nesta configuração, quando existirem itens no carrinho que não possuam nenhum método de entrega do tipo delivery em comum, ou seja, os SLAIDs são distintos, e o carrinho tenha algum pickup-point, não será possível concluir o pedido.
 
 * **Docas distintas:** uma única loja oferece todos os itens de um pedido, mas no cálculo da rota de envio eles envolvem docas diferentes. Então é preciso _dividir os pacotes de entrega,_ mas sem dividir o pedido entre lojas distintas. Isso é feito automaticamente pela plataforma.
diff --git a/docs/tutorials/pt/order-status-table-oms.md b/docs/tutorials/pt/order-status-table-oms.md
index 08156b4e1..482d00ce9 100644
--- a/docs/tutorials/pt/order-status-table-oms.md
+++ b/docs/tutorials/pt/order-status-table-oms.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Este artigo tem como objetivo listar os valores compatíveis de status nos diversos sistemas internos e externos à VTEX.
 
-<div class="alert alert-warning">
-Caso válido para quando o pedido tem apenas uma transação.
-</div>
+>⚠️ Caso válido para quando o pedido tem apenas uma transação.
 
 <table style="width: 619px;" border="1" cellspacing="0" cellpadding="0"><tbody><tr style="height: 56px;"><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>Gerenciamento de Pedidos</b></td><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>Meus Pedidos</b>
 </td><td style="width: 126px; height: 56px;" valign="top"><p align="center"><b>Pagamentos</b></td><td style="width: 79px; height: 56px;" valign="top"><p align="center"><b>API Rest</b></td><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>WebService</b></td></tr><tr style="height: 82px;"><td style="width: 113px; height: 82px;" valign="top"><p align="center">Processando
diff --git a/docs/tutorials/pt/order-to-delivery.md b/docs/tutorials/pt/order-to-delivery.md
index 76a4ae268..a95023c45 100644
--- a/docs/tutorials/pt/order-to-delivery.md
+++ b/docs/tutorials/pt/order-to-delivery.md
@@ -15,15 +15,11 @@ legacySlug: pedidos-para-entrega
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>  
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).  
 
 **Pedidos para entrega** é uma página que permite gerenciar os pedidos que serão preparados na loja para envio ou coleta pelo cliente. Ela apresenta a quantidade de pedidos em cada categoria, além de alertas para pedidos atrasados ou com pendências.
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está disponível apenas para o aplicativo do VTEX Sales App.</p>
-</div>
+>ℹ️ Essa funcionalidade está disponível apenas para o aplicativo do VTEX Sales App.
 
 **Pedidos para entrega** permite que os vendedores acompanhem as etapas dos pedidos, por meio de informações de pedido e entrega dentro de cada categoria.
 
diff --git a/docs/tutorials/pt/order-transactional-email-templates.md b/docs/tutorials/pt/order-transactional-email-templates.md
index 603f24e5d..a5b92a4e1 100644
--- a/docs/tutorials/pt/order-transactional-email-templates.md
+++ b/docs/tutorials/pt/order-transactional-email-templates.md
@@ -17,9 +17,7 @@ subcategory: 4D5LrWwlHGmOWMomOaaGee
 
 O objetivo deste artigo é listar os templates de emails transacionais padrão referentes ao fluxo de um pedido. Além disso, vamos especificar o gatilho necessário para o disparo de cada email.
 
-<div class="alert alert-warning">
-Atenção: pedidos de origem Fulfillment não recebem emails transacionais da VTEX. Ou seja, neste caso, o disparo de emails fica a cargo do próprio marketplace.
-</div>
+>⚠️ Atenção: pedidos de origem Fulfillment não recebem emails transacionais da VTEX. Ou seja, neste caso, o disparo de emails fica a cargo do próprio marketplace.
 
 Para acessar os templates, siga os passos abaixo.
 
diff --git a/docs/tutorials/pt/orders-management-feed-v3-setup.md b/docs/tutorials/pt/orders-management-feed-v3-setup.md
index 8b72d8486..a163add19 100644
--- a/docs/tutorials/pt/orders-management-feed-v3-setup.md
+++ b/docs/tutorials/pt/orders-management-feed-v3-setup.md
@@ -23,13 +23,9 @@ O Feed v3 possibilita a personalização do feed com filtros e intervalos necess
 
 Isso quer dizer que é possível definir quais status estarão visíveis no feed de eventos da sua loja através da [API Feed Configuration](https://developers.vtex.com/reference/feed-v3#feedconfiguration). A lista com os possíveis status de pedido pode ser vista no artigo [Fluxo de pedido em Gerenciamento de pedidos](https://help.vtex.com/pt/tutorial/fluxo-de-pedido/#entendendo-os-status).
 
-<div class="alert alert-info">
-Se o objeto <code>filter</code> não for configurado na API, as atualizações de <strong>todos</strong> os status serão enviadas ao feed. 
-</div>
+>ℹ️ Se o objeto `filter` não for configurado na API, as atualizações de **todos** os status serão enviadas ao feed.
 
-<div class="alert alert-info"> 
-A AppKey que será usada na integração deve ser a mesma usada na configuração inicial.
-</div>
+>ℹ️ A AppKey que será usada na integração deve ser a mesma usada na configuração inicial.
 
 Um exemplo de body seria o seguinte:
 
@@ -52,17 +48,13 @@ O tempo de espera _default_ definido no campo é de 30 segundos, mas ele poderá
 
 O tempo de permanência de um evento no seu feed é definido em segundos no campo `MessageRetentionPeriodInSeconds`. Se um evento não receber interações dentro do tempo configurado, ele será excluído da fila do feed e os dados referentes a ele serão perdidos. O tempo máximo a ser definido no campo é de até 345600 segundos (4 dias). 
 
-<div class="alert alert-info">
-Para configurar e usar o Feed v3, é necessário ter um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?locale=pt">perfil de acesso</a> habilitado com o recurso <code>Feed v3 and Hook</code>, dentro do produto de <strong>OMS</strong>. 
-</div>
+>ℹ️ Para configurar e usar o Feed v3, é necessário ter um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc?locale=pt) habilitado com o recurso `Feed v3 and Hook`, dentro do produto de **OMS**.
 
 ## Como funcionam as APIs do Feed v3
 
 O Feed v3 trabalha com duas chamadas: uma para a sua leitura e outra para informar que um evento já foi lido e deve ser excluído.
 
-<div class="alert alert-warning"> 
-Não se esqueça de configurar o Feed antes de usar!
-</div>
+>⚠️ Não se esqueça de configurar o Feed antes de usar!
 
 ### Get feed order status
 
@@ -70,9 +62,7 @@ A [chamada de leitura do feed](https://developers.vtex.com/reference/feed-v3#get
 
 O parâmetro `maxLot` indica o número máximo de eventos que serão retornados a cada chamada. No feed v3, você pode especificar __até 10 eventos__. 
 
-<div class="alert alert-warning">
-Toda vez que uma chamada de leitura do feed é feita, <strong>todos</strong> os eventos retornados ficam invisíveis no feed pelo tempo definido no campo <code>visibilityTimeoutInSeconds</code> da API de Feed Configuration.
-</div> 
+>⚠️ Toda vez que uma chamada de leitura do feed é feita, **todos** os eventos retornados ficam invisíveis no feed pelo tempo definido no campo `visibilityTimeoutInSeconds` da API de Feed Configuration. 
 
 ### Confirm item feed order status
 
@@ -82,15 +72,11 @@ No body do _commit_ deve ser passado o valor do `handles`. Esse valor é retorna
 
 No body, cada _array_ pode conter quantos `handles` forem necessários. Isso significa que é possível _commitar_ mais de um evento por vez.
 
-<div class="alert alert-info">
-O campo <code>visibilityTimeoutInSeconds</code> indica o tempo máximo para realizar um <i>commit</i> de um evento. 
-</div> 
+>ℹ️ O campo `visibilityTimeoutInSeconds` indica o tempo máximo para realizar um <i>commit</i> de um evento. 
 
 Não existem casos em que um evento do feed não deva ser _commitado_. Seu sistema deve _commitar_ todos os eventos da sua fila. __Uma vez que um evento foi _commitado_, não é possível recuperá-lo no feed com o mesmo appkey.__
 
-<div class="alert alert-warning">
-Todos os possíveis status de pedido (considerando a filtragem, quando aplicável) devem ser tratados na integração para evitar a ocorrência de erros. Atenção especial deve ser dada ao status <code>Status Null</code>, que pode não ser identificado e acabar sendo mapeado como outro status, possivelmente gerando erros.
-</div> 
+>⚠️ Todos os possíveis status de pedido (considerando a filtragem, quando aplicável) devem ser tratados na integração para evitar a ocorrência de erros. Atenção especial deve ser dada ao status `Status Null`, que pode não ser identificado e acabar sendo mapeado como outro status, possivelmente gerando erros. 
 
 Para entender mais sobre o funcionamento do feed, acesse nosso artigo sobre [como funciona o feed do módulo de Gerenciamento de pedidos](https://help.vtex.com/pt/tutorial/como-funciona-o-feed-v3-do-modulo-de-gerenciamento-de-pedidos--5SzSKee2f666YCoWkm0eQC).
 
diff --git a/docs/tutorials/pt/out-of-stock-errors-in-marketplace-integration-orders.md b/docs/tutorials/pt/out-of-stock-errors-in-marketplace-integration-orders.md
index 39be1114f..15276e287 100644
--- a/docs/tutorials/pt/out-of-stock-errors-in-marketplace-integration-orders.md
+++ b/docs/tutorials/pt/out-of-stock-errors-in-marketplace-integration-orders.md
@@ -28,9 +28,7 @@ Erros de falta de estoque podem ocorrer por diferentes motivos, os mais comuns s
 
 Após solucionar o erro, o pedido deve ser reprocessado manualmente. No seu Admin, no módulo **MARKETPLACE > Conexões > Pedidos**, clique sobre o pedido com erro. Feito isso, o botão **Ações** se torna visível, clique sobre ele e escolha a opção **Reprocessar**.
 
-<div class="alert alert-info">
-Caso o erro persista, abra um <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt">chamado para suporte VTEX.</a>
-</div>
+>ℹ️ Caso o erro persista, abra um [chamado para suporte VTEX.](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt)
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/payment-methods.md b/docs/tutorials/pt/payment-methods.md
index 382b62e5a..12419bdf1 100644
--- a/docs/tutorials/pt/payment-methods.md
+++ b/docs/tutorials/pt/payment-methods.md
@@ -17,8 +17,6 @@ subcategory: 6uIlQ5imochc5LFi3dzCSv
 
 O VTEX Payment aceita como formas de pagamento boleto bancário, cartão de crédito e cartão de débito, sendo este último apenas em casos de integração com o [inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos--6N0QlieWqboSVU2ehgAVAb) - solução Omnichannel da VTEX.
 
-<div class="alert alert-danger">
-<strong>Atenção</strong>: em casos de integração com o inStore, o VTEX Payment só é suportado em devices <strong>Android</strong>. Até o momento, o VTEX Payment <strong>não</strong> funciona com a integração entre inStore e Windows.  
-</div>
+>❗ **Atenção**: em casos de integração com o inStore, o VTEX Payment só é suportado em devices **Android**. Até o momento, o VTEX Payment **não** funciona com a integração entre inStore e Windows.
 
 Quanto ao cartão de crédito, a plataforma aceita as seguintes bandeiras: Visa, Master Card, Elo, American Express, Banes Card, Hipercard, JCB, Aura, Hiper. Além disso, os pagamentos podem ser parcelados em até 12 vezes.
diff --git a/docs/tutorials/pt/payment-provider-protocol.md b/docs/tutorials/pt/payment-provider-protocol.md
index f79ac6a6c..e56205fff 100644
--- a/docs/tutorials/pt/payment-provider-protocol.md
+++ b/docs/tutorials/pt/payment-provider-protocol.md
@@ -68,9 +68,7 @@ O provedor deve encaminhar à VTEX, o [AOC](https://www.pcisecuritystandards.org
 - __Assinatura__: Documento assinado pelo representante da empresa e pelo QSA.
 - __Data de expiração__: a validade do AOC é de 1 ano após a data de assinatura.  Um AOC emitido a mais de 11 meses não deve ser encaminhado à VTEX, ou seja, com tempo inferior a 30 dias para a data de expiração.
 
-<div class="alert alert-danger">
-Os documentos SAQ (Self-Assessment Questionnaire) e AOC (Attestation of Compliance for Onsite Assessments – Merchants Version) não são aceitos no processo de integração da VTEX.
-</div>
+>❗ Os documentos SAQ (Self-Assessment Questionnaire) e AOC (Attestation of Compliance for Onsite Assessments – Merchants Version) não são aceitos no processo de integração da VTEX.
 
 #### Provedores de pagamentos com boletos, promissórias ou cartões de loja com bandeira própria (Private Label ou cartões em geral, mas que envolvam soluções com redirect)
 
@@ -93,9 +91,9 @@ Depois de receber os dados de acesso e implementar o back-end, o provedor deve i
 
 ![ppp-vtex-store-pt](https://images.ctfassets.net/alneenqid6w5/2sZn44SfDSGcUkgouQ2iyu/d4ba38eb2aed1c4a4072cddbc2b4decf/image.png)
 
-<div class="alert alert-warning">
-Para passar no processo de homologação, é necessário implementar uma lógica específica para lidar com os requisitos do teste. Nas requisições enviadas ao Test Suite, utilize o header extra <code>X-VTEX-API-Is-TestSuite = true</code> para identificá-las e mascarar qualquer cenário exigido.<br>Toda comunicação com servidores, seja durante o processo de homologação ou em produção, deve ocorrer via HTTPS, que por padrão utiliza a porta 443. É importante lembrar que toda comunicação HTTPS deve ser exclusivamente sobre TLS 1.2.
-</div> 
+>⚠️ Para passar no processo de homologação, é necessário implementar uma lógica específica para lidar com os requisitos do teste. Nas requisições enviadas ao Test Suite, utilize o header extra `X-VTEX-API-Is-TestSuite = true` para identificá-las e mascarar qualquer cenário exigido.
+>
+> Toda comunicação com servidores, seja durante o processo de homologação ou em produção, deve ocorrer via HTTPS, que por padrão utiliza a porta 443. É importante lembrar que toda comunicação HTTPS deve ser exclusivamente sobre TLS 1.2. 
 
 Após a instação, clique no item Apps no painel lateral esquerdo do Admin. Em seguida, selecione o app Payment Provider Test Suite para configurá-lo corretamente.
 
@@ -108,9 +106,7 @@ Feito isso, você encontrará um formulário com três seções: __Service info_
 * **Service URL:** Defina a URL do seu serviço de provedor. Essa URL será o endereço base do protocolo e deve seguir o formato determinado por ele. Por exemplo, se a URL do serviço for `https://example.com/`, a URL completa para o endpoint /payments será `https://example.com/payments`.
 * **AppKey e AppToken:** O botão Test with AppKey and AppToken permite que você escolha entre configurar os valores desses campos ou não, o que pode facilitar os testes durante a etapa de desenvolvimento. Se não habilitar essa opção, as credenciais serão enviadas nos headers como uma string vazia.
 
-<div class="alert alert-info">
-  <p>O Gateway armazena as credenciais das lojas configuradas na afiliação e as envia nos headers X-VTEX-API-AppKey e X-VTEX-API-AppToken. A exceção para isso são as integrações desenvolvidas com VTEX IO. Para elas, os headers serão enviados como x-provider-api-appKey e x-provider-api-appToken. Se você está desenvolvendo com o <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework">Payment Provider Framework (IO)</a>, isso é configurado pela opção usesProviderHeadersName. Veja as configurações disponíveis <a href="https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework#available-configurable-options">aqui</a>.
-</p></div>
+>ℹ️ O Gateway armazena as credenciais das lojas configuradas na afiliação e as envia nos headers X-VTEX-API-AppKey e X-VTEX-API-AppToken. A exceção para isso são as integrações desenvolvidas com VTEX IO. Para elas, os headers serão enviados como x-provider-api-appKey e x-provider-api-appToken. Se você está desenvolvendo com o [Payment Provider Framework (IO)](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework), isso é configurado pela opção usesProviderHeadersName. Veja as configurações disponíveis [aqui](https://developers.vtex.com/docs/guides/payments-integration-payment-provider-framework#available-configurable-options).
 
 #### Payment method
 
@@ -134,9 +130,7 @@ Quando você clicar no botão `Run Test`, o Test Suite irá chamar a **Service U
 * **Bank Invoice flow** Neste teste, nós enviamos uma requisição[ Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para `{{ServiceURL}}/payments`, esperando por uma resposta com status undefined e o campo `bankIssueInvoiceUrl` preenchido com a URL do ticket. Após 15 segundos, nós esperamos receber outra resposta no mesmo formato através de um POST da URL enviada no campo callbackUrl e com o status approved. Com a integração em produção, esta última chamada feita por `callbackUrl` é autenticada com as chaves de ambiente do parceiro: `vtex-app-key` e `vtex-app-token`. Mais detalhes sobre o fluxo de callback podem ser encontrados na seção [Autorização de pagamento](#autorizacao-de-pagamento).
 * **Redirect flow:** Este teste é dividido em dois passos. No primeiro, nós enviamos uma requisição [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) para {{ServiceURL}}/payments, esperando por uma resposta com status undefined e o campo redirectUrl preenchido com a URL que será utilizada para redirecionar o cliente. Após 15 segundos, nós esperamos receber outra resposta no mesmo formato através de um POST da URL enviada no campo `callbackUrl` e com o status approved. Com a integração em produção, esta última chamada feita por `callbackUrl` é autenticada com as chaves de ambiente do parceiro: `vtex-app-key` e `vtex-app-token`. Mais detalhes sobre o fluxo de callback podem ser encontrados na seção [Autorização de pagamento](#autorizacao-de-pagamento). Para o conector que irá utilizar o Redirect, não há necessidade de passar em todos os testes do Test Suite, apenas no de Redirect.
 
-<div class="alert alert-warning">
-No caso dos cartões de crédito, os testes obrigatórios são: Authorize, Denied, Cancel, Async Approved e Async Denied.
-</div>
+>⚠️ No caso dos cartões de crédito, os testes obrigatórios são: Authorize, Denied, Cancel, Async Approved e Async Denied.
 
 Para identificar como responder corretamente a cada um dos testes com cartão de crédito, utilize estes números específicos:
 
@@ -163,8 +157,7 @@ Tudo começa com a solicitação de um novo pagamento, após a criação de um n
 
 ![fluxo-atualizado-ppp](https://images.ctfassets.net/alneenqid6w5/7lQZhSFEff1iaN7t2UVVNE/2890bc7073210c268d7d429d0162c9b7/FLUXO1.png)
 
-<div class="alert alert-info">
-  O período padrão de 7 dias para novas tentativas de pagamento assíncronas só é aplicado quando o usuário não especifica um valor no campo <code>delayToCancel</code> do endpoint <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a> ou ao enviar o callbackURL.</div>
+>ℹ️ O período padrão de 7 dias para novas tentativas de pagamento assíncronas só é aplicado quando o usuário não especifica um valor no campo `delayToCancel` do endpoint [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments) ou ao enviar o callbackURL.
 
 ### Autorização de pagamento
 Nesse ponto a VTEX chama o endpoint __*/payments*__ e envia um payload com os dados de pagamento para o seu provedor. O provedor deve processar esses dados e enviar de volta a resposta, que deve conter um dos valores de status: __approved__, __denied__ ou __undefined__.
@@ -213,21 +206,15 @@ Veja abaixo, um exemplo de payload encaminhado junto ao callback URL:
 {"paymentId":"8B3BA2F4352545A8B1C5A215F356A01C","status":"approved","authorizationId":"184520","nsu":"21705348","tid":"21705348","acquirer":"pagarme","code":"0000","message":"Transação aprovada com sucesso","delayToAutoSettle":1200, "delayToAutoSettleAfterAntifraud":1200, "delayToCancel":86400,"cardBrand":"Mastercard","firstDigits":"534696","lastDigits":"6921","maxValue":16.6}
 ```
 
-<div class="alert alert-info">
-  Os valores dos parâmetros enviados no payload do callback substituem os valores originais informados na chamada do <a href="https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments">Create Payment</a>.  
-</div>
+>ℹ️ Os valores dos parâmetros enviados no payload do callback substituem os valores originais informados na chamada do [Create Payment](https://developers.vtex.com/docs/api-reference/payment-provider-protocol#post-/payments).
 
-<div class="alert alert-warning">
-  Caso os parâmetros de tempo de espera (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) não sejam enviados com a callback URL, os valores serão automaticamente configurados para 24 horas.
-</div>
+>⚠️ Caso os parâmetros de tempo de espera (<i>delayToAutoSettle</i> e <i>delayToAutoSettleAfterAntifraud</i>) não sejam enviados com a callback URL, os valores serão automaticamente configurados para 24 horas.
 
 Ao fazer a solicitação de callback, recomendamos que os provedores de pagamento utilizem a callback URL exatamente como recebida, o que garante que todos os parâmetros estejam incluídos.
 
 Ao chamar a CallbackURL, seu provedor deve enviar no request os headers *X-VTEX-API-AppKey* e *X-VTEX-API-AppToken*. Mais informações sobre isso na [seção de credenciais VTEX](/pt/tutorial/payment-provider-protocol#credenciais-vtex).
 
-<div class="alert alert-danger">
-Além da CallbackURL, se o status for <strong>undefined</strong>, a VTEX tentará novamente chamar o endpoint da autorização de pagamento. Se o status retornado nessas chamadas permanecer como <strong>undefined</strong>, as chamadas continuarão por até 7 dias. Por isso, <strong>é importante que seu provedor esteja pronto para receber a mesma autorização de pagamento várias vezes</strong>.
-</div>
+>❗ Além da CallbackURL, se o status for **undefined**, a VTEX tentará novamente chamar o endpoint da autorização de pagamento. Se o status retornado nessas chamadas permanecer como **undefined**, as chamadas continuarão por até 7 dias. Por isso, **é importante que seu provedor esteja pronto para receber a mesma autorização de pagamento várias vezes**.
 
 Uma vez que o pagamento foi processado pelo seu provedor, de forma direta ou assíncrona, movemos a transação de pagamento dentro da VTEX para o status *autorizado* ou *cancelado*, de acordo com o status da resposta do processamento.
 
@@ -251,9 +238,7 @@ Se a transação de pagamento for autorizada no Gateway da VTEX, ela poderá rec
 
 Quando o provedor recebe um pedido de liquidação, ele deve liquidar o pagamento e responder com informações de liquidação. Se essa chamada falhar, fazemos algumas retentativas, por até 1 dia.
 
-<div class="alert alert-danger">
-Seu provedor deve estar preparado para receber a mesma chamada de liquidação várias vezes.
-</div>
+>❗ Seu provedor deve estar preparado para receber a mesma chamada de liquidação várias vezes.
 
 Se a chamada de liquidação funcionar bem, movemos a transação de pagamento para o status *Finalizado*, e o fluxo termina com sucesso.
 
diff --git a/docs/tutorials/pt/payments-in-vtex-marketplaces.md b/docs/tutorials/pt/payments-in-vtex-marketplaces.md
index bb343746f..6f0c5a8dc 100644
--- a/docs/tutorials/pt/payments-in-vtex-marketplaces.md
+++ b/docs/tutorials/pt/payments-in-vtex-marketplaces.md
@@ -27,9 +27,7 @@ Pedidos realizados em um marketplace podem conter itens de múltiplos sellers, q
 
 Caso o seller seja o processador de pagamentos, ele deve operar sob as condições determinadas em nosso [Split de transação](https://help.vtex.com/pt/tutorial/split-payment#split-de-transacao). Da mesma forma, se o marketplace VTEX processar pagamentos, deve seguir o fluxo de [Split de recebíveis](https://help.vtex.com/pt/tutorial/split-payment--6k5JidhYRUxileNolY2VLx#split-de-recebiveis), ou realizar as suas transferências fora do ambiente da VTEX. 
 
-<div class="alert alert-info">
-Clientes VTEX no Brasil podem utilizar tanto o split de transação quanto o split de recebíveis. Já clientes VTEX em outros países devem utilizar somente o split de transação. Note que alguns países impõem restrições sobre o repasse de valores entre sellers e marketplaces. Informe-se sobre as restrições com as autoridades financeiras do seu país antes de construir sua arquitetura de pagamentos.
-</div>
+>ℹ️ Clientes VTEX no Brasil podem utilizar tanto o split de transação quanto o split de recebíveis. Já clientes VTEX em outros países devem utilizar somente o split de transação. Note que alguns países impõem restrições sobre o repasse de valores entre sellers e marketplaces. Informe-se sobre as restrições com as autoridades financeiras do seu país antes de construir sua arquitetura de pagamentos.
 
 Para definir os valores para repasse externo ao ambiente da VTEX, utilize os [relatórios do OMS](https://help.vtex.com/pt/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY) para calcular comissões. No Brasil, a movimentação ou repasse de valores em ambiente externo, sem a participação da plataforma VTEX, somente poderá ser realizada por instituições financeiras.
 
@@ -37,9 +35,7 @@ Para definir os valores para repasse externo ao ambiente da VTEX, utilize os [re
 
 Confira abaixo as configurações necessárias no seu Admin VTEX para criar comissões sobre pedidos de sellers e para tornar o seller ou marketplace o processador de pagamentos.
 
-<div class="alert alert-info">
-Caso a sua integração com sellers externos ou sellers VTEX seja feita por meio de API, confira <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-seller-processing-payments">External seller processing payment</a>. 
-</div>
+>ℹ️ Caso a sua integração com sellers externos ou sellers VTEX seja feita por meio de API, confira <a href = "https://developers.vtex.com/vtex-rest-api/docs/external-seller-processing-payments">External seller processing payment</a>.
 
 ### Configurar comissões para seller
 
diff --git a/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md b/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md
index 9b80b47d8..7ec2bc447 100644
--- a/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md
+++ b/docs/tutorials/pt/penetration-testing-and-vulnerability-notice.md
@@ -15,13 +15,9 @@ legacySlug: avaliacoes-de-seguranca-e-relatorios-de-vulnerabilidade
 subcategory: vONCJSxwN5qZiElOEtKkH
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade faz parte do produto <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ Esta funcionalidade faz parte do produto [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
-<div class="alert alert-warning">
-  <p>Se desejar uma análise do seu relatório de teste de penetração pela equipe de Segurança da VTEX, é necessário ter o VTEX Shield. Além disso, todos os testes de penetração devem ser previamente <a href="#agendar-teste-de-penetracao">agendados com a VTEX</a>. Qualquer teste realizado de forma autônoma sem aviso prévio à VTEX será considerado uma tentativa de ação não autorizada.</p>
-</div>
+>⚠️ Se desejar uma análise do seu relatório de teste de penetração pela equipe de Segurança da VTEX, é necessário ter o VTEX Shield. Além disso, todos os testes de penetração devem ser previamente [agendados com a VTEX](#agendar-teste-de-penetracao). Qualquer teste realizado de forma autônoma sem aviso prévio à VTEX será considerado uma tentativa de ação não autorizada.
 
 A VTEX avalia rigorosamente os recursos da plataforma, testando e identificando vulnerabilidades por meio de escaneamento e testes de penetração recorrentes. Essas verificações de vulnerabilidade são executadas periodicamente.
 
@@ -40,9 +36,7 @@ Neste guia, explicamos o procedimento para agendar um teste de penetração e re
 
 ## Agendar teste de penetração
 
-<div class="alert alert-warning">
-  <p>Somente lojas com o <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a> podem agendar testes de penetração e obter uma resposta do time de Segurança, com acesso a uma análise profunda do relatório do teste, conforme descrito nos procedimentos deste guia.</p>
-</div>
+>⚠️ Somente lojas com o [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh) podem agendar testes de penetração e obter uma resposta do time de Segurança, com acesso a uma análise profunda do relatório do teste, conforme descrito nos procedimentos deste guia.
 
 Para realizar um teste de penetração no ambiente da sua loja, é necessário alinhar o cronograma de testes com a VTEX, para organização interna e planejamento da equipe de segurança. Siga as instruções abaixo:
 
@@ -59,9 +53,7 @@ Para realizar um teste de penetração no ambiente da sua loja, é necessário a
 6. Realize o teste na data agendada, mediante a autorização da VTEX.
 7. Envie um relatório com os resultados no mesmo ticket para o [Suporte VTEX](https://help.vtex.com/pt/support).
 
-  <div class="alert alert-warning">
-    <p>É obrigatório seguir as orientações descritas em <a href="#relatorios-de-testes-de-penetracao">Relatórios de testes de penetração</a> para que o prazo de análise seja cumprido pela VTEX.</p>
-  </div>
+  >⚠️ É obrigatório seguir as orientações descritas em [Relatórios de testes de penetração](#relatorios-de-testes-de-penetracao) para que o prazo de análise seja cumprido pela VTEX.
 
    Nomeie uma pessoa de sua equipe de segurança para ser o ponto de contato da equipe de segurança da VTEX no processo de análise do relatório do teste.
 
@@ -69,9 +61,7 @@ A equipe de segurança da VTEX se dedica a realizar uma análise abrangente de t
 
 Em até 10 dias úteis após o recebimento do [relatório](#relatorios-de-testes-de-penetracao), a equipe identificará falsos positivos e reclassificará a gravidade das ameaças identificadas conforme necessário, seguindo as práticas recomendadas da VTEX. Cada decisão nesse processo será acompanhada de uma justificativa detalhada para garantir total transparência e compreensão.
 
-<div class="alert alert-warning">
-  <p>Lojas que estão se preparando para o go-live e desejarem realizar um teste de penetração também precisam agendá-lo com antecedência. Nesse caso, é obrigatório enviar o relatório com os resultados para o <a href="https://help.vtex.com/pt/support">Suporte VTEX</a> pelo menos <strong>45 dias</strong> antes da data planejada para o go-live. Neste período, a VTEX vai analisar o resultado e endereçar qualquer vulnerabilidade identificada no processo.</p>
-</div>
+>⚠️ Lojas que estão se preparando para o go-live e desejarem realizar um teste de penetração também precisam agendá-lo com antecedência. Nesse caso, é obrigatório enviar o relatório com os resultados para o [Suporte VTEX](https://help.vtex.com/pt/support) pelo menos **45 dias** antes da data planejada para o go-live. Neste período, a VTEX vai analisar o resultado e endereçar qualquer vulnerabilidade identificada no processo.
 
 ### Relatórios de testes de penetração
 
@@ -114,9 +104,7 @@ Nossos clientes são encorajados a reportar, de modo responsável, quaisquer vul
 
 Aqueles que desejarem reportar uma vulnerabilidade devem antes trabalhar com suas próprias equipes de segurança e desenvolvimento para realizar uma avaliação de segurança e eliminar  falsos positivos ou problemas oriundos de configurações personalizadas. Somente casos compatíveis com a [definição de vulnerabilidade](#definicao-de-vulnerabilidade) serão verificados.
 
-<div class="alert alert-warning">
-  <p>Consulte o documento <a href="https://vtex.com/br-pt/security/security-practices/">Práticas de Segurança da VTEX</a> e nossa <a href="https://help.vtex.com/pt/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX#risk-assessment-na-vtex">FAQ de Segurança</a> antes de reportar qualquer vulnerabilidade. Estes documentos esclarecem nossos processos e ajudam a eliminar falsos positivos.</p>
-</div>
+>⚠️ Consulte o documento [Práticas de Segurança da VTEX](https://vtex.com/br-pt/security/security-practices/) e nossa [FAQ de Segurança](https://help.vtex.com/pt/tutorial/the-risk-assessment-process--4K97IpqkpCpDYsZOSxtfkX#risk-assessment-na-vtex) antes de reportar qualquer vulnerabilidade. Estes documentos esclarecem nossos processos e ajudam a eliminar falsos positivos.
 
 Após esse procedimento, caso haja uma vulnerabilidade, siga estes passos:
 
@@ -125,9 +113,7 @@ Após esse procedimento, caso haja uma vulnerabilidade, siga estes passos:
 
   As vulnerabilidades devem ser reportadas individualmente, seguindo o modelo estabelecido. Caso tenha encontrado mais de uma vulnerabilidade em seu teste, preencha múltiplos modelos e anexe ao seu chamado.
 
-  <div class="alert alert-warning">
-    <p>Todas as informações devem ser preenchidas e são importantes para a avaliação. Comunicações de vulnerabilidade fora do padrão estabelecido não serão endereçadas pelo time de Segurança da VTEX.</p>
-  </div>
+  >⚠️ Todas as informações devem ser preenchidas e são importantes para a avaliação. Comunicações de vulnerabilidade fora do padrão estabelecido não serão endereçadas pelo time de Segurança da VTEX.
 
 3. Abra uma solicitação para o nosso [Suporte](https://help.vtex.com/pt/support) para registrar o aviso de vulnerabilidade de segurança. Não esqueça de anexar o modelo de comunicação de vulnerabilidades preenchido neste chamado.
 4. Salve o número do seu chamado, pois você poderá precisar dele em futuras comunicações.
diff --git a/docs/tutorials/pt/pickup-points-for-subscription-orders-beta.md b/docs/tutorials/pt/pickup-points-for-subscription-orders-beta.md
index e87febea9..e61b4ecf9 100644
--- a/docs/tutorials/pt/pickup-points-for-subscription-orders-beta.md
+++ b/docs/tutorials/pt/pickup-points-for-subscription-orders-beta.md
@@ -15,9 +15,7 @@ legacySlug: pontos-de-retirada-para-pedidos-de-assinatura-beta
 subcategory: 3RmFd9bgAeRAVGeBd7XDUr
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Um ponto de retirada é um local físico onde o cliente tem a opção de retirar o seu pedido, em vez de recebê-lo em casa. Um cenário para essa funcionalidade é a retirada em loja física, por exemplo.
 
@@ -28,9 +26,7 @@ Veja abaixo o que é necessário para habilitar essa funcionalidade.
 - [Requisitos](#requisitos)
 - [Escolher pontos de retirada](#escolher-pontos-de-retirada)
 
-<div class="alert alert-info">
-  <p>A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao <b>Checkout V6</b>.</p>
-</div>
+>ℹ️ A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao **Checkout V6**.
 
 ## Requisitos
 
diff --git a/docs/tutorials/pt/pickup-points-for-subscription-orders.md b/docs/tutorials/pt/pickup-points-for-subscription-orders.md
index f8561f52e..3cf368cea 100644
--- a/docs/tutorials/pt/pickup-points-for-subscription-orders.md
+++ b/docs/tutorials/pt/pickup-points-for-subscription-orders.md
@@ -24,9 +24,7 @@ Veja abaixo o que é necessário para habilitar essa funcionalidade.
 - [Requisitos](#requisitos)
 - [Escolher pontos de retirada](#escolher-pontos-de-retirada)
 
-<div class="alert alert-info">
-  <p>A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao <a href="https://help.vtex.com/pt/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH">Checkout V6</a>.</p>
-</div>
+>ℹ️ A funcionalidade de pontos de retirada está disponível apenas para as contas que já têm acesso ao [Checkout V6](https://help.vtex.com/pt/tutorial/ativar-o-checkout-v6--7qVqv3ptRvpVVplrvg8ruH).
 
 ## Requisitos
 
diff --git a/docs/tutorials/pt/pickup-points.md b/docs/tutorials/pt/pickup-points.md
index ccba58514..5d5e498a3 100644
--- a/docs/tutorials/pt/pickup-points.md
+++ b/docs/tutorials/pt/pickup-points.md
@@ -79,7 +79,7 @@ A VTEX considera que o ponto de retirada é uma forma de envio e, por isso, as c
     - a. No Admin VTEX, acesse **Configurações da loja > Storefront > Checkout**, ou digite *Checkout* na barra de busca no topo da página. 
     - b. Seleciona a configuração utilizada na loja e clique no ícone <i class="fas fa-cog"></i>.
     - c. Clique na aba **Checkout** na barra superior.
-    - d. Selecione o <i class="fas fa-toggle-on"></i> do campo **Endereço na nota fiscal para retirada em loja**.![NFpontoretiradaPT](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/491e27746972c957683057e5c944bb84/NFpontoretiradaPT.png)<div class="alert alert-warning">A opção de <b>Endereço na nota fiscal para retirada em loja</b> deve estar habilitada em todas as lojas do Brasil, pois é num requisito que a Nota Fiscal emitida contenha a informação do endereço do cliente, mesmo que a opção de entrega do pedido seja no ponto de retirada. O endereço preenchido pelo cliente será registrado no campo `invoiceData`do <a href="https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata">orderForm</a>.</div>
+    - d. Selecione o <i class="fas fa-toggle-on"></i> do campo **Endereço na nota fiscal para retirada em loja**.![NFpontoretiradaPT](https://images.ctfassets.net/alneenqid6w5/7yOdSylqbRcHEfT9c9OfwX/491e27746972c957683057e5c944bb84/NFpontoretiradaPT.png)>⚠️ A opção de **Endereço na nota fiscal para retirada em loja** deve estar habilitada em todas as lojas do Brasil, pois é num requisito que a Nota Fiscal emitida contenha a informação do endereço do cliente, mesmo que a opção de entrega do pedido seja no ponto de retirada. O endereço preenchido pelo cliente será registrado no campo `invoiceData`do [orderForm](https://developers.vtex.com/vtex-rest-api/reference/orderform-fields#invoicedata).
 
 6. Configurar a quantidade de pontos de retirada que são exibidos no checkout:
     - a. No Admin VTEX, acesse **Configurações da loja > Envio > Configurações**, ou digite *Envio* na barra de busca no topo da página e selecione *Configurações da loja / Envio*. 
diff --git a/docs/tutorials/pt/piperun-suiteshare.md b/docs/tutorials/pt/piperun-suiteshare.md
index 725cdefc8..0e95ff075 100644
--- a/docs/tutorials/pt/piperun-suiteshare.md
+++ b/docs/tutorials/pt/piperun-suiteshare.md
@@ -31,9 +31,7 @@ Com a Piperun podemos ter duas integrações diferentes: **Integração estáti
 
 ## Integração Dinâmica
 
-<div class="alert alert-warning">
-  <p>Na integração dinâmica, você envia os leads para um pipeline e estágio específico do seu funil e atribui a um usuário da sua conta PipeRun.</p>
-</div>
+>⚠️ Na integração dinâmica, você envia os leads para um pipeline e estágio específico do seu funil e atribui a um usuário da sua conta PipeRun.
 
 ![Piperun - Suiteshare_2](https://images.ctfassets.net/alneenqid6w5/5K6w6Kf2Y47ISe5j8umeIv/9a6b1f91d8d69ec27f1f85d799754af0/Piperun_-_Suiteshare_2.png)
 
@@ -57,9 +55,7 @@ Clique no botão **Salvar**.
 
 ## Integração Estática 
 
-<div class="alert alert-warning">
-  <p>Na integração estática, você envia os leads para um estágio específico do seu funil sem atribuir a nenhum usuário automaticamente.</p>
-</div>
+>⚠️ Na integração estática, você envia os leads para um estágio específico do seu funil sem atribuir a nenhum usuário automaticamente.
 
 ![Piperun - Suiteshare_7](https://images.ctfassets.net/alneenqid6w5/3adHKF0lGdefcI8eYzs3me/06cf495e6609100c1f06b944d80febff/Piperun_-_Suiteshare_7.png)
 
@@ -87,9 +83,7 @@ Copie a Hash fornecida pela Piperun. 
 
 ![Piperun - Suiteshare_13](https://images.ctfassets.net/alneenqid6w5/4ZKN2T0Y2GHgzM3fw4ltEN/a251d7d53b4c8a4a8f57a06ec2835008/Piperun_-_Suiteshare_13.png)
 
-<div class="alert alert-danger">
-  <p>Para copiar a Hash, é necessário clicar com o botão direito do mouse e selecione a opção copiar.</p>
-</div>
+>❗ Para copiar a Hash, é necessário clicar com o botão direito do mouse e selecione a opção copiar.
 
 Você ainda pode definir opcionais para esse lead, por exemplo: de onde ele veio, ou tags para sua identificação. 
 
diff --git a/docs/tutorials/pt/planner-actions-on-releases-beta.md b/docs/tutorials/pt/planner-actions-on-releases-beta.md
index 75588a2df..caddf09a7 100644
--- a/docs/tutorials/pt/planner-actions-on-releases-beta.md
+++ b/docs/tutorials/pt/planner-actions-on-releases-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-acoes-em-lancamentos-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>O <strong>Lançamentos</strong> está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ O **Lançamentos** está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam [FastStore](https://www.faststore.dev/).
 
 O módulo **Lançamentos** permite que você gerencie [lançamentos](https://help.vtex.com/pt/tutorial/planner-conceito-de-lancamento-beta--4pWhQTXG0aIIsi2TYxxRkZ) de forma a coordenar a criação, planejamento e publicação de alterações na sua loja. Um lançamento significa uma modificação ou um agrupamento de modificações que podem ser publicadas de forma conjunta.
 
@@ -36,9 +34,7 @@ Cada página apresenta uma visualização dos lançamentos e permite realizar a
 * [Publicar lançamento](#publicar-lancamento)
 * [Excluir lançamento](#excluir-lancamento)
 
-<div class="alert alert-warning">
-  <p>Na fase beta, os lançamentos precisam estar relacionados ao <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>, pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o <strong>Lançamentos</strong>, é necessário configurar o CMS conforme descrito em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ Na fase beta, os lançamentos precisam estar relacionados ao [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o **Lançamentos**, é necessário configurar o CMS conforme descrito em [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Criar lançamento
 
@@ -113,9 +109,7 @@ Para publicar o lançamento e tornar as modificações visíveis no storefront d
 
 Todos os [status de lançamentos](https://help.vtex.com/pt/tutorial/planner-conceito-de-lancamento-beta--4pWhQTXG0aIIsi2TYxxRkZ#status-de-lancamentos) permitem que um lançamento seja excluído, ou seja, que o lançamento seja deletado de forma permanente.
 
-<div class="alert alert-info">
-  <p>Se em vez de excluir um lançamento você desejar arquivá-lo, você deve despublicar o lançamento. Assim, o lançamento não é deletado e pode ser republicado a qualquer momento.</p>
-</div>
+>ℹ️ Se em vez de excluir um lançamento você desejar arquivá-lo, você deve despublicar o lançamento. Assim, o lançamento não é deletado e pode ser republicado a qualquer momento.
 
 Quando um lançamento no status `Publicado` é excluído, as modificações que ele agrupava são mantidas no storefront da loja, apenas o lançamento que agrupava as modificações deixa de existir.
 
diff --git a/docs/tutorials/pt/planner-calendar-page-beta.md b/docs/tutorials/pt/planner-calendar-page-beta.md
index 9dccb8df1..29d64b22d 100644
--- a/docs/tutorials/pt/planner-calendar-page-beta.md
+++ b/docs/tutorials/pt/planner-calendar-page-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-pagina-calendario-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>O <strong>Lançamentos</strong> está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ O **Lançamentos** está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam [FastStore](https://www.faststore.dev/).
 
 O módulo **Lançamentos** permite que você gerencie seus [lançamentos](https://help.vtex.com/pt/tutorial/planner-conceito-de-lancamento-beta--4pWhQTXG0aIIsi2TYxxRkZ) de forma a coordenar a criação, planejamento e publicação das modificações na sua loja. 
 
@@ -31,9 +29,7 @@ Existem três formas de visualização da página **Calendário**:
 
 O **Calendário** apresenta somente [lançamentos agendados](https://help.vtex.com/pt/tutorial/planner-acoes-em-lancamentos-beta--1zsomdifPEQkdV6RW93JyW#agendar). Para visualizar todos os seus lançamentos, acesse a página [Lançamentos](https://help.vtex.com/pt/tutorial/planner-pagina-lancamentos-beta--2p7IiVD6K8i1iRiwHph5sw).
 
-<div class="alert alert-warning">
-  <p>Na fase beta, os lançamentos precisam estar relacionados ao <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>, pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar <strong>Lançamentos</strong>, é necessário configurar o CMS conforme descrito em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ Na fase beta, os lançamentos precisam estar relacionados ao [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar **Lançamentos**, é necessário configurar o CMS conforme descrito em [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Visualização por mês
 
diff --git a/docs/tutorials/pt/planner-release-concept-beta.md b/docs/tutorials/pt/planner-release-concept-beta.md
index dace3ccb4..babfa269a 100644
--- a/docs/tutorials/pt/planner-release-concept-beta.md
+++ b/docs/tutorials/pt/planner-release-concept-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-conceito-de-lancamento-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>O <strong>Lançamentos</strong> está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ O **Lançamentos** está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam [FastStore](https://www.faststore.dev/).
 
 O gerenciamento de uma operação de ecommerce requer que o lojista faça uma série de atualizações na loja e muitas vezes elas estão relacionadas entre si. Um exemplo é a realização de uma campanha publicitária, em que diferentes elementos do storefront precisam ser configurados.
 
@@ -30,9 +28,7 @@ Um lançamento significa uma modificação ou um agrupamento de modificações q
 * Maior controle ao testar e revisar modificações antes de sua publicação.
 * Facilidade em agendar ou excluir grupos de modificações.
 
-<div class="alert alert-warning">
-  <p>Na fase beta, os lançamentos precisam estar relacionados ao <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>, pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o <strong>Lançamentos</strong>, é necessário configurar o CMS conforme descrito em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ Na fase beta, os lançamentos precisam estar relacionados ao [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o **Lançamentos**, é necessário configurar o CMS conforme descrito em [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 A funcionalidade pode ser acessada pelo menu de navegação do Admin VTEX **Lançamentos**, no qual existem as seguintes páginas:
 
diff --git a/docs/tutorials/pt/planner-releases-page-beta.md b/docs/tutorials/pt/planner-releases-page-beta.md
index 6416ee370..42a0209b4 100644
--- a/docs/tutorials/pt/planner-releases-page-beta.md
+++ b/docs/tutorials/pt/planner-releases-page-beta.md
@@ -15,9 +15,7 @@ legacySlug: planner-pagina-lancamentos-beta
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>O <strong>Lançamentos</strong> está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ O **Lançamentos** está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam [FastStore](https://www.faststore.dev/).
 
 O módulo **Lançamentos** permite que você [gerencie seus lançamentos](https://help.vtex.com/pt/tutorial/planner-acoes-em-lancamentos-beta--1zsomdifPEQkdV6RW93JyW) de forma a coordenar a criação, planejamento e publicação das modificações na sua loja.
 
@@ -27,9 +25,7 @@ Na página **Lançamentos**, todos os lançamentos que existem são apresentados
 
 A ordenação dos lançamentos agendados é feita com base na data de publicação: quanto mais longínquo no futuro é um lançamento primeiro ele aparece na listagem, e quanto mais distante no passado, por último ele aparece.
 
-<div class="alert alert-warning">
-  <p>Na fase beta, os lançamentos precisam estar relacionados ao <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>, pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o <strong>Lançamentos</strong>, é necessário configurar o CMS conforme descrito em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ Na fase beta, os lançamentos precisam estar relacionados ao [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o **Lançamentos**, é necessário configurar o CMS conforme descrito em [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 ## Visualização em lista
 
diff --git a/docs/tutorials/pt/portadores-vtex-tracking.md b/docs/tutorials/pt/portadores-vtex-tracking.md
index 0066301d0..7a4421fb2 100644
--- a/docs/tutorials/pt/portadores-vtex-tracking.md
+++ b/docs/tutorials/pt/portadores-vtex-tracking.md
@@ -53,9 +53,7 @@ Para adicionar um novo portador, vá na plataforma web no menu à esquerda:
 
 Os campos que não são obrigatórios são utilizados para fins de consulta, não impactam o funcionamento do sistema.
 
-<div class="alert alert-danger">
-Se o campo Fuso horário não for preenchido será considerado o fuso horário de Brasília (UTC -03:00) para o cálculo do horário da entrega para o cliente final.
-</div>
+>❗ Se o campo Fuso horário não for preenchido será considerado o fuso horário de Brasília (UTC -03:00) para o cálculo do horário da entrega para o cliente final.
 
 #### Dados de cadastro
 
@@ -68,9 +66,7 @@ Se o campo Fuso horário não for preenchido será considerado o fuso horário d
 
 Os campos que não são obrigatórios são utilizados para fins de consulta, não impactam o funcionamento do sistema.
 
-<div class="alert alert-danger">
-Se ao fazer o cadastro o email do portador não for preenchido, o portador não conseguirá utilizar o aplicativo VTEX Tracking.
-</div>
+>❗ Se ao fazer o cadastro o email do portador não for preenchido, o portador não conseguirá utilizar o aplicativo VTEX Tracking.
 
 #### Dados de contato
 
diff --git a/docs/tutorials/pt/predefined-roles.md b/docs/tutorials/pt/predefined-roles.md
index f3a898be6..b6ae27118 100644
--- a/docs/tutorials/pt/predefined-roles.md
+++ b/docs/tutorials/pt/predefined-roles.md
@@ -75,9 +75,7 @@ O recurso **Assisted Sales** causa o redirecionamento automático do usuário pa
 
 Portanto, recomendamos a utilização de duas contas separadas (com emails distintos) para usuários de televendas: uma conta para o perfil __Call center operator__ (com os recursos <em>Assisted Sales</em> e <em>View order</em>) e outra conta para realizar operações no Admin, se necessário.
 
-<div class="alert alert-warning">
-  Ao criar um <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#">perfil de acesso</a>, evite incluir <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">recursos</a> de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
-</div>
+>⚠️ Ao criar um [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#), evite incluir [recursos](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#) de televendas junto com outros recursos. Do contrário, o perfil pode não funcionar como esperado.
 
 Tabela de recursos:
 
@@ -144,9 +142,7 @@ Tabela de recursos:
 
 ## Sales App - Sales Associate
 
-<div class="alert alert-warning">
-  <p>Vendedores registrados no Sales App não têm acesso ao Admin VTEX, apenas ao Sales App.</p>
-</div>
+>⚠️ Vendedores registrados no Sales App não têm acesso ao Admin VTEX, apenas ao Sales App.
 
 Tabela de recursos:
 
diff --git a/docs/tutorials/pt/price-divergence-rule.md b/docs/tutorials/pt/price-divergence-rule.md
index 639ee6bb9..7cc26572e 100644
--- a/docs/tutorials/pt/price-divergence-rule.md
+++ b/docs/tutorials/pt/price-divergence-rule.md
@@ -19,9 +19,7 @@ Quando um seller vende em um marketplace, por vezes há uma diferença entre o p
 
 Para otimizar o processamento de pedidos com erro de diferença de preço, existe o fluxo de Autorização de pedidos, no qual o seller pode [configurar uma regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe). No Admin VTEX, acesse **Configurações da loja > Pedidos > Autorização de pedidos**, ou digite **Autorização de pedidos** na barra de busca no topo da página.
 
-<div class="alert alert-warning">
-Uma vez que o seller cria a regra de Divergência de valores, ela passa a valer para todos os marketplaces.
-</div>
+>⚠️ Uma vez que o seller cria a regra de Divergência de valores, ela passa a valer para todos os marketplaces.
 
 A regra de Divergência de valores é composta de uma ou mais regras de autorização de pedidos. Cada regra de autorização corresponde a um intervalo percentual do preço do pedido, e pode variar de 0% a 100%. É necessário associar uma entre três ações a cada regra de autorização:
 
@@ -33,9 +31,7 @@ A regra de Divergência de valores é composta de uma ou mais regras de autoriza
 
 Quando a [configuração de uma regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe) não foi feita, pedidos com erro de divergência de preço são aprovados automaticamente. Isso vale para marketplaces VTEX, marketplaces externos e conectores certificados (parceiros), mas não para [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex).
 
-<div class="alert alert-warning">
-Quando um seller está integrado a um conector nativo, como o Mercado Livre ou a B2W, mas não configurou uma regra de Divergência de valores, pedidos com erro por diferença de preço ficam pendentes até a criação da regra. É possível acompanhá-los no seu Admin VTEX, em <b>Marketplace > Conexões > Pedidos</b>.
-</div>
+>⚠️ Quando um seller está integrado a um conector nativo, como o Mercado Livre ou a B2W, mas não configurou uma regra de Divergência de valores, pedidos com erro por diferença de preço ficam pendentes até a criação da regra. É possível acompanhá-los no seu Admin VTEX, em **Marketplace > Conexões > Pedidos**.
 
 Após a criação da regra de Divergência de valores, pedidos de integrações com conectores nativos que apresentem diferença de preço passam a ser exibidos na página [Todos os pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi).
 
diff --git a/docs/tutorials/pt/price-divergence-rules-beta.md b/docs/tutorials/pt/price-divergence-rules-beta.md
index ab4b19ed0..62bb819d9 100644
--- a/docs/tutorials/pt/price-divergence-rules-beta.md
+++ b/docs/tutorials/pt/price-divergence-rules-beta.md
@@ -15,9 +15,7 @@ legacySlug: regra-de-alcada-em-divergencias-de-preco-para-sellers
 subcategory: 4ZBiXqnPntLbsijZ0djFcD
 ---
 
-<div class="alert alert-info">
-  <p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 Integrações entre sellers VTEX e [conectores nativos](https://help.vtex.com/pt/tutorial/integrando-com-marketplace--tutorials_402#integrado-a-conector-nativo-vtex) podem apresentar divergências nos preços configurados na VTEX e o que aparece na vitrine do marketplace, o que pode gerar erros no OMS.
 
@@ -35,9 +33,7 @@ Pedidos devem ser gerenciados e aprovados manualmente pelo OMS ou pelo [VTEX DO]
 
 Uma regra é configurada automaticamente com percentual de divergência entre 0% a 30% para `Negar automaticamente` os pedidos em seu Admin VTEX, e é possível alterá-la ou até mesmo criar mais de uma regra ao fazer a configuração.
 
-<div class="alert alert-info">
-Depois de configurar o mecanismo de regra de divergência de valores (Beta), não será mais necessário configurar o campo Divergência de Preço dentro da integração do marketplace. Caso você já tenha configurado o campo dentro da integração, a configuração realizada não será mais válida.
-</div>
+>ℹ️ Depois de configurar o mecanismo de regra de divergência de valores (Beta), não será mais necessário configurar o campo Divergência de Preço dentro da integração do marketplace. Caso você já tenha configurado o campo dentro da integração, a configuração realizada não será mais válida.
 
 ## Configuração de regra de divergência de valores (Beta)
 
@@ -88,10 +84,8 @@ Você tem duas formas de autorizar os pedidos com status `Aguardando autorizaç
 - [Autorizar manualmente no OMS](#autorizacao-de-pedidos)
 - [Autorizar pelo VTEX DO](#autorizacao-pelo-vtex-do)
 
-<div class="alert alert-warning">
-Você precisa ter permissão do owner da conta para autorizar os pedidos, caso contrário, a seguinte mensagem aparecerá na tela: 
-“Você ainda não possui regras de autorização. Então todos os casos de divergências são negados automaticamente."
-</div>
+>⚠️ Você precisa ter permissão do owner da conta para autorizar os pedidos, caso contrário, a seguinte mensagem aparecerá na tela: 
+> “Você ainda não possui regras de autorização. Então todos os casos de divergências são negados automaticamente."
 
 ### Autorização manual no OMS
 
diff --git a/docs/tutorials/pt/product-list.md b/docs/tutorials/pt/product-list.md
index 5ce47dec5..33bc074e9 100644
--- a/docs/tutorials/pt/product-list.md
+++ b/docs/tutorials/pt/product-list.md
@@ -30,7 +30,7 @@ A partir da lista de produtos, você pode realizar uma variedade de ações:
 
 Ao clicar no botão `CRIAR PRODUTO`, você abrirá a página para cadastro de um novo produto no catálogo. Acesse o artigo [Como criar um produto](https://help.vtex.com/pt/tutorial/como-criar-um-produto-beta--671zAWe0B9eCikzDu7kB1G) para saber como realizar esse procedimento.
 
-<div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+>⚠️ O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte.
 
 ## Buscar produtos
 
diff --git a/docs/tutorials/pt/product-registration-fields.md b/docs/tutorials/pt/product-registration-fields.md
index 9f916cf6a..9587608da 100644
--- a/docs/tutorials/pt/product-registration-fields.md
+++ b/docs/tutorials/pt/product-registration-fields.md
@@ -25,15 +25,16 @@ __Palavras Substitutas:__ sinônimos de termos relacionados ao nome dado para se
 
 __TextLink:__ utilizado para criar a URL do produto. Campo obrigatório. Para mais informações, confira o artigo [Como definir a URL de um produto](https://help.vtex.com/pt/tutorial/como-a-url-de-produto-e-montada--frequentlyAskedQuestions_368).
 
-<div class="alert alert-danger">
-  <p>Ao preencher o <b>textLink</b> do produto, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
-  <ul>
-<li><code>a</code></li>
-<li><code>meta</code></li>
-<li><code>api</code></li>
-<li><code>admin</code></li>
-</ul></p>
-</div>
+>❗ Ao preencher o **textLink** do produto, evite utilizar as seguintes palavras reservadas, pois isso pode prejudicar o desempenho da sua loja e interferir no funcionamento de páginas definidas no Admin VTEX. Veja a lista de palavras reservadas abaixo.
+>
+> *`a`
+>
+> *`meta`
+>
+> *`api`
+>
+> *`admin`
+> 
 
 __Título da Página (Tag Title):__ texto que fica na aba do navegador e corresponde ao título da página do produto. Este campo é importante para SEO.
 
@@ -73,9 +74,7 @@ Veja como criar as [especificações do seu Produto](https://help.vtex.com/pt/tu
 
 Se você tiver criado algum campo de produto obrigatório, o produto só poderá ser ativado após o preenchimento desta especificação.
 
-<div class="alert alert-info">
-Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo <a href="https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382">Por que o produto não aparece no site?</a> para entender como resolver esse problema.
-</div>
+>ℹ️ Se o seu produto não aparecer no site da sua loja após o cadastro, confira o artigo [Por que o produto não aparece no site?](https://help.vtex.com/pt/faq/por-que-o-produto-nao-aparece-no-site--frequentlyAskedQuestions_382) para entender como resolver esse problema.
 
 ### Saiba mais
 - [Produtos - Definição de conceito](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru)
diff --git a/docs/tutorials/pt/products-and-skus-beta.md b/docs/tutorials/pt/products-and-skus-beta.md
index e05be4416..036c06104 100644
--- a/docs/tutorials/pt/products-and-skus-beta.md
+++ b/docs/tutorials/pt/products-and-skus-beta.md
@@ -23,9 +23,7 @@ A página **Produtos e SKUs** possibilita visualizar e gerenciar a lista complet
 
 ![products-skus-pt](https://images.ctfassets.net/alneenqid6w5/3Euar7pKsXKgqIfz1MwOOa/42eb4310fbe66a016176c54adb447ad9/products-skus-pt.png)
 
-<div class="alert alert-info">
-  <p>Esta página está disponível somente para lojas que estão operando com o <a href="https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">Novo Admin VTEX</a>. Para acessar esta página e fazer parte de uma nova experiência, participe do <a href="https://content.vtex.com/participe-do-programa-beta-pt/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> do Novo Admin VTEX.</p>
-</div>
+>ℹ️ Esta página está disponível somente para lojas que estão operando com o [Novo Admin VTEX](https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa). Para acessar esta página e fazer parte de uma nova experiência, participe do [programa Beta](https://content.vtex.com/participe-do-programa-beta-pt/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta) do Novo Admin VTEX.
 
 A página permite que você realize as seguintes ações:
 
@@ -83,9 +81,7 @@ A lista de produtos pode ser filtrada conforme a sua necessidade. Você pode uti
 
 Selecione os filtros desejados e clique em `Aplicar` para filtrar os produtos. Para cancelar a seleção, clique em `Limpar`.
 
-<div class="alert alert-warning">
-  <p>Não é possível filtrar produtos por <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w">seller</a> ou por data da pré-venda nesta versão do Catálogo.</p>
-</div>
+>⚠️ Não é possível filtrar produtos por [seller](https://help.vtex.com/pt/tutorial/o-que-e-um-seller--5FkLvhZ3Few4CWWIuYOK2w) ou por data da pré-venda nesta versão do Catálogo.
 
 ## Acompanhar status de produtos
 
diff --git a/docs/tutorials/pt/promotions-beta.md b/docs/tutorials/pt/promotions-beta.md
index bc6ceb792..6941f2db9 100644
--- a/docs/tutorials/pt/promotions-beta.md
+++ b/docs/tutorials/pt/promotions-beta.md
@@ -15,9 +15,7 @@ legacySlug: promocoes-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class="alert alert-danger">
-<p>Esta funcionalidade será descontinuada no dia 16 de maio de 2022. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>❗ Esta funcionalidade será descontinuada no dia 16 de maio de 2022. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 A plataforma VTEX disponibiliza uma forma otimizada e prática de cadastrar diversos tipos de promoção que se adequam a diferentes cenários. Por meio de uma interface centralizada para gerenciamento de promoções, sua loja pode oferecer mais benefícios focados na atração e fidelização de clientes.
 
@@ -99,9 +97,7 @@ Este efeito gera um desconto total sobre o valor do produto definido como brinde
 - __SKUs__: opção que permite selecionar o SKU que será o brinde da compra.
 - __Quantidade máxima por compra__: opção que permite selecionar a quantidade máxima de brindes que uma compra pode receber.
 
-<div class="alert alert-warning">
-<p>O produto <b>Brinde</b> também precisa ter um preço cadastrado, mesmo que seja dado de graça ao cliente.</p>
-</div>
+>⚠️ O produto **Brinde** também precisa ter um preço cadastrado, mesmo que seja dado de graça ao cliente.
 
 #### Frete
 
@@ -130,9 +126,7 @@ Este efeito gera um desconto total sobre o valor do produto definido como brinde
   - __UTM Source.__
   - __Faixa de código postal.__
 
-<div class="alert alert-info">
-<p>Caso você queira vincular um <a href= "https://help.vtex.com/pt/tutorial/como-criar-cupom--tutorials_319?&utm_source=autocomplete">cupom já existente</a> à nova promoção, é necessário selecionar as opções de UTM Campaign e UTM Source e informar os códigos do cupom.</p>
-</div>
+>ℹ️ Caso você queira vincular um <a href= "https://help.vtex.com/pt/tutorial/como-criar-cupom--tutorials_319?&utm_source=autocomplete">cupom já existente</a> à nova promoção, é necessário selecionar as opções de UTM Campaign e UTM Source e informar os códigos do cupom.
 
 ### Cupons
 Caso você queira criar um novo cupom associado à promoção, clique em __NOVO CUPOM__ e preencha os campos a seguir:
@@ -145,15 +139,11 @@ Ao clicar em __Opções Avançadas__, existe a possibilidade de configurar um ca
 
 - __Limitar uso__: opção que limita a quantidade de vezes que o cupom pode ser utilizado.
 
-<div class="alert alert-warning">
-<p>Para salvar o novo cupom, é necessário clicar no botão <b>OK</b>. Se a janela for fechada sem essa confirmação, o cupom não será criado.</p>
-</div>
+>⚠️ Para salvar o novo cupom, é necessário clicar no botão **OK**. Se a janela for fechada sem essa confirmação, o cupom não será criado.
 
 Ao criar um novo cupom para a nova promoção, ele passará a ser exibido também na aba __Cupom__ do módulo __Promoções e Taxas__. Além disso, suas condições de UTM Source e/ou UTM Campaign serão vinculadas automaticamente à promoção nova no filtro __Clientes Específicos__.
 
-<div class="alert alert-warning">
-<p>Se as condições de UTM Source e UTM Campaign forem alteradas na configuração do filtro <b>Clientes Específicos</b> após a criação do cupom por esse fluxo, o cupom será excluído.</p>
-</div>
+>⚠️ Se as condições de UTM Source e UTM Campaign forem alteradas na configuração do filtro **Clientes Específicos** após a criação do cupom por esse fluxo, o cupom será excluído.
 
 ### Restrições
 - __Limitar uso na sua loja__: limita a quantidade de vezes que a promoção pode ser aplicada na loja.
diff --git a/docs/tutorials/pt/promotions-simulator-beta.md b/docs/tutorials/pt/promotions-simulator-beta.md
index e196c9b2a..da1df9e58 100644
--- a/docs/tutorials/pt/promotions-simulator-beta.md
+++ b/docs/tutorials/pt/promotions-simulator-beta.md
@@ -15,9 +15,7 @@ legacySlug: simulador-de-promocoes-beta
 subcategory: 1yTYB5p4b6iwMsUg8uieyq
 ---
 
-<div class="alert alert-warning">
-  <p>Os usuários devem possuir um <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> com autorização para acessar o módulo <strong>Promoções </strong>no Admin VTEX para utilizar o <strong>Simulador de promoções</strong>.</p>
-</div>
+>⚠️ Os usuários devem possuir um [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) com autorização para acessar o módulo **Promoções **no Admin VTEX para utilizar o **Simulador de promoções**.
 
 O **Simulador de promoções** é uma ferramenta que permite visualizar as promoções criadas na sua loja VTEX que foram aplicadas no carrinho de compras e os motivos para sua ativação. Também é possível testar a aplicação de promoções antes de ativá-las, incluindo promoções agendadas e inativas.
 
@@ -47,9 +45,7 @@ A interface do **Simulador de promoções** apresenta as seguintes informações
 | **Total** | Preço total que será cobrado pelo produto, considerando descontos da promoção e quantidade de itens. |
 | **Desconto** | Status do desconto no carrinho, que pode ser `Aplicado` ou `Não aplicado`. O status `Aplicado` indica que ao menos uma promoção foi aplicada ao produto. |
 
-<div class="alert alert-info">
-  <p>Envie um feedback sobre sua experiência utilizando o **Simulador de promoções** a partir do botão de megafone <i class="fas fa-megaphone"></i> no canto direito da tela.</p>
-</div>
+>ℹ️ Envie um feedback sobre sua experiência utilizando o **Simulador de promoções** a partir do botão de megafone <i class="fas fa-megaphone"></i> no canto direito da tela.
 
 ### Atualizar simulador
 
@@ -92,9 +88,7 @@ Para fazer uma simulação, siga as instruções abaixo:
 
     Você verá o resultado da simulação a partir das promoções selecionadas. Para visualizar se as promoções testadas foram aplicadas aos itens do carrinho na simulação, observe o status da coluna **Desconto** ou clique no produto.
 
-<div class="alert alert-info">
-  <p>É possível aplicar promoções em produtos que já possuem uma promoção ativa. Apesar do conflito entre elas, o sistema VTEX sempre seleciona a promoção mais benéfica para os clientes da sua loja, considerando o preço total dos itens ou frete.</p>
-</div>
+>ℹ️ É possível aplicar promoções em produtos que já possuem uma promoção ativa. Apesar do conflito entre elas, o sistema VTEX sempre seleciona a promoção mais benéfica para os clientes da sua loja, considerando o preço total dos itens ou frete.
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/promotions-simulator.md b/docs/tutorials/pt/promotions-simulator.md
index eb7a6b0d1..fed33983b 100644
--- a/docs/tutorials/pt/promotions-simulator.md
+++ b/docs/tutorials/pt/promotions-simulator.md
@@ -15,9 +15,7 @@ legacySlug: simulador-de-promocoes
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class="alert alert-info">
-<p>Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 O **Simulador de promoções** permite visualizar as promoções aplicadas ao carrinho e suas condições. Com diversas possibilidades de configuração de promoções, é importante ter visibilidade da [concorrência](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270) e do [acúmulo](https://help.vtex.com/pt/tutorial/entendendo-a-concorrencia-de-promocoes--tutorials_2270?&utm_source=autocomplete#acumular) de promoções durante a compra e das causas de ativação de promoções.
 
diff --git a/docs/tutorials/pt/qr-code-suiteshare.md b/docs/tutorials/pt/qr-code-suiteshare.md
index 8fa24372a..97493ab88 100644
--- a/docs/tutorials/pt/qr-code-suiteshare.md
+++ b/docs/tutorials/pt/qr-code-suiteshare.md
@@ -23,9 +23,7 @@ No VTEX Assisted Sales (SuiteShare) você conseguirá unir a tecnologia dos QRCO
 
 Se na sua empresa, você utiliza materiais impressos, esses códigos são a melhor opção para levar os clientes do offline para o online.
 
-<div class="alert alert-warning">
-  <p>Antes de começar, você já deverá ter criado um link para cada número de WhatsApp. Se ainda não fez isso, é só <a href="https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB">acessar esse link</a>.</p>
-</div>
+>⚠️ Antes de começar, você já deverá ter criado um link para cada número de WhatsApp. Se ainda não fez isso, é só [acessar esse link](https://help.vtex.com/pt/tutorial/links--7h7YXPFovF2k5z6ZSZs5WB).
 
 No painel do VTEX Assisted Sales (SuiteShare), acesse a opção _**Atrair > Links**_.
 
diff --git a/docs/tutorials/pt/ready-to-dispatch.md b/docs/tutorials/pt/ready-to-dispatch.md
index 81eb6d8c3..99c9b7b31 100644
--- a/docs/tutorials/pt/ready-to-dispatch.md
+++ b/docs/tutorials/pt/ready-to-dispatch.md
@@ -15,13 +15,13 @@ legacySlug: pronto-para-envio
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/).
 
-<div class="alert alert-warning">
-<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92">Painel VTEX Shipping Network</a></li><li><a href="https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq">Entregas Correios</a></li><li>Pronto para envio</li></ul></p>
-</div>
+>⚠️ O [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:
+> 
+> *[Painel VTEX Shipping Network](https://help.vtex.com/pt/tutorial/painel-vtex-shipping-network--51e8tx1IehiN4ZtURRWU92)
+> * [Entregas Correios](https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq)
+> * Pronto para envio
 
 Quando um pedido está pronto para o envio e com a nota fiscal inserida na plataforma ([faturado](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/2WgQrlHTyVo4hLjhUs1LMT)), a loja providencia a etiqueta de envio e notifica a transportadora que o envio deve ser feito.
 
@@ -71,9 +71,7 @@ Você pode organizar a lista de pacotes de duas formas, clicando nas opções ao
 * `Data da criação`: ordena pela data em que os pedidos foram criados.
 * `Data da fatura`: ordena pela data em que as notas fiscais foram criadas.
 
-<div class="alert alert-warning">
-O <b>Pronto para envio</b> emite etiquetas para todos os <a href="https://help.vtex.com/pt/tutorial/faturar-um-pedido-manualmente--7p1h852V5t54KyscpgxE2v">pedidos faturados</a> no Admin VTEX cujos itens foram referenciados na nota fiscal, seja via API no ERP ou manualmente. No entanto, apenas as etiquetas de transportadoras vinculadas ao <b>VTEX Shipping Network</b> possuem layout e rastreabilidade válidos via API.
-</div>
+>⚠️ O **Pronto para envio** emite etiquetas para todos os [pedidos faturados](https://help.vtex.com/pt/tutorial/faturar-um-pedido-manualmente--7p1h852V5t54KyscpgxE2v) no Admin VTEX cujos itens foram referenciados na nota fiscal, seja via API no ERP ou manualmente. No entanto, apenas as etiquetas de transportadoras vinculadas ao **VTEX Shipping Network** possuem layout e rastreabilidade válidos via API.
 
 ### Impressão de etiquetas
 
@@ -94,9 +92,7 @@ As transportadoras são notificadas quando é feito o download das etiquetas.
 
 ![etiquetas](https://images.contentful.com/alneenqid6w5/1L1fExGcJgTPi3WD5nmWBL/7714df72cacfafda1d915aa86cc1203e/etiquetas.png)
 
-<div class="alert alert-danger">
-Em caso de erros ou dúvidas, entre em contato diretamente com o suporte do <b>VTEX Shipping Network</b> através do email vtexlog@vtex.com.br.
-</div>
+>❗ Em caso de erros ou dúvidas, entre em contato diretamente com o suporte do **VTEX Shipping Network** através do email vtexlog@vtex.com.br.
 
 ### Alterar o tipo do tamanho das etiquetas
 
diff --git a/docs/tutorials/pt/received-skus-beta.md b/docs/tutorials/pt/received-skus-beta.md
index 269757e34..9782a3fc8 100644
--- a/docs/tutorials/pt/received-skus-beta.md
+++ b/docs/tutorials/pt/received-skus-beta.md
@@ -55,9 +55,7 @@ Para verificar todas as especificações de um produto, clique sobre o nome do p
 
 Na seção **Problemas,** estão disponíveis todos os anúncios que ainda não foram aprovados, por existirem problemas que precisam ser corrigidos pelo seller. Os filtros, ações e campos de identificação disponíveis na seção **[Pendentes](#pendentes)** são similares aos da seção Problemas.
 
-<div class="alert alert-info">
-A ação pedir correção não está disponível na seção <b>Problemas.</b>
-</div>
+>ℹ️ A ação pedir correção não está disponível na seção **Problemas.**
 
 Para identificar qual o problema de um anúncio, basta clicar no nome do produto desejado. Uma nova janela será exibida com as informações referentes ao produto, a mensagem de erro e o revisor do anúncio.
 
@@ -85,9 +83,7 @@ Cada linha da lista representa um produto com as seguintes informações:
 - **Seller:** nome do seller que enviou o anúncio.  
 - **Data de envio:** mostra quando o anúncio foi enviado ao marketplace.  
 
-<div class="alert alert-info">
-Os anúncios listados nessa seção estão sendo avaliados pelo Matcher e pelo Offer Quality ou Auto approve, caso tenham sido configurados. Após essa avaliação o anúncio pode ser enviado para as seções <b>Pendentes, Problemas, Aprovados ou Bloqueados</b>, a depender do cumprimento de requisitos.
-</div>
+>ℹ️ Os anúncios listados nessa seção estão sendo avaliados pelo Matcher e pelo Offer Quality ou Auto approve, caso tenham sido configurados. Após essa avaliação o anúncio pode ser enviado para as seções **Pendentes, Problemas, Aprovados ou Bloqueados**, a depender do cumprimento de requisitos.
 
 ### Bloqueados
 
@@ -126,17 +122,13 @@ Nesse caso, os itens serão ordenados de forma crescente ou decrescente ao clica
 
 Todos os SKUs exibidos na lista já estão disponíveis para catalogação. Entretanto, recomenda-se realizar o [mapeamento de categorias e marcas](https://help.vtex.com/pt/tutorial/mapeamento-de-categorias-e-marcas-para-marketplace-vtex-beta--6NU8LwR6i0tTb8nk30bnbE) antes desse passo para que o processo de catalogação seja mais rápido.
 
-<div class="alert alert-warning">
-Os anúncios presentes na seção Pendentes permanecem disponíveis por apenas 30 dias. Depois desse período, elas expiram automaticamente e o Seller precisará enviar novamente.
-</div>
+>⚠️ Os anúncios presentes na seção Pendentes permanecem disponíveis por apenas 30 dias. Depois desse período, elas expiram automaticamente e o Seller precisará enviar novamente.
 
 ### Opções de catalogação
 
 Para catalogar um anúncio acesse a página **SKUs recebidos** no Admin VTEX clicando em **Marketplace > SKUs recebidos** ou digite **SKUs recebidos** na barra de busca do Admin.
 
-<div class="alert alert-info">
-Todos os anúncios da seção Pendentes podem ser catalogados individualmente ou em massa.
-</div>
+>ℹ️ Todos os anúncios da seção Pendentes podem ser catalogados individualmente ou em massa.
 
 As ações disponíveis para catalogação são:
 
@@ -149,9 +141,7 @@ As ações disponíveis para catalogação são:
 
 ![criar-novos-produtos-PT](https://images.ctfassets.net/alneenqid6w5/4H2vmekbrtbXQXUVrwVoSF/07a3e80b2b4143779da1ebfdd29729a7/criar-novos-produtos-PT.png)
 
-<div class="alert alert-info">
-Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
-</div>
+>ℹ️ Esta ação pode ser realizada nas seções de anúncios **Pendentes** e **Problemas**.
 
 - **Associar a um produto existente:** cria uma relação entre o produto do seller e um produto que já existe no catálogo do marketplace. Para executar essa ação siga os passos abaixo:
 
@@ -167,9 +157,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
 Imagine que o marketplace já tenha o SKU Camisa Branca nos tamanhos P, M e G. Mas, recentemente, o seller enviou para estoque os tamanhos PP e GG da mesma Camisa Branca.  
 Ao criar uma nova associação, os tamanhos novos são agrupados com os demais que já estavam cadastrados. Dessa forma, o produto terá os tamanhos PP, P, M, G e GG disponíveis.
 
-<div class="alert alert-info">
-Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
-</div>
+>ℹ️ Esta ação pode ser realizada nas seções de anúncios **Pendentes** e **Problemas**.
 
 - **Associar a um SKU existente:** cria uma relação entre o novo SKU do seller e um SKU que já existe no catálogo do marketplace. Para executar essa ação siga os passos abaixo:
 
@@ -186,9 +174,7 @@ Um possível caso seria o de um marketplace ter o “celular XYZ” com memória
 
 Agora, digamos que o mesmo marketplace recebeu do “seller2” o mesmo SKU 128GB. Assim, para não duplicar o catálogo, o marketplace precisa associar esses SKUs.
 
-<div class="alert alert-info">
-Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>.
-</div>
+>ℹ️ Esta ação pode ser realizada nas seções de anúncios **Pendentes** e **Problemas**.
 
 - **Recusar e bloquear:** bloqueia os anúncios selecionados e estes não serão mais reprocessados automaticamente. Para executar essa ação siga os passos abaixo:
 
@@ -202,9 +188,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
 Quando um SKU é bloqueado pelo marketplace, significa que na próxima vez que o seller enviar seus produtos, aqueles que foram bloqueados não estarão mais em meio aos enviados. É possível desbloquear um SKU por API REST, se o marketplace deseja voltar a recebê-lo como sugestão do seller.  
 Para saber mais sobre aprovação de SKUs, acesse nossa documentação [Send SKU Suggestion](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-).
 
-<div class="alert alert-info">
-Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>Problemas</b>. Os anúncios bloqueados serão exibidos na seção <b>Bloqueados</b>.
-</div>
+>ℹ️ Esta ação pode ser realizada nas seções de anúncios **Pendentes** e **Problemas**. Os anúncios bloqueados serão exibidos na seção **Bloqueados**.
 
 - **Recusar para correção:** rejeita o anúncio e envia para o seller a solicitação de correção de informação. Para executar essa ação siga os passos abaixo:
 
@@ -215,9 +199,7 @@ Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b> e <b>P
 
 ![recusar-e-corrigir-PT](https://images.ctfassets.net/alneenqid6w5/62XmAvuM9luOqmLCwLpW2A/e53cdbf195194a408fb05f790f812083/recusar-e-corrigir-PT.png)
 
-<div class="alert alert-info">
-Esta ação pode ser realizada nas seções de anúncios <b>Pendentes</b>. Os anúncios para correção serão exibidos na seção <b>Problemas</b>.
-</div>
+>ℹ️ Esta ação pode ser realizada nas seções de anúncios **Pendentes**. Os anúncios para correção serão exibidos na seção **Problemas**.
 
 **Aprovação automática:** também é possível configurar a aprovação automática de SKUs de um seller específico, independente da sua pontuação do Matcher. Essa ação só pode ser realizada por meio de API Rest. Confira as documentações de [Suggestions](https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions), para saber mais.
 
diff --git a/docs/tutorials/pt/reconciliation-of-accounts-receivable.md b/docs/tutorials/pt/reconciliation-of-accounts-receivable.md
index 34eaa56ad..1757d14cc 100644
--- a/docs/tutorials/pt/reconciliation-of-accounts-receivable.md
+++ b/docs/tutorials/pt/reconciliation-of-accounts-receivable.md
@@ -41,9 +41,7 @@ Para isso, confira o passo a passo:
 6. Selecione um __mês__ do ano;
 7. Clique no botão cinza __Exportar__.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: o relatório apresenta as datas de captura do adquirente. Ou seja, o momento em que o adquirente detectou o pagamento da compra. Por outro lado, o dia em que a compra foi feita pode ser consultado no módulo Gerenciamento de Pedidos. 
-</div>
+>ℹ️ **Atenção**: o relatório apresenta as datas de captura do adquirente. Ou seja, o momento em que o adquirente detectou o pagamento da compra. Por outro lado, o dia em que a compra foi feita pode ser consultado no módulo Gerenciamento de Pedidos.
 
 Por fim, o relatório é encaminhado para a pasta de download do computador.
 
diff --git a/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
index cba43e35d..1f500fe12 100644
--- a/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
+++ b/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -76,9 +76,7 @@ Para configurar um novo número de WhatsApp você precisará ter acesso de admin
   <li>Cole o número de telefone copiado na etapa anterior, e selecione a opção de <strong>SMS</strong>, clique em <code>Avançar</code>.</li>
 </ol>
 
-<div class="alert alert-warning">
-  O número gerado pode ser americano, mas se a sua página do Facebook for verificada, seus clientes verão o nome da empresa. Caso não esteja verificada, recomendamos seguir o <a href="https://www.facebook.com/business/help/2058515294227817?id=180505742745347">processo de verificação com a Meta</a>.
-</div>
+>⚠️ O número gerado pode ser americano, mas se a sua página do Facebook for verificada, seus clientes verão o nome da empresa. Caso não esteja verificada, recomendamos seguir o [processo de verificação com a Meta](https://www.facebook.com/business/help/2058515294227817?id=180505742745347).
 
 <ol start="13">
   <li>Copie o código de verificação exibido no Admin VTEX.</li>
@@ -96,9 +94,7 @@ Para configurar um novo número de WhatsApp você precisará ter acesso de admin
   <li>Clique em <code>Finalizar</code>.</li>
 </ol>
 
-<div class="alert alert-warning">
-Após ativada uma campanha de recuperação de checkout abandonado, pode levar até 48 horas para as métricas de análise começarem a ser exibidas.
-</div>
+>⚠️ Após ativada uma campanha de recuperação de checkout abandonado, pode levar até 48 horas para as métricas de análise começarem a ser exibidas.
 
 <div class = "alert alert-info">
 Saiba mais sobre o <a href="https://help.vtex.com/pt/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">Gerenciamento e detalhes do WhatsApp AI Campaigns</a>.
diff --git a/docs/tutorials/pt/redirect-from-other-addresses.md b/docs/tutorials/pt/redirect-from-other-addresses.md
index 7b1ede2a7..e16266a7a 100644
--- a/docs/tutorials/pt/redirect-from-other-addresses.md
+++ b/docs/tutorials/pt/redirect-from-other-addresses.md
@@ -31,9 +31,7 @@ Existem diversas maneiras de configurar redirecionamentos, sendo o uso do <code>
 
 A seguir, apresentaremos instruções para configurar redirecionamentos para o endereço principal da sua loja utilizando a ferramenta [Direcionar](http://direcionar.com.br/), por sua simplicidade de uso.
 
-<div class="alert alert-warning">
-  <p>O <a href="http://direcionar.com.br/">Direcionar</a> não é um serviço da VTEX e não funciona com HTTPS. Existem outros serviços similares, e a VTEX não recomenda nenhum específico. A VTEX não se responsabiliza por problemas causados por serviços externos de redirecionamento.</p>
-</div>
+>⚠️ O [Direcionar](http://direcionar.com.br/) não é um serviço da VTEX e não funciona com HTTPS. Existem outros serviços similares, e a VTEX não recomenda nenhum específico. A VTEX não se responsabiliza por problemas causados por serviços externos de redirecionamento.
 
 ### Redirecionamento de endereço sem subdomínio (como www)
 
diff --git a/docs/tutorials/pt/redirection-from-other-addresses.md b/docs/tutorials/pt/redirection-from-other-addresses.md
index 2e7507fe9..7a781cae9 100644
--- a/docs/tutorials/pt/redirection-from-other-addresses.md
+++ b/docs/tutorials/pt/redirection-from-other-addresses.md
@@ -24,9 +24,7 @@ Veja o exemplo abaixo:
 
 Esse redirecionamento pode ser feito de inúmeras formas, sendo o uso do `htaccess` no servidor uma das mais conhecidas. Mas por ser uma solução bastante técnica e que depende de outros fatores, sugerimos o uso do serviço [Direcionar.com.br](http://direcionar.com.br).
 
-<div class="alert alert-warning">
-<strong> Vale ressaltar que o Direcionar não é um serviço da VTEX e não funciona com HTTPS</strong>. Existem outros serviços similares, e você é livre para escolher a opção que mais lhe convenha.
-</div>
+>⚠️ ** Vale ressaltar que o Direcionar não é um serviço da VTEX e não funciona com HTTPS**. Existem outros serviços similares, e você é livre para escolher a opção que mais lhe convenha.
 
 Este guia contém as instruções para que você faça redirecionamentos para o endereço principal da sua loja. Confira este outro artigo para saber como [configurar acesso sem www](https://help.vtex.com/pt/tutorial/configurando-acesso-sem-www--tutorials_4278).
 
diff --git a/docs/tutorials/pt/redirects.md b/docs/tutorials/pt/redirects.md
index b72a0491e..2bad539da 100644
--- a/docs/tutorials/pt/redirects.md
+++ b/docs/tutorials/pt/redirects.md
@@ -17,9 +17,7 @@ subcategory: 1wvyJwJhKgewxGeAGCVmM6
 
 **Redirecionamentos** direciona o cliente para qualquer outra página, seja interna ou externa à loja. Esse redirecionamento é feito na área de busca do seu storefront, utilizando termos ou filtros selecionados pelo cliente. Desse modo, uma das vantagens dos Redirecionamentos é contemplar cenários de comunicação que a busca de catálogo da loja não abrange, como o redirecionamento de uma pesquisa por uma marca para a sua página promocional.
 
-<div class="alert alert-warning">
-<p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo VTEX Intelligent Search: configurações Multi-idioma (Beta) para saber mais.</p>
-</div>
+>⚠️ Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo VTEX Intelligent Search: configurações Multi-idioma (Beta) para saber mais.
 
 ## Como o redirecionamento funciona
 
diff --git a/docs/tutorials/pt/regionalization-beta.md b/docs/tutorials/pt/regionalization-beta.md
index 0667fb821..db7b82c00 100644
--- a/docs/tutorials/pt/regionalization-beta.md
+++ b/docs/tutorials/pt/regionalization-beta.md
@@ -15,9 +15,7 @@ legacySlug: regionalizacao-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 A Regionalização é uma funcionalidade do [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) que permite otimizar os resultados de busca de acordo com a disponibilidade de sellers na região do cliente. Para instalar e configurar o VTEX Intelligent Search na sua loja, leia o nosso artigo [Search](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search).
 
@@ -36,9 +34,7 @@ Para começar a utilizar a Regionalização, você precisa seguir as etapas abai
 2. [Solicitação para ativar a Regionalização](#2-solicitacao-para-ativar-a-regionalizacao)
 3. [Configuração no VTEX IO](#3-configuracao-no-vtex-io)
 
-<div class="alert alert-warning">
-  <p>Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.</p>
-</div>
+>⚠️ Apesar de lojas regionalizadas mostrarem apenas produtos disponíveis em uma determinada região na página de listagem de produtos, os filtros não levam em consideração a regionalização. Por conta dessa limitação, é possível que os clientes da loja selecionem valores de filtros que resultam em produtos indisponíveis em sua região.
 
 ## 1. Configuração de sellers 
 
diff --git a/docs/tutorials/pt/registering-a-category.md b/docs/tutorials/pt/registering-a-category.md
index b2f5d69e8..fe496fd35 100644
--- a/docs/tutorials/pt/registering-a-category.md
+++ b/docs/tutorials/pt/registering-a-category.md
@@ -15,9 +15,7 @@ legacySlug: cadastrando-categoria
 subcategory: 1E7tziZCkY4w8i4EmUuwec
 ---
 
-<div class="alert alert-info">
-Na plataforma VTEX, a estrutura Departamento, Categoria e Subcategoria não é pré-definida. Ela varia de acordo com a estrutura da sua loja, não sendo obrigatória a criação desses 3 níveis hierárquicos.
-</div>
+>ℹ️ Na plataforma VTEX, a estrutura Departamento, Categoria e Subcategoria não é pré-definida. Ela varia de acordo com a estrutura da sua loja, não sendo obrigatória a criação desses 3 níveis hierárquicos.
 
 O cadastro de uma categoria acontece no __Catálogo__, no Admin VTEX.
 
diff --git a/docs/tutorials/pt/registering-a-products-base-price.md b/docs/tutorials/pt/registering-a-products-base-price.md
index 0a3a90d02..f29ee4b21 100644
--- a/docs/tutorials/pt/registering-a-products-base-price.md
+++ b/docs/tutorials/pt/registering-a-products-base-price.md
@@ -15,9 +15,7 @@ legacySlug: cadastrar-o-preco-base-de-um-produto
 subcategory: 4id9W3RDyw02CasOm2C2iy
 ---
 
-<div class="alert alert-info">
-Este artigo se refere à versão mais recente do Pricing da VTEX. Caso a sua loja ainda não esteja nesta nova versão, você pode solicitar a migração entrando em contato com o nosso time de atendimento.
-</div>
+>ℹ️ Este artigo se refere à versão mais recente do Pricing da VTEX. Caso a sua loja ainda não esteja nesta nova versão, você pode solicitar a migração entrando em contato com o nosso time de atendimento.
 
 O __preço base__ é o preço básico de venda de um produto. Ele é composto pelo __preço de custo__ mais o __markup__ desejado na venda do produto.
 
@@ -29,9 +27,7 @@ Para configurar o preço base, siga os passos abaixo:
 - No campo __Markup__, preencha com o percentual da margem de lucro a ser obtida com a venda do SKU.
 - O preço base de venda será calculado em função dos dados fornecidos nos passos anteriores.
 
-<div class="alert alert-info">
-Caso o SKU possua algum preço de lista, você pode acrescentar esta informação clicando em <strong>+ Adicionar Preço de Lista</strong>. Este preço funciona como o "preço de". O preço base funcionará como o "preço por".
-</div>
+>ℹ️ Caso o SKU possua algum preço de lista, você pode acrescentar esta informação clicando em **+ Adicionar Preço de Lista**. Este preço funciona como o "preço de". O preço base funcionará como o "preço por".
 
 ## Artigos relacionados
 
diff --git a/docs/tutorials/pt/registering-geolocation.md b/docs/tutorials/pt/registering-geolocation.md
index 1549ec0ee..685dc7cd5 100644
--- a/docs/tutorials/pt/registering-geolocation.md
+++ b/docs/tutorials/pt/registering-geolocation.md
@@ -32,9 +32,7 @@ Acessando o link [Gere seus polígonos com geojson.io](http://geojson.io/#map=2/
 
 Esse JSON será usado para adicionar o polígono na plataforma, que entenderá a partir dessa linguagem quais códigos postais estão inclusos nessa área.
 
-<div class="alert alert-danger">
-Na configuração de um polígono, não é possível delimitar áreas sobrepostas, ou seja, não é possível sobrepor coordenadas geográficas.
-</div>
+>❗ Na configuração de um polígono, não é possível delimitar áreas sobrepostas, ou seja, não é possível sobrepor coordenadas geográficas.
 
 ### Como adicionar um polígono
 
@@ -60,8 +58,7 @@ Exemplo:
 
 Pronto, agora é só usar esse mesmo ID para preencher a coluna **PolygonName** da [planilha de frete](http://help.vtex.com/tutorial/como-montar-a-planilha-de-frete/).
 
-<div class="alert alert-warning">É importante atentar para o fato de que, no caso de você usar geolocalização, preenchendo portanto a coluna <b>PolygonName</b> da planilha de frete, a transportadora em questão não usará as colunas <b>ZipCodeStart</b> e <b>ZipCodeEnd</b>, que deverão ser preenchidas com 0.
-</div>
+>⚠️ É importante atentar para o fato de que, no caso de você usar geolocalização, preenchendo portanto a coluna **PolygonName** da planilha de frete, a transportadora em questão não usará as colunas **ZipCodeStart** e **ZipCodeEnd**, que deverão ser preenchidas com 0.
 
    Lembre-se também que para que a geolocalização funcione, deve estar preenchido o campo API Key em **Configurações da loja > Storefront > Checkout**, [na aba Checkout](https://help.vtex.com/pt/tutorial/geolocalizacao-no-checkout/), com a mesma chave que utilizou para habilitar a geolocalização.
 
@@ -86,6 +83,4 @@ Caso precise alterar algum local de entrega de um polígono já existente, é p
 
 Depois disso, não será necessário alterar nenhuma informação na planilha de frete, visto que o ID do polígono continua o mesmo, e é por meio dele que o sistema faz a consulta.
 
-<div class="alert alert-warning">
-  Caso a transportadora e planilha de frete tenham sido criadas antes de cadastrar o Polígono, recomendamos que seja editada a transportadora que tem vínculo com esse Polígono, para atualizar o relacionamento. Com isso após a Criação ou Alteração de um Poligono, abra a transportadora e clique em Salvar, somente para sensibilizar uma atualização.
-</div>
+>⚠️ Caso a transportadora e planilha de frete tenham sido criadas antes de cadastrar o Polígono, recomendamos que seja editada a transportadora que tem vínculo com esse Polígono, para atualizar o relacionamento. Com isso após a Criação ou Alteração de um Poligono, abra a transportadora e clique em Salvar, somente para sensibilizar uma atualização.
diff --git a/docs/tutorials/pt/registering-holidays.md b/docs/tutorials/pt/registering-holidays.md
index 80eda9edd..9b2d59897 100644
--- a/docs/tutorials/pt/registering-holidays.md
+++ b/docs/tutorials/pt/registering-holidays.md
@@ -34,9 +34,7 @@ A funcionalidade **Feriados** será considerada para transportadoras com a confi
 3. Na seção **Finais de semana e feriados**, certifique-se que a opção `Entrega em feriados` está com o switch desativado <i class="fas fa-toggle-off"></i>. 
 4. Clique em `Salvar`.
 
-<div class="alert alert-info">
-Você pode definir feriados para os anos seguintes.
-</div>
+>ℹ️ Você pode definir feriados para os anos seguintes.
 
 ## Como é feito o cálculo do envio com feriados
 
@@ -57,9 +55,7 @@ Do ponto de vista técnico, os feriados são considerados na variável `shipping
 2. Existe um feriado cadastrado na terça-feira (06/02).
 3. A data estimada para o cliente receber o pedido será quinta-feira (08/02), pois o feriado de terça-feira não é considerado dia útil.
 
-<div class="alert alert-warning">
-Existe uma exceção na qual o feriado cadastrado conta como dia útil: quando o cliente realiza um pedido em um feriado e a transportadora tem horário de despacho configurado (<a href="https://help.vtex.com/pt/tutorial/carrier-working-hours--2oGpbInIgdxSWUi3TZjdCS">Período de Envio</a>) para esse mesmo dia.
-</div>
+>⚠️ Existe uma exceção na qual o feriado cadastrado conta como dia útil: quando o cliente realiza um pedido em um feriado e a transportadora tem horário de despacho configurado ([Período de Envio](https://help.vtex.com/pt/tutorial/carrier-working-hours--2oGpbInIgdxSWUi3TZjdCS)) para esse mesmo dia.
 
 ### Exemplo 2
 
diff --git a/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md b/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
index a3dbaa3be..f304075ed 100644
--- a/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
+++ b/docs/tutorials/pt/regular-promotion-with-nominal-discount-based-on-formula.md
@@ -48,17 +48,13 @@ Você pode fazer uma operação de multiplicação para calcular o percentual de
 
 Para priorizar um cálculo antes de outro, escreva o cálculo que deve ser realizado antes entre parênteses `()`. Exemplo: se uma loja quer aplicar o desconto de 40% sobre o valor total somado ao frete, a fórmula deve ser `(total + freight) * 0.4`.
 
-<div class="alert alert-info">
-  <p>Use sempre o ponto (<code>.</code>) como separador decimal.</p>
-</div>
+>ℹ️ Use sempre o ponto (`.`) como separador decimal.
 
 ## Funções
 
 Se desejar, você pode usar a função `min` para [limitar o valor do desconto](#limitar-o-valor-do-desconto) ou a função `max` para [priorizar o maior desconto possível](#priorizar-o-maior-desconto-possivel). Continue a leitura para mais detalhes sobre essas possibilidades.
 
-<div class="alert alert-info">
-<p>Ao utilizar funções, é necessário incluir um espaço entre a função e os parênteses de abertura. Exemplo: <code>min (total * 0.2, 10)</code>.</p>
-</div>
+>ℹ️ Ao utilizar funções, é necessário incluir um espaço entre a função e os parênteses de abertura. Exemplo: `min (total * 0.2, 10)`.
 
 ### Limitar o valor do desconto
 
diff --git a/docs/tutorials/pt/releases-module-beta.md b/docs/tutorials/pt/releases-module-beta.md
index 2ea1b2b1d..135a34c11 100644
--- a/docs/tutorials/pt/releases-module-beta.md
+++ b/docs/tutorials/pt/releases-module-beta.md
@@ -15,9 +15,7 @@ legacySlug: modulo-lancamentos-beta
 subcategory: 
 ---
 
-<div class="alert alert-info">
-O módulo <b>Lançamentos</b> está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam FastStore.
-</div>
+>ℹ️ O módulo **Lançamentos** está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam FastStore.
 
 O gerenciamento de uma operação de ecommerce requer que o lojista faça uma série de atualizações e modificações na sua loja, que muitas vezes estão relacionadas entre si. Um exemplo é a realização de uma campanha publicitária, em que diferentes elementos do storefront precisam ser configurados.
 
@@ -190,9 +188,7 @@ Outra forma de publicar é entrando na página de detalhes do lançamento, confo
 
 Siga o passo a passo abaixo para excluir um lançamento:
 
-<div class="alert alert-danger">
-Lançamentos excluídos são deletados e não podem ser recuperados. As atualizações que faziam parte do lançamento são mantidas, mas o agrupamento entre elas deixa de existir.
-</div>
+>❗ Lançamentos excluídos são deletados e não podem ser recuperados. As atualizações que faziam parte do lançamento são mantidas, mas o agrupamento entre elas deixa de existir.
 
 1. No Admin VTEX, acesse **Configurações da loja > Lançamentos.**
   > Se sua loja utiliza o Redesigned VTEX Admin, acesse **Storefront > Lançamentos**.
diff --git a/docs/tutorials/pt/releases-overview.md b/docs/tutorials/pt/releases-overview.md
index 5e7075c92..eb7de7532 100644
--- a/docs/tutorials/pt/releases-overview.md
+++ b/docs/tutorials/pt/releases-overview.md
@@ -15,15 +15,11 @@ legacySlug: visao-geral-lancamentos
 subcategory: 3vXj7HrnYK8V5riTOwUuYv
 ---
 
-<div class="alert alert-info">
-  <p>O <strong>Lançamentos</strong> está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam <a href="https://www.faststore.dev/">FastStore</a>.</p>
-</div>
+>ℹ️ O **Lançamentos** está em fase beta, o que significa que estamos trabalhando para aprimorá-lo. Esta funcionalidade é válida somente para lojas que usam [FastStore](https://www.faststore.dev/).
 
 O menu **Lançamentos** permite que você gerencie grupos de modificações relacionadas, de forma a coordenar o planejamento, criação, agendamento e publicação de alterações na sua loja. Uma modificação ou um agrupamento de modificações que podem ser publicadas de forma conjunta pelo **Lançamentos** são chamadas de [lançamento](https://help.vtex.com/pt/tutorial/planner-conceito-de-lancamento-beta--4pWhQTXG0aIIsi2TYxxRkZ).
 
-<div class="alert alert-warning">
-  <p>Na fase beta, os lançamentos precisam estar relacionados ao <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS</a>, pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o <strong>Lançamentos</strong>, é necessário configurar o CMS conforme descrito em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.</p>
-</div>
+>⚠️ Na fase beta, os lançamentos precisam estar relacionados ao [CMS](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), pois outros módulos da plataforma VTEX ainda não estão inclusos. Para utilizar o **Lançamentos**, é necessário configurar o CMS conforme descrito em [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 Confira a seguir quais são as páginas contidas no menu **Lançamentos**.
 
diff --git a/docs/tutorials/pt/relevance-rules.md b/docs/tutorials/pt/relevance-rules.md
index 3068fd888..4e2429352 100644
--- a/docs/tutorials/pt/relevance-rules.md
+++ b/docs/tutorials/pt/relevance-rules.md
@@ -39,9 +39,7 @@ As informações aplicadas para compor a relevância são:
 
 O conjunto de distribuição de pesos e critérios gera uma pontuação para o produto, o que auxilia no seu posicionamento na ordenação do resultado da pesquisa.
 
-<div class="alert alert-warning">
-  <p>Caso deseje utilizar critérios prioritários, recomendamos adicionar apenas um critério neste campo. Adicionar mais critérios compromete a ordenação do resultado de busca, visto que apenas o primeiro critério será considerado.</p>
-</div>
+>⚠️ Caso deseje utilizar critérios prioritários, recomendamos adicionar apenas um critério neste campo. Adicionar mais critérios compromete a ordenação do resultado de busca, visto que apenas o primeiro critério será considerado.
 
 Dessa forma, é possível adequar o comportamento do resultado de busca a uma estratégia específica.
 
diff --git a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
index de152f8bb..f54a77ceb 100644
--- a/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
+++ b/docs/tutorials/pt/removing-error-message-request-headers-must-only-contain-ascii.md
@@ -85,7 +85,5 @@ Se desejar, você também pode incluir no script as seguintes funções:
 - Expirar automaticamente os cookies contendo caracteres especiais
 - Acionar o recarregamento da página por meio da função `window.location.reload()`  
 
-<div class="alert alert-warning">
-  A remoção dos cookies via script não é uma solução definitiva. Conforme descrito na seção <b>Desabilitando cookies com caracteres especiais</b>, é necessário identificar a origem e interromper o processo de envio de cookies com caracteres especiais.
-</div>  
+>⚠️ A remoção dos cookies via script não é uma solução definitiva. Conforme descrito na seção **Desabilitando cookies com caracteres especiais**, é necessário identificar a origem e interromper o processo de envio de cookies com caracteres especiais.  
 
diff --git a/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md b/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
index 95ce972fa..23a529f86 100644
--- a/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
+++ b/docs/tutorials/pt/responsibilities-in-the-vtex-ecosystem.md
@@ -178,9 +178,7 @@ Ainda assim, podem existir lojas parceiras estratégicas para o seu negócio que
 
 Para o suporte de uma operação nesse cenário, é importante que o lojista entenda quais as responsabilidades de cada participante dessa operação, detalhadas a seguir.
 
-<div class="alert alert-warning">
-  <p>As seções a seguir consideram uma loja que já está operando integrada com um marketplace externo via conector externo. Para saber como integrar o seu Catálogo da VTEX com um conector externo pela primeira vez, acesse o guia <a href="https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word">Catalog Integration</a>.</p>
-</div>
+>⚠️ As seções a seguir consideram uma loja que já está operando integrada com um marketplace externo via conector externo. Para saber como integrar o seu Catálogo da VTEX com um conector externo pela primeira vez, acesse o guia [Catalog Integration](https://developers.vtex.com/docs/guides/external-marketplace-integration-catalog" class="t-body mv5 lh-copy c-link active-c-link hover-c-link visited-c-link hover-c-link break-word).
 
 ### Atualização ou envio de novos produtos e SKUs
 
diff --git a/docs/tutorials/pt/returning-order-items.md b/docs/tutorials/pt/returning-order-items.md
index 45b7140ba..eaf7a3a23 100644
--- a/docs/tutorials/pt/returning-order-items.md
+++ b/docs/tutorials/pt/returning-order-items.md
@@ -35,12 +35,13 @@ Para realizar a devolução pelo Admin VTEX, realize os seguintes passos:
 
 ![Devolução de itens de um pedido](https://drive.google.com/uc?export=download&id=1o0QkZZpgn7nXD5LVENxmlp9e_PKTGDva)
 
-<div class="alert alert-warning">
-Note que:
-<ul>
-<li>A devolução de um SKU no <b>Gerenciamento de pedidos</b> não atualiza a quantidade de SKUs que estão disponíveis no inventário. A loja deve atualizar a quantidade de itens no <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">inventário</a>.</li>
-<li>O número da nota fiscal de devolução deve ser diferente da nota fiscal de venda.</li>
-<li>Após a devolução, o sistema de pagamentos é notificado para a realização do <a href="https://help.vtex.com/pt/tutorial/como-funciona-estorno-quando-ha-devolucao-do-item">estorno</a>.</li>
-<li>Só é possível realizar a devolução de pedidos que têm pelo menos uma nota fiscal inserida na plataforma.</li>
-</ul>
-</div>
+>⚠️ Note que:
+>
+> *A devolução de um SKU no **Gerenciamento de pedidos** não atualiza a quantidade de SKUs que estão disponíveis no inventário. A loja deve atualizar a quantidade de itens no [inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
+>
+> *O número da nota fiscal de devolução deve ser diferente da nota fiscal de venda.
+>
+> *Após a devolução, o sistema de pagamentos é notificado para a realização do [estorno](https://help.vtex.com/pt/tutorial/como-funciona-estorno-quando-ha-devolucao-do-item).
+>
+> *Só é possível realizar a devolução de pedidos que têm pelo menos uma nota fiscal inserida na plataforma.
+> 
diff --git a/docs/tutorials/pt/risk-assessment.md b/docs/tutorials/pt/risk-assessment.md
index 5f98530f3..11da4a1f8 100644
--- a/docs/tutorials/pt/risk-assessment.md
+++ b/docs/tutorials/pt/risk-assessment.md
@@ -45,9 +45,7 @@ Algumas informações sobre segurança são restritas a usuários logados no Adm
 
 <iframe src="https://help.vtex.com/insertaccountname?id=7AmPOGXykmE9SYyYDzdAZ4" title="Insira seu nome de conta e clique no botão." frameBorder="0" width="400" height="50"></iframe>
 
-<div class="alert alert-warning">
-  Se está tendo dificuldades para acessar o conteúdo dos FAQs, tente instalar a versão mais recente do aplicativo <code>vtex.admin-docs</code> usando a <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">CLI da VTEX</a> e repetir o processo.
-</div>
+>⚠️ Se está tendo dificuldades para acessar o conteúdo dos FAQs, tente instalar a versão mais recente do aplicativo `vtex.admin-docs` usando a [CLI da VTEX](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) e repetir o processo.
 
 ## FAQ - Segurança
 
diff --git a/docs/tutorials/pt/roles.md b/docs/tutorials/pt/roles.md
index 23290533a..ff4e3610a 100644
--- a/docs/tutorials/pt/roles.md
+++ b/docs/tutorials/pt/roles.md
@@ -38,9 +38,7 @@ A página apresenta uma lista com todos os perfis de acesso cadastrados na conta
 
 Em uma conta recém-criada, apenas o perfil *Owner (Admin Super)* estará listado. Este perfil dá ao usuário acesso irrestrito a todos os recursos nativos da plataforma.
 
-<div class="alert alert-warning">
-  <p>A quantidade de usuários com o perfil <em>Owner (Admin Super)</em> deve ser a menor possível. Além disso, é preciso se certificar que haja visibilidade e controle de quem recebe esse acesso.</p>
-</div>
+>⚠️ A quantidade de usuários com o perfil *Owner (Admin Super)* deve ser a menor possível. Além disso, é preciso se certificar que haja visibilidade e controle de quem recebe esse acesso.
 
 ## Criar um perfil de acesso
 
@@ -58,9 +56,7 @@ Você pode editar os recursos e usuários relacionados a um perfil de acesso. Pa
 
 Para deletar um perfil de acesso, clique em `⫶` na linha do perfil de acesso que deseja excluir e, em seguida, em <i class="far fa-trash-alt"></i> `Excluir`.
 
-<div class="alert alert-warning">
-  <p>Ao excluir um perfil de acesso, usuários associados a ele perderão acesso aos <a href="https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3">recursos do License Manager</a> relacionados ao perfil excluído, a não ser que tenham outros perfis de acesso com as mesmas permissões.</p>
-</div>
+>⚠️ Ao excluir um perfil de acesso, usuários associados a ele perderão acesso aos [recursos do License Manager](https://help.vtex.com/pt/tutorial/recursos-do-license-manager--3q6ztrC8YynQf6rdc6euk3) relacionados ao perfil excluído, a não ser que tenham outros perfis de acesso com as mesmas permissões.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/routing-monitoring.md b/docs/tutorials/pt/routing-monitoring.md
index fa3eb9c08..3f8c86ef2 100644
--- a/docs/tutorials/pt/routing-monitoring.md
+++ b/docs/tutorials/pt/routing-monitoring.md
@@ -27,9 +27,7 @@ No monitoramento de rotas é possível acompanhar o andamento de uma rota, inclu
 *   Alterar manualmente o status das entregas.
 *   Retirar o canhoto de informações da rota.
 
-<div class="alert alert-info"> 
-As atualizações dos dados entre os sistemas VTEX Tracking acontecem de forma automática. O tempo de atualização e sincronização das informações podem ser configurados na plataforma. No entanto, para visualizar na plataforma web as mudanças ocorridas, é preciso que você atualize a página de Monitoramento de Rotas. Para saber mais sobre as configurações de conta confira <a href="https://help.vtex.com/pt/subcategory/vtex-tracking--7yiFRk9TGfMNeyhT83UljP">Configurações de conta</a>.
-</div>
+>ℹ️ As atualizações dos dados entre os sistemas VTEX Tracking acontecem de forma automática. O tempo de atualização e sincronização das informações podem ser configurados na plataforma. No entanto, para visualizar na plataforma web as mudanças ocorridas, é preciso que você atualize a página de Monitoramento de Rotas. Para saber mais sobre as configurações de conta confira [Configurações de conta](https://help.vtex.com/pt/subcategory/vtex-tracking--7yiFRk9TGfMNeyhT83UljP).
 
 A tela de monitoramento de rotas é acessada através do menu **Monitoramento** > **Rotas**. Nela, você encontra uma lista das rotas e rotas itinerantes (rotas cujo período de realização ultrapassa um dia). 
 
@@ -75,8 +73,6 @@ Caso precise mudar o status, ao final da página [Detalhes da rota](#detalhes-da
 3. É possível editar ainda a **Ocorrência** e **Justificativa** caso queira.
 4. Depois de selecionar as opções desejadas clique em **Confirmar.**
 
-<div class="alert alert-info"> 
-Para que esteja disponível uma Justificativa ela deve ser cadastrada previamente na aba de Configurações de Conta. Para saber mais confira <a href="https://help.vtex.com/pt/tutorial/justificativa-de-status-vtex-tracking--4shboc7h5XPUpA8TQzXPRG">Justificativa de status</a>.
-</div>
+>ℹ️ Para que esteja disponível uma Justificativa ela deve ser cadastrada previamente na aba de Configurações de Conta. Para saber mais confira [Justificativa de status](https://help.vtex.com/pt/tutorial/justificativa-de-status-vtex-tracking--4shboc7h5XPUpA8TQzXPRG).
 
 ![Monitoramento de Rota](https://images.ctfassets.net/alneenqid6w5/3cHz27dvHjO7ObLDxJTIuc/01103e99a288ab15935a7b453487fd7c/Monitoramento_Rota.gif)
diff --git a/docs/tutorials/pt/sales-associate-code-field-at-checkout.md b/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
index cd89bf90e..49c464755 100644
--- a/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
+++ b/docs/tutorials/pt/sales-associate-code-field-at-checkout.md
@@ -20,9 +20,7 @@ Na VTEX, você pode criar um campo para registrar o código de vendedor no Check
 - Oferecer descontos exclusivos ao consumidor.
 - Administrar a performance de seus vendedores, extraindo dados como número de vendas / ticket médio por vendedor, ranking para comissionamento de vendas, entre outros.
 
-<div class="alert alert-warning">
-  O campo <b>código de vendedor</b> não substitui o campo <b>cupom de desconto</b> (nativo na plataforma VTEX). Ao realizar as configurações deste artigo, ambos poderão ser utilizados para oferecer descontos.
-</div>
+>⚠️ O campo **código de vendedor** não substitui o campo **cupom de desconto** (nativo na plataforma VTEX). Ao realizar as configurações deste artigo, ambos poderão ser utilizados para oferecer descontos.
 
 Para criar o campo e inseri-lo na tela do Checkout de sua loja, três etapas são necessárias:
 
@@ -55,9 +53,7 @@ Após a criação da entidade *codigovendedor*, é necessário associá-la a uma
 1. No Admin VTEX, acesse **Promoções > Promoções**, ou digite **Promoções** na barra de busca no topo da página.
 2. Crie uma nova [promoção regular](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI). Preencha as informações de **Dados gerais de promoção** e **A quais itens esta promoção será aplicada?** conforme desejado.
 
-<div class="alert alert-info">
-  Caso deseje utilizar o campo código de vendedor para oferecer desconto no valor da compra, preencha as informações em <b>Tipo e valor de de desconto?</b>.
-</div>
+>ℹ️ Caso deseje utilizar o campo código de vendedor para oferecer desconto no valor da compra, preencha as informações em **Tipo e valor de de desconto?**.
 
 <blockquote><ui>3. Em <b>Quais as condições para a promoção ser válida?</b>, clique na opção <b>utm_campaign</b> e digite no campo <i>codigovendedor</i>.</ui>
 
@@ -77,9 +73,7 @@ Adicionalmente, os seguintes passos devem ser realizados:
 
 1. Ao simular uma compra e inserir o código do vendedor na tela do Checkout, certifique-se que a chamada GET [Search Documents](https://developers.vtex.com/docs/api-reference/master-data-api-v2#get-/api/dataentities/-dataEntityName-/search) realize a busca na entidade `codigovendedor` e retorne todas as informações cadastradas do vendedor. Exemplo de chamada: https://{accountName}.{environment}.com.br/api/dataentities/codigovendedor/search?codigovendedor=12345.
 
-<div class="alert alert-warning">
-  O campo <b>status</b> deve retornar o valor <b>true</b>, indicando que o código do vendedor é válido.
-</div>
+>⚠️ O campo **status** deve retornar o valor **true**, indicando que o código do vendedor é válido.
 
 <blockquote><ui>2. Efetue a chamada POST <a href="https://developers.vtex.com/docs/api-reference/checkout-api#post-/api/checkout/pvt/configuration/orderForm">Update orderForm configuration</a> para incluir as seguintes informações no <a href="https://developers.vtex.com/docs/guides/orderform-fields">orderForm</a> de sua loja</ui>:
 
@@ -87,9 +81,7 @@ Adicionalmente, os seguintes passos devem ser realizados:
 
 <blockquote><blockquote>- <b>openTextField</b> (opcional): inserir observações ou comentários (ex. informações para filtros de comissionamento).
 
-<div class="alert alert-warning">
-  Somente a informação do nome do vendedor deve ser exibida na tela do Checkout.
-</div>
+>⚠️ Somente a informação do nome do vendedor deve ser exibida na tela do Checkout.
 
 Após executar todas as etapas acima descritas, o campo **Código do Vendedor** estará disponível na tela do Checkout.
 
diff --git a/docs/tutorials/pt/sales-performance.md b/docs/tutorials/pt/sales-performance.md
index 28f5e15ec..9a2a78cf3 100644
--- a/docs/tutorials/pt/sales-performance.md
+++ b/docs/tutorials/pt/sales-performance.md
@@ -212,9 +212,7 @@ A lista representa as métricas e filtros aplicados no gráfico em formato de ta
   - __Absoluto:__ visualize em números absolutos o aumento ou diminuição das métricas da lista, entre um período e outro. 
   - __Representativo:__ visualize o percentual de representatividade de um item dentro de uma métrica.
 
-<div class="alert alert-info">
-Note que as métricas <em>Ticket médio</em> e <em>Itens por pedido</em> não terão visualização Percentual ou Representativa disponíveis, já que são métricas calculadas dividindo outras, e a soma de todas as partes de cada uma não é igual ao Total.
-</div>
+>ℹ️ Note que as métricas *Ticket médio* e *Itens por pedido* não terão visualização Percentual ou Representativa disponíveis, já que são métricas calculadas dividindo outras, e a soma de todas as partes de cada uma não é igual ao Total.
 
 ### Exportar dados
 
diff --git a/docs/tutorials/pt/scheduled-delivery.md b/docs/tutorials/pt/scheduled-delivery.md
index 6e1463d56..e56daf887 100644
--- a/docs/tutorials/pt/scheduled-delivery.md
+++ b/docs/tutorials/pt/scheduled-delivery.md
@@ -21,9 +21,9 @@ Os períodos de entrega que ficam disponíveis para os consumidores são chamado
 
 Caso a política de envio ofereça o serviço, você pode habilitar a entrega agendada configurando as janelas de entrega e definindo a capacidade de realização das entregas para cada janela de entrega, caso desejar.A habilitação da entrega agendada é feita através do campo __Entrega Agendada__ presente na tela de criação ou edição de Política de Envio. 
 
-<div class="alert alert-warning">
-Para que a <a href="https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi">Entrega agendada</a> e a <a href="https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz">Capacidade de entrega</a> funcionem corretamente, você deve observar que:<p><ul><li>A soma {<a href="https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC">account name</a>} + {ID da política de envio} não pode exceder 60 caracteres.</li><li>Não se deve utilizar espaçamento no ID de <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">políticas de envio</a>.</li></ul></p>
-</div>
+>⚠️ Para que a [Entrega agendada](https://help.vtex.com/pt/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi) e a [Capacidade de entrega](https://help.vtex.com/pt/tutorial/managing-delivery-capacity--2y217FQZCjD0I1n62yxVcz) funcionem corretamente, você deve observar que:
+> *A soma {[account name](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC)} + {ID da política de envio} não pode exceder 60 caracteres.
+> * Não se deve utilizar espaçamento no ID de [políticas de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 Uma vez habilitada a Entrega Agendada, você pode configurar os campos que determinarão como ela funcionará. Tais campos definem o [tempo máximo de entrega](#tempo-maximo-de-entrega), o [período de entrega](#periodo-de-entrega) e o [limite da capacidade de entrega](#capacidade-de-entrega).
 
@@ -37,9 +37,7 @@ O tempo máximo de entrega é o maior período de tempo que a política de envio
 
 O período de entrega, também chamado de janela de entrega, se refere aos horários nos quais a transportadora está disponível para realizar entregas durante o dia. Nos períodos/janelas são definidos horários de início e fim do funcionamento por dia da semana no qual você pode ainda, definir um valor de frete adicional a ser cobrado para dias da semana específicos, como por exemplo, sábados.
 
-<div class="alert alert-info"> 
-Uma janela de entrega deixa de estar disponível para seleção após ter sido iniciada. Apenas janelas de entrega próximas (ainda não iniciadas) ficarão disponíveis para os clientes.
-</div>
+>ℹ️ Uma janela de entrega deixa de estar disponível para seleção após ter sido iniciada. Apenas janelas de entrega próximas (ainda não iniciadas) ficarão disponíveis para os clientes.
 
 ## Capacidade de Entrega
 
@@ -47,9 +45,7 @@ Definir capacidade de entrega é a forma que você tem em limitar a quantidade d
 
 Quando o cliente finaliza a compra e seleciona a entrega agendada, as opções de data e hora apresentadas levam em consideração a capacidade de entrega. Invariavelmente, o cliente só conseguirá agendar entregas nas janelas que ainda tiverem disponibilidade de 1 item/pedido. 
 
-<div class="alert alert-info"> 
-Se a janela já tiver a capacidade total de itens/pedidos, ela deixa de estar disponível para escolha. Para deixar novamente a janela disponível você deve aumentar os itens/pedidos da capacidade de entrega. Isso pode ser feito editando uma <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de envio</a>.
-</div>
+>ℹ️ Se a janela já tiver a capacidade total de itens/pedidos, ela deixa de estar disponível para escolha. Para deixar novamente a janela disponível você deve aumentar os itens/pedidos da capacidade de entrega. Isso pode ser feito editando uma [Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 
 Leia o artigo [Gerenciar capacidade de entrega](https://help.vtex.com/pt/tutorial/gerenciar-capacidade-de-entrega--2y217FQZCjD0I1n62yxVcz) para saber mais.
 
diff --git a/docs/tutorials/pt/scheduling-features-for-special-events.md b/docs/tutorials/pt/scheduling-features-for-special-events.md
index a92fdc752..73ecbd75c 100644
--- a/docs/tutorials/pt/scheduling-features-for-special-events.md
+++ b/docs/tutorials/pt/scheduling-features-for-special-events.md
@@ -59,9 +59,7 @@ Assim como na promoção, o agendamento de taxas é feito durante a sua criaçã
 
 O agendamento de conteúdo pelo Site Editor pode ser feito tanto pela [criação](https://help.vtex.com/pt/tutorial/managing-page-and-template-content--3tMbx6HXy4Fy5r9EhboG37#criando-conteudo) quanto pela [edição](https://help.vtex.com/pt/tutorial/managing-page-and-template-content--3tMbx6HXy4Fy5r9EhboG37#editando-conteudo) de bloco. 
 
-<div class="alert alert-warning">
-  <p>O agendamento de conteúdo está disponível apenas para lojas desenvolvidas usando <a href="https://vtex.com/br-pt/store-framework/">VTEX IO</a>.</p>
-</div>
+>⚠️ O agendamento de conteúdo está disponível apenas para lojas desenvolvidas usando [VTEX IO](https://vtex.com/br-pt/store-framework/).
 
 Para agendar um conteúdo da sua loja, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/scheduling-prices.md b/docs/tutorials/pt/scheduling-prices.md
index b71305793..1a9b581d4 100644
--- a/docs/tutorials/pt/scheduling-prices.md
+++ b/docs/tutorials/pt/scheduling-prices.md
@@ -48,9 +48,7 @@ Para realizar o agendamento pelo Admin, siga os passos abaixo.
 - **Data Fim:** data de fim do agendamento do preço fixo. Será a partir dessa data que o preço fixo não será mais válido.
 - **Hora Fim:** hora de fim do agendamento do preço fixo. Será a partir dessa hora que o preço fixo não será mais válido.
 
-<div class="alert alert-info">
-  <p>No agendamento feito pelo Admin, o fuso-horário considerado será o utilizado pelo computador do usuário.</p>
-</div>
+>ℹ️ No agendamento feito pelo Admin, o fuso-horário considerado será o utilizado pelo computador do usuário.
 
 ## Agendamento por importação de planilha de preços fixos
 
diff --git a/docs/tutorials/pt/scheduling-report.md b/docs/tutorials/pt/scheduling-report.md
index 5397d24dd..dee9b3d65 100644
--- a/docs/tutorials/pt/scheduling-report.md
+++ b/docs/tutorials/pt/scheduling-report.md
@@ -39,6 +39,4 @@ Se você quiser visualizar todos os serviços que foram filtrados de forma mais
 *   Horário que o serviço foi feito.
 *   O turno que o serviço foi feito.
 
-<div class="alert alert-danger"> 
-A plataforma do VTEX Tracking está sofrendo atualizações, por esse motivo  é possível que essa funcionalidade não se comporte como esperado. Aguarde as novas atualizações e usufrua integralmente dessa aba. 
-</div>
+>❗ A plataforma do VTEX Tracking está sofrendo atualizações, por esse motivo  é possível que essa funcionalidade não se comporte como esperado. Aguarde as novas atualizações e usufrua integralmente dessa aba.
diff --git a/docs/tutorials/pt/search-by-geo-coordinates.md b/docs/tutorials/pt/search-by-geo-coordinates.md
index b264c535b..682d8f0f4 100644
--- a/docs/tutorials/pt/search-by-geo-coordinates.md
+++ b/docs/tutorials/pt/search-by-geo-coordinates.md
@@ -15,8 +15,7 @@ legacySlug: busca-por-geocoordenadas
 subcategory: 5tSNDlvmik8gGuKw2goW4q
 ---
 
-<div class="alert alert-warning">
-<strong>Atenção:</strong> Essa funcionalidade está em BETA.</div>
+>⚠️ **Atenção:** Essa funcionalidade está em BETA.
 
 ### Configurando JSON Schema
 
diff --git a/docs/tutorials/pt/search-navigator-control.md b/docs/tutorials/pt/search-navigator-control.md
index c7370d984..5da73ee5b 100644
--- a/docs/tutorials/pt/search-navigator-control.md
+++ b/docs/tutorials/pt/search-navigator-control.md
@@ -21,9 +21,7 @@ subcategory: 2g6LxtasS4iSeGEqeYUuGW
 
 O controle `<vtex.cmc:searchNavigator/>` renderiza um menu de filtros relacionados ao resultado de uma busca.
 
-<div class="alert alert-info">
-Esse controle funciona <b>apenas em páginas com contexto de busca</b>, ou seja, páginas onde os resultados exibidos foram trazidos por uma busca do usuário.
-</div>
+>ℹ️ Esse controle funciona **apenas em páginas com contexto de busca**, ou seja, páginas onde os resultados exibidos foram trazidos por uma busca do usuário.
 
 Quando o usuário faz uma busca na loja, o sistema da VTEX tenta trazer resultados de acordo com uma ordem de prioridade de filtros. [Entenda como funciona a busca aqui.](/pt/tutorial/como-funciona-a-busca-da-vtex)
 
@@ -54,10 +52,8 @@ Essa flag fica na tela de cadastro da categoria.
 
 ![searchNavigator1](https://images.contentful.com/alneenqid6w5/Q04sSdSPeK4U6Cu48MKkK/198759d6dcdb5d740f0e7b380d8f38cc/searchNavigator1.jpg)
 
-<div class="alert alert-info">
-  <strong>Importante</strong>: O controle <code>&lt;vtex.cmc:searchNavigator/&gt;</code> exibe, por padrão, apenas a categoria raiz (primeiro nível) e a subcategoria mais específica (último nível) dentro do contexto atual. Desdobramentos intermediários da árvore de categorias são omitidos.
-  Além disso, o controle só funciona nos três primeiros níveis, que são tradicionalmente Departamento, Categoria e Subcategoria. Caso sua <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">arquitetura de catálogo</a> contenha subdivisões além do 3º nível, estas não serão exibidas usando o controle nativo.
-</div>
+>ℹ️ **Importante**: O controle `&lt;vtex.cmc:searchNavigator/&gt;` exibe, por padrão, apenas a categoria raiz (primeiro nível) e a subcategoria mais específica (último nível) dentro do contexto atual. Desdobramentos intermediários da árvore de categorias são omitidos.
+>   Além disso, o controle só funciona nos três primeiros níveis, que são tradicionalmente Departamento, Categoria e Subcategoria. Caso sua [arquitetura de catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR) contenha subdivisões além do 3º nível, estas não serão exibidas usando o controle nativo.
 
 ## Marcas
 
@@ -67,9 +63,7 @@ A página de cadastro de marca não tem uma flag de exibição no menu renderiza
 
 Então, por padrão, marcas sempre são exibidas.
 
-<div class="alert alert-warning">
-No entanto, em páginas de departamento ou categoria, as marcas somente serão exibidas pelo controle Search Navigator se, no cadastro da categoria, a flag <b>Filtro de Marca</b> estiver marcada.
-</div>
+>⚠️ No entanto, em páginas de departamento ou categoria, as marcas somente serão exibidas pelo controle Search Navigator se, no cadastro da categoria, a flag **Filtro de Marca** estiver marcada.
 
 ### Em outras páginas:
 
@@ -95,6 +89,12 @@ Por serem filtros cadastrados nas categorias, as faixas de preço somente são e
 
 ---
 
-<div class="alert alert-info">
-Os filtros <strong>sempre</strong> são renderizados com base nos atributos dos produtos do contexto de busca. Ou seja, com base na categoria, especificação (cor, tamanho), marca, coleção etc.<br><br>Portanto, além das condições listadas acima para que esses atributos apareçam como filtros no menu, é necessário antes de mais nada que o termo buscado retorne um contexto com produtos que tenham esses atributos.<br><br>Se o usuário fizer, por exemplo, uma busca por "celular" e a categoria Camisas não contiver nenhum celular, ela não será exibida no menu, ainda que no cadastro dessa categoria a flag de exibição esteja marcada.
-</div>
+>ℹ️ Os filtros **sempre** são renderizados com base nos atributos dos produtos do contexto de busca. Ou seja, com base na categoria, especificação (cor, tamanho), marca, coleção etc.
+>
+> 
+>
+> Portanto, além das condições listadas acima para que esses atributos apareçam como filtros no menu, é necessário antes de mais nada que o termo buscado retorne um contexto com produtos que tenham esses atributos.
+>
+> 
+>
+> Se o usuário fizer, por exemplo, uma busca por "celular" e a categoria Camisas não contiver nenhum celular, ela não será exibida no menu, ainda que no cadastro dessa categoria a flag de exibição esteja marcada.
diff --git a/docs/tutorials/pt/search-parameters.md b/docs/tutorials/pt/search-parameters.md
index 0ebd0ef5b..97bf6479a 100644
--- a/docs/tutorials/pt/search-parameters.md
+++ b/docs/tutorials/pt/search-parameters.md
@@ -83,9 +83,7 @@ Os parâmetros acima podem ser combinados de diversas formas, porém, vale ressa
 
 ## Padrão 2
 
-<div class="alert alert-info">
-  Para lojas hospedadas no VTEX IO, o padrão 2 é o modelo indicado.
-  </div>
+>ℹ️ Para lojas hospedadas no VTEX IO, o padrão 2 é o modelo indicado.
 
 URL: www.loja.com.br/**\[NomeCategoria\]**/**\[NomeMarca\]**/**\[IdColeção\]**/**\[ValorBuscado\]?map=c,b,productClusterIds,specificationFilter_\[IdCampoProduto/Sku\]**
 
diff --git a/docs/tutorials/pt/searching-for-events-on-audit.md b/docs/tutorials/pt/searching-for-events-on-audit.md
index c216a4bf7..ba42390e9 100644
--- a/docs/tutorials/pt/searching-for-events-on-audit.md
+++ b/docs/tutorials/pt/searching-for-events-on-audit.md
@@ -28,15 +28,11 @@ Para iniciar uma busca no Audit, selecione a guia **Eventos de auditoria**. No m
 
 Usando o botão **Data selecionada** é possível escolher uma data pré-definida para a busca. Para selecionar o exato período onde a busca deve ocorrer, clique no botão **Usar datas personalizadas.**
 
-<div class="alert alert-warning">
-Apenas registros dos últimos 3 meses são armazenados.
-</div>
+>⚠️ Apenas registros dos últimos 3 meses são armazenados.
 
 É possível adicionar mais filtros para realizar a busca de eventos com mais precisão. Para isso, clique no botão **Adicionar Filtro**. No painel que aparece, selecione o parâmetro de filtragem (_Ação_, _Detalhes do Evento_ ou _Autor_) e a qual valor este tópico deve ser comparado. 
 
-<div class="alert alert-info">
-Os resultados da busca correspondem exatamente ao conteúdo escrito no tópico do filtro. Para evitar resultados inesperados, certifique-se de que não foram digitados espaços desnecessários nos termos da busca.
-</div>
+>ℹ️ Os resultados da busca correspondem exatamente ao conteúdo escrito no tópico do filtro. Para evitar resultados inesperados, certifique-se de que não foram digitados espaços desnecessários nos termos da busca.
 
 Note que é possível adicionar mais de um filtro,  inclusive com o mesmo tópico. Neste caso, serão buscados eventos que se igualem a qualquer um dos valores inseridos. 
 
@@ -48,9 +44,7 @@ Após selecionada a aplicação, a data e os demais filtros da busca, clique no
 
 Note que toda busca realizada é salva na aba **Últimas Buscas**. Para refazer uma busca, clique nesse aba, e clique no botão <img src="https://images.ctfassets.net/alneenqid6w5/4gWsOnbLMOUeWh0r5YRDz/9b7148d995c03ca84b39473f266b46a9/refresh.png" width="15"> correspondente à busca que deseja ser refeita.
 
-<div class="alert alert-warning">
-Apenas 50 buscas ficam gravadas neste painel. Se quiser salvar uma busca indefinidamente, realize a mesma e adicione aos favoritos do seu browser.
-</div>
+>⚠️ Apenas 50 buscas ficam gravadas neste painel. Se quiser salvar uma busca indefinidamente, realize a mesma e adicione aos favoritos do seu browser.
 
 <div class = "alert alert-info">
 Confira a <a href="https://help.vtex.com/pt/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista de eventos disponíveis no Audit</a>.
diff --git a/docs/tutorials/pt/searching-for-old-orders.md b/docs/tutorials/pt/searching-for-old-orders.md
index 952c1b381..be549d364 100644
--- a/docs/tutorials/pt/searching-for-old-orders.md
+++ b/docs/tutorials/pt/searching-for-old-orders.md
@@ -25,6 +25,4 @@ Para buscar seus pedidos antigos, siga os passos abaixo:
 6. Escolha uma data/hora inicial e uma data/hora final
 7. Clique no botão __Confirme__
 
-<div class="alert alert-info">
-Lembre-se que a busca por período é <strong>limitada a um intervalo de 6 meses</strong>. Dessa forma, se você deseja, por exemplo, buscar pedidos do ano de 2017, o intervalo de tempo escolhido no <strong>passo 6</strong> deve ser um período de 6 meses. Exemplo: Data Inicial = 01/01/2017 e Data Final = 30/06/2017.
-</div>
+>ℹ️ Lembre-se que a busca por período é **limitada a um intervalo de 6 meses**. Dessa forma, se você deseja, por exemplo, buscar pedidos do ano de 2017, o intervalo de tempo escolhido no **passo 6** deve ser um período de 6 meses. Exemplo: Data Inicial = 01/01/2017 e Data Final = 30/06/2017.
diff --git a/docs/tutorials/pt/searching-for-orders-in-oms.md b/docs/tutorials/pt/searching-for-orders-in-oms.md
index aaac3fb79..9e759ef52 100644
--- a/docs/tutorials/pt/searching-for-orders-in-oms.md
+++ b/docs/tutorials/pt/searching-for-orders-in-oms.md
@@ -15,9 +15,7 @@ legacySlug: como-buscar-o-pedido
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class="alert alert-info">
-<strong>Atenção:</strong> só é possível fazer consultas usando um intervalo de no máximo <b>6 meses</b>.
-</div>
+>ℹ️ **Atenção:** só é possível fazer consultas usando um intervalo de no máximo **6 meses**.
 
 A barra de buscas do Gerenciamento de pedidos permite encontrar os pedidos de várias formas diferentes. Basta digitar o termo desejado e pressionar __Enter__ para verificar os resultados. Ela também pode ser usada em conjunto com os filtros, sempre que você precisar [filtrar pedidos no Gerenciamento de pedidos](/pt/tutorial/como-filtrar-pedidos).
 
diff --git a/docs/tutorials/pt/security-certificate-ssl.md b/docs/tutorials/pt/security-certificate-ssl.md
index 20f8ab94b..59b737697 100644
--- a/docs/tutorials/pt/security-certificate-ssl.md
+++ b/docs/tutorials/pt/security-certificate-ssl.md
@@ -21,6 +21,4 @@ Sempre que você acessa uma página segura, isto é, protegida por um certificad
 
 Não é necessário solicitar a compra do certificado SSL. A VTEX gera um certificado SSL para a sua loja e garante sua renovação automática. O certificado é emitido via Let’s Encrypt e sua criação é responsabilidade da VTEX no [momento do Go-Live da loja](https://help.vtex.com/pt/tutorial/configurando-o-apontamento-de-dns-para-a-vtex--tutorials_4280).
 
-<div class="alert alert-warning">
-<p>Não recomendamos a instalação de outros certificados. No entanto, caso seja necessário, faça a solicitação para o nosso <a href="https://help.vtex.com/pt/support">suporte</a>.</p>
-</div>
+>⚠️ Não recomendamos a instalação de outros certificados. No entanto, caso seja necessário, faça a solicitação para o nosso [suporte](https://help.vtex.com/pt/support).
diff --git a/docs/tutorials/pt/security-monitor.md b/docs/tutorials/pt/security-monitor.md
index 9a25fde79..9c6a381e1 100644
--- a/docs/tutorials/pt/security-monitor.md
+++ b/docs/tutorials/pt/security-monitor.md
@@ -15,9 +15,7 @@ legacySlug: security-monitor
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade faz parte do produto <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ Esta funcionalidade faz parte do produto [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 O Security Monitor é um dashboard que auxilia lojistas a identificarem e gerenciarem riscos potenciais em sua conta em tempo real. A ferramenta identifica e notifica lojistas por email sobre riscos relacionados a configurações e comportamento de usuários administrativos, possibilitando ações preventivas contra vulnerabilidades de segurança.
 
diff --git a/docs/tutorials/pt/seller-creating-an-account-in-the-seller-portal.md b/docs/tutorials/pt/seller-creating-an-account-in-the-seller-portal.md
index b62fd7955..2a34fd9b9 100644
--- a/docs/tutorials/pt/seller-creating-an-account-in-the-seller-portal.md
+++ b/docs/tutorials/pt/seller-creating-an-account-in-the-seller-portal.md
@@ -36,9 +36,7 @@ O processo de criação de conta no Seller Portal começa com o [convite enviado
 - [Criar conta para seller VTEX](#conectar-conta-vtex-no-marketplace): loja hospedada na plataforma VTEX.    
 - [Criar conta para seller externo](#criar-conta-para-seller-externo): loja hospedada em outra plataforma de ecommerce, ou que ainda não está hospedada em nenhuma plataforma.    
 
-<div class="alert alert-info">
-O link de criação de conta enviado para o seller é válido por 7 dias. Uma vez aberto, o seller tem seis horas para completar o formulário de cadastro, sem interrupções. Caso não seja possível concluir o cadastro nesse período, é necessário solicitar ao marketplace que envie o convite novamente.
-</div>
+>ℹ️ O link de criação de conta enviado para o seller é válido por 7 dias. Uma vez aberto, o seller tem seis horas para completar o formulário de cadastro, sem interrupções. Caso não seja possível concluir o cadastro nesse período, é necessário solicitar ao marketplace que envie o convite novamente.
 
 ### Conectar conta VTEX no marketplace
 
diff --git a/docs/tutorials/pt/seller-management.md b/docs/tutorials/pt/seller-management.md
index b64f34448..b7f77776d 100644
--- a/docs/tutorials/pt/seller-management.md
+++ b/docs/tutorials/pt/seller-management.md
@@ -87,9 +87,7 @@ Clicando no botão <i class="fas fa-ellipsis-v"></i> na linha do seller, as segu
 - __Detalhes do seller:__ redireciona para a página de Detalhes do Seller, para visualizar ou editar informações.  
 - __Pedidos:__ redireciona para a página Todos os Pedidos, no OMS da VTEX, já filtrando pelos pedidos daquele seller.  
 
-<div class="alert alert-info">
-  Note que a lista está ordenada por ordem alfabética. Para visualizar os dados de todos os sellers, navegue entre as páginas de resultados, clicando nas setas  <i class="fas fa-angle-left"></i> e  <i class="fas fa-angle-right"></i> ao final da página. Utilize os filtros e a busca para refinar os resultados.
-  </div>
+>ℹ️ Note que a lista está ordenada por ordem alfabética. Para visualizar os dados de todos os sellers, navegue entre as páginas de resultados, clicando nas setas  <i class="fas fa-angle-left"></i> e  <i class="fas fa-angle-right"></i> ao final da página. Utilize os filtros e a busca para refinar os resultados.
 
   ### Seller identificável e não identificável (white label)
 
diff --git a/docs/tutorials/pt/seller-portal-promotions.md b/docs/tutorials/pt/seller-portal-promotions.md
index a118129ed..15d246ad0 100644
--- a/docs/tutorials/pt/seller-portal-promotions.md
+++ b/docs/tutorials/pt/seller-portal-promotions.md
@@ -91,6 +91,4 @@ Para acessar a página **Promoções arquivadas**, clique no ícone <i class="fa
 
 Você poderá desarquivar ou duplicar as promoções arquivadas clicando no ícone <i class="fas fa-ellipsis-v"></i>. 
 
-<div class="alert alert-info">
-  <p>Ao desarquivar uma promoção, seu status mudará para <code>Pausada</code>.</p>
-  </div>
+>ℹ️ Ao desarquivar uma promoção, seu status mudará para `Pausada`.
diff --git a/docs/tutorials/pt/seller-portal-shared-products.md b/docs/tutorials/pt/seller-portal-shared-products.md
index 5348cfe44..83f26e721 100644
--- a/docs/tutorials/pt/seller-portal-shared-products.md
+++ b/docs/tutorials/pt/seller-portal-shared-products.md
@@ -16,7 +16,7 @@ subcategory: 4hisB47iAVZk4r3SEmMoG
 ---
 
 
-<div class="alert alert-warning"> O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso<a href="https://support.vtex.com/hc/pt-br/requests">Suporte.</div>
+>⚠️ O limite para cada conta do Seller Portal é de 100 mil produtos. Para mais informações, entre em contato com nosso<a href="https://support.vtex.com/hc/pt-br/requests">Suporte.
 
 **Produtos Compartilhados** é o módulo onde você gerencia os produtos em comum entre seu catálogo e o que já é ofertado no marketplace. O painel de produtos compartilhados informa todos os produtos que o marketplace disponibilizou para sua loja vender. São produtos sincronizados com o Catálogo do marketplace. 
 
diff --git a/docs/tutorials/pt/send-the-seller-white-label-payment-methods-to-the-marketplace.md b/docs/tutorials/pt/send-the-seller-white-label-payment-methods-to-the-marketplace.md
index 221c3920a..3a642bf12 100644
--- a/docs/tutorials/pt/send-the-seller-white-label-payment-methods-to-the-marketplace.md
+++ b/docs/tutorials/pt/send-the-seller-white-label-payment-methods-to-the-marketplace.md
@@ -19,9 +19,7 @@ O objetivo deste tutorial é ensinar como enviar os meios de pagamento de um Sel
 
 Esta feature permite que as compras realizadas num e-commerce sejam realizadas com os meios de pagamento de uma loja física. Isto diminui a complexidade da operação, separando centros de custo, pois a fatura e os pagamentos serão vinculados diretamente ao CNPJ da loja física, que atua como Seller White Label de um Marketplace.
 
-<div class="alert alert-info">
-Esta configuração substitui a utilização da antiga feature de<strong> Contas Alternativas</strong> para este cenário.
-</div>
+>ℹ️ Esta configuração substitui a utilização da antiga feature de** Contas Alternativas** para este cenário.
 
 ## Cadastrar meios de pagamento no Seller White Label
 
diff --git a/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md b/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
index df473b3f4..d3233f53b 100644
--- a/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
+++ b/docs/tutorials/pt/sending-clothes-shoes-and-bags-attributes-to-mercado-livre.md
@@ -15,9 +15,7 @@ legacySlug: envio-dos-atributos-de-roupas-calcados-e-bolsas-para-o-mercado-livre
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class="alert alert-info">
-O envio dos atributos dos produtos de tipo Roupas, Calçados ou Bolsas segue um fluxo diferente dos demais. Neste processo de mapeamento, o resultado é que os SKUs serão mostrados todos no mesmo anúncio. Para os outros tipos de produto, o Mercado Livre realiza um mapeamento automático.
-</div>
+>ℹ️ O envio dos atributos dos produtos de tipo Roupas, Calçados ou Bolsas segue um fluxo diferente dos demais. Neste processo de mapeamento, o resultado é que os SKUs serão mostrados todos no mesmo anúncio. Para os outros tipos de produto, o Mercado Livre realiza um mapeamento automático.
 
 Para enviar os atributos dos produtos do tipo __Roupas__, __Calçados__ e __Bolsas__ para o Mercado Livre, siga os passos abaixo:
 
@@ -25,9 +23,7 @@ Para enviar os atributos dos produtos do tipo __Roupas__, __Calçados__ e __Bols
 2. Preencha a planilha modelo com os Ids dos SKUs a serem enviados para o Mercado Livre e com os valores de atributos aceitos pelo Mercado Livre. Os valores aceitos podem ser encontrados nos links abaixo.
 3. Salve a planilha modelo com os valores preenchidos. 
 
-<div class="alert alert-info">
-Os valores aceitos pelo Mercado Livre podem ser encontrados nos links a seguir. Clique no nome do seu país para fazer o download. Você vai encontrar códigos referentes a <u>Cor Principal</u>, <u>Cor Secundária</u>, <u>Tamanho de calçado para adultos</u>, <u>Tamanho de calçado para crianças</u>, <u>Tamanho de roupa para adultos</u> e <u>Tamanho de roupa para crianças</u>. Estes valores deve ser preenchidos adequadamente nos campos <strong>Cor Principal</strong>, <strong>Cor Secundária</strong> e <strong>Tamanho</strong> da planilha modelo. Com exceção do atributo <em>Cor Secundária</em>, todos os outros campos são obrigatórios (SKU_ID, Cor Principal e Tamanho).
-</div>
+>ℹ️ Os valores aceitos pelo Mercado Livre podem ser encontrados nos links a seguir. Clique no nome do seu país para fazer o download. Você vai encontrar códigos referentes a <u>Cor Principal</u>, <u>Cor Secundária</u>, <u>Tamanho de calçado para adultos</u>, <u>Tamanho de calçado para crianças</u>, <u>Tamanho de roupa para adultos</u> e <u>Tamanho de roupa para crianças</u>. Estes valores deve ser preenchidos adequadamente nos campos **Cor Principal**, **Cor Secundária** e **Tamanho** da planilha modelo. Com exceção do atributo *Cor Secundária*, todos os outros campos são obrigatórios (SKU_ID, Cor Principal e Tamanho).
 
 __Links com os valores aceitos pelo Mercado Livre__:
 
diff --git a/docs/tutorials/pt/sending-sku-attributes-to-amazon.md b/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
index f8985dcdb..0aa0fb3b5 100644
--- a/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/pt/sending-sku-attributes-to-amazon.md
@@ -23,13 +23,9 @@ O mapeamento só será feito uma vez para cada categoria. Desta forma, mesmo já
 
 2. Preencha os campos da planilha de mapeamento de acordo com as indicações abaixo:
 
-<div class="alert alert-danger">
-OBS: se <strong>nenhum</strong> dos atributos da sua categoria for exigido obrigatoriamente pela Amazon, então <strong>não é necessário fazer o mapeamento</strong>. Basta reindexar seus produtos para que eles sejam enviados diretamente pela integração.
-</div>
+>❗ OBS: se **nenhum** dos atributos da sua categoria for exigido obrigatoriamente pela Amazon, então **não é necessário fazer o mapeamento**. Basta reindexar seus produtos para que eles sejam enviados diretamente pela integração.
 
-<div class="alert alert-danger">
-Atenção: caso as colunas não forem nomeadas <strong>tal qual</strong> a forma que é ilustrada na imagem, as SKUs <strong>não</strong> serão enviadas corretamente para a Amazon. Qualquer <strong>pequeno erro de digitação</strong> pode afetar o processo. 
-</div>
+>❗ Atenção: caso as colunas não forem nomeadas **tal qual** a forma que é ilustrada na imagem, as SKUs **não** serão enviadas corretamente para a Amazon. Qualquer **pequeno erro de digitação** pode afetar o processo.
 
 1. __ID categoria:__ é o ID da categoria na VTEX. Você consegue encontrá-lo ao lado do nome de cada categoria ao expandir a árvore.
 2. __VariationTheme:__ é a maneira que o SKU varia no marketplace. Você deve preencher com os Variations Themes que se adequam à categoria de seus produtos e respectivos PTDs.
@@ -51,9 +47,7 @@ Planilha de exemplo usando a categoria Clothing & Accessories:
 
 ![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
-<div class="alert alert-danger">
-Lembre-se que estes valores devem estar de acordo com os valores aceitos pela Amazon. Consulte os termos aceitos e faça o De/Para entre o que está cadastrado no seu campo de SKU na VTEX e os valores permitidos na Amazon.
-</div>
+>❗ Lembre-se que estes valores devem estar de acordo com os valores aceitos pela Amazon. Consulte os termos aceitos e faça o De/Para entre o que está cadastrado no seu campo de SKU na VTEX e os valores permitidos na Amazon.
 
 Após preencher a planilha, acesse __Integrações__ no menu do Admin:
 
diff --git a/docs/tutorials/pt/sent-offers-beta.md b/docs/tutorials/pt/sent-offers-beta.md
index 1529128e9..aa2ebe7cb 100644
--- a/docs/tutorials/pt/sent-offers-beta.md
+++ b/docs/tutorials/pt/sent-offers-beta.md
@@ -33,9 +33,7 @@ Quando um seller configura condições de preço e estoque, ele está preparando
 -   **Com erro:** quando o sistema encontra um problema que previne um anúncio de ser enviado, ou atualizado em um canal. Esse status significa que o anúncio requer correção manual. 
 -   **Indisponível:** quando o anúncio é descartado, por estar inativo ou não incluído na política comercial determinada para o canal.
 
-<div class="alert alert-info">
-Ao clicar em  <code>Ver Lista</code>  você será redirecionado à <a href="https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE">listagem de Anúncios</a>.
-</div>
+>ℹ️ Ao clicar em  `Ver Lista`  você será redirecionado à [listagem de Anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE).
 
 ## Canais
 
diff --git a/docs/tutorials/pt/sent-offers-buybox-opportunities.md b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
index 4cba68222..63e8bcc08 100644
--- a/docs/tutorials/pt/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
@@ -15,12 +15,10 @@ legacySlug: anuncios-enviados-oportunidades-de-buybox-beta
 subcategory: 
 ---
 
-<div class="alert alert-info">
-Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo <b>Gerenciamento de anúncios</b>.
-Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
-Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email <a href="taissa.araujo@vtex.com.br">taissa.araujo@vtex.com.br</a>.
-Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do <a href="https://developers.vtex.com/updates/release-notes">Developer portal na página de release notes</a> e <a href="https://help.vtex.com/pt/en/announcements">VTEX Help Center na página de novidades</a>.
-</div>  
+>ℹ️ Para evoluir sua experiência ao sincronizar e atualizar anúncios, o time da VTEX está desenvolvendo uma nova funcionalidade que irá substituir o atual módulo **Gerenciamento de anúncios**.
+> Por este motivo, o Gerenciamento de anúncios não receberá novas atualizações ou manutenção. 
+> Para conectores e marketplaces que já se integraram com o módulo, solicitamos que entre em contato com nosso time de desenvolvimento através do email [taissa.araujo@vtex.com.br](taissa.araujo@vtex.com.br).
+> Para os conectores com interesse em iniciar a integração, solicitamos que aguardem o lançamento do novo módulo, assim que disponível avisaremos a todos os clientes através do [Developer portal na página de release notes](https://developers.vtex.com/updates/release-notes) e [VTEX Help Center na página de novidades](https://help.vtex.com/pt/en/announcements).  
 
 Anúncio é um SKU de um seller que foi enviado para um canal de vendas e teve seu preço e estoque configurados. O módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/listagem-de-anuncios--7MRb9S78aBdZjFGpbuffpE) do Admin VTEX permite que sellers supervisionem o envio e sincronização de seus produtos para marketplaces e também apresenta oportunidades de mais vendas para seus anúncios. 
 
@@ -65,9 +63,7 @@ Siga os passos abaixo para adicionar seu anúncio ao Catálogo MeLi:
 4. Na página de **Oportunidade do Anúncio**, avalie se seu anúncio é compatível com o anúncio já presente no marketplace. Caso sejam compatíveis, clique em `Adicionar ao Catálogo MeLi`. 
 5. Clique em `Adicionar`.
 
-<div class="alert alert-warning">
-Essa ação não poderá ser desfeita, portanto certifique-se de que os anúncios são compatíveis. Se seu anúncio não for compatível com o produto já presente no marketplace, não adicione-o ao Catálogo MeLi. Adicionar anúncios que não fazem parte do produto pode prejudicar sua reputação como seller naquele marketplace.  
-</div>
+>⚠️ Essa ação não poderá ser desfeita, portanto certifique-se de que os anúncios são compatíveis. Se seu anúncio não for compatível com o produto já presente no marketplace, não adicione-o ao Catálogo MeLi. Adicionar anúncios que não fazem parte do produto pode prejudicar sua reputação como seller naquele marketplace.
 
 Para que seu anúncio esteja bem posicionado no Catálogo MeLi, finalize as configurações indicadas na próxima seção [Ganhando e perdendo no Catálogo MeLi](#ganhando-e-perdendo-no-buybox).
 
diff --git a/docs/tutorials/pt/service-indicators.md b/docs/tutorials/pt/service-indicators.md
index 70b533c0e..c54aa01f4 100644
--- a/docs/tutorials/pt/service-indicators.md
+++ b/docs/tutorials/pt/service-indicators.md
@@ -15,9 +15,7 @@ legacySlug: indicadores-de-servico
 subcategory: 2A1RNDhwU4kqCN3XimtaD2
 ---
 
-<div class="alert alert-info"> 
- Esse artigo está relacionado com a funcionalidade de <b>Relatório de Indicadores</b>. Caso queira saber mais, acesse<a href="https://help.vtex.com/pt/tutorial/relatorio-de-indicadores--7lbICsrCArXDxUYeeHJ2c5">  Relatório de Indicadores</a>.
-</div>
+>ℹ️ Esse artigo está relacionado com a funcionalidade de **Relatório de Indicadores**. Caso queira saber mais, acesse[  Relatório de Indicadores](https://help.vtex.com/pt/tutorial/relatorio-de-indicadores--7lbICsrCArXDxUYeeHJ2c5).
 
 ## Serviço
 
diff --git a/docs/tutorials/pt/service-management.md b/docs/tutorials/pt/service-management.md
index d0b6312dc..8511527a8 100644
--- a/docs/tutorials/pt/service-management.md
+++ b/docs/tutorials/pt/service-management.md
@@ -26,9 +26,7 @@ Depois de acessar a aba você pode:
 * [Finalizar serviços](#finalizar-servicos);
 * [Deletar serviços](#deletar-servicos);
 
-<div class="alert alert-info">
-Não recomendamos o cadastro de novos serviços por essa aba.  Para cadastrar serviços pela plataforma utilize a Importação de Serviços
-</div>
+>ℹ️ Não recomendamos o cadastro de novos serviços por essa aba.  Para cadastrar serviços pela plataforma utilize a Importação de Serviços
 
 ## Lista de Serviços
 
@@ -55,9 +53,7 @@ Pela lista você pode visualizar os detalhes de um serviço específico, alterá
     2. Clique em Salvar. 
 * **Exclusão do serviço:** ao clicar em `Excluir`. Na página Detalhes do Serviços clique em `Apagar` no canto superior esquerdo da tela.
 
-<div class="alert alert-warning"> 
-Só é possível excluir e editar um serviço que possui status <b>Ativo</b>.
-</div>
+>⚠️ Só é possível excluir e editar um serviço que possui status **Ativo**.
 
 ## Filtros
 
diff --git a/docs/tutorials/pt/services-import.md b/docs/tutorials/pt/services-import.md
index cbb5b62d9..6d371acae 100644
--- a/docs/tutorials/pt/services-import.md
+++ b/docs/tutorials/pt/services-import.md
@@ -75,16 +75,16 @@ Depois de baixar o modelo é preciso preencher os campos com as informações do
 * **Romaneio:** número do romaneio ou nome para a rota estruturada. Este campo será relevante caso a funcionalidade de romaneio esteja ativada pelo embarcador. É importante ressaltar que se essa funcionalidade estiver ativada, é possível criar rotas com datas futuras, sendo possível atribuir o portador no momento da criação. Também é possível atribuir a rota a um portador posteriormente. Para ativar essa funcionalidade entre em contato com o [suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM). 
 * **Peso:** peso do pacote. Utilize quilogramas (Kg) como unidade de medida.
 
-<div class="alert alert-danger">
-Cuidados com o preenchimento da planilha:
- <body>
-<ul>
-  <li>Se algum campo não for utilizado deixe-o em branco.</li>
-  <li>Não altere os rótulos das colunas da planilha modelo.</li>
-  <li>Caso os campos estejam preenchidos de forma errada o serviço não será criado.</li>
-   </ul>
-  </body>
-</div>
+>❗ Cuidados com o preenchimento da planilha:
+>  <body>
+>
+> * Se algum campo não for utilizado deixe-o em branco.
+>
+> * Não altere os rótulos das colunas da planilha modelo.
+>
+> * Caso os campos estejam preenchidos de forma errada o serviço não será criado.
+>
+> </body>
 
 ![menu importação de serviços](https://images.ctfassets.net/alneenqid6w5/6VXBtxVKQvnNvqEwCI09dZ/15a4abddec959d9efdd9ae97f4116b97/importacao_servi__os.png)
 
diff --git a/docs/tutorials/pt/services-scheduling.md b/docs/tutorials/pt/services-scheduling.md
index 210a6c8ae..699622729 100644
--- a/docs/tutorials/pt/services-scheduling.md
+++ b/docs/tutorials/pt/services-scheduling.md
@@ -17,10 +17,8 @@ subcategory: 7GypxQ3HDmFVCHTNTwyhr0
 
 Caso haja a necessidade de se organizar para algum serviço que deve ser feito em uma data e turno já definidos, você  pode fazer esse agendamento na plataforma VTEX Tracking.
 
-<div class="alert alert-warning"> 
-Para utilizar o agendamento, os serviços precisam estar previamente cadastrados na plataforma.  Leia o artigo <a href="https://vtexhelp.myvtex.com/tutorial/importacao-de-servicos--2LRgMnGbX0af7krrs6tXy3?__bindingAddress=vtexhelp.myvtex.com/">Importação de Serviços</a>
- para maiores informações.
-</div>
+>⚠️ Para utilizar o agendamento, os serviços precisam estar previamente cadastrados na plataforma.  Leia o artigo [Importação de Serviços](https://vtexhelp.myvtex.com/tutorial/importacao-de-servicos--2LRgMnGbX0af7krrs6tXy3?__bindingAddress=vtexhelp.myvtex.com/)
+>  para maiores informações.
 
 Para agendar um serviço é preciso realizar os seguintes passos:
 
@@ -50,9 +48,7 @@ Para escolher o turno da entrega, marque um X na célula em apenas um dos turnos
 
 ![exemplo de planilha de agendamento](https://images.ctfassets.net/alneenqid6w5/5crlOibYcmzfWkusdc2iSP/2cefb30f0df8fc7ab61104a09f8f9414/exemplo_planilha_agendamento.png)
 
-<div class="alert alert-danger"> 
-O modelo da planilha não deve ser alterado. Nenhuma coluna deve ser modificada ou trocada de posição. 
-</div>
+>❗ O modelo da planilha não deve ser alterado. Nenhuma coluna deve ser modificada ou trocada de posição.
 
 ## Upload da planilha
 
@@ -72,8 +68,6 @@ Depois de preencher a planilha, você precisa subir o arquivo na plataforma VTEX
 4. Na tela de Editar Serviço, faça a edição necessária.
 5. Clique em __Salvar.__
 
-<div class="alert alert-warning">
-Os agendamentos só podem ser alterados se as entregas ainda estiverem no status Ativo. 
-</div>
+>⚠️ Os agendamentos só podem ser alterados se as entregas ainda estiverem no status Ativo.
 
 ![Agendamento de serviços](https://images.ctfassets.net/alneenqid6w5/OhKdJX8S3Ef4EjoUOaGL3/5f463a280ae7cfa51a856d047b39be82/Agendamento.gif)
diff --git a/docs/tutorials/pt/set-up-alelo-payment-method-for-cielo-v3.md b/docs/tutorials/pt/set-up-alelo-payment-method-for-cielo-v3.md
index 39b90740f..ab26881fe 100644
--- a/docs/tutorials/pt/set-up-alelo-payment-method-for-cielo-v3.md
+++ b/docs/tutorials/pt/set-up-alelo-payment-method-for-cielo-v3.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Neste artigo, explicaremos como habilitar o vale alimentação Alelo como um meio de pagamento no Checkout.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: o vale alimentação Alelo é um meio de pagamento aceito apenas entre clientes brasileiros.
-</div>
+>ℹ️ **Atenção**: o vale alimentação Alelo é um meio de pagamento aceito apenas entre clientes brasileiros.
 
 Atualmente, na VTEX, a Cielo é a adquirente que aceita a Alelo como meio de pagamento. Logo, o primeiro passo é habilitar essa adquirente como afiliação de gateway na sua loja. Você pode conferir o tutorial completo de como realizar essa configuração [aqui](https://help.vtex.com/pt/tutorial/configurar-adquirente-cielo--3avjZ7q65WcM02K8K0eeWu?locale=pt "aqui"). 
 
@@ -41,6 +39,4 @@ Agora, acompanhe as instruções:
 8. Do lado direito da tela, defina as __condições especiais__ de pagamento.
 9. Clique no botão azul __“Salvar”__ para finalizar.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: lembre-se que as condições especiais de pagamento demoram cerca de 10 minutos para serem aplicadas no Checkout.
-</div> 
+>ℹ️ **Atenção**: lembre-se que as condições especiais de pagamento demoram cerca de 10 minutos para serem aplicadas no Checkout. 
diff --git a/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md b/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md
index 9ff301842..3db324304 100644
--- a/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md
+++ b/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 O 3D Secure 2.0 (3DS 2) é um fluxo de autenticação que aumenta a segurança nos pagamentos realizados com cartões de crédito e débito, por meio da análise interna de uma grande quantidade de dados presentes em cada transação.
 
-<div class="alert alert-warning">
-O 3DS 2 é suportado somente para algumas afiliações na VTEX. Verifique junto ao seu provedor de pagamentos e no Admin VTEX se esta funcionalidade está disponível.
-</div>
+>⚠️ O 3DS 2 é suportado somente para algumas afiliações na VTEX. Verifique junto ao seu provedor de pagamentos e no Admin VTEX se esta funcionalidade está disponível.
 
 Antes de iniciar a configuração, é necessário abrir um chamado com o time de suporte da VTEX solicitando a habilitação do 3DS 2 na sua loja. Para maiores informações, acesse [como abrir um ticket](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
@@ -39,7 +37,5 @@ Para configurar a autenticação 3DS 2 nas afiliações, siga os passos abaixo:
 6. No campo __Suporte 3DS 2.0__, selecione a opção __“Yes”__.
 7. Clique em __"Salvar"__. 
 
-<div class="alert alert-warning">
-  A descrição do campo do 3DS 2 (<b>"Suporte 3DS 2.0"</b>, informado no Passo 8) pode sofrer variações de acordo com o tipo de provedor de pagamento a ser configurado. Consulte o suporte técnico do provedor de pagamento escolhido para identificar o campo correto a ser selecionado para habilitar a autenticação 3DS 2.
-</div>
+>⚠️ A descrição do campo do 3DS 2 (**"Suporte 3DS 2.0"**, informado no Passo 8) pode sofrer variações de acordo com o tipo de provedor de pagamento a ser configurado. Consulte o suporte técnico do provedor de pagamento escolhido para identificar o campo correto a ser selecionado para habilitar a autenticação 3DS 2.
 
diff --git a/docs/tutorials/pt/setting-up-a-personal-gift-message.md b/docs/tutorials/pt/setting-up-a-personal-gift-message.md
index 8ebbedc66..eb915e17f 100644
--- a/docs/tutorials/pt/setting-up-a-personal-gift-message.md
+++ b/docs/tutorials/pt/setting-up-a-personal-gift-message.md
@@ -51,6 +51,4 @@ Você pode visualizar a mensagem escrita em __Minha Conta > Meus Pedidos__:
 
 ![](https://images.contentful.com/alneenqid6w5/6h7iGpA880OgaemumSsEiG/10764ef2d3113be498fb24802e5d35c5/mensagem-meus-pedidos.png)
 
-<div class="alert alert-info">
-  <p>Após a configuração do serviço no SKU, aguarde a indexação para o cadastro ter efeito no site. Após isto já será possível testar a compra com este serviço ativo.</p>
-</div>
+>ℹ️ Após a configuração do serviço no SKU, aguarde a indexação para o cadastro ter efeito no site. Após isto já será possível testar a compra com este serviço ativo.
diff --git a/docs/tutorials/pt/setting-up-abandoned-carts.md b/docs/tutorials/pt/setting-up-abandoned-carts.md
index 45ae60f99..b4bb994b2 100644
--- a/docs/tutorials/pt/setting-up-abandoned-carts.md
+++ b/docs/tutorials/pt/setting-up-abandoned-carts.md
@@ -42,9 +42,7 @@ Você pode criar o seu próprio template de email customizado ou utilizar a opç
 
 ![template xhtml](https://images.ctfassets.net/alneenqid6w5/44IZ7N3din2EELL15z5FeQ/5e4164dc9abd8f5139d7934cae41e44c/Template_XHTML.PNG)
 
-<div class="alert alert-warning">
-Recomendamos que a customização de template seja realizada por profissionais com experiência no módulo CMS, e preferencialmente, que já tenham realizado configurações de outros templates de página e prateleira.
-</div>
+>⚠️ Recomendamos que a customização de template seja realizada por profissionais com experiência no módulo CMS, e preferencialmente, que já tenham realizado configurações de outros templates de página e prateleira.
 
 Para utilizar uma opção padrão de template, siga os seguintes passos:
 
@@ -131,9 +129,7 @@ Para que o disparo da trigger seja realizado, os filtros precisam estar obrigato
 13. Clique em `Salvar`.
 14. Crie um carrinho e feche a página para testar a trigger.
 
-  <div class="alert alert-warning">
-    <p>A sessão de uma página expira em 30 minutos. Somente depois desse período o Master Data inicia a contagem do período agendado para o disparo da trigger de Carrinho Abandonado. Logo, o tempo até o email chegar corresponde ao tempo da sessão (30 minutos) mais o período agendado na trigger.</p>
-</div>
+  >⚠️ A sessão de uma página expira em 30 minutos. Somente depois desse período o Master Data inicia a contagem do período agendado para o disparo da trigger de Carrinho Abandonado. Logo, o tempo até o email chegar corresponde ao tempo da sessão (30 minutos) mais o período agendado na trigger.
 
 14. Uma vez que você houver recebido a mensagem do carrinho abandonado em seu email, no campo __Destinatário__ (passo 12), selecione a opção __CL:Email__ e  clique em `Adicionar email dinâmico`.
 15. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/setting-up-alternative-accounts.md b/docs/tutorials/pt/setting-up-alternative-accounts.md
index 8cdd55e0e..79d762c9c 100644
--- a/docs/tutorials/pt/setting-up-alternative-accounts.md
+++ b/docs/tutorials/pt/setting-up-alternative-accounts.md
@@ -15,6 +15,4 @@ legacySlug: configurando-contas-alternativas
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-info">
-O recurso de Contas Alternativas foi descontinuado. Para substituí-lo, use a solução de <strong>Contas Franquia</strong> e <strong>Sellers White Label</strong>. Veja mais detalhes <a href="http://help.vtex.com/pt/faq/definicoes-de-conta-franquia-e-seller-white-label">neste artigo do Help</a>.
-</div>
+>ℹ️ O recurso de Contas Alternativas foi descontinuado. Para substituí-lo, use a solução de **Contas Franquia** e **Sellers White Label**. Veja mais detalhes [neste artigo do Help](http://help.vtex.com/pt/faq/definicoes-de-conta-franquia-e-seller-white-label).
diff --git a/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
index 88660b170..a5ca15fd9 100644
--- a/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/pt/setting-up-app-linking-for-payments-app-in-instore.md
@@ -37,9 +37,7 @@ Se necessário, o inStore pode enviar informações adicionais. Exemplo com o su
 - `administrativePassword`: string - senha padrão. Por exemplo, `cappta`.
 - `cnpj`: string.
 
-<div class="alert alert-info">
-Para criar qualquer configuração extra, você precisa enviar para a equipe do inStore (instoredevs@vtex.com.br) os extras que a app precisa para concluir a transação. Assim, criaremos um formulário no módulo de Pagamentos para que o cliente possa configurar seu adquirente.
-</div>
+>ℹ️ Para criar qualquer configuração extra, você precisa enviar para a equipe do inStore (instoredevs@vtex.com.br) os extras que a app precisa para concluir a transação. Assim, criaremos um formulário no módulo de Pagamentos para que o cliente possa configurar seu adquirente.
 
 ## URI de envio e URI de resposta para cada ação
 
@@ -124,9 +122,7 @@ URI final que a app de pagamento receberá para executar a ação de reembolso c
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&autoConfirm=True&sellerName=instoreqa&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class="alert alert-warning">
-<strong>OBSERVAÇÃO:</strong> Nem todos os parâmetros serão utilizados por todos os adquirentes/apps de pagamento. Exemplo: <code>transactionId</code>. Este parâmetro é o ID de uma transação na VTEX que identifica todos os pagamentos de um pedido completo no PCI Gateway da VTEX. Uma transação pode conter vários pagamentos, como quando um pedido é pago com vários cartões de crédito ou débito.
-</div>
+>⚠️ **OBSERVAÇÃO:** Nem todos os parâmetros serão utilizados por todos os adquirentes/apps de pagamento. Exemplo: `transactionId`. Este parâmetro é o ID de uma transação na VTEX que identifica todos os pagamentos de um pedido completo no PCI Gateway da VTEX. Uma transação pode conter vários pagamentos, como quando um pedido é pago com vários cartões de crédito ou débito.
 
 ## Exemplos de URI de resposta para cada ação
 
@@ -185,9 +181,7 @@ Para que a integração funcione, é preciso que o cliente configure no módulo
 
 A integração do AppLinking não inclui outras dependências, uma vez que a comunicação entre o aplicativo inStore e o aplicativo de pagamento acontece com URIs específicas contendo todos os parâmetros de configuração e pagamento necessários para a ação.
 
-<div class="alert alert-warning">
-No Android, toda comunicação deve acontecer com uma nova <code>Intent</code>. Isso significa que você não deve enviar a resposta como um retorno de chamada da <code>Intent</code> inicial. Em vez disso, você deve enviar um novo <code>Intent</code> ao aplicativo inStore com a resposta do anterior.
-</div>
+>⚠️ No Android, toda comunicação deve acontecer com uma nova `Intent`. Isso significa que você não deve enviar a resposta como um retorno de chamada da `Intent` inicial. Em vez disso, você deve enviar um novo `Intent` ao aplicativo inStore com a resposta do anterior.
 
 Para configurar o conector do InStore, você deve seguir os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-b2b-on-vtex.md b/docs/tutorials/pt/setting-up-b2b-on-vtex.md
index 1199c091e..8fd51ca29 100644
--- a/docs/tutorials/pt/setting-up-b2b-on-vtex.md
+++ b/docs/tutorials/pt/setting-up-b2b-on-vtex.md
@@ -21,9 +21,7 @@ Na VTEX, ambientes B2B normalmente são completamente ou parcialmente bloqueados
 
 Veja abaixo as configurações necessárias para criar uma loja B2B, na VTEX.
 
-<div class="alert alert-info">
-<p>Toda loja B2B se preparando para entrar em produção e fazer configuração final de domínio deve contatar <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a> com antecedência e solicitar que a configuração interna seja feita.</p>
-</div>
+>ℹ️ Toda loja B2B se preparando para entrar em produção e fazer configuração final de domínio deve contatar [nosso Suporte](https://support.vtex.com/hc/pt-br/requests) com antecedência e solicitar que a configuração interna seja feita.
 
 ## Pré-requisito
 
@@ -65,9 +63,7 @@ O usuário que ainda não é cadastrado no site precisa ter uma interface para r
 
 Dessa forma, é necessário definir os campos desse pré-cadastro. Normalmente, os B2Bs utilizam informações de cliente (nome, e-mail, telefone, etc) e endereço (rua, bairro, cidade, etc) para esse pré-cadastro. Confira o artigo [Importar dados de clientes](https://help.vtex.com/pt/tutorial/importando-dados-de-clientes-brasil--2zWYVOyj0sISYQmeUwCsI0 "Importar dados de clientes - Brasil") para mais informações sobre os dados necessários.
 
-<div class="alert alert-warning">
-  <p>O campo utilizado como regra condicional na política comercial nunca poderá fazer parte desse formulário, uma vez que o próprio usuário não pode realizar sua própria aprovação, cabendo à loja essa responsabilidade.</p>
-</div>
+>⚠️ O campo utilizado como regra condicional na política comercial nunca poderá fazer parte desse formulário, uma vez que o próprio usuário não pode realizar sua própria aprovação, cabendo à loja essa responsabilidade.
 
 ## 4. Criar formulário de pré-cadastro
 
@@ -79,7 +75,4 @@ As informações submetidas no formulário deverão ser enviadas para o CRM atra
 
 Com tudo configurado e, finalmente, com o B2B em produção, a rotina do lojista dependerá das regras e necessidades de seu negócio. Basicamente, a cada novo cadastro, o lojista deverá avaliar o usuário e aprová-lo ou não na interface do CRM, que pode ser acessada pela URL `http://{nome_da_conta}.vtexcrm.com.br/`.
 
-<div class="alert alert-info">
-  <p>Este artigo descreve as configurações básicas de um B2B, porém, é possível customizar o sistema para essa necessidade de várias formas, inclusive, enviando emails (triggers) a partir de eventos pré-definidos.
-</p>
-</div>
+>ℹ️ Este artigo descreve as configurações básicas de um B2B, porém, é possível customizar o sistema para essa necessidade de várias formas, inclusive, enviando emails (triggers) a partir de eventos pré-definidos.
diff --git a/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md b/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md
index 80461486c..be45fd878 100644
--- a/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md
+++ b/docs/tutorials/pt/setting-up-bradesco-registered-ticket.md
@@ -15,13 +15,11 @@ legacySlug: configurar-boleto-registrado-bradesco
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Para configurar o boleto registrado do Bradesco, é necessário utilizar o conector do __Bradesco Registrado__ e configurar a condição de pagamento de boleto bancário. Desta forma, os boletos emitidos serão registrados pelo Bradesco.
 
-<div class="alert alert-info">
-Atenção: antes de configurar o meio de pagamento no Admin VTEX, é preciso cadastrar a URL de notificação no <a href="https://meiosdepagamentobradesco.com.br/gl/login.jsp"> Internet Banking Bradesco</a>. Para isso, basta inserir o valor https://meiosdepagamentobradesco.com.br/notification no campo em questão.
-</div>
+>ℹ️ Atenção: antes de configurar o meio de pagamento no Admin VTEX, é preciso cadastrar a URL de notificação no [ Internet Banking Bradesco](https://meiosdepagamentobradesco.com.br/gl/login.jsp). Para isso, basta inserir o valor https://meiosdepagamentobradesco.com.br/notification no campo em questão.
 
 Para realizar a configuração, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-conductor-gateway.md b/docs/tutorials/pt/setting-up-conductor-gateway.md
index 41cfdbc18..7847ac50a 100644
--- a/docs/tutorials/pt/setting-up-conductor-gateway.md
+++ b/docs/tutorials/pt/setting-up-conductor-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-conductor
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A Conductor é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) que atua há mais de 20 anos com o processamento de pagamentos. Na VTEX, ela pode ser configurada para processar pagamentos realizados com __cartões de crédito com bandeira própria__.
 
diff --git a/docs/tutorials/pt/setting-up-customized-payments-using-mercadopago-latin-america.md b/docs/tutorials/pt/setting-up-customized-payments-using-mercadopago-latin-america.md
index 64d37764e..fb571626e 100644
--- a/docs/tutorials/pt/setting-up-customized-payments-using-mercadopago-latin-america.md
+++ b/docs/tutorials/pt/setting-up-customized-payments-using-mercadopago-latin-america.md
@@ -15,9 +15,7 @@ legacySlug: configurar-pagamentos-customizados-usando-mercadopago-latam
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Este artigo trata de configurações aplicáveis em lojas que atuam nos seguintes países da América Latina: <strong>Argentina</strong>, <strong>Chile</strong>, <strong>Colômbia</strong> e <strong>Uruguai</strong>.
-</div>
+>⚠️ Este artigo trata de configurações aplicáveis em lojas que atuam nos seguintes países da América Latina: **Argentina**, **Chile**, **Colômbia** e **Uruguai**.
 
 Você pode usar o Mercado Pago para oferecer pagamentos customizados (usando cartões de crédito locais) na sua loja. Para isso, você precisa primeiro cadastrar a afiliação de gateway [MercadoPagoV1](/pt/tutorial/configurar-o-subadquirente-mercadopagov1). Depois, basta seguir as etapas abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-cybersource-antifraud.md b/docs/tutorials/pt/setting-up-cybersource-antifraud.md
index c0489a330..4dd465739 100644
--- a/docs/tutorials/pt/setting-up-cybersource-antifraud.md
+++ b/docs/tutorials/pt/setting-up-cybersource-antifraud.md
@@ -21,9 +21,7 @@ Se você estiver procurando mais detalhes sobre o __gateway__ CyberSource, leia
 
 ## Configurar antifraude CyberSource
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de efetuar o Passo 6. desta seção.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de efetuar o Passo 6. desta seção.
 
 1. No Admin VTEX, acesse __Configurações da loja > Pagamentos > Provedores__, ou digite __Provedores__ na barra de busca no topo da página.
 2. Na tela de provedores, clique no botão `Novo provedor`.
@@ -52,6 +50,4 @@ Depois de configurar o antifraude da CyberSource, ele vai estar disponível para
 6. Selecione a CyberSource.
 7. Clique em `Salvar`.
 
-<div class="alert alert-warning">
-Para que uma transação passe pela análise do antifraude, <strong>a condição de pagamento utilizada pelo cliente precisa estar associada a ele</strong>.
-</div>
+>⚠️ Para que uma transação passe pela análise do antifraude, **a condição de pagamento utilizada pelo cliente precisa estar associada a ele**.
diff --git a/docs/tutorials/pt/setting-up-cybersource-gateway.md b/docs/tutorials/pt/setting-up-cybersource-gateway.md
index 272306cbc..a21ed2f5c 100644
--- a/docs/tutorials/pt/setting-up-cybersource-gateway.md
+++ b/docs/tutorials/pt/setting-up-cybersource-gateway.md
@@ -37,9 +37,7 @@ Os seguintes apps da Cybersource devem ser instalados na conta de sua loja:
 - __vtex.cybersource__
 - __vtex.cybersource-payer-auth__
 
-<div class="alert alert-warning">
-  Caso você pretenda utilizar o sistema de antifraude da Cybersource, mas deseja transacionar os pagamentos em um gateway que não seja o da Cybersource, será necessário instalar o app <b>vtex.cybersource-fraud</b>.
-  </div>
+>⚠️ Caso você pretenda utilizar o sistema de antifraude da Cybersource, mas deseja transacionar os pagamentos em um gateway que não seja o da Cybersource, será necessário instalar o app **vtex.cybersource-fraud**.
 
 Saiba mais como instalar aplicativos em uma conta VTEX em [Installing an app](https://developers.vtex.com/docs/guides/vtex-io-documentation-installing-an-app). 
 
@@ -47,9 +45,7 @@ Saiba mais como instalar aplicativos em uma conta VTEX em [Installing an app](ht
 
 Após a instalação dos apps você deve criar as chaves de autenticação no ambiente da Cybersource. 
 
-<div class="alert alert-warning">
-  As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Cybersource para informações atualizadas.
-  </div>
+>⚠️ As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta na Cybersource para informações atualizadas.
 
 Siga os passos abaixo:
 
@@ -138,9 +134,7 @@ Para processar pagamentos com cartões de crédito por meio da Cybersource, siga
 8. Se desejar, você também poderá configurar [condições especiais de pagamento](https://help.vtex.com/pt/tutorial/condicoes-especiais--tutorials_456).
 9. Clique em __Salvar__.
 
-<div class="alert alert-warning">
-  Se você criou anteriormente condições de pagamento com cartão de crédito para outros gateways (incluindo o provedor Cybersource legado), poderá definir essas condições como <b>Inativas</b>. As transações em andamento iniciadas nesse provedor ainda serão processadas por ele, mesmo que esteja inativo. Apenas novas transações serão processadas pelo novo provedor Cybersource IO. Caso você precise reverter para o provedor anterior por qualquer motivo, basta definir as respectivas condições de pagamento como <b>Ativas</b> e as condições de pagamento do Cybersource IO como <b>Inativas</b>.
-  </div>
+>⚠️ Se você criou anteriormente condições de pagamento com cartão de crédito para outros gateways (incluindo o provedor Cybersource legado), poderá definir essas condições como **Inativas**. As transações em andamento iniciadas nesse provedor ainda serão processadas por ele, mesmo que esteja inativo. Apenas novas transações serão processadas pelo novo provedor Cybersource IO. Caso você precise reverter para o provedor anterior por qualquer motivo, basta definir as respectivas condições de pagamento como **Ativas** e as condições de pagamento do Cybersource IO como **Inativas**.
 
 ## Configurar Cybersource IO Device Fingerprint (opcional)
 
@@ -148,9 +142,7 @@ Device Fingerprint é um identificador que atua no processamento de um pagamento
 
 Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
 
 Para configurar o Device Fingerprint da Cybersource IO, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-decidir-gateway.md b/docs/tutorials/pt/setting-up-decidir-gateway.md
index a3c4cce76..71faaa5ad 100644
--- a/docs/tutorials/pt/setting-up-decidir-gateway.md
+++ b/docs/tutorials/pt/setting-up-decidir-gateway.md
@@ -35,9 +35,7 @@ Para configurar a Decidir, siga os passos abaixo:
 13. No campo __Mudanca de Margem__, defina a margem percentual em que será permitida a alteração do valor do pagamento.
 14. Clique em __Salvar__.
 
-<div class="alert alert-warning">
-Atenção: em casos de contratação do antifraude <strong>CyberSource</strong>, recomendamos que a loja entre em contato com o time da própria CyberSource para saber os detalhes da configuração do Checkout. 
-</div>
+>⚠️ Atenção: em casos de contratação do antifraude **CyberSource**, recomendamos que a loja entre em contato com o time da própria CyberSource para saber os detalhes da configuração do Checkout.
 
 ## Configurar condição de pagamento
 Depois de seguir os passos indicados, a Decidir vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ela vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com Decidir). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
diff --git a/docs/tutorials/pt/setting-up-device-fingerprint-for-niubiz.md b/docs/tutorials/pt/setting-up-device-fingerprint-for-niubiz.md
index 02a2416bd..8f294c9e6 100644
--- a/docs/tutorials/pt/setting-up-device-fingerprint-for-niubiz.md
+++ b/docs/tutorials/pt/setting-up-device-fingerprint-for-niubiz.md
@@ -19,9 +19,7 @@ __Device Fingerprint__ é um identificador que atua no processamento de um pagam
 
 Por meio da coleta de dados não sensíveis, o Device Fingerprint identifica e analisa o nível de segurança do dispositivo utilizado para realizar a transação, bem como as transações que anteriormente foram realizadas com este mesmo dispositivo.
 
-<div class="alert alert-info">
-Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
-</div>
+>ℹ️ Cada loja deve ter somente um Device Fingerprint cadastrado. Verifique se você já efetuou o cadastro do Device Fingerprint em outro conector, antes de continuar os passos abaixo.
 
 Neste artigo, explicaremos como associar o recurso Device Fingerprint à afiliação Niubiz. 
 
@@ -29,9 +27,7 @@ Para isso, é necessário gerar um identificador via [Google Tag Manager](https:
 
 ### Crie o identificador
 
-<div class="alert alert-info">
-As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.
-</div>
+>ℹ️ As instruções dessa etapa do artigo são realizadas em um ambiente externo. Desse modo, podem estar desatualizadas.
 
 Antes de qualquer coisa, você precisa criar o identificador.
 
@@ -104,9 +100,7 @@ Dito isso, confira as instruções:
 
 Desse modo, o Google Tag Manager criará o identificador. 
 
-<div class="alert alert-warning">
-Anote o ID em um local que você não o perca.
-</div>
+>⚠️ Anote o ID em um local que você não o perca.
 
 ## Configuração no Admin VTEX
 
diff --git a/docs/tutorials/pt/setting-up-firstdata-acquirer.md b/docs/tutorials/pt/setting-up-firstdata-acquirer.md
index abf0225d5..ef7726fc8 100644
--- a/docs/tutorials/pt/setting-up-firstdata-acquirer.md
+++ b/docs/tutorials/pt/setting-up-firstdata-acquirer.md
@@ -15,7 +15,7 @@ legacySlug: configurar-adquirente-firstdata
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Na VTEX, é possível realizar a integração com a FirstData. Com este provedor, sua loja pode realizar vendas por meio de cartões de crédito, débito e Plan Ahora (sistema de pagamento argentino).
 
diff --git a/docs/tutorials/pt/setting-up-future-inventory.md b/docs/tutorials/pt/setting-up-future-inventory.md
index 26b9f779b..36aa7c225 100644
--- a/docs/tutorials/pt/setting-up-future-inventory.md
+++ b/docs/tutorials/pt/setting-up-future-inventory.md
@@ -15,17 +15,13 @@ legacySlug: configurar-estoque-futuro
 subcategory: 32vrn4K2ZscjUaIBe6w5fm
 ---
 
-<div class="alert alert-info">
-<p>Essa funcionalidade está em fase closed Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase closed Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Para algumas operações de e-commerce, é útil ter a capacidade de vender um item que não esteja disponível para pronta entrega, mas que tenha data prevista de chegada ao estoque. A feature de __Estoque Futuro__ permite exatamente isso.
 
 ## Como funciona o Estoque Futuro
 
-<div class="alert alert-warning">
-Atualmente a configuração de Estoque Futuro está disponível somente <a target="_blank" href="https://developers.vtex.com/reference/inventory#savesupplylot">via API</a>.
-</div>
+>⚠️ Atualmente a configuração de Estoque Futuro está disponível somente <a target="_blank" href="https://developers.vtex.com/reference/inventory#savesupplylot">via API</a>.
 
 A API de Estoque Futuro permite cadastrar um __Lote de Abastecimento__. Esse lote representa o estoque futuro e carrega duas informações principais:
 - Quantidade de itens.
@@ -37,8 +33,7 @@ Neste caso, compras desses SKUs irão consumir os itens disponíveis no lote de
 
 >Tempo final de entrega = SLA de entrega + prazo de recebimento do lote de abastecimento
 
-<div class="alert alert-info">
-Caso a data do recebimento seja anterior à data do cálculo do frete, o tempo adicional será 0 (zero), já que - neste caso - o lote de abastecimento já foi recebido.</div>
+>ℹ️ Caso a data do recebimento seja anterior à data do cálculo do frete, o tempo adicional será 0 (zero), já que - neste caso - o lote de abastecimento já foi recebido.
 
 Veja a documentação do endpoint usado para salvar um Estoque Futuro:
 [Save Supply Lot](https://developers.vtex.com/reference/inventory#savesupplylot)
@@ -58,9 +53,7 @@ Ao usar a API de Estoque Futuro, fique atento às seguintes restrições:
 
 É possível transferir inventário de um lote de abastecimento para o estoque de pronta entrega. Essa transferência faz com que os itens passem a ser considerados imediatamente disponíveis. Com isso, deixa de haver adição de prazo ao tempo de entrega para eles.
 
-<div class="alert alert-info">
-A transferência para pronta entrega libera espaço para o cadastro de um novo lote. Ou seja, se sua loja tem 10 lotes cadastrados (limite permitido) e transfere 2 deles para pronta entrega, você passa a ter 8 lotes cadastrados e dois espaços disponíveis.
-</div>
+>ℹ️ A transferência para pronta entrega libera espaço para o cadastro de um novo lote. Ou seja, se sua loja tem 10 lotes cadastrados (limite permitido) e transfere 2 deles para pronta entrega, você passa a ter 8 lotes cadastrados e dois espaços disponíveis.
 
 Veja a documentação do endpoint usado para transferir um Estoque Futuro para pronta entrega:
 [Transfer Supply Lot](https://developers.vtex.com/reference/inventory#transfersupplylot)
diff --git a/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md b/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md
index 9f40a9f12..7bf03a421 100644
--- a/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md
+++ b/docs/tutorials/pt/setting-up-itau-registered-ticket-itau-registrado.md
@@ -15,7 +15,7 @@ legacySlug: configurar-boleto-registrado-itau-itau-registrado
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Para configurar o boleto registrado do Itaú, você pode escolher entre dois conectores diferentes: o __Boleto Itaú__ (também conhecido como __Itaú Registrado__ e que você vai aprender a configurar neste artigo) ou o [ItauShopline](https://help.vtex.com/pt/tutorial/configurar-boleto-registrado-itau--3TqzCHPU7KIYGsOKuUeQcq). No caso do __Boleto Itaú__, a geração do boleto é feita de forma transparente (sem redirecionamento para o site do Itaú), mas a conciliação é feita através de arquivos.
 
diff --git a/docs/tutorials/pt/setting-up-itau-registered-ticket.md b/docs/tutorials/pt/setting-up-itau-registered-ticket.md
index 780d6b928..a745688f2 100644
--- a/docs/tutorials/pt/setting-up-itau-registered-ticket.md
+++ b/docs/tutorials/pt/setting-up-itau-registered-ticket.md
@@ -15,7 +15,7 @@ legacySlug: configurar-boleto-registrado-itau
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Para configurar o boleto registrado do Itaú, você pode escolher entre dois conectores diferentes: o __ItauShopline__ (que você vai aprender a configurar neste artigo) ou o [Boleto Itaú (Itaú Registrado)](/pt/tutorial/configurar-boleto-registrado-itau-itau-registrado). No caso do __ItauShopline__, ele faz um redirecionamento para o site do Itaú e a conciliação do boleto é feita automaticamente.
 
diff --git a/docs/tutorials/pt/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md b/docs/tutorials/pt/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
index c146358b6..9de9280ac 100644
--- a/docs/tutorials/pt/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
+++ b/docs/tutorials/pt/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method.md
@@ -25,9 +25,7 @@ Para cada um desses métodos de pagamento, existem diferentes requisitos de conf
     - __Klarna__: é necessário [configurar a afiliação Klarna](/pt/tutorial/setting-up-klarna-pay-now-y-klarna-pay-later-as-payment-method#configurar-afiliação-klarna) e instalar o app _vtexdemoemea.klarna@2.0.9_ (ou versão superior) em sua loja. Saiba mais como instalar o aplicativo em [Installing an app](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-installing-an-app).
     - __Adyen__: é necessário [configurar a afiliação Adyen](https://help.vtex.com/es/tutorial/how-to-configure-the-adyen-gateway-on-vtex--tutorials_2337). Para completar esta configuração, solicite à Adyen para ativar o campo __Live Endpoint URL Prefix__ em sua loja e preencha-o de acordo com as informações descritas [nesta documentação da Adyen](https://www.adyen.help/hc/en-us/articles/360014322079-How-can-I-find-the-endpoint-URL-for-my-LIVE-account-).
 
-<div class="alert alert-warning">
-Klarna Pay Now e Klarna Pay Later estão habilitadas <b>apenas para o SmartCheckout V6</b>, e somente clientes do mercado europeu e estadunidense poderão utilizar suas soluções, por isso não são meios de pagamento aplicáveis para clientes brasileiros.
-</div>
+>⚠️ Klarna Pay Now e Klarna Pay Later estão habilitadas **apenas para o SmartCheckout V6**, e somente clientes do mercado europeu e estadunidense poderão utilizar suas soluções, por isso não são meios de pagamento aplicáveis para clientes brasileiros.
 
 ## Configurar afiliação Klarna
 
@@ -41,9 +39,7 @@ Para configurar a afiliação Klarna, siga o passo a passo abaixo:
 6. Preencha os campos __Application Key__ e __Application Token__ com informações da sua conta Klarna.
 7. Clique em __Salvar__.  
 
-<div class="alert alert-warning">
-  Se você estiver usando o conector Klarna em um ambiente de teste, o campo <b>Application Key</b> deve ser configurado como <i>playground.{Klarna User}</i>. Quando usado em ambiente de produção, o campo <b>Application Key</b> deve ser o <i>Klarna User</i>.
-</div>
+>⚠️ Se você estiver usando o conector Klarna em um ambiente de teste, o campo **Application Key** deve ser configurado como <i>playground.{Klarna User}</i>. Quando usado em ambiente de produção, o campo **Application Key** deve ser o <i>Klarna User</i>.
 
 ## Klarna Pay Now
 
diff --git a/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md b/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
index 2f0b3654b..554e3ddb2 100644
--- a/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
+++ b/docs/tutorials/pt/setting-up-lendico-boleto-in-installments-as-a-payment-method.md
@@ -45,9 +45,7 @@ Quando tiver as chaves em mãos, entre em contato novamente com a Provu e inform
 
 Por fim, a Provu lhe informará as suas credenciais - Key e Token -, necessárias para cadastrar finalizar o cadastro da afiliação.
 
-<div class="alert alert-danger">
-Guarde as credenciais da Provu em lugar seguro, em que não irá perdê-las. Os valores da Key e do Token são imprescindíveis para o cadastro da afiliação. 
-</div>
+>❗ Guarde as credenciais da Provu em lugar seguro, em que não irá perdê-las. Os valores da Key e do Token são imprescindíveis para o cadastro da afiliação.
 
 ### 2. Cadastro da afiliação
 
@@ -60,9 +58,7 @@ Com as credenciais da Provu em mãos, prossiga com as instruções a seguir:
 3. Digite o nome __Lendico__ na barra de busca e clique sobre o nome do provedor.
 4. Preencha o campo __Nome da Afiliação__.
 5. Logo abaixo, clique no botão __Live/Produção__ para ativar a afiliação.
-<div class="alert alert-warning">
-Confira se a área ao redor do botão mudou a cor para verde. Isso indica que a afiliação será ativada ao final da configuração. 
-</div>
+>⚠️ Confira se a área ao redor do botão mudou a cor para verde. Isso indica que a afiliação será ativada ao final da configuração.
 6. Do lado direito da tela, preencha os campos __Aplication Key__ e __Aplication Token__ com os respectivos dados fornecidos pela própria Lendico.
 7. Clique em __Salvar__.
 
diff --git a/docs/tutorials/pt/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md b/docs/tutorials/pt/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
index 9b132b4ad..9def13a6e 100644
--- a/docs/tutorials/pt/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
+++ b/docs/tutorials/pt/setting-up-mercado-pago-offline-and-wallet-as-payment-methods.md
@@ -41,9 +41,7 @@ Para configurar o Mercado Pago Offline, siga as instruções abaixo:
   <br>
   <li>Logo abaixo, clique no botão <b>Status</b> para ativar a regra.</li>
 <br>
-<div class="alert alert-info">
-  Não é necessário selecionar o campo <strong>Processar com afiliação</strong>, pois o subadquirente MercadoPagoV2 já vem configurado como afiliação padrão para o MercadoPagoOff.
-</div>
+>ℹ️ Não é necessário selecionar o campo **Processar com afiliação**, pois o subadquirente MercadoPagoV2 já vem configurado como afiliação padrão para o MercadoPagoOff.
 <br>
   <li>Se optar por utilizar o antifraude, habilite a opção <b>Usar Antifraude</b> e escolha uma das opções de antifraude disponíveis.</li>
   <br>
diff --git a/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md b/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md
index baf37d188..f43938d64 100644
--- a/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md
+++ b/docs/tutorials/pt/setting-up-mercadopagov1-sub-acquirer.md
@@ -15,13 +15,11 @@ legacySlug: configurar-o-subadquirente-mercadopagov1
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 No gateway da VTEX, você pode configurar o [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) MercadoPago para operar de várias formas. O __MercadoPagoV1__ permite que sua loja receba pagamentos com cartões de débito e crédito, além da [carteira digital](/pt/faq/o-que-e-uma-carteira-digital-e-wallet) Mercado Pago.
 
-<div class="alert alert-warning">
-A integração <strong>MercadoPagoV1</strong> não suporta pagamentos por boleto bancário.
-</div>
+>⚠️ A integração **MercadoPagoV1** não suporta pagamentos por boleto bancário.
 
 Para configurar o MercadoPagoV1, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
index ea7951823..f76aa4d03 100644
--- a/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/pt/setting-up-merchant-id-in-apple-pay.md
@@ -15,9 +15,7 @@ legacySlug: como-configurar-certificado-para-validar-merchant-do-apple-pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Este processo será mais simples assim que a Apple validar as integrações com a plataforma VTEX. Este artigo será, então, atualizado para atender ao novo cenário. 
-</div>
+>⚠️ Este processo será mais simples assim que a Apple validar as integrações com a plataforma VTEX. Este artigo será, então, atualizado para atender ao novo cenário.
 
 Para que sua loja receba pagamentos via __Apple Pay__, você precisar configurar o __Merchant ID__ na sua conta de desenvolvedor na Apple (`developer.apple.com`). 
 
@@ -93,9 +91,7 @@ Primeiro, você precisa validar cada uma das URLs desejadas. Uma vez que esse pa
 
 Por fim, é preciso importar esse arquivo para o sistema da VTEX por meio do Postman - ferramenta de gestão de [APIs](https://help.vtex.com/pt/tutorial/introduction-to-vtex-apis--3SjAqQ0BeUqu2ge8AiIkmW "APIs").
 
-<div class="alert alert-warning">
-<strong>Importante:</strong> essa validação só pode ser feita um domínio por vez. Isso significa que, caso sua loja use 10 domínios diferentes, o processo terá que ser repetido 10 vezes. 
-</div>
+>⚠️ **Importante:** essa validação só pode ser feita um domínio por vez. Isso significa que, caso sua loja use 10 domínios diferentes, o processo terá que ser repetido 10 vezes.
 
 Confira as instruções:
 
@@ -132,9 +128,7 @@ Agora, você deve gerar um certificado do Merchant ID, que será usado toda vez
 
 Para completar a ação, você vai precisar criar uma senha para proteger os dados exportados. 
 
-<div class="alert alert-info">
-Atenção: recomendamos que a senha seja fácil de lembrar, já que ela será informada no campo Apple Merchant Password no momento da configuração da afiliação de gateway na VTEX.
-</div>
+>ℹ️ Atenção: recomendamos que a senha seja fácil de lembrar, já que ela será informada no campo Apple Merchant Password no momento da configuração da afiliação de gateway na VTEX.
 
 1. Acesse o módulo __Certificates, Identifiers & Profilers__;
 2. No menu do lado esquerdo, clique em __Identifiers__;
diff --git a/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md b/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md
index 5b1ca9837..6671004a3 100644
--- a/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md
+++ b/docs/tutorials/pt/setting-up-mundipagg-fraud-prevention-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-mundipagg-fraud-prevention
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A Mundipagg oferece uma versão do seu [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com a funcionalidade de antifraude. O Mundipagg Fraud Prevention traz ainda mais segurança para o processamento de compras feitas com boletos, transferências bancárias e as principais bandeiras de cartão de crédito.
 
@@ -36,9 +36,7 @@ Para configurar o Mundipagg Fraud Prevention, siga os passos abaixo:
 13. Em __Usa Antifraude__, informe se você tem a funcionalidade antifraude contratada com a Mundipagg.
 14. Clique em __Salvar__.
 
-<div class="alert alert-info">
-Os passos indicados nos itens <strong>8</strong>, <strong>9</strong>, <strong>11</strong> e <strong>12</strong> devem ser preenchidos se você quiser oferecer boletos bancários como condição de pagamento na sua loja. 
-</div>
+>ℹ️ Os passos indicados nos itens **8**, **9**, **11** e **12** devem ser preenchidos se você quiser oferecer boletos bancários como condição de pagamento na sua loja.
 
 ## Configurar condição de pagamento
 Depois de seguir os passos indicados, o Mundipagg Fraud Prevention vai estar configurado na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ele vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com o Mundipagg Fraud Prevention). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
diff --git a/docs/tutorials/pt/setting-up-mundipagg-gateway.md b/docs/tutorials/pt/setting-up-mundipagg-gateway.md
index 072ca4288..adcc2b7a5 100644
--- a/docs/tutorials/pt/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/pt/setting-up-mundipagg-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-mundipagg
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A Mundipagg é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que processa pagamentos feitos com boletos, transferências bancárias e as principais bandeiras de cartão de crédito.
 
@@ -35,9 +35,7 @@ Para configurar a Mundipagg, siga os passos abaixo:
 12. No campo __Captura de segurança antecipada__, escolha em quanto tempo você deseja que a captura seja realizada (depois da aprovação da transação e da análise do antifraude). Você também pode desativar a função.
 13. Clique em __Salvar__.
 
-<div class="alert alert-info">
-Os passos indicados nos itens <strong>8</strong>, <strong>9</strong>, <strong>11</strong> e <strong>12</strong> devem ser preenchidos se você quiser oferecer boletos bancários como condição de pagamento na sua loja. 
-</div>
+>ℹ️ Os passos indicados nos itens **8**, **9**, **11** e **12** devem ser preenchidos se você quiser oferecer boletos bancários como condição de pagamento na sua loja.
 
 ## Configurar condição de pagamento
 Depois de seguir os passos indicados, a Mundipagg vai estar configurada na sua loja. Assim, quando você for cadastrar uma condição de pagamento, ela vai estar disponível no campo __Processar com a afiliação__ (desde que o meio de pagamento seja compatível com a Mundipagg). Para saber como definir condições de pagamento, acesse [este artigo do Help](/pt/tutorial/condicoes-de-pagamento).
diff --git a/docs/tutorials/pt/setting-up-my-account.md b/docs/tutorials/pt/setting-up-my-account.md
index 5def7a7e1..6433e4d6f 100644
--- a/docs/tutorials/pt/setting-up-my-account.md
+++ b/docs/tutorials/pt/setting-up-my-account.md
@@ -31,6 +31,4 @@ Para realizar as customizações na página, é necessário:
 2. Se autenticar através das opções __Receber código de acesso por e-mail__ ou __Entrar com e-mail e senha__
 3. Entrar na seção __Minha conta__, localizada no canto superior esquerdo da tela ao lado de __Meu carrinho__
 
-<div class="alert alert-info">
-Para lojas criadas a partir de 15 de maio de 2019, nenhum ajuste de customização é necessário, uma vez que o novo My Account já foi instalado nativamente na plataforma.
-</div>
+>ℹ️ Para lojas criadas a partir de 15 de maio de 2019, nenhum ajuste de customização é necessário, uma vez que o novo My Account já foi instalado nativamente na plataforma.
diff --git a/docs/tutorials/pt/setting-up-nethone-antifraud.md b/docs/tutorials/pt/setting-up-nethone-antifraud.md
index 9ff2aeb05..de15c67d4 100644
--- a/docs/tutorials/pt/setting-up-nethone-antifraud.md
+++ b/docs/tutorials/pt/setting-up-nethone-antifraud.md
@@ -17,9 +17,7 @@ subcategory:
 
 [Nethone](https://nethone.com/pt) é uma solução antifraude que através de inteligência artificial e machine learning identifica aspectos comportamentais específicos do usuário e minimiza os riscos e chances de fraude nas transações da sua loja.
 
-<div class="alert alert-warning">
-  A integração da Nethone, na VTEX, é feita via <b>Application Key (App Key)</b> e <b>Application Token (App Token)</b>. Você encontra essas informações no pacote de plugins que a Nethone enviará após a assinatura do contrato. Em caso de dúvidas, entre em contato com o suporte da Nethone.
-  </div>
+>⚠️ A integração da Nethone, na VTEX, é feita via **Application Key (App Key)** e **Application Token (App Token)**. Você encontra essas informações no pacote de plugins que a Nethone enviará após a assinatura do contrato. Em caso de dúvidas, entre em contato com o suporte da Nethone.
 
 Para configurar a Nethone, você precisará:
 
@@ -72,9 +70,7 @@ A próxima etapa de configuração da Nethone é feita via Javascript, por meio
 
 ## Configurar o Google Tag Manager
 
-<div class="alert alert-warning">
-  As configurações documentadas a seguir são realizadas em um sistema externo à VTEX, podendo ser descontinuadas sem aviso prévio.
-  </div>
+>⚠️ As configurações documentadas a seguir são realizadas em um sistema externo à VTEX, podendo ser descontinuadas sem aviso prévio.
 
 Com o número de identificação da sua conta instalado no checkout, realize as configurações abaixo para acompanhar as tentativas de compra que acontecerem em sua loja. 
 
diff --git a/docs/tutorials/pt/setting-up-nexxpago-gateway.md b/docs/tutorials/pt/setting-up-nexxpago-gateway.md
index a0c7984d5..72e02cd35 100644
--- a/docs/tutorials/pt/setting-up-nexxpago-gateway.md
+++ b/docs/tutorials/pt/setting-up-nexxpago-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-nexxpago
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A Nexxpago é uma empresa com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) que oferece diversas soluções de pagamento. A principal delas é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que permite o processamento de pagamentos por meio de boletos bancários e cartões de crédito.
 
diff --git a/docs/tutorials/pt/setting-up-nps-gateway.md b/docs/tutorials/pt/setting-up-nps-gateway.md
index aad40ad97..65636fbab 100644
--- a/docs/tutorials/pt/setting-up-nps-gateway.md
+++ b/docs/tutorials/pt/setting-up-nps-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-nps
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 O Ingenico ePayments (NPS) é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com forte atuação na América Latina e que permite que sua loja aceite diversas condições de pagamento.
 
diff --git a/docs/tutorials/pt/setting-up-offline-payment-conditions-using-mercadopago.md b/docs/tutorials/pt/setting-up-offline-payment-conditions-using-mercadopago.md
index 409929467..ce51f50de 100644
--- a/docs/tutorials/pt/setting-up-offline-payment-conditions-using-mercadopago.md
+++ b/docs/tutorials/pt/setting-up-offline-payment-conditions-using-mercadopago.md
@@ -15,9 +15,7 @@ legacySlug: configurar-condicoes-de-pagamento-offline-usando-mercadopago-latam
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Este artigo trata de configurações aplicáveis em lojas que atuam nos seguintes países da América Latina: <strong>Argentina</strong>, <strong>Chile</strong>, <strong>Colômbia</strong>, <strong>México</strong>, <strong>Peru</strong>, <strong>Uruguai</strong> e <strong>Venezuela</strong>.
-</div>
+>⚠️ Este artigo trata de configurações aplicáveis em lojas que atuam nos seguintes países da América Latina: **Argentina**, **Chile**, **Colômbia**, **México**, **Peru**, **Uruguai** e **Venezuela**.
 
 Você pode usar o Mercado Pago para oferecer condições de pagamento offline na sua loja. Para isso, você precisa primeiro cadastrar a afiliação de gateway [MercadoPagoV1](/pt/tutorial/configurar-o-subadquirente-mercadopagov1).
 
diff --git a/docs/tutorials/pt/setting-up-pagarmev2-gateway.md b/docs/tutorials/pt/setting-up-pagarmev2-gateway.md
index 65cbd8abf..93a096ed2 100644
--- a/docs/tutorials/pt/setting-up-pagarmev2-gateway.md
+++ b/docs/tutorials/pt/setting-up-pagarmev2-gateway.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Na VTEX, é possível processar pagamentos com o provedor PagarMe por meio das integrações V2 e V3.
 
-<div class="alert alert-warning">
-Caso deseje configurar a versão V3 da Pagarme em sua loja, acesse <a href="https://help.vtex.com/pt/tutorial/configurar-pagamento-com-pagarmev3--5PMavdamrVijwIrHas9ndE">Configurar pagamento com PagarMeV3</a>.
-</div>
+>⚠️ Caso deseje configurar a versão V3 da Pagarme em sua loja, acesse [Configurar pagamento com PagarMeV3](https://help.vtex.com/pt/tutorial/configurar-pagamento-com-pagarmev3--5PMavdamrVijwIrHas9ndE).
 
 Para configurar a PagarMeV2, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-pagbrasil-gateway.md b/docs/tutorials/pt/setting-up-pagbrasil-gateway.md
index 3c29c82ac..2f89dbd92 100644
--- a/docs/tutorials/pt/setting-up-pagbrasil-gateway.md
+++ b/docs/tutorials/pt/setting-up-pagbrasil-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-pagbrasil
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A PagBrasil é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) especializado em meios de pagamento brasileiros, principalmente cartões de crédito e débito, transferências online e boletos bancários.
 
diff --git a/docs/tutorials/pt/setting-up-paghiper-gateway.md b/docs/tutorials/pt/setting-up-paghiper-gateway.md
index 88fd6f2de..b0f780725 100644
--- a/docs/tutorials/pt/setting-up-paghiper-gateway.md
+++ b/docs/tutorials/pt/setting-up-paghiper-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-paghiper
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A PagHiper é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) especializado no processamento de compras realizadas por boletos bancários.
 
diff --git a/docs/tutorials/pt/setting-up-payment-with-paypal.md b/docs/tutorials/pt/setting-up-payment-with-paypal.md
index df02ddc04..31780e9c6 100644
--- a/docs/tutorials/pt/setting-up-payment-with-paypal.md
+++ b/docs/tutorials/pt/setting-up-payment-with-paypal.md
@@ -15,7 +15,7 @@ legacySlug: configurar-paypal
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 No gateway da VTEX, é possível configurar o subadquirente PayPal para receber seus pagamentos. Nesta modalidade, o seu cliente escolhe o __meio de pagamento__ PayPal e realiza sua autenticação no ambiente do PayPal.
 
diff --git a/docs/tutorials/pt/setting-up-paymentez-gateway.md b/docs/tutorials/pt/setting-up-paymentez-gateway.md
index d759ee1ca..4f2115ce3 100644
--- a/docs/tutorials/pt/setting-up-paymentez-gateway.md
+++ b/docs/tutorials/pt/setting-up-paymentez-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-paymentez
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A Paymentez é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que possui certificação [PCI](/pt/faq/o-que-e-o-pci-ssc) nível 2 e tem sua atuação concentrada na América Latina.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-alignet.md b/docs/tutorials/pt/setting-up-payments-with-alignet.md
index b4d24e85b..ac2bd469f 100644
--- a/docs/tutorials/pt/setting-up-payments-with-alignet.md
+++ b/docs/tutorials/pt/setting-up-payments-with-alignet.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagamentos-com-alignet
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Na plataforma VTEX, é possível configurar o [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) Alignet para receber pagamentos na sua loja. Nessa modalidade, o cliente escolhe o __meio de pagamento__ Alignet e é redirecionado para autenticação no ambiente do subadquirente.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-apple-pay.md b/docs/tutorials/pt/setting-up-payments-with-apple-pay.md
index 6125e57cf..0330aebcd 100644
--- a/docs/tutorials/pt/setting-up-payments-with-apple-pay.md
+++ b/docs/tutorials/pt/setting-up-payments-with-apple-pay.md
@@ -20,9 +20,7 @@ Seus clientes podem fazer compras usando o Apple Pay, a [carteira digital](/pt/f
 - Ter conta em `developer.apple.com`.
 - Ter contrato com um gateway que processe pagamentos com Apple Pay.
 
-<div class="alert alert-warning">
-  O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse <a href="https://support.apple.com/pt-br/HT208531">Dispositivos compatíveis com o Apple Pay</a>.
-</div>
+>⚠️ O Apple Pay funciona atualmente somente nos sistemas operacionais MacOs e IOS, e no navegador Safari. Para maiores informações, acesse [Dispositivos compatíveis com o Apple Pay](https://support.apple.com/pt-br/HT208531).
 
 Com os requisitos cumpridos, basta seguir os passos abaixo para oferecer essa condição de pagamento na sua loja:
 
@@ -32,9 +30,7 @@ Primeiramente é necessário configurar no Admin de sua loja um provedor que pro
 
 Para conferir todas as opções de provedores disponíveis para este meio de pagamento, acesse a lista conforme descrito no Passo 5 da seção [Configurar pagamento com Apple Pay](#configurar-pagamento-com-apple-pay).
 
-<div class="alert alert-warning">
-  Antes de iniciar a configuração do provedor é necessário <a href="registrar o Merchant ID no Apple Pay">registrar o Merchant ID no Apple Pay</a>.
-</div>
+>⚠️ Antes de iniciar a configuração do provedor é necessário [registrar o Merchant ID no Apple Pay](registrar o Merchant ID no Apple Pay).
 
 ## Configurar pagamento com Apple Pay
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md b/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md
index ed105d62b..deedc81e2 100644
--- a/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md
+++ b/docs/tutorials/pt/setting-up-payments-with-cieloecommerce.md
@@ -47,9 +47,7 @@ Para configurar a CieloEcommerce, siga os passos abaixo:
 
 <blockquote><ui>14. Em <b>AntifraudProvider</b>, selecione o provedor de antifraude que deseja utilizar com o CieloEcommerce.</ui>
 
-<blockquote><ui><div class="alert alert-warning">
-  Verifique com a Cielo se as opções de antifraude no CieloEcommerce já estão disponíveis para uso. Caso ainda estejam em desenvolvimento, ambos os campos descritos no passo 15 deverão ser deixados em branco. Para mais informações sobre como utilizar opções de antifraude em sua loja, acesse <a href="https://help.vtex.com/pt/tutorial/como-configurar-antifraude">Configurar o antifraude</a>.
-  </div></blockquote>
+<blockquote><ui>>⚠️ Verifique com a Cielo se as opções de antifraude no CieloEcommerce já estão disponíveis para uso. Caso ainda estejam em desenvolvimento, ambos os campos descritos no passo 15 deverão ser deixados em branco. Para mais informações sobre como utilizar opções de antifraude em sua loja, acesse [Configurar o antifraude](https://help.vtex.com/pt/tutorial/como-configurar-antifraude).</blockquote>
 <br>
 <blockquote><ui>15. Em <b>Antifraud</b> e <b>AntifraudSequenceCriteria</b>, selecione as opções conforme informações do antifraude CieloEcommerce.</ui>
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-credimarcas.md b/docs/tutorials/pt/setting-up-payments-with-credimarcas.md
index c0ac99ac0..96c7851dc 100644
--- a/docs/tutorials/pt/setting-up-payments-with-credimarcas.md
+++ b/docs/tutorials/pt/setting-up-payments-with-credimarcas.md
@@ -39,9 +39,7 @@ Para configurar o provedor Credimarcas, siga os passos abaixo:
 
 ## Configurar Promissória
 
-<div class="alert alert-warning">
-  <p>Caso ainda não tenha configurado a promissória como método de pagamento em outros conectores de sua loja, acesse <a href="https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ">Configurar pagamentos com Promissória</a>.</p>
-</div>
+>⚠️ Caso ainda não tenha configurado a promissória como método de pagamento em outros conectores de sua loja, acesse [Configurar pagamentos com Promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ).
 
 Para utilizar a Credimarcas com promissórias, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-itau-rede.md b/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
index cd7732fea..c9f8f5f08 100644
--- a/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
+++ b/docs/tutorials/pt/setting-up-payments-with-itau-rede.md
@@ -25,9 +25,7 @@ Para utilizar o Itaú Rede, é necessário:
 
 ## Obter credenciais no ambiente Userede
 
-<div class="alert alert-warning">
-As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta no Itaú Rede para informações atualizadas.
-</div>
+>⚠️ As configurações realizadas em um ambiente externo à VTEX podem ser descontinuadas ou modificadas sem aviso prévio. Consulte sua conta no Itaú Rede para informações atualizadas.
 
 Para obter as credenciais __Chave de aplicação__ e __Token de aplicação__ necessárias para configurar o Itaú Rede na VTEX, siga os passos abaixo:
 
@@ -59,9 +57,7 @@ Para obter as credenciais __Chave de aplicação__ e __Token de aplicação__ ne
 
 <blockquote><ui>8. Após a criação da nova chave, clique em <b>copiar</b> e preserve a informação em um local seguro. Esta chave deverá ser utilizada no campo <b>Token de aplicação</b> na seção <a href="#configurar-itau-rede-na-vtex">Configurar Itaú Rede na VTEX</a>.</ui>
 
-<blockquote><ui><div class="alert alert-warning">
-Após uma chave de integração ser criada no ambiente Rede, não é possível acessá-la novamente em outros locais. Registre a informação da chave em um local protegido, e em caso de perda, repita o processo para gerar uma nova chave.
-  </div></ui></blockquote>
+<blockquote><ui>>⚠️ Após uma chave de integração ser criada no ambiente Rede, não é possível acessá-la novamente em outros locais. Registre a informação da chave em um local protegido, e em caso de perda, repita o processo para gerar uma nova chave.</ui></blockquote>
 
 ## Configurar Itaú Rede na VTEX
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-iugu.md b/docs/tutorials/pt/setting-up-payments-with-iugu.md
index 6a2dffa9a..7c0faf495 100644
--- a/docs/tutorials/pt/setting-up-payments-with-iugu.md
+++ b/docs/tutorials/pt/setting-up-payments-with-iugu.md
@@ -44,9 +44,7 @@ Para processar os meios de pagamento cartão de crédito, pix e boleto bancário
 
 Depois de seguir os passos indicados, o provedor iugu pode demorar até 10 minutos para aparecer no Checkout da sua loja como uma opção de pagamento.
 
-<div class="alert alert-warning">
-  Antes de realizar transações por cartão de crédito, PIX ou Boleto bancário com a iugu em sua loja, verifique se esses meios de pagamento já estão habilitados em <a href="https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento">sua área do cliente no portal da iugu</a>.
-  </div>
+>⚠️ Antes de realizar transações por cartão de crédito, PIX ou Boleto bancário com a iugu em sua loja, verifique se esses meios de pagamento já estão habilitados em [sua área do cliente no portal da iugu](https://dev.iugu.com/docs/configurando-conector-iugu-na-vtex#configurando-condi%C3%A7%C3%B5es-de-pagamento).
 
 ## Configurar split de pagamento no marketplace com iugu
 
@@ -64,15 +62,11 @@ Para habilitar o split de recebíveis com a iugu em sua loja, siga os passos aba
 4. Em __Controle de pagamento__, selecione a opção __Ativar split de recebíveis e enviar recebedores de pagamento__ e indique o __Responsável pelas tarifas de processamento de pagamentos__ e __Responsável pelos estornos__ (marketplace, sellers ou marketplaces e sellers).
 5. Clique em `Salvar`.
 
-<div class="alert alert-warning">
-  A opção de split de recebíveis não está disponível para utilização em ambiente de teste.
-  </div>
+>⚠️ A opção de split de recebíveis não está disponível para utilização em ambiente de teste.
 
 Depois de seguir os passos indicados, a funcionalidade de split de recebíveis com o provedor iugu pode demorar até 10 minutos para ser ativada em sua loja.
 
-<div class="alert alert-warning">
-  Para definir as comissões específicas de cada seller em sua loja, acesse <b>Marketplace > Sellers> Gerenciamento</b> no Admin VTEX, selecione o seller desejado e insira os valores de comissão em <b>Comissões</b>.
-  </div>
+>⚠️ Para definir as comissões específicas de cada seller em sua loja, acesse **Marketplace > Sellers> Gerenciamento** no Admin VTEX, selecione o seller desejado e insira os valores de comissão em **Comissões**.
 
 ## Configurar recorrência com a iugu
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-koin.md b/docs/tutorials/pt/setting-up-payments-with-koin.md
index 20fcfcfad..e097b4172 100644
--- a/docs/tutorials/pt/setting-up-payments-with-koin.md
+++ b/docs/tutorials/pt/setting-up-payments-with-koin.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagamentos-com-koin
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Você pode configurar a Koin para receber pagamentos na sua loja. Nesta modalidade, seu cliente escolhe o __meio de pagamento__ Koin Pós-pago para efetuar a compra.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md b/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md
index b14c89c2d..d90cdcab6 100644
--- a/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md
+++ b/docs/tutorials/pt/setting-up-payments-with-mercado-pago.md
@@ -39,9 +39,7 @@ Abaixo estão as configurações para o conector __Mercado Pago__.
 12. No campo __Tipo de estorno__, escolha entre o processo automático ou a solicitação manual (neste caso, o MercadoPago vai enviar um e-mail avisando do estorno pendente).
 13. Clique em __Salvar__.  
 
-<div class="alert alert-warning">
-O passo indicado no item <strong>11</strong> é realizado em ambiente externo à VTEX. Portanto, o processo indicado pode ser atualizado sem aviso prévio. 
-</div>
+>⚠️ O passo indicado no item **11** é realizado em ambiente externo à VTEX. Portanto, o processo indicado pode ser atualizado sem aviso prévio.
 
 ## Configurar condição de pagamento MercadoPago
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações > Condições de pagamento**, ou digite **Configurações** na barra de busca no topo da página.
diff --git a/docs/tutorials/pt/setting-up-payments-with-notes-payable.md b/docs/tutorials/pt/setting-up-payments-with-notes-payable.md
index 28fd4be5f..7e9eec165 100644
--- a/docs/tutorials/pt/setting-up-payments-with-notes-payable.md
+++ b/docs/tutorials/pt/setting-up-payments-with-notes-payable.md
@@ -25,9 +25,7 @@ Na VTEX, sua loja pode receber pagamentos por meio de promissórias. Para isso,
 
 Para configurar uma afiliação de gateway, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
-<div class="alert alert-warning">
-Verifique se a afiliação de gateway desejada suporta o processamento de pagamento por promissória.
-</div>
+>⚠️ Verifique se a afiliação de gateway desejada suporta o processamento de pagamento por promissória.
 
 ## Configurar Promissória
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-nuvei.md b/docs/tutorials/pt/setting-up-payments-with-nuvei.md
index 91c44aa8d..24ff6659e 100644
--- a/docs/tutorials/pt/setting-up-payments-with-nuvei.md
+++ b/docs/tutorials/pt/setting-up-payments-with-nuvei.md
@@ -38,17 +38,13 @@ Para utilizar o Nuvei, siga os passos abaixo:
 
 <blockquote><ui>7. Para preencher os campos <b>Merchant Id</b>, <b>Merchant Site Id</b> e <b>Client Secret</b> (Secret Key), acesse as informações disponíveis em <b>Settings > My Integration Settings</b> dentro do painel de controle de sua conta no ambiente Nuvei.</ui>
 
-<blockquote><ui><div class="alert alert-warning">
- A Nuvei possui credenciais (Merchant Id, Merchant Site Id e Client Secret) específicas para cada tipo de ambiente. Acesse os ambientes de teste <a href="sandbox.nuvei.com">(Integration)</a> e <a href="cpanel.nuvei.com">Live</a> para identificar as informações relativas a cada um deles.
-  </div></blockquote>
+<blockquote><ui>>⚠️ A Nuvei possui credenciais (Merchant Id, Merchant Site Id e Client Secret) específicas para cada tipo de ambiente. Acesse os ambientes de teste [(Integration)](sandbox.nuvei.com) e [Live](cpanel.nuvei.com) para identificar as informações relativas a cada um deles.</blockquote>
 <br>  
 <blockquote><ui>8. Em <b>Environment</b>, selecione se deseja configurar o provedor Nuvei no ambiente <b>Integration</b> ou <b>Live</b>.</ui>
 
 <blockquote><ui>9. Em <b>Test 3ds challenge Integration only</b>, caso você tenha selecionado o ambiente de teste (<b>Integration</b>) é possível realizar testes de segurança 3DS por meio das opções <b>Force 3ds Challenge</b>, <b>Force 3ds Frictionless</b> ou <b>User cardHolder name</b>. Para mais informações sobre os testes, acesse a documentação <a href="https://docs.nuvei.com/documentation/integration/testing/testing-cards/?highlight=test%20cards#3d-secure-v2-test-scenarios">Nuvei</a>.</ui>
 
- <blockquote><ui><div class="alert alert-warning">
-   Sempre que o <b>Environment</b> do provedor for configurado como <b>Live</b>, a opção selecionada para o campo <b>Test 3ds challenge Integration only</b> deve ser <b>User cardHolder name</b>.
-  </div></blockquote>
+ <blockquote><ui>>⚠️ Sempre que o **Environment** do provedor for configurado como **Live**, a opção selecionada para o campo **Test 3ds challenge Integration only** deve ser **User cardHolder name**.</blockquote>
 <br>  
 <blockquote><ui>10. Clique em <b>Salvar</b>.</ui>
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pagosweb.md b/docs/tutorials/pt/setting-up-payments-with-pagosweb.md
index ce54cc06f..edf9f5f91 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pagosweb.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pagosweb.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagamentos-com-pagosweb
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Você pode configurar o PagosWEB para receber pagamentos na sua loja. Nesta modalidade, seu cliente escolhe o __meio de pagamento__ PagosWEB para efetuar a compra.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-payclub.md b/docs/tutorials/pt/setting-up-payments-with-payclub.md
index 42a6b4d53..cde9f375e 100644
--- a/docs/tutorials/pt/setting-up-payments-with-payclub.md
+++ b/docs/tutorials/pt/setting-up-payments-with-payclub.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagamentos-com-payclub
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Você pode configurar o [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) PayClub para receber pagamentos na sua loja. Nesta modalidade, seu cliente escolhe o __meio de pagamento__ PayClub e realiza a autenticação no ambiente externo da solução de pagamentos.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-promissory.md b/docs/tutorials/pt/setting-up-payments-with-promissory.md
index 6404f99b4..d17d1807c 100644
--- a/docs/tutorials/pt/setting-up-payments-with-promissory.md
+++ b/docs/tutorials/pt/setting-up-payments-with-promissory.md
@@ -25,9 +25,7 @@ Na VTEX, sua loja pode receber pagamentos por meio de promissórias. Para isso,
 
 Para configurar uma afiliação de gateway, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444#).
 
-<div class="alert alert-warning">
-Verifique se a afiliação de gateway desejada suporta o processamento de pagamento por promissória.
-</div>
+>⚠️ Verifique se a afiliação de gateway desejada suporta o processamento de pagamento por promissória.
 
 ## Configurar Promissória
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-pse.md b/docs/tutorials/pt/setting-up-payments-with-pse.md
index 4f95673eb..cda1bed7f 100644
--- a/docs/tutorials/pt/setting-up-payments-with-pse.md
+++ b/docs/tutorials/pt/setting-up-payments-with-pse.md
@@ -21,8 +21,7 @@ Para habilitar o PSE em sua loja são necessárias as seguintes ações:
 - [Instalar e configurar o aplicativo Banks for PSE](#instalando-o-banks-for-pse-app).
 - [Configurar o PSE como condição de pagamento](#configurando-a-condição-de-pagamento-pse).
 
-<div class="alert alert-warning">
-Para configurar o PSE app em sua loja, você deve ter permissão para acessar o módulo de Pagamentos. Caso ainda não tenha este acesso, solicite-o através do <a href="https://help.vtex.com/support">VTEX Support</a>.</div>
+>⚠️ Para configurar o PSE app em sua loja, você deve ter permissão para acessar o módulo de Pagamentos. Caso ainda não tenha este acesso, solicite-o através do [VTEX Support](https://help.vtex.com/support).
 
 ## Instalando o Banks for PSE App
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-stelo.md b/docs/tutorials/pt/setting-up-payments-with-stelo.md
index d275af05a..76fbe7556 100644
--- a/docs/tutorials/pt/setting-up-payments-with-stelo.md
+++ b/docs/tutorials/pt/setting-up-payments-with-stelo.md
@@ -15,7 +15,7 @@ legacySlug: configurar-pagamentos-com-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Além de um [subadquirente](/pt/tutorial/configurar-subadquirente-stelo) para processar transações realizadas com diversas condições de pagamento, a Stelo também oferece um serviço de [carteira digital](/pt/faq/o-que-e-uma-carteira-digital-e-wallet). Seu cliente escolhe pagar com ela e é redirecionado para autenticação no ambiente da Stelo.
 
diff --git a/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md b/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md
index 3abd072ae..b1596ab14 100644
--- a/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md
+++ b/docs/tutorials/pt/setting-up-payments-with-store-card-cobranded.md
@@ -28,9 +28,7 @@ A primeira estapa de configuração será a de criação do pagamento customizad
 6. Em __Bandeira do cartão__, escolha a bandeira à qual o cartão da sua loja está vinculado. Atualmente, as bandeiras possíveis são: American Express, Cabal, Diners, Elo, Mastercard e Visa.
 7. Em __Intervalos de BIN (opcional)__, você pode informar uma faixa de BINs (inserindo o primeiro e o último código da sequência, separados por hífen) ou várias (separando cada faixa por vírgula e sem espaços).
 
-<div class="alert alert-warning">
-  Quando o cliente inserir um número bin fora da faixa especificada neste campo, a seguinte mensagem será exibida "Confira o número do seu cartão. Não conseguimos confirmar se o número digitado está correto". Caso não haja erro no número digitado, ele poderá clicar em "SIM, O NÚMERO ESTÁ CORRETO" para continuar a finalização do pedido.
-</div>
+>⚠️ Quando o cliente inserir um número bin fora da faixa especificada neste campo, a seguinte mensagem será exibida "Confira o número do seu cartão. Não conseguimos confirmar se o número digitado está correto". Caso não haja erro no número digitado, ele poderá clicar em "SIM, O NÚMERO ESTÁ CORRETO" para continuar a finalização do pedido.
 
 <blockquote><ui>8. No campo <b>Código de Pagamento em Adquirente (opcional)</b>, indique o código para ser enviado e processado pelo adquirente contratado por você.</ui>
 
@@ -41,9 +39,7 @@ A primeira estapa de configuração será a de criação do pagamento customizad
 ## Configurar condição de pagamento
 Após configurar o cartão, será necessária a configuração da condição de pagamento.
 
-<div class="alert alert-warning">
-  Caso o conector a ser escolhido (no <b>Passo 8.</b>) ainda não estiver cadastrado em sua loja, será exibida a mensagem “(Configurar)” após o nome do conector. Nesta situação, escolha outro conector disponível ou realize o seu cadastro. Para saber mais, acesse <a href="https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Cadastrar afiliações de gateway</a>.
-</div>
+>⚠️ Caso o conector a ser escolhido (no **Passo 8.**) ainda não estiver cadastrado em sua loja, será exibida a mensagem “(Configurar)” após o nome do conector. Nesta situação, escolha outro conector disponível ou realize o seu cadastro. Para saber mais, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de Pagamentos__, clique no botão __“+”__.
diff --git a/docs/tutorials/pt/setting-up-paypal-plus.md b/docs/tutorials/pt/setting-up-paypal-plus.md
index 645486355..0075f7e8c 100644
--- a/docs/tutorials/pt/setting-up-paypal-plus.md
+++ b/docs/tutorials/pt/setting-up-paypal-plus.md
@@ -15,7 +15,7 @@ legacySlug: configurar-paypal-plus-paypal-transparente
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 No gateway da VTEX, é possível configurar o subadquirente PayPal Plus, o checkout transparente da PayPal. Nesta modalidade, basta o cliente inserir as informações do cartão de crédito e finalizar a compra normalmente. O pagamento é feito diretamente em seu site, sem redirecionar seus clientes. 
 
diff --git a/docs/tutorials/pt/setting-up-payu-gateway.md b/docs/tutorials/pt/setting-up-payu-gateway.md
index 9e0b3698d..97a7ac1b0 100644
--- a/docs/tutorials/pt/setting-up-payu-gateway.md
+++ b/docs/tutorials/pt/setting-up-payu-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-payu
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A PayU é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que oferece uma série de soluções para facilitar (e deixar mais seguras) as transações realizadas na sua loja. Com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc), essa solução é exclusiva para Argentina, Brasil, Chile, Colômbia, México, Panamá e Peru.
 
diff --git a/docs/tutorials/pt/setting-up-payu-global-gateway.md b/docs/tutorials/pt/setting-up-payu-global-gateway.md
index 481cebd50..19fc19f3b 100644
--- a/docs/tutorials/pt/setting-up-payu-global-gateway.md
+++ b/docs/tutorials/pt/setting-up-payu-global-gateway.md
@@ -17,8 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 A PayU Global é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) que oferece uma série de soluções para facilitar (e deixar mais seguras) as transações realizadas na sua loja. Com certificação [PCI](/pt/faq/o-que-e-o-pci-ssc), essa solução é exclusiva para lojas da Romênia.
 
-<div class="alert alert-info"> Atenção: atualmente, a VTEX só suporta as versões 1.0.0 e 1.0.1 do PaymentsOS. 
-</div>
+>ℹ️ Atenção: atualmente, a VTEX só suporta as versões 1.0.0 e 1.0.1 do PaymentsOS.
 
 Para configurar a PayU Global, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-payzen-gateway.md b/docs/tutorials/pt/setting-up-payzen-gateway.md
index 9ec2feb44..f4aaf4a02 100644
--- a/docs/tutorials/pt/setting-up-payzen-gateway.md
+++ b/docs/tutorials/pt/setting-up-payzen-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-o-gateway-payzen
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Na VTEX, você pode configurar o [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) PayZen na sua loja. De fácil integração, ele segue os padrões de segurança definidos pelo [Pagamentos](/pt/faq/o-que-e-o-pci-ssc).
 
diff --git a/docs/tutorials/pt/setting-up-pix-as-a-payment-method.md b/docs/tutorials/pt/setting-up-pix-as-a-payment-method.md
index 987886bb5..6868b33f8 100644
--- a/docs/tutorials/pt/setting-up-pix-as-a-payment-method.md
+++ b/docs/tutorials/pt/setting-up-pix-as-a-payment-method.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 O [Pix](https://vtex.com/pt-br/blog/produto/pix-no-e-commerce/ "Pix") é um meio de pagamento eletrônico específico do Brasil. Por meio dele, é possível o envio e o recebimento instantâneo de pagamentos entre diferentes bancos e instituições financeiras, 24h por dia, sete dias por semana.
 
-<div class="alert alert-warning">
-O Pix <strong>não é</strong> um meio de pagamento suportado por clientes marketplace que realizem split de transação.
-</div>
+>⚠️ O Pix **não é** um meio de pagamento suportado por clientes marketplace que realizem split de transação.
 
 Para maiores informações sobre o PIX, acesse o [PIX FAQ](https://help.vtex.com/pt/tutorial/pix-faq--3lx7zCU2lQroTEBCYKYbo3 "o FAQ sobre as principais dúvidas relacionadas ao Pix"). 
 
@@ -27,9 +25,7 @@ Para maiores informações sobre o PIX, acesse o [PIX FAQ](https://help.vtex.com
 
 Para receber pagamentos por meio do PIX na VTEX, você precisa ter cadastrado uma afiliação de gateway capaz de processar esse meio de pagamento e realizar a configuração descrita abaixo:
 
-<div class="alert alert-warning">
-  Caso o conector a ser escolhido (no <b>Passo 8.</b>) ainda não estiver cadastrado em sua loja, será exibida a mensagem “(Configurar)” após o nome do conector. Nesta situação, escolha outro conector disponível ou realize o seu cadastro. Para saber mais, acesse <a href="https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#">Cadastrar afiliações de gateway</a>.
-</div>
+>⚠️ Caso o conector a ser escolhido (no **Passo 8.**) ainda não estiver cadastrado em sua loja, será exibida a mensagem “(Configurar)” após o nome do conector. Nesta situação, escolha outro conector disponível ou realize o seu cadastro. Para saber mais, acesse [Cadastrar afiliações de gateway](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444?&utm_source=autocomplete#).
 
 1. No Admin VTEX, acesse **Configurações da loja** > **Pagamentos** > **Configurações**, ou digite **Configurações** na barra de busca no topo da página.
 2. Na aba __Condições de pagamento__, clique no botão __+__.
diff --git a/docs/tutorials/pt/setting-up-place2pay-gateway.md b/docs/tutorials/pt/setting-up-place2pay-gateway.md
index 942629e04..ec9e4fb4c 100644
--- a/docs/tutorials/pt/setting-up-place2pay-gateway.md
+++ b/docs/tutorials/pt/setting-up-place2pay-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-place2pay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 O Place2Pay é a versão com redirect do gateway PlaceToPay, que oferece soluções para lojas de grande e pequeno porte.
 
diff --git a/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md b/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md
index 93c780d5c..2955021ca 100644
--- a/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md
+++ b/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md
@@ -23,13 +23,9 @@ Para regionalizar os preços e disponibilidades dos SKUs, é necessário:
 2. [Sellers White Label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa#) realizem entregas de pedidos feitos em sua loja para determinadas faixas de CEP.
 3. A sessão do usuário navegando na loja contenha as informações sobre o seu CEP e país de origem.
 
-<div class="alert alert-info">
-Para usar essa feature é necessário que a loja tenha o sistema de Sessões (<a href="https://help.vtex.com/pt/tutorial/vtex-session-visao-geral-do-sistema-de-sessoes--6C4Edou6bYqqEAOCAg2MQQ#">VTEX Session</a>) instalado. O VTEX Session é nativo em todas as lojas e você pode confirmar a sua instalação pela presença dos cookies <code>vtex_session</code> e <code>vtex_segment</code> ao navegar na loja.
-</div>
+>ℹ️ Para usar essa feature é necessário que a loja tenha o sistema de Sessões ([VTEX Session](https://help.vtex.com/pt/tutorial/vtex-session-visao-geral-do-sistema-de-sessoes--6C4Edou6bYqqEAOCAg2MQQ#)) instalado. O VTEX Session é nativo em todas as lojas e você pode confirmar a sua instalação pela presença dos cookies `vtex_session` e `vtex_segment` ao navegar na loja.
 
-<div class="alert alert-warning">
-Em casos de <a href="https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#">Multilevel Omnichannel Inventory</a>, um marketplace (nível 1) não pode configurar exibição de preços e disponibilidade de produtos de Sellers White Label (nível 3) com a funcionalidade de regionalização.
-</div>
+>⚠️ Em casos de [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#), um marketplace (nível 1) não pode configurar exibição de preços e disponibilidade de produtos de Sellers White Label (nível 3) com a funcionalidade de regionalização.
 
 <div class = "alert alert-info">
 A feature <b>Region</b> funciona tanto para lojas CMS Portal Legado quanto lojas desenvolvidas utilizando <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC">VTEX IO</a>, mas a funcionalidade <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a> é válida somente para lojas VTEX IO. Disso resulta que lojas com CMS Portal Legado possuem uma limitação na indexação de dados regionalizados e não é possível ordenar corretamente os sellers que atendem a vitrine de uma RegionId tomando por base a disponibilidade dos itens.
@@ -48,7 +44,5 @@ Para configurar a entrega, siga os passos abaixo:
 5. Cadastre um [estoque](https://help.vtex.com/pt/tutorial/gerenciar-estoque--tutorials_137#).
 6. [Adicione estoque aos SKUs](https://help.vtex.com/pt/tutorial/managing-stock-items) que serão entregues pela rota configurada.
 
-<div class="alert alert-info">
-Para um SKU aparecer como disponível para venda, é necessário que ele tenha estoque e preço associados a ele.
-</div>
+>ℹ️ Para um SKU aparecer como disponível para venda, é necessário que ele tenha estoque e preço associados a ele.
 
diff --git a/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md b/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
index bda4b0976..91c5627b0 100644
--- a/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
+++ b/docs/tutorials/pt/setting-up-price-tables-for-specific-users.md
@@ -21,9 +21,7 @@ Diferentemente das políticas comerciais, que também podem ser usadas para segm
 
 Por exemplo, digamos que você queira que os clientes de Minas Gerais vejam um preço diferente do que veem os clientes do Rio de Janeiro. Neste caso, você pode criar duas tabelas de preço diferentes, e associar a primeira aos clientes de Minas Gerais, e a segunda aos do Rio de Janeiro.
 
-<div class="alert alert-info">
-<p>Preços fixos ou regras de preço podem ser definidos para modificar o preço de um SKU em uma tabela de preço.</p>
-</div>
+>ℹ️ Preços fixos ou regras de preço podem ser definidos para modificar o preço de um SKU em uma tabela de preço.
 
 Isto permite ao lojista mais liberdade para lidar com informações contextuais de seus clientes.
 
@@ -63,10 +61,8 @@ Outra maneira de usar tabelas de preço é declarando-as diretamente no formulá
 10. Na linha da entidade alterada, clique no ícone disquete para publicar.
 11. Então, na mesma linha da entidade editada, clique no ícone setas para reindexá-la.
 
-<div class="alert alert-info">
-<p>Cada cliente pode ter no máximo 5 tabelas de preço atreladas a ele.
-Quando o cliente tiver mais de uma tabela de preço atrelada, o sistema irá seguir a ordem das tabelas de preço cadastradas para determinar o preço de cada SKU. Se o SKU não possui preço configurado na primeira tabela de preço, o sistema vai buscar na segunda em diante. Caso não haja preço configurado em nenhuma tabela atrelada ao cliente, o preço aplicado será o preço base.</p>
-</div>
+>ℹ️ Cada cliente pode ter no máximo 5 tabelas de preço atreladas a ele.
+> Quando o cliente tiver mais de uma tabela de preço atrelada, o sistema irá seguir a ordem das tabelas de preço cadastradas para determinar o preço de cada SKU. Se o SKU não possui preço configurado na primeira tabela de preço, o sistema vai buscar na segunda em diante. Caso não haja preço configurado em nenhuma tabela atrelada ao cliente, o preço aplicado será o preço base.
 
 Agora sua entidade de __Clientes__ tem um atributo `priceTables`, que pode ser populado diretamente na UI do Master Data ou por API.
 
@@ -88,9 +84,7 @@ Para atualizar o preço fixo em uma tabela específica, clique na coluna dessa t
 
 Para inserir e atualizar os preços de uma tabela específica por API, confira a [documentação da API de Pricing](https://developers.vtex.com/reference/prices-and-fixed-prices#createeditfixedpricesonapricetableortradepolicy).
 
-<div class="alert alert-info">
-<p>A tabela de preços tem prioridade sobre o preço da Política Comercial. Isso significa que, se determinada tabela de preços se aplicar ao contexto de um usuário, o preço definido nela será utilizado, mesmo que esse cliente esteja também no contexto de uma política comercial que defina um preço diferente.</p>
-</div>
+>ℹ️ A tabela de preços tem prioridade sobre o preço da Política Comercial. Isso significa que, se determinada tabela de preços se aplicar ao contexto de um usuário, o preço definido nela será utilizado, mesmo que esse cliente esteja também no contexto de uma política comercial que defina um preço diferente.
 
 ## Como exibir preços diferentes para usuários diferentes
 
@@ -104,6 +98,4 @@ Por exemplo, estes dois clientes estão atrelados a tabelas de preços diferente
 Quando o cliente Daniel, que está na tabela Silver, estiver logado na loja, ele verá os preços definidos nessa tabela. A mochila do exemplo acima aparecerá com o valor de R$ 50,00.
 Já o cliente Breno, que está na tabela Gold, verá os preços definidos nessa outra tabela. Para ele a mochila custará R$ 60,50.
 
-<div class="alert alert-warning">
-<p>Lembre-se de que os preços variam de acordo com a sessão. Ou seja, o cliente <strong>precisa</strong> estar autenticado para que haja alteração (seja através de token, senha, Google ou Facebook). Sem a autenticação do usuário, o preço sempre será o padrão. E atenção: o fato de ele inserir o email no processo de checkout não é suficiente, já que nesse processo ele realiza sua identificação, mas não a autenticação.</p>
-</div>
+>⚠️ Lembre-se de que os preços variam de acordo com a sessão. Ou seja, o cliente **precisa** estar autenticado para que haja alteração (seja através de token, senha, Google ou Facebook). Sem a autenticação do usuário, o preço sempre será o padrão. E atenção: o fato de ele inserir o email no processo de checkout não é suficiente, já que nesse processo ele realiza sua identificação, mas não a autenticação.
diff --git a/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md b/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md
index d447a4a01..566e8faed 100644
--- a/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md
+++ b/docs/tutorials/pt/setting-up-rede-acquirer-with-erederest.md
@@ -15,13 +15,11 @@ legacySlug: configurar-adquirente-rede-com-o-erederest
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Na VTEX, você pode fazer a integração com o [adquirente](/pt/tutorial/o-que-e-um-adquirente) Rede usando o conector ERedeREST. Esse conector traz uma série de melhorias, entre elas o suporte a meios de pagamento com pré-autorização (__Visa__, __Mastercard__, __American Express__, __Diners__, __Hipercard__, __JCB__ e __Credz__).
 
-<div class="alert alert-warning">
-A bandeira <strong>Elo</strong> ainda não oferece suporte para pré-autorização. 
-</div>
+>⚠️ A bandeira **Elo** ainda não oferece suporte para pré-autorização.
 
 Outra característica importante do conector ERedeREST é que você também pode configurá-lo para aceitar pagamentos com [__Apple Pay__](/pt/tutorial/configurar-pagamentos-com-apple-pay), a carteira digital da Apple.
 
diff --git a/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md b/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md
index 04304e3d2..0f9da9343 100644
--- a/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md
+++ b/docs/tutorials/pt/setting-up-seller-white-label-as-a-pickup-point.md
@@ -23,9 +23,7 @@ Conforme explicado no artigo [Definições de Conta Franquia e Seller White Labe
 
 Desta maneira, o ponto de retirada configurado na Conta Franquia servirá para atender às entregas dos pedidos realizados na Conta Principal. Neste cenário, a Conta Franquia atua como __Seller White Label__ da Conta Principal.
 
-<div class="alert alert-danger">
-As configurações devem ser feitas na conta do Seller White Label. Os itens só ficarão disponíveis para retirada no checkout do cliente final se o SKU estiver disponível no estoque da conta principal e da conta do Seller White Label.
-</div>
+>❗ As configurações devem ser feitas na conta do Seller White Label. Os itens só ficarão disponíveis para retirada no checkout do cliente final se o SKU estiver disponível no estoque da conta principal e da conta do Seller White Label.
 
 ## Configurações iniciais 
 
@@ -48,9 +46,7 @@ Para saber em detalhes como preencher os  campos da planilha, acesse nosso artig
 
 Se a configuração do ponto de retirada tiver sido feita corretamente na Conta Franquia, os SKUs com __estoque disponível e preço__ poderão ser vendidos na Conta Principal, onde a Conta Franquia vai atuar como um __Seller White Label__ e a Conta Principal funcionará como um __Marketplace__.
 
-<div class="alert alert-warning">
-Certifique-se de que o seller white label está ativo. Para isso, acesse o Admin VTEX, em <b>Marketplace > Sellers > Gerenciamento</b>, e na linha do seller e coluna <i>Status</i>, clique em <code>Ativo</code>.
-</div>
+>⚠️ Certifique-se de que o seller white label está ativo. Para isso, acesse o Admin VTEX, em **Marketplace > Sellers > Gerenciamento**, e na linha do seller e coluna <i>Status</i>, clique em `Ativo`.
 
 ### Seller White Label/Conta Franquia
 
diff --git a/docs/tutorials/pt/setting-up-shipment.md b/docs/tutorials/pt/setting-up-shipment.md
index ec8295e56..4ce9e41a9 100644
--- a/docs/tutorials/pt/setting-up-shipment.md
+++ b/docs/tutorials/pt/setting-up-shipment.md
@@ -17,9 +17,7 @@ subcategory: 1UL6Q7nUN6SkA2g2SUsECi
 
 Esta é uma configuração amplamente utilizada quando um fluxo muito grande de pedidos acaba gerando uma demanda logística considerável, pois possibilita que um pacote aguarde o tempo de preparo de outro para ser enviado em grupo, por uma mesma transportadora, a um destinatário final.
 
-<div class="alert alert-warning">
-Os grupos de remessa são criados pela somatória do tempo de custo do Estoque até a Doca e do tempo de custo da Doca.
-</div>
+>⚠️ Os grupos de remessa são criados pela somatória do tempo de custo do Estoque até a Doca e do tempo de custo da Doca.
 
 Na imagem abaixo vemos a configuração de remessa de __6 dias.__ Cada caixinha representa o custo em dias de um pacote, considerando apenas o __custo de estoque e o custo da doca.__
 
diff --git a/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md b/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md
index c36398e80..d95963e35 100644
--- a/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md
+++ b/docs/tutorials/pt/setting-up-sitef-gateway-with-pre-auth.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-sitef-com-pre-auth
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Para permitir que compras feitas com cartão de crédito tenham o valor reservado, você pode configurar o gateway __Sitef com pre-auth__ (pré-autorização) na sua loja.
 
diff --git a/docs/tutorials/pt/setting-up-sitef-gateway.md b/docs/tutorials/pt/setting-up-sitef-gateway.md
index ab6ac0f8c..db753b7bb 100644
--- a/docs/tutorials/pt/setting-up-sitef-gateway.md
+++ b/docs/tutorials/pt/setting-up-sitef-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-gateway-sitef
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 Na VTEX, é possível configurar o gateway Sitef. Para configurá-lo, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md b/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md
index a1a27893c..cc1238452 100644
--- a/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md
+++ b/docs/tutorials/pt/setting-up-sub-acquirer-stelo.md
@@ -15,7 +15,7 @@ legacySlug: configurar-subadquirente-stelo
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 A Stelo é um [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) que facilita a integração de meios de pagamento à sua loja.
 
diff --git a/docs/tutorials/pt/setting-up-the-global-category.md b/docs/tutorials/pt/setting-up-the-global-category.md
index 63399cb1e..2c48dc922 100644
--- a/docs/tutorials/pt/setting-up-the-global-category.md
+++ b/docs/tutorials/pt/setting-up-the-global-category.md
@@ -19,9 +19,7 @@ A árvore da categoria global é a taxonomia criada pelo Google para o [Merchant
 
 As mesmas categorias globais estão disponíveis para os produtos de todas as lojas.
 
-<div class="alert alert-info">
-Para toda categoria da sua loja, é necessário escolher uma categoria global.
-</div>
+>ℹ️ Para toda categoria da sua loja, é necessário escolher uma categoria global.
 
 ### Por que usar?
 
@@ -29,9 +27,7 @@ Adotamos essa taxonomia porque ela é amplamente aplicável a qualquer contexto,
 
 Ela é usada, por exemplo, como referência para a integração de produtos com Amazon, Buscapé e marketplaces.
 
-<div class="alert alert-info">
-O comportamento padrão da nossa integração com o Google Shopping é <strong>não enviar</strong> esta informação. Assim, a maioria das lojas conta com a categorização automática da própria Google. Caso prefira a categorização manual, <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM" target="_blank">abra um chamado de suporte</a>.
-</div>
+>ℹ️ O comportamento padrão da nossa integração com o Google Shopping é **não enviar** esta informação. Assim, a maioria das lojas conta com a categorização automática da própria Google. Caso prefira a categorização manual, [abra um chamado de suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM" target="_blank).
 
 ### Quando ela é aplicada?
 
@@ -59,9 +55,7 @@ Você sempre deve escolher a categoria global que mais se aproxima dos produtos
 
 O ideal é que uma categoria global seja determinada nas configurações de categoria. Isso permite que todos os produtos de uma categoria pertençam à mesma categoria global. 
 
-<div class="alert alert-danger">
-Escolher uma categoria global no cadastro do produto é recomendável somente se ele tiver que ser configurado de forma diferente da categoria na qual está inserido.
-</div>
+>❗ Escolher uma categoria global no cadastro do produto é recomendável somente se ele tiver que ser configurado de forma diferente da categoria na qual está inserido.
 
 A configuração da categoria global é feita no Admin, e o seu preenchimento é obrigatório. Para configurá-la, siga os passos abaixo:
 
@@ -74,6 +68,4 @@ A configuração da categoria global é feita no Admin, e o seu preenchimento é
 7. Escreva o nome da categoria que deseja encontrar e clique no botão <i class="fas fa-search"></i>. Você pode utilizar a barra de busca para encontrar a categoria desejada.
 8. Clique na categoria escolhida, para que ela seja selecionada, e em seguida clique no botão `Salvar`.
 
-<div class="alert alert-info">
-A categoria global pode também ser <a href="https://help.vtex.com/pt/tutorial/configuring-xml--tutorials_242">configurada por arquivo XML</a>.
-</div>
+>ℹ️ A categoria global pode também ser [configurada por arquivo XML](https://help.vtex.com/pt/tutorial/configuring-xml--tutorials_242).
diff --git a/docs/tutorials/pt/setting-up-the-logistics-for-instore.md b/docs/tutorials/pt/setting-up-the-logistics-for-instore.md
index 04a2644a0..2b6118d94 100644
--- a/docs/tutorials/pt/setting-up-the-logistics-for-instore.md
+++ b/docs/tutorials/pt/setting-up-the-logistics-for-instore.md
@@ -15,10 +15,8 @@ legacySlug: configurar-logistica-para-o-instore
 subcategory: 4T6qfa6gNO6g4sAUIa6s2G
 ---
 
-<div class="alert alert-info">
-Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
-<a href="https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl">estratégia de envio</a>.
-</div> 
+>ℹ️ Aviso: Esta documentação está em processo de atualização para refletir a mudança do conceito de Painéis para 
+> [estratégia de envio](https://help.vtex.com/announcements/estoque-e-entrega-entenda-o-que-mudou-na-aba-paineis--1YNfaeNG206XKI2UbGBRSl). 
 
 
 Para que o inStore funcione corretamente, é necessário realizar uma configuração logística específica para ele. O inStore deve ser configurado com um __ponto de retirada__. O cadastro logístico segue duas etapas:
diff --git a/docs/tutorials/pt/setting-up-the-moip-sub-acquirer.md b/docs/tutorials/pt/setting-up-the-moip-sub-acquirer.md
index 401208866..c2d856982 100644
--- a/docs/tutorials/pt/setting-up-the-moip-sub-acquirer.md
+++ b/docs/tutorials/pt/setting-up-the-moip-sub-acquirer.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 O Moip é um [subadquirente](/pt/tutorial/o-que-e-um-subadquirente) que oferece uma integração única para conectar sua loja a todas as partes envolvidas no fluxo de pagamento oferecendo proteção contra fraudes e uma solução de [checkout transparente](/pt/tutorial/o-que-e-checkout-transparente) (sem redirecionamentos).
 
-<div class="alert alert-warning">
-As informações deste artigo são apenas referências de configuração para lojistas que já estejam utilizando o subadquirente Moip. Para novas afiliações, recomendamos a utilização do subadquirente <a href="https://help.vtex.com/pt/tutorial/configurar-o-subadquirente-moipv2--4BipUcTxQ7cq2BiYzUDmEH">MoipV2</a>.
-  </div>
+>⚠️ As informações deste artigo são apenas referências de configuração para lojistas que já estejam utilizando o subadquirente Moip. Para novas afiliações, recomendamos a utilização do subadquirente [MoipV2](https://help.vtex.com/pt/tutorial/configurar-o-subadquirente-moipv2--4BipUcTxQ7cq2BiYzUDmEH).
 
 Para configurar o Moip, siga os passos abaixo:
 
@@ -38,9 +36,7 @@ Para configurar o Moip, siga os passos abaixo:
   6. Clique em <b>Salvar</b>.
   </ui><br><br>
 
-<div class="alert alert-warning">
-O MOIP não processa transações quando produtos com valor "$0,00" estão no carrinho.  Por exemplo: Se um <a href="https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete">anexo</a> de embalagem de presente for criado, o valor do item vai ser $ 0,00, o que impossibilita o processamento do pagamento.
-  </div>
+>⚠️ O MOIP não processa transações quando produtos com valor "$0,00" estão no carrinho.  Por exemplo: Se um [anexo](https://help.vtex.com/pt/tutorial/o-que-e-um-anexo--aGICk0RVbqKg6GYmQcWUm?&utm_source=autocomplete) de embalagem de presente for criado, o valor do item vai ser $ 0,00, o que impossibilita o processamento do pagamento.
 
 ## Configurar condição de pagamento
 
diff --git a/docs/tutorials/pt/setting-up-the-notify-me-option.md b/docs/tutorials/pt/setting-up-the-notify-me-option.md
index 57e6e943e..18dfa34a0 100644
--- a/docs/tutorials/pt/setting-up-the-notify-me-option.md
+++ b/docs/tutorials/pt/setting-up-the-notify-me-option.md
@@ -15,9 +15,7 @@ legacySlug: configurar-o-avise-me
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-<div class="alert alert-warning">
-  <p> Este artigo explica como configurar o <strong>Avise-me</strong> em lojas que utilizam o <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>. Em lojas que utilizam <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, a configuração precisa ser feita seguindo os passos do guia <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify">Availability Notify</a>.</p>
-</div>
+>⚠️ Este artigo explica como configurar o **Avise-me** em lojas que utilizam o [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj). Em lojas que utilizam [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), a configuração precisa ser feita seguindo os passos do guia [Availability Notify](https://developers.vtex.com/vtex-developer-docs/docs/vtex-availability-notify).
 
 Quando um produto está fora de [estoque](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139), o lojista pode optar por disponibilizar para o cliente o **Avise-me**. Essa funcionalidade permite que os clientes interessados sejam notificados por email quando o item voltar a ficar disponível.
 
diff --git a/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md b/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
index a8bd1c120..3e43e56ea 100644
--- a/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
+++ b/docs/tutorials/pt/setting-up-the-sales-funnel-on-google-analytics.md
@@ -19,9 +19,7 @@ As metas do **Google Analytics** servem para ajudar a avaliar se os objetivos de
 
 Com o funil de vendas configurado, é possível acompanhar e analisar os passos do cliente até a finalização de um pedido. Para configurar o funil de vendas vamos levar em conta que o processo de compra se inicia na tela do seu produto e passa pelo carrinho de compras, checkout (dados pessoais, entrega e frete, pagamento) e chega até a meta, que é a página de pedido confirmado.
 
-<div class="alert alert-info">
-Para facilitar, toda a configuração apresentada neste artigo pode ser <a href="https://support.google.com/analytics/answer/1032415?hl=pt-BR" target="_blank">importada diretamente para o Google Analytics</a> com <a href="https://analytics.google.com/analytics/web/template?uid=tTp2GkIJRiGodszJbq8RsA" target="_blank">este modelo</a>.
-</div>
+>ℹ️ Para facilitar, toda a configuração apresentada neste artigo pode ser [importada diretamente para o Google Analytics](https://support.google.com/analytics/answer/1032415?hl=pt-BR" target="_blank) com [este modelo](https://analytics.google.com/analytics/web/template?uid=tTp2GkIJRiGodszJbq8RsA" target="_blank).
 
 Para configuração manual ou edição de uma meta já existente, o primeiro passo é acessar o Analytics e clicar no botão __Administrador__ no canto inferior esquerdo. Em seguida, ir na opção __Metas__, da coluna "Vista".
 
@@ -62,30 +60,35 @@ Agora é só salvar a meta e aguardar o tempo que o sistema leva para começar a
 
 Para visualizar seu funil, consulte os relatórios do Analytics e acesse o menu __Conversões__ e a opção __Metas__.
 
-<div class="alert alert-warning">
-<p> Se você tiver uma loja multilíngue com idiomas como <a href="https://support.google.com/webmasters/answer/182192?hl=pt-BR#locale-specific-urls">subdiretórios com gTLD</a> você deve substituir cada <a href="https://support.google.com/analytics/answer/1034376?hl=pt-BR&ref_topic=1034375">circunflexo</a> (<code>^</code>) por uma <a href="https://support.google.com/analytics/answer/1034324?hl=en">regex </a> que corresponda aos diferentes subdiretórios. Por exemplo, se o seu site estiver disponível em:</p>
-  <ul>
-    <li><strong>Italiano: </strong><code>example.com/it</code></li>
-    <li><strong>Espanhol: </strong><code>example.com/es</code></li>
-    <li><strong>Francês: </strong><code>example.com/fr</code></li>
-  </ul>
-  <p>Você teria que alterar seu destino:</p>
-  <ul>
-<li><strong>De: </strong><code>^/checkout/orderPlaced</code></li> 
-<li><strong>Para: </strong><code>^/(it|es|fr)/checkout/orderPlaced</code></li>
-  </ul>
-  <p>Isso também precisaria ser feito para cada etapa do funil.</p>
-</div>
-
-<div class="alert alert-warning">
-<p>As configurações de funil deste artigo foram atualizadas para acompanhar a nova versão de <a href="http://help.vtex.com/pt/tutorial/o-que-e-o-carrinho-compartilhado">carrinho compartilhado do SmartCheckout</a>.</p>
-<p>Para efeito de comparação, abaixo temos a configuração antiga:</p>
-<ol>
-<li>Produto: <code>/p($|\?)</code> (não obrigatório)</li>
-<li>Carrinho: <code>^/checkout/(#/cart)?$</code></li>
-<li>Identificação: <code>^/checkout/#/email</code></li>
-<li>Dados Pessoais: <code>^/checkout/#/profile</code></li>
-<li>Entrega: <code>^/checkout/#/shipping</code></li>
-<li>Pagamento: <code>^/checkout/#/payment</code></li>
-</ol>
-</div>
+>⚠️ Se você tiver uma loja multilíngue com idiomas como [subdiretórios com gTLD](https://support.google.com/webmasters/answer/182192?hl=pt-BR#locale-specific-urls) você deve substituir cada [circunflexo](https://support.google.com/analytics/answer/1034376?hl=pt-BR&ref_topic=1034375) (`^`) por uma [regex ](https://support.google.com/analytics/answer/1034324?hl=en) que corresponda aos diferentes subdiretórios. Por exemplo, se o seu site estiver disponível em:
+>
+> * **Italiano: **`example.com/it`
+>
+> * **Espanhol: **`example.com/es`
+>
+> * **Francês: **`example.com/fr`
+>
+> Você teria que alterar seu destino:
+>
+> ***De: **`^/checkout/orderPlaced` 
+>
+> ***Para: **`^/(it|es|fr)/checkout/orderPlaced`
+>
+> Isso também precisaria ser feito para cada etapa do funil.
+
+>⚠️ As configurações de funil deste artigo foram atualizadas para acompanhar a nova versão de [carrinho compartilhado do SmartCheckout](http://help.vtex.com/pt/tutorial/o-que-e-o-carrinho-compartilhado).
+>
+> Para efeito de comparação, abaixo temos a configuração antiga:
+>
+> Produto: `/p($|\?)` (não obrigatório)
+>
+> Carrinho: `^/checkout/(#/cart)?$`
+>
+> Identificação: `^/checkout/#/email`
+>
+> Dados Pessoais: `^/checkout/#/profile`
+>
+> Entrega: `^/checkout/#/shipping`
+>
+> Pagamento: `^/checkout/#/payment`
+> 
diff --git a/docs/tutorials/pt/setting-up-the-tnspay-gateway.md b/docs/tutorials/pt/setting-up-the-tnspay-gateway.md
index dfb090e05..113b7cace 100644
--- a/docs/tutorials/pt/setting-up-the-tnspay-gateway.md
+++ b/docs/tutorials/pt/setting-up-the-tnspay-gateway.md
@@ -15,7 +15,7 @@ legacySlug: configurar-o-gateway-tnspay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 O TNSPay é um [gateway](/pt/tutorial/o-que-e-um-gateway-de-pagamentos) com certificação PCI e que oferece uma série de recursos de segurança para facilitar o processamento de [compras recorrentes](/pt/faq/como-funciona-a-compra-recorrente).
 
diff --git a/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md b/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
index 174b7dcdd..8af69a640 100644
--- a/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
+++ b/docs/tutorials/pt/setting-up-the-type-of-interest-rate.md
@@ -41,6 +41,4 @@ O response que retornou a chamada anterior "GET Rule by ID" será o request da s
 
 https://developers.vtex.com/reference/configuration-1#putrulebyid
 
-<div class="alert alert-danger">
-IMPORTANTE: Atualmente, a forma de pagamento somente pode ser modificada via API. Caso seja necessário modificar a forma de pagamento a partir da interface do usuário, o processo de configuração por API deverá ser repetido, pois ao Salvar as alterações, será considerado valor vazio por padrão.
-</div>
+>❗ IMPORTANTE: Atualmente, a forma de pagamento somente pode ser modificada via API. Caso seja necessário modificar a forma de pagamento a partir da interface do usuário, o processo de configuração por API deverá ser repetido, pois ao Salvar as alterações, será considerado valor vazio por padrão.
diff --git a/docs/tutorials/pt/setting-up-triggers.md b/docs/tutorials/pt/setting-up-triggers.md
index de6df465f..97a78a2a2 100644
--- a/docs/tutorials/pt/setting-up-triggers.md
+++ b/docs/tutorials/pt/setting-up-triggers.md
@@ -15,9 +15,7 @@ legacySlug: configurar-triggers
 subcategory: 5tSNDlvmik8gGuKw2goW4q
 ---
 
-<div class="alert alert-info">
-Esse artigo se refere ao Master Data v2. Se você quiser utilizar o Master Data v1, veja os passos <a href="https://help.vtex.com/pt/tutorial/criando-trigger-no-master-data--tutorials_1270">deste artigo</a>.
-</div>
+>ℹ️ Esse artigo se refere ao Master Data v2. Se você quiser utilizar o Master Data v1, veja os passos [deste artigo](https://help.vtex.com/pt/tutorial/criando-trigger-no-master-data--tutorials_1270).
 
 Um trigger do Master Data é uma ação executada após uma inserção ou uma atualização. 
 
diff --git a/docs/tutorials/pt/setup-safetypay.md b/docs/tutorials/pt/setup-safetypay.md
index 921211b0d..ad4017848 100644
--- a/docs/tutorials/pt/setup-safetypay.md
+++ b/docs/tutorials/pt/setup-safetypay.md
@@ -15,7 +15,7 @@ legacySlug: configurar-safetypay
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-danger">Essa integração de pagamento não pode ser mais configurada na plataforma devido ao <a href="https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14">processo de remoção de provedores legados</a> e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.</div>
+>❗ Essa integração de pagamento não pode ser mais configurada na plataforma devido ao [processo de remoção de provedores legados](https://help.vtex.com/pt/announcements/conectores-legados-de-pagamentos-serao-descontinuados-em-2024--4R5YIjUu1IWkiOHzXtQU14) e o artigo será removido em breve do Help Center. Verifique com o seu provedor maiores informações sobre o desenvolvimento da nova integração de pagamento e os passos necessários para a migração das configurações em sua loja.
 
 SafetyPay é uma solução de pagamentos que conecta diretamente o checkout da sua loja ao banco do seu cliente. Nesta solução, o seu cliente escolhe a SafetyPay como meio de pagamento e é *redirecionado* para o ambiente seguro do internet banking escolhido. Uma vez redirecionado, o cliente pode fazer uma transferência bancária e realizar o pagamento do pedido.
 
diff --git a/docs/tutorials/pt/shipping-options-beta.md b/docs/tutorials/pt/shipping-options-beta.md
index 5f309b152..faf28d80c 100644
--- a/docs/tutorials/pt/shipping-options-beta.md
+++ b/docs/tutorials/pt/shipping-options-beta.md
@@ -15,9 +15,7 @@ legacySlug: delivery-options-beta
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 **Opções de envio** é a funcionalidade que permite ao lojista criar, editar e gerenciar no mesmo local as opções de envio de pedidos, garantindo mais simplicidade e eficiência na gestão da sua operação. O termo envio é a forma geral de se referir a entrega ou retirada de um pedido. Na configuração de cada opção de envio, o lojista determina:
 
diff --git a/docs/tutorials/pt/shipping-policy-beta.md b/docs/tutorials/pt/shipping-policy-beta.md
index 0787ce72d..a9dd2ff32 100644
--- a/docs/tutorials/pt/shipping-policy-beta.md
+++ b/docs/tutorials/pt/shipping-policy-beta.md
@@ -19,11 +19,7 @@ Política de envio é um conjunto de regras que definem as opções e condiçõe
 
 Todas essas configurações são baseadas principalmente no contrato que a sua loja tem com uma [transportadora](https://help.vtex.com/pt/tutorial/o-que-e-uma-transportadora--7u9duMD5UQa2QQwukAWMcE), com um prestador de serviço, ou com qualquer outro tipo de contrato de serviço de frete que sua loja ofereça aos consumidores.
 
-<div class="alert alert-info"> 
-
-É possível que uma mesma transportadora seja base de múltiplas políticas de envio, cada uma com suas particularidades. Veja abaixo como criar, editar e excluir políticas de envio.
-
-</div>
+>ℹ️ É possível que uma mesma transportadora seja base de múltiplas políticas de envio, cada uma com suas particularidades. Veja abaixo como criar, editar e excluir políticas de envio.
 
 Pela plataforma da VTEX, é possível: 
 
diff --git a/docs/tutorials/pt/shipping-rate-template.md b/docs/tutorials/pt/shipping-rate-template.md
index ecb4ef9bf..8011fb6d3 100644
--- a/docs/tutorials/pt/shipping-rate-template.md
+++ b/docs/tutorials/pt/shipping-rate-template.md
@@ -24,9 +24,7 @@ Para cadastrar preços de envio pela planilha de frete é necessário:
 1. [Preencher os campos da planilha](#preencher-os-campos-da-planilha)
 2. [Enviar o arquivo pelo Admin VTEX](#enviar-o-arquivo-pelo-admin-vtex)
 
-<div class="alert alert-info"> 
-Há também como cadastrar preços de envio pelo módulo <a href="https://help.vtex.com/pt/tutorial/gerenciar-valores-de-frete--tutorials_141">Tarifas de Envio</a>. Recomendamos utilizar a <a href="https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127">Planilha de frete</a> ao incluir vários intervalos de código postal, e utilizar Tarifas de Envio para gerenciar os preços de frete já cadastrados e para cadastrar cada intervalo de código postal individualmente.
-</div>
+>ℹ️ Há também como cadastrar preços de envio pelo módulo [Tarifas de Envio](https://help.vtex.com/pt/tutorial/gerenciar-valores-de-frete--tutorials_141). Recomendamos utilizar a [Planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) ao incluir vários intervalos de código postal, e utilizar Tarifas de Envio para gerenciar os preços de frete já cadastrados e para cadastrar cada intervalo de código postal individualmente.
 
 ## Preencher os campos da planilha
 
@@ -175,9 +173,7 @@ Confira a tabela a seguir para entender cada campo detalhadamente.
 </tbody>
 </table>
 
-<div class="alert alert-info"> 
-Para fins de usabilidade de termos, utilizamos em nossa documentação o termo "peso" ao invés de "massa". 
-</div>
+>ℹ️ Para fins de usabilidade de termos, utilizamos em nossa documentação o termo "peso" ao invés de "massa".
 
 Veja abaixo um exemplo de preenchimento dos campos, considerando o formato aceito em cada coluna. 
 
@@ -196,13 +192,9 @@ O envio da planilha é feito no cadastro ou na edição de **Política de Envio.
 
 ![upload tarifas envioPT]   (//images.contentful.com/alneenqid6w5/1qNl0ZaHhZMpshuBWRQhs9/f5814cef893c4f139a8497ec1985cbb2/upload_tarifas_envioPT.png)
 
-<div class="alert alert-warning"> 
-Para cadastrar uma <b>nova</b> Política de Envio, é preciso preencher outros campos além da Planilha de frete. Entenda como criar, editar e preencher todos os campos necessários no artigo <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de Envio</a>.
-</div>
+>⚠️ Para cadastrar uma **nova** Política de Envio, é preciso preencher outros campos além da Planilha de frete. Entenda como criar, editar e preencher todos os campos necessários no artigo [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 
-<div class="alert alert-danger"> 
-Cada aba dentro da planilha não pode ultrapassar 65.536 linhas. É possível criar várias abas na mesma planilha, respeitando o limite de linhas. Não há limite de abas dentro do arquivo, no entanto o arquivo total não pode exceder 10Mb. Se preciso, compacte o arquivo em formato <b>.zip</b>. Se ainda não for suficiente, divida em dois arquivos e cadastre outra política de envio para fazer upload do segundo arquivo criado. 
-</div>
+>❗ Cada aba dentro da planilha não pode ultrapassar 65.536 linhas. É possível criar várias abas na mesma planilha, respeitando o limite de linhas. Não há limite de abas dentro do arquivo, no entanto o arquivo total não pode exceder 10Mb. Se preciso, compacte o arquivo em formato **.zip**. Se ainda não for suficiente, divida em dois arquivos e cadastre outra política de envio para fazer upload do segundo arquivo criado.
 
 Caso exista algum problema no preenchimento dos campos do arquivo enviado, você receberá um email informando o erro. Não esqueça de verificar o preenchimento correto antes de realizar uma nova tentativa de envio.
 
diff --git a/docs/tutorials/pt/shipping-rates.md b/docs/tutorials/pt/shipping-rates.md
index 49b136f27..dad567d7a 100644
--- a/docs/tutorials/pt/shipping-rates.md
+++ b/docs/tutorials/pt/shipping-rates.md
@@ -17,9 +17,7 @@ subcategory: 7uJcyu0VawEm8ggqKu404u
 
 As tarifas de envio são os custos de frete que sua loja oferece aos clientes, e estão relacionadas às [Políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) da sua loja. Dessa forma, os preços acordados entre sua loja e os responsáveis pelas entregas (como transportadoras, pontos de retirada, prestadores de serviços) devem ser configurados como **Tarifas de envio.**  
 
-<div class="alert alert-warning">
-O <a href="https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV">custo final do envio</a> para o cliente inclui tarifa de envio, <a href="https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV">adicionais de frete</a> e custo de doca com estoque.
-</div>
+>⚠️ O [custo final do envio](https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV) para o cliente inclui tarifa de envio, [adicionais de frete](https://help.vtex.com/pt/tutorial/adicionais-de-frete--2vqGwMn0LabkOHY6zSHYNV) e custo de doca com estoque.
 
 ![Tarifa envio PT](https://images.ctfassets.net/alneenqid6w5/21DY5nCwLfuquTatiw2Q3e/7b02d517a10fc6acdf0f343c3b1ea797/Tarifa_envio_PT.svg)
 
@@ -28,11 +26,7 @@ Pelo Admin VTEX, há duas maneiras de cadastrar as tarifas de envio:
 * Na página `Estratégia de envio`: ao adicionar uma nova `Política de envio` ou atualizar uma já cadastrada, você deve fazer o _upload_ da [planilha de frete](https://help.vtex.com/pt/tutorial/como-montar-a-planilha-de-frete--tutorials_127). Essa maneira de cadastro de tarifas de envio é indicada quando há muitos códigos postais para serem adicionados com sua precificação de entrega. 
 * Na página `Tarifas de envio`: para casos em que se deseja atualizar tarifas já cadastradas ou adicionar poucas tarifas. É possível editar e inserir novos preços de envio sem a manipulação da planilha de frete. Para saber mais, acesse o [tutorial de gerenciamento de tarifas](https://help.vtex.com/pt/tutorial/gerenciar-valores-de-frete--tutorials_141).
 
-<div class="alert alert-warning">
-Você pode configurar a localização por polígono, o <b>custo de seguro</b> e o <b>adicional de frete</b> apenas pela <b><a href="https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127">planilha de frete</a>
-</b>. 
-</div>
+>⚠️ Você pode configurar a localização por polígono, o **custo de seguro** e o **adicional de frete** apenas pela <b>[planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127)
+> </b>.
 
-<div class="alert alert-info">
-Para casos em que há vários preços de envio para serem atualizados ou cadastrados, recomendamos utilizar a <a href="https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127">Planilha de frete</a> em vez do módulo <b>Tarifas de envio</b>. Caso queira conferir como as tarifas de envio cadastradas serão apresentadas ao cliente final, utilize o módulo <b><a href="https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144">Simulador de envio</a></b>.
-</div>
+>ℹ️ Para casos em que há vários preços de envio para serem atualizados ou cadastrados, recomendamos utilizar a [Planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) em vez do módulo **Tarifas de envio**. Caso queira conferir como as tarifas de envio cadastradas serão apresentadas ao cliente final, utilize o módulo **[Simulador de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144)**.
diff --git a/docs/tutorials/pt/shipping-simulation.md b/docs/tutorials/pt/shipping-simulation.md
index 6e8504a5b..31f248ae9 100644
--- a/docs/tutorials/pt/shipping-simulation.md
+++ b/docs/tutorials/pt/shipping-simulation.md
@@ -23,14 +23,15 @@ O simulador pode ser utilizado também para validar as configurações das  **[E
 
 * **Disponibilidade de Sellers White Label:** o simulador seleciona o franqueado mais próximo ao endereço de entrega (a configuração logística é calculada através do ambiente do _Seller White Label_, e não no Main Account).
 
-<div class="alert alert-warning"> 
-Pode haver divergência entre o preço final apontado pelo simulador, e o preço real em sua loja, visto que a simulação não leva em consideração:
-<body>
-<ul>
-<li>Promoções aplicadas àqueles itens.</li>
-<li>Descontos de frete configurados através de promoções.</li>
-<li>O Prazo de Entrega Total apresentado no resultado da simulação não considera o campo <b>Data Previsão Chegada (pré-venda)</b> <a href="https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY">do cadastro do item.</a></li>
-</ul></body></div>
+>⚠️ Pode haver divergência entre o preço final apontado pelo simulador, e o preço real em sua loja, visto que a simulação não leva em consideração:
+> <body>
+>
+> *Promoções aplicadas àqueles itens.
+>
+> *Descontos de frete configurados através de promoções.
+>
+> *O Prazo de Entrega Total apresentado no resultado da simulação não considera o campo **Data Previsão Chegada (pré-venda)** [do cadastro do item.](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-sku--21DDItuEQc6mseiW8EakcY)
+> </body>
 
 Nesse artigo contém:
 
diff --git a/docs/tutorials/pt/shopee-integration.md b/docs/tutorials/pt/shopee-integration.md
index 6fc549324..d80f7a6bd 100644
--- a/docs/tutorials/pt/shopee-integration.md
+++ b/docs/tutorials/pt/shopee-integration.md
@@ -84,9 +84,7 @@ Depois de ter feito as pré-configurações da sua loja VTEX, você poderá inst
 
 No final da instalação, o app estará disponível no seu Admin VTEX.
 
-<div class="alert alert-info">
-O acesso ao aplicativo da Shopee pode ser realizado seguindo as instruções acima ou através do caminho <b>Admin VTEX > Marketplace > Marketplaces e integrações.</b>
-</div>
+>ℹ️ O acesso ao aplicativo da Shopee pode ser realizado seguindo as instruções acima ou através do caminho **Admin VTEX > Marketplace > Marketplaces e integrações.**
 
 ## Configurações Shopee
 
@@ -198,9 +196,7 @@ Você será direcionado a página de mapeamento da Shopee e a página apresentar
 
 Na página de mapeamento, existe uma barra de busca que permite buscar a categoria por nome. Além disso, a seção **Categorias da loja** exibe lista das categorias da sua loja VTEX. 
 
-<div class="alert alert-info">
-  A Shopee exige uma especificação para diferenciar um SKU do outro. Caso não haja especificação mapeada em seu produto, a integração utilizará o nome do SKU para criar essa especificação.
-  </div>
+>ℹ️ A Shopee exige uma especificação para diferenciar um SKU do outro. Caso não haja especificação mapeada em seu produto, a integração utilizará o nome do SKU para criar essa especificação.
 
 A lista de categorias da sua loja VTEX inclui o status de seu  mapeamento  por meio dos ícones:
 
@@ -219,9 +215,7 @@ O mapeamento dos atributos permite que exista uma correspondência entre o padr
 
 Os campos não mapeados não impedem que o mapeamento ocorra, porém, quanto mais atributos enviados para a Shopee seu produto tiver, melhor rankeado ele será no marketplace.
 
-<div class="alert alert-warning">
-A descrição dos produtos precisa ter, no mínimo, 100 caracteres. Além disso, a Shopee não aceita produtos com menos de 100 gramas, assim como não é possível enviar produtos com dimensões inválidas. Exemplo: Altura = 0 cm , Largura = 0,000001 cm. Em caso de dúvida, acesse o artigo <a href="https://seller.shopee.com.br/edu/article/3305/dimensoes-e-pesos-permitidos-para-enviar-pacotes-na-shopee">Dimensões e pesos permitidos para enviar pacotes da Shopee</a>.
-</div>
+>⚠️ A descrição dos produtos precisa ter, no mínimo, 100 caracteres. Além disso, a Shopee não aceita produtos com menos de 100 gramas, assim como não é possível enviar produtos com dimensões inválidas. Exemplo: Altura = 0 cm , Largura = 0,000001 cm. Em caso de dúvida, acesse o artigo [Dimensões e pesos permitidos para enviar pacotes da Shopee](https://seller.shopee.com.br/edu/article/3305/dimensoes-e-pesos-permitidos-para-enviar-pacotes-na-shopee).
 
 Para realizar o mapeamento de categorias e atributos no Admin VTEX vá em **Apps > Shopee > Mapeamento de categorias** e siga os passos abaixo:
 
@@ -234,9 +228,7 @@ Para realizar o mapeamento de categorias e atributos no Admin VTEX vá em **Apps
 
 Ao finalizar o mapeamento de categorias e atributos corretamente, o status da categoria mudará para **Mapeado**.
 
-<div class="alert alert-warning">
-A Shopee só aceita marcas já registradas no seu catálogo de produtos. Quando não houver uma marca cadastrada no produto ou a marca cadastrada no produto não corresponder aos nomes aceitos pelo marketplace, ele será categorizado na Shopee como `NoBrand`.
-</div>
+>⚠️ A Shopee só aceita marcas já registradas no seu catálogo de produtos. Quando não houver uma marca cadastrada no produto ou a marca cadastrada no produto não corresponder aos nomes aceitos pelo marketplace, ele será categorizado na Shopee como `NoBrand`.
 
 ## Gerenciar produtos
 
diff --git a/docs/tutorials/pt/sku-bindings.md b/docs/tutorials/pt/sku-bindings.md
index bc73dd9dc..03f6dea7d 100644
--- a/docs/tutorials/pt/sku-bindings.md
+++ b/docs/tutorials/pt/sku-bindings.md
@@ -97,9 +97,7 @@ Para remover o vínculo entre o SKU do seller e o SKU do marketplace, realize os
 2. Na linha do item desejado, clique sobre o ícone menu <i class="fas fa-ellipsis-v"></i>.
 3. Clique em <i class="far fa-trash-alt"></i> `Remover`.
 
-<div class="alert alert-warning">
-Remover um vínculo faz com que o SKU do seller deixe de fazer parte do catálogo do Marketplace, desaparecendo da listagem da página <b>Vínculos de SKU</b>. Não é possível recuperar um vínculo removido, mas o seller pode reenviar o SKU para o marketplace, que <a href="https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus--tutorials_396">cataloga</a> o SKU novamente e torna-o disponível.
-</div>
+>⚠️ Remover um vínculo faz com que o SKU do seller deixe de fazer parte do catálogo do Marketplace, desaparecendo da listagem da página **Vínculos de SKU**. Não é possível recuperar um vínculo removido, mas o seller pode reenviar o SKU para o marketplace, que [cataloga](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus--tutorials_396) o SKU novamente e torna-o disponível.
 
 ## Exportar
 
diff --git a/docs/tutorials/pt/sku-registration-fields.md b/docs/tutorials/pt/sku-registration-fields.md
index 15124b1ab..e670e8fcd 100644
--- a/docs/tutorials/pt/sku-registration-fields.md
+++ b/docs/tutorials/pt/sku-registration-fields.md
@@ -15,9 +15,7 @@ legacySlug: campos-de-cadastro-de-sku
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class="alert alert-warning">
-  <p>Existe um limite de 50 SKUs por produto. Para solicitar que o limite seja ampliado, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>⚠️ Existe um limite de 50 SKUs por produto. Para solicitar que o limite seja ampliado, entre em contato com <a href= "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 Para entender o significado de cada campo do cadastro de SKU, veja a descrição completa dos itens relacionados na página.
 
@@ -77,9 +75,7 @@ Após o preenchimento dos campos, clique em `Salvar`. Para dar continuidade ao c
 
 ## Imagens
 
-<div class="alert alert-info">
-  <p>A imagem de SKU apresenta o tamanho limite de 3200 x 3200 pixels.</p>
-</div>
+>ℹ️ A imagem de SKU apresenta o tamanho limite de 3200 x 3200 pixels.
 
 Como cadastrar uma nova imagem:
 
@@ -131,6 +127,4 @@ Após o preenchimento dos campos necessários, basta clicar em Salvar, na aba SK
 - [Preencher campos de cadastro do Produto](/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke)
 - [Preencher campos da Planilha de Importação](/pt/tutorial/preencher-campos-da-planilha-de-importacao--4nYhx63Q5yokQWaMguaIgI)
 
-<div class="alert alert-danger">
-Para garantir que itens adicionados ao estoque fiquem disponíveis para venda na loja, o <a href="https://help.vtex.com/pt/tutorial/descobrir-o-id-de-um-sku--4VQZsYeb3igGK2YowuEYWW"> ID do SKU </a> não deve conter <b>o número zero à esquerda</b>. O sistema não reconhece, por exemplo, IDs no formato <code>01</code>, <code>02</code>, <code>021</code>, pois é esperado o formato  <code>1</code>, <code>2</code>, <code>21</code>.
-</div>
+>❗ Para garantir que itens adicionados ao estoque fiquem disponíveis para venda na loja, o [ ID do SKU ](https://help.vtex.com/pt/tutorial/descobrir-o-id-de-um-sku--4VQZsYeb3igGK2YowuEYWW) não deve conter **o número zero à esquerda**. O sistema não reconhece, por exemplo, IDs no formato `01`, `02`, `021`, pois é esperado o formato  `1`, `2`, `21`.
diff --git a/docs/tutorials/pt/sla-errors-in-marketplace-integration-orders.md b/docs/tutorials/pt/sla-errors-in-marketplace-integration-orders.md
index 839f5cad8..c52c56274 100644
--- a/docs/tutorials/pt/sla-errors-in-marketplace-integration-orders.md
+++ b/docs/tutorials/pt/sla-errors-in-marketplace-integration-orders.md
@@ -31,9 +31,7 @@ Os problemas mais comuns que ocasionam erros de SLA são:
 
 Após solucionar o erro, o pedido deve ser reprocessado manualmente. No seu Admin, no módulo **Marketplace > Conexões > Pedidos**, clique sobre o pedido com erro. Feito isso, o botão **Ações** se torna visível, clique sobre ele e escolha a opção **Reprocessar**.
 
-<div class="alert alert-info">
-Caso o erro persista, abra um <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt">chamado para suporte VTEX</a>.
-</div>
+>ℹ️ Caso o erro persista, abra um [chamado para suporte VTEX](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM?locale=pt).
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md b/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md
index 1d4834c69..831ff0081 100644
--- a/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md
+++ b/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md
@@ -17,9 +17,7 @@ subcategory: 6XAvmMxp7yyY06ewYMuggs
 
 O SmartCheckout permite que os dados do cliente possam ser preenchidos no Checkout de forma automática, sendo necessário apenas informar o seu email cadastrado na loja. Esta função reduz o tempo de compra e elimina a necessidade de inserir dados novamente a cada compra realizada na mesma loja.
 
-<div class="alert alert-info">
-Para que o SmartCheckout reutilize os dados do cliente no Checkout, é necessário que o mesmo já tenha realizado uma compra anteriormente ou criado um perfil cadastrado na loja.
-</div>
+>ℹ️ Para que o SmartCheckout reutilize os dados do cliente no Checkout, é necessário que o mesmo já tenha realizado uma compra anteriormente ou criado um perfil cadastrado na loja.
 
 ## Dados de cadastro do cliente
 
diff --git a/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md b/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
index b10dcee11..e10e22557 100644
--- a/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
+++ b/docs/tutorials/pt/smartcheckout-v5-general-characteristics.md
@@ -55,9 +55,7 @@ Você pode usar os arquivos `checkout5-custom.js` e `orderplaced2-custom.js` p
 4. No menu __Arquivos__, localizado no lado direito da página, clique naqueles em que desejar realizar ajustes no código.
 5. Clique no botão `Salvar`.
 
-<div class="alert alert-warning">
-  Customizar arquivos de Javascript pode danificar seu Checkout. A VTEX <b>não recomenda</b> customizações e não se responsabiliza por qualquer dano causado por esse código.
-</div>
+>⚠️ Customizar arquivos de Javascript pode danificar seu Checkout. A VTEX **não recomenda** customizações e não se responsabiliza por qualquer dano causado por esse código.
 
 __IMPORTANTE:__ não use esses arquivos para inserir tags de marketing e integrações. Se precisar delas, faça isso pelo Google Tag Manager.
 
diff --git a/docs/tutorials/pt/sms-and-email-report.md b/docs/tutorials/pt/sms-and-email-report.md
index 6f67b7442..bfefc86ec 100644
--- a/docs/tutorials/pt/sms-and-email-report.md
+++ b/docs/tutorials/pt/sms-and-email-report.md
@@ -47,7 +47,5 @@ Para cada  quadrado há um botão no canto superior à direita que ao clicá-lo
 
 Para visualizar em formato de tabela e exportar as informações, abaixo dos filtros, clique em `TABELA`. Para baixar a tabela em formato .csv clique no botão `EXPORTAR`.
 
-<div class="alert alert-info"> 
-As mensagens que são enviadas automaticamente aos clientes durante a entrega do serviço são configuradas internamente pela VTEX.
-</div>
+>ℹ️ As mensagens que são enviadas automaticamente aos clientes durante a entrega do serviço são configuradas internamente pela VTEX.
 
diff --git a/docs/tutorials/pt/special-conditions.md b/docs/tutorials/pt/special-conditions.md
index a23d8360b..e3e024a30 100644
--- a/docs/tutorials/pt/special-conditions.md
+++ b/docs/tutorials/pt/special-conditions.md
@@ -136,9 +136,7 @@ Digamos que você deseje oferecer uma condição especial de pagamento para clie
 
 Neste caso, você deve selecionar o banco emissor que é o seu parceiro responsável por esse cartão e, em seguida, o nome da sua loja no campo __Co-brand__.
 
-<div class="alert alert-warning">
-Por padrão, a informação de que um cartão tem co-brand <strong>não</strong> está cadastrada na base de dados da VTEX. Por isso, caso sua loja deseje segmentar uma condição de pagamento por cartões da loja, você precisa enviar a lista de cartões com co-brand para o time de suporte da VTEX por meio de um ticket.
-</div>
+>⚠️ Por padrão, a informação de que um cartão tem co-brand **não** está cadastrada na base de dados da VTEX. Por isso, caso sua loja deseje segmentar uma condição de pagamento por cartões da loja, você precisa enviar a lista de cartões com co-brand para o time de suporte da VTEX por meio de um ticket.
 
 ## Período
 
diff --git a/docs/tutorials/pt/split-payment.md b/docs/tutorials/pt/split-payment.md
index 69a801255..fedc6b3af 100644
--- a/docs/tutorials/pt/split-payment.md
+++ b/docs/tutorials/pt/split-payment.md
@@ -15,9 +15,7 @@ legacySlug: split-de-pagamento
 subcategory: 3tDGibM2tqMyqIyukqmmMw
 ---
 
-<div class="alert alert-warning">
-Esta é uma solução para pagamentos em contextos de marketplace.
-</div>
+>⚠️ Esta é uma solução para pagamentos em contextos de marketplace.
 
 Para garantir que nossos clientes de [marketplace](https://help.vtex.com/pt/tutorial/o-que-e-um-marketplace--680lLJTnmEAmekcC0MIea8) dividam o pagamento entre todos os [sellers](https://help.vtex.com/pt/tutorial/what-is-a-seller) automaticamente, estabeleçam uma comissão baseada em um percentual fixo e permaneçam atuando conforme as regulamentações em vigor, a VTEX oferece o __Split de pagamentos__.
 
@@ -26,9 +24,7 @@ Veja a seguir dois exemplos de cenários de aplicação de split de pagamentos o
 1. Quando o marketplace é responsável por processar o pagamento da compra, a VTEX divide automaticamente esse pagamento para que cada beneficiário receba a sua parte diretamente na própria conta bancária, realizando assim o [Split de recebíveis](https://help.vtex.com/pt/tutorial/split-payment#split-de-recebiveis).
 2. Quando o carrinho envolve sellers que são responsáveis por processar o seu próprio meio de pagamento (sem depender do marketplace), a VTEX cria diferentes transações de pagamento para o Marketplace e os sellers, efetuando o [Split de transação](https://help.vtex.com/pt/tutorial/split-payment#split-de-transacao).
 
-<div class="alert alert-warning">
-A distribuição dos valores de uma compra sempre é realizada conforme os acordos de percentual de comissão pré-definidos entre o marketplace e os sellers.
-</div>
+>⚠️ A distribuição dos valores de uma compra sempre é realizada conforme os acordos de percentual de comissão pré-definidos entre o marketplace e os sellers.
 
 Confira abaixo mais detalhes sobre cada um dos modelos de split de pagamentos:
 
diff --git a/docs/tutorials/pt/store-overview-beta.md b/docs/tutorials/pt/store-overview-beta.md
index 7ffb33ec5..0cfa623e9 100644
--- a/docs/tutorials/pt/store-overview-beta.md
+++ b/docs/tutorials/pt/store-overview-beta.md
@@ -15,9 +15,7 @@ legacySlug: visao-geral-da-loja-beta
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class="alert alert-info"> 
-A versão atualizada da página Visão Geral da Loja (Beta) está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É importante observar que podem ser aplicadas taxas extras no futuro. Além disso, a página Visão Geral atualmente presente no Admin VTEX continuará disponível para uso por enquanto.
-</div>
+>ℹ️ A versão atualizada da página Visão Geral da Loja (Beta) está disponível para uso gratuito no Admin VTEX durante seu período Beta, ou até decidido pela VTEX. É importante observar que podem ser aplicadas taxas extras no futuro. Além disso, a página Visão Geral atualmente presente no Admin VTEX continuará disponível para uso por enquanto.
 
 A página Visão Geral (Beta) em seu Admin VTEX fornece um acompanhamento em tempo real da sua operação no dia atual, oferecendo visibilidade sobre indicadores para que você e sua equipe tenham um feedback rápido das ações realizadas na loja e possam atuar prontamente em melhorias. 
 
@@ -65,9 +63,7 @@ Os dados da página são atualizados com frequências diferentes. Os gráficos n
 | Resultados financeiros | - [Receita captada](#monitoramento) <br>- [Ticket Médio](#metricas)<br>- [Produtos com maior receita](#metricas)                                                                                                                                                                                                                         |
 | Conversão              | - [Taxa de Conversão](#metricas) <br>- [Funil de vendas](#funil-de-vendas) <br>- [Pedidos captados](#monitoramento), comparando com o número de Pedidos cancelados. Dependendo do resultado, isso pode direcionar sua equipe a identificar problemas operacionais no fulfillment ou atendimento ao consumidor que causaram os pedidos cancelados. |
 
-<div class="alert alert-info"> 
-Note que enquanto os gráficos em Monitoramento são atualizados em até três minutos, as Métricas são atualizadas de quinze em quinze minutos, o que pode influenciar a sua análise de resultados. Saiba mais em <a href="#atualizacao-de-dados">Atualização de dados</a>.
-</div>
+>ℹ️ Note que enquanto os gráficos em Monitoramento são atualizados em até três minutos, as Métricas são atualizadas de quinze em quinze minutos, o que pode influenciar a sua análise de resultados. Saiba mais em [Atualização de dados](#atualizacao-de-dados).
 
 ### Analisar resultados de campanhas
 
diff --git a/docs/tutorials/pt/subscription-plans.md b/docs/tutorials/pt/subscription-plans.md
index 94e6c4d09..c06a2e384 100644
--- a/docs/tutorials/pt/subscription-plans.md
+++ b/docs/tutorials/pt/subscription-plans.md
@@ -63,17 +63,13 @@ Cada coluna da lista de planos de assinaturas exibe uma informação sobre o pla
     * **Ativo**: significa que o plano está disponível para utilização dos clientes ao criar novas assinaturas com produtos associados.
     * **Inativo**: significa que o plano não está disponível para uso ao criar novas assinaturas, mesmo que tenha produtos associados.
 
-<div class="alert alert-info">
-<p>Planos inativos são desabilitados somente para novas compras. Caso existam clientes que já haviam criado assinaturas enquanto o plano estava ativo, o plano vai continuar criando pedidos nas frequências estabelecidas durante os próximos ciclos desses clientes mesmo após ser inativado.</p>
-</div>
+>ℹ️ Planos inativos são desabilitados somente para novas compras. Caso existam clientes que já haviam criado assinaturas enquanto o plano estava ativo, o plano vai continuar criando pedidos nas frequências estabelecidas durante os próximos ciclos desses clientes mesmo após ser inativado.
 
 * **Botão** <i class="fas fa-ellipsis-v"></i>: ao clicar neste botão, você pode optar pelas ações a seguir.
     * **Editar**: abre a página de editar o plano de assinatura.
     * **Deletar**: possibilita excluir o plano definitivamente. Antes de deletar, aparece uma tela de confirmação desta opção. Após clicar em `Deletar plano` para confirmar a escolha, essa ação **não** pode ser desfeita.
 
-<div class="alert alert-warning">
-<p>Quando um plano é deletado, os clientes que já compraram nas frequências desse plano <strong>não</strong> terão seus pedidos gerados a partir do próximo ciclo de assinatura. Para impedir o uso ao criar novas assinaturas, mas manter os próximos pedidos dos clientes que já criaram assinaturas no plano em questão, você precisa optar por inativar o plano em vez de deletá-lo.</p>
-</div>
+>⚠️ Quando um plano é deletado, os clientes que já compraram nas frequências desse plano **não** terão seus pedidos gerados a partir do próximo ciclo de assinatura. Para impedir o uso ao criar novas assinaturas, mas manter os próximos pedidos dos clientes que já criaram assinaturas no plano em questão, você precisa optar por inativar o plano em vez de deletá-lo.
 
 ## Mostrar linhas
 
diff --git a/docs/tutorials/pt/support-indicators.md b/docs/tutorials/pt/support-indicators.md
index 3342c1a34..7712e40f4 100644
--- a/docs/tutorials/pt/support-indicators.md
+++ b/docs/tutorials/pt/support-indicators.md
@@ -15,9 +15,7 @@ legacySlug: indicadores-de-suporte
 subcategory: 2A1RNDhwU4kqCN3XimtaD2
 ---
 
-<div class="alert alert-info"> 
- Esse artigo está relacionado com a funcionalidade de <b>Relatório de Indicadores</b>. Caso queira saber mais, acesse<a href="https://help.vtex.com/pt/tutorial/relatorio-de-indicadores--7lbICsrCArXDxUYeeHJ2c5">  Relatório de Indicadores</a>.
-</div>
+>ℹ️ Esse artigo está relacionado com a funcionalidade de **Relatório de Indicadores**. Caso queira saber mais, acesse[  Relatório de Indicadores](https://help.vtex.com/pt/tutorial/relatorio-de-indicadores--7lbICsrCArXDxUYeeHJ2c5).
 
 ## Suporte
 
diff --git a/docs/tutorials/pt/table-of-base-prices.md b/docs/tutorials/pt/table-of-base-prices.md
index 66dae4f96..930bccaec 100644
--- a/docs/tutorials/pt/table-of-base-prices.md
+++ b/docs/tutorials/pt/table-of-base-prices.md
@@ -25,9 +25,7 @@ Para entender como preencher a [planilha de cadastro de preço base](https://hel
 
 - **List Price**: preço de lista é um preço que funciona como um preço antigo de SKU que recebeu um desconto. Também é conhecido como “preço De” e pode ser exibido na vitrine da sua loja. Este é um campo opcional no cadastro de um preço.
 
-<div class="alert alert-info">
-<p>Nas colunas <b>Cost Price</b>, <b>Base Price</b> e <b>List Price</b>, você pode inserir valores com casas decimais separadas por ponto. Exemplo: <code>4.95</code>.</p>
-</div>
+>ℹ️ Nas colunas **Cost Price**, **Base Price** e **List Price**, você pode inserir valores com casas decimais separadas por ponto. Exemplo: `4.95`.
 
 Os próximos campos são opcionais na planilha, exportados somente para exibição e para facilitar a identificação de um SKU. Para visualizá-los na planilha, é necessário selecionar a opção *Incluir metadados nas tabelas exportadas* na exportação.
 
diff --git a/docs/tutorials/pt/telesales-toolbar.md b/docs/tutorials/pt/telesales-toolbar.md
index 89018e6f5..616e41ca8 100644
--- a/docs/tutorials/pt/telesales-toolbar.md
+++ b/docs/tutorials/pt/telesales-toolbar.md
@@ -29,9 +29,7 @@ Para habilitar a toolbar de televendas, é necessário que o administrador da lo
 
 Para saber como customizar a aparência da Toolbar no módulo **CMS**, confira o artigo [Customizar a Toolbar de televendas](https://help.vtex.com/pt/tutorial/customizar-a-toolbar-de-televendas--1XEz1zqO3KyIuwC4asUsOg).
 
-<div class="alert alert-warning">
-<p>Para lojas desenvolvidas no <a href="https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io">VTEX IO</a>, é necessário configurar o aplicativo <strong>VTEX Telemarketing</strong> para habilitar e customizar a toolbar de televendas. Para saber mais sobre esse processo, acesse o guia <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-telemarketing">VTEX Telemarketing</a>.</p>
-</div>
+>⚠️ Para lojas desenvolvidas no [VTEX IO](https://developers.vtex.com/vtex-developer-docs/docs/what-is-vtex-io), é necessário configurar o aplicativo **VTEX Telemarketing** para habilitar e customizar a toolbar de televendas. Para saber mais sobre esse processo, acesse o guia [VTEX Telemarketing](https://developers.vtex.com/vtex-developer-docs/docs/vtex-telemarketing).
 
 ## Entrar como cliente
 
diff --git a/docs/tutorials/pt/testing-webservice-using-soapui.md b/docs/tutorials/pt/testing-webservice-using-soapui.md
index 9110fd2c3..7e0a760cc 100644
--- a/docs/tutorials/pt/testing-webservice-using-soapui.md
+++ b/docs/tutorials/pt/testing-webservice-using-soapui.md
@@ -15,11 +15,13 @@ legacySlug: testando-webservice-com-soapui
 subcategory: 1vwB9FtTSQmcSewQw02QoW
 ---
 
-<div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
-<p><strong>Todos os outros métodos do Web Service serão descontinuados no dia 28/02/2017.</strong></p>
-<p>Use as APIs REST equivalentes, disponíveis em nosso <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: somente os métodos SOAP pertinentes ao **catálogo** são válidos.
+>
+> **Todos os outros métodos do Web Service serão descontinuados no dia 28/02/2017.**
+>
+> Use as APIs REST equivalentes, disponíveis em nosso [Developer Docs](//help.vtex.com/developer-docs/).
 
-<div class="alert alert-warning">As configurações documentadas neste artigo são realizadas em um ambiente fora da VTEX, portanto podem ser descontinuadas sem prévio aviso.</div>
+>⚠️ As configurações documentadas neste artigo são realizadas em um ambiente fora da VTEX, portanto podem ser descontinuadas sem prévio aviso.
 
 SoapUI é uma ferramenta que pode ser utilizada para simular conexão e execução de métodos de um determinado webservice, sem ter a necessidade de fazer isso apenas via programação.
 
@@ -44,6 +46,8 @@ Efetue o login com os dados do Web Service desejado. Após efetuar o login, voc
 
 ![](https://images.contentful.com/alneenqid6w5/3TBC8YgtvyQ6sMQAyQACOg/5e14a72feaa3bf0d00a8b245d56788d1/2.png)
 
-<div class="alert alert-danger"><p>Atenção: somente os métodos SOAP pertinentes ao <strong>catálogo</strong> são válidos.</p>
-<p><strong>Todos os outros métodos estão descontinuados.</strong></p>
-<p>Use as APIs REST equivalentes, disponíveis em nosso <a href="//help.vtex.com/developer-docs/">Developer Docs</a>.</p></div>
+>❗ Atenção: somente os métodos SOAP pertinentes ao **catálogo** são válidos.
+>
+> **Todos os outros métodos estão descontinuados.**
+>
+> Use as APIs REST equivalentes, disponíveis em nosso [Developer Docs](//help.vtex.com/developer-docs/).
diff --git a/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md b/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md
index 1f8798282..c7961ee46 100644
--- a/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md
+++ b/docs/tutorials/pt/the-order-was-split-into-packages-with-separate-deliveries.md
@@ -32,9 +32,7 @@ A data de entrega de cada pacote é alterada de acordo com o valor do `shippingE
 
 Para evitar uma divisão de pacotes em pedidos que incluam produtos de pré-venda, você pode configurar o [agrupamento de produtos por remessa](https://help.vtex.com/pt/tutorial/como-funciona-a-remessa). Desta forma, é possível agrupar em um único conjunto todos os pacotes a serem entregues pela mesma transportadora e provenientes da mesma [doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj).
 
-<div class="alert alert-danger">
-Ao configurar o agrupamento da remessa, esse comportamento será aplicado a todos os pedidos com datas de entrega distintas e não somente aos casos envolvendo produtos de pré-venda.
-</div>
+>❗ Ao configurar o agrupamento da remessa, esse comportamento será aplicado a todos os pedidos com datas de entrega distintas e não somente aos casos envolvendo produtos de pré-venda.
 
 ### Configurando a remessa
 
diff --git a/docs/tutorials/pt/the-risk-assessment-process.md b/docs/tutorials/pt/the-risk-assessment-process.md
index 43bee4ee3..39cf7f43c 100644
--- a/docs/tutorials/pt/the-risk-assessment-process.md
+++ b/docs/tutorials/pt/the-risk-assessment-process.md
@@ -62,7 +62,5 @@ Tópicos:
 Insira abaixo seu [nome de conta](https://help.vtex.com/pt/tutorial/what-is-an-account-name--i0mIGLcg3QyEy8OCicEoC#) VTEX para acessar a documentação.
 <iframe src="https://help.vtex.com/insertaccountname?id=1ayXEtqawI9yuxFXutiITh" title="Insira seu nome de conta e clique no botão." frameBorder="0" width="400" height="50"></iframe>
 
-<div class="alert alert-warning">
-  Se está tendo dificuldades para acessar o conteúdo dos FAQs, tente instalar a versão mais recente do aplicativo <code>vtex.admin-docs</code> usando a <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference">CLI da VTEX</a> e repetir o processo.
-</div>
+>⚠️ Se está tendo dificuldades para acessar o conteúdo dos FAQs, tente instalar a versão mais recente do aplicativo `vtex.admin-docs` usando a [CLI da VTEX](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-vtex-io-cli-installation-and-command-reference) e repetir o processo.
 
diff --git a/docs/tutorials/pt/total-shipping-cost.md b/docs/tutorials/pt/total-shipping-cost.md
index 2df25d377..9adab7e28 100644
--- a/docs/tutorials/pt/total-shipping-cost.md
+++ b/docs/tutorials/pt/total-shipping-cost.md
@@ -32,8 +32,6 @@ Sendo assim, de modo geral, o custo final de envio pode ser calculado desta form
 
 ![Custo-final-envio-PT](https://images.contentful.com/alneenqid6w5/5qeoN5AQPvoWyOPcNW3J6q/dc18eacbd9078557282f53cecb2ae4cf/Custo-final-envio-PT.svg)
 
-<div class="alert alert-danger">
-Se o <b>adicional por preço</b> for menor que o <b>adicional de seguro</b>, a tarifa que é considerada é a do adicional de seguro e o adicional por preço é desconsiderado no cálculo da tarifa final.<p>
-A escolha da transportadora para o envio dos itens considera apenas o preço da Tarifa de envio, desconsiderando os custos da doca e estoque (caso existam). Para simular o cenário de entrega para o cliente, use o <a href="https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144">Simulador de envio</a>.
-</div>
+>❗ Se o **adicional por preço** for menor que o **adicional de seguro**, a tarifa que é considerada é a do adicional de seguro e o adicional por preço é desconsiderado no cálculo da tarifa final.<p>
+> A escolha da transportadora para o envio dos itens considera apenas o preço da Tarifa de envio, desconsiderando os custos da doca e estoque (caso existam). Para simular o cenário de entrega para o cliente, use o [Simulador de envio](https://help.vtex.com/pt/tutorial/simulacao-de-frete--tutorials_144).
 
diff --git a/docs/tutorials/pt/tracking-your-sales-analytics.md b/docs/tutorials/pt/tracking-your-sales-analytics.md
index 34de764a1..c2ed69b02 100644
--- a/docs/tutorials/pt/tracking-your-sales-analytics.md
+++ b/docs/tutorials/pt/tracking-your-sales-analytics.md
@@ -27,7 +27,7 @@ A tabela abaixo descreve as principais métricas disponíveis no Insights. Todas
 | Receita      | Valor total apurado pelos pedidos aprovados |
 | Ticket médio | Valor médio de receita por pedido |
 
-<div class="alert alert-warning">Não temos acesso aos dados de sessões e conversão referentes a fluxos de compra realizados fora de lojas VTEX. Por isso, pedidos realizados em marketplaces não são incluídos nas métricas do Insights.</div>
+>⚠️ Não temos acesso aos dados de sessões e conversão referentes a fluxos de compra realizados fora de lojas VTEX. Por isso, pedidos realizados em marketplaces não são incluídos nas métricas do Insights.
 
 ## Conhecendo a interface
 
diff --git a/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md b/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md
index 518e65070..cc38b0ea7 100644
--- a/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md
+++ b/docs/tutorials/pt/tutorial-vtex-tracking-mobile-app.md
@@ -24,9 +24,7 @@ O aplicativo móvel do [VTEX Tracking](https://help.vtex.com/pt/tutorial/visao-g
   - [Pausar entrega](#pausar-entrega).
   - [Coletar dados do recebedor](#finalizacao-da-entrega).
 
-<div class="alert alert-info">
-A disponibilidade das funcionalidades listadas acima está condicionada à ativação por parte  da empresa de serviço de entrega.
-</div>
+>ℹ️ A disponibilidade das funcionalidades listadas acima está condicionada à ativação por parte  da empresa de serviço de entrega.
 
 ## Como instalar
 
@@ -37,9 +35,7 @@ Para instalar o aplicativo:
 3. Clique em __Instalar__.
 4. Aguarde o download e instalação.
 
-<div class="alert alert-warning">
-O aplicativo VTEX Tracking está disponível atualmente apenas para sistema Android.
-</div>
+>⚠️ O aplicativo VTEX Tracking está disponível atualmente apenas para sistema Android.
 
 ## Como acessar
 
@@ -56,9 +52,7 @@ Com os dados do cadastro em mãos, siga as instruções abaixo para acesso:
   <img src="https:////images.ctfassets.net/alneenqid6w5/3a3HtOlFA2xpLn5UsufytL/affee1c9cccda41ad54258fd8e99e09d/tela1seriousblack.png" width="250" height="450">
 </p>
 
-<div class="alert alert-warning">
-Caso o aplicativo apresente instabilidade, recomendamos a limpeza do cache do dispositivo móvel  e/ou a re-instalação do aplicativo.
-</div>
+>⚠️ Caso o aplicativo apresente instabilidade, recomendamos a limpeza do cache do dispositivo móvel  e/ou a re-instalação do aplicativo.
 
 ### Recuperar senha
 
@@ -70,9 +64,7 @@ Abra o aplicativo.
 3. Preencha o email.
 4. Clique em __ENVIAR__.
 
-<div class="alert alert-warning">
-Utilize como email de recuperação o mesmo email que foi cadastrado na plataforma web (veja Como acessar). Caso você não tenha a informação sobre um email cadastrado, entre em contato com a empresa de serviço de entrega.
-</div>
+>⚠️ Utilize como email de recuperação o mesmo email que foi cadastrado na plataforma web (veja Como acessar). Caso você não tenha a informação sobre um email cadastrado, entre em contato com a empresa de serviço de entrega.
 
 <p align="center">
   <img src="//images.ctfassets.net/alneenqid6w5/1CSmj8fe1tImUFUT6URnUc/42133d558ae524c9559cac2a13d2a5a8/tela2seriousblack.png" width="250" height="450">
@@ -81,16 +73,12 @@ Utilize como email de recuperação o mesmo email que foi cadastrado na platafor
  ## Como fazer uma entrega 
 
 O aplicativo apresenta na tela inicial, uma lista com as as entregas do dia a serem realizadas de acordo com a rota configurada. As rotas são os trajetos planejados a serem percorridos desde o ponto de coleta até o ponto de entrega. 
-<div class="alert alert-info">
-Para que as rotas estejam disponíveis no aplicativo é necessário que elas sejam previamente planejadas na plataforma web pela empresa de serviço de entregas. Entre em contato com a empresa, caso não tenha rotas disponíveis para você. 
-</div>
+>ℹ️ Para que as rotas estejam disponíveis no aplicativo é necessário que elas sejam previamente planejadas na plataforma web pela empresa de serviço de entregas. Entre em contato com a empresa, caso não tenha rotas disponíveis para você.
 
 <p align="center">
   <img src="//images.ctfassets.net/alneenqid6w5/5qjV5bJ7TIcbw1gNMZ41sB/ebd8ec4093e7e46852e0f297d705cac6/tela3seriousblack.png" width="230" height="450">
 </p>
-<div class="alert alert-danger">
-  Use a opção <b>PAUSAR</b> com cautela pois ao iniciar novamente a rota, os destinatários receberão notificações do novo início da entrega. 
-</div>
+>❗ Use a opção **PAUSAR** com cautela pois ao iniciar novamente a rota, os destinatários receberão notificações do novo início da entrega.
 
 ### Realizar entrega
 Para realizar uma entrega é necessário primeiro iniciá-la. Para tanto:
@@ -102,9 +90,7 @@ Abra o aplicativo.
 
 Após a inicialização da entrega, o destinatário passa a receber notificações via SMS com atualizações automáticas da rota de entrega e você tem acesso à detalhes como nome do destinatário, número de nota fiscal, série da nota fiscal, tipo de entrega e endereço de entrega podendo  usar aplicativos externos como Google Maps ou o Waze para abrir no mapa.
 
-<div class="alert alert-warning">
-É importante ressaltar que por conta de configurações específicas, é possível que seu aplicativo não apresente todas as funcionalidades ou apareçam de forma diferente na sua tela.
-</div>
+>⚠️ É importante ressaltar que por conta de configurações específicas, é possível que seu aplicativo não apresente todas as funcionalidades ou apareçam de forma diferente na sua tela.
 
 <a id="Fotos"> Durante a entrega,</a> você pode adicionar fotos que comprovem, por exemplo, a sua localização, a execução da entrega ou quaisquer outros motivos que requeiram registro fotográfico. Para adicionar:
 
@@ -116,26 +102,26 @@ Após a inicialização da entrega, o destinatário passa a receber notificaçõ
   <img src="//images.ctfassets.net/alneenqid6w5/5t3tVl6Y5y2okAuB50jDkH/b73c7ae1b8a208c22396855e5216c4c8/tela4seriousblack.png" width="230" height="450">
 </p>
 
-<div class="alert alert-info">
-Essa opção pode também estar disponível antes do início da rota mediante a configuração  pela empresa de serviço de entrega. Assim, ao invés de FOTOS estar disponível durante a entrega, ela aparecerá antes mesmo do início da rota. Se este for o caso, é preciso fotografar antes de realizar o início da rota. Então:
-<ol>
-  <li>Clique em <b>Fotografar.</b></li>
-  <li>Tire a foto.</li>
-  <li>Clique em <b>Iniciar</b> para iniciar a rota.</li>
-</ol>
-  <figure class="half">
-  <table class="center">
-    <tr>
-      <td>
-        <img src="//images.ctfassets.net/alneenqid6w5/7ISKJH3ZW7nEQZkR95hKjk/f51efbf5bcdfe29e73c96728baad3519/tela5seriousblack.png" width="250" height="450">
-      </td>
-      <td>
-        <img src="//images.ctfassets.net/alneenqid6w5/6buR2z5OvycFvz340pLxsI/52aed865af8c9b7d557c99dfda43896d/tela6seriousblack.png" width="250" height="450">
-      </td>
-    </tr>
-  </table>
-</figure>
- </div>
+>ℹ️ Essa opção pode também estar disponível antes do início da rota mediante a configuração  pela empresa de serviço de entrega. Assim, ao invés de FOTOS estar disponível durante a entrega, ela aparecerá antes mesmo do início da rota. Se este for o caso, é preciso fotografar antes de realizar o início da rota. Então:
+>
+> 1. Clique em **Fotografar.**
+>
+> 2. Tire a foto.
+>
+> 3. Clique em **Iniciar** para iniciar a rota.
+>
+> <figure class="half">
+>   <table class="center">
+>     <tr>
+>       <td>
+>         <img src="//images.ctfassets.net/alneenqid6w5/7ISKJH3ZW7nEQZkR95hKjk/f51efbf5bcdfe29e73c96728baad3519/tela5seriousblack.png" width="250" height="450">
+>       </td>
+>       <td>
+>         <img src="//images.ctfassets.net/alneenqid6w5/6buR2z5OvycFvz340pLxsI/52aed865af8c9b7d557c99dfda43896d/tela6seriousblack.png" width="250" height="450">
+>       </td>
+>     </tr>
+>   </table>
+> </figure>
 
   ### Ocorrências durante a entrega
 <a id="Reportar_problemas">Durante a entrega, </a> caso aconteça uma ocorrência, como por exemplo ausência do morador e/ou endereço errado, é possível fazer um reporte. 
@@ -182,9 +168,7 @@ Ao escolher uma ocorrência que tenha possibilidade de abertura de chat, uma men
   <img src="//images.ctfassets.net/alneenqid6w5/5KMsyiWbF99kWOHlLR4cLO/78f5f101f39f66d04bcdeea3e80c7645/tela8seriousblack.jpg" width="230" height="450">
 </p>
 
-<div class="alert alert-danger">
-  Use a opção <b>PAUSAR</b> com cautela pois ao iniciar novamente a rota, os destinatários receberão notificações do novo início da entrega. 
-</div>
+>❗ Use a opção **PAUSAR** com cautela pois ao iniciar novamente a rota, os destinatários receberão notificações do novo início da entrega.
 
 ### Finalização da Entrega
 <a id="FinalEntrega">Depois de chegar ao</a> destinatário e efetuar a entrega, é preciso finalizar a entrega no aplicativo e colher os dados do recebedor: 
@@ -226,9 +210,7 @@ Ao voltar para a página de finalização, será preciso escrever um comentário
 
 Após esses passos, a entrega é finalizada e o  aplicativo  abre uma caixa de diálogo perguntando se você deseja iniciar a próxima entrega da lista. Caso deseje, clique em __SIM__. 
 
-<div class="alert alert-info">
-Se esta caixa de diálogo não abrir automaticamente, na próxima entrega da tela de listas de entrega, clique em <b>Iniciar</b> e siga novamente as instruções de <a href="#Iniciar_rota">Como fazer uma entrega</a>.
-</div>
+>ℹ️ Se esta caixa de diálogo não abrir automaticamente, na próxima entrega da tela de listas de entrega, clique em **Iniciar** e siga novamente as instruções de [Como fazer uma entrega](#Iniciar_rota).
 
 <figure class="half">
   <table class="center">
diff --git a/docs/tutorials/pt/understand-vtex-payment-fees.md b/docs/tutorials/pt/understand-vtex-payment-fees.md
index 5eaa9b018..444e90a3d 100644
--- a/docs/tutorials/pt/understand-vtex-payment-fees.md
+++ b/docs/tutorials/pt/understand-vtex-payment-fees.md
@@ -26,6 +26,4 @@ Por exemplo, digamos que um lojista opte por trabalhar com as  taxas do Plano Av
 - __À vista__: já que a taxa de crédito é 2,5%, o valor que é descontado pelo VTEX Payment é de R$2,50. 
 - __Parcelado__: neste caso, a taxa é de 2,7%. Logo, R$ 2,70 são descontados pelo VTEX Payment. 
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: no exemplo acima, as taxas de crédito para produtos parcelados eram as mesmas para todas as parcelas. Entretanto, isso não é uma regra. As taxas podem variar diante do número de parcelas que o pagamento do produto for dividido.
-</div> 
+>ℹ️ **Atenção**: no exemplo acima, as taxas de crédito para produtos parcelados eram as mesmas para todas as parcelas. Entretanto, isso não é uma regra. As taxas podem variar diante do número de parcelas que o pagamento do produto for dividido. 
diff --git a/docs/tutorials/pt/understanding-competition-of-promotions.md b/docs/tutorials/pt/understanding-competition-of-promotions.md
index cde08a719..41e74feb3 100644
--- a/docs/tutorials/pt/understanding-competition-of-promotions.md
+++ b/docs/tutorials/pt/understanding-competition-of-promotions.md
@@ -84,8 +84,7 @@ Logo, a sequência de aplicação é:
 
 ![promocao3 PT](https://images.ctfassets.net/alneenqid6w5/1LKDzbLkhua8Gk284SEwsk/997fdac9b6380c68a729bf4d48e20af8/promocao3_PT.png)
 
-<div class="alert alert-warning">
-Pedidos de origem <a href="https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406">Marketplace</a> e Fulfillment não reconhecem acúmulo de promoção, uma vez que o uso de promoções em Marketplaces VTEX ou externos é restrito a alguns tipos específicos.</div>
+>⚠️ Pedidos de origem [Marketplace](https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406) e Fulfillment não reconhecem acúmulo de promoção, uma vez que o uso de promoções em Marketplaces VTEX ou externos é restrito a alguns tipos específicos.
 
 ## Estratégias de concorrência de promoções
 
@@ -100,8 +99,7 @@ Veja a seguir as duas estratégias de concorrência de promoções:
 - [Concorrência por cenário](#concorrencia-por-cenario)
 - [Concorrência por item](#concorrencia-por-item)
 
-<div class="alert alert-info">
-Por padrão, todas as contas seguem a estratégia de concorrência por cenário. Caso o modelo de concorrência por item atenda melhor suas necessidades de negócio, <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM">abra um chamado com nosso time de suporte</a> e solicite a mudança.</div>
+>ℹ️ Por padrão, todas as contas seguem a estratégia de concorrência por cenário. Caso o modelo de concorrência por item atenda melhor suas necessidades de negócio, [abra um chamado com nosso time de suporte](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM) e solicite a mudança.
 
 ### Concorrência por cenário
 
diff --git a/docs/tutorials/pt/understanding-how-indexation-works.md b/docs/tutorials/pt/understanding-how-indexation-works.md
index a17b7873d..bd448f8c8 100644
--- a/docs/tutorials/pt/understanding-how-indexation-works.md
+++ b/docs/tutorials/pt/understanding-how-indexation-works.md
@@ -15,10 +15,9 @@ legacySlug: entendendo-o-funcionamento-da-indexacao
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class="alert alert-warning">
-<p>Tutorial válido apenas para lojas que utilizam a busca do <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a>.</p>
-<p>Se a sua loja utiliza o <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">Intelligent Search</a>, consulte a página <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH">Histórico da Indexação</a> para acompanhar o processo de indexação.</p>
-</div>
+>⚠️ Tutorial válido apenas para lojas que utilizam a busca do [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj).
+>
+> Se a sua loja utiliza o [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG), consulte a página [Histórico da Indexação](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/4flMwTaQL8FRKl1YT58ezH) para acompanhar o processo de indexação.
 
 A indexação é um processo que prepara os dados gerais do SKU, tais como dados de catálogo, de preço e de estoque e atualiza as informações para servir de base para pesquisas e montagens das prateleiras do site.
 
diff --git a/docs/tutorials/pt/understanding-incomplete-orders.md b/docs/tutorials/pt/understanding-incomplete-orders.md
index fda2ecf5e..b88b2c108 100644
--- a/docs/tutorials/pt/understanding-incomplete-orders.md
+++ b/docs/tutorials/pt/understanding-incomplete-orders.md
@@ -23,9 +23,7 @@ Além disso, todos os pedidos incompletos não têm Workflow e esse é um compor
 
 Como um pedido incompleto foi interrompido, ativar um Workflow para uma situação inativa não seria funcional.
 
-<div class="alert alert-danger"> 
-É recomendado que caso haja um Pedido Incompleto, o pedido seja refeito na loja. Pedidos incompletos são utilizados apenas para registro, e a plataforma não faz novas requisições para um pedido incompleto. Assim, se um pedido está incompleto e o cliente quer dar continuidade ao pedido, ele precisa criar um novo pedido com os mesmos itens. 
-</div>
+>❗ É recomendado que caso haja um Pedido Incompleto, o pedido seja refeito na loja. Pedidos incompletos são utilizados apenas para registro, e a plataforma não faz novas requisições para um pedido incompleto. Assim, se um pedido está incompleto e o cliente quer dar continuidade ao pedido, ele precisa criar um novo pedido com os mesmos itens.
 
 Desse modo, processo segue como de costume.
 
diff --git a/docs/tutorials/pt/understanding-the-conversation-tracker.md b/docs/tutorials/pt/understanding-the-conversation-tracker.md
index f0cfb6bdd..cd106f5c6 100644
--- a/docs/tutorials/pt/understanding-the-conversation-tracker.md
+++ b/docs/tutorials/pt/understanding-the-conversation-tracker.md
@@ -24,9 +24,7 @@ O Conversation Tracker pode ter duas configurações:
 - **Complexa** - Cria um alias (email alternativo) de forma não legível evitando assim a identificação do email por sistemas externos, também vincula qualquer email enviado a este endereço a linha do tempo do pedido. Normalmente a loja com esta configuração apresentaram o alias da seguinte forma: `ff2e6348a53a4d449af92be2a1011328@ct.vtex.com.br`
 - **Simples** - Cria um alias (email alternativo) de menor complexidade para o email do usuário comprador, isso faz com que o email continue legível na UI do OMS e quando visto no JSON do pedido. Outro ponto importante é que o endereço do emissor (loja) também é mascarado da mesma forma que o email do usuário no JSON. É necessário para que o sistema possa vincular os emails dessa compra na linha do tempo do pedido. Normalmente a loja com esta configuração apresentarão o alias da seguinte forma: `nomepessoa@vtex.com.br-207700027841b.ct.vtex.com.br`
 
-<div class="alert alert-info">
-Todas as lojas vêm com a configuração <strong>Complexa</strong> por padrão.
-</div>
+>ℹ️ Todas as lojas vêm com a configuração **Complexa** por padrão.
 
 O  Conversation Tracker oferece diversas outras vantagens, principalmente em questões de segurança:
 
diff --git a/docs/tutorials/pt/understanding-the-cubic-weight-factor.md b/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
index 1ab553f4e..8ecfda512 100644
--- a/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
+++ b/docs/tutorials/pt/understanding-the-cubic-weight-factor.md
@@ -34,9 +34,7 @@ O fator de cubagem é o coeficiente resultante da relação entre peso e volume
 
 O cálculo do peso cubado é realizado efetuando a multiplicação do Comprimento pela Largura e pela Altura e, em seguida, a divisão pelo Fator de cubagem fornecido pela transportadora.
 
-<div class="alert alert-warning">
-Ao realizar o cálculo do peso cúbico, a plataforma VTEX não utiliza unidades de medida e os números gerados são absolutos. Ou seja, os números e medidas que você levar em consideração serão aqueles do resultado final. Vale ressaltar que a unidade de medida do seu cálculo deve ser igual àquela utilizada pela transportadora em questão.
-</div>
+>⚠️ Ao realizar o cálculo do peso cúbico, a plataforma VTEX não utiliza unidades de medida e os números gerados são absolutos. Ou seja, os números e medidas que você levar em consideração serão aqueles do resultado final. Vale ressaltar que a unidade de medida do seu cálculo deve ser igual àquela utilizada pela transportadora em questão.
 
 Observe o exemplo a seguir:
 
diff --git a/docs/tutorials/pt/understanding-the-updating-of-the-xml.md b/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
index 8341eef55..dedb0a5c1 100644
--- a/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
+++ b/docs/tutorials/pt/understanding-the-updating-of-the-xml.md
@@ -23,4 +23,6 @@ Essa consulta significa que o XML foi chamado em menos de 48 horas. Aqueles XML
 
 [![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png "![xml](https://images.contentful.com/alneenqid6w5/4f0ryUsnO8UQM8micg88EQ/8127b7bad05fd3b27fcc84f0754e7ea0/xml.png)")
 
-<div class="alert alert-info">Caso a opção "Exibir os SKUs sem saldo disponível (esgotados) em Estoque entre os resultados" esteja desmarcada, os produtos/SKUs que estiverem esgotados não aparecerão no XML. <br>Produtos inativos também <strong>não</strong> aparecem no XML.</div>
+>ℹ️ Caso a opção "Exibir os SKUs sem saldo disponível (esgotados) em Estoque entre os resultados" esteja desmarcada, os produtos/SKUs que estiverem esgotados não aparecerão no XML. 
+>
+> Produtos inativos também **não** aparecem no XML.
diff --git a/docs/tutorials/pt/understanding-vtex-matcher-scoring.md b/docs/tutorials/pt/understanding-vtex-matcher-scoring.md
index 26ff2bb47..daca1f221 100644
--- a/docs/tutorials/pt/understanding-vtex-matcher-scoring.md
+++ b/docs/tutorials/pt/understanding-vtex-matcher-scoring.md
@@ -42,9 +42,7 @@ O Score final determina o status do produto, entre as opções *Aprovado*, *Nega
 ## Catalogação
 Confira na tabela abaixo como cada pontuação gera um status e uma ação correspondente.
 
-<div class="alert alert-info">
-A pontuação máxima do VTEX Matcher para catalogação automática é 95. Scores maiores que 95 requerem catalogação manual.
-</div>
+>ℹ️ A pontuação máxima do VTEX Matcher para catalogação automática é 95. Scores maiores que 95 requerem catalogação manual.
 
 | Score      | Status   | Cenário                                                                                                                                                                | Ação                                                                                                                                                                                                                                                                                                           |
 |------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
diff --git a/docs/tutorials/pt/understanding-vtexs-email-capture-system.md b/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
index a30446a1c..31e1fac54 100644
--- a/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
+++ b/docs/tutorials/pt/understanding-vtexs-email-capture-system.md
@@ -39,16 +39,12 @@ Para melhor compreensão, iremos apresentar um cenário (dividido em 3 etapas),
 |------------------|------------------|
 | Clica em `Ir para entrega`. | Checkout solicita que o RC.JS transfira o endereço de e-mail e as informações do carrinho para o Master Data (por meio do Profile System). |
 
-<div class="alert alert-warning">
-Para que a função do <a href="https://help.vtex.com/pt/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#">carrinho abandonado</a> possa ser utilizada, é necessário que o usuário tenha preenchido as seguintes informações: e-mail, nome, sobrenome e CPF. A falta de um destes dados, impossibilita a utilização do carrinho abandonado.
-</div>
+>⚠️ Para que a função do [carrinho abandonado](https://help.vtex.com/pt/tutorial/acesse-o-carrinho-abandonado-dos-clientes--4bbXy1TlzJaiCr41xKDN4e#) possa ser utilizada, é necessário que o usuário tenha preenchido as seguintes informações: e-mail, nome, sobrenome e CPF. A falta de um destes dados, impossibilita a utilização do carrinho abandonado.
 
 | __Usuário__ | __Plataforma VTEX__ |
 |------------------|------------------|
 | Preenche as informações de frete e pagamento. | O orderForm do Checkout torna-se um pedido e é transmitido para o OMS da VTEX. As informações completas do usuário (nome, sobrenome, e-mail, carrinho e todas as informações adicionais) são transmitidas para o Master Data. A captura de e-mail pode levar até 46 minutos para ser corretamente refletida no CRM. |
 
-<div class="alert alert-info">
-Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
-</div>
+>ℹ️ Cada módulo da VTEX é responsável por solicitar ao RC.JS que transmita os dados capturados na sessão. O RC.JS tem por função agir como um "mensageiro" de informações.
 
 ![image (3)](https://images.ctfassets.net/alneenqid6w5/18dCifD9tOEo8mgUocamIc/958e0da9d2c7aa724f5c1c80bb0b616e/image__3_.png)
diff --git a/docs/tutorials/pt/updating-prices-in-marketplaces.md b/docs/tutorials/pt/updating-prices-in-marketplaces.md
index b5f555bac..bbf0fc0e4 100644
--- a/docs/tutorials/pt/updating-prices-in-marketplaces.md
+++ b/docs/tutorials/pt/updating-prices-in-marketplaces.md
@@ -20,6 +20,4 @@ A atualização de preços em marketplaces depende de dois fatores:
 - Cadastro de preços para os produtos na [tabela de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) associada à política comercial usada na integração com o marketplace.
 - [Indexação do produto](https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao--tutorials_256) após cadastro do novo preço.
 
-<div class="alert alert-warning">
-  <p>Apenas <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj">preços fixos</a> são utilizados nas nossas integrações nativas com marketplaces. Outros cenários previstos na <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx">arquitetura do sistema de preços</a> estão disponíveis apenas para marketplace VTEX-VTEX.</p>
-</div>
+>⚠️ Apenas [preços fixos](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3g39iXkQza4AW7C7L814mj) são utilizados nas nossas integrações nativas com marketplaces. Outros cenários previstos na [arquitetura do sistema de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/7GptzvlPDVM11ojEjywIQx) estão disponíveis apenas para marketplace VTEX-VTEX.
diff --git a/docs/tutorials/pt/url-mapping-301-redirect.md b/docs/tutorials/pt/url-mapping-301-redirect.md
index 99a2986b3..0bc1be655 100644
--- a/docs/tutorials/pt/url-mapping-301-redirect.md
+++ b/docs/tutorials/pt/url-mapping-301-redirect.md
@@ -15,9 +15,7 @@ legacySlug: adicionar-ou-editar-um-mapeamento-de-url-manualmente
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class="alert alert-warning">
-<p>Este tutorial é para lojas no CMS Portal legado. Para outras lojas, você faz essa configuração através de <a href="https://help.vtex.com/pt/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc">Páginas</a>. Acesse a documentação <a href="https://help.vtex.com/pt/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV">Gerenciando redirecionamentos de URL</a> para mais informações.</p>
-</div>
+>⚠️ Este tutorial é para lojas no CMS Portal legado. Para outras lojas, você faz essa configuração através de [Páginas](https://help.vtex.com/pt/tutorial/paginas-visao-geral--5iBUUJbK5NqG6OxlDrGNzc). Acesse a documentação [Gerenciando redirecionamentos de URL](https://help.vtex.com/pt/tutorial/gerenciando-redirecionamentos-de-url--3UJuFrU8imSVWg134mkvJV) para mais informações.
 
 Os mapeamentos de URLs são utilizados para redirecionar URLs específicas para outras. Esse recurso é muito útil quando a loja já possui URLs indexadas em buscadores e pretende redirecioná-las para outras mais atrativas, mantendo o SEO e evitando erros de indexação.
 
@@ -46,9 +44,7 @@ Existem duas formas de adicionar e alterar um Mapeamento de URL:
 - **End date:** data e hora em que o mapeamento deixará de ser considerado.
 - **Active:** opção se o mapeamento está ativo ou inativo.
 
-<div class="alert alert-info"> 
-  <p>Para criar um mapeamento para home (diretório raiz) preencha o campo <b>URL Para</b> com uma barra <code>/</code>.</p>
-</div>
+>ℹ️ Para criar um mapeamento para home (diretório raiz) preencha o campo **URL Para** com uma barra `/`.
 
 ## Importação por Planilha
 
diff --git a/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md b/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
index 61c68a105..35c3426d4 100644
--- a/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
+++ b/docs/tutorials/pt/using-session-manager-to-track-browsing-sessions-in-vtex-stores.md
@@ -32,7 +32,7 @@ Por exemplo, um usuário com um link de campanha específico pode ter uma tabela
 
 Além de obter informações de sessão para um dispositivo que esteja navegando pela infraestrutura da VTEX, o Session Manager permite que você armazene *dados customizados* naquela sessão. Estas informações são facilmente recuperáveis e permitem que você evite fazer algo como configurar um cookie para registrar informações específicas sobre um usuário. 
 
-<div class="alert alert-info">O Session Manager também foi construído para permitir que desenvolvedores criem seus próprios triggers e lógica de processamento. Ainda estamos finalizando o desenvolvimento desta solução extensível, mas no futuro você deverá poder configurar a execução condicional de código customizado, de acordo com a presença de valores específicos de parâmetros nos dados de sessão de um usuário.</div>
+>ℹ️ O Session Manager também foi construído para permitir que desenvolvedores criem seus próprios triggers e lógica de processamento. Ainda estamos finalizando o desenvolvimento desta solução extensível, mas no futuro você deverá poder configurar a execução condicional de código customizado, de acordo com a presença de valores específicos de parâmetros nos dados de sessão de um usuário.
 
 ## Agregação de dados de sessão: chamadas create e transform
 Estritamente falando, o Session Manager é um sistema backend de API que armazena e processa dados de sessão contidos em objetos JSON. Cada conta VTEX tem configurações que indicam quais apps instaladas têm uma dependência de sessão e como elas pretendem processar estas informações.
@@ -51,7 +51,7 @@ Transforms frequentemente disparam outras transforms, repetindo até que nenhuma
 6. A App C monitorava o parâmetro de sessão Z, o que disparou a Transform 3
 7. A Transform 3 não teve efeitos colaterais em parâmetros monitorados por apps, portanto o ciclo se encerrou e a sessão foi salva até que outras mudanças sejam feitas.
 
-<div class="alert alert-info">Chamadas transform são feitas para todas as apps simultaneamente para otimização de desempenho. É por isso que a App C foi afetada tanto pela Transform 2 quanto pela Transform 3 - ela não tinha como saber que o resultado da Transform 2 na App B levaria à necessidade de mudanças adicionais nos seus parâmetros de saída.</div>
+>ℹ️ Chamadas transform são feitas para todas as apps simultaneamente para otimização de desempenho. É por isso que a App C foi afetada tanto pela Transform 2 quanto pela Transform 3 - ela não tinha como saber que o resultado da Transform 2 na App B levaria à necessidade de mudanças adicionais nos seus parâmetros de saída.
 
 Quando uma nova sessão é criada, uma versão mais simples desse ciclo é executada, que chamamos de **chamada create**. Todas as apps que tiverem a configuração `RunOnCreate: true` serão notificadas para executar simultaneamente com uma entrada vazia. Se estas apps modificarem quaisquer parâmetros monitorados por outras apps, isto dispara um ciclo de transform que será executado até que as dependências de entrada sejam resolvidas.
 
diff --git a/docs/tutorials/pt/usuarios-vtex-tracking.md b/docs/tutorials/pt/usuarios-vtex-tracking.md
index 152c60b93..11b83b659 100644
--- a/docs/tutorials/pt/usuarios-vtex-tracking.md
+++ b/docs/tutorials/pt/usuarios-vtex-tracking.md
@@ -56,8 +56,7 @@ O relatório contém informações sobre o último acesso, e status do usuário
 
 ## Redefinir senha de acesso
 
-<div class="alert alert-warning">Você não poderá escolher uma nova senha. Se optar por resetar a senha de acesso, o sistema irá gerar uma senha aleatória para o usuário.
-</div>
+>⚠️ Você não poderá escolher uma nova senha. Se optar por resetar a senha de acesso, o sistema irá gerar uma senha aleatória para o usuário.
 
 1. Acesse o módulo **Configurações da Conta**.  
 2. Acesse a aba **Usuários**.  
diff --git a/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md b/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md
index ee848b38f..d8da863ad 100644
--- a/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md
+++ b/docs/tutorials/pt/visao-geral-da-estrutura-do-catalogo.md
@@ -23,9 +23,7 @@ Um exemplo de estrutura de catálogo seria o seguinte:
 
 ![img como funciona o catalogo](https://images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
 
-<div class="alert alert-warning">
-Não é necessário que a sua árvore de categorias possua três níveis. A hierarquia exibida acima é apenas um exemplo. A quantidade de níveis de categoria a ser criada depende muito do setor de atuação de cada loja.
-</div>
+>⚠️ Não é necessário que a sua árvore de categorias possua três níveis. A hierarquia exibida acima é apenas um exemplo. A quantidade de níveis de categoria a ser criada depende muito do setor de atuação de cada loja.
 
 Depois que criar sua loja e cadastrar seus produtos, você conseguirá ter uma visão mais concreta e organizada do que leu aqui. 
 
diff --git a/docs/tutorials/pt/vtex-ad-network-beta.md b/docs/tutorials/pt/vtex-ad-network-beta.md
index 2e9b26a25..4af94c14b 100644
--- a/docs/tutorials/pt/vtex-ad-network-beta.md
+++ b/docs/tutorials/pt/vtex-ad-network-beta.md
@@ -72,9 +72,7 @@ Este processo de priorização ocorre em três etapas:
 
 Uma vez determinados os anúncios exibidos na página, determina-se o valor dos lances. O lance vencedor do leilão terá o valor final do segundo maior lance mais R$ 0,01.
 
-<div class="alert alert-danger">
-É possível que nenhum anúncio seja selecionado com o processo de priorização, caso não haja produtos promovidos que se encaixem no contexto de navegação, na cobertura de loja ou que não tenham orçamento disponível.
-</div>
+>❗ É possível que nenhum anúncio seja selecionado com o processo de priorização, caso não haja produtos promovidos que se encaixem no contexto de navegação, na cobertura de loja ou que não tenham orçamento disponível.
 
 ### Índice de qualidade
 
@@ -109,9 +107,7 @@ Confira abaixo como você pode fazer parte do **VTEX Ad Network**, seja como [lo
 
 ### Lojas
 
-<div class="alert alert-warning">
-Por ora, apenas lojas desenvolvidas com <a href="https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework">Store Framework</a> podem disponibilizar espaço de anúncios.
-</div>
+>⚠️ Por ora, apenas lojas desenvolvidas com [Store Framework](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/67SCtUreXxKYWhZh8n0zvZ#store-framework) podem disponibilizar espaço de anúncios.
 
 Para disponibilizar espaço publicitário na sua loja, você precisa entrar em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ) para solicitar a instalação do app __VTEX Ad Network para lojas__ na sua conta VTEX.
 
diff --git a/docs/tutorials/pt/vtex-admin-start-here.md b/docs/tutorials/pt/vtex-admin-start-here.md
index d4a29f667..e11386e75 100644
--- a/docs/tutorials/pt/vtex-admin-start-here.md
+++ b/docs/tutorials/pt/vtex-admin-start-here.md
@@ -52,9 +52,7 @@ Confira nossos artigos sobre a visão geral de cada menu do seu Admin VTEX, para
 - [Configurações de usuário](https://help.vtex.com/pt/v4/docs/visao-geral-configuracoes-usuario--1qYAvOTZBVYMosJ7tQm3Ry)
 - [Faturas](https://help.vtex.com/pt/v4/docs/billing-overview--CcugO41lhNJzQKpazKYQC)
 
-<div class="alert alert-info">
-Também é possível utilizar a barra de busca na parte superior do Admin VTEX para encontrar páginas específicas no menu lateral. 
-</div>
+>ℹ️ Também é possível utilizar a barra de busca na parte superior do Admin VTEX para encontrar páginas específicas no menu lateral.
 
 ### Central de Informações
 
diff --git a/docs/tutorials/pt/vtex-agreement.md b/docs/tutorials/pt/vtex-agreement.md
index 31a75008f..795b89304 100644
--- a/docs/tutorials/pt/vtex-agreement.md
+++ b/docs/tutorials/pt/vtex-agreement.md
@@ -29,7 +29,5 @@ O Master Agreement aplicável a você está disponível na seção **Política d
 
 Também é possível encontrar os Master Agreements mais atualizados, ou seja, aplicáveis aos novos clientes e parceiros, na página [Contrato da VTEX](https://vtex.com/br-pt/privacy-and-agreements/agreements/).
 
-<div class="alert alert-info">
-Caso os <b>MSA, MPA, Anexo 1</b> ou <b>Termos e condições específicos de parceria</b> firmados com a VTEX tragam alguma informação diferente daquela descrita nesta documentação, priorize o seu documento assinado com a VTEX.
-</div>
+>ℹ️ Caso os **MSA, MPA, Anexo 1** ou **Termos e condições específicos de parceria** firmados com a VTEX tragam alguma informação diferente daquela descrita nesta documentação, priorize o seu documento assinado com a VTEX.
 
diff --git a/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md b/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
index b60343c27..8fa8807bf 100644
--- a/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
+++ b/docs/tutorials/pt/vtex-dashboard-guide-for-black-week-faq.md
@@ -47,9 +47,9 @@ Para configurar a referência, siga os passos a seguir:
 4. Defina uma data.  
 5. Clique em **`Aplicar`**.  
 
-<div class="alert alert-warning">
-Uma comparação útil durante a Black Week é com a mesma data do ano anterior. No ajuste de referência, defina preferencialmente uma data entre 21/11/2022 e 27/11/2022, idealmente, os mesmos dias da semana. <br>Esta opção está disponível para clientes que utilizavam a plataforma VTEX nesse período no ano passado.</br>
-</div>
+>⚠️ Uma comparação útil durante a Black Week é com a mesma data do ano anterior. No ajuste de referência, defina preferencialmente uma data entre 21/11/2022 e 27/11/2022, idealmente, os mesmos dias da semana. 
+>
+> Esta opção está disponível para clientes que utilizavam a plataforma VTEX nesse período no ano passado.</br>
 
 ![referencia-pt](https://images.ctfassets.net/alneenqid6w5/1ba2BbD9ANCJfHj5o4jwQC/c92d901550424a6ce3e095a28fd1f8db/referencia-pt.png)
 
@@ -72,9 +72,7 @@ Para visualizar os produtos mais vendidos, no quadro de **Métricas,** clique no
 
 ![mais-vendidos-pt](https://images.ctfassets.net/alneenqid6w5/1sooXuFeV0NyhByWoLegHb/9c99acbbf617a57ef431bfec05873aa9/mais-vendidos-pt.png)
 
-<div class="alert alert-info">
-Para análises ou acompanhamentos de períodos maiores, recomendamos o uso do nosso dashboard de performance de vendas, que será detalhado na próxima pergunta.
-  </div>
+>ℹ️ Para análises ou acompanhamentos de períodos maiores, recomendamos o uso do nosso dashboard de performance de vendas, que será detalhado na próxima pergunta.
 
 ## Como acompanhar meus dados de ecommerce além do dia de hoje?
 
@@ -139,9 +137,9 @@ Há alguns motivos que podem levar a diferenças entre as métricas da Visão ge
 
 Para ver as métricas combinadas de todas as lojas,acesse o dashboard **Performance de vendas,** que apresenta dados agregados com uma taxa de atualização de aproximadamente 90 minutos. 
 
-<div class="alert alert-danger">
-  No <b>dashboard Visão geral em tempo real,</b> ecommercess que operam com mais de uma moeda têm seus pedidos somados somente na moeda mais utilizada em suas vendas.<br>Para comparar com a tela de <b>Pedidos,</b> você deve somar o total de pedidos de todas as suas moedas.</br>
-</div>  
+>❗ No **dashboard Visão geral em tempo real,** ecommercess que operam com mais de uma moeda têm seus pedidos somados somente na moeda mais utilizada em suas vendas.
+>
+> Para comparar com a tela de **Pedidos,** você deve somar o total de pedidos de todas as suas moedas.</br>  
 
 ![todos-os-pedidos-pt](https://images.ctfassets.net/alneenqid6w5/4tG8VMrSZU45ZRsDHifGPV/9891a93c18c0a1858c4d96340e17ac21/todos-os-pedidos-pt.png)
 
diff --git a/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md b/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
index 082705b33..741c60f7b 100644
--- a/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
+++ b/docs/tutorials/pt/vtex-intelligent-search-multilanguage-settings-beta.md
@@ -15,17 +15,13 @@ legacySlug: vtex-intelligent-search-configuracoes-multi-idioma-beta
 subcategory: 23WdCYqmn2V2Z7SDlc14DF
 ---
 
-<div class="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 O [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) é um aplicativo de busca inteligente para ecommerce que está disponível para lojas desenvolvidas usando o [VTEX IO](https://vtex.com/br-pt/store-framework/). Para instalar e configurar o VTEX Intelligent Search na sua loja, leia o nosso guia [Search](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search). A ferramenta exibe sugestões de busca e de produtos que possam interessar o usuário, além de corrigir erros ortográficos e entender palavras que não estão no cadastro do produto.
 
 O VTEX Intelligent Search Multi-idioma expande as funcionalidades do [Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) e oferece uma experiência de pesquisa multi-idioma, ideal para lojas que realizam operações em diversos países. Esse recurso facilita a adaptação da loja para vários idiomas e garante a busca em todos os idiomas cadastrados.
 
-<div class="alert alert-info">
-<p> Caso você deseje expandir o seu ecommerce para outro idioma, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a> para que o time da VTEX realize as configurações necessárias.</p>
-</div>
+>ℹ️ Caso você deseje expandir o seu ecommerce para outro idioma, entre em contato com o [nosso Suporte](https://support.vtex.com/hc/pt-br/requests) para que o time da VTEX realize as configurações necessárias.
 
 Com o VTEX Intelligent Search Multi-idioma instalado, as informações do Catálogo da loja são traduzidas pelo aplicativo [Messages](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization). Para isso, é importante cadastrar a tradução dos seguintes campos: __Nome__, __Marca__, __Descrição__, __Categorias__, __CategoryTrees__, __metadata__, __metadataKeyword__, __Especificações__, __SKU {name}__. Leia o guia para desenvolvedores [Tradução do conteúdo do catálogo](https://developers.vtex.com/vtex-developer-docs/docs/catalog-internationalization) para mais informações.
 
@@ -50,9 +46,7 @@ Para saber mais sobre os campos, leia nosso artigo sobre [como configurar Regras
 ### Sinônimos
 Existem duas formas de configurar Sinônimos em uma loja multi-idioma no Admin: preencher um formulário ou importar um arquivo `.csv`.
 
-<div class="alert alert-warning">
-  <p> Configurações criadas ou alteradas em <b>Sinônimos</b> podem levar até 2 horas para serem aplicadas na loja. </p>
-</div>
+>⚠️ Configurações criadas ou alteradas em **Sinônimos** podem levar até 2 horas para serem aplicadas na loja.
 
 #### Criar Sinônimos via formulário
 Com o VTEX Intelligent Search Multi-idioma instalado, a página de edição ou criação de Sinônimos — encontrada no Admin VTEX em __Storefront__ > __Intelligent Search__ > __Sinônimos__ — apresenta o campo adicional __Idiomas__, que possibilita escolher a quais idiomas os Sinônimos cadastrados serão aplicados, conforme a imagem abaixo. Clique nos idiomas desejados para selecioná-los.
@@ -71,9 +65,7 @@ Caso prefira fazer a importação de Sinônimos para idiomas específicos por ar
 - __Bidirecional__: `<Termos separados por vírgula>;<status>;<locales separados por vírgula>`
     - Exemplo: `tv,smart tv;true;en-GB`: ao pesquisar por qualquer um dos termos na loja no idioma inglês (`locale en-GB`), qualquer produto que contenha um desses termos irá aparecer nos resultados da busca.
 
-<div class="alert alert-warning">
-<p> Se o arquivo .csv importado não apresentar a coluna `locale`, o sinônimo será válido para todos os idiomas disponíveis na loja.</p>
-</div>
+>⚠️ Se o arquivo .csv importado não apresentar a coluna `locale`, o sinônimo será válido para todos os idiomas disponíveis na loja.
 
 Para saber mais sobre a importação de planilha de Sinônimos, leia nosso artigo sobre [como configurar Sinônimos no VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3ExbC3QKNF4zH7Gs8jD1cL).
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
index 9768586c8..5cd44b4a8 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
@@ -28,9 +28,7 @@ O módulo **VTEX Pick and Pack Fulfillment** está relacionado ao processo de ma
 * [Configurações](#configuracoes)
 * [Usuários](#usuarios)
 
-<div class="alert alert-danger">
-O <b>VTEX Pick and Pack</b> não é um sistema de faturação. Após a coleta e o empacotamento, o pedido deve ser faturado e atualizado como <code>Faturado</code> no OMS, de modo que o <b>VTEX Fulfillment</b> possa terminar o fluxo de coleta e empacotamento e seguir com o envio.
-</div>
+>❗ O **VTEX Pick and Pack** não é um sistema de faturação. Após a coleta e o empacotamento, o pedido deve ser faturado e atualizado como `Faturado` no OMS, de modo que o **VTEX Fulfillment** possa terminar o fluxo de coleta e empacotamento e seguir com o envio.
 
 ## Coleta e empacotamento
 
@@ -155,9 +153,7 @@ Na página de detalhes, você pode realizar as ações abaixo. As ações dispon
 * [Adicionar serviço de envio](#adicionar-servico-de-envio)
 * [Rastrear pedido](#rastrear-pedido)
 
-<div class="alert alert-danger">
-Embora as ações acima possam ser realizadas por <a href="https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios">usuários</a> com acesso ao Admin, geralmente as ações com um <b>*</b> (asterisco) devem ser executadas somente por entregadores em seus dispositivos móveis, sem qualquer acesso ao Admin da loja.
-</div>
+>❗ Embora as ações acima possam ser realizadas por [usuários](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios) com acesso ao Admin, geralmente as ações com um ***** (asterisco) devem ser executadas somente por entregadores em seus dispositivos móveis, sem qualquer acesso ao Admin da loja.
 
 #### Coletar
 
@@ -296,9 +292,8 @@ Para criar um novo pacote, siga os passos abaixo:
 
 Você pode adicionar um único produto a um pacote ou todos os produtos de uma vez. Depois que todos os produtos estiverem embalados, clique em `Fechar pacotes`. Uma vez fechados os pacotes, você não poderá mais adicionar itens ou fazer qualquer tipo de alteração.
 
-<div class="alert alert-danger">
-<p>O <b>VTEX Pick and Pack</b> não é um sistema de faturação. Assim que o pedido passar para o status de <code>Pronto para faturar</code>, ele deve ser faturado e atualizado como <code>faturado</code> no OMS. Somente depois disso o <b>VTEX Fulfillment</b> irá terminar o fluxo de coleta e empacotamento e proceder para o envio.</p><p>Se o pedido é faturado em um status diferente de /<code>Pronto para faturar</code>, o sistema irá considerar que é um caso de fulfillment externo e mudará o status do pedido para <code>Inativo</code>, desativando o <b>VTEX Pick and Pack</b> para processá-lo.</p>
-</div>
+>❗ O **VTEX Pick and Pack** não é um sistema de faturação. Assim que o pedido passar para o status de `Pronto para faturar`, ele deve ser faturado e atualizado como `faturado` no OMS. Somente depois disso o **VTEX Fulfillment** irá terminar o fluxo de coleta e empacotamento e proceder para o envio.
+> Se o pedido é faturado em um status diferente de /`Pronto para faturar`, o sistema irá considerar que é um caso de fulfillment externo e mudará o status do pedido para `Inativo`, desativando o **VTEX Pick and Pack** para processá-lo.
 
 #### Imprimir recibo e comprovante
 
@@ -338,9 +333,7 @@ No **VTEX Pick and Pack**, a página **Insights** apresenta dados e análises so
 * [Coleta e empacotamento](#insights-coleta-e-empacotamento)
 * [Operação](#insights-operacao)
 
-<div class="alert alert-warning">
-Para poder acessar a página de <b>Insights</b>, você precisa ter um perfil de usuário administrador no VTEX Fulfillment, que é diferente dos <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfis de acesso</a>. Para mais informações, consulte a seção <a href="https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios">Usuários</a>.
-</div>
+>⚠️ Para poder acessar a página de **Insights**, você precisa ter um perfil de usuário administrador no VTEX Fulfillment, que é diferente dos [perfis de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc). Para mais informações, consulte a seção [Usuários](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios).
 
 ### Insights: Coleta e empacotamento
 
@@ -410,9 +403,7 @@ Para configurar o **VTEX Pick and Pack** na sua loja, no Admin VTEX, acesse **Ap
 * [Impressão](#configuracoes-de-impressao)
 * [Webhooks](#configuracoes-de-weebhook)
 
-<div class="alert alert-warning">
-Para poder acessar as <b>Configurações</b>, você precisa ser um <a href="https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios-e-license-manager-no-vtex-fulfillment">usuário administrador do VTEX Fulfillment</a> ou um usuário de atendimento ao cliente.
-</div>
+>⚠️ Para poder acessar as **Configurações**, você precisa ser um [usuário administrador do VTEX Fulfillment](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#usuarios-e-license-manager-no-vtex-fulfillment) ou um usuário de atendimento ao cliente.
 
 ### Configurações gerais
 
@@ -626,9 +617,7 @@ Para gerar uma chave API, siga os passos abaixo:
 4. Clique em `Gerar`.
 5. Salve a chave API em um lugar seguro.
 
-  <div class="alert alert-danger">
-A chave API será exibida apenas uma vez. Você não poderá acessar essa informação novamente, então salve-a em um local seguro.
-</div>
+  >❗ A chave API será exibida apenas uma vez. Você não poderá acessar essa informação novamente, então salve-a em um local seguro.
 
 6. Insira a senha.
 7. Clique em `Salvar`.
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
index cecb0c325..4c488b832 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
@@ -48,9 +48,7 @@ Ao selecionar esta ordem de serviço para manuseio, o aplicativo indicará a sep
 
 Em seguida, o aplicativo te auxiliará no empacotamento de cada pedido com seus respectivos itens.
 
-<div class="alert alert-warning">
-Ordens de serviço se aplicam apenas às fases de separação e empacotamento de pedidos. Você deve fazer o envio de cada pedido separadamente.
-</div>
+>⚠️ Ordens de serviço se aplicam apenas às fases de separação e empacotamento de pedidos. Você deve fazer o envio de cada pedido separadamente.
 
 ### Criar ordem de serviço
 
@@ -117,9 +115,7 @@ Uma vez separados, os produtos são listados na aba __Resumo__.
 
 Há cenários em que pode ser necessário recusar produtos por conta das configurações da loja e disponibilidade dos itens no inventário. 
 
-<div class="alert alert-warning">
-A opção de recusar itens pode não estar disponível. Em caso de dúvida, consulte a administração da loja.
-</div>
+>⚠️ A opção de recusar itens pode não estar disponível. Em caso de dúvida, consulte a administração da loja.
 
 Para recusar um produto da ordem de serviço, siga os passos abaixo:
 
@@ -136,17 +132,13 @@ Para recusar todos os produtos da ordem de serviço de uma única vez, siga este
 2. Clique na opção **Marcar como pronto para empacotar.** 
 3. Toque em **Recusar todos os itens disponíveis.**
 
-<div class="alert alert-danger">
-Se todos os itens de um pedido forem recusados, o pedido será concluído automaticamente.
-</div>
+>❗ Se todos os itens de um pedido forem recusados, o pedido será concluído automaticamente.
 
 ## Substituir itens
 
 Outra opção para casos de itens indisponíveis é substituir o item por um outro, a depender das configurações da loja e disponibilidade dos itens no inventário.
 
-<div class="alert alert-warning">
-A opção de substituir itens pode não estar disponível. Em caso de dúvida, consulte a administração da loja.
-</div>
+>⚠️ A opção de substituir itens pode não estar disponível. Em caso de dúvida, consulte a administração da loja.
 
 Para substituir itens da ordem de serviço, siga os passos abaixo:
 
@@ -181,9 +173,7 @@ Siga os passos abaixo para empacotar itens:
 
 1. Em Empacotamento, clique no pedido que deseja empacotar. 
 2. Clique no botão <i class="fas fa-plus"></i> do produto que deseja adicionar no pacote ou clique em <i class="fas fa-box"></i> para empacotar todos os produtos ao mesmo tempo.
-<div class="alert alert-warning">
-Caso opte por empacotar todos os itens do pedido, os produtos que ainda não foram empacotados serão registrados em um único novo pacote.
-</div>
+>⚠️ Caso opte por empacotar todos os itens do pedido, os produtos que ainda não foram empacotados serão registrados em um único novo pacote.
 4. Selecione um pacote já registrado ou adicione um novo pacote clicando em `+ Criar pacote`. 
 5. Selecione o tipo do pacote que deseja adicionar.
 6. Selecione o número de unidades deste produto que deseja adicionar àquele pacote.
@@ -203,9 +193,7 @@ __Pedidos e pacotes__
 
 A fase de envio permite criar serviços de envio referentes a pedidos que foram separados e empacotados.
 
-<div class="alert alert-warning">
-O envio é uma etapa opcional do aplicativo, a depender da sua operação e configurações feitas pelo administrador de loja.
-</div>
+>⚠️ O envio é uma etapa opcional do aplicativo, a depender da sua operação e configurações feitas pelo administrador de loja.
 
 Para enviar pacotes no aplicativo Pick and Pack, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/vtex-shield.md b/docs/tutorials/pt/vtex-shield.md
index c2407e1a0..f545db589 100644
--- a/docs/tutorials/pt/vtex-shield.md
+++ b/docs/tutorials/pt/vtex-shield.md
@@ -15,9 +15,7 @@ legacySlug: vtex-shield
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 O VTEX Shield oferece camadas adicionais e personalizáveis de proteção para lojas que priorizam a resiliência da plataforma, além dos padrões de segurança garantidos pelas [certificações e práticas de segurança](https://vtex.com/br-pt/security/security-practices/) existentes na VTEX.
 
@@ -52,9 +50,7 @@ Somente lojas com VTEX Shield que optarem por esse recurso podem solicitar a ati
 
 ## Data Protection Plus
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade está em fase beta fechada, disponível apenas para algumas regiões. Em caso de dúvidas, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>.</p>
-</div>
+>ℹ️ Esta funcionalidade está em fase beta fechada, disponível apenas para algumas regiões. Em caso de dúvidas, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ).
 
 O [Data Protection Plus](https://developers.vtex.com/docs/guides/data-protection-plus) é uma arquitetura de dados que oferece uma camada adicional de proteção para dados pessoais. Nessa arquitetura, todos os dados PII (Personally Identifiable Information) são armazenados no [Profile System](https://developers.vtex.com/docs/guides/profile-system), um serviço desenvolvido especificamente para processar PII seguindo um [conjunto de regras e processos](https://developers.vtex.com/docs/guides/pii-data-architecture-specifications) apropriados para esse objetivo.
 
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
index 04c9f8643..4b0e05a35 100644
--- a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
@@ -15,9 +15,7 @@ legacySlug: vtex-shipping-network-correios-ativacao
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network-correios/">VTEX Shipping Network Correios</a>. Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/). Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
 
 [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/) é a solução para você integrar sua operação com os serviços PAC e SEDEX dos Correios pelo Admin VTEX e obter de recursos exclusivos. Para lojas VTEX, as tabelas dos Correios ofertadas têm preços especiais, de forma a reduzir os custos logísticos do seu negócio. 
 
@@ -44,9 +42,7 @@ Para realizar a ativação, siga o passo a passo abaixo:
 
   b. Em **Sua tabela dos Correios**, selecione uma das seguintes opções: <p><ul><li>Não possuo contrato com os Correios</li><li>Bronze</li><li>Prata</li><li>Ouro</li><li>Platinum</li></ul></p>
 
-  <div class="alert alert-warning">
-Caso você já possua um contrato com os Correios, antes de ativar o <b>VTEX Shipping Network Correios</b> você deve desativá-lo nas suas <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">políticas de envio</a> ou removê-lo das <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">docas</a>. Se isso não for feito, a plataforma VTEX pode gerar erros de duplicidade e outros problemas, inclusive erros na emissão de etiquetas no <a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a>.
-</div>
+  >⚠️ Caso você já possua um contrato com os Correios, antes de ativar o **VTEX Shipping Network Correios** você deve desativá-lo nas suas [políticas de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140) ou removê-lo das [docas](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj). Se isso não for feito, a plataforma VTEX pode gerar erros de duplicidade e outros problemas, inclusive erros na emissão de etiquetas no [Pronto para envio](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs).
 
   c. Clique em **Conhecer Oferta**.
 
@@ -73,6 +69,4 @@ Caso você já possua um contrato com os Correios, antes de ativar o <b>VTEX Shi
 
 Feito isso, a ativação do **VTEX Shipping Network Correios** terá sido concluída.
 
-<div class="alert alert-danger">
-Para as novas políticas de envio serem válidas, além de estarem ativadas, é necessário que todas as <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">docas</a> da sua operação tenham o endereço cadastrado. Caso contrário, a plataforma vai apresentar erros. Portanto, certifique-se de configurar o endereço de todas as docas, mesmo aquelas não associadas aos Correios.
-</div>
+>❗ Para as novas políticas de envio serem válidas, além de estarem ativadas, é necessário que todas as [docas](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) da sua operação tenham o endereço cadastrado. Caso contrário, a plataforma vai apresentar erros. Portanto, certifique-se de configurar o endereço de todas as docas, mesmo aquelas não associadas aos Correios.
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-faq.md b/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
index 79d7908e1..8552ce555 100644
--- a/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
@@ -15,9 +15,7 @@ legacySlug: vtex-shipping-network-correios-faq
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network-correios/">VTEX Shipping Network Correios</a>. Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/). Em caso de dúvidas, entre em contato pelo email <i>vtexlog@vtex.com.br</i>.
 
 Este artigo reúne as dúvidas mais comuns sobre o [VTEX Shipping Network Correios](https://vtex.com/br-pt/shipping-network-correios/), a solução da VTEX para você integrar sua operação com os serviços PAC e SEDEX dos Correios pelo Admin VTEX, dispor de recursos exclusivos e aproveitar nossas tarifas competitivas.
 
@@ -110,9 +108,7 @@ A fatura do **VTEX Shipping Network Correios** é feita com emissão de nota fis
 
 Todo mês é gerado um relatório com informações das entregas dos Correios e respectivos custos, e esse documento é enviado para o email do responsável, um contato definido no momento da implantação. Para alterá-lo, entre em contato com o nosso suporte pelo email _vtexlog@vtex.com.br_.
 
-<div class="alert alert-warning">
-A nota fiscal apresenta o valor total de custos com os Correios, no entanto, é possível checar o preço de cada envio no relatório mensal que o responsável recebe por email.
-</div>
+>⚠️ A nota fiscal apresenta o valor total de custos com os Correios, no entanto, é possível checar o preço de cada envio no relatório mensal que o responsável recebe por email.
 
 ## 7. Como contratar o VTEX Shipping Network Correios?
 
diff --git a/docs/tutorials/pt/vtex-shipping-network-dashboard.md b/docs/tutorials/pt/vtex-shipping-network-dashboard.md
index 439a0fe9d..3d47e16a5 100644
--- a/docs/tutorials/pt/vtex-shipping-network-dashboard.md
+++ b/docs/tutorials/pt/vtex-shipping-network-dashboard.md
@@ -15,13 +15,13 @@ legacySlug: painel-vtex-log
 subcategory: 5n5MnINzWTQUX1I2EZl4Ib
 ---
 
-<div class="alert alert-info">
-Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>.
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Caso tenha interesse em adotar essa funcionalidade no seu negócio, acesse o site [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/).
 
-<div class="alert alert-warning">
-<p>O <a href="https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC">VTEX Shipping Network Correios</a> integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a> integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:</p><p><ul><li><a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para envio</a></li><li><a href="https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq">Entregas Correios</a></li><li>Painel VTEX Shipping Network</li></ul></p>
-</div>
+>⚠️ O [VTEX Shipping Network Correios](https://help.vtex.com/pt/tutorial/vtex-shipping-network-correios-faq--2Wavf7Wie5GEUAEHKtn5oC) integra sua operação com os serviços PAC e SEDEX do contrato VTEX junto aos Correios, e o [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) integra a sua operação com os Correios e outras transportadoras. Com ambas as soluções você pode usar as funcionalidades:
+> 
+> *[Pronto para envio](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs)
+> * [Entregas Correios](https://help.vtex.com/pt/tutorial/entregas-correios-vtex-shipping-network--5CZRA0lq60EecmwZpsjvfq)
+> * Painel VTEX Shipping Network
 
 O [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) utiliza os dados de rastreio dos pedidos diretamente das transportadoras, mantendo você e seu cliente atualizados sobre o status de cada entrega.
 
@@ -92,9 +92,7 @@ Também é possível visualizar os pedidos nas seguintes situações:
 
 Todas as transportadoras **VTEX Shipping Network** possuem selo de verificação o qual é visível na tabela de desempenho. O selo está na tabela de desempenho  sinalizando com uma marcação de cor rosa quais as transportadoras são **VTEX Shipping Network**.
 
-<div class="alert alert-warning">
-É importante saber que, no caso em que a transportadora não teve a performance calculada na plataforma, os dados de rastreamento não foram integrados ao <b>VTEX Shipping Network</b>.
-</div>
+>⚠️ É importante saber que, no caso em que a transportadora não teve a performance calculada na plataforma, os dados de rastreamento não foram integrados ao **VTEX Shipping Network**.
 
 Para que o cálculo da performance seja feito em transportadoras que não são **VTEX Shipping Network**, os dados devem ser enviados pelo seller por uma API de tracking disponibilizada pela solução **VTEX Shipping Network**. Nestes casos, vale ressaltar que os dados do painel podem ser imprecisos, pois não há validação da entrega ser realizada no prazo indicado. 
 
diff --git a/docs/tutorials/pt/vtex-status-page.md b/docs/tutorials/pt/vtex-status-page.md
index 95ccd89be..a29040f11 100644
--- a/docs/tutorials/pt/vtex-status-page.md
+++ b/docs/tutorials/pt/vtex-status-page.md
@@ -125,9 +125,7 @@ Para visualizar as ocorrências de um dia específico, passe o mouse sobre a dat
 
 ![statuspage-8](https://images.ctfassets.net/alneenqid6w5/2aRBMeTVELfszcFQFpXyUJ/36a4d394c1fb447958eec18ceaa849d3/statuspage-8.png)
 
-<div class="alert alert-warning">
-  <p>Se a manutenção agendada durar um período maior que um dia, somente a data de início estará marcada no calendário. É necessário abrir o <a href="#registro-de-manutencao-agendada">registro da manutenção</a> para ver a data de início e a data de fim.</p>
-</div>
+>⚠️ Se a manutenção agendada durar um período maior que um dia, somente a data de início estará marcada no calendário. É necessário abrir o [registro da manutenção](#registro-de-manutencao-agendada) para ver a data de início e a data de fim.
 
 A seguir, detalhamos as informações disponíveis no [registro de incidente](#registro-de-incidente) e no [registro de manutenção agendada](#registro-de-manutencao-agendada).
 
diff --git a/docs/tutorials/pt/vtex-tracking-holidays.md b/docs/tutorials/pt/vtex-tracking-holidays.md
index 2c82c766e..1e00dc8c7 100644
--- a/docs/tutorials/pt/vtex-tracking-holidays.md
+++ b/docs/tutorials/pt/vtex-tracking-holidays.md
@@ -15,9 +15,7 @@ legacySlug: feriados-vtex-tracking
 subcategory: 7yiFRk9TGfMNeyhT83UljP
 ---
 
-<div class="alert alert-info">
-O cadastro de Feriados é vinculado apenas à funcionalidade de agendamento de entrega, que está disponível somente para usuários VTEX Tracking com integração de sistemas. 
-</div>
+>ℹ️ O cadastro de Feriados é vinculado apenas à funcionalidade de agendamento de entrega, que está disponível somente para usuários VTEX Tracking com integração de sistemas.
 
 Os clientes recebem uma comunicação via  e-mail ou SMS com a previsão da entrega do seu pedido. Se o cliente já souber que não estará disponível para receber seu pacote no período informado, pode reagendar a entrega para outra data e período.  
 
diff --git a/docs/tutorials/pt/warehouse.md b/docs/tutorials/pt/warehouse.md
index 9c687982a..751bad12c 100644
--- a/docs/tutorials/pt/warehouse.md
+++ b/docs/tutorials/pt/warehouse.md
@@ -21,17 +21,13 @@ Para a plataforma VTEX o estoque é a identificação do espaço físico de arma
 
 ![EstrategiaEnvio](https://images.ctfassets.net/alneenqid6w5/91iqVknOpCjUKO1XQaYvq/02cad4cbd4829e774e2b51474e4675cf/Frame_2__1_.svg)
 
-<div class="alert alert-info">
-A transportadora que realizará a entrega de um certo pedido é definida pela <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">política de envio</a>. Para que uma transportadora seja escolhida para a realização da entrega do pedido, é preciso que a política de envio dessa transportadora satisfaça as condições necessárias para a entrega do pedido. A política de envio é vinculada ao estoque pela Doca.
-</div>
+>ℹ️ A transportadora que realizará a entrega de um certo pedido é definida pela [política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140). Para que uma transportadora seja escolhida para a realização da entrega do pedido, é preciso que a política de envio dessa transportadora satisfaça as condições necessárias para a entrega do pedido. A política de envio é vinculada ao estoque pela Doca.
 
 Na plataforma VTEX, é possível cadastrar o nome do estoque, adicionar itens ao estoque, [configurar as docas](https://help.vtex.com/pt/tutorial/como-cadastrar-doca--7K3FultD8I2cuuA6iyGEiW) que fazem o recebimento do estoque, configurar o tempo que o pedido leva para ser preparado para ser enviado à doca e o valor cobrado por esse manuseio. 
 
 Com um estoque cadastrado os produtos que estão disponíveis naquele estoque podem ser inseridos. É possível ter vários estoques, e para cada um adicionar os seus itens específicos, para refletir na sua configuração logística. 
 
-<div class="alert alert-info">
-Para adicionar itens ao seu estoque, os produtos precisam ser previamente cadastrados no <a href="https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR">catálogo</a>. Com isso, é possível associá-los ao estoque pelo <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">gerenciamento de inventário</a>. 
-</div>
+>ℹ️ Para adicionar itens ao seu estoque, os produtos precisam ser previamente cadastrados no [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/7kz4uWVq6NoaOdUpiJv4PR). Com isso, é possível associá-los ao estoque pelo [gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
 A disponibilidade dos produtos da sua loja é dada por produtos cadastrados em diferentes estoques. O que significa que para o cliente final os itens que ficam disponíveis durante a navegação na loja são itens referentes a todos os estoques. Assim, existe a possibilidade de em uma única compra ter produtos de diferentes estoques da sua loja. Para o controle de movimentações dos estoques e  disponibilidade de itens da sua loja acesse o [Gerenciamento de Inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
@@ -41,14 +37,15 @@ Saiba mais sobre como gerenciar componentes logísticos na plataforma VTEX:
 * Para acompanhar e gerenciar os itens do estoque consulte o [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 * Para configurar e gerenciar a relação entre os estoques e as retiradas dos pedidos consulte [Gerenciamento de docas.](https://help.vtex.com/pt/tutorial/como-cadastrar-doca--7K3FultD8I2cuuA6iyGEiW)
 
-<div class="alert alert-warning">
-A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política Comercial;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de Envio;</a></li>
-  <li><a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">Doca;</a></li>
-<li>Estoque.</li>
-</ol>
-</body>
-</div>
+>⚠️ A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
+> <body>
+>
+> [Política Comercial;](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV)
+>
+> 2. [Política de Envio;](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140)
+>
+> 3. [Doca;](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj)
+>
+> Estoque.
+>
+> </body>
diff --git a/docs/tutorials/pt/web-application-firewall-waf.md b/docs/tutorials/pt/web-application-firewall-waf.md
index 3aac9e02c..c27ef923e 100644
--- a/docs/tutorials/pt/web-application-firewall-waf.md
+++ b/docs/tutorials/pt/web-application-firewall-waf.md
@@ -15,9 +15,7 @@ legacySlug: web-application-firewall-waf
 subcategory: jrgbOxKaOW0kdZs7rdgvS
 ---
 
-<div class="alert alert-info">
-  <p>Esta funcionalidade faz parte do produto <a href="https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh">VTEX Shield</a>. Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ Esta funcionalidade faz parte do produto [VTEX Shield](https://help.vtex.com/pt/tutorial/vtex-shield--2CVk6H9eY2CBtHjtDI7BFh). Se já é cliente da VTEX e deseja adotar o VTEX Shield no seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 O Web Application Firewall (WAF) é uma camada de segurança projetada para proteger aplicações web por meio do monitoramento e da filtragem do tráfego da Internet.
 
diff --git a/docs/tutorials/pt/what-are-layouts.md b/docs/tutorials/pt/what-are-layouts.md
index e8eb2a2cd..29ca6395c 100644
--- a/docs/tutorials/pt/what-are-layouts.md
+++ b/docs/tutorials/pt/what-are-layouts.md
@@ -19,10 +19,10 @@ Os __layouts__ são os responsáveis por determinar quais [placeholders](/pt/tut
 
 Isso é feito primeiro a partir da configuração do placeholder, que vai dizer qual o tipo utilizado e o arquivo que vai preenchê-lo. Depois, para que o layout se torne funcional, ele precisa estar vinculado a um [template](/pt/tutorial/o-que-sao-templates). Assim, o código da página em que o placeholder vai ser exibido vai saber exatamente de onde vem a informação.
 
-<div class="alert alert-warning">
-<strong>Importante</strong><br>
-Para funcionar, cada layout precisa estar vinculado a um único template.
-</div>
+>⚠️ **Importante**
+>
+> 
+> Para funcionar, cada layout precisa estar vinculado a um único template.
 
 
 ### Artigos relacionados
diff --git a/docs/tutorials/pt/what-are-utm-source-utm-campaign-and-utm-medium.md b/docs/tutorials/pt/what-are-utm-source-utm-campaign-and-utm-medium.md
index 92b872cab..a46c2d352 100644
--- a/docs/tutorials/pt/what-are-utm-source-utm-campaign-and-utm-medium.md
+++ b/docs/tutorials/pt/what-are-utm-source-utm-campaign-and-utm-medium.md
@@ -23,9 +23,7 @@ Ou então você pode definir que, para essa mesma UTM, determinada promoção se
 
 Com isso, a plataforma permite que você tome determinadas ações de acordo com a origem do tráfego da loja.
 
-<div class="alert alert-info">
-Na tela de <strong>Gerenciamento de Pedidos</strong>, apenas o utm_source está <a href="https://help.vtex.com/pt/tutorial/como-filtrar-pedidos">disponível para filtro</a>.
-</div>
+>ℹ️ Na tela de **Gerenciamento de Pedidos**, apenas o utm_source está [disponível para filtro](https://help.vtex.com/pt/tutorial/como-filtrar-pedidos).
 
 ### Tipos de UTM
 
@@ -38,9 +36,7 @@ Mas você pode usar essas UTMs da maneira que melhor atender suas regras de neg
 
 Portanto, na prática, o que importa é definir a ação correta para os valores desses parâmetros.
 
-<div class="alert alert-danger">
-Atenção: caracteres <strong>especiais não</strong> devem ser utilizados em UTMs. Essas variáveis  só funcionam corretamente caso sejam utilizados caracteres <strong> alfanuméricos, hífens e underscore </strong>.
-</div>
+>❗ Atenção: caracteres **especiais não** devem ser utilizados em UTMs. Essas variáveis  só funcionam corretamente caso sejam utilizados caracteres ** alfanuméricos, hífens e underscore **.
 
 Para maiores informações sobre problemas de adicionar UTMs no carrinho, acesse [Why are the UTMs not being applied to the cart?](https://developers.vtex.com/vtex-rest-api/docs/check-marketing-utms-used-at-checkout#why-are-the-utms-not-being-applied-to-the-cart).
 
diff --git a/docs/tutorials/pt/what-is-a-dispute.md b/docs/tutorials/pt/what-is-a-dispute.md
index 744315fd5..68d7d5ae2 100644
--- a/docs/tutorials/pt/what-is-a-dispute.md
+++ b/docs/tutorials/pt/what-is-a-dispute.md
@@ -32,6 +32,4 @@ Existem duas possibilidades para o resultado de uma disputa:
 - Se o lojista ganhar a defesa da disputa, o dinheiro da compra é retornado para sua conta.
 - Caso ele perca a defesa, o valor correspondente continua com o cliente.
 
-<div class="alert alert-info">
-<strong>Atenção:</strong> o <i>chargeback</i> é um tipo de estorno típico do cenário de ecommerce. Aqui, compras feitas por meio de cartão de crédito são canceladas ou estornadas quando o titular do cartão ganha a disputa.
-</div>
+>ℹ️ **Atenção:** o <i>chargeback</i> é um tipo de estorno típico do cenário de ecommerce. Aqui, compras feitas por meio de cartão de crédito são canceladas ou estornadas quando o titular do cartão ganha a disputa.
diff --git a/docs/tutorials/pt/what-is-a-franchise-account.md b/docs/tutorials/pt/what-is-a-franchise-account.md
index 72dbd3e1a..6f99a75d1 100644
--- a/docs/tutorials/pt/what-is-a-franchise-account.md
+++ b/docs/tutorials/pt/what-is-a-franchise-account.md
@@ -46,14 +46,13 @@ Toda conta franquia atua automaticamente como um Seller White Label da conta pri
 
 Os clientes finais não escolhem e não têm visibilidade da existência dos Sellers White Label em nenhum momento do processo. Nessa lógica, a relação dos consumidores é com a marca (conta principal) e não com cada loja física (conta franquia).
 
-<div class="alert alert-info">
-<p>Apesar de toda conta franquia atuar como Seller White Label da conta principal, esses conceitos não significam a mesma coisa. A conta franquia é um tipo de conta, enquanto ser White Label é uma propriedade de um seller.
-<ul>
-<li><strong>Conta</strong>: pode ser do tipo franquia ou pode ser uma conta normal.</li>
-<li><strong>Seller</strong>: pode ser do tipo White Label ou pode ser do tipo não White Label.</li>
-</ul>
-Como esses conceitos são independentes, <strong>eventualmente</strong> é possível que uma conta franquia atue como seller não White Label de um outro marketplace, diferente da conta principal.</p>
-</div>
+>ℹ️ Apesar de toda conta franquia atuar como Seller White Label da conta principal, esses conceitos não significam a mesma coisa. A conta franquia é um tipo de conta, enquanto ser White Label é uma propriedade de um seller.
+>
+> ***Conta**: pode ser do tipo franquia ou pode ser uma conta normal.
+>
+> ***Seller**: pode ser do tipo White Label ou pode ser do tipo não White Label.
+>
+> Como esses conceitos são independentes, **eventualmente** é possível que uma conta franquia atue como seller não White Label de um outro marketplace, diferente da conta principal.
 
 ## Configurações da conta franquia
 
@@ -96,9 +95,7 @@ Uma vez que você tenha [alterado essa configuração](#configurar-meios-de-paga
 
 A VTEX oferece soluções de split de pagamentos que podem tornar automática a distribuição de recebíveis para sellers. Recomendamos a leitura do artigo [Split de pagamento](https://help.vtex.com/pt/tutorial/split-de-pagamento--6k5JidhYRUxileNolY2VLx) para mais informações.
 
-<div class="alert alert-warning">
-<p>Caso você deseje implementar o VTEX Sales App,é necessario que as lojas físicas utilizem os meios de pagamento da conta principal.</p>
-</div>
+>⚠️ Caso você deseje implementar o VTEX Sales App,é necessario que as lojas físicas utilizem os meios de pagamento da conta principal.
 
 ## Solicitar criação de conta franquia
 
diff --git a/docs/tutorials/pt/what-is-a-marketplace.md b/docs/tutorials/pt/what-is-a-marketplace.md
index 3bfc8cea1..3c9f39400 100644
--- a/docs/tutorials/pt/what-is-a-marketplace.md
+++ b/docs/tutorials/pt/what-is-a-marketplace.md
@@ -21,9 +21,7 @@ Numa experiência de compra, um usuário navega por um website selecionando prod
 
 Um marketplace também pode ser entendido como uma *loja vitrine*, que exibe os próprios produtos e também produtos de outras lojas (sellers). Geralmente, um marketplace é uma loja com um bom tráfego de usuários. Isso incentiva outras lojas a exibirem seus produtos no marketplace, visando uma maior conversão. Neste cenário, o __marketplace__ é a loja responsável pelo fechamento da compra e o __seller__ é a loja responsável por realizar a entrega do pedido.
 
-<div class="alert alert-info">
-Seguindo esta lógica, podemos concluir que uma loja VTEX que venda seus próprios produtos em sua própria loja atua como marketplace e seller de forma simultânea. Neste contexto, o pagamento é feito dentro do ambiente da loja (marketplace) e a entrega do pedido é de responsabilidade dessa mesma loja (seller). Veja mais detalhes sobre este assunto em <a href="https://help.vtex.com/tutorial/o-que-sao-pedidos-com-origem-marketplace-e-origem-fulfillment--6eVYrmUAwMOeKICU2KuG06">nosso artigo</a> sobre a origem dos pedidos. 
-</div>
+>ℹ️ Seguindo esta lógica, podemos concluir que uma loja VTEX que venda seus próprios produtos em sua própria loja atua como marketplace e seller de forma simultânea. Neste contexto, o pagamento é feito dentro do ambiente da loja (marketplace) e a entrega do pedido é de responsabilidade dessa mesma loja (seller). Veja mais detalhes sobre este assunto em [nosso artigo](https://help.vtex.com/tutorial/o-que-sao-pedidos-com-origem-marketplace-e-origem-fulfillment--6eVYrmUAwMOeKICU2KuG06) sobre a origem dos pedidos.
 
 ## Artigos relacionados
 
diff --git a/docs/tutorials/pt/what-is-a-service.md b/docs/tutorials/pt/what-is-a-service.md
index 80257493c..fa16567cc 100644
--- a/docs/tutorials/pt/what-is-a-service.md
+++ b/docs/tutorials/pt/what-is-a-service.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Um serviço é um item, opcional e com custo, que pode vir acompanhando um produto. Ele é utilizado para atribuir um valor, muitas vezes emocional, mas também de um adicional de serviço, propriamente dito, a um SKU. Por exemplo, uma embalagem de presente, uma fita diferenciada, um cartão de presente ou uma instalação de produto.
 
-<div class="alert alert-warning">
-É importante lembrar que um serviço sempre é cobrado. No entanto, a VTEX não controla o estoque de um serviço. Sendo essa a função do marketplace ou do seller.
-</div>
+>⚠️ É importante lembrar que um serviço sempre é cobrado. No entanto, a VTEX não controla o estoque de um serviço. Sendo essa a função do marketplace ou do seller.
 
 Se o seu produto comprado for uma Camisa da Seleção Brasileira, o nome do seu Serviço pode ser __Embalagem de Presente__, e ser exibido durante o fluxo de pedido na tela que você escolher: produto, carrinho ou serviço.
 
diff --git a/docs/tutorials/pt/what-is-an-affiliate.md b/docs/tutorials/pt/what-is-an-affiliate.md
index 3ea0202a2..dc01ad506 100644
--- a/docs/tutorials/pt/what-is-an-affiliate.md
+++ b/docs/tutorials/pt/what-is-an-affiliate.md
@@ -15,9 +15,7 @@ legacySlug: o-que-e-afiliado
 subcategory: 1qvm3kIrt6KA6IeGc4EQ6k
 ---
 
-<div class="alert alert-info"> 
-O conceito de afiliado da VTEX é diferente da <a href="https://pt.wikipedia.org/wiki/Programa_de_afiliados">definição usual</a>. Leia abaixo para saber mais. 
-</div>
+>ℹ️ O conceito de afiliado da VTEX é diferente da [definição usual](https://pt.wikipedia.org/wiki/Programa_de_afiliados). Leia abaixo para saber mais.
 
 [Configurar afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado) será necessário apenas quando a loja atuar como seller de um marketplace.
 
diff --git a/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md b/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
index a54ee4ea9..302efbc77 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-acquirer-brand-gateway-and-sub-acquirer-in-brazil.md
@@ -73,7 +73,5 @@ Ele coleta dados sobre o comportamento dos usuários e os comparam com padrões
 
 Na VTEX, primeiro a operadora do pagamento aprova a compra e, em seguida, o antifraude avalia o pedido. Com tudo em ordem, ele segue seu fluxo normal. São exemplos de antifraude a ClearSale e a Konduto. 
 
-<div class="alert alert-info">
-É importante ressaltar que cada negócio depende de fatores específicos que influenciam na decisão sobre qual modalidade usar. São diversas as variáveis que podem determinar a escolha do meio de pagamento e qual será o seu fluxo financeiro. É fundamental, portanto, ter em mente as reais necessidades e propósitos do lojista e do projeto desejado.
-</div>
+>ℹ️ É importante ressaltar que cada negócio depende de fatores específicos que influenciam na decisão sobre qual modalidade usar. São diversas as variáveis que podem determinar a escolha do meio de pagamento e qual será o seu fluxo financeiro. É fundamental, portanto, ter em mente as reais necessidades e propósitos do lojista e do projeto desejado.
 
diff --git a/docs/tutorials/pt/what-is-the-difference-between-sales-policy-affiliate-and-seller.md b/docs/tutorials/pt/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
index 6b04eb42b..e9900109b 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
@@ -45,9 +45,7 @@ Cada marketplace deverá ter um __identificador único de afiliação__.
 
 Após criar um [afiliado](/pt/tutorial/como-configurar-afiliado/), você deve associar uma política comercial a ele. A política comercial contém as informações dos sortimentos de produto, logística e preço que serão enviadas para o afiliado em questão.
 
-<div class="alert alert-info">
-Caso a configuração de marketplace seja feita pelo módulo <a href="http://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/">Bridge</a>, o afiliado será criado automaticamente no módulo OMS.
-</div>
+>ℹ️ Caso a configuração de marketplace seja feita pelo módulo [Bridge](http://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/), o afiliado será criado automaticamente no módulo OMS.
 
 #### **SAIBA MAIS**
 
diff --git a/docs/tutorials/pt/what-is-the-period-considered-for-calculating-my-billing.md b/docs/tutorials/pt/what-is-the-period-considered-for-calculating-my-billing.md
index 6e07cc43a..a96f5b864 100644
--- a/docs/tutorials/pt/what-is-the-period-considered-for-calculating-my-billing.md
+++ b/docs/tutorials/pt/what-is-the-period-considered-for-calculating-my-billing.md
@@ -22,6 +22,4 @@ Portanto, o período que deve ser considerado é sempre do primeiro ao último d
 ## Exemplo 
 No dia 01/03 é emitida uma fatura com a referência "Fevereiro". Todos os pedidos que passaram pelo status __aprovado__, do dia 01/02 até 28/02, serão considerados nessa fatura.
 
-<div class="alert alert-warning">
-Caso receba uma cobrança sem que sua loja esteja no ar, saiba que ela é referente ao <strong>fee mensal</strong> da taxa de manutenção do seu ambiente. Esse valor é cobrado pois mesmo que a loja não esteja em produção já está consumindo a estrutura VTEX.
-</div>
+>⚠️ Caso receba uma cobrança sem que sua loja esteja no ar, saiba que ela é referente ao **fee mensal** da taxa de manutenção do seu ambiente. Esse valor é cobrado pois mesmo que a loja não esteja em produção já está consumindo a estrutura VTEX.
diff --git a/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md b/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
index d71663818..8abf796b9 100644
--- a/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
+++ b/docs/tutorials/pt/what-is-the-purpose-of-the-customized-control.md
@@ -37,9 +37,7 @@ Para criar uma tag personalizada de controle customizado, basta clicar em __Add_
 
 ![cms-custom-elements PT](https://images.ctfassets.net/alneenqid6w5/oYjlNFuR8WKUkCag2yiQM/8da98e4f84d6e31639552d8d28931089/custom_elements_pt.png)
 
-<div class="alert alert-warning">
-  <p><b>Atenção:</b> não crie um controle do tipo HTML com um elemento <code>title</code>. Isso pode interferir no funcionamento correto da sua loja.</p>
-</div>
+>⚠️ **Atenção:** não crie um controle do tipo HTML com um elemento `title`. Isso pode interferir no funcionamento correto da sua loja.
 
 ## Aplicando um controle customizado a um template de página
 
diff --git a/docs/tutorials/pt/what-is-the-shared-cart.md b/docs/tutorials/pt/what-is-the-shared-cart.md
index 8eeaee38a..b1650c376 100644
--- a/docs/tutorials/pt/what-is-the-shared-cart.md
+++ b/docs/tutorials/pt/what-is-the-shared-cart.md
@@ -33,15 +33,11 @@ Exemplo:
 
 - **URL do carrinho compartilhado**: `https://www.{nomedaloja}.com/checkout/?orderFormId=31155bb8fd6944c99829c171aa8ed5c4#/cart`
 
-<div class="alert alert-warning">
-Ao montar a URL do carrinho compartilhado, garanta que a querystring <b>?orderFormId=...</b> seja posicionada entre <b>/checkout/</b> e <b>#/cart</b>.
-</div>
+>⚠️ Ao montar a URL do carrinho compartilhado, garanta que a querystring **?orderFormId=...** seja posicionada entre **/checkout/** e **#/cart**.
 
 Para obter acesso a informações de identificação de carrinhos, confira a [Checkout API](https://developers.vtex.com/vtex-rest-api/reference/checkout-api-overview).
 
-<div class="alert alert-info">
-A utilização da funcionalidade do carrinho abandonado é opcional, não gerando impacto para lojas que não fizerem o seu uso.
-</div>
+>ℹ️ A utilização da funcionalidade do carrinho abandonado é opcional, não gerando impacto para lojas que não fizerem o seu uso.
 
 ## Segurança das informações
 
@@ -54,6 +50,4 @@ Para saber mais sobre proteção de dados, acesse [Segurança do SmartCheckout](
 Quando novos parâmetros são inseridos em uma URL, como por exemplo a `querystring`, o rastreamento de páginas pode ser alterado, impactando avaliações realizadas por sistemas como o funil de conversão do Google Analytics. Para utilizar serviço de rastreamento de páginas com parâmetros adicionais, veja as regras atualizadas em 
 [como configurar funil de vendas no Google Analytics](https://help.vtex.com/pt/faq/configurar-funil-de-vendas-no-google-analytics).
 
-<div class="alert alert-info">
-Caso utilize outro sistema de rastreamento de página em sua loja, verifique a documentação interna deste sistema.
-</div>
+>ℹ️ Caso utilize outro sistema de rastreamento de página em sua loja, verifique a documentação interna deste sistema.
diff --git a/docs/tutorials/pt/what-is-the-sponsor-user.md b/docs/tutorials/pt/what-is-the-sponsor-user.md
index ad111ae8c..4cedf2569 100644
--- a/docs/tutorials/pt/what-is-the-sponsor-user.md
+++ b/docs/tutorials/pt/what-is-the-sponsor-user.md
@@ -43,7 +43,5 @@ Somente o usuário Titular pode realizar as seguintes ações essenciais de manu
 
 Além disso, quando a VTEX precisa comunicar informações sensíveis à loja, como mudanças em perfis de acesso, tal comunicação é feita direta e exclusivamente com o usuário Titular.
 
-<div class="alert alert-info">
-A criação de <a href="https://help.vtex.com/pt/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet">credenciais de autenticação</a> (appKey/appToken) para integrações via API não é mais restrita ao usuário Titular. Veja este <a href="https://help.vtex.com/pt/announcements/mudancas-no-nome-e-acoes-restritas-disponiveis-para-o-usuario-master">anúncio</a> para mais detalhes sobre esta mudança.
-</div>
+>ℹ️ A criação de [credenciais de autenticação](https://help.vtex.com/pt/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) (appKey/appToken) para integrações via API não é mais restrita ao usuário Titular. Veja este [anúncio](https://help.vtex.com/pt/announcements/mudancas-no-nome-e-acoes-restritas-disponiveis-para-o-usuario-master) para mais detalhes sobre esta mudança.
 
diff --git a/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md b/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md
index 14376f432..aa13721ff 100644
--- a/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md
+++ b/docs/tutorials/pt/what-to-do-when-a-customer-opens-dispute.md
@@ -19,9 +19,7 @@ No momento em que uma disputa é aberta, o lojista é notificado pelo email do O
 
 Vale ressaltar que o lojista tem um prazo de sete dias corridos para responder o email com todos os anexos.
 
-<div class="alert alert-danger">
-<strong>Atenção:</strong> caso a documentação não seja enviada no prazo estipulado ou esteja incorreta e não seja corrigida, o lojista perderá a disputa.
-</div>
+>❗ **Atenção:** caso a documentação não seja enviada no prazo estipulado ou esteja incorreta e não seja corrigida, o lojista perderá a disputa.
 
 Para se abrir uma disputa, o lojista deve enviar um email com o assunto Defesa Disputa - [Nome da Account VTEX] - ID da Autorização, para os emails  **enviochargeback@ssf.zoop.com.br**  e **payment@vtex.com.br**. O email deve conter os seguintes documentos:
 
diff --git a/docs/tutorials/pt/when-should-i-group-products-in-the-same-shipment.md b/docs/tutorials/pt/when-should-i-group-products-in-the-same-shipment.md
index e254b7fdd..d43b358d7 100644
--- a/docs/tutorials/pt/when-should-i-group-products-in-the-same-shipment.md
+++ b/docs/tutorials/pt/when-should-i-group-products-in-the-same-shipment.md
@@ -23,9 +23,7 @@ Remessa é o nome dado ao conjunto de pacotes que será enviado ao __mesmo temp
 
 Esta é uma pratica válida, por exemplo, no caso de transportadoras como os Correios, em que para cada entrega é necessário a nota fiscal, que muitas vezes é a mesma para vários itens, ou em um cenário que o lojista possua estoques fisicamente distantes, mas que compartilhem da mesma doca.
 
-<div class="alert alert-warning">
-Os grupos de remessa são criados pela somatória do tempo de custo do Estoque até a Doca e do tempo de custo da Doca.
-</div>
+>⚠️ Os grupos de remessa são criados pela somatória do tempo de custo do Estoque até a Doca e do tempo de custo da Doca.
 
 ### Artigos relacionados
 - [Configurar remessa](/pt/tutorial/como-funciona-a-remessa)
diff --git a/docs/tutorials/pt/when-will-money-from-sale-be-credited-to-my-account.md b/docs/tutorials/pt/when-will-money-from-sale-be-credited-to-my-account.md
index 95eeda065..594750841 100644
--- a/docs/tutorials/pt/when-will-money-from-sale-be-credited-to-my-account.md
+++ b/docs/tutorials/pt/when-will-money-from-sale-be-credited-to-my-account.md
@@ -31,6 +31,4 @@ Ou seja:
 
 Além disso, é importante frisar que quando a data esperada de pagamento cai em feriado ou em finais de semana, o dinheiro é transferido para o lojista no próximo dia útil. A regra é aplicada em todos os planos de recebimentos do VTEX Payment.
 
-<div class="alert alert-info">
-<strong>Atenção</strong>: Mudar de plano não interfere na data de recebimento das vendas, tampouco nas taxas aplicadas ao valor do produto. Por exemplo, caso um item seja parcelado em três vezes enquanto o Plano D30 estava em vigor, as taxas e as datas de recebimento aplicadas a esse plano valerão para todas as parcelas. Mesmo que o lojista opte por adotar outro plano nesse intervalo de tempo..    
-</div>
+>ℹ️ **Atenção**: Mudar de plano não interfere na data de recebimento das vendas, tampouco nas taxas aplicadas ao valor do produto. Por exemplo, caso um item seja parcelado em três vezes enquanto o Plano D30 estava em vigor, as taxas e as datas de recebimento aplicadas a esse plano valerão para todas as parcelas. Mesmo que o lojista opte por adotar outro plano nesse intervalo de tempo..
diff --git a/docs/tutorials/pt/white-label-sellers-selection.md b/docs/tutorials/pt/white-label-sellers-selection.md
index b37a28a6a..2e418a4c5 100644
--- a/docs/tutorials/pt/white-label-sellers-selection.md
+++ b/docs/tutorials/pt/white-label-sellers-selection.md
@@ -51,9 +51,7 @@ Quando um cliente está navegando no marketplace e sua localização não é con
 
 Seja por meio de geocoordenadas capturadas ou por dados fornecidos pelo cliente, quando o marketplace dispõe da localização do cliente, a plataforma VTEX consegue consultar todos os sellers que atendem àquela região para exibir preço e disponibilidade de produtos na vitrine. Saiba mais em [Configurar preço e disponibilidade de SKUs por Region](https://help.vtex.com/pt/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc).
 
-<div class="alert alert-warning">
-Quando a localização do cliente é conhecida, a consulta a todos os sellers é o comportamento padrão da plataforma VTEX, conforme a funcionalidade <a href="https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release">Region v2</a>. No entanto, é possível que algumas lojas VTEX ainda operem com o Region v1, que possui limitações na seleção de sellers para a vitrine.
-</div>
+>⚠️ Quando a localização do cliente é conhecida, a consulta a todos os sellers é o comportamento padrão da plataforma VTEX, conforme a funcionalidade [Region v2](https://developers.vtex.com/vtex-developer-docs/changelog/region-v2-release). No entanto, é possível que algumas lojas VTEX ainda operem com o Region v1, que possui limitações na seleção de sellers para a vitrine.
 
 ## Seleção de sellers no carrinho
 
diff --git a/docs/tutorials/pt/why-does-payment-with-registered-bank-slip-require-authentication.md b/docs/tutorials/pt/why-does-payment-with-registered-bank-slip-require-authentication.md
index 6b20b6682..2ca4db4aa 100644
--- a/docs/tutorials/pt/why-does-payment-with-registered-bank-slip-require-authentication.md
+++ b/docs/tutorials/pt/why-does-payment-with-registered-bank-slip-require-authentication.md
@@ -23,6 +23,4 @@ Estas informações ficam salvas no perfil do cliente e são exibidas no boleto
 
 Por conta disso, o login é solicitado tanto no momento da __escolha do boleto registrado como meio de pagamento__ quanto para __baixar o boleto na página de fechamento de compra (order placed)__.
 
-<div class="alert alert-info">
-A autenticação é exigida mesmo na primeira compra. Estamos trabalhando para que a autenticação seja exigida somente em casos de recompra, aonde o usuário está com os dados mascarados (pois ainda não passou pelo processo de identificação).
-</div>
+>ℹ️ A autenticação é exigida mesmo na primeira compra. Estamos trabalhando para que a autenticação seja exigida somente em casos de recompra, aonde o usuário está com os dados mascarados (pois ainda não passou pelo processo de identificação).
diff --git a/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md b/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
index a4ac69a5e..d538f7fb9 100644
--- a/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
+++ b/docs/tutorials/pt/why-was-a-customer-able-to-register-a-cpf-in-a-cnpj-field.md
@@ -17,21 +17,16 @@ subcategory: 42hDtnYXHw5ExG6l19RP1l
 
 Este cenário costuma ocorrer por conta de uma inconsistência nos campos de cadastro do usuário. Para verificarmos o cenário, precisamos acessar os dados deste cliente no __Profile System__ da sua loja.
 
-<div class="alert alert-warning">
-Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
-<ul>
-<li>
-<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
-Características das versões do Master Data
-</a>
-</li>
-<li>
-<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
-Master Data v2
-</a>
-</li>
-</ul>
-</div>
+>⚠️ Este artigo diz respeito ao funcionamento do Master Data v1. É importante avaliar qual versão do Master Data atende as necessidades ou está em uso na sua operação. Saiba mais:
+>
+> *<a href="https://help.vtex.com/tutorial/master-data--4otjBnR27u4WUIciQsmkAw#versions-available">
+> Características das versões do Master Data
+> </a>
+>
+> *<a href="https://developers.vtex.com/vtex-rest-api/docs/getting-started-1">
+> Master Data v2
+> </a>
+> 
 
 Siga os passos abaixo para validar as informações:
 
diff --git a/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md b/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md
index 53e85ae97..6973306e3 100644
--- a/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md
+++ b/docs/tutorials/pt/writing-an-effective-ticket-to-vtex-support.md
@@ -49,16 +49,14 @@ Para verificar se o problema está associado ao IO siga os passos abaixo:
       ```
     vtex uninstall {tema}
      ```
-    <div class="alert alert-info">
-    Você pode conferir se existe algum tema instalado usando o comando <code>vtex list</code>, que lista todos os aplicativos instalados na loja.
-    </div>
+    >ℹ️ Você pode conferir se existe algum tema instalado usando o comando `vtex list`, que lista todos os aplicativos instalados na loja.
 4. Clone o tema padrão do Store Framework no seu computador.
 5. No prompt de comando, acesse a pasta do tema padrão.
 6. Rode o comando:
     ```
     vtex link
     ```
-   <div class="alert alert-warning"> Se a sua loja não possui o aplicativo Reviews and Ratings instalado, você pode receber um erro ao tentar linkar. Para evitar isso, remova este app da lista de `peer dependencies` do arquivo `manifest.json` do tema padrão.   </div>
+   >⚠️ Se a sua loja não possui o aplicativo Reviews and Ratings instalado, você pode receber um erro ao tentar linkar. Para evitar isso, remova este app da lista de `peer dependencies` do arquivo `manifest.json` do tema padrão.
 7. Acesse a frente de loja relativa ao seu workspace, usando a URL:
     ```
     https://{workspace}--{accountName}.myvtex.com

From a1c29d6eddd7ef4285102ec8ef2c50d8caa23210 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Tue, 27 Aug 2024 14:05:24 -0300
Subject: [PATCH 11/13] edit fix-callouts.js regex

---
 docs-utils/fix-callouts.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs-utils/fix-callouts.js b/docs-utils/fix-callouts.js
index 93468c5c3..6c731df2e 100644
--- a/docs-utils/fix-callouts.js
+++ b/docs-utils/fix-callouts.js
@@ -74,9 +74,9 @@ function processFile(filePath) {
 
         // Replace HTML structures with corresponding markdown symbols
         const newData = data
-            .replace(/<div class="alert alert-info">(.*?)<\/div>/gs, (match, p1) => `>ℹ️ ${convertCallout(p1)}`)
-            .replace(/<div class="alert alert-warning">(.*?)<\/div>/gs, (match, p1) => `>⚠️ ${convertCallout(p1)}`)
-            .replace(/<div class="alert alert-danger">(.*?)<\/div>/gs, (match, p1) => `>❗ ${convertCallout(p1)}`);
+            .replace(/<div\s+class\s*=\s*"alert alert-info">(.*?)<\/div>/gs, (match, p1) => `>ℹ️ ${convertCallout(p1)}`)
+            .replace(/<div\s+class\s*=\s*"alert alert-warning">(.*?)<\/div>/gs, (match, p1) => `>⚠️ ${convertCallout(p1)}`)
+            .replace(/<div\s+class\s*=\s*"alert alert-danger">(.*?)<\/div>/gs, (match, p1) => `>❗ ${convertCallout(p1)}`);
 
         // Write the modified content back to the file
         fs.writeFile(filePath, newData, 'utf8', (err) => {

From e980a35f90b9dac70e138b52e93949b8009fcc61 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Tue, 27 Aug 2024 14:06:00 -0300
Subject: [PATCH 12/13] run fix-callouts.js

---
 ...automatic-archiving-inactive-promotions.md |  4 +-
 .../checkout-api-now-supports-recaptcha-v3.md |  4 +-
 ...ing-up-the-cardholder-document-id-field.md |  8 +---
 ...xpand-your-operation-through-vtex-admin.md |  4 +-
 ...le-shopping-new-option-to-submit-prices.md |  4 +-
 ...your-fbaclassic-dba-orders-in-one-place.md |  4 +-
 .../en/marketplace-seller-network.md          |  4 +-
 .../new-cdn-gives-more-security-and-speed.md  |  8 ++--
 ...ew-events-available-in-the-audit-module.md |  4 +-
 ...uthorization-flow-for-native-connectors.md |  4 +-
 ...der-and-anti-fraud-management-interface.md |  4 +-
 .../en/partial-invoice-settlements-in-oms.md  |  4 +-
 ...agination-will-change-in-the-search-api.md |  4 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |  4 +-
 ...eckout-will-now-be-unchecked-by-default.md |  8 ++--
 .../en/vtex-insurance-discontinuity.md        |  2 +-
 ...automatic-archiving-inactive-promotions.md |  4 +-
 ...ing-up-the-cardholder-document-id-field.md |  8 +---
 ...xpand-your-operation-through-vtex-admin.md |  4 +-
 ...le-shopping-new-option-to-submit-prices.md |  4 +-
 ...the-catalog-through-web-service-will-be.md |  4 +-
 ...your-fbaclassic-dba-orders-in-one-place.md |  4 +-
 .../es/marketplace-seller-network.md          |  4 +-
 .../new-cdn-gives-more-security-and-speed.md  |  8 ++--
 ...ew-events-available-in-the-audit-module.md |  4 +-
 ...bute-for-products-sent-to-mercado-libre.md |  4 +-
 ...uthorization-flow-for-native-connectors.md |  4 +-
 ...der-and-anti-fraud-management-interface.md |  4 +-
 .../es/partial-invoice-settlements-in-oms.md  |  4 +-
 ...agination-will-change-in-the-search-api.md |  4 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |  4 +-
 ...eckout-will-now-be-unchecked-by-default.md |  4 +-
 .../es/vtex-insurance-discontinuity.md        |  2 +-
 ...login-now-needs-2-factor-authentication.md |  4 +-
 ...automatic-archiving-inactive-promotions.md |  4 +-
 .../pt/boost-your-marketplace-sales.md        |  4 +-
 ...ing-up-the-cardholder-document-id-field.md |  8 +---
 ...xpand-your-operation-through-vtex-admin.md |  4 +-
 ...le-shopping-new-option-to-submit-prices.md |  4 +-
 ...your-fbaclassic-dba-orders-in-one-place.md |  4 +-
 ...ew-events-available-in-the-audit-module.md |  4 +-
 ...uthorization-flow-for-native-connectors.md |  4 +-
 ...der-and-anti-fraud-management-interface.md |  4 +-
 .../pt/new-ready-to-dispatch-functionality.md |  4 +-
 .../pt/partial-invoice-settlements-in-oms.md  |  4 +-
 ...agination-will-change-in-the-search-api.md |  4 +-
 ...ers-in-the-vtex-admin-global-search-bar.md |  4 +-
 .../pt/vtex-insurance-discontinuity.md        |  2 +-
 ...h-specification-parameter-returns-empty.md |  4 +-
 ...earch-term-not-return-existing-products.md |  4 +-
 ...ilter-bringing-any-result-in-the-search.md |  4 +-
 ...y-vtex-search-engine-ignores-some-terms.md |  4 +-
 ...was-not-an-order-sent-to-the-anti-fraud.md |  4 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |  4 +-
 .../nao-encontro-uma-colecao-o-que-fazer.md   |  4 +-
 ...h-specification-parameter-returns-empty.md |  4 +-
 ...earch-term-not-return-existing-products.md |  4 +-
 ...ilter-bringing-any-result-in-the-search.md |  4 +-
 ...y-vtex-search-engine-ignores-some-terms.md |  4 +-
 ...was-not-an-order-sent-to-the-anti-fraud.md |  4 +-
 ...iption-but-it-doesnt-appear-on-the-site.md |  4 +-
 .../nao-encontro-uma-colecao-o-que-fazer.md   |  4 +-
 ...h-specification-parameter-returns-empty.md |  4 +-
 ...earch-term-not-return-existing-products.md |  4 +-
 ...ilter-bringing-any-result-in-the-search.md |  4 +-
 ...y-vtex-search-engine-ignores-some-terms.md |  4 +-
 ...date-of-deliveries-tracking-by-correios.md |  4 +-
 ...product-registration-search-doesnt-work.md |  4 +-
 ...ode-hyphen-and-replaces-it-with-a-space.md |  4 +-
 ...ch-doesnt-work-for-a-second-folderlevel.md |  4 +-
 ...talizer-and-filters-showing-wrong-value.md |  4 +-
 ...lection-filter-disregards-searched-term.md |  4 +-
 ...olders-dont-consider-the-search-context.md |  4 +-
 ...experience-some-trouble-on-firefox-89-0.md |  4 +-
 ...date-of-deliveries-tracking-by-correios.md |  4 +-
 ...product-registration-search-doesnt-work.md |  4 +-
 ...ode-hyphen-and-replaces-it-with-a-space.md |  4 +-
 ...talizer-and-filters-showing-wrong-value.md |  4 +-
 ...lection-filter-disregards-searched-term.md |  4 +-
 ...olders-dont-consider-the-search-context.md |  4 +-
 ...experience-some-trouble-on-firefox-89-0.md |  4 +-
 ...date-of-deliveries-tracking-by-correios.md |  4 +-
 ...product-registration-search-doesnt-work.md |  4 +-
 ...ode-hyphen-and-replaces-it-with-a-space.md |  4 +-
 ...ch-doesnt-work-for-a-second-folderlevel.md |  4 +-
 ...talizer-and-filters-showing-wrong-value.md |  4 +-
 ...lection-filter-disregards-searched-term.md |  4 +-
 ...olders-dont-consider-the-search-context.md |  4 +-
 ...experience-some-trouble-on-firefox-89-0.md |  4 +-
 docs/tracks/en/add-on-products.md             |  4 +-
 .../tracks/en/adding-new-stores-to-instore.md |  4 +-
 docs/tracks/en/allowing-order-replacement.md  |  8 +---
 docs/tracks/en/autocomplete-search.md         | 15 ++-----
 docs/tracks/en/backend-integrations.md        | 12 ++----
 docs/tracks/en/billing-support.md             |  8 +---
 docs/tracks/en/canceling-an-order.md          |  4 +-
 docs/tracks/en/configuring-synonyms.md        |  2 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |  4 +-
 docs/tracks/en/creating-regular-promotions.md | 20 +++------
 docs/tracks/en/facebook-business-extension.md |  4 +-
 docs/tracks/en/facebook.md                    |  4 +-
 docs/tracks/en/frontend-implementation.md     | 16 ++-----
 .../en/getting-started-with-logistics.md      | 12 +++---
 docs/tracks/en/go-live-process.md             |  8 +---
 docs/tracks/en/google-pay.md                  | 16 ++-----
 .../how-does-vtex-intelligent-search-work.md  |  8 +---
 ...-and-edit-transactional-email-templates.md |  4 +-
 docs/tracks/en/how-vtex-support-works.md      |  6 +--
 ...ating-instore-to-a-new-payment-acquirer.md |  4 +-
 docs/tracks/en/integration-configurations.md  | 43 +++++++++----------
 docs/tracks/en/inventory.md                   |  8 +---
 .../managing-sales-associates-in-instore.md   |  8 +---
 .../en/manual-product-matching-on-amazon.md   |  4 +-
 docs/tracks/en/mapping-colors-and-sizes.md    | 14 ++----
 docs/tracks/en/opening-tickets.md             |  4 +-
 docs/tracks/en/partial-invoices.md            |  8 +---
 docs/tracks/en/pre-go-live.md                 |  4 +-
 .../en/reports-vtex-intelligent-search.md     |  8 +---
 .../en/sending-products-to-google-shopping.md |  4 +-
 ...app-linking-for-payments-app-in-instore.md |  4 +-
 docs/tracks/en/settings.md                    | 18 ++++----
 .../en/shipping-costs-and-simulation.md       |  4 +-
 docs/tracks/en/shipping-strategies.md         | 28 +++++-------
 docs/tracks/en/synonyms.md                    |  4 +-
 docs/tracks/en/unified-search.md              |  4 +-
 .../viewing-the-email-history-of-an-order.md  |  4 +-
 docs/tracks/en/vtex-modules-ii.md             |  8 +---
 ...hat-features-does-the-integration-offer.md |  4 +-
 docs/tracks/en/what-is-the-master-user.md     |  4 +-
 docs/tracks/es/accounts-and-architecture.md   |  4 +-
 docs/tracks/es/add-on-products.md             |  4 +-
 docs/tracks/es/adding-collections-track.md    |  4 +-
 .../tracks/es/adding-new-stores-to-instore.md |  4 +-
 docs/tracks/es/allowing-order-replacement.md  |  8 +---
 docs/tracks/es/autocomplete-search.md         | 15 ++-----
 docs/tracks/es/backend-integrations.md        | 12 ++----
 docs/tracks/es/billing-support.md             |  8 +---
 docs/tracks/es/canceling-an-order.md          |  4 +-
 docs/tracks/es/configuring-synonyms.md        |  2 +-
 ...-integration-with-fbe-in-the-vtex-admin.md |  4 +-
 docs/tracks/es/create-the-category-tree.md    |  8 +---
 docs/tracks/es/creating-regular-promotions.md | 22 +++-------
 .../es/enabling-product-recommendations.md    |  4 +-
 docs/tracks/es/facebook-business-extension.md |  4 +-
 docs/tracks/es/facebook.md                    |  4 +-
 docs/tracks/es/frontend-implementation.md     | 16 ++-----
 .../es/getting-started-with-logistics.md      | 11 ++---
 docs/tracks/es/go-live-process.md             |  8 +---
 docs/tracks/es/google-pay.md                  | 16 ++-----
 .../how-does-vtex-intelligent-search-work.md  |  8 +---
 ...-and-edit-transactional-email-templates.md |  4 +-
 docs/tracks/es/how-vtex-support-works.md      |  4 +-
 docs/tracks/es/integration-configurations.md  |  9 ++--
 docs/tracks/es/inventory.md                   |  8 +---
 .../managing-sales-associates-in-instore.md   |  8 +---
 .../es/manual-product-matching-on-amazon.md   |  4 +-
 docs/tracks/es/mapping-colors-and-sizes.md    | 12 ++----
 ...egories-and-attributes-to-mercado-libre.md |  4 +-
 docs/tracks/es/opening-tickets.md             |  4 +-
 docs/tracks/es/partial-invoices.md            |  8 +---
 docs/tracks/es/pre-go-live.md                 |  4 +-
 .../es/reports-vtex-intelligent-search.md     |  8 +---
 .../es/sending-product-data-to-dafiti.md      |  4 +-
 .../es/sending-products-to-google-shopping.md |  4 +-
 docs/tracks/es/set-a-price-for-the-sku.md     |  4 +-
 docs/tracks/es/settings.md                    | 18 ++++----
 .../es/shipping-costs-and-simulation.md       |  4 +-
 docs/tracks/es/shipping-strategies.md         | 24 ++++-------
 docs/tracks/es/synonyms.md                    |  4 +-
 docs/tracks/es/unified-search.md              |  4 +-
 .../viewing-the-email-history-of-an-order.md  |  4 +-
 docs/tracks/es/vtex-modules-ii.md             |  4 +-
 docs/tracks/es/what-is-the-master-user.md     |  4 +-
 docs/tracks/pt/add-on-products.md             |  4 +-
 .../tracks/pt/adding-new-stores-to-instore.md |  4 +-
 docs/tracks/pt/allowing-order-replacement.md  |  8 +---
 docs/tracks/pt/autocomplete-search.md         | 15 ++-----
 docs/tracks/pt/backend-integrations.md        | 12 ++----
 docs/tracks/pt/billing-support.md             |  8 +---
 docs/tracks/pt/canceling-an-order.md          |  4 +-
 docs/tracks/pt/configure-integration.md       |  6 +--
 docs/tracks/pt/configuring-banners.md         |  4 +-
 .../tracks/pt/configuring-dafiti-connector.md |  6 +--
 .../pt/configuring-payment-connectors.md      |  4 +-
 docs/tracks/pt/configuring-synonyms.md        |  6 +--
 .../pt/configuring-the-connector-b2w.md       | 10 ++---
 ...-integration-with-fbe-in-the-vtex-admin.md |  4 +-
 docs/tracks/pt/creating-regular-promotions.md | 20 +++------
 docs/tracks/pt/facebook-business-extension.md |  4 +-
 docs/tracks/pt/facebook.md                    |  4 +-
 docs/tracks/pt/frontend-implementation.md     | 16 ++-----
 .../pt/getting-started-with-logistics.md      | 10 ++---
 docs/tracks/pt/go-live-process.md             |  8 +---
 .../how-does-vtex-intelligent-search-work.md  | 16 ++-----
 ...-and-edit-transactional-email-templates.md |  4 +-
 ...usiness-extension-e-conversions-api-app.md |  4 +-
 docs/tracks/pt/integration-configurations.md  |  9 ++--
 docs/tracks/pt/integration-overview-b2w.md    |  4 +-
 docs/tracks/pt/inventory.md                   |  8 +---
 .../managing-sales-associates-in-instore.md   |  8 +---
 .../pt/manual-product-matching-on-amazon.md   |  4 +-
 docs/tracks/pt/mapping-colors-and-sizes.md    | 12 ++----
 ...egories-and-attributes-to-mercado-libre.md |  4 +-
 docs/tracks/pt/opening-tickets.md             |  4 +-
 docs/tracks/pt/partial-invoices.md            |  8 +---
 docs/tracks/pt/pre-go-live.md                 |  4 +-
 .../registering-the-carrefour-integration.md  | 10 ++---
 .../registering-the-centauro-integration.md   |  6 +--
 docs/tracks/pt/registering-the-integration.md |  6 +--
 .../registering-the-netshoes-integration.md   |  6 +--
 .../pt/reports-vtex-intelligent-search.md     |  8 +---
 .../pt/sending-product-data-to-dafiti.md      |  4 +-
 .../pt/sending-products-to-google-shopping.md |  4 +-
 docs/tracks/pt/settings.md                    | 18 ++++----
 .../pt/shipping-costs-and-simulation.md       |  4 +-
 docs/tracks/pt/shipping-strategies.md         | 31 ++++++-------
 docs/tracks/pt/synonyms.md                    |  4 +-
 docs/tracks/pt/unified-search.md              |  4 +-
 .../untitled-entry-2019-11-25-at-06-07-48.md  |  4 +-
 .../viewing-the-email-history-of-an-order.md  |  4 +-
 docs/tracks/pt/vtex-modules-ii.md             |  8 +---
 docs/tracks/pt/what-is-the-master-user.md     |  4 +-
 docs/tracks/pt/what-is-vtex-payment.md        |  4 +-
 .../en/accessing-the-beta-environment.md      |  8 +---
 .../en/adding-sku-specifications-or-fields.md | 16 ++-----
 ...adding-specifications-or-product-fields.md |  8 +---
 .../advertising-with-vtex-ad-network-beta.md  | 16 ++-----
 docs/tutorials/en/affiliates-program-app.md   | 20 +++------
 docs/tutorials/en/all-orders.md               |  4 +-
 docs/tutorials/en/analytics.md                |  8 +---
 docs/tutorials/en/application-keys.md         |  4 +-
 docs/tutorials/en/audit.md                    | 12 ++----
 docs/tutorials/en/autocomplete.md             | 15 ++-----
 docs/tutorials/en/b2b-checkout-settings.md    |  4 +-
 .../best-practices-against-virtual-attacks.md |  8 +---
 .../en/best-practices-application-keys.md     |  4 +-
 ...ices-for-the-success-of-your-vtex-store.md | 24 +++--------
 docs/tutorials/en/beta-price-configuration.md |  4 +-
 docs/tutorials/en/buy-one-get-one.md          | 12 ++----
 ...e-worksheet-exported-from-orders-module.md |  4 +-
 docs/tutorials/en/campaign-promotion.md       |  8 +---
 docs/tutorials/en/canceling-orders.md         |  4 +-
 docs/tutorials/en/carrier-working-hours.md    |  4 +-
 ...egory-variations-and-attributes-mapping.md |  4 +-
 docs/tutorials/en/change-seller.md            |  4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |  4 +-
 .../changing-items-from-a-complete-order.md   |  4 +-
 .../changing-the-total-cost-of-the-order.md   |  4 +-
 ...ount-franchise-account-or-seller-portal.md |  4 +-
 docs/tutorials/en/collection-types.md         |  4 +-
 docs/tutorials/en/comprehensive-seller.md     |  4 +-
 ...onfiguring-a-seller-on-vtex-marketplace.md | 16 ++-----
 .../en/configuring-access-without-www.md      |  4 +-
 ...port-for-organizations-and-cost-centers.md | 16 ++-----
 .../en/configuring-dns-pointing-to-vtex.md    | 22 ++++------
 ...nfiguring-domains-in-account-management.md |  4 +-
 .../configuring-payment-conditions-for-b2b.md |  4 +-
 .../en/configuring-price-divergence-rule.md   |  8 +---
 ...configuring-promotions-for-marketplaces.md |  8 +---
 docs/tutorials/en/configuring-xml.md          |  4 +-
 .../en/creating-a-more-for-less-promotion.md  | 16 +++----
 ...ing-a-specification-group-in-a-category.md |  4 +-
 .../tutorials/en/creating-collections-beta.md |  6 +--
 .../en/creating-landing-pages-per-binding.md  |  8 +---
 docs/tutorials/en/creating-landing-pages.md   | 10 +----
 docs/tutorials/en/creating-pickup-points.md   | 11 ++---
 docs/tutorials/en/creating-price-tables.md    |  6 +--
 .../en/creating-service-for-a-sku.md          |  8 +---
 docs/tutorials/en/creating-synonyms.md        |  2 +-
 ...data-dictionary-vtex-data-pipeline-beta.md |  4 +-
 docs/tutorials/en/data-subject-rights.md      | 16 ++-----
 .../en/declining-order-cancelation.md         |  8 +---
 .../en/deleting-a-folder-from-cms.md          |  8 ++--
 ...-vtex-ad-network-ads-in-your-store-beta.md |  4 +-
 ...ic-relevance-in-intelligent-search-beta.md |  8 +---
 .../tutorials/en/events-available-in-audit.md |  4 +-
 ...mporting-product-and-sku-specifications.md |  8 +---
 docs/tutorials/en/filtering-all-orders.md     | 20 +++------
 ...es-with-blocked-terms-to-return-results.md |  4 +-
 ...d-questions-new-orders-module-interface.md |  4 +-
 .../en/fulfillment-logistics-vtex.md          | 13 +++---
 docs/tutorials/en/generating-a-har-file.md    |  8 +---
 docs/tutorials/en/gift-card.md                |  4 +-
 docs/tutorials/en/google-analytics-faq.md     |  4 +-
 docs/tutorials/en/google-pay-beta.md          | 20 +++------
 .../tutorials/en/how-does-reservation-work.md | 12 ++----
 .../tutorials/en/how-does-vtex-search-work.md |  4 +-
 docs/tutorials/en/how-my-account-works.md     |  8 +---
 .../en/how-shipping-calculation-works.md      | 16 ++-----
 docs/tutorials/en/how-subscriptions-work.md   |  4 +-
 .../en/how-the-order-replacement-works.md     |  2 +-
 .../tutorials/en/how-to-change-order-items.md | 10 ++---
 .../tutorials/en/how-to-change-orders-beta.md |  4 +-
 .../en/how-to-configure-subscriptions.md      |  4 +-
 ...ow-to-configure-xml-for-google-shopping.md | 12 ++----
 ...eate-landing-pages-with-customized-urls.md |  4 +-
 ...dentify-an-order-split-from-omnichannel.md |  4 +-
 .../how-to-identify-order-closing-errors.md   |  4 +-
 ...identify-promotions-applied-to-the-cart.md |  4 +-
 .../en/how-to-integrate-with-facebook.md      |  2 +-
 .../en/how-to-manage-subscriptions.md         |  4 +-
 .../en/how-to-manually-invoice-an-order.md    |  4 +-
 ...optimize-searches-with-substitute-words.md |  3 +-
 .../tutorials/en/how-to-return-order-items.md |  4 +-
 .../en/how-to-update-the-image-of-an-sku.md   |  8 +---
 docs/tutorials/en/how-to-use-rebates.md       |  4 +-
 .../en/i-cant-import-the-price-table.md       | 12 ++----
 .../en/i-cant-receive-emails-from-vtex.md     |  8 +---
 ...-view-the-product-in-the-search-results.md | 16 ++-----
 ...-and-exporting-an-inventory-spreadsheet.md |  4 +-
 .../en/integrating-with-mercado-livre.md      |  4 +-
 ...e-for-marketplaces-marketplace-non-vtex.md |  8 +---
 docs/tutorials/en/interaction-details.md      |  4 +-
 docs/tutorials/en/inventory-update-history.md |  9 ++--
 ...ble-to-use-the-vtex-admin-search-report.md |  4 +-
 .../lead-time-shipping-time-at-sku-level.md   |  8 +---
 .../tutorials/en/license-manager-resources.md |  4 +-
 docs/tutorials/en/loading-dock.md             | 18 ++++----
 .../making-product-collections-searchable.md  |  4 +-
 .../en/managing-delivery-capacity.md          |  4 +-
 docs/tutorials/en/managing-http-headers.md    |  4 +-
 .../en/managing-shipping-policies.md          |  4 +-
 docs/tutorials/en/managing-stock-items.md     |  2 +-
 docs/tutorials/en/master-data.md              | 16 ++-----
 .../en/my-store-order-was-not-created.md      |  4 +-
 docs/tutorials/en/offer-details.md            |  4 +-
 docs/tutorials/en/offer-management.md         |  4 +-
 docs/tutorials/en/oms-page-structure.md       |  8 +---
 ...pening-tickets-to-vtex-support-finacial.md | 12 ++----
 .../tutorials/en/operational-capacity-beta.md |  8 +---
 .../en/order-allocation-algorithm-beta.md     |  8 +---
 ...-cancellation-requested-by-the-customer.md |  8 +---
 docs/tutorials/en/order-details-page.md       | 12 ++----
 docs/tutorials/en/order-flow-and-status.md    | 16 ++-----
 docs/tutorials/en/order-report.md             |  4 +-
 .../en/order-split-and-delivery-split.md      |  4 +-
 docs/tutorials/en/order-status-table-oms.md   |  4 +-
 docs/tutorials/en/order-tracking.md           |  4 +-
 docs/tutorials/en/orders-overview.md          |  4 +-
 .../en/physical-store-instore-beta.md         |  8 +---
 docs/tutorials/en/pickup-points.md            | 21 +++++----
 docs/tutorials/en/platform-status-page.md     |  4 +-
 ...ier-from-meeting-certain-zip-code-range.md |  4 +-
 docs/tutorials/en/price-divergence-rule.md    |  4 +-
 docs/tutorials/en/prices-settings.md          |  8 +---
 docs/tutorials/en/products-and-skus-beta.md   |  4 +-
 docs/tutorials/en/promotion-alerts-beta.md    |  4 +-
 ...tion-alerts-how-to-create-an-alert-beta.md |  4 +-
 docs/tutorials/en/promotion-examples.md       |  4 +-
 .../protection-against-transaction-attacks.md |  6 +--
 ...ed-checkouts-with-whatsapp-ai-campaigns.md | 12 ++----
 .../register-tracking-on-the-tax-receipt.md   |  4 +-
 docs/tutorials/en/registering-a-category.md   |  4 +-
 .../en/registering-gateway-affiliations.md    | 14 ++----
 docs/tutorials/en/registering-geolocation.md  |  3 +-
 docs/tutorials/en/regular-promotion.md        | 28 +++---------
 docs/tutorials/en/releases-module-beta.md     | 20 +++------
 docs/tutorials/en/returning-order-items.md    |  4 +-
 .../en/sales-associates-instore-beta.md       | 12 ++----
 docs/tutorials/en/sales-performance.md        |  4 +-
 docs/tutorials/en/search-behavior.md          |  8 +---
 .../en/search-control-fulltextsearchbox.md    |  4 +-
 docs/tutorials/en/search-parameters.md        |  4 +-
 .../en/searching-for-events-on-audit.md       |  8 +---
 .../en/seller-portal-creating-a-promotion.md  |  4 +-
 ...tal-getting-started-for-the-marketplace.md | 16 ++-----
 .../en/sending-sku-attributes-to-amazon.md    |  4 +-
 docs/tutorials/en/sent-offers-beta.md         |  4 +-
 .../en/sent-offers-buybox-opportunities.md    |  4 +-
 docs/tutorials/en/set-up-mundi-gateway.md     |  4 +-
 ...the-grace-period-for-order-cancellation.md |  4 +-
 .../setting-up-3ds-2-authentication-flow.md   |  4 +-
 .../en/setting-up-abandoned-carts.md          |  4 +-
 ...app-linking-for-payments-app-in-instore.md |  4 +-
 .../en/setting-up-mundipagg-gateway.md        |  4 +-
 docs/tutorials/en/setting-up-my-account.md    |  4 +-
 ...rice-and-availability-of-skus-by-region.md |  4 +-
 .../en/setting-up-product-comparison.md       |  4 +-
 ...ween-a-marketplace-and-a-seller-on-vtex.md | 12 ++----
 docs/tutorials/en/shipping-options-beta.md    |  8 +---
 docs/tutorials/en/shipping-simulation.md      |  4 +-
 docs/tutorials/en/sku-bindings.md             | 16 ++-----
 docs/tutorials/en/sku-registration-fields.md  |  4 +-
 ...-customer-information-automatic-fill-in.md | 21 ++++-----
 docs/tutorials/en/smartcheckout-security.md   |  5 +--
 docs/tutorials/en/special-conditions.md       |  4 +-
 docs/tutorials/en/store-overview-beta.md      |  4 +-
 docs/tutorials/en/telesales-features.md       |  4 +-
 ...actional-emails-for-subscription-orders.md |  4 +-
 ...eshooting-errors-in-subscription-orders.md |  4 +-
 ...divergence-errors-in-marketplace-orders.md |  4 +-
 .../visao-geral-da-estrutura-do-catalogo.md   |  4 +-
 docs/tutorials/en/vtex-ad-network-beta.md     |  4 +-
 docs/tutorials/en/vtex-admin-start-here.md    |  4 +-
 docs/tutorials/en/vtex-do-interface.md        |  4 +-
 .../en/vtex-pick-and-pack-fulfillment.md      | 24 +++--------
 .../en/vtex-pick-and-pack-insights.md         |  4 +-
 .../en/vtex-pick-and-pack-last-mile.md        |  4 +-
 .../tutorials/en/vtex-pick-and-pack-mobile.md |  4 +-
 .../tutorials/en/vtex-pick-and-pack-orders.md |  4 +-
 .../en/vtex-pick-and-pack-settings.md         | 12 ++----
 .../en/vtex-pick-and-pack-worksheets.md       |  4 +-
 docs/tutorials/en/vtex-pick-and-pack.md       |  8 +---
 docs/tutorials/en/web-page-performance.md     | 16 ++-----
 docs/tutorials/en/what-are-layouts.md         |  8 ++--
 docs/tutorials/en/what-is-a-service.md        |  4 +-
 docs/tutorials/en/what-is-an-attachment.md    |  4 +-
 .../en/what-is-order-configuration.md         |  4 +-
 ...tween-sales-policy-affiliate-and-seller.md |  4 +-
 ...tween-unbinding-and-removing-seller-sku.md |  4 +-
 docs/tutorials/en/what-is-the-sponsor-user.md |  4 +-
 ...-a-product-words-that-may-be-ignored-by.md |  4 +-
 docs/tutorials/en/white-label-seller.md       |  8 +---
 .../en/white-label-sellers-selection.md       | 29 +++++--------
 .../es/accessing-the-beta-environment.md      |  8 +---
 docs/tutorials/es/adding-collections-cms.md   |  4 +-
 .../es/adding-sku-specifications-or-fields.md | 16 ++-----
 ...adding-specifications-or-product-fields.md |  8 +---
 .../advertising-with-vtex-ad-network-beta.md  | 16 ++-----
 docs/tutorials/es/affiliates-program-app.md   | 20 +++------
 docs/tutorials/es/all-orders.md               |  4 +-
 docs/tutorials/es/analytics.md                |  8 +---
 docs/tutorials/es/application-keys.md         |  4 +-
 docs/tutorials/es/audit.md                    | 12 ++----
 docs/tutorials/es/autocomplete.md             | 15 ++-----
 docs/tutorials/es/b2b-checkout-settings.md    |  4 +-
 .../best-practices-against-virtual-attacks.md |  8 +---
 .../es/best-practices-application-keys.md     |  4 +-
 ...ices-for-the-success-of-your-vtex-store.md | 24 +++--------
 docs/tutorials/es/beta-price-configuration.md |  8 +---
 docs/tutorials/es/buy-one-get-one.md          | 12 ++----
 ...e-worksheet-exported-from-orders-module.md |  4 +-
 docs/tutorials/es/campaign-promotion.md       |  8 +---
 docs/tutorials/es/canceling-orders.md         |  4 +-
 docs/tutorials/es/carrier-working-hours.md    |  4 +-
 docs/tutorials/es/change-seller.md            |  4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |  4 +-
 .../changing-items-from-a-complete-order.md   |  4 +-
 .../changing-the-total-cost-of-the-order.md   |  4 +-
 ...ount-franchise-account-or-seller-portal.md |  4 +-
 .../es/collection-highlight-control.md        |  4 +-
 docs/tutorials/es/collection-types.md         |  4 +-
 docs/tutorials/es/comprehensive-seller.md     |  4 +-
 ...onfiguring-a-seller-on-vtex-marketplace.md | 16 ++-----
 .../es/configuring-access-without-www.md      |  4 +-
 ...port-for-organizations-and-cost-centers.md | 12 ++----
 .../es/configuring-dns-pointing-to-vtex.md    | 22 ++++------
 ...nfiguring-domains-in-account-management.md |  4 +-
 .../configuring-payment-conditions-for-b2b.md |  4 +-
 .../es/configuring-price-divergence-rule.md   |  8 +---
 ...configuring-promotions-for-marketplaces.md |  8 +---
 docs/tutorials/es/configuring-xml.md          |  4 +-
 .../es/creating-a-more-for-less-promotion.md  | 12 ++----
 .../es/creating-a-product-collection.md       |  4 +-
 ...ing-a-specification-group-in-a-category.md |  4 +-
 .../tutorials/es/creating-collections-beta.md | 29 ++++---------
 .../es/creating-landing-pages-per-binding.md  |  8 +---
 docs/tutorials/es/creating-landing-pages.md   | 10 +----
 docs/tutorials/es/creating-pickup-points.md   | 13 ++----
 docs/tutorials/es/creating-price-tables.md    | 12 ++----
 .../es/creating-service-for-a-sku.md          |  8 +---
 docs/tutorials/es/creating-synonyms.md        |  2 +-
 docs/tutorials/es/data-subject-rights.md      | 16 ++-----
 .../es/declining-order-cancelation.md         |  8 +---
 docs/tutorials/es/defining-window-displays.md |  4 +-
 .../es/deleting-a-folder-from-cms.md          |  8 ++--
 ...-vtex-ad-network-ads-in-your-store-beta.md |  4 +-
 ...ic-relevance-in-intelligent-search-beta.md |  8 +---
 .../tutorials/es/events-available-in-audit.md |  4 +-
 ...mporting-product-and-sku-specifications.md |  8 +---
 ...ling-out-collection-registration-fields.md |  4 +-
 docs/tutorials/es/filtering-all-orders.md     | 20 +++------
 ...es-with-blocked-terms-to-return-results.md |  4 +-
 ...d-questions-new-orders-module-interface.md |  4 +-
 .../es/fulfillment-logistics-vtex.md          | 10 ++---
 docs/tutorials/es/gift-card.md                |  4 +-
 docs/tutorials/es/google-analytics-faq.md     |  4 +-
 docs/tutorials/es/google-pay-beta.md          | 20 +++------
 .../tutorials/es/how-does-reservation-work.md | 12 ++----
 .../tutorials/es/how-does-vtex-search-work.md |  4 +-
 .../es/how-mercado-livre-integration-works.md |  4 +-
 docs/tutorials/es/how-my-account-works.md     |  8 +---
 .../es/how-shipping-calculation-works.md      | 16 ++-----
 docs/tutorials/es/how-subscriptions-work.md   |  4 +-
 .../tutorials/es/how-to-change-order-items.md | 10 ++---
 .../tutorials/es/how-to-change-orders-beta.md |  4 +-
 .../es/how-to-configure-subscriptions.md      |  4 +-
 ...ow-to-configure-xml-for-google-shopping.md | 12 ++----
 ...eate-landing-pages-with-customized-urls.md |  4 +-
 .../es/how-to-delete-a-collection.md          |  4 +-
 ...dentify-an-order-split-from-omnichannel.md |  4 +-
 .../how-to-identify-order-closing-errors.md   |  4 +-
 ...identify-promotions-applied-to-the-cart.md |  4 +-
 ...llection-of-products-in-the-shop-window.md |  4 +-
 .../es/how-to-integrate-with-facebook.md      |  2 +-
 .../es/how-to-manage-subscriptions.md         |  4 +-
 .../es/how-to-manually-invoice-an-order.md    |  4 +-
 ...optimize-searches-with-substitute-words.md |  4 +-
 .../tutorials/es/how-to-return-order-items.md |  4 +-
 .../es/how-to-update-the-image-of-an-sku.md   |  8 +---
 docs/tutorials/es/how-to-use-rebates.md       |  4 +-
 ...ith-different-layouts-for-the-same-page.md |  4 +-
 .../es/i-cant-import-the-price-table.md       | 12 ++----
 .../es/i-cant-receive-emails-from-vtex.md     |  8 +---
 ...-view-the-product-in-the-search-results.md | 15 ++-----
 ...e-for-marketplaces-marketplace-non-vtex.md |  4 +-
 docs/tutorials/es/interaction-details.md      |  4 +-
 docs/tutorials/es/inventory-update-history.md |  8 ++--
 ...ble-to-use-the-vtex-admin-search-report.md |  4 +-
 .../lead-time-shipping-time-at-sku-level.md   |  8 +---
 .../tutorials/es/license-manager-resources.md |  4 +-
 docs/tutorials/es/loading-dock.md             | 18 ++++----
 .../making-product-collections-searchable.md  |  8 +---
 .../es/managing-delivery-capacity.md          |  4 +-
 docs/tutorials/es/managing-http-headers.md    |  4 +-
 .../es/managing-shipping-policies.md          |  4 +-
 docs/tutorials/es/managing-stock-items.md     |  2 +-
 docs/tutorials/es/master-data.md              | 16 ++-----
 ...ercado-livre-automobilist-compatibility.md | 12 ++----
 docs/tutorials/es/mercado-livre-faq.md        |  4 +-
 .../es/my-store-order-was-not-created.md      |  4 +-
 docs/tutorials/es/offer-details.md            |  4 +-
 docs/tutorials/es/offer-management.md         |  4 +-
 docs/tutorials/es/oms-page-structure.md       |  4 +-
 ...pening-tickets-to-vtex-support-finacial.md | 12 ++----
 .../tutorials/es/operational-capacity-beta.md |  8 +---
 .../es/order-allocation-algorithm-beta.md     |  8 +---
 ...-cancellation-requested-by-the-customer.md |  8 +---
 docs/tutorials/es/order-details-page.md       | 12 ++----
 docs/tutorials/es/order-flow-and-status.md    | 16 ++-----
 docs/tutorials/es/order-report.md             |  4 +-
 .../es/order-split-and-delivery-split.md      |  4 +-
 docs/tutorials/es/order-status-table-oms.md   |  4 +-
 docs/tutorials/es/order-tracking.md           |  4 +-
 docs/tutorials/es/orders-overview.md          |  4 +-
 .../es/physical-store-instore-beta.md         |  8 +---
 docs/tutorials/es/pickup-points.md            | 17 ++++----
 docs/tutorials/es/platform-status-page.md     |  4 +-
 ...ier-from-meeting-certain-zip-code-range.md |  4 +-
 docs/tutorials/es/price-divergence-rule.md    |  4 +-
 docs/tutorials/es/prices-settings.md          |  4 +-
 docs/tutorials/es/promotion-alerts-beta.md    |  4 +-
 ...tion-alerts-how-to-create-an-alert-beta.md |  4 +-
 docs/tutorials/es/promotion-examples.md       |  4 +-
 .../protection-against-transaction-attacks.md |  6 +--
 ...ed-checkouts-with-whatsapp-ai-campaigns.md | 12 ++----
 .../register-tracking-on-the-tax-receipt.md   |  4 +-
 docs/tutorials/es/registering-a-category.md   |  4 +-
 .../es/registering-gateway-affiliations.md    | 14 ++----
 docs/tutorials/es/registering-geolocation.md  |  8 +---
 docs/tutorials/es/regular-promotion.md        | 30 ++++---------
 docs/tutorials/es/releases-module-beta.md     | 20 +++------
 docs/tutorials/es/returning-order-items.md    |  4 +-
 .../es/sales-associates-instore-beta.md       | 12 ++----
 docs/tutorials/es/sales-performance.md        |  4 +-
 docs/tutorials/es/search-behavior.md          |  8 +---
 .../es/search-control-fulltextsearchbox.md    |  4 +-
 docs/tutorials/es/search-navigator-control.md |  4 +-
 docs/tutorials/es/search-parameters.md        |  8 +---
 .../es/searching-for-events-on-audit.md       |  8 +---
 .../es/seller-portal-creating-a-promotion.md  |  4 +-
 ...tal-getting-started-for-the-marketplace.md | 16 ++-----
 docs/tutorials/es/sent-offers-beta.md         |  4 +-
 .../es/sent-offers-buybox-opportunities.md    |  4 +-
 docs/tutorials/es/set-up-mundi-gateway.md     |  4 +-
 ...the-grace-period-for-order-cancellation.md |  4 +-
 .../setting-up-3ds-2-authentication-flow.md   |  4 +-
 .../es/setting-up-abandoned-carts.md          |  4 +-
 .../es/setting-up-merchant-id-in-apple-pay.md |  4 +-
 docs/tutorials/es/setting-up-my-account.md    |  4 +-
 ...rice-and-availability-of-skus-by-region.md |  4 +-
 .../es/setting-up-product-comparison.md       |  4 +-
 .../es/setting-up-the-global-category.md      |  4 +-
 ...ween-a-marketplace-and-a-seller-on-vtex.md | 12 ++----
 docs/tutorials/es/shipping-options-beta.md    |  8 +---
 docs/tutorials/es/shipping-simulation.md      |  4 +-
 docs/tutorials/es/sku-bindings.md             | 16 ++-----
 docs/tutorials/es/sku-registration-fields.md  |  4 +-
 ...-customer-information-automatic-fill-in.md | 21 ++++-----
 docs/tutorials/es/smartcheckout-security.md   |  5 +--
 docs/tutorials/es/store-overview-beta.md      |  4 +-
 docs/tutorials/es/telesales-features.md       |  4 +-
 ...actional-emails-for-subscription-orders.md |  4 +-
 ...eshooting-errors-in-subscription-orders.md |  4 +-
 ...divergence-errors-in-marketplace-orders.md |  4 +-
 docs/tutorials/es/understanding-b2b-orders.md |  7 ++-
 .../visao-geral-da-estrutura-do-catalogo.md   |  4 +-
 docs/tutorials/es/vtex-ad-network-beta.md     |  4 +-
 docs/tutorials/es/vtex-admin-start-here.md    |  4 +-
 docs/tutorials/es/vtex-do-interface.md        |  4 +-
 .../es/vtex-pick-and-pack-fulfillment.md      | 24 +++--------
 .../es/vtex-pick-and-pack-insights.md         |  4 +-
 .../es/vtex-pick-and-pack-last-mile.md        |  4 +-
 .../tutorials/es/vtex-pick-and-pack-mobile.md |  4 +-
 .../tutorials/es/vtex-pick-and-pack-orders.md |  4 +-
 .../es/vtex-pick-and-pack-settings.md         | 12 ++----
 .../es/vtex-pick-and-pack-worksheets.md       |  4 +-
 docs/tutorials/es/vtex-pick-and-pack.md       |  8 +---
 docs/tutorials/es/web-page-performance.md     | 12 ++----
 docs/tutorials/es/what-are-layouts.md         |  8 ++--
 docs/tutorials/es/what-is-a-service.md        |  5 +--
 docs/tutorials/es/what-is-an-attachment.md    |  4 +-
 .../es/what-is-order-configuration.md         |  4 +-
 ...tween-unbinding-and-removing-seller-sku.md |  4 +-
 docs/tutorials/es/what-is-the-sponsor-user.md |  4 +-
 ...-a-product-words-that-may-be-ignored-by.md |  4 +-
 docs/tutorials/es/white-label-seller.md       |  8 +---
 .../es/white-label-sellers-selection.md       | 29 +++++--------
 .../pt/accessing-the-beta-environment.md      |  8 +---
 docs/tutorials/pt/adding-collections-cms.md   |  4 +-
 .../pt/adding-sku-specifications-or-fields.md | 16 ++-----
 ...adding-specifications-or-product-fields.md |  8 +---
 .../advertising-with-vtex-ad-network-beta.md  | 16 ++-----
 docs/tutorials/pt/affiliates-program-app.md   | 20 +++------
 docs/tutorials/pt/all-orders.md               |  4 +-
 docs/tutorials/pt/analytics.md                |  8 +---
 docs/tutorials/pt/application-keys.md         |  4 +-
 docs/tutorials/pt/audit.md                    | 12 ++----
 docs/tutorials/pt/autocomplete.md             | 15 ++-----
 docs/tutorials/pt/b2b-checkout-settings.md    |  4 +-
 .../best-practices-against-virtual-attacks.md |  8 +---
 .../pt/best-practices-application-keys.md     |  4 +-
 ...ices-for-the-success-of-your-vtex-store.md | 24 +++--------
 docs/tutorials/pt/beta-price-configuration.md |  8 +---
 docs/tutorials/pt/buy-one-get-one.md          | 12 ++----
 ...e-worksheet-exported-from-orders-module.md |  4 +-
 docs/tutorials/pt/campaign-promotion.md       |  8 +---
 docs/tutorials/pt/canceling-orders.md         |  4 +-
 docs/tutorials/pt/carrier-working-hours.md    |  4 +-
 ...rking-hours-and-scheduled-delivery-beta.md |  4 +-
 ...-seller-of-an-vtex-sales-app-order-beta.md | 12 ++----
 docs/tutorials/pt/change-seller.md            |  4 +-
 ...e-price-of-an-item-in-the-shopping-cart.md |  4 +-
 .../changing-items-from-a-complete-order.md   |  4 +-
 .../changing-the-total-cost-of-the-order.md   |  4 +-
 ...ount-franchise-account-or-seller-portal.md |  4 +-
 .../pt/collection-highlight-control.md        |  4 +-
 docs/tutorials/pt/collection-types.md         |  4 +-
 docs/tutorials/pt/comprehensive-seller.md     |  4 +-
 ...onfiguring-a-seller-on-vtex-marketplace.md | 16 ++-----
 .../pt/configuring-access-without-www.md      |  4 +-
 docs/tutorials/pt/configuring-banners.md      |  4 +-
 ...port-for-organizations-and-cost-centers.md | 12 ++----
 .../pt/configuring-dns-pointing-to-vtex.md    | 22 ++++------
 ...nfiguring-domains-in-account-management.md |  4 +-
 .../configuring-payment-conditions-for-b2b.md |  4 +-
 .../pt/configuring-price-divergence-rule.md   |  8 +---
 ...configuring-promotions-for-marketplaces.md |  8 +---
 docs/tutorials/pt/configuring-xml.md          |  4 +-
 .../pt/creating-a-more-for-less-promotion.md  | 12 ++----
 .../pt/creating-a-product-collection.md       |  4 +-
 ...ing-a-specification-group-in-a-category.md |  4 +-
 .../tutorials/pt/creating-collections-beta.md | 29 ++++---------
 .../pt/creating-landing-pages-per-binding.md  |  8 +---
 docs/tutorials/pt/creating-landing-pages.md   | 10 +----
 docs/tutorials/pt/creating-pickup-points.md   | 12 ++----
 .../pt/creating-service-for-a-sku.md          |  8 +---
 docs/tutorials/pt/creating-synonyms.md        |  6 +--
 docs/tutorials/pt/data-subject-rights.md      | 16 ++-----
 .../pt/declining-order-cancelation.md         |  8 +---
 docs/tutorials/pt/defining-window-displays.md |  4 +-
 ...liveries-progress-vtex-shipping-network.md | 12 ++----
 ...-vtex-ad-network-ads-in-your-store-beta.md |  4 +-
 ...ic-relevance-in-intelligent-search-beta.md |  8 +---
 .../tutorials/pt/events-available-in-audit.md |  4 +-
 ...mporting-product-and-sku-specifications.md |  8 +---
 ...ling-out-collection-registration-fields.md |  4 +-
 docs/tutorials/pt/filtering-all-orders.md     | 20 +++------
 ...es-with-blocked-terms-to-return-results.md |  4 +-
 ...d-questions-new-orders-module-interface.md |  4 +-
 .../pt/fulfillment-logistics-vtex.md          | 10 ++---
 docs/tutorials/pt/gift-card.md                |  4 +-
 docs/tutorials/pt/google-analytics-faq.md     |  4 +-
 docs/tutorials/pt/google-pay-beta.md          |  4 +-
 .../tutorials/pt/how-does-reservation-work.md | 14 +++---
 .../tutorials/pt/how-does-vtex-search-work.md |  4 +-
 .../pt/how-mercado-livre-integration-works.md |  4 +-
 docs/tutorials/pt/how-my-account-works.md     |  8 +---
 .../pt/how-shipping-calculation-works.md      | 16 ++-----
 docs/tutorials/pt/how-subscriptions-work.md   |  4 +-
 .../pt/how-the-skyhub-integration-works.md    | 16 ++-----
 .../tutorials/pt/how-to-change-order-items.md | 10 ++---
 .../tutorials/pt/how-to-change-orders-beta.md |  4 +-
 .../pt/how-to-configure-subscriptions.md      |  4 +-
 ...ow-to-configure-xml-for-google-shopping.md | 12 ++----
 ...eate-landing-pages-with-customized-urls.md |  4 +-
 .../pt/how-to-delete-a-collection.md          |  4 +-
 ...dentify-an-order-split-from-omnichannel.md |  4 +-
 .../how-to-identify-order-closing-errors.md   |  4 +-
 ...identify-promotions-applied-to-the-cart.md |  4 +-
 ...llection-of-products-in-the-shop-window.md |  4 +-
 .../pt/how-to-integrate-with-facebook.md      |  2 +-
 .../pt/how-to-manage-subscriptions.md         |  4 +-
 .../pt/how-to-manually-invoice-an-order.md    |  4 +-
 ...optimize-searches-with-substitute-words.md |  8 +---
 .../tutorials/pt/how-to-return-order-items.md |  4 +-
 docs/tutorials/pt/how-to-use-rebates.md       |  4 +-
 ...ith-different-layouts-for-the-same-page.md |  4 +-
 .../pt/i-cant-import-the-price-table.md       | 12 ++----
 .../pt/i-cant-receive-emails-from-vtex.md     |  8 +---
 ...-view-the-product-in-the-search-results.md | 15 ++-----
 .../pt/importing-amazon-classic-fba-orders.md |  4 +-
 .../pt/importing-amazon-dba-orders.md         |  4 +-
 ...-and-exporting-an-inventory-spreadsheet.md |  4 +-
 docs/tutorials/pt/integrating-with-loopi.md   | 16 ++-----
 ...e-for-marketplaces-marketplace-non-vtex.md |  8 +---
 docs/tutorials/pt/interaction-details.md      |  4 +-
 docs/tutorials/pt/inventory-update-history.md |  8 ++--
 ...ble-to-use-the-vtex-admin-search-report.md |  4 +-
 docs/tutorials/pt/kabum-integration.md        |  4 +-
 .../lead-time-shipping-time-at-sku-level.md   |  8 +---
 .../tutorials/pt/license-manager-resources.md |  4 +-
 docs/tutorials/pt/loading-dock.md             | 18 ++++----
 .../pt/locations-details-page-beta.md         |  4 +-
 docs/tutorials/pt/locations-module-beta.md    | 16 ++-----
 .../making-product-collections-searchable.md  |  8 +---
 .../pt/managing-delivery-capacity.md          |  4 +-
 docs/tutorials/pt/managing-http-headers.md    |  4 +-
 .../pt/managing-page-and-template-content.md  | 24 +++--------
 .../pt/managing-shipping-policies.md          |  8 +---
 docs/tutorials/pt/managing-stock-items.md     |  2 +-
 ...ies-and-brands-for-the-marketplace-beta.md | 12 ++----
 .../pt/marketplaces-and-integrations.md       |  8 +---
 docs/tutorials/pt/master-data.md              | 20 +++------
 ...ercado-livre-automobilist-compatibility.md | 12 ++----
 docs/tutorials/pt/mercado-livre-faq.md        |  4 +-
 .../pt/my-store-order-was-not-created.md      |  4 +-
 docs/tutorials/pt/offer-details.md            |  4 +-
 docs/tutorials/pt/offer-management.md         |  4 +-
 docs/tutorials/pt/oms-page-structure.md       |  4 +-
 ...pening-tickets-to-vtex-support-finacial.md |  4 +-
 .../tutorials/pt/operational-capacity-beta.md |  8 +---
 .../pt/order-allocation-algorithm-beta.md     |  8 +---
 ...-cancellation-requested-by-the-customer.md |  8 +---
 docs/tutorials/pt/order-details-page.md       | 12 ++----
 docs/tutorials/pt/order-flow-and-status.md    | 16 ++-----
 docs/tutorials/pt/order-report.md             |  4 +-
 .../pt/order-split-and-delivery-split.md      |  4 +-
 docs/tutorials/pt/order-tracking.md           |  6 +--
 docs/tutorials/pt/orders-overview.md          |  4 +-
 .../pt/physical-store-instore-beta.md         |  8 +---
 docs/tutorials/pt/pickup-points.md            | 20 ++++-----
 docs/tutorials/pt/platform-status-page.md     |  4 +-
 docs/tutorials/pt/predefined-roles.md         |  4 +-
 ...ier-from-meeting-certain-zip-code-range.md |  4 +-
 docs/tutorials/pt/price-divergence-rule.md    |  4 +-
 docs/tutorials/pt/prices-settings.md          |  4 +-
 docs/tutorials/pt/products-and-skus-beta.md   |  4 +-
 docs/tutorials/pt/promotion-alerts-beta.md    |  4 +-
 ...tion-alerts-how-to-create-an-alert-beta.md |  4 +-
 docs/tutorials/pt/promotion-examples.md       |  4 +-
 .../protection-against-transaction-attacks.md |  6 +--
 docs/tutorials/pt/ready-to-dispatch.md        | 12 ++----
 ...ed-checkouts-with-whatsapp-ai-campaigns.md |  8 +---
 .../register-tracking-on-the-tax-receipt.md   |  4 +-
 .../pt/registering-gateway-affiliations.md    | 14 ++----
 docs/tutorials/pt/regular-promotion.md        | 28 +++---------
 docs/tutorials/pt/releases-module-beta.md     | 16 ++-----
 docs/tutorials/pt/returning-order-items.md    |  4 +-
 .../pt/sales-associates-instore-beta.md       | 12 ++----
 docs/tutorials/pt/sales-performance.md        |  4 +-
 docs/tutorials/pt/search-behavior.md          | 16 ++-----
 .../pt/search-control-fulltextsearchbox.md    |  4 +-
 docs/tutorials/pt/search-navigator-control.md |  4 +-
 docs/tutorials/pt/search-parameters.md        |  8 +---
 .../pt/searching-for-events-on-audit.md       |  8 +---
 docs/tutorials/pt/seller-monitoring.md        |  2 +-
 .../pt/seller-portal-creating-a-promotion.md  |  4 +-
 ...tal-getting-started-for-the-marketplace.md | 16 ++-----
 docs/tutorials/pt/sent-offers-beta.md         |  4 +-
 .../pt/sent-offers-buybox-opportunities.md    |  4 +-
 docs/tutorials/pt/set-up-mundi-gateway.md     |  4 +-
 ...the-grace-period-for-order-cancellation.md |  4 +-
 .../setting-up-3ds-2-authentication-flow.md   |  4 +-
 .../pt/setting-up-abandoned-carts.md          |  4 +-
 docs/tutorials/pt/setting-up-my-account.md    |  4 +-
 ...rice-and-availability-of-skus-by-region.md |  4 +-
 .../pt/setting-up-product-comparison.md       |  4 +-
 ...ween-a-marketplace-and-a-seller-on-vtex.md | 12 ++----
 docs/tutorials/pt/shipping-options-beta.md    |  8 +---
 docs/tutorials/pt/shipping-simulation.md      |  4 +-
 docs/tutorials/pt/shopee-integration.md       | 12 ++----
 docs/tutorials/pt/sku-bindings.md             | 16 ++-----
 docs/tutorials/pt/sku-registration-fields.md  |  4 +-
 ...-customer-information-automatic-fill-in.md | 21 ++++-----
 docs/tutorials/pt/smartcheckout-security.md   |  5 +--
 docs/tutorials/pt/special-conditions.md       |  4 +-
 docs/tutorials/pt/store-overview-beta.md      |  4 +-
 docs/tutorials/pt/telesales-features.md       |  4 +-
 ...actional-emails-for-subscription-orders.md |  4 +-
 ...eshooting-errors-in-subscription-orders.md |  4 +-
 ...divergence-errors-in-marketplace-orders.md |  4 +-
 docs/tutorials/pt/understanding-b2b-orders.md |  7 ++-
 docs/tutorials/pt/vtex-ad-network-beta.md     |  4 +-
 docs/tutorials/pt/vtex-admin-start-here.md    |  4 +-
 docs/tutorials/pt/vtex-do-interface.md        |  4 +-
 .../pt/vtex-pick-and-pack-fulfillment.md      | 24 +++--------
 .../pt/vtex-pick-and-pack-insights.md         |  4 +-
 .../pt/vtex-pick-and-pack-last-mile.md        |  4 +-
 .../tutorials/pt/vtex-pick-and-pack-mobile.md |  4 +-
 .../tutorials/pt/vtex-pick-and-pack-orders.md |  4 +-
 .../pt/vtex-pick-and-pack-settings.md         | 12 ++----
 .../pt/vtex-pick-and-pack-worksheets.md       |  4 +-
 docs/tutorials/pt/vtex-pick-and-pack.md       |  8 +---
 ...ex-shipping-network-correios-activation.md |  4 +-
 .../pt/vtex-shipping-network-correios-faq.md  | 12 ++----
 docs/tutorials/pt/vtex-tracking-overview.md   |  4 +-
 docs/tutorials/pt/web-page-performance.md     | 16 ++-----
 docs/tutorials/pt/what-is-an-attachment.md    |  4 +-
 .../pt/what-is-order-configuration.md         |  4 +-
 ...tween-unbinding-and-removing-seller-sku.md |  4 +-
 docs/tutorials/pt/what-is-the-sponsor-user.md |  4 +-
 ...-a-product-words-that-may-be-ignored-by.md |  4 +-
 docs/tutorials/pt/white-label-seller.md       |  8 +---
 .../pt/white-label-sellers-selection.md       | 29 +++++--------
 815 files changed, 1617 insertions(+), 4230 deletions(-)

diff --git a/docs/announcements/en/automatic-archiving-inactive-promotions.md b/docs/announcements/en/automatic-archiving-inactive-promotions.md
index d5a84d3ef..ad2241086 100644
--- a/docs/announcements/en/automatic-archiving-inactive-promotions.md
+++ b/docs/announcements/en/automatic-archiving-inactive-promotions.md
@@ -31,9 +31,7 @@ We have implemented the following improvements to the promotion management exper
 
 **Feature optimization:** We've improved the loading time and performance of the promotions list.
 
-<div class = "alert alert-info">
-To view the promotions that have been automatically archived, go to VTEX Admin <b>Promotions > Promotions</b>, or type <b>Promotions</b> in the search bar at the top of the page. In the top right corner, click <i class="fas fa-ellipsis-v" aria-hidden="true"></i>, and then click Applied Promotions.
-</div>
+>ℹ️ To view the promotions that have been automatically archived, go to VTEX Admin **Promotions > Promotions**, or type **Promotions** in the search bar at the top of the page. In the top right corner, click <i class="fas fa-ellipsis-v" aria-hidden="true"></i>, and then click Applied Promotions.
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md b/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md
index fc61fbc2a..ecc0c3c27 100644
--- a/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md
+++ b/docs/announcements/en/checkout-api-now-supports-recaptcha-v3.md
@@ -23,9 +23,7 @@ Besides the native storefront functionality of the VTEX platform, stores impleme
 
 Now, the Checkout API also supports score-based reCAPTCHA reCAPTCHA validation (equivalent to v3), which is suitable for native mobile apps.
 
-<div class = "alert alert-info">
-VTEX is integrated with reCAPTCHA enterprise, which offers two validation approaches: checkbox (equivalent to reCAPTCHA v2) and score-based (equivalent to reCATPCHA v3). See this article on <a href="https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-versions">reCAPTCHA at VTEX Checkout</a> to learn what version you should use depending on your storefront characteristics. You can also learn more each method: <a href="https://developers.google.com/recaptcha/docs/display">reCAPTCHA v2</a> or <a href="https://developers.google.com/recaptcha/docs/v3">reCAPTCHA v3</a> with the documentation provided by Google.
-</div>
+>ℹ️ VTEX is integrated with reCAPTCHA enterprise, which offers two validation approaches: checkbox (equivalent to reCAPTCHA v2) and score-based (equivalent to reCATPCHA v3). See this article on [reCAPTCHA at VTEX Checkout](https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-versions) to learn what version you should use depending on your storefront characteristics. You can also learn more each method: [reCAPTCHA v2](https://developers.google.com/recaptcha/docs/display) or [reCAPTCHA v3](https://developers.google.com/recaptcha/docs/v3) with the documentation provided by Google.
 
 However, the reCAPTCHA checkbox (equivalent to v2) integration option is still available and is the recommended option if you want to implement a [reCAPTCHA integration](https://developers.vtex.com/docs/guides/recaptcha) other than in a native mobile app.
 
diff --git a/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
index c5edb4390..fb79cd544 100644
--- a/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/en/checkout-setting-up-the-cardholder-document-id-field.md
@@ -29,9 +29,7 @@ Previously, when selecting a credit or debit card as a payment method on the Che
 
 Now, if the anti-fraud solution thinks that the **Cardholder Document** field is not necessary for their anti-fraud analysis, the retailer can go to the VTEX Admin and configure whether or not the field should be displayed at Checkout.
 
-<div class = "alert alert-info">
-  The <b>Cardholder Document</b> field must be filled out with information that is specific to each country, such as CPF (Brazil) and Social Security Number (United States). The field name will be displayed differently at Checkout, depending on the country where the purchase is taking place.
-</div>
+>ℹ️ The **Cardholder Document** field must be filled out with information that is specific to each country, such as CPF (Brazil) and Social Security Number (United States). The field name will be displayed differently at Checkout, depending on the country where the purchase is taking place.
 
 ## Why did we make this change?
 
@@ -47,9 +45,7 @@ To check if the anti-fraud solutions configured in your store allow changing the
 
 ![cardholder document field](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/350f0aaab8c88555c89a9ca3f2304f6c/cardholder_document_field.png)
 
-<div class = "alert alert-warning">
-  If the <b>Cardholder document field</b> option is not available on the configuration screen of your anti-fraud solution provider, the <b>Cardholder document</b> field will still be displayed at Checkout in your store, and the customer will be required to fill it out.
-</div>
+>⚠️ If the **Cardholder document field** option is not available on the configuration screen of your anti-fraud solution provider, the **Cardholder document** field will still be displayed at Checkout in your store, and the customer will be required to fill it out.
 
 For more information about how to configure the visibility of this field on your store’s Checkout, see [Cardholder Document Configuration (Help Center)](https://help.vtex.com/en/tutorial/antifraud-provider--4aZtmdpgFikcsQomWyqAOq#cardholder-document-configuration).
 
diff --git a/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
index 8b5e4b965..978c8fb0f 100644
--- a/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/en/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -31,9 +31,7 @@ With Extensions Hub, the entire navigation and app purchasing experience happens
 
 The **App Store** displays prices in US dollars (USD) for stores all over the world, and in Brazilian reais (BRL) for stores in Brazil. Payments for app purchases, subscriptions, and usage are processed automatically, and the corresponding amounts are added to your [VTEX invoice](https://help.vtex.com/en/tutorial/billing-overview--6UxfCl4fw4GmyQwoUuIcQs) in your local currency, eliminating the need for credit card payment. If your operation is located outside Brazil and your invoice is in a currency other than USD, we will convert the USD amount to your local currency.
 
-<div class = "alert alert-info">
-The <a href="http://apps.vtex.com/">App Store website</a> will still exist for viewing apps in a public way, but it will no longer support app purchases. Purchases can only be made through the VTEX Admin.
-</div>
+>ℹ️ The [App Store website](http://apps.vtex.com/) will still exist for viewing apps in a public way, but it will no longer support app purchases. Purchases can only be made through the VTEX Admin.
 
 ### Partners
 
diff --git a/docs/announcements/en/google-shopping-new-option-to-submit-prices.md b/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
index e88241e05..ef25cbe58 100644
--- a/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
+++ b/docs/announcements/en/google-shopping-new-option-to-submit-prices.md
@@ -23,9 +23,7 @@ Previously, merchants could see the **Consider discount for boleto payment in th
 - __Submit base price (for discount prices):__ Only displays products with a [list price](https://help.vtex.com/en/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#list-price).
 - __Apply discount to submitted price:__ Google Shopping will display the VTEX store's products with the associated discount and payment method.
 
-<div class = "alert alert-warning">
-  The <b>Apply discount to submitted price</b> setting is only available for VTEX stores in Brazil.
-</div>
+>⚠️ The **Apply discount to submitted price** setting is only available for VTEX stores in Brazil.
 
 ![envio-de-precos-google-en](https://images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/419f9830910ef18e14deec1eef56f5aa/envio-de-precos-google-en.png)  
 
diff --git a/docs/announcements/en/manage-your-fbaclassic-dba-orders-in-one-place.md b/docs/announcements/en/manage-your-fbaclassic-dba-orders-in-one-place.md
index a94bbba3d..893217c59 100644
--- a/docs/announcements/en/manage-your-fbaclassic-dba-orders-in-one-place.md
+++ b/docs/announcements/en/manage-your-fbaclassic-dba-orders-in-one-place.md
@@ -44,6 +44,4 @@ We have improved the integration with Amazon to allow VTEX sellers to:
 
 Every seller using the [native](https://help.vtex.com/pt/tutorial/integrando-com-marketplace/) VTEX–Amazon [integration](https://help.vtex.com/pt/tutorial/integrando-com-marketplace/) can benefit from this improvement with no additional cost associated with VTEX. To enable the VTEX Admin feature, you have to register and configure one of the options in Amazon [Seller Central](https://sellercentral.amazon.com/). Then follow the instructions on the [FBA Classic or DBA Order Import](https://help.vtex.com/pt/tutorial/importacao-de-pedidos-amazon-fba-dba) page.
 
-<div class = "alert alert-info">
-The DBA order import feature is available for VTEX stores in Brazil.
-</div>
+>ℹ️ The DBA order import feature is available for VTEX stores in Brazil.
diff --git a/docs/announcements/en/marketplace-seller-network.md b/docs/announcements/en/marketplace-seller-network.md
index d19face8f..f82479c75 100644
--- a/docs/announcements/en/marketplace-seller-network.md
+++ b/docs/announcements/en/marketplace-seller-network.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Expand your sales channels and connect with leading marketplaces and sellers through the Marketplace Seller Network.'
 ---
 
-<div class = "alert alert-info">
-  <p>This app is exclusively available for Brazil and will soon be released in other regions. If you want to have early access, just download the app and sign up — we will notify you when new partners join your region.</p>
-</div>
+>ℹ️ This app is exclusively available for Brazil and will soon be released in other regions. If you want to have early access, just download the app and sign up — we will notify you when new partners join your region.
 
 Picture expanding your revenue streams with less investment and way more velocity. One of the main challenges for marketplaces and sellers from our ecosystem is to connect with new partners to expand their offers and reach. With that in mind, we've developed the new Marketplace Seller Network.
 
diff --git a/docs/announcements/en/new-cdn-gives-more-security-and-speed.md b/docs/announcements/en/new-cdn-gives-more-security-and-speed.md
index 10756e236..7fb691aa8 100644
--- a/docs/announcements/en/new-cdn-gives-more-security-and-speed.md
+++ b/docs/announcements/en/new-cdn-gives-more-security-and-speed.md
@@ -26,9 +26,11 @@ Some of the advantages of using a CDN are:
 
 And with HTTP/2 support you have access to a series of other improvements.
 
-<div class = "alert alert-warning">
-<strong>All VTEX stores have to migrate</strong> to the new CDN.<br><br>Check out <a href="http://help.vtex.com/en/tutorial/activating-new-vtex-cdn">in this article </a> how to perform this migration.
-</div>
+>⚠️ **All VTEX stores have to migrate** to the new CDN.
+>
+> 
+>
+> Check out [in this article ](http://help.vtex.com/en/tutorial/activating-new-vtex-cdn) how to perform this migration.
 
 There are no risks or contraindications to joining the new model.
 
diff --git a/docs/announcements/en/new-events-available-in-the-audit-module.md b/docs/announcements/en/new-events-available-in-the-audit-module.md
index 87c4619af..e231a1214 100644
--- a/docs/announcements/en/new-events-available-in-the-audit-module.md
+++ b/docs/announcements/en/new-events-available-in-the-audit-module.md
@@ -228,9 +228,7 @@ VTEX has added the following events to the [list of events available in Audit](h
   </tr>
 </table>
 
-<div class = "alert alert-info">
-See the <a href="https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ">full list of events available in Audit</a>.
-</div>
+>ℹ️ See the [full list of events available in Audit](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## What needs to be done?
 
diff --git a/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md b/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md
index b88a01887..f0fe08774 100644
--- a/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md
+++ b/docs/announcements/en/new-orders-authorization-flow-for-native-connectors.md
@@ -46,9 +46,7 @@ These fields were removed from the connector registers and the following message
 
 > Note: Orders with price divergence between the marketplace and VTEX will only be integrated after [configuring a Price Divergence rule](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
-<div class = "alert alert-info">
-When first integrating with a native connector, it is recommended that the seller create the Price Divergence rule before configuring the integration. Not following the recommendation does not prevent the integration from being completed.
-</div>
+>ℹ️ When first integrating with a native connector, it is recommended that the seller create the Price Divergence rule before configuring the integration. Not following the recommendation does not prevent the integration from being completed.
 
 For the seller that integrates with a native connector for the first time and does not create the Price Divergence rule, orders with price divergence error will be pending in the VTEX Admin, in **MARKETPLACE > Integrations > Orders**. The error message on the interface is as follows:
 
diff --git a/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
index 59df44f9f..945d36c23 100644
--- a/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
+++ b/docs/announcements/en/new-payment-provider-and-anti-fraud-management-interface.md
@@ -31,6 +31,4 @@ The new payment and anti-fraud provider management page is now automatically ava
 
 Learn more about the new interface features in [Register payment and anti-fraud providers](https://help.vtex.com/en/tutorial/registering-gateway-affiliations--tutorials_444).
 
-<div class = "alert alert-warning">
-  The previous version of the affiliations management interface, available at <b>Store Settings > Payment > Settings > Gateway Affiliations</b>, will still be accessible until January 14, 2024.
-</div>
+>⚠️ The previous version of the affiliations management interface, available at **Store Settings > Payment > Settings > Gateway Affiliations**, will still be accessible until January 14, 2024.
diff --git a/docs/announcements/en/partial-invoice-settlements-in-oms.md b/docs/announcements/en/partial-invoice-settlements-in-oms.md
index 37012dfbb..06dca50cc 100644
--- a/docs/announcements/en/partial-invoice-settlements-in-oms.md
+++ b/docs/announcements/en/partial-invoice-settlements-in-oms.md
@@ -19,9 +19,7 @@ When managing orders in OMS, the VTEX order management system, adding the invoic
 
 We improved the OMS so that partial invoices added to orders also trigger partial settlements in the transaction. The total order amount will be updated after adding the invoice, and it corresponds to the amount settled in the VTEX payment gateway. 
 
-<div class = "alert alert-info">
-The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Legacy connectors do not support the functionality.
-</div>
+>ℹ️ The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Legacy connectors do not support the functionality.
 
 ## What has changed?
 
diff --git a/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
index 2f3ff10dd..ee4a0e068 100644
--- a/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/en/requests-with-pagination-will-change-in-the-search-api.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisEN: 'Starting march 31st, the request header resources for pagination will be deprecated.'
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 Starting __march 31st__, the  request header `resources` for pagination will be deprecated. As a result, you will have to use the parameters `_from` and `_to` in the URL in order to make a request. For example:
 
diff --git a/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
index 7e4ea2b83..9d0391e54 100644
--- a/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
+++ b/docs/announcements/en/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -34,9 +34,7 @@ To do this, click the search bar, select the `Orders` option, and search for wha
 
 By clicking a result, you will be redirected to the [Order Details page](https://help.vtex.com/en/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl). The last 10 orders you searched for will be recorded in your recent search history, making access more convenient. The search record is stored at the [user](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) level and not shared among users.
 
-<div class = "alert alert-info">
-To access orders via the VTEX Admin global search, the user <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role</a> must be associated with the <b>View Order</b> resource (OMSViewer key) of the Order Management System (OMS).
-</div>
+>ℹ️ To access orders via the VTEX Admin global search, the user [role](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) must be associated with the **View Order** resource (OMSViewer key) of the Order Management System (OMS).
 
 ## Why did we make this change?
 
diff --git a/docs/announcements/en/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md b/docs/announcements/en/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
index 7cc6d3f01..53a64c088 100644
--- a/docs/announcements/en/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
+++ b/docs/announcements/en/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
@@ -19,9 +19,11 @@ As of __27 April 2020__, the VTEX Checkout UI will receive an important change:
 
 This change aims to comply with data protection laws, keeping your store in line with recent changes in legislation.
 
-<div class = "alert alert-warning">
-<strong>Attention:</strong> if your store currently performs any customization of the VTEX Checkout that changes the behavior of the newsletter flag (for example, clearing the flag via script), the change we are announcing may affect the expected behavior. In cases where currently the customization via script unchecks the flag, for example, it may be that now it will start doing just the opposite, i.e., checking the flag.<br><br>So, if your store has implemented any customization that changes the standard behavior of the newsletter flag, it's important to ensure that your development team is aware of the change and makes adjustments if necessary.
-</div>
+>⚠️ **Attention:** if your store currently performs any customization of the VTEX Checkout that changes the behavior of the newsletter flag (for example, clearing the flag via script), the change we are announcing may affect the expected behavior. In cases where currently the customization via script unchecks the flag, for example, it may be that now it will start doing just the opposite, i.e., checking the flag.
+>
+> 
+>
+> So, if your store has implemented any customization that changes the standard behavior of the newsletter flag, it's important to ensure that your development team is aware of the change and makes adjustments if necessary.
 
 - __Date and time of change__: April 27, 2020, at 11am (Brazil Time).
 - __What you need to do__: if your store customizes the Checkout newsletter flag (and only in this case), your development team should check if the change will impact the flag's behavior.
diff --git a/docs/announcements/en/vtex-insurance-discontinuity.md b/docs/announcements/en/vtex-insurance-discontinuity.md
index bec16f24d..10341b0df 100644
--- a/docs/announcements/en/vtex-insurance-discontinuity.md
+++ b/docs/announcements/en/vtex-insurance-discontinuity.md
@@ -27,5 +27,5 @@ There will be no contractual or commercial changes since the contract was betwee
 
 No action is required, as the update will be applied automatically to all VTEX stores. Any technical questions or issues related to the product should be addressed directly with [Assurant](https://www.assurant.com.br/).
 
-<div class = "alert alert-warning">VTEX will not provide technical support to customers.</div>
+>⚠️ VTEX will not provide technical support to customers.
 
diff --git a/docs/announcements/es/automatic-archiving-inactive-promotions.md b/docs/announcements/es/automatic-archiving-inactive-promotions.md
index f27b3f189..fdb8e44ba 100644
--- a/docs/announcements/es/automatic-archiving-inactive-promotions.md
+++ b/docs/announcements/es/automatic-archiving-inactive-promotions.md
@@ -31,9 +31,7 @@ Aplicamos las siguientes optimizaciones en la experiencia de gestión de promoci
 
 **Optimización de recursos:** hemos optimizado el tiempo de carga y el desempeño de la lista de promociones.
 
-<div class = "alert alert-info">
-Para ver a las promociones que se archivaron automáticamente, accede al Admin VTEX <b>Promociones > Promociones</b>, o <b>ingresa Promociones</b> en la barra de búsqueda de la parte superior de la página. En la esquina superior derecha haz clic en <i class="fas fa-ellipsis-v" aria-hidden="true"></i>, y después en Promociones aplicadas.
-</div>
+>ℹ️ Para ver a las promociones que se archivaron automáticamente, accede al Admin VTEX **Promociones > Promociones**, o **ingresa Promociones** en la barra de búsqueda de la parte superior de la página. En la esquina superior derecha haz clic en <i class="fas fa-ellipsis-v" aria-hidden="true"></i>, y después en Promociones aplicadas.
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
index 8f133a2a7..16a9b209a 100644
--- a/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/es/checkout-setting-up-the-cardholder-document-id-field.md
@@ -29,9 +29,7 @@ Antes, al seleccionar la tarjeta de crédito o débito como medio de pago en la
 
 Ahora, si el proveedor antifraude entiende que el campo **Identificación del titular de la tarjeta** no es obligatorio para su análisis antifraude, el administrador de la tienda podrá configurar en el Admin VTEX si el campo debe mostrarse o no en el Checkout.
 
-<div class = "alert alert-info">
-  El campo <b>Identificación del titular de la tarjeta</b> debe rellenarse con el dato específico de cada país, como CPF (Brasil) y número de seguro social (Estados Unidos). El nombre de campo se mostrará de diferentes maneras en el Checkout, según el país donde se realice la compra.
-</div>
+>ℹ️ El campo **Identificación del titular de la tarjeta** debe rellenarse con el dato específico de cada país, como CPF (Brasil) y número de seguro social (Estados Unidos). El nombre de campo se mostrará de diferentes maneras en el Checkout, según el país donde se realice la compra.
 
 ## ¿Por qué realizamos este cambio?
 
@@ -47,9 +45,7 @@ Para comprobar si los proveedores antifraude configurados en tu tienda permiten
 
 ![campo de documento del titular de la tarjeta](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/d826f02dac101b0385119f52685fb846/campo_de_documento_del_titular_de_la_tarjeta.png)
 
-<div class = "alert alert-warning">
-  Si la opción <b>Campo de documento del titular de la tarjeta</b> no está disponible en la pantalla de configuración de tu proveedor antifraude, el campo <b>Identificación del titular de la tarjeta</b> seguirá apareciendo en la pantalla del Checkout de la tienda y será obligatorio que el cliente lo rellene.
-</div>
+>⚠️ Si la opción **Campo de documento del titular de la tarjeta** no está disponible en la pantalla de configuración de tu proveedor antifraude, el campo **Identificación del titular de la tarjeta** seguirá apareciendo en la pantalla del Checkout de la tienda y será obligatorio que el cliente lo rellene.
 
 Para más información sobre cómo configurar la visualización del campo en el Checkout de tu tienda, accede a [Campo de documento del titular de la tarjeta](https://help.vtex.com/es/tutorial/antifraud-provider--4aZtmdpgFikcsQomWyqAOq#configuracion-del-documento-del-titular-de-la-tarjeta).
 
diff --git a/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
index 43cda1f7c..66a086a3d 100644
--- a/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/es/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -31,9 +31,7 @@ Con el Hub de extensiones, toda la experiencia de navegación y compra de aplica
 
 Los precios en la **App Store** se mostrarán en dólares estadounidenses (USD), a menos que tu tienda esté en Brasil, en cuyo caso los precios serán en reales (BRL). Los pagos por compra, suscripción y uso de la aplicación se procesan automáticamente y los importes correspondientes se añaden a tu [factura VTEX](https://help.vtex.com/es/tutorial/vision-general-facturacion--6UxfCl4fw4GmyQwoUuIcQs) en tu moneda local, eliminando la necesidad de pago con tarjeta de crédito. Si tu operación no está ubicada en Brasil y tu factura está en una moneda distinta de USD, convertiremos el importe en USD a tu moneda local.
 
-<div class = "alert alert-info">
-El <a href="http://apps.vtex.com/">sitio web de la App Store</a> seguirá existiendo, pero solo para la visualización de aplicaciones de forma pública. Ya no será posible comprar aplicaciones a través del sitio web, dado que las compras solo pueden realizarse en el Admin VTEX.
-</div>
+>ℹ️ El [sitio web de la App Store](http://apps.vtex.com/) seguirá existiendo, pero solo para la visualización de aplicaciones de forma pública. Ya no será posible comprar aplicaciones a través del sitio web, dado que las compras solo pueden realizarse en el Admin VTEX.
 
 ### Partners
 
diff --git a/docs/announcements/es/google-shopping-new-option-to-submit-prices.md b/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
index 162c3a8c3..2ab5927e0 100644
--- a/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
+++ b/docs/announcements/es/google-shopping-new-option-to-submit-prices.md
@@ -23,9 +23,7 @@ Antes, el registro de la [integración con Google Shopping](https://help.vtex.co
 - __Enviar precio base (para precios con descuento):__ solo muestra los productos registrados con [precio de lista](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista).  
 - __Aplicar descuento al precio enviado:__ muestra los productos de la tienda VTEX en Google Shopping con el descuento y medio de pago registrados.  
 
-<div class = "alert alert-warning">
-  La configuración <b>Aplicar descuento al precio enviado</b> solo está disponible para tiendas VTEX en Brasil.
-</div>
+>⚠️ La configuración **Aplicar descuento al precio enviado** solo está disponible para tiendas VTEX en Brasil.
 
 ![envio-de-precos-google-es](https://images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/afc4f30ca92f564cb47326e9956b21df/envio-de-precos-google-es.png)
 
diff --git a/docs/announcements/es/integration-methods-with-the-catalog-through-web-service-will-be.md b/docs/announcements/es/integration-methods-with-the-catalog-through-web-service-will-be.md
index 4cf8e0744..3cd242cc2 100644
--- a/docs/announcements/es/integration-methods-with-the-catalog-through-web-service-will-be.md
+++ b/docs/announcements/es/integration-methods-with-the-catalog-through-web-service-will-be.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'En 29/10, vamos a descontinuar algunos métodos de Web Service para integración con el catálogo.'
 ---
 
-<div class = "alert alert-info">
-El cambio descrito aquí sólo tiene impacto en su operación si su tienda utiliza integración por <b>Web Service</b> y esa integración utiliza alguno de los métodos listados abajo. De lo contrario, <b>no</b> es necesario tomar ninguna acción.
-</div>
+>ℹ️ El cambio descrito aquí sólo tiene impacto en su operación si su tienda utiliza integración por **Web Service** y esa integración utiliza alguno de los métodos listados abajo. De lo contrario, **no** es necesario tomar ninguna acción.
 
 A partir del día __29 de octubre__, VTEX va a descontinuar los siguientes métodos de integración por Web Service, con el objetivo de mejorar el desempeño de la plataforma.
 
diff --git a/docs/announcements/es/manage-your-fbaclassic-dba-orders-in-one-place.md b/docs/announcements/es/manage-your-fbaclassic-dba-orders-in-one-place.md
index 3ea0dfd49..1ec244f19 100644
--- a/docs/announcements/es/manage-your-fbaclassic-dba-orders-in-one-place.md
+++ b/docs/announcements/es/manage-your-fbaclassic-dba-orders-in-one-place.md
@@ -44,6 +44,4 @@ Mejoramos la integración con Amazon para que los sellers VTEX puedan:
 
 Cualquier seller que utilice la [integración nativa](https://help.vtex.com/es/tutorial/integrando-com-marketplace/) VTEX-Amazon podrá beneficiarse de esta mejora sin costo adicional asociado a VTEX. Para activar la funcionalidad en el Admin VTEX, debes registrar y configurar una de las opciones en Amazon [Seller Central](https://sellercentral.amazon.com/) y seguir las instrucciones de la página de [Importación de pedidos de FBA Classic y DBA](https://help.vtex.com/pt/tutorial/importacao-de-pedidos-amazon-fba-dba).
 
-<div class = "alert alert-info">
-La funcionalidad Importación de pedidos de DBA está disponible para las tiendas VTEX en Brasil.
-</div>
+>ℹ️ La funcionalidad Importación de pedidos de DBA está disponible para las tiendas VTEX en Brasil.
diff --git a/docs/announcements/es/marketplace-seller-network.md b/docs/announcements/es/marketplace-seller-network.md
index 1ce40b029..752e29d90 100644
--- a/docs/announcements/es/marketplace-seller-network.md
+++ b/docs/announcements/es/marketplace-seller-network.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Expanda sus canales de ventas y conéctese a marketplaces líderes del mercado con Marketplace Seller Network.'
 ---
 
-<div class = "alert alert-info">
-  <p>Esta aplicación está disponible exclusivamente para Brasil y pronto se lanzará en otras regiones. Si desea ser uno de los primeros en tener acceso, solo tiene que descargar la aplicación e inscribirse, le avisaremos cuando se incorporen nuevos partners en su región.  </p>
-</div>
+>ℹ️ Esta aplicación está disponible exclusivamente para Brasil y pronto se lanzará en otras regiones. Si desea ser uno de los primeros en tener acceso, solo tiene que descargar la aplicación e inscribirse, le avisaremos cuando se incorporen nuevos partners en su región.
 
 Imagine expandir sus fuentes de ingresos con menos inversión y más velocidad. Para los marketplaces y sellers de nuestro ecosistema, uno de los mayores retos es conectarse con nuevos partners para ampliar sus ofertas y su alcance. Por eso, desarrollamos la aplicación Marketplace Seller Network.
 
diff --git a/docs/announcements/es/new-cdn-gives-more-security-and-speed.md b/docs/announcements/es/new-cdn-gives-more-security-and-speed.md
index 1da027ea2..ced0035aa 100644
--- a/docs/announcements/es/new-cdn-gives-more-security-and-speed.md
+++ b/docs/announcements/es/new-cdn-gives-more-security-and-speed.md
@@ -26,9 +26,11 @@ Algunas de las ventajas de usar una CDN son:
 
 Y con el soporte de HTTP/2 usted tiene acceso a una serie de otras mejoras.
 
-<div class = "alert alert-warning">
-<strong>Todas las tiendas VTEX deben migrar</strong> a la nueva CDN.<br><br>Ver <a href="http://help.vtex.com/es/tutorial/activar-nueva-cdn-de-vtex">en este artículo</a> cómo hacer esta migración.
-</div>
+>⚠️ **Todas las tiendas VTEX deben migrar** a la nueva CDN.
+>
+> 
+>
+> Ver [en este artículo](http://help.vtex.com/es/tutorial/activar-nueva-cdn-de-vtex) cómo hacer esta migración.
 
 No hay riesgos o contraindicaciones para adherirse al nuevo modelo.
 
diff --git a/docs/announcements/es/new-events-available-in-the-audit-module.md b/docs/announcements/es/new-events-available-in-the-audit-module.md
index d529f8b64..6a4f05058 100644
--- a/docs/announcements/es/new-events-available-in-the-audit-module.md
+++ b/docs/announcements/es/new-events-available-in-the-audit-module.md
@@ -228,9 +228,7 @@ VTEX agregó los siguientes eventos a la [lista de eventos disponibles en Audit]
   </tr>
 </table>
 
-<div class = "alert alert-info">
-Consulta la <a href="https://help.vtex.com/es/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista completa de eventos disponibles en Audit</a>.
-</div>
+>ℹ️ Consulta la [lista completa de eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## ¿Qué se necesita hacer?
 
diff --git a/docs/announcements/es/new-mandatory-attribute-for-products-sent-to-mercado-libre.md b/docs/announcements/es/new-mandatory-attribute-for-products-sent-to-mercado-libre.md
index 7d9bf4daa..bc14ebe41 100644
--- a/docs/announcements/es/new-mandatory-attribute-for-products-sent-to-mercado-libre.md
+++ b/docs/announcements/es/new-mandatory-attribute-for-products-sent-to-mercado-libre.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'Los productos de la categoría Celulares y Smartphones en MeLi tendrán un nuevo atributo obligatorio'
 ---
 
-<div class = "alert alert-info">
-Atributo necesario únicamente para los clientes integrados en Brasil.
-</div>
+>ℹ️ Atributo necesario únicamente para los clientes integrados en Brasil.
 
 Cuando una tienda VTEX integrada con Mercado Libre quiere [enviar sus productos](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/5XNeiye4rS4oao2MueSUeA) al catálogo del marketplace, debe mapear las categorías y atributos de estos productos.
 
diff --git a/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md b/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md
index ae7096a56..f85d70a48 100644
--- a/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md
+++ b/docs/announcements/es/new-orders-authorization-flow-for-native-connectors.md
@@ -46,9 +46,7 @@ Estos campos se eliminaron de los registros del conector y se agregó el siguien
 
 > Atención: los pedidos con divergencia de precio entre el marketplace y VTEX solo se integrarán mediante la [configuración de una regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
-<div class = "alert alert-info">
-Al realizar la primera integración con un conector nativo, es recomendable que el seller cree la regla de Divergencia de precios antes de configurar la integración. No seguir la recomendación no impide que se complete la integración.
-</div>
+>ℹ️ Al realizar la primera integración con un conector nativo, es recomendable que el seller cree la regla de Divergencia de precios antes de configurar la integración. No seguir la recomendación no impide que se complete la integración.
 
 Para el seller que se integra con un conector nativo por primera vez y no crea la regla de Divergencia de precios, los pedidos con error de divergencia de valores estarán pendientes en el Admin VTEX, en **MARKETPLACE > Integraciones > Pedidos**. El mensaje de error en la interfaz es el siguiente:
 
diff --git a/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
index 1ad282c60..1014bcb69 100644
--- a/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
+++ b/docs/announcements/es/new-payment-provider-and-anti-fraud-management-interface.md
@@ -31,6 +31,4 @@ La nueva página de gestión de proveedores de pago y antifraude ya está dispon
 
 Para más información sobre las funcionalidades de la nueva interfaz, accede a [Registrar proveedores de pagos y antifraude](https://help.vtex.com/es/tutorial/afiliaciones-de-gateway--tutorials_444).
 
-<div class = "alert alert-warning">
-  La versión anterior de la interfaz de administración de afiliaciones, disponible en <b>Configuración de la tienda > Pago > Configuración > Afiliaciones de Gateway</b>, seguirá siendo accesible hasta el 14 de enero de 2024.
-</div>
+>⚠️ La versión anterior de la interfaz de administración de afiliaciones, disponible en **Configuración de la tienda > Pago > Configuración > Afiliaciones de Gateway**, seguirá siendo accesible hasta el 14 de enero de 2024.
diff --git a/docs/announcements/es/partial-invoice-settlements-in-oms.md b/docs/announcements/es/partial-invoice-settlements-in-oms.md
index 6dabfc8af..fd4b68be9 100644
--- a/docs/announcements/es/partial-invoice-settlements-in-oms.md
+++ b/docs/announcements/es/partial-invoice-settlements-in-oms.md
@@ -19,9 +19,7 @@ Si gestionas pedidos en el OMS, el sistema de gestión de pedidos de VTEX, debes
 
 Desarrollamos una mejora en el OMS que hará que las facturas parciales emitidas en los pedidos también disparen liquidaciones parciales en la transacción. El valor total del pedido se actualizará luego de emitir la factura y se corresponderá con la información obtenida a través del _gateway_ de pagos de VTEX. 
 
-<div class = "alert alert-info">
-La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el <a href="https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Los conectores legados no admiten la funcionalidad.
-</div>
+>ℹ️ La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Los conectores legados no admiten la funcionalidad.
 
 ## ¿Qué cambió?
 
diff --git a/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
index e93b0321f..9461c90e0 100644
--- a/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/es/requests-with-pagination-will-change-in-the-search-api.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisES: 'A partir de 31/02/18, requests con paginación no se podrán hacer con el header resources del request.'
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 A partir de __31 de marzo__, los requests con paginación en la API de búsqueda ya no se podrán hacer con el header `resources` del request. Él se interrumpirá y, para solicitar una respuesta de la API, usted deberá utilizar los parámetros `_from` y `_to` en la URL, como en el ejemplo:
 
diff --git a/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
index 6bb117c3a..797ad287c 100644
--- a/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
+++ b/docs/announcements/es/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -34,9 +34,7 @@ Para buscar, haz clic en la barra de búsqueda, selecciona la opción `Pedidos`
 
 Al hacer clic en un resultado, se te redirigirá a la [página de detalles](https://help.vtex.com/es/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) del pedido. Además, los últimos 10 pedidos buscados se registran como historial de búsquedas recientes para mayor facilidad de acceso. El registro de búsqueda se almacena a nivel de [usuario](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) y no se comparte entre diferentes usuarios.
 
-<div class = "alert alert-info">
-Para acceder a los pedidos a través de la búsqueda global del Admin VTEX, el <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol</a> del usuario debe estar asociado al recurso <b>View order</b> (clave OMSViewier) del <i>Order Management System</i> (OMS).
-</div>
+>ℹ️ Para acceder a los pedidos a través de la búsqueda global del Admin VTEX, el [rol](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) del usuario debe estar asociado al recurso **View order** (clave OMSViewier) del <i>Order Management System</i> (OMS).
 
 ## ¿Por qué realizamos este cambio?
 
diff --git a/docs/announcements/es/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md b/docs/announcements/es/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
index 40122c36b..4d33e6bd5 100644
--- a/docs/announcements/es/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
+++ b/docs/announcements/es/the-newsletter-opt-in-flag-in-the-checkout-will-now-be-unchecked-by-default.md
@@ -19,9 +19,7 @@ A partir del __27 de abril de 2020__, la interfaz de usuario de VTEX Checkout re
 
 Este cambio tiene como objetivo cumplir con las leyes de protección de datos, manteniendo su tienda en línea con los cambios recientes en la legislación sobre ese tema.
 
-<div class = "alert alert-warning">
-<strong>Atención:</strong> si su tienda actualmente realiza alguna personalización del Checkout VTEX que cambia el comportamiento del flag del newsletter (por ejemplo, deseleccionando el flag a través de un script), el cambio que estamos anunciando puede afectar el comportamiento esperado. En los casos en que actualmente la personalización a través del script deselecciona el flag, por ejemplo, puede que ahora comience a hacer exactamente lo contrario, seleccionando el flag. Por eso, si su tienda ha implementado alguna personalización que cambie el comportamiento estándar del flag de newsletter, es importante asegurarse de que su equipo de desarrollo esté al tanto del cambio y realice ajustes si es necesario.
-</div>
+>⚠️ **Atención:** si su tienda actualmente realiza alguna personalización del Checkout VTEX que cambia el comportamiento del flag del newsletter (por ejemplo, deseleccionando el flag a través de un script), el cambio que estamos anunciando puede afectar el comportamiento esperado. En los casos en que actualmente la personalización a través del script deselecciona el flag, por ejemplo, puede que ahora comience a hacer exactamente lo contrario, seleccionando el flag. Por eso, si su tienda ha implementado alguna personalización que cambie el comportamiento estándar del flag de newsletter, es importante asegurarse de que su equipo de desarrollo esté al tanto del cambio y realice ajustes si es necesario.
 
 - __Fecha y hora del cambio__: 27 de abril de 2020, a las 11 a.m. (hora de Brasil).
 - __Qué necesita hacer__: si su tienda personaliza el flag de newsletter en el Checkout (y solo en este caso), su equipo de desarrollo debe verificar si el cambio afectará el comportamiento del flag.
diff --git a/docs/announcements/es/vtex-insurance-discontinuity.md b/docs/announcements/es/vtex-insurance-discontinuity.md
index 07e03d2eb..dd6af80b5 100644
--- a/docs/announcements/es/vtex-insurance-discontinuity.md
+++ b/docs/announcements/es/vtex-insurance-discontinuity.md
@@ -25,5 +25,5 @@ No habrá cambios contractuales o comerciales, ya que el contrato era entre los
 # ¿Qué se necesita hacer?
 No se requiere ninguna acción. La actualización se aplicará automáticamente a todas las tiendas VTEX. Cualquier duda técnica u otros problemas relacionados al producto se deben dirigir directamente a [Assurant](https://www.assurant.com.br/).
 
-<div class = "alert alert-warning"> VTEX no prestará soporte técnico a los clientes.</div>
+>⚠️ VTEX no prestará soporte técnico a los clientes.
 
diff --git a/docs/announcements/es/vtex-login-now-needs-2-factor-authentication.md b/docs/announcements/es/vtex-login-now-needs-2-factor-authentication.md
index 5aefd1966..33d7c1727 100644
--- a/docs/announcements/es/vtex-login-now-needs-2-factor-authentication.md
+++ b/docs/announcements/es/vtex-login-now-needs-2-factor-authentication.md
@@ -17,9 +17,7 @@ announcementSynopsisES: 'A partir del 16/11, la autenticación de 2 factores se
 
 A partir del 16 de noviembre, a las 14h (horario de Brasil), la autenticación de 2 factores (2FA) se vuelve __obrigatoria para todos los e-mails__ en el Admin de VTEX. Si usted utiliza email y contraseña para iniciar sesión, habilite el 2FA antes de esa fecha.
 
-<div class= "alert alert-info">
-Vea el artículo sobre <a href="http://help.vtex.com/es/tutorial/habilitar-login-por-autenticacion-de-2-factores"> como habilitar el 2FA </a>.
-</div>
+>ℹ️ Vea el artículo sobre [ como habilitar el 2FA ](http://help.vtex.com/es/tutorial/habilitar-login-por-autenticacion-de-2-factores).
 
 2FA es un método de autenticación que aumenta mucho la seguridad de su tienda. Porque en el momento del login, además de pedir email y contraseña, el sistema requiere una clave de acceso generada por aplicación o SMS.
 
diff --git a/docs/announcements/pt/automatic-archiving-inactive-promotions.md b/docs/announcements/pt/automatic-archiving-inactive-promotions.md
index a61d106f7..f0da1d5d6 100644
--- a/docs/announcements/pt/automatic-archiving-inactive-promotions.md
+++ b/docs/announcements/pt/automatic-archiving-inactive-promotions.md
@@ -31,9 +31,7 @@ Aplicamos as seguintes melhorias na experiência de gerenciamento de promoções
 
 **Otimização de recursos:** melhoria no carregamento e performance da lista de promoções.
 
-<div class = "alert alert-info">
-Para visualizar as promoções que foram arquivadas automaticamente, você pode acessar no Admin VTEX <b>Promoções > Promoções</b>, ou digite <b>Promoções</b> na barra de busca no topo da página, e no canto superior direito clique nos <i class="fas fa-ellipsis-v" aria-hidden="true"></i> e em Promoções aplicadas.
-</div>
+>ℹ️ Para visualizar as promoções que foram arquivadas automaticamente, você pode acessar no Admin VTEX **Promoções > Promoções**, ou digite **Promoções** na barra de busca no topo da página, e no canto superior direito clique nos <i class="fas fa-ellipsis-v" aria-hidden="true"></i> e em Promoções aplicadas.
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/boost-your-marketplace-sales.md b/docs/announcements/pt/boost-your-marketplace-sales.md
index 59a418c07..d4c1c1952 100644
--- a/docs/announcements/pt/boost-your-marketplace-sales.md
+++ b/docs/announcements/pt/boost-your-marketplace-sales.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'A nova funcionalidade facilita a identificação de pedidos com divergência no preço e permite sua loja recuperar vendas.'
 ---
 
-<div class ="alert alert-warning">
-Desde que este anúncio foi publicado, deixou de ser necessário entrar em contato com o suporte da VTEX para integrar pedidos com divergência de preço. Você <strong>não</strong> precisa mais abrir um ticket para usar essa feature. Basta, em vez disso, acessar a feature pelo Admin, em <b>Gerenciamento de pedidos</b> > <b>Autorização de pedidos</b>.
-</div>
+>⚠️ Desde que este anúncio foi publicado, deixou de ser necessário entrar em contato com o suporte da VTEX para integrar pedidos com divergência de preço. Você **não** precisa mais abrir um ticket para usar essa feature. Basta, em vez disso, acessar a feature pelo Admin, em **Gerenciamento de pedidos** > **Autorização de pedidos**.
 
 Agora, você tem a opção de integrar aqueles pedidos que vêm do marketplace com alguma divergência no preço. Para isso, introduzimos o novo status `waiting-for-manual-authorization` no fluxo de pedido que permite a integração manual nesses casos. 
 
diff --git a/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md b/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
index 9fa08e9c1..935d702d7 100644
--- a/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
+++ b/docs/announcements/pt/checkout-setting-up-the-cardholder-document-id-field.md
@@ -29,9 +29,7 @@ Anteriormente, ao selecionar o cartão de crédito ou débito como métodos de p
 
 A partir de agora, caso o provedor de antifraude entenda que o campo **Identificação do titular do cartão** não seja obrigatório para a sua análise antifraude, o lojista poderá configurar no Admin VTEX se o campo deverá ser exibido ou não no Checkout.
 
-<div class = "alert alert-info">
-  O campo <b>Identificação do titular do cartão</b> deve ser preenchido com um dado específico para cada país, como CPF (Brasil) e Social Security Number (Estados Unidos). O nome do campo será exibido de formas diferentes no Checkout, de acordo com o país onde a compra está sendo realizada.
-</div>
+>ℹ️ O campo **Identificação do titular do cartão** deve ser preenchido com um dado específico para cada país, como CPF (Brasil) e Social Security Number (Estados Unidos). O nome do campo será exibido de formas diferentes no Checkout, de acordo com o país onde a compra está sendo realizada.
 
 ## Por que realizamos esta mudança?
 
@@ -47,9 +45,7 @@ Para verificar se os provedores de antifraude configurados em sua loja permitem
 
 ![campo de documento do titular do cartão](https://images.ctfassets.net/alneenqid6w5/23Hyo1jo4hkC3nXPmOa7NW/5bbfb8cbfce605b09d61e10a8ff06e3b/campo_de_documento_do_titular_do_cart__o.png)
 
-<div class = "alert alert-warning">
-  Caso a opção <b>Campo de documento do titular do cartão</b> não esteja disponível na tela de configuração do seu provedor de antifraude, o campo <b>Identificação do titular do cartão</b> continuará sendo exibido na tela do Checkout da loja e deverá ser obrigatoriamente preenchido pelo cliente.
-</div>
+>⚠️ Caso a opção **Campo de documento do titular do cartão** não esteja disponível na tela de configuração do seu provedor de antifraude, o campo **Identificação do titular do cartão** continuará sendo exibido na tela do Checkout da loja e deverá ser obrigatoriamente preenchido pelo cliente.
 
 Para maiores informações sobre como configurar a exibição do campo no Checkout de sua loja, acesse [Campo de documento do titular do cartão](https://help.vtex.com/pt/tutorial/antifraud-provider--4aZtmdpgFikcsQomWyqAOq#campo-de-documento-do-titular-do-cartao).
 
diff --git a/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md b/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
index 4cd2080e8..0bdda1cea 100644
--- a/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
+++ b/docs/announcements/pt/extension-hub-expand-your-operation-through-vtex-admin.md
@@ -31,9 +31,7 @@ Com o Hub de Extensões, toda a experiência de navegação e compra de apps aco
 
 Os preços na **App Store** aparecem em reais (BRL) para lojas no Brasil e em dólares (USD) para lojas em outros países. Os pagamentos pela aquisição, assinatura e utilização de apps são processados automaticamente e os valores correspondentes são adicionados à sua [fatura VTEX](https://help.vtex.com/pt/tutorial/visao-geral-faturas--6UxfCl4fw4GmyQwoUuIcQs) na sua moeda local, eliminando a necessidade de pagamento por cartão de crédito. Caso a sua operação não esteja localizada no Brasil e a sua fatura esteja em uma moeda diferente de USD, faremos a conversão do valor em USD para a sua moeda local.
 
-<div class = "alert alert-info">
-O <a href="http://apps.vtex.com/">site da App Store</a> continuará existindo apenas para visualização de apps de forma pública. Não será mais possível fazer a compra de apps pelo site. As compras podem ser feitas apenas no Admin VTEX.
-</div>
+>ℹ️ O [site da App Store](http://apps.vtex.com/) continuará existindo apenas para visualização de apps de forma pública. Não será mais possível fazer a compra de apps pelo site. As compras podem ser feitas apenas no Admin VTEX.
 
 ### Parceiros
 
diff --git a/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md b/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
index 367562790..9164f3962 100644
--- a/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
+++ b/docs/announcements/pt/google-shopping-new-option-to-submit-prices.md
@@ -23,9 +23,7 @@ Anteriormente, no cadastro da [integração com o Google Shopping](https://help.
 - **Enviar preço-base (para preços com desconto):** apresentará somente os produtos cadastrados com [preço lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista).  
 - **Aplicar desconto no preço enviado:** apresentará no Google Shopping os produtos da loja VTEX com o desconto e o meio de pagamento cadastrados.  
 
-<div class = "alert alert-warning">
-  A configuração <b>Aplicar desconto no preço enviado</b> está disponível somente para lojas VTEX Brasil.
-</div>
+>⚠️ A configuração **Aplicar desconto no preço enviado** está disponível somente para lojas VTEX Brasil.
 
 ![envio-de-precos-google-pt](https://images.ctfassets.net/alneenqid6w5/5ZZihnxaawRM55WkmZ8YJA/309246aab10954d984d851b58442a4ef/envio-de-precos-google-pt.png)
 
diff --git a/docs/announcements/pt/manage-your-fbaclassic-dba-orders-in-one-place.md b/docs/announcements/pt/manage-your-fbaclassic-dba-orders-in-one-place.md
index a741ac11f..59dd3e9d0 100644
--- a/docs/announcements/pt/manage-your-fbaclassic-dba-orders-in-one-place.md
+++ b/docs/announcements/pt/manage-your-fbaclassic-dba-orders-in-one-place.md
@@ -43,6 +43,4 @@ Aprimoramos a integração com a Amazon para permitir que sellers VTEX
 
 Todo seller que utilize a [integração nativa](https://help.vtex.com/pt/tutorial/integrando-com-marketplace/) VTEX - Amazon poderá se beneficiar dessa melhoria sem custo adicional atrelado à VTEX. Para ativar a funcionalidade no Admin VTEX, é necessário registrar e configurar uma das opções no [Seller Central](https://sellercentral.amazon.com/) da Amazon e seguir as instruções na página de [Importação dos pedidos do FBA Classic ou DBA](https://help.vtex.com/pt/tutorial/importacao-de-pedidos-amazon-fba-dba).
 
-<div class = "alert alert-info">
-A funcionalidade Importação dos pedidos do DBA está disponível para lojas VTEX no Brasil.
-</div>
+>ℹ️ A funcionalidade Importação dos pedidos do DBA está disponível para lojas VTEX no Brasil.
diff --git a/docs/announcements/pt/new-events-available-in-the-audit-module.md b/docs/announcements/pt/new-events-available-in-the-audit-module.md
index 73f76a041..2ace8fc15 100644
--- a/docs/announcements/pt/new-events-available-in-the-audit-module.md
+++ b/docs/announcements/pt/new-events-available-in-the-audit-module.md
@@ -228,9 +228,7 @@ A VTEX adicionou os seguintes eventos à [lista de eventos registrados pelo Audi
   </tr>
 </table>
 
-<div class = "alert alert-info">
-Confira a <a href="https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista completa de eventos disponíveis no Audit</a>.
-</div>
+>ℹ️ Confira a [lista completa de eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/eventos-disponiveis-no-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## O que precisa ser feito?
 
diff --git a/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md b/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md
index d97215d89..3a371dc36 100644
--- a/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md
+++ b/docs/announcements/pt/new-orders-authorization-flow-for-native-connectors.md
@@ -48,9 +48,7 @@ Esses campos foram retirados dos cadastros dos conectores e a seguinte mensagem
 
 > Atenção: pedidos com diferença de preço entre o marketplace e a VTEX só serão integrados mediante a [configuração de uma regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe).
 
-<div class = "alert alert-info">
-Ao integrar pela primeira vez com um conector nativo, é aconselhável que o seller crie a regra de Divergência de valores antes de configurar a integração. Descumprir a recomendação não impede que a integração seja concluída.
-</div>
+>ℹ️ Ao integrar pela primeira vez com um conector nativo, é aconselhável que o seller crie a regra de Divergência de valores antes de configurar a integração. Descumprir a recomendação não impede que a integração seja concluída.
 
 Para o seller que integrar pela primeira vez com um conector nativo e não criar a regra de Divergência de valores, pedidos com erro de divergência de preço ficarão pendentes no Admin VTEX, em **MARKETPLACE > Integrações > Pedidos**. A mensagem do erro na interface é a seguinte:
 
diff --git a/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md b/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
index bd5f5cad3..835a27b11 100644
--- a/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
+++ b/docs/announcements/pt/new-payment-provider-and-anti-fraud-management-interface.md
@@ -31,6 +31,4 @@ A nova página de gerenciamento de provedores de pagamento e antifraude já est
 
 Para mais detalhes sobre as funcionalidades da nova interface, acesse [Cadastrar provedores de pagamento e antifraude](https://help.vtex.com/pt/tutorial/afiliacoes-de-gateway--tutorials_444).
 
-<div class = "alert alert-warning">
-  A versão anterior da interface de gerenciamento de afiliações, disponível em <b>Configurações da loja > Pagamentos > Configurações > Afiliações de gateways</b>, ainda poderá ser acessada até 14 de janeiro de 2024.
-</div>
+>⚠️ A versão anterior da interface de gerenciamento de afiliações, disponível em **Configurações da loja > Pagamentos > Configurações > Afiliações de gateways**, ainda poderá ser acessada até 14 de janeiro de 2024.
diff --git a/docs/announcements/pt/new-ready-to-dispatch-functionality.md b/docs/announcements/pt/new-ready-to-dispatch-functionality.md
index 525ba26d0..c3a9cf937 100644
--- a/docs/announcements/pt/new-ready-to-dispatch-functionality.md
+++ b/docs/announcements/pt/new-ready-to-dispatch-functionality.md
@@ -21,9 +21,7 @@ Para que o envio de pacotes seja feito pelas transportadoras é preciso que cada
 
 A nova funcionalidade permite notificar transportadoras e imprimir etiquetas padronizadas para o envio de pacotes. Com a ferramenta, a loja também consulta as etiquetas de pacotes que estão prontos para envio (pacotes de pedidos faturados) e pedidos que já tiveram as etiquetas impressas.
 
-<div class = "alert alert-info">
-As etiquetas geradas seguem o padrão VTEX Shipping Network para transportadoras que possuem integração com essa solução.
-</div>
+>ℹ️ As etiquetas geradas seguem o padrão VTEX Shipping Network para transportadoras que possuem integração com essa solução.
 
 ## Por que realizamos esta mudança?
 
diff --git a/docs/announcements/pt/partial-invoice-settlements-in-oms.md b/docs/announcements/pt/partial-invoice-settlements-in-oms.md
index 865002ad1..4b9842051 100644
--- a/docs/announcements/pt/partial-invoice-settlements-in-oms.md
+++ b/docs/announcements/pt/partial-invoice-settlements-in-oms.md
@@ -19,9 +19,7 @@ Ao gerenciar pedidos no OMS, o sistema gerenciador de pedidos da VTEX, inserir a
 
 Desenvolvemos uma melhoria no OMS que fará com que as faturas parciais inseridas nos pedidos também disparem liquidações parciais na transação. O valor total do pedido será atualizado após a inserção da nota fiscal, e corresponde ao que é captado pelo gateway de pagamentos da VTEX. 
 
-<div class = "alert alert-info">
-A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Conectores legados não possuem suporte à funcionalidade.
-</div>
+>ℹ️ A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Conectores legados não possuem suporte à funcionalidade.
 
 ## O que mudou?
 
diff --git a/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md b/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
index 24dca2343..74dbc576a 100644
--- a/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
+++ b/docs/announcements/pt/requests-with-pagination-will-change-in-the-search-api.md
@@ -15,9 +15,7 @@ announcementImageID: ''
 announcementSynopsisPT: 'A partir de 31/03/18, requisições com paginação na API de busca não vão ser feitas com o header resources do request.'
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 A partir de __31 de março__, as requisições com paginação na API de busca não vão mais poder ser feitas com o header `resources` do request. Ele será descontinuado e, para requisitar uma resposta da API, você deverá utilizar os parâmetros `_from` e `_to` na URL, conforme o exemplo:
 
diff --git a/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md b/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
index 619ea5376..cd40defa3 100644
--- a/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
+++ b/docs/announcements/pt/search-for-orders-in-the-vtex-admin-global-search-bar.md
@@ -34,9 +34,7 @@ Para isso, clique na barra de busca, selecione a opção `Pedidos`, e realize a
 
 Ao clicar em um resultado, você é redirecionado para a [página de detalhes](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-do-pedido--2Y75n54Cc9VizrlG1N6ZNl) do pedido. Além disso, os últimos 10 pedidos buscados ficam registrados como um histórico de buscas recentes, aumentando a praticidade de acesso. O registro de busca é armazenado a nível de [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) e não é compartilhado entre usuários diferentes.
 
-<div class = "alert alert-info">
-Para acessar pedidos pela busca global do Admin VTEX, é necessário que o <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> do usuário esteja associado ao recurso <b>View order</b> (chave OMSViewer) do <i>Order Management System</i> (OMS).
-</div>
+>ℹ️ Para acessar pedidos pela busca global do Admin VTEX, é necessário que o [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) do usuário esteja associado ao recurso **View order** (chave OMSViewer) do <i>Order Management System</i> (OMS).
 
 ## Por que fizemos essa mudança?
 
diff --git a/docs/announcements/pt/vtex-insurance-discontinuity.md b/docs/announcements/pt/vtex-insurance-discontinuity.md
index 3dc35bffc..f7a47fbdd 100644
--- a/docs/announcements/pt/vtex-insurance-discontinuity.md
+++ b/docs/announcements/pt/vtex-insurance-discontinuity.md
@@ -26,5 +26,5 @@ Não haverá nenhuma alteração contratual ou comercial, já que o contrato era
 
 Nenhuma ação é necessária, já que a atualização será aplicada automaticamente em todas as lojas VTEX. Eventuais dúvidas técnicas e problemas relacionados ao produto deverão ser tratadas diretamente com a [Assurant](https://www.assurant.com.br/). 
 
-<div class = "alert alert-warning"> A VTEX não prestará suporte técnico aos clientes.</div>
+>⚠️ A VTEX não prestará suporte técnico aos clientes.
 
diff --git a/docs/faq/en/search-with-specification-parameter-returns-empty.md b/docs/faq/en/search-with-specification-parameter-returns-empty.md
index f6e736e4f..71127c860 100644
--- a/docs/faq/en/search-with-specification-parameter-returns-empty.md
+++ b/docs/faq/en/search-with-specification-parameter-returns-empty.md
@@ -14,9 +14,7 @@ locale: en
 legacySlug: search-with-specification-parameter-returns-empty
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 If the URL `http://www.{account-name}.com.br/busca/?fq=specificationFilter_{XXX}:{Y}` is not bringing the products/SKUs that have the intended specification, the __Filter__ parameter is not marked in the product/SKU field registration.
 
diff --git a/docs/faq/en/why-does-a-search-term-not-return-existing-products.md b/docs/faq/en/why-does-a-search-term-not-return-existing-products.md
index b33778480..63ed10e29 100644
--- a/docs/faq/en/why-does-a-search-term-not-return-existing-products.md
+++ b/docs/faq/en/why-does-a-search-term-not-return-existing-products.md
@@ -14,9 +14,7 @@ locale: en
 legacySlug: why-does-a-search-term-not-return-existing-products
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 
 The article [How does VTEX search work?](/en/tutorial/how-does-vtex-search-work) illustrates the main rules that the search engine algorithm uses to display and prioritize the products based on a search term.
diff --git a/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md b/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
index 08e8992a6..1b783ebb2 100644
--- a/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
+++ b/docs/faq/en/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
@@ -14,9 +14,7 @@ locale: en
 legacySlug: why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 You can use the search parameters to filter product fields or SKU fields in the store search.
 
diff --git a/docs/faq/en/why-vtex-search-engine-ignores-some-terms.md b/docs/faq/en/why-vtex-search-engine-ignores-some-terms.md
index 497240049..bad25e299 100644
--- a/docs/faq/en/why-vtex-search-engine-ignores-some-terms.md
+++ b/docs/faq/en/why-vtex-search-engine-ignores-some-terms.md
@@ -14,9 +14,7 @@ locale: en
 legacySlug: why-vtex-search-engine-ignores-some-terms
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 The article [How does VTEX search work?](https://help.vtex.com/en/tutorial/how-does-vtex-search-work) illustrates the main rules that the search engine algorithm uses to display and prioritize the products based on a search term.
 
diff --git a/docs/faq/en/why-was-not-an-order-sent-to-the-anti-fraud.md b/docs/faq/en/why-was-not-an-order-sent-to-the-anti-fraud.md
index d80071e89..770bfee22 100644
--- a/docs/faq/en/why-was-not-an-order-sent-to-the-anti-fraud.md
+++ b/docs/faq/en/why-was-not-an-order-sent-to-the-anti-fraud.md
@@ -18,6 +18,4 @@ Whenever a payment is made, the payment gateway connector performs some initial
 
 After several attempts, if you don't get the expected responses, the payment and the order are both canceled. Orders in this situation are not sent to the anti-fraud.
 
-<div class = "alert alert-warning">
-You can not resubmit a canceled order to the anti-fraud.
-</div>
+>⚠️ You can not resubmit a canceled order to the anti-fraud.
diff --git a/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 4d0cdf6f2..5f5fb0462 100644
--- a/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/es/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: he-activado-la-recurrencia-de-un-producto-pero-no-aparece-en-el-sitio
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 Siempre que cambie o cree una suscripción, es necesario reindexar sus SKUs para que ella funcione correctamente. Al hacer esto, usted estará guardando la información de que ese SKU tiene un anexo (en este caso, la suscripción) y debe ser tratado de forma distinta.
 
diff --git a/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md b/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md
index c403f8822..c83405b75 100644
--- a/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md
+++ b/docs/faq/es/nao-encontro-uma-colecao-o-que-fazer.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: nao-encontro-uma-colecao-o-que-fazer
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 De forma predeterminada, el CMS sólo muestra las __últimas 20 colecciones__ actualizadas.
 
diff --git a/docs/faq/es/search-with-specification-parameter-returns-empty.md b/docs/faq/es/search-with-specification-parameter-returns-empty.md
index b4e2d345c..68f240e67 100644
--- a/docs/faq/es/search-with-specification-parameter-returns-empty.md
+++ b/docs/faq/es/search-with-specification-parameter-returns-empty.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: busqueda-con-parametro-de-especificacion-devuelve-busqueda-vacia
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 En el caso de que la URL `http://www.{account-name}.com.br/busca/?fq=specificationFilter_{XXX}:{Y}` no está trayendo los productos/SKUs que tienen la especificación deseada, es posible que el parámetro __Filtro__ no esté marcado en el registro del campo de producto/SKU.
 
diff --git a/docs/faq/es/why-does-a-search-term-not-return-existing-products.md b/docs/faq/es/why-does-a-search-term-not-return-existing-products.md
index 1b8f5153f..97a446909 100644
--- a/docs/faq/es/why-does-a-search-term-not-return-existing-products.md
+++ b/docs/faq/es/why-does-a-search-term-not-return-existing-products.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: por-que-un-termino-buscado-no-retorna-productos-existentes
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 
 El artículo [Cómo funciona la búsqueda de VTEX?](/es/tutorial/como-funciona-la-busqueda-de-vtex/) demuestra las principales reglas que el algoritmo del buscador utiliza para exhibir y priorizar los productos a partir de un término buscado.
diff --git a/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md b/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
index ee7b0bc47..c78db8cc2 100644
--- a/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
+++ b/docs/faq/es/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: por-que-el-filtro-de-campo-de-producto-o-sku-no-esta-traendo-resultado-en
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Usted puede utilizar los parámetros de búsqueda para filtrar los campos de producto o campos de SKU en la búsqueda de la tienda.
 
diff --git a/docs/faq/es/why-vtex-search-engine-ignores-some-terms.md b/docs/faq/es/why-vtex-search-engine-ignores-some-terms.md
index 243152b54..98ebd1471 100644
--- a/docs/faq/es/why-vtex-search-engine-ignores-some-terms.md
+++ b/docs/faq/es/why-vtex-search-engine-ignores-some-terms.md
@@ -14,9 +14,7 @@ locale: es
 legacySlug: por-que-el-buscador-de-vtex-ignora-algunos-terminos-buscados
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 El artículo [Cómo funciona la búsqueda de VTEX?](https://help.vtex.com/es/tutorial/como-funciona-la-busqueda-de-vtex) demuestra las principales reglas que el algoritmo del buscador utiliza para exhibir y priorizar los productos a partir de un término buscado.
 
diff --git a/docs/faq/es/why-was-not-an-order-sent-to-the-anti-fraud.md b/docs/faq/es/why-was-not-an-order-sent-to-the-anti-fraud.md
index 92172d7e8..785ebcff9 100644
--- a/docs/faq/es/why-was-not-an-order-sent-to-the-anti-fraud.md
+++ b/docs/faq/es/why-was-not-an-order-sent-to-the-anti-fraud.md
@@ -18,6 +18,4 @@ Cada vez que se realiza un pago, el conector de gateway de pago realiza algunas
 
 Después de varios intentos, si no obtiene las respuestas esperadas, el pago y el pedido se cancelan. Los pedidos en esta situación no se envían al antifraude.
 
-<div class = "alert alert-warning">
-No se puede reenviar un pedido cancelado para el antifraude.
-</div>
+>⚠️ No se puede reenviar un pedido cancelado para el antifraude.
diff --git a/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md b/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
index 26596aa42..5388808ee 100644
--- a/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
+++ b/docs/faq/pt/i-ve-activated-a-product-subscription-but-it-doesnt-appear-on-the-site.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: ativei-a-recorrencia-de-um-produto-mas-ele-nao-aparece-no-site
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 Sempre que você alterar ou criar uma assinatura, é preciso reindexar seus SKUs para que ela funcione corretamete. Ao fazer isso, você estará salvando a informação de que aquele SKU tem um anexo (neste caso, a assinatura) e deve ser tratado de forma diferente.
 
diff --git a/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md b/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md
index df2af4984..ef938e5ee 100644
--- a/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md
+++ b/docs/faq/pt/nao-encontro-uma-colecao-o-que-fazer.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: nao-encontro-uma-colecao-o-que-fazer
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 Por padrão, o CMS só exibe as __últimas 20 coleções__ atualizadas.
 
diff --git a/docs/faq/pt/search-with-specification-parameter-returns-empty.md b/docs/faq/pt/search-with-specification-parameter-returns-empty.md
index 88e7e83f0..8ba6652c7 100644
--- a/docs/faq/pt/search-with-specification-parameter-returns-empty.md
+++ b/docs/faq/pt/search-with-specification-parameter-returns-empty.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: busca-com-parametro-de-especificacao-retorna-busca-vazia-o-que-fazer
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Caso a URL `http://www.{account-name}.com.br/busca/?fq=specificationFilter_{XXX}:{Y}` não esteja trazendo os produtos/SKUs que têm a especificação desejada, é possível que o parâmetro __Filtro__ não esteja marcado no cadastro do campo de produto/SKU. 
 
diff --git a/docs/faq/pt/why-does-a-search-term-not-return-existing-products.md b/docs/faq/pt/why-does-a-search-term-not-return-existing-products.md
index 57ae7a41e..80f39bc15 100644
--- a/docs/faq/pt/why-does-a-search-term-not-return-existing-products.md
+++ b/docs/faq/pt/why-does-a-search-term-not-return-existing-products.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: por-que-um-termo-buscado-nao-retorna-produtos-que-existem
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 
 O artigo [Como funciona a busca da VTEX?](/pt/tutorial/como-funciona-a-busca-da-vtex/) demonstra as principais regras que o algoritmo do buscador utiliza para exibir e priorizar os produtos a partir de um termo buscado.
diff --git a/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md b/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
index 06be6f523..37290de16 100644
--- a/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
+++ b/docs/faq/pt/why-isnt-the-product-or-sku-field-filter-bringing-any-result-in-the-search.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: por-que-o-filtro-de-campo-de-produto-ou-campo-de-sku-nao-esta-retornando
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Você pode usar os parâmetros de busca para filtrar campos de produto ou campos de SKU na busca da loja.
 
diff --git a/docs/faq/pt/why-vtex-search-engine-ignores-some-terms.md b/docs/faq/pt/why-vtex-search-engine-ignores-some-terms.md
index 009e27ec5..e9c841d1f 100644
--- a/docs/faq/pt/why-vtex-search-engine-ignores-some-terms.md
+++ b/docs/faq/pt/why-vtex-search-engine-ignores-some-terms.md
@@ -14,9 +14,7 @@ locale: pt
 legacySlug: por-que-o-buscador-da-vtex-ignora-alguns-termos-buscados
 ---
 
-<div class = "alert alert-warning">
-  A VTEX oferece duas opções de busca: a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search, acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">O que é VTEX Intelligent Search?</a>.
-</div>
+>⚠️ A VTEX oferece duas opções de busca: a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search, acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">O que é VTEX Intelligent Search?</a>.
 
 O artigo [Como funciona a busca da VTEX?](https://help.vtex.com/pt/tutorial/como-funciona-a-busca-da-vtex) demonstra as principais regras que o algoritmo do buscador utiliza para exibir e priorizar os produtos a partir de um termo buscado.
 
diff --git a/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
index 2c789e362..01d2a425d 100644
--- a/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/en/automatic-update-of-deliveries-tracking-by-correios.md
@@ -34,9 +34,7 @@ It's possible to send tracking updates via API, with emails continuing to be sen
 
 Delivery confirmation via OMS is also passed on to the marketplaces.
 
-<div class = "alert alert-info">
-Now, we offer the <a href="https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib">VTEX Shipping Network</a>, a logistics solution to integrate your operation with Correios and/or carriers with partnerships with VTEX. All of your store's orders linked to this solution will have the tracking automatically updated. (Valid only for Brazil)
-</div>
+>ℹ️ Now, we offer the [VTEX Shipping Network](https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib), a logistics solution to integrate your operation with Correios and/or carriers with partnerships with VTEX. All of your store's orders linked to this solution will have the tracking automatically updated. (Valid only for Brazil)
 
 Another option is to use solutions developed by partners to track deliveries by Correios, such as [XP Agência's tracking system](https://rastreio.xpagencia.com.br/).
 
diff --git a/docs/known-issues/en/button-to-add-brand-in-the-product-registration-search-doesnt-work.md b/docs/known-issues/en/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
index bacb625f0..d9f1893a9 100644
--- a/docs/known-issues/en/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
+++ b/docs/known-issues/en/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Summary
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 The button to add the brand in the product registration search, inside the catalog, does not have the expected behavior. By choosing the brand and clicking this button, the search returns all products and the text of the search fields disappear.
 
diff --git a/docs/known-issues/en/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md b/docs/known-issues/en/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
index 46912edd6..2aacc5259 100644
--- a/docs/known-issues/en/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
+++ b/docs/known-issues/en/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Summary
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 When the searched term has a hyphen (`-`), the search replaces this character with a space in the querystring, not bringing the expected result.
 
diff --git a/docs/known-issues/en/search-doesnt-work-for-a-second-folderlevel.md b/docs/known-issues/en/search-doesnt-work-for-a-second-folderlevel.md
index 11d4cafa5..a02ab95bf 100644
--- a/docs/known-issues/en/search-doesnt-work-for-a-second-folderlevel.md
+++ b/docs/known-issues/en/search-doesnt-work-for-a-second-folderlevel.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Summary
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 In the [VTEX Search documentation](http://help.vtex.com/en/tutorial/how-does-vtex-search-work/), we have the following scenario:
 
diff --git a/docs/known-issues/en/search-result-totalizer-and-filters-showing-wrong-value.md b/docs/known-issues/en/search-result-totalizer-and-filters-showing-wrong-value.md
index 82750a24c..bf714eae8 100644
--- a/docs/known-issues/en/search-result-totalizer-and-filters-showing-wrong-value.md
+++ b/docs/known-issues/en/search-result-totalizer-and-filters-showing-wrong-value.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Summary
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 When doing any type of search (category, brand, by term etc), the searchNavigator control displays all possible filters for the result, usually on the side. On the side of each filter, the system displays the totalizer. That is the quantity of products that exist for each option. Eventually, this totalizer does not present a correct value and when clicking on the option the result displays more or less products than the quantity indicated in the filter.
 
diff --git a/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md b/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md
index 4e97280e4..c218a8f5e 100644
--- a/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md
+++ b/docs/known-issues/en/searchnavigator-control-multiselection-filter-disregards-searched-term.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Summary
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 When a user searches for a term and thereafter applies a filter to the multi-selection options (in the searchNavigator control), the searched term is initially removed from the query, meaning that the filter ignores the term and performs the search query only by considering the options chosen by the user.
 
diff --git a/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
index 366ae687e..e22c722f7 100644
--- a/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/en/secondlevel-folders-dont-consider-the-search-context.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Summary
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 Second-level folders are not considering the "search context" that was registered for it. The _slug_ of the URL's second level is acting as a filter of the first folder (based on its context).
 
diff --git a/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 7ffc0ca7c..0b6c71c4f 100644
--- a/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/en/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -38,9 +38,7 @@ To fix this issue, you should turn off the tracking toggle:
 
 Don’t worry: turning off this option will not make your store unprotected.
 
-<div class= "alert alert-info">
-If after these steps your Admin or store is still not loading, we advise you to try another browser.
-</div>
+>ℹ️ If after these steps your Admin or store is still not loading, we advise you to try another browser.
 
 ![Firefox bug EN](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/06a078dc34744d8e07cf858e2288679a/Firefox_bug_EN.jpg)
 
diff --git a/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
index dec29830c..530da1d5d 100644
--- a/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/es/automatic-update-of-deliveries-tracking-by-correios.md
@@ -34,9 +34,7 @@ Es posible enviar actualizaciones de rastreo vía API, manteniendo el comportami
 
 La confirmación de entrega hecha vía OMS también se retransmite a los marketplaces.
 
-<div class = "alert alert-info">
-Actualmente, ofrecemos el <a href="https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib">VTEX Shipping Network</a>, nuestra solución logística para integrar su operación con Correios y/o transportadoras asociadas. Todos los pedidos de su tienda vinculados a esta solución tendrán seguimiento (tracking) con actualizaciones automáticas. (Exclusivo Brasil)
-</div>
+>ℹ️ Actualmente, ofrecemos el [VTEX Shipping Network](https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib), nuestra solución logística para integrar su operación con Correios y/o transportadoras asociadas. Todos los pedidos de su tienda vinculados a esta solución tendrán seguimiento (tracking) con actualizaciones automáticas. (Exclusivo Brasil)
 
 Otra opción es utilizar soluciones desarrolladas por parceros para el seguimiento de las entregas de Correios, como el [rastreo de XP Agência](https://rastreio.xpagencia.com.br/).
 
diff --git a/docs/known-issues/es/button-to-add-brand-in-the-product-registration-search-doesnt-work.md b/docs/known-issues/es/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
index 419afa504..55a759b7c 100644
--- a/docs/known-issues/es/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
+++ b/docs/known-issues/es/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumario
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 El botón de agregar marca en la búsqueda del registro de productos, en el catálogo, no tiene el comportamiento esperado. Al elegir la marca y hacer clic en ese botón, la búsqueda devuelve todos los productos y los textos de los campos de búsqueda desaparecen.
 
diff --git a/docs/known-issues/es/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md b/docs/known-issues/es/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
index 67b352665..d51353b3d 100644
--- a/docs/known-issues/es/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
+++ b/docs/known-issues/es/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumario
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Cuando el término buscado tiene un guión (`-`), la búsqueda reemplaza este carácter por un espacio en la querystring, no trayendo el resultado esperado.
 
diff --git a/docs/known-issues/es/search-result-totalizer-and-filters-showing-wrong-value.md b/docs/known-issues/es/search-result-totalizer-and-filters-showing-wrong-value.md
index bd5b5f3e8..a64642b9c 100644
--- a/docs/known-issues/es/search-result-totalizer-and-filters-showing-wrong-value.md
+++ b/docs/known-issues/es/search-result-totalizer-and-filters-showing-wrong-value.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumario
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Al realizar cualquier tipo de búsqueda (categoría, marca, término, etc.), el control searchNavigator muestra todos los filtros posibles para el resultado, generalmente en el lateral. En el lado de cada filtro, el sistema muestra el totalizador. Esa es la cantidad de productos que existen para cada opción. Eventualmente, este totalizador no presenta un valor correcto y al hacer clic en la opción, el resultado muestra más o menos productos que la cantidad indicada en el filtro.
 
diff --git a/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md b/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md
index f4394729f..76d6a7f8d 100644
--- a/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md
+++ b/docs/known-issues/es/searchnavigator-control-multiselection-filter-disregards-searched-term.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumario
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Cuando el usuario realiza una búsqueda por término y, a continuación, aplica un filtro en las opciones de selección múltiple (en el control searchNavigator), el término buscado inicialmente se elimina de la consulta, es decir, el filtro ignora el término y aplica la búsqueda solo con las opciones elegidas por el usuario.
 
diff --git a/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md
index 643591c86..ac156ba82 100644
--- a/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/es/secondlevel-folders-dont-consider-the-search-context.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumario
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Las carpetas de segundo nivel no están considerando el "contexto de búsqueda" que se ha registrado para ella. El _slug_ del segundo nivel de la dirección URL está actuando como un filtro de la primera carpeta (según su contexto).
 
diff --git a/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 33209d0ae..cbd325149 100644
--- a/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/es/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -37,9 +37,7 @@ Para solucionar este problema, debe desactivar la opción de rastreo:
 
 No se preocupe: desactivar esta opción no significa que su tienda estará desprotegida.
 
-<div class= "alert alert-info">
-Si después de estos pasos su Admin VTEX o tienda aún no se carga, le sugerimos que intente acceder con otro navegador.
-</div>
+>ℹ️ Si después de estos pasos su Admin VTEX o tienda aún no se carga, le sugerimos que intente acceder con otro navegador.
 
 ![Firefox bug ES](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/5d89ca13799da3ada490e383f0913573/Firefox_bug_ES.jpg)
 
diff --git a/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md b/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
index edf04445d..3ff9cb5b1 100644
--- a/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
+++ b/docs/known-issues/pt/automatic-update-of-deliveries-tracking-by-correios.md
@@ -35,9 +35,7 @@ Basta ter um código de rastreio válido em qualquer pedido. Nos dias seguintes,
 
 A confirmação de entrega feita via OMS também é repassada aos marketplaces.
 
-<div class = "alert alert-info">
-Atualmente, oferecemos o <a href="https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib">VTEX Shipping Network</a>, nossa solução logística para integrar sua operação aos serviços dos Correios e/ou transportadoras parceiras. Todos os pedidos da loja que estiverem vinculados a essa solução vão dispor de rastreamento com atualização automática.
-</div>
+>ℹ️ Atualmente, oferecemos o [VTEX Shipping Network](https://help.vtex.com/pt/subcategory/vtex-shipping-network--5n5MnINzWTQUX1I2EZl4Ib), nossa solução logística para integrar sua operação aos serviços dos Correios e/ou transportadoras parceiras. Todos os pedidos da loja que estiverem vinculados a essa solução vão dispor de rastreamento com atualização automática.
 
 Outra opção é utilizar soluções desenvolvidas por parceiros para acompanhar entregas dos Correios, como o [rastreio da XP Agência](https://rastreio.xpagencia.com.br/).
 
diff --git a/docs/known-issues/pt/button-to-add-brand-in-the-product-registration-search-doesnt-work.md b/docs/known-issues/pt/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
index f215885e6..6fc67210c 100644
--- a/docs/known-issues/pt/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
+++ b/docs/known-issues/pt/button-to-add-brand-in-the-product-registration-search-doesnt-work.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 O botão de adicionar marca na busca de Cadastro de Produtos no catálogo não tem o comportamento esperado. Ao escolher a marca e clicar nesse botão, a busca retorna todos os produtos e os textos dos campos de busca desaparecem.
 
diff --git a/docs/known-issues/pt/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md b/docs/known-issues/pt/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
index 174b35ea6..6a64eeb86 100644
--- a/docs/known-issues/pt/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
+++ b/docs/known-issues/pt/search-doesnt-encode-hyphen-and-replaces-it-with-a-space.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Quando o termo buscado possui um hífen (`-`), a busca substitui este caractere por um espaço na querystring, não trazendo o resultado esperado.
 
diff --git a/docs/known-issues/pt/search-doesnt-work-for-a-second-folderlevel.md b/docs/known-issues/pt/search-doesnt-work-for-a-second-folderlevel.md
index 3f1c5190f..275970c3c 100644
--- a/docs/known-issues/pt/search-doesnt-work-for-a-second-folderlevel.md
+++ b/docs/known-issues/pt/search-doesnt-work-for-a-second-folderlevel.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Na [documentação da Busca da VTEX](http://help.vtex.com/tutorial/como-funciona-a-busca-da-vtex/), temos o seguinte cenário contemplado:
 
diff --git a/docs/known-issues/pt/search-result-totalizer-and-filters-showing-wrong-value.md b/docs/known-issues/pt/search-result-totalizer-and-filters-showing-wrong-value.md
index d5ee1337b..60891daf1 100644
--- a/docs/known-issues/pt/search-result-totalizer-and-filters-showing-wrong-value.md
+++ b/docs/known-issues/pt/search-result-totalizer-and-filters-showing-wrong-value.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Ao fazer qualquer tipo de busca (categoria, marca, por termo etc), o controle searchNavigator exibe, normalmente na lateral, todos os filtros possíveis para o resultado. Do lado de cada filtro, o sistema exibe o totalizador, ou seja, a quantidade de produtos que existe para cada opção. Eventualmente esse totalizador não apresenta um valor correto e, ao clicar na opção, o resultado exibe mais ou menos produtos do que a quantidade indicada no filtro.
 
diff --git a/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md b/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md
index 02c9907cb..1cbfe7de4 100644
--- a/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md
+++ b/docs/known-issues/pt/searchnavigator-control-multiselection-filter-disregards-searched-term.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Quando o usuário realiza uma busca por termo e, em seguida, aplica um filtro nas opções de multi seleção (no controle searchNavigator), o termo buscado inicialmente é removido da consulta, ou seja, o filtro ignora o termo e aplica a busca somente com as opções escolhidas pelo usuário.
 
diff --git a/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md b/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md
index 1ef7e71f7..d0c9ca143 100644
--- a/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md
+++ b/docs/known-issues/pt/secondlevel-folders-dont-consider-the-search-context.md
@@ -18,9 +18,7 @@ internalReference:
 
 ## Sumário
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Pastas de segundo nível não estão considerando o "contexto de busca" que foi cadastrado para ela. O _slug_ do segundo nível da URL está atuando como um filtro da primeira pasta (com base no contexto dela).
 
diff --git a/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md b/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
index 03de1111b..e1e9c36a2 100644
--- a/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
+++ b/docs/known-issues/pt/vtex-admin-and-the-storefront-might-experience-some-trouble-on-firefox-89-0.md
@@ -37,9 +37,7 @@ Para consertar esse problema, você deve desligar a opção de rastreamento:
 
 Não se preocupe: desligar essa opção não significa que sua loja estará desprotegida.    
 
-<div class= "alert alert-info">
-Se após estes passos o seu Admin ou loja ainda não carregarem, sugerimos que tente acessá-lo com outro navegador. 
-</div>  
+>ℹ️ Se após estes passos o seu Admin ou loja ainda não carregarem, sugerimos que tente acessá-lo com outro navegador.  
 
 ![Firefox bug PT](https://images.ctfassets.net/alneenqid6w5/4EZo0FaHBx1DfbSrGVpbku/4ec41440848f1adad3924c07d5154369/Firefox_bug_PT.jpg)
 
diff --git a/docs/tracks/en/add-on-products.md b/docs/tracks/en/add-on-products.md
index 1d4245b61..46037f75c 100644
--- a/docs/tracks/en/add-on-products.md
+++ b/docs/tracks/en/add-on-products.md
@@ -125,6 +125,4 @@ The main advantages of this feature are:
 
 - **Increased conversion rates and sales:** The feature encourages customers to return to the payment page to complete their purchase, thereby increasing sales and conversion rates for retailers.
 
-<div class = "alert alert-info">
-WhatsApp AI Campaigns is only available for stores using <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> that don't have Checkout customizations.
-</div>
+>ℹ️ WhatsApp AI Campaigns is only available for stores using [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) that don't have Checkout customizations.
diff --git a/docs/tracks/en/adding-new-stores-to-instore.md b/docs/tracks/en/adding-new-stores-to-instore.md
index 1161f14f2..55c06c889 100644
--- a/docs/tracks/en/adding-new-stores-to-instore.md
+++ b/docs/tracks/en/adding-new-stores-to-instore.md
@@ -74,9 +74,7 @@ You can add a physical store by following the steps below:
 * **Trade policy:** the [trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) that will be applied in the physical store. Mandatory field.
 * **Pickup point:** the [pickup point](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R) associated to this physical store, where customers pick up their orders. 
 
-<div class ="alert alert-info">
-<p>Changes can take up to 15 minutes to be processed and applied to VTEX Sales App.</p> 
-</div>
+>ℹ️ Changes can take up to 15 minutes to be processed and applied to VTEX Sales App.
 
 ## Searching for a physical store
 
diff --git a/docs/tracks/en/allowing-order-replacement.md b/docs/tracks/en/allowing-order-replacement.md
index 5d53bd316..90d93f3b5 100644
--- a/docs/tracks/en/allowing-order-replacement.md
+++ b/docs/tracks/en/allowing-order-replacement.md
@@ -18,9 +18,7 @@ trackSlugEN: orders
 
 The goal is to help them correct errors without having to manually place a new order or contact your support, which facilitates the operation of your store and reduces costs.
 
-<div class = "alert alert-warning">
-Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
-</div>
+>⚠️ Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Enabling order replacement
 
@@ -32,6 +30,4 @@ This feature is available to all stores. To enable it, follow the steps below:
 
 Within 15 minutes, after automatic cache refresh, the feature should be available.
 
-<div class = "alert alert-info">
-For more information about the feature and cases that do not allow replacement, see the article <a href="https://help.vtex.com/en/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8">Order replacement</a>.
-</div>
+>ℹ️ For more information about the feature and cases that do not allow replacement, see the article [Order replacement](https://help.vtex.com/en/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8).
diff --git a/docs/tracks/en/autocomplete-search.md b/docs/tracks/en/autocomplete-search.md
index 8b80535b3..2e8f138fc 100644
--- a/docs/tracks/en/autocomplete-search.md
+++ b/docs/tracks/en/autocomplete-search.md
@@ -14,9 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
-<div class = "alert alert-warning">
-The Autocomplete tool is enabled by default in VTEX Intelligent Search. It is not possible to disable it in the Admin.
-</div>
+>⚠️ The Autocomplete tool is enabled by default in VTEX Intelligent Search. It is not possible to disable it in the Admin.
 
 Autocomplete is the functionality that displays previous search results based on current and previous searches. These results are presented in four different lists, which can be together or separated, depending on the customer's interaction. The existing sections are:
 
@@ -37,19 +35,14 @@ During the interaction with the search bar, VTEX Intelligent Search immediately
 
 When the user starts typing, the system displays the _Search suggestions_ and the _Product suggestions_ and removes the previous lists.
 
-<div class = "alert alert-info">
-  <p>Section information <i>Most searched terms</i> and <i>Search suggestions</i> are updated daily using the data from the last 14 days of the customers' interaction with the search.</p>
-  </div>
+>ℹ️ Section information <i>Most searched terms</i> and <i>Search suggestions</i> are updated daily using the data from the last 14 days of the customers' interaction with the search.
 
 This way, it is possible to provide the customer with a more fluid and personalized search experience. They can view the result quickly and receive suggestions based on their search.
 
 Another advantage for the store's manager is the increase in conversion due to this dynamic of usability and experience.
 
-<div class = "alert alert-info">
-  <p>Autocomplete offers search keyword suggestions even for completely new stores that do not yet have data on customer interaction such as clicks and searches.
-    In this case, the feature suggests search options based on an algorithm that extracts keywords from the store's catalog, products, brands, and categories.
-    </p>
-  </div>
+>ℹ️ Autocomplete offers search keyword suggestions even for completely new stores that do not yet have data on customer interaction such as clicks and searches.
+>     In this case, the feature suggests search options based on an algorithm that extracts keywords from the store's catalog, products, brands, and categories.
 
  ## Most searched terms
 
diff --git a/docs/tracks/en/backend-integrations.md b/docs/tracks/en/backend-integrations.md
index bd5ed55b9..d5cb94d32 100644
--- a/docs/tracks/en/backend-integrations.md
+++ b/docs/tracks/en/backend-integrations.md
@@ -182,9 +182,7 @@ On VTEX, it is important to understand the distinction between products and SKUs
 - [Product](https://help.vtex.com/en/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru): Abstract catalog unit, visible on the store shelves.
 - [SKU](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA): Concrete catalog unit in stock, representing specific variations of a product, such as color, size, and other attributes. SKUs are displayed as individual items on product pages. SKUs are displayed as individual items on product pages.
 
-<div class = "alert alert-info">
-The way in which products and SKUs are structured directly influences the customer's shopping experience.
-</div>
+>ℹ️ The way in which products and SKUs are structured directly influences the customer's shopping experience.
 
 You should import products in the order shown in the table below:
 
@@ -265,9 +263,7 @@ There are two ways of tracking order status changes on VTEX:
 
 For both types of integration, you can apply [filters](https://developers.vtex.com/docs/guides/orders-feed#filter) to select the types of events that the back office should process.
 
-<div class = "alert alert-info">
-For most cases, VTEX recommends integrating orders via <a href="https://developers.vtex.com/docs/guides/orders-feed">Feed v3</a> due to its resilience.
-</div>
+>ℹ️ For most cases, VTEX recommends integrating orders via [Feed v3](https://developers.vtex.com/docs/guides/orders-feed) due to its resilience.
 
 #### Obtaining order details
 
@@ -394,9 +390,7 @@ If you can't find an app that meets the needs of your VTEX store, you can develo
 
   d. **(Optional) Validate whether the app meets your business needs:** Once the version has been published, it may be beneficial to install the app in a [production workspace](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace) and conduct an [A/B test](https://developers.vtex.com/docs/guides/ab-tests) in order to compare the sales conversion rate before and after using your new app.
 
-<div class = "alert alert-info">
-If you're interested in learning more about app development, we recommend visiting our <a href="https://learn.vtex.com/">Learning Center</a>.
-</div>
+>ℹ️ If you're interested in learning more about app development, we recommend visiting our [Learning Center](https://learn.vtex.com/).
 
 - **Considering making your app publicly available?** You can [make the app available](https://developers.vtex.com/docs/guides/vtex-io-documentation-making-your-new-app-version-publicly-available) in the App Store, allowing other accounts to leverage the solution you've developed.
 - **Do you want to make your app available on the App Store?** There are some advantages to making your app available on the App Store, such as increasing its visibility and the potential for [monetization](https://developers.vtex.com/docs/guides/vtex-io-documentation-setting-your-apps-billing-model). To do this, you need to follow a few steps and comply with certain rules. In summary, you must become a [registered developer](https://developers.vtex.com/docs/guides/vtex-io-documentation-becoming-a-registered-vtex-app-store-developer), ensure the app code is stored in a [GitHub](https://github.com) repository, develop the app in accordance with the [App Store's best practices](https://developers.vtex.com/docs/guides/vtex-io-documentation-homologation-requirements-for-vtex-app-store), and [submit it](https://developers.vtex.com/docs/guides/vtex-io-documentation-submitting-your-app-in-the-vtex-app-store) to the homologation process. Once it is approved, your app will be available on the App Store.
diff --git a/docs/tracks/en/billing-support.md b/docs/tracks/en/billing-support.md
index 7cb650abb..d0bb36530 100644
--- a/docs/tracks/en/billing-support.md
+++ b/docs/tracks/en/billing-support.md
@@ -26,9 +26,7 @@ VTEX is committed to ensuring compliance with the procedures and policies for pa
 
 - [Accounts Payable - International](https://help.vtex.com/en/tutorial/accounts-payable-international--3yea9sIlsA0KgUC28ASCGs): Practices to follow for all payments to suppliers related to the accounts payable procedures of VTEX branches outside Brazil.
 
-<div class = "alert alert-info">
-To check the list of VTEX international offices and to find out in which country the invoice is issued, see the <a href="https://help.vtex.com/en/tutorial/names-of-vtex-branches-worldwide--zg05n6OIOZOEmLW7dcq9z">Names of VTEX branches worldwide</a> article.
-</div>
+>ℹ️ To check the list of VTEX international offices and to find out in which country the invoice is issued, see the [Names of VTEX branches worldwide](https://help.vtex.com/en/tutorial/names-of-vtex-branches-worldwide--zg05n6OIOZOEmLW7dcq9z) article.
 
 Revenue refers to orders with the `Approved orders` status on the [Order Details page](https://help.vtex.com/en/tutorial/order-details-page--2Y75n54Cc9VizrlG1N6ZNl). Once an order is financially approved, the invoice reflects the total amount, including shipping and taxes. This is regardless of subsequent cancellations due to using the platform's infrastructure.
 
@@ -46,6 +44,4 @@ After the [first access](https://help.vtex.com/en/tracks/vtex-store-overview--eS
 
 To make these changes, you need to [open a ticket to billing support](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM#financial), indicating the type of change you need.
 
-<div class = "alert alert-info">
-For more information on how to request an SLA verification and the discounts granted for SLA violations, read the <a href="https://help.vtex.com/en/tutorial/how-to-request-sla-verification--3L99VeoLhYEwMqqkWKu86i">How to request a platform SLA verification? </a>
-</div>
+>ℹ️ For more information on how to request an SLA verification and the discounts granted for SLA violations, read the [How to request a platform SLA verification? ](https://help.vtex.com/en/tutorial/how-to-request-sla-verification--3L99VeoLhYEwMqqkWKu86i)
diff --git a/docs/tracks/en/canceling-an-order.md b/docs/tracks/en/canceling-an-order.md
index 8366884b5..83ea5ca45 100644
--- a/docs/tracks/en/canceling-an-order.md
+++ b/docs/tracks/en/canceling-an-order.md
@@ -21,9 +21,7 @@ You can cancel an order with VTEX in three different ways:
 
 >⚠️ Once an order is canceled, you cannot change its status. Orders that have **invoiced** status can not be canceled.
 
-<div class = "alert alert-info">
-Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
-</div>
+>ℹ️ Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Cancellation through Orders module
 
diff --git a/docs/tracks/en/configuring-synonyms.md b/docs/tracks/en/configuring-synonyms.md
index 9c4698cfe..323583dce 100644
--- a/docs/tracks/en/configuring-synonyms.md
+++ b/docs/tracks/en/configuring-synonyms.md
@@ -14,7 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugEN: vtex-intelligent-search
 ---
 
-<div class = "alert alert-info"> We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Synonyms</a> instead of <a href="https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Substitute Words</a> to associate words with products, as synonyms allow you to manage terms per product in a more scalable way. Contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a> for more information.</div>
+>ℹ️ We recommend using [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) instead of [Substitute Words](https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete) to associate words with products, as synonyms allow you to manage terms per product in a more scalable way. Contact our [Support team](https://support.vtex.com/hc/pt-br/requests) for more information.
 
 There are two ways to set up synonyms in VTEX Admin: [individually](#creating-synonyms-individually) or by [importing a spreadsheet in CSV format](#importing-csv-spreadsheet). If you need to register synonyms in bulk, we recommend using the spreadsheet. See the instructions for each configuration form in the following sections.
 
diff --git a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index eeb0e6674..a49c305bf 100644
--- a/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/en/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -22,9 +22,7 @@ To start configuring the integration, please follow the steps below:
 2. By default, the fields related to **region and currency** and the **URL** of your VTEX store will be filled in. Check the information and, if necessary, make changes.
 3. Unless you have a custom Facebook Pixel implementation, keep the option_ Enable Pixel configuration_ enabled.
 
-  <div class = "alert alert-info">
-Regardless of whether you have installed the <a href= "https://apps.vtex.com/vtex-facebook-pixel/p">Facebook Pixel app</a>, the recommendation is that the <b>Enable Pixel configuration</b> option remains enabled. The exception is when you already use the Google Tag Manager. More information on <a href= "https://help.vtex.com/en/tracks/integration-with-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D/434Z1iWnaa0zbOMDyr6oi#facebook-pixel">Facebook Pixel</a>.
-</div>
+  >ℹ️ Regardless of whether you have installed the <a href= "https://apps.vtex.com/vtex-facebook-pixel/p">Facebook Pixel app</a>, the recommendation is that the **Enable Pixel configuration** option remains enabled. The exception is when you already use the Google Tag Manager. More information on <a href= "https://help.vtex.com/en/tracks/integration-with-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D/434Z1iWnaa0zbOMDyr6oi#facebook-pixel">Facebook Pixel</a>.
 
 4. Click on `CONTINUE WITH FACEBOOK`.
 5. The next screen asks for your Facebook account. Fill in your information and click on `Log in`. If you have the [Facebook integration](https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc) configured, your data will already be saved.
diff --git a/docs/tracks/en/creating-regular-promotions.md b/docs/tracks/en/creating-regular-promotions.md
index a13eeeb1d..6055d8708 100644
--- a/docs/tracks/en/creating-regular-promotions.md
+++ b/docs/tracks/en/creating-regular-promotions.md
@@ -57,9 +57,7 @@ In this section, you need to configure your promotion's general information. The
   - **Maximum shipping:** Maximum amount for the shipping cost.
   - **Free shipping:** Full discount on shipping costs.
   - **Gift:** Full discount on the product amount set as a gift. By selecting this option, you can indicate the SKU (by name or ID) that will be considered a gift, choose if you want to activate the gift multiplier, and the maximum number of products that can be used as gifts in the promotion.
-<div class = "alert alert-info">
-The gift product must have a price associated with it, even though it is given to the customer for free.
-</div>
+>ℹ️ The gift product must have a price associated with it, even though it is given to the customer for free.
 
   - **Nominal discount based on formula:** Discount calculated based on a formula you can create using the product total amount, shipping, and the number of items as variables. Please note that the shipping cost considered by the formula will be the lowest available for the order, regardless of the customer's selection. The decimal separator must always be a period. For example: If the discount is 30% of the product's total amount + shipping cost, the formula should be (total + freight) * 0.3. For more information about the formula, check out our [documentation](https://help.vtex.com/en/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
   - **Nominal reward value:** Credit that will be added to the store's reward program. For more information, check out the [Regular promotion with reward value](https://help.vtex.com/en/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) article.
@@ -68,9 +66,7 @@ The gift product must have a price associated with it, even though it is given t
   - **Additional information (optional):** Allows you to add a name and value to the promotion.
   - **Promotion is highlighted:** Adds a tag with the promotion name to the window display and the product page. This tag will only be added if you use the right promotion display control in the template `<vtex.cmc:discountHightLight/>`.
 
-<div class = "alert alert-info">
-Nominal promotions will only be displayed in the cart, not in the window display or on the product page.
-</div>
+>ℹ️ Nominal promotions will only be displayed in the cart, not in the window display or on the product page.
 
 ## Restrict this promotion to seller products
 
@@ -81,9 +77,7 @@ In this section, you can determine to which sellers the promotion will apply. Yo
 
 For the promotion to be valid for all sellers, leave the field blank.
 
-<div class = "alert alert-warning">
-  <p>You cannot directly select a white label seller. To include a white label seller to the promotion, there are two options:</p><ol>1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.</ol><ol>2. Leave the checkbox empty to include all sellers, meaning that all types of sellers - whether white label or not - will be added to the promotion.</ol>
-</div>
+>⚠️ You cannot directly select a white label seller. To include a white label seller to the promotion, there are two options:1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.2. Leave the checkbox empty to include all sellers, meaning that all types of sellers - whether white label or not - will be added to the promotion.
 
 ## Trade policy
 
@@ -129,9 +123,7 @@ The order must meet the conditions specified in this section for the promotion t
 - **Apply the selected discount only when one of the above carriers is selected by the customer:** The promotion will only be applied once the customer has selected the shipping method in question. If it is not selected, it will not be eligible for the discount. This criterion will only be considered if the promotion type refers to the shipping cost, i.e., only if it is one of the following types: Percentage shipping, Nominal shipping, Maximum shipping, or Free shipping.
 - **Payment method:** Allows you to choose if the promotion will be applied to one or more of the selected payment methods.
 
-<div class = "alert alert-info">
-By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact [our Support](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue).
-</div>
+>ℹ️ By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact [our Support](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue).
 
 - **Number of installments:** Discount given if the number of installments selected by the customer is within the specified range. This field does not apply to boletos (Brazilian payment method).
 >⚠️ Promotions based on payment method and number of installments do not apply to orders paid for with two cards or vouchers.
@@ -141,9 +133,7 @@ By default, you can add up to 20 payment methods per promotion. You can also cus
 - **Create a new coupon with the UTMs above:** Creates a coupon from the added UTMs to give customers access to the promotion using just the coupon code, without the need for UTMs.
 - **utmi_cp:** The discount will be given if the customer navigation uses the utmi_cp parameter with the specified value, which is case-sensitive.
 
-<div class = "alert alert-info">
-In the UTMs field, enter only the value that the UTMs must match to activate the promotion. You don't need to enter ?utm_source= in the field.
-</div>
+>ℹ️ In the UTMs field, enter only the value that the UTMs must match to activate the promotion. You don't need to enter ?utm_source= in the field.
 
 - **Only on first purchase:** The discount will only be given on the customer's first purchase.
 - **Apply the discount even if the user is not logged in?:** This field is available when the Only on first purchase field is selected. If this field is checked, the promotion will be applied even if the customer has not entered their email and password. When unchecked, the promotion will only be applied if the customer has logged in with their email and password.
diff --git a/docs/tracks/en/facebook-business-extension.md b/docs/tracks/en/facebook-business-extension.md
index 676941bdd..08ec31a0e 100644
--- a/docs/tracks/en/facebook-business-extension.md
+++ b/docs/tracks/en/facebook-business-extension.md
@@ -51,6 +51,4 @@ The Conversions API is designed to create a direct connection between your marke
 - Improved measurement of marketing data.
 - Increased data control.
 
-<div class = "alert alert-info">
-Learn more in the Facebook documentation <a href= "https://www.facebook.com/business/help/2041148702652965?locale=en_US">About Conversions API</a>.
-</div>
+>ℹ️ Learn more in the Facebook documentation <a href= "https://www.facebook.com/business/help/2041148702652965?locale=en_US">About Conversions API</a>.
diff --git a/docs/tracks/en/facebook.md b/docs/tracks/en/facebook.md
index 6c0647fec..f85a214ac 100644
--- a/docs/tracks/en/facebook.md
+++ b/docs/tracks/en/facebook.md
@@ -14,9 +14,7 @@ trackId: 7h8KvIC4DbRRc8VlyJ8PFc
 trackSlugEN: facebook-integration
 ---
 
-<div class = "alert alert-info">
-There is an integration with the <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D">Facebook Business Extension and Conversions API</a> that should be your default selection when integrating with Facebook. This is valid even if the <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Facebook Integration</a> has already been completed because the app integration ensures that previous features as well as others work, such as the Conversions API and Facebook Pixels.
-</div>
+>ℹ️ There is an integration with the <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D">Facebook Business Extension and Conversions API</a> that should be your default selection when integrating with Facebook. This is valid even if the <a href= "https://help.vtex.com/en/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Facebook Integration</a> has already been completed because the app integration ensures that previous features as well as others work, such as the Conversions API and Facebook Pixels.
 
 [Facebook](https://about.fb.com) is the social network with the largest number of users in the world. Created in 2004, it is the platform where more than three billion people connect and share information every day.
 
diff --git a/docs/tracks/en/frontend-implementation.md b/docs/tracks/en/frontend-implementation.md
index 1911c6bd5..bb1e00504 100644
--- a/docs/tracks/en/frontend-implementation.md
+++ b/docs/tracks/en/frontend-implementation.md
@@ -24,9 +24,7 @@ This article helps you choose the right technology for building your storefront
 
 The frontend implementation is a stage focused on defining the technologies to implement based on the business needs related to the storefront.
 
-<div class = "alert alert-info">
-The frontend can be implemented by the company's internal development team or our <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">implementation partners </a>.<a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512">Users</a> with access to the VTEX Admin can view our partner list through the <a href="https://partnernetwork.myvtex.com/Parceiros">Partner Portal</a>.
-</div>
+>ℹ️ The frontend can be implemented by the company's internal development team or our [implementation partners ](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners).[Users](https://help.vtex.com/en/tutorial/managing-users--tutorials_512) with access to the VTEX Admin can view our partner list through the [Partner Portal](https://partnernetwork.myvtex.com/Parceiros).
 
 ## Before you begin
 
@@ -39,9 +37,7 @@ Before implementing the frontend, you should configure the following steps in yo
 | Configuring catalog | The team configures the product[ catalog](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalog), category tree, and related information, such as descriptions, images, and prices, to populate and test the store, including features such as product listing pages (PLP), search features, product details pages (PDP), and checkout.<br><br>Not having a catalog can result in incomplete testing and data integration problems, which delays implementation.<br><br>Learn more in the [VTEX modules I](https://help.vtex.com/pt/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) article. |
 | Defining the apps needed to operate the store | The team defines the native and third-party apps needed to operate the store.<br><br>For stores that will be built using [Store Framework](#store-framework), there is a list of native and third-party apps.<br><br>Learn more in the [VTEX IO apps](https://developers.vtex.com/docs/vtex-io-apps) article. |
 
-<div class = "alert alert-info">
-The <a href="#development-stages">development stage</a> can run in parallel with other <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">backend integrations</a> and <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7">module configuration</a> steps, such as setting up payment methods and logistics. This will depend on the type of <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">architecture and planning</a> chosen for the VTEX store, and the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners">implementing agency</a> or <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">VTEX Support</a> should monitor these processes.
-</div>
+>ℹ️ The [development stage](#development-stages) can run in parallel with other [backend integrations](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) and [module configuration](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7) steps, such as setting up payment methods and logistics. This will depend on the type of [architecture and planning](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) chosen for the VTEX store, and the [implementing agency](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#implementation-partners) or [VTEX Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) should monitor these processes.
 
 ## Frontend development technologies on VTEX
 
@@ -120,9 +116,7 @@ For B2B stores, Store Framework is a good choice, as it provides the [B2B Suite]
 
 FastStore is an evolving alternative focused on store performance. This solution offers a fast loading experience, crucial for keeping store visitors engaged and reducing cart abandonment rates. For simpler use cases with a focus on performance, FastStore cab be the recommended technology.
 
-<div class = "alert alert-info">
-The <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">VTEX support</a> team can help you choose between one of the available storefront technologies.
-</div>
+>ℹ️ The [VTEX support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) team can help you choose between one of the available storefront technologies.
 
 The table below compares the two technologies based on their main features:
 
@@ -215,9 +209,7 @@ Before launching the store into production and [going live](https://help.vtex.co
 - [FastStore MVP requirements](#faststore-mvp-requirements)
 - [Store Framework MVP requirements](#store-framework-mvp-requirements)
 
-<div class = "alert alert-info">
-The following recommendations are for basic storefront setup. Other settings may be required depending on the <a href="https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">architecture chosen</a> for your store's operation.
-</div>
+>ℹ️ The following recommendations are for basic storefront setup. Other settings may be required depending on the [architecture chosen](https://help.vtex.com/en/tracks/vtex-store-overview--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) for your store's operation.
 
 ### Developing using FastStore
 
diff --git a/docs/tracks/en/getting-started-with-logistics.md b/docs/tracks/en/getting-started-with-logistics.md
index 224882b51..444f8f552 100644
--- a/docs/tracks/en/getting-started-with-logistics.md
+++ b/docs/tracks/en/getting-started-with-logistics.md
@@ -38,11 +38,10 @@ This walkthrough brings together the following articles:
 * [Shipping costs and simulation](https://help.vtex.com/en/tracks/logistics-101--13TFDwDttPl9ki9OXQhyjx/3by48jFhzpZEseYFpH9uVt): Explains how to set up shipping costs and use the shipping rate simulation tool.
 * [Scheduled deliveries and delivery capacity](https://help.vtex.com/en/tracks/logistics-101--13TFDwDttPl9ki9OXQhyjx/5TuyqHRCCwYMaDv4r8rZdo): Explains how to make scheduled deliveries available to customers and manage the delivery capacity of such deliveries. 
 
-<div class = "alert alert-info">If you have already made the first steps in the <b>Inventory & shipping</b> module, check out this complementary content:
-The article <a href="https://help.vtex.com/en/tutorial/logistics--53udnvI5eBy8DKo8FOjMoP">Logistics</a>, for quick access to information on the <b>Inventory & shipping</b> sections. 
-Our <a href="https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby">Logistics Glossary</a>, in which you can find the definitions of logistics terms used at VTEX.
-The logistics settings available via <a href="https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview">API</a>. 
-</div>
+>ℹ️ If you have already made the first steps in the **Inventory & shipping** module, check out this complementary content:
+> The article [Logistics](https://help.vtex.com/en/tutorial/logistics--53udnvI5eBy8DKo8FOjMoP), for quick access to information on the **Inventory & shipping** sections. 
+> Our [Logistics Glossary](https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby), in which you can find the definitions of logistics terms used at VTEX.
+> The logistics settings available via [API](https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview).
 
 Basically, the **Inventory & shipping** module is divided into the following sections:
 
@@ -58,8 +57,7 @@ Basically, the **Inventory & shipping** module is divided into the following sec
 
 ![estoque e entregaEN](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/8286563b415555a4ab5e56cb8e6e290c/estoque_e_entregaEN.png)
 
-<div class = "alert alert-info"> Clients using <a href="https://vtex.com/us-en/">VTEX Shipping Network</a> can access this feature in the Inventory & shipping module.
-</div>
+>ℹ️ Clients using [VTEX Shipping Network](https://vtex.com/us-en/) can access this feature in the Inventory & shipping module.
 
 Check out the following articles of this series to learn the order you should configure these sections and how the platform interprets these settings.
 
diff --git a/docs/tracks/en/go-live-process.md b/docs/tracks/en/go-live-process.md
index 52fdd2898..769ca58de 100644
--- a/docs/tracks/en/go-live-process.md
+++ b/docs/tracks/en/go-live-process.md
@@ -20,9 +20,7 @@ Here you will find detailed step-by-step instructions on how to go live with you
 
 ![Go-live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/b1f21c5f9b94732df8e7ca5fd3b6ed69/go_live_en.jpg)
 
-<div class = "alert alert-info">
-Note that a store in production is different from an account in production. In general, to have a store in production, you need to put the account in production and set up DNS pointing. See below all the steps involved in this process.
-</div>
+>ℹ️ Note that a store in production is different from an account in production. In general, to have a store in production, you need to put the account in production and set up DNS pointing. See below all the steps involved in this process.
 
 ## Before you begin
 
@@ -36,9 +34,7 @@ Copy this [Store configuration checklist](https://assets.ctfassets.net/alneenqid
 
 Your store's go-live process may vary depending on some aspects of your operation. As some steps are time-sensitive, we recommend you plan your go-live process at least 15 days in advance.
 
-<div class = "alert alert-info">
-If you use the Legacy CMS Portal and want to migrate to a storefront built using <a href="https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS IO</a>, follow the instructions in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migrating your storefront from Legacy CMS Portal to Store Framework</a> guide.
-</div>
+>ℹ️ If you use the Legacy CMS Portal and want to migrate to a storefront built using [CMS IO](https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), follow the instructions in the [Migrating your storefront from Legacy CMS Portal to Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io) guide.
 
 For organization and convenience, this guide divides the steps involved in the go-live into four stages:
 
diff --git a/docs/tracks/en/google-pay.md b/docs/tracks/en/google-pay.md
index d49fe3934..cdd00b2c8 100644
--- a/docs/tracks/en/google-pay.md
+++ b/docs/tracks/en/google-pay.md
@@ -27,26 +27,20 @@ To enable Google Pay, follow the steps below.
 1. In the VTEX Admin, go to **Store Settings > Payments > Wallets** or type **Wallets** in the search bar at the top of the page.
 2. Select **Activate** to include the Google Pay extension.
 
-<div class = "alert alert-info">
-<p>The card brands supported by the Google Pay extension are the ones configured in the payment conditions.</p>
-</div>
+>ℹ️ The card brands supported by the Google Pay extension are the ones configured in the payment conditions.
 
 ![google-pay-checkout-en](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/2857562e61a935524807632c23be2e91/Screenshot_2024-08-01_at_14.21.39.png)
 
 Google Pay will then be available in your VTEX store's checkout as a new payment method. It may take around 10 minutes to be implemented.
 
-<div class = "alert alert-warning">
-<p>For now, Google Pay does not support subscriptions.</p>
-</div>
+>⚠️ For now, Google Pay does not support subscriptions.
 
 To use Google Pay, you must meet the following requirements:
 
 * Having at least one active [payment condition](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) configured for credit or debit cards with an [acquirer](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente), establishing which acquirer will process the wallet payment.
 * Using [VTEX Checkout](https://help.vtex.com/en/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) in your store.
 
-<div class = "alert alert-warning">
-<p>For stores that have the <a href="https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> authentication flow configured and supported by the acquirer, payment with Google Pay will follow the card native flow and will use 3DS as well. For more information on how to configure the authentication flow, please refer to <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Setting up 3DS 2 authentication flow</a>.</p>
-</div>
+>⚠️ For stores that have the [3DS](https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) authentication flow configured and supported by the acquirer, payment with Google Pay will follow the card native flow and will use 3DS as well. For more information on how to configure the authentication flow, please refer to [Setting up 3DS 2 authentication flow](https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2).
 
 >ℹ️ You can also set up Google Pay to be processed with Adyen or Stripe. To do this, access the **Payment Conditions** screen in Admin, click on **Google Pay** and select the desired option.
 
@@ -73,9 +67,7 @@ To add the information that the order was placed with a Google Pay card to the e
 
 After this change, whenever there is any mention of the last four digits of the card in these email templates, the "(Google Pay)" information will be added for payments made with a digital wallet.
 
-<div class = "alert alert-info">
-<p>For stores provisioned as of March 2023, the templates will already be updated with the information for payments made with Google Pay.</p>
-</div>
+>ℹ️ For stores provisioned as of March 2023, the templates will already be updated with the information for payments made with Google Pay.
 
 ## FAQ
 
diff --git a/docs/tracks/en/how-does-vtex-intelligent-search-work.md b/docs/tracks/en/how-does-vtex-intelligent-search-work.md
index adec93591..f810a3f66 100644
--- a/docs/tracks/en/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/en/how-does-vtex-intelligent-search-work.md
@@ -49,9 +49,7 @@ Example: Suppose a customer wants to search for the term `ball`. Using the defau
 * `balk` (change 1 character)
 * `abll` (swap 2 characters next to each other)
 
-<div class ="alert alert-info">
-  <p>Blank spaces are not considered in <em>fuzzy</em>, so <code>base ball</code> will not be corrected to <code>baseball</code>. We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">synonyms</a> for such cases.</p>
-</div>
+>ℹ️ Blank spaces are not considered in *fuzzy*, so `base ball` will not be corrected to `baseball`. We recommend using [synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) for such cases.
 
 ### Minimum result
 
@@ -62,9 +60,7 @@ In a search with multiple terms, the following logic occurs:
 1. If the minimum result is not reached even after the initial autocorrect, the search starts to include more comprehensive results containing any of the search terms. For example, if a user searches for "nike sneakers" and the catalog doesn't have any products matching that name, the search will return products with only the term "sneakers" instead.
 2. If the comprehensive search doesn't return the minimum result, the process will be repeated, applying autocorrect again to each term.
 
-<div class= "alert alert-warning">
-  <p>Searches with multiple terms are more efficient when customers sort the results by relevance, as such sorting can return more results than the initial search context. When sorted by relevance, items with multiple terms are prioritized. However, with other sorting criteria, such as price or bestsellers, the result ranking is based on these numerical values and does not necessarily prioritize items that match more search terms.</p>
-</div>
+>⚠️ Searches with multiple terms are more efficient when customers sort the results by relevance, as such sorting can return more results than the initial search context. When sorted by relevance, items with multiple terms are prioritized. However, with other sorting criteria, such as price or bestsellers, the result ranking is based on these numerical values and does not necessarily prioritize items that match more search terms.
 
 ### Pagination limit
 
diff --git a/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
index ef1f2a422..d33ee6dfa 100644
--- a/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/en/how-to-create-and-edit-transactional-email-templates.md
@@ -23,9 +23,7 @@ To edit a transactional email template, follow the steps below.
 3. Change the e-mail title and the recipient (values bounded by double braces are variable; in the next article we will learn how to handle them). You can add recipients on Carbon Copy (`CC`) and Blind Carbon Copy (`CCO`).  
 4. Check the box __Use default sender__ to use the registered email address as default, as explained in the previous article on this track.
 
-<div class = "alert alert-info">
-The list of templates is available in the article <a href="https://help.vtex.com/en/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">Order transactional email templates</a>.
-</div>
+>ℹ️ The list of templates is available in the article [Order transactional email templates](https://help.vtex.com/en/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my).
 
 In the __HTML__ field you will find the template's HTML code. You can edit the code in the field itself or copy it to an editor of your choice, edit it and then paste it back into the template field.
 
diff --git a/docs/tracks/en/how-vtex-support-works.md b/docs/tracks/en/how-vtex-support-works.md
index 63dd647b6..f87829ced 100644
--- a/docs/tracks/en/how-vtex-support-works.md
+++ b/docs/tracks/en/how-vtex-support-works.md
@@ -20,10 +20,8 @@ VTEX Support is provided online and allows you to open tickets with different pr
 - Login using a Google account.
 - Email and password with two-factor authentication via app or SMS.
 
-<div class = "alert alert-warning">
-To get authentication authorization, the <a href="https://help.vtex.com/en/tutorial/managing-users--tutorials_512">user</a> must have access to the VTEX Admin and a <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">role </a>
- associated with <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager resources. </a>.
-</div>
+>⚠️ To get authentication authorization, the [user](https://help.vtex.com/en/tutorial/managing-users--tutorials_512) must have access to the VTEX Admin and a [role ](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc)
+>  associated with [License Manager resources. ](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3).
 
 VTEX Support is divided in regions, and each region has its own service level agreement (SLA), priority, and Customer Excellence (CX) team available for that region. These are the regions where support operates:
 
diff --git a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
index 2492fb3f4..81937ea48 100644
--- a/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
+++ b/docs/tracks/en/integrating-instore-to-a-new-payment-acquirer.md
@@ -121,9 +121,7 @@ Final URI that the payment app will receive to perform the refund action with th
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&sellerName=instoreqa&autoConfirm=True&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class = "alert alert-warning">
-<strong>NOTE:</strong> Not all parameters will be used by all payment acquirers/apps. Example: <code>transactionId</code>. This parameter is the ID of a transaction in VTEX that identifies all payments of a complete order on VTEX PCI Gateway. A transaction can contain multiple payments, such as when an order is paid with multiple credit or debit cards.
-</div>
+>⚠️ **NOTE:** Not all parameters will be used by all payment acquirers/apps. Example: `transactionId`. This parameter is the ID of a transaction in VTEX that identifies all payments of a complete order on VTEX PCI Gateway. A transaction can contain multiple payments, such as when an order is paid with multiple credit or debit cards.
 
 ## Examples of response URIs for each action
 
diff --git a/docs/tracks/en/integration-configurations.md b/docs/tracks/en/integration-configurations.md
index 6a4d521f3..f7d700d87 100644
--- a/docs/tracks/en/integration-configurations.md
+++ b/docs/tracks/en/integration-configurations.md
@@ -63,29 +63,28 @@ Shipping items using Wish ranges from the all-encompassing to the very specific.
 >
 > _Ex: the shipping rate to New York (metropolitan region) is U$ 10,00, while the rate for NY (State) is U$ 15,00._
 >
-> <div class = "alert alert-info">
->   OBS: shipping by region is only available to sellers that use **Wish Express** [(additional info here).]([https://merchantfaq.wish.com/hc/en-us/articles/360018939394-How-to-Ship-Wish-Express-to-Brazil])
+> >ℹ️ >   OBS: shipping by region is only available to sellers that use **Wish Express** [(additional info here).]([https://merchantfaq.wish.com/hc/en-us/articles/360018939394-How-to-Ship-Wish-Express-to-Brazil])
 >  To configure Wish Express, simply follow [these steps.]([https://merchantfaq.wish.com/hc/en-us/articles/232047747-Wish-Express-Sign-Up-Flow])
-  
-Specify if you'll use Wish Express in the setup. In case you won't, you may skip to next step.
-
-Remember that the shipping rate will be automatically set based on the [Logistics module shipping tables](https://help.vtex.com/tracks/logistics-101--13TFDwDttPl9ki9OXQhyjx/2Pj1gKR80QIuUhc0orMraD). This means that it the shipping will be dynamic and may vary due a change in the carrier's price table or even according to item availability.
-
-_ex: Carrier X has a shipping rate of U$ 7,00 to Atlanta (metropolitan region) in its price table. However, that price table is updated to U$ 9,55. Next time the inventory is updated, the shipping rate for that region will be updated for your Wish products._
- 
-## Defining the available carriers
-
-To indicate which of your store's carriers corresponds to [those accepted by Wish](https://merchant.wish.com/documentation/shippingproviders), you'll need to perform a from/to in your configuration.
-
-  1. Using the first selector (_dropdown_), indicate which carrier will be used for Wish;
-  2. Using the second selector, indicate which VTEX [carrier type]([https://help.vtex.com/tutorial/difference-between-delivery-types--tutorials_126] would correspond to the one selected during the previous step;
-
-  _Ex: Suppose that you're using TNT as a carrier and that your VTEX Shipping Networkistics panel identifies this carrier or delivery type as "standard". Therefore, the field should be called "Standard". Remember that the word should exactly match the one appearing in your Logistics module. 
-  
-  3. Click on "save" to conclude the setup.
-
-<div class = "alert alert-info">
-  OBS: if a non-Wish certified carrier is added, orders will not benefit from tracking, and consequently, <strong>no commission</strong> will be transferred. Use extra caution when performing this step.</div>
+>
+> Specify if you'll use Wish Express in the setup. In case you won't, you may skip to next step.
+>
+> Remember that the shipping rate will be automatically set based on the [Logistics module shipping tables](https://help.vtex.com/tracks/logistics-101--13TFDwDttPl9ki9OXQhyjx/2Pj1gKR80QIuUhc0orMraD). This means that it the shipping will be dynamic and may vary due a change in the carrier's price table or even according to item availability.
+>
+> _ex: Carrier X has a shipping rate of U$ 7,00 to Atlanta (metropolitan region) in its price table. However, that price table is updated to U$ 9,55. Next time the inventory is updated, the shipping rate for that region will be updated for your Wish products._
+>
+> ## Defining the available carriers
+>
+> To indicate which of your store's carriers corresponds to [those accepted by Wish](https://merchant.wish.com/documentation/shippingproviders), you'll need to perform a from/to in your configuration.
+>
+> 1. Using the first selector (_dropdown_), indicate which carrier will be used for Wish;
+>   2. Using the second selector, indicate which VTEX [carrier type]([https://help.vtex.com/tutorial/difference-between-delivery-types--tutorials_126] would correspond to the one selected during the previous step;
+>
+> _Ex: Suppose that you're using TNT as a carrier and that your VTEX Shipping Networkistics panel identifies this carrier or delivery type as "standard". Therefore, the field should be called "Standard". Remember that the word should exactly match the one appearing in your Logistics module. 
+>
+> 3. Click on "save" to conclude the setup.
+>
+> <div class = "alert alert-info">
+>   OBS: if a non-Wish certified carrier is added, orders will not benefit from tracking, and consequently, **no commission** will be transferred. Use extra caution when performing this step.
 
 ## Price divergence rates
  
diff --git a/docs/tracks/en/inventory.md b/docs/tracks/en/inventory.md
index ef50f039d..5367ff9c1 100644
--- a/docs/tracks/en/inventory.md
+++ b/docs/tracks/en/inventory.md
@@ -16,9 +16,7 @@ trackSlugEN: logistics-101
 
 Inventory is the feature for managing products available for sale. Once [products have been added](https://help.vtex.com/en/tutorial/product-registration-fields--4dYXWIK3zyS8IceKkQseke) to the [catalog](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), they must be listed in a warehouse to become available for sale. The [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) module is where catalog items are associated with a warehouse.
 
-<div class = "alert alert-info">
-Remember to add at least one <a href="https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb">warehouse</a> in your store before using the <a href="https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139">Inventory</a>. 
-</div>
+>ℹ️ Remember to add at least one [warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb) in your store before using the [Inventory](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139).
 
 In the inventory, retailers can see:
 
@@ -31,9 +29,7 @@ To add items in bulk to the inventory, use the inventory template to import them
 
 Use the [critical inventory level alert](https://help.vtex.com/en/tutorial/setting-up-the-critical-stock-alert--6FD0GHeQPCsKIMgkQ88SGu) to receive notifications when an item is almost out of stock.
 
-<div class = "alert alert-info">
-You can also set up your inventory via the <a href="https://developers.vtex.com/vtex-rest-api/reference/inventory"> Inventory API.</a>
-</div>
+>ℹ️ You can also set up your inventory via the [ Inventory API.](https://developers.vtex.com/vtex-rest-api/reference/inventory)
 
 ### Learn more
 
diff --git a/docs/tracks/en/managing-sales-associates-in-instore.md b/docs/tracks/en/managing-sales-associates-in-instore.md
index 4ff8a8873..9c9e62574 100644
--- a/docs/tracks/en/managing-sales-associates-in-instore.md
+++ b/docs/tracks/en/managing-sales-associates-in-instore.md
@@ -40,9 +40,7 @@ You can add a sales associate by following the steps below:
 
 After being added, the sales associate will receive a confirmation email and be redirected to the sales associate's login option in Sales App.
 
-<div class ="alert alert-warning">
-<p>Sales associates registered in Sales App cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.</p>
-</div>
+>⚠️ Sales associates registered in Sales App cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.
 
 ### Sales associate fields
 
@@ -57,9 +55,7 @@ After being added, the sales associate will receive a confirmation email and be
 
 * **Store:** the [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) in which the sales associate will be registered. Mandatory field.
 
-<div class ="alert alert-info">
-<p>Changes can take up to 15 minutes to be processed and applied to Sales App.</p> 
-</div>
+>ℹ️ Changes can take up to 15 minutes to be processed and applied to Sales App.
 
 ## Searching for a sales associate
 
diff --git a/docs/tracks/en/manual-product-matching-on-amazon.md b/docs/tracks/en/manual-product-matching-on-amazon.md
index a4f262739..77fe3b885 100644
--- a/docs/tracks/en/manual-product-matching-on-amazon.md
+++ b/docs/tracks/en/manual-product-matching-on-amazon.md
@@ -14,9 +14,7 @@ trackId: 6sgd4Pagy3wNsWKBvmIFrP
 trackSlugEN: amazon-integration
 ---
 
-<div class = "alert alert-info">
-The flow documented in this article is not mandatory. If you choose to keep automatic matching, VTEX takes no responsibility for any possible matching issues on Amazon.
-</div>
+>ℹ️ The flow documented in this article is not mandatory. If you choose to keep automatic matching, VTEX takes no responsibility for any possible matching issues on Amazon.
 
 Whenever an [SKU](https://help.vtex.com/en/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) with a registered [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) is sent to Amazon, the marketplace does the matching by combining offers for the same product using its EAN. 
 
diff --git a/docs/tracks/en/mapping-colors-and-sizes.md b/docs/tracks/en/mapping-colors-and-sizes.md
index 6e8562aa3..afe3a7b91 100644
--- a/docs/tracks/en/mapping-colors-and-sizes.md
+++ b/docs/tracks/en/mapping-colors-and-sizes.md
@@ -18,14 +18,10 @@ After going through the initial Wish integration configurations, we will now map
 
 This information is sent when uploading the mapping spreadsheet, which has a from/to. This mapping will be performed once for each category. This means that once the mapping has been performed once, new products that are created will be directly integrated in the correct category, together with their corresponding variations and attributes.
 
-<div class = "alert alert-info">
-You need to map categories so that Wish can correctly distinguish your SKUs. 
-Example: suppose that two SKUs exist for the same product, having different colors but the same sizes in VTEX. If the category is not mapped, Wish will recognize the two SKUs as merely one. 
-</div>
+>ℹ️ You need to map categories so that Wish can correctly distinguish your SKUs. 
+> Example: suppose that two SKUs exist for the same product, having different colors but the same sizes in VTEX. If the category is not mapped, Wish will recognize the two SKUs as merely one.
 
-<div class = "alert alert-warning">
-Products with no color or size will not be submitted to Wish. If a category does not have these fields in VTEX, you will need to <a href="https://help.vtex.com/en/tutorial/creating-sku-fields--tutorials_119">create an SKU field</a> in the Catalog and fill it ou with the appropriate values before mapping color and size for your SKUs.
-</div>
+>⚠️ Products with no color or size will not be submitted to Wish. If a category does not have these fields in VTEX, you will need to [create an SKU field](https://help.vtex.com/en/tutorial/creating-sku-fields--tutorials_119) in the Catalog and fill it ou with the appropriate values before mapping color and size for your SKUs.
 
   - Download the Wish Mapping Spreadsheet in .xlsx format [here](https://drive.google.com/uc?export=download&id=1yJCgahkDhc4Gbvtxpe9kID1CwWsijdOf) .
 
@@ -62,9 +58,7 @@ Notice that VTEX uses the fields "Colors" and "Sizes", while Wish uses "Color" a
 On the VTEX platform, the product pertaining to this category have two possible colors: wine red and icy white.
 You should choose the closest color match, which in Wish's case can be "White/Ice Glaze" for "Icy White" and "Red" for "Wine Red", based on [list of accepted colors](https://merchant.wish.com/documentation/colors)). 
 
-<div class = "alert alert-info">
-The table's header should be filled in exactly as in the example below. Remember to not add any special characters such as "enter" or "space" when filling this table in.   
-</div>
+>ℹ️ The table's header should be filled in exactly as in the example below. Remember to not add any special characters such as "enter" or "space" when filling this table in.
 
 ![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
diff --git a/docs/tracks/en/opening-tickets.md b/docs/tracks/en/opening-tickets.md
index 3d7aa2ac7..888ba7824 100644
--- a/docs/tracks/en/opening-tickets.md
+++ b/docs/tracks/en/opening-tickets.md
@@ -22,9 +22,7 @@ Access to a VTEX account gives you access to the [support dashboard](https://sup
 
 ![Support imagem 1 - EN](https://images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/c0f1b4654f82949a438f82b2416a11c7/support_imagem1_EN.gif)
 
-<div class = "alert alert-info">
-Learn more about how to open a ticket and ticket types in the article <a href="https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM">Opening tickets to VTEX support. </a>
-</div>
+>ℹ️ Learn more about how to open a ticket and ticket types in the article [Opening tickets to VTEX support. ](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM)
 
 ## Support types
 
diff --git a/docs/tracks/en/partial-invoices.md b/docs/tracks/en/partial-invoices.md
index 5cdfec9dc..b2f96a3c6 100644
--- a/docs/tracks/en/partial-invoices.md
+++ b/docs/tracks/en/partial-invoices.md
@@ -32,9 +32,7 @@ Partial invoices generate the following actions in the **Orders** module and oth
 * As the partial invoice only settles the amount corresponding to the invoice, requesting changes to the order amount is possible. A partial invoice keeps the transaction open.
 * Orders with partial invoices cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
-<div class = "alert alert-info">
-The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Legacy connectors do not support the functionality.
-</div>
+>ℹ️ The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Legacy connectors do not support the functionality.
 
 ## Sending a partial invoice
 
@@ -54,9 +52,7 @@ To send a partial invoice through the VTEX Admin, follow the steps below:
 
 Once order changes have been made, you can view all the transaction events by clicking [See transaction details](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
 
-<div class = "alert alert-info">
-The same actions can also be done using our Orders API. To do so, check out these endpoints: <a href="https://developers.vtex.com/vtex-rest-api/reference/registerchange">Register Change on Order</a>, <a href="https://developers.vtex.com/vtex-rest-api/reference/invoicenotification">Invoice notification</a>, <a href="https://developers.vtex.com/vtex-rest-api/reference/getpaymenttransaction">Retrieve Payment transaction</a>, and <a href="https://developers.vtex.com/vtex-rest-api/reference/updatepartialinvoicesendtrackingnumber">Update order's partial invoice (send tracking number)</a>.
-</div>
+>ℹ️ The same actions can also be done using our Orders API. To do so, check out these endpoints: [Register Change on Order](https://developers.vtex.com/vtex-rest-api/reference/registerchange), [Invoice notification](https://developers.vtex.com/vtex-rest-api/reference/invoicenotification), [Retrieve Payment transaction](https://developers.vtex.com/vtex-rest-api/reference/getpaymenttransaction), and [Update order's partial invoice (send tracking number)](https://developers.vtex.com/vtex-rest-api/reference/updatepartialinvoicesendtrackingnumber).
 
 ## Learn more
 
diff --git a/docs/tracks/en/pre-go-live.md b/docs/tracks/en/pre-go-live.md
index 13848a7f1..874bd524c 100644
--- a/docs/tracks/en/pre-go-live.md
+++ b/docs/tracks/en/pre-go-live.md
@@ -28,9 +28,7 @@ If your storefront is powered by [CMS IO](https://help.vtex.com/en/tracks/cms--2
 
 After you receive the internal pointing confirmation, you must do the [common DNS pointing](https://help.vtex.com/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#setting-up-dns-pointing) within 5 days. Otherwise the internal pointing will be deleted and you will need to redo the request.
 
-<div class = "alert alert-info">
-Learn more at <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live">Go live with Store Framework</a> or <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migration from legacy CMS to Store Framework</a>.
-</div>
+>ℹ️ Learn more at [Go live with Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live) or [Migration from legacy CMS to Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 ## Requesting special pointing
 
diff --git a/docs/tracks/en/reports-vtex-intelligent-search.md b/docs/tracks/en/reports-vtex-intelligent-search.md
index f774d5b39..6880f807f 100644
--- a/docs/tracks/en/reports-vtex-intelligent-search.md
+++ b/docs/tracks/en/reports-vtex-intelligent-search.md
@@ -23,9 +23,7 @@ Follow the steps below to access the page:
 1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
 2. Under __Intelligent Search__, click __Analytics__. 
 
-<div class = "alert alert-info">
-  <p>The <b>Analytics</b> page is native to VTEX Intelligent Search. You cannot disable it in the Admin.</p>
-</div>
+>ℹ️ The **Analytics** page is native to VTEX Intelligent Search. You cannot disable it in the Admin.
 
 ## Data
 
@@ -71,9 +69,7 @@ To export a report in .csv format, you must follow the steps below:
 5. Wait until the file is available for download. Leaving this page will not interrupt the process.
 6. Click on `Download`.
 
-<div class = "alert alert-info">
-  <p>The file will be available for download for 48 hours.</p>
-</div>
+>ℹ️ The file will be available for download for 48 hours.
 
 The report (CSV file) you have downloaded contains two tables. The first table contains information about searched terms, as illustrated below. It also shows funnel metrics (from the **ProductsClick** column to the **ProductsSold** column) if you have selected this option.
 
diff --git a/docs/tracks/en/sending-products-to-google-shopping.md b/docs/tracks/en/sending-products-to-google-shopping.md
index d7d05ac56..77ab5a0dc 100644
--- a/docs/tracks/en/sending-products-to-google-shopping.md
+++ b/docs/tracks/en/sending-products-to-google-shopping.md
@@ -20,9 +20,7 @@ Only catalogs can be integrated with Google Shopping. Unlike other integrations,
 
 After integrating and authenticating your account, the marketplace does not automatically receive the products after integrating with the seller. First, the seller must [reindex the database](https://help.vtex.com/en/tutorial/entendendo-o-funcionamento-da-indexacao). This process prepares the SKU information and products and sends catalog, price, and stock general information to the marketplace.  
 
-<div class = "alert alert-info">
-Please note that only the <a href="https://help.vtex.com/en/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA">sponsor user (owner)</a> has permission to reindex a VTEX store database. During reindexing, which may vary in terms of time, the products are queued for updating the information, while still remaining available for sale on the store site. 
-</div>
+>ℹ️ Please note that only the [sponsor user (owner)](https://help.vtex.com/en/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA) has permission to reindex a VTEX store database. During reindexing, which may vary in terms of time, the products are queued for updating the information, while still remaining available for sale on the store site.
 
 To reindex the database, paste the link below in your browser, replacing the `{storename}` with the name of your store:
 
diff --git a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
index 902d2a7ef..f0038c9f2 100644
--- a/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tracks/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -121,9 +121,7 @@ Final URI that the payment app will receive to perform the refund action with th
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&sellerName=instoreqa&autoConfirm=True&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class = "alert alert-warning">
-<strong>NOTE:</strong> Not all parameters will be used by all payment acquirers/apps. Example: <code>transactionId</code>. This parameter is the ID of a transaction in VTEX that identifies all payments of a complete order on VTEX PCI Gateway. A transaction can contain multiple payments, such as when an order is paid with multiple credit or debit cards.
-</div>
+>⚠️ **NOTE:** Not all parameters will be used by all payment acquirers/apps. Example: `transactionId`. This parameter is the ID of a transaction in VTEX that identifies all payments of a complete order on VTEX PCI Gateway. A transaction can contain multiple payments, such as when an order is paid with multiple credit or debit cards.
 
 ## Examples of response URIs for each action
 
diff --git a/docs/tracks/en/settings.md b/docs/tracks/en/settings.md
index ff5bf6d59..a5d8f5593 100644
--- a/docs/tracks/en/settings.md
+++ b/docs/tracks/en/settings.md
@@ -44,16 +44,14 @@ Although not recommended, another alternative would be not including CAA records
 
 To easily create/verify your CAA records, you can use [CAA Record Helper by SSLMate](https://sslmate.com/caa/). The [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) program can also help you verify your records with the `dig domain.com CAA` command – a `SERVFAIL` status can indicate non-compliance of your DNS server.
 
-<div class = "alert alert-info">
-Learn more:
-<p>
-<ul>
-<li><a href="https://sslmate.com/caa/">CAA Record Helper by SSLMate</a></li>
-<li><a href="https://letsencrypt.org/docs/caa/">Let's Encrypt: Certificate Authority Authorization (CAA)</a></li>
-<li><a href="https://sslmate.com/caa/about">SSL Mate: About CAA</a></li>
-</ul>
-</p>
-</div>
+>ℹ️ Learn more:
+>
+> *[CAA Record Helper by SSLMate](https://sslmate.com/caa/)
+>
+> *[Let's Encrypt: Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)
+>
+> *[SSL Mate: About CAA](https://sslmate.com/caa/about)
+> 
 
 ## Putting your account into production
 
diff --git a/docs/tracks/en/shipping-costs-and-simulation.md b/docs/tracks/en/shipping-costs-and-simulation.md
index c09b84e56..a1018c6a2 100644
--- a/docs/tracks/en/shipping-costs-and-simulation.md
+++ b/docs/tracks/en/shipping-costs-and-simulation.md
@@ -42,6 +42,4 @@ To do this validation, you can use the [Shipping simulator](https://help.vtex.co
 * Whether there are pickup points available for that product.
 * Which [white label seller](https://help.vtex.com/en/tutorial/what-are-franchise-account-and-seller-white-label--5orlGHyDHGAYciQ64oEgKa) will deliver the product. 
 
-<div class = "alert alert-info">
-You can also simulate shipping options via the <a href="https://developers.vtex.com/vtex-rest-api/reference/calculatesla">SLA calculation API</a>. 
-</div>
+>ℹ️ You can also simulate shipping options via the [SLA calculation API](https://developers.vtex.com/vtex-rest-api/reference/calculatesla).
diff --git a/docs/tracks/en/shipping-strategies.md b/docs/tracks/en/shipping-strategies.md
index 1991aa52a..e1e39a4a5 100644
--- a/docs/tracks/en/shipping-strategies.md
+++ b/docs/tracks/en/shipping-strategies.md
@@ -26,9 +26,7 @@ The shipping strategy is defined by three logistics entities:
 * [Warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb): location where the items are stored. The shipping policy is not the only variable for choosing the delivery; it is also necessary to consider in which warehouse the products are stored.
 * [Loading dock](https://help.vtex.com/en/tutorial/loading-dock--5DY8xHEjOLYDVL41Urd5qj): location where items will be picked up. The stores use the loading dock to configure the collection of packages. The carriers pick up the packages from the loading docks.
 
-<div class = "alert alert-info">
-There are other possible scenarios for using loading docks. To learn about use cases, read the article Loading docks. To learn more about the flow of deliveries, see the article <a href="https://help.vtex.com/en/tutorial/como-funciona-o-fluxo-de-entregas--4ku3QKWfxmUO8UgA0yqgUq"> How does the delivery flow work</a>.
-</div>
+>ℹ️ There are other possible scenarios for using loading docks. To learn about use cases, read the article Loading docks. To learn more about the flow of deliveries, see the article [ How does the delivery flow work](https://help.vtex.com/en/tutorial/como-funciona-o-fluxo-de-entregas--4ku3QKWfxmUO8UgA0yqgUq).
 
 Please note that:
 
@@ -54,17 +52,15 @@ For cases where a store offers [pickup points](https://help.vtex.com/en/tutorial
 
 The pickup point is displayed at checkout as a shipping option. The customer can choose between **delivery** and **pickup**.
 
-<div class = "alert alert-info">
-The shipping strategy can also be configured via API. You can use the following APIs:
-<body>
-<ul>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/docks">Loading docks API</a>;
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse">Warehouses API</a>;
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/get_logistics-pvt-shipping-policies-id">Shipping policies API</a>;
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/listallpickupppoints">Pickup points API</a>.
-</ul>
-</body>
-</div>
+>ℹ️ The shipping strategy can also be configured via API. You can use the following APIs:
+> <body>
+>
+> <li>[Loading docks API](https://developers.vtex.com/vtex-rest-api/reference/docks);
+> <li>[Warehouses API](https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse);
+> <li>[Shipping policies API](https://developers.vtex.com/vtex-rest-api/reference/get_logistics-pvt-shipping-policies-id);
+> <li>[Pickup points API](https://developers.vtex.com/vtex-rest-api/reference/listallpickupppoints).
+>
+> </body>
 
 ### Configuration
 
@@ -104,7 +100,5 @@ To register holidays on the platform, you can:
 
 You can register delivery times for scheduled deliveries from carriers and pickup points. The **[Scheduled delivery](https://help.vtex.com/en/tutorial/scheduled-delivery--22g3HAVCGLFiU7xugShOBi)** feature allows stores to offer delivery windows to their customers.
 
-<div class = "alert alert-info">
-Shipping also depends on the <a href="https://help.vtex.com/en/tutorial/total-shipping-cost--5bwhIO108VA5Y2YOpef9lV">shipping cost</a> that your store offers to customers. This subject will be covered in the following articles. For more information about how carriers are chosen to for deliveries, read the article <a href="https://help.vtex.com/en/tutorial/hoy-shipping-calculation-works--tutorials_116"> How shipping is calculated</a>.
-</div>
+>ℹ️ Shipping also depends on the [shipping cost](https://help.vtex.com/en/tutorial/total-shipping-cost--5bwhIO108VA5Y2YOpef9lV) that your store offers to customers. This subject will be covered in the following articles. For more information about how carriers are chosen to for deliveries, read the article [ How shipping is calculated](https://help.vtex.com/en/tutorial/hoy-shipping-calculation-works--tutorials_116).
 
diff --git a/docs/tracks/en/synonyms.md b/docs/tracks/en/synonyms.md
index 71198545c..6e1b1a5e5 100644
--- a/docs/tracks/en/synonyms.md
+++ b/docs/tracks/en/synonyms.md
@@ -23,9 +23,7 @@ Synonyms also complement search reports without results. From this analysis, the
 Accordingly, VTEX Intelligent Search receives the term searched by the customer and searches for it in the synonym rules registered in its database. In case there is a rule, these words will be directed to the search within the catalog.
 This way, if there is a synonym rule, no matter how the customer searches or how the product name is registered, they will always find what they are looking for.
 
-<div class = "alert alert-warning">
-Synonyms should not be used to correct spelling, plural and singular errors or even pronouns, articles and prepositions errors in the searched terms. VTEX Intelligent Search can automatically interpret, learn and solve all these cases through algorithms.
-</div>
+>⚠️ Synonyms should not be used to correct spelling, plural and singular errors or even pronouns, articles and prepositions errors in the searched terms. VTEX Intelligent Search can automatically interpret, learn and solve all these cases through algorithms.
 
 ## Types of synonyms
 
diff --git a/docs/tracks/en/unified-search.md b/docs/tracks/en/unified-search.md
index 10c358cee..c53289345 100644
--- a/docs/tracks/en/unified-search.md
+++ b/docs/tracks/en/unified-search.md
@@ -16,9 +16,7 @@ trackSlugEN: instore-using-the-app
 
 VTEX Sales App's [endless aisle](https://help.vtex.com/en/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn) feature allows sales associates to search for products beyond the inventory of the current store and add them to the cart. To search for a product, click the magnifying glass icon <i class="fas fa-search"></i>, and a search bar will be displayed at the top of the store's homepage.  Enter the product name, reference code, SKU ID, or EAN.
 
-<div class = "alert alert-info">
-This feature uses the browser's cache to optimize searches in scenarios with slow internet connections.
-</div>
+>ℹ️ This feature uses the browser's cache to optimize searches in scenarios with slow internet connections.
 
 ![Barra busca - EN](https://images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/31aeb140714a23b6e5d0f958e90dcea2/Tela_1_barra_busca.gif)
 
diff --git a/docs/tracks/en/viewing-the-email-history-of-an-order.md b/docs/tracks/en/viewing-the-email-history-of-an-order.md
index 8efa1e2b2..577013cce 100644
--- a/docs/tracks/en/viewing-the-email-history-of-an-order.md
+++ b/docs/tracks/en/viewing-the-email-history-of-an-order.md
@@ -22,6 +22,4 @@ To see email history, go to the **Orders** module, enter the desired order and s
 
 This record is made by a system called __Conversation Tracker__. To get a deeper understanding of how it works, see our article on [communication with the client during the order flow](https://help.vtex.com/en/tutorial/understanding-the-conversation-tracker--tutorials_195).
 
-<div class = "alert alert-info">
-Since the communication with customers is a responsibility from marketplaces, only orders with marketplace origin keep a transactional emails history. Orders with fulfilllment origin do not keep a register of transactional emails.
-</div>
+>ℹ️ Since the communication with customers is a responsibility from marketplaces, only orders with marketplace origin keep a transactional emails history. Orders with fulfilllment origin do not keep a register of transactional emails.
diff --git a/docs/tracks/en/vtex-modules-ii.md b/docs/tracks/en/vtex-modules-ii.md
index d51734fea..b06e5cf56 100644
--- a/docs/tracks/en/vtex-modules-ii.md
+++ b/docs/tracks/en/vtex-modules-ii.md
@@ -71,9 +71,7 @@ Payment providers must be enabled in a store to transmit and receive the informa
 2. Select the desired provider by clicking the corresponding link in the table.
 3. Go to the VTEX Admin to configure the provider and follow the instructions listed in the specific configuration article.
 
-<div class = "alert alert-info">
-You can also find provider configuration articles by entering the name of the provider in the search bar of the <a href="https://help.vtex.com/en">Help Center</a>.
-</div>
+>ℹ️ You can also find provider configuration articles by entering the name of the provider in the search bar of the [Help Center](https://help.vtex.com/en).
 
 #### Defining payment methods and payment conditions
 
@@ -256,9 +254,7 @@ Learn more in [Optimization of shipping options at Checkout](https://help.vtex.c
 
 This feature allows sending emails to customers who have created a shopping cart but have not completed the purchase.
 
-<div class = "alert alert-info">
-Configuring the abandoned cart feature during the onboarding process allows forwarding all future carts for customer review, encouraging them to complete their purchases.
-</div>
+>ℹ️ Configuring the abandoned cart feature during the onboarding process allows forwarding all future carts for customer review, encouraging them to complete their purchases.
 
 Learn more in [Setting up Cart Abandonment](https://help.vtex.com/en/tutorial/configurar-carrinho-abandonado--tutorials_740).
 
diff --git a/docs/tracks/en/what-features-does-the-integration-offer.md b/docs/tracks/en/what-features-does-the-integration-offer.md
index ae7a72752..cf398e71e 100644
--- a/docs/tracks/en/what-features-does-the-integration-offer.md
+++ b/docs/tracks/en/what-features-does-the-integration-offer.md
@@ -14,6 +14,4 @@ trackId: 2YfvI3Jxe0CGIKoWIGQEIq
 trackSlugEN: what-features-does-the-integration-offer
 ---
 
-<div class= "alert alert-warning">
-This is a regional exclusive content not applicable to English speaking countries.
-</div>
+>⚠️ This is a regional exclusive content not applicable to English speaking countries.
diff --git a/docs/tracks/en/what-is-the-master-user.md b/docs/tracks/en/what-is-the-master-user.md
index 743f74187..8203be4b1 100644
--- a/docs/tracks/en/what-is-the-master-user.md
+++ b/docs/tracks/en/what-is-the-master-user.md
@@ -18,9 +18,7 @@ For the VTEX platform, the **Sponsor user** is the user who is primarily respons
 
 By default, the Sponsor user email is the one of the person who was responsible for hiring VTEX. But after receiving the VTEX environment, it can exchanged by the Sponsor user.
 
-<div class = "alert alert-warning">
-The Sponsor user is not the same as the <b>Owner (Admin Super)</b>. The <b>Owner (Admin Super)</b> is a License Manager role that defines the permissions of a user in your store. It can even be assigned to multiple users.
-</div>
+>⚠️ The Sponsor user is not the same as the **Owner (Admin Super)**. The **Owner (Admin Super)** is a License Manager role that defines the permissions of a user in your store. It can even be assigned to multiple users.
 
 If your user has role to the Account management module, you can verify who is the Sponsor user by accessing the __Accounts__ tab and searching for the name of the store.
 
diff --git a/docs/tracks/es/accounts-and-architecture.md b/docs/tracks/es/accounts-and-architecture.md
index 5bb0c8907..5d3d0483c 100644
--- a/docs/tracks/es/accounts-and-architecture.md
+++ b/docs/tracks/es/accounts-and-architecture.md
@@ -125,7 +125,5 @@ Es común que agencias y [partners de implementación ](https://vtex.com/mx-es/p
 
 El [Cuadrante VTEX](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) es un programa en que VTEX evalúa internamente el rendimiento y los resultados de éxito de operación de sus partners. Es una forma de reconocer y recompensar anualmente a los partners que demuestren el máximo nivel de entrega y excelencia. [Aquí](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) puedes ver el resultado del Cuadrante VTEX 2023.
 
-<div class = "alert alert-info">
-El <a href="https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/">Cuadrante VTEX</a> es un programa exclusivo para partners de implementación en Brasil.
-</div>
+>ℹ️ El [Cuadrante VTEX](https://vtex.com/pt-br/blog/parceiros/quadrante_vtex_2023/) es un programa exclusivo para partners de implementación en Brasil.
 
diff --git a/docs/tracks/es/add-on-products.md b/docs/tracks/es/add-on-products.md
index 4854364af..6e94bdf39 100644
--- a/docs/tracks/es/add-on-products.md
+++ b/docs/tracks/es/add-on-products.md
@@ -127,6 +127,4 @@ Los principales beneficios de la funcionalidad son:
 
 **Aumento de las tasas de conversión y ventas:** incentiva a los clientes a volver a la página de checkout para finalizar su compra, aumentando así las ventas y las tasas de conversión de los retailers.
 
-<div class = "alert alert-info">
-WhatsApp AI Campaigns solamente está disponible para tiendas que utilizan <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> y no tienen personalizaciones en Checkout.
-</div>
+>ℹ️ WhatsApp AI Campaigns solamente está disponible para tiendas que utilizan [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) y no tienen personalizaciones en Checkout.
diff --git a/docs/tracks/es/adding-collections-track.md b/docs/tracks/es/adding-collections-track.md
index 0770377df..fab0db39e 100644
--- a/docs/tracks/es/adding-collections-track.md
+++ b/docs/tracks/es/adding-collections-track.md
@@ -14,9 +14,7 @@ trackId: 5AF0XfnjfWeopIFBgs3LIQ
 trackSlugES: catalogo-101
 ---
 
-<div class = "alert alert-warning">
-  <p>Antes de crear una colección, es necesario haber configurado la autorización. Para eso, debe tener un perfil de acceso con el recurso <b>Write Collections</b>, en la sección <b>Collection</b> de los perfiles de Catalog. Vea <a href="https://help.vtex.com/es/tutorial/perfiles-de-acceso--7HKK5Uau2H6wxE1rH5oRbc">aquí</a> cómo configurar un recurso.</p>
-</div>
+>⚠️ Antes de crear una colección, es necesario haber configurado la autorización. Para eso, debe tener un perfil de acceso con el recurso **Write Collections**, en la sección **Collection** de los perfiles de Catalog. Vea [aquí](https://help.vtex.com/es/tutorial/perfiles-de-acceso--7HKK5Uau2H6wxE1rH5oRbc) cómo configurar un recurso.
 
 Realice el siguiente paso a paso para registrar una nueva colección:
 
diff --git a/docs/tracks/es/adding-new-stores-to-instore.md b/docs/tracks/es/adding-new-stores-to-instore.md
index ffce7a9ad..ce7bd73e3 100644
--- a/docs/tracks/es/adding-new-stores-to-instore.md
+++ b/docs/tracks/es/adding-new-stores-to-instore.md
@@ -74,9 +74,7 @@ Puedes crear una tienda física siguiendo los pasos a continuación:
 * **Política comercial:** [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será aplicada na loja física. Campo obrigatório.
 * **Punto de recogida:** [punto de recogida](https://help.vtex.com/es/tutorial/puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R) registrado para esta tienda física, donde los clientes recogen sus pedidos.
 
-<div class ="alert alert-info">
-<p>Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en inStore.</p> 
-</div>
+>ℹ️ Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en inStore.
 
 ## Buscar tienda física
 
diff --git a/docs/tracks/es/allowing-order-replacement.md b/docs/tracks/es/allowing-order-replacement.md
index b20af354e..2eb6a36dc 100644
--- a/docs/tracks/es/allowing-order-replacement.md
+++ b/docs/tracks/es/allowing-order-replacement.md
@@ -18,9 +18,7 @@ La **Sustitución de pedidos** permite a los clientes de su tienda cambiar los d
 
 El objetivo es ayudarlos a corregir errores sin tener que realizar manualmente un nuevo pedido o contactar a su soporte, lo que facilita el funcionamiento de su tienda y reduce costos.
 
-<div class = "alert alert-warning">
-No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
-</div>
+>⚠️ No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Habilitación de la sustitución de pedidos
 
@@ -32,7 +30,5 @@ La funcionalidad está disponible para todas las tiendas. Para habilitarla, sigu
 
 Dentro de 15 minutos, después de la actualización automática de caché, la funcionalidad estará disponible.
 
-<div class = "alert alert-info">
-Para más información sobre la funcionalidad y asos que no permiten la sustitución, vea el artículo <a href="https://help.vtex.com/es/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8">Cambio de pedido</a>.
-</div>
+>ℹ️ Para más información sobre la funcionalidad y asos que no permiten la sustitución, vea el artículo [Cambio de pedido](https://help.vtex.com/es/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8).
 
diff --git a/docs/tracks/es/autocomplete-search.md b/docs/tracks/es/autocomplete-search.md
index d3cd7aaa4..112c4f342 100644
--- a/docs/tracks/es/autocomplete-search.md
+++ b/docs/tracks/es/autocomplete-search.md
@@ -15,9 +15,7 @@ trackSlugES: vtex-intelligent-search
 ---
 
 
-<div class = "alert alert-warning">
-    Autocomplete es una herramienta que ya está activa en VTEX Intelligent Search. No es posible desactivarla en el Admin.
-    </div>
+>⚠️ Autocomplete es una herramienta que ya está activa en VTEX Intelligent Search. No es posible desactivarla en el Admin.
 
 Autocomplete funciona según la información obtenida a través del historial de búsqueda de términos relacionados con el Catálogo. Estos resultados se muestran en cuatro listas diferentes, que pueden estar juntas o separadas, dependiendo de la interacción con el cliente. Las secciones son:
 
@@ -35,19 +33,14 @@ Durante la interacción con la barra de búsqueda, VTEX Intelligent Search inmed
 
 Cuando el usuario comienza a escribir, el sistema muestra las Sugerencias de búsqueda y Sugerencias de productos y elimina las listas anteriores.
 
-<div class = "alert alert-info">
-  <p>La información de las secciones <b>Términos más buscados</b> y <b>Sugerencia de búsquedas</b> es actualizada diariamente. Para la actualización, se utilizan los datos de los últimos 14 días de interacción de los clientes con la búsqueda.</p>
-  </div>
+>ℹ️ La información de las secciones **Términos más buscados** y **Sugerencia de búsquedas** es actualizada diariamente. Para la actualización, se utilizan los datos de los últimos 14 días de interacción de los clientes con la búsqueda.
 
 De esta forma, es posible proporcionar al cliente una experiencia de búsqueda más fluida y personalizada. Así puede ver el resultado rápidamente, además de recibir sugerencias basadas en su búsqueda. 
 
 Otra ventaja para el administrador de la tienda es el aumento de conversión, que es el resultado de la dinámica de facilidad de uso y experiencia.
 
-<div class = "alert alert-info">
-  <p>Autocomplete ofrece sugerencias de búsqueda incluso cuando la tienda es nueva y aún no muestra datos de interacciones con los clientes, como clics y búsquedas.
-    En este caso, la funcionalidad genera sugerencias de búsqueda a partir de un algoritmo que extrae palabras clave del catálogo, productos, marcas y categorías registradas en la tienda.
-</p>
-  </div>
+>ℹ️ Autocomplete ofrece sugerencias de búsqueda incluso cuando la tienda es nueva y aún no muestra datos de interacciones con los clientes, como clics y búsquedas.
+>     En este caso, la funcionalidad genera sugerencias de búsqueda a partir de un algoritmo que extrae palabras clave del catálogo, productos, marcas y categorías registradas en la tienda.
 
 ## Términos más buscados
 
diff --git a/docs/tracks/es/backend-integrations.md b/docs/tracks/es/backend-integrations.md
index bde641cbf..281bd23ff 100644
--- a/docs/tracks/es/backend-integrations.md
+++ b/docs/tracks/es/backend-integrations.md
@@ -180,9 +180,7 @@ En VTEX, es importante entender la distinción entre productos y SKU:
 - [Producto](https://help.vtex.com/es/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru): unidad abstracta del catálogo, visible en los estantes de la tienda.
 - [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA): unidad concreta del catálogo en el stock que representa las variaciones específicas de un producto, como color, tamaño y otros atributos. Los SKU se muestran como ítems individuales en las páginas de los productos.
 
-<div class = "alert alert-info">
-La manera en que se estructuran los productos y SKU afectan directamente la experiencia de compra de los clientes.
-</div>
+>ℹ️ La manera en que se estructuran los productos y SKU afectan directamente la experiencia de compra de los clientes.
 
 La importación de productos debe seguir el orden descrito en la tabla a continuación:
 
@@ -262,9 +260,7 @@ Existen dos formas dar seguimiento a los cambios de status de los pedidos en VTE
 
 Los dos tipos de integración permiten aplicar [filtros](https://developers.vtex.com/docs/guides/orders-feed#filter) para seleccionar los tipos de eventos que el sistema de back office debe procesar.
 
-<div class = "alert alert-info">
-En la mayoría de los casos, VTEX recomienda integrar los pedidos con <a href="https://developers.vtex.com/docs/guides/orders-feed">Feed v3</a> porque es un método más robusto.
-</div>
+>ℹ️ En la mayoría de los casos, VTEX recomienda integrar los pedidos con [Feed v3](https://developers.vtex.com/docs/guides/orders-feed) porque es un método más robusto.
 
 #### Obtener detalles del pedido
 
@@ -392,9 +388,7 @@ Si no encuentras una aplicación que satisfaga las necesidades de tu tienda VTEX
 
   d. **(Opcional) Validar que la aplicación satisfaga la necesidad de negocio:** después de tener la versión publicada, podría ser beneficioso instalar la aplicación en un [workspace de producción](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace) y realizar una [prueba A/B](https://developers.vtex.com/docs/guides/ab-tests) para comparar la tasa de conversión de las ventas con la nueva aplicación. 
 
-<div class = "alert alert-info">
-Si deseas saber más sobre el desarrollo de aplicaciones, accede a nuestro <a href="https://learn.vtex.com/">Learning Center</a>.
-</div>
+>ℹ️ Si deseas saber más sobre el desarrollo de aplicaciones, accede a nuestro [Learning Center](https://learn.vtex.com/).
 
 - **¿Deseas que la aplicación sea pública?** Puedes [disponibilizar](https://developers.vtex.com/docs/guides/vtex-io-documentation-making-your-new-app-version-publicly-available) la aplicación en la App Store para permitir que otras cuentas puedan aprovechar la solución desarrollada.
 - **¿Deseas que la aplicación esté disponible en la App Store?** Disponibilizar la aplicación en la App Store tiene varias ventajas, como aumentar la visibilidad de la aplicación y la posibilidad de [monetizarla](https://developers.vtex.com/docs/guides/vtex-io-documentation-setting-your-apps-billing-model) siguiendo algunos pasos y reglas. En resumen, debes ser un [desarrollador registrado](https://developers.vtex.com/docs/guides/vtex-io-documentation-becoming-a-registered-vtex-app-store-developer), tener el código de la aplicación almacenado en un repositorio de [GitHub](https://github.com/), desarrollar la aplicación siguiendo las [mejores prácticas de la App Store](https://developers.vtex.com/docs/guides/vtex-io-documentation-homologation-requirements-for-vtex-app-store) y [enviarla](https://developers.vtex.com/docs/guides/vtex-io-documentation-submitting-your-app-in-the-vtex-app-store) al proceso de homologación. Tras el proceso de homologación, la aplicación estará disponible en la App Store.
diff --git a/docs/tracks/es/billing-support.md b/docs/tracks/es/billing-support.md
index 74adce2ec..f687eac0b 100644
--- a/docs/tracks/es/billing-support.md
+++ b/docs/tracks/es/billing-support.md
@@ -25,9 +25,7 @@ VTEX tiene como objetivo garantizar el cumplimiento de los procedimientos y pol
 - [Cuentas por pagar - Brasil](https://help.vtex.com/pt/tutorial/contas-a-pagar-brasil--tutorials_660): prácticas a seguir para todos los pagos a proveedores relacionados con los procedimientos de cuentas por pagar de las sucursales de VTEX en Brasil.
 - [Cuentas por pagar - Internacional](https://help.vtex.com/es/tutorial/cuentas-por-pagar-internacional--3yea9sIlsA0KgUC28ASCGs): prácticas a seguir para todos los pagos a proveedores relacionados con los procedimientos de cuentas por pagar de las sucursales de VTEX a excepción de Brasil.
 
-<div class = "alert alert-info">
-Para consultar la lista de sucursales VTEX en todo el mundo y saber en qué país se emiten facturas, consulta el artículo <a href="https://help.vtex.com/es/tutorial/nombres-de-las-sucursales-vtex-en-el-mundo--zg05n6OIOZOEmLW7dcq9z"> País de facturación de la tienda. </a>
-</div>
+>ℹ️ Para consultar la lista de sucursales VTEX en todo el mundo y saber en qué país se emiten facturas, consulta el artículo [ País de facturación de la tienda. ](https://help.vtex.com/es/tutorial/nombres-de-las-sucursales-vtex-en-el-mundo--zg05n6OIOZOEmLW7dcq9z)
 
 ## Cálculo de los ingresos por facturación por VTEX
 
@@ -47,7 +45,5 @@ Tras el primer acceso, es posible modificar los datos registrados de la tienda,
 
 Para realizar estas modificaciones es necesario [abrir un ticket de soporte financiero](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM#financiero), especificando el tipo de modificación requerida.
 
-<div class = "alert alert-info">
-Para obtener más información sobre cómo solicitar una evaluación de SLA y los descuentos concedidos por infracciones de SLA, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-solicitar-la-verificacion-de-sla--3L99VeoLhYEwMqqkWKu86i"> Cómo solicitar la verificación de SLA de operación de la plataforma. </a>
-</div>
+>ℹ️ Para obtener más información sobre cómo solicitar una evaluación de SLA y los descuentos concedidos por infracciones de SLA, consulta el artículo [ Cómo solicitar la verificación de SLA de operación de la plataforma. ](https://help.vtex.com/es/tutorial/como-solicitar-la-verificacion-de-sla--3L99VeoLhYEwMqqkWKu86i)
 
diff --git a/docs/tracks/es/canceling-an-order.md b/docs/tracks/es/canceling-an-order.md
index cfae8fee4..0cb86d8cb 100644
--- a/docs/tracks/es/canceling-an-order.md
+++ b/docs/tracks/es/canceling-an-order.md
@@ -21,9 +21,7 @@ Usted puede cancelar un pedido con VTEX de tres maneras diferentes:
 
 >⚠️ Una vez cancelado el pedido, no se puede cambiar su status. Es posible cancelar el pedido hasta antes de **Facturado**, después el pedido no puede ser modificado.
 
-<div class = "alert alert-info">
-No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
-</div>
+>ℹ️ No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Cancelación por el módulo Pedidos
 
diff --git a/docs/tracks/es/configuring-synonyms.md b/docs/tracks/es/configuring-synonyms.md
index 61cd61a35..08a40c1ea 100644
--- a/docs/tracks/es/configuring-synonyms.md
+++ b/docs/tracks/es/configuring-synonyms.md
@@ -14,7 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugES: vtex-intelligent-search
 ---
 
-<div class = "alert alert-info"> Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ">Sinónimos</a> en lugar de <a href="https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palabras sustitutas</a> para asociar palabras con productos, ya que los sinónimos permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>. </div>
+>ℹ️ Recomendamos usar [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ) en lugar de [Palabras sustitutas](https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete) para asociar palabras con productos, ya que los sinónimos permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con [nuestro equipo de soporte](https://support.vtex.com/hc/es/requests).
 
 Hay dos formas de configurar sinónimos en VTEX Admin: [individualmente](#crear-sinonimos-individualmente) o [importando una hoja de cálculo en formato CSV](#). Si necesita registrar sinónimos en bloque, le recomendamos que utilice la hoja de cálculo. Consulte las instrucciones para cada método de configuración en las secciones siguientes.
 
diff --git a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index e580c518d..12e972c6d 100644
--- a/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/es/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -22,9 +22,7 @@ Para iniciar la configuración de la integración, realiza los siguientes pasos:
 2. Por estándar, los campos sobre la **región y la moneda**, así como la **URL** de tu tienda VTEX, estarán rellenados. Revisa la información y realiza cambios si es necesario.
 3. Mantén activada la opción _Habilitar la integración de Píxel_, a menos que tengas una implementación personalizada de Facebook Pixel. 
 
-  <div class = "alert alert-info">
-Independientemente de que tengas instalada la <a href= "https://apps.vtex.com/vtex-facebook-pixel/p">aplicación de Facebook Pixel</a>, se recomienda que la opción <b>Habilitar la integración de Píxel</b> permanezca activada. La excepción es cuando ya utilizas Google Tag Manager. Obtén más información en <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D/434Z1iWnaa0zbOMDyr6oi#pixel-de-facebook">Píxel de Facebook </a>.
-</div>
+  >ℹ️ Independientemente de que tengas instalada la <a href= "https://apps.vtex.com/vtex-facebook-pixel/p">aplicación de Facebook Pixel</a>, se recomienda que la opción **Habilitar la integración de Píxel** permanezca activada. La excepción es cuando ya utilizas Google Tag Manager. Obtén más información en <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D/434Z1iWnaa0zbOMDyr6oi#pixel-de-facebook">Píxel de Facebook </a>.
 
 4. Haz clic en `CONTINUAR CON FACEBOOK`.
 5. En la siguiente pantalla, se te pedirá tu cuenta de Facebook. Rellena tus datos y haz clic en `Entrar`. Si tienes configurada la [integración con Facebook](https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc), tus datos ya estarán guardados.
diff --git a/docs/tracks/es/create-the-category-tree.md b/docs/tracks/es/create-the-category-tree.md
index 6adaab3bb..4b2b14d08 100644
--- a/docs/tracks/es/create-the-category-tree.md
+++ b/docs/tracks/es/create-the-category-tree.md
@@ -42,15 +42,11 @@ __OBS__: la nomenclatura __Departamento / Categoría / Subcategoría__ es solame
 
 Pero atención:
 
-<div class = "alert alert-warning">
-Recomendamos que se creen <strong>como máximo 3 niveles de categoría</strong>. Más niveles pueden hacer que la operación de su catálogo sea demasiado compleja.
-</div>
+>⚠️ Recomendamos que se creen **como máximo 3 niveles de categoría**. Más niveles pueden hacer que la operación de su catálogo sea demasiado compleja.
 
 Dos puntos fundamentales:
 
 - ¿Quién planea la distribución de las categorías de su sitio? __Usted! Esta planificación debe reflejar los objetivos de su negocio.__
 - ¿Cuándo debe definirse la distribución de las categorías? __Antes que las categorías se insertan en la plataforma.__
 
-<div class = "alert alert-warning">
-Es muy importante que su equipo defina la composición del árbol de categorías <strong>antes</strong> de montarla en la plataforma. Después de que usted comienza a insertar productos, necesitar mover las categorías puede convertirse en un problema de estructuración complejo.
-</div>
+>⚠️ Es muy importante que su equipo defina la composición del árbol de categorías **antes** de montarla en la plataforma. Después de que usted comienza a insertar productos, necesitar mover las categorías puede convertirse en un problema de estructuración complejo.
diff --git a/docs/tracks/es/creating-regular-promotions.md b/docs/tracks/es/creating-regular-promotions.md
index b664cd6a0..949b175a7 100644
--- a/docs/tracks/es/creating-regular-promotions.md
+++ b/docs/tracks/es/creating-regular-promotions.md
@@ -61,9 +61,7 @@ En esta sección, debes configurar la información general de la promoción. Los
     - **Envío máximo:** el valor máximo del envío.
     - **Envío gratis:** el descuento total sobre el valor del envío.
     - **Regalo:** el descuento total sobre el valor del producto definido como regalo. Seleccionando esta opción podrás indicar el SKU (por nombre o ID) que se considerará como regalo, elegir si debe activarse el [multiplicador de regalo](https://help.vtex.com/es/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK) y la cantidad máxima de productos que se pueden utilizar como regalos en la promoción.
-<div class = "alert alert-info">
-El producto de regalo también debe tener un precio registrado aunque se ofrezca gratuitamente al cliente.
-</div>
+>ℹ️ El producto de regalo también debe tener un precio registrado aunque se ofrezca gratuitamente al cliente.
 
    - **Descuento nominal basado en fórmula:** el descuento se calcula con base en una fórmula que se puede crear utilizando como variables la suma de los precios de los productos, el envío y la cantidad de ítems. Ten en cuenta que el envío considerado por la fórmula será el envío de menor costo disponible para el pedido, independientemente de la selección del cliente. El separador decimal debe ser siempre el punto. Ejemplo: si el descuento es 30 % del valor total del producto + el valor del envío, la fórmula debe ser (total + freight) * 0.3. Para más información, consulta la [documentación de la fórmula](https://help.vtex.com/es/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
    - **Valor de recompensa nominal:** el crédito que será añadido al programa de fidelidad de la tienda. Para más información, consulta [Promoción regular con valor de fidelidad](https://help.vtex.com/es/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR).
@@ -72,9 +70,7 @@ El producto de regalo también debe tener un precio registrado aunque se ofrezca
  - **Información adicional (opcional):** permite incluir en la promoción información adicional compuesta de un nombre y un valor.
  - **Promoción resaltada:** inserta un flag con el nombre de la promoción utilizada en la vitrina y en la página del producto. El flag solo se inserta si se utiliza el control de visualización de promociones correcto en la plantilla: `<vtex.cmc:discountHightLight/>`.
 
-<div class = "alert alert-info">
-Las promociones nominales solo se muestran en el carrito, no en la vitrina o la página del producto.
-</div>
+>ℹ️ Las promociones nominales solo se muestran en el carrito, no en la vitrina o la página del producto.
 
 ## Restringir esta promoción a los productos de los sellers
 
@@ -85,9 +81,7 @@ En esta sección se pueden definir los sellers a los que se aplicará la promoci
 
 Para que la promoción sea válida para todos los sellers, deja la selección sin marcar.
 
-<div class = "alert alert-warning">
-  <p>No es posible seleccionar directamente un <em>seller white label</em>. Para incluir a un <em>seller white label</em> en la promoción, tiene dos opciones:</p><ol>1. Restringir a los <em>sellers</em> a la tienda principal. Esta restricción agrega a todos los <em>sellers white label</em> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <em>sellers</em>. Aquí, todos los tipos de <em>sellers</em>, <em>white label</em> o no, se agregarán a la promoción.</ol>
-</div>
+>⚠️ No es posible seleccionar directamente un *seller white label*. Para incluir a un *seller white label* en la promoción, tiene dos opciones:1. Restringir a los *sellers* a la tienda principal. Esta restricción agrega a todos los *sellers white label* de su tienda a la promoción.2. Dejar la selección sin marcar para incluir a todos los *sellers*. Aquí, todos los tipos de *sellers*, *white label* o no, se agregarán a la promoción.
 
 ## Política comercial
 
@@ -130,10 +124,8 @@ El pedido del cliente debe cumplir las condiciones registradas en esta sección
 - **Método de envío:** el descuento se concederá si el tipo de envío seleccionado por el cliente es el mismo que el registrado en la promoción. Este criterio solamente se considerará si el efecto de la promoción está relacionado con el valor de envío, es decir, si el tipo de la promoción es Envío porcentual, Envío nominal, Envío máximo o Envío gratis. Ten en cuenta que esta configuración no se puede combinar con la opción "Aplicar el descuento solo a la opción de envío más barata".
 - **Aplicar el descuento solo cuando el cliente seleccione una de las transportadoras anteriores:** la promoción se aplicará solo después de que el cliente seleccione la forma de entrega en cuestión. Mientras no se seleccione, no tendrá descuento. Este criterio solo se tendrá en cuenta si el tipo de promoción está relacionado con el valor del envío, es decir, solo si el tipo es Envío porcentual, Envío nominal, Envío máximo o Envío gratis.
 - **Medio de pago:** permite elegir si la promoción se aplicará a uno o varios de los medios de pago seleccionados.
-<div class = "alert alert-info">
-El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con nuestro equipo de soporte <a href="https://support.vtex.com/hc/pt-br/requests">.
-técnica</a>.</p>.
-</div>
+>ℹ️ El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con nuestro equipo de soporte <a href="https://support.vtex.com/hc/pt-br/requests">.
+> técnica</a>.</p>.
 
 - **Número de cuotas:** el descuento se concederá si la cantidad de cuotas seleccionada por el cliente está en el intervalo registrado. Este campo no se aplica a la selección de boleto.
 
@@ -144,9 +136,7 @@ técnica</a>.</p>.
 - **Crear un nuevo cupón con los UTM anteriores:** crea un cupón a partir de los UTM registrados para que el cliente tenga acceso a esta promoción solo con el código del cupón.
 - **utmi_cp:** el descuento se concederá si la navegación se realiza con el utmi_cp con el valor registrado (distingue entre mayúsculas y minúsculas).
 
-<div class = "alert alert-info">
-En el campo de UTM, ingresa únicamente el valor que deberán asumir los UTM para activar la promoción. No es necesario ingresar ?utm_source= dentro del campo.
-</div>
+>ℹ️ En el campo de UTM, ingresa únicamente el valor que deberán asumir los UTM para activar la promoción. No es necesario ingresar ?utm_source= dentro del campo.
 
 - **Solo en la primera compra:** el descuento solo se concederá en la primera compra del cliente.
 - **¿Se debe aplicar el descuento incluso si el usuario no tiene sesión iniciada?:** este campo se muestra cuando se selecciona la opción Solo en la primera compra. Si se marca esta opción, la promoción se aplicará aun cuando el cliente no ingrese su email y contraseña. Por otro lado, si no se selecciona, la promoción solo se aplicará si el consumidor ingresó con su email y contraseña previamente registrados.
diff --git a/docs/tracks/es/enabling-product-recommendations.md b/docs/tracks/es/enabling-product-recommendations.md
index b99c903d0..75f9436b7 100644
--- a/docs/tracks/es/enabling-product-recommendations.md
+++ b/docs/tracks/es/enabling-product-recommendations.md
@@ -14,9 +14,7 @@ trackId: 1z9kBm12oBPyVNDo1ivVc2
 trackSlugES: habilitar-recomendacion-de-producto
 ---
 
-<div class = "alert alert-danger">
-El cambio en la configuración de recomendaciones de productos en inStore, explicado en este artículo, implica cambiar los archivos <code>checkout-instore-custom.js</code> y <code>checkout-instore-custom.css</code>. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en estos archivos pueden causar errores críticos.
-</div>
+>❗ El cambio en la configuración de recomendaciones de productos en inStore, explicado en este artículo, implica cambiar los archivos `checkout-instore-custom.js` y `checkout-instore-custom.css`. Esta operación solo debe ser realizada por personas con experiencia en programación. Cambios incorrectos en estos archivos pueden causar errores críticos.
 
 Por defecto, inStore muestra una lista de productos sugeridos al vendedor en dos etapas del pedido:
 - En el carrito
diff --git a/docs/tracks/es/facebook-business-extension.md b/docs/tracks/es/facebook-business-extension.md
index eac705f06..f63994635 100644
--- a/docs/tracks/es/facebook-business-extension.md
+++ b/docs/tracks/es/facebook-business-extension.md
@@ -51,6 +51,4 @@ La API de Conversiones está diseñada para crear una conexión directa entre tu
 - Mejora de la medición de los datos de _marketing_.
 - Mayor control sobre los datos.
 
-<div class = "alert alert-info">
-Descubre más en la documentación de Facebook <a href= "https://www.facebook.com/business/help/2041148702652965?locale=es_LA">Información sobre la API de Conversiones</a>.
-</div>
+>ℹ️ Descubre más en la documentación de Facebook <a href= "https://www.facebook.com/business/help/2041148702652965?locale=es_LA">Información sobre la API de Conversiones</a>.
diff --git a/docs/tracks/es/facebook.md b/docs/tracks/es/facebook.md
index e9ce00e89..28ee7498b 100644
--- a/docs/tracks/es/facebook.md
+++ b/docs/tracks/es/facebook.md
@@ -14,9 +14,7 @@ trackId: 7h8KvIC4DbRRc8VlyJ8PFc
 trackSlugES: integracion-de-facebook
 ---
 
-<div class = "alert alert-info">
-Hay una integración con la aplicación <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D">Facebook Business Extension y Conversions API</a> que debe ser tu selección predeterminada con Facebook. Esto es válido inclusive para los que ya realizaron la <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Integración de Facebook</a>, ya que la integración con la aplicación garantiza las funcionalidades anteriores y otras, como la API de conversiones y píxel de Facebook.
-</div>
+>ℹ️ Hay una integración con la aplicación <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D">Facebook Business Extension y Conversions API</a> que debe ser tu selección predeterminada con Facebook. Esto es válido inclusive para los que ya realizaron la <a href= "https://help.vtex.com/es/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Integración de Facebook</a>, ya que la integración con la aplicación garantiza las funcionalidades anteriores y otras, como la API de conversiones y píxel de Facebook.
 
 [Facebook](https://about.fb.com/ltam/) es la red social con el mayor número de usuarios en el mundo. Creada en 2004, es la plataforma a través de la cual más de tres mil millones de personas se conectan y comparten información todos los días.
 
diff --git a/docs/tracks/es/frontend-implementation.md b/docs/tracks/es/frontend-implementation.md
index 586fc5346..2b0bf9f48 100644
--- a/docs/tracks/es/frontend-implementation.md
+++ b/docs/tracks/es/frontend-implementation.md
@@ -24,9 +24,7 @@ El propósito de este artículo es brindar orientación en la elección de la te
 
 La implementación del frontend es una etapa centrada en la definición de las tecnologías a implementar, en función de las necesidades del negocio relacionadas con el storefront.
 
-<div class = "alert alert-info">
-El frontend puede ser implementado tanto por el equipo de desarrollo interno de la empresa como por nuestros <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion">partners de implementación</a>. <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512">Los usuarios</a> con acceso al Admin VTEX pueden consultar la lista de nuestros partners a través del <a href="https://partnerportal.vtex.com/">Partner Portal</a> (exclusivo Brasil).
-</div>
+>ℹ️ El frontend puede ser implementado tanto por el equipo de desarrollo interno de la empresa como por nuestros [partners de implementación](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#partners-de-implementacion). [Los usuarios](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512) con acceso al Admin VTEX pueden consultar la lista de nuestros partners a través del [Partner Portal](https://partnerportal.vtex.com/) (exclusivo Brasil).
 
 ## Antes de empezar
 
@@ -39,9 +37,7 @@ Antes de empezar a implementar el frontend, se recomienda que la tienda complete
 | Configuración del catálogo | El equipo configura el [catálogo](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) con los productos, el árbol de categorías y la información relacionada, como descripciones, imágenes y precios, para completar y probar la tienda, incluyendo recursos como las páginas de lista de productos (PLP), funcionalidad de búsqueda, las páginas de detalles de producto (PDP) y checkout.<br><br>La falta de catálogo puede resultar en pruebas incompletas y problemas en la integración de datos, lo que retrasa la implementación.<br><br>Más información en el artículo [Módulos de VTEX I](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7). |
 | Definición de las aplicaciones necesarias para la operación de la tienda | El equipo define las aplicaciones, tanto nativas como de terceros, necesarias para la operación de la tienda.<br><br>Hay una lista de aplicaciones nativas y de terceros para tiendas que se construyan usando [Store Framework](#store-framework).<br><br>Más información en el artículo [VTEX IO Apps](https://developers.vtex.com/docs/vtex-io-apps). |
 
-<div class = "alert alert-info">
-La <a href="#fases-de-desarrollo">fase de desarrollo</a> puede llevarse a cabo simultáneamente con otras fases de las <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">integraciones de backend</a> y <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7">configuración de módulos</a>, como por ejemplo, la configuración de medios de pago y ajustes logísticos. Esto va a depender del tipo de <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitectura y planificación</a> elegida para la tienda VTEX y deberá ir acompañado de la <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6ylpartners-de-implementacion">agencia implementadora</a> o del <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">soporte VTEX</a>.
-</div>
+>ℹ️ La [fase de desarrollo](#fases-de-desarrollo) puede llevarse a cabo simultáneamente con otras fases de las [integraciones de backend](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) y [configuración de módulos](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), como por ejemplo, la configuración de medios de pago y ajustes logísticos. Esto va a depender del tipo de [arquitectura y planificación](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) elegida para la tienda VTEX y deberá ir acompañado de la [agencia implementadora](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6ylpartners-de-implementacion) o del [soporte VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8).
 
 ## Tecnologías de desarrollo de frontend de VTEX
 
@@ -118,9 +114,7 @@ Store Framework es una opción más madura, que ofrece una estructura flexible a
 
 FastStore es una alternativa más reciente en proceso de evolución, enfocada en el desempeño de la tienda. Esta solución ofrece una experiencia de carga rápida, que es esencial para mantener el interés de los visitantes de la tienda y reducir las tasas de abandono de carrito. FastStore es la tecnología más recomendada para casos de uso más simples enfocados en desempeño.
 
-<div class = "alert alert-info">
-El equipo de <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">soporte de VTEX</a> puede ayudarte a elegir una de las tecnologías de storefront disponibles.
-</div>
+>ℹ️ El equipo de [soporte de VTEX](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) puede ayudarte a elegir una de las tecnologías de storefront disponibles.
 
 En la siguiente tabla se comparan las dos tecnologías según sus principales funcionalidades:
 
@@ -213,9 +207,7 @@ Antes de lanzar la tienda en producción, y antes del [go-live](https://help.vte
 - [Requisitos para un PMV de FastStore](#requisitos-para-un-pmv-de-faststore)
 - [Requisitos para un PMV de Store Framework](#requisitos-para-un-pmv-de-store-framework).
 
-<div class = "alert alert-info">
-Las recomendaciones a continuación abordan configuraciones básicas de storefront. Dependiendo de la <a href="https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitectura elegida</a> para la operación de la tienda, pueden ser necesarias otras configuraciones.
-</div>
+>ℹ️ Las recomendaciones a continuación abordan configuraciones básicas de storefront. Dependiendo de la [arquitectura elegida](https://help.vtex.com/es/tracks/serie-de-la-tienda-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) para la operación de la tienda, pueden ser necesarias otras configuraciones.
 
 ### Desarrollo con FastStore
 
diff --git a/docs/tracks/es/getting-started-with-logistics.md b/docs/tracks/es/getting-started-with-logistics.md
index 7fdf0494f..062fbda58 100644
--- a/docs/tracks/es/getting-started-with-logistics.md
+++ b/docs/tracks/es/getting-started-with-logistics.md
@@ -38,10 +38,9 @@ La pista reúne los artículos:
 * [Costos y simulación de envío](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/3by48jFhzpZEseYFpH9uVt): explica cómo registrar los costos de envío y cómo utilizar la herramienta de simulación de envío de la tienda.
 * [Entregas programadas y capacidad de entrega](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/5TuyqHRCCwYMaDv4r8rZdo): explica cómo la tienda debe ofrecer a los clientes las entregas programadas, así como gestionar la capacidad de entrega. 
 
-<div class = "alert alert-info"> Si tu tienda ya ha dado los primeros pasos en el módulo de <b>Inventario y envío</b>, consulta el artículo <a href="https://help.vtex.com/es/tutorial/logistics--53udnvI5eBy8DKo8FOjMoP">Logística</a>, para acceder rápidamente a la información de las secciones del módulo <b>Inventario y envío</b>. 
-Consulta el artículo <a href="https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby">Glosario de logística</a> para consultar el significado de los términos logísticos utilizados en VTEX.
-Las configuraciones logísticas disponibles mediante <a href="https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview">API</a>. 
-</div>
+>ℹ️ Si tu tienda ya ha dado los primeros pasos en el módulo de **Inventario y envío**, consulta el artículo [Logística](https://help.vtex.com/es/tutorial/logistics--53udnvI5eBy8DKo8FOjMoP), para acceder rápidamente a la información de las secciones del módulo **Inventario y envío**. 
+> Consulta el artículo [Glosario de logística](https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby) para consultar el significado de los términos logísticos utilizados en VTEX.
+> Las configuraciones logísticas disponibles mediante [API](https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview).
 
 El módulo de **Inventario y envío** se divide en las siguientes secciones:
 
@@ -57,9 +56,7 @@ El módulo de **Inventario y envío** se divide en las siguientes secciones:
 
 ![estoque e entregaES](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/a66b016481c796b9170823b1c111d3d9/estoque_e_entregaES.png)
 
-<div class = "alert alert-info">
-Los clientes que utilizan <a href="https://vtex.com/ar-es/">VTEX Shipping Network</a> acceden a la funcionalidad a través del módulo Inventario y envío.
-</div>
+>ℹ️ Los clientes que utilizan [VTEX Shipping Network](https://vtex.com/ar-es/) acceden a la funcionalidad a través del módulo Inventario y envío.
 
 Consulta los siguientes artículos de la pista para conocer el orden en que deben configurarse estas secciones y cómo interpreta la plataforma esta configuración.
 
diff --git a/docs/tracks/es/go-live-process.md b/docs/tracks/es/go-live-process.md
index 344afef86..dafa3cfab 100644
--- a/docs/tracks/es/go-live-process.md
+++ b/docs/tracks/es/go-live-process.md
@@ -20,9 +20,7 @@ En este tutorial, encontrarás una guía detallada paso a paso sobre cómo reali
 
 ![Go live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/d2dcbd2093cd822624d8ed29642eae4e/go_live_es.jpg)
 
-<div class = "alert alert-info">
-Ten en cuenta que una tienda en producción es diferente de una cuenta en producción. En general, se puede decir que para que una tienda esté en producción, es necesario poner la cuenta en producción y realizar el apuntamiento de DNS. Consulta todos los pasos de este proceso a continuación.
-</div>
+>ℹ️ Ten en cuenta que una tienda en producción es diferente de una cuenta en producción. En general, se puede decir que para que una tienda esté en producción, es necesario poner la cuenta en producción y realizar el apuntamiento de DNS. Consulta todos los pasos de este proceso a continuación.
 
 ## Antes de comenzar
 Antes de realizar el go live de tu tienda, es importante garantizar que hayas completado todas las configuraciones necesarias para el buen funcionamiento de la tienda.
@@ -35,9 +33,7 @@ Copia esta [Lista de verificación de tienda](https://assets.ctfassets.net/alnee
 
 El proceso de _go live_ de tu tienda puede tener variaciones en función de algunas características de tu operación. Además, algunos pasos son sensibles al tiempo. Por estos motivos, te recomendamos que planifiques todo el proceso de _go live_ con al menos 15 días de antelación.
 
-<div class = "alert alert-info">
-Si utilizas el CMS Portal Legado y quieres migrar a un storefront creado con <a href="https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">CMS IO</a>, sigue las instrucciones de la guía sobre cómo <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">migrar tu storefront de CMS Portal Legado a Store Framework</a>.
-</div>
+>ℹ️ Si utilizas el CMS Portal Legado y quieres migrar a un storefront creado con [CMS IO](https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), sigue las instrucciones de la guía sobre cómo [migrar tu storefront de CMS Portal Legado a Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 En aras de la organización y la comodidad, esta guía divide los pasos del _go live_ en cuatro etapas:
 
diff --git a/docs/tracks/es/google-pay.md b/docs/tracks/es/google-pay.md
index 46003b281..a8a2c4189 100644
--- a/docs/tracks/es/google-pay.md
+++ b/docs/tracks/es/google-pay.md
@@ -27,26 +27,20 @@ Para activar Google Pay, sigue los pasos a continuación.
 1. En el Admin VTEX, haz clic en el ícono del engranaje **Configuración de la tienda > Pago > Carteras** o ingresa. **Carteras** en la barra de búsqueda de la parte superior de la página.
 2. Selecciona la opción **Activar** para modificar el checkout e incluir la extensión de Google Pay.
 
-<div class = "alert alert-info">
-<p>Las redes admitidas en Google Pay son las mismas configuradas en las condiciones de pago.</p>
-</div>
+>ℹ️ Las redes admitidas en Google Pay son las mismas configuradas en las condiciones de pago.
 
 Una vez hecho esto, Google Pay estará disponible en el checkout de tu tienda VTEX como nuevo medio de pago. La configuración puede demorarse alrededor de 10 minutos en aparecer en el checkout.
 
 ![google-pay-checkout-es](https://images.ctfassets.net/alneenqid6w5/5EjOagjPXAeIAAN0Fpzkdq/b131b38fa81affd857db8c107278f3e9/Screenshot_2024-08-01_at_14.22.06.png)
 
-<div class = "alert alert-warning">
-<p>Google Pay, por el momento, no admite suscripciones.</p>
-</div>
+>⚠️ Google Pay, por el momento, no admite suscripciones.
 
 Para utilizar Google Pay deben cumplirse los siguientes requisitos:
 
 * Tener al menos una [condición de pago](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) activa configurada para tarjetas de crédito o débito con un adquirente, definiendo qué [adquirente](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente) procesará el pago.
 * Utilizar el [Checkout VTEX](https://help.vtex.com/es/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) en tu tienda.
 
-<div class = "alert alert-warning">
-  <p>En las tiendas que tengan el flujo de autenticación <a href="https://help.vtex.com/es/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado y admitido por el adquirente, el pago con Google Pay seguirá el flujo nativo de la tarjeta y también utilizará 3DS. Para más información sobre este tema, accede a <a href="https://help.vtex.com/es/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar flujo de autenticación 3DS 2</a>.</p>
-</div>
+>⚠️ En las tiendas que tengan el flujo de autenticación [3DS](https://help.vtex.com/es/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) configurado y admitido por el adquirente, el pago con Google Pay seguirá el flujo nativo de la tarjeta y también utilizará 3DS. Para más información sobre este tema, accede a [Configurar flujo de autenticación 3DS 2](https://help.vtex.com/es/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2).
 
 >ℹ️ También puedes configurar Google Pay para que se procese con Adyen o Stripe. Para hacer esto, acceda a la pantalla **Condiciones de pago** en Admin, haga clic en **Google Pay** y seleccione la opción deseada.
 
@@ -73,9 +67,7 @@ Para agregar en la plantilla de email que se le enviará al comprador la informa
 
 Así, siempre que haya cualquier mención de los últimos cuatro dígitos de la tarjeta en estas plantillas de email, se añadirá la información «(Google Pay)» si el pago se realizó con cartera digital.
 
-<div class = "alert alert-info">
-  <p>Para tiendas aprovisionadas a partir de marzo de 2023, las plantillas ya estarán actualizadas con la información del pago del pedido realizado con Google Pay.</p>
-</div>
+>ℹ️ Para tiendas aprovisionadas a partir de marzo de 2023, las plantillas ya estarán actualizadas con la información del pago del pedido realizado con Google Pay.
 
 ## Preguntas frecuentes
 
diff --git a/docs/tracks/es/how-does-vtex-intelligent-search-work.md b/docs/tracks/es/how-does-vtex-intelligent-search-work.md
index 875bb5344..bf12766a1 100644
--- a/docs/tracks/es/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/es/how-does-vtex-intelligent-search-work.md
@@ -49,9 +49,7 @@ Ejemplo: un cliente desea buscar el término `bola`. Siguiendo la configuración
 * `bora` (cambiar 1 carácter)
 * `obla` (intercambiar 2 caracteres que estén uno al lado del otro)
 
-<div class ="alert alert-info">
-	<p>El <em>fuzzy</em> no considera los espacios en blanco. Esto quiere decir que, por ejemplo, <code>base ball</code> no se corregiría a <code>baseball</code>. Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinónimos</a> en estos casos.</p>
-</div>
+>ℹ️ El *fuzzy* no considera los espacios en blanco. Esto quiere decir que, por ejemplo, `base ball` no se corregiría a `baseball`. Recomendamos usar [sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) en estos casos.
 
 ### Resultado mínimo
 
@@ -62,9 +60,7 @@ En las búsquedas que contienen varios términos, se aplica la siguiente lógica
 Si no se devuelve la cantidad mínima de resultados con la autocorrección inicial, la búsqueda comienza a incluir resultados más amplios que contengan cualquiera de los términos buscados. Por ejemplo, cuando un usuario busca “zapatilla nike” pero el catálogo no tiene ningún producto con ese nombre, la búsqueda puede mostrar como resultado un producto que contenga solo “zapatilla” en el nombre.
 Si la búsqueda más amplia no devuelve la cantidad de resultados mínima, se repetirá la autocorrección nuevamente en cada uno de los términos.
 
-<div class= "alert alert-warning">
-<p>Las búsquedas que contienen varios términos son más eficientes cuando el cliente ordena los resultados por relevancia, ya que pueden devolver un número mayor de resultados más allá del contexto de búsqueda inicial. En el orden por relevancia también pueden priorizarse ítems relacionados con cada término. Por otro lado, cuando se aplican otros criterios, como precio o más vendidos, el orden de los resultados depende de los valores numéricos y no necesariamente prioriza ítems que contienen más palabras.</p>
-</div>
+>⚠️ Las búsquedas que contienen varios términos son más eficientes cuando el cliente ordena los resultados por relevancia, ya que pueden devolver un número mayor de resultados más allá del contexto de búsqueda inicial. En el orden por relevancia también pueden priorizarse ítems relacionados con cada término. Por otro lado, cuando se aplican otros criterios, como precio o más vendidos, el orden de los resultados depende de los valores numéricos y no necesariamente prioriza ítems que contienen más palabras.
 
 ### Límite de paginación
 
diff --git a/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
index 79ad65dfd..ffb3d0be2 100644
--- a/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/es/how-to-create-and-edit-transactional-email-templates.md
@@ -23,9 +23,7 @@ Para editar un template de correo electrónico transaccional, siga los pasos a c
 3. Altere el título del correo electrónico y el destinatario (los valores entre llaves dobles son variables; en el próximo artículo aprenderemos cómo manejarlas). Usted puede incluir destinatarios en copia (`CC`) y copia oculta (`CCO`).
 4. Deje el flag __Utilizar remitente estándar__ para hacer uso de la dirección de correo electrónico registrado como estándar, como se explica en el artículo anterior de esta guía.
 
-<div class = "alert alert-info">
-La lista de plantillas está disponible en el artículo <a href="https://help.vtex.com/es/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">Plantillas de correo electrónico transaccional relacionadas con el pedido</a>.
-</div>
+>ℹ️ La lista de plantillas está disponible en el artículo [Plantillas de correo electrónico transaccional relacionadas con el pedido](https://help.vtex.com/es/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my).
 
 Es en el campo __HTML__ donde encuentra el código HTML del template. Puede editar el código en el propio campo o copiarlo en el editor de su preferencia, editarlo y luego pegarlo nuevamente en el campo del template.
 
diff --git a/docs/tracks/es/how-vtex-support-works.md b/docs/tracks/es/how-vtex-support-works.md
index 2ac57d2b0..1cc33130e 100644
--- a/docs/tracks/es/how-vtex-support-works.md
+++ b/docs/tracks/es/how-vtex-support-works.md
@@ -20,9 +20,7 @@ El soporte VTEX se presta online y permite abrir tickets con distintos niveles d
 - Inicio de sesión usando la cuenta de Google.
 - Email y contraseña con autenticación de dos factores mediante aplicación o SMS.
 
-<div class = "alert alert-warning">
-Para obtener la autorización de autenticación, el <a href="https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512">usuario </a> <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">rol </a> asociado con <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos de License Manager. </a>
-</div>
+>⚠️ Para obtener la autorización de autenticación, el [usuario ](https://help.vtex.com/es/tutorial/gestionar-usuarios--tutorials_512) [rol ](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) asociado con [recursos de License Manager. ](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3)
 
 El soporte VTEX está dividido en regiones, y cada región tiene su propio acuerdo de nivel de servicio (SLA), prioridad y disponibilidad del equipo de Customer Excellence (CX) para aquella determinada región. Las regiones donde hay servicio de soporte son las siguientes:
 
diff --git a/docs/tracks/es/integration-configurations.md b/docs/tracks/es/integration-configurations.md
index 04e4d65f5..3d4288b61 100644
--- a/docs/tracks/es/integration-configurations.md
+++ b/docs/tracks/es/integration-configurations.md
@@ -62,10 +62,8 @@ Es el precio específico para cada una de las subregiones de un país. De esta m
 
 _Ej.: el precio de envío a Rio de Janeiro (región metropolitana) es de R$ 10,00, mientras que para Rio de Janeiro (interior) es de R$ 15,00._
 
-<div class = "alert alert-info">
-  OBS: el envío por región está disponible apenas para sellers que usan <strong>Wish Express</strong> <a href="https://merchantfaq.wish.com/hc/pt/articles/360018939394-Como-enviar-usando-o-Wish-Express-Brasil-">(sepa más aquí).</a>
- Para configurar Wish Express, basta seguir <a href="https://merchantfaq.wish.com/hc/pt/articles/232047747-Wish-Express-Fluxo-de-Inscri%C3%A7%C3%A3o">estos pasos.</a>
-  </div>
+>ℹ️ OBS: el envío por región está disponible apenas para sellers que usan **Wish Express** [(sepa más aquí).](https://merchantfaq.wish.com/hc/pt/articles/360018939394-Como-enviar-usando-o-Wish-Express-Brasil-)
+>  Para configurar Wish Express, basta seguir [estos pasos.](https://merchantfaq.wish.com/hc/pt/articles/232047747-Wish-Express-Fluxo-de-Inscri%C3%A7%C3%A3o)
   
 Indique en la configuración si va a utilizar Wish Express. Si no es así, puede pasar al siguiente paso.
 
@@ -84,8 +82,7 @@ Para indicar cuál transportadora de su tienda corresponde a las [transportadora
 
   3. Haga clic en el botón “Guardar” para finalizar.
 
-<div class = "alert alert-info">
-  OBS: si se mapea alguna transportadora no certificada por Wish, los pedidos no podrán ser rastreados y, consecuentemente, <strong>no habrá</strong> transferencia de comisión. Por lo tanto, es necesario ser muy cuidadoso en esta etapa.</div>
+>ℹ️ OBS: si se mapea alguna transportadora no certificada por Wish, los pedidos no podrán ser rastreados y, consecuentemente, **no habrá** transferencia de comisión. Por lo tanto, es necesario ser muy cuidadoso en esta etapa.
 
 ## Tasa de divergencia de precios
  
diff --git a/docs/tracks/es/inventory.md b/docs/tracks/es/inventory.md
index 23954bd7c..2cbbc7dda 100644
--- a/docs/tracks/es/inventory.md
+++ b/docs/tracks/es/inventory.md
@@ -17,9 +17,7 @@ trackSlugES: logistica-101
 
 _Stock_ es la funcionalidad de gestión de los productos disponibles para la venta. Una vez [registrados los productos](https://help.vtex.com/es/tutorial/campos-de-registro-de-producto--4dYXWIK3zyS8IceKkQseke) en el [catálogo](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), es necesario añadirlos al _stock_ de una tienda para que estén realmente disponibles para la venta. El módulo de [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139) es donde los ítems del catálogo se vinculan a un _stock_.
 
-<div class = "alert alert-info">
-Recuerda que debes añadir al menos un <a href="https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb">almacén</a> en tu tienda antes de poder utilizar la funcionalidad de <a href="https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139"> Stock.</a> 
-</div>
+>ℹ️ Recuerda que debes añadir al menos un [almacén](https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb) en tu tienda antes de poder utilizar la funcionalidad de [ Stock.](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139)
 
 Mediante dicha funcionalidad, el administrador de la tienda también puede comprobar:
 
@@ -32,9 +30,7 @@ Para añadir ítems en masa a un _stock_, utiliza la plantilla de importación d
 
 Utiliza la [alerta de stock crítico](https://help.vtex.com/es/tutorial/configurar-la-alerta%20de%20Stock%20Cr%C3%ADtico--6FD0GHeQPCsKIMgkQ88SGu) para recibir notificaciones de los ítems que están a punto de agotarse.
 
-<div class = "alert alert-info">
-La configuración de stock también puede realizarse a través de la <a href="https://developers.vtex.com/vtex-rest-api/reference/inventory">API de stock</a>.
-</div>
+>ℹ️ La configuración de stock también puede realizarse a través de la [API de stock](https://developers.vtex.com/vtex-rest-api/reference/inventory).
 
 ### Más información
 
diff --git a/docs/tracks/es/managing-sales-associates-in-instore.md b/docs/tracks/es/managing-sales-associates-in-instore.md
index e6fd433b0..c790f47c9 100644
--- a/docs/tracks/es/managing-sales-associates-in-instore.md
+++ b/docs/tracks/es/managing-sales-associates-in-instore.md
@@ -40,9 +40,7 @@ Puedes realizar el registro de un vendedor siguiendo los pasos a continuación:
 
 Una vez registrado, el vendedor recibirá un email de confirmación de registro y será redirigido a la aplicación VTEX Sales App para iniciar sesión como vendedor.
 
-<div class ="alert alert-warning">
-<p>Los vendedores registrados en VTEX Sales App no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.</p> 
-</div>
+>⚠️ Los vendedores registrados en VTEX Sales App no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.
 
 ### Campos de registro del vendedor
 
@@ -57,9 +55,7 @@ Una vez registrado, el vendedor recibirá un email de confirmación de registro
 
 * **Tienda:** [cuenta franquicia](https://help.vtex.com/es/tutorial/que-es-una-cuenta-franquicia--kWQC6RkFSCUFGgY5gSjdl) en la que el vendedor será registrado. Campo obligatorio.
 
-<div class ="alert alert-info">
-<p>Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en VTEX Sales App.</p> 
-</div>
+>ℹ️ Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en VTEX Sales App.
 
 ## Buscar vendedor
 
diff --git a/docs/tracks/es/manual-product-matching-on-amazon.md b/docs/tracks/es/manual-product-matching-on-amazon.md
index 37c847dc5..7ead551d7 100644
--- a/docs/tracks/es/manual-product-matching-on-amazon.md
+++ b/docs/tracks/es/manual-product-matching-on-amazon.md
@@ -14,9 +14,7 @@ trackId: 6sgd4Pagy3wNsWKBvmIFrP
 trackSlugES: integracion-de-amazon
 ---
 
-<div class = "alert alert-info">
-El flujo documentado en este artículo no es obligatorio. Si optas por mantener la correspondencia automática, VTEX no será responsable de posibles problemas de correspondencia con Amazon.
-</div>
+>ℹ️ El flujo documentado en este artículo no es obligatorio. Si optas por mantener la correspondencia automática, VTEX no será responsable de posibles problemas de correspondencia con Amazon.
 
 Cada vez que se envía a Amazon un [SKU](https://help.vtex.com/es/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA) con [EAN](https://sellercentral.amazon.com.br/learn/courses?ref_=su_course_accordion&moduleId=71d0b122-4e43-4547-a05a-04517e8f41a2&courseId=959bc7cb-2866-499c-b24a-8d3f6def1306&modLanguage=Portuguese&videoPlayer=youtube) registrado, el marketplace realiza un proceso llamado correspondencia, que consiste en unificar los anuncios de un mismo producto a través de su EAN.
 
diff --git a/docs/tracks/es/mapping-colors-and-sizes.md b/docs/tracks/es/mapping-colors-and-sizes.md
index b73da5bd2..831527727 100644
--- a/docs/tracks/es/mapping-colors-and-sizes.md
+++ b/docs/tracks/es/mapping-colors-and-sizes.md
@@ -18,13 +18,9 @@ Después de hacer las configuraciones iniciales para la integración con Wish, a
 
 El envío de esta información se realiza cargando la plantilla de mapeo, que contiene un de/para. El mapeo solo se hará una vez para cada categoría. Esto significa que, una vez realizado el mapeo, los nuevos productos que se creen se integrarán directamente en la categoría correcta (y con sus respectivas variaciones y atributos).
 
-<div class = "alert alert-info">
-Usted debe realizar el mapeo de categoría para que Wish pueda diferenciar sus SKUs correctamente. Ejemplo: imagine que hay dos SKUs de un mismo producto con diferentes colores y tamaños iguales en VTEX, si no se realiza el mapeo de categoría, Wish reconocerá ambos SKUs como uno solo.
-</div>
+>ℹ️ Usted debe realizar el mapeo de categoría para que Wish pueda diferenciar sus SKUs correctamente. Ejemplo: imagine que hay dos SKUs de un mismo producto con diferentes colores y tamaños iguales en VTEX, si no se realiza el mapeo de categoría, Wish reconocerá ambos SKUs como uno solo.
 
-<div class = "alert alert-warning">
-Los productos sin un color o tamaño mapeado no se enviarán a Wish. Si alguna categoría no tiene estos campos en VTEX, será necesario <a href="https://help.vtex.com/es/tutorial/criando-campo-de-sku--tutorials_119">crear un campo de SKU</a> en el Catálogo y complete los valores apropiados antes de realizar la asignación de color y tamaño.
-</div>
+>⚠️ Los productos sin un color o tamaño mapeado no se enviarán a Wish. Si alguna categoría no tiene estos campos en VTEX, será necesario [crear un campo de SKU](https://help.vtex.com/es/tutorial/criando-campo-de-sku--tutorials_119) en el Catálogo y complete los valores apropiados antes de realizar la asignación de color y tamaño.
 
   - [Descargue aquí](https://drive.google.com/uc?export=download&id=1yJCgahkDhc4Gbvtxpe9kID1CwWsijdOf) la Plantilla de Mapeo de Wish en el  formato .xlsx.
 
@@ -61,9 +57,7 @@ Note que en VTEX el nombre de los campos es "Colores" y "Tamaños", pero Wish lo
 En VTEX, los productos de esta categoría poseen dos colores posibles: rojo y hielo. 
 Debe escogerse el color disponible más cercano que, en el caso de Wish, "Hielo" podría ser "White/Ice Glaze" (basado en [lista de colores aceptados](https://merchant.wish.com/documentation/colors)). Y "Rojo" podría ser "Red".
 
-<div class = "alert alert-info">
-  OBS: la cabecera de la tabla debe rellenarse exactamente como está en el siguiente ejemplo. Recuerde no agregar caracteres especiales como enter o espacio al rellenar esta tabla. 
-  </div>
+>ℹ️ OBS: la cabecera de la tabla debe rellenarse exactamente como está en el siguiente ejemplo. Recuerde no agregar caracteres especiales como enter o espacio al rellenar esta tabla.
 
 ![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
diff --git a/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
index 0530a9c33..d7166b59d 100644
--- a/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/es/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -21,9 +21,7 @@ Para enviar tus productos a Mercado Libre, debes:
 1. [Mapear las categorías de los productos.](#mapear-categorias)
 2. [Mapear los atributos de los productos.](#mapear-atributos)
 
-<div class = "alert alert-info">
-Tus productos deben tener el <a href="https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Stock</a> e <a href="https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">Precio</a> configurados antes de enviarlos a Mercado Libre.
-</div>
+>ℹ️ Tus productos deben tener el [Stock](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [Precio](https://help.vtex.com/es/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) configurados antes de enviarlos a Mercado Libre.
 
 ## Mapear categorías
 
diff --git a/docs/tracks/es/opening-tickets.md b/docs/tracks/es/opening-tickets.md
index cdfe306f7..f309dde1e 100644
--- a/docs/tracks/es/opening-tickets.md
+++ b/docs/tracks/es/opening-tickets.md
@@ -22,9 +22,7 @@ El acceso a una cuenta VTEX te permite entrar al [dashboard de soporte](https://
 
 ![Support imagem 1 - ES](https://images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/0ac7e761404016450b146bfc8fabfa67/support__imagem1_ES.gif)
 
-<div class = "alert alert-info">
-Para obtener más información sobre cómo abrir un ticket y sobre los tipos existentes, consulta el artículo <a href="https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM"> Abrir tickets para el soporte VTEX. </a>
-</div>
+>ℹ️ Para obtener más información sobre cómo abrir un ticket y sobre los tipos existentes, consulta el artículo [ Abrir tickets para el soporte VTEX. ](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM)
 
 ## Tipos de soporte
 
diff --git a/docs/tracks/es/partial-invoices.md b/docs/tracks/es/partial-invoices.md
index ffec5ed72..3e3205e6f 100644
--- a/docs/tracks/es/partial-invoices.md
+++ b/docs/tracks/es/partial-invoices.md
@@ -32,9 +32,7 @@ Las facturas parciales generan las siguientes acciones en el módulo **Pedidos**
 * Como en la factura parcial solo se liquida el valor correspondiente a la factura, se pueden realizar cambios en los importes del pedido. Con la factura parcial, la transacción queda pendiente.
 * No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos parcialmente facturados. Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
-<div class = "alert alert-info">
-La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el <a href="https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Los conectores legados no admiten la funcionalidad.
-</div>
+>ℹ️ La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Los conectores legados no admiten la funcionalidad.
 
 ## Envío de la factura parcial via Admin
 
@@ -54,9 +52,7 @@ Para enviar una factura parcial, sigue los pasos a continuación:
 
 Luego de realizar todos los cambios en el pedido, puedes seguir todos los eventos de la transacción haciendo clic en [Ver detalles de la transacción](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
 
-<div class = "alert alert-info">
-También puedes realizar las mismas acciones a través de nuestra API de Pedidos. Para hacerlo, revisa los <i>endpoints</i>: <a href="https://developers.vtex.com/vtex-rest-api/reference/registerchange">Register Change on Order</a>, <a href="https://developers.vtex.com/vtex-rest-api/reference/invoicenotification">Invoice notification</a>, <a href="https://developers.vtex.com/vtex-rest-api/reference/getpaymenttransaction">Retrieve Payment transaction</a>, y  <a href="https://developers.vtex.com/vtex-rest-api/reference/updatepartialinvoicesendtrackingnumber">Update order's partial invoice (send tracking number)</a>.
-    </div>  
+>ℹ️ También puedes realizar las mismas acciones a través de nuestra API de Pedidos. Para hacerlo, revisa los <i>endpoints</i>: [Register Change on Order](https://developers.vtex.com/vtex-rest-api/reference/registerchange), [Invoice notification](https://developers.vtex.com/vtex-rest-api/reference/invoicenotification), [Retrieve Payment transaction](https://developers.vtex.com/vtex-rest-api/reference/getpaymenttransaction), y  [Update order's partial invoice (send tracking number)](https://developers.vtex.com/vtex-rest-api/reference/updatepartialinvoicesendtrackingnumber).  
 
 ## Más información
 
diff --git a/docs/tracks/es/pre-go-live.md b/docs/tracks/es/pre-go-live.md
index 35b08eb43..3b64115aa 100644
--- a/docs/tracks/es/pre-go-live.md
+++ b/docs/tracks/es/pre-go-live.md
@@ -28,9 +28,7 @@ Si tu storefront se creó con [CMS IO](https://help.vtex.com/es/tracks/cms--2Ycp
 
 Después de recibir la confirmación del apuntamiento interno, debes realizar el [apuntamiento de DNS común](https://help.vtex.com/es/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-el-apuntamiento-de-dns) dentro de cinco días. De lo contrario, se eliminará el apuntamiento interno y tendrás que volver a solicitarlo.
 
-<div class = "alert alert-info">
-Aprende más sobre el <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live">go-live con Store Framework</a> o la <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migración del CMS heredado a Store Framework</a>.
-</div>
+>ℹ️ Aprende más sobre el [go-live con Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live) o la [Migración del CMS heredado a Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 ## Solicitar el apuntamiento especial
 
diff --git a/docs/tracks/es/reports-vtex-intelligent-search.md b/docs/tracks/es/reports-vtex-intelligent-search.md
index 748c1490a..3af89380a 100644
--- a/docs/tracks/es/reports-vtex-intelligent-search.md
+++ b/docs/tracks/es/reports-vtex-intelligent-search.md
@@ -23,9 +23,7 @@ A continuación se indican los pasos necesarios para acceder a la página:
 1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda en la parte superior de la página.
 2. En __Intelligent Search__, haz clic en __Analytics__. 
 
-<div class = "alert alert-info">
-  <p>La página <strong>Analytics</strong> es nativa en VTEX Intelligent Search. No se puede deshabilitar en el Admin.</p>
-</div>
+>ℹ️ La página **Analytics** es nativa en VTEX Intelligent Search. No se puede deshabilitar en el Admin.
 
 ## Datos
 
@@ -71,9 +69,7 @@ Para exportar un informe en formato CSV, debe seguir los pasos que se indican a
 5. Espere a que el archivo esté disponible para su descarga. Salir de esta página no interrumpe el proceso. 
 6. Haga clic en `Descargar`. 
 
-<div class = "alert alert-info">
-  <p>El archivo permanece disponible para descarga durante 48 horas.</p>
-</div>
+>ℹ️ El archivo permanece disponible para descarga durante 48 horas.
 
 El informe CSV descargado tiene dos tablas. La primera tabla, que se muestra a continuación, contiene información sobre los términos de búsqueda y las métricas de embudo (desde la columna **ProductsClick** hasta la columna **ProductsSold**), si se ha seleccionado esa opción.
 
diff --git a/docs/tracks/es/sending-product-data-to-dafiti.md b/docs/tracks/es/sending-product-data-to-dafiti.md
index a2fc2d5ea..64fdd8c55 100644
--- a/docs/tracks/es/sending-product-data-to-dafiti.md
+++ b/docs/tracks/es/sending-product-data-to-dafiti.md
@@ -62,9 +62,7 @@ La pestaña *Categories* de la plantilla de mapeo tiene dos columnas para rellen
 - **VTEXCategoryId:** ID de la categoría en VTEX. El ID de la categoría se encuentra al lado del nombre de la categoría al navegar por el árbol de categorías en el Admin VTEX, en *Productos > Catálogo > Categorías*.
 - **DafitiCategoryId:**  ID de la categoría en Dafiti. Debes buscar la mejor equivalencia posible del producto que estás mapeando en la plantilla de consulta de Dafiti.
 
-<div class = "alert alert-info">
-Puedes mapear una categoría de VTEX en varias categorías de Dafiti. Para hacerlo, debes separar los ID en la columna de Dafiti con comas. En ese caso, todos los productos de esa categoría en VTEX se relacionarán con las categorías seleccionadas en Dafiti.
-</div>
+>ℹ️ Puedes mapear una categoría de VTEX en varias categorías de Dafiti. Para hacerlo, debes separar los ID en la columna de Dafiti con comas. En ese caso, todos los productos de esa categoría en VTEX se relacionarán con las categorías seleccionadas en Dafiti.
 
 ### Attributenames
 
diff --git a/docs/tracks/es/sending-products-to-google-shopping.md b/docs/tracks/es/sending-products-to-google-shopping.md
index 6c396f06d..743390d46 100644
--- a/docs/tracks/es/sending-products-to-google-shopping.md
+++ b/docs/tracks/es/sending-products-to-google-shopping.md
@@ -20,9 +20,7 @@ En Google Shopping, solamente los [catálogos](https://help.vtex.com/es/tracks/c
 
 Después de configurar la integración y autenticar su cuenta, el envío de productos al _marketplace_ no es automático sino que será necesario que el _seller_ [reindexe la base](https://help.vtex.com/es/tutorial/entendendo-o-funcionamento-da-indexacao). Este proceso prepara los datos de los SKU y de los productos y envía al _marketplace_ la información general sobre el catálogo, los precios y el _stock_. 
 
-<div class = "alert alert-info">
-Solo el <a href="https://help.vtex.com/es/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA">usuario titular (owner)</a> tiene permiso para reindexar la base de una tienda VTEX. Durante el periodo de reindexación, que es variable, los productos ingresan en una fila para que se actualicen los datos, pero siguen disponibles para la venta en el sitio web de la tienda. 
-</div>
+>ℹ️ Solo el [usuario titular (owner)](https://help.vtex.com/es/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA) tiene permiso para reindexar la base de una tienda VTEX. Durante el periodo de reindexación, que es variable, los productos ingresan en una fila para que se actualicen los datos, pero siguen disponibles para la venta en el sitio web de la tienda.
 
 Para reindexar la base, copia en tu navegador la dirección a continuación y reemplaza «{nomedaloja}» con el nombre de tu tienda:
 
diff --git a/docs/tracks/es/set-a-price-for-the-sku.md b/docs/tracks/es/set-a-price-for-the-sku.md
index 8fec00e22..8421709e4 100644
--- a/docs/tracks/es/set-a-price-for-the-sku.md
+++ b/docs/tracks/es/set-a-price-for-the-sku.md
@@ -16,9 +16,7 @@ trackSlugES: vtex-getting-started
 
 Cualquier SKU de su tienda necesita un precio para ser exhibido al cliente final.
 
-<div class = "alert alert-warning">
-Incluso un SKU que se ofrecerá como regalo necesita tener un precio registrado.
-</div>
+>⚠️ Incluso un SKU que se ofrecerá como regalo necesita tener un precio registrado.
 
 Para registrar el precio, siga los pasos abajo.
 1. En el módulo __Catalog__, pase el ratón sobre __Cadastro de Productos__, vaya a __Productos y SKUs__ y haga clic en la opción __Cadastro de Productos y SKUs__.
diff --git a/docs/tracks/es/settings.md b/docs/tracks/es/settings.md
index 531115c76..539d7fa1f 100644
--- a/docs/tracks/es/settings.md
+++ b/docs/tracks/es/settings.md
@@ -44,16 +44,14 @@ Otra alternativa, aunque no recomendada, sería no incluir registros CAA en tu s
 
 Para facilitar el trabajo de crear y verificar tus registros CAA, puedes utilizar [CAA Record Helper de SSLMate](https://sslmate.com/caa/). El programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) también puede ayudar a verificar los registros mediante el comando `dig domain.com CAA`; el status `SERVFAIL` puede indicar que tu servidor DNS no está en cumplimiento.
 
-<div class = "alert alert-info">
-Más información:
-<p>
-<ul>
-<li><a href="https://sslmate.com/caa/">CAA Record Helper by SSLMate</a></li>
-<li><a href="https://letsencrypt.org/docs/caa/">Let's Encrypt: Certificate Authority Authorization (CAA)</a></li>
-<li><a href="https://sslmate.com/caa/about">SSL Mate: About CAA</a></li>
-</ul>
-</p>
-</div>
+>ℹ️ Más información:
+>
+> *[CAA Record Helper by SSLMate](https://sslmate.com/caa/)
+>
+> *[Let's Encrypt: Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)
+>
+> *[SSL Mate: About CAA](https://sslmate.com/caa/about)
+> 
 
 ## Poner la cuenta en producción
 
diff --git a/docs/tracks/es/shipping-costs-and-simulation.md b/docs/tracks/es/shipping-costs-and-simulation.md
index aee173482..36a04d163 100644
--- a/docs/tracks/es/shipping-costs-and-simulation.md
+++ b/docs/tracks/es/shipping-costs-and-simulation.md
@@ -43,6 +43,4 @@ Esta validación la realiza el [Simulador de envío](https://help.vtex.com/es/tu
 * Si hay puntos de recogida del producto.
 * Qué [seller white label](https://help.vtex.com/es/tutorial/que-son-cuenta-franquicia-y-seller-white-label--5orlGHyDHGAYciQ64oEgKa) realizará la entrega del producto. 
 
-<div class = "alert alert-info">
-También simula el envío a través de la API utilizando la <a href="https://developers.vtex.com/vtex-rest-api/reference/calculatesla">API de cálculo de SLA</a>.
-</div>
+>ℹ️ También simula el envío a través de la API utilizando la [API de cálculo de SLA](https://developers.vtex.com/vtex-rest-api/reference/calculatesla).
diff --git a/docs/tracks/es/shipping-strategies.md b/docs/tracks/es/shipping-strategies.md
index 587a8d39d..05ca37207 100644
--- a/docs/tracks/es/shipping-strategies.md
+++ b/docs/tracks/es/shipping-strategies.md
@@ -26,9 +26,7 @@ La estrategia de envío está definida por tres entidades logísticas:
 * [Almacén](https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb): identificación del lugar donde se almacenan los ítems. La política de envío no es la única variable para elegir la entrega, también hay que tener en cuenta en qué almacén se encuentran los productos del pedido. 
 * [Muelle](https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj): punto de recogida del almacén. Es a través del muelle que la tienda define la recogida de los paquetes. Las transportadoras recogen los paquetes para envío en el muelle.
 
-<div class = "alert alert-info">
-Hay otros escenarios posibles para el uso del muelle, consulta el artículo <a href="https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj">Muelle</a> y comprueba los casos de uso. Para saber más sobre el flujo de entregas, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-funciona-el-flujo-de-entregas--4ku3QKWfxmUO8UgA0yqgUq">¿Cómo funciona el flujo de entregas?</a>.
-</div>
+>ℹ️ Hay otros escenarios posibles para el uso del muelle, consulta el artículo [Muelle](https://help.vtex.com/es/tutorial/muelles--5DY8xHEjOLYDVL41Urd5qj) y comprueba los casos de uso. Para saber más sobre el flujo de entregas, consulta el artículo [¿Cómo funciona el flujo de entregas?](https://help.vtex.com/es/tutorial/como-funciona-el-flujo-de-entregas--4ku3QKWfxmUO8UgA0yqgUq).
 
 Ten en cuenta que:
 
@@ -54,15 +52,13 @@ En los casos en los que la tienda ofrece [puntos de recogida](https://help.vtex.
 
 El punto de recogida está disponible en el _checkout_ como opción de envío y el cliente elige entre **Entrega** (transportadora) y **Recogida** (punto de recogida).
 
-<div class = "alert alert-info">
-La configuración de la Estrategia de envío también se puede realizar a través de las API. Consulta las API disponibles:
-<body>
-<ul>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/docks">API de muelles</li></a>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse">API de almacenes</li></a>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/get_logistics-pvt-shipping-policies-id">API de políticas de envío</li></a>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/listallpickupppoints">API de puntos de recogida</li></a>
-</div>
+>ℹ️ La configuración de la Estrategia de envío también se puede realizar a través de las API. Consulta las API disponibles:
+> <body>
+> <ul>
+> <li>[API de muelles</li>](https://developers.vtex.com/vtex-rest-api/reference/docks)
+> <li>[API de almacenes</li>](https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse)
+> <li>[API de políticas de envío</li>](https://developers.vtex.com/vtex-rest-api/reference/get_logistics-pvt-shipping-policies-id)
+> <li>[API de puntos de recogida</li>](https://developers.vtex.com/vtex-rest-api/reference/listallpickupppoints)
 
 ### Cómo configurar
 
@@ -102,6 +98,4 @@ Para registrar los feriados en la plataforma, puedes:
 
 Puedes registrar los horarios de entrega para envíos programados de las transportadoras y puntos de recogida. La funcionalidad **[Entrega programada](https://help.vtex.com/es/tutorial/entrega-programada--22g3HAVCGLFiU7xugShOBi)** permite a la tienda ofrecer ventanas de entrega a los clientes.
 
-<div class = "alert alert-info">
-El envío también depende del <a href="https://help.vtex.com/es/tutorial/costo-final-del-envio--5bwhIO108VA5Y2YOpef9lV">costo de envío</a> que tu tienda ofrece a los clientes. Este tema se presentará en los próximos artículos. Para entender mejor cómo se eligen las transportadoras que realizarán una entrega, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-funciona-el-calculo-del-flete--tutorials_116">Cómo funciona el cálculo del flete</a>.
-</div>
+>ℹ️ El envío también depende del [costo de envío](https://help.vtex.com/es/tutorial/costo-final-del-envio--5bwhIO108VA5Y2YOpef9lV) que tu tienda ofrece a los clientes. Este tema se presentará en los próximos artículos. Para entender mejor cómo se eligen las transportadoras que realizarán una entrega, consulta el artículo [Cómo funciona el cálculo del flete](https://help.vtex.com/es/tutorial/como-funciona-el-calculo-del-flete--tutorials_116).
diff --git a/docs/tracks/es/synonyms.md b/docs/tracks/es/synonyms.md
index cd73dfef4..f39043247 100644
--- a/docs/tracks/es/synonyms.md
+++ b/docs/tracks/es/synonyms.md
@@ -24,9 +24,7 @@ Para esto, VTEX Intelligent Search recibe el término buscado por el cliente y l
 
 Así, si hay una regla de sinónimos, no importa cómo el cliente busque o cómo está registrado el nombre del producto, siempre encontrará lo que busca.
 
-<div class = "alert alert-warning">
-Los sinónimos no deben ser usados para resolver errores de ortografía, plural y singular o incluso pronombres, artículos y preposiciones en los términos investigados. En todos estos puntos, VTEX Intelligent Search es capaz de interpretar, aprender y resolver automáticamente por medio de algoritmos.
-</div>
+>⚠️ Los sinónimos no deben ser usados para resolver errores de ortografía, plural y singular o incluso pronombres, artículos y preposiciones en los términos investigados. En todos estos puntos, VTEX Intelligent Search es capaz de interpretar, aprender y resolver automáticamente por medio de algoritmos.
 
 ## Tipos de sinónimos
 
diff --git a/docs/tracks/es/unified-search.md b/docs/tracks/es/unified-search.md
index ea138e406..30b517578 100644
--- a/docs/tracks/es/unified-search.md
+++ b/docs/tracks/es/unified-search.md
@@ -17,9 +17,7 @@ trackSlugES: instore-usando-el-app
 
 El [pasillo infinito](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn) de VTEX Sales App le permite al vendedor buscar y agregar al carrito productos más allá del stock de su tienda. Para buscar un producto, haz clic en el ícono de lupa <i class="fas fa-search"></i>. Se mostrará la barra de búsqueda en la parte superior de la página de inicio de la tienda.  Ingresa el nombre del producto, código de referencia, ID de SKU o EAN para buscar.
 
-<div class = "alert alert-info">
-Para mejorar la experiencia en situaciones en que la conexión de internet esté lenta, esta funcionalidad tiene recursos de optimización que utilizan la caché del navegador para agilizar la búsqueda.
-</div>
+>ℹ️ Para mejorar la experiencia en situaciones en que la conexión de internet esté lenta, esta funcionalidad tiene recursos de optimización que utilizan la caché del navegador para agilizar la búsqueda.
 
 ![Barra busca - ES](https://images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/1ad8c720186c675630364918f1d9e0f1/Tela_1_barra_busca.gif)
 
diff --git a/docs/tracks/es/viewing-the-email-history-of-an-order.md b/docs/tracks/es/viewing-the-email-history-of-an-order.md
index d4872e952..45bace10b 100644
--- a/docs/tracks/es/viewing-the-email-history-of-an-order.md
+++ b/docs/tracks/es/viewing-the-email-history-of-an-order.md
@@ -22,6 +22,4 @@ Para ver el historial de correos electrónicos, vaya al módulo **Pedidos**, ent
 
 El sistema que hace este registro se llama __Conversation Tracker__. Para entender más a fondo cómo funciona, consulte el artículo [Cómo se realiza la comunicación con el cliente durante el flujo del pedido](https://help.vtex.com/es/tutorial/comprendiendo-el-conversation-tracker--tutorials_195).
 
-<div class = "alert alert-info">
-Como la comunicación con el cliente es responsabilidad del marketplace, solamente los pedidos con origen marketplace tienen un historial de emails transaccionales. Los pedidos con origen fulfillment no mantienen tal historial.
-</div>
+>ℹ️ Como la comunicación con el cliente es responsabilidad del marketplace, solamente los pedidos con origen marketplace tienen un historial de emails transaccionales. Los pedidos con origen fulfillment no mantienen tal historial.
diff --git a/docs/tracks/es/vtex-modules-ii.md b/docs/tracks/es/vtex-modules-ii.md
index 05cf83ce6..53b61d0ad 100644
--- a/docs/tracks/es/vtex-modules-ii.md
+++ b/docs/tracks/es/vtex-modules-ii.md
@@ -73,9 +73,7 @@ Es necesario activar los proveedores de pago en la tienda a fin de permitir la t
 2. Selecciona el proveedor deseado haciendo clic en el respectivo link en la tabla.
 3. En el Admin VTEX, configura el proveedor según las instrucciones descritas en el artículo de configuración.
 
-<div class = "alert alert-info">
-También se puede acceder a los artículos de configuración de proveedores escribiendo el nombre del proveedor deseado en la barra de búsqueda del <a href="https://help.vtex.com/es/">Help Center</a>.
-</div>
+>ℹ️ También se puede acceder a los artículos de configuración de proveedores escribiendo el nombre del proveedor deseado en la barra de búsqueda del [Help Center](https://help.vtex.com/es/).
 
 #### Definir medios y condiciones de pago
 
diff --git a/docs/tracks/es/what-is-the-master-user.md b/docs/tracks/es/what-is-the-master-user.md
index a9a4d59e6..46cee9f63 100644
--- a/docs/tracks/es/what-is-the-master-user.md
+++ b/docs/tracks/es/what-is-the-master-user.md
@@ -18,9 +18,7 @@ Para la plataforma VTEX, el usuario Titular es el principal responsable de la ti
 
 De forma predeterminada, el e-mail del usuario Titular es del dueño del acuerdo comercial de contratación de VTEX. Pero, después de recibir el ambiente VTEX, se puede cambiar el correo electrónico del usuario Titular.
 
-<div class = "alert alert-warning">
-El usuario titular no es el mismo que el <b>Owner (Admin Super)</b>. El <b>Owner (Admin Super)</b> es un perfil de acceso del License Manager que define los permisos que se conceden a un determinado usuario de tu tienda, e incluso puede asignarse a varios usuarios.
-</div>
+>⚠️ El usuario titular no es el mismo que el **Owner (Admin Super)**. El **Owner (Admin Super)** es un perfil de acceso del License Manager que define los permisos que se conceden a un determinado usuario de tu tienda, e incluso puede asignarse a varios usuarios.
 
 Si su usuario tiene perfil de acceso al módulo Gestión de la cuenta, usted puede verificar quién es el usuario Titular. Basta con acceder a la pestaña __Cuentas__ y buscar el nombre de la tienda.
 
diff --git a/docs/tracks/pt/add-on-products.md b/docs/tracks/pt/add-on-products.md
index af1c674d8..4766019c3 100644
--- a/docs/tracks/pt/add-on-products.md
+++ b/docs/tracks/pt/add-on-products.md
@@ -119,6 +119,4 @@ Os principais benefícios dessa funcionalidade são:
 - **Melhoria na experiência do cliente:** É possível personalizar mensagens para aumentar a relevância e fortalecer a relação com a marca.
 - **Aumento nas taxas de conversão e vendas:** incentiva que os clientes retornem à página de pagamento para finalizar sua compra, aumentando desta forma as vendas e taxas de conversão para lojistas.
 
-<div class = "alert alert-info">
-O WhatsApp AI Campaigns está disponível  apenas para lojas que utilizam <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> que não tenham customizações no Checkout.
-</div>
+>ℹ️ O WhatsApp AI Campaigns está disponível  apenas para lojas que utilizam [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) que não tenham customizações no Checkout.
diff --git a/docs/tracks/pt/adding-new-stores-to-instore.md b/docs/tracks/pt/adding-new-stores-to-instore.md
index b775a3360..d4ed4f814 100644
--- a/docs/tracks/pt/adding-new-stores-to-instore.md
+++ b/docs/tracks/pt/adding-new-stores-to-instore.md
@@ -75,9 +75,7 @@ Você pode cadastrar uma loja física seguindo os passos a seguir:
 * **Política comercial:** [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será aplicada na loja física. Campo obrigatório.
 * **Ponto de retirada:** [ponto de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) cadastrado para essa loja física, onde clientes retiram seus pedidos. 
 
-<div class ="alert alert-info">
-<p>As alterações podem levar até 15 minutos para serem processadas e aplicadas no VTEX Sales App.</p> 
-</div>
+>ℹ️ As alterações podem levar até 15 minutos para serem processadas e aplicadas no VTEX Sales App.
 
 ## Buscar loja física
 
diff --git a/docs/tracks/pt/allowing-order-replacement.md b/docs/tracks/pt/allowing-order-replacement.md
index 6e8451113..37663aa79 100644
--- a/docs/tracks/pt/allowing-order-replacement.md
+++ b/docs/tracks/pt/allowing-order-replacement.md
@@ -18,9 +18,7 @@ A **Substituição de pedidos** permite aos clientes da sua loja alterar dados d
 
 O objetivo é ajudá-los a corrigir erros sem a necessidade de realizar um novo pedido manualmente ou de entrar em contato com seu suporte, o que facilita a operação da sua loja e reduz custos.
 
-<div class = "alert alert-warning">
-Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
-</div>
+>⚠️ Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Como ativar a Substituição de pedidos
 
@@ -32,7 +30,5 @@ A funcionalidade está disponível para todos as lojas. Para ativá-la, siga os
 
 Em 15 minutos, após a atualização automática do cache, a funcionalidade estará disponível.
 
-<div class = "alert alert-info">
-Para mais informações sobre a funcionalidade e casos que não permitem substituição, veja o artigo <a href="https://help.vtex.com/pt/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8">Substituição de pedidos</a>.
-</div>
+>ℹ️ Para mais informações sobre a funcionalidade e casos que não permitem substituição, veja o artigo [Substituição de pedidos](https://help.vtex.com/pt/tutorial/substituicao-de-pedidos--2IK9mwQjBKseQmE8K8saO8).
 
diff --git a/docs/tracks/pt/autocomplete-search.md b/docs/tracks/pt/autocomplete-search.md
index f78c35fd9..a23abc5f8 100644
--- a/docs/tracks/pt/autocomplete-search.md
+++ b/docs/tracks/pt/autocomplete-search.md
@@ -14,9 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
-<div class = "alert alert-warning">
-O Autocomplete é uma ferramenta já ativa no VTEX Intelligent Search. Não é possível desligá-la no Admin.
-    </div>
+>⚠️ O Autocomplete é uma ferramenta já ativa no VTEX Intelligent Search. Não é possível desligá-la no Admin.
 
 O Autocomplete funciona com base nas informações obtidas por meio do histórico de busca de termos relacionados ao Catálogo. Esses resultados são apresentados em quatro listas diferentes, que podem estar juntas ou separadas, dependendo da interação com o cliente. As seções existentes são:
 
@@ -34,19 +32,14 @@ Durante a interação com a barra de busca, o VTEX Intelligent Search exibe imed
 
 Quando o usuário começa a digitar, o sistema mostra as _Sugestões de busca_ e _Sugestões de produtos_ e remove as listas anteriores.
 
-<div class = "alert alert-info">
-  <p>As informações das seções <b>Termos mais buscados</b> e <b>Sugestão de busca</b> são atualizadas diariamente. Para isso, são utilizados os dados dos últimos 14 dias da interação dos clientes com a busca.</p>
-  </div>
+>ℹ️ As informações das seções **Termos mais buscados** e **Sugestão de busca** são atualizadas diariamente. Para isso, são utilizados os dados dos últimos 14 dias da interação dos clientes com a busca.
 
 Dessa forma, é possível proporcionar ao cliente uma experiência de pesquisa mais fluida e personalizada. Ele consegue visualizar o resultado de maneira rápida, além de receber sugestões baseadas na sua busca.
 
 Outra vantagem para o gestor da loja é o aumento de conversão, resultado dessa dinâmica de usabilidade e experiência.
 
-<div class = "alert alert-info">
-  <p> O Autocomplete oferece sugestões de pesquisa mesmo quando a loja é totalmente nova e ainda não dispõe de dados de interações com clientes, como cliques e buscas.
-    Nesse caso, a funcionalidade gera sugestões de busca a partir de um algoritmo que extrai palavras-chave do catálogo, dos produtos, das marcas e das categorias registradas na loja.
-</p>
-  </div>
+>ℹ️ O Autocomplete oferece sugestões de pesquisa mesmo quando a loja é totalmente nova e ainda não dispõe de dados de interações com clientes, como cliques e buscas.
+>     Nesse caso, a funcionalidade gera sugestões de busca a partir de um algoritmo que extrai palavras-chave do catálogo, dos produtos, das marcas e das categorias registradas na loja.
 
 ## Termos mais buscados
 
diff --git a/docs/tracks/pt/backend-integrations.md b/docs/tracks/pt/backend-integrations.md
index 0c56bb739..700683f39 100644
--- a/docs/tracks/pt/backend-integrations.md
+++ b/docs/tracks/pt/backend-integrations.md
@@ -181,9 +181,7 @@ Na VTEX, é importante compreender a distinção entre Produtos e SKUs:
 - [Produto](https://help.vtex.com/pt/tracks/catalog-101--5AF0XfnjfWeopIFBgs3LIQ/1wmX3QvQVxbKVmalhIE5Ru): unidade abstrata do catálogo, visível nas prateleiras da loja. 
 - [SKU](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3mJbIqMlz6oKDmyZ2bKJoA): unidade concreta do catálogo no estoque, representando as variações específicas de um produto, como cor, tamanho e outros atributos. Os SKUs são exibidos como itens individuais em páginas de produtos.
 
-<div class = "alert alert-info">
-A maneira como produtos e SKUs são estruturados tem impacto direto na experiência de compra dos clientes.
-</div>
+>ℹ️ A maneira como produtos e SKUs são estruturados tem impacto direto na experiência de compra dos clientes.
 
 A importação de produtos segue os passos na ordem da tabela abaixo:
 
@@ -262,9 +260,7 @@ Existem duas formas de rastrear mudanças de status de pedidos na VTEX:
 
 Para os dois tipos de integração, é possível aplicar [filtros](https://developers.vtex.com/docs/guides/orders-feed#filter) para selecionar os tipos de evento que devem ser processados pelo back-office.
 
-<div class = "alert alert-info">
-Para a maioria dos casos, a VTEX recomenda a integração de pedidos pelo <a href="https://developers.vtex.com/docs/guides/orders-feed">Feed v3</a> devido à sua resiliência.
-</div>
+>ℹ️ Para a maioria dos casos, a VTEX recomenda a integração de pedidos pelo [Feed v3](https://developers.vtex.com/docs/guides/orders-feed) devido à sua resiliência.
 
 #### Obter detalhes do pedido
 
@@ -392,9 +388,7 @@ Se a loja VTEX não encontrar um app que atenda às necessidades do seu modelo d
 
     d. **(Opcional) Validar se o meu app atende a minha necessidade de negócio:** após ter a versão publicada, pode ser interessante instalar o app em um [workspace de produção](https://developers.vtex.com/docs/guides/vtex-io-documentation-creating-a-production-workspace) e realizar um [teste A/B](https://developers.vtex.com/docs/guides/ab-tests) a fim de comparar a taxa de conversão das vendas considerando o seu novo app.
 
-<div class = "alert alert-info">
-Caso queira aprender mais sobre o desenvolvimento de apps, recomendamos acessar o nosso <a href="https://learn.vtex.com/">Learning Center</a>.
-</div>
+>ℹ️ Caso queira aprender mais sobre o desenvolvimento de apps, recomendamos acessar o nosso [Learning Center](https://learn.vtex.com/).
 
 - **Deseja tornar o app disponível publicamente?** É possível [disponibilizar](https://developers.vtex.com/docs/guides/vtex-io-documentation-making-your-new-app-version-publicly-available) o app na App Store, permitindo que outras contas possam se alavancar da solução desenvolvida.
 - **Deseja tornar o app disponível na App Store?** Existem algumas vantagens em tornar o app disponível na App Store, como aumentar a visibilidade do seu app e a possibilidade de [monetizá-lo](https://developers.vtex.com/docs/guides/vtex-io-documentation-setting-your-apps-billing-model). Para isso, é necessário seguir alguns passos e regras. Em resumo, deve-se tornar um [desenvolvedor registrado](https://developers.vtex.com/docs/guides/vtex-io-documentation-becoming-a-registered-vtex-app-store-developer), ter o código do app armazenado em um repositório do [GitHub](https://github.com), desenvolver o app obedecendo as [melhores práticas da App Store](https://developers.vtex.com/docs/guides/vtex-io-documentation-homologation-requirements-for-vtex-app-store) e [submetê-lo](https://developers.vtex.com/docs/guides/vtex-io-documentation-submitting-your-app-in-the-vtex-app-store) ao processo de homologação. Após homologado, o app estará disponível na App Store.
diff --git a/docs/tracks/pt/billing-support.md b/docs/tracks/pt/billing-support.md
index 191bb1510..9991ab7e8 100644
--- a/docs/tracks/pt/billing-support.md
+++ b/docs/tracks/pt/billing-support.md
@@ -25,9 +25,7 @@ A VTEX busca garantir a conformidade com os procedimentos e políticas de pagame
 - [Contas a Pagar - Brasil](https://help.vtex.com/pt/tutorial/contas-a-pagar-brasil--tutorials_660): práticas a serem seguidas em todos os pagamentos a fornecedores relacionados aos procedimentos de contas a pagar das filiais VTEX no Brasil.
 - [Contas a pagar - Internacional](https://help.vtex.com/pt/tutorial/contas-a-pagar-internacional--3yea9sIlsA0KgUC28ASCGs): práticas a serem seguidas em todos os pagamentos a fornecedores relacionados aos procedimentos de contas a pagar das filiais VTEX fora do Brasil.
 
-<div class = "alert alert-info">
-  <p>Para conferir a lista de filiais VTEX pelo mundo e saber em qual país é emitida a fatura, basta consultar o artigo <a href="https://help.vtex.com/pt/tutorial/nomes-das-filiais-vtex-pelo-mundo--zg05n6OIOZOEmLW7dcq9z">País de faturamento da loja</a>.</p>
-</div>
+>ℹ️ Para conferir a lista de filiais VTEX pelo mundo e saber em qual país é emitida a fatura, basta consultar o artigo [País de faturamento da loja](https://help.vtex.com/pt/tutorial/nomes-das-filiais-vtex-pelo-mundo--zg05n6OIOZOEmLW7dcq9z).
 
 ## Cálculo da receita da fatura pela VTEX
 
@@ -47,6 +45,4 @@ Após o [primeiro acesso](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--e
 
 Para fazer essas alterações, é necessário [abrir um chamado para o suporte financeiro](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM#financeiro), especificando o tipo de alteração necessária.
 
-<div class = "alert alert-info">
-  <p>Para obter mais informações sobre como solicitar a avaliação de SLA e descontos concedidos devido a violações do SLA, basta consultar o artigo <a href="https://help.vtex.com/pt/tutorial/como-solicitar-a-apuracao-de-sla--3L99VeoLhYEwMqqkWKu86i>">Solicitar apuração de SLA do suporte VTEX</a>.</p>
-</div>
+>ℹ️ Para obter mais informações sobre como solicitar a avaliação de SLA e descontos concedidos devido a violações do SLA, basta consultar o artigo [Solicitar apuração de SLA do suporte VTEX](https://help.vtex.com/pt/tutorial/como-solicitar-a-apuracao-de-sla--3L99VeoLhYEwMqqkWKu86i>).
diff --git a/docs/tracks/pt/canceling-an-order.md b/docs/tracks/pt/canceling-an-order.md
index 1c474bdad..516984829 100644
--- a/docs/tracks/pt/canceling-an-order.md
+++ b/docs/tracks/pt/canceling-an-order.md
@@ -21,9 +21,7 @@ trackSlugPT: pedidos
 
 >⚠️ Uma vez que o pedido seja cancelado, não é possível alterar o seu status. Pedidos com status **Faturado** não podem ser cancelados.
 
-<div class = "alert alert-info">
-Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
-</div>
+>ℹ️ Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Cancelamento pelo módulo Pedidos
 
diff --git a/docs/tracks/pt/configure-integration.md b/docs/tracks/pt/configure-integration.md
index 3a6a9e64c..4bea5374a 100644
--- a/docs/tracks/pt/configure-integration.md
+++ b/docs/tracks/pt/configure-integration.md
@@ -49,10 +49,8 @@ Feito isso, a integração da sua loja VTEX com o Magalu Marketplace estará con
 
 **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-  <p><b>Exemplo de nome para o novo campo:</b> <code>MGZ_ProductName</code> para nome do produto e <code>MGZ_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+>   **Exemplo de nome para o novo campo:** `MGZ_ProductName` para nome do produto e `MGZ_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/configuring-banners.md b/docs/tracks/pt/configuring-banners.md
index bd3cc5c30..ba6f1accf 100644
--- a/docs/tracks/pt/configuring-banners.md
+++ b/docs/tracks/pt/configuring-banners.md
@@ -24,9 +24,7 @@ Para configurar um banner, siga os seguintes passos:
 
 Depois de realizar as configurações do banner, você deve adicioná-lo a uma página da sua loja. Para isso, siga os passos do guia [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner).
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
-</div>
+>ℹ️ Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo [VTEX Intelligent Search: configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners) para saber mais.
 
 ![banner-form-pt](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
 
diff --git a/docs/tracks/pt/configuring-dafiti-connector.md b/docs/tracks/pt/configuring-dafiti-connector.md
index dd2b2132b..f4cfba184 100644
--- a/docs/tracks/pt/configuring-dafiti-connector.md
+++ b/docs/tracks/pt/configuring-dafiti-connector.md
@@ -55,10 +55,8 @@ A configuração do conector é feita no Admin. Para realizá-la, siga as instru
 - **Client Secret:** código único utilizado para autenticação da integração.
 - **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-  <p><b>Exemplo de nome para o novo campo:</b> <code>DFT_ProductName</code> para nome do produto e <code>DFT_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+>   **Exemplo de nome para o novo campo:** `DFT_ProductName` para nome do produto e `DFT_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/configuring-payment-connectors.md b/docs/tracks/pt/configuring-payment-connectors.md
index 1e9810885..e6d0f1c00 100644
--- a/docs/tracks/pt/configuring-payment-connectors.md
+++ b/docs/tracks/pt/configuring-payment-connectors.md
@@ -18,9 +18,7 @@ O módulo de __Pagamentos__ permite que diversos provedores de pagamento (gatewa
 
 Quando uma compra é realizada em sua loja e o cliente efetua o pagamento, a transmissão de dados entre a VTEX e o provedor escolhido ocorre por meio de protocolos de comunicação configurados no Admin VTEX.
 
-<div class = "alert alert-info">
-  Para verificar quais provedores de pagamento estão disponíveis em sua região e os respectivos artigos de configurações, acesse a <a href="https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp">Lista de provedores de pagamento por país</a>.</p>
-</div>
+>ℹ️ Para verificar quais provedores de pagamento estão disponíveis em sua região e os respectivos artigos de configurações, acesse a [Lista de provedores de pagamento por país](https://help.vtex.com/pt/tutorial/lista-de-provedores-de-pagamento-por-pais--2im3BEGXxSAcRuxEaIHPvp).</p>
 
 Veja abaixo um exemplo de como configurar um provedor de pagamento:
 
diff --git a/docs/tracks/pt/configuring-synonyms.md b/docs/tracks/pt/configuring-synonyms.md
index 028cd1365..921e54d28 100644
--- a/docs/tracks/pt/configuring-synonyms.md
+++ b/docs/tracks/pt/configuring-synonyms.md
@@ -14,7 +14,7 @@ trackId: 19wrbB7nEQcmwzDPl1l4Cb
 trackSlugPT: vtex-intelligent-search
 ---
 
-<div class = "alert alert-info"> Para relacionar palavras ao produto, é recomendada a utilização da configuração de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV?&utm_source=autocomplete">Sinônimos</a> ao invés das <a href="https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palavras Substitutas</a>, uma vez que os sinônimos possibilitam uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.</div>
+>ℹ️ Para relacionar palavras ao produto, é recomendada a utilização da configuração de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV?&utm_source=autocomplete) ao invés das [Palavras Substitutas](https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete), uma vez que os sinônimos possibilitam uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso [Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Existem duas formas de configurar sinônimos no Admin VTEX: [individualmente](#criar-sinonimos-individualmente) ou por [importação de uma planilha em formato CSV](#importar-csv). Se você precisa cadastrar sinônimos em massa, recomendamos utilizar a planilha. Confira as instruções para cada forma de configuração nas seções a seguir.
 
@@ -40,9 +40,7 @@ Siga o passo a passo para configurar sinônimos individualmente no Admin VTEX:
 
 A alteração pode demorar até duas horas para ser aplicada.
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
-</div>
+>ℹ️ Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo [VTEX Intelligent Search: configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos) para saber mais.
 
 ## Importar CSV
 
diff --git a/docs/tracks/pt/configuring-the-connector-b2w.md b/docs/tracks/pt/configuring-the-connector-b2w.md
index 7ca842b1a..fdcfa2898 100644
--- a/docs/tracks/pt/configuring-the-connector-b2w.md
+++ b/docs/tracks/pt/configuring-the-connector-b2w.md
@@ -45,18 +45,14 @@ Para realizar a configuração do conector, siga os passos abaixo:
 - **Estoque mínimo (Se o saldo do SKU estiver igual ou abaixo do valor configurado, será enviado saldo 0 para o marketplace e o anúncio será desativado)*:** insira o valor mínimo de estoque de segurança. Se a quantidade de itens de um produto em estoque estiver abaixo do valor escolhido, seu anúncio será pausado para evitar vendas sem estoque durante o tempo de atualização da SkyHub/B2W pela VTEX. Escolha com atenção, pois essa configuração é aplicada a todos os produtos. Verifique se algum produto deixaria de ser anunciado devido ao seu estoque inicial.
 - **Enviar KIT*:** ao escolher _Não_, SKUs [cadastrados como kit](https://help.vtex.com/pt/tutorial/cadastrando-kit--tutorials_215) não são enviados para a B2W. Ao habilitar _Sim_, todos os itens da sua política comercial são enviados para o marketplace, sem filtrar SKUs cadastrados como kit. Mudanças na configuração do conector podem ser feitas a qualquer momento, sendo que isso não afeta SKUs que já tenham sido enviados. Por exemplo, se você mudasse sua configuração de _Sim_ para _Não_, SKUs enviados anteriormente para a B2W não seriam removidos ou sofreriam qualquer alteração.
 
-  <div class = "alert alert-info">
-Com a opção <i>Não</i> ativada, tentativas de envio para a B2W de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo <b>MARKETPLACE > Integrações > Produtos</b>, ao se clicar sobre o SKU.
-</div>
+  >ℹ️ Com a opção <i>Não</i> ativada, tentativas de envio para a B2W de SKUs cadastrados como kit resultarão no seguinte aviso: <i>O conector está configurado para não enviar SKUs do tipo Kit</i>. Esta mensagem pode ser visualizada no Admin, no módulo **MARKETPLACE > Integrações > Produtos**, ao se clicar sobre o SKU.
 
 - **E-mails Para Notificação de Pedidos Não Integrados*:** digite o endereço eletrônico desejado e, em seguida, clique em `+` sinal de adição. Você pode inserir vários emails para receberem a notificação de [pedidos da B2W que não foram integrados](https://help.vtex.com/pt/tutorial/erros-de-integracao-de-pedidos-da-b2w--2iQqCJIfySN0JsCJkOG2h8).
 - **Etiqueta dos pedidos de B2W Entrega*:** selecione o formato que você deseja para a emissão de etiquetas, se em JSON (JavaScript Object Notation) ou em PDF (Portable Document Format).  
 - **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação Cadastrar especificações ou campos de produto.  
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-  <p><b>Exemplo de nome para o novo campo:</b> <code>B2W_ProductName</code> para nome do produto e <code>B2W_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+>   **Exemplo de nome para o novo campo:** `B2W_ProductName` para nome do produto e `B2W_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
index 445130972..84221326c 100644
--- a/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
+++ b/docs/tracks/pt/configuring-the-integration-with-fbe-in-the-vtex-admin.md
@@ -22,9 +22,7 @@ Para dar início à configuração da integração, realize os seguintes passos:
 2. Por padrão, os campos sobre **região e moeda**, e **URL** da sua loja VTEX estarão preenchidos. Confira as informações e, se necessário, faça alterações.
 3. A menos que você possua uma implementação customizada do Facebook Pixel, mantenha ativada a opção _Habilitar integração de Pixel_.
 
-  <div class = "alert alert-info">
-Independente de você ter instalado a <a href= "https://apps.vtex.com/vtex-facebook-pixel/p">app Facebook Pixel</a>, a recomendação é que a opção <b>Habilitar integração de Pixel</b> permaneça ativada. A exceção é quando já se utiliza o Gerenciador de Tags do Google. Mais informações em <a href= "https://help.vtex.com/pt/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D/434Z1iWnaa0zbOMDyr6oi#pixel-do-facebook">Pixel do Facebook</a>.
-</div>
+  >ℹ️ Independente de você ter instalado a <a href= "https://apps.vtex.com/vtex-facebook-pixel/p">app Facebook Pixel</a>, a recomendação é que a opção **Habilitar integração de Pixel** permaneça ativada. A exceção é quando já se utiliza o Gerenciador de Tags do Google. Mais informações em <a href= "https://help.vtex.com/pt/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D/434Z1iWnaa0zbOMDyr6oi#pixel-do-facebook">Pixel do Facebook</a>.
 
 4. Clique em `CONTINUAR COM O FACEBOOK`.
 5. A tela seguinte solicita sua conta no Facebook. Preencha com seus dados e clique em `Entrar`. Se você tiver a [integração com o Facebook](https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc) configurada, seus dados já estarão salvos.
diff --git a/docs/tracks/pt/creating-regular-promotions.md b/docs/tracks/pt/creating-regular-promotions.md
index 11f9ca4ec..081a8f9e7 100644
--- a/docs/tracks/pt/creating-regular-promotions.md
+++ b/docs/tracks/pt/creating-regular-promotions.md
@@ -59,9 +59,7 @@ Nesta seção, você deve configurar as informações gerais da sua promoção.
      - **Frete máximo:** valor máximo que o frete poderá assumir.
      - **Frete grátis:** desconto total sobre o valor do frete.
      - **Brinde:** desconto total sobre o valor do produto definido como brinde. Ao selecionar essa opção  é possível indicar o SKU por nome ou ID que será considerado como brinde, escolher se o [multiplicador de brindes](https://help.vtex.com/pt/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK) deve ser ativado e a quantidade máxima de produtos que poderão ser utilizados como brindes na promoção.
-<div class = "alert alert-info">
-O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido gratuitamente ao cliente.
-</div>
+>ℹ️ O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido gratuitamente ao cliente.
 
    - **Desconto nominal baseado em fórmula:** o desconto é calculado com base na fórmula que você pode criar usando como variáveis a soma dos preços de produtos, o frete e a quantidade de itens. Observe que o frete considerado pela fórmula será o menor disponível para o pedido, independentemente da seleção do cliente. O separador decimal deve ser sempre o ponto. Exemplo: se o desconto for 30% do valor total do produto + valor do frete, a fórmula deve ser (total + freight) * 0.3. Para obter mais informações sobre a fórmula, leia nossa [documentação](https://help.vtex.com/pt/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
    - **Valor fidelidade nominal:** crédito que será adicionado no programa de fidelidade da loja. Leia [Promoção regular com valor fidelidade](https://help.vtex.com/pt/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) para mais informações.
@@ -70,9 +68,7 @@ O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido
 - **Informações adicionais (opcional):** permite  incluir informações adicionais a promoção composto de um nome e valor.
 - **Destaque nos produtos:** insere uma flag com o nome da promoção, utilizada na vitrine e na página do produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template `vtex.cmc:discountHightLight/>`.
 
-<div class = "alert alert-info">
-Promoções do tipo Nominal só serão apresentadas no carrinho, e não na vitrine ou na página de produto.
-</div>
+>ℹ️ Promoções do tipo Nominal só serão apresentadas no carrinho, e não na vitrine ou na página de produto.
 
 ## Restringir esta promoção a produtos dos sellers
 
@@ -83,9 +79,7 @@ Nesta seção, é possível definir para quais sellers a promoção será aplica
 
 Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
-</div>
+>⚠️ **Atenção:** não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.
 
 ## Política comercial
 
@@ -130,18 +124,14 @@ O pedido do cliente deve atender às condições cadastradas nesta seção para
 - **Tipo de frete:** o desconto será concedido caso o tipo de frete escolhido pelo cliente seja o mesmo que o cadastrado na promoção. Esse critério somente será considerado se o efeito da promoção for relativo ao Valor de Frete, ou seja, somente se for um dos seguintes efeitos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis. Importante observar que esta configuração não pode ser combinada com a opção “Aplicar desconto ao frete mais barato”, já que uma opção invalida a outra.
 - **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente:** a promoção será aplicada somente após o cliente efetivamente selecionar a forma de entrega em questão. Enquanto não for selecionada, ela ficará sem o desconto. Esse critério somente será considerado se o tipo da promoção for relativo ao valor de frete, ou seja, somente se for um dos seguintes tipos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis.
 - **Meio de pagamento:** permite escolher se a promoção será aplicada em um ou mais tipos de meios de pagamento selecionados.
-<div class = "alert alert-info">
-Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o [nosso Suporte.](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue)
-</div>
+>ℹ️ Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o [nosso Suporte.](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue)
 - **Número de parcelas:** o desconto será concedido caso o número de parcelas selecionadas pelo cliente estiver no intervalo cadastrado. Esse campo não se aplica para a seleção de boleto.
  >⚠️ Promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.
 - **utm_source:** o desconto será concedido caso a navegação seja realizada com as **utm_source** correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas um **utm_source** no checkout.
 - **utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
 - **Criar cupom a partir das UTMs acima:** cria um cupom a partir das UTMs cadastradas para dar ao cliente acesso à essa promoção sem a necessidade das utms, apenas com o código do cupom.
 - **utmi_cp:** o desconto será concedido caso a navegação seja realizada com a utmi_cp com o valor cadastrado (case sensitive).
- <div class = "alert alert-info">
-No campo das UTMs coloque somente o valor que as UTMs terão que assumir para ativar a promoção. Não é necessário colocar ?utm_source= dentro do campo.
-</div>
+ >ℹ️ No campo das UTMs coloque somente o valor que as UTMs terão que assumir para ativar a promoção. Não é necessário colocar ?utm_source= dentro do campo.
 - **Apenas na primeira compra:** o desconto só será concedido na primeira compra do cliente.
 - **Aplicar o desconto mesmo se o cliente não estiver logado:** este campo é disponibilizado quando o campo **Apenas na primeira compra** é selecionado. Se este campo é marcado, a promoção será aplicada mesmo que o consumidor não tenha inserido e-mail e senha. Quando desmarcado, a promoção somente será aplicada se o consumidor tiver acessado com e-mail e senha previamente cadastrados.
 - **Pedido de assinatura:** permite selecionar uma das opções abaixo:
diff --git a/docs/tracks/pt/facebook-business-extension.md b/docs/tracks/pt/facebook-business-extension.md
index 0c2073faf..9334475e4 100644
--- a/docs/tracks/pt/facebook-business-extension.md
+++ b/docs/tracks/pt/facebook-business-extension.md
@@ -51,6 +51,4 @@ A API de Conversões foi desenvolvida para criar uma conexão direta entre os se
 - Aprimoração da mensuração de dados de marketing.
 - Aumento do controle de dados.
 
-<div class = "alert alert-info">
-Saiba mais na documentação do Facebook <a href= "https://www.facebook.com/business/help/2041148702652965?locale=pt_BR">Sobre a API de Conversões</a>.
-</div>
+>ℹ️ Saiba mais na documentação do Facebook <a href= "https://www.facebook.com/business/help/2041148702652965?locale=pt_BR">Sobre a API de Conversões</a>.
diff --git a/docs/tracks/pt/facebook.md b/docs/tracks/pt/facebook.md
index c7d9dba42..a938f184b 100644
--- a/docs/tracks/pt/facebook.md
+++ b/docs/tracks/pt/facebook.md
@@ -14,9 +14,7 @@ trackId: 7h8KvIC4DbRRc8VlyJ8PFc
 trackSlugPT: integracao-com-o-facebook
 ---
 
-<div class = "alert alert-info">
-Existe a integração com a app <a href= "https://help.vtex.com/pt/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D">Facebook Business Extension e Conversions API</a>, que deve ser sua escolha padrão para integrar com o Facebook. Isso é válido inclusive para quem já realizou a <a href= "https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Integração com o Facebook</a>, pois a integração com a app garante as funcionalidades prévias e outras, como API de Conversões e Pixel do Facebook.
-</div>
+>ℹ️ Existe a integração com a app <a href= "https://help.vtex.com/pt/tracks/integracao-com-o-facebook-business-extension--2hS3ANSZ7vlHCcba4h7k8D">Facebook Business Extension e Conversions API</a>, que deve ser sua escolha padrão para integrar com o Facebook. Isso é válido inclusive para quem já realizou a <a href= "https://help.vtex.com/pt/tracks/integracao-com-o-facebook--7h8KvIC4DbRRc8VlyJ8PFc">Integração com o Facebook</a>, pois a integração com a app garante as funcionalidades prévias e outras, como API de Conversões e Pixel do Facebook.
 
 O [Facebook](https://about.fb.com/br/company-info/) é a rede social com maior número de usuários no mundo. Criado em 2004, é a plataforma pela qual mais de três bilhões de pessoas se conectam e compartilham informação todos os dias.
 
diff --git a/docs/tracks/pt/frontend-implementation.md b/docs/tracks/pt/frontend-implementation.md
index 4b63e57e1..d2e3939c7 100644
--- a/docs/tracks/pt/frontend-implementation.md
+++ b/docs/tracks/pt/frontend-implementation.md
@@ -24,9 +24,7 @@ Este artigo tem como objetivo auxiliar na escolha de qual tecnologia usar para c
 
 O foco da implementação de frontend é uma etapa com foco em definir as tecnologias a serem implementadas, de acordo com as necessidades do negócio relacionadas à frente de loja.
 
-<div class = "alert alert-info">
-O frontend pode ser implementado pelo time de desenvolvimento interno da empresa ou pelos nossos <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">parceiros de implementação</a>. <a href="https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512">Usuários</a> com acesso ao Admin VTEX podem consultar a lista dos nossos parceiros pelo <a href="https://partnerportal.vtex.com/">Partner Portal</a>.
-</div>
+>ℹ️ O frontend pode ser implementado pelo time de desenvolvimento interno da empresa ou pelos nossos [parceiros de implementação](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao). [Usuários](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) com acesso ao Admin VTEX podem consultar a lista dos nossos parceiros pelo [Partner Portal](https://partnerportal.vtex.com/).
 
 ## Antes de começar
 
@@ -39,9 +37,7 @@ Antes de começar a implementação do frontend, é recomendado que a loja tenha
 | Configuração do catálogo | O time configurou o [catálogo](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7#catalogo) com os produtos, a árvore de categoria e informações relacionadas, como descrições, imagens e preços, a fim de preencher e testar a loja, incluindo recursos como páginas de listagem de produtos (PLP), funcionalidade de pesquisa, páginas de detalhes de produtos (PDP) e checkout.<br><br>A ausência de um catálogo pode resultar em testes incompletos e problemas de integração de dados, atrasando a implementação.<br><br>Mais informações no artigo [Módulos da VTEX I](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7). |
 | Definição dos aplicativos necessários à operação da loja | O time definiu os aplicativos, nativos ou de terceiros, necessários para a operação da loja.<br><br>Para lojas que serão construídas usando [Store Framework](#store-framework), existe uma lista de apps nativos e de terceiros.<br><br>Mais informações no artigo [VTEX IO apps](https://developers.vtex.com/docs/vtex-io-apps). |
 
-<div class = "alert alert-info">
-A <a href="#etapas-de-desenvolvimento">etapa de desenvolvimento</a> pode acontecer em paralelo com outras etapas da <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu">Integrações de backend</a> e <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7">configuração de módulos</a>, como por exemplo as configurações de meios de pagamentos e logística. Isso vai depender do tipo de <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitetura e planejamento</a> escolhidos para a loja VTEX e deve ser acompanhado pela <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao">agência implementadora</a> ou <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">Suporte VTEX</a>.
-</div>
+>ℹ️ A [etapa de desenvolvimento](#etapas-de-desenvolvimento) pode acontecer em paralelo com outras etapas da [Integrações de backend](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/7euXDZR5CCnVFSrXyczIhu) e [configuração de módulos](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/75MX4aorniD0BYAB8Nwbo7), como por exemplo as configurações de meios de pagamentos e logística. Isso vai depender do tipo de [arquitetura e planejamento](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) escolhidos para a loja VTEX e deve ser acompanhado pela [agência implementadora](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#parceiros-de-implementacao) ou [Suporte VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8).
 
 ## Tecnologias de desenvolvimento de frontend na VTEX
 
@@ -119,9 +115,7 @@ Para lojas B2B, o Store Framework é uma ótima opção, uma vez que disponibili
 
 A FastStore é uma alternativa em evolução mais recente focada na performance da loja. Esta solução oferece uma experiência de carregamento rápido, o que é essencial para manter os visitantes da loja engajados e reduzir as taxas de abandono de carrinho. Para casos de uso mais simples e com foco em performance, a FastStore pode ser a tecnologia mais recomendada. 
 
-<div class = "alert alert-info">
-A equipe de <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">suporte da VTEX</a> pode auxiliar no momento de escolher entre uma das tecnologias de storefront disponíveis.
-</div>
+>ℹ️ A equipe de [suporte da VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) pode auxiliar no momento de escolher entre uma das tecnologias de storefront disponíveis.
 
 A tabela abaixo compara as duas tecnologias de acordo com suas principais funcionalidades:
 
@@ -214,9 +208,7 @@ Antes de lançar a loja em produção e do [go-live](https://help.vtex.com/pt/tr
 - [Requisitos para um MVP da FastStore](#requisitos-para-um-mvp-da-faststore)
 - [Requisitos para um MVP do Store Framework](#requisitos-para-um-mvp-do-store-framework)
 
-<div class = "alert alert-info">
-As recomendações a seguir são para configurações básicas de frente de loja. Dependendo da <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl">arquitetura escolhida</a> para a operação da loja, outras configurações podem ser necessárias.
-</div>
+>ℹ️ As recomendações a seguir são para configurações básicas de frente de loja. Dependendo da [arquitetura escolhida](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl) para a operação da loja, outras configurações podem ser necessárias.
 
 ### Desenvolvendo com a FastStore
 
diff --git a/docs/tracks/pt/getting-started-with-logistics.md b/docs/tracks/pt/getting-started-with-logistics.md
index 201a3745e..90e8d6c01 100644
--- a/docs/tracks/pt/getting-started-with-logistics.md
+++ b/docs/tracks/pt/getting-started-with-logistics.md
@@ -38,10 +38,8 @@ A trilha reúne os artigos:
 * [Custos e simulação de envio](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/3by48jFhzpZEseYFpH9uVt): explica como cadastrar custos de envio e como utilizar a ferramenta de simulação de frete da loja.
 * [Entregas agendadas e capacidade de entregas](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/5TuyqHRCCwYMaDv4r8rZdo): explica como a loja deve disponibilizar entregas agendadas para os clientes, além de gerenciar a capacidade de realização desse tipo de entrega. 
 
-<div class = "alert alert-info">
-Se a sua loja já trilhou os primeiros passos do módulo <b>Estoque & entrega</b>, confira o artigo <a href="https://help.vtex.com/pt/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP">Logística</a>, para ter acesso rápido às informações das seções do módulo <b>Estoque & entrega.</b> 
-Confira o artigo <a href="https://help.vtex.com/pt/tutorial/glossario-de-logistica--16DSSiXn548rsidi0A8Hby">Glossário de logística</a>, para conhecer os significados de termos logísticos utilizados na VTEX. Há também as configurações de logística disponíveis via <a href="https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview">API</a>. 
-</div>
+>ℹ️ Se a sua loja já trilhou os primeiros passos do módulo **Estoque & entrega**, confira o artigo [Logística](https://help.vtex.com/pt/tutorial/logistica--53udnvI5eBy8DKo8FOjMoP), para ter acesso rápido às informações das seções do módulo **Estoque & entrega.** 
+> Confira o artigo [Glossário de logística](https://help.vtex.com/pt/tutorial/glossario-de-logistica--16DSSiXn548rsidi0A8Hby), para conhecer os significados de termos logísticos utilizados na VTEX. Há também as configurações de logística disponíveis via [API](https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview).
 
 De forma resumida, o módulo **Estoque & entrega** divide-se nas seguintes seções:
 
@@ -57,9 +55,7 @@ De forma resumida, o módulo **Estoque & entrega** divide-se nas seguintes seç
 
     ![estoque e entregaPT](https://images.ctfassets.net/alneenqid6w5/21rlEVE55jPh2hYBKTn99U/4dff7a2616eb80d8ec89344ec2d2363c/estoque_e_entregaPT.png)
 
-<div class = "alert alert-info">
-  Clientes que utilizam o <a href="https://vtex.com/br-pt/log/"><b>VTEX Shipping Network</a></b> acessam a funcionalidade pelo módulo <b>Estoque & Entrega</b>.
-</div>
+>ℹ️ Clientes que utilizam o [**VTEX Shipping Network](https://vtex.com/br-pt/log/)** acessam a funcionalidade pelo módulo **Estoque & Entrega**.
 
 Confira os próximos artigos da trilha para saber a ordem em que essas seções devem ser configuradas e como a plataforma interpreta essas configurações.
 
diff --git a/docs/tracks/pt/go-live-process.md b/docs/tracks/pt/go-live-process.md
index 52ab55ce2..c50567745 100644
--- a/docs/tracks/pt/go-live-process.md
+++ b/docs/tracks/pt/go-live-process.md
@@ -20,9 +20,7 @@ Neste tutorial você encontra o passo a passo detalhado de como realizar o go-li
 
 ![Go-live](https://images.ctfassets.net/alneenqid6w5/1DBW4Cw10Z3Gt4orXMAqWE/032594f36e1fe4fda13252502060b753/go_live_pt.jpg)
 
-<div class = "alert alert-info">
-Note que uma loja em produção é diferente de uma conta em produção. De modo geral, pode-se dizer que para ter uma loja em produção é necessário colocar a conta em produção e realizar o apontamento de DNS. Confira abaixo todos os passos envolvidos nesse processo.
-</div>
+>ℹ️ Note que uma loja em produção é diferente de uma conta em produção. De modo geral, pode-se dizer que para ter uma loja em produção é necessário colocar a conta em produção e realizar o apontamento de DNS. Confira abaixo todos os passos envolvidos nesse processo.
 
 ## Antes de começar
 
@@ -36,9 +34,7 @@ Copie esta [Checklist de configuração de loja](https://assets.ctfassets.net/al
 
 O processo de go-live da sua loja pode ter variações dependendo de algumas características da sua operação. Além disso, alguns passos são sensíveis ao tempo. Por esses motivos recomendamos que planeje o processo completo do seu go-live com no mínimo 15 dias de antecedência.
 
-<div class = "alert alert-info">
-  <p>Se você usa o CMS Legado Portal e deseja migrar para uma frente de loja construída com <a href="https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, siga as instruções no guia <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migrando sua frente de loja do CMS Legado Portal para Store Framework</a>.</p>
-</div>
+>ℹ️ Se você usa o CMS Legado Portal e deseja migrar para uma frente de loja construída com [VTEX IO](https://help.vtex.com/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), siga as instruções no guia [Migrando sua frente de loja do CMS Legado Portal para Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 Por motivo de organização e conveniência, este guia divide os passos envolvidos no go-live em quatro estágios:
 
diff --git a/docs/tracks/pt/how-does-vtex-intelligent-search-work.md b/docs/tracks/pt/how-does-vtex-intelligent-search-work.md
index 5db51f9b1..25c24eed7 100644
--- a/docs/tracks/pt/how-does-vtex-intelligent-search-work.md
+++ b/docs/tracks/pt/how-does-vtex-intelligent-search-work.md
@@ -49,9 +49,7 @@ Exemplo: suponha que um cliente queira pesquisar pelo termo `bola`. Seguindo a c
 * `bora` (trocar 1 caractere)
 * `obla` (trocar 2 caracteres que ficam um do lado do outro entre eles)
 
-<div class ="alert alert-info">
-	<p>Espaços em branco não são considerados no <em>fuzzy</em>, então <code>base ball</code> não será corrigido para <code>baseball</code>, por exemplo. Recomendamos o uso de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinônimos</a> para esses casos.</p>
-</div>
+>ℹ️ Espaços em branco não são considerados no *fuzzy*, então `base ball` não será corrigido para `baseball`, por exemplo. Recomendamos o uso de [sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) para esses casos.
 
 ### Resultado mínimo
 
@@ -62,9 +60,7 @@ Em uma busca com múltiplos termos, ocorre a lógica a seguir:
 1. Se o resultado mínimo não for atingido mesmo com a autocorreção inicial, a busca passa a incluir resultados mais abrangentes, que apresentam qualquer um dos termos pesquisados. Por exemplo, quando um usuário pesquisa por "tenis nike", mas o catálogo não possui nenhum produto com esse nome, a busca pode apresentar como resultado um produto com apenas o termo "tenis" no nome.
 2. Se a busca abrangente não apresentar o resultado mínimo, ela será repetida aplicando a autocorreção novamente a cada um dos termos.
 
-<div class= "alert alert-warning">
-<p>Buscas com múltiplos termos são mais eficientes quando o cliente ordena os resultados por relevância, já que elas podem ter um número maior de resultados além do contexto que foi buscado. Na ordenação por relevância, ainda priorizam-se os itens relacionados aos múltiplos termos. Porém, ao aplicar outras ordenações, como preço ou mais vendidos, a ordem dos resultados depende desses valores numéricos e não necessariamente prioriza itens que contêm mais palavras dos termos de busca.</p>
-</div>
+>⚠️ Buscas com múltiplos termos são mais eficientes quando o cliente ordena os resultados por relevância, já que elas podem ter um número maior de resultados além do contexto que foi buscado. Na ordenação por relevância, ainda priorizam-se os itens relacionados aos múltiplos termos. Porém, ao aplicar outras ordenações, como preço ou mais vendidos, a ordem dos resultados depende desses valores numéricos e não necessariamente prioriza itens que contêm mais palavras dos termos de busca.
 
 ### Limite de paginação
 
@@ -88,9 +84,7 @@ _Exemplo_: foi configurado que a especificação "cor" é pesquisável e o produ
 
 É possível buscar por caracteres especiais (`-` e `/`) para encontrar um produto.
 
-<div class ="alert alert-warning">
-	<p>A escolha dos campos de busca afeta as possibilidades das <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">Regras de merchandising</a>, pois apenas campos pesquisáveis podem ser utilizados para configurar as regras. Por exemplo, ao definir somente o campo <strong><code>SKUID</code> </strong>como pesquisável, não será possível promover um <strong><code>ProductID</code> </strong>ou um <strong><code>ProductRefID</code> </strong>utilizando Regras de merchandising.</p>
-</div>
+>⚠️ A escolha dos campos de busca afeta as possibilidades das [Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), pois apenas campos pesquisáveis podem ser utilizados para configurar as regras. Por exemplo, ao definir somente o campo **`SKUID` **como pesquisável, não será possível promover um **`ProductID` **ou um **`ProductRefID` **utilizando Regras de merchandising.
 
 ### Definição e ordenação de campos de filtro
 
@@ -104,9 +98,7 @@ _Exemplo_: um lojista configurou que o critério Promoção possui uma relevânc
 
 Para mais informações sobre como personalizar a ordenação dos resultados de acordo com as necessidades da sua loja, leia o artigo [Configuração de relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
 
-<div class ="alert alert-info">
-	<p>Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções. Usando o comando <code>map=productClusterIds</code>, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar <code>productClusterNames</code>, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search.</p>
-</div>
+>ℹ️ Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções. Usando o comando `map=productClusterIds`, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar `productClusterNames`, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search.
 
 ## Formas alternativas de busca
 
diff --git a/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md b/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
index d6f448462..e03934d75 100644
--- a/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
+++ b/docs/tracks/pt/how-to-create-and-edit-transactional-email-templates.md
@@ -23,9 +23,7 @@ Para editar um template de e-mail transacional, siga os passos abaixo.
 3. Altere o título do e-mail e o destinatário (os valores entre chaves duplas são variáveis; vamos aprender no próximo artigo como lidar com elas). Você pode incluir destinatários em cópia (`CC`) e cópia oculta (`CCO`).
 4. Deixe a flag __Usar o remetente padrão__ para usar o endereço de e-mail cadastrado como padrão, conforme explicado no artigo anterior desta trilha.
 
-<div class = "alert alert-info">
-A lista de templates está disponível no artigo <a href="https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my">Templates de emails transacionais referentes ao pedido</a>.
-</div>
+>ℹ️ A lista de templates está disponível no artigo [Templates de emails transacionais referentes ao pedido](https://help.vtex.com/pt/tutorial/templates-de-emails-transacionais--3g2S2kqBOoSGcCaqMYK2my).
 
 É no campo __HTML__ que você encontra o código HTML do template. Você pode editar o código no próprio campo ou copiá-lo para o editor de sua preferência, editar e depois colar novamente no campo do template.
 
diff --git a/docs/tracks/pt/installing-the-facebook-business-extension-e-conversions-api-app.md b/docs/tracks/pt/installing-the-facebook-business-extension-e-conversions-api-app.md
index 51ab803cc..469a2d53c 100644
--- a/docs/tracks/pt/installing-the-facebook-business-extension-e-conversions-api-app.md
+++ b/docs/tracks/pt/installing-the-facebook-business-extension-e-conversions-api-app.md
@@ -26,6 +26,4 @@ Na VTEX App Store, está disponível a app _Facebook Business Extension e Conver
 
 A app estará disponível no seu Admin VTEX, no módulo **CONFIGURAÇÕES DA CONTA > Aplicativos > Meus Aplicativos**, na aba **Instaladas**.
 
-<div class = "alert alert-info">
-Também é possível instalar a app <i>Facebook Business Extension e Conversions API</i> pelo <i>Toolbelt</i> do VTEX IO. Saiba mais em <a href= "https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-installing-an-app">Installing an app</a>.
-</div>
+>ℹ️ Também é possível instalar a app <i>Facebook Business Extension e Conversions API</i> pelo <i>Toolbelt</i> do VTEX IO. Saiba mais em <a href= "https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-installing-an-app">Installing an app</a>.
diff --git a/docs/tracks/pt/integration-configurations.md b/docs/tracks/pt/integration-configurations.md
index a7a99f5f6..0350880fe 100644
--- a/docs/tracks/pt/integration-configurations.md
+++ b/docs/tracks/pt/integration-configurations.md
@@ -62,10 +62,8 @@ _Ex: o preço de envio para todo o Brasil é R$ 20,00 enquanto que para a Argent
 
 _Ex: o preço de envio para Rio de Janeiro (região metropolitana) é de R$ 10,00, enquanto que para o Rio de Janeiro (interior) é de R$ 15,00._
 
-<div class = "alert alert-info">
-  OBS: o envio por região está disponível apenas para sellers que usam <strong>Wish Express</strong> <a href="https://merchantfaq.wish.com/hc/pt/articles/360018939394-Como-enviar-usando-o-Wish-Express-Brasil-">(saiba mais aqui).</a>
- Para configurar a Wish Express, basta seguir <a href="https://merchantfaq.wish.com/hc/pt/articles/232047747-Wish-Express-Fluxo-de-Inscri%C3%A7%C3%A3o">estes passos.</a>
-  </div>
+>ℹ️ OBS: o envio por região está disponível apenas para sellers que usam **Wish Express** [(saiba mais aqui).](https://merchantfaq.wish.com/hc/pt/articles/360018939394-Como-enviar-usando-o-Wish-Express-Brasil-)
+>  Para configurar a Wish Express, basta seguir [estes passos.](https://merchantfaq.wish.com/hc/pt/articles/232047747-Wish-Express-Fluxo-de-Inscri%C3%A7%C3%A3o)
   
 Indique no setup se você usará Wish Express. Caso não use, pode pular para o passo seguinte.
 
@@ -84,8 +82,7 @@ Para indicar qual transportadora da sua loja corresponde às [transportadoras ac
 
   3. Clique no botão “Salvar” para concluir.
 
-<div class = "alert alert-info">
-  OBS: caso seja mapeada alguma transportadora não-certificada pela Wish, os pedidos não poderão ser rastreados e, consequentemente, <strong>não haverá</strong> repasse da comissão. Então é necessário ser bem cauteloso nesta etapa.</div>
+>ℹ️ OBS: caso seja mapeada alguma transportadora não-certificada pela Wish, os pedidos não poderão ser rastreados e, consequentemente, **não haverá** repasse da comissão. Então é necessário ser bem cauteloso nesta etapa.
 
 ## Taxa de divergência de preço
  
diff --git a/docs/tracks/pt/integration-overview-b2w.md b/docs/tracks/pt/integration-overview-b2w.md
index ed691a151..e81a3c94c 100644
--- a/docs/tracks/pt/integration-overview-b2w.md
+++ b/docs/tracks/pt/integration-overview-b2w.md
@@ -18,9 +18,7 @@ A B2W e as Lojas Americanas fizeram uma fusão, dando origem ao Americanas Marke
 
 Para dar início à integração, o primeiro passo é fazer o [cadastro da sua loja](https://americanasmarketplace.com.br/v3/registre-se/vtex?utm_source=vtex&utm_medium=vtex_homepage&utm_campaign=parceiro_vtex_cadastro) no portal da Americanas. Feito isso, realize seu cadastro na [SkyHub](https://ajuda.skyhub.com.br/hc/pt-br).
 
-<div class = "alert alert-info">
-A <a href="https://ajuda.skyhub.com.br/hc/pt-br">SkyHub</a> é a integradora que gerencia a comunicação entre VTEX e a B2W. Portanto, a integração é feita com a SkyHub, que é a responsável pelo envio dos seus produtos para o marketplace.
-</div>
+>ℹ️ A [SkyHub](https://ajuda.skyhub.com.br/hc/pt-br) é a integradora que gerencia a comunicação entre VTEX e a B2W. Portanto, a integração é feita com a SkyHub, que é a responsável pelo envio dos seus produtos para o marketplace.
 
 Uma vez recebida a confirmação do Americanas Marketplace, prossiga com as configurações no ambiente VTEX:
 
diff --git a/docs/tracks/pt/inventory.md b/docs/tracks/pt/inventory.md
index 624aece30..fedc01e7b 100644
--- a/docs/tracks/pt/inventory.md
+++ b/docs/tracks/pt/inventory.md
@@ -16,9 +16,7 @@ trackSlugPT: logistica-101
 
 O inventário é a funcionalidade de gerenciamento dos produtos disponíveis para venda. Depois que os[ produtos são cadastrados](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) no [catálogo](https://help.vtex.com/pt/tracks/catalogo-101--5AF0XfnjfWeopIFBgs3LIQ/3rA2tTpIoEXdv2nzC27zxR), é preciso adicioná-los a um estoque da loja para que eles fiquem de fato disponíveis para venda. O módulo [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) é onde os itens do catálogo são vinculados a um estoque.
 
-<div class = "alert alert-info">
-Lembre-se de adicionar pelo menos um <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">estoque</a> em sua loja antes de usufruir do <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">Inventário</a>. 
-</div>
+>ℹ️ Lembre-se de adicionar pelo menos um [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) em sua loja antes de usufruir do [Inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
 Com o inventário, o lojista também pode conferir:
 
@@ -31,9 +29,7 @@ Para inserir itens em massa no inventário, utilize a planilha de importação d
 
 Utilize o[ alerta de estoque crítico](https://help.vtex.com/pt/tutorial/configurar-o-alerta-de-estoque-critico--6FD0GHeQPCsKIMgkQ88SGu) para receber notificações de itens que estão próximos de serem esgotados.
 
-<div class = "alert alert-info">
-As configurações do inventário também podem ser feitas via  <a href="https://developers.vtex.com/vtex-rest-api/reference/inventory">API de inventário</a>.
-</div>
+>ℹ️ As configurações do inventário também podem ser feitas via  [API de inventário](https://developers.vtex.com/vtex-rest-api/reference/inventory).
 
 ### Saiba mais
 
diff --git a/docs/tracks/pt/managing-sales-associates-in-instore.md b/docs/tracks/pt/managing-sales-associates-in-instore.md
index ceb6967dc..560810e0e 100644
--- a/docs/tracks/pt/managing-sales-associates-in-instore.md
+++ b/docs/tracks/pt/managing-sales-associates-in-instore.md
@@ -40,9 +40,7 @@ Você pode cadastrar um vendedor seguindo os passos abaixo:
 
 Após o cadastro, o vendedor irá receber um email de confirmação do cadastramento, e com redirecionamento para a opção de login do vendedor ao aplicativo Sales App.
 
-<div class ="alert alert-warning">
-<p>Os vendedores cadastrados no Sales App não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin, seu cadastro será excluído.</p> 
-</div>
+>⚠️ Os vendedores cadastrados no Sales App não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin, seu cadastro será excluído.
 
 ### Campos de cadastro do vendedor
 
@@ -57,9 +55,7 @@ Após o cadastro, o vendedor irá receber um email de confirmação do cadastram
 
 * **Loja:** [conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) em que o vendedor será cadastrado. Campo obrigatório.
 
-<div class ="alert alert-info">
-<p>As alterações podem levar até 15 minutos para serem processadas e aplicadas no Sales App.</p> 
-</div>
+>ℹ️ As alterações podem levar até 15 minutos para serem processadas e aplicadas no Sales App.
 
 ## Buscar vendedor
 
diff --git a/docs/tracks/pt/manual-product-matching-on-amazon.md b/docs/tracks/pt/manual-product-matching-on-amazon.md
index 61f9fdc0b..804ea6c72 100644
--- a/docs/tracks/pt/manual-product-matching-on-amazon.md
+++ b/docs/tracks/pt/manual-product-matching-on-amazon.md
@@ -27,6 +27,4 @@ Após realizar o [envio desses produtos](https://help.vtex.com/pt/tracks/configu
 
 Após ter feito a confirmação do ASIN, você terá concluído o *matching* do produto.
 
-<div class = "alert alert-danger">
-Ainda é possível utilizar o <em>matching</em> automático através da sua ativação no card da integração, entretanto o seller assume a responsabilidade por possíveis <em>mismatchs</em>(erro de compatibilidade) que esse fluxo pode gerar.
-</div>
+>❗ Ainda é possível utilizar o *matching* automático através da sua ativação no card da integração, entretanto o seller assume a responsabilidade por possíveis *mismatchs*(erro de compatibilidade) que esse fluxo pode gerar.
diff --git a/docs/tracks/pt/mapping-colors-and-sizes.md b/docs/tracks/pt/mapping-colors-and-sizes.md
index b3b706bf7..6b7db208b 100644
--- a/docs/tracks/pt/mapping-colors-and-sizes.md
+++ b/docs/tracks/pt/mapping-colors-and-sizes.md
@@ -18,13 +18,9 @@ Depois de fazer as configurações iniciais para a integração com a Wish, agor
 
 O envio dessas informações é feito por meio do upload da planilha de mapeamento, que contém um de/para. O mapeamento só será feito uma vez para cada categoria. Isso significa que, já tendo feito o mapeamento uma vez, os novos produtos que forem criados vão ser integrados diretamente na categoria correta (e com suas respectivas variações e atributos).
 
-<div class = "alert alert-info">
-É preciso realizar o mapeamento de categoria para que a Wish possa diferenciar os seus SKUs corretamente. Exemplo: imagine que existam dois SKUs de um mesmo produto com cores diferentes e tamanhos iguais na VTEX, caso o mapeamento de categoria não seja realizado, a Wish reconhecerá os dois SKUs como um só. 
-</div>
+>ℹ️ É preciso realizar o mapeamento de categoria para que a Wish possa diferenciar os seus SKUs corretamente. Exemplo: imagine que existam dois SKUs de um mesmo produto com cores diferentes e tamanhos iguais na VTEX, caso o mapeamento de categoria não seja realizado, a Wish reconhecerá os dois SKUs como um só.
 
-<div class = "alert alert-warning">
-Produtos sem cor ou tamanho mapeados não serão enviados para a Wish. Caso alguma categoria não tenha estes campos na VTEX, será necessário <a href="https://help.vtex.com/pt/tutorial/criando-campo-de-sku--tutorials_119">criar um campo de SKU</a> no Catálogo e preencher com os valores adequados antes de realizar o mapeamento de cor e tamanho.
-</div>
+>⚠️ Produtos sem cor ou tamanho mapeados não serão enviados para a Wish. Caso alguma categoria não tenha estes campos na VTEX, será necessário [criar um campo de SKU](https://help.vtex.com/pt/tutorial/criando-campo-de-sku--tutorials_119) no Catálogo e preencher com os valores adequados antes de realizar o mapeamento de cor e tamanho.
 
   - [Baixe aqui](https://drive.google.com/uc?export=download&id=1yJCgahkDhc4Gbvtxpe9kID1CwWsijdOf) a Planilha de Mapeamento da Wish no formato .xlsx.
 
@@ -61,9 +57,7 @@ Repare que na VTEX o nome dos campos é "Cores" e "Tamanhos", mas a Wish chama d
 Na VTEX, os produtos dessa categoria possuem duas cores possíveis: vermelho e gelo. 
 Deve-se escolher a cor disponível mais próxima que, no caso da Wish, "Gelo" poderia ser "White/Ice Glaze" (baseado na [lista de cores aceitas](https://merchant.wish.com/documentation/colors)). E "Vermelho" poderia ser "Red".
 
-<div class = "alert alert-info">
-  OBS: o cabeçalho da tabela deve ser preenchida exatamente como está no exemplo abaixo. Lembre-se de não adicionar caracteres especiais como enter ou espaço no preenchimento dessa tabela. 
-  </div>
+>ℹ️ OBS: o cabeçalho da tabela deve ser preenchida exatamente como está no exemplo abaixo. Lembre-se de não adicionar caracteres especiais como enter ou espaço no preenchimento dessa tabela.
 
 ![PT - Tabela Wish](https://images.ctfassets.net/alneenqid6w5/5fvuqSjSRGHwbFVNUSTM3T/6f8f13054b1be01cbd1340d7b5b90bbd/Tabela_Wish.png)
 
diff --git a/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md b/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
index 16ec1a5dd..dfdd2dfad 100644
--- a/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
+++ b/docs/tracks/pt/mapping-product-categories-and-attributes-to-mercado-libre.md
@@ -21,9 +21,7 @@ Para enviar os seus produtos para o Mercado Livre, você deverá:
 1. [Mapear as categorias dos produtos](#mapear-categorias)
 2. [Mapear os atributos dos produtos](#mapear-atributos)
 
-<div class = "alert alert-info">
-Seus produtos precisam ter o <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a> e <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">Preço</a> configurados antes de enviá-los ao Mercado Livre.
-</div>
+>ℹ️ Seus produtos precisam ter o [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [Preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) configurados antes de enviá-los ao Mercado Livre.
 
 ## Mapear categorias
 
diff --git a/docs/tracks/pt/opening-tickets.md b/docs/tracks/pt/opening-tickets.md
index bf4ef83af..e99082a6a 100644
--- a/docs/tracks/pt/opening-tickets.md
+++ b/docs/tracks/pt/opening-tickets.md
@@ -22,9 +22,7 @@ O acesso a uma conta VTEX possibilita acessar o [painel de suporte](https://supp
 
 ![Support imagem 1 - PT](https://images.ctfassets.net/alneenqid6w5/75ezzwg9iant6cmq04FhTz/8b56af5455d0c5ce1879a98aaa6b6768/support_imagem1_PT.gif)
 
-<div class = "alert alert-info">
-Para obter mais informações sobre como abrir um chamado e sobre tipos de chamado, basta acessar o artigo <a href="https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex">Abrir chamados para o suporte VTEX</a>.
-</div>
+>ℹ️ Para obter mais informações sobre como abrir um chamado e sobre tipos de chamado, basta acessar o artigo [Abrir chamados para o suporte VTEX](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex).
 
 ## Tipos de suporte
 
diff --git a/docs/tracks/pt/partial-invoices.md b/docs/tracks/pt/partial-invoices.md
index bd8b533ed..6f76aa79e 100644
--- a/docs/tracks/pt/partial-invoices.md
+++ b/docs/tracks/pt/partial-invoices.md
@@ -34,9 +34,7 @@ As faturas parciais causam as seguintes ações no OMS, e demais sistemas da VTE
 * Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido faturados parcialmente. Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 * Valores maiores ou iguais ao total do pedido seguem o fluxo para faturado. Qualquer nota inserida além desses valores entrará como Nota Fiscal Avulsa que não receberá atualização de tracking.  
 
-<div class = "alert alert-info">
-A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Conectores legados não possuem suporte à funcionalidade.
-</div>
+>ℹ️ A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Conectores legados não possuem suporte à funcionalidade.
 
 ## Enviar fatura parcial
 
@@ -55,9 +53,7 @@ Para enviar uma fatura parcial, siga os passos abaixo:
 
 É possível acompanhar todos os eventos da transação, após as mudanças ocorridas ao pedido, ao clicar em [Ver detalhes da transação](https://help.vtex.com/pt/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/3Nt40DMEWkvhlpaL5PlBy).
 
-<div class = "alert alert-info">
-Também é possível realizar as mesmas ações por meio da nossa API de Orders. Para isso, confira os endpoints: <a href="https://developers.vtex.com/vtex-rest-api/reference/registerchange">Register Change on Order</a>, <a href="https://developers.vtex.com/vtex-rest-api/reference/invoicenotification">Invoice notification</a>, <a href="https://developers.vtex.com/vtex-rest-api/reference/getpaymenttransaction">Retrieve Payment transaction</a>, e <a href="https://developers.vtex.com/vtex-rest-api/reference/updatepartialinvoicesendtrackingnumber">Update order's partial invoice (send tracking number)</a>.
-  </div>
+>ℹ️ Também é possível realizar as mesmas ações por meio da nossa API de Orders. Para isso, confira os endpoints: [Register Change on Order](https://developers.vtex.com/vtex-rest-api/reference/registerchange), [Invoice notification](https://developers.vtex.com/vtex-rest-api/reference/invoicenotification), [Retrieve Payment transaction](https://developers.vtex.com/vtex-rest-api/reference/getpaymenttransaction), e [Update order's partial invoice (send tracking number)](https://developers.vtex.com/vtex-rest-api/reference/updatepartialinvoicesendtrackingnumber).
 
 ## Saiba mais
 
diff --git a/docs/tracks/pt/pre-go-live.md b/docs/tracks/pt/pre-go-live.md
index 3fdc3eb9a..4ae471132 100644
--- a/docs/tracks/pt/pre-go-live.md
+++ b/docs/tracks/pt/pre-go-live.md
@@ -28,9 +28,7 @@ Se sua frente de loja é feita com [CMS IO](https://help.vtex.com/pt/tracks/cms-
 
 Após receber a confirmação do apontamento interno, você deverá realizar o [apontamento comum de DNS](https://help.vtex.com/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/12bQlMbJ68Ot0LIaO6Btkj#realizar-apontamento-de-dns) em até cinco dias. Do contrário o apontamento interno será excluído e você precisará refazer esta solicitação.
 
-<div class = "alert alert-info">
-Saiba mais sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live">go-live com Store Framework</a> ou <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migração do CMS legado para Store Framework</a>.
-</div>
+>ℹ️ Saiba mais sobre [go-live com Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live) ou [Migração do CMS legado para Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 ## Solicitar apontamento especial
 
diff --git a/docs/tracks/pt/registering-the-carrefour-integration.md b/docs/tracks/pt/registering-the-carrefour-integration.md
index 4288457fd..622a98e83 100644
--- a/docs/tracks/pt/registering-the-carrefour-integration.md
+++ b/docs/tracks/pt/registering-the-carrefour-integration.md
@@ -45,9 +45,7 @@ Caso a categoria de produtos não exija o mapeamento de certificados, o campo de
 
 - __Política comercial*__: ID da [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será utilizada para a integração com o Carrefour. São os produtos dessa política comercial que serão enviados para o marketplace.
 
-<div class = "alert alert-info">
-  Preencha ao menos um dos campos do <b>mapeamento de SLA</b> mesmo que eles não sejam obrigatórios. Caso nenhum deles seja preenchido, não será possível simular o frete na VTEX e, consequentemente, os pedidos feitos no Carrefour não serão integrados.
-</div>
+>ℹ️ Preencha ao menos um dos campos do **mapeamento de SLA** mesmo que eles não sejam obrigatórios. Caso nenhum deles seja preenchido, não será possível simular o frete na VTEX e, consequentemente, os pedidos feitos no Carrefour não serão integrados.
 
 - __Mapeamento de SLA de tipo Normal*:__ preencha com o nome do [Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126) cadastrado na [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_1400). Por exemplo, se você cadastrou como `Normal`, então, deve preencher esse campo o nome exatamente igual.
 - __Mapeamento de SLA de tipo Expressa*:__ preencha com o nome do [Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126) cadastrado na [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_1400). Por exemplo, se você cadastrou como `Expressa`, então, deve preencher esse campo o nome exatamente igual.
@@ -55,10 +53,8 @@ Caso a categoria de produtos não exija o mapeamento de certificados, o campo de
 - __Mapeamento de SLA de tipo Agendada*:__ preencha com o nome do [Método de Envio](https://help.vtex.com/pt/tutorial/como-funciona-o-tipo-de-entrega--tutorials_126) cadastrado na [Política de Envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_1400). Por exemplo, se você cadastrou como `Agendada`, então, deve preencher esse campo o nome exatamente igual.
 - **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-  <p><b>Exemplo de nome para o novo campo:</b> <code>CRF_ProductName</code> para nome do produto e <code>CRF_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+>   **Exemplo de nome para o novo campo:** `CRF_ProductName` para nome do produto e `CRF_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/registering-the-centauro-integration.md b/docs/tracks/pt/registering-the-centauro-integration.md
index 4abca4422..930fe93d6 100644
--- a/docs/tracks/pt/registering-the-centauro-integration.md
+++ b/docs/tracks/pt/registering-the-centauro-integration.md
@@ -35,10 +35,8 @@ Nessa etapa, você realizará o cadastro da sua loja na integração da Centauro
 
 **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-  <p><b>Exemplo de nome para o novo campo:</b> <code>CTR_ProductName</code> para nome do produto e <code>CTR_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+>   **Exemplo de nome para o novo campo:** `CTR_ProductName` para nome do produto e `CTR_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/registering-the-integration.md b/docs/tracks/pt/registering-the-integration.md
index 28f36ef09..91640b965 100644
--- a/docs/tracks/pt/registering-the-integration.md
+++ b/docs/tracks/pt/registering-the-integration.md
@@ -38,10 +38,8 @@ O cadastro do conector é feito no Admin da VTEX. Para realizá-lo, siga as inst
 
 **Mapeamento de Campos Customizados (Nome e descrição):**  Para utilizar esse mapeamento é necessário criar um campo customizado. Para saber como criar campos customizados, acesse a documentação [Cadastrar especificações ou campos de produto](https://help.vtex.com/pt/tutorial/criando-um-campo-de-produto--tutorials_106).  
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-<p><b>Exemplo de nome para o novo campo:</b> <code>CBH_ProductName</code> para nome do produto e <code>CBH_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+> **Exemplo de nome para o novo campo:** `CBH_ProductName` para nome do produto e `CBH_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/registering-the-netshoes-integration.md b/docs/tracks/pt/registering-the-netshoes-integration.md
index bd7c752bf..6096aa75c 100644
--- a/docs/tracks/pt/registering-the-netshoes-integration.md
+++ b/docs/tracks/pt/registering-the-netshoes-integration.md
@@ -52,10 +52,8 @@ trackSlugPT: configurar-integracao-da-netshoes
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
-<div class = "alert alert-info">
-  O mapeamento de campos customizáveis está disponível apenas para <b>nome do produto</b> e <b>descrição do produto</b>.
-  <p><b>Exemplo de nome para o novo campo:</b> <code>NTS_ProductName</code> para nome do produto e <code>NTS_ProductDescription</code> para descrição do produto.</p>
-</div>  
+>ℹ️ O mapeamento de campos customizáveis está disponível apenas para **nome do produto** e **descrição do produto**.
+>   **Exemplo de nome para o novo campo:** `NTS_ProductName` para nome do produto e `NTS_ProductDescription` para descrição do produto.  
 
 Para o mapeamento funcionar, é necessário o seller seguir os seguintes passos:  
 
diff --git a/docs/tracks/pt/reports-vtex-intelligent-search.md b/docs/tracks/pt/reports-vtex-intelligent-search.md
index d93486627..ae4082c7e 100644
--- a/docs/tracks/pt/reports-vtex-intelligent-search.md
+++ b/docs/tracks/pt/reports-vtex-intelligent-search.md
@@ -23,9 +23,7 @@ Siga os passos abaixo para acessar a página:
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
 2. Em __Intelligent Search__, clique em __Analytics__. 
 
-<div class = "alert alert-info">
-<p>A página de <strong>Analytics</strong> é nativa no VTEX Intelligent Search. Não é possível desabilitá-la no Admin.</p>
-</div>
+>ℹ️ A página de **Analytics** é nativa no VTEX Intelligent Search. Não é possível desabilitá-la no Admin.
 
 ## Dados
 
@@ -71,9 +69,7 @@ Para exportar um relatório no formato CSV, você deve seguir os passos abaixo.
 5. Espere o arquivo estar disponível para download. Sair desta página não interrompe o processo.
 6. Clique em `Baixar`.
 
-<div class = "alert alert-info">
-<p>O arquivo permanece disponível para download por 48 horas.</p>
-</div>
+>ℹ️ O arquivo permanece disponível para download por 48 horas.
 
 O relatório CSV baixado apresenta duas tabelas. A primeira tabela, ilustrada abaixo, contém informações sobre termos pesquisados e as métricas de funil (da coluna **ProductsClick** até a coluna **ProductsSold**), caso essa opção tenha sido selecionada.
 
diff --git a/docs/tracks/pt/sending-product-data-to-dafiti.md b/docs/tracks/pt/sending-product-data-to-dafiti.md
index 874453114..0dddb32fe 100644
--- a/docs/tracks/pt/sending-product-data-to-dafiti.md
+++ b/docs/tracks/pt/sending-product-data-to-dafiti.md
@@ -62,9 +62,7 @@ A aba **Categories** da planilha de mapeamento possui duas colunas para serem pr
 - **VTEXCategoryId:** ID da Categoria na VTEX. O ID da categoria pode ser encontrado ao lado do nome da Categoria, ao navegar pela árvore de categorias no Admin VTEX, em *Produtos > Catálogo > Categorias*.
 - **DafitiCategoryId:**  ID da Categoria na Dafiti. Você deve procurar a melhor equivalência possível na planilha de consulta da Dafiti correspondente ao produto que está sendo mapeado.
 
-<div class = "alert alert-info">
-É possível mapear uma categoria VTEX para múltiplas categorias Dafiti. Para isso, é necessário separar os IDs na coluna da Dafiti por vírgula. Nesse caso, todos os produtos desta categoria na VTEX serão relacionados às categorias selecionadas na Dafiti.
-</div>
+>ℹ️ É possível mapear uma categoria VTEX para múltiplas categorias Dafiti. Para isso, é necessário separar os IDs na coluna da Dafiti por vírgula. Nesse caso, todos os produtos desta categoria na VTEX serão relacionados às categorias selecionadas na Dafiti.
 
 ### Attributenames
 
diff --git a/docs/tracks/pt/sending-products-to-google-shopping.md b/docs/tracks/pt/sending-products-to-google-shopping.md
index 4b1a41648..e24a8fa33 100644
--- a/docs/tracks/pt/sending-products-to-google-shopping.md
+++ b/docs/tracks/pt/sending-products-to-google-shopping.md
@@ -20,9 +20,7 @@ No Google Shopping somente [catálogos](https://help.vtex.com/pt/tracks/catalogo
 
 Após a configuração da integração e autenticação da sua conta, o envio de produtos para o marketplace não é automático, é necessário [reindexar a base](https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao). Esse processo prepara os dados dos SKUs e produtos e envia para o marketplace informações gerais sobre catálogo, preço e estoque. 
 
-<div class = "alert alert-info">
-Somente o <a href="https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA">usuário Titular (owner)</a> tem permissão para reindexar a base de uma loja VTEX. Durante o período de reindexação, que é variável, os produtos entram numa fila para atualização de dados, mas seguem disponíveis para venda no site da loja.
-</div>
+>ℹ️ Somente o [usuário Titular (owner)](https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA) tem permissão para reindexar a base de uma loja VTEX. Durante o período de reindexação, que é variável, os produtos entram numa fila para atualização de dados, mas seguem disponíveis para venda no site da loja.
 
 Para reindexar a base, copie o endereço abaixo no seu navegador, substituindo `{nomedaloja}` pelo nome da sua loja:
 
diff --git a/docs/tracks/pt/settings.md b/docs/tracks/pt/settings.md
index d16659484..01f991df4 100644
--- a/docs/tracks/pt/settings.md
+++ b/docs/tracks/pt/settings.md
@@ -44,16 +44,14 @@ Outra alternativa, embora não recomendada, seria não incluir registros CAA no
 
 Para facilitar o trabalho de criar/verificar seus registros CAA, você pode usar o [CAA Record Helper by SSLMate](https://sslmate.com/caa/). O programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) também pode ajudar na verificação dos registros, através do comando `dig domain.com CAA` - um status `SERVFAIL` pode indicar não-conformidade do seu servidor DNS.
 
-<div class = "alert alert-info">
-Saiba mais:
-<p>
-<ul>
-<li><a href="https://sslmate.com/caa/">CAA Record Helper by SSLMate</a></li>
-<li><a href="https://letsencrypt.org/docs/caa/">Let's Encrypt: Certificate Authority Authorization (CAA)</a></li>
-<li><a href="https://sslmate.com/caa/about">SSL Mate: About CAA</a></li>
-</ul>
-</p>
-</div>
+>ℹ️ Saiba mais:
+>
+> *[CAA Record Helper by SSLMate](https://sslmate.com/caa/)
+>
+> *[Let's Encrypt: Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)
+>
+> *[SSL Mate: About CAA](https://sslmate.com/caa/about)
+> 
 
 ## Colocar conta em produção
 
diff --git a/docs/tracks/pt/shipping-costs-and-simulation.md b/docs/tracks/pt/shipping-costs-and-simulation.md
index 5ff89fec6..370539e55 100644
--- a/docs/tracks/pt/shipping-costs-and-simulation.md
+++ b/docs/tracks/pt/shipping-costs-and-simulation.md
@@ -43,6 +43,4 @@ Essa validação é feita pelo [Simulador de envio](https://help.vtex.com/pt/tut
 * Se há pontos de retirada para o produto.
 * Qual [seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa) realizará a entrega do produto. 
 
-<div class = "alert alert-info">
-Simule também o envio via API, utilizando a <a href="https://developers.vtex.com/vtex-rest-api/reference/calculatesla">API de cálculo de SLA</a>.
-</div>
+>ℹ️ Simule também o envio via API, utilizando a [API de cálculo de SLA](https://developers.vtex.com/vtex-rest-api/reference/calculatesla).
diff --git a/docs/tracks/pt/shipping-strategies.md b/docs/tracks/pt/shipping-strategies.md
index e446f3d26..0a66600d8 100644
--- a/docs/tracks/pt/shipping-strategies.md
+++ b/docs/tracks/pt/shipping-strategies.md
@@ -26,9 +26,7 @@ A estratégia de envio é definida por três entidades logísticas:
 * [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb): identificação do local de armazenamento dos itens. A política de envio não é a única variável para a escolha da entrega; é preciso considerar, também, em qual estoque estão os produtos do pedido.
 * [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj): ponto de retirada do estoque. É pela doca que a loja define a retirada dos pacotes. As transportadoras retiram os pacotes para envio pela doca.
 
-<div class = "alert alert-info">
-Há outros cenários possíveis para o uso de docas. Consulte o artigo <a href="https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj">Doca</a> e confira os casos de uso. Para saber mais sobre o fluxo das entregas, consulte o artigo <a href="https://help.vtex.com/pt/tutorial/como-funciona-o-fluxo-de-entregas--4ku3QKWfxmUO8UgA0yqgUq">Como funciona o fluxo de entregas</a>.
-</div>
+>ℹ️ Há outros cenários possíveis para o uso de docas. Consulte o artigo [Doca](https://help.vtex.com/pt/tutorial/doca--5DY8xHEjOLYDVL41Urd5qj) e confira os casos de uso. Para saber mais sobre o fluxo das entregas, consulte o artigo [Como funciona o fluxo de entregas](https://help.vtex.com/pt/tutorial/como-funciona-o-fluxo-de-entregas--4ku3QKWfxmUO8UgA0yqgUq).
 
 Note que:
 
@@ -54,17 +52,18 @@ Para os casos em que a loja oferece [pontos de retirada](https://help.vtex.com/p
 
 O ponto de retirada fica disponível no checkout como uma opção de envio, e o cliente escolhe entre **Entrega** (transportadora) e **Retirada** (ponto de retirada).
 
-<div class = "alert alert-info">
-As configurações da Estratégia de envio também podem ser feitas via API. Confira as APIs disponíveis:
-<body>
-<ul>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/docks">API de docas</a></li>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse">API de estoques</a></li>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/get_logistics-pvt-shipping-policies-id">API de políticas de envio</a></li>
-<li><a href="https://developers.vtex.com/vtex-rest-api/reference/listallpickupppoints">API de pontos de retirada</a></li>
-  </ul>
-  </body>
-</div>
+>ℹ️ As configurações da Estratégia de envio também podem ser feitas via API. Confira as APIs disponíveis:
+> <body>
+>
+> *[API de docas](https://developers.vtex.com/vtex-rest-api/reference/docks)
+>
+> *[API de estoques](https://developers.vtex.com/vtex-rest-api/reference/createupdatewarehouse)
+>
+> *[API de políticas de envio](https://developers.vtex.com/vtex-rest-api/reference/get_logistics-pvt-shipping-policies-id)
+>
+> *[API de pontos de retirada](https://developers.vtex.com/vtex-rest-api/reference/listallpickupppoints)
+>
+> </body>
 
 ### Como configurar
 
@@ -104,7 +103,5 @@ Para cadastrar feriados na plataforma, você pode:
 
 É possível cadastrar horários de entrega para envios agendados de transportadoras e pontos de retirada. A funcionalidade **[Entrega agendada](https://help.vtex.com/pt/tutorial/entrega-agendada--22g3HAVCGLFiU7xugShOBi)** permite que a loja ofereça janelas de entrega para seus clientes.
 
-<div class = "alert alert-info">
-O envio depende também do <a href="https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV">custo de envio</a> que a sua loja oferece aos clientes. Esse assunto será abordado nos artigos seguintes. Para mais informações sobre como é feita a escolha das transportadoras para realizar uma entrega, consulte o artigo <a href="https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-frete--tutorials_116">Como funciona o cálculo do frete.</a>
-</div>
+>ℹ️ O envio depende também do [custo de envio](https://help.vtex.com/pt/tutorial/custo-final-do-envio--5bwhIO108VA5Y2YOpef9lV) que a sua loja oferece aos clientes. Esse assunto será abordado nos artigos seguintes. Para mais informações sobre como é feita a escolha das transportadoras para realizar uma entrega, consulte o artigo [Como funciona o cálculo do frete.](https://help.vtex.com/pt/tutorial/como-funciona-o-calculo-de-frete--tutorials_116)
 
diff --git a/docs/tracks/pt/synonyms.md b/docs/tracks/pt/synonyms.md
index a2fec488f..59ecba5dc 100644
--- a/docs/tracks/pt/synonyms.md
+++ b/docs/tracks/pt/synonyms.md
@@ -24,9 +24,7 @@ Para isso, o VTEX Intelligent Search recebe o termo pesquisado pelo cliente e o
 
 Desse modo, caso exista uma regras de sinônimos, não importa como o cliente pesquise ou como está cadastrado o nome do produto, ele sempre encontrará o que procura.
 
-<div class = "alert alert-warning">
-Sinônimos não devem ser utilizados para resolver erros de grafia, de plural e singular ou mesmo de pronomes, de artigos e de preposições  nos termos pesquisados. Em todos estes pontos, o VTEX Intelligent Search é capaz de interpretar, aprender e resolver automaticamente por meio de algoritmos.
-</div>
+>⚠️ Sinônimos não devem ser utilizados para resolver erros de grafia, de plural e singular ou mesmo de pronomes, de artigos e de preposições  nos termos pesquisados. Em todos estes pontos, o VTEX Intelligent Search é capaz de interpretar, aprender e resolver automaticamente por meio de algoritmos.
 
 ### Tipos de sinônimos
 
diff --git a/docs/tracks/pt/unified-search.md b/docs/tracks/pt/unified-search.md
index 44151cdeb..46a098d47 100644
--- a/docs/tracks/pt/unified-search.md
+++ b/docs/tracks/pt/unified-search.md
@@ -16,9 +16,7 @@ trackSlugPT: instore-usando-o-app
 
 Com a [prateleira infinita](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv/40KMlmGI5tN0r0KPCDWgGn) do VTEX Sales App, o vendedor pode buscar por produtos que não estão limitados ao estoque da loja e adicioná-los ao carrinho. Para buscar um produto, clique no ícone de lupa <i class="fas fa-search"></i> e a barra de busca será exibida no topo da página inicial da loja.  Digite o nome do produto, código referência, SKU ID  ou EAN para encontrar o que precisa.
 
-<div class = "alert alert-info">
-Para melhorar a experiência em cenários em que a conexão com a internet esteja em baixa velocidade, esta funcionalidade conta com recursos otimizados que fazem uso do cache do navegador para otimizar a busca.
-</div>
+>ℹ️ Para melhorar a experiência em cenários em que a conexão com a internet esteja em baixa velocidade, esta funcionalidade conta com recursos otimizados que fazem uso do cache do navegador para otimizar a busca.
 
 ![Barra busca - PT](https://images.ctfassets.net/alneenqid6w5/3bfHAUCI0TwYoAkLMf67yw/3c7031056980ae911e2436933bee89fa/Tela_1_barra_busca.gif)
 
diff --git a/docs/tracks/pt/untitled-entry-2019-11-25-at-06-07-48.md b/docs/tracks/pt/untitled-entry-2019-11-25-at-06-07-48.md
index b61a33c04..d3f84778e 100644
--- a/docs/tracks/pt/untitled-entry-2019-11-25-at-06-07-48.md
+++ b/docs/tracks/pt/untitled-entry-2019-11-25-at-06-07-48.md
@@ -22,9 +22,7 @@ Para configurar um banner, siga os seguintes passos:
 
 - **Posição**: área que o banner aparecerá na página de resultado de busca. Temos já definidas **quatro áreas**. **Duas acima** do resultado de busca e **duas  abaixo**. 
 
-<div class = "alert alert-warning">
-  OBS.: São dois banners em cada área pois um fica em modo "full",  ocupando a área horizontal toda da loja, e a outra fica no bloco do resultado de busca (área da direita onde se tem a listagem de produtos - que normalmente ocupa 70% da tela, e os 30% restantes correspondem a área de filtros) ⇒ explicar melhor
-  </div>
+>⚠️ OBS.: São dois banners em cada área pois um fica em modo "full",  ocupando a área horizontal toda da loja, e a outra fica no bloco do resultado de busca (área da direita onde se tem a listagem de produtos - que normalmente ocupa 70% da tela, e os 30% restantes correspondem a área de filtros) ⇒ explicar melhor
 
 - **Datas de início e de fim**: datas que definem o início e o fim da disponibilidade do banner. O gestor pode agendar campanhas futuras, facilitando o seu controle.
 
diff --git a/docs/tracks/pt/viewing-the-email-history-of-an-order.md b/docs/tracks/pt/viewing-the-email-history-of-an-order.md
index b7a6c2cdb..a8a38d77c 100644
--- a/docs/tracks/pt/viewing-the-email-history-of-an-order.md
+++ b/docs/tracks/pt/viewing-the-email-history-of-an-order.md
@@ -22,6 +22,4 @@ Para ver o histórico de emails, acesse o módulo **Pedidos**, entre no pedido d
 
 O sistema que faz esse registro chama-se __Conversation Tracker__. Para entender mais a fundo como ele funciona, veja o artigo [Como é feita a comunicação com o cliente durante o fluxo pedido](https://help.vtex.com/pt/tutorial/conversation-tracker--tutorials_195).
 
-<div class = "alert alert-info">
-Como a comunicação com o cliente é uma responsabilidade do marketplace, apenas pedidos com origem marketplace tem o histórico de email transacionais. Pedidos com origem fulfillment não mantêm tal histórico.
-</div>
+>ℹ️ Como a comunicação com o cliente é uma responsabilidade do marketplace, apenas pedidos com origem marketplace tem o histórico de email transacionais. Pedidos com origem fulfillment não mantêm tal histórico.
diff --git a/docs/tracks/pt/vtex-modules-ii.md b/docs/tracks/pt/vtex-modules-ii.md
index 264c81076..ef3c5b0b1 100644
--- a/docs/tracks/pt/vtex-modules-ii.md
+++ b/docs/tracks/pt/vtex-modules-ii.md
@@ -74,9 +74,7 @@ Os provedores de pagamento precisam ser habilitados em uma loja de modo que tran
 2. Selecionar o provedor desejado, clicando no respectivo link da tabela.
 3. Acessar o Admin VTEX para configurar o provedor conforme as instruções descritas no respectivo artigo de configuração.
 
-<div class = "alert alert-info">
-Os artigos de configuração de provedores também podem ser acessados ao digitar o nome do provedor desejado na barra de busca do <a href="https://help.vtex.com/pt/">Help Center</a>.
-</div>
+>ℹ️ Os artigos de configuração de provedores também podem ser acessados ao digitar o nome do provedor desejado na barra de busca do [Help Center](https://help.vtex.com/pt/).
 
 #### Definindo meios e condições de pagamento
 
@@ -256,9 +254,7 @@ Mais informações em [Otimização das opções de entrega no Checkout](https:/
 
 Funcionalidade que permite envio de e-mails aos clientes para recordá-los sobre a conclusão da compra de um carrinho que tenha sido criado anteriormente, mas não finalizado.
 
-<div class = "alert alert-info">
-Configurar o carrinho abandonado durante o Onboarding, permitirá que todos os carrinhos que ainda serão criados, possam ser encaminhados para avaliação do cliente ou finalizados.
-</div>
+>ℹ️ Configurar o carrinho abandonado durante o Onboarding, permitirá que todos os carrinhos que ainda serão criados, possam ser encaminhados para avaliação do cliente ou finalizados.
 
 Mais informações em [Configurar carrinho abandonado](https://help.vtex.com/pt/tutorial/configurar-carrinho-abandonado--tutorials_740).
 
diff --git a/docs/tracks/pt/what-is-the-master-user.md b/docs/tracks/pt/what-is-the-master-user.md
index e4f953539..8a629594d 100644
--- a/docs/tracks/pt/what-is-the-master-user.md
+++ b/docs/tracks/pt/what-is-the-master-user.md
@@ -18,9 +18,7 @@ Para a plataforma VTEX, o **usuário Titular** é o principal responsável pela
 
 Por padrão, o e-mail do usuário Titular é o do dono do acordo comercial de contratação da VTEX. Mas, depois que recebe o ambiente VTEX, esse e-mail pode ser trocado.
 
-<div class = "alert alert-warning"> 
-Usuário Titular não é o mesmo que <b>Owner (Admin Super)</b>. O <b>Owner (Admin Super)</b> é um perfil de acesso do License Manager, que define permissões concedidas a um dado usuário da sua loja, podendo inclusive ser atribuído a múltiplos usuários.
-</div>
+>⚠️ Usuário Titular não é o mesmo que **Owner (Admin Super)**. O **Owner (Admin Super)** é um perfil de acesso do License Manager, que define permissões concedidas a um dado usuário da sua loja, podendo inclusive ser atribuído a múltiplos usuários.
 
 Se seu usuário tem perfil de acesso ao módulo Gerenciamento da conta, você pode verificar quem é o usuário Titular acessando a aba __Contas__ e buscando o nome da loja.
 
diff --git a/docs/tracks/pt/what-is-vtex-payment.md b/docs/tracks/pt/what-is-vtex-payment.md
index f8d5b9d5b..b4b9ea500 100644
--- a/docs/tracks/pt/what-is-vtex-payment.md
+++ b/docs/tracks/pt/what-is-vtex-payment.md
@@ -18,9 +18,7 @@ O VTEX Payment é uma solução de pagamentos corporativa para clientes VTEX. Cr
 
 Para gerir suas operações, o cliente tem acesso a uma conta digital.
 
-<div class = "alert alert-info">
-O VTEX Payment é um gateway opcional de pagamentos para uso dos clientes VTEX. Sua ativação pode ser solicitada e implementada de maneira rápida (plug and play), pois é nativamente integrada ao sistema VTEX.
-</div>
+>ℹ️ O VTEX Payment é um gateway opcional de pagamentos para uso dos clientes VTEX. Sua ativação pode ser solicitada e implementada de maneira rápida (plug and play), pois é nativamente integrada ao sistema VTEX.
 
 ## Antifraude
 
diff --git a/docs/tutorials/en/accessing-the-beta-environment.md b/docs/tutorials/en/accessing-the-beta-environment.md
index d87454f0d..e81606ab2 100644
--- a/docs/tutorials/en/accessing-the-beta-environment.md
+++ b/docs/tutorials/en/accessing-the-beta-environment.md
@@ -17,9 +17,7 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 
 On VTEX, all stores have a beta environment, where platform users (sales associates, developers, or other authorized users) can run tests to validate new settings or versions of applications/services before making changes to the stable environment.
 
-<div class = "alert alert-info">
-The beta environment is an exact replica of the stable environment, including store data and configurations.
-</div>
+>ℹ️ The beta environment is an exact replica of the stable environment, including store data and configurations.
 
 In this way, **changing data in the beta environment will also affect data in the stable environment**.
 
@@ -43,6 +41,4 @@ To access the beta environment in your store, enable the <code>vtex-commerce-env
 </li>
 </ol>
 
-<div class = "alert alert-info">
-To go back to the main store environment, return to the Dev. Tools panel in your browser and remove the vtex-commerce-env cookie. Refresh the page again to switch back to the <b>stable</b> environment.
-</div>
+>ℹ️ To go back to the main store environment, return to the Dev. Tools panel in your browser and remove the vtex-commerce-env cookie. Refresh the page again to switch back to the **stable** environment.
diff --git a/docs/tutorials/en/adding-sku-specifications-or-fields.md b/docs/tutorials/en/adding-sku-specifications-or-fields.md
index 827a866b0..dbdd4b744 100644
--- a/docs/tutorials/en/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/en/adding-sku-specifications-or-fields.md
@@ -33,9 +33,7 @@ In this article, we explain how the specification inheritance works for the adde
         * [SKU Registration](#sku-registration)
         * [Spreadsheet](#spreadsheet)
 
-<div class = "alert alert-info">
-  <p>To create an SKU specification using <strong>Catalog API</strong>, follow the <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> developer's guide.</p>
-</div>
+>ℹ️ To create an SKU specification using **Catalog API**, follow the [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) developer's guide.
 
 ## SKU Specification inheritance
 
@@ -55,9 +53,7 @@ See the step-by-step instructions below.
 
 ### Creating an SKU field
 
-<div class = "alert alert-warning">
-  <p>Once created, the SKU fields cannot be deleted. If you uncheck the field, all the SKUs in that category will become inactive, until the field is checked again. If you do not fill out a specification when adding an SKU, it may cause the SKU not to appear on the website, because it is inactive.</p>
-</div>
+>⚠️ Once created, the SKU fields cannot be deleted. If you uncheck the field, all the SKUs in that category will become inactive, until the field is checked again. If you do not fill out a specification when adding an SKU, it may cause the SKU not to appear on the website, because it is inactive.
 
 To create an SKU field, follow the instructions below:
 
@@ -65,9 +61,7 @@ To create an SKU field, follow the instructions below:
 2. Click on **Categories**.
 3. Click the category associated with the specification group in which you want to create the SKU field.
 
-  <div class = "alert alert-warning">
-    <p>Please note that when you create a specification for a higher category level, it will appear in all the sublevels of that category.</p>
-  </div>
+  >⚠️ Please note that when you create a specification for a higher category level, it will appear in all the sublevels of that category.
 
 3. Click `Actions` <i class="fas fa-angle-down"></i>.
 4. Click `Field (SKU)`.
@@ -138,9 +132,7 @@ The **Values** of the SKU fields will vary according to the selected field type:
 
 ![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/a6da423b96ac0edb46837b590e7a030f/en-sku-spec-2.gif)
 
-<div class = "alert alert-info">
-  <p>If you are adding values for the first time in a field, you must return to the form of that specific field and check the <strong>Active</strong> option.</p>
-</div>
+>ℹ️ If you are adding values for the first time in a field, you must return to the form of that specific field and check the **Active** option.
 
 #### Accessing or editing values
 
diff --git a/docs/tutorials/en/adding-specifications-or-product-fields.md b/docs/tutorials/en/adding-specifications-or-product-fields.md
index bc27f7264..3ce352651 100644
--- a/docs/tutorials/en/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/en/adding-specifications-or-product-fields.md
@@ -33,9 +33,7 @@ In this article, we explain how the specification inheritance works for the adde
         * [Product registration](#product-registration)
         * [Spreadsheet](#spreadsheet)
 
-<div class = "alert alert-info">
-  <p>To create a product specification using <strong>Catalog API</strong>, follow the <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> developer's guide.</p>
-</div>
+>ℹ️ To create a product specification using **Catalog API**, follow the [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) developer's guide.
 
 ## Product specifications inheritance
 
@@ -148,9 +146,7 @@ For the **Combo**, **Radio** and **CheckBox** field types, you must add preset v
 
 ![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/c8c76e2f734ee038be20a6c273fdf987/EN_ProdutoGif_2_Alterado.gif)
 
-<div class = "alert alert-info">
-  <p>If you are adding values for the first time in a field, you must return to the form of that specific field and check the <strong>Active</strong> option.</p>
-</div>
+>ℹ️ If you are adding values for the first time in a field, you must return to the form of that specific field and check the **Active** option.
 
 #### Accessing or editing values
 
diff --git a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
index 178674ebf..d07a54e1d 100644
--- a/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/en/advertising-with-vtex-ad-network-beta.md
@@ -15,9 +15,7 @@ legacySlug: advertising-with-vtex-ad-network-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>VTEX Ad Network is in beta, which means that we are working to improve. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
-</div>
+>ℹ️ VTEX Ad Network is in beta, which means that we are working to improve. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). If you are not yet a customer but are interested in this solution, please fill out the [contact form](https://vtex.com/us-en/contact/).
 
 [VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) allows you to advertise your products on VTEX stores that have them listed in their catalog.
 
@@ -35,9 +33,7 @@ If you're already a **VTEX Ad Network** advertiser, check this article to learn
 
 Follow the steps below to create a [VTEX Ad Network campaign](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campaigns):
 
-<div class = "alert alert-info">
-VTEX currently offers a single ad format: search results. Learn more about this <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ad-format">ad format</a>.
-</div>
+>ℹ️ VTEX currently offers a single ad format: search results. Learn more about this [ad format](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ad-format).
 
 1. On VTEX Admin, go to **Storefront > Ad Network > Campaigns**.
 2. Click `Create campaign`.
@@ -123,9 +119,7 @@ Below you will find a table with details about each campaign:
 - **Budget:** Total budget.
 - **Remaining:** Budget still available at the moment.
 
-<div class = "alert alert-info">
-Learn more about <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#attribution-window">sales attribution to ads</a>.
-</div>
+>ℹ️ Learn more about [sales attribution to ads](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#attribution-window).
 
 You can filter the table data using the following options:
 
@@ -155,7 +149,5 @@ You'll find a table below the aggregated data detailing each product's performan
 - **ROAS:** Return on advertising spend.
 - **Remaining:** Budget still available at the moment.
 
-<div class = "alert alert-info">
-Learn more about <a href="https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#attribution-window">sales attribution to ads</a>.
-</div>
+>ℹ️ Learn more about [sales attribution to ads](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#attribution-window).
 
diff --git a/docs/tutorials/en/affiliates-program-app.md b/docs/tutorials/en/affiliates-program-app.md
index a12279442..fb26ca4c6 100644
--- a/docs/tutorials/en/affiliates-program-app.md
+++ b/docs/tutorials/en/affiliates-program-app.md
@@ -15,9 +15,7 @@ legacySlug: affiliates-program-app
 subcategory: 6GWaAkVqXQYN79ilMgUsPr
 ---
 
-<div class = "alert alert-info">
-The <b>Affiliates Program</b> is an app that is only supported by <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a> stores and is not available for stores that use <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">Legacy Portal CMS</a> or <a href="https://www.faststore.dev/tutorials/cms/0#vtex-headless-cms">Headless CMS</a>. Please visit the Affiliates Program app developer guide to install and configure the app on your VTEX store. 
-</div>
+>ℹ️ The **Affiliates Program** is an app that is only supported by [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2) stores and is not available for stores that use [Legacy Portal CMS](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) or [Headless CMS](https://www.faststore.dev/tutorials/cms/0#vtex-headless-cms). Please visit the Affiliates Program app developer guide to install and configure the app on your VTEX store.
 
 In the **Affiliates Program** app, an affiliate is someone who partners with your VTEX store to promote sales in exchange for a commission. The term is, therefore, different from the [usual concept of an affiliate at VTEX](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). 
 
@@ -48,9 +46,7 @@ The **affiliate profile page** is an interface where the affiliate can track and
 
 The **registration page** allows those who are interested in becoming affiliates to fill in their information to apply for VTEX store registration. 
 
-<div class = "alert alert-info">
-The affiliate pages are customizable. Learn more in the <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app">Affiliates Program app</a> developer's guide.
-</div>
+>ℹ️ The affiliate pages are customizable. Learn more in the [Affiliates Program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app) developer's guide.
 
 ### VTEX Admin pages
 
@@ -129,9 +125,7 @@ At the top of the page, you see the following metrics about orders placed throug
 - **Order Total:** Sum of the order values, calculated from the item prices without shipping costs.
 - **Order Total Commission:**  Sum of the amounts of affiliate commissions on orders.
 
-<div class = "alert alert-info">
-To track an order flow, click the <code>Order ID</code>. This will redirect you to the VTEX Admin under <b>Orders > All Orders</b>.
-</div>
+>ℹ️ To track an order flow, click the `Order ID`. This will redirect you to the VTEX Admin under **Orders > All Orders**.
 
 ### Searching for orders
 
@@ -197,9 +191,7 @@ To export a SKU commission spreadsheet with a CSV extension, at the top of the *
 
 The file will be sent to the email address of the [user](https://help.vtex.com/en/tutorial/gerenciando-usuarios--tutorials_512) who is currently logged in.
 
-<div class = "alert alert-info">
-The exported content refers to the list SKU commissions at the time of export. Only the selected SKU commissions will be exported if a filter is active.
-</div>
+>ℹ️ The exported content refers to the list SKU commissions at the time of export. Only the selected SKU commissions will be exported if a filter is active.
 
 ### Importing commissions
 
@@ -215,9 +207,7 @@ Check if the following message is displayed:
 
 The name of the submitted fileadded file name will appear next to the `Last Import` field.
 
-<div class = "alert alert-info">
-You can identify the import information and the user by hovering over the <code>?</code> symbol next to <code>Last Import</code>.
-</div>
+>ℹ️ You can identify the import information and the user by hovering over the `?` symbol next to `Last Import`.
 
 ### Downloading the last import
 
diff --git a/docs/tutorials/en/all-orders.md b/docs/tutorials/en/all-orders.md
index e6e01a007..9a80d5e7b 100644
--- a/docs/tutorials/en/all-orders.md
+++ b/docs/tutorials/en/all-orders.md
@@ -15,9 +15,7 @@ legacySlug: order-listing-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-<div class = "alert alert-info">
-You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
-</div>
+>ℹ️ You can only access information from orders created in the last two years, and that same period is valid for customers through [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 The **All Orders** page allows retailers to track their store's orders and extract information for intelligent business management. To access the page, go to your VTEX Admin menu and click **Orders > All Orders**. On this page, you can:
 
diff --git a/docs/tutorials/en/analytics.md b/docs/tutorials/en/analytics.md
index b87bebcdf..16c3c4e00 100644
--- a/docs/tutorials/en/analytics.md
+++ b/docs/tutorials/en/analytics.md
@@ -24,9 +24,7 @@ Follow the steps below to access the page:
 1. In the VTEX Admin, go to **Storefront**, or type **Storefront** in the search bar at the top of the page.
 2. Under __Intelligent Search__, click __Analytics__. 
 
-<div class = "alert alert-info">
-  <p>The <b>Analytics</b> page is native to VTEX Intelligent Search. You cannot disable it in the Admin.</p>
-</div>
+>ℹ️ The **Analytics** page is native to VTEX Intelligent Search. You cannot disable it in the Admin.
 
 ## Data
 
@@ -72,9 +70,7 @@ To export a report in .csv format, you must follow the steps below:
 5. Wait until the file is available for download. Leaving this page will not interrupt the process.
 6. Click on `Download`.
 
-<div class = "alert alert-info">
-  <p>The file will be available for download for 48 hours.</p>
-</div>
+>ℹ️ The file will be available for download for 48 hours.
 
 The report (CSV file) you have downloaded contains two tables. The first table contains information about searched terms, as illustrated below. It also shows funnel metrics (from the **ProductsClick** column to the **ProductsSold** column) if you have selected this option.
 
diff --git a/docs/tutorials/en/application-keys.md b/docs/tutorials/en/application-keys.md
index a65012e32..2e0bbaa3a 100644
--- a/docs/tutorials/en/application-keys.md
+++ b/docs/tutorials/en/application-keys.md
@@ -45,9 +45,7 @@ On the **Application Keys** page, you can manage the [internal](#internal-app-ke
 
 To view this page, at the top bar of the VTEX Admin, click your **profile avatar** — indicated by the first letter of your email — and then click **Account settings** > **Application Keys**.
 
-<div class = "alert alert-info">
-<p>Learn more about <a href="https://help.vtex.com/en/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm">best practices for using application keys</a>.</p>
-</div>
+>ℹ️ Learn more about [best practices for using application keys](https://help.vtex.com/en/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm).
 
 ## Generating internal application keys
 
diff --git a/docs/tutorials/en/audit.md b/docs/tutorials/en/audit.md
index efb69a273..0f67a0184 100644
--- a/docs/tutorials/en/audit.md
+++ b/docs/tutorials/en/audit.md
@@ -38,9 +38,7 @@ Follow the instructions to search for an event using the filters available in Au
 2. In the **Application** menu under **Filters**, select the application related to the query.
 3. In the **Date** menu, choose a predefined date for the query. If you prefer to set the exact date range for the query, select the **Custom** option and choose the **Start** and **End** dates for the query.
 
-   <div class= "alert alert-info">
-     <p>Only records from the last 3 months are stored.</p>
-   </div>
+   >ℹ️ Only records from the last 3 months are stored.
 
 4. If you wish, add a filter by Action. To do this, in the field next to `Action` **must be**, type the name of the action and press `Enter`. You can enter more than one value by pressing `Enter` after each selection. Check the name of each action in [Events available in Audit](https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 5. If necessary, you can add specific filters to search for events more accurately. To do this, click the `Add Filter` button.
@@ -56,9 +54,7 @@ Follow the instructions to search for an event using the filters available in Au
 
     Check the [Results](#results) section to see how the events are displayed.
 
-<div class= "alert alert-warning">
-  <p>The query results correspond exactly to the content entered in the filter field. To avoid unexpected results, make sure you haven't typed extra spaces in the query terms.</p>
-</div>
+>⚠️ The query results correspond exactly to the content entered in the filter field. To avoid unexpected results, make sure you haven't typed extra spaces in the query terms.
 
 If you wish, you can share a query with another user. To do this, click `Share Query` in the top right-hand corner of the page. The link to the Audit search will be copied to your clipboard.
 
@@ -129,6 +125,4 @@ See below the information available in this tab:
 | Period | Start and end date of the period selected for the query. |
 | Redo Query | Button to redo the query. |
 
-<div class= "alert alert-warning">
-  <p>The <strong>Last queries</strong> tab only saves up to 50 queries. If you want to save a query beyond this limit, add it to your browser favorites.</p>
-</div>
+>⚠️ The **Last queries** tab only saves up to 50 queries. If you want to save a query beyond this limit, add it to your browser favorites.
diff --git a/docs/tutorials/en/autocomplete.md b/docs/tutorials/en/autocomplete.md
index 21482684f..2192e3c67 100644
--- a/docs/tutorials/en/autocomplete.md
+++ b/docs/tutorials/en/autocomplete.md
@@ -15,9 +15,7 @@ legacySlug: autocomplete
 subcategory: 30Kdgc6wJkMWgcXLB8mGr7
 ---
 
-<div class = "alert alert-warning">
-The Autocomplete tool is enabled by default in VTEX Intelligent Search. It is not possible to disable it in the Admin.
-</div>
+>⚠️ The Autocomplete tool is enabled by default in VTEX Intelligent Search. It is not possible to disable it in the Admin.
 
 Autocomplete is the functionality that displays previous search results based on current and previous searches. These results are presented in four different lists, which can be together or separated, depending on the customer's interaction. The existing sections are:
 
@@ -38,19 +36,14 @@ During the interaction with the search bar, VTEX Intelligent Search immediately
 
 When the user starts typing, the system displays the _Search suggestions_ and the _Product suggestions_ and removes the previous lists.
 
-<div class = "alert alert-info">
-  <p>Section information <i>Most searched terms</i> and <i>Search suggestions</i> are updated daily using the data from the last 14 days of the customers' interaction with the search.</p>
-  </div>
+>ℹ️ Section information <i>Most searched terms</i> and <i>Search suggestions</i> are updated daily using the data from the last 14 days of the customers' interaction with the search.
 
 This way, it is possible to provide the customer with a more fluid and personalized search experience. They can view the result quickly and receive suggestions based on their search.
 
 Another advantage for the store's manager is the increase in conversion due to this dynamic of usability and experience.
 
-<div class = "alert alert-info">
-  <p>Autocomplete offers search keyword suggestions even for completely new stores that do not yet have data on customer interaction such as clicks and searches.
-    In this case, the feature suggests search options based on an algorithm that extracts keywords from the store's catalog, products, brands, and categories.
-    </p>
-  </div>
+>ℹ️ Autocomplete offers search keyword suggestions even for completely new stores that do not yet have data on customer interaction such as clicks and searches.
+>     In this case, the feature suggests search options based on an algorithm that extracts keywords from the store's catalog, products, brands, and categories.
 
  ## Most searched terms
 
diff --git a/docs/tutorials/en/b2b-checkout-settings.md b/docs/tutorials/en/b2b-checkout-settings.md
index 66ece1b1b..6796e4bfb 100644
--- a/docs/tutorials/en/b2b-checkout-settings.md
+++ b/docs/tutorials/en/b2b-checkout-settings.md
@@ -62,9 +62,7 @@ Follow the steps below to customize your store checkout:
 <li>When you enable <code>Show Create a Quote button</code>, the checkout page will include a <code>Create Quote</code> button that allows creating a budget using the current cart items.</li>
 </ol>
 
-<div class = "alert alert-info">
-You should only enable the <code>Create Quote</code> button if the Order Quote app is installed in your store. For more information, check <a href="https://developers.vtex.com/docs/apps/vtex.b2b-quotes">B2B Quotes & Carts</a>.
-</div>
+>ℹ️ You should only enable the `Create Quote` button if the Order Quote app is installed in your store. For more information, check [B2B Quotes & Carts](https://developers.vtex.com/docs/apps/vtex.b2b-quotes).
 
 <ol start="4">
 <li>Click <code>Save</code>.</li>
diff --git a/docs/tutorials/en/best-practices-against-virtual-attacks.md b/docs/tutorials/en/best-practices-against-virtual-attacks.md
index 62e75c354..73660f21f 100644
--- a/docs/tutorials/en/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/en/best-practices-against-virtual-attacks.md
@@ -23,9 +23,7 @@ VTEX offers different protections against possible attacks on stores. Still, the
 - [orderForm settings](#orderform-settings)
 - [Disabling password login](#disabling-password-login)
 
-<div class = "alert alert-info">
-  <p>The measures in this guide do not entirely eliminate the possibility of an attack but may considerably reduce the likelihood of them happening if properly employed.</p>
-</div>
+>ℹ️ The measures in this guide do not entirely eliminate the possibility of an attack but may considerably reduce the likelihood of them happening if properly employed.
 
 ## Anti-fraud solution
 
@@ -48,9 +46,7 @@ We recommend using [reCAPTCHA v3](https://help.vtex.com/en/tutorial/using-recapt
 
 Learn more about how to set up this verification at your store's checkout in the article [reCAPTCHA at checkout](https://help.vtex.com/en/tutorial/using-recaptcha-at-checkout--18Te3oDd7f4qcjKu9jhNzP#recaptcha-v3). To implement reCAPTCHA V3 in a VTEX store, see the [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score) developer's guide.
 
-<div class = "alert alert-info">
-reCAPTCHA verification is enabled by default when store customers go through the steps of <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#credit-cards">adding credit cards</a>, without having to be configured by the store.
-</div>
+>ℹ️ reCAPTCHA verification is enabled by default when store customers go through the steps of [adding credit cards](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh#credit-cards), without having to be configured by the store.
 
 ## orderForm settings
 
diff --git a/docs/tutorials/en/best-practices-application-keys.md b/docs/tutorials/en/best-practices-application-keys.md
index d11d0ba0e..720e22f08 100644
--- a/docs/tutorials/en/best-practices-application-keys.md
+++ b/docs/tutorials/en/best-practices-application-keys.md
@@ -17,9 +17,7 @@ subcategory: 6uJgdHqWf1Mo0rUfgxseTn
 
 VTEX has several APIs available for customers and partners to develop highly customizable integrations with the platform. [Application keys](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) are used to provide secure access to data consumed by integrations without exposing your account to unauthorized users or apps.
 
-<div class = "alert alert-info">
-This type of credential is used to authenticate identities via API.
-</div>
+>ℹ️ This type of credential is used to authenticate identities via API.
 
 Improper handling of [application keys](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) can generate leaks, consequently leading to improper access scenarios. Below, you can see the best practices we recommend to manage the credentials you can implement to increase the security of your store.
 
diff --git a/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md b/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md
index 2e40a95b6..928fb3087 100644
--- a/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md
+++ b/docs/tutorials/en/best-practices-for-the-success-of-your-vtex-store.md
@@ -30,9 +30,7 @@ This article presents key practices to help you manage your VTEX store efficient
     * [Join the VTEX Community](#join-the-vtex-community)
     * [Learn best practices for VTEX Support requests](#learn-best-practices-for-vtex-support-requests)
 
-<div class = "alert alert-info">
-<b>Partner agencies</b><p>Several agencies and implementation partners have been certified by VTEX for demonstrating excellence and reliability in platform projects. Whether you need efficient implementation, customized store architecture, or ongoing infrastructure support, we recommend working with our partner agencies. To explore our partners, visit <a href="http://vtex.com">vtex.com</a> or the <a href="https://partnerportal.vtex.com/parceiros">Partner Portal</a> (available in Portuguese only).</p>
-</div>
+>ℹ️ **Partner agencies**Several agencies and implementation partners have been certified by VTEX for demonstrating excellence and reliability in platform projects. Whether you need efficient implementation, customized store architecture, or ongoing infrastructure support, we recommend working with our partner agencies. To explore our partners, visit [vtex.com](http://vtex.com) or the [Partner Portal](https://partnerportal.vtex.com/parceiros) (available in Portuguese only).
 
 ## Performance and security
 
@@ -50,9 +48,7 @@ The main benefits of creating and maintaining updated documentation of the opera
 * **Quick action on security issues:** Addressing security issues or vulnerabilities is more efficient when architecture documentation is available.
 * **Support optimization:** When support from our team or third parties is needed, sharing the architecture documentation streamlines communication between parties and increases the effectiveness of their efforts.
 
-<div class = "alert alert-info">
-For guidelines on documenting your store architecture, see the <a href="https://developers.vtex.com/docs/guides">Get started</a> page on our Developer Portal and learn about the <a href="https://assets.vtex.com/4524045/">interactive framework</a> of the VTEX platform.
-</div>
+>ℹ️ For guidelines on documenting your store architecture, see the [Get started](https://developers.vtex.com/docs/guides) page on our Developer Portal and learn about the [interactive framework](https://assets.vtex.com/4524045/) of the VTEX platform.
 
 ### Follow security guidelines
 
@@ -62,9 +58,7 @@ There are strategies to prevent and reduce store exposure to the risk of malicio
 * **reCAPTCHA:** Use [reCAPTCHA](https://help.vtex.com/en/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#) to prevent fraud involving fake user accounts created by malicious software.
 * **Authentication:** If your store has been experiencing recurrent attacks, consider disabling password login and opting for alternative [authentication](https://help.vtex.com/en/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) methods for your customers.
 
-<div class = "alert alert-info">
-For more information about preventive actions, see the article <a href="https://help.vtex.com/en/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE">Best practices against virtual attacks</a> and this <a href="https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470">post</a> on VTEX Community (available in Portuguese).
-</div>
+>ℹ️ For more information about preventive actions, see the article [Best practices against virtual attacks](https://help.vtex.com/en/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE) and this [post](https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470) on VTEX Community (available in Portuguese).
 
 ### Manage access permission levels
 
@@ -104,9 +98,7 @@ Some of the main advantages of staying up to date are:
 * Configure updates to increase store security, as we continually innovate to protect your business operation.
 * If you need to contact support, familiarity with new features allows you to interact more efficiently with our support team, resulting in quicker solutions.
 
-<div class = "alert alert-info">
-The announcements from the Help Center <b>News</b> page are also accessible through your VTEX Admin. To view this content, click the bell icon at the top of the page.
-</div>
+>ℹ️ The announcements from the Help Center **News** page are also accessible through your VTEX Admin. To view this content, click the bell icon at the top of the page.
 
 ### Receive platform status notifications
 
@@ -118,9 +110,7 @@ For this purpose, VTEX provides a [platform status page](https://status.vtex.com
 * [RSS feed](https://rss.com/blog/how-do-rss-feeds-work/)
 * [Slack](https://slack.com/)
 
-<div class = "alert alert-info">
-For moreninformation about the platform status page, see the article <a href="https://</a>help.vtex.com/en/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ">VTEX Status Page</a>.
-</div>
+>ℹ️ For moreninformation about the platform status page, see the article [VTEX Status Page](https://</a>help.vtex.com/en/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ).
 
 ### Explore our onboarding content
 
@@ -165,7 +155,5 @@ These are the [best practices for opening a ticket with VTEX Support](https://he
 
 These are some of the most important recommendations. For more information, see the article [Best practices for opening a ticket with VTEX Support](https://help.vtex.com/en/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX).
 
-<div class = "alert alert-info">
-For an overview of our ticket support system, check the <a href="https://help.vtex.com/en/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">VTEX Support</a> track in the <b>Onboarding guide</b>.
-</div>
+>ℹ️ For an overview of our ticket support system, check the [VTEX Support](https://help.vtex.com/en/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8) track in the **Onboarding guide**.
 
diff --git a/docs/tutorials/en/beta-price-configuration.md b/docs/tutorials/en/beta-price-configuration.md
index 7ecbe2899..123dcac5f 100644
--- a/docs/tutorials/en/beta-price-configuration.md
+++ b/docs/tutorials/en/beta-price-configuration.md
@@ -40,9 +40,7 @@ In this section, you can set the default markup and price variation limit for yo
 
 - **Overwrite seller prices:** this option overwrites all seller prices with the ones from the current account. 
 
-<div class = "alert alert-info">
-  <p>The configuration <b>Overwrite prices for sellers</b> is not available for white label sellers.</p>
-</div>
+>ℹ️ The configuration **Overwrite prices for sellers** is not available for white label sellers.
 
 ## Price table rules
 
diff --git a/docs/tutorials/en/buy-one-get-one.md b/docs/tutorials/en/buy-one-get-one.md
index 5f5726450..376f2e33d 100644
--- a/docs/tutorials/en/buy-one-get-one.md
+++ b/docs/tutorials/en/buy-one-get-one.md
@@ -63,9 +63,7 @@ In this section, you can determine to which sellers the promotion will apply. Yo
 
 For the promotion to be valid for all sellers, leave the field blank.
 
-<div class = "alert alert-warning">
-  <p>It is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:</p><ol>1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.</ol><ol>2. Leave the field blank.  In this way, all sellers will be included in the promotion.</ol>
-</div>
+>⚠️ It is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.2. Leave the field blank.  In this way, all sellers will be included in the promotion.
 
 ![Restrict this promotion to seller products](https://images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/32b26e784595d4551700c022fc539598/Restrict_this_promotion_to_seller_products.png)
 
@@ -90,13 +88,9 @@ In this section, you can define the collections, SKUs, and minimum quantity for
 - **SKUs:** Allows you to enter the SKU name or ID to which the discount will apply. You can import a list of SKUs that must be saved in a text file (**.txt**), with each ID listed on a different row.
 - **Minimum quantity:** Allows you to define the minimum quantity of products that must be added to the cart for the discount to be applied. This is a required field.
 
-<div class = "alert alert-warning">
-<p>The promotion will not be created if the Collections or SKUs fields are not completed.<p>
-</div>
+>⚠️ <p>The promotion will not be created if the Collections or SKUs fields are not completed.<p>
 
-<div class = "alert alert-warning">
-<p>A Buy One Get One promotion can be created with a maximum of 100 different SKUs at the same time.<p>
-</div>
+>⚠️ <p>A Buy One Get One promotion can be created with a maximum of 100 different SKUs at the same time.<p>
 
 ![Buy One Get One](https://images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c521b34d5694bf3712f5450f32839a91/Buy_One_Get_One.png)
 
diff --git a/docs/tutorials/en/calculating-revenue-through-the-worksheet-exported-from-orders-module.md b/docs/tutorials/en/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
index bdda99484..fc2f22550 100644
--- a/docs/tutorials/en/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
+++ b/docs/tutorials/en/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
@@ -29,8 +29,6 @@ To calculate the total revenue from the worksheet, follow the steps below:
 4. Remove all duplicate values from the second column (__Order__). This must be done because in the case of carts with more than one SKU, several lines are generated for the same order - one for each SKU.
 5. Add the values in column __Total Value__. In this column you find the total value of the order (that is, already considering all SKUs in the cart).
 
-<div class = "alert alert-info">
-The sum of values in the Total Value column (after the removal of duplicate orders) is the total revenue obtained from the selected orders in the worksheet.
-</div>
+>ℹ️ The sum of values in the Total Value column (after the removal of duplicate orders) is the total revenue obtained from the selected orders in the worksheet.
 
 To understand all the columns, see the article [Order report](https://help.vtex.com/en/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
diff --git a/docs/tutorials/en/campaign-promotion.md b/docs/tutorials/en/campaign-promotion.md
index ddf7ad694..593f4cbc5 100644
--- a/docs/tutorials/en/campaign-promotion.md
+++ b/docs/tutorials/en/campaign-promotion.md
@@ -72,9 +72,7 @@ Below is a description of all the fields you need to fill in to create a campaig
   - **Free shipping:** full discount on the shipping cost.
   - **Gift:** full discount on the product defined as a gift. You can select one or more SKUs or more than one unit of the same SKU as a giveaway. To define more than one gift, select the **Activate Gift Multiplier** option and set the quantity. Learn more about this option in [this article](https://help.vtex.com/en/tutorial/what-does-it-mean-to-activate-a-gift-multiplier-on-a-promotion--1gydgkmjEWcoo2CskUwuYK).
 
-  <div class = "alert alert-info">
-  <p>The <b>Gift</b> product must have a price associated with it, even though it is given to the customer for free.</p>
- </div>
+  >ℹ️ The **Gift** product must have a price associated with it, even though it is given to the customer for free.
 
   - **Formula-based nominal discount:** the discount is calculated based on the total of the product prices, the shipping cost and the desired discount percentage rate. The shipping rate used in the formula will be the lowest available for the order, regardless of what the customer selects. You must always use dot as decimal separator. For example, the discount will be 30% of the product price + shipping rate. Therefore, the formula should be as follows: `(total price + shipping rate) * 0.3)`.
   - **Nominal reward value:** credit that will be added to the store's loyalty program. 
@@ -101,9 +99,7 @@ In this section, you can define to which sellers the promotion will apply. You c
 
 For the promotion to be valid for all sellers, leave the field blank.
 
-<div class = "alert alert-warning">
-  <p><b>Warning:</b> it is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:</p><ol>1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.</ol><ol>2. Leave the field blank.  This way, all sellers will be included in the promotion.</ol>
-</div>
+>⚠️ **Warning:** it is not possible to select a white label seller. There are two ways to include a white label seller in the promotion:1. Restrict sellers to the main store. This will add all white label sellers in your store to the promotion.2. Leave the field blank.  This way, all sellers will be included in the promotion.
 
 #### Trade Policy
 
diff --git a/docs/tutorials/en/canceling-orders.md b/docs/tutorials/en/canceling-orders.md
index d8a38f470..d18785990 100644
--- a/docs/tutorials/en/canceling-orders.md
+++ b/docs/tutorials/en/canceling-orders.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Orders on VTEX can be canceled at practically any status during their evolution. It must be stressed that once canceled, the order status cannot be altered.
 
-<div class = "alert alert-warning">
-Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be canceled. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
-</div>
+>⚠️ Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be canceled. If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 There are two ways of doing this, through the VTEX Admin or API.
 
diff --git a/docs/tutorials/en/carrier-working-hours.md b/docs/tutorials/en/carrier-working-hours.md
index 3a761d53e..114839465 100644
--- a/docs/tutorials/en/carrier-working-hours.md
+++ b/docs/tutorials/en/carrier-working-hours.md
@@ -31,9 +31,7 @@ The way you configure working hours will influence the delivery time calculation
 
   >❗ To authorize the carrier to receive orders on weekends, this toggle must be marked as `Active`. Even if Saturdays and Sundays are configured as valid windows, activating the toggle is mandatory to authorize the carrier to receive orders outside business hours.
 
-  <div class = "alert alert-info">
-When this option is enabled, the order <a href="https://help.vtex.com/en/tutorial/how-shipping-calculation-works--tutorials_116">shipping calculation</a> is influenced, and the period from order placement to the carrier's business time is added to the total shipping time.
-</div>
+  >ℹ️ When this option is enabled, the order [shipping calculation](https://help.vtex.com/en/tutorial/how-shipping-calculation-works--tutorials_116) is influenced, and the period from order placement to the carrier's business time is added to the total shipping time.
 
 3. Select the `Day of the week`, as well as the `Start time` and `End time` for shipping items to customers.
     * **Day of the week**: days on which carriers make deliveries.
diff --git a/docs/tutorials/en/category-variations-and-attributes-mapping.md b/docs/tutorials/en/category-variations-and-attributes-mapping.md
index fcc8ee74d..667ab91fe 100644
--- a/docs/tutorials/en/category-variations-and-attributes-mapping.md
+++ b/docs/tutorials/en/category-variations-and-attributes-mapping.md
@@ -15,9 +15,7 @@ legacySlug: category-variations-and-attributes-mapping
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class = "alert alert-info">
-The Mercado Livre plataform is available only in spanish and portuguese, so the related terms in the article below do not have a translation.   
-  </div>
+>ℹ️ The Mercado Livre plataform is available only in spanish and portuguese, so the related terms in the article below do not have a translation.
 
 After making the initial settings for integration with Mercado Livre, we are now going to categorize and send product variations and attributes to the marketplace. You will send this information through the __upload of the mapping spreadsheet__, which contains a correspondence table.
 
diff --git a/docs/tutorials/en/change-seller.md b/docs/tutorials/en/change-seller.md
index 316ce5216..1666f8d49 100644
--- a/docs/tutorials/en/change-seller.md
+++ b/docs/tutorials/en/change-seller.md
@@ -17,9 +17,7 @@ subcategory: 5m1qqfnmfYKsO0KiOQC8Ky
 
 The Change Seller is the feature that gives marketplaces the autonomy to change the seller that will fulfill an order. 
 
-<div class = "alert alert-info">
-The Change Seller feature can only be configured using APIs. For more information, see our <a href="https://developers.vtex.com/vtex-rest-api/docs/change-seller">Change Seller documentations for developers</a>.
-</div>
+>ℹ️ The Change Seller feature can only be configured using APIs. For more information, see our [Change Seller documentations for developers](https://developers.vtex.com/vtex-rest-api/docs/change-seller).
 
 Sellers can be changed in two situations: 
 
diff --git a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
index f2b8d02a9..0a4a75133 100644
--- a/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/en/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -42,7 +42,5 @@ The operational security of this functionality is based on controlling the acces
 
 After the order is closed, the manual price entered needs to be approved by the store administrator or a user with permission in the [Order Authorization system](https://help.vtex.com/en/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn).
 
-<div class = "alert alert-info">
-Once the manual price value has been validated, the order follows the normal invoicing flow.
-</div>
+>ℹ️ Once the manual price value has been validated, the order follows the normal invoicing flow.
 
diff --git a/docs/tutorials/en/changing-items-from-a-complete-order.md b/docs/tutorials/en/changing-items-from-a-complete-order.md
index 413c0ab56..ee8fcfab8 100644
--- a/docs/tutorials/en/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/en/changing-items-from-a-complete-order.md
@@ -73,6 +73,4 @@ When changing or removing items from an order, the order total changes. In this
 
 The order total will be updated once the invoice is added, corresponding to what is settled by the VTEX payment gateway. The VTEX Payments system will automatically refund the customer if an item is returned.
 
-<div class = "alert alert-info">
-The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Legacy connectors do not support the functionality.
-</div>
+>ℹ️ The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Legacy connectors do not support the functionality.
diff --git a/docs/tutorials/en/changing-the-total-cost-of-the-order.md b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
index 4bf4bed62..aeab7c644 100644
--- a/docs/tutorials/en/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/en/changing-the-total-cost-of-the-order.md
@@ -42,6 +42,4 @@ When changing or removing items from an order, the order total changes. In this
 
 The order total will be updated once the invoice is added, corresponding to what is captured by the VTEX payment gateway. The VTEX Payments system will automatically refund the customer if an item is returned.
 
-<div class = "alert alert-info">
-The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Legacy connectors do not support the functionality.
-</div>
+>ℹ️ The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Legacy connectors do not support the functionality.
diff --git a/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
index c71eaa5a5..a76fea230 100644
--- a/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/en/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -31,9 +31,7 @@ The table below presents the main use cases for each account type:
 | ---------- | ---------- | ---------- |
 | The [Seller Portal](https://help.vtex.com/en/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) is recommended for external sellers that do not have a VTEX account but want to connect to a VTEX marketplace. This feature allows the VTEX marketplace to [share products](https://help.vtex.com/en/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) with its sellers, reducing friction and simplifying the operation management. Each Seller Portal environment created integrates the seller with a single VTEX marketplace. | The standard account is recommended for stores that prefer to handle all the ecommerce operations, using [unified commerce](https://help.vtex.com/en/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv) strategies. A standard account can act both as a VTEX seller and a VTEX marketplace, connecting to multiple marketplaces and [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex). | A [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) is of strategic use for sales growth operations by integrating physical stores. It offers the advantage of inheriting the catalog of a standard account. Franchise accounts are usually used by franchisees and brand representatives. |
 
-<div class = "alert alert-info">
-Your business model and objectives will help determine the best operating option for you in the VTEX ecosystem. Learn more in the article <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">Marketplace strategies at VTEX</a>.
-</div>
+>ℹ️ Your business model and objectives will help determine the best operating option for you in the VTEX ecosystem. Learn more in the article [Marketplace strategies at VTEX](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
 See below for comparisons explaining how the Seller Portal, standard accounts and franchise accounts relate to the modules and features of the VTEX platform:
 
diff --git a/docs/tutorials/en/collection-types.md b/docs/tutorials/en/collection-types.md
index 184da0bbe..aba0b839f 100644
--- a/docs/tutorials/en/collection-types.md
+++ b/docs/tutorials/en/collection-types.md
@@ -31,9 +31,7 @@ On VTEX, there are three ways to configure Collections:
 | Automatic | CMS | Created by Brand or Category filters | No control |  
 | Hybrid | CMS and Collections module (Beta) | Created by Brand or Category filters. You can also add products manually | No control        |
 
-<div class = "alert alert-warning">
-  <p>Collections created in the CMS module and with more than one <a href = "https://help.vtex.com/en/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">group</a> cannot be reordered in the new Beta Collection module. We recommend you do not change the ordering, as it may compromise the efficiency of the functionality.</p>
-</div>
+>⚠️ Collections created in the CMS module and with more than one <a href = "https://help.vtex.com/en/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">group</a> cannot be reordered in the new Beta Collection module. We recommend you do not change the ordering, as it may compromise the efficiency of the functionality.
 
   ## Manual collections
 
diff --git a/docs/tutorials/en/comprehensive-seller.md b/docs/tutorials/en/comprehensive-seller.md
index 54ca99e69..b5e45a517 100644
--- a/docs/tutorials/en/comprehensive-seller.md
+++ b/docs/tutorials/en/comprehensive-seller.md
@@ -47,9 +47,7 @@ When there is no customer location information set, the seller selection heurist
 
 This occurs both during browsing and in the cart, in order to prevent the customer from seeing products from sellers that do not deliver to their address.
 
-<div class = "alert alert-info">
-Even if during browsing the customer's location information is captured and stored in the <code>regionId</code> field of the Session API, the location is not used in the cart. Only products from the main seller and comprehensive sellers will be available to the customer in the cart. Products from other sellers will only be available after the customer enters the delivery zip code at checkout.
-</div>
+>ℹ️ Even if during browsing the customer's location information is captured and stored in the `regionId` field of the Session API, the location is not used in the cart. Only products from the main seller and comprehensive sellers will be available to the customer in the cart. Products from other sellers will only be available after the customer enters the delivery zip code at checkout.
 
 In cases of more than one comprehensive seller, the checkout selects the one with the highest amount in stock for the item in question, among all comprehensive sellers. Know more in [White label sellers selection](https://help.vtex.com/en/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa). 
 
diff --git a/docs/tutorials/en/configuring-a-seller-on-vtex-marketplace.md b/docs/tutorials/en/configuring-a-seller-on-vtex-marketplace.md
index f7cc64989..6ca143566 100644
--- a/docs/tutorials/en/configuring-a-seller-on-vtex-marketplace.md
+++ b/docs/tutorials/en/configuring-a-seller-on-vtex-marketplace.md
@@ -25,17 +25,13 @@ This article shows how to configure your store as a VTEX seller and start sellin
 
 To learn about what type of information needs to be exchanged between sellers and marketplaces, please read the article [Shared information](https://help.vtex.com/en/tutorial/informacoes-compartilhadas-entre-marketplace-e-seller-na-vtex--3o7WGiBtfnKKZ3Ddug26k3) between a marketplace and a seller on VTEX. If you want your store to operate as a marketplace, check out the article [Configuring a VTEX marketplace](https://help.vtex.com/en/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb).
 
-<div class = "alert alert-info">
-To start selling your products in marketplaces or to find new partners to sell on your marketplace, use <a href="https://help.vtex.com/en/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM">Marketplaces and Integrations</a>, a feature which facilitates the identification of and communication between marketplaces and sellers operating in the VTEX ecosystem.
-</div>
+>ℹ️ To start selling your products in marketplaces or to find new partners to sell on your marketplace, use [Marketplaces and Integrations](https://help.vtex.com/en/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM), a feature which facilitates the identification of and communication between marketplaces and sellers operating in the VTEX ecosystem.
 
 ## Defining the trade policy
 
 On VTEX, the [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) groups the configurations for your catalog, pricing, promotions, logistics, customer segmentation, and payments in a single sales channel. A seller can integrate with the marketplace by using the store's default trade policy or by defining specific settings for the integration, configuring a [trade policy for the marketplace](https://help.vtex.com/en/tutorial/configurando-a-politica-comercial-para-marketplace/).
 
-<div class = "alert alert-info">
-The same trade policy can be used to integrate with multiple marketplaces. <a href="https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X">Requesting additional trade policies</a> to integrate with <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a>, certified connectors (partners), or other VTEX stores is free of charge.
-</div>
+>ℹ️ The same trade policy can be used to integrate with multiple marketplaces. [Requesting additional trade policies](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) to integrate with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex), certified connectors (partners), or other VTEX stores is free of charge.
 
 If you want to configure promotions, you don't have to create a marketplace specific trade policy. You can segment promotions using the [affiliate](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). For more information, read the article [Configuring promotions for marketplaces](https://help.vtex.com/en/tutorial/configurar-promocao-para-marketplace--tutorials_406).
 
@@ -45,9 +41,7 @@ The product assortment sent to the marketplace has to be managed through the tra
 
 On VTEX, the [affiliate](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) is the code created by the VTEX seller to identify the marketplace where their products will be sold. Each marketplace must correspond to a single affiliate. Through the affiliate, the marketplace is notified about orders, changes in the SKU information, and about price and stock changes, for example.
 
-<div class = "alert alert-info">
-The integration with <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex">native connectors</a> creates the affiliate code automatically.  However, when a VTEX seller integrates with a VTEX marketplace or an external one, the seller needs to create the affiliate ID manually.
-</div>
+>ℹ️ The integration with [native connectors](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrating-with-a-native-connector-vtex) creates the affiliate code automatically.  However, when a VTEX seller integrates with a VTEX marketplace or an external one, the seller needs to create the affiliate ID manually.
 
 The seller must follow the steps described in the article [Configuring affiliates](https://help.vtex.com/en/tutorial/como-configurar-afiliado--tutorials_187) and add the identifier code to the marketplace after it has been created. This way, the VTEX marketplace will [add the seller](https://help.vtex.com/en/tutorial/configuring-the-seller--tutorials_392) and associate it to a trade policy.
 
@@ -55,9 +49,7 @@ The seller must follow the steps described in the article [Configuring affiliate
 
 The marketplace does not automatically receive the products after integrating with the seller. First, the seller must [reindex the database](https://help.vtex.com/en/tutorial/entendendo-o-funcionamento-da-indexacao). This process prepares the SKU information and products and sends catalog, price, and stock general information to the marketplace.  
 
-<div class = "alert alert-info">
-Please note that only the <a href="https://help.vtex.com/en/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA">sponsor user (owner)</a> has permission to reindex a VTEX store database. During reindexing, which may vary in terms of time, the products are queued for updating the information, while still remaining available for sale on the store site. 
-</div>
+>ℹ️ Please note that only the [sponsor user (owner)](https://help.vtex.com/en/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA) has permission to reindex a VTEX store database. During reindexing, which may vary in terms of time, the products are queued for updating the information, while still remaining available for sale on the store site.
 
 To reindex the database, paste the link below in your browser, replacing the `{storename}` with the name of your store:
 
diff --git a/docs/tutorials/en/configuring-access-without-www.md b/docs/tutorials/en/configuring-access-without-www.md
index 86afd45a3..ad9f058b8 100644
--- a/docs/tutorials/en/configuring-access-without-www.md
+++ b/docs/tutorials/en/configuring-access-without-www.md
@@ -31,9 +31,7 @@ Your main domain needs to contain a subdomain, that may or may not be `www`. See
 - `store.mybrand.com` - Valid main domain.
 - `mystore.com` - Not a valid main domain because it does not have a subdomain, but can be redirected.
 
-<div class = "alert alert-info">
-  Learn how to <a href="https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450">configure your store's main domain</a>.
-</div>
+>ℹ️ Learn how to [configure your store's main domain](https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450).
 
 This redirection can be done in many ways. Although being quite technical and dependent on other factors, the most popular one is using `htaccess` on the server.
 
diff --git a/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index d9b17743f..eef6b0d8b 100644
--- a/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/en/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -17,9 +17,7 @@ subcategory: 6bSdupUQgvuXjBL9Igawxl
 
 Bulk data import simplifies the process of updating and maintaining information for buyer organizations, their users (members), and cost centers.
 
-<div class = "alert alert-info">
-Before configuring the bulk import feature, you should have the <a href="https://developers.vtex.com/docs/apps/vtex.b2b-suite">B2B Suite</a> installed in your store.
-</div>
+>ℹ️ Before configuring the bulk import feature, you should have the [B2B Suite](https://developers.vtex.com/docs/apps/vtex.b2b-suite) installed in your store.
 
 Here's how to import data in bulk into the VTEX platform:
 
@@ -27,17 +25,13 @@ Here's how to import data in bulk into the VTEX platform:
 
 2. In the Organizations tab, click **New**, and then Bulk Import. Click the Upload button and select your **XLSX file**, or drag and drop the file into the dashed area. The imported file must be smaller than 50 MB.
 
-<div class = "alert alert-info">
-If necessary, download a template file by clicking VTEX File Template at the bottom of the import window and enter the import data.
-</div>
+>ℹ️ If necessary, download a template file by clicking VTEX File Template at the bottom of the import window and enter the import data.
 
 <ol start="3">
 	<li>Once the platform has verified the imported file and found no errors, click Import.</li>
 </ol>
 
-<div class = "alert alert-info">
-If the platform detects any errors, check the section <b>Import errors</b>.
-</div>
+>ℹ️ If the platform detects any errors, check the section **Import errors**.
 
 <ol start="4">
 	<li>Once the import process is complete, you can click View Import Details to access the import report.</li>
@@ -55,9 +49,7 @@ To get a detailed overview of the detected problems, follow the steps below:
 2. Download the spreadsheet by clicking **Download Reviewed XLSX**. This spreadsheet shows the error details.
 3. After fixing the errors, you can restart the import process by uploading the corrected file again.
 
-<div class = "alert alert-info">
-Make sure you only upload the file with corrections to the previously detected errors to ensure a successful import.
-</div>
+>ℹ️ Make sure you only upload the file with corrections to the previously detected errors to ensure a successful import.
 
 ![Bulk import - EN](https://images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/f15af7d4180b8949ef33c25c761122a8/Bulk_import_vers_o_error-gif-EN.gif)
 
diff --git a/docs/tutorials/en/configuring-dns-pointing-to-vtex.md b/docs/tutorials/en/configuring-dns-pointing-to-vtex.md
index 07cbd43c0..54f5eb433 100644
--- a/docs/tutorials/en/configuring-dns-pointing-to-vtex.md
+++ b/docs/tutorials/en/configuring-dns-pointing-to-vtex.md
@@ -68,16 +68,14 @@ Although not recommended, another alternative would be not including CAA records
 
 To easily create/verify your CAA records, you can use [CAA Record Helper by SSLMate](https://sslmate.com/caa/). The [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) program can also help you verify your records with the `dig domain.com CAA` command – a `SERVFAIL` status can indicate non-compliance of your DNS server.
 
-<div class = "alert alert-info">
-Learn more:
-<p>
-<ul>
-<li><a href="https://sslmate.com/caa/">CAA Record Helper by SSLMate</a></li>
-<li><a href="https://letsencrypt.org/docs/caa/">Let's Encrypt: Certificate Authority Authorization (CAA)</a></li>
-<li><a href="https://sslmate.com/caa/about">SSL Mate: About CAA</a></li>
-</ul>
-</p>
-</div>
+>ℹ️ Learn more:
+>
+> *[CAA Record Helper by SSLMate](https://sslmate.com/caa/)
+>
+> *[Let's Encrypt: Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)
+>
+> *[SSL Mate: About CAA](https://sslmate.com/caa/about)
+> 
 
 ## Pointing the DNS
 
@@ -93,9 +91,7 @@ If your storefront is powered by [CMS IO](https://help.vtex.com/en/tracks/cms--2
 
 After you receive the internal pointing confirmation, you must do the [common DNS pointing](#common-dns-pointing) within 5 days. Otherwise the internal pointing will be deleted and you will need to redo the request.
 
-<div class = "alert alert-info">
-Learn more at <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live">Go live with Store Framework</a> or <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migration from legacy CMS to Store Framework</a>.
-</div>
+>ℹ️ Learn more at [Go live with Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live) or [Migration from legacy CMS to Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 ### Common DNS pointing
 
diff --git a/docs/tutorials/en/configuring-domains-in-account-management.md b/docs/tutorials/en/configuring-domains-in-account-management.md
index 1903ac461..bfd5895f4 100644
--- a/docs/tutorials/en/configuring-domains-in-account-management.md
+++ b/docs/tutorials/en/configuring-domains-in-account-management.md
@@ -33,9 +33,7 @@ Any domain registered this way needs to contain a subdomain, that may or may not
 - `www.mystore.com` - Valid domain.
 - `store.mybrand.com` - Valid domain.
 
-<div class = "alert alert-info">
-  Learn how to <a href="https://help.vtex.com/en/tutorial/configuring-access-without-www--tutorials_4278">configure access without www</a>.
-</div>
+>ℹ️ Learn how to [configure access without www](https://help.vtex.com/en/tutorial/configuring-access-without-www--tutorials_4278).
 
 ## Register new domain
 
diff --git a/docs/tutorials/en/configuring-payment-conditions-for-b2b.md b/docs/tutorials/en/configuring-payment-conditions-for-b2b.md
index 5cdacf407..802eecf6e 100644
--- a/docs/tutorials/en/configuring-payment-conditions-for-b2b.md
+++ b/docs/tutorials/en/configuring-payment-conditions-for-b2b.md
@@ -19,9 +19,7 @@ In a B2B operation, [payment conditions](https://help.vtex.com/es/tutorial/how-t
 
 An organization administrator user can customize the available payment options by cost center.
 
-<div class = "alert alert-info">
-When you configure a payment condition in the Payments module, it will display as a payment method in the <b>Available</b> list in the <b>Payment Conditions</b> tab. To view the list, click the name of the organization. The payment methods listed are the ones that are already assigned to the organization.
-</div>
+>ℹ️ When you configure a payment condition in the Payments module, it will display as a payment method in the **Available** list in the **Payment Conditions** tab. To view the list, click the name of the organization. The payment methods listed are the ones that are already assigned to the organization.
 
 ## Linking payment conditions to the organization
 To link a payment condition to a buyer organization, follow the instructions below:
diff --git a/docs/tutorials/en/configuring-price-divergence-rule.md b/docs/tutorials/en/configuring-price-divergence-rule.md
index 592981d67..86562ce57 100644
--- a/docs/tutorials/en/configuring-price-divergence-rule.md
+++ b/docs/tutorials/en/configuring-price-divergence-rule.md
@@ -33,9 +33,7 @@ We recommend that the seller creates the Price Divergence rule before configurin
 
 The [Price Divergence rule](https://help.vtex.com/en/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) is composed of one or more order authorization rules, which correspond to ranges between 0% and 100% of the order price. The configuration is done so that each range is associated with an automatic processing action.
 
-<div class = "alert alert-info">
-To create a Price Divergence rule, the user must have a Super Admin (Owner) or OMS Full role. To ensure security in the management of your operations, please refer to the article Best practices for secure user management.
-</div>
+>ℹ️ To create a Price Divergence rule, the user must have a Super Admin (Owner) or OMS Full role. To ensure security in the management of your operations, please refer to the article Best practices for secure user management.
 
 To create a price divergence rule, follow the steps below:
 
@@ -79,9 +77,7 @@ You can edit Price Divergence rule at any time. To do this, log in to your VTEX
 
 On this page, you can delete the price divergence rule by clicking on **DELETE RULES**. This causes all configured authorization rules to be permanently deleted.
 
-<div class = "alert alert-info">
-This action cannot be undone. If you want to reapply the rules, you need to configure them again. The same applies to the authorization rules that make up the Price Divergence rule.
-</div>
+>ℹ️ This action cannot be undone. If you want to reapply the rules, you need to configure them again. The same applies to the authorization rules that make up the Price Divergence rule.
 
 On the same page, in the **All** tab, you can see the list of all the order authorization rules created. To delete an authorization rule, click on the **DELETE RULE** button next to the rule you want to delete.
 
diff --git a/docs/tutorials/en/configuring-promotions-for-marketplaces.md b/docs/tutorials/en/configuring-promotions-for-marketplaces.md
index 86b889f07..09e1894c5 100644
--- a/docs/tutorials/en/configuring-promotions-for-marketplaces.md
+++ b/docs/tutorials/en/configuring-promotions-for-marketplaces.md
@@ -51,9 +51,7 @@ For this type of promotion, it is important to keep the following information in
 
 There are differences between the settings available for VTEX marketplaces and external marketplaces. See in the table below the features applicable in each case.
 
-<div class = "alert alert-warning">
-  <p>In the case of external integrations, configurations are unique to each marketplace, and it’s up to them to decide which features they will use.</p>
-</div>
+>⚠️ In the case of external integrations, configurations are unique to each marketplace, and it’s up to them to decide which features they will use.
 
 | Settings  | Description      | Available for VTEX marketplaces? | Available for external marketplaces? |
 | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | ------------------------------------ |
@@ -136,6 +134,4 @@ If necessary, you can segment promotions for specific marketplaces. You can obta
 3. In the **Sales Policy** section, select the **Equal to** and **Delivered by me (Other stores)** options.
 4. Click on `Save`.
 
-<div class = "alert alert-warning">
-  <p> Please remember to <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindex all products included in the promotion</a> after you’ve created it and at the beginning and end of the promotions. This will ensure that the prices of your products are up to date.</p>
-</div>
+>⚠️ Please remember to <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindex all products included in the promotion</a> after you’ve created it and at the beginning and end of the promotions. This will ensure that the prices of your products are up to date.
diff --git a/docs/tutorials/en/configuring-xml.md b/docs/tutorials/en/configuring-xml.md
index 830d82388..f278b0d7b 100644
--- a/docs/tutorials/en/configuring-xml.md
+++ b/docs/tutorials/en/configuring-xml.md
@@ -23,9 +23,7 @@ The XML configuration functionality in VTEX makes use of this feature of being a
 
 This means that, when entering the tag names in the __Id do Produto__ field, for example, with __Product_Id__, the VTEX database will understand that this information has to be entered there, making it possible to understand by Google, Facebook, Buscapé and many other systems that will read the structure.
 
-<div class = "alert alert-info">
-  <p>Changes to XML take an average of two hours to be updated.</p>
-</div>
+>ℹ️ Changes to XML take an average of two hours to be updated.
 
 Here are some examples of partners that integrate with VTEX XML:
 
diff --git a/docs/tutorials/en/creating-a-more-for-less-promotion.md b/docs/tutorials/en/creating-a-more-for-less-promotion.md
index 16fbeade2..7b34fafc9 100644
--- a/docs/tutorials/en/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/en/creating-a-more-for-less-promotion.md
@@ -62,11 +62,9 @@ In this section, you can define to which sellers the promotion will apply. You c
 
 For the promotion to be valid for all sellers, leave the field blank.
 
-<div class = "alert alert-warning">
-  <p>You cannot select a white label seller directly. To include a white label seller in the promotion, you have two options:</p><ol>1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.
-</ol><ol>2. Leave the selection empty, including all sellers. Here, all types of sellers — white label or not — will be added to the promotion.
-</ol>
-</div>
+>⚠️ You cannot select a white label seller directly. To include a white label seller in the promotion, you have two options:1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.
+> 2. Leave the selection empty, including all sellers. Here, all types of sellers — white label or not — will be added to the promotion.
+> 
 
 ![Restringir - EN](https://images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/8dba06aef0da8ce4d546c0e2fea91917/Restringir_-_EN.png)
 
@@ -91,9 +89,7 @@ In this section, you can define the products, number of items, and discounts inc
     - **SKUs**: names or IDs of the SKUs to which the discount will apply. You can import a list of SKUs by clicking on the `Select a .txt file` button. The text file (.txt) must contain each SKU ID in a different row. You can also download the list of SKUs added to the field by clicking on the `Download SKU list` button.
     - **Collections**: Collections to which the promotion will apply. The promotion will only be applied to products in the collections listed in this field. You can add a collection by entering its name. You can also select more than one collection.
 
-<div class = "alert alert-info">
-  <p>If you do not inform any product collection or SKU, the platform will not allow the creation of the promotion.</p> <p>
-</div>
+>ℹ️ If you do not inform any product collection or SKU, the platform will not allow the creation of the promotion. <p>
 
 - **And gets** `number` **of these products**: the number of items defined to receive the discount. Required field.
    - **With a discount of**: the percentage discount the customer will receive if they buy the number of items defined in the promotion.
@@ -132,9 +128,7 @@ In this section, we will detail the conditions you must apply for a promotion to
 - **Create a new coupon with the UTMs above**: Create a coupon based on the UTM values selected above to give customers access to this promotion using only the coupon code.
 - **Payment system**: Allows you to choose if the promotion will be applied to one or more of the selected payment methods.
 
-  <div class = "alert alert-info">
-  <p> By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
- </div>
+  >ℹ️ By default, you can add up to 20 payment methods per promotion. You can also customize it to add up to 100 payment methods. If you need to use more than 20 payment methods, please contact [our Support](https://support.vtex.com/hc/en-us/requests).
 
 ![Condições de promoção - EN](https://images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/8efc11e8c289f9777a22e3b7d29362d5/Condi__es_de_promo__o_-_EN.png)
 
diff --git a/docs/tutorials/en/creating-a-specification-group-in-a-category.md b/docs/tutorials/en/creating-a-specification-group-in-a-category.md
index d1e6b6796..40a4accb8 100644
--- a/docs/tutorials/en/creating-a-specification-group-in-a-category.md
+++ b/docs/tutorials/en/creating-a-specification-group-in-a-category.md
@@ -24,9 +24,7 @@ In this article, we explain how the specification inheritance works and how to c
 * [Specification inheritance](#specification-inheritance)
 * [Step-by-step instructions in the VTEX Admin](#step-by-step-instructions-in-the-vtex-admin)
 
-<div class = "alert alert-info">
-  <p>To create a specification group using the <strong>Catalog API</strong>, follow the <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> developer's guide.</p>
-</div>
+>ℹ️ To create a specification group using the **Catalog API**, follow the [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) developer's guide.
 
 ## Specification inheritance
 
diff --git a/docs/tutorials/en/creating-collections-beta.md b/docs/tutorials/en/creating-collections-beta.md
index 8f4f0bb52..52e1ca6d0 100644
--- a/docs/tutorials/en/creating-collections-beta.md
+++ b/docs/tutorials/en/creating-collections-beta.md
@@ -47,9 +47,7 @@ Follow the step by step below to add a new collection:
 5. Click on `Create` to update the information filled in the form.
 6. Then, [select the products](https://help.vtex.com/en/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye#products-selection) that will be part of the collection.
 
-<div class = "alert alert-info">
-  <p>Note that the collections created in this module are not automatically changed. Automatic collections - made by applying filters - cannot be configured in the module.</p>
-</div>
+>ℹ️ Note that the collections created in this module are not automatically changed. Automatic collections - made by applying filters - cannot be configured in the module.
 
 ### Collection data fields
 
@@ -112,7 +110,7 @@ If you want to add in bulk, apply one of the filters and click on the `Add All`
 
 #### By spreadsheet
 
-<div class = "alert alert-info">The maximum limit for import and export is 10,000 SKUs per operation.</div>
+>ℹ️ The maximum limit for import and export is 10,000 SKUs per operation.
 
 You can also add items to a collection using a spreadsheet by following the steps below:
 
diff --git a/docs/tutorials/en/creating-landing-pages-per-binding.md b/docs/tutorials/en/creating-landing-pages-per-binding.md
index 66598b267..c01500ad2 100644
--- a/docs/tutorials/en/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/en/creating-landing-pages-per-binding.md
@@ -33,16 +33,12 @@ In the Admin, you can create customized landing pages by [binding](https://help.
 - `Description` — Summary of the new web page to be displayed on search engines' result pages. 
 - `Keywords` — Topics that define what the page content is about, helping to deliver the latter to the interested users navigating on search engines' result pages.
 
-  <div class = "alert alert-info">
-All five fields above directly impact the store accesses and positioning on search engines' result pages. Before filling the page's metadata out, be mindful of SEO best practices.
-</div>
+  >ℹ️ All five fields above directly impact the store accesses and positioning on search engines' result pages. Before filling the page's metadata out, be mindful of SEO best practices.
 
 5. Choose a template from the available ones to be displayed on your new landing page in the `Default` field.
 6. If you desire to create a conditional template, click on the `Add conditional template` button and fill out the fields according to the desired conditions. 
 
-  <div class = "alert alert-warning">
-Notice that the condition template will only be displayed when one <i>or</i> all predefined conditions are matched on the interface.
-</div>
+  >⚠️ Notice that the condition template will only be displayed when one <i>or</i> all predefined conditions are matched on the interface.
 
 7. Save your changes.
 
diff --git a/docs/tutorials/en/creating-landing-pages.md b/docs/tutorials/en/creating-landing-pages.md
index a1e53b8a1..4e5fd834c 100644
--- a/docs/tutorials/en/creating-landing-pages.md
+++ b/docs/tutorials/en/creating-landing-pages.md
@@ -39,17 +39,11 @@ In the Admin, you can create customized landing pages, such as pages for special
 
 >⚠️ To avoid conflicts and protect the integrity of the system, changing an existing URL route is not allowed. If you need to change a URL, we recommend creating a new page with the desired path and deactivating the old one if necessary.
 
-<div class = "alert alert-info">
-<p>The five fields above have a direct impact on store hits and search engine results rankings. Before filling in the page metadata, keep SEO best practices in mind.
-</p>
-</div>
+>ℹ️ The five fields above have a direct impact on store hits and search engine results rankings. Before filling in the page metadata, keep SEO best practices in mind.
 
 4.Choose a template for your new landing page from the **Templates** dropdown menu.
 
-<div class = "alert alert-info">
-  <p>If you want to create a conditional template, click on <strong>Add Conditional Template</strong> and fill in the fields according to the desired conditions. Please note that the conditional template will only be displayed when one or all of the predefined conditions match in the interface.
-</p>
-</div>
+>ℹ️ If you want to create a conditional template, click on **Add Conditional Template** and fill in the fields according to the desired conditions. Please note that the conditional template will only be displayed when one or all of the predefined conditions match in the interface.
 
 5.Save your changes.
 
diff --git a/docs/tutorials/en/creating-pickup-points.md b/docs/tutorials/en/creating-pickup-points.md
index b054020e6..5da928cc0 100644
--- a/docs/tutorials/en/creating-pickup-points.md
+++ b/docs/tutorials/en/creating-pickup-points.md
@@ -50,8 +50,7 @@ Select <i class="fas fa-toggle-on"></i> to activate the pickup point.
 * **Country:** the country where the pickup point is located.
 * **Search address:** enter the address information for the search. You can use the zip code, street, city, number, and additional address information. 
 * To edit the address information, click `Edit`. 
-* To add a different address, click `Clear` and search again.<div class = "alert alert-info">
-The address information and the location on the map will be displayed at checkout.</div>
+* To add a different address, click `Clear` and search again.>ℹ️ The address information and the location on the map will be displayed at checkout.
 
 #### Additional information
 
@@ -62,7 +61,7 @@ The address information and the location on the map will be displayed at checkou
 
 * **Days of the week:**
     1. Check the boxes for the days the pickup point will be available for your customers to pick up their orders. 
-    2. Select the pickup point's business hours for each day.<div class = "alert alert-info">If this field is not filled in, the platform will consider that the pickup point operates 24 hours a day.</div>
+    2. Select the pickup point's business hours for each day.>ℹ️ If this field is not filled in, the platform will consider that the pickup point operates 24 hours a day.
 
 * **Exceptions or holidays:** to add specific days when the pickup point is not operating, follow the steps below.
     3. Click `Add an exception`;
@@ -75,13 +74,11 @@ The address information and the location on the map will be displayed at checkou
 
 You can create pickup points by importing the template (XLS file). This way, you can create more than one pickup point at a time.
 
-<div class = "alert alert-info">
-The XLS file must not exceed 10MB (approximately 50,000 pick points). If necessary, you can upload more than one template. 
-</div>
+>ℹ️ The XLS file must not exceed 10MB (approximately 50,000 pick points). If necessary, you can upload more than one template.
 
 1. In the VTEX Admin, go to **Shipping > Pickup points**, or type *Pickup points* in the search bar at the top of the page. 
 2. Click <i class="fas fa-upload"></i> `Upload an XLS`.
-3. Download the template and fill in the [fields](#template-fields).<div class = "alert alert-info">Please note that the template comes with example values, which must be replaced with the data from your store's pickup points.</div>
+3. Download the template and fill in the [fields](#template-fields).>ℹ️ Please note that the template comes with example values, which must be replaced with the data from your store's pickup points.
 4. After uploading the template, click `OK`.   
 
 ### Template fields
diff --git a/docs/tutorials/en/creating-price-tables.md b/docs/tutorials/en/creating-price-tables.md
index 771d25aa0..f068be80b 100644
--- a/docs/tutorials/en/creating-price-tables.md
+++ b/docs/tutorials/en/creating-price-tables.md
@@ -32,8 +32,6 @@ To find a Price Table:
 
 To include a price in the Price Table, you will need to add a base price to your SKUs. Access our article on [how to add a base price](https://help.vtex.com/en/tutorial/cadastrar-o-preco-base-de-um-produto--4S9SbPWlVmOAAWO6yq8wE6).
 
-<div class = "alert alert-info"> 
-You can not create price tables with equal names. You can not add special characters to price table names. Just letters and numbers. </div> 
-<div class = "alert alert-warning"> 
-For security reasons, you can not manually delete price tables. If you need to delete a price table, open a ticket with VTEX support. </div>
+>ℹ️ You can not create price tables with equal names. You can not add special characters to price table names. Just letters and numbers. 
+>⚠️ For security reasons, you can not manually delete price tables. If you need to delete a price table, open a ticket with VTEX support.
 
diff --git a/docs/tutorials/en/creating-service-for-a-sku.md b/docs/tutorials/en/creating-service-for-a-sku.md
index 5726272cd..7204d30ca 100644
--- a/docs/tutorials/en/creating-service-for-a-sku.md
+++ b/docs/tutorials/en/creating-service-for-a-sku.md
@@ -75,9 +75,7 @@ To link a service to a SKU, please follow the steps below:
 5. Click on `Export`.
 6. Save the exported template to your computer in CSV format.
 7. Fill in the [template fields](#template-fields). Keep the file in CSV format when saving changes.
-<div class = "alert alert-warning">
-  <p>The size of the template file cannot exceed 4Mb (4096KB).</p>
-</div>
+>⚠️ The size of the template file cannot exceed 4Mb (4096KB).
 8. Click on the bar next to the `Select` button, as shown below.
   ![Anexos - EN](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/6d834bfa0595150d8c6a5b69c6088e23/sku-services.png)
 9. Select the updated CSV template.
@@ -103,7 +101,5 @@ Use the template carefully, always making sure that the information is correctly
 - **Custo:** the cost of the service to the store.
 - **Ativo:** status of the service. Enter `1` to keep the service active and `0` to keep it inactive.
 
-<div class = "alert alert-warning">
-  <p>Adding a new template will not replace the services already linked to the SKU. To unlink a service, use the endpoint <a href ="https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/skuservice/-skuServiceId-">Dissociate SKU service</a>.</p>
-</div>
+>⚠️ Adding a new template will not replace the services already linked to the SKU. To unlink a service, use the endpoint <a href ="https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/skuservice/-skuServiceId-">Dissociate SKU service</a>.
 
diff --git a/docs/tutorials/en/creating-synonyms.md b/docs/tutorials/en/creating-synonyms.md
index 5ce206008..79723fdee 100644
--- a/docs/tutorials/en/creating-synonyms.md
+++ b/docs/tutorials/en/creating-synonyms.md
@@ -15,7 +15,7 @@ legacySlug: configuring-synonyms
 subcategory: BBzMtJan1UTxC9QZODnlN
 ---
 
-<div class = "alert alert-info"> We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Synonyms</a> instead of <a href="https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Substitute Words</a> to associate words with products, as synonyms allow you to manage terms per product in a more scalable way. Contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a> for more information.</div>
+>ℹ️ We recommend using [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) instead of [Substitute Words](https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete) to associate words with products, as synonyms allow you to manage terms per product in a more scalable way. Contact our [Support team](https://support.vtex.com/hc/pt-br/requests) for more information.
 
 There are two ways to set up synonyms in VTEX Admin: [individually](#creating-synonyms-individually) or by [importing a spreadsheet in CSV format](#importing-csv-spreadsheet). If you need to register synonyms in bulk, we recommend using the spreadsheet. See the instructions for each configuration form in the following sections.
 
diff --git a/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md b/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md
index 36d4cd326..0de12674f 100644
--- a/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md
+++ b/docs/tutorials/en/data-dictionary-vtex-data-pipeline-beta.md
@@ -15,9 +15,7 @@ legacySlug: vtex-data-pipeline-catalog-beta
 subcategory: oMrzcOMVbBpH0reeMFHFg
 ---
 
-<div class= "alert alert-info">
-This feature is currently in beta, which means we are working on improving it. If you have any questions, please contact <a href="https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue">our support</a>.
-</div>  
+>ℹ️ This feature is currently in beta, which means we are working on improving it. If you have any questions, please contact [our support](https://vtexhelp.zendesk.com/auth/v2/login/signin?return_to=https%3A%2F%2Fsupport.vtex.com%2Fhc%2Fpt-br%2Frequests&theme=hc&locale=pt-br&brand_id=144968&auth_origin=144968%2Ctrue%2Ctrue).  
 
 **VTEX Data Pipeline** is a tool that only VTEX clients can leverage, which allows exploring and analyzing the ecommerce data that is currently available on our servers. **Data Pipeline** is a VTEX add-on product that integrates the data from your ecommerce website to the data warehouse and BI tools of your choice cleanly and securely.  
 
diff --git a/docs/tutorials/en/data-subject-rights.md b/docs/tutorials/en/data-subject-rights.md
index 00fb2b712..7a1e4ba1a 100644
--- a/docs/tutorials/en/data-subject-rights.md
+++ b/docs/tutorials/en/data-subject-rights.md
@@ -57,9 +57,7 @@ To export data from the Master Data v1 through the Admin dashboard, follow these
 
 Repeat this step for customer data (**CL**) and address (**AD**) entities and any other entity you have configured to get personal information from your customers.
 
-<div class = "alert alert-info">
-Learn more about <a href="https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters">filtering data</a> and <a href="https://help.vtex.com/en/tutorial/exporting-data--tutorials_1125">exporting data</a> in the Master Data v1 interface.
-</div>
+>ℹ️ Learn more about [filtering data](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) and [exporting data](https://help.vtex.com/en/tutorial/exporting-data--tutorials_1125) in the Master Data v1 interface.
 
 #### Master Data v2
 
@@ -87,9 +85,7 @@ Your customers can exercise their right to consent and rectify personal data usi
 - View and edit their address information.
 - View and edit their saved payment methods.
 
-<div class = "alert alert-info">
-Learn more about the <a href="https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh">My Account page</a>.
-</div>
+>ℹ️ Learn more about the [My Account page](https://help.vtex.com/en/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh).
 
 ## Consent
 
@@ -103,9 +99,7 @@ When completing a purchase at VTEX Checkout, your customers can choose to subscr
 
 In case you need to [adjust the subscription status of a particular customer](https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1), your development team can do it directly using the Master Data v1 API.
 
-<div class = "alert alert-info">
-Learn more about the My Account page and how your developers can<a href="https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1">directly edit a customer newsletter subscription</a>.
-</div>
+>ℹ️ Learn more about the My Account page and how your developers can[directly edit a customer newsletter subscription](https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1).
 
 ### Abandoned cart
 
@@ -125,9 +119,7 @@ The right to consent allows people to buy in your store without their personal d
 
 Please contact your development team to make this option available following the [Enable the Save user data opt-in](https://developers.vtex.com/docs/guides/enable-the-save-user-data-opt-in) guide.
 
-<div class = "alert alert-info">
-Learn more about <a href="https://help.vtex.com/en/tutorial/configurar-carrinho-abandonado--tutorials_740">abandoned cart automation</a>.
-</div>
+>ℹ️ Learn more about [abandoned cart automation](https://help.vtex.com/en/tutorial/configurar-carrinho-abandonado--tutorials_740).
 
 ## Erasure
 
diff --git a/docs/tutorials/en/declining-order-cancelation.md b/docs/tutorials/en/declining-order-cancelation.md
index 120bc54e3..fcd079b55 100644
--- a/docs/tutorials/en/declining-order-cancelation.md
+++ b/docs/tutorials/en/declining-order-cancelation.md
@@ -23,13 +23,9 @@ The order flow has a [cancellation window](https://help.vtex.com/en/tutorial/ord
 
 For developer’s content, see [Order canceling improvements](https://developers.vtex.com/docs/guides/order-canceling-improvements).
 
-<div class = "alert alert-info">
-In this article, the terms marketplace and seller refer to <a href="https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplace</a> and <a href="https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace">VTEX seller</a>. The decline cancellation request feature is not available for external sellers and marketplaces.
-</div>
+>ℹ️ In this article, the terms marketplace and seller refer to [VTEX marketplace](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace) and [VTEX seller](https://help.vtex.com/en/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace). The decline cancellation request feature is not available for external sellers and marketplaces.
 
-<div class = "alert alert-warning">
-Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
-</div>
+>⚠️ Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Order cancellation declined diagram
 
diff --git a/docs/tutorials/en/deleting-a-folder-from-cms.md b/docs/tutorials/en/deleting-a-folder-from-cms.md
index c78d2f31e..e02088fbd 100644
--- a/docs/tutorials/en/deleting-a-folder-from-cms.md
+++ b/docs/tutorials/en/deleting-a-folder-from-cms.md
@@ -28,9 +28,11 @@ To delete a CMS folder, follow the steps below:
 
 ![erroDeletarPasta2](https://images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
 
-<div class = "alert alert-danger">
-Some folders are required. Your store will not function properly without them. Others are important, so it's not a good idea to delete them.<br><br>Understand this theme deeper by reading the article <a href="http://help.vtex.com/en/tutorial/cms-folder-structure">CMS folder structure</a>.
-</div>
+>❗ Some folders are required. Your store will not function properly without them. Others are important, so it's not a good idea to delete them.
+>
+> 
+>
+> Understand this theme deeper by reading the article [CMS folder structure](http://help.vtex.com/en/tutorial/cms-folder-structure).
 
 If a folder contains other folders, you must delete all internal folders before deleting the more external one. Otherwise, the system will return the error "Object reference not set to an instance of an object", as in the image below.
 
diff --git a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
index fb24676b4..399d64f3b 100644
--- a/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/en/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -15,9 +15,7 @@ legacySlug: displaying-vtex-ad-network-ads-in-your-store-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>VTEX Ad Network is in beta, which means that we are working to improve. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
-</div>
+>ℹ️ VTEX Ad Network is in beta, which means that we are working to improve. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). If you are not yet a customer but are interested in this solution, please fill out the [contact form](https://vtex.com/us-en/contact/).
 
 With [VTEX Ad Network (Beta)](https://help.vtex.com/en/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), VTEX stores can offer ad space in their stores for brands to promote products. VTEX will select ads for products already in your catalog, and your store will receive a fee for each ad click in your store.
 
diff --git a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
index 5d57a96e1..cf0f2506b 100644
--- a/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/en/dynamic-relevance-in-intelligent-search-beta.md
@@ -28,9 +28,7 @@ In Intelligent Search, you can configure your search relevance in two ways:
 
 Only one of these is applied to your store at a time, and you can [change the relevance type configured](#changing-relevance-type). If you change the relevance from manual to dynamic, all the manual rules you have set will remain saved.
 
-<div class = "alert alert-info">
-Manual relevance is the store default setting.
-</div>
+>ℹ️ Manual relevance is the store default setting.
 
 ## Manual relevance
 
@@ -65,9 +63,7 @@ To enable dynamic relevance, follow these steps:
 
 To change the relevance type, follow the steps below:
 
-<div class = "alert alert-warning">
-We do not recommend constantly changing the relevance type used by your store. The system needs a week to settle.
-</div>
+>⚠️ We do not recommend constantly changing the relevance type used by your store. The system needs a week to settle.
 
 1. In the VTEX Admin, go to **Storefront > Intelligent Search > Relevance Rules** or type **Relevance Rules** in the search bar at the top of the page.
 2. Click `Change`.
diff --git a/docs/tutorials/en/events-available-in-audit.md b/docs/tutorials/en/events-available-in-audit.md
index e0f62e390..8a106f4c3 100644
--- a/docs/tutorials/en/events-available-in-audit.md
+++ b/docs/tutorials/en/events-available-in-audit.md
@@ -35,9 +35,7 @@ Below, you will find a list of the potential events available in [Audit](https:/
 * [Headless CMS](#headless-cms)
 * [Seller Management](#seller-management)
 
-<div class = "alert alert-info">
-In case you encounter an event in Audit which has not been included in this list, please inform us through the <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">documentation feedback page</a>.
-</div>
+>ℹ️ In case you encounter an event in Audit which has not been included in this list, please inform us through the [documentation feedback page](https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform).
 
 >⚠️ In the Audit filter options, you can find **Shipping Options**, **Profile System**, and **Billing** options besides the applications listed in this guide. Since these options refer to internal resources or features in closed beta, most accounts will not have events associated with them.
 
diff --git a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
index 4894319a9..5aee75ce4 100644
--- a/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/en/exporting-and-importing-product-and-sku-specifications.md
@@ -19,9 +19,7 @@ After defining the category tree and registering [product specifications and SKU
 
 In this article, we explain how to export and import spreadsheets with product and SKU specifications in VTEX Admin.
 
-<div class = "alert alert-info">
-  <p>To export and import specifications using the <strong>Catalog API</strong>, follow the developer guide <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a>.</p>
-</div>
+>ℹ️ To export and import specifications using the **Catalog API**, follow the developer guide [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification).
 
 ## Exporting product or SKU specifications
 
@@ -37,9 +35,7 @@ In this article, we explain how to export and import spreadsheets with product a
 
 ![skuexport2.en](https://images.ctfassets.net/alneenqid6w5/6oBhxWWjktsofR8XGRzl3E/87e1859f2f3ece16f3c0e1c527a392ee/skuexport2.en.png)
 
-<div class = "alert alert-info">
-  <p>The exported spreadsheet will be available in your email for one week. If you exceed this period, follow the export step-by-step again to generate a new spreadsheet.</p>
-</div>
+>ℹ️ The exported spreadsheet will be available in your email for one week. If you exceed this period, follow the export step-by-step again to generate a new spreadsheet.
 
 ## Importing product or SKU specifications
 
diff --git a/docs/tutorials/en/filtering-all-orders.md b/docs/tutorials/en/filtering-all-orders.md
index 3b092ba68..18b093cfc 100644
--- a/docs/tutorials/en/filtering-all-orders.md
+++ b/docs/tutorials/en/filtering-all-orders.md
@@ -15,9 +15,7 @@ legacySlug: filtering-orders-in-oms, filtering-orders-on-the-oms
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class = "alert alert-info">
-You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
-</div>
+>ℹ️ You can only access information from orders created in the last two years, and that same period is valid for customers through [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 In the **Orders** module, the **All Orders** page allows you to access your store's orders, search and filter them, as shown in the image below:
 
@@ -49,9 +47,7 @@ To search using the search bar, type in the desired term and press the `enter` k
 
 [Sequence](https://help.vtex.com/en/tutorial/cuidados-ao-definir-a-numeracao-de-pedido--VAKKptfcaOxFxM8gfPobu) is a six-digit string displayed in your VTEX Admin right after the order ID. For example, in order `1268540501456-01 (501456)`, the order ID is `1268540501456`, the `-01` indicates that a seller will handle fulfillment, and the sequence is `501456`. 
 
-<div class = "alert alert-info">
-In addition to the list above, it is possible to activate other search criteria, as you will see in the <a href="https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192#filters-other">Other</a> section.
-</div>
+>ℹ️ In addition to the list above, it is possible to activate other search criteria, as you will see in the [Other](https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192#filters-other) section.
 
 By default, the **All orders** page has the orders created **Today** filter activated. To search by other dates, use the filters available under [Filters: Date](#filters-date) or [Created](#created).
 
@@ -90,9 +86,7 @@ When you click `Filters`, a modal is displayed with the following options:
 
 Select the desired option and click 'Apply' to apply a filter to the search. To remove applied filters, click **Clear Filters > Apply**.
 
-<div class = "alert alert-info">
-By default, the <i class="fas fa-toggle-on"></i> <b>My time zone: GMT-3</b> option appears enabled for all filters. When disabled, the time zone reference changes to GMT-0 and, if re-enabled, becomes the time zone adopted by the user's browser.
-</div>
+>ℹ️ By default, the <i class="fas fa-toggle-on"></i> **My time zone: GMT-3** option appears enabled for all filters. When disabled, the time zone reference changes to GMT-0 and, if re-enabled, becomes the time zone adopted by the user's browser.
 
 If there is no match for the filter combination used in the search, the search won't provide any results.
 
@@ -199,9 +193,7 @@ On the **Orders > All Orders** page, there is the `Filter by Status` <i class="f
 
 When clicking `Filter by Status` <i class="fas fa-angle-down"></i>, your store's [order status](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196) options are displayed. For example, if among all your orders, there are no canceled ones, this option will not be visible. 
 
-<div class = "alert alert-info">
-For more status filter options, go to the section <a href="https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192#filters-status">Filters: Status</a>. If you want to check all existing order status, read the article <a href="https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196">Order flow and status</a>.
-</div>
+>ℹ️ For more status filter options, go to the section [Filters: Status](https://help.vtex.com/en/tutorial/filtrar-todos-pedidos--tutorials_192#filters-status). If you want to check all existing order status, read the article [Order flow and status](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
 
 ## Created
 
@@ -217,8 +209,6 @@ This filter has the **Today** date enabled by default, but by clicking it, the f
 * Current month
 * Last 30 days
 
-<div class = "alert alert-info">
-By default, the <i class="fas fa-toggle-on"></i> <b>My time zone: GMT-3</b> option is enabled. When disabled, the time zone reference changes to GMT-0 and, if re-enabled, becomes the time zone used in the user's browser.
-</div>
+>ℹ️ By default, the <i class="fas fa-toggle-on"></i> **My time zone: GMT-3** option is enabled. When disabled, the time zone reference changes to GMT-0 and, if re-enabled, becomes the time zone used in the user's browser.
 
 For more date and period filter options, visit the [Filters: Date](#filters-date) section. 
diff --git a/docs/tutorials/en/forcing-searches-with-blocked-terms-to-return-results.md b/docs/tutorials/en/forcing-searches-with-blocked-terms-to-return-results.md
index fcead55d8..a3d4cad0a 100644
--- a/docs/tutorials/en/forcing-searches-with-blocked-terms-to-return-results.md
+++ b/docs/tutorials/en/forcing-searches-with-blocked-terms-to-return-results.md
@@ -15,9 +15,7 @@ legacySlug: forcing-searches-with-blocked-terms-to-return-results
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 To make customer searches more accurate, VTEX search engine ignores some terms that are very common. Some examples are the words "com" and "todo", from Portuguese, "that" and "with", from English, and "hace" and "uno", from Spanish. [See here the complete list of blocked terms](/en/tutorial/why-vtex-search-engine-ignores-some-terms).
 
diff --git a/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
index 7f34eef22..e6117b2aa 100644
--- a/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/en/frequently-asked-questions-new-orders-module-interface.md
@@ -32,9 +32,7 @@ You can see the sections and fields correspondence between the old version of th
 
 The six-month filter is now replaced by an unlimited date search that returns all orders related to the criteria used, regardless of their creation date. You can, for example, view a customer's full purchase history using the customer's name, email, or document. Read the article [Filter orders on All Orders](https://help.vtex.com/en/tutorial/como-filtrar-pedidos--tutorials_192) to learn more. 
 
-<div class = "alert alert-info">
-The search in All Orders cannot be combined with other filters. So, once you remove the date limit from the search, any active filters become inactive. However, you can combine filters and select the custom period of six months, for example.
-</div>
+>ℹ️ The search in All Orders cannot be combined with other filters. So, once you remove the date limit from the search, any active filters become inactive. However, you can combine filters and select the custom period of six months, for example.
 
 Enter the desired term in the search bar to search all orders. This will make the <i class="fas fa-toggle-off"></i> `Remove date limit` option visible. Then, activate it to search.
 
diff --git a/docs/tutorials/en/fulfillment-logistics-vtex.md b/docs/tutorials/en/fulfillment-logistics-vtex.md
index e6a94b2b0..f9fbaf890 100644
--- a/docs/tutorials/en/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/en/fulfillment-logistics-vtex.md
@@ -19,11 +19,10 @@ Logistics or fulfillment is the process of planning and executing the transporta
 
 The VTEX platform allows you to register and control your inventory, manage shipping rates, control item availability, and track deliveries. 
 
-<div class = "alert alert-info">If you have not made the first steps in the <b>Shipping</b> module, check out this complementary content:
-The article <a href="https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a">Getting started with Logistics</a>. 
-Our <a href="https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby">Logistics Glossary</a>, in which you can find the definitions of logistics terms used at VTEX.
-The logistics settings available via <a href="https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview">API</a>. 
-</div>
+>ℹ️ If you have not made the first steps in the **Shipping** module, check out this complementary content:
+> The article [Getting started with Logistics](https://help.vtex.com/en/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a). 
+> Our [Logistics Glossary](https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby), in which you can find the definitions of logistics terms used at VTEX.
+> The logistics settings available via [API](https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview).
 
 To find out which logistics configurations are necessary and how to perform them, you must first understand the steps in the purchase flow of a product.
 
@@ -44,9 +43,7 @@ Once the order is placed, the [reservation of the products is authorized](https:
 
 8. After invoicing and shipping, the store is responsible for updating the inventory, which also means removing the items from inventory.
 
-<div class = "alert alert-info">
-Please note that the shipping process depends on the configuration made on the platform. Here, we present the scenarios for each type of shipping (delivery and pickup), but there are other possible flows in the shipping process. For example, when the customer chooses pickup and the selected pickup point is the warehouse, there is no need to transport the packages.
-</div>
+>ℹ️ Please note that the shipping process depends on the configuration made on the platform. Here, we present the scenarios for each type of shipping (delivery and pickup), but there are other possible flows in the shipping process. For example, when the customer chooses pickup and the selected pickup point is the warehouse, there is no need to transport the packages.
 
 ![Envio EN](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/2cf59529b64fd641f61b1afdb807d136/Envio_EN.svg)
 
diff --git a/docs/tutorials/en/generating-a-har-file.md b/docs/tutorials/en/generating-a-har-file.md
index ac1483932..1b76db8d7 100644
--- a/docs/tutorials/en/generating-a-har-file.md
+++ b/docs/tutorials/en/generating-a-har-file.md
@@ -21,13 +21,9 @@ A useful feature for this is the requests log generated by the browser's develop
 
 Through it you can generate a __HAR__ file, which contains detailed information about each request. Then just send it to our support team.
 
-<div class = "alert alert-warning">
-The HAR file contains sensitive information about your store. Share it only with VTEX support team.
-</div>
+>⚠️ The HAR file contains sensitive information about your store. Share it only with VTEX support team.
 
-<div class = "alert alert-warning">
-The step-by-step of how to generate a HAR file using <strong>Google Chrome</strong> is below. This is the most recommended way to proceed, but if you want to use other browsers, such as Mozilla Firefox or Microsoft Edge, be sure to check out the correct procedure <a href="[https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting">here</a>.
-</div>
+>⚠️ The step-by-step of how to generate a HAR file using **Google Chrome** is below. This is the most recommended way to proceed, but if you want to use other browsers, such as Mozilla Firefox or Microsoft Edge, be sure to check out the correct procedure [here]([https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting).
 
 ### Generating the HAR file in Google Chrome
 
diff --git a/docs/tutorials/en/gift-card.md b/docs/tutorials/en/gift-card.md
index c12510384..aa2d7d47c 100644
--- a/docs/tutorials/en/gift-card.md
+++ b/docs/tutorials/en/gift-card.md
@@ -32,9 +32,7 @@ To create a new gift card, follow the step by step:
   <br>
   <li>Click on the <b>New Gift Card</b> button.</li> 
   <br>
-  <div class = "alert alert-info">
-  <p>On the gift card creation screen, the <b>Gift card</b> field is automatically filled in by the VTEX system with the ID code of the new gift card. This is the code to be entered by the customer on the checkout screen to apply the gift card to the cart and reduce the payment value of the order.</p>
-</div>
+  >ℹ️ On the gift card creation screen, the **Gift card** field is automatically filled in by the VTEX system with the ID code of the new gift card. This is the code to be entered by the customer on the checkout screen to apply the gift card to the cart and reduce the payment value of the order.
 <br>
   <li>Fill in the fields that will be displayed as explained below:</li>
   <br>
diff --git a/docs/tutorials/en/google-analytics-faq.md b/docs/tutorials/en/google-analytics-faq.md
index 215b8c238..5d50c2a23 100644
--- a/docs/tutorials/en/google-analytics-faq.md
+++ b/docs/tutorials/en/google-analytics-faq.md
@@ -49,9 +49,7 @@ As VTEX is responsible for processing transactions from your store, all of them
 - Transaction tag triggers even with transactions that were not successfully completed.
 - Failed or duplicated display of the order confirmation page if the transaction tag is linked to the page display.
 
-<div class = "alert alert-info">
-Consider that there is also a delay of up to 48 hours in recording transaction data on Google Analytics.
-</div>
+>ℹ️ Consider that there is also a delay of up to 48 hours in recording transaction data on Google Analytics.
 
 Also, integrations can be built in such a way that they end up not triggering certain tags on your storefront. For example, there are integrations that use a [payment app](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-app) and complete the purchase without redirecting the customer to the order confirmation page, such as the integration developed by AME Digital. Transactions will always be recorded in VTEX, but in this case, it is likely that they are not recorded in Google Analytics, generating divergence.
 
diff --git a/docs/tutorials/en/google-pay-beta.md b/docs/tutorials/en/google-pay-beta.md
index e5b229f79..ffcfb9244 100644
--- a/docs/tutorials/en/google-pay-beta.md
+++ b/docs/tutorials/en/google-pay-beta.md
@@ -15,9 +15,7 @@ legacySlug: google-pay-beta
 subcategory: 3lZEaiSilZPwa3eCUUzwyr
 ---
 
-<div class = "alert alert-info">
-This module is in Beta, which means we are working on improving it. If you have any questions, please contact our <a href="https://help.vtex.com/en/support">Support team.</a>
-</div>
+>ℹ️ This module is in Beta, which means we are working on improving it. If you have any questions, please contact our [Support team.](https://help.vtex.com/en/support)
 
 Google Pay™ is a digital payments service that allows users not to share their actual card information with the store, providing more security and streamlining the checkout step. With Google Pay, users can make payments using credit or debit cards without having to enter any information manually, and Google Pay is also available in various apps, websites and in the Google Wallet. 
 
@@ -32,26 +30,20 @@ To enable Google Pay, follow the steps below.
 1. In the VTEX Admin, go to **Store Settings > Payments > Wallets** or type **Wallets** in the search bar at the top of the page.
 2. Select **Activate** to include the Google Pay extension.
 
-<div class = "alert alert-info">
-<p>The issuing banks supported by the Google Pay extension are the ones configured in the payment conditions.</p>
-</div>
+>ℹ️ The issuing banks supported by the Google Pay extension are the ones configured in the payment conditions.
 
 ![google pay - EN](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/c1848f1deba2af0d837f96f21eae86a5/image.png)
 
 Google Pay will then be available in your VTEX store's checkout as a new payment method. It may take around 10 minutes to be implemented.
 
-<div class = "alert alert-warning">
-<p>For now, Google Pay does not support subscriptions.</p>
-</div>
+>⚠️ For now, Google Pay does not support subscriptions.
 
 To use Google Pay, you must meet the following requirements:
 
 * Having at least one active [payment condition](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) configured for credit or debit cards with an [acquirer](https://help.vtex.com/en/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente), establishing which acquirer will process the wallet payment.
 * Using [VTEX Checkout](https://help.vtex.com/en/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) in your store.
 
-<div class = "alert alert-warning">
-<p>For stores that have the <a href="https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> authentication flow configured and supported by the acquirer, payment with Google Pay will follow the card native flow and will use 3DS as well. For more information on how to configure the authentication flow, please refer to <a href="https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Setting up 3DS 2 authentication flow</a>.</p>
-</div>
+>⚠️ For stores that have the [3DS](https://help.vtex.com/en/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) authentication flow configured and supported by the acquirer, payment with Google Pay will follow the card native flow and will use 3DS as well. For more information on how to configure the authentication flow, please refer to [Setting up 3DS 2 authentication flow](https://help.vtex.com/pt/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2).
 
 ## Viewing transactions completed with Google Pay
 
@@ -68,9 +60,7 @@ To add the information that the order was placed with a Google Pay card to the e
 
 After this change, whenever there is any mention of the last four digits of the card in these email templates, the "(Google Pay)" information will be added for payments made with a digital wallet.
 
-<div class = "alert alert-info">
-<p>For stores provisioned as of March 2023, the templates will already be updated with the information for payments made with Google Pay.</p>
-</div>
+>ℹ️ For stores provisioned as of March 2023, the templates will already be updated with the information for payments made with Google Pay.
 
 ## FAQ
 
diff --git a/docs/tutorials/en/how-does-reservation-work.md b/docs/tutorials/en/how-does-reservation-work.md
index 180e504e4..bf1a8f7f9 100644
--- a/docs/tutorials/en/how-does-reservation-work.md
+++ b/docs/tutorials/en/how-does-reservation-work.md
@@ -17,10 +17,8 @@ subcategory: 3PQwnyOcNyYgawy06oe6gE
 
 Reservation is a VTEX solution that prevents the same item from being sold more than once. After a purchase is completed, the purchased item is subtracted from the available inventory and its status is changed to **Reserved**.
 
-<div class = "alert alert-info">
-On the VTEX platform, warehouse refers to the physical location where items are stored. To identify at which warehouse items will be picked up by the carriers, you must add the warehouses to the platform. To learn more, please refer to the article <a href="https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb">Warehouses.</a>
-<p>Inventory is a list of the items your store has in stock. You can add and track the available items in your store on the Inventory management page. To learn more, please refer to the article <a href="https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139">Inventory management</a>.
-</div>
+>ℹ️ On the VTEX platform, warehouse refers to the physical location where items are stored. To identify at which warehouse items will be picked up by the carriers, you must add the warehouses to the platform. To learn more, please refer to the article [Warehouses.](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb)
+> <p>Inventory is a list of the items your store has in stock. You can add and track the available items in your store on the Inventory management page. To learn more, please refer to the article [Inventory management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139).
 
 After an item is sold, it goes through the following statuses in your store's inventory:
 
@@ -92,8 +90,6 @@ When the retailer or the ERP updates the quantity of that item in the inventory,
 
 As explained above, removal from inventory is a consequence of the retailer updating the inventory. Therefore, it is not possible to view this status on the platform. It is only possible to view the number of items available for sale and the movement of items in the [Inventory Management](https://help.vtex.com/en/tutorial/managing-stock-items--tutorials_139) page.
 
-<div class = "alert alert-info">
-All the statuses described here are internal and exclusive to VTEX for item sales control.
-<p>The reservation status is a consequence of the order status. Some changes depend on buyers' actions, and others depend on manual or ERP updates.
-</div>
+>ℹ️ All the statuses described here are internal and exclusive to VTEX for item sales control.
+> <p>The reservation status is a consequence of the order status. Some changes depend on buyers' actions, and others depend on manual or ERP updates.
 
diff --git a/docs/tutorials/en/how-does-vtex-search-work.md b/docs/tutorials/en/how-does-vtex-search-work.md
index 84ed0f6c5..b4813a74a 100644
--- a/docs/tutorials/en/how-does-vtex-search-work.md
+++ b/docs/tutorials/en/how-does-vtex-search-work.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 This article sets out to describe how VTEX's search system works.
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 ## VTEX search engine product display prioritization 
 
diff --git a/docs/tutorials/en/how-my-account-works.md b/docs/tutorials/en/how-my-account-works.md
index 027ca5d0c..e463dde1a 100644
--- a/docs/tutorials/en/how-my-account-works.md
+++ b/docs/tutorials/en/how-my-account-works.md
@@ -26,9 +26,7 @@ In [basic settings](#basic-settings), you can configure which sections will appe
 - [Subscriptions](#subscriptions)
 - [Authentication](#authentication)
 
-<div class = "alert alert-info">
-To learn about <b>My Account</b> customization, see our developer documentation <a href="https://developers.vtex.com/docs/guides/vtex-my-account">My Account - StoreV2 version</a>. Be aware that VTEX does not offer support for <b>My Account</b> when customized.
-</div>
+>ℹ️ To learn about **My Account** customization, see our developer documentation [My Account - StoreV2 version](https://developers.vtex.com/docs/guides/vtex-my-account). Be aware that VTEX does not offer support for **My Account** when customized.
 
 ## Profile
 
@@ -77,9 +75,7 @@ The `Add address` button allows customers to include new addresses besides the o
 
 ## Orders
 
-<div class = "alert alert-info">
-In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
-</div>
+>ℹ️ In [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), customers can only access their orders from the last two years.
 
 This section displays a list of all orders placed by the customer in your store. The list is sorted by creation date and displays details such as order date, total price of the order, order ID, status, and items purchased.
 
diff --git a/docs/tutorials/en/how-shipping-calculation-works.md b/docs/tutorials/en/how-shipping-calculation-works.md
index e824664b8..0b19a6d8a 100644
--- a/docs/tutorials/en/how-shipping-calculation-works.md
+++ b/docs/tutorials/en/how-shipping-calculation-works.md
@@ -17,9 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 During the shopping experience, when the customer enters their location at checkout, the VTEX platform analyzes the [shipping strategies](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) suitable for the order and displays the available shipping options to the customer.
 
-<div class = "alert alert-info">
-In the window display stage of the shopping flow, when the customer has not yet informed their address, the products displayed belong to the sellers already configured as <a href="https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">comprehensive sellers</a> or using the <a href="https://help.vtex.com/en/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc">Region</a> feature. These sellers are able to ship orders to all regions covered by the marketplace operation.
-</div>
+>ℹ️ In the window display stage of the shopping flow, when the customer has not yet informed their address, the products displayed belong to the sellers already configured as [comprehensive sellers](https://help.vtex.com/en/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI) or using the [Region](https://help.vtex.com/en/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc) feature. These sellers are able to ship orders to all regions covered by the marketplace operation.
 
 This article presents a general overview of the shipping calculation and is divided into the following sections:
 
@@ -34,9 +32,7 @@ To determine which combination of logistics steps configured by the store is the
 - **Delivery:** The customer receives the order at their address. 
 - **Pickup:** The customer picks up the order from a [pickup point](https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R).
 
-<div class = "alert alert-info">
-Both delivery and pickup have the same selection criteria. However, the pickup option has one additional criterion, described further on in this article.
-</div>
+>ℹ️ Both delivery and pickup have the same selection criteria. However, the pickup option has one additional criterion, described further on in this article.
 
 The selection of logistics combinations is made according to the criteria below, applied in the following order:
 
@@ -64,9 +60,7 @@ The selection of logistics combinations is made according to the criteria below,
   <li><a href="https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW#campos-de-cadastro">Priority loading docks</a></li>
 </ul>
 <br>
-  <div class = "alert alert-info">
-When there is a tie between loading docks, the tiebreak criterion is the <a href="https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">overhead</a>, which represents a value in number of days that will determine the most advantageous loading dock for a given shipment. The lower the overhead, the higher the chances for a loading dock to be selected. Please note that the overhead is not considered when calculating the shipping time.
-</div>
+  >ℹ️ When there is a tie between loading docks, the tiebreak criterion is the [overhead](https://help.vtex.com/en/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW), which represents a value in number of days that will determine the most advantageous loading dock for a given shipment. The lower the overhead, the higher the chances for a loading dock to be selected. Please note that the overhead is not considered when calculating the shipping time.
 
 5. **Exclusive criterion for the pickup option:** There is an additional step in the selection when analyzing [pickup points](https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R). The VTEX platform creates a list of eligible pickup points, using as criterion the shortest distance between the pickup point and the customer's location.
 
@@ -95,9 +89,7 @@ The SLA is calculated using the following fields and parameters:
 
 A shipping time estimate can be obtained using the [Shipping simulator](https://help.vtex.com/en/tutorial/simulador-de-envio--tutorials_144), which considers the VTEX store [shipping strategies](https://help.vtex.com/en/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3).
 
-<div class = "alert alert-info">
-The <a href="https://help.vtex.com/en/tutorial/simulador-de-envio--tutorials_144">Shipping simulator</a> result is only an approximation since the determining factors are only provided at checkout, such as carrier availability at the time of purchase, payment confirmation time and <a href="https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">white label sellers' selection</a> result.
-</div>
+>ℹ️ The [Shipping simulator](https://help.vtex.com/en/tutorial/simulador-de-envio--tutorials_144) result is only an approximation since the determining factors are only provided at checkout, such as carrier availability at the time of purchase, payment confirmation time and [white label sellers' selection](https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) result.
 
 ## Learn more	
 
diff --git a/docs/tutorials/en/how-subscriptions-work.md b/docs/tutorials/en/how-subscriptions-work.md
index dab08ea72..d1cfef358 100644
--- a/docs/tutorials/en/how-subscriptions-work.md
+++ b/docs/tutorials/en/how-subscriptions-work.md
@@ -45,9 +45,7 @@ To do that, go to the **My Account** page on your store's website, access the **
 
 ## How your customers view and manage their subscriptions
 
-<div class = "alert alert-info">
-In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
-</div>
+>ℹ️ In [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), customers can only access their orders from the last two years.
 
 A list of all the customer’s subscriptions, containing their details and statuses, will be displayed in the **Subscriptions** section, on the **My Account** page. Your customer will also receive a confirmation of the subscription and the generated order by email.  
 
diff --git a/docs/tutorials/en/how-the-order-replacement-works.md b/docs/tutorials/en/how-the-order-replacement-works.md
index 0c78d4615..3835b6451 100644
--- a/docs/tutorials/en/how-the-order-replacement-works.md
+++ b/docs/tutorials/en/how-the-order-replacement-works.md
@@ -71,6 +71,6 @@ When you select **Change order**, the customers are taken to a screen where they
 
 To complete the change, customers are taken to the cart and the Checkout, where they can alter address, freight, payment method and SKU.
 
-<div class = "alert alert-warning">The purchase must be closed for the process to be completed, but <em>customers are never charged twice</em>. In some cases the previous payment will be reused; when this is not possible, the previous charge on the credit card will automatically be reversed.</div>
+>⚠️ The purchase must be closed for the process to be completed, but *customers are never charged twice*. In some cases the previous payment will be reused; when this is not possible, the previous charge on the credit card will automatically be reversed.
 
 Payment reuse can only be applied if the value of the new order is the same as the original order. Also, if the payment expires within 2 days, it can not be reused.
diff --git a/docs/tutorials/en/how-to-change-order-items.md b/docs/tutorials/en/how-to-change-order-items.md
index e6b1ec456..2c775099c 100644
--- a/docs/tutorials/en/how-to-change-order-items.md
+++ b/docs/tutorials/en/how-to-change-order-items.md
@@ -26,10 +26,8 @@ There are two ways to make a change to an order:
 
 You can edit order items provided they have not been invoiced yet. To add or remove an item or change its number, please follow the step-by-step instructions below.
 
-<div class = "alert alert-info">
-To edit the order, its status must be <code> Handling shipping</code> which is equivalent to the <code>handling</code> status in the <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes">API</a>.  Read our article <a href="https://help.vtex.com/en/tutorial/order-status-table-oms--frequentlyAskedQuestions_773">Order status table </a>to learn more.
-Check the <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190#restrictions">Restrictions</a> section for the conditions for using the feature.
-</div>
+>ℹ️ To edit the order, its status must be ` Handling shipping` which is equivalent to the `handling` status in the [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes).  Read our article [Order status table ](https://help.vtex.com/en/tutorial/order-status-table-oms--frequentlyAskedQuestions_773)to learn more.
+> Check the [Restrictions](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190#restrictions) section for the conditions for using the feature.
 
 1. In the VTEX Admin, go to **Orders > All Orders**, or type **All Orders** in the search bar at the top of the page.    
 2. Search for the order by using the search bar [or the filters](https://help.vtex.com/en/tutorial/como-filtrar-pedidos--tutorials_192) and select the desired order.    
@@ -55,6 +53,4 @@ When [changing or removing items from an order](https://help.vtex.com/en/tutoria
 
 The order total will be updated once the invoice is added, corresponding to what is captured by the VTEX payment gateway. The VTEX Payments system will automatically refund the customer if an item is returned.
 
-<div class = "alert alert-info">
-The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Legacy connectors do not support the functionality.
-</div>
+>ℹ️ The partial invoices feature is available to all VTEX stores, but the partial settlement in the gateway is in beta. Besides, for partial invoices to trigger partial settlements in the transaction, it is necessary to use a connector with the [Payment Provider Protocol](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Legacy connectors do not support the functionality.
diff --git a/docs/tutorials/en/how-to-change-orders-beta.md b/docs/tutorials/en/how-to-change-orders-beta.md
index 75eab35b5..b3efa9e5d 100644
--- a/docs/tutorials/en/how-to-change-orders-beta.md
+++ b/docs/tutorials/en/how-to-change-orders-beta.md
@@ -77,9 +77,7 @@ On the order details page, you can do the following:
 - [Replace items](#replacing-items)
 - [Change weight](#changing-weight)
 
-<div class = "alert alert-info">
-You can make a single change to the order or combine several at once. There is no limit to how many times an order can be changed. Read the <a href="https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ">How Change order works (Beta)</a> article to learn more.
-</div>
+>ℹ️ You can make a single change to the order or combine several at once. There is no limit to how many times an order can be changed. Read the [How Change order works (Beta)](https://help.vtex.com/en/tutorial/how-change-order-works-beta--56TO0bOFXsfmpc7YZ3wIUZ) article to learn more.
 
 ### Adding items
 
diff --git a/docs/tutorials/en/how-to-configure-subscriptions.md b/docs/tutorials/en/how-to-configure-subscriptions.md
index 5854918e8..0fbbc234f 100644
--- a/docs/tutorials/en/how-to-configure-subscriptions.md
+++ b/docs/tutorials/en/how-to-configure-subscriptions.md
@@ -15,9 +15,7 @@ legacySlug: how-to-configure-subscription-v2
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
-<div class = "alert alert-info">
-To install the Subscriptions module, please contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.
-</div>
+>ℹ️ To install the Subscriptions module, please contact [our Support](https://support.vtex.com/hc/en-us/requests).
 
 The **Subscriptions** system is an app developed by VTEX to facilitate recurring sales. It works as an automatic scheduler, repeating orders according to the frequency chosen by your customer.
 
diff --git a/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md b/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md
index 84d62881c..e627b0a50 100644
--- a/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md
+++ b/docs/tutorials/en/how-to-configure-xml-for-google-shopping.md
@@ -15,13 +15,9 @@ legacySlug: how-to-configure-xml-for-google-shopping
 subcategory: 2OCA7SVfWoMSiAi0GEGwKo
 ---
 
-<div class = "alert alert-info">
-  <p>We have developed a new type of integration with Google Shopping via API, which allows real-time tracking. Learn more at <a href="https://help.vtex.com/en/tracks/integrating-with-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG">Integrating with Google Shopping</a>.</p>
-</div>
+>ℹ️ We have developed a new type of integration with Google Shopping via API, which allows real-time tracking. Learn more at [Integrating with Google Shopping](https://help.vtex.com/en/tracks/integrating-with-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG).
 
-<div class = "alert alert-warning">
-  <p>This article refers to the May 22, 2013 Google Shopping spec template. Google modifies and updates this template without previous warning. Always check if our explanation remains up-to-date according to the <a href="https://support.google.com/merchants/answer/188494?hl=en-US">Google Shopping documentation</a>.</p>
-</div>
+>⚠️ This article refers to the May 22, 2013 Google Shopping spec template. Google modifies and updates this template without previous warning. Always check if our explanation remains up-to-date according to the [Google Shopping documentation](https://support.google.com/merchants/answer/188494?hl=en-US).
 
 You can set up Google Shopping via VTEX Admin by following the steps below:
 
@@ -39,6 +35,4 @@ You can set up Google Shopping via VTEX Admin by following the steps below:
 
 ![](https://images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
 
-<div class = "alert alert-warning">
-  <p>If the option <strong>Show unavailable SKUs</strong> is unchecked, out-of-stock products or SKUs will not be shown in the XML. Inactive products also do not appear in the XML.</p>
-</div>
+>⚠️ If the option **Show unavailable SKUs** is unchecked, out-of-stock products or SKUs will not be shown in the XML. Inactive products also do not appear in the XML.
diff --git a/docs/tutorials/en/how-to-create-landing-pages-with-customized-urls.md b/docs/tutorials/en/how-to-create-landing-pages-with-customized-urls.md
index 9e1d0db5c..afac942af 100644
--- a/docs/tutorials/en/how-to-create-landing-pages-with-customized-urls.md
+++ b/docs/tutorials/en/how-to-create-landing-pages-with-customized-urls.md
@@ -15,9 +15,7 @@ legacySlug: how-does-the-search-context-work
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 Tutorial valid only for Legacy CMS Stores.
diff --git a/docs/tutorials/en/how-to-identify-an-order-split-from-omnichannel.md b/docs/tutorials/en/how-to-identify-an-order-split-from-omnichannel.md
index 30a2e10b9..509ccbb57 100644
--- a/docs/tutorials/en/how-to-identify-an-order-split-from-omnichannel.md
+++ b/docs/tutorials/en/how-to-identify-an-order-split-from-omnichannel.md
@@ -26,9 +26,7 @@ When the order is split, a suffix is added to the ID, such as `-01` or `-02`. Ea
 
 > For example: In the marketplace, an order's split ID could be `527103869572-01` or `v527103anml-01`.
 
-<div class = "alert alert-info">
-Orders placed on the marketplace will have an ID in the sellers' environment. Each seller has restricted access to its order section and no access to other sellers' orders.
-</div>
+>ℹ️ Orders placed on the marketplace will have an ID in the sellers' environment. Each seller has restricted access to its order section and no access to other sellers' orders.
 
 The order ID in the seller's environment is based on the same sequence used in the marketplace but has an additional prefix corresponding to the [affiliate ID](https://help.vtex.com/en/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0), composed of three consonants that identify the seller in the marketplace.
 
diff --git a/docs/tutorials/en/how-to-identify-order-closing-errors.md b/docs/tutorials/en/how-to-identify-order-closing-errors.md
index b87d8d05b..6ceba53ff 100644
--- a/docs/tutorials/en/how-to-identify-order-closing-errors.md
+++ b/docs/tutorials/en/how-to-identify-order-closing-errors.md
@@ -19,8 +19,6 @@ Whenever a user clicks on Complete Order, the checkout immediately creates an or
 
 And since every order has at least one transaction, it is also possible to find this transaction in **Orders > Transactions**. Since this is an error situation, the transaction will probably have been cancelled.
 
-<div class = "alert alert-info">
-We recommend that whenever there is an order error, the first place to look is the transaction log in <b>Orders > Transactions</b>. Learn more in <a href="https://help.vtex.com/en/tutorial/how-to-view-the-orders-details">Viewing the order's details in Orders</a>.
-</div>
+>ℹ️ We recommend that whenever there is an order error, the first place to look is the transaction log in **Orders > Transactions**. Learn more in [Viewing the order's details in Orders](https://help.vtex.com/en/tutorial/how-to-view-the-orders-details).
 
 The error message shown to the customer can be the result of different things. From internal errors, such as the failure to reserve an item, to problems with the card, such as incomplete data, or even a response from the gateway, with data input wrongly.
diff --git a/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
index 5af3d1c78..92ca12e96 100644
--- a/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/en/how-to-identify-promotions-applied-to-the-cart.md
@@ -46,9 +46,7 @@ However, if more than one promotion is applied, what appears will be the sum of
 
 ## orderForm
 
-<div class = "alert alert-warning">
-  <p>To conduct the investigation documented in this section, you must use Google Chrome. Because it is a tool external to VTEX, it can be updated without prior notice.</p>
-</div>
+>⚠️ To conduct the investigation documented in this section, you must use Google Chrome. Because it is a tool external to VTEX, it can be updated without prior notice.
 
 On the cart page, you can check the `orderForm`, which is a file in JSON format with all the information corresponding to the order being created.
 
diff --git a/docs/tutorials/en/how-to-integrate-with-facebook.md b/docs/tutorials/en/how-to-integrate-with-facebook.md
index d5426ee2d..12c77fca1 100644
--- a/docs/tutorials/en/how-to-integrate-with-facebook.md
+++ b/docs/tutorials/en/how-to-integrate-with-facebook.md
@@ -46,7 +46,7 @@ __Business manager Id__: Facebook __Business Manager__ account ID, which can be
 
 __Store site URL__: Fill in the address of your store. Example: `https://www.yourstore.com`. This field is used to form the complete URL of the product that is sent.
 
-<div class = "alert alert-info">All fields are required for full integration.</div>
+>ℹ️ All fields are required for full integration.
 
 ## Authorization
 
diff --git a/docs/tutorials/en/how-to-manage-subscriptions.md b/docs/tutorials/en/how-to-manage-subscriptions.md
index 00ef53cfe..5513f8a3f 100644
--- a/docs/tutorials/en/how-to-manage-subscriptions.md
+++ b/docs/tutorials/en/how-to-manage-subscriptions.md
@@ -39,9 +39,7 @@ The **Unique Subscriptions** section allows you to:
 
 ### Subscription Orders
 
-<div class = "alert alert-info">
-You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
-</div>
+>ℹ️ You can only access information from orders created in the last two years, and that same period is valid for customers through [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 The **Subscription Orders** section allows you to:
 
diff --git a/docs/tutorials/en/how-to-manually-invoice-an-order.md b/docs/tutorials/en/how-to-manually-invoice-an-order.md
index 00135b12e..f96fa1096 100644
--- a/docs/tutorials/en/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/en/how-to-manually-invoice-an-order.md
@@ -24,9 +24,7 @@ To invoice the order on the VTEX platform, you need to add the items' invoice to
 * Via [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice).
 * Via VTEX Admin.
 
-<div class = "alert alert-info">
-You can change the <a href="https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE">carrier</a> associated with the order when invoicing it. To do so, in the <b>Order Tracking</b> section, click <i>Carrier</i> and select the desired option.
-</div>
+>ℹ️ You can change the [carrier](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) associated with the order when invoicing it. To do so, in the **Order Tracking** section, click <i>Carrier</i> and select the desired option.
 
 To send the invoice via VTEX Admin, follow the steps below:
 
diff --git a/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
index 0c7abf0bd..8bc386974 100644
--- a/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/en/how-to-optimize-searches-with-substitute-words.md
@@ -15,8 +15,7 @@ legacySlug: how-to-optimize-searches-with-substitute-words
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-We don't recommend using <a href="https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu">Substitute Words</a> when using Intelligent Search. To associate words with products, we recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Synonyms</a>, which allows you to manage terms per product in a more scalable way. For more information, contact our <a href="https://support.vtex.com/hc/pt-br/requests">Support team</a>.</div>
+>⚠️ We don't recommend using [Substitute Words](https://help.vtex.com/en/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu) when using Intelligent Search. To associate words with products, we recommend using [Synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV), which allows you to manage terms per product in a more scalable way. For more information, contact our [Support team](https://support.vtex.com/hc/pt-br/requests).
 
 ## How the search engine works 
 VTEX has an intelligent algorithm that, based on the term searched for, identifies the best result for the user, i.e., it always shoes the result that will generate more conversions into sales.
diff --git a/docs/tutorials/en/how-to-return-order-items.md b/docs/tutorials/en/how-to-return-order-items.md
index 1f87cc4f8..f26c03b4b 100644
--- a/docs/tutorials/en/how-to-return-order-items.md
+++ b/docs/tutorials/en/how-to-return-order-items.md
@@ -38,6 +38,4 @@ On the Order Details page, you can orchestrate this operation by completing the
 
 After the refund is processed in the system, your returned items and information will be displayed in the **Returned items** section.
 
-<div class = "alert alert-info">
-You can change orders via API using the endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a>, and issue invoices after changes using the endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice">Order invoice notification</a>.
-</div>
+>ℹ️ You can change orders via API using the endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes), and issue invoices after changes using the endpoint [Order invoice notification](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice).
diff --git a/docs/tutorials/en/how-to-update-the-image-of-an-sku.md b/docs/tutorials/en/how-to-update-the-image-of-an-sku.md
index 87c0d86c7..51628b2ed 100644
--- a/docs/tutorials/en/how-to-update-the-image-of-an-sku.md
+++ b/docs/tutorials/en/how-to-update-the-image-of-an-sku.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 There are two ways to update SKU images: using the VTEX Admin or Catalog API.
 
-<div class = "alert alert-danger">
-You must perform this procedure very carefully. The procedure described below involves <em>deleting all images</em> of an SKU, which will make it <strong>INACTIVE</strong>. Please pay close attention to the recommendations in the steps below so that the image is successfully updated.
-</div>
+>❗ You must perform this procedure very carefully. The procedure described below involves *deleting all images* of an SKU, which will make it **INACTIVE**. Please pay close attention to the recommendations in the steps below so that the image is successfully updated.
 
 Since this procedure involves deleting all images from an SKU, consequently making it inactive, we recommend performing the image replacement process in small batches of SKUs.
 
@@ -33,9 +31,7 @@ Since this procedure involves deleting all images from an SKU, consequently maki
 4. Click on the __Images__ tab.
 5. Choose the images you want to delete and click __Remove__.
 
-<div class = "alert alert-danger">
-We recommend doing these image updates in small batches. Remember that deleting all images of an SKU inactivates it.
-</div>
+>❗ We recommend doing these image updates in small batches. Remember that deleting all images of an SKU inactivates it.
 
 ### Uploading new images
 
diff --git a/docs/tutorials/en/how-to-use-rebates.md b/docs/tutorials/en/how-to-use-rebates.md
index e6375c42a..7a704f150 100644
--- a/docs/tutorials/en/how-to-use-rebates.md
+++ b/docs/tutorials/en/how-to-use-rebates.md
@@ -25,9 +25,7 @@ Besides strengthening the relationship between suppliers and resellers, this sce
 
 The most suitable way to use rebates received from suppliers is through [Regular Promotions](https://help.vtex.com/en/tracks/promotions--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) with usage restrictions enforcement. Learn more about the Regular Promotions possibilities in our article [Promotion examples](https://help.vtex.com/en/tutorial/promotion-examples--5A8UTc7knvAscxo7e7rMFD).
 
-<div class = "alert alert-warning">
-  <p>The customer can eventually cancel the purchase of an order with a rebate discount. In this case, you have to redirect the discount to another client to reach the total number of credits. To check whether the rebate has been applied to an order, use the <a href = "https://developers.vtex.com/vtex-developer-docs/reference/user-orders#userorderslist">Retrieve User's orders</a> or <a href="https://developers.vtex.com/vtex-developer-docs/reference/orders#getorder">Get Order</a> endpoints from the Orders API.</p>
-</div>
+>⚠️ The customer can eventually cancel the purchase of an order with a rebate discount. In this case, you have to redirect the discount to another client to reach the total number of credits. To check whether the rebate has been applied to an order, use the <a href = "https://developers.vtex.com/vtex-developer-docs/reference/user-orders#userorderslist">Retrieve User's orders</a> or [Get Order](https://developers.vtex.com/vtex-developer-docs/reference/orders#getorder) endpoints from the Orders API.
 
 ## Example
 
diff --git a/docs/tutorials/en/i-cant-import-the-price-table.md b/docs/tutorials/en/i-cant-import-the-price-table.md
index c9cd01d54..b01bbc642 100644
--- a/docs/tutorials/en/i-cant-import-the-price-table.md
+++ b/docs/tutorials/en/i-cant-import-the-price-table.md
@@ -19,9 +19,7 @@ __Tags/Keywords__: *price table, spreadsheet import, cells.*
 
 [Price tables, or price spreadsheets](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8), store SKU information which, when applied in specific contexts, such as trade policies, promotions, or customer clusters, allows you to calculate the product prices in a VTEX store. For more information, see [Base price](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) and [Fixed price](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy). 
 
-<div class ="alert alert-warning">
-  You cannot import a <b>calculated price</b> table into the VTEX Admin. The <b>Export</b> function is available for this table only for the merchant to check the final price for each product.
-</div>
+>⚠️ You cannot import a **calculated price** table into the VTEX Admin. The **Export** function is available for this table only for the merchant to check the final price for each product.
 
 After [importing a price table](https://help.vtex.com/en/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D), error messages may display for certain SKUs, as shown in the examples below:
 
@@ -50,9 +48,7 @@ Make sure that all fields in your table are properly populated based on the guid
 - [Planilha de preço-base](https://help.vtex.com/en/tutorial/table-of-base-prices--4Jox8TeQ5feqAn78TZ0DNA)
 - [Planilha de preço fixo](https://help.vtex.com/en/tutorial/filling-out-an-import-spreadsheets-fixed-price-fields--50RFoH3ruV97FJgeBUCURh)
 
-<div class ="alert alert-warning">
-  Before importing the table into the VTEX Admin, make sure that it does not contain columns with error information (<b>Error Code</b> and <b>Error Message</b>) or any filters applied to the cells. Importing a table under these conditions may cause errors in the data import process.
-</div>
+>⚠️ Before importing the table into the VTEX Admin, make sure that it does not contain columns with error information (**Error Code** and **Error Message**) or any filters applied to the cells. Importing a table under these conditions may cause errors in the data import process.
 
 Example of a table with filters applied and __Error Code__ and __Error Message__ fields:
 
@@ -62,6 +58,4 @@ Example of a table with filters applied and __Error Code__ and __Error Message__
 
 Price tables should not exceed a maximum size limit of 1 megabyte (MB). If your current file is larger, divide the information into files smaller than 1 megabyte (MB).
 
-<div class ="alert alert-warning">
-  All data for a specific SKU must be in a single table. You cannot enter information for the same SKU in different tables.
-</div>
+>⚠️ All data for a specific SKU must be in a single table. You cannot enter information for the same SKU in different tables.
diff --git a/docs/tutorials/en/i-cant-receive-emails-from-vtex.md b/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
index 7075ac80d..a18192d42 100644
--- a/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
+++ b/docs/tutorials/en/i-cant-receive-emails-from-vtex.md
@@ -62,9 +62,7 @@ After the test, if the message from VTEX has not been sent to the email address
 
 Check if the external SMTP server is configured according to the [SPF system](https://help.vtex.com/en/tutorial/best-practices-on-spf--42t0lkl2VyC6Yewc4wA6wI), which prevents unauthorized servers from sending emails on behalf of a specific domain. You can configure [SPF](https://developers.vtex.com/docs/guides/setting-up-the-spf) and [DKIM](https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails) (DomainKeys Identified Mail) on the server if necessary.
 
-<div class ="alert alert-warning">
-Check your spam folder to ensure that VTEX emails are not being sent there. This may be due to internal mail server rules.
-</div>
+>⚠️ Check your spam folder to ensure that VTEX emails are not being sent there. This may be due to internal mail server rules.
 
 ### Configuring order and payment notifications
 
@@ -82,9 +80,7 @@ Amazon (AWS) has an email platform called Amazon Simple Email Service ([Amazon S
 
 Generally, an email can be added to the AWS suppression list and removed after approximately 12 hours. During this period, emails sent by VTEX will not be received by the email address added to the list.
 
-<div class ="alert alert-warning">
-AWS manages the suppression list, and VTEX has no control over the addresses on and off the list.
-</div>
+>⚠️ AWS manages the suppression list, and VTEX has no control over the addresses on and off the list.
 
 If you suspect AWS has blocked your email, wait 12 hours and try resending an email to the blocked address.
 
diff --git a/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
index f35c34c95..3e63bfc20 100644
--- a/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
+++ b/docs/tutorials/en/i-cant-view-the-product-in-the-search-results.md
@@ -47,9 +47,7 @@ A missing product in a search result may come from incomplete fields during the
 
 <blockquote><ui>1. In the Admin VTEX, go to </b>Catalog > All Products</b>.</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Stores using the <b>Produtos and SKUS (Beta)</b> page should check the product registration fields by going to <b>Catalog > Products and SKUs</b> in the VTEX Admin. Learn more about <a href="https://help.vtex.com/en/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">Produtos and SKUS (Beta)</a>.
-</div></blockquote>
+<blockquote><ui>>⚠️ Stores using the **Produtos and SKUS (Beta)** page should check the product registration fields by going to **Catalog > Products and SKUs** in the VTEX Admin. Learn more about [Produtos and SKUS (Beta)](https://help.vtex.com/en/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By).</blockquote>
 
 <blockquote><ui>2. Find the product you want and click <b>Edit product</b>.</ui>
 
@@ -63,9 +61,7 @@ A missing product in a search result may come from incomplete fields during the
 
 <blockquote><ui>7. Go to the store's website, search for the desired term, and ensure that the products displayed in the search results are the same as the ones available on the <b>Explained Search</b> page under Intelligent Search (<b>Storefront > Intelligent Search > Explained Search</b>).</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  If the search term is included in the product's name or description, but the product belongs to a different brand than the term specified in the search, proceed with the other steps to solve the problem.
-</div></blockquote>
+<blockquote><ui>>⚠️ If the search term is included in the product's name or description, but the product belongs to a different brand than the term specified in the search, proceed with the other steps to solve the problem.</blockquote>
 
 ### Changing search filters in Rewriter
 
@@ -123,9 +119,7 @@ internal {
 }
 ```
 
-<blockquote><ui><div class ="alert alert-warning">
-  The value <i>ft</i> (full text) instead of <i>b</i> (brand) in the <i>map</i> parameter indicates that products with the term <i>Pendleton</i> in the name or description will also be displayed in the search.
-</div></blockquote>
+<blockquote><ui>>⚠️ The value <i>ft</i> (full text) instead of <i>b</i> (brand) in the <i>map</i> parameter indicates that products with the term <i>Pendleton</i> in the name or description will also be displayed in the search.</blockquote>
 
 <blockquote><ui>7. Click the GraphiQL IDE arrow (next to <b>GraphiQL</b>) to update the search filter. The display of the following message in the GraphiQL IDE results field will confirm the new default search filter for the term.</ui>
 
@@ -154,9 +148,7 @@ internal {
 
 <blockquote><ui>8. Go to the store's website, search for the desired term, and ensure that the products displayed in the search results are the same as the ones available on the <b>Explained Search</b> page under Intelligent Search (<b>Storefront > Intelligent Search > Explained Search</b>).</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  If the search term is associated with a brand that no longer exists on your site, you will need to remove the internal search route within the Rewriter app, as described in the solution below</a>.
-</div></blockquote>
+<blockquote><ui>>⚠️ If the search term is associated with a brand that no longer exists on your site, you will need to remove the internal search route within the Rewriter app, as described in the solution below</a>.</blockquote>
 
 ### Removing internal search route in Rewriter
 
diff --git a/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md b/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md
index 444de1696..3dcee0707 100644
--- a/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md
+++ b/docs/tutorials/en/importing-and-exporting-an-inventory-spreadsheet.md
@@ -68,6 +68,4 @@ Check the meaning of each of the inventory spreadsheet fields.
 - **LockIds** (text): Booking identification code.  
 - **DispatchedReservations** (number): number of SKU items that have already moved beyond the `Item received for processing` status and whose booking is no longer valid. 
 - 
-<div class = "alert alert-info">
-  To include an item with infinite stock, you must fill in the <b>TotalQuantity</b> field with the value <code>1000000</code> and change the <b>UnlimitedQuantity</b> field to <code>True</code>.
-</div>
+>ℹ️ To include an item with infinite stock, you must fill in the **TotalQuantity** field with the value `1000000` and change the **UnlimitedQuantity** field to `True`.
diff --git a/docs/tutorials/en/integrating-with-mercado-livre.md b/docs/tutorials/en/integrating-with-mercado-livre.md
index 52bc8a18b..f411d836e 100644
--- a/docs/tutorials/en/integrating-with-mercado-livre.md
+++ b/docs/tutorials/en/integrating-with-mercado-livre.md
@@ -72,9 +72,7 @@ The initial steps are essential for a successful configuration:
 
 ### Sending Product Attributes to Mercado Livre
 
-<div class = "alert alert-danger">
-This step is only required for stores that sell products like <strong>clothing, shoes and bags</strong>. If your store has these types of product, it's necessary to register their specifications. Go to <a href="https://help.vtex.com/en/tutorial/sending-clothes-shoes-and-bags-attributes-to-mercado-livre">this article</a> to learn how to perform such registration. If your store does not have these products, go directly to the <strong>Template configuration</strong> step.
-</div>
+>❗ This step is only required for stores that sell products like **clothing, shoes and bags**. If your store has these types of product, it's necessary to register their specifications. Go to [this article](https://help.vtex.com/en/tutorial/sending-clothes-shoes-and-bags-attributes-to-mercado-livre) to learn how to perform such registration. If your store does not have these products, go directly to the **Template configuration** step.
 
 __You've finished configuring the *first step* of the integration. Now let's go to the __Template Configuration__ step.
 
diff --git a/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md b/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md
index ca2df66da..ee8b5b16c 100644
--- a/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md
+++ b/docs/tutorials/en/integration-guide-for-marketplaces-marketplace-non-vtex.md
@@ -55,9 +55,7 @@ In this article, you get an overview of the process of integrating both blocks,
 
 3) Marketplace searches for SKU price, inventory and shipping data using the Fulfillment API.  
 
-<div class = "alert alert-info">
-For more information, see the documentation for developers <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">External Marketplace</a>.
-</div>
+>ℹ️ For more information, see the documentation for developers [External Marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
 
 ## B) Flow referring to Order sending and processing
 
@@ -92,6 +90,4 @@ The integrations flow referring to the shipping and processing of orders can be
 5) Report carrier tracking.  
 6) Submit cancellation request.  
 
-<div class = "alert alert-info">
-For more information, see the documentation for developers <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">External Marketplace</a>.
-</div>
+>ℹ️ For more information, see the documentation for developers [External Marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
diff --git a/docs/tutorials/en/interaction-details.md b/docs/tutorials/en/interaction-details.md
index e73dce533..1bff9723f 100644
--- a/docs/tutorials/en/interaction-details.md
+++ b/docs/tutorials/en/interaction-details.md
@@ -32,9 +32,7 @@ On the **Interaction details** page, you will see the following sections:
 - [Interaction result](#interaction-result)      
 - [Timeline](#timeline)
 
-<div class = "alert alert-info">
-In <b>Offer Management</b> , you can track offers using <a href="https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> (Classic and Premium), <a href="https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> and VTEX marketplaces. For connectors to integrate via API, see <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Offer Management Integration Guide</a>.
-</div>
+>ℹ️ In **Offer Management** , you can track offers using [Mercado Libre](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic and Premium), [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) and VTEX marketplaces. For connectors to integrate via API, see [Offer Management Integration Guide](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Header
 ![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/d28534c5926b61794e3b16ac91636f86/Interaction_details_EN_cabe__alho.jpg)
diff --git a/docs/tutorials/en/inventory-update-history.md b/docs/tutorials/en/inventory-update-history.md
index 64d99e215..ef7981285 100644
--- a/docs/tutorials/en/inventory-update-history.md
+++ b/docs/tutorials/en/inventory-update-history.md
@@ -19,11 +19,10 @@ The inventory contains information about the products available in a store and i
 
 This article contains instructions for accessing the inventory update history in the VTEX Admin. 
 
-<div class = "alert alert-info">
-Don't forget the difference between warehouse and inventory:
-<p><b><a href="https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb">Warehouse:</b></a> Name given to the store's storage locations.</p>
-<p><b>Inventory:</b> List of SKUs and warehouses in which they are stored.</p>
-</div>
+>ℹ️ Don't forget the difference between warehouse and inventory:
+> **[Warehouse:**](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb) Name given to the store's storage locations.
+>
+> **Inventory:** List of SKUs and warehouses in which they are stored.
 
 To view the update history of a SKU, follow the steps below:
 
diff --git a/docs/tutorials/en/is-it-possible-to-use-the-vtex-admin-search-report.md b/docs/tutorials/en/is-it-possible-to-use-the-vtex-admin-search-report.md
index 0aeb9d03c..c62c7c400 100644
--- a/docs/tutorials/en/is-it-possible-to-use-the-vtex-admin-search-report.md
+++ b/docs/tutorials/en/is-it-possible-to-use-the-vtex-admin-search-report.md
@@ -15,9 +15,7 @@ legacySlug: is-it-possible-to-use-the-vtex-admin-search-report
 subcategory: 5yDQmr18K4GgQAeGwq8USa
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 The VTEX search report that could be accessed via __Reports > Search__ has been deprecated.
 
diff --git a/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
index 3e68138f7..fc0c6aa88 100644
--- a/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
+++ b/docs/tutorials/en/lead-time-shipping-time-at-sku-level.md
@@ -27,9 +27,7 @@ This article covers the following:
 - [Configuring lead time:](#configuring-lead-time) How to configure lead time through the VTEX Admin.
 - [Configuring lead time calculation in calendar days:](#configuring-lead-time-calculation-in-calendar-days-optional) Optional step for the lead time calculation to be in calendar days, not business days (default).
 
-<div class = "alert alert-info">
-To configure lead time via API, see <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>ℹ️ To configure lead time via API, see [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## Total shipping time
 
@@ -83,9 +81,7 @@ To configure the lead time for a SKU, follow the steps below:
   ![lead_time_inventory_management_EN](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/34a3c9f845038312b1b3cdb273102562/lead_time_inventory_management_EN.png)
 4. Click `Save` at the bottom of the page.
 
-<div class = "alert alert-info">
-In the VTEX Admin, lead time is always configured in days, but you can configure it in hours, minutes, and seconds using the Update inventory by SKU and warehouse endpoint.
-</div>
+>ℹ️ In the VTEX Admin, lead time is always configured in days, but you can configure it in hours, minutes, and seconds using the Update inventory by SKU and warehouse endpoint.
 
 ## Configuring lead time calculation in calendar days (optional)
 
diff --git a/docs/tutorials/en/license-manager-resources.md b/docs/tutorials/en/license-manager-resources.md
index 2be79704c..154097500 100644
--- a/docs/tutorials/en/license-manager-resources.md
+++ b/docs/tutorials/en/license-manager-resources.md
@@ -24,9 +24,7 @@ Therefore, the VTEX platform offers you the possibility to create custom access
 
 <iframe src="https://help.vtex.com/tables/resources/en" title="License Manager resources" frameBorder="0" width="100%" height="850"></iframe>
 
-<div class = "alert alert-info">
-  <p>In the <a href="https://help.vtex.com/en/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a> application, License Manager resources are identified by the corresponding keys.</p>
-</div>
+>ℹ️ In the [Audit](https://help.vtex.com/en/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA) application, License Manager resources are identified by the corresponding keys.
 
 ## Internal or deprecated resources
 
diff --git a/docs/tutorials/en/loading-dock.md b/docs/tutorials/en/loading-dock.md
index fd04d290b..3c9aad2d9 100644
--- a/docs/tutorials/en/loading-dock.md
+++ b/docs/tutorials/en/loading-dock.md
@@ -22,16 +22,14 @@ On VTEX, the loading dock is an intermediary between storing items and deliverin
 
 ![Doca EN](https://images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/0e98be333d982b352836b24b72f65997/Doca_EN.svg)
 
-<div class = "alert alert-info">
-The Warehouse is the physical storage for the goods sold by the store; the Trade policy is the configuration of the store's sales strategies; and the Shipping policy is a set of rules that define the shipping options and conditions.
-For the logistics system to work as expected, we suggest that you configure it in the following order:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV">Trade policy</a>;</li>
-<li><a href="https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140">Shipping policy</a>;</li>
-<li>Loading dock;</li>
-<li><a href="https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb">Warehouse</a>.</li>
-</div>
+>ℹ️ The Warehouse is the physical storage for the goods sold by the store; the Trade policy is the configuration of the store's sales strategies; and the Shipping policy is a set of rules that define the shipping options and conditions.
+> For the logistics system to work as expected, we suggest that you configure it in the following order:
+> <body>
+> <ol>
+> <li>[Trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV);</li>
+> <li>[Shipping policy](https://help.vtex.com/en/tutorial/politica-de-envio--tutorials_140);</li>
+> <li>Loading dock;</li>
+> <li>[Warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb).</li>
 
 ## Use cases
 
diff --git a/docs/tutorials/en/making-product-collections-searchable.md b/docs/tutorials/en/making-product-collections-searchable.md
index 5683ac8b7..ebc5727be 100644
--- a/docs/tutorials/en/making-product-collections-searchable.md
+++ b/docs/tutorials/en/making-product-collections-searchable.md
@@ -15,9 +15,7 @@ legacySlug: tornar-colecao-de-produtos-encontravel-pela-busca
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 You can make it possible for the user to find products associated with a specific collection when searching for it by name on the store's page.
 
diff --git a/docs/tutorials/en/managing-delivery-capacity.md b/docs/tutorials/en/managing-delivery-capacity.md
index 7bd93b2e8..9c0f95b0a 100644
--- a/docs/tutorials/en/managing-delivery-capacity.md
+++ b/docs/tutorials/en/managing-delivery-capacity.md
@@ -34,6 +34,4 @@ Once you have selected a shipping policy and a date, you will see the delivery w
 *   **Available**: number of items/orders that can still be scheduled (the total capacity minus the booked items).
 *   **Status**: classified as visible or not visible, depending on the availability of the delivery window. The delivery window will be shown as visible for your customers if its capacity hasn’t been reached yet.
 
-<div class = "alert alert-info">
-By clicking on <b>EDIT SHIPPING POLICY</b>, you’ll be redirected to the shipping policy page selected in the Shipping policy filter, where you can edit it.
-</div>
+>ℹ️ By clicking on **EDIT SHIPPING POLICY**, you’ll be redirected to the shipping policy page selected in the Shipping policy filter, where you can edit it.
diff --git a/docs/tutorials/en/managing-http-headers.md b/docs/tutorials/en/managing-http-headers.md
index 8601653b7..a2e69d311 100644
--- a/docs/tutorials/en/managing-http-headers.md
+++ b/docs/tutorials/en/managing-http-headers.md
@@ -22,9 +22,7 @@ Headers play a crucial role in HTTP communication, providing additional informat
 - __Request Headers:__ Sent by the client to the server. They contain information about the request made, such as the type of HTTP method used, the type of accepted content, cookies, among others.
 - __Response Headers:__ Sent by the server to the client. They provide information about the sent response, such as the response status, type of returned content, cookies, among others.
 
-<div class = "alert alert-info">
-For more information, refer to the <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP">MDN’s HTTP</a> guide and related documentation.
-</div>
+>ℹ️ For more information, refer to the [MDN’s HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP) guide and related documentation.
 
 In this guide, you will learn how to manage Security Response Headers in your Store Framework store.
 ## Security Response Headers
diff --git a/docs/tutorials/en/managing-shipping-policies.md b/docs/tutorials/en/managing-shipping-policies.md
index ee35cf66f..a9c1a8dc4 100644
--- a/docs/tutorials/en/managing-shipping-policies.md
+++ b/docs/tutorials/en/managing-shipping-policies.md
@@ -52,9 +52,7 @@ The information displayed on this page is described in the table below:
 
 In the search box with the magnifying glass icon <i class="fas fa-search"></i>, you can search for shipping policies by name. Typing a character into the search bar immediately initiates the search. To clear the search, click the close icon <i class="far fa-times-circle"></i>.
 
-<div class = "alert alert-info">
-If the search does not return any results, check the spelling used in the search and if a filter has been selected.
-</div>
+>ℹ️ If the search does not return any results, check the spelling used in the search and if a filter has been selected.
 
 ## Filtering shipping policies
 
diff --git a/docs/tutorials/en/managing-stock-items.md b/docs/tutorials/en/managing-stock-items.md
index 293851ca1..36e5528e0 100644
--- a/docs/tutorials/en/managing-stock-items.md
+++ b/docs/tutorials/en/managing-stock-items.md
@@ -39,7 +39,7 @@ In the VTEX Admin, go to **Catalog > Inventory > Inventory Management**, or type
     * **Products:** the name of the product.
     * **Warehouse**: to which warehouse the SKU belongs to.
     * **SKU ID:** the identifier code for the SKU.
-    * **Last Update**: most recent quantity of SKU units registered on the VTEX platform.<p><div class = "alert alert-info">If you click any number in the <b>Last Update</b> column, the <a href="https://help.vtex.com/en/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2">Update Logs</a> window will open with the changes registers. Each row corresponds to an update with the user who made the change, the date and the inventory quantity before an and after the update. You can only see the last 50 updates of a SKU.</div></p>
+    * **Last Update**: most recent quantity of SKU units registered on the VTEX platform.<p>>ℹ️ If you click any number in the **Last Update** column, the [Update Logs](https://help.vtex.com/en/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2) window will open with the changes registers. Each row corresponds to an update with the user who made the change, the date and the inventory quantity before an and after the update. You can only see the last 50 updates of a SKU.</p>
     * **Reserved:** reserved SKU units. Orders for these reservations have not yet been approved for payment.
     By clicking on the values in this column to see details about the SKU reservation data, you are redirected to the Order management page. To learn more about how to view a reservation, please refer to [How to track reservation status](https://help.vtex.com/en/tutorial/how-does-reservation-work--tutorials_92#como-acompanhar-o-status-da-reserva)
     * **Fulfilled:** shipped units of that SKU. The items in this column are from orders with `Payment approved`, `Preparing for delivery` or `Invoiced` status. <p>By clicking on the items to view details of shipped SKUs, you will be redirected to the Order management page.</p>
diff --git a/docs/tutorials/en/master-data.md b/docs/tutorials/en/master-data.md
index d4df71a3e..08bf93fa5 100644
--- a/docs/tutorials/en/master-data.md
+++ b/docs/tutorials/en/master-data.md
@@ -27,9 +27,7 @@ In this article you will learn more about each available version of the Master D
 
 Currently there are two versions available and you can choose the one that best suits your operational needs. The main difference between the two is that v2 does not have a graphical interface and can be used only through [Master Data v2 API](https://developers.vtex.com/docs/api-reference/master-data-api-v2), although it has other relevant functionalities, such as the use of [JSON schemas](https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema).
 
-<div class = "alert alert-info">
-Note that the VTEX platform natively saves customer data from your store in Master Data v1.
-</div>
+>ℹ️ Note that the VTEX platform natively saves customer data from your store in Master Data v1.
 
 Check the table below to learn more about the different functionalities of each version.
 
@@ -270,9 +268,7 @@ As mentioned above, each document has an ID automatically generated by the platf
 
 For example, you can query a document with a client's information by specifying the value of the 'email' field for the client.
 
-<div class = "alert alert-info">
-Learn more about <a href=https://help.vtex.com/en/tutorial/setting-up-an-index-on-master-data--tutorials_785>setting up indexes in Master Data v1</a> or <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>setting up indexes with Master Data v2 API</a>.
-</div>
+>ℹ️ Learn more about <a href=https://help.vtex.com/en/tutorial/setting-up-an-index-on-master-data--tutorials_785>setting up indexes in Master Data v1</a> or <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>setting up indexes with Master Data v2 API</a>.
 
 ## Triggers
 
@@ -287,17 +283,13 @@ Learn more about how [to configure triggers in Master Data v1](https://help.vtex
 
 With Master Data v2, you can define data formats with JSON schemas. This format indicates how the Master Data should validate and index documents.
 
-<div class = "alert alert-info">
-Learn more about <a href=https://json-schema.org/>JSON schemas</a>.
-</div>
+>ℹ️ Learn more about <a href=https://json-schema.org/>JSON schemas</a>.
 
 You can save a document to any data entity if the content is a valid JSON. A data entity may or may not have multiple JSON schemas associated with it.
 
 ![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/72f691a72fe0166b1e16a38c6bf89d11/schemas_en.jpg)
 
-<div class = "alert alert-info">
-A document can be compatible with multiple JSON Schemas, but also with none.
-</div>
+>ℹ️ A document can be compatible with multiple JSON Schemas, but also with none.
 
 ## Applications
 
diff --git a/docs/tutorials/en/my-store-order-was-not-created.md b/docs/tutorials/en/my-store-order-was-not-created.md
index 23a7ab959..e8ad4f6d1 100644
--- a/docs/tutorials/en/my-store-order-was-not-created.md
+++ b/docs/tutorials/en/my-store-order-was-not-created.md
@@ -43,9 +43,7 @@ The following solutions focus on inventory management via VTEX Admin:
 * **Update inventory count:** In the line that corresponds to the desired SKU and warehouse, on the _Update Count_ column, type the number of items available for sales, and click `Save`. This number cannot be negative, otherwise you will have a [negative inventory](https://help.vtex.com/en/faq/why-is-my-stock-negative--frequentlyAskedQuestions_159).
 * **Configure Infinite Inventory:** In the line that corresponds to the desired SKU and warehouse, on the _Infinite Inventory_ column, turn on the switch, and click `Save`. When this configuration is activated, the item is considered always available for sales and the store never runs _out-of-stock_ for it.
 
-<div class = "alert alert-info">
-To configure <i>out-of-stock</i> products to be displayed in your storefront, in your VTEX Admin access <b>Catalog > All Products</b>, and in the product configuration page, in the <b>Product</b> tab, select the checkbox <b>Yes</b> for <i>Show when out of stock</i>.
-</div>
+>ℹ️ To configure <i>out-of-stock</i> products to be displayed in your storefront, in your VTEX Admin access **Catalog > All Products**, and in the product configuration page, in the **Product** tab, select the checkbox **Yes** for <i>Show when out of stock</i>.
 
 ### Review XML integration
 
diff --git a/docs/tutorials/en/offer-details.md b/docs/tutorials/en/offer-details.md
index fed484e45..69ccd818c 100644
--- a/docs/tutorials/en/offer-details.md
+++ b/docs/tutorials/en/offer-details.md
@@ -33,9 +33,7 @@ The **Offer details** page contains the following sections:
 - [Offer status](#offer-status)  
 - [List of interactions](#list-of-interactions) 
 
-<div class = "alert alert-info">
-In <b>Offer Management</b> , you can track offers using <a href="https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> (Classic and Premium), <a href="https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> and VTEX marketplaces. For connectors to integrate via API, see <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Offer Management Integration Guide</a>.
-</div>
+>ℹ️ In **Offer Management** , you can track offers using [Mercado Libre](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic and Premium), [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) and VTEX marketplaces. For connectors to integrate via API, see [Offer Management Integration Guide](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Header
 
diff --git a/docs/tutorials/en/offer-management.md b/docs/tutorials/en/offer-management.md
index 722b957fc..5891e2c25 100644
--- a/docs/tutorials/en/offer-management.md
+++ b/docs/tutorials/en/offer-management.md
@@ -97,9 +97,7 @@ You can click on a column name to sort the offers in ascending or descending ord
 
 To export the offer list in XLSX format, click the <i class="fa-solid fa-arrow-down-to-line"></i> down arrow icon at the top of the interface. The file will be sent to the email of the logged-in user. The export time depends on the volume of offers exported and on the processing circumstances of the VTEX platform.
 
-<div class = "alert alert-info">
-The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
-</div>
+>ℹ️ The exported content refers to all items in the offer list at the moment of exporting. If any of the filters are active, only the selected offers will be exported.
 
 ## Consulting discarded offers
 
diff --git a/docs/tutorials/en/oms-page-structure.md b/docs/tutorials/en/oms-page-structure.md
index 0ca4bf129..7292d2918 100644
--- a/docs/tutorials/en/oms-page-structure.md
+++ b/docs/tutorials/en/oms-page-structure.md
@@ -15,9 +15,7 @@ legacySlug: oms-page-structure
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class = "alert alert-info">
-For documentation on the new Order Management System (OMS) interface, see <a href="https://help.vtex.com/en/tutorial/order-list-beta--2QTduKHAJMFIZ3BAsi6Pi">Order List (Beta)</a>.
-</div>
+>ℹ️ For documentation on the new Order Management System (OMS) interface, see [Order List (Beta)](https://help.vtex.com/en/tutorial/order-list-beta--2QTduKHAJMFIZ3BAsi6Pi).
 
 To better understand the __Orders Management__, see the descriptive of each area of the module responsible for the display and management of your store's orders.
 
@@ -33,9 +31,7 @@ The bar doesn't show the exact position of the stores that are in the top 5 posi
 
 For all the data of order variations, and also for the numbers of evolution in the ranking, the green color indicates a positive result; blue, neutral; and red, negative.
 
-<div class = "alert alert-warning">
-Important: If the order comparison is done based on 0 orders in the past, the variation is 0%.
-</div>
+>⚠️ Important: If the order comparison is done based on 0 orders in the past, the variation is 0%.
 
 ![barra-status-oms en](https://images.ctfassets.net/alneenqid6w5/3B36BC5ZO8q66GYEOoeOK4/051f7dea8deea96f4bdc321251cfca31/status_bar_en.png)
 
diff --git a/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
index ceaa39883..6e8de70ce 100644
--- a/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/en/opening-tickets-to-vtex-support-finacial.md
@@ -57,17 +57,11 @@ This classification is important for the support team to prioritize the most urg
 
 *If the indicated level does not apply to the scenario, the agent can modify it.*
 
-<div class = "alert alert-info">
-<strong>Normal:</strong> general questions.
-</div>
+>ℹ️ **Normal:** general questions.
 
-<div class = "alert alert-warning">
-<strong>High:</strong> important documentation is making the process unfeasible.
-</div>
+>⚠️ **High:** important documentation is making the process unfeasible.
 
-<div class = "alert alert-danger">
-<strong>Urgent:</strong> Admin blocked, threatening the profit of their business.
-</div>
+>❗ **Urgent:** Admin blocked, threatening the profit of their business.
 
 ## Interacting with the support
 
diff --git a/docs/tutorials/en/operational-capacity-beta.md b/docs/tutorials/en/operational-capacity-beta.md
index 0c81c2432..cd07958be 100644
--- a/docs/tutorials/en/operational-capacity-beta.md
+++ b/docs/tutorials/en/operational-capacity-beta.md
@@ -15,9 +15,7 @@ legacySlug: locations-module
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class = "alert alert-info">
-This feature is in beta, which means that we are working to improve it. To use <b>Operational Capability (Beta)</b>, fill out the <a href="https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform">contact form</a>. To use the feature, it is required to have <a href="https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl">franchise accounts</a> associated with the <a href="https://help.vtex.com/en/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#vtex-account-types">main account</a>.
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. To use **Operational Capability (Beta)**, fill out the [contact form](https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform). To use the feature, it is required to have [franchise accounts](https://help.vtex.com/en/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) associated with the [main account](https://help.vtex.com/en/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#vtex-account-types).
 
 The **Operational Capacity** page allows you to manage the sellers' capacity to receive and handle the store's orders to optimize your logistics network. You can monitor the order allocation between sellers and perform [actions](#acoes-na-pagina-de-detalhes-do-seller) to improve order allocation between them.
 
@@ -63,9 +61,7 @@ In the VTEX Admin, under **Shipping > Operational Capacity**, you can do the fol
 
 Using the search bar, you can search for sellers by their name.
 
-<div class = "alert alert-info">
-You can associate the search for sellers with the <a href="https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtering-sellers">filter by status</a>. If your search did not return any results, make sure no filters are active.
-</div>
+>ℹ️ You can associate the search for sellers with the [filter by status](https://help.vtex.com/en/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtering-sellers). If your search did not return any results, make sure no filters are active.
 
 ### Filtering sellers
 
diff --git a/docs/tutorials/en/order-allocation-algorithm-beta.md b/docs/tutorials/en/order-allocation-algorithm-beta.md
index 2b34fa44e..49ab58baf 100644
--- a/docs/tutorials/en/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/en/order-allocation-algorithm-beta.md
@@ -31,9 +31,7 @@ The **Order Allocation Algorithm** works differently for pickup and delivery shi
 | 6. For each applicable shipping option, the algorithm calculates the rate that will be displayed to the consumer at checkout according to the pricing rule set in the shipping option. | 6. The algorithm calculates the rate that will be displayed to the consumer at checkout, according to the pricing rule configured in the shipping option. |
 | 7. At checkout, the shipping options selected are displayed to the consumer, with the estimated time and delivery cost. | 7. At checkout, all the pickup points that cover the items in the cart are displayed to the consumer. |
 
-<div class = "alert alert-info">
-The priority criterion of the <a href="https://help.vtex.com/en/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">current algorithm</a> is to find the lowest package split of the order. The <b>Order Allocation Algorithm</b> main criterion is to seek the lowest shipping cost for the retailer.
-</div>
+>ℹ️ The priority criterion of the [current algorithm](https://help.vtex.com/en/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) is to find the lowest package split of the order. The **Order Allocation Algorithm** main criterion is to seek the lowest shipping cost for the retailer.
 
 The next sections give details on how the algorithm works and are divided in:
 
@@ -74,8 +72,6 @@ When analyzing fulfillment point combinations, the algorithm considers:
 
 Through the shipping policy, the **Order Allocation Algorithm** simulates the combinations of fulfillment points seeking to meet the order at the lowest cost to the retailer. The process is done by querying the [shipping rate template](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127) and analyzing the [carrier](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) costs.
 
-<div class = "alert alert-info">
-In the <a href="https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">current algorithm</a>, the retailer often sets up the <a href="https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127">shipping rate template</a> with the values they want to display to the customer at checkout rather than the real carrier cost. With the Order Allocation Algorithm, the retailer does not need to consider how the cost in the shipping rate template reflects on the shopping experience, as the <a href="https://help.vtex.com/en/tutorial/shipping-options-beta--7gsdck3519Z3VPqzwFFHJL">shipping option</a> configuration determines it. In addition, the Order Allocation Algorithm becomes more accurate by referencing the real carrier cost.
-</div>
+>ℹ️ In the [current algorithm](https://help.vtex.com/en/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa), the retailer often sets up the [shipping rate template](https://help.vtex.com/en/tutorial/planilha-de-frete--tutorials_127) with the values they want to display to the customer at checkout rather than the real carrier cost. With the Order Allocation Algorithm, the retailer does not need to consider how the cost in the shipping rate template reflects on the shopping experience, as the [shipping option](https://help.vtex.com/en/tutorial/shipping-options-beta--7gsdck3519Z3VPqzwFFHJL) configuration determines it. In addition, the Order Allocation Algorithm becomes more accurate by referencing the real carrier cost.
 
 After analyzing the possible simulations, the **Order Allocation Algorithm** determines for each shipping option possible fulfillment point combinations. At checkout, the customer gets all the shipping options with at least one valid combination of fulfillment points available for the order.
diff --git a/docs/tutorials/en/order-cancellation-requested-by-the-customer.md b/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
index b11f1506b..2c267e22f 100644
--- a/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/en/order-cancellation-requested-by-the-customer.md
@@ -19,9 +19,7 @@ Customers may request to cancel their order for various reasons. They can [cance
 
 >❗ Once an order is canceled, it is no longer possible to change its status.
 
-<div class = "alert alert-warning">
-Orders with <a href="https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">partial invoices</a> cannot be <a href="https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186">canceled</a>. If the customer wants to replace or remove items from the order, it is possible to <a href="https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">change the order</a>.
-</div>
+>⚠️ Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Cancellation within the grace period
 
@@ -29,9 +27,7 @@ When the customer requests to cancel an order during the [grace period](https://
 
 * Customers must request the cancellation in __My Orders__, by clicking `Request order cancellation`.
 
-<div class = "alert alert-info">
-When the customer requests the order's cancellation within the grace period, the notification of this action is sent only to the <a href="https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">Sponsor user</a> (admin master) of the account.
-</div>
+>ℹ️ When the customer requests the order's cancellation within the grace period, the notification of this action is sent only to the [Sponsor user](https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) (admin master) of the account.
 
 ## Cancellation approved by the retailer
 
diff --git a/docs/tutorials/en/order-details-page.md b/docs/tutorials/en/order-details-page.md
index 7acc134da..c03a58eaf 100644
--- a/docs/tutorials/en/order-details-page.md
+++ b/docs/tutorials/en/order-details-page.md
@@ -15,9 +15,7 @@ legacySlug: order-details-page-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-<div class = "alert alert-info">
-You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
-</div>
+>ℹ️ You can only access information from orders created in the last two years, and that same period is valid for customers through [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 The order details page allows you to view all the information of an order and manage it in a single place. To access it, in the VTEX Admin, go to **Orders > [All orders](https://help.vtex.com/en/tutorial/lista-de-pedidos-beta--2QTduKHAJMFIZ3BAsi6Pi)**, and click the desired order.
 
@@ -44,9 +42,7 @@ The order details page is divided into blocks that group information or features
 
 To learn more about order flow and status, please check out the article [Order flow and status](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
 
-<div class = "alert alert-info">
-You will find below a list of all possible sections for the <b>Order details page</b>, but please note that only the sections that apply to the order in question will be visible.
-</div>
+>ℹ️ You will find below a list of all possible sections for the **Order details page**, but please note that only the sections that apply to the order in question will be visible.
 
 ## Top bar
 
@@ -76,9 +72,7 @@ General order information is displayed at the top of the page, just below the to
   - Contact details (mobile number and email)  
 * **Delivery/Pickup:** address details and recipient name for shipping by carrier or for pickup by customer.  
 
-<div class = "alert alert-info">
-Click on the <i class="fas fa-chevron-right"></i> icon to enlarge the block.
-</div>
+>ℹ️ Click on the <i class="fas fa-chevron-right"></i> icon to enlarge the block.
 
 ### Order status
 
diff --git a/docs/tutorials/en/order-flow-and-status.md b/docs/tutorials/en/order-flow-and-status.md
index 7349130b7..bd852146f 100644
--- a/docs/tutorials/en/order-flow-and-status.md
+++ b/docs/tutorials/en/order-flow-and-status.md
@@ -22,9 +22,7 @@ This article will present the following information:
 - A [table with all the order statuses available on the Admin and via API](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#order-status-details).
 - [Scenarios in which orders are canceled](https://help.vtex.com/en/tutorial/fluxo-e-status-de-pedidos--tutorials_196#order-cancellation).
 
-<div class = "alert alert-info">
-Learn how to track an order flow in the article <a href="https://help.vtex.com/en/tutorial/acompanhamento-de-pedidos--et0Ei7F3bjcrEmVAR2kKS">Order tracking</a>.
-</div>
+>ℹ️ Learn how to track an order flow in the article [Order tracking](https://help.vtex.com/en/tutorial/acompanhamento-de-pedidos--et0Ei7F3bjcrEmVAR2kKS).
 
 ## Flow types
 
@@ -67,9 +65,7 @@ This is the order flow visible to the store responsible for shipping the order p
 
 3. The status automatically changes to `Cancellation window`. The order will remain at this status until the [cancellation window is closed](https://help.vtex.com/en/tutorial/configuracoes-gerais/#orders).
 
-  <div class = "alert alert-info">
-The <i>Cancellation window</i> allows the customer to cancel the purchase without the store's approval, within a period of time previously configured by the store. After this period, the store must authorize the customer's cancellation request.
-</div>
+  >ℹ️ The <i>Cancellation window</i> allows the customer to cancel the purchase without the store's approval, within a period of time previously configured by the store. After this period, the store must authorize the customer's cancellation request.
 
 4. At this stage, there are two possible statuses:
     * **Order not canceled:** If the cancellation window period expires and the customer does not request the purchase cancellation, the status changes to `Ready for handling`. This status indicates to the seller that they can begin handling the order for delivery.
@@ -119,9 +115,7 @@ Once there is a request to cancel an order, the platform processes the order can
 
 Orders with [partial invoices](https://help.vtex.com/en/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe) cannot be [canceled](https://help.vtex.com/en/tutorial/como-cancelar-pedido--tutorials_186). If the customer wants to replace or remove items from the order, it is possible to [change the order](https://help.vtex.com/en/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
-<div class = "alert alert-info">
-Learn more about cancellation and refunds in the articles <a href="https://help.vtex.com/en/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente">Why was my cancelled order charged in the customer's invoice?</a>, and <a href="https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento">Refund or cancellation</a>.
-</div>
+>ℹ️ Learn more about cancellation and refunds in the articles [Why was my cancelled order charged in the customer's invoice?](https://help.vtex.com/en/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente), and [Refund or cancellation](https://help.vtex.com/en/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento).
 
 While the cancellation is being processed, the order status remains at `Canceling`. The order status changes to `Canceled` when the cancellation is complete.
 
@@ -366,7 +360,5 @@ Here is a table with more details about each order status. The table is divided
 
 <br></br>
 
-<div class = "alert alert-info">
-The statuses marked with asterisks (*) in the table do not allow modification or cancellation because the platform changes them automatically.
-</div>
+>ℹ️ The statuses marked with asterisks (*) in the table do not allow modification or cancellation because the platform changes them automatically.
 
diff --git a/docs/tutorials/en/order-report.md b/docs/tutorials/en/order-report.md
index 3fb5ee613..d552331f4 100644
--- a/docs/tutorials/en/order-report.md
+++ b/docs/tutorials/en/order-report.md
@@ -19,9 +19,7 @@ When you export an order report on the [All Orders](https://help.vtex.com/en/tut
 
 Each row in the spreadsheet refers to a [SKU](https://help.vtex.com/en/tutorial/o-que-e-um-sku--1K75s4RXAQyOuGUYKMM68u). For example, if an order contains 3 SKUs, it will be listed in 3 rows of the report, each dedicated to data of one SKU.
 
-<div class = "alert alert-info">
-The order report link is available for download for six hours.
-</div>
+>ℹ️ The order report link is available for download for six hours.
 
 Each column corresponds to specific information, as described below.
 
diff --git a/docs/tutorials/en/order-split-and-delivery-split.md b/docs/tutorials/en/order-split-and-delivery-split.md
index 46e11b8da..e1e388b0b 100644
--- a/docs/tutorials/en/order-split-and-delivery-split.md
+++ b/docs/tutorials/en/order-split-and-delivery-split.md
@@ -22,9 +22,7 @@ See below for the main differences between order split and package split scenari
 * **[Order split](#order-split)**: occurs when more than one seller fulfills the same purchase. This means that if a single purchase will be fulfilled by three sellers, three orders will be generated.
 * **[Delivery split](#package-split-delivery-split)**: occurs when there is more than one delivery for an order. For example, when a single seller is responsible for delivery, but the order is delivered in more than one shipment.
 
-<div class = "alert alert-info">
-Whenever there is an order split, there is a delivery split. In addition, a seller may choose to split the same order into more than one package; thus, at the end of the purchase, the number of packages will always be greater than or equal to the number of orders generated.
-</div>
+>ℹ️ Whenever there is an order split, there is a delivery split. In addition, a seller may choose to split the same order into more than one package; thus, at the end of the purchase, the number of packages will always be greater than or equal to the number of orders generated.
 
 To facilitate the identification of cases in which there are order splits and delivery splits, see some examples below:
 
diff --git a/docs/tutorials/en/order-status-table-oms.md b/docs/tutorials/en/order-status-table-oms.md
index d224a65fe..f82c05225 100644
--- a/docs/tutorials/en/order-status-table-oms.md
+++ b/docs/tutorials/en/order-status-table-oms.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 The purpose of this article is to list the compatible status values in the various systems internal and external to VTEX.
 
-<div class = "alert alert-warning">
-Valid for when the order has only one transaction.
-</div>
+>⚠️ Valid for when the order has only one transaction.
 
 <table style="width: 619px;" border="1" cellspacing="0" cellpadding="0"><tbody><tr style="height: 56px;"><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>Orders Management</b>
 </td><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>My Orders</b>
diff --git a/docs/tutorials/en/order-tracking.md b/docs/tutorials/en/order-tracking.md
index 667eed01d..daa9d876a 100644
--- a/docs/tutorials/en/order-tracking.md
+++ b/docs/tutorials/en/order-tracking.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 On the [All Orders](https://help.vtex.com/en/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi) page, you can keep track of your store's orders, and on the [order details page](https://help.vtex.com/en/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl) you can view stages and perform actions throughout the life cycle of an order. You can check the status and interactions of the order, access customer, delivery, and payment data, track delivery, and send [emails](https://help.vtex.com/en/tutorial/understanding-the-message-center--tutorials_84) to customers.
 
-<div class = "alert alert-info">
-For more information on the <b>Orders</b>module, read our article <a href="https://help.vtex.com/en/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi">All Orders</a>. To learn about the statuses (stages) of the order flow, read our article<a href="https://help.vtex.com/en/tutorial/order-flow-on-the-oms--tutorials_196">Order flow and status</a>.
-</div>
+>ℹ️ For more information on the **Orders**module, read our article [All Orders](https://help.vtex.com/en/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi). To learn about the statuses (stages) of the order flow, read our article[Order flow and status](https://help.vtex.com/en/tutorial/order-flow-on-the-oms--tutorials_196).
 
 To track an order, follow the steps below:
 
diff --git a/docs/tutorials/en/orders-overview.md b/docs/tutorials/en/orders-overview.md
index 875419561..e9e9b119a 100644
--- a/docs/tutorials/en/orders-overview.md
+++ b/docs/tutorials/en/orders-overview.md
@@ -37,9 +37,7 @@ Besides searching for orders in **Orders > All Orders**, you can search for orde
 - Customer email
 - Customer document
 
-<div class = "alert alert-info">
-You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
-</div>
+>ℹ️ You can only access information from orders created in the last two years, and that same period is valid for customers through [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 ## Subscriptions
 
diff --git a/docs/tutorials/en/physical-store-instore-beta.md b/docs/tutorials/en/physical-store-instore-beta.md
index 224622d5c..e86a0c637 100644
--- a/docs/tutorials/en/physical-store-instore-beta.md
+++ b/docs/tutorials/en/physical-store-instore-beta.md
@@ -15,9 +15,7 @@ legacySlug: physical-store-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>This functionality is in Beta stage, which means we are working to improve it. If in doubt, contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>ℹ️ This functionality is in Beta stage, which means we are working to improve it. If in doubt, contact [our Support](https://support.vtex.com/hc/en-us/requests).
 
 **Physical store** is a page in the VTEX Admin **Store Settings** that displays the physical stores added to the [inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) app and allows you to manage their information.
 
@@ -77,9 +75,7 @@ You can add a physical store by following the steps below:
 * **Trade policy:** the [trade policy](https://help.vtex.com/en/tutorial/how-trade-policies-work--6Xef8PZiFm40kg2STrMkMV) that will be applied in the physical store. Mandatory field.
 * **Pickup point:** the [pickup point](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R) associated to this physical store, where customers pick up their orders. 
 
-<div class ="alert alert-info">
-<p>Changes can take up to 15 minutes to be processed and applied to inStore.</p> 
-</div>
+>ℹ️ Changes can take up to 15 minutes to be processed and applied to inStore.
 
 ## Searching for a store
 
diff --git a/docs/tutorials/en/pickup-points.md b/docs/tutorials/en/pickup-points.md
index 67a7863ae..ea524bdd2 100644
--- a/docs/tutorials/en/pickup-points.md
+++ b/docs/tutorials/en/pickup-points.md
@@ -41,15 +41,14 @@ Keep in mind that:
 * VTEX limits the location to a 50km radius between the pickup point and the customer's address.
 * In cases where transport between the [warehouse](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb) and the pickup point is required, VTEX also takes into account the existence of this route when choosing the pickup point.
 
-<div class = "alert alert-info">
-Through pickup points, VTEX also enables the merchant:
-<body>
-<ul>
-<li>Set up contingency pickup points: pickup points that can supply inventory to other points when needed, allowing the buyer the most convenient choice. To learn more, visit <a href="https://help.vtex.com/en/tutorial/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout--3mowqWEfjyM2g6WoWgE0Ao">Contingency Pickup Points.</a></li>
-<li>Set up a white label seller as the pickup point. Learn more at <a href="https://help.vtex.com/en/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e">Setting up Seller White Label as a Pickup Point.</a></li>
-</ul>
-</body>
-</div>
+>ℹ️ Through pickup points, VTEX also enables the merchant:
+> <body>
+>
+> *Set up contingency pickup points: pickup points that can supply inventory to other points when needed, allowing the buyer the most convenient choice. To learn more, visit [Contingency Pickup Points.](https://help.vtex.com/en/tutorial/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout--3mowqWEfjyM2g6WoWgE0Ao)
+>
+> *Set up a white label seller as the pickup point. Learn more at [Setting up Seller White Label as a Pickup Point.](https://help.vtex.com/en/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e)
+>
+> </body>
 
 Assure the pickup points settings are within the accepted limits and aligned with the store's sales strategy. This allows the [shipping simulation](https://help.vtex.com/en/tutorial/simulador-de-envio--tutorials_144) to consider the data correctly and ensures, for example, that the pickup point settings are not limiting the store's operation. 
 
@@ -72,9 +71,9 @@ VTEX considers the pickup point to be a shipping method, and therefore the setti
     - Step 2: On the **Shipping Policies** tab, select the shipping policy created for the pickup point.
     - Step 3: In the **Actions** column, click on the <i class="fas fa-pen"></i> icon for editing.
     - Step 4: Enable the <i class="fas fa-toggle-on"></i> of the **Link pickup points** field.
-    - Step 5: Select the pickup point from the available fields. ![relacionarpontosretiradaEN](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/6df4f0848577031ee8dcab4898061a62/relacionarpontosretiradaEN.png)<div class = "alert alert-info">For stores that have more than 50 pick points, we recommend using the Pickup Point Tags field when creating a pick point. Using tags makes it easier to find the <a href="https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140#adding-a-shipping-policy">pickup points when linking them to the shipping policy.</a> Also remember that the shipping policy that is linked to a pickup point will not be available for any other shipping method. We recommend creating a shipping policy that is exclusive to the pickup point.</div>
+    - Step 5: Select the pickup point from the available fields. ![relacionarpontosretiradaEN](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/6df4f0848577031ee8dcab4898061a62/relacionarpontosretiradaEN.png)>ℹ️ For stores that have more than 50 pick points, we recommend using the Pickup Point Tags field when creating a pick point. Using tags makes it easier to find the [pickup points when linking them to the shipping policy.](https://help.vtex.com/en/tutorial/shipping-policy--tutorials_140#adding-a-shipping-policy) Also remember that the shipping policy that is linked to a pickup point will not be available for any other shipping method. We recommend creating a shipping policy that is exclusive to the pickup point.
 
-4. [Registering geolocation](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): for greater accuracy of the location of the pickup points at the checkout.<div class = "alert alert-info">Viewing pickup points with map and time at checkout is only available for Checkout V6.</div>
+4. [Registering geolocation](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): for greater accuracy of the location of the pickup points at the checkout.>ℹ️ Viewing pickup points with map and time at checkout is only available for Checkout V6.
 
 5. Enable the address request at checkout. This way, the customer will be required to provide their address to be used on the invoice:
     - Step 1: In the VTEX Admin, go to **Store settings > Storefront > Checkout**, or type *Checkout* in the search bar at the top of the page.  
diff --git a/docs/tutorials/en/platform-status-page.md b/docs/tutorials/en/platform-status-page.md
index 1acc051ae..f1565920b 100644
--- a/docs/tutorials/en/platform-status-page.md
+++ b/docs/tutorials/en/platform-status-page.md
@@ -21,9 +21,7 @@ Events are reported by our team whenever our automatic monitoring system identif
 
 Below, you will find details about the VTEX platform status page elements.
 
-<div class = "alert alert-info">
-The status page is built on Atlassian Statuspage.
-</div>
+>ℹ️ The status page is built on Atlassian Statuspage.
 
 ## Notifications
 
diff --git a/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md b/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md
index a66b4f213..34be94407 100644
--- a/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md
+++ b/docs/tutorials/en/prevent-a-carrier-from-meeting-certain-zip-code-range.md
@@ -33,6 +33,4 @@ To do so, you would follow these steps:
 4. Each of these lines must be turned into two, so that the zip code 45920-000 is ignored. So you would have: `ZipCodeStart` = __37900-001__ and `ZipCodeEnd` = __45919-999__ / `ZipCodeStart` = __45920-001__ and `ZipCodeEnd` = __97904-999__.  
 With this, the spreadsheet would "jump" the zip code 45920-000. And consequently it would no longer be considered as an address served by that carrier.
 
-<div class = "alert alert-info">
-The postal code examples in this article refer to Brazil, each country has its own postal code format.
-</div>
+>ℹ️ The postal code examples in this article refer to Brazil, each country has its own postal code format.
diff --git a/docs/tutorials/en/price-divergence-rule.md b/docs/tutorials/en/price-divergence-rule.md
index a7ee46ad8..427b971f4 100644
--- a/docs/tutorials/en/price-divergence-rule.md
+++ b/docs/tutorials/en/price-divergence-rule.md
@@ -47,9 +47,7 @@ To create a Price Divergence rule, the user must have a Super Admin (Owner) or O
 
 You can track orders integrated using the Price Divergence rule in the VTEX Admin by clicking on **Orders > [All Orders](https://help.vtex.com/en/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**.
 
-<div class = "alert alert-info">
-It is important to regularly track orders in the <b>Orders</b> module. Orders that need to be manually approved remain in pending status until being approved by an authorized user.
-</div>
+>ℹ️ It is important to regularly track orders in the **Orders** module. Orders that need to be manually approved remain in pending status until being approved by an authorized user.
 
 ### Learn more
 
diff --git a/docs/tutorials/en/prices-settings.md b/docs/tutorials/en/prices-settings.md
index d3316d9ff..01572353e 100644
--- a/docs/tutorials/en/prices-settings.md
+++ b/docs/tutorials/en/prices-settings.md
@@ -29,12 +29,8 @@ See all the available configurations below:
   - **Always:** the account will always inherit all the prices from the parent account.
   - **Only for non-existent prices:** the parent account prices will be inherited only if they are non-existent in the current account.
 
-  <div class = "alert alert-info">
-    <p>The option to <b>Inherit prices from parent account</b> is only available for child accounts.</p>
-  </div>
+  >ℹ️ The option to **Inherit prices from parent account** is only available for child accounts.
 
 - **Overwrite seller prices:** this option overwrites all seller prices with the ones from the current account. 
 
-  <div class = "alert alert-info">
-    <p>The configuration <b>Overwrite prices for sellers</b> is not available for white label sellers.</p>
-  </div>
+  >ℹ️ The configuration **Overwrite prices for sellers** is not available for white label sellers.
diff --git a/docs/tutorials/en/products-and-skus-beta.md b/docs/tutorials/en/products-and-skus-beta.md
index 4015f53c9..db3991813 100644
--- a/docs/tutorials/en/products-and-skus-beta.md
+++ b/docs/tutorials/en/products-and-skus-beta.md
@@ -15,9 +15,7 @@ legacySlug: products-and-skus-beta
 subcategory: 6XPsLadoT3moZ7eTduCg3c
 ---
 
-<div class = "alert alert-info">
-  <p>This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href = "https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
-</div>
+>ℹ️ This feature is in beta, which means that we are working to improve it. If you have any questions, please contact <a href = "https://support.vtex.com/hc/pt-br/requests">our Support</a>.
 
 The **Products and SKUs** page allows you to view and manage the list of all products in your store, including information about SKUs, last updated, and status. To access it, go to **Catalog > Products and SKUs**.
 
diff --git a/docs/tutorials/en/promotion-alerts-beta.md b/docs/tutorials/en/promotion-alerts-beta.md
index 08b28b161..9ed3f3529 100644
--- a/docs/tutorials/en/promotion-alerts-beta.md
+++ b/docs/tutorials/en/promotion-alerts-beta.md
@@ -15,9 +15,7 @@ legacySlug: promotion-alerts-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class = "alert alert-info">
-This module is in Beta, which means we are working on improving it. If you have any questions, please contact our <a href="https://help.vtex.com/en/support">Support team</a>.
-</div>
+>ℹ️ This module is in Beta, which means we are working on improving it. If you have any questions, please contact our [Support team](https://help.vtex.com/en/support).
 
 Creating promotions is a great strategy to attract more customers to your ecommerce website. When configuring them, you must ensure that the discounts applied will produce the expected results since mistakes during the promotion creation can lead to revenue losses.
 
diff --git a/docs/tutorials/en/promotion-alerts-how-to-create-an-alert-beta.md b/docs/tutorials/en/promotion-alerts-how-to-create-an-alert-beta.md
index 7ed212486..1660618e6 100644
--- a/docs/tutorials/en/promotion-alerts-how-to-create-an-alert-beta.md
+++ b/docs/tutorials/en/promotion-alerts-how-to-create-an-alert-beta.md
@@ -15,9 +15,7 @@ legacySlug: promotion-alerts-how-to-create-an-alert-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class = "alert alert-info">
-This module is in Beta, which means we are working on improving it. If you have any questions, please contact our <a href="https://help.vtex.com/en/support">Support team.</a>
-</div>
+>ℹ️ This module is in Beta, which means we are working on improving it. If you have any questions, please contact our [Support team.](https://help.vtex.com/en/support)
 
 Creating promotions is a great strategy to attract more customers to your ecommerce website. When configuring them, you must ensure that the applied discounts will produce the expected results since mistakes when creating a promotion can lead to revenue losses.
 
diff --git a/docs/tutorials/en/promotion-examples.md b/docs/tutorials/en/promotion-examples.md
index 9a9866102..2e50a5762 100644
--- a/docs/tutorials/en/promotion-examples.md
+++ b/docs/tutorials/en/promotion-examples.md
@@ -95,9 +95,7 @@ Purchase a sweater and save 50% on a classic or contemporary long sleeve shirt.
 - “Purchase a sweater and save 50%” on another item makes this a [Buy Together Promotion](https://help.vtex.com/en/tutorial/buy-together--tutorials_323).
 - “Sweater and classic or contemporary long sleeve shirt” are items this benefit will be applied to.
 
-<div class = "alert alert-warning">
-  <p>The Buy Together Promotion works only with a percentage discount.</p>
-</div>
+>⚠️ The Buy Together Promotion works only with a percentage discount.
 
 ## Scenario 12
 
diff --git a/docs/tutorials/en/protection-against-transaction-attacks.md b/docs/tutorials/en/protection-against-transaction-attacks.md
index c2a1b0b6a..b8cfafc30 100644
--- a/docs/tutorials/en/protection-against-transaction-attacks.md
+++ b/docs/tutorials/en/protection-against-transaction-attacks.md
@@ -21,8 +21,7 @@ Protection against transaction attacks is one of the solutions offered by VTEX t
 
 In its first version, when activated, the protection will consist of applying a change to the payment flow of the purchase. This will not result in an increase in order time or a decrease in store conversion. Once the order is placed, the consumer will receive an electronic message (email or SMS) informing whether the payment has been approved or rejected.
 
-<div class = "alert alert-info"> The protection does not completely prevent the store from suffering card attacks, but it considerably reduces the number of such events. In this way, transactions become more secure.
-</div>
+>ℹ️ The protection does not completely prevent the store from suffering card attacks, but it considerably reduces the number of such events. In this way, transactions become more secure.
 
 ### How to enable protection against transaction attacks?
 
@@ -42,8 +41,7 @@ To enable the protection, please follow the instructions below:
 
 ### How to disable protection against transaction attacks?
 
-<div class = "alert alert-danger"> Disabling the protection against transaction attacks increases the risk of card testing fraud (operation performed by a fraudster using a large number of card data to make fraudulent transactions). In case of attacks that may harm one or more of VTEX's internal systems, the platform may compulsorily reactivate the protection against attacks, and the retailer will be informed of this operation.
-</div>
+>❗ Disabling the protection against transaction attacks increases the risk of card testing fraud (operation performed by a fraudster using a large number of card data to make fraudulent transactions). In case of attacks that may harm one or more of VTEX's internal systems, the platform may compulsorily reactivate the protection against attacks, and the retailer will be informed of this operation.
 
 To disable the protection, please follow the instructions below:
 
diff --git a/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
index 3dd2f61cb..bdbc79f69 100644
--- a/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
+++ b/docs/tutorials/en/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -25,9 +25,7 @@ The main advantages of this feature are:
 
 - **Increased conversion rates and sales:** The feature encourages customers to return to the payment page to complete their purchase, thereby increasing sales and conversion rates for retailers.
 
-<div class = "alert alert-info">
-WhatsApp AI Campaigns is only available for stores using <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> that don't have Checkout customizations.
-</div>
+>ℹ️ WhatsApp AI Campaigns is only available for stores using [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) that don't have Checkout customizations.
 
 ## Activating WhatsApp AI Campaigns
 
@@ -55,9 +53,7 @@ To install the Connectly app, follow the steps below:
 
 To configure a new WhatsApp number, you need to have admin access to your Facebook profile. Follow these steps to configure a new number and link it:
 
-<div class = "alert alert-info">
-We recommend creating a new phone number exclusively for linking to WhatsApp Business. This helps to avoid losing access to numbers previously used for other purposes.
-</div>
+>ℹ️ We recommend creating a new phone number exclusively for linking to WhatsApp Business. This helps to avoid losing access to numbers previously used for other purposes.
 
 <ol start="1">
   <li>In the VTEX Admin, go to <strong>Promotions &gt; WhatsApp Campaigns &gt; Overview</strong>, or type <strong>WhatsApp Campaigns Overview</strong> in the search bar at the top of the page.</li>
@@ -106,7 +102,5 @@ We recommend creating a new phone number exclusively for linking to WhatsApp Bus
 
 >⚠️ Once an abandoned checkout recovery campaign has been activated, it can take up to 48 hours for analytics metrics to start being displayed.
 
-<div class = "alert alert-info">
-Learn more about <a href="https://help.vtex.com/en/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">WhatsApp AI Campaigns management and details</a>.
-</div>
+>ℹ️ Learn more about [WhatsApp AI Campaigns management and details](https://help.vtex.com/en/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s).
 
diff --git a/docs/tutorials/en/register-tracking-on-the-tax-receipt.md b/docs/tutorials/en/register-tracking-on-the-tax-receipt.md
index 0e1681eaf..6d2d6a316 100644
--- a/docs/tutorials/en/register-tracking-on-the-tax-receipt.md
+++ b/docs/tutorials/en/register-tracking-on-the-tax-receipt.md
@@ -30,6 +30,4 @@ To register the tax receipt tracking, follow the steps below:
     - Carrier
 7. Click `Save Invoice`.
 
-<div class = "alert alert-info">
-You can change the <a href="https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE">carrier</a> associated with the order when registering the tax receipt tracking. To do so, in the <b>Order Tracking</b> section, click <i>Carrier</i> and select the desired option.
-</div>
+>ℹ️ You can change the [carrier](https://help.vtex.com/en/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) associated with the order when registering the tax receipt tracking. To do so, in the **Order Tracking** section, click <i>Carrier</i> and select the desired option.
diff --git a/docs/tutorials/en/registering-a-category.md b/docs/tutorials/en/registering-a-category.md
index 724db174c..ecc921826 100644
--- a/docs/tutorials/en/registering-a-category.md
+++ b/docs/tutorials/en/registering-a-category.md
@@ -15,9 +15,7 @@ legacySlug: registering-a-category
 subcategory: 1E7tziZCkY4w8i4EmUuwec
 ---
 
-<div class = "alert alert-info">
-On the VTEX platform, Department, Category, and Subcategory structure is not predefined. It varies according to the structure of your store, and it is not mandatory to create these 3 hierarchical levels.
-</div>
+>ℹ️ On the VTEX platform, Department, Category, and Subcategory structure is not predefined. It varies according to the structure of your store, and it is not mandatory to create these 3 hierarchical levels.
 
 The registration of a category happens inside the __Catalog__ on VTEX Admin.
 
diff --git a/docs/tutorials/en/registering-gateway-affiliations.md b/docs/tutorials/en/registering-gateway-affiliations.md
index 89ff2b913..d484a5745 100644
--- a/docs/tutorials/en/registering-gateway-affiliations.md
+++ b/docs/tutorials/en/registering-gateway-affiliations.md
@@ -36,13 +36,9 @@ To add a new payment or antifraud provider to your store, follow the steps below
 5. If a warning message is displayed indicating that you need to install the app, click the __Install App__ button and follow the installation instructions. This message is only displayed for some gateway provider types. 
 6. Click `Save`.
 
-<div class = "alert alert-info">
-  <p>If there are other fields to be completed besides App key and App token (Step 6), the gateway provider must be configured according to the specific tutorial. For more information, see the <a href="https://help.vtex.com/en/subcategory/payment-settings--3tDGibM2tqMyqIyukqmmMw">Payment Settings</a> subsection.</p>
-</div>
+>ℹ️ If there are other fields to be completed besides App key and App token (Step 6), the gateway provider must be configured according to the specific tutorial. For more information, see the [Payment Settings](https://help.vtex.com/en/subcategory/payment-settings--3tDGibM2tqMyqIyukqmmMw) subsection.
 
-<div class = "alert alert-danger">
-The credentials used to complete the App key and Appn token fields must be supplied by the payment provider to identify the store. <a href="https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet">Credentials generated in the Admin</a> starting with <code>vtexappkey-</code> should be used.
-</div>
+>❗ The credentials used to complete the App key and Appn token fields must be supplied by the payment provider to identify the store. [Credentials generated in the Admin](https://help.vtex.com/en/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) starting with `vtexappkey-` should be used.
 
 To configure the payment methods that will be processed by your chosen payment provider, read [Configuring Payment Conditions](https://help.vtex.com/en/tutorial/how-to-configure-payment-conditions--tutorials_455).
 
@@ -76,8 +72,7 @@ To select the providers using filters, go to the provider management page and ap
 
 ![interface_provedor_EN_6](https://images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/bb0b07f72dac4a7b01f5e94aa388899c/artigo_interface_provedor_EN_6.JPG)
 
-<div class = "alert alert-danger">
-To clear the applied filters and see all the providers in the store again, click the <code>Clear All</code> button.</div>
+>❗ To clear the applied filters and see all the providers in the store again, click the `Clear All` button.
 
 ## Editing provider settings
 
@@ -90,6 +85,5 @@ To edit the settings of existing payment or antifraud providers in the store, fo
 
 ![interface_provedor_EN_7](https://images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/6dffc24a68b01dd43309f119907ed1d0/artigo_interface_provedor_EN_7.JPG)
 
-<div class = "alert alert-danger">
-Before changing the provider's settings, such as authorization details, processing mode, or refund type, ensure the new information entered will not affect your store's performance.</div>
+>❗ Before changing the provider's settings, such as authorization details, processing mode, or refund type, ensure the new information entered will not affect your store's performance.
 
diff --git a/docs/tutorials/en/registering-geolocation.md b/docs/tutorials/en/registering-geolocation.md
index 5ba93b66a..7aa1fcdfd 100644
--- a/docs/tutorials/en/registering-geolocation.md
+++ b/docs/tutorials/en/registering-geolocation.md
@@ -83,5 +83,4 @@ If you need to change some delivery area of a polygon that already exists, you c
 
 Here the process is even simpler, because you don't need to change any information on the freight spreadsheet, since the system performs the search by ID.
 
-<div class = "alert alert-warning"> If the carrier and freight worksheet were created before registering the Polygon, we recommend that you edit the carrier that has a link with this Polygon to update the relationship. With this after Creating or Modifying a Polygon, open the carrier and click Save, just to raise awareness of an update.
-</div>
+>⚠️ If the carrier and freight worksheet were created before registering the Polygon, we recommend that you edit the carrier that has a link with this Polygon to update the relationship. With this after Creating or Modifying a Polygon, open the carrier and click Save, just to raise awareness of an update.
diff --git a/docs/tutorials/en/regular-promotion.md b/docs/tutorials/en/regular-promotion.md
index 0b97366ba..35e5c6d20 100644
--- a/docs/tutorials/en/regular-promotion.md
+++ b/docs/tutorials/en/regular-promotion.md
@@ -47,9 +47,7 @@ In this section, you must configure the general information of your promotion. T
   - **Maximum shipping**: Shipping maximum value. 
   - **Free Shipping**: 100% discount on shipping value.
   - **Gift**: Total discount on the product value set as a gift. You can choose more than one SKU as a gift or more than one unit of an SKU. To set more than one gift, select **Activate gift multiplier** and set the maximum selectable quantity.  For more information, read this [article](https://help.vtex.com/en/tutorial/gift-multiplier-in-promotions--1gydgkmjEWcoo2CskUwuYK#).
-<div class = "alert alert-info">
-  <p>The gift also needs to have a nominal price, even if it's given for free to the customer.</p>
-</div>
+>ℹ️ The gift also needs to have a nominal price, even if it's given for free to the customer.
   - **Nominal discount based on formula**: the discount is calculated based on the a formula that you can create using the products' total price (`total`), shipping fees (`freight`), and quantity of items (`quantity`) as variables. Note that the shipping value in the formula will be the lowest available for the order, regardless of the customer's selection. The decimal separator symbol must always be the decimal point. For example: if the discount is 30% of the total product value + shipping value, the formula should be `(total + freight) * 0.3`. For more information on the formula, read our [documentation](https://help.vtex.com/en/tutorial/regular-promotion-with-nominal-discount-based-on-formula--2Pwrq6THyGViNedQG381jV).
   - **Nominal reward value**: Nominal value for rewards program. Read [Regular promotion with reward value](https://help.vtex.com/en/tutorial/regular-promotion-with-reward-value--3FCip23ZtvG0sDt0rVGVmR) for more information.
   - **Percentage reward value**: Percentage value for rewards program. Read [Regular promotion with reward value](https://help.vtex.com/en/tutorial/regular-promotion-with-reward-value--3FCip23ZtvG0sDt0rVGVmR) for more information.
@@ -57,9 +55,7 @@ In this section, you must configure the general information of your promotion. T
 
 - **Promotion is highlighted:** If you select **Yes**, you can insert a flag with the promotion name used in the product's window display and page. This tag will only be added if you use the correct promotion display control in the template: `<vtex.cmc:discountHightLight/>`.
 
-<div class = "alert alert-info">
-  <p><b>Nominal</b> promotions will only be displayed in the cart, not on the shelf or product page.</p>
-</div>
+>ℹ️ **Nominal** promotions will only be displayed in the cart, not on the shelf or product page.
 
 ### Restrict this promotion to products from sellers
 
@@ -70,9 +66,7 @@ In this section, you can set which sellers the promotion will apply to as well a
 
 To enable a promotion for all sellers, leave the checkbox empty.
 
-<div class = "alert alert-warning">
-  <p>You cannot directly select a white label seller. To include a white label seller to the promotion, there are two options:</p><ol>1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.</ol><ol>2. Leave the checkbox empty to include all sellers, meaning that all types of sellers - whether white label or not - will be added to the promotion.</ol>
-</div>
+>⚠️ You cannot directly select a white label seller. To include a white label seller to the promotion, there are two options:1. Restrict sellers to the main store. This restriction adds all your store's white label sellers to the promotion.2. Leave the checkbox empty to include all sellers, meaning that all types of sellers - whether white label or not - will be added to the promotion.
 
 ### Trade Policy
 
@@ -103,9 +97,7 @@ See an example below. In this case, the promotion includes all products from the
 
 In the **Products** and **SKUs** fields, you can opt to upload a **.txt** file with one product or SKU ID per row instead of selecting one product or one SKU at a time. To do this, click on **Choose file** and select your **.txt** file.
 
-<div class = "alert alert-warning">
-<p>If you select <strong>Apply to the following products</strong> and do not fill in any selection criteria, the promotion will not be created, and the following message will appear: <strong>Set eligible products or apply to all products</strong>. In this case, go to the previous field and fill in the selection criteria or select <strong>Apply to all products</strong>.</p>
-</div>
+>⚠️ If you select **Apply to the following products** and do not fill in any selection criteria, the promotion will not be created, and the following message will appear: **Set eligible products or apply to all products**. In this case, go to the previous field and fill in the selection criteria or select **Apply to all products**.
 
 Products must meet all the conditions specified in this section to be available in the promotion.
 
@@ -128,24 +120,18 @@ The customer's request must meet the conditions added in this section to be vali
 - **Apply selected discount only when one of the above carriers is selected by the customer:** The promotion will apply only after the customer has effectively selected the delivery method in question. Until that method is selected, no discount is applied. This criterion is only applicable to shipping discounts, such as Percentage rate discount, Nominal rate discount, Maximum value rate or Free shipping.
 - **Payment method:** The discount will be granted if the payment method selected by the customer is the same as the one given. This discount will only be applied at checkout, when the customer selects the same payment method added for the promotion.
 
- <div class = "alert alert-info">
-  <p> By default, you can add up to 20 payment methods per promotion. In addition, you can include up to 100 payment methods via customization. If you need to use more than 20, contact <a href="https://support.vtex.com/hc/pt-br/requests">our Support</a>.</p>
- </div>
+ >ℹ️ By default, you can add up to 20 payment methods per promotion. In addition, you can include up to 100 payment methods via customization. If you need to use more than 20, contact [our Support](https://support.vtex.com/hc/pt-br/requests).
 
 - **Number of installments:** The discount will apply if the number of installments selected by the customer is less than or equal to the maximum number set.
 
-<div class = "alert alert-warning">
-  <p><b>Warning</b>: Promotions by payment method and number of installments are not valid for orders paid using two cards or gift cards.</p>
-</div>
+>⚠️ **Warning**: Promotions by payment method and number of installments are not valid for orders paid using two cards or gift cards.
 
 - **Utm\_source:** The discount will apply if browsing is done through the **utm_source** that contains the set value. The customer can only enter one **utm_source** at checkout.
 - **Utm\_campaign:** The discount will apply if browsing is done with the utm_campaign that contains the set value.
 - **Create a new coupon with the UTMs above:** Create a coupon with given UTMs to give the customer access to the promotion without UTMs, simply by using a coupon code.
 - **Utmi\_cp:** The discount will apply if navigation is done with the utmi_cp that contains the set value (case sensitive).
 
-<div class = "alert alert-info">
-  <p>The UTMs field must only contain the value that the UTMs will have to have to activate the discount. No need to insert <i>?utm_source=</i> in the field</p>
-</div>
+>ℹ️ The UTMs field must only contain the value that the UTMs will have to have to activate the discount. No need to insert <i>?utm_source=</i> in the field
 
 - **Only if it's a first buy:** The discount will only apply for the customer's first purchase.
 - **Is a subscription order**: Option that defines that the promotion will apply to subscription orders. See the conditions below:
diff --git a/docs/tutorials/en/releases-module-beta.md b/docs/tutorials/en/releases-module-beta.md
index f83790af5..a838f3003 100644
--- a/docs/tutorials/en/releases-module-beta.md
+++ b/docs/tutorials/en/releases-module-beta.md
@@ -15,9 +15,7 @@ legacySlug: releases-module-beta
 subcategory: 
 ---
 
-<div class = "alert alert-info">
-The <b>Releases</b> module is currently in beta version, which means we are working to improve it. This feature is only available for stores using FastStore.
-</div>
+>ℹ️ The **Releases** module is currently in beta version, which means we are working to improve it. This feature is only available for stores using FastStore.
 
 Managing an ecommerce operation requires the retailer to perform several updates and changes in the store, which are often interconnected — for example, carrying out a publicity campaign in which different storefront elements need to be configured.
 
@@ -30,9 +28,7 @@ The main benefits of the module are:
 - Better control when testing and reviewing changes before publishing.
 - Easier scheduling or deleting grouped changes.
 
-<div class = "alert alert-info">
-To use the <b>Releases</b> module, you must configure the CMS. Learn more in <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.
-</div>
+>ℹ️ To use the **Releases** module, you must configure the CMS. Learn more in [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 This article will cover the following topics:
 
@@ -66,9 +62,7 @@ To create a release, follow the step-by-step instructions below:
 6. Click `Create a release`.
 7. In the _Name_ field, write a name for the release.
 
-  <div class = "alert alert-info">
-In this stage, the fields <b>Day to publish</b> and <b>Time</b> are not required. This information can be decided upon later, as described in <a href="https://help.vtex.com/en/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#scheduling-releases">Scheduling releases</a>.
-</div>
+  >ℹ️ In this stage, the fields **Day to publish** and **Time** are not required. This information can be decided upon later, as described in [Scheduling releases](https://help.vtex.com/en/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#scheduling-releases).
 
 8. Click `Create`.
 
@@ -82,9 +76,7 @@ To create a release, follow the step-by-step instructions below:
 2. Click the `Create` button.
 3. In the _Name_ field, write a name for the release.
 
-  <div class = "alert alert-info">
-In this stage, the fields <b>Day to publish</b> and <i>Time</i> are not required. This information can be decided upon later, as described in Scheduling releases.
-</div>
+  >ℹ️ In this stage, the fields **Day to publish** and <i>Time</i> are not required. This information can be decided upon later, as described in Scheduling releases.
 
 4. Click `Create`.
 
@@ -127,9 +119,7 @@ When creating a release, you can set the publish date or not, which is why there
 - **Unschedule:** Cancel the publish date, which will put the release in the `Unscheduled` status.
 - **Reschedule:** Set a new date for a release with a date defined.
 
-<div class = "alert alert-info">
-When you schedule or reschedule a release publication, you can select the option <b>Add end date</b> to set a deadline for the release to be unpublished. The end date does not mean deleting the release but archiving it to be republished at any time.
-</div>
+>ℹ️ When you schedule or reschedule a release publication, you can select the option **Add end date** to set a deadline for the release to be unpublished. The end date does not mean deleting the release but archiving it to be republished at any time.
 
 ### Scheduling
 
diff --git a/docs/tutorials/en/returning-order-items.md b/docs/tutorials/en/returning-order-items.md
index ba8984915..3a2630b33 100644
--- a/docs/tutorials/en/returning-order-items.md
+++ b/docs/tutorials/en/returning-order-items.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Customers can request to exchange or return items from an order. The **Return items** feature allows you to remove items from an order in order to return them.
 
-<div class = "alert alert-info">
-See the article <a href="https://help.vtex.com/en/tutorial/como-devolver-itens-do-pedido-beta--2bSNWwD0g8fcUmuupLao9i">How to return items from an order (Beta)</a> and learn how to use this feature in Admin V4.
-</div>
+>ℹ️ See the article [How to return items from an order (Beta)](https://help.vtex.com/en/tutorial/como-devolver-itens-do-pedido-beta--2bSNWwD0g8fcUmuupLao9i) and learn how to use this feature in Admin V4.
 
 To return order items, follow the steps below:
 
diff --git a/docs/tutorials/en/sales-associates-instore-beta.md b/docs/tutorials/en/sales-associates-instore-beta.md
index 70beca28e..c9922fb75 100644
--- a/docs/tutorials/en/sales-associates-instore-beta.md
+++ b/docs/tutorials/en/sales-associates-instore-beta.md
@@ -15,9 +15,7 @@ legacySlug: sales-associates-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>This functionality is in Beta stage, which means we are working to improve it. If in doubt, contact <a href="https://support.vtex.com/hc/en-us/requests">our Support</a>.</p>
-</div>
+>ℹ️ This functionality is in Beta stage, which means we are working to improve it. If in doubt, contact [our Support](https://support.vtex.com/hc/en-us/requests).
 
 **Sales associates** is a VTEX Admin **Store Settings** page that displays a list of the sales associates registered in your [inStore](https://help.vtex.com/en/tracks/instore-getting-started-and-setting-up--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) app. It allows you to manage sales associate information across all your store's [franchise accounts](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
@@ -54,9 +52,7 @@ After creation, the sales associate will receive a confirmation email and will b
 
 ![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
-<div class ="alert alert-warning">
-<p>Sales associates registered in inStore cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.</p> 
-</div>
+>⚠️ Sales associates registered in inStore cannot access the VTEX Admin. If a sales associate tries to log in to Admin, their registration will be deleted.
 
 ### Sales associate fields
 
@@ -70,9 +66,7 @@ After creation, the sales associate will receive a confirmation email and will b
 
 * **Store:** the [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) in which the sales associate will be registered. Mandatory field.
 
-<div class ="alert alert-info">
-<p>Changes can take up to 15 minutes to be processed and applied to inStore.</p> 
-</div>
+>ℹ️ Changes can take up to 15 minutes to be processed and applied to inStore.
 
 ## Searching for a sales associate
 
diff --git a/docs/tutorials/en/sales-performance.md b/docs/tutorials/en/sales-performance.md
index 8f277f8fa..18d9ea904 100644
--- a/docs/tutorials/en/sales-performance.md
+++ b/docs/tutorials/en/sales-performance.md
@@ -36,9 +36,7 @@ To ensure that you have access to the latest updated data as well as to all of y
 
 These groups are also processed by different systems, which may cause a difference between the data of the OMS and Sales Performance. Although, we do aim for a maximum of 5% divergence.
 
-<div class ="alert alert-warning">
-The revenue metric may differ from the average ticket metric recorded in the OMS and Sales Performance, for example. This is because Sales Performance considers an order's item values, while OMS also considers discounts, freight, fees, and promotions applied to the order, which may increase or decrease its final total.
-</div>
+>⚠️ The revenue metric may differ from the average ticket metric recorded in the OMS and Sales Performance, for example. This is because Sales Performance considers an order's item values, while OMS also considers discounts, freight, fees, and promotions applied to the order, which may increase or decrease its final total.
 
 ## Period
 
diff --git a/docs/tutorials/en/search-behavior.md b/docs/tutorials/en/search-behavior.md
index 3fff4155a..e58670c44 100644
--- a/docs/tutorials/en/search-behavior.md
+++ b/docs/tutorials/en/search-behavior.md
@@ -49,9 +49,7 @@ Example: Suppose a customer wants to search for the term `ball`. Using the defau
 * `balk` (change 1 character)
 * `abll` (swap 2 characters next to each other)
 
-<div class ="alert alert-info">
-  <p>Blank spaces are not considered in <em>fuzzy</em>, so <code>base ball</code> will not be corrected to <code>baseball</code>. We recommend using <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">synonyms</a> for such cases.</p>
-</div>
+>ℹ️ Blank spaces are not considered in *fuzzy*, so `base ball` will not be corrected to `baseball`. We recommend using [synonyms](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) for such cases.
 
 ### Minimum result
 
@@ -62,9 +60,7 @@ In a search with multiple terms, the following logic occurs:
 1. If the minimum result is not reached even after the initial autocorrect, the search starts to include more comprehensive results containing any of the search terms. For example, if a user searches for "nike sneakers" and the catalog doesn't have any products matching that name, the search will return products with only the term "sneakers" instead.
 2. If the comprehensive search doesn't return the minimum result, the process will be repeated, applying autocorrect again to each term.
 
-<div class= "alert alert-warning">
-  <p>Searches with multiple terms are more efficient when customers sort the results by relevance, as such sorting can return more results than the initial search context. When sorted by relevance, items with multiple terms are prioritized. However, with other sorting criteria, such as price or bestsellers, the result ranking is based on these numerical values and does not necessarily prioritize items that match more search terms.</p>
-</div>
+>⚠️ Searches with multiple terms are more efficient when customers sort the results by relevance, as such sorting can return more results than the initial search context. When sorted by relevance, items with multiple terms are prioritized. However, with other sorting criteria, such as price or bestsellers, the result ranking is based on these numerical values and does not necessarily prioritize items that match more search terms.
 
 ### Pagination limit
 
diff --git a/docs/tutorials/en/search-control-fulltextsearchbox.md b/docs/tutorials/en/search-control-fulltextsearchbox.md
index fe01bf7d8..246cc8064 100644
--- a/docs/tutorials/en/search-control-fulltextsearchbox.md
+++ b/docs/tutorials/en/search-control-fulltextsearchbox.md
@@ -15,9 +15,7 @@ legacySlug: search-control-fulltextsearchbox
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 The `<vtex.cmc:fullTextSearchBox />` control is responsible for generating the search box. Besides the search filed, the control renders a combo for restricting a search in one department. Below we have an example of the control with no application of css:
 
diff --git a/docs/tutorials/en/search-parameters.md b/docs/tutorials/en/search-parameters.md
index ba4d914ba..813489fdb 100644
--- a/docs/tutorials/en/search-parameters.md
+++ b/docs/tutorials/en/search-parameters.md
@@ -15,9 +15,7 @@ legacySlug: search-parameters
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <strong>Warning</strong>: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ **Warning**: VTEX has two search options - VTEX search and VTEX Intelligent Search. This article refers to the VTEX search. To learn more about the VTEX Intelligent Search application, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 When making a search on VTEX, there are different possibilities of urls. The urls of Departments and Categories are made up as follows:
 
diff --git a/docs/tutorials/en/searching-for-events-on-audit.md b/docs/tutorials/en/searching-for-events-on-audit.md
index 310466eb9..fc270e3b8 100644
--- a/docs/tutorials/en/searching-for-events-on-audit.md
+++ b/docs/tutorials/en/searching-for-events-on-audit.md
@@ -46,9 +46,7 @@ Every search you perform will be saved in the **Last searches** tab. To redo a s
 
 >⚠️ This page shows only the last 50 searches. If you want to save a search indefinitely, perform the same search and add it to your browser favorites.
 
-<div class = "alert alert-info">
-You may find the full <a href="https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">list of events in Audit</a>.
-</div>
+>ℹ️ You may find the full [list of events in Audit](https://help.vtex.com/en/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## Examples of search filters 
 
@@ -77,7 +75,5 @@ You may find the full <a href="https://help.vtex.com/en/tutorial/events-availabl
 
 To see some more examples of filters you can use, click on the **Guide ** tab. 
 
-<div class = "alert alert-info">
-In the Audit application, <a href="https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">License Manager resources</a> are identified by the corresponding keys.
-</div>
+>ℹ️ In the Audit application, [License Manager resources](https://help.vtex.com/en/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) are identified by the corresponding keys.
 
diff --git a/docs/tutorials/en/seller-portal-creating-a-promotion.md b/docs/tutorials/en/seller-portal-creating-a-promotion.md
index ec94659e6..feb6f0ff5 100644
--- a/docs/tutorials/en/seller-portal-creating-a-promotion.md
+++ b/docs/tutorials/en/seller-portal-creating-a-promotion.md
@@ -27,9 +27,7 @@ To create a new promotion as a seller in the Seller Portal, follow the steps bel
 
 Then, the promotion will be activated and applied to your store.
 
-<div class = "alert alert-info">
-When multiple promotions apply to the same cart items, the Promotions module applies the one offering the highest discount to benefit the customer.
-</div> 
+>ℹ️ When multiple promotions apply to the same cart items, the Promotions module applies the one offering the highest discount to benefit the customer. 
 
 ## Promotion fields
 
diff --git a/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
index a9bee80b6..a787f1537 100644
--- a/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/en/seller-portal-getting-started-for-the-marketplace.md
@@ -60,9 +60,7 @@ The **Invited Sellers** page is where marketplace operators [invite sellers](htt
 
 Through the Seller Portal, marketplaces hosted on VTEX can connect with sellers who have a VTEX account, sellers hosted on other platforms, or sellers who are not hosted on any platform. Upon accepting the invitation, the seller chooses whether to integrate their existing VTEX account or create a new account to sell on the marketplace. 
 
-<div class = "alert alert-info">
-Once the <a href="https://help.vtex.com/en/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#convidar-seller">marketplace invites the seller</a>, an email is sent to the seller containing a link to create an account on the Seller Portal. The link is valid for seven days. After opening it, the seller has six hours to complete the registration form, without interruption.
-</div>
+>ℹ️ Once the [marketplace invites the seller](https://help.vtex.com/en/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#convidar-seller), an email is sent to the seller containing a link to create an account on the Seller Portal. The link is valid for seven days. After opening it, the seller has six hours to complete the registration form, without interruption.
 
 If the seller does not register within that period, the marketplace will have to resend the invitation. This can be done from the VTEX Admin through **MARKETPLACE > Sellers > Seller Invite**. You need to select the seller from the list and click the **Resend Invitation** button.
 
@@ -77,9 +75,7 @@ To learn more, check the following articles:
 
 Once the seller accepts the marketplace invitation and they register their Seller Portal account, the next step is activating them so they can connect to the marketplace. This changes the seller status from _Invited_ to _Active_ and adds them to **Seller Management**. Follow the instructions to activate the seller in [Connecting sellers](https://help.vtex.com/en/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#connecting-sellers).
 
-<div class = "alert alert-info">
-The seller activation step is intended to provide more security for the marketplace, in case some alignment with the seller is required before they start selling on the marketplace.
-</div>
+>ℹ️ The seller activation step is intended to provide more security for the marketplace, in case some alignment with the seller is required before they start selling on the marketplace.
 
 #### Actions through REST APIs
 
@@ -102,9 +98,7 @@ This step is optional for the marketplace and will depend on the goal of your bu
 
 When the marketplace decides to allow sharing, this is done through a [trade policy](https://help.vtex.com/en/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). Then, the seller receives the list of products that are already available in the marketplace, which allows them to import and configure inventory and pricing in the Seller Portal, under **Products > Shared Products**.
 
-<div class = "alert alert-info">
-If the marketplace operator creates an additional trade policy to define the seller catalog assortment on the Seller Portal, the policy is charged as <a href="https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X">requesting an additional trade policy</a>.
-</div>
+>ℹ️ If the marketplace operator creates an additional trade policy to define the seller catalog assortment on the Seller Portal, the policy is charged as [requesting an additional trade policy](https://help.vtex.com/en/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X).
 
 #### Sharing products
 
@@ -122,9 +116,7 @@ On VTEX, an [offer](https://help.vtex.com/en/tutorial/anuncios-y-envio-de-produc
 
 When the seller creates a new product, the marketplace needs to review and approve the offer in a process called [cataloging offers](https://help.vtex.com/en/tutorial/sugerindo-e-aprovando-skus--tutorials_396). Cataloging allows you to create new products and associate offers with SKUs or existing products to make them available for sale.
 
-<div class = "alert alert-info">
-Offers for <a href="https://help.vtex.com/en/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu">products that are shared</a> between the marketplace and the seller are approved automatically, without requiring any manual action.
-</div>
+>ℹ️ Offers for [products that are shared](https://help.vtex.com/en/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) between the marketplace and the seller are approved automatically, without requiring any manual action.
 
 The cataloging process can be completed through the VTEX Admin, under **MARKETPLACE > Sellers > Received SKUs** or through the [Match Received SKUs](https://developers.vtex.com/vtex-rest-api/reference/match) API.
 
diff --git a/docs/tutorials/en/sending-sku-attributes-to-amazon.md b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
index 31efcbc48..c25ebf77c 100644
--- a/docs/tutorials/en/sending-sku-attributes-to-amazon.md
+++ b/docs/tutorials/en/sending-sku-attributes-to-amazon.md
@@ -46,9 +46,7 @@ Sample spreadsheet using the Clothing & Accessories category:
 
 ![Amazon Mapeamento ](https://images.ctfassets.net/alneenqid6w5/5p6RrFb0T6my86cCOmW0c8/a5e93f7732929c9d9ea4cc0dd855b9a1/Amazon_Mapeamento.png)
 
-<div class = "alert alert-danger">
-Note that these values must conform to the ones from Amazon. Check which terms are allowed and make the From/To between what is registered in your SKU field in VTEX and the values accepted by Amazon.
-</div>
+>❗ Note that these values must conform to the ones from Amazon. Check which terms are allowed and make the From/To between what is registered in your SKU field in VTEX and the values accepted by Amazon.
 
 After filling out the spreadsheet, access __Integrations__ from the Admin menu:
 
diff --git a/docs/tutorials/en/sent-offers-beta.md b/docs/tutorials/en/sent-offers-beta.md
index ba359b0fb..fcf5d61f7 100644
--- a/docs/tutorials/en/sent-offers-beta.md
+++ b/docs/tutorials/en/sent-offers-beta.md
@@ -38,9 +38,7 @@ By setting up the product’s price and inventory conditions, the seller prepare
 
 This component lists all channels that have been integrated and the number of offers sent, processing and containing errors on each channel. This list provides sellers with greater visibility into the health of their integrations with external channels.
 
-<div class = "alert alert-info">
-In <b>Sent Offers</b> , you can track offers using <a href="https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Classic</a>, <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Premium</a>, <a href="https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> and <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplaces</a>.
-</div>
+>ℹ️ In **Sent Offers** , you can track offers using [Mercado Libre Classic](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Mercado Libre Premium](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) and [VTEX marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace).
 
 ## Learn more
 
diff --git a/docs/tutorials/en/sent-offers-buybox-opportunities.md b/docs/tutorials/en/sent-offers-buybox-opportunities.md
index 816e1099b..6c5ae24d8 100644
--- a/docs/tutorials/en/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/en/sent-offers-buybox-opportunities.md
@@ -27,9 +27,7 @@ An example of an opportunity is Mercado Libre’s *Buybox* feature. Buybox is a
 
 On the **Offer Management** page, *Opportunities* will be indicated in the offers listed, as illustrated in the next section.
 
-<div class = "alert alert-info">
-In <b>Offer Management</b> , you can track offers using <a href="https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Classic</a>, <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Premium</a>, <a href="https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> and <a href="https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace">VTEX marketplaces</a>. For connectors to integrate via API, see <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Offer Management Integration Guide</a>.
-</div>
+>ℹ️ In **Offer Management** , you can track offers using [Mercado Libre Classic](https://help.vtex.com/en/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Mercado Libre Premium](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Netshoes](https://help.vtex.com/en/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) and [VTEX marketplaces](https://help.vtex.com/en/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#being-a-vtex-marketplace). For connectors to integrate via API, see [Offer Management Integration Guide](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Offer list
 
diff --git a/docs/tutorials/en/set-up-mundi-gateway.md b/docs/tutorials/en/set-up-mundi-gateway.md
index 280d4a8a5..7a7b7558c 100644
--- a/docs/tutorials/en/set-up-mundi-gateway.md
+++ b/docs/tutorials/en/set-up-mundi-gateway.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 At VTEX, it is possible to integrate with the Mundi payment provider.
 
-<div class= "alert alert-warning">
-If you also want to use Mundi's anti-fraud, the settings for this function must be performed by the company's own hub. In case of doubts about this stage of the operation, consult Mundi's technical support.
-</div>
+>⚠️ If you also want to use Mundi's anti-fraud, the settings for this function must be performed by the company's own hub. In case of doubts about this stage of the operation, consult Mundi's technical support.
 
 To configure Mundi, follow the steps below:
 
diff --git a/docs/tutorials/en/setting-the-grace-period-for-order-cancellation.md b/docs/tutorials/en/setting-the-grace-period-for-order-cancellation.md
index cf29839be..745bb570a 100644
--- a/docs/tutorials/en/setting-the-grace-period-for-order-cancellation.md
+++ b/docs/tutorials/en/setting-the-grace-period-for-order-cancellation.md
@@ -21,9 +21,7 @@ That is, if the customer requests cancellation before or during the grace period
 
 If the customer requests cancellation after the grace period has ended, the store receives the request, but cancellation is only made if the store approves it at the Orders management.
 
-<div class = "alert alert-info">
-By default, the grace period for order cancellation is set to 30 minutes, but you can change it to better meet your business' demands.
-</div>
+>ℹ️ By default, the grace period for order cancellation is set to 30 minutes, but you can change it to better meet your business' demands.
 
 For example, if your store sells food or pharmaceuticals that need to be delivered in a short time, it probably makes sense to have a lower cancellation tolerance.
 
diff --git a/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md b/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md
index d90bfe4a3..0d90a1991 100644
--- a/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md
+++ b/docs/tutorials/en/setting-up-3ds-2-authentication-flow.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 3D Secure 2.0 (3DS 2) is an authentication flow that increases security in payments made with credit and debit cards, through the internal analysis of a large amount of data present in each transaction.
 
-<div class = "alert alert-warning">
-<p>3DS 2 is only supported for some VTEX affiliations. Check with your payment provider and Admin VTEX if this functionality is available.</p>
-</div>
+>⚠️ 3DS 2 is only supported for some VTEX affiliations. Check with your payment provider and Admin VTEX if this functionality is available.
 
 Before starting the configuration, it is necessary to open a ticket with the VTEX support team requesting the 3DS 2 activation in your store. For more information, see [how to open a ticket](https://help.vtex.com/en/tutorial/opening-tickets-to-vtex-support--16yOEqpO32UQYygSmMSSAM).
 
diff --git a/docs/tutorials/en/setting-up-abandoned-carts.md b/docs/tutorials/en/setting-up-abandoned-carts.md
index 2c6aa1873..60ac4a9bb 100644
--- a/docs/tutorials/en/setting-up-abandoned-carts.md
+++ b/docs/tutorials/en/setting-up-abandoned-carts.md
@@ -63,9 +63,7 @@ Once the new email template has been created or the data from the default templa
 7. In __Html__, enter the created or default email template information.
 8. Click on `Save`.
 
-<div class = "alert alert-info">
-The JSON Data field must not be filled or its data used in the email template. It only contains information to allow a preview of the format in which the data will be viewed in the email.
-</div>
+>ℹ️ The JSON Data field must not be filled or its data used in the email template. It only contains information to allow a preview of the format in which the data will be viewed in the email.
 
 ![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/72c7499b2fdc65ee661c3cb45a387a60/new_template.PNG)
 
diff --git a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
index ea57f5ac5..f5f254a87 100644
--- a/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
+++ b/docs/tutorials/en/setting-up-app-linking-for-payments-app-in-instore.md
@@ -122,9 +122,7 @@ Final URI that the payment app will receive to perform the refund action with th
 super-acquirer://payment-reversal?acquirerAuthorizationCode=86273634-3a05-4f0a-a430-f55ed3f21eab&acquirerId=954090369&transactionId=1093019039&paymentId=1093019888&acquirerTid=1093019888&administrativeCode=11010103033&sellerName=instoreqa&autoConfirm=True&scheme=instore&urlCallback=instore://payment-reversal
 ```
 
-<div class = "alert alert-warning">
-<strong>NOTE:</strong> Not all parameters will be used by all payment acquirers/apps. Example: <code>transactionId</code>. This parameter is the ID of a transaction in VTEX that identifies all payments of a complete order on VTEX PCI Gateway. A transaction can contain multiple payments, such as when an order is paid with multiple credit or debit cards.
-</div>
+>⚠️ **NOTE:** Not all parameters will be used by all payment acquirers/apps. Example: `transactionId`. This parameter is the ID of a transaction in VTEX that identifies all payments of a complete order on VTEX PCI Gateway. A transaction can contain multiple payments, such as when an order is paid with multiple credit or debit cards.
 
 ## Examples of response URIs for each action
 
diff --git a/docs/tutorials/en/setting-up-mundipagg-gateway.md b/docs/tutorials/en/setting-up-mundipagg-gateway.md
index 7a60508d1..eb546fa36 100644
--- a/docs/tutorials/en/setting-up-mundipagg-gateway.md
+++ b/docs/tutorials/en/setting-up-mundipagg-gateway.md
@@ -35,9 +35,7 @@ To configure Mundipagg, follow the steps below:
 12. In __Captura de segurança antecipada__ ("Early security capture"), choose how long you want the capture to take after the transaction approval and the anti-fraud analysis. You can also disable this function.
 13. Click __Save__.
 
-<div class = "alert alert-info">
-The steps indicated in steps <strong>8</strong>, <strong>9</strong>, <strong>11</strong> and <strong>12</strong> must be completed if you want to offer bank slips as payment conditions in your store.
-</div>
+>ℹ️ The steps indicated in steps **8**, **9**, **11** and **12** must be completed if you want to offer bank slips as payment conditions in your store.
 
 ## Setting up the payment condition
 After following the steps indicated above, Mundipagg will be configured in your store. Thus, while you're registering a payment condition, it will be available in the __Process with affiliation__ field (provided the payment method is compatible with Mundipagg). To learn how to set up payment conditions, visit [this Help article](/en/tutorial/how-to-configure-payment-conditions).
diff --git a/docs/tutorials/en/setting-up-my-account.md b/docs/tutorials/en/setting-up-my-account.md
index 895fc8e0e..fb702d511 100644
--- a/docs/tutorials/en/setting-up-my-account.md
+++ b/docs/tutorials/en/setting-up-my-account.md
@@ -15,9 +15,7 @@ legacySlug: setting-up-my-account
 subcategory: 1RWR7qSyaREbD5RfgCjdYG
 ---
 
-<div class = "alert alert-info">
-In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
-</div>
+>ℹ️ In [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), customers can only access their orders from the last two years.
 
 The new [My Account](https://help.vtex.com/en/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh) is already installed in all VTEX accounts pertaining to a <strong>test environment</strong>, allowing adjustments on the new page to be implemented without impacting user experience.
 
diff --git a/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md b/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md
index 94c10d2b9..f5c02a911 100644
--- a/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md
+++ b/docs/tutorials/en/setting-up-price-and-availability-of-skus-by-region.md
@@ -27,9 +27,7 @@ To regionalize SKU prices and availability, it is necessary:
 
 >⚠️ In case of [Multilevel Omnichannel Inventory](https://help.vtex.com/en/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#), a marketplace (level 1) cannot configure the display of prices and availability of White Label Seller products (level 3) with the regionalization feature.
 
-<div class = "alert alert-info">
-The feature <b>Region</b> works for both CMS Portal Legacy stores and stores developed using <a href="https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC">VTEX IO</a>, but the feature <a href="https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a> is available only for stores using VTEX IO. As a result, stores with CMS Portal Legacy have a limitation in indexing regionalized data, and it is not possible to correctly order the sellers that serve the storefront of a RegionId based on the availability of items.
-</div>
+>ℹ️ The feature **Region** works for both CMS Portal Legacy stores and stores developed using [VTEX IO](https://help.vtex.com/en/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC), but the feature [VTEX Intelligent Search](https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) is available only for stores using VTEX IO. As a result, stores with CMS Portal Legacy have a limitation in indexing regionalized data, and it is not possible to correctly order the sellers that serve the storefront of a RegionId based on the availability of items.
 
 ## Setting up delivery in Franchise Account/White Label Seller
 
diff --git a/docs/tutorials/en/setting-up-product-comparison.md b/docs/tutorials/en/setting-up-product-comparison.md
index 2229e2ea7..6538f251c 100644
--- a/docs/tutorials/en/setting-up-product-comparison.md
+++ b/docs/tutorials/en/setting-up-product-comparison.md
@@ -24,9 +24,7 @@ We can divide this feature in two parts::
 1. **Comparison Page**: Where the user will view the comparison of products selected in the window shop.
 2. **Window display**: Where the user will select the products to be compared.
 
-<div class = "alert alert-warning">
-  <p>This feature can't be used on the website's home page.</p>
-</div>
+>⚠️ This feature can't be used on the website's home page.
 
 ## Setting up
 
diff --git a/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md b/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
index 977373bde..ad24cab35 100644
--- a/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
+++ b/docs/tutorials/en/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
@@ -23,9 +23,7 @@ In order to collaborate, a marketplace hosted on the VTEX platform and a seller,
 - [Connected marketplace and seller](#connected-marketplace-and-seller)
 - [Sharing customer emails](#sharing-customer-emails)
 
-<div class = "alert alert-info">
-If you want to start selling your products on other marketplaces, use <a href="https://help.vtex.com/en/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM">Marketplaces and Integrations</a>. This feature allows marketplaces and sellers operating in the VTEX ecosystem to identify and contact each another.
-</div>
+>ℹ️ If you want to start selling your products on other marketplaces, use [Marketplaces and Integrations](https://help.vtex.com/en/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM). This feature allows marketplaces and sellers operating in the VTEX ecosystem to identify and contact each another.
 
 ## Connecting a marketplace and a seller 
 
@@ -43,9 +41,7 @@ Also, to [add the seller](https://help.vtex.com/en/tutorial/configurando-seller)
 
 You can integrate a VTEX marketplace with a VTEX seller or with an external seller either through the VTEX Admin or through API. In either case, the information shared between the marketplace and the seller will be the same.
 
-<div class = "alert alert-info">
-For more information on how to connect a VTEX marketplace to a VTEX seller using the VTEX Admin, please check out the article <a href="https://help.vtex.com/en/tutorial/configurando-seller">Adding a seller</a>. For integration via API use the call <a href="https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers">Configure Seller Account</a>. For external sellers, check out the <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">External Seller Integration Guide</a>.
-</div>
+>ℹ️ For more information on how to connect a VTEX marketplace to a VTEX seller using the VTEX Admin, please check out the article [Adding a seller](https://help.vtex.com/en/tutorial/configurando-seller). For integration via API use the call [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers). For external sellers, check out the [External Seller Integration Guide](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide).
 
 ### Connecting a VTEX marketplace to a VTEX seller
 
@@ -84,9 +80,7 @@ The marketplace can give the seller partial access to the email addresses of its
 - [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers): this allows setting up the seller account, whether it is a VTEX seller or an external one.
 - [Update Seller by Seller ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#patch-/seller-register/pvt/sellers/-sellerId-): this allows updating the seller information, whether it is a VTEX seller or an external one.
 
-<div class = "alert alert-info">
-For orders placed in the marketplace, the customer email is not displayed to the seller. The customer establishes a relationship with the marketplace. Therefore, the customer's consent would be necessary for sharing their information.
-</div>
+>ℹ️ For orders placed in the marketplace, the customer email is not displayed to the seller. The customer establishes a relationship with the marketplace. Therefore, the customer's consent would be necessary for sharing their information.
 
 ## Learn more
 
diff --git a/docs/tutorials/en/shipping-options-beta.md b/docs/tutorials/en/shipping-options-beta.md
index 6ac024055..6c44f5d2c 100644
--- a/docs/tutorials/en/shipping-options-beta.md
+++ b/docs/tutorials/en/shipping-options-beta.md
@@ -33,9 +33,7 @@ The purpose of **Shipping Options**, however, is not to replace [shipping polici
 
 The **Shipping Options** distinguish between what the consumer is charged for shipping the order and the shipping cost for the retailer, as it is possible to set up different pricing rules for the shipping rate.
 
-<div class = "alert alert-info">
-The shipping costs that the carriers charge must be in the shipping rate template so that the suitable carrier can be chosen.
-</div>
+>ℹ️ The shipping costs that the carriers charge must be in the shipping rate template so that the suitable carrier can be chosen.
 
 The **Shipping Options** allow the retailer to configure the shipping rate based on:
 
@@ -57,9 +55,7 @@ In each shipping option, the retailer sets an SLA (_Service Level Agreement_), a
 
 The VTEX [Order Allocation Algorithm](https://help.vtex.com/en/tutorial/order-allocation-algorithm-beta--1zLCAyEdnVe3EsE9Kz88xA) analyzes the store and distribution center combinations that serve each shipping option and seeks the ones with the lowest shipping cost. In the example, the result is a combination of lowest-cost same-day shipping and another combination of lowest-cost shipping within 5 business days.
 
-<div class = "alert alert-info">
-The <b>Shipping options</b> ensure that the consumer will always have a shipping option available for their location, which wasn't the case before. The only exception is if there is no seller and no shipping policy that meets the conditions for a shipping option. In this case, no shipping option will appear for the consumer at checkout.
-</div>
+>ℹ️ The **Shipping options** ensure that the consumer will always have a shipping option available for their location, which wasn't the case before. The only exception is if there is no seller and no shipping policy that meets the conditions for a shipping option. In this case, no shipping option will appear for the consumer at checkout.
 
 ## Actions and configuration
 
diff --git a/docs/tutorials/en/shipping-simulation.md b/docs/tutorials/en/shipping-simulation.md
index 1f02d11e9..8e67a3a12 100644
--- a/docs/tutorials/en/shipping-simulation.md
+++ b/docs/tutorials/en/shipping-simulation.md
@@ -52,9 +52,7 @@ If you want, you can check the `Simulate items individually` box.
 
  10. Click on the `Shipping simulation` button.
 
-<div class = "alert alert-info">
-The items measurements in the simulation result appear in centimeters and grams; however, the actual values for the Checkout are the measurement units registered in the SKU and <a href="https://help.vtex.com/en/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">product registration fields</a>.
-</div>
+>ℹ️ The items measurements in the simulation result appear in centimeters and grams; however, the actual values for the Checkout are the measurement units registered in the SKU and [product registration fields](https://help.vtex.com/en/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke).
 
 ## Simulation details
 
diff --git a/docs/tutorials/en/sku-bindings.md b/docs/tutorials/en/sku-bindings.md
index 71d303393..2373c9770 100644
--- a/docs/tutorials/en/sku-bindings.md
+++ b/docs/tutorials/en/sku-bindings.md
@@ -21,9 +21,7 @@ Every time a seller sends its products to a VTEX marketplace, the marketplace [c
 
 Once the marketplace has cataloged the SKUs, either via the **Received SKUs** page or by using the [VTEX Matcher](https://help.vtex.com/en/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), the bindings between the seller’s SKUs and the marketplace SKUs appear on the **SKU Bindings** page. Bindings will automatically have the _Bind_ status.
 
-<div class = "alert alert-info">
-By default, <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">white label sellers</a> do not have that binding between their SKUs and the ones from the marketplace.
-</div>
+>ℹ️ By default, [white label sellers](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) do not have that binding between their SKUs and the ones from the marketplace.
 
 The **SKU Bindings** page allows the marketplace to track and manage the binding relationship between the seller’s SKUs and the ones from the marketplace. To access the page, go to the VTEX Admin, **Marketplace > Sellers > SKU Bindings**. You'll see the following interface:
 
@@ -65,17 +63,13 @@ You can also search through the list by filtering per binding status. To do this
 
 To return to the list with all the binding statuses, click on the `Clear all` button. This button will only clear the status filter, not the terms you have entered into the search boxes.
 
-<div class = "alert alert-info">
-If the search returns no results, check the spelling of the words you have written or check the combination of filters you have used.
-</div>
+>ℹ️ If the search returns no results, check the spelling of the words you have written or check the combination of filters you have used.
 
 ## Unbinding a SKU
 
 To undo a SKU binding, click on the _switch_ <i class="fas fa-toggle-on"></i> option and confirm the option `Unbind SKU`. 
 
-<div class = "alert alert-info">
-When you unbind the seller's SKU, the SKU will no longer receive price and stock updates, and it will be shown as unavailable in the marketplace catalog. You may rebind the SKU at any time. To do so, you do not have to catalog the seller's SKU again.
-</div>
+>ℹ️ When you unbind the seller's SKU, the SKU will no longer receive price and stock updates, and it will be shown as unavailable in the marketplace catalog. You may rebind the SKU at any time. To do so, you do not have to catalog the seller's SKU again.
 
 If you want to reestablish the binding between the seller’s SKU and the marketplace SKU, select the _switch_ option <i class="fas fa-toggle-on"></i> again by clicking on it.
 
@@ -109,9 +103,7 @@ To export the SKU binding list in XLSX format, follow the steps below:
 
 The spreadsheet will be sent to the email of the user that is currently logged in. Export time depends on processing factors of the VTEX platform and on the size of the file.
 
-<div class = "alert alert-info">
-When exporting, the exported file will have a list with the bindings of the SKUs. If there's an active search or filter, only the selected bindings will be exported.
-</div>
+>ℹ️ When exporting, the exported file will have a list with the bindings of the SKUs. If there's an active search or filter, only the selected bindings will be exported.
 
 ## Learn more
 
diff --git a/docs/tutorials/en/sku-registration-fields.md b/docs/tutorials/en/sku-registration-fields.md
index a522a3503..05a29c0f3 100644
--- a/docs/tutorials/en/sku-registration-fields.md
+++ b/docs/tutorials/en/sku-registration-fields.md
@@ -31,9 +31,7 @@ __Reference Code:__ Unique reference code used internally for organizational pur
 
 __Shipping Weight:__ Shipping weight, which must have a value greater than zero to make the <a href="https://help.vtex.com/en/tutorial/how-proportional-shipping-costs-are-calculated--frequentlyAskedQuestions_155">proportional shipping cost</a> work properly.
 
-<div class = "alert alert-info">
-The <b>Inventory & Shipping/Shipping</b> module does not take units of measure into account in the fields below. It is only necessary to be consistent with what is registered in the SKU and in the <a href="https://help.vtex.com/en/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">product registration fields</a>.
-</div>
+>ℹ️ The **Inventory & Shipping/Shipping** module does not take units of measure into account in the fields below. It is only necessary to be consistent with what is registered in the SKU and in the [product registration fields](https://help.vtex.com/en/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke).
 
 __Shipping Height:__ Shipping height.
 
diff --git a/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md b/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md
index 261fee757..3b23d67a1 100644
--- a/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md
+++ b/docs/tutorials/en/smartcheckout-customer-information-automatic-fill-in.md
@@ -40,9 +40,7 @@ The information previously entered in the [Master Data](https://help.vtex.com/en
    - street
    - receiverName
 
-<div class = "alert alert-warning">
-If one or more fields have not been properly filled in in the Master Data, SmartCheckout will not automatically populate the customer information fields at Checkout. In this case, customers will have to fill in their identification data manually for each purchase. 
-</div>
+>⚠️ If one or more fields have not been properly filled in in the Master Data, SmartCheckout will not automatically populate the customer information fields at Checkout. In this case, customers will have to fill in their identification data manually for each purchase.
 
 ## Purchasing with SmartCheckout
 
@@ -53,19 +51,16 @@ At checkout, the customer's information is automatically filled in as follows:
 3. SmartCheckout verifies whether the email address belongs to a store customer or not. 
 4. After the email is verified, the customer’s identification fields are automatically filled in with the data from the Master Data at Checkout.
 
-<div class = "alert alert-warning">
-To protect customer data, personal information will be shown only partially on the checkout page (part of the data is hidden using the <a href="https://help.vtex.com/en/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#">PCI-DSS</a> payment security standard). This procedure allows the customers to identify whether their current data is correct and, if needed, to also select different addresses for delivery.
-</div>
+>⚠️ To protect customer data, personal information will be shown only partially on the checkout page (part of the data is hidden using the [PCI-DSS](https://help.vtex.com/en/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#) payment security standard). This procedure allows the customers to identify whether their current data is correct and, if needed, to also select different addresses for delivery.
 <ul>
 5. The customer chooses the delivery and payment methods, and completes the purchase order.
 </ul>
-<div class = "alert alert-warning">
-If payment with a credit or debit card is chosen, the following additional security criteria will apply:
-  <ul>
-    <li>The CVV (Card Verification Value) will be requested for final validation and completion of the purchase order.</li>
-    <li>The customer won't be able to pay with a debit or credit card if the address is different from the one stored on the profile.</li>
-   </ul>
-</div>
+>⚠️ If payment with a credit or debit card is chosen, the following additional security criteria will apply:
+>
+> * The CVV (Card Verification Value) will be requested for final validation and completion of the purchase order.
+>
+> * The customer won't be able to pay with a debit or credit card if the address is different from the one stored on the profile.
+>    
 
 Changes to the stored data, such as address or phone number, will only be allowed once the customer is [authenticated in the store](https://help.vtex.com/en/tutorial/como-meu-cliente-pode-fazer-login-na-minha-loja--3FCNpwbpZe0U4auiI4CC0C#). 
 
diff --git a/docs/tutorials/en/smartcheckout-security.md b/docs/tutorials/en/smartcheckout-security.md
index d868cf07c..d0598467b 100644
--- a/docs/tutorials/en/smartcheckout-security.md
+++ b/docs/tutorials/en/smartcheckout-security.md
@@ -35,7 +35,6 @@ This means that the scammer would have to authenticate via login or by using an
 
 Moreover, at checkout, the information is hidden using a certified payment security standard [PCI-DSS](https://help.vtex.com/pt/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#). According to this standard, the last digits of a card do not need to be hidden. The displayed information allows recognizing the payment method, but it's not enough for making a purchase.
 
-<div class = "alert alert-info">
-<p>With VTEX SmartCheckout™, safety comes first. If an email address is recognized, the way the details are filled in ensures that only the email owner will recognize the information.</p><p>When accessing the store from the restricted domain <code>myvtex.com</code>, store operators can see the unmasked data in SmartCheckout to run tests. Access from this domain is restricted to store admins with the right access level and credentials.</p>
-</div>
+>ℹ️ With VTEX SmartCheckout™, safety comes first. If an email address is recognized, the way the details are filled in ensures that only the email owner will recognize the information.
+> When accessing the store from the restricted domain `myvtex.com`, store operators can see the unmasked data in SmartCheckout to run tests. Access from this domain is restricted to store admins with the right access level and credentials.
 
diff --git a/docs/tutorials/en/special-conditions.md b/docs/tutorials/en/special-conditions.md
index c1a3fb7fd..7a6e342c1 100644
--- a/docs/tutorials/en/special-conditions.md
+++ b/docs/tutorials/en/special-conditions.md
@@ -158,6 +158,4 @@ How to configure the payment condition period:
 
 Suppose that your store usually offers a payment with in to 6x, without interest, but wants to use the end-of-year sales to offer payment in up to 12x, without interest. In this case, follow the steps above, and add the period of the payment condition. Its application can cease on January 1st of the following year, for example.
 
-<div class = "alert alert-warning">
-  <p>Payment conditions have a cache of up to 10 minutes it Smart Checkout. Thus, any change in Payment Conditions in the <strong>Payments</strong> module can take up to 10 minutes to start operating in Smart Checkout.</p>
-</div>
+>⚠️ Payment conditions have a cache of up to 10 minutes it Smart Checkout. Thus, any change in Payment Conditions in the **Payments** module can take up to 10 minutes to start operating in Smart Checkout.
diff --git a/docs/tutorials/en/store-overview-beta.md b/docs/tutorials/en/store-overview-beta.md
index 293649db5..5190403aa 100644
--- a/docs/tutorials/en/store-overview-beta.md
+++ b/docs/tutorials/en/store-overview-beta.md
@@ -36,9 +36,7 @@ In this article, we describe the main page sections and actions. You will learn
 
 The metrics on this page include order and browsing data collected by different systems.
 
-<div class ="alert alert-warning">
-The revenue metric may differ from the average ticket metric recorded in the OMS and Sales Performance, for example. This is because Sales Performance considers an order's item values, while OMS also considers discounts, freight, fees, and promotions applied to the order, which may increase or decrease its final total.
-</div>
+>⚠️ The revenue metric may differ from the average ticket metric recorded in the OMS and Sales Performance, for example. This is because Sales Performance considers an order's item values, while OMS also considers discounts, freight, fees, and promotions applied to the order, which may increase or decrease its final total.
 
 -	**Orders and revenue:** The order and revenue data comes from the VTEX Order Management System (OMS) and includes orders placed on all your sales channels.
 -	**Sessions:** The browsing data comes from the platform’s internal system, which collects user sessions from storefronts of VTEX stores. Sessions represent the total number of views on pages accessed by a single user while browsing through your ecommerce store, excluding marketplaces, apps, VTEX Sales App, or other sales channels.
diff --git a/docs/tutorials/en/telesales-features.md b/docs/tutorials/en/telesales-features.md
index 2361367e6..155d3baeb 100644
--- a/docs/tutorials/en/telesales-features.md
+++ b/docs/tutorials/en/telesales-features.md
@@ -36,9 +36,7 @@ The telesales toolbar is displayed at the top of your store's website for users
 
 To learn how to use this feature, check out the [Telesales toolbar](https://help.vtex.com/en/tutorial/usando-e-customizando-toolbar-de-televendas--tutorials_5500) tutorial.
 
-<div class = "alert alert-info">
-A use case for the telesales feature is to import orders from other platforms to the VTEX <b>Orders</b> module. To do this, you can associate a specific <a href="https://help.vtex.com/en/tutorial/creating-a-sales-policy--563tbcL0TYKEKeOY4IAgAE">trade policy</a> with payment <a href="https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ">Notes Payable</a> (payment method immediately and manually approved by the operator).
-  </div>
+>ℹ️ A use case for the telesales feature is to import orders from other platforms to the VTEX **Orders** module. To do this, you can associate a specific [trade policy](https://help.vtex.com/en/tutorial/creating-a-sales-policy--563tbcL0TYKEKeOY4IAgAE) with payment [Notes Payable](https://help.vtex.com/en/tutorial/setting-up-payments-with-notes-payable--5pW7avTwtyQcMu4uiW8quQ) (payment method immediately and manually approved by the operator).
 
 ### My Account
 
diff --git a/docs/tutorials/en/transactional-emails-for-subscription-orders.md b/docs/tutorials/en/transactional-emails-for-subscription-orders.md
index 42ad38c24..90d4a5359 100644
--- a/docs/tutorials/en/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/en/transactional-emails-for-subscription-orders.md
@@ -28,9 +28,7 @@ You can also create your own email template. Learn how to [configure transaction
 
 ## How your customer tracks their Subscription Orders
 
-<div class = "alert alert-info">
-In <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>, customers can only access their orders from the last two years.
-</div>
+>ℹ️ In [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), customers can only access their orders from the last two years.
 
 Each action that occurs within the Subscription order flow contains a trigger that sends an email notifying your customer. After activating the Subscription, your customer will receive e-mails with details of the status of each subscription order every time they perform an action.
 
diff --git a/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
index a1d87aa7a..88cddb2fe 100644
--- a/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/en/troubleshooting-errors-in-subscription-orders.md
@@ -15,9 +15,7 @@ legacySlug: how-to-troubleshoot-subscription-orders-with-errors
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
-<div class = "alert alert-info">
-You can only access information from orders created in the last two years, and that same period is valid for customers through <a href="https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">My Account</a>.
-</div>
+>ℹ️ You can only access information from orders created in the last two years, and that same period is valid for customers through [My Account](https://help.vtex.com/en/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 You can identify and manage errors in subscription orders in the Admin, in **Subscriptions** > **Dashboards** > **Subscription Orders**.
 
diff --git a/docs/tutorials/en/troubleshooting-price-divergence-errors-in-marketplace-orders.md b/docs/tutorials/en/troubleshooting-price-divergence-errors-in-marketplace-orders.md
index 5d4b7dd91..be637cd83 100644
--- a/docs/tutorials/en/troubleshooting-price-divergence-errors-in-marketplace-orders.md
+++ b/docs/tutorials/en/troubleshooting-price-divergence-errors-in-marketplace-orders.md
@@ -23,9 +23,7 @@ When the price set by a seller is different from the price offered by the market
 
 To activate the Orders Authorization flow for native connectors, you need to [configure a Price Divergence rule](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe). Only users with Super Admin (Owner) or OMS Full [roles](https://help.vtex.com/en/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) can do this.
 
-<div class = "alert alert-info">
-Once you have <a href="https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configured the Price Divergence rule</a>, it will apply to all marketplaces where you are a seller.
-</div>
+>ℹ️ Once you have [configured the Price Divergence rule](https://help.vtex.com/en/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), it will apply to all marketplaces where you are a seller.
 
 For VTEX marketplaces, external marketplaces and certified connectors (partners), as long as the Price Divergence rule has not been created, orders with price divergence error are automatically approved.
 
diff --git a/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md b/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md
index 0d7e2beb6..1e549b028 100644
--- a/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md
+++ b/docs/tutorials/en/visao-geral-da-estrutura-do-catalogo.md
@@ -23,9 +23,7 @@ An example of a catalog structure would be as follows:
 
 ![img como funciona o catalogo](https://images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
 
-<div class = "alert alert-warning">
-Your categories tree does not need to have three levels. The hierarchy shown above is just an example. The amount of category levels to be created depends very much on the sector of activity of each store.
-</div>
+>⚠️ Your categories tree does not need to have three levels. The hierarchy shown above is just an example. The amount of category levels to be created depends very much on the sector of activity of each store.
 
 Once you create your store and register your products, you'll get a more concrete and organized view of what you've read here.
 
diff --git a/docs/tutorials/en/vtex-ad-network-beta.md b/docs/tutorials/en/vtex-ad-network-beta.md
index 2fa9d6f93..b6954d738 100644
--- a/docs/tutorials/en/vtex-ad-network-beta.md
+++ b/docs/tutorials/en/vtex-ad-network-beta.md
@@ -15,9 +15,7 @@ legacySlug: vtex-ad-network-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>VTEX Ad Network is in beta, which means that we are working to improve it. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
-</div>
+>ℹ️ VTEX Ad Network is in beta, which means that we are working to improve it. If you are already a VTEX customer and wish to adopt this functionality for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). If you are not yet a customer but are interested in this solution, please fill out the [contact form](https://vtex.com/us-en/contact/).
 
 **VTEX Ad Network** connects VTEX stores with brands interested in advertising their products. This connection allows advertisers and merchants to boost their business:
 
diff --git a/docs/tutorials/en/vtex-admin-start-here.md b/docs/tutorials/en/vtex-admin-start-here.md
index f7942e291..817845937 100644
--- a/docs/tutorials/en/vtex-admin-start-here.md
+++ b/docs/tutorials/en/vtex-admin-start-here.md
@@ -89,9 +89,7 @@ Feedback type (select one or more options):
 
 **A screenshot will help us better understand your feedback (optional):** Optional field to add screenshots or documents that can help us understand your feedback in more detail.
 
-<div class = "alert alert-info">
-This feedback process should not be used to create a ticket or technical support request at VTEX.
-</div>
+>ℹ️ This feedback process should not be used to create a ticket or technical support request at VTEX.
 
 ### User and Account Settings
 
diff --git a/docs/tutorials/en/vtex-do-interface.md b/docs/tutorials/en/vtex-do-interface.md
index bad5bf9be..7e4c8c533 100644
--- a/docs/tutorials/en/vtex-do-interface.md
+++ b/docs/tutorials/en/vtex-do-interface.md
@@ -19,9 +19,7 @@ VTEX DO manages tasks automatically created by the VTEX Admin that require manua
 
 ![VTEX Do overview EN](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/0b341bae7a9f462483ddefb3ad044e14/VTEX_Do_overview_EN.gif)
 
-<div class = "alert alert-info">
-Only users with the <a href = "https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> role can perform tasks through VTEX DO.
-</div>
+>ℹ️ Only users with the <a href = "https://help.vtex.com/en/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> role can perform tasks through VTEX DO.
 
 The tasks are listed in two tabs:
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
index e6b9b320b..eb027bc27 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-fulfillment.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-fulfillment
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-If you are interested in implementing for your business, fill out our <a href="https://vtex.com/us-en/contact/">form</a> and indicate the name of the desired product in the <code>Comments</code> section.
-</div>
+>ℹ️ If you are interested in implementing for your business, fill out our [form](https://vtex.com/us-en/contact/) and indicate the name of the desired product in the `Comments` section.
 
 [VTEX Pick and Pack](https://help.vtex.com/en/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU) is a solution to streamline stores’ fulfillment processes by optimizing orders’ picking and packing, and the last-mile delivery. The solution is composed of the [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) and **VTEX Pick and Pack Fulfillment** features, and appears in your VTEX Admin in **Apps**.
 
@@ -349,9 +347,7 @@ You can combine multiple filters to filter the information you want to see in th
 * City
 * Seller
 
-<div class = "alert alert-info">
-The filter <b>Seller</b> is visible only for the account that operates as a marketplace. <a href="https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">White label sellers</a> do not have that filter option in <b>Insights</b>.
-</div>
+>ℹ️ The filter **Seller** is visible only for the account that operates as a marketplace. [White label sellers](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) do not have that filter option in **Insights**.
 
 Besides the **Total orders** chart, there is a sequence of charts where you obtain data about _Payment methods_ and orders that were:
 
@@ -370,9 +366,7 @@ Below **Total orders**, you will find a chart about the number of orders and uni
 
 In the tab **Operation**, you will see the Picking and Packing **Order flow**, a chart with the total amount of orders distributed per day in the last seven days. The darker the blue, the more orders, the lighter the blue, the less.
 
-<div class = "alert alert-info">
-The Picking and Packing <b>Order flow</b> chart is calculated taking into account all orders of the last 7 days, and distributes them in hours, going from 0 to 23. Even if you change the period to 15 days, for example, the chart will remain fixed considering 7 days.
-</div>
+>ℹ️ The Picking and Packing **Order flow** chart is calculated taking into account all orders of the last 7 days, and distributes them in hours, going from 0 to 23. Even if you change the period to 15 days, for example, the chart will remain fixed considering 7 days.
 
 Below the **Order flow**, there is another chart with orders data filtered by picker. You will see information about:
 
@@ -463,9 +457,7 @@ To create a package, do the following:
 2. Fill in the name that will identify the package.
 3. Fill in with the package’s measures: height, width and length, using numbers only. 
 
-  <div class = "alert alert-info">
-The measurement unit is the one configured in the tab General, in <b>Units of measure</b>.
-</div>
+  >ℹ️ The measurement unit is the one configured in the tab General, in **Units of measure**.
 
 4. Click `Add`.
 
@@ -510,9 +502,7 @@ Once you are done with the printing settings, click `Save`.
 
 In this tab, you can configure a webhook to be notified about orders’ status changes and to get information about a given order. 
 
-<div class = "alert alert-info">
-For more information, see our VTEX <a href="https://developers.vtex.com/docs/guides/vtex-pick-and-pack-get-order-status-and-information-api">Pick and Pack documentation</a> for developers.
-</div>
+>ℹ️ For more information, see our VTEX [Pick and Pack documentation](https://developers.vtex.com/docs/guides/vtex-pick-and-pack-get-order-status-and-information-api) for developers.
 
 ## Users
 
@@ -563,9 +553,7 @@ To create a new _picker_, follow the steps below:
     * **Stores:** Select the environment the picker will be associated with. Each environment can have multiple [white label sellers](https://help.vtex.com/en/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) associated with it.
     * **Categories:** Select up to four categories related to the products the picker will collect.
 
-  <div class = "alert alert-info">
-The categories related to the picker optimize the algorithm when determining which picker will get the order. However, it is not a limitation, any picker can be assigned to tasks from all categories.
-</div>
+  >ℹ️ The categories related to the picker optimize the algorithm when determining which picker will get the order. However, it is not a limitation, any picker can be assigned to tasks from all categories.
 
 4. Click `Save user`.
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-insights.md b/docs/tutorials/en/vtex-pick-and-pack-insights.md
index cc0cb685e..8fb3f52d8 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-insights.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-insights.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-insights
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
-</div>
+>ℹ️ This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our [form](https://vtex.com/us-en/contact/) apontaby entering the product name in the `Comments` field.
 
 **Insights** is a VTEX Admin page that displays information about your store's performance regarding VTEX Pick and Pack.
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-last-mile.md b/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
index 5c72541ac..db4d94e17 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-last-mile.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-last-mile
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-If you are interested in implementing for your business, fill out our <a href="https://vtex.com/us-en/contact/">form</a> and indicate the name of the desired product in the <code>Comments</code> section.
-</div>
+>ℹ️ If you are interested in implementing for your business, fill out our [form](https://vtex.com/us-en/contact/) and indicate the name of the desired product in the `Comments` section.
 
 [VTEX Pick and Pack](https://content.vtex.com/en/pick-and-pack/) is a solution to streamline stores’ fulfillment processes by optimizing orders’ picking and packing, and the last-mile delivery. The solution is composed of the [VTEX Fulfillment](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) and the **Last Mile** modules. 
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-mobile.md b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
index 343c2e155..37d1422c7 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-mobile.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-mobile
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-<p>If you are already a VTEX customer and wish to adopt this functionality for your business, please contact <a href="https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Commercial Support</a>. Additional fees may apply. If you are not yet a customer but are interested in this solution, please fill out the <a href="https://vtex.com/us-en/contact/">contact form</a>.</p>
-</div>
+>ℹ️ If you are already a VTEX customer and wish to adopt this functionality for your business, please contact [Commercial Support](https://help.vtex.com/en/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Additional fees may apply. If you are not yet a customer but are interested in this solution, please fill out the [contact form](https://vtex.com/us-en/contact/).
 
 The [VTEX Pick and Pack](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) mobile app helps the picker — the person who picks and packs items in the facility — handle orders, from picking to shipping. This makes the store's order picking and delivery flow smoother and more efficient.
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-orders.md b/docs/tutorials/en/vtex-pick-and-pack-orders.md
index c8d691118..5504dcf64 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-orders.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-orders.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-orders
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
-</div>
+>ℹ️ This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our [form](https://vtex.com/us-en/contact/) apontaby entering the product name in the `Comments` field.
 
 **Orders** is a VTEX Admin page that displays information on orders placed and managed by VTEX Pick and Pack.
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-settings.md b/docs/tutorials/en/vtex-pick-and-pack-settings.md
index 4ec3db685..c34e67801 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-settings.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-settings.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-settings
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
-</div>
+>ℹ️ This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our [form](https://vtex.com/us-en/contact/) apontaby entering the product name in the `Comments` field.
 
 **Settings** is a VTEX Admin page that allows you to select the VTEX Pick and Pack settings for your store. The settings are distributed in the following tabs:
 
@@ -40,9 +38,7 @@ In this tab, you'll find the settings related to the picking of order items. Her
 
 In this section, you can define the picking strategy types you would like for your pickers.
 
-<div class = "alert alert-info">
-  Only the <strong>Wave picking</strong> strategy is currently available.
-</div>
+>ℹ️ Only the **Wave picking** strategy is currently available.
 
 ### Order Changes
 
@@ -250,9 +246,7 @@ You can add bulk SKU IDs and EANs for your products via a CSV file. To do this,
 
 You can also index the catalog to update the product list. To do this, click `Index Catalog` and then `Continue`.
 
-<div class = "alert alert-danger">
-Indexing the catalog will delete and recreate all its contents, so you could lose all your custom EAN and SKU codes.
-</div>
+>❗ Indexing the catalog will delete and recreate all its contents, so you could lose all your custom EAN and SKU codes.
 
 ## Facilities
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack-worksheets.md b/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
index 6ce73ba93..521e3de46 100644
--- a/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
+++ b/docs/tutorials/en/vtex-pick-and-pack-worksheets.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-worksheets
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our <a href="https://vtex.com/us-en/contact/">form</a> apontaby entering the product name in the <code>Comments</code> field.
-</div>
+>ℹ️ This feature is in closed beta, so only selected customers can access it now. If you want to implement it in the future, please complete our [form](https://vtex.com/us-en/contact/) apontaby entering the product name in the `Comments` field.
 
 **Worksheets** is a VTEX Admin page to manage the worksheets used by pickers to group and pick the order items in real time. Pickers can group as many orders as they like in each worksheet.
 
diff --git a/docs/tutorials/en/vtex-pick-and-pack.md b/docs/tutorials/en/vtex-pick-and-pack.md
index 0290e00db..6bc11482d 100644
--- a/docs/tutorials/en/vtex-pick-and-pack.md
+++ b/docs/tutorials/en/vtex-pick-and-pack.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-If you are interested in implementing for your business, fill out our <a href="https://vtex.com/us-en/contact/">form</a> and indicate the name of the desired product in the <code>Comments</code> section.
-</div>
+>ℹ️ If you are interested in implementing for your business, fill out our [form](https://vtex.com/us-en/contact/) and indicate the name of the desired product in the `Comments` section.
 
 **VTEX Pick and Pack** is the solution that enables merchants to manage order picking, packing, and delivery from physical stores and warehouses to customers’ addresses or [pickup points](https://help.vtex.com/en/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). All management is made in one place, providing visibility and control for merchants through the whole fulfillment process.
 
@@ -42,7 +40,5 @@ With **VTEX Pick and Pack**, merchants can also collect data and analytics on th
 * **[Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr):** Admin app for the store operator to instruct delivery drivers from their own fleet about collecting and delivering orders to customers’ address or pickup points. It includes route optimization and proof of collecting and delivering, meaning the driver can upload the customer's signature, a picture, or a note confirming the delivery was made.  
 * **Mobile Applications:** Applications for mobile devices meant exclusively for pickers and drivers, so that they fulfill their parts with no access to the store’s Admin.
 
-<div class = "alert alert-info">
-<b>Fulfillment</b> and <b>Last Mile</b> apps for pickers and drivers are available only for Android devices.
-</div>
+>ℹ️ **Fulfillment** and **Last Mile** apps for pickers and drivers are available only for Android devices.
 
diff --git a/docs/tutorials/en/web-page-performance.md b/docs/tutorials/en/web-page-performance.md
index 8a05ef0fd..f343b743d 100644
--- a/docs/tutorials/en/web-page-performance.md
+++ b/docs/tutorials/en/web-page-performance.md
@@ -15,9 +15,7 @@ legacySlug: web-page-performance
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class = "alert alert-info">
-This page is only available to stores operating with the <a href="https://help.vtex.com/en/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">New VTEX Admin</a>. To access this page and be part of the new experience, join the New VTEX Admin <a href="https://content.vtex.com/participe-do-programa-beta-en/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">Beta program</a>.
-  </div>
+>ℹ️ This page is only available to stores operating with the [New VTEX Admin](https://help.vtex.com/en/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa). To access this page and be part of the new experience, join the New VTEX Admin [Beta program](https://content.vtex.com/participe-do-programa-beta-en/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta).
 
 [PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about) is a tool developed by Google to report on the performance of a page on both mobile and desktop devices, providing suggestions on how its performance may be improved. It uses [Google's Core Web Vitals](https://web.dev/vitals/#core-web-vitals) as metrics to assess online performance. 
 
@@ -46,9 +44,7 @@ Performance metrics can be measured by two types of data:
 
 Note that you should not compare results from the two data types. They are not comparable, since they come from different sources, and serve different purposes. Know more about how each data type can be applied in Google's [How metrics are measured](https://web.dev/user-centric-performance-metrics/#how-metrics-are-measured) documentation.
 
-<div class = "alert alert-info">
-To make sure your website is reaching the recommended target for all metrics, PageSpeed Insights measures the activity of the 75th percentile of page loads, segmented across mobile and desktop devices.
-  </div>
+>ℹ️ To make sure your website is reaching the recommended target for all metrics, PageSpeed Insights measures the activity of the 75th percentile of page loads, segmented across mobile and desktop devices.
 
   ### How to use field and lab data to improve Core Web Vitals
 
@@ -73,9 +69,7 @@ The URL is displayed in a card, along with:
 
 You can browse through the added links and select which one to display on Web Page Performance, and analyze its performance metrics. By clicking on the <i class='fa-solid fa-ellipsis-vertical'></i> menu icon, it is also possible to `Copy URL` and `Visit Page` by clicking on the corresponding buttons on the URL's card.
 
-<div class = "alert alert-info">
-Google's PageSpeed Insights also shows metrics for the whole domain of the URL inserted, in case there is not enough data to show for a specific page. Meanwhile, Web Page Performance indicates data for the URL only, to make your assessment more actionable.
-  </div>
+>ℹ️ Google's PageSpeed Insights also shows metrics for the whole domain of the URL inserted, in case there is not enough data to show for a specific page. Meanwhile, Web Page Performance indicates data for the URL only, to make your assessment more actionable.
 
   ### Which URLs should you track? 
 
@@ -174,9 +168,7 @@ The Performance section of Web Page Performance includes a score which summarize
 * **Needs improvement:** from 50 to 90. The color code is orange.
 * **Poor**: below 50. The color code is red.
 
-<div class = "alert alert-warning">
-Note that performance varies a lot between stores, and is dependent on how your storefront's architecture was built. Complex storefronts, with multiple external scripts and features tend to perform with lower scores. For stores built on VTEX IO, check out <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-debugging-performance-issues">VTEX IO: Debugging Performance Issues</a>. For stores using <a href="https://www.faststore.dev/">FastStore</a>, there is an <a href="https://www.faststore.dev/releases/2022/04/22/webops">automated Lighthouse report for deploy previews</a>.
-</div>
+>⚠️ Note that performance varies a lot between stores, and is dependent on how your storefront's architecture was built. Complex storefronts, with multiple external scripts and features tend to perform with lower scores. For stores built on VTEX IO, check out [VTEX IO: Debugging Performance Issues](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-debugging-performance-issues). For stores using [FastStore](https://www.faststore.dev/), there is an [automated Lighthouse report for deploy previews](https://www.faststore.dev/releases/2022/04/22/webops).
 
 Below the score you will see the individual scores achieved by a list of Web Vitals, along with a color code that indicates its threshold. You can manually update the score, by clicking on the <i class='fa fa-refresh'></i> refresh icon.
 
diff --git a/docs/tutorials/en/what-are-layouts.md b/docs/tutorials/en/what-are-layouts.md
index 11465a3eb..d9ecc0497 100644
--- a/docs/tutorials/en/what-are-layouts.md
+++ b/docs/tutorials/en/what-are-layouts.md
@@ -19,10 +19,10 @@ __Layouts__ are responsible for determining which [placeholders](/en/tutorial/wh
 
 This is done first with the placeholder settings, that will tell you which type is used and what file will fill it. Then, in order for the layout to become functional, it must be linked to a [template](/en/tutorial/what-are-templates). Thus, the page code where the placeholder will be displayed will know exactly where the information comes from.
 
-<div class = "alert alert-warning">
-<strong>Important</strong><br>
-In order to work, each layout must be linked to a single template.
-</div>
+>⚠️ **Important**
+>
+> 
+> In order to work, each layout must be linked to a single template.
 
 ### Related articles
 - [What is CMS?](/en/faq/what-is-cms)
diff --git a/docs/tutorials/en/what-is-a-service.md b/docs/tutorials/en/what-is-a-service.md
index 9ab1fb95f..9b9000eaf 100644
--- a/docs/tutorials/en/what-is-a-service.md
+++ b/docs/tutorials/en/what-is-a-service.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 A service is an item that may come with a product, optionally and with cost. It is used to assign a value, often emotional, but also of an additional service itself to an SKU. For example, a gift packaging, a distinctive ribbon, a gift card or a product installation.
 
-<div class = "alert alert-warning">
-It's important to remember that a service is always charged. However, VTEX does not control the stock of a service. This is a responsibility of the marketplace or the seller.
-</div>
+>⚠️ It's important to remember that a service is always charged. However, VTEX does not control the stock of a service. This is a responsibility of the marketplace or the seller.
 
 If your purchased product is a Brazilian National Team Shirt, the name of your service might be __Gift Packaging___, and it might be displayed during the order flow on the screen that you choose: product, cart or service.
 
diff --git a/docs/tutorials/en/what-is-an-attachment.md b/docs/tutorials/en/what-is-an-attachment.md
index 77c5625f5..fbebeb1f8 100644
--- a/docs/tutorials/en/what-is-an-attachment.md
+++ b/docs/tutorials/en/what-is-an-attachment.md
@@ -17,9 +17,7 @@ subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 
 An attachment is the optional and cost-free customization of a product. It's used to add information to an SKU. This information may be related to a [service](/en/tutorial/what-is-a-service) or the purchased item itself.
 
-<div class = "alert alert-warning">
-VTEX does not control the stock of an attachment. This is a responsibility of the marketplace or the seller.
-</div>
+>⚠️ VTEX does not control the stock of an attachment. This is a responsibility of the marketplace or the seller.
 
 If your purchased item is a Brazilian National Team Shirt, the name of your Attachment may be __Customization__, and its keys:
 
diff --git a/docs/tutorials/en/what-is-order-configuration.md b/docs/tutorials/en/what-is-order-configuration.md
index bec25d53e..16cccf693 100644
--- a/docs/tutorials/en/what-is-order-configuration.md
+++ b/docs/tutorials/en/what-is-order-configuration.md
@@ -34,7 +34,5 @@ You must associate a [price table](https://help.vtex.com/en/tracks/prices-101--6
 
 If you configure a scenario that has no price table linked to it, it will use a default price table.
 
-<div class = "alert alert-info">
-  <p>Users need to be logged in to use Order Configuration and view the different prices based on their configurations.</p>
-</div>
+>ℹ️ Users need to be logged in to use Order Configuration and view the different prices based on their configurations.
 
diff --git a/docs/tutorials/en/what-is-the-difference-between-sales-policy-affiliate-and-seller.md b/docs/tutorials/en/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
index 9c362d7a7..e8ef1fc77 100644
--- a/docs/tutorials/en/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
+++ b/docs/tutorials/en/what-is-the-difference-between-sales-policy-affiliate-and-seller.md
@@ -45,9 +45,7 @@ Each marketplace must have a __unique affiliate identifier__.
 
 After creating an [affiliate](/en/tutorial/configuring-affiliates/), you must associate a sales policy with it. The sales policy contains the product assortment, logistics and price information that will be sent to the affiliate.
 
-<div class = "alert alert-info">
-If the marketplace configuration is made through the <a href="http://help.vtex.com/en/tutorial/configuring-a-marketplace-sales-policy/">Bridge</a> module, the affiliate will be automatically created in the OMS.
-</div>
+>ℹ️ If the marketplace configuration is made through the [Bridge](http://help.vtex.com/en/tutorial/configuring-a-marketplace-sales-policy/) module, the affiliate will be automatically created in the OMS.
 
 #### **LEAR MORE**
 
diff --git a/docs/tutorials/en/what-is-the-difference-between-unbinding-and-removing-seller-sku.md b/docs/tutorials/en/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
index b8650b04b..21a17e1d8 100644
--- a/docs/tutorials/en/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
+++ b/docs/tutorials/en/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
@@ -19,9 +19,7 @@ The products sent by a seller to the marketplace go through the [Received SKUs](
 
 If you [unbinde a seller's SKU](https://help.vtex.com/en/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX#unbinding-a-sku), it will no longer be shown as available in the marketplace. The SKU will be unbinded from the catalogue and will no longer be updated in terms of seller’s price and stocks.
 
-<div class = "alert alert-info">
-An unbinded SKU will not return to the queue for approval in <b>Received SKUs</b>, since it still exists in the marketplace's catalogue.
-</div>
+>ℹ️ An unbinded SKU will not return to the queue for approval in **Received SKUs**, since it still exists in the marketplace's catalogue.
 
 If you want to delete a seller's SKU, you must [remove the seller's SKU](https://help.vtex.com/en/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX#removing). When you remove an SKU, it is permanently deleted from the marketplace's catalogue. The removed SKU will only appear in the catalogue again if the seller resends it to **Received SKUs**.
 
diff --git a/docs/tutorials/en/what-is-the-sponsor-user.md b/docs/tutorials/en/what-is-the-sponsor-user.md
index 6a9a66ce7..2a78e7f79 100644
--- a/docs/tutorials/en/what-is-the-sponsor-user.md
+++ b/docs/tutorials/en/what-is-the-sponsor-user.md
@@ -17,9 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 Each VTEX account has a single Sponsor user – the only one who is granted full access to every section in the Admin, including critical maintenance and authorization actions.
 
-<div class = "alert alert-warning">
-The Sponsor user is not the same as the <b>Owner (Admin Super)</b>. The <b>Owner (Admin Super)</b> is a License Manager role that defines the permissions of a user in your store. It can even be assigned to multiple users.
-</div>
+>⚠️ The Sponsor user is not the same as the **Owner (Admin Super)**. The **Owner (Admin Super)** is a License Manager role that defines the permissions of a user in your store. It can even be assigned to multiple users.
 
 The Sponsor management page allows you to identify the current Sponsor user, transfer store ownership and view the activity log associated with Sponsor user actions. To access this page, navigate to **Account settings** > **Account management** > **Account**, scroll down to the Contact section and click `Sponsor management`.
 
diff --git a/docs/tutorials/en/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md b/docs/tutorials/en/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
index cda623854..a7591e3ba 100644
--- a/docs/tutorials/en/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
+++ b/docs/tutorials/en/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
@@ -15,9 +15,7 @@ legacySlug: what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignore
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  VTEX has two search options - Legacy CMS Portal search and VTEX Intelligent Search. This article refers to the Legacy CMS Portal search. To learn more about  VTEX Intelligent Search, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
-</div>
+>⚠️ VTEX has two search options - Legacy CMS Portal search and VTEX Intelligent Search. This article refers to the Legacy CMS Portal search. To learn more about  VTEX Intelligent Search, see <a href = "https://help.vtex.com/en/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">this track</a>.
 
 If you need to use in your products words that perhaps are not important for the search engine, several good practices exist:
 
diff --git a/docs/tutorials/en/white-label-seller.md b/docs/tutorials/en/white-label-seller.md
index 53ba8b749..d1cdb1382 100644
--- a/docs/tutorials/en/white-label-seller.md
+++ b/docs/tutorials/en/white-label-seller.md
@@ -30,18 +30,14 @@ A [franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-acco
 
 A franchise account is of strategic use for sales growth operations, such as the integration of physical stores, considering the opportunity of inheriting a catalog already registered on the VTEX platform. Learn more in [What is a franchise account](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
-<div class = "alert alert-info">
-All franchise accounts are by default white label sellers of the main account. Even though white label seller and franchise account are related concepts, they are not equivalent because white label seller is a type of seller, and franchise account is a type of account.
-</div>
+>ℹ️ All franchise accounts are by default white label sellers of the main account. Even though white label seller and franchise account are related concepts, they are not equivalent because white label seller is a type of seller, and franchise account is a type of account.
 
 A standard account may act as a white label seller of another VTEX store, case in which the marketplace does not inform the customer who is the seller in charge of the order fulfillment. A franchise account can also act as a normal seller of a marketplace other than the main account. Summing up:
 
 - **Account:** Can be a franchise account or a standard account.
 - **Seller:** Can be regular or white label.
 
-<div class = "alert alert-info">
-To add a white label seller, this model must be provided for in your contract with VTEX. In case you need to make changes to your contract, please contact your VTEX sales representative and submit a request to add a franchise account through our Support. Every franchise account is created as a white label seller. It is not possible to change the seller type after its creation.
-  </div>
+>ℹ️ To add a white label seller, this model must be provided for in your contract with VTEX. In case you need to make changes to your contract, please contact your VTEX sales representative and submit a request to add a franchise account through our Support. Every franchise account is created as a white label seller. It is not possible to change the seller type after its creation.
 
 ### Learn more
 
diff --git a/docs/tutorials/en/white-label-sellers-selection.md b/docs/tutorials/en/white-label-sellers-selection.md
index 3df335615..e58cc7c9f 100644
--- a/docs/tutorials/en/white-label-sellers-selection.md
+++ b/docs/tutorials/en/white-label-sellers-selection.md
@@ -22,9 +22,7 @@ There are two types of sellers on the VTEX platform:
 - **Common seller:** The seller is visible for customers in the marketplace and can be chosen by the customer during their shopping experience.
 - **[White label seller](https://help.vtex.com/en/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa):** The seller remains unknown to the customer during their shopping experience and is automatically selected by the VTEX platform to deliver the order. 
 
-<div class = "alert alert-info">
-At VTEX, a franchise account is associated with a main account, and it acts as a white label seller of the main account. This business model is strategic for retailers who want to connect physical stores to their digital sales channel. Learn more in <a href="https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">What is a franchise account?</a>.
-</div>
+>ℹ️ At VTEX, a franchise account is associated with a main account, and it acts as a white label seller of the main account. This business model is strategic for retailers who want to connect physical stores to their digital sales channel. Learn more in [What is a franchise account?](https://help.vtex.com/en/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
 When the customer browses the marketplace, either the window display or the shopping cart, the seller information regarding item availability and shipping options may vary, depending on the marketplace knowing or not the buyer's location. Therefore, this article is divided into the following:
 
@@ -39,9 +37,7 @@ When customers browse the marketplace, they expect to view products that can be
 - [Window display when customer location is not defined.](#window-display-when-customer-location-is-not-defined)
 - [Window display when customer location is defined.](#window-display-when-customer-location-is-defined)
 
-<div class = "alert alert-info">
-During the window display stage of the shopping experience, the VTEX platform does not consider the sellers' shipping options. This only happens when the customer enters the address at checkout. However, the price and availability presented in the window display may change when completing the purchase.
-</div>
+>ℹ️ During the window display stage of the shopping experience, the VTEX platform does not consider the sellers' shipping options. This only happens when the customer enters the address at checkout. However, the price and availability presented in the window display may change when completing the purchase.
 
 ### Window display when customer location is not defined
 
@@ -79,9 +75,7 @@ After filtering all sellers based on the criteria above, up to six sellers will
 - [Delivery](#shipping-method-delivery): the customer receives the order at their address.
 - [Pickup](#shipping-method-pickup): the customer picks up the order from a [pickup point](https://help.vtex.com/en/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R).
 
-<div class = "alert alert-info">
-By default, from a total of up to twelve sellers, up to six do delivery and up to six offer pickup. However, if less than six sellers meet the criteria for one shipping method, the other category may list more than six sellers. For example, if there are only five sellers for order delivery, the pickup list may have seven sellers, so that the total adds up to twelve sellers.
-</div>
+>ℹ️ By default, from a total of up to twelve sellers, up to six do delivery and up to six offer pickup. However, if less than six sellers meet the criteria for one shipping method, the other category may list more than six sellers. For example, if there are only five sellers for order delivery, the pickup list may have seven sellers, so that the total adds up to twelve sellers.
 
 #### Shipping method: delivery
 
@@ -96,13 +90,12 @@ The selection of up to six white label sellers for delivery shipping consists of
 6. Based on the selection of sellers covering the shopping cart, the VTEX platform calculates the combinations with the lowest number of sellers.
 7. Out of these combinations, a list of maximum six sellers is made for delivery shipping.
 
-<div class = "alert alert-info">
-During selection, different sellers may come to a tie. In that case, the selection is divided into two criteria in order to choose:
-  <ul>
-    <li>Up to three sellers with the best cost.</li>
-    <li>Up to three sellers with the best time.</li>
-  </ul>
-</div>
+>ℹ️ During selection, different sellers may come to a tie. In that case, the selection is divided into two criteria in order to choose:
+>
+> * Up to three sellers with the best cost.
+>
+> * Up to three sellers with the best time.
+>   
 
 If there is a tie between sellers on the best cost or time, the tiebreaker criterion is the seller with the highest quantity of SKUs in stock.
 
@@ -168,9 +161,7 @@ The selection of up to six sellers is made for the customer to get all shopping
     - **Best time:** Sellers which make the products available for pickup in the shortest time.
     - **Best cost:** Sellers which offer the cheapest prices for order pickup.
 
-<div class = "alert alert-info">
-When there is a tie between the best cost and best time, the tiebreak criterion is the seller with the highest quantity of SKUs in stock.
-</div>
+>ℹ️ When there is a tie between the best cost and best time, the tiebreak criterion is the seller with the highest quantity of SKUs in stock.
 
 ##### Example for pickup shipping
 
diff --git a/docs/tutorials/es/accessing-the-beta-environment.md b/docs/tutorials/es/accessing-the-beta-environment.md
index 1de99affd..6ef4cce8d 100644
--- a/docs/tutorials/es/accessing-the-beta-environment.md
+++ b/docs/tutorials/es/accessing-the-beta-environment.md
@@ -17,9 +17,7 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 
 En VTEX, todas las tiendas disponen de un entorno beta. En este entorno, los usuarios de la plataforma, ya sean retailers, desarrolladores u otras personas con acceso, pueden llevar a cabo pruebas para validar nuevas configuraciones o versiones de aplicaciones/servicios antes de implementar cambios en el entorno donde los clientes realizan sus compras, conocido como entorno de producción (stable).
 
-<div class = "alert alert-info">
-El entorno beta es una reproducción exacta del entorno de producción (stable), que incluye todos los datos y configuraciones de la tienda.
-</div>
+>ℹ️ El entorno beta es una reproducción exacta del entorno de producción (stable), que incluye todos los datos y configuraciones de la tienda.
 
 De esta manera, **cualquier modificación de datos en el entorno beta afecta a los datos en el entorno stable**.
 
@@ -45,6 +43,4 @@ Para acceder al entorno beta de tu tienda debes habilitar la cookie <code>vtex-c
 </li>
 </ol>
 
-<div class = "alert alert-info">
-Para restaurar la tienda a su entorno principal, accede nuevamente a la pantalla DevTools de tu navegador y elimina la cookie vtex-commerce-env. Actualiza la página una vez más para volver al entorno de producción <b>stable</b>.
-</div>
+>ℹ️ Para restaurar la tienda a su entorno principal, accede nuevamente a la pantalla DevTools de tu navegador y elimina la cookie vtex-commerce-env. Actualiza la página una vez más para volver al entorno de producción **stable**.
diff --git a/docs/tutorials/es/adding-collections-cms.md b/docs/tutorials/es/adding-collections-cms.md
index b11ddf352..9a9598e23 100644
--- a/docs/tutorials/es/adding-collections-cms.md
+++ b/docs/tutorials/es/adding-collections-cms.md
@@ -15,9 +15,7 @@ legacySlug: registrar-una-coleccion
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p>Existen dos formas de configurar colecciones, mediante el Portal CMS Legado o utilizando el módulo <a href="https://help.vtex.com/es/tutorial/registrar-colecciones-beta--yJBHqNMViOAnnnq4fyOye">Colecciones Beta</a>. Este artículo se refiere a la configuración de colecciones mediante el Portal CMS Legado.</p>
-</div>
+>⚠️ Existen dos formas de configurar colecciones, mediante el Portal CMS Legado o utilizando el módulo [Colecciones Beta](https://help.vtex.com/es/tutorial/registrar-colecciones-beta--yJBHqNMViOAnnnq4fyOye). Este artículo se refiere a la configuración de colecciones mediante el Portal CMS Legado.
 
 Realice el siguiente paso a paso para registrar una nueva colección:  
 
diff --git a/docs/tutorials/es/adding-sku-specifications-or-fields.md b/docs/tutorials/es/adding-sku-specifications-or-fields.md
index bdcb454e3..ac48349db 100644
--- a/docs/tutorials/es/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/es/adding-sku-specifications-or-fields.md
@@ -33,9 +33,7 @@ En este artículo, explicamos cómo funciona la herencia de especificaciones que
         * [Registro del SKU](#registro-del-sku)
         * [Plantilla](#plantilla)
 
-<div class = "alert alert-info">
-  <p>Para crear una especificación de SKU con la <strong>API Catálogo</strong>, sigue la guía para desarrolladores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> (Cómo crear una especificación).</p>
-</div>
+>ℹ️ Para crear una especificación de SKU con la **API Catálogo**, sigue la guía para desarrolladores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) (Cómo crear una especificación).
 
 ## Herencia de especificaciones de SKU
 
@@ -55,9 +53,7 @@ En las secciones a continuación, podrás ver el paso a paso completo.
 
 ### Crear un campo de SKU
 
-<div class = "alert alert-warning">
-  <p>Una vez creados, los campos del SKU no pueden borrarse. Si se inactiva un campo, todos los SKU que están en la categoría quedarán inactivos hasta que el campo vuelva a reactivarse. Una de las causas por las que el SKU no aparece en el sitio web puede ser que no se haya rellenado una especificación en el registro, ya que esto deja al SKU inactivo.</p>
-</div>
+>⚠️ Una vez creados, los campos del SKU no pueden borrarse. Si se inactiva un campo, todos los SKU que están en la categoría quedarán inactivos hasta que el campo vuelva a reactivarse. Una de las causas por las que el SKU no aparece en el sitio web puede ser que no se haya rellenado una especificación en el registro, ya que esto deja al SKU inactivo.
 
 Para crear un campo del SKU, sigue las instrucciones a continuación:
 
@@ -65,9 +61,7 @@ Para crear un campo del SKU, sigue las instrucciones a continuación:
 2. Haz clic en **Categorías**.
 3. Haz clic en la categoría asociada al grupo de especificaciones en el que deseas crear un campo del SKU.
 
-  <div class = "alert alert-warning">
-    <p>Verás que, al crear un campo en un nivel de categoría superior, la especificación aparecerá en todos los niveles de categoría inferiores.</p>
-  </div>
+  >⚠️ Verás que, al crear un campo en un nivel de categoría superior, la especificación aparecerá en todos los niveles de categoría inferiores.
 
 3. Haz clic en `Acciones` <i class="fas fa-angle-down"></i>.
 4. Haz clic en `Campo (SKU)`.
@@ -138,9 +132,7 @@ Los **valores** de los campos del SKU variarán según el tipo de campo elegido:
 
 ![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/157aeb729b88c61a3341697b60008c7c/es-sku-spec-2.gif)
 
-<div class = "alert alert-info">
-  <p>Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción <strong>Activo</strong>.</p>
-</div>
+>ℹ️ Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción **Activo**.
 
 #### Obtener o editar valores registrados
 
diff --git a/docs/tutorials/es/adding-specifications-or-product-fields.md b/docs/tutorials/es/adding-specifications-or-product-fields.md
index e87f6d0cd..c6cc453c8 100644
--- a/docs/tutorials/es/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/es/adding-specifications-or-product-fields.md
@@ -33,9 +33,7 @@ En este artículo, te explicamos cómo funciona la herencia de las especificacio
         * [Registro de producto](#registro-de-producto)
         * [Plantilla](#plantilla)
 
-<div class = "alert alert-info">
-  <p>Para crear una especificación de producto con la <strong>API Catálogo</strong>, sigue la guía para desarrolladores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> (Cómo crear una especificación).</p>
-</div>
+>ℹ️ Para crear una especificación de producto con la **API Catálogo**, sigue la guía para desarrolladores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) (Cómo crear una especificación).
 
 ## Herencia de especificaciones de producto
 
@@ -148,9 +146,7 @@ Sin embargo, para los campos **Combo**, **Radio** y **Checkbox** es necesario re
 
 ![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/35fc1b6e4edc189e4d4195d35f777514/ES_ProdutoGif_2_Alterado.gif)
 
-<div class = "alert alert-info">
-  <p>Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción <strong>Activo</strong>.</p>
-</div>
+>ℹ️ Si estás registrando los primeros valores de un campo, deberás regresar al formulario de ese campo específico y seleccionar la opción **Activo**.
 
 #### Obtener o editar valores registrados
 
diff --git a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
index b8719b824..1933e3d0f 100644
--- a/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/es/advertising-with-vtex-ad-network-beta.md
@@ -15,9 +15,7 @@ legacySlug: anunciar-con-vtex-ad-network-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 [VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) te permite anunciar productos de tu marca en storefronts de retailers VTEX que tengan tu producto en su catálogo.
 
@@ -35,9 +33,7 @@ Si ya eres un anunciante de **VTEX Ad Network**, en este artículo puedes ver de
 
 Para crear una [campaña de VTEX Ad Network](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanas), sigue los pasos a continuación:
 
-<div class = "alert alert-info">
-Actualmente, VTEX cuenta con un único formato de anuncio: resultados de búsqueda. Consulta más información sobre este <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#formato-de-anuncio">formato de anuncio</a>.
-</div>
+>ℹ️ Actualmente, VTEX cuenta con un único formato de anuncio: resultados de búsqueda. Consulta más información sobre este [formato de anuncio](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#formato-de-anuncio).
 
 1. En el Admin VTEX, accede a __Storefront > Ad Network > Campañas__.
 2. Haz clic en `Crear campaña`.
@@ -121,9 +117,7 @@ A continuación, se muestra una tabla con la información de cada campaña:
 - **Presupuesto:** presupuesto total.
 - **Presupuesto restante:** presupuesto que aún está disponible.
 
-<div class = "alert alert-info">
-Consulta más información sobre <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ventana-de-atribucion">atribución de ventas a anuncios</a>.
-</div>
+>ℹ️ Consulta más información sobre [atribución de ventas a anuncios](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ventana-de-atribucion).
 
 Puedes filtrar los datos de la tabla utilizando las siguientes opciones:
 
@@ -153,7 +147,5 @@ Debajo de los datos agregados, se muestra una tabla con la información del dese
 - **ROAS:** retorno de inversión publicitaria.
 - **Presupuesto restante:** presupuesto que aún está disponible actualmente.
 
-<div class = "alert alert-info">
-Consulta más información sobre <a href="https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ventana-de-atribucion">atribución de ventas a anuncios</a>.
-</div>
+>ℹ️ Consulta más información sobre [atribución de ventas a anuncios](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#ventana-de-atribucion).
 
diff --git a/docs/tutorials/es/affiliates-program-app.md b/docs/tutorials/es/affiliates-program-app.md
index ace15483f..9e643741d 100644
--- a/docs/tutorials/es/affiliates-program-app.md
+++ b/docs/tutorials/es/affiliates-program-app.md
@@ -15,9 +15,7 @@ legacySlug: aplicacion-affiliates-program
 subcategory: 6GWaAkVqXQYN79ilMgUsPr
 ---
 
-<div class = "alert alert-info">
-<b>Affiliates program</b> es una aplicación solo compatible con las tiendas <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, y no está disponible para las tiendas que utilizan <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS - Portal Legado</a> o <a href="https://faststore.dev/tutorials/cms/0#vtex-headless-cms">Headless CMS</a>. Para instalar y configurar la app en tu tienda VTEX, consulta la guía del desarrollador <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app">Affiliates Program app</a>.
-</div>
+>ℹ️ **Affiliates program** es una aplicación solo compatible con las tiendas [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), y no está disponible para las tiendas que utilizan [CMS - Portal Legado](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) o [Headless CMS](https://faststore.dev/tutorials/cms/0#vtex-headless-cms). Para instalar y configurar la app en tu tienda VTEX, consulta la guía del desarrollador [Affiliates Program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app).
 
 En la aplicación **Affiliates Program**, un afiliado es alguien que se asocia con tu tienda VTEX para promover las ventas a cambio de una comisión. El término es, por tanto, diferente del [concepto habitual de afiliado en VTEX](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0).
 
@@ -48,9 +46,7 @@ La **página del perfil del afiliado** es una interfaz a través de la cual pued
 
 La página de **registro** permite que los interesados en convertirse en afiliados completen sus datos para solicitar el registro en su tienda VTEX.
 
-<div class = "alert alert-info">
-Las páginas de afiliación son personalizables. Para más información, consulta la guía del desarrollador <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app">Affiliates program app</a>.
-</div>
+>ℹ️ Las páginas de afiliación son personalizables. Para más información, consulta la guía del desarrollador [Affiliates program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app).
 
 ### Páginas en el Admin VTEX
 
@@ -127,9 +123,7 @@ En la parte superior de la página, verás las siguientes métricas sobre los pe
 - **Total del pedido:** suma de los valores del pedido, realizada a partir del precio de los ítems y sin incluir los gastos de envío.
 - **Total de la comisión del pedido:** suma de los valores de las comisiones de los afiliados sobre los pedidos.
 
-<div class = "alert alert-info">
-Para seguir el flujo de un pedido, haz clic en el <code>ID del pedido</code>. De este modo, se te redirigirá a <b>Pedidos > Todos los pedidos</b> en el Admin VTEX.
-</div> 
+>ℹ️ Para seguir el flujo de un pedido, haz clic en el `ID del pedido`. De este modo, se te redirigirá a **Pedidos > Todos los pedidos** en el Admin VTEX. 
 
 ### Buscar pedidos
 
@@ -195,9 +189,7 @@ Para exportar una plantilla de comisiones por SKU con extensión .CSV, en la par
 
 El archivo se enviará al email del [usuario](https://help.vtex.com/es/tutorial/gerenciando-usuarios--tutorials_512) conectado.
 
-<div class = "alert alert-info">
-El contenido exportado se refiere a las comisiones de los SKU de la lista en el momento de la exportación. Si algún filtro está activo, solo se exportarán las comisiones de SKU seleccionadas.
-</div>
+>ℹ️ El contenido exportado se refiere a las comisiones de los SKU de la lista en el momento de la exportación. Si algún filtro está activo, solo se exportarán las comisiones de SKU seleccionadas.
 
 ### Importar comisiones
 
@@ -213,9 +205,7 @@ Comprueba que aparece el siguiente mensaje:
 
 El nombre del archivo agregado aparecerá junto al campo `Última importación`.
 
-<div class = "alert alert-info">
-Puedes identificar la fecha de importación y el usuario que realizó la acción pasando el cursor por encima del símbolo <code>?</code> debajo de `Última importación`.
-</div>
+>ℹ️ Puedes identificar la fecha de importación y el usuario que realizó la acción pasando el cursor por encima del símbolo `?` debajo de `Última importación`.
 
 ### Descargar la última importación
 
diff --git a/docs/tutorials/es/all-orders.md b/docs/tutorials/es/all-orders.md
index f6ba9d8ff..acd98deae 100644
--- a/docs/tutorials/es/all-orders.md
+++ b/docs/tutorials/es/all-orders.md
@@ -15,9 +15,7 @@ legacySlug: lista-de-pedidos-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-<div class = "alert alert-info">
-Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
-</div>
+>ℹ️ Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 La página **Todos los pedidos** permite a los administradores de la tienda hacer seguimiento de los pedidos de su tienda y extraer información para la gestión inteligente de su negocio. Para acceder a la página, en el menú del Admin VTEX, haz clic en **Pedidos > Todos los pedidos**. En esta página puedes: 
 
diff --git a/docs/tutorials/es/analytics.md b/docs/tutorials/es/analytics.md
index 7a6e6f232..39fd0a63b 100644
--- a/docs/tutorials/es/analytics.md
+++ b/docs/tutorials/es/analytics.md
@@ -24,9 +24,7 @@ A continuación se indican los pasos necesarios para acceder a la página:
 1. En el Admin VTEX, accede a **Storefront**, o escribe **Storefront** en la barra de búsqueda en la parte superior de la página.
 2. En __Intelligent Search__, haz clic en __Analytics__. 
 
-<div class = "alert alert-info">
-  <p>La página <strong>Analytics</strong> es nativa en VTEX Intelligent Search. No se puede deshabilitar en el Admin.</p>
-</div>
+>ℹ️ La página **Analytics** es nativa en VTEX Intelligent Search. No se puede deshabilitar en el Admin.
 
 ## Datos
 
@@ -72,9 +70,7 @@ Para exportar un informe en formato CSV, debe seguir los pasos que se indican a
 5. Espere a que el archivo esté disponible para su descarga. Salir de esta página no interrumpe el proceso. 
 6. Haga clic en `Descargar`. 
 
-<div class = "alert alert-info">
-  <p>El archivo permanece disponible para descarga durante 48 horas.</p>
-</div>
+>ℹ️ El archivo permanece disponible para descarga durante 48 horas.
 
 El informe CSV descargado tiene dos tablas. La primera tabla, que se muestra a continuación, contiene información sobre los términos de búsqueda y las métricas de embudo (desde la columna **ProductsClick** hasta la columna **ProductsSold**), si se ha seleccionado esa opción.
 
diff --git a/docs/tutorials/es/application-keys.md b/docs/tutorials/es/application-keys.md
index d85f7faba..37bf2921b 100644
--- a/docs/tutorials/es/application-keys.md
+++ b/docs/tutorials/es/application-keys.md
@@ -45,9 +45,7 @@ En la página **Claves de aplicación** puedes gestionar las claves de aplicaci
 
 Para acceder a esta página, en la barra superior del Admin VTEX, haz clic en el **avatar de tu perfil** (marcado con la inicial de tu email) y luego en **Configuración de la cuenta** > **Claves de aplicación**.
 
-<div class = "alert alert-info">
- <p>Consulta este artículo para saber más sobre <a href="https://help.vtex.com/es/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm">buenas prácticas para el uso de claves de aplicación.</p></a>
-</div>
+>ℹ️ Consulta este artículo para saber más sobre [buenas prácticas para el uso de claves de aplicación.](https://help.vtex.com/es/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm)
 
 ## Generar claves de aplicación internas
 
diff --git a/docs/tutorials/es/audit.md b/docs/tutorials/es/audit.md
index 0ace769e5..aa30a6a08 100644
--- a/docs/tutorials/es/audit.md
+++ b/docs/tutorials/es/audit.md
@@ -38,9 +38,7 @@ Para consultar un evento utilizando los filtros disponibles en Audit, sigue esto
 2. En el menú **Aplicación** dentro de la sección **Filtros**, selecciona la aplicación relacionada con la consulta.
 3. En el menú **Fecha**, escoge una de las fechas predefinidas para la consulta. Si prefieres definir el intervalo de fechas exacto, activa la opción de usar una fecha **Personalizada **y selecciona la fecha de **Inicio** y **Fin** para la consulta.
 
-   <div class= "alert alert-info">
-     <p>Solo se almacenan los registros de los últimos tres meses.</p>
-   </div>
+   >ℹ️ Solo se almacenan los registros de los últimos tres meses.
 
 4. Si lo desea, añada un filtro por Acción. Para ello, en el campo situado junto a `Acción debe ser`, escriba el nombre de la acción y pulse `Enter`. Puede introducir más de un valor pulsando `Enter` después de cada selección. Compruebe el nombre de cada acción en [Eventos disponibles en Audit](https://help.vtex.com/es/tutorial/eventos-disponibles-en-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 5. Puedes agregar filtros más específicos para consultar eventos con más precisión haciendo clic en el botón `Agregar filtro`.
@@ -58,9 +56,7 @@ Para consultar un evento utilizando los filtros disponibles en Audit, sigue esto
 
     Consulta la sección [Resultados](#resultados) para entender la presentación de los eventos.
 
-<div class= "alert alert-warning">
-  <p>Los resultados de consulta corresponden exactamente al contenido ingresado en la casilla del filtro. Para evitar resultados inesperados, comprueba que no se hayan ingresado espacios adicionales en los términos de consulta.</p>
-</div>
+>⚠️ Los resultados de consulta corresponden exactamente al contenido ingresado en la casilla del filtro. Para evitar resultados inesperados, comprueba que no se hayan ingresado espacios adicionales en los términos de consulta.
 
 Si lo deseas, puedes compartir la consulta con otro usuario haciendo clic en `Compartir consulta` en la parte superior derecha de la página. El enlace a la búsqueda de Audit se copiará en su portapapeles.
 
@@ -131,7 +127,5 @@ Esta pestaña contiene la siguiente información:
 | Periodo | Fecha de inicio y fin del periodo seleccionado para la consulta. |
 | Rehacer consulta | Botón que permite repetir la consulta. |
 
-<div class= "alert alert-warning">
-  <p>Solo se almacenan 50 consultas en la pestaña <strong>Últimas consultas</strong>. Si deseas guardar consultas por encima de límite, agrégalas a los favoritos de tu navegador.</p>
-</div>
+>⚠️ Solo se almacenan 50 consultas en la pestaña **Últimas consultas**. Si deseas guardar consultas por encima de límite, agrégalas a los favoritos de tu navegador.
 
diff --git a/docs/tutorials/es/autocomplete.md b/docs/tutorials/es/autocomplete.md
index 430edca19..644627932 100644
--- a/docs/tutorials/es/autocomplete.md
+++ b/docs/tutorials/es/autocomplete.md
@@ -16,9 +16,7 @@ subcategory: 30Kdgc6wJkMWgcXLB8mGr7
 ---
 
 
-<div class = "alert alert-warning">
-    Autocomplete es una herramienta que ya está activa en VTEX Intelligent Search. No es posible desactivarla en el Admin.
-    </div>
+>⚠️ Autocomplete es una herramienta que ya está activa en VTEX Intelligent Search. No es posible desactivarla en el Admin.
 
 Autocomplete funciona según la información obtenida a través del historial de búsqueda de términos relacionados con el Catálogo. Estos resultados se muestran en cuatro listas diferentes, que pueden estar juntas o separadas, dependiendo de la interacción con el cliente. Las secciones son:
 
@@ -36,19 +34,14 @@ Durante la interacción con la barra de búsqueda, VTEX Intelligent Search inmed
 
 Cuando el usuario comienza a escribir, el sistema muestra las Sugerencias de búsqueda y Sugerencias de productos y elimina las listas anteriores.
 
-<div class = "alert alert-info">
-  <p>La información de las secciones <b>Términos más buscados</b> y <b>Sugerencia de búsquedas</b> es actualizada diariamente. Para la actualización, se utilizan los datos de los últimos 14 días de interacción de los clientes con la búsqueda.</p>
-  </div>
+>ℹ️ La información de las secciones **Términos más buscados** y **Sugerencia de búsquedas** es actualizada diariamente. Para la actualización, se utilizan los datos de los últimos 14 días de interacción de los clientes con la búsqueda.
 
 De esta forma, es posible proporcionar al cliente una experiencia de búsqueda más fluida y personalizada. Así puede ver el resultado rápidamente, además de recibir sugerencias basadas en su búsqueda. 
 
 Otra ventaja para el administrador de la tienda es el aumento de conversión, que es el resultado de la dinámica de facilidad de uso y experiencia.
 
-<div class = "alert alert-info">
-  <p>Autocomplete ofrece sugerencias de búsqueda incluso cuando la tienda es nueva y aún no muestra datos de interacciones con los clientes, como clics y búsquedas.
-    En este caso, la funcionalidad genera sugerencias de búsqueda a partir de un algoritmo que extrae palabras clave del catálogo, productos, marcas y categorías registradas en la tienda.
-</p>
-  </div>
+>ℹ️ Autocomplete ofrece sugerencias de búsqueda incluso cuando la tienda es nueva y aún no muestra datos de interacciones con los clientes, como clics y búsquedas.
+>     En este caso, la funcionalidad genera sugerencias de búsqueda a partir de un algoritmo que extrae palabras clave del catálogo, productos, marcas y categorías registradas en la tienda.
 
 ## Términos más buscados
 
diff --git a/docs/tutorials/es/b2b-checkout-settings.md b/docs/tutorials/es/b2b-checkout-settings.md
index da228c04b..c3a1d6c89 100644
--- a/docs/tutorials/es/b2b-checkout-settings.md
+++ b/docs/tutorials/es/b2b-checkout-settings.md
@@ -63,9 +63,7 @@ Sigue las instrucciones a continuación para personalizar el proceso de checkout
 <li>Al activar <code>Mostrar el botón Crear una cotización</code>, se agregará el botón <code>Crear una cotización</code>  en el checkout, lo que permite crear un presupuesto utilizando el contenido actual del carrito.</li>
 </ol>
 
-<div class = "alert alert-info">
-Solo se debe activar el botón <code>Crear una cotización</code> si tu tienda tiene instalada la aplicación B2B Quotes & Carts. Para más información consulta  <a href="https://developers.vtex.com/docs/apps/vtex.b2b-quotes">B2B Quotes & Carts</a>.
-</div>
+>ℹ️ Solo se debe activar el botón `Crear una cotización` si tu tienda tiene instalada la aplicación B2B Quotes & Carts. Para más información consulta  [B2B Quotes & Carts](https://developers.vtex.com/docs/apps/vtex.b2b-quotes).
 
 <ol start="4">
 <li>Haz clic en <code>Guardar</code>.</li>
diff --git a/docs/tutorials/es/best-practices-against-virtual-attacks.md b/docs/tutorials/es/best-practices-against-virtual-attacks.md
index 6992ef0d4..d8f259263 100644
--- a/docs/tutorials/es/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/es/best-practices-against-virtual-attacks.md
@@ -22,9 +22,7 @@ VTEX cuenta con varias protecciones contra posibles ataques a las tiendas. Sin e
 - [reCAPTCHA v3 en el checkout](#recaptcha-v3-en-el-checkout)
 - [Desactivar el inicio de sesión con contraseña](#desactivar-el-inicio-de-sesión-con-contrasena)
 
-<div class = "alert alert-info">
-Las medidas mencionadas en esta guía no eliminan por completo la posibilidad de ataques, pero sí pueden disminuir las probabilidades de que ocurran si se aplican adecuadamente.
-</div>
+>ℹ️ Las medidas mencionadas en esta guía no eliminan por completo la posibilidad de ataques, pero sí pueden disminuir las probabilidades de que ocurran si se aplican adecuadamente.
 
 ## Antifraude
 
@@ -48,9 +46,7 @@ Recomendamos utilizar [reCAPTCHA v3](https://help.vtex.com/es/tutorial/using-rec
 
 Aprende a configurar esta validación en el checkout de tu tienda en [reCAPTCHA en el checkout](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP). Para implementar reCAPTCHA v3 en una tienda VTEX, consulta la guía de desarrolladores [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
 
-<div class = "alert alert-info">
-La validación por reCAPTCHA también está activada de forma predeterminada en el flujo de <a href=tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes>registro de tarjetas</a> de los clientes de la tienda; por lo tanto, no es necesario que la tienda la configure.
-</div>
+>ℹ️ La validación por reCAPTCHA también está activada de forma predeterminada en el flujo de <a href=tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes>registro de tarjetas</a> de los clientes de la tienda; por lo tanto, no es necesario que la tienda la configure.
 
 ## Configuración de orderForm
 
diff --git a/docs/tutorials/es/best-practices-application-keys.md b/docs/tutorials/es/best-practices-application-keys.md
index fc9a6c9ab..e009d23c0 100644
--- a/docs/tutorials/es/best-practices-application-keys.md
+++ b/docs/tutorials/es/best-practices-application-keys.md
@@ -17,9 +17,7 @@ subcategory: 6uJgdHqWf1Mo0rUfgxseTn
 
 VTEX dispone de varias API para que los clientes y partners puedan desarrollar integraciones altamente personalizables con la plataforma.  Las [claves de aplicación](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) se utilizan para proporcionar acceso seguro a los datos consumidos por las integraciones, sin exponer la cuenta a usuarios o aplicaciones no autorizados.
 
-<div class = "alert alert-info">
-Este tipo de credencial se utiliza para la autenticación de la identidad a través de la API.
-</div>
+>ℹ️ Este tipo de credencial se utiliza para la autenticación de la identidad a través de la API.
 
 El manejo inadecuado de las [claves de aplicación](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) puede generar fugas y, en consecuencia, situaciones de acceso indebido. A continuación, puedes ver las buenas prácticas que recomendamos para la gestión de estas credenciales que puedes implementar para aumentar la seguridad de tu tienda.
 
diff --git a/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md b/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md
index 6bd5cf3da..a4ced4c3b 100644
--- a/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md
+++ b/docs/tutorials/es/best-practices-for-the-success-of-your-vtex-store.md
@@ -30,9 +30,7 @@ Este artículo presenta algunas de las principales prácticas para que gestiones
     * [Participa en VTEX Community](#participa-en-vtex-community)
     * [Conoce las mejores prácticas en tickets de soporte VTEX](#conoce-las-mejores-practicas-en-tickets-de-soporte-vtex)
 
-<div class = "alert alert-info">
-<b>Agencias partners</b><p>Existen varias agencias y partners de implementación que han sido certificados por VTEX debido a su demostrada excelencia y fiabilidad en proyectos realizados con la plataforma. Por lo tanto, ya sea para una implementación eficiente, una arquitectura de tienda personalizada o para obtener apoyo continuo en infraestructura, recomendamos contratar agencias partners. Para conocer a nuestros partners, accede al <a href="https://partnerportal.vtex.com/parceiros">Partner Portal</a> (solamente en portugués) o a <a href="http://vtex.com">vtex.com</a> (otros idiomas).</p>
-</div>
+>ℹ️ **Agencias partners**Existen varias agencias y partners de implementación que han sido certificados por VTEX debido a su demostrada excelencia y fiabilidad en proyectos realizados con la plataforma. Por lo tanto, ya sea para una implementación eficiente, una arquitectura de tienda personalizada o para obtener apoyo continuo en infraestructura, recomendamos contratar agencias partners. Para conocer a nuestros partners, accede al [Partner Portal](https://partnerportal.vtex.com/parceiros) (solamente en portugués) o a [vtex.com](http://vtex.com) (otros idiomas).
 
 ## Desempeño y seguridad
 
@@ -50,9 +48,7 @@ Los principales beneficios de elaborar y mantener actualizada la documentación
 * **Actuación rápida en problemas de seguridad:** solucionar problemas de seguridad o vulnerabilidades es más rápido cuando se comparte la documentación de la arquitectura.
 * **Optimización del soporte:** cuando se requiere asistencia de nuestro equipo de soporte o de terceros, compartir la documentación de la arquitectura agiliza la comunicación entre las partes y aumenta la eficiencia de su actuación.
 
-<div class = "alert alert-info">
-Para documentar la arquitectura de la tienda, visita la página <a href="https://developers.vtex.com/docs/guides">Get started</a> en nuestro portal para desarrolladores y explora el <a href="https://assets.vtex.com/4524045/">framework interactivo</a> de la plataforma VTEX.
-</div>
+>ℹ️ Para documentar la arquitectura de la tienda, visita la página [Get started](https://developers.vtex.com/docs/guides) en nuestro portal para desarrolladores y explora el [framework interactivo](https://assets.vtex.com/4524045/) de la plataforma VTEX.
 
 ### Sigue las directrices de seguridad
 
@@ -62,9 +58,7 @@ Existen estrategias para prevenir y reducir la exposición de tu tienda al riesg
 * **reCAPTCHA:** utiliza [reCAPTCHA](https://help.vtex.com/es/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#) para prevenir fraudes con falsos usuarios creados por programas maliciosos.
 * **Autenticación:** si tu tienda está experimentando ataques recurrentes, considera desactivar el inicio de sesión mediante contraseña y opta por otro método de [autenticación](https://help.vtex.com/es/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) para los clientes de tu tienda.
 
-<div class = "alert alert-info">
-Para más información sobre acciones preventivas, consulta el artículo <a href="https://help.vtex.com/es/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE">Prácticas recomendadas para evitar ataques virtuales</a> y este <a href="https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470">post</a> (disponible en portugués) en VTEX Community.
-</div>
+>ℹ️ Para más información sobre acciones preventivas, consulta el artículo [Prácticas recomendadas para evitar ataques virtuales](https://help.vtex.com/es/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE) y este [post](https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470) (disponible en portugués) en VTEX Community.
 
 ### Controla el nivel de acceso de los permisos
 
@@ -104,9 +98,7 @@ Algunos de los principales beneficios de mantenerse informado son:
 * Al configurar las actualizaciones, aumentas la seguridad de tu tienda, ya que estamos constantemente innovando para proteger tu negocio.
 * Si necesitas contactar al equipo de soporte, comprender el funcionamiento de las nuevas funciones te permitirá interactuar de manera más eficaz con ellos, lo que resultará en resoluciones más rápidas.
 
-<div class = "alert alert-info">
-Los anuncios de la página <b>Noticias</b> del Help Center también están disponibles a través de tu Admin VTEX. Para acceder al contenido, basta con hacer clic en el ícono de campana situado en la parte superior de la página.
-</div>
+>ℹ️ Los anuncios de la página **Noticias** del Help Center también están disponibles a través de tu Admin VTEX. Para acceder al contenido, basta con hacer clic en el ícono de campana situado en la parte superior de la página.
 
 ### Recibe notificaciones de status de la plataforma
 
@@ -118,9 +110,7 @@ Por este motivo, VTEX pone a disposición la página [VTEX Status](https://statu
 * [Feed RSS](https://rss.com/blog/how-do-rss-feeds-work/)
 * [Slack](https://slack.com/)
 
-<div class = "alert alert-info">
-Para comprender los detalles de la página de status de la plataforma, accede al artículo <a href="https://help.vtex.com/es/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ">Página VTEX Status</a>.
-</div>
+>ℹ️ Para comprender los detalles de la página de status de la plataforma, accede al artículo [Página VTEX Status](https://help.vtex.com/es/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ).
 
 ### Conoce nuestros contenidos de onboarding
 
@@ -165,7 +155,5 @@ Existen [Buenas prácticas para abrir un ticket con el soporte VTEX](https://hel
 
 Estas recomendaciones son algunas de las más importantes. Para más información, consulta el artículo [Buenas prácticas para abrir un ticket con el soporte VTEX](https://help.vtex.com/es/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX).
 
-<div class = "alert alert-info">
-Para una visión general de nuestro soporte vía tickets, consulta la serie <a href="https://help.vtex.com/es/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">Soporte VTEX</a>, presente en la <b>Guía de onboarding</b>.
-</div>
+>ℹ️ Para una visión general de nuestro soporte vía tickets, consulta la serie [Soporte VTEX](https://help.vtex.com/es/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8), presente en la **Guía de onboarding**.
 
diff --git a/docs/tutorials/es/beta-price-configuration.md b/docs/tutorials/es/beta-price-configuration.md
index c61b9b402..502db104e 100644
--- a/docs/tutorials/es/beta-price-configuration.md
+++ b/docs/tutorials/es/beta-price-configuration.md
@@ -15,9 +15,7 @@ legacySlug: configuracion-de-precios-beta
 subcategory: 2XTQ6yFYeU5bGHK8Qq3f4I
 ---
 
-<div class = "alert alert-info">
-  <p>Esta funcionalidad está en versión Beta, lo que significa que estamos trabajando para mejorarla. Si tiene alguna pregunta, póngase en contacto con <a href = "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad está en versión Beta, lo que significa que estamos trabajando para mejorarla. Si tiene alguna pregunta, póngase en contacto con <a href = "https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
 
 Esta nueva sección de Configuración de precios (Beta) permite crear y gestionar reglas para las tablas de precios, así como cambiar la configuración general de forma práctica y rápida. 
 
@@ -39,9 +37,7 @@ En esta sección, usted puede definir el markup estándar y el límite de variac
 
 - **Sobrescribir precios de sellers:**  esta opción sobrescribe todos los precios de sellers con los de la cuenta actual.
 
-<div class = "alert alert-info">
-  <p>La configuración <b>Sobrescribir precios de sellers</b> no está disponible para sellers White label.</p>
-</div>
+>ℹ️ La configuración **Sobrescribir precios de sellers** no está disponible para sellers White label.
 
 ## Reglas para tablas de precios
 
diff --git a/docs/tutorials/es/buy-one-get-one.md b/docs/tutorials/es/buy-one-get-one.md
index 240075ca4..aad2f29b4 100644
--- a/docs/tutorials/es/buy-one-get-one.md
+++ b/docs/tutorials/es/buy-one-get-one.md
@@ -65,9 +65,7 @@ En esta sección se pueden definir los sellers a los que se aplicará la promoci
 
 Para que la promoción sea válida para todos los sellers, deja la selección sin marcar.
 
-<div class = "alert alert-warning">
-  <p>No es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:</p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.</ol>
-</div>
+>⚠️ No es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.
 
 ![Restringir esta promoción a los productos de los sellers](https://images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/2b00df355cb9670e4a5b799e5c9482e7/Restringir_esta_promoci_n_a_los_productos_de_los_sellers.png)
 
@@ -91,13 +89,9 @@ En esta sección se definen las colecciones, SKU y cantidad mínima que deben re
 - **SKUs:** permite seleccionar el nombre o ID de los SKU sobre los que deseas aplicar el descuento. También puedes importar una lista de SKU, que debe guardarse en un archivo de texto (**.txt**) con cada ID descrito en una fila diferente.
 - **Cantidad mínima:** permite definir la cantidad mínima de productos que deben agregarse al carrito para que se conceda el descuento. Es un campo obligatorio.
 
-<div class = "alert alert-warning">
- <p>La promoción no se creará si no se rellenan los campos Colecciones o SKUs.<p>
-</div>
+>⚠️ <p>La promoción no se creará si no se rellenan los campos Colecciones o SKUs.<p>
 
-<div class = "alert alert-warning">
- <p>Se puede crear una promoción Compra uno y lleva uno gratis con un máximo de 100 SKU diferentes al mismo tiempo.<p>
-</div>
+>⚠️ <p>Se puede crear una promoción Compra uno y lleva uno gratis con un máximo de 100 SKU diferentes al mismo tiempo.<p>
 
 ![Compra uno y lleva uno gratis](https://images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/c37f45ddde8ac8ddab99cae1500a951d/Compra_uno_y_lleva_uno_gratis.png)
 
diff --git a/docs/tutorials/es/calculating-revenue-through-the-worksheet-exported-from-orders-module.md b/docs/tutorials/es/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
index e00c4cf97..0bd850bcd 100644
--- a/docs/tutorials/es/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
+++ b/docs/tutorials/es/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
@@ -29,8 +29,6 @@ Para calcular los ingresos totales de la planilla, sigue los pasos a continuaci
 4. Quite todos los valores duplicados de la segunda columna (__Order__). Esto debe hacerse porque, en los casos de compras de más de un SKU, se generan varias líneas para el mismo pedido - una para cada SKU.
 5. Agregue los valores de la columna __Total Value__. En esta columna queda el valor total del pedido (es decir, ya considerando todos los SKUs del carrito).
 
-<div class = "alert alert-info">
-La suma de los valores de la columna Total Value (después de la eliminación de los pedidos duplicados) es el ingreso total obtenido con los pedidos seleccionados en la planilla.
-</div>
+>ℹ️ La suma de los valores de la columna Total Value (después de la eliminación de los pedidos duplicados) es el ingreso total obtenido con los pedidos seleccionados en la planilla.
 
 Para entender todas las columnas de la planilla, vea el artículo [Informe de pedidos](https://help.vtex.com/es/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
diff --git a/docs/tutorials/es/campaign-promotion.md b/docs/tutorials/es/campaign-promotion.md
index 37c4065cf..24294e07d 100644
--- a/docs/tutorials/es/campaign-promotion.md
+++ b/docs/tutorials/es/campaign-promotion.md
@@ -72,9 +72,7 @@ A continuación se describen todos los campos que debe rellenar para crear una p
   - **Flete gratis:** es el descuento total sobre el valor del flete.
   - **Regalo:** es el descuento total sobre el valor del producto definido como regalo. Puede seleccionar uno o más SKU como regalos, o más de una unidad para el mismo SKU. Para definir más de un regalo, escoja la opción **Activar multiplicador de regalo** y defina la cantidad deseada. Lea más sobre esta opción en este [artículo](https://help.vtex.com/es/tutorial/que-significa-activar-el-multiplicador-de-regalo-en-una-promocion--1gydgkmjEWcoo2CskUwuYK).
 
-  <div class = "alert alert-info">
-  <p>El producto de <b>Regalo</b> también debe tener un precio registrado aunque se dé al cliente de forma gratuita.</p>
- </div>
+  >ℹ️ El producto de **Regalo** también debe tener un precio registrado aunque se dé al cliente de forma gratuita.
 
   - **Descuento nominal basado en la fórmula:** el descuento se calcula sumando los precios de los productos (total), el flete (<i>freight</i>) y el porcentaje de descuento deseado. Es importante destacar que el valor del flete que se incluirá en la fórmula será el valor menor que esté disponible para el pedido, independientemente de la selección del cliente. El separador decimal debe ser siempre el punto. Ejemplo: el descuento será del 30 % del valor del producto + el valor del flete. Entonces, la fórmula debe rellenarse así: ((total + freight) * 0.3).
   - **Valor de fidelidad nominal:** es el crédito que será añadido al programa de fidelidad de la tienda. 
@@ -100,9 +98,7 @@ En esta sección puede definir en qué <i>sellers</i> se aplicará la promoción
 
 Para que la promoción sea válida para todos los <i>sellers</i>, deje la selección sin marcar.
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> no es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:</p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.</ol>
-</div>
+>⚠️ **Atención:** no es posible seleccionar directamente un <i>seller white label</i>. Para incluir a un <i>seller white label</i> en la promoción, tiene dos opciones:1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de su tienda a la promoción.2. Dejar la selección sin marcar para incluir a todos los <i>sellers</i>. Aquí, todos los tipos de <i>sellers, white label</i> o no, se agregarán a la promoción.
 
 #### Política comercial
 
diff --git a/docs/tutorials/es/canceling-orders.md b/docs/tutorials/es/canceling-orders.md
index a9dff5b78..886249ae6 100644
--- a/docs/tutorials/es/canceling-orders.md
+++ b/docs/tutorials/es/canceling-orders.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Tiene lugar la cancelación de Pedido en VTEX en prácticamente cualquier status de su evolución. Corresponde destacar que, una vez cancelado el pedido, no se revierte el status del pedido.
 
-<div class = "alert alert-warning">
-No es posible cancelar pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
-</div>
+>⚠️ No es posible cancelar pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 Hay dos formas de hacer esta acción, por el Admin VTEX o API.
 
diff --git a/docs/tutorials/es/carrier-working-hours.md b/docs/tutorials/es/carrier-working-hours.md
index 3e10963fc..06404a87b 100644
--- a/docs/tutorials/es/carrier-working-hours.md
+++ b/docs/tutorials/es/carrier-working-hours.md
@@ -31,9 +31,7 @@ La configuración del horario laboral influye en el cálculo del tiempo de entre
 
   >❗ Para autorizar la transportadora a recibir pedidos los fines de semana, este interruptor debe estar marcado como `Activo`. Incluso si los sábados y domingos están configurados como ventanas válidas, activar el interruptor es obligatorio para autorizar al transportista a recibir pedidos fuera del horario laboral.
 
-  <div class = "alert alert-info">
-Cuando esta opción está habilitada, el <a href="https://help.vtex.com/es/tutorial/how-shipping-calculation-works--tutorials_116">cálculo del envío</a> del pedido se ve influenciado y al tiempo total de envío se suma el tiempo desde que se realiza el pedido hasta la hora de apertura del transportista.
-</div>
+  >ℹ️ Cuando esta opción está habilitada, el [cálculo del envío](https://help.vtex.com/es/tutorial/how-shipping-calculation-works--tutorials_116) del pedido se ve influenciado y al tiempo total de envío se suma el tiempo desde que se realiza el pedido hasta la hora de apertura del transportista.
 
 3. Seleccione el `Día de la semana`, así como la `Hora de inicio` y `Hora de fin` del periodo de envío, considerando que:
     * **Día de la semana:** los días de la semana en que la transportadora realiza entregas.
diff --git a/docs/tutorials/es/change-seller.md b/docs/tutorials/es/change-seller.md
index d49c13ef8..1e6b0eb9b 100644
--- a/docs/tutorials/es/change-seller.md
+++ b/docs/tutorials/es/change-seller.md
@@ -17,9 +17,7 @@ subcategory: 5m1qqfnmfYKsO0KiOQC8Ky
 
 El Change Seller es la funcionalidad que da a los <i>marketplaces</i> la autonomía para cambiar el <i>seller</i> que entregará el pedido.
 
-<div class = "alert alert-info">
-La funcionalidad Change Seller solo se puede configurar a través de las APIs. Para más información, consulte la <a href="https://developers.vtex.com/vtex-rest-api/docs/change-seller">documentación Change Seller para desarrolladores</a>.
-</div>
+>ℹ️ La funcionalidad Change Seller solo se puede configurar a través de las APIs. Para más información, consulte la [documentación Change Seller para desarrolladores](https://developers.vtex.com/vtex-rest-api/docs/change-seller).
 
 Un cambio de <i>seller</i> puede ocurrir en dos situaciones:
 
diff --git a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
index 6a27f5a52..6d2fb8865 100644
--- a/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/es/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -41,7 +41,5 @@ La seguridad operativa de esta funcionalidad se basa en controlar el acceso de p
 
 Una vez que se cierra el pedido, el precio ingresado manualmente debe ser aprobado por el administrador de la tienda o un usuario con permiso en el sistema de [Autorización de pedidos](https://help.vtex.com/es/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn).
 
-<div class = "alert alert-info">
-Una vez validado el valor del precio manual, el pedido sigue el flujo de facturación normal.
-</div>
+>ℹ️ Una vez validado el valor del precio manual, el pedido sigue el flujo de facturación normal.
 
diff --git a/docs/tutorials/es/changing-items-from-a-complete-order.md b/docs/tutorials/es/changing-items-from-a-complete-order.md
index db2ac54d0..f2f697e44 100644
--- a/docs/tutorials/es/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/es/changing-items-from-a-complete-order.md
@@ -73,6 +73,4 @@ Al cambiar o eliminar ítems de un pedido, el valor total del pedido cambia. En
 
 El valor total del pedido se actualizará después de que se inserte la factura, y corresponde al valor liquidado por el gateway de pagos de VTEX. Si el cliente devuelve un ítem, el reembolso se realizará automáticamente a través del sistema de Pagos de VTEX.
 
-<div class = "alert alert-info">
-La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el <a href="https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Los conectores legados no admiten la funcionalidad.
-</div>
+>ℹ️ La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Los conectores legados no admiten la funcionalidad.
diff --git a/docs/tutorials/es/changing-the-total-cost-of-the-order.md b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
index 9f1be3758..be1bd2178 100644
--- a/docs/tutorials/es/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/es/changing-the-total-cost-of-the-order.md
@@ -42,6 +42,4 @@ Al cambiar o eliminar ítems de un pedido, el valor total del pedido cambia. En
 
 El valor total del pedido se actualizará después de que se inserte la factura, y corresponde al valor capturado por el gateway de pagos de VTEX. Si el cliente devuelve un ítem, el reembolso se realizará automáticamente a través del sistema de Pagos de VTEX.
 
-<div class = "alert alert-info">
-La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el <a href="https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Los conectores legados no admiten la funcionalidad.
-</div>
+>ℹ️ La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Los conectores legados no admiten la funcionalidad.
diff --git a/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
index 29b604f82..d8cc8f787 100644
--- a/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/es/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -31,9 +31,7 @@ La tabla que figura a continuación muestra los principales escenarios de uso de
 | ---------- | ---------- | ---------- |
 | Se sugiere usar el [Seller Portal](https://help.vtex.com/es/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) cuando el marketplace VTEX quiere conectarse a un seller externo que no tiene una cuenta en VTEX. Esta funcionalidad permite [compartir productos](https://help.vtex.com/es/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) del marketplace VTEX con el seller, lo cual disminuye las discrepancias y simplifica la gestión de la operación. Cada entorno del Seller Portal que se crea integra al seller con un único marketplace VTEX. | Se sugiere la cuenta estándar para las tiendas que quieren realizar su operación de ecommerce de manera completa, mediante el uso de estrategias de [comercio unificado](https://help.vtex.com/es/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv). La cuenta estándar puede funcionar como seller VTEX, marketplace VTEX y conectarse con varios marketplaces y [conectores nativos](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex). | La cuenta franquicia es estratégica para las operaciones que desean expandir sus ventas con la integración de tiendas físicas, ya que existe la posibilidad de heredar el catálogo de una cuenta estándar. Los franquiciados y representantes de la marca son quienes suelen adoptar la cuenta franquicia. |
 
-<div class = "alert alert-info">
-El modelo y los objetivos de tu negocio definirán cuál es tu mejor opción para operar en el ecosistema VTEX. Obtén más información en <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">Estrategias de marketplace en VTEX</a>.
-</div>
+>ℹ️ El modelo y los objetivos de tu negocio definirán cuál es tu mejor opción para operar en el ecosistema VTEX. Obtén más información en [Estrategias de marketplace en VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
 A continuación, hay una serie de comparaciones sobre cómo el Seller Portal, la cuenta estándar y la cuenta franquicia se relacionan con los módulos y las funcionalidades de la plataforma VTEX:
 
diff --git a/docs/tutorials/es/collection-highlight-control.md b/docs/tutorials/es/collection-highlight-control.md
index ac8e57de0..50646edb3 100644
--- a/docs/tutorials/es/collection-highlight-control.md
+++ b/docs/tutorials/es/collection-highlight-control.md
@@ -15,9 +15,7 @@ legacySlug: control-de-destaque-de-coleccion
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el Portal CMS Legado</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el Portal CMS Legado</a>.
 
 El control `<vtex.cmc:HightLight/>` (para páginas de producto) o `$product.HightLight` (para estantes) renderiza un elemento HTML con una clase específica en el contexto de los productos que forman parte de una colección marcada con la flag __Highlight__.
 
diff --git a/docs/tutorials/es/collection-types.md b/docs/tutorials/es/collection-types.md
index 3b03f485d..b07e50fef 100644
--- a/docs/tutorials/es/collection-types.md
+++ b/docs/tutorials/es/collection-types.md
@@ -31,9 +31,7 @@ En VTEX, hay tres alternativas de configuración de colecciones, que son:
 | Automática | CMS | Creada por filtros de Marca o Categoría | No se puede modificar |
 | Híbrida | CMS y módulo de Colecciones Beta | Creada por filtros de Marca o Categoría. También se pueden agregar los productos manualmente | No se puede modificar |
 
-<div class = "alert alert-warning">
-  <p>La coleciones creadas en el módulo CMS y con más de un <a href = " https://help.vtex.com/es/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">grupo</a> no pueden ser reordenadas en el nuevo módulo de Colecciones Beta. Aconsejamos que no cambie el orden, ya que puede comprometer la eficiencia de la funcionalidad.</p>
-</div>
+>⚠️ La coleciones creadas en el módulo CMS y con más de un <a href = " https://help.vtex.com/es/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">grupo</a> no pueden ser reordenadas en el nuevo módulo de Colecciones Beta. Aconsejamos que no cambie el orden, ya que puede comprometer la eficiencia de la funcionalidad.
 
 ## Colecciones manuales
 
diff --git a/docs/tutorials/es/comprehensive-seller.md b/docs/tutorials/es/comprehensive-seller.md
index 3a4b3c4f7..183da49eb 100644
--- a/docs/tutorials/es/comprehensive-seller.md
+++ b/docs/tutorials/es/comprehensive-seller.md
@@ -45,9 +45,7 @@ Cuando todavía no hay información sobre la ubicación del cliente, la heuríst
 
 Esto ocurre tanto durante la navegación como en el carrito, con el objetivo de evitar que el cliente vea productos de vendedores que no entregan en su dirección.
 
-<div class = "alert alert-info">
-Aunque durante la navegación la información sobre la ubicación del cliente se haya capturado y almacenado en el campo <code>regionId</code> de la API de Sesión, la ubicación no se utiliza en el carrito. Solo los productos del seller principal y de los sellers de extensa cobertura estarán disponibles para el cliente en el carrito. Los productos de otros sellers solo estarán disponibles después de que el cliente indique el código postal de entrega en el checkout.
-</div>
+>ℹ️ Aunque durante la navegación la información sobre la ubicación del cliente se haya capturado y almacenado en el campo `regionId` de la API de Sesión, la ubicación no se utiliza en el carrito. Solo los productos del seller principal y de los sellers de extensa cobertura estarán disponibles para el cliente en el carrito. Los productos de otros sellers solo estarán disponibles después de que el cliente indique el código postal de entrega en el checkout.
 
 En los casos de más de un *seller* de extensa cobertura registrado, el *checkout* selecciona el que tiene mayor saldo en stock para el artículo en cuestión, entre todos los *seller* de extensa cobertura. Aprende más en [Selección de sellers white label](https://help.vtex.com/es/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa).
 
diff --git a/docs/tutorials/es/configuring-a-seller-on-vtex-marketplace.md b/docs/tutorials/es/configuring-a-seller-on-vtex-marketplace.md
index dd9dcb27d..856b315a7 100644
--- a/docs/tutorials/es/configuring-a-seller-on-vtex-marketplace.md
+++ b/docs/tutorials/es/configuring-a-seller-on-vtex-marketplace.md
@@ -25,17 +25,13 @@ Este artículo explica cómo configurar tu tienda para convertirse en un _seller
 
 Para saber qué datos deben intercambiar los _sellers_ y los _marketplaces_, consulta el artículo [Información compartida](https://help.vtex.com/es/tutorial/informacoes-compartilhadas-entre-marketplace-e-seller-na-vtex--3o7WGiBtfnKKZ3Ddug26k3) entre el _marketplace_ y el _seller en VTEX. Si tu tienda quiere operar como _marketplace_, consulta el artículo [Configurar marketplaces VTEX](https://help.vtex.com/es/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb).
 
-<div class = "alert alert-info">
-Para comenzar a vender tus productos en <i>marketplaces</i> o para encontrar nuevos <i>partners</i> comerciales que vendan en tu <i>marketplace</i>, usa <a href="https://help.vtex.com/es/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM">Marketplaces e integraciones</a>, la funcionalidad que facilita la identificación y el contacto entre los <i>marketplaces</i> y <i>sellers</i> en el ecosistema VTEX.
-</div>
+>ℹ️ Para comenzar a vender tus productos en <i>marketplaces</i> o para encontrar nuevos <i>partners</i> comerciales que vendan en tu <i>marketplace</i>, usa [Marketplaces e integraciones](https://help.vtex.com/es/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM), la funcionalidad que facilita la identificación y el contacto entre los <i>marketplaces</i> y <i>sellers</i> en el ecosistema VTEX.
 
 ## Definir la política comercial
 
 En VTEX, la [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) agrupa configuraciones de catálogo, precios, promociones, logística, segmentación de clientes y pagos en un canal de venta. El _seller_ puede integrarse al _marketplace_ utilizando la política comercial predefinida de su tienda o también puede definir configuraciones específicas para la integración mediante la configuración de una [política comercial para el marketplace](https://help.vtex.com/es/tutorial/configurando-a-politica-comercial-para-marketplace/).
 
-<div class = "alert alert-info">
-Se puede usar una misma política comercial para integrarla con varios <i>marketplaces</i>. La <a href="https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X">contratación de una política comercial adicional</a> para integrarse con un <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conector nativo</a>, un conector certificado (partner) u otras tiendas VTEX es gratuita.
-</div>
+>ℹ️ Se puede usar una misma política comercial para integrarla con varios <i>marketplaces</i>. La [contratación de una política comercial adicional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) para integrarse con un [conector nativo](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex), un conector certificado (partner) u otras tiendas VTEX es gratuita.
 
 No es necesario crear una política comercial específica para un _marketplace_ solo para configurar promociones, ya que se pueden segmentar las promociones por [afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). Obtén más información en [Configurar promoción para marketplace](https://help.vtex.com/es/tutorial/configurar-promocao-para-marketplace--tutorials_406).
 
@@ -45,9 +41,7 @@ El surtido de productos enviados al _marketplace_ se debe gestionar a través de
 
 En VTEX, el [afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) es el código que el _seller_ VTEX crea para identificar al _marketplace_ en el que venderá sus productos. Cada _marketplace_ debe corresponder a un único afiliado. Será a través del afiliado que el _marketplace_ recibirá notificaciones sobre pedidos, cambios en la información de un SKU y modificaciones de precios y _stock_, por ejemplo.
 
-<div class = "alert alert-info">
-La integración con <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex">conectores nativos</a> crea el código del afiliado automáticamente. No obstante, para que el <i>seller</i> VTEX se integre con un <i>marketplace</i> VTEX o un <i>marketplace</i> externo, el <i>seller</i> debe crear el ID de afiliado de forma manual.
-</div>
+>ℹ️ La integración con [conectores nativos](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-con-un-conector-nativo-vtex) crea el código del afiliado automáticamente. No obstante, para que el <i>seller</i> VTEX se integre con un <i>marketplace</i> VTEX o un <i>marketplace</i> externo, el <i>seller</i> debe crear el ID de afiliado de forma manual.
 
 El _seller_ debe seguir los pasos que se indican en el artículo [Configurar afiliado](https://help.vtex.com/es/tutorial/como-configurar-afiliado--tutorials_187) y, una vez que haya creado el código identificador, se lo debe informar al _marketplace_. Luego de esto, el _marketplace_ VTEX [agregará al seller](https://help.vtex.com/es/tutorial/configuring-the-seller--tutorials_392) y lo asociará a una política comercial.
 
@@ -55,9 +49,7 @@ El _seller_ debe seguir los pasos que se indican en el artículo [Configurar afi
 
 Una vez que el _seller_ y el _marketplace_ están integrados, el envío de productos al _marketplace_ no es automático sino que será necesario que el _seller_ [reindexe la base](https://help.vtex.com/es/tutorial/entendendo-o-funcionamento-da-indexacao). Este proceso prepara los datos de los SKU y de los productos y envía al _marketplace_ la información general sobre el catálogo, los precios y el _stock_. 
 
-<div class = "alert alert-info">
-Solo el <a href="https://help.vtex.com/es/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA">usuario titular (owner)</a> tiene permiso para reindexar la base de una tienda VTEX. Durante el periodo de reindexación, que es variable, los productos ingresan en una fila para que se actualicen los datos, pero siguen disponibles para la venta en el sitio web de la tienda. 
-</div>
+>ℹ️ Solo el [usuario titular (owner)](https://help.vtex.com/es/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA) tiene permiso para reindexar la base de una tienda VTEX. Durante el periodo de reindexación, que es variable, los productos ingresan en una fila para que se actualicen los datos, pero siguen disponibles para la venta en el sitio web de la tienda.
 
 Para reindexar la base, copia en tu navegador la dirección a continuación y reemplaza «{nomedaloja}» con el nombre de tu tienda:
 
diff --git a/docs/tutorials/es/configuring-access-without-www.md b/docs/tutorials/es/configuring-access-without-www.md
index ec424d54f..a352c2874 100644
--- a/docs/tutorials/es/configuring-access-without-www.md
+++ b/docs/tutorials/es/configuring-access-without-www.md
@@ -31,9 +31,7 @@ El dominio principal de tu tienda debe contener un subdominio, que puede ser o n
 - `tienda.mimarca.com` - Dominio principal válido.
 - `mitienda.com` - No puede ser su dominio principal ya que no contiene un subdominio, pero puede ser redireccionado.
 
-<div class = "alert alert-info">
-  Obtenga más información sobre como <a href="https://help.vtex.com/es/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450">configurar el dominio principal de su tienda</a>.
-</div>
+>ℹ️ Obtenga más información sobre como [configurar el dominio principal de su tienda](https://help.vtex.com/es/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450).
 
 Esta redirección se puede realizar de muchas formas. El uso de `htaccess` en el servidor es una de las más conocidas, pero es muy técnica y depende de otros factores.
 
diff --git a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index 077655e69..1c8a9ac5a 100644
--- a/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/es/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -25,17 +25,13 @@ Para importar los datos en masa a la plataforma VTEX, sigue los pasos a continua
 
 2.	En la pestaña Organizaciones, haz clic en **Nuevo** y luego en Importar en masa. Haz clic en el botón Cargar y selecciona tu archivo **XLSX**, o arrastra y suelta el archivo a la área punteada. El tamaño del archivo importado debe ser menor que 50 MB.
 
-<div class = "alert alert-info">
-Puedes bajar un archivo de plantilla haciendo clic en VTEX file template en la parte inferior de la ventana de importación y rellenar los datos.
-</div>
+>ℹ️ Puedes bajar un archivo de plantilla haciendo clic en VTEX file template en la parte inferior de la ventana de importación y rellenar los datos.
 
 <ol start="3">
 	<li>Después de que la plataforma realice la verificación del archivo de importación y no encuentre errores, haz clic en Importar.</li>
 </ol>
 
-<div class = "alert alert-info">
-  Si la plataforma detecta algún error, consulta la sección <b>Errores de importación</b>.
-</div>
+>ℹ️ Si la plataforma detecta algún error, consulta la sección **Errores de importación**.
 
 <ol start="4">
 	<li>Una vez finalizado el proceso de importación, puedes hacer clic en Ver detalles de la importación para acceder al informe de importación.</li>
@@ -55,9 +51,7 @@ Para ver los detalles de los problemas encontrados, sigue los pasos a continuaci
 
 3. Después de corregir los errores, puedes reiniciar el proceso de importación cargando el archivo corregido nuevamente.
 
-<div class = "alert alert-info">
-Asegúrate de que el archivo que cargues solo contenga las correcciones de los errores previamente identificados para garantizar que la importación se realice correctamente.
-</div>
+>ℹ️ Asegúrate de que el archivo que cargues solo contenga las correcciones de los errores previamente identificados para garantizar que la importación se realice correctamente.
 
 ![Bulk import - ES](https://images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/2cdc7eb8e0710fff44a55b1a2619c58b/Bulk_import_vers_o_error-gif-ES.gif)
 
diff --git a/docs/tutorials/es/configuring-dns-pointing-to-vtex.md b/docs/tutorials/es/configuring-dns-pointing-to-vtex.md
index 6ddd333a5..f1a625c6e 100644
--- a/docs/tutorials/es/configuring-dns-pointing-to-vtex.md
+++ b/docs/tutorials/es/configuring-dns-pointing-to-vtex.md
@@ -68,16 +68,14 @@ Otra alternativa, aunque no recomendada, sería no incluir registros CAA en tu s
 
 Para facilitar el trabajo de crear y verificar tus registros CAA, puedes utilizar [CAA Record Helper de SSLMate](https://sslmate.com/caa/). El programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) también puede ayudar a verificar los registros mediante el comando `dig domain.com CAA`; el status `SERVFAIL` puede indicar que tu servidor DNS no está en cumplimiento.
 
-<div class = "alert alert-info">
-Más información:
-<p>
-<ul>
-<li><a href="https://sslmate.com/caa/">CAA Record Helper by SSLMate</a></li>
-<li><a href="https://letsencrypt.org/docs/caa/">Let's Encrypt: Certificate Authority Authorization (CAA)</a></li>
-<li><a href="https://sslmate.com/caa/about">SSL Mate: About CAA</a></li>
-</ul>
-</p>
-</div>
+>ℹ️ Más información:
+>
+> *[CAA Record Helper by SSLMate](https://sslmate.com/caa/)
+>
+> *[Let's Encrypt: Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)
+>
+> *[SSL Mate: About CAA](https://sslmate.com/caa/about)
+> 
 
 ## Apuntamiento de DNS
 
@@ -93,9 +91,7 @@ Si tu storefront se creó con [CMS IO](https://help.vtex.com/es/tracks/cms--2Ycp
 
 Después de recibir la confirmación del apuntamiento interno, debes realizar el [apuntamiento de DNS común](#apuntamiento-de-dns-comun) dentro de cinco días. De lo contrario, se eliminará el apuntamiento interno y tendrás que volver a solicitarlo.
 
-<div class = "alert alert-info">
-Aprende más sobre el <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live">Go-live con Store Framework</a> o la <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migración del CMS heredado a Store Framework</a>.
-</div>
+>ℹ️ Aprende más sobre el [Go-live con Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live) o la [Migración del CMS heredado a Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 ## Apuntamiento de DNS común
 
diff --git a/docs/tutorials/es/configuring-domains-in-account-management.md b/docs/tutorials/es/configuring-domains-in-account-management.md
index de6bcb2d8..9b2fa7634 100644
--- a/docs/tutorials/es/configuring-domains-in-account-management.md
+++ b/docs/tutorials/es/configuring-domains-in-account-management.md
@@ -33,9 +33,7 @@ Todo dominio registrado de esta forma debe contener un subdominio, que puede ser
 - `www.mitienda.com` - Dominio válido.
 - `tienda.mimarca.com` - Dominio válido.
 
-<div class = "alert alert-info">
-  Obtenga más información sobre como <a href="https://help.vtex.com/es/tutorial/configuring-access-without-www--tutorials_4278">configurar acceso sin www</a>.
-</div>
+>ℹ️ Obtenga más información sobre como [configurar acceso sin www](https://help.vtex.com/es/tutorial/configuring-access-without-www--tutorials_4278).
 
 ## Registrar nuevo dominio
 
diff --git a/docs/tutorials/es/configuring-payment-conditions-for-b2b.md b/docs/tutorials/es/configuring-payment-conditions-for-b2b.md
index 05102e499..798a37e66 100644
--- a/docs/tutorials/es/configuring-payment-conditions-for-b2b.md
+++ b/docs/tutorials/es/configuring-payment-conditions-for-b2b.md
@@ -19,9 +19,7 @@ En una operación B2B, las [condiciones de pago](https://help.vtex.com/es/tutori
 
 Los usuarios con rol de administrador de la organización pueden personalizar por centro de costos las opciones de pago disponibles.
 
-<div class = "alert alert-info">
-Cuando configuras una condición de pago en el módulo de Pagos, se mostrará como un medio de pago en la sección <b>Disponible</b> dentro de la pestaña <b>Condiciones de pago</b>. Para acceder a esta sección solo tienes que hacer clic en el nombre de la organización. Los medios de pago listados son aquellos que ya están asignados a la organización.
-</div>
+>ℹ️ Cuando configuras una condición de pago en el módulo de Pagos, se mostrará como un medio de pago en la sección **Disponible** dentro de la pestaña **Condiciones de pago**. Para acceder a esta sección solo tienes que hacer clic en el nombre de la organización. Los medios de pago listados son aquellos que ya están asignados a la organización.
 
 ## Asociar condiciones de pago a la organización
 Para asociar una condición de pago con una organización de compras sigue las instrucciones a continuación:
diff --git a/docs/tutorials/es/configuring-price-divergence-rule.md b/docs/tutorials/es/configuring-price-divergence-rule.md
index 34e94a42b..344b4b08e 100644
--- a/docs/tutorials/es/configuring-price-divergence-rule.md
+++ b/docs/tutorials/es/configuring-price-divergence-rule.md
@@ -33,9 +33,7 @@ Recomendamos que el _seller_ cree la regla de Divergencia de precios antes de co
 
 La [regla de divergencia de precios](https://help.vtex.com/es/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) se compone de una o varias reglas de autorización de pedidos, que corresponden a intervalos entre el 0% y el 100% del precio del pedido. La configuración se realiza de forma que cada intervalo esté asociado a una acción automática de procesamiento.
 
-<div class = "alert alert-info">
-Para crear una regla de divergencia de precios, el usuario debe tener el <a href="https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">rol</a> Admin Super (Owner) o OMS Full. Garantiza la seguridad en la gestión de tus operaciones y consulta las <a href="https://help.vtex.com/es/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM">buenas prácticas de seguridad para la gestión de usuarios</a>.
-</div>
+>ℹ️ Para crear una regla de divergencia de precios, el usuario debe tener el [rol](https://help.vtex.com/es/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (Owner) o OMS Full. Garantiza la seguridad en la gestión de tus operaciones y consulta las [buenas prácticas de seguridad para la gestión de usuarios](https://help.vtex.com/es/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM).
 
 Para crear una regla de divergencia de precios, sigue los pasos a continuación:
 
@@ -79,9 +77,7 @@ La regla de divergencia de precios se puede editar en cualquier momento. Para ha
 
 En la página de edición de reglas, puedes eliminar la regla de divergencia de precios haciendo clic en **ELIMINAR REGLAS**. Esto hace que todas las reglas de autorización configuradas se eliminen permanentemente.
 
-<div class = "alert alert-info">
-Si eliminas la regla de divergencia de precios, esta acción no se puede revertir. Para que vuelva a aplicarse, será necesario configurarla de nuevo. Lo mismo se aplica a las reglas de autorización que componen la regla de divergencia de precios.
-</div>
+>ℹ️ Si eliminas la regla de divergencia de precios, esta acción no se puede revertir. Para que vuelva a aplicarse, será necesario configurarla de nuevo. Lo mismo se aplica a las reglas de autorización que componen la regla de divergencia de precios.
 
 En la misma página, en la pestaña **Todas**, puedes ver la lista de todas las reglas de autorización de pedidos creadas. Para eliminar una regla de autorización, haz clic en el botón **ELIMINAR REGLA** junto a la regla que deseas eliminar.
 
diff --git a/docs/tutorials/es/configuring-promotions-for-marketplaces.md b/docs/tutorials/es/configuring-promotions-for-marketplaces.md
index 58d45d8c0..8bbda40a2 100644
--- a/docs/tutorials/es/configuring-promotions-for-marketplaces.md
+++ b/docs/tutorials/es/configuring-promotions-for-marketplaces.md
@@ -50,9 +50,7 @@ Para este tipo de promociones es importante tener en cuenta la siguiente informa
 
 Existen diferencias entre la configuración disponible para marketplaces VTEX y para marketplaces externos. Consulta en la tabla siguiente las funcionalidades que se aplican en cada caso.
 
-<div class = "alert alert-warning">
-  <p>En el caso de las integraciones externas, las configuraciones son únicas para cada marketplace, y estos deciden qué funcionalidades utilizarán.</p>
-</div>
+>⚠️ En el caso de las integraciones externas, las configuraciones son únicas para cada marketplace, y estos deciden qué funcionalidades utilizarán.
 
 | Nombre  | Descripción      | ¿Disponible para marketplaces VTEX? | ¿Disponible para marketplaces externos? |
 | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | ------------------------------------ |
@@ -135,6 +133,4 @@ Los sellers pueden segmentar las promociones para mercados específicos. Hay dos
 2. En la sección **Política Comercial**, seleccione las opciones **Es igual a** y **Entregado por mí (Tienda de otros)**.
 4. Haga clic en `Guardar`.
 
-<div class = "alert alert-warning">
-  <p>Una vez creada la promoción, recuerde <a href = "https://help.vtex.com/es/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar los productos afectados</a> al inicio y al final de las promociones. De esta manera, sus productos tendrán los precios actualizados.</p>
-</div>
+>⚠️ Una vez creada la promoción, recuerde <a href = "https://help.vtex.com/es/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar los productos afectados</a> al inicio y al final de las promociones. De esta manera, sus productos tendrán los precios actualizados.
diff --git a/docs/tutorials/es/configuring-xml.md b/docs/tutorials/es/configuring-xml.md
index 91b99572c..5e0c7501e 100644
--- a/docs/tutorials/es/configuring-xml.md
+++ b/docs/tutorials/es/configuring-xml.md
@@ -36,9 +36,7 @@ He aquí algunos ejemplos de *partners* que se integran con VTEX XML:
 - UOL Dynad
 - Zanox
 
-<div class = "alert alert-info">
-  <p>Los cambios en XML tardan en promedio dos horas en actualizarse.</p>
-</div>
+>ℹ️ Los cambios en XML tardan en promedio dos horas en actualizarse.
 
 ## Nuevo XML
 
diff --git a/docs/tutorials/es/creating-a-more-for-less-promotion.md b/docs/tutorials/es/creating-a-more-for-less-promotion.md
index 955cbe4d9..ad617700b 100644
--- a/docs/tutorials/es/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/es/creating-a-more-for-less-promotion.md
@@ -62,9 +62,7 @@ En esta sección se pueden definir los sellers a los que se aplicará la promoci
 
 Para que la promoción sea válida para todos los sellers, deja la selección sin marcar.
 
-<div class = "alert alert-warning">
-  <p>No es posible seleccionar directamente un <i>seller white label</i>. Hay dos opciones para incluir un <i>seller white label</i> en la promoción: </p><ol>1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de tu tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir todos los <i>sellers</i>. En este caso, todos los tipos de <i>sellers, white label</i> y otros, se agregan a la promoción.</ol>
-</div>
+>⚠️ No es posible seleccionar directamente un <i>seller white label</i>. Hay dos opciones para incluir un <i>seller white label</i> en la promoción:1. Restringir los <i>sellers</i> a la tienda principal. Esta restricción agrega todos los <i>sellers white label</i> de tu tienda a la promoción.2. Dejar la selección sin marcar para incluir todos los <i>sellers</i>. En este caso, todos los tipos de <i>sellers, white label</i> y otros, se agregan a la promoción.
 
 ![Restringir - ES](https://images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/709b4d87b04c6bcdb845f948e27f46ed/Restringir_-_ES.png)
 
@@ -89,9 +87,7 @@ En esta sección se definen los productos, la cantidad y el descuento que serán
     - **SKUs:** nombres o ID de los SKU a los que se aplicará el descuento. Puedes importar una lista de SKU haciendo clic en el botón `Selecciona un archivo .txt`. El archivo de texto (.txt) debe tener cada ID de SKU en una línea diferente. También puedes descargar la lista de SKU agregada al campo haciendo clic en el botón `Descargar lista de SKU`.
 - **Colecciones:** selección de las colecciones que se incluirán en la promoción. La promoción solo se aplicará a los productos que figuren en las colecciones registradas en este campo. Solo tienes que introducir el nombre de la colección de productos en la que deseas ofrecer este tipo de descuento. Es posible seleccionar más de una colección.
 
-<div class = "alert alert-info">
-  <p>Si no se especifican los productos por colección o SKU, la plataforma no permitirá la creación de la promoción.</p>
-</div>
+>ℹ️ Si no se especifican los productos por colección o SKU, la plataforma no permitirá la creación de la promoción.
 
 - **Y lleva**  `número` **de estos productos:** la cantidad de unidades del producto que recibirá el descuento configurado. Campo obligatorio.
     - **Con un descuento de:**  el cliente se llevará la cantidad seleccionada de productos con un descuento porcentual definido en el campo.
@@ -130,9 +126,7 @@ En esta sección se proporciona información detallada sobre las condiciones que
 - **Crear un nuevo cupón con los UTM anteriores:** crea un cupón a partir de los UTM registrados para que el cliente tenga acceso a esta promoción solo con el código del cupón.
 - **Medio de pago:** permite elegir si la promoción se aplicará a uno o varios de los medios de pago seleccionados.
 
- <div class = "alert alert-info">
-  <p> El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con <a href="https://support.vtex.com/hc/es-419/requests">nuestro equipo de soporte</a>.</p>
- </div>
+ >ℹ️ El máximo predeterminado de medios de pago registrados por promoción es 20, aunque es posible crear una personalización para incluir hasta 100 medios de pago. Si necesitas utilizar más de 20, ponte en contacto con [nuestro equipo de soporte](https://support.vtex.com/hc/es-419/requests).
 
  ![Condições de promoção - ES](https://images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/13714c02ac6369e9274f4045af6b208b/Condi__es_de_promo__o_-_ES.png)
 
diff --git a/docs/tutorials/es/creating-a-product-collection.md b/docs/tutorials/es/creating-a-product-collection.md
index debf56cf2..419cea59e 100644
--- a/docs/tutorials/es/creating-a-product-collection.md
+++ b/docs/tutorials/es/creating-a-product-collection.md
@@ -15,9 +15,7 @@ legacySlug: creando-colecciones-de-productos
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <p>Existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo <a href="https://help.vtex.com/es/tutorial/registrar-colecciones-beta--yJBHqNMViOAnnnq4fyOye">Colecciones Beta</a>. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ Existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo [Colecciones Beta](https://help.vtex.com/es/tutorial/registrar-colecciones-beta--yJBHqNMViOAnnnq4fyOye). Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 Para crear una colección, siga las siguientes instrucciones:
 
diff --git a/docs/tutorials/es/creating-a-specification-group-in-a-category.md b/docs/tutorials/es/creating-a-specification-group-in-a-category.md
index 1f34b552e..b2dac7ec8 100644
--- a/docs/tutorials/es/creating-a-specification-group-in-a-category.md
+++ b/docs/tutorials/es/creating-a-specification-group-in-a-category.md
@@ -24,9 +24,7 @@ En este artículo, te explicamos cómo funciona la herencia de especificaciones
 * [Herencia de especificaciones](#herencia-de-especificaciones)
 * [Paso a paso en el Admin VTEX](#paso-a-paso-en-el-admin-vtex)
 
-<div class = "alert alert-info">
-  <p>Para crear un grupo de especificaciones con la <strong>API Catálogo</strong>, sigue la guía para desarrolladores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> (Cómo crear una especificación).</p>
-</div>
+>ℹ️ Para crear un grupo de especificaciones con la **API Catálogo**, sigue la guía para desarrolladores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) (Cómo crear una especificación).
 
 ## Herencia de especificaciones
 
diff --git a/docs/tutorials/es/creating-collections-beta.md b/docs/tutorials/es/creating-collections-beta.md
index fd590a264..1bf049afe 100644
--- a/docs/tutorials/es/creating-collections-beta.md
+++ b/docs/tutorials/es/creating-collections-beta.md
@@ -15,10 +15,9 @@ legacySlug: registrar-colecciones-beta
 subcategory: 3aExYJkji3NIu9Ks8bxbWx
 ---
 
-<div class = "alert alert-info">
-  <p>Existen dos formas de configurar las colecciones, a través del <b>CMS</b> o utilizando el módulo <b>Colecciones (Beta)</b>. Este artículo se refiere a la configuración de colecciones mediante el módulo <b>Colecciones (Beta)</b>.</p> 
-    <p>La funcionalidad está en versión Beta y disponible únicamente para ambientes Admin v3. En caso de dudas, <a href="https://support.vtex.com/hc/es-419/requests">contacte a nuestro soporte</a>.</p>
-</div>
+>ℹ️ Existen dos formas de configurar las colecciones, a través del **CMS** o utilizando el módulo **Colecciones (Beta)**. Este artículo se refiere a la configuración de colecciones mediante el módulo **Colecciones (Beta)**. 
+>
+> La funcionalidad está en versión Beta y disponible únicamente para ambientes Admin v3. En caso de dudas, [contacte a nuestro soporte](https://support.vtex.com/hc/es-419/requests).
 
 Este nuevo módulo de **Colecciones (Beta)** permite crear y gestionar colecciones de forma práctica y rápida.
 
@@ -36,9 +35,7 @@ Este artículo explica cómo:
 
 Para crear una colección, debe tener el [perfil de acceso](https://help.vtex.com/en/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc?locale=es) _Owner (Admin Super)_ o crear otro perfil con el recurso **Write Collections**, en la sección **Collection** de los perfiles de **Catalog**. Vea aquí [cómo crear un perfil de acceso](https://help.vtex.com/es/tutorial/access-profiles--7HKK5Uau2H6wxE1rH5oRbc#creando-un-perfil-de-acceso).
 
-<div class = "alert alert-info">
-  <p>Es importante destacar que las colecciones creadas en este módulo no se alteran automáticamente. Las colecciones automáticas — realizadas mediante la selección de filtros — no se pueden configurar en el módulo.</p>
-</div>
+>ℹ️ Es importante destacar que las colecciones creadas en este módulo no se alteran automáticamente. Las colecciones automáticas — realizadas mediante la selección de filtros — no se pueden configurar en el módulo.
 
 ## Crear una colección
 
@@ -106,14 +103,12 @@ Si desea incluir productos de forma masiva, aplique uno de los filtros y haga cl
 
 ![ES-colecao-adicionar-todos](https://images.ctfassets.net/alneenqid6w5/1Qtj7Lq2xPebiPh4SrSV4R/6e66d5f68b4ffe07f6d1dd86bf16726c/ES-colecao-adicionar-todos.png)
 
-<div class = "alert alert-danger">
-<p>No agregue de forma masiva una cantidad superior a 150 mil productos. Eso puede comprometer la indexación del catálogo y el funcionamiento de la tienda.</p>
-</div>
+>❗ No agregue de forma masiva una cantidad superior a 150 mil productos. Eso puede comprometer la indexación del catálogo y el funcionamiento de la tienda.
 
 #### Por plantilla
 Usted también puede agregar ítems a una colección mediante una plantilla. 
 
-<div class = "alert alert-info">El límite máximo para la importación e exportación es de 10,000 SKUs por operación.</div>
+>ℹ️ El límite máximo para la importación e exportación es de 10,000 SKUs por operación.
 
 Para eso, realice los siguientes pasos: 
 
@@ -127,9 +122,7 @@ Para eso, realice los siguientes pasos:
   5. Después de completar la plantilla, guarde las modificaciones e importe el documento en el Admin. Usted puede arrastrar y soltar el archivo en el área indicada o hacer clic en **Selecciona un archivo**. Se aceptan archivos en formato CSV o XML. En caso de que utilice un arquivo CSV, use , para delimitar los campos.
   6. Para finalizar, haga clic en `Importar`.
 
-<div class = "alert alert-warning">
-  <p>La plantilla puede contener hasta 10.000 líneas. Sin embargo, en tiendas con un catálogo extenso, recomendamos incluir un máximo de 50 líneas a la vez para asegurar que la importación funcione correctamente.</p>
-</div>
+>⚠️ La plantilla puede contener hasta 10.000 líneas. Sin embargo, en tiendas con un catálogo extenso, recomendamos incluir un máximo de 50 líneas a la vez para asegurar que la importación funcione correctamente.
 
 ### Eliminación de productos
 
@@ -147,9 +140,7 @@ Si desea eliminar productos de forma masiva, aplique uno de los filtros y haga c
 
 También puede hacer clic en el botón <i class="far fa-check-circle" title = "produtos nesta coleção"></i> (Productos nen esta colección) en la barra superior y después seleccionar `Eliminar Todo`. 
 
-<div class = "alert alert-danger">
-  <p>No elimine de forma masiva una cantidad superior a 150 mil productos. Eso puede comprometer la indexación del catálogo y el funcionamiento de su tienda.</p>
-</div>
+>❗ No elimine de forma masiva una cantidad superior a 150 mil productos. Eso puede comprometer la indexación del catálogo y el funcionamiento de su tienda.
 
 #### Por plantilla
 
@@ -170,9 +161,7 @@ Para alterar el orden de su colección, siga estos pasos:
 
   a. Haga clic en el ícono <i class="fas fa-grip-vertical" title = "arrastrar vertical"></i>, arrastre y suelte el ítem de acuerdo con la posición deseada.
 
-  <div class = "alert alert-info">
-    <p>No se puede utilizar esta opción si un filtro está activo.</p>
-  </div>
+  >ℹ️ No se puede utilizar esta opción si un filtro está activo.
 
   b. Seleccione la caja de los productos que desea alterar y haga clic en `Mover a la posición`. Indique el número de la nueva posición y, para finalizar, haga clic en `Mover`. De esta manera, puede ordenar todos los ítems de la lista de forma masiva. 
 
diff --git a/docs/tutorials/es/creating-landing-pages-per-binding.md b/docs/tutorials/es/creating-landing-pages-per-binding.md
index eb2e73d10..39e64230e 100644
--- a/docs/tutorials/es/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/es/creating-landing-pages-per-binding.md
@@ -33,15 +33,11 @@ En el Admin, puede crear páginas de destino personalizadas según el [*binding*
 - `Descripción` - Resumen de la nueva página web que se mostrará en las páginas de resultados de los motores de búsqueda. 
 - `Palabras clave` - Temas que definen de qué se trata el contenido de la página para que ella sea más fácil de encontrar para los usuarios que naveguen las páginas de resultados de los motores de búsqueda.
 
-  <div class = "alert alert-info">
-Los cinco campos anteriores afectan directamente los accesos y el posicionamiento de la tienda en las páginas de resultados de los motores de búsqueda. Antes de rellenar los metadatos de la página, consulte las prácticas recomendadas de SEO. 
-</div>
+  >ℹ️ Los cinco campos anteriores afectan directamente los accesos y el posicionamiento de la tienda en las páginas de resultados de los motores de búsqueda. Antes de rellenar los metadatos de la página, consulte las prácticas recomendadas de SEO.
 
 5. Elija un *template* para que se muestre en la página de destino de entre los que están disponibles en el campo `Estándar`.
 6. Si desea crear una plantilla condicional, haga clic en el botón `Añadir template condicional` y rellene los campos según las condiciones deseadas.
 
-  <div class = "alert alert-warning">
-Tenga en cuenta que el <i>template</i> condicional solo se mostrará cuando una <i>o</i> todas las condiciones predefinidas coincidan en la interfaz. 
-</div>
+  >⚠️ Tenga en cuenta que el <i>template</i> condicional solo se mostrará cuando una <i>o</i> todas las condiciones predefinidas coincidan en la interfaz.
 
 7. Guarde los cambios.
diff --git a/docs/tutorials/es/creating-landing-pages.md b/docs/tutorials/es/creating-landing-pages.md
index 3a6f6d08c..dc5807049 100644
--- a/docs/tutorials/es/creating-landing-pages.md
+++ b/docs/tutorials/es/creating-landing-pages.md
@@ -39,17 +39,11 @@ En el Admin puedes crear páginas de destino personalizadas, como páginas para
 
 >⚠️ Para evitar conflictos y garantizar la integridad del sistema, no se permite modificar la URL de una ruta existente. Si es necesario modificarla, se recomienda crear una nueva página con la nueva ruta y, de ser necesario, desactivar la anterior.
 
-<div class = "alert alert-info">
-<p>Los cinco campos anteriores impactan directamente en los accesos a la tienda y en el posicionamiento en las páginas de resultados de los motores de búsqueda. Antes de rellenar los metadatos de la página, ten en cuenta las mejores prácticas de SEO.
-</p>
-</div>
+>ℹ️ Los cinco campos anteriores impactan directamente en los accesos a la tienda y en el posicionamiento en las páginas de resultados de los motores de búsqueda. Antes de rellenar los metadatos de la página, ten en cuenta las mejores prácticas de SEO.
 
 4.Elige un template para tu nueva página de destino desde el menú desplegable **Templates**.
 
-<div class = "alert alert-info">
-  <p>Si deseas crear un template condicional, haz clic en <strong>Agregar template condicional</strong> y rellena los campos según las condiciones deseadas. Ten en cuenta que el template condicional solo se mostrará cuando una o todas las condiciones predefinidas coincidan en la interfaz.
-</p>
-</div>
+>ℹ️ Si deseas crear un template condicional, haz clic en **Agregar template condicional** y rellena los campos según las condiciones deseadas. Ten en cuenta que el template condicional solo se mostrará cuando una o todas las condiciones predefinidas coincidan en la interfaz.
 
 5.Guarda los cambios.
 
diff --git a/docs/tutorials/es/creating-pickup-points.md b/docs/tutorials/es/creating-pickup-points.md
index 45955dc0a..6d21eefbe 100644
--- a/docs/tutorials/es/creating-pickup-points.md
+++ b/docs/tutorials/es/creating-pickup-points.md
@@ -52,9 +52,7 @@ Selecciona <i class="fas fa-toggle-on"></i> para activar el punto de recogida.
 * Para editar la información de la dirección, haz clic en `Editar`. 
 * Para añadir una dirección diferente, haz clic en `Borrar` y vuelve a realizar la búsqueda.
 
-<div class = "alert alert-info">
-La información de la dirección y la ubicación en el mapa se mostrarán en el checkout. 
-</div>
+>ℹ️ La información de la dirección y la ubicación en el mapa se mostrarán en el checkout.
 
 #### Información adicional
 
@@ -65,7 +63,7 @@ La información de la dirección y la ubicación en el mapa se mostrarán en el
 
 * **Días de la semana:**
     1. Marca las casillas de los días en que el punto de recogida estará disponible para que tus clientes recojan sus pedidos. 
-    2. Selecciona también las horas labolables del punto de recogida para cada día. <div class = "alert alert-info">Si este campo no se rellena, la plataforma considerará que el punto de recogida funciona las 24 horas del día. </div>
+    2. Selecciona también las horas labolables del punto de recogida para cada día. >ℹ️ Si este campo no se rellena, la plataforma considerará que el punto de recogida funciona las 24 horas del día.
 * **Excepciones o feriados**: para añadir días específicos en los que el punto de recogida no funcionará, sigue los pasos a continuación:
     1. Haz clic en `Agregar excepción`.
     2. Rellena el **día** y la **hora**;
@@ -77,15 +75,12 @@ La información de la dirección y la ubicación en el mapa se mostrarán en el
 
 Es posible registrar los puntos de recogida mediante la importación de una plantilla (archivo XLS). Esto te permite registrar más de un punto de recogida a la vez.
 
-<div class = "alert alert-info">
-El archivo XLS no debe superar los 10 MB (aproximadamente 50.000 puntos de recogida). Si es necesario, registra más de una plantilla. 
-</div>
+>ℹ️ El archivo XLS no debe superar los 10 MB (aproximadamente 50.000 puntos de recogida). Si es necesario, registra más de una plantilla.
 
 1. En el Admin VTEX, accede a **Envío > Puntos de recogida**, o escribe *Puntos de recogida* en la barra de búsqueda en la parte superior de la página.  
 2. Haz clic en <i class="fas fa-upload"></i> `Cargar un XLS`.
 3. Descarga la plantilla y rellena los 
-[campos](#campos-de-la-plantilla).<div class = "alert alert-info">
-Ten en cuenta que la plantilla viene con valores de ejemplo, que debes sustituir por los datos de los puntos de recogida de tu tienda.</div>
+[campos](#campos-de-la-plantilla).>ℹ️ Ten en cuenta que la plantilla viene con valores de ejemplo, que debes sustituir por los datos de los puntos de recogida de tu tienda.
 4. Tras cargar la plantilla, haz clic en `OK`. Se habrán registrado los puntos de recogida. 
 
 ### Campos de la plantilla
diff --git a/docs/tutorials/es/creating-price-tables.md b/docs/tutorials/es/creating-price-tables.md
index 07cb62a86..af0d5cc7f 100644
--- a/docs/tutorials/es/creating-price-tables.md
+++ b/docs/tutorials/es/creating-price-tables.md
@@ -32,12 +32,8 @@ Para encontrar una Tabla de Precio:
 
 Para añadir precios en la tabla de precios, registra un precio base a sus SKU. Mira como hacerlo en este [tutorial](https://help.vtex.com/es/tutorial/registrar-el-precio-base-de-un-producto--4S9SbPWlVmOAAWO6yq8wE6).
 
-<div class = "alert alert-info">
-No puede crear tablas de precio con nombres iguales.
-No se pueden añadir caracteres especiales a los nombres de las tablas de precios. Sólo letras y números.
-</div>
-
-<div class = "alert alert-warning">
-Por motivos de seguridad, no se puede eliminar tablas de precio manualmente. Si necesita borrar una tabla de precios, abra una llamada con el soporte de VTEX.
-</div>
+>ℹ️ No puede crear tablas de precio con nombres iguales.
+> No se pueden añadir caracteres especiales a los nombres de las tablas de precios. Sólo letras y números.
+
+>⚠️ Por motivos de seguridad, no se puede eliminar tablas de precio manualmente. Si necesita borrar una tabla de precios, abra una llamada con el soporte de VTEX.
 
diff --git a/docs/tutorials/es/creating-service-for-a-sku.md b/docs/tutorials/es/creating-service-for-a-sku.md
index 5dc825dd1..97114f6ef 100644
--- a/docs/tutorials/es/creating-service-for-a-sku.md
+++ b/docs/tutorials/es/creating-service-for-a-sku.md
@@ -75,9 +75,7 @@ Para vincular un servicio a un SKU, sigue los pasos a continuación:
 5. Haz clic en `Exportar`.
 6. Guarda la plantilla en formato CSV que se exportará en su ordenador.
 7. Rellena los [campos de la plantilla](#campos-de-la-plantilla). Mantén el formato CSV del archivo al guardar los cambios.
-<div class = "alert alert-warning">
-  <p>El tamaño del archivo de la plantilla no debe superar los 4Mb (4096KB).</p>
-</div>
+>⚠️ El tamaño del archivo de la plantilla no debe superar los 4Mb (4096KB).
 8. Haz clic en la barra que se encuentra junto al botón `Select`, que se muestra a continuación.
   ![Anexos - ES](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/844c4cb0282e3b4e32c9b494906b0597/sku-services-ES.png)
 9. Selecciona la plantilla CSV actualizada.
@@ -103,6 +101,4 @@ Maneja la plantilla con cuidado, comprobando siempre que la información está c
 - **Custo:** es el costo del servicio para la tienda.
 - **Ativo:** es el status del servicio. Introduce `1` para mantener el servicio activo y `0` para mantenerlo inactivo.
 
-<div class = "alert alert-warning">
-  <p>Añadir una nueva plantilla no sustituirá los servicios ya vinculados al SKU. Para desvincular un servicio, utiliza el <i>endpoint</i> <a href ="https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/skuservice/-skuServiceId-">Dissociate SKU Service</a>.</p>
-</div>
+>⚠️ Añadir una nueva plantilla no sustituirá los servicios ya vinculados al SKU. Para desvincular un servicio, utiliza el <i>endpoint</i> <a href ="https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/skuservice/-skuServiceId-">Dissociate SKU Service</a>.
diff --git a/docs/tutorials/es/creating-synonyms.md b/docs/tutorials/es/creating-synonyms.md
index 5a2830a29..5aa59e6c0 100644
--- a/docs/tutorials/es/creating-synonyms.md
+++ b/docs/tutorials/es/creating-synonyms.md
@@ -15,7 +15,7 @@ legacySlug: configurar-sinonimos
 subcategory: BBzMtJan1UTxC9QZODnlN
 ---
 
-<div class = "alert alert-info"> Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ">Sinónimos</a> en lugar de <a href="https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palabras sustitutas</a> para asociar palabras con productos, ya que los sinónimos permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>. </div>
+>ℹ️ Recomendamos usar [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ) en lugar de [Palabras sustitutas](https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete) para asociar palabras con productos, ya que los sinónimos permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con [nuestro equipo de soporte](https://support.vtex.com/hc/es/requests).
 
 Hay dos formas de configurar sinónimos en VTEX Admin: [individualmente](#crear-sinonimos-individualmente) o [importando una hoja de cálculo en formato CSV](#). Si necesita registrar sinónimos en bloque, le recomendamos que utilice la hoja de cálculo. Consulte las instrucciones para cada método de configuración en las secciones siguientes.
 
diff --git a/docs/tutorials/es/data-subject-rights.md b/docs/tutorials/es/data-subject-rights.md
index c1aec6104..c8cef7f40 100644
--- a/docs/tutorials/es/data-subject-rights.md
+++ b/docs/tutorials/es/data-subject-rights.md
@@ -57,9 +57,7 @@ Para exportar datos de Master Data v1 a través del dashboard del Admin, sigue l
 
 Repite estos pasos para las entidades de datos de clientes (**CL**), direcciones (**AD**) y cualquier otra que hayas configurado para recibir datos personales de los clientes.
 
-<div class = "alert alert-info">
-Aprende más sobre cómo <a href="https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters">filtrar datos</a> y <a href="https://help.vtex.com/es/tutorial/exporting-data--tutorials_1125">exportar datos</a> en la interfaz de Master Data v1.
-</div>
+>ℹ️ Aprende más sobre cómo [filtrar datos](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) y [exportar datos](https://help.vtex.com/es/tutorial/exporting-data--tutorials_1125) en la interfaz de Master Data v1.
 
 #### Master Data v2
 
@@ -87,9 +85,7 @@ Tus clientes pueden ejercer su derecho de consentimiento y rectificación de dat
 - Ver y editar sus direcciones registradas.
 - Ver y editar sus medios de pago registrados.
 
-<div class = "alert alert-info">
-Aprende más sobre la <a href="https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh">página Mi Cuenta</a>.
-</div>
+>ℹ️ Aprende más sobre la [página Mi Cuenta](https://help.vtex.com/es/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh).
 
 ## Consentimiento
 
@@ -103,9 +99,7 @@ Al finalizar una compra en el checkout VTEX, tus clientes pueden elegir suscribi
 
 De ser necesario, tu equipo de desarrollo puede [ajustar directamente la opción de inscripción de un cliente específico](https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1) mediante la API de Master Data v1.
 
-<div class = "alert alert-info">
-Aprende más sobre la página Mi cuenta[7] . Observa también cómo tu equipo de desarrollo puede <a href="https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1">ajustar directamente la inscripción de un cliente en el newsletter</a>.
-</div>
+>ℹ️ Aprende más sobre la página Mi cuenta[7] . Observa también cómo tu equipo de desarrollo puede [ajustar directamente la inscripción de un cliente en el newsletter](https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1).
 
 ### Carrito abandonado
 
@@ -125,9 +119,7 @@ El derecho de consentimiento permite que las personas realicen compras en tu tie
 
 Ponte en contacto con tu equipo de desarrollo para proporcionar esta opción según la guía [Activar la opción de guardar datos del usuario](https://developers.vtex.com/docs/guides/enable-the-save-user-data-opt-in).
 
-<div class = "alert alert-info">
-Aprende más sobre la <a href="https://help.vtex.com/es/tutorial/configurar-carrinho-abandonado--tutorials_740">automatización de carritos abandonados</a>.
-</div>
+>ℹ️ Aprende más sobre la [automatización de carritos abandonados](https://help.vtex.com/es/tutorial/configurar-carrinho-abandonado--tutorials_740).
 
 ## Eliminación
 
diff --git a/docs/tutorials/es/declining-order-cancelation.md b/docs/tutorials/es/declining-order-cancelation.md
index 3d76dca05..52f1f5827 100644
--- a/docs/tutorials/es/declining-order-cancelation.md
+++ b/docs/tutorials/es/declining-order-cancelation.md
@@ -23,13 +23,9 @@ En el flujo de pedidos hay un [periodo de cancelación](https://help.vtex.com/es
 
 Para contenido para desarrolladores, consulte [Order canceling improvements](https://developers.vtex.com/docs/guides/order-canceling-improvements).
 
-<div class = "alert alert-info">
-En este artículo, los términos marketplace y seller se refieren a <a href="https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace">marketplace VTEX</a> y <a href="https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-seller">seller VTEX</a>. La funcionalidad de denegar solicitudes de cancelación de pedidos no está disponible para sellers o marketplaces externos.
-</div>
+>ℹ️ En este artículo, los términos marketplace y seller se refieren a [marketplace VTEX](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-marketplace) y [seller VTEX](https://help.vtex.com/es/tutorial/marketplace-strategies-at-vtex--tutorials_402#being-a-vtex-seller). La funcionalidad de denegar solicitudes de cancelación de pedidos no está disponible para sellers o marketplaces externos.
 
-<div class = "alert alert-warning">
-No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
-</div>
+>⚠️ No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Diagrama de denegación de cancelación de pedidos
 
diff --git a/docs/tutorials/es/defining-window-displays.md b/docs/tutorials/es/defining-window-displays.md
index ff3b7f976..2e4f4b925 100644
--- a/docs/tutorials/es/defining-window-displays.md
+++ b/docs/tutorials/es/defining-window-displays.md
@@ -15,9 +15,7 @@ legacySlug: definicion-de-vitrinas
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 Las vitrinas se usan en el destaque de productos en diversas páginas, se pueden usar también para recomendaciones, en la página del producto.
 
diff --git a/docs/tutorials/es/deleting-a-folder-from-cms.md b/docs/tutorials/es/deleting-a-folder-from-cms.md
index 8c149548b..d385adb01 100644
--- a/docs/tutorials/es/deleting-a-folder-from-cms.md
+++ b/docs/tutorials/es/deleting-a-folder-from-cms.md
@@ -27,9 +27,11 @@ Para borrar una carpeta de CMS, siga los pasos abajo:
 
 ![erroDeletarPasta2](https://images.contentful.com/alneenqid6w5/5LV3bGobResaCycAs4e4oS/0644cad6454dd3d6c0beb1eb8afc1da8/erroDeletarPasta2.png)
 
-<div class = "alert alert-danger">
-Algunas carpetas son obligatorias. Su tienda no funcionará correctamente sin ellas. Otras son importantes, así que no es una buena idea borrarlas.<br><br>Para entender mejor este asunto, lea el artículo <a href="http://help.vtex.com/es/tutorial/estructura-de-carpetas-de-cms">Estructura de carpetas de CMS</a>.
-</div>
+>❗ Algunas carpetas son obligatorias. Su tienda no funcionará correctamente sin ellas. Otras son importantes, así que no es una buena idea borrarlas.
+>
+> 
+>
+> Para entender mejor este asunto, lea el artículo [Estructura de carpetas de CMS](http://help.vtex.com/es/tutorial/estructura-de-carpetas-de-cms).
 
 Si una carpeta contiene otras carpetas, antes de borrarla es necesario borrar todas las carpetas internas. En caso contrario, el sistema devuelve el error "Object reference not set to an instance of an object", como en la siguiente imagen.
 
diff --git a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
index a2baf35f1..1ecd12619 100644
--- a/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/es/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -15,9 +15,7 @@ legacySlug: mostrar-anuncios-de-vtex-ad-network-en-tu-tienda-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 [VTEX Ad Network (Beta)](https://help.vtex.com/es/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur) les permite a los retailers VTEX disponibilizar espacio publicitario para que las marcas promocionen productos en tu tienda. VTEX seleccionará anuncios de productos que ya sean parte de tu catálogo y tu tienda recibirá una comisión por cada clic en los anuncios de tu storefront.
 
diff --git a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
index 9190f5539..884627e1a 100644
--- a/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/es/dynamic-relevance-in-intelligent-search-beta.md
@@ -30,9 +30,7 @@ En Intelligent Search, hay dos formas de configurar la relevancia de búsqueda:
 
 Solamente una de ellas se aplica a tu tienda por vez, pero puedes [cambiar el tipo de relevancia](#cambiar-el-tipo-de-relevancia) configurado. Si cambias la relevancia manual a dinámica, todas las reglas manuales ya registradas se seguirán guardando.
 
-<div class = "alert alert-info">
-La relevancia manual está configurada como predeterminada en la tienda.
-</div>
+>ℹ️ La relevancia manual está configurada como predeterminada en la tienda.
 
 ## Manual 
 
@@ -67,9 +65,7 @@ Para activar la relevancia dinámica, sigue estos pasos:
 
 Para cambiar el tipo de relevancia sigue los pasos a continuación:
 
-<div class = "alert alert-warning">
-No recomendamos cambiar constantemente el tipo de relevancia que utiliza tu tienda. El sistema necesita una semana para asentarse.
-</div>
+>⚠️ No recomendamos cambiar constantemente el tipo de relevancia que utiliza tu tienda. El sistema necesita una semana para asentarse.
 
 1. En el Admin VTEX, accede a **Storefront > Intelligent Search > Reglas de relevancia**  o ingresa **Reglas de relevancia** en la barra de búsqueda de la parte superior de la página.
 2. Haz clic en `Cambiar`.
diff --git a/docs/tutorials/es/events-available-in-audit.md b/docs/tutorials/es/events-available-in-audit.md
index 6ace6e0f4..f7fc8738e 100644
--- a/docs/tutorials/es/events-available-in-audit.md
+++ b/docs/tutorials/es/events-available-in-audit.md
@@ -35,9 +35,7 @@ A continuación, verás la lista de posibles eventos disponibles en [Audit] (htt
 * [Headless CMS](#headless-cms)
 * [Gestión de sellers](#gestion-de-sellers)
 
-<div class = "alert alert-info">
-Si, en Audit, ves algún evento no incluido en esta lista, por favor, envíanos más información a través de la <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback sobre documentación</a>.
-</div>
+>ℹ️ Si, en Audit, ves algún evento no incluido en esta lista, por favor, envíanos más información a través de la [página de feedback sobre documentación](https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform).
 
 >⚠️ En el módulo Audit, al hacer clic en los filtros de auditoría puedes encontrar **Opciones de envío**, **Profile System** y **Billing**, además de otras aplicaciones citadas a continuación. Estas opciónes se refieren a recursos internos o funcionalidades en beta cerrada, por lo que la mayoría de las cuentas no tendrán eventos asociados.
 
diff --git a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
index a7edf30f0..64f736b48 100644
--- a/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/es/exporting-and-importing-product-and-sku-specifications.md
@@ -21,9 +21,7 @@ En este artículo, explicamos cómo funciona la exportación e importación de p
 
 Para exportar e importar especificaciones mediante la API del catálogo, siga la guía para desarrolladores Cómo crear una especificación.
 
-<div class = "alert alert-info">
-  <p>Para exportar e importar especificaciones mediante la <strong>Catalog API</strong>, siga la guía para desarrolladores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a> (Cómo crear una especificación).</p>
-</div>
+>ℹ️ Para exportar e importar especificaciones mediante la **Catalog API**, siga la guía para desarrolladores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification) (Cómo crear una especificación).
 
 ## Exportar especificaciones de producto o SKU
 
@@ -41,9 +39,7 @@ Vea a continuación cómo exportar la plantilla con las especificaciones del pro
 
 ![skuexport2.es](https://images.ctfassets.net/alneenqid6w5/6aQThG8rLVv6c48ZAO1in4/eeb2118c25334f4b18d485b2c2127cd5/skuexport2.es.png)
 
-<div class = "alert alert-info">
-  <p>La hoja de plantilla exportada estará disponible en tu email durante una semana. Si supera este periodo, vuelva a seguir la exportación paso a paso para generar una nueva hoja de plantilla.</p>
-</div>
+>ℹ️ La hoja de plantilla exportada estará disponible en tu email durante una semana. Si supera este periodo, vuelva a seguir la exportación paso a paso para generar una nueva hoja de plantilla.
 
 ## Importar especificaciones de producto o SKU
 
diff --git a/docs/tutorials/es/filling-out-collection-registration-fields.md b/docs/tutorials/es/filling-out-collection-registration-fields.md
index 9fbc7780e..f47cc14a2 100644
--- a/docs/tutorials/es/filling-out-collection-registration-fields.md
+++ b/docs/tutorials/es/filling-out-collection-registration-fields.md
@@ -15,9 +15,7 @@ legacySlug: rellenar-campos-de-registro-de-coleccion
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 Para entender mejor el significado de los campos de registro de una colección de productos, vea a continuación la descripción completa de cada uno de estos:
 
diff --git a/docs/tutorials/es/filtering-all-orders.md b/docs/tutorials/es/filtering-all-orders.md
index ffe812366..b8a6685e6 100644
--- a/docs/tutorials/es/filtering-all-orders.md
+++ b/docs/tutorials/es/filtering-all-orders.md
@@ -15,9 +15,7 @@ legacySlug: como-filtrar-pedidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class = "alert alert-info">
-Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
-</div>
+>ℹ️ Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 En el módulo **Pedidos**, la página **Todos los pedidos** permite acceder a todos los pedidos de la tienda y buscar utilizando la barra de búsqueda y filtros según se muestra en la imagen a continuación:
 
@@ -49,9 +47,7 @@ Para realizar una búsqueda en la barra de búsqueda, ingresa el término desead
 
 El [sequence](https://help.vtex.com/es/tutorial/cuidados-ao-definir-a-numeracao-de-pedido--VAKKptfcaOxFxM8gfPobu) es una secuencia de seis dígitos que aparece en el Admin VTEX justo después del ID del pedido. Por ejemplo, en el pedido `1268540501456-01 (501456)`, el ID del pedido es `1268540501456`, el `-01` indica que el cumplimiento será realizado por un seller y el sequence es `501456`.
 
-<div class = "alert alert-info">
-Además de los criterios enumerados anteriormente, es posible activar otros criterios de búsqueda, como se verá en la sección <a href="https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-otros">Otros</a>.
-</div>
+>ℹ️ Además de los criterios enumerados anteriormente, es posible activar otros criterios de búsqueda, como se verá en la sección [Otros](https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-otros).
 
 De forma predeterminada, la página **Todos los pedidos** se muestra con el filtro de pedidos creados **Hoy** activado. Para buscar otras fechas, utiliza los filtros descritos en [Filtros: Fechas](#filtros-fechas) y [Creado](#creado).
 
@@ -90,9 +86,7 @@ Al hacer clic en `Filtros`, se muestra una ventana modal que presenta las siguie
 
 Para que se aplique un filtro a la búsqueda, selecciona la opción deseada y haz clic en **Aplicar**. Para remover los filtros aplicados, haz clic en **Limpiar filtros > Aplicar**.
 
-<div class = "alert alert-info">
-De forma predeterminada, la opción <i class="fas fa-toggle-on"></i> <b>Utilizar mi zona horaria: GMT-3</b> aparece activada para todos los filtros. Cuando se desactiva, la referencia de zona horaria cambia a GMT-0 y, si se vuelve a activar, se convierte en la zona horaria utilizada por el navegador del usuario.
-</div>
+>ℹ️ De forma predeterminada, la opción <i class="fas fa-toggle-on"></i> **Utilizar mi zona horaria: GMT-3** aparece activada para todos los filtros. Cuando se desactiva, la referencia de zona horaria cambia a GMT-0 y, si se vuelve a activar, se convierte en la zona horaria utilizada por el navegador del usuario.
 
 Si no hay ninguna coincidencia para la combinación de filtros utilizada, la búsqueda no devuelve ningún pedido en la pantalla.
 
@@ -199,9 +193,7 @@ La página **Pedidos > Todos los pedidos** tiene la opción `Filtrar por status`
 
 Al hacer clic en `Filtrar por status` <i class="fas fa-angle-down"></i>, se muestran las opciones de [status de pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196) de tu tienda. Por ejemplo, si no hay pedidos cancelados entre todos tus pedidos, esta opción no estará visible.
 
-<div class = "alert alert-info">
-Para más opciones de filtros de status, consulta la sección <a href="https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-status">Filtros: Status</a>. Si deseas ver todos los status de pedidos que hay, consulta el artículo <a href="https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196">Flujo y status de pedidos</a>.
-</div>
+>ℹ️ Para más opciones de filtros de status, consulta la sección [Filtros: Status](https://help.vtex.com/es/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-status). Si deseas ver todos los status de pedidos que hay, consulta el artículo [Flujo y status de pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
 
 ## Creado
 
@@ -217,8 +209,6 @@ Este filtro tiene la fecha **Hoy** activada como estándar, pero al hacer clic a
 - Mes actual
 - Últimos 30 días
 
-<div class = "alert alert-info">
-De forma predeterminada, la opción <i class="fas fa-toggle-on"></i> <b>Utilizar mi zona horaria: GMT-3</b> está activada. Cuando se desactiva, la referencia de zona horaria cambia a GMT-0 y, si se vuelve a activar, se convierte en la zona horaria utilizada por el navegador del usuario.
-</div>
+>ℹ️ De forma predeterminada, la opción <i class="fas fa-toggle-on"></i> **Utilizar mi zona horaria: GMT-3** está activada. Cuando se desactiva, la referencia de zona horaria cambia a GMT-0 y, si se vuelve a activar, se convierte en la zona horaria utilizada por el navegador del usuario.
 
 Para ver más opciones de filtros de fechas y periodos, consulta la sección [Filtros: Fechas](#filtros-fechas).
diff --git a/docs/tutorials/es/forcing-searches-with-blocked-terms-to-return-results.md b/docs/tutorials/es/forcing-searches-with-blocked-terms-to-return-results.md
index ec8b18828..59aa27747 100644
--- a/docs/tutorials/es/forcing-searches-with-blocked-terms-to-return-results.md
+++ b/docs/tutorials/es/forcing-searches-with-blocked-terms-to-return-results.md
@@ -15,9 +15,7 @@ legacySlug: forzar-busquedas-con-terminos-bloqueados-a-devolver-resultados
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Para hacer las búsquedas de los clientes más precisas, el buscador de VTEX ignora algunos términos que son muy comunes. Ejemplos incluyen las palabras "com" y "todo", del portugués, "that" y "with", del Inglés, y "hace" y "uno", del español. [Aquí tienes la lista completa de términos bloqueados](/es/tutorial/por-que-el-buscador-de-vtex-ignora-algunos-terminos-buscados).
 
diff --git a/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
index bfd39f900..cc5fa3b1b 100644
--- a/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/es/frequently-asked-questions-new-orders-module-interface.md
@@ -32,9 +32,7 @@ En la imagen a continuación, puedes ver la correspondencia de secciones y campo
 
 El filtro de seis meses fue sustituido por la búsqueda sin límite de fecha que devuelve los pedidos relacionados con el criterio utilizado, independientemente de la fecha de creación del pedido. Por ejemplo, puedes acceder al historial de compras completo de un cliente utilizando su nombre, email o documento. Aprende más en el artículo [Filtrar pedidos en Todos los pedidos](https://help.vtex.com/es/tutorial/como-filtrar-pedidos--tutorials_192).
 
-<div class = "alert alert-info">
-La búsqueda en todos los pedidos no puede asociarse a otros filtros, por lo que al remover el límite de fechas de búsqueda, los demás filtros se inactivan. Sin embargo, puedes combinar filtros y seleccionar el periodo personalizado de seis meses.
-</div>
+>ℹ️ La búsqueda en todos los pedidos no puede asociarse a otros filtros, por lo que al remover el límite de fechas de búsqueda, los demás filtros se inactivan. Sin embargo, puedes combinar filtros y seleccionar el periodo personalizado de seis meses.
 
 Para buscar en todos los pedidos, ingresa el término deseado en la casilla de búsqueda. Se mostrará la opción <i class="fas fa-toggle-off"></i> `Remover límite de fechas`. Solo tienes que activarla para iniciar la búsqueda.
 
diff --git a/docs/tutorials/es/fulfillment-logistics-vtex.md b/docs/tutorials/es/fulfillment-logistics-vtex.md
index 2ee8a8aa3..c5cc91b4e 100644
--- a/docs/tutorials/es/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/es/fulfillment-logistics-vtex.md
@@ -20,10 +20,9 @@ La logística o fulfillment es el proceso de planificación y ejecución del tra
 
 VTEX te permite registrar e controlar el _stock_, gestionar las tarifas de envío, controlar la disponibilidad de los ítems y hacer el seguimiento de las entregas. 
 
-<div class = "alert alert-info"> Si tu tienda no ha dado los primeros pasos en el módulo de <b>Envío</b>, consulta el artículo <a href="https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a">Logística: primeros pasos</a>.
-Consulta el artículo <a href="https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby">Glosario de logística</a> para consultar el significado de los términos logísticos utilizados en VTEX.
-Las configuraciones logísticas disponibles mediante <a href="https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview">API</a>. 
-</div>
+>ℹ️ Si tu tienda no ha dado los primeros pasos en el módulo de **Envío**, consulta el artículo [Logística: primeros pasos](https://help.vtex.com/es/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a).
+> Consulta el artículo [Glosario de logística](https://help.vtex.com/en/tutorial/logistics-glossary--16DSSiXn548rsidi0A8Hby) para consultar el significado de los términos logísticos utilizados en VTEX.
+> Las configuraciones logísticas disponibles mediante [API](https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview).
 
 Para saber qué configuraciones logísticas son necesarias y cómo realizarlas, primero hay que entender los pasos del flujo de compra de un producto:
 
@@ -44,8 +43,7 @@ Para saber qué configuraciones logísticas son necesarias y cómo realizarlas,
     * En el caso de los pedidos que se envían a los [puntos de recogida](https://help.vtex.com/es/tutorial/como-funcionan-puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R) (recogida), la tienda debe dejar los paquetes disponibles para que el cliente los recoja. Para ello, los paquetes se sacan del [almacén](https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb) y se transportan al punto de recogida. El transporte desde el muelle hasta el punto de recogida se define por una[ política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140).
 8. Tras la facturación y el envío, la tienda se encarga de actualizar el _stock_, lo que para la plataforma significa también dar de baja a los ítems en el _stock_.
 
-<div class = "alert alert-info">Ten en cuenta que el proceso de envío dependerá de la configuración realizada en la plataforma. Aquí presentamos los escenarios para cada tipo de envío (entrega y recogida), pero hay otros flujos posibles en el proceso de envío. Por ejemplo, cuando se realiza el envío por recogida y el almacén coincide con el punto de recogida, no es necesario transportar los paquetes entre estos lugares.
-</div>
+>ℹ️ Ten en cuenta que el proceso de envío dependerá de la configuración realizada en la plataforma. Aquí presentamos los escenarios para cada tipo de envío (entrega y recogida), pero hay otros flujos posibles en el proceso de envío. Por ejemplo, cuando se realiza el envío por recogida y el almacén coincide con el punto de recogida, no es necesario transportar los paquetes entre estos lugares.
 
 ![Envio ES](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/b45650074aea4947a048e8140434fa46/Envio_ES.svg)
 ## Configuración del proceso logístico
diff --git a/docs/tutorials/es/gift-card.md b/docs/tutorials/es/gift-card.md
index 93e539f2f..a62496d03 100644
--- a/docs/tutorials/es/gift-card.md
+++ b/docs/tutorials/es/gift-card.md
@@ -32,9 +32,7 @@ Para crear un nuevo vale de compra, siga los pasos a continuación:
   <br>
   <li>Haga clic en el botón azul <b>Nuevo vale</b>.</li>
   <br>   
-<div class = "alert alert-info">
-  <p>En la pantalla de creación del vale, el campo <b>Vale</b> es llenado automáticamente por el sistema VTEX con el código ID del nuevo vale. Este es el código que debe ingresar el cliente en la pantalla de checkout para aplicar el vale al carrito y reducir el valor de pago del pedido.</p>
-</div>
+>ℹ️ En la pantalla de creación del vale, el campo **Vale** es llenado automáticamente por el sistema VTEX con el código ID del nuevo vale. Este es el código que debe ingresar el cliente en la pantalla de checkout para aplicar el vale al carrito y reducir el valor de pago del pedido.
 <br>
   <li>Complete los campos presentados de acuerdo con las orientaciones que se indican a continuación:</li>
   <br>
diff --git a/docs/tutorials/es/google-analytics-faq.md b/docs/tutorials/es/google-analytics-faq.md
index 16742f4de..443f5400a 100644
--- a/docs/tutorials/es/google-analytics-faq.md
+++ b/docs/tutorials/es/google-analytics-faq.md
@@ -50,9 +50,7 @@ Como VTEX procesa las transacciones de tu tienda, todas las transacciones se reg
 - La tag de transacción se activa incluso con transacciones que no se completaron con éxito.
 - Falla o duplicación de la visualización de la página de confirmación del pedido, si la tag de transacción está vinculada a la visualización de esta página.
 
-<div class = "alert alert-info">
-También debes tener en cuenta que hay un retraso de hasta 48 horas en el registro de datos de transacciones en Google Analytics.
-</div>
+>ℹ️ También debes tener en cuenta que hay un retraso de hasta 48 horas en el registro de datos de transacciones en Google Analytics.
 
 Además, las integraciones pueden construirse de forma que acaben por no desencadenar determinadas etiquetas en tu storefront. Por ejemplo, hay integraciones que utilizan una [aplicación de pago](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-app) y finalizan la compra sin redirigir al cliente a la página de confirmación del pedido, como la integración desarrollada por AME Digital. Las transacciones siempre se registrarán en VTEX, pero en este caso es probable que no se registre en Google Analytics, generando divergencias.
 
diff --git a/docs/tutorials/es/google-pay-beta.md b/docs/tutorials/es/google-pay-beta.md
index 359632e9c..98e9de78f 100644
--- a/docs/tutorials/es/google-pay-beta.md
+++ b/docs/tutorials/es/google-pay-beta.md
@@ -15,9 +15,7 @@ legacySlug: google-pay-beta
 subcategory: 3lZEaiSilZPwa3eCUUzwyr
 ---
 
-<div class = "alert alert-info">
-Este módulo se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Si tienes alguna duda, ponte en contacto <a href="https://help.vtex.com/es/support">con nuestro Soporte. </a>
-</div>
+>ℹ️ Este módulo se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Si tienes alguna duda, ponte en contacto [con nuestro Soporte. ](https://help.vtex.com/es/support)
 
 Google Pay™ es un servicio de pagos digitales que permite a los usuarios no compartir los datos reales de su tarjeta con la tienda, aportando más seguridad y agilizando la fase de checkout. Con Google Pay, el usuario puede realizar pagos utilizando tarjetas de crédito o débito, sin necesidad de rellenar ningún dato manualmente, y Google Pay también está disponible en muchas aplicaciones, sitios web y Catera Google. 
 
@@ -32,26 +30,20 @@ Para activar Google Pay, sigue los pasos a continuación.
 1. En el Admin VTEX, haz clic en el ícono del engranaje **Configuración de la tienda > Pago > Carteras** o ingresa. **Carteras** en la barra de búsqueda de la parte superior de la página.
 2. Selecciona la opción **Activar** para modificar el checkout e incluir la extensión de Google Pay.
 
-<div class = "alert alert-info">
-<p>Las redes admitidas en Google Pay son las mismas configuradas en las condiciones de pago.</p>
-</div>
+>ℹ️ Las redes admitidas en Google Pay son las mismas configuradas en las condiciones de pago.
 
 Una vez hecho esto, Google Pay estará disponible en el checkout de tu tienda VTEX como nuevo medio de pago. La configuración puede demorarse alrededor de 10 minutos en aparecer en el checkout.
 
 ![google pay - ES](https://images.ctfassets.net/alneenqid6w5/IhdcOpZC0MPaZLYbPUYw1/fc1aa919d82b228ed26d2a967f4a4064/image.png)
 
-<div class = "alert alert-warning">
-<p>Google Pay, por el momento, no admite suscripciones.</p>
-</div>
+>⚠️ Google Pay, por el momento, no admite suscripciones.
 
 Para utilizar Google Pay deben cumplirse los siguientes requisitos:
 
 * Tener al menos una [condición de pago](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/6bzGxlz4inf8sKmvZ1c7i3) activa configurada para tarjetas de crédito o débito con un adquirente, definiendo qué [adquirente](https://help.vtex.com/es/tracks/pagamentos--6GAS7ZzGAm7AGoEAwDbwJG/kdPbEIWf8Xq8tESQvViMB#adquirente) procesará el pago.
 * Utilizar el [Checkout VTEX](https://help.vtex.com/es/tutorial/checkout-vtex-visao-geral--7wcprkM7yZUflOqbzAN5SI) en tu tienda.
 
-<div class = "alert alert-warning">
-  <p>En las tiendas que tengan el flujo de autenticación <a href="https://help.vtex.com/es/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa">3DS</a> configurado y admitido por el adquirente, el pago con Google Pay seguirá el flujo nativo de la tarjeta y también utilizará 3DS. Para más información sobre este tema, accede a <a href="https://help.vtex.com/es/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2">Configurar flujo de autenticación 3DS 2</a>.</p>
-</div>
+>⚠️ En las tiendas que tengan el flujo de autenticación [3DS](https://help.vtex.com/es/tutorial/o-que-e-3d-secure--1eWPdop8mECuaEomQgkAIa) configurado y admitido por el adquirente, el pago con Google Pay seguirá el flujo nativo de la tarjeta y también utilizará 3DS. Para más información sobre este tema, accede a [Configurar flujo de autenticación 3DS 2](https://help.vtex.com/es/tutorial/configurar-fluxo-de-autenticacao-3ds-2--58XMn5LOA6fwrSkoDoAsg2).
 
 ## Consultar transacciones finalizadas con Google Pay
 
@@ -68,9 +60,7 @@ Para agregar en la plantilla de email que se le enviará al comprador la informa
 
 Así, siempre que haya cualquier mención de los últimos cuatro dígitos de la tarjeta en estas plantillas de email, se añadirá la información «(Google Pay)» si el pago se realizó con cartera digital.
 
-<div class = "alert alert-info">
-  <p>Para tiendas aprovisionadas a partir de marzo de 2023, las plantillas ya estarán actualizadas con la información del pago del pedido realizado con Google Pay.</p>
-</div>
+>ℹ️ Para tiendas aprovisionadas a partir de marzo de 2023, las plantillas ya estarán actualizadas con la información del pago del pedido realizado con Google Pay.
 
 ## Preguntas frecuentes
 
diff --git a/docs/tutorials/es/how-does-reservation-work.md b/docs/tutorials/es/how-does-reservation-work.md
index 45511f57e..7640fc07d 100644
--- a/docs/tutorials/es/how-does-reservation-work.md
+++ b/docs/tutorials/es/how-does-reservation-work.md
@@ -17,10 +17,8 @@ subcategory: 3PQwnyOcNyYgawy06oe6gE
 
 La reserva es una solución VTEX que impide que el mismo ítem se venda más de una vez. Una vez finalizada la compra, el ítem comprado se resta del _stock_ disponible y pasa internamente al status **Reservado**.
 
-<div class = "alert alert-info">
-En VTEX, Almacén es el lugar físico donde se almacenan los ítems. Para que se pueda identificar de qué almacén recogerán los ítems las transportadoras, los almacenes deben estar registrados en la plataforma. Consulta el artículo <a href="https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb">Almacén</a> para obtener más información. 
-<p>El stock es una lista de los ítems que tu tienda tiene en stock. Puedes añadir y hacer un seguimiento de los ítems disponibles en tu tienda a través de la Gestión del stock. Consulta el artículo <a href="https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139">Gestión del stock</a> para obtener más información.
-</div>
+>ℹ️ En VTEX, Almacén es el lugar físico donde se almacenan los ítems. Para que se pueda identificar de qué almacén recogerán los ítems las transportadoras, los almacenes deben estar registrados en la plataforma. Consulta el artículo [Almacén](https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb) para obtener más información. 
+> <p>El stock es una lista de los ítems que tu tienda tiene en stock. Puedes añadir y hacer un seguimiento de los ítems disponibles en tu tienda a través de la Gestión del stock. Consulta el artículo [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139) para obtener más información.
 
 Después de ser vendido, un ítem pasa por los siguientes status en el_ stock _de tu tienda:
 
@@ -93,8 +91,6 @@ Cuando el administrador de la tienda o el ERP actualice la cantidad de ese ítem
 
 Como se ha descrito anteriormente, el status dado de baja en el stock resulta de la actualización del stock por parte del administrador de la tienda. Por lo tanto, no es posible ver este status en la plataforma. Solo puedes consultar la cantidad de ítems disponibles para la venta y el movimiento de los ítems a través de la [Gestión del stock](https://help.vtex.com/es/tutorial/gestionar-items-en-inventario--tutorials_139).
 
-<div class = "alert alert-info">
-Todos los status aquí descritos son internos y exclusivos de VTEX para el control de la venta de los ítems.
-<p>El status de la reserva es una consecuencia del status del pedido. Algunos cambios dependen de acciones de los compradores, y otros de actualizaciones manuales o del ERP.
-</div>
+>ℹ️ Todos los status aquí descritos son internos y exclusivos de VTEX para el control de la venta de los ítems.
+> <p>El status de la reserva es una consecuencia del status del pedido. Algunos cambios dependen de acciones de los compradores, y otros de actualizaciones manuales o del ERP.
 
diff --git a/docs/tutorials/es/how-does-vtex-search-work.md b/docs/tutorials/es/how-does-vtex-search-work.md
index 6cbf50e79..542dd84a8 100644
--- a/docs/tutorials/es/how-does-vtex-search-work.md
+++ b/docs/tutorials/es/how-does-vtex-search-work.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Este artículo tiene el objetivo de describir el funcionamiento del sistema de búsqueda de VTEX.
 
-<div class = "alert alert-warning">
-  VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 ## Cómo el buscador de VTEX prioriza la exhibición de productos
 
diff --git a/docs/tutorials/es/how-mercado-livre-integration-works.md b/docs/tutorials/es/how-mercado-livre-integration-works.md
index 5ff9b507e..3ceb53d03 100644
--- a/docs/tutorials/es/how-mercado-livre-integration-works.md
+++ b/docs/tutorials/es/how-mercado-livre-integration-works.md
@@ -96,9 +96,7 @@ Para poder integrarse, los campos de la plataforma VTEX a continuación deben es
 
 En el campo **Política comercial**, debes marcar la opción correspondiente a [política comercial](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/15NZiQstCET8zyQUIa7nhw) vinculada a Mercado Libre.
 
-<div class = "alert alert-info">
-Para agregar imágenes nuevas en un anuncio que ya existe en Mercado Libre, deberás hacer todos los cambios directamente en el panel del marketplace. Mercado Libre solo acepta 12 imágenes por producto sin variación, y hasta 10 imágenes por producto con variación.
-</div>
+>ℹ️ Para agregar imágenes nuevas en un anuncio que ya existe en Mercado Libre, deberás hacer todos los cambios directamente en el panel del marketplace. Mercado Libre solo acepta 12 imágenes por producto sin variación, y hasta 10 imágenes por producto con variación.
 
 ## 3. Precios
 
diff --git a/docs/tutorials/es/how-my-account-works.md b/docs/tutorials/es/how-my-account-works.md
index 1d7cdd704..ac882e51c 100644
--- a/docs/tutorials/es/how-my-account-works.md
+++ b/docs/tutorials/es/how-my-account-works.md
@@ -26,9 +26,7 @@ Es posible configurar qué pestañas aparecen para el consumidor en las [configu
 - [Suscripciones](#subscripciones)
 - [Autenticación](#autenticacion)
 
-<div class = "alert alert-info">
-Para saper sobre cómo personalizar la funcionalidad <b>Mi cuenta</b>, consulte la documentación para desarrolladores <a href="https://developers.vtex.com/docs/guides/vtex-my-account">My Account - StoreV2 version</a>. Es importante señalar que VTEX no presta soporte a <b>Mi cuenta</b> que es personalizada.
-</div>
+>ℹ️ Para saper sobre cómo personalizar la funcionalidad **Mi cuenta**, consulte la documentación para desarrolladores [My Account - StoreV2 version](https://developers.vtex.com/docs/guides/vtex-my-account). Es importante señalar que VTEX no presta soporte a **Mi cuenta** que es personalizada.
 
 ## Perfil
 
@@ -77,9 +75,7 @@ El botón `Añadir dirección` permite incluir direcciones diferentes a las que
 
 ## Pedidos
 
-<div class = "alert alert-info">
-En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
-</div>
+>ℹ️ En [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), los clientes solo pueden acceder a los pedidos de los últimos dos años.
 
 Esta pestaña proporciona una lista completa de los pedidos realizados por un cliente en su tienda. La lista se ordena por fecha de creación y muestra detalles como la fecha del pedido, el valor total de la compra, el ID del pedido, el _status_ y los ítems comprados.
 
diff --git a/docs/tutorials/es/how-shipping-calculation-works.md b/docs/tutorials/es/how-shipping-calculation-works.md
index d9204d6c5..04c296fb9 100644
--- a/docs/tutorials/es/how-shipping-calculation-works.md
+++ b/docs/tutorials/es/how-shipping-calculation-works.md
@@ -17,9 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Cuando, durante una experiencia de compra, el consumidor ingresa su ubicación en el _checkout_, la plataforma VTEX analiza cuáles son las [estrategias de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) que mejor se adaptan al pedido y ofrece al consumidor las opciones disponibles.
 
-<div class = "alert alert-info">
-En la etapa de la vitrina del flujo de compra, y cuando el consumidor aún no ingresó su domicilio, los productos que aparecen son los de <i>sellers</i> con la funcionalidad <a href="https://help.vtex.com/es/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc">Región</a> configurada o los <a href="https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers de extensa cobertura</a>, es decir, <i>sellers</i> que pueden enviar pedidos a todas las regiones cubiertas por la operación del <i>marketplace</i>.
-</div>
+>ℹ️ En la etapa de la vitrina del flujo de compra, y cuando el consumidor aún no ingresó su domicilio, los productos que aparecen son los de <i>sellers</i> con la funcionalidad [Región](https://help.vtex.com/es/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc) configurada o los [sellers de extensa cobertura](https://help.vtex.com/es/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI), es decir, <i>sellers</i> que pueden enviar pedidos a todas las regiones cubiertas por la operación del <i>marketplace</i>.
 
 Este artículo brinda un panorama general sobre cómo se calcula el envío y se divide en tres secciones:
 
@@ -34,9 +32,7 @@ Para completar el pedido, la tienda configura combinaciones de logística y, par
 - **Entrega:** el consumidor recibe el pedido en el domicilio informado.
 - **Recogida:** el consumidor retira el pedido en un [punto de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R).
 
-<div class = "alert alert-info">
-Los tipos de envío «entrega» y «recogida» siguen los mismos criterios de selección. El envío tipo «recogida» tiene un criterio adicional que mencionaremos más adelante.
-</div>
+>ℹ️ Los tipos de envío «entrega» y «recogida» siguen los mismos criterios de selección. El envío tipo «recogida» tiene un criterio adicional que mencionaremos más adelante.
 
 Para su selección, las combinaciones de logística siguen los criterios y el orden de aplicación que se indica a continuación:
 
@@ -65,9 +61,7 @@ Para su selección, las combinaciones de logística siguen los criterios y el or
   <li><a href="https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW#campos-de-cadastro">Muelles de carga prioritarios</a></li>
 </ul>
 <br>
-  <div class = "alert alert-info">
-Cuando hay un empate entre dos muelles de carga, el criterio de desempate es el <i><a href="https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW">overhead</a></i> o sobrecarga, es decir, el valor en días para elegir el muelle que es más beneficioso para un determinado envío. Cuanto menor sea el overhead o sobrecarga, más posibilidades habrá de que se elija ese muelle. Cabe mencionar que el overhead o sobrecarga no se tiene en cuenta al momento de calcular el tiempo de envío.
-</div>
+  >ℹ️ Cuando hay un empate entre dos muelles de carga, el criterio de desempate es el <i>[overhead](https://help.vtex.com/es/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW)</i> o sobrecarga, es decir, el valor en días para elegir el muelle que es más beneficioso para un determinado envío. Cuanto menor sea el overhead o sobrecarga, más posibilidades habrá de que se elija ese muelle. Cabe mencionar que el overhead o sobrecarga no se tiene en cuenta al momento de calcular el tiempo de envío.
 
 5. **Etapa exclusiva para el envío del tipo «recogida»:** existe un paso adicional en la selección para analizar los [puntos de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R). La plataforma VTEX crea una lista con los puntos de recogida posibles utilizando el criterio de menor distancia entre el punto de recogida y la ubicación del consumidor.
 
@@ -96,9 +90,7 @@ Se utilizan los siguientes campos y parámetros para calcular el SLA:
 
 Se puede obtener una estimación del tiempo de envío a través del [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144), ya que la simulación tiene en cuenta las configuraciones de las [estrategias de envío](https://help.vtex.com/es/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) de la tienda VTEX.
 
-<div class = "alert alert-info">
-El resultado obtenido con el <a href="https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144">Simulador de envío</a> es solo un aproximado, ya que recién en el checkout se conocen los factores determinantes, por ejemplo, la disponibilidad de la transportadora en el horario de la compra, el tiempo de confirmación del pago y el resultado de la <a href="https://help.vtex.com/es/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">selección de sellers white label</a>.
-</div>
+>ℹ️ El resultado obtenido con el [Simulador de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144) es solo un aproximado, ya que recién en el checkout se conocen los factores determinantes, por ejemplo, la disponibilidad de la transportadora en el horario de la compra, el tiempo de confirmación del pago y el resultado de la [selección de sellers white label](https://help.vtex.com/es/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa).
 
 ## Más información	
 
diff --git a/docs/tutorials/es/how-subscriptions-work.md b/docs/tutorials/es/how-subscriptions-work.md
index 6f121f844..9a260873c 100644
--- a/docs/tutorials/es/how-subscriptions-work.md
+++ b/docs/tutorials/es/how-subscriptions-work.md
@@ -45,9 +45,7 @@ Para ello, solo hay que entrar a la página **Mi cuenta** en el sitio web de su
 
 ## Cómo el cliente de su tienda visualiza las Suscripciones
 
-<div class = "alert alert-info">
-En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
-</div>
+>ℹ️ En [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), los clientes solo pueden acceder a los pedidos de los últimos dos años.
 
 Después de finalizar el pedido con Suscripción, su cliente visualiza en la página **Mi cuenta** la sección **Suscripciones**. En esta sección, el cliente también puede encontrar la lista de suscripciones realizadas con los detalles y el estado individual. Su cliente también recibirá por *email* una confirmación de la suscripción y del pedido generado.
 
diff --git a/docs/tutorials/es/how-to-change-order-items.md b/docs/tutorials/es/how-to-change-order-items.md
index f06cd2537..af49e1dd1 100644
--- a/docs/tutorials/es/how-to-change-order-items.md
+++ b/docs/tutorials/es/how-to-change-order-items.md
@@ -26,10 +26,8 @@ Hay dos formas de modificar un pedido:
 
 Es posible editar ítems que aún no fueron facturados en un pedido. Para agregar nuevos ítems, remover ítems o modificar la cantidad de cada uno, realice los siguientes pasos.  
 
-<div class = "alert alert-info">
-Para realizar el cambio, el pedido debe tener el status <code>  «Preparando entrega»</code> equivalente al status <code>«handling» </code> en la <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes">API</a>. Para obtener más información sobre los estados de los pedidos, lea nuestro artículo <a href="https://help.vtex.com/es/tutorial/tabla-de-estados-de-pedidos-oms--frequentlyAskedQuestions_773">Tabla de estados de pedidos</a>.
-Consulte la sección de <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190#restricciones">Restricciones</a> para conocer las condiciones de uso de la funcionalidad.
-</div>
+>ℹ️ Para realizar el cambio, el pedido debe tener el status `  «Preparando entrega»` equivalente al status `«handling» ` en la [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/changes). Para obtener más información sobre los estados de los pedidos, lea nuestro artículo [Tabla de estados de pedidos](https://help.vtex.com/es/tutorial/tabla-de-estados-de-pedidos-oms--frequentlyAskedQuestions_773).
+> Consulte la sección de [Restricciones](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190#restricciones) para conocer las condiciones de uso de la funcionalidad.
 
 1. En el Admin VTEX, accede a **Pedidos > Todos los pedidos**, o escribe **Todos los pedidos** en la barra de búsqueda en la parte superior de la página.  
 2. Busca el pedido en la barra de búsqueda o [usa los filtros](https://help.vtex.com/es/tutorial/como-filtrar-pedidos--tutorials_192) y selecciona el pedido deseado.    
@@ -55,6 +53,4 @@ Al [cambiar o eliminar ítems de un pedido](https://help.vtex.com/es/tutorial/al
 
 El valor total del pedido se actualizará después de que se inserte la factura, y corresponde al valor capturado por el gateway de pagos de VTEX. Si el cliente devuelve un ítem, el reembolso se realizará automáticamente a través del sistema de Pagos de VTEX.
 
-<div class = "alert alert-info">
-La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el <a href="https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Los conectores legados no admiten la funcionalidad.
-</div>
+>ℹ️ La funcionalidad de facturas parciales está disponible para toda la base de clientes VTEX, pero la liquidación parcial en el gateway se encuentra en la versión Beta. Además, para que las facturas parciales disparen liquidaciones parciales en la transacció, es necesario utilizar un conector que utilice el [Payment Provider Protocol](https://help.vtex.com/es/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Los conectores legados no admiten la funcionalidad.
diff --git a/docs/tutorials/es/how-to-change-orders-beta.md b/docs/tutorials/es/how-to-change-orders-beta.md
index b9effa688..0a967d00f 100644
--- a/docs/tutorials/es/how-to-change-orders-beta.md
+++ b/docs/tutorials/es/how-to-change-orders-beta.md
@@ -77,9 +77,7 @@ Una vez en la página de detalles del pedido, puedes realizar las siguientes mod
 * [Sustituir ítems](#sustituir-items)
 * [Modificar peso](#modificar-peso)
 
-<div class = "alert alert-info">
-Se puede realizar una sola modificación en el pedido o combinar varias a la vez. No hay un límite específico respecto a la cantidad de veces que el pedido puede modificarse. Para obtener más información, consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Cómo funciona Modificar pedido (beta)</a>.
-</div>
+>ℹ️ Se puede realizar una sola modificación en el pedido o combinar varias a la vez. No hay un límite específico respecto a la cantidad de veces que el pedido puede modificarse. Para obtener más información, consulta el artículo [Cómo funciona Modificar pedido (beta)](https://help.vtex.com/es/tutorial/como-funciona-modificar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ).
 
 ### Agregar ítems
 
diff --git a/docs/tutorials/es/how-to-configure-subscriptions.md b/docs/tutorials/es/how-to-configure-subscriptions.md
index e85293b62..dda1458dc 100644
--- a/docs/tutorials/es/how-to-configure-subscriptions.md
+++ b/docs/tutorials/es/how-to-configure-subscriptions.md
@@ -15,9 +15,7 @@ legacySlug: como-configurar-suscripcion-v2
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
-<div class = "alert alert-info">
-La instalación del módulo de Suscripciones se realiza solicitando <a href="https://support.vtex.com/hc/es-419/requests">nuestro Soporte</a>.
-</div>
+>ℹ️ La instalación del módulo de Suscripciones se realiza solicitando [nuestro Soporte](https://support.vtex.com/hc/es-419/requests).
 
 El sistema de **Suscripciones** es una aplicación desarrollada por VTEX para facilitar las ventas recurrentes. Funciona como un programador automático, que repite un pedido en la frecuencia deseada por el cliente de su tienda.
 
diff --git a/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md b/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md
index 1bd9873a8..afe8a38fc 100644
--- a/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md
+++ b/docs/tutorials/es/how-to-configure-xml-for-google-shopping.md
@@ -15,13 +15,9 @@ legacySlug: como-configurar-xml-google-shopping
 subcategory: 2OCA7SVfWoMSiAi0GEGwKo
 ---
 
-<div class = "alert alert-info">
-  <p>Desenvolvemos um novo tipo de integração com o Google Shopping por API, que permite acompanhamento em tempo real. Saiba mais em <a href="https://help.vtex.com/es/tracks/integracion-con-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG">Integración con Google Shopping</a>.</p>
-</div>
+>ℹ️ Desenvolvemos um novo tipo de integração com o Google Shopping por API, que permite acompanhamento em tempo real. Saiba mais em [Integración con Google Shopping](https://help.vtex.com/es/tracks/integracion-con-google-shopping--25Sl7iOqq58PGfVfTAo8Xw/2kGKxwD9HKJvTLDTikQ4zG).
 
-<div class = "alert alert-warning">
-  <p>Este artículo hace referencia al modelo del 22 de mayo de 2013 de las especificaciones de Google Shopping. O Google modifica e atualiza seu modelo sem prévio aviso. Por ello, comprueba siempre si nuestra explicación permanece actualizada según la <a href="https://support.google.com/merchants/answer/188494?hl=pt-BR">documentación de Google Shopping</a>.</p>
-</div>
+>⚠️ Este artículo hace referencia al modelo del 22 de mayo de 2013 de las especificaciones de Google Shopping. O Google modifica e atualiza seu modelo sem prévio aviso. Por ello, comprueba siempre si nuestra explicación permanece actualizada según la [documentación de Google Shopping](https://support.google.com/merchants/answer/188494?hl=pt-BR).
 
 Puede configurar Google Shopping a través de VTEX Admin siguiendo los siguientes pasos:
 
@@ -39,6 +35,4 @@ Puede configurar Google Shopping a través de VTEX Admin siguiendo los siguiente
 
 ![](https://images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
 
-<div class = "alert alert-warning">
-  <p>Si la opción <strong>Mostrar SKU no disponibles</strong> está desmarcada, los productos o SKU que estén agotados no aparecerán en el XML. Los productos inactivos tampoco aparecerán en el XML.</p>
-</div>
+>⚠️ Si la opción **Mostrar SKU no disponibles** está desmarcada, los productos o SKU que estén agotados no aparecerán en el XML. Los productos inactivos tampoco aparecerán en el XML.
diff --git a/docs/tutorials/es/how-to-create-landing-pages-with-customized-urls.md b/docs/tutorials/es/how-to-create-landing-pages-with-customized-urls.md
index 1e381d6cd..1243509a0 100644
--- a/docs/tutorials/es/how-to-create-landing-pages-with-customized-urls.md
+++ b/docs/tutorials/es/how-to-create-landing-pages-with-customized-urls.md
@@ -15,9 +15,7 @@ legacySlug: como-funciona-el-contexto-de-busqueda, como-crear-landing-pages-con-
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - búsqueda VTEX y VTEX Intelligent Search. Este artículo hace referencia a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - búsqueda VTEX y VTEX Intelligent Search. Este artículo hace referencia a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 Tutorial válido solo para tiendas CMS Portal Legado.
diff --git a/docs/tutorials/es/how-to-delete-a-collection.md b/docs/tutorials/es/how-to-delete-a-collection.md
index dcdff1895..9ffc23eb3 100644
--- a/docs/tutorials/es/how-to-delete-a-collection.md
+++ b/docs/tutorials/es/how-to-delete-a-collection.md
@@ -15,9 +15,7 @@ legacySlug: como-borrar-coleccion; como-eliminar-una-coleccion
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 ## Vía Admin
 No se puede eliminar por completo una colección a través del Admin. 
diff --git a/docs/tutorials/es/how-to-identify-an-order-split-from-omnichannel.md b/docs/tutorials/es/how-to-identify-an-order-split-from-omnichannel.md
index dace51704..88ed04a90 100644
--- a/docs/tutorials/es/how-to-identify-an-order-split-from-omnichannel.md
+++ b/docs/tutorials/es/how-to-identify-an-order-split-from-omnichannel.md
@@ -26,9 +26,7 @@ Cuando hay un _split_ de pedido, se añade un sufijo al código, tal como `-01`
 
 > Ejemplo: en el entorno del marketplace, el código de pedido con _split_ es `527103869572-01` o `v527103anml-01`.
 
-<div class = "alert alert-info">
-El pedido realizado en el marketplace tiene un código identificador en el entorno de los sellers. Cada seller tiene acceso restringido a su parte del pedido y no tiene ningún acceso a los pedidos de otros sellers.
-</div>
+>ℹ️ El pedido realizado en el marketplace tiene un código identificador en el entorno de los sellers. Cada seller tiene acceso restringido a su parte del pedido y no tiene ningún acceso a los pedidos de otros sellers.
 
 El código identificador del pedido en el entorno del seller tiene como base la misma secuencia utilizada en el marketplace, más el prefijo adicional correspondiente al [ID de afiliado](https://help.vtex.com/es/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0), el código de tres consonantes que identifica al seller en el marketplace.
 
diff --git a/docs/tutorials/es/how-to-identify-order-closing-errors.md b/docs/tutorials/es/how-to-identify-order-closing-errors.md
index f7a633d4f..bed099593 100644
--- a/docs/tutorials/es/how-to-identify-order-closing-errors.md
+++ b/docs/tutorials/es/how-to-identify-order-closing-errors.md
@@ -19,8 +19,6 @@ Siempre que el usuario hace clic en cerrar pedido, el checkout de inmediato crea
 
 Como todo pedido tiene, como mínimo, una transacción, también es posible encontrar esa transacción en **Pedidos > Transacciones**. Por ser un escenario de error, probablemente ya estará como transacción cancelada.
 
-<div class = "alert alert-info">
-La recomendación es que, para todo error de pedido, el primer sitio a consultar es el log de las transacciones en <b>Pedidos > Transacciones</b>. Sepa más em <a href="https://help.vtex.com/es/tutorial/how-to-view-the-orders-details">Visualizar detalles del pedido en Pedidos</a>.
-</div>
+>ℹ️ La recomendación es que, para todo error de pedido, el primer sitio a consultar es el log de las transacciones en **Pedidos > Transacciones**. Sepa más em [Visualizar detalles del pedido en Pedidos](https://help.vtex.com/es/tutorial/how-to-view-the-orders-details).
 
 El mensaje de error exhibido para el cliente puede generarse por distintas razones. Desde errores internos, como falla en efecturar una reserva de un ítem, hasta problemas con la tarjeta, como datos incompletos, o incluso una respuesta del gateway, como datos insertados de modo equivocado.
diff --git a/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
index 7aa59d8d9..274e1976a 100644
--- a/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/es/how-to-identify-promotions-applied-to-the-cart.md
@@ -44,9 +44,7 @@ Sin embargo, si se aplicó más de una promoción, aparecerá solo la sumatoria
 
 ## orderForm
 
-<div class = "alert alert-warning">
-  <p>Para realizar la investigación que se muestra en esta sección, deberás usar Google Chrome. Como se trata de una herramienta externa a VTEX, puede actualizarse sin previo aviso.</p>
-</div>
+>⚠️ Para realizar la investigación que se muestra en esta sección, deberás usar Google Chrome. Como se trata de una herramienta externa a VTEX, puede actualizarse sin previo aviso.
 
 En la página del carrito, puedes verificar el `orderForm`, un archivo en formato JSON con toda la información correspondiente al pedido que se está creando.
 
diff --git a/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
index c0b0b315c..642c80220 100644
--- a/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/es/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -15,9 +15,7 @@ legacySlug: como-incluir-una-coleccion-de-productos-en-la-vitrina-de-la-tienda
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 Las vitrinas se usan en el destaque de productos en diversas páginas. Se pueden usar también para recomendaciones, en la página del producto.
 
diff --git a/docs/tutorials/es/how-to-integrate-with-facebook.md b/docs/tutorials/es/how-to-integrate-with-facebook.md
index f6407f4bf..4668621c6 100644
--- a/docs/tutorials/es/how-to-integrate-with-facebook.md
+++ b/docs/tutorials/es/how-to-integrate-with-facebook.md
@@ -43,7 +43,7 @@ __Id del Business Manager__: ID de la cuenta de __Business Manager__ de Facebook
 
 __URL del sitio web de la tienda__: Coloque el sitio web de su tienda. Ejemplo: `https://www.sutienda.com`. Este campo se utiliza para formar la URL completa del producto que se envía.
 
-<div class = "alert alert-info">Todos los campos son obligatorios para el pleno funcionamiento de la integración.</div>
+>ℹ️ Todos los campos son obligatorios para el pleno funcionamiento de la integración.
 
 ## Autorización
 
diff --git a/docs/tutorials/es/how-to-manage-subscriptions.md b/docs/tutorials/es/how-to-manage-subscriptions.md
index 3586902c0..0b1ed6230 100644
--- a/docs/tutorials/es/how-to-manage-subscriptions.md
+++ b/docs/tutorials/es/how-to-manage-subscriptions.md
@@ -39,9 +39,7 @@ La sección de **Suscripciones Únicas** permite:
 
 ### Pedidos de Suscripción
 
-<div class = "alert alert-info">
-Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
-</div>
+>ℹ️ Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 La sección **Pedidos de Suscripción** permite: 
 
diff --git a/docs/tutorials/es/how-to-manually-invoice-an-order.md b/docs/tutorials/es/how-to-manually-invoice-an-order.md
index fa1ae2c1d..a0302d9f9 100644
--- a/docs/tutorials/es/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/es/how-to-manually-invoice-an-order.md
@@ -24,9 +24,7 @@ Facturar un pedido en la plataforma VTEX significa ingresar la factura de los í
 * A través de la [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice) de envío de facturas.
 * A través del Admin VTEX.
 
-<div class = "alert alert-info">
-Al facturar un pedido, es posible cambiar la <a href="https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE">transportadora</a> asociada al pedido. Para hacer esto, en la sección <b>Seguimiento del pedido</b>, haga clic en <i>Transportadora</i> y seleccione la opción deseada.
-</div>
+>ℹ️ Al facturar un pedido, es posible cambiar la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) asociada al pedido. Para hacer esto, en la sección **Seguimiento del pedido**, haga clic en <i>Transportadora</i> y seleccione la opción deseada.
 
 Para enviar una factura a través del Admin VTEX, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
index 4f113903c..d929f4c29 100644
--- a/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/es/how-to-optimize-searches-with-substitute-words.md
@@ -15,9 +15,7 @@ legacySlug: optimizar-las-busquedas-con-palabras-sustitutas
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-No recomendamos el uso de <a href="https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu">Palabras sustitutas</a> cuando se utilice Intelligent search. Para asociar palabras con productos es preferible emplear <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ">Sinónimos</a>, ya que permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con <a href="https://support.vtex.com/hc/es/requests">nuestro equipo de soporte</a>.
-</div>
+>⚠️ No recomendamos el uso de [Palabras sustitutas](https://help.vtex.com/es/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu) cuando se utilice Intelligent search. Para asociar palabras con productos es preferible emplear [Sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZ), ya que permiten gestionar los términos por producto de una forma más escalable. Para más información, ponte en contacto con [nuestro equipo de soporte](https://support.vtex.com/hc/es/requests).
 
 ## Cómo funciona el buscador
 El buscador de VTEX posee un algoritmo inteligente que, a partir del término buscado, identifica cuál es el mejor resultado para presentarle al usuario, o sea, se le presenta siempre el resultado que generará más conversión de venta.
diff --git a/docs/tutorials/es/how-to-return-order-items.md b/docs/tutorials/es/how-to-return-order-items.md
index f7143620a..f6618bbab 100644
--- a/docs/tutorials/es/how-to-return-order-items.md
+++ b/docs/tutorials/es/how-to-return-order-items.md
@@ -36,6 +36,4 @@ La página de Detalles del pedido permite orquestar esa operación realizando lo
 
 Después de que el reembolso sea procesado por el sistema, los ítems devueltos y su información aparecerán en la sección *Ítems devueltos*.
 
-<div class = "alert alert-info">
-El cambio de pedidos se realiza a través de API por el endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> y la emisión de facturas actualizadas por el endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice">Order invoice notification</a>.
-</div>
+>ℹ️ El cambio de pedidos se realiza a través de API por el endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) y la emisión de facturas actualizadas por el endpoint [Order invoice notification](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice).
diff --git a/docs/tutorials/es/how-to-update-the-image-of-an-sku.md b/docs/tutorials/es/how-to-update-the-image-of-an-sku.md
index 8cbeadf93..572c56e39 100644
--- a/docs/tutorials/es/how-to-update-the-image-of-an-sku.md
+++ b/docs/tutorials/es/how-to-update-the-image-of-an-sku.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Usted puede actualizar una imagen de SKU de dos formas: en el Admin VTEX ou por la Catalog API.
 
-<div class = "alert alert-danger">
-Este es un procedimiento que se debe realizar con mucho cuidado. El procedimiento que se describe a continuación implica la exclusión de todas las imágenes de un SKU, lo que lo volverá <strong>INACTIVO</strong>. Manténgase atento a las recomendaciones de los siguientes pasos para que la actualización de las imágenes se realice con éxito.
-</div>
+>❗ Este es un procedimiento que se debe realizar con mucho cuidado. El procedimiento que se describe a continuación implica la exclusión de todas las imágenes de un SKU, lo que lo volverá **INACTIVO**. Manténgase atento a las recomendaciones de los siguientes pasos para que la actualización de las imágenes se realice con éxito.
 
 Como este procedimiento implica la exclusión de todas las imágenes de un SKU y lo vuelve inactivo, recomendamos que el proceso de sustitución de imágenes se realice en pequeños lotes de SKUs.
 
@@ -33,9 +31,7 @@ Como este procedimiento implica la exclusión de todas las imágenes de un SKU y
 4. Haga clic en la pestaña __Imágenes__.
 5. Seleccione las imágenes que desea borrar y haga clic en __Retirar__. Recuerde que al borrar todas las imágenes de un SKU este quedará inactivo.
 
-<div class = "alert alert-danger">
-Recomendamos que estas actualizaciones de imágenes se realicen en pequeños lotes. Recuerde que, al borrar todas las imágenes de un SKU, este quedará inactivo.
-</div>
+>❗ Recomendamos que estas actualizaciones de imágenes se realicen en pequeños lotes. Recuerde que, al borrar todas las imágenes de un SKU, este quedará inactivo.
 
 ### Subir las nuevas imágenes
 
diff --git a/docs/tutorials/es/how-to-use-rebates.md b/docs/tutorials/es/how-to-use-rebates.md
index 4343e4452..19a10a596 100644
--- a/docs/tutorials/es/how-to-use-rebates.md
+++ b/docs/tutorials/es/how-to-use-rebates.md
@@ -25,9 +25,7 @@ Este escenario no solo fortalece las relaciones entre los proveedores y revended
 
 La forma más adecuada de utilizar el rebate recibido de los proveedores es a través de [Promociones regulares](https://help.vtex.com/es/tracks/promociones--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI) con las restricciones de uso que se requieren. Para saber más sobre las opciones de Promoción Regular, lea nuestro artículo [Ejemplos de promoción](https://help.vtex.com/es/tutorial/ejemplos-de-promociones--5A8UTc7knvAscxo7e7rMFD).
 
-<div class = "alert alert-warning">
-  <p>El cliente eventualmente puede cancelar la compra de un pedido con descuento del rebate. En ese caso, se debe redirigir la promoción a otro cliente para alcanzar el total de créditos. Para verificar si el rebate se ha aplicado a un pedido, utilice los endpoints <a href = "https://developers.vtex.com/vtex-developer-docs/reference/user-orders#userorderslist">Retrieve User's orders</a> o <a href="https://developers.vtex.com/vtex-developer-docs/reference/orders#getorder">Get Order</a> de Orders API.</p>
-</div>
+>⚠️ El cliente eventualmente puede cancelar la compra de un pedido con descuento del rebate. En ese caso, se debe redirigir la promoción a otro cliente para alcanzar el total de créditos. Para verificar si el rebate se ha aplicado a un pedido, utilice los endpoints <a href = "https://developers.vtex.com/vtex-developer-docs/reference/user-orders#userorderslist">Retrieve User's orders</a> o [Get Order](https://developers.vtex.com/vtex-developer-docs/reference/orders#getorder) de Orders API.
 
 ## Ejemplo
 
diff --git a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
index e85a04563..b24a7838e 100644
--- a/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/es/how-to-work-with-different-layouts-for-the-same-page.md
@@ -15,9 +15,7 @@ legacySlug: como-trabajar-con-diferentes-layouts-para-una-misma-pagina
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 En la página __Storefront__ > __Layout__, se establece un layout estándar para todas las páginas del mismo tipo incluidas en cada carpeta de un website, ejemplo: _producto_.
 
diff --git a/docs/tutorials/es/i-cant-import-the-price-table.md b/docs/tutorials/es/i-cant-import-the-price-table.md
index af2d01514..ae3d6beb6 100644
--- a/docs/tutorials/es/i-cant-import-the-price-table.md
+++ b/docs/tutorials/es/i-cant-import-the-price-table.md
@@ -19,9 +19,7 @@ __Tags/Palavras clave__: *plantilla de precios, importación de plantillas, celd
 
 Las [tablas o plantillas de precio](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) almacenan información de SKU que tras aplicarse en determinados contextos, como políticas comerciales, promociones o clústeres de clientes, permiten calcular los valores de venta de los productos en una tienda VTEX. Para más información, consulta [Precio base](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) y [Precio fijo](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy).
 
-<div class ="alert alert-warning">
-  No se puede importar una plantilla de <b>precio calculado</b> en el Admin VTEX. Solo se permite <b>exportar</b> esta plantilla para que el retailer pueda consultar los valores de precio final de cada producto.
-</div>
+>⚠️ No se puede importar una plantilla de **precio calculado** en el Admin VTEX. Solo se permite **exportar** esta plantilla para que el retailer pueda consultar los valores de precio final de cada producto.
 
 Tras [importar una plantilla de precios](https://help.vtex.com/es/tracks/precios-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D) pueden aparecer algunos mensajes de error en algunos SKU según los ejemplos a continuación:
 
@@ -50,9 +48,7 @@ Comprueba que los campos de tu plantilla estén rellenados según las guías de
 - [Plantilla de precios base](https://help.vtex.com/es/tutorial/tabla-de-precios-base--4Jox8TeQ5feqAn78TZ0DNA)
 - [Plantilla de precios fijos](https://help.vtex.com/es/tutorial/rellenar-campos-de-la-plantilla-de-importacion-de-precios-fijos--50RFoH3ruV97FJgeBUCURh)
 
-<div class ="alert alert-warning">
-  Antes de importar la plantilla en el Admin VTEX, comprueba que no contenga columnas con información de errores (<b>Error Code</b> y <b>Error Message</b>) ni que tenga algún tipo de filtro aplicado en las celdas. Si intentas importar una plantilla así, pueden generarse errores en el proceso de importación de datos.
-</div>
+>⚠️ Antes de importar la plantilla en el Admin VTEX, comprueba que no contenga columnas con información de errores (**Error Code** y **Error Message**) ni que tenga algún tipo de filtro aplicado en las celdas. Si intentas importar una plantilla así, pueden generarse errores en el proceso de importación de datos.
 
 Ejemplo de plantilla con filtros aplicados y con los campos __Error Code__ y __Error Messages__:
 
@@ -62,6 +58,4 @@ Ejemplo de plantilla con filtros aplicados y con los campos __Error Code__ y __E
 
 Las plantillas de precios no deben exceder el límite de tamaño máximo de 1 megabyte (1 MB). Si tu plantilla excede el límite de tamaño, divide los datos en plantillas de menos de 1 megabyte (1 MB).
 
-<div class ="alert alert-warning">
-  Todos los datos de un SKU específico deben mantenerse en la misma plantilla. No se permite registrar información del mismo SKU en plantillas diferentes.
-</div>
+>⚠️ Todos los datos de un SKU específico deben mantenerse en la misma plantilla. No se permite registrar información del mismo SKU en plantillas diferentes.
diff --git a/docs/tutorials/es/i-cant-receive-emails-from-vtex.md b/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
index 84b04326c..0786e1502 100644
--- a/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
+++ b/docs/tutorials/es/i-cant-receive-emails-from-vtex.md
@@ -62,9 +62,7 @@ Después de la prueba, si el usuario que inició sesión en el Admin no recibió
 
 Comprueba que el servidor SMTP externo está correctamente configurado según el [sistema SPF](https://help.vtex.com/es/tutorial/configurar-spf--42t0lkl2VyC6Yewc4wA6wI), que se encarga de impedir que servidores no autorizados envíen emails en nombre de un dominio concreto. Si es necesario, puedes realizar la [configuración del SPF (Sender Policy Framework)](https://developers.vtex.com/docs/guides/setting-up-the-spf) y el [DKIM](https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails) (DomainKeys Identified Mail) en el servidor.
 
-<div class ="alert alert-warning">
-Comprueba que los emails no estén en la carpeta de spam. A veces caen en esta carpeta debido a reglas internas de los servidores de correo.
-</div>
+>⚠️ Comprueba que los emails no estén en la carpeta de spam. A veces caen en esta carpeta debido a reglas internas de los servidores de correo.
 
 ### Configurar notificaciones de pedidos y pagos
 
@@ -82,9 +80,7 @@ Amazon (AWS) tiene una plataforma de email llamada Amazon Simple Email Service (
 
 En situaciones normales, una dirección de email puede ser incluida en la lista de supresión de AWS y ser removida transcurridas aproximadamente 12 horas. Durante este periodo, los emails enviados por VTEX no se recibirán en la dirección de email incluida en la lista.
 
-<div class ="alert alert-warning">
-La gestión de la lista de supresión es responsabilidad de AWS, y VTEX no tiene ninguna responsabilidad sobre el movimiento de direcciones dentro y fuera de la lista.
-</div>
+>⚠️ La gestión de la lista de supresión es responsabilidad de AWS, y VTEX no tiene ninguna responsabilidad sobre el movimiento de direcciones dentro y fuera de la lista.
 
 Si sospechas que tu dirección de email ha sido bloqueada por AWS, espera 12 horas e intenta volver a enviar un email a la dirección bloqueada.
 
diff --git a/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
index 3d42d555e..266bd7d1f 100644
--- a/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
+++ b/docs/tutorials/es/i-cant-view-the-product-in-the-search-results.md
@@ -47,9 +47,7 @@ La ausencia del producto en un resultado de búsqueda puede atribuirse a que alg
 
 <blockquote><ui>1. En el Admin VTEX, accede a </b>Catálogo > Todos los productos</b>.</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Las tiendas que utilizan la página <b>Productos y SKUs (beta)</b> deben verificar los campos de registro de productos accediendo a <b>Catálogo >  Productos y SKUs</b> en el Admin VTEX. Más información en <a href="https://help.vtex.com/es/tutorial/productos-y-skus-beta--2ig7TmROlirWirZjFWZ3By">Productos y SKUs (beta)</a>.
-</div></blockquote>
+<blockquote><ui>>⚠️ Las tiendas que utilizan la página **Productos y SKUs (beta)** deben verificar los campos de registro de productos accediendo a **Catálogo >  Productos y SKUs** en el Admin VTEX. Más información en [Productos y SKUs (beta)](https://help.vtex.com/es/tutorial/productos-y-skus-beta--2ig7TmROlirWirZjFWZ3By).</blockquote>
 
 <blockquote><ui>2. Haz clic en sobre el producto que deseas <b>EDITAR</b>.</ui>
 
@@ -63,9 +61,7 @@ La ausencia del producto en un resultado de búsqueda puede atribuirse a que alg
 
 <blockquote><ui>7. Accede al sitio web de la tienda, ingresa el término deseado y verifica que los productos que se muestran en los resultados de la búsqueda coinciden con los productos disponibles en la <b>Explicación de la búsqueda</b> de Intelligent Search (<b>Storefront > Intelligent Search > Explicación de la búsqueda</b>).</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Si el término buscado está presente en el nombre o la descripción del producto, pero el producto pertenece a una marca diferente a la especificada en la búsqueda, procede con los pasos a continuación para solucionar el problema.
-</div></blockquote>
+<blockquote><ui>>⚠️ Si el término buscado está presente en el nombre o la descripción del producto, pero el producto pertenece a una marca diferente a la especificada en la búsqueda, procede con los pasos a continuación para solucionar el problema.</blockquote>
 
 ### Modificar filtro de búsqueda en Rewriter
 
@@ -123,9 +119,7 @@ internal {
 }
 ```
 
-<blockquote><ui><div class ="alert alert-warning">
-  El valor <i>ft</i> (full text) en lugar de <i>b</i> (brand) en el parámetro <i>map</i> indica que los productos en los que el término <i>Pendleton</i> esté presente en el nombre o la descripción también se mostrarán en la búsqueda.
-</div></blockquote>
+<blockquote><ui>>⚠️ El valor <i>ft</i> (full text) en lugar de <i>b</i> (brand) en el parámetro <i>map</i> indica que los productos en los que el término <i>Pendleton</i> esté presente en el nombre o la descripción también se mostrarán en la búsqueda.</blockquote>
 
 <blockquote><ui>7. Haz clic en la flecha de IDE de GraphiQL (a la derecha de <b>GraphiQL</b>) para actualizar el filtro de búsqueda. El nuevo valor predeterminado de filtro de búsqueda para el término será confirmado mostrando el siguiente mensaje en el campo de resultados de IDE de GraphiQL.</ui>
 
@@ -154,8 +148,7 @@ internal {
 
 <blockquote><ui>8. Accede al sitio web de la tienda, ingresa el término deseado y verifica que los productos que se muestran en los resultados de la búsqueda coinciden con los productos disponibles en la <b>Explicación de la búsqueda</b> de Intelligent Search (<b>Storefront > Intelligent Search > Explicación de la búsqueda</b>).</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Si el término de búsqueda está relacionado con una marca que ya no existe en su sitio web, deberá eliminar la ruta de búsqueda interna dentro de la aplicación Rewriter como se describe en la solución a continuación.</div></blockquote>
+<blockquote><ui>>⚠️ Si el término de búsqueda está relacionado con una marca que ya no existe en su sitio web, deberá eliminar la ruta de búsqueda interna dentro de la aplicación Rewriter como se describe en la solución a continuación.</blockquote>
 
 ### Remoção da rota interna de busca no Rewriter
 
diff --git a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md
index 715103db1..8f3522aa2 100644
--- a/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md
+++ b/docs/tutorials/es/integration-guide-for-marketplaces-marketplace-non-vtex.md
@@ -62,9 +62,7 @@ En este artículo, obtendrá una visión general del proceso de integración de
 
 3) Marketplace busca precio, inventario y datos de flete del SKU a través de la API de Fullfillment.  
 
-<div class = "alert alert-info">
-Más información en la documentación para desarrolladores <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">External Marketplace</a>.
-</div>
+>ℹ️ Más información en la documentación para desarrolladores [External Marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
 
 ## B) Flujo Referente al Envío y Procesamiento de Pedidos
 
diff --git a/docs/tutorials/es/interaction-details.md b/docs/tutorials/es/interaction-details.md
index eeabc078c..81d0d3ce6 100644
--- a/docs/tutorials/es/interaction-details.md
+++ b/docs/tutorials/es/interaction-details.md
@@ -33,9 +33,7 @@ La página **Detalles de la interacción** cuenta con las siguientes secciones:
 - [Resultado de la interacción](#resultado-de-la-interaccion)    
 - [Línea de tiempo](#linea-de-tiempo)   
 
-<div class = "alert alert-info">
-<b>Gestión de anuncios</b> permite hacer un seguimiento de los anuncios con <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> (Classic y Premium), <a href="https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> y marketplaces VTEX. Para los conectores que desean integrarse a través de API, existe la <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Guía de integración de Gestión de anuncios</a>.
-</div>  
+>ℹ️ **Gestión de anuncios** permite hacer un seguimiento de los anuncios con [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic y Premium), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y marketplaces VTEX. Para los conectores que desean integrarse a través de API, existe la [Guía de integración de Gestión de anuncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).  
 
 ## Encabezado
 ![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/cc97295e6fa0f0d1cfaa76cd755904cb/Interaction_details_ES_cabe__alho.jpg)
diff --git a/docs/tutorials/es/inventory-update-history.md b/docs/tutorials/es/inventory-update-history.md
index 2e032770c..ca418b104 100644
--- a/docs/tutorials/es/inventory-update-history.md
+++ b/docs/tutorials/es/inventory-update-history.md
@@ -19,11 +19,9 @@ El _stock_ contiene la información de los productos disponibles en una tienda y
 
 Este artículo contiene las instrucciones para acceder al historial de movimientos de _stock_ desde el VTEX Admin.
 
-<div class = "alert alert-info">
-No olvides la diferencia entre almacén y stock:
-<p><b><a href="https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb">Almacén:</a></b> donde se almacenan los productos de la tienda.
-<p><b>Stock:</b>lista de los SKU y de los almacenes en los que se encuentran.
-</div>
+>ℹ️ No olvides la diferencia entre almacén y stock:
+> <p>**[Almacén:](https://help.vtex.com/es/tutorial/almacen--6oIxvsVDTtGpO7y6zwhGpb)** donde se almacenan los productos de la tienda.
+> <p>**Stock:**lista de los SKU y de los almacenes en los que se encuentran.
 
 Para ver los movimientos de un SKU:
 
diff --git a/docs/tutorials/es/is-it-possible-to-use-the-vtex-admin-search-report.md b/docs/tutorials/es/is-it-possible-to-use-the-vtex-admin-search-report.md
index 0c2c41d6a..da9cdcf37 100644
--- a/docs/tutorials/es/is-it-possible-to-use-the-vtex-admin-search-report.md
+++ b/docs/tutorials/es/is-it-possible-to-use-the-vtex-admin-search-report.md
@@ -15,9 +15,7 @@ legacySlug: es-posible-utilizar-el-informe-de-busqueda-en-el-admin-de-vtex
 subcategory: 5yDQmr18K4GgQAeGwq8USa
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 El informe de búsqueda de VTEX al que se accedía por el camino __Informes > Búsqueda__ se ha descontinuado.
 
diff --git a/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
index 87a2d626a..30a36c466 100644
--- a/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
+++ b/docs/tutorials/es/lead-time-shipping-time-at-sku-level.md
@@ -27,9 +27,7 @@ Este artículo aborda los siguientes aspectos:
 - [Configurar lead time:](#configurar-lead-time) cómo realizar la configuración en el Admin VTEX.
 - [Configurar el contaje del lead time en días naturales:](#configurar-el-contaje-del-lead-time-en-dias-naturales-opcional) etapa opcional para que el contaje del lead time sea en días naturales y no en días laborables, que es el valor predeterminado.
 
-<div class = "alert alert-info">
-Para configurar el lead time vía API, accede a <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>ℹ️ Para configurar el lead time vía API, accede a [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## Tiempo total de envío
 
@@ -83,9 +81,7 @@ Para configurar el lead time de un SKU sigue los pasos a continuación:
   ![lead_time_inventory_management_ES](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/898387e10a3c41d8837df10604ec652d/lead_time_inventory_management_ES.png)
 4. Haz clic en `Guardar` en la parte inferior de la página.
 
-<div class = "alert alert-info">
-En el Admin VTEX, el lead time siempre se configura en días, pero también se pueden configurar periodos en horas, minutos y segundos, utilizando el endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>ℹ️ En el Admin VTEX, el lead time siempre se configura en días, pero también se pueden configurar periodos en horas, minutos y segundos, utilizando el endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## Configurar el contaje del lead time en días naturales (opcional)
 
diff --git a/docs/tutorials/es/license-manager-resources.md b/docs/tutorials/es/license-manager-resources.md
index 920f3a4dc..e61933b3f 100644
--- a/docs/tutorials/es/license-manager-resources.md
+++ b/docs/tutorials/es/license-manager-resources.md
@@ -24,9 +24,7 @@ Por lo tanto, la plataforma VTEX ofrece la posibilidad de crear roles de usuario
 
 <iframe src="https://help.vtex.com/tables/resources/es" title="Recursos del License Manager" frameBorder="0" width="100%" height="850"></iframe>
 
-<div class = "alert alert-info">
-  <p>En la aplicación <a href="https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a>, los recursos de License Manager son identificados por las respectivas claves.</p>
-</div>
+>ℹ️ En la aplicación [Audit](https://help.vtex.com/es/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA), los recursos de License Manager son identificados por las respectivas claves.
 
 ## Recursos internos o obsoletos
 
diff --git a/docs/tutorials/es/loading-dock.md b/docs/tutorials/es/loading-dock.md
index 627e64e9b..47b9ae104 100644
--- a/docs/tutorials/es/loading-dock.md
+++ b/docs/tutorials/es/loading-dock.md
@@ -22,16 +22,14 @@ En VTEX, el muelle es un intermediario entre el almacenamiento de ítems y la en
 
 ![Doca ES](https://images.ctfassets.net/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/e3f7d64c72c143e395895e7bf2865663/Doca_ES.svg)
 
-<div class = "alert alert-info">
-El almacén es el espacio físico de almacenamiento de los productos vendidos por la tienda; la política comercial es la configuración de las estrategias de venta de la tienda; y la política de envío es un conjunto de reglas que definen las opciones y condiciones de envío.
-El orden de registro sugerido en la plataforma VTEX para el funcionamiento previsto del sistema logístico es:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV">Política comercial</a>;</li>
-<li><a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140">Política de envío</a>;</li>
-<li>Muelle;</li>
-<li><a href="https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Almacén</a>.</li>
-</div>
+>ℹ️ El almacén es el espacio físico de almacenamiento de los productos vendidos por la tienda; la política comercial es la configuración de las estrategias de venta de la tienda; y la política de envío es un conjunto de reglas que definen las opciones y condiciones de envío.
+> El orden de registro sugerido en la plataforma VTEX para el funcionamiento previsto del sistema logístico es:
+> <body>
+> <ol>
+> <li>[Política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV);</li>
+> <li>[Política de envío](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140);</li>
+> <li>Muelle;</li>
+> <li>[Almacén](https://help.vtex.com/es/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb).</li>
 
 ## Casos de uso
 
diff --git a/docs/tutorials/es/making-product-collections-searchable.md b/docs/tutorials/es/making-product-collections-searchable.md
index 934bbf936..285822987 100644
--- a/docs/tutorials/es/making-product-collections-searchable.md
+++ b/docs/tutorials/es/making-product-collections-searchable.md
@@ -15,17 +15,13 @@ legacySlug: tornar-colecao-de-produtos-encontravel-pela-busca
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Puede hacer con que, al buscar por el nombre de una colección en la búsqueda de la tienda, el usuario encuentre los productos de esta colección.
 
 Por ejemplo, digamos que tiene una colección llamada "Día del Niño", y que seleccione esta colección para su búsqueda. Si un cliente de la tienda busca el término "Día del Niño", los productos que forman parte de esa colección serán renderizados en el resultado de la búsqueda.
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 Para hacer que una colección pueda buscarse, siga los siguientes pasos: 
 
diff --git a/docs/tutorials/es/managing-delivery-capacity.md b/docs/tutorials/es/managing-delivery-capacity.md
index 0deefa1b7..a424f979d 100644
--- a/docs/tutorials/es/managing-delivery-capacity.md
+++ b/docs/tutorials/es/managing-delivery-capacity.md
@@ -34,6 +34,4 @@ Una vez que haya seleccionado la política de envío y la fecha que se mostrará
 *   **Disponible:** cuántos ítems/pedidos están disponibles para programarse (cantidad de capacidad menos reservado) 
 *   **Status:** puede ser visible o no visible, dependiendo de si la ventana de entrega todavía está disponible. Si todavía está disponible, la ventana tendrá el status visible para sus clientes. 
 
-<div class = "alert alert-info">
-Puede hacer clic en <b>EDITAR POLÍTICA DE ENVÍO</b> para ser redirigido a la pantalla de edición de la política de envío seleccionada en el filtro Política de envío.
-</div>
+>ℹ️ Puede hacer clic en **EDITAR POLÍTICA DE ENVÍO** para ser redirigido a la pantalla de edición de la política de envío seleccionada en el filtro Política de envío.
diff --git a/docs/tutorials/es/managing-http-headers.md b/docs/tutorials/es/managing-http-headers.md
index e3ec3cf2f..3f866b6cc 100644
--- a/docs/tutorials/es/managing-http-headers.md
+++ b/docs/tutorials/es/managing-http-headers.md
@@ -22,9 +22,7 @@ Los encabezados son clave en la comunicación HTTP, ya que proporcionan informac
 - __Encabezados de request:__ enviados por el cliente al servidor. Contienen información sobre el request realizado, tal como tipo de método HTTP utilizado, tipo de contenido aceptado, cookies, entre otros.
 - __Encabezados de respuesta:__ enviados por el servidor al cliente. Proporcionan información sobre la respuesta enviada, tal como status de la respuesta, tipo de contenido devuelto, cookies, entre otros.
 
-<div class = "alert alert-info">
-Para más información, consulta la guía de <a href="https://developer.mozilla.org/es/docs/Web/HTTP">MDN HTTP</a> y la documentación relacionada.
-</div>
+>ℹ️ Para más información, consulta la guía de [MDN HTTP](https://developer.mozilla.org/es/docs/Web/HTTP) y la documentación relacionada.
 
 En esta guía, aprenderás a gestionar los encabezados de respuestas de seguridad.
 
diff --git a/docs/tutorials/es/managing-shipping-policies.md b/docs/tutorials/es/managing-shipping-policies.md
index a20bf09e0..4b00a482c 100644
--- a/docs/tutorials/es/managing-shipping-policies.md
+++ b/docs/tutorials/es/managing-shipping-policies.md
@@ -52,9 +52,7 @@ La información de la lista se describe en la siguiente tabla:
 
 La caja de búsqueda que tiene el ícono de lupa <i class="fas fa-search"></i> te permite buscar políticas de envío por nombre. Ingresar un carácter en la barra de búsqueda activa la búsqueda inmediatamente. Para limpiar la búsqueda, haz clic en el ícono de cerrar <i class="far fa-times-circle"></i>.
 
-<div class = "alert alert-info">
-Si la búsqueda no devuelve ningún resultado, comprueba la ortografía del término o si hay algún filtro seleccionado.
-</div>
+>ℹ️ Si la búsqueda no devuelve ningún resultado, comprueba la ortografía del término o si hay algún filtro seleccionado.
 
 ## Filtrar políticas de envío
 
diff --git a/docs/tutorials/es/managing-stock-items.md b/docs/tutorials/es/managing-stock-items.md
index ff38765d9..2a8a24d18 100644
--- a/docs/tutorials/es/managing-stock-items.md
+++ b/docs/tutorials/es/managing-stock-items.md
@@ -39,7 +39,7 @@ En el Admin VTEX, accede a **Catálogo > Stock > Gestión de stock**, o escribe
     * **Productos**: el nombre del producto.
     * **Almacén**: indica el almacén de la tienda en el que se encuentra el SKU.
     * **ID del SKU**: código que identifica el SKU.
-    * **Última actualización**: número de unidades del SKU más reciente registrado en la plataforma VTEX.<p><div class = "alert alert-info">Al hacer clic en cualquier valor en la columna <b>Última actualización</b>, se abrirá la ventana <a href="https://help.vtex.com/es/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2">Registro de actualizaciones</a> con datos de cambios. Cada fila corresponde a una actualización, y las columnas contienen el usuario que realizó el cambio, la fecha de la última actualización y la cantidad de ítems antes y después de la actualización. Solo puedes consultar las últimas 50 actualizaciones en el registro de un SKU.</div></p>
+    * **Última actualización**: número de unidades del SKU más reciente registrado en la plataforma VTEX.<p>>ℹ️ Al hacer clic en cualquier valor en la columna **Última actualización**, se abrirá la ventana [Registro de actualizaciones](https://help.vtex.com/es/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2) con datos de cambios. Cada fila corresponde a una actualización, y las columnas contienen el usuario que realizó el cambio, la fecha de la última actualización y la cantidad de ítems antes y después de la actualización. Solo puedes consultar las últimas 50 actualizaciones en el registro de un SKU.</p>
     * **Reservado**: unidades de ítems del SKU reservadas. Los pedidos de las reservas aún no tienen el pago aprobado. 
     Haz clic en los valores de esta columna para ver los detalles de los datos de las reservas del SKU y se te redirigirá a la gestión de pedidos. Para saber más sobre cómo consultar una reserva, consulta [Cómo seguir el status de la reserva](https://help.vtex.com/es/tutorial/how-does-reservation-work--tutorials_92#como-seguir-el-status-de-la-reserva).
     * **Enviados**: unidades del SKU enviadas. Los ítems de esta columna provienen de pedidos con status `Pago aprobado`, `Preparando entrega` o `Facturado`. <p>Al hacer clic en los ítems de la columna para ver los detalles de los SKU enviados, se te redirigirá a la gestión de pedidos.</p>
diff --git a/docs/tutorials/es/master-data.md b/docs/tutorials/es/master-data.md
index 90a2029a4..ad08499dd 100644
--- a/docs/tutorials/es/master-data.md
+++ b/docs/tutorials/es/master-data.md
@@ -27,9 +27,7 @@ En este artículo, encontrarás más detalles sobre cada versión disponible de
 
 Actualmente existen dos versiones disponibles y puedes elegir la que mejor se adapte a las necesidades de tu operación. La principal diferencia entre ambas es que la v2 no incluye interfaz gráfica, por lo que se puede usar solo a través de la [API del Master Data v2](https://developers.vtex.com/docs/api-reference/master-data-api-v2), pero sí tiene otras funcionalidades importantes, por ejemplo, [esquemas JSON](https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema).
 
-<div class = "alert alert-info">
-La plataforma VTEX guarda de forma nativa los datos de los clientes de tu tienda en Master Data v1.
-</div>
+>ℹ️ La plataforma VTEX guarda de forma nativa los datos de los clientes de tu tienda en Master Data v1.
 
 En la tabla a continuación, obtendrás más información sobre las diferencias en las funcionalidades de cada versión.
 
@@ -286,9 +284,7 @@ Como se dijo anteriormente, cada documento tiene un ID que la plataforma genera
 
 Por ejemplo, puedes consultar un documento con información de un cliente especificando el valor del campo `email` del cliente.
 
-<div class = "alert alert-info">
-Obtén más información sobre cómo <a href=https://help.vtex.com/es/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices en Master Data v1</a> o <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>configurar índices con la API del Master Data v2</a>.
-</div>
+>ℹ️ Obtén más información sobre cómo <a href=https://help.vtex.com/es/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices en Master Data v1</a> o <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>configurar índices con la API del Master Data v2</a>.
 
 ## Triggers
 
@@ -303,17 +299,13 @@ Obtén más información sobre cómo [configurar triggers en el Master Data v1]
 
 Con la v2 de Master Data puedes definir formatos de datos con esquemas JSON. Este formato indica cómo Master Data debe validar e indexar los documentos.
 
-<div class = "alert alert-info">
-Obtén más información en <a href=https://json-schema.org/>esquemas JSON</a>.
-</div>
+>ℹ️ Obtén más información en <a href=https://json-schema.org/>esquemas JSON</a>.
 
 Puedes guardar un documento en cualquier entidad de datos si el contenido es un JSON válido. Una entidad de datos puede tener asociados o no varios esquemas JSON.
 
 ![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/3b032813aed32ec745e01d4d32cf4e87/schemas_es.jpg)
 
-<div class = "alert alert-info">
-Un documento puede ser compatible con varios esquemas JSON, o con ninguno.
-</div>
+>ℹ️ Un documento puede ser compatible con varios esquemas JSON, o con ninguno.
 
 ## Aplicaciones
 
diff --git a/docs/tutorials/es/mercado-livre-automobilist-compatibility.md b/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
index 3d6be0520..d3fad148d 100644
--- a/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
+++ b/docs/tutorials/es/mercado-livre-automobilist-compatibility.md
@@ -15,9 +15,7 @@ legacySlug: mercado-libre-compatibilidad-de-autopartes
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class = "alert alert-info">
-Este recurso solo está disponible para sellers VTEX que vendan productos de autos en Argentina, Brasil y México.
-</div>  
+>ℹ️ Este recurso solo está disponible para sellers VTEX que vendan productos de autos en Argentina, Brasil y México.  
 
 En el módulo [Gestión de anuncios](https://help.vtex.com/es/tutorial/gerenciamento-de-anuncios--7MRb9S78aBdZjFGpbuffpE), los sellers de tiendas VTEX pueden monitorear y gestionar los anuncios enviados a los canales de ventas [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic y Premium), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y otros marketplaces VTEX.  
 
@@ -25,9 +23,7 @@ La compatibilidad de autopartes permite a los sellers indicar los vehículos que
 
 En los anuncios enviados a Mercado Libre, se pueden identificar los que tengan el error `Compatibilidad con MELI`, que ocurre cuando una anuncio de accesorio de autopartes se envía sin la información de los vehículos compatibles o cuando la configuración es incorrecta.  
 
-<div class = "alert alert-warning">
-Los anuncios que tengan error no se envían a Mercado Libre hasta que se corrijan.
-</div>  
+>⚠️ Los anuncios que tengan error no se envían a Mercado Libre hasta que se corrijan.  
 
 ![Mercado Libre: compatibilidad de autopartes](https://images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/df37ddb666928a86c4199ce98bfe7af6/comp_automobilistica.png) 
 
@@ -46,9 +42,7 @@ Para corregir los errores de `Compatibilidad con MELI` sigue los pasos a continu
 
 Después de completar las instrucciones, tu anuncio estará listo para enviarlo a Mercado Libre.
 
-<div class = "alert alert-info"> 
-No se puede informar la compatibilidad de autopartes para lubricantes, refrigerantes y líquidos de frenos.
-</div>   
+>ℹ️ No se puede informar la compatibilidad de autopartes para lubricantes, refrigerantes y líquidos de frenos.   
 
 ### Artículos relacionados:  
 
diff --git a/docs/tutorials/es/mercado-livre-faq.md b/docs/tutorials/es/mercado-livre-faq.md
index d00e69f26..22af14111 100644
--- a/docs/tutorials/es/mercado-livre-faq.md
+++ b/docs/tutorials/es/mercado-livre-faq.md
@@ -27,9 +27,7 @@ Existen tres formas de enviar a Mercado Libre la descripción de un producto:
 - Crear una especificación de producto
 - Crear una plantilla en el Centro de mensajes (opcional)
 
-<div class = "alert alert-info">
-Consulta el artículo de Mercado Libre <a href="https://www.mercadolibre.com.ar/ayuda/completar_datos_productos_3147#:~:text=Ingres%C3%A1%20desde%20Modificar%2C%20en%20el%20listado%20de%20publicaciones.&text=Ahora%20bien%2C%20si%20ten%C3%A9s%20muchas,las%20publicaciones%20ordenadas%20por%20categor%C3%ADa.">“Cómo describir tus productos”</a> para obtener sugerencias sobre cómo describir tus productos.
-</div>
+>ℹ️ Consulta el artículo de Mercado Libre [“Cómo describir tus productos”](https://www.mercadolibre.com.ar/ayuda/completar_datos_productos_3147#:~:text=Ingres%C3%A1%20desde%20Modificar%2C%20en%20el%20listado%20de%20publicaciones.&text=Ahora%20bien%2C%20si%20ten%C3%A9s%20muchas,las%20publicaciones%20ordenadas%20por%20categor%C3%ADa.) para obtener sugerencias sobre cómo describir tus productos.
 
 #### Rellenar el campo Descripción de producto
 
diff --git a/docs/tutorials/es/my-store-order-was-not-created.md b/docs/tutorials/es/my-store-order-was-not-created.md
index 2c6cf41fb..da3227d2c 100644
--- a/docs/tutorials/es/my-store-order-was-not-created.md
+++ b/docs/tutorials/es/my-store-order-was-not-created.md
@@ -43,9 +43,7 @@ Las siguientes soluciones se centran en la gestión del stock a través del Admi
 * **Actualizar recuento de stock:** en la fila correspondiente al SKU y almacén deseados, en la columna _Actualizar recuento_, ingresa el número de ítems disponibles para la venta y haz clic en `Guardar`. Este número debe ser positivo; lo contrario resultaría en un [stock negativo](https://help.vtex.com/es/faq/why-is-my-stock-negative--frequentlyAskedQuestions_159).
 * **Configurar stock ilimitado:** en la fila correspondiente al SKU y almacén deseados, en la columna Stock infinito, haz clic en el botón de activación y después en `Guardar`. Cuando se activa esta configuración, el ítem se considera siempre disponible para la venta y la tienda nunca presentará productos sin stock (agotados).
 
-<div class = "alert alert-info">
-Para realizar la configuración y que los productos sin stock (agotados) se muestren en tu storefront, accede al <b>Admin VTEX > Catálogo > Todos los productos</b> y en la página de configuración del producto, en la pestaña <b>Producto</b>, marca la opción <b>Sí</b> en el campo <i>Mostrar producto sin stock (agotado)</i>.
-</div>
+>ℹ️ Para realizar la configuración y que los productos sin stock (agotados) se muestren en tu storefront, accede al **Admin VTEX > Catálogo > Todos los productos** y en la página de configuración del producto, en la pestaña **Producto**, marca la opción **Sí** en el campo <i>Mostrar producto sin stock (agotado)</i>.
 
 ### Revisar la integración XML
 
diff --git a/docs/tutorials/es/offer-details.md b/docs/tutorials/es/offer-details.md
index 00d82ef11..136c52993 100644
--- a/docs/tutorials/es/offer-details.md
+++ b/docs/tutorials/es/offer-details.md
@@ -35,9 +35,7 @@ La página **Detalles del anuncio** incluye las siguientes secciones:
 - [Status del anuncio](#status-del-anuncio)    
 - [Lista de interacciones](#lista-de-interacciones)
 
-<div class = "alert alert-info">
-<b>Gestión de anuncios</b> permite hacer un seguimiento de los anuncios con <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre</a> (Classic y Premium), <a href="https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> y marketplaces VTEX. Para los conectores que desean integrarse a través de API, existe la <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Guía de integración de Gestión de anuncios</a>.
-</div>
+>ℹ️ **Gestión de anuncios** permite hacer un seguimiento de los anuncios con [Mercado Libre](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic y Premium), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y marketplaces VTEX. Para los conectores que desean integrarse a través de API, existe la [Guía de integración de Gestión de anuncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Encabezado
 
diff --git a/docs/tutorials/es/offer-management.md b/docs/tutorials/es/offer-management.md
index 4e3c74328..04a9c29a5 100644
--- a/docs/tutorials/es/offer-management.md
+++ b/docs/tutorials/es/offer-management.md
@@ -98,9 +98,7 @@ Puedes hacer clic sobre los nombres de las columnas para ordenar los anuncios de
 
 Para exportar la lista de anuncios en formato XLSX, haz clic sobre el ícono <i class="fa-solid fa-arrow-down-to-line"></i> flecha hacia abajo, ubicado en la parte superior de la interfaz. El archivo se enviará al email del usuario registrado. El tiempo que tarde la exportación dependerá de la cantidad de anuncios de la lista exportada y de cuestiones de procesamiento de la plataforma VTEX.
 
-<div class = "alert alert-info">
-El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
-</div>
+>ℹ️ El contenido exportado incluirá el total de anuncios de la lista al momento de la exportación. Si hay algún filtro activo, solo se exportarán los anuncios seleccionados.
 
 ## Consultar los anuncios no disponibles
 
diff --git a/docs/tutorials/es/oms-page-structure.md b/docs/tutorials/es/oms-page-structure.md
index b023e2cb5..8789635ff 100644
--- a/docs/tutorials/es/oms-page-structure.md
+++ b/docs/tutorials/es/oms-page-structure.md
@@ -15,9 +15,7 @@ legacySlug: estructura-de-la-pagina-del-oms
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class = "alert alert-info">
-Sobre la nueva interfaz del Order Management System (OMS), ver el artículo <a href="https://help.vtex.com/es/tutorial/order-list-beta--2QTduKHAJMFIZ3BAsi6Pi">Lista de Pedidos (Beta)</a>.
-</div>
+>ℹ️ Sobre la nueva interfaz del Order Management System (OMS), ver el artículo [Lista de Pedidos (Beta)](https://help.vtex.com/es/tutorial/order-list-beta--2QTduKHAJMFIZ3BAsi6Pi).
 
 Para entender mejor el __Gestión de Pedidos__, vea el descriptivo de cada área del módulo responsable por la visualización y gestión de los pedidos de su tienda.
 
diff --git a/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
index 8f0a12974..2f8cb37af 100644
--- a/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/es/opening-tickets-to-vtex-support-finacial.md
@@ -57,17 +57,11 @@ Esta clasificación es importante para que el equipo de soporte priorice los lla
 
 *Si el nivel indicado no se aplica al escenario del ticket, el agente puede modificarlo.*
 
-<div class = "alert alert-info">
-<strong>Normal:</strong> preguntas en general.
-</div>
+>ℹ️ **Normal:** preguntas en general.
 
-<div class = "alert alert-warning">
-<strong>Alto:</strong> las documentaciones importantes están inviabilizando el proceso.
-</div>
+>⚠️ **Alto:** las documentaciones importantes están inviabilizando el proceso.
 
-<div class = "alert alert-danger">
-<strong>Urgente:</strong> Admin bloqueado, amenazando el beneficio de su negocio.
-</div>
+>❗ **Urgente:** Admin bloqueado, amenazando el beneficio de su negocio.
 
 ## Interactuando en el ticket
 
diff --git a/docs/tutorials/es/operational-capacity-beta.md b/docs/tutorials/es/operational-capacity-beta.md
index ff80a051b..202463606 100644
--- a/docs/tutorials/es/operational-capacity-beta.md
+++ b/docs/tutorials/es/operational-capacity-beta.md
@@ -15,9 +15,7 @@ legacySlug: modulo-localidades
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class = "alert alert-info">
-Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar la <b>Capacidad operativa (Beta)</b>, completa el <a href="https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform">formulario de contacto</a>. El requisito para usar la funcionalidad es tener <a href="https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl">cuentas franquicia</a> asociadas a la <a href="https://help.vtex.com/es/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-cuenta-vtex">cuenta principal</a>.
-</div>
+>ℹ️ Esta funcionalidad se encuentra en la versión beta, por lo tanto, estamos trabajando para mejorarla. Si deseas utilizar la **Capacidad operativa (Beta)**, completa el [formulario de contacto](https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform). El requisito para usar la funcionalidad es tener [cuentas franquicia](https://help.vtex.com/es/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) asociadas a la [cuenta principal](https://help.vtex.com/es/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-cuenta-vtex).
 
 La página **Capacidad operativa** permite gestionar la capacidad de los sellers para recibir y preparar pedidos de la tienda, lo que te permite optimizar tu red logística. Puedes monitorear la distribución de pedidos entre los sellers y realizar [acciones](https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#acciones-en-la-pagina-de-detalles-del-seller) para mejorarla.
 
@@ -63,9 +61,7 @@ En la página **Envío > Capacidad operativa** del Admin VTEX, puedes realizar l
 
 En la barra de búsqueda puedes escribir el nombre de un seller para encontrarlo.
 
-<div class = "alert alert-info">
-Puedes asociar la búsqueda de sellers con el <a href="https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtrar-sellers">filtro de status</a>. Si no se devuelve ningún resultado, comprueba que no haya ningún filtro activo.
-</div>
+>ℹ️ Puedes asociar la búsqueda de sellers con el [filtro de status](https://help.vtex.com/es/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtrar-sellers). Si no se devuelve ningún resultado, comprueba que no haya ningún filtro activo.
 
 ### Filtrar sellers
 
diff --git a/docs/tutorials/es/order-allocation-algorithm-beta.md b/docs/tutorials/es/order-allocation-algorithm-beta.md
index 1edf52964..97d8f10bf 100644
--- a/docs/tutorials/es/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/es/order-allocation-algorithm-beta.md
@@ -31,9 +31,7 @@ subcategory: 13sVE3TApOK1C8jMVLTJRh
 | 6. Para cada opción de envío aplicable, el algoritmo calcula la tarifa que se mostrará al consumidor en el checkout según la regla de precios configurada en la opción de envío. | 6. El algoritmo calcula la tarifa que se mostrará al consumidor en el checkout según la regla de precios configurada en la opción de envío. |
 | 7. En la fase de checkout, se muestran al consumidor las opciones de envío seleccionadas junto con la previsión de costo y plazo de envío. | 7. En la fase de checkout, se muestran al consumidor todos los puntos de recogida que cubren los ítems del carrito. |
 
-<div class = "alert alert-info">
-El criterio de prioridad del <a href="https://help.vtex.com/es/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo actual</a> es buscar la menor división de paquetes del pedido. <b>Order Allocation Algorithm</b> tiene como criterio principal buscar el menor costo de envío para el administrador de la tienda.
-</div>
+>ℹ️ El criterio de prioridad del [algoritmo actual](https://help.vtex.com/es/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) es buscar la menor división de paquetes del pedido. **Order Allocation Algorithm** tiene como criterio principal buscar el menor costo de envío para el administrador de la tienda.
 
 Las próximas secciones presentan los detalles del funcionamiento del algoritmo y se dividen en:
 
@@ -74,8 +72,6 @@ Al analizar las combinaciones de puntos de fulfillment, el algoritmo toma en cue
 
 A través de la política de envío, el **Order Allocation Algorithm** simula las combinaciones de puntos de fulfillment buscando las que cumplen con el pedido al menor costo para el administrador de la tienda. El proceso se realiza mediante consultas a la [plantilla de envío](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127) y análisis de costo de las [transportadoras](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE).
 
-<div class = "alert alert-info">
-En el <a href="https://help.vtex.com/es/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo actual</a>, muchas veces el administrador de la tienda configura la <a href="https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127">plantilla de envío</a> con los valores que desea presentar al consumidor en el checkout y no con el costo real de las transportadoras. Con el <b>Order Allocation Algorithm</b>, el administrador de la tienda no tiene que tener en cuenta cómo el costo de la plantilla de envío se refleja en la experiencia de compra del consumidor, ya que ahora esto lo determina la configuración de las <a href="https://help.vtex.com/es/tutorial/shipping-options-beta--7gsdck3519Z3VPqzwFFHJL">opciones de envío</a>. Además, el <b>Order Allocation Algorithm</b> es más preciso al tomar como referencia los costos reales de las transportadoras.
-</div>
+>ℹ️ En el [algoritmo actual](https://help.vtex.com/es/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa), muchas veces el administrador de la tienda configura la [plantilla de envío](https://help.vtex.com/es/tutorial/planilha-de-frete--tutorials_127) con los valores que desea presentar al consumidor en el checkout y no con el costo real de las transportadoras. Con el **Order Allocation Algorithm**, el administrador de la tienda no tiene que tener en cuenta cómo el costo de la plantilla de envío se refleja en la experiencia de compra del consumidor, ya que ahora esto lo determina la configuración de las [opciones de envío](https://help.vtex.com/es/tutorial/shipping-options-beta--7gsdck3519Z3VPqzwFFHJL). Además, el **Order Allocation Algorithm** es más preciso al tomar como referencia los costos reales de las transportadoras.
 
 Después de analizar las posibles simulaciones, el **Order Allocation Algorithm** determina un resultado de combinaciones de puntos de fulfillment para cada opción de envío. En el checkout, se muestran al consumidor todas las opciones de envío que tienen por lo menos una combinación válida de puntos de fulfillment que cumplen con el pedido.
diff --git a/docs/tutorials/es/order-cancellation-requested-by-the-customer.md b/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
index 97a1323fc..fceabe818 100644
--- a/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/es/order-cancellation-requested-by-the-customer.md
@@ -19,9 +19,7 @@ Hay situaciones en las que los clientes pueden solicitar la cancelación de un p
 
 >❗ Después que se cancela el pedido, no se le puede cambiar el status.
 
-<div class = "alert alert-warning">
-No es posible <a href="https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186">cancelar</a> pedidos <a href="https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">parcialmente facturados</a>. Si el cliente desea sustituir o remover ítems del pedido, es posible <a href="https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">modificar el pedido</a>.
-</div>
+>⚠️ No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Cancelación en la ventana de cancelación
 
@@ -29,9 +27,7 @@ Cuando el cliente solicita la cancelación durante la [ventana de cancelación](
 
 * Esta acción la realiza el cliente en __Mis pedidos__, al hacer clic en `Solicitar cancelación del pedido`.
 
-<div class = "alert alert-info">
-Cuando el cliente solicita la cancelación del pedido durante la ventana de cancelación, la notificación de esta acción se envía únicamente al usuario con <a href="https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfil de acceso</a> de Titular de la cuenta (usuario master).
-</div>
+>ℹ️ Cuando el cliente solicita la cancelación del pedido durante la ventana de cancelación, la notificación de esta acción se envía únicamente al usuario con [perfil de acceso](https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) de Titular de la cuenta (usuario master).
 
 ## Cancelación aprobada por el administrador de la tienda
 
diff --git a/docs/tutorials/es/order-details-page.md b/docs/tutorials/es/order-details-page.md
index 6f4e46736..91ecc8c9e 100644
--- a/docs/tutorials/es/order-details-page.md
+++ b/docs/tutorials/es/order-details-page.md
@@ -15,9 +15,7 @@ legacySlug: pagina-de-detalles-del-pedido-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-<div class = "alert alert-info">
-Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
-</div>
+>ℹ️ Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 La página **Detalles del pedido** permite ver toda la información sobre un pedido y gestionarlo en un solo lugar. Para ver la página, haz clic en **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-los-pedidos--2QTduKHAJMFIZ3BAsi6Pi)** y selecciona un pedido de la lista.
 
@@ -44,9 +42,7 @@ La página **Detalles del pedido** está dividida en bloques que agrupan informa
 
 Para más información sobre el status y el flujo del pedido, consulta el artículo [Flujo y status de pedidos](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
 
-<div class = "alert alert-info">
-A continuación, se detallan todas las secciones posibles de la página <b>Detalles del pedido</b>, pero ten en cuenta que solo serán visibles las secciones que se aplican al pedido en cuestión.
-</div>
+>ℹ️ A continuación, se detallan todas las secciones posibles de la página **Detalles del pedido**, pero ten en cuenta que solo serán visibles las secciones que se aplican al pedido en cuestión.
 
 ## Barra superior
 
@@ -76,9 +72,7 @@ La información general del pedido se muestra en la parte superior de la página
   - Contacto (celular e email)    
 * **Entrega/Recogida:** datos del domicilio y del destinatario para realizar el envío a través de una transportadora o para que el cliente recoja el pedido de la tienda.    
 
-<div class = "alert alert-info">
-Haz clic en el ícono <i class="fas fa-chevron-right"></i> para ampliar el bloque.
-</div>
+>ℹ️ Haz clic en el ícono <i class="fas fa-chevron-right"></i> para ampliar el bloque.
 
 ### Status del pedido
 
diff --git a/docs/tutorials/es/order-flow-and-status.md b/docs/tutorials/es/order-flow-and-status.md
index 537ab6a0a..e7615c0a2 100644
--- a/docs/tutorials/es/order-flow-and-status.md
+++ b/docs/tutorials/es/order-flow-and-status.md
@@ -22,9 +22,7 @@ Este artículo contiene la siguiente información:
 - Una [tabla con todos los status mostrados en el Admin y las APIs](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#tabla-de-status-de-los-pedidos).
 - Los [casos en que se produce la cancelación de un pedido](https://help.vtex.com/es/tutorial/fluxo-e-status-de-pedidos--tutorials_196#cancelacion-del-pedido).
 
-<div class = "alert alert-info">
-Para saber cómo seguir el flujo de un pedido, consulta el artículo <a href="https://help.vtex.com/es/tutorial/acompanhamento-de-pedidos--et0Ei7F3bjcrEmVAR2kKS">Seguimiento de pedidos</a>.
-</div>
+>ℹ️ Para saber cómo seguir el flujo de un pedido, consulta el artículo [Seguimiento de pedidos](https://help.vtex.com/es/tutorial/acompanhamento-de-pedidos--et0Ei7F3bjcrEmVAR2kKS).
 
 ## Tipos de flujo
 
@@ -66,9 +64,7 @@ Este es el flujo del pedido visto por la tienda responsable de enviar los produc
 
 3. El status cambia automáticamente a `Periodo de cancelación`. El pedido permanecerá en esta etapa hasta que haya transcurrido el [tiempo de espera para cancelar configurado](https://help.vtex.com/es/tutorial/configuracoes-gerais/#pedidos). 
 
-  <div class = "alert alert-info">
-El Periodo de cancelación existe para que el cliente pueda cancelar la compra sin la aprobación de la tienda en un determinado periodo de tiempo previamente configurado. Después de este periodo, la tienda debe autorizar la solicitud de cancelación del cliente.
-</div>
+  >ℹ️ El Periodo de cancelación existe para que el cliente pueda cancelar la compra sin la aprobación de la tienda en un determinado periodo de tiempo previamente configurado. Después de este periodo, la tienda debe autorizar la solicitud de cancelación del cliente.
 
 4. En esta etapa hay dos posibilidades:
     * **Pedido no cancelado:** si la ventana de cancelación vence y el cliente no solicita la cancelación de la compra, el status pasa a `Listo para preparación`. Este status indica al _seller_ que el pedido ya debe ser preparado para el envío.
@@ -121,9 +117,7 @@ Cuando se solicita la cancelación de un pedido, la plataforma procesa automáti
 
 No es posible [cancelar](https://help.vtex.com/es/tutorial/como-cancelar-pedido--tutorials_186) pedidos [parcialmente facturados](https://help.vtex.com/es/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Si el cliente desea sustituir o remover ítems del pedido, es posible [modificar el pedido](https://help.vtex.com/es/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
-<div class = "alert alert-info">
-Ve más información sobre la cancelación y el reembolso en los artículos <a href="https://help.vtex.com/pt/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente">¿Por qué se cobró en la factura del cliente mi pedido cancelado?</a> y <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento">Reembolso o cancelación</a>.
-</div>
+>ℹ️ Ve más información sobre la cancelación y el reembolso en los artículos [¿Por qué se cobró en la factura del cliente mi pedido cancelado?](https://help.vtex.com/pt/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente) y [Reembolso o cancelación](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento).
 
 Mientras se realiza el proceso de cancelación, el status permanece en `Cancelando`. Una vez completada la cancelación, el status del pedido cambia a `Cancelado`. 
 
@@ -368,7 +362,5 @@ A continuación se muestra la tabla con los status de los pedidos. La informaci
 
 <br></br>
 
-<div class = "alert alert-info">
-Los status marcados con asteriscos (*) en la tabla no permiten cambio o cancelación, ya que están bajo la acción de la plataforma.
-</div>
+>ℹ️ Los status marcados con asteriscos (*) en la tabla no permiten cambio o cancelación, ya que están bajo la acción de la plataforma.
 
diff --git a/docs/tutorials/es/order-report.md b/docs/tutorials/es/order-report.md
index 5574d4bce..530eec91d 100644
--- a/docs/tutorials/es/order-report.md
+++ b/docs/tutorials/es/order-report.md
@@ -19,9 +19,7 @@ La exportación de pedidos en la página [Todos los pedidos](https://help.vtex.c
 
 Cada fila de la plantilla se refiere a un [SKU](https://help.vtex.com/es/tutorial/o-que-e-um-sku--1K75s4RXAQyOuGUYKMM68u). Por ejemplo, si en un pedido hay 3 SKUs, este será referenciado en 3 filas en el informe. Cada fila mostrará los datos de un SKU del pedido.
 
-<div class = "alert alert-info">
-El link del informe de pedidos está disponible para descargar durante seis horas.
-</div>
+>ℹ️ El link del informe de pedidos está disponible para descargar durante seis horas.
 
 Las columnas corresponden a información específica sobre el pedido, conforme se describe a continuación.
 
diff --git a/docs/tutorials/es/order-split-and-delivery-split.md b/docs/tutorials/es/order-split-and-delivery-split.md
index 0487657c8..d0e685a46 100644
--- a/docs/tutorials/es/order-split-and-delivery-split.md
+++ b/docs/tutorials/es/order-split-and-delivery-split.md
@@ -22,9 +22,7 @@ Ve a continuación las principales diferencias entre los escenarios de división
 * **[División de pedidos](#division-de-pedidos):** se produce cuando hay más de un _seller_ que atiende la misma compra. Esto significa que si hay tres _sellers_ para atender una misma compra, se generan tres pedidos. 
 * **[División de paquetes](#division-de-paquetes-entregas):** se produce cuando hay más de una entrega para un mismo pedido. Por ejemplo, cuando un único _seller_ es responsable de la entrega, pero el pedido se entrega en más de un envío. 
 
-<div class = "alert alert-info">
-Siempre que hay una división de pedidos, hay una división de paquetes. Además, un seller puede optar por dividir un mismo pedido en más de un paquete; así, al final de la compra, el número de paquetes siempre será mayor o igual que el número de pedidos generados.
-</div>
+>ℹ️ Siempre que hay una división de pedidos, hay una división de paquetes. Además, un seller puede optar por dividir un mismo pedido en más de un paquete; así, al final de la compra, el número de paquetes siempre será mayor o igual que el número de pedidos generados.
 
 Para facilitar la identificación de los casos en los que hay división de pedidos y división de entregas, mira algunos ejemplos a continuación:
 
diff --git a/docs/tutorials/es/order-status-table-oms.md b/docs/tutorials/es/order-status-table-oms.md
index d152ec6b8..b094258b8 100644
--- a/docs/tutorials/es/order-status-table-oms.md
+++ b/docs/tutorials/es/order-status-table-oms.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Este artículo tiene como objetivo enumerar los valores de estado compatibles en los diversos sistemas internos y externos a VTEX.
 
-<div class = "alert alert-warning">
-Caso válido para cuando el pedido tiene solo una transacción.
-</div>
+>⚠️ Caso válido para cuando el pedido tiene solo una transacción.
 
 <table style="width: 619px;" border="1" cellspacing="0" cellpadding="0"><tbody><tr style="height: 56px;"><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>Gestión de Pedidos</b>
 </td><td style="width: 113px; height: 56px;" valign="top"><p align="center"><b>Mis Ordenes</b>
diff --git a/docs/tutorials/es/order-tracking.md b/docs/tutorials/es/order-tracking.md
index 71ad9b229..8c09f57a7 100644
--- a/docs/tutorials/es/order-tracking.md
+++ b/docs/tutorials/es/order-tracking.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 La página [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi), permite hacer seguimiento de los pedidos de la tienda, y la página de [detalles del pedido](https://help.vtex.com/es/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl) permite ver toda la información sobre un pedido y gestionarlo en un solo lugar. Puedes comprobar en qué etapa se encuentra el pedido y sus interacciones; acceder a los datos del cliente, de la entrega y del pago; hacer un seguimiento de la entrega; y enviar [emails](https://help.vtex.com/es/tutorial/como-funciona-el-message-center--tutorials_84) al cliente.
 
-<div class = "alert alert-info">
-Para saber más, consulta el artículo <a href="https://help.vtex.com/es/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi">Todos los pedidos</a>. Para ver cuáles son los status del flujo de pedidos, consulta el artículo <a href="https://help.vtex.com/es/tutorial/flujo-de-pedido-en-el-oms--tutorials_196">Flujo y status de pedidos</a>.
-</div>
+>ℹ️ Para saber más, consulta el artículo [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi). Para ver cuáles son los status del flujo de pedidos, consulta el artículo [Flujo y status de pedidos](https://help.vtex.com/es/tutorial/flujo-de-pedido-en-el-oms--tutorials_196).
 
 Para hacer el seguimiento de un pedido, sigue los pasos a continuación:
 
diff --git a/docs/tutorials/es/orders-overview.md b/docs/tutorials/es/orders-overview.md
index df4a4ab74..19f758758 100644
--- a/docs/tutorials/es/orders-overview.md
+++ b/docs/tutorials/es/orders-overview.md
@@ -37,9 +37,7 @@ Además de buscar pedidos en **Pedidos > Todos los pedidos**, puede buscar pedid
 - Email del cliente
 - Documento del cliente
 
-<div class = "alert alert-info">
-Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
-</div>
+>ℹ️ Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 ## Suscripciones
 
diff --git a/docs/tutorials/es/physical-store-instore-beta.md b/docs/tutorials/es/physical-store-instore-beta.md
index 31c8835b3..400305d5c 100644
--- a/docs/tutorials/es/physical-store-instore-beta.md
+++ b/docs/tutorials/es/physical-store-instore-beta.md
@@ -15,9 +15,7 @@ legacySlug: tienda-fisica-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>Esta funcionalidad se encuentra en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de duda, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de duda, póngase en contacto con [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 **Tienda física** es una de las páginas de **Configuración de la tienda** del Admin VTEX que muestra una lista de tiendas físicas registradas en la aplicación [inStore](https://help.vtex.com/es/tracks/instore-primeros-pasos-y-configuracion--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). En ella, puedes gestionar la información de todas las tiendas físicas de la cuenta.
 
@@ -77,9 +75,7 @@ Puedes crear una tienda física siguiendo los pasos a continuación:
 * **Política comercial:** [política comercial](https://help.vtex.com/es/tutorial/como-funciona-una-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será aplicada na loja física. Campo obrigatório.
 * **Punto de recogida:** [punto de recogida](https://help.vtex.com/es/tutorial/puntos-de-recogida--2fljn6wLjn8M4lJHA6HP3R) registrado para esta tienda física, donde los clientes recogen sus pedidos.
 
-<div class ="alert alert-info">
-<p>Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en inStore.</p> 
-</div>
+>ℹ️ Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en inStore.
 
 ## Buscar tienda
 
diff --git a/docs/tutorials/es/pickup-points.md b/docs/tutorials/es/pickup-points.md
index 79ce7593b..e9647cbbf 100644
--- a/docs/tutorials/es/pickup-points.md
+++ b/docs/tutorials/es/pickup-points.md
@@ -41,12 +41,13 @@ Es importante observar que:
 * VTEX limita la ubicación a un radio de 50 km entre el punto de recogida y la dirección del cliente.
 * Cuando hay transporte entre el [stock](https://help.vtex.com/en/tutorial/warehouse--6oIxvsVDTtGpO7y6zwhGpb) y el punto de recogida, VTEX también toma en cuenta la existencia de la ruta a la hora de elegir el punto de recogida.
 
-<div class = "alert alert-info">Con los puntos de recogida, VTEX también hace posible que el administrador de la tienda:
-<body>
-<ul>
-<li>Configure puntos de recogida de contingencia: puntos de recogida que pueden suministrar stock a otros puntos cuando sea necesario y así permitir la elección más conveniente para el comprador. Para obtener más información, visite <a href="https://help.vtex.com/en/tutorial/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout--3mowqWEfjyM2g6WoWgE0Ao">Punto de recogida de contingencia.</a></li>
-<li>Configure un seller white label como punto de recogida. Obtenga más información en <a href="https://help.vtex.com/en/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e">Configurar seller white label como punto de recogida (pickup point)</a>.</li>
-</ul></body></div>
+>ℹ️ Con los puntos de recogida, VTEX también hace posible que el administrador de la tienda:
+> <body>
+>
+> *Configure puntos de recogida de contingencia: puntos de recogida que pueden suministrar stock a otros puntos cuando sea necesario y así permitir la elección más conveniente para el comprador. Para obtener más información, visite [Punto de recogida de contingencia.](https://help.vtex.com/en/tutorial/creating-a-contingency-pickup-point-to-guarantee-it-as-an-option-at-checkout--3mowqWEfjyM2g6WoWgE0Ao)
+>
+> *Configure un seller white label como punto de recogida. Obtenga más información en [Configurar seller white label como punto de recogida (pickup point)](https://help.vtex.com/en/tutorial/setting-up-seller-white-label-as-a-pickup-point--6fSUE2O0taaoKieAaiuc4e).
+> </body>
 
 Es importante verificar que la configuración de la cantidad de puntos de recogida esté dentro de los límites aceptados y de acuerdo con la estrategia de ventas de la tienda. Esto permite que la [simulación de envío](https://help.vtex.com/es/tutorial/simulador-de-envio--tutorials_144) considere correctamente los datos y asegura, por ejemplo, que el número de puntos de recogida no limita la operación de la tienda.
 
@@ -68,9 +69,9 @@ VTEX considera que el punto de recogida es una forma de envío. Es por eso que l
     - Paso 2: Haz clic en la pestaña **Políticas de envío**, selecciona la política de envío creada para el punto de recogida.
     - Paso 3: En la columna **Acciones**, haz clic en el ícono <i class="fas fa-pen"></i> para editar.
     - Paso 4: Activa el botón <i class="fas fa-toggle-on"></i> del campo **Asociar puntos de recogida**.
-    - Paso 5: Selecciona el punto de recogida mediante los campos disponibles.![relacionarpontosretiradaES](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/d72f0278d6fdbb3041d883fa4685f436/relacionarpontosretiradaES.png) <div class = "alert alert-info">Para las tiendas que tienen más de 50 puntos de recogida, recomendamos utilizar el campo Tags de <a href="https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140#registrar-politica-de-envio">los puntos de recogida al crear un punto de recogida</a>. Utilizar tags facilita la búsqueda de los puntos de recogida al asociarlos con la política de envío.También recuerda que la política de envío que está asociada a un punto de recogida no estará disponible para otros tipos de envíos. Recomendamos crear una política de envío dedicada al punto de recogida.</div>
+    - Paso 5: Selecciona el punto de recogida mediante los campos disponibles.![relacionarpontosretiradaES](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/d72f0278d6fdbb3041d883fa4685f436/relacionarpontosretiradaES.png) >ℹ️ Para las tiendas que tienen más de 50 puntos de recogida, recomendamos utilizar el campo Tags de [los puntos de recogida al crear un punto de recogida](https://help.vtex.com/es/tutorial/politica-de-envio--tutorials_140#registrar-politica-de-envio). Utilizar tags facilita la búsqueda de los puntos de recogida al asociarlos con la política de envío.También recuerda que la política de envío que está asociada a un punto de recogida no estará disponible para otros tipos de envíos. Recomendamos crear una política de envío dedicada al punto de recogida.
 
-4. [Registrar la geolocalización](https://help.vtex.com/es/tutorial/gestionar-geolocalizacion--tutorials_138): para una mayor precisión de la ubicación de los puntos de recogida en el _checkout_.<div class = "alert alert-info">La visualización de los puntos de recogida con el mapa y la hora en el checkout solo está disponible para Checkout V6.</div>
+4. [Registrar la geolocalización](https://help.vtex.com/es/tutorial/gestionar-geolocalizacion--tutorials_138): para una mayor precisión de la ubicación de los puntos de recogida en el _checkout_.>ℹ️ La visualización de los puntos de recogida con el mapa y la hora en el checkout solo está disponible para Checkout V6.
 
 5. Habilitar la solicitud de dirección en el checkout. De este modo, el cliente tiene que agregar la dirección que se utilizará en la factura:
     - Paso 1: En el Admin VTEX, accede a **Configuración de la tienda > Storefront > Checkout**, o escribe *Checkout* en la barra de búsqueda en la parte superior de la página.  
diff --git a/docs/tutorials/es/platform-status-page.md b/docs/tutorials/es/platform-status-page.md
index e409fecf0..dcd0de6ea 100644
--- a/docs/tutorials/es/platform-status-page.md
+++ b/docs/tutorials/es/platform-status-page.md
@@ -21,9 +21,7 @@ Los eventos son reportados por nuestro equipo siempre que nuestro sistema autom
 
 A continuación, encontrarás información detallada sobre los elementos de la página de status de la plataforma VTEX.
 
-<div class = "alert alert-info">
-La página de status se desarrolla con la herramienta Atlassian Statuspage.
-</div>
+>ℹ️ La página de status se desarrolla con la herramienta Atlassian Statuspage.
 
 ## Notificaciones
 
diff --git a/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md b/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md
index 9fa79e55d..a476df440 100644
--- a/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md
+++ b/docs/tutorials/es/prevent-a-carrier-from-meeting-certain-zip-code-range.md
@@ -34,6 +34,4 @@ Para ello, siga estos pasos:
 
 Con ello, la planilla de flete pasaría a "saltar" el código postal 45920-000. Por lo tanto, ya no se consideraría como una opción de dirección atendida por ese transportista.
 
-<div class = "alert alert-info">
-Los ejemplos de códigos postales de este artículo se refieren a Brasil, cada país tiene su propio formato de código postal.
-</div>
+>ℹ️ Los ejemplos de códigos postales de este artículo se refieren a Brasil, cada país tiene su propio formato de código postal.
diff --git a/docs/tutorials/es/price-divergence-rule.md b/docs/tutorials/es/price-divergence-rule.md
index 30fd3f4c0..2a27e7f85 100644
--- a/docs/tutorials/es/price-divergence-rule.md
+++ b/docs/tutorials/es/price-divergence-rule.md
@@ -47,9 +47,7 @@ Para crear una regla de Divergencia de precios, el usuario debe tener el rol Adm
 
 Puedes hacer el seguimiento de los pedidos integrados a partir de la regla de Divergencia de precios en el Admin VTEX, en **Pedidos > [Todos los pedidos](https://help.vtex.com/es/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**.
 
-<div class = "alert alert-info">
-Es importante hacer un seguimiento periódico de los pedidos en la Gestión de pedidos. Si requieren aprobación manual, los pedidos quedan pendientes hasta que un usuario habilitado conceda la autorización necesaria.
-</div>
+>ℹ️ Es importante hacer un seguimiento periódico de los pedidos en la Gestión de pedidos. Si requieren aprobación manual, los pedidos quedan pendientes hasta que un usuario habilitado conceda la autorización necesaria.
 
 ### Más información
 
diff --git a/docs/tutorials/es/prices-settings.md b/docs/tutorials/es/prices-settings.md
index a3c10b537..ee9d70c4a 100644
--- a/docs/tutorials/es/prices-settings.md
+++ b/docs/tutorials/es/prices-settings.md
@@ -35,6 +35,4 @@ Consulte los ajustes disponibles a continuación:
 
 - **Sobrescribir precios de sellers:**  esta opción sobrescribe todos los precios de sellers con los de la cuenta actual.
 
-  <div class = "alert alert-info">
-    <p>La configuración <b>Sobrescribir precios de sellers</b> no está disponible para sellers White label.</p>
-  </div>
+  >ℹ️ La configuración **Sobrescribir precios de sellers** no está disponible para sellers White label.
diff --git a/docs/tutorials/es/promotion-alerts-beta.md b/docs/tutorials/es/promotion-alerts-beta.md
index 6606c4d1c..6e7f02cf7 100644
--- a/docs/tutorials/es/promotion-alerts-beta.md
+++ b/docs/tutorials/es/promotion-alerts-beta.md
@@ -15,9 +15,7 @@ legacySlug: alertas-de-promociones-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class = "alert alert-info">
-Este módulo está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro <a href="https://help.vtex.com/es/support">equipo de soporte</a>.
-</div>
+>ℹ️ Este módulo está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro [equipo de soporte](https://help.vtex.com/es/support).
 
 Crear promociones es una buena estrategia para atraer a más compradores a tu sitio de ecommerce. Al configurarlas, es muy importante tener cuidado de que los descuentos aplicados tengan los efectos esperados, ya que los errores al registrar promociones pueden causar pérdidas de ingresos.
 
diff --git a/docs/tutorials/es/promotion-alerts-how-to-create-an-alert-beta.md b/docs/tutorials/es/promotion-alerts-how-to-create-an-alert-beta.md
index 7a17a8e85..9602e9385 100644
--- a/docs/tutorials/es/promotion-alerts-how-to-create-an-alert-beta.md
+++ b/docs/tutorials/es/promotion-alerts-how-to-create-an-alert-beta.md
@@ -15,9 +15,7 @@ legacySlug: alerta-de-promociones-como-crear-una-alerta-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class = "alert alert-info">
-Este módulo está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro <a href="https://support.vtex.com/hc/pt-br/requests">equipo de soporte</a>.
-</div>
+>ℹ️ Este módulo está en fase beta. Esto significa que estamos trabajando para mejorarlo. Si tienes alguna duda, por favor ponte en contacto con nuestro [equipo de soporte](https://support.vtex.com/hc/pt-br/requests).
 
 Crear promociones es una buena estrategia para atraer a más compradores a tu sitio de ecommerce. Al configurarlas, es muy importante tener cuidado de que los descuentos aplicados tengan los efectos esperados, ya que los errores al registrar promociones pueden causar pérdidas de ingresos.
 
diff --git a/docs/tutorials/es/promotion-examples.md b/docs/tutorials/es/promotion-examples.md
index 411ffc8bb..147016924 100644
--- a/docs/tutorials/es/promotion-examples.md
+++ b/docs/tutorials/es/promotion-examples.md
@@ -95,9 +95,7 @@ Compre un suéter y obtenga 50% de descuento en una camisa de manga larga, clás
 - "Compre un suéter y obtenga 50%" en otro artículo, hace que esto sea una [Promoción Comprar Juntos](https://help.vtex.com/es/tutorial/buy-together--tutorials_323).
 - "Suéter y camisa de manga larga, clásica o contemporánea" son los artículos a los que se aplicará este beneficio.
 
-<div class = "alert alert-warning">
-  <p>La Promoción Comprar Juntos funciona solamente con un porcentaje de descuento.</p>
-</div>
+>⚠️ La Promoción Comprar Juntos funciona solamente con un porcentaje de descuento.
 
 ## Escenario 12
 
diff --git a/docs/tutorials/es/protection-against-transaction-attacks.md b/docs/tutorials/es/protection-against-transaction-attacks.md
index c96a347c8..a4afabadc 100644
--- a/docs/tutorials/es/protection-against-transaction-attacks.md
+++ b/docs/tutorials/es/protection-against-transaction-attacks.md
@@ -21,8 +21,7 @@ La protección contra los ataques a las transacciones es una de las soluciones q
 
 En su primera versión, cuando se active, la protección consistirá en aplicar un cambio en el flujo de pago de la compra. Esto no provocará un aumento del tiempo del pedido ni una disminución de la conversión de la tienda. Una vez cerrado el pedido, el consumidor recibirá posteriormente el mensaje de pago aprobado (o rechazado) a través de un mensaje electrónico (email o SMS).
 
-<div class = "alert alert-info"> La protección no impide totalmente que la tienda sufra ataques a tarjetas, pero reduce considerablemente el número de estos eventos. De este modo, las transacciones se vuelven más seguras.
-</div>
+>ℹ️ La protección no impide totalmente que la tienda sufra ataques a tarjetas, pero reduce considerablemente el número de estos eventos. De este modo, las transacciones se vuelven más seguras.
 
 ### ¿Cómo activar la protección contra los ataques a las transacciones?
 
@@ -42,8 +41,7 @@ Para activar la protección, mira el paso a paso que se muestra a continuación.
 
 ### ¿Cómo desactivar la protección contra los ataques a las transacciones?
 
-<div class = "alert alert-danger"> Desactivar la protección contra los ataques a las transacciones aumenta el riesgo de fraude de pruebas de tarjetas (operación realizada por un defraudador que utiliza un gran número de datos de tarjetas para realizar transacciones fraudulentas). En caso de ataques que puedan dañar uno o varios sistemas internos de VTEX, la plataforma podrá reactivar obligatoriamente la protección contra ataques, y el administrador de la tienda será informado de esta operación.
-</div>
+>❗ Desactivar la protección contra los ataques a las transacciones aumenta el riesgo de fraude de pruebas de tarjetas (operación realizada por un defraudador que utiliza un gran número de datos de tarjetas para realizar transacciones fraudulentas). En caso de ataques que puedan dañar uno o varios sistemas internos de VTEX, la plataforma podrá reactivar obligatoriamente la protección contra ataques, y el administrador de la tienda será informado de esta operación.
 
 Para desactivar la protección, mira el paso a paso que se muestra a continuación.
 
diff --git a/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
index 9a88c47ed..74692de45 100644
--- a/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
+++ b/docs/tutorials/es/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -26,9 +26,7 @@ Los principales beneficios de la funcionalidad son:
 
 **Aumento de las tasas de conversión y ventas:** incentiva a los clientes a volver a la página de checkout para finalizar su compra, aumentando así las ventas y las tasas de conversión de los retailers.
 
-<div class = "alert alert-info">
-WhatsApp AI Campaigns solamente está disponible para tiendas que utilizan <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> y no tienen personalizaciones en Checkout.
-</div>
+>ℹ️ WhatsApp AI Campaigns solamente está disponible para tiendas que utilizan [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) y no tienen personalizaciones en Checkout.
 
 ## Activar WhatsApp AI Campaigns
 
@@ -56,9 +54,7 @@ Para instalar la aplicación Connectly sigue los pasos que se indican a continua
 
 Para configurar un nuevo número de WhatsApp necesitarás acceso de administrador a tu perfil de Meta. Sigue las instrucciones para configurar un nuevo número y completar la asociación:
 
-<div class = "alert alert-info">
-Se recomienda crear un nuevo número de teléfono exclusivamente para vincularlo a WhatsApp Business. Esto ayuda a evitar pérdidas de acceso a números utilizados anteriormente para otros fines.
-</div>
+>ℹ️ Se recomienda crear un nuevo número de teléfono exclusivamente para vincularlo a WhatsApp Business. Esto ayuda a evitar pérdidas de acceso a números utilizados anteriormente para otros fines.
 
 <ol start="1">
   <li>En el Admin VTEX, ve a <strong>Promociones &gt; Campañas de WhatsApp &gt; Vista general</strong>, o ingresa <strong>Vista general de Campañas de WhatsApp</strong> en la barra de búsqueda de la parte superior de la página.</li>
@@ -107,7 +103,5 @@ Se recomienda crear un nuevo número de teléfono exclusivamente para vincularlo
 
 >⚠️ Una vez que se ha activado una campaña de recuperación de checkout abandonado pueden transcurrir hasta 48 horas para que comiencen a mostrarse las métricas de análisis.
 
-<div class = "alert alert-info">
-Aprende más sobre <a href="https://help.vtex.com/es/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">Gestión y detalles de WhatsApp AI Campaigns</a>.
-</div>
+>ℹ️ Aprende más sobre [Gestión y detalles de WhatsApp AI Campaigns](https://help.vtex.com/es/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s).
 
diff --git a/docs/tutorials/es/register-tracking-on-the-tax-receipt.md b/docs/tutorials/es/register-tracking-on-the-tax-receipt.md
index a6e0a10e7..679bb8c4c 100644
--- a/docs/tutorials/es/register-tracking-on-the-tax-receipt.md
+++ b/docs/tutorials/es/register-tracking-on-the-tax-receipt.md
@@ -30,6 +30,4 @@ Para registrar el rastreo en la nota fiscal, sigue los pasos a continuación:
     - Transportadora
 7. Haz click en `Guardar factura`.
 
-<div class = "alert alert-info">
-Al registrar el rastreo en la nota fiscal, es posible cambiar la <a href="https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE">transportadora</a> asociada al pedido. Para hacer esto, en la sección <b>Seguimiento del pedido</b>, haga clic en <i>Transportadora</i> y seleccione la opción deseada.
-</div>
+>ℹ️ Al registrar el rastreo en la nota fiscal, es posible cambiar la [transportadora](https://help.vtex.com/es/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) asociada al pedido. Para hacer esto, en la sección **Seguimiento del pedido**, haga clic en <i>Transportadora</i> y seleccione la opción deseada.
diff --git a/docs/tutorials/es/registering-a-category.md b/docs/tutorials/es/registering-a-category.md
index ebedc81fc..dd0927649 100644
--- a/docs/tutorials/es/registering-a-category.md
+++ b/docs/tutorials/es/registering-a-category.md
@@ -15,9 +15,7 @@ legacySlug: registrando-categoria
 subcategory: 1E7tziZCkY4w8i4EmUuwec
 ---
 
-<div class = "alert alert-info">
-En la plataforma VTEX, la estructura Departamento, Categoría y subcategoría no está predefinida. Se varía de acuerdo con la estructura de su tienda, no siendo obligatoria la creación de estos 3 niveles jerárquicos.
-</div>
+>ℹ️ En la plataforma VTEX, la estructura Departamento, Categoría y subcategoría no está predefinida. Se varía de acuerdo con la estructura de su tienda, no siendo obligatoria la creación de estos 3 niveles jerárquicos.
 
 El registro de una Categoría ocurre dentro del Catálogo, en el Admin VTEX.
 
diff --git a/docs/tutorials/es/registering-gateway-affiliations.md b/docs/tutorials/es/registering-gateway-affiliations.md
index 0c9991e65..8217de627 100644
--- a/docs/tutorials/es/registering-gateway-affiliations.md
+++ b/docs/tutorials/es/registering-gateway-affiliations.md
@@ -35,13 +35,9 @@ Para agregar un nuevo proveedor de pago o antifraude a tu tienda, sigue los paso
 5. Si aparece un mensaje de alerta que diga que se debe instalar la aplicación, haz clic en el botón __Instalar aplicación__ y sigue las instrucciones de instalación. El mensaje solo se muestra en algunos tipos de proveedores de gateway.
 6. Haz clic en `Guardar`.
 
-<div class = "alert alert-info">
-  <p>Si hay otros campos que rellenar además de Clave de aplicación y Token de aplicación (paso 6), la configuración del proveedor de gateway se debe llevar a cabo siguiendo el tutorial correspondiente. Para más información, consulta la subsección <a href="https://help.vtex.com/es/subcategory/configuracion-de-pagos--3tDGibM2tqMyqIyukqmmMw">Configuración de Pagos</a>.</p>
-</div>
+>ℹ️ Si hay otros campos que rellenar además de Clave de aplicación y Token de aplicación (paso 6), la configuración del proveedor de gateway se debe llevar a cabo siguiendo el tutorial correspondiente. Para más información, consulta la subsección [Configuración de Pagos](https://help.vtex.com/es/subcategory/configuracion-de-pagos--3tDGibM2tqMyqIyukqmmMw).
 
-<div class = "alert alert-danger">
-Las credenciales utilizadas para rellenar los campos Clave de aplicación y Token de aplicación las debe informar el proveedor de pago para identificar la tienda. No se deben utilizar las credenciales <a href="https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet">generadas en el Admin</a>, que empiezan por <code>vtexappkey-</code>.
-</div>
+>❗ Las credenciales utilizadas para rellenar los campos Clave de aplicación y Token de aplicación las debe informar el proveedor de pago para identificar la tienda. No se deben utilizar las credenciales [generadas en el Admin](https://help.vtex.com/es/tutorial/claves-de-aplicacion--2iffYzlvvz4BDMr6WGUtet), que empiezan por `vtexappkey-`.
 
 Para configurar los medios de pago que el proveedor escogido procesará, accede a [Configurar condiciones de pago](https://help.vtex.com/es/tutorial/condiciones-de-pago--tutorials_455). 
 
@@ -75,8 +71,7 @@ Para cambiar la lista de proveedores usando filtros, accede a la página de gest
 
 ![interface_provedor_ES_6](https://images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/5aae0659cf9128a58fe3ce02d03a6023/interface_provedor_ES_6.JPG)
 
-<div class = "alert alert-danger">
-Para remover los filtros aplicados y ver todos los proveedores registrados en la tienda, haz clic en el botón <code>Limpiar todo</code>.</div>
+>❗ Para remover los filtros aplicados y ver todos los proveedores registrados en la tienda, haz clic en el botón `Limpiar todo`.
 
 ## Editar configuración de un proveedor
 
@@ -89,5 +84,4 @@ Para editar la configuración de un proveedor de pago o antifraude registrado en
 
 ![interface_provedor_ES_7](https://images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/4931462bfe35657876f4a5e6c63d5386/artigo_interface_provedor_ES_7.JPG)
 
-<div class = "alert alert-danger">
-Antes de editar la configuración de un proveedor, como datos de autorización, modo de procesamiento o tipo de reembolso, asegúrate de verificar que la nueva información no afecte el rendimiento operativo de la tienda.</div>
+>❗ Antes de editar la configuración de un proveedor, como datos de autorización, modo de procesamiento o tipo de reembolso, asegúrate de verificar que la nueva información no afecte el rendimiento operativo de la tienda.
diff --git a/docs/tutorials/es/registering-geolocation.md b/docs/tutorials/es/registering-geolocation.md
index eaaa5ff18..597ddf045 100644
--- a/docs/tutorials/es/registering-geolocation.md
+++ b/docs/tutorials/es/registering-geolocation.md
@@ -57,9 +57,7 @@ Un ejemplo de cómo quedaría es:
 
 Después, basta guardar.
 
-<div class = "alert alert-warning">
- Listo, ahora es sólo utilizar ese mismo ID en la plantilla de flete en la columna <b>PolygonName</b>. Es importante atentarse en el llenado, pues ese transportista no utilizará las columnas <b>ZipCodeStart</b> y <b>ZipCodeStart</b>, que deberán quedar en blanco.
-</div>
+>⚠️ Listo, ahora es sólo utilizar ese mismo ID en la plantilla de flete en la columna **PolygonName**. Es importante atentarse en el llenado, pues ese transportista no utilizará las columnas **ZipCodeStart** y **ZipCodeStart**, que deberán quedar en blanco.
 
 En **Configuración de la tienda > Storefront > Checkout**, en la [pestaña Checkout](https://help.vtex.com/es/tutorial/geolocalizacao-no-checkout/), el campo API Key debe rellenarse con la misma clave que se utilizó para activar la geolocalización.
 
@@ -84,6 +82,4 @@ Caso necesite alterar algún lugar de entrega de un polígono que ya existe, ust
 
 Aquí el proceso es todavía más simples, pues no será necesario alterar ninguna información en la plantilla de flete, visto que es a través del ID que el sistema hace la consulta.
 
-<div class = "alert alert-warning"> 
-  En el caso de que el transportista y la hoja de flete hayan sido creados antes de registrar el Polígono, recomendamos que sea editada la compañía que tiene vínculo con ese Polígono, para actualizar la relación. Con esto después de la Creación o Cambio de un Poligono, abra la compañía y haga clic en Guardar, sólo para sensibilizar una actualización.
-</div>
+>⚠️ En el caso de que el transportista y la hoja de flete hayan sido creados antes de registrar el Polígono, recomendamos que sea editada la compañía que tiene vínculo con ese Polígono, para actualizar la relación. Con esto después de la Creación o Cambio de un Poligono, abra la compañía y haga clic en Guardar, sólo para sensibilizar una actualización.
diff --git a/docs/tutorials/es/regular-promotion.md b/docs/tutorials/es/regular-promotion.md
index bd8bc7d08..e08432526 100644
--- a/docs/tutorials/es/regular-promotion.md
+++ b/docs/tutorials/es/regular-promotion.md
@@ -47,9 +47,7 @@ En esta sección, debe configurar los datos generales de la promoción. Los camp
   - **Envío máximo**: es el valor máximo establecido para el flete. 
   - **Flete gratis**: es el descuento total sobre el valor del flete.
   - **Regalo**: es el descuento total sobre el valor del producto definido como regalo. Puede seleccionar uno o más SKU como regalos, o más de una unidad para el mismo SKU. Para definir más de un regalo, escoja la opción **Activar multiplicador de regalo** y defina la cantidad deseada. Lea más sobre esta opción en este [artículo](https://help.vtex.com/es/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK#).
-<div class = "alert alert-info">
-  <p>El producto de regalo también debe tener un precio registrado aunque se dé al cliente de forma gratuita.</p>
-</div>
+>ℹ️ El producto de regalo también debe tener un precio registrado aunque se dé al cliente de forma gratuita.
   - **Descuento nominal basado en la fórmula**: el descuento se calcula en base a la fórmula que puede crear utilizando como variables la suma de los precios de los productos (`total`), el flete (`freight`) y la cantidad de artículos (`quantity`). Tenga en cuenta que el flete considerado por la fórmula será el más bajo disponible para el pedido, independientemente de la selección del cliente. El separador decimal debe ser siempre un punto. Ejemplo: si el descuento es del 30% del valor total del producto + el valor del flete, la fórmula debe ser `(total + flete) * 0,3`. Para más información sobre la fórmula, lea nuestra [documentación](https://help.vtex.com/es/tutorial/promocion-regular-con-descuento-nominal-basado-en-la-formula--2Pwrq6THyGViNedQG381jV).
   - **Valor de fidelidad nominal:** es el crédito que será añadido al programa de fidelidad de la tienda. Lea [Promoción regular con valor de fidelidad](https://help.vtex.com/es/tutorial/promocion-regular-con-valor-de-fidelidad--3FCip23ZtvG0sDt0rVGVmR) para más información.
   - **Valor de fidelidad porcentual**: es el porcentaje de crédito que se añadirá al programa de fidelidad de la tienda. Lea [Promoción regular con valor de fidelidad](https://help.vtex.com/es/tutorial/promocion-regular-con-valor-de-fidelidad--3FCip23ZtvG0sDt0rVGVmR) para más información.
@@ -57,9 +55,7 @@ En esta sección, debe configurar los datos generales de la promoción. Los camp
 
 - **Destaque en los productos**: inserta una flag con el nombre de la promoción, usada en la vitrina y en la página del producto. Esta flag solo se insertará si se utiliza el control correcto de exhibición de promoción en el formato: `<vtex.cmc:discountHightLight/>`
 
-<div class = "alert alert-info">
-  <p>Las promociones del tipo <b>Nominal</b> solo se presentarán en el carrito, no en la vitrina o en la página de producto.</p>
-</div>
+>ℹ️ Las promociones del tipo **Nominal** solo se presentarán en el carrito, no en la vitrina o en la página de producto.
 
 ### Restringir esta promoción a productos dos sellers
 
@@ -70,9 +66,7 @@ En esta sección, se puede definir a qué *sellers* se aplicará la promoción.
 
 Para que la promoción sea válida para todos los *sellers*, deje la selección sin marcar.
 
-<div class = "alert alert-warning">
-  <p>No es posible seleccionar directamente un <em>seller white label</em>. Para incluir a un <em>seller white label</em> en la promoción, tiene dos opciones:</p><ol>1. Restringir a los <em>sellers</em> a la tienda principal. Esta restricción agrega a todos los <em>sellers white label</em> de su tienda a la promoción.</ol><ol>2. Dejar la selección sin marcar para incluir a todos los <em>sellers</em>. Aquí, todos los tipos de <em>sellers</em>, <em>white label</em> o no, se agregarán a la promoción.</ol>
-</div>
+>⚠️ No es posible seleccionar directamente un *seller white label*. Para incluir a un *seller white label* en la promoción, tiene dos opciones:1. Restringir a los *sellers* a la tienda principal. Esta restricción agrega a todos los *sellers white label* de su tienda a la promoción.2. Dejar la selección sin marcar para incluir a todos los *sellers*. Aquí, todos los tipos de *sellers*, *white label* o no, se agregarán a la promoción.
 
 ### Política Comercial
 
@@ -103,9 +97,7 @@ Vea a continuación un ejemplo de cómo rellenarlo. En este caso, participan en
 
 En los campos **Productos** y **SKUs**, se puede cargar un archivo **.txt** con un ID de producto o de SKU por fila, en vez de seleccionar un producto o un SKU a la vez. Para ello, debe hacer clic en **Elegir archivo** y seleccionar el archivo **.txt** deseado.
 
-<div class = "alert alert-warning">
-<p>Si selecciona<strong> Aplicar a los siguientes productos</strong> y no rellena ninguno de los criterios de selección, la promoción no se creará y aparecerá el mensaje <strong>Defina los productos elegibles o aplique a todos los productos</strong>. En este caso, debe volver y rellenar los criterios de selección o elegir <strong>Aplicar a todos los productos.</strong></p>
-</div>
+>⚠️ Si selecciona** Aplicar a los siguientes productos** y no rellena ninguno de los criterios de selección, la promoción no se creará y aparecerá el mensaje **Defina los productos elegibles o aplique a todos los productos**. En este caso, debe volver y rellenar los criterios de selección o elegir **Aplicar a todos los productos.**
 
 Para ser válidos en la promoción, los productos deben cumplir todas las condiciones registradas en esta sección.
 
@@ -128,25 +120,19 @@ El pedido del cliente debe cumplir las condiciones registradas en esta sección
 - **Aplicar el descuento solamente cuando el cliente seleccione uno de los transportistas anteriores:** la promoción se aplicará solo después de que el cliente seleccione la forma de entrega en cuestión. Mientras no se seleccione, no tendrá descuento. Este criterio solo se considerará si la promoción está relacionada con el Valor de Flete, es decir, en alguno de los siguientes casos: Carga porcentual», «Carga nominal», «Envío máximo» o «Flete gratis».
 - **Medio de pago:** se concederá el descuento si el medio de pago seleccionado por el cliente es igual al registrado. Este descuento solo se aplica al finalizar la compra, cuando el cliente seleccione el mismo medio de pago registrado aquí.
 
- <div class = "alert alert-info">
-  <p> Por estándar, puede registrar hasta 20 medios de pago por promoción. Además, existe la posibilidad de personalización para incluir hasta 100 medios de pago. Si necesita utilizar más de 20, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro servicio de asistencia
-técnica</a>.</p>
- </div>
+ >ℹ️ Por estándar, puede registrar hasta 20 medios de pago por promoción. Además, existe la posibilidad de personalización para incluir hasta 100 medios de pago. Si necesita utilizar más de 20, contacte a <a href="https://support.vtex.com/hc/pt-br/requests">nuestro servicio de asistencia
+> técnica</a>.
 
 - **Número de cuotas:** se concederá el descuento si el número de cuotas seleccionado por el cliente está dentro del intervalo registrado. Este campo no se aplica para la selección de boleto bancario.
 
-<div class = "alert alert-warning">
-  <p><b>Atención</b>: las promociones por medio de pago y/o número de cuotas no se aplican a pedidos pagados con dos tarjetas o vales de compra.</p>
-</div>
+>⚠️ **Atención**: las promociones por medio de pago y/o número de cuotas no se aplican a pedidos pagados con dos tarjetas o vales de compra.
 
 - **Utm\_source:** se concederá el descuento si la navegación se realiza con la **utm_source** correspondiente a alguno de los valores registrados. Es importante resaltar que el cliente solo puede ingresar una **utm_source** en el checkout.
 - **Utm\_campaign:** se concederá el descuento si la navegación se realiza con la **utm\_campaign** con el valor registrado.
 - **Generar cupón con las UTM arriba:** crea un cupón con las UTM registradas para darle al cliente acceso a esta promoción sin necesidad de las UTM, tan solo con el código del cupón.
 - **Utmi\_cp:** se concederá el descuento si la navegación se realiza con la utmi\_cp con el valor registrado (case sensitive).
 
-<div class = "alert alert-info">
-  <p>En el campo de las UTM, ingrese solo el valor que tendrán las UTM para activar la promoción. No es necesario ingresar <i>?utm_source=</i> dentro del campo.</p>
-</div>
+>ℹ️ En el campo de las UTM, ingrese solo el valor que tendrán las UTM para activar la promoción. No es necesario ingresar <i>?utm_source=</i> dentro del campo.
 
 - **Solo en la primera compra:** solo se concederá el descuento en la primera compra del cliente.
 - **Es un pedido de suscripción**: opción que define que la promoción se aplicará a los pedidos de suscripción. Estas son las condiciones:
diff --git a/docs/tutorials/es/releases-module-beta.md b/docs/tutorials/es/releases-module-beta.md
index 47c6bfca6..1d2ef0ade 100644
--- a/docs/tutorials/es/releases-module-beta.md
+++ b/docs/tutorials/es/releases-module-beta.md
@@ -15,9 +15,7 @@ legacySlug: modulo-de-lanzamientos-beta
 subcategory: 
 ---
 
-<div class = "alert alert-info">
-El módulo <b>Lanzamientos</b> se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan FastStore.
-</div>
+>ℹ️ El módulo **Lanzamientos** se encuentra en la versión Beta, por lo tanto, estamos trabajando para mejorarlo. Esta funcionalidad es válida únicamente para las tiendas que usan FastStore.
 
 La gestión de una operación de _ecommerce_ exige que el _retailer_ haga una serie de actualizaciones y cambios en su tienda que, muchas veces, suelen relacionarse entre sí; por ejemplo, una campaña publicitaria en la cual se deben configurar distintos elementos del _storefront_.
 
@@ -30,9 +28,7 @@ Los principales beneficios para el módulo son:
 - Mayor control al probar y revisar los cambios antes de la publicación.
 - Facilidad para programar o eliminar grupos de cambios.
 
-<div class = "alert alert-info">
-El módulo <b>Lanzamientos</b> debe estar configurado en el CMS para poder usarlo. Obtén más información en <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.
-</div>
+>ℹ️ El módulo **Lanzamientos** debe estar configurado en el CMS para poder usarlo. Obtén más información en [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 Este artículo trata los siguientes temas:
 
@@ -66,9 +62,7 @@ Para crear un lanzamiento, sigue las instrucciones paso a paso a continuación:
 6. Haz clic en `Crear lanzamiento`.
 7. Rellena el campo _Nombre_ con un nombre para el lanzamiento.
 
-  <div class = "alert alert-info">
-En esta etapa, no es obligatorio rellenar los campos <b>Día de publicación</b> y <b>Hora</b>. Esto puede determinarse más adelante, tal como veremos en <a href="https://help.vtex.com/es/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#programar-lanzamientos">Programar lanzamientos</a>.
-</div>
+  >ℹ️ En esta etapa, no es obligatorio rellenar los campos **Día de publicación** y **Hora**. Esto puede determinarse más adelante, tal como veremos en [Programar lanzamientos](https://help.vtex.com/es/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#programar-lanzamientos).
 
 8. Haz clic en `Crear`.
 
@@ -82,9 +76,7 @@ Para crear un lanzamiento, sigue las instrucciones paso a paso a continuación:
 2. Haz clic en el botón `Crear`.
 3. Rellena el campo _Nombre_ con un nombre para el lanzamiento.
 
-  <div class = "alert alert-info">
-En esta etapa, no es obligatorio rellenar los campos Día de publicación y Hora. Esto puede determinarse más adelante, tal como veremos en Programar lanzamientos.
-</div>
+  >ℹ️ En esta etapa, no es obligatorio rellenar los campos Día de publicación y Hora. Esto puede determinarse más adelante, tal como veremos en Programar lanzamientos.
 
 4. Haz clic en `Crear`.
 
@@ -127,9 +119,7 @@ Al crear un lanzamiento, se puede definir o no la fecha de publicación. Existen
 - **Desprogramar:** cancelar la fecha de publicación, lo cual hace que el lanzamiento pase al status `No programado`.
 - **Reprogramar:** definir una fecha nueva para un lanzamiento que ya tenía una fecha determinada.
 
-<div class = "alert alert-info">
-Al programar o reprogramar la publicación de un lanzamiento es posible seleccionar la opción <b>Agregar fecha de finalización</b> para definir un plazo en el que se quitará la publicación del lanzamiento. La fecha de finalización no significa que se <a href="https://help.vtex.com/es/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#e#eliminar-lanzamientos">eliminará el lanzamiento</a>, sino que se archivará y podrá publicarse nuevamente en cualquier momento.
-</div>
+>ℹ️ Al programar o reprogramar la publicación de un lanzamiento es posible seleccionar la opción **Agregar fecha de finalización** para definir un plazo en el que se quitará la publicación del lanzamiento. La fecha de finalización no significa que se [eliminará el lanzamiento](https://help.vtex.com/es/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#e#eliminar-lanzamientos), sino que se archivará y podrá publicarse nuevamente en cualquier momento.
 
 ### Programar
 
diff --git a/docs/tutorials/es/returning-order-items.md b/docs/tutorials/es/returning-order-items.md
index da04fc799..b623c2650 100644
--- a/docs/tutorials/es/returning-order-items.md
+++ b/docs/tutorials/es/returning-order-items.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Los clientes de tu tienda pueden solicitar el cambio o la devolución de ítems de un pedido. De este modo, la funcionalidad **Devolución de ítems** permite retirar ítems de un pedido para que los productos sean devueltos.
 
-<div class = "alert alert-info">
-Consulta el artículo <a href="https://help.vtex.com/es/tutorial/como-devolver-itens-do-pedido-beta--2bSNWwD0g8fcUmuupLao9i">Cómo devolver ítems del pedido (Beta)</a> para saber cómo utilizar la funcionalidad en el Admin V4.
-</div>
+>ℹ️ Consulta el artículo [Cómo devolver ítems del pedido (Beta)](https://help.vtex.com/es/tutorial/como-devolver-itens-do-pedido-beta--2bSNWwD0g8fcUmuupLao9i) para saber cómo utilizar la funcionalidad en el Admin V4.
 
 Para realizar la devolución en el VTEX Admin:
 
diff --git a/docs/tutorials/es/sales-associates-instore-beta.md b/docs/tutorials/es/sales-associates-instore-beta.md
index 56bca92b5..bc4940631 100644
--- a/docs/tutorials/es/sales-associates-instore-beta.md
+++ b/docs/tutorials/es/sales-associates-instore-beta.md
@@ -15,9 +15,7 @@ legacySlug: vendedores-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>Esta funcionalidad se encuentra en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de duda, póngase en contacto con <a href="https://support.vtex.com/hc/pt-br/requests">nuestro Soporte</a>.</p>
-</div>
+>ℹ️ Esta funcionalidad se encuentra en etapa Beta, lo que significa que estamos trabajando para mejorarla. En caso de duda, póngase en contacto con [nuestro Soporte](https://support.vtex.com/hc/pt-br/requests).
 
 **Vendedores** es una de las páginas de **Configuración de la tienda** del Admin VTEX que muestra la lista de vendedores registrados en la aplicación inStore de la tienda. Desde aquí, puedes gestionar la información de los vendedores en todas las cuentas franquicias de tu tienda.
 
@@ -56,9 +54,7 @@ Después de registrado, el vendedor recibirá un email de confirmación y se le
 
 ![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
-<div class ="alert alert-warning">
-<p>Los vendedores registrados en inStore no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.</p> 
-</div>
+>⚠️ Los vendedores registrados en inStore no tienen permiso para acceder al Admin VTEX. Si un vendedor intenta iniciar sesión en el Admin, se eliminará su registro.
 
 ### Campos de registro del vendedor
 
@@ -72,9 +68,7 @@ Después de registrado, el vendedor recibirá un email de confirmación y se le
 
 * **Tienda:** [cuenta franquicia](https://help.vtex.com/es/tutorial/que-es-una-cuenta-franquicia--kWQC6RkFSCUFGgY5gSjdl) en la que el vendedor será registrado. Campo obligatorio.
 
-<div class ="alert alert-info">
-<p>Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en inStore.</p> 
-</div>
+>ℹ️ Los cambios pueden tardar hasta 15 minutos en procesarse y aplicarse en inStore.
 
 ## Buscar vendedor
 
diff --git a/docs/tutorials/es/sales-performance.md b/docs/tutorials/es/sales-performance.md
index b72153d30..8aa5a16d5 100644
--- a/docs/tutorials/es/sales-performance.md
+++ b/docs/tutorials/es/sales-performance.md
@@ -35,9 +35,7 @@ Para asegurarte de que tienes acceso tanto a los últimos datos actualizados com
 
 Estos grupos también son procesados por sistemas diferentes, lo que puede provocar una diferencia entre los datos del OMS y los del Desempeño de las Ventas, aunque nuestro objetivo es presentar una divergencia máxima del 3%.
 
-<div class ="alert alert-warning">
-Por ejemplo, puede que haya diferencias entre las métricas de ingresos y ticket promedio registradas en el OMS y Desempeño de Ventas. Esto se debe a que Desempeño de Ventas considera el valor de los ítems, mientras que el OMS también toma en cuenta descuentos, valor de envío, impuestos y promociones en el pedido, lo que puede aumentar o disminuir el valor final.
-</div>
+>⚠️ Por ejemplo, puede que haya diferencias entre las métricas de ingresos y ticket promedio registradas en el OMS y Desempeño de Ventas. Esto se debe a que Desempeño de Ventas considera el valor de los ítems, mientras que el OMS también toma en cuenta descuentos, valor de envío, impuestos y promociones en el pedido, lo que puede aumentar o disminuir el valor final.
 
 ## Periodo
 
diff --git a/docs/tutorials/es/search-behavior.md b/docs/tutorials/es/search-behavior.md
index 1d8c134cb..b6877407d 100644
--- a/docs/tutorials/es/search-behavior.md
+++ b/docs/tutorials/es/search-behavior.md
@@ -49,9 +49,7 @@ Ejemplo: un cliente desea buscar el término `bola`. Siguiendo la configuración
 * `bora` (cambiar 1 carácter)
 * `obla` (intercambiar 2 caracteres que estén uno al lado del otro)
 
-<div class ="alert alert-info">
-	<p>El <em>fuzzy</em> no considera los espacios en blanco. Esto quiere decir que, por ejemplo, <code>base ball</code> no se corregiría a <code>baseball</code>. Recomendamos usar <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinónimos</a> en estos casos.</p>
-</div>
+>ℹ️ El *fuzzy* no considera los espacios en blanco. Esto quiere decir que, por ejemplo, `base ball` no se corregiría a `baseball`. Recomendamos usar [sinónimos](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) en estos casos.
 
 ### Resultado mínimo
 
@@ -62,9 +60,7 @@ En las búsquedas que contienen varios términos, se aplica la siguiente lógica
 Si no se devuelve la cantidad mínima de resultados con la autocorrección inicial, la búsqueda comienza a incluir resultados más amplios que contengan cualquiera de los términos buscados. Por ejemplo, cuando un usuario busca “zapatilla nike” pero el catálogo no tiene ningún producto con ese nombre, la búsqueda puede mostrar como resultado un producto que contenga solo “zapatilla” en el nombre.
 Si la búsqueda más amplia no devuelve la cantidad de resultados mínima, se repetirá la autocorrección nuevamente en cada uno de los términos.
 
-<div class= "alert alert-warning">
-<p>Las búsquedas que contienen varios términos son más eficientes cuando el cliente ordena los resultados por relevancia, ya que pueden devolver un número mayor de resultados más allá del contexto de búsqueda inicial. En el orden por relevancia también pueden priorizarse ítems relacionados con cada término. Por otro lado, cuando se aplican otros criterios, como precio o más vendidos, el orden de los resultados depende de los valores numéricos y no necesariamente prioriza ítems que contienen más palabras.</p>
-</div>
+>⚠️ Las búsquedas que contienen varios términos son más eficientes cuando el cliente ordena los resultados por relevancia, ya que pueden devolver un número mayor de resultados más allá del contexto de búsqueda inicial. En el orden por relevancia también pueden priorizarse ítems relacionados con cada término. Por otro lado, cuando se aplican otros criterios, como precio o más vendidos, el orden de los resultados depende de los valores numéricos y no necesariamente prioriza ítems que contienen más palabras.
 
 ### Límite de paginación
 
diff --git a/docs/tutorials/es/search-control-fulltextsearchbox.md b/docs/tutorials/es/search-control-fulltextsearchbox.md
index ee133c684..11a397eef 100644
--- a/docs/tutorials/es/search-control-fulltextsearchbox.md
+++ b/docs/tutorials/es/search-control-fulltextsearchbox.md
@@ -15,9 +15,7 @@ legacySlug: controle-de-busca-fulltextsearchbox
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 El control `<vtex.cmc:fullTextSearchBox />`es responsable de generar la caja de búsqueda. Además del campo de búsqueda, el control renderiza un combo para restringir una búsqueda en un departamento. Tenemos abajo un ejemplo del control sin ninguna aplicación de css:
 
diff --git a/docs/tutorials/es/search-navigator-control.md b/docs/tutorials/es/search-navigator-control.md
index 4ad0bb4e0..e6d61fe18 100644
--- a/docs/tutorials/es/search-navigator-control.md
+++ b/docs/tutorials/es/search-navigator-control.md
@@ -15,9 +15,7 @@ legacySlug: control-search-navigator
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 El control `<vtex.cmc:searchNavigator/>` renderiza un menú de filtros relacionados con el resultado de una búsqueda.
 
diff --git a/docs/tutorials/es/search-parameters.md b/docs/tutorials/es/search-parameters.md
index 9138c581f..a4c02d3dc 100644
--- a/docs/tutorials/es/search-parameters.md
+++ b/docs/tutorials/es/search-parameters.md
@@ -15,9 +15,7 @@ legacySlug: parametros-de-busqueda
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atención</strong>: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ **Atención**: VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Al realizar búsquedas en la VTEX, existen algunas posibilidades de urls. Tenemos las urls de Departamentos y Categorías, que son formadas de la siguiente forma:
 
@@ -57,9 +55,7 @@ Donde:
 
 ![](https://images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
 
-<div class = "alert alert-warning">
-  <p><b>Atención:</b> existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.</p>
-</div>
+>⚠️ **Atención:** existen dos formas de configurar colecciones, mediante el CMS o utilizando el módulo Colecciones Beta. Este artículo se refiere a <a href = "https://help.vtex.com/es/tutorial/registrar-una-coleccion-cms--2YBy6P6X0NFRpkD2ZBxF6L">la configuración de colecciones mediante el CMS</a>.
 
 **H:\[IdColeção\]**: Retorna productos de una determinada colección, de acuerdo al ID informado. Este código se informa en la edición de la colección, en **Configurações &gt; Portal &gt; Pasta Portal &gt; Subpasta Coleções:**
 
diff --git a/docs/tutorials/es/searching-for-events-on-audit.md b/docs/tutorials/es/searching-for-events-on-audit.md
index 633d66928..fba8a14f9 100644
--- a/docs/tutorials/es/searching-for-events-on-audit.md
+++ b/docs/tutorials/es/searching-for-events-on-audit.md
@@ -46,9 +46,7 @@ Observa que cada búsqueda que realizas se guarda en la pestaña **Últimas bús
 
 >⚠️ Solo se registran 50 búsquedas en este panel. Si quieres guardar una búsqueda por tiempo indefinido, realízala y añádela a los favoritos de tu navegador.
 
-<div class = "alert alert-info">
-Revisa la <a href="https://help.vtex.com/es/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista completa de eventos de Audit</a>.
-</div>
+>ℹ️ Revisa la [lista completa de eventos de Audit](https://help.vtex.com/es/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## Ejemplos de filtros de búsqueda 
 
@@ -77,7 +75,5 @@ Revisa la <a href="https://help.vtex.com/es/tutorial/events-available-in-audit--
 
 Para ver más ejemplos de filtros que se pueden utilizar, haz clic en la pestaña **Guía.** 
 
-<div class = "alert alert-info">
-En la aplicación Audit, los <a href="https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos del License Manager</a> son identificados por las respectivas claves.
-</div>
+>ℹ️ En la aplicación Audit, los [recursos del License Manager](https://help.vtex.com/es/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) son identificados por las respectivas claves.
 
diff --git a/docs/tutorials/es/seller-portal-creating-a-promotion.md b/docs/tutorials/es/seller-portal-creating-a-promotion.md
index fcdd5b23f..5dcffb446 100644
--- a/docs/tutorials/es/seller-portal-creating-a-promotion.md
+++ b/docs/tutorials/es/seller-portal-creating-a-promotion.md
@@ -27,9 +27,7 @@ Para crear una nueva promoción como seller en el Seller Portal, sigue los pasos
 
 Después, se activará la promoción y se aplicará a tu tienda.
 
-<div class = "alert alert-info">
-Las promociones que puedan aplicarse a los mismos ítems del carrito se comparan por su valor de descuento. A este respecto, el módulo Promociones intenta siempre aplicar la promoción más ventajosa para el comprador.
-</div>
+>ℹ️ Las promociones que puedan aplicarse a los mismos ítems del carrito se comparan por su valor de descuento. A este respecto, el módulo Promociones intenta siempre aplicar la promoción más ventajosa para el comprador.
 
 ## Campos de registro de la promoción
 
diff --git a/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
index d84e11b26..84bb46f42 100644
--- a/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/es/seller-portal-getting-started-for-the-marketplace.md
@@ -60,9 +60,7 @@ La página de **Invitación de Sellers** es donde los operadores del _marketplac
 
 A través del Seller Portal, los _marketplaces_ hospedados en VTEX pueden conectarse con _sellers_ que tienen una cuenta VTEX, _sellers_ hospedados en otras plataformas o _sellers_ que no están alojados en ninguna plataforma. Al aceptar la invitación, el _seller_ elige si desea integrar su cuenta VTEX existente o crear una nueva cuenta para vender en el _marketplace_. 
 
-<div class = "alert alert-info">
-Una vez que el <a href="https://help.vtex.com/es/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#convidar-seller">marketplace invita al seller</a>, se le envía un email con un link para crear una cuenta en el Seller Portal. El link es válido durante siete días. Después de hacer clic en link, el seller tiene seis horas para completar el formulario de registro.
-</div>
+>ℹ️ Una vez que el [marketplace invita al seller](https://help.vtex.com/es/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#convidar-seller), se le envía un email con un link para crear una cuenta en el Seller Portal. El link es válido durante siete días. Después de hacer clic en link, el seller tiene seis horas para completar el formulario de registro.
 
 Si el _seller_ no completa el registro en el plazo previsto, el _marketplace_ debe enviar la invitación de nuevo. Puedes acceder a la página desde el Admin VTEX, en **MARKETPLACE > Sellers > Invitación de sellers**. Debes seleccionar el _seller_ de la lista y hacer clic en el botón **Reenviar invitación**.
 
@@ -77,9 +75,7 @@ Para saber más, consulta los siguientes artículos:
 
 Una vez que el _seller_ acepta la invitación al _marketplace_ y finaliza el registro de su cuenta en el Seller Portal, el siguiente paso es la activación para conectarlo al _marketplace_. Esto hace que el _seller_ pase del status _Invitado_ al status _Activo_, y se incluya en la **Gestión de sellers**. Consulta el paso a paso de cómo activar el _seller_ en [Conectar seller](https://help.vtex.com/es/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#conectar-seller).
 
-<div class = "alert alert-info">
-La etapa de activación del <i>seller</i> pretende dar más seguridad al <i>marketplace</i>, en caso de que se requiera alguna alineación con el <i>seller</i> antes de que empiece a vender en el <i>marketplace</i>.
-</div>
+>ℹ️ La etapa de activación del <i>seller</i> pretende dar más seguridad al <i>marketplace</i>, en caso de que se requiera alguna alineación con el <i>seller</i> antes de que empiece a vender en el <i>marketplace</i>.
 
 #### Acciones por API Rest
 
@@ -102,9 +98,7 @@ Este paso es opcional para el _marketplace_ y dependerá del objetivo de tu mode
 
 Cuando el _marketplace_ opta por compartir el catálogo, lo hace a través de una [política comercial](https://help.vtex.com/es/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). El _seller_ recibe la lista de productos ya registrados en el _marketplace_ para importar y configurar el _stock_ y el precio en el Seller Portal, en **Precios > Catálogo > Productos compartidos**.
 
-<div class = "alert alert-info">
-La creación de una política comercial adicional por parte del operador del marketplace para definir el surtido del catálogo de sellers en el Seller Portal se cobra como un <a href="https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X">contratación de política comercial adicional</a>.
-</div>
+>ℹ️ La creación de una política comercial adicional por parte del operador del marketplace para definir el surtido del catálogo de sellers en el Seller Portal se cobra como un [contratación de política comercial adicional](https://help.vtex.com/es/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X).
 
 #### Compartir productos
 
@@ -122,9 +116,7 @@ En VTEX, un [anuncio](https://help.vtex.com/es/tutorial/anuncios-y-envio-de-prod
 
 Cuando el _seller_ crea un nuevo producto, el _marketplace_ debe revisarlo y aprobar el anuncio del producto siguiendo un proceso llamado [catalogación de anuncios](https://help.vtex.com/es/tutorial/sugerindo-e-aprovando-skus--tutorials_396). La catalogación permite crear nuevos productos y asociar anuncios a SKU o productos ya existentes para ponerlos a la venta.
 
-<div class = "alert alert-info">
-Los anuncios de <a href="https://help.vtex.com/es/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu">productos compartidos</a> entre el marketplace y el seller se aprueban automáticamente sin necesidad de ninguna acción manual.
-</div>
+>ℹ️ Los anuncios de [productos compartidos](https://help.vtex.com/es/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) entre el marketplace y el seller se aprueban automáticamente sin necesidad de ninguna acción manual.
 
 El proceso de catalogación puede ser realizado en el Admin VTEX, en **MARKETPLACE > Sellers > SKU recibidos**, o mediante la API [Match Received SKUs](https://developers.vtex.com/vtex-rest-api/reference/match).
 
diff --git a/docs/tutorials/es/sent-offers-beta.md b/docs/tutorials/es/sent-offers-beta.md
index 48776310a..56500e2a3 100644
--- a/docs/tutorials/es/sent-offers-beta.md
+++ b/docs/tutorials/es/sent-offers-beta.md
@@ -37,9 +37,7 @@ Cuando un seller configura condiciones de precios y stock, prepara su producto p
 
 Este componente realiza una lista de todos los canales integrados, así como del número de anuncios enviados, anuncios en procesamiento y anuncios con error, en cada canal. A través de la lista, los sellers tienen una mayor visibilidad sobre el estado de sus integraciones con canales externos.
 
-<div class = "alert alert-info">
-Anuncios enviados permite hacer un seguimiento de los anuncios con <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Classic</a>, <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Premium</a>, <a href="https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> y <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex">marketplaces VTEX</a>.
-</div>
+>ℹ️ Anuncios enviados permite hacer un seguimiento de los anuncios con [Mercado Libre Classic](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Mercado Libre Premium](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y [marketplaces VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex).
 
 ## Conozca más
 
diff --git a/docs/tutorials/es/sent-offers-buybox-opportunities.md b/docs/tutorials/es/sent-offers-buybox-opportunities.md
index 31c6588c1..d1b8bbc58 100644
--- a/docs/tutorials/es/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/es/sent-offers-buybox-opportunities.md
@@ -28,9 +28,7 @@ Un ejemplo de oportunidad es la función de Catálogo MeLi de Mercado Libre. Lo
 
 Las *Oportunidades* acompañan la presencia de un anuncio en las diferentes páginas del módulo **Gestión de anuncios**, como se muestra en las imágenes de la sección siguiente.
 
-<div class = "alert alert-info">
-<b>Gestión de anuncios</b> permite hacer un seguimiento de los anuncios con <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Classic</a>, <a href="https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Libre Premium</a>, <a href="https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> y <a href="https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex">marketplaces VTEX</a>. Para los conectores que desean integrarse a través de API, existe la <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Guía de integración de Gestión de anuncios</a>.
-</div>
+>ℹ️ **Gestión de anuncios** permite hacer un seguimiento de los anuncios con [Mercado Libre Classic](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Mercado Libre Premium](https://help.vtex.com/es/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Netshoes](https://help.vtex.com/es/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) y [marketplaces VTEX](https://help.vtex.com/es/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-un-marketplace-vtex). Para los conectores que desean integrarse a través de API, existe la [Guía de integración de Gestión de anuncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Lista de anuncios
 
diff --git a/docs/tutorials/es/set-up-mundi-gateway.md b/docs/tutorials/es/set-up-mundi-gateway.md
index 90fe738cd..1ee3980ed 100644
--- a/docs/tutorials/es/set-up-mundi-gateway.md
+++ b/docs/tutorials/es/set-up-mundi-gateway.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 En VTEX es posible la integración con el proveedor de pagos Mundi.
 
-<div class= "alert alert-warning">
-Si también desea utilizar el antifraude de Mundi, la configuración de esta función debe realizarla el propio hub de la empresa. En caso de dudas sobre esta etapa de la operación, consulte con el soporte técnico de Mundi.
-</div>
+>⚠️ Si también desea utilizar el antifraude de Mundi, la configuración de esta función debe realizarla el propio hub de la empresa. En caso de dudas sobre esta etapa de la operación, consulte con el soporte técnico de Mundi.
 
 Para configurar la afiliación Mundi, siga los pasos a continuación:
 
diff --git a/docs/tutorials/es/setting-the-grace-period-for-order-cancellation.md b/docs/tutorials/es/setting-the-grace-period-for-order-cancellation.md
index 13a3c27c9..b20aefc20 100644
--- a/docs/tutorials/es/setting-the-grace-period-for-order-cancellation.md
+++ b/docs/tutorials/es/setting-the-grace-period-for-order-cancellation.md
@@ -21,9 +21,7 @@ Es decir, si el cliente solicita la cancelación antes o durante el período de
 
 Si el cliente solicita la cancelación después de que la carencia haya terminado, la tienda recibe la solicitud, pero la cancelación sólo se realiza si la tienda la aprueba en Gestión de pedidos.
 
-<div class = "alert alert-info">
-De forma predeterminada, el tiempo de carencia para cancelación de pedido es de 30 minutos, pero se puede configurar para satisfacer la demanda de su negocio.
-</div>
+>ℹ️ De forma predeterminada, el tiempo de carencia para cancelación de pedido es de 30 minutos, pero se puede configurar para satisfacer la demanda de su negocio.
 
 Por ejemplo, si su tienda vende alimentos o productos farmacéuticos, que necesitan ser entregados en poco tiempo, puede ser mejor tener una carencia de cancelación menor de 30 minutos.
 
diff --git a/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md b/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md
index 124394481..2320c661a 100644
--- a/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md
+++ b/docs/tutorials/es/setting-up-3ds-2-authentication-flow.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 3D Secure 2.0 (3DS 2) es un flujo de autenticación que aumenta la seguridad en los pagos realizados con tarjetas de crédito y débito, mediante el análisis interno de una gran cantidad de datos presentes en cada transacción.
 
-<div class = "alert alert-warning">
-<p>3DS 2 solo es compatible con algunas afiliaciones de VTEX. Consulte con su proveedor de pago y Admin VTEX si esta funcionalidad está disponible.</p>
-</div>
+>⚠️ 3DS 2 solo es compatible con algunas afiliaciones de VTEX. Consulte con su proveedor de pago y Admin VTEX si esta funcionalidad está disponible.
 
 Antes de iniciar la configuración, es necesario abrir un ticket con el equipo de soporte de VTEX solicitando la activación de 3DS 2 en su tienda. Para más información acceda al [cómo abrir un ticket](https://help.vtex.com/es/tutorial/abrir-tickets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
diff --git a/docs/tutorials/es/setting-up-abandoned-carts.md b/docs/tutorials/es/setting-up-abandoned-carts.md
index 9b1a38a1f..0210216f4 100644
--- a/docs/tutorials/es/setting-up-abandoned-carts.md
+++ b/docs/tutorials/es/setting-up-abandoned-carts.md
@@ -63,9 +63,7 @@ Una vez que se haya creado el nuevo template de email o se hayan utilizado los d
 7. En __Html__, ingrese la información del template de email creado o predeterminado.
 8. Haga clic `Save`. 
 
-<div class = "alert alert-info">
-El campo JSON Data no debe completarse ni sus datos deben usarse en el template de email. Solo contiene información para permitir una vista previa del formato en el que se verán los datos en el email.
-</div>
+>ℹ️ El campo JSON Data no debe completarse ni sus datos deben usarse en el template de email. Solo contiene información para permitir una vista previa del formato en el que se verán los datos en el email.
 
 ![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
 
diff --git a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
index 660f0b4f9..00093e417 100644
--- a/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
+++ b/docs/tutorials/es/setting-up-merchant-id-in-apple-pay.md
@@ -92,9 +92,7 @@ Primero, debe validar cada una de las URL deseadas. Una vez que este paso se com
 
 Finalmente, es necesario importar este archivo al sistema de VTEX a través de Postman - herramienta de gestión de [APIs](https://help.vtex.com/es/tutorial/introduccion-a-las-apis-vtex--3SjAqQ0BeUqu2ge8AiIkmW "APIs").
 
-<div class = "alert alert-warning">
-<strong>Importante:</strong> solo puede hacerse esta validación de un dominio a la vez. Esto significa que si su tienda usa 10 dominios diferentes, el proceso tendrá que repetirse 10 veces.
-</div>
+>⚠️ **Importante:** solo puede hacerse esta validación de un dominio a la vez. Esto significa que si su tienda usa 10 dominios diferentes, el proceso tendrá que repetirse 10 veces.
 
 Verifique las instrucciones:
 
diff --git a/docs/tutorials/es/setting-up-my-account.md b/docs/tutorials/es/setting-up-my-account.md
index ef700a21f..e968e9c2b 100644
--- a/docs/tutorials/es/setting-up-my-account.md
+++ b/docs/tutorials/es/setting-up-my-account.md
@@ -15,9 +15,7 @@ legacySlug: configuración-de-my-account
 subcategory: 1RWR7qSyaREbD5RfgCjdYG
 ---
 
-<div class = "alert alert-info">
-En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
-</div>
+>ℹ️ En [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), los clientes solo pueden acceder a los pedidos de los últimos dos años.
 
 El nuevo [My Account](https://help.vtex.com/es/tutorial/como-funciona-el-my-account--2BQ3GiqhqGJTXsWVuio3Xh) ya está instalado en todas las cuentas VTEX en un <strong>ambiente de prueba</strong>, permitiendo ajustes en la nueva página sin impactos en la experiencia de usuario.
 
diff --git a/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md b/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md
index 76e588dea..90821cc90 100644
--- a/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md
+++ b/docs/tutorials/es/setting-up-price-and-availability-of-skus-by-region.md
@@ -27,9 +27,7 @@ Para regionalizar los precios y la disponibilidad de SKU, debe:
 
 >⚠️ Para [Multilevel Omnichannel Inventory](https://help.vtex.com/es/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#), un marketplace (nivel 1) no puede configurar la exhibición de los precios y la disponibilidad de los productos para los sellers white label (nivel 3) con la funcionalidad de regionalización.
 
-<div class = "alert alert-info">
-La funcionalidad <b>Region</b> funciona tanto para las tiendas Portal CMS Legado como para las tiendas desarrolladas con <a href="https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC">VTEX IO</a>, pero la funcionalidad <a href="https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a> solo es válida para las tiendas VTEX IO. Como resultado, las tiendas con Portal CMS Legado tienen una limitación en la indexación de datos regionalizados y no es posible ordenar correctamente los sellers que atienden la ventana de un RegionId en función de la disponibilidad de ítems.
-</div>
+>ℹ️ La funcionalidad **Region** funciona tanto para las tiendas Portal CMS Legado como para las tiendas desarrolladas con [VTEX IO](https://help.vtex.com/es/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC), pero la funcionalidad [VTEX Intelligent Search](https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) solo es válida para las tiendas VTEX IO. Como resultado, las tiendas con Portal CMS Legado tienen una limitación en la indexación de datos regionalizados y no es posible ordenar correctamente los sellers que atienden la ventana de un RegionId en función de la disponibilidad de ítems.
 
 ## Configurar la entrega en la Cuenta Franquicia/Seller White Label
 
diff --git a/docs/tutorials/es/setting-up-product-comparison.md b/docs/tutorials/es/setting-up-product-comparison.md
index 3d1a5255d..d6c6f6df9 100644
--- a/docs/tutorials/es/setting-up-product-comparison.md
+++ b/docs/tutorials/es/setting-up-product-comparison.md
@@ -24,9 +24,7 @@ Podemos dividir ese recurso en dos partes:
 1. **Página de Comparación**: En la que el usuario visualizará la comparación de los productos seleccionados en la vitrina.
 2. **Vitrina**: Donde el usuario seleccionará los productos que desea comparar.
 
-<div class = "alert alert-warning">
-  <p>Esta funcionalidad no puede utilizarse en la página de inicio del sitio.</p>
-</div>
+>⚠️ Esta funcionalidad no puede utilizarse en la página de inicio del sitio.
 
 ## **Configuración**
 
diff --git a/docs/tutorials/es/setting-up-the-global-category.md b/docs/tutorials/es/setting-up-the-global-category.md
index 6d7d594fd..206e7a72e 100644
--- a/docs/tutorials/es/setting-up-the-global-category.md
+++ b/docs/tutorials/es/setting-up-the-global-category.md
@@ -27,9 +27,7 @@ Adoptamos esa taxonomía porque es ampliamente aplicable a cualquier contexto, y
 
 Se utiliza, por ejemplo, como referencia para la integración de productos con Amazon, Buscapé y marketplaces.
 
-<div class = "alert alert-info">
-El comportamiento predeterminado de nuestra integración con Google Shopping es <strong>no enviar</strong> esta información. Por lo tanto, la mayoría de las tiendas se basan en la propia categorización automática de Google. Si prefiere la categorización manual, <a href="https://help.vtex.com/es/tutorial/abrir-tikets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM" target="_blank">contacte nuestro soporte</a>.
-</div>
+>ℹ️ El comportamiento predeterminado de nuestra integración con Google Shopping es **no enviar** esta información. Por lo tanto, la mayoría de las tiendas se basan en la propia categorización automática de Google. Si prefiere la categorización manual, [contacte nuestro soporte](https://help.vtex.com/es/tutorial/abrir-tikets-para-el-soporte-vtex--16yOEqpO32UQYygSmMSSAM" target="_blank).
 
 ### ¿Cuándo se aplica?
 
diff --git a/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md b/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
index ca6844ee7..ddb7c032d 100644
--- a/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
+++ b/docs/tutorials/es/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
@@ -23,9 +23,7 @@ Un _marketplace_ hospedado en la plataforma VTEX y un _seller_, ya sea un _selle
 - [Marketplace y seller conectados](#marketplace-y-seller-conectados)
 - [Intercambio de emails de clientes](#intercambio-de-emails-de-clientes)
 
-<div class = "alert alert-info">
-Si quieres empezar a vender tus productos en otros <i>marketplaces</i>, usa <a href="https://help.vtex.com/es/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM">Marketplaces e integraciones</a>. Esta funcionalidad facilita la identificación y el contacto entre <i>marketplaces</i> y <i>sellers</i> que operan en el ecosistema VTEX.
-</div>
+>ℹ️ Si quieres empezar a vender tus productos en otros <i>marketplaces</i>, usa [Marketplaces e integraciones](https://help.vtex.com/es/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM). Esta funcionalidad facilita la identificación y el contacto entre <i>marketplaces</i> y <i>sellers</i> que operan en el ecosistema VTEX.
 
 ## Conectar marketplace y seller
 
@@ -43,9 +41,7 @@ Además, para [agregar al seller](https://help.vtex.com/es/tutorial/configurando
 
 El _marketplace_ VTEX se puede integrar tanto con un _seller_ VTEX como con un _seller_ externo, ya sea a través del Admin VTEX o de una API. En ambos casos, los datos que compartirán el _marketplace_ y el _seller_ serán los mismos.
 
-<div class = "alert alert-info">
-Para obtener más información sobre cómo conectar un marketplace VTEX con un seller VTEX o con un seller externo a través del Admin VTEX, consulta el artículo <a href="https://help.vtex.com/es/tutorial/configurando-seller">Agregar seller</a>. Para realizar la integración a través de una API, usa la llamada <a href="https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers">Configure Seller Account</a>. Si se trata de un seller externo, consulta la <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">guía de integración con un <i>seller</i> externo</a>.
-</div>
+>ℹ️ Para obtener más información sobre cómo conectar un marketplace VTEX con un seller VTEX o con un seller externo a través del Admin VTEX, consulta el artículo [Agregar seller](https://help.vtex.com/es/tutorial/configurando-seller). Para realizar la integración a través de una API, usa la llamada [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers). Si se trata de un seller externo, consulta la [guía de integración con un <i>seller</i> externo](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide).
 
 ### Conectar un marketplace VTEX con un seller VTEX
 
@@ -84,9 +80,7 @@ El _marketplace_ puede otorgar al _seller_ un acceso parcial a los emails de su
 - [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers): permite configurar la cuenta del _seller_, ya sea un _seller_ VTEX o externo.
 - [Update Seller by Seller ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#patch-/seller-register/pvt/sellers/-sellerId-): permite actualizar los datos del _seller_, ya sea un _seller_ VTEX o externo.
 
-<div class = "alert alert-info">
-En los pedidos que se realizan a través del <i>marketplace</i>, el <i>seller</i> no puede ver el email del cliente. El cliente establece una relación con el <i>marketplace</i> y, por lo tanto, se necesitaría su consentimiento para compartir sus datos.
-</div>
+>ℹ️ En los pedidos que se realizan a través del <i>marketplace</i>, el <i>seller</i> no puede ver el email del cliente. El cliente establece una relación con el <i>marketplace</i> y, por lo tanto, se necesitaría su consentimiento para compartir sus datos.
 
 ### Más información
 
diff --git a/docs/tutorials/es/shipping-options-beta.md b/docs/tutorials/es/shipping-options-beta.md
index c01bd2c73..ef146d1b3 100644
--- a/docs/tutorials/es/shipping-options-beta.md
+++ b/docs/tutorials/es/shipping-options-beta.md
@@ -33,9 +33,7 @@ Sin embargo, el objetivo de las **Opciones de envío** no es sustituir las [pol
 
 Con las **Opciones de envío**, se separa lo que se cobra a los consumidores por el envío del pedido y el costo de envío para el administrador de la tienda, ya que se pueden configurar diferentes reglas de precios para la tarifa de envío.
 
-<div class = "alert alert-info">
-Para que la selección de las transportadoras para el envío se realice correctamente, se debe ingresar en las plantillas de envío el costo real que las transportadoras cobran por realizar el envío.
-</div>
+>ℹ️ Para que la selección de las transportadoras para el envío se realice correctamente, se debe ingresar en las plantillas de envío el costo real que las transportadoras cobran por realizar el envío.
 
 La funcionalidad **Opciones de envío** permite al administrador de la tienda configurar la tarifa de envío a partir de:
 
@@ -57,9 +55,7 @@ En cada opción de envío, el administrador de la tienda registra un SLA (_Servi
 
 El algoritmo de la plataforma VTEX, [Order Allocation Algorithm](https://help.vtex.com/es/tutorial/order-allocation-algorithm-beta--1zLCAyEdnVe3EsE9Kz88xA), analiza las combinaciones de tiendas y centros de distribución que dan servicio a cada una de las opciones de envío y busca seleccionar las que tienen el menor costo de envío. En el ejemplo, el resultado es una combinación del menor costo de envío el mismo día y otra combinación del menor costo de envío en hasta 5 días laborales.
 
-<div class = "alert alert-info">
-Con las <b>Opciones de envío</b>, existe la garantía de que siempre se presentará al consumidor una opción de envío disponible para la ubicación, lo que antes no ocurría. La única excepción es si no hay un seller ni política de envío que cumpla las condiciones de una opción de envío. En este caso, no se mostrará ninguna opción de envío al consumidor en el checkout.
-</div>
+>ℹ️ Con las **Opciones de envío**, existe la garantía de que siempre se presentará al consumidor una opción de envío disponible para la ubicación, lo que antes no ocurría. La única excepción es si no hay un seller ni política de envío que cumpla las condiciones de una opción de envío. En este caso, no se mostrará ninguna opción de envío al consumidor en el checkout.
 
 ## Acciones y configuración
 
diff --git a/docs/tutorials/es/shipping-simulation.md b/docs/tutorials/es/shipping-simulation.md
index 1cec1ee0c..a949c7da9 100644
--- a/docs/tutorials/es/shipping-simulation.md
+++ b/docs/tutorials/es/shipping-simulation.md
@@ -54,9 +54,7 @@ Si lo desea, puede seleccionar la casilla `Simular ítems individualmente`.
 
  10. Haga clic en el botón `Simular Envío`.  
 
-<div class = "alert alert-info">
-En el resultado de la simulación, las medidas del ítem aparecen en centímetros y gramos, pero el valor real considerado en el Checkout son las unidades de medida registradas en los <a href="https://help.vtex.com/es/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">campos de registro del producto</a> y SKU.
-</div>
+>ℹ️ En el resultado de la simulación, las medidas del ítem aparecen en centímetros y gramos, pero el valor real considerado en el Checkout son las unidades de medida registradas en los [campos de registro del producto](https://help.vtex.com/es/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) y SKU.
 
 ## Detalles de la simulación
 
diff --git a/docs/tutorials/es/sku-bindings.md b/docs/tutorials/es/sku-bindings.md
index 7927af52a..ed83deef0 100644
--- a/docs/tutorials/es/sku-bindings.md
+++ b/docs/tutorials/es/sku-bindings.md
@@ -21,9 +21,7 @@ Cuando el _seller_ envía sus productos al _marketplace_ VTEX, el marketplace [c
 
 Después de que el _marketplace_ cataloga los SKU, ya sea a través de la página **SKU recibidos** o el [VTEX Matcher](https://help.vtex.com/es/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), los vínculos entre los SKU del _seller_ y los SKU del _marketplace_ aparecen en la página **Vínculos de SKU**. Automáticamente, los vínculos pasan a tener el status _Vinculado_.
 
-<div class = "alert alert-info">
-Por defecto, para los <a href="https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa"><i>sellers white label</i></a> no existe vinculación entre sus SKU y los SKU del <i>marketplace</i>.
-</div>
+>ℹ️ Por defecto, para los [<i>sellers white label</i>](https://help.vtex.com/es/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) no existe vinculación entre sus SKU y los SKU del <i>marketplace</i>.
 
 La página **Vínculos de SKU** le permite al _marketplace_ seguir y gestionar la vinculación entre los SKU del _seller_ y los del _marketplace_. Para acceder a la página, en el Admin VTEX, ingresa a **Marketplace > Sellers > Vínculos de SKU**. Aparecerá la siguiente interfaz:
 
@@ -65,17 +63,13 @@ También puedes buscar en la lista filtrando por el status de vinculación. Para
 
 Para regresar a la lista con todos los status de vinculación, haz clic en el botón `Limpiar filtros de búsqueda`. Este botón solo cancela el filtro de status, no los términos ingresados en el recuadro de búsqueda.
 
-<div class = "alert alert-info">
-Si la búsqueda no arroja ningún resultado, verifica la ortografía de lo que escribiste en el recuadro de búsqueda o la combinación de filtros que usaste.
-</div>
+>ℹ️ Si la búsqueda no arroja ningún resultado, verifica la ortografía de lo que escribiste en el recuadro de búsqueda o la combinación de filtros que usaste.
 
 ## Desvincular SKU
 
 Para deshacer un vínculo entre dos SKU, haz clic en la _tilde_ <i class="fas fa-toggle-on"></i> y confirma la opción `Deshacer el vínculo del SKU`. 
 
-<div class = "alert alert-info">
-Al desvincular el SKU del <i>seller</i>, el SKU deja de recibir actualizaciones de precio y <i>stock</i> y no estará disponible en el catálogo del <i>marketplace</i>. El SKU puede revincularse en cualquier momento sin necesidad de volver a catalogar el SKU del <i>seller</i>.
-</div>
+>ℹ️ Al desvincular el SKU del <i>seller</i>, el SKU deja de recibir actualizaciones de precio y <i>stock</i> y no estará disponible en el catálogo del <i>marketplace</i>. El SKU puede revincularse en cualquier momento sin necesidad de volver a catalogar el SKU del <i>seller</i>.
 
 Si deseas restablecer el vínculo entre el SKU del _seller_ y el SKU del _marketplace_, activa nuevamente la _tilde_ <i class="fas fa-toggle-on"></i>, haciendo clic en ella.
 
@@ -109,9 +103,7 @@ Para exportar la lista de vínculos de SKU en formato XLSX, sigue los pasos a co
 
 La plantilla generada se le enviará por email al usuario registrado. El tiempo de exportación dependerá del procesamiento de la plataforma VTEX y del tamaño del archivo.
 
-<div class = "alert alert-info">
-El contenido exportado incluirá la lista de vínculos de SKU al momento de la exportación. Si hay alguna búsqueda o filtro activo, solo se exportarán los vínculos seleccionados.
-</div>
+>ℹ️ El contenido exportado incluirá la lista de vínculos de SKU al momento de la exportación. Si hay alguna búsqueda o filtro activo, solo se exportarán los vínculos seleccionados.
 
 ## Más información
 
diff --git a/docs/tutorials/es/sku-registration-fields.md b/docs/tutorials/es/sku-registration-fields.md
index 5be8d1b41..9a3be721d 100644
--- a/docs/tutorials/es/sku-registration-fields.md
+++ b/docs/tutorials/es/sku-registration-fields.md
@@ -31,9 +31,7 @@ __Código de Referencia__: código de referencia único creado para ayudar con l
 
 __Peso para Flete:__ calculado para flete. Debe registrarse con un valor mayor que cero para que el <a href="https://help.vtex.com/es/tutorial/como-se-realiza-el-prorrateo-del-flete--frequentlyAskedQuestions_155">prorrateo del flete</a> funcione correctamente.
 
-<div class = "alert alert-info">
-<p>El módulo <b>Inventario y envío/Envío</b> no tiene en cuenta las unidades de medida en los campos a continuación. Solo sea consistente con lo que está registrado en los <a href="https://help.vtex.com/es/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">campos de registro de producto</a> y de SKU.</p>
-</div>
+>ℹ️ El módulo **Inventario y envío/Envío** no tiene en cuenta las unidades de medida en los campos a continuación. Solo sea consistente con lo que está registrado en los [campos de registro de producto](https://help.vtex.com/es/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) y de SKU.
 
 __Altura para Flete:__ calculada para flete.
 
diff --git a/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md b/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md
index 10c4b903d..f1550def4 100644
--- a/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md
+++ b/docs/tutorials/es/smartcheckout-customer-information-automatic-fill-in.md
@@ -40,9 +40,7 @@ Los datos del cliente que se usan en el checkout provienen de la información re
    - street
    - receiverName
 
-<div class = "alert alert-warning">
-Si la información de uno o más campos no está completa en el Master Data, SmartCheckout no mostrará ningún dato del cliente de manera automática en la pantalla del Checkout. En este caso, el cliente deberá completar todos los datos de identificación de manera manual en cada compra que realice.  
-</div>
+>⚠️ Si la información de uno o más campos no está completa en el Master Data, SmartCheckout no mostrará ningún dato del cliente de manera automática en la pantalla del Checkout. En este caso, el cliente deberá completar todos los datos de identificación de manera manual en cada compra que realice.
 
 ## Procedimiento de compra con SmartCheckout
 
@@ -53,19 +51,16 @@ El flujo de rellenado automático de los datos del cliente en el Checkout es el
 3. SmartCheckout verifica que el email ingresado pertenezca a un cliente registrado en la tienda.  
 4. Al verificar el email, los campos de identificación del cliente se completan automáticamente con los datos que se recuperan del Master Data durante el Checkout.
 
-<div class = "alert alert-warning">
-Para proteger los datos del cliente, la información de identificación se mostrará parcialmente en la pantalla del checkout (parte de los datos están enmascarados de acuerdo con el estándar <a href="https://help.vtex.com/es/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#">PCI-DSS</a> de seguridad de pagos). Este procedimiento le permite al cliente identificar si sus datos son correctos y elegir entre las distintas direcciones registradas para la entrega, en caso de que corresponda.
-</div>
+>⚠️ Para proteger los datos del cliente, la información de identificación se mostrará parcialmente en la pantalla del checkout (parte de los datos están enmascarados de acuerdo con el estándar [PCI-DSS](https://help.vtex.com/es/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#) de seguridad de pagos). Este procedimiento le permite al cliente identificar si sus datos son correctos y elegir entre las distintas direcciones registradas para la entrega, en caso de que corresponda.
 <ul>
 5. El cliente selecciona los medios de entrega y pago, y termina el pedido de compra.
 </ul>
-<div class = "alert alert-warning">
-Si el cliente elije tarjeta de crédito o débito como medio de pago, se adoptarán los criterios adicionales de seguridad a continuación:
-  <ul>
-    <li>Solicitación del CVV (código de seguridad de la tarjeta) para la validación final y finalización del pedido de compra.</li>
-    <li>Imposibilidad de realizar compras con tarjeta si se utiliza una dirección diferente a la registrada en el perfil del cliente.</li>
-  </ul>
-</div>
+>⚠️ Si el cliente elije tarjeta de crédito o débito como medio de pago, se adoptarán los criterios adicionales de seguridad a continuación:
+>
+> * Solicitación del CVV (código de seguridad de la tarjeta) para la validación final y finalización del pedido de compra.
+>
+> * Imposibilidad de realizar compras con tarjeta si se utiliza una dirección diferente a la registrada en el perfil del cliente.
+>   
 
 Cualquier modificación en los datos registrados, como la dirección o el teléfono, solo se permitirá una vez que el cliente haya [iniciado sesión en la tienda](https://help.vtex.com/es/tutorial/como-meu-cliente-pode-fazer-login-na-minha-loja--3FCNpwbpZe0U4auiI4CC0C). 
 
diff --git a/docs/tutorials/es/smartcheckout-security.md b/docs/tutorials/es/smartcheckout-security.md
index f4737e976..f7e86c7c9 100644
--- a/docs/tutorials/es/smartcheckout-security.md
+++ b/docs/tutorials/es/smartcheckout-security.md
@@ -35,7 +35,6 @@ Esto significa que, al intentar realizar una compra con un email ajeno, el estaf
 
 Además, la forma en la que la información aparece enmascarada en el checkout está certificada por el estándar [PCI-DSS] (https://help.vtex.com/pt/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#) de seguridad de pagos. Según este estándar, no hace falta ocultar los últimos dígitos de una tarjeta. La forma en la que se exhibe la información es suficiente para reconocer el medio de pago, pero no sirve para realizar compras.
 
-<div class = "alert alert-info">
-<p>Con Smartcheckout™ de VTEX, la seguridad está en primer lugar. Siempre que se reconoce un email, todos los datos se completan de manera tal que se garantiza que solo el propietario del email reconocerá su información.</p><p>Al acceder a la tienda a través del dominio restringido <code>myvtex.com</code>, los operadores de la tienda pueden ver los datos no enmascarados en SmartCheckout para realizar pruebas. El acceso a este dominio está restringido a los administradores de la tienda con el debido nivel de acceso y las credenciales correspondientes.</p>
-</div>
+>ℹ️ Con Smartcheckout™ de VTEX, la seguridad está en primer lugar. Siempre que se reconoce un email, todos los datos se completan de manera tal que se garantiza que solo el propietario del email reconocerá su información.
+> Al acceder a la tienda a través del dominio restringido `myvtex.com`, los operadores de la tienda pueden ver los datos no enmascarados en SmartCheckout para realizar pruebas. El acceso a este dominio está restringido a los administradores de la tienda con el debido nivel de acceso y las credenciales correspondientes.
 
diff --git a/docs/tutorials/es/store-overview-beta.md b/docs/tutorials/es/store-overview-beta.md
index ff74cbf1f..2e3b89210 100644
--- a/docs/tutorials/es/store-overview-beta.md
+++ b/docs/tutorials/es/store-overview-beta.md
@@ -36,9 +36,7 @@ En este artículo, presentamos las principales secciones y acciones presentes en
 
 Las métricas de la página incluyen datos sobre los pedidos y la navegación, que se obtienen de distintos sistemas.
 
-<div class ="alert alert-warning">
-Por ejemplo, puede que haya diferencias entre las métricas de ingresos y ticket promedio registradas en el OMS y Desempeño de Ventas. Esto se debe a que Desempeño de Ventas considera el valor de los ítems, mientras que el OMS también toma en cuenta descuentos, valor de envío, impuestos y promociones en el pedido, lo que puede aumentar o disminuir el valor final.
-</div>
+>⚠️ Por ejemplo, puede que haya diferencias entre las métricas de ingresos y ticket promedio registradas en el OMS y Desempeño de Ventas. Esto se debe a que Desempeño de Ventas considera el valor de los ítems, mientras que el OMS también toma en cuenta descuentos, valor de envío, impuestos y promociones en el pedido, lo que puede aumentar o disminuir el valor final.
 
 * **Pedidos e ingresos:** los datos sobre pedidos e ingresos proceden del OMS, el Sistema de Gestión de Pedidos de VTEX, e incluyen los pedidos realizados a través de todos tus canales de venta.
 * **Sesiones:** los datos de navegación proceden del sistema interno de la plataforma que captura las sesiones de los usuarios en el storefront de las tiendas VTEX. Las sesiones están representadas por el conjunto de páginas vistas a las que accede un mismo usuario cuando navega por tu tienda online, sin tener en cuenta marketplaces, aplicaciones, VTEX Sales App y cualquier otro canal de venta.
diff --git a/docs/tutorials/es/telesales-features.md b/docs/tutorials/es/telesales-features.md
index f2be915ea..d40b2d7a5 100644
--- a/docs/tutorials/es/telesales-features.md
+++ b/docs/tutorials/es/telesales-features.md
@@ -36,9 +36,7 @@ La barra de herramientas de televentas es una barra superior que se muestra en e
 
 Para saber cómo utilizar esta función, consulte el tutorial [Barra de herramientas de televentas](https://help.vtex.com/es/tutorial/usando-e-customizando-toolbar-de-televendas--tutorials_5500).
 
-<div class = "alert alert-info">
-Un caso de uso de la funcionalidad de televentas es importar pedidos de otras plataformas al módulo <b>Pedidos</b> de Admin VTEX. Para ello, puedes asociar una <a href="https://help.vtex.com/es/tutorial/crear-una-politica-comercial--563tbcL0TYKEKeOY4IAgAE">política comercial</a> específica con el pago mediante <a href="https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ">pagaré</a> (medio de pago aprobado de forma inmediata y manual por el propio operador).
-  </div>
+>ℹ️ Un caso de uso de la funcionalidad de televentas es importar pedidos de otras plataformas al módulo **Pedidos** de Admin VTEX. Para ello, puedes asociar una [política comercial](https://help.vtex.com/es/tutorial/crear-una-politica-comercial--563tbcL0TYKEKeOY4IAgAE) específica con el pago mediante [pagaré](https://help.vtex.com/es/tutorial/configurar-pagos-con-pagare--5pW7avTwtyQcMu4uiW8quQ) (medio de pago aprobado de forma inmediata y manual por el propio operador).
 
 ### Mi cuenta
 
diff --git a/docs/tutorials/es/transactional-emails-for-subscription-orders.md b/docs/tutorials/es/transactional-emails-for-subscription-orders.md
index 0c3e9887c..1c01a4525 100644
--- a/docs/tutorials/es/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/es/transactional-emails-for-subscription-orders.md
@@ -28,9 +28,7 @@ También puede crear su propia plantilla de correo electrónico. Entienda mejor
 
 ## Cómo su cliente acompaña sus pedidos de suscripción
 
-<div class = "alert alert-info">
-En <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>, los clientes solo pueden acceder a los pedidos de los últimos dos años.
-</div>
+>ℹ️ En [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), los clientes solo pueden acceder a los pedidos de los últimos dos años.
 
 Cada acción, que ocurre dentro del flujo de pedidos de Suscripción, contiene un gatillo que dispara un correo electrónico notificando a su cliente.  Una vez activada la suscripción, el cliente recibirá correos electrónicos con detalles del status de cada pedido de suscripción cada vez que realice una acción. 
 
diff --git a/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
index bb44dd4d4..fcb5b49a3 100644
--- a/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/es/troubleshooting-errors-in-subscription-orders.md
@@ -15,9 +15,7 @@ legacySlug: como-resolver-pedidos-de-suscripcion-con-errores
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
-<div class = "alert alert-info">
-Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Mi Cuenta</a>.
-</div>
+>ℹ️ Solo puedes acceder a la información de los pedidos creados en los últimos años. Este periodo también se aplica a los pedidos de los clientes a través de [Mi Cuenta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 Es posible identificar y gestionar errores en pedidos de suscripción a través del módulo **Suscripciones** > **Dashboards** > **Pedidos de suscripción** en el Admin.
 
diff --git a/docs/tutorials/es/troubleshooting-price-divergence-errors-in-marketplace-orders.md b/docs/tutorials/es/troubleshooting-price-divergence-errors-in-marketplace-orders.md
index 3b5e6073c..560b86305 100644
--- a/docs/tutorials/es/troubleshooting-price-divergence-errors-in-marketplace-orders.md
+++ b/docs/tutorials/es/troubleshooting-price-divergence-errors-in-marketplace-orders.md
@@ -23,9 +23,7 @@ Cuando el precio establecido por un seller es diferente del precio ofrecido por
 
 Para activar el flujo de autorización de pedidos para conectores nativos, debe [configurar una regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe). Solo los usuarios con el rol de acceso OMS Full o Admin Super (Owner) pueden hacer esto.
 
-<div class = "alert alert-info">
-Una vez que haya <a href="https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configurado la regla de Divergencia de precios</a>, se aplicará a todos los mercados en los que sea seller.
-</div>
+>ℹ️ Una vez que haya [configurado la regla de Divergencia de precios](https://help.vtex.com/es/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), se aplicará a todos los mercados en los que sea seller.
 
 Para los VTEX marketplaces, los marketplaces externos y los conectores certificados (partners), siempre que no se haya creado la regla de Divergencia de precios, los pedidos con error de divergencia de valores se aprueban automáticamente.
 
diff --git a/docs/tutorials/es/understanding-b2b-orders.md b/docs/tutorials/es/understanding-b2b-orders.md
index 3f04e8b27..dadc5f28a 100644
--- a/docs/tutorials/es/understanding-b2b-orders.md
+++ b/docs/tutorials/es/understanding-b2b-orders.md
@@ -27,10 +27,9 @@ Esa experiencia de autoservicio es posible gracias a una integración vía API c
 - **ERP order number:** número de identificación del pedido en el ERP de la tienda.
 - **My order:** número de identificación asociado al cliente que efectuó la compra.
 
-<div class = "alert alert-warning">
-  <p>Esta app solo está disponible para las tiendas desarrolladas con 
-    <a href="https://vtex.com/br-pt/store-framework/">VTEX IO</a>.</p><p>Antes de continuar, necesita <a href = "https://developers.vtex.com/vtex-developer-docs/docs/querying-b2b-order-statuses">instalar y configurar Pedidos B2B</a> en su tienda.</p>
-</div>
+>⚠️ Esta app solo está disponible para las tiendas desarrolladas con 
+>     [VTEX IO](https://vtex.com/br-pt/store-framework/).
+> Antes de continuar, necesita <a href = "https://developers.vtex.com/vtex-developer-docs/docs/querying-b2b-order-statuses">instalar y configurar Pedidos B2B</a> en su tienda.
 
 ## Contexto
 
diff --git a/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md b/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md
index 10b03de33..54e40086f 100644
--- a/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md
+++ b/docs/tutorials/es/visao-geral-da-estrutura-do-catalogo.md
@@ -23,9 +23,7 @@ Un ejemplo de la estructura de catálogo sería el siguiente:
 
 ![img como funciona o catalogo](https://images.contentful.com/alneenqid6w5/3AXUNSkDagO06cKmMsq6w4/5e80021d54e3fa58f9b0c6a261e1f407/img_como_funciona_o_catalogo.png)
 
-<div class = "alert alert-warning">
-No es necesario que su árbol de categorías tenga tres niveles. La jerarquía que se muestra arriba es sólo un ejemplo. La cantidad de niveles de categorías a ser creados depende mucho del sector de actuación de cada tienda.
-</div>
+>⚠️ No es necesario que su árbol de categorías tenga tres niveles. La jerarquía que se muestra arriba es sólo un ejemplo. La cantidad de niveles de categorías a ser creados depende mucho del sector de actuación de cada tienda.
 
 Después de crear su tienda y registrar sus productos, usted tendrá una visión más concreta y organizada de lo que leyó aquí.
 
diff --git a/docs/tutorials/es/vtex-ad-network-beta.md b/docs/tutorials/es/vtex-ad-network-beta.md
index bf58ce5d0..a10a85ec8 100644
--- a/docs/tutorials/es/vtex-ad-network-beta.md
+++ b/docs/tutorials/es/vtex-ad-network-beta.md
@@ -15,9 +15,7 @@ legacySlug: vtex-ad-network-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ VTEX Ad Network se encuentra en fase beta, lo que significa que estamos trabajando para mejorarlo. Si ya eres cliente de VTEX y deseas adoptar esta funcionalidad para tu negocio, por favor, póngate en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Si aún no es cliente pero estás interesado(a) en esta solución, por favor, completa el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 **VTEX Ad Network** conecta a retailers VTEX con marcas interesadas en anunciar sus productos. Con esta conexión, anunciantes y retailers VTEX pueden impulsar su negocio:
 
diff --git a/docs/tutorials/es/vtex-admin-start-here.md b/docs/tutorials/es/vtex-admin-start-here.md
index 5e903dee0..c94d08737 100644
--- a/docs/tutorials/es/vtex-admin-start-here.md
+++ b/docs/tutorials/es/vtex-admin-start-here.md
@@ -89,9 +89,7 @@ Tipo de feedback (marca una o varias casillas):
 
 **Agregar captura de pantalla para ayudarnos a comprender mejor tu opinión:** campo opcional para adjuntar capturas de pantalla u otros documentos que faciliten la comprensión.
 
-<div class = "alert alert-info">
-Este proceso de feedback no debe utilizarse para abrir un ticket o solicitud de soporte técnico en VTEX.
-</div>
+>ℹ️ Este proceso de feedback no debe utilizarse para abrir un ticket o solicitud de soporte técnico en VTEX.
 
 ### Configuración de la cuenta y del usuario
 
diff --git a/docs/tutorials/es/vtex-do-interface.md b/docs/tutorials/es/vtex-do-interface.md
index 1e455b4df..5ee4f45a8 100644
--- a/docs/tutorials/es/vtex-do-interface.md
+++ b/docs/tutorials/es/vtex-do-interface.md
@@ -19,9 +19,7 @@ VTEX DO es un gestor de tareas creadas automáticamente por el Admin VTEX para q
 
 ![VTEX Do overview ES](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/220b438c30b05a78d3932e097fefc42b/VTEX_Do_overview_ES.gif)
 
-<div class = "alert alert-info">
-Solo los usuarios con el perfil de acceso <a href = "https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> pueden realizar tareas a través de VTEX DO.
-</div>
+>ℹ️ Solo los usuarios con el perfil de acceso <a href = "https://help.vtex.com/es/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> pueden realizar tareas a través de VTEX DO.
 
 Las tareas aparecen en dos pestañas:
 - **Todas:** todas las tareas vinculadas a los pedidos de la cuenta de la tienda.
diff --git a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
index b0b9bf312..0eff0d6bd 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-fulfillment.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-fulfillment
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Si tienes interés en implementarla en tu negocio, rellena nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> indicando en el campo <code>Comentarios</code> el nombre del producto deseado.
-</div>
+>ℹ️ Si tienes interés en implementarla en tu negocio, rellena nuestro [formulario](https://vtex.com/co-es/contacto/) indicando en el campo `Comentarios` el nombre del producto deseado.
 
 - [Ingreso a la aplicación](#ingreso-a-la-aplicacion)
     - [Página de inicio](#pagina-de-inicio)
@@ -90,9 +88,7 @@ Al ingresar, encontrarás pedidos que están listos para preparación, organizad
 
 Los pedidos en color rojo son aquellos que llevan mucho tiempo sin ser gestionados y el verde representa aquellos más recientes.
 
-<div class = "alert alert-info">
-Las hojas de trabajo permitirán combinar varios pedidos, de modo que todos los ítems puedan ser alistados.
-</div>
+>ℹ️ Las hojas de trabajo permitirán combinar varios pedidos, de modo que todos los ítems puedan ser alistados.
 
 Elige los pedidos que deseas gestionar y haz clic en la opción  **Empezar a alistar.** En ese momento el sistema crea las hojas de trabajo, con su respectivo número de identificación, que estarán compuestas por los ítems de los pedidos seleccionados.
 
@@ -346,9 +342,7 @@ La estrategia de alistamiento está estructurada por olas, e incluye:
 - Tags de hojas de trabajo.
 - Activar códigos EAN dinámicos.
 
-<div class = "alert alert-info">
-Alistamiento por olas significa que a medida que van llegando los pedidos estos pueden alistarse.
-</div>
+>ℹ️ Alistamiento por olas significa que a medida que van llegando los pedidos estos pueden alistarse.
 
 ### Cambios en los pedidos
 
@@ -393,13 +387,9 @@ Existen tres tipos: precio, peso y cantidad. La configuración se compone de:
 - **Decimales:** cantidad de decimales que soporta.
 - **Prueba:** permite verificar que la configuración esté correcta.
 
-<div class = "alert alert-info">
-Puedes seleccionar los tres tipos de configuraciones para la tienda.
-</div>
+>ℹ️ Puedes seleccionar los tres tipos de configuraciones para la tienda.
 
-<div class = "alert alert-info">
-Si quieres eliminar un tipo puedes hacerlo dentro del campo haciendo clic sobre la X que lo acompaña.
-</div>
+>ℹ️ Si quieres eliminar un tipo puedes hacerlo dentro del campo haciendo clic sobre la X que lo acompaña.
 
 >❗ EAN dinámico es un código que se genera con el peso del producto para calcular el precio.
 
@@ -460,9 +450,7 @@ Para la gestión del usuario alistador, es importante la asignación de instalac
 
 Los alistadores pueden vincularse a una o varias instalaciones.
 
-<div class = "alert alert-info">
-Instalación: es el lugar físico donde existen alistadores recolectando productos.
-</div>
+>ℹ️ Instalación: es el lugar físico donde existen alistadores recolectando productos.
 
 ### Configuración de catálogo
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-insights.md b/docs/tutorials/es/vtex-pick-and-pack-insights.md
index d7c1d9859..6c640d352 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-insights.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-insights.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-analisis
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
-</div>
+>ℹ️ Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro [formulario](https://vtex.com/co-es/contacto/) apontaby introduciendo el nombre del producto en el campo `Comentarios`.
 
 **Análisis** es una página del Admin VTEX que muestra información sobre el desempeño de tu tienda en relación con VTEX Pick and Pack.
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-last-mile.md b/docs/tutorials/es/vtex-pick-and-pack-last-mile.md
index 3f977efd6..f9224e958 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-last-mile.md
@@ -17,7 +17,5 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 
 <div class="alert alert-warning" role="alert">Contenido bajo traducción.</div>
 
-<div class = "alert alert-info">
-Si tienes interés en implementarla en tu negocio, rellena nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> indicando en el campo <code>Comentarios</code> el nombre del producto deseado.
-</div>
+>ℹ️ Si tienes interés en implementarla en tu negocio, rellena nuestro [formulario](https://vtex.com/co-es/contacto/) indicando en el campo `Comentarios` el nombre del producto deseado.
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-mobile.md b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
index e593b799e..a55a4768a 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-mobile.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-mobile
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-<p>Si ya es cliente de VTEX y desea adoptar esta funcionalidad para su negocio, por favor, póngase en contacto con el <a href="https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Soporte Comercial</a>. Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el <a href="https://vtex.com/co-es/contacto/">formulario de contacto</a>.</p>
-</div>
+>ℹ️ Si ya es cliente de VTEX y desea adoptar esta funcionalidad para su negocio, por favor, póngase en contacto con el [Soporte Comercial](https://help.vtex.com/es/tracks/soporte-en-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Pueden aplicarse tarifas adicionales. Si aún no es cliente pero está interesado en esta solución, por favor, complete el [formulario de contacto](https://vtex.com/co-es/contacto/).
 
 La aplicación móvil de [VTEX Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) ayuda al alistador (profesional responsable de seleccionar y empacar los ítems en la instalación) en la preparación de los pedidos, desde el alistamiento de los ítems hasta el envío. Esto hace que el flujo de alistamiento y envío de los pedidos de la tienda sea más organizado y fluido.
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-orders.md b/docs/tutorials/es/vtex-pick-and-pack-orders.md
index b20acb442..6a858564e 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-orders.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-orders.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-pedidos
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
-</div>
+>ℹ️ Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro [formulario](https://vtex.com/co-es/contacto/) apontaby introduciendo el nombre del producto en el campo `Comentarios`.
 
 **Pedidos** es una página del Admin VTEX que muestra información sobre los pedidos realizados y gestionados por [VTEX Pick and Pack](https://help.vtex.com/es/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU).
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-settings.md b/docs/tutorials/es/vtex-pick-and-pack-settings.md
index 289a771b0..1ac2fe754 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-settings.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-settings.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-configuracion
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
-</div>
+>ℹ️ Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro [formulario](https://vtex.com/co-es/contacto/) apontaby introduciendo el nombre del producto en el campo `Comentarios`.
 
 __Configuración__ es una página del Admin VTEX donde puedes realizar los ajustes de VTEX Pick and Pack para tu tienda. Los ajustes se distribuyen en las siguientes secciones:
 
@@ -40,9 +38,7 @@ En esta sección se encuentran los ajustes relativos a la etapa de alistamiento,
 
 En esta sección puedes definir el tipo de estrategia de alistamiento que deseas que realicen los alistadores.
 
-<div class = "alert alert-info">
-  Actualmente solo está disponible la estrategia <strong>Alistamiento por olas</strong>.
-</div>
+>ℹ️ Actualmente solo está disponible la estrategia **Alistamiento por olas**.
 
 #### Cambios en el pedido
 
@@ -252,9 +248,7 @@ Puedes agregar ID de SKU y EAN de tus productos masivamente, a través de un arc
 
 También puedes indexar el catálogo para actualizar la lista de productos. Para hacerlo, haz clic en `Indexar catálogo` y después en `Continuar`.
 
-<div class = "alert alert-danger">
-  La indexación del catálogo borrará y recreará todo su contenido, lo que significa que puedes perder todos tus códigos EAN y SKU personalizados.
-</div>
+>❗ La indexación del catálogo borrará y recreará todo su contenido, lo que significa que puedes perder todos tus códigos EAN y SKU personalizados.
 
 ## Instalaciones
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack-worksheets.md b/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
index 5d2dfda98..e6dde6fdb 100644
--- a/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
+++ b/docs/tutorials/es/vtex-pick-and-pack-worksheets.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-hojas-de-trabajo
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> apontaby introduciendo el nombre del producto en el campo <code>Comentarios</code>.
-</div>
+>ℹ️ Esta función se encuentra en fase beta cerrada, por lo que sólo los clientes seleccionados pueden acceder a ella ahora. Si desea implementarla en el futuro, rellene nuestro [formulario](https://vtex.com/co-es/contacto/) apontaby introduciendo el nombre del producto en el campo `Comentarios`.
 
 **Hojas de trabajo** es una sección del Admin que gestiona, en tiempo real, las hojas de trabajo que utilizan los alistadores para agrupar y alistar los ítems de cada pedido. El alistador puede agrupar tantos pedidos como desee en cada hoja de trabajo. 
 
diff --git a/docs/tutorials/es/vtex-pick-and-pack.md b/docs/tutorials/es/vtex-pick-and-pack.md
index 08fd64744..54c6bf503 100644
--- a/docs/tutorials/es/vtex-pick-and-pack.md
+++ b/docs/tutorials/es/vtex-pick-and-pack.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Si tienes interés en implementarla en tu negocio, rellena nuestro <a href="https://vtex.com/co-es/contacto/">formulario</a> indicando en el campo <code>Comentarios</code> el nombre del producto deseado.
-</div>
+>ℹ️ Si tienes interés en implementarla en tu negocio, rellena nuestro [formulario](https://vtex.com/co-es/contacto/) indicando en el campo `Comentarios` el nombre del producto deseado.
 
 **VTEX Pick and Pack** es la solución que permite a los comerciantes gestionar la recolección, el empaquetado y la entrega de pedidos desde tiendas físicas y almacenes a las direcciones de los clientes o [puntos de recogida](https://help.vtex.com/es/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). Toda la gestión se realiza en un único lugar, lo que proporciona visibilidad y control a los comerciantes durante todo el proceso de fulfillment.
 
@@ -42,7 +40,5 @@ Con **VTEX Pick and Pack**, los comerciantes también pueden obtener datos y an
 - **[Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr):** aplicación del Admin que permite al operador de la tienda dar instrucciones a los entregadores sobre la recogida y entrega de pedidos en la dirección de los clientes o en los puntos de recogida. Incluye la optimización de rutas y la prueba de recogida y entrega, lo que significa que el entregador puede cargar una firma del cliente, una foto o un comentario que confirme que se ha realizado la entrega.
 - **Aplicaciones móviles:** aplicaciones para dispositivos móviles destinadas exclusivamente a los entregadores, para que puedan realizar sus actividades sin necesidad de acceder al Admin de la tienda.
 
-<div class = "alert alert-info">
-Las aplicaciones <b>Fufillment</b> y <b>Last Mile</b> para entregadores solo están disponibles para dispositivos Android.
-</div>
+>ℹ️ Las aplicaciones **Fufillment** y **Last Mile** para entregadores solo están disponibles para dispositivos Android.
 
diff --git a/docs/tutorials/es/web-page-performance.md b/docs/tutorials/es/web-page-performance.md
index 3c91d137b..44b1e6626 100644
--- a/docs/tutorials/es/web-page-performance.md
+++ b/docs/tutorials/es/web-page-performance.md
@@ -15,9 +15,7 @@ legacySlug: rendimiento-de-paginas-web
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class = "alert alert-info">
-Esta página solo está disponible para las tiendas que operan con el <a href="https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">nuevo Admin VTEX</a>. Para acceder a esta página y formar parte de una nueva experiencia, únete al <a href="https://content.vtex.com/participe-do-programa-beta-es/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> del nuevo Admin VTEX.
-</div>
+>ℹ️ Esta página solo está disponible para las tiendas que operan con el [nuevo Admin VTEX](https://help.vtex.com/es/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa). Para acceder a esta página y formar parte de una nueva experiencia, únete al [programa Beta](https://content.vtex.com/participe-do-programa-beta-es/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta) del nuevo Admin VTEX.
 
 [PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about) es una herramienta desarrollada por Google para generar informes de rendimiento de una página, tanto en dispositivos móviles como de escritorio, y brinda sugerencias sobre cómo se podría mejorar. Utiliza las [Métricas web principales de Google](https://web.dev/vitals/#core-web-vitals) para evaluar el rendimiento _online_. 
 
@@ -46,9 +44,7 @@ Las métricas de rendimiento se pueden medir con dos tipos de datos:
 
 Ten en cuenta que no deberías comparar los resultados de los dos tipos de datos. No son comparables porque provienen de distintas fuentes y cumplen distintos propósitos. Obtén más información sobre cómo se puede aplicar cada tipo de dato en el documento de Google [Cómo se miden las métricas](https://web.dev/user-centric-performance-metrics/#how-metrics-are-measured).
 
-<div class = "alert alert-info">
-  Para asegurarte de que tu sitio web alcance el objetivo recomendado para todas las métricas, PageSpeed Insights mide la actividad del percentil 75 de las cargas de la página, dividida entre los dispositivos móviles y de escritorio.
-</div>
+>ℹ️ Para asegurarte de que tu sitio web alcance el objetivo recomendado para todas las métricas, PageSpeed Insights mide la actividad del percentil 75 de las cargas de la página, dividida entre los dispositivos móviles y de escritorio.
 
 ### Cómo usar los datos de campo y de laboratorio para mejorar las Métricas web principales
 
@@ -169,9 +165,7 @@ La sección Rendimiento de Rendimiento de las páginas web incluye una puntuaci
 * **Necesita mejorar:** de 50 a 90. El código de color es naranja.
 * **Mala**: por debajo de 50. El código de color es rojo.
 
-<div class = "alert alert-warning">
-Ten en cuenta que el rendimiento varía mucho entre las tiendas y depende de cómo se creó la arquitectura del storefront. Los storefronts complejos, con códigos externos y funcionalidades, suelen tener un rendimiento con puntuaciones bajas. Para las tiendas creadas en VTEX IO, consulta <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-debugging-performance-issues">VTEX IO: Debugging Performance Issues (Depuración de problemas de rendimiento)</a>. Para las tiendas que usan <a href="https://www.faststore.dev/">FastStore</a>, hay un <a href="https://www.faststore.dev/releases/2022/04/22/webops">informe automático de Lighthouse para desplegar vistas previas</a>.
-</div>
+>⚠️ Ten en cuenta que el rendimiento varía mucho entre las tiendas y depende de cómo se creó la arquitectura del storefront. Los storefronts complejos, con códigos externos y funcionalidades, suelen tener un rendimiento con puntuaciones bajas. Para las tiendas creadas en VTEX IO, consulta [VTEX IO: Debugging Performance Issues (Depuración de problemas de rendimiento)](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-debugging-performance-issues). Para las tiendas que usan [FastStore](https://www.faststore.dev/), hay un [informe automático de Lighthouse para desplegar vistas previas](https://www.faststore.dev/releases/2022/04/22/webops).
 
 Debajo de la puntuación verás cada puntuación individual que se logró a través de un listado de Métricas web principales, junto con un código de color que indica su límite. Puedes actualizar la puntuación manualmente haciendo clic en el ícono de actualizar <i class='fa fa-refresh'></i>.
 
diff --git a/docs/tutorials/es/what-are-layouts.md b/docs/tutorials/es/what-are-layouts.md
index d19fc2c7f..a204e20e8 100644
--- a/docs/tutorials/es/what-are-layouts.md
+++ b/docs/tutorials/es/what-are-layouts.md
@@ -19,10 +19,10 @@ Los __layouts__ son los responsables de determinar qué [placeholders](/es/tutor
 
 Esto se hace primero a partir de la configuración del placeholder, que va a decir qué tipo es utilizado y el archivo que va a llenarlo. Después, para que el layout se sea funcional, debe estar vinculado a un [template](/es/tutorial/que-son-templates). Así, el código de la página en la que se mostrará el placeholder va a saber exactamente de dónde viene la información.
 
-<div class = "alert alert-warning">
-<strong>Importante:</strong><br>
-Para funcionar, cada layout debe estar vinculado a un solo template.
-</div>
+>⚠️ **Importante:**
+>
+> 
+> Para funcionar, cada layout debe estar vinculado a un solo template.
 
 ### Artículos relacionados
 - [¿Qué es el CMS?](/es/faq/que-es-el-cms)
diff --git a/docs/tutorials/es/what-is-a-service.md b/docs/tutorials/es/what-is-a-service.md
index 330a35e97..3b7b6ba70 100644
--- a/docs/tutorials/es/what-is-a-service.md
+++ b/docs/tutorials/es/what-is-a-service.md
@@ -17,9 +17,8 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Un servicio es un ítem, opcional y con coste, que puede venir acompañando un producto. Se utiliza para asignar un valor, a menudo emocional, pero también de un adicional de servicio propiamente dicho a un SKU. Por ejemplo, una embalaje de regalo, una cinta diferenciada, una tarjeta de regalo o una instalación de producto.
 
-<div class = "alert alert-warning">>
-Es importante recordar que un servicio siempre se cobra. Sin embargo, VTEX no controla el stock de un servicio. Esta es una función del marketplace o del seller.
-</div>
+>⚠️ >
+> Es importante recordar que un servicio siempre se cobra. Sin embargo, VTEX no controla el stock de un servicio. Esta es una función del marketplace o del seller.
 
 Si su producto comprado es una Camisa de la Selección Brasileña, el nombre de su Servicio puede ser __Embalaje de Regalo__, y ser exhibido durante el flujo de pedido en la pantalla que usted elija: producto, carrito o servicio.
 
diff --git a/docs/tutorials/es/what-is-an-attachment.md b/docs/tutorials/es/what-is-an-attachment.md
index c27fe5886..efc738b36 100644
--- a/docs/tutorials/es/what-is-an-attachment.md
+++ b/docs/tutorials/es/what-is-an-attachment.md
@@ -17,9 +17,7 @@ subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 
 Un anexo es la personalización, opcional y sin costo, de un producto. Se utiliza para agregar una información a un SKU. Esta información puede ser relacionada con un [servicio](/es/tutorial/que-es-un-servicio) o al propio artículo comprado.
 
-<div class = "alert alert-warning">
-VTEX no controla el inventario de un anexo. Esta esa uns función del marketplace o del seller.
-</div>
+>⚠️ VTEX no controla el inventario de un anexo. Esta esa uns función del marketplace o del seller.
 
 Si su artículo comprado es una Camisa de la Selección Brasileña, el nombre de su Anexo puede ser __Personalización__, y sus llaves:
 
diff --git a/docs/tutorials/es/what-is-order-configuration.md b/docs/tutorials/es/what-is-order-configuration.md
index 79f214150..d02326593 100644
--- a/docs/tutorials/es/what-is-order-configuration.md
+++ b/docs/tutorials/es/what-is-order-configuration.md
@@ -33,7 +33,5 @@ Una vez instalada, la configuración de uso de Order Configuration se establece
 Por API, usted debe asociar una [tabla de precios](https://help.vtex.com/es/tracks/prices-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) con cada escenario, creando una correlación entre ambos. De esta manera, cuando el usuario configure sus condiciones de compra, recibirá los precios que se refieren a esa regla.
 
 Si el usuario configura un escenario que no tiene asociada ninguna tabla de precios, se utilizará una tabla de precios predeterminada.
-<div class = "alert alert-info">
-  <p>Es importante tener en cuenta que el usuario necesita estar conectado para utilizar Order Configuration y poder ver los diferentes precios basados en su configuración</p>
-</div>
+>ℹ️ Es importante tener en cuenta que el usuario necesita estar conectado para utilizar Order Configuration y poder ver los diferentes precios basados en su configuración
 
diff --git a/docs/tutorials/es/what-is-the-difference-between-unbinding-and-removing-seller-sku.md b/docs/tutorials/es/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
index 2da90338e..035e3e769 100644
--- a/docs/tutorials/es/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
+++ b/docs/tutorials/es/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
@@ -19,9 +19,7 @@ Todos los productos que llegan del seller al marketplace pasan por el módulo [S
 
 Al [desvincular un SKU de seller](https://help.vtex.com/es/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX#desvincular-sku), éste dejará de exhibirse como disponible en el marketplace. El SKU estará desvinculado del catálogo del marketplace, y así no recibirá más ninguna actualización, como precio y stock del seller.
 
-<div class = "alert alert-info">
-Un SKU desvinculado no retorna a la hilera de aprobación <b>SKU recibidos</b>, pues ya existe en el catálogo del marketplace.
-</div>
+>ℹ️ Un SKU desvinculado no retorna a la hilera de aprobación **SKU recibidos**, pues ya existe en el catálogo del marketplace.
 
 Si lo que usted desea es retirar el SKU, usted debe [remover el SKU de seller](https://help.vtex.com/es/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX#remover). Al remover el SKU, él deja de formar parte del catálogo del marketplace. El SKU removido sólo volverá a formar parte del catálogo si el seller reenvía el SKU al **SKU recibidos**.
 
diff --git a/docs/tutorials/es/what-is-the-sponsor-user.md b/docs/tutorials/es/what-is-the-sponsor-user.md
index 5d6892241..07ec3844a 100644
--- a/docs/tutorials/es/what-is-the-sponsor-user.md
+++ b/docs/tutorials/es/what-is-the-sponsor-user.md
@@ -17,9 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 Cada cuenta de VTEX tiene un único usuario titular que es el único que tiene acceso completo a todas las secciones del Admin, incluidas las acciones críticas de mantenimiento y autorización. 
 
-<div class = "alert alert-warning">
-El usuario titular no es el mismo que el <b>Owner (Admin Super)</b>. El <b>Owner (Admin Super)</b> es un perfil de acceso del License Manager que define los permisos que se conceden a un determinado usuario de tu tienda, e incluso puede asignarse a varios usuarios.
-</div>
+>⚠️ El usuario titular no es el mismo que el **Owner (Admin Super)**. El **Owner (Admin Super)** es un perfil de acceso del License Manager que define los permisos que se conceden a un determinado usuario de tu tienda, e incluso puede asignarse a varios usuarios.
 
 La página de gestión del titular le permite identificar al usuario titular actual, transferir la propiedad de la tienda y ver el registro de actividad asociado al usuario titular. Para acceder a esta página navegue a **Configuración de la cuenta** > **Gestión de la cuenta** > **Cuenta**, desplácese hacia abajo hasta la sección de «Contacto» y haga clic en el enlace `Gestión de titulares`.
 
diff --git a/docs/tutorials/es/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md b/docs/tutorials/es/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
index 66beb0f6e..4f51f7eeb 100644
--- a/docs/tutorials/es/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
+++ b/docs/tutorials/es/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
@@ -15,9 +15,7 @@ legacySlug: que-hacer-cuando-necesito-usar-para-un-producto-palabras-que-pueden-
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
-</div>
+>⚠️ VTEX presenta dos opciones de búsqueda - La búsqueda VTEX y VTEX Intelligent Search. Este artículo se refiere a la búsqueda VTEX. Para saber más sobre la aplicación VTEX Intelligent Search, consulte <a href = "https://help.vtex.com/es/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nuestra guía</a>.
 
 Si usted necesita utilizar, en sus productos, palabras que tal vez para el buscador no sean importantes, existen algunas buenas prácticas:
 
diff --git a/docs/tutorials/es/white-label-seller.md b/docs/tutorials/es/white-label-seller.md
index 7e6bc80bb..a18f4cd3b 100644
--- a/docs/tutorials/es/white-label-seller.md
+++ b/docs/tutorials/es/white-label-seller.md
@@ -30,18 +30,14 @@ La [cuenta franquicia](https://help.vtex.com/es/tutorial/what-is-a-franchise-acc
 
 Usar la cuenta franquicia es estratégico, por ejemplo, para las operaciones que desean expandir sus ventas con la integración de tiendas físicas, ya que existe la posibilidad de heredar un catálogo ya registrado en la plataforma VTEX. Obtén más información en [¿Qué es una cuenta franquicia?](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
-<div class = "alert alert-info">
-De forma predeterminada, toda cuenta franquicia es un <i>seller white label</i> de la cuenta principal. Aunque <i>seller white label</i> y cuenta franquicia son conceptos que están relacionados, no se corresponden entre sí, ya que <i>seller white label</i> es un tipo de <i>seller</i>, y cuenta franquicia es un tipo de cuenta.
-</div>
+>ℹ️ De forma predeterminada, toda cuenta franquicia es un <i>seller white label</i> de la cuenta principal. Aunque <i>seller white label</i> y cuenta franquicia son conceptos que están relacionados, no se corresponden entre sí, ya que <i>seller white label</i> es un tipo de <i>seller</i>, y cuenta franquicia es un tipo de cuenta.
 
 Es posible que una cuenta estándar funcione como _seller white label_ de otra tienda VTEX. En este escenario, el marketplace no informa al consumidor quién es el _seller_ que realiza el envío del pedido. Otra posibilidad es que una cuenta franquicia actúe como un _seller_ normal de un _marketplace_ que no sea la cuenta principal. En resumen:
 
 - **Cuenta:** puede ser una cuenta franquicia o una cuenta estándar.
 - **_Seller_:** puede ser común o _white label_.
 
-<div class = "alert alert-info">
-Para agregar un seller white label, es necesario tener este modelo previsto en el contrato con VTEX. Una vez acordado un contrato con el representante de ventas de VTEX responsable de tu marketplace, solicita la adición de una cuenta franquicia por medio de nuestro Soporte. Todas las cuentas franquicias se crean como un seller white label, y no es posible cambiar el tipo de seller después de su creación.
-</div>
+>ℹ️ Para agregar un seller white label, es necesario tener este modelo previsto en el contrato con VTEX. Una vez acordado un contrato con el representante de ventas de VTEX responsable de tu marketplace, solicita la adición de una cuenta franquicia por medio de nuestro Soporte. Todas las cuentas franquicias se crean como un seller white label, y no es posible cambiar el tipo de seller después de su creación.
 
 ### Más información
 
diff --git a/docs/tutorials/es/white-label-sellers-selection.md b/docs/tutorials/es/white-label-sellers-selection.md
index 55a78946c..9d4a4013e 100644
--- a/docs/tutorials/es/white-label-sellers-selection.md
+++ b/docs/tutorials/es/white-label-sellers-selection.md
@@ -22,9 +22,7 @@ Existen dos tipos de _sellers_ en VTEX:
 - **Seller común:** el _seller_ está visible en la vitrina del _marketplace_ y el consumidor puede elegirlo durante su experiencia de compra.
 - **[Seller white label](https://help.vtex.com/es/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa):** el _seller_ permanece oculto durante la experiencia de compra del consumidor y la plataforma VTEX lo selecciona automáticamente para realizar el envío del pedido.
 
-<div class = "alert alert-info">
-En VTEX, la cuenta franquicia es un tipo de cuenta que no solo se crea y asocia a una cuenta principal, sino que también tiene la característica de ser un <i>seller white label</i> de la cuenta principal. Este modelo de negocio resulta estratégico para los <i>retailers</i> que desean conectar las tiendas físicas con su canal de venta digital. Obtén más información en <a href="https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">¿Qué es una cuenta franquicia?</a>.
-</div>
+>ℹ️ En VTEX, la cuenta franquicia es un tipo de cuenta que no solo se crea y asocia a una cuenta principal, sino que también tiene la característica de ser un <i>seller white label</i> de la cuenta principal. Este modelo de negocio resulta estratégico para los <i>retailers</i> que desean conectar las tiendas físicas con su canal de venta digital. Obtén más información en [¿Qué es una cuenta franquicia?](https://help.vtex.com/es/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
 Cuando el consumidor navega por el _marketplace_, ya sea mientras mira la vitrina o cuando está en el carrito, la información sobre la disponibilidad de los _ítems_ y las opciones de envío de los _sellers_ que se le presentan al consumidor pueden variar y dependerá si el _marketplace_ conoce o no la ubicación del comprador. En tal sentido, este artículo se divide en:
 
@@ -39,9 +37,7 @@ Al navegar por el _marketplace_, los clientes esperan ver productos que se pueda
 - [Vitrina sin localización del cliente](#vitrina-sin-localizacion-del-cliente)
 - [Vitrina con localización del cliente](#vitrina-con-localizacion-del-cliente)
 
-<div class = "alert alert-info">
-En la etapa de la vitrina, la plataforma VTEX no toma en cuenta las opciones de envío de los <i>sellers</i>. Esto recién se hace cuando el cliente ingresa su dirección en el <i>checkout</i>. Por lo tanto, es posible que el precio y la disponibilidad mostrados en la vitrina sean distintos al cerrar la compra.
-</div>
+>ℹ️ En la etapa de la vitrina, la plataforma VTEX no toma en cuenta las opciones de envío de los <i>sellers</i>. Esto recién se hace cuando el cliente ingresa su dirección en el <i>checkout</i>. Por lo tanto, es posible que el precio y la disponibilidad mostrados en la vitrina sean distintos al cerrar la compra.
 
 ### Vitrina sin localización del cliente
 
@@ -79,9 +75,7 @@ Luego de filtrar a los _sellers_ según los criterios mencionados, se selecciona
 - [Entrega](#modalidad-de-envio-entrega): el cliente recibe el pedido en su dirección.
 - [Recogida](#modalidad-de-envio-retiro-en-un-punto-de-recogida): el cliente recoge el pedido en un [punto de recogida](https://help.vtex.com/es/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R). 
 
-<div class = "alert alert-info">
-  De manera predeterminada, del total máximo de doce <i>sellers</i>, hasta seis realizan entregas y hasta seis ofrecen la opción de retirar el pedido en un punto de recogida. Sin embargo, si menos de seis <i>sellers</i> cumplen con los criterios de una modalidad de envío, es posible que la lista de <i>sellers</i> de la otra modalidad de envío incluya más de seis. Por ejemplo, si solo cinco <i>sellers</i> entregan el pedido, la lista de <i>sellers</i> que ofrezcan la opción de recogida del pedido podrá estar integrada por siete <i>sellers</i>, de manera tal que haya un total de doce <i>sellers</i>.
-</div>
+>ℹ️ De manera predeterminada, del total máximo de doce <i>sellers</i>, hasta seis realizan entregas y hasta seis ofrecen la opción de retirar el pedido en un punto de recogida. Sin embargo, si menos de seis <i>sellers</i> cumplen con los criterios de una modalidad de envío, es posible que la lista de <i>sellers</i> de la otra modalidad de envío incluya más de seis. Por ejemplo, si solo cinco <i>sellers</i> entregan el pedido, la lista de <i>sellers</i> que ofrezcan la opción de recogida del pedido podrá estar integrada por siete <i>sellers</i>, de manera tal que haya un total de doce <i>sellers</i>.
 
 #### Modalidad de envío: entrega
 
@@ -96,13 +90,12 @@ La selección de hasta seis _sellers white label_ para el envío en la modalidad
 6. Sobre la base de los _sellers_ seleccionados para cubrir el carrito, la plataforma VTEX calcula las combinaciones que incluyen menos _sellers_.
 7. De todas esas combinaciones, surge una lista de –como máximo– seis _sellers_ para el envío en la modalidad de entrega.
 
-<div class = "alert alert-info">
-Es posible que, en alguna etapa de la selección, haya un empate de sellers. Cuando esto ocurre, la selección se divide en dos frentes para así seleccionar:i
-<ul>
-  <li>Hasta tres sellers que ofrezcan el menor costo.</li>
-  <li>Hasta tres sellers que ofrezcan el mejor plazo.</li>
-</ul>
-</div>
+>ℹ️ Es posible que, en alguna etapa de la selección, haya un empate de sellers. Cuando esto ocurre, la selección se divide en dos frentes para así seleccionar:i
+>
+> * Hasta tres sellers que ofrezcan el menor costo.
+>
+> * Hasta tres sellers que ofrezcan el mejor plazo.
+> 
 
 Si hay un empate entre los _sellers_ con los criterios de menor costo o mejor plazo, el criterio de desempate será el del _seller_ que tenga el mayor número de SKU en su _stock_.
 
@@ -168,9 +161,7 @@ La selección de un máximo de seis _sellers_ para la modalidad de envío en un
     - **Mejor plazo:** _sellers_ que preparan los productos para su retiro en el punto de recogida en menos tiempo.
     - **Menor costo:** _sellers_ que ofrecen menores precios para el retiro del pedido en el punto de recogida.
 
-<div class = "alert alert-info">
-Cuando hay un empate entre los criterios de menor costo o mejor plazo, el factor de desempate es el <i>seller</i> con el número más alto de SKU en su <i>stock</i>.
-</div>
+>ℹ️ Cuando hay un empate entre los criterios de menor costo o mejor plazo, el factor de desempate es el <i>seller</i> con el número más alto de SKU en su <i>stock</i>.
 
 ##### Ejemplo para envío en la modalidad de retiro en un punto de recogida
 
diff --git a/docs/tutorials/pt/accessing-the-beta-environment.md b/docs/tutorials/pt/accessing-the-beta-environment.md
index 5e78fa421..eb21a371c 100644
--- a/docs/tutorials/pt/accessing-the-beta-environment.md
+++ b/docs/tutorials/pt/accessing-the-beta-environment.md
@@ -17,9 +17,7 @@ subcategory: Se4oi5LroIII2Ei0uGAoE
 
 Na VTEX, todas as lojas possuem um ambiente beta. Neste local, o usuário da plataforma (lojista, desenvolvedor ou outra pessoa com acesso) pode realizar testes para validar novas configurações  ou versões de aplicações/serviços antes de promover as mudanças no ambiente em que os clientes realizam as compras, também conhecido como ambiente de produção (stable).
 
-<div class = "alert alert-info">
-O ambiente beta é uma reprodução exata do ambiente de produção (stable), incluindo dados e configurações da loja.
-</div>
+>ℹ️ O ambiente beta é uma reprodução exata do ambiente de produção (stable), incluindo dados e configurações da loja.
 
 Dessa forma, **a alteração de dados no ambiente beta afeta os dados no ambiente stable**.
 
@@ -41,6 +39,4 @@ Para acessar o ambiente beta em sua loja, é necessário habilitar o cookie `vte
 <li>Atualize a página pressionando a tecla <code>F5</code> ou o botão de atualizar do seu navegador. Após o carregamento da página, o Admin da loja já estará em ambiente Beta.</li>
 </ol>
 
-<div class = "alert alert-info">
-Para voltar à loja em seu ambiente principal, acesse novamente a tela Dev. Tools do seu navegador e remova o cookie <code>vtex-commerce-env</code> inserido. Atualize novamente a página para retornar ao ambiente de produção <b>stable</b>.
-</div>
+>ℹ️ Para voltar à loja em seu ambiente principal, acesse novamente a tela Dev. Tools do seu navegador e remova o cookie `vtex-commerce-env` inserido. Atualize novamente a página para retornar ao ambiente de produção **stable**.
diff --git a/docs/tutorials/pt/adding-collections-cms.md b/docs/tutorials/pt/adding-collections-cms.md
index c09b28db0..7c0bce4b2 100644
--- a/docs/tutorials/pt/adding-collections-cms.md
+++ b/docs/tutorials/pt/adding-collections-cms.md
@@ -15,9 +15,7 @@ legacySlug: cadastrar-colecoes
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p>Existem duas formas de configurar coleções: por meio do Portal CMS Legado ou utilizando o módulo de <a href="https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye">Coleções Beta</a>. Este artigo refere-se à configuração de coleções por meio do Portal CMS Legado.</p>
-</div>
+>⚠️ Existem duas formas de configurar coleções: por meio do Portal CMS Legado ou utilizando o módulo de [Coleções Beta](https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye). Este artigo refere-se à configuração de coleções por meio do Portal CMS Legado.
 
 Siga o passo a passo abaixo para cadastrar uma nova coleção:
 
diff --git a/docs/tutorials/pt/adding-sku-specifications-or-fields.md b/docs/tutorials/pt/adding-sku-specifications-or-fields.md
index 218bb4050..3b20c59d4 100644
--- a/docs/tutorials/pt/adding-sku-specifications-or-fields.md
+++ b/docs/tutorials/pt/adding-sku-specifications-or-fields.md
@@ -33,9 +33,7 @@ Neste artigo, explicamos como funciona a herança das especificações que você
         * [Cadastro do SKU](#cadastro-do-sku)
         * [Planilha](#planilha)
 
-<div class = "alert alert-info">
-  <p>Para criar uma especificação de SKU utilizando a <strong>Catalog API</strong>, siga o guia para desenvolvedores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a>.</p>
-</div>
+>ℹ️ Para criar uma especificação de SKU utilizando a **Catalog API**, siga o guia para desenvolvedores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification).
 
 ## Herança de especificações de SKU
 
@@ -55,9 +53,7 @@ Veja o passo a passo completo nas seções a seguir.
 
 ### Criar um campo de SKU
 
-<div class = "alert alert-warning">
-  <p>Uma vez criados, campos de SKU não podem ser apagados. Se você tornar o campo inativo, todos os SKUs que estão na categoria ficarão inativos, até que o campo fique ativo novamente. Não preencher uma especificação no cadastro do SKU pode ser uma das causas para que o SKU não apareça no site, pois ele fica inativo.</p>
-</div>
+>⚠️ Uma vez criados, campos de SKU não podem ser apagados. Se você tornar o campo inativo, todos os SKUs que estão na categoria ficarão inativos, até que o campo fique ativo novamente. Não preencher uma especificação no cadastro do SKU pode ser uma das causas para que o SKU não apareça no site, pois ele fica inativo.
 
 Para criar um campo de SKU, siga as instruções abaixo:
 
@@ -65,9 +61,7 @@ Para criar um campo de SKU, siga as instruções abaixo:
 2. Clique em **Categorias**.
 3. Clique na categoria associada ao grupo de especificações em que você deseja criar um campo de SKU.
 
-    <div class = "alert alert-warning">
-      <p>Observe que ao criar um campo em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela.</p>
-    </div>
+    >⚠️ Observe que ao criar um campo em um nível de categoria mais alto, a especificação será apresentada em todos os níveis de categoria abaixo dela.
 
 3. Clique em `Ações` <i class="fas fa-angle-down"></i>.
 4. Clique em `Campo (SKU)`.
@@ -138,9 +132,7 @@ Os **Valores** dos campos de SKU irão variar de acordo com o tipo do campo esco
 
 ![sku-spec-2](https://images.ctfassets.net/alneenqid6w5/5MwO6aTSuIzCbxlrnzjTHQ/066317aa51dbd5521e83f85d9923782f/pt-sku-spec-2.gif)
 
-<div class = "alert alert-info">
-  <p>Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção <strong>Ativo</strong>.</p>
-</div>
+>ℹ️ Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção **Ativo**.
 
 #### Acessar ou editar valores cadastrados
 
diff --git a/docs/tutorials/pt/adding-specifications-or-product-fields.md b/docs/tutorials/pt/adding-specifications-or-product-fields.md
index c285561c4..f54823568 100644
--- a/docs/tutorials/pt/adding-specifications-or-product-fields.md
+++ b/docs/tutorials/pt/adding-specifications-or-product-fields.md
@@ -33,9 +33,7 @@ Neste artigo, explicamos como funciona a herança das especificações que você
         * [Cadastro do produto](#cadastro-do-produto)
         * [Planilha](#planilha)
 
-<div class = "alert alert-info">
-  <p>Para criar uma especificação de produto utilizando a<strong> Catalog API</strong>, siga o guia para desenvolvedores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a>.</p>
-</div>
+>ℹ️ Para criar uma especificação de produto utilizando a** Catalog API**, siga o guia para desenvolvedores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification).
 
 ## Herança de especificações de produto
 
@@ -148,9 +146,7 @@ Já para os campos de tipo **Combo**, **Radio** e **CheckBox**, é necessário c
 
 ![product-spec-2](https://images.ctfassets.net/alneenqid6w5/5F0K7fQTFOf2b7opIrgpP6/283b1aca04c1790b548ee51438fe132f/PT_ProdutoGif_2_Alterado.gif)
 
-<div class = "alert alert-info">
-  <p>Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção <strong>Ativo</strong>.</p>
-</div>
+>ℹ️ Caso esteja cadastrando os primeiros valores de um campo, é necessário voltar no formulário daquele campo específico e marcar a opção **Ativo**.
 
 #### Acessar ou editar valores cadastrados
 
diff --git a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
index 3379a2e71..860dea422 100644
--- a/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
+++ b/docs/tutorials/pt/advertising-with-vtex-ad-network-beta.md
@@ -15,9 +15,7 @@ legacySlug: anunciando-com-vtex-ad-network-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 Com [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), você pode anunciar produtos da sua marca em frentes de lojas VTEX que possuem seu produto no catálogo.
 
@@ -36,9 +34,7 @@ Se você já é um anunciante do **VTEX Ad Network**, confira neste artigo como
 
 Para criar uma [campanha](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#campanhas), siga os passos abaixo:
 
-<div class = "alert alert-info">
-Atualmente a VTEX disponibiliza um único formato de anúncio: resultados de pesquisa. Saiba mais sobre este <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#formato-de-anuncio">formato de anúncio</a>.
-</div>
+>ℹ️ Atualmente a VTEX disponibiliza um único formato de anúncio: resultados de pesquisa. Saiba mais sobre este [formato de anúncio](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#formato-de-anuncio).
 
 1. No Admin VTEX, acesse **Storefront > Ad Network > Campanhas**.
 2. Clique em `Criar Campanha`.
@@ -125,9 +121,7 @@ Abaixo você encontra uma tabela com informações de cada campanha:
 - **Orçamento:** orçamento total.
 - **Orçamento restante:** orçamento ainda disponível até o momento.
 
-<div class = "alert alert-info">
-Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#janela-de-atribuicao">atribuição de vendas a anúncios</a>.
-</div>
+>ℹ️ Saiba mais sobre [atribuição de vendas a anúncios](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#janela-de-atribuicao).
 
 Você pode filtrar os dados da tabela de acordo com estes filtros:
 
@@ -157,7 +151,5 @@ Abaixo dos dados agregados você encontra uma tabela com informações sobre o d
 - **ROAS:** retorno sobre investimento em publicidade.
 - **Orçamento restante:** orçamento ainda disponível até o momento.
 
-<div class = "alert alert-info">
-Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#janela-de-atribuicao">atribuição de vendas a anúncios</a>.
-</div>
+>ℹ️ Saiba mais sobre [atribuição de vendas a anúncios](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur#janela-de-atribuicao).
 
diff --git a/docs/tutorials/pt/affiliates-program-app.md b/docs/tutorials/pt/affiliates-program-app.md
index 2def9fcb3..1134fbc56 100644
--- a/docs/tutorials/pt/affiliates-program-app.md
+++ b/docs/tutorials/pt/affiliates-program-app.md
@@ -15,9 +15,7 @@ legacySlug: aplicativo-affiliates-program
 subcategory: 6GWaAkVqXQYN79ilMgUsPr
 ---
 
-<div class = "alert alert-info">
-O <b>Affiliates Program</b> é um aplicativo compatível apenas com lojas <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2">VTEX IO</a>, e não está disponível para lojas que utilizam <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj">CMS Portal Legado</a> ou <a href="https://faststore.dev/tutorials/cms/0#vtex-headless-cms">Headless CMS</a>. Para instalar e configurar o aplicativo na sua loja VTEX, acesse o guia para desenvolvedores Affiliates Program app.
-</div>
+>ℹ️ O **Affiliates Program** é um aplicativo compatível apenas com lojas [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/4yB9wSl79cArd68aRBnBZ2), e não está disponível para lojas que utilizam [CMS Portal Legado](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/1oN446gRGcR2s70RvBCAmj) ou [Headless CMS](https://faststore.dev/tutorials/cms/0#vtex-headless-cms). Para instalar e configurar o aplicativo na sua loja VTEX, acesse o guia para desenvolvedores Affiliates Program app.
 
 No aplicativo **Affiliates Program**, um afiliado é alguém que se associa a sua loja VTEX para promover as vendas em troca de uma comissão. O termo é, portanto, diferente do [conceito usual de afiliado na VTEX](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0).
 
@@ -48,9 +46,7 @@ A **página de perfil do afiliado** é uma interface pela qual ele pode acompanh
 
 A **página de cadastro** permite que os próprios interessados em se tornar afiliados preencham seus dados para solicitar registro junto a sua loja VTEX.
 
-<div class = "alert alert-info">
-As páginas dos afiliados são customizáveis. Para mais informações, veja o guia para desenvolvedores <a href="https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app">Affiliates Program app</a>.
-</div>
+>ℹ️ As páginas dos afiliados são customizáveis. Para mais informações, veja o guia para desenvolvedores [Affiliates Program app](https://developers.vtex.com/vtex-developer-docs/docs/affiliates-program-app).
 
 ### Páginas no Admin VTEX
 
@@ -127,9 +123,7 @@ No topo da página, você visualiza as seguintes métricas sobre os pedidos real
 - **Total do pedido:** soma dos valores dos pedidos, feita a partir do preço dos itens e sem incluir os custos de envio.
 - **Total da comissão do pedido:**  soma dos valores das comissões dos afiliados sobre os pedidos.
 
-<div class = "alert alert-info">
-Para acompanhar o fluxo de um pedido, clique sobre o `ID do pedido`. Desta forma, você é redirecionado para o Admin VTEX em <b>Pedidos > Todos os pedidos</b>.
-</div>
+>ℹ️ Para acompanhar o fluxo de um pedido, clique sobre o `ID do pedido`. Desta forma, você é redirecionado para o Admin VTEX em **Pedidos > Todos os pedidos**.
 
 ### Pesquisar pedidos
 
@@ -195,9 +189,7 @@ Para exportar uma planilha de comissionamento por SKU com extensão CSV, no topo
 
 O arquivo será enviado para o email do [usuário](https://help.vtex.com/pt/tutorial/gerenciando-usuarios--tutorials_512) logado.
 
-<div class = "alert alert-info">
-O conteúdo exportado é referente ao comissionamento dos SKUs da listagem no momento da exportação. Se algum filtro estiver ativo, somente as comissões de SKU selecionadas serão exportadas.
-</div>
+>ℹ️ O conteúdo exportado é referente ao comissionamento dos SKUs da listagem no momento da exportação. Se algum filtro estiver ativo, somente as comissões de SKU selecionadas serão exportadas.
 
 ### Importar comissões
 
@@ -213,9 +205,7 @@ Confira se a seguinte mensagem aparece:
 
 O nome do arquivo adicionado vai aparecer próximo ao campo `Última importação`.
 
-<div class = "alert alert-info">
-É possível identificar a data de importação e o usuário que executou a ação, passando o cursor sobre o símbolo `?` em `Última importação`.
-</div>
+>ℹ️ É possível identificar a data de importação e o usuário que executou a ação, passando o cursor sobre o símbolo `?` em `Última importação`.
 
 ### Fazer o download da última importação
 
diff --git a/docs/tutorials/pt/all-orders.md b/docs/tutorials/pt/all-orders.md
index 16ba6e8a7..1090c0414 100644
--- a/docs/tutorials/pt/all-orders.md
+++ b/docs/tutorials/pt/all-orders.md
@@ -15,9 +15,7 @@ legacySlug: lista-de-pedidos-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-<div class = "alert alert-info">
-É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 A página **Todos os Pedidos** permite que lojistas acompanhem os pedidos da sua loja e extraiam informação para uma gestão inteligente do seu negócio. Para acessar a página, no menu do seu Admin VTEX, clique em **Pedidos > Todos os Pedidos**. Nesta página, você pode:
 
diff --git a/docs/tutorials/pt/analytics.md b/docs/tutorials/pt/analytics.md
index fe9646e13..f9ff41b80 100644
--- a/docs/tutorials/pt/analytics.md
+++ b/docs/tutorials/pt/analytics.md
@@ -24,9 +24,7 @@ Siga os passos abaixo para acessar a página:
 1. No Admin VTEX, acesse **Storefront**, ou digite **Storefront** na barra de busca no topo da página.
 2. Em __Intelligent Search__, clique em __Analytics__. 
 
-<div class = "alert alert-info">
-<p>A página de <strong>Analytics</strong> é nativa no VTEX Intelligent Search. Não é possível desabilitá-la no Admin.</p>
-</div>
+>ℹ️ A página de **Analytics** é nativa no VTEX Intelligent Search. Não é possível desabilitá-la no Admin.
 
 ## Dados
 
@@ -72,9 +70,7 @@ Para exportar um relatório no formato CSV, você deve seguir os passos abaixo.
 5. Espere o arquivo estar disponível para download. Sair desta página não interrompe o processo.
 6. Clique em `Baixar`.
 
-<div class = "alert alert-info">
-<p>O arquivo permanece disponível para download por 48 horas.</p>
-</div>
+>ℹ️ O arquivo permanece disponível para download por 48 horas.
 
 O relatório CSV baixado apresenta duas tabelas. A primeira tabela, ilustrada abaixo, contém informações sobre termos pesquisados e as métricas de funil (da coluna **ProductsClick** até a coluna **ProductsSold**), caso essa opção tenha sido selecionada.
 
diff --git a/docs/tutorials/pt/application-keys.md b/docs/tutorials/pt/application-keys.md
index 1da17b1d3..02decad7a 100644
--- a/docs/tutorials/pt/application-keys.md
+++ b/docs/tutorials/pt/application-keys.md
@@ -45,9 +45,7 @@ Na página **Chaves de aplicação**, você pode gerenciar as chaves de aplicaç
 
 Para visualizar essa página, na barra superior do Admin VTEX, clique no **avatar do seu perfil**, marcado pela inicial do seu email, e depois em **Configurações da conta** > **Chaves de aplicação**.
 
-<div class = "alert alert-info">
-<p>Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm">Boas práticas na utilização de chaves de aplicação</a>.</p>
-</div>
+>ℹ️ Saiba mais sobre [Boas práticas na utilização de chaves de aplicação](https://help.vtex.com/pt/tutorial/boas-praticas-chaves-de-aplicacao--7b6nD1VMHa49aI5brlOvJm).
 
 ## Gerar chaves de aplicação internas
 
diff --git a/docs/tutorials/pt/audit.md b/docs/tutorials/pt/audit.md
index 1867c00e7..9370d3e43 100644
--- a/docs/tutorials/pt/audit.md
+++ b/docs/tutorials/pt/audit.md
@@ -38,9 +38,7 @@ Confira o passo a passo para buscar por um evento utilizando os filtros disponí
 2. Em **Filtros**, no menu **Aplicação**, selecione a aplicação relacionada à busca.
 3. No menu **Data**, escolha uma data pré-definida para a busca. Se preferir definir o exato intervalo de datas para a busca, ative a opção **Personalizada** e determine as datas de **Início** e **Fim** para a busca.
 
-   <div class= "alert alert-info">
-     <p>Apenas registros dos últimos três meses são armazenados.</p>
-   </div>
+   >ℹ️ Apenas registros dos últimos três meses são armazenados.
 
 4. Se desejar, inclua um filtro por Ação. Para isso, no campo ao lado de `Ação deve ser`, digite o nome da ação e tecle `Enter`. Você pode inserir mais de um valor teclando `Enter` após cada seleção. Confira o nome de cada ação em [Eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 5. Se necessário, você pode adicionar filtros mais específicos para realizar a busca por eventos com mais precisão. Para isso, clique no botão `Adicionar Filtro`.
@@ -56,9 +54,7 @@ Confira o passo a passo para buscar por um evento utilizando os filtros disponí
 
     Confira [Resultados](#resultados) para entender como os eventos são apresentados.
 
-<div class= "alert alert-warning">
-  <p>Os resultados da busca correspondem exatamente ao conteúdo escrito no tópico do filtro. Para evitar resultados inesperados, certifique-se de que você não digitou espaços desnecessários nos termos da busca.</p>
-</div>
+>⚠️ Os resultados da busca correspondem exatamente ao conteúdo escrito no tópico do filtro. Para evitar resultados inesperados, certifique-se de que você não digitou espaços desnecessários nos termos da busca.
 
 Se desejar, você pode compartilhar uma busca com outro usuário. Para isso, clique em `Compartilhar busca`, no canto superior direito da página. O link para a busca no Audit será copiado para a sua área de transferência.
 
@@ -129,6 +125,4 @@ Confira a seguir as informações disponíveis nesta aba:
 | Período buscado | Data de início e fim do período selecionado para a busca. |
 | Refazer busca | Botão que permite repetir a busca. |
 
-<div class= "alert alert-warning">
-  <p>Apenas 50 buscas ficam gravadas na aba <b>Últimas buscas</b>. Se quiser salvar uma busca além desse limite, adicione-a aos favoritos do seu browser.</p>
-</div>
+>⚠️ Apenas 50 buscas ficam gravadas na aba **Últimas buscas**. Se quiser salvar uma busca além desse limite, adicione-a aos favoritos do seu browser.
diff --git a/docs/tutorials/pt/autocomplete.md b/docs/tutorials/pt/autocomplete.md
index 6d40c219e..8b8042e46 100644
--- a/docs/tutorials/pt/autocomplete.md
+++ b/docs/tutorials/pt/autocomplete.md
@@ -15,9 +15,7 @@ legacySlug: autocomplete
 subcategory: 30Kdgc6wJkMWgcXLB8mGr7
 ---
 
-<div class = "alert alert-warning">
-O Autocomplete é uma ferramenta já ativa no VTEX Intelligent Search. Não é possível desligá-la no Admin.
-    </div>
+>⚠️ O Autocomplete é uma ferramenta já ativa no VTEX Intelligent Search. Não é possível desligá-la no Admin.
 
 O Autocomplete funciona com base nas informações obtidas por meio do histórico de busca de termos relacionados ao Catálogo. Esses resultados são apresentados em quatro listas diferentes, que podem estar juntas ou separadas, dependendo da interação com o cliente. As seções existentes são:
 
@@ -35,19 +33,14 @@ Durante a interação com a barra de busca, o VTEX Intelligent Search exibe imed
 
 Quando o usuário começa a digitar, o sistema mostra as _Sugestões de busca_ e _Sugestões de produtos_ e remove as listas anteriores.
 
-<div class = "alert alert-info">
-  <p>As informações das seções <b>Termos mais buscados</b> e <b>Sugestão de busca</b> são atualizadas diariamente. Para isso, são utilizados os dados dos últimos 14 dias da interação dos clientes com a busca.</p>
-  </div>
+>ℹ️ As informações das seções **Termos mais buscados** e **Sugestão de busca** são atualizadas diariamente. Para isso, são utilizados os dados dos últimos 14 dias da interação dos clientes com a busca.
 
 Dessa forma, é possível proporcionar ao cliente uma experiência de pesquisa mais fluida e personalizada. Ele consegue visualizar o resultado de maneira rápida, além de receber sugestões baseadas na sua busca.
 
 Outra vantagem para o gestor da loja é o aumento de conversão, resultado dessa dinâmica de usabilidade e experiência.
 
-<div class = "alert alert-info">
-  <p> O Autocomplete oferece sugestões de pesquisa mesmo quando a loja é totalmente nova e ainda não dispõe de dados de interações com clientes, como cliques e buscas.
-    Nesse caso, a funcionalidade gera sugestões de busca a partir de um algoritmo que extrai palavras-chave do catálogo, dos produtos, das marcas e das categorias registradas na loja.
-</p>
-  </div>
+>ℹ️ O Autocomplete oferece sugestões de pesquisa mesmo quando a loja é totalmente nova e ainda não dispõe de dados de interações com clientes, como cliques e buscas.
+>     Nesse caso, a funcionalidade gera sugestões de busca a partir de um algoritmo que extrai palavras-chave do catálogo, dos produtos, das marcas e das categorias registradas na loja.
 
 ## Termos mais buscados
 
diff --git a/docs/tutorials/pt/b2b-checkout-settings.md b/docs/tutorials/pt/b2b-checkout-settings.md
index 282c9d80e..31025f227 100644
--- a/docs/tutorials/pt/b2b-checkout-settings.md
+++ b/docs/tutorials/pt/b2b-checkout-settings.md
@@ -62,9 +62,7 @@ Siga as instruções abaixo para personalizar o processo de checkout B2B na sua
 <li>Ao habilitar <code>Mostrar botão Criar uma cotação</code>, será adicionado o botão <code>Criar uma cotação</code> no checkout, que permite criar um orçamento usando o conteúdo atual do carrinho.</li>
 </ol>
 
-<div class = "alert alert-info">
-Você deve habilitar o botão <code>Criar uma Cotação</code> somente se sua loja tiver o aplicativo Cotações B2B instalado. Para mais informações acesse <a href="https://developers.vtex.com/docs/apps/vtex.b2b-quotes">B2B Quotes & Carts</a>.
-</div>
+>ℹ️ Você deve habilitar o botão `Criar uma Cotação` somente se sua loja tiver o aplicativo Cotações B2B instalado. Para mais informações acesse [B2B Quotes & Carts](https://developers.vtex.com/docs/apps/vtex.b2b-quotes).
 
 <ol start="4">
 <li>Clique em <code>Salvar</code>.</li>
diff --git a/docs/tutorials/pt/best-practices-against-virtual-attacks.md b/docs/tutorials/pt/best-practices-against-virtual-attacks.md
index 2f76e953b..2d46b36f7 100644
--- a/docs/tutorials/pt/best-practices-against-virtual-attacks.md
+++ b/docs/tutorials/pt/best-practices-against-virtual-attacks.md
@@ -23,9 +23,7 @@ A VTEX dispõe de diversas proteções contra possíveis ataques a lojas. Ainda
 * [Configurações do orderForm](#configuracoes-do-orderform)
 * [Desabilitar login por senha](#desabilitar-login-por-senha)
 
-<div class = "alert alert-info">
-  <p>As medidas citadas neste guia não eliminam por completo a possibilidade de ataques, mas podem reduzir bastante a probabilidade deles acontecerem, caso empregadas adequadamente.</p>
-</div>
+>ℹ️ As medidas citadas neste guia não eliminam por completo a possibilidade de ataques, mas podem reduzir bastante a probabilidade deles acontecerem, caso empregadas adequadamente.
 
 ## Antifraude
 
@@ -49,9 +47,7 @@ Recomendamos o uso do [reCAPTCHA v3](https://help.vtex.com/en/tutorial/using-rec
 
 Saiba mais sobre como configurar esta validação no Checkout da sua loja em [reCAPTCHA no Checkout](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#). Para a implementação do reCAPTCHA V3 em uma loja VTEX, consulte o guia para desenvolvedores [reCAPTCHA](https://developers.vtex.com/docs/guides/recaptcha#recaptcha-v3-score).
 
-<div class = "alert alert-info">
-  <p>No fluxo de <a href="https://help.vtex.com/pt/tutorial/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes">cadastro de cartões</a> dos clientes da loja na página <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, a validação por reCAPTCHA está ativa por padrão, sem a necessidade de configuração por parte dos lojistas.</p>
-</div>
+>ℹ️ No fluxo de [cadastro de cartões](https://help.vtex.com/pt/tutorial/tutorial/how-does-my-account-work--2BQ3GiqhqGJTXsWVuio3Xh#cartoes) dos clientes da loja na página [Minha Conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh), a validação por reCAPTCHA está ativa por padrão, sem a necessidade de configuração por parte dos lojistas.
 
 ## Configurações do orderForm
 
diff --git a/docs/tutorials/pt/best-practices-application-keys.md b/docs/tutorials/pt/best-practices-application-keys.md
index 3cf6ba4dd..c86f96b36 100644
--- a/docs/tutorials/pt/best-practices-application-keys.md
+++ b/docs/tutorials/pt/best-practices-application-keys.md
@@ -17,9 +17,7 @@ subcategory: 6uJgdHqWf1Mo0rUfgxseTn
 
 A VTEX dispõe de diversas APIs para que clientes e parceiros possam desenvolver integrações altamente personalizáveis ​​com a plataforma.  [Chaves de aplicação](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) são usadas para fornecer acesso seguro a dados consumidos por integrações, sem expor sua conta a usuários ou aplicativos não autorizados.
 
-<div class = "alert alert-info">
-Este tipo de credencial é utilizado para autenticação de identidade via API.
-</div>
+>ℹ️ Este tipo de credencial é utilizado para autenticação de identidade via API.
 
 O manuseio inadequado de [chaves de aplicação](https://help.vtex.com/tutorial/application-keys--2iffYzlvvz4BDMr6WGUtet) pode gerar vazamentos e, consequentemente, situações de acesso indevido. Conheça abaixo boas práticas que recomendamos para o gerenciamento destas credenciais, as quais você pode implementar para aumentar a segurança da sua loja.
 
diff --git a/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md b/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md
index deef4e709..77f6a17ef 100644
--- a/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md
+++ b/docs/tutorials/pt/best-practices-for-the-success-of-your-vtex-store.md
@@ -30,9 +30,7 @@ Este artigo apresenta algumas das principais práticas para você gerenciar sua
     * [Participe da VTEX Community](#participe-da-vtex-community)
     * [Conheça boas práticas em solicitações do Suporte VTEX](#conheca-boas-praticas-em-solicitacoes-do-suporte-vtex)
 
-<div class = "alert alert-info">
-<b>Agências parceiras</b><p>Existem diversas agências e parceiros de implementação que foram certificados pela VTEX por terem demonstrado excelência e confiabilidade em projetos com a plataforma. Portanto, seja para uma implementação eficiente, uma arquitetura de loja personalizada ou para obter apoio contínuo na infraestrutura, recomendamos a contratação de agências parceiras. Para conferir nossos parceiros, acesse o <a href="https://partnerportal.vtex.com/parceiros">Partner Portal</a> (somente português) ou acesse <a href="http://VTEX.com">VTEX.com</a> (demais idiomas).</p>
-</div>
+>ℹ️ **Agências parceiras**Existem diversas agências e parceiros de implementação que foram certificados pela VTEX por terem demonstrado excelência e confiabilidade em projetos com a plataforma. Portanto, seja para uma implementação eficiente, uma arquitetura de loja personalizada ou para obter apoio contínuo na infraestrutura, recomendamos a contratação de agências parceiras. Para conferir nossos parceiros, acesse o [Partner Portal](https://partnerportal.vtex.com/parceiros) (somente português) ou acesse [VTEX.com](http://VTEX.com) (demais idiomas).
 
 ## Performance e segurança
 
@@ -50,9 +48,7 @@ Os principais benefícios em criar uma documentação da arquitetura da sua oper
 * **Atuação rápida em questões de segurança:** a correção de problemas ou vulnerabilidades de segurança são mais rápidas quando a documentação da arquitetura é compartilhada.
 * **Otimização do suporte:** quando é necessário apoio do nosso suporte ou de terceiros, compartilhar a documentação da arquitetura facilita a comunicação entre as partes e a eficácia de sua atuação.
 
-<div class = "alert alert-info">
-Com relação a documentar a arquitetura da loja, veja a página <a href="https://developers.vtex.com/docs/guides">Get started</a> no nosso portal para desenvolvedores, e conheça o <a href="https://assets.vtex.com/4524045/">framework interativo</a> da plataforma VTEX.
-</div>
+>ℹ️ Com relação a documentar a arquitetura da loja, veja a página [Get started](https://developers.vtex.com/docs/guides) no nosso portal para desenvolvedores, e conheça o [framework interativo](https://assets.vtex.com/4524045/) da plataforma VTEX.
 
 ### Siga as orientações gerais de segurança
 
@@ -62,9 +58,7 @@ Existem estratégias para prevenir e reduzir a exposição da sua loja ao risco
 * **reCAPTCHA:** use o [reCAPTCHA](https://help.vtex.com/pt/tutorial/recaptcha-no-checkout--18Te3oDd7f4qcjKu9jhNzP#) para se prevenir de fraudes com falsos usuários criados por programas maliciosos.
 * **Autenticação:** caso sua loja esteja sofrendo ataques recorrentes, considere desabilitar o login por senha e optar por outra forma de [autenticação](https://help.vtex.com/pt/tutorial/pagina-de-autenticacao--21CkKHLKP1o41lUpGhuRUs) para os clientes da sua loja.
 
-<div class = "alert alert-info">
-Para mais informações sobre ações preventivas, veja o artigo <a href="https://help.vtex.com/pt/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE">Boas práticas contra ataques virtuais</a> e este <a href="https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470">post na VTEX Community</a>.
-</div>
+>ℹ️ Para mais informações sobre ações preventivas, veja o artigo [Boas práticas contra ataques virtuais](https://help.vtex.com/pt/tutorial/boas-praticas-contra-ataques-virtuais--191rpbF7UgrKapVCi1PCDE) e este [post na VTEX Community](https://community.vtex.com/t/duvidas-frequentes-varias-tentativas-de-compras-fraudulentas-o-que-fazer/39470).
 
 ### Controle o nível de permissão de acessos
 
@@ -104,9 +98,7 @@ Alguns dos principais benefícios em se manter informado são:
 * Configurar as atualizações para aumentar a segurança da sua loja, pois inovamos continuamente visando a proteção do seu negócio.
 * Caso seja necessário contatar o suporte, conhecer o funcionamento dos novos recursos permite uma interação mais eficiente com o suporte, o que resulta em resoluções mais rápidas.
 
-<div class = "alert alert-info">
-Os anúncios da página <b>Novidades</b> do Help Center também são disponibilizados pelo seu Admin VTEX. Para acessar o conteúdo, basta clicar no ícone de sino no topo da página.
-</div>
+>ℹ️ Os anúncios da página **Novidades** do Help Center também são disponibilizados pelo seu Admin VTEX. Para acessar o conteúdo, basta clicar no ícone de sino no topo da página.
 
 ### Receba notificações de status da plataforma
 
@@ -118,9 +110,7 @@ Para isso, a VTEX disponibiliza a [página de status da plataforma](https://stat
 * [Feed RSS](https://rss.com/blog/how-do-rss-feeds-work/)
 * [Slack](https://slack.com/)
 
-<div class = "alert alert-info">
-Para entender os detalhes da página de status da plataforma, acesse o artigo <a href="https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ">Página de status da VTEX</a>.
-</div>
+>ℹ️ Para entender os detalhes da página de status da plataforma, acesse o artigo [Página de status da VTEX](https://help.vtex.com/pt/tutorial/pagina-de-status-da-vtex--gPhqDn9IQ3c67wbJEX3JJ).
 
 ### Conheça nossos conteúdos de onboarding
 
@@ -165,7 +155,5 @@ Existem [boas práticas para abrir um ticket para o Suporte VTEX](https://help.v
 
 Estas recomendações são algumas das mais importantes. Para mais informações, veja o artigo [Boas práticas para a abertura de um Ticket para o Suporte VTEX](https://help.vtex.com/pt/tutorial/como-escrever-um-ticket-completo-para-o-suporte-vtex--6u4ehk6F0ksuDgYuCbFDRX).
 
-<div class = "alert alert-info">
-Para obter uma visão geral do nosso suporte via ticket, veja a trilha <a href="https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8">Suporte na VTEX</a>, que compõe o <b>Guia de onboarding</b>.
-</div>
+>ℹ️ Para obter uma visão geral do nosso suporte via ticket, veja a trilha [Suporte na VTEX](https://help.vtex.com/pt/tracks/suporte-na-vtex--4AXsGdGHqExp9ZkiNq9eMy/7w7cUmbrdPEKpTMItjXEB8), que compõe o **Guia de onboarding**.
 
diff --git a/docs/tutorials/pt/beta-price-configuration.md b/docs/tutorials/pt/beta-price-configuration.md
index fbf546876..cad5fa972 100644
--- a/docs/tutorials/pt/beta-price-configuration.md
+++ b/docs/tutorials/pt/beta-price-configuration.md
@@ -15,9 +15,7 @@ legacySlug: configuracao-de-precos-beta
 subcategory: 2XTQ6yFYeU5bGHK8Qq3f4I
 ---
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está em estágio Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em estágio Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 Esta nova seção de Configuração de Preços (Beta) permite criar e gerenciar regras para tabelas de preços e alterar configurações gerais de forma prática e rápida. 
 
@@ -39,9 +37,7 @@ Nesta seção, você pode definir o markup padrão e o limite de variação de p
 
 - **Sobrescrever preços de sellers:** essa opção sobrescreve todos os preços de sellers com os da conta atual.
 
-<div class = "alert alert-info">
-  <p>A configuração <b>Sobrescrever preços de sellers</b> não é disponível para sellers white label.</p>
-</div>
+>ℹ️ A configuração **Sobrescrever preços de sellers** não é disponível para sellers white label.
 
 ## Regras para tabelas de preço
 
diff --git a/docs/tutorials/pt/buy-one-get-one.md b/docs/tutorials/pt/buy-one-get-one.md
index adbd6068d..0fb9ab741 100644
--- a/docs/tutorials/pt/buy-one-get-one.md
+++ b/docs/tutorials/pt/buy-one-get-one.md
@@ -64,9 +64,7 @@ Nesta seção, é possível definir para quais sellers a promoção será aplica
 
 Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
 
-<div class = "alert alert-warning">
-  <p>Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
-</div>
+>⚠️ Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.
 
 ![Restringir esta promoção a produtos dos sellers](https://images.ctfassets.net/alneenqid6w5/3Up0CJMzHHY9rZO0LLRXuw/cf6fdde6e939077f04001cb3e76f02b5/Restringir_esta_promo__o_a_produtos_dos_sellers.png)
 
@@ -91,13 +89,9 @@ Esta seção define as coleções, SKUs e quantidade mínima que devem ser preen
 - **SKUs**: permite inserir o nome ou ID dos SKUs nos quais deseja que o desconto seja aplicado. É possível realizar a  importação de uma lista de SKUs, que deve estar salvo em um arquivo de texto (**.txt**) com cada ID descrito em uma linha diferente.
 - **Quantidade mínima**: permite definir a quantidade mínima de produtos que devem ser inseridos no carrinho, para que o desconto seja concedido. Esse campo é de preenchimento obrigatório.
 
-<div class = "alert alert-warning">
-<p>A promoção não será criada caso os campos de Coleções ou SKUs não estejam preenchidos.</p>
-</div>
+>⚠️ A promoção não será criada caso os campos de Coleções ou SKUs não estejam preenchidos.
 
-<div class = "alert alert-warning">
-<p>Uma promoção Compre e Ganhe pode ser criada com o máximo de 100 SKUs diferentes ao mesmo tempo.</p>
-</div>
+>⚠️ Uma promoção Compre e Ganhe pode ser criada com o máximo de 100 SKUs diferentes ao mesmo tempo.
 
 ![Compre e Ganhe](https://images.ctfassets.net/alneenqid6w5/27rGDqH0dMTcgA8m7cWs27/e818e8a1252f1b46032be2d043fa62cb/Compre_e_Ganhe.png)
 
diff --git a/docs/tutorials/pt/calculating-revenue-through-the-worksheet-exported-from-orders-module.md b/docs/tutorials/pt/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
index 107a2138f..3c79e07ec 100644
--- a/docs/tutorials/pt/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
+++ b/docs/tutorials/pt/calculating-revenue-through-the-worksheet-exported-from-orders-module.md
@@ -29,8 +29,6 @@ Para calcular a receita total a partir da planilha, siga os passos abaixo:
 4. Remova todos os valores duplicados da segunda coluna (__Order__). Isto deve ser feito porque, nos casos de compras de mais de um SKU, são geradas diversas linhas para o mesmo pedido - uma para cada SKU.
 5. Some os valores da coluna __Total Value__. Nesta coluna fica o valor total do pedido (ou seja, já considerando todos os SKUs do carrinho).
 
-<div class = "alert alert-info">
-A soma dos valores da coluna Total Value (após a remoção dos pedidos duplicados) é a receita total obtida com os pedidos selecionados na planilha.
-</div>
+>ℹ️ A soma dos valores da coluna Total Value (após a remoção dos pedidos duplicados) é a receita total obtida com os pedidos selecionados na planilha.
 
 Para entender cada coluna, veja o artigo [Relatório de pedidos](https://help.vtex.com/pt/tutorial/planilha-de-pedidos--31m1ewsmsEe0WS4So2aGMY).
diff --git a/docs/tutorials/pt/campaign-promotion.md b/docs/tutorials/pt/campaign-promotion.md
index f4e37d98e..ce4b489fc 100644
--- a/docs/tutorials/pt/campaign-promotion.md
+++ b/docs/tutorials/pt/campaign-promotion.md
@@ -72,9 +72,7 @@ Veja abaixo a descrição de todos os campos que você precisa preencher para cr
   - **Frete grátis**: desconto total sobre o valor do frete.
   - **Brinde**: desconto total sobre o valor do produto definido como brinde. Você pode selecionar um ou mais SKUs como brinde ou mais de uma unidade do mesmo SKU. Para definir mais de um brinde, selecione a opção **Ativar multiplicador de brindes** e defina a quantidade desejada. Saiba mais sobre essa opção neste [artigo](https://help.vtex.com/pt/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK#).
 
-  <div class = "alert alert-info">
-  <p>O produto <b>Brinde</b> também precisa ter um preço cadastrado, mesmo sendo dado de graça ao cliente.</p>
- </div>
+  >ℹ️ O produto **Brinde** também precisa ter um preço cadastrado, mesmo sendo dado de graça ao cliente.
 
   - **Desconto nominal baseado em fórmula**: desconto é calculado com a soma dos preços de produtos (total), com o frete (freight) e com o percentual de desconto desejado. É importante destacar que o frete implementado na fórmula será o menor disponível para o pedido, independente da seleção do cliente. O separador decimal deve ser sempre o ponto. Exemplo: o desconto será de 30% do valor do produto + valor do frete. Logo, a fórmula deve ser preenchida da seguinte maneira: `((total + freight) * 0.3)`.
   - **Valor fidelidade nominal**: crédito que será adicionado no programa de fidelidade da loja. 
@@ -101,9 +99,7 @@ Nesta seção, é possível definir para quais sellers a promoção será aplica
 
 Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
-</div>
+>⚠️ **Atenção:** não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.
 
 #### Política Comercial
 
diff --git a/docs/tutorials/pt/canceling-orders.md b/docs/tutorials/pt/canceling-orders.md
index 31359d0c1..6228d511c 100644
--- a/docs/tutorials/pt/canceling-orders.md
+++ b/docs/tutorials/pt/canceling-orders.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 O cancelamento de pedido na VTEX pode ser realizado em praticamente qualquer status de sua evolução. Cabe destacar que uma vez cancelado, não é possível alterar o status do pedido.
 
-<div class = "alert alert-warning">
-Não é possível cancelar pedidos que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
-</div>
+>⚠️ Não é possível cancelar pedidos que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 Há duas formas de fazer esta ação, pelo Admin VTEX e por API.
 
diff --git a/docs/tutorials/pt/carrier-working-hours.md b/docs/tutorials/pt/carrier-working-hours.md
index 5e0b09634..0b79c33ea 100644
--- a/docs/tutorials/pt/carrier-working-hours.md
+++ b/docs/tutorials/pt/carrier-working-hours.md
@@ -31,9 +31,7 @@ As configurações de horário de funcionamento influenciam o cálculo do tempo
 
   >❗ Para autorizar a transportadora a receber pedidos nos finais de semana, este toggle deve ser marcado como `Ativo`. Mesmo se sábados e domingos estiverem configurados como janelas válidas, a ativação do toggle é obrigatória para autorizar a transportadora a receber pedidos fora do horário de funcionamento.
 
-  <div class = "alert alert-info">
-Quando esta opção está habilitada, o <a href="https://help.vtex.com/pt/tutorial/how-shipping-calculation-works--tutorials_116">cálculo de envio</a> do pedido é influenciado, e o tempo desde a realização do pedido até o horário de início de funcionamento da transportadora é somado ao tempo de envio total de envio.
-</div>
+  >ℹ️ Quando esta opção está habilitada, o [cálculo de envio](https://help.vtex.com/pt/tutorial/how-shipping-calculation-works--tutorials_116) do pedido é influenciado, e o tempo desde a realização do pedido até o horário de início de funcionamento da transportadora é somado ao tempo de envio total de envio.
 
 3. Selecione o `Dia da semana` e respectivamente o `Horário de início` e `Horário de término` do envio, sendo:
     * **Dia da semana:** os dias da semana que a transportadora faz as entregas.
diff --git a/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md b/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
index 03c859255..578dff166 100644
--- a/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
+++ b/docs/tutorials/pt/carriers-working-hours-and-scheduled-delivery-beta.md
@@ -15,9 +15,7 @@ legacySlug: horario-de-funcionamento-de-transportadoras-e-entrega-agendada-beta
 subcategory: 32vrn4K2ZscjUaIBe6w5fm
 ---
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 O módulo *Estoque & Entrega* é onde você faz todo o gerenciamento da logística da sua loja. A aba *Estratégia de Envio* permite que você cadastre sua rota logística, incluindo as **Políticas de Envio** ou transportadoras. Pensando em melhorar a experiência do módulo, atualizamos essa funcionalidade.
 
diff --git a/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md b/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
index 061290260..60fee1f2a 100644
--- a/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
+++ b/docs/tutorials/pt/change-seller-of-an-vtex-sales-app-order-beta.md
@@ -15,15 +15,11 @@ legacySlug: trocar-seller-de-um-pedido-do-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Durante o processamento de um pedido no VTEX Sales App, é possível que ele seja recusado por motivos diversos, como falta de estoque de um produto no seller que atenderia o pedido. Como solução para este problema, o sistema pode escolher um seller que apresenta estoque disponível dos itens do pedido.
 
-<div class ="alert alert-warning">
-<p>Um pedido recusado no VTEX Sales App não significa que ele foi cancelado. O status recusado indica apenas que o seller indicado não será capaz de finalizar o pedido.</p>
-</div>
+>⚠️ Um pedido recusado no VTEX Sales App não significa que ele foi cancelado. O status recusado indica apenas que o seller indicado não será capaz de finalizar o pedido.
 
 Existem duas possibilidades de troca de seller:
 
@@ -57,7 +53,5 @@ Para trocar manualmente o seller de um pedido no VTEX Sales App, siga os passos
 6. Confira as informações da troca de seller e clique em `Confirmar` para finalizar.
 ![trocar seller 2 PT](https://images.ctfassets.net/alneenqid6w5/7DLR4MFL58OoL4tmQNAgJf/6ff588942b260ec8585a7fc7350dcaa3/image.png)
 
-<div class ="alert alert-info">
-<p>O cliente só será notificado da troca de seller por email caso o prazo de entrega seja diferente do que o original.</p>
-</div>
+>ℹ️ O cliente só será notificado da troca de seller por email caso o prazo de entrega seja diferente do que o original.
 
diff --git a/docs/tutorials/pt/change-seller.md b/docs/tutorials/pt/change-seller.md
index 8c6701eac..b5e4e0c7f 100644
--- a/docs/tutorials/pt/change-seller.md
+++ b/docs/tutorials/pt/change-seller.md
@@ -17,9 +17,7 @@ subcategory: 5m1qqfnmfYKsO0KiOQC8Ky
 
 O Change Seller é a funcionalidade que dá aos marketplaces autonomia para trocar o seller que vai realizar o fulfillment do pedido.
 
-<div class = "alert alert-info">
-A funcionalidade Change Seller só pode ser configurada por meio de APIs. Para mais informações, consulte a <a href="https://developers.vtex.com/vtex-rest-api/docs/change-seller">documentação para desenvolvedores Change Seller</a>.
-</div>
+>ℹ️ A funcionalidade Change Seller só pode ser configurada por meio de APIs. Para mais informações, consulte a [documentação para desenvolvedores Change Seller](https://developers.vtex.com/vtex-rest-api/docs/change-seller).
 
 A troca de seller pode ocorrer em duas situações:
 
diff --git a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
index 5bac99754..257f3aef4 100644
--- a/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
+++ b/docs/tutorials/pt/change-the-price-of-an-item-in-the-shopping-cart.md
@@ -42,7 +42,5 @@ A segurança operacional desta funcionalidade está baseada no controle do acess
 
 Assim que o pedido é fechado, o preço manual inserido precisa ser aprovado pelo administrador da loja ou por um usuário com permissão no sistema de[Autorização de Pedidos](https://help.vtex.com/pt/tutorial/how-order-authorization-works--3MBK6CmKHAuUjMBieDU0pn). 
 
-<div class = "alert alert-info">
-Uma vez validado o valor do preço manual, o pedido segue o fluxo normal de faturamento.
-</div>
+>ℹ️ Uma vez validado o valor do preço manual, o pedido segue o fluxo normal de faturamento.
 
diff --git a/docs/tutorials/pt/changing-items-from-a-complete-order.md b/docs/tutorials/pt/changing-items-from-a-complete-order.md
index 07bf49c4c..a105f42a4 100644
--- a/docs/tutorials/pt/changing-items-from-a-complete-order.md
+++ b/docs/tutorials/pt/changing-items-from-a-complete-order.md
@@ -72,6 +72,4 @@ Ao alterar ou remover itens de um pedido, o valor total do pedido é alterado. N
 
 O valor total do pedido será atualizado após a inserção da nota fiscal, e corresponde ao que é captado pelo gateway de pagamentos da VTEX. Caso um item seja devolvido, o sistema de Pagamentos da VTEX fará o estorno automaticamente ao cliente.
 
-<div class = "alert alert-info">
-A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Conectores legados não possuem suporte à funcionalidade.
-</div>
+>ℹ️ A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Conectores legados não possuem suporte à funcionalidade.
diff --git a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
index a74b35fcd..99c9079df 100644
--- a/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
+++ b/docs/tutorials/pt/changing-the-total-cost-of-the-order.md
@@ -41,6 +41,4 @@ Ao alterar ou remover itens de um pedido, o valor total do pedido é alterado. N
 
 O valor total do pedido será atualizado após a inserção da nota fiscal, e corresponde ao que é captado pelo gateway de pagamentos da VTEX. Caso um item seja devolvido, o sistema de Pagamentos da VTEX fará o estorno automaticamente ao cliente.
 
-<div class = "alert alert-info">
-A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Conectores legados não possuem suporte à funcionalidade.
-</div>
+>ℹ️ A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Conectores legados não possuem suporte à funcionalidade.
diff --git a/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md b/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
index 05c892087..a580665b5 100644
--- a/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
+++ b/docs/tutorials/pt/choosing-between-standard-account-franchise-account-or-seller-portal.md
@@ -31,9 +31,7 @@ A tabela a seguir apresenta os principais cenários de uso de cada tipo de conta
 | ---------- | ---------- | ---------- |
 | O [Seller Portal](https://help.vtex.com/pt/tutorial/seller-portal-primeiros-passos--6w1vBdRH2uuBGmUqgNQjwK) é indicado quando o marketplace VTEX deseja se conectar a um seller externo, ou seja, que não possui conta na VTEX. A funcionalidade permite o [compartilhamento de produtos](https://help.vtex.com/pt/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) do marketplace VTEX com o seller, diminuindo a fricção e simplificando o gerenciamento da operação. Cada ambiente do Seller Portal criado integra o seller a um único marketplace VTEX. | A conta padrão é indicada para lojas que desejam realizar sua operação de ecommerce de forma completa, utilizando estratégias de [comércio unificado](https://help.vtex.com/pt/tracks/estrategias-de-comercio-unificado--3WGDRRhc3vf1MJb9zGncnv). A conta padrão pode atuar como seller VTEX, marketplace VTEX e se conectar a múltiplos marketplaces e [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex). | A [conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl) é estratégica para operações que desejam expandir suas vendas com a integração de lojas físicas, com a facilidade de herdar o catálogo de uma conta padrão. A conta franquia é comumente adotada por franqueados e representantes da marca. |
 
-<div class = "alert alert-info">
-O que vai definir a melhor opção para você operar no ecossistema VTEX é o modelo e os objetivos do seu negócio. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402">Estratégias de marketplace na VTEX</a>.
-</div>
+>ℹ️ O que vai definir a melhor opção para você operar no ecossistema VTEX é o modelo e os objetivos do seu negócio. Saiba mais em [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402).
 
 A seguir, há uma série de comparativos de como Seller Portal, conta padrão e conta franquia se relacionam com módulos e funcionalidades da plataforma VTEX:
 
diff --git a/docs/tutorials/pt/collection-highlight-control.md b/docs/tutorials/pt/collection-highlight-control.md
index e536375c1..9f8a5ed2d 100644
--- a/docs/tutorials/pt/collection-highlight-control.md
+++ b/docs/tutorials/pt/collection-highlight-control.md
@@ -15,9 +15,7 @@ legacySlug: controle-de-destaque-de-colecao
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do Portal CMS Legado.</a>.</p>
-</div>
+>⚠️ existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do Portal CMS Legado.</a>.
 
 O controle `<vtex.cmc:HightLight/>` (para páginas de produto) ou `$product.HightLight` (para prateleiras) renderiza um elemento HTML com uma classe específica no contexto dos produtos que fizerem parte de uma coleção marcada com a flag __Highlight__.
 
diff --git a/docs/tutorials/pt/collection-types.md b/docs/tutorials/pt/collection-types.md
index 863401421..90a9fe553 100644
--- a/docs/tutorials/pt/collection-types.md
+++ b/docs/tutorials/pt/collection-types.md
@@ -31,9 +31,7 @@ Na VTEX, temos três possibilidades de configuração de Coleções:
 | Automática | CMS | Criada por filtros de Marca ou Categoria | Sem controle |
 | Híbrida    | CMS e módulo de Coleções Beta | Criada por filtros de Marca ou Categoria. Também é possível adicionar os produtos manualmente| Sem controle        |
 
-<div class = "alert alert-warning">
-  <p>Coleções criadas no módulo CMS e com mais de um <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L#">grupo</a> não podem ser reordenadas no novo módulo de Coleções Beta. Indicamos que você não altere a ordenação, pois pode comprometer eficiência da funcionalidade.</p>
-</div>
+>⚠️ Coleções criadas no módulo CMS e com mais de um <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L#">grupo</a> não podem ser reordenadas no novo módulo de Coleções Beta. Indicamos que você não altere a ordenação, pois pode comprometer eficiência da funcionalidade.
 
 ## Coleções manuais
 
diff --git a/docs/tutorials/pt/comprehensive-seller.md b/docs/tutorials/pt/comprehensive-seller.md
index a7d980fd5..c290b99fc 100644
--- a/docs/tutorials/pt/comprehensive-seller.md
+++ b/docs/tutorials/pt/comprehensive-seller.md
@@ -45,9 +45,7 @@ Quando ainda não há informações de localização do cliente, a heurística d
 
 Isso acontece tanto durante a navegação quanto no carrinho, com o objetivo de evitar que o cliente veja produtos de vendedores que não realizam entregas no seu endereço.
 
-<div class = "alert alert-info">
-Mesmo que durante a navegação as informações de localização do cliente tenham sido capturadas e armazenadas  no campo <code>regionId</code> da API de Sessão, a localização não é usada no carrinho. No carrinho só fica disponível para o cliente os produtos do seller principal e dos sellers abrangentes. Os produtos dos outros sellers só ficam disponíveis após o cliente informar o código postal de entrega no checkout.
-</div>
+>ℹ️ Mesmo que durante a navegação as informações de localização do cliente tenham sido capturadas e armazenadas  no campo `regionId` da API de Sessão, a localização não é usada no carrinho. No carrinho só fica disponível para o cliente os produtos do seller principal e dos sellers abrangentes. Os produtos dos outros sellers só ficam disponíveis após o cliente informar o código postal de entrega no checkout.
 
 Em casos de mais de um seller abrangente cadastrado, o checkout seleciona aquele que tem maior saldo em estoque para o item em questão, dentre todos os sellers abrangentes. Saiba mais em [Seleção de seller white label](https://help.vtex.com/pt/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa).
 
diff --git a/docs/tutorials/pt/configuring-a-seller-on-vtex-marketplace.md b/docs/tutorials/pt/configuring-a-seller-on-vtex-marketplace.md
index d41e025f2..52c40af9b 100644
--- a/docs/tutorials/pt/configuring-a-seller-on-vtex-marketplace.md
+++ b/docs/tutorials/pt/configuring-a-seller-on-vtex-marketplace.md
@@ -25,17 +25,13 @@ Este artigo orienta como configurar sua loja para se tornar seller VTEX e começ
 
 Para saber quais dados precisam ser trocados entre sellers e marketplaces, veja o artigo [Informações compartilhadas](https://help.vtex.com/pt/tutorial/informacoes-compartilhadas-entre-marketplace-e-seller-na-vtex--3o7WGiBtfnKKZ3Ddug26k3) entre marketplace e seller na VTEX. Caso sua loja deseje operar como marketplace, confira o artigo [Configurar marketplace VTEX](https://help.vtex.com/pt/tutorial/configurar-marketplace-vtex--7splyp5MqIyt2Iyz5jsNzb).
 
-<div class = "alert alert-info">
-Para começar a vender seus produtos em marketplaces, utilize o <a href="https://help.vtex.com/pt/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM">Marketplaces e integrações</a>, a funcionalidade que facilita a identificação e o contato entre marketplaces e sellers do ecossistema VTEX.
-</div>
+>ℹ️ Para começar a vender seus produtos em marketplaces, utilize o [Marketplaces e integrações](https://help.vtex.com/pt/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM), a funcionalidade que facilita a identificação e o contato entre marketplaces e sellers do ecossistema VTEX.
 
 ## Definir política comercial
 
 Na VTEX, a [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) agrupa configurações de catálogo, preços, promoções, logística, segmentação de clientes e pagamentos em um canal de venda. O seller pode integrar com o marketplace utilizando a política comercial padrão da sua loja ou definir configurações específicas para a integração, configurando uma [política comercial para marketplace](https://help.vtex.com/pt/tutorial/configurando-a-politica-comercial-para-marketplace/).
 
-<div class = "alert alert-info">
-Uma mesma política comercial pode ser usada para integrar com múltiplos marketplaces. No entanto, a <a href="https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X">contratação de política comercial adicional</a> para integrar com <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conector nativo</a>, conector certificado (parceiro) ou outras lojas VTEX é isenta de taxas.
-</div>
+>ℹ️ Uma mesma política comercial pode ser usada para integrar com múltiplos marketplaces. No entanto, a [contratação de política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X) para integrar com [conector nativo](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex), conector certificado (parceiro) ou outras lojas VTEX é isenta de taxas.
 
 Não é necessário criar uma política comercial específica para um marketplace apenas para configurar promoções, pois é possível segmentar promoções pelo [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0). Saiba mais em [Configurar promoção para marketplace](https://help.vtex.com/pt/tutorial/configurar-promocao-para-marketplace--tutorials_406).
 
@@ -45,9 +41,7 @@ A gestão do sortimento de produtos enviados para o marketplace deve ser feita a
 
 Na VTEX, o [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0) é o código que o seller VTEX cria para identificar o marketplace no qual vai vender seus produtos, sendo que cada marketplace deve corresponder a um afiliado único. É por meio do afiliado que o marketplace será notificado sobre pedidos, mudanças nas informações de um SKU e alterações de preço e estoque, por exemplo.
 
-<div class = "alert alert-info">
-A integração com <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex">conectores nativos</a> cria o código do afiliado de forma automática. No entanto, para um seller VTEX integrar com um marketplace VTEX ou externo, o seller precisa criar o ID do afiliado de forma manual.
-</div>
+>ℹ️ A integração com [conectores nativos](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-nativo-vtex) cria o código do afiliado de forma automática. No entanto, para um seller VTEX integrar com um marketplace VTEX ou externo, o seller precisa criar o ID do afiliado de forma manual.
 
 O seller deve seguir os passos do artigo [Configurar afiliado](https://help.vtex.com/pt/tutorial/como-configurar-afiliado--tutorials_187) e, uma vez que tenha criado o código identificador, deve informá-lo ao marketplace. A partir disso, o marketplace VTEX vai [adicionar o seller](https://help.vtex.com/pt/tutorial/configuring-the-seller--tutorials_392) e associá-lo a uma política comercial.
 
@@ -55,9 +49,7 @@ O seller deve seguir os passos do artigo [Configurar afiliado](https://help.vtex
 
 Após seller e marketplace estarem integrados, o envio de produtos para o marketplace não é automático, é necessário ao seller [reindexar a base](https://help.vtex.com/pt/tutorial/entendendo-o-funcionamento-da-indexacao). Esse processo prepara os dados dos SKUs e produtos e envia para o marketplace informações gerais sobre catálogo, preço e estoque. 
 
-<div class = "alert alert-info">
-Somente o <a href="https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA">usuário Titular (owner)</a> tem permissão para reindexar a base de uma loja VTEX. Durante o período de reindexação, que é variável, os produtos entram numa fila para atualização de dados, mas seguem disponíveis para venda no site da loja.
-</div>
+>ℹ️ Somente o [usuário Titular (owner)](https://help.vtex.com/pt/tracks/contas-e-permissoes--5PxyAgZrtiYlaYZBTlhJ2A/56Bd0KpwbvAji1aFs94xdA) tem permissão para reindexar a base de uma loja VTEX. Durante o período de reindexação, que é variável, os produtos entram numa fila para atualização de dados, mas seguem disponíveis para venda no site da loja.
 
 Para reindexar a base, copie o endereço abaixo no seu navegador, substituindo `{nomedaloja}` pelo nome da sua loja:
 
diff --git a/docs/tutorials/pt/configuring-access-without-www.md b/docs/tutorials/pt/configuring-access-without-www.md
index 92beae5bb..3cf9c9da3 100644
--- a/docs/tutorials/pt/configuring-access-without-www.md
+++ b/docs/tutorials/pt/configuring-access-without-www.md
@@ -31,9 +31,7 @@ O domínio principal da sua loja precisa conter subdomínio, que pode ou não se
 - `www.minhaloja.com` - Domínio principal válido.
 - `loja.minhamarca.com` - Domínio principal válido.
 
-<div class = "alert alert-info">
-  Saiba mais sobre como <a href="https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450">configurar o domínio principal da sua loja</a>.
-</div>
+>ℹ️ Saiba mais sobre como [configurar o domínio principal da sua loja](https://help.vtex.com/pt/tutorial/configurando-dominios-no-gerenciamento-da-conta--tutorials_2450).
 
 Este redirecionamento pode ser feito de inúmeras formas, sendo o uso do `htaccess` no servidor uma das mais conhecidas, mas bastante técnica e que depende de outros fatores.
 
diff --git a/docs/tutorials/pt/configuring-banners.md b/docs/tutorials/pt/configuring-banners.md
index ce9fe2a57..1c7d814fb 100644
--- a/docs/tutorials/pt/configuring-banners.md
+++ b/docs/tutorials/pt/configuring-banners.md
@@ -25,9 +25,7 @@ Para configurar um banner, siga os seguintes passos:
 
 Depois de realizar as configurações do banner, você deve adicioná-lo a uma página da sua loja. Para isso, siga os passos do guia [Banner](https://developers.vtex.com/vtex-developer-docs/docs/vtex-search-banner).
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
-</div>
+>ℹ️ Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo [VTEX Intelligent Search: configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#banners) para saber mais.
 
 ![banner-form-pt](https://images.ctfassets.net/alneenqid6w5/4eY6elSTbPcVvjQHuxOhdu/4be57613a6396be3b68aeee7084eba3a/image.png)
 
diff --git a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
index 426cc3af5..1eca938d7 100644
--- a/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
+++ b/docs/tutorials/pt/configuring-bulk-data-import-for-organizations-and-cost-centers.md
@@ -25,17 +25,13 @@ Veja abaixo como realizar a importação em massa de dados na plataforma VTEX:
 
 2. Na aba Organizações, clique no botão **Novo**, e selecione Importar em massa. Clique no botão **Enviar** e selecione seu arquivo **XLSX**, ou arraste e solte o arquivo na área tracejada. O arquivo importado deve ser menor que 50 MB.
 
-<div class = "alert alert-info">
-Caso necessário, baixe um arquivo modelo clicando em VTEX file template no rodapé da janela de importação e preencha os dados de importação.
-</div>
+>ℹ️ Caso necessário, baixe um arquivo modelo clicando em VTEX file template no rodapé da janela de importação e preencha os dados de importação.
 
 <ol start="3">
 	<li>Após a plataforma realizar uma verificação no arquivo importado e não indicar erros, clique em Importar.</li>
 </ol>
 
-<div class = "alert alert-info">
-  Caso a plataforma encontre algum tipo de erro, verifique a seção <b>Erros de importação</b>.
-</div>
+>ℹ️ Caso a plataforma encontre algum tipo de erro, verifique a seção **Erros de importação**.
 
 <ol start="4">
 	<li>Após o processo de importação ser concluído, você pode clicar em  Exibir detalhes de importação para acessar o relatório de importação.</li>
@@ -55,9 +51,7 @@ Para obter uma visão detalhada dos problemas encontrados, siga os passos abaixo
 
 3. Após corrigir os erros, você pode reiniciar o processo de importação, fazendo upload do arquivo corrigido novamente.
 
-<div class = "alert alert-info">
- Certifique-se de carregar apenas o arquivo contendo as correções dos erros previamente identificados para garantir uma importação bem-sucedida.
-</div>
+>ℹ️ Certifique-se de carregar apenas o arquivo contendo as correções dos erros previamente identificados para garantir uma importação bem-sucedida.
 
 ![Bulk import - PT](https://images.ctfassets.net/alneenqid6w5/xXZgwvWu4ngsY9D9hjQsO/4ebe7b4b5b1c0d5b2d7feb36134d9a5e/Bulk_import_vers_o_error-gif-PT.gif)
 
diff --git a/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md b/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md
index 540ba19dc..2607e8ce2 100644
--- a/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md
+++ b/docs/tutorials/pt/configuring-dns-pointing-to-vtex.md
@@ -68,16 +68,14 @@ Outra alternativa, embora não recomendada, seria não incluir registros CAA no
 
 Para facilitar o trabalho de criar/verificar seus registros CAA, você pode usar o [CAA Record Helper by SSLMate](https://sslmate.com/caa/). O programa [DiG](https://www.hostinger.com/tutorials/how-to-use-the-dig-command-in-linux/) também pode ajudar na verificação dos registros, através do comando `dig domain.com CAA` - um status `SERVFAIL` pode indicar não-conformidade do seu servidor DNS.
 
-<div class = "alert alert-info">
-Saiba mais:
-<p>
-<ul>
-<li><a href="https://sslmate.com/caa/">CAA Record Helper by SSLMate</a></li>
-<li><a href="https://letsencrypt.org/docs/caa/">Let's Encrypt: Certificate Authority Authorization (CAA)</a></li>
-<li><a href="https://sslmate.com/caa/about">SSL Mate: About CAA</a></li>
-</ul>
-</p>
-</div>
+>ℹ️ Saiba mais:
+>
+> *[CAA Record Helper by SSLMate](https://sslmate.com/caa/)
+>
+> *[Let's Encrypt: Certificate Authority Authorization (CAA)](https://letsencrypt.org/docs/caa/)
+>
+> *[SSL Mate: About CAA](https://sslmate.com/caa/about)
+> 
 
 ## Apontamento de DNS
 
@@ -93,9 +91,7 @@ Se sua frente de loja é feita com [CMS IO](https://help.vtex.com/pt/tracks/cms-
 
 Após receber a confirmação do apontamento interno, você deverá realizar o [apontamento comum de DNS](#apontamento-comum-de-dns) em até cinco dias. Do contrário o apontamento interno será excluído e você precisará refazer esta solicitação.
 
-<div class = "alert alert-info">
-Saiba mais sobre <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live">Go live com Store Framework</a> ou <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io">Migração do CMS legado para Store Framework</a>.
-</div>
+>ℹ️ Saiba mais sobre [Go live com Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-go-live) ou [Migração do CMS legado para Store Framework](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-migrating-storefront-from-legacy-to-io).
 
 ### Apontamento comum de DNS
 
diff --git a/docs/tutorials/pt/configuring-domains-in-account-management.md b/docs/tutorials/pt/configuring-domains-in-account-management.md
index 7d09bb00d..e2f2fcde7 100644
--- a/docs/tutorials/pt/configuring-domains-in-account-management.md
+++ b/docs/tutorials/pt/configuring-domains-in-account-management.md
@@ -33,9 +33,7 @@ Qualquer domínio registrado desta forma precisa conter subdomínio, que pode ou
 - `www.minhaloja.com` - Domínio válido.
 - `loja.minhamarca.com` - Domínio válido.
 
-<div class = "alert alert-info">
-  Saiba mais sobre como <a href="https://help.vtex.com/pt/tutorial/configuring-access-without-www--tutorials_4278">configurar acesso sem www</a>.
-</div>
+>ℹ️ Saiba mais sobre como [configurar acesso sem www](https://help.vtex.com/pt/tutorial/configuring-access-without-www--tutorials_4278).
 
 ## Cadastrar um novo domínio
 
diff --git a/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md b/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md
index 97b740b20..f34d70e11 100644
--- a/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md
+++ b/docs/tutorials/pt/configuring-payment-conditions-for-b2b.md
@@ -19,9 +19,7 @@ Em uma operação B2B, as [condições de pagamento](https://help.vtex.com/pt/tu
 
 As opções de pagamento disponíveis podem ser personalizadas por centro de custo pelo usuário com perfil de administrador da organização. 
 
-<div class = "alert alert-info">
-Quando você configura uma condição de pagamento no módulo Pagamentos, ela aparece como um meio de pagamento na lista <b>Disponível</b>, dentro da aba <b>Condições de Pagamento</b>. Para visualizar essa lista, clique no nome da organização. Os métodos de pagamento listados são aqueles já atribuídos à organização.
-</div>
+>ℹ️ Quando você configura uma condição de pagamento no módulo Pagamentos, ela aparece como um meio de pagamento na lista **Disponível**, dentro da aba **Condições de Pagamento**. Para visualizar essa lista, clique no nome da organização. Os métodos de pagamento listados são aqueles já atribuídos à organização.
 
 ## Associar condições de pagamento à organização
 Para associar uma condição de pagamento a uma organização compradora, siga as instruções abaixo:
diff --git a/docs/tutorials/pt/configuring-price-divergence-rule.md b/docs/tutorials/pt/configuring-price-divergence-rule.md
index 1a7735443..693ac3b88 100644
--- a/docs/tutorials/pt/configuring-price-divergence-rule.md
+++ b/docs/tutorials/pt/configuring-price-divergence-rule.md
@@ -33,9 +33,7 @@ Quando um seller está integrado a um conector nativo, como o Mercado Livre ou a
 
 A [regra de Divergência de valores](https://help.vtex.com/pt/tutorial/regra-de-divergencia-de-valores--6RlFLhD1rIRRshl83KnCjW) é composta de uma ou múltiplas regras de autorização de pedidos, que correspondem a intervalos entre 0% a 100% do preço do pedido. A configuração é feita de forma que cada intervalo é associado a uma ação automática de processamento.
 
-<div class = "alert alert-info">
-Para criar uma regra de Divergência de valores, o usuário precisa ter o <a href="https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> de Admin Super (Owner) ou OMS Full. Garanta a segurança na gestão das suas operações e confira as <a href="https://help.vtex.com/pt/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM">melhores práticas de segurança para gestão de usuários</a>.
-</div>
+>ℹ️ Para criar uma regra de Divergência de valores, o usuário precisa ter o [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) de Admin Super (Owner) ou OMS Full. Garanta a segurança na gestão das suas operações e confira as [melhores práticas de segurança para gestão de usuários](https://help.vtex.com/pt/faq/metodos-de-seguranca-para-criacao-de-perfis-de-usuarios-em-uma-loja--15YDwC9jGgqWi3rvcDaiGM).
 
 Para criar uma regra de Divergência de valores, siga os passos abaixo:
 
@@ -79,9 +77,7 @@ A edição da regra de Divergência de valores pode ser feita a qualquer momento
 
 Na página de edição de regras, existe a opção de deletar a regra de Divergência de valores, clicando em **EXCLUIR REGRAS**. Isso faz com que todas as regras de autorização configuradas sejam permanentemente deletadas.
 
-<div class = "alert alert-info">
-Caso você exclua a regra de Divergência de valores, essa ação não pode ser desfeita. Para voltar a valer, será necessário configurá-la novamente. Isso se aplica também às regras de autorização que compõem a regra de Divergência de valores.
-</div>
+>ℹ️ Caso você exclua a regra de Divergência de valores, essa ação não pode ser desfeita. Para voltar a valer, será necessário configurá-la novamente. Isso se aplica também às regras de autorização que compõem a regra de Divergência de valores.
 
 Na mesma página, na aba **Todas**, é possível identificar a lista de todas as regras de autorização de pedidos criadas. Para excluir uma regra de autorização, você pode clicar no botão **EXCLUIR REGRA** ao lado da regra que deseja deletar.
 
diff --git a/docs/tutorials/pt/configuring-promotions-for-marketplaces.md b/docs/tutorials/pt/configuring-promotions-for-marketplaces.md
index 19ac0f80f..8359d2b7f 100644
--- a/docs/tutorials/pt/configuring-promotions-for-marketplaces.md
+++ b/docs/tutorials/pt/configuring-promotions-for-marketplaces.md
@@ -50,9 +50,7 @@ Para este tipo de promoção, é importante ter em mente as seguintes informaç
 
 Existem diferenças entre as configurações disponíveis para marketplaces VTEX e para marketplaces externos. Veja na tabela abaixo quais funcionalidades se aplicam a cada caso.
 
-<div class = "alert alert-warning">
-  <p>No caso de integrações externas, as configurações são únicas de cada marketplace, e estes decidem quais funcionalidades vão utilizar.</p>
-</div>
+>⚠️ No caso de integrações externas, as configurações são únicas de cada marketplace, e estes decidem quais funcionalidades vão utilizar.
 
 | Nome  | Descrição      | Disponível para marketplace VTEX? | Disponível para marketplace externo? |
 | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | ------------------------------------ |
@@ -135,6 +133,4 @@ Se necessário, é possível segmentar promoções para marketplaces específico
 3. Na seção **Política Comercial**, selecione as opções **Iguais a** e **Entregue por mim (Lojas de terceiros)**.
 4. Clique em `Salvar`.
 
-<div class = "alert alert-warning">
-  <p>Uma vez que você crie a promoção, lembre-se de <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar os produtos afetados</a> no inicio e fim das promoções. Dessa forma, os seus produtos terão os preços atualizados.</p>
-</div>
+>⚠️ Uma vez que você crie a promoção, lembre-se de <a href = "https://help.vtex.com/pt/tutorial/entendendo-a-manutencao-da-base-de-dados--34P9LGs7BCIQK6acQom802">reindexar os produtos afetados</a> no inicio e fim das promoções. Dessa forma, os seus produtos terão os preços atualizados.
diff --git a/docs/tutorials/pt/configuring-xml.md b/docs/tutorials/pt/configuring-xml.md
index 0be7c1199..613e07b25 100644
--- a/docs/tutorials/pt/configuring-xml.md
+++ b/docs/tutorials/pt/configuring-xml.md
@@ -36,9 +36,7 @@ Veja a seguir alguns exemplos de parceiros que integram com o XML da VTEX:
 - UOL Dynad
 - Zanox
 
-<div class = "alert alert-info">
-  <p>Alterações no XML levam em média duas horas para serem atualizadas.</p>
-</div>
+>ℹ️ Alterações no XML levam em média duas horas para serem atualizadas.
 
 ## Novo XML
 
diff --git a/docs/tutorials/pt/creating-a-more-for-less-promotion.md b/docs/tutorials/pt/creating-a-more-for-less-promotion.md
index adcdea7a7..dbdee87aa 100644
--- a/docs/tutorials/pt/creating-a-more-for-less-promotion.md
+++ b/docs/tutorials/pt/creating-a-more-for-less-promotion.md
@@ -60,9 +60,7 @@ Nesta seção, é possível definir para quais sellers a promoção será aplica
 
 Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
 
-<div class = "alert alert-warning">
-  <p>Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
-</div>
+>⚠️ Não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.
 
 ![Restringir - PT](https://images.ctfassets.net/alneenqid6w5/7KJhtOylpPsj0g5Q1lF2T0/6a43d51af7293cbfee1e0f9a2de2428a/Restringir_-_PT.png)
 
@@ -87,9 +85,7 @@ Esta seção define os produtos, a quantidade e o desconto que serão afetados p
     - **SKUs:** nomes ou IDs dos SKUs que terão o desconto aplicado. Você pode fazer a importação de uma lista de SKUs clicando no botão `Selecione um arquivo .txt`. O arquivo de texto (.txt) deve ter cada SKU ID em uma linha diferente. Você também pode baixar a lista de SKUs adicionada no campo clicando no botão `Download da lista de SKUs`.
 - **Coleções:** seleção de coleções que serão incluídas na promoção. A promoção será aplicada somente aos produtos que estejam nas coleções cadastradas neste campo. Para isso, digite o nome da coleção de produtos que deseja oferecer esse tipo de desconto. É possível selecionar mais de uma coleção.
 
-<div class = "alert alert-info">
-  <p>Se não forem informados produtos por coleção ou por SKU, a plataforma não permitirá a criação da promoção.</p>
-</div>
+>ℹ️ Se não forem informados produtos por coleção ou por SKU, a plataforma não permitirá a criação da promoção.
 
 - **E leva `quantidade` desses produtos:** quantidade de unidades do produto que receberá o desconto configurado. Campo de preenchimento obrigatório.
     - **Com desconto de:** o cliente levará a quantidade selecionada de produtos com um desconto percentual definido no campo.
@@ -128,9 +124,7 @@ Nesta seção, detalharemos as condições em que você deve aplicar para que um
 - **Criar cupom a partir das UTMs acima:** cria um cupom a partir das UTMs cadastradas para dar ao cliente acesso à essa promoção apenas com o código do cupom.
 - **Meio de pagamento:** permite escolher se a promoção será aplicada em um ou mais tipos de meios de pagamento selecionados.
 
- <div class = "alert alert-info">
-  <p> Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
- </div>
+ >ℹ️ Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 ![Condições de promoção - PT](https://images.ctfassets.net/alneenqid6w5/1mPsbqBbsHGXaSKeoFL1vY/d5a51e69868ee890a701dba2dfe8a1f2/Condi__es_de_promo__o_-_PT.png)
 
diff --git a/docs/tutorials/pt/creating-a-product-collection.md b/docs/tutorials/pt/creating-a-product-collection.md
index e0fff5aae..2e002951e 100644
--- a/docs/tutorials/pt/creating-a-product-collection.md
+++ b/docs/tutorials/pt/creating-a-product-collection.md
@@ -15,9 +15,7 @@ legacySlug: criando-colecao-de-produtos
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <p>Existem duas formas de configurar coleções, por meio do Portal CMS Legado ou utilizando o módulo de <a href="https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye">Coleções Beta</a>. Este artigo refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do Portal CMS Legado</a>.</p>
-</div>
+>⚠️ Existem duas formas de configurar coleções, por meio do Portal CMS Legado ou utilizando o módulo de [Coleções Beta](https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye). Este artigo refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do Portal CMS Legado</a>.
 
 Para criar uma coleção, siga as instruções abaixo:
 
diff --git a/docs/tutorials/pt/creating-a-specification-group-in-a-category.md b/docs/tutorials/pt/creating-a-specification-group-in-a-category.md
index 0c2c65c71..99d941032 100644
--- a/docs/tutorials/pt/creating-a-specification-group-in-a-category.md
+++ b/docs/tutorials/pt/creating-a-specification-group-in-a-category.md
@@ -23,9 +23,7 @@ Neste artigo, explicamos como funciona a herança de especificações e o cadast
 - [Herança de especificações](#heranca-de-especificacoes)
 - [Passo a passo no Admin VTEX](#passo-a-passo-no-admin-vtex)
 
-<div class = "alert alert-info">
-  <p>Para criar um grupo de especificações utilizando a <strong>Catalog API</strong>, siga o guia para desenvolvedores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a>.</p>
-</div>
+>ℹ️ Para criar um grupo de especificações utilizando a **Catalog API**, siga o guia para desenvolvedores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification).
 
 ## Herança de especificações
 
diff --git a/docs/tutorials/pt/creating-collections-beta.md b/docs/tutorials/pt/creating-collections-beta.md
index 3b2b61ac3..eff5991bd 100644
--- a/docs/tutorials/pt/creating-collections-beta.md
+++ b/docs/tutorials/pt/creating-collections-beta.md
@@ -15,10 +15,9 @@ legacySlug: cadastrar-colecoes-beta
 subcategory: 3aExYJkji3NIu9Ks8bxbWx
 ---
 
-<div class = "alert alert-info">
-  <p>Existem duas formas de configurar coleções: por meio do <b>Portal CMS Legado</b> ou utilizando o módulo de <b>Coleções (Beta)</b>. Este artigo refere-se à configuração de coleções por meio do módulo de <b>Coleções (Beta)</b>.</p>
-  <p>Essa funcionalidade está em estágio Beta e disponível para ambientes a partir do Admin v3. Em caso de dúvidas <a href="https://support.vtex.com/hc/pt-br/requests">entre em contato com nosso Suporte</a>.</p>
-</div>
+>ℹ️ Existem duas formas de configurar coleções: por meio do **Portal CMS Legado** ou utilizando o módulo de **Coleções (Beta)**. Este artigo refere-se à configuração de coleções por meio do módulo de **Coleções (Beta)**.
+>
+> Essa funcionalidade está em estágio Beta e disponível para ambientes a partir do Admin v3. Em caso de dúvidas [entre em contato com nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 O módulo de __Coleções (Beta)__ permite criar e gerenciar coleções de forma prática e rápida.
 
@@ -47,9 +46,7 @@ Siga o passo a passo abaixo para cadastrar uma nova coleção:
 5. Clique em `Criar` para atualizar as informações preenchidas no formulário.
 6. Em seguida, [selecione os produtos](https://help.vtex.com/pt/tutorial/cadastrar-colecoes-beta--yJBHqNMViOAnnnq4fyOye#selecao-de-produtos) que farão parte da coleção.
 
-<div class = "alert alert-info">
-  <p>É importante ressaltar que as coleções criadas neste módulo não são automaticamente alteradas. Coleções automáticas - feitas por seleção de filtros - não são possíveis de configurar no módulo.</p>
-</div>
+>ℹ️ É importante ressaltar que as coleções criadas neste módulo não são automaticamente alteradas. Coleções automáticas - feitas por seleção de filtros - não são possíveis de configurar no módulo.
 
 ### Campos de cadastro de coleção
 
@@ -106,15 +103,13 @@ Caso você deseje realizar uma inclusão massiva, aplique pelo menos um dos filt
 
 ![Coleções Adicionar Todos - PT](https://images.ctfassets.net/alneenqid6w5/7Bo9F9fU4sGW4FqBTBquD8/20fa966d9f2bb7339ad12140fc722d2b/Screenshot_22.png)
 
-<div class = "alert alert-danger">
-  <p>Não adicione massivamente uma quantidade acima de 100 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.</p>
-</div>
+>❗ Não adicione massivamente uma quantidade acima de 100 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.
 
 #### Por planilha
 
 Você também pode adicionar os itens em uma coleção por planilha.
 
-<div class = "alert alert-info">O limite máximo para importação e exportação é de 10 mil SKUs por operação.</div>
+>ℹ️ O limite máximo para importação e exportação é de 10 mil SKUs por operação.
 
 Para isso, siga os passos a seguir:
 
@@ -125,9 +120,7 @@ Para isso, siga os passos a seguir:
   5. Depois de preencher a planilha, salve as alterações e importe o documento no Admin. Você pode soltar o arquivo na área indicada ou clicar em **Escolha um arquivo**. São aceitos arquivos em formato CSV ou XML. Em caso de um arquivo CSV, use `,` para delimitar os campos.
   6. Para finalizar, clique em `Importar`.
 
-<div class = "alert alert-warning">
-  <p>A planilha pode conter até 10 mil linhas. Porém, em lojas com um catálogo extenso, recomendamos incluir no máximo 50 linhas por vez para garantir o funcionamento correto da importação.</p>
-</div>
+>⚠️ A planilha pode conter até 10 mil linhas. Porém, em lojas com um catálogo extenso, recomendamos incluir no máximo 50 linhas por vez para garantir o funcionamento correto da importação.
 
 ### Remoção de produtos
 
@@ -145,9 +138,7 @@ Caso você deseje realizar uma remoção massiva, aplique um dos filtros e cliqu
 
 Você também pode clicar no botão <i class="far fa-check-circle" title = "check em círculo"></i> (**Produtos nesta coleção**) na barra superior e depois selecionar `Remover Todos`.
 
-<div class = "alert alert-danger">
-  <p>Não remova massivamente uma quantidade acima de 150 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.</p>
-</div>
+>❗ Não remova massivamente uma quantidade acima de 150 mil produtos. Isso pode comprometer a indexação do Catálogo e o funcionamento da sua loja.
 
 #### Por planilha
 
@@ -168,9 +159,7 @@ Para alterar a ordem da sua coleção, siga os passos abaixo:
 
   a. Clique no ícone <i class="fas fa-grip-vertical" title="arrastar vertical"></i>, arraste o item e solte para a posição desejada.
 
-  <div class = "alert alert-info">
-    <p>Não é possível utilizar essa opção caso um filtro esteja ativo.</p>
-  </div>
+  >ℹ️ Não é possível utilizar essa opção caso um filtro esteja ativo.
 
   b. Selecione a caixa dos produtos que deseja alterar e clique em `Mover de Posição`. Indique o número da nova posição e, para finalizar, clique em `Mover`. Aqui é possível reordenar massivamente os itens da lista.
 
diff --git a/docs/tutorials/pt/creating-landing-pages-per-binding.md b/docs/tutorials/pt/creating-landing-pages-per-binding.md
index 9200ac398..9478d00f4 100644
--- a/docs/tutorials/pt/creating-landing-pages-per-binding.md
+++ b/docs/tutorials/pt/creating-landing-pages-per-binding.md
@@ -33,16 +33,12 @@ No Admin, é possível criar *landing pages* customizadas por [*binding*](https:
 - `Descrição` - Resumo da nova página a ser exibido nas páginas de resultados dos mecanismos de busca.
 - `Palavras-chave` - Tópicos que definem o conteúdo da página, ajudando a distribuí-la aos usuários interessados que navegam nas páginas de resultados dos mecanismos de busca.
 
-  <div class = "alert alert-info">
-Todos os cinco campos acima impactam diretamente os acessos à loja e o posicionamento da mesma nas páginas de resultados dos mecanismos de busca. Antes de preencher os metadados da página, esteja ciente das práticas recomendadas de <i>SEO</i>.
-</div>
+  >ℹ️ Todos os cinco campos acima impactam diretamente os acessos à loja e o posicionamento da mesma nas páginas de resultados dos mecanismos de busca. Antes de preencher os metadados da página, esteja ciente das práticas recomendadas de <i>SEO</i>.
 
 5. Escolha um *template* para ser exibido em sua nova *landing page* no campo `Padrão`.
 6. Se você deseja criar um *template* condicional, clique no botão `Adicionar template condicional` e preencha os campos de acordo com as condições desejadas.
 
-  <div class = "alert alert-warning">
-Observe que o <i>template</i> de condição só será exibido quando uma <i>ou</i> todas as condições predefinidas forem realizadas na interface.
-</div>
+  >⚠️ Observe que o <i>template</i> de condição só será exibido quando uma <i>ou</i> todas as condições predefinidas forem realizadas na interface.
 
 7. Salve suas alterações.
 
diff --git a/docs/tutorials/pt/creating-landing-pages.md b/docs/tutorials/pt/creating-landing-pages.md
index 1650851aa..2f2a4695a 100644
--- a/docs/tutorials/pt/creating-landing-pages.md
+++ b/docs/tutorials/pt/creating-landing-pages.md
@@ -39,16 +39,10 @@ No Admin, você pode criar landing pages personalizadas, como páginas para ofer
 
 >⚠️ Para evitar conflitos e garantir a integridade do sistema, não é permitida a alteração da URL de uma rota já existente. Caso precise modificar uma URL, recomenda-se criar uma nova página com o caminho desejado e desativar a antiga, se necessário.
 
-<div class = "alert alert-info">
-<p>Os cinco campos acima têm um impacto direto nos acessos à loja e em seu posicionamento nos resultados dos mecanismos de busca. Ao preencher os metadados da página, considere as melhores práticas de SEO.
-</p>
-</div>
+>ℹ️ Os cinco campos acima têm um impacto direto nos acessos à loja e em seu posicionamento nos resultados dos mecanismos de busca. Ao preencher os metadados da página, considere as melhores práticas de SEO.
 
 4.Escolha um modelo para a sua nova landing page no menu **Templates**.
 
-<div class = "alert alert-info">
-  <p>Se você deseja criar um template condicional, clique em <strong>Adicionar template condicional</strong> e preencha os campos de acordo com as condições desejadas. Tenha em mente que o modelo condicional só será exibido quando uma ou todas as condições pré-definidas coincidirem na interface.
-</p>
-</div>
+>ℹ️ Se você deseja criar um template condicional, clique em **Adicionar template condicional** e preencha os campos de acordo com as condições desejadas. Tenha em mente que o modelo condicional só será exibido quando uma ou todas as condições pré-definidas coincidirem na interface.
 
 5.Salve as alterações.
diff --git a/docs/tutorials/pt/creating-pickup-points.md b/docs/tutorials/pt/creating-pickup-points.md
index 1fdea9359..f822953f9 100644
--- a/docs/tutorials/pt/creating-pickup-points.md
+++ b/docs/tutorials/pt/creating-pickup-points.md
@@ -52,9 +52,7 @@ Selecione <i class="fas fa-toggle-on"></i> para que o ponto de retirada fique at
 * Para editar alguma informação do endereço, clique em `Editar`. 
 * Para adicionar um endereço diferente, clique em `Limpar` e refaça a busca.
 
-<div class = "alert alert-info">
-As informações de endereço e a localização no mapa serão exibidas no checkout. 
-</div>
+>ℹ️ As informações de endereço e a localização no mapa serão exibidas no checkout.
 
 #### Informações adicionais
 
@@ -66,7 +64,7 @@ As informações de endereço e a localização no mapa serão exibidas no check
 * **Dias da semana:** 
     1. Marque com <i class="far fa-check-square"></i> os dias em que seu ponto de retirada estará disponível para seus clientes retirarem pedidos. 
     2. Selecione também os horários de funcionamento do ponto de retirada para cada dia.
-    <div class = "alert alert-info">Caso esse campo não seja preenchido, a plataforma considera o horário de funcionamento de 24 horas por dia.</div>
+    >ℹ️ Caso esse campo não seja preenchido, a plataforma considera o horário de funcionamento de 24 horas por dia.
 * **Exceções ou feriados:** para adicionar dias específicos em que o ponto de retirada não funcionará:
     3. Clique em `Adicionar exceção`;
     4. Preencha **Dia** e **Horário;**
@@ -78,13 +76,11 @@ As informações de endereço e a localização no mapa serão exibidas no check
 
 É possível cadastrar pontos de retirada via importação de planilha (arquivo XLS). Dessa forma, você cadastra mais de um ponto de retirada de uma única vez.
 
-<div class = "alert alert-info">
-O arquivo XLS não deve ultrapassar 10MB (aproximadamente 50 mil pontos de retirada). Se preciso, cadastre mais de uma planilha. 
-</div>
+>ℹ️ O arquivo XLS não deve ultrapassar 10MB (aproximadamente 50 mil pontos de retirada). Se preciso, cadastre mais de uma planilha.
 
 1. No Admin VTEX, acesse **Envio > Pontos de retirada**, ou digite *Pontos de retirada* na barra de busca no topo da página.    
 2. Clique em <i class="fas fa-upload"></i> `Subir um XLS`.
-3. Baixe o modelo e preencha os [campos da planilha](#campos-da-planilha).<div class = "alert alert-info">Note que a planilha modelo já vem com valores de exemplo, que devem ser substituídos pelos dados dos pontos de retirada da sua loja.</div>
+3. Baixe o modelo e preencha os [campos da planilha](#campos-da-planilha).>ℹ️ Note que a planilha modelo já vem com valores de exemplo, que devem ser substituídos pelos dados dos pontos de retirada da sua loja.
 4. Ao final do upload, clique em `OK`. Os pontos de retirada já estão cadastrados. 
 
 ### Campos da planilha
diff --git a/docs/tutorials/pt/creating-service-for-a-sku.md b/docs/tutorials/pt/creating-service-for-a-sku.md
index a2a2d0874..bf08a3319 100644
--- a/docs/tutorials/pt/creating-service-for-a-sku.md
+++ b/docs/tutorials/pt/creating-service-for-a-sku.md
@@ -76,9 +76,7 @@ Para vincular um serviço a um SKU, siga os passos abaixo:
 5. Clique em `Exportar`.
 6. Salve a planilha de formato CSV que será exportada no seu computador.
 7. Preencha os [campos da planilha](#campos-da-planilha). Mantenha o formato CSV do arquivo quando salvar as alterações.
-<div class = "alert alert-warning">
-  <p>O tamanho do arquivo da planilha não poderá exceder 4Mb (4096KB).</p>
-</div>
+>⚠️ O tamanho do arquivo da planilha não poderá exceder 4Mb (4096KB).
 8. Clique na barra ao lado do botão `Select`, destacada abaixo.
   ![Anexos - PT](https://images.ctfassets.net/alneenqid6w5/76FSnqnRMroOc0Ex2knz1Z/8581377e9a02b411cd383a85be145983/image.png)
 9. Selecione a planilha CSV atualizada.
@@ -104,7 +102,5 @@ Manipule a planilha com cautela, sempre verificando se as informações contidas
 - **Custo:** o custo do serviço para a loja.
 - **Ativo:** status do serviço. Preencha com `1` para manter o serviço ativo ou com `0` para manter inativo.
 
-<div class = "alert alert-warning">
-  <p>A inclusão de uma nova planilha não irá substituir os serviços já vinculados ao SKU. Para desvincular um serviço, utilize o endpoint <a href ="https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/skuservice/-skuServiceId-">Dissociate SKU Service</a>.</p>
-</div>
+>⚠️ A inclusão de uma nova planilha não irá substituir os serviços já vinculados ao SKU. Para desvincular um serviço, utilize o endpoint <a href ="https://developers.vtex.com/docs/api-reference/catalog-api#delete-/api/catalog/pvt/skuservice/-skuServiceId-">Dissociate SKU Service</a>.
 
diff --git a/docs/tutorials/pt/creating-synonyms.md b/docs/tutorials/pt/creating-synonyms.md
index e9d1b853f..babea1338 100644
--- a/docs/tutorials/pt/creating-synonyms.md
+++ b/docs/tutorials/pt/creating-synonyms.md
@@ -15,7 +15,7 @@ legacySlug: configurar-sinonimos
 subcategory: BBzMtJan1UTxC9QZODnlN
 ---
 
-<div class = "alert alert-info"> Para relacionar palavras ao produto, é recomendada a utilização da configuração de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV?&utm_source=autocomplete">Sinônimos</a> ao invés das <a href="https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palavras Substitutas</a>, uma vez que os sinônimos possibilitam uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.</div>
+>ℹ️ Para relacionar palavras ao produto, é recomendada a utilização da configuração de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV?&utm_source=autocomplete) ao invés das [Palavras Substitutas](https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete), uma vez que os sinônimos possibilitam uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso [Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Existem duas formas de configurar sinônimos no Admin VTEX: [individualmente](#criar-sinonimos-individualmente) ou por [importação de uma planilha em formato CSV](#importar-csv). Se você precisa cadastrar sinônimos em massa, recomendamos utilizar a planilha. Confira as instruções para cada forma de configuração nas seções a seguir.
 
@@ -41,9 +41,7 @@ Siga o passo a passo para configurar sinônimos individualmente no Admin VTEX:
 
 A alteração pode demorar até duas horas para ser aplicada.
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo <a href="https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos">VTEX Intelligent Search: configurações Multi-idioma (Beta)</a> para saber mais.</p>
-</div>
+>ℹ️ Essa funcionalidade está disponível no VTEX Intelligent Search Multi-idioma. Leia o nosso artigo [VTEX Intelligent Search: configurações Multi-idioma (Beta)](https://help.vtex.com/pt/tutorial/vtex-intelligent-search-configuracoes-multi-idioma-beta--2WahlTESLXIJ9XBdQMdTYO#sinonimos) para saber mais.
 
 ## Importar CSV
 
diff --git a/docs/tutorials/pt/data-subject-rights.md b/docs/tutorials/pt/data-subject-rights.md
index 0034752f6..fee14f528 100644
--- a/docs/tutorials/pt/data-subject-rights.md
+++ b/docs/tutorials/pt/data-subject-rights.md
@@ -57,9 +57,7 @@ Para exportar dados do Master Data v1 pelo painel Admin, siga estes passos:
 
 Repita este passo a passo para as entidades de dados de clientes (**CL**), endereços (**AD**) e quaisquer outra que tenha configurado para receber informações pessoais de seus clientes.
 
-<div class = "alert alert-info">
-Saiba mais sobre como <a href="https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters">filtrar dados</a> e <a href="https://help.vtex.com/pt/tutorial/exporting-data--tutorials_1125">exportar dados</a>. na interface do Master Data v1.
-</div>
+>ℹ️ Saiba mais sobre como [filtrar dados](https://help.vtex.com/tutorial/filtering-data-on-master-data--tutorials_778#how-to-use-filters) e [exportar dados](https://help.vtex.com/pt/tutorial/exporting-data--tutorials_1125). na interface do Master Data v1.
 
 #### Master Data v2
 
@@ -87,9 +85,7 @@ Seus clientes podem exercer seu direito de consentimento e de retificação de d
 - Visualizar e editar seus endereços cadastrados.
 - Visualizar e editar seus meios de pagamento registrados.
 
-<div class = "alert alert-info">
-Saiba mais sobre a página <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ Saiba mais sobre a página [Minha Conta](https://help.vtex.com/pt/tutorial/como-funciona-a-minha-conta--2BQ3GiqhqGJTXsWVuio3Xh).
 
 ## Consentimento
 
@@ -103,9 +99,7 @@ Ao concluir uma compra no checkout VTEX, seus clientes poderão optar por se ins
 
 Caso seja necessário, seu time de desenvolvimento pode [ajustar diretamente a opção de inscrição de um cliente específico](https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1) usando a API do Master Data v1.
 
-<div class = "alert alert-info">
-Saiba mais sobre a página Minha Conta. Confira também como seu time de desenvolvimento pode <a href="https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1">ajustar diretamente a inscrição de um cliente na newsletter</a>.
-</div>
+>ℹ️ Saiba mais sobre a página Minha Conta. Confira também como seu time de desenvolvimento pode [ajustar diretamente a inscrição de um cliente na newsletter](https://developers.vtex.com/docs/guides/newsletter-inclusion-master-data-v1).
 
 ### Carrinho abandonado
 
@@ -125,9 +119,7 @@ O direito de consentimento permite que pessoas façam compras na sua loja sem qu
 
 Entre em contato com o seu time de desenvolvimento para disponibilizar esta opção de acordo com o guia [Habilitando opção de salvar dados de usuário](https://developers.vtex.com/docs/guides/enable-the-save-user-data-opt-in).
 
-<div class = "alert alert-info">
-Saiba mais sobre <a href="https://help.vtex.com/pt/tutorial/configurar-carrinho-abandonado--tutorials_740">automação de carrinho abandonado</a>.
-</div>
+>ℹ️ Saiba mais sobre [automação de carrinho abandonado](https://help.vtex.com/pt/tutorial/configurar-carrinho-abandonado--tutorials_740).
 
 ## Exclusão
 
diff --git a/docs/tutorials/pt/declining-order-cancelation.md b/docs/tutorials/pt/declining-order-cancelation.md
index fe48ea5ce..d8691fc53 100644
--- a/docs/tutorials/pt/declining-order-cancelation.md
+++ b/docs/tutorials/pt/declining-order-cancelation.md
@@ -23,13 +23,9 @@ O fluxo de pedidos tem uma[ janela para cancelamento](https://help.vtex.com/pt/t
 
 Para conferir nosso conteúdo para desenvolvedores, veja [Order canceling improvements](https://developers.vtex.com/docs/guides/order-canceling-improvements).
 
-<div class = "alert alert-info">
-Neste artigo, os termos marketplace e seller se referem ao <a href="https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-um-marketplace-vtex">marketplace VTEX</a> e ao <a href="https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#sendo-seller-vtex">seller VTEX</a>. A funcionalidade de recusar solicitação de cancelamento não está disponível para sellers e marketplaces externos.
-</div>
+>ℹ️ Neste artigo, os termos marketplace e seller se referem ao [marketplace VTEX](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#ser-um-marketplace-vtex) e ao [seller VTEX](https://help.vtex.com/pt/tutorial/marketplace-strategies-at-vtex--tutorials_402#sendo-seller-vtex). A funcionalidade de recusar solicitação de cancelamento não está disponível para sellers e marketplaces externos.
 
-<div class = "alert alert-warning">
-Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
-</div>
+>⚠️ Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Diagrama de cancelamento de pedido recusado
 A imagem a seguir mostra o fluxo de recusa da solicitação de cancelamento de um pedido após a janela para cancelamento:
diff --git a/docs/tutorials/pt/defining-window-displays.md b/docs/tutorials/pt/defining-window-displays.md
index 66497e19d..5eb32780f 100644
--- a/docs/tutorials/pt/defining-window-displays.md
+++ b/docs/tutorials/pt/defining-window-displays.md
@@ -15,9 +15,7 @@ legacySlug: definicao-de-vitrines
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 As vitrines são utilizadas no destaque de produtos em diversas páginas, elas também podem ser utilizadas para recomendações, na página do produto.
 
diff --git a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
index 985fab019..50ac79b4a 100644
--- a/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
+++ b/docs/tutorials/pt/deliveries-progress-vtex-shipping-network.md
@@ -40,9 +40,7 @@ Além disso, ao final do artigo você vai encontrar informações sobre:
 * Conexão com agências dos Correios
 * Serviço de Logística Reversa dos Correios
 
-<div class = "alert alert-info">
-Para imprimir etiquetas dos pacotes no Admin VTEX, utilize a ferramenta <a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs"><b>Pronto para envio</b></a>. Você também pode fazer isso por API. Saiba  mais na nossa documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration">VTEX Shipping Network Labels Integration</a>.
-</div>
+>ℹ️ Para imprimir etiquetas dos pacotes no Admin VTEX, utilize a ferramenta [**Pronto para envio**](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs). Você também pode fazer isso por API. Saiba  mais na nossa documentação para desenvolvedores [VTEX Shipping Network Labels Integration](https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration).
 
 ## Informações dos Pedidos
 
@@ -167,9 +165,7 @@ Para selecionar um pacote específico, é possível utilizar a barra de busca ou
 
 É possível exportar os dados dos pacotes listados em formato CSV (valores separados por vírgulas). Para isso, no canto superior direito, clique em `Exportar CSV`. Será feito o download de um arquivo com informações sobre os pacotes organizadas como **[Informações dos Pedidos](#informacoes-dos-pedidos)**. 
 
-<div class = "alert alert-info">
-As informações exportadas são referentes aos pacotes apresentados na tela no momento da exportação.
-</div>
+>ℹ️ As informações exportadas são referentes aos pacotes apresentados na tela no momento da exportação.
 
 ## Solicitar Informações do Pedido aos Correios
 
@@ -200,9 +196,7 @@ Caso você ainda não tenha uma operação com uma agência, acesse a [busca dos
 
 Ao contratar o **VTEX Shipping Network Correios**, você pode utilizar o serviço [Logística Reversa dos Correios](https://www.correios.com.br/enviar/encomendas/logistica-reversa). A VTEX disponibiliza um login e uma senha para você utilizar no site dos Correios e gerar a autorização de postagem.
 
-<div class = "alert alert-info">
-Para solicitar login e senha para utilizar o serviço de <b>Logística Reversa dos Correios</b>, entre em contato com a VTEX pelo email <i>vtexlog@vtex.com.br</i>.
-</div>
+>ℹ️ Para solicitar login e senha para utilizar o serviço de **Logística Reversa dos Correios**, entre em contato com a VTEX pelo email <i>vtexlog@vtex.com.br</i>.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
index c5ce5e9ba..f2d03e32e 100644
--- a/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
+++ b/docs/tutorials/pt/displaying-vtex-ad-network-ads-in-your-store-beta.md
@@ -15,9 +15,7 @@ legacySlug: exibindo-anuncios-do-vtex-ad-network-na-sua-loja-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 Com [VTEX Ad Network (Beta)](https://help.vtex.com/pt/tutorial/vtex-ad-network-beta--2cgqXcBuJmXN2livQvClur), lojas VTEX podem disponibilizar espaço publicitário para que marcas promovam seus produtos na sua loja. Desta forma, a VTEX selecionará anúncios de produtos que já compõem o seu catálogo e sua loja receberá um valor por cada clique em anúncios na sua frente de loja.
 
diff --git a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
index 4763cab09..1e36e686e 100644
--- a/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
+++ b/docs/tutorials/pt/dynamic-relevance-in-intelligent-search-beta.md
@@ -30,9 +30,7 @@ No Intelligent Search, existem duas formas de configurar a relevância da sua bu
 
 Apenas uma delas é aplicada à sua loja por vez e você pode [alterar o tipo de relevância](#alterar-o-tipo-de-relevancia) configurado na sua loja. Caso você altere a relevância manual para dinâmica, todas as regras manuais já cadastradas continuam salvas.
 
-<div class = "alert alert-info">
-A relevância manual é configurada como padrão da loja.
-</div>
+>ℹ️ A relevância manual é configurada como padrão da loja.
 
 ## Manual 
 
@@ -67,9 +65,7 @@ Para ativar a relevância dinâmica, siga os seguintes passos:
 
 Para alterar o tipo de relevância, siga os passos abaixo:
 
-<div class = "alert alert-warning">
-Não recomendamos a troca constante do tipo de relevância utilizado pela sua loja. O sistema precisa de uma semana para se estabelecer.
-</div>
+>⚠️ Não recomendamos a troca constante do tipo de relevância utilizado pela sua loja. O sistema precisa de uma semana para se estabelecer.
 
 1. No Admin VTEX, acesse **Storefront > Intelligent Search > Regras de relevância**  ou digite **Regras de relevância** na barra de busca no topo da página.
 2. Clique em `Alterar` .
diff --git a/docs/tutorials/pt/events-available-in-audit.md b/docs/tutorials/pt/events-available-in-audit.md
index ec10c00c2..c68e39a4f 100644
--- a/docs/tutorials/pt/events-available-in-audit.md
+++ b/docs/tutorials/pt/events-available-in-audit.md
@@ -35,9 +35,7 @@ Confira a seguir a lista dos possíveis eventos disponíveis no [Audit](https://
 * [Headless CMS](#headless-cms)
 * [Gerenciamento de sellers](#gerenciamento-de-sellers)
 
-<div class = "alert alert-info">
-  <p>Caso você visualize no Audit algum evento que não esteja listado aqui, por favor nos informe usando a <a href="https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform">página de feedback de documentação</a>.</p>
-  </div>
+>ℹ️ Caso você visualize no Audit algum evento que não esteja listado aqui, por favor nos informe usando a [página de feedback de documentação](https://docs.google.com/forms/d/e/1FAIpQLSfmnotPvPjw-SjiE7lt2Nt3RQgNUe10ixXZmuO2v9enOJReoQ/viewform).
 
 >⚠️ Nas opções de filtros do Audit, você pode encontrar **Opções de envio**, **Profile System** e **Billing** além das aplicações citadas abaixo. Essas opções se referem a recursos internos ou funcionalidades em fase beta fechada, portanto, a maior parte das contas não terão eventos associados.
 
diff --git a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
index d55a00ec8..bd0155e52 100644
--- a/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
+++ b/docs/tutorials/pt/exporting-and-importing-product-and-sku-specifications.md
@@ -19,9 +19,7 @@ Após a definição da árvore de categorias e o cadastro de [especificações d
 
 Neste artigo, explicamos como funciona a exportação e importação de planilhas com as especificações de produto e de SKU no Admin VTEX.
 
-<div class = "alert alert-info">
-  <p>Para exportar e importar especificações utilizando a <strong>Catalog API</strong>, siga o guia para desenvolvedores <a href="https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification">How to create a specification</a>.</p>
-</div>
+>ℹ️ Para exportar e importar especificações utilizando a **Catalog API**, siga o guia para desenvolvedores [How to create a specification](https://developers.vtex.com/vtex-developer-docs/docs/how-to-create-a-specification).
 
 ## Exportar especificações de produto ou de SKU
 
@@ -39,9 +37,7 @@ Veja a seguir como exportar a planilha com as especificações de produto ou de
 
 ![skuexport2.pt](https://images.ctfassets.net/alneenqid6w5/32z4zfvN7GeKcfZsuVQsGA/cac3411fabd0a1d32cb85b4592d0a4dd/skuexport2.pt.png)
 
-<div class = "alert alert-info">
-  <p>A planilha exportada ficará disponível por uma semana no seu email. Caso exceda esse prazo, siga o passo a passo de exportação novamente para gerar uma nova planilha.</p>
-</div>
+>ℹ️ A planilha exportada ficará disponível por uma semana no seu email. Caso exceda esse prazo, siga o passo a passo de exportação novamente para gerar uma nova planilha.
 
 ## Importar especificações de produto ou de SKU
 
diff --git a/docs/tutorials/pt/filling-out-collection-registration-fields.md b/docs/tutorials/pt/filling-out-collection-registration-fields.md
index ec52ce53e..4b5240a70 100644
--- a/docs/tutorials/pt/filling-out-collection-registration-fields.md
+++ b/docs/tutorials/pt/filling-out-collection-registration-fields.md
@@ -15,9 +15,7 @@ legacySlug: preencher-campos-de-cadastro-de-colecao
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 Para entender melhor o significado dos campos de cadastro de uma coleção de produtos, veja abaixo a descrição completa de cada um deles:
 
diff --git a/docs/tutorials/pt/filtering-all-orders.md b/docs/tutorials/pt/filtering-all-orders.md
index 614118c8e..45a241d63 100644
--- a/docs/tutorials/pt/filtering-all-orders.md
+++ b/docs/tutorials/pt/filtering-all-orders.md
@@ -15,9 +15,7 @@ legacySlug: como-filtrar-pedidos
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class = "alert alert-info">
-É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 No módulo **Pedidos**, a página **Todos os pedidos** permite a você acessar os pedidos da sua loja e pesquisar usando a barra de busca e filtros, como na imagem abaixo:
 
@@ -49,9 +47,7 @@ Para realizar a pesquisa na barra de busca, digite o termo desejado e aperte a t
 
 O [sequence](https://help.vtex.com/pt/tutorial/cuidados-ao-definir-a-numeracao-de-pedido--VAKKptfcaOxFxM8gfPobu) é uma sequência de seis dígitos que aparece no seu Admin VTEX logo após o ID do pedido. Por exemplo, no pedido `1268540501456-01 (501456)`, o ID do pedido é `1268540501456`, o `-01` indica que o fulfillment será realizado por um seller e o sequence é `501456`.
 
-<div class = "alert alert-info">
-Além dos critérios listados acima, é possível ativar outros critérios de busca, como será visto na seção <a href="https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-outros">Outros</a>.
-</div>
+>ℹ️ Além dos critérios listados acima, é possível ativar outros critérios de busca, como será visto na seção [Outros](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-outros).
 
 Por padrão, a página **Todos os pedidos** vem com o filtro de pedidos criados **Hoje** ativado. Para buscar em outras datas, use os filtros descritos em [Filtros: Datas](#filtros-datas) e em [Criado](#criado).
 
@@ -90,9 +86,7 @@ Ao clicar em `Filtros`, um modal é aberto e apresenta as seguintes opções:
 
 Para que um filtro seja aplicado à busca, selecione a opção desejadas e clique em **Aplicar**. Para remover filtros aplicados, clique em **Limpar filtros > Aplicar**.
 
-<div class = "alert alert-info">
-Por padrão, a opção <i class="fas fa-toggle-on"></i> <b>Usar meu fuso horário: GMT-3</b> aparece ativada para todos os filtros. Ao ser desativada, a referência de fuso horário muda para GMT-0 e, se reativada, passa a ser o fuso horário adotado no navegador do usuário.
-</div>
+>ℹ️ Por padrão, a opção <i class="fas fa-toggle-on"></i> **Usar meu fuso horário: GMT-3** aparece ativada para todos os filtros. Ao ser desativada, a referência de fuso horário muda para GMT-0 e, se reativada, passa a ser o fuso horário adotado no navegador do usuário.
 
 Caso não exista uma correspondência para a combinação de filtros utilizada na busca, a pesquisa retorna sem pedidos na tela.
 
@@ -199,9 +193,7 @@ Na página **Pedidos > Todos os pedidos**, existe a opção `Filtrar por status`
 
 Ao clicar em `Filtrar por status` <i class="fas fa-angle-down"></i>, aparecem as opções de [status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196) da sua loja. Por exemplo, se entre todos os seus pedidos não houver pedidos cancelados, esta opção não estará visível.
 
-<div class = "alert alert-info">
-Para mais opções de filtros de status, veja a seção <a href="https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-status">Filtros: Status</a>. Se você quiser conferir todos os status de pedidos existentes, veja o artigo <a href="https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196">Fluxo e status de pedidos</a>.
-</div>
+>ℹ️ Para mais opções de filtros de status, veja a seção [Filtros: Status](https://help.vtex.com/pt/tutorial/filtrar-todos-pedidos--tutorials_192#filtros-status). Se você quiser conferir todos os status de pedidos existentes, veja o artigo [Fluxo e status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
 
 ## Criado
 
@@ -217,8 +209,6 @@ Este filtro tem a data **Hoje** ativada de forma padrão, mas ao clicar nele apa
 - Mês atual
 - Últimos 30 dias
 
-<div class = "alert alert-info">
-Por padrão, a opção <i class="fas fa-toggle-on"></i> <b>Usar meu fuso horário: GMT-3</b> aparece ativada. Ao ser desativada, a referência de fuso horário muda para GMT-0 e, se reativada, passa a ser o fuso horário usado no navegador do usuário.
-</div>
+>ℹ️ Por padrão, a opção <i class="fas fa-toggle-on"></i> **Usar meu fuso horário: GMT-3** aparece ativada. Ao ser desativada, a referência de fuso horário muda para GMT-0 e, se reativada, passa a ser o fuso horário usado no navegador do usuário.
 
 Para mais opções de filtros de datas e períodos, veja a seção [Filtros: Datas](#filtros-datas).
diff --git a/docs/tutorials/pt/forcing-searches-with-blocked-terms-to-return-results.md b/docs/tutorials/pt/forcing-searches-with-blocked-terms-to-return-results.md
index 3d6a404b3..501631507 100644
--- a/docs/tutorials/pt/forcing-searches-with-blocked-terms-to-return-results.md
+++ b/docs/tutorials/pt/forcing-searches-with-blocked-terms-to-return-results.md
@@ -15,9 +15,7 @@ legacySlug: forcar-buscas-com-termos-bloqueados-a-retornarem-resultados
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Para tornar as buscas dos clientes mais precisas, o buscador da VTEX ignora alguns termos que são muito comuns. Alguns exemplos são as palavras "com" e "todo", do português, "that" e "with", do inglês, e "hace" e "uno", do espanhol. [Veja aqui a lista completa de termos bloqueados](/pt/tutorial/por-que-o-buscador-da-vtex-ignora-alguns-termos-buscados).
 
diff --git a/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md b/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
index 44ae01702..22fe06644 100644
--- a/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
+++ b/docs/tutorials/pt/frequently-asked-questions-new-orders-module-interface.md
@@ -32,9 +32,7 @@ Você pode visualizar a correspondência de seções e campos entre a versão an
 
 O filtro de seis meses foi substituído pela busca sem limite de data, que retorna todos os pedidos relacionados ao critério utilizado, independente da data de criação do pedido. É possível, por exemplo, acessar o histórico completo de compras de um cliente, utilizando o nome, email ou documento do cliente. Saiba mais no artigo [Filtrar pedidos em Todos os pedidos](https://help.vtex.com/pt/tutorial/como-filtrar-pedidos--tutorials_192).
 
-<div class = "alert alert-info">
-A busca em todos os pedidos não pode ser associada a outros filtros, portanto, ao remover o limite de datas da busca, outros filtros se tornam inativos. Você pode, no entanto, combinar filtros e selecionar o período personalizado de seis meses, por exemplo.
-</div>
+>ℹ️ A busca em todos os pedidos não pode ser associada a outros filtros, portanto, ao remover o limite de datas da busca, outros filtros se tornam inativos. Você pode, no entanto, combinar filtros e selecionar o período personalizado de seis meses, por exemplo.
 
 Para buscar em todos os pedidos, digite o termo desejado na caixa de busca. Isso fará com que a opção <i class="fas fa-toggle-off"></i> `Remover limite de datas` se torne visível. Depois basta ativá-la e isso dará início à busca.
 
diff --git a/docs/tutorials/pt/fulfillment-logistics-vtex.md b/docs/tutorials/pt/fulfillment-logistics-vtex.md
index 98a72a504..bbd7b19be 100644
--- a/docs/tutorials/pt/fulfillment-logistics-vtex.md
+++ b/docs/tutorials/pt/fulfillment-logistics-vtex.md
@@ -19,10 +19,8 @@ A logística ou fulfillment é o processo de planejamento, transporte e armazena
 
 A VTEX possibilita o cadastro e controle dos estoques, o gerenciamento das tarifas de envio, o controle da disponibilidade dos itens e o acompanhamento das entregas. 
 
-<div class = "alert alert-info">
-Se a sua loja não trilhou os primeiros passos do módulo <b>Envio</b>, confira o artigo <a href="https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a">Primeiros passos da Logística</a>.</b> 
-Confira o artigo <a href="https://help.vtex.com/pt/tutorial/glossario-de-logistica--16DSSiXn548rsidi0A8Hby">Glossário de logística</a>, para conhecer os significados de termos logísticos utilizados na VTEX. Há também as configurações de logística disponíveis via <a href="https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview">API</a>. 
-</div>
+>ℹ️ Se a sua loja não trilhou os primeiros passos do módulo **Envio**, confira o artigo [Primeiros passos da Logística](https://help.vtex.com/pt/tracks/logistica-101--13TFDwDttPl9ki9OXQhyjx/6Y8C1JuPtO5E61Ew91tq1a).</b> 
+> Confira o artigo [Glossário de logística](https://help.vtex.com/pt/tutorial/glossario-de-logistica--16DSSiXn548rsidi0A8Hby), para conhecer os significados de termos logísticos utilizados na VTEX. Há também as configurações de logística disponíveis via [API](https://developers.vtex.com/vtex-rest-api/reference/logistics-api-overview).
 
 Para saber quais configurações logísticas são necessárias e como são realizadas, primeiro é preciso entender as etapas do fluxo de compra de um produto:
 
@@ -43,9 +41,7 @@ Para saber quais configurações logísticas são necessárias e como são reali
     * Para os pedidos que são enviados para os [pontos de retirada](https://help.vtex.com/pt/tutorial/como-funcionam-pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) (retirada), a loja deve deixar os pacotes disponíveis para o cliente retirar. Para isso, os pacotes são retirados do [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e transportados até o ponto de retirada. O transporte da doca até o ponto de retirada é definido por uma[ política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140).
 8. Após o faturamento e envio, a loja é responsável por atualizar o inventário, que, para a plataforma, significa também a baixa dos itens no estoque.
 
-<div class = "alert alert-info">
-Note que o processo de envio dependerá das configurações realizadas na plataforma. Aqui apresentamos  os cenários para cada tipo de envio (entrega e retirada), mas há outros fluxos possíveis no processo de envio. Por exemplo, quando o envio é por retirada e o estoque coincide com o ponto de retirada, não é necessário o transporte dos pacotes entre esses locais.
-</div>
+>ℹ️ Note que o processo de envio dependerá das configurações realizadas na plataforma. Aqui apresentamos  os cenários para cada tipo de envio (entrega e retirada), mas há outros fluxos possíveis no processo de envio. Por exemplo, quando o envio é por retirada e o estoque coincide com o ponto de retirada, não é necessário o transporte dos pacotes entre esses locais.
 
 ![Envio PT](https://images.ctfassets.net/alneenqid6w5/2e2f4toAiFamlcXlAQfC3h/186ee5138e0d5d412c9eb50890708241/Envio_PT.svg)
 
diff --git a/docs/tutorials/pt/gift-card.md b/docs/tutorials/pt/gift-card.md
index 953c1703e..d35195771 100644
--- a/docs/tutorials/pt/gift-card.md
+++ b/docs/tutorials/pt/gift-card.md
@@ -32,9 +32,7 @@ Para criar um novo vale-presente, confira o passo a passo:
   <br>
   <li>Clique no botão azul <b>Criar vale</b>.</li>  
   <br>
-<div class = "alert alert-info">
-  <p>Na tela de criação do vale, o campo <b>Vale-presente</b> é automaticamente preenchido pelo sistema VTEX com o código ID do novo vale. Esse é o código a ser inserido pelo cliente na tela do checkout para aplicar o vale-presente no carrinho e reduzir o valor de pagamento do pedido.</p>
-</div>
+>ℹ️ Na tela de criação do vale, o campo **Vale-presente** é automaticamente preenchido pelo sistema VTEX com o código ID do novo vale. Esse é o código a ser inserido pelo cliente na tela do checkout para aplicar o vale-presente no carrinho e reduzir o valor de pagamento do pedido.
 <br>
   <li>Preencha os demais campos apresentados conforme as orientações abaixo:</li>
   <br>
diff --git a/docs/tutorials/pt/google-analytics-faq.md b/docs/tutorials/pt/google-analytics-faq.md
index ba75e6879..15e9a1f72 100644
--- a/docs/tutorials/pt/google-analytics-faq.md
+++ b/docs/tutorials/pt/google-analytics-faq.md
@@ -50,9 +50,7 @@ Como a VTEX é responsável por processar transações da sua loja, todas as tra
 - Tag de transação dispara mesmo com transações que não foram concluídas com sucesso.
 - Falha ou duplicidade na exibição da página de confirmação do pedido, caso a tag de transação esteja vinculada à exibição desta página.
 
-<div class = "alert alert-info">
-Considere também que há um atraso de até 48h no registro de dados de transações no Google Analytics.
-</div>
+>ℹ️ Considere também que há um atraso de até 48h no registro de dados de transações no Google Analytics.
 
 Além disso, integrações podem ser construídas de modo que acabem não disparando certas tags na sua frente de loja. Por exemplo, há integrações que usam um [app de pagamento](https://developers.vtex.com/vtex-rest-api/docs/payments-integration-payment-app) e finalizam a compra sem direcionar o cliente à página de confirmação de pedido, como a integração desenvolvida pela AME Digital. Transações sempre serão registradas na VTEX, mas, nesse caso, é provável que não seja registrada no Google Analytics, gerando divergência.
 
diff --git a/docs/tutorials/pt/google-pay-beta.md b/docs/tutorials/pt/google-pay-beta.md
index e8ea60c05..20b8bf5fc 100644
--- a/docs/tutorials/pt/google-pay-beta.md
+++ b/docs/tutorials/pt/google-pay-beta.md
@@ -15,9 +15,7 @@ legacySlug: google-pay-beta
 subcategory: 3lZEaiSilZPwa3eCUUzwyr
 ---
 
-<div class = "alert alert-info">
-Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 O Google Pay™ é um serviço de pagamentos digitais que possibilita ao usuário não compartilhar os dados reais do seu cartão com a loja, trazendo mais segurança e acelerando a etapa de checkout. Com Google Pay o usuário pode realizar pagamentos por meio de cartões de crédito ou de débito, sem a necessidade de preencher qualquer dado manualmente, e o Google Pay também está disponível em diversos apps, sites e na Carteira do Google
 
diff --git a/docs/tutorials/pt/how-does-reservation-work.md b/docs/tutorials/pt/how-does-reservation-work.md
index 9cf0aa472..61b101834 100644
--- a/docs/tutorials/pt/how-does-reservation-work.md
+++ b/docs/tutorials/pt/how-does-reservation-work.md
@@ -17,11 +17,9 @@ subcategory: 3PQwnyOcNyYgawy06oe6gE
 
 A reserva é uma solução VTEX que impede que um mesmo item seja vendido mais de uma vez. Após a finalização de uma compra, o item comprado é subtraído do inventário disponível e, internamente, passa para o status **Reservado**.
 
-<div class = "alert alert-info">
-Na VTEX, Estoque é o local físico onde os itens são armazenados. Para poder identificar de qual estoque os itens serão retirados pelas transportadoras, é preciso cadastrar os estoques na plataforma. Consulte o artigo <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a> para saber mais. 
-<p>
-O inventário é a relação dos itens que sua loja possui em estoque. Você pode adicionar e acompanhar os itens disponíveis na sua loja pelo Gerenciamento de Inventário. Consulte o artigo <a href="https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139">Gerenciar inventário</a> para saber mais.
-</div>
+>ℹ️ Na VTEX, Estoque é o local físico onde os itens são armazenados. Para poder identificar de qual estoque os itens serão retirados pelas transportadoras, é preciso cadastrar os estoques na plataforma. Consulte o artigo [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) para saber mais. 
+> <p>
+> O inventário é a relação dos itens que sua loja possui em estoque. Você pode adicionar e acompanhar os itens disponíveis na sua loja pelo Gerenciamento de Inventário. Consulte o artigo [Gerenciar inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139) para saber mais.
 
 Após ser vendido, um item passa pelos seguintes status no inventário da sua loja:
 
@@ -93,8 +91,6 @@ Quando o lojista ou o ERP atualizarem a quantidade desse item no inventário  re
 
 Como descrito acima, a baixa no estoque é uma consequência da atualização do inventário pelo lojista. Portanto, não é possível visualizar esse status na plataforma. É possível apenas conferir a quantidade de itens disponíveis para venda e a movimentação dos itens pelo [Gerenciamento de inventário](https://help.vtex.com/pt/tutorial/gerenciar-itens-em-estoque--tutorials_139).
 
-<div class = "alert alert-info">
-É importante lembrar que todos os status aqui descritos são internos e exclusivos da VTEX para o controle de venda de itens.
-<p>O status da reserva é consequência do status do pedido. Algumas mudanças dependem de atitudes do comprador, e outras, de atualização manual ou do ERP.
-</div>
+>ℹ️ É importante lembrar que todos os status aqui descritos são internos e exclusivos da VTEX para o controle de venda de itens.
+> <p>O status da reserva é consequência do status do pedido. Algumas mudanças dependem de atitudes do comprador, e outras, de atualização manual ou do ERP.
 
diff --git a/docs/tutorials/pt/how-does-vtex-search-work.md b/docs/tutorials/pt/how-does-vtex-search-work.md
index de625d704..8052b6394 100644
--- a/docs/tutorials/pt/how-does-vtex-search-work.md
+++ b/docs/tutorials/pt/how-does-vtex-search-work.md
@@ -17,9 +17,7 @@ subcategory: pwxWmUu7T222QyuGogs68
 
 Este artigo tem o objetivo de descrever o funcionamento do sistema de busca da VTEX.
 
-<div class = "alert alert-warning">
-  A VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ A VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 ## Como o buscador da VTEX prioriza a exibição de produtos
 
diff --git a/docs/tutorials/pt/how-mercado-livre-integration-works.md b/docs/tutorials/pt/how-mercado-livre-integration-works.md
index 36c6f8ee6..0236812b9 100644
--- a/docs/tutorials/pt/how-mercado-livre-integration-works.md
+++ b/docs/tutorials/pt/how-mercado-livre-integration-works.md
@@ -98,9 +98,7 @@ Os produtos precisam ter os seguintes campos na plataforma VTEX marcados para se
 
 No campo **Política comercial**, você deverá marcar a opção correspondente à [política comercial](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq/15NZiQstCET8zyQUIa7nhw) vinculada ao Mercado Livre.
 
-<div class = "alert alert-info">
-Para acrescentar novas imagens em um anúncio que já existe no Mercado Livre, você precisará fazer todas as mudanças direto no painel do próprio marketplace. O Mercado Livre só aceita 12 imagens por produto sem variação, e até 10 imagens por variação.
-</div>
+>ℹ️ Para acrescentar novas imagens em um anúncio que já existe no Mercado Livre, você precisará fazer todas as mudanças direto no painel do próprio marketplace. O Mercado Livre só aceita 12 imagens por produto sem variação, e até 10 imagens por variação.
 
 ## 3. Preços
 
diff --git a/docs/tutorials/pt/how-my-account-works.md b/docs/tutorials/pt/how-my-account-works.md
index 54763a2ab..13009acad 100644
--- a/docs/tutorials/pt/how-my-account-works.md
+++ b/docs/tutorials/pt/how-my-account-works.md
@@ -26,9 +26,7 @@ A página __Minha Conta__ (__My Account__) oferece autonomia aos seus clientes p
 - [Assinaturas](#assinaturas)
 - [Autenticação](#autenticacao)
 
-<div class = "alert alert-info">
-Para saber sobre a customização da funcionalidade <b>Minha conta</b>, veja a documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-my-account">My Account - StoreV2 version</a>. É importante ressaltar que a VTEX não presta suporte a <b>Minha Conta</b> quando customizada.
-</div>
+>ℹ️ Para saber sobre a customização da funcionalidade **Minha conta**, veja a documentação para desenvolvedores [My Account - StoreV2 version](https://developers.vtex.com/docs/guides/vtex-my-account). É importante ressaltar que a VTEX não presta suporte a **Minha Conta** quando customizada.
 
 ## Dados pessoais
 
@@ -77,9 +75,7 @@ O botão `Adicionar endereço` permite incluir endereços diferentes daqueles j
 
 ## Pedidos
 
-<div class = "alert alert-info">
-Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
-</div>
+>ℹ️ Em [Minha Conta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
 
 Essa aba traz a listagem completa dos pedidos realizados pelo cliente na sua loja. A lista é ordenada por data de criação e exibe detalhes como data do pedido, valor total da compra, ID do pedido, status e itens adquiridos.
 
diff --git a/docs/tutorials/pt/how-shipping-calculation-works.md b/docs/tutorials/pt/how-shipping-calculation-works.md
index 5ab2d1d27..a11c220cf 100644
--- a/docs/tutorials/pt/how-shipping-calculation-works.md
+++ b/docs/tutorials/pt/how-shipping-calculation-works.md
@@ -17,9 +17,7 @@ subcategory: 7fTH6bP0C4IaM8qWi0kkQC
 
 Na experiência de compra, quando o consumidor insere sua localização no checkout, a plataforma VTEX analisa quais [estratégias de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) atendem o pedido e apresenta ao consumidor as opções de envio disponíveis.
 
-<div class = "alert alert-info">
-Durante o fluxo de compra, na etapa da vitrine, quando o consumidor ainda não inseriu o seu endereço, os produtos que serão apresentados são aqueles pertencentes a sellers que tenham configurado a funcionalidade <a href="https://help.vtex.com/pt/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc">Region</a> ou <a href="https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI">sellers abrangentes</a>, que são aqueles capazes de enviar pedidos para todas as regiões atendidas pela operação do marketplace.
-</div>
+>ℹ️ Durante o fluxo de compra, na etapa da vitrine, quando o consumidor ainda não inseriu o seu endereço, os produtos que serão apresentados são aqueles pertencentes a sellers que tenham configurado a funcionalidade [Region](https://help.vtex.com/pt/tutorial/configurar-preco-e-disponibilidade-de-skus-por-region--12ne58BmvYsYuGsimmugoc) ou [sellers abrangentes](https://help.vtex.com/pt/tutorial/seller-abrangente--5Qn4O2GpjUIzWTPpvLUfkI), que são aqueles capazes de enviar pedidos para todas as regiões atendidas pela operação do marketplace.
 
 Este artigo apresenta uma visão geral do cálculo de envio e está dividido nas seguintes seções:
 
@@ -34,9 +32,7 @@ Para determinar qual combinação de etapas logísticas configuradas pela loja s
 - **Entrega:** o consumidor recebe o pedido no endereço informado. 
 - **Retirada:** o consumidor busca o pedido em um [ponto de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R).
 
-<div class = "alert alert-info">
-Entrega e retirada possuem os mesmo critérios de seleção, existe apenas um critério adicional na retirada, que será abordado adiante.
-</div>
+>ℹ️ Entrega e retirada possuem os mesmo critérios de seleção, existe apenas um critério adicional na retirada, que será abordado adiante.
 
 A seleção de combinações logísticas acontece de acordo com os seguintes critérios, nesta ordem de aplicação:
 
@@ -64,9 +60,7 @@ A seleção de combinações logísticas acontece de acordo com os seguintes cri
   <li><a href="https://help.vtex.com/pt/tutorial/gerenciar-doca--7K3FultD8I2cuuA6iyGEiW#campos-de-cadastro">Docas prioritárias</a></li>
 </ul>
 <br>
-  <div class = "alert alert-info">
-Quando existe um empate entre docas, o critério de desempate é o overhead, que é o valor em dias para a escolha da doca mais vantajosa para determinado envio. Quanto menor o overhead, maiores são as chances de seleção da doca. Vale ressaltar que o overhead não é considerado no cálculo do tempo de envio.
-</div>
+  >ℹ️ Quando existe um empate entre docas, o critério de desempate é o overhead, que é o valor em dias para a escolha da doca mais vantajosa para determinado envio. Quanto menor o overhead, maiores são as chances de seleção da doca. Vale ressaltar que o overhead não é considerado no cálculo do tempo de envio.
 
 5. **Etapa exclusiva para envio do tipo retirada:** existe um passo adicional na seleção para analisar os [pontos de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R). A plataforma VTEX cria uma lista com os pontos de retirada elegíveis, utilizando o critério menor distância entre o ponto de retirada e a localização do consumidor.
 
@@ -95,9 +89,7 @@ O cálculo do SLA é feito utilizando os seguintes campos e parâmetros:
 
 É possível obter uma estimativa do tempo de envio por meio do [Simulador de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144), sendo que a simulação considera as configurações das [estratégias de envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) da loja VTEX.
 
-<div class = "alert alert-info">
-O resultado obtido com o <a href="https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144">Simulador de envio</a> é apenas aproximado, pois fatores determinantes são conhecidos somente no checkout, tais como disponibilidade de transportadora no horário da compra, tempo de confirmação do pagamento e resultado da <a href="https://help.vtex.com/pt/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">seleção de sellers white label</a>.
-</div>
+>ℹ️ O resultado obtido com o [Simulador de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144) é apenas aproximado, pois fatores determinantes são conhecidos somente no checkout, tais como disponibilidade de transportadora no horário da compra, tempo de confirmação do pagamento e resultado da [seleção de sellers white label](https://help.vtex.com/pt/tutorial/selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa).
 
 ## Saiba mais	
 
diff --git a/docs/tutorials/pt/how-subscriptions-work.md b/docs/tutorials/pt/how-subscriptions-work.md
index ac2d38af6..35c7457cf 100644
--- a/docs/tutorials/pt/how-subscriptions-work.md
+++ b/docs/tutorials/pt/how-subscriptions-work.md
@@ -47,9 +47,7 @@ Para isso, basta entrar na página **Minha Conta** no site da sua loja, acessar
 
 ## Como o cliente da sua loja visualiza suas Assinaturas
 
-<div class = "alert alert-info">
-Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
-</div>
+>ℹ️ Em [Minha Conta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
 
 Após a finalização do pedido com Assinatura, o seu cliente visualiza na página **Minha Conta** a seção **Assinaturas**. Nessa seção, ele também pode encontrar a lista de assinaturas realizadas com os detalhes e estado individual. Seu cliente também receberá por e-mail uma confirmação da Assinatura e do pedido gerado.
 
diff --git a/docs/tutorials/pt/how-the-skyhub-integration-works.md b/docs/tutorials/pt/how-the-skyhub-integration-works.md
index 8a3b693df..361de2ecc 100644
--- a/docs/tutorials/pt/how-the-skyhub-integration-works.md
+++ b/docs/tutorials/pt/how-the-skyhub-integration-works.md
@@ -64,9 +64,7 @@ Existem dois status possíveis para um produto na B2W:
 - **Ativo:** aparece no marketplace e está disponível para venda.
 - **Inativo:** não aparece no marketplace e está indisponível para venda.
 
-<div class = "alert alert-info">
-Não existem campos obrigatórios para que um produto seja integrado. No entanto, se um produto não possui preço cadastrado ou estoque positivo, ele se torna inativo.
-</div>
+>ℹ️ Não existem campos obrigatórios para que um produto seja integrado. No entanto, se um produto não possui preço cadastrado ou estoque positivo, ele se torna inativo.
 
 ### Exibição de produtos
 
@@ -86,9 +84,7 @@ Depois que os produtos recebem a primeira carga de estoque, a atualização ser
 
 A integração envia o [preço de lista](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx#preco-de-lista) e o preço final para cada SKU. O preço final é enviado de acordo com o retorno da [simulação de fulfillment](https://developers.vtex.com/vtex-rest-api/reference/fulfillment-simulation). Em um cenário padrão, o preço enviado será sempre o determinado pela política comercial usada na integração.
 
-<div class = "alert alert-info">
-Qualquer alteração no <a href= "https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx">preço base</a> ou no <a href= "https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy">preço fixo</a> de um produto vai se refletir automaticamente na B2W. Vale ressaltar que o preço fixo se sobrepõe a todas as configurações de preços existentes em uma <a href= "https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8">tabela de preços</a>.
-</div>
+>ℹ️ Qualquer alteração no <a href= "https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx">preço base</a> ou no <a href= "https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy">preço fixo</a> de um produto vai se refletir automaticamente na B2W. Vale ressaltar que o preço fixo se sobrepõe a todas as configurações de preços existentes em uma <a href= "https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8">tabela de preços</a>.
 
 Não é possível enviar preços diferenciados em função da forma de pagamento, pois a escolha da forma de pagamento é determinada no ambiente da B2W.
 
@@ -163,9 +159,7 @@ Ao faturar o pedido na VTEX, a integração atualiza o status na SkyHub para `Sh
 
 O campo `CourierStatus` pode ser populado automaticamente por [atualizações de rastreio das próprias transportadoras](https://help.vtex.com/pt/tutorial/quais-transportadoras-disponibilizam-o-rastreio-de-frete) ou manualmente, pela API _[Update Order Tracking Status](https://developers.vtex.com/vtex-developer-docs/reference/updatetrackingstatus)_ ou pelo Admin VTEX, em **PEDIDOS > Gerenciamento de pedidos**. Quando o campo retornar `finished=true`, então o status do pedido é declarado como `Delivered` e a integração envia essa informação ao marketplace. Caso o campo retorne `finished=false`, o status do pedido não é alterado para `Delivered`, permanecendo no status anterior.
 
-<div class = "alert alert-info">
-Se você utiliza o serviço <a href="https://help.vtex.com/pt/tracks/configurar-integracao-da-b2w--6w07SJBVqE020KIOOS8ygk/5hHCiAMHih2lc5xb3A5Ohp#b2w-entregas-e-b2w-entregas-direct">B2W Entregas ou B2W Entregas Direct</a>, o preço do frete não entrará no valor do pedido integrado na VTEX e na nota fiscal constará apenas o custo dos produtos. A nota fiscal do frete deverá ser emitida pela própria B2W, que é quem está fornecendo esse serviço.
-</div>
+>ℹ️ Se você utiliza o serviço [B2W Entregas ou B2W Entregas Direct](https://help.vtex.com/pt/tracks/configurar-integracao-da-b2w--6w07SJBVqE020KIOOS8ygk/5hHCiAMHih2lc5xb3A5Ohp#b2w-entregas-e-b2w-entregas-direct), o preço do frete não entrará no valor do pedido integrado na VTEX e na nota fiscal constará apenas o custo dos produtos. A nota fiscal do frete deverá ser emitida pela própria B2W, que é quem está fornecendo esse serviço.
 
 ### Enviar pedido
 
@@ -180,9 +174,7 @@ Apesar de a SkyHub consultar o frete na VTEX, a integração permite usar uma so
 
 No caso de uma solução de terceiros fazer o cálculo de frete ou no caso de utilizar uma tabela de contingência, a integração faz um _match_ do frete calculado com a transportadora que mais se adequa na VTEX. O parâmetro utilizado é o nome da transportadora escolhida. Caso a integração não consiga encontrar uma transportadora idêntica, a VTEX integra o pedido com a transportadora mais barata disponível.
 
-<div class = "alert alert-info">
-Para o seller que utiliza o serviço <a href="https://help.vtex.com/pt/tracks/configurar-integracao-da-b2w--6w07SJBVqE020KIOOS8ygk/5hHCiAMHih2lc5xb3A5Ohp#b2w-entregas-e-b2w-entregas-direct">B2W Entregas ou B2W Entregas Direct</a>, a SkyHub não consulta a VTEX sobre frete, pois o envio é responsabilidade do marketplace. É possível também <a href="https://help.vtex.com/pt/tutorial/configurar-integracao-de-lojas-fisicas-com-a-b2w--1yv2BSquNmdp8M6vJvaLwm">Configurar integração de lojas físicas com a B2W</a> e oferecer ao consumidor a opção de pontos de retirada do pedido.
-</div>
+>ℹ️ Para o seller que utiliza o serviço [B2W Entregas ou B2W Entregas Direct](https://help.vtex.com/pt/tracks/configurar-integracao-da-b2w--6w07SJBVqE020KIOOS8ygk/5hHCiAMHih2lc5xb3A5Ohp#b2w-entregas-e-b2w-entregas-direct), a SkyHub não consulta a VTEX sobre frete, pois o envio é responsabilidade do marketplace. É possível também [Configurar integração de lojas físicas com a B2W](https://help.vtex.com/pt/tutorial/configurar-integracao-de-lojas-fisicas-com-a-b2w--1yv2BSquNmdp8M6vJvaLwm) e oferecer ao consumidor a opção de pontos de retirada do pedido.
 
 <br></br>
 ### Saiba mais
diff --git a/docs/tutorials/pt/how-to-change-order-items.md b/docs/tutorials/pt/how-to-change-order-items.md
index bfea2469c..6069d024d 100644
--- a/docs/tutorials/pt/how-to-change-order-items.md
+++ b/docs/tutorials/pt/how-to-change-order-items.md
@@ -29,10 +29,8 @@ Há duas formas de realizar a alteração de um pedido:
 
 É possível editar itens que não foram faturados ainda em um pedido. Para adicionar novos itens, retirar itens, ou mudar a quantidade de cada um, confira os passos abaixo.  
 
-<div class = "alert alert-info">
-Para realizar a alteração, o pedido precisa estar no status <code>Preparando entrega</code>, equivalente ao status <code>handling</code> na <a href="https://developers.vtex.com/vtex-developer-docs/reference/orders#registerchange">API</a>. Para saber mais sobre status de pedidos, acesse o nosso artigo <a href="https://help.vtex.com/pt/tutorial/tabela-de-status-de-pedidos-oms--frequentlyAskedQuestions_773">Tabela de status de pedidos</a>.
-Confira a seção <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190#cuidados-e-limitacoes">Cuidados e limitações</a> para saber mais sobre as condições de uso da funcionalidade. 
-</div>
+>ℹ️ Para realizar a alteração, o pedido precisa estar no status `Preparando entrega`, equivalente ao status `handling` na [API](https://developers.vtex.com/vtex-developer-docs/reference/orders#registerchange). Para saber mais sobre status de pedidos, acesse o nosso artigo [Tabela de status de pedidos](https://help.vtex.com/pt/tutorial/tabela-de-status-de-pedidos-oms--frequentlyAskedQuestions_773).
+> Confira a seção [Cuidados e limitações](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190#cuidados-e-limitacoes) para saber mais sobre as condições de uso da funcionalidade.
 
 1. No Admin VTEX, acesse **Pedidos > Todos os pedidos**, ou digite **Todos os pedidos** na barra de busca no topo da página.      
 2. Busque o pedido pela barra de busca ou [utilizando os filtros](https://help.vtex.com/pt/tutorial/como-filtrar-pedidos--tutorials_192) e selecione o pedido desejado.      
@@ -58,6 +56,4 @@ Ao [alterar ou remover itens de um pedido](https://help.vtex.com/pt/tutorial/alt
 
 O valor total do pedido será atualizado após a inserção da nota fiscal, e corresponde ao que é captado pelo gateway de pagamentos da VTEX. Caso um item seja devolvido, o sistema de Pagamentos da VTEX fará o estorno automaticamente ao cliente.
 
-<div class = "alert alert-info">
-A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m">Payment Provider Protocol</a>. Conectores legados não possuem suporte à funcionalidade.
-</div>
+>ℹ️ A funcionalidade faturas parciais está disponível para toda a base de clientes VTEX, mas a liquidação parcial no gateway está em fase Beta. Além disso, para que as faturas parciais inseridas nos pedidos disparem liquidações parciais na transação, é necessário usar um conector que utiliza o [Payment Provider Protocol](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m). Conectores legados não possuem suporte à funcionalidade.
diff --git a/docs/tutorials/pt/how-to-change-orders-beta.md b/docs/tutorials/pt/how-to-change-orders-beta.md
index 8dc6dc899..528287124 100644
--- a/docs/tutorials/pt/how-to-change-orders-beta.md
+++ b/docs/tutorials/pt/how-to-change-orders-beta.md
@@ -77,9 +77,7 @@ Uma vez na página de detalhes do pedido, você pode realizar as seguintes alter
 * [Substituir itens](#substituir-itens)
 * [Alterar peso](#alterar-peso)
 
-<div class = "alert alert-info">
-É possível realizar uma única alteração no pedido ou combinar várias de uma só vez. Não existe um limite para quantas vezes um pedido pode ser alterado. Para mais informações, veja o artigo <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ">Como funciona a Alterar pedido (Beta)</a>.
-</div>
+>ℹ️ É possível realizar uma única alteração no pedido ou combinar várias de uma só vez. Não existe um limite para quantas vezes um pedido pode ser alterado. Para mais informações, veja o artigo [Como funciona a Alterar pedido (Beta)](https://help.vtex.com/pt/tutorial/como-funciona-a-alterar-pedido-beta--56TO0bOFXsfmpc7YZ3wIUZ).
 
 ### Adicionar itens
 
diff --git a/docs/tutorials/pt/how-to-configure-subscriptions.md b/docs/tutorials/pt/how-to-configure-subscriptions.md
index f3c86e013..6395205ae 100644
--- a/docs/tutorials/pt/how-to-configure-subscriptions.md
+++ b/docs/tutorials/pt/how-to-configure-subscriptions.md
@@ -15,9 +15,7 @@ legacySlug: como-configurar-assinatura-v2
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
-<div class = "alert alert-info">
-A instalação do módulo Assinaturas é feita por meio de solicitação ao <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ A instalação do módulo Assinaturas é feita por meio de solicitação ao [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 O sistema de __Assinaturas__ é um aplicativo desenvolvido pela VTEX para facilitar as vendas recorrentes. Funciona como um agendador automático, repetindo um pedido na frequência desejada pelo cliente da sua loja.
 
diff --git a/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md b/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md
index 56011c823..3739ca0ea 100644
--- a/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md
+++ b/docs/tutorials/pt/how-to-configure-xml-for-google-shopping.md
@@ -15,13 +15,9 @@ legacySlug: como-configurar-xml-do-google-shopping
 subcategory: 2OCA7SVfWoMSiAi0GEGwKo
 ---
 
-<div class = "alert alert-info">
- <p>Desenvolvemos um novo tipo de integração com o Google Shopping por API, que permite acompanhamento em tempo real. Saiba mais em <a href="https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw">Configurar integração com o Google Shopping</a>.</p>
-</div>
+>ℹ️ Desenvolvemos um novo tipo de integração com o Google Shopping por API, que permite acompanhamento em tempo real. Saiba mais em [Configurar integração com o Google Shopping](https://help.vtex.com/pt/tracks/configurar-integracao-com-o-google-shopping--25Sl7iOqq58PGfVfTAo8Xw).
 
-<div class = "alert alert-warning">
- <p>Este artigo se refere ao modelo de 22 de maio de 2013 de especificações do Google Shopping. O Google modifica e atualiza seu modelo sem prévio aviso. Portanto, sempre confirme se nossa explicação permanece atualizada segundo a <a href="https://support.google.com/merchants/answer/188494?hl=pt-BR">documentação do Google Shopping</a>.</p>
-</div>
+>⚠️ Este artigo se refere ao modelo de 22 de maio de 2013 de especificações do Google Shopping. O Google modifica e atualiza seu modelo sem prévio aviso. Portanto, sempre confirme se nossa explicação permanece atualizada segundo a [documentação do Google Shopping](https://support.google.com/merchants/answer/188494?hl=pt-BR).
 
 Você pode configurar o Google Shopping através do Admin VTEX, seguindo os passos abaixo:
 
@@ -39,6 +35,4 @@ Você pode configurar o Google Shopping através do Admin VTEX, seguindo os pass
 
 ![](https://images.contentful.com/alneenqid6w5/3boyluRWTYA4C0s4qkSG2I/28be460a5f8a6340f0b389fe5000b27c/2.png)
 
-<div class = "alert alert-warning">
-  <p>Caso a opção <strong>Exibir SKUs indisponíveis</strong> esteja desmarcada, os produtos ou SKUs que estiverem esgotados não aparecerão no XML. Produtos inativos também não aparecem no XML.</p>
-</div>
+>⚠️ Caso a opção **Exibir SKUs indisponíveis** esteja desmarcada, os produtos ou SKUs que estiverem esgotados não aparecerão no XML. Produtos inativos também não aparecem no XML.
diff --git a/docs/tutorials/pt/how-to-create-landing-pages-with-customized-urls.md b/docs/tutorials/pt/how-to-create-landing-pages-with-customized-urls.md
index 4dfff33e9..d9d335907 100644
--- a/docs/tutorials/pt/how-to-create-landing-pages-with-customized-urls.md
+++ b/docs/tutorials/pt/how-to-create-landing-pages-with-customized-urls.md
@@ -15,9 +15,7 @@ legacySlug: como-funciona-o-contexto-de-busca, como-funciona-o-contexto-de-busca
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 <div style="background-color:#FCF8F2; border-left: 2px solid #F0AD4E; border-top-left-radius: 2px; border-bottom-left-radius: 2px; padding: 15px; margin-bottom: 10px">
 Tutorial válido apenas para lojas CMS Portal Legado.
diff --git a/docs/tutorials/pt/how-to-delete-a-collection.md b/docs/tutorials/pt/how-to-delete-a-collection.md
index 710e5150c..c00302494 100644
--- a/docs/tutorials/pt/how-to-delete-a-collection.md
+++ b/docs/tutorials/pt/how-to-delete-a-collection.md
@@ -15,9 +15,7 @@ legacySlug: como-deletar-colecao
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 ## Via Admin
 Não é possível deletar totalmente uma coleção pelo Admin.
diff --git a/docs/tutorials/pt/how-to-identify-an-order-split-from-omnichannel.md b/docs/tutorials/pt/how-to-identify-an-order-split-from-omnichannel.md
index cb9dfd9fd..017fea1bc 100644
--- a/docs/tutorials/pt/how-to-identify-an-order-split-from-omnichannel.md
+++ b/docs/tutorials/pt/how-to-identify-an-order-split-from-omnichannel.md
@@ -26,9 +26,7 @@ Quando é feito o split do pedido, um sufixo é adicionado ao código, como `-01
 
 > Exemplo: no ambiente do marketplace, o código do pedido com divisão é `527103869572-01` ou `v527103anml-01`. 
 
-<div class = "alert alert-info">
-O pedido realizado no marketplace tem um código identificador no ambiente dos sellers. Cada seller tem acesso restrito à sua própria parte do pedido e não dispõe de qualquer acesso aos pedidos de outros sellers.
-</div>
+>ℹ️ O pedido realizado no marketplace tem um código identificador no ambiente dos sellers. Cada seller tem acesso restrito à sua própria parte do pedido e não dispõe de qualquer acesso aos pedidos de outros sellers.
 
 O código identificador do pedido no ambiente do seller tem como base a mesma sequência usada no marketplace, com a adição do prefixo correspondente ao [ID do afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk2yOeMc0), o código de três consoantes que identifica o seller no marketplace.
 
diff --git a/docs/tutorials/pt/how-to-identify-order-closing-errors.md b/docs/tutorials/pt/how-to-identify-order-closing-errors.md
index a0c26f0dd..bd7cba8d8 100644
--- a/docs/tutorials/pt/how-to-identify-order-closing-errors.md
+++ b/docs/tutorials/pt/how-to-identify-order-closing-errors.md
@@ -19,8 +19,6 @@ Sempre que o usuário clica em fechar pedido, o checkout cria um novo pedido na
 
 E como todo pedido tem, no mínimo, uma transação, também é possível encontrar essa transação em **Pedidos > Transações**. Por ser um cenário de erro, provavelmente já estará como transação cancelada.
 
-<div class = "alert alert-info">
-A recomendação é para todo erro de pedido, o primeiro local a se consutar é o log das transações em <b>Pedidos > Transações</b>. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/how-to-view-the-orders-details">Visualizar detalhes da transação em Pedidos</a>.
-</div>
+>ℹ️ A recomendação é para todo erro de pedido, o primeiro local a se consutar é o log das transações em **Pedidos > Transações**. Saiba mais em [Visualizar detalhes da transação em Pedidos](https://help.vtex.com/pt/tutorial/how-to-view-the-orders-details).
 
 A mensagem de erro exibida para o cliente pode ser gerada por diferentes motivos. Desde erros internos, como falha em efetuar uma reserva de um item, até problemas com o cartão, como dados incompletos, ou mesmo uma resposta do gateway, como dados inseridos errados.
diff --git a/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md b/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
index defb71d61..9a4b44744 100644
--- a/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
+++ b/docs/tutorials/pt/how-to-identify-promotions-applied-to-the-cart.md
@@ -44,9 +44,7 @@ Porém, caso mais de uma promoção seja aplicada, o que aparecerá será apenas
 
 ## orderForm
 
-<div class = "alert alert-warning">
-  <p>Para realizar a investigação documentada nesta seção, é necessário utilizar o Google Chrome. Por se tratar de uma ferramenta externa à VTEX, ela pode ser atualizada sem aviso prévio.</p>
-</div>
+>⚠️ Para realizar a investigação documentada nesta seção, é necessário utilizar o Google Chrome. Por se tratar de uma ferramenta externa à VTEX, ela pode ser atualizada sem aviso prévio.
 
 Na página do carrinho, você pode verificar o orderForm, que é um arquivo em formato JSON com todas as informações correspondentes ao pedido que está sendo criado.
 
diff --git a/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md b/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
index 2b6c45ac0..0db497065 100644
--- a/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
+++ b/docs/tutorials/pt/how-to-include-a-collection-of-products-in-the-shop-window.md
@@ -15,9 +15,7 @@ legacySlug: como-incluir-uma-colecao-de-produtos-na-vitrine-da-loja
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 As vitrines são utilizadas no destaque de produtos em diversas páginas, elas também podem ser utilizadas para recomendações, na página do produto.
 
diff --git a/docs/tutorials/pt/how-to-integrate-with-facebook.md b/docs/tutorials/pt/how-to-integrate-with-facebook.md
index 62f64beda..57a13c73f 100644
--- a/docs/tutorials/pt/how-to-integrate-with-facebook.md
+++ b/docs/tutorials/pt/how-to-integrate-with-facebook.md
@@ -43,7 +43,7 @@ __Id do business manager__: ID da conta do __Business Manager__ do Facebook, que
 
 __URL do site da loja__: Preencha com o endereço da sua loja. Exemplo: `https://www.sualoja.com.br`. Este campo é usado para formar a URL completa do produto que é enviado.
 
-<div class = "alert alert-info">Todos os campos são obrigatórios para o pleno funcionamento da integração.</div>
+>ℹ️ Todos os campos são obrigatórios para o pleno funcionamento da integração.
 
 ## Autorização
 
diff --git a/docs/tutorials/pt/how-to-manage-subscriptions.md b/docs/tutorials/pt/how-to-manage-subscriptions.md
index 14359a1e8..3e335c00f 100644
--- a/docs/tutorials/pt/how-to-manage-subscriptions.md
+++ b/docs/tutorials/pt/how-to-manage-subscriptions.md
@@ -39,9 +39,7 @@ A seção **Assinaturas Únicas** permite:
 
 ### Pedidos de Assinatura
 
-<div class = "alert alert-info">
-É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 A seção **Pedidos de Assinatura** permite:
 
diff --git a/docs/tutorials/pt/how-to-manually-invoice-an-order.md b/docs/tutorials/pt/how-to-manually-invoice-an-order.md
index cbb51d914..3852c30b3 100644
--- a/docs/tutorials/pt/how-to-manually-invoice-an-order.md
+++ b/docs/tutorials/pt/how-to-manually-invoice-an-order.md
@@ -24,9 +24,7 @@ Faturar o pedido na plataforma VTEX significa inserir a nota fiscal dos itens no
 * Via [API](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice) de envio de fatura.
 * Via Admin VTEX.
 
-<div class = "alert alert-info">
-No momento de faturar um pedido, é possível alterar a <a href="https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE">transportadora</a> associada ao pedido. Para isso na etapa de preenchimento do <b>Rastreamento do pedido</b>, clique em <i>Transportadora</i> e selecione a opção desejada.
-</div>
+>ℹ️ No momento de faturar um pedido, é possível alterar a [transportadora](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) associada ao pedido. Para isso na etapa de preenchimento do **Rastreamento do pedido**, clique em <i>Transportadora</i> e selecione a opção desejada.
 
 Para enviar a fatura pelo Admin VTEX, realize os seguintes passos:
 
diff --git a/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md b/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
index 129d3fd57..767ded72b 100644
--- a/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
+++ b/docs/tutorials/pt/how-to-optimize-searches-with-substitute-words.md
@@ -15,16 +15,12 @@ legacySlug: otimizar-as-buscas-com-palavras-substitutas
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-As operações da configuração <a href="https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete">Palavras Substitutas</a> não são recomendadas para a sua loja em caso de utilização do Intelligent Search. Para relacionar palavras ao produto, é recomendada a utilização da configuração de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">Sinônimos</a>, que possibilita uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso <a href="https://support.vtex.com/hc/pt-br/requests">Suporte</a>.
-</div>
+>⚠️ As operações da configuração [Palavras Substitutas](https://help.vtex.com/pt/tutorial/otimizar-as-buscas-com-palavras-substitutas--32FqSsl5VuQyiIMEc02Uwu?&utm_source=autocomplete) não são recomendadas para a sua loja em caso de utilização do Intelligent Search. Para relacionar palavras ao produto, é recomendada a utilização da configuração de [Sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV), que possibilita uma gestão mais escalável de termos por produto. Para mais informações, entre em contato com nosso [Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 ## Como funciona o buscador
 O buscador da VTEX possui um algoritmo inteligente que, a partir do termo de busca, identifica qual é o melhor resultado para apresentar ao usuário, ou seja, a ele é apresentado sempre o resultado que gerará mais conversão de venda.
 
-<div class = "alert alert-info">
-Veja mais detalhes de <a href="https://help.vtex.com/pt/tutorial/como-funciona-a-busca-da-vtex--tutorials_542">como funciona a busca</a> na VTEX.
-</div>
+>ℹ️ Veja mais detalhes de [como funciona a busca](https://help.vtex.com/pt/tutorial/como-funciona-a-busca-da-vtex--tutorials_542) na VTEX.
 
 ## Para que serve uma palavra substituta
 Se o sistema de busca não identifica Landing Page, Marca ou Departamento de acordo com o termo buscado, aplica uma Busca por Palavra Substituta (palavra chave). 
diff --git a/docs/tutorials/pt/how-to-return-order-items.md b/docs/tutorials/pt/how-to-return-order-items.md
index 375fe4bec..df8e11333 100644
--- a/docs/tutorials/pt/how-to-return-order-items.md
+++ b/docs/tutorials/pt/how-to-return-order-items.md
@@ -40,6 +40,4 @@ A página de **Detalhes do Pedido** permite orquestrar essa operação, seguindo
 
 Após o reembolso ser processado pelo sistema, os itens devolvidos e suas informações aparecerão na seção **Itens Devolvidos**.
 
-<div class = "alert alert-info">
-A alteração de pedidos via API é feita pelo endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes">Create order change</a> e a emissão de faturas após alterações é feita pelo endpoint <a href="https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice">Order invoice notification</a>.
-</div>
+>ℹ️ A alteração de pedidos via API é feita pelo endpoint [Create order change](https://developers.vtex.com/docs/api-reference/orders-api#patch-/api/order-system/orders/-changeOrderId-/changes) e a emissão de faturas após alterações é feita pelo endpoint [Order invoice notification](https://developers.vtex.com/docs/api-reference/orders-api#post-/api/oms/pvt/orders/-orderId-/invoice).
diff --git a/docs/tutorials/pt/how-to-use-rebates.md b/docs/tutorials/pt/how-to-use-rebates.md
index 320cf22d1..d53d97cbc 100644
--- a/docs/tutorials/pt/how-to-use-rebates.md
+++ b/docs/tutorials/pt/how-to-use-rebates.md
@@ -25,9 +25,7 @@ Todo esse cenário além de fortalecer os relacionamentos entre fornecedores e r
 
 A maneira mais apropriada para utilizar o rebate recebido dos fornecedores é por meio de [Promoções Regulares](https://help.vtex.com/pt/tracks/promocoes--6asfF1vFYiZgTQtOzwJchR/7FjbeZdE2KMwk5L1t98pZI#) com restrições de uso requeridas. Para saber mais sobre as possibilidades da Promoção Regular, leia nosso artigo de [Exemplos de promoção](https://help.vtex.com/pt/tutorial/exemplos-de-promocao--5A8UTc7knvAscxo7e7rMFD).
 
-<div class = "alert alert-warning">
-  <p>O cliente pode eventualmente cancelar a compra de um pedido com desconto do rebate. Nesse caso, é preciso redirecionar a promoção para outro cliente para, assim, atingir o total dos créditos. Para verificar se o rebate foi aplicado a um pedido, use os endpoints <a href = "https://developers.vtex.com/vtex-developer-docs/reference/user-orders#userorderslist">Retrieve User's orders</a> ou <a href="https://developers.vtex.com/vtex-developer-docs/reference/orders#getorder">Get Order</a> da Orders API.</p>
-</div>
+>⚠️ O cliente pode eventualmente cancelar a compra de um pedido com desconto do rebate. Nesse caso, é preciso redirecionar a promoção para outro cliente para, assim, atingir o total dos créditos. Para verificar se o rebate foi aplicado a um pedido, use os endpoints <a href = "https://developers.vtex.com/vtex-developer-docs/reference/user-orders#userorderslist">Retrieve User's orders</a> ou [Get Order](https://developers.vtex.com/vtex-developer-docs/reference/orders#getorder) da Orders API.
 
 ## Exemplo
 
diff --git a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
index 8d833a66f..519d2203b 100644
--- a/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
+++ b/docs/tutorials/pt/how-to-work-with-different-layouts-for-the-same-page.md
@@ -15,9 +15,7 @@ legacySlug: como-trabalhar-com-diferentes-layouts-para-uma-mesma-pagina
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 Na página __Storefront__ > __Layout__, um layout padrão é aplicado para todas as páginas de mesmo tipo existentes dentro de cada pasta de um website, como por exemplo _Produto_.
 
diff --git a/docs/tutorials/pt/i-cant-import-the-price-table.md b/docs/tutorials/pt/i-cant-import-the-price-table.md
index 42de3697b..b03eebd6f 100644
--- a/docs/tutorials/pt/i-cant-import-the-price-table.md
+++ b/docs/tutorials/pt/i-cant-import-the-price-table.md
@@ -19,9 +19,7 @@ __Tags/Palavras-chave__: *planilha de preços, importação de planilhas, célul
 
 As [tabelas ou planilhas de preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/1wAm5m3IUfIj6maBdaRJt8) armazenam informações de SKUs que após serem aplicadas em determinados contextos, tais como políticas comerciais, promoções ou cluster de clientes, permitem calcular os valores de venda dos produtos em uma loja VTEX. Para mais informações, acesse [Preço base](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3XcXp0r5WrJvogB8KIX4Kx) e [Preço fixo](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/3HxF2u5VwidqnUGnFoKdDy). 
 
-<div class ="alert alert-warning">
-  Não é possível importar uma planilha de <b>Preço calculado</b> no Admin VTEX. A função <b>Exportar</b> está disponível para esta planilha apenas para que o lojista possa conferir os valores de preço final de cada produto.
-</div>
+>⚠️ Não é possível importar uma planilha de **Preço calculado** no Admin VTEX. A função **Exportar** está disponível para esta planilha apenas para que o lojista possa conferir os valores de preço final de cada produto.
 
 Após [importar uma planilha de preços](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP/5lV5s54lQ69zPXxngbpI5D), algumas mensagens de erro podem surgir em determinados SKUs, como nos exemplos abaixos: 
 
@@ -50,9 +48,7 @@ Confira se os campos de sua planilha estão devidamente preenchidos conforme as
 - [Planilha de preço-base](https://help.vtex.com/pt/tutorial/preencher-campos-da-planilha-de-importacao-de-precos-base--4Jox8TeQ5feqAn78TZ0DNA)
 - [Planilha de preço fixo](https://help.vtex.com/pt/tutorial/preencher-campos-da-planilha-de-importacao-de-precos-fixo--50RFoH3ruV97FJgeBUCURh)
 
-<div class ="alert alert-warning">
-  Antes de importar a planilha no Admin VTEX, certifique-se de que a mesma não contenha colunas com informações de erro (<b>Error Code</b> e <b>Error Message</b>) ou que exista algum tipo de filtro aplicado nas células. Caso você tente importar a planilha nestas condições, podem ocorrer erros no processo de importação dos dados.
-</div>
+>⚠️ Antes de importar a planilha no Admin VTEX, certifique-se de que a mesma não contenha colunas com informações de erro (**Error Code** e **Error Message**) ou que exista algum tipo de filtro aplicado nas células. Caso você tente importar a planilha nestas condições, podem ocorrer erros no processo de importação dos dados.
 
 Exemplo de planilha com filtros aplicados e campos __Error Code__ e __Error Message__ presentes:
 
@@ -62,6 +58,4 @@ Exemplo de planilha com filtros aplicados e campos __Error Code__ e __Error Mess
 
 Planilhas de preço devem possuir um limite máximo de tamanho de 1 megabyte (MB). Caso a sua planilha atual seja maior que este valor, divida as informações em planilhas de tamanho inferior a 1 megabyte (MB).
 
-<div class ="alert alert-warning">
-  Todos os dados de um SKU específico devem ser mantidos na mesma planilha, não sendo permitido o cadastro de informações do mesmo SKU em planilhas diferentes.
-</div>
+>⚠️ Todos os dados de um SKU específico devem ser mantidos na mesma planilha, não sendo permitido o cadastro de informações do mesmo SKU em planilhas diferentes.
diff --git a/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md b/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
index adcb246f0..28781ce8f 100644
--- a/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
+++ b/docs/tutorials/pt/i-cant-receive-emails-from-vtex.md
@@ -62,9 +62,7 @@ Após o teste, caso a mensagem da VTEX não tenha sido enviada para o email do u
 
 Confira se o servidor SMTP externo está devidamente configurado conforme o [sistema SPF](https://help.vtex.com/pt/tutorial/configuracao-de-spf--42t0lkl2VyC6Yewc4wA6wI), responsável por evitar que servidores não autorizados enviem emails em nome de um domínio específico. Caso necessário, você pode realizar a [configuração do SPF](https://developers.vtex.com/docs/guides/setting-up-the-spf) e da [DKIM](https://developers.vtex.com/docs/guides/setting-up-dkim-for-transactional-emails) (DomainKeys Identified Mail) no servidor.
 
-<div class ="alert alert-warning">
-Acesse também a sua caixa de spam para garantir que os emails da VTEX não estão sendo enviados para este local. Isto pode ocorrer devido a regras internas de servidores de mail.
-</div>
+>⚠️ Acesse também a sua caixa de spam para garantir que os emails da VTEX não estão sendo enviados para este local. Isto pode ocorrer devido a regras internas de servidores de mail.
 
 ### Configuração da notificação de pedido e pagamento
 
@@ -82,9 +80,7 @@ A Amazon (AWS) possui uma plataforma de email chamada Amazon Simple Email Servic
 
 Em situações normais, um endereço de email pode ser incluído na lista de supressão da AWS e ser removido após aproximadamente 12 horas. Durante este período, emails enviados pela VTEX não serão recebidos pelo endereço de email incluído na lista.
 
-<div class ="alert alert-warning">
-A gestão da lista de supressão é de responsabilidade da AWS, e a VTEX não tem responsabilidade sobre a movimentação de entrada e saída de endereços na lista.
-</div>
+>⚠️ A gestão da lista de supressão é de responsabilidade da AWS, e a VTEX não tem responsabilidade sobre a movimentação de entrada e saída de endereços na lista.
 
 Caso desconfie que o seu endereço de email tenha sido bloqueado pela AWS, aguarde o período de 12 horas e tente reenviar novamente um email para o endereço bloqueado.
 
diff --git a/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md b/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
index c4d643b0e..62700ccd1 100644
--- a/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
+++ b/docs/tutorials/pt/i-cant-view-the-product-in-the-search-results.md
@@ -47,9 +47,7 @@ A ausência do produto em um resultado de busca pode ser atribuída ao preenchim
 
 <blockquote><ui>1. No Admin VTEX, acesse </b>Catálogo > Todos os produtos</b>.</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Lojas que utilizam a página <b>Produtos e SKUS (Beta)</b>, devem verificar os campos de cadastro do produto acessando <b>Catálogo > Produtos e SKUS</b> no Admin VTEX. Saiba mais em <a href="https://help.vtex.com/pt/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By">Produtos e SKUS (Beta)</a>.
-</div></blockquote>
+<blockquote><ui>>⚠️ Lojas que utilizam a página **Produtos e SKUS (Beta)**, devem verificar os campos de cadastro do produto acessando **Catálogo > Produtos e SKUS** no Admin VTEX. Saiba mais em [Produtos e SKUS (Beta)](https://help.vtex.com/pt/tutorial/products-and-skus-beta--2ig7TmROlirWirZjFWZ3By).</blockquote>
 
 <blockquote><ui>2. Localize o produto desejado e clique em <b>EDITAR</b>.</ui>
 
@@ -63,9 +61,7 @@ A ausência do produto em um resultado de busca pode ser atribuída ao preenchim
 
 <blockquote><ui>7. Acesse o site da loja, digite o termo desejado e verifique se os produtos exibidos no resultado da busca são iguais aos produtos disponíveis na página <b>Explicação da busca</b> do Intelligent Search (<b>Storefront > Intelligent Search > Explicação da busca</b>).</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Se o termo de busca estiver presente no nome ou descrição do produto, mas o produto for de uma marca diferente do termo especificado na busca, prossiga com as demais etapas para solucionar o problema.
-</div></blockquote>
+<blockquote><ui>>⚠️ Se o termo de busca estiver presente no nome ou descrição do produto, mas o produto for de uma marca diferente do termo especificado na busca, prossiga com as demais etapas para solucionar o problema.</blockquote>
 
 ### Modificação do filtro da busca no Rewriter
 
@@ -123,9 +119,7 @@ internal {
 }
 ```
 
-<blockquote><ui><div class ="alert alert-warning">
-  O valor <i>ft</i> (full text) ao invés de <i>b</i> (brand) no parâmetro <i>map</i> indica que produtos em que o termo <i>Pendleton</i> esteja presente no nome ou na descrição também passarão a ser exibidos na busca.
-</div></blockquote>
+<blockquote><ui>>⚠️ O valor <i>ft</i> (full text) ao invés de <i>b</i> (brand) no parâmetro <i>map</i> indica que produtos em que o termo <i>Pendleton</i> esteja presente no nome ou na descrição também passarão a ser exibidos na busca.</blockquote>
 
 <blockquote><ui>7. Clique na seta do GraphiQL IDE (ao lado de <b>GraphiQL</b>) para realizar a atualização do filtro de busca. O novo padrão de filtro de busca para o termo será confirmada pela exibição da seguinte mensagem no campo de resultados do GraphiQL IDE.</ui>
 
@@ -154,8 +148,7 @@ internal {
 
 <blockquote><ui>8. Acesse o site da loja, digite o termo desejado e verifique se os produtos exibidos no resultado da busca são iguais aos produtos disponíveis na página <b>Explicação da busca</b> do Intelligent Search (<b>Storefront > Intelligent Search > Explicação da busca</b>).</ui>
 
-<blockquote><ui><div class ="alert alert-warning">
-  Se o termo de busca estiver relacionado a uma marca que não existe mais em seu site, será necessário remover a rota interna de busca dentro do app Rewriter conforme descrito na solução abaixo.</div></blockquote>
+<blockquote><ui>>⚠️ Se o termo de busca estiver relacionado a uma marca que não existe mais em seu site, será necessário remover a rota interna de busca dentro do app Rewriter conforme descrito na solução abaixo.</blockquote>
 
 ### Remoção da rota interna de busca no Rewriter
 
diff --git a/docs/tutorials/pt/importing-amazon-classic-fba-orders.md b/docs/tutorials/pt/importing-amazon-classic-fba-orders.md
index aef82d42f..409af116d 100644
--- a/docs/tutorials/pt/importing-amazon-classic-fba-orders.md
+++ b/docs/tutorials/pt/importing-amazon-classic-fba-orders.md
@@ -53,9 +53,7 @@ Após criar a especificação de produto, seu produto estará ativo para os pedi
 
 ### 2. Definir Estratégia de Envio para Pedidos FBA Classic
 
-<div class = "alert alert-info">
-É importante assegurar que a política comercial utilizada é específica para a Amazon. Dessa forma, você garante que o estoque criado não será utilizado por outra integração.
-</div>
+>ℹ️ É importante assegurar que a política comercial utilizada é específica para a Amazon. Dessa forma, você garante que o estoque criado não será utilizado por outra integração.
 
 Para dar continuidade à configuração, é preciso determinar uma [Estratégia de Envio](https://help.vtex.com/pt/tutorial/estrategia-de-envio--58vLBDbjYVQzJ6rRc5QNz3) exclusiva para o FBA Classic, ou seja, informar qual será a operação de entrega de seus produtos. Dessa forma, você não influenciará na estratégia de envio já definida na etapa Definir Estratégia de Envio na Amazon.
 
diff --git a/docs/tutorials/pt/importing-amazon-dba-orders.md b/docs/tutorials/pt/importing-amazon-dba-orders.md
index 0a21b032a..6e038d78d 100644
--- a/docs/tutorials/pt/importing-amazon-dba-orders.md
+++ b/docs/tutorials/pt/importing-amazon-dba-orders.md
@@ -15,9 +15,7 @@ legacySlug: importacao-de-pedidos-amazon-dba
 subcategory: 4uqMnZjwBO04uWgCom8QiA
 ---
 
-<div class = "alert alert-info">
-A funcionalidade Importação de Pedidos Amazon DBA está disponível apenas para sellers VTEX Brasil.  
-</div>  
+>ℹ️ A funcionalidade Importação de Pedidos Amazon DBA está disponível apenas para sellers VTEX Brasil.  
 
 Existem três tipos de configuração logística para atender aos pedidos realizados na Amazon:
 
diff --git a/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md b/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md
index b5825caa4..61be36873 100644
--- a/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md
+++ b/docs/tutorials/pt/importing-and-exporting-an-inventory-spreadsheet.md
@@ -68,6 +68,4 @@ A seguir, confira o significado de cada campo da planilha de estoque.
 - **LockIds** (texto): Código identificador da reserva.  
 - **DispatchedReservations** (número): número de itens do SKU que já passaram do status `Pronto para manuseio`, ou seja, cujas reservas já caíram.  
 
-<div class = "alert alert-info">
-  Para incluir um item com estoque infinito, é preciso preencher o campo <b>TotalQuantity</b> com o valor <code>1000000</code> e alterar o campo <b>UnlimitedQuantity</b> para <code>True</code>. 
-</div>
+>ℹ️ Para incluir um item com estoque infinito, é preciso preencher o campo **TotalQuantity** com o valor `1000000` e alterar o campo **UnlimitedQuantity** para `True`.
diff --git a/docs/tutorials/pt/integrating-with-loopi.md b/docs/tutorials/pt/integrating-with-loopi.md
index f1e817c18..3d00a2291 100644
--- a/docs/tutorials/pt/integrating-with-loopi.md
+++ b/docs/tutorials/pt/integrating-with-loopi.md
@@ -56,9 +56,7 @@ Para configurar a integração e ser capaz de cadastrar e mapear corretamente se
 - [Status de pedidos na Loopi](https://help.vtex.com/pt/tutorial/integracao-com-loopi--2wmap3hWksLxJ0IYe7nYFP#status-de-pedidos-na-loopi)
 - [Operação logística na Loopi](https://help.vtex.com/pt/tutorial/integracao-com-loopi--2wmap3hWksLxJ0IYe7nYFP#operacao-logistica-na-loopi)
 
-<div class = "alert alert-info">
-Para anunciar e vender na Loopi é necessário estar em conformidade com os <a href="https://loopi.shop/termos-de-uso">termos e condições legais do marketplace</a>.
-</div>
+>ℹ️ Para anunciar e vender na Loopi é necessário estar em conformidade com os [termos e condições legais do marketplace](https://loopi.shop/termos-de-uso).
 
 ### Cadastramento de produtos na Loopi
 
@@ -127,9 +125,7 @@ O consumidor é notificado sobre todas as mudanças de _status_ de pedidos. As n
 
 O cálculo de frete e o prazo de entrega dos pedidos é fechado no ambiente da Loopi, no momento da compra. As configurações logísticas serão aquelas que você escolher na Estratégia de Envio definida para a integração. Essa configuração será feita adiante, como parte da etapa de configurações no seu Admin VTEX.
 
-<div class = "alert alert-info">
-O fullfilment, ou seja, a responsabilidade da entrega do pedido ao cliente, é responsabilidade da loja VTEX.
-</div>
+>ℹ️ O fullfilment, ou seja, a responsabilidade da entrega do pedido ao cliente, é responsabilidade da loja VTEX.
 
 ## Configurações na plataforma VTEX
 
@@ -236,9 +232,7 @@ Dentro do mapeamento de um atributo, seja ele _cor_ ou _tamanho_, existe o campo
 
 Para ter certeza de que todas as categorias da sua loja VTEX foram mapeadas corretamente na Loopi, você deve ser capaz de visualizar no _Loopi Mapper_ o ícone de _mapeamento completo_ ao longo de toda a lista de categorias da sua loja VTEX.
 
-<div class = "alert alert-info">
-Em seu canal no Youtube, a Loopi disponibiliza o <a href="https://www.youtube.com/watch?v=ryfqmh8qpo4">vídeo Mapeamento de categorias</a>, no qual apresenta um exemplo de item de moda sendo mapeado.
-</div>
+>ℹ️ Em seu canal no Youtube, a Loopi disponibiliza o [vídeo Mapeamento de categorias](https://www.youtube.com/watch?v=ryfqmh8qpo4), no qual apresenta um exemplo de item de moda sendo mapeado.
 
 #### Mapeamento de especificações
 
@@ -250,9 +244,7 @@ Após realizar o mapeamento de categorias, variações e atributos dos seus prod
 
 Após a realização da carga inicial, a integração da sua loja VTEX com o marketplace estará concluída.
 
-<div class = "alert alert-info">
-Em caso de dúvidas, entre em contato com a Loopi pelo email <i>contato@loopi.shop</i>.
-</div>
+>ℹ️ Em caso de dúvidas, entre em contato com a Loopi pelo email <i>contato@loopi.shop</i>.
 
 <br></br>
 ### Saiba mais
diff --git a/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md b/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md
index c8a5f7b16..1eb36e3a5 100644
--- a/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md
+++ b/docs/tutorials/pt/integration-guide-for-marketplaces-marketplace-non-vtex.md
@@ -52,9 +52,7 @@ Neste artigo, você confere a visão geral do processo de integração de ambos
 
 3) Marketplace busca preço, estoque e dados de frete do SKU pela API de Fullfillment.  
 
-<div class = "alert alert-info">
-Saiba mais na documentação para desenvolvedores <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">External Marketplace</a>.
-</div>
+>ℹ️ Saiba mais na documentação para desenvolvedores [External Marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
 
 ## B) Fluxo referente ao Envio e Processamento de Pedidos 
 
@@ -92,6 +90,4 @@ O fluxo de integrações referente ao envio e processamento de pedidos pode ser
 
 6) Enviar solicitação de cancelamento.
 
-<div class = "alert alert-info">
-Saiba mais na documentação para desenvolvedores <a href="https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide">External Marketplace</a>.
-</div>
+>ℹ️ Saiba mais na documentação para desenvolvedores [External Marketplace](https://developers.vtex.com/vtex-rest-api/docs/external-marketplace-integration-guide).
diff --git a/docs/tutorials/pt/interaction-details.md b/docs/tutorials/pt/interaction-details.md
index 51fd2348f..69efaa238 100644
--- a/docs/tutorials/pt/interaction-details.md
+++ b/docs/tutorials/pt/interaction-details.md
@@ -33,9 +33,7 @@ A página **Detalhes da interação** apresenta as seguintes seções:
 - [Resultado da Interação](#resultado-da-interacao)    
 - [Linha do tempo](#linha-do-tempo)     
 
-<div class = "alert alert-info">
-O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre</a> (Classic e Premium), <a href="https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> e marketplaces VTEX. Para conectores que desejam integrar via API, existe o <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Guia de integração da Gerenciamento de anúncios</a>.
-</div>
+>ℹ️ O **Gerenciamento de anúncios** permite acompanhar anúncios com o [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic e Premium), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e marketplaces VTEX. Para conectores que desejam integrar via API, existe o [Guia de integração da Gerenciamento de anúncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Cabeçalho
 ![Interaction details PT cabeçalho](https://images.ctfassets.net/alneenqid6w5/7zEocS2MW5dSRzZaaqNDUc/13e23260eaabde52ec1c38246a05be68/Interaction_details_PT_cabe__alho.jpg)
diff --git a/docs/tutorials/pt/inventory-update-history.md b/docs/tutorials/pt/inventory-update-history.md
index 3feadb095..47b3bbd65 100644
--- a/docs/tutorials/pt/inventory-update-history.md
+++ b/docs/tutorials/pt/inventory-update-history.md
@@ -19,11 +19,9 @@ O inventário contém as informações dos produtos que a loja possui para venda
 
 Esse artigo contém as instruções para acessar o histórico de movimentações do inventário pelo Admin VTEX. 
 
-<div class = "alert alert-info">
-Não esqueça da diferença entre estoque e inventário:
-  <p> <b><a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque:</a></b> nome dado para os locais de armazenamento da loja.
-<p>  <b>Inventário:</b> relação dos SKUs e os estoques em que estão armazenados.
-</div>
+>ℹ️ Não esqueça da diferença entre estoque e inventário:
+>   <p> **[Estoque:](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb)** nome dado para os locais de armazenamento da loja.
+> <p>  **Inventário:** relação dos SKUs e os estoques em que estão armazenados.
 
 Para visualizar as movimentações de um SKU:
 
diff --git a/docs/tutorials/pt/is-it-possible-to-use-the-vtex-admin-search-report.md b/docs/tutorials/pt/is-it-possible-to-use-the-vtex-admin-search-report.md
index 908e6a25f..73b39fa6a 100644
--- a/docs/tutorials/pt/is-it-possible-to-use-the-vtex-admin-search-report.md
+++ b/docs/tutorials/pt/is-it-possible-to-use-the-vtex-admin-search-report.md
@@ -15,9 +15,7 @@ legacySlug: e-possivel-usar-o-relatorio-de-busca-no-admin-da-vtex
 subcategory: 5yDQmr18K4GgQAeGwq8USa
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 O relatório de busca da VTEX que podia ser acessado pelo caminho __Relatórios > Busca__ foi descontinuado. 
 
diff --git a/docs/tutorials/pt/kabum-integration.md b/docs/tutorials/pt/kabum-integration.md
index 970d0675a..a0164d77d 100644
--- a/docs/tutorials/pt/kabum-integration.md
+++ b/docs/tutorials/pt/kabum-integration.md
@@ -83,9 +83,7 @@ O [afiliado](https://help.vtex.com/pt/tutorial/o-que-e-afiliado--4bN3e1YarSEammk
 
 ## Envio de informações para o KaBuM!
 
-<div class = "alert alert-info">
-O processo de onboarding com conectores certificados é responsabilidade dos próprios parceiros.
-</div>
+>ℹ️ O processo de onboarding com conectores certificados é responsabilidade dos próprios parceiros.
 
 Após concluir as configurações na plataforma VTEX, para dar prosseguimento a integração com o KaBuM!, você precisará possuir uma **chave de API da KaBuM!**. Caso não possua, saiba como obtê-la lendo o artigo da KaBuM! [Geração de chave de API](https://kabum.movidesk.com/kb/article/269610/geracao-de-chave-de-api).
 
diff --git a/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md b/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
index a369c086a..59f5fef76 100644
--- a/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
+++ b/docs/tutorials/pt/lead-time-shipping-time-at-sku-level.md
@@ -27,9 +27,7 @@ Este artigo aborda os seguintes aspectos:
 - [Configurar lead time:](#configurar-lead-time) como realizar a configuração pelo Admin VTEX.
 - [Configurar a contagem do lead time em dias do calendário:](#configurar-a-contagem-do-lead-time-em-dias-do-calendario-opcional) etapa opcional para que a contagem do lead time seja em dias corridos, e não dias úteis, que é o padrão.
 
-<div class = "alert alert-info">
-Para configurar o lead time por API, acesse <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>ℹ️ Para configurar o lead time por API, acesse [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## Tempo total de envio
 
@@ -83,9 +81,7 @@ Para configurar o lead time de um SKU, siga os passos abaixo:
   ![lead_time_inventory_management_PT](https://images.ctfassets.net/alneenqid6w5/mfWUVzj7tgHMQxJTnVjGX/37732ea98f52933cabb401cb6246ab2f/lead_time_inventory_management_PT.png)
 4. No canto inferior da página, clique em `Salvar`.
 
-<div class = "alert alert-info">
-Pelo Admin VTEX, o lead time é sempre configurado em dias, mas é possível configurar períodos em horas, minutos e segundos, usando o endpoint <a href="https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-">Update inventory by SKU and warehouse</a>.
-</div>
+>ℹ️ Pelo Admin VTEX, o lead time é sempre configurado em dias, mas é possível configurar períodos em horas, minutos e segundos, usando o endpoint [Update inventory by SKU and warehouse](https://developers.vtex.com/docs/api-reference/logistics-api#put-/api/logistics/pvt/inventory/skus/-skuId-/warehouses/-warehouseId-).
 
 ## Configurar a contagem do lead time em dias do calendário (opcional)
 
diff --git a/docs/tutorials/pt/license-manager-resources.md b/docs/tutorials/pt/license-manager-resources.md
index 982d9f1ff..58f8ffbe7 100644
--- a/docs/tutorials/pt/license-manager-resources.md
+++ b/docs/tutorials/pt/license-manager-resources.md
@@ -24,9 +24,7 @@ Por isso, a plataforma VTEX oferece a possibilidade de criar perfis de acessos c
 
 <iframe src="https://help.vtex.com/tables/resources/pt" title="Recursos do License Manager" frameBorder="0" width="100%" height="850"></iframe>
 
-<div class = "alert alert-info">
-  <p>No aplicativo <a href="https://help.vtex.com/pt/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA">Audit</a>, recursos do License Manager são identificados pelas respectivas chaves.</p>
-</div>
+>ℹ️ No aplicativo [Audit](https://help.vtex.com/pt/tutorial/audit--5RXf9WJ5YLFBcS8q8KcxTA), recursos do License Manager são identificados pelas respectivas chaves.
 
 ## Recursos internos ou deprecados
 
diff --git a/docs/tutorials/pt/loading-dock.md b/docs/tutorials/pt/loading-dock.md
index 954eee468..20d044f6b 100644
--- a/docs/tutorials/pt/loading-dock.md
+++ b/docs/tutorials/pt/loading-dock.md
@@ -21,16 +21,14 @@ Na VTEX, a doca é um intermediador entre o armazenamento de itens e a entrega d
 
 ![Doca PT](https://images.contentful.com/alneenqid6w5/4SyPLXtyDFTNbilUXZMsiM/b26625a316028e55b1f15c0c7e3433ee/Doca_PT.svg)
 
-<div class = "alert alert-info">
-O Estoque é o espaço físico de armazenamento das mercadorias vendidas pela loja; a Política comercial é a configuração das estratégias de venda da loja; e a Política de envio é um conjunto de regras que definem as opções e condições de frete.
-A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
-<body>
-<ol>
-<li><a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE">Política comercial</a>;</li>
-<li><a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140">Política de envio</a>;</li>
-<li>Doca;</li>
-<li><a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a>.</li>
-</div>
+>ℹ️ O Estoque é o espaço físico de armazenamento das mercadorias vendidas pela loja; a Política comercial é a configuração das estratégias de venda da loja; e a Política de envio é um conjunto de regras que definem as opções e condições de frete.
+> A ordem de cadastro sugerida na plataforma VTEX para o funcionamento esperado do sistema logístico é:
+> <body>
+> <ol>
+> <li>[Política comercial](https://help.vtex.com/pt/tutorial/criar-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE);</li>
+> <li>[Política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140);</li>
+> <li>Doca;</li>
+> <li>[Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb).</li>
 
 ## Casos de uso
 
diff --git a/docs/tutorials/pt/locations-details-page-beta.md b/docs/tutorials/pt/locations-details-page-beta.md
index 67b8b1351..f50e6a48b 100644
--- a/docs/tutorials/pt/locations-details-page-beta.md
+++ b/docs/tutorials/pt/locations-details-page-beta.md
@@ -37,9 +37,7 @@ Você acompanha em tempo real quanto da capacidade de cada dia foi utilizada e p
 
 Também é possível [aumentar a capacidade operacional](#aumentar-capacidade-operacional) da localidade pela página de detalhes.
 
-<div class = "alert alert-info">
-Para ver todas as ações que você pode realizar com localidades, veja o artigo <a href="https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy">Módulo Localidades</a>.
-</div>
+>ℹ️ Para ver todas as ações que você pode realizar com localidades, veja o artigo [Módulo Localidades](https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy).
 
 ## Ver histórico
 
diff --git a/docs/tutorials/pt/locations-module-beta.md b/docs/tutorials/pt/locations-module-beta.md
index 84bb518c5..a024db2b2 100644
--- a/docs/tutorials/pt/locations-module-beta.md
+++ b/docs/tutorials/pt/locations-module-beta.md
@@ -93,18 +93,14 @@ Para realizar esta etapa, siga os passos abaixo:
 
 1. Em **Gostaria de configurar uma capacidade?**, clique em umas das alternativas:</br><p><ul><li><b>Configurar:</b> a localidade tem um limite na capacidade de receber pedidos e, caso este limite seja atingido, novos pedidos podem ser alocados em outras localidades. Isso aumenta a eficiência da sua operação e aumenta as chances de cumprir as promessas de envio feitas aos clientes.</li><li><b>Manter ilimitada:</b> a localidade mantém a capacidade irrestrita de receber novos pedidos. Como não é possível determinar um limite máximo, a localidade pode receber mais pedidos do que é capaz de dar vazão no tempo de envio prometido, o que pode causar um atraso nos envios e consequente frustração de clientes.</li></ul></p>
 
-  <div class = "alert alert-info">
-Por padrão, as localidades são criadas sendo ilimitadas. Se você não deseja configurar a capacidade, você terá concluído a criação da nova localidade. Se você deseja configurá-la, prossiga com o passo a passo.
-</div>
+  >ℹ️ Por padrão, as localidades são criadas sendo ilimitadas. Se você não deseja configurar a capacidade, você terá concluído a criação da nova localidade. Se você deseja configurá-la, prossiga com o passo a passo.
 
 2. Em **Unidade da capacidade operacional**, escolha se a capacidade operacional será definida pelo número de _pedidos_ ou de _itens_. O número de itens considera os itens de todos os pedidos feitos no dia.
 3. Em **Capacidade**, determine qual a quantidade limite para os dias da semana. O sistema não restringe um valor máximo.
 4. Em **Regra**, escolha o que deve acontecer quando uma localidade atinge a capacidade máxima do dia:<br><p><ul><li><b>Continuar recebendo pedidos consumindo a capacidade dos dias seguintes:</b> a localidade continua válida para novos pedidos e eles são alocados na capacidade dos próximos dias. A promessa de envio dos novos pedidos será ajustada, mas não é possível configurar esse período em horas, por exemplo, porque ele vai corresponder automaticamente ao número de dias seguintes no qual for alocado.</li></ul></p>
   <p><ul><ul><li>Se você escolher esta opção, determine qual o <i>número de dias</i> seguintes para alocar os pedidos que ultrapassarem a capacidade do dia atual.</li></ul></ul></p>
 
-  <div class = "alert alert-info">
-Por exemplo, uma loja vende chocolates e sua capacidade operacional hoje foi 100% consumida. A loja continua recebendo novos pedidos, mas eles serão preparados só amanhã, porque o time não consegue preparar mais pedidos do que já previstos para hoje. No checkout, as promessas de envio de novos pedidos agora aparecem com um dia a mais de prazo, pois os pedidos serão preparados amanhã. Se a capacidade de amanhã for consumida ainda hoje, os novos pedidos serão alocados para depois de amanhã e preparados dali a dois dias, porque a loja configurou três dias para <b>Continuar recebendo pedidos consumindo a capacidade dos próximos dias</b>. Veja mais no artigo <a href="https://help.vtex.com/pt/tutorial/pagina-de-detalhes-da-localidade--3se4QBRYsNCwC8Wo56J6zG">Página de detalhes da localidade</a>.
-</div>
+  >ℹ️ Por exemplo, uma loja vende chocolates e sua capacidade operacional hoje foi 100% consumida. A loja continua recebendo novos pedidos, mas eles serão preparados só amanhã, porque o time não consegue preparar mais pedidos do que já previstos para hoje. No checkout, as promessas de envio de novos pedidos agora aparecem com um dia a mais de prazo, pois os pedidos serão preparados amanhã. Se a capacidade de amanhã for consumida ainda hoje, os novos pedidos serão alocados para depois de amanhã e preparados dali a dois dias, porque a loja configurou três dias para **Continuar recebendo pedidos consumindo a capacidade dos próximos dias**. Veja mais no artigo [Página de detalhes da localidade](https://help.vtex.com/pt/tutorial/pagina-de-detalhes-da-localidade--3se4QBRYsNCwC8Wo56J6zG).
 
   <ul><li><b>Desativar esta localidade até o final do dia:</b> uma vez que atinja o limite da sua capacidade, a localidade deixa de ser válida para novos pedidos no dia, sendo que estes pedidos são recebidos por outras localidades.</li></ul>
 5. Clique em `Salvar alterações`. 
@@ -144,9 +140,7 @@ Para editar a capacidade operacional de várias localidades, realize o passo a p
 
 Utilizando a barra de busca, você pode usar o nome da localidade para encontrá-la.
 
-<div class = "alert alert-info">
-É possível associar a busca com o <a href="https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy#filtrar-localidades">filtro por status</a>. Caso os resultados da sua busca retornem vazios, observe se não há um filtro ativo.
-</div>
+>ℹ️ É possível associar a busca com o [filtro por status](https://help.vtex.com/pt/tutorial/modulo-localidades--2thSYLMAS8KAd8V4XuBLSy#filtrar-localidades). Caso os resultados da sua busca retornem vazios, observe se não há um filtro ativo.
 
 ### Filtrar localidades
 
@@ -202,6 +196,4 @@ Para definir a melhor estratégia para o seu modelo de negócios e escolher se o
 * **Localidade atingiu** <i class="fas fa-exclamation-triangle"></i> **limite máximo:** uma localidade com o alerta 100% da capacidade consumida deixa de receber novos pedidos naquele dia. Porém, no dia seguinte, a capacidade de localidade é liberada e ela automaticamente recebe novos pedidos.
     > _Exemplo:_ na véspera do Natal, uma loja atingiu o limite máximo da sua capacidade do dia e a equipe não conseguiria preparar mais pedidos, portanto não valeria [aumentar a capacidade](#editar-capacidade-operacional). No dia seguinte, a equipe conseguiria preparar novos pedidos, portanto seria estratégico não editar a localidade, pois no dia seguinte ela automaticamente tem sua capacidade liberada e volta a receber novos pedidos.
 
-<div class = "alert alert-info">
-Quando você pausa uma localidade configurada com a regra <b>Continuar recebendo pedidos consumindo a capacidade dos próximos dias</b>, novos pedidos não são recebidos e, portanto, não podem ser alocados nos dias seguintes. Porém, localidades com essa configuração que ultrapassaram a capacidade do dia tem novos pedidos automaticamente alocados nos dias seguintes, inclusive com a promessa de envio aos clientes ajustada.
-</div>
+>ℹ️ Quando você pausa uma localidade configurada com a regra **Continuar recebendo pedidos consumindo a capacidade dos próximos dias**, novos pedidos não são recebidos e, portanto, não podem ser alocados nos dias seguintes. Porém, localidades com essa configuração que ultrapassaram a capacidade do dia tem novos pedidos automaticamente alocados nos dias seguintes, inclusive com a promessa de envio aos clientes ajustada.
diff --git a/docs/tutorials/pt/making-product-collections-searchable.md b/docs/tutorials/pt/making-product-collections-searchable.md
index fc476ada1..ca23103e4 100644
--- a/docs/tutorials/pt/making-product-collections-searchable.md
+++ b/docs/tutorials/pt/making-product-collections-searchable.md
@@ -15,17 +15,13 @@ legacySlug: tornar-colecao-de-produtos-encontravel-pela-busca
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Este artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Este artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Você pode fazer com que, ao buscar pelo nome de uma coleção na busca da loja, o usuário encontre os produtos dessa coleção.
 
 Por exemplo: digamos que você tenha uma coleção chamada "Dia das crianças", e que você marque esta coleção como buscável. Se um cliente da loja buscar pelo termo "Dia das crianças", os produtos que fazem parte dessa coleção serão renderizados no resultado de busca.
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 Para tornar uma coleção buscável, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/managing-delivery-capacity.md b/docs/tutorials/pt/managing-delivery-capacity.md
index 845ba3a68..a303881f4 100644
--- a/docs/tutorials/pt/managing-delivery-capacity.md
+++ b/docs/tutorials/pt/managing-delivery-capacity.md
@@ -34,6 +34,4 @@ Uma vez selecionada a política de envio e a data a serem apresentadas na lista,
 *   **Disponível**: quantos itens/pedidos ainda estão disponíveis para agendamento (a quantidade de capacidade menos reservado)
 *   **Status**: pode ser visível ou não visível, dependendo da janela de entrega ainda está disponível. A janela ficará com status visível para seus clientes se ela ainda estiver disponível.
 
-<div class = "alert alert-info">
-Você pode clicar em <b>EDITAR POLÍTICA DE ENVIO</b> para ser redirecionado à tela de edição da política de envio selecionada no filtro Política de envio.
-</div>
+>ℹ️ Você pode clicar em **EDITAR POLÍTICA DE ENVIO** para ser redirecionado à tela de edição da política de envio selecionada no filtro Política de envio.
diff --git a/docs/tutorials/pt/managing-http-headers.md b/docs/tutorials/pt/managing-http-headers.md
index cf91dc8c4..de735c146 100644
--- a/docs/tutorials/pt/managing-http-headers.md
+++ b/docs/tutorials/pt/managing-http-headers.md
@@ -22,9 +22,7 @@ Os cabeçalhos desempenham um papel fundamental na comunicação HTTP, fornecend
 - **Cabeçalhos de requisição:** Enviados pelo cliente ao servidor. Eles contêm informações sobre a requisição feita, como o tipo de método HTTP usado, o tipo de conteúdo aceito, cookies, entre outros.
 - **Cabeçalhos de resposta:** Enviados pelo servidor para o cliente. Fornecem informações sobre a resposta enviada, como o status da resposta, o tipo de conteúdo retornado, cookies, entre outros.
 
-<div class = "alert alert-info">
-Para mais informações, leia o guia de MDN <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP">HTTP</a> e as documentações relacionadas.
-</div>
+>ℹ️ Para mais informações, leia o guia de MDN [HTTP](https://developer.mozilla.org/en-US/docs/Web/HTTP) e as documentações relacionadas.
 
 Neste guia, você aprenderá a gerenciar os cabeçalhos de resposta de segurança na sua loja desenvolvida com Store Framework.
 
diff --git a/docs/tutorials/pt/managing-page-and-template-content.md b/docs/tutorials/pt/managing-page-and-template-content.md
index 4fddbc601..0e6a896d3 100644
--- a/docs/tutorials/pt/managing-page-and-template-content.md
+++ b/docs/tutorials/pt/managing-page-and-template-content.md
@@ -17,9 +17,7 @@ subcategory: 9Arh3cJIOYlfSD1MUC2h3
 
 O Site Editor reflete nativamente o aplicativo Store Theme, permitindo que você sobrescreva as configurações predefinidas para blocos e crie um novo conteúdo para as páginas e *templates* da sua loja.
 
-<div class = "alert alert-info">
-O Site Editor não permite que você adicione um novo bloco a um <i>template</i> ou página específica, apenas sobrescrever as configurações de bloco existentes do Store Theme.
-</div>
+>ℹ️ O Site Editor não permite que você adicione um novo bloco a um <i>template</i> ou página específica, apenas sobrescrever as configurações de bloco existentes do Store Theme.
 
 Exercite sua autonomia sobre o código e construa o cenário de loja desejado de acordo com as necessidades de seu negócio, usando uma interface amigável a seu favor!
 
@@ -40,13 +38,9 @@ Exercite sua autonomia sobre o código e construa o cenário de loja desejado de
 4. Faça as alterações desejadas de acordo com as configurações disponíveis para o bloco.
 5. Defina se o conteúdo será ativado assim que for salvo clicando no campo `Ative agora`. É possível também definir uma data de início e uma data de término, se desejar. Para fazer isso, selecione os respectivos botões e escolha a data adequada no calendário.
 
-  <div class = "alert alert-warning">
-Depois que o campo `esta URL` estiver marcado, o conteúdo só ficará visível na URL específico em que você salvou suas alterações. Portanto, tome cuidado com os parâmetros e outros componentes de URL que podem afetar a exibição do conteúdo - quanto mais específica for a seu URL, isto é, com mais parâmetros e <i>querystrings</i>, mais restrito será o novo conteúdo.
-</div>
+  >⚠️ Depois que o campo `esta URL` estiver marcado, o conteúdo só ficará visível na URL específico em que você salvou suas alterações. Portanto, tome cuidado com os parâmetros e outros componentes de URL que podem afetar a exibição do conteúdo - quanto mais específica for a seu URL, isto é, com mais parâmetros e <i>querystrings</i>, mais restrito será o novo conteúdo.
 
-  <div class = "alert alert-info">
-O Site Editor aplica configurações de conteúdo de acordo com a hierarquia de parâmetros da URL. Reproduza o conteúdo de forma nativa para todas as páginas sob o mesmo parâmetro pai, criando apenas conteúdo para a URL com o mesmo. Considere uma determinada URL de categoria, por exemplo. Ao criar conteúdo para ela, todas as URLs das páginas de produto cujo parâmetro pai é a categoria também serão atualizadas.
-</div>
+  >ℹ️ O Site Editor aplica configurações de conteúdo de acordo com a hierarquia de parâmetros da URL. Reproduza o conteúdo de forma nativa para todas as páginas sob o mesmo parâmetro pai, criando apenas conteúdo para a URL com o mesmo. Considere uma determinada URL de categoria, por exemplo. Ao criar conteúdo para ela, todas as URLs das páginas de produto cujo parâmetro pai é a categoria também serão atualizadas.
 
 6. Ainda na seção `Visibilidade`, verifique se o conteúdo será criado apenas na URL para a qual você navegou inicialmente ou em todo o *template* —  incluindo a URL que você está atualmente e todas as outras do *template*.
 
@@ -61,9 +55,7 @@ O Site Editor aplica configurações de conteúdo de acordo com a hierarquia de
 2. O conteúdo disponível é o ativo vigente. Edite os campos com os novos valores ou clique em `Versões` para editar as configurações de outros conteúdos.
 3. Salve suas alterações.
 
-  <div class = "alert alert-warning">
-Os conteúdos derivados do Store Theme não podem ter sua visibilidade atualizada por você por meio do Site Editor. Independentemente de suas ações, eles são sempre exibidos por <i>template</i> e não por URL. Os conteúdos criados manualmente no Site Editor, por sua vez, podem ter sua visibilidade alterada para URL ou <i>template</i>, de acordo com a sua necessidade.
-</div>
+  >⚠️ Os conteúdos derivados do Store Theme não podem ter sua visibilidade atualizada por você por meio do Site Editor. Independentemente de suas ações, eles são sempre exibidos por <i>template</i> e não por URL. Os conteúdos criados manualmente no Site Editor, por sua vez, podem ter sua visibilidade alterada para URL ou <i>template</i>, de acordo com a sua necessidade.
 
 ## Excluindo e redefinindo conteúdo
 
@@ -75,9 +67,7 @@ Os conteúdos derivados do Store Theme não podem ter sua visibilidade atualizad
 3. Clique no menu kebab do conteúdo desejado (três pontos).
 4. Clique em `Excluir` ou` Redefinir` e confirme sua ação.
 
-<div class = "alert alert-warning">
-As ações <code>Excluir</code> e <code>Redefinir</code> dependem do tipo de conteúdo. O conteúdo nativo, ou seja, o conteúdo criado diretamente no código, não pode ser excluído pelo admin, apenas <i>resetado</i> (caso tenha sido sobrescrito). Você só pode excluir o conteúdo que criou manualmente pelo Site Editor.
-</div>
+>⚠️ As ações `Excluir` e `Redefinir` dependem do tipo de conteúdo. O conteúdo nativo, ou seja, o conteúdo criado diretamente no código, não pode ser excluído pelo admin, apenas <i>resetado</i> (caso tenha sido sobrescrito). Você só pode excluir o conteúdo que criou manualmente pelo Site Editor.
 
 ## Configurando conteúdo ativo e inativo
 
@@ -89,7 +79,5 @@ Observe que ao clicar no menu kebab de um determinado conteúdo (três pontos),
 
 O caminho para definir qual conteúdo deve estar ativo e inativo é excluir ou redefinir o conteúdo ativo vigente para permitir que o primeiro da fila dos inativos seja, então, ativado.
 
-<div class = "alert alert-info">
-A fila para conteúdos inativos começa do conteúdo mais recente ao mais antigo. Lembre-se de que os conteúdos criados por meio do Site Editor <i>sempre</i> prevalecem sobre o que foi definido no código.
-</div>
+>ℹ️ A fila para conteúdos inativos começa do conteúdo mais recente ao mais antigo. Lembre-se de que os conteúdos criados por meio do Site Editor <i>sempre</i> prevalecem sobre o que foi definido no código.
 
diff --git a/docs/tutorials/pt/managing-shipping-policies.md b/docs/tutorials/pt/managing-shipping-policies.md
index 15d52a23e..16be765d1 100644
--- a/docs/tutorials/pt/managing-shipping-policies.md
+++ b/docs/tutorials/pt/managing-shipping-policies.md
@@ -29,9 +29,7 @@ Este artigo apresenta como acompanhar e gerenciar suas políticas de envio. No A
 * [Ativar ou desativar política de envio](#ativar-ou-desativar-politica-de-envio)
 * [Excluir política de envio](#excluir-politica-de-envio)
 
-<div class = "alert alert-info">
-Também é possível criar políticas de envio, confira o passo a passo no artigo <a href="https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT">Criar uma política de envio</a>.
-</div>
+>ℹ️ Também é possível criar políticas de envio, confira o passo a passo no artigo [Criar uma política de envio](https://help.vtex.com/pt/tutorial/criar-uma-politica-de-envio--66rJO4LKBdyMJOH6Z3dsaT).
 
 ## Visualizar lista de políticas de envio
 
@@ -54,9 +52,7 @@ As informações apresentadas nessa página estão descritas na tabela a seguir:
 
 Na caixa de busca com o ícone lupa <i class="fas fa-search"></i>, é possível buscar políticas de envio pelo nome. Ao digitar um caractere na barra de busca, a pesquisa é imediatamente realizada. Para limpar a busca, clique no ícone fechar <i class="far fa-times-circle"></i>.
 
-<div class = "alert alert-info">
-Caso não haja um resultado para a pesquisa, verifique a ortografia usada na busca e se existe algum filtro selecionado.
-</div>
+>ℹ️ Caso não haja um resultado para a pesquisa, verifique a ortografia usada na busca e se existe algum filtro selecionado.
 
 ## Filtrar políticas de envio
 
diff --git a/docs/tutorials/pt/managing-stock-items.md b/docs/tutorials/pt/managing-stock-items.md
index da64bf779..1675a8e36 100644
--- a/docs/tutorials/pt/managing-stock-items.md
+++ b/docs/tutorials/pt/managing-stock-items.md
@@ -39,7 +39,7 @@ No Admin VTEX, acesse **Catálogo > Inventário > Gerenciamento de inventário**
     * **Produtos:** o nome do produto.
     * **Estoque**: em qual estoque da loja o SKU está.
     * **ID do SKU:** código identificador do SKU.
-    * **Última atualização**: número de unidades do SKU mais recente registrado na plataforma VTEX.<p><div class = "alert alert-info">Ao clicar em qualquer valor da coluna <b>Última atualização</b>, a janela <a href="https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2">Registro de atualizações</a> ficará disponível com a tabela das alterações. Cada linha corresponde a um registro de atualização, e as colunas contêm o usuário que realizou a alteração, a data da atualização e a quantidade de itens antes e depois da atualização. Só é possível consultar até as últimas 50 movimentações de um SKU.</div></p>
+    * **Última atualização**: número de unidades do SKU mais recente registrado na plataforma VTEX.<p>>ℹ️ Ao clicar em qualquer valor da coluna **Última atualização**, a janela [Registro de atualizações](https://help.vtex.com/pt/tutorial/historico-de-movimentacoes-do-inventario--5AM7xbmMzmKSEQewakamc2) ficará disponível com a tabela das alterações. Cada linha corresponde a um registro de atualização, e as colunas contêm o usuário que realizou a alteração, a data da atualização e a quantidade de itens antes e depois da atualização. Só é possível consultar até as últimas 50 movimentações de um SKU.</p>
     * **Reservados:** unidades de itens do SKU reservados. Os pedidos dessas reservas ainda não estão com o pagamento aprovado. 
     Ao clicar nos valores dessa coluna para conferir detalhes sobre os dados das reservas do SKU,  você será redirecionado para o gerenciamento de pedidos. Para saber mais sobre como consultar uma reserva, veja [Como acompanhar o status da reserva](https://help.vtex.com/pt/tutorial/how-does-reservation-work--tutorials_92#como-acompanhar-o-status-da-reserva)
     * **Enviados:** unidades despachadas do SKU. Os itens desta coluna são de pedidos com status `Pagamento aprovado`, `Preparando entrega` ou `Faturado`. <p>Ao clicar nos itens da coluna para conferir detalhes de SKUs enviados, você será redirecionado para o gerenciamento de pedidos.</p>
diff --git a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
index 1c7566edd..6b5f030a5 100644
--- a/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
+++ b/docs/tutorials/pt/mapping-categories-and-brands-for-the-marketplace-beta.md
@@ -26,9 +26,7 @@ O marketplace VTEX realiza a correspondência de valores dos catálogos por meio
 - Envia produtos pela primeira vez para o marketplace VTEX.
 - Envia novas informações de categorias, marcas ou especificações, ainda não mapeadas no marketplace VTEX.
 
-<div class = "alert alert-info">
-O envio de um item para mapear novas informações não modifica os valores já mapeados no marketplace VTEX.
-</div>
+>ℹ️ O envio de um item para mapear novas informações não modifica os valores já mapeados no marketplace VTEX.
 
 Para facilitar a conexão entre sellers e marketplaces VTEX, existe a página **Categorias e marcas Beta**, que permite ao marketplace VTEX fazer a correspondência entre suas categorias e marcas e as categorias e marcas do seller. As ações que o marketplace VTEX precisa realizar para o mapeamento são:
 
@@ -67,9 +65,7 @@ O status do mapeamento de categorias no marketplace VTEX é indicado por ícones
 | <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento:** houve um problema e o mapeamento não foi realizado. | 
 | <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado:** a categoria ainda não foi mapeada. |
 
-<div class = "alert alert-info">
-Não é possível excluir um mapeamento de categoria, mas você pode alterar as configurações a qualquer momento, seguindo os mesmos passos do primeiro mapeamento realizado.
-</div>
+>ℹ️ Não é possível excluir um mapeamento de categoria, mas você pode alterar as configurações a qualquer momento, seguindo os mesmos passos do primeiro mapeamento realizado.
 
 ## Mapear marcas do seller
 
@@ -92,9 +88,7 @@ O status do mapeamento de marcas no marketplace VTEX é indicado por ícones na
 | <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/lsN6TxCm1e6frHvIQ8xjt/491ad1e6d99ab858e2a76d0ea31e1a39/erromapeamento_mapper.JPG" /> | **Erro no mapeamento:** houve um problema e o mapeamento não foi realizado. | 
 | <img class="shadow-4" src="https://images.ctfassets.net/alneenqid6w5/3nVJUJHetaqPHThGGpoG8T/d7f667b269105a5c65aa7b16b1aace21/incompleto_mapper.JPG" /> | **Não mapeado:** a categoria ainda não foi mapeada. |
 
-<div class = "alert alert-info">
-Não é possível excluir um mapeamento de marca, mas você pode alterar as configurações a qualquer momento, seguindo os mesmos passos do primeiro mapeamento realizado.
-</div>
+>ℹ️ Não é possível excluir um mapeamento de marca, mas você pode alterar as configurações a qualquer momento, seguindo os mesmos passos do primeiro mapeamento realizado.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/marketplaces-and-integrations.md b/docs/tutorials/pt/marketplaces-and-integrations.md
index 4230cd6f9..3a940cf6a 100644
--- a/docs/tutorials/pt/marketplaces-and-integrations.md
+++ b/docs/tutorials/pt/marketplaces-and-integrations.md
@@ -24,9 +24,7 @@ Dos marketplaces disponibilizados, temos a opção de marketplace VTEX e marketp
 | **VTEX** | São os perfis de clientes VTEX que optaram abrir o seu ambiente para que sellers divulguem seus produtos para venda. |
 | **Externo** | São aqueles marketplaces que não são clientes VTEX e desenvolveram a integração, seja ela certificada ou parceira. |
 
-<div class= "alert alert-info">
-Note que a <b>Marketplaces e Integrações</b> é uma ferramenta que promove o contato entre potenciais parceiros, mas não é uma etapa obrigatória para tornar-se marketplace na VTEX. Se você deseja atuar como um marketplace VTEX, leia a documentação <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex">Estratégias de marketplace na VTEX</a>.  
-</div>  
+>ℹ️ Note que a **Marketplaces e Integrações** é uma ferramenta que promove o contato entre potenciais parceiros, mas não é uma etapa obrigatória para tornar-se marketplace na VTEX. Se você deseja atuar como um marketplace VTEX, leia a documentação [Estratégias de marketplace na VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#sendo-seller-vtex).  
 
 ## Encontrando marketplaces  
 
@@ -80,9 +78,7 @@ Na tela irá aparecer uma mensagem de sucesso.
 
 Caso o seller necessite fazer novo contato com o mesmo marketplace, repita os passos acima.
 
-<div class= "alert alert-info">
-O potencial parceiro comercial receberá um email com as informações preenchidas no campo Mensagem. Caso o interesse seja mútuo, o encarregado pelo seller ou marketplace poderá entrar em contato e negociar os termos do acordo entre marketplace e seller.
-</div>  
+>ℹ️ O potencial parceiro comercial receberá um email com as informações preenchidas no campo Mensagem. Caso o interesse seja mútuo, o encarregado pelo seller ou marketplace poderá entrar em contato e negociar os termos do acordo entre marketplace e seller.  
 
 ## Editar  
 
diff --git a/docs/tutorials/pt/master-data.md b/docs/tutorials/pt/master-data.md
index 356aeeb58..b2127e01b 100644
--- a/docs/tutorials/pt/master-data.md
+++ b/docs/tutorials/pt/master-data.md
@@ -21,17 +21,13 @@ Por padrão, o Master Data é usado para armazenar e organizar dados de clientes
 
 Neste artigo você saberá mais detalhes sobre cada versão disponível do Master Data, conceitos importantes e como utilizar.
 
-<div class = "alert alert-info">
-Note que a depender da funcionalidade e versão que deseja utilizar, você deverá entrar em contato com o time de desenvolvimento da sua operação.
-</div>
+>ℹ️ Note que a depender da funcionalidade e versão que deseja utilizar, você deverá entrar em contato com o time de desenvolvimento da sua operação.
 
 ## Versões disponíveis
 
 Atualmente existem duas versões disponíveis e você pode escolher aquela que melhor se adequa às necessidades da sua operação. A principal diferença entre as duas é que a v2 não possui interface gráfica, podendo ser utilizada apenas por meio da [API do Master Data v2](https://developers.vtex.com/docs/api-reference/master-data-api-v2), ainda que possua outras funcionalidades relevantes, como o uso de [JSON schemas](https://developers.vtex.com/docs/guides/starting-to-work-on-master-data-with-json-schema).
 
-<div class = "alert alert-info">
-Vale ressaltar a plataforma VTEX nativamente salva dados de clientes da sua loja no Master Data v1.
-</div>
+>ℹ️ Vale ressaltar a plataforma VTEX nativamente salva dados de clientes da sua loja no Master Data v1.
 
 Confira a tabela abaixo para saber mais sobre as funcionalidades de cada versão versões se diferem.
 
@@ -257,9 +253,7 @@ Como mencionado acima, cada documento tem um ID gerado automaticamente pela plat
 
 Por exemplo, é possível consultar um documento com informações de um cliente especificando o valor do campo `email` referente ao cliente.
 
-<div class = "alert alert-info">
-Saiba mais sobre como <a href=https://help.vtex.com/pt/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices no Master Data v1</a> ou <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>configurar índices com a API do Master Data v2</a>.
-</div>
+>ℹ️ Saiba mais sobre como <a href=https://help.vtex.com/pt/tutorial/setting-up-an-index-on-master-data--tutorials_785>configurar índices no Master Data v1</a> ou <a href=https://developers.vtex.com/vtex-rest-api/reference/putindices>configurar índices com a API do Master Data v2</a>.
 
 ## Triggers
 
@@ -274,17 +268,13 @@ Saiba mais sobre como [configurar triggers no Master Data v1](https://help.vtex.
 
 Com a v2 do Master Data, você pode definir formatos de dados com JSON schemas. Este formato indica como o Master Data deve validar e indexar documentos.
 
-<div class = "alert alert-info">
-  Saiba mais sobre <a href=https://json-schema.org/>JSON schemas</a>.
-</div>
+>ℹ️ Saiba mais sobre <a href=https://json-schema.org/>JSON schemas</a>.
 
 Você pode salvar um documento em qualquer entidade de dados se o conteúdo for um JSON válido. Uma entidade de dados pode ou não ter múltiplos JSON schemas associados.
 
 ![Master Data schemas](https://images.ctfassets.net/alneenqid6w5/CaidhUAHIxcwas8eWLQZu/908c8b04ea9e32271a494eeb0f2f7a56/schemas_pt.jpg)
 
-<div class = "alert alert-info">
-Um documento pode ser compatível com múltiplos JSON Schemas, mas também com nenhum.
-</div>
+>ℹ️ Um documento pode ser compatível com múltiplos JSON Schemas, mas também com nenhum.
 
 ## Casos de uso
 
diff --git a/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md b/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
index 623b0afe3..19b899949 100644
--- a/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
+++ b/docs/tutorials/pt/mercado-livre-automobilist-compatibility.md
@@ -15,9 +15,7 @@ legacySlug: mercado-livre-compatibilidade-automobilistica
 subcategory: 2zVauFUkYn8vgS0y0MfWeK
 ---
 
-<div class = "alert alert-info">
-Este recurso está disponível apenas para sellers VTEX que vendem produtos automobilísticos da Argentina, Brasil e México.
-</div>  
+>ℹ️ Este recurso está disponível apenas para sellers VTEX que vendem produtos automobilísticos da Argentina, Brasil e México.  
 
 No módulo [Gerenciamento de anúncios](https://help.vtex.com/pt/tutorial/gerenciamento-de-anuncios--7MRb9S78aBdZjFGpbuffpE), os sellers de lojas VTEX podem acompanhar e gerenciar os anúncios enviados aos canais de vendas, [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic e Premium), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e outros marketplaces VTEX. 
 
@@ -25,9 +23,7 @@ A compatibilidade automobilística, possibilita aos sellers informar com quais v
 
 Nos anúncios enviados ao Mercado Livre é possível identificar quais apresentam o erro `Compatibilidade com Meli`, esse erro ocorre quando o anúncio de um acessório automobilístico é enviado sem as informações de qual veículo ele é compatível ou quando as configurações estão cadastradas de maneira incorreta. 
 
-<div class = "alert alert-warning">
-Os anúncios que apresentarem erro, não serão enviados ao Mercado Livre até que seja corrigido.
-</div>  
+>⚠️ Os anúncios que apresentarem erro, não serão enviados ao Mercado Livre até que seja corrigido.  
 
 ![Mercado Livre: Compatibilidade Automobilística](https://images.ctfassets.net/alneenqid6w5/7JjKhuTHSN7j1V51FzjT5v/71bc2c07df8a14d172a0f58afb4e99f8/compatibilidade_automobilistica_1.png)  
 
@@ -46,9 +42,7 @@ Para corrigir os erros de `Compatibilidade com Meli`, siga o passo a passo abaix
 
 Realizado o passo a passo, seu anúncio está pronto para ser enviado ao Mercado Livre.  
 
-<div class = "alert alert-info">
-Não é possível informar a compatibilidade automobilística para lubrificantes, fluido refrigerante e fluido para freios.
-</div>
+>ℹ️ Não é possível informar a compatibilidade automobilística para lubrificantes, fluido refrigerante e fluido para freios.
 
 Artigos relacionados:
 
diff --git a/docs/tutorials/pt/mercado-livre-faq.md b/docs/tutorials/pt/mercado-livre-faq.md
index cc76f9661..0ca56600d 100644
--- a/docs/tutorials/pt/mercado-livre-faq.md
+++ b/docs/tutorials/pt/mercado-livre-faq.md
@@ -50,9 +50,7 @@ Existem três formas de enviar a descrição do seu produto para o Mercado Livre
 - Criar uma especificação de produto
 - Criar template na Central de Mensagens (opcional)
 
-<div class = "alert alert-info">
-Leia o artigo do Mercado Livre <a href="https://www.mercadolivre.com.br/ajuda/completar_informacao_dos_seus_produtos_3147">“Como descrever os seus produtos”</a> para dicas de como descrever seus produtos.
-</div>
+>ℹ️ Leia o artigo do Mercado Livre [“Como descrever os seus produtos”](https://www.mercadolivre.com.br/ajuda/completar_informacao_dos_seus_produtos_3147) para dicas de como descrever seus produtos.
 
 #### Preencher o campo Descrição do produto
 
diff --git a/docs/tutorials/pt/my-store-order-was-not-created.md b/docs/tutorials/pt/my-store-order-was-not-created.md
index 53ad4ceb1..3e2e0fb6a 100644
--- a/docs/tutorials/pt/my-store-order-was-not-created.md
+++ b/docs/tutorials/pt/my-store-order-was-not-created.md
@@ -43,9 +43,7 @@ As soluções abaixo são voltadas para o gerenciamento de inventário via Admin
 * **Atualizar a contagem do inventário:** na linha correspondente ao SKU e estoque desejados, digite o número de itens disponíveis para venda na coluna Atualizar contagem e clique em `Salvar`. Este número não pode ser negativo, caso contrário o [estoque será negativo](https://help.vtex.com/pt/faq/why-is-my-stock-negative--frequentlyAskedQuestions_159).
 * **Configurar o estoque infinito:** na linha correspondente ao SKU e estoque desejados, na coluna Estoque infinito, clique no botão de ativação e depois em `Salvar`. Quando essa configuração é ativada, o item passa a ser considerado sempre disponível para vendas e a loja nunca fica sem estoque dele.
 
-<div class = "alert alert-info">
-Para configurar os produtos sem estoque a serem exibidos no seu storefront, acesse <b>Catálogo > Todos os produtos</b> no Admin VTEX e, na página de configuração do produto, na aba <b>Produto</b>, marque a opção <b>Sim</b> no campo <i>Mostrar produto esgotado</i>.
-</div>
+>ℹ️ Para configurar os produtos sem estoque a serem exibidos no seu storefront, acesse **Catálogo > Todos os produtos** no Admin VTEX e, na página de configuração do produto, na aba **Produto**, marque a opção **Sim** no campo <i>Mostrar produto esgotado</i>.
 
 ### Revisar integração XML
 
diff --git a/docs/tutorials/pt/offer-details.md b/docs/tutorials/pt/offer-details.md
index 97f302588..cc109cca9 100644
--- a/docs/tutorials/pt/offer-details.md
+++ b/docs/tutorials/pt/offer-details.md
@@ -34,9 +34,7 @@ A página **Detalhes do anúncio** apresenta as seguintes seções:
 - [Status do anúncio](#status-do-anuncio)  
 - [Lista de Interações](#lista-de-interacoes)
 
-<div class = "alert alert-info">
-O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre</a> (Classic e Premium), <a href="https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> e marketplaces VTEX. Para conectores que desejam integrar via API, existe o <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Guia de integração da Gerenciamento de anúncios</a>.
-</div>
+>ℹ️ O **Gerenciamento de anúncios** permite acompanhar anúncios com o [Mercado Livre](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq) (Classic e Premium), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e marketplaces VTEX. Para conectores que desejam integrar via API, existe o [Guia de integração da Gerenciamento de anúncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Cabeçalho
 
diff --git a/docs/tutorials/pt/offer-management.md b/docs/tutorials/pt/offer-management.md
index eae246c6f..39aa796cb 100644
--- a/docs/tutorials/pt/offer-management.md
+++ b/docs/tutorials/pt/offer-management.md
@@ -98,9 +98,7 @@ Na lista de anúncios, existem colunas com as seguintes informações:
 
 Para exportar a lista de anúncios em formato XLSX, clique sobre o <i class="fas fa-arrow-to-bottom"></i> ícone seta para baixo, localizado no topo da interface. O arquivo será enviado para o email do usuário logado, sendo que o tempo da exportação vai depender do volume de anúncios da listagem exportada e questões de processamento da plataforma VTEX.
 
-<div class = "alert alert-info">
-O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
-</div>
+>ℹ️ O conteúdo exportado é referente ao total de anúncios da listagem no momento da exportação. Se algum filtro estiver ativo, somente os anúncios selecionados serão exportados.
 
 ## Consultar anúncios indisponíveis
 
diff --git a/docs/tutorials/pt/oms-page-structure.md b/docs/tutorials/pt/oms-page-structure.md
index 2bff6096c..3cf445e1c 100644
--- a/docs/tutorials/pt/oms-page-structure.md
+++ b/docs/tutorials/pt/oms-page-structure.md
@@ -15,9 +15,7 @@ legacySlug: estrutura-da-pagina-do-oms
 subcategory: 2t00bBkcAwIkgSCGKsMOwY
 ---
 
-<div class = "alert alert-info">
-Para conferir a documentação sobre a nova interface do Order Management System (OMS), veja <a href="https://help.vtex.com/pt/tutorial/order-list-beta--2QTduKHAJMFIZ3BAsi6Pi">Lista de Pedidos (Beta)</a>.
-</div>
+>ℹ️ Para conferir a documentação sobre a nova interface do Order Management System (OMS), veja [Lista de Pedidos (Beta)](https://help.vtex.com/pt/tutorial/order-list-beta--2QTduKHAJMFIZ3BAsi6Pi).
 
 Para entender melhor a seção de __Gerenciamento de pedidos__, veja o descritivo de cada área do módulo responsável pela exibição e gestão dos pedidos da sua loja.
 
diff --git a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
index 4b0bfd960..a534237a0 100644
--- a/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
+++ b/docs/tutorials/pt/opening-tickets-to-vtex-support-finacial.md
@@ -59,9 +59,7 @@ Essa classificação é importante para que o time de suporte priorize os chamad
 
 >ℹ️ **Normal:** perguntas em geral.
 
-<div class = "alert alert-warning">
-<strong>Alto:</strong> documentações importantes estão inviabilizando o processo.
-</div>
+>⚠️ **Alto:** documentações importantes estão inviabilizando o processo.
 
 >❗ **Urgente:** Admin bloqueado, ameaçando o lucro dos seus negócios.
 
diff --git a/docs/tutorials/pt/operational-capacity-beta.md b/docs/tutorials/pt/operational-capacity-beta.md
index c3d3cc66f..96e1194ab 100644
--- a/docs/tutorials/pt/operational-capacity-beta.md
+++ b/docs/tutorials/pt/operational-capacity-beta.md
@@ -15,9 +15,7 @@ legacySlug: modulo-localidades
 subcategory: 13sVE3TApOK1C8jMVLTJRh
 ---
 
-<div class = "alert alert-info">
-Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a <b>Capacidade operacional (Beta)</b>, preencha o <a href="https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform">formulário de contato</a>. O requisito para usar a funcionalidade é ter <a href="https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl">contas franquia</a> associadas à <a href="https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-conta-na-vtex">conta principal</a>.
-</div>
+>ℹ️ Essa funcionalidade está em fase beta, o que significa que estamos trabalhando para aprimorá-la. Se você deseja utilizar a **Capacidade operacional (Beta)**, preencha o [formulário de contato](https://docs.google.com/forms/d/e/1FAIpQLScgmHPJEnVfd1EK9znevW-bcdxL2WVqzNZdrwri9auKayZDJA/viewform). O requisito para usar a funcionalidade é ter [contas franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) associadas à [conta principal](https://help.vtex.com/pt/tracks/trilha-da-loja-vtex--eSDNk26pdvemF3XKM0nK9/4yPqZQyj0t675QpcG7H6yl#tipos-de-conta-na-vtex).
 
 O módulo **Capacidade operacional** permite que você gerencie a capacidade dos sellers de receberem e prepararem os pedidos da loja, de forma a otimizar sua malha logística. Você acompanha a distribuição de pedidos entre os sellers e pode realizar [ações](#acoes-na-pagina-de-detalhes-do-seller) para melhorar a distribuição dos pedidos entre eles. 
 
@@ -63,9 +61,7 @@ No Admin VTEX, na página **Envio > Capacidade operacional**, você pode realiza
 
 Utilizando a barra de busca, você pode usar o nome do seller para encontrá-lo.
 
-<div class = "alert alert-info">
-É possível associar a busca de sellers com o <a href="https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtrar-sellers">filtro por status</a>. Caso os resultados da sua busca retornem vazios, observe se não há um filtro ativo.
-</div>
+>ℹ️ É possível associar a busca de sellers com o [filtro por status](https://help.vtex.com/pt/tutorial/capacidade-operacional-beta--2thSYLMAS8KAd8V4XuBLSy#filtrar-sellers). Caso os resultados da sua busca retornem vazios, observe se não há um filtro ativo.
 
 ### Filtrar sellers
 
diff --git a/docs/tutorials/pt/order-allocation-algorithm-beta.md b/docs/tutorials/pt/order-allocation-algorithm-beta.md
index c4f8b5229..7ab2bdc32 100644
--- a/docs/tutorials/pt/order-allocation-algorithm-beta.md
+++ b/docs/tutorials/pt/order-allocation-algorithm-beta.md
@@ -33,9 +33,7 @@ O **Order Allocation Algorithm** funciona de formas diferentes para envio do tip
 
 <br>
 
-<div class = "alert alert-info">
-O critério prioritário do <a href="https://help.vtex.com/pt/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo atual</a> é buscar a menor quebra de pacotes do pedido. O <b>Order Allocation Algorithm</b> tem como critério principal buscar os menores custos de envio para o lojista.
-</div>
+>ℹ️ O critério prioritário do [algoritmo atual](https://help.vtex.com/pt/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa) é buscar a menor quebra de pacotes do pedido. O **Order Allocation Algorithm** tem como critério principal buscar os menores custos de envio para o lojista.
 
 As próximas seções apresentam detalhes sobre o funcionamento do algoritmo e estão divididas em:
 
@@ -76,8 +74,6 @@ Ao analisar combinações de fulfillment points, o algoritmo considera:
 
 Por meio da política de envio, o **Order Allocation Algorithm** simula as combinações de fulfillment points buscando os menores custos para o lojista. O processo é feito por meio de consultas a [planilhas de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) e análise de custos com [transportadoras](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE).
 
-<div class = "alert alert-info">
-No <a href="https://help.vtex.com/pt/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa">algoritmo atual</a>, muitas vezes o lojista configura a <a href="https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127">planilha de frete</a> com os valores que ele deseja apresentar para o consumidor no checkout, e não o custo real com as transportadoras. Com o <b>Order Allocation Algorithm</b>, o lojista não precisa considerar como o custo na planilha de frete se reflete na experiência de compra do consumidor, pois isso passa a ser determinado por configurações nas <a href="https://help.vtex.com/pt/tutorial/shipping-options-beta--7gsdck3519Z3VPqzwFFHJL">opções de envio</a>. Além disso, o <b>Order Allocation Algorithm</b> se torna mais preciso ao ter como referência os custos reais com transportadoras.
-</div>
+>ℹ️ No [algoritmo atual](https://help.vtex.com/pt/tutorial/algoritmo-de-selecao-de-sellers-white-label--3MemNQ4pKkWCpMdzI27AHa), muitas vezes o lojista configura a [planilha de frete](https://help.vtex.com/pt/tutorial/planilha-de-frete--tutorials_127) com os valores que ele deseja apresentar para o consumidor no checkout, e não o custo real com as transportadoras. Com o **Order Allocation Algorithm**, o lojista não precisa considerar como o custo na planilha de frete se reflete na experiência de compra do consumidor, pois isso passa a ser determinado por configurações nas [opções de envio](https://help.vtex.com/pt/tutorial/shipping-options-beta--7gsdck3519Z3VPqzwFFHJL). Além disso, o **Order Allocation Algorithm** se torna mais preciso ao ter como referência os custos reais com transportadoras.
 
 Após analisar as simulações possíveis, o **Order Allocation Algorithm** determina para cada opção de envio um resultado de combinações de fulfillment points. No checkout, o consumidor é apresentado a todas as opções de envio que possuem pelo menos uma combinação válida de fulfillment points que atendem o pedido.
diff --git a/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md b/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
index e22908de7..669e5c2c4 100644
--- a/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
+++ b/docs/tutorials/pt/order-cancellation-requested-by-the-customer.md
@@ -19,9 +19,7 @@ Existem cenários em que os clientes podem solicitar o cancelamento de um pedido
 
 >❗ Uma vez que o pedido é cancelado, não é mais possível alterar o status do pedido.
 
-<div class = "alert alert-warning">
-Não é possível <a href="https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186">cancelar pedidos</a> que já tenham sido <a href="https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe">faturados parcialmente</a>. Caso o cliente deseje substituir ou remover itens do pedido, é possível <a href="https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190">alterar o pedido</a>.
-</div>
+>⚠️ Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
 ## Cancelamento no prazo de carência
 
@@ -29,9 +27,7 @@ Ocorre quando o cliente solicita cancelamento no [tempo carência](https://help.
 
 * Essa ação é feita pelo cliente em __Meus pedidos__, ao clicar em `Solicitar cancelamento do pedido`.
 
-<div class = "alert alert-info">
-Quando o cliente solicita o cancelamento do pedido durante o prazo de carência, a notificação desta ação é enviada somente para o usuário com <a href="https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc">perfil de acesso</a> de Titular da conta (usuário master).
-</div>
+>ℹ️ Quando o cliente solicita o cancelamento do pedido durante o prazo de carência, a notificação desta ação é enviada somente para o usuário com [perfil de acesso](https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc) de Titular da conta (usuário master).
 
 ## Cancelamento aprovado pelo lojista
 
diff --git a/docs/tutorials/pt/order-details-page.md b/docs/tutorials/pt/order-details-page.md
index 2a24ba9d3..de731eae5 100644
--- a/docs/tutorials/pt/order-details-page.md
+++ b/docs/tutorials/pt/order-details-page.md
@@ -15,9 +15,7 @@ legacySlug: pagina-de-detalhes-do-pedido-beta
 subcategory: 3VNOhxDrvYxJThhuJClrYZ
 ---
 
-<div class = "alert alert-info">
-É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 A página de **Detalhes do Pedido** permite visualizar todas as informações de um pedido e gerenciá-lo em um único lugar. Para visualizá-la, no Admin VTEX, acesse **Pedidos > [Todos os Pedidos](https://help.vtex.com/pt/tutorial/lista-de-pedidos-interface--2QTduKHAJMFIZ3BAsi6Pi)**, e clique no pedido desejado.
 
@@ -44,9 +42,7 @@ A página de **Detalhes do pedido** está dividida em blocos que agrupam informa
 
 Para saber mais sobre os status e o fluxo do pedido, confira o artigo [Fluxo e status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196).
 
-<div class = "alert alert-info">
-A seguir listamos todas as seções da página <b>Detalhes do pedido</b>. Note que somente as seções que se aplicarem ao pedido em questão estarão visíveis.
-</div>
+>ℹ️ A seguir listamos todas as seções da página **Detalhes do pedido**. Note que somente as seções que se aplicarem ao pedido em questão estarão visíveis.
 
 ##  Barra superior
 
@@ -72,9 +68,7 @@ As informações gerais do pedido são exibidas no início da página, logo abai
   - Contato (celular e email)
 * **Entrega/Retirada:** dados do endereço e destinatário para o envio por transportadora ou retirada pelo cliente.
 
-<div class = "alert alert-info">
-Clique em <i class="fas fa-chevron-right"></i> na lateral dos blocos para mostrar mais informações, caso os blocos estejam minimizados.
-</div>
+>ℹ️ Clique em <i class="fas fa-chevron-right"></i> na lateral dos blocos para mostrar mais informações, caso os blocos estejam minimizados.
 
 ## Status do pedido
 
diff --git a/docs/tutorials/pt/order-flow-and-status.md b/docs/tutorials/pt/order-flow-and-status.md
index db54d3d61..7bed77143 100644
--- a/docs/tutorials/pt/order-flow-and-status.md
+++ b/docs/tutorials/pt/order-flow-and-status.md
@@ -22,9 +22,7 @@ Esse artigo contém as seguintes informações:
 - Uma [tabela com todos os status vistos pelo Admin e API](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#tabela-de-status-de-pedidos).
 - Os casos em que [ocorre o cancelamento de um pedido](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#cancelamento-de-pedido).
 
-<div class = "alert alert-info">
-Para saber como acompanhar o fluxo de um pedido, confira o artigo <a href="https://help.vtex.com/pt/tutorial/acompanhamento-de-pedidos--et0Ei7F3bjcrEmVAR2kKS">Acompanhamento de pedido</a>.
-</div>
+>ℹ️ Para saber como acompanhar o fluxo de um pedido, confira o artigo [Acompanhamento de pedido](https://help.vtex.com/pt/tutorial/acompanhamento-de-pedidos--et0Ei7F3bjcrEmVAR2kKS).
 
 ## Tipos de fluxo
 
@@ -66,9 +64,7 @@ Esse é o fluxo do pedido visto pela loja responsável pelo envio dos produtos q
 
 3. O status passa automaticamente para `Janela para cancelamento`. O pedido ficará nesse estágio até o limite da [janela para cancelamento](https://help.vtex.com/pt/tutorial/configuracoes-gerais/#pedidos).
 
-  <div class = "alert alert-info">
-A carência do cancelamento existe para que o cliente possa cancelar a compra sem a aprovação da loja, em um determinado período de tempo configurado previamente. Depois desse período, a loja precisa autorizar a solicitação de cancelamento do cliente.
-</div>
+  >ℹ️ A carência do cancelamento existe para que o cliente possa cancelar a compra sem a aprovação da loja, em um determinado período de tempo configurado previamente. Depois desse período, a loja precisa autorizar a solicitação de cancelamento do cliente.
 
 4. No status `Janela para cancelamento`, há duas possibilidades:
     * **Pedido não cancelado**: se o tempo de carência expira e o cliente não solicita o cancelamento da compra, o status segue para `Pronto para manuseio`. Esse é o status que indica ao seller que o pedido já deve ser preparado para o envio.
@@ -117,9 +113,7 @@ Quando é feita a solicitação de cancelamento de um pedido, a plataforma proce
 
 Não é possível [cancelar pedidos](https://help.vtex.com/pt/tutorial/como-cancelar-pedido--tutorials_186) que já tenham sido [faturados parcialmente](https://help.vtex.com/pt/tracks/pedidos--2xkTisx4SXOWXQel8Jg8sa/q9GPspTb9cHlMeAZfdEUe). Caso o cliente deseje substituir ou remover itens do pedido, é possível [alterar o pedido](https://help.vtex.com/pt/tutorial/alteracao-de-itens-de-um-pedido-finalizado--tutorials_190).
 
-<div class = "alert alert-info">
-Saiba mais sobre cancelamento e reembolso nos artigos <a href="https://help.vtex.com/pt/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente">Por que meu pedido cancelado foi cobrado na fatura do cliente</a>, <a href="https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento">Reembolso ou cancelamento</a>.
-</div>
+>ℹ️ Saiba mais sobre cancelamento e reembolso nos artigos [Por que meu pedido cancelado foi cobrado na fatura do cliente](https://help.vtex.com/pt/faq/por-que-meu-pedido-cancelado-foi-cobrado-na-fatura-do-cliente), [Reembolso ou cancelamento](https://help.vtex.com/pt/tutorial/payment-provider-protocol--RdsT2spdq80MMwwOeEq0m#reembolsocancelamento).
 
 Enquanto o cancelamento está sendo processado, o status do pedido permanece em `Cancelando`. Depois que o cancelamento é concluído, o status do pedido passa para `Cancelado`. 
 
@@ -364,6 +358,4 @@ Veja abaixo a tabela com os status de pedido. As informações da tabela estão
 
 <br></br>
 
-<div class = "alert alert-info">
-Os status assinalados com asteriscos (*) na tabela não permitem modificação ou cancelamento, pois estão sob ação da plataforma.
-</div>
+>ℹ️ Os status assinalados com asteriscos (*) na tabela não permitem modificação ou cancelamento, pois estão sob ação da plataforma.
diff --git a/docs/tutorials/pt/order-report.md b/docs/tutorials/pt/order-report.md
index 1de29b2e0..86ffee6c0 100644
--- a/docs/tutorials/pt/order-report.md
+++ b/docs/tutorials/pt/order-report.md
@@ -19,9 +19,7 @@ A exportação de pedidos na página [Todos os pedidos](https://help.vtex.com/pt
 
 Cada linha da planilha refere-se a um [SKU](https://help.vtex.com/pt/tutorial/o-que-e-um-sku--1K75s4RXAQyOuGUYKMM68u). Se no mesmo pedido existem, por exemplo, 3 SKUs, esse pedido vai ser referenciado em 3 linhas no relatório, cada uma delas com dados referentes a um SKU do pedido.
 
-<div class = "alert alert-info">
-O link do relatório de pedidos fica disponível para download por seis horas.
-</div>
+>ℹ️ O link do relatório de pedidos fica disponível para download por seis horas.
 
 As colunas correspondem a uma informação específica sobre o pedido, conforme descrito abaixo.
 
diff --git a/docs/tutorials/pt/order-split-and-delivery-split.md b/docs/tutorials/pt/order-split-and-delivery-split.md
index fe28e76f8..92ed4eab9 100644
--- a/docs/tutorials/pt/order-split-and-delivery-split.md
+++ b/docs/tutorials/pt/order-split-and-delivery-split.md
@@ -22,9 +22,7 @@ Veja a seguir as principais diferenças entre os cenários de divisão de pedido
 * **[Divisão de pedidos](#divisao-de-pedidos):** ocorre quando há mais de um seller atendendo a uma mesma compra. Isso significa que, se há três sellers para atender a uma única compra, há três pedidos gerados. 
 * **[Divisão de pacotes](#divisao-de-pacotes-entregas):** ocorre quando há mais de uma entrega para um pedido. Por exemplo, quando um único seller é responsável pela entrega, mas a entrega do pedido é feita em mais de uma remessa de pacote. 
 
- <div class = "alert alert-info">
-Sempre que há uma divisão de pedidos, há divisão de pacotes. Além disso, um seller pode optar por dividir um único pedido em mais de um pacote; portanto, ao final da compra, o número de pacotes será sempre maior ou igual ao número de pedidos gerados.
-</div>
+ >ℹ️ Sempre que há uma divisão de pedidos, há divisão de pacotes. Além disso, um seller pode optar por dividir um único pedido em mais de um pacote; portanto, ao final da compra, o número de pacotes será sempre maior ou igual ao número de pedidos gerados.
 
 Para facilitar a identificação dos casos em que há divisão de pedidos e divisão de entregas, confira alguns exemplos abaixo:
 
diff --git a/docs/tutorials/pt/order-tracking.md b/docs/tutorials/pt/order-tracking.md
index daf52025c..d5252bc04 100644
--- a/docs/tutorials/pt/order-tracking.md
+++ b/docs/tutorials/pt/order-tracking.md
@@ -17,10 +17,8 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 A página [Todos os pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi) é onde você acompanha os pedidos da sua loja, e na página [detalhes do pedido](https://help.vtex.com/pt/tutorial/order-details-page-interface--2Y75n54Cc9VizrlG1N6ZNl), visualiza as diferentes possibilidades de status e ações ao longo do ciclo de vida de um pedido. É possível conferir o estágio e as interações do pedido; acessar os dados do cliente, da entrega e do pagamento; rastrear a entrega; e enviar [emails](https://help.vtex.com/pt/tutorial/conhecendo-o-message-center--tutorials_84) para o cliente.
 
-<div class = "alert alert-info">
-Para entender mais sobre como o módulo <b>Pedidos</b> é estruturado, confira o artigo <a href="https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi">Todos os pedidos</a>.
-Para conferir quais são os status do fluxo de pedidos, confira o artigo <a href="https://help.vtex.com/pt/tutorial/fluxo-de-pedido--tutorials_196">Fluxo e status de pedidos</a>.
-</div>
+>ℹ️ Para entender mais sobre como o módulo **Pedidos** é estruturado, confira o artigo [Todos os pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi).
+> Para conferir quais são os status do fluxo de pedidos, confira o artigo [Fluxo e status de pedidos](https://help.vtex.com/pt/tutorial/fluxo-de-pedido--tutorials_196).
 
 Para acompanhar um pedido, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/orders-overview.md b/docs/tutorials/pt/orders-overview.md
index 95318b79c..31437bf76 100644
--- a/docs/tutorials/pt/orders-overview.md
+++ b/docs/tutorials/pt/orders-overview.md
@@ -36,9 +36,7 @@ Além de pesquisar pedidos em **Pedidos > Todos os pedidos**, você pode buscar
 - Email do cliente
 - Documento do cliente 
 
-<div class = "alert alert-info">
-É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 ## Assinaturas
 
diff --git a/docs/tutorials/pt/physical-store-instore-beta.md b/docs/tutorials/pt/physical-store-instore-beta.md
index 4affcb3bd..c9b0621d0 100644
--- a/docs/tutorials/pt/physical-store-instore-beta.md
+++ b/docs/tutorials/pt/physical-store-instore-beta.md
@@ -15,9 +15,7 @@ legacySlug: loja-fisica-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 **Loja física** é uma página das **Configurações da loja** do Admin VTEX que apresenta a listagem de lojas físicas cadastradas no aplicativo [inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf). Nela, você pode gerenciar informações de todas as lojas físicas da conta.
 
@@ -78,9 +76,7 @@ Você pode cadastrar uma loja física seguindo os passos a seguir:
 * **Política comercial:** [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV) que será aplicada na loja física. Campo obrigatório.
 * **Ponto de retirada:** [ponto de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R) cadastrado para essa loja física, onde clientes retiram seus pedidos. 
 
-<div class ="alert alert-info">
-<p>As alterações podem levar até 15 minutos para serem processadas e aplicadas no inStore.</p> 
-</div>
+>ℹ️ As alterações podem levar até 15 minutos para serem processadas e aplicadas no inStore.
 
 ## Buscar loja
 
diff --git a/docs/tutorials/pt/pickup-points.md b/docs/tutorials/pt/pickup-points.md
index 5d5e498a3..553f94de6 100644
--- a/docs/tutorials/pt/pickup-points.md
+++ b/docs/tutorials/pt/pickup-points.md
@@ -41,15 +41,13 @@ Vale ressaltar que:
 * A VTEX limita a localização a um raio de 50km entre o ponto de retirada e o endereço do cliente.
 * Nos casos em que há transporte entre o [estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e o ponto de retirada, a VTEX também leva em consideração a existência dessa rota para a escolha do ponto de retirada.
 
-<div class = "alert alert-info">
-Com pontos de retirada, a VTEX também possibilita que o lojista:
-<body>
-<ul>
-<li>Configure <b>pontos de retirada de contingência:</b> pontos de retirada que podem fornecer inventário a outros pontos quando for necessário, possibilitando a escolha mais conveniente ao comprador. Para saber mais, acesse <a href="https://help.vtex.com/pt/tutorial/criar-ponto-de-retirada-de-contingencia-para-garanti-lo-como-opcao-no--3mowqWEfjyM2g6WoWgE0Ao">Ponto de retirada de contingência.</li></a>
-<li>Configure um <b>seller white label como ponto de retirada.</b> Saiba mais em <a href="https://help.vtex.com/pt/tutorial/configurar-seller-white-label-ponto-de-retirada-pickup-point--6fSUE2O0taaoKieAaiuc4e">Configurar Seller White Label como Ponto de Retirada (Pickup Point).</li></a>
-<ul>
-</body>
-</div>
+>ℹ️ Com pontos de retirada, a VTEX também possibilita que o lojista:
+> <body>
+> <ul>
+> <li>Configure **pontos de retirada de contingência:** pontos de retirada que podem fornecer inventário a outros pontos quando for necessário, possibilitando a escolha mais conveniente ao comprador. Para saber mais, acesse [Ponto de retirada de contingência.</li>](https://help.vtex.com/pt/tutorial/criar-ponto-de-retirada-de-contingencia-para-garanti-lo-como-opcao-no--3mowqWEfjyM2g6WoWgE0Ao)
+> <li>Configure um **seller white label como ponto de retirada.** Saiba mais em [Configurar Seller White Label como Ponto de Retirada (Pickup Point).</li>](https://help.vtex.com/pt/tutorial/configurar-seller-white-label-ponto-de-retirada-pickup-point--6fSUE2O0taaoKieAaiuc4e)
+> <ul>
+> </body>
 
 É importante verificar se as configurações da quantidade de pontos de retirada estão dentro dos limites aceitos e de acordo com a estratégia de vendas da loja. Isso permite que a [simulação de envio](https://help.vtex.com/pt/tutorial/simulador-de-envio--tutorials_144) considere os dados corretamente e garante, por exemplo, que a configuração do número de pontos de retirada não limita a operação da loja.
 
@@ -71,9 +69,9 @@ A VTEX considera que o ponto de retirada é uma forma de envio e, por isso, as c
     - b. Na aba **Política de envio**, selecione a política de envio criada para o ponto de retirada.
     - c. Na coluna **Ações**, clique no ícone <i class="fas fa-pen"></i> para edição.
     - d. Ative o <i class="fas fa-toggle-on"></i> do campo **Relacionar pontos de retirada**.
-    - e. Selecione o ponto de retirada pelos campos disponíveis.![relacionarpontosretiradaPT](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/666ecbf11f8f19e5b8b1ca8b381abbf8/relacionarpontosretiradaPT.png)<div class = "alert alert-info">Para lojas que possuem mais de 50 pontos de retirada, recomendamos utilizar o campo Tags dos pontos de retirada ao criar um ponto de retirada. Utilizar tags facilita a busca dos pontos de <a href="https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio">retirada na hora de relacioná-los com a política de envio</a>.Lembre-se também que a política de envio que está associada a um ponto de retirada não fica disponível para outro tipo de envio. Recomendamos criar uma política de envio exclusiva do ponto de retirada.</div>
+    - e. Selecione o ponto de retirada pelos campos disponíveis.![relacionarpontosretiradaPT](https://images.ctfassets.net/alneenqid6w5/6BvdDCekjMPgqE0ULZmNaV/666ecbf11f8f19e5b8b1ca8b381abbf8/relacionarpontosretiradaPT.png)>ℹ️ Para lojas que possuem mais de 50 pontos de retirada, recomendamos utilizar o campo Tags dos pontos de retirada ao criar um ponto de retirada. Utilizar tags facilita a busca dos pontos de [retirada na hora de relacioná-los com a política de envio](https://help.vtex.com/pt/tutorial/politica-de-envio--tutorials_140#cadastrar-uma-politica-de-envio).Lembre-se também que a política de envio que está associada a um ponto de retirada não fica disponível para outro tipo de envio. Recomendamos criar uma política de envio exclusiva do ponto de retirada.
 
-4. [Cadastrar a geolocalização](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): para maior precisão da localização dos pontos de retirada no checkout.<div class = "alert alert-info">A visualização dos pontos de retirada com mapa e horário no checkout está disponível apenas para o Checkout V6.</div>
+4. [Cadastrar a geolocalização](https://help.vtex.com/pt/tutorial/gerenciar-geolocalizacao--tutorials_138): para maior precisão da localização dos pontos de retirada no checkout.>ℹ️ A visualização dos pontos de retirada com mapa e horário no checkout está disponível apenas para o Checkout V6.
 
 5. Habilitar a solicitação de endereço no checkout. Dessa forma, o cliente precisa adicionar o seu endereço para ser usado na nota fiscal:
     - a. No Admin VTEX, acesse **Configurações da loja > Storefront > Checkout**, ou digite *Checkout* na barra de busca no topo da página. 
diff --git a/docs/tutorials/pt/platform-status-page.md b/docs/tutorials/pt/platform-status-page.md
index 10d20d257..91aad9e48 100644
--- a/docs/tutorials/pt/platform-status-page.md
+++ b/docs/tutorials/pt/platform-status-page.md
@@ -21,9 +21,7 @@ Os eventos são reportados pela nossa equipe sempre que nosso sistema automátic
 
 Abaixo, você encontra detalhes sobre os elementos da página de status da plataforma VTEX.
 
-<div class = "alert alert-info">
-A página de status é feita com <a href="https://www.atlassian.com/software/statuspage">Atlassian Statuspage</a>.
-</div>
+>ℹ️ A página de status é feita com [Atlassian Statuspage](https://www.atlassian.com/software/statuspage).
 
 ## Notificações
 
diff --git a/docs/tutorials/pt/predefined-roles.md b/docs/tutorials/pt/predefined-roles.md
index b6ae27118..83ce85c40 100644
--- a/docs/tutorials/pt/predefined-roles.md
+++ b/docs/tutorials/pt/predefined-roles.md
@@ -19,9 +19,7 @@ subcategory: 1HSqkejwuYcQSMC400uY84
 
 Neste documento estão listados os perfis de acesso que estão predefinidos para novas lojas VTEX e respectivos recursos. Para acessá-los diretamente, use a lista abaixo.
 
-<div class = "alert alert-info">
-<p>Para saber mais sobre cada recurso listado nos perfis, veja o artigo <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#">Recursos do License Manager</a>.</p>
-</div>
+>ℹ️ Para saber mais sobre cada recurso listado nos perfis, veja o artigo [Recursos do License Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3#).
 
 * [Admin - Start page only](#admin-start-page-only)
 * [Checkout Admin](#checkout-admin)
diff --git a/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md b/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md
index d6d79788a..a761b498f 100644
--- a/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md
+++ b/docs/tutorials/pt/prevent-a-carrier-from-meeting-certain-zip-code-range.md
@@ -34,6 +34,4 @@ Para isso, siga estes passos:
 
 Com isso, a planilha passaria a "pular" o CEP 45920-000. E consequentemente ele deixaria de ser considerado como opção de endereço atendido por essa transportadora.
 
-<div class = "alert alert-info">
-Os exemplos de código postal deste artigo são referentes ao Brasil, cada país tem o seu próprio formato de código postal.
-</div>
+>ℹ️ Os exemplos de código postal deste artigo são referentes ao Brasil, cada país tem o seu próprio formato de código postal.
diff --git a/docs/tutorials/pt/price-divergence-rule.md b/docs/tutorials/pt/price-divergence-rule.md
index 7cc26572e..84f083c41 100644
--- a/docs/tutorials/pt/price-divergence-rule.md
+++ b/docs/tutorials/pt/price-divergence-rule.md
@@ -47,9 +47,7 @@ Para criar uma regra de Divergência de valores, o usuário precisa ter o perfil
 
 Você pode acompanhar pedidos integrados a partir da regra de Divergência de valores no Admin VTEX, em **Pedidos > [Todos os pedidos](https://help.vtex.com/pt/tutorial/todos-os-pedidos--2QTduKHAJMFIZ3BAsi6Pi)**.
 
-<div class = "alert alert-info">
-É importante acompanhar regularmente os pedidos no módulo <b>Pedidos</b> Caso exijam aprovação manual, os pedidos permanecem pendentes até que um usuário habilitado conceda a autorização necessária.
-</div>
+>ℹ️ É importante acompanhar regularmente os pedidos no módulo **Pedidos** Caso exijam aprovação manual, os pedidos permanecem pendentes até que um usuário habilitado conceda a autorização necessária.
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/prices-settings.md b/docs/tutorials/pt/prices-settings.md
index ddb03c239..f09b0661d 100644
--- a/docs/tutorials/pt/prices-settings.md
+++ b/docs/tutorials/pt/prices-settings.md
@@ -35,6 +35,4 @@ Veja as configurações disponíveis a seguir:
 
 - **Sobrescrever preços de sellers:** permite sobrescrever todos os preços de sellers com os da conta atual.
 
-  <div class = "alert alert-info">
-    <p>A configuração <b>Sobrescrever preços de sellers</b> não é disponível para sellers white label.</p>
-  </div>
+  >ℹ️ A configuração **Sobrescrever preços de sellers** não é disponível para sellers white label.
diff --git a/docs/tutorials/pt/products-and-skus-beta.md b/docs/tutorials/pt/products-and-skus-beta.md
index 036c06104..5c364bb0f 100644
--- a/docs/tutorials/pt/products-and-skus-beta.md
+++ b/docs/tutorials/pt/products-and-skus-beta.md
@@ -15,9 +15,7 @@ legacySlug: produtos-e-skus-beta
 subcategory: 6XPsLadoT3moZ7eTduCg3c
 ---
 
-<div class = "alert alert-info">
-  <p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href = "https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
 
 A página **Produtos e SKUs** possibilita visualizar e gerenciar a lista completa de produtos cadastrados na sua loja, incluindo informações sobre SKUs, data da última atualização e status. Para acessá-la, entre no menu **Catálogo > Produtos e SKUs**.
 
diff --git a/docs/tutorials/pt/promotion-alerts-beta.md b/docs/tutorials/pt/promotion-alerts-beta.md
index 0e8d70641..2db0379a0 100644
--- a/docs/tutorials/pt/promotion-alerts-beta.md
+++ b/docs/tutorials/pt/promotion-alerts-beta.md
@@ -15,9 +15,7 @@ legacySlug: alerta-de-promocoes-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class = "alert alert-info">
-Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Criar promoções é uma boa estratégia para atrair mais compradores para o ecommerce. Ao configurá-las, é fundamental ter atenção para que os descontos aplicados resultem nos efeitos esperados, pois erros durante o cadastro de promoções podem causar perdas de receita.
 
diff --git a/docs/tutorials/pt/promotion-alerts-how-to-create-an-alert-beta.md b/docs/tutorials/pt/promotion-alerts-how-to-create-an-alert-beta.md
index a0d3355ec..2468dba13 100644
--- a/docs/tutorials/pt/promotion-alerts-how-to-create-an-alert-beta.md
+++ b/docs/tutorials/pt/promotion-alerts-how-to-create-an-alert-beta.md
@@ -15,9 +15,7 @@ legacySlug: alerta-de-promocoes-como-criar-um-alerta-beta
 subcategory: 6iTRZiMeCGXYiO2ckABFZi
 ---
 
-<div class = "alert alert-info">
-Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.
-</div>
+>ℹ️ Este módulo está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 Criar promoções é uma boa estratégia para atrair mais compradores para o ecommerce. Ao configurá-las, é fundamental ter atenção para que os descontos aplicados resultem nos efeitos esperados, pois erros durante o cadastro de promoções podem causar perdas de receita.
 
diff --git a/docs/tutorials/pt/promotion-examples.md b/docs/tutorials/pt/promotion-examples.md
index 19f9c71e7..b7bbbe413 100644
--- a/docs/tutorials/pt/promotion-examples.md
+++ b/docs/tutorials/pt/promotion-examples.md
@@ -95,9 +95,7 @@ Compre um suéter e ganhe 50% de desconto em uma camisa clássica ou contemporâ
 - “Compre um suéter e ganhe 50% de desconto” em outro item faz com que esta seja uma [Promoção Compre Junto](https://help.vtex.com/pt/tutorial/buy-together--tutorials_323).
 - “Suéter e camisa clássica ou contemporânea de manga comprida” são os itens aos quais este benefício será aplicado.
 
-<div class = "alert alert-warning">
-  <p>A Promoção Compre Junto funciona apenas com descontos percentuais.</p>
-</div>
+>⚠️ A Promoção Compre Junto funciona apenas com descontos percentuais.
 
 ## Cenário 12
 
diff --git a/docs/tutorials/pt/protection-against-transaction-attacks.md b/docs/tutorials/pt/protection-against-transaction-attacks.md
index 1bd91a0d8..4c093fef2 100644
--- a/docs/tutorials/pt/protection-against-transaction-attacks.md
+++ b/docs/tutorials/pt/protection-against-transaction-attacks.md
@@ -21,8 +21,7 @@ A proteção contra ataques envolvendo transações é uma das soluções que a
 
 Na primeira versão, ao ser ativada, a proteção consistirá em aplicar uma alteração no fluxo de pagamento da compra. Este procedimento não causará um aumento no tempo do pedido ou na diminuição da conversão da loja. Uma vez que o pedido esteja fechado, o consumidor receberá a mensagem de pagamento aprovado (ou reprovado) posteriormente via mensagem eletrônica (email ou SMS).
 
-<div class = "alert alert-info"> A proteção não impede totalmente que a loja sofra ataques de cartões, mas reduz de forma considerável o número desses eventos. Desta forma, as transações tornam-se mais seguras.
-</div>
+>ℹ️ A proteção não impede totalmente que a loja sofra ataques de cartões, mas reduz de forma considerável o número desses eventos. Desta forma, as transações tornam-se mais seguras.
 
 ### Como habilitar a proteção contra ataques em transações?
 
@@ -42,8 +41,7 @@ Para habilitar a proteção, confira o passo a passo:
 
 ### Como desabilitar a proteção contra ataques em transações?
 
-<div class = "alert alert-danger"> Desabilitar a proteção contra ataques em transações aumenta o risco para o lojista de fraude por teste de cartão (operação efetuada por um fraudador utilizando um grande número de dados de cartões para realizar transações fraudulentas). Em caso de ataques que possam prejudicar um ou mais sistemas internos da VTEX, a plataforma poderá reabilitar compulsoriamente a proteção contra ataques, e o lojista será informado desta operação.
-</div>
+>❗ Desabilitar a proteção contra ataques em transações aumenta o risco para o lojista de fraude por teste de cartão (operação efetuada por um fraudador utilizando um grande número de dados de cartões para realizar transações fraudulentas). Em caso de ataques que possam prejudicar um ou mais sistemas internos da VTEX, a plataforma poderá reabilitar compulsoriamente a proteção contra ataques, e o lojista será informado desta operação.
 
 Para desabilitar a proteção, confira o passo a passo:
 
diff --git a/docs/tutorials/pt/ready-to-dispatch.md b/docs/tutorials/pt/ready-to-dispatch.md
index 99c9b7b31..1b104097c 100644
--- a/docs/tutorials/pt/ready-to-dispatch.md
+++ b/docs/tutorials/pt/ready-to-dispatch.md
@@ -27,9 +27,7 @@ Quando um pedido está pronto para o envio e com a nota fiscal inserida na plata
 
 Para gerar etiquetas padronizadas e notificar as transportadoras do envio automaticamente, o [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/) tem a funcionalidade **Pronto para envio**.
 
-<div class = "alert alert-info">
-Além de emitir etiquetas de envio pelo Admin VTEX com a funcionalidade <b>Pronto para envio</b>, você pode fazer isso por API conectada diretamente ao seu ERP. Saiba  mais na nossa documentação para desenvolvedores <a href="https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration">VTEX Shipping Network Labels Integration</a>.
-</div>
+>ℹ️ Além de emitir etiquetas de envio pelo Admin VTEX com a funcionalidade **Pronto para envio**, você pode fazer isso por API conectada diretamente ao seu ERP. Saiba  mais na nossa documentação para desenvolvedores [VTEX Shipping Network Labels Integration](https://developers.vtex.com/docs/guides/vtex-shipping-network-labels-integration).
 
 O sistema da VTEX identifica o número de pacotes de um pedido de acordo com o número de notas fiscais desse pedido, de forma que o número de etiquetas que o lojista pode imprimir para cada pedido corresponde ao número de notas fiscais. 
 
@@ -40,9 +38,7 @@ Para emitir etiquetas pelo seu Admin VTEX, acesse **Envio > Pronto para envio**,
 * Imprimir uma nova etiqueta de envio, na aba [Pronto para etiquetar](#pronto-para-etiquetar).
 * Acessar etiquetas impressas previamente, na aba [Pacotes enviados](#pacotes-enviados).
 
-<div class = "alert alert-info">
-O pedido só aparecerá em <b>Pronto para envio</b> após o <a href="https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#tabela-de-status-de-pedidos">status</a> <i>faturado</i>. Não é possível gerar a etiqueta de um pedido não faturado.
-</div>
+>ℹ️ O pedido só aparecerá em **Pronto para envio** após o [status](https://help.vtex.com/pt/tutorial/fluxo-e-status-de-pedidos--tutorials_196#tabela-de-status-de-pedidos) <i>faturado</i>. Não é possível gerar a etiqueta de um pedido não faturado.
 
 ## Aba Pronto para etiquetar 
 
@@ -112,9 +108,7 @@ Feito isso, você terá alterado o tipo das dimensões das etiquetas.
 
 No seu Admin VTEX, em **Envio > Pronto para envio**, a aba `Pacotes enviados` disponibiliza a consulta de pacotes que já tiveram as etiquetas de envio baixadas. Além disso, você pode reimprimir as etiquetas e _Notfis_.
 
-<div class = "alert alert-info">
-<i>Notfis</i> é o arquivo da mensagem usada na comunicação entre a sua loja e a transportadora. Esse arquivo contém os dados das notas fiscais dos pacotes enviados. Quando uma transportadora não é integrada ao <b>VTEX Shipping Network</b>, apenas o arquivo <i>notfis</i> fica disponível para download.
-</div>
+>ℹ️ <i>Notfis</i> é o arquivo da mensagem usada na comunicação entre a sua loja e a transportadora. Esse arquivo contém os dados das notas fiscais dos pacotes enviados. Quando uma transportadora não é integrada ao **VTEX Shipping Network**, apenas o arquivo <i>notfis</i> fica disponível para download.
 
 Na aba `Pacotes enviados`, para buscar por pedidos na lista de pacotes com etiquetas baixadas, você pode:
 
diff --git a/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md b/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
index 1f500fe12..a460b2003 100644
--- a/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
+++ b/docs/tutorials/pt/recovering-abandoned-checkouts-with-whatsapp-ai-campaigns.md
@@ -25,9 +25,7 @@ Os principais benefícios dessa funcionalidade são:
 
 - **Aumento nas taxas de conversão e vendas:** incentiva que os clientes retornem à página de pagamento para finalizar sua compra, aumentando desta forma as vendas e taxas de conversão para lojistas.
 
-<div class = "alert alert-info">
-O WhatsApp AI Campaigns está disponível  apenas para lojas que utilizam <a href="https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework">Store Framework</a> que não tenham customizações no Checkout.
-</div>
+>ℹ️ O WhatsApp AI Campaigns está disponível  apenas para lojas que utilizam [Store Framework](https://help.vtex.com/tracks/store-development--3fHF3GIjK8UugnQKIakpl9/5DTcawNjc5MovtD7HNqURl#store-framework) que não tenham customizações no Checkout.
 
 ## Ativando WhatsApp AI Campaigns
 
@@ -96,7 +94,5 @@ Para configurar um novo número de WhatsApp você precisará ter acesso de admin
 
 >⚠️ Após ativada uma campanha de recuperação de checkout abandonado, pode levar até 48 horas para as métricas de análise começarem a ser exibidas.
 
-<div class = "alert alert-info">
-Saiba mais sobre o <a href="https://help.vtex.com/pt/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s">Gerenciamento e detalhes do WhatsApp AI Campaigns</a>.
-</div>
+>ℹ️ Saiba mais sobre o [Gerenciamento e detalhes do WhatsApp AI Campaigns](https://help.vtex.com/pt/tutorial/gerenciamento-e-detalhes-do-whatsapp-ai-campaigns--q9JqDErMqGV4zvsYqkD4s).
 
diff --git a/docs/tutorials/pt/register-tracking-on-the-tax-receipt.md b/docs/tutorials/pt/register-tracking-on-the-tax-receipt.md
index 4bbb570a0..ec7f42171 100644
--- a/docs/tutorials/pt/register-tracking-on-the-tax-receipt.md
+++ b/docs/tutorials/pt/register-tracking-on-the-tax-receipt.md
@@ -30,6 +30,4 @@ Para cadastrar o rastreio na nota fiscal, siga os passos abaixo:
     - Transportadora
 7. Clique em `Salvar nota fiscal`. 
 
-<div class = "alert alert-info">
-No momento de cadastrar o rastreio na nota fiscal, é possível alterar a <a href="https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE">transportadora</a> associada ao pedido. Para isso na etapa de preenchimento do <b>Rastreamento do pedido</b>, clique em <i>Transportadora</i> e selecione a opção desejada.
-</div>
+>ℹ️ No momento de cadastrar o rastreio na nota fiscal, é possível alterar a [transportadora](https://help.vtex.com/pt/tutorial/transportadoras-na-vtex--7u9duMD5UQa2QQwukAWMcE) associada ao pedido. Para isso na etapa de preenchimento do **Rastreamento do pedido**, clique em <i>Transportadora</i> e selecione a opção desejada.
diff --git a/docs/tutorials/pt/registering-gateway-affiliations.md b/docs/tutorials/pt/registering-gateway-affiliations.md
index e90f10e98..b5ec65c59 100644
--- a/docs/tutorials/pt/registering-gateway-affiliations.md
+++ b/docs/tutorials/pt/registering-gateway-affiliations.md
@@ -36,13 +36,9 @@ Para adicionar um novo provedor de pagamento ou antifraude em sua loja, siga os
 5. Caso seja exibida uma mensagem de alerta indicando a necessidade de instalação do app, clique no botão __Instalar app__ e siga as instruções de instalação. Esta mensagem é exibida somente para alguns tipos de afiliações de gateway.
 6. Clique em `Salvar`.
 
-<div class = "alert alert-info">
-  <p>Caso haja outros campos a serem preenchidos além do <b>Chave de aplicação</b> e <b>Token de aplicação</b> (Passo 6), o provedor deve ser configurado conforme tutorial específico. Para maiores informações, verifique a subseção <a href="https://help.vtex.com/pt/subcategory/configuracoes-de-pagamentos--3tDGibM2tqMyqIyukqmmMw">Configurações de Pagamento</a>.</p>
-</div>
+>ℹ️ Caso haja outros campos a serem preenchidos além do **Chave de aplicação** e **Token de aplicação** (Passo 6), o provedor deve ser configurado conforme tutorial específico. Para maiores informações, verifique a subseção [Configurações de Pagamento](https://help.vtex.com/pt/subcategory/configuracoes-de-pagamentos--3tDGibM2tqMyqIyukqmmMw).
 
-<div class = "alert alert-danger">
-  As credenciais utilizadas para preencher os campos <strong>Chave de aplicação</strong> e <strong>Token de aplicação</strong> devem ser fornecidas pelo provedor de pagamentos para identificar a loja. Não devem ser utilizadas <a href="https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet#gerar-chaves-de-aplicacao-na-sua-conta">credenciais geradas no Admin</a>, que se iniciam com <code>vtexappkey-</code>.
-</div>
+>❗ As credenciais utilizadas para preencher os campos **Chave de aplicação** e **Token de aplicação** devem ser fornecidas pelo provedor de pagamentos para identificar a loja. Não devem ser utilizadas [credenciais geradas no Admin](https://help.vtex.com/pt/tutorial/chaves-de-aplicacao--2iffYzlvvz4BDMr6WGUtet#gerar-chaves-de-aplicacao-na-sua-conta), que se iniciam com `vtexappkey-`.
 
 Para configurar os métodos de pagamento a serem processados pelo provedor de pagamento escolhido, acesse [Condições de Pagamento](https://help.vtex.com/pt/tutorial/condicoes-de-pagamento). 
 
@@ -76,8 +72,7 @@ Para selecionar a exibição de provedores por meio de filtros, acesse a página
 
 ![interface_provedor_PT_6](https://images.ctfassets.net/alneenqid6w5/36BloW94uLYLN7qGFO1HeP/fe3d094d3ce7e5463841694309b28a52/interface_provedor_PT_6.JPG)
 
-<div class = "alert alert-danger">
-Para remover os filtros aplicados e voltar a visualizar todos os provedores cadastrados na loja, clique no botão <code>Limpar todos</code>.</div>
+>❗ Para remover os filtros aplicados e voltar a visualizar todos os provedores cadastrados na loja, clique no botão `Limpar todos`.
 
 ### Editar configurações de provedores
 
@@ -90,6 +85,5 @@ Para editar configurações de provedores de pagamento ou antifraude já cadastr
 
 ![interface_provedor_PT_7](https://images.ctfassets.net/alneenqid6w5/49bqIpjzfjB6VGrjwMiYEK/1852b341c59e2ac6419504214fcfdee0/artigo_interface_provedor_PT_7.JPG)
 
-<div class = "alert alert-danger">
-Antes de realizar qualquer alteração na configuração de um provedor, como por exemplo: dados de autorização, modo de processamento ou tipo de reembolso, certifique-se de que as novas informações a serem inseridas não irão prejudicar o seu desempenho operacional na loja.</div>
+>❗ Antes de realizar qualquer alteração na configuração de um provedor, como por exemplo: dados de autorização, modo de processamento ou tipo de reembolso, certifique-se de que as novas informações a serem inseridas não irão prejudicar o seu desempenho operacional na loja.
 
diff --git a/docs/tutorials/pt/regular-promotion.md b/docs/tutorials/pt/regular-promotion.md
index e1d15ffcd..486b2ad0d 100644
--- a/docs/tutorials/pt/regular-promotion.md
+++ b/docs/tutorials/pt/regular-promotion.md
@@ -47,9 +47,7 @@ Nesta seção, você deve configurar as informações gerais da sua promoção.
   - **Frete máximo**: valor máximo que o frete poderá assumir. 
   - **Frete grátis**: desconto total sobre o valor do frete.
   - **Brinde**: desconto total sobre o valor do produto definido como brinde. Você pode selecionar um ou mais SKUs como brinde ou mais de uma unidade do mesmo SKU. Para definir mais de um brinde, selecione a opção **Ativar multiplicador de brindes** e defina a quantidade desejada. Saiba mais sobre essa opção neste [artigo](https://help.vtex.com/pt/tutorial/o-que-significa-ativar-o-multiplicador-de-brinde-em-uma-promocao--1gydgkmjEWcoo2CskUwuYK#).
-  <div class = "alert alert-info">
-  <p>O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido gratuitamente ao cliente.</p>
- </div>
+  >ℹ️ O produto Brinde também precisa ter um preço cadastrado, mesmo sendo oferecido gratuitamente ao cliente.
 
   - **Desconto nominal baseado em fórmula**: o desconto é calculado com base na fórmula que você pode criar usando como variáveis a soma dos preços de produtos, o frete e a quantidade de itens. Observe que o frete considerado pela fórmula será o menor disponível para o pedido, independentemente da seleção do cliente. O separador decimal deve ser sempre o ponto. Exemplo: se o desconto for 30% do valor total do produto + valor do frete, a fórmula deve ser `(total + freight) * 0.3`. Para obter mais informações sobre a fórmula, leia nossa [documentação](https://help.vtex.com/pt/tutorial/promocao-regular-com-desconto-nominal-baseado-em-formula--2Pwrq6THyGViNedQG381jV).
   - **Valor fidelidade nominal**: crédito que será adicionado no programa de fidelidade da loja. Leia [Promoção regular com valor fidelidade](https://help.vtex.com/pt/tutorial/promocao-regular-com-valor-fidelidade--3FCip23ZtvG0sDt0rVGVmR) para mais informações.
@@ -58,9 +56,7 @@ Nesta seção, você deve configurar as informações gerais da sua promoção.
 
 - **Destaque nos produtos**: insere uma flag com o nome da promoção, utilizada na vitrine e na página de produto. Essa flag só será inserida caso use o controle correto de exibição de promoção no template: `<vtex.cmc:discountHightLight/>`
 
-<div class = "alert alert-info">
-  <p><b>OBS:</b> Promoções do tipo <b>Nominal</b> só serão apresentadas no carrinho, e não na vitrine ou na página de produto.</p>
-</div>
+>ℹ️ **OBS:** Promoções do tipo **Nominal** só serão apresentadas no carrinho, e não na vitrine ou na página de produto.
 
 ### Restringir esta promoção a produtos dos sellers
 
@@ -71,9 +67,7 @@ Nesta seção, é possível definir para quais sellers a promoção será aplica
 
 Para que a promoção seja válida para todos os sellers, deixe a seleção vazia.
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:</p><ol>1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.</ol><ol>2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.</ol>
-</div>
+>⚠️ **Atenção:** não é possível selecionar diretamente um seller white label. Para incluir um seller white na promoção, existem duas opções:1. Restringir os sellers à loja principal. Essa restrição adiciona todos os sellers white label da sua loja à promoção.2. Deixar a seleção vazia, incluindo todos os sellers. Aqui, todos os tipos de sellers - white label ou não - serão adicionados à promoção.
 
 ### Política Comercial
 
@@ -104,9 +98,7 @@ Veja um exemplo de preenchimento abaixo. Nesse caso, participam da promoção to
 
 Nos campos **Produtos** e **SKUs**, existe a opção de fazer o upload de um arquivo **.txt** com um ID de produto ou de SKU por linha, em vez de selecionar um produto ou um SKU de cada vez. Para isso, você precisa clicar em **Escolher arquivo** e selecionar o arquivo **.txt** desejado.
 
-<div class = "alert alert-warning">
-<p>Se você selecionar <strong>Aplicar aos seguintes produtos</strong> e não preencher nenhum dos critérios de seleção, a promoção não será cadastrada e a mensagem <strong>Defina os produtos elegíveis ou aplique a todos os produtos</strong> será exibida. Nesse caso, você deve retornar e preencher os critérios de seleção ou optar por <strong>Aplicar a todos os produtos</strong>.</p>
-</div>
+>⚠️ Se você selecionar **Aplicar aos seguintes produtos** e não preencher nenhum dos critérios de seleção, a promoção não será cadastrada e a mensagem **Defina os produtos elegíveis ou aplique a todos os produtos** será exibida. Nesse caso, você deve retornar e preencher os critérios de seleção ou optar por **Aplicar a todos os produtos**.
 
 Para serem válidos na promoção, os produtos precisam atender a todas as condições cadastradas nesta seção.
 
@@ -129,24 +121,18 @@ O pedido do cliente deve atender às condições cadastradas nesta seção para
 - **Aplicar o desconto somente quando uma das transportadoras acima for selecionada pelo cliente**: a promoção será aplicada somente após o cliente efetivamente selecionar a forma de entrega em questão. Enquanto não for selecionada, ela ficará sem o desconto. Esse critério somente será considerado se o tipo da promoção for relativo ao valor de frete, ou seja, somente se for um dos seguintes tipos: Frete percentual, Frete nominal, Frete máximo ou Frete grátis.
 - **Meio de pagamento:** o desconto será concedido caso a forma de pagamento selecionada pelo cliente seja a mesma cadastrada na promoção. Esse desconto somente será aplicado na finalização da compra, quando o cliente selecionar a mesma forma de pagamento cadastrada.
 
-  <div class = "alert alert-info">
-  <p> Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
- </div>
+  >ℹ️ Por padrão, você pode cadastrar até 20 meios de pagamento por promoção. Além disso, existe a possibilidade de customização para incluir até 100 meios de pagamento. Caso precise utilizar mais de 20, entre em contato com o [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 - **Número de parcelas**: o desconto será concedido caso o número de parcelas selecionadas pelo cliente estiver no intervalo cadastrado. Esse campo não se aplica para a seleção de boleto. 
 
-<div class = "alert alert-warning">
-  <p><b>Atenção</b>: promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.</p>
-</div>
+>⚠️ **Atenção**: promoções por forma de pagamento e número de parcelas não atendem a pedidos pagos com dois cartões ou vale-compras.
 
 - **Utm_source:** o desconto será concedido caso a navegação seja realizada com as **utm_source** correspondente a qualquer um dos valores cadastrados. É importante destacar que o cliente pode inserir apenas um **utm_source** no checkout.
 - **Utm_campaign:** o desconto será concedido caso a navegação seja realizada com a utm_campaign com o valor cadastrado.
 - **Criar cupom a partir das UTMs acima:** cria um cupom a partir das UTMs cadastradas para dar ao cliente acesso à essa promoção sem a necessidade das utms, apenas com o código do cupom.
 - **Utmi_cp:** o desconto será concedido caso a navegação seja realizada com a utmi_cp com o valor cadastrado (case sensitive).
 
-<div class = "alert alert-info">
-     <p>No campo das UTMs coloque somente o valor que as UTMs terão que assumir para ativar a promoção. Não é necessário colocar <i>?utm_source=</i> dentro do campo.</p>
-  </div>
+>ℹ️ No campo das UTMs coloque somente o valor que as UTMs terão que assumir para ativar a promoção. Não é necessário colocar <i>?utm_source=</i> dentro do campo.
 
 - **Apenas na primeira compra:** o desconto só será concedido na primeira compra do cliente.
 - **É um pedido de assinatura**: opção que define que a promoção será aplicada para pedidos de assinatura. Veja as condições a seguir:
diff --git a/docs/tutorials/pt/releases-module-beta.md b/docs/tutorials/pt/releases-module-beta.md
index 135a34c11..67b79580c 100644
--- a/docs/tutorials/pt/releases-module-beta.md
+++ b/docs/tutorials/pt/releases-module-beta.md
@@ -28,9 +28,7 @@ Os principais benefícios com o módulo são:
 - Maior controle ao testar e revisar mudanças antes da publicação.
 - Facilidade em agendar ou excluir grupos de modificações.
 
-<div class = "alert alert-info">
-Para utilizar o módulo <b>Lançamentos</b> é necessário realizar a configuração do CMS. Saiba mais em <a href="https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS">Installing Releases on VTEX Headless CMS</a>.
-</div>
+>ℹ️ Para utilizar o módulo **Lançamentos** é necessário realizar a configuração do CMS. Saiba mais em [Installing Releases on VTEX Headless CMS](https://www.faststore.dev/how-to-guides/cms/vtex-headless-cms/Installing%20Releases%20on%20VTEX%20Headless%20CMS).
 
 O artigo trata adiante dos seguintes tópicos:
 
@@ -65,9 +63,7 @@ Siga o passo a passo abaixo para criar um lançamento:
 6. Clique em `Criar um lançamento`.
 7. Preencha o campo _Nome_ com um nome para o lançamento.
 
-  <div class = "alert alert-info">
-Nesta etapa, não é obrigatório preencher os campos <b>Dia da publicação</b> e Hora</b>. Isso pode ser determinado depois, como será visto em <a href="https://help.vtex.com/pt/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#agendar-lancamentos">Agendar lançamentos</a>.
-</div>
+  >ℹ️ Nesta etapa, não é obrigatório preencher os campos **Dia da publicação** e Hora</b>. Isso pode ser determinado depois, como será visto em [Agendar lançamentos](https://help.vtex.com/pt/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#agendar-lancamentos).
 
 8. Clique em `Criar`.
 
@@ -82,9 +78,7 @@ Siga o passo a passo abaixo para criar um lançamento:
 2. Clique no botão `Criar`.
 3. Preencha o campo _Nome_ com um nome para o lançamento.
 
-  <div class = "alert alert-info">
-Nesta etapa, não é obrigatório preencher os campos <b>Dia da publicação</b> e Hora</b>. Isso pode ser determinado depois, como será visto em <a href="https://help.vtex.com/pt/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#agendar-lancamentos">Agendar lançamentos</a>.
-</div>
+  >ℹ️ Nesta etapa, não é obrigatório preencher os campos **Dia da publicação** e Hora</b>. Isso pode ser determinado depois, como será visto em [Agendar lançamentos](https://help.vtex.com/pt/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#agendar-lancamentos).
 
 4. Clique em `Criar`.
 
@@ -127,9 +121,7 @@ Na criação de um lançamento, é possível definir ou não a data de publicaç
 - **Desagendar:** cancelar a data de publicação, o que faz o lançamento passar para o status `Não agendado`.
 - **Reagendar:** definir uma nova data para um lançamento que já tinha data determinada.
 
-<div class = "alert alert-info">
-Ao agendar ou reagendar a publicação de um lançamento, é possível selecionar a opção <b>Adicionar data de fim</b>, de forma a definir um prazo para o lançamento ser despublicado. A data fim não significa a <a href="https://help.vtex.com/pt/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#excluir-lancamentos">exclusão do lançamento</a>, e sim o seu arquivamento, podendo o lançamento ser publicado novamente a qualquer tempo.
-</div>
+>ℹ️ Ao agendar ou reagendar a publicação de um lançamento, é possível selecionar a opção **Adicionar data de fim**, de forma a definir um prazo para o lançamento ser despublicado. A data fim não significa a [exclusão do lançamento](https://help.vtex.com/pt/tutorial/modulo-lancamentos-beta--n2tN0WX5I6MJMbrJrS0Kb#excluir-lancamentos), e sim o seu arquivamento, podendo o lançamento ser publicado novamente a qualquer tempo.
 
 ### Agendar
 
diff --git a/docs/tutorials/pt/returning-order-items.md b/docs/tutorials/pt/returning-order-items.md
index eaf7a3a23..1b67f80f9 100644
--- a/docs/tutorials/pt/returning-order-items.md
+++ b/docs/tutorials/pt/returning-order-items.md
@@ -17,9 +17,7 @@ subcategory: 2t00bBkcAwIkgSCGKsMOwY
 
 Os clientes da sua loja podem solicitar a troca ou devolução de itens de um pedido. Dessa forma, a funcionalidade **Devolução de itens** permite remover itens de um pedido para que produtos sejam devolvidos.
 
-<div class = "alert alert-info">
-Consulte o artigo <a href="https://help.vtex.com/pt/tutorial/como-devolver-itens-do-pedido-beta--2bSNWwD0g8fcUmuupLao9i">Como devolver itens do pedido (Beta)</a> para saber como utilizar a funcionalidade no Admin V4.
-</div>
+>ℹ️ Consulte o artigo [Como devolver itens do pedido (Beta)](https://help.vtex.com/pt/tutorial/como-devolver-itens-do-pedido-beta--2bSNWwD0g8fcUmuupLao9i) para saber como utilizar a funcionalidade no Admin V4.
 
 Para realizar a devolução pelo Admin VTEX, realize os seguintes passos:
 
diff --git a/docs/tutorials/pt/sales-associates-instore-beta.md b/docs/tutorials/pt/sales-associates-instore-beta.md
index bd3bcd2f8..45d4075a5 100644
--- a/docs/tutorials/pt/sales-associates-instore-beta.md
+++ b/docs/tutorials/pt/sales-associates-instore-beta.md
@@ -15,9 +15,7 @@ legacySlug: vendedores-instore-beta
 subcategory: 5SE2asHiQtHKfbnFru8RWH
 ---
 
-<div class ="alert alert-info">
-<p>Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com <a href="https://support.vtex.com/hc/pt-br/requests">nosso Suporte</a>.</p>
-</div>
+>ℹ️ Essa funcionalidade está em fase Beta, o que significa que estamos trabalhando para aprimorá-la. Em caso de dúvidas, entre em contato com [nosso Suporte](https://support.vtex.com/hc/pt-br/requests).
 
 **Vendedores** é uma página das **Configurações da loja** do Admin VTEX que apresenta a listagem de vendedores cadastrados no aplicativo [inStore](https://help.vtex.com/pt/tracks/instore-primeiros-passos-e-configuracoes--zav76TFEZlAjnyBVL5tRc/7fnnVlG3Kv1Tay9iagc5yf) da loja. Nela, você pode gerenciar informações dos vendedores em todas as [contas franquias](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) da sua loja.
 
@@ -54,9 +52,7 @@ Após o cadastro, o vendedor irá receber um email confirmando o cadastro e redi
 
 ![email-vendedor-pt](https://images.ctfassets.net/alneenqid6w5/28VbbIXujzHcE3BriNtZPq/3aa9729eb2211875302b7316dbe46c93/image.png)
 
-<div class ="alert alert-warning">
-<p>Os vendedores cadastrados no inStore não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin seu cadastro será excluído.</p> 
-</div>
+>⚠️ Os vendedores cadastrados no inStore não apresentam permissão para acessar o Admin VTEX. Caso um vendedor tente realizar o login no Admin seu cadastro será excluído.
 
 ### Campos de cadastro do vendedor
 
@@ -70,9 +66,7 @@ Após o cadastro, o vendedor irá receber um email confirmando o cadastro e redi
 
 * **Loja:** [conta franquia](https://help.vtex.com/pt/tutorial/o-que-e-conta-franquia--kWQC6RkFSCUFGgY5gSjdl) em que o vendedor será cadastrado. Campo obrigatório.
 
-<div class ="alert alert-info">
-<p>As alterações podem levar até 15 minutos para serem processadas e aplicadas no inStore.</p> 
-</div>
+>ℹ️ As alterações podem levar até 15 minutos para serem processadas e aplicadas no inStore.
 
 ## Buscar vendedor
 
diff --git a/docs/tutorials/pt/sales-performance.md b/docs/tutorials/pt/sales-performance.md
index 9a2a78cf3..5a11948b1 100644
--- a/docs/tutorials/pt/sales-performance.md
+++ b/docs/tutorials/pt/sales-performance.md
@@ -35,9 +35,7 @@ Para garantir que você tenha acesso tanto aos últimos dados atualizados e tamb
 
 Esses grupos também são processados por sistemas diferentes, o que pode causar uma diferença entre dados do OMS e do Performance de Vendas, apesar de buscarmos apresentar no máximo 5% de divergência. 
 
-<div class ="alert alert-warning">
-É provável que existam diferenças entre as métricas de receita e ticket médio registradas no OMS e no Performance de Vendas, por exemplo. Isso ocorre porque o Performance de Vendas considera o valor dos itens, enquanto o OMS também considera os descontos, frete, taxas e promoções sobre o pedido - o que pode aumentar ou diminuir seu valor final. 
-</div>
+>⚠️ É provável que existam diferenças entre as métricas de receita e ticket médio registradas no OMS e no Performance de Vendas, por exemplo. Isso ocorre porque o Performance de Vendas considera o valor dos itens, enquanto o OMS também considera os descontos, frete, taxas e promoções sobre o pedido - o que pode aumentar ou diminuir seu valor final.
 
 ## Período
 
diff --git a/docs/tutorials/pt/search-behavior.md b/docs/tutorials/pt/search-behavior.md
index 60cd47ceb..e03a20a10 100644
--- a/docs/tutorials/pt/search-behavior.md
+++ b/docs/tutorials/pt/search-behavior.md
@@ -49,9 +49,7 @@ Exemplo: suponha que um cliente queira pesquisar pelo termo `bola`. Seguindo a c
 * `bora` (trocar 1 caractere)
 * `obla` (trocar 2 caracteres que ficam um do lado do outro entre eles)
 
-<div class ="alert alert-info">
-	<p>Espaços em branco não são considerados no <em>fuzzy</em>, então <code>base ball</code> não será corrigido para <code>baseball</code>, por exemplo. Recomendamos o uso de <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV">sinônimos</a> para esses casos.</p>
-</div>
+>ℹ️ Espaços em branco não são considerados no *fuzzy*, então `base ball` não será corrigido para `baseball`, por exemplo. Recomendamos o uso de [sinônimos](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1pxAWPEglBey1UFdvcetZV) para esses casos.
 
 ### Resultado mínimo
 
@@ -62,9 +60,7 @@ Em uma busca com múltiplos termos, ocorre a lógica a seguir:
 1. Se o resultado mínimo não for atingido mesmo com a autocorreção inicial, a busca passa a incluir resultados mais abrangentes, que apresentam qualquer um dos termos pesquisados. Por exemplo, quando um usuário pesquisa por "tenis nike", mas o catálogo não possui nenhum produto com esse nome, a busca pode apresentar como resultado um produto com apenas o termo "tenis" no nome.
 2. Se a busca abrangente não apresentar o resultado mínimo, ela será repetida aplicando a autocorreção novamente a cada um dos termos.
 
-<div class= "alert alert-warning">
-<p>Buscas com múltiplos termos são mais eficientes quando o cliente ordena os resultados por relevância, já que elas podem ter um número maior de resultados além do contexto que foi buscado. Na ordenação por relevância, ainda priorizam-se os itens relacionados aos múltiplos termos. Porém, ao aplicar outras ordenações, como preço ou mais vendidos, a ordem dos resultados depende desses valores numéricos e não necessariamente prioriza itens que contêm mais palavras dos termos de busca.</p>
-</div>
+>⚠️ Buscas com múltiplos termos são mais eficientes quando o cliente ordena os resultados por relevância, já que elas podem ter um número maior de resultados além do contexto que foi buscado. Na ordenação por relevância, ainda priorizam-se os itens relacionados aos múltiplos termos. Porém, ao aplicar outras ordenações, como preço ou mais vendidos, a ordem dos resultados depende desses valores numéricos e não necessariamente prioriza itens que contêm mais palavras dos termos de busca.
 
 ### Limite de paginação
 
@@ -88,9 +84,7 @@ _Exemplo_: foi configurado que a especificação "cor" é pesquisável e o produ
 
 É possível buscar por caracteres especiais (`-` e `/`) para encontrar um produto.
 
-<div class ="alert alert-warning">
-	<p>A escolha dos campos de busca afeta as possibilidades das <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0">Regras de merchandising</a>, pois apenas campos pesquisáveis podem ser utilizados para configurar as regras. Por exemplo, ao definir somente o campo <strong><code>SKUID</code> </strong>como pesquisável, não será possível promover um <strong><code>ProductID</code> </strong>ou um <strong><code>ProductRefID</code> </strong>utilizando Regras de merchandising.</p>
-</div>
+>⚠️ A escolha dos campos de busca afeta as possibilidades das [Regras de merchandising](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/5tBSYXb9EIdePa0MWTnFd0), pois apenas campos pesquisáveis podem ser utilizados para configurar as regras. Por exemplo, ao definir somente o campo **`SKUID` **como pesquisável, não será possível promover um **`ProductID` **ou um **`ProductRefID` **utilizando Regras de merchandising.
 
 ### Definição e ordenação de campos de filtro
 
@@ -104,9 +98,7 @@ _Exemplo_: um lojista configurou que o critério Promoção possui uma relevânc
 
 Para mais informações sobre como personalizar a ordenação dos resultados de acordo com as necessidades da sua loja, leia o artigo [Configuração de relevância](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/1qlObWIib6KqgrfX1FCOXS).
 
-<div class ="alert alert-info">
-	<p>Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções. Usando o comando <code>map=productClusterIds</code>, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar <code>productClusterNames</code>, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search.</p>
-</div>
+>ℹ️ Ao utilizar o Intelligent Search, existem duas opções que definirão a ordem de suas coleções. Usando o comando `map=productClusterIds`, estará definindo que a ordem de suas coleções será a que foi pré definida pelo lojista, com seu próprio critério de relevância. Se você optar por usar `productClusterNames`, definirá que deseja que suas coleções sigam os padrões de relevância do próprio Intelligent Search.
 
 ## Formas alternativas de busca
 
diff --git a/docs/tutorials/pt/search-control-fulltextsearchbox.md b/docs/tutorials/pt/search-control-fulltextsearchbox.md
index 630f1bacd..5a124719d 100644
--- a/docs/tutorials/pt/search-control-fulltextsearchbox.md
+++ b/docs/tutorials/pt/search-control-fulltextsearchbox.md
@@ -15,9 +15,7 @@ legacySlug: controle-de-busca-fulltextsearchbox
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 O controle `<vtex.cmc:fullTextSearchBox />` é responsável por gerar a caixa de busca. Além do campo de pesquisa o controle renderiza um combo para restringir uma busca em um departamento. Abaixo temos um exemplo do controle sem nenhuma aplicação de css:
 
diff --git a/docs/tutorials/pt/search-navigator-control.md b/docs/tutorials/pt/search-navigator-control.md
index 5da73ee5b..9793f7006 100644
--- a/docs/tutorials/pt/search-navigator-control.md
+++ b/docs/tutorials/pt/search-navigator-control.md
@@ -15,9 +15,7 @@ legacySlug: controle-search-navigator
 subcategory: 2g6LxtasS4iSeGEqeYUuGW
 ---
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 O controle `<vtex.cmc:searchNavigator/>` renderiza um menu de filtros relacionados ao resultado de uma busca.
 
diff --git a/docs/tutorials/pt/search-parameters.md b/docs/tutorials/pt/search-parameters.md
index 97bf6479a..e761c9eaa 100644
--- a/docs/tutorials/pt/search-parameters.md
+++ b/docs/tutorials/pt/search-parameters.md
@@ -15,9 +15,7 @@ legacySlug: parametros-de-busca
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  <strong>Atenção</strong>: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
-</div>
+>⚠️ **Atenção**: a VTEX apresenta duas opções da busca - a busca VTEX e o VTEX Intelligent Search. Esse artigo se refere à busca VTEX. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">nossa track</a>.
 
 Ao realizar buscas na VTEX, existem algumas possibilidades de URLs. Temos as URLs de Departamentos e Categorias, que são formadas da seguinte maneira:
 
@@ -59,9 +57,7 @@ OBS: O ID da categoria também pode ser encontrado em sua página de edição, a
 
 ![](https://images.contentful.com/alneenqid6w5/2CuMf8UzCIkiYyMKUiIOcy/9c354e12e064bdb7f310611f7fc0ee41/id_marca.png)
 
-<div class = "alert alert-warning">
-  <p><b>Atenção:</b> existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.</p>
-</div>
+>⚠️ **Atenção:** existem duas formas de configurar coleções, por meio do CMS ou utilizando o módulo de Coleções Beta. Este artigo, refere-se à <a href = "https://help.vtex.com/pt/tutorial/cadastro-de-colecoes-cms--2YBy6P6X0NFRpkD2ZBxF6L">configuração de coleções por meio do CMS</a>.
 
 **H:\[IdColeção\]**: Retorna produtos de uma determinada coleção, de acordo com o ID informado. Este código é informado na edição da coleção, em **Configurações &gt; Portal &gt; Pasta Portal &gt; Subpasta Coleções:**
 
diff --git a/docs/tutorials/pt/searching-for-events-on-audit.md b/docs/tutorials/pt/searching-for-events-on-audit.md
index ba42390e9..c34a8335f 100644
--- a/docs/tutorials/pt/searching-for-events-on-audit.md
+++ b/docs/tutorials/pt/searching-for-events-on-audit.md
@@ -46,9 +46,7 @@ Note que toda busca realizada é salva na aba **Últimas Buscas**. Para refazer
 
 >⚠️ Apenas 50 buscas ficam gravadas neste painel. Se quiser salvar uma busca indefinidamente, realize a mesma e adicione aos favoritos do seu browser.
 
-<div class = "alert alert-info">
-Confira a <a href="https://help.vtex.com/pt/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ">lista de eventos disponíveis no Audit</a>.
-</div>
+>ℹ️ Confira a [lista de eventos disponíveis no Audit](https://help.vtex.com/pt/tutorial/events-available-in-audit--6r1Mzcu5NmkmmDLJlz9CCZ).
 
 ## Exemplos de filtros de busca 
 
@@ -77,6 +75,4 @@ Confira a <a href="https://help.vtex.com/pt/tutorial/events-available-in-audit--
 
 Para ver mais alguns exemplos de filtros que podem ser utilizados, clique na aba **Guia**. 
 
-<div class = "alert alert-info">
-No aplicativo Audit, <a href="https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3">recursos do License Manager</a> são identificados pelas respectivas chaves.
-</div>
+>ℹ️ No aplicativo Audit, [recursos do License Manager](https://help.vtex.com/pt/tutorial/license-manager-resources--3q6ztrC8YynQf6rdc6euk3) são identificados pelas respectivas chaves.
diff --git a/docs/tutorials/pt/seller-monitoring.md b/docs/tutorials/pt/seller-monitoring.md
index f15f4753a..93fcabed7 100644
--- a/docs/tutorials/pt/seller-monitoring.md
+++ b/docs/tutorials/pt/seller-monitoring.md
@@ -53,7 +53,7 @@ Ao clicar em **`Salvar`**, você receberá notificações no Admin acerca da per
 |**Segmentação***|Você irá definir quais sellers ou grupo de sellers serão afetados pelo valor definido em **Valor limite.**|
 |**Limite preferível**|Valor definido para alertar que o seller está se aproximando do **Valor limite.**|
 
-<div class ="alert alert-info"> Quando há variação configurada em uma métrica, a ordenação define a prioridade. Para casos em que só existe uma segmentação por grupo e outra por exceção, não existe conflito independente da ordenação. </div> 
+>ℹ️ Quando há variação configurada em uma métrica, a ordenação define a prioridade. Para casos em que só existe uma segmentação por grupo e outra por exceção, não existe conflito independente da ordenação. 
 
 ## Editando a métrica
 
diff --git a/docs/tutorials/pt/seller-portal-creating-a-promotion.md b/docs/tutorials/pt/seller-portal-creating-a-promotion.md
index 16b4f8ba2..bd3771c4d 100644
--- a/docs/tutorials/pt/seller-portal-creating-a-promotion.md
+++ b/docs/tutorials/pt/seller-portal-creating-a-promotion.md
@@ -27,9 +27,7 @@ Para criar uma nova promoção como seller no Seller Portal, siga o passo a pass
 
 Feito isso, a promoção será ativada e aplicada na sua loja.
 
-<div class = "alert alert-info">
-As promoções que afetam os mesmos itens inseridos no carrinho são comparadas pelo seu valor de desconto. Nesse caso, o módulo de Promoções procura sempre aplicar a promoção mais vantajosa para o comprador.
-</div>
+>ℹ️ As promoções que afetam os mesmos itens inseridos no carrinho são comparadas pelo seu valor de desconto. Nesse caso, o módulo de Promoções procura sempre aplicar a promoção mais vantajosa para o comprador.
 
 ## Campos de cadastro da promoção
 
diff --git a/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md b/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
index 2ff0b34fa..b01760c3e 100644
--- a/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
+++ b/docs/tutorials/pt/seller-portal-getting-started-for-the-marketplace.md
@@ -60,9 +60,7 @@ A página **Convite de Sellers** é onde operadores de marketplace [convidam sel
 
 Por meio do Seller Portal, marketplaces hospedados na VTEX podem se conectar com sellers que têm conta VTEX, sellers hospedados em outras plataformas ou sellers que não estão hospedados em nenhuma plataforma. Ao aceitar o convite, o seller escolhe se deseja integrar sua conta VTEX existente ou criar uma conta nova para vender no marketplace.
 
-<div class = "alert alert-info">
-Uma vez que o <a href="https://help.vtex.com/pt/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#convidar-seller">marketplace convida o seller</a>, um email é enviado ao seller com um link para criação de conta no Seller Portal. O link é válido por sete dias e, após acessá-lo, o seller tem seis horas para completar o formulário de cadastro, sem interrupções.
-</div>
+>ℹ️ Uma vez que o [marketplace convida o seller](https://help.vtex.com/pt/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#convidar-seller), um email é enviado ao seller com um link para criação de conta no Seller Portal. O link é válido por sete dias e, após acessá-lo, o seller tem seis horas para completar o formulário de cadastro, sem interrupções.
 
 Caso o seller não conclua o cadastro no período previsto, o marketplace precisa enviar o convite novamente. Isso pode ser feito pelo Admin VTEX, em **Marketplace > Convite de Sellers**. É preciso selecionar o seller na lista e clicar no botão **Reenviar convite**.
 
@@ -77,9 +75,7 @@ Para saber mais, confira os seguintes artigos:
 
 Uma vez que o seller aceite o convite do marketplace e finalize o registro da sua conta no Seller Portal, o passo seguinte é a ativação para conectá-lo ao marketplace. Isso faz com que o seller passe do status _Convidado_ para o status _Ativo_, e que ele seja incluído no **Gerenciamento de Sellers**. Confira o passo a passo para ativar o seller em [Conectar seller](https://help.vtex.com/pt/tutorial/marketplace-convite-de-sellers-beta--6rb2FkcslmDueJ689Ulb9A#conectar-seller).
 
-<div class = "alert alert-info">
-A etapa de ativação do seller visa garantir mais segurança ao marketplace, caso seja necessário algum alinhamento com o seller antes que ele comece a vender no marketplace.
-</div>
+>ℹ️ A etapa de ativação do seller visa garantir mais segurança ao marketplace, caso seja necessário algum alinhamento com o seller antes que ele comece a vender no marketplace.
 
 #### Ações por API Rest
 
@@ -102,9 +98,7 @@ Esta etapa é opcional para o marketplace e vai depender do objetivo do seu mode
 
 Quando o marketplace opta pelo compartilhamento, isso é feito por meio de uma [política comercial](https://help.vtex.com/pt/tutorial/como-funciona-uma-politica-comercial--6Xef8PZiFm40kg2STrMkMV). O seller então recebe a lista de produtos já cadastrados no marketplace para importar e configurar estoque e preço no Seller Portal, em **Preços > Produtos Compartilhados**.
 
-<div class = "alert alert-info">
-A criação de uma política comercial adicional por parte do operador do marketplace para definir o sortimento de catálogo de sellers no Seller Portal é cobrada como <a href="https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X">contratação de política comercial adicional</a>.
-</div>
+>ℹ️ A criação de uma política comercial adicional por parte do operador do marketplace para definir o sortimento de catálogo de sellers no Seller Portal é cobrada como [contratação de política comercial adicional](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X).
 
 #### Compartilhamento de Produtos
 
@@ -122,9 +116,7 @@ Na VTEX, [anúncio](https://help.vtex.com/pt/tutorial/anuncios-y-envio-de-produc
 
 Quando o seller cria um novo produto, o marketplace precisa revisar e aprovar o anúncio do produto em um processo chamado [catalogação de anúncios](https://help.vtex.com/pt/tutorial/sugerindo-e-aprovando-skus--tutorials_396). A catalogação permite criar novos produtos e associar anúncios a SKUs ou produtos já existentes para disponibilizá-los para venda.
 
-<div class = "alert alert-info">
-Anúncios de <a href="https://help.vtex.com/pt/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu">produtos compartilhados</a> entre marketplace e seller são aprovados de forma automática, sem necessidade de ação manual.
-</div>
+>ℹ️ Anúncios de [produtos compartilhados](https://help.vtex.com/pt/tutorial/seller-portal-produtos-compartilhados--6vUGj2UmOuLzQTK9pj04lu) entre marketplace e seller são aprovados de forma automática, sem necessidade de ação manual.
 
 O processo de catalogação pode ser realizado pelo Admin VTEX, em **MARKETPLACE > Sellers > SKUs Recebidos**, ou por meio da API [Match Received SKUs](https://developers.vtex.com/vtex-rest-api/reference/match).
 
diff --git a/docs/tutorials/pt/sent-offers-beta.md b/docs/tutorials/pt/sent-offers-beta.md
index aa2ebe7cb..90b6d16cd 100644
--- a/docs/tutorials/pt/sent-offers-beta.md
+++ b/docs/tutorials/pt/sent-offers-beta.md
@@ -39,9 +39,7 @@ Quando um seller configura condições de preço e estoque, ele está preparando
 
 Esse componente lista todos os canais integrados, além dos números de anúncios enviados, anúncios em  processamento e anúncios com erro, para cada canal. Por meio da lista, sellers têm maior visibilidade sobre a saúde das suas integrações com canais externos. 
 
-<div class = "alert alert-info">
-A <b>Anúncios enviados</b> permite acompanhar anúncios com o <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre Classic</a>, <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre Premium</a>, <a href="https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> e <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex">marketplaces VTEX</a>.
-</div>
+>ℹ️ A **Anúncios enviados** permite acompanhar anúncios com o [Mercado Livre Classic](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Mercado Livre Premium](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e [marketplaces VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex).
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/sent-offers-buybox-opportunities.md b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
index 63e8bcc08..9b6a7b72e 100644
--- a/docs/tutorials/pt/sent-offers-buybox-opportunities.md
+++ b/docs/tutorials/pt/sent-offers-buybox-opportunities.md
@@ -28,9 +28,7 @@ Um exemplo de oportunidade é a funcionalidade de Catálogo MeLi. O Catálogo Me
 
 As *Oportunidades* acompanham a presença de um anúncio nas diferentes páginas do módulo **Gerenciamento de anúncios**, como será visto nas imagens a seguir.
 
-<div class = "alert alert-info">
-O <b>Gerenciamento de anúncios</b> permite acompanhar anúncios com o <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre Classic</a>, <a href="https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq">Mercado Livre Premium</a>, <a href="https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm">Netshoes</a> e <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex">marketplaces VTEX</a>. Para conectores que desejam integrar via API, existe o <a href="https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors">Guia de integração do Gerenciamento de anúncios</a>.
-</div>
+>ℹ️ O **Gerenciamento de anúncios** permite acompanhar anúncios com o [Mercado Livre Classic](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Mercado Livre Premium](https://help.vtex.com/pt/tracks/configurar-integracao-do-mercado-livre--2YfvI3Jxe0CGIKoWIGQEIq), [Netshoes](https://help.vtex.com/pt/tracks/configurar-integracao-da-netshoes--5Ua87lhFg4m0kEcuyqmcCm) e [marketplaces VTEX](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#ser-um-marketplace-vtex). Para conectores que desejam integrar via API, existe o [Guia de integração do Gerenciamento de anúncios](https://developers.vtex.com/vtex-rest-api/docs/sent-offers-integration-guide-connectors).
 
 ## Listagem de Anúncios
 
diff --git a/docs/tutorials/pt/set-up-mundi-gateway.md b/docs/tutorials/pt/set-up-mundi-gateway.md
index 2a2b70d77..9dca6c665 100644
--- a/docs/tutorials/pt/set-up-mundi-gateway.md
+++ b/docs/tutorials/pt/set-up-mundi-gateway.md
@@ -17,9 +17,7 @@ subcategory: 3tDGibM2tqMyqIyukqmmMw
 
 Na VTEX, é possível fazer uma integração com o provedor de pagamentos Mundi.
 
-<div class= "alert alert-warning">
-Se desejar utilizar também o antifraude da Mundi, as configurações desta função devem ser realizadas pelo hub da própria empresa. Em caso de dúvidas sobre essa etapa da operação, consulte o suporte técnico da Mundi.
-</div>
+>⚠️ Se desejar utilizar também o antifraude da Mundi, as configurações desta função devem ser realizadas pelo hub da própria empresa. Em caso de dúvidas sobre essa etapa da operação, consulte o suporte técnico da Mundi.
 
 Para configurar Mundi, siga os passos abaixo:
 
diff --git a/docs/tutorials/pt/setting-the-grace-period-for-order-cancellation.md b/docs/tutorials/pt/setting-the-grace-period-for-order-cancellation.md
index 5c7aa08ef..f909f6c1f 100644
--- a/docs/tutorials/pt/setting-the-grace-period-for-order-cancellation.md
+++ b/docs/tutorials/pt/setting-the-grace-period-for-order-cancellation.md
@@ -21,9 +21,7 @@ Ou seja, se o cliente solicitar o cancelamento antes ou durante o período de ca
 
 Se o cliente solicitar o cancelamento depois que a carência tiver terminado, a loja recebe a solicitação, mas o cancelamento só é realizado se o lojista aprová-lo em **Pedidos**.
 
-<div class = "alert alert-info">
-Por padrão, o tempo de carência para cancelamento é de 30 minutos mas você pode configurá-lo para atender à demanda do seu negócio.
-</div>
+>ℹ️ Por padrão, o tempo de carência para cancelamento é de 30 minutos mas você pode configurá-lo para atender à demanda do seu negócio.
 
 Por exemplo, se sua loja vende comida ou produtos farmacêuticos, que precisam ser entregues em pouco tempo, talvez faça sentido ter uma carência para cancelamento menor que 30 minutos.
 
diff --git a/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md b/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md
index 3db324304..b51deaea7 100644
--- a/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md
+++ b/docs/tutorials/pt/setting-up-3ds-2-authentication-flow.md
@@ -21,9 +21,7 @@ O 3D Secure 2.0 (3DS 2) é um fluxo de autenticação que aumenta a segurança n
 
 Antes de iniciar a configuração, é necessário abrir um chamado com o time de suporte da VTEX solicitando a habilitação do 3DS 2 na sua loja. Para maiores informações, acesse [como abrir um ticket](https://help.vtex.com/pt/tutorial/abrir-chamados-para-o-suporte-vtex--16yOEqpO32UQYygSmMSSAM).
 
-<div class = "alert alert-warning">
-<p>Na VTEX, o 3DS 2 não efetua compras realizadas em dois cartões. Caso um pedido seja realizado nessas condições, o pagamento será cancelado.</p>
-</div>
+>⚠️ Na VTEX, o 3DS 2 não efetua compras realizadas em dois cartões. Caso um pedido seja realizado nessas condições, o pagamento será cancelado.
 
 ## Configurando o 3DS 2 
 
diff --git a/docs/tutorials/pt/setting-up-abandoned-carts.md b/docs/tutorials/pt/setting-up-abandoned-carts.md
index b4bb994b2..ebacb062b 100644
--- a/docs/tutorials/pt/setting-up-abandoned-carts.md
+++ b/docs/tutorials/pt/setting-up-abandoned-carts.md
@@ -65,9 +65,7 @@ Uma vez criado o novo template de email ou utilizado os dados do template padrã
 7. Em __Html__, insira as informações do template de email criado ou padrão.
 8. Clique em `Salvar`. 
 
-<div class = "alert alert-info">
-O campo JSON Data não deve ser preenchido ou seus dados utilizados no template do email. Ele contém apenas informações para permitir uma pré-visualização do formato em que os dados que serão visualizados no email.
-</div>
+>ℹ️ O campo JSON Data não deve ser preenchido ou seus dados utilizados no template do email. Ele contém apenas informações para permitir uma pré-visualização do formato em que os dados que serão visualizados no email.
 
 ![New template - message center](https://images.ctfassets.net/alneenqid6w5/7nX1YnaZoesV51yG24Z3ls/68a8a4f2f7ad9f9911598b3aab475817/Novo_template.PNG)
 
diff --git a/docs/tutorials/pt/setting-up-my-account.md b/docs/tutorials/pt/setting-up-my-account.md
index 6433e4d6f..ac23ff054 100644
--- a/docs/tutorials/pt/setting-up-my-account.md
+++ b/docs/tutorials/pt/setting-up-my-account.md
@@ -15,9 +15,7 @@ legacySlug: configurar-o-my-account
 subcategory: 1RWR7qSyaREbD5RfgCjdYG
 ---
 
-<div class = "alert alert-info">
-Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
-</div>
+>ℹ️ Em [Minha Conta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
 
 O novo [My Account](https://help.vtex.com/pt/tutorial/como-funciona-o-my-account--2BQ3GiqhqGJTXsWVuio3Xh) já está instalado em todas as contas VTEX em um <strong>ambiente teste</strong>, permitindo ajustes na nova página sem impactos na experiência do usuário. 
 
diff --git a/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md b/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md
index 2955021ca..41b02218c 100644
--- a/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md
+++ b/docs/tutorials/pt/setting-up-price-and-availability-of-skus-by-region.md
@@ -27,9 +27,7 @@ Para regionalizar os preços e disponibilidades dos SKUs, é necessário:
 
 >⚠️ Em casos de [Multilevel Omnichannel Inventory](https://help.vtex.com/pt/tutorial/multilevel-omnichannel-inventory--7M1xyCZWUyCB7PcjNtOyw4#), um marketplace (nível 1) não pode configurar exibição de preços e disponibilidade de produtos de Sellers White Label (nível 3) com a funcionalidade de regionalização.
 
-<div class = "alert alert-info">
-A feature <b>Region</b> funciona tanto para lojas CMS Portal Legado quanto lojas desenvolvidas utilizando <a href="https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC">VTEX IO</a>, mas a funcionalidade <a href="https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG">VTEX Intelligent Search</a> é válida somente para lojas VTEX IO. Disso resulta que lojas com CMS Portal Legado possuem uma limitação na indexação de dados regionalizados e não é possível ordenar corretamente os sellers que atendem a vitrine de uma RegionId tomando por base a disponibilidade dos itens.
-</div>
+>ℹ️ A feature **Region** funciona tanto para lojas CMS Portal Legado quanto lojas desenvolvidas utilizando [VTEX IO](https://help.vtex.com/pt/tracks/cms--2YcpgIljVaLVQYMzxQbc3z/6OCY6S9tqBXPD5mgpbBInC), mas a funcionalidade [VTEX Intelligent Search](https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb/3qgT47zY08biLP3d5os3DG) é válida somente para lojas VTEX IO. Disso resulta que lojas com CMS Portal Legado possuem uma limitação na indexação de dados regionalizados e não é possível ordenar corretamente os sellers que atendem a vitrine de uma RegionId tomando por base a disponibilidade dos itens.
 
 ## Configurar a entrega na Conta Franquia/Seller White Label
 
diff --git a/docs/tutorials/pt/setting-up-product-comparison.md b/docs/tutorials/pt/setting-up-product-comparison.md
index be571d3dd..88144339a 100644
--- a/docs/tutorials/pt/setting-up-product-comparison.md
+++ b/docs/tutorials/pt/setting-up-product-comparison.md
@@ -24,9 +24,7 @@ Podemos dividir esse recurso em duas partes:
 1. **Página de Comparação**: Onde o usuário visualizará a comparação dos produtos selecionados na vitrine.
 2. **Vitrine**: Onde o usuário selecionará os produtos a serem comparados.
 
-<div class = "alert alert-warning">
-  <p>A comparação de produtos não é aplicável na página inicial do site.</p>
-</div>
+>⚠️ A comparação de produtos não é aplicável na página inicial do site.
 
 ## Configuração
 
diff --git a/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md b/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
index 48bd47390..0a6af45e1 100644
--- a/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
+++ b/docs/tutorials/pt/shared-information-between-a-marketplace-and-a-seller-on-vtex.md
@@ -23,9 +23,7 @@ Um marketplace hospedado na plataforma VTEX e um seller, seja um seller VTEX ou
 - [Marketplace e seller conectados](#marketplace-e-seller-conectados)
 - [Compartilhamento de emails de clientes](#compartilhamento-de-emails-de-clientes)
 
-<div class = "alert alert-info">
-Se quiser começar a vender seus produtos em outros marketplaces, utilize o <a href="https://help.vtex.com/pt/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM">Marketplaces e integrações</a>. Essa funcionalidade facilita a identificação e o contato entre marketplaces e sellers que operam no ecossistema VTEX.
-</div>
+>ℹ️ Se quiser começar a vender seus produtos em outros marketplaces, utilize o [Marketplaces e integrações](https://help.vtex.com/pt/tutorial/encontre-marketplaces-e-sellers-no-ecossistema-vtex--2bzC7tXlVgLEEjxo4ixcAM). Essa funcionalidade facilita a identificação e o contato entre marketplaces e sellers que operam no ecossistema VTEX.
 
 ## Conectar marketplace e seller
 
@@ -43,9 +41,7 @@ Além disso, para [adicionar o seller](https://help.vtex.com/pt/tutorial/configu
 
 É possível integrar o marketplace VTEX a seller VTEX, ou seller externo, tanto pelo Admin VTEX quanto por API. Nos dois casos, os dados compartilhados entre marketplace e seller serão os mesmos.
 
-<div class = "alert alert-info">
-Para mais informações sobre como conectar marketplace VTEX a seller VTEX, ou seller externo, pelo Admin VTEX, veja o artigo <a href="https://help.vtex.com/pt/tutorial/configurando-seller">Adicionar seller</a>. Para integração por API, utilize a chamada <a href="https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers">Configure Seller Account</a>. Em caso de seller externo, confira o <a href="https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide">guia de integração com seller externo</a>.
-</div>
+>ℹ️ Para mais informações sobre como conectar marketplace VTEX a seller VTEX, ou seller externo, pelo Admin VTEX, veja o artigo [Adicionar seller](https://help.vtex.com/pt/tutorial/configurando-seller). Para integração por API, utilize a chamada [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers). Em caso de seller externo, confira o [guia de integração com seller externo](https://developers.vtex.com/vtex-rest-api/docs/external-seller-integration-guide).
 
 ### Conectar marketplace VTEX a seller VTEX
 
@@ -84,9 +80,7 @@ O marketplace pode conceder ao seller acesso parcial aos emails da sua base de c
 - [Configure Seller Account](https://developers.vtex.com/docs/api-reference/marketplace-apis#post-/seller-register/pvt/sellers): permite configurar a conta do seller, seja ele seller VTEX ou externo.
 - [Update Seller by Seller ID](https://developers.vtex.com/docs/api-reference/marketplace-apis#patch-/seller-register/pvt/sellers/-sellerId-): permite atualizar os dados do seller, seja ele seller VTEX ou externo.
 
-<div class = "alert alert-info">
-Em pedidos realizados no marketplace, o email do cliente não é exibido para o seller. A relação do cliente é estabelecida com o marketplace e seria necessário o consentimento do cliente para o compartilhamento de seus dados.
-</div>
+>ℹ️ Em pedidos realizados no marketplace, o email do cliente não é exibido para o seller. A relação do cliente é estabelecida com o marketplace e seria necessário o consentimento do cliente para o compartilhamento de seus dados.
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/shipping-options-beta.md b/docs/tutorials/pt/shipping-options-beta.md
index faf28d80c..2cd6c1df1 100644
--- a/docs/tutorials/pt/shipping-options-beta.md
+++ b/docs/tutorials/pt/shipping-options-beta.md
@@ -33,9 +33,7 @@ O objetivo com as **Opções de envio**, no entanto, não é substituir [políti
 
 Com as **Opções de envio**, é feita uma separação entre o que é cobrado dos consumidores pelo envio do pedido e o custo do frete para o lojista, pois é possível configurar diferentes regras de precificação para a tarifa de envio. 
 
-<div class = "alert alert-info">
-Para que a escolha das transportadoras para envio do pedido seja feita corretamente, é necessário inserir nas planilhas de frete o custo real que as transportadoras cobram para realizar o envio.
-</div>
+>ℹ️ Para que a escolha das transportadoras para envio do pedido seja feita corretamente, é necessário inserir nas planilhas de frete o custo real que as transportadoras cobram para realizar o envio.
 
 As **Opções de envio** permitem ao lojista configurar a tarifa de envio a partir de:
 
@@ -57,9 +55,7 @@ Em cada opção de envio, o lojista registra um SLA (_Service Level Agreement_),
 
 O algoritmo da plataforma VTEX, o [Order Allocation Algorithm](https://help.vtex.com/pt/tutorial/order-allocation-algorithm-beta--1zLCAyEdnVe3EsE9Kz88xA), analisa as combinações de lojas e centros de distribuição que atendem cada uma das opções de envio e busca selecionar aquelas que apresentam o menor custo de envio. No exemplo, o resultado é uma combinação de menor custo de envio no mesmo dia, e outra combinação de menor custo de envio em até 5 dias úteis.
 
-<div class = "alert alert-info">
-Com as <b>Opções de envio</b>, existe a garantia de que uma opção de envio disponível para a localidade sempre será apresentada ao consumidor, o que não ocorria antes. A única exceção é se não houver seller e política de envio que atendam às condições de uma shipping option. Neste caso, nenhuma shipping option aparecerá para o consumidor no checkout.
-</div>
+>ℹ️ Com as **Opções de envio**, existe a garantia de que uma opção de envio disponível para a localidade sempre será apresentada ao consumidor, o que não ocorria antes. A única exceção é se não houver seller e política de envio que atendam às condições de uma shipping option. Neste caso, nenhuma shipping option aparecerá para o consumidor no checkout.
 
 ## Ações e configurações
 
diff --git a/docs/tutorials/pt/shipping-simulation.md b/docs/tutorials/pt/shipping-simulation.md
index 31f248ae9..78be01359 100644
--- a/docs/tutorials/pt/shipping-simulation.md
+++ b/docs/tutorials/pt/shipping-simulation.md
@@ -61,9 +61,7 @@ Se desejar, pode preencher o box `Simular itens individualmente`.
 
  10. Clique no botão `Simular Frete`.
 
-<div class = "alert alert-info">
-No resultado da simulação, as medidas dos itens aparecem em centímetros e gramas, mas o valor real considerado no Checkout são as unidades de medida cadastradas nos <a href="https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">campos de cadastro do produto</a> e do SKU.
-</div>
+>ℹ️ No resultado da simulação, as medidas dos itens aparecem em centímetros e gramas, mas o valor real considerado no Checkout são as unidades de medida cadastradas nos [campos de cadastro do produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) e do SKU.
 
 ## Detalhes da Simulação
 
diff --git a/docs/tutorials/pt/shopee-integration.md b/docs/tutorials/pt/shopee-integration.md
index d80f7a6bd..19edf8fc9 100644
--- a/docs/tutorials/pt/shopee-integration.md
+++ b/docs/tutorials/pt/shopee-integration.md
@@ -33,9 +33,7 @@ Depois de criar sua conta na Shopee, você estará apto(a) para realizar as segu
 - [Gerenciar produtos](#gerenciar-produtos)
 - [Gerenciamento de pedidos da Shopee na plataforma VTEX](#gerenciamento-de-pedidos-da-shopee-na-plataforma-vtex)
 
-<div class = "alert alert-info">
-A integração com a Shopee não consegue integrar pedidos de produtos cujo os anúncios já existem na Shopee. A partir da ativação da integração, os pedidos que serão fechados na Shopee, serão integrados na VTEX.
-</div>
+>ℹ️ A integração com a Shopee não consegue integrar pedidos de produtos cujo os anúncios já existem na Shopee. A partir da ativação da integração, os pedidos que serão fechados na Shopee, serão integrados na VTEX.
 
 ## Configurar política comercial para Shopee
 
@@ -52,9 +50,7 @@ Só será necessário [configurar uma política comercial para marketplace](http
 
 Para [contratar políticas comerciais adicionais](https://help.vtex.com/pt/tutorial/contratacao-de-politica-comercial-adicional--61vuFOw4yGh6nwSmkLJL1X), basta psolicitar via ticket em nosso [Suporte](https://help.vtex.com/pt/support) selecionando a opção **Comercial** e o tipo de solicitação `Criação de Política Comercial`.
 
-<div class = "alert alert-info">
-A integração com a Shopee não é um <a href="https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro">conector certificado (parceiro)</a> da VTEX, fazendo que a contratação de política comercial adicional não seja isenta de taxas.
-</div>
+>ℹ️ A integração com a Shopee não é um [conector certificado (parceiro)](https://help.vtex.com/pt/tutorial/estrategias-de-marketplace-na-vtex--tutorials_402#integrado-a-conector-certificado-parceiro) da VTEX, fazendo que a contratação de política comercial adicional não seja isenta de taxas.
 
 ## Definir Doca e Estoque
 
@@ -184,9 +180,7 @@ Para enviar os seus produtos para a Shopee, você deverá:
 1. [Mapear as categorias dos produtos.](#mapear-categorias)
 2. [Mapear os atributos dos produtos.](#mapear-atributos)
 
-<div class = "alert alert-info">
-Seus produtos precisam ter o <a href="https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb">Estoque</a> e <a href="https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP">Preço</a> configurados antes de enviá-los ao marketplace.
-</div>
+>ℹ️ Seus produtos precisam ter o [Estoque](https://help.vtex.com/pt/tutorial/estoque--6oIxvsVDTtGpO7y6zwhGpb) e [Preço](https://help.vtex.com/pt/tracks/precos-101--6f8pwCns3PJHqMvQSugNfP) configurados antes de enviá-los ao marketplace.
 
 ### Mapear categorias
 
diff --git a/docs/tutorials/pt/sku-bindings.md b/docs/tutorials/pt/sku-bindings.md
index 03f6dea7d..38a86fe22 100644
--- a/docs/tutorials/pt/sku-bindings.md
+++ b/docs/tutorials/pt/sku-bindings.md
@@ -21,9 +21,7 @@ Quando o seller envia seus produtos para o marketplace VTEX, o marketplace [cata
 
 Após a catalogação, que o marketplace pode realizar pela página **SKUs Recebidos** ou utilizando o [VTEX Matcher](https://help.vtex.com/pt/tutorial/entendendo-a-pontuacao-do-vtex-matcher--tutorials_424), os vínculos entre os SKUs do seller e os SKUs do marketplace aparecem na página **Vínculos de SKU**. De forma automática, os vínculos possuem o status _Vinculado_.
 
-<div class = "alert alert-info">
-Por padrão, para <a href="https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">sellers white label</a> não existe essa relação de vínculo entre os seus SKUs e os SKUs do marketplace.
-</div>
+>ℹ️ Por padrão, para [sellers white label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) não existe essa relação de vínculo entre os seus SKUs e os SKUs do marketplace.
 
 A página **Vínculos de SKU** permite ao marketplace acompanhar e gerenciar a relação de vínculo entre os SKUs do seller e do marketplace. Para acessar a página, no Admin VTEX vá em **Marketplace > Sellers > Vínculos de SKU**. A seguinte interface vai aparecer:
 
@@ -65,17 +63,13 @@ Também é possível pesquisar na listagem filtrando por status de vinculação.
 
 Para retornar à listagem com todos os status de vínculo, clique no botão `Limpar todos`. Este botão só cancela o filtro de status, e não termos pesquisados nas caixas de busca.
 
-<div class = "alert alert-info">
-Caso não haja um resultado para a pesquisa, verifique a ortografia utilizada na busca ou a combinação de filtros utilizada.
-</div> 
+>ℹ️ Caso não haja um resultado para a pesquisa, verifique a ortografia utilizada na busca ou a combinação de filtros utilizada. 
 
 ## Desvincular SKU
 
 Para desfazer o vínculo entre SKUs, clique sobre o _switch_ <i class="fas fa-toggle-on"></i> e confirme a opção `Desfazer o vínculo do SKU`.
 
-<div class = "alert alert-info">
-Ao desvincular o SKU do seller, o SKU deixa de receber atualizações de preço e estoque e se torna indisponível no catálogo do marketplace. O SKU pode ser revinculado a qualquer momento, não sendo para isso necessário catalogar o SKU do seller novamente.
-</div>
+>ℹ️ Ao desvincular o SKU do seller, o SKU deixa de receber atualizações de preço e estoque e se torna indisponível no catálogo do marketplace. O SKU pode ser revinculado a qualquer momento, não sendo para isso necessário catalogar o SKU do seller novamente.
 
 Se desejar restabelecer o vínculo entre o SKU do seller e o SKU do marketplace, ative o _switch_ <i class="fas fa-toggle-on"></i> novamente, clicando sobre ele.
 
@@ -109,9 +103,7 @@ Para exportar a lista de vínculos de SKUs em formato XLSX, realize os seguintes
 
 A planilha gerada será enviada para o email do usuário logado. O tempo da exportação vai depender de questões de processamento da plataforma VTEX e o volume do arquivo.
 
-<div class = "alert alert-info">
-O conteúdo exportado é referente à listagem de vínculos de SKUs no momento da exportação. Se uma busca ou filtro estiver ativo, somente os vínculos selecionados serão exportados.
-</div>
+>ℹ️ O conteúdo exportado é referente à listagem de vínculos de SKUs no momento da exportação. Se uma busca ou filtro estiver ativo, somente os vínculos selecionados serão exportados.
 
 ## Saiba mais
 
diff --git a/docs/tutorials/pt/sku-registration-fields.md b/docs/tutorials/pt/sku-registration-fields.md
index e670e8fcd..483661d0f 100644
--- a/docs/tutorials/pt/sku-registration-fields.md
+++ b/docs/tutorials/pt/sku-registration-fields.md
@@ -31,9 +31,7 @@ __Código de Referência:__ código de referência único criado para ajudar na
 
 __Peso para Frete:__ calculado para frete. Deve ser cadastrado com valor maior do que zero para o funcionamento correto do <a href="https://help.vtex.com/pt/tutorial/como-e-feito-o-rateio-de-frete--frequentlyAskedQuestions_155">rateio de frete</a>.
 
-<div class = "alert alert-info">
-<p>O módulo de <strong>Envio/Estoque e Entrega</strong> não leva em consideração unidades de medida nos campos abaixo. Basta ser consistente com o que é cadastrado nos <a href="https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke">campos de cadastro do produto</a> e do SKU.</p>
-</div>
+>ℹ️ O módulo de **Envio/Estoque e Entrega** não leva em consideração unidades de medida nos campos abaixo. Basta ser consistente com o que é cadastrado nos [campos de cadastro do produto](https://help.vtex.com/pt/tutorial/campos-de-cadastro-de-produto--4dYXWIK3zyS8IceKkQseke) e do SKU.
 
 __Altura para Frete:__ calculada para frete.
 
diff --git a/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md b/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md
index 831ff0081..84746a042 100644
--- a/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md
+++ b/docs/tutorials/pt/smartcheckout-customer-information-automatic-fill-in.md
@@ -40,9 +40,7 @@ Os dados do cliente utilizados no Checkout têm origem nas informações cadastr
    - street
    - receiverName
 
-<div class = "alert alert-warning">
-Caso um ou mais dados não estiverem preenchidos corretamente no Master Data, o SmartCheckout não irá trazer nenhuma informação do cliente de forma automática na tela do Checkout. Nesta situação, será necessário que o cliente preencha todos os dados de identificação manualmente em cada compra a ser realizada. 
-</div>
+>⚠️ Caso um ou mais dados não estiverem preenchidos corretamente no Master Data, o SmartCheckout não irá trazer nenhuma informação do cliente de forma automática na tela do Checkout. Nesta situação, será necessário que o cliente preencha todos os dados de identificação manualmente em cada compra a ser realizada.
 
 ## Procedimento de compra com o SmartCheckout
 
@@ -53,19 +51,16 @@ O fluxo de preenchimento automático de dados do cliente no Checkout ocorre da s
 3. O Checkout verifica se o email inserido pertence a algum cliente cadastrado na loja. 
 4. Caso seja localizado o email, o checkout preenche automaticamente os campos de identificação do cliente com os dados recebidos do Master Data.
 
-<div class = "alert alert-warning">
-Para a proteção dos dados do cliente, as informações de identificação serão exibidas apenas parcialmente na tela do Checkout (parte dos dados são mascarados conforme padrão <a href="https://help.vtex.com/pt/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E">PCI-DSS</a> de segurança em pagamentos). Este procedimento permite que o cliente possa identificar se os seus dados atuais estão corretos e também selecionar diferentes endereços cadastrados para a entrega, caso necessário.
-</div>
+>⚠️ Para a proteção dos dados do cliente, as informações de identificação serão exibidas apenas parcialmente na tela do Checkout (parte dos dados são mascarados conforme padrão [PCI-DSS](https://help.vtex.com/pt/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E) de segurança em pagamentos). Este procedimento permite que o cliente possa identificar se os seus dados atuais estão corretos e também selecionar diferentes endereços cadastrados para a entrega, caso necessário.
 <ul>
 5. O cliente seleciona os meios de entrega e pagamento, e conclui o pedido de compra.
 </ul>
-<div class = "alert alert-warning">
-Caso o cartão de crédito ou débito seja selecionado como meio de pagamento, os seguintes critérios adicionais de segurança são adotados:
-  <ul>
-    <li>Solicitação do CVV (Card Verification Value) para a validação final e conclusão do pedido de compra.</li>
-    <li>Impossibilidade de realizar compras com cartões utilizando um endereço diferente daquele cadastrado no perfil do cliente.</li>
-  </ul>    
-</div>
+>⚠️ Caso o cartão de crédito ou débito seja selecionado como meio de pagamento, os seguintes critérios adicionais de segurança são adotados:
+>
+> * Solicitação do CVV (Card Verification Value) para a validação final e conclusão do pedido de compra.
+>
+> * Impossibilidade de realizar compras com cartões utilizando um endereço diferente daquele cadastrado no perfil do cliente.
+>   
 
 Qualquer tipo de alteração nos dados cadastrados, como endereço e telefone, será permitida somente após o cliente realizar a sua [autenticação na loja](https://help.vtex.com/pt/tutorial/como-meu-cliente-pode-fazer-login-na-minha-loja--3FCNpwbpZe0U4auiI4CC0C#). 
 
diff --git a/docs/tutorials/pt/smartcheckout-security.md b/docs/tutorials/pt/smartcheckout-security.md
index adb858a38..2287edfdc 100644
--- a/docs/tutorials/pt/smartcheckout-security.md
+++ b/docs/tutorials/pt/smartcheckout-security.md
@@ -35,7 +35,6 @@ Isso significa que, ao tentar realizar uma compra com um email de terceiros, um
 
 Além disso, a forma que as informações aparecem mascaradas no checkout é certificada pelo padrão [PCI-DSS](https://help.vtex.com/pt/tutorial/what-is-the-pci-ssc--4jo3Vkox3amSO2w4qIWa0E#) de segurança em pagamentos. Segundo este padrão, os últimos dígitos de um cartão não precisam ser ocultados. A forma com que a informação é exibida é suficiente apenas para o reconhecimento do meio de pagamento, mas insuficiente para realização de compras.
 
-<div class = "alert alert-info">
-<p>Com o VTEX Smartcheckout™ a segurança vem em primeiro lugar. Sempre que um email é reconhecido, todos os dados são preenchidos de uma maneira que garante que somente o proprietário do email reconheça suas informações.</p><p>Ao acessar a loja pelo domínio restrito <code>myvtex.com</code> operadores de loja podem ver os dados não mascarados no SmartCheckout a fim de realizar testes. Acesso por este domínio é restrito a administradores de loja com o devido nível de acesso, com as devidas credenciais.</p>
-</div>
+>ℹ️ Com o VTEX Smartcheckout™ a segurança vem em primeiro lugar. Sempre que um email é reconhecido, todos os dados são preenchidos de uma maneira que garante que somente o proprietário do email reconheça suas informações.
+> Ao acessar a loja pelo domínio restrito `myvtex.com` operadores de loja podem ver os dados não mascarados no SmartCheckout a fim de realizar testes. Acesso por este domínio é restrito a administradores de loja com o devido nível de acesso, com as devidas credenciais.
 
diff --git a/docs/tutorials/pt/special-conditions.md b/docs/tutorials/pt/special-conditions.md
index e3e024a30..0266c4ee3 100644
--- a/docs/tutorials/pt/special-conditions.md
+++ b/docs/tutorials/pt/special-conditions.md
@@ -158,6 +158,4 @@ Veja a seguir como configurar o período na condição de pagamento:
 
 Imagine que sua loja normalmente oferece um parcelamento em até 6x sem juros, mas quer aproveitar as vendas do final de ano para oferecer um parcelamento em até 12x sem juros. Nesse caso, bastaria seguir os passos acima e cadastrar o período para a condição de pagamento, deixar de ser aplicada em 01 de janeiro do ano seguinte, por exemplo.
 
-<div class = "alert alert-warning">
-  <p>As condições de pagamento possuem um cache de até 10 minutos no Smart Checkout. Logo, qualquer mudança nas Condições de Pagamento do módulo <strong>Pagamentos</strong> pode levar até 10 minutos para entrar em produção no Smart Checkout.</p>
-</div>
+>⚠️ As condições de pagamento possuem um cache de até 10 minutos no Smart Checkout. Logo, qualquer mudança nas Condições de Pagamento do módulo **Pagamentos** pode levar até 10 minutos para entrar em produção no Smart Checkout.
diff --git a/docs/tutorials/pt/store-overview-beta.md b/docs/tutorials/pt/store-overview-beta.md
index 0cfa623e9..82a6f27f3 100644
--- a/docs/tutorials/pt/store-overview-beta.md
+++ b/docs/tutorials/pt/store-overview-beta.md
@@ -36,9 +36,7 @@ Neste artigo, apresentamos as principais seções e ações presentes na página
 
 As métricas da página incluem dados sobre pedidos e navegação, que são captados de sistemas diferentes.
 
-<div class ="alert alert-warning">
-É provável que existam diferenças entre as métricas de receita e ticket médio registradas no OMS e no Performance de Vendas, por exemplo. Isso ocorre porque o Performance de Vendas considera o valor dos itens, enquanto o OMS também considera os descontos, frete, taxas e promoções sobre o pedido - o que pode aumentar ou diminuir seu valor final. 
-</div>
+>⚠️ É provável que existam diferenças entre as métricas de receita e ticket médio registradas no OMS e no Performance de Vendas, por exemplo. Isso ocorre porque o Performance de Vendas considera o valor dos itens, enquanto o OMS também considera os descontos, frete, taxas e promoções sobre o pedido - o que pode aumentar ou diminuir seu valor final.
 
 * **Pedidos e receitas:** os dados sobre pedidos e receitas vêm do OMS, ou Sistema de Gerenciamento de Pedidos da VTEX e incluem pedidos realizados em todos os seus canais de venda.
 * **Sessões:** os dados de navegação vêm do sistema interno da plataforma que capta sessões dos usuários no storefront de lojas VTEX. Sessões são representadas pelo conjunto de visualizações das páginas acessadas por um mesmo usuário  ao navegar em seu ecommerce, desconsiderando marketplaces, apps, Sales App e qualquer outro canal de venda.
diff --git a/docs/tutorials/pt/telesales-features.md b/docs/tutorials/pt/telesales-features.md
index 36adff0cb..6511e90f2 100644
--- a/docs/tutorials/pt/telesales-features.md
+++ b/docs/tutorials/pt/telesales-features.md
@@ -36,9 +36,7 @@ A Toolbar de televendas é uma barra superior exibida no site da loja para usuá
 
 Para saber como utilizar esse recurso, confira o tutorial [Toolbar de Televendas](https://help.vtex.com/pt/tutorial/usando-e-customizando-toolbar-de-televendas--tutorials_5500).
 
-<div class = "alert alert-info">
-Um caso de uso do televendas é  importar pedidos de outras plataformas para o módulo Pedidos da VTEX. Para isso, você pode associar uma <a href="https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE">política comercial</a> específica com o pagamento por <a href="https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ">promissória</a> (método de pagamento aprovado imediatamente e manualmente pelo próprio operador).
-</div> 
+>ℹ️ Um caso de uso do televendas é  importar pedidos de outras plataformas para o módulo Pedidos da VTEX. Para isso, você pode associar uma [política comercial](https://help.vtex.com/pt/tutorial/o-que-e-uma-politica-comercial--563tbcL0TYKEKeOY4IAgAE) específica com o pagamento por [promissória](https://help.vtex.com/pt/tutorial/configurar-pagamentos-com-promissoria--5pW7avTwtyQcMu4uiW8quQ) (método de pagamento aprovado imediatamente e manualmente pelo próprio operador). 
 
 ### Minha Conta
 
diff --git a/docs/tutorials/pt/transactional-emails-for-subscription-orders.md b/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
index da55baf25..e0aa8e52c 100644
--- a/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
+++ b/docs/tutorials/pt/transactional-emails-for-subscription-orders.md
@@ -28,9 +28,7 @@ Também é possível criar seu próprio template de e-mail. Entenda melhor como
 
 ## Como seu cliente acompanha seus Pedidos de Assinatura
 
-<div class = "alert alert-info">
-Em <a href="https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>, os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
-</div>
+>ℹ️ Em [Minha Conta](https://help.vtex.com/es/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh), os clientes conseguem acessar somente os seus pedidos criados nos últimos dois anos.
 
 Cada ação, ocorrida dentro do fluxo de pedidos de Assinatura, contém um gatilho que dispara um e-mail notificando o seu cliente. Após a ativação da Assinatura, seu cliente receberá e-mails com detalhes do estado de cada pedido da assinatura toda vez que realizar uma ação. 
 
diff --git a/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md b/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
index d6e886c33..b724d4127 100644
--- a/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
+++ b/docs/tutorials/pt/troubleshooting-errors-in-subscription-orders.md
@@ -15,9 +15,7 @@ legacySlug: como-solucionar-pedidos-de-assinatura-com-erros
 subcategory: 1rA9wuuskW3PpjvMrhatAM
 ---
 
-<div class = "alert alert-info">
-É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo <a href="https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh">Minha Conta</a>.
-</div>
+>ℹ️ É possível acessar informações somente de pedidos criados nos últimos dois anos, sendo o mesmo período válido para clientes acessarem pedidos pelo [Minha Conta](https://help.vtex.com/pt/tutorial/how-my-account-works--2BQ3GiqhqGJTXsWVuio3Xh).
 
 É possível identificar e gerenciar erros em pedidos de assinaturas através do módulo de **Assinaturas** > **Dashboards** > **Pedidos de Assinatura** no Admin.
 
diff --git a/docs/tutorials/pt/troubleshooting-price-divergence-errors-in-marketplace-orders.md b/docs/tutorials/pt/troubleshooting-price-divergence-errors-in-marketplace-orders.md
index a13c87639..3e364205b 100644
--- a/docs/tutorials/pt/troubleshooting-price-divergence-errors-in-marketplace-orders.md
+++ b/docs/tutorials/pt/troubleshooting-price-divergence-errors-in-marketplace-orders.md
@@ -23,9 +23,7 @@ Quando o preço definido por um seller é diferente do preço oferecido pelo mar
 
 Para aderir ao fluxo de Autorização de pedidos, você precisa [configurar uma regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe). Somente usuários com [perfil de acesso](https://help.vtex.com/pt/tutorial/perfis-de-acesso--7HKK5Uau2H6wxE1rH5oRbc) Admin Super (_Owner_) ou OMS Full podem fazer isso.
 
-<div class = "alert alert-info">
-Uma vez que você <a href="https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe">configure a regra de Divergência de valores</a>, ela passa a valer para todos os marketplaces nos quais você seja um seller.
-</div>
+>ℹ️ Uma vez que você [configure a regra de Divergência de valores](https://help.vtex.com/pt/tutorial/configuracao-da-regra-de-divergencia-de-valores--awAKP0sS5J8jgLs2g7pPe), ela passa a valer para todos os marketplaces nos quais você seja um seller.
 
 Para marketplaces VTEX, marketplaces externos e conectores certificados (parceiros), enquanto a regra de Divergência de valores não for criada, pedidos com erro de divergência de preço são aprovados automaticamente.
 
diff --git a/docs/tutorials/pt/understanding-b2b-orders.md b/docs/tutorials/pt/understanding-b2b-orders.md
index 71f32105a..933fb2ae1 100644
--- a/docs/tutorials/pt/understanding-b2b-orders.md
+++ b/docs/tutorials/pt/understanding-b2b-orders.md
@@ -27,10 +27,9 @@ Essa experiência de autosserviço é possível graças a uma integração via A
 - **ERP order number:** número identificador do pedido realizado por meio do ERP da loja.
 - **My order:** número identificador associado ao cliente que efetuou a compra.
 
-<div class = "alert alert-warning">
-  <p>Esta app só está disponível para lojas desenvolvidas usando 
-    <a href="https://vtex.com/br-pt/store-framework/">VTEX IO</a>.</p><p>Antes de prosseguir, é preciso <a href = "https://developers.vtex.com/vtex-developer-docs/docs/querying-b2b-order-statuses">instalar e configurar Pedidos B2B</a> na sua loja.</p>
-</div>
+>⚠️ Esta app só está disponível para lojas desenvolvidas usando 
+>     [VTEX IO](https://vtex.com/br-pt/store-framework/).
+> Antes de prosseguir, é preciso <a href = "https://developers.vtex.com/vtex-developer-docs/docs/querying-b2b-order-statuses">instalar e configurar Pedidos B2B</a> na sua loja.
 
 ## Contexto
 
diff --git a/docs/tutorials/pt/vtex-ad-network-beta.md b/docs/tutorials/pt/vtex-ad-network-beta.md
index 4af94c14b..b455e8f27 100644
--- a/docs/tutorials/pt/vtex-ad-network-beta.md
+++ b/docs/tutorials/pt/vtex-ad-network-beta.md
@@ -15,9 +15,7 @@ legacySlug: vtex-ad-network-beta
 subcategory: 2AksvvAtAsbAfE7HsBIVDU
 ---
 
-<div class = "alert alert-info">
-<p>O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ O VTEX Ad Network está em fase Beta, o que significa que estamos trabalhando para aprimorá-lo. Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 O **VTEX Ad Network** conecta lojas VTEX a marcas interessadas em anunciar seus produtos. Com esta conexão, anunciantes e lojas VTEX podem potencializar seu negócio:
 
diff --git a/docs/tutorials/pt/vtex-admin-start-here.md b/docs/tutorials/pt/vtex-admin-start-here.md
index e11386e75..20e284ccb 100644
--- a/docs/tutorials/pt/vtex-admin-start-here.md
+++ b/docs/tutorials/pt/vtex-admin-start-here.md
@@ -90,9 +90,7 @@ Tipo de feedback (selecione um ou mais campos):
 
 **Uma captura de tela nos ajudará a entender melhor seu feedback (opcional):** campo opcional para adicionar capturas de tela ou documentos que possam nos auxiliar na compreensão do seu feedback.
 
-<div class = "alert alert-info">
-Este processo de envio de feedback não deve ser utilizado para criar um ticket ou solicitação de suporte técnico na VTEX.
-</div>
+>ℹ️ Este processo de envio de feedback não deve ser utilizado para criar um ticket ou solicitação de suporte técnico na VTEX.
 
 ### Configurações da conta e do usuário
 
diff --git a/docs/tutorials/pt/vtex-do-interface.md b/docs/tutorials/pt/vtex-do-interface.md
index a3f777957..a734a1abc 100644
--- a/docs/tutorials/pt/vtex-do-interface.md
+++ b/docs/tutorials/pt/vtex-do-interface.md
@@ -19,9 +19,7 @@ O VTEX DO é um gerenciador de tarefas criadas automaticamente pelo Admin VTEX,
 
 ![VTEX Do overview PT](https://images.ctfassets.net/alneenqid6w5/4FzyUh5uqhzXKfbw9MJXsQ/76b1688496144fe90a8fc65f94a62bef/VTEX_Do_overview_PT.gif)
 
-<div class = "alert alert-info">
-Somente usuários com o perfil de acesso <a href = "https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> podem realizar tarefas pelo VTEX DO. 
-</div>
+>ℹ️ Somente usuários com o perfil de acesso <a href = "https://help.vtex.com/pt/tutorial/roles--7HKK5Uau2H6wxE1rH5oRbc#oms-full-access">OMS - Full Access</a> podem realizar tarefas pelo VTEX DO.
 
 As tarefas estão listadas em duas abas:
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md b/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
index 5cd44b4a8..372a3fdc0 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-fulfillment.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-fulfillment
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
 [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU) é uma solução para otimizar os processos de fulfillment das lojas, otimizando a coleta e o empacotamento dos pedidos, além da entrega last mile. A solução é composta pelas páginas de [Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr) e **VTEX Pick and Pack Fulfillment**, e aparece em seu Admin VTEX em **Apps**.
 
@@ -349,9 +347,7 @@ Você pode combinar vários filtros para filtrar as informações que deseja ver
 * Cidade
 * Seller
 
-<div class = "alert alert-info">
-O filtro <b>Seller</b> está disponível apenas para contas que operam como marketplace. <a href="https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa">Sellers white label</a> não têm essa opção de filtro em <b>Insights</b>.
-</div>
+>ℹ️ O filtro **Seller** está disponível apenas para contas que operam como marketplace. [Sellers white label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) não têm essa opção de filtro em **Insights**.
 
 Além da métrica de **total de pedidos**, há uma sequência de métricas para obter dados sobre _meios de pagamento_ e pedidos:
 
@@ -370,9 +366,7 @@ Abaixo do **total de pedidos**, você encontrará métricas sobre o número de p
 
 Na aba **Operação**, você verá o **fluxo de pedidos** de Coleta e empacotamento, que mostrará a quantidade total de pedidos distribuídos por dia nos últimos sete dias. Quanto mais escuro for o tom de azul, mais pedidos, quanto mais claro, menos.
 
-<div class = "alert alert-info">
-O fluxo de <b>Coleta e empacotamento</b> é calculado considerando todos os pedidos dos últimos 7 dias e os distribui em horas, de 0 a 23. Mesmo se você mudar o período para 15 dias, por exemplo, a visualização permanecerá fixa considerando 7 dias.
-</div>
+>ℹ️ O fluxo de **Coleta e empacotamento** é calculado considerando todos os pedidos dos últimos 7 dias e os distribui em horas, de 0 a 23. Mesmo se você mudar o período para 15 dias, por exemplo, a visualização permanecerá fixa considerando 7 dias.
 
 Abaixo do **fluxo de pedidos**, há uma métrica com pedidos filtrados por entregador. Você irá ver informações sobre:
 
@@ -463,9 +457,7 @@ Para criar um pacote, faça o seguinte:
 2. Preencha o nome que identificará o pacote.
 3. Preencha as medidas do pacote: altura, largura e comprimento, usando apenas números. 
 
-  <div class = "alert alert-info">
-A unidade de medida é aquela configurada na aba <a href="https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#configuracoes-gerais">Geral</a>, em <b>Unidades de medida</b>.
-</div>
+  >ℹ️ A unidade de medida é aquela configurada na aba [Geral](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA#configuracoes-gerais), em **Unidades de medida**.
 
 4. Clique em `Adicionar`.
 
@@ -510,9 +502,7 @@ Ao terminar de definir as configurações de impressão, clique em `Salvar`.
 
 Nesta aba, você pode configurar um webhook para ser notificado sobre alterações de status dos pedidos e [obter informações](https://developers.vtex.com/docs/guides/vtex-pick-and-pack-get-order-status-and-information-api) sobre um pedido específico.
 
-<div class = "alert alert-info">
-Para mais informações, veja nossa documentação do <a href="https://developers.vtex.com/docs/guides/vtex-pick-and-pack-get-order-status-and-information-api#webhook">VTEX Pick and Pack para desenvolvedores</a>.
-</div>
+>ℹ️ Para mais informações, veja nossa documentação do [VTEX Pick and Pack para desenvolvedores](https://developers.vtex.com/docs/guides/vtex-pick-and-pack-get-order-status-and-information-api#webhook).
 
 ## Usuários
 
@@ -563,9 +553,7 @@ Para criar um novo _entregador_, siga os passos abaixo:
     * **Lojas:** selecione o ambiente ao qual o entregador será associado. Cada ambiente pode ter múltiplos [sellers white label](https://help.vtex.com/pt/tutorial/seller-white-label--5orlGHyDHGAYciQ64oEgKa) associados a ele.
     * **Categorias:** selecione até quatro categorias relacionadas aos produtos que o entregador irá coletar.
 
-  <div class = "alert alert-info">
-As categorias relacionadas ao entregador otimizam o algoritmo ao determinar qual entregador receberá o pedido. Mas essa não é uma limitação: qualquer entregador pode ser alocado para serviços de todas as categorias.
-</div>
+  >ℹ️ As categorias relacionadas ao entregador otimizam o algoritmo ao determinar qual entregador receberá o pedido. Mas essa não é uma limitação: qualquer entregador pode ser alocado para serviços de todas as categorias.
 
 4. Clique em `Salvar usuário`.
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-insights.md b/docs/tutorials/pt/vtex-pick-and-pack-insights.md
index fb6a1bd3c..a41c7cd25 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-insights.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-insights.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-insights
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
 **Insights** é uma página do Admin VTEX que exibe informações sobre o desempenho da sua loja em relação ao VTEX Pick and Pack.
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md b/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md
index fde798f50..a6e567aa6 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-last-mile.md
@@ -17,7 +17,5 @@ subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 
 <div class="alert alert-warning" role="alert">Conteúdo em tradução.</div>
 
-<div class = "alert alert-info">
-Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
index 4c488b832..8f1bbc433 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-mobile.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-mobile
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-<p>Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o <a href="https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ">Suporte Comercial</a>. É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o <a href="https://vtex.com/br-pt/contato/">formulário de contato</a>.</p>
-</div>
+>ℹ️ Se já é cliente da VTEX e deseja adotar essa funcionalidade em seu negócio, entre em contato com o [Suporte Comercial](https://help.vtex.com/pt/tracks/support-at-vtex--4AXsGdGHqExp9ZkiNq9eMy/3KQWGgkPOwbFTPfBxL7YwZ). É possível que taxas adicionais se apliquem. Se ainda não é cliente, mas tem interesse nesta solução, preencha o [formulário de contato](https://vtex.com/br-pt/contato/).
 
 O aplicativo móvel do [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack-fulfillment--1zGUEItEEVsal6cuBEBNcA) auxilia o separador - profissional responsável por selecionar e empacotar itens na instalação - no manuseio de pedidos, abrangendo desde a separação dos itens até o envio. Assim, o fluxo de separação e entrega dos pedidos da loja torna-se mais organizado e fluido.
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-orders.md b/docs/tutorials/pt/vtex-pick-and-pack-orders.md
index d65726123..3e2153dd8 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-orders.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-orders.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-pedidos
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
 **Pedidos** é uma página do Admin VTEX que exibe as informações dos pedidos realizados e gerenciados pelo [VTEX Pick and Pack](https://help.vtex.com/pt/tutorial/vtex-pick-and-pack--1OOops3WrUyz7e0bnhkfXU).  
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-settings.md b/docs/tutorials/pt/vtex-pick-and-pack-settings.md
index efd539978..a5246d121 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-settings.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-settings.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-configuracoes
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
 **Configurações** é uma página do Admin VTEX que permite selecionar as configurações desejadas para o funcionamento do VTEX Pick and Pack na sua loja. As configurações estão distribuídas nas seguintes abas:
 
@@ -40,9 +38,7 @@ Nesta aba, você encontrará as configurações relacionadas à etapa de separa
 
 Nesta seção, você pode definir o tipo de estratégia de separação que deseja para os seus separadores.
 
-<div class = "alert alert-info">
-  Apenas a estratégia <strong>Separação por ondas</strong> está disponível no momento.
-</div>
+>ℹ️ Apenas a estratégia **Separação por ondas** está disponível no momento.
 
 ### Alterações no pedido
 
@@ -252,9 +248,7 @@ Você pode adicionar SKU IDs e EANs dos seus produtos em massa, por meio de um a
 
 Você também pode indexar o catálogo para atualizar a listagem de produtos. Para isso, clique em `Indexar catálogo` e depois em `Continuar`.
 
-<div class = "alert alert-danger">
-A indexação do catálogo irá apagar e recriar todo o conteúdo dele, o que significa que você poderá perder todos os códigos EAN e SKU personalizados.
-</div>
+>❗ A indexação do catálogo irá apagar e recriar todo o conteúdo dele, o que significa que você poderá perder todos os códigos EAN e SKU personalizados.
 
 ## Instalações
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md b/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
index 28f33e8f0..4ac8aacd2 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack-worksheets.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack-ordens-de-servico
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Essa funcionalidade está na fase Beta fechado, o que significa que somente clientes selecionados têm acesso a ela no momento. Caso tenha interesse em implementá-la futuramente, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
 **Ordens de serviço** é uma página do Admin VTEX que gerencia, em tempo real, as ordens de serviço utilizadas pelos separadores para agrupar e separar os itens de cada pedido. O separador pode agrupar quantos pedidos desejar em cada ordem de serviço. 
 
diff --git a/docs/tutorials/pt/vtex-pick-and-pack.md b/docs/tutorials/pt/vtex-pick-and-pack.md
index fbf6cf4ac..20939e9cd 100644
--- a/docs/tutorials/pt/vtex-pick-and-pack.md
+++ b/docs/tutorials/pt/vtex-pick-and-pack.md
@@ -15,9 +15,7 @@ legacySlug: vtex-pick-and-pack
 subcategory: 7Kllu6CmeLNV3tYXlCFvOt
 ---
 
-<div class = "alert alert-info">
-Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso <a href="https://vtex.com/br-pt/contato/">formulário</a> apontando no campo <code>Comentários</code> o nome do produto desejado.
-</div>
+>ℹ️ Caso tenha interesse em adotar essa funcionalidade no seu negócio, preencha nosso [formulário](https://vtex.com/br-pt/contato/) apontando no campo `Comentários` o nome do produto desejado.
 
 **VTEX Pick and Pack** é a solução que permite aos comerciantes gerenciar a coleta, o empacotamento e a entrega de pedidos a partir de lojas físicas e estoques para endereços de clientes ou [pontos de retirada](https://help.vtex.com/pt/tutorial/pickup-points--2fljn6wLjn8M4lJHA6HP3R). Todo o gerenciamento é feito em um só lugar, gerando maior controle e visibilidade para os comerciantes em todo o processo de fulfillment.
 
@@ -42,7 +40,5 @@ O **VTEX Pick and Pack** é uma solução composta por:
 * **[Last Mile](https://help.vtex.com/en/tutorial/vtex-pick-and-pack-last-mile--HN7WKV0xoq2ssVjsJlfzr):** aplicativo do Admin para o operador da loja instruir os entregadores sobre a coleta e entrega dos pedidos no endereço dos clientes ou nos pontos de retirada. Inclui a otimização de rotas e comprovação de coleta e entrega, ou seja, o entregador pode fazer o upload de uma assinatura do cliente, uma foto ou uma observação que confirme que a entrega foi feita. 
 * **Aplicativos móveis:** aplicativos para dispositivos móveis destinados exclusivamente para entregadores, para que eles possam realizar suas atividades sem acessar o Admin da loja.
 
-<div class = "alert alert-info">
-Os apps de <b>Fulfillment</b> e <b>Last Mile</b> para entregadores e motoristas estão disponíveis apenas para dispositivos Android.
-</div>
+>ℹ️ Os apps de **Fulfillment** e **Last Mile** para entregadores e motoristas estão disponíveis apenas para dispositivos Android.
 
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
index 4b0e05a35..466c0a48b 100644
--- a/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-activation.md
@@ -25,9 +25,7 @@ O vídeo abaixo apresenta todas as etapas da ativação, e na seção seguinte v
 
 ![vsncorreios_ativacao_PT](https://images.ctfassets.net/alneenqid6w5/3jkyhn9NypaHZBeXAib7iz/410d76ca2ba8b25cbfce2c0adcb27813/vsncorreios_ativacao.gif)
 
-<div class = "alert alert-info">
-Se você deseja integrar a sua operação com outras transportadoras além dos Correios, temos o <a href="https://vtex.com/br-pt/shipping-network/">VTEX Shipping Network</a>, com sugestões de parceiros selecionados pela nossa equipe com foco no seu modelo de negócio.
-</div>
+>ℹ️ Se você deseja integrar a sua operação com outras transportadoras além dos Correios, temos o [VTEX Shipping Network](https://vtex.com/br-pt/shipping-network/), com sugestões de parceiros selecionados pela nossa equipe com foco no seu modelo de negócio.
 
 ## Ativar VTEX Shipping Network Correios
 
diff --git a/docs/tutorials/pt/vtex-shipping-network-correios-faq.md b/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
index 8552ce555..b097e5300 100644
--- a/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
+++ b/docs/tutorials/pt/vtex-shipping-network-correios-faq.md
@@ -126,9 +126,7 @@ Um motivo recorrente é quando o peso ou as dimensões (comprimento, largura e a
 
 Portanto, certifique-se de que o peso e as dimensões dos itens no Catálogo refletem exatamente as características dos seus produtos.
 
-<div class = "alert alert-info">
-Quando existe uma divergência no cálculo de frete no relatório de envios dos Correios, você deve entrar em contato pelo email <i>vtexlog@vtex.com.br</i> e abrir um ticket solicitando a análise dos custos e detalhes dos envios. O relatório mencionado é enviado mensalmente para o email do contato definido na etapa de contração do <b>VTEX Shipping Network Correios</b>.
-</div>
+>ℹ️ Quando existe uma divergência no cálculo de frete no relatório de envios dos Correios, você deve entrar em contato pelo email <i>vtexlog@vtex.com.br</i> e abrir um ticket solicitando a análise dos custos e detalhes dos envios. O relatório mencionado é enviado mensalmente para o email do contato definido na etapa de contração do **VTEX Shipping Network Correios**.
 
 ## 9. Como posso emitir etiquetas de envio?
 
@@ -146,9 +144,7 @@ Você pode [escolher o tipo de formato das etiquetas de envio](https://help.vtex
 
 Essa fatura é feita pelo Admin VTEX como qualquer outra fatura e em determinado momento você seleciona a opção de referenciar os itens do pedido. Para o passo a passo completo, veja o artigo [Como faturar um pedido](https://help.vtex.com/pt/tutorial/faturar-um-pedido-manualmente--7p1h852V5t54KyscpgxE2v).
 
-<div class = "alert alert-info">
-Vale ressaltar que etiquetas de envio ficam disponíveis para impressão no <a href="https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs">Pronto para Envio</a> somente quando os itens do pedido foram referenciados na Nota Fiscal e o status de um pedido é <i>faturado</i>.
-</div>
+>ℹ️ Vale ressaltar que etiquetas de envio ficam disponíveis para impressão no [Pronto para Envio](https://help.vtex.com/pt/tutorial/pronto-para-envio--5YOZV7Aotv3pap0fGNESDs) somente quando os itens do pedido foram referenciados na Nota Fiscal e o status de um pedido é <i>faturado</i>.
 
 ## 11. É possível conciliar as minhas transportadoras atuais com o serviço dos Correios do VTEX Shipping Network Correios?
 
@@ -183,9 +179,7 @@ No Admin VTEX, a funcionalidade **Solicitar Informações** permite abrir um _Pe
 
 O seu contrato com o **VTEX Shipping Network Correios** permite utilizar o serviço de [Logística Reversa dos Correios](https://www.correios.com.br/enviar/encomendas/logistica-reversa). Para isso, a VTEX disponibiliza um login e uma senha para você utilizar no site dos Correios e gerar uma autorização de postagem.
 
-<div class = "alert alert-info">
-Para solicitar o seu login e senha para o serviço de <i>Logística Reversa dos Correios</i>, entre em contato com a VTEX pelo email <i>vtexlog@vtex.com.br</i>.
-</div>
+>ℹ️ Para solicitar o seu login e senha para o serviço de <i>Logística Reversa dos Correios</i>, entre em contato com a VTEX pelo email <i>vtexlog@vtex.com.br</i>.
 
 ## 16. Como descobrir a URL de rastreio de um pedido?
 
diff --git a/docs/tutorials/pt/vtex-tracking-overview.md b/docs/tutorials/pt/vtex-tracking-overview.md
index e0f3391bf..e3abc5a5f 100644
--- a/docs/tutorials/pt/vtex-tracking-overview.md
+++ b/docs/tutorials/pt/vtex-tracking-overview.md
@@ -21,9 +21,7 @@ VTEX Tracking é uma solução da VTEX voltada ao monitoramento de entregas. Ela
 - **Aplicativo Móvel**: de uso exclusivo do portador, ou motorista, que realiza as entregas.  
 - **Last Mile**: interface voltada à comunicação com o destinatário. 
 
-<div class = "alert alert-info">
-Confira como instalar e configurar a integração entre uma loja VTEX e a app VTEX Tracking no artigo <a href="https://help.vtex.com/pt/tutorial/como-instalar-e-configurar-a-app-vtex-tracking-no-seu-admin-vtex--3ejuFsJ1m0r08cT6afpIPf">Como instalar e configurar a app VTEX Tracking</a>.
-</div>
+>ℹ️ Confira como instalar e configurar a integração entre uma loja VTEX e a app VTEX Tracking no artigo [Como instalar e configurar a app VTEX Tracking](https://help.vtex.com/pt/tutorial/como-instalar-e-configurar-a-app-vtex-tracking-no-seu-admin-vtex--3ejuFsJ1m0r08cT6afpIPf).
 
 ## Plataforma web
 Através da plataforma web, os clientes VTEX Tracking realizam toda a gestão e monitoramento de suas entregas. Ela conta com as seguintes funcionalidades:
diff --git a/docs/tutorials/pt/web-page-performance.md b/docs/tutorials/pt/web-page-performance.md
index 584f968d2..126e662c3 100644
--- a/docs/tutorials/pt/web-page-performance.md
+++ b/docs/tutorials/pt/web-page-performance.md
@@ -15,9 +15,7 @@ legacySlug: performance-de-paginas-web
 subcategory: QPnz120TdtLcXSh65c4Gs
 ---
 
-<div class = "alert alert-info">
-Esta página está disponível somente para lojas que estão operando com o <a href="https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa">Novo Admin VTEX</a>. Para acessar esta página e fazer parte de uma nova experiência, participe do <a href="https://content.vtex.com/participe-do-programa-beta-pt/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta">programa Beta</a> do Novo Admin VTEX.
-</div>
+>ℹ️ Esta página está disponível somente para lojas que estão operando com o [Novo Admin VTEX](https://help.vtex.com/pt/announcements/bem-vindo-ao-novo-admin-vtex--5tLPBodp6Xu03vYdyBTGTa). Para acessar esta página e fazer parte de uma nova experiência, participe do [programa Beta](https://content.vtex.com/participe-do-programa-beta-pt/?utm_source=landing_page&utm_medium=help_center&utm_campaign=new_admin_beta) do Novo Admin VTEX.
 
 O [PageSpeed Insights](https://developers.google.com/speed/docs/insights/v5/about) é uma ferramenta desenvolvida pelo Google para gerar relatórios sobre o desempenho de uma página, tanto em dispositivos móveis quanto em computadores, fornecendo sugestões sobre como essa página pode ser aprimorada. A ferramenta usa as [Principais métricas da web do Google](https://web.dev/vitals/#core-web-vitals) para avaliar o desempenho online. 
 
@@ -48,9 +46,7 @@ Eles são obtidos a partir de simulações com o [Lighthouse](https://github.com
 
 Não compare os resultados desses dois tipos de dados. Como eles vêm de fontes diferentes e servem propósitos diferentes, não é possível compará-los. Saiba mais sobre a aplicação de cada tipo de dado na documentação [Métricas de desempenho centradas no usuário](https://web.dev/user-centric-performance-metrics/#how-metrics-are-measured) do Google.
 
-<div class = "alert alert-info">
-  O PageSpeed Insights analisa a atividade do 75º percentil dos carregamentos de páginas, diferenciando dispositivos móveis e computadores, para garantir que seu site atinja as metas recomendadas para todas as métricas.
-</div>
+>ℹ️ O PageSpeed Insights analisa a atividade do 75º percentil dos carregamentos de páginas, diferenciando dispositivos móveis e computadores, para garantir que seu site atinja as metas recomendadas para todas as métricas.
 
 ### Como usar dados de campo e de laboratório para otimizar as principais métricas da web
 
@@ -75,9 +71,7 @@ A URL é exibida em um card junto com:
 
 Navegue pelos links adicionados e selecione um deles para ser exibido na tela “Performance das páginas web”. Feito isso, analise as métricas de desempenho do link selecionado. Clique no ícone de menu <i class='fa-solid fa-ellipsis-vertical'></i>. Além disso, é possível acessar as opções `Copiar URL` e `Visitar página`; basta clicar nos botões correspondentes no card da URL.
 
-<div class = "alert alert-info">
-O PageSpeed Insights do Google também exibe métricas relacionadas a todo o domínio da URL inserida, caso não haja dados suficientes a serem exibidos para determinada página. O dashboard Performance das páginas web, por sua vez, exibe dados referentes apenas à URL, o que torna sua avaliação mais prática.
-</div>
+>ℹ️ O PageSpeed Insights do Google também exibe métricas relacionadas a todo o domínio da URL inserida, caso não haja dados suficientes a serem exibidos para determinada página. O dashboard Performance das páginas web, por sua vez, exibe dados referentes apenas à URL, o que torna sua avaliação mais prática.
 
 ### Quais URLs monitorar? 
 Se seu storefront estiver incorporado à VTEX, a página exibe, por padrão, as 10 principais páginas com mais acesso em sua loja. 
@@ -175,9 +169,7 @@ No dashboard de Performance das páginas web, você encontra os limites e as ava
 * **Precisam de melhorias:** de 50 a 90. O código de cor é laranja.
 * **Ruins**: abaixo de 50. O código de cor é vermelho.
 
-<div class = "alert alert-warning">
-  Observação: há uma variação significativa de desempenho entre as lojas e esta variação depende de como a arquitetura do seu storefront foi projetada. Storefronts complexos, com vários scripts e recursos externos, tendem a apresentar um desempenho com pontuações menores. Para lojas desenvolvidas com VTEX IO, consulte <a href="https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-debugging-performance-issues">VTEX IO: Debugging Performance Issues</a> (Depurando problemas de desempenho, em inglês). Para lojas que usam o <a href="https://www.faststore.dev/">FastStore</a>, há um <a href="https://www.faststore.dev/releases/2022/04/22/webops">relatório automatizado do Lighthouse sobre visualizações de implantação</a>.
-  </div>
+>⚠️ Observação: há uma variação significativa de desempenho entre as lojas e esta variação depende de como a arquitetura do seu storefront foi projetada. Storefronts complexos, com vários scripts e recursos externos, tendem a apresentar um desempenho com pontuações menores. Para lojas desenvolvidas com VTEX IO, consulte [VTEX IO: Debugging Performance Issues](https://developers.vtex.com/vtex-developer-docs/docs/vtex-io-documentation-debugging-performance-issues) (Depurando problemas de desempenho, em inglês). Para lojas que usam o [FastStore](https://www.faststore.dev/), há um [relatório automatizado do Lighthouse sobre visualizações de implantação](https://www.faststore.dev/releases/2022/04/22/webops).
 
 Abaixo da pontuação são exibidas as pontuações individuais em uma lista de métricas da web, junto com o código de cor que indica o seu intervalo. Para atualizar manualmente a pontuação, clique no ícone de atualização <i class='fa fa-refresh'></i>.
 
diff --git a/docs/tutorials/pt/what-is-an-attachment.md b/docs/tutorials/pt/what-is-an-attachment.md
index df3cae1b1..21214140e 100644
--- a/docs/tutorials/pt/what-is-an-attachment.md
+++ b/docs/tutorials/pt/what-is-an-attachment.md
@@ -17,9 +17,7 @@ subcategory: 1hoOi2R0Rm6ky0yCwOUoiy
 
 Um anexo é a customização, opcional e sem custo, de um produto. Ele é utilizado para adicionar uma informação a um SKU. Essa informação pode ser relacionada a um [serviço](/pt/tutorial/o-que-e-um-servico) ou ao próprio item comprado.
 
-<div class = "alert alert-warning">
-A VTEX não controla o estoque de um anexo. Sendo essa a função do marketplace ou do seller. 
-</div>
+>⚠️ A VTEX não controla o estoque de um anexo. Sendo essa a função do marketplace ou do seller.
 
 Se o seu item comprado for uma Camisa da Seleção Brasileira, o nome do seu Anexo pode ser __Personalização__, e suas chaves:
 
diff --git a/docs/tutorials/pt/what-is-order-configuration.md b/docs/tutorials/pt/what-is-order-configuration.md
index d6e8db4ef..6cb8750bf 100644
--- a/docs/tutorials/pt/what-is-order-configuration.md
+++ b/docs/tutorials/pt/what-is-order-configuration.md
@@ -34,6 +34,4 @@ Por API, você deve associar uma [tabela de preços](https://help.vtex.com/pt/tr
 
 Caso o usuário configure um cenário que não apresente nenhuma tabela de preços associada, será usada uma tabela de preços default.
 
-<div class = "alert alert-info">
-  <p>É importante destacar que o usuário precisa estar logado para usar o Order Configuration e, assim, visualizar os diferentes preços baseado na sua configuração</p>
-</div>
+>ℹ️ É importante destacar que o usuário precisa estar logado para usar o Order Configuration e, assim, visualizar os diferentes preços baseado na sua configuração
diff --git a/docs/tutorials/pt/what-is-the-difference-between-unbinding-and-removing-seller-sku.md b/docs/tutorials/pt/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
index c50d8e485..4fa498d70 100644
--- a/docs/tutorials/pt/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
+++ b/docs/tutorials/pt/what-is-the-difference-between-unbinding-and-removing-seller-sku.md
@@ -19,9 +19,7 @@ Todos os produtos que chegam do seller para o marketplace passam pelo módulo [S
 
 Ao [desvincular o SKU](https://help.vtex.com/pt/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX#desvincular-sku) do seller, o SKU deixa de estar disponível e não é mais exibido no marketplace. Além disso, o SKU desvinculado não recebe mais atualizações de preço e estoque.
 
-<div class = "alert alert-info">
-Um SKU desvinculado não retorna para a fila de aprovação da página <b>SKUs Recebidos</b>, pois continua existindo no catálogo do marketplace.
-</div>
+>ℹ️ Um SKU desvinculado não retorna para a fila de aprovação da página **SKUs Recebidos**, pois continua existindo no catálogo do marketplace.
 
 Se o objetivo do marketplace é excluir permanentemente o SKU do seller, é preciso [remover o SKU](https://help.vtex.com/pt/tutorial/vinculos-de-sku--1SmrVgNwjJX17hdqwLa0TX#remover), pois desta forma o SKU do seller deixa de fazer parte do catálogo do marketplace. Para voltar a fazer parte do catálogo novamente, o SKU precisa ser enviado novamente pelo seller e aprovado pelo marketplace.
 
diff --git a/docs/tutorials/pt/what-is-the-sponsor-user.md b/docs/tutorials/pt/what-is-the-sponsor-user.md
index 4cedf2569..77fc4452f 100644
--- a/docs/tutorials/pt/what-is-the-sponsor-user.md
+++ b/docs/tutorials/pt/what-is-the-sponsor-user.md
@@ -17,9 +17,7 @@ subcategory: 63DHe3VQEEE6Uuua8gIs2M
 
 Cada conta VTEX tem apenas um usuário Titular - o único a quem é dado acesso total a todas as seções do Admin, incluindo ações importantes de manutenção e autorização. 
 
-<div class = "alert alert-warning"> 
-Usuário Titular não é o mesmo que <b>Owner (Admin Super)</b>. O <b>Owner (Admin Super)</b> é um perfil de acesso do License Manager, que define permissões concedidas a um dado usuário da sua loja, podendo inclusive ser atribuído a múltiplos usuários.
-</div>
+>⚠️ Usuário Titular não é o mesmo que **Owner (Admin Super)**. O **Owner (Admin Super)** é um perfil de acesso do License Manager, que define permissões concedidas a um dado usuário da sua loja, podendo inclusive ser atribuído a múltiplos usuários.
 
 A página de gerenciamento do Titular permite identificar o usuário Titular atual, transferir a propriedade da loja e visualizar o log de atividades associado às ações do usuário Titular. Para acessar esta página, clique em **Configurações da conta** > **Gerenciamento da conta** > **Conta**. Na seção Contato, clique em `Gerenciamento de titulares`.
 
diff --git a/docs/tutorials/pt/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md b/docs/tutorials/pt/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
index 1e6d7f831..7ec07c7e1 100644
--- a/docs/tutorials/pt/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
+++ b/docs/tutorials/pt/what-to-do-when-i-need-to-use-for-a-product-words-that-may-be-ignored-by.md
@@ -15,9 +15,7 @@ legacySlug: o-que-fazer-quando-preciso-usar-para-um-produto-palavras-que-podem-s
 subcategory: pwxWmUu7T222QyuGogs68
 ---
 
-<div class = "alert alert-warning">
-  A VTEX apresenta duas opções da busca - a busca do Portal CMS Legado e o VTEX Intelligent Search. Esse artigo se refere à busca do Portal CMS Legado. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse a trilha <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">Intelligent Search</a>.
-</div>
+>⚠️ A VTEX apresenta duas opções da busca - a busca do Portal CMS Legado e o VTEX Intelligent Search. Esse artigo se refere à busca do Portal CMS Legado. Para saber mais sobre o aplicativo VTEX Intelligent Search acesse a trilha <a href = "https://help.vtex.com/pt/tracks/vtex-intelligent-search--19wrbB7nEQcmwzDPl1l4Cb">Intelligent Search</a>.
 
 Se você precisa utilizar, em seus produtos, palavras que talvez não sejam importantes para o buscador, existem algumas boas práticas que podem ser adotadas:
 
diff --git a/docs/tutorials/pt/white-label-seller.md b/docs/tutorials/pt/white-label-seller.md
index 78acbb036..a39667f96 100644
--- a/docs/tutorials/pt/white-label-seller.md
+++ b/docs/tutorials/pt/white-label-seller.md
@@ -30,18 +30,14 @@ A [conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account
 
 Utilizar a conta franquia é estratégico para operações que desejam expandir suas vendas com a integração de lojas físicas, por exemplo, pois existe a facilidade de herdar um catálogo já cadastrado na plataforma VTEX. Saiba mais em [O que é conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
-<div class = "alert alert-info">
-Por padrão, toda conta franquia é um seller white label da conta principal. E apesar de seller white label e conta franquia serem conceitos relacionados, eles não são correspondentes, pois seller white label é um tipo de seller e conta franquia é um tipo de conta.
-</div>
+>ℹ️ Por padrão, toda conta franquia é um seller white label da conta principal. E apesar de seller white label e conta franquia serem conceitos relacionados, eles não são correspondentes, pois seller white label é um tipo de seller e conta franquia é um tipo de conta.
 
 É possível que uma conta padrão atue como seller white label de uma outra loja VTEX, cenário no qual o marketplace não informa ao consumidor quem é o seller que realiza o envio do pedido. Outra possibilidade é uma conta franquia atuar como um seller normal de um marketplace que não seja a conta principal. Em resumo:
 
 - **Conta:** pode ser do tipo conta franquia ou conta padrão.
 - **Seller:** pode ser do tipo comum ou white label.
 
-<div class = "alert alert-info">
-Para adicionar um seller white label é necessário ter esse modelo previsto no contrato com a VTEX. Uma vez ajustado o contrato com o representante comercial da VTEX responsável por seu marketplace, solicite a adição de uma conta franquia por meio do nosso Suporte. Toda conta franquia é criada como seller white label e não é possível mudar o tipo de seller após a sua criação.
-  </div>
+>ℹ️ Para adicionar um seller white label é necessário ter esse modelo previsto no contrato com a VTEX. Uma vez ajustado o contrato com o representante comercial da VTEX responsável por seu marketplace, solicite a adição de uma conta franquia por meio do nosso Suporte. Toda conta franquia é criada como seller white label e não é possível mudar o tipo de seller após a sua criação.
 
 ### Saiba mais
 
diff --git a/docs/tutorials/pt/white-label-sellers-selection.md b/docs/tutorials/pt/white-label-sellers-selection.md
index 2e418a4c5..23216d10c 100644
--- a/docs/tutorials/pt/white-label-sellers-selection.md
+++ b/docs/tutorials/pt/white-label-sellers-selection.md
@@ -22,9 +22,7 @@ Existem dois tipos de sellers na VTEX:
 - **Seller comum:** o seller é visível na vitrine do marketplace e pode ser escolhido pelo consumidor durante sua experiência de compra.
 - **[Seller white label](https://help.vtex.com/pt/tutorial/definicoes-de-conta-franquia-e-seller-white-label--5orlGHyDHGAYciQ64oEgKa):** o seller permanece oculto na experiência de compra do consumidor e é selecionado de forma automática pela plataforma VTEX para realizar o envio do pedido.
 
-<div class = "alert alert-info">
-Na VTEX, a conta franquia é um tipo de conta criada associada a uma conta principal e tem a característica de ser um seller white label da conta principal. Esse modelo de negócio é estratégico para lojistas que desejam conectar lojas físicas ao seu canal digital de venda, saiba mais em <a href="https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl">O que é conta franquia</a>.
-</div>
+>ℹ️ Na VTEX, a conta franquia é um tipo de conta criada associada a uma conta principal e tem a característica de ser um seller white label da conta principal. Esse modelo de negócio é estratégico para lojistas que desejam conectar lojas físicas ao seu canal digital de venda, saiba mais em [O que é conta franquia](https://help.vtex.com/pt/tutorial/what-is-a-franchise-account--kWQC6RkFSCUFGgY5gSjdl).
 
 Quando o consumidor navega no marketplace, seja na etapa da vitrine ou no carrinho, as informações sobre disponibilidade dos itens e opções de envio dos sellers apresentadas ao consumidor podem variar, a depender do marketplace saber ou não a localização desse comprador. Diante disso, este artigo se divide em:
 
@@ -39,9 +37,7 @@ Quando os clientes navegam pelo marketplace, sua expectativa é visualizar produ
 - [Vitrine sem localização do cliente](#vitrine-sem-localizacao-do-cliente)
 - [Vitrine com localização do cliente](#vitrine-com-localizacao-do-cliente)
 
-<div class = "alert alert-info">
-Na etapa da vitrine, a plataforma VTEX não considera as opções de envio dos sellers, isso só é feito quando o cliente insere seu endereço no checkout. Portanto, é possível que o preço e a disponibilidade apresentados na vitrine sejam diferentes no fechamento da compra.
-</div>
+>ℹ️ Na etapa da vitrine, a plataforma VTEX não considera as opções de envio dos sellers, isso só é feito quando o cliente insere seu endereço no checkout. Portanto, é possível que o preço e a disponibilidade apresentados na vitrine sejam diferentes no fechamento da compra.
 
 ### Vitrine sem localização do cliente
 
@@ -79,9 +75,7 @@ Após filtrar todos os sellers com base nos critérios apresentados, é feita um
 - [Entrega](#tipo-de-envio-entrega): o cliente recebe o pedido no seu endereço.
 - [Retirada](#tipo-de-envio-retirada): o cliente retira o pedido em um [ponto de retirada](https://help.vtex.com/pt/tutorial/pontos-de-retirada--2fljn6wLjn8M4lJHA6HP3R).
 
-<div class = "alert alert-info">
-Por padrão, do total de até doze sellers, até seis realizam a entrega e até seis a retirada. No entanto, se menos de seis sellers atenderem aos critérios de um tipo de envio, é possível que a lista de sellers do outro tipo seja maior que seis. Por exemplo, se somente cinco sellers entregam o pedido, a lista de retirada pode ser composta de sete sellers, de forma a totalizar doze sellers.
-</div>
+>ℹ️ Por padrão, do total de até doze sellers, até seis realizam a entrega e até seis a retirada. No entanto, se menos de seis sellers atenderem aos critérios de um tipo de envio, é possível que a lista de sellers do outro tipo seja maior que seis. Por exemplo, se somente cinco sellers entregam o pedido, a lista de retirada pode ser composta de sete sellers, de forma a totalizar doze sellers.
 
 #### Tipo de envio: entrega
 
@@ -96,13 +90,12 @@ A seleção de até seis sellers white label para envio do tipo entrega é feita
 6. A partir dos sellers selecionados para cobrir o carrinho, a plataforma VTEX calcula as combinações menos numerosas de sellers.
 7. Dentre essas combinações, é feita uma lista de, no máximo, seis sellers para envio do tipo entrega.
 
-<div class = "alert alert-info">
-É possível que em alguma etapa da seleção haja um empate de sellers. Quando isso ocorre, a seleção se divide em duas frentes, de forma a selecionar:
-<ul>
-  <li>Até três sellers que apresentam o melhor custo.</li>
-  <li>Até três sellers que apresentam o melhor prazo.</li>
-</ul>
-</div>
+>ℹ️ É possível que em alguma etapa da seleção haja um empate de sellers. Quando isso ocorre, a seleção se divide em duas frentes, de forma a selecionar:
+>
+> * Até três sellers que apresentam o melhor custo.
+>
+> * Até três sellers que apresentam o melhor prazo.
+> 
 
 Se existir um empate entre sellers nos critérios de melhor custo ou prazo, o critério do desempate é o seller ter a maior quantidade de SKUs em estoque.
 
@@ -168,9 +161,7 @@ A seleção de até seis sellers para envio do tipo retirada é planejada para o
       - **Melhor prazo:** sellers que disponibilizam os produtos para a coleta em menos tempo.
       - **Melhor custo:** sellers que oferecem menores preços para retirada do pedido.
 
-<div class = "alert alert-info">
-Quando existe um empate no critério de melhor custo ou melhor prazo, o fator de desempate é o seller ter a maior quantidade de SKUs no estoque.
-</div>
+>ℹ️ Quando existe um empate no critério de melhor custo ou melhor prazo, o fator de desempate é o seller ter a maior quantidade de SKUs no estoque.
 
 ##### Exemplo para envio tipo retirada
 

From db158060bf706b564c7ca8938eb8f6a51bb2fc8a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BAlia=20Rabello?=
 <77292838+julia-rabello@users.noreply.github.com>
Date: Tue, 27 Aug 2024 14:56:15 -0300
Subject: [PATCH 13/13] fix asterisk manually

also fixed in https://app.contentful.com/spaces/alneenqid6w5/environments/master/entries/5xklf2wSdeztQh4iy5kJvD?focusedField=text&focusedLocale=es
---
 docs/tracks/en/sending-products-to-amazon.md | 2 +-
 docs/tracks/es/sending-products-to-amazon.md | 2 +-
 docs/tracks/pt/sending-products-to-amazon.md | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/tracks/en/sending-products-to-amazon.md b/docs/tracks/en/sending-products-to-amazon.md
index 0599b7515..5a11be265 100644
--- a/docs/tracks/en/sending-products-to-amazon.md
+++ b/docs/tracks/en/sending-products-to-amazon.md
@@ -51,7 +51,7 @@ To map a category, follow these steps:
 4. Match the attributes in the side window, as shown in the image below: ![Amazon Mapper Attributes](https://downloads.ctfassets.net/alneenqid6w5/3gw5pXd6bvjIMs4ydBLmwv/da4ea7365efc744b036e55305feaea6f/mapper_amazon_atributos.gif)  
 5. Click the `Save Changes` button.  
 
->❗ Fields with an * asterisks are required.
+>❗ Fields with an asterisk (`*`) are required.
 >
 >
 > Completing an attribute can trigger new required fields that only become visible under **Marketplace > Connections > Products** after the mapping has been saved.</br>
diff --git a/docs/tracks/es/sending-products-to-amazon.md b/docs/tracks/es/sending-products-to-amazon.md
index 0387f587a..cadc7d725 100644
--- a/docs/tracks/es/sending-products-to-amazon.md
+++ b/docs/tracks/es/sending-products-to-amazon.md
@@ -53,7 +53,7 @@ Para realizar el mapeo de categorías:
 
 5. Haz clic en el botón `Guardar cambios`.
 
->❗ Los campos marcados con un asterisco * son obligatorios.
+>❗ Los campos marcados con un asterisco (`*`) son obligatorios.
 >
 >
 > Al ingresar un atributo pueden activarse nuevos campos obligatorios que solo serán visibles en la página **Marketplace > Conexiones > Productos,** después de guardar el mapeo.</br>
diff --git a/docs/tracks/pt/sending-products-to-amazon.md b/docs/tracks/pt/sending-products-to-amazon.md
index 11007f588..c96fdd9b8 100644
--- a/docs/tracks/pt/sending-products-to-amazon.md
+++ b/docs/tracks/pt/sending-products-to-amazon.md
@@ -54,7 +54,7 @@ Para realizar o mapeamento de categorias:
 
 5. Clique no botão __`Salvar Alterações`__.  
 
->❗ Os campos sinalizados com o asterisco ***** são obrigatórios.  
+>❗ Os campos sinalizados com o asterisco (`*`) são obrigatórios.  
 > O preenchimento de um atributo pode desencadear novos campos obrigatórios que só ficarão visíveis na página ** Marketplace> Conexões> Produtos, ** após salvar o mapeamento.  
 
 ### Mapeamento via Planilha